From owner-freebsd-current Sun Nov 8 00:16:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA13257
for freebsd-current-outgoing; Sun, 8 Nov 1998 00:16:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13252
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 00:16:49 -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 TAA18086;
Sun, 8 Nov 1998 19:16:28 +1100
Date: Sun, 8 Nov 1998 19:16:28 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811080816.TAA18086@godzilla.zeta.org.au>
To: phk@critter.freebsd.dk, wpaul@skynet.ctr.columbia.edu
Subject: Re: Grrr... calcru: negative time blah blah blah
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> >debug.tc_diag_buffer: 11932 11932 11932 11937 [...]
>> >[...] 11932 11932 49982 50184 50259 11934 11930 [...]
>>
>> This is bad, really really bad. Best case sequence is:
>>
>> 11932: hardclock()
>> 11932: hardclock()
>> 49982: {micro|nano}[run]time()
>> 50184: {micro|nano}[run]time()
>> 50259: hardclock()
>> 11934: hardclock()
>>
>> At least 4 calls to hardclock() is missing here.
>
>Hm...
Timecounter strangeness seems to be only a symptom here. I've seen
similar strangeness caused by ddb masking interrupts. However,
{micro|nano}[run]time() only have obvious problems when tco_delta()
overflows a u_int. Overflow occurs after only about 10 seconds for
a 400MHz tsc timecounter, but not for one hour for an i8254 timecounter.
>> Does the problem also exist for a !SMP case ?
>
>Okay, I built a kernel with no apm0 device and tried again. It seems
>that now I don't get the calcru error messages and the X server actually
>runs without exploding. No other processes die, at least not during
>the time I had it running. However, the system did get sluggish again
>after the X server started.
>sysctl kern.timecounter shows this:
>kern.timecounter.frequency: 448623175
>kern.timecounter.adjustment: 0
"Lost" (probably actually blocked) interrupts account for the sluggishness,
and the the timecounter problems apparently don't occur because the tsc
timecounter advances even when you don't look at it.
>Running sysctl debug _BEFORE_ triggering the problem by running the
>X server shows this:
>...
>debug.tc_diag_maxforward: -692379806
This apparently gets set to a bad value during initialization. There
must be some sign extension bugs for a negative value to be the maximum.
>Running sysctl debug _AFTER_ running and stopping the X server shows
>this:
>
>debug.elf_trace: 0
>debug.tc_diag_buffer: 24640675 24640697 24640635 24640686 24640672 24640673 24641091 4938 12316 24640342 24640621 24640649 24640659 24640686 19566403 19641525 19642603 19757035 20530799 20631303 20644237 20684791 20703487 24641328 24640255 24640435 246410
>77 24640268 24640686 24640690 24640656 24640671 24640659 24640790 24640596 24641023 24640295 24640672 24640673 24640672 24640673 24640686 24640659 24640699 24641102 24640216 24640686 24640694 24640638 24640686 24640672 24640673 24640686 24641077 24640254
>Everything seems to have been divided in half. The machine still runs
I think that's just because one of {micro|nano}[run]time() is now called
about twice per clock tick.
>Isn't there any way I can mask a particular interrupt so the dispatcher
>just ignores it? Not a great fix I grant you, but it would help prove
>the theory.
intr_handler[n] = null_routine;
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 00:17:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA13392
for freebsd-current-outgoing; Sun, 8 Nov 1998 00:17:00 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from geisha.samurai.com (geisha.samurai.com [205.207.28.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13282
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 00:16:56 -0800 (PST)
(envelope-from bryanf@geisha.samurai.com)
Received: (from bryanf@localhost)
by geisha.samurai.com (8.9.1a/8.9.1) id DAA14242
for freebsd-current@freebsd.org; Sun, 8 Nov 1998 03:16:41 -0500 (EST)
Date: Sun, 8 Nov 1998 03:16:41 -0500
From: Bryan Fullerton <bryanf@samurai.com>
To: freebsd-current@FreeBSD.ORG
Subject: aic0 again..
Message-ID: <19981108031641.E9754@samurai.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.15i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I was just reading on the list archives about the impending CAM drivers for
aic cards back in September - did these ever come to be? I'm still getting
errors about missing files when I do a make depend on -current, cvsup'ed
earlier this evening.
Specifically, I have an Adaptec 1522A card which I'd like to use.
Thanks,
Bryan
--
Bryan Fullerton http://www.samurai.com/
Owner, Lead Consultant http://www.feh.net/
Samurai Consulting http://www.icomm.ca/
"No, we don't do seppuku." Can you feel the Ohmu call?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 00:33:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA14330
for freebsd-current-outgoing; Sun, 8 Nov 1998 00:33:00 -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 AAA14322
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 00:32:57 -0800 (PST)
(envelope-from ken@panzer.plutotech.com)
Received: (from ken@localhost)
by panzer.plutotech.com (8.9.1/8.8.5) id BAA14750;
Sun, 8 Nov 1998 01:32:37 -0700 (MST)
From: "Kenneth D. Merry" <ken@plutotech.com>
Message-Id: <199811080832.BAA14750@panzer.plutotech.com>
Subject: Re: aic0 again..
In-Reply-To: <19981108031641.E9754@samurai.com> from Bryan Fullerton at "Nov 8, 98 03:16:41 am"
To: bryanf@samurai.com (Bryan Fullerton)
Date: Sun, 8 Nov 1998 01:32:37 -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
Bryan Fullerton wrote...
> I was just reading on the list archives about the impending CAM drivers for
> aic cards back in September - did these ever come to be? I'm still getting
> errors about missing files when I do a make depend on -current, cvsup'ed
> earlier this evening.
>
> Specifically, I have an Adaptec 1522A card which I'd like to use.
Brian Beattie <beattie@aracnet.com> has been working on the driver, but it
isn't done yet.
I would suggest getting another SCSI card if you want to use your SCSI
peripherals any time soon.
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 Sun Nov 8 00:47:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA15432
for freebsd-current-outgoing; Sun, 8 Nov 1998 00:47:07 -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 AAA15424
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 00:47:04 -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 JAA14431;
Sun, 8 Nov 1998 09:42:56 +0100 (CET)
To: Bruce Evans <bde@zeta.org.au>
cc: wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG
Subject: Re: Grrr... calcru: negative time blah blah blah
In-reply-to: Your message of "Sun, 08 Nov 1998 19:16:28 +1100."
<199811080816.TAA18086@godzilla.zeta.org.au>
Date: Sun, 08 Nov 1998 09:42:56 +0100
Message-ID: <14429.910514576@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 <199811080816.TAA18086@godzilla.zeta.org.au>, Bruce Evans writes:
>Timecounter strangeness seems to be only a symptom here. I've seen
>similar strangeness caused by ddb masking interrupts. However,
>{micro|nano}[run]time() only have obvious problems when tco_delta()
>overflows a u_int. Overflow occurs after only about 10 seconds for
>a 400MHz tsc timecounter, but not for one hour for an i8254 timecounter.
Uhm, it happens earlier for a i8254, in fact it happens whenever more
than one interrupt is lost. The majority of the bits are software
bits.
>>Running sysctl debug _BEFORE_ triggering the problem by running the
>>X server shows this:
>>...
>>debug.tc_diag_maxforward: -692379806
>
>This apparently gets set to a bad value during initialization. There
>must be some sign extension bugs for a negative value to be the maximum.
sysctl doesnt know about unsigned ints.
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 00:54:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA15964
for freebsd-current-outgoing; Sun, 8 Nov 1998 00:54:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15959
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 00:54:36 -0800 (PST)
(envelope-from xroot@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
by implode.root.com (8.8.5/8.8.5) with ESMTP id AAA09445;
Sun, 8 Nov 1998 00:55:50 -0800 (PST)
Message-Id: <199811080855.AAA09445@implode.root.com>
To: "George W. Dinolt" <george.w.dinolt@lmco.com>
cc: Robert Schulhof <rrs@LMI.Net>, freebsd-current@FreeBSD.ORG
Subject: Re: libc_r link error
In-reply-to: Your message of "Sat, 07 Nov 1998 19:15:12 PST."
<36450CC0.7F05F71A@lmco.com>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sun, 08 Nov 1998 00:55:50 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> I'm having problems linking to libc_r using cc/egcs1.1 with a current as of
>> today version of the library. I get an unresolved symbol SYS_sendfile which
>> I can't track down. I can't find a reference to sendfile() in
>> any of the library source code, except for a man page
>>
>> /usr/lib/libc_r.so: undefined reference to `SYS_sendfile'
>The upshot of all this (pedantry) is that updating syscall.h in
>/usr/include/sys and recompiling libc_r (after removing the offending
>files) fixed the problem. Of course the "right" thing to do is a new
>"make world". That will happen tonight after I go to bed.
On systems with SHARED=copies (the default), you need to do a "make
includes" before rebuilding the libraries.
-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 Sun Nov 8 01:06:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA16925
for freebsd-current-outgoing; Sun, 8 Nov 1998 01:06:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cassiopeia.hkstar.com (cassiopeia.hkstar.com [202.82.3.11])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16920
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 01:06:00 -0800 (PST)
(envelope-from c5666305@b1.hkstar.com)
Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87])
by cassiopeia.hkstar.com (8.9.1/8.9.1) with ESMTP id RAA16028
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 17:05:46 +0800 (HKT)
Received: (from c5666305@localhost)
by b1.hkstar.com (8.8.8/8.8.8) id RAA15058
for freebsd-current@freebsd.org; Sun, 8 Nov 1998 17:08:05 +0800 (HKT)
From: Chan Yiu Wah <c5666305@b1.hkstar.com>
Message-Id: <199811080908.RAA15058@b1.hkstar.com>
Subject: how to solve error for ctm src-cur.3587.gz
To: freebsd-current@FreeBSD.ORG
Date: Sun, 8 Nov 1998 17:08:05 +0800 (HKT)
X-Mailer: ELM [version 2.5 PL0b1]
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,
I recent y tried to ctm the src-cur.3587.gz to my system and I got
the error message.
FN: sys/i386/conf/GENERIC md5 mistmatch
FN: sys/i386/conf/GENERIC edit fail
Can anyone tell me how to solve ? I have tried to get the src-cur.3587.gz
from fto.freebsd.org and it didn't help to solve the problem. Pleas help.
Cheers.
Clarence
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 02:06:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA20415
for freebsd-current-outgoing; Sun, 8 Nov 1998 02:06:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20400
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 02:05: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 VAA24481;
Sun, 8 Nov 1998 21:05:41 +1100
Date: Sun, 8 Nov 1998 21:05:41 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811081005.VAA24481@godzilla.zeta.org.au>
To: bde@zeta.org.au, phk@critter.freebsd.dk
Subject: Re: Grrr... calcru: negative time blah blah blah
Cc: current@FreeBSD.ORG, wpaul@skynet.ctr.columbia.edu
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>>Timecounter strangeness seems to be only a symptom here. I've seen
>>similar strangeness caused by ddb masking interrupts. However,
>>{micro|nano}[run]time() only have obvious problems when tco_delta()
>>overflows a u_int. Overflow occurs after only about 10 seconds for
>>a 400MHz tsc timecounter, but not for one hour for an i8254 timecounter.
>
>Uhm, it happens earlier for a i8254, in fact it happens whenever more
>than one interrupt is lost. The majority of the bits are software
>bits.
That's neither (C) overflow nor in {micro|nano}[run]time(). When the
low-level i8254 timecounter is not called often enough, the timecounter
just drops some multiple of timer0_max_count (about 11932) timecounter
ticks. This doesn't necessarily happen when more than one interrupt
is lost -- it happens when the low-level timecounter is not called for
more than (2 - epsilon) interrupt periods. There must have been some
low-level timecounter calls for the observed timecounter deltas to be
more than (2 * timer0_max_count).
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 02:11:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA20628
for freebsd-current-outgoing; Sun, 8 Nov 1998 02:11:48 -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 CAA20618
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 02:11:42 -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 LAA14667;
Sun, 8 Nov 1998 11:10:07 +0100 (CET)
To: Bruce Evans <bde@zeta.org.au>
cc: current@FreeBSD.ORG, wpaul@skynet.ctr.columbia.edu
Subject: Re: Grrr... calcru: negative time blah blah blah
In-reply-to: Your message of "Sun, 08 Nov 1998 21:05:41 +1100."
<199811081005.VAA24481@godzilla.zeta.org.au>
Date: Sun, 08 Nov 1998 11:10:07 +0100
Message-ID: <14665.910519807@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 <199811081005.VAA24481@godzilla.zeta.org.au>, Bruce Evans writes:
>>>Timecounter strangeness seems to be only a symptom here. I've seen
>>>similar strangeness caused by ddb masking interrupts. However,
>>>{micro|nano}[run]time() only have obvious problems when tco_delta()
>>>overflows a u_int. Overflow occurs after only about 10 seconds for
>>>a 400MHz tsc timecounter, but not for one hour for an i8254 timecounter.
>>
>>Uhm, it happens earlier for a i8254, in fact it happens whenever more
>>than one interrupt is lost. The majority of the bits are software
>>bits.
>
>That's neither (C) overflow nor in {micro|nano}[run]time(). When the
>low-level i8254 timecounter is not called often enough, the timecounter
>just drops some multiple of timer0_max_count (about 11932) timecounter
>ticks. This doesn't necessarily happen when more than one interrupt
>is lost -- it happens when the low-level timecounter is not called for
>more than (2 - epsilon) interrupt periods. There must have been some
>low-level timecounter calls for the observed timecounter deltas to be
>more than (2 * timer0_max_count).
ahh, DuH!, yes. erhm. you're right...
So we're back to square one: this doesn't really look like a
timecounter problem...
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 03:06:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA26435
for freebsd-current-outgoing; Sun, 8 Nov 1998 03:06:14 -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 DAA26422;
Sun, 8 Nov 1998 03:06:11 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.59.121])
by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA2D1B; Sun, 8 Nov 1998 12:05:55 +0100
Message-ID: <XFMail.981108120955.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, 08 Nov 1998 12:09:55 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: FreeBSD Current <current@FreeBSD.ORG>,
FreeBSD Hackers <hackers@FreeBSD.ORG>
Subject: AWE-32
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi guys,
sorry for posting to two lists, but the problem might or might not be relevant
to CURRENT. Couldn't determine yet.
Problem is, I was trying to set-up my SoundBlaster AWE-32, when rebooting I got
the fooling stuff at probing:
Probing for PnP devices:
CSN 1 Vendor ID: CTL009c [0x9c008c0e] Serial 0x10046cf4 Comp ID: PNP0600
[0x0006d041]
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
Hold it! That's awkward...
controller snd0
device sb0 at isa? port 0x220 irq 5 drq 1
device sbxvi0 at isa? drq 5
device sbmidi0 at isa? port 0x330
device awe0 at isa? port 0x620
Am I missing something in here?
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
*BSD & picoBSD: 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 Sun Nov 8 03:18:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA27725
for freebsd-current-outgoing; Sun, 8 Nov 1998 03:18: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 DAA27687
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 03:18:03 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2])
by nlsystems.com (8.9.1/8.8.5) with SMTP id LAA18882;
Sun, 8 Nov 1998 11:17:32 GMT
Date: Sun, 8 Nov 1998 11:17:32 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Robert Schulhof <rrs@LMI.Net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: libc_r link error
In-Reply-To: <199811072258.OAA22536@badlans.lanminds.com>
Message-ID: <Pine.BSF.4.01.9811081116310.16226-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, 7 Nov 1998, Robert Schulhof wrote:
>
> Hi,
>
> I'm having problems linking to libc_r using cc/egcs1.1 with a current as of
> today version of the library. I get an unresolved symbol SYS_sendfile which
> I can't track down. I can't find a reference to sendfile() in
> any of the library source code, except for a man page
>
>
> /usr/lib/libc_r.so: undefined reference to `SYS_sendfile'
There is a new syscall. You need to do a make world really but a
workaround might be to install sys/syscall.h by hand and then rebuild
libc.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 951 1891
Fax: +44 181 381 1039
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 03:18:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA27741
for freebsd-current-outgoing; Sun, 8 Nov 1998 03:18:24 -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 DAA27735
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 03:18:18 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.59.121])
by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA33B5 for <current@FreeBSD.ORG>;
Sun, 8 Nov 1998 12:17:53 +0100
Message-ID: <XFMail.981108122153.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, 08 Nov 1998 12:21:53 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: FreeBSD Current <current@FreeBSD.ORG>
Subject: ZIP, again
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Well since the archives for current are dead, I am forced to ask again on the
list...
I have a ZIP+ Drive on my parallel port that I want to use... Last time I asked
I was using a SNAP 3.0 but I am now fully CURRENT (as far as can be) and am
giving it a shot again.
controller ppbus0
controller vpo0 at ppbus?
device nlpt0 at ppbus?
device ppi0 at ppbus?
controller ppc0 at isa? disable port ? tty irq 7
This is right afaik... Yet when I reboot I get this:
[chronias] asmodai $ dmesg
Copyright (c) 1992-1998 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 3.0-CURRENT #3: Sat Nov 7 20:56:15 CET 1998
asmodai@chronias.ninth-circle.org:/work/cvs/src/sys/compile/CHRONIAS
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium/P55C (199.43-MHz 586-class CPU)
Origin = "GenuineIntel" Id = 0x544 Stepping=4
Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX>
real memory = 100663296 (98304K bytes)
config> quit
avail memory = 95002624 (92776K bytes)
Probing for devices on PCI bus 0:
chip0: <Intel 82437VX PCI cache memory controller> rev 0x02 on pci0.0.0
chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.7.0
ahc0: <Adaptec 2940 Ultra SCSI adapter> rev 0x00 int a irq 11 on pci0.17.0
ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
vga0: <Tseng Labs ET6000 graphics accelerator> rev 0x30 int a irq 9 on pci0.18.0
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> rev 0x02 int a irq 12 on
pci0.20.0
fxp0: Ethernet address 00:a0:c9:4d:2f:4f
Probing for PnP devices:
CSN 1 Vendor ID: CTL009c [0x9c008c0e] Serial 0x10046cf4 Comp ID: PNP0600
[0x0006d041]
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
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
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
PC-Card Vadem 469 (5 mem & 2 I/O windows)
pcic: controller irq 7
Initializing PC-card drivers: sio
Intel Pentium F00F detected, installing workaround
Waiting 15 seconds for SCSI devices to settle
changing root device to da1s2a
da1 at ahc0 bus 0 target 1 lun 0
da1: <QUANTUM FIREBALL ST6.4S 0F0C> Fixed Direct Access SCSI2 device
da1: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled
da1: 6180MB (12657717 512 byte sectors: 255H 63S/T 787C)
da0 at ahc0 bus 0 target 0 lun 0
da0: <QUANTUM FIREBALL_TM3200S 300X> Fixed Direct Access SCSI2 device
da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled
da0: 3067MB (6281856 512 byte sectors: 255H 63S/T 391C)
cd0 at ahc0 bus 0 target 5 lun 0
cd0: <SONY CD-ROM CDU-415 1.1i> Removable CD-ROM SCSI2 device
cd0: 10.0MB/s transfers (10.0MHz, offset 15)
cd0: Attempt to query device size failed: NOT READY, Medium not present
(da1:ahc0:0:1:0): tagged openings now 8
fxp0: promiscuous mode enabled
Anyone have some ideas for me?
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
*BSD & picoBSD: 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 Sun Nov 8 03:58:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA02436
for freebsd-current-outgoing; Sun, 8 Nov 1998 03:58:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02431
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 03:58:50 -0800 (PST)
(envelope-from root@swimsuit.internet.dk)
Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1])
by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id MAA01264;
Sun, 8 Nov 1998 12:58:27 +0100 (CET)
(envelope-from root@swimsuit.internet.dk)
Date: Sun, 8 Nov 1998 12:58:26 +0100 (CET)
From: Leif Neland <root@swimsuit.internet.dk>
To: Joel Ray Holveck <joelh@gnu.org>
cc: freebsd-current@FreeBSD.ORG
Subject: ext2fs_mod.o not found, was: How to make /dev/da0
In-Reply-To: <86n262rbjn.fsf@detlev.UUCP>
Message-ID: <Pine.BSF.4.05.9811081253400.1255-100000@gina.swimsuit.internet.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Still can't mount ext2fs:
> > I cant mount /dev/sd0s1 or /dev/da0s1
> > gina//dev $ mount_ext2fs /dev/sd0s1 /sd1
> > mount_ext2fs: vfsload(ext2fs): No such file or directory
>
> Now you've hit the proper problem: ext2fs (the Linux filesystem) isn't
> being loaded. That's where you need to look. Read up on vfsload(2)
> to see what it does, and how. Did you make world the same time you
> rebuilt your kernel? When did you rebuild your kernel?
I have a 2.2.7-RELEASE fresh from the distribution, and a 3.0 cvsupped and
rebuilt this night. Neither has a ext2fs_mod.o
I do have linux-emuation enabled in rc.conf
Leif
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 04:03:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA03579
for freebsd-current-outgoing; Sun, 8 Nov 1998 04:03:26 -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 EAA03574
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 04:03:24 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.59.121])
by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA569; Sun, 8 Nov 1998 13:03:08 +0100
Message-ID: <XFMail.981108130708.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.9811080026310.8500-100000@gina.swimsuit.internet.dk>
Date: Sun, 08 Nov 1998 13:07:08 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Leif Neland <root@swimsuit.internet.dk>
Subject: RE: How to make /dev/da0
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 07-Nov-98 Leif Neland wrote:
> ncr0: <ncr 53c810a fast10 scsi> rev 0x12 int a irq 10 on pci0.11.0
>
> da0 at ncr0 bus 0 target 6 lun 0
> da0: <IBM DCAS-34330 S60B> Fixed Direct Access SCSI2 device
> da0: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled
> da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
>
> But I don't have any /dev/da0*
>
> No MAKEDEV will make a dev0
>
> This have never heard of /dev/da0
> -r-xr-xr-x 1 root wheel 28634 22 Jul 10:16 /dev/MAKEDEV
> gina//dev $ /dev/MAKEDEV da0
> da0 - no such device name
Hejsa...
da0 is just the name Direct Access from the CAM layer... The Devices are still
named sdx
take a peek at /etc/fstab
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
*BSD & picoBSD: 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 Sun Nov 8 04:27:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA07158
for freebsd-current-outgoing; Sun, 8 Nov 1998 04:27:59 -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 EAA07153
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 04:27:58 -0800 (PST)
(envelope-from gjp@gjp.erols.com)
Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1])
by gjp.erols.com (8.9.1/8.8.7) with ESMTP id HAA22094;
Sun, 8 Nov 1998 07:26:18 -0500 (EST)
(envelope-from gjp@gjp.erols.com)
X-Mailer: exmh version 2.0.1 12/23/97
To: Leif Neland <root@swimsuit.internet.dk>
cc: Joel Ray Holveck <joelh@gnu.org>, freebsd-current@FreeBSD.ORG
From: "Gary Palmer" <gpalmer@FreeBSD.ORG>
Subject: Re: ext2fs_mod.o not found, was: How to make /dev/da0
In-reply-to: Your message of "Sun, 08 Nov 1998 12:58:26 +0100."
<Pine.BSF.4.05.9811081253400.1255-100000@gina.swimsuit.internet.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 08 Nov 1998 07:26:18 -0500
Message-ID: <22090.910527978@gjp.erols.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Leif Neland wrote in message ID
<Pine.BSF.4.05.9811081253400.1255-100000@gina.swimsuit.internet.dk>:
> Still can't mount ext2fs:
If memory serves, ext2fs can't be dynamically loaded, you have to recompile
your kernel and compile it in statically.
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 Sun Nov 8 04:42:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA08385
for freebsd-current-outgoing; Sun, 8 Nov 1998 04:42:59 -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 EAA08379
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 04:42:53 -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 WAA04514;
Sun, 8 Nov 1998 22:33:43 +1000 (EST)
(envelope-from akm)
From: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Message-Id: <199811081233.WAA04514@zeus.theinternet.com.au>
Subject: Re: How to make /dev/da0
In-Reply-To: <XFMail.981108130708.asmodai@wxs.nl> from Jeroen Ruigrok/Asmodai at "Nov 8, 98 01:07:08 pm"
To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai)
Date: Sun, 8 Nov 1998 22:33:43 +1000 (EST)
Cc: root@swimsuit.internet.dk, 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
+----[ Jeroen Ruigrok/Asmodai ]---------------------------------------------
| On 07-Nov-98 Leif Neland wrote:
| > ncr0: <ncr 53c810a fast10 scsi> rev 0x12 int a irq 10 on pci0.11.0
| >
| > da0 at ncr0 bus 0 target 6 lun 0
| > da0: <IBM DCAS-34330 S60B> Fixed Direct Access SCSI2 device
| > da0: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled
| > da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
| >
| > But I don't have any /dev/da0*
| >
| > No MAKEDEV will make a dev0
| >
| > This have never heard of /dev/da0
| > -r-xr-xr-x 1 root wheel 28634 22 Jul 10:16 /dev/MAKEDEV
| > gina//dev $ /dev/MAKEDEV da0
| > da0 - no such device name
|
| Hejsa...
|
| da0 is just the name Direct Access from the CAM layer... The Devices are still
| named sdx
|
| take a peek at /etc/fstab
# Device Mountpoint FStype Options Dump Pass#
/dev/da0s1b none swap sw 0 0
/dev/da0s1a / ufs rw 1 1
/dev/da2s1e /export ufs rw 2 2
/dev/da1s1e /home ufs rw 2 2
/dev/da0s1f /usr ufs rw 2 2
/dev/da0s1e /var ufs rw 2 2
brw-r----- 1 root operator 4, 0x00010002 Nov 2 18:55 /dev/da0
brw-r----- 1 root operator 4, 0 Nov 2 18:55 /dev/da0a
etc...
I'm guessing you didn't update your /dev after your installworld.
--
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 Sun Nov 8 04:53:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA09199
for freebsd-current-outgoing; Sun, 8 Nov 1998 04:53:12 -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 EAA09194
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 04:53:09 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.59.121])
by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA2154; Sun, 8 Nov 1998 13:52:51 +0100
Message-ID: <XFMail.981108135651.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: <199811081233.WAA04514@zeus.theinternet.com.au>
Date: Sun, 08 Nov 1998 13:56:51 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Subject: Re: How to make /dev/da0
Cc: freebsd-current@FreeBSD.ORG, root@swimsuit.internet.dk
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 08-Nov-98 Andrew Kenneth Milton wrote:
> +----[ Jeroen Ruigrok/Asmodai ]---------------------------------------------
>| take a peek at /etc/fstab
>
># Device Mountpoint FStype Options Dump Pass#
> /dev/da0s1b none swap sw 0 0
> /dev/da0s1a / ufs rw 1 1
> /dev/da2s1e /export ufs rw 2 2
> /dev/da1s1e /home ufs rw 2 2
> /dev/da0s1f /usr ufs rw 2 2
> /dev/da0s1e /var ufs rw 2 2
>
> brw-r----- 1 root operator 4, 0x00010002 Nov 2 18:55 /dev/da0
> brw-r----- 1 root operator 4, 0 Nov 2 18:55 /dev/da0a
>
> etc...
>
>
> I'm guessing you didn't update your /dev after your installworld.
OK, red head here ;)
Ignore my further attempts at helping =P
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
*BSD & picoBSD: 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 Sun Nov 8 05:09:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA10681
for freebsd-current-outgoing; Sun, 8 Nov 1998 05:09:54 -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 FAA10671
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 05:09:52 -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 OAA09170;
Sun, 8 Nov 1998 14:09:36 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id OAA17167;
Sun, 8 Nov 1998 14:09:35 +0100 (MET)
Message-ID: <19981108140935.06929@follo.net>
Date: Sun, 8 Nov 1998 14:09:35 +0100
From: Eivind Eklund <eivind@yes.no>
To: Russell Cattelan <cattelan@thebarn.com>, John Fieber <jfieber@indiana.edu>
Cc: "David E. Cross" <crossd@cs.rpi.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <Pine.SGI.4.05.9811061258001.810-100000@o2.cs.rpi.edu> <Pine.BSF.4.05.9811061348550.482-100000@fallout.campusview.indiana.edu> <13891.30546.555159.254752@lupo.thebarn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <13891.30546.555159.254752@lupo.thebarn.com>; from Russell Cattelan on Fri, Nov 06, 1998 at 04:28:07PM -0600
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Nov 06, 1998 at 04:28:07PM -0600, Russell Cattelan wrote:
> I've been complaining about this problem since January.
The 'dying daemons bug', not the 'inetd crashes/gives "junk pointer"
messages' bug?
Let's list the facts we have here:
* Problem first spotted in January
* Problem occur on my PPro box with the combinations
- 64MB RAM/128MB swap
- 64MB RAM/256 MB swap (much less frequently than with 128MB swap)
- 80MB RAM/256 MB swap (seems more frequent than with
64MB/256MB, but I have not recorded how it behaves, so I
can't really say)
I've got a PPro 200 (Origin = "GenuineIntel" Id = 0x617 Stepping=7)
* Problem occur on a P200MMX (Origin = "GenuineIntel" Id = 0x543 Stepping=3)
with 96MB RAM and 200MB swap
* Problem has never occured on a P133 (unknown stepping) with 24MB RAM
and 64MB swap.
* Problem occur with both IDE and a bunch of different SCSI cards
(thus it seems we can eliminate the disk system)
I know of three pieces of hardware I have that I've not yet gotten
confirmation that other doesn't have:
(1) AWE64 soundboard
(2) TV card
(3) Network card - a PCI ed (though I changed to this later than first
seeing the bugs, I think...)
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 05:46:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA12373
for freebsd-current-outgoing; Sun, 8 Nov 1998 05:46:45 -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 FAA12368
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 05:46:43 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id FAA24483;
Sun, 8 Nov 1998 05:39:27 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdD24481; Sun Nov 8 13:39:26 1998
Date: Sun, 8 Nov 1998 05:38:57 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Eivind Eklund <eivind@yes.no>
cc: Russell Cattelan <cattelan@thebarn.com>, John Fieber <jfieber@indiana.edu>,
"David E. Cross" <crossd@cs.rpi.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <19981108140935.06929@follo.net>
Message-ID: <Pine.BSF.3.95.981108053807.11891C-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
We've been having a problem with daemons dying with sig11 singe at least
mid 97 with 486DX100 boxen.
julian
On Sun, 8 Nov 1998, Eivind Eklund wrote:
> On Fri, Nov 06, 1998 at 04:28:07PM -0600, Russell Cattelan wrote:
> > I've been complaining about this problem since January.
>
> The 'dying daemons bug', not the 'inetd crashes/gives "junk pointer"
> messages' bug?
>
> Let's list the facts we have here:
> * Problem first spotted in January
>
> * Problem occur on my PPro box with the combinations
> - 64MB RAM/128MB swap
> - 64MB RAM/256 MB swap (much less frequently than with 128MB swap)
> - 80MB RAM/256 MB swap (seems more frequent than with
> 64MB/256MB, but I have not recorded how it behaves, so I
> can't really say)
> I've got a PPro 200 (Origin = "GenuineIntel" Id = 0x617 Stepping=7)
> * Problem occur on a P200MMX (Origin = "GenuineIntel" Id = 0x543 Stepping=3)
> with 96MB RAM and 200MB swap
> * Problem has never occured on a P133 (unknown stepping) with 24MB RAM
> and 64MB swap.
> * Problem occur with both IDE and a bunch of different SCSI cards
> (thus it seems we can eliminate the disk system)
>
> I know of three pieces of hardware I have that I've not yet gotten
> confirmation that other doesn't have:
> (1) AWE64 soundboard
> (2) TV card
> (3) Network card - a PCI ed (though I changed to this later than first
> seeing the bugs, I think...)
>
> Eivind.
>
> 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 Nov 8 06:01:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA13155
for freebsd-current-outgoing; Sun, 8 Nov 1998 06:01:36 -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 GAA13150
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 06:01:34 -0800 (PST)
(envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
by cheddar.netmonger.net (8.8.8/8.8.8) id JAA15480;
Sun, 8 Nov 1998 09:01:19 -0500 (EST)
Message-ID: <19981108090118.A15279@netmonger.net>
Date: Sun, 8 Nov 1998 09:01:18 -0500
From: Christopher Masto <chris@netmonger.net>
To: Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG
Subject: Re: Lock up on accessing sio?
References: <199811080455.PAA07388@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199811080455.PAA07388@godzilla.zeta.org.au>; from Bruce Evans on Sun, Nov 08, 1998 at 03:55:48PM +1100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 08, 1998 at 03:55:48PM +1100, Bruce Evans wrote:
> >sio0: configured irq 4 not in bitmap of probed irqs 0
> >sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
> >sio0: type 8250
>
> >The "configured irq 4 not in bitmap" line also appeared when booting
> >2.2.5.. I don't think it's significant.
>
> It's very significant, but can't appear in 2.2.5. It means that interrupts
> don't seem to be working. 2.2.5 would have failed the probe at this point.
Hmm.. well, it was 2.2.5-STABLE from some point, not the RELEASE
version. I'm pretty sure that I'd seeen that message before, but I
could be wrong. If it failed the probe, I wouldn't have had Hylafax
happily running on that machine. I have a backup of the working
system, so I guess I can find the date on the kernel and look at the
changes through the point where it stopped working. I suspect there
will be many..
--
Christopher Masto Director of Operations S NetMonger Communications
chris@netmonger.net info@netmonger.net SSS http://www.netmonger.net
\_/
Microsoft now is in 40 percent of American households. If they can
somehow insert themselves in as a piece of infrastructure in the next
generation of televisions, they could go to 100 percent penetration of
American households and eventually the world.
- BARRY RANDALL, Analyst, Dain Bosworth
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 06:13:58 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA14995
for freebsd-current-outgoing; Sun, 8 Nov 1998 06:13:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14988
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 06:13:55 -0800 (PST)
(envelope-from leifn@swimsuit.internet.dk)
Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1])
by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id PAA02361
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 15:13:35 +0100 (CET)
(envelope-from leifn@swimsuit.internet.dk)
Date: Sun, 8 Nov 1998 15:13:35 +0100 (CET)
From: Leif Neland <leifn@swimsuit.internet.dk>
To: freebsd-current@FreeBSD.ORG
Subject: EXT2FS should be in GENERIC
Message-ID: <Pine.BSF.4.05.9811081502170.2076-100000@gina.swimsuit.internet.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Now I have solved how to mount my ext2fs from /dev/da0s1 or /dev/sd0s1.
The reason hadn't anything to do with /dev/da*, it was because EXT2FS had
to be compiled into the kernel.
May I suggest EXT2FS is included in the GENERIC kernel? This would make it
easier enlightning those misguided souls running linux, when Freebsd out
of the box can read their disks.
Or at least the option should be at the top of the GENERIC config
alongside the other FS's like MSDOSFS and CD9660 (perhaps commented out)
instead of being hidden at the bottom of LINT under "More undocumented
options for linting"
Leif
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 06:23:08 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA15517
for freebsd-current-outgoing; Sun, 8 Nov 1998 06:23:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15512
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 06:23:07 -0800 (PST)
(envelope-from jfieber@fallout.campusview.indiana.edu)
Received: from localhost (jfieber@localhost)
by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id JAA18025;
Sun, 8 Nov 1998 09:22:50 -0500 (EST)
Date: Sun, 8 Nov 1998 09:22:50 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Eivind Eklund <eivind@yes.no>
cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <19981108140935.06929@follo.net>
Message-ID: <Pine.BSF.4.05.9811080909420.482-100000@fallout.campusview.indiana.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 Sun, 8 Nov 1998, Eivind Eklund wrote:
> * Problem first spotted in January
>
> * Problem occur on my PPro box with the combinations
> - 64MB RAM/128MB swap
> - 64MB RAM/256 MB swap (much less frequently than with 128MB swap)
> - 80MB RAM/256 MB swap (seems more frequent than with
> 64MB/256MB, but I have not recorded how it behaves, so I
> can't really say)
> I've got a PPro 200 (Origin = "GenuineIntel" Id = 0x617 Stepping=7)
> * Problem occur on a P200MMX (Origin = "GenuineIntel" Id = 0x543 Stepping=3)
> with 96MB RAM and 200MB swap
> * Problem has never occured on a P133 (unknown stepping) with 24MB RAM
> and 64MB swap.
> * Problem occur with both IDE and a bunch of different SCSI cards
> (thus it seems we can eliminate the disk system)
* AMD K6/200 (Origin = "AuthenticAMD" Id = 0x562 Stepping=2)
Generally, the problem appears as though it can be triggerd by,
or is associated with running low on or running out of swap.
One question: Is the problem "sticky"? By that I mean, if it is
triggered by a memomry shortage, is something in the kernel
corrupted that tends to kill/corrupt daemons from that point in
time on, or is it just something that affects isolated processes.
The symptom (junk pointer to low in ined's case) is obviously
triggered by some action of the process, but is the problem
itself triggered by an action of that same process?
Based on behavior of my system, my hunch is the first scenario
but I am definately not certain. I'll try and cook up some way
to test it but if anyone else has any ideas about it, that would
be great.
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 06:54:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA17922
for freebsd-current-outgoing; Sun, 8 Nov 1998 06:54:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17911
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 06:54:07 -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 BAA05823;
Mon, 9 Nov 1998 01:53:42 +1100
Date: Mon, 9 Nov 1998 01:53:42 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811081453.BAA05823@godzilla.zeta.org.au>
To: andreas@klemm.gtn.com, jb@cimlogic.com.au
Subject: Re: ELF interpreter /usr/libexec/ld-elf.so.1 not found, Abort trap
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> [...]
>> ELF interpreter /usr/libexec/ld-elf.so.1 not found
>> Abort trap
>> Manifying B::Terse.3
>[...]
>> ELF interpreter /usr/libexec/ld-elf.so.1 not found
>> Abort trap
>
>Last time I did one of these builds, I saw the same thing, but the
>upgrade didn't stop because of it. Something in the perl build needs
>to be built and installed as a build tool (these get built static).
The perl build installs a statically linked miniperl as perl, but
sometimes shoots itself in the foot by setting $PATH to a relative path.
It's a bug for the build to continue after an this error.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 07:09:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA19247
for freebsd-current-outgoing; Sun, 8 Nov 1998 07:09:50 -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 HAA19242
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 07:09:48 -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 QAA09976;
Sun, 8 Nov 1998 16:09:34 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id QAA17514;
Sun, 8 Nov 1998 16:09:34 +0100 (MET)
Message-ID: <19981108160934.30826@follo.net>
Date: Sun, 8 Nov 1998 16:09:34 +0100
From: Eivind Eklund <eivind@yes.no>
To: John Fieber <jfieber@indiana.edu>
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <19981108140935.06929@follo.net> <Pine.BSF.4.05.9811080909420.482-100000@fallout.campusview.indiana.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <Pine.BSF.4.05.9811080909420.482-100000@fallout.campusview.indiana.edu>; from John Fieber on Sun, Nov 08, 1998 at 09:22:50AM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 08, 1998 at 09:22:50AM -0500, John Fieber wrote:
> One question: Is the problem "sticky"? By that I mean, if it is
> triggered by a memomry shortage, is something in the kernel
> corrupted that tends to kill/corrupt daemons from that point in
> time on, or is it just something that affects isolated processes.
All daemons running at that point seems to get something corrupted.
If you restart the daemon, it won't happen again until you again run
out of memory (or whatever it is that trigger the corruption).
> The symptom (junk pointer to low in ined's case) is obviously
> triggered by some action of the process, but is the problem
> itself triggered by an action of that same process?
The 'junk pointer too low to make sense' seems to be a different
problem, caused by race conditions in the signal handlers of inetd.
There is a patch fixing this in a PR; however, David has said that
this is not the 'right fix', so it has not been committed.
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 07:10:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA19365
for freebsd-current-outgoing; Sun, 8 Nov 1998 07:10:59 -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 HAA19356
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 07:10:55 -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 QAA10002;
Sun, 8 Nov 1998 16:10:39 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id QAA17550;
Sun, 8 Nov 1998 16:10:38 +0100 (MET)
Message-ID: <19981108161038.42967@follo.net>
Date: Sun, 8 Nov 1998 16:10:38 +0100
From: Eivind Eklund <eivind@yes.no>
To: Julian Elischer <julian@whistle.com>
Cc: John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <19981108140935.06929@follo.net> <Pine.BSF.3.95.981108053807.11891C-100000@current1.whistle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <Pine.BSF.3.95.981108053807.11891C-100000@current1.whistle.com>; from Julian Elischer on Sun, Nov 08, 1998 at 05:38:57AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 08, 1998 at 05:38:57AM -0800, Julian Elischer wrote:
> We've been having a problem with daemons dying with sig11 singe at least
> mid 97 with 486DX100 boxen.
Can you give more details? Which NIC, and is there anything that use
PCI busmastering DMA or contigmalloc() in action here?
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 07:16:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA19723
for freebsd-current-outgoing; Sun, 8 Nov 1998 07:16:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from root.com (implode.root.com [198.145.90.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19712
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 07:16:04 -0800 (PST)
(envelope-from xroot@root.com)
Received: from implode.root.com (localhost [127.0.0.1])
by root.com (8.8.5/8.8.5) with ESMTP id HAA03267;
Sun, 8 Nov 1998 07:17:12 -0800 (PST)
Message-Id: <199811081517.HAA03267@root.com>
To: Eivind Eklund <eivind@yes.no>
cc: John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-reply-to: Your message of "Sun, 08 Nov 1998 16:09:34 +0100."
<19981108160934.30826@follo.net>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sun, 08 Nov 1998 07:17:11 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>On Sun, Nov 08, 1998 at 09:22:50AM -0500, John Fieber wrote:
>> One question: Is the problem "sticky"? By that I mean, if it is
>> triggered by a memomry shortage, is something in the kernel
>> corrupted that tends to kill/corrupt daemons from that point in
>> time on, or is it just something that affects isolated processes.
>
>All daemons running at that point seems to get something corrupted.
>If you restart the daemon, it won't happen again until you again run
>out of memory (or whatever it is that trigger the corruption).
brk(2) will fail and return ENOMEM if the system is low on swap space. If
the application (phk malloc or the caller of malloc?) isn't prepared for this,
it may end up with a NULL pointer that it doesn't expect - perhaps not even
tripping over it until sometime later.
-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 Sun Nov 8 07:41:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA21686
for freebsd-current-outgoing; Sun, 8 Nov 1998 07:41:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21681
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 07:41:41 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id KAA21232;
Sun, 8 Nov 1998 10:44:24 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Sun, 8 Nov 1998 10:44:24 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: "David E. Cross" <crossd@phoenix.cs.rpi.edu>
cc: current@FreeBSD.ORG
Subject: Re: O_SYNC
In-Reply-To: <199811072154.QAA00324@phoenix.cs.rpi.edu>
Message-ID: <Pine.BSF.4.05.9811081043010.19817-100000@porkfriedrice.ny.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
Yes, however every other OS defines it at "O_SYNC" why are we different?
or, if there is a reason, why isn't there a compatibility #define?
can someone check this on netbsd/open bsd/os ? is it bsd or us?
Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com
-- There are operating systems, and then there's FreeBSD.
-- http://www.freebsd.org/ 3.0-current
On Sat, 7 Nov 1998, David E. Cross wrote:
> Is 'O_FSYNC" what you are looking for?
>
> #define O_FSYNC 0x0080 /* synchronous writes */
>
>
> --
> David Cross
>
> 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 Nov 8 07:50:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA22043
for freebsd-current-outgoing; Sun, 8 Nov 1998 07:50:52 -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 HAA22038
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 07:50:50 -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 QAA10344;
Sun, 8 Nov 1998 16:50:24 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id QAA04915;
Sun, 8 Nov 1998 16:50:24 +0100 (MET)
Message-ID: <19981108165023.60036@follo.net>
Date: Sun, 8 Nov 1998 16:50:23 +0100
From: Eivind Eklund <eivind@yes.no>
To: dg@root.com
Cc: John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <19981108160934.30826@follo.net> <199811081517.HAA03267@root.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <199811081517.HAA03267@root.com>; from David Greenman on Sun, Nov 08, 1998 at 07:17:11AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 08, 1998 at 07:17:11AM -0800, David Greenman wrote:
> >On Sun, Nov 08, 1998 at 09:22:50AM -0500, John Fieber wrote:
> >> One question: Is the problem "sticky"? By that I mean, if it is
> >> triggered by a memomry shortage, is something in the kernel
> >> corrupted that tends to kill/corrupt daemons from that point in
> >> time on, or is it just something that affects isolated processes.
> >
> >All daemons running at that point seems to get something corrupted.
> >If you restart the daemon, it won't happen again until you again run
> >out of memory (or whatever it is that trigger the corruption).
>
> brk(2) will fail and return ENOMEM if the system is low on swap space.
phkmalloc() checks for this.
Anyway; why does it do this? It does not look like it actually needs
to do this, and if we do a memory overcommit, it seems to me that we
could do it all the way (or at least have a sysctl to make it do it
all the way). I'm also sorely missing a sysctl to turn off memory
overcommit... (I don't know the VM system well enough to implement it
myself, and I feel very uncomfortable with doing changes in it.)
> If the application (phk malloc or the caller of malloc?) isn't
> prepared for this, it may end up with a NULL pointer that it doesn't
> expect - perhaps not even tripping over it until sometime later.
I'm pretty sure this is not the problem. Inactive daemons seems start
dying, and I don't always get the "out of swap space" message that
comes with setting swap_pager_full.
The symptoms are that when the daemon fork after a 'daemons dying
occurrance', they will immediately get a sig11 on the child fork.
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 08:00:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA22632
for freebsd-current-outgoing; Sun, 8 Nov 1998 08:00:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from detlev.UUCP (tex-84.camalott.com [208.229.74.84])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22622;
Sun, 8 Nov 1998 08:00:23 -0800 (PST)
(envelope-from joelh@gnu.org)
Received: (from joelh@localhost)
by detlev.UUCP (8.9.1/8.9.1) id JAA11509;
Sun, 8 Nov 1998 09:59:53 -0600 (CST)
(envelope-from joelh)
To: "Gary Palmer" <gpalmer@FreeBSD.ORG>
Cc: Leif Neland <root@swimsuit.internet.dk>, freebsd-current@FreeBSD.ORG
Subject: Re: ext2fs_mod.o not found, was: How to make /dev/da0
References: <22090.910527978@gjp.erols.com>
From: Joel Ray Holveck <joelh@gnu.org>
Date: 08 Nov 1998 09:59:52 -0600
In-Reply-To: "Gary Palmer"'s message of "Sun, 08 Nov 1998 07:26:18 -0500"
Message-ID: <86d86yw4xz.fsf@detlev.UUCP>
Lines: 12
X-Mailer: Gnus v5.5/Emacs 20.3
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> Still can't mount ext2fs:
> If memory serves, ext2fs can't be dynamically loaded, you have to recompile
> your kernel and compile it in statically.
What is the status on ext2fs? It's listed in the "undocumented"
section of LINT right now; is it being maintained or anything?
--
Joel Ray Holveck - joelh@gnu.org
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 08:10:25 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA23386
for freebsd-current-outgoing; Sun, 8 Nov 1998 08:10:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23376;
Sun, 8 Nov 1998 08:10:22 -0800 (PST)
(envelope-from dmm125@bellatlantic.net)
Received: from client201-122-14.bellatlantic.net (client201-122-14.bellatlantic.net [151.201.122.14])
by iconmail.bellatlantic.net (IConNet Sendmail) with ESMTP id LAA26093;
Sun, 8 Nov 1998 11:06:36 -0500 (EST)
Newsgroups: comp.unix.bsd.freebsd.misc
Date: Sun, 8 Nov 1998 11:05:27 +0000 (GMT)
From: Donn Miller <dmm125@bellatlantic.net>
X-Sender: dmm125@localhost
To: ports@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Ports/patches for X332servonly
Message-ID: <Pine.BSF.4.05.9811081054100.424-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Just trying to find out if anyone did a port and/or patch for
X332servonly.tgz. It's like the full source for XFree86 but it doesn't
include the stuff for building shared libs. I need the source code so I
can modify it to make a driver for my chipset, which is unsupported.
BTW, building XFree86 from sratch is pretty nasty. One minor change to
any of the config files in xc/config/cf sometimes throws the whole build
out of whack.
The shared/static libs build OK, but when it comes time to link all the
object files and libs together to produce the X-server, massive amounts of
errors about "undefined reference to ..." come pouring out like crazy.
This is in the subdir xc/programs/Xserver/hw...
I tried building it w/out changing any source at first, just to see if it
would compile, and it won't compile. So anyone successfully built the
XFree86 servers from source on 3.0-R?
Thanks for any help you can provide,
Donn
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 08:11:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA23733
for freebsd-current-outgoing; Sun, 8 Nov 1998 08:11:03 -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 IAA23719
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 08:10:58 -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 RAA16652;
Sun, 8 Nov 1998 17:07:12 +0100 (CET)
To: dg@root.com
cc: Eivind Eklund <eivind@yes.no>, John Fieber <jfieber@indiana.edu>,
current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-reply-to: Your message of "Sun, 08 Nov 1998 07:17:11 PST."
<199811081517.HAA03267@root.com>
Date: Sun, 08 Nov 1998 17:07:12 +0100
Message-ID: <16650.910541232@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 <199811081517.HAA03267@root.com>, David Greenman writes:
>>On Sun, Nov 08, 1998 at 09:22:50AM -0500, John Fieber wrote:
>>> One question: Is the problem "sticky"? By that I mean, if it is
>>> triggered by a memomry shortage, is something in the kernel
>>> corrupted that tends to kill/corrupt daemons from that point in
>>> time on, or is it just something that affects isolated processes.
>>
>>All daemons running at that point seems to get something corrupted.
>>If you restart the daemon, it won't happen again until you again run
>>out of memory (or whatever it is that trigger the corruption).
>
> brk(2) will fail and return ENOMEM if the system is low on swap space. If
>the application (phk malloc or the caller of malloc?) isn't prepared for this,
>it may end up with a NULL pointer that it doesn't expect - perhaps not even
>tripping over it until sometime later.
This would be (semi-)easy to check for:
ln -s A /etc/malloc.conf
will make malloc call abort() rather than return a NULL pointer.
Trouble is that fd#2 from daemons isn't always available for barfing
into for malloc [*]
Poul-Henning
[*] I've often wished that we had a syslog(2), ie system call,
which didn't require you to go through all the open/bind/send/
gyrations. Come to think of it, I son't see any reason apart
from the ideological aspect for not having that. It would
improve the reliability and security of syslog a fair bit.
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 08:13:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA23982
for freebsd-current-outgoing; Sun, 8 Nov 1998 08:13:50 -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 IAA23977
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 08:13:48 -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 RAA10606;
Sun, 8 Nov 1998 17:13:19 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id RAA05017;
Sun, 8 Nov 1998 17:13:19 +0100 (MET)
Message-ID: <19981108171319.19261@follo.net>
Date: Sun, 8 Nov 1998 17:13:19 +0100
From: Eivind Eklund <eivind@yes.no>
To: dg@root.com
Cc: John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <19981108160934.30826@follo.net> <199811081517.HAA03267@root.com> <19981108165023.60036@follo.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <19981108165023.60036@follo.net>; from Eivind Eklund on Sun, Nov 08, 1998 at 04:50:23PM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 08, 1998 at 04:50:23PM +0100, Eivind Eklund wrote:
> On Sun, Nov 08, 1998 at 07:17:11AM -0800, David Greenman wrote:
> > If the application (phk malloc or the caller of malloc?) isn't
> > prepared for this, it may end up with a NULL pointer that it doesn't
> > expect - perhaps not even tripping over it until sometime later.
>
> I'm pretty sure this is not the problem. Inactive daemons seems start
> dying, and I don't always get the "out of swap space" message that
> comes with setting swap_pager_full.
Oh, and another aspect: This suddenly started happening. It has been
stable for 3/4 of a year, and then suddenly started happening
reproducably one day, after a kernel update while John was doing his
changes.
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 08:25:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA24513
for freebsd-current-outgoing; Sun, 8 Nov 1998 08:25:56 -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 IAA24507
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 08:25:53 -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.1/8.9.1/Spinner) with ESMTP id AAA24983;
Mon, 9 Nov 1998 00:18:35 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811081618.AAA24983@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: dg@root.com, Eivind Eklund <eivind@yes.no>,
John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-reply-to: Your message of "Sun, 08 Nov 1998 17:07:12 +0100."
<16650.910541232@critter.freebsd.dk>
Date: Mon, 09 Nov 1998 00:18:34 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Poul-Henning Kamp wrote:
> [*] I've often wished that we had a syslog(2), ie system call,
> which didn't require you to go through all the open/bind/send/
> gyrations. Come to think of it, I son't see any reason apart
> from the ideological aspect for not having that. It would
> improve the reliability and security of syslog a fair bit.
As long as it's called something like __syslog(), and the sprintf style
expansion is done in user mode. openlog() takes an ident string.. To get
"better" syslog security, for non-root processes, this could be ignored and
the p_comm of the process used, and the pid forced on..
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 Nov 8 08:50:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA26731
for freebsd-current-outgoing; Sun, 8 Nov 1998 08:50: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 IAA26723
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 08:50: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 LAA04708;
Sun, 8 Nov 1998 11:45:50 -0500 (EST)
Date: Sun, 8 Nov 1998 11:45:50 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Eivind Eklund <eivind@yes.no>
cc: dg@root.com, John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <19981108165023.60036@follo.net>
Message-ID: <Pine.BSF.4.05.9811081144340.4580-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
Is it just me or has noone actually captured the corefiles, compiled
whatever died -g, and tried to debug exactly what caused the sig11? Not
the underlying cause, just the "actual" cause (like a certain register
being a wrong value).
Cheers,
Brian Feldman
On Sun, 8 Nov 1998, Eivind Eklund wrote:
> On Sun, Nov 08, 1998 at 07:17:11AM -0800, David Greenman wrote:
> > >On Sun, Nov 08, 1998 at 09:22:50AM -0500, John Fieber wrote:
> > >> One question: Is the problem "sticky"? By that I mean, if it is
> > >> triggered by a memomry shortage, is something in the kernel
> > >> corrupted that tends to kill/corrupt daemons from that point in
> > >> time on, or is it just something that affects isolated processes.
> > >
> > >All daemons running at that point seems to get something corrupted.
> > >If you restart the daemon, it won't happen again until you again run
> > >out of memory (or whatever it is that trigger the corruption).
> >
> > brk(2) will fail and return ENOMEM if the system is low on swap space.
>
> phkmalloc() checks for this.
>
> Anyway; why does it do this? It does not look like it actually needs
> to do this, and if we do a memory overcommit, it seems to me that we
> could do it all the way (or at least have a sysctl to make it do it
> all the way). I'm also sorely missing a sysctl to turn off memory
> overcommit... (I don't know the VM system well enough to implement it
> myself, and I feel very uncomfortable with doing changes in it.)
>
> > If the application (phk malloc or the caller of malloc?) isn't
> > prepared for this, it may end up with a NULL pointer that it doesn't
> > expect - perhaps not even tripping over it until sometime later.
>
> I'm pretty sure this is not the problem. Inactive daemons seems start
> dying, and I don't always get the "out of swap space" message that
> comes with setting swap_pager_full.
>
> The symptoms are that when the daemon fork after a 'daemons dying
> occurrance', they will immediately get a sig11 on the child fork.
>
> Eivind.
>
> 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 Nov 8 09:59:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA02636
for freebsd-current-outgoing; Sun, 8 Nov 1998 09:59:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lupo.thebarn.com (lupo.lcse.umn.edu [128.101.182.105])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02624
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 09:59:29 -0800 (PST)
(envelope-from cattelan@lupo.thebarn.com)
Received: (from cattelan@localhost)
by lupo.thebarn.com (8.9.1/8.9.1) id LAA29080;
Sun, 8 Nov 1998 11:58:39 -0600 (CST)
Message-Id: <199811081758.LAA29080@lupo.thebarn.com>
From: Russell Cattelan <cattelan@thebarn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sun, 8 Nov 1998 11:58:38 -0600 (CST)
To: current@FreeBSD.ORG
Cc: "Eivind Eklund <eivind@yes.no>
John Fieber" <jfieber@indiana.edu>,
"David E. Cross" <crossd@cs.rpi.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <19981108140935.06929@follo.net>
References: <Pine.SGI.4.05.9811061258001.810-100000@o2.cs.rpi.edu>
<Pine.BSF.4.05.9811061348550.482-100000@fallout.campusview.indiana.edu>
<13891.30546.555159.254752@lupo.thebarn.com>
<19981108140935.06929@follo.net>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <13893.55958.378493.589621@lupo.thebarn.com>
FCC: ~/Mail/sent
I went back and checked my outgoing mail archives, I didn't find any
messages from january but I did find this one from April.
Is this similar to what other people are seeing?
From: Russell Cattelan <cattelan@thebarn.com>
To: freebsd-current@freebsd.org
Subject: VM scrambling pages if space is exceeded
Date: Sun, 19 Apr 98 12:36:09 CDT
This problem has been cropping up with "current" for about the
last month. The basic problem shows up with daemon processes
coreing sortly after swap space is maxed out.
The most common programs: cron, sendmail and recently socks5.
The main process keep running but every time it goes to
fork a copy, the copy dies.
I am running -current (as of Apr 14), built from scratch.
Apr 19 12:03:43 lupo /kernel: swap_pager: suggest more swap space: 124 MB
Apr 19 12:10:03 lupo /kernel: pid 15046 (cron), uid 0: exited on signal 11
Apr 19 12:14:27 lupo /kernel: pid 15057 (socks5), uid 0: exited on signal 11
Apr 19 12:14:50 lupo /kernel: pid 15059 (socks5), uid 0: exited on signal 11
I wasn't sure if I had bad bits at some point but I have two systems
exhibiting the same behavior.
--
Russell Cattelan
Eivind Eklund writes:
> On Fri, Nov 06, 1998 at 04:28:07PM -0600, Russell Cattelan wrote:
> > I've been complaining about this problem since January.
>
> The 'dying daemons bug', not the 'inetd crashes/gives "junk pointer"
> messages' bug?
>
> Let's list the facts we have here:
> * Problem first spotted in January
>
> * Problem occur on my PPro box with the combinations
> - 64MB RAM/128MB swap
> - 64MB RAM/256 MB swap (much less frequently than with 128MB swap)
> - 80MB RAM/256 MB swap (seems more frequent than with
> 64MB/256MB, but I have not recorded how it behaves, so I
> can't really say)
> I've got a PPro 200 (Origin = "GenuineIntel" Id = 0x617 Stepping=7)
> * Problem occur on a P200MMX (Origin = "GenuineIntel" Id = 0x543 Stepping=3)
> with 96MB RAM and 200MB swap
> * Problem has never occured on a P133 (unknown stepping) with 24MB RAM
> and 64MB swap.
> * Problem occur with both IDE and a bunch of different SCSI cards
> (thus it seems we can eliminate the disk system)
>
> I know of three pieces of hardware I have that I've not yet gotten
> confirmation that other doesn't have:
> (1) AWE64 soundboard
> (2) TV card
> (3) Network card - a PCI ed (though I changed to this later than first
> seeing the bugs, I think...)
>
> Eivind.
>
--
Russell Cattelan
cattelan@thebarn.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 10:43:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA06858
for freebsd-current-outgoing; Sun, 8 Nov 1998 10:43:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06852
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 10:43:19 -0800 (PST)
(envelope-from son@teaser.fr)
Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40])
by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id TAA08358;
Sun, 8 Nov 1998 19:42:49 +0100 (MET)
Received: (from son@localhost)
by teaser.fr (8.9.1/8.8.5) id UAA01908;
Sun, 8 Nov 1998 20:16:14 GMT
Message-ID: <19981108201614.45459@breizh.prism.uvsq.fr>
Date: Sun, 8 Nov 1998 20:16:14 +0000
From: Nicolas Souchu <nsouch@teaser.fr>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Cc: FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: ZIP, again
References: <XFMail.981108122153.asmodai@wxs.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81e
In-Reply-To: <XFMail.981108122153.asmodai@wxs.nl>; from Jeroen Ruigrok/Asmodai on Sun, Nov 08, 1998 at 12:21:53PM +0100
X-Operating-System: FreeBSD breizh 3.0-BETA FreeBSD 3.0-BETA
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 08, 1998 at 12:21:53PM +0100, Jeroen Ruigrok/Asmodai wrote:
>
>Well since the archives for current are dead, I am forced to ask again on the
>list...
>
>I have a ZIP+ Drive on my parallel port that I want to use... Last time I asked
>I was using a SNAP 3.0 but I am now fully CURRENT (as far as can be) and am
>giving it a shot again.
>
>controller ppbus0
>controller vpo0 at ppbus?
>device nlpt0 at ppbus?
>device ppi0 at ppbus?
>
>controller ppc0 at isa? disable port ? tty irq 7
^^^^^^^
You're joking?
>
>This is right afaik... Yet when I reboot I get this:
>
--
nsouch@teaser.fr / nsouch@freebsd.org
FreeBSD - Turning PCs into workstations - 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 Nov 8 10:52:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA07461
for freebsd-current-outgoing; Sun, 8 Nov 1998 10:52:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07097
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 10:47:08 -0800 (PST)
(envelope-from dima@tejblum.dnttm.rssi.ru)
Received: (from uucp@localhost)
by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id VAA25379;
Sun, 8 Nov 1998 21:06:36 +0300
Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1])
by tejblum.dnttm.rssi.ru (8.9.1/8.9.1) with ESMTP id VAA00888;
Sun, 8 Nov 1998 21:06:30 +0300 (MSK)
(envelope-from dima@tejblum.dnttm.rssi.ru)
Message-Id: <199811081806.VAA00888@tejblum.dnttm.rssi.ru>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Eivind Eklund <eivind@yes.no>
cc: dg@root.com, John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-reply-to: Your message of "Sun, 08 Nov 1998 17:13:19 +0100."
<19981108171319.19261@follo.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 08 Nov 1998 21:06:29 +0300
From: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Eivind Eklund wrote:
>
> Oh, and another aspect: This suddenly started happening. It has been
> stable for 3/4 of a year, and then suddenly started happening
> reproducably one day, after a kernel update while John was doing his
> changes.
Please don't tell anyone, but I am almost convinced that the bug is
here:
-----swap_pager.c, line 1132------
/*
* If we're out of swap space, then attempt to free
* some whenever multiple pages are brought in. We
* must set the dirty bits so that the page contents
* will be preserved.
*/
if (SWAPLOW ||
(vm_swap_size < btodb((cnt.v_page_count - cnt.v_wire_count)) * PAGE_SIZE)) {
for (i = 0; i < count; i++) {
m[i]->dirty = VM_PAGE_BITS_ALL;
}
swap_pager_freespace(object,
m[0]->pindex + paging_offset, count);
}
------------------------------------
If I sysctl out the call to swap_pager_freespace, all symptoms
disappear. This code activates at about the time when the "suggest more
swap space" message printed. IIRC, it was introduced by John Dyson this
winter.
(Perhaps, the code just triggers a bug elsewhere... No idea what is
wrong).
Dima
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 10:52:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA07508
for freebsd-current-outgoing; Sun, 8 Nov 1998 10:52:59 -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 KAA07503
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 10:52:56 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.59.13]) by smtp02.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAA1B2A;
Sun, 8 Nov 1998 19:52:41 +0100
Message-ID: <XFMail.981108195642.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: <19981108201614.45459@breizh.prism.uvsq.fr>
Date: Sun, 08 Nov 1998 19:56:42 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Nicolas Souchu <nsouch@teaser.fr>
Subject: Re: ZIP, again
Cc: FreeBSD Current <current@FreeBSD.ORG>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 08-Nov-98 Nicolas Souchu wrote:
> On Sun, Nov 08, 1998 at 12:21:53PM +0100, Jeroen Ruigrok/Asmodai wrote:
> You're joking?
Nah,, just blind as a bat...
btw, the detection is ok right now...
Forget all about my posts..
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl | Cum angelis et pueris,
Junior Network/Security Specialist | fideles inveniamur
*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 Nov 8 10:53:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA07551
for freebsd-current-outgoing; Sun, 8 Nov 1998 10:53:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.dyn.ml.org (sf3-56.ppp.wenet.net [206.15.84.56])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07546
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 10:53:50 -0800 (PST)
(envelope-from garbanzo@hooked.net)
Received: from localhost (garbanzo@localhost)
by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id KAA21837;
Sun, 8 Nov 1998 10:57:04 -0800 (PST)
(envelope-from garbanzo@hooked.net)
X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs
Date: Sun, 8 Nov 1998 10:57:03 -0800 (PST)
From: Alex Zepeda <garbanzo@hooked.net>
X-Sender: garbanzo@zippy.dyn.ml.org
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: ZIP, again
In-Reply-To: <XFMail.981108122153.asmodai@wxs.nl>
Message-ID: <Pine.BSF.4.05.9811081056260.21356-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 Sun, 8 Nov 1998, Jeroen Ruigrok/Asmodai wrote:
[..]
> controller ppbus0
> controller vpo0 at ppbus?
> device nlpt0 at ppbus?
> device ppi0 at ppbus?
>
> controller ppc0 at isa? disable port ? tty irq 7
^^^^^^^
Have you tried removing the disable keyword?
> Anyone have some ideas for me?
- 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 Sun Nov 8 11:16:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA09564
for freebsd-current-outgoing; Sun, 8 Nov 1998 11:16:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rgate2.ricochet.net (rgate2.ricochet.net [204.179.143.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09526
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 11:15:56 -0800 (PST)
(envelope-from enkhyl@scient.com)
Received: from mg130-168.ricochet.net (mg130-168.ricochet.net [204.179.130.168])
by rgate2.ricochet.net (8.8.8/8.8.8) with ESMTP id NAA05047;
Sun, 8 Nov 1998 13:15:06 -0600 (CST)
Date: Sun, 8 Nov 1998 11:13:10 -0800 (PST)
From: Christopher Nielsen <enkhyl@scient.com>
X-Sender: enkhyl@ender.sf.scient.com
Reply-To: enkhyl@hayseed.net
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: ZIP, again
In-Reply-To: <XFMail.981108122153.asmodai@wxs.nl>
Message-ID: <Pine.BSF.4.05.9811081110350.1149-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 Sun, 8 Nov 1998, Jeroen Ruigrok/Asmodai wrote:
> I have a ZIP+ Drive on my parallel port that I want to use... Last time I asked
> I was using a SNAP 3.0 but I am now fully CURRENT (as far as can be) and am
> giving it a shot again.
>
> controller ppbus0
> controller vpo0 at ppbus?
> device nlpt0 at ppbus?
> device ppi0 at ppbus?
>
> controller ppc0 at isa? disable port ? tty irq 7
^^^^^^^
|
You can start by removing this ------+
I don't know if that will definitely fix your problem, but having it there
will keep it from working.
--
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 Sun Nov 8 11:25:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA10703
for freebsd-current-outgoing; Sun, 8 Nov 1998 11:25:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from root.com (implode.root.com [198.145.90.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10695
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 11:25:44 -0800 (PST)
(envelope-from xroot@root.com)
Received: from implode.root.com (localhost [127.0.0.1])
by root.com (8.8.5/8.8.5) with ESMTP id LAA06586;
Sun, 8 Nov 1998 11:24:08 -0800 (PST)
Message-Id: <199811081924.LAA06586@root.com>
To: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
cc: Eivind Eklund <eivind@yes.no>, John Fieber <jfieber@indiana.edu>,
current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-reply-to: Your message of "Sun, 08 Nov 1998 21:06:29 +0300."
<199811081806.VAA00888@tejblum.dnttm.rssi.ru>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sun, 08 Nov 1998 11:24:08 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>Eivind Eklund wrote:
>>
>> Oh, and another aspect: This suddenly started happening. It has been
>> stable for 3/4 of a year, and then suddenly started happening
>> reproducably one day, after a kernel update while John was doing his
>> changes.
>
>Please don't tell anyone, but I am almost convinced that the bug is
>here:
>
>-----swap_pager.c, line 1132------
> /*
> * If we're out of swap space, then attempt to free
> * some whenever multiple pages are brought in. We
> * must set the dirty bits so that the page contents
> * will be preserved.
> */
> if (SWAPLOW ||
> (vm_swap_size < btodb((cnt.v_page_count - cnt.v_wire_count)) * PAGE_SIZE)) {
> for (i = 0; i < count; i++) {
> m[i]->dirty = VM_PAGE_BITS_ALL;
> }
> swap_pager_freespace(object,
> m[0]->pindex + paging_offset, count);
> }
>------------------------------------
>If I sysctl out the call to swap_pager_freespace, all symptoms
>disappear. This code activates at about the time when the "suggest more
>swap space" message printed. IIRC, it was introduced by John Dyson this
>winter.
>
>(Perhaps, the code just triggers a bug elsewhere... No idea what is
>wrong).
I don't see anything wrong with it, but if it is the cause of the
problem, it can safely be removed. I'd suggest that people #if 0 out
the code and see if the problem completely vanishes.
-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 Sun Nov 8 11:39:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA12152
for freebsd-current-outgoing; Sun, 8 Nov 1998 11:39:32 -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 LAA12147
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 11:39:27 -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 UAA11970;
Sun, 8 Nov 1998 20:29:23 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id UAA06890;
Sun, 8 Nov 1998 20:29:23 +0100 (MET)
Message-ID: <19981108202820.49780@follo.net>
Date: Sun, 8 Nov 1998 20:28:20 +0100
From: Eivind Eklund <eivind@yes.no>
To: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
Cc: dg@root.com, John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <19981108171319.19261@follo.net> <199811081806.VAA00888@tejblum.dnttm.rssi.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <199811081806.VAA00888@tejblum.dnttm.rssi.ru>; from Dmitrij Tejblum on Sun, Nov 08, 1998 at 09:06:29PM +0300
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 08, 1998 at 09:06:29PM +0300, Dmitrij Tejblum wrote:
> Eivind Eklund wrote:
> >
> > Oh, and another aspect: This suddenly started happening. It has been
> > stable for 3/4 of a year, and then suddenly started happening
> > reproducably one day, after a kernel update while John was doing his
> > changes.
>
> Please don't tell anyone, but I am almost convinced that the bug is
> here:
>
> -----swap_pager.c, line 1132------
> /*
> * If we're out of swap space, then attempt to free
> * some whenever multiple pages are brought in. We
> * must set the dirty bits so that the page contents
> * will be preserved.
> */
> if (SWAPLOW ||
> (vm_swap_size < btodb((cnt.v_page_count - cnt.v_wire_count)) * PAGE_SIZE)) {
> for (i = 0; i < count; i++) {
> m[i]->dirty = VM_PAGE_BITS_ALL;
> }
> swap_pager_freespace(object,
> m[0]->pindex + paging_offset, count);
> }
> ------------------------------------
> If I sysctl out the call to swap_pager_freespace, all symptoms
> disappear. This code activates at about the time when the "suggest more
> swap space" message printed. IIRC, it was introduced by John Dyson this
> winter.
>
> (Perhaps, the code just triggers a bug elsewhere... No idea what is
> wrong).
This code is pretty old, but the context for it was changed in
revision 1.89 of vm_swap_pager.c on the 23rd of february. It match
the time pretty well.
revision 1.89
date: 1998/02/23 08:22:24; author: dyson; state: Exp; lines: +273 -285
Significantly improve the efficiency of the swap pager, which appears to
have declined due to code-rot over time. The swap pager rundown code
has been clean-up, and unneeded wakeups removed. Lots of splbio's
are changed to splvm's. Also, set the dynamic tunables for the
pageout daemon to be more sane for larger systems (thereby decreasing
the daemon overheadla.)
I'm not able to fully wrap my head around the code in question - it
seems like there are interactions with lots of other parts. It looks
as if there might a problem with the removal of the use of of the
swap_pager_free TAILQ in swap_pager_getpages, but I don't understand
why this would cause a problem, and I'm not sure which other changes
are related to this, so I can't easily just back that part out.
If anybody else is going to look at it, I found the best way to get an
overview given the type of changes is with
cvs diff -c -w -r1.88 -r1.89 /sys/vm/swap_pager.c | $PAGER
in one window, and
$PAGER /sys/vm/swap_pager.c
in another. If you don't drop whitespace changes, it is close to
impossible to read (given that some things have changed their
indentation level). For once, context diffs were also better than
unified diffs.
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 11:44:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA12685
for freebsd-current-outgoing; Sun, 8 Nov 1998 11:44:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12658
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 11:44:24 -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 LAA03204;
Sun, 8 Nov 1998 11:43:16 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811081943.LAA03204@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>
cc: current@FreeBSD.ORG
Subject: Re: meaning of "file: table is full" kernel log messages?
In-reply-to: Your message of "Sat, 07 Nov 1998 13:20:50 PST."
<Pine.BSF.4.02A.9811071314400.1428-100000@smarter.than.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 08 Nov 1998 11:43:15 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> My daily security check email noted some kernel log entries that I didn't
> recognize:
>
> smarter kernel log messages:
> > file: table is full
> <message repeats MANY times>
You probably want to rebuild your kernel with maxusers set much higher
(what's it currently set to - 10?)
> Checking dmesg, I noted that the next message indicated that a process
> segfaulted, but as there's no date stamps, I don't know if it happened
> immediately afterward.
That'll be in the messages file as well.
> I'm running -CURRENT with the kernel built Oct 13 (I'd be more current,
> but the new bootloader causes my machine to lock up... any fix for this
> yet?)
No idea; what's the problem?
--
\\ 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 Nov 8 12:00:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA14415
for freebsd-current-outgoing; Sun, 8 Nov 1998 12:00:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ifi.uio.no (ifi.uio.no [129.240.64.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14410
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 12:00:18 -0800 (PST)
(envelope-from andreasd@ifi.uio.no)
Received: from hrotti.ifi.uio.no (3034@hrotti.ifi.uio.no [129.240.64.15])
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id UAA11989
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 20:59:52 +0100 (MET)
Received: (from andreasd@localhost) by hrotti.ifi.uio.no ; Sun, 8 Nov 1998 20:59:52 +0100 (MET)
To: freebsd-current@FreeBSD.ORG
Subject: bootloader
From: Andreas Dobloug <andreasd@ifi.uio.no>
Date: 08 Nov 1998 20:59:51 +0100
Message-ID: <xnpk9162bwo.fsf@hrotti.ifi.uio.no>
Lines: 32
X-Mailer: Gnus v5.3/Emacs 19.34
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
I'm having problems with the boot loader.
I tried to build an elf-kernel, saved it as kernel.elf, and followed
this procedure:
| Reboot, and at the boot: prompt type '/boot/loader', then abort the
| kernel load and type 'boot kernel.elf'.
but the boot-loader couldn't find anything on my hd.
I.e. it reports something like "'/': no such file or directory" when
typing ls, and it can't find either kernel nor kernel.elf.
# dmesg | grep ahc
ahc0: <Adaptec aic7890/91 Ultra2 SCSI adapter> rev 0x00 int a irq 19
on pci0.6.0
ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs
da0 at ahc0 bus 0 target 1 lun 0
da1 at ahc0 bus 0 target 6 lun 0
(da1:ahc0:0:6:0): tagged openings now 63
(da0:ahc0:0:1:0): tagged openings now 63
The FBSD root is located on da1 (da1s3a)
When booting, the boot-loader prompt (and hence the environment)
reports 'disk2s3a' which I presume is the equivalent of da1s3a.
I guess the problem is me trying to boot from da1?
--
Andreas Dobloug : email: andreasd@ifi.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 Nov 8 12:25:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA16976
for freebsd-current-outgoing; Sun, 8 Nov 1998 12:25:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alive.znep.com (207-178-54-226.go2net.com [207.178.54.226])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16971
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 12:25:34 -0800 (PST)
(envelope-from marcs@znep.com)
Received: from localhost (marcs@localhost)
by alive.znep.com (8.9.1/8.9.1) with ESMTP id MAA07787;
Sun, 8 Nov 1998 12:20:59 -0800 (PST)
(envelope-from marcs@znep.com)
Date: Sun, 8 Nov 1998 12:20:59 -0800 (PST)
From: Marc Slemko <marcs@znep.com>
To: David Greenman <dg@root.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Err...something fishy going on in top.
In-Reply-To: <199811030905.BAA13428@implode.root.com>
Message-ID: <Pine.BSF.4.05.9811081217130.5670-100000@alive.znep.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, 3 Nov 1998, David Greenman wrote:
> >I rebuilt world a couple of hours ago, from a cvsup at around 8:30 CST
> >tonight. When I rebooted, the box seemed slower than it should have been.
> >To make a long story short, in the process of doing stuff, I noticed that
> >whenever there's heavy disk i/o, instead of the amount of memory dedicated
> >to cache increasing, the amount of memory being listed as inactive was
> >increasing. Huh? I'm confused. Right now, it looks like none of my
> >memory is being used for file cacheing, even though I have > 32 MB free.
> >What am I missing?
>
> You're missing what it all actually means. "cache" is a queue, not an
> indication of caching. The same is also true for "active", "inactive", and
> "free" - they are just various page queues that the system moves pages
> between depending on their priority. A change was made recently so that
the top man page says things like:
Cache: number of pages used for VM-level disk caching
Buf: number of pages used for BIO-level disk caching
It would be useful if someone who understood the exact semantics of each
could make the docs a bit more... verbose.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 13:26:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA23583
for freebsd-current-outgoing; Sun, 8 Nov 1998 13:26:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23577
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 13:26:23 -0800 (PST)
(envelope-from jfieber@fallout.campusview.indiana.edu)
Received: from localhost (jfieber@localhost)
by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id QAA18801;
Sun, 8 Nov 1998 16:25:53 -0500 (EST)
Date: Sun, 8 Nov 1998 16:25:53 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Eivind Eklund <eivind@yes.no>
cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <19981108160934.30826@follo.net>
Message-ID: <Pine.BSF.4.05.9811081553230.482-100000@fallout.campusview.indiana.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 Sun, 8 Nov 1998, Eivind Eklund wrote:
> On Sun, Nov 08, 1998 at 09:22:50AM -0500, John Fieber wrote:
> > One question: Is the problem "sticky"? By that I mean, if it is
> > triggered by a memomry shortage, is something in the kernel
> > corrupted that tends to kill/corrupt daemons from that point in
> > time on, or is it just something that affects isolated processes.
>
> All daemons running at that point seems to get something corrupted.
> If you restart the daemon, it won't happen again until you again run
> out of memory (or whatever it is that trigger the corruption).
I've just been re-examining log files. What I see is that
problems always follow this message which never occurs more than
once during any give time the system is up:
/kernel: swap_pager: suggest more swap space: 125 MB
It is always 125 MB...I'm still not completely clear on what that
number is, but anyway...
Here are some highlights from one particular system run where inetd
and httpd die. I've omitted redundant "signal 11" lines since once
the process is corrupted, any connection attempt generates a slew of
them.
Nov 3 16:53:44 fallout /kernel: FreeBSD 3.0-CURRENT #17: Tue Nov 3 16:46:57 EST 1998
Nov 3 17:33:58 fallout /kernel: swap_pager: suggest more swap space: 125 MB
Nov 5 03:09:22 fallout /kernel: pid 15615 (inetd), uid 0: exited on signal 11
...I kill and restart inetd at some point in this interval...
Nov 5 09:42:25 fallout /kernel: pid 16904 (inetd), uid 0: exited on signal 11
...And again...
Nov 5 13:36:34 fallout /kernel: pid 17779 (inetd), uid 0: exited on signal 11
...And again, this time inetd has the "junk pointer" patchs from
PR 8183 applied...
Nov 6 00:52:19 fallout /kernel: pid 19759 (httpd), uid 65534: exited on signal 11
Nov 6 03:14:47 fallout /kernel: pid 20245 (inetd), uid 0: exited on signal 11
...and I reboot in the morning...
There are no "swap_pager: out of swap" message anywhere in the logs
which go back to just before I switched from 2.2.7 to 3.0-BETA. Any
memory shortages after the first "suggest more swap" message are not
being logged if they occur.
Since this sample I've bumped swap from 128MB to 256MB and have not
had any problems yet.
Another curiosity, I'm getting some curiously garbled lines in the
log files:
Oct 25 09:11:00 fallout /kernel: pid 29392 (inetd
Oct 25 09:10:49 fallout inetd[180]: /usr/local/libexec/amanda/amandad[28958]: exit status 0xb
Oct 25 09:11:00 fallout /kernel: ), uid 0: exited on signal 11
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 13:37:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA24870
for freebsd-current-outgoing; Sun, 8 Nov 1998 13:37:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24851
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 13:37:01 -0800 (PST)
(envelope-from jfieber@fallout.campusview.indiana.edu)
Received: from localhost (jfieber@localhost)
by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id QAA18829;
Sun, 8 Nov 1998 16:36:26 -0500 (EST)
Date: Sun, 8 Nov 1998 16:36:26 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Eivind Eklund <eivind@yes.no>
cc: dg@root.com, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <19981108171319.19261@follo.net>
Message-ID: <Pine.BSF.4.05.9811081628170.482-100000@fallout.campusview.indiana.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 Sun, 8 Nov 1998, Eivind Eklund wrote:
> On Sun, Nov 08, 1998 at 04:50:23PM +0100, Eivind Eklund wrote:
> > On Sun, Nov 08, 1998 at 07:17:11AM -0800, David Greenman wrote:
> > > If the application (phk malloc or the caller of malloc?) isn't
> > > prepared for this, it may end up with a NULL pointer that it doesn't
> > > expect - perhaps not even tripping over it until sometime later.
> >
> > I'm pretty sure this is not the problem. Inactive daemons seems start
> > dying, and I don't always get the "out of swap space" message that
> > comes with setting swap_pager_full.
>
> Oh, and another aspect: This suddenly started happening. It has been
> stable for 3/4 of a year, and then suddenly started happening
> reproducably one day, after a kernel update while John was doing his
> changes.
I'd never seen this until I went from 2.2.7 to 3.0-BETA and later
-RELEASE. When I made the move, there were no hardware or swap
configuration changes. Apache, compiled under 2.2.7, started
having problems that did not change when I re-compiled under 3.0.
Sendmail and inetd are different in 3.0 so I can't make any
cross-version comparisons there.
So something is different...whether inetd, apache and sendmail
(and some have reported crond) are just having latent bugs
activated by a change in the OS, or the OS is whacky I don't
know.
Anyway, the disk housing my extra 128MB of swap is just a
temporary loaner so I anticipate returning to crashing inetd
soon. :-)
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 14:16:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA24903
for freebsd-current-outgoing; Sun, 8 Nov 1998 13:37:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24897
for <current@freebsd.org>; Sun, 8 Nov 1998 13:37:17 -0800 (PST)
(envelope-from tlambert@usr08.primenet.com)
Received: (from daemon@localhost)
by smtp04.primenet.com (8.8.8/8.8.8) id OAA16560
for <current@freebsd.org>; Sun, 8 Nov 1998 14:37:01 -0700 (MST)
Received: from usr08.primenet.com(206.165.6.208)
via SMTP by smtp04.primenet.com, id smtpd016550; Sun Nov 8 14:36:57 1998
Received: (from tlambert@localhost)
by usr08.primenet.com (8.8.5/8.8.5) id OAA16293
for current@freebsd.org; Sun, 8 Nov 1998 14:36:56 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199811082136.OAA16293@usr08.primenet.com>
Subject: jobs@freebsd.org
To: current@FreeBSD.ORG
Date: Sun, 8 Nov 1998 21:36:56 +0000 (GMT)
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
I think there needs to be a new list, "jobs@freebsd.org", for
companies looking for people to send job listings to.
Whistle is currently looking for a couple of people, and it's
really hard to identify FreeBSD capable people who are interested
in being "looked for".
There are the pages where people who want to do consulting
advertise themselves, but no place where a company who wants
full time employees can put up a sign.
What's missing is a community contact point, and I think that
jobs@freebsd.org would be a good place for people to self-select
themselves into the community.
Anyone else think this is a good idea?
Terry Lambert
terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 14:31:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA29723
for freebsd-current-outgoing; Sun, 8 Nov 1998 14:31:19 -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 OAA29712
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 14:31:16 -0800 (PST)
(envelope-from ken@panzer.plutotech.com)
Received: (from ken@localhost)
by panzer.plutotech.com (8.9.1/8.8.5) id PAA17331;
Sun, 8 Nov 1998 15:30:54 -0700 (MST)
From: "Kenneth D. Merry" <ken@plutotech.com>
Message-Id: <199811082230.PAA17331@panzer.plutotech.com>
Subject: Re: jobs@freebsd.org
In-Reply-To: <199811082136.OAA16293@usr08.primenet.com> from Terry Lambert at "Nov 8, 98 09:36:56 pm"
To: tlambert@primenet.com (Terry Lambert)
Date: Sun, 8 Nov 1998 15:30:54 -0700 (MST)
Cc: 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
Terry Lambert wrote...
> I think there needs to be a new list, "jobs@freebsd.org", for
> companies looking for people to send job listings to.
>
> Whistle is currently looking for a couple of people, and it's
> really hard to identify FreeBSD capable people who are interested
> in being "looked for".
>
> There are the pages where people who want to do consulting
> advertise themselves, but no place where a company who wants
> full time employees can put up a sign.
>
> What's missing is a community contact point, and I think that
> jobs@freebsd.org would be a good place for people to self-select
> themselves into the community.
>
> Anyone else think this is a good idea?
Did you bother looking at the available lists? Among them is:
freebsd-jobs jobs offered and sought
(an alias for that is 'jobs@freebsd.org')
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 Sun Nov 8 14:31:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA29765
for freebsd-current-outgoing; Sun, 8 Nov 1998 14:31:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from picnic.mat.net (picnic.mat.net [206.246.122.117])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29755
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 14:31:30 -0800 (PST)
(envelope-from chuckr@mat.net)
Received: from localhost (chuckr@localhost)
by picnic.mat.net (8.9.1/8.8.5) with ESMTP id RAA11314;
Sun, 8 Nov 1998 17:30:16 -0500 (EST)
Date: Sun, 8 Nov 1998 17:30:16 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Terry Lambert <tlambert@primenet.com>
cc: current@FreeBSD.ORG
Subject: Re: jobs@freebsd.org
In-Reply-To: <199811082136.OAA16293@usr08.primenet.com>
Message-ID: <Pine.BSF.4.05.9811081726520.10145-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 Sun, 8 Nov 1998, Terry Lambert wrote:
> I think there needs to be a new list, "jobs@freebsd.org", for
> companies looking for people to send job listings to.
>
> Whistle is currently looking for a couple of people, and it's
> really hard to identify FreeBSD capable people who are interested
> in being "looked for".
>
> There are the pages where people who want to do consulting
> advertise themselves, but no place where a company who wants
> full time employees can put up a sign.
>
> What's missing is a community contact point, and I think that
> jobs@freebsd.org would be a good place for people to self-select
> themselves into the community.
>
> Anyone else think this is a good idea?
Terry, isn't this what chat's for? I'm just a little overwhelmed by the
number of lists, and chat hasn't got any real limitations. They might
get upset if you posted porno, but shy of that, you aren't going to see
any official censorship. Jobs type things are well within reasonable
limits. I'd personally like to see chat used for things like that.
----------------------------+-----------------------------------------------
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 Sun Nov 8 14:40:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA00690
for freebsd-current-outgoing; Sun, 8 Nov 1998 14:40:00 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: (from jmb@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA00681;
Sun, 8 Nov 1998 14:39:57 -0800 (PST)
(envelope-from jmb)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199811082239.OAA00681@hub.freebsd.org>
Subject: Re: jobs@freebsd.org
In-Reply-To: <199811082136.OAA16293@usr08.primenet.com> from Terry Lambert at "Nov 8, 98 09:36:56 pm"
To: tlambert@primenet.com (Terry Lambert)
Date: Sun, 8 Nov 1998 14:39:57 -0800 (PST)
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
Terry Lambert wrote:
> I think there needs to be a new list, "jobs@freebsd.org", for
> companies looking for people to send job listings to.
there already is a mailing list for companies and people
looking for FreeBSD related jobs. created the list quite
some time ago....round about the first week of june 1997,
if not earlier....the earliest archived message is
june 13th 1997.
the list is called "freebsd-jobs@freebsd.org"
you can also use the alias "jobs@freebsd.org"
jmb
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 14:41:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA00892
for freebsd-current-outgoing; Sun, 8 Nov 1998 14:41:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00873
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 14:41:22 -0800 (PST)
(envelope-from son@teaser.fr)
Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40])
by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id WAA25301;
Sun, 8 Nov 1998 22:44:56 +0100 (MET)
Received: (from son@localhost)
by teaser.fr (8.9.1/8.8.5) id WAA03531;
Sun, 8 Nov 1998 22:01:53 GMT
Message-ID: <19981108220152.06173@breizh.prism.uvsq.fr>
Date: Sun, 8 Nov 1998 22:01:53 +0000
From: Nicolas Souchu <nsouch@teaser.fr>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Cc: FreeBSD Current <current@FreeBSD.ORG>
Subject: ZIP+ and NatSemi parallel port chipst (was Re: ZIP, again)
References: <19981108201614.45459@breizh.prism.uvsq.fr> <XFMail.981108195642.asmodai@wxs.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81e
In-Reply-To: <XFMail.981108195642.asmodai@wxs.nl>; from Jeroen Ruigrok/Asmodai on Sun, Nov 08, 1998 at 07:56:42PM +0100
X-Operating-System: FreeBSD breizh 3.0-BETA FreeBSD 3.0-BETA
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 08, 1998 at 07:56:42PM +0100, Jeroen Ruigrok/Asmodai wrote:
>
>On 08-Nov-98 Nicolas Souchu wrote:
>> On Sun, Nov 08, 1998 at 12:21:53PM +0100, Jeroen Ruigrok/Asmodai wrote:
>> You're joking?
>
>Nah,, just blind as a bat...
:)
I'm a bit curious.. is your parallel port chipset generic or what else?
(send me your boot logs if you don't know)
In fact, we have some problems with NSC chips here.
Anybody could report successfull ZIP+ detection with NatSemi chips?
Thanks.
Nicolas.
--
nsouch@teaser.fr / nsouch@freebsd.org
FreeBSD - Turning PCs into workstations - 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 Nov 8 15:17:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA05115
for freebsd-current-outgoing; Sun, 8 Nov 1998 15:17:35 -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 PAA05110
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 15:17:32 -0800 (PST)
(envelope-from gjp@gjp.erols.com)
Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1])
by gjp.erols.com (8.9.1/8.8.7) with ESMTP id SAA23303;
Sun, 8 Nov 1998 18:15:59 -0500 (EST)
(envelope-from gjp@gjp.erols.com)
X-Mailer: exmh version 2.0.1 12/23/97
To: Joel Ray Holveck <joelh@gnu.org>
cc: Leif Neland <root@swimsuit.internet.dk>, freebsd-current@FreeBSD.ORG
From: "Gary Palmer" <gpalmer@FreeBSD.ORG>
Subject: Re: ext2fs_mod.o not found, was: How to make /dev/da0
In-reply-to: Your message of "08 Nov 1998 09:59:52 CST."
<86d86yw4xz.fsf@detlev.UUCP>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 08 Nov 1998 18:15:59 -0500
Message-ID: <23299.910566959@gjp.erols.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Joel Ray Holveck wrote in message ID
<86d86yw4xz.fsf@detlev.UUCP>:
> What is the status on ext2fs? It's listed in the "undocumented"
> section of LINT right now; is it being maintained or anything?
I don't think any one person claims ownership of it, however when bugs arise
they do tend to get worked on because a lot of people use ext2fs.
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 Sun Nov 8 15:27:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA06531
for freebsd-current-outgoing; Sun, 8 Nov 1998 15:27:45 -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 PAA06526
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 15:27:44 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id PAA03141;
Sun, 8 Nov 1998 15:22:57 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdjK3139; Sun Nov 8 23:22:55 1998
Date: Sun, 8 Nov 1998 15:22:25 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Eivind Eklund <eivind@yes.no>
cc: John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <19981108161038.42967@follo.net>
Message-ID: <Pine.BSF.3.95.981108152109.12341C-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, 8 Nov 1998, Eivind Eklund wrote:
> On Sun, Nov 08, 1998 at 05:38:57AM -0800, Julian Elischer wrote:
> > We've been having a problem with daemons dying with sig11 singe at least
> > mid 97 with 486DX100 boxen.
>
> Can you give more details? Which NIC, and is there anything that use
> PCI busmastering DMA or contigmalloc() in action here?
ed0 and ed1
(SMC compatible)
no contigmalloc.
no bus master DMA
>
> Eivind.
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 15:39:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA07531
for freebsd-current-outgoing; Sun, 8 Nov 1998 15:39:56 -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 PAA07526
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 15:39:54 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id PAA03211;
Sun, 8 Nov 1998 15:27:28 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdhf3209; Sun Nov 8 23:27:18 1998
Date: Sun, 8 Nov 1998 15:26:48 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Brian Feldman <green@unixhelp.org>
cc: Eivind Eklund <eivind@yes.no>, dg@root.com,
John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.BSF.4.05.9811081144340.4580-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.3.95.981108152353.12341D-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 we have.
It's been a while since we looked at it closely but it appeared that
a page of useful memeory was suddenly unmapped from the process.
we were hoping that switching to a newer version of FreeBSD
would solve it be we're still seeing it in 3.0 based systems.
On Sun, 8 Nov 1998, Brian Feldman wrote:
> Is it just me or has noone actually captured the corefiles, compiled
> whatever died -g, and tried to debug exactly what caused the sig11? Not
> the underlying cause, just the "actual" cause (like a certain register
> being a wrong value).
>
> Cheers,
> Brian Feldman
>
> On Sun, 8 Nov 1998, Eivind Eklund wrote:
>
> > On Sun, Nov 08, 1998 at 07:17:11AM -0800, David Greenman wrote:
> > > >On Sun, Nov 08, 1998 at 09:22:50AM -0500, John Fieber wrote:
> > > >> One question: Is the problem "sticky"? By that I mean, if it is
> > > >> triggered by a memomry shortage, is something in the kernel
> > > >> corrupted that tends to kill/corrupt daemons from that point in
> > > >> time on, or is it just something that affects isolated processes.
> > > >
> > > >All daemons running at that point seems to get something corrupted.
> > > >If you restart the daemon, it won't happen again until you again run
> > > >out of memory (or whatever it is that trigger the corruption).
> > >
> > > brk(2) will fail and return ENOMEM if the system is low on swap space.
> >
> > phkmalloc() checks for this.
> >
> > Anyway; why does it do this? It does not look like it actually needs
> > to do this, and if we do a memory overcommit, it seems to me that we
> > could do it all the way (or at least have a sysctl to make it do it
> > all the way). I'm also sorely missing a sysctl to turn off memory
> > overcommit... (I don't know the VM system well enough to implement it
> > myself, and I feel very uncomfortable with doing changes in it.)
> >
> > > If the application (phk malloc or the caller of malloc?) isn't
> > > prepared for this, it may end up with a NULL pointer that it doesn't
> > > expect - perhaps not even tripping over it until sometime later.
> >
> > I'm pretty sure this is not the problem. Inactive daemons seems start
> > dying, and I don't always get the "out of swap space" message that
> > comes with setting swap_pager_full.
> >
> > The symptoms are that when the daemon fork after a 'daemons dying
> > occurrance', they will immediately get a sig11 on the child fork.
> >
> > Eivind.
> >
> > 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
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 15:45:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA07934
for freebsd-current-outgoing; Sun, 8 Nov 1998 15:45:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from garman.dyn.ml.org (pm106-17.dialip.mich.net [192.195.231.219])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA07927
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 15:45:11 -0800 (PST)
(envelope-from garman@garman.dyn.ml.org)
Message-Id: <199811082345.PAA07927@hub.freebsd.org>
Received: (qmail 2602 invoked from smtpd); 8 Nov 1998 21:57:04 -0000
Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1)
by localhost.garman.net with SMTP; 8 Nov 1998 21:57:03 -0000
Date: Sun, 8 Nov 1998 16:57:02 -0500 (EST)
From: garman@earthling.net
Reply-To: garman@earthling.net
Subject: Re: The infamous dying daemons bug
To: green@unixhelp.org
cc: eivind@yes.no, dg@root.com, jfieber@indiana.edu, current@FreeBSD.ORG
In-Reply-To: <Pine.BSF.4.05.9811081144340.4580-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 8 Nov, Brian Feldman wrote:
> Is it just me or has noone actually captured the corefiles, compiled
> whatever died -g, and tried to debug exactly what caused the sig11? Not
> the underlying cause, just the "actual" cause (like a certain register
> being a wrong value).
>
Yes, I have in my samba case.
In the samba case, smbd attempts to allocate 56 bytes for a ServicePtrs
array. This (apparently) fails (according to the log files)... and the
segv occurs when later it attempts to dereference it. I lost the nice
traces I did earlier (remember those null postings from me? :)) cause
my mail client wasn't able to allocate memory for my message :)
I had traces from both a "normal" samba which didn't exhibit the
symptoms, and a "tainted" samba which did. The only thing different
was the ServicePtrs array was NULL in the smbd that segfaulted.
This happens when my swap is at 50-70% capacity, so i'm not running
critically low on memory here.
I can redo the smbd traces if there's interest.
I'd really like to know whats going on, as smbd isn't the only thing
involved; ssh refuses connections after a while (yet the daemon is
still running; i haven't gdb'ed it yet, but i'm assuming its the same
problems)
thanks
--
Jason Garman http://garman.dyn.ml.org/
Student, University of Maryland garman@earthling.net
And now... did you know that: Whois: JAG145
"If you fart consistently for 6 years and 9 months, enough gas is
produced to create the energy of an atomic bomb." -- 0xdeadbeef posting
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 16:04:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA11324
for freebsd-current-outgoing; Sun, 8 Nov 1998 16:04:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from PigStuy.dyn.ml.org (nyc-ny75-56.ix.netcom.com [209.109.228.120])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11318
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 16:04:20 -0800 (PST)
(envelope-from spork@pigstuy.dyn.ml.org)
Received: from localhost (spork@localhost)
by PigStuy.dyn.ml.org (8.8.8/8.8.7) with SMTP id TAA01535
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 19:03:52 -0500 (EST)
(envelope-from spork@pigstuy.dyn.ml.org)
Date: Sun, 8 Nov 1998 19:03:51 -0500 (EST)
From: Spike Gronim <spork@pigstuy.dyn.ml.org>
Reply-To: sporkl@ix.netcom.com
To: freebsd-current@FreeBSD.ORG
Subject: SparQ Drive and 3.0 upgrade
Message-ID: <Pine.BSF.3.96.981108190140.450C-100000@PigStuy.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
Hello.
I recently got a SparQ EIDE 1.0GB drive, and my 2.2.7-STABLE
system doesn't detect it. I downloaded the 3.0 boot floppy and booting
that it got detected. If I upgrade to 3.0-RELEASE right now, on my PII
w/an AHA-2940UW, AGP video card, etc., will I completely regret it? What
is the cvsup tag for 3.0? Thanks.
-Spike Gronim
sporkl@ix.netcom.com
The majority only rules those who let them.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 16:25:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA13436
for freebsd-current-outgoing; Sun, 8 Nov 1998 16:25:01 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles27.castles.com [208.214.165.27])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13430
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 16:25: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 QAA04399;
Sun, 8 Nov 1998 16:24:06 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811090024.QAA04399@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: sporkl@ix.netcom.com
cc: freebsd-current@FreeBSD.ORG
Subject: Re: SparQ Drive and 3.0 upgrade
In-reply-to: Your message of "Sun, 08 Nov 1998 19:03:51 EST."
<Pine.BSF.3.96.981108190140.450C-100000@PigStuy.dyn.ml.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 08 Nov 1998 16:24:05 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> I recently got a SparQ EIDE 1.0GB drive, and my 2.2.7-STABLE
> system doesn't detect it. I downloaded the 3.0 boot floppy and booting
> that it got detected. If I upgrade to 3.0-RELEASE right now, on my PII
> w/an AHA-2940UW, AGP video card, etc., will I completely regret it? What
> is the cvsup tag for 3.0? Thanks.
3.0-RELEASE has the same format release tag as all the other releases.
You'd be better off supping straight to -current though.
What you'll regret most however is buying one of those disgusting Sparq
drives.
--
\\ 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 Nov 8 17:15:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA17211
for freebsd-current-outgoing; Sun, 8 Nov 1998 17:15:49 -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 RAA17201
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 17:15:45 -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 UAA09906;
Sun, 8 Nov 1998 20:03:46 -0500 (EST)
Date: Sun, 8 Nov 1998 20:03:45 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Julian Elischer <julian@whistle.com>
cc: Eivind Eklund <eivind@yes.no>, dg@root.com,
John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.BSF.3.95.981108152353.12341D-100000@current1.whistle.com>
Message-ID: <Pine.BSF.4.05.9811082002450.9729-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
Yech, that really isn't good having your process's memory disappearing
under you... anyone have any idea why for instance I don't have this
problem, nor do many others?
Cheers,
Brian Feldman
On Sun, 8 Nov 1998, Julian Elischer wrote:
> yes we have.
>
> It's been a while since we looked at it closely but it appeared that
> a page of useful memeory was suddenly unmapped from the process.
>
> we were hoping that switching to a newer version of FreeBSD
> would solve it be we're still seeing it in 3.0 based systems.
>
>
> On Sun, 8 Nov 1998, Brian Feldman wrote:
>
> > Is it just me or has noone actually captured the corefiles, compiled
> > whatever died -g, and tried to debug exactly what caused the sig11? Not
> > the underlying cause, just the "actual" cause (like a certain register
> > being a wrong value).
> >
> > Cheers,
> > Brian Feldman
> >
> > On Sun, 8 Nov 1998, Eivind Eklund wrote:
> >
> > > On Sun, Nov 08, 1998 at 07:17:11AM -0800, David Greenman wrote:
> > > > >On Sun, Nov 08, 1998 at 09:22:50AM -0500, John Fieber wrote:
> > > > >> One question: Is the problem "sticky"? By that I mean, if it is
> > > > >> triggered by a memomry shortage, is something in the kernel
> > > > >> corrupted that tends to kill/corrupt daemons from that point in
> > > > >> time on, or is it just something that affects isolated processes.
> > > > >
> > > > >All daemons running at that point seems to get something corrupted.
> > > > >If you restart the daemon, it won't happen again until you again run
> > > > >out of memory (or whatever it is that trigger the corruption).
> > > >
> > > > brk(2) will fail and return ENOMEM if the system is low on swap space.
> > >
> > > phkmalloc() checks for this.
> > >
> > > Anyway; why does it do this? It does not look like it actually needs
> > > to do this, and if we do a memory overcommit, it seems to me that we
> > > could do it all the way (or at least have a sysctl to make it do it
> > > all the way). I'm also sorely missing a sysctl to turn off memory
> > > overcommit... (I don't know the VM system well enough to implement it
> > > myself, and I feel very uncomfortable with doing changes in it.)
> > >
> > > > If the application (phk malloc or the caller of malloc?) isn't
> > > > prepared for this, it may end up with a NULL pointer that it doesn't
> > > > expect - perhaps not even tripping over it until sometime later.
> > >
> > > I'm pretty sure this is not the problem. Inactive daemons seems start
> > > dying, and I don't always get the "out of swap space" message that
> > > comes with setting swap_pager_full.
> > >
> > > The symptoms are that when the daemon fork after a 'daemons dying
> > > occurrance', they will immediately get a sig11 on the child fork.
> > >
> > > Eivind.
> > >
> > > 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
> >
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 17:18:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA17501
for freebsd-current-outgoing; Sun, 8 Nov 1998 17:18:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA17496
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 17:18:12 -0800 (PST)
(envelope-from tom@uniserve.com)
Received: from shell.uniserve.ca [204.244.186.218]
by pop.uniserve.com with smtp (Exim 1.82 #4)
id 0zcfxN-000300-00; Sun, 8 Nov 1998 17:17:25 -0800
Date: Sun, 8 Nov 1998 17:17:22 -0800 (PST)
From: Tom <tom@uniserve.com>
X-Sender: tom@shell.uniserve.ca
To: Mike Smith <mike@smith.net.au>
cc: sporkl@ix.netcom.com, freebsd-current@FreeBSD.ORG
Subject: Re: SparQ Drive and 3.0 upgrade
In-Reply-To: <199811090024.QAA04399@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.02A.9811081716400.7009-100000@shell.uniserve.ca>
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, 8 Nov 1998, Mike Smith wrote:
> >
> > I recently got a SparQ EIDE 1.0GB drive, and my 2.2.7-STABLE
> > system doesn't detect it. I downloaded the 3.0 boot floppy and booting
> > that it got detected. If I upgrade to 3.0-RELEASE right now, on my PII
> > w/an AHA-2940UW, AGP video card, etc., will I completely regret it? What
> > is the cvsup tag for 3.0? Thanks.
>
> 3.0-RELEASE has the same format release tag as all the other releases.
> You'd be better off supping straight to -current though.
>
> What you'll regret most however is buying one of those disgusting Sparq
> drives.
Especially now that SyQuest has just gone out of business.
> --
> \\ 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
Tom
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 17:32:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA19406
for freebsd-current-outgoing; Sun, 8 Nov 1998 17:32:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from PaLaDiN7.ml.org (PaLaDiN7.ml.org [208.132.240.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19400
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 17:32:40 -0800 (PST)
(envelope-from pal@PaLaDiN7.ml.org)
Received: from localhost (localhost.my.domain [127.0.0.1])
by PaLaDiN7.ml.org (8.9.1/8.9.1) with ESMTP id UAA06338;
Sun, 8 Nov 1998 20:32:19 -0500 (EST)
(envelope-from pal@PaLaDiN7.ml.org)
Date: Sun, 8 Nov 1998 20:32:17 -0500 (EST)
From: pal <pal@PaLaDiN7.ml.org>
To: freebsd-current@FreeBSD.ORG
cc: osa@freebsd.org.ru
Subject: SSH 2.0.10 BUG? (!)
Message-ID: <Pine.BSF.4.05.9811082026240.316-100000@PaLaDiN7.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
Hi,
I have FreeBSD 3.0 current, actualy I have current version only of
/src/sys other from 3.0-RELEASE and ssh 2.0.10 installed on it.
My friend Sergey Osokin (osa@freebsd.org.ru) discovered it when he
connected to my FreeBSD box using SSH2 (veersion 2.0.10)
same thing appears when I trying to connect to it from linux box at work
using same ssh2. The user connected this
way not showed up by finger and w/who utilities however ps aux| grep
$username show processes they are running
and netstat shows established connections, last showes user as logged in.
However, further experiments showing that ssh1 clients connected to my box
shows up fine in all those utilities.
Best wishes,
Gene
P.S. bug submitted to SSH developers
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 17:41:08 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA20640
for freebsd-current-outgoing; Sun, 8 Nov 1998 17:41:08 -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 RAA20635;
Sun, 8 Nov 1998 17:41:01 -0800 (PST)
(envelope-from dawes@rf900.physics.usyd.edu.au)
Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id MAA21714; Mon, 9 Nov 1998 12:39:15 +1100 (EST)
Message-ID: <19981109123915.A21444@rf900.physics.usyd.edu.au>
Date: Mon, 9 Nov 1998 12:39:15 +1100
From: David Dawes <dawes@rf900.physics.usyd.edu.au>
To: Donn Miller <dmm125@bellatlantic.net>, ports@FreeBSD.ORG,
current@FreeBSD.ORG
Subject: Re: Ports/patches for X332servonly
References: <Pine.BSF.4.05.9811081054100.424-100000@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.05.9811081054100.424-100000@localhost>; from Donn Miller on Sun, Nov 08, 1998 at 11:05:27AM +0000
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 08, 1998 at 11:05:27AM +0000, Donn Miller wrote:
>Just trying to find out if anyone did a port and/or patch for
>X332servonly.tgz. It's like the full source for XFree86 but it doesn't
>include the stuff for building shared libs. I need the source code so I
>can modify it to make a driver for my chipset, which is unsupported.
>
>BTW, building XFree86 from sratch is pretty nasty. One minor change to
>any of the config files in xc/config/cf sometimes throws the whole build
>out of whack.
That surprises you?
>The shared/static libs build OK, but when it comes time to link all the
>object files and libs together to produce the X-server, massive amounts of
>errors about "undefined reference to ..." come pouring out like crazy.
>This is in the subdir xc/programs/Xserver/hw...
>
>I tried building it w/out changing any source at first, just to see if it
>would compile, and it won't compile. So anyone successfully built the
>XFree86 servers from source on 3.0-R?
Patches are required for FreeBSD/ELF (FreeBSD wasn't ELF when 3.3.2 was
released). You should be able to use the patches in FreeBSD's XFree86
port. Just ignore any that might be for files not included in
X332servonly.tgz
Or you could wait for a week or so for XFree86 3.3.3 which will include
support for FreeBSD/ELF out of the box.
BTW, what chipset are you planning to add support for?
David
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 17:42:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA20978
for freebsd-current-outgoing; Sun, 8 Nov 1998 17:42:03 -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 RAA20908;
Sun, 8 Nov 1998 17:41:59 -0800 (PST)
(envelope-from doconnor@gsoft.com.au)
Received: from cain.gsoft.com.au (cain [203.38.152.97])
by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA15085;
Mon, 9 Nov 1998 12:11:38 +1030 (CST)
(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.981109121137.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: <XFMail.981108120955.asmodai@wxs.nl>
Date: Mon, 09 Nov 1998 12:11:37 +1030 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Subject: RE: AWE-32
Cc: FreeBSD Hackers <hackers@FreeBSD.ORG>,
FreeBSD Current <current@FreeBSD.ORG>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 08-Nov-98 Jeroen Ruigrok/Asmodai wrote:
> controller snd0
> device sb0 at isa? port 0x220 irq 5 drq 1
> device sbxvi0 at isa? drq 5
> device sbmidi0 at isa? port 0x330
> device awe0 at isa? port 0x620
>
> Am I missing something in here?
Have you typed ->
pnp 1 0 enable os port0 0x220 port1 0x330 port2 0x388 irq0 5 drq0 1 drq1 5
pnp 1 1 enable os port0 0x200
pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20
When you boot -c?
---
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 Sun Nov 8 18:05:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA23131
for freebsd-current-outgoing; Sun, 8 Nov 1998 18:05:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from garman.dyn.ml.org (pm106-17.dialip.mich.net [192.195.231.219])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA23126
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 18:05:52 -0800 (PST)
(envelope-from garman@garman.dyn.ml.org)
Message-Id: <199811090205.SAA23126@hub.freebsd.org>
Received: (qmail 3099 invoked from smtpd); 9 Nov 1998 02:07:07 -0000
Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1)
by localhost.garman.net with SMTP; 9 Nov 1998 02:07:07 -0000
Date: Sun, 8 Nov 1998 21:07:06 -0500 (EST)
From: garman@earthling.net
Reply-To: garman@earthling.net
Subject: Re: The infamous dying daemons bug
To: green@unixhelp.org
cc: current@FreeBSD.ORG
In-Reply-To: <Pine.BSF.4.05.9811082002450.9729-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 8 Nov, Brian Feldman wrote:
> Yech, that really isn't good having your process's memory disappearing
> under you... anyone have any idea why for instance I don't have this
> problem, nor do many others?
>
whats your swap usage look like? this problem (for me at least) is
much much more likely to occur with a (relatively) high amount of swap
usage, usually in the 50-70% range (out of 150MB of swap)
enjoy
--
Jason Garman http://garman.dyn.ml.org/
Student, University of Maryland garman@earthling.net
And now... did you know that: Whois: JAG145
"If you fart consistently for 6 years and 9 months, enough gas is
produced to create the energy of an atomic bomb." -- 0xdeadbeef posting
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 18:23:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA24779
for freebsd-current-outgoing; Sun, 8 Nov 1998 18:23:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from werple.mira.net (werple.mira.net [203.9.190.18])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA24774
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 18:23:53 -0800 (PST)
(envelope-from gfm@mira.net)
Received: (qmail 20016 invoked from network); 9 Nov 1998 02:23:37 -0000
Received: from dp-m-r095.werple.net.au (203.17.46.95)
by mira.net with SMTP; 9 Nov 1998 02:23:37 -0000
From: gfm@mira.net (Graham Menhennitt)
To: freebsd-current@FreeBSD.ORG
Subject: 3.0-CURRENT: Adaptec 1540 not detected (with workaround)
Date: Mon, 09 Nov 1998 02:25:45 GMT
Message-ID: <36484fb6.262608561@mira.net>
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 SAA24775
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I have just upgraded by 2.2-STABLE machine to 3.0-CURRENT. It couldn't boot
either kernel.GENERIC or the custom kernel that I built. It said that it
didn't detect my Adaptec 1540 (and then paniced with "cannot mount root").
I even specified the exact port address, IRQ and DRQ in userconfig. Still
no go. It used to work fine with 2.2 and was correctly detected by the
kernel on the 3.0 boot floppy.
Eventually I found the problem. In /usr/src/sys/dev/aha/aha.c there is some
code that attempts to distinguish between Adaptec and Buslogic adaptors.
This was failing. I'm not sure what model my adaptor is (I think it's an
'A') but it is a genuine Adaptec. Hence the comment in the code about
cloned cards may apply to some genuine ones also.
Anyway, the following patch worked around the problem for me.
Graham
*** aha.c Sun Nov 8 17:19:37 1998
--- aha.c_save Fri Oct 16 09:46:33 1998
***************
*** 324,340 ****
* this register, and return 0xff, while buslogic cards will return
* something different.
*
* XXX I'm not sure how this will impact other cloned cards.
*/
if (aha->boardid <= 0x42) {
status = aha_inb(aha, GEOMETRY_REG);
if (status != 0xff)
! /*return (ENXIO)*/;
}
return (0);
}
/*
* Pull the boards setup information and record it in our softc.
*/
--- 324,340 ----
* this register, and return 0xff, while buslogic cards will return
* something different.
*
* XXX I'm not sure how this will impact other cloned cards.
*/
if (aha->boardid <= 0x42) {
status = aha_inb(aha, GEOMETRY_REG);
if (status != 0xff)
! return (ENXIO);
}
return (0);
}
/*
* Pull the boards setup information and record it in our softc.
*/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 18:28:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA25304
for freebsd-current-outgoing; Sun, 8 Nov 1998 18:28:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from PigStuy.dyn.ml.org ([205.184.128.107])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25299
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 18:28:44 -0800 (PST)
(envelope-from spork@pigstuy.dyn.ml.org)
Received: from localhost (spork@localhost)
by PigStuy.dyn.ml.org (8.8.8/8.8.7) with SMTP id VAA07072;
Sun, 8 Nov 1998 21:28:06 -0500 (EST)
(envelope-from spork@pigstuy.dyn.ml.org)
Date: Sun, 8 Nov 1998 21:28:06 -0500 (EST)
From: Spike Gronim <spork@pigstuy.dyn.ml.org>
Reply-To: sporkl@ix.netcom.com
To: pal <pal@PaLaDiN7.ml.org>
cc: freebsd-current@FreeBSD.ORG, osa@freebsd.org.ru
Subject: Re: SSH 2.0.10 BUG? (!)
In-Reply-To: <Pine.BSF.4.05.9811082026240.316-100000@PaLaDiN7.ml.org>
Message-ID: <Pine.BSF.3.96.981108212602.450G-100000@PigStuy.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 Sun, 8 Nov 1998, pal wrote:
> Hi,
> I have FreeBSD 3.0 current, actualy I have current version only of
> /src/sys other from 3.0-RELEASE and ssh 2.0.10 installed on it.
>
> My friend Sergey Osokin (osa@freebsd.org.ru) discovered it when he
> connected to my FreeBSD box using SSH2 (veersion 2.0.10)
> same thing appears when I trying to connect to it from linux box at work
> using same ssh2. The user connected this
> way not showed up by finger and w/who utilities however ps aux| grep
> $username show processes they are running
> and netstat shows established connections, last showes user as logged in.
> However, further experiments showing that ssh1 clients connected to my box
> shows up fine in all those utilities.
>
> Best wishes,
> Gene
>
> P.S. bug submitted to SSH developers
Could it be incorrectly set permissions on your sshd binary? I encountered
similar problems with my xterms, untill I changed the permissions to
-rwsr-xr-x.
-Spike Gronim
sporkl@ix.netcom.com
The majority only rules those who let them.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 18:33:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA25563
for freebsd-current-outgoing; Sun, 8 Nov 1998 18:33:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from PaLaDiN7.ml.org (PaLaDiN7.ml.org [208.132.240.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25558
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 18:33:46 -0800 (PST)
(envelope-from pal@PaLaDiN7.ml.org)
Received: from localhost (localhost.my.domain [127.0.0.1])
by PaLaDiN7.ml.org (8.9.1/8.9.1) with ESMTP id VAA06653;
Sun, 8 Nov 1998 21:33:19 -0500 (EST)
(envelope-from pal@PaLaDiN7.ml.org)
Date: Sun, 8 Nov 1998 21:33:17 -0500 (EST)
From: pal <pal@PaLaDiN7.ml.org>
To: sporkl@ix.netcom.com
cc: freebsd-current@FreeBSD.ORG, osa@freebsd.org.ru
Subject: Re: SSH 2.0.10 BUG? (!)
In-Reply-To: <Pine.BSF.3.96.981108212602.450G-100000@PigStuy.dyn.ml.org>
Message-ID: <Pine.BSF.4.05.9811082130270.316-100000@PaLaDiN7.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
its:
-rwxr-xr-x 1 root wheel 1310188 28 20:57 sshd2
On Sun, 8 Nov 1998, Spike Gronim wrote:
> On Sun, 8 Nov 1998, pal wrote:
[skiped]
>
>
> Could it be incorrectly set permissions on your sshd binary? I encountered
> similar problems with my xterms, untill I changed the permissions to
> -rwsr-xr-x.
>
> -Spike Gronim
> sporkl@ix.netcom.com
>
>
> The majority only rules those who let them.
>
>
> 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 Nov 8 18:38:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA26072
for freebsd-current-outgoing; Sun, 8 Nov 1998 18:38:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mailgw1.lmco.com (mailgw1.lmco.com [192.31.106.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26065
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 18:38:04 -0800 (PST)
(envelope-from george.w.dinolt@lmco.com)
Received: from emss02g01.ems.lmco.com (relay2.ems.lmco.com [198.7.15.39])
by mailgw1.lmco.com (8.8.8/8.8.8) with ESMTP id TAA32063;
Sun, 8 Nov 1998 19:37:49 -0700 (MST)
Received: from wdl1.wdl.lmco.com ([137.249.32.1]) by lmco.com (PMDF V5.1-10 #20543)
with SMTP id <0F24009NWVB000@lmco.com>; Sun, 8 Nov 1998 19:37:49 -0700 (MST)
Received: from lmco.com by wdl1.wdl.lmco.com (SMI-8.6/WDL-5.0) id SAA12033; Sun, 08 Nov 1998 18:37:40 -0800
Date: Sun, 08 Nov 1998 18:37:55 -0800
From: "George W. Dinolt" <george.w.dinolt@lmco.com>
Subject: Re: Boot Loader question
To: Mike Smith <mike@smith.net.au>
Cc: freebsd-current@FreeBSD.ORG, rnordier@nordier.com
Message-id: <36465583.E523F26E@lmco.com>
Organization: Lockheed Martin Western Development Labs
MIME-version: 1.0
X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
References: <199811070750.XAA00452@dingo.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike and Robert:
Many thanks for your responses to my message.
Mike Smith wrote:
> ...
> Ok. Have you considered something like this:
>
> set choice=1
> echo "1 - FreeBSD 2.2"
> echo "2 - FreeBSD-current"
> read -t 10 -p "Select >>" choice
> set currdev=disk${choice}s1a:
> source /boot/boot.conf2
>
> in the default boot.conf, and then the 'real' boot instructions in
> /boot/boot.conf2?
I have taken your suggestion and a have a version which boots off of wd0
(my first disk) and takes the appropriate default action when I don't
type something in. Many thanks.
> ...
> However, to help you we need to know *what* the error is.
After the latest patches available via CTM (src-cur.3611)
with the following "Id's"
$Id: boot1.s,v 1.4 1998/11/05 20:52:25 rnordier Exp $
$Id: boot2.c,v 1.13 1998/10/27 20:16:36 rnordier Exp $
I create a floppy with the following set of commands:
fdformat /dev/fd0.1440
disklabel -w -r fd0 fd1440
disklabel -B -b /boot/boot1 -s /boot/boot2 /dev/fd0
newfs rfd0 fd1440
mount /dev/fd0 /floppy
mkdir /floppy/boot
cp /boot/{boot1,boot2,loader} /floppy/boot
cd /floppy
echo boot/loader > boot.config
When I boot from this floppy I get the error message:
Read error
Hit return to reboot:
If I follow the instructions, the floppy light goes on briefly and the
"Hit return..." message is reprinted on a new line.
If I remove the floppy and hit return (error messages still on screen),
I get my usual
F1 ...
F2 ...
F3 ...
messages and everything works as expected, that is I can boot.
Robert Nordier wrote:
...
>Since you use floppies, and get reproducible errors now, it'd be great
>if you'd undertake to test the new bootblocks and let us now if the
>problem has been resolved.
...
Glad to help. Unfortunately, I live behind a very restrictive firewall
and get my updates via CTM so I am usually a day or so behind the direct
CVS paths. I will keep you posted.
Regards,
George Dinolt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 18:56:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA27508
for freebsd-current-outgoing; Sun, 8 Nov 1998 18:56:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27499;
Sun, 8 Nov 1998 18:56:26 -0800 (PST)
(envelope-from dmm125@bellatlantic.net)
Received: from bellatlantic.net (client201-122-109.bellatlantic.net [151.201.122.109])
by iconmail.bellatlantic.net (IConNet Sendmail) with ESMTP id VAA12788;
Sun, 8 Nov 1998 21:49:12 -0500 (EST)
Message-ID: <3646118E.FFF8013E@bellatlantic.net>
Date: Sun, 08 Nov 1998 21:47:58 +0000
From: Donn Miller <dmm125@bellatlantic.net>
X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-RELEASE i386)
MIME-Version: 1.0
To: David Dawes <dawes@rf900.physics.usyd.edu.au>
CC: ports@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: Ports/patches for X332servonly
References: <Pine.BSF.4.05.9811081054100.424-100000@localhost> <19981109123915.A21444@rf900.physics.usyd.edu.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
David Dawes wrote:
> On Sun, Nov 08, 1998 at 11:05:27AM +0000, Donn Miller wrote:
> >Just trying to find out if anyone did a port and/or patch for
> >X332servonly.tgz. It's like the full source for XFree86 but it doesn't
> >include the stuff for building shared libs. I need the source code so I
> >can modify it to make a driver for my chipset, which is unsupported.
> >
> >BTW, building XFree86 from sratch is pretty nasty. One minor change to
> >any of the config files in xc/config/cf sometimes throws the whole build
> >out of whack.
>
> That surprises you?
>
Well, actually, it was the X332servonly, which is missing the full lib sources
for the XFree86 dist., so I did
cp xf86site.def host.def
And did some changes to host.def. I noticed that if I changed certain things
in host.def, the "make World" command would spew out some major errors. Not
surprising, considering X332servonly is a subset of the full XF86 sources...
It was complaining about an oldX directory missing whenever I changed
something.
>
> >The shared/static libs build OK, but when it comes time to link all the
> >object files and libs together to produce the X-server, massive amounts of
> >errors about "undefined reference to ..." come pouring out like crazy.
> >This is in the subdir xc/programs/Xserver/hw...
> >
> >I tried building it w/out changing any source at first, just to see if it
> >would compile, and it won't compile. So anyone successfully built the
> >XFree86 servers from source on 3.0-R?
>
> Patches are required for FreeBSD/ELF (FreeBSD wasn't ELF when 3.3.2 was
> released). You should be able to use the patches in FreeBSD's XFree86
> port. Just ignore any that might be for files not included in
> X332servonly.tgz
>
> Or you could wait for a week or so for XFree86 3.3.3 which will include
> support for FreeBSD/ELF out of the box.
>
> BTW, what chipset are you planning to add support for?
>
I was going to try to build a driver for SiS 5597/5598. I heard that it might
included in the next release of XF86, but I just wanted to see if I could do
it on my own. Actually, even though the SiS 5598 is unsupported, I found that
using the driver for a related SiS chipset, 86c205, almost works.
The only thing is that there's this strange fuzziness/flickering in certain
areas of the screen. I thought that maybe it was because the VCO center freq.
was a little different than the sis 86c205. I suspected only minor changes to
the drivers were needed to give me a "less flickery" screen. Didn't certain
ATI chipsets have this problem?
I was maybe also hoping to hack the X-server code and do a little tweaking and
get some accelerated functions to work. Someone told me the reason that the
KDE window manager's problem not refreshing when windows are moved/resized was
do to a buggy X-server, and I hoped to correct this as well.
But if I did manage to make the X-server work better for my chipset, I would
definitely submit the patches to the XFree86 team. I realize that most people
don't have the time to make the perfect X-server for every chipset, so I
figured I have a lot of free time, I can dedicate a lot of it to tweaking and
perfecting the X-server code. (Not that I'm necessarily going to succeed, but
I'm definitely going to try).
Someone suggested I buy an X-server from Xi or just get a new video card. But
I don't believe in paying companies that kind of money when the X source is
available. With enough hacking on the freely available source, the sky's the
limit. :]
Thanks for getting back to me on this.
Donn
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 19:07:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA28653
for freebsd-current-outgoing; Sun, 8 Nov 1998 19:07:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from farm.farm.sperry-sun.com ([32.97.92.188])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28648
for <freebsd-current@FreeBSD.org>; Sun, 8 Nov 1998 19:07:17 -0800 (PST)
(envelope-from rich@FreeBSD.org)
Received: from rich.farm.sperry-sun.com (rich@rich.farm.sperry-sun.com [10.216.65.2])
by farm.farm.sperry-sun.com (8.9.1/8.9.1) with ESMTP id VAA12799
for <freebsd-current@FreeBSD.org>; Sun, 8 Nov 1998 21:07:01 -0600 (CST)
(envelope-from rich@FreeBSD.org)
Received: (from rich@localhost)
by rich.farm.sperry-sun.com (8.9.1/8.9.1) id VAA01881;
Sun, 8 Nov 1998 21:05:39 -0600 (CST)
(envelope-from rich@rich.farm.sperry-sun.com)
Date: Sun, 8 Nov 1998 21:05:39 -0600 (CST)
Message-Id: <199811090305.VAA01881@rich.farm.sperry-sun.com>
X-Authentication-Warning: rich.farm.sperry-sun.com: rich set sender to rich@rich.farm.sperry-sun.com using -f
From: Murphey <rich@FreeBSD.ORG>
To: freebsd-current@FreeBSD.ORG
Subject: vintage SNAPs?
Reply-to: rich@FreeBSD.ORG
References: <199811081918.LAA03047@dingo.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Does anyone know where to find a copy of 3.0-*-SNAP releases from
September or early October?
Thanks,
Rich
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 19:19:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA29728
for freebsd-current-outgoing; Sun, 8 Nov 1998 19:19:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29721
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 19:19:43 -0800 (PST)
(envelope-from psalzman@gamefish.pcola.gulf.net)
Received: from localhost (psalzman@localhost)
by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id DAA05774;
Mon, 9 Nov 1998 03:18:40 GMT
(envelope-from psalzman@gamefish.pcola.gulf.net)
Date: Mon, 9 Nov 1998 03:18:40 +0000 (GMT)
From: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
To: pal <pal@PaLaDiN7.ml.org>
cc: freebsd-current@FreeBSD.ORG, osa@freebsd.org.ru
Subject: Re: SSH 2.0.10 BUG? (!)
In-Reply-To: <Pine.BSF.4.05.9811082026240.316-100000@PaLaDiN7.ml.org>
Message-ID: <Pine.BSF.4.05.9811090314040.5722-100000@gamefish.pcola.gulf.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Thats odd, it sounds like it is not writing to the utmp
file. Hmm.. It did not have this problem on my machine.
--
Phillip Salzman
"See Spot do run. Good Spot. See Spot run Microsoft Windows
NT 4.0. See Spot crash. Bad Spot."
On Sun, 8 Nov 1998, pal wrote:
> Hi,
> I have FreeBSD 3.0 current, actualy I have current version only of
> /src/sys other from 3.0-RELEASE and ssh 2.0.10 installed on it.
>
> My friend Sergey Osokin (osa@freebsd.org.ru) discovered it when he
> connected to my FreeBSD box using SSH2 (veersion 2.0.10)
> same thing appears when I trying to connect to it from linux box at work
> using same ssh2. The user connected this
> way not showed up by finger and w/who utilities however ps aux| grep
> $username show processes they are running
> and netstat shows established connections, last showes user as logged in.
> However, further experiments showing that ssh1 clients connected to my box
> shows up fine in all those utilities.
>
> Best wishes,
> Gene
>
> P.S. bug submitted to SSH developers
>
>
> 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 Nov 8 19:28:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA00643
for freebsd-current-outgoing; Sun, 8 Nov 1998 19:28: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 TAA00624
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 19:27:52 -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 WAA11767;
Sun, 8 Nov 1998 22:27:35 -0500 (EST)
Date: Sun, 8 Nov 1998 22:27:35 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: garman@earthling.net
cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <199811090205.VAA10769@janus.syracuse.net>
Message-ID: <Pine.BSF.4.05.9811082226380.11650-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
Device 1K-blocks Used Avail Capacity Type
/dev/wd0s1b 102400 12300 89972 12% Interleaved
/dev/wd1s1b 102400 12408 89864 12% Interleaved
Total 204544 24708 179836 12%
This is normal usage after
swap_pager: suggest more swap space: 157 MB
swap_pager: out of swap space
pid 5795 (memory), uid 1000, was killed: out of swap space
Cheers,
Brian Feldman
On Sun, 8 Nov 1998 garman@earthling.net wrote:
> On 8 Nov, Brian Feldman wrote:
> > Yech, that really isn't good having your process's memory disappearing
> > under you... anyone have any idea why for instance I don't have this
> > problem, nor do many others?
> >
> whats your swap usage look like? this problem (for me at least) is
> much much more likely to occur with a (relatively) high amount of swap
> usage, usually in the 50-70% range (out of 150MB of swap)
>
> enjoy
> --
> Jason Garman http://garman.dyn.ml.org/
> Student, University of Maryland garman@earthling.net
> And now... did you know that: Whois: JAG145
> "If you fart consistently for 6 years and 9 months, enough gas is
> produced to create the energy of an atomic bomb." -- 0xdeadbeef posting
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 19:30:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA00818
for freebsd-current-outgoing; Sun, 8 Nov 1998 19:30:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00813
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 19:30:31 -0800 (PST)
(envelope-from psalzman@gamefish.pcola.gulf.net)
Received: from localhost (psalzman@localhost)
by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id DAA05817;
Mon, 9 Nov 1998 03:29:25 GMT
(envelope-from psalzman@gamefish.pcola.gulf.net)
Date: Mon, 9 Nov 1998 03:29:25 +0000 (GMT)
From: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
To: pal <pal@PaLaDiN7.ml.org>
cc: sporkl@ix.netcom.com, freebsd-current@FreeBSD.ORG, osa@freebsd.org.ru
Subject: Re: SSH 2.0.10 BUG? (!)
In-Reply-To: <Pine.BSF.4.05.9811082130270.316-100000@PaLaDiN7.ml.org>
Message-ID: <Pine.BSF.4.05.9811090329010.5722-100000@gamefish.pcola.gulf.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
make it +s
--
Phillip Salzman
"I have three, but you cannot have any."
On Sun, 8 Nov 1998, pal wrote:
> its:
>
> -rwxr-xr-x 1 root wheel 1310188 28 20:57 sshd2
>
> On Sun, 8 Nov 1998, Spike Gronim wrote:
>
> > On Sun, 8 Nov 1998, pal wrote:
> [skiped]
> >
> >
> > Could it be incorrectly set permissions on your sshd binary? I encountered
> > similar problems with my xterms, untill I changed the permissions to
> > -rwsr-xr-x.
> >
> > -Spike Gronim
> > sporkl@ix.netcom.com
> >
> >
> > The majority only rules those who let them.
> >
> >
> > 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
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 19:44:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA02077
for freebsd-current-outgoing; Sun, 8 Nov 1998 19:44:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alive.znep.com (207-178-54-226.go2net.com [207.178.54.226])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02069
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 19:44:52 -0800 (PST)
(envelope-from marcs@znep.com)
Received: from localhost (marcs@localhost)
by alive.znep.com (8.9.1/8.9.1) with ESMTP id TAA09032;
Sun, 8 Nov 1998 19:39:14 -0800 (PST)
(envelope-from marcs@znep.com)
Date: Sun, 8 Nov 1998 19:39:14 -0800 (PST)
From: Marc Slemko <marcs@znep.com>
To: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
cc: pal <pal@PaLaDiN7.ml.org>, sporkl@ix.netcom.com,
freebsd-current@FreeBSD.ORG, osa@freebsd.org.ru
Subject: Re: SSH 2.0.10 BUG? (!)
In-Reply-To: <Pine.BSF.4.05.9811090329010.5722-100000@gamefish.pcola.gulf.net>
Message-ID: <Pine.BSF.4.05.9811081938100.8174-100000@alive.znep.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, 9 Nov 1998, Phillip Salzman wrote:
> make it +s
DO NOT.
Doing so would quite possibly introduce a major security hole. Very few
daemons are designed to have the setuid bit set, for the simple reason
that if they have to be root they are normally already root.
> On Sun, 8 Nov 1998, pal wrote:
>
> > its:
> >
> > -rwxr-xr-x 1 root wheel 1310188 28 20:57 sshd2
[...]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 19:54:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA02832
for freebsd-current-outgoing; Sun, 8 Nov 1998 19:54: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 TAA02825;
Sun, 8 Nov 1998 19:54: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 OAA10814;
Mon, 9 Nov 1998 14:23:53 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.1/8.9.0) id OAA11179;
Mon, 9 Nov 1998 14:23:52 +1030 (CST)
Message-ID: <19981109142351.E499@freebie.lemis.com>
Date: Mon, 9 Nov 1998 14:23:51 +1030
From: Greg Lehey <grog@lemis.com>
To: rich@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: Re: vintage SNAPs?
References: <199811081918.LAA03047@dingo.cdrom.com> <199811090305.VAA01881@rich.farm.sperry-sun.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199811090305.VAA01881@rich.farm.sperry-sun.com>; from Murphey on Sun, Nov 08, 1998 at 09:05:39PM -0600
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, 8 November 1998 at 21:05:39 -0600, Murphey wrote:
>
> Does anyone know where to find a copy of 3.0-*-SNAP releases from
> September or early October?
Can't you just check one out from the repository?
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 Nov 8 20:17:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA05992
for freebsd-current-outgoing; Sun, 8 Nov 1998 20:17: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 UAA05987
for <current@FreeBSD.ORG>; Sun, 8 Nov 1998 20:17:38 -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 XAA13563;
Sun, 8 Nov 1998 23:17:00 -0500 (EST)
(envelope-from wollman)
Date: Sun, 8 Nov 1998 23:17:00 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199811090417.XAA13563@khavrinen.lcs.mit.edu>
To: dg@root.com
Cc: Eivind Eklund <eivind@yes.no>, John Fieber <jfieber@indiana.edu>,
current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <199811081517.HAA03267@root.com>
References: <19981108160934.30826@follo.net>
<199811081517.HAA03267@root.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Sun, 08 Nov 1998 07:17:11 -0800, David Greenman <dg@root.com> said:
> brk(2) will fail and return ENOMEM if the system is low on swap space. If
> the application (phk malloc or the caller of malloc?) isn't prepared for this,
> it may end up with a NULL pointer that it doesn't expect - perhaps not even
> tripping over it until sometime later.
Totally unrelated to the problem. It seems, so far as I was able to
characterize, to happen to daemons which are *swapped out* at the time
of the memory shortage. If it's active enough to still be in core, it
doesn't get spammed.
-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 Nov 8 20:23:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA06480
for freebsd-current-outgoing; Sun, 8 Nov 1998 20:23:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06472
for <freebsd-current@FreeBSD.ORG>; Sun, 8 Nov 1998 20:23:21 -0800 (PST)
(envelope-from psalzman@gamefish.pcola.gulf.net)
Received: from localhost (psalzman@localhost)
by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id EAA06066;
Mon, 9 Nov 1998 04:22:11 GMT
(envelope-from psalzman@gamefish.pcola.gulf.net)
Date: Mon, 9 Nov 1998 04:22:11 +0000 (GMT)
From: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
To: Marc Slemko <marcs@znep.com>
cc: pal <pal@PaLaDiN7.ml.org>, sporkl@ix.netcom.com,
freebsd-current@FreeBSD.ORG, osa@freebsd.org.ru
Subject: Re: SSH 2.0.10 BUG? (!)
In-Reply-To: <Pine.BSF.4.05.9811081938100.8174-100000@alive.znep.com>
Message-ID: <Pine.BSF.4.05.9811090421540.6059-100000@gamefish.pcola.gulf.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
True. I wonder why it isn't writing to the utmp file...
On Sun, 8 Nov 1998, Marc Slemko wrote:
> On Mon, 9 Nov 1998, Phillip Salzman wrote:
>
> > make it +s
>
> DO NOT.
>
> Doing so would quite possibly introduce a major security hole. Very few
> daemons are designed to have the setuid bit set, for the simple reason
> that if they have to be root they are normally already root.
>
> > On Sun, 8 Nov 1998, pal wrote:
> >
> > > its:
> > >
> > > -rwxr-xr-x 1 root wheel 1310188 28 20:57 sshd2
> [...]
>
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 20:28:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA06907
for freebsd-current-outgoing; Sun, 8 Nov 1998 20:28:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06899;
Sun, 8 Nov 1998 20:28:25 -0800 (PST)
(envelope-from andyf@speednet.com.au)
Received: from localhost (andyf@localhost)
by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id PAA04066;
Mon, 9 Nov 1998 15:27:57 +1100 (EST)
X-Authentication-Warning: backup.zippynet.iol.net.au: andyf owned process doing -bs
Date: Mon, 9 Nov 1998 15:27:51 +1100 (EST)
From: Andy Farkas <andyf@speednet.com.au>
X-Sender: andyf@backup.zippynet.iol.net.au
To: rich@FreeBSD.ORG
cc: freebsd-current@FreeBSD.ORG
Subject: Re: vintage SNAPs?
In-Reply-To: <19981109142351.E499@freebie.lemis.com>
Message-ID: <Pine.BSF.4.05.9811091525580.4036-100000@backup.zippynet.iol.net.au>
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, 9 Nov 1998, Greg Lehey wrote:
> > Does anyone know where to find a copy of 3.0-*-SNAP releases from
> > September or early October?
>
> Can't you just check one out from the repository?
>
Check the FreeBSD 'Projects' page (http://www.freebsd.org/projects/)
About 7 links down id the "RELEASE/SNAP Finder" ...
--
:{ andyf@speednet.com.au
Andy Farkas
System Administrator
Speed Internet Services
http://www.speednet.com.au/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 20:33:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA07453
for freebsd-current-outgoing; Sun, 8 Nov 1998 20:33:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07428;
Sun, 8 Nov 1998 20:33:01 -0800 (PST)
(envelope-from andyf@speednet.com.au)
Received: from localhost (andyf@localhost)
by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id PAA04077;
Mon, 9 Nov 1998 15:32:42 +1100 (EST)
X-Authentication-Warning: backup.zippynet.iol.net.au: andyf owned process doing -bs
Date: Mon, 9 Nov 1998 15:32:32 +1100 (EST)
From: Andy Farkas <andyf@speednet.com.au>
X-Sender: andyf@backup.zippynet.iol.net.au
To: rich@FreeBSD.ORG
cc: freebsd-current@FreeBSD.ORG
Subject: Re: vintage SNAPs?
In-Reply-To: <Pine.BSF.4.05.9811091525580.4036-100000@backup.zippynet.iol.net.au>
Message-ID: <Pine.BSF.4.05.9811091532280.4036-100000@backup.zippynet.iol.net.au>
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, 9 Nov 1998, Andy Farkas wrote:
> Date: Mon, 9 Nov 1998 15:27:51 +1100 (EST)
> From: Andy Farkas <andyf@speednet.com.au>
> To: rich@FreeBSD.ORG
> Cc: freebsd-current@FreeBSD.ORG
> Subject: Re: vintage SNAPs?
>
>
> On Mon, 9 Nov 1998, Greg Lehey wrote:
>
> > > Does anyone know where to find a copy of 3.0-*-SNAP releases from
> > > September or early October?
> >
> > Can't you just check one out from the repository?
> >
>
> Check the FreeBSD 'Projects' page (http://www.freebsd.org/projects/)
>
> About 7 links down id the "RELEASE/SNAP Finder" ...
>
>
>
--
:{ andyf@speednet.com.au
Andy Farkas
System Administrator
Speed Internet Services
http://www.speednet.com.au/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 20:38:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA07903
for freebsd-current-outgoing; Sun, 8 Nov 1998 20:38:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rufus.comms.unsw.EDU.AU (rufus.comms.unsw.EDU.AU [149.171.96.100])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07871;
Sun, 8 Nov 1998 20:38:30 -0800 (PST)
(envelope-from c.day@student.unsw.edu.au)
Received: from lab_machine ([129.94.222.69]) by rufus.comms.unsw.EDU.AU (8.8.8/8.7.5.kenso-central) with SMTP id PAA10873; Mon, 9 Nov 1998 15:34:54 +1100 (EST)
Message-Id: <3.0.5.32.19981109150346.00931d20@pop3.student.unsw.edu.au>
X-Sender: z2172268@pop3.student.unsw.edu.au
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Mon, 09 Nov 1998 15:03:46 +1000
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>,
FreeBSD Current <current@FreeBSD.ORG>,
FreeBSD Hackers <hackers@FreeBSD.ORG>
From: chris day <c.day@student.unsw.edu.au>
Subject: Re: AWE-32
In-Reply-To: <XFMail.981108120955.asmodai@wxs.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
When you boot, go into kernel config, then at the prompt type
pnp 1 0 os enable port0 0x220 port1 0x330 irq0 5 drq0 1 drq1 5
pnp 1 2 os enable port0 0x620 port1 0xa20 port2 0xe20
This is the PnP strings for my PnP AWE64, the only difference with mine is
that I also add 'port2 0x388' to the first line for the OPL.
Anyways hopefully this should work.
regards, chris
>Probing for PnP devices:
>CSN 1 Vendor ID: CTL009c [0x9c008c0e] Serial 0x10046cf4 Comp ID: PNP0600
>[0x0006d041]
>
>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
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 8 22:57:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA18976
for freebsd-current-outgoing; Sun, 8 Nov 1998 22:57:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18971
for <current@freebsd.org>; Sun, 8 Nov 1998 22:57:21 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id CAA22061
for <current@freebsd.org>; Mon, 9 Nov 1998 02:00:09 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Mon, 9 Nov 1998 02:00:09 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: current@FreeBSD.ORG
Subject: newer gcc?
Message-ID: <Pine.BSF.4.05.9811090157020.19817-100000@porkfriedrice.ny.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
Has there been any thought to jumping to a newer version of gcc,
specifically egcs?
Also if one was to integrate egcs into the source tree what "stage" would
be integrated? What i mean is that egcs does a whole bunch of odd things
to get itself built, would only the last pass be done in freebsd'd build?
or how far back in the build should the integrated source start?
What i mean is definetly post-configure but before.... what?
Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com
-- There are operating systems, and then there's FreeBSD.
-- http://www.freebsd.org/ 3.0-current
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 00:19:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA26988
for freebsd-current-outgoing; Mon, 9 Nov 1998 00:19:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from enterprise.sl.ru (enterprise.sl.ru [195.16.101.4] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA26977
for <current@freebsd.org>; Mon, 9 Nov 1998 00:19:04 -0800 (PST)
(envelope-from tarkhil@synchroline.ru)
Received: from enterprise.sl.ru (tarkhil@localhost.synchroline.ru [127.0.0.1])
by enterprise.sl.ru (8.9.1/8.8.8) with ESMTP id LAA04657
for <current@freebsd.org>; Mon, 9 Nov 1998 11:20:03 +0300 (MSK)
(envelope-from tarkhil@enterprise.sl.ru)
Message-Id: <199811090820.LAA04657@enterprise.sl.ru>
X-Mailer: exmh version 2.0.2 2/24/98
To: current@FreeBSD.ORG
Reply-To: tarkhil@synchroline.ru
Subject: weird problem - maybe in my head?
X-URL: http://freebsd.svib.ru
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 09 Nov 1998 11:20:02 +0300
From: "Alexander B. Povolotsky" <tarkhil@synchroline.ru>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello!
On machine running
FreeBSD satellite.megabit7.ru 3.0-19980804-SNAP FreeBSD 3.0-19980804-SNAP #5:
Mon Nov 2 13:31:21 MSK 1998 root@satellite.megabit7.ru:/usr/src/sys/compil
e/SYNC i386
as well as FreeBSD-Current
I've got the following error (100% repeatable!!!):
Attempt to get by ftp (via proxy or not, usnig wget, lynx, ftp, ncftp3) file
boot.flp (pathname doesn't mean) result in fetching about 10000 bytes (ftom
9288 to 10136), and after that point NOTHING is transferred. Server doesn't
matter.
Gzipping file helped at once. Renaming file didn't, so something in that file
must make my IP stack (or what???) crazy.
I know it is weird, but I have no more clues...
Alex.
--
Alexander B. Povolotsky, System Administrator
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 00:23:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA27608
for freebsd-current-outgoing; Mon, 9 Nov 1998 00:23:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from foobar.franken.de (foobar.franken.de [194.94.249.81])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA27596
for <freebsd-current@FreeBSD.ORG>; Mon, 9 Nov 1998 00:23:06 -0800 (PST)
(envelope-from logix@foobar.franken.de)
Received: (from logix@localhost)
by foobar.franken.de (8.8.8/8.8.5) id JAA22486;
Mon, 9 Nov 1998 09:20:01 +0100 (CET)
Message-ID: <19981109091957.A22438@foobar.franken.de>
Date: Mon, 9 Nov 1998 09:19:57 +0100
From: Harold Gutch <logix@foobar.franken.de>
To: Marc Slemko <marcs@znep.com>,
Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
Cc: pal <pal@PaLaDiN7.ml.org>, sporkl@ix.netcom.com,
freebsd-current@FreeBSD.ORG, osa@freebsd.org.ru
Subject: Re: SSH 2.0.10 BUG? (!)
References: <Pine.BSF.4.05.9811090329010.5722-100000@gamefish.pcola.gulf.net> <Pine.BSF.4.05.9811081938100.8174-100000@alive.znep.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.05.9811081938100.8174-100000@alive.znep.com>; from Marc Slemko on Sun, Nov 08, 1998 at 07:39:14PM -0800
X-Organisation: BatmanSystemDistribution
X-Mission: To free the world from the Penguin
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 08, 1998 at 07:39:14PM -0800, Marc Slemko wrote:
> On Mon, 9 Nov 1998, Phillip Salzman wrote:
> > make it +s
>
> DO NOT.
>
> Doing so would quite possibly introduce a major security hole. Very few
> daemons are designed to have the setuid bit set, for the simple reason
> that if they have to be root they are normally already root.
>
sshd has to run as root if you want to be able to login as more
than the user it runs as. What difference should an suid-bit make
if it belongs to root and it's run by root anyway ? Not that it
would be of any use, I just don't see how it should do any harm
or even "indroduce a major security hole".
Other than that sshd doesn't have an suid bit set on any system I
know of, but it does write the users which login to utmp. I have
never used sshd2 though, so perhaps it is a bug in sshd2.
> > On Sun, 8 Nov 1998, pal wrote:
> >
> > > its:
> > >
> > > -rwxr-xr-x 1 root wheel 1310188 28 20:57 sshd2
--
bye, logix
<Shabby> Sleep is an abstinence syndrome wich occurs due to lack of caffein.
Wed Mar 4 04:53:33 CET 1998 #unix, ircnet
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 00:33:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA28693
for freebsd-current-outgoing; Mon, 9 Nov 1998 00:33:01 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.oeno.com (ns.oeno.com [194.100.99.145])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA28688
for <current@freebsd.org>; Mon, 9 Nov 1998 00:32:59 -0800 (PST)
(envelope-from will@ns.oeno.com)
Received: (qmail 10485 invoked by uid 1001); 9 Nov 1998 08:32:43 -0000
Date: 9 Nov 1998 08:32:43 -0000
Message-ID: <19981109083243.10482.qmail@ns.oeno.com>
From: Ville-Pertti Keinonen <will@iki.fi>
To: james@westongold.com
CC: james@westongold.com, current@FreeBSD.ORG
In-reply-to: <32BABEF63EAED111B2C5204C4F4F5020180A@WGP01> (message from James
Mansion on Fri, 6 Nov 1998 08:56:36 -0000)
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Which was my point really. I'd rather waste the VM space and make the
> context switch more costly than have pthread_self and
> pthread_[sg]etspecific make kernel calls. Context switching is
> somewhat infrequent after all. If its not, the efficiency of these
> APIs is hardly your biggest worry.
I certainly was not suggesting putting anything like pthread_self in
the kernel. In fact almost any kludge would be preferable to that.
But there are better ways than what you were suggesting.
...
> It does mean that the page maps for multiple kernel threads executing in
> a process need to be different OR that a register is used somehow.
Here I'd probably vote for the segment register approach.
> As an application programmer it doesn't seem to matter, though as a
> C/C++ programmer I guess I'd rather see the dedicated use of a segment
> register since it seems likely to give the best performance and I'm
> not using them directly anyway. But I guess that's a whole ABI change.
...
Not an evil change, though, it would hardly break anything.
> Huh? I'm asking for pthread_*_[sg]etpshared, for P1003.1-1996. Are you
> objecting to them in principal?
No, you didn't mention that was what you meant.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 00:36:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA29261
for freebsd-current-outgoing; Mon, 9 Nov 1998 00:36:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from foobar.franken.de (foobar.franken.de [194.94.249.81])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29253
for <freebsd-current@FreeBSD.ORG>; Mon, 9 Nov 1998 00:36:48 -0800 (PST)
(envelope-from logix@foobar.franken.de)
Received: (from logix@localhost)
by foobar.franken.de (8.8.8/8.8.5) id JAA22519;
Mon, 9 Nov 1998 09:34:59 +0100 (CET)
Message-ID: <19981109093459.B22438@foobar.franken.de>
Date: Mon, 9 Nov 1998 09:34:59 +0100
From: Harold Gutch <logix@foobar.franken.de>
To: Marc Slemko <marcs@znep.com>,
Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
Cc: pal <pal@PaLaDiN7.ml.org>, sporkl@ix.netcom.com,
freebsd-current@FreeBSD.ORG, osa@freebsd.org.ru
Subject: Re: SSH 2.0.10 BUG? (!)
References: <Pine.BSF.4.05.9811090329010.5722-100000@gamefish.pcola.gulf.net> <Pine.BSF.4.05.9811081938100.8174-100000@alive.znep.com> <19981109091957.A22438@foobar.franken.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <19981109091957.A22438@foobar.franken.de>; from Harold Gutch on Mon, Nov 09, 1998 at 09:19:57AM +0100
X-Organisation: BatmanSystemDistribution
X-Mission: To free the world from the Penguin
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Nov 09, 1998 at 09:19:57AM +0100, Harold Gutch wrote:
> On Sun, Nov 08, 1998 at 07:39:14PM -0800, Marc Slemko wrote:
> > On Mon, 9 Nov 1998, Phillip Salzman wrote:
> > > make it +s
> >
> > DO NOT.
> >
> > Doing so would quite possibly introduce a major security hole. Very few
> > daemons are designed to have the setuid bit set, for the simple reason
> > that if they have to be root they are normally already root.
> >
> sshd has to run as root if you want to be able to login as more
> than the user it runs as. What difference should an suid-bit make
> if it belongs to root and it's run by root anyway ? Not that it
> would be of any use, I just don't see how it should do any harm
> or even "indroduce a major security hole".
>
Sorry, forget this argumentation, I somehow assumed sshd would
only be run once at startup and that was it.
I guess users can run sshd later on too without any problems and
yes, a suid bit probably will give them more privileges in this
case.
--
bye, logix
<Shabby> Sleep is an abstinence syndrome wich occurs due to lack of caffein.
Wed Mar 4 04:53:33 CET 1998 #unix, ircnet
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 00:47:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA29877
for freebsd-current-outgoing; Mon, 9 Nov 1998 00:47:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m1-60-dbn.dial-up.net [196.34.155.60])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29872
for <freebsd-current@FreeBSD.ORG>; Mon, 9 Nov 1998 00:47:31 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id KAA05474; Mon, 9 Nov 1998 10:45:17 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199811090845.KAA05474@ceia.nordier.com>
Subject: Re: Boot Loader question
In-Reply-To: <36465583.E523F26E@lmco.com> from "George W. Dinolt" at "Nov 8, 98 06:37:55 pm"
To: george.w.dinolt@lmco.com (George W. Dinolt)
Date: Mon, 9 Nov 1998 10:45:13 +0200 (SAT)
Cc: mike@smith.net.au, 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
George W. Dinolt wrote:
[ ... ]
> After the latest patches available via CTM (src-cur.3611)
> with the following "Id's"
> $Id: boot1.s,v 1.4 1998/11/05 20:52:25 rnordier Exp $
> $Id: boot2.c,v 1.13 1998/10/27 20:16:36 rnordier Exp $
>
> I create a floppy with the following set of commands:
>
> fdformat /dev/fd0.1440
> disklabel -w -r fd0 fd1440
> disklabel -B -b /boot/boot1 -s /boot/boot2 /dev/fd0
> newfs rfd0 fd1440
> mount /dev/fd0 /floppy
> mkdir /floppy/boot
> cp /boot/{boot1,boot2,loader} /floppy/boot
> cd /floppy
> echo boot/loader > boot.config
>
> When I boot from this floppy I get the error message:
>
> Read error
> Hit return to reboot:
[ ... ]
Thanks for the detailed response.
A number of changes to boot1/boot2 were committed yesterday, and it
would be interesting to know whether these resolve the problem.
The most recent revisions are:
boot1.s 1.5
boot2.c 1.16
--
Robert Nordier
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 00:49:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA00291
for freebsd-current-outgoing; Mon, 9 Nov 1998 00:49:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00271;
Mon, 9 Nov 1998 00:49:00 -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 TAA14661;
Mon, 9 Nov 1998 19:48:32 +1100
Date: Mon, 9 Nov 1998 19:48:32 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811090848.TAA14661@godzilla.zeta.org.au>
To: bde@zeta.org.au, peter@netplex.com.au
Subject: Re: Dog Sloooow SMP
Cc: current@FreeBSD.ORG, jc@irbs.com, mike@smith.net.au, smp@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> It's only OK for MII's because of various `#if 0's and `#ifdef SMP's
>> that prevent non-OK code from running on MII's.
>
>I think it should be CPU specific, not cpu class specific. The
>model-specific-registers are very specific to the Intel family. I'd be a
>lot happier if it was 'if (cpu == CPU_686 || cpu == CPU_PII) ...' Of
>course, feature tests would be better. 'if (cpu_features & CF_PPRO_MSR)...'
>The problem is that there is a 'cpu_feature' already for the CPUID. We
>need more general flags than what Intel choose to tell us.
FreeBSD should use its own bitmap of capabilities and not test the Intel
flags except once to translate them. 32 general flags might even be
enough.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 01:19:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA03241
for freebsd-current-outgoing; Mon, 9 Nov 1998 01:19:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from trifork.gu.net (trifork.gu.net [194.93.191.246])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03225
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 01:19:48 -0800 (PST)
(envelope-from fbsd@trifork.gu.net)
Received: from localhost (localhost.gu.net [127.0.0.1])
by trifork.gu.net (8.9.1/8.9.1) with ESMTP id LAA00666;
Mon, 9 Nov 1998 11:18:43 +0200 (EET)
(envelope-from fbsd@trifork.gu.net)
Date: Mon, 9 Nov 1998 11:18:43 +0200 (EET)
From: Andrew Stesin <fbsd@trifork.gu.net>
Reply-To: fbsd@trifork.gu.net
To: "Alexander B. Povolotsky" <tarkhil@synchroline.ru>
cc: current@FreeBSD.ORG
Subject: Re: weird problem - maybe in my head?
In-Reply-To: <199811090820.LAA04657@enterprise.sl.ru>
Message-ID: <Pine.BSF.4.05.9811091106420.311-100000@trifork.gu.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, 9 Nov 1998, Alexander B. Povolotsky wrote:
> boot.flp (pathname doesn't mean) result in fetching about 10000 bytes (ftom
> 9288 to 10136), and after that point NOTHING is transferred. Server doesn't
> matter.
Which boot.flp exactly? what kind of network connection?
what network hardware is in use? how sysctl variables for TCP are set?
I've just tried 3.0-19981103-SNAP boot.flp from releng22,
it works perfectly for me via ep0 ethernet.
Maybe you have a braindamaged ISND TA or CSU/DSU or sattelite
modem somewhere on your way? I recall some troubles like yours
were due to crazy hardware.
trifork# uname -a
FreeBSD trifork.gu.net 3.0-19981020-SNAP FreeBSD 3.0-19981020-SNAP #3: Wed Oct 2
8 15:30:48 EET 1998 root@trifork.gu.net:/usr/src/sys/compile/TRIFORK i386
trifork#
--
Best regards,
Andrew Stesin
nic-hdl: ST73-RIPE
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 01:38:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA05837
for freebsd-current-outgoing; Mon, 9 Nov 1998 01:38:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05819;
Mon, 9 Nov 1998 01:38:26 -0800 (PST)
(envelope-from narvi@haldjas.folklore.ee)
Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged))
by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP
id LAA26286; Mon, 9 Nov 1998 11:36:52 +0200 (EET)
Date: Mon, 9 Nov 1998 11:36:51 +0200 (EET)
From: Narvi <narvi@haldjas.folklore.ee>
To: Bruce Evans <bde@zeta.org.au>
cc: peter@netplex.com.au, current@FreeBSD.ORG, jc@irbs.com, mike@smith.net.au,
smp@FreeBSD.ORG
Subject: Re: Dog Sloooow SMP
In-Reply-To: <199811090848.TAA14661@godzilla.zeta.org.au>
Message-ID: <Pine.BSF.3.96.981109113234.5111D-100000@haldjas.folklore.ee>
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, 9 Nov 1998, Bruce Evans wrote:
> >> It's only OK for MII's because of various `#if 0's and `#ifdef SMP's
> >> that prevent non-OK code from running on MII's.
> >
> >I think it should be CPU specific, not cpu class specific. The
> >model-specific-registers are very specific to the Intel family. I'd be a
> >lot happier if it was 'if (cpu == CPU_686 || cpu == CPU_PII) ...' Of
> >course, feature tests would be better. 'if (cpu_features & CF_PPRO_MSR)...'
> >The problem is that there is a 'cpu_feature' already for the CPUID. We
> >need more general flags than what Intel choose to tell us.
>
> FreeBSD should use its own bitmap of capabilities and not test the Intel
> flags except once to translate them. 32 general flags might even be
> enough.
>
How about 64 for the odd case that K7 actually materialises as promised
and people start putting them in dual motherboards?
Or will that (SMP support for EV7 like systems) resolved with support for
SMP Alpha?
> Bruce
Sander
There is no love, no good, no happiness and no future -
all these are just illusions.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 02:22:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA10265
for freebsd-current-outgoing; Mon, 9 Nov 1998 02:22:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10247;
Mon, 9 Nov 1998 02:22:47 -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 VAA22031;
Mon, 9 Nov 1998 21:22:30 +1100
Date: Mon, 9 Nov 1998 21:22:30 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811091022.VAA22031@godzilla.zeta.org.au>
To: bde@zeta.org.au, narvi@haldjas.folklore.ee
Subject: Re: Dog Sloooow SMP
Cc: current@FreeBSD.ORG, jc@irbs.com, mike@smith.net.au, peter@netplex.com.au,
smp@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> FreeBSD should use its own bitmap of capabilities and not test the Intel
>> flags except once to translate them. 32 general flags might even be
>> enough.
>>
>
>How about 64 for the odd case that K7 actually materialises as promised
>and people start putting them in dual motherboards?
That would be almost twice as slow for CC=gcc. CC=egcs handles 64-bit
bit tests better, especially for the low 32 bits.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 02:38:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA12124
for freebsd-current-outgoing; Mon, 9 Nov 1998 02:38:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from enterprise.sl.ru (enterprise.sl.ru [195.16.101.4] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12069
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 02:38:27 -0800 (PST)
(envelope-from tarkhil@synchroline.ru)
Received: from enterprise.sl.ru (tarkhil@localhost.synchroline.ru [127.0.0.1])
by enterprise.sl.ru (8.9.1/8.8.8) with ESMTP id NAA05060;
Mon, 9 Nov 1998 13:37:44 +0300 (MSK)
(envelope-from tarkhil@enterprise.sl.ru)
Message-Id: <199811091037.NAA05060@enterprise.sl.ru>
X-Mailer: exmh version 2.0.2 2/24/98
To: fbsd@trifork.gu.net
cc: current@FreeBSD.ORG
Subject: Re: weird problem - maybe in my head?
In-reply-to: Your message "Mon, 09 Nov 1998 11:18:43 +0200."
<Pine.BSF.4.05.9811091106420.311-100000@trifork.gu.net>
Reply-To: tarkhil@synchroline.ru
X-URL: http://freebsd.svib.ru
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 09 Nov 1998 13:37:43 +0300
From: "Alexander B. Povolotsky" <tarkhil@synchroline.ru>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<Pine.BSF.4.05.9811091106420.311-100000@trifork.gu.net>Andrew Stesin writes:
>> boot.flp (pathname doesn't mean) result in fetching about 10000 bytes (ftom
>> 9288 to 10136), and after that point NOTHING is transferred. Server doesn't
>> matter.
>
> Which boot.flp exactly? what kind of network connection?
> what network hardware is in use? how sysctl variables for TCP are set?
> Maybe you have a braindamaged ISND TA or CSU/DSU or sattelite
> modem somewhere on your way? I recall some troubles like yours
> were due to crazy hardware.
YES :-E Livingston Portmaster is The Crazy Thing. Sorry :-(
Alex
--
Alexander B. Povolotsky, System Administrator
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 03:24:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA16525
for freebsd-current-outgoing; Mon, 9 Nov 1998 03:24:48 -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 DAA16501;
Mon, 9 Nov 1998 03:24:43 -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.1/8.9.1/Spinner) with ESMTP id TAA29164;
Mon, 9 Nov 1998 19:21:41 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811091121.TAA29164@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bruce Evans <bde@zeta.org.au>
cc: narvi@haldjas.folklore.ee, current@FreeBSD.ORG, jc@irbs.com,
mike@smith.net.au, smp@FreeBSD.ORG
Subject: Re: Dog Sloooow SMP
In-reply-to: Your message of "Mon, 09 Nov 1998 21:22:30 +1100."
<199811091022.VAA22031@godzilla.zeta.org.au>
Date: Mon, 09 Nov 1998 19:21:40 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Bruce Evans wrote:
> >> FreeBSD should use its own bitmap of capabilities and not test the Intel
> >> flags except once to translate them. 32 general flags might even be
> >> enough.
> >>
> >
> >How about 64 for the odd case that K7 actually materialises as promised
> >and people start putting them in dual motherboards?
>
> That would be almost twice as slow for CC=gcc. CC=egcs handles 64-bit
> bit tests better, especially for the low 32 bits.
32 vs. 64 is almost irrelevant.. There's no limit to the number of 32 bit
variables that we can use with flags in them, so there's no reason why
we'd use a 64 bit variable in the first place.
However.. One thing that bugs me is that we presently can optimize out
code and tests for a runtime boost when compiled for a specific cpu. eg:
if we support 386 cpus, we test for whether we have an invlpg instruction
or not - but if we are not compiling with a 386 option then this code and
the test for >= 486 goes away.
> 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 Mon Nov 9 03:44:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA18762
for freebsd-current-outgoing; Mon, 9 Nov 1998 03:44:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from post.mail.demon.net (post-12.mail.demon.net [194.217.242.41])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18757;
Mon, 9 Nov 1998 03:44:15 -0800 (PST)
(envelope-from marko@uk.radan.com)
Received: from [158.152.75.22] (helo=uk.radan.com)
by post.mail.demon.net with smtp (Exim 2.05demon1 #1)
id 0zcpjh-00007l-00; Mon, 9 Nov 1998 11:43:58 +0000
Organisation: Radan Computational Ltd., Bath, UK.
Phone: +44-1225-320320 Fax: +44-1225-320311
Received: from beavis.uk.radan.com (beavis [193.114.228.122]) by uk.radan.com (8.6.10/8.6.10) with SMTP id LAA00304; Mon, 9 Nov 1998 11:40:48 GMT
Received: from uk.radan.com (gppsun4) by beavis.uk.radan.com (4.1/SMI-4.1)
id AA06499; Mon, 9 Nov 98 11:40:46 GMT
Message-Id: <3646D4A0.2E4D402B@uk.radan.com>
Date: Mon, 09 Nov 1998 11:40:16 +0000
From: Mark Ovens <marko@uk.radan.com>
Organization: Radan Computational Ltd
X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 4.1.3_U1 sun4m)
Mime-Version: 1.0
To: current@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: UK User Group meeting
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
If there are any UK FreeBSD users (or anyone who may be in the UK on
21/11) here who are not on the UKUG mailing list this is to inform you
that the UKUG is holding a User Group meeting on Saturday 21/11 in
Oxford.
The venue is Jamal's Balti House, Walton Street, Oxford at 10p.m.
(although some of us will probably meet up earlier in a local pub).
If you are interested in joining us please e-mail me.
--
Trust the computer industry to shorten Year 2000 to Y2K. It
was this thinking that caused the problem in the first place.
Mark Ovens, CNC Applications Engineer, Radan Computational Ltd.
Bath, Avon, England. Sheet Metal CAD/CAM Solutions
mailto:marko@uk.radan.com http://www.radan.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 03:48:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA19034
for freebsd-current-outgoing; Mon, 9 Nov 1998 03:48:34 -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 DAA19029
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 03:48:29 -0800 (PST)
(envelope-from gjp@gjp.erols.com)
Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1])
by gjp.erols.com (8.9.1/8.8.7) with ESMTP id GAA24907;
Mon, 9 Nov 1998 06:48:14 -0500 (EST)
(envelope-from gjp@gjp.erols.com)
To: Alfred Perlstein <bright@hotjobs.com>
cc: current@FreeBSD.ORG
From: "Gary Palmer" <gpalmer@FreeBSD.ORG>
Subject: Re: newer gcc?
In-reply-to: Your message of "Mon, 09 Nov 1998 02:00:09 EST."
<Pine.BSF.4.05.9811090157020.19817-100000@porkfriedrice.ny.genx.net>
Date: Mon, 09 Nov 1998 06:48:13 -0500
Message-ID: <24903.910612093@gjp.erols.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Alfred Perlstein wrote in message ID
<Pine.BSF.4.05.9811090157020.19817-100000@porkfriedrice.ny.genx.net>:
>
> Has there been any thought to jumping to a newer version of gcc,
> specifically egcs?
egcs is too fast a moving target for consideration at this
point. Also, the quality varies too much from day to day, so even if
we did include egcs, it would be a lot of work to find a stable
release. I believe there is talk about moving to a later version of
gcc, but I cannot see (and would oppose) a move to egcs at this point.
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 Mon Nov 9 04:36:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA26590
for freebsd-current-outgoing; Mon, 9 Nov 1998 04:36:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26510
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 04:35:59 -0800 (PST)
(envelope-from werner@btp1da.phy.uni-bayreuth.de)
Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id NAA27222; Mon, 9 Nov 1998 13:33:12 +0100 (MET)
Message-ID: <XFMail.981109133311.werner@btp1da.phy.uni-bayreuth.de>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="_=XFMail.1.3.p0.FreeBSD:981109133311:22665=_"
In-Reply-To: <199811062045.MAA18819@math.berkeley.edu>
Date: Mon, 09 Nov 1998 13:33:11 +0100 (MET)
Organization: University of bayreuth
From: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
To: (Dan Strick) <dan@math.berkeley.edu>
Subject: RE: latest kernel breaks linux netscape.
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
This message is in MIME format
--_=XFMail.1.3.p0.FreeBSD:981109133311:22665=_
Content-Type: text/plain; charset=us-ascii
On 06-Nov-98 Dan Strick wrote:
>> Is the FBSD-Netscape working for you ?
>> Here both versions (4.07 and 45) freeze my system completely on exit !
>> No keyboard response, no panic .
>
> I had (almost) precisely this problem back in August when running
> the pre-BETA SNAP releases. I attributed it to non-specific VM bugs
> that the FreeBSD developers were vaguely aware of and didn't want
> to hear any more about (short of an explanation and a fix).
>
> The symptoms eventually went away (sometime in September I believe)
> and I hoped they were gone for good. I feel a little awkward complaining
> about a vague symptom (e.g. system frequently locks up after running
> Netscape) that I am not prepared to debug myself. Unfortunately,
> Netscape is such an important application that I can't recommend
> FreeBSD to anyone else unless it runs Netscape. I am grateful
> the the problem seems to be gone.
>
> I just tested both Netscape 4.06 FreeBSD and Linux 2.0 binaries, and
> they seemed to work just fine. I am running 3.0-19981031-SNAP on this
> machine.
>
> I recall one previous email that implicated the USER_LDT kernel
> config option in other netscape problems and another that reported
> problems when running netscape after wine (which supposedly requires
> the USER_LDT kernel config option). I build my kernels with the
> USER_LDT option.
>
> Dan Strick
> dan@math.berkeley.edu
----------------------------------
With a current system from today (Mon Nov 9) all my problems with netscape
went away. FBSD-netscape 4.07-navigator and 4.5-communicator are working fine
also with nfs-homed users.
It seems that changes in the system sources cured my problems.
Attached is a list of changes between Nov 6 and Nov 9 (from my cvsup-logfile).
Werner
--_=XFMail.1.3.p0.FreeBSD:981109133311:22665=_
Content-Disposition: attachment; filename="changes.lst"
Content-Transfer-Encoding: base64
Content-Description: changes.lst
Content-Type: application/octet-stream; name=changes.lst; SizeOnDisk=3837
IAogIEFkZCBkZWx0YSAxLjEzNSA5OC4xMS4wOC4xMy4wNS4zMCBicmlhbgogIEFkZCBkZWx0YSAx
LjEzNiA5OC4xMS4wOC4xMy4wNi4xOSBicmlhbgogRWRpdCBzcmMvdXNyLnNiaW4vc3lzY3RsL3N5
c2N0bC5jCiAgQWRkIGRlbHRhIDEuMTkgOTguMTEuMDguMTkuMjcuNDMgcGhrClNodXR0aW5nIGRv
d24gY29ubmVjdGlvbiB0byBzZXJ2ZXIKRmluaXNoZWQgc3VjY2Vzc2Z1bGx5ClBhcnNpbmcgc3Vw
ZmlsZSAiL3Vzci9jdnN1cC9zZWN1cmUtc3VwZmlsZSIKTG9va2luZyB1cCBhZGRyZXNzIG9mIGN2
c3VwLmludGVybmF0LkZyZWVCU0Qub3JnCkNvbm5lY3RpbmcgdG8gY3ZzdXAuaW50ZXJuYXQuRnJl
ZUJTRC5vcmcKQ29ubmVjdGVkIHRvIGN2c3VwLmludGVybmF0LkZyZWVCU0Qub3JnClNlcnZlciBz
b2Z0d2FyZSB2ZXJzaW9uOiBSRUxfMTVfNApOZWdvdGlhdGluZyBmaWxlIGF0dHJpYnV0ZSBzdXBw
b3J0CkV4Y2hhbmdpbmcgY29sbGVjdGlvbiBpbmZvcm1hdGlvbgpFc3RhYmxpc2hpbmcgYWN0aXZl
LW1vZGUgZGF0YSBjb25uZWN0aW9uClJ1bm5pbmcKVXBkYXRpbmcgY29sbGVjdGlvbiBzcmMtY3J5
cHRvL2N2cwpVcGRhdGluZyBjb2xsZWN0aW9uIHNyYy1lQm9uZXMvY3ZzClVwZGF0aW5nIGNvbGxl
Y3Rpb24gc3JjLXNlY3VyZS9jdnMKU2h1dHRpbmcgZG93biBjb25uZWN0aW9uIHRvIHNlcnZlcgpG
aW5pc2hlZCBzdWNjZXNzZnVsbHkKIAogRGVsZXRlIHNyYy9zeXMvbW9kdWxlcy9pYmNzMi9pYmNz
Mi5jCiBFZGl0IHNyYy9nYW1lcy9mb3J0dW5lL2RhdGZpbGVzL2ZvcnR1bmVzCiBFZGl0IHNyYy9n
YW1lcy9mb3J0dW5lL2RhdGZpbGVzL2ZvcnR1bmVzMgogRWRpdCBzcmMvaW5jbHVkZS9wcm90b2Nv
bHMvcndob2QuaAogRWRpdCBzcmMvbGliL2xpYmMvZ2VuL3BvcGVuLjMKIEVkaXQgc3JjL2xpYi9s
aWJjL3N5cy9zZW5kZmlsZS4yCiBFZGl0IHNyYy9saWIvbGliY19yL3V0aHJlYWQvdXRocmVhZF9j
b25kLmMKIEVkaXQgc3JjL2xpYi9saWJmZXRjaC9NYWtlZmlsZQogRWRpdCBzcmMvbGliL2xpYmZl
dGNoL2NvbW1vbi5jCiBFZGl0IHNyYy9saWIvbGliZmV0Y2gvY29tbW9uLmgKIEVkaXQgc3JjL2xp
Yi9saWJmZXRjaC9mZXRjaC4zCiBFZGl0IHNyYy9saWIvbGliZmV0Y2gvZmV0Y2guYwogRWRpdCBz
cmMvbGliL2xpYmZldGNoL2ZldGNoLmgKIEVkaXQgc3JjL2xpYi9saWJmZXRjaC9maWxlLmMKIEVk
aXQgc3JjL2xpYi9saWJmZXRjaC9mdHAuYwogRWRpdCBzcmMvbGliL2xpYmZldGNoL2Z0cC5lcnJv
cnMKIEVkaXQgc3JjL2xpYi9saWJmZXRjaC9odHRwLmMKIEVkaXQgc3JjL2xpYi9saWJmZXRjaC9o
dHRwLmVycm9ycwogRWRpdCBzcmMvbGliZXhlYy9ydGxkLWFvdXQvcnRsZC5jCiBFZGl0IHNyYy9y
ZWxlYXNlL01ha2VmaWxlCiBFZGl0IHNyYy9zYmluL2ZzZGIvZnNkYi5jCiBFZGl0IHNyYy9zYmlu
L2tsZHN0YXQva2xkc3RhdC5jCiBFZGl0IHNyYy9zYmluL2tsZHVubG9hZC9rbGR1bmxvYWQuOAog
RWRpdCBzcmMvc2Jpbi9rbGR1bmxvYWQva2xkdW5sb2FkLmMKIEVkaXQgc3JjL3NoYXJlL21hbi9t
YW40L21hbjQuaTM4Ni9NYWtlZmlsZQogRWRpdCBzcmMvc2hhcmUvbWFuL21hbjQvbWFuNC5pMzg2
L2xuYy40CiBFZGl0IHNyYy9zaGFyZS9tay9ic2QucG9ydC5tawogRWRpdCBzcmMvc2hhcmUvbWsv
YnNkLnBvcnQuc3ViZGlyLm1rCiBFZGl0IHNyYy9zaGFyZS9zeXNjb25zL2ZvbnRzL01ha2VmaWxl
CiBFZGl0IHNyYy9zeXMvYWxwaGEvYWxwaGEvY2xvY2suYwogRWRpdCBzcmMvc3lzL2FscGhhL2Fs
cGhhL2Nsb2NrX2lmLm0KIEVkaXQgc3JjL3N5cy9hbHBoYS9hbHBoYS9tZW0uYwogRWRpdCBzcmMv
c3lzL2FscGhhL2NvbmYvZmlsZXMuYWxwaGEKIEVkaXQgc3JjL3N5cy9ib290L2NvbW1vbi9pbnRl
cnBfZm9ydGguYwogRWRpdCBzcmMvc3lzL2Jvb3QvZmljbC9maWNsLmMKIEVkaXQgc3JjL3N5cy9i
b290L2ZpY2wvZmljbC5oCiBFZGl0IHNyYy9zeXMvYm9vdC9maWNsL3NvZnR3b3Jkcy9zb2Z0Y29y
ZS5mcgogRWRpdCBzcmMvc3lzL2Jvb3QvZmljbC93b3Jkcy5jCiBFZGl0IHNyYy9zeXMvYm9vdC9p
Mzg2L2Jvb3QyL01ha2VmaWxlCiBFZGl0IHNyYy9zeXMvYm9vdC9pMzg2L2Jvb3QyL2Jvb3QxLm00
CiBFZGl0IHNyYy9zeXMvYm9vdC9pMzg2L2Jvb3QyL2Jvb3QxLnMKIEVkaXQgc3JjL3N5cy9ib290
L2kzODYvYm9vdDIvYm9vdDIuYwogRWRpdCBzcmMvc3lzL2NvbmYvZmlsZXMKIEVkaXQgc3JjL3N5
cy9kZXYvZGVjL21jY2xvY2tfaWYubQogRWRpdCBzcmMvc3lzL2Rldi9paWNidXMvaWljYmJfaWYu
bQogRWRpdCBzcmMvc3lzL2Rldi9paWNidXMvaWljYnVzLmMKIEVkaXQgc3JjL3N5cy9kZXYvaWlj
YnVzL2lpY2J1c19pZi5tCiBFZGl0IHNyYy9zeXMvZGV2L3BwYnVzL2lmX3BsaXAuYwogRWRpdCBz
cmMvc3lzL2Rldi9zbWJ1cy9zbWJ1c19pZi5tCiBFZGl0IHNyYy9zeXMvaTM4Ni9jb25mL0xJTlQK
IEVkaXQgc3JjL3N5cy9pMzg2L2kzODYvbWVtLmMKIEVkaXQgc3JjL3N5cy9pMzg2L2kzODYvcG1h
cC5jCiBFZGl0IHNyYy9zeXMvaTM4Ni9pYmNzMi9pYmNzMl9zeXN2ZWMuYwogRWRpdCBzcmMvc3lz
L2kzODYvaXNhL3BjdnQvcGN2dF9kcnYuYwogRWRpdCBzcmMvc3lzL2kzODYvaXNhL3NuZC9zb3Vu
ZC5jCiBFZGl0IHNyYy9zeXMvaTM4Ni9pc2Evc3BpZ290LmMKIEVkaXQgc3JjL3N5cy9pMzg2L2lz
YS9zeXNjb25zLmMKIEVkaXQgc3JjL3N5cy9pc2Evc3lzY29ucy5jCiBFZGl0IHNyYy9zeXMva2Vy
bi9idXNfaWYubQogRWRpdCBzcmMvc3lzL2tlcm4vZGV2aWNlX2lmLm0KIEVkaXQgc3JjL3N5cy9r
ZXJuL2tlcm5fbGlua2VyLmMKIEVkaXQgc3JjL3N5cy9rZXJuL2xpbmtfZWxmLmMKIEVkaXQgc3Jj
L3N5cy9rZXJuL21ha2VkZXZvcHMucGwKIEVkaXQgc3JjL3N5cy9rZXJuL3N1YnJfeHh4LmMKIEVk
aXQgc3JjL3N5cy9rZXJuL3VpcGNfc3lzY2FsbHMuYwogRWRpdCBzcmMvc3lzL21pc2Nmcy9kZXZm
cy9kZXZmc2RlZnMuaAogRWRpdCBzcmMvc3lzL21vZHVsZXMvY29mZi9NYWtlZmlsZQogRWRpdCBz
cmMvc3lzL21vZHVsZXMvaWJjczIvTWFrZWZpbGUKIEVkaXQgc3JjL3N5cy9uZnMvbmZzX2Jpby5j
CiBFZGl0IHNyYy9zeXMvbmZzL25mc19zdWJzLmMKIEVkaXQgc3JjL3N5cy9uZnMvbmZzX3Zub3Bz
LmMKIEVkaXQgc3JjL3N5cy9wYzk4L2NvbmYvTWFrZWZpbGUucGM5OAogRWRpdCBzcmMvc3lzL3Bj
OTgvY29uZi9vcHRpb25zLnBjOTgKIEVkaXQgc3JjL3N5cy9wYzk4L2kzODYvbWFjaGRlcC5jCiBF
ZGl0IHNyYy9zeXMvcGM5OC9pMzg2L3VzZXJjb25maWcuYwogRWRpdCBzcmMvc3lzL3BjOTgvcGM5
OC9zeXNjb25zLmMKIEVkaXQgc3JjL3N5cy9wY2kvYnJvb2t0cmVlODQ4LmMKIEVkaXQgc3JjL3N5
cy9wY2kvYnQ4NDhfaTJjLmMKIEVkaXQgc3JjL3N5cy9wY2kvbWV0ZW9yLmMKIEVkaXQgc3JjL3N5
cy9wY2kvcGNpX2NvbXBhdC5jCiBFZGl0IHNyYy9zeXMvcGNpL3hycHUuYwogRWRpdCBzcmMvc3lz
L3N5cy9jb25mLmgKIEVkaXQgc3JjL3N5cy9zeXMvbW91bnQuaAogRWRpdCBzcmMvc3lzL3ZtL2Rl
dmljZV9wYWdlci5jCiBFZGl0IHNyYy91c3IuYmluL01ha2VmaWxlCiBFZGl0IHNyYy91c3IuYmlu
L2ZldGNoL2ZldGNoLjEKIEVkaXQgc3JjL3Vzci5iaW4vZmV0Y2gvbWFpbi5jCiBFZGl0IHNyYy91
c3IuYmluL3cvdy5jCiBFZGl0IHNyYy91c3Iuc2Jpbi9wcHAvcHBwLjgKIEVkaXQgc3JjL3Vzci5z
YmluL3N5c2N0bC9zeXNjdGwuYwogQ2hlY2tvdXQgc3JjL2xpYi9saWJmZXRjaC9mZXRjaF9lcnIu
ZXQKIENoZWNrb3V0IHNyYy9zaGFyZS9tYW4vbWFuNC9tYW40LmkzODYvcmwuNAogQ2hlY2tvdXQg
c3JjL3N5cy9pc2EvcHNtLmMK
--_=XFMail.1.3.p0.FreeBSD:981109133311:22665=_--
End of MIME message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 05:51:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA03927
for freebsd-current-outgoing; Mon, 9 Nov 1998 05:51:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA03919
for <freebsd-current@freebsd.org>; Mon, 9 Nov 1998 05:51:39 -0800 (PST)
(envelope-from larry@marso.com)
Received: (from larry@localhost)
by second.dialup.access.net (8.9.1/8.8.8) id IAA18623
for freebsd-current@freebsd.org; Mon, 9 Nov 1998 08:49:05 -0500 (EST)
(envelope-from larry)
Date: Mon, 9 Nov 1998 08:49:05 -0500
From: "Larry S. Marso" <larry@marso.com>
To: freebsd-current@FreeBSD.ORG
Subject: MFS image invalid! after 3.0-Release->Pre-Release
Message-ID: <19981109084904.A18586@marso.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.13i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I had to revert from 3.0-Release to a pre-CAM (August) 3.0, given app
incompatibilities.
After a make world, creating a new kernel and remaking the devices using
/usr/src/etc/etc.i386/MAKEDEV, I rebooted.
However, using the new kernel, my machine reboots halfway through startup,
complaining about an invalid MFS image.
I can reboot fine using kernel.old.
Best regards
--
Larry S. Marso
larry@marso.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 06:22:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA06798
for freebsd-current-outgoing; Mon, 9 Nov 1998 06:22:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06793
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 06:22:24 -0800 (PST)
(envelope-from psalzman@gamefish.pcola.gulf.net)
Received: from localhost (psalzman@localhost)
by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id OAA07841;
Mon, 9 Nov 1998 14:21:57 GMT
(envelope-from psalzman@gamefish.pcola.gulf.net)
Date: Mon, 9 Nov 1998 14:21:57 +0000 (GMT)
From: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
To: Alfred Perlstein <bright@hotjobs.com>
cc: current@FreeBSD.ORG
Subject: Re: newer gcc?
In-Reply-To: <Pine.BSF.4.05.9811090157020.19817-100000@porkfriedrice.ny.genx.net>
Message-ID: <Pine.BSF.4.05.9811091418020.7784-100000@gamefish.pcola.gulf.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, 9 Nov 1998, Alfred Perlstein wrote:
>
> Has there been any thought to jumping to a newer version of gcc,
> specifically egcs?
Doesn't egcs require an ELF filetype? Currently many people
are still a.out. I'm sure it will change in the future.
--
Phillip Salzman
"I know something you don't know!!!!!"
>
> Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com
> -- There are operating systems, and then there's FreeBSD.
> -- http://www.freebsd.org/ 3.0-current
>
>
> 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 Nov 9 06:34:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA07405
for freebsd-current-outgoing; Mon, 9 Nov 1998 06:34:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07399
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 06:34:03 -0800 (PST)
(envelope-from psalzman@gamefish.pcola.gulf.net)
Received: from localhost (psalzman@localhost)
by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id OAA07882;
Mon, 9 Nov 1998 14:31:27 GMT
(envelope-from psalzman@gamefish.pcola.gulf.net)
Date: Mon, 9 Nov 1998 14:31:27 +0000 (GMT)
From: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
To: "Alexander B. Povolotsky" <tarkhil@synchroline.ru>
cc: current@FreeBSD.ORG
Subject: Re: weird problem - maybe in my head?
In-Reply-To: <199811090820.LAA04657@enterprise.sl.ru>
Message-ID: <Pine.BSF.4.05.9811091427590.7784-100000@gamefish.pcola.gulf.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
What type of connection are you on? I have experienced this
problem before. It happened whenever I hit a lot (heh, not really) of
bandwidth. Try turning off TCP Extensions in rc.conf. If its a modem,
also make sure you have the speed set to the correct rate - and not
higher.
--
Phillip Salzman
"See Spot run. Good Spot. See Spot install Windows NT, see Spot crash,
BAD SPOT!"
On Mon, 9 Nov 1998, Alexander B. Povolotsky wrote:
> Hello!
>
> On machine running
>
> FreeBSD satellite.megabit7.ru 3.0-19980804-SNAP FreeBSD 3.0-19980804-SNAP #5:
> Mon Nov 2 13:31:21 MSK 1998 root@satellite.megabit7.ru:/usr/src/sys/compil
> e/SYNC i386
>
> as well as FreeBSD-Current
>
> I've got the following error (100% repeatable!!!):
>
> Attempt to get by ftp (via proxy or not, usnig wget, lynx, ftp, ncftp3) file
> boot.flp (pathname doesn't mean) result in fetching about 10000 bytes (ftom
> 9288 to 10136), and after that point NOTHING is transferred. Server doesn't
> matter.
>
> Gzipping file helped at once. Renaming file didn't, so something in that file
> must make my IP stack (or what???) crazy.
>
> I know it is weird, but I have no more clues...
>
> Alex.
> --
> Alexander B. Povolotsky, System Administrator
>
>
> 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 Nov 9 06:47:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA08830
for freebsd-current-outgoing; Mon, 9 Nov 1998 06:47:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08823
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 06:47:27 -0800 (PST)
(envelope-from jfieber@fallout.campusview.indiana.edu)
Received: from localhost (jfieber@localhost)
by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id JAA07111;
Mon, 9 Nov 1998 09:45:37 -0500 (EST)
Date: Mon, 9 Nov 1998 09:45:37 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Brian Feldman <green@unixhelp.org>
cc: garman@earthling.net, current@FreeBSD.ORG, julian@whistle.com,
wollman@khavrinen.lcs.mit.edu
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.BSF.4.05.9811082226380.11650-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.4.05.9811090932230.462-100000@fallout.campusview.indiana.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 Sun, 8 Nov 1998, Brian Feldman wrote:
> Device 1K-blocks Used Avail Capacity Type
> /dev/wd0s1b 102400 12300 89972 12% Interleaved
> /dev/wd1s1b 102400 12408 89864 12% Interleaved
> Total 204544 24708 179836 12%
> This is normal usage after
> swap_pager: suggest more swap space: 157 MB
> swap_pager: out of swap space
> pid 5795 (memory), uid 1000, was killed: out of swap space
I don't think this illustrates bug we are trying to smoke out
though. This is showing the "memory" process as being killed,
presumably because it went overboard on memory consumption.
The dying daemon bug seems to manifists itself in the death of
innocent bystander processes and usually by a signal 11, not by
"out of swap space". Note these two observations:
Date: Sun, 8 Nov 1998 15:26:48 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
Message-ID: <Pine.BSF.3.95.981108152353.12341D-100000@current1.whistle.com>
It's been a while since we looked at it closely but it appeared
that a page of useful memeory was suddenly unmapped from the
process.
Date: Sun, 8 Nov 1998 23:17:00 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199811090417.XAA13563@khavrinen.lcs.mit.edu>
It seems, so far as I was able to characterize, to happen to
daemons which are *swapped out* at the time of the memory
shortage. If it's active enough to still be in core, it doesn't
get spammed.
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 07:05:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA13416
for freebsd-current-outgoing; Mon, 9 Nov 1998 07:05:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13397
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 07:05:00 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id KAA22513;
Mon, 9 Nov 1998 10:07:38 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Mon, 9 Nov 1998 10:07:38 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
cc: current@FreeBSD.ORG
Subject: Re: newer gcc?
In-Reply-To: <Pine.BSF.4.05.9811091418020.7784-100000@gamefish.pcola.gulf.net>
Message-ID: <Pine.BSF.4.05.9811091003040.22497-100000@porkfriedrice.ny.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, 9 Nov 1998, Phillip Salzman wrote:
> > Has there been any thought to jumping to a newer version of gcc,
> > specifically egcs?
>
> Doesn't egcs require an ELF filetype? Currently many people
> are still a.out. I'm sure it will change in the future.
Well i only brought this up again for 2 reasons, as i know it has been
discussed to death in the past, however with the move to ELF and perl5 i
thought... what the hell :)
Anyhow:
a) egcs is a bit more improved than gcc in terms of c++ support, and more
features/optimizations.
b) i thought the move to elf was so that we _could_ better use the newer
GNU tools.
The reason i was asking is that i may bmake it and stick it into my tree,
if i can produce a "release" build using it maybe people would show more
interest.
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 07:19:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA14892
for freebsd-current-outgoing; Mon, 9 Nov 1998 07:19:06 -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 HAA14887
for <freebsd-current@freebsd.org>; Mon, 9 Nov 1998 07:19:05 -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 HAA19335
for <freebsd-current@freebsd.org>; Mon, 9 Nov 1998 07:18:50 -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 HAA10076
for <freebsd-current@freebsd.org>; Mon, 9 Nov 1998 07:18:49 -0800 (PST)
Received: (from gdonl@localhost)
by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id HAA25276
for freebsd-current@freebsd.org; Mon, 9 Nov 1998 07:18:48 -0800 (PST)
Date: Mon, 9 Nov 1998 07:18:48 -0800 (PST)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199811091518.HAA25276@salsa.gv.tsc.tdk.com>
To: freebsd-current@FreeBSD.ORG
Subject: userland visible change to <sys/proc.h>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I just checked in a change to fix a bug in getsid() that increases
the size of the session structure in <sys/proc.h>. When you next
rebuild your kernel using version 1.59 of proc.h, it will probably
be necessary for you to "make includes" and rebuild libkvm so that
your userland will match your kernel.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 08:25:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA21215
for freebsd-current-outgoing; Mon, 9 Nov 1998 08:25: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 IAA21210
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 08:25:30 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id IAA16950; Mon, 9 Nov 1998 08:25:14 -0800 (PST)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
id sma016939; Mon Nov 9 08:24:47 1998
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id IAA01667; Mon, 9 Nov 1998 08:24:42 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199811091624.IAA01667@bubba.whistle.com>
Subject: Re: The infamous dying daemons bug
In-Reply-To: <19981106200028.23174@follo.net> from Eivind Eklund at "Nov 6, 98 08:00:28 pm"
To: eivind@yes.no (Eivind Eklund)
Date: Mon, 9 Nov 1998 08:24:42 -0800 (PST)
Cc: crossd@cs.rpi.edu, jfieber@indiana.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
Eivind Eklund writes:
> > Does this happen to everyone, I personally have *never* seen it happen,
> > and I have run quite a few systems run with full memory utilization.
>
> No. Unfortunately, we've not found any (or I at least don't know of
> any) common factors between all the machines that have this problem.
Has the use of memory mapping been ruled out as a possible common factor?
-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 Nov 9 08:26:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA21407
for freebsd-current-outgoing; Mon, 9 Nov 1998 08:26:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from garman.dyn.ml.org (pm106-17.dialip.mich.net [192.195.231.219])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA21393
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 08:26:54 -0800 (PST)
(envelope-from garman@garman.dyn.ml.org)
Message-Id: <199811091626.IAA21393@hub.freebsd.org>
Received: (qmail 21094 invoked from smtpd); 9 Nov 1998 16:28:09 -0000
Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1)
by localhost.garman.net with SMTP; 9 Nov 1998 16:28:09 -0000
Date: Mon, 9 Nov 1998 11:28:08 -0500 (EST)
From: garman@earthling.net
Reply-To: garman@earthling.net
Subject: Re: The infamous dying daemons bug
To: wollman@khavrinen.lcs.mit.edu
cc: dg@root.com, eivind@yes.no, jfieber@indiana.edu, current@FreeBSD.ORG
In-Reply-To: <199811090417.XAA13563@khavrinen.lcs.mit.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 8 Nov, Garrett Wollman wrote:
> Totally unrelated to the problem. It seems, so far as I was able to
> characterize, to happen to daemons which are *swapped out* at the time
> of the memory shortage. If it's active enough to still be in core, it
> doesn't get spammed.
>
Yes, this fits the symptoms i'm seeing here with samba. The daemon
will be fine as long as it has not been swapped out; after that, it's
*poof*. That's also probably why people with heavy-use samba servers
haven't seen this problem.
enjoy
--
Jason Garman http://garman.dyn.ml.org/
Student, University of Maryland garman@earthling.net
And now... did you know that: Whois: JAG145
"If you fart consistently for 6 years and 9 months, enough gas is
produced to create the energy of an atomic bomb." -- 0xdeadbeef posting
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 08:29:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA21647
for freebsd-current-outgoing; Mon, 9 Nov 1998 08:29:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21642
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 08:29:40 -0800 (PST)
(envelope-from crossd@cs.rpi.edu)
Received: from o2.cs.rpi.edu (root@o2.cs.rpi.edu [128.113.96.156])
by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id LAA19702;
Mon, 9 Nov 1998 11:29:19 -0500 (EST)
Received: from localhost (crossd@localhost)
by o2.cs.rpi.edu (8.9.1a/8.9.1) with ESMTP id LAA05887;
Mon, 9 Nov 1998 11:27:11 -0500 (EST)
X-Authentication-Warning: o2.cs.rpi.edu: crossd owned process doing -bs
Date: Mon, 9 Nov 1998 11:27:11 -0500
From: "David E. Cross" <crossd@cs.rpi.edu>
To: Archie Cobbs <archie@whistle.com>
cc: Eivind Eklund <eivind@yes.no>, jfieber@indiana.edu, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <199811091624.IAA01667@bubba.whistle.com>
Message-ID: <Pine.SGI.4.05.9811091124580.5731-100000@o2.cs.rpi.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Eivind Eklund writes:
> > > Does this happen to everyone, I personally have *never* seen it happen,
> > > and I have run quite a few systems run with full memory utilization.
> >
> > No. Unfortunately, we've not found any (or I at least don't know of
> > any) common factors between all the machines that have this problem.
>
> Has the use of memory mapping been ruled out as a possible common factor?
Maybe if someone who is having this problem could donate the machine to a
core member?
--
David Cross
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 08:40:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA22731
for freebsd-current-outgoing; Mon, 9 Nov 1998 08:40:35 -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 IAA22718
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 08:40:29 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id IAA17163; Mon, 9 Nov 1998 08:40:14 -0800 (PST)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
id sma017158; Mon Nov 9 08:39:50 1998
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id IAA01712; Mon, 9 Nov 1998 08:39:50 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199811091639.IAA01712@bubba.whistle.com>
Subject: Re: ThinkPad 600E
In-Reply-To: <199811061303.aa10592@mail.eecis.udel.edu> from Jerry Alexandratos at "Nov 6, 98 01:03:50 pm"
To: alexandr@mail.eecis.udel.edu
Date: Mon, 9 Nov 1998 08:39:50 -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
Jerry Alexandratos writes:
> So, looks like it'll be a 600E. I'm excited because it doesn't have any
> of that Mwave crap!!! However, it only comes with a DVD drive. Will
> -current recognize the DVD drive as a CD-ROM drive? If not, any ideas
> on how far away we are from getting DVD support?
My work-sponsored laptop has a DVD as well, which is recognized
as a normal CD-ROM and works fine as such:
wdc1 at 0x170-0x177 irq 15 on isa
wdc1: unit 0 (atapi): <MATSHITADVD-ROM SR-8171/058A>, removable, accel, dma, iordis
-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 Nov 9 09:03:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA24466
for freebsd-current-outgoing; Mon, 9 Nov 1998 09:03:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24459
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 09:03:10 -0800 (PST)
(envelope-from jfieber@fallout.campusview.indiana.edu)
Received: from localhost (jfieber@localhost)
by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id LAA07431;
Mon, 9 Nov 1998 11:57:11 -0500 (EST)
Date: Mon, 9 Nov 1998 11:57:11 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Archie Cobbs <archie@whistle.com>
cc: Eivind Eklund <eivind@yes.no>, crossd@cs.rpi.edu, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <199811091624.IAA01667@bubba.whistle.com>
Message-ID: <Pine.BSF.4.05.9811091151230.462-100000@fallout.campusview.indiana.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, 9 Nov 1998, Archie Cobbs wrote:
> Eivind Eklund writes:
> > > Does this happen to everyone, I personally have *never* seen it happen,
> > > and I have run quite a few systems run with full memory utilization.
> >
> > No. Unfortunately, we've not found any (or I at least don't know of
> > any) common factors between all the machines that have this problem.
>
> Has the use of memory mapping been ruled out as a possible common factor?
Hm... dynamically linked binaries mmap() the libraries, correct?
And a statically linked binary wouldn't use memory mapping unless
it explicitly does so itself? So, would the replacement of a
dynamically linked inetd that dies with a static inetd be a valid
test here?
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 09:10:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA25075
for freebsd-current-outgoing; Mon, 9 Nov 1998 09:10: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 JAA25061
for <current@freebsd.org>; Mon, 9 Nov 1998 09:10:30 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id JAA17543 for <current@freebsd.org>; Mon, 9 Nov 1998 09:10:14 -0800 (PST)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
id sma017541; Mon Nov 9 09:10:09 1998
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id JAA01978 for current@freebsd.org; Mon, 9 Nov 1998 09:10:09 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199811091710.JAA01978@bubba.whistle.com>
Subject: Re: The infamous dying daemons bug
In-Reply-To: <199811091626.IAA21393@hub.freebsd.org> from "garman@earthling.net" at "Nov 9, 98 11:28:08 am"
To: current@FreeBSD.ORG
Date: Mon, 9 Nov 1998 09:10:09 -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
garman@earthling.net writes:
> > Totally unrelated to the problem. It seems, so far as I was able to
> > characterize, to happen to daemons which are *swapped out* at the time
> > of the memory shortage. If it's active enough to still be in core, it
> > doesn't get spammed.
> >
> Yes, this fits the symptoms i'm seeing here with samba. The daemon
> will be fine as long as it has not been swapped out; after that, it's
> *poof*. That's also probably why people with heavy-use samba servers
> haven't seen this problem.
Vague observations..
- samba, inetd, sendmail all do a lot of forking (which
may be nothing other than a common need for more memory)
- samba uses memory mapping to implement file locking
I'd like to try to confirm/deny that memory mapping is one
required ingredient of the recipie. The only other known
ingredient seems to be running out of swap.
Could someone who is seeing this happen often recompile their
kernel with memory mapping disabled, and see if that changes
anything (other than making programs that use mmap() stop working)?
Ie, comment out
options SYSVSHM
options SYSVSEM
options SYSVMSG
(this *does* disable mmap(), right? If not, instead patch the
mmap() syscall to always return an error)
-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 Nov 9 09:15:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA25482
for freebsd-current-outgoing; Mon, 9 Nov 1998 09:15:27 -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 JAA25477
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 09:15:24 -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 SAA05657;
Mon, 9 Nov 1998 18:15:02 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id SAA15216;
Mon, 9 Nov 1998 18:15:02 +0100 (MET)
Message-ID: <19981109181501.17552@follo.net>
Date: Mon, 9 Nov 1998 18:15:01 +0100
From: Eivind Eklund <eivind@yes.no>
To: Archie Cobbs <archie@whistle.com>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <199811091626.IAA21393@hub.freebsd.org> <199811091710.JAA01978@bubba.whistle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <199811091710.JAA01978@bubba.whistle.com>; from Archie Cobbs on Mon, Nov 09, 1998 at 09:10:09AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Nov 09, 1998 at 09:10:09AM -0800, Archie Cobbs wrote:
> Could someone who is seeing this happen often recompile their
> kernel with memory mapping disabled, and see if that changes
> anything (other than making programs that use mmap() stop working)?
> Ie, comment out
>
> options SYSVSHM
> options SYSVSEM
> options SYSVMSG
>
> (this *does* disable mmap(), right? If not, instead patch the
> mmap() syscall to always return an error)
This does NOT remove mmap() support.
If you remove mmap() support, not dynamically linked executables will
work. You'll have to recompile everything static before trying this
trick.
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 09:21:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA25986
for freebsd-current-outgoing; Mon, 9 Nov 1998 09:21:34 -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 JAA25980
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 09:21:32 -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 SAA21871;
Mon, 9 Nov 1998 18:20:20 +0100 (CET)
To: Archie Cobbs <archie@whistle.com>
cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-reply-to: Your message of "Mon, 09 Nov 1998 09:10:09 PST."
<199811091710.JAA01978@bubba.whistle.com>
Date: Mon, 09 Nov 1998 18:20:19 +0100
Message-ID: <21869.910632019@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
This is not a feasible path.
And those options doesn't disable mmap(2) anyway.
phkmalloc(3) uses mmap(2) for it's page table.
A static inetd sounds like a good experiment.
Poul-Henning
>Vague observations..
>
> - samba, inetd, sendmail all do a lot of forking (which
> may be nothing other than a common need for more memory)
>
> - samba uses memory mapping to implement file locking
>
>I'd like to try to confirm/deny that memory mapping is one
>required ingredient of the recipie. The only other known
>ingredient seems to be running out of swap.
>
>Could someone who is seeing this happen often recompile their
>kernel with memory mapping disabled, and see if that changes
>anything (other than making programs that use mmap() stop working)?
>Ie, comment out
>
> options SYSVSHM
> options SYSVSEM
> options SYSVMSG
>
>(this *does* disable mmap(), right? If not, instead patch the
>mmap() syscall to always return an error)
>
>-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
>
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 09:24:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA26276
for freebsd-current-outgoing; Mon, 9 Nov 1998 09:24: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 JAA26271
for <current@freebsd.org>; Mon, 9 Nov 1998 09:24:30 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id JAA17670; Mon, 9 Nov 1998 09:24:15 -0800 (PST)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
id sma017666; Mon Nov 9 09:24:11 1998
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id JAA02097; Mon, 9 Nov 1998 09:24:11 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199811091724.JAA02097@bubba.whistle.com>
Subject: Re: The infamous dying daemons bug
In-Reply-To: <19981109181501.17552@follo.net> from Eivind Eklund at "Nov 9, 98 06:15:01 pm"
To: eivind@yes.no (Eivind Eklund)
Date: Mon, 9 Nov 1998 09:24: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
Eivind Eklund writes:
> > Could someone who is seeing this happen often recompile their
> > kernel with memory mapping disabled, and see if that changes
> > anything (other than making programs that use mmap() stop working)?
> > Ie, comment out
> >
> > options SYSVSHM
> > options SYSVSEM
> > options SYSVMSG
> >
> > (this *does* disable mmap(), right? If not, instead patch the
> > mmap() syscall to always return an error)
>
> This does NOT remove mmap() support.
>
> If you remove mmap() support, not dynamically linked executables will
> work. You'll have to recompile everything static before trying this
> trick.
Oops, I was confusing memory mapping and shared memory.
Let's try the statically compiled inetd experiment first then..
any volunteers who can readily reproduce the problem want to
try it?
-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 Nov 9 09:35:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA27457
for freebsd-current-outgoing; Mon, 9 Nov 1998 09:35:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from feral-gw.feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27447
for <freebsd-current@freebsd.org>; Mon, 9 Nov 1998 09:35:12 -0800 (PST)
(envelope-from mjacob@feral.com)
Received: from localhost (mjacob@localhost)
by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id JAA13973
for <freebsd-current@freebsd.org>; Mon, 9 Nov 1998 09:34:29 -0800
Date: Mon, 9 Nov 1998 09:34:29 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
X-Sender: mjacob@feral-gw
Reply-To: mjacob@feral.com
To: freebsd-current@FreeBSD.ORG
Subject: sorry if I missed a thread here...
Message-ID: <Pine.LNX.4.02.9811090932220.13717-100000@feral-gw>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'm having problems with 3.0-current (as of a day or so ago) where
there are panics in the ffs code where a 'supervisor page not present'
panic occurs (it occurred in ffs_fragextend for me).
I'm not the only one this is happening to- in testing some Exabyte 8200
related fixes, dump seems to have triggered this. But I've been able
to trigger this whilst doing a dump | restore operation.
Any threads I should pick up on this? I'll try and isolate it a bit
more closely...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 09:44:08 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA28488
for freebsd-current-outgoing; Mon, 9 Nov 1998 09:44: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 JAA28479
for <current@freebsd.org>; Mon, 9 Nov 1998 09:44: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 JAA04773;
Mon, 9 Nov 1998 09:43:51 -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 JAA15097;
Mon, 9 Nov 1998 09:43:50 -0800 (PST)
(envelope-from jdp@polstra.com)
Date: Mon, 9 Nov 1998 09:43:50 -0800 (PST)
Message-Id: <199811091743.JAA15097@vashon.polstra.com>
To: psalzman@gamefish.pcola.gulf.net
Subject: Re: newer gcc?
Newsgroups: polstra.freebsd.current
In-Reply-To: <Pine.BSF.4.05.9811091418020.7784-100000@gamefish.pcola.gulf.net>
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.4.05.9811091418020.7784-100000@gamefish.pcola.gulf.net>,
Phillip Salzman <psalzman@gamefish.pcola.gulf.net> wrote:
>
> Doesn't egcs require an ELF filetype?
No. Have you tried ports/lang/egcs?
--
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 Nov 9 10:08:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA01451
for freebsd-current-outgoing; Mon, 9 Nov 1998 10:08:16 -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 KAA01442
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 10:08:12 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
by time.cdrom.com (8.8.8/8.8.8) with ESMTP id JAA07537;
Mon, 9 Nov 1998 09:07:25 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Alfred Perlstein <bright@hotjobs.com>
cc: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>, current@FreeBSD.ORG
Subject: Re: newer gcc?
In-reply-to: Your message of "Mon, 09 Nov 1998 10:07:38 EST."
<Pine.BSF.4.05.9811091003040.22497-100000@porkfriedrice.ny.genx.net>
Date: Mon, 09 Nov 1998 09:07:25 -0800
Message-ID: <7531.910631245@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> The reason i was asking is that i may bmake it and stick it into my tree,
That's a bit premature. I'd be more interested if you could even build
the world from egcs installed in /usr/local.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 10:08:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA01506
for freebsd-current-outgoing; Mon, 9 Nov 1998 10:08:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from picnic.mat.net (picnic.mat.net [206.246.122.117])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01494
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 10:08:37 -0800 (PST)
(envelope-from chuckr@mat.net)
Received: from localhost (chuckr@localhost)
by picnic.mat.net (8.9.1/8.8.5) with ESMTP id NAA14433;
Mon, 9 Nov 1998 13:07:12 -0500 (EST)
Date: Mon, 9 Nov 1998 13:07:12 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Alfred Perlstein <bright@hotjobs.com>
cc: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>, current@FreeBSD.ORG
Subject: Re: newer gcc?
In-Reply-To: <Pine.BSF.4.05.9811091003040.22497-100000@porkfriedrice.ny.genx.net>
Message-ID: <Pine.BSF.4.05.9811091304440.10145-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 Mon, 9 Nov 1998, Alfred Perlstein wrote:
>
> On Mon, 9 Nov 1998, Phillip Salzman wrote:
>
> > > Has there been any thought to jumping to a newer version of gcc,
> > > specifically egcs?
> >
> > Doesn't egcs require an ELF filetype? Currently many people
> > are still a.out. I'm sure it will change in the future.
>
> Well i only brought this up again for 2 reasons, as i know it has been
> discussed to death in the past, however with the move to ELF and perl5 i
> thought... what the hell :)
>
> Anyhow:
>
> a) egcs is a bit more improved than gcc in terms of c++ support, and more
> features/optimizations.
>
> b) i thought the move to elf was so that we _could_ better use the newer
> GNU tools.
>
> The reason i was asking is that i may bmake it and stick it into my tree,
> if i can produce a "release" build using it maybe people would show more
> interest.
This gets brought up about twice a year, forever. Please search the
mail archives for endless rehashing of this old bone. There are very
good reasons to *require* a certain amount of stability to FreeBSD's
compiler, these reasons haven't changed a bit, and aren't likely to.
----------------------------+-----------------------------------------------
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 Mon Nov 9 10:39:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA04901
for freebsd-current-outgoing; Mon, 9 Nov 1998 10:39:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04896
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 10:39:45 -0800 (PST)
(envelope-from psalzman@gamefish.pcola.gulf.net)
Received: from localhost (psalzman@localhost)
by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id SAA09096;
Mon, 9 Nov 1998 18:39:28 GMT
(envelope-from psalzman@gamefish.pcola.gulf.net)
Date: Mon, 9 Nov 1998 18:39:27 +0000 (GMT)
From: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
To: Alfred Perlstein <bright@hotjobs.com>
cc: current@FreeBSD.ORG
Subject: Re: newer gcc?
In-Reply-To: <Pine.BSF.4.05.9811091003040.22497-100000@porkfriedrice.ny.genx.net>
Message-ID: <Pine.BSF.4.05.9811091740260.7784-100000@gamefish.pcola.gulf.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> b) i thought the move to elf was so that we _could_ better use the newer
> GNU tools.
Yes, it was. But I doubt we really want to abandon our AOUT users
this early on. I'm limited to a.out right now because of the freak'n
problems with "Exceeded CPU timelimit" which occurs every time I attempt
to compile large programs. But thats probally caused by my crappy
hardware.
Maybe i'll get a new computer... someday.
>
> The reason i was asking is that i may bmake it and stick it into my tree,
> if i can produce a "release" build using it maybe people would show more
> interest.
Do it, then get it commited :)
> -Alfred
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 11:16:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA09474
for freebsd-current-outgoing; Mon, 9 Nov 1998 11:16:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA09454
for <current@freebsd.org>; Mon, 9 Nov 1998 11:16:27 -0800 (PST)
(envelope-from tom@uniserve.com)
Received: from shell.uniserve.ca [204.244.186.218]
by pop.uniserve.com with smtp (Exim 1.82 #4)
id 0zcwmg-0002B2-00; Mon, 9 Nov 1998 11:15:30 -0800
Date: Mon, 9 Nov 1998 11:15:28 -0800 (PST)
From: Tom <tom@uniserve.com>
X-Sender: tom@shell.uniserve.ca
To: "Alexander B. Povolotsky" <tarkhil@synchroline.ru>
cc: fbsd@trifork.gu.net, current@FreeBSD.ORG
Subject: Re: weird problem - maybe in my head?
In-Reply-To: <199811091037.NAA05060@enterprise.sl.ru>
Message-ID: <Pine.BSF.4.02A.9811091112420.22595-100000@shell.uniserve.ca>
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, 9 Nov 1998, Alexander B. Povolotsky wrote:
> <Pine.BSF.4.05.9811091106420.311-100000@trifork.gu.net>Andrew Stesin writes:
> >> boot.flp (pathname doesn't mean) result in fetching about 10000 bytes (ftom
> >> 9288 to 10136), and after that point NOTHING is transferred. Server doesn't
> >> matter.
> >
> > Which boot.flp exactly? what kind of network connection?
> > what network hardware is in use? how sysctl variables for TCP are set?
>
> > Maybe you have a braindamaged ISND TA or CSU/DSU or sattelite
> > modem somewhere on your way? I recall some troubles like yours
> > were due to crazy hardware.
>
> YES :-E Livingston Portmaster is The Crazy Thing. Sorry :-(
I don't know where this is coming from, but I have used almost every
piece of Livingston equipment with FreeBSD and never experienced a data
transfer problem! Most likely you have a configuration problem.
> Alex
> --
> Alexander B. Povolotsky, System Administrator
Tom
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 11:20:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA09876
for freebsd-current-outgoing; Mon, 9 Nov 1998 11:20:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09871
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 11:20:21 -0800 (PST)
(envelope-from psalzman@gamefish.pcola.gulf.net)
Received: from localhost (psalzman@localhost)
by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id TAA09270;
Mon, 9 Nov 1998 19:19:54 GMT
(envelope-from psalzman@gamefish.pcola.gulf.net)
Date: Mon, 9 Nov 1998 19:19:54 +0000 (GMT)
From: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
To: "David E. Cross" <crossd@cs.rpi.edu>
cc: Archie Cobbs <archie@whistle.com>, Eivind Eklund <eivind@yes.no>,
jfieber@indiana.edu, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.SGI.4.05.9811091124580.5731-100000@o2.cs.rpi.edu>
Message-ID: <Pine.BSF.4.05.9811091907350.7784-100000@gamefish.pcola.gulf.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'm having a problem that I believe is related to this. Any kernel above
3.0-RELEASE does not work correctly. Things happen, such as fsck dying
on signal 11 -- other things on signal 6. X doesn't start, the computer
locks up when I try. I've limited the commit that caused this to
sometime around the 3.0-RELEASE tag. I'm sure some VM code has been
commited around that time... I'm going to search it more.
Right now i'm living with -BETA
--
Phillip Salzman
On Mon, 9 Nov 1998, David E. Cross wrote:
>
>
> > Eivind Eklund writes:
> > > > Does this happen to everyone, I personally have *never* seen it happen,
> > > > and I have run quite a few systems run with full memory utilization.
> > >
> > > No. Unfortunately, we've not found any (or I at least don't know of
> > > any) common factors between all the machines that have this problem.
> >
> > Has the use of memory mapping been ruled out as a possible common factor?
> Maybe if someone who is having this problem could donate the machine to a
> core member?
>
> --
> David Cross
>
>
> 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 Nov 9 11:27:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA10729
for freebsd-current-outgoing; Mon, 9 Nov 1998 11:27:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10708
for <freebsd-current@freebsd.org>; Mon, 9 Nov 1998 11:27:13 -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 PAA09544
for <freebsd-current@freebsd.org>; Mon, 9 Nov 1998 15:26:53 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Mon, 9 Nov 1998 15:26:52 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: freebsd-current@FreeBSD.ORG
Subject: 18gig drive's supported?
Message-ID: <Pine.BSF.4.05.9811091514160.9466-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
I dont' know if there is anything special that the OS has to do as far as
large drive support is concerneed, but we just added the following drive
to our system, and can't get anywhere with it:
a1 at ahc0 bus 0 target 1 lun 0
da1: 17366MB (35566000 512 byte sectors: 255H 63S/T 2213C)
da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da1: <COMPAQ DGHS18Y 01A0> Fixed Direct Access SCSI3 device
We currently have three controllers in that machine, with 2+ drives per
controller...the other drives all work (4gig drives), but this new 18gig
appears to be a problem.
hub> dmesg | grep ahc
ahc0: <Adaptec 2940 Ultra SCSI adapter> rev 0x01 int a irq 12 on pci0.9.0
ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
ahc1: <Adaptec 2940 Ultra SCSI adapter> rev 0x01 int a irq 9 on pci0.10.0
ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
ahc2: <Adaptec 2940A Ultra SCSI adapter> rev 0x01 int a irq 11 on pci0.12.0
ahc2: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs
probe1:ahc0:0:1:0): Sending SDTR!!
ub> dmesg | grep "^da" | sort
da0 at ahc0 bus 0 target 0 lun 0
da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C)
da0: <QUANTUM VIKING II 4.5WSE 3506> Fixed Direct Access SCSI2 device
da1 at ahc0 bus 0 target 1 lun 0
da1: 17366MB (35566000 512 byte sectors: 255H 63S/T 2213C)
da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da1: <COMPAQ DGHS18Y 01A0> Fixed Direct Access SCSI3 device
da2 at ahc1 bus 0 target 0 lun 0
da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enables
da2: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C)
da2: <QUANTUM XP34550W LYK8> Fixed Direct Access SCSI2 device
da3 at ahc1 bus 0 target 1 lun 0
da3: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da3: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C)
da3: <QUANTUM XP34550W LYK8> Fixed Direct Access SCSI2 device
da4 at ahc2 bus 0 target 1 lun 0
da4: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
da4: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C)
da4: <QUANTUM XP34301 1071> Fixed Direct Access SCSI2 device
da5 at ahc2 bus 0 target 2 lun 0
da5: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
da5: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C)
da5: <QUANTUM XP34301 1071> Fixed Direct Access SCSI2 device
da6 at ahc2 bus 0 target 3 lun 0
da6: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled
da6: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C)
da6: <QUANTUM XP34550S LXY4> Fixed Direct Access SCSI2 device
da7 at ahc2 bus 0 target 4 lun 0
da7: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
da7: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C)
da7: <QUANTUM XP34301 1071> Fixed Direct Access SCSI2 device
da8 at ahc2 bus 0 target 5 lun 0
da8: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
da8: 4101MB (8399520 512 byte sectors: 255H 63S/T 522C)
da8: <Quantum XP34300 L912> Fixed Direct Access SCSI2 device
If I run /stand/sysinstall->Configure->Label, I get back a message stating
that 'No disks found! Please verify that your disk controller is being
properly probed at boot time'
The system comes out on uname -a as 3.0-CURRENT, dated November 4th...
Thoughts and/or ideas? Its obvious that the kernel is finding all the drives,
so I'm curious why /stand/sysinstall doesn't see them...
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 Mon Nov 9 12:02:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA14671
for freebsd-current-outgoing; Mon, 9 Nov 1998 12:02:55 -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 MAA14652
for <freebsd-current@FreeBSD.ORG>; Mon, 9 Nov 1998 12:02:54 -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 MAA00450;
Mon, 9 Nov 1998 12:01:00 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811092001.MAA00450@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Larry S. Marso" <larry@marso.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: MFS image invalid! after 3.0-Release->Pre-Release
In-reply-to: Your message of "Mon, 09 Nov 1998 08:49:05 EST."
<19981109084904.A18586@marso.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 09 Nov 1998 12:01:00 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I had to revert from 3.0-Release to a pre-CAM (August) 3.0, given app
> incompatibilities.
>
> After a make world, creating a new kernel and remaking the devices using
> /usr/src/etc/etc.i386/MAKEDEV, I rebooted.
>
> However, using the new kernel, my machine reboots halfway through startup,
> complaining about an invalid MFS image.
>
> I can reboot fine using kernel.old.
That doesn't sound like an august-vintage kernel you've got there; it
sounds like you've got a ~3.0-RELEASE kernel with MFS_ROOT set.
--
\\ 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 Mon Nov 9 12:07:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA15216
for freebsd-current-outgoing; Mon, 9 Nov 1998 12:07:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from priscilla.mu.org (priscilla.mu.org [206.152.116.84])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15209
for <current@freebsd.org>; Mon, 9 Nov 1998 12:07:11 -0800 (PST)
(envelope-from paul@priscilla.mu.org)
Received: (from paul@localhost)
by priscilla.mu.org (8.8.8/8.8.8) id OAA02810;
Mon, 9 Nov 1998 14:06:01 -0600 (CST)
Message-ID: <19981109140601.A2798@mu.org>
Date: Mon, 9 Nov 1998 14:06:01 -0600
From: Paul Saab <paul@mu.org>
To: The Hermit Hacker <scrappy@hub.org>
Cc: current@FreeBSD.ORG
Subject: Re: 18gig drive's supported?
References: <Pine.BSF.4.05.9811091514160.9466-100000@thelab.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.05.9811091514160.9466-100000@thelab.hub.org>; from The Hermit Hacker on Mon, Nov 09, 1998 at 03:26:52PM -0400
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
did you upgrade this system from a pre-cam system? If you did I
think you need to upgrade sysinstall too.
paul
The Hermit Hacker (scrappy@hub.org) wrote:
> I dont' know if there is anything special that the OS has to do as far as
> large drive support is concerneed, but we just added the following drive
> to our system, and can't get anywhere with it:
>
> a1 at ahc0 bus 0 target 1 lun 0
> da1: 17366MB (35566000 512 byte sectors: 255H 63S/T 2213C)
> da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
> da1: <COMPAQ DGHS18Y 01A0> Fixed Direct Access SCSI3 device
>
>
> We currently have three controllers in that machine, with 2+ drives per
> controller...the other drives all work (4gig drives), but this new 18gig
> appears to be a problem.
>
> hub> dmesg | grep ahc
> ahc0: <Adaptec 2940 Ultra SCSI adapter> rev 0x01 int a irq 12 on pci0.9.0
> ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
> ahc1: <Adaptec 2940 Ultra SCSI adapter> rev 0x01 int a irq 9 on pci0.10.0
> ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
> ahc2: <Adaptec 2940A Ultra SCSI adapter> rev 0x01 int a irq 11 on pci0.12.0
> ahc2: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs
> probe1:ahc0:0:1:0): Sending SDTR!!
> ub> dmesg | grep "^da" | sort
> da0 at ahc0 bus 0 target 0 lun 0
> da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
> da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C)
> da0: <QUANTUM VIKING II 4.5WSE 3506> Fixed Direct Access SCSI2 device
> da1 at ahc0 bus 0 target 1 lun 0
> da1: 17366MB (35566000 512 byte sectors: 255H 63S/T 2213C)
> da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
> da1: <COMPAQ DGHS18Y 01A0> Fixed Direct Access SCSI3 device
> da2 at ahc1 bus 0 target 0 lun 0
> da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enables
> da2: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C)
> da2: <QUANTUM XP34550W LYK8> Fixed Direct Access SCSI2 device
> da3 at ahc1 bus 0 target 1 lun 0
> da3: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
> da3: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C)
> da3: <QUANTUM XP34550W LYK8> Fixed Direct Access SCSI2 device
> da4 at ahc2 bus 0 target 1 lun 0
> da4: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
> da4: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C)
> da4: <QUANTUM XP34301 1071> Fixed Direct Access SCSI2 device
> da5 at ahc2 bus 0 target 2 lun 0
> da5: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
> da5: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C)
> da5: <QUANTUM XP34301 1071> Fixed Direct Access SCSI2 device
> da6 at ahc2 bus 0 target 3 lun 0
> da6: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled
> da6: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C)
> da6: <QUANTUM XP34550S LXY4> Fixed Direct Access SCSI2 device
> da7 at ahc2 bus 0 target 4 lun 0
> da7: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
> da7: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C)
> da7: <QUANTUM XP34301 1071> Fixed Direct Access SCSI2 device
> da8 at ahc2 bus 0 target 5 lun 0
> da8: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
> da8: 4101MB (8399520 512 byte sectors: 255H 63S/T 522C)
> da8: <Quantum XP34300 L912> Fixed Direct Access SCSI2 device
>
> If I run /stand/sysinstall->Configure->Label, I get back a message stating
> that 'No disks found! Please verify that your disk controller is being
> properly probed at boot time'
>
> The system comes out on uname -a as 3.0-CURRENT, dated November 4th...
>
> Thoughts and/or ideas? Its obvious that the kernel is finding all the drives,
> so I'm curious why /stand/sysinstall doesn't see them...
>
> 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
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 12:26:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA17333
for freebsd-current-outgoing; Mon, 9 Nov 1998 12:26:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from blondie.ottawa.cc (blondie.ottawa.cc [209.112.49.20])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17327
for <freebsd-current@FreeBSD.ORG>; Mon, 9 Nov 1998 12:26:39 -0800 (PST)
(envelope-from mat@blondie.ottawa.cc)
Received: from localhost (mat@localhost)
by blondie.ottawa.cc (8.9.1/8.9.1) with ESMTP id UAA09555;
Mon, 9 Nov 1998 20:25:48 -0500 (EST)
(envelope-from mat@blondie.ottawa.cc)
Date: Mon, 9 Nov 1998 20:25:48 -0500 (EST)
From: User MAT <mat@blondie.ottawa.cc>
To: mike@seidata.com
cc: Bill Fenner <fenner@parc.xerox.com>, Dmitry Eremin <dmiter@sci-nnov.ru>,
freebsd-current@FreeBSD.ORG
Subject: Re: /kernel: arp: 192.168.1.188 is on de1 but got reply from
00:c0:4f:a4:81:2d on de0
In-Reply-To: <Pine.BSF.4.05.9811061654360.17661-100000@ns1.seidata.com>
Message-ID: <Pine.BSF.4.05.9811092017590.9547-100000@blondie.ottawa.cc>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Sorry to pick up this thread so late...
I've noticed something similar on my machine at home. The box is
connected to a cable modem. I have my roomates machine (running Win95)
going through another NIC and I'm natd'ing it.
One night, because of a similar message to above, I ran natd with
the debuging output. What I infered from all of this is that my ISP is
routing packets wrongly and that the private (10.xxx./192.168.1.x) packets
were actually comming from internet (or my perception of it) (I acutally
got the ether addrr of some machines using the private net numbers).
This should cause confusion because the netmask indicates that all
192.168.1.x should be comming from a different device (in my case, the
roomates computer).
Furthermore but unrelated, that ISP uses private net number for
their routers !!!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 12:28:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA17514
for freebsd-current-outgoing; Mon, 9 Nov 1998 12:28:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from terminator.informatik.ba-stuttgart.de (terminator.informatik.ba-stuttgart.de [141.31.111.23])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17496
for <freebsd-current@FreeBSD.ORG>; Mon, 9 Nov 1998 12:28:24 -0800 (PST)
(envelope-from henry@MX.BA-Stuttgart.De)
Received: from marylin.goethestr12-net.marbach-neckar (marylin.informatik.ba-stuttgart.de [141.31.112.1])
by terminator.informatik.ba-stuttgart.de (8.8.8/8.8.8) with ESMTP id VAA01194;
Mon, 9 Nov 1998 21:22:57 +0100 (CET)
(envelope-from henry@MX.BA-Stuttgart.De)
Received: (from henry@localhost)
by marylin.goethestr12-net.marbach-neckar (8.9.1/8.8.8) id VAA00697;
Mon, 9 Nov 1998 21:26:06 +0100 (CET)
(envelope-from henry)
From: Henry Vogt <henry@MX.BA-Stuttgart.De>
Message-Id: <199811092026.VAA00697@marylin.goethestr12-net.marbach-neckar>
Subject: Re: 18gig drive's supported?
In-Reply-To: <Pine.BSF.4.05.9811091514160.9466-100000@thelab.hub.org> from The Hermit Hacker at "Nov 9, 98 03:26:52 pm"
To: scrappy@hub.org (The Hermit Hacker)
Date: Mon, 9 Nov 1998 21:26:06 +0100 (CET)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL40 (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
Hello,
> I dont' know if there is anything special that the OS has to do as far as
> large drive support is concerneed, but we just added the following drive
> to our system, and can't get anywhere with it:
>
> a1 at ahc0 bus 0 target 1 lun 0
> da1: 17366MB (35566000 512 byte sectors: 255H 63S/T 2213C)
> da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
> da1: <COMPAQ DGHS18Y 01A0> Fixed Direct Access SCSI3 device
>
>
> We currently have three controllers in that machine, with 2+ drives per
> controller...the other drives all work (4gig drives), but this new 18gig
> appears to be a problem.
>
Nothing special with 18Gig Drives, they work.(see below)
Either this is a bug in 3.0-current sysinstall (or aic7880 Driver?)
Since sysinstall doesn't recognized my either, I had to disklabel them first
with a 2.2.7 System, but they work fine with 3.0-Current.
I have a similar Machine with aic 7890 Controller, 3.0 sysinstall
works flawless here.
----------------------------- C U T ----------------------------
FreeBSD 3.0-CURRENT #0: Thu Nov 5 07:55:09 CET 1998
henry@gilels:/usr/src/sys/compile/SPIELBERG
[...]
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
Probing for devices on PCI bus 0:
chip0: <Intel 82440FX (Natoma) PCI and memory controller> rev 0x02 on pci0.0.0
chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.7.0
ahc0: <Adaptec 2940 Ultra SCSI adapter> rev 0x00 int a irq 16 on pci0.8.0
ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
[...]
SMP: AP CPU #1 Launched!
[...]
changing root device to da0s1a
da3 at ahc0 bus 0 target 3 lun 0
da3: <SEAGATE ST118273W 5764> Fixed Direct Access SCSI2 device
da3: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da3: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C)
da2 at ahc0 bus 0 target 2 lun 0
da2: <SEAGATE ST118273W 5764> Fixed Direct Access SCSI2 device
da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da2: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C)
da1 at ahc0 bus 0 target 1 lun 0
da1: <SEAGATE ST34572W 0784> Fixed Direct Access SCSI2 device
da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C)
da0 at ahc0 bus 0 target 0 lun 0
da0: <SEAGATE ST34572W 0784> Fixed Direct Access SCSI2 device
da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C)
[...]
----------------------------- C U T ----------------------------
Hope this info helps.
Henry
--
//
// Do you suffer from long term memory loss ? I don't remember:-(
//
// Henry Vogt (henry@MX.BA-Stuttgart.De)
// Goethestr. 12, 71672 Marbach (Neckar), Tel. 07144/841653
//
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 12:37:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA18399
for freebsd-current-outgoing; Mon, 9 Nov 1998 12:37:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from saturn.spel.com (saturn.spel.com [208.226.39.196])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18385
for <current@freebsd.org>; Mon, 9 Nov 1998 12:37:22 -0800 (PST)
(envelope-from mturpin@saturn.spel.com)
Received: from localhost (mturpin@localhost)
by saturn.spel.com (8.9.1/8.9.1) with ESMTP id PAA00208
for <current@freebsd.org>; Mon, 9 Nov 1998 15:34:11 -0500 (EST)
(envelope-from mturpin@saturn.spel.com)
Date: Mon, 9 Nov 1998 15:34:11 -0500 (EST)
From: Mark Turpin <mturpin@saturn.spel.com>
To: current@FreeBSD.ORG
Subject: psmintr: out of sync
Message-ID: <Pine.BSF.4.05.9811091524170.203-100000@saturn.spel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello,
I am getting the following error when I run X.
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (00c8 != 0008).
An older message said to try adding flags 0x100 to the device line in the
kernel config file. That did make the errors stop.
The mouse is a Genius NetMouse Pro. Below are the startup messages.
Nov 9 15:19:06 saturn /kernel: video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000
Nov 9 15:19:06 saturn /kernel: video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000
Nov 9 15:19:06 saturn /kernel: video#0: mode:6, flags:0x3 G 640x200x1, 1 plane(s), font:8x8, win:0xb8000
Nov 9 15:19:07 saturn /kernel: video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000
Nov 9 15:19:07 saturn /kernel: video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000
Nov 9 15:19:07 saturn /kernel: video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000
Nov 9 15:19:07 saturn /kernel: video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000
Nov 9 15:19:07 saturn /kernel: video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000
Nov 9 15:19:07 saturn /kernel: video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000
Nov 9 15:19:07 saturn /kernel: video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000
Nov 9 15:19:07 saturn /kernel: video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000
Nov 9 15:19:07 saturn /kernel: video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000
Nov 9 15:19:07 saturn /kernel: video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000
Nov 9 15:19:07 saturn /kernel: VGA parameters upon power-up
Nov 9 15:19:07 saturn /kernel: 50
Nov 9 15:19:07 saturn /kernel: 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81
Nov 9 15:19:07 saturn /kernel: bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96
Nov 9 15:19:07 saturn /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c
Nov 9 15:19:07 saturn /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff
Nov 9 15:19:07 saturn /kernel: VGA parameters in BIOS for mode 24
Nov 9 15:19:07 saturn /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81
Nov 9 15:19:07 saturn /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96
Nov 9 15:19:07 saturn /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c
Nov 9 15:19:07 saturn /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff
Nov 9 15:19:07 saturn /kernel: EGA/VGA parameters to be used for mode 24
Nov 9 15:19:07 saturn /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81
Nov 9 15:19:07 saturn /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96
Nov 9 15:19:07 saturn /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c
Nov 9 15:19:07 saturn /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff
Nov 9 15:19:07 saturn /kernel: sc0: the current keyboard controller command byte 0065
Nov 9 15:19:07 saturn /kernel: kbdio: DIAGNOSE status:0055
Nov 9 15:19:07 saturn /kernel: kbdio: TEST_KBD_PORT status:0000
Nov 9 15:19:07 saturn /kernel: kbdio: RESET_KBD return code:00fa
Nov 9 15:19:07 saturn /kernel: kbdio: RESET_KBD status:00aa
Nov 9 15:19:07 saturn /kernel: sc0: keyboard device ID: ab41
Nov 9 15:19:07 saturn /kernel: sc0 at 0x60-0x6f irq 1 on motherboard
Nov 9 15:19:07 saturn /kernel: sc0: VGA color <16 virtual consoles, flags=0x0>
Nov 9 15:19:07 saturn /kernel: ed0 not found at 0x280
Nov 9 15:19:07 saturn /kernel: fe0 not found at 0x300
Nov 9 15:19:07 saturn /kernel: sio0: i
Nov 9 15:19:07 saturn /kernel: rq maps: 0x1 0x11 0x1 0x1
Nov 9 15:19:07 saturn /kernel: sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
Nov 9 15:19:07 saturn /kernel: sio0: type 16550A
Nov 9 15:19:07 saturn /kernel: sio1: irq maps: 0x1 0x9 0x1 0x1
Nov 9 15:19:07 saturn /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa
Nov 9 15:19:07 saturn /kernel: sio1: type 16550A
Nov 9 15:19:07 saturn /kernel: sio2: disabled, not probed.
Nov 9 15:19:07 saturn /kernel: sio3: disabled, not probed.
Nov 9 15:19:07 saturn /kernel: lpt0 at 0x378-0x37f irq 7 on isa
Nov 9 15:19:07 saturn /kernel: lpt0: Interrupt-driven port
Nov 9 15:19:07 saturn /kernel: lp0: TCP/IP capable interface
Nov 9 15:19:07 saturn /kernel: lpt1 not found
Nov 9 15:19:07 saturn /kernel: mse0: wrong signature ff
Nov 9 15:19:07 saturn /kernel: mse0 not found at 0x23c
Nov 9 15:19:07 saturn /kernel: psm0: current command byte:0065
Nov 9 15:19:07 saturn /kernel: kbdio: TEST_AUX_PORT status:0000
Nov 9 15:19:07 saturn /kernel: kbdio: RESET_AUX return code:00fa
Nov 9 15:19:07 saturn /kernel: kbdio: RESET_AUX status:00aa
Nov 9 15:19:07 saturn /kernel: kbdio: RESET_AUX ID:0000
Nov 9 15:19:07 saturn /kernel: psm: status 00 02 64
Nov 9 15:19:07 saturn /kernel: psm: status 00 03 06
Nov 9 15:19:07 saturn /kernel: psm: status 00 33 55
Nov 9 15:19:07 saturn /kernel: psm: data 18 ff 00
Nov 9 15:19:07 saturn /kernel: psm: status 00 02 64
Nov 9 15:19:08 saturn /kernel: psm0 at 0x60-0x64 irq 12 on motherboard
Nov 9 15:19:08 saturn /kernel: psm0: model NetMouse, device ID 0, 3 buttons
Nov 9 15:19:08 saturn /kernel: psm0: config:00000000, flags:00000000, packet size:4
Nov 9 15:19:08 saturn /kernel: psm0: syncmask:c8, syncbits:08
Nov 9 15:19:08 saturn /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
Nov 9 15:19:08 saturn /kernel: fdc0: FIFO enabled, 8 bytes threshold
Nov 9 15:19:08 saturn /kernel: fd0: 1.44MB 3.5in
Nov 9 15:19:08 saturn /kernel: wdc0 not found at 0x1f0
Nov 9 15:19:08 saturn /kernel: wdc1 not found at 0x170
Nov 9 15:19:08 saturn /kernel: wt0 not found at 0x300
Nov 9 15:19:08 saturn /kernel: mcd0: timeout getting s
Nov 9 15:19:08 saturn /kernel: tatus
Nov 9 15:19:08 saturn /kernel: mcd0 not found at 0x300
Nov 9 15:19:08 saturn /kernel: matcdc0 not found at 0x230
Nov 9 15:19:08 saturn /kernel: scd0 not found at 0x230
Nov 9 15:19:08 saturn /kernel: ie0: unknown board_id: f000
Nov 9 15:19:08 saturn /kernel: ie0 not found at 0x300
Nov 9 15:19:08 saturn /kernel: ep0 not found at 0x300
Nov 9 15:19:08 saturn /kernel: ex0 not found
Nov 9 15:19:08 saturn /kernel: le0 not found at 0x300
Nov 9 15:19:08 saturn /kernel: lnc0 not found at 0x280
Nov 9 15:19:08 saturn /kernel: ze0 not found at 0x300
Nov 9 15:19:08 saturn /kernel: zp0 not found at 0x300
Nov 9 15:19:08 saturn /kernel: cs0 not found at 0x300
Nov 9 15:19:08 saturn /kernel: adv0 not found at 0x330
Nov 9 15:19:08 saturn /kernel: bt0: Failed Status Reg Test - 0
Nov 9 15:19:08 saturn /kernel: bt0: Failed Status Reg Test - ff
Nov 9 15:19:08 saturn last message repeated 4 times
Nov 9 15:19:08 saturn /kernel: bt0 not found at 0x134
Nov 9 15:19:08 saturn /kernel: aha0 not found at 0x134
Nov 9 15:19:08 saturn /kernel: npx0 on motherboard
Nov 9 15:19:08 saturn /kernel: npx0: INT 16 interface
Nov 9 15:19:08 saturn /kernel: apm0: disabled, not probed.
Nov 9 15:19:08 saturn /kernel: imasks: bio c8000040, tty c706109a, net c706109a
Nov 9 15:19:08 saturn /kernel: SMP: enabled INTs: 1, 3, 4, 6, 7, 12, 17, 18, apic_imen: 0x00f9ef25
Nov 9 15:19:08 saturn /kernel: BIOS Geometries:
Nov 9 15:19:08 saturn /kernel: 0:03fe3f20 0..1022=1023 cylinders, 0..63=64 heads, 1..32=32 sectors
Nov 9 15:19:08 saturn /kernel: 0 accounted for
Nov 9 15:19:08 saturn /kernel: Device configuration finished.
Nov 9 15:19:08 saturn /kernel: APIC_IO: routing 8254 via 8259 on pin 0
Nov 9 15:19:08 saturn /kernel: new masks: bio c8000040, tty c706109a, net c706109a
Nov 9 15:19:08 saturn /kernel: Waiting 15 seconds for SCSI devices to settle
Nov 9 15:19:08 saturn /kernel: (noperiph:
Nov 9 15:19:08 saturn /kernel: ahc0:0:X:X): SCSI bus reset delivered. 0 SCBs aborted.
Nov 9 15:19:08 saturn /kernel: SMP: AP CPU #1 Launched!
Nov 9 15:19:08 saturn /kernel: SMP: CPU1 apic_initialize():
Nov 9 15:19:08 saturn /kernel: lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff
Nov 9 15:19:08 saturn /kernel: ahc0: Selection Timeout on A:4. 1 SCBs aborted
Nov 9 15:19:08 saturn /kernel: ahc0: Selection Timeout on A:5. 1 SCBs aborted
Nov 9 15:19:08 saturn /kernel: ahc0: Selection Timeout on A:6. 1 SCBs aborted
Nov 9 15:19:08 saturn /kernel: ahc0: Selection Timeout on A:8. 1 SCBs aborted
Nov 9 15:19:08 saturn /kernel: ahc0: Selection Timeout on A:9. 1 SCBs aborted
Nov 9 15:19:08 saturn /kernel: ahc0: Selection Timeout on A:10. 1 SCBs aborted
Nov 9 15:19:08 saturn /kernel: ahc0: Selection Timeout on A:11. 1 SCBs aborted
Nov 9 15:19:08 saturn /kernel: ahc0: Selection Timeout on A:12. 1 SCBs aborted
Nov 9 15:19:08 saturn /kernel: ahc0: Selection Timeout on A:13. 1 SCBs aborted
Nov 9 15:19:08 saturn /kernel: ahc0: Selection Timeout on A:14. 1 SCBs aborted
Nov 9 15:19:08 saturn /kernel: ahc0: Selection Timeout on A:15. 1 SCBs aborted
Nov 9 15:19:08 saturn /kernel: (probe0:ahc0:0:0:0): MODE SENSE(06). CDB: 1a 0 a 0 14 0
Nov 9 15:19:08 saturn /kernel: (probe0:ahc0:0:0:0): RECOVERED ERROR asc:5d,0
Nov 9 15:19:08 saturn /kernel: (probe0:ahc0:0:0:0): Failure prediction threshold exceeded field replaceable unit: 45
Nov 9 15:19:08 saturn /kernel: ahc0: target 1 synchronous at 5.0MHz, offset = 0xb
Nov 9 15:19:08 saturn /kernel: ahc0: target 1 using asynchronous transfers
Nov 9 15:19:08 saturn /kernel: ahc0: target 1 synchronous at 5.0M
Nov 9 15:19:08 saturn /kernel: Hz, offset = 0xb
Nov 9 15:19:08 saturn /kernel: (probe3:ahc0:0:3:0): INQUIRY. CDB: 12 1 80 0 ff 0
Nov 9 15:19:08 saturn /kernel: (probe3:ahc0:0:3:0): ILLEGAL REQUEST asc:24,0
Nov 9 15:19:09 saturn /kernel: (probe3:ahc0:0:3:0): Invalid field in CDB
Nov 9 15:19:09 saturn /kernel: ahc0: target 0 synchronous at 20.0MHz, offset = 0xf
Nov 9 15:19:09 saturn /kernel: (probe2:ahc0:0:2:0): MODE SENSE(06). CDB: 1a 0 a 0 14 0
Nov 9 15:19:09 saturn /kernel: (probe2:ahc0:0:2:0): ILLEGAL REQUEST asc:24,0
Nov 9 15:19:09 saturn /kernel: (probe2:ahc0:0:2:0): Invalid field in CDB
Nov 9 15:19:09 saturn /kernel: ahc0: target 3 synchronous at 10.0MHz, offset = 0xf
Nov 9 15:19:09 saturn /kernel: ahc0: target 3 using asynchronous transfers
Nov 9 15:19:09 saturn /kernel: ahc0: target 3 synchronous at 10.0MHz, offset = 0xf
Nov 9 15:19:09 saturn /kernel: (probe2:ahc0:0:2:0): INQUIRY. CDB: 12 1 80 0 ff 0
Nov 9 15:19:09 saturn /kernel: (probe2:ahc0:0:2:0): ILLEGAL REQUEST asc:24,0
Nov 9 15:19:09 saturn /kernel: (probe2:ahc0:0:2:0): Invalid field in CDB
Nov 9 15:19:09 saturn /kernel: ahc0: target 2 synchronous at 10.0MHz, offset = 0xf
Nov 9 15:19:09 saturn /kernel: ahc0: target 2 using asynchronous transfers
Nov 9 15:19:09 saturn /kernel: ahc0: target 2 synchronous at 10.0MHz, offset = 0xf
Nov 9 15:19:09 saturn /kernel: sa0 at ahc0 bus 0 target 1 lun 0
Nov 9 15:19:09 saturn /kernel: sa0: <EXABYTE EXB-85058SQANXB7 07T0> Removable Sequential Access SCSI2 device
Nov 9 15:19:09 saturn /kernel: sa0: Serial Number 06013793
Nov 9 15:19:09 saturn /kernel: sa0: 5.0MB/s transfers (5.0MHz, offset 11)
Nov 9 15:19:09 saturn /kernel: pass0 at ahc0 bus 0 target 0 lun 0
Nov 9 15:19:09 saturn /kernel: pass0: <SEAGATE
Nov 9 15:19:09 saturn /kernel: ST19171N 0023> Fixed Direct Access SCSI2 device
Nov 9 15:19:09 saturn /kernel: pass0: Serial Number LAA55623
Nov 9 15:19:09 saturn /kernel: pass0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled
Nov 9 15:19:09 saturn /kernel: pass1 at ahc0 bus 0 target 1 lun 0
Nov 9 15:19:09 saturn /kernel: pass1: <EXABYTE EXB-85058SQANXB7 07T0> Removable Sequential Access SCSI2 device
Nov 9 15:19:09 saturn /kernel: pass1: Serial Number 06013793
Nov 9 15:19:09 saturn /kernel: pass1: 5.0MB/s transfers (5.0MHz, offset 11)
Nov 9 15:19:09 saturn /kernel: pass2 at ahc0 bus 0 target 2 lun 0
Nov 9 15:19:09 saturn /kernel: pass2: <iomega jaz 1GB J.83> Removable Direct Access SCSI2 device
Nov 9 15:19:09 saturn /kernel: pass2: 10.0MB/s transfers (10.0MHz, offset 15)
Nov 9 15:19:09 saturn /kernel: pass3 at ahc0 bus 0 target 3 lun 0
Nov 9 15:19:09 saturn /kernel: pass3: <PLEXTOR CD-ROM PX-8XCS 1.01> Removable CD-ROM SCSI2 device
Nov 9 15:19:09 saturn /kernel: pass3: 10.0MB/s transfers (10.0MHz, offset 15)
Nov 9 15:19:09 saturn /kernel: ahc0: target 2 using asynchronous transfers
Nov 9 15:19:09 saturn /kernel: Considering FFS root f/s.
Nov 9 15:19:09 saturn /kernel: changing root device to da0s1a
Nov 9 15:19:09 saturn /kernel: ahc0: target 2 synchronous at 10.0MHz, offset = 0xf
Nov 9 15:19:09 saturn /kernel: da0 at ahc0 bus 0 target 0 lun 0
Nov 9 15:19:09 saturn /kernel: da0: <SEAGATE ST19171N 0023> Fixed Direct Access SCSI2 device
Nov 9 15:19:09 saturn /kernel: da0: Serial Number LAA55623
Nov 9 15:19:09 saturn /kernel: da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled
Nov 9 15:19:09 saturn /kernel: da0: 8683MB (17783112 512 byte s
Nov 9 15:19:09 saturn /kernel: ectors: 255H 63S/T 1106C)
Nov 9 15:19:09 saturn /kernel: ahc0: target 2 using asynchronous transfers
Nov 9 15:19:09 saturn /kernel: cd0 at ahc0 bus 0 target 3 lun 0
Nov 9 15:19:09 saturn /kernel: cd0: <PLEXTOR CD-ROM PX-8XCS 1.01> Removable CD-ROM SCSI2 device
Nov 9 15:19:09 saturn /kernel: cd0: 10.0MB/s transfers (10.0MHz, offset 15)
Nov 9 15:19:09 saturn /kernel: cd0: cd present [326524 x 2048 byte records]
Nov 9 15:19:09 saturn /kernel: ahc0: target 2 synchronous at 10.0MHz, offset = 0xf
Nov 9 15:19:09 saturn /kernel: ahc0: target 2 using asynchronous transfers
Nov 9 15:19:09 saturn /kernel: ahc0: target 2 synchronous at 10.0MHz, offset = 0xf
Nov 9 15:19:09 saturn /kernel: ahc0: target 2 using asynchronous transfers
Nov 9 15:19:09 saturn /kernel: ahc0: target 2 synchronous at 10.0MHz, offset = 0xf
Nov 9 15:19:09 saturn /kernel: ahc0: target 2 using asynchronous transfers
Nov 9 15:19:09 saturn /kernel: ahc0: target 2 synchronous at 10.0MHz, offset = 0xf
Nov 9 15:19:09 saturn /kernel: (da1:ahc0:0:2:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
Nov 9 15:19:09 saturn /kernel: (da1:ahc0:0:2:0): NOT READY asc:3a,0
Nov 9 15:19:09 saturn /kernel: (da1:ahc0:0:2:0): Medium not present
Nov 9 15:19:10 saturn /kernel: da1 at ahc0 bus 0 target 2 lun 0
Nov 9 15:19:10 saturn /kernel: da1: <iomega jaz 1GB J.83> Removable Direct Access SCSI2 device
Nov 9 15:19:10 saturn /kernel: da1: 10.0MB/s transfers (10.0MHz, offset 15)
Nov 9 15:19:10 saturn /kernel: da1: Attempt to query device size failed: NOT READY, Medium not present
Nov 9 15:19:10 saturn /kernel: da0s1: type 0xa5, start 0, end = 17783111, size 17783112 : OK
Thanks
Mark Turpin
-----------------------------------------------------------------------------
Mark Turpin | Consulting - Training - Network Installation
Systems Engineer |
Main Street Technology Centre | http://www.MainStreetTech.com
-----------------------------------------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 12:57:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA20548
for freebsd-current-outgoing; Mon, 9 Nov 1998 12:57:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20540
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 12:56:59 -0800 (PST)
(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
by lor.watermarkgroup.com (8.8.8/8.8.8) id PAA22043;
Mon, 9 Nov 1998 15:56:29 -0500 (EST)
(envelope-from luoqi)
Date: Mon, 9 Nov 1998 15:56:29 -0500 (EST)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <199811092056.PAA22043@lor.watermarkgroup.com>
To: dg@root.com, wollman@khavrinen.lcs.mit.edu
Subject: Re: The infamous dying daemons bug
Cc: current@FreeBSD.ORG, eivind@yes.no, jfieber@indiana.edu
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Totally unrelated to the problem. It seems, so far as I was able to
> characterize, to happen to daemons which are *swapped out* at the time
> of the memory shortage. If it's active enough to still be in core, it
> doesn't get spammed.
>
I went through swap_pager.c today and found a problem that could potentially
have bad consequences. It's a comparison between page index in the swap pager
and the size of the vm object, since a shadowed object may have a non-zero
paging offset with respect to the swap pager, the comparison should have taken
the offset into account. This piece of code has been there since '95, so
I can't say if this was responsible for the daemon dying problem.
-lq
Index: swap_pager.c
===================================================================
RCS file: /home/ncvs/src/sys/vm/swap_pager.c,v
retrieving revision 1.103
diff -u -r1.103 swap_pager.c
--- swap_pager.c 1998/10/31 15:31:28 1.103
+++ swap_pager.c 1998/11/09 11:02:54
@@ -349,7 +349,7 @@
*valid = 0;
ix = pindex / SWB_NPAGES;
if ((ix >= object->un_pager.swp.swp_nblocks) ||
- (pindex >= object->size)) {
+ (pindex >= object->size + OFF_TO_IDX(object->paging_offset))) {
return (FALSE);
}
swb = &object->un_pager.swp.swp_blocks[ix];
@@ -1227,8 +1227,8 @@
* intent of this code is to allocate small chunks for
* small objects)
*/
- if ((off == 0) && ((fidx + ntoget) > object->size)) {
- ntoget = object->size - fidx;
+ if ((off == 0) && ((fidx + ntoget) > object->size + paging_pindex)) {
+ ntoget = object->size + paging_pindex - fidx;
}
retrygetspace:
if (!swap_pager_full && ntoget > 1 &&
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 13:02:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA21402
for freebsd-current-outgoing; Mon, 9 Nov 1998 13:02:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21283
for <current@freebsd.org>; Mon, 9 Nov 1998 13:02:03 -0800 (PST)
(envelope-from archer@grape.carrier.kiev.ua)
Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111])
by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) with ESMTP id XAA24004;
Mon, 9 Nov 1998 23:01:36 +0200 (EET)
(envelope-from archer@grape.carrier.kiev.ua)
Received: (from uucp@localhost)
by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id XAA01919;
Mon, 9 Nov 1998 23:00:51 +0200 (EET)
(envelope-from archer@grape.carrier.kiev.ua)
Received: (from archer@localhost)
by grape.carrier.kiev.ua (8.9.1/8.9.1) id WAA27346;
Mon, 9 Nov 1998 22:42:14 +0200 (EET)
(envelope-from archer)
Date: Mon, 9 Nov 1998 22:42:14 +0200 (EET)
From: Alexander Litvin <archer@lucky.net>
Message-Id: <199811092042.WAA27346@grape.carrier.kiev.ua>
To: dg@root.com
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
X-Newsgroups: grape.freebsd.current
In-Reply-To: <199811081924.LAA06586@root.com>
Organization: Lucky Grape
User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386))
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <199811081924.LAA06586@root.com> you wrote:
>>Please don't tell anyone, but I am almost convinced that the bug is
>>here:
>>
>>-----swap_pager.c, line 1132------
>> /*
>> * If we're out of swap space, then attempt to free
>> * some whenever multiple pages are brought in. We
>> * must set the dirty bits so that the page contents
>> * will be preserved.
>> */
>> if (SWAPLOW ||
>> (vm_swap_size < btodb((cnt.v_page_count - cnt.v_wire_count)) * PAGE_SIZE)) {
>> for (i = 0; i < count; i++) {
>> m[i]->dirty = VM_PAGE_BITS_ALL;
>> }
>> swap_pager_freespace(object,
>> m[0]->pindex + paging_offset, count);
>> }
>>------------------------------------
>>If I sysctl out the call to swap_pager_freespace, all symptoms
>>disappear. This code activates at about the time when the "suggest more
>>swap space" message printed. IIRC, it was introduced by John Dyson this
>>winter.
>>
>>(Perhaps, the code just triggers a bug elsewhere... No idea what is
>>wrong).
DG> I don't see anything wrong with it, but if it is the cause of the
DG> problem, it can safely be removed. I'd suggest that people #if 0 out
DG> the code and see if the problem completely vanishes.
If it is not the cause, it is at least related. May be, someone
more skillful may investigate it?
I can quite reliably reproduce 'daemons dying' just by starting
a bunch of special 'memory hungry' progs. If I comment out
swap_pager_freespace() in the code above, that doesn't work
anymore. At least with the memory usage pattern of the above
mantioned 'memory hungry' progs, daemons keep running.
HURRAY?
Though, when I tried to stress the system with 'make -j# buildworld',
something weird happened. Particularily, I got a corrupt ld built.
It happened several times -- sometimes it is a bootstrap ld, and
as a result my buildworld just stopped (ld running indefinitely).
The last time it was a dynamic ld which I 'managed' to install into
/usr/libexec/elf/ld (made installworld) -- I was forced to extract
binary from 3.0-RELEASE distribution, since my system was not
able to build anything.
It may or may not be related to kernel stuff. The fact that it always
happen to ld makes me feel that it may be just build process coruption.
Anybody seen things like this? Anybody interested in details?
DG> -DG
DG> David Greenman
DG> Co-founder/Principal Architect, The FreeBSD Project
---
Weiler's Law:
Nothing is impossible for the man who doesn't have to do it
himself.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 13:48:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA26483
for freebsd-current-outgoing; Mon, 9 Nov 1998 13:48:15 -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 NAA26478
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 13:48:14 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id NAA03005;
Mon, 9 Nov 1998 13:37:37 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdzh3001; Mon Nov 9 21:37:29 1998
Date: Mon, 9 Nov 1998 13:36:56 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Luoqi Chen <luoqi@watermarkgroup.com>
cc: dg@root.com, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG,
eivind@yes.no, jfieber@indiana.edu
Subject: Re: The infamous dying daemons bug
In-Reply-To: <199811092056.PAA22043@lor.watermarkgroup.com>
Message-ID: <Pine.BSF.3.95.981109133607.13494I-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
We;ve been seeing problems since 96/97
On Mon, 9 Nov 1998, Luoqi Chen wrote:
> the offset into account. This piece of code has been there since '95, so
> I can't say if this was responsible for the daemon dying problem.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 13:55:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA27026
for freebsd-current-outgoing; Mon, 9 Nov 1998 13:55:01 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from paris.dppl.com (paris.dppl.com [205.230.74.150])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA27014
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 13:54:59 -0800 (PST)
(envelope-from yds@ingress.net)
Received: (qmail 22159 invoked from network); 9 Nov 1998 21:54:44 -0000
Received: from ichiban.ingress.com (HELO ichiban) (205.230.64.31)
by paris.dppl.com with SMTP; 9 Nov 1998 21:54:44 -0000
Message-ID: <03b901be0c2b$90ce0360$1f40e6cd@ichiban.ingress.com>
From: "Yarema" <yds@ingress.net>
To: <current@FreeBSD.ORG>
Subject: /usr/bin/groff: can't find `DESC' file
Date: Mon, 9 Nov 1998 16:54:46 -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
typing man whatever-has-no-cat-page produces the following:
/usr/bin/groff: can't find `DESC' file
/usr/bin/groff:fatal error: invalid device `ascii'
I did a make aout-to-elf some time late last week. Why is this happening?
>From what I can tell /usr/share/groff_font/ contains all the right stuff. No
different from a 2.2.7 system. Or am I looking in the wrong place?
--
Yarema
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 14:09:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA28472
for freebsd-current-outgoing; Mon, 9 Nov 1998 14:09:40 -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 OAA28466
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 14:09:38 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.58.114])
by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA6022; Mon, 9 Nov 1998 23:09:21 +0100
Message-ID: <XFMail.981109231327.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: <19981108220152.06173@breizh.prism.uvsq.fr>
Date: Mon, 09 Nov 1998 23:13:27 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Nicolas Souchu <nsouch@teaser.fr>
Subject: RE: ZIP+ and NatSemi parallel port chipst (was Re: ZIP, again)
Cc: FreeBSD Current <current@FreeBSD.ORG>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 08-Nov-98 Nicolas Souchu wrote:
> On Sun, Nov 08, 1998 at 07:56:42PM +0100, Jeroen Ruigrok/Asmodai wrote:
>>
>>On 08-Nov-98 Nicolas Souchu wrote:
>>> On Sun, Nov 08, 1998 at 12:21:53PM +0100, Jeroen Ruigrok/Asmodai wrote:
> I'm a bit curious.. is your parallel port chipset generic or what else?
> (send me your boot logs if you don't know)
ppc: parallel port found at 0x378
ppc0 at 0x378 irq 7 on isa
ppc0: W83877F chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
nlpt0: <generic printer> on ppbus 0
nlpt0: Interrupt-driven port
ppi0: <generic parallel i/o> on ppbus 0
imm0: <Iomega Matchmaker Parallel to SCSI interface> on ppbus 0
imm0: EPP 1.9 mode
There ye goes...
> In fact, we have some problems with NSC chips here.
>
> Anybody could report successfull ZIP+ detection with NatSemi chips?
So I guess it's detected alright... Now to know how to use it *G*
Can ye define NatSemi chips? Or is that short for National Semiconductor?
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl | Cum angelis et pueris,
Junior Network/Security Specialist | fideles inveniamur
*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 Nov 9 14:12:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA28820
for freebsd-current-outgoing; Mon, 9 Nov 1998 14:12:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from maui.net (maui.net [207.175.210.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28810
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 14:12:39 -0800 (PST)
(envelope-from langfod@maui.net)
Received: (from langfod@localhost)
by maui.net (8.8.7/8.8.5) id MAA21714;
Mon, 9 Nov 1998 12:12:19 -1000 (HST)
From: David Langford <langfod@maui.net>
Message-Id: <199811092212.MAA21714@maui.net>
Subject: Re: /usr/bin/groff: can't find `DESC' file
To: yds@ingress.net (Yarema)
Date: Mon, 9 Nov 1998 12:12:19 -1000 (HST)
Cc: current@FreeBSD.ORG
In-Reply-To: <03b901be0c2b$90ce0360$1f40e6cd@ichiban.ingress.com> from "Yarema" at Nov 9, 98 04:54:46 pm
X-blank-line: This space intentionaly left blank.
X-Mailer: ELM [version 2.4 PL24 ME8a]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
a.out works fine but Elf does not.
Trace shows that the path isnt being added to the file_open
with /usr/share/groff/font.
I am begining to wonder if it is a problem with the Elf C++ compiler.
I have been unable to figure out a solution on my machines.
This is very frustrating.
I sent similar email a couple of weeks ago and I only got one
reply. It mustnt be important to anyone.
-David Langford
langfod@dihelix.com
>typing man whatever-has-no-cat-page produces the following:
>
>/usr/bin/groff: can't find `DESC' file
>/usr/bin/groff:fatal error: invalid device `ascii'
>
>I did a make aout-to-elf some time late last week. Why is this happening?
>From what I can tell /usr/share/groff_font/ contains all the right stuff. No
>different from a 2.2.7 system. Or am I looking in the wrong place?
>
>--
>Yarema
>
>
>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 Nov 9 14:16:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA29061
for freebsd-current-outgoing; Mon, 9 Nov 1998 14:16:12 -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 OAA29056
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 14:16:10 -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 OAA01266;
Mon, 9 Nov 1998 14:13:51 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811092213.OAA01266@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: David Langford <langfod@maui.net>
cc: yds@ingress.net (Yarema), current@FreeBSD.ORG
Subject: Re: /usr/bin/groff: can't find `DESC' file
In-reply-to: Your message of "Mon, 09 Nov 1998 12:12:19 -1000."
<199811092212.MAA21714@maui.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 09 Nov 1998 14:13:51 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> a.out works fine but Elf does not.
>
> Trace shows that the path isnt being added to the file_open
> with /usr/share/groff/font.
>
> I am begining to wonder if it is a problem with the Elf C++ compiler.
>
> I have been unable to figure out a solution on my machines.
> This is very frustrating.
>
> I sent similar email a couple of weeks ago and I only got one
> reply. It mustnt be important to anyone.
No, it's just that it works fine for the rest of us, which simply
implies that you've done something wrong, intentionally or otherwise.
With no idea what you've done, nor how the problem might come about,
there's nothing that anyone else can offer to help you. Until one of
the people actually seeing the problem sits down and works it out,
you're stuck.
--
\\ 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 Mon Nov 9 14:25:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA00161
for freebsd-current-outgoing; Mon, 9 Nov 1998 14:25:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00151
for <current@freebsd.org>; Mon, 9 Nov 1998 14:25:43 -0800 (PST)
(envelope-from arno@heho.snv.jussieu.fr)
Received: from hall.snv.jussieu.fr (hall.snv.jussieu.fr [134.157.37.2])
by shiva.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id XAA20493
for <current@freebsd.org>; Mon, 9 Nov 1998 23:25:20 +0100 (CET)
Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.37.22])
by hall.snv.jussieu.fr (8.8.8/jtpda-5.2) with SMTP id XAA17227
for <current@freebsd.org>; Mon, 9 Nov 1998 23:24:55 +0100 (CET)
Received: by heho.snv.jussieu.fr (4.1/jf930126)
at Mon, 9 Nov 98 23:25:19 +0100
To: current@FreeBSD.ORG
Subject: Re: /usr/bin/groff: can't find `DESC' file
References: <199811092213.OAA01266@dingo.cdrom.com>
From: arno@heho.snv.jussieu.fr (Arno J. Klaassen)
Date: 09 Nov 1998 23:25:18 +0100
In-Reply-To: Mike Smith's message of Mon, 09 Nov 1998 14:13:51 -0800
Message-Id: <wpvhkosdv5.fsf@heho.snv.jussieu.fr>
Lines: 33
X-Mailer: Gnus v5.5/Emacs 20.2
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > [ .. can't find DESC file ..]
> > a.out works fine but Elf does not.
> >
> > Trace shows that the path isnt being added to the file_open
> > with /usr/share/groff/font.
> >
> > I am begining to wonder if it is a problem with the Elf C++ compiler.
> >
> > I have been unable to figure out a solution on my machines.
> > This is very frustrating.
> >
> > I sent similar email a couple of weeks ago and I only got one
> > reply. It mustnt be important to anyone.
>
> No, it's just that it works fine for the rest of us, which simply
> implies that you've done something wrong, intentionally or otherwise.
>
> With no idea what you've done, nor how the problem might come about,
> there's nothing that anyone else can offer to help you. Until one of
> the people actually seeing the problem sits down and works it out,
> you're stuck.
I got this error when comcping with CFLAGS='-O3 -pipe'.
rebuilding world with CFLAGS='-O -pipe' made it disappear.
introducing CXXFLAGS might be not a bad idea (if it does not
exist already in some form or another (I'm not yte completely
familiarised with th FreeBSD build environment)).
Arno
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 14:31:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA00723
for freebsd-current-outgoing; Mon, 9 Nov 1998 14:31:10 -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 OAA00717
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 14:31:06 -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 OAA01366;
Mon, 9 Nov 1998 14:29:38 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811092229.OAA01366@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: arno@heho.snv.jussieu.fr (Arno J. Klaassen)
cc: current@FreeBSD.ORG
Subject: Re: /usr/bin/groff: can't find `DESC' file
In-reply-to: Your message of "09 Nov 1998 23:25:18 +0100."
<wpvhkosdv5.fsf@heho.snv.jussieu.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 09 Nov 1998 14:29:38 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> > > [ .. can't find DESC file ..]
>
> > > a.out works fine but Elf does not.
> > >
> > > Trace shows that the path isnt being added to the file_open
> > > with /usr/share/groff/font.
> > >
> > > I am begining to wonder if it is a problem with the Elf C++ compiler.
> > >
> > > I have been unable to figure out a solution on my machines.
> > > This is very frustrating.
> > >
> > > I sent similar email a couple of weeks ago and I only got one
> > > reply. It mustnt be important to anyone.
> >
> > No, it's just that it works fine for the rest of us, which simply
> > implies that you've done something wrong, intentionally or otherwise.
> >
> > With no idea what you've done, nor how the problem might come about,
> > there's nothing that anyone else can offer to help you. Until one of
> > the people actually seeing the problem sits down and works it out,
> > you're stuck.
>
> I got this error when comcping with CFLAGS='-O3 -pipe'.
> rebuilding world with CFLAGS='-O -pipe' made it disappear.
>
> introducing CXXFLAGS might be not a bad idea (if it does not
> exist already in some form or another (I'm not yte completely
> familiarised with th FreeBSD build environment)).
'-Ox' is known to produce broken code for any value of 'x'. Only '-O'
is supported.
--
\\ 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 Mon Nov 9 15:11:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA04688
for freebsd-current-outgoing; Mon, 9 Nov 1998 15:11: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 PAA04683
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 15:11:28 -0800 (PST)
(envelope-from lh@aus.org)
Received: from bsd.aus.org (bsd.aus.org [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id RAA26504; Mon, 9 Nov 1998 17:52:51 -0500 (EST)
Message-ID: <XFMail.981109181059.lh@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: <wpvhkosdv5.fsf@heho.snv.jussieu.fr>
Date: Mon, 09 Nov 1998 18:10:59 -0500 (EST)
From: Luke <lh@aus.org>
To: (Arno J. Klaassen) <arno@heho.snv.jussieu.fr>
Subject: Re: /usr/bin/groff: can't find `DESC' file
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> > a.out works fine but Elf does not.
>> >
>> > Trace shows that the path isnt being added to the file_open
>> > with /usr/share/groff/font.
>> >
>> > I am begining to wonder if it is a problem with the Elf C++ compiler.
>> >
> I got this error when comcping with CFLAGS='-O3 -pipe'.
> rebuilding world with CFLAGS='-O -pipe' made it disappear.
>
> introducing CXXFLAGS might be not a bad idea (if it does not
> exist already in some form or another (I'm not yte completely
> familiarised with th FreeBSD build environment)).
I had a similar problem, I too used -O3 on my buildworld, but am now
using groff/man/troff built with -O3 and my src tree hasnt changed. I think I
remember nuking groff/troff in usr/obj worked.
---
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 Nov 9 15:14:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA04968
for freebsd-current-outgoing; Mon, 9 Nov 1998 15:14:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from float.dyn.ml.org (h24-64-194-119.gv.wave.shaw.ca [24.64.194.119])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04962
for <current@freebsd.org>; Mon, 9 Nov 1998 15:14:30 -0800 (PST)
(envelope-from jake@float.dyn.ml.org)
Received: from float.dyn.ml.org (jake@localhost [127.0.0.1])
by float.dyn.ml.org (8.9.1/8.9.1) with ESMTP id PAA00738
for <current@freebsd.org>; Mon, 9 Nov 1998 15:14:07 -0800 (PST)
(envelope-from jake@float.dyn.ml.org)
Message-Id: <199811092314.PAA00738@float.dyn.ml.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: current@FreeBSD.ORG
Subject: Re: /kernel: arp: 192.168.1.188 is on de1 but got reply from
00:c0:4f:a4:81:2d on de0
In-reply-to: Your message of "Mon, 09 Nov 1998 20:25:48 EST."
<Pine.BSF.4.05.9811092017590.9547-100000@blondie.ottawa.cc>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 09 Nov 1998 15:14:06 -0800
From: Jake <jake@checker.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Furthermore but unrelated, that ISP uses private net number for
> their routers !!!
I get cable modem service from Shaw in Victoria, and indeed at least one
of the routers uses private net numbers.
traceroute to gulf.csc.UVic.CA (142.104.105.200), 30 hops max, 40 byte packets
1 h24-64-192-1.ed.wave.shaw.ca (24.64.192.1) 16.485 ms 16.200 ms 17.417 ms
2 r1-fe3-0-0-100bt.bc.home.net (24.64.3.193) 18.743 ms 21.709 ms 17.316 ms
3 10.0.186.69 (10.0.186.69) 20.018 ms 21.793 ms 23.522 ms
<-----------
4 198.231.127.65 (198.231.127.65) 24.411 ms 22.439 ms 23.999 ms
5 172.16.4.86 (172.16.4.86) 24.323 ms 25.528 ms 23.130 ms
6 c7507-at-home.hc.BC.net (134.87.99.2) 47.835 ms 44.574 ms 50.165 ms
7 gigapop-vlan2.hc.BC.net (207.23.240.235) 47.524 ms 51.419 ms 47.499 ms
8 CF-HCrtr.atm.BC.net (207.23.240.6) 50.032 ms 44.950 ms 45.670 ms
9 UVicrtr.atm.BC.net (207.23.240.98) 51.829 ms 52.185 ms 50.211 ms
10 gulf.csc.UVic.CA (142.104.105.200) 52.174 ms 54.995 ms 51.029 ms
I haven't tried natd yet, but I assume this'll come up when I do.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 15:25:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA06155
for freebsd-current-outgoing; Mon, 9 Nov 1998 15:25:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp2.erols.com (smtp2.erols.com [207.172.3.235])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06142
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 15:25:42 -0800 (PST)
(envelope-from shmit@natasya.noc.erols.net)
Received: from natasya.noc.erols.net (natasya.noc.erols.net [207.172.25.236])
by smtp2.erols.com (8.8.8/8.8.5) with ESMTP id SAA01240;
Mon, 9 Nov 1998 18:26:59 -0500 (EST)
Received: (from shmit@localhost)
by natasya.noc.erols.net (8.9.1/8.9.1) id SAA09191;
Mon, 9 Nov 1998 18:25:26 -0500 (EST)
Message-ID: <19981109182526.E901@kublai.com>
Date: Mon, 9 Nov 1998 18:25:26 -0500
From: Brian Cully <shmit@kublai.com>
To: "Arno J. Klaassen" <arno@heho.snv.jussieu.fr>, current@FreeBSD.ORG
Subject: Re: /usr/bin/groff: can't find `DESC' file
Reply-To: shmit@kublai.com
References: <199811092213.OAA01266@dingo.cdrom.com> <wpvhkosdv5.fsf@heho.snv.jussieu.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <wpvhkosdv5.fsf@heho.snv.jussieu.fr>; from Arno J. Klaassen on Mon, Nov 09, 1998 at 11:25:18PM +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 Mon, Nov 09, 1998 at 11:25:18PM +0100, Arno J. Klaassen wrote:
> I got this error when comcping with CFLAGS='-O3 -pipe'.
> rebuilding world with CFLAGS='-O -pipe' made it disappear.
Don't do that. -On is known to produce bad code.
> introducing CXXFLAGS might be not a bad idea (if it does not
> exist already in some form or another (I'm not yte completely
> familiarised with th FreeBSD build environment)).
CXXFLAGS exists. Unfortunately, it over-rides CFLAGS for C++ objects,
so many points in your typical `make world' fail (groff is a fine
example). The only way around it, that I can discern, is to
introduce a standard INCS and OPTS variable that gets added by
bsd.prog.mk and bsd.lib.mk to CFLAGS and CXXFLAGS. Of course, you'd
still have to convert the old makefiles to take advantage of the
new syntax. You'd also have to convince a bunch of decade-long BSD
bigots that this is The Right Thing To Do (that includes me ;-)).
Or, you could hack each of the problematic Makefiles in a way
similar to the one described above. This'll probably get you a lot
farther than trying to change the way things have been done for
the last ten years.
--
Brian Cully <shmit@rcn.com>
They Might Be Giant's Dial-a-Song service: (718) 387-6962.
``Free when you call from work!''
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 15:31:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA06791
for freebsd-current-outgoing; Mon, 9 Nov 1998 15:31:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06785
for <freebsd-current@freebsd.org>; Mon, 9 Nov 1998 15:31:41 -0800 (PST)
(envelope-from jreynold@sedona.ch.intel.com)
Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21])
by pan.ch.intel.com (8.8.6/8.8.5) with ESMTP id XAA04010
for <freebsd-current@freebsd.org>; Mon, 9 Nov 1998 23:31:26 GMT
Received: from hip186.ch.intel.com (jreynold@hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1a-chandler01) with ESMTP id QAA18243 for <freebsd-current@freebsd.org>; Mon, 9 Nov 1998 16:31:25 -0700 (MST)
Received: by hip186.ch.intel.com (8.8.6/)
id SAA17044; Mon, 9 Nov 1998 18:31:25 -0500 (EST)
From: John Reynolds~ <jreynold@sedona.ch.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <13895.31563.888702.914625@hip186.ch.intel.com>
Date: Mon, 9 Nov 1998 16:31:23 -0700 (MST)
To: freebsd-current@FreeBSD.ORG
Subject: Re: 3.0-CURRENT: Adaptec 1540 not detected (with workaround)
X-Mailer: VM 6.62 under Emacs 19.34.1
X-BabyCountDown: 31 days
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I have just upgraded by 2.2-STABLE machine to 3.0-CURRENT. It couldn't boot
> either kernel.GENERIC or the custom kernel that I built. It said that it
> didn't detect my Adaptec 1540 (and then paniced with "cannot mount root").
> I even specified the exact port address, IRQ and DRQ in userconfig. Still
> no go. It used to work fine with 2.2 and was correctly detected by the
> kernel on the 3.0 boot floppy.
>
> Eventually I found the problem. In /usr/src/sys/dev/aha/aha.c there is some
> code that attempts to distinguish between Adaptec and Buslogic adaptors.
> This was failing. I'm not sure what model my adaptor is (I think it's an
> 'A') but it is a genuine Adaptec. Hence the comment in the code about
> cloned cards may apply to some genuine ones also.
COOL! So there *was* a problem after all! I saw the exact same things
happening to my 1542C (not even using the exact IRQ and DRQ values in
userconfig helped). Sounds like this was a real problem. Is somebody going
to commit the changes that gfm@mira.net (Graham Menhennitt) provided? If so,
will another "official" 3.0 boot floppy be rolled with this change? I ask
only because I don't know if using a SNAP or CURRENT boot.flp with the 3.0
CD-ROMs (whenever they get to my door) would be a Bad Thing(tm) or
not. Probably not? Right now, the 3.0-RELEASE boot.flp will not pick up
Adaptec 154x cards at all.
-Jr
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| John Reynolds CEG, CCE, Next Generation Flows, HLA |
| Intel Corporation MS: CH6-210 Phone: 554-9092 pgr: 868-6512 |
| jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 15:56:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA09262
for freebsd-current-outgoing; Mon, 9 Nov 1998 15:56:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dorsey.fcc.net (dorsey.fcc.net [207.198.253.29])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09255
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 15:56:12 -0800 (PST)
(envelope-from nathan@rockland.net)
Received: from noc.fcc.net ([207.198.253.18]) by dorsey.fcc.net
(Post.Office MTA v3.5.2 release 221 ID# 0-55805U3500L350S0V35)
with ESMTP id net; Mon, 9 Nov 1998 18:55:15 -0500
Received: (from nathan@localhost)
by noc.fcc.net (8.9.1/8.9.1) id SAA08881;
Mon, 9 Nov 1998 18:56:38 -0500 (EST)
Message-ID: <19981109185638.B8871@rtfm.net>
Date: Mon, 9 Nov 1998 18:56:38 -0500
From: Nathan Dorfman <nathan@rtfm.net>
To: Alfred Perlstein <bright@hotjobs.com>,
"David E. Cross" <crossd@phoenix.cs.rpi.edu>
Cc: current@FreeBSD.ORG
Subject: Re: O_SYNC
References: <199811072154.QAA00324@phoenix.cs.rpi.edu> <Pine.BSF.4.05.9811081043010.19817-100000@porkfriedrice.ny.genx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.05.9811081043010.19817-100000@porkfriedrice.ny.genx.net>; from Alfred Perlstein on Sun, Nov 08, 1998 at 10:44:24AM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 08, 1998 at 10:44:24AM -0500, Alfred Perlstein wrote:
>
> Yes, however every other OS defines it at "O_SYNC" why are we different?
> or, if there is a reason, why isn't there a compatibility #define?
>
> can someone check this on netbsd/open bsd/os ? is it bsd or us?
NetBSD 1.3.2:
fcntl.h:92:#define O_SYNC 0x0080 /* synchronous writes */
fcntl.h:127:#define FFSYNC O_SYNC /* kernel */
fcntl.h:129:#define O_FSYNC O_SYNC /* compat */
> Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com
> -- There are operating systems, and then there's FreeBSD.
> -- http://www.freebsd.org/ 3.0-current
>
> On Sat, 7 Nov 1998, David E. Cross wrote:
>
> > Is 'O_FSYNC" what you are looking for?
> >
> > #define O_FSYNC 0x0080 /* synchronous writes */
> >
> >
> > --
> > David Cross
> >
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 16:00:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA09562
for freebsd-current-outgoing; Mon, 9 Nov 1998 16:00:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09557
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 16:00:35 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id TAA17020;
Mon, 9 Nov 1998 19:03:21 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Mon, 9 Nov 1998 19:03:20 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Nathan Dorfman <nathan@rtfm.net>
cc: "David E. Cross" <crossd@phoenix.cs.rpi.edu>, current@FreeBSD.ORG
Subject: Re: O_SYNC
In-Reply-To: <19981109185638.B8871@rtfm.net>
Message-ID: <Pine.BSF.4.05.9811091901470.22497-100000@porkfriedrice.ny.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, 9 Nov 1998, Nathan Dorfman wrote:
> > > Is 'O_FSYNC" what you are looking for?
> > >
> > > #define O_FSYNC 0x0080 /* synchronous writes */
> >
> > Yes, however every other OS defines it at "O_SYNC" why are we different?
> > or, if there is a reason, why isn't there a compatibility #define?
> >
> > can someone check this on netbsd/open bsd/os ? is it bsd or us?
>
> NetBSD 1.3.2:
> fcntl.h:92:#define O_SYNC 0x0080 /* synchronous writes */
> fcntl.h:127:#define FFSYNC O_SYNC /* kernel */
> fcntl.h:129:#define O_FSYNC O_SYNC /* compat */
>
anyone want to commit this to make FreeBSD a bit more port-friendly?
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 16:00:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA09758
for freebsd-current-outgoing; Mon, 9 Nov 1998 16:00:47 -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 QAA09611
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 16:00:41 -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 QAA07389;
Mon, 9 Nov 1998 16:00:01 -0800 (PST)
(envelope-from dwhite@resnet.uoregon.edu)
Date: Mon, 9 Nov 1998 16:00:00 -0800 (PST)
From: Doug White <dwhite@resnet.uoregon.edu>
To: Archie Cobbs <archie@whistle.com>
cc: alexandr@mail.eecis.udel.edu, current@FreeBSD.ORG
Subject: Re: ThinkPad 600E
In-Reply-To: <199811091639.IAA01712@bubba.whistle.com>
Message-ID: <Pine.BSF.4.03.9811091559390.3471-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 Mon, 9 Nov 1998, Archie Cobbs wrote:
> Jerry Alexandratos writes:
> > So, looks like it'll be a 600E. I'm excited because it doesn't have any
> > of that Mwave crap!!! However, it only comes with a DVD drive. Will
> > -current recognize the DVD drive as a CD-ROM drive? If not, any ideas
> > on how far away we are from getting DVD support?
>
> My work-sponsored laptop has a DVD as well, which is recognized
> as a normal CD-ROM and works fine as such:
>
> wdc1 at 0x170-0x177 irq 15 on isa
> wdc1: unit 0 (atapi): <MATSHITADVD-ROM SR-8171/058A>, removable, accel, dma, iordis
Hm, it does attach as wcd0? Just curious to see the wcd* messages
printed below this one.
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 Mon Nov 9 16:04:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA10658
for freebsd-current-outgoing; Mon, 9 Nov 1998 16:04:12 -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 QAA10635
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 16:04:07 -0800 (PST)
(envelope-from sthaug@nethelp.no)
From: sthaug@nethelp.no
Received: (qmail 12426 invoked by uid 1001); 10 Nov 1998 00:03:46 +0000 (GMT)
To: nathan@rtfm.net
Cc: current@FreeBSD.ORG
Subject: Re: O_SYNC
In-Reply-To: Your message of "Mon, 9 Nov 1998 18:56:38 -0500"
References: <19981109185638.B8871@rtfm.net>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Tue, 10 Nov 1998 01:03:46 +0100
Message-ID: <12424.910656226@verdi.nethelp.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Yes, however every other OS defines it at "O_SYNC" why are we different?
> > or, if there is a reason, why isn't there a compatibility #define?
> >
> > can someone check this on netbsd/open bsd/os ? is it bsd or us?
>
> NetBSD 1.3.2:
> fcntl.h:92:#define O_SYNC 0x0080 /* synchronous writes */
> fcntl.h:127:#define FFSYNC O_SYNC /* kernel */
> fcntl.h:129:#define O_FSYNC O_SYNC /* compat */
BSD/OS 3.1 fcntl.h:
#define O_FSYNC 0x0080 /* synchronous writes */
#define FFSYNC O_FSYNC /* kernel */
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 Mon Nov 9 16:30:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA14752
for freebsd-current-outgoing; Mon, 9 Nov 1998 16:30:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.gtn.com (mail.gtn.com [194.77.0.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14726
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 16:30:49 -0800 (PST)
(envelope-from andreas@klemm.gtn.com)
Received: (from uucp@localhost)
by mail.gtn.com (8.8.6/8.8.6) with UUCP id BAA11990
for current@FreeBSD.ORG; Tue, 10 Nov 1998 01:30:11 +0100 (MET)
Received: (from andreas@localhost)
by klemm.gtn.com (8.9.1/8.9.1) id BAA05729
for current@FreeBSD.ORG; Tue, 10 Nov 1998 01:18:09 +0100 (CET)
(envelope-from andreas)
Message-ID: <19981110011809.A5722@klemm.gtn.com>
Date: Tue, 10 Nov 1998 01:18:09 +0100
From: Andreas Klemm <andreas@klemm.gtn.com>
To: current@FreeBSD.ORG
Subject: [make release] disklabel fails creating boot.std floppy and no space
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
X-Disclaimer: A free society is one where it is safe to be unpopular
X-Operating-System: FreeBSD 3.0-CURRENT SMP
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Just wanted to inform you...
c -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitializ
ed -Wformat -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../inc
lude -DKERNEL -include opt_global.h -aout vers.c
loading kernel
rearranging symbols
text data bss dec hex
1458176 1581056 112060 3151292 3015bc
./dumpnlist /R/stage/boot.std/kernel > /tmp/mnt_xx/stand/symbols
./write_mfs_in_kernel /R/stage/boot.std/kernel fs-image.std
kzip -v /R/stage/boot.std/kernel
real kernel start address will be: 0x100000
real kernel end address will be: 0x4015bc
kzip data start address will be: 0x2ab57e
kzip data end address will be: 0x409510
sh -e /usr/src/release/doFS.sh /R/stage /mnt 1440 /R/stage/boot.std 80000 minim
um
disklabel: ioctl DIOCWLABEL: Operation not supported by device
^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Warning: Block size restricts cylinders per group to 9.
/dev/rvn0c: 2880 sectors in 1 cylinders of 1 tracks, 2880 sectors
1.4MB in 1 cyl groups (9 c/g, 12.66MB/g, 32 i/g)
super-block backups (for fsck -b #) at:
32,
/mnt: write failed, file system is full
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cpio: write error: No space left on device
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
--
Andreas Klemm http://www.FreeBSD.ORG/~andreas
What gives you 90% more speed, for example, in kernel compilation ?
http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html
"NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP''
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 17:00:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA17345
for freebsd-current-outgoing; Mon, 9 Nov 1998 17:00:32 -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 RAA17320
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 17:00:20 -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 TAA26308;
Mon, 9 Nov 1998 19:59:34 -0500 (EST)
Date: Mon, 9 Nov 1998 19:59:34 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: John Fieber <jfieber@indiana.edu>
cc: garman@earthling.net, current@FreeBSD.ORG, julian@whistle.com,
wollman@khavrinen.lcs.mit.edu
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.BSF.4.05.9811090932230.462-100000@fallout.campusview.indiana.edu>
Message-ID: <Pine.BSF.4.05.9811091953110.26160-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, 9 Nov 1998, John Fieber wrote:
> On Sun, 8 Nov 1998, Brian Feldman wrote:
>
> > Device 1K-blocks Used Avail Capacity Type
> > /dev/wd0s1b 102400 12300 89972 12% Interleaved
> > /dev/wd1s1b 102400 12408 89864 12% Interleaved
> > Total 204544 24708 179836 12%
> > This is normal usage after
> > swap_pager: suggest more swap space: 157 MB
> > swap_pager: out of swap space
> > pid 5795 (memory), uid 1000, was killed: out of swap space
>
> I don't think this illustrates bug we are trying to smoke out
> though. This is showing the "memory" process as being killed,
> presumably because it went overboard on memory consumption.
>
> The dying daemon bug seems to manifists itself in the death of
The point of "memory" is to eat up ram. Watch:
#include <stdio.h>
#define SIZE 1024
void
main(void) {
int count, yep = 0;
void *stfu[102400];
for (count = 0; count < 102400; count++) {
if((stfu[count] = malloc(SIZE)) != (void *) NULL) {
printf("%p (%i) malloc'd\n", stfu[count], count);
bzero(stfu[count], SIZE);
yep++;
}
else
break;
}
for (count = 0; count < yep; count++) {
free(stfu[count]);
printf("%i free'd\n", count);
}
if (yep != 102400) {
printf("mallocs failed at %i", yep);
exit (1);
}
else
exit (0);
}
> innocent bystander
> processes and usually by a signal 11, not by
> "out of swap space". Note these two observations:
The point of the memory starvation was to _bring_up_ things like this.
Indeed, after the memory starvation had occurred, no processes ata ll were
killed.
>
> Date: Sun, 8 Nov 1998 15:26:48 -0800 (PST)
> From: Julian Elischer <julian@whistle.com>
> Message-ID: <Pine.BSF.3.95.981108152353.12341D-100000@current1.whistle.com>
>
> It's been a while since we looked at it closely but it appeared
> that a page of useful memeory was suddenly unmapped from the
> process.
>
> Date: Sun, 8 Nov 1998 23:17:00 -0500 (EST)
> From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
> Message-Id: <199811090417.XAA13563@khavrinen.lcs.mit.edu>
>
> It seems, so far as I was able to characterize, to happen to
> daemons which are *swapped out* at the time of the memory
> shortage. If it's active enough to still be in core, it doesn't
> get spammed.
>
> -john
According to these e-mails, I have been attempting the same scenarios,
but without the same effects.
Cheers,
Brian Feldman
>
>
> 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 Nov 9 17:02:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA17651
for freebsd-current-outgoing; Mon, 9 Nov 1998 17:02:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17644
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 17:02:48 -0800 (PST)
(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
by dan.emsphone.com (8.9.1/8.9.1) id TAA23189;
Mon, 9 Nov 1998 19:02:26 -0600 (CST)
Date: Mon, 9 Nov 1998 19:02:25 -0600
From: Dan Nelson <dnelson@emsphone.com>
To: sthaug@nethelp.no, nathan@rtfm.net
Cc: current@FreeBSD.ORG
Subject: Re: O_SYNC
Message-ID: <19981109190225.A22989@emsphone.com>
References: <19981109185638.B8871@rtfm.net> <12424.910656226@verdi.nethelp.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.3i
In-Reply-To: <12424.910656226@verdi.nethelp.no>; from "sthaug@nethelp.no" on Tue Nov 10 01:03:46 GMT 1998
X-OS: FreeBSD 2.2.7-STABLE
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In the last episode (Nov 10), sthaug@nethelp.no said:
> > > Yes, however every other OS defines it at "O_SYNC" why are we different?
> > > or, if there is a reason, why isn't there a compatibility #define?
> > >
> > > can someone check this on netbsd/open bsd/os ? is it bsd or us?
> >
> > NetBSD 1.3.2:
> > fcntl.h:92:#define O_SYNC 0x0080 /* synchronous writes */
> > fcntl.h:127:#define FFSYNC O_SYNC /* kernel */
> > fcntl.h:129:#define O_FSYNC O_SYNC /* compat */
>
> BSD/OS 3.1 fcntl.h:
>
> #define O_FSYNC 0x0080 /* synchronous writes */
> #define FFSYNC O_FSYNC /* kernel */
It's O_SYNC on Dec OSF/1, SCO Open Server, and SunOS too.
-Dan Nelson
dnelson@emsphone.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 17:07:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA18162
for freebsd-current-outgoing; Mon, 9 Nov 1998 17: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 RAA18115
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 17: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 UAA26425;
Mon, 9 Nov 1998 20:06:13 -0500 (EST)
Date: Mon, 9 Nov 1998 20:06:13 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Alfred Perlstein <bright@hotjobs.com>
cc: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>, current@FreeBSD.ORG
Subject: Re: newer gcc?
In-Reply-To: <Pine.BSF.4.05.9811091003040.22497-100000@porkfriedrice.ny.genx.net>
Message-ID: <Pine.BSF.4.05.9811092000470.26160-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, 9 Nov 1998, Alfred Perlstein wrote:
>
> On Mon, 9 Nov 1998, Phillip Salzman wrote:
>
> > > Has there been any thought to jumping to a newer version of gcc,
> > > specifically egcs?
> >
> > Doesn't egcs require an ELF filetype? Currently many people
> > are still a.out. I'm sure it will change in the future.
>
> Well i only brought this up again for 2 reasons, as i know it has been
> discussed to death in the past, however with the move to ELF and perl5 i
> thought... what the hell :)
Of course, when 3.0 is the branch people are encouraged to move to, and as
it's already entirely ELF (except the boot floppies, but still...) it will
be safe to do this. But of course, the policy of least surprise is highly
important in this kind of thing
>
> Anyhow:
>
> a) egcs is a bit more improved than gcc in terms of c++ support, and more
> features/optimizations.
The "features/optimization" part is very debatable. For C code, I tend to
get much inferior assembly output using egcs, or even gcc 2.8.1, rather
than 2.7.2.1.x, even if of course egcs _is_ better for C++, as I've seen.
Have you actually successfully compiled an entire world with egcs? Let me
know when you do (kernel too).
>
> b) i thought the move to elf was so that we _could_ better use the newer
> GNU tools.
This is correct, but you're kinda mistaken here: the move to elf is to
have a newer TOOLCHAIN, which is mainly binutils (GNU ld, as, obj*, gdb,
bfd) not for the latest compiler. For this matter TenDRA is a rather nice
compiler, but has generated entirely incorrect code at times, so for right
now is best as a linter.
>
> The reason i was asking is that i may bmake it and stick it into my tree,
> if i can produce a "release" build using it maybe people would show more
> interest.
>
> -Alfred
Cheers,
Brian Feldman
>
>
> 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 Nov 9 17:25:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA20238
for freebsd-current-outgoing; Mon, 9 Nov 1998 17:25:26 -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 RAA20231
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 17:25:23 -0800 (PST)
(envelope-from lee@st-lcremean.tidalwave.net)
Received: (from lee@localhost)
by st-lcremean.tidalwave.net (8.9.1/8.8.8) id UAA03133;
Mon, 9 Nov 1998 20:24:32 -0500 (EST)
(envelope-from lee)
Message-ID: <19981109202432.A3125@tidalwave.net>
Date: Mon, 9 Nov 1998 20:24:32 -0500
From: Lee Cremeans <lee@st-lcremean.tidalwave.net>
To: Brian Feldman <green@unixhelp.org>, John Fieber <jfieber@indiana.edu>
Cc: garman@earthling.net, current@FreeBSD.ORG, julian@whistle.com,
wollman@khavrinen.lcs.mit.edu
Subject: Re: The infamous dying daemons bug
Reply-To: lcremean@tidalwave.net
References: <Pine.BSF.4.05.9811090932230.462-100000@fallout.campusview.indiana.edu> <Pine.BSF.4.05.9811091953110.26160-100000@janus.syracuse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.05.9811091953110.26160-100000@janus.syracuse.net>; from Brian Feldman on Mon, Nov 09, 1998 at 07:59:34PM -0500
X-OS: FreeBSD 3.0-CURRENT
X-Evil: microsoft.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Nov 09, 1998 at 07:59:34PM -0500, Brian Feldman wrote:
>
> According to these e-mails, I have been attempting the same scenarios,
> but without the same effects.
Just out of curiosity, Brian, what processor and motherboard/chipset do you
have? I think that, while we have looked at processors, we haven't examined
motherboards.
FWIW, I have a AMD K6-2 and an Acer Aladdin IV+ chipset, and I have seen
inetd go into "junk pointer" mode before. It was after Netscape munched all
my swap.
--
Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)
A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did
$++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net
http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 17:39:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA21526
for freebsd-current-outgoing; Mon, 9 Nov 1998 17:39: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 RAA21516
for <current@freebsd.org>; Mon, 9 Nov 1998 17:39:50 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from spectrum.physics.adelaide.edu.au (spectrum [129.127.36.1])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id MAA18456;
Tue, 10 Nov 1998 12:09:29 +1030 (CST)
Received: from localhost by spectrum.physics.adelaide.edu.au; (5.65/1.1.8.2/26Jun95-0330PM)
id AA09762; Tue, 10 Nov 1998 12:09:28 +1030
Date: Tue, 10 Nov 1998 12:09:25 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: Alfred Perlstein <bright@hotjobs.com>,
Phillip Salzman <psalzman@gamefish.pcola.gulf.net>,
current@FreeBSD.ORG
Subject: Re: newer gcc?
In-Reply-To: <7531.910631245@time.cdrom.com>
Message-Id: <Pine.OSF.4.05.9811101205130.9655-100000@spectrum.physics.adelaide.edu.au>
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, 9 Nov 1998, Jordan K. Hubbard wrote:
> > The reason i was asking is that i may bmake it and stick it into my tree,
>
> That's a bit premature. I'd be more interested if you could even build
> the world from egcs installed in /usr/local.
>From memory (I don't have the list with me), the following things do not
compile with the current egcs port and die with various errors:
lib/libc
lib/libc_r
lib/libstand
games/bs
games/<one other one>
gnu/lib/libg++
gnu/lib/libstd++
gnu/usr.bin/groff
sys/<lots of stuff> - the boot code dies with errors, and the modules die
because of the -elf directive or something
lkm/* because of -aout
I've not looked into the exact causes and whether they're something I can
easily submit fixes for myself, but that's the list :-) Apart from that
everything else seems to compile and run just fine (-O2 -mpentium
-march=pentium)..
Kris
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 17:43:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA22139
for freebsd-current-outgoing; Mon, 9 Nov 1998 17:43:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22132
for <current@freebsd.org>; Mon, 9 Nov 1998 17:43:01 -0800 (PST)
(envelope-from archer@grape.carrier.kiev.ua)
Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111])
by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) with ESMTP id DAA09815;
Tue, 10 Nov 1998 03:42:36 +0200 (EET)
(envelope-from archer@grape.carrier.kiev.ua)
Received: (from uucp@localhost)
by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id DAA05575;
Tue, 10 Nov 1998 03:40:45 +0200 (EET)
(envelope-from archer@grape.carrier.kiev.ua)
Received: (from archer@localhost)
by grape.carrier.kiev.ua (8.9.1/8.9.1) id DAA00563;
Tue, 10 Nov 1998 03:36:28 +0200 (EET)
(envelope-from archer)
Date: Tue, 10 Nov 1998 03:36:28 +0200 (EET)
From: Alexander Litvin <archer@lucky.net>
Message-Id: <199811100136.DAA00563@grape.carrier.kiev.ua>
To: Luoqi Chen <luoqi@watermarkgroup.com>
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
X-Newsgroups: grape.freebsd.current
In-Reply-To: <199811092056.PAA22043@lor.watermarkgroup.com>
Organization: Lucky Grape
User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386))
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <199811092056.PAA22043@lor.watermarkgroup.com> you wrote:
>> Totally unrelated to the problem. It seems, so far as I was able to
>> characterize, to happen to daemons which are *swapped out* at the time
>> of the memory shortage. If it's active enough to still be in core, it
>> doesn't get spammed.
>>
LC> I went through swap_pager.c today and found a problem that could potentially
LC> have bad consequences. It's a comparison between page index in the swap pager
LC> and the size of the vm object, since a shadowed object may have a non-zero
LC> paging offset with respect to the swap pager, the comparison should have taken
LC> the offset into account. This piece of code has been there since '95, so
LC> I can't say if this was responsible for the daemon dying problem.
It is definitely not responsible. At least for this particular problem,
though it may fix something else ;)
After applying the patch, and artificially exhausting memory, I promptly
got:
Nov 10 03:15:34 grape /kernel: swap_pager: suggest more swap space: 61 MB
Nov 10 03:16:26 grape /kernel: pid 310 (sendmail), uid 0: exited on signal 11
Nov 10 03:17:26 grape /kernel: pid 311 (sendmail), uid 0: exited on signal 11
Nov 10 03:18:25 grape /kernel: pid 313 (sendmail), uid 0: exited on signal 11
Nov 10 03:19:25 grape /kernel: pid 353 (sendmail), uid 0: exited on signal 11
Nov 10 03:20:26 grape /kernel: pid 394 (sendmail), uid 0: exited on signal 11
LC> -lq
LC> Index: swap_pager.c
LC> ===================================================================
LC> RCS file: /home/ncvs/src/sys/vm/swap_pager.c,v
LC> retrieving revision 1.103
LC> diff -u -r1.103 swap_pager.c
LC> --- swap_pager.c 1998/10/31 15:31:28 1.103
LC> +++ swap_pager.c 1998/11/09 11:02:54
LC> @@ -349,7 +349,7 @@
LC> *valid = 0;
LC> ix = pindex / SWB_NPAGES;
LC> if ((ix >= object->un_pager.swp.swp_nblocks) ||
LC> - (pindex >= object->size)) {
LC> + (pindex >= object->size + OFF_TO_IDX(object->paging_offset))) {
LC> return (FALSE);
LC> }
LC> swb = &object->un_pager.swp.swp_blocks[ix];
LC> @@ -1227,8 +1227,8 @@
LC> * intent of this code is to allocate small chunks for
LC> * small objects)
LC> */
LC> - if ((off == 0) && ((fidx + ntoget) > object->size)) {
LC> - ntoget = object->size - fidx;
LC> + if ((off == 0) && ((fidx + ntoget) > object->size + paging_pindex)) {
LC> + ntoget = object->size + paging_pindex - fidx;
LC> }
LC> retrygetspace:
LC> if (!swap_pager_full && ntoget > 1 &&
---
We are the people our parents warned us about.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 17:45:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA22491
for freebsd-current-outgoing; Mon, 9 Nov 1998 17:45:48 -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 RAA22486
for <current@freebsd.org>; Mon, 9 Nov 1998 17:45:44 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from spectrum.physics.adelaide.edu.au (spectrum [129.127.36.1])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id MAA11051;
Tue, 10 Nov 1998 12:15:21 +1030 (CST)
Received: from localhost by spectrum.physics.adelaide.edu.au; (5.65/1.1.8.2/26Jun95-0330PM)
id AA09781; Tue, 10 Nov 1998 12:15:19 +1030
Date: Tue, 10 Nov 1998 12:15:17 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
To: Brian Feldman <green@unixhelp.org>
Cc: Alfred Perlstein <bright@hotjobs.com>,
Phillip Salzman <psalzman@gamefish.pcola.gulf.net>,
current@FreeBSD.ORG
Subject: Re: newer gcc?
In-Reply-To: <Pine.BSF.4.05.9811092000470.26160-100000@janus.syracuse.net>
Message-Id: <Pine.OSF.4.05.9811101212170.9655-100000@spectrum.physics.adelaide.edu.au>
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, 9 Nov 1998, Brian Feldman wrote:
> The "features/optimization" part is very debatable. For C code, I tend to
> get much inferior assembly output using egcs, or even gcc 2.8.1, rather
> than 2.7.2.1.x, even if of course egcs _is_ better for C++, as I've seen.
> Have you actually successfully compiled an entire world with egcs? Let me
> know when you do (kernel too).
An egcs ELF kernel compiled and booted fine for me after disabling
-Wformat-extensions in kern.mk (gave me a lot of warnings about extra
arguments to format() or something, which I didnt bother to understand -- but
it worked). Perhaps I'll run with such a kernel for a while to see if I notice
anything unstable about it.
Kris
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 17:54:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA23325
for freebsd-current-outgoing; Mon, 9 Nov 1998 17:54:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23308
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 17:54:47 -0800 (PST)
(envelope-from john.saunders@scitec.com.au)
Received: by firewall.scitec.com.au; id MAA20177; Tue, 10 Nov 1998 12:54:28 +1100 (EST)
Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2)
id xma020161; Tue, 10 Nov 98 12:54:13 +1100
Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id MAA03156; Tue, 10 Nov 1998 12:54:13 +1100
From: "John Saunders" <john.saunders@scitec.com.au>
To: "Alexander B. Povolotsky" <tarkhil@synchroline.ru>
Cc: <current@FreeBSD.ORG>
Subject: RE: weird problem - maybe in my head?
Date: Tue, 10 Nov 1998 12:54:12 +1100
Message-ID: <001001be0c4d$03c611c0$6cb611cb@saruman.scitec.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4
Importance: Normal
In-Reply-To: <Pine.BSF.4.05.9811091106420.311-100000@trifork.gu.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On Mon, 9 Nov 1998, Alexander B. Povolotsky wrote:
>
> > boot.flp (pathname doesn't mean) result in fetching about 10000 bytes
(ftom
> > 9288 to 10136), and after that point NOTHING is transferred. Server
doesn't
> > matter.
[snip]
> Maybe you have a braindamaged ISND TA or CSU/DSU or sattelite
> modem somewhere on your way? I recall some troubles like yours
> were due to crazy hardware.
Could very well be. I had a problem a while back that whenever I
displayed my mgetty logs my modem would hang up. It turns out that
the brain dead modem caught the +++ sequence and hung up. Until
I could replace the modem I simply used ssh to login so that the
encryption garbled the +++ sequence.
-- . +-------------------------------------------------------+
,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au |
/ Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 |
\_,--\_/ | "By the time you make ends meet, they move the ends." |
v +-------------------------------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 18:03:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA24465
for freebsd-current-outgoing; Mon, 9 Nov 1998 18:03:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24451
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 18:02:57 -0800 (PST)
(envelope-from andyf@speednet.com.au)
Received: from localhost (andyf@localhost)
by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id NAA07713;
Tue, 10 Nov 1998 13:00:44 +1100 (EST)
X-Authentication-Warning: backup.zippynet.iol.net.au: andyf owned process doing -bs
Date: Tue, 10 Nov 1998 13:00:44 +1100 (EST)
From: Andy Farkas <andyf@speednet.com.au>
X-Sender: andyf@backup.zippynet.iol.net.au
To: John Saunders <john.saunders@scitec.com.au>
cc: "Alexander B. Povolotsky" <tarkhil@synchroline.ru>, current@FreeBSD.ORG
Subject: RE: weird problem - maybe in my head?
In-Reply-To: <001001be0c4d$03c611c0$6cb611cb@saruman.scitec.com.au>
Message-ID: <Pine.BSF.4.05.9811101258090.7690-100000@backup.zippynet.iol.net.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
ATS2=255 then write config ...
> Could very well be. I had a problem a while back that whenever I
> displayed my mgetty logs my modem would hang up. It turns out that
> the brain dead modem caught the +++ sequence and hung up. Until
> I could replace the modem I simply used ssh to login so that the
> encryption garbled the +++ sequence.
>
> -- . +-------------------------------------------------------+
> ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au |
> / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 |
> \_,--\_/ | "By the time you make ends meet, they move the ends." |
> v +-------------------------------------------------------+
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
--
:{ andyf@speednet.com.au
Andy Farkas
System Administrator
Speed Internet Services
http://www.speednet.com.au/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 18:05:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA24793
for freebsd-current-outgoing; Mon, 9 Nov 1998 18:05:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from werple.mira.net (werple.mira.net [203.9.190.18])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA24772
for <freebsd-current@FreeBSD.ORG>; Mon, 9 Nov 1998 18:05:15 -0800 (PST)
(envelope-from gfm@mira.net)
Received: (qmail 10717 invoked from network); 10 Nov 1998 02:04:56 -0000
Received: from dp-m-q219.werple.net.au (203.17.45.219)
by mira.net with SMTP; 10 Nov 1998 02:04:56 -0000
From: gfm@mira.net (Graham Menhennitt)
To: freebsd-current@FreeBSD.ORG
Subject: Re: 3.0-CURRENT: Adaptec 1540 not detected (with workaround)
Date: Tue, 10 Nov 1998 02:07:37 GMT
Message-ID: <36499e6e.16635120@mira.net>
References: <13895.31563.888702.914625@hip186.ch.intel.com>
In-Reply-To: <13895.31563.888702.914625@hip186.ch.intel.com>
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 SAA24787
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 9 Nov 1998 16:31:23 -0700 (MST), John Reynolds~
<jreynold@sedona.ch.intel.com> wrote:
>
>> I have just upgraded by 2.2-STABLE machine to 3.0-CURRENT. It couldn't boot
>> either kernel.GENERIC or the custom kernel that I built. It said that it
>> didn't detect my Adaptec 1540 (and then paniced with "cannot mount root").
>> I even specified the exact port address, IRQ and DRQ in userconfig. Still
>> no go. It used to work fine with 2.2 and was correctly detected by the
>> kernel on the 3.0 boot floppy.
>>
>> Eventually I found the problem. In /usr/src/sys/dev/aha/aha.c there is some
>> code that attempts to distinguish between Adaptec and Buslogic adaptors.
>> This was failing. I'm not sure what model my adaptor is (I think it's an
>> 'A') but it is a genuine Adaptec. Hence the comment in the code about
>> cloned cards may apply to some genuine ones also.
>
>COOL! So there *was* a problem after all! I saw the exact same things
>happening to my 1542C (not even using the exact IRQ and DRQ values in
>userconfig helped). Sounds like this was a real problem. Is somebody going
>to commit the changes that gfm@mira.net (Graham Menhennitt) provided? If so,
No, definitely don't commit my patch. All it does is remove the test. It
was simply given as a workaround - not a fix!! It will probably break as
many machines as it fixes.
I'll do a bit more investigaing and try to come up with something a bit
more robust.
>will another "official" 3.0 boot floppy be rolled with this change? I ask
>only because I don't know if using a SNAP or CURRENT boot.flp with the 3.0
>CD-ROMs (whenever they get to my door) would be a Bad Thing(tm) or
>not. Probably not? Right now, the 3.0-RELEASE boot.flp will not pick up
>Adaptec 154x cards at all.
Strange, the 3.0-RELEASE boot.flp _did_ work for me. It was just the
kernel.GENERIC from the bin tarball and my custom kernel that failed.
Graham
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 18:09:17 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA25317
for freebsd-current-outgoing; Mon, 9 Nov 1998 18:09:17 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from poboxer.pobox.com (port17.prairietech.net [208.141.230.94])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25309
for <current@freebsd.org>; Mon, 9 Nov 1998 18:09:10 -0800 (PST)
(envelope-from alk@poboxer.pobox.com)
Received: (from alk@localhost) by poboxer.pobox.com (8.9.1/8.7.3) id UAA20709; Mon, 9 Nov 1998 20:08:03 -0600 (CST)
From: Tony Kimball <anthony.kimball@east.sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 9 Nov 1998 20:08:01 -0600 (CST)
X-Face: O9M"E%K;(f-Go/XDxL+pCxI5<W_e*r7B8ojMD.5+qDgOp4/\gTQEgbOoBqf:Vtl*aW:<;9/
UIVk'U^XhYg+v#r~*X<$Q=_ik@5:%E}pl]9|9|:]WLW8n:fLgg0~cfwWRBQxK/HSG0b1D/gljJC$qp
b=HDF@+"H<|fXy`w#$8#6A"!F:>*gr[=FN@Y`cl1.Tn
Reply-To: alk@pobox.com
To: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <13895.40864.375388.573511@avalon.east>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Is this similar to what other people are seeing?
> ...
> Apr 19 12:03:43 lupo /kernel: swap_pager: suggest more swap space: 124 MB
> Apr 19 12:10:03 lupo /kernel: pid 15046 (cron), uid 0: exited on signal 11
Lately, I'm still seing lines like this:
> Apr 19 12:03:43 lupo /kernel: swap_pager: suggest more swap space: 124 MB
but no daemon deaths since I switched to SMP.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 19:10:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA01723
for freebsd-current-outgoing; Mon, 9 Nov 1998 19:10: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 TAA01714
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 19:10:45 -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 WAA28021;
Mon, 9 Nov 1998 22:10:11 -0500 (EST)
Date: Mon, 9 Nov 1998 22:10:11 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: David Langford <langfod@maui.net>
cc: Yarema <yds@ingress.net>, current@FreeBSD.ORG
Subject: Re: /usr/bin/groff: can't find `DESC' file
In-Reply-To: <199811092212.MAA21714@maui.net>
Message-ID: <Pine.BSF.4.05.9811092209140.27915-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, 9 Nov 1998, David Langford wrote:
> a.out works fine but Elf does not.
>
> Trace shows that the path isnt being added to the file_open
> with /usr/share/groff/font.
>
> I am begining to wonder if it is a problem with the Elf C++ compiler.
>
> I have been unable to figure out a solution on my machines.
> This is very frustrating.
Check the optimization level used when compiling groff.
>
> I sent similar email a couple of weeks ago and I only got one
> reply. It mustnt be important to anyone.
>
>
> -David Langford
> langfod@dihelix.com
Cheers,
Brian Feldman
>
>
> >typing man whatever-has-no-cat-page produces the following:
> >
> >/usr/bin/groff: can't find `DESC' file
> >/usr/bin/groff:fatal error: invalid device `ascii'
> >
> >I did a make aout-to-elf some time late last week. Why is this happening?
> >From what I can tell /usr/share/groff_font/ contains all the right stuff. No
> >different from a 2.2.7 system. Or am I looking in the wrong place?
> >
> >--
> >Yarema
> >
> >
> >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
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 19:18:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA02288
for freebsd-current-outgoing; Mon, 9 Nov 1998 19:18:04 -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 TAA02281
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 19:18:00 -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 WAA28095;
Mon, 9 Nov 1998 22:17:15 -0500 (EST)
Date: Mon, 9 Nov 1998 22:17:15 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Dan Nelson <dnelson@emsphone.com>
cc: sthaug@nethelp.no, nathan@rtfm.net, current@FreeBSD.ORG
Subject: Re: O_SYNC
In-Reply-To: <19981109190225.A22989@emsphone.com>
Message-ID: <Pine.BSF.4.05.9811092214440.27915-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, 9 Nov 1998, Dan Nelson wrote:
> In the last episode (Nov 10), sthaug@nethelp.no said:
> > > > Yes, however every other OS defines it at "O_SYNC" why are we different?
> > > > or, if there is a reason, why isn't there a compatibility #define?
Good point. Let's get this added as a compatibility define, since it seems
to have already caused at least one person trouble, it will undoubtedly
cause more. And hey, we're not doing anything with O_SYNC now, and the
namespace is already heavily polluted...
> > >
> > > > > can someone check this on netbsd/open bsd/os ? is it bsd or us?
> > >
> > > NetBSD 1.3.2:
> > > fcntl.h:92:#define O_SYNC 0x0080 /* synchronous writes */
> > > fcntl.h:127:#define FFSYNC O_SYNC /* kernel */
> > > fcntl.h:129:#define O_FSYNC O_SYNC /* compat */
> >
> > BSD/OS 3.1 fcntl.h:
> >
> > #define O_FSYNC 0x0080 /* synchronous writes */
> > #define FFSYNC O_FSYNC /* kernel */
>
> It's O_SYNC on Dec OSF/1, SCO Open Server, and SunOS too.
>
> -Dan Nelson
> dnelson@emsphone.com
Brian Feldman
>
> 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 Nov 9 19:20:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA02466
for freebsd-current-outgoing; Mon, 9 Nov 1998 19:20:03 -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 TAA02417
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 19:19:53 -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 WAA28135;
Mon, 9 Nov 1998 22:19:27 -0500 (EST)
Date: Mon, 9 Nov 1998 22:19:27 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: lcremean@tidalwave.net
cc: John Fieber <jfieber@indiana.edu>, garman@earthling.net,
current@FreeBSD.ORG, julian@whistle.com, wollman@khavrinen.lcs.mit.edu
Subject: Re: The infamous dying daemons bug
In-Reply-To: <19981109202432.A3125@tidalwave.net>
Message-ID: <Pine.BSF.4.05.9811092217450.27915-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
Well, my mobo is... an SM5-A. Err, I have no idea what chipset or anything
:/ What I know is:
CPU: AMD-K6tm w/ multimedia extensions (200.46-MHz 586-class CPU)
chip0: <Intel 82437VX PCI cache memory controller> rev 0x02 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
Cheers,
Brian Feldman
On Mon, 9 Nov 1998, Lee Cremeans wrote:
> On Mon, Nov 09, 1998 at 07:59:34PM -0500, Brian Feldman wrote:
>
> >
> > According to these e-mails, I have been attempting the same scenarios,
> > but without the same effects.
>
> Just out of curiosity, Brian, what processor and motherboard/chipset do you
> have? I think that, while we have looked at processors, we haven't examined
> motherboards.
>
> FWIW, I have a AMD K6-2 and an Acer Aladdin IV+ chipset, and I have seen
> inetd go into "junk pointer" mode before. It was after Netscape munched all
> my swap.
>
> --
> Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)
> A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did
> $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net
> http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 19:39:58 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA03808
for freebsd-current-outgoing; Mon, 9 Nov 1998 19:39:58 -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 TAA03802
for <current@freebsd.org>; Mon, 9 Nov 1998 19:39:56 -0800 (PST)
(envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp)
Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:/jtS/DHX7gnvmLs9s1+QRb29KrT09SZ0@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 MAA16670;
Tue, 10 Nov 1998 12:39:30 +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 MAA14161; Tue, 10 Nov 1998 12:40:58 +0900 (JST)
Message-Id: <199811100340.MAA14161@zodiac.mech.utsunomiya-u.ac.jp>
To: Mark Turpin <mturpin@saturn.spel.com>
cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: psmintr: out of sync
In-reply-to: Your message of "Mon, 09 Nov 1998 15:34:11 EST."
<Pine.BSF.4.05.9811091524170.203-100000@saturn.spel.com>
References: <Pine.BSF.4.05.9811091524170.203-100000@saturn.spel.com>
Date: Tue, 10 Nov 1998 12:40:57 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I am getting the following error when I run X.
Would you describe your system? Motherboard, CPU, X server...
>Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (0000 != 0008).
>Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Do you see them often, or just occasionally? Is the mouse working,
or is it totally unusable?
If the mouse is working and you see the above messages just occasionally,
please ignore the messages.
The "psmintor: out of sync" message is generated if
a) there is mismatch of the mouse protocol; the psm driver is expecting
a wrong data format (this is unlikely in your case because your mouse
is correctly recognized as NetMouse). If this happens, we need to fix
the psm driver; there is a bug somewhere.
b) Or, if some data bytes from the mouse are somehow lost. While I don't
like this happening, it is relatively harmless because the psm driver
should be able to resyunc with the mouse data stream.
c) Or, if you are using a display/keyboard/mouse switch box. Some swich
box products do not constantly supply power to the mouse and may
momentalily cut the power when switching between host computers. This
will reset the mouse and lose settings in the mouse which the psm driver
has carefully set up. This may lead to out-of-sync situation sooner
or later. Other switch products do supply power OK, but
its built-in CPU tries to emulate/translate mouse data. The problem
is that the firmware of the built-in CPU is sometimes just buggy or
is not good enough and may confuse the psm driver.
>An older message said to try adding flags 0x100 to the device line in the
>kernel config file. That did make the errors stop.
Do you mean that the mouse was not working but now works because of
the flags 0x100? Or, the mouse was working and it now works too AND
there is no more error messages?
>The mouse is a Genius NetMouse Pro. Below are the startup messages.
>
[...]
>Nov 9 15:19:07 saturn /kernel: psm0: current command byte:0065
>Nov 9 15:19:07 saturn /kernel: kbdio: TEST_AUX_PORT status:0000
>Nov 9 15:19:07 saturn /kernel: kbdio: RESET_AUX return code:00fa
>Nov 9 15:19:07 saturn /kernel: kbdio: RESET_AUX status:00aa
>Nov 9 15:19:07 saturn /kernel: kbdio: RESET_AUX ID:0000
>Nov 9 15:19:07 saturn /kernel: psm: status 00 02 64
>Nov 9 15:19:07 saturn /kernel: psm: status 00 03 06
>Nov 9 15:19:07 saturn /kernel: psm: status 00 33 55
>Nov 9 15:19:07 saturn /kernel: psm: data 18 ff 00
>Nov 9 15:19:07 saturn /kernel: psm: status 00 02 64
>Nov 9 15:19:08 saturn /kernel: psm0 at 0x60-0x64 irq 12 on motherboard
>Nov 9 15:19:08 saturn /kernel: psm0: model NetMouse, device ID 0, 3 buttons
>Nov 9 15:19:08 saturn /kernel: psm0: config:00000000, flags:00000000, packet
>size:4
>Nov 9 15:19:08 saturn /kernel: psm0: syncmask:c8, syncbits:08
NetMouse Pro is a variant of NetMouse. Looks like it is correctly
recognized.
Kazu
yokota@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 Nov 9 20:35:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA08209
for freebsd-current-outgoing; Mon, 9 Nov 1998 20:35:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08204
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 20:35:36 -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 PAA03024;
Tue, 10 Nov 1998 15:35:16 +1100
Date: Tue, 10 Nov 1998 15:35:16 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811100435.PAA03024@godzilla.zeta.org.au>
To: nathan@rtfm.net, sthaug@nethelp.no
Subject: Re: O_SYNC
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> NetBSD 1.3.2:
>> fcntl.h:92:#define O_SYNC 0x0080 /* synchronous writes */
>> fcntl.h:127:#define FFSYNC O_SYNC /* kernel */
>> fcntl.h:129:#define O_FSYNC O_SYNC /* compat */
>
>BSD/OS 3.1 fcntl.h:
>
>#define O_FSYNC 0x0080 /* synchronous writes */
>#define FFSYNC O_FSYNC /* kernel */
O_SYNC is apparently a non-BSD thing.
POSIX.1b has optional features O_SYNC, O_DSYNC and O_RSYNC. O_SYNC syncs
everything related to writes; O_DSYNC syncs written data; O_RSYNC syncs
everything related to reads (mainly inode access times).
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 21:09:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA10735
for freebsd-current-outgoing; Mon, 9 Nov 1998 21:09:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from garman.dyn.ml.org (pm106-14.dialip.mich.net [192.195.231.216])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA10726
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 21:09:00 -0800 (PST)
(envelope-from garman@garman.dyn.ml.org)
Message-Id: <199811100509.VAA10726@hub.freebsd.org>
Received: (qmail 23868 invoked from smtpd); 10 Nov 1998 05:10:18 -0000
Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1)
by localhost.garman.net with SMTP; 10 Nov 1998 05:10:18 -0000
Date: Tue, 10 Nov 1998 00:10:17 -0500 (EST)
From: garman@earthling.net
Reply-To: garman@earthling.net
Subject: Re: The infamous dying daemons bug
To: crossd@cs.rpi.edu
cc: archie@whistle.com, eivind@yes.no, jfieber@indiana.edu,
current@FreeBSD.ORG
In-Reply-To: <Pine.SGI.4.05.9811091124580.5731-100000@o2.cs.rpi.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 9 Nov, David E. Cross wrote:
>> Has the use of memory mapping been ruled out as a possible common factor?
> Maybe if someone who is having this problem could donate the machine to a
> core member?
>
unfortunately i can't physically ship this system anywhere, but i'm
more than willing to give core team members accounts on here to help
diagnose the problem.
I'm also (per a previous message) currently running a staticly compiled
version of inetd; we'll see if this helps any (i'm seeing the
realloc: junk ptr/etc messages from inetd as well)
enjoy
--
Jason Garman http://garman.dyn.ml.org/
Student, University of Maryland garman@earthling.net
And now... did you know that: Whois: JAG145
"If you fart consistently for 6 years and 9 months, enough gas is
produced to create the energy of an atomic bomb." -- 0xdeadbeef posting
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 21:13:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA11215
for freebsd-current-outgoing; Mon, 9 Nov 1998 21:13: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 VAA11210
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 21:13: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 PAA16546;
Tue, 10 Nov 1998 15:43:28 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.1/8.9.0) id PAA18091;
Tue, 10 Nov 1998 15:43:27 +1030 (CST)
Message-ID: <19981110154327.X499@freebie.lemis.com>
Date: Tue, 10 Nov 1998 15:43:27 +1030
From: Greg Lehey <grog@lemis.com>
To: Alexander Litvin <archer@lucky.net>, Luoqi Chen <luoqi@watermarkgroup.com>
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <199811092056.PAA22043@lor.watermarkgroup.com> <199811100136.DAA00563@grape.carrier.kiev.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199811100136.DAA00563@grape.carrier.kiev.ua>; from Alexander Litvin on Tue, Nov 10, 1998 at 03:36:28AM +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 Tuesday, 10 November 1998 at 3:36:28 +0200, Alexander Litvin wrote:
> In article <199811092056.PAA22043@lor.watermarkgroup.com> you wrote:
>>> Totally unrelated to the problem. It seems, so far as I was able to
>>> characterize, to happen to daemons which are *swapped out* at the time
>>> of the memory shortage. If it's active enough to still be in core, it
>>> doesn't get spammed.
>>>
> LC> I went through swap_pager.c today and found a problem that could potentially
> LC> have bad consequences. It's a comparison between page index in the swap pager
> LC> and the size of the vm object, since a shadowed object may have a non-zero
> LC> paging offset with respect to the swap pager, the comparison should have taken
> LC> the offset into account. This piece of code has been there since '95, so
> LC> I can't say if this was responsible for the daemon dying problem.
>
> It is definitely not responsible. At least for this particular problem,
> though it may fix something else ;)
>
> After applying the patch, and artificially exhausting memory, I promptly
> got:
>
> Nov 10 03:15:34 grape /kernel: swap_pager: suggest more swap space: 61 MB
> Nov 10 03:16:26 grape /kernel: pid 310 (sendmail), uid 0: exited on signal 11
> Nov 10 03:17:26 grape /kernel: pid 311 (sendmail), uid 0: exited on signal 11
> Nov 10 03:18:25 grape /kernel: pid 313 (sendmail), uid 0: exited on signal 11
> Nov 10 03:19:25 grape /kernel: pid 353 (sendmail), uid 0: exited on signal 11
> Nov 10 03:20:26 grape /kernel: pid 394 (sendmail), uid 0: exited on signal 11
Ah, now that's one that I've been getting without exhausting memory.
I'm assuming that these dying sendmails are children of the daemon.
What happens when you kill -1 the daemon ("accepting connections on
port 25 (sendmail)")? In my experience, it *always* dies with a
SIGSEGV after these messages have occurred.
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 Mon Nov 9 21:21:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA11946
for freebsd-current-outgoing; Mon, 9 Nov 1998 21:21:01 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11940
for <current@freebsd.org>; Mon, 9 Nov 1998 21:21:00 -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 BAA13322;
Tue, 10 Nov 1998 01:20:32 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 10 Nov 1998 01:20:31 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Paul Saab <paul@mu.org>
cc: current@FreeBSD.ORG
Subject: Re: 18gig drive's supported?
In-Reply-To: <19981109140601.A2798@mu.org>
Message-ID: <Pine.BSF.4.05.9811100118590.337-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 Mon, 9 Nov 1998, Paul Saab wrote:
> did you upgrade this system from a pre-cam system? If you did I
> think you need to upgrade sysinstall too.
Yes...next question, how to upgrade sysinstall? Went into
/usr/src/release/sysinstall, typed 'make cleandir;make depend'...it
failed:
file2c 'u_char boot0[] = {' '};' < /boot/boot0 >> makedevs.tmp
cannot open /boot/boot0: no such file
*** Error code 2
Am still an aout system...if that means anything/helps?
>
> paul
>
> The Hermit Hacker (scrappy@hub.org) wrote:
> > I dont' know if there is anything special that the OS has to do as far as
> > large drive support is concerneed, but we just added the following drive
> > to our system, and can't get anywhere with it:
> >
> > a1 at ahc0 bus 0 target 1 lun 0
> > da1: 17366MB (35566000 512 byte sectors: 255H 63S/T 2213C)
> > da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
> > da1: <COMPAQ DGHS18Y 01A0> Fixed Direct Access SCSI3 device
> >
> >
> > We currently have three controllers in that machine, with 2+ drives per
> > controller...the other drives all work (4gig drives), but this new 18gig
> > appears to be a problem.
> >
> > hub> dmesg | grep ahc
> > ahc0: <Adaptec 2940 Ultra SCSI adapter> rev 0x01 int a irq 12 on pci0.9.0
> > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
> > ahc1: <Adaptec 2940 Ultra SCSI adapter> rev 0x01 int a irq 9 on pci0.10.0
> > ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
> > ahc2: <Adaptec 2940A Ultra SCSI adapter> rev 0x01 int a irq 11 on pci0.12.0
> > ahc2: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs
> > probe1:ahc0:0:1:0): Sending SDTR!!
> > ub> dmesg | grep "^da" | sort
> > da0 at ahc0 bus 0 target 0 lun 0
> > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
> > da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C)
> > da0: <QUANTUM VIKING II 4.5WSE 3506> Fixed Direct Access SCSI2 device
> > da1 at ahc0 bus 0 target 1 lun 0
> > da1: 17366MB (35566000 512 byte sectors: 255H 63S/T 2213C)
> > da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
> > da1: <COMPAQ DGHS18Y 01A0> Fixed Direct Access SCSI3 device
> > da2 at ahc1 bus 0 target 0 lun 0
> > da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enables
> > da2: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C)
> > da2: <QUANTUM XP34550W LYK8> Fixed Direct Access SCSI2 device
> > da3 at ahc1 bus 0 target 1 lun 0
> > da3: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
> > da3: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C)
> > da3: <QUANTUM XP34550W LYK8> Fixed Direct Access SCSI2 device
> > da4 at ahc2 bus 0 target 1 lun 0
> > da4: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
> > da4: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C)
> > da4: <QUANTUM XP34301 1071> Fixed Direct Access SCSI2 device
> > da5 at ahc2 bus 0 target 2 lun 0
> > da5: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
> > da5: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C)
> > da5: <QUANTUM XP34301 1071> Fixed Direct Access SCSI2 device
> > da6 at ahc2 bus 0 target 3 lun 0
> > da6: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled
> > da6: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C)
> > da6: <QUANTUM XP34550S LXY4> Fixed Direct Access SCSI2 device
> > da7 at ahc2 bus 0 target 4 lun 0
> > da7: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
> > da7: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C)
> > da7: <QUANTUM XP34301 1071> Fixed Direct Access SCSI2 device
> > da8 at ahc2 bus 0 target 5 lun 0
> > da8: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
> > da8: 4101MB (8399520 512 byte sectors: 255H 63S/T 522C)
> > da8: <Quantum XP34300 L912> Fixed Direct Access SCSI2 device
> >
> > If I run /stand/sysinstall->Configure->Label, I get back a message stating
> > that 'No disks found! Please verify that your disk controller is being
> > properly probed at boot time'
> >
> > The system comes out on uname -a as 3.0-CURRENT, dated November 4th...
> >
> > Thoughts and/or ideas? Its obvious that the kernel is finding all the drives,
> > so I'm curious why /stand/sysinstall doesn't see them...
> >
> > 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 Mon Nov 9 21:41:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA13765
for freebsd-current-outgoing; Mon, 9 Nov 1998 21:41:05 -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 VAA13759
for <current@freebsd.org>; Mon, 9 Nov 1998 21:41:03 -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 0zd6Xl-0004Db-00; Mon, 9 Nov 1998 22:40:45 -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 WAA05121 for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 22:40:37 -0700 (MST)
Message-Id: <199811100540.WAA05121@harmony.village.org>
Subject: Re: newer gcc?
to: current@FreeBSD.ORG
In-reply-to: Your message of "Mon, 09 Nov 1998 09:07:25 PST."
<7531.910631245@time.cdrom.com>
References: <7531.910631245@time.cdrom.com>
Date: Mon, 09 Nov 1998 22:40:37 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <7531.910631245@time.cdrom.com> "Jordan K. Hubbard" writes:
: That's a bit premature. I'd be more interested if you could even build
: the world from egcs installed in /usr/local.
As would I. I'm trying to get a cross build environment working, and
am finding that gcc is a hard nut to crack at its current revision
level.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 21:48:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA14347
for freebsd-current-outgoing; Mon, 9 Nov 1998 21:48:05 -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 VAA14338
for <freebsd-current@freebsd.org>; Mon, 9 Nov 1998 21:48:03 -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 0zd6eV-0004Ds-00; Mon, 9 Nov 1998 22:47: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 WAA16931; Mon, 9 Nov 1998 22:47:35 -0700 (MST)
Message-Id: <199811100547.WAA16931@harmony.village.org>
To: gfm@mira.net (Graham Menhennitt)
Subject: Re: 3.0-CURRENT: Adaptec 1540 not detected (with workaround)
Cc: freebsd-current@FreeBSD.ORG
In-reply-to: Your message of "Tue, 10 Nov 1998 02:07:37 GMT."
<36499e6e.16635120@mira.net>
References: <36499e6e.16635120@mira.net> <13895.31563.888702.914625@hip186.ch.intel.com>
Date: Mon, 09 Nov 1998 22:47:35 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <36499e6e.16635120@mira.net> Graham Menhennitt writes:
: I'll do a bit more investigaing and try to come up with something a bit
: more robust.
I've fixed a number of minor bugs in the detection of aha 154x cards
since 3.0 was released. I've committed these patches to the tree.
You might want to hold off on anything too elabertate until just
commits his fixes to the tree for the aha/bt problem of not all I/O
ports probe currectly. They seem to work for me fairly well on the
cards I've set to the non-default addresses.
Also, the aha-154x rev A will not work with CAM at this point in
time. It doesn't support residuals at all, and would be kinda hard to
get working. Given that I didn't have a card in hand, I punted on it.
The tests that distinquish the aha from the bt should catch this
correctly, please drop me a line if they do not.
Warner
P.S. I mised the first part of this thread, or I would have replied
before now....
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 21:52:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA14740
for freebsd-current-outgoing; Mon, 9 Nov 1998 21:52: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 VAA14735
for <freebsd-current@freebsd.org>; Mon, 9 Nov 1998 21:52: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 0zd6in-0004E1-00; Mon, 9 Nov 1998 22:52:09 -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 WAA16957; Mon, 9 Nov 1998 22:52:01 -0700 (MST)
Message-Id: <199811100552.WAA16957@harmony.village.org>
To: John Reynolds~ <jreynold@sedona.ch.intel.com>
Subject: Re: 3.0-CURRENT: Adaptec 1540 not detected (with workaround)
Cc: freebsd-current@FreeBSD.ORG
In-reply-to: Your message of "Mon, 09 Nov 1998 16:31:23 MST."
<13895.31563.888702.914625@hip186.ch.intel.com>
References: <13895.31563.888702.914625@hip186.ch.intel.com>
Date: Mon, 09 Nov 1998 22:52:01 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <13895.31563.888702.914625@hip186.ch.intel.com> John Reynolds~ writes:
: not. Probably not? Right now, the 3.0-RELEASE boot.flp will not pick up
: Adaptec 154x cards at all.
That is incorrect. I've booted the 3.0 release boot.flp several times
on with the various aha cards that I have in my machine. It detects
them in the cases that I've seen. However, there are some I/O
addresses that it fails to detect them for. These problems are in the
process of being corrected.
There were also some problems with cards that have their bioses
enabled not probing correctly. These problems have been corrected.
I am aware of some problems with a 1542B using hawk (any?) disks, but
have not had a chance to investigate those problems.
At some point there will likely be a new snapshot produced, which will
have better aha detection code.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 9 22:16:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA16076
for freebsd-current-outgoing; Mon, 9 Nov 1998 22:16:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles162.castles.com [208.214.165.162])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA16063
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 22:16:43 -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 WAA00484;
Mon, 9 Nov 1998 22:15:36 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811100615.WAA00484@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: The Hermit Hacker <scrappy@hub.org>
cc: Paul Saab <paul@mu.org>, current@FreeBSD.ORG
Subject: Re: 18gig drive's supported?
In-reply-to: Your message of "Tue, 10 Nov 1998 01:20:31 -0400."
<Pine.BSF.4.05.9811100118590.337-100000@thelab.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 09 Nov 1998 22:15:35 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On Mon, 9 Nov 1998, Paul Saab wrote:
>
> > did you upgrade this system from a pre-cam system? If you did I
> > think you need to upgrade sysinstall too.
>
> Yes...next question, how to upgrade sysinstall? Went into
> /usr/src/release/sysinstall, typed 'make cleandir;make depend'...it
> failed:
>
> file2c 'u_char boot0[] = {' '};' < /boot/boot0 >> makedevs.tmp
> cannot open /boot/boot0: no such file
> *** Error code 2
>
> Am still an aout system...if that means anything/helps?
Go to /sys/boot and say 'make; make install' first. You haven't built
the world for a long time it seems.
--
\\ 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 Mon Nov 9 22:35:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA17323
for freebsd-current-outgoing; Mon, 9 Nov 1998 22:35:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17318
for <current@FreeBSD.ORG>; Mon, 9 Nov 1998 22:35: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 RAA13398;
Tue, 10 Nov 1998 17:34:54 +1100
Date: Tue, 10 Nov 1998 17:34:54 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811100634.RAA13398@godzilla.zeta.org.au>
To: archie@whistle.com, phk@critter.freebsd.dk
Subject: Re: The infamous dying daemons bug
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>A static inetd sounds like a good experiment.
I couldn't duplicate the dying daemons problem despite trying fairly
hard, and thought that this might be because I link everything in the
world static. I didn't try hard enough to downgrade to a default world.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 00:19:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA24632
for freebsd-current-outgoing; Tue, 10 Nov 1998 00:19:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24601;
Tue, 10 Nov 1998 00:18:17 -0800 (PST)
(envelope-from dv@dv.ru)
Received: from localhost (dv@localhost)
by xkis.kis.ru (8.9.0/8.9.0) with SMTP id LAA00217;
Tue, 10 Nov 1998 11:17:55 +0300 (MSK)
Date: Tue, 10 Nov 1998 11:17:55 +0300 (MSK)
From: Dmitry Valdov <dv@dv.ru>
X-Sender: dv@xkis.kis.ru
To: Brian Somers <brian@FreeBSD.ORG>
cc: current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-Reply-To: <199811100032.QAA13871@freefall.freebsd.org>
Message-ID: <Pine.BSF.3.95q.981110111417.27884F-100000@xkis.kis.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi!
There is a problem in ppp - when you kill it with -9, You'll not be able to
start it again until you reboot.
Sometimes I need to kill it with -9 because when killing with SIGHUP it
tries to properly shutdown PPP session via LCP, but there is some cases when
it inpossible.
On Mon, 9 Nov 1998, Brian Somers wrote:
> Date: Mon, 9 Nov 1998 16:32:39 -0800 (PST)
> From: Brian Somers <brian@FreeBSD.ORG>
> To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
> Subject: cvs commit: src/usr.sbin/ppp ip.c
>
> brian 1998/11/09 16:32:39 PST
>
> Modified files:
> usr.sbin/ppp ip.c
> Log:
> Don't forget to initialise dbuff when debugging.
>
> Revision Changes Path
> 1.54 +9 -5 src/usr.sbin/ppp/ip.c
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe cvs-all" 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 Nov 10 00:48:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA27273
for freebsd-current-outgoing; Tue, 10 Nov 1998 00:48:20 -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 AAA27266;
Tue, 10 Nov 1998 00:48:16 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from spectrum.physics.adelaide.edu.au (spectrum [129.127.36.1])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id TAA15632;
Tue, 10 Nov 1998 19:17:59 +1030 (CST)
Received: from localhost by spectrum.physics.adelaide.edu.au; (5.65/1.1.8.2/26Jun95-0330PM)
id AA10853; Tue, 10 Nov 1998 19:17:48 +1030
Date: Tue, 10 Nov 1998 19:17:47 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
To: Dmitry Valdov <dv@dv.ru>
Cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-Reply-To: <Pine.BSF.3.95q.981110111417.27884F-100000@xkis.kis.ru>
Message-Id: <Pine.OSF.4.05.9811101915420.10597-100000@spectrum.physics.adelaide.edu.au>
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, 10 Nov 1998, Dmitry Valdov wrote:
> There is a problem in ppp - when you kill it with -9, You'll not be able to
> start it again until you reboot.
> Sometimes I need to kill it with -9 because when killing with SIGHUP it
> tries to properly shutdown PPP session via LCP, but there is some cases when
> it inpossible.
Doing a 'route delete default' seems to fix this for me (otherwise it just
hangs when I try and restart it).
Kris
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 00:55:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA28199
for freebsd-current-outgoing; Tue, 10 Nov 1998 00:55:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pc08.labcontrol.com. (pc08.labcontrol.com [194.163.70.139])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA28192
for <freebsd-current@freebsd.org>; Tue, 10 Nov 1998 00:55:12 -0800 (PST)
(envelope-from mvw@pc08.labcontrol.com)
Received: by pc08.labcontrol.com. (SMI-8.6/SMI-SVR4)
id JAA20698; Tue, 10 Nov 1998 09:55:16 +0100
Date: Tue, 10 Nov 1998 09:55:16 +0100
Message-Id: <199811100855.JAA20698@pc08.labcontrol.com.>
From: Marc van Woerkom <mvw@rebecca.labcontrol.com>
To: freebsd-current@FreeBSD.ORG
Subject: aout-to-elf
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi!
While the 'aout-to-elf-install' target failed with the source
tree from Sun morning (9th November) - two stops: a missing
../lib/m3/aout directory and a missing gv.h for the pearl install -
the CURRENT from Monday evening worked perfect.
Thanks a lot!
Regards,
Marc
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 00:55:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA28230
for freebsd-current-outgoing; Tue, 10 Nov 1998 00:55:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28223;
Tue, 10 Nov 1998 00:55:23 -0800 (PST)
(envelope-from dv@dv.ru)
Received: from localhost (dv@localhost)
by xkis.kis.ru (8.9.0/8.9.0) with SMTP id LAA01370;
Tue, 10 Nov 1998 11:52:33 +0300 (MSK)
Date: Tue, 10 Nov 1998 11:52:33 +0300 (MSK)
From: Dmitry Valdov <dv@dv.ru>
X-Sender: dv@xkis.kis.ru
To: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-Reply-To: <Pine.OSF.4.05.9811101915420.10597-100000@spectrum.physics.adelaide.edu.au>
Message-ID: <Pine.BSF.3.95q.981110114942.1147C-100000@xkis.kis.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 Tue, 10 Nov 1998, Kris Kennaway wrote:
> Date: Tue, 10 Nov 1998 19:17:47 +1030 (CST)
> From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
> To: Dmitry Valdov <dv@dv.ru>
> Cc: Brian Somers <brian@freebsd.org>, current@freebsd.org
> Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
>
> On Tue, 10 Nov 1998, Dmitry Valdov wrote:
>
> > There is a problem in ppp - when you kill it with -9, You'll not be able to
> > start it again until you reboot.
> > Sometimes I need to kill it with -9 because when killing with SIGHUP it
> > tries to properly shutdown PPP session via LCP, but there is some cases when
> > it inpossible.
>
> Doing a 'route delete default' seems to fix this for me (otherwise it just
> hangs when I try and restart it).
>
Thanks, will be know. But why not to fix it in ppp? :)
Also there is one more bug - sometimes ppp don't detect carrier lost and
stays in open state for a long time. :(
Dmitry.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 01:05:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA29138
for freebsd-current-outgoing; Tue, 10 Nov 1998 01:05:36 -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 BAA29129;
Tue, 10 Nov 1998 01:05:29 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from spectrum.physics.adelaide.edu.au (spectrum [129.127.36.1])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id TAA17146;
Tue, 10 Nov 1998 19:35:12 +1030 (CST)
Received: from localhost by spectrum.physics.adelaide.edu.au; (5.65/1.1.8.2/26Jun95-0330PM)
id AA10874; Tue, 10 Nov 1998 19:35:11 +1030
Date: Tue, 10 Nov 1998 19:35:10 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
To: Dmitry Valdov <dv@dv.ru>
Cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-Reply-To: <Pine.BSF.3.95q.981110114942.1147C-100000@xkis.kis.ru>
Message-Id: <Pine.OSF.4.05.9811101930000.10597-100000@spectrum.physics.adelaide.edu.au>
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, 10 Nov 1998, Dmitry Valdov wrote:
> Also there is one more bug - sometimes ppp don't detect carrier lost and
> stays in open state for a long time. :(
Sorry for the "implicit bug report", Brian, but I've been meaning to track
this down for a long time and make sure it's not user error. I often see this
as well - it's noticeable for me because I have ipfw installed and when the
modem drops carrier I see packets being 'reflected' by the modem's local echo
(I assume), and bouncing off the ipfw 'incoming address of myself' filter.
Kris
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 01:09:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA29421
for freebsd-current-outgoing; Tue, 10 Nov 1998 01:09:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29401;
Tue, 10 Nov 1998 01:09:13 -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 UAA23868;
Tue, 10 Nov 1998 20:08:50 +1100
Date: Tue, 10 Nov 1998 20:08:50 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811100908.UAA23868@godzilla.zeta.org.au>
To: bde@zeta.org.au, peter@netplex.com.au
Subject: Re: Dog Sloooow SMP
Cc: current@FreeBSD.ORG, jc@irbs.com, mike@smith.net.au,
narvi@haldjas.folklore.ee, smp@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> >How about 64 for the odd case that K7 actually materialises as promised
>> >and people start putting them in dual motherboards?
>>
>> That would be almost twice as slow for CC=gcc. CC=egcs handles 64-bit
>> bit tests better, especially for the low 32 bits.
>
>32 vs. 64 is almost irrelevant.. There's no limit to the number of 32 bit
>variables that we can use with flags in them, so there's no reason why
>we'd use a 64 bit variable in the first place.
It's easier and potentially faster to keep all the flags in a single
(scalar) variable.
>However.. One thing that bugs me is that we presently can optimize out
>code and tests for a runtime boost when compiled for a specific cpu. eg:
>if we support 386 cpus, we test for whether we have an invlpg instruction
>or not - but if we are not compiling with a 386 option then this code and
>the test for >= 486 goes away.
Attempt to keep compile-time options and tests when they make a difference.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 01:17:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA00470
for freebsd-current-outgoing; Tue, 10 Nov 1998 01:17:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.training.iafrica.com (axl.training.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00455;
Tue, 10 Nov 1998 01:17:24 -0800 (PST)
(envelope-from sheldonh@axl.training.iafrica.com)
Received: from sheldonh (helo=axl.training.iafrica.com)
by axl.training.iafrica.com with local-esmtp (Exim 2.05 #1)
id 0zd9sj-0002vb-00; Tue, 10 Nov 1998 11:14:37 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: Dmitry Valdov <dv@dv.ru>
cc: Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-reply-to: Your message of "Tue, 10 Nov 1998 11:52:33 +0300."
<Pine.BSF.3.95q.981110114942.1147C-100000@xkis.kis.ru>
Date: Tue, 10 Nov 1998 11:14:37 +0200
Message-ID: <11258.910689277@axl.training.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 10 Nov 1998 11:52:33 +0300, Dmitry Valdov wrote:
> Thanks, will be know. But why not to fix it in ppp? :)
Hi Dmitry,
Even if ppp does the route cleanup for you, a signal 9 (KILL) doesn't
allow it to attempt graceful exit. This means that building cleanup code
into ppp would not "fix it in ppp", since the code would never be
reached once a SIGKILL is received.
Assuming you _want_ to send ppp a SIGKILL instead of SIGTERM, your best
bet is to run ppp from a shell wrapper script and put the route cleanup
in the script, after the line that runs ppp.
It would be nicer, though, if you could send ppp a SIGTERM instead. I
remember that this wasn't always feasible last year when I used to use
ppp (sometimes SIGTERM would have no apparent effect), but it's worth
checking to see whether the software doesn't respond to this signal if
you haven't checked already.
Hope this helps,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 01:26:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA01002
for freebsd-current-outgoing; Tue, 10 Nov 1998 01:26:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles162.castles.com [208.214.165.162])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00986;
Tue, 10 Nov 1998 01:26:44 -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 BAA01418;
Tue, 10 Nov 1998 01:24:34 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811100924.BAA01418@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bruce Evans <bde@zeta.org.au>
cc: peter@netplex.com.au, current@FreeBSD.ORG, jc@irbs.com, mike@smith.net.au,
narvi@haldjas.folklore.ee, smp@FreeBSD.ORG
Subject: Re: Dog Sloooow SMP
In-reply-to: Your message of "Tue, 10 Nov 1998 20:08:50 +1100."
<199811100908.UAA23868@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Nov 1998 01:24:33 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> >However.. One thing that bugs me is that we presently can optimize out
> >code and tests for a runtime boost when compiled for a specific cpu. eg:
> >if we support 386 cpus, we test for whether we have an invlpg instruction
> >or not - but if we are not compiling with a 386 option then this code and
> >the test for >= 486 goes away.
>
> Attempt to keep compile-time options and tests when they make a difference.
It occurred to me that we could probably build a header somewhere full
of defines like this:
#if defined(CPU_686) && !defined(CPU_586) && !defined....
# define CPU_686_ONLY
#endif
...
#ifdef CPU_686_ONLY
# define CPU_CAP_FOOBAR (1)
#else
# define CPU_CAP_FOOBAR ((cpu == CPU_686) || (cpu == CPU_PII))
#endif
...
of course, you can customise the "slow mode" definition to suit, but
this is pretty clean.
--
\\ 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 Nov 10 01:50:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA03076
for freebsd-current-outgoing; Tue, 10 Nov 1998 01:50:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02940;
Tue, 10 Nov 1998 01:49:28 -0800 (PST)
(envelope-from gelderen@mediaport.org)
Received: from wit395301.student.utwente.nl ([130.89.235.121]:9220 "HELO deskfix" ident: "NO-IDENT-SERVICE[2]") by schuimpje.snt.utwente.nl with SMTP id <7989-21506>; Tue, 10 Nov 1998 10:48:31 +0100
Message-ID: <008d01be0c8f$188b6dc0$1400000a@deskfix.local>
From: "Jeroen C. van Gelderen" <gelderen@mediaport.org>
To: "Sheldon Hearn" <axl@iafrica.com>, "Dmitry Valdov" <dv@dv.ru>
Cc: "Kris Kennaway" <kkennawa@physics.adelaide.edu.au>,
"Brian Somers" <brian@FreeBSD.ORG>, <current@FreeBSD.ORG>
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
Date: Tue, 10 Nov 1998 10:47:14 +0100
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.1
X-Mimeole: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
From: Sheldon Hearn <axl@iafrica.com>
>Even if ppp does the route cleanup for you, a signal 9 (KILL) doesn't
>allow it to attempt graceful exit. This means that building cleanup code
>into ppp would not "fix it in ppp", since the code would never be
>reached once a SIGKILL is received.
Just a humble thought: route removal can be seen as cleanup, but it can also
be seen as preparation. Maybe you can do it at ppp startup. Or -if that's
not possible- you may be able to detect the condition as handle it
gracefully...
Cheers,
Jeroen
(who does not run ppp)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 02:03:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA04086
for freebsd-current-outgoing; Tue, 10 Nov 1998 02:03:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles162.castles.com [208.214.165.162])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04078
for <current@freebsd.org>; Tue, 10 Nov 1998 02:03:08 -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 CAA01721
for <current@freebsd.org>; Tue, 10 Nov 1998 02:02:12 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811101002.CAA01721@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: current@FreeBSD.ORG
Subject: Simple NFS ACCESS caching, call for testers
Mime-Version: 1.0
Content-Type: multipart/mixed ;
boundary="==_Exmh_-13891298860"
Date: Tue, 10 Nov 1998 02:02:11 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
This is a multipart MIME message.
--==_Exmh_-13891298860
Content-Type: text/plain; charset=us-ascii
The attached patch adds a trivial cache for NFS ACCESS operations,
which may provide a moderate to substantial performance improvement in
some cases.
The issues surrounding caching these requests are actually quite
subtle, and it's not immediately clear that a more sophisticated
approach would actually yield great results in many more cases than
this trivial one does. The trivial implementation has the advantage of
simplicity. 8)
If you have an NFS v3 server that you beat heavily on, I'd love to know
whether these changes make any difference to you.
Apply the patches to a -current kernel (they should apply fairly
cleanly to a -stable kernel as well, but I haven't tried this).
The new kernel has three new sysctl options:
vfs.nfs.access_cache_timeout
The time (in seconds) for which an ACCESS result is cached.
Try values from 2 to 10 or so. A value of 0 (the default)
disables caching.
vfs.nfs.access_cache_hits
The number of access calls that have been satisfied from
cached entries rather than wire calls.
vfs.nfs.access_cache_fills
The number of access calls that have had to go to the wire
to be satisfied.
Trivial testing tends to indicate that operations involving a single
UID and a large directory hierarchy may benefit substantially from
this, but I really need more results before I can commit.
--==_Exmh_-13891298860
Content-Type: text/plain ; name="nfsdiff"; charset=us-ascii
Content-Description: nfsdiff
Content-Disposition: attachment; filename="nfsdiff"
Index: nfs_vnops.c
===================================================================
RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v
retrieving revision 1.111
diff -u -r1.111 nfs_vnops.c
--- nfs_vnops.c 1998/11/09 07:00:14 1.111
+++ nfs_vnops.c 1998/11/10 08:48:40
@@ -60,6 +60,7 @@
#include <sys/fcntl.h>
#include <sys/lockf.h>
#include <sys/stat.h>
+#include <sys/sysctl.h>
#include <vm/vm.h>
#include <vm/vm_extern.h>
@@ -247,6 +248,35 @@
int nfs_numasync = 0;
#define DIRHDSIZ (sizeof (struct dirent) - (MAXNAMLEN + 1))
+static int nfsaccess_cache_timeout;
+SYSCTL_INT(_vfs_nfs, OID_AUTO, access_cache_timeout, CTLFLAG_RW,
+ &nfsaccess_cache_timeout, 0, "NFS ACCESS cache timeout");
+
+static int nfsaccess_cache_hits;
+SYSCTL_INT(_vfs_nfs, OID_AUTO, access_cache_hits, CTLFLAG_RD,
+ &nfsaccess_cache_hits, 0, "NFS ACCESS cache hit count");
+
+static int nfsaccess_cache_fills;
+SYSCTL_INT(_vfs_nfs, OID_AUTO, access_cache_fills, CTLFLAG_RD,
+ &nfsaccess_cache_fills, 0, "NFS ACCESS cache fill count");
+
+/*
+ * Compare two ucred structures, returns zero on equality, nonzero
+ * otherwise.
+ */
+static int
+nfsa_ucredcmp(struct ucred *c1, struct ucred *c2)
+{
+ int i;
+
+ if ((c1->cr_uid != c2->cr_uid) || (c1->cr_ngroups != c2->cr_ngroups))
+ return(1);
+ for (i = 0; i < c1->cr_ngroups; i++)
+ if (c1->cr_groups[i] != c2->cr_groups[i])
+ return(1);
+ return(0);
+}
+
/*
* nfs access vnode op.
* For nfs version 2, just return ok. File accesses may fail later.
@@ -269,8 +299,9 @@
caddr_t bpos, dpos, cp2;
int error = 0, attrflag;
struct mbuf *mreq, *mrep, *md, *mb, *mb2;
- u_int32_t mode, rmode;
+ u_int32_t mode, rmode, wmode;
int v3 = NFS_ISV3(vp);
+ struct nfsnode *np = VTONFS(vp);
/*
* Disallow write attempts on filesystems mounted read-only;
@@ -288,18 +319,14 @@
}
}
/*
- * For nfs v3, do an access rpc, otherwise you are stuck emulating
+ * For nfs v3, check to see if we have done this recently, and if
+ * so return our cached result instead of making an ACCESS call.
+ * If not, do an access rpc, otherwise you are stuck emulating
* ufs_access() locally using the vattr. This may not be correct,
* since the server may apply other access criteria such as
- * client uid-->server uid mapping that we do not know about, but
- * this is better than just returning anything that is lying about
- * in the cache.
+ * client uid-->server uid mapping that we do not know about.
*/
if (v3) {
- nfsstats.rpccnt[NFSPROC_ACCESS]++;
- nfsm_reqhead(vp, NFSPROC_ACCESS, NFSX_FH(v3) + NFSX_UNSIGNED);
- nfsm_fhtom(vp, v3);
- nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED);
if (ap->a_mode & VREAD)
mode = NFSV3ACCESS_READ;
else
@@ -315,22 +342,50 @@
NFSV3ACCESS_DELETE);
if (ap->a_mode & VEXEC)
mode |= NFSV3ACCESS_LOOKUP;
+ }
+ /* XXX safety belt, only make blanket request if caching */
+ if (nfsaccess_cache_timeout > 0) {
+ wmode = NFSV3ACCESS_READ | NFSV3ACCESS_MODIFY |
+ NFSV3ACCESS_EXTEND | NFSV3ACCESS_EXECUTE |
+ NFSV3ACCESS_DELETE | NFSV3ACCESS_LOOKUP;
+ } else {
+ wmode = mode;
}
- *tl = txdr_unsigned(mode);
- nfsm_request(vp, NFSPROC_ACCESS, ap->a_p, ap->a_cred);
- nfsm_postop_attr(vp, attrflag);
- if (!error) {
- nfsm_dissect(tl, u_int32_t *, NFSX_UNSIGNED);
- rmode = fxdr_unsigned(u_int32_t, *tl);
- /*
- * The NFS V3 spec does not clarify whether or not
- * the returned access bits can be a superset of
- * the ones requested, so...
- */
- if ((rmode & mode) != mode)
+
+ /* do we have a cached result? */
+ if ((time_second < (np->n_modestamp + nfsaccess_cache_timeout)) &&
+ !nfsa_ucredcmp(ap->a_cred, &np->n_modecred)) {
+ nfsaccess_cache_hits++;
+ if ((np->n_mode & mode) != mode)
error = EACCES;
+ } else {
+ nfsstats.rpccnt[NFSPROC_ACCESS]++;
+ nfsm_reqhead(vp, NFSPROC_ACCESS, NFSX_FH(v3) + NFSX_UNSIGNED);
+ nfsm_fhtom(vp, v3);
+ nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED);
+ *tl = txdr_unsigned(wmode);
+ nfsm_request(vp, NFSPROC_ACCESS, ap->a_p, ap->a_cred);
+ nfsm_postop_attr(vp, attrflag);
+ if (!error) {
+ nfsm_dissect(tl, u_int32_t *, NFSX_UNSIGNED);
+ rmode = fxdr_unsigned(u_int32_t, *tl);
+ /*
+ * The NFS V3 spec does not clarify whether or not
+ * the returned access bits can be a superset of
+ * the ones requested, so...
+ */
+ if ((rmode & mode) != mode) {
+ error = EACCES;
+ } else if (nfsaccess_cache_timeout > 0) {
+ /* cache the result */
+ nfsaccess_cache_fills++;
+ np->n_mode = rmode;
+ np->n_modecred = *ap->a_cred;
+ np->n_modestamp = time_second;
+ }
+ }
+ nfsm_reqdone;
}
- nfsm_reqdone;
return (error);
} else {
if (error = nfsspec_access(ap))
Index: nfsnode.h
===================================================================
RCS file: /home/ncvs/src/sys/nfs/nfsnode.h,v
retrieving revision 1.26
diff -u -r1.26 nfsnode.h
--- nfsnode.h 1998/05/31 18:32:23 1.26
+++ nfsnode.h 1998/11/10 08:41:02
@@ -93,6 +93,9 @@
u_quad_t n_lrev; /* Modify rev for lease */
struct vattr n_vattr; /* Vnode attribute cache */
time_t n_attrstamp; /* Attr. cache timestamp */
+ u_int32_t n_mode; /* ACCESS mode cache */
+ struct ucred n_modecred; /* credentials having mode */
+ time_t n_modestamp; /* mode cache timestamp */
time_t n_mtime; /* Prev modify time. */
time_t n_ctime; /* Prev create time. */
time_t n_expiry; /* Lease expiry time */
--==_Exmh_-13891298860
Content-Type: text/plain; charset=us-ascii
\\ 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
--==_Exmh_-13891298860--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 02:05:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA04435
for freebsd-current-outgoing; Tue, 10 Nov 1998 02:05:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04421;
Tue, 10 Nov 1998 02:05:32 -0800 (PST)
(envelope-from dv@dv.ru)
Received: from localhost (dv@localhost)
by xkis.kis.ru (8.9.0/8.9.0) with SMTP id NAA04245;
Tue, 10 Nov 1998 13:04:04 +0300 (MSK)
Date: Tue, 10 Nov 1998 13:04:04 +0300 (MSK)
From: Dmitry Valdov <dv@dv.ru>
X-Sender: dv@xkis.kis.ru
To: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-Reply-To: <Pine.OSF.4.05.9811101930000.10597-100000@spectrum.physics.adelaide.edu.au>
Message-ID: <Pine.BSF.3.95q.981110130222.4032C-100000@xkis.kis.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 Tue, 10 Nov 1998, Kris Kennaway wrote:
> Date: Tue, 10 Nov 1998 19:35:10 +1030 (CST)
> From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
> To: Dmitry Valdov <dv@dv.ru>
> Cc: Brian Somers <brian@freebsd.org>, current@freebsd.org
> Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
>
> On Tue, 10 Nov 1998, Dmitry Valdov wrote:
>
> > Also there is one more bug - sometimes ppp don't detect carrier lost and
> > stays in open state for a long time. :(
>
> Sorry for the "implicit bug report", Brian, but I've been meaning to track
> this down for a long time and make sure it's not user error. I often see this
> as well
Really. Me and my friend experiencing this problem very often.
Dmitry.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 02:07:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA04591
for freebsd-current-outgoing; Tue, 10 Nov 1998 02:07:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04578;
Tue, 10 Nov 1998 02:07:39 -0800 (PST)
(envelope-from dv@dv.ru)
Received: from localhost (dv@localhost)
by xkis.kis.ru (8.9.0/8.9.0) with SMTP id NAA04395;
Tue, 10 Nov 1998 13:06:48 +0300 (MSK)
Date: Tue, 10 Nov 1998 13:06:48 +0300 (MSK)
From: Dmitry Valdov <dv@dv.ru>
X-Sender: dv@xkis.kis.ru
To: Sheldon Hearn <axl@iafrica.com>
cc: Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-Reply-To: <11258.910689277@axl.training.iafrica.com>
Message-ID: <Pine.BSF.3.95q.981110130512.4032D-100000@xkis.kis.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 Tue, 10 Nov 1998, Sheldon Hearn wrote:
> Date: Tue, 10 Nov 1998 11:14:37 +0200
> From: Sheldon Hearn <axl@iafrica.com>
> To: Dmitry Valdov <dv@dv.ru>
> Cc: Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
> Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
> Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
>
>
>
> On Tue, 10 Nov 1998 11:52:33 +0300, Dmitry Valdov wrote:
>
> > Thanks, will be know. But why not to fix it in ppp? :)
>
> Hi Dmitry,
>
> Even if ppp does the route cleanup for you, a signal 9 (KILL) doesn't
> allow it to attempt graceful exit. This means that building cleanup code
> into ppp would not "fix it in ppp", since the code would never be
> reached once a SIGKILL is received.
>
I know it. But why when I'm starting ppp next time it hangs? I think, it
should not hang. It can delete route, print warning or error message and so
on.
Dmitry.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 03:19:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA09841
for freebsd-current-outgoing; Tue, 10 Nov 1998 03:19:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bb.web.sk (web2pvt.web.sk [195.28.73.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09832
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 03:19:27 -0800 (PST)
(envelope-from debnar@zoznam.sk)
Received: from bb.web.sk (debnar@bb.web.sk [195.28.73.33])
by bb.web.sk (8.8.5/8.8.5) with SMTP id MAA11485
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 12:19:04 +0100 (CET)
Date: Tue, 10 Nov 1998 12:19:03 +0100 (CET)
From: Ivan Debnar <debnar@zoznam.sk>
X-Sender: debnar@bb.web.sk
To: current@FreeBSD.ORG
Subject: Compaq Proliant 2500
Message-ID: <Pine.BSI.3.95.981110121649.11468A-100000@bb.web.sk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I would just like to ask, if anyone has tried to run FreeBSD current on
Compaq Proliant 2500 series.
Are drivers available for Compaq Netelignet 10/100 NIC's and for its SCSI
controller ?
Any info appreciated.
I'm going to give it a try tomorow, so I would like to be prepared.
Thanks again
Ivan Debnar
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 03:31:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA11041
for freebsd-current-outgoing; Tue, 10 Nov 1998 03:31:41 -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 DAA11035
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 03:31:36 -0800 (PST)
(envelope-from sthaug@nethelp.no)
From: sthaug@nethelp.no
Received: (qmail 19124 invoked by uid 1001); 10 Nov 1998 11:31:17 +0000 (GMT)
To: debnar@zoznam.sk
Cc: current@FreeBSD.ORG
Subject: Re: Compaq Proliant 2500
In-Reply-To: Your message of "Tue, 10 Nov 1998 12:19:03 +0100 (CET)"
References: <Pine.BSI.3.95.981110121649.11468A-100000@bb.web.sk>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Date: Tue, 10 Nov 1998 12:31:17 +0100
Message-ID: <19122.910697477@verdi.nethelp.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I would just like to ask, if anyone has tried to run FreeBSD current on
> Compaq Proliant 2500 series.
I have 2.2.7-19980914-SNAP up & running on a Proliant 3000. Extremely
stable and fast.
> Are drivers available for Compaq Netelignet 10/100 NIC's and for its SCSI
> controller ?
No driver for the Thunderlan Ethernet controller on the 2.2.7 boot disks
when I installed this - I ended up using an Intel NIC for the installation.
Once installed you can make a kernel with the tl driver. However, checking
the HARDWARE.TXT from a recent (2.2.7-19981103-SNAP) 2.2.7 SNAP, the tl
driver seems to be included on the installation disks now.
The SCSI controller on the 3000 is NCR/Symbios 53c876 based - it appears as
two 53c875 controllers. Supported by the ncr driver.
I had trouble installing a prerelase of 3.0 on this system - no PCI Ethernet
card or SCSI controller was detected. I'm going to make another attempt at
3.0 in a few days.
Not sure about the details for the 2500 though.
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 Nov 10 03:44:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA12027
for freebsd-current-outgoing; Tue, 10 Nov 1998 03:44:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from morgan.angis.su.OZ.AU (morgan.angis.su.OZ.AU [129.78.25.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA12022
for <current@freebsd.org>; Tue, 10 Nov 1998 03:44:24 -0800 (PST)
(envelope-from tonym@angis.usyd.edu.au)
Received: (from tonym@localhost) by morgan.angis.su.OZ.AU (8.8.7/8.6.6) id WAA29147 for current@freebsd.org; Tue, 10 Nov 1998 22:44:04 +1100 (EST)
Date: Tue, 10 Nov 1998 22:44:04 +1100 (EST)
From: Tony Maher <tonym@angis.usyd.edu.au>
Message-Id: <199811101144.WAA29147@morgan.angis.su.OZ.AU>
To: current@FreeBSD.ORG
Subject: Travan TR4 dump/restore
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello,
running current from around 30 Oct 98, having trouble with backups.
Thought it was a hardware problem so installed new tape drive
but it still problems.
from dmesg
ahc0: <Adaptec 2940 SCSI adapter> rev 0x03 int a irq 11 on pci0.9.0
ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs
sa0 at ahc0 bus 0 target 5 lun 0
sa0: <Seagate STT8000N 3.22> Removable Sequential Access SCSI2 device
sa0: 10.0MB/s transfers (10.0MHz, offset 15)
Running
dump 0uabf 64 /dev/nrsa0 /
dump 0uabf 64 /dev/nrsa0 /usr
dump 0uabf 64 /dev/nrsa0 /var
dump 0uabf 64 /dev/nrsa0 /n/01
dump 0uabf 64 /dev/nrsa0 /n/02
Dumps run without any errors, but trying to restore get
"resync restore, skipped 33 blocks"
restore iv
Verify tape and initialize maps
Tape block size is 64
Dump date: Tue Nov 10 19:28:29 1998
Dumped from: the epoch
Level 0 dump of / on zen.my.domain:/dev/da1s1a
Label: none
Extract directories from tape
resync restore, skipped 33 blocks
Initialize symbol table.
Can actually extract files ok from the first dumpset.
However trying to get it from second dumpset
mt rewind
mt -f /dev/nrsa0 fsf
restore ivf /dev/nrsa0
Verify tape and initialize maps
Tape block size is 64
Dump date: Tue Nov 10 19:29:18 1998
Dumped from: the epoch
Level 0 dump of /usr on zen.my.domain:/dev/da1s1g
Label: none
resync restore, skipped 33 blocks
Cannot find file dump list
Exits back to command line.
Is this known problem? Anyone using a TR4 tape drive succesfully?
thanks
tonym
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 05:22:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA22157
for freebsd-current-outgoing; Tue, 10 Nov 1998 05:22:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22149
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 05:22:25 -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 JAA16614;
Tue, 10 Nov 1998 09:21:27 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 10 Nov 1998 09:21:27 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Mike Smith <mike@smith.net.au>
cc: Paul Saab <paul@mu.org>, current@FreeBSD.ORG
Subject: Re: 18gig drive's supported?
In-Reply-To: <199811100615.WAA00484@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811100919330.15423-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 Mon, 9 Nov 1998, Mike Smith wrote:
> > On Mon, 9 Nov 1998, Paul Saab wrote:
> >
> > > did you upgrade this system from a pre-cam system? If you did I
> > > think you need to upgrade sysinstall too.
> >
> > Yes...next question, how to upgrade sysinstall? Went into
> > /usr/src/release/sysinstall, typed 'make cleandir;make depend'...it
> > failed:
> >
> > file2c 'u_char boot0[] = {' '};' < /boot/boot0 >> makedevs.tmp
> > cannot open /boot/boot0: no such file
> > *** Error code 2
> >
> > Am still an aout system...if that means anything/helps?
>
> Go to /sys/boot and say 'make; make install' first. You haven't built
> the world for a long time it seems.
Surprisingly, I did...when I upgraded the system to its currently
level...:( Now I've got sysinstall upgraded and installed, but when I go
to 'label' or 'fdisk', it auto-presents me with da0, but doesn't give me
the old choices of working with any of the other drives...did I miss a new
command line switch her or something like that? Have read man pages, have
built a new libdisk.a *just in case*...
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 Nov 10 05:37:58 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA23394
for freebsd-current-outgoing; Tue, 10 Nov 1998 05:37:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ifi.uio.no (ifi.uio.no [129.240.64.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23389
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 05:37:55 -0800 (PST)
(envelope-from dag-erli@ifi.uio.no)
Received: from gnipahellir.ifi.uio.no (2602@gnipahellir.ifi.uio.no [129.240.64.86])
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id OAA28787;
Tue, 10 Nov 1998 14:37:09 +0100 (MET)
Received: (from dag-erli@localhost) by gnipahellir.ifi.uio.no ; Tue, 10 Nov 1998 14:37:08 +0100 (MET)
Mime-Version: 1.0
To: The Hermit Hacker <scrappy@hub.org>
Cc: Mike Smith <mike@smith.net.au>, Paul Saab <paul@mu.org>,
current@FreeBSD.ORG
Subject: Re: 18gig drive's supported?
References: <Pine.BSF.4.05.9811100919330.15423-100000@thelab.hub.org>
Organization: University of Oslo, Department of Informatics
X-url: http://www.stud.ifi.uio.no/~dag-erli/
X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list
X-disclaimer-1: The views expressed in this article are mine alone, and do
X-disclaimer-2: not necessarily coincide with those of any organisation or
X-disclaimer-3: company with which I am or have been affiliated.
X-Stop-Spam: http://www.cauce.org/
From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= )
Date: 10 Nov 1998 14:37:07 +0100
In-Reply-To: The Hermit Hacker's message of "Tue, 10 Nov 1998 09:21:27 -0400 (AST)"
Message-ID: <xzp3e7rzn24.fsf@gnipahellir.ifi.uio.no>
Lines: 14
X-Mailer: Gnus v5.5/Emacs 19.34
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id FAA23390
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
The Hermit Hacker <scrappy@hub.org> writes:
> Surprisingly, I did...when I upgraded the system to its currently
> level...:( Now I've got sysinstall upgraded and installed, but when I go
> to 'label' or 'fdisk', it auto-presents me with da0, but doesn't give me
> the old choices of working with any of the other drives...did I miss a new
> command line switch her or something like that? Have read man pages, have
> built a new libdisk.a *just in case*...
libdisk.a is a static library. Rebuilding it won't do you any good
unless you rebuild everything that uses it as well.
DES
--
Dag-Erling Smørgrav - dag-erli@ifi.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 Nov 10 05:50:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA24293
for freebsd-current-outgoing; Tue, 10 Nov 1998 05:50:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24283
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 05:50:54 -0800 (PST)
(envelope-from regnauld@EU.org)
Received: from mail.prosa.dk ([192.168.100.254])
by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id OAA14165;
Tue, 10 Nov 1998 14:54:16 +0100 (CET)
(envelope-from regnauld@EU.org)
X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk
Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10])
by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id PAA14706;
Tue, 10 Nov 1998 15:14:37 +0100 (CET)
Received: (from uucp@localhost)
by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) with UUCP id OAA21789;
Tue, 10 Nov 1998 14:49:10 +0100 (CET)
Received: (from regnauld@localhost)
by stimpy.prosa.dk (8.9.1/8.9.1/stimpy-1.0) id OAA01158;
Tue, 10 Nov 1998 14:52:45 +0100 (CET)
(envelope-from regnauld)
Message-ID: <19981110145245.60834@stimpy.prosa.dk>
Date: Tue, 10 Nov 1998 14:52:45 +0100
From: Phil Regnauld <regnauld@EU.org>
To: alk@pobox.com
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <13895.40864.375388.573511@avalon.east>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.88e
In-Reply-To: <13895.40864.375388.573511@avalon.east>; from Tony Kimball on Mon, Nov 09, 1998 at 08:08:01PM -0600
X-Operating-System: FreeBSD 3.0-CURRENT i386
Phone: +45 3336 4148
Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark
Organization: PROSA
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Tony Kimball writes:
> Lately, I'm still seing lines like this:
>
> > Apr 19 12:03:43 lupo /kernel: swap_pager: suggest more swap space: 124 MB
I have a stupid program that mallocs all the memory it can, then gets
shot by the system.
The system has 128MB RAM, and 256 MB swap.
Around 100MB of swap used, the system comes out and says:
/kernel: swap_pager: suggest more swap space: 254 MB
- Is it supposed to come out that early
- What is the suggestion based on ? Is it telling me
to _add_ 254MB of swap to my system (+ 254 = 510 MB), or
to _increase_ my swap space, which already is above
254 ? This looks a bit weird...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 05:55:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA24923
for freebsd-current-outgoing; Tue, 10 Nov 1998 05:55:32 -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 FAA24918
for <current@freebsd.org>; Tue, 10 Nov 1998 05:55:28 -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 AAA23270;
Wed, 11 Nov 1998 00:25:10 +1030 (CST)
Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM)
id AA26639; Wed, 11 Nov 1998 00:25:32 +1030
Date: Wed, 11 Nov 1998 00:25:31 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
X-Sender: kkennawa@bragg
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: grog@lemis.com, current@FreeBSD.ORG
Subject: world stuff which doesnt compile with egcs (was Re: newer gcc?)
In-Reply-To: <Pine.OSF.4.05.9811101205130.9655-100000@spectrum.physics.adelaide.edu.au>
Message-Id: <Pine.OSF.4.05.9811110010270.19783-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, 10 Nov 1998, Kris Kennaway wrote:
> On Mon, 9 Nov 1998, Jordan K. Hubbard wrote:
>
> > > The reason i was asking is that i may bmake it and stick it into my tree,
> >
> > That's a bit premature. I'd be more interested if you could even build
> > the world from egcs installed in /usr/local.
>
> >From memory (I don't have the list with me), the following things do not
> compile with the current egcs port and die with various errors:
>
> lib/libc
> lib/libc_r
> lib/libstand
> games/bs
> games/<one other one>
games/rogue
sbin/vinum (one simple patch included, doesnt fix the second problem)
libexec/rtld-elf/
> gnu/lib/libg++
> gnu/lib/libstd++
> gnu/usr.bin/groff
> sys/<lots of stuff> - the boot code dies with errors, and the modules die
> because of the -elf directive or something
This was incorrect: the only thing which fails to compile now is
sys/i386/loader. The rest (including modules, etc) must have been transient
failures at the time I tested which have since been fixed. Some of the modules
give me warnings about extra format arguments as does the kernel when I
compile it under ELF; will I notice anything different with such an
egcs-compiled module (or kernel)?
> lkm/* because of -aout
Following is a list of the exact point at which the above die. One of the
vinum errors was caused by what I presume to be a typo'ed variable (I couldnt
find any definition of the datatype it was barfing on). The other one I
couldnt find any easy fix in my quick browsing of the code (hey, I'm a
physicist, not a C programmer! :) - no doubt Greg will be able to identify any
simple solution.
Note that assert.c seems to cause problems whenever it's used (libc, libc_r,
libstand). The three gnu breakages are caused by differences in the c++
support between gcc and egcs, apparently (I didnt bother to include the output
figuring probably no-one cared :)
************
*** lib/libc
************
--- assert.o ---
/usr2/src/lib/libc/../libc/gen/assert.c:43: parse error before string constant
/usr2/src/lib/libc/../libc/gen/assert.c:46: parse error before `{'
/usr2/src/lib/libc/../libc/gen/assert.c:50: conflicting types for `abort'
/usr/include/stdlib.h:85: previous declaration of `abort'
/usr2/src/lib/libc/../libc/gen/assert.c:50: warning: data definition has no type or storage class
/usr2/src/lib/libc/../libc/gen/assert.c:52: parse error before `}'
*** Error code 1
**************
*** lib/libc_r
**************
- as for libc
************
*** games/bs
************
(probably egcs breakage?)
cc -O2 -pipe -mpentium -march=pentium -c bs.c
{standard input}: Assembler messages:
{standard input}:650: Error: base/index register must be 32 bit register
{standard input}:651: Error: base/index register must be 32 bit register
{standard input}:652: Error: base/index register must be 32 bit register
{standard input}:653: Error: base/index register must be 32 bit register
{standard input}:654: Error: base/index register must be 32 bit register
***************
*** games/rogue
***************
cc -O2 -pipe -mpentium -march=pentium -DUNIX -fwritable-strings -c message.c
message.c:56: initializer element for `msgs[0]' is not constant
message.c:56: initializer element for `msgs[1]' is not constant
message.c:56: initializer element for `msgs[2]' is not constant
message.c:56: initializer element for `msgs[3]' is not constant
message.c:56: initializer element for `msgs[4]' is not constant
**************
*** sbin/vinum
**************
In file included from /usr2/src/sys/modules/vinum/../../../lkm/vinum/vinumhdr.h:91,
from /usr2/src/sys/modules/vinum/../../../lkm/vinum/request.c:44:
/usr2/src/sys/modules/vinum/../../../lkm/vinum/vinumext.h:44: warning: type defaults to `int' in declaration of `debug'
/usr2/src/sys/modules/vinum/../../../lkm/vinum/request.c: In function `vinumstart':
/usr2/src/sys/modules/vinum/../../../lkm/vinum/request.c:209: incompatible type for argument 2 of `logrq'
/usr2/src/sys/modules/vinum/../../../lkm/vinum/request.c: In function `launch_requests':
/usr2/src/sys/modules/vinum/../../../lkm/vinum/request.c:386: incompatible type for argument 2 of `logrq'
/usr2/src/sys/modules/vinum/../../../lkm/vinum/request.c:414: incompatible type for argument 2 of `logrq'
*** Error code 1
cc -I/usr2/src/sys/modules/vinum/../../../lkm/vinum -O -g -I/usr/include/machine -DDEBUG -Wall -Wno-unused -Wno-parentheses -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -ansi -DKLD_MODULE -nostdinc -I- -I/usr2/src/sys/modules/vinum/../../../lkm/vinum -I/usr/include/machine -I/usr2/src/sys/modules/vinum -I/usr2/src/sys/modules/vinum/@ -c /usr2/src/sys/modules/vinum/../../../lkm/vinum/util.c
In file included from /usr2/src/sys/modules/vinum/../../../lkm/vinum/vinumhdr.h:91,
from /usr2/src/sys/modules/vinum/../../../lkm/vinum/util.c:41:
/usr2/src/sys/modules/vinum/../../../lkm/vinum/vinumext.h:44: warning: type defaults to `int' in declaration of `debug'
/usr2/src/sys/modules/vinum/../../../lkm/vinum/util.c: In function `VolState':
/usr2/src/sys/modules/vinum/../../../lkm/vinum/util.c:157: conversion to incomplete type
--- util.c~ Wed Sep 16 15:26:21 1998
+++ util.c Tue Nov 10 23:31:45 1998
@@ -154,7 +154,7 @@
int i;
for (i = 0; i < STATECOUNT(vol); i++)
if (strcmp(text, volstatetext[i]) == 0) /* found it */
- return (enum volstate) i;
+ return (enum volumestate) i;
return -1;
}
gnu/lib/libg++
gnu/lib/libstdc++
gnu/usr.bin/groff
*********************
*** libexec/rtld-elf/
*********************
map_object.o(.text+0x107): undefined reference to `__eprintf'
*******************
*** sys/i386/loader
*******************
cc -nostdlib -static -Ttext 0x1000 -o loader.sym /usr2/src/sys/boot/i386/loader/../btx/lib/crt0.o main.o conf.o bcache.o boot.o commands.o console.o devopen.o interp.o interp_backslash.o interp_parse.o load_aout.o load_elf.o ls.o misc.o module.o panic.o isapnp.o pnp.o vers.o -lstand /usr2/src/sys/boot/i386/loader/../libi386/libi386.a -lstand
cc: 0x1000: No such file or directory
****************
*** lib/libstand
****************
assert.c:33: parse error before string constant
assert.c:36: warning: type defaults to `int' in declaration of `exit'
assert.c:36: warning: data definition has no type or storage class
assert.c:37: parse error before `}'
lkm/ (lack of -aout directive for egcs)
Kris
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 05:57:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA25113
for freebsd-current-outgoing; Tue, 10 Nov 1998 05:57:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25105
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 05:57:52 -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 JAA16756;
Tue, 10 Nov 1998 09:57:10 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 10 Nov 1998 09:57:10 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" <dag-erli@ifi.uio.no>
cc: Mike Smith <mike@smith.net.au>, Paul Saab <paul@mu.org>,
current@FreeBSD.ORG
Subject: Re: 18gig drive's supported?
In-Reply-To: <xzp3e7rzn24.fsf@gnipahellir.ifi.uio.no>
Message-ID: <Pine.BSF.4.05.9811100955480.15423-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8BIT
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 10 Nov 1998, Dag-Erling C. [iso-8859-1] Smørgrav wrote:
> The Hermit Hacker <scrappy@hub.org> writes:
> > Surprisingly, I did...when I upgraded the system to its currently
> > level...:( Now I've got sysinstall upgraded and installed, but when I go
> > to 'label' or 'fdisk', it auto-presents me with da0, but doesn't give me
> > the old choices of working with any of the other drives...did I miss a new
> > command line switch her or something like that? Have read man pages, have
> > built a new libdisk.a *just in case*...
>
> libdisk.a is a static library. Rebuilding it won't do you any good
> unless you rebuild everything that uses it as well.
I knew I was going to screw up along here somewhere, and it was
going to be one of those "boot to the head" sort of screw ups :( Just
clued into what it was...I was working on the wrong machine :( I run
screen on the remote server, and had telnet'd into my home machine...both
running 3.0...I rebuilt sysinstall on my home machine, not on the server I
wanted to work on :(
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 Nov 10 06:15:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA27109
for freebsd-current-outgoing; Tue, 10 Nov 1998 06:15:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from aldan.algebra.com (kot.ne.mediaone.net [24.128.29.55])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27103
for <current@freebsd.org>; Tue, 10 Nov 1998 06:15:30 -0800 (PST)
(envelope-from mi@aldan.algebra.com)
Received: (from mi@localhost)
by aldan.algebra.com (8.8.8/8.8.7) id OAA13678
for current@freebsd.org; Tue, 10 Nov 1998 14:14:50 GMT
(envelope-from mi)
From: Mikhail Teterin <mi@aldan.algebra.com>
Message-Id: <199811101414.OAA13678@aldan.algebra.com>
Subject: build fails in src/lib/csu/i386/
To: current@FreeBSD.ORG
Date: Tue, 10 Nov 1998 14:14:50 +0000 (GMT)
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
CVSUPed yesterday after removing the entire tree first. Then, I also did
``make includes'', just in case. Still:
cc -O -DNDEBUG -DLIBC_SCCS -fno-omit-frame-pointer -c -DCRT0 -DDYNAMIC /home/mi/src/lib/csu/i386/crt0.c -o crt0.o
/home/mi/src/lib/csu/i386/crt0.c: In function `__do_dynamic_link':
/home/mi/src/lib/csu/i386/crt0.c:196: storage size of `crt' isn't known
/home/mi/src/lib/csu/i386/crt0.c:260: `CRT_VERSION_BSD_5' undeclared (first use this function)
/home/mi/src/lib/csu/i386/crt0.c:260: (Each undeclared identifier is reported only once
/home/mi/src/lib/csu/i386/crt0.c:260: for each function it appears in.)
/home/mi/src/lib/csu/i386/crt0.c:264: `CRT_VERSION_BSD_4' undeclared (first use this function)
/home/mi/src/lib/csu/i386/crt0.c:268: `CRT_VERSION_BSD_3' undeclared (first use this function)
/home/mi/src/lib/csu/i386/crt0.c:269: invalid use of undefined type `struct _dynamic'
/home/mi/src/lib/csu/i386/crt0.c:275: dereferencing pointer to incomplete type
/home/mi/src/lib/csu/i386/crt0.c:288: `LDSO_VERSION_HAS_DLEXIT' undeclared (first use this function)
/home/mi/src/lib/csu/i386/crt0.c:289: dereferencing pointer to incomplete type
TIA!
-mi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 06:16:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA27161
for freebsd-current-outgoing; Tue, 10 Nov 1998 06:16:00 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27156
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 06:15:59 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id JAA01180;
Tue, 10 Nov 1998 09:16:16 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Tue, 10 Nov 1998 09:16:16 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Phil Regnauld <regnauld@EU.org>
cc: alk@pobox.com, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <19981110145245.60834@stimpy.prosa.dk>
Message-ID: <Pine.BSF.4.05.9811100914130.343-100000@porkfriedrice.ny.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
Now that i think about it i have had the:
/kernel: swap_pager: suggest more swap space: 254 MB
unsure about the number, but in my case i didn't notice anything flaky
about my system afterwards.
(i had left for work and done a
make -j<some really large number for kicks> buildworld)
Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com
-- There are operating systems, and then there's FreeBSD.
-- http://www.freebsd.org/ 3.0-current
On Tue, 10 Nov 1998, Phil Regnauld wrote:
> Tony Kimball writes:
> > Lately, I'm still seing lines like this:
> >
> > > Apr 19 12:03:43 lupo /kernel: swap_pager: suggest more swap space: 124 MB
>
> I have a stupid program that mallocs all the memory it can, then gets
> shot by the system.
>
> The system has 128MB RAM, and 256 MB swap.
>
> Around 100MB of swap used, the system comes out and says:
>
>
> /kernel: swap_pager: suggest more swap space: 254 MB
>
>
> - Is it supposed to come out that early
> - What is the suggestion based on ? Is it telling me
> to _add_ 254MB of swap to my system (+ 254 = 510 MB), or
> to _increase_ my swap space, which already is above
> 254 ? This looks a bit weird...
>
> 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 Nov 10 06:30:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA28579
for freebsd-current-outgoing; Tue, 10 Nov 1998 06:30:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.gtn.com (mail.gtn.com [192.109.159.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28567
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 06:30:49 -0800 (PST)
(envelope-from andreas@klemm.gtn.com)
Received: (from uucp@localhost)
by mail.gtn.com (8.8.6/8.8.6) with UUCP id PAA05498;
Tue, 10 Nov 1998 15:15:29 +0100 (MET)
Received: (from andreas@localhost)
by klemm.gtn.com (8.9.1/8.9.1) id OAA23094;
Tue, 10 Nov 1998 14:57:43 +0100 (CET)
(envelope-from andreas)
Message-ID: <19981110145743.A23087@klemm.gtn.com>
Date: Tue, 10 Nov 1998 14:57:43 +0100
From: Andreas Klemm <andreas@klemm.gtn.com>
To: Tony Maher <tonym@angis.usyd.edu.au>, current@FreeBSD.ORG
Subject: Re: Travan TR4 dump/restore
References: <199811101144.WAA29147@morgan.angis.su.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199811101144.WAA29147@morgan.angis.su.OZ.AU>; from Tony Maher on Tue, Nov 10, 1998 at 10:44:04PM +1100
X-Disclaimer: A free society is one where it is safe to be unpopular
X-Operating-System: FreeBSD 3.0-CURRENT SMP
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, Nov 10, 1998 at 10:44:04PM +1100, Tony Maher wrote:
>
> from dmesg
> ahc0: <Adaptec 2940 SCSI adapter> rev 0x03 int a irq 11 on pci0.9.0
> ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs
> sa0 at ahc0 bus 0 target 5 lun 0
> sa0: <Seagate STT8000N 3.22> Removable Sequential Access SCSI2 device
> sa0: 10.0MB/s transfers (10.0MHz, offset 15)
>
> Running
> dump 0uabf 64 /dev/nrsa0 /
> dump 0uabf 64 /dev/nrsa0 /usr
> dump 0uabf 64 /dev/nrsa0 /var
> dump 0uabf 64 /dev/nrsa0 /n/01
> dump 0uabf 64 /dev/nrsa0 /n/02
>
> Dumps run without any errors, but trying to restore get
> "resync restore, skipped 33 blocks"
What if you use 32 blocks ?
dump 0uabf 32 /dev/nrsa0 /
....
--
Andreas Klemm http://www.FreeBSD.ORG/~andreas
What gives you 90% more speed, for example, in kernel compilation ?
http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html
"NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP''
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 06:39:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA29387
for freebsd-current-outgoing; Tue, 10 Nov 1998 06:39:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from heaven.gigo.com (ppp.gigo.com [207.173.132.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29350;
Tue, 10 Nov 1998 06:38:50 -0800 (PST)
(envelope-from jfesler@gigo.com)
Received: by heaven.gigo.com (8.8.8/8.8.8) with SMTP id GAA10265;
Tue, 10 Nov 1998 06:37:42 -0800 (PST)
X-SMTP: helo heaven.gigo.com from jfesler@gigo.com server jfesler@heaven.gigo.com ip 207.173.133.57
Date: Tue, 10 Nov 1998 06:37:39 -0800 (PST)
From: Jason Fesler <jfesler@gigo.com>
To: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
cc: Dmitry Valdov <dv@dv.ru>, Brian Somers <brian@FreeBSD.ORG>,
current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-Reply-To: <Pine.OSF.4.05.9811101930000.10597-100000@spectrum.physics.ade
laide.edu.au>
Message-ID: <Pine.BSF.4.00.9811100634590.25966-100000@heaven.gigo.com>
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 the "implicit bug report", Brian, but I've been meaning to track
> this down for a long time and make sure it's not user error. I often see this
I've had this since the 2.2.2 days when I first started running ppp.
After a while (hours, days, weeks - random) either carrier isn't noticed
as being missing, or all outgoing packets don't cross the serial cable to
to the other side. After a while I kinda gave up.
I now every few minutes fping a few hosts on the nearby remote side. If
they _all_ fail (a good 10 second timeout is given) then I kill -9 the ppp
session, wait 2 seconds, then restart ppp. It's caught every strange
random bug on either side soon enough that I no longer have to try and
call home and walk the wife through ppp..
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 06:55:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA01484
for freebsd-current-outgoing; Tue, 10 Nov 1998 06:55:46 -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 GAA01079
for <freebsd-current@FreeBSD.ORG>; Tue, 10 Nov 1998 06:52:32 -0800 (PST)
(envelope-from daeron@Wit401305.student.utwente.nl)
From: daeron@Wit401305.student.utwente.nl
Received: (from daeron@localhost)
by Wit401305.student.utwente.nl (8.9.1/8.9.1) id PAA06367;
Tue, 10 Nov 1998 15:41:08 +0100 (CET)
(envelope-from daeron)
Date: Tue, 10 Nov 1998 15:41:08 +0100 (CET)
Message-Id: <199811101441.PAA06367@Wit401305.student.utwente.nl>
To: freebsd-current@FreeBSD.ORG
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-URL: http://www.freebsd.org/handbook/handbook272.html
X-Mailer: Lynx, Version 2.8.1dev.25
X-Personal_name: Pascal Hofstee
Subject: subscribe freebsd-current
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
subscribe freebsd-current
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 07:03:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA02439
for freebsd-current-outgoing; Tue, 10 Nov 1998 07:03:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02433
for <current@freebsd.org>; Tue, 10 Nov 1998 07:03:31 -0800 (PST)
(envelope-from archer@grape.carrier.kiev.ua)
Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111])
by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) with ESMTP id RAA14123;
Tue, 10 Nov 1998 17:03:05 +0200 (EET)
(envelope-from archer@grape.carrier.kiev.ua)
Received: (from uucp@localhost)
by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id RAA19328;
Tue, 10 Nov 1998 17:00:57 +0200 (EET)
(envelope-from archer@grape.carrier.kiev.ua)
Received: (from archer@localhost)
by grape.carrier.kiev.ua (8.9.1/8.9.1) id QAA28210;
Tue, 10 Nov 1998 16:56:26 +0200 (EET)
(envelope-from archer)
Date: Tue, 10 Nov 1998 16:56:26 +0200 (EET)
From: Alexander Litvin <archer@lucky.net>
Message-Id: <199811101456.QAA28210@grape.carrier.kiev.ua>
To: Greg Lehey <grog@lemis.com>
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
X-Newsgroups: grape.freebsd.current
In-Reply-To: <199811092056.PAA22043@lor.watermarkgroup.com> <199811100136.DAA00563@grape.carrier.kiev.ua> <19981110154327.X499@freebie.lemis.com>
Organization: Lucky Grape
User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386))
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <19981110154327.X499@freebie.lemis.com> you wrote:
GL> On Tuesday, 10 November 1998 at 3:36:28 +0200, Alexander Litvin wrote:
>> LC> I went through swap_pager.c today and found a problem that could potentially
>> LC> have bad consequences. It's a comparison between page index in the swap pager
>> LC> and the size of the vm object, since a shadowed object may have a non-zero
>> LC> paging offset with respect to the swap pager, the comparison should have taken
>> LC> the offset into account. This piece of code has been there since '95, so
>> LC> I can't say if this was responsible for the daemon dying problem.
>>
>> It is definitely not responsible. At least for this particular problem,
>> though it may fix something else ;)
>>
>> After applying the patch, and artificially exhausting memory, I promptly
>> got:
>>
>> Nov 10 03:15:34 grape /kernel: swap_pager: suggest more swap space: 61 MB
>> Nov 10 03:16:26 grape /kernel: pid 310 (sendmail), uid 0: exited on signal 11
>> Nov 10 03:17:26 grape /kernel: pid 311 (sendmail), uid 0: exited on signal 11
>> Nov 10 03:18:25 grape /kernel: pid 313 (sendmail), uid 0: exited on signal 11
>> Nov 10 03:19:25 grape /kernel: pid 353 (sendmail), uid 0: exited on signal 11
>> Nov 10 03:20:26 grape /kernel: pid 394 (sendmail), uid 0: exited on signal 11
GL> Ah, now that's one that I've been getting without exhausting memory.
GL> I'm assuming that these dying sendmails are children of the daemon.
GL> What happens when you kill -1 the daemon ("accepting connections on
GL> port 25 (sendmail)")? In my experience, it *always* dies with a
GL> SIGSEGV after these messages have occurred.
Well, as I understand, 'swap_pager: suggest more swap space' does
not mean that memory is exhausted, but only that it is about to
be exhausted. At least, in this case it didn't come to any processes
being killed by kernel.
You're right -- that sendmails were childs of a daemon (queue runners).
I'm not sure about what happens if I send SIGHUP to the daemon. I
think it may or may not restart -- it depends. Last time I examined
a 'deseased' daemon (it was not sendmail, but a dummy daemon written
specially for testing), it appeared that some range of process memory,
where code of dynamic library lives, was corrupt (zeroed in that case).
I'll try later to kill -1 such daemon. Now I'm in the process of testing
Dima's kludge. Until now I was unable to reproduce a problem. Daemons
keep living ;)
GL> Greg
GL> --
GL> See complete headers for address, home page and phone numbers
GL> finger grog@lemis.com for PGP public key
---
Dealing with failure is easy:
Work hard to improve.
Success is also easy to handle:
You've solved the wrong problem. Work hard to improve.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 07:16:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA04349
for freebsd-current-outgoing; Tue, 10 Nov 1998 07:16:32 -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 HAA04344
for <current@freebsd.org>; Tue, 10 Nov 1998 07:16:29 -0800 (PST)
(envelope-from lists@tar.com)
Received: from ppro.tar.com (ppro.tar.com [204.95.187.9])
by ns.tar.com (8.9.1/8.8.7) with SMTP id JAA20439;
Tue, 10 Nov 1998 09:16:04 -0600 (CST)
Message-Id: <199811101516.JAA20439@ns.tar.com>
From: "Richard Seaman, Jr." <lists@tar.com>
To: "Brian Feldman" <green@unixhelp.org>
Cc: "current@freebsd.org" <current@FreeBSD.ORG>
Date: Tue, 10 Nov 98 09:16:04 -0600
Reply-To: "Richard Seaman, Jr." <lists@tar.com>
X-Mailer: PMMail 1.92 For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: RFSIGSHARE ready?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 6 Nov 1998 21:27:50 -0500 (EST), Brian Feldman wrote:
>I suppose it is. LinuxThreads don't work tho... I need %@#!^ testers!
I looked briefly at your code, and I have a question. I understand
that the "flags" argument to the clone call takes a signal number
in the low order 8 bits of flags. This is the signal to be sent to
the parent on exit of the thread.
I can see where you implement signal sharing, but not where you
record and implement this exit signal handling. Linuxthreads relies
on the thread manager thread receiving a "PTHREAD_SIG_RESTART"
signal (actually SIGUSR1) when threads exit.
Perhaps I've missed something?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 07:34:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA06557
for freebsd-current-outgoing; Tue, 10 Nov 1998 07:34:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from saturn.spel.com (saturn.spel.com [208.226.39.196])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06551
for <current@freebsd.org>; Tue, 10 Nov 1998 07:34:16 -0800 (PST)
(envelope-from mturpin@saturn.spel.com)
Received: from localhost (mturpin@localhost)
by saturn.spel.com (8.9.1/8.9.1) with ESMTP id KAA00214;
Tue, 10 Nov 1998 10:30:43 -0500 (EST)
(envelope-from mturpin@saturn.spel.com)
Date: Tue, 10 Nov 1998 10:30:43 -0500 (EST)
From: Mark Turpin <mturpin@saturn.spel.com>
To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
cc: current@FreeBSD.ORG
Subject: Re: psmintr: out of sync
In-Reply-To: <199811100340.MAA14161@zodiac.mech.utsunomiya-u.ac.jp>
Message-ID: <Pine.BSF.4.05.9811101005250.3134-100000@saturn.spel.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's odd. Now I can't get it to error again. I used my old kernel,
the one without the flags 0x100 and it doesn't give me the error.
Yesterday I could get it to do it every time I restarted the machine. I'll
try to get it to do it again. But for the time being it seems to work
fine without giving the messages.
But, You can see how many of these messages appeared.
Weird.
Thanks anyway
Mark Turpin
Nov 9 15:13:28 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:28 saturn /kernel: psmintr: out of sync (00c0 != 0008).
Nov 9 15:13:28 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:28 saturn last message repeated 2 times
Nov 9 15:13:28 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:28 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:28 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:28 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:28 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:28 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:28 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:29 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:29 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:29 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:29 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:29 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:29 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:29 saturn last message repeated 2 times
Nov 9 15:13:29 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:29 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:29 saturn /kernel: psmintr: out of sync (00c0 != 0008).
Nov 9 15:13:29 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:29 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:30 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:30 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:30 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:31 saturn last message repeated 17 times
Nov 9 15:13:31 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:31 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:31 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:31 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:31 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:31 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn last message repeated 4 times
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn last message repeated 2 times
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn last message repeated 2 times
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn last message repeated 2 times
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:32 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn last message repeated 10 times
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn last message repeated 6 times
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c0 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c0 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c0 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c0 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c0 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c0 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c0 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn last message repeated 2 times
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn last message repeated 2 times
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:33 saturn last message repeated 3 times
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c0 != 0008).
Nov 9 15:13:33 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:34 saturn last message repeated 5 times
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (0000 != 0008).
Nov 9 15:13:34 saturn last message repeated 2 times
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (00c8 != 0008).
Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (0000 != 0008).
> > I am getting the following error when I run X.
>
> Would you describe your system? Motherboard, CPU, X server...
>
> >Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (0000 != 0008).
> >Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (00c8 != 0008).
>
> Do you see them often, or just occasionally? Is the mouse working,
> or is it totally unusable?
>
> If the mouse is working and you see the above messages just occasionally,
> please ignore the messages.
>
> The "psmintor: out of sync" message is generated if
>
> a) there is mismatch of the mouse protocol; the psm driver is expecting
> a wrong data format (this is unlikely in your case because your mouse
> is correctly recognized as NetMouse). If this happens, we need to fix
> the psm driver; there is a bug somewhere.
> b) Or, if some data bytes from the mouse are somehow lost. While I don't
> like this happening, it is relatively harmless because the psm driver
> should be able to resyunc with the mouse data stream.
> c) Or, if you are using a display/keyboard/mouse switch box. Some swich
> box products do not constantly supply power to the mouse and may
> momentalily cut the power when switching between host computers. This
> will reset the mouse and lose settings in the mouse which the psm driver
> has carefully set up. This may lead to out-of-sync situation sooner
> or later. Other switch products do supply power OK, but
> its built-in CPU tries to emulate/translate mouse data. The problem
> is that the firmware of the built-in CPU is sometimes just buggy or
> is not good enough and may confuse the psm driver.
>
> >An older message said to try adding flags 0x100 to the device line in the
> >kernel config file. That did make the errors stop.
>
> Do you mean that the mouse was not working but now works because of
> the flags 0x100? Or, the mouse was working and it now works too AND
> there is no more error messages?
>
> >The mouse is a Genius NetMouse Pro. Below are the startup messages.
> >
> [...]
> >Nov 9 15:19:07 saturn /kernel: psm0: current command byte:0065
> >Nov 9 15:19:07 saturn /kernel: kbdio: TEST_AUX_PORT status:0000
> >Nov 9 15:19:07 saturn /kernel: kbdio: RESET_AUX return code:00fa
> >Nov 9 15:19:07 saturn /kernel: kbdio: RESET_AUX status:00aa
> >Nov 9 15:19:07 saturn /kernel: kbdio: RESET_AUX ID:0000
> >Nov 9 15:19:07 saturn /kernel: psm: status 00 02 64
> >Nov 9 15:19:07 saturn /kernel: psm: status 00 03 06
> >Nov 9 15:19:07 saturn /kernel: psm: status 00 33 55
> >Nov 9 15:19:07 saturn /kernel: psm: data 18 ff 00
> >Nov 9 15:19:07 saturn /kernel: psm: status 00 02 64
> >Nov 9 15:19:08 saturn /kernel: psm0 at 0x60-0x64 irq 12 on motherboard
> >Nov 9 15:19:08 saturn /kernel: psm0: model NetMouse, device ID 0, 3 buttons
> >Nov 9 15:19:08 saturn /kernel: psm0: config:00000000, flags:00000000, packet
> >size:4
> >Nov 9 15:19:08 saturn /kernel: psm0: syncmask:c8, syncbits:08
>
> NetMouse Pro is a variant of NetMouse. Looks like it is correctly
> recognized.
>
> Kazu
> yokota@FreeBSD.ORG
>
>
>
-----------------------------------------------------------------------------
Mark Turpin | Consulting - Training - Network Installation
Systems Engineer |
Main Street Technology Centre | http://www.MainStreetTech.com
-----------------------------------------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 07:48:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA07853
for freebsd-current-outgoing; Tue, 10 Nov 1998 07:48:30 -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 HAA07848
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 07:48:27 -0800 (PST)
(envelope-from gjp@gjp.erols.com)
Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1])
by gjp.erols.com (8.9.1/8.8.7) with ESMTP id KAA03640;
Tue, 10 Nov 1998 10:43:47 -0500 (EST)
(envelope-from gjp@gjp.erols.com)
To: Alfred Perlstein <bright@hotjobs.com>
cc: Phil Regnauld <regnauld@EU.org>, alk@pobox.com, current@FreeBSD.ORG
From: "Gary Palmer" <gpalmer@FreeBSD.ORG>
Subject: Re: The infamous dying daemons bug
In-reply-to: Your message of "Tue, 10 Nov 1998 09:16:16 EST."
<Pine.BSF.4.05.9811100914130.343-100000@porkfriedrice.ny.genx.net>
Date: Tue, 10 Nov 1998 10:43:47 -0500
Message-ID: <3636.910712627@gjp.erols.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Alfred Perlstein wrote in message ID
<Pine.BSF.4.05.9811100914130.343-100000@porkfriedrice.ny.genx.net>:
>
> Now that i think about it i have had the:
>
> /kernel: swap_pager: suggest more swap space: 254 MB
>
> unsure about the number, but in my case i didn't notice anything flaky
> about my system afterwards.
John Dyson added this warning a few months ago, and the times that
I've seen it are when the machine *just* starts hitting swap space,
and is no-where near running out. No offense to John, but I don't
think that whatever algorythm he uses in generating that message is
anywhere near to being right, and I wonder what peoples opinions about
either hiding it behind bootverbose or removing it are?
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 Tue Nov 10 08:00:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA08961
for freebsd-current-outgoing; Tue, 10 Nov 1998 08:00: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 IAA08956
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 08:00:17 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id HAA00146; Tue, 10 Nov 1998 07:52:04 -0800 (PST)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
id sma000142; Tue Nov 10 07:51:44 1998
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id HAA07789; Tue, 10 Nov 1998 07:51:44 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199811101551.HAA07789@bubba.whistle.com>
Subject: Re: ThinkPad 600E
In-Reply-To: <Pine.BSF.4.03.9811091559390.3471-100000@resnet.uoregon.edu> from Doug White at "Nov 9, 98 04:00:00 pm"
To: dwhite@resnet.uoregon.edu (Doug White)
Date: Tue, 10 Nov 1998 07:51:44 -0800 (PST)
Cc: alexandr@mail.eecis.udel.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
Doug White writes:
> > My work-sponsored laptop has a DVD as well, which is recognized
> > as a normal CD-ROM and works fine as such:
> >
> > wdc1 at 0x170-0x177 irq 15 on isa
> > wdc1: unit 0 (atapi): <MATSHITADVD-ROM SR-8171/058A>, removable, accel, dma, iordis
>
> Hm, it does attach as wcd0? Just curious to see the wcd* messages
> printed below this one.
Yep.. Here's the complete wd* output:
wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff on isa
wdc0: unit 0 (wd0): <TOSHIBA MK6409MAV>, 32-bit, multi-block-16
wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 on isa
wdc1: unit 0 (atapi): <MATSHITADVD-ROM SR-8171/058A>, removable, accel, dma, iordis
wcd0: 3437Kb/sec, 512Kb cache, audio play, 255 volume levels, ejectable tray
wcd0: no disc inside, unlocked
-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 Tue Nov 10 08:07:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA09478
for freebsd-current-outgoing; Tue, 10 Nov 1998 08:07:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09467;
Tue, 10 Nov 1998 08:07:27 -0800 (PST)
(envelope-from jfieber@fallout.campusview.indiana.edu)
Received: from localhost (jfieber@localhost)
by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id LAA12748;
Tue, 10 Nov 1998 11:07:04 -0500 (EST)
Date: Tue, 10 Nov 1998 11:07:04 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Gary Palmer <gpalmer@FreeBSD.ORG>
cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <3636.910712627@gjp.erols.com>
Message-ID: <Pine.BSF.4.05.9811101055580.8312-100000@fallout.campusview.indiana.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 Tue, 10 Nov 1998, Gary Palmer wrote:
> John Dyson added this warning a few months ago, and the times that
> I've seen it are when the machine *just* starts hitting swap space,
> and is no-where near running out. No offense to John, but I don't
> think that whatever algorythm he uses in generating that message is
> anywhere near to being right, and I wonder what peoples opinions about
> either hiding it behind bootverbose or removing it are?
Even if the algorithm were right, the meaning of the message is
clear as mud. So it tells me 125MB. Okay. Um... 125MB? What
the heck am I supposed to do with that? Where did the number
come from? What does it mean?
The message isn't useful unless it can be understood. Judging
from other people's comments, I'm not alone in being confused by
it.
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 08:23:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA11507
for freebsd-current-outgoing; Tue, 10 Nov 1998 08:23:48 -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 IAA11501;
Tue, 10 Nov 1998 08:23:39 -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 RAA00162;
Tue, 10 Nov 1998 17:12:07 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id RAA20835;
Tue, 10 Nov 1998 17:12:06 +0100 (MET)
Message-ID: <19981110171205.19613@follo.net>
Date: Tue, 10 Nov 1998 17:12:05 +0100
From: Eivind Eklund <eivind@yes.no>
To: Gary Palmer <gpalmer@FreeBSD.ORG>, Alfred Perlstein <bright@hotjobs.com>
Cc: Phil Regnauld <regnauld@EU.org>, alk@pobox.com, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <Pine.BSF.4.05.9811100914130.343-100000@porkfriedrice.ny.genx.net> <3636.910712627@gjp.erols.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <3636.910712627@gjp.erols.com>; from Gary Palmer on Tue, Nov 10, 1998 at 10:43:47AM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, Nov 10, 1998 at 10:43:47AM -0500, Gary Palmer wrote:
> Alfred Perlstein wrote in message ID
> <Pine.BSF.4.05.9811100914130.343-100000@porkfriedrice.ny.genx.net>:
> >
> > Now that i think about it i have had the:
> >
> > /kernel: swap_pager: suggest more swap space: 254 MB
> >
> > unsure about the number, but in my case i didn't notice anything flaky
> > about my system afterwards.
>
> John Dyson added this warning a few months ago, and the times that
> I've seen it are when the machine *just* starts hitting swap space,
> and is no-where near running out. No offense to John, but I don't
> think that whatever algorythm he uses in generating that message is
> anywhere near to being right, and I wonder what peoples opinions about
> either hiding it behind bootverbose or removing it are?
Based on my reading of the code (and I don't fully understand the VM
code, so this may be a wrong analysis):
That message seems to be very right. It seems to come when we get
into a 'memory overcommit' situation (ie, there isn't enough swap to
satify your memory use if you dirty all pages). It suggest adding
twice as much swap space as what we overcommit. It may be that we
should re-phrase it to something like
"Overcommitting %dMB of memory. This message will only be shown once."
or similar, though.
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 08:42:08 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA13930
for freebsd-current-outgoing; Tue, 10 Nov 1998 08:42: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 IAA13321;
Tue, 10 Nov 1998 08:40:55 -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 LAA06629;
Tue, 10 Nov 1998 11:39:48 -0500 (EST)
Date: Tue, 10 Nov 1998 11:39:48 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Sheldon Hearn <axl@iafrica.com>
cc: Dmitry Valdov <dv@dv.ru>, Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-Reply-To: <11258.910689277@axl.training.iafrica.com>
Message-ID: <Pine.BSF.4.05.9811101138460.6411-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 Tue, 10 Nov 1998, Sheldon Hearn wrote:
>
>
> On Tue, 10 Nov 1998 11:52:33 +0300, Dmitry Valdov wrote:
>
> > Thanks, will be know. But why not to fix it in ppp? :)
>
> Hi Dmitry,
>
> Even if ppp does the route cleanup for you, a signal 9 (KILL) doesn't
Duh.
> allow it to attempt graceful exit. This means that building cleanup code
> into ppp would not "fix it in ppp", since the code would never be
> reached once a SIGKILL is received.
>
> Assuming you _want_ to send ppp a SIGKILL instead of SIGTERM, your best
> bet is to run ppp from a shell wrapper script and put the route cleanup
> in the script, after the line that runs ppp.
>
> It would be nicer, though, if you could send ppp a SIGTERM instead. I
> remember that this wasn't always feasible last year when I used to use
> ppp (sometimes SIGTERM would have no apparent effect), but it's worth
I've noticed this too, sometimes having to SIGKILL ppp because SIGTERM
didn't seem to do much of anything.
> checking to see whether the software doesn't respond to this signal if
> you haven't checked already.
>
> Hope this helps,
> Sheldon.
>
Brian Feldman
> 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 Nov 10 09:07:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA17939
for freebsd-current-outgoing; Tue, 10 Nov 1998 09:07:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17899;
Tue, 10 Nov 1998 09:06:46 -0800 (PST)
(envelope-from drosih@rpi.edu)
Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47])
by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id MAA64714;
Tue, 10 Nov 1998 12:07:16 -0500
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: drosih@pop1.rpi.edu
Message-Id: <v04011700b26e1fccb9c1@[128.113.24.47]>
In-Reply-To:
<Pine.BSF.4.05.9811101055580.8312-100000@fallout.campusview.indiana.edu>
References: <3636.910712627@gjp.erols.com>
Date: Tue, 10 Nov 1998 12:06:25 -0500
To: John Fieber <jfieber@indiana.edu>, Gary Palmer <gpalmer@FreeBSD.ORG>
From: Garance A Drosihn <drosih@rpi.edu>
Subject: Re: The infamous dying daemons bug
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
At 11:07 AM -0500 11/10/98, John Fieber wrote:
>On Tue, 10 Nov 1998, Gary Palmer wrote:
>
>> John Dyson added this warning a few months ago, and the times that
>> I've seen it are when the machine *just* starts hitting swap space,
>> and is no-where near running out. No offense to John, but I don't
>> think that whatever algorythm he uses in generating that message
>> is anywhere near to being right, and I wonder what peoples opinions
>> about either hiding it behind bootverbose or removing it are?
>
> Even if the algorithm were right, the meaning of the message is
> clear as mud. So it tells me 125MB. Okay. Um... 125MB? What
> the heck am I supposed to do with that? Where did the number
> come from? What does it mean?
>
> The message isn't useful unless it can be understood. Judging
> from other people's comments, I'm not alone in being confused
> by it.
Presumably the message is there to give advance warning about the
usage of swap. A message that says "Hey, you're out of swap" just
seconds before the machine completely dies is not quite as useful
as one that tries to give you more advance notice (such that you
could think about adding more swap space next weekend).
I like that idea, even if this particular implementation and the
wording of the warning message could be improved upon...
(on a mainframe OS I used to work on, the operating system would
sometimes come out with "It's time to add another volume, methinks",
which was enough to get people's attention without sounding like
an emergency situation)
---
Garance Alistair Drosehn = gad@eclipse.its.rpi.edu
Senior Systems Programmer or drosih@rpi.edu
Rensselaer Polytechnic Institute
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 09:14:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA19117
for freebsd-current-outgoing; Tue, 10 Nov 1998 09:14:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19049
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 09:14:06 -0800 (PST)
(envelope-from drosih@rpi.edu)
Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47])
by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id MAA125308;
Tue, 10 Nov 1998 12:14:09 -0500
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: drosih@pop1.rpi.edu
Message-Id: <v04011701b26e23588f01@[128.113.24.47]>
In-Reply-To: <199811101002.CAA01721@dingo.cdrom.com>
Date: Tue, 10 Nov 1998 12:13:18 -0500
To: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
From: Garance A Drosihn <drosih@rpi.edu>
Subject: Re: Simple NFS ACCESS caching, call for testers
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
At 2:02 AM -0800 11/10/98, Mike Smith wrote:
> The attached patch adds a trivial cache for NFS ACCESS operations,
> which may provide a moderate to substantial performance improvement
> in some cases.
>
> If you have an NFS v3 server that you beat heavily on, I'd love to
> know whether these changes make any difference to you.
Are these meant for the server-side, or for the client side?
Ie, would you want to see a test of someone installing this on a
FreeBSD-based NFS server (which may in fact be serving files to
machines running other OS's), or on FreeBSD clients? (or only if
freebsd is the OS on both sides?)
---
Garance Alistair Drosehn = gad@eclipse.its.rpi.edu
Senior Systems Programmer or drosih@rpi.edu
Rensselaer Polytechnic Institute
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 09:14:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA19151
for freebsd-current-outgoing; Tue, 10 Nov 1998 09:14:40 -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 JAA19138
for <current@freebsd.org>; Tue, 10 Nov 1998 09:14:32 -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 MAA21297;
Tue, 10 Nov 1998 12:14:07 -0500 (EST)
(envelope-from wollman)
Date: Tue, 10 Nov 1998 12:14:07 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199811101714.MAA21297@khavrinen.lcs.mit.edu>
To: current@FreeBSD.ORG
Subject: [wollman: Who will be attending LISA?]
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I tried to send this to FreeBSD-announce, but apparently it didn't
meet with the moderator's approval.
------- start of forwarded message (RFC 934 encapsulation) -------
To: announce@freebsd.org
Subject: Who will be attending LISA?
I'd like to arrange some sort of social get-together for FreeBSDers
who will be at LISA in Boston this December. Please reply to me
privately if you are interested, and noting when you will be
available, and what you might be interested in doing or talking about.
I can easily enough give tours of Tech Square, and if there's
sufficient interest I might be able to arrange oter activities.
- -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
------- end -------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 09:18:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA19926
for freebsd-current-outgoing; Tue, 10 Nov 1998 09:18:18 -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 JAA19921
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 09:18:16 -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 KAA15873;
Tue, 10 Nov 1998 10:11:08 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id KAA11800; Tue, 10 Nov 1998 10:11:07 -0700
Date: Tue, 10 Nov 1998 10:11:07 -0700
Message-Id: <199811101711.KAA11800@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: Bruce Evans <bde@zeta.org.au>
Cc: archie@whistle.com, phk@critter.freebsd.dk, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <199811100634.RAA13398@godzilla.zeta.org.au>
References: <199811100634.RAA13398@godzilla.zeta.org.au>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> >A static inetd sounds like a good experiment.
>
> I couldn't duplicate the dying daemons problem despite trying fairly
> hard, and thought that this might be because I link everything in the
> world static.
I thought you linked everything shared. What made you change your mind?
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 09:46:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA22920
for freebsd-current-outgoing; Tue, 10 Nov 1998 09:46:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22913
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 09:46:45 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id MAA00698;
Tue, 10 Nov 1998 12:48:56 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Tue, 10 Nov 1998 12:48:55 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Mike Smith <mike@smith.net.au>
cc: current@FreeBSD.ORG
Subject: Re: Simple NFS ACCESS caching, call for testers
In-Reply-To: <199811101002.CAA01721@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811101214590.370-100000@porkfriedrice.ny.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
vfs.nfs.async: 1
vfs.nfs.gatherdelay: 10000
vfs.nfs.gatherdelay_v3: 10000
vfs.nfs.defect: 0
vfs.nfs.diskless_valid: 0
vfs.nfs.diskless_rootpath:
vfs.nfs.diskless_swappath:
vfs.nfs.access_cache_timeout: 6
vfs.nfs.access_cache_hits: 225001
vfs.nfs.access_cache_fills: 10981
nfsserver:/xxx /xxx nfs rw,tcp,bg,nfsv3,-r32768,-w32768,intr 0 0
Those are the mount options, I didn't notice a substantial increase in
performance. However FreeBSD was about 30-50% faster untarring files from
NFS->NFS*. When doing parallel "ls -lR" on a large+deep NFS tree linux
beat freebsd by about 1 second.
(*) I suspect it would have been faster had I not been running x11amp
(idle), for some reason it really kills NFS access.
I'm trying to figure out some sorta test that would stress the cache but
couldn't think of anything besides the two I just ran.
Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com
-- There are operating systems, and then there's FreeBSD.
-- http://www.freebsd.org/ 3.0-current
On Tue, 10 Nov 1998, Mike Smith wrote:
>
> The attached patch adds a trivial cache for NFS ACCESS operations,
> which may provide a moderate to substantial performance improvement in
> some cases.
>
> The issues surrounding caching these requests are actually quite
> subtle, and it's not immediately clear that a more sophisticated
> approach would actually yield great results in many more cases than
> this trivial one does. The trivial implementation has the advantage of
> simplicity. 8)
>
> If you have an NFS v3 server that you beat heavily on, I'd love to know
> whether these changes make any difference to you.
>
> Apply the patches to a -current kernel (they should apply fairly
> cleanly to a -stable kernel as well, but I haven't tried this).
>
> The new kernel has three new sysctl options:
>
> vfs.nfs.access_cache_timeout
>
> The time (in seconds) for which an ACCESS result is cached.
> Try values from 2 to 10 or so. A value of 0 (the default)
> disables caching.
>
> vfs.nfs.access_cache_hits
>
> The number of access calls that have been satisfied from
> cached entries rather than wire calls.
>
> vfs.nfs.access_cache_fills
>
> The number of access calls that have had to go to the wire
> to be satisfied.
>
> Trivial testing tends to indicate that operations involving a single
> UID and a large directory hierarchy may benefit substantially from
> this, but I really need more results before I can commit.
>
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 09:51:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA23285
for freebsd-current-outgoing; Tue, 10 Nov 1998 09:51:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles244.castles.com [208.214.165.244])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23280
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 09:51:25 -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 JAA03856;
Tue, 10 Nov 1998 09:50:20 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811101750.JAA03856@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Garance A Drosihn <drosih@rpi.edu>
cc: current@FreeBSD.ORG
Subject: Re: Simple NFS ACCESS caching, call for testers
In-reply-to: Your message of "Tue, 10 Nov 1998 12:13:18 EST."
<v04011701b26e23588f01@[128.113.24.47]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Nov 1998 09:50:19 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> At 2:02 AM -0800 11/10/98, Mike Smith wrote:
> > The attached patch adds a trivial cache for NFS ACCESS operations,
> > which may provide a moderate to substantial performance improvement
> > in some cases.
> >
> > If you have an NFS v3 server that you beat heavily on, I'd love to
> > know whether these changes make any difference to you.
>
> Are these meant for the server-side, or for the client side?
The patches are for clients only.
> Ie, would you want to see a test of someone installing this on a
> FreeBSD-based NFS server (which may in fact be serving files to
> machines running other OS's), or on FreeBSD clients? (or only if
> freebsd is the OS on both sides?)
The server is irrelevant, as long as it supports NFS v3.
--
\\ 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 Nov 10 09:53:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA23419
for freebsd-current-outgoing; Tue, 10 Nov 1998 09:53:41 -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 JAA23402
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 09:53:35 -0800 (PST)
(envelope-from gjp@gjp.erols.com)
Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1])
by gjp.erols.com (8.9.1/8.8.7) with ESMTP id MAA04130;
Tue, 10 Nov 1998 12:53:02 -0500 (EST)
(envelope-from gjp@gjp.erols.com)
To: Garance A Drosihn <drosih@rpi.edu>
cc: John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
From: "Gary Palmer" <gpalmer@FreeBSD.ORG>
Subject: Re: The infamous dying daemons bug
In-reply-to: Your message of "Tue, 10 Nov 1998 12:06:25 EST."
<v04011700b26e1fccb9c1@[128.113.24.47]>
Date: Tue, 10 Nov 1998 12:53:02 -0500
Message-ID: <4126.910720382@gjp.erols.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Garance A Drosihn wrote in message ID
<v04011700b26e1fccb9c1@[128.113.24.47]>:
> Presumably the message is there to give advance warning about the
> usage of swap. A message that says "Hey, you're out of swap" just
> seconds before the machine completely dies is not quite as useful
> as one that tries to give you more advance notice (such that you
> could think about adding more swap space next weekend).
Then I'd prefer to see a user-tunable setting which prints out a
kernel error when you reach a certain percentage of swap space
used. IMHO, in a server environment, that makes much more sense as you
want to keep everything possible in RAM, and using swap (any swap) is
a last resort. Thats certainly how I try to tune my servers.
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 Tue Nov 10 10:15:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA25653
for freebsd-current-outgoing; Tue, 10 Nov 1998 10:15:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles244.castles.com [208.214.165.244])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25648
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 10:15:02 -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 KAA03982;
Tue, 10 Nov 1998 10:14:03 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811101814.KAA03982@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Alfred Perlstein <bright@hotjobs.com>
cc: current@FreeBSD.ORG
Subject: Re: Simple NFS ACCESS caching, call for testers
In-reply-to: Your message of "Tue, 10 Nov 1998 12:48:55 EST."
<Pine.BSF.4.05.9811101214590.370-100000@porkfriedrice.ny.genx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Nov 1998 10:14:02 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> vfs.nfs.access_cache_timeout: 6
> vfs.nfs.access_cache_hits: 225001
> vfs.nfs.access_cache_fills: 10981
About a 95% hit rate, or a saving of about 450,000 packets on the
network. Your tests are a close-to-ideal case in that there's only one
user so the cache entry in the vnode won't get thrashed, but even so this
is much better than I'd expected.
> I'm trying to figure out some sorta test that would stress the cache but
> couldn't think of anything besides the two I just ran.
The "worst case" scenario for this scheme is multiple users (literally,
multiple different sets of credentials) accessing the same set of files
at once. Because the ACCESS status is a 3-tuple of path, credentials
and rights, caching them "properly" is very expensive. The current
approach is very cheap, but I expect it will degrade substantially
under this sort of load. It also doesn't preserve state across
multiple disconnected accesses to the same file (unless nfsnodes are
cached and reused, I'm not sure about this).
Still, as I said it's cheap, and it seems to offer some significant
improvements. It can probably also be retrofitted to 2.2, which will
make some of our heavy NFS customers happy.
--
\\ 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 Nov 10 10:17:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA25854
for freebsd-current-outgoing; Tue, 10 Nov 1998 10:17:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from halsey.arkenstone.org ([209.213.203.135])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25844
for <current@freebsd.org>; Tue, 10 Nov 1998 10:17:21 -0800 (PST)
(envelope-from jfayre@mindspring.com)
Received: from localhost by arkenstone.org
via sendmail with esmtp
id <m0zdBqA-000Lg0C@halsey.arkenstone.org> (Debian Smail3.2.0.101)
for <current@freebsd.org>; Tue, 10 Nov 1998 03:20:06 -0800 (PST)
Date: Tue, 10 Nov 1998 03:20:05 -0800 (PST)
From: Jason Fayre <jfayre@mindspring.com>
X-Sender: jfayre@halsey.arkenstone.org
To: current@FreeBSD.ORG
Subject: isntallation help!!!!
Message-ID: <Pine.LNX.4.05.9811100314130.3786-100000@halsey.arkenstone.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 situation is driving me crazy.
I have tried to install FreeBSD on my system several times. I have tried
with 2.2.6 and with 3.0.
Problem:
Install completes successfully. When I try to boot the system for the
first time, the kernel starts and goes through the device checks.
Then I get the message:
kernel panic: unable to mount root (2)
The lines just preceding this error are:
changing root to wd0s1a
changing root to wd0a
I may not have this info exactly correct as I am now at work and the
system is at home. I have tried install disks from 2.2.6, 3.0.release and
the latest 3.0 snap.
Here is my configuration:
Pentium 166
48MB of ram
Ne2000 network card at 300H, irq 11
2.5gb ide segate hard drive.
I have tried using the entire drive for freebsd in case it might be a
drive geometry problem, but no change.
Help!!!!!
Jason Fayre
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 10:24:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA26835
for freebsd-current-outgoing; Tue, 10 Nov 1998 10:24:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA26830
for <current@freebsd.org>; Tue, 10 Nov 1998 10:24:46 -0800 (PST)
(envelope-from tom@uniserve.com)
Received: from shell.uniserve.ca [204.244.186.218]
by pop.uniserve.com with smtp (Exim 1.82 #4)
id 0zdISQ-0002P9-00; Tue, 10 Nov 1998 10:24:02 -0800
Date: Tue, 10 Nov 1998 10:24:00 -0800 (PST)
From: Tom <tom@uniserve.com>
X-Sender: tom@shell.uniserve.ca
To: The Hermit Hacker <scrappy@hub.org>
cc: Mike Smith <mike@smith.net.au>, Paul Saab <paul@mu.org>,
current@FreeBSD.ORG
Subject: Re: 18gig drive's supported?
In-Reply-To: <Pine.BSF.4.05.9811100919330.15423-100000@thelab.hub.org>
Message-ID: <Pine.BSF.4.02A.9811101021260.7226-100000@shell.uniserve.ca>
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, 10 Nov 1998, The Hermit Hacker wrote:
> Surprisingly, I did...when I upgraded the system to its currently
> level...:( Now I've got sysinstall upgraded and installed, but when I go
> to 'label' or 'fdisk', it auto-presents me with da0, but doesn't give me
> the old choices of working with any of the other drives...did I miss a new
> command line switch her or something like that? Have read man pages, have
> built a new libdisk.a *just in case*...
Give up and use fdisk, disklabel, and newfs directly. I think it was a
mistake to re-invent the whell and re-develop all these functions and call
it sysinstall. sysinstall has problems with large DPT disks too, but
disklable and newfs work fine directly.
> Marc G. Fournier
> Systems Administrator @ hub.org
> primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
Tom
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 11:35:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA04452
for freebsd-current-outgoing; Tue, 10 Nov 1998 11:35:34 -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 LAA04443;
Tue, 10 Nov 1998 11:35:24 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id LAA03881;
Tue, 10 Nov 1998 11:36:13 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
To: current@FreeBSD.ORG
cc: peter@FreeBSD.ORG
Subject: Is it soup yet? :-)
Date: Tue, 10 Nov 1998 11:36:11 -0800
Message-ID: <3864.910726571@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 just wondering when we're going to switch the kernel to ELF and
put /usr/src/sys/modules into the build path. I'd really like the
/usr/bin/linux command to start doing the right thing on current 3.0
SNAPshots, among other things. :-)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 11:52:17 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA06258
for freebsd-current-outgoing; Tue, 10 Nov 1998 11:52:17 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from marathon.tekla.fi (marathon.tekla.fi [192.98.7.5])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06250
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 11:52:15 -0800 (PST)
(envelope-from sja@tekla.fi)
Received: from poveri.tekla.fi (poveri.tekla.fi [192.98.7.19])
by marathon.tekla.fi (8.8.7/8.8.7) with SMTP id VAA16464
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 21:51:56 +0200
From: Sakari Jalovaara <sja@tekla.fi>
Received: by poveri.tekla.fi; (5.65v3.2/1.1.8.2/20Aug96-0557PM)
id AA10677; Tue, 10 Nov 1998 21:52:08 +0200
Date: Tue, 10 Nov 1998 21:52:08 +0200
Message-Id: <9811101952.AA10677@poveri.tekla.fi>
To: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Could someone who can reproduce the dying daemons problem try a little
experiment: kill syslogd and then induce the out-of-memory condition.
Do other daemons still start dying?
++sja
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 11:54:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA06582
for freebsd-current-outgoing; Tue, 10 Nov 1998 11:54:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from morgan.angis.su.OZ.AU (morgan.angis.su.OZ.AU [129.78.25.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06571
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 11:54:11 -0800 (PST)
(envelope-from tonym@angis.usyd.edu.au)
Received: (from tonym@localhost) by morgan.angis.su.OZ.AU (8.8.7/8.6.6) id GAA10195; Wed, 11 Nov 1998 06:53:32 +1100 (EST)
Date: Wed, 11 Nov 1998 06:53:32 +1100 (EST)
From: Tony Maher <tonym@angis.usyd.edu.au>
Message-Id: <199811101953.GAA10195@morgan.angis.su.OZ.AU>
To: andreas@klemm.gtn.com, current@FreeBSD.ORG, tonym@angis.usyd.edu.au
Subject: Re: Travan TR4 dump/restore
Cc: mjacob@feral-gw
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello Andreas,
>> Dumps run without any errors, but trying to restore get
>> "resync restore, skipped 33 blocks"
>
> What if you use 32 blocks ?
>
> dump 0uabf 32 /dev/nrsa0 /
> ....
Just tried with 2 small partitions. Worked perfectly.
I'll test more tonight when I get back from work.
mt status
Mode Density Blocksize bpi Compression
Current: 0x45 512 bytes 0 unsupported
---------available modes---------
0: 0x45 512 bytes 0 unsupported
1: 0x45 512 bytes 0 unsupported
2: 0x45 512 bytes 0 unsupported
3: 0x45 512 bytes 0 unsupported
Many thanks!
tonym :-)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 12:46:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA12458
for freebsd-current-outgoing; Tue, 10 Nov 1998 12:46:28 -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 MAA12424;
Tue, 10 Nov 1998 12:46:14 -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 MAA00415;
Tue, 10 Nov 1998 12:44:48 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811102044.MAA00415@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: current@FreeBSD.ORG, peter@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Tue, 10 Nov 1998 11:36:11 PST."
<3864.910726571@zippy.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Nov 1998 12:44:48 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I'm just wondering when we're going to switch the kernel to ELF and
> put /usr/src/sys/modules into the build path. I'd really like the
> /usr/bin/linux command to start doing the right thing on current 3.0
> SNAPshots, among other things. :-)
I think we're about ready to do it. We probably want to insist that
people cut over to the new bootstrap first, perhaps with a HEADS UP
announcement from someone that hasn't cried wolf before.
--
\\ 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 Nov 10 12:48:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA12770
for freebsd-current-outgoing; Tue, 10 Nov 1998 12:48:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from limbo.rtfm.net (limbo.rtfm.net [207.198.222.47])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12763
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 12:48:30 -0800 (PST)
(envelope-from nathan@limbo.rtfm.net)
Received: (from nathan@localhost)
by limbo.rtfm.net (8.9.1/8.9.1) id PAA00988;
Tue, 10 Nov 1998 15:43:29 -0500 (EST)
(envelope-from nathan)
Message-ID: <19981110154329.F892@rtfm.net>
Date: Tue, 10 Nov 1998 15:43:29 -0500
From: Nathan Dorfman <nathan@rtfm.net>
To: Bruce Evans <bde@zeta.org.au>, sthaug@nethelp.no
Cc: current@FreeBSD.ORG
Subject: Re: O_SYNC
References: <199811100435.PAA03024@godzilla.zeta.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199811100435.PAA03024@godzilla.zeta.org.au>; from Bruce Evans on Tue, Nov 10, 1998 at 03:35:16PM +1100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, Nov 10, 1998 at 03:35:16PM +1100, Bruce Evans wrote:
> O_SYNC is apparently a non-BSD thing.
>
> POSIX.1b has optional features O_SYNC, O_DSYNC and O_RSYNC. O_SYNC syncs
> everything related to writes; O_DSYNC syncs written data; O_RSYNC syncs
> everything related to reads (mainly inode access times).
It isn't in 4.4BSD-Encumbered.
> Bruce
--
________________ ___________________________________________
/ Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing*
/ nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing
/ finger for PGP key \ religion to the pope?" -Jamie Bowden
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 12:49:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA12879
for freebsd-current-outgoing; Tue, 10 Nov 1998 12:49:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from freebsd.myers.lan (toscana-209-79-56-101.snfc21.pacbell.net [209.79.56.101])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12871
for <freebsd-current@freebsd.org>; Tue, 10 Nov 1998 12:49:43 -0800 (PST)
(envelope-from myers@iname.com)
From: myers@iname.com
Received: from iname.com (localhost [127.0.0.1])
by freebsd.myers.lan (8.9.1/8.9.1) with ESMTP id MAA27174;
Tue, 10 Nov 1998 12:46:42 GMT
(envelope-from myers@iname.com)
Message-Id: <199811101246.MAA27174@freebsd.myers.lan>
Date: Tue, 10 Nov 1998 12:46:40 +0000 (GMT)
Subject: Re: Simple NFS ACCESS caching, call for testers
To: mike@smith.net.au
cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <199811101730.JAA03751@dingo.cdrom.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Anything and everything is worthwhile. Please let me know the
> vfs.nfa.access_cache statistics you see from your tests.
Using a Solaris 2.6 server and running 'make tags' from
NFS-mounted /usr/src:
vfs.nfs.async: 0
vfs.nfs.access_cache_hits: 305092
vfs.nfs.access_cache_fills: 10489
That's a patch I believe I'll keep...
-David.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 13:23:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA17268
for freebsd-current-outgoing; Tue, 10 Nov 1998 13:23:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.gtn.com (mail.gtn.com [192.109.159.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17253
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 13:23:43 -0800 (PST)
(envelope-from andreas@klemm.gtn.com)
Received: (from uucp@localhost)
by mail.gtn.com (8.8.6/8.8.6) with UUCP id WAA20690;
Tue, 10 Nov 1998 22:15:09 +0100 (MET)
Received: (from andreas@localhost)
by klemm.gtn.com (8.9.1/8.9.1) id VAA13189;
Tue, 10 Nov 1998 21:38:18 +0100 (CET)
(envelope-from andreas)
Message-ID: <19981110213817.A13182@klemm.gtn.com>
Date: Tue, 10 Nov 1998 21:38:17 +0100
From: Andreas Klemm <andreas@klemm.gtn.com>
To: Tony Maher <tonym@angis.usyd.edu.au>, current@FreeBSD.ORG
Cc: mjacob@feral-gw
Subject: Re: Travan TR4 dump/restore
References: <199811101953.GAA10195@morgan.angis.su.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199811101953.GAA10195@morgan.angis.su.OZ.AU>; from Tony Maher on Wed, Nov 11, 1998 at 06:53:32AM +1100
X-Disclaimer: A free society is one where it is safe to be unpopular
X-Operating-System: FreeBSD 3.0-CURRENT SMP
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Nov 11, 1998 at 06:53:32AM +1100, Tony Maher wrote:
> Hello Andreas,
>
> >> Dumps run without any errors, but trying to restore get
> >> "resync restore, skipped 33 blocks"
> >
> > What if you use 32 blocks ?
> >
> > dump 0uabf 32 /dev/nrsa0 /
> > ....
>
> Just tried with 2 small partitions. Worked perfectly.
> I'll test more tonight when I get back from work.
>
>
> mt status
> Mode Density Blocksize bpi Compression
> Current: 0x45 512 bytes 0 unsupported
> ---------available modes---------
> 0: 0x45 512 bytes 0 unsupported
> 1: 0x45 512 bytes 0 unsupported
> 2: 0x45 512 bytes 0 unsupported
> 3: 0x45 512 bytes 0 unsupported
>
> Many thanks!
Hmmm,
my personal experience was, that it's now safe with CAM to use
blocksizes over 32 .... Since physio (if I remember right) was
done in 32 blocks chunks even is you choose 64 or more ...
--
Andreas Klemm http://www.FreeBSD.ORG/~andreas
What gives you 90% more speed, for example, in kernel compilation ?
http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html
"NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP''
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 13:26:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA17781
for freebsd-current-outgoing; Tue, 10 Nov 1998 13:26:23 -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 NAA17708;
Tue, 10 Nov 1998 13:26:08 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id VAA08058;
Tue, 10 Nov 1998 21:25:35 GMT
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1])
by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id VAA16076;
Tue, 10 Nov 1998 21:27:01 GMT
(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199811102127.VAA16076@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jeroen C. van Gelderen" <gelderen@mediaport.org>
cc: "Sheldon Hearn" <axl@iafrica.com>, "Dmitry Valdov" <dv@dv.ru>,
"Kris Kennaway" <kkennawa@physics.adelaide.edu.au>,
"Brian Somers" <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-reply-to: Your message of "Tue, 10 Nov 1998 10:47:14 +0100."
<008d01be0c8f$188b6dc0$1400000a@deskfix.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Nov 1998 21:27:01 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> From: Sheldon Hearn <axl@iafrica.com>
> >Even if ppp does the route cleanup for you, a signal 9 (KILL) doesn't
> >allow it to attempt graceful exit. This means that building cleanup code
> >into ppp would not "fix it in ppp", since the code would never be
> >reached once a SIGKILL is received.
>
> Just a humble thought: route removal can be seen as cleanup, but it can also
> be seen as preparation. Maybe you can do it at ppp startup. Or -if that's
> not possible- you may be able to detect the condition as handle it
> gracefully...
It cleans the interface it wants to use. This should be enough.
It's always possible to put a ``delete! default'' in ppp.conf just in
case that's been left around.
> Cheers,
> Jeroen
> (who does not run ppp)
--
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 Nov 10 13:29:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA18093
for freebsd-current-outgoing; Tue, 10 Nov 1998 13:29:23 -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 NAA18066;
Tue, 10 Nov 1998 13:29:08 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id VAA08595;
Tue, 10 Nov 1998 21:28:49 GMT
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1])
by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id VAA16348;
Tue, 10 Nov 1998 21:30:16 GMT
(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199811102130.VAA16348@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Dmitry Valdov <dv@dv.ru>
cc: Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-reply-to: Your message of "Tue, 10 Nov 1998 11:52:33 +0300."
<Pine.BSF.3.95q.981110114942.1147C-100000@xkis.kis.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Nov 1998 21:30:15 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
>
> On Tue, 10 Nov 1998, Kris Kennaway wrote:
>
> > Date: Tue, 10 Nov 1998 19:17:47 +1030 (CST)
> > From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
> > To: Dmitry Valdov <dv@dv.ru>
> > Cc: Brian Somers <brian@freebsd.org>, current@freebsd.org
> > Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
> >
> > On Tue, 10 Nov 1998, Dmitry Valdov wrote:
> >
> > > There is a problem in ppp - when you kill it with -9, You'll not be able to
> > > start it again until you reboot.
> > > Sometimes I need to kill it with -9 because when killing with SIGHUP it
> > > tries to properly shutdown PPP session via LCP, but there is some cases when
> > > it inpossible.
> >
> > Doing a 'route delete default' seems to fix this for me (otherwise it just
> > hangs when I try and restart it).
> >
>
> Thanks, will be know. But why not to fix it in ppp? :)
What do you suggest is changed ? Ppp can't delete the default route
on it's own - it doesn't necessarily belong to ppp.
> Also there is one more bug - sometimes ppp don't detect carrier lost and
> stays in open state for a long time. :(
Get the latest version from http://www.Awfulhak.org/ppp.html and
enable debug logging. You'll see ppps idea of carrier. I suspect
that either your modem is faking carrier all the time or that you're
running a very old version (2.2.5?).
> Dmitry.
--
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 Nov 10 13:31:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA18568
for freebsd-current-outgoing; Tue, 10 Nov 1998 13:31:26 -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 NAA18409;
Tue, 10 Nov 1998 13:30:46 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id VAA07867;
Tue, 10 Nov 1998 21:24:19 GMT
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1])
by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id VAA15982;
Tue, 10 Nov 1998 21:25:45 GMT
(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199811102125.VAA15982@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Dmitry Valdov <dv@dv.ru>
cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-reply-to: Your message of "Tue, 10 Nov 1998 11:17:55 +0300."
<Pine.BSF.3.95q.981110111417.27884F-100000@xkis.kis.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Nov 1998 21:25:45 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Hi!
>
> There is a problem in ppp - when you kill it with -9, You'll not be able to
> start it again until you reboot.
Have you tried this with the latest ppp ? It cleans out the
interface before it starts - this should result in the routing table
being adjusted.
Having said that, killing anything with -9 is usually bad news.
> Sometimes I need to kill it with -9 because when killing with SIGHUP it
> tries to properly shutdown PPP session via LCP, but there is some cases when
> it inpossible.
So use signal 2 or connect to the diagnostic socket and do a ``down''.
[.....]
--
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 Nov 10 13:32:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA18660
for freebsd-current-outgoing; Tue, 10 Nov 1998 13:32:00 -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 NAA18621;
Tue, 10 Nov 1998 13:31:46 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id VAA08890;
Tue, 10 Nov 1998 21:31:26 GMT
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1])
by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id VAA17404;
Tue, 10 Nov 1998 21:32:53 GMT
(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199811102132.VAA17404@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
cc: Dmitry Valdov <dv@dv.ru>, Brian Somers <brian@FreeBSD.ORG>,
current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-reply-to: Your message of "Tue, 10 Nov 1998 19:35:10 +1030."
<Pine.OSF.4.05.9811101930000.10597-100000@spectrum.physics.adelaide.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Nov 1998 21:32:53 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On Tue, 10 Nov 1998, Dmitry Valdov wrote:
>
> > Also there is one more bug - sometimes ppp don't detect carrier lost and
> > stays in open state for a long time. :(
>
> Sorry for the "implicit bug report", Brian, but I've been meaning to track
> this down for a long time and make sure it's not user error. I often see this
> as well - it's noticeable for me because I have ipfw installed and when the
> modem drops carrier I see packets being 'reflected' by the modem's local echo
> (I assume), and bouncing off the ipfw 'incoming address of myself' filter.
Try ``set log +debug''. You should see the online/offline status of
the link at frequent intervals. If this doesn't agree with your
modem, then you modem may be misconfigured.
> Kris
--
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 Nov 10 13:32:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA18727
for freebsd-current-outgoing; Tue, 10 Nov 1998 13:32:31 -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 NAA18711
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 13:32:23 -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 NAA08947;
Tue, 10 Nov 1998 13:31:54 -0800 (PST)
(envelope-from dwhite@resnet.uoregon.edu)
Date: Tue, 10 Nov 1998 13:31:53 -0800 (PST)
From: Doug White <dwhite@resnet.uoregon.edu>
To: Jason Fayre <jfayre@mindspring.com>
cc: current@FreeBSD.ORG
Subject: Re: isntallation help!!!!
In-Reply-To: <Pine.LNX.4.05.9811100314130.3786-100000@halsey.arkenstone.org>
Message-ID: <Pine.BSF.4.03.9811101331060.2215-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 Tue, 10 Nov 1998, Jason Fayre wrote:
> Hello,
> This situation is driving me crazy.
> I have tried to install FreeBSD on my system several times. I have tried
> with 2.2.6 and with 3.0.
This belongs on -questions, not -current.
> Problem:
> Install completes successfully. When I try to boot the system for the
> first time, the kernel starts and goes through the device checks.
> Then I get the message:
> kernel panic: unable to mount root (2)
> The lines just preceding this error are:
> changing root to wd0s1a
> changing root to wd0a
See FAQ question 2.25.
http://www.freebsd.org/FAQ
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 Tue Nov 10 13:36:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA19229
for freebsd-current-outgoing; Tue, 10 Nov 1998 13:36:44 -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 NAA19206;
Tue, 10 Nov 1998 13:36:28 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.59.29]) by smtp04.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAACCA;
Tue, 10 Nov 1998 22:36:01 +0100
Message-ID: <XFMail.981110224016.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: <199811102044.MAA00415@dingo.cdrom.com>
Date: Tue, 10 Nov 1998 22:40:16 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Mike Smith <mike@smith.net.au>
Subject: Re: Is it soup yet? :-)
Cc: peter@FreeBSD.ORG, current@FreeBSD.ORG,
"Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 10-Nov-98 Mike Smith wrote:
>> I'm just wondering when we're going to switch the kernel to ELF and
>> put /usr/src/sys/modules into the build path. I'd really like the
>> /usr/bin/linux command to start doing the right thing on current 3.0
>> SNAPshots, among other things. :-)
>
> I think we're about ready to do it. We probably want to insist that
> people cut over to the new bootstrap first, perhaps with a HEADS UP
> announcement from someone that hasn't cried wolf before.
If I may ask of something... =)
Could someone please point a checklist of steps for a good migrating of aout to
ELF? This would make it easier for us as well as being used as a reference
point on the web in future for 2.2.x users to 3.0.x...
Thanks,
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl | Cum angelis et pueris,
Junior Network/Security Specialist | fideles inveniamur
*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 Tue Nov 10 13:59:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA22672
for freebsd-current-outgoing; Tue, 10 Nov 1998 13:59:30 -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 NAA22657;
Tue, 10 Nov 1998 13:59:19 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id VAA08912;
Tue, 10 Nov 1998 21:35:01 GMT
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1])
by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id VAA17445;
Tue, 10 Nov 1998 21:36:28 GMT
(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199811102136.VAA17445@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Dmitry Valdov <dv@dv.ru>
cc: Sheldon Hearn <axl@iafrica.com>,
Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-reply-to: Your message of "Tue, 10 Nov 1998 13:06:48 +0300."
<Pine.BSF.3.95q.981110130512.4032D-100000@xkis.kis.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Nov 1998 21:36:28 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
>
> On Tue, 10 Nov 1998, Sheldon Hearn wrote:
>
> > Date: Tue, 10 Nov 1998 11:14:37 +0200
> > From: Sheldon Hearn <axl@iafrica.com>
> > To: Dmitry Valdov <dv@dv.ru>
> > Cc: Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
> > Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
> > Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
> >
> >
> >
> > On Tue, 10 Nov 1998 11:52:33 +0300, Dmitry Valdov wrote:
> >
> > > Thanks, will be know. But why not to fix it in ppp? :)
> >
> > Hi Dmitry,
> >
> > Even if ppp does the route cleanup for you, a signal 9 (KILL) doesn't
> > allow it to attempt graceful exit. This means that building cleanup code
> > into ppp would not "fix it in ppp", since the code would never be
> > reached once a SIGKILL is received.
> >
>
> I know it. But why when I'm starting ppp next time it hangs? I think, it
> should not hang. It can delete route, print warning or error message and so
> on.
So put a ``delete! default'' in your config file.
> Dmitry.
--
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 Nov 10 14:02:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23216
for freebsd-current-outgoing; Tue, 10 Nov 1998 14:02:37 -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 OAA23165;
Tue, 10 Nov 1998 14:02:23 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id VAA08907;
Tue, 10 Nov 1998 21:34:03 GMT
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1])
by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id VAA17430;
Tue, 10 Nov 1998 21:35:30 GMT
(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199811102135.VAA17430@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Sheldon Hearn <axl@iafrica.com>
cc: Dmitry Valdov <dv@dv.ru>, Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-reply-to: Your message of "Tue, 10 Nov 1998 11:14:37 +0200."
<11258.910689277@axl.training.iafrica.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Nov 1998 21:35:29 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
>
> On Tue, 10 Nov 1998 11:52:33 +0300, Dmitry Valdov wrote:
>
> > Thanks, will be know. But why not to fix it in ppp? :)
>
> Hi Dmitry,
>
> Even if ppp does the route cleanup for you, a signal 9 (KILL) doesn't
> allow it to attempt graceful exit. This means that building cleanup code
> into ppp would not "fix it in ppp", since the code would never be
> reached once a SIGKILL is received.
>
> Assuming you _want_ to send ppp a SIGKILL instead of SIGTERM, your best
> bet is to run ppp from a shell wrapper script and put the route cleanup
> in the script, after the line that runs ppp.
>
> It would be nicer, though, if you could send ppp a SIGTERM instead. I
> remember that this wasn't always feasible last year when I used to use
> ppp (sometimes SIGTERM would have no apparent effect), but it's worth
> checking to see whether the software doesn't respond to this signal if
> you haven't checked already.
A SIGTERM followed by a SIGINT will now bring ppp down immediately
irrespective of the current mode. A ``pppctl .... down\; quit all''
will also bring it down in a hurry.
> Hope this helps,
> Sheldon.
--
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 Nov 10 14:02:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23265
for freebsd-current-outgoing; Tue, 10 Nov 1998 14:02:46 -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 OAA23211;
Tue, 10 Nov 1998 14:02:37 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id VAA09191;
Tue, 10 Nov 1998 21:39:27 GMT
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1])
by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id VAA17466;
Tue, 10 Nov 1998 21:40:54 GMT
(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199811102140.VAA17466@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Jason Fesler <jfesler@gigo.com>
cc: Kris Kennaway <kkennawa@physics.adelaide.edu.au>, Dmitry Valdov <dv@dv.ru>,
Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-reply-to: Your message of "Tue, 10 Nov 1998 06:37:39 PST."
<Pine.BSF.4.00.9811100634590.25966-100000@heaven.gigo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Nov 1998 21:40:53 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Sorry for the "implicit bug report", Brian, but I've been meaning to track
> > this down for a long time and make sure it's not user error. I often see this
>
> I've had this since the 2.2.2 days when I first started running ppp.
> After a while (hours, days, weeks - random) either carrier isn't noticed
> as being missing, or all outgoing packets don't cross the serial cable to
> to the other side. After a while I kinda gave up.
Ppp won't expect carrier if it's not detected when ppp starts doing
LCP. This allows null-modem cables without the correct wiring to
work.
As I've said to a couple of these posts - enable debug logging and
you'll see the carrier status reported every second. You can also
``show modem'' to see what things look like.
> I now every few minutes fping a few hosts on the nearby remote side. If
> they _all_ fail (a good 10 second timeout is given) then I kill -9 the ppp
> session, wait 2 seconds, then restart ppp. It's caught every strange
> random bug on either side soon enough that I no longer have to try and
> call home and walk the wife through ppp..
Ppp should be a lot more reliable these days.
--
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 Nov 10 14:07:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23792
for freebsd-current-outgoing; Tue, 10 Nov 1998 14:07:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from werple.mira.net (werple.mira.net [203.9.190.18])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA23780
for <freebsd-current@FreeBSD.ORG>; Tue, 10 Nov 1998 14:07:24 -0800 (PST)
(envelope-from gfm@mira.net)
Received: (qmail 27050 invoked from network); 10 Nov 1998 22:07:04 -0000
Received: from dp-m-r051.werple.net.au (203.17.46.51)
by mira.net with SMTP; 10 Nov 1998 22:07:04 -0000
From: gfm@mira.net (Graham Menhennitt)
To: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>,
freebsd-current@FreeBSD.ORG
Subject: Re: 3.0-CURRENT: Adaptec 1540 not detected (with workaround)
Date: Tue, 10 Nov 1998 22:09:37 GMT
Message-ID: <3648b287.87315503@mira.net>
References: <199811100058.RAA22604@narnia.plutotech.com>
In-Reply-To: <199811100058.RAA22604@narnia.plutotech.com>
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 OAA23785
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Ok, I did a bit more investigating. Firstly, I pulled the card out of the
machine. It's an AHA 1542B.
Then I added a printf to output the board id and the status value read from
the geometry register. The values were 0x41 and 0xFF respectively. Hang
on... with those values, the test should pass!!! I did a bit more fiddling
and found that putting in the printf makes it work! It must be a timing
problem. Sure enough, I added a delay loop before reading the geometry
register and it fixed it. I forgot to generate a patch file but it now
looks like:
if (aha->boardid <= 0x42) {
int dummy;
for(dummy = 0; dummy < 1000; dummy++)
;
status = aha_inb(aha, GEOMETRY_REG);
if (status != 0xff)
return (ENXIO);
}
I tried 100 for the loop count but it still failed.
I don't know if there is a more elegant way of doing this. But anyway, the
above seems to work 100% reliably.
Could somebody please commit this change.
Graham
On Mon, 9 Nov 1998 17:58:30 -0700 (MST), you wrote:
>In article <36484fb6.262608561@mira.net> you wrote:
>> Eventually I found the problem. In /usr/src/sys/dev/aha/aha.c there is some
>> code that attempts to distinguish between Adaptec and Buslogic adaptors.
>> This was failing. I'm not sure what model my adaptor is (I think it's an
>> 'A') but it is a genuine Adaptec. Hence the comment in the code about
>> cloned cards may apply to some genuine ones also.
>
>
>Can you print out the value of aha->boardid and send it to me? It
>would also be useful for you to look in your machine and determine
>exactly which version of this card you have.
>
>Thanks,
>Justin
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 14:07:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23810
for freebsd-current-outgoing; Tue, 10 Nov 1998 14:07:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from werple.mira.net (werple.mira.net [203.9.190.18])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA23786
for <freebsd-current@FreeBSD.ORG>; Tue, 10 Nov 1998 14:07:26 -0800 (PST)
(envelope-from gfm@mira.net)
Received: (qmail 27064 invoked from network); 10 Nov 1998 22:07:06 -0000
Received: from dp-m-r051.werple.net.au (203.17.46.51)
by mira.net with SMTP; 10 Nov 1998 22:07:06 -0000
From: gfm@mira.net (Graham Menhennitt)
To: freebsd-current@FreeBSD.ORG
Subject: Named bootfile format doco: help please
Date: Tue, 10 Nov 1998 22:09:40 GMT
Message-ID: <364ab500.87948363@mira.net>
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 OAA23804
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I've just installed 3.0-CURRENT onto my machine which was previously
running 2.2-STABLE. Everything seems to be working ok except for named. I
can't seem to work out what I need to put into the named.boot file. The
doco that comes with 3.0 seems to be for the older version. I also went to
the bind web site www.isc.org and found the same old doco.
Could somebody point me to the doco for version 8.1.2. Alternatively could
somebody give me an example of how to set up named for my configuration.
I have a small local network. The FreeBSD box runs the name server. It
should be a master for my local net. I have a dial-up connection to my ISP
from the FreeBSD box. I run ipfw and natd on the FreeBSD box to do IP
masqerading. When I am connected to the ISP, the local name server should
forward requests (for non-local addresses) to the ISP's.
I'm sure that this is a very common setup. If you have something similar
working under 3.0, could you please send me your namedb files.
Thanks for any help,
Graham
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 14:33:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA27553
for freebsd-current-outgoing; Tue, 10 Nov 1998 14:33:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.imc-to.com (mail.imc-to.com [209.82.43.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27548
for <freebsd-current@FreeBSD.ORG>; Tue, 10 Nov 1998 14:33:45 -0800 (PST)
(envelope-from tim@imc.ca)
Received: from valkyrie.imc-to.com (209.82.43.200) by mail.imc-to.com with SMTP
(Eudora Internet Mail Server 2.1); Tue, 10 Nov 1998 19:05:46 -0400
Message-ID: <3648BEB2.ABD322C@imc.ca>
Date: Tue, 10 Nov 1998 17:31:14 -0500
From: Tim Gibson <tim@imc.ca>
Organization: IMC Inc.
X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.0-RELEASE i386)
MIME-Version: 1.0
To: Graham Menhennitt <gfm@mira.net>
CC: freebsd-current@FreeBSD.ORG
Subject: Re: Named bootfile format doco: help please
References: <364ab500.87948363@mira.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I realize that this one should be dumped in the questions, but since
current is so recent
others will probably look here for the answer. To the install team,
could you add a note
on upgrades that the format has changed on the named boot file? There
are still alot of
sites that don't update often.
Graham Menhennitt wrote:
>
> I've just installed 3.0-CURRENT onto my machine which was previously
> running 2.2-STABLE. Everything seems to be working ok except for named. I
> can't seem to work out what I need to put into the named.boot file. The
> doco that comes with 3.0 seems to be for the older version. I also went to
> the bind web site www.isc.org and found the same old doco.
>
> Could somebody point me to the doco for version 8.1.2. Alternatively could
> somebody give me an example of how to set up named for my configuration.
>From the BIND page on ISC;
OUR GOODIES:
The latest release intended for vendors or
advanced users.
The latest kit intended for semipublic
testing.
what's this? >> BIND 8.1.2 Documentation.
A fairly recent BOG (BIND Operations Guide),
available in both
PostScript or Lineprinter formats. Thanks to
Graeme Cox there is also a
somewhat recent HTML version available.
We sign some of our software distributions
using PGP.
A discussion of BIND and load balancing.
John Gilmore made a Secure DNS information
and software download
site.
Click there, click on 8.1.2 Configuration File Guide.
You'll notice that Vix has completely rearranged the syntax. This is
what's
causing your BIND error message and the failure to start. Simply convert
over
to the new format and you'll be back in biz. There's an easily editable
exmample too.
Tim Gibson
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 14:58:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA00821
for freebsd-current-outgoing; Tue, 10 Nov 1998 14:58:48 -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 OAA00810
for <current@freebsd.org>; Tue, 10 Nov 1998 14:58:39 -0800 (PST)
(envelope-from kkennawa@physics.adelaide.edu.au)
Received: from mercury (mercury [129.127.36.44])
by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id JAA25825;
Wed, 11 Nov 1998 09:28:21 +1030 (CST)
Received: from localhost by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM)
id AA07986; Wed, 11 Nov 1998 09:28:20 +1030
Date: Wed, 11 Nov 1998 09:28:20 +1030 (CST)
From: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
To: Brian Somers <brian@awfulhak.org>
Cc: current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-Reply-To: <199811102132.VAA17404@woof.lan.awfulhak.org>
Message-Id: <Pine.OSF.4.05.9811110927330.8022-100000@mercury.physics.adelaide.edu.au>
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, 10 Nov 1998, Brian Somers wrote:
> Try ``set log +debug''. You should see the online/offline status of
> the link at frequent intervals. If this doesn't agree with your
> modem, then you modem may be misconfigured.
Thanks. I'll play around with this when I get the time and try and narrow down
what I'm seeing.
Kris
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 15:14:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA02936
for freebsd-current-outgoing; Tue, 10 Nov 1998 15:14:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02920
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 15:14:52 -0800 (PST)
(envelope-from regnauld@EU.org)
Received: from mail.prosa.dk ([192.168.100.254])
by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id AAA27064;
Wed, 11 Nov 1998 00:19:16 +0100 (CET)
(envelope-from regnauld@EU.org)
X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk
Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10])
by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id AAA15357;
Wed, 11 Nov 1998 00:39:42 +0100 (CET)
Received: (from uucp@localhost)
by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) with UUCP id AAA26453;
Wed, 11 Nov 1998 00:14:17 +0100 (CET)
Received: (from regnauld@localhost)
by stimpy.prosa.dk (8.9.1/8.9.1/stimpy-1.0) id TAA01463;
Tue, 10 Nov 1998 19:18:53 +0100 (CET)
(envelope-from regnauld)
Message-ID: <19981110191728.63304@stimpy.prosa.dk>
Date: Tue, 10 Nov 1998 19:17:28 +0100
From: Phil Regnauld <regnauld@EU.org>
To: Eivind Eklund <eivind@yes.no>
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <Pine.BSF.4.05.9811100914130.343-100000@porkfriedrice.ny.genx.net> <3636.910712627@gjp.erols.com> <19981110171205.19613@follo.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.88e
In-Reply-To: <19981110171205.19613@follo.net>; from Eivind Eklund on Tue, Nov 10, 1998 at 05:12:05PM +0100
X-Operating-System: FreeBSD 3.0-CURRENT i386
Phone: +45 3336 4148
Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark
Organization: PROSA
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Eivind Eklund writes:
> That message seems to be very right. It seems to come when we get
> into a 'memory overcommit' situation (ie, there isn't enough swap to
> satify your memory use if you dirty all pages).
On a freshly booted machine ? With no processes running other than
getty and inetd, with 128MB of RAM ? (and 256MB of swap).
Hmmm. The message doesn't always come, also. This is why I was a bit
surprised...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 16:11:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA10915
for freebsd-current-outgoing; Tue, 10 Nov 1998 16:11:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from picnic.mat.net (picnic.mat.net [206.246.122.117])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10847;
Tue, 10 Nov 1998 16:11:08 -0800 (PST)
(envelope-from chuckr@mat.net)
Received: from localhost (chuckr@localhost)
by picnic.mat.net (8.9.1/8.8.5) with ESMTP id TAA19796;
Tue, 10 Nov 1998 19:09:23 -0500 (EST)
Date: Tue, 10 Nov 1998 19:09:23 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Mike Smith <mike@smith.net.au>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@FreeBSD.ORG,
peter@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <199811102044.MAA00415@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811101903050.10145-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 Tue, 10 Nov 1998, Mike Smith wrote:
> > I'm just wondering when we're going to switch the kernel to ELF and
> > put /usr/src/sys/modules into the build path. I'd really like the
> > /usr/bin/linux command to start doing the right thing on current 3.0
> > SNAPshots, among other things. :-)
>
> I think we're about ready to do it. We probably want to insist that
> people cut over to the new bootstrap first, perhaps with a HEADS UP
> announcement from someone that hasn't cried wolf before.
??? Modules are *already* installed by buildworld. Peter did this,
what, a week ago? As far as the kernel goes, I found out during my own
conversion that the bootblocks from 2.2.6 will give you a non-booting
machine ... that's the bar you have to jump, in getting elf kernels
installed on everyone's machine, without major hassle from everyone who
comes late to the game.
I don't know enough about the bootblocks ... I just followed Mike's
steps in getting myself installed ok, but is it possible to write a
program that could probe the boot disk, read the bootblocks, and decide
if they need upgrading ... and if they do, printing a warning message,
and then refuse to install the new kernel?
If this could be done, you know this will save a *lot* of complaints
about insufficient warnings. You could warn until you're hoarse,
they'll *still* miss it, unless the build process itself screams at
them.
>
> --
> \\ 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
>
>
----------------------------+-----------------------------------------------
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 Tue Nov 10 16:19:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA11954
for freebsd-current-outgoing; Tue, 10 Nov 1998 16:19: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 QAA11922;
Tue, 10 Nov 1998 16:19:37 -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 KAA20201;
Wed, 11 Nov 1998 10:49:18 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.1/8.9.0) id KAA19952;
Wed, 11 Nov 1998 10:49:17 +1030 (CST)
Message-ID: <19981111104917.Q18183@freebie.lemis.com>
Date: Wed, 11 Nov 1998 10:49:17 +1030
From: Greg Lehey <grog@lemis.com>
To: Mike Smith <mike@smith.net.au>, "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: current@FreeBSD.ORG, peter@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
References: <3864.910726571@zippy.cdrom.com> <199811102044.MAA00415@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199811102044.MAA00415@dingo.cdrom.com>; from Mike Smith on Tue, Nov 10, 1998 at 12:44: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 Tuesday, 10 November 1998 at 12:44:48 -0800, Mike Smith wrote:
>> I'm just wondering when we're going to switch the kernel to ELF and
>> put /usr/src/sys/modules into the build path. I'd really like the
>> /usr/bin/linux command to start doing the right thing on current 3.0
>> SNAPshots, among other things. :-)
>
> I think we're about ready to do it. We probably want to insist that
> people cut over to the new bootstrap first, perhaps with a HEADS UP
> announcement from someone that hasn't cried wolf before.
I agree entirely. I've been watching the development in the bootstrap
area, and I'd like to have some pretty straightforward instructions
once the fuss is over and done with.
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 Tue Nov 10 16:21:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA12144
for freebsd-current-outgoing; Tue, 10 Nov 1998 16:21:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12128;
Tue, 10 Nov 1998 16:21:40 -0800 (PST)
(envelope-from dima@tejblum.dnttm.rssi.ru)
Received: (from uucp@localhost)
by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id CAA06970;
Wed, 11 Nov 1998 02:53:28 +0300
Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1])
by tejblum.dnttm.rssi.ru (8.9.1/8.9.1) with ESMTP id CAA02240;
Wed, 11 Nov 1998 02:52:35 +0300 (MSK)
(envelope-from dima@tejblum.dnttm.rssi.ru)
Message-Id: <199811102352.CAA02240@tejblum.dnttm.rssi.ru>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Eivind Eklund <eivind@yes.no>
cc: Gary Palmer <gpalmer@FreeBSD.ORG>, Alfred Perlstein <bright@hotjobs.com>,
Phil Regnauld <regnauld@EU.org>, alk@pobox.com, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-reply-to: Your message of "Tue, 10 Nov 1998 17:12:05 +0100."
<19981110171205.19613@follo.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 02:52:35 +0300
From: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Eivind Eklund wrote:
> > > /kernel: swap_pager: suggest more swap space: 254 MB
> >
> > John Dyson added this warning a few months ago, and the times that
> > I've seen it are when the machine *just* starts hitting swap space,
> > and is no-where near running out. No offense to John, but I don't
> > think that whatever algorythm he uses in generating that message is
> > anywhere near to being right, and I wonder what peoples opinions about
> > either hiding it behind bootverbose or removing it are?
>
> Based on my reading of the code (and I don't fully understand the VM
> code, so this may be a wrong analysis):
>
> That message seems to be very right. It seems to come when we get
> into a 'memory overcommit' situation (ie, there isn't enough swap to
> satify your memory use if you dirty all pages). It suggest adding
> twice as much swap space as what we overcommit.
I don't know what is 'overcommit'. Apparently, it is not measured
anywhere. This message suggest you have swap space twice as much as
your RAM (sounds familiar, eh?). It is printed when your free swap space
is less than your RAM size. Apparently, this is also to warn you that
system will try hard to keep swap free. This is done by the code I
pointed to in my previous posting. IMHO, the limit for free swap
space is too large.
Dima
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 16:48:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA14763
for freebsd-current-outgoing; Tue, 10 Nov 1998 16:48:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14754
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 16:48: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 LAA22971;
Wed, 11 Nov 1998 11:47:51 +1100
Date: Wed, 11 Nov 1998 11:47:51 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811110047.LAA22971@godzilla.zeta.org.au>
To: bde@zeta.org.au, nate@mt.sri.com
Subject: Re: The infamous dying daemons bug
Cc: archie@whistle.com, current@FreeBSD.ORG, phk@critter.freebsd.dk
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> I couldn't duplicate the dying daemons problem despite trying fairly
>> hard, and thought that this might be because I link everything in the
>> world static.
>
>I thought you linked everything shared. What made you change your mind?
Inexpensive disks.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 17:11:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA16693
for freebsd-current-outgoing; Tue, 10 Nov 1998 17:11:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16686
for <current@freebsd.org>; Tue, 10 Nov 1998 17:11:23 -0800 (PST)
(envelope-from archer@grape.carrier.kiev.ua)
Received: from grape.carrier.kiev.ua (root@grape.carrier.kiev.ua [193.193.193.219])
by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) with ESMTP id DAA04714;
Wed, 11 Nov 1998 03:10:54 +0200 (EET)
(envelope-from archer@grape.carrier.kiev.ua)
Received: (from archer@localhost)
by grape.carrier.kiev.ua (8.9.1/8.9.1) id CAA01861;
Wed, 11 Nov 1998 02:38:38 +0200 (EET)
(envelope-from archer)
Date: Wed, 11 Nov 1998 02:38:38 +0200 (EET)
From: Alexander Litvin <archer@lucky.net>
Message-Id: <199811110038.CAA01861@grape.carrier.kiev.ua>
To: Alexander Litvin <archer@lucky.net>
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
X-Newsgroups: grape.freebsd.current
In-Reply-To: <199811101456.QAA28210@grape.carrier.kiev.ua>
Organization: Lucky Grape
User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386))
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <199811101456.QAA28210@grape.carrier.kiev.ua> you wrote:
>>> Nov 10 03:15:34 grape /kernel: swap_pager: suggest more swap space: 61 MB
>>> Nov 10 03:16:26 grape /kernel: pid 310 (sendmail), uid 0: exited on signal 11
>>> Nov 10 03:17:26 grape /kernel: pid 311 (sendmail), uid 0: exited on signal 11
>>> Nov 10 03:18:25 grape /kernel: pid 313 (sendmail), uid 0: exited on signal 11
>>> Nov 10 03:19:25 grape /kernel: pid 353 (sendmail), uid 0: exited on signal 11
>>> Nov 10 03:20:26 grape /kernel: pid 394 (sendmail), uid 0: exited on signal 11
GL>> Ah, now that's one that I've been getting without exhausting memory.
GL>> I'm assuming that these dying sendmails are children of the daemon.
GL>> What happens when you kill -1 the daemon ("accepting connections on
GL>> port 25 (sendmail)")? In my experience, it *always* dies with a
GL>> SIGSEGV after these messages have occurred.
AL> Well, as I understand, 'swap_pager: suggest more swap space' does
AL> not mean that memory is exhausted, but only that it is about to
AL> be exhausted. At least, in this case it didn't come to any processes
AL> being killed by kernel.
AL> You're right -- that sendmails were childs of a daemon (queue runners).
AL> I'm not sure about what happens if I send SIGHUP to the daemon. I
AL> think it may or may not restart -- it depends. Last time I examined
AL> a 'deseased' daemon (it was not sendmail, but a dummy daemon written
AL> specially for testing), it appeared that some range of process memory,
AL> where code of dynamic library lives, was corrupt (zeroed in that case).
AL> I'll try later to kill -1 such daemon. Now I'm in the process of testing
AL> Dima's kludge. Until now I was unable to reproduce a problem. Daemons
AL> keep living ;)
Brought up old kernel without kludge.
It appears that memory corruption leading to 'daemons dying' may take
different forms. E.g., once it appears that sendmail continues to
fork for queue runs successfully, but when I do 'telnet localhost 25',
it just accepts connection, forks, changes proctitle ('startup with ...'),
and goes into some strange state -- no EHLO, just accepts all I type
in telnet and that's all. In that state kill -1 restarts sendmail ok.
Other time I exhaust memory, sendmail segfaults every child forked
for queue run, again restarts ok on SIGHUP. Once I even got in responce
to 'telnet localhost 25':
Trying 127.0.0.1...
Connected to localhost.carrier.kiev.ua.
Escape character is '^]'.
archer... Recipient names must be specified
As if I started sendmail without arguments on command prompt!
I think it is ehough evidence that 'daemons dying' is caused by
memory corruption.
GL>> Greg
GL>> --
GL>> See complete headers for address, home page and phone numbers
GL>> finger grog@lemis.com for PGP public key
---
I really hate this damned machine
I wish that they would sell it.
It never does quite what I want
But only what I tell it.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 17:32:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA18476
for freebsd-current-outgoing; Tue, 10 Nov 1998 17:32:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18414
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 17:31:57 -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 VAA20607;
Tue, 10 Nov 1998 21:31:18 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 10 Nov 1998 21:31:17 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Tom <tom@uniserve.com>
cc: Mike Smith <mike@smith.net.au>, Paul Saab <paul@mu.org>,
current@FreeBSD.ORG
Subject: Re: 18gig drive's supported?
In-Reply-To: <Pine.BSF.4.02A.9811101021260.7226-100000@shell.uniserve.ca>
Message-ID: <Pine.BSF.4.05.9811102108420.337-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, 10 Nov 1998, Tom wrote:
>
> On Tue, 10 Nov 1998, The Hermit Hacker wrote:
>
> > Surprisingly, I did...when I upgraded the system to its currently
> > level...:( Now I've got sysinstall upgraded and installed, but when I go
> > to 'label' or 'fdisk', it auto-presents me with da0, but doesn't give me
> > the old choices of working with any of the other drives...did I miss a new
> > command line switch her or something like that? Have read man pages, have
> > built a new libdisk.a *just in case*...
>
> Give up and use fdisk, disklabel, and newfs directly. I think it was a
> mistake to re-invent the whell and re-develop all these functions and call
> it sysinstall. sysinstall has problems with large DPT disks too, but
> disklable and newfs work fine directly.
Actually, the only one that I use /stand/sysinstall for is the
fdisk part...disklabel and newfs I always use directly. fdisk just isn't
"intuitive" to even the far extreme. For instance, I just put a 9gig
drive into the machine, that was previously used under NetBSD. Going in
through /stand/sysinstall, I can't fdisk the drive, which I find odd. So,
using fdisk itself, I see:
hub# fdisk da2
******* Working on device /dev/rda2 *******
parameters extracted from in-core disklabel are:
cylinders=1106 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1106 heads=255 sectors/track=63 (16065 blks/cyl)
fdisk: invalid fdisk partition table found
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
<UNUSED>
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 1, size 17767889 (8675 Meg), flag 80 (active)
beg: cyl 0/ sector 2/ head 0;
end: cyl 81/ sector 63/ head 254
I just read through the fdisk man page, and *nothing* jumped out at me as
to how I can fix this manually...
Ideas or suggestions?
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 Nov 10 17:42:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA19365
for freebsd-current-outgoing; Tue, 10 Nov 1998 17:42:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from werple.mira.net (werple.mira.net [203.9.190.18])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA19360
for <freebsd-current@FreeBSD.ORG>; Tue, 10 Nov 1998 17:42:52 -0800 (PST)
(envelope-from gfm@mira.net)
Received: (qmail 24826 invoked from network); 11 Nov 1998 01:42:34 -0000
Received: from dp-m-r059.werple.net.au (203.17.46.59)
by mira.net with SMTP; 11 Nov 1998 01:42:34 -0000
From: gfm@mira.net (Graham Menhennitt)
To: Tim Gibson <tim@imc.ca>, freebsd-current@FreeBSD.ORG
Subject: Re: Named bootfile format doco: help please
Date: Wed, 11 Nov 1998 01:45:05 GMT
Message-ID: <3648eb90.101916788@mira.net>
References: <364ab500.87948363@mira.net> <3648BEB2.ABD322C@imc.ca>
In-Reply-To: <3648BEB2.ABD322C@imc.ca>
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 RAA19361
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 10 Nov 1998 17:31:14 -0500, Tim Gibson <tim@imc.ca> wrote:
>> Could somebody point me to the doco for version 8.1.2. Alternatively could
>> somebody give me an example of how to set up named for my configuration.
>
>From the BIND page on ISC;
>
>what's this? >> BIND 8.1.2 Documentation.
> A fairly recent BOG (BIND Operations Guide),
>available in both
> PostScript or Lineprinter formats. Thanks to
>Graeme Cox there is also a
> somewhat recent HTML version available.
Ok - I didn't look at the postscript or lineprinter format versions. But
the HTML version is still for the old format. I'll have a look at the ps
one.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 17:54:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA20355
for freebsd-current-outgoing; Tue, 10 Nov 1998 17:54:20 -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 RAA20350
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 17:54:19 -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 RAA02125;
Tue, 10 Nov 1998 17:51:40 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811110151.RAA02125@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: The Hermit Hacker <scrappy@hub.org>
cc: Tom <tom@uniserve.com>, Mike Smith <mike@smith.net.au>,
Paul Saab <paul@mu.org>, current@FreeBSD.ORG
Subject: Re: 18gig drive's supported?
In-reply-to: Your message of "Tue, 10 Nov 1998 21:31:17 -0400."
<Pine.BSF.4.05.9811102108420.337-100000@thelab.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Nov 1998 17:51:39 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I just read through the fdisk man page, and *nothing* jumped out at me as
> to how I can fix this manually...
>
> Ideas or suggestions?
# dd if=/dev/zero of=/dev/da0 count=16
# disklabel -rw da0 auto
--
\\ 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 Nov 10 18:22:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA23385
for freebsd-current-outgoing; Tue, 10 Nov 1998 18:22: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 SAA23378
for <current@freebsd.org>; Tue, 10 Nov 1998 18:22:29 -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 VAA14964;
Tue, 10 Nov 1998 21:22:06 -0500 (EST)
Date: Tue, 10 Nov 1998 21:22:05 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: "Richard Seaman, Jr." <lists@tar.com>
cc: "current@freebsd.org" <current@FreeBSD.ORG>
Subject: Re: RFSIGSHARE ready?
In-Reply-To: <199811101516.JAA20439@ns.tar.com>
Message-ID: <Pine.BSF.4.05.9811102118180.14660-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
Thank you!
On Tue, 10 Nov 1998, Richard Seaman, Jr. wrote:
> On Fri, 6 Nov 1998 21:27:50 -0500 (EST), Brian Feldman wrote:
>
> >I suppose it is. LinuxThreads don't work tho... I need %@#!^ testers!
>
> I looked briefly at your code, and I have a question. I understand
> that the "flags" argument to the clone call takes a signal number
> in the low order 8 bits of flags. This is the signal to be sent to
> the parent on exit of the thread.
This is strange... a signal is 5 bits. But I never new this, so thanks for
telling me!! I never new this, and this will be absolutely key to getting
LinuxThreads working (although this should REALLY be done in user-space...
perhaps I shall modify pthread_exit or whatever to send the signal
manually and see if that works perfectly. If so, I know where my effort
should be going :)
>
> I can see where you implement signal sharing, but
not where
you > record and implement this exit signal handling. Linuxthreads relies
> on the thread manager thread receiving a "PTHREAD_SIG_RESTART"
> signal (actually SIGUSR1) when threads exit.
>
> Perhaps I've missed something?
This doesn't necessarily sound like it's the last bug to be fixed, but it
sure could be. Thanks a bunch!
Cheers,
Brian Feldman
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 18:28:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA24092
for freebsd-current-outgoing; Tue, 10 Nov 1998 18:28:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from werple.mira.net (werple.mira.net [203.9.190.18])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA24087
for <freebsd-current@FreeBSD.ORG>; Tue, 10 Nov 1998 18:28:21 -0800 (PST)
(envelope-from gfm@mira.net)
Received: (qmail 1797 invoked from network); 11 Nov 1998 02:28:02 -0000
Received: from dp-m-q215.werple.net.au (203.17.45.215)
by mira.net with SMTP; 11 Nov 1998 02:28:02 -0000
From: gfm@mira.net (Graham Menhennitt)
To: Tim Gibson <tim@imc.ca>, freebsd-current@FreeBSD.ORG
Subject: Re: Named bootfile format doco: help please
Date: Wed, 11 Nov 1998 02:30:33 GMT
Message-ID: <364cf6ac.104760998@mira.net>
References: <364ab500.87948363@mira.net> <3648BEB2.ABD322C@imc.ca> <3648eb90.101916788@mira.net>
In-Reply-To: <3648eb90.101916788@mira.net>
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 SAA24088
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 11 Nov 1998 01:45:05 GMT, I wrote:
>On Tue, 10 Nov 1998 17:31:14 -0500, Tim Gibson <tim@imc.ca> wrote:
>
>>> Could somebody point me to the doco for version 8.1.2. Alternatively could
>>> somebody give me an example of how to set up named for my configuration.
>>
>>From the BIND page on ISC;
>>
>>what's this? >> BIND 8.1.2 Documentation.
>> A fairly recent BOG (BIND Operations Guide),
>>available in both
>> PostScript or Lineprinter formats. Thanks to
>>Graeme Cox there is also a
>> somewhat recent HTML version available.
>
>Ok - I didn't look at the postscript or lineprinter format versions. But
>the HTML version is still for the old format. I'll have a look at the ps
>one.
Oops, I've had another look. There are actually four links here
BIND 8.1.2 Documentation.
PostScript
Lineprinter
HTML
I was looking for HTML so I picked the fourth. It's the old version. I
missed the first one which is exactly what I wanted. Sorry.
Thanks,
Graham
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 18:46:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA25725
for freebsd-current-outgoing; Tue, 10 Nov 1998 18:46:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25720;
Tue, 10 Nov 1998 18:46:31 -0800 (PST)
(envelope-from drosih@rpi.edu)
Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47])
by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id VAA153568;
Tue, 10 Nov 1998 21:47:08 -0500
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: drosih@pop1.rpi.edu
Message-Id: <v04011703b26ea9a621c9@[128.113.24.47]>
In-Reply-To: <4126.910720382@gjp.erols.com>
References: Your message of "Tue, 10 Nov 1998 12:06:25 EST."
<v04011700b26e1fccb9c1@[128.113.24.47]>
Date: Tue, 10 Nov 1998 21:46:17 -0500
To: "Gary Palmer" <gpalmer@FreeBSD.ORG>
From: Garance A Drosihn <drosih@rpi.edu>
Subject: Re: The infamous dying daemons bug
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
At 12:53 PM -0500 11/10/98, Gary Palmer wrote:
>Garance A Drosihn wrote in message ID
><v04011700b26e1fccb9c1@[128.113.24.47]>:
>> Presumably the message is there to give advance warning about the
>> usage of swap. A message that says "Hey, you're out of swap" just
>> seconds before the machine completely dies is not quite as useful
>> as one that tries to give you more advance notice (such that you
>> could think about adding more swap space next weekend).
>
> Then I'd prefer to see a user-tunable setting which prints out a
> kernel error when you reach a certain percentage of swap space
> used. IMHO, in a server environment, that makes much more sense
> as you want to keep everything possible in RAM, and using swap
> (any swap) is a last resort. Thats certainly how I try to tune
> my servers.
Could that be handled by something that runs during the weekly
system-checks? (the email that goes to root). I almost cobbled
something together by checking the output of "top" for this, but
in my case it isn't all that critical that no swap is used. (my
machine has been up for two months without going to swap, but it
is also configured with 400meg of swapspace "just in case").
A user-tunable setting for the kernel error message seems like
a reasonable idea too, of course.
---
Garance Alistair Drosehn = gad@eclipse.its.rpi.edu
Senior Systems Programmer or drosih@rpi.edu
Rensselaer Polytechnic Institute
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 19:02:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA27331
for freebsd-current-outgoing; Tue, 10 Nov 1998 19:02: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 TAA27315
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 19:02:31 -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 NAA20772;
Wed, 11 Nov 1998 13:32:13 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.1/8.9.0) id NAA20401;
Wed, 11 Nov 1998 13:32:12 +1030 (CST)
Message-ID: <19981111133212.B20374@freebie.lemis.com>
Date: Wed, 11 Nov 1998 13:32:12 +1030
From: Greg Lehey <grog@lemis.com>
To: Alexander Litvin <archer@lucky.net>
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <199811101456.QAA28210@grape.carrier.kiev.ua> <199811110038.CAA01861@grape.carrier.kiev.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199811110038.CAA01861@grape.carrier.kiev.ua>; from Alexander Litvin on Wed, Nov 11, 1998 at 02:38:38AM +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 Wednesday, 11 November 1998 at 2:38:38 +0200, Alexander Litvin wrote:
> In article <199811101456.QAA28210@grape.carrier.kiev.ua> you wrote:
>
>>>> Nov 10 03:15:34 grape /kernel: swap_pager: suggest more swap space: 61 MB
>>>> Nov 10 03:16:26 grape /kernel: pid 310 (sendmail), uid 0: exited on signal 11
>>>> Nov 10 03:17:26 grape /kernel: pid 311 (sendmail), uid 0: exited on signal 11
>>>> Nov 10 03:18:25 grape /kernel: pid 313 (sendmail), uid 0: exited on signal 11
>>>> Nov 10 03:19:25 grape /kernel: pid 353 (sendmail), uid 0: exited on signal 11
>>>> Nov 10 03:20:26 grape /kernel: pid 394 (sendmail), uid 0: exited on signal 11
>
> GL>> Ah, now that's one that I've been getting without exhausting memory.
> GL>> I'm assuming that these dying sendmails are children of the daemon.
> GL>> What happens when you kill -1 the daemon ("accepting connections on
> GL>> port 25 (sendmail)")? In my experience, it *always* dies with a
> GL>> SIGSEGV after these messages have occurred.
>
> AL> Well, as I understand, 'swap_pager: suggest more swap space' does
> AL> not mean that memory is exhausted, but only that it is about to
> AL> be exhausted. At least, in this case it didn't come to any processes
> AL> being killed by kernel.
>
> AL> You're right -- that sendmails were childs of a daemon (queue runners).
> AL> I'm not sure about what happens if I send SIGHUP to the daemon. I
> AL> think it may or may not restart -- it depends. Last time I examined
> AL> a 'deseased' daemon (it was not sendmail, but a dummy daemon written
> AL> specially for testing), it appeared that some range of process memory,
> AL> where code of dynamic library lives, was corrupt (zeroed in that case).
>
> AL> I'll try later to kill -1 such daemon. Now I'm in the process of testing
> AL> Dima's kludge. Until now I was unable to reproduce a problem. Daemons
> AL> keep living ;)
>
> Brought up old kernel without kludge.
>
> It appears that memory corruption leading to 'daemons dying' may take
> different forms. E.g., once it appears that sendmail continues to
> fork for queue runs successfully, but when I do 'telnet localhost 25',
> it just accepts connection, forks, changes proctitle ('startup with ...'),
> and goes into some strange state -- no EHLO, just accepts all I type
> in telnet and that's all. In that state kill -1 restarts sendmail ok.
> Other time I exhaust memory, sendmail segfaults every child forked
> for queue run, again restarts ok on SIGHUP. Once I even got in responce
> to 'telnet localhost 25':
>
> Trying 127.0.0.1...
> Connected to localhost.carrier.kiev.ua.
> Escape character is '^]'.
> archer... Recipient names must be specified
>
> As if I started sendmail without arguments on command prompt!
>
> I think it is ehough evidence that 'daemons dying' is caused by
> memory corruption.
Well, no, I had an alternative explanation: for me, this problem
started with sendmail 8.9. I think I even went back and tried
sendmail 8.8.<mumble> and it didn't cause any problems. It could be a
bug in sendmail, possibly related to the config I'm using (it often
refuses connections because it thinks some test on the domain name
succeeds, when in fact it should have failed).
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 Tue Nov 10 20:16:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA03034
for freebsd-current-outgoing; Tue, 10 Nov 1998 20:16:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03021;
Tue, 10 Nov 1998 20:16:12 -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 AAA21290;
Wed, 11 Nov 1998 00:15:51 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 11 Nov 1998 00:15:51 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: freebsd-current@FreeBSD.ORG
cc: freebsd-scsi@FreeBSD.ORG
Subject: SCSI Bus errors spewing on console...
Message-ID: <Pine.BSF.4.05.9811110012450.337-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
Can someone tell me *what* this means? I have someone rushing to the
office right now to reboot the machine, as there is nothing that I can do
from here...is it a mis-configuration in my kernel (ie. I have to raise a
limit somewhere?) or a driving going back (which one?) or something
altogether different?
I'm running a 3.0 system, still aout, but based on the cvs tree of
~3.0-RELEASE...I'd provide dmesg output, except I can't get into the
machine to get it ;(
It started all of a sudden...server was working fine all evening, then all
of a sudden, loadavg went through the roof...figured I might have more
response through the serial console, so switched to that, and saw this..
thanks in advance for *any* help on this...
ahc2: Bus Device Reset on A:1. 4 SCBs aborted
ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET
SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40
ahc2: Bus Device Reset on A:1. 4 SCBs aborted
ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET
SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40
ahc2: Bus Device Reset on A:1. 4 SCBs aborted
ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET
SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40
ahc2: Bus Device Reset on A:1. 4 SCBs aborted
ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET
SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40
ahc2: Bus Device Reset on A:1. 4 SCBs aborted
ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET
SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40
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 Nov 10 22:45:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA08184
for freebsd-current-outgoing; Tue, 10 Nov 1998 22:45:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08178
for <current@freebsd.org>; Tue, 10 Nov 1998 22:45:20 -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 QAA14820
for current@freebsd.org; Wed, 11 Nov 1998 16:04:07 +1100
Date: Wed, 11 Nov 1998 16:04:07 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811110504.QAA14820@godzilla.zeta.org.au>
To: current@FreeBSD.ORG
Subject: linux bugs
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Installing linux from sys/modules/linux/ clobbers the version installed
from lkm/linux/, and vice versa. Breakage is limited by bugs in
`make world' - lkms are only built if ${OBJFORMAT} == aout, although
they should be built in all cases in case the kernel format is aout.
`make clean' in sys/modules/linux/ deletes linux if there is no obj
directory.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 22:46:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA08361
for freebsd-current-outgoing; Tue, 10 Nov 1998 22:46:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from proxy3.aha.ru (proxy3.aha.ru [195.2.83.100])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08341
for <current@FreeBSD.org>; Tue, 10 Nov 1998 22:46:13 -0800 (PST)
(envelope-from osa@etrust.ru)
Received: from ns1.aha.ru (ns1.aha.ru [195.2.80.142])
by proxy3.aha.ru (8.9.1/aha-r/0.03F) with ESMTP id IAA16894
for <current@FreeBSD.org>; Wed, 11 Nov 1998 08:51:52 +0300 (MSK)
Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112])
by ns1.aha.ru (8.9.1/8.9.1/aha-r/0.04B) with ESMTP id IAA14054
for <current@FreeBSD.org>; Wed, 11 Nov 1998 08:51:50 +0300 (MSK)
Received: by sunny.aha.ru id IAA26482;
(8.8.8/vak/1.9) Wed, 11 Nov 1998 08:48:55 +0300 (MSK)
Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3)
id sma026438; Wed Nov 11 08:48:30 1998
Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116])
by serv.etrust.ru (8.9.1/8.9.1) with ESMTP id IAA14020
for <current@FreeBSD.org>; Wed, 11 Nov 1998 08:50:54 +0300 (MSK)
(envelope-from osa@etrust.ru)
Received: from localhost (localhost [127.0.0.1])
by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id IAA03309
for <current@FreeBSD.org>; Wed, 11 Nov 1998 08:53:07 +0300 (MSK)
(envelope-from osa@etrust.ru)
Date: Wed, 11 Nov 1998 08:53:05 +0300 (MSK)
From: oZZ!!! <osa@etrust.ru>
To: current@FreeBSD.ORG
Subject: StarOffice-5.0...
Message-ID: <Pine.BSF.4.05.9811110847250.3304-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
Hello!
I try to install StarOffice-5.0 for linux.
It want libc-2.0.7.so & libthread-0.7.so....
( as said in README glibc-2.0.7-7-7.i386.rpm)
I think its a RedHat distribution, but how can operate with
that rpm-filez ??
Plz help
Rgdz,
Osokin Sergey aka oZZ,
osa@etrust.ru
http://www.freebsd.org.ru
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 22:47:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA08548
for freebsd-current-outgoing; Tue, 10 Nov 1998 22:47:53 -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 WAA08541
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 22:47:52 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id WAA09461;
Tue, 10 Nov 1998 22:48:22 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
To: Bruce Evans <bde@zeta.org.au>
cc: current@FreeBSD.ORG
Subject: Re: linux bugs
In-reply-to: Your message of "Wed, 11 Nov 1998 16:04:07 +1100."
<199811110504.QAA14820@godzilla.zeta.org.au>
Date: Tue, 10 Nov 1998 22:48:22 -0800
Message-ID: <9457.910766902@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Installing linux from sys/modules/linux/ clobbers the version installed
> from lkm/linux/, and vice versa. Breakage is limited by bugs in
Given that modules are meant to replace lkms, I don't find that
particularly odd.
> `make world' - lkms are only built if ${OBJFORMAT} == aout, although
> they should be built in all cases in case the kernel format is aout.
Hmmm. Should they? What about a.out modules?
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 22:55:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA09611
for freebsd-current-outgoing; Tue, 10 Nov 1998 22:55:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from luke.cpl.net (luke.cpl.net [209.150.92.68])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09598
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 22:54:59 -0800 (PST)
(envelope-from shawn@luke.cpl.net)
Received: (from shawn@localhost)
by luke.cpl.net (8.8.8/8.8.8) id WAA29840;
Tue, 10 Nov 1998 22:54:40 -0800 (PST)
Message-ID: <19981110225440.C25741@cpl.net>
Date: Tue, 10 Nov 1998 22:54:40 -0800
From: Shawn Ramsey <shawn@cpl.net>
To: oZZ!!! <osa@etrust.ru>, current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
References: <Pine.BSF.4.05.9811110847250.3304-100000@ozz.etrust.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93i
In-Reply-To: <Pine.BSF.4.05.9811110847250.3304-100000@ozz.etrust.ru>; from oZZ!!! on Wed, Nov 11, 1998 at 08:53:05AM +0300
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I try to install StarOffice-5.0 for linux.
> It want libc-2.0.7.so & libthread-0.7.so....
> ( as said in README glibc-2.0.7-7-7.i386.rpm)
> I think its a RedHat distribution, but how can operate with
> that rpm-filez ??
> Plz help
I don't think 5.0 works on FreeBSD. I attempted it, and was only able to
achieve a core dump executing setup.
This was on a 2.2.7-RELEASE system.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 22:55:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA09652
for freebsd-current-outgoing; Tue, 10 Nov 1998 22:55:22 -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 WAA09646
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 22:55:16 -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.1/8.9.1/Spinner) with ESMTP id OAA08875;
Wed, 11 Nov 1998 14:40:32 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811110640.OAA08875@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Tue, 10 Nov 1998 22:17:20 PST."
<9326.910765040@zippy.cdrom.com>
Date: Wed, 11 Nov 1998 14:40:32 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"Jordan K. Hubbard" wrote:
> I can see we are simply of two minds on this issue. :) What do some of
> the others think?
Oh, one other thing.. I don't care enough about this to argue about it
(for long :-). Don't interpret my objections as an implied "over my dead
body" kinda thing. I just want to point out that /usr/mdec has worked
quite well for *years*, it's a known quantity, and that *I* believe that
taking up precious root disk space by shoving unneeded stuff in /boot
(which is critical to system bootup) is going in exactly the wrong
direction and gains so little (or no) benefit.
Yes, "mdec" is a wierd name. So is "/etc/rc", "creat(2)", "dd", "pax",
"vi", etc etc. Incidently, my objections are about putting it in /, not so
much changing the name.
> - Jordan
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 22:55:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA09706
for freebsd-current-outgoing; Tue, 10 Nov 1998 22:55:30 -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 WAA09661
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 22:55: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.1/8.9.1/Spinner) with ESMTP id OAA08762;
Wed, 11 Nov 1998 14:05:24 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811110605.OAA08762@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Tue, 10 Nov 1998 21:49:00 PST."
<8872.910763340@zippy.cdrom.com>
Date: Wed, 11 Nov 1998 14:05:23 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"Jordan K. Hubbard" wrote:
> > Oh, one other thing.. libdisk is built by doing a file2c of /usr/mdec/
> > boot1/boot2 and compiling it in. It is using the *old* boot code, because
> > libdisk is built before src/sys/boot in a 'make world'.
>
> I suppose we could move src/sys/boot earlier in the worldbuild.
> Any objections?
How do we build them? It uses elf (cc, as, m4, etc), the btx tools, and
libstand, and are they all available before we build src/lib? I have a
hard enough time following the inter-dependencies of a world build..
> > BTW; I really do not like moving the bootblock source files (boot0/1/2) to
> > /boot; I think of /boot as an equivalent to the bootblocks.. /usr/mdec
>
> There are several good reasons for shooting /usr/mdec through the
> head, once more through the heart for good measure and then jumping up
> and down on its twitching corpse for awhile. I shall list them:
>
> 1. It is under /usr. disklabel is in /sbin. Enough said.
So? If you've got as far as running /sbin/disklabel, you have already
booted. Availability (or not) of new bootblocks isn't going to make the
slightest difference as to whether you can repair and mount /usr or not.
I'd argue that if you can't mount /usr, the stage 0,1 and 2 bootblocks are
the least of your worries. :-)
> 2. /usr/mdec, evil though it was, gave us a single place to look for
> boot related material. It wasn't a lot of material (<2MB) but it
> was diverse enough to include UFS, DOS and network booting code
> and it would be a shame to have to remember to look in two places for
> that stuff. I think there should be only one boot frob
> directory and that it should be /boot
/usr/mdec was a storage area, nothing more. /boot contains *running* code
and configuration files and is a rather sensitive area. IMHO, we don't
need to fill it up with 1.5MB of junk that isn't related to getting this
instance of the system up and running. cdboot for instance does not
belong in /boot. The netboot roms do not belong in /boot. fbsdboot.exe
does not belong in /boot.
I for one do not have a spare 1.5MB of root partition space on my systems
(except one) to fill up with junk. Most were partitioned years ago and
date back to 2.0 or 2.0.5 days.
> - Jordan
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 22:56:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA09906
for freebsd-current-outgoing; Tue, 10 Nov 1998 22:56:15 -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 WAA09890
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 22:56:06 -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.1/8.9.1/Spinner) with ESMTP id NAA08393;
Wed, 11 Nov 1998 13:09:18 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811110509.NAA08393@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mike Smith <mike@smith.net.au>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Tue, 10 Nov 1998 12:44:48 PST."
<199811102044.MAA00415@dingo.cdrom.com>
Date: Wed, 11 Nov 1998 13:09:17 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Smith wrote:
> > I'm just wondering when we're going to switch the kernel to ELF and
> > put /usr/src/sys/modules into the build path. I'd really like the
> > /usr/bin/linux command to start doing the right thing on current 3.0
> > SNAPshots, among other things. :-)
>
> I think we're about ready to do it. We probably want to insist that
> people cut over to the new bootstrap first, perhaps with a HEADS UP
> announcement from someone that hasn't cried wolf before.
Just something to tickle everybody's sense of perverse.. You can load ELF
kld modules into an a.out kernel and vice versa...
/boot/loader will not let you do this, but the kernel does it (and does
the right thing as far as I've seen).
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 22:56:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA09968
for freebsd-current-outgoing; Tue, 10 Nov 1998 22:56:39 -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 WAA09936
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 22:56:25 -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.1/8.9.1/Spinner) with ESMTP id NAA08424;
Wed, 11 Nov 1998 13:13:12 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811110513.NAA08424@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mike Smith <mike@smith.net.au>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Tue, 10 Nov 1998 12:44:48 PST."
<199811102044.MAA00415@dingo.cdrom.com>
Date: Wed, 11 Nov 1998 13:13:11 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Smith wrote:
> > I'm just wondering when we're going to switch the kernel to ELF and
> > put /usr/src/sys/modules into the build path. I'd really like the
> > /usr/bin/linux command to start doing the right thing on current 3.0
> > SNAPshots, among other things. :-)
>
> I think we're about ready to do it. We probably want to insist that
> people cut over to the new bootstrap first, perhaps with a HEADS UP
> announcement from someone that hasn't cried wolf before.
Oh, one other thing.. libdisk is built by doing a file2c of /usr/mdec/
boot1/boot2 and compiling it in. It is using the *old* boot code, because
libdisk is built before src/sys/boot in a 'make world'.
BTW; I really do not like moving the bootblock source files (boot0/1/2) to
/boot; I think of /boot as an equivalent to the bootblocks.. /usr/mdec
should be where they remain stored, and it's where disklabel expects them
too.
> --
> \\ 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
>
>
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 Nov 10 23:06:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA11657
for freebsd-current-outgoing; Tue, 10 Nov 1998 23:06: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 XAA11649
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 23:06:45 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id WAA09330;
Tue, 10 Nov 1998 22:17:20 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
To: Peter Wemm <peter@netplex.com.au>
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 14:05:23 +0800."
<199811110605.OAA08762@spinner.netplex.com.au>
Date: Tue, 10 Nov 1998 22:17:20 -0800
Message-ID: <9326.910765040@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 see we are simply of two minds on this issue. :) What do some of
the others think?
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 23:06:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA11665
for freebsd-current-outgoing; Tue, 10 Nov 1998 23:06:49 -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 XAA11651
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 23:06:46 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id VAA08876;
Tue, 10 Nov 1998 21:49:01 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
To: Peter Wemm <peter@netplex.com.au>
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 13:13:11 +0800."
<199811110513.NAA08424@spinner.netplex.com.au>
Date: Tue, 10 Nov 1998 21:49:00 -0800
Message-ID: <8872.910763340@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Oh, one other thing.. libdisk is built by doing a file2c of /usr/mdec/
> boot1/boot2 and compiling it in. It is using the *old* boot code, because
> libdisk is built before src/sys/boot in a 'make world'.
I suppose we could move src/sys/boot earlier in the worldbuild.
Any objections?
> BTW; I really do not like moving the bootblock source files (boot0/1/2) to
> /boot; I think of /boot as an equivalent to the bootblocks.. /usr/mdec
There are several good reasons for shooting /usr/mdec through the
head, once more through the heart for good measure and then jumping up
and down on its twitching corpse for awhile. I shall list them:
1. It is under /usr. disklabel is in /sbin. Enough said.
2. /usr/mdec, evil though it was, gave us a single place to look for
boot related material. It wasn't a lot of material (<2MB) but it
was diverse enough to include UFS, DOS and network booting code
and it would be a shame to have to remember to look in two places for
that stuff. I think there should be only one boot frob
directory and that it should be /boot
3. /usr/mdec is a silly-assed name. Who thought of it? What does it even
stand for? hier(7) just says "boot programs; see disklabel(8)" and
doesn't particularly enlighten. And if it's just for disklabel,
as hier(7) strongly implies, then why isn't it on the root filesystem
along with disklabel? Like I said, it's <2MB in size so it can't be
for space reasons.
In short, I think /usr/mdec was a temporary cerebral aneurism on
someone's part and is a cryptically named, improperly located
anachronism that needs death. I want my boot blocks and anything else
I might want to copy on/off a floppy for booting purposes on the root
filesystem where they belong, along with my kernels! :-)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 23:48:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA16789
for freebsd-current-outgoing; Tue, 10 Nov 1998 23:48:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16758;
Tue, 10 Nov 1998 23:47:58 -0800 (PST)
(envelope-from dv@dv.ru)
Received: from localhost (dv@localhost)
by xkis.kis.ru (8.9.0/8.9.0) with SMTP id KAA21116;
Wed, 11 Nov 1998 10:46:57 +0300 (MSK)
Date: Wed, 11 Nov 1998 10:46:57 +0300 (MSK)
From: Dmitry Valdov <dv@dv.ru>
X-Sender: dv@xkis.kis.ru
To: Brian Somers <brian@Awfulhak.org>
cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-Reply-To: <199811102125.VAA15982@woof.lan.awfulhak.org>
Message-ID: <Pine.BSF.3.95q.981111104515.20962A-100000@xkis.kis.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 Tue, 10 Nov 1998, Brian Somers wrote:
> Date: Tue, 10 Nov 1998 21:25:45 +0000
> From: Brian Somers <brian@Awfulhak.org>
> To: Dmitry Valdov <dv@dv.ru>
> Cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
> Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
>
> > Hi!
> >
> > There is a problem in ppp - when you kill it with -9, You'll not be able to
> > start it again until you reboot.
>
> Have you tried this with the latest ppp ? It cleans out the
> interface before it starts - this should result in the routing table
> being adjusted.
>
Yes, I have tried it with 3 days old ppp. I'll try it again in this week
after next 'make world'.
> Having said that, killing anything with -9 is usually bad news.
I know. But why not to do cleanup at startup instead of hanging?
Dmitry.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 23:51:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA16993
for freebsd-current-outgoing; Tue, 10 Nov 1998 23:51:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16969;
Tue, 10 Nov 1998 23:51:13 -0800 (PST)
(envelope-from dv@dv.ru)
Received: from localhost (dv@localhost)
by xkis.kis.ru (8.9.0/8.9.0) with SMTP id KAA21217;
Wed, 11 Nov 1998 10:50:33 +0300 (MSK)
Date: Wed, 11 Nov 1998 10:50:33 +0300 (MSK)
From: Dmitry Valdov <dv@dv.ru>
X-Sender: dv@xkis.kis.ru
To: Brian Somers <brian@Awfulhak.org>
cc: Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-Reply-To: <199811102130.VAA16348@woof.lan.awfulhak.org>
Message-ID: <Pine.BSF.3.95q.981111104744.20962B-100000@xkis.kis.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 Tue, 10 Nov 1998, Brian Somers wrote:
> Date: Tue, 10 Nov 1998 21:30:15 +0000
> From: Brian Somers <brian@Awfulhak.org>
> To: Dmitry Valdov <dv@dv.ru>
> Cc: Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
> Brian Somers <brian@freebsd.org>, current@freebsd.org
> Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
>
> > > > There is a problem in ppp - when you kill it with -9, You'll not be able to
> > > > start it again until you reboot.
> > > > Sometimes I need to kill it with -9 because when killing with SIGHUP it
> > > > tries to properly shutdown PPP session via LCP, but there is some cases when
> > > > it inpossible.
> > >
> > > Doing a 'route delete default' seems to fix this for me (otherwise it just
> > > hangs when I try and restart it).
> > >
> >
> > Thanks, will be know. But why not to fix it in ppp? :)
>
> What do you suggest is changed ? Ppp can't delete the default route
> on it's own - it doesn't necessarily belong to ppp.
>
Why? If I have add default [...] in ppp.conf, and there is impossible to
have 2 defaults then ppp shoul delete old default and make new :)
> > Also there is one more bug - sometimes ppp don't detect carrier lost and
> > stays in open state for a long time. :(
>
> Get the latest version from http://www.Awfulhak.org/ppp.html and
> enable debug logging. You'll see ppps idea of carrier. I suspect
> that either your modem is faking carrier all the time or that you're
> running a very old version (2.2.5?).
>
1. I'm running version from -current.
2. I've USR Sportster 28800 modem and my friend have an IDC modem. We are
both experiencing the same problem.
Please check it, I'm really shure that it isn't nmodem or user error :)
Dmitry.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 10 23:55:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA17376
for freebsd-current-outgoing; Tue, 10 Nov 1998 23:55:53 -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 XAA17371
for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 23:55:48 -0800 (PST)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.9.1/8.9.1) id SAA04980;
Wed, 11 Nov 1998 18:56:03 +1100 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199811110756.SAA04980@cimlogic.com.au>
Subject: Re: Is it soup yet? :-)
In-Reply-To: <9326.910765040@zippy.cdrom.com> from "Jordan K. Hubbard" at "Nov 10, 98 10:17:20 pm"
To: jkh@zippy.cdrom.com (Jordan K. Hubbard)
Date: Wed, 11 Nov 1998 18:56:02 +1100 (EST)
Cc: peter@netplex.com.au, mike@smith.net.au, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL40 (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 wrote:
> I can see we are simply of two minds on this issue. :) What do some of
> the others think?
I like the idea of having /boot (and killing /usr/mdec) and trashing lkms
asap. The kld flexibility is neat and /boot just seems to make sense.
I think this stuff is a _big_ step forward (and it's a shame it wasn't
ready for 3.0).
I've read Peter's concerns about systems that were disklabelled ages
ago, but I question the length of time we are expected to support disk
allocations from the past. Let's move forward...
--
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 Nov 11 00:04:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA18264
for freebsd-current-outgoing; Wed, 11 Nov 1998 00:04:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18137;
Wed, 11 Nov 1998 00:03:28 -0800 (PST)
(envelope-from nik@nothing-going-on.demon.co.uk)
Received: (from nik@localhost)
by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id AAA20896;
Wed, 11 Nov 1998 00:13:38 GMT
(envelope-from nik)
Message-ID: <19981111001338.06541@nothing-going-on.org>
Date: Wed, 11 Nov 1998 00:13:38 +0000
From: Nik Clayton <nik@nothing-going-on.demon.co.uk>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>, Mike Smith <mike@smith.net.au>
Cc: peter@FreeBSD.ORG, current@FreeBSD.ORG,
"Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Subject: Re: Is it soup yet? :-)
References: <199811102044.MAA00415@dingo.cdrom.com> <XFMail.981110224016.asmodai@wxs.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <XFMail.981110224016.asmodai@wxs.nl>; from Jeroen Ruigrok/Asmodai on Tue, Nov 10, 1998 at 10:40:16PM +0100
Organization: Nik at home, where there's nothing going on
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, Nov 10, 1998 at 10:40:16PM +0100, Jeroen Ruigrok/Asmodai wrote:
> Could someone please point a checklist of steps for a good migrating of
> aout to ELF? This would make it easier for us as well as being used as
> a reference point on the web in future for 2.2.x users to 3.0.x...
And when they do, can they either cc: it to -doc, or please take the
time to send-pr as a doc-change request. At the very least, I can add it
to my 'make world' tutorial.
N
--
C.R.F. Consulting -- we're run to make me richer. . .
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 00:08:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA18702
for freebsd-current-outgoing; Wed, 11 Nov 1998 00:08:40 -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 AAA18695
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 00:08:39 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id AAA00874;
Wed, 11 Nov 1998 00:04:56 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdAkl867; Wed Nov 11 08:04:45 1998
Date: Wed, 11 Nov 1998 00:04:10 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <8872.910763340@zippy.cdrom.com>
Message-ID: <Pine.BSF.3.95.981110235343.15702D-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
well, don't forget that those of us that require the old style bootblocks
and have *LOTS* of machines in the field that will be
upgrading to 3.0 based systems would like to see you NOT making the
following changes:
1/ kernels that REQUIRE the new bootblocks, even if statically linked.
2/ kernels that REQUIRE the new bootblocks, even if statically linked.
just thought I'd restate this to remind everyone in the boot-block crew..
:-)
the ability to run on old bootblocks is how shall I say...
"required".
loading new bootblocks is not an option on these systems, however they
must still have an upgrade path.
However anything goes with dynamically linked kernels...
(we don't use them anyhow)
On Tue, 10 Nov 1998, Jordan K. Hubbard wrote:
> > Oh, one other thing.. libdisk is built by doing a file2c of /usr/mdec/
> > boot1/boot2 and compiling it in. It is using the *old* boot code, because
> > libdisk is built before src/sys/boot in a 'make world'.
>
> I suppose we could move src/sys/boot earlier in the worldbuild.
> Any objections?
no, but keep our custommers in mind :-)
>
> > BTW; I really do not like moving the bootblock source files (boot0/1/2) to
> > /boot; I think of /boot as an equivalent to the bootblocks.. /usr/mdec
>
> There are several good reasons for shooting /usr/mdec through the
> head, once more through the heart for good measure and then jumping up
> and down on its twitching corpse for awhile. I shall list them:
>
> 1. It is under /usr. disklabel is in /sbin. Enough said.
>
> 2. /usr/mdec, evil though it was, gave us a single place to look for
> boot related material. It wasn't a lot of material (<2MB) but it
> was diverse enough to include UFS, DOS and network booting code
> and it would be a shame to have to remember to look in two places for
> that stuff. I think there should be only one boot frob
> directory and that it should be /boot
>
> 3. /usr/mdec is a silly-assed name. Who thought of it? What does it even
> stand for? hier(7) just says "boot programs; see disklabel(8)" and
> doesn't particularly enlighten. And if it's just for disklabel,
> as hier(7) strongly implies, then why isn't it on the root filesystem
> along with disklabel? Like I said, it's <2MB in size so it can't be
> for space reasons.
I don't care where this stuff goes as long as it still works :-)
>
> In short, I think /usr/mdec was a temporary cerebral aneurism on
> someone's part and is a cryptically named, improperly located
> anachronism that needs death. I want my boot blocks and anything else
> I might want to copy on/off a floppy for booting purposes on the root
> filesystem where they belong, along with my kernels! :-)
>
> - Jordan
>
> 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 Nov 11 00:12:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA19090
for freebsd-current-outgoing; Wed, 11 Nov 1998 00:12:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19084
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 00:12: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 TAA32188;
Wed, 11 Nov 1998 19:12:24 +1100
Date: Wed, 11 Nov 1998 19:12:24 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811110812.TAA32188@godzilla.zeta.org.au>
To: bde@zeta.org.au, jkh@zippy.cdrom.com
Subject: Re: linux bugs
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> Installing linux from sys/modules/linux/ clobbers the version installed
>> from lkm/linux/, and vice versa. Breakage is limited by bugs in
>
>Given that modules are meant to replace lkms, I don't find that
>particularly odd.
It's odd when the lkm one wins. Peter just fixed this.
>> `make world' - lkms are only built if ${OBJFORMAT} == aout, although
>> they should be built in all cases in case the kernel format is aout.
>
>Hmmm. Should they? What about a.out modules?
They didn't work until recently. It's surprising that stale lkms didn't
cause many problems.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 00:18:58 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA19557
for freebsd-current-outgoing; Wed, 11 Nov 1998 00:18: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 AAA19545
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 00:18:56 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id AAA09944;
Wed, 11 Nov 1998 00:18:40 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
To: Julian Elischer <julian@whistle.com>
cc: Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 00:04:10 PST."
<Pine.BSF.3.95.981110235343.15702D-100000@current1.whistle.com>
Date: Wed, 11 Nov 1998 00:18:39 -0800
Message-ID: <9940.910772319@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> the ability to run on old bootblocks is how shall I say...
> "required".
Well, you have and have always had just two options the minute we pull
the elf kernel switch: You switch customers to the 3-stage boot by
dropping a /boot.conf file into place which calls /boot/loader (which
you also install along with the 3.0 upgrade) or you relabel them so
they look just like freshly installed 3.0.x systems; it's your choice
whether you want to go for minimal impact or minimal difference.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 00:26:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA20182
for freebsd-current-outgoing; Wed, 11 Nov 1998 00:26:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from axl.training.iafrica.com (axl.training.iafrica.com [196.31.1.175])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20152
for <current@freebsd.org>; Wed, 11 Nov 1998 00:26:26 -0800 (PST)
(envelope-from sheldonh@axl.training.iafrica.com)
Received: from sheldonh (helo=axl.training.iafrica.com)
by axl.training.iafrica.com with local-esmtp (Exim 2.05 #1)
id 0zdVa1-0001Zb-00; Wed, 11 Nov 1998 10:24:45 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: oZZ!!! <osa@etrust.ru>
cc: current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-reply-to: Your message of "Wed, 11 Nov 1998 08:53:05 +0300."
<Pine.BSF.4.05.9811110847250.3304-100000@ozz.etrust.ru>
Date: Wed, 11 Nov 1998 10:24:45 +0200
Message-ID: <6050.910772685@axl.training.iafrica.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 11 Nov 1998 08:53:05 +0300, oZZ!!! wrote:
> I think its a RedHat distribution, but how can operate with
> that rpm-filez ??
Please not that the following answer to your question will almost
certainly _not_ solve your problem. However, you did ask a specific
question and you're probably going to want to ask it again in the
future.
There is a FreeBSD port for rpm, the RedHat package manager. If you know
about the ports tree already, it's in ports/misc/rpm . If you're not
familiar with the FreeBSD Ports Tree, see the FreeBSD handbook, section
4.
http://www.freebsd.org/handbook/handbook23.html#25
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 Nov 11 00:50:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA22003
for freebsd-current-outgoing; Wed, 11 Nov 1998 00:50:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.oeno.com (ns.oeno.com [194.100.99.145])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA21998
for <current@freebsd.org>; Wed, 11 Nov 1998 00:50:35 -0800 (PST)
(envelope-from will@ns.oeno.com)
Received: (qmail 2974 invoked by uid 1001); 11 Nov 1998 08:50:15 -0000
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
References: <8872.910763340@zippy.cdrom.com.newsgate.clinet.fi>
From: Ville-Pertti Keinonen <will@iki.fi>
Date: 11 Nov 1998 10:50:10 +0200
In-Reply-To: "Jordan K. Hubbard"'s message of "11 Nov 1998 09:39:50 +0200"
Message-ID: <863e7qbol9.fsf@not.oeno.com>
Lines: 8
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"Jordan K. Hubbard" <jkh@zippy.cdrom.com> writes:
> 3. /usr/mdec is a silly-assed name. Who thought of it? What does it even
The mdec name certainly isn't FreeBSD-specific, changing it would add
to the difficulty of finding things based on a "general knowledge" of
Unix-like systems.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 00:54:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA22298
for freebsd-current-outgoing; Wed, 11 Nov 1998 00:54:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22282
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 00:53: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 TAA02403;
Wed, 11 Nov 1998 19:53:40 +1100
Date: Wed, 11 Nov 1998 19:53:40 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811110853.TAA02403@godzilla.zeta.org.au>
To: jkh@zippy.cdrom.com, peter@netplex.com.au
Subject: Re: Is it soup yet? :-)
Cc: current@FreeBSD.ORG, mike@smith.net.au
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> > Oh, one other thing.. libdisk is built by doing a file2c of /usr/mdec/
>> > boot1/boot2 and compiling it in. It is using the *old* boot code, because
>> > libdisk is built before src/sys/boot in a 'make world'.
And it only works in the non-null DESTDIR case because it doesn't honour
DESTDIR.
>> I suppose we could move src/sys/boot earlier in the worldbuild.
>> Any objections?
>
>How do we build them? It uses elf (cc, as, m4, etc), the btx tools, and
>libstand, and are they all available before we build src/lib? I have a
>hard enough time following the inter-dependencies of a world build..
All tools are built before all (target) libraries.
I object to moving /usr/mdec, of course.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 01:05:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA22983
for freebsd-current-outgoing; Wed, 11 Nov 1998 01:05:14 -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 BAA22969;
Wed, 11 Nov 1998 01:05:09 -0800 (PST)
(envelope-from geoffb@gti.noc.demon.net)
Received: by server.noc.demon.net; id JAA07613; Wed, 11 Nov 1998 09:04:21 GMT
Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2)
id xma007607; Wed, 11 Nov 98 09:04:16 GMT
Received: (from geoffb@localhost)
by gti.noc.demon.net (8.8.8/8.8.8) id JAA10682;
Wed, 11 Nov 1998 09:04:07 GMT
From: Geoff Buckingham <geoffb@gti.noc.demon.net>
Message-Id: <199811110904.JAA10682@gti.noc.demon.net>
Subject: Re: SCSI Bus errors spewing on console...
In-Reply-To: <Pine.BSF.4.05.9811110012450.337-100000@thelab.hub.org> from The Hermit Hacker at "Nov 11, 98 00:15:51 am"
To: scrappy@hub.org (The Hermit Hacker)
Date: Wed, 11 Nov 1998 09:04:07 +0000 (GMT)
Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG
Reply-To: geoffb@demon.net
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
>
> Can someone tell me *what* this means? I have someone rushing to the
> office right now to reboot the machine, as there is nothing that I can do
> from here...is it a mis-configuration in my kernel (ie. I have to raise a
> limit somewhere?) or a driving going back (which one?) or something
> altogether different?
>
> I'm running a 3.0 system, still aout, but based on the cvs tree of
> ~3.0-RELEASE...I'd provide dmesg output, except I can't get into the
> machine to get it ;(
>
> It started all of a sudden...server was working fine all evening, then all
> of a sudden, loadavg went through the roof...figured I might have more
> response through the serial console, so switched to that, and saw this..
>
> thanks in advance for *any* help on this...
>
>
> ahc2: Bus Device Reset on A:1. 4 SCBs aborted
> ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET
> SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40
> ahc2: Bus Device Reset on A:1. 4 SCBs aborted
> ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET
> SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40
> ahc2: Bus Device Reset on A:1. 4 SCBs aborted
> ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET
> SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40
> ahc2: Bus Device Reset on A:1. 4 SCBs aborted
> ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET
> SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40
> ahc2: Bus Device Reset on A:1. 4 SCBs aborted
> ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET
> SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40
>
>
This looks an awful lot like a problemm we had with an adaptec 3940UW, our
problem went away when we switched to a 2940UW with a more recent revision
of the adaptec firmware.
--
GeoffB
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 01:07:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA23130
for freebsd-current-outgoing; Wed, 11 Nov 1998 01:07:09 -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 BAA23116
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 01:06:57 -0800 (PST)
(envelope-from daeron@Wit401305.student.utwente.nl)
Received: from localhost (daeron@localhost)
by Wit401305.student.utwente.nl (8.9.1/8.9.1) with ESMTP id KAA25952;
Wed, 11 Nov 1998 10:03:12 +0100 (CET)
(envelope-from daeron@Wit401305.student.utwente.nl)
Date: Wed, 11 Nov 1998 10:03:12 +0100 (CET)
From: Pascal Hofstee <daeron@Wit401305.student.utwente.nl>
To: Shawn Ramsey <shawn@cpl.net>
cc: oZZ!!! <osa@etrust.ru>, current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <19981110225440.C25741@cpl.net>
Message-ID: <Pine.BSF.4.05.9811111001370.25823-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 Tue, 10 Nov 1998, Shawn Ramsey wrote:
> I don't think 5.0 works on FreeBSD. I attempted it, and was only able to
> achieve a core dump executing setup.
>
> This was on a 2.2.7-RELEASE system.
As far as I know StarOffice 5.0 install-program tries to read the
commandline from /proc ... I think i saw some postings about this on
comps.os.unix.bsd.* (or something like that)
Pascal Hofstee
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 01:07:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA23223
for freebsd-current-outgoing; Wed, 11 Nov 1998 01:07:49 -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 BAA23210
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 01:07:44 -0800 (PST)
(envelope-from sthaug@nethelp.no)
From: sthaug@nethelp.no
Received: (qmail 10403 invoked by uid 1001); 11 Nov 1998 09:07:25 +0000 (GMT)
To: will@iki.fi
Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: Your message of "11 Nov 1998 10:50:10 +0200"
References: <863e7qbol9.fsf@not.oeno.com>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Wed, 11 Nov 1998 10:07:25 +0100
Message-ID: <10401.910775245@verdi.nethelp.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > 3. /usr/mdec is a silly-assed name. Who thought of it? What does it even
>
> The mdec name certainly isn't FreeBSD-specific, changing it would add
> to the difficulty of finding things based on a "general knowledge" of
> Unix-like systems.
Has it: FreeBSD, NetBSD, possibly OpenBSD.
Doesn't have it: Solaris 2, HP-UX, Digital Unix, BSD/OS, RedHat 5.2
I'm afraid there isn't much "general" about /usr/mdec.
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 Nov 11 01:27:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA24924
for freebsd-current-outgoing; Wed, 11 Nov 1998 01:27:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from morgan.angis.su.OZ.AU (morgan.angis.su.OZ.AU [129.78.25.38])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24902
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 01:27:24 -0800 (PST)
(envelope-from tonym@angis.usyd.edu.au)
Received: (from tonym@localhost) by morgan.angis.su.OZ.AU (8.8.7/8.6.6) id UAA29192; Wed, 11 Nov 1998 20:26:28 +1100 (EST)
Date: Wed, 11 Nov 1998 20:26:28 +1100 (EST)
From: Tony Maher <tonym@angis.usyd.edu.au>
Message-Id: <199811110926.UAA29192@morgan.angis.su.OZ.AU>
To: andreas@klemm.gtn.com
Subject: Re: Travan TR4 dump/restore
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> my personal experience was, that it's now safe with CAM to use
> blocksizes over 32 .... Since physio (if I remember right) was
> done in 32 blocks chunks even is you choose 64 or more ...
Justed dumped whole system again this time using 32 instead of 64.
dump 0uabf 32 /dev/nrsa0 /
dump 0uabf 32 /dev/nrsa0 /usr
dump 0uabf 32 /dev/nrsa0 /var
dump 0uabf 32 /dev/nrsa0 /n/01
dump 0uabf 32 /dev/nrsa0 /n/02
mt -f /dev/nrsa0 fsf 2
restore ivf /dev/nrsa0
and extracted subdirectory perfectly.
It definitely didnt like 64 blocks last nite.
Maybe something about this particular drive?!
sa0: <Seagate STT8000N 3.22> Removable Sequential Access SCSI2 device
Well as long as it backups up the files ;-)
I'll put the old drive back on later tonite if I get the chance
and try it again with 32 blocks.
Reading sa (4) man page
The block size used may be any value supported by the device,
the SCSI adapter and the system (usually between 1 byte and 64 Kbytes,
sometimes more).
Pretty sure the old drive under 2.2.-stable supported 64 (hard to test now).
thanks again.
tonym
.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 01:40:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA26070
for freebsd-current-outgoing; Wed, 11 Nov 1998 01:40:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26062
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 01:40:32 -0800 (PST)
(envelope-from archer@grape.carrier.kiev.ua)
Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111])
by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) with ESMTP id LAA12246;
Wed, 11 Nov 1998 11:40:09 +0200 (EET)
(envelope-from archer@grape.carrier.kiev.ua)
Received: (from uucp@localhost)
by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id LAA21102;
Wed, 11 Nov 1998 11:38:43 +0200 (EET)
(envelope-from archer@grape.carrier.kiev.ua)
Received: (from archer@localhost)
by grape.carrier.kiev.ua (8.9.1/8.9.1) id LAA14578;
Wed, 11 Nov 1998 11:26:20 +0200 (EET)
(envelope-from archer)
Message-ID: <19981111112620.20264@carrier.kiev.ua>
Date: Wed, 11 Nov 1998 11:26:20 +0200
From: Alexander Litvin <archer@lucky.net>
To: Greg Lehey <grog@lemis.com>
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <199811101456.QAA28210@grape.carrier.kiev.ua> <199811110038.CAA01861@grape.carrier.kiev.ua> <19981111133212.B20374@freebie.lemis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.88e
In-Reply-To: <19981111133212.B20374@freebie.lemis.com>; from Greg Lehey on Wed, Nov 11, 1998 at 01:32:12PM +1030
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Nov 11, 1998 at 01:32:12PM +1030, Greg Lehey wrote:
> > Brought up old kernel without kludge.
> >
> > It appears that memory corruption leading to 'daemons dying' may take
> > different forms. E.g., once it appears that sendmail continues to
> > fork for queue runs successfully, but when I do 'telnet localhost 25',
> > it just accepts connection, forks, changes proctitle ('startup with ...'),
> > and goes into some strange state -- no EHLO, just accepts all I type
> > in telnet and that's all. In that state kill -1 restarts sendmail ok.
> > Other time I exhaust memory, sendmail segfaults every child forked
> > for queue run, again restarts ok on SIGHUP. Once I even got in responce
> > to 'telnet localhost 25':
> >
> > Trying 127.0.0.1...
> > Connected to localhost.carrier.kiev.ua.
> > Escape character is '^]'.
> > archer... Recipient names must be specified
> >
> > As if I started sendmail without arguments on command prompt!
> >
> > I think it is ehough evidence that 'daemons dying' is caused by
> > memory corruption.
>
> Well, no, I had an alternative explanation: for me, this problem
> started with sendmail 8.9. I think I even went back and tried
> sendmail 8.8.<mumble> and it didn't cause any problems. It could be a
> bug in sendmail, possibly related to the config I'm using (it often
> refuses connections because it thinks some test on the domain name
> succeeds, when in fact it should have failed).
Oh, come on! Just installed 8.8.8 -- same stuff, dies on queue runs
and when accepting connection. And AFAIR the whole story had started
before 8.9 was released and merged to CURRENT.
And again, as I already wrote, I was able to make my specially written
test daemon to die in the same fassion. Should I mention that this
daemon does not make any DNS lookups?
Why people still try to pretend that this definitely kernel-related
problem may be explained by user-level bugs? Yes, inetd is buggy
(it was for ages), sendmail is buggy, etc. But on 2.x.x it seems
nobody ever saw anything similar.
And why Dima's kludge make it go away all at once?
>
> Greg
> --
> See complete headers for address, home page and phone numbers
> finger grog@lemis.com for PGP public key
---
I don't mind what Congress does, as long as they don't do it in the
streets and frighten the horses.
-- Victor Hugo
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 02:18:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA28669
for freebsd-current-outgoing; Wed, 11 Nov 1998 02:18:53 -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 CAA28664
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 02:18:49 -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 UAA26402;
Wed, 11 Nov 1998 20:09:27 +1000 (EST)
(envelope-from akm)
From: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Message-Id: <199811111009.UAA26402@zeus.theinternet.com.au>
Subject: Re: Is it soup yet? :-)
In-Reply-To: <9326.910765040@zippy.cdrom.com> from "Jordan K. Hubbard" at "Nov 10, 98 10:17:20 pm"
To: jkh@zippy.cdrom.com (Jordan K. Hubbard)
Date: Wed, 11 Nov 1998 20:09:26 +1000 (EST)
Cc: peter@netplex.com.au, mike@smith.net.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
+----[ Jordan K. Hubbard ]---------------------------------------------
| I can see we are simply of two minds on this issue. :) What do some of
| the others think?
I think I don't want you jumping up and down on my twitching corpse d8)
I think anything but /usr/mdec would be an improvement.
--
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 Nov 11 02:54:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA01299
for freebsd-current-outgoing; Wed, 11 Nov 1998 02:54:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01292
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 02:54:29 -0800 (PST)
(envelope-from regnauld@EU.org)
Received: from mail.prosa.dk ([192.168.100.254])
by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id LAA10588;
Wed, 11 Nov 1998 11:56:43 +0100 (CET)
(envelope-from regnauld@EU.org)
X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk
Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10])
by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id MAA16202;
Wed, 11 Nov 1998 12:17:14 +0100 (CET)
Received: (from uucp@localhost)
by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) with UUCP id LAA29759;
Wed, 11 Nov 1998 11:51:52 +0100 (CET)
Received: (from regnauld@localhost)
by stimpy.prosa.dk (8.9.1/8.9.1/stimpy-1.0) id LAA01085;
Wed, 11 Nov 1998 11:41:35 +0100 (CET)
(envelope-from regnauld)
Message-ID: <19981111114135.08028@stimpy.prosa.dk>
Date: Wed, 11 Nov 1998 11:41:35 +0100
From: Phil Regnauld <regnauld@EU.org>
To: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <19981110171205.19613@follo.net> <199811102352.CAA02240@tejblum.dnttm.rssi.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.88e
In-Reply-To: <199811102352.CAA02240@tejblum.dnttm.rssi.ru>; from Dmitrij Tejblum on Wed, Nov 11, 1998 at 02:52:35AM +0300
X-Operating-System: FreeBSD 3.0-CURRENT i386
Phone: +45 3336 4148
Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark
Organization: PROSA
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Dmitrij Tejblum writes:
> your RAM (sounds familiar, eh?). It is printed when your free swap space
> is less than your RAM size. Apparently, this is also to warn you that
> system will try hard to keep swap free. This is done by the code I
> pointed to in my previous posting. IMHO, the limit for free swap
> space is too large.
Well yes: I had 256/256 MB of swap free :-)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 03:09:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA02247
for freebsd-current-outgoing; Wed, 11 Nov 1998 03:09:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m1-55-dbn.dial-up.net [196.34.155.55])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02210;
Wed, 11 Nov 1998 03:08:15 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id NAA00886; Wed, 11 Nov 1998 13:05:24 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199811111105.NAA00886@ceia.nordier.com>
Subject: Re: Is it soup yet? :-)
In-Reply-To: <Pine.BSF.4.05.9811101903050.10145-100000@picnic.mat.net> from Chuck Robey at "Nov 10, 98 07:09:23 pm"
To: chuckr@mat.net (Chuck Robey)
Date: Wed, 11 Nov 1998 13:05:17 +0200 (SAT)
Cc: mike@smith.net.au, jkh@zippy.cdrom.com, current@FreeBSD.ORG,
peter@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
Chuck Robey wrote:
> I don't know enough about the bootblocks ... I just followed Mike's
> steps in getting myself installed ok, but is it possible to write a
> program that could probe the boot disk, read the bootblocks, and decide
> if they need upgrading ... and if they do, printing a warning message,
> and then refuse to install the new kernel?
>
> If this could be done, you know this will save a *lot* of complaints
> about insufficient warnings. You could warn until you're hoarse,
> they'll *still* miss it, unless the build process itself screams at
It'd be reasonably simple to do a dd/sh script to detect whether the
new (/sys/boot/i386/boot2) bootblocks are installed. But detecting
whether the old boot blocks are up to the task of loading boot/loader
is probably a non-starter.
Don't think one could really refuse to install the kernel. Though a
default option to preserve a /kernel.aout (if otherwise no aout kernel
would be available in /) may be an easy route, if we must protect
folks from themselves.
--
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 Nov 11 03:20:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA03193
for freebsd-current-outgoing; Wed, 11 Nov 1998 03:20:49 -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 DAA03184
for <current@freebsd.org>; Wed, 11 Nov 1998 03:20:48 -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 DAA21320
for <current@freebsd.org>; Wed, 11 Nov 1998 03:20:31 -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 DAA23991
for <current@freebsd.org>; Wed, 11 Nov 1998 03:20:30 -0800 (PST)
Received: (from gdonl@localhost)
by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id DAA00867
for current@freebsd.org; Wed, 11 Nov 1998 03:20:29 -0800 (PST)
Date: Wed, 11 Nov 1998 03:20:29 -0800 (PST)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199811111120.DAA00867@salsa.gv.tsc.tdk.com>
To: current@FreeBSD.ORG
Subject: patch for kern/7899 committed, proc structure size changed
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I just committed a patch for kern/7899 which fixes some security
issues with F_SETOWN, fixes some related bugs, and tidies things up
a bit. This patch increases the size of the proc and pgrp structures,
which affects some userland programs. When you next build your kernel
with /usr/src/sys/proc.h version 1.60 or newer, you'll also need to
update /usr/include/sys, and rebuild the following libraries and programs.
libkvm
lkm/vinum
fstat
gcore
gdb
ipfilter
ps
top
w
You should be able to update your includes by doing something like
"cd /usr/src/include; env MAKEOBJDIRPREFIX=/usr/obj/elf make install".
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 03:27:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA03935
for freebsd-current-outgoing; Wed, 11 Nov 1998 03:27:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03489
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 03:24:16 -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 MAA26435;
Wed, 11 Nov 1998 12:22:55 +0100 (CET)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Wed, 11 Nov 1998 12:22:55 +0100 (CET)
From: Andrzej Bialecki <abial@nask.pl>
X-Sender: abial@korin.warman.org.pl
To: Pascal Hofstee <daeron@Wit401305.student.utwente.nl>
cc: Shawn Ramsey <shawn@cpl.net>, oZZ!!! <osa@etrust.ru>, current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <Pine.BSF.4.05.9811111001370.25823-100000@Wit401305.student.utwente.nl>
Message-ID: <Pine.BSF.4.02A.9811111218510.20241-200000@korin.warman.org.pl>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-956434210-910783375=:20241"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.
--0-956434210-910783375=:20241
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Wed, 11 Nov 1998, Pascal Hofstee wrote:
>
>
> On Tue, 10 Nov 1998, Shawn Ramsey wrote:
>
> > I don't think 5.0 works on FreeBSD. I attempted it, and was only able to
> > achieve a core dump executing setup.
> >
> > This was on a 2.2.7-RELEASE system.
>
> As far as I know StarOffice 5.0 install-program tries to read the
> commandline from /proc ... I think i saw some postings about this on
> comps.os.unix.bsd.* (or something like that)
Yes, I've got the diffs against relatively fresh current. BTW, I asked
this question on -emulation, but got back a profound silence... Can we/
should we incorporate this patch, and hide it under a kernel option, say
PROCFS_CMDLINE? The life would be soooo easier for people new to our linux
emulation...
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/
-------------------- ~-+==---+-+ -------------------------------------
--0-956434210-910783375=:20241
Content-Type: TEXT/PLAIN; charset=US-ASCII; name=d
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.BSF.4.02A.9811111222550.20241@korin.warman.org.pl>
Content-Description:
Content-Disposition: attachment; filename=d
SW5kZXg6IHByb2Nmcy5oDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpSQ1Mg
ZmlsZTogL2hvbWUvbmN2cy9zcmMvc3lzL21pc2Nmcy9wcm9jZnMvcHJvY2Zz
Lmgsdg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjIwDQpkaWZmIC1jIC1yMS4y
MCBwcm9jZnMuaA0KKioqIHByb2Nmcy5oCTE5OTgvMDcvMDcgMDQ6MDg6NDQJ
MS4yMA0KLS0tIHByb2Nmcy5oCTE5OTgvMTEvMDYgMTI6MTY6NTkNCioqKioq
KioqKioqKioqKg0KKioqIDU2LDYyICoqKioNCiAgCVBub3RlLAkJLyogcHJv
Y2VzcyBub3RpZmllciAqLw0KICAJUG5vdGVwZywJLyogcHJvY2VzcyBncm91
cCBub3RpZmllciAqLw0KICAJUG1hcCwJCS8qIG1lbW9yeSBtYXAgKi8NCiEg
CVB0eXBlCQkvKiBleGVjdXRhYmxlIHR5cGUgKi8NCiAgfSBwZnN0eXBlOw0K
ICANCiAgLyoNCi0tLSA1Niw2MyAtLS0tDQogIAlQbm90ZSwJCS8qIHByb2Nl
c3Mgbm90aWZpZXIgKi8NCiAgCVBub3RlcGcsCS8qIHByb2Nlc3MgZ3JvdXAg
bm90aWZpZXIgKi8NCiAgCVBtYXAsCQkvKiBtZW1vcnkgbWFwICovDQohIAlQ
dHlwZSwJCS8qIGV4ZWN1dGFibGUgdHlwZSAqLw0KISAJUGNtZGxuCQkvKiBl
eGVjdXRhYmxlIHR5cGUgKi8NCiAgfSBwZnN0eXBlOw0KICANCiAgLyoNCioq
KioqKioqKioqKioqKg0KKioqIDE1NCwxNTkgKioqKg0KLS0tIDE1NSwxNjEg
LS0tLQ0KICBpbnQgcHJvY2ZzX2Rvc3RhdHVzIF9fUCgoc3RydWN0IHByb2Mg
Kiwgc3RydWN0IHByb2MgKiwgc3RydWN0IHBmc25vZGUgKnBmc3AsIHN0cnVj
dCB1aW8gKnVpbykpOw0KICBpbnQgcHJvY2ZzX2RvbWFwIF9fUCgoc3RydWN0
IHByb2MgKiwgc3RydWN0IHByb2MgKiwgc3RydWN0IHBmc25vZGUgKnBmc3As
IHN0cnVjdCB1aW8gKnVpbykpOw0KICBpbnQgcHJvY2ZzX2RvdHlwZSBfX1Ao
KHN0cnVjdCBwcm9jICosIHN0cnVjdCBwcm9jICosIHN0cnVjdCBwZnNub2Rl
ICpwZnNwLCBzdHJ1Y3QgdWlvICp1aW8pKTsNCisgaW50IHByb2Nmc19kb2Nt
ZGxuIF9fUCgoc3RydWN0IHByb2MgKiwgc3RydWN0IHByb2MgKiwgc3RydWN0
IHBmc25vZGUgKnBmc3AsIHN0cnVjdCB1aW8gKnVpbykpOw0KICANCiAgLyog
UmV0dXJuIDEgaWYgcHJvY2VzcyBoYXMgc3BlY2lhbCBrZXJuZWwgZGlnZ2lu
ZyBwcml2aWxlZ2VzICovDQogIGludCBwcm9jZnNfa21lbWFjY2VzcyBfX1Ao
KHN0cnVjdCBwcm9jICopKTsNCkluZGV4OiBwcm9jZnNfc3RhdHVzLmMNCj09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT0NClJDUyBmaWxlOiAvaG9tZS9uY3ZzL3Ny
Yy9zeXMvbWlzY2ZzL3Byb2Nmcy9wcm9jZnNfc3RhdHVzLmMsdg0KcmV0cmll
dmluZyByZXZpc2lvbiAxLjExDQpkaWZmIC1jIC1yMS4xMSBwcm9jZnNfc3Rh
dHVzLmMNCioqKiBwcm9jZnNfc3RhdHVzLmMJMTk5OC8wNy8xMSAwNzo0NTo0
NQkxLjExDQotLS0gcHJvY2ZzX3N0YXR1cy5jCTE5OTgvMTEvMDYgMTI6MjE6
MDgNCioqKioqKioqKioqKioqKg0KKioqIDE0NywxNDkgKioqKg0KLS0tIDE0
NywxOTEgLS0tLQ0KICANCiAgCXJldHVybiAoZXJyb3IpOw0KICB9DQorIA0K
KyBpbnQNCisgcHJvY2ZzX2RvY21kbG4oY3VycCwgcCwgcGZzLCB1aW8pDQor
IAlzdHJ1Y3QgcHJvYyAqY3VycDsNCisgCXN0cnVjdCBwcm9jICpwOw0KKyAJ
c3RydWN0IHBmc25vZGUgKnBmczsNCisgCXN0cnVjdCB1aW8gKnVpbzsNCisg
ew0KKyAJc3RydWN0IHNlc3Npb24gKnNlc3M7DQorIAlzdHJ1Y3QgdHR5ICp0
cDsNCisgCXN0cnVjdCB1Y3JlZCAqY3I7DQorIAljaGFyICpwczsNCisgCWNo
YXIgKnNlcDsNCisgCWludCBwaWQscHBpZCxwZ2lkLHNpZDsNCisgCWludCBp
Ow0KKyAJaW50IHhsZW47DQorIAlpbnQgZXJyb3I7DQorIAljaGFyIHBzYnVm
WzI1Nl07DQorIA0KKyAJaWYodWlvLT51aW9fcnchPVVJT19SRUFEKQ0KKyAJ
CXJldHVybihFT1BOT1RTVVBQKTsNCisgDQorIAlwaWQ9cC0+cF9waWQ7DQor
IAlwcGlkPXAtPnBfcHB0cj9wLT5wX3BwdHItPnBfcGlkOjA7DQorIAlwZ2lk
PXAtPnBfcGdycC0+cGdfaWQ7DQorIAlzZXNzPXAtPnBfcGdycC0+cGdfc2Vz
c2lvbjsNCisgCXNpZD1zZXNzLT5zX2xlYWRlciA/IHNlc3MtPnNfbGVhZGVy
LT5wX3BpZCA6IDA7DQorIAlwcz1wc2J1ZjsNCisgCWJjb3B5KHAtPnBfY29t
bSwgcHMsIE1BWENPTUxFTik7DQorIAlwc1tNQVhDT01MRU5dID0gJ1wwJzsN
CisgCXBzICs9IHN0cmxlbihwcyk7DQorIA0KKyAJeGxlbiA9IHBzIC0gcHNi
dWY7DQorIAl4bGVuIC09IHVpby0+dWlvX29mZnNldDsNCisgCXBzID0gcHNi
dWYgKyB1aW8tPnVpb19vZmZzZXQ7DQorIAl4bGVuID0gbWluKHhsZW4sIHVp
by0+dWlvX3Jlc2lkKTsNCisgCWlmICh4bGVuIDw9IDApDQorIAkJZXJyb3I9
MDsNCisgCWVsc2UNCisgCQllcnJvcj11aW9tb3ZlKHBzLHhsZW4sdWlvKTsN
CisgCXJldHVybihlcnJvcik7DQorIH0NCkluZGV4OiBwcm9jZnNfc3Vici5j
DQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09DQpSQ1MgZmlsZTogL2hvbWUvbmN2
cy9zcmMvc3lzL21pc2Nmcy9wcm9jZnMvcHJvY2ZzX3N1YnIuYyx2DQpyZXRy
aWV2aW5nIHJldmlzaW9uIDEuMjENCmRpZmYgLWMgLXIxLjIxIHByb2Nmc19z
dWJyLmMNCioqKiBwcm9jZnNfc3Vici5jCTE5OTcvMTIvMTIgMDM6MzM6NDMJ
MS4yMQ0KLS0tIHByb2Nmc19zdWJyLmMJMTk5OC8xMS8wNiAxMjowMDozOA0K
KioqKioqKioqKioqKioqDQoqKiogMTgxLDE4NiAqKioqDQotLS0gMTgxLDE4
NyAtLS0tDQogIAljYXNlIFB0eXBlOg0KICAJY2FzZSBQbWFwOg0KICAJY2Fz
ZSBQc3RhdHVzOg0KKyAJY2FzZSBQY21kbG46DQogIAkJcGZzLT5wZnNfbW9k
ZSA9IChWUkVBRCkgfA0KICAJCQkJKFZSRUFEID4+IDMpIHwNCiAgCQkJCShW
UkVBRCA+PiA2KTsNCioqKioqKioqKioqKioqKg0KKioqIDI4MCwyODUgKioq
Kg0KLS0tIDI4MSwyOTAgLS0tLQ0KICANCiAgCWNhc2UgUHR5cGU6DQogIAkJ
cnR2YWwgPSBwcm9jZnNfZG90eXBlKGN1cnAsIHAsIHBmcywgdWlvKTsNCisg
CQlicmVhazsNCisgDQorIAljYXNlIFBjbWRsbjoNCisgCQlydHZhbCA9IHBy
b2Nmc19kb2NtZGxuKGN1cnAsIHAsIHBmcywgdWlvKTsNCiAgCQlicmVhazsN
CiAgDQogIAlkZWZhdWx0Og0KSW5kZXg6IHByb2Nmc192bm9wcy5jDQo9PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09DQpSQ1MgZmlsZTogL2hvbWUvbmN2cy9zcmMv
c3lzL21pc2Nmcy9wcm9jZnMvcHJvY2ZzX3Zub3BzLmMsdg0KcmV0cmlldmlu
ZyByZXZpc2lvbiAxLjYxDQpkaWZmIC1jIC1yMS42MSBwcm9jZnNfdm5vcHMu
Yw0KKioqIHByb2Nmc192bm9wcy5jCTE5OTgvMDcvMTEgMDc6NDU6NDYJMS42
MQ0KLS0tIHByb2Nmc192bm9wcy5jCTE5OTgvMTEvMDYgMTI6MjE6NTANCioq
KioqKioqKioqKioqKg0KKioqIDEwMSwxMDYgKioqKg0KLS0tIDEwMSwxMDcg
LS0tLQ0KICAJeyBEVF9SRUcsIE4oIm5vdGVwZyIpLAlQbm90ZXBnLAlOVUxM
IH0sDQogIAl7IERUX1JFRywgTigibWFwIiksIAlQbWFwLAkJcHJvY2ZzX3Zh
bGlkbWFwIH0sDQogIAl7IERUX1JFRywgTigiZXR5cGUiKSwJUHR5cGUsCQlw
cm9jZnNfdmFsaWR0eXBlIH0sDQorIAl7IERUX1JFRywgTigiY21kbGluZSIp
LAlQY21kbG4sCQlOVUxMIH0sDQogICN1bmRlZiBODQogIH07DQogIHN0YXRp
YyBjb25zdCBpbnQgbnByb2NfdGFyZ2V0cyA9IHNpemVvZihwcm9jX3Rhcmdl
dHMpIC8gc2l6ZW9mKHByb2NfdGFyZ2V0c1swXSk7DQoqKioqKioqKioqKioq
KioNCioqKiA1NzMsNTc4ICoqKioNCi0tLSA1NzQsNTgwIC0tLS0NCiAgCWNh
c2UgUHN0YXR1czoNCiAgCWNhc2UgUG5vdGU6DQogIAljYXNlIFBub3RlcGc6
DQorIAljYXNlIFBjbWRsbjoNCiAgCQl2YXAtPnZhX25saW5rID0gMTsNCiAg
CQl2YXAtPnZhX3VpZCA9IHByb2NwLT5wX3VjcmVkLT5jcl91aWQ7DQogIAkJ
dmFwLT52YV9naWQgPSBwcm9jcC0+cF91Y3JlZC0+Y3JfZ2lkOw0K
--0-956434210-910783375=:20241--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 03:32:58 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA04271
for freebsd-current-outgoing; Wed, 11 Nov 1998 03:32:58 -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 DAA04266
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 03:32:53 -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.1/8.9.1/Spinner) with ESMTP id TAA10496;
Wed, 11 Nov 1998 19:28:24 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811111128.TAA10496@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Robert Nordier <rnordier@nordier.com>
cc: chuckr@mat.net (Chuck Robey), mike@smith.net.au, jkh@zippy.cdrom.com,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Sat, 11 Nov 1998 13:05:17 +0200."
<199811111105.NAA00886@ceia.nordier.com>
Date: Wed, 11 Nov 1998 19:28:23 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Robert Nordier wrote:
> Chuck Robey wrote:
>
> > I don't know enough about the bootblocks ... I just followed Mike's
> > steps in getting myself installed ok, but is it possible to write a
> > program that could probe the boot disk, read the bootblocks, and decide
> > if they need upgrading ... and if they do, printing a warning message,
> > and then refuse to install the new kernel?
> >
> > If this could be done, you know this will save a *lot* of complaints
> > about insufficient warnings. You could warn until you're hoarse,
> > they'll *still* miss it, unless the build process itself screams at
>
> It'd be reasonably simple to do a dd/sh script to detect whether the
> new (/sys/boot/i386/boot2) bootblocks are installed. But detecting
> whether the old boot blocks are up to the task of loading boot/loader
> is probably a non-starter.
>
> Don't think one could really refuse to install the kernel. Though a
> default option to preserve a /kernel.aout (if otherwise no aout kernel
> would be available in /) may be an easy route, if we must protect
> folks from themselves.
We could check that the /kernel (if it exists) that we are going to replace
is the same format as the one we've just built and fail (with a descriptive
message) if not.
Then let them choose to either install an elf kernel by using a different
target that renames the old kernel somewhere safe, or to override the
KERNFORMAT in /etc/make.conf and try and hang onto the old a.out format.
We can give explicit instructions on how to upgrade bootblocks, do
preliminary tests, etc by pointing them to a README file somewhere.
This way we will stop people getting their feet blown off by accident if
they were not paying attention. I think this is the safest way of forcing
the issue without hurting people.
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 03:43:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA05481
for freebsd-current-outgoing; Wed, 11 Nov 1998 03:43:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns.oeno.com (ns.oeno.com [194.100.99.145])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA05473
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 03:43:06 -0800 (PST)
(envelope-from will@ns.oeno.com)
Received: (qmail 7865 invoked by uid 1001); 11 Nov 1998 11:42:42 -0000
Date: 11 Nov 1998 11:42:42 -0000
Message-ID: <19981111114242.7862.qmail@ns.oeno.com>
From: Ville-Pertti Keinonen <will@iki.fi>
To: sthaug@nethelp.no
CC: jkh@zippy.cdrom.com, current@FreeBSD.ORG
In-reply-to: <10401.910775245@verdi.nethelp.no> (sthaug@nethelp.no)
Subject: Re: Is it soup yet? :-)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > > 3. /usr/mdec is a silly-assed name. Who thought of it? What does it even
> > The mdec name certainly isn't FreeBSD-specific, changing it would add
> > to the difficulty of finding things based on a "general knowledge" of
> > Unix-like systems.
> Has it: FreeBSD, NetBSD, possibly OpenBSD.
> Doesn't have it: Solaris 2, HP-UX, Digital Unix, BSD/OS, RedHat 5.2
Digital UNIX has /mdec. I doubt I'm the only person who associates
the name mdec with a directory that contains binary boot code images
for various disk/filesystem types and methods of boot. I don't object
to changing it, but simply wanted to point out that changing it can
add confusion.
I don't like the idea of putting boot block images in /boot, though.
(Unless they are magically mapped to where they are actually read from
on boot)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 04:54:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA13653
for freebsd-current-outgoing; Wed, 11 Nov 1998 04:54:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from picnic.mat.net (picnic.mat.net [206.246.122.117])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA13647
for <current@freebsd.org>; Wed, 11 Nov 1998 04:54:28 -0800 (PST)
(envelope-from chuckr@mat.net)
Received: from localhost (chuckr@localhost)
by picnic.mat.net (8.9.1/8.8.5) with ESMTP id WAA20331
for <current@freebsd.org>; Tue, 10 Nov 1998 22:27:07 -0500 (EST)
Date: Tue, 10 Nov 1998 22:27:07 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: current@FreeBSD.ORG
Subject: softupdates
Message-ID: <Pine.BSF.4.05.9811102224550.10145-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
I'm having an odd problem, and I want to see if maybe softupdates might
possibly be causing it. Can I turn off softupdates by just doing the
tunefs command, or do I have to remove the softupdates mods to the
kernel sources, and recompile/reinstall the kernel, in addition to the
tunefs command?
----------------------------+-----------------------------------------------
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 Nov 11 06:05:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA18232
for freebsd-current-outgoing; Wed, 11 Nov 1998 06:05:00 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from picnic.mat.net (picnic.mat.net [206.246.122.117])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18224
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 06:04:56 -0800 (PST)
(envelope-from chuckr@mat.net)
Received: from localhost (chuckr@localhost)
by picnic.mat.net (8.9.1/8.8.5) with ESMTP id JAA21493;
Wed, 11 Nov 1998 09:02:11 -0500 (EST)
Date: Wed, 11 Nov 1998 09:02:11 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: Julian Elischer <julian@whistle.com>, Peter Wemm <peter@netplex.com.au>,
Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <9940.910772319@zippy.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811110857490.10145-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 Wed, 11 Nov 1998, Jordan K. Hubbard wrote:
> > the ability to run on old bootblocks is how shall I say...
> > "required".
>
> Well, you have and have always had just two options the minute we pull
> the elf kernel switch: You switch customers to the 3-stage boot by
> dropping a /boot.conf file into place which calls /boot/loader (which
> you also install along with the 3.0 upgrade) or you relabel them so
> they look just like freshly installed 3.0.x systems; it's your choice
> whether you want to go for minimal impact or minimal difference.
Trouble is, with old bootblocks, that "drop boot.conf" trick doesn't
work, it just hangs. To get the elf kernel booted, you have to update
the bootblocks, *then* they can use both. Julian's request is dead as
it stands, you can't do that. To get the elf kernel, you need newer
bootblocks, which is why I suggested detecting the old ones, and maybe
refusing to install an elf kernel.
My own kernel, which I tested it on, didn't use klms or klds. Linking
doesn't matter, it's loading that's affected. Once the kernel gets into
place, that's when linking becomes an issue (if it is at all) right?
Not sure how to detect sufficiently new bootblocks ... it might not be
possible.
>
> - Jordan
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
>
----------------------------+-----------------------------------------------
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 Nov 11 06:22:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA19205
for freebsd-current-outgoing; Wed, 11 Nov 1998 06:22:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19199
for <current@freebsd.org>; Wed, 11 Nov 1998 06:22:23 -0800 (PST)
(envelope-from werner@btp1da.phy.uni-bayreuth.de)
Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id PAA08681 for current@freebsd.org; Wed, 11 Nov 1998 15:14:59 +0100 (MET)
Message-ID: <XFMail.981111151459.werner@btp1da.phy.uni-bayreuth.de>
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, 11 Nov 1998 15:14:59 +0100 (MET)
Organization: University of bayreuth
From: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
To: current@FreeBSD.ORG
Subject: make release broken
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
----------------------------------
"make release NODOC=YES NOPORTS=YES CHROOTDIR=/spare1/snap3 BUILDNAME=snap3"
died with:
....
....
loading kernel
rearranging symbols
text data bss dec hex
1462272 110592 110900 1683764 19b134
./dumpnlist /R/stage/boot.std/kernel > /tmp/mnt_xx/stand/symbols
kzip -v /R/stage/boot.std/kernel
/usr/lib/aout/kztail.o: Undefined symbol `_kzipmalloc' referenced from text
segment
/usr/lib/aout/kztail.o: Undefined symbol `_kzipfree' referenced from text
segment
kzip: ld returned 100
real kernel start address will be: 0x100000
real kernel end address will be: 0x29b134
*** Error code 3
Stop.
Werner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 07:13:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA24398
for freebsd-current-outgoing; Wed, 11 Nov 1998 07:13:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles229.castles.com [208.214.165.229])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24387
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 07:12:57 -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 VAA00601;
Tue, 10 Nov 1998 21:46:53 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811110546.VAA00601@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Peter Wemm <peter@netplex.com.au>
cc: Mike Smith <mike@smith.net.au>, "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 13:13:11 +0800."
<199811110513.NAA08424@spinner.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 10 Nov 1998 21:46:52 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Mike Smith wrote:
> > > I'm just wondering when we're going to switch the kernel to ELF and
> > > put /usr/src/sys/modules into the build path. I'd really like the
> > > /usr/bin/linux command to start doing the right thing on current 3.0
> > > SNAPshots, among other things. :-)
> >
> > I think we're about ready to do it. We probably want to insist that
> > people cut over to the new bootstrap first, perhaps with a HEADS UP
> > announcement from someone that hasn't cried wolf before.
>
> Oh, one other thing.. libdisk is built by doing a file2c of /usr/mdec/
> boot1/boot2 and compiling it in. It is using the *old* boot code, because
> libdisk is built before src/sys/boot in a 'make world'.
Looks like it needs to be fixed then.
> BTW; I really do not like moving the bootblock source files (boot0/1/2) to
> /boot; I think of /boot as an equivalent to the bootblocks.. /usr/mdec
> should be where they remain stored, and it's where disklabel expects them
> too.
That's just an "in progress" thing. /usr/mdec's days are numbered; the
only serious contender would be /usr/libdata/boot, and that's just as
bad as anything else on /usr.
--
\\ 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 Nov 11 07:24:25 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA25636
for freebsd-current-outgoing; Wed, 11 Nov 1998 07:24:25 -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 HAA25626
for <current@freebsd.org>; Wed, 11 Nov 1998 07:24:21 -0800 (PST)
(envelope-from lists@tar.com)
Received: from ppro.tar.com (ppro.tar.com [204.95.187.9])
by ns.tar.com (8.9.1/8.8.7) with SMTP id JAA04046
for <current@freebsd.org>; Wed, 11 Nov 1998 09:23:59 -0600 (CST)
Message-Id: <199811111523.JAA04046@ns.tar.com>
From: "Richard Seaman, Jr." <lists@tar.com>
To: "current@freebsd.org" <current@FreeBSD.ORG>
Date: Wed, 11 Nov 98 09:23:59 -0600
Reply-To: "Richard Seaman, Jr." <lists@tar.com>
X-Mailer: PMMail 1.92 For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: RFSIGSHARE ready?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
==================BEGIN FORWARDED MESSAGE==================
>From: "Richard Seaman, Jr." <lists@tar.com>
>To: "Brian Feldman" <green@unixhelp.org>
>Cc: "current@freebsd." <current@freebsd.>
>Date: Wed, 11 Nov 98 09:19:25 -0600
>Reply-To: "Richard Seaman, Jr." <lists@tar.com>
>Subject: Re: RFSIGSHARE ready?
>
On Tue, 10 Nov 1998 21:22:05 -0500 (EST), Brian Feldman wrote:
>This doesn't necessarily sound like it's the last bug to be fixed, but it
>sure could be. Thanks a bunch!
I have a ported version of linuxthreads that executes in FreeBSD.
However, I haven't incorporated your RFSIGSHARE patches into the
kernel, so I'm sure the signal handling is not quite right.
It doesn't use the clone call, it just uses rfork instead.
It also uses thr_sleep and thr_wakeup instead of the restart
signal handling that linuxthreads uses for suspend and restart.
This gets around some of the signal handling problems in FreeBSD
vs. linux clone, and looks like it might be speedier.
It still needs work, but if this is related to what you're trying
to accomplish, I'll tar it up and send it to you, if you want.
Three issues you need to be aware of, at least.
1) There is something wrong with the definition of
THREAD_STACK_START_ADDRESS in internals.h when executing in FreeBSD.
Setting:
#define THREAD_STACK_START_ADDRESS (0xe0000000)
works, but there's probably a better choice.
2) The mmap call in manager.c uses an option MAP_GROWSDOWN that
doesn't seem to exist in FreeBSD. The user stack appears way
too small (in fact I think its effectively zero length), since
I assume the MAP_GROWSDOWN option adds to the mmaped region on
demand as stack is needed.
What I have done, until I think of something better, is change
the call to this:
if (mmap((caddr_t)((char *)(new_thread+1) - STACK_SIZE),
STACK_SIZE, PROT_READ | PROT_WRITE,
MAP_PRIVATE | MAP_ANON | MAP_FIXED, -1, 0)
!= (caddr_t) -1) break;
3) There are numerous libc issues to be dealt with to make linuxthreads
work properly, though they are not unique to linuxthreads. The same
issues apply to any pthreads implementation other than the existing
FreeBSD libc_r version. When I have the issues clear in my own mind,
I was planning on posting a message.
===================END 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 Nov 11 07:53:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA28975
for freebsd-current-outgoing; Wed, 11 Nov 1998 07:53:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.webspan.net (mail.webspan.net [206.154.70.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28969
for <freebsd-current@freebsd.org>; Wed, 11 Nov 1998 07:53:29 -0800 (PST)
(envelope-from opsys@mail.webspan.net)
Received: from orion.webspan.net (orion.webspan.net [206.154.70.5])
by mail.webspan.net (WEBSPAN/970608) with SMTP id KAA10941
for <freebsd-current@freebsd.org>; Wed, 11 Nov 1998 10:53:12 -0500 (EST)
Date: Wed, 11 Nov 1998 10:53:09 -0500 (EST)
From: Open Systems Networking <opsys@mail.webspan.net>
X-Sender: opsys@orion.webspan.net
To: freebsd-current@FreeBSD.ORG
Subject: Softupdates in current problem..
Message-ID: <Pine.BSF.4.02.9811111049490.29257-100000@orion.webspan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Just tried rebuilding a kernel after the latest commits that needed libkvm
system includes and a few utils rebuilt and installed and was just
rebuilding the kernel to reboot and ffs_softdep.c breaks on:
../include -DKERNEL -include opt_global.h -elf
../../ufs/ffs/ffs_softdep.c
../../ufs/ffs/ffs_softdep.c: In function `allocdirect_merge':
../../ufs/ffs/ffs_softdep.c:1266: warning: int format, ufs_lbn_t arg (arg
4)
../../ufs/ffs/ffs_softdep.c: In function `softdep_setup_freeblocks':
../../ufs/ffs/ffs_softdep.c:1667: structure has no member named `lh_first'
../../ufs/ffs/ffs_softdep.c:1668: structure has no member named `lh_first'
../../ufs/ffs/ffs_softdep.c:2832: warning: int format, ufs_lbn_t arg (arg
3)
../../ufs/ffs/ffs_softdep.c:2837: warning: int format, long int arg (arg
3)
../../ufs/ffs/ffs_softdep.c: In function `handle_written_inodeblock':
../../ufs/ffs/ffs_softdep.c:3181: warning: int format, ufs_lbn_t arg (arg
4)
../../ufs/ffs/ffs_softdep.c:3188: warning: int format, long int arg (arg
4)
Chris
--
"You both seem to be ignoring the fact that the networking market is
driven by so-called 'IT professionals' these days, most of whom can't
tell the difference between an ARP and a carp." --Wes Peters
===================================| Open Systems FreeBSD Consulting.
FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186
-----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134
FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net
http://www.freebsd.org | Consulting, Network Engineering, Security
===================================| http://open-systems.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 08:38:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA05187
for freebsd-current-outgoing; Wed, 11 Nov 1998 08:38:48 -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 IAA05172
for <freebsd-current@freebsd.org>; Wed, 11 Nov 1998 08:38:42 -0800 (PST)
(envelope-from entropy@compufit.at)
Received: from unet3-167.univie.ac.at ([131.130.232.167] helo=darkstar)
by darkstar.psa.at with smtp (Exim 2.05 #1)
id 0zddO3-0001RP-00; Wed, 11 Nov 1998 17:44:56 +0100
Date: Wed, 11 Nov 1998 17:36:31 +0100
From: Alexander Sanda <entropy@compufit.at>
To: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: SSH 2.0.10 BUG? (!)
In-Reply-To: <Pine.BSF.4.05.9811090329010.5722-100000@gamefish.pcola.gulf.net>
References: <Pine.BSF.4.05.9811082130270.316-100000@PaLaDiN7.ml.org> <Pine.BSF.4.05.9811090329010.5722-100000@gamefish.pcola.gulf.net>
Message-Id: <3649BD0F21A.EE5FENTROPY@darkstar.psa.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver 1.24.16
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 9 Nov 1998 03:29:25 +0000 (GMT)
Phillip Salzman <psalzman@gamefish.pcola.gulf.net> wrote:
> make it +s
I don't think this is a good idea.
sshd is already started with root permissions (either standalone or from
inetd), so it's not necessary to make it suid root.
I have several FreeBSD boxen running sshd (both version 1 and 2); none
of the daemons is suid root, and they don't show the problem which is
subject of this thread.
--
# /AS/
# GNU is not Unix, BSD is. #
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 08:45:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA05896
for freebsd-current-outgoing; Wed, 11 Nov 1998 08:45:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from freebsd.scds.com (jseger.shore.net [204.167.102.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05869
for <current@freebsd.org>; Wed, 11 Nov 1998 08:45:05 -0800 (PST)
(envelope-from jseger@jseger.scds.com)
Received: from jseger.scds.com (localhost.scds.com [127.0.0.1])
by freebsd.scds.com (8.9.1/8.8.8) with ESMTP id LAA27758
for <current@freebsd.org>; Wed, 11 Nov 1998 11:44:07 -0500 (EST)
(envelope-from jseger@jseger.scds.com)
Message-Id: <199811111644.LAA27758@freebsd.scds.com>
To: current@FreeBSD.ORG
Subject: Problems building in a chroot'ed environment
Date: Wed, 11 Nov 1998 11:44:06 -0500
From: "Justin M. Seger" <jseger@freebsd.scds.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi guys. I've been having this problem doing a make world in a
chroot'ed environment for about a week now. The real world is
up-to-date and the /usr/src in the chroot'ed environment is also
up-to-date.
===> linux
cc -c -O -pipe -DLKM -DCOMPAT_LINUX -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -DACTUALLY_LKM_NOT_KERNEL -nostdinc -I- -I/usr/obj/aout/usr/src/lkm/linux -I/usr/obj/aout/usr/src/lkm/linux/@ -I/usr/obj/aout/usr/src/tmp/usr/include -aout -UKERNEL /usr/src/lkm/linux/../../sys/i386/linux/linux_genassym.c
cc -O -pipe -DLKM -DCOMPAT_LINUX -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -DACTUALLY_LKM_NOT_KERNEL -nostdinc -I- -I/usr/obj/aout/usr/src/lkm/linux -I/usr/obj/aout/usr/src/lkm/linux/@ -I/usr/obj/aout/usr/src/tmp/usr/include -aout -aout -o linux_genassym linux_genassym.o
./linux_genassym > linux_assym.h
Floating point exception - core dumped
*** Error code 136
If anyone has any ideas, please send them my way ASAP. I need to get
this working to do a new packages-current run.
Thanks,
-Justin Seger-
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 09:07:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA08076
for freebsd-current-outgoing; Wed, 11 Nov 1998 09:07:13 -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 JAA08071
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 09:07: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 MAA24134;
Wed, 11 Nov 1998 12:05:50 -0500 (EST)
Date: Wed, 11 Nov 1998 12:05:49 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Shawn Ramsey <shawn@cpl.net>
cc: oZZ!!! <osa@etrust.ru>, current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <19981110225440.C25741@cpl.net>
Message-ID: <Pine.BSF.4.05.9811111204370.24080-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 Tue, 10 Nov 1998, Shawn Ramsey wrote:
> > I try to install StarOffice-5.0 for linux.
>
> I don't think 5.0 works on FreeBSD. I attempted it, and was only able to
> achieve a core dump executing setup.
>
> This was on a 2.2.7-RELEASE system.
>
I tried this as well. In fact, this is with its included glibc. By the
way, this is why I've been working on LinuxThreads, software such as
StarOffice 5. The crash seems to be inside the initialization routines of
crtX or glibc itself.
Cheers,
Brian Feldman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 09:11:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA08450
for freebsd-current-outgoing; Wed, 11 Nov 1998 09:11:16 -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 JAA08438
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 09:10:59 -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 MAA24182;
Wed, 11 Nov 1998 12:09:33 -0500 (EST)
Date: Wed, 11 Nov 1998 12:09:33 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Andrzej Bialecki <abial@nask.pl>
cc: Pascal Hofstee <daeron@Wit401305.student.utwente.nl>,
Shawn Ramsey <shawn@cpl.net>, oZZ!!! <osa@etrust.ru>,
current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <Pine.BSF.4.02A.9811111218510.20241-200000@korin.warman.org.pl>
Message-ID: <Pine.BSF.4.05.9811111208380.24080-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, 11 Nov 1998, Andrzej Bialecki wrote:
> Yes, I've got the diffs against relatively fresh current. BTW, I asked
> this question on -emulation, but got back a profound silence... Can we/
> should we incorporate this patch, and hide it under a kernel option, say
> PROCFS_CMDLINE? The life would be soooo easier for people new to our linux
> emulation...
>
> Andrzej Bialecki
>
Send it here! I need to get StarOffice 5 working as much as possible, so I
may continue LinuxThreads work with a Real Program.
Cheers,
Brian Feldman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 09:27:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA10358
for freebsd-current-outgoing; Wed, 11 Nov 1998 09:27:29 -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 JAA10243
for <current@freebsd.org>; Wed, 11 Nov 1998 09:26: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 MAA24396
for <current@freebsd.org>; Wed, 11 Nov 1998 12:25:51 -0500 (EST)
Date: Wed, 11 Nov 1998 12:25:50 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: current@FreeBSD.ORG
Subject: Re: RFSIGSHARE ready? (fwd)
Message-ID: <Pine.BSF.4.05.9811111225130.24080-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
Sorry, this message should have gotten sent correctly the first time :(
freebsd itself is not a domain though, so here it is.
---------- Forwarded message ----------
Date: Wed, 11 Nov 1998 12:23:46 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
To: "Richard Seaman, Jr." <lists@tar.com>
Cc: "current@freebsd." <current@freebsd>
Subject: Re: RFSIGSHARE ready?
Thanks, you're helping a lot here! We're trying to accomplish different
things, and imho mine is the only correct way. We need to be entirely
binary-compatible with Linux (not FreeBSD binaries, but be able to run
Linux binaries, static, unmodified), and this will have to be done in the
kernel. I'm going to take you're information and work on LinuxThreads
more. Since you know the code, here's your assignment(should you choose to
accept it;):
using the original LinuxThreads code (NO mods except for debug
info) and compiling with a Linux cross-devel toolchain, I need you're
assistance figuring out what's wrong here. In some programs, the program
getsto spinning in pthread_handle_create and CANNOT be killed, for some
reason or another. In other cases, tsleep (invoked from sigsuspend) is
sleeping forever, of course wakeup works but it's still in a while() loop
so it just continues. In this manner, both situations are unkillable, no
matter WHAT signal is sent (I sent all of them to test by the way)
Example:
294 green 89 0 1068K 440K RUN 22:15 93.77% 93.77% ex5
{"/home/green"}$ for i in USR1 USR2 ILL SEGV KILL BUS
> do kill -$i 294
> done
294 green 105 0 1068K 440K RUN 23:15 96.21% 96.21% ex5
Think you can figure this all out, at least somewhat? I'll see
about the stack allocation MAP_GROWSDOWN, look how it's done in sys/vm. It
would be helpful if you (or anyone else reading this) would help out as
much as possible. For instance, if someone would figure out why I am not
able to signal these processes for instance (perhaps a stupid coding bug
about initialization of a member of struct proc/(user/procsig), and I'm
unintentionally creating an artificial signal blocking situation? Thanks
in advance to all who will help.
Cheers,
Brian Feldman
And here are the latest patches, which now have parent signaling
implemented:
--- src/sys/i386/linux/linux_dummy.c.orig Thu Nov 6 14:28:52 1997
+++ src/sys/i386/linux/linux_dummy.c Wed Nov 11 11:20:58 1998
@@ -212,13 +212,6 @@
}
int
-linux_clone(struct proc *p, struct linux_clone_args *args)
-{
- printf("Linux-emul(%d): clone() not supported\n", p->p_pid);
- return ENOSYS;
-}
-
-int
linux_uname(struct proc *p, struct linux_uname_args *args)
{
printf("Linux-emul(%d): uname() not supported\n", p->p_pid);
--- src/sys/i386/linux/linux_misc.c.orig Mon Oct 5 08:40:42 1998
+++ src/sys/i386/linux/linux_misc.c Wed Nov 11 11:26:15 1998
@@ -41,6 +41,7 @@
#include <sys/resourcevar.h>
#include <sys/stat.h>
#include <sys/sysctl.h>
+#include <sys/unistd.h>
#include <sys/vnode.h>
#include <sys/wait.h>
#include <sys/time.h>
@@ -558,6 +559,55 @@
if (p->p_retval[1] == 1)
p->p_retval[0] = 0;
return 0;
+}
+
+#define CLONE_VM 0x100
+#define CLONE_FS 0x200
+#define CLONE_FILES 0x400
+#define CLONE_SIGHAND 0x800
+#define CLONE_PID 0x1000
+
+int
+linux_clone(struct proc *p, struct linux_clone_args *args)
+{
+ int error, ff = RFPROC, top;
+ struct proc *p2;
+
+#ifdef SMP
+ printf("linux_clone(%d): does not work with SMP\n", p->p_pid);
+ return (EOPNOTSUPP);
+#else
+#ifdef DEBUG_CLONE
+ if (args->flags & CLONE_PID)
+ printf("linux_clone(%d): CLONE_PID not yet supported\n",
p->p_pid);
+ if (args->flags & CLONE_FS)
+ printf("linux_clone(%d): CLONE_FS not yet supported\n", p->p_pid);
+#endif
+ if (args->flags & CLONE_VM)
+ ff |= RFMEM;
+ if (args->flags & CLONE_SIGHAND)
+ ff |= RFSIGSHARE;
+ if (!(args->flags & CLONE_FILES))
+ ff |= RFFDG;
+ if (error = fork1(p, ff))
+ return error;
+ p2 = pfind(p->p_retval[0]);
+ if (p2 == 0)
+ return ESRCH;
+ if (args->stack) {
+ copyin(args->stack, &top, 4);
+ p2->p_md.md_regs->tf_esp = (int)args->stack;
+ p2->p_md.md_regs->tf_eip = top;
+ }
+ p2->p_sigparent = args->flags & 0x000000ff;
+#ifdef DEBUG_CLONE
+ copyin(args->stack + 4, &top, 4);
+ printf("linux_clone: pids %d, %d; child eip=%#x, esp=%#x,
*esp=%#x\n",
+ p->p_pid, p2->p_pid, p2->p_md.md_regs->tf_eip,
p2->p_md.md_regs->tf_esp,
+ top);
+#endif
+ return 0;
+#endif
}
/* XXX move */
--- src/sys/i386/linux/linux_proto.h.orig Fri Jul 10 18:30:04 1998
+++ src/sys/i386/linux/linux_proto.h Wed Nov 11 11:20:58 1998
@@ -2,7 +2,7 @@
* System call prototypes.
*
* DO NOT EDIT-- this file is automatically generated.
- * created from Id: syscalls.master,v 1.11 1998/06/09 03:28:14 bde
Exp
+ * created from Id: syscalls.master,v 1.12 1998/07/10 22:30:08 jkh
Exp
*/
#ifndef _LINUX_SYSPROTO_H_
@@ -301,7 +301,8 @@
struct linux_sigcontext * scp; char scp_[PAD_(struct
linux_sigcontext *)];
};
struct linux_clone_args {
- register_t dummy;
+ int flags; char flags_[PAD_(int)];
+ void * stack; char stack_[PAD_(void *)];
};
struct linux_newuname_args {
struct linux_newuname_t * buf; char buf_[PAD_(struct
linux_newuname_t *)];
--- src/sys/i386/linux/linux_syscall.h.orig Fri Jul 10 18:30:06 1998
+++ src/sys/i386/linux/linux_syscall.h Wed Nov 11 11:20:58 1998
@@ -2,7 +2,7 @@
* System call numbers.
*
* DO NOT EDIT-- this file is automatically generated.
- * created from Id: syscalls.master,v 1.11 1998/06/09 03:28:14 bde
Exp
+ * created from Id: syscalls.master,v 1.12 1998/07/10 22:30:08 jkh
Exp
*/
#define LINUX_SYS_linux_setup 0
--- src/sys/i386/linux/linux_sysent.c.orig Fri Jul 10 18:30:07 1998
+++ src/sys/i386/linux/linux_sysent.c Wed Nov 11 11:20:59 1998
@@ -2,7 +2,7 @@
* System call switch table.
*
* DO NOT EDIT-- this file is automatically generated.
- * created from Id: syscalls.master,v 1.11 1998/06/09 03:28:14 bde
Exp
+ * created from Id: syscalls.master,v 1.12 1998/07/10 22:30:08 jkh
Exp
*/
#include "opt_compat.h"
@@ -134,7 +134,7 @@
{ 5, (sy_call_t *)linux_ipc }, /* 117 = linux_ipc
*/
{ 1, (sy_call_t *)fsync }, /* 118 = fsync */
{ 1, (sy_call_t *)linux_sigreturn }, /* 119 =
linux_sigreturn */
- { 0, (sy_call_t *)linux_clone }, /* 120 =
linux_clone */
+ { 2, (sy_call_t *)linux_clone }, /* 120 =
linux_clone */
{ 2, (sy_call_t *)setdomainname }, /* 121 =
setdomainname */
{ 1, (sy_call_t *)linux_newuname }, /* 122 =
linux_newuname */
{ 3, (sy_call_t *)linux_modify_ldt }, /* 123 =
linux_modify_ldt */
--- src/sys/i386/linux/syscalls.master.orig Fri Jul 10 18:30:08 1998
+++ src/sys/i386/linux/syscalls.master Wed Nov 11 11:20:59 1998
@@ -171,7 +171,7 @@
caddr_t ptr); }
118 NOPROTO LINUX { int fsync(int fd); }
119 STD LINUX { int linux_sigreturn(struct linux_sigcontext
*scp); }
-120 STD LINUX { int linux_clone(void); }
+120 STD LINUX { int linux_clone(int flags, void *stack); }
121 NOPROTO LINUX { int setdomainname(char *name, \
int len); }
122 STD LINUX { int linux_newuname(struct linux_newuname_t
*buf); }
--- src/sys/kern/kern_fork.c.orig Mon Nov 9 10:07:41 1998
+++ src/sys/kern/kern_fork.c Wed Nov 11 11:24:06 1998
@@ -325,6 +325,17 @@
p2->p_cred->p_refcnt = 1;
crhold(p1->p_ucred);
+ if (flags & RFSIGSHARE) {
+ p2->p_sig->ps_refcnt++;
+ } else {
+ p2->p_sig = malloc(sizeof(struct procsig), M_TEMP,
M_WAITOK);
+ p2->p_sig->ps_refcnt = 1;
+ bcopy(&p1->p_sig->ps_begincopy, &p2->p_sig->ps_begincopy,
+ (unsigned)&p1->p_sig->ps_endcopy -
+ (unsigned)&p1->p_sig->ps_begincopy);
+ p2->p_sigacts = &p2->p_sig->ps_sigacts;
+ }
+
/* bump references to the text vnode (for procfs) */
p2->p_textvp = p1->p_textvp;
if (p2->p_textvp)
--- src/sys/kern/kern_exit.c.orig Wed Nov 11 05:03:54 1998
+++ src/sys/kern/kern_exit.c Wed Nov 11 11:23:05 1998
@@ -324,6 +324,14 @@
/* move this to cpu_exit */
p->p_addr->u_pcb.pcb_savacc.faddr = (float *)NULL;
#endif
+
+ if (p->p_sigparent && p->p_pptr->p_pid != 1) {
+ struct kill_args ka;
+ ka.signum = p->p_sigparent;
+ ka.pid = p->p_pptr->p_pid;
+ kill(p, &ka);
+ }
+
/*
* Clear curproc after we've done all operations
* that could block, and before tearing down the rest
@@ -339,6 +347,9 @@
FREE(p->p_limit, M_SUBPROC);
p->p_limit = NULL;
}
+
+ if (--p->p_sig->ps_refcnt == 0)
+ free(p->p_sig, M_TEMP);
/*
* Finally, call machine-dependent code to release the remaining
--- src/sys/kern/init_main.c.orig Thu Oct 15 13:09:19 1998
+++ src/sys/kern/init_main.c Wed Nov 11 11:20:59 1998
@@ -83,6 +83,7 @@
static struct pgrp pgrp0;
struct proc proc0;
static struct pcred cred0;
+static struct procsig procsig0;
static struct filedesc0 filedesc0;
static struct plimit limit0;
static struct vmspace vmspace0;
@@ -415,6 +416,10 @@
p->p_ucred = crget();
p->p_ucred->cr_ngroups = 1; /* group 0 */
+ /* Create procsig. */
+ p->p_sig = &procsig0;
+ p->p_sig->ps_refcnt = 2;
+
/* Create the file descriptor table. */
fdp = &filedesc0;
p->p_fd = &fdp->fd_fd;
@@ -461,11 +466,12 @@
#endif
/*
- * We continue to place resource usage info and signal
- * actions in the user struct so they're pageable.
+ * We continue to place resource usage info in the user struct so
+ * it's pageable.
*/
p->p_stats = &p->p_addr->u_stats;
- p->p_sigacts = &p->p_addr->u_sigacts;
+
+ p->p_sigacts = &p->p_sig->ps_sigacts;
/*
* Charge root for one process.
--- src/sys/sys/proc.h.orig Wed Nov 11 05:56:05 1998
+++ src/sys/sys/proc.h Wed Nov 11 11:22:17 1998
@@ -47,6 +47,7 @@
#include <sys/rtprio.h> /* For struct rtprio. */
#include <sys/select.h> /* For struct selinfo. */
#include <sys/signal.h>
+#include <sys/signalvar.h>
#ifndef KERNEL
#include <sys/time.h> /* For structs itimerval, timeval.
*/
#endif
@@ -78,6 +79,16 @@
int pg_jobc; /* # procs qualifying pgrp for job control
*/
};
+struct procsig {
+#define ps_begincopy ps_sigmask
+ sigset_t ps_sigmask; /* Current signal mask. */
+ sigset_t ps_sigignore; /* Signals being ignored. */
+ sigset_t ps_sigcatch; /* Signals being caught by user. */
+ struct sigacts ps_sigacts;
+#define ps_endcopy ps_refcnt
+ int ps_refcnt;
+};
+
/*
* Description of a process.
*
@@ -164,17 +175,18 @@
char p_pad3[2]; /* padding for alignment */
register_t p_retval[2]; /* syscall aux returns */
struct sigiolst p_sigiolst; /* list of sigio sources */
+ int p_sigparent; /* signal to parent on exit */
/* End area that is zeroed on creation. */
#define p_endzero p_startcopy
/* The following fields are all copied upon creation in fork. */
-#define p_startcopy p_sigmask
-
- sigset_t p_sigmask; /* Current signal mask. */
- sigset_t p_sigignore; /* Signals being ignored. */
- sigset_t p_sigcatch; /* Signals being caught by user. */
+#define p_startcopy p_sig
+ struct procsig *p_sig;
+#define p_sigmask p_sig->ps_sigmask
+#define p_sigignore p_sig->ps_sigignore
+#define p_sigcatch p_sig->ps_sigcatch
u_char p_priority; /* Process priority. */
u_char p_usrpri; /* User-priority based on p_cpu and
p_nice. */
char p_nice; /* Process "nice" value. */
--- src/sys/sys/unistd.h.orig Sat Mar 28 06:51:01 1998
+++ src/sys/sys/unistd.h Wed Nov 11 11:20:59 1998
@@ -186,6 +186,7 @@
#define RFCENVG (1<<11) /* UNIMPL zero plan9 `env space'
*/
#define RFCFDG (1<<12) /* zero fd table */
#define RFTHREAD (1<<13) /* enable kernel thread support */
+#define RFSIGSHARE (1<<14) /* share signal masks */
#define RFPPWAIT (1<<31) /* parent sleeps until child exits (vfork)
*/
#endif /* !_POSIX_SOURCE */
--- src/sys/sys/user.h.orig Wed Jul 15 16:18:00 1998
+++ src/sys/sys/user.h Wed Nov 11 11:20:59 1998
@@ -102,7 +102,6 @@
struct user {
struct pcb u_pcb;
- struct sigacts u_sigacts; /* p_sigacts points here (use it!)
*/
struct pstats u_stats; /* p_stats points here (use it!)
*/
/*
--- src/sys/sys/proc.h.orig Wed Nov 11 05:56:05 1998
+++ src/sys/sys/proc.h Wed Nov 11 11:22:17 1998
@@ -47,6 +47,7 @@
#include <sys/rtprio.h> /* For struct rtprio. */
#include <sys/select.h> /* For struct selinfo. */
#include <sys/signal.h>
+#include <sys/signalvar.h>
#ifndef KERNEL
#include <sys/time.h> /* For structs itimerval, timeval.
*/
#endif
@@ -78,6 +79,16 @@
int pg_jobc; /* # procs qualifying pgrp for job control
*/
};
+struct procsig {
+#define ps_begincopy ps_sigmask
+ sigset_t ps_sigmask; /* Current signal mask. */
+ sigset_t ps_sigignore; /* Signals being ignored. */
+ sigset_t ps_sigcatch; /* Signals being caught by user. */
+ struct sigacts ps_sigacts;
+#define ps_endcopy ps_refcnt
+ int ps_refcnt;
+};
+
/*
* Description of a process.
*
@@ -164,17 +175,18 @@
char p_pad3[2]; /* padding for alignment */
register_t p_retval[2]; /* syscall aux returns */
struct sigiolst p_sigiolst; /* list of sigio sources */
+ int p_sigparent; /* signal to parent on exit */
/* End area that is zeroed on creation. */
#define p_endzero p_startcopy
/* The following fields are all copied upon creation in fork. */
-#define p_startcopy p_sigmask
-
- sigset_t p_sigmask; /* Current signal mask. */
- sigset_t p_sigignore; /* Signals being ignored. */
- sigset_t p_sigcatch; /* Signals being caught by user. */
+#define p_startcopy p_sig
+ struct procsig *p_sig;
+#define p_sigmask p_sig->ps_sigmask
+#define p_sigignore p_sig->ps_sigignore
+#define p_sigcatch p_sig->ps_sigcatch
u_char p_priority; /* Process priority. */
u_char p_usrpri; /* User-priority based on p_cpu and
p_nice. */
char p_nice; /* Process "nice" value. */
--- src/sys/vm/vm_glue.c.orig Tue Oct 13 04:24:43 1998
+++ src/sys/vm/vm_glue.c Wed Nov 11 11:20:59 1998
@@ -235,8 +235,6 @@
* p_stats; zero the rest of p_stats (statistics).
*/
p2->p_stats = &up->u_stats;
- p2->p_sigacts = &up->u_sigacts;
- up->u_sigacts = *p1->p_sigacts;
bzero(&up->u_stats.pstat_startzero,
(unsigned) ((caddr_t) &up->u_stats.pstat_endzero -
(caddr_t) &up->u_stats.pstat_startzero));
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 09:36:25 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA11659
for freebsd-current-outgoing; Wed, 11 Nov 1998 09:36:25 -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 JAA11648
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 09:36: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 KAA25893;
Wed, 11 Nov 1998 10:35:37 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id KAA17377; Wed, 11 Nov 1998 10:35:35 -0700
Date: Wed, 11 Nov 1998 10:35:35 -0700
Message-Id: <199811111735.KAA17377@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: Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <9326.910765040@zippy.cdrom.com>
References: <199811110605.OAA08762@spinner.netplex.com.au>
<9326.910765040@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 can see we are simply of two minds on this issue. :) What do some of
> the others think?
Leave it in /usr/mdec. Like Peter said, /usr/mdec is a 'storage' place,
and generally speaking you don't 'store' crap on the / partition.
Since it shouldn't go in /, then there's no sense in renaming it 'just
because we can' in /usr since it would be gratuitous.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 09:40:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12011
for freebsd-current-outgoing; Wed, 11 Nov 1998 09:40: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 JAA12006
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 09:40:32 -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 KAA25932;
Wed, 11 Nov 1998 10:39:50 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id KAA17419; Wed, 11 Nov 1998 10:39:43 -0700
Date: Wed, 11 Nov 1998 10:39:43 -0700
Message-Id: <199811111739.KAA17419@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: jkh@zippy.cdrom.com (Jordan K. Hubbard), peter@netplex.com.au,
mike@smith.net.au, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <199811110756.SAA04980@cimlogic.com.au>
References: <9326.910765040@zippy.cdrom.com>
<199811110756.SAA04980@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
> I've read Peter's concerns about systems that were disklabelled ages
> ago, but I question the length of time we are expected to support disk
> allocations from the past. Let's move forward...
Umm, this issue isn't 'disklabellede disks from the past', it was 'size
of the / partition'. The smaller the root partition, the less likely
you'll corrupt it and the less more quickly you can fsck the darn thing
at boot time and get on with fixing crashes when they happen.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 09:41:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12079
for freebsd-current-outgoing; Wed, 11 Nov 1998 09:41:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles229.castles.com [208.214.165.229])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12068
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 09:40:57 -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 JAA03898;
Wed, 11 Nov 1998 09:39:01 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811111739.JAA03898@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Chuck Robey <chuckr@mat.net>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Julian Elischer <julian@whistle.com>,
Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 09:02:11 EST."
<Pine.BSF.4.05.9811110857490.10145-100000@picnic.mat.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 09:39:00 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On Wed, 11 Nov 1998, Jordan K. Hubbard wrote:
>
> > > the ability to run on old bootblocks is how shall I say...
> > > "required".
> >
> > Well, you have and have always had just two options the minute we pull
> > the elf kernel switch: You switch customers to the 3-stage boot by
> > dropping a /boot.conf file into place which calls /boot/loader (which
> > you also install along with the 3.0 upgrade) or you relabel them so
> > they look just like freshly installed 3.0.x systems; it's your choice
> > whether you want to go for minimal impact or minimal difference.
>
> Trouble is, with old bootblocks, that "drop boot.conf" trick doesn't
> work, it just hangs. To get the elf kernel booted, you have to update
> the bootblocks, *then* they can use both. Julian's request is dead as
> it stands, you can't do that. To get the elf kernel, you need newer
> bootblocks, which is why I suggested detecting the old ones, and maybe
> refusing to install an elf kernel.
This isn't entirely true, actually. *Some*sytems* don't like loading
the loader with the old bootblocks. I'd really appreciate it if
someone with one of these systems (yes, how about you Chuck?) actually
sat down and worked out *why* attempting to read zero bytes from the
disk spins forever. If all it takes to fix the problem is to pad the
string table > 0, that's easy to deal with.
--
\\ 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 Nov 11 09:41:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12122
for freebsd-current-outgoing; Wed, 11 Nov 1998 09:41:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles229.castles.com [208.214.165.229])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12116
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 09:41:33 -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 JAA03920;
Wed, 11 Nov 1998 09:40:22 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811111740.JAA03920@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: oZZ!!! <osa@etrust.ru>
cc: current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-reply-to: Your message of "Wed, 11 Nov 1998 08:53:05 +0300."
<Pine.BSF.4.05.9811110847250.3304-100000@ozz.etrust.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 09:40:21 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> Hello!
> I try to install StarOffice-5.0 for linux.
Please post emulation-related questions to freebsd-emulation.
StarOffice 5 does not run on FreeBSD. Don't waste your time.
> It want libc-2.0.7.so & libthread-0.7.so....
> ( as said in README glibc-2.0.7-7-7.i386.rpm)
> I think its a RedHat distribution, but how can operate with
> that rpm-filez ??
> Plz help
>
> Rgdz,
> Osokin Sergey aka oZZ,
> osa@etrust.ru
> http://www.freebsd.org.ru
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
--
\\ 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 Nov 11 09:45:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12551
for freebsd-current-outgoing; Wed, 11 Nov 1998 09:45:35 -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 JAA12546
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 09:45:34 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id JAA18589
for current@FreeBSD.ORG; Wed, 11 Nov 1998 09:45:17 -0800 (PST)
(envelope-from obrien)
Message-ID: <19981111094517.B18529@nuxi.com>
Date: Wed, 11 Nov 1998 09:45:17 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
Reply-To: obrien@NUXI.com
References: <199811110605.OAA08762@spinner.netplex.com.au> <9326.910765040@zippy.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <9326.910765040@zippy.cdrom.com>; from Jordan K. Hubbard on Tue, Nov 10, 1998 at 10:17:20PM -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 can see we are simply of two minds on this issue. :) What do some of
> the others think?
While I agree with the silly name, I think we are approaching another
gratuitous change. It is our history, /usr/mdec is where people are used
to looking, ...
--
-- David (obrien@NUXI.ucdavis.edu -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 Wed Nov 11 09:49:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA13065
for freebsd-current-outgoing; Wed, 11 Nov 1998 09:49:43 -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 JAA12999
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 09:49:26 -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 MAA24685;
Wed, 11 Nov 1998 12:48:12 -0500 (EST)
Date: Wed, 11 Nov 1998 12:48:12 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Mike Smith <mike@smith.net.au>
cc: oZZ!!! <osa@etrust.ru>, current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <199811111740.JAA03920@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811111246460.24080-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, 11 Nov 1998, Mike Smith wrote:
> >
> > Hello!
> > I try to install StarOffice-5.0 for linux.
>
> Please post emulation-related questions to freebsd-emulation.
>
> StarOffice 5 does not run on FreeBSD. Don't waste your time.
Correction: does not run on FreeBSD _yet_. I am actively working on
getting LinuxThreads working entirely on FreeBSD, and am much closer than
before. Don't expect LinuxThreaded programs to not work for much longer.
>
> > It want libc-2.0.7.so & libthread-0.7.so....
> > ( as said in README glibc-2.0.7-7-7.i386.rpm)
> > I think its a RedHat distribution, but how can operate with
> > that rpm-filez ??
> > Plz help
> >
> > Rgdz,
> > Osokin Sergey aka oZZ,
> > osa@etrust.ru
> > http://www.freebsd.org.ru
> >
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-current" in the body of the message
> >
>
> --
> \\ 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
>
Cheers,
Brian Feldman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 09:53:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA13421
for freebsd-current-outgoing; Wed, 11 Nov 1998 09:53:02 -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 JAA13415
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 09:53:00 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id JAA18691;
Wed, 11 Nov 1998 09:51:51 -0800 (PST)
(envelope-from obrien)
Message-ID: <19981111095151.C18529@nuxi.com>
Date: Wed, 11 Nov 1998 09:51:51 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: sthaug@nethelp.no
Cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
Reply-To: obrien@NUXI.com
References: <863e7qbol9.fsf@not.oeno.com> <10401.910775245@verdi.nethelp.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <10401.910775245@verdi.nethelp.no>; from sthaug@nethelp.no on Wed, Nov 11, 1998 at 10:07:25AM +0100
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 mdec name certainly isn't FreeBSD-specific, changing it would add
> > to the difficulty of finding things based on a "general knowledge" of
> > Unix-like systems.
>
> Has it: FreeBSD, NetBSD, possibly OpenBSD.
AND SunOS, Ultrix. I.e. BSD derived systems.
(yes we've still got SunOS and Ultrix systems)
--
-- David (obrien@NUXI.ucdavis.edu -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 Wed Nov 11 09:54:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA13531
for freebsd-current-outgoing; Wed, 11 Nov 1998 09:54:44 -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 JAA13522
for <current@freebsd.org>; Wed, 11 Nov 1998 09:54:41 -0800 (PST)
(envelope-from lists@tar.com)
Received: from ppro.tar.com (ppro.tar.com [204.95.187.9])
by ns.tar.com (8.9.1/8.8.7) with SMTP id LAA21780
for <current@freebsd.org>; Wed, 11 Nov 1998 11:54:19 -0600 (CST)
Message-Id: <199811111754.LAA21780@ns.tar.com>
From: "Richard Seaman, Jr." <lists@tar.com>
To: "current@freebsd.org" <current@FreeBSD.ORG>
Date: Wed, 11 Nov 98 11:54:19 -0600
Reply-To: "Richard Seaman, Jr." <lists@tar.com>
X-Mailer: PMMail 1.92 For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: RFSIGSHARE ready?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
==================BEGIN FORWARDED MESSAGE==================
>From: "Richard Seaman, Jr." <lists@tar.com>
>To: "Brian Feldman" <green@unixhelp.org>
>Cc: "current@freebsd." <current@freebsd>
>Date: Wed, 11 Nov 98 11:51:43 -0600
>Reply-To: "Richard Seaman, Jr." <lists@tar.com>
>Subject: Re: RFSIGSHARE ready?
>
On Wed, 11 Nov 1998 12:23:46 -0500 (EST), Brian Feldman wrote:
>In some programs, the program
>getsto spinning in pthread_handle_create and CANNOT be killed, for some
>reason or another. In other cases, tsleep (invoked from sigsuspend) is
>sleeping forever, of course wakeup works but it's still in a while() loop
>so it just continues. In this manner, both situations are unkillable, no
>matter WHAT signal is sent (I sent all of them to test by the way)
I found a similar problem when I first invoked a threaded program
using linux threads. The problem went away when I moved
THREAD_STACK_START_ADDRESS down to 0xe0000000.
===================END 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 Nov 11 09:57:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA13793
for freebsd-current-outgoing; Wed, 11 Nov 1998 09:57:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles229.castles.com [208.214.165.229])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13779
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 09:57:50 -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 JAA04059;
Wed, 11 Nov 1998 09:56:01 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811111756.JAA04059@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Ville-Pertti Keinonen <will@iki.fi>
cc: sthaug@nethelp.no, jkh@zippy.cdrom.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "11 Nov 1998 11:42:42 GMT."
<19981111114242.7862.qmail@ns.oeno.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 09:56:01 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> > > > 3. /usr/mdec is a silly-assed name. Who thought of it? What does it even
>
> > > The mdec name certainly isn't FreeBSD-specific, changing it would add
> > > to the difficulty of finding things based on a "general knowledge" of
> > > Unix-like systems.
>
> > Has it: FreeBSD, NetBSD, possibly OpenBSD.
> > Doesn't have it: Solaris 2, HP-UX, Digital Unix, BSD/OS, RedHat 5.2
>
> Digital UNIX has /mdec. I doubt I'm the only person who associates
> the name mdec with a directory that contains binary boot code images
> for various disk/filesystem types and methods of boot. I don't object
> to changing it, but simply wanted to point out that changing it can
> add confusion.
>
> I don't like the idea of putting boot block images in /boot, though.
> (Unless they are magically mapped to where they are actually read from
> on boot)
I think the issue is perhaps a little over-emotional. The images total
8k in three files, and really don't justify or warrant a directory all
to themselves *anywhere*.
--
\\ 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 Nov 11 10:04:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA14372
for freebsd-current-outgoing; Wed, 11 Nov 1998 10:04: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 KAA14366
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 10:04:32 -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 NAA24944;
Wed, 11 Nov 1998 13:04:10 -0500 (EST)
Date: Wed, 11 Nov 1998 13:04:10 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: "Richard Seaman, Jr." <lists@tar.com>
cc: "current@freebsd.org" <current@FreeBSD.ORG>
Subject: Re: RFSIGSHARE ready?
In-Reply-To: <199811111754.LAA21780@ns.tar.com>
Message-ID: <Pine.BSF.4.05.9811111302240.24080-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, 11 Nov 1998, Richard Seaman, Jr. wrote:
> ==================BEGIN FORWARDED MESSAGE==================
> >From: "Richard Seaman, Jr." <lists@tar.com>
> >To: "Brian Feldman" <green@unixhelp.org>
> >Cc: "current@freebsd." <current@freebsd>
> >Date: Wed, 11 Nov 98 11:51:43 -0600
> >Reply-To: "Richard Seaman, Jr." <lists@tar.com>
> >Subject: Re: RFSIGSHARE ready?
> >
>
> On Wed, 11 Nov 1998 12:23:46 -0500 (EST), Brian Feldman wrote:
>
> >In some programs, the program
> >getsto spinning in pthread_handle_create and CANNOT be killed, for some
> >reason or another. In other cases, tsleep (invoked from sigsuspend) is
> >sleeping forever, of course wakeup works but it's still in a while() loop
> >so it just continues. In this manner, both situations are unkillable, no
> >matter WHAT signal is sent (I sent all of them to test by the way)
>
> I found a similar problem when I first invoked a threaded program
> using linux threads. The problem went away when I moved
> THREAD_STACK_START_ADDRESS down to 0xe0000000.
Creating an unkillable process? this is _NOT_ a good thing.
And should not be able to be accomplished under any circumstances. Tho, I
can think of now, ttywait (I believe) is one such.
Cheers,
Brian Feldman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 10:10:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA14909
for freebsd-current-outgoing; Wed, 11 Nov 1998 10:10:37 -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 KAA14900
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 10:10:34 -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 LAA26225;
Wed, 11 Nov 1998 11:09:52 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id LAA17690; Wed, 11 Nov 1998 11:09:51 -0700
Date: Wed, 11 Nov 1998 11:09:51 -0700
Message-Id: <199811111809.LAA17690@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: Ville-Pertti Keinonen <will@iki.fi>, sthaug@nethelp.no,
jkh@zippy.cdrom.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <199811111756.JAA04059@dingo.cdrom.com>
References: <19981111114242.7862.qmail@ns.oeno.com>
<199811111756.JAA04059@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
> I think the issue is perhaps a little over-emotional. The images total
> 8k in three files, and really don't justify or warrant a directory all
> to themselves *anywhere*.
More than that. I've got 101K in mine, which includes boot1, boot2,
fbsdboot.exe, a bunch of com files for ether-booting, and rawboot.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 10:17:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA15659
for freebsd-current-outgoing; Wed, 11 Nov 1998 10:17:37 -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 KAA15641
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 10:17:30 -0800 (PST)
(envelope-from lists@tar.com)
Received: from ppro.tar.com (ppro.tar.com [204.95.187.9])
by ns.tar.com (8.9.1/8.8.7) with SMTP id MAA03748;
Wed, 11 Nov 1998 12:17:01 -0600 (CST)
Message-Id: <199811111817.MAA03748@ns.tar.com>
From: "Richard Seaman, Jr." <lists@tar.com>
To: "Brian Feldman" <green@unixhelp.org>
Cc: "current@freebsd.org" <current@FreeBSD.ORG>
Date: Wed, 11 Nov 98 12:17:01 -0600
Reply-To: "Richard Seaman, Jr." <lists@tar.com>
X-Mailer: PMMail 1.92 For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: RFSIGSHARE ready?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 11 Nov 1998 13:04:10 -0500 (EST), Brian Feldman wrote:
>On Wed, 11 Nov 1998, Richard Seaman, Jr. wrote:
>
>> ==================BEGIN FORWARDED MESSAGE==================
>> >From: "Richard Seaman, Jr." <lists@tar.com>
>> >To: "Brian Feldman" <green@unixhelp.org>
>> >Cc: "current@freebsd." <current@freebsd>
>> >Date: Wed, 11 Nov 98 11:51:43 -0600
>> >Reply-To: "Richard Seaman, Jr." <lists@tar.com>
>> >Subject: Re: RFSIGSHARE ready?
>> >
>>
>> On Wed, 11 Nov 1998 12:23:46 -0500 (EST), Brian Feldman wrote:
>>
>> >In some programs, the program
>> >getsto spinning in pthread_handle_create and CANNOT be killed, for some
>> >reason or another. In other cases, tsleep (invoked from sigsuspend) is
>> >sleeping forever, of course wakeup works but it's still in a while() loop
>> >so it just continues. In this manner, both situations are unkillable, no
>> >matter WHAT signal is sent (I sent all of them to test by the way)
>>
>> I found a similar problem when I first invoked a threaded program
>> using linux threads. The problem went away when I moved
>> THREAD_STACK_START_ADDRESS down to 0xe0000000.
>
>Creating an unkillable process? this is _NOT_ a good thing.
>And should not be able to be accomplished under any circumstances. Tho, I
>can think of now, ttywait (I believe) is one such.
Actually it wasn't unkillable, it just hung in pthread_handle_create.
FYI, I just tried recompiling with the stack size set to
INITIAL_STACK_SIZE, instead of STACK_SIZE, and it also hangs in
pthread_handle_create. I still think you have compatibility
problems between the linux mmap with MAP_GROWSDOWN and the
FreeBSD mmap.
The stack in question here is the stack of the new threads, not the
intial process. linuxthreads manages this stack, and I'm not convinced
the FreeBSD kernel does, without additional coaxing.
Also, FYI I just tried a make buildworld with your patches (before
the newest ones you just sent), and it breaks in
/usr/src/bin/ps/keyword.c in lines 161-163.
Also, FYI I have had trouble applying the patches you have posted to
list, since it appears that some of the lines are getting wrapped.
I don't think that my mailer is doing this, possibly this is
happening either in your mailer, or in the -current list remailer.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 10:18:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA15836
for freebsd-current-outgoing; Wed, 11 Nov 1998 10:18:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from relay.hq.tis.com (relay.hq.tis.com [192.94.214.100])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15819
for <freebsd-current@freebsd.org>; Wed, 11 Nov 1998 10:18:36 -0800 (PST)
(envelope-from stevek@tis.com)
Received: by relay.hq.tis.com; id NAA08163; Wed, 11 Nov 1998 13:24:13 -0500 (EST)
Received: from clipper.hq.tis.com(10.33.1.2) by relay.hq.tis.com via smap (4.1)
id xma008108; Wed, 11 Nov 98 13:23:19 -0500
Received: from mufasa.va.tis.com (mufasa.va.tis.com [192.168.10.18])
by clipper.hq.tis.com (8.9.1/8.9.1) with ESMTP id NAA18342;
Wed, 11 Nov 1998 13:15:08 -0500 (EST)
Received: from localhost (stevek@localhost)
by mufasa.va.tis.com (8.8.7/8.8.7) with SMTP id NAA15877;
Wed, 11 Nov 1998 13:24:41 -0500 (EST)
(envelope-from stevek@mufasa.va.tis.com)
Date: Wed, 11 Nov 1998 13:24:41 -0500 (EST)
From: Steve Kiernan <stevek@tis.com>
To: freebsd-current@FreeBSD.ORG
cc: Alexander Litvin <archer@lucky.net>
Subject: Re: The infamous dying daemons bug
Message-ID: <Pine.BSF.3.96.981111131906.15869B-100000@mufasa.va.tis.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, 9 Nov 1998, Alexander Litvin wrote:
>
> Though, when I tried to stress the system with 'make -j# buildworld',
> something weird happened. Particularily, I got a corrupt ld built.
> It happened several times -- sometimes it is a bootstrap ld, and
> as a result my buildworld just stopped (ld running indefinitely).
> The last time it was a dynamic ld which I 'managed' to install into
> /usr/libexec/elf/ld (made installworld) -- I was forced to extract
> binary from 3.0-RELEASE distribution, since my system was not
> able to build anything.
>
> It may or may not be related to kernel stuff. The fact that it always
> happen to ld makes me feel that it may be just build process coruption.
>
> Anybody seen things like this? Anybody interested in details?
I've seen similar things happen on my 3.0-RELEASE system. If all running
programs can remain paged in, the system runs fine. Once processes start
getting swapped out, I get corruption when pages are paged in from swap.
Header files get an occasional random character changed in them,
shared libraries crash with SEGV errors (once libc.so became
'corrupted' and I had to reboot), builds fail randomly and the system
basically goes into chaos and occassionally crashes.
Since there's no a.out gdb compiled I went to compile the latest gdb with
a.out support, but it blew up in syntax errors. What version of gdb will
actually build on 3.0 with a.out support so I can debug my crash dumps?
--
Stephen Kiernan
stevek@tis.com
TIS Labs at Network Associates, Inc.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 10:23:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA16256
for freebsd-current-outgoing; Wed, 11 Nov 1998 10:23:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from feral-gw.feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16250
for <freebsd-current@freebsd.org>; Wed, 11 Nov 1998 10:23:13 -0800 (PST)
(envelope-from mjacob@feral.com)
Received: from localhost (mjacob@localhost)
by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id KAA21740
for <freebsd-current@freebsd.org>; Wed, 11 Nov 1998 10:22:16 -0800
Date: Wed, 11 Nov 1998 10:22:16 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
X-Sender: mjacob@feral-gw
Reply-To: mjacob@feral.com
To: freebsd-current@FreeBSD.ORG
Subject: fsck -f vs. fsck -p -f
Message-ID: <Pine.LNX.4.02.9811111018170.21231-100000@feral-gw>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I just had a really peculiar occurrence:
root fsck -p /dev/rda2a
/dev/rda2a: clean, 5789274 free (76594 frags, 714085 blocks, 0.9% fragmentation)
quarm.feral.com > root fsck -f -p /dev/rda2a
/dev/rda2a: UNKNOWN FILE TYPE I=16212
/dev/rda2a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
quarm.feral.com > root fsck -f /dev/rda2a
** /dev/rda2a
** Last Mounted on /mnt2
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
175499 files, 2782327 used, 5789274 free (76594 frags, 714085 blocks, 0.9%
fragmentation)
There was absolutely no peep of errors here...
Now- this may be a flakey disk and it's under a shakey development
framework, but I thought I'd ask if there's anything *but* busted h/w or
I/O layer goop that could have this happen...
(this is a Fibre Channel disk on a PLDA (private loop direct attach) to my
2x180 SMP FreeBSD system- I'm filling this disk with lots and lots of
random files to test some filesystem stuff..)
-matt
quarm.feral.com > uname -a
FreeBSD quarm.feral.com 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Wed Nov 11
10:04:31 PST 1998
mjacob@quarm.feral.com:/freebsd/FreeBSD-current/src/sys/compile/QUARM
i386
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 10:35:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA17839
for freebsd-current-outgoing; Wed, 11 Nov 1998 10:35: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 KAA17825
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 10:35:15 -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 NAA25440;
Wed, 11 Nov 1998 13:34:44 -0500 (EST)
Date: Wed, 11 Nov 1998 13:34:44 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: "Richard Seaman, Jr." <lists@tar.com>
cc: "current@freebsd.org" <current@FreeBSD.ORG>
Subject: Re: RFSIGSHARE ready?
In-Reply-To: <199811111817.MAA03748@ns.tar.com>
Message-ID: <Pine.BSF.4.05.9811111324110.24080-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, 11 Nov 1998, Richard Seaman, Jr. wrote:
> On Wed, 11 Nov 1998 13:04:10 -0500 (EST), Brian Feldman wrote:
>
> >On Wed, 11 Nov 1998, Richard Seaman, Jr. wrote:
> >
> >> ==================BEGIN FORWARDED MESSAGE==================
> >> >From: "Richard Seaman, Jr." <lists@tar.com>
> >> >To: "Brian Feldman" <green@unixhelp.org>
> >> >Cc: "current@freebsd." <current@freebsd>
> >> >Date: Wed, 11 Nov 98 11:51:43 -0600
> >> >Reply-To: "Richard Seaman, Jr." <lists@tar.com>
> >> >Subject: Re: RFSIGSHARE ready?
> >> >
> >>
> >> On Wed, 11 Nov 1998 12:23:46 -0500 (EST), Brian Feldman wrote:
> >>
> >> >In some programs, the program
> >> >getsto spinning in pthread_handle_create and CANNOT be killed, for some
> >> >reason or another. In other cases, tsleep (invoked from sigsuspend) is
> >> >sleeping forever, of course wakeup works but it's still in a while() loop
> >> >so it just continues. In this manner, both situations are unkillable, no
> >> >matter WHAT signal is sent (I sent all of them to test by the way)
> >>
> >> I found a similar problem when I first invoked a threaded program
> >> using linux threads. The problem went away when I moved
> >> THREAD_STACK_START_ADDRESS down to 0xe0000000.
> >
> >Creating an unkillable process? this is _NOT_ a good thing.
> >And should not be able to be accomplished under any circumstances. Tho, I
> >can think of now, ttywait (I believe) is one such.
>
> Actually it wasn't unkillable, it just hung in pthread_handle_create.
> FYI, I just tried recompiling with the stack size set to
> INITIAL_STACK_SIZE, instead of STACK_SIZE, and it also hangs in
> pthread_handle_create. I still think you have compatibility
> problems between the linux mmap with MAP_GROWSDOWN and the
> FreeBSD mmap.
>
> The stack in question here is the stack of the new threads, not the
> intial process. linuxthreads manages this stack, and I'm not convinced
> the FreeBSD kernel does, without additional coaxing.
>
> Also, FYI I just tried a make buildworld with your patches (before
> the newest ones you just sent), and it breaks in
> /usr/src/bin/ps/keyword.c in lines 161-163.
>
> Also, FYI I have had trouble applying the patches you have posted to
> list, since it appears that some of the lines are getting wrapped.
> I don't think that my mailer is doing this, possibly this is
> happening either in your mailer, or in the -current list remailer.
>
>
Yeah, a few lines in ps need to be deleted. That should be it.
Brian Feldman
begin 644 linux_clone.patch.gz
M'XL("%>\238"`VQI;G5X7V-L;VYE+G!A=&-H`.T:V7+;1O(9_(JV79%)\1#`
M2Q05N^Q(E*V-KA)EQUN)"PL!`Q$1"6!QR%*\_O?M[AF`('A(R;YLI:PR"7"F
MNZ>GI^]QL]F$.+)WXH=XQ^L,^CM3ST_OY;?II+/90\MN!9%WHUU-4C@+[@#Z
M8'2'[<&PUP9C;V^W4J_7'R6A_2(<QC8,_#=LZ\/>@+`'E3=OH-DVV@VC`W5Z
M]N'-FPI\JT`%/#^I-"49>QKXHAHG46HG$$:!#=MA`]3O`HAI13<Q;--WK=+\
M6FD"_H414G*KST\(KBEFZ;3Z@U,;@B1:`S](($[#,(@2X?SF/V]`V'P=FJ'G
MU/8EA4@D:>3#Z.Q\_,\QCGVK-"M-8D^MG?K6[!'V&&2!/?A:@4WL2:*/L;?I
M_&9>;&?'=QKX<([<0`_TP;"K#[MM>0`;CT]2*)]>?VCTYJ?7-?#0ZOB]RT?W
MPO/M:>H(^)$H1B(.TL@6=U;4FKPNS\:)E:P:?HCM9$H3]<6)U/?BQ%F!<><'
MCE@Q_L7R5BV0>#.&)O9[O0'QW^OM-7H]W@']>2Y46<QX]'?6]%?C,[QZ!0:>
MFE8<UG$8]'V)H[0$?]:_5>K(NR-<SQ=P<')^-C(_GFKZO:'KY?&C,8ZW5XP?
MGXQHJKL\-3Y^]_[MV2%.#I8G+XX/Y4(Z\4!*6O\?;*C^M5)G>?@)B"@*H@:X
M+N[Y\NCB\OR@`4D0[DN(1<+M?9:`YR)O,#Z]D#"9JA<98EUW`A&SHG\)HEOX
MXB430BHK>[T@Y>KH_.+L_&K\X>*"9EZ(:2SR!0]'/WUX9[(\%/MXG+2AYFMW
M:N'NMN;"PCUJ:_G*H9BY!['!$C>N<S1^PC)'XR>L\D+XCN=N7NWC*:V&Y_0?
M.JC3T>DCW"E]*B+AT/C]V\M1`?/9ZIV1FM:*J$>'[PI8K#2H,"X>K%$-27T8
M6ATC3ROPL(UP(:JR4UVTL:)T"0A-KD!B-+X\>+^T0W0M]FT-?6Q=LX/PP?.+
MXPW80L5M0)<H:V&;5ILYK9F#:Q)0XIHB#I&;*AY8K8"X'MPC\+DU8`233PD=
M>S>A%0DTHE>P*$7]7N<_U]U?K[[+.X`Z=!=VL<:\AH!Z$\,/3@,_^V!/O*D#
MR.RK'U[<-P`W*5^VU1NI&VU1*5Q#L5]X7=[WNIDX)%+(85EM"WY2#<MXO[,-
MGSY]@EEP)V![9W-H0S>3!*V)C&U'D0?_2*=@Z&`,AAU]J'>?$-L4B4=2$XQJ
M];8*;;`-XX<X$3.PK>D4F$#R$(JX17,\?W@.Z)5@='A\A>PG$R\&UYL*P*>5
M)L',2CS"?8`;X8O(0@MO88JQ#78DZ`>X43#3CITA4`Q$P+@ULW#%J('\M8A#
M9&Q'[^_H>Z!W*`LSNG"-86UT'P)*]ZF$VHK0[@[*K-UFF0W@]]N))`0D?Z"H
MZ?JDD.;)\=F'3R8F/^CUK\[-]R8+IZ-3T*_38\`"TA:B"2J]'?B)N$]@6XOM
M<%^S)U8$^&;^>O'VT*RNA:Y]QI#Z#3\20EN*3IC9H?G?>+0C,P'.,LDV4?\U
MMBRU%K^KU<B4/Q/07>`YQ!$;M.*)WA6<G%[-@B^^%!*YK^4=Y].TX^O45=3Q
M;=6.B]"TW$:%5\>X7N7[3U#YG,A?5WH_G5V+Z.^K\3*7TG*%-Y7DT&>%FO[H
M&:&+SS+NY2/:?=H1,8T5)[3WM!.*,7VR)Y!8UU/Q]W5,*IU_'H2):0>SD`J)
MYRP;H],EZ<@'>Z6OT&M`-7XP:3VV-BEK+[3A6T/3-(P\AK&+L7D^3NL@HE%"
M=.,'OX@TH-2&Q]8@Y,Y-13U"9<R]?+GY)$4]I*&OI,'N+\=OZSF^G$#<.N*V
M_R(NK,!%I7=0,SR?O-0<VT#LQ:F->\_<W)Q`.U\^GU,4.BLIS`),$A[,J9/,
M:71R&H79]5E#2=G66>A@HX66B&PV46.7@Z-\L!IJ&N=REN-0S`J3J+9/B0\J
MD79VSH%5NAV4`Y5;K%95?G,RR#UM?'6X`%52H?4Q%<,N4VGB\:^A(BL2BG\,
M67\,DGFC"-L`&31ETBUY;1LK=[6@.%4.C]OTVH#?<A'Q.L+/"+77,)$IS_JH
MBH%7[KF@%+<B\OG+I)*DV![A[A:>('GJ8==85H4R:ED!NGD4YNRHW:/&`CT,
MI0$R449/Z,CZQK6Y(C`PS=#L:!),L?(Q:"HE&,R;@7(:K&FR:F%>F,G21LO+
M"WS$BF*]3EG.-Z"2N`2%B\U0@P.[&GM_B,`MM@-PNM:`4_-J='I!SU_>'E^=
M_\P5TLIE).,X>4WE275+<I[!7&-VYM,$5BF+V/,90M:JJ8\S/FZW1`%+`X*"
MYF:PG%R)4\M.8F2QM+B:8`%5ZBAV=";7Z2S$HL056*#9(L8J#N.C`#8;;BRA
M_+&&)1FY<4VZ*DF50.ZH\),LR9]TF+)2G8_5UJB@N/?R?*&@3'IOB$&TU]VD
M@A*UK(*=H=XKJF!7JF"W@>&851#WRP469P"X4SM,F93:%K%,#JKY.C5#^[J%
M'S.V[BS;;KDT3C6Q.PTL<LYG'TY.<+-9::=4-5RL=[>V5/L"_9TJ)>$9==*D
M9BK]N_70X7-.?6OQ,=Y:+3KN=$;"7:"831.A5TNTY2Q2HU;#UJU5*YXT?F$B
M<C`5Z'3L-.)6E>6B)X<OXB7*Q*%82"E4$%(*Y`5^+%&2"6[8#E*LG:_1>&X;
M8/GX*E`M2$\LK+MO$/N+SXH3B3B1XN_LL?B[NXT]%0*.+D<C*:*I-_,2LK/Q
MAY^HET;6KFGS*=R<$C#S+X7;;(:K#%$U1#0W$B(_@,R6V8W,MW_D^93G-62R
M.+/L">:[34>$>(QT8#8I/"I&)%!.L5`[(H^-FUQ68QQ.3)HMWA-0HYE:Q*B-
M>T-C;XT:%U`WA])!A\2(W]*-4M?8L_.&XTT4\I<^+];X9.E+CBV`DV>E9-2A
M_D-I3GK![+F,3!FS(V);G[\M+R!/C[^79^]F<6C9(GLB@&RA]V0/O=_`7$2&
MBCP,H"+8T8U(JJPA\_'F:SLR_9LH2,.8?3'9-O\$7:;)=1HYX+P[VU-+YHGA
M/!YLS7<['U]T\]S,A0(QT@FN'D@$D1<FZ!YEO2'=B.N04]PJ"DF2=AT>=_"'
MZ^`OM?V^T<"#KW?[N/^VO$50C2&IN$U2W%\$4#*#09[U,YR2'+/[!4ACZP:K
M&=\-V#;)>5A3B8@.GTP9)YGQ-!91=APQN_J'EVC&(>++DJG^IU9;2572\)*7
M<8$NF5_N9$DM9'PJNEP>W4>VPW(46X#*@UCAR!8@E\)=T0,<8-*%W$=!D%!;
M%LCKD1*(&,OZHH'3AR:RIL-BA.KU\UA3-.TY4MFHVT-CMW!MM,LJO[OZVB@)
M(R]H35[+.NLHR&6K9EB2I5LC=%AVL@H'9^BH5B*QGJRX:I(3\VLKV0C[>71Y
M-CI9<YU47A<UCF:B.VO:`'K#%\6#U&X2PR[?/NWN-0QY\\DMK/#&_#VXMMFB
M7TC3A7^GUA3K'(HT[/+HY!"(M30*IDSW&V>,!2=()OYU?D-43)=`J@>6,K>H
M1?B&F3F5)?DHKWZ01AS&I3B`QI4+*6'@/`9#QADS;(SQD9B5$\YJ+-M*[,D*
M)-M*;R8)7#^P766X<E^0*?M".E?88I8XYBY,-0;G`W1#QSYM1S5'E!M#-P&!
M"];<'*A]PM5<OTM9/)9SF,VK9B<5+QIF'9;3^;7]>9]/'W\XM`$Z'3RO&W]&
MTF.S+_0K\[N-#$U5EF"E]ZH]'DLDM6<2<#"-"3-[9:E-D2)QS(,@G5,LI<5Z
M5$B;Y#KR&,FAR?0,-YQG?]R!'Z'SQ"E+YCR8(_XAH@#M&`&Y@X,B4CJL.F4A
MR9N`-'9J44*R5\2N*$X$6&]\89EX8NK$1)V3+(3SD'`:%DB3-^7:BDOY^1(Y
M8;DE5MHFNLFY.CU):\L(3U+:,M*?T=FU.^#H7#+4;9XIZG*V*5CPZ-)D%X`D
MOXM@<JP$R,POPO$0JEIJ9@J-#C;RD@?>XX6T!,@&583/@=,8\VB/03_@MIL9
M'%QC\LAJ@P5OF')0#DW?L[,<0>'3B-3-;*7G-/0<T#Q2"5L.2=G_`I!!:8QJ
M>HH)?7L`>G_8,X:ZL3HH96B/M&T&?7+(]%"!28GO\NA@=/;Q'5:BQH\_&EB_
MT([/CD\O3MA$*$/P]^!?PK\#3NU>%JV$L(\.,^0V(S,6)D2<.)6`K]Y?CMX>
M2NA.C:0C?`:CQ%F@`4_08)SLFKBH:H46@43O,GH\(;,KV$-<6O'B@NI]1NG(
MS2D/$4^%P`0SQ5QHFMT?HL>(H7I'EEK+.K(<T@COF7EQ/C[^9([//UP>C%8>
M(-E'(:?@'ARF$OVA,1CJ^IKC8Z1'#D_GQC@]^JI48`OCY&Q^6Z-A50M<WU*\
M;!:<+,>5>8+%'CU/KL(`?6H,$X&2K"))#._/:@MN.I1979;':0J?!]=CJQSW
M>^+U/?'ZGGA]3[R^)U[?$Z__O\3K;H;_S!N:RAI]J9"-O@[H7;K\Z':6@U(1
M[9$K[4ZO,8`Z/91#ACQX[LMD*6NNDN%E8;7*_;4X\>RX5FBQM!=Z+&FXV%PI
MWQ&H^<RG-;6%`838SN\<5#M%NR:.JD7*+8[^4M]HLD'<X-_\Y@*J577[5X,5
8F,J<H4F-X(V0^1JUVG[EORDAXG[#+0``
`
end
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 10:52:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA19523
for freebsd-current-outgoing; Wed, 11 Nov 1998 10:52:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from net.ganymed.org (ws5.cable.vol.at [194.183.130.5])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19474;
Wed, 11 Nov 1998 10:52:24 -0800 (PST)
(envelope-from flo@ganymed.org)
Received: from stone (stone.ganymed.org [192.168.2.3])
by net.ganymed.org (8.8.8/8.8.5) with SMTP id TAA01287;
Wed, 11 Nov 1998 19:51:55 +0100 (CET)
Message-Id: <3.0.32.19981111195130.0068d1d0@triton>
X-Sender: flo@triton
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Wed, 11 Nov 1998 19:51:35 +0100
To: freebsd-current@FreeBSD.ORG
From: Florian Nigsch <flo@ganymed.org>
Subject: Upgrade from 2.2-STABLE to -CURRENT
Cc: freebsd-stable@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
Hello!
I have experienced a little problem. In fact, it's a serious problem: :)
I keep pace with the sourcecodechanges with the CVSup mechanism, and so i
wanted to upgrade my FreeBSD 2.2-STABLE (2.2.7) system to -CURRENT. I read
some docs and Makefiles, found out that the best i could do was to try a
"make aout-to-elf" ind /usr/src.
Now, what I ended up with was the following:
===> strip
.
.
.
cc -O2 -m486 -pipe -D_GNU_SOURCE -I- -I.
-I/usr/src/gnu/usr.bin/binutils/strip
-I/usr/src/gnu/usr.bin/binutils/strip/../libbfd/i386
-I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/include
-I/usr/src/gnu/usr.bin/binutils/strip/../libbinutils
-I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/binutils
-I/usr/obj/aout/usr/src/tmp/usr/include -static -o strip objcopy.o
is-strip.o -L../libbinutils -lbinutils -L../libbfd -lbfd -L../libiberty
-liberty
cp strip maybe_stripped
strip maybe_stripped
*** Error code 1
...and five more "*** Error code 1".
I don't know what to try next, so I'd appreciate any comments or
recommendations in order to get rid of this problem!
please email me directly at flo@ganymed.org because I'm not subscribed to
freebsd-stable nor to freebsd-current.
Thanks to all of you in advance,
ciao,
Flo
-----------------------------------------------------
F. Nigsch <flo@ganymed.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 11:01:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA20347
for freebsd-current-outgoing; Wed, 11 Nov 1998 11:01:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.dyn.ml.org (pm3-36.ppp.wenet.net [206.15.85.36])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20338;
Wed, 11 Nov 1998 11:01:07 -0800 (PST)
(envelope-from garbanzo@hooked.net)
Received: from localhost (garbanzo@localhost)
by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id VAA14565;
Tue, 10 Nov 1998 21:06:50 -0800 (PST)
(envelope-from garbanzo@hooked.net)
X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs
Date: Tue, 10 Nov 1998 21:06:50 -0800 (PST)
From: Alex Zepeda <garbanzo@hooked.net>
X-Sender: garbanzo@zippy.dyn.ml.org
To: Dmitry Valdov <dv@dv.ru>
cc: Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-Reply-To: <Pine.BSF.3.95q.981110130222.4032C-100000@xkis.kis.ru>
Message-ID: <Pine.BSF.4.05.9811102106350.14287-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 Tue, 10 Nov 1998, Dmitry Valdov wrote:
[...]
> Really. Me and my friend experiencing this problem very often.
Yup, me too. I've seen this for quite a while.
- 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 Wed Nov 11 11:08:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA21424
for freebsd-current-outgoing; Wed, 11 Nov 1998 11:08:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from kstreet.interlog.com (kstreet.interlog.com [198.53.146.171])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21419
for <current@FreeBSD.org>; Wed, 11 Nov 1998 11:08:17 -0800 (PST)
(envelope-from kws@kstreet.interlog.com)
Received: (from kws@localhost)
by kstreet.interlog.com (8.9.1/8.9.1) id OAA00441;
Sat, 31 Oct 1998 14:07:54 -0500 (EST)
(envelope-from kws)
From: Kevin Street <street@iname.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <13883.24586.614752.970999@kstreet.interlog.com>
Date: Sat, 31 Oct 1998 14:07:54 -0500 (EST)
To: current@FreeBSD.ORG
Subject: boot loader problems with mix of wd and da
X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I have some difficulties using the new boot blocks and loader in some
configurations. I have a backup copy of my root partition on another
drive that causes the loader some problems.
kernel is aout
disks are wd0, wd1, da0, da1 (removable)
I boot through Partition Magic's Boot Manager which lives on wd0.
The normal root is on wd1s2a. The backup root is on da0s2a.
I've done (after a Nov 10 make world):
disklabel -B -b /boot/boot1 -s /boot/boot2 wd1
disklabel -B -b /boot/boot1 -s /boot/boot2 da0
The normal boot through wd1 is fine.
If I want to boot my backup root on da0 then the results vary:
1) If I don't have a /boot.config on da0 then it autoboots into /boot/loader,
currdev is set to disk3s2. It finds /boot/boot.conf ok, loads the kernel
but the kernel boot fails with "changing root device to da2s2a".
(there is no da2).
2) If I do have a /boot.config on da0 with:
2:da(0,a)/boot/loader
Then it finds and loads the loader, but currdev is set to disk1s2 so it
can't find /boot/boot.conf or anything else. disk1s2 would actually be the
Boot Manager on wd0. If I manually change currdev to disk3s2, then I can
load the kernel but boot fails as above.
3) If I interrupt the loading of /boot/loader and instead type in:
2:da(0,a)kernel
Then everything is fine. The kernel boot succeeds and correctly does
"changing root device to da0s2a". (The kernel is compiled with root on
wd1s2a since that's its normal spot). I suspect this won't work if I
go to an elf kernel since I need to use /boot/loader for elf, right?
So, why is currdev set differently in case 1 and case 2?
Why does /boot/loader confuse the kernel into thinking there's a da2 on
which it might find root?
--
Kevin Street
street@iName.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 11:08:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA21438
for freebsd-current-outgoing; Wed, 11 Nov 1998 11:08:21 -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 LAA21314;
Wed, 11 Nov 1998 11:08:00 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.59.133])
by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA736D; Wed, 11 Nov 1998 20:07:36 +0100
Message-ID: <XFMail.981111201146.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: <19981111001338.06541@nothing-going-on.org>
Date: Wed, 11 Nov 1998 20:11:46 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Nik Clayton <nik@nothing-going-on.demon.co.uk>
Subject: Re: Is it soup yet? :-)
Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@FreeBSD.ORG,
peter@FreeBSD.ORG, Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 11-Nov-98 Nik Clayton wrote:
> On Tue, Nov 10, 1998 at 10:40:16PM +0100, Jeroen Ruigrok/Asmodai wrote:
>> Could someone please point a checklist of steps for a good migrating of
>> aout to ELF? This would make it easier for us as well as being used as
>> a reference point on the web in future for 2.2.x users to 3.0.x...
>
> And when they do, can they either cc: it to -doc, or please take the
> time to send-pr as a doc-change request. At the very least, I can add it
> to my 'make world' tutorial.
As far as one kind soul was willing to point me to, all it would take would be
a 'make aout-to-elf [plus other options]'
Anything else changed from that point which the unaware reader might be warned
of in advance or is that still all it takes?
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl | Cum angelis et pueris,
Junior Network/Security Specialist | fideles inveniamur
*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 Nov 11 11:35:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA24762
for freebsd-current-outgoing; Wed, 11 Nov 1998 11:35:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24752
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 11:35:44 -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 PAA25629;
Wed, 11 Nov 1998 15:33:06 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 11 Nov 1998 15:33:05 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Brian Feldman <green@unixhelp.org>
cc: Mike Smith <mike@smith.net.au>, oZZ!!! <osa@etrust.ru>,
current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <Pine.BSF.4.05.9811111246460.24080-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.4.05.9811111531030.337-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 Wed, 11 Nov 1998, Brian Feldman wrote:
> On Wed, 11 Nov 1998, Mike Smith wrote:
>
> > >
> > > Hello!
> > > I try to install StarOffice-5.0 for linux.
> >
> > Please post emulation-related questions to freebsd-emulation.
> >
> > StarOffice 5 does not run on FreeBSD. Don't waste your time.
>
> Correction: does not run on FreeBSD _yet_. I am actively working on
> getting LinuxThreads working entirely on FreeBSD, and am much closer than
> before. Don't expect LinuxThreaded programs to not work for much longer.
Keep up the good work Brian...the longer I can avoid installing a
Linux system to get its commercial apps, the happier I will be. With
attitudes like "don't waste your time" vs "its being worked on", I fear
that that day is fast approaching where I'll have to buy a third machine
just to keep from having to run Windows to get the good apps :(
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 Wed Nov 11 11:37:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA24999
for freebsd-current-outgoing; Wed, 11 Nov 1998 11:37:51 -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 LAA24994
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 11:37:49 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id LAA17191;
Wed, 11 Nov 1998 11:30:45 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdD17173; Wed Nov 11 19:30:37 1998
Date: Wed, 11 Nov 1998 11:29:54 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <9940.910772319@zippy.cdrom.com>
Message-ID: <Pine.BSF.3.95.981111112705.16498A-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
we can't replace the bootblocks.. the owners of these machines in every
continent can't do that.. :-)
we will probably be dropping in a 3rd stage loader
made in a.out, called 'kernel'
the new kernel will probably be called elfkernel or similar (ekernel?)
julian
On Wed, 11 Nov 1998, Jordan K. Hubbard wrote:
> > the ability to run on old bootblocks is how shall I say...
> > "required".
>
> Well, you have and have always had just two options the minute we pull
> the elf kernel switch: You switch customers to the 3-stage boot by
> dropping a /boot.conf file into place which calls /boot/loader (which
> you also install along with the 3.0 upgrade) or you relabel them so
> they look just like freshly installed 3.0.x systems; it's your choice
> whether you want to go for minimal impact or minimal difference.
>
> - Jordan
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 11:47:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA25903
for freebsd-current-outgoing; Wed, 11 Nov 1998 11:47:38 -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 LAA25874
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 11:47:34 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id LAA17817;
Wed, 11 Nov 1998 11:46:00 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdo17813; Wed Nov 11 19:45:51 1998
Date: Wed, 11 Nov 1998 11:45:17 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
Reply-To: Julian Elischer <julian@whistle.com>
To: Chuck Robey <chuckr@mat.net>
cc: current@FreeBSD.ORG
Subject: Re: softupdates
In-Reply-To: <Pine.BSF.4.05.9811102224550.10145-100000@picnic.mat.net>
Message-ID: <Pine.BSF.3.95.981111114358.16498D-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
you have two options...
1/ tunefs -n disable from single user mode
OR
2/ compile a kernel with options SOFTUPDATES removed.
On Tue, 10 Nov 1998, Chuck Robey wrote:
> I'm having an odd problem, and I want to see if maybe softupdates might
> possibly be causing it. Can I turn off softupdates by just doing the
> tunefs command, or do I have to remove the softupdates mods to the
> kernel sources, and recompile/reinstall the kernel, in addition to the
> tunefs command?
>
> ----------------------------+-----------------------------------------------
> 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
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 11:52:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA26384
for freebsd-current-outgoing; Wed, 11 Nov 1998 11:52:06 -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 LAA26377
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 11:52:03 -0800 (PST)
(envelope-from lists@tar.com)
Received: from ppro.tar.com (ppro.tar.com [204.95.187.9])
by ns.tar.com (8.9.1/8.8.7) with SMTP id NAA17744;
Wed, 11 Nov 1998 13:51:34 -0600 (CST)
Message-Id: <199811111951.NAA17744@ns.tar.com>
From: "Richard Seaman, Jr." <lists@tar.com>
To: "Brian Feldman" <green@unixhelp.org>
Cc: "current@freebsd.org" <current@FreeBSD.ORG>
Date: Wed, 11 Nov 98 13:51:33 -0600
Reply-To: "Richard Seaman, Jr." <lists@tar.com>
X-Mailer: PMMail 1.92 For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: RFSIGSHARE ready?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I've looked more closely at your patch. If I understand what it does,
it shares signal actions as well as signal masks between threads.
Its my understanding that POSIX specifies that signal actions
are shared process wide, but that each thread has its own signal
mask. It appears to me that this is also what linux threads
attempts to implement.
If you want POSIX and linux thread compliant signal handling,
I would think you would share the p_sigacts structure, but
not the p_sigmask structure. However, I have no idea what
the linux kernel actually does, so if your goal is to match
that, I have no idea if your implementation does that.
Also, FYI, your patches break a make buildworld in gdb too.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 12:02:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA27112
for freebsd-current-outgoing; Wed, 11 Nov 1998 12:02:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27104
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 12:02:44 -0800 (PST)
(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
by freebsd.dk (8.9.1/8.9.1) id VAA00590;
Wed, 11 Nov 1998 21:00:55 +0100 (CET)
(envelope-from sos)
From: Søren Schmidt <sos@freebsd.dk>
Message-Id: <199811112000.VAA00590@freebsd.dk>
Subject: Re: StarOffice-5.0...
In-Reply-To: <Pine.BSF.4.02A.9811111218510.20241-200000@korin.warman.org.pl> from Andrzej Bialecki at "Nov 11, 1998 12:22:55 pm"
To: abial@nask.pl (Andrzej Bialecki)
Date: Wed, 11 Nov 1998 21:00:55 +0100 (CET)
Cc: daeron@Wit401305.student.utwente.nl, shawn@cpl.net, osa@etrust.ru,
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 Andrzej Bialecki wrote:
> > As far as I know StarOffice 5.0 install-program tries to read the
> > commandline from /proc ... I think i saw some postings about this on
> > comps.os.unix.bsd.* (or something like that)
>
> Yes, I've got the diffs against relatively fresh current. BTW, I asked
> this question on -emulation, but got back a profound silence... Can we/
> should we incorporate this patch, and hide it under a kernel option, say
> PROCFS_CMDLINE? The life would be soooo easier for people new to our linux
> emulation...
Hmm, if we should have a Linsux compatible /proc, it really should be
a beast mounted on /compat/linux/proc. If you provide this, I'm sure
it will be received with open arms :)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 12:14:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA28006
for freebsd-current-outgoing; Wed, 11 Nov 1998 12:14:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27980
for <freebsd-current@freebsd.org>; Wed, 11 Nov 1998 12:14:00 -0800 (PST)
(envelope-from jack@germanium.xtalwind.net)
Received: from localhost (jack@localhost)
by germanium.xtalwind.net (8.9.1/8.9.1) with ESMTP id PAA24112
for <freebsd-current@freebsd.org>; Wed, 11 Nov 1998 15:12:54 -0500 (EST)
Date: Wed, 11 Nov 1998 15:12:54 -0500 (EST)
From: jack <jack@germanium.xtalwind.net>
To: freebsd-current@FreeBSD.ORG
Subject: Tekram DC-390 and 3.0
Message-ID: <Pine.BSF.4.05.9811111510340.24083-100000@germanium.xtalwind.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Before I order one, can anyone verify that the Tekram DC-390
controller still works with current?
Thanks.
--------------------------------------------------------------------------
Jack O'Neill Systems Administrator / Systems Analyst
jack@germanium.xtalwind.net Crystal Wind Communications, Inc.
Finger jack@germanium.xtalwind.net for my PGP key.
PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD
enriched, vcard, HTML messages > /dev/null
--------------------------------------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 12:21:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA28817
for freebsd-current-outgoing; Wed, 11 Nov 1998 12:21:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fourier.physics.purdue.edu (fourier.physics.purdue.edu [128.210.146.43])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28802
for <freebsd-current@FreeBSD.ORG>; Wed, 11 Nov 1998 12:21:49 -0800 (PST)
(envelope-from jonsmith@fourier.physics.purdue.edu)
Received: from localhost (jonsmith@localhost)
by fourier.physics.purdue.edu (8.8.8/8.8.8) with SMTP id PAA22798;
Wed, 11 Nov 1998 15:19:22 GMT
(envelope-from jonsmith@fourier.physics.purdue.edu)
Date: Wed, 11 Nov 1998 15:19:22 +0000 (GMT)
From: Jonathan Smith <jonsmith@fourier.physics.purdue.edu>
To: jack <jack@germanium.xtalwind.net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Tekram DC-390 and 3.0
In-Reply-To: <Pine.BSF.4.05.9811111510340.24083-100000@germanium.xtalwind.net>
Message-ID: <Pine.BSF.3.96.981111151451.22793A-100000@fourier.physics.purdue.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, 11 Nov 1998, jack wrote:
> Before I order one, can anyone verify that the Tekram DC-390
> controller still works with current?
>
> Thanks.
>
> --------------------------------------------------------------------------
> Jack O'Neill Systems Administrator / Systems Analyst
Boot up hardware test reports the DC-390F as ncr0. We've had it up for a
while with a problem in large volume address translation (requiring boot
from floppy), but we think that was our own misconfiguration. We shall be
bringing it back up within a week, if you'd like a report then.
jon smith
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 12:36:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA29801
for freebsd-current-outgoing; Wed, 11 Nov 1998 12:36:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29793
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 12:36:21 -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 MAA04864;
Wed, 11 Nov 1998 12:33:50 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811112033.MAA04864@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Kevin Street <street@iname.com>
cc: current@FreeBSD.ORG
Subject: Re: boot loader problems with mix of wd and da
In-reply-to: Your message of "Sat, 31 Oct 1998 14:07:54 EST."
<13883.24586.614752.970999@kstreet.interlog.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 12:33:50 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I have some difficulties using the new boot blocks and loader in some
> configurations. I have a backup copy of my root partition on another
> drive that causes the loader some problems.
>
> kernel is aout
> disks are wd0, wd1, da0, da1 (removable)
>
> I boot through Partition Magic's Boot Manager which lives on wd0.
> The normal root is on wd1s2a. The backup root is on da0s2a.
> I've done (after a Nov 10 make world):
> disklabel -B -b /boot/boot1 -s /boot/boot2 wd1
> disklabel -B -b /boot/boot1 -s /boot/boot2 da0
>
> The normal boot through wd1 is fine.
>
> If I want to boot my backup root on da0 then the results vary:
>
> 1) If I don't have a /boot.config on da0 then it autoboots into /boot/loader,
> currdev is set to disk3s2. It finds /boot/boot.conf ok, loads the kernel
> but the kernel boot fails with "changing root device to da2s2a".
> (there is no da2).
This is the same as the old problem that required you to prefix a BIOS
unit number offset to the 'sd' in the old loader. You need to
explicitly set $rootdev:
set rootdev=da0s2a
> 2) If I do have a /boot.config on da0 with:
> 2:da(0,a)/boot/loader
> Then it finds and loads the loader, but currdev is set to disk1s2 so it
> can't find /boot/boot.conf or anything else. disk1s2 would actually be the
> Boot Manager on wd0. If I manually change currdev to disk3s2, then I can
> load the kernel but boot fails as above.
This is not the right way to do it; the BIOS unit numbers get all
screwed up.
> 3) If I interrupt the loading of /boot/loader and instead type in:
> 2:da(0,a)kernel
> Then everything is fine. The kernel boot succeeds and correctly does
> "changing root device to da0s2a". (The kernel is compiled with root on
> wd1s2a since that's its normal spot). I suspect this won't work if I
> go to an elf kernel since I need to use /boot/loader for elf, right?
>
> So, why is currdev set differently in case 1 and case 2?
Because you've supplied the '2', obviously enough.
> Why does /boot/loader confuse the kernel into thinking there's a da2 on
> which it might find root?
Because you haven't told it not to.
--
\\ 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 Nov 11 12:40:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA00328
for freebsd-current-outgoing; Wed, 11 Nov 1998 12:40:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00323
for <freebsd-current@FreeBSD.ORG>; Wed, 11 Nov 1998 12:40: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 MAA04898;
Wed, 11 Nov 1998 12:37:56 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811112037.MAA04898@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: jack <jack@germanium.xtalwind.net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Tekram DC-390 and 3.0
In-reply-to: Your message of "Wed, 11 Nov 1998 15:12:54 EST."
<Pine.BSF.4.05.9811111510340.24083-100000@germanium.xtalwind.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 12:37:51 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Before I order one, can anyone verify that the Tekram DC-390
> controller still works with current?
Which one? There are two basic variants, one using the AMD chip (not
supported) and one that uses an NCR part (supported fine).
--
\\ 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 Nov 11 12:40:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA00344
for freebsd-current-outgoing; Wed, 11 Nov 1998 12:40:37 -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 MAA00338
for <freebsd-current@FreeBSD.ORG>; Wed, 11 Nov 1998 12:40:35 -0800 (PST)
(envelope-from sthaug@nethelp.no)
From: sthaug@nethelp.no
Received: (qmail 20527 invoked by uid 1001); 11 Nov 1998 20:40:15 +0000 (GMT)
To: jack@germanium.xtalwind.net
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Tekram DC-390 and 3.0
In-Reply-To: Your message of "Wed, 11 Nov 1998 15:12:54 -0500 (EST)"
References: <Pine.BSF.4.05.9811111510340.24083-100000@germanium.xtalwind.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, 11 Nov 1998 21:40:15 +0100
Message-ID: <20523.910816815@verdi.nethelp.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Before I order one, can anyone verify that the Tekram DC-390
> controller still works with current?
Works very well with -current on several machines here.
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 Nov 11 12:44:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA00876
for freebsd-current-outgoing; Wed, 11 Nov 1998 12:44:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00861
for <freebsd-current@FreeBSD.ORG>; Wed, 11 Nov 1998 12:44:35 -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 MAA04940;
Wed, 11 Nov 1998 12:41:52 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811112041.MAA04940@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Jonathan Smith <jonsmith@fourier.physics.purdue.edu>
cc: jack <jack@germanium.xtalwind.net>, freebsd-current@FreeBSD.ORG
Subject: Re: Tekram DC-390 and 3.0
In-reply-to: Your message of "Wed, 11 Nov 1998 15:19:22 GMT."
<Pine.BSF.3.96.981111151451.22793A-100000@fourier.physics.purdue.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 12:41:52 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> Boot up hardware test reports the DC-390F as ncr0. We've had it up for a
> while with a problem in large volume address translation (requiring boot
> from floppy), but we think that was our own misconfiguration. We shall be
> bringing it back up within a week, if you'd like a report then.
That's probably correct - if you installed the system using sysinstall
and elected to use "dangerously dedicated mode" (all disk, not
cross-compatible), the NCR BIOS will usually get the geometry wrong (it
looks to see how the disk is laid out, and doesn't understand what a DD
layout looks like). Some system BIOSses make the same mistakes on IDE
disks.
It is for this reason that we *strongly* *discourage* the use of
this mode.
--
\\ 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 Nov 11 12:45:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA00968
for freebsd-current-outgoing; Wed, 11 Nov 1998 12:45:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00957
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 12:45:40 -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 LAA04505;
Wed, 11 Nov 1998 11:37:01 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811111937.LAA04505@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: obrien@NUXI.com
cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 09:45:17 PST."
<19981111094517.B18529@nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 11:37:01 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > I can see we are simply of two minds on this issue. :) What do some of
> > the others think?
>
> While I agree with the silly name, I think we are approaching another
> gratuitous change. It is our history, /usr/mdec is where people are used
> to looking, ...
It is our history to have buggy NFS. It is our history to have a
bogus kernel module subsystem. It is our history to play catch-up to
Linux.
The good old days weren't always good, and tomorrow's not as bad as it
seems.
--
\\ 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 Nov 11 12:46:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA01079
for freebsd-current-outgoing; Wed, 11 Nov 1998 12:46:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01053
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 12:46: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 LAA04529;
Wed, 11 Nov 1998 11:41:05 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811111941.LAA04529@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Nate Williams <nate@mt.sri.com>
cc: Mike Smith <mike@smith.net.au>, Ville-Pertti Keinonen <will@iki.fi>,
sthaug@nethelp.no, jkh@zippy.cdrom.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 11:09:51 MST."
<199811111809.LAA17690@mt.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 11:41:04 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > I think the issue is perhaps a little over-emotional. The images total
> > 8k in three files, and really don't justify or warrant a directory all
> > to themselves *anywhere*.
>
> More than that. I've got 101K in mine, which includes boot1, boot2,
> fbsdboot.exe, a bunch of com files for ether-booting, and rawboot.
We're not discussing any of that legacy cruft, none of which belongs in
/usr/mdec either. The discussion here is specific to the disposition of
boot0, boot1 and boot2.
--
\\ 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 Nov 11 12:58:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA01930
for freebsd-current-outgoing; Wed, 11 Nov 1998 12:58: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 MAA01890
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 12:58:01 -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 NAA27523;
Wed, 11 Nov 1998 13:57:33 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id NAA19037; Wed, 11 Nov 1998 13:57:32 -0700
Date: Wed, 11 Nov 1998 13:57:32 -0700
Message-Id: <199811112057.NAA19037@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>, Ville-Pertti Keinonen <will@iki.fi>,
sthaug@nethelp.no, jkh@zippy.cdrom.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <199811111941.LAA04529@dingo.cdrom.com>
References: <199811111809.LAA17690@mt.sri.com>
<199811111941.LAA04529@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
> > > I think the issue is perhaps a little over-emotional. The images total
> > > 8k in three files, and really don't justify or warrant a directory all
> > > to themselves *anywhere*.
> >
> > More than that. I've got 101K in mine, which includes boot1, boot2,
> > fbsdboot.exe, a bunch of com files for ether-booting, and rawboot.
>
> We're not discussing any of that legacy cruft, none of which belongs in
> /usr/mdec either. The discussion here is specific to the disposition of
> boot0, boot1 and boot2.
So, where does the 'legacy cruft' go then? Seems like everything in
/usr/mdec belongs in /usr/mdec right now, and breaking it up is change
for the sake of change....
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 12:59:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA02084
for freebsd-current-outgoing; Wed, 11 Nov 1998 12:59:24 -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 MAA02078
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 12:59:22 -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 NAA27540;
Wed, 11 Nov 1998 13:59:03 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id NAA19049; Wed, 11 Nov 1998 13:59:02 -0700
Date: Wed, 11 Nov 1998 13:59:02 -0700
Message-Id: <199811112059.NAA19049@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: obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <199811111937.LAA04505@dingo.cdrom.com>
References: <19981111094517.B18529@nuxi.com>
<199811111937.LAA04505@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
> > > I can see we are simply of two minds on this issue. :) What do some of
> > > the others think?
> >
> > While I agree with the silly name, I think we are approaching another
> > gratuitous change. It is our history, /usr/mdec is where people are used
> > to looking, ...
>
> It is our history to have buggy NFS. It is our history to have a
> bogus kernel module subsystem. It is our history to play catch-up to
> Linux.
Mike, go to a dictionary and lookup the word 'gratiutious'. Your
statements are flame-bait and provide no content. Moving stuff out of
/usr/mdec provides *NO* (!!) functionality improvement, just movement.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 13:01:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA02389
for freebsd-current-outgoing; Wed, 11 Nov 1998 13:01:19 -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 NAA02377
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 13:01:17 -0800 (PST)
(envelope-from obrien@cs.ucdavis.edu)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id NAA19909;
Wed, 11 Nov 1998 13:00:49 -0800 (PST)
(envelope-from obrien)
Message-ID: <19981111130048.K14341@nuxi.com>
Date: Wed, 11 Nov 1998 13:00:48 -0800
From: "David O'Brien" <obrien@cs.ucdavis.edu>
To: Mike Smith <mike@smith.net.au>
Cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
Reply-To: obrien@cs.ucdavis.edu
References: <19981111094517.B18529@nuxi.com> <199811111937.LAA04505@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199811111937.LAA04505@dingo.cdrom.com>; from Mike Smith on Wed, Nov 11, 1998 at 11:37:01AM -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
> > While I agree with the silly name, I think we are approaching another
> > gratuitous change. It is our history, /usr/mdec is where people are used
> > to looking, ...
>
> It is our history to have buggy NFS.
Sorry, by "history" I mean BSD, not just FreeBSD.
--
-- David (obrien@NUXI.ucdavis.edu -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 Wed Nov 11 13:02:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA02423
for freebsd-current-outgoing; Wed, 11 Nov 1998 13:01:27 -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 NAA02410
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 13:01:23 -0800 (PST)
(envelope-from peter.jeremy@auss2.alcatel.com.au)
Received: by border.alcanet.com.au id <40345>; Thu, 12 Nov 1998 08:00:26 +1100
Date: Thu, 12 Nov 1998 07:59:43 +1100
From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Subject: /boot vs /usr/mdec [was Re: Is it soup yet? :-)]
To: current@FreeBSD.ORG
Message-Id: <98Nov12.080026est.40345@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Nate Williams <nate@mt.sri.com> wrote:
>Mike Smith <mike@smith.net.au> wrote:
>> I think the issue is perhaps a little over-emotional. The images total
>> 8k in three files, and really don't justify or warrant a directory all
>> to themselves *anywhere*.
>
>More than that. I've got 101K in mine, which includes boot1, boot2,
>fbsdboot.exe, a bunch of com files for ether-booting, and rawboot.
/usr/mdec on 3.0-RELEASE contains 1.5MB, os which 1.4MB is cdboot.
There's 100K (exactly) of other boot images.
FWIW, I don't see any point in moving this to /boot (or anywhere else
in /). I share the viewpoints which can be summarised as (in my
priority order):
1) / should contain only the tools/programs/data necessary to boot the
system and resurrect the remaining filesystems. The contents of
/usr/mdec do not fall into this category (see below).
2) /usr/mdec is the standard BSD place for boot-related data. It may
be an obscure place, but so is /usr/platform/sun4m/lib/fs/ufs
[the Solaris 2.x equivalent on a sun4m].
3) Resizing / is painful. Minimising the amount of extraneous junk
loaded into / helps put off that evil day.
/usr/mdec does not contain any _files_ that are helpful in booting a
system or resurrecting a system once it is booted. The contents of
boot[12] are essential to boot a system, but they have to be located
in particular physical disk blocks - not in a filesystem. Similarly,
the network card ROM images have to be in a ROM on the network card to
be of any use. fbsdboot.exe is of no use at all inside a UFS
filesystem (since the fileloader it is designed to work with cannot
understand UFS).
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 5247
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 13:02:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA02454
for freebsd-current-outgoing; Wed, 11 Nov 1998 13:01:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from home.dv.ru (home.dv.ru [195.98.33.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02296;
Wed, 11 Nov 1998 13:00:40 -0800 (PST)
(envelope-from dv@dv.ru)
Received: from localhost (dv@localhost)
by home.dv.ru (8.9.1/8.9.1) with SMTP id AAA00661;
Thu, 12 Nov 1998 00:00:01 +0300 (MSK)
(envelope-from dv@dv.ru)
X-Authentication-Warning: home.dv.ru: dv owned process doing -bs
Date: Thu, 12 Nov 1998 00:00:00 +0300 (MSK)
From: Dmitry Valdov <dv@dv.ru>
To: Brian Somers <brian@FreeBSD.ORG>
cc: current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
In-Reply-To: <Pine.BSF.3.95q.981111105347.20962F-100000@xkis.kis.ru>
Message-ID: <Pine.BSF.4.02A.9811112357130.646-100000@home.dv.ru>
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 just tried to put
"delete! default" in ppp.conf file and it has no effect. ppp hangs when
default route exists.
On Wed, 11 Nov 1998, Dmitry Valdov wrote:
>
>
> ---------- Forwarded message ----------
> Date: Tue, 10 Nov 1998 21:40:53 +0000
> From: Brian Somers <brian@Awfulhak.org>
> To: Jason Fesler <jfesler@gigo.com>
> Cc: Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
> Dmitry Valdov <dv@dv.ru>, Brian Somers <brian@FreeBSD.ORG>,
> current@FreeBSD.ORG
> Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
>
> > > Sorry for the "implicit bug report", Brian, but I've been meaning to track
> > > this down for a long time and make sure it's not user error. I often see this
> >
> > I've had this since the 2.2.2 days when I first started running ppp.
> > After a while (hours, days, weeks - random) either carrier isn't noticed
> > as being missing, or all outgoing packets don't cross the serial cable to
> > to the other side. After a while I kinda gave up.
>
> Ppp won't expect carrier if it's not detected when ppp starts doing
> LCP. This allows null-modem cables without the correct wiring to
> work.
>
> As I've said to a couple of these posts - enable debug logging and
> you'll see the carrier status reported every second. You can also
> ``show modem'' to see what things look like.
>
> > I now every few minutes fping a few hosts on the nearby remote side. If
> > they _all_ fail (a good 10 second timeout is given) then I kill -9 the ppp
> > session, wait 2 seconds, then restart ppp. It's caught every strange
> > random bug on either side soon enough that I no longer have to try and
> > call home and walk the wife through ppp..
>
> Ppp should be a lot more reliable these days.
> --
> 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 Wed Nov 11 13:15:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA03581
for freebsd-current-outgoing; Wed, 11 Nov 1998 13:15:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03575
for <freebsd-current@FreeBSD.ORG>; Wed, 11 Nov 1998 13:15:26 -0800 (PST)
(envelope-from jack@germanium.xtalwind.net)
Received: from localhost (jack@localhost)
by germanium.xtalwind.net (8.9.1/8.9.1) with ESMTP id QAA24302;
Wed, 11 Nov 1998 16:14:44 -0500 (EST)
Date: Wed, 11 Nov 1998 16:14:44 -0500 (EST)
From: jack <jack@germanium.xtalwind.net>
To: Mike Smith <mike@smith.net.au>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Tekram DC-390 and 3.0
In-Reply-To: <199811112037.MAA04898@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811111546430.24198-100000@germanium.xtalwind.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, 11 Nov 1998, Mike Smith wrote:
> > Before I order one, can anyone verify that the Tekram DC-390
> > controller still works with current?
>
> Which one? There are two basic variants, one using the AMD chip (not
> supported) and one that uses an NCR part (supported fine).
The current incarnations of that card are DC-390, SCSI-2 which
uses the AMD 53c974A chip, and the DC-390U Ultra SCSI and DC-390F
Ultra-Wide SCSI which use the NCR 875.
If the AMD chip is no longer supported may I suggest that the
following be removed from LINT. Or if only the `A' version
of the chip is not supported that that be made clearer.
-----
# $Id: LINT,v 1.502 1998/11/08 09:57:28 peter Exp $
[snip]
# The `amd' device provides support for the Tekram DC-390 and
390T
# SCSI host adapters, but is expected to work with any AMD 53c974
# PCI SCSI chip and the AMD Ethernet+SCSI Combo chip, after some
# local patches were applied to the sources (that had originally
# been written by Tekram and limited to work with their SCSI
cards).
-----
and
----
amd0 n/a n/a n/a n/a Tekram DC-390(T) / AMD
53c974 PCI SCSI
----
be removed from, or clarified in, HARDWARE.TXT, dated Oct. 16,
1998.
I'm being particularly cautious because the DC-800B, a 1542
compatible card with caching that has worked well with 2.x, will
not work with the current aha.c. And it isn't the timing problem
that was reported. A liberal dose of printf(3)s in aha.c shows
that that dog just ain't gonna hunt. :(
--------------------------------------------------------------------------
Jack O'Neill Systems Administrator / Systems Analyst
jack@germanium.xtalwind.net Crystal Wind Communications, Inc.
Finger jack@germanium.xtalwind.net for my PGP key.
PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD
enriched, vcard, HTML messages > /dev/null
--------------------------------------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 13:24:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA04504
for freebsd-current-outgoing; Wed, 11 Nov 1998 13:24:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from home.dv.ru (home.dv.ru [195.98.33.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04490;
Wed, 11 Nov 1998 13:24:27 -0800 (PST)
(envelope-from dv@dv.ru)
Received: from localhost (dv@localhost)
by home.dv.ru (8.9.1/8.9.1) with SMTP id AAA00777;
Thu, 12 Nov 1998 00:21:17 +0300 (MSK)
(envelope-from dv@dv.ru)
X-Authentication-Warning: home.dv.ru: dv owned process doing -bs
Date: Thu, 12 Nov 1998 00:21:16 +0300 (MSK)
From: Dmitry Valdov <dv@dv.ru>
To: Brian Somers <brian@FreeBSD.ORG>
cc: current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
In-Reply-To: <Pine.BSF.3.95q.981111105056.20962C-100000@xkis.kis.ru>
Message-ID: <Pine.BSF.4.02A.9811120012480.757-100000@home.dv.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi!
Just have this problem again. With debug set on. ppp thinks that
everything is ok, but modem already hanged up. When I kill it with -1 it
says that
it normally terminated the connection then exit.
I think the workaround is to send ate0 to modem because it sends something
to modem and receiving it :) But default config has ATE1 in it.
I'm *really* sure that my modem is configured properly and it's not a user
error :)
What can I do to help you to resolve the problem? I'm using dial-on-demand
(pmdemand section) and running ppp with a command ppp -auto pmdemand.
On Wed, 11 Nov 1998, Dmitry Valdov wrote:
>
>
> ---------- Forwarded message ----------
> Date: Tue, 10 Nov 1998 21:32:53 +0000
> From: Brian Somers <brian@Awfulhak.org>
> To: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
> Cc: Dmitry Valdov <dv@dv.ru>, Brian Somers <brian@freebsd.org>,
> current@freebsd.org
> Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
>
> > On Tue, 10 Nov 1998, Dmitry Valdov wrote:
> >
> > > Also there is one more bug - sometimes ppp don't detect carrier lost and
> > > stays in open state for a long time. :(
> >
> > Sorry for the "implicit bug report", Brian, but I've been meaning to track
> > this down for a long time and make sure it's not user error. I often see this
> > as well - it's noticeable for me because I have ipfw installed and when the
> > modem drops carrier I see packets being 'reflected' by the modem's local echo
> > (I assume), and bouncing off the ipfw 'incoming address of myself' filter.
>
> Try ``set log +debug''. You should see the online/offline status of
> the link at frequent intervals. If this doesn't agree with your
> modem, then you modem may be misconfigured.
>
> > Kris
>
> --
> 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 Wed Nov 11 13:25:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA04543
for freebsd-current-outgoing; Wed, 11 Nov 1998 13:25:00 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04538
for <current@freebsd.org>; Wed, 11 Nov 1998 13:24:58 -0800 (PST)
(envelope-from locke@Venus.mcs.net)
Received: from Venus.mcs.net (locke@Venus.mcs.net [192.160.127.92]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id PAA15932 for <current@freebsd.org>; Wed, 11 Nov 1998 15:24:39 -0600 (CST)
Received: from localhost (locke@localhost) by Venus.mcs.net (8.8.7/8.8.2) with SMTP id PAA19533 for <current@freebsd.org>; Wed, 11 Nov 1998 15:24:39 -0600 (CST)
Date: Wed, 11 Nov 1998 15:24:38 -0600 (CST)
From: Quagmire <locke@Mcs.Net>
To: current@FreeBSD.ORG
Subject: aout-to-elf-build failure after freebsd.cf?
Message-ID: <Pine.BSF.3.95.981111151540.19367A-100000@Venus.mcs.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Decided to upgrade my -current aout system (cvsupped yesterday) to elf
(cvsupped today around 1) using make aout-to-elf-build. I'm running SMP
w/o softupdates. I deleted the /usr/obj tree of files before building.
Running "make -j8 aout-to-elf-build" results (eventually :) in the
following error:
--- wcd_mod.o ---
ld -r -aout -o tmp.o wcd.o
rm -f symb.tmp
for i in _wcd_mod ; do echo $i >> symb.tmp ; done
symorder -c symb.tmp tmp.o
rm -f symb.tmp
my tmp.o wcd_mod.o
===> etc
--- all ---
===> etc/sendmail
--- freebsd.cf ---
rm -f freebsd.cf
(cd /usr/src/etc/sendmail && m4
-D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/sendmail/cf/
/usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 freebsd.mc) >
freebsd.cf
chmod 444 freebsd.cf
1 error
*** Error code 2
1 error
#
(note: the "(cd ... > freebsd.cf" line is one line--pine wordwraps)
Help! :)
Thanks,
Peter Johnson
locke@mcs.net
(and yes, I subscribe to the -current list, so no need to cc me).
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 13:25:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA04573
for freebsd-current-outgoing; Wed, 11 Nov 1998 13:25:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mordred.cs.ucla.edu (Mordred.CS.UCLA.EDU [131.179.48.34])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04568
for <freebsd-current@freebsd.org>; Wed, 11 Nov 1998 13:25:13 -0800 (PST)
(envelope-from scottm@mordred.cs.ucla.edu)
Received: from mordred.cs.ucla.edu (localhost [127.0.0.1])
by mordred.cs.ucla.edu (8.9.1/8.9.1) with ESMTP id NAA21397;
Wed, 11 Nov 1998 13:24:35 -0800 (PST)
(envelope-from scottm@mordred.cs.ucla.edu)
Message-Id: <199811112124.NAA21397@mordred.cs.ucla.edu>
X-Mailer: exmh version 2.0.2 2/24/98
To: jack <jack@germanium.xtalwind.net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Tekram DC-390 and 3.0
In-reply-to: Your message of "Wed, 11 Nov 1998 15:12:54 EST."
<Pine.BSF.4.05.9811111510340.24083-100000@germanium.xtalwind.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 13:24:35 -0800
From: Scott Michel <scottm@cs.ucla.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I've got a DC-390F, and it's a wonderfully priced replacement of
the Adaptec. And it works with 3.0. Immensely pleased.
-scooter
> Before I order one, can anyone verify that the Tekram DC-390
> controller still works with current?
>
> Thanks.
>
> --------------------------------------------------------------------------
> Jack O'Neill Systems Administrator / Systems Analyst
> jack@germanium.xtalwind.net Crystal Wind Communications, Inc.
> Finger jack@germanium.xtalwind.net for my PGP key.
> PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD
> enriched, vcard, HTML messages > /dev/null
> --------------------------------------------------------------------------
>
>
>
> 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 Nov 11 13:45:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA06626
for freebsd-current-outgoing; Wed, 11 Nov 1998 13:45:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06621
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 13:45:39 -0800 (PST)
(envelope-from dan@math.berkeley.edu)
Received: (from dan@localhost)
by math.berkeley.edu (8.8.7/8.8.7) id NAA23992;
Wed, 11 Nov 1998 13:45:15 -0800 (PST)
Date: Wed, 11 Nov 1998 13:45:15 -0800 (PST)
From: dan@math.berkeley.edu (Dan Strick)
Message-Id: <199811112145.NAA23992@math.berkeley.edu>
To: sthaug@nethelp.no
Subject: Re: Is it soup yet? :-)
Cc: current@FreeBSD.ORG, dan@math.berkeley.edu
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > The mdec name certainly isn't FreeBSD-specific, changing it would add
> ...
> Has it: FreeBSD, NetBSD, possibly OpenBSD.
You forgot Solaris-1. /usr/mdec goes back at least as far as
"research version 6" circa 1976. I don't remember when it
disappeared from the BTL/ATT/USL/..SystemV sequence (never used
the later versions at all).
The name of the directory was a minor mystery even in 1976.
I suspect the "dec" stood for "Digital Equipment Corporation"
but never knew what to make of the "m".
If everyone wants to change the name of the directory to something
more obvious ... sure, why not. While we are at it, why don't we
also change the name of that non-obvious "grep" command.
Dan Strick
dan@math.berkeley.edu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 13:53:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA07457
for freebsd-current-outgoing; Wed, 11 Nov 1998 13:53:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from feral-gw.feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07447
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 13:53:32 -0800 (PST)
(envelope-from mjacob@feral.com)
Received: from localhost (mjacob@localhost)
by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id NAA22422;
Wed, 11 Nov 1998 13:51:29 -0800
Date: Wed, 11 Nov 1998 13:51:29 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
X-Sender: mjacob@feral-gw
Reply-To: mjacob@feral.com
To: Dan Strick <dan@math.berkeley.edu>
cc: sthaug@nethelp.no, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <199811112145.NAA23992@math.berkeley.edu>
Message-ID: <Pine.LNX.4.02.9811111346260.22015-100000@feral-gw>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
m in mdec was short for 'machine' IIRC. It wasn't in /usr originally I
believe.
It was part of the kernel for v7. I don't really recally it as part
of v6/PWB, but this is quite a while agao.
The boot gup all has to go somewhere. It should be probably ensured to be
in the root filesystem. This seems to me to say /boot.
On Wed, 11 Nov 1998, Dan Strick wrote:
> > > The mdec name certainly isn't FreeBSD-specific, changing it would add
> > ...
> > Has it: FreeBSD, NetBSD, possibly OpenBSD.
>
> You forgot Solaris-1. /usr/mdec goes back at least as far as
> "research version 6" circa 1976. I don't remember when it
> disappeared from the BTL/ATT/USL/..SystemV sequence (never used
> the later versions at all).
>
> The name of the directory was a minor mystery even in 1976.
> I suspect the "dec" stood for "Digital Equipment Corporation"
> but never knew what to make of the "m".
>
> If everyone wants to change the name of the directory to something
> more obvious ... sure, why not. While we are at it, why don't we
> also change the name of that non-obvious "grep" command.
>
> Dan Strick
> dan@math.berkeley.edu
>
> 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 Nov 11 14:05:25 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA08771
for freebsd-current-outgoing; Wed, 11 Nov 1998 14:05:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08756
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 14:05:20 -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 OAA05485;
Wed, 11 Nov 1998 14:02:15 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811112202.OAA05485@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Nate Williams <nate@mt.sri.com>
cc: Mike Smith <mike@smith.net.au>, Ville-Pertti Keinonen <will@iki.fi>,
sthaug@nethelp.no, jkh@zippy.cdrom.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 13:57:32 MST."
<199811112057.NAA19037@mt.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 14:02:14 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > > > I think the issue is perhaps a little over-emotional. The images total
> > > > 8k in three files, and really don't justify or warrant a directory all
> > > > to themselves *anywhere*.
> > >
> > > More than that. I've got 101K in mine, which includes boot1, boot2,
> > > fbsdboot.exe, a bunch of com files for ether-booting, and rawboot.
> >
> > We're not discussing any of that legacy cruft, none of which belongs in
> > /usr/mdec either. The discussion here is specific to the disposition of
> > boot0, boot1 and boot2.
>
> So, where does the 'legacy cruft' go then? Seems like everything in
> /usr/mdec belongs in /usr/mdec right now, and breaking it up is change
> for the sake of change....
Of the items you list in your /usr/mdec, only boot0, boot1 and boot2 are
native boot tools. (8.5k) Boot1 and boot2 go under multiple names due
to legacy behaviour in disklabel which we don't need (as we have a
unified bootstrap set) and should lose.
Fbsdboot.exe is obsolete; it should be maintained outside the tree if at
all. It's no longer possible to safely boot from any recent DOS
environment; this was established to a considerable degree of confidence
last time its functionality came up.
The ethernet bootstrap modules are a tossup. They're so obsolete that
they're almost useless, but not quite. I don't believe they should be
built or installed by default, however, as they normally need to be
customised for a particular environment.
Rawboot was a one-off hack and should not be built or installed.
Cdboot should not be built or installed either; it is a template for a
custom tool that's built when making bootable CDROMs. It should be
constructed when the CDROM is being built (as it needs to be populated
according to the needs of the CDROM).
So all you have left are boot0, boot1 and boot2. Given that all of the
rest of the boot process data is being accumulated in /boot, and given
that we're only talking about 8.5k and three files, moving them seems
to make the most sense.
This isn't change for the sake of change. It's an attempt to be
complete and consistent as an altnerative to leaving rotting appendages
lying around. I have far too much to worry about to undertake
makework. 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 Wed Nov 11 14:18:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA10017
for freebsd-current-outgoing; Wed, 11 Nov 1998 14:18:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from silverback.gorilla.net (silverback.gorilla.net [208.128.8.1])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA10010
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 14:18:16 -0800 (PST)
(envelope-from tom@gorilla.net)
Received: from peeper.TOJ.org [208.143.84.133] by silverback.gorilla.net with ESMTP
(SMTPD32-4.07) id ABE82700E0; Wed, 11 Nov 1998 16:12:56 CDT
Received: (from tom@localhost)
by peeper.TOJ.org (8.9.1/8.8.8) id QAA02418
for current@FreeBSD.ORG; Wed, 11 Nov 1998 16:18:09 -0600 (CST)
(envelope-from tom)
Message-ID: <19981111161736.A2411@TOJ.org>
Date: Wed, 11 Nov 1998 16:17:36 -0600
From: Tom Jackson <toj@gorilla.net>
To: current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
References: <9940.910772319@zippy.cdrom.com> <Pine.BSF.4.05.9811110857490.10145-100000@picnic.mat.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.05.9811110857490.10145-100000@picnic.mat.net>; from Chuck Robey on Wed, Nov 11, 1998 at 09:02:11AM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Nov 11, 1998 at 09:02:11AM -0500, Chuck Robey wrote:
>
> Trouble is, with old bootblocks, that "drop boot.conf" trick doesn't
> work, it just hangs. To get the elf kernel booted, you have to update
> the bootblocks, *then* they can use both. Julian's request is dead as
> it stands, you can't do that. To get the elf kernel, you need newer
> bootblocks, which is why I suggested detecting the old ones, and maybe
> refusing to install an elf kernel.
>
Question to you Chuck. Does issuing '/boot/loader' at the boot: prompt
work and have you tried boot.config (!boot.conf) with the /boot/loader
in it?
--
Tom
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 14:28:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA10869
for freebsd-current-outgoing; Wed, 11 Nov 1998 14:28:18 -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 OAA10864
for <freebsd-current@freebsd.org>; Wed, 11 Nov 1998 14:28:14 -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 XAA16644
for freebsd-current@freebsd.org; Wed, 11 Nov 1998 23:27:45 +0100 (CET)
Received: from localhost (blaz@localhost)
by gold.amis.net (8.9.1/8.8.8) with ESMTP id XAA00980
for <freebsd-current@freebsd.org>; Wed, 11 Nov 1998 23:26:58 +0100 (CET)
Date: Wed, 11 Nov 1998 23:26:57 +0100 (CET)
From: Blaz Zupan <blaz@gold.amis.net>
To: freebsd-current@FreeBSD.ORG
Subject: modules vs. LKM's
Message-ID: <Pine.BSF.4.05.9811112325330.895-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
The latest makefile changes install a /usr/bin/linux.sh instead of
/usr/bin/linux. They also install a joy.sh and ibcs2.sh in /usr/bin. I
hope this is not intentional ;)
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 Wed Nov 11 14:29:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA10964
for freebsd-current-outgoing; Wed, 11 Nov 1998 14:29:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from kstreet.interlog.com (kstreet.interlog.com [198.53.146.171])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10957
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 14:29:24 -0800 (PST)
(envelope-from kws@kstreet.interlog.com)
Received: (from kws@localhost)
by kstreet.interlog.com (8.9.1/8.9.1) id RAA00391;
Wed, 11 Nov 1998 17:28:43 -0500 (EST)
(envelope-from kws)
From: Kevin Street <street@iname.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <13898.3995.612543.848374@kstreet.interlog.com>
Date: Wed, 11 Nov 1998 17:28:43 -0500 (EST)
To: Mike Smith <mike@smith.net.au>
Cc: current@FreeBSD.ORG
Subject: Re: boot loader problems with mix of wd and da
In-Reply-To: <199811112033.MAA04864@dingo.cdrom.com>
References: <13883.24586.614752.970999@kstreet.interlog.com>
<199811112033.MAA04864@dingo.cdrom.com>
X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Smith writes:
>This is the same as the old problem that required you to prefix a BIOS
>unit number offset to the 'sd' in the old loader. You need to
>explicitly set $rootdev:
>
> set rootdev=da0s2a
In boot/boot.conf ? It does not help. The kernel still tries to
mount da2s2a as root. This is without anything in boot.config, so
hopefully it's not confused about the bios unit numbers. currdev is
disk3s2a, so it's correct.
>> So, why is currdev set differently in case 1 and case 2?
>Because you've supplied the '2', obviously enough.
heh...obvious...I supplied 2 so loader sets it to disk1 instead of
disk3...yipe!
>> Why does /boot/loader confuse the kernel into thinking there's a da2 on
>> which it might find root?
>Because you haven't told it not to.
well I tried shouting "Yo, kernel, please don't mount root from
devices we don't have" while it was booting, but this didn't seem to help
either :->
--
Kevin Street
street@iName.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 14:33:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA11477
for freebsd-current-outgoing; Wed, 11 Nov 1998 14:33:40 -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 OAA11471
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 14:33:38 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id OAA18764;
Wed, 11 Nov 1998 14:34:08 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
To: Nate Williams <nate@mt.sri.com>
cc: Mike Smith <mike@smith.net.au>, obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 13:59:02 MST."
<199811112059.NAA19049@mt.sri.com>
Date: Wed, 11 Nov 1998 14:34:07 -0800
Message-ID: <18761.910823647@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> statements are flame-bait and provide no content. Moving stuff out of
> /usr/mdec provides *NO* (!!) functionality improvement, just movement.
Would you also advocate moving disklabel from /sbin to /usr/sbin
then? If not, why not?
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 14:35:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA11742
for freebsd-current-outgoing; Wed, 11 Nov 1998 14:35:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11726
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 14:35: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 OAA05716;
Wed, 11 Nov 1998 14:33:01 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811112233.OAA05716@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Kevin Street <street@iname.com>
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: boot loader problems with mix of wd and da
In-reply-to: Your message of "Wed, 11 Nov 1998 17:28:43 EST."
<13898.3995.612543.848374@kstreet.interlog.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 14:33:01 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Mike Smith writes:
> >This is the same as the old problem that required you to prefix a BIOS
> >unit number offset to the 'sd' in the old loader. You need to
> >explicitly set $rootdev:
> >
> > set rootdev=da0s2a
>
> In boot/boot.conf ? It does not help. The kernel still tries to
> mount da2s2a as root. This is without anything in boot.config, so
> hopefully it's not confused about the bios unit numbers. currdev is
> disk3s2a, so it's correct.
Oops, sorry, that should be:
set rootdev=disk0s2a
The syntax is stupid because this is a stupid problem that's very
difficult to solve.
> >> Why does /boot/loader confuse the kernel into thinking there's a da2 on
> >> which it might find root?
> >Because you haven't told it not to.
>
> well I tried shouting "Yo, kernel, please don't mount root from
> devices we don't have" while it was booting, but this didn't seem to help
> either :->
8)
The problem is that we don't have a unified disk naming space, so it's
extremely difficult to discern that "disk2" in BIOS lingo is in fact
"da0" when you go to pass it to the kernel. Probing is Bad and Evil
and I didn't want to go that way. Maybe it's the only way to go
though. 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 Wed Nov 11 14:39:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA12106
for freebsd-current-outgoing; Wed, 11 Nov 1998 14:39:39 -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 OAA12092
for <freebsd-current@FreeBSD.ORG>; Wed, 11 Nov 1998 14:39:37 -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 OAA29717;
Wed, 11 Nov 1998 14:39:13 -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 OAA05147;
Wed, 11 Nov 1998 14:39:12 -0800 (PST)
Received: (from gdonl@localhost)
by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id OAA02098;
Wed, 11 Nov 1998 14:39:11 -0800 (PST)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199811112239.OAA02098@salsa.gv.tsc.tdk.com>
Date: Wed, 11 Nov 1998 14:39:11 -0800
In-Reply-To: Open Systems Networking <opsys@mail.webspan.net>
"Softupdates in current problem.." (Nov 11, 10:53am)
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: Open Systems Networking <opsys@mail.webspan.net>,
freebsd-current@FreeBSD.ORG
Subject: Re: Softupdates in current problem..
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Nov 11, 10:53am, Open Systems Networking wrote:
} Subject: Softupdates in current problem..
}
} Just tried rebuilding a kernel after the latest commits that needed libkvm
} system includes and a few utils rebuilt and installed and was just
} rebuilding the kernel to reboot and ffs_softdep.c breaks on:
}
} ../include -DKERNEL -include opt_global.h -elf
} ../../ufs/ffs/ffs_softdep.c
} ../../ufs/ffs/ffs_softdep.c: In function `softdep_setup_freeblocks':
} ../../ufs/ffs/ffs_softdep.c:1667: structure has no member named `lh_first'
} ../../ufs/ffs/ffs_softdep.c:1668: structure has no member named `lh_first'
How wierd. It's barfing on TAILQ_FIRST(&vp->v_dirtyblkhd), but there
are several other places in this file that use the same expression
that it doesn't complain about. The other warnings are normal for this
file.
I didn't have any problems building a kernel -aout.
If it still doesn't compile after another cvsup, about all I can
suggest is running 'cc -E' on this file with all the same compiler
command line defines and include paths and then dig through the output
to see if you can decipher the problem.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 14:40:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA12314
for freebsd-current-outgoing; Wed, 11 Nov 1998 14:40: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 OAA12306
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 14:40:44 -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 PAA28438;
Wed, 11 Nov 1998 15:40:18 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id PAA19821; Wed, 11 Nov 1998 15:40:17 -0700
Date: Wed, 11 Nov 1998 15:40:17 -0700
Message-Id: <199811112240.PAA19821@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>, Mike Smith <mike@smith.net.au>,
obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <18761.910823647@zippy.cdrom.com>
References: <199811112059.NAA19049@mt.sri.com>
<18761.910823647@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
> > statements are flame-bait and provide no content. Moving stuff out of
> > /usr/mdec provides *NO* (!!) functionality improvement, just movement.
>
> Would you also advocate moving disklabel from /sbin to /usr/sbin
> then? If not, why not?
Works for me! Since you can't boot w/out working boot-blocks, it makes
no sense to depend on disklabel having stuff that it can't get unless
/usr is mounted.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 15:02:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA15108
for freebsd-current-outgoing; Wed, 11 Nov 1998 15:02:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from picnic.mat.net (picnic.mat.net [206.246.122.117])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15096
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 15:02:52 -0800 (PST)
(envelope-from chuckr@mat.net)
Received: from localhost (chuckr@localhost)
by picnic.mat.net (8.9.1/8.8.5) with ESMTP id SAA23267;
Wed, 11 Nov 1998 18:01:26 -0500 (EST)
Date: Wed, 11 Nov 1998 18:01:26 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Tom Jackson <toj@gorilla.net>
cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <19981111161736.A2411@TOJ.org>
Message-ID: <Pine.BSF.4.05.9811111753170.10145-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 Wed, 11 Nov 1998, Tom Jackson wrote:
> On Wed, Nov 11, 1998 at 09:02:11AM -0500, Chuck Robey wrote:
> >
> > Trouble is, with old bootblocks, that "drop boot.conf" trick doesn't
> > work, it just hangs. To get the elf kernel booted, you have to update
> > the bootblocks, *then* they can use both. Julian's request is dead as
> > it stands, you can't do that. To get the elf kernel, you need newer
> > bootblocks, which is why I suggested detecting the old ones, and maybe
> > refusing to install an elf kernel.
> >
> Question to you Chuck. Does issuing '/boot/loader' at the boot: prompt
> work and have you tried boot.config (!boot.conf) with the /boot/loader
> in it?
I did it. It works only if you install bootblocks newer than the ones I
originally had in the machine, from the 2.2.6 cdrom. Those, no, they
don't work at all ... you get to the point where it's saying
bss=[0x0] text=[0x4] (I forget the actual numbers)
and it hangs. Installing the new bootblocks cleared the problem, but if
you do this without the new bootblocks, you're in trouble.
Peter had told me about how to test it without changing boot.conf, so I
knew it was failing before it cut me off from my machine. I used
disklabel to install the new boot stuff, and then there were no bugs
left, and I'm now running elf.
I figured that the chances of others having bootblocks too old for elf
kernels, and not knowing about the need to update the bootblocks, is
probably pretty high. I don't know if you just change boot.conf, with
the old boot blocks, if you cut your throat (need a floppy boot to fix),
but I think so. That's the worry that bothered me.
----------------------------+-----------------------------------------------
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 Nov 11 15:07:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA15556
for freebsd-current-outgoing; Wed, 11 Nov 1998 15:07:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from picnic.mat.net (picnic.mat.net [206.246.122.117])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15550
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 15:07:22 -0800 (PST)
(envelope-from chuckr@mat.net)
Received: from localhost (chuckr@localhost)
by picnic.mat.net (8.9.1/8.8.5) with ESMTP id SAA23271;
Wed, 11 Nov 1998 18:04:16 -0500 (EST)
Date: Wed, 11 Nov 1998 18:04:15 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Nate Williams <nate@mt.sri.com>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, Mike Smith <mike@smith.net.au>,
obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <199811112240.PAA19821@mt.sri.com>
Message-ID: <Pine.BSF.4.05.9811111802590.10145-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 Wed, 11 Nov 1998, Nate Williams wrote:
> > > statements are flame-bait and provide no content. Moving stuff out of
> > > /usr/mdec provides *NO* (!!) functionality improvement, just movement.
> >
> > Would you also advocate moving disklabel from /sbin to /usr/sbin
> > then? If not, why not?
>
> Works for me! Since you can't boot w/out working boot-blocks, it makes
> no sense to depend on disklabel having stuff that it can't get unless
> /usr is mounted.
No, you forget, there's 2 reasons to have things in /. One, they're
needed for boot. Two, they qualify as emergency repair tools.
Diskalbel falls into the 2nd category (note I agree with Nate's original
position here).
>
>
> Nate
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
>
----------------------------+-----------------------------------------------
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 Nov 11 15:13:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA16088
for freebsd-current-outgoing; Wed, 11 Nov 1998 15:13: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 PAA16078
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 15:13:37 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca9-181.ix.netcom.com [209.109.236.181]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id PAA26859; Wed, 11 Nov 1998 15:12:59 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id PAA16909; Wed, 11 Nov 1998 15:12:56 -0800 (PST)
Date: Wed, 11 Nov 1998 15:12:56 -0800 (PST)
Message-Id: <199811112312.PAA16909@silvia.hip.berkeley.edu>
To: chuckr@mat.net
CC: nate@mt.sri.com, jkh@zippy.cdrom.com, mike@smith.net.au, obrien@NUXI.com,
current@FreeBSD.ORG
In-reply-to: <Pine.BSF.4.05.9811111802590.10145-100000@picnic.mat.net>
(message from Chuck Robey on Wed, 11 Nov 1998 18:04:15 -0500 (EST))
Subject: Re: Is it soup yet? :-)
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* No, you forget, there's 2 reasons to have things in /. One, they're
* needed for boot. Two, they qualify as emergency repair tools.
* Diskalbel falls into the 2nd category (note I agree with Nate's original
* position here).
And the bootblocks might be needed for emergency repair. Consider, if
you have a disk that's failing all over the place, you managed to boot
single-user from it (or booted from a floppy) and mounted root, you
now need to somehow set up a bootable FreeBSD installation on your
second hard drive. You are toast if the bootblocks are in the broken
/usr.
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 15:13:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA16092
for freebsd-current-outgoing; Wed, 11 Nov 1998 15:13: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 PAA16080
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 15:13: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 QAA28738;
Wed, 11 Nov 1998 16:13:06 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id QAA20091; Wed, 11 Nov 1998 16:13:05 -0700
Date: Wed, 11 Nov 1998 16:13:05 -0700
Message-Id: <199811112313.QAA20091@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: Chuck Robey <chuckr@mat.net>
Cc: Nate Williams <nate@mt.sri.com>, "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Mike Smith <mike@smith.net.au>, obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <Pine.BSF.4.05.9811111802590.10145-100000@picnic.mat.net>
References: <199811112240.PAA19821@mt.sri.com>
<Pine.BSF.4.05.9811111802590.10145-100000@picnic.mat.net>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > > > statements are flame-bait and provide no content. Moving stuff out of
> > > > /usr/mdec provides *NO* (!!) functionality improvement, just movement.
> > >
> > > Would you also advocate moving disklabel from /sbin to /usr/sbin
> > > then? If not, why not?
> >
> > Works for me! Since you can't boot w/out working boot-blocks, it makes
> > no sense to depend on disklabel having stuff that it can't get unless
> > /usr is mounted.
>
> No, you forget, there's 2 reasons to have things in /. One, they're
> needed for boot. Two, they qualify as emergency repair tools.
But, if you can't repair the system w/out mounting /usr, then
disklabel(8)'s presence on the root FS buys you nothing. That and the
fact that you wouldn't be running disklabel on a system that only has a
working / partition.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 15:24:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA17409
for freebsd-current-outgoing; Wed, 11 Nov 1998 15:24:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17404
for <freebsd-current@FreeBSD.ORG>; Wed, 11 Nov 1998 15:24:56 -0800 (PST)
(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
by lor.watermarkgroup.com (8.8.8/8.8.8) id SAA15367;
Wed, 11 Nov 1998 18:24:03 -0500 (EST)
(envelope-from luoqi)
Date: Wed, 11 Nov 1998 18:24:03 -0500 (EST)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <199811112324.SAA15367@lor.watermarkgroup.com>
To: Don.Lewis@tsc.tdk.com, freebsd-current@FreeBSD.ORG, opsys@mail.webspan.net
Subject: Re: Softupdates in current problem..
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On Nov 11, 10:53am, Open Systems Networking wrote:
> } Subject: Softupdates in current problem..
> }
> } Just tried rebuilding a kernel after the latest commits that needed libkvm
> } system includes and a few utils rebuilt and installed and was just
> } rebuilding the kernel to reboot and ffs_softdep.c breaks on:
> }
> } ../include -DKERNEL -include opt_global.h -elf
> } ../../ufs/ffs/ffs_softdep.c
>
> } ../../ufs/ffs/ffs_softdep.c: In function `softdep_setup_freeblocks':
> } ../../ufs/ffs/ffs_softdep.c:1667: structure has no member named `lh_first'
> } ../../ufs/ffs/ffs_softdep.c:1668: structure has no member named `lh_first'
>
> How wierd. It's barfing on TAILQ_FIRST(&vp->v_dirtyblkhd), but there
> are several other places in this file that use the same expression
> that it doesn't complain about. The other warnings are normal for this
> file.
>
> I didn't have any problems building a kernel -aout.
>
> If it still doesn't compile after another cvsup, about all I can
> suggest is running 'cc -E' on this file with all the same compiler
> command line defines and include paths and then dig through the output
> to see if you can decipher the problem.
>
Chris has a stale copy of ffs_softdep.c (it's better to make it a symlink
to contrib/sys/softupdates/ffs_softdep.c). A couple of weeks ago, the
clean/dirty buf queues were changed from LISTQ to TAILQ.
-lq
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 15:45:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA19942
for freebsd-current-outgoing; Wed, 11 Nov 1998 15:45:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19918
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 15:44:55 -0800 (PST)
(envelope-from abial@nask.pl)
Received: from localhost (abial@localhost)
by korin.warman.org.pl (8.9.1/8.8.5) with ESMTP id AAA18077;
Thu, 12 Nov 1998 00:45:45 +0100 (CET)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Thu, 12 Nov 1998 00:45:44 +0100 (CET)
From: Andrzej Bialecki <abial@nask.pl>
X-Sender: abial@korin.warman.org.pl
To: =?ISO-8859-2?Q?S=F8ren_Schmidt?= <sos@freebsd.dk>
cc: daeron@Wit401305.student.utwente.nl, shawn@cpl.net, osa@etrust.ru,
current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <199811112000.VAA00590@freebsd.dk>
Message-ID: <Pine.BSF.4.02A.9811120040270.12730-100000@korin.warman.org.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-2
Content-Transfer-Encoding: 8BIT
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 11 Nov 1998, Søren Schmidt wrote:
> It seems Andrzej Bialecki wrote:
> > Yes, I've got the diffs against relatively fresh current. BTW, I asked
> > this question on -emulation, but got back a profound silence... Can we/
> > should we incorporate this patch, and hide it under a kernel option, say
> > PROCFS_CMDLINE? The life would be soooo easier for people new to our linux
> > emulation...
>
> Hmm, if we should have a Linsux compatible /proc, it really should be
> a beast mounted on /compat/linux/proc. If you provide this, I'm sure
> it will be received with open arms :)
I proposed some option which is within my reach (considering my skills and
time available). If not - well, the issue will have to wait until either
my abilities become appropriate, or someone else will take it over. As it
is now, I propose the above hack as a temporary solution.
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 Wed Nov 11 15:49:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA20384
for freebsd-current-outgoing; Wed, 11 Nov 1998 15:49:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from picnic.mat.net (picnic.mat.net [206.246.122.117])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20377;
Wed, 11 Nov 1998 15:49:38 -0800 (PST)
(envelope-from chuckr@mat.net)
Received: from localhost (chuckr@localhost)
by picnic.mat.net (8.9.1/8.8.5) with ESMTP id SAA23356;
Wed, 11 Nov 1998 18:48:15 -0500 (EST)
Date: Wed, 11 Nov 1998 18:48:15 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Satoshi Asami <asami@FreeBSD.ORG>
cc: nate@mt.sri.com, jkh@zippy.cdrom.com, mike@smith.net.au, obrien@NUXI.com,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <199811112312.PAA16909@silvia.hip.berkeley.edu>
Message-ID: <Pine.BSF.4.05.9811111846200.10145-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 Wed, 11 Nov 1998, Satoshi Asami wrote:
> * No, you forget, there's 2 reasons to have things in /. One, they're
> * needed for boot. Two, they qualify as emergency repair tools.
> * Diskalbel falls into the 2nd category (note I agree with Nate's original
> * position here).
>
> And the bootblocks might be needed for emergency repair. Consider, if
> you have a disk that's failing all over the place, you managed to boot
> single-user from it (or booted from a floppy) and mounted root, you
> now need to somehow set up a bootable FreeBSD installation on your
> second hard drive. You are toast if the bootblocks are in the broken
> /usr.
No, Nate's got a point. How many times have you hand-mounted /usr?
I know darned well I have (I *hate* using ex to edit files!). As long
as mount (+friends) are under /, then disklabel's available.
>
> Satoshi
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
>
----------------------------+-----------------------------------------------
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 Nov 11 15:53:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA20824
for freebsd-current-outgoing; Wed, 11 Nov 1998 15:53:47 -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 PAA20811
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 15:53:45 -0800 (PST)
(envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca9-181.ix.netcom.com [209.109.236.181]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id PAA26915; Wed, 11 Nov 1998 15:53:06 -0800 (PST)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id PAA17123; Wed, 11 Nov 1998 15:53:02 -0800 (PST)
Date: Wed, 11 Nov 1998 15:53:02 -0800 (PST)
Message-Id: <199811112353.PAA17123@silvia.hip.berkeley.edu>
To: chuckr@mat.net
CC: nate@mt.sri.com, jkh@zippy.cdrom.com, mike@smith.net.au, obrien@NUXI.com,
current@FreeBSD.ORG
In-reply-to: <Pine.BSF.4.05.9811111846200.10145-100000@picnic.mat.net>
(message from Chuck Robey on Wed, 11 Nov 1998 18:48:15 -0500 (EST))
Subject: Re: Is it soup yet? :-)
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
* No, Nate's got a point. How many times have you hand-mounted /usr?
* I know darned well I have (I *hate* using ex to edit files!). As long
* as mount (+friends) are under /, then disklabel's available.
I'm not disputing that. My point is that bootblocks aid disklabel's
ability to conduct emergency repair, so they should be in root too.
Satoshi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 15:54:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA20964
for freebsd-current-outgoing; Wed, 11 Nov 1998 15:54:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20954
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 15:54:28 -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 PAA06123;
Wed, 11 Nov 1998 15:50:26 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811112350.PAA06123@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Nate Williams <nate@mt.sri.com>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, Mike Smith <mike@smith.net.au>,
obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 15:40:17 MST."
<199811112240.PAA19821@mt.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 15:50:26 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > > statements are flame-bait and provide no content. Moving stuff out of
> > > /usr/mdec provides *NO* (!!) functionality improvement, just movement.
> >
> > Would you also advocate moving disklabel from /sbin to /usr/sbin
> > then? If not, why not?
>
> Works for me! Since you can't boot w/out working boot-blocks, it makes
> no sense to depend on disklabel having stuff that it can't get unless
> /usr is mounted.
Disklabel doesn't depend on the files unless you're trying to make
something bootable. On the other hand, you may need disklabel in order
to recover the filesystem holding /usr.
Moving disklabel is indeed change for change's sake, and gratuitous to
boot. Much of this talk of bloat is nothing but a joke, since in the
common case disk space costs less than talk. In the non-common case,
you're going to customise anyway, so it doesn't matter where things
"normally" are.
--
\\ 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 Nov 11 15:56:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA21189
for freebsd-current-outgoing; Wed, 11 Nov 1998 15:56:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21167
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 15:56:08 -0800 (PST)
(envelope-from drosih@rpi.edu)
Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47])
by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id SAA66566
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 18:56:43 -0500
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: drosih@pop1.rpi.edu
Message-Id: <v04011706b26fd32f1110@[128.113.24.47]>
In-Reply-To: <199811112312.PAA16909@silvia.hip.berkeley.edu>
References: <Pine.BSF.4.05.9811111802590.10145-100000@picnic.mat.net>
(message from Chuck Robey on Wed, 11 Nov 1998 18:04:15 -0500 (EST))
Date: Wed, 11 Nov 1998 18:55:52 -0500
To: current@FreeBSD.ORG
From: Garance A Drosihn <drosih@rpi.edu>
Subject: Re: Is it soup yet? :-)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
So, to get back to the "is this soup yet?" question, I guess things
must be pretty far along if the only thing anyone here is worried
about is the location of three files on the directory structure.
My own feeling is that given the files in question, /boot is
probably as good a place as any, and certainly more memorable
to me (as a "casual" freebsd user) than /usr/mdec/ ever was.
---
Garance Alistair Drosehn = gad@eclipse.its.rpi.edu
Senior Systems Programmer or drosih@rpi.edu
Rensselaer Polytechnic Institute
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 15:56:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA21216
for freebsd-current-outgoing; Wed, 11 Nov 1998 15:56:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21210
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 15:56: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 TAA27364;
Wed, 11 Nov 1998 19:54:24 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 11 Nov 1998 19:54:23 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Andrzej Bialecki <abial@nask.pl>
cc: =?ISO-8859-2?Q?S=F8ren_Schmidt?= <sos@freebsd.dk>,
daeron@Wit401305.student.utwente.nl, shawn@cpl.net, osa@etrust.ru,
current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <Pine.BSF.4.02A.9811120040270.12730-100000@korin.warman.org.pl>
Message-ID: <Pine.BSF.4.05.9811111952370.337-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8BIT
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 12 Nov 1998, Andrzej Bialecki wrote:
> On Wed, 11 Nov 1998, Søren Schmidt wrote:
>
> > It seems Andrzej Bialecki wrote:
>
> > > Yes, I've got the diffs against relatively fresh current. BTW, I asked
> > > this question on -emulation, but got back a profound silence... Can we/
> > > should we incorporate this patch, and hide it under a kernel option, say
> > > PROCFS_CMDLINE? The life would be soooo easier for people new to our linux
> > > emulation...
> >
> > Hmm, if we should have a Linsux compatible /proc, it really should be
> > a beast mounted on /compat/linux/proc. If you provide this, I'm sure
> > it will be received with open arms :)
>
> I proposed some option which is within my reach (considering my skills and
> time available). If not - well, the issue will have to wait until either
> my abilities become appropriate, or someone else will take it over. As it
> is now, I propose the above hack as a temporary solution.
Just curious, but what exactly does that '/proc/*/cmdline' thing
"do", and is there any reason why it is inappropriate for it to be a
standard part of our /proc?
When talkign with friends that use Linux, and talking about our
/proc file system, they think its hilarious that I can't go into proc and
find out what irqs are being used by the system...maybe I'm missing
something, but about the only way I can do it currently is to look through
dmesg output? Is there another way?
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 Wed Nov 11 16:08:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA24304
for freebsd-current-outgoing; Wed, 11 Nov 1998 16:08:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24285
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 16:08:23 -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 BAA24622;
Thu, 12 Nov 1998 01:09:39 +0100 (CET)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Thu, 12 Nov 1998 01:09:39 +0100 (CET)
From: Andrzej Bialecki <abial@nask.pl>
X-Sender: abial@korin.warman.org.pl
To: The Hermit Hacker <scrappy@hub.org>
cc: =?ISO-8859-2?Q?S=F8ren_Schmidt?= <sos@freebsd.dk>,
daeron@Wit401305.student.utwente.nl, shawn@cpl.net, osa@etrust.ru,
current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <Pine.BSF.4.05.9811111952370.337-100000@thelab.hub.org>
Message-ID: <Pine.BSF.4.02A.9811120104460.12730-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 Wed, 11 Nov 1998, The Hermit Hacker wrote:
> Just curious, but what exactly does that '/proc/*/cmdline' thing
> "do", and is there any reason why it is inappropriate for it to be a
> standard part of our /proc?
It\s just a copy of the argv[0]. Why the programs can\t access their
argv[0] instead is beyond me - looks like a very stupid thing...
>
> When talkign with friends that use Linux, and talking about our
> /proc file system, they think its hilarious that I can't go into proc and
> find out what irqs are being used by the system...maybe I'm missing
> something, but about the only way I can do it currently is to look through
> dmesg output? Is there another way?
>From my POV, it's hilarious to go to /proc to read the hardware
parameters of the system - the name "proc" is supposed to mean "info
related to processes", isn't it?
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 Wed Nov 11 16:23:17 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA26281
for freebsd-current-outgoing; Wed, 11 Nov 1998 16:23:17 -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 QAA26270;
Wed, 11 Nov 1998 16:23:08 -0800 (PST)
(envelope-from wosch@panke.de.freebsd.org)
Received: (from uucp@localhost)
by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id BAA05923;
Thu, 12 Nov 1998 01:22:46 +0100 (CET)
(envelope-from wosch@panke.de.freebsd.org)
Received: (from wosch@localhost)
by campa.panke.de.freebsd.org (8.8.8/8.8.8) id XAA02270;
Wed, 11 Nov 1998 23:25:17 +0100 (MET)
(envelope-from wosch)
Message-ID: <19981111232515.C716@panke.de.freebsd.org>
Date: Wed, 11 Nov 1998 23:25:15 +0100
From: Wolfram Schneider <wosch@panke.de.freebsd.org>
To: current@FreeBSD.ORG
Cc: jraynard@FreeBSD.ORG
Subject: sfio does not work on elf machines
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I just tested sfio on bento (3.0-current, elf). Some
tests failed which worked on my home machine, 3.0-current a.out
---- tappend.c ----
Line=45: Bad getr2
failed
---- tmprocess.c ----
./runtest: line 44: 5666 Segmentation fault (core dumped) ./t
failed
Wolfram
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 16:27:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA26638
for freebsd-current-outgoing; Wed, 11 Nov 1998 16:27:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from silverback.gorilla.net (silverback.gorilla.net [208.128.8.1])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA26632
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 16:27:22 -0800 (PST)
(envelope-from tom@gorilla.net)
Received: from peeper.TOJ.org [208.143.84.78] by silverback.gorilla.net with ESMTP
(SMTPD32-4.07) id AA2A7400C4; Wed, 11 Nov 1998 18:22:02 CDT
Received: (from tom@localhost)
by peeper.TOJ.org (8.9.1/8.8.8) id SAA02703
for current@FreeBSD.ORG; Wed, 11 Nov 1998 18:27:17 -0600 (CST)
(envelope-from tom)
Message-ID: <19981111182554.B2411@TOJ.org>
Date: Wed, 11 Nov 1998 18:25:54 -0600
From: Tom Jackson <toj@gorilla.net>
To: current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
References: <19981111161736.A2411@TOJ.org> <Pine.BSF.4.05.9811111753170.10145-100000@picnic.mat.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.05.9811111753170.10145-100000@picnic.mat.net>; from Chuck Robey on Wed, Nov 11, 1998 at 06:01:26PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Nov 11, 1998 at 06:01:26PM -0500, Chuck Robey wrote:
> On Wed, 11 Nov 1998, Tom Jackson wrote:
>...
> I figured that the chances of others having bootblocks too old for elf
> kernels, and not knowing about the need to update the bootblocks, is
Point well taken
> probably pretty high. I don't know if you just change boot.conf, with
> the old boot blocks, if you cut your throat (need a floppy boot to fix),
> but I think so. That's the worry that bothered me.
>
I've had a very good experience with this since E-day by following Mike,
John, Peter, and Robert's advice and doing it in little steps :). My
bootblocks have stayed up to date due to the new boot.help and advice from
the knowledgable.
I had never used boot.conf[ig] before. When I had tried to use /boot.conf
to direct the process to /boot/loader, *it failed* and just tried to load
/kernel direct. This was when I found I had to use /boot.config, and this
did work. This was my main point.
Later,
--
Tom
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 16:38:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA27784
for freebsd-current-outgoing; Wed, 11 Nov 1998 16:38:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail13.digital.com (mail13.digital.com [192.208.46.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27774
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 16:38:04 -0800 (PST)
(envelope-from Reggie.Perry@digital.com)
Received: from rust.zso.dec.com (rust.zso.dec.com [16.64.0.1])
by mail13.digital.com (8.9.1a/8.9.1/WV2.0a) with SMTP id TAA16958
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 19:37:34 -0500 (EST)
Received: from zsoexc1.zso.dec.com by rust.zso.dec.com (5.65/DECwest-CLUSTRIX-mwd-12Dec94)
id AA28136; Wed, 11 Nov 1998 16:37:31 -0800
Received: by zsoexc1.zso.dec.com with Internet Mail Service (5.5.1960.3)
id <W1CA3X52>; Wed, 11 Nov 1998 16:34:20 -0800
Message-Id: <69CAF7F9AF57D2118D9A0000F881B4DD02F354@zsoexc1.zso.dec.com>
From: Reggie Perry <Reggie.Perry@digital.com>
Cc: "'current@FreeBSD.ORG'" <current@FreeBSD.ORG>
Subject: RE: Is it soup yet? :-)
Date: Wed, 11 Nov 1998 16:34:19 -0800
X-Mailer: Internet Mail Service (5.5.1960.3)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Add Ultrix to the "Has it" list...
-Reggie
-----Original Message-----
From: owner-freebsd-current@FreeBSD.ORG
[mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of sthaug@nethelp.no
Sent: Wednesday, November 11, 1998 1:07 AM
To: will@iki.fi
Cc: jkh@zippy.cdrom.com; current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
> > 3. /usr/mdec is a silly-assed name. Who thought of it? What does it
even
>
> The mdec name certainly isn't FreeBSD-specific, changing it would add
> to the difficulty of finding things based on a "general knowledge" of
> Unix-like systems.
Has it: FreeBSD, NetBSD, possibly OpenBSD.
Doesn't have it: Solaris 2, HP-UX, Digital Unix, BSD/OS, RedHat 5.2
I'm afraid there isn't much "general" about /usr/mdec.
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
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 16:56:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA29825
for freebsd-current-outgoing; Wed, 11 Nov 1998 16:56:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mx2.ews.uiuc.edu (mx2.ews.uiuc.edu [130.126.161.238])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29774
for <current@freebsd.org>; Wed, 11 Nov 1998 16:56:28 -0800 (PST)
(envelope-from locke@mcs.net)
Received: from petedorm (isr3193.urh.uiuc.edu [130.126.64.183])
by mx2.ews.uiuc.edu (8.8.8/8.8.8) with SMTP id SAA16046
for <current@freebsd.org>; Wed, 11 Nov 1998 18:55:26 -0600
Message-Id: <3.0.5.32.19981111185527.009feba0@popmail.mcs.net>
X-Sender: locke@popmail.mcs.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Wed, 11 Nov 1998 18:55:27 -0600
To: current@FreeBSD.ORG
From: Peter Johnson <locke@mcs.net>
Subject: Re: aout-to-elf-build failure after freebsd.cf?
In-Reply-To: <Pine.BSF.3.95.981111151540.19367A-100000@Venus.mcs.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Oops, sorry about this one folks.. building it w/o -j8 worked (although it
was quite slow). Interesting points to note, however:
1. Building "world" with -j8 works fine.
2. Building aout-to-elf-build w/o -j8 finishes the exact same way, but
doesn't display the error messages (eg, the last output line is "chmod 444
freebsd.cf"). So why the errors with -j8?
Thanks,
Peter Johnson
locke@mcs.net
(side note: sorry about the name on the original message.. wasn't paying
attention to my mailer config at the time I was writing the message :)
At 03:24 PM 11/11/98 -0600, Peter Johnson wrote:
>
>Decided to upgrade my -current aout system (cvsupped yesterday) to elf
>(cvsupped today around 1) using make aout-to-elf-build. I'm running SMP
>w/o softupdates. I deleted the /usr/obj tree of files before building.
>Running "make -j8 aout-to-elf-build" results (eventually :) in the
>following error:
>
>--- wcd_mod.o ---
>ld -r -aout -o tmp.o wcd.o
>rm -f symb.tmp
>for i in _wcd_mod ; do echo $i >> symb.tmp ; done
>symorder -c symb.tmp tmp.o
>rm -f symb.tmp
>my tmp.o wcd_mod.o
>===> etc
>--- all ---
>===> etc/sendmail
>--- freebsd.cf ---
>rm -f freebsd.cf
>(cd /usr/src/etc/sendmail && m4
>-D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/sendmail/cf/
>/usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 freebsd.mc) >
>freebsd.cf
>chmod 444 freebsd.cf
>1 error
>*** Error code 2
>1 error
>#
-------------------------------------
Peter Johnson
-------------------------------------
locke@mcs.net
http://locke.home.ml.org
PGP Keys available from above address.
-------------------------------------
Freelance C/C++/Java/Pascal/Asm programmer
for DJGPP, Borland, and Watcom compilers
Member of BiLogic demo group
-> http://BiLogic.home.ml.org/
-------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 16:58:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA00238
for freebsd-current-outgoing; Wed, 11 Nov 1998 16:58:51 -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 QAA00220;
Wed, 11 Nov 1998 16:58:48 -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 QAA23741;
Wed, 11 Nov 1998 16:58:20 -0800 (PST)
(envelope-from dwhite@resnet.uoregon.edu)
Date: Wed, 11 Nov 1998 16:58:19 -0800 (PST)
From: Doug White <dwhite@resnet.uoregon.edu>
To: Florian Nigsch <flo@ganymed.org>
cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Upgrade from 2.2-STABLE to -CURRENT
In-Reply-To: <3.0.32.19981111195130.0068d1d0@triton>
Message-ID: <Pine.BSF.4.03.9811111653530.16040-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, 11 Nov 1998, Florian Nigsch wrote:
> Hello!
>
> I have experienced a little problem. In fact, it's a serious problem: :)
>
> I keep pace with the sourcecodechanges with the CVSup mechanism, and so i
> wanted to upgrade my FreeBSD 2.2-STABLE (2.2.7) system to -CURRENT. I read
> some docs and Makefiles, found out that the best i could do was to try a
> "make aout-to-elf" ind /usr/src.
> Now, what I ended up with was the following:
How current a -CURRENT?
> cp strip maybe_stripped
> strip maybe_stripped
> *** Error code 1
> ...and five more "*** Error code 1".
Hm, it's running the wrong strip(1), I'm guessing. Revision 1.9 of
strip's Makefile claims to fix this bug.
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 Wed Nov 11 17:01:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA00484
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:01: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 RAA00479
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 17:01:25 -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.1/8.9.1/Spinner) with ESMTP id JAA13377;
Thu, 12 Nov 1998 09:00:32 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811120100.JAA13377@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Julian Elischer <julian@whistle.com>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 11:29:54 PST."
<Pine.BSF.3.95.981111112705.16498A-100000@current1.whistle.com>
Date: Thu, 12 Nov 1998 09:00:32 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Julian Elischer wrote:
> we can't replace the bootblocks.. the owners of these machines in every
> continent can't do that.. :-)
>
>
> we will probably be dropping in a 3rd stage loader
> made in a.out, called 'kernel'
>
> the new kernel will probably be called elfkernel or similar (ekernel?)
Call be crazy, but I think I'd almost like to move the "real" kernel to
/boot/kernel, providing the search paths were ok.
> julian
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 17:06:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA00803
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:06:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from picnic.mat.net (picnic.mat.net [206.246.122.117])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00778
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 17:06:00 -0800 (PST)
(envelope-from chuckr@mat.net)
Received: from localhost (chuckr@localhost)
by picnic.mat.net (8.9.1/8.8.5) with ESMTP id UAA23544;
Wed, 11 Nov 1998 20:04:36 -0500 (EST)
Date: Wed, 11 Nov 1998 20:04:36 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Peter Johnson <locke@mcs.net>
cc: current@FreeBSD.ORG
Subject: Re: aout-to-elf-build failure after freebsd.cf?
In-Reply-To: <3.0.5.32.19981111185527.009feba0@popmail.mcs.net>
Message-ID: <Pine.BSF.4.05.9811111959220.10145-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 Wed, 11 Nov 1998, Peter Johnson wrote:
> Oops, sorry about this one folks.. building it w/o -j8 worked (although it
> was quite slow). Interesting points to note, however:
>
> 1. Building "world" with -j8 works fine.
> 2. Building aout-to-elf-build w/o -j8 finishes the exact same way, but
> doesn't display the error messages (eg, the last output line is "chmod 444
> freebsd.cf"). So why the errors with -j8?
This was a pathing error with the legacy build, and no longer exists
with current ... fixed, I think, in Makefile.inc0 rev 1.9. You can
either update, or just drop -j. Sure was a major PITA until it was
found. Luoqi Chen found it (all I found was a new collection of ways to
panic a machine).
>
> Thanks,
>
> Peter Johnson
> locke@mcs.net
>
> (side note: sorry about the name on the original message.. wasn't paying
> attention to my mailer config at the time I was writing the message :)
>
> At 03:24 PM 11/11/98 -0600, Peter Johnson wrote:
> >
> >Decided to upgrade my -current aout system (cvsupped yesterday) to elf
> >(cvsupped today around 1) using make aout-to-elf-build. I'm running SMP
> >w/o softupdates. I deleted the /usr/obj tree of files before building.
> >Running "make -j8 aout-to-elf-build" results (eventually :) in the
> >following error:
> >
> >--- wcd_mod.o ---
> >ld -r -aout -o tmp.o wcd.o
> >rm -f symb.tmp
> >for i in _wcd_mod ; do echo $i >> symb.tmp ; done
> >symorder -c symb.tmp tmp.o
> >rm -f symb.tmp
> >my tmp.o wcd_mod.o
> >===> etc
> >--- all ---
> >===> etc/sendmail
> >--- freebsd.cf ---
> >rm -f freebsd.cf
> >(cd /usr/src/etc/sendmail && m4
> >-D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/sendmail/cf/
> >/usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 freebsd.mc) >
> >freebsd.cf
> >chmod 444 freebsd.cf
> >1 error
> >*** Error code 2
> >1 error
> >#
>
> -------------------------------------
> Peter Johnson
> -------------------------------------
> locke@mcs.net
> http://locke.home.ml.org
> PGP Keys available from above address.
> -------------------------------------
> Freelance C/C++/Java/Pascal/Asm programmer
> for DJGPP, Borland, and Watcom compilers
> Member of BiLogic demo group
> -> http://BiLogic.home.ml.org/
> -------------------------------------
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
>
----------------------------+-----------------------------------------------
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 Nov 11 17:15:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA01571
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:15:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ifi.uio.no (ifi.uio.no [129.240.64.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01554
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 17:15:12 -0800 (PST)
(envelope-from dag-erli@ifi.uio.no)
Received: from grjottunagard.ifi.uio.no (2602@grjottunagard.ifi.uio.no [129.240.64.131])
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id CAA10934;
Thu, 12 Nov 1998 02:14:28 +0100 (MET)
Received: (from dag-erli@localhost) by grjottunagard.ifi.uio.no ; Thu, 12 Nov 1998 02:14:28 +0100 (MET)
Mime-Version: 1.0
To: Peter Wemm <peter@netplex.com.au>
Cc: Mike Smith <mike@smith.net.au>, "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
References: <199811110513.NAA08424@spinner.netplex.com.au>
Organization: University of Oslo, Department of Informatics
X-url: http://www.stud.ifi.uio.no/~dag-erli/
X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list
X-disclaimer-1: The views expressed in this article are mine alone, and do
X-disclaimer-2: not necessarily coincide with those of any organisation or
X-disclaimer-3: company with which I am or have been affiliated.
X-Stop-Spam: http://www.cauce.org/
From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= )
Date: 12 Nov 1998 02:14:27 +0100
In-Reply-To: Peter Wemm's message of "Wed, 11 Nov 1998 13:13:11 +0800"
Message-ID: <xzpogqdvhjg.fsf@grjottunagard.ifi.uio.no>
Lines: 11
X-Mailer: Gnus v5.5/Emacs 19.34
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA01567
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Peter Wemm <peter@netplex.com.au> writes:
> Oh, one other thing.. libdisk is built by doing a file2c of /usr/mdec/
> boot1/boot2 and compiling it in. It is using the *old* boot code, because
> libdisk is built before src/sys/boot in a 'make world'.
Can't it be hacked to read the boot blocks from /boot/boot[12] at run
time?
DES
--
Dag-Erling Smørgrav - dag-erli@ifi.uio.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 17:16:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA01865
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:16:45 -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 RAA01852;
Wed, 11 Nov 1998 17:16:38 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id BAA02685;
Thu, 12 Nov 1998 01:06:34 GMT
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1])
by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id BAA04676;
Thu, 12 Nov 1998 01:08:06 GMT
(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199811120108.BAA04676@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Dmitry Valdov <dv@dv.ru>
cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
In-reply-to: Your message of "Thu, 12 Nov 1998 00:00:00 +0300."
<Pine.BSF.4.02A.9811112357130.646-100000@home.dv.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 12 Nov 1998 01:08:05 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Are you doing anything funny with ``hostname'' on your machine ?
The only reports I've heard where ppp hangs at startup is when your
``hostname'' won't resolve (see http://www.FreeBSD.org/FAQ/userppp.html).
If this isn't the problem, I'd appreciate if you could build ppp with
-g and when it hangs, run ``gdb -p whatever'' and do a ``bt''.
Cheers.
> I've just tried to put
> "delete! default" in ppp.conf file and it has no effect. ppp hangs when
> default route exists.
>
>
> On Wed, 11 Nov 1998, Dmitry Valdov wrote:
>
> >
> >
> > ---------- Forwarded message ----------
> > Date: Tue, 10 Nov 1998 21:40:53 +0000
> > From: Brian Somers <brian@Awfulhak.org>
> > To: Jason Fesler <jfesler@gigo.com>
> > Cc: Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
> > Dmitry Valdov <dv@dv.ru>, Brian Somers <brian@FreeBSD.ORG>,
> > current@FreeBSD.ORG
> > Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
> >
> > > > Sorry for the "implicit bug report", Brian, but I've been meaning to track
> > > > this down for a long time and make sure it's not user error. I often see this
> > >
> > > I've had this since the 2.2.2 days when I first started running ppp.
> > > After a while (hours, days, weeks - random) either carrier isn't noticed
> > > as being missing, or all outgoing packets don't cross the serial cable to
> > > to the other side. After a while I kinda gave up.
> >
> > Ppp won't expect carrier if it's not detected when ppp starts doing
> > LCP. This allows null-modem cables without the correct wiring to
> > work.
> >
> > As I've said to a couple of these posts - enable debug logging and
> > you'll see the carrier status reported every second. You can also
> > ``show modem'' to see what things look like.
> >
> > > I now every few minutes fping a few hosts on the nearby remote side. If
> > > they _all_ fail (a good 10 second timeout is given) then I kill -9 the ppp
> > > session, wait 2 seconds, then restart ppp. It's caught every strange
> > > random bug on either side soon enough that I no longer have to try and
> > > call home and walk the wife through ppp..
> >
> > Ppp should be a lot more reliable these days.
--
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 Wed Nov 11 17:18:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA01989
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:18:34 -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 RAA01984
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 17:18:33 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id RAA05949;
Wed, 11 Nov 1998 17:18:28 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
To: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= )
cc: Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "12 Nov 1998 02:14:27 +0100."
<xzpogqdvhjg.fsf@grjottunagard.ifi.uio.no>
Date: Wed, 11 Nov 1998 17:18:26 -0800
Message-ID: <5945.910833506@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Can't it be hacked to read the boot blocks from /boot/boot[12] at run
> time?
Yeah, that's not even a bad idea. Send diffs! :-)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 17:19:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA02047
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:19:06 -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 RAA02033;
Wed, 11 Nov 1998 17:19:00 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id BAA02965;
Thu, 12 Nov 1998 01:11:05 GMT
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1])
by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id BAA04700;
Thu, 12 Nov 1998 01:12:37 GMT
(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199811120112.BAA04700@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Dmitry Valdov <dv@dv.ru>
cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
In-reply-to: Your message of "Thu, 12 Nov 1998 00:21:16 +0300."
<Pine.BSF.4.02A.9811120012480.757-100000@home.dv.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 12 Nov 1998 01:12:37 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In the log, does it mention something like:
deflink: /dev/cuaa0 doesn't support CD
? This will happen if your modem doesn't show a CD signal at all
when LCP is started. If this is the case, your modem is
misconfigured, or isn't connected when your dial/login scripts have
finished.
> Hi!
>
> Just have this problem again. With debug set on. ppp thinks that
> everything is ok, but modem already hanged up. When I kill it with -1 it
> says that
> it normally terminated the connection then exit.
> I think the workaround is to send ate0 to modem because it sends something
> to modem and receiving it :) But default config has ATE1 in it.
> I'm *really* sure that my modem is configured properly and it's not a user
> error :)
>
> What can I do to help you to resolve the problem? I'm using dial-on-demand
> (pmdemand section) and running ppp with a command ppp -auto pmdemand.
>
>
> On Wed, 11 Nov 1998, Dmitry Valdov wrote:
>
> >
> >
> > ---------- Forwarded message ----------
> > Date: Tue, 10 Nov 1998 21:32:53 +0000
> > From: Brian Somers <brian@Awfulhak.org>
> > To: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
> > Cc: Dmitry Valdov <dv@dv.ru>, Brian Somers <brian@freebsd.org>,
> > current@freebsd.org
> > Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
> >
> > > On Tue, 10 Nov 1998, Dmitry Valdov wrote:
> > >
> > > > Also there is one more bug - sometimes ppp don't detect carrier lost and
> > > > stays in open state for a long time. :(
> > >
> > > Sorry for the "implicit bug report", Brian, but I've been meaning to track
> > > this down for a long time and make sure it's not user error. I often see this
> > > as well - it's noticeable for me because I have ipfw installed and when the
> > > modem drops carrier I see packets being 'reflected' by the modem's local echo
> > > (I assume), and bouncing off the ipfw 'incoming address of myself' filter.
> >
> > Try ``set log +debug''. You should see the online/offline status of
> > the link at frequent intervals. If this doesn't agree with your
> > modem, then you modem may be misconfigured.
> >
> > > Kris
--
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 Wed Nov 11 17:19:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA02063
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:19:11 -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 RAA02042;
Wed, 11 Nov 1998 17:19:04 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id XAA29792;
Wed, 11 Nov 1998 23:51:51 GMT
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1])
by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id XAA04310;
Wed, 11 Nov 1998 23:53:22 GMT
(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199811112353.XAA04310@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Dmitry Valdov <dv@dv.ru>
cc: Brian Somers <brian@Awfulhak.org>,
Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
In-reply-to: Your message of "Wed, 11 Nov 1998 10:50:33 +0300."
<Pine.BSF.3.95q.981111104744.20962B-100000@xkis.kis.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 23:53:22 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > What do you suggest is changed ? Ppp can't delete the default route
> > on it's own - it doesn't necessarily belong to ppp.
> >
>
> Why? If I have add default [...] in ppp.conf, and there is impossible to
> have 2 defaults then ppp shoul delete old default and make new :)
>From the man page:
iface add[!] addr[[/bits| mask] peer]
Add the given addr mask peer combination to the interface. Instead
of specifying mask, /bits can be used (with no space between it and
addr). If the given address already exists, the command fails unless
the ``!'' is used - in which case the previous interface address en-
try is overwritten with the new one, allowing a change of netmask or
peer address.
If only addr is specified, bits defaults to ``32'' and peer defaults
to ``255.255.255.255''. This address (the broadcast address) is the
only duplicate peer address that ppp allows.
> > > Also there is one more bug - sometimes ppp don't detect carrier lost and
> > > stays in open state for a long time. :(
> >
> > Get the latest version from http://www.Awfulhak.org/ppp.html and
> > enable debug logging. You'll see ppps idea of carrier. I suspect
> > that either your modem is faking carrier all the time or that you're
> > running a very old version (2.2.5?).
> >
>
> 1. I'm running version from -current.
> 2. I've USR Sportster 28800 modem and my friend have an IDC modem. We are
> both experiencing the same problem.
>
> Please check it, I'm really shure that it isn't nmodem or user error :)
Have you tried enabling ``debug'' logs ? Does it report the carrier
status correctly ?
> Dmitry.
--
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 Wed Nov 11 17:24:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA02633
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:24:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ifi.uio.no (ifi.uio.no [129.240.64.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02620
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 17:24:26 -0800 (PST)
(envelope-from dag-erli@ifi.uio.no)
Received: from grjottunagard.ifi.uio.no (2602@grjottunagard.ifi.uio.no [129.240.64.131])
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id CAA11606;
Thu, 12 Nov 1998 02:22:43 +0100 (MET)
Received: (from dag-erli@localhost) by grjottunagard.ifi.uio.no ; Thu, 12 Nov 1998 02:22:42 +0100 (MET)
Mime-Version: 1.0
To: Julian Elischer <julian@whistle.com>
Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
References: <Pine.BSF.3.95.981111112705.16498A-100000@current1.whistle.com>
Organization: University of Oslo, Department of Informatics
X-url: http://www.stud.ifi.uio.no/~dag-erli/
X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list
X-disclaimer-1: The views expressed in this article are mine alone, and do
X-disclaimer-2: not necessarily coincide with those of any organisation or
X-disclaimer-3: company with which I am or have been affiliated.
X-Stop-Spam: http://www.cauce.org/
From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= )
Date: 12 Nov 1998 02:22:41 +0100
In-Reply-To: Julian Elischer's message of "Wed, 11 Nov 1998 11:29:54 -0800 (PST)"
Message-ID: <xzpn25xvh5q.fsf@grjottunagard.ifi.uio.no>
Lines: 11
X-Mailer: Gnus v5.5/Emacs 19.34
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA02629
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Julian Elischer <julian@whistle.com> writes:
> we will probably be dropping in a 3rd stage loader
> made in a.out, called 'kernel'
>
> the new kernel will probably be called elfkernel or similar (ekernel?)
For originality's sake, how about vmunix? :)
DES
--
Dag-Erling Smørgrav - dag-erli@ifi.uio.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 17:37:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA03776
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:37: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 RAA03763
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 17:37:48 -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 UAA01368;
Wed, 11 Nov 1998 20:36:54 -0500 (EST)
Date: Wed, 11 Nov 1998 20:36:54 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: The Hermit Hacker <scrappy@hub.org>
cc: Mike Smith <mike@smith.net.au>, oZZ!!! <osa@etrust.ru>,
current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <Pine.BSF.4.05.9811111531030.337-100000@thelab.hub.org>
Message-ID: <Pine.BSF.4.05.9811112033040.725-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
> Keep up the good work Brian...the longer I can avoid installing a
> Linux system to get its commercial apps, the happier I will be. With
Thanks! Positive response makes work worth doing :)
> attitudes like "don't waste your time" vs "its being worked on", I fear
> that that day is fast approaching where I'll have to buy a third machine
> just to keep from having to run Windows to get the good apps :(
>
Happily, I've been able to be entirely Windows-free! StarOffice 4.0 (no
service pack level) completes my needs :) 5.0's gonna work soon...
> Marc G. Fournier
> Systems Administrator @ hub.org
> primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
>
Don't spread it around, because I don't want anyone to think that I'm
giving up. I am taking a one week hiatus from coding, so if you want to
poke around a bit, or know someone who would, it would help keep the work
moving! As for me, I need a one week vacation, and I'll be able to look at
this problem more thoroughly as well.
Cheers,
Brian Feldman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 17:39:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA04011
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:39:30 -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 RAA04000
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 17:39: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 UAA01413;
Wed, 11 Nov 1998 20:38:37 -0500 (EST)
Date: Wed, 11 Nov 1998 20:38:37 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Julian Elischer <julian@whistle.com>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <Pine.BSF.3.95.981111112705.16498A-100000@current1.whistle.com>
Message-ID: <Pine.BSF.4.05.9811112037450.725-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
> we will probably be dropping in a 3rd stage loader
> made in a.out, called 'kernel'
This is really hackish...
>
> the new kernel will probably be called elfkernel or similar (ekernel?)
>
and totally gross.
> julian
>
Brian Feldman
> On Wed, 11 Nov 1998, Jordan K. Hubbard wrote:
>
> > > the ability to run on old bootblocks is how shall I say...
> > > "required".
> >
> > Well, you have and have always had just two options the minute we pull
> > the elf kernel switch: You switch customers to the 3-stage boot by
> > dropping a /boot.conf file into place which calls /boot/loader (which
> > you also install along with the 3.0 upgrade) or you relabel them so
> > they look just like freshly installed 3.0.x systems; it's your choice
> > whether you want to go for minimal impact or minimal difference.
> >
> > - Jordan
> >
>
>
> 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 Nov 11 17:50:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA04852
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:50: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 RAA04839
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 17:50:01 -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 UAA01555;
Wed, 11 Nov 1998 20:49:24 -0500 (EST)
Date: Wed, 11 Nov 1998 20:49:24 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: "Richard Seaman, Jr." <lists@tar.com>
cc: "current@freebsd.org" <current@FreeBSD.ORG>
Subject: Re: RFSIGSHARE ready?
In-Reply-To: <199811111951.NAA17744@ns.tar.com>
Message-ID: <Pine.BSF.4.05.9811112041160.725-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, 11 Nov 1998, Richard Seaman, Jr. wrote:
> I've looked more closely at your patch. If I understand what it does,
> it shares signal actions as well as signal masks between threads.
Correct. If the flag is used, of course.
>
> Its my understanding that POSIX specifies that signal actions
> are shared process wide, but that each thread has its own signal
> mask. It appears to me that this is also what linux threads
> attempts to implement.
CLONE_SIGHAND, what does that mean to you? To me it means that signal
handlers are shared between processes.
>
> If you want POSIX and linux thread compliant signal handling,
> I would think you would share the p_sigacts structure, but
> not the p_sigmask structure. However, I have no idea what
> the linux kernel actually does, so if your goal is to match
> that, I have no idea if your implementation does that.
I do intend to for every appearence emulate the behavior of Linux for the
Linux processes.
>
> Also, FYI, your patches break a make buildworld in gdb too.
I'll look into this.
Cheers,
Brian Feldman
>
>
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 17:53:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA05182
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:53:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from websmtp1.bellsouth.bigfoot.com (websmtp1.bellsouth.bigfoot.com [208.156.60.91])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05175
for <current@freebsd.org>; Wed, 11 Nov 1998 17:53:10 -0800 (PST)
(envelope-from BSB-Publishing@bellsouth.com)
Received: from v5q6k3 (170-56-111.ipt.aol.com [152.170.56.111])
by websmtp1.bellsouth.bigfoot.com (8.9.1/8.8.5) with SMTP id UAA26191;
Wed, 11 Nov 1998 20:21:23 -0500 (EST)
Date: Wed, 11 Nov 1998 20:21:23 -0500 (EST)
Message-Id: <199811120121.UAA26191@websmtp1.bellsouth.bigfoot.com>
From: BSB Publishing <BSB-Publishing@bellsouth.com>
To: <curly7jrt@aol.com>
Subject: Offering 50,000 African American Email Addresses . . .
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
Email up to 50,000 African-American Consumers
CALL TOLL FREE TO ORDER - (800)305-1458
Also . . . Email 4,000 Black business owners and entrepreneurs
simultaneously. Generate web traffic and sales by exchanging links and
banners with other African- American Entrepreneurs.
Do you have a product or service of interest to African-Americans on the
Internet? Would you like to effortlessly expand your customer base by up to
50,000 African-Americans for under $100? If you answered yes to either
of these questions, then our email marketing lists are what you need.
We have a database of well over 50,000 email addresses of
African-Americans who may be interested in your products and services.
We also offer a email list of 4,000 African American entreprenuers and
businesses who do business on the internet. These contacts could lead
to a mutually profitible business relationship including banner and
link exchanges.
These pre-screened email addresses are compiled on 3.5" diskettes in
standard "DBASE IV" and "TEXT" format which are universally compatible
with email merge programs like CyberMailer Pro and word processing
programs. All you need to do is import the list into an email merge
program which will automatically email everyone on the list. It
couldn't be easier or more efficient.
Email up to 50,000 African-Americans immediately!
50,000 AA Email Addresses - $99.95
10,000 AA Email Addresses - $49.95
4,000 AA Entreprenuers - $39.95
***Special Limited time offer***
Order 50,000 African American Email Addresses and receive 4,000
African American Entreprenuers for FREE. ($39.95 value)
CALL TOLL FREE TO ORDER - (800)305-1458
BSB Publishing Co.
5411 E. State Street #348
Rockford, IL 61108
All orders are shipped C.O.D.
$10.00 - Priority Mail Shipping
$12.00 - Overnight Shipping
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 17:53:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA05395
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:53:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from werple.mira.net (werple.mira.net [203.9.190.18])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA05390
for <freebsd-current@FreeBSD.ORG>; Wed, 11 Nov 1998 17:53:53 -0800 (PST)
(envelope-from gfm@mira.net)
Received: (qmail 24778 invoked from network); 12 Nov 1998 01:53:33 -0000
Received: from dp-m-q206.werple.net.au (203.17.45.206)
by mira.net with SMTP; 12 Nov 1998 01:53:33 -0000
From: gfm@mira.net (Graham Menhennitt)
To: freebsd-current@FreeBSD.ORG
Subject: Doco on installing new boot blocks (was: Is it soup yet?)
Date: Thu, 12 Nov 1998 01:56:18 GMT
Message-ID: <364b0d4f.176091736@mira.net>
References: <9940.910772319@zippy.cdrom.com>
In-Reply-To: <9940.910772319@zippy.cdrom.com>
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 RAA05391
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 11 Nov 1998 00:18:39 -0800, "Jordan K. Hubbard"
<jkh@zippy.cdrom.com> wrote:
>> the ability to run on old bootblocks is how shall I say...
>> "required".
>
>Well, you have and have always had just two options the minute we pull
>the elf kernel switch: You switch customers to the 3-stage boot by
>dropping a /boot.conf file into place which calls /boot/loader (which
>you also install along with the 3.0 upgrade) or you relabel them so
>they look just like freshly installed 3.0.x systems; it's your choice
>whether you want to go for minimal impact or minimal difference.
As somebody who has just upgraded from 2.2-STABLE to 3.0-RELEASE but is
still using the old boot blocks (actually, probably those from 2.1.5), I
would like to know what's involved in upgrading them. Can someone please
point me to some doco.
Thanks,
Graham
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 17:57:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA05741
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:57:51 -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 RAA05733
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 17:57:48 -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 UAA01624;
Wed, 11 Nov 1998 20:53:57 -0500 (EST)
Date: Wed, 11 Nov 1998 20:53:57 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= <sos@freebsd.dk>
cc: Andrzej Bialecki <abial@nask.pl>, daeron@Wit401305.student.utwente.nl,
shawn@cpl.net, osa@etrust.ru, current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <199811112000.VAA00590@freebsd.dk>
Message-ID: <Pine.BSF.4.05.9811112050420.725-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id RAA05737
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, 11 Nov 1998, Søren Schmidt wrote:
> It seems Andrzej Bialecki wrote:
> > > As far as I know StarOffice 5.0 install-program tries to read the
> > > commandline from /proc ... I think i saw some postings about this on
> > > comps.os.unix.bsd.* (or something like that)
> >
> > Yes, I've got the diffs against relatively fresh current. BTW, I asked
> > this question on -emulation, but got back a profound silence... Can we/
> > should we incorporate this patch, and hide it under a kernel option, say
> > PROCFS_CMDLINE? The life would be soooo easier for people new to our linux
> > emulation...
>
> Hmm, if we should have a Linsux compatible /proc, it really should be
> a beast mounted on /compat/linux/proc. If you provide this, I'm sure
> it will be received with open arms :)
Linux_procfs sounds good, but if a Linux procfs is implemented... erm....
you see, wouldn't this waste resources? unless we'd be emulating the
ENTIRE linux proc (which is total crap, and shouldn't exist), it's
probably better just to add it to the standard procfs.
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member
>
Cheers,
Brian Feldman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 17:58:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA05806
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:58:30 -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 RAA05799
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 17:58:27 -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 UAA01701;
Wed, 11 Nov 1998 20:57:55 -0500 (EST)
Date: Wed, 11 Nov 1998 20:57:55 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Mike Smith <mike@smith.net.au>
cc: obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <199811111937.LAA04505@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811112056130.725-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, 11 Nov 1998, Mike Smith wrote:
> > > I can see we are simply of two minds on this issue. :) What do some of
> > > the others think?
> >
> > While I agree with the silly name, I think we are approaching another
> > gratuitous change. It is our history, /usr/mdec is where people are used
> > to looking, ...
>
> It is our history to have buggy NFS. It is our history to have a
> bogus kernel module subsystem. It is our history to play catch-up to
> Linux.
When we "catch up" to Linux, for every advance, we always have a
better-implemented version of whatever new has been gotten on Linux. Maybe
except for NFS.... but that's being working on, eh?
>
> The good old days weren't always good, and tomorrow's not as bad as it
> seems.
>
> --
> \\ 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
>
>
Cheers,
Brian Feldman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 17:59:17 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA05844
for freebsd-current-outgoing; Wed, 11 Nov 1998 17:59:17 -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 RAA05837
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 17:59:12 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id RAA01725;
Wed, 11 Nov 1998 17:52:03 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdUc1709; Thu Nov 12 01:51:55 1998
Date: Wed, 11 Nov 1998 17:51:21 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Brian Feldman <green@unixhelp.org>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <Pine.BSF.4.05.9811112037450.725-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.3.95.981111174824.16843B-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
hackish or not here's the picture..
The automatic upgrade provedure cannot replace bootblocks.
however we will soon only be able to profuce kernels the existing
bootblocks can't read/load.
they look for a a.out file called /kernel
we give them one.
These are "embedded" FreeBSD machines.
they are all over the world.
We are certainly not in the position of bringing each back to the factory!
julian
On Wed, 11 Nov 1998, Brian Feldman wrote:
> > we will probably be dropping in a 3rd stage loader
> > made in a.out, called 'kernel'
>
> This is really hackish...
>
> >
> > the new kernel will probably be called elfkernel or similar (ekernel?)
> >
>
> and totally gross.
>
> > julian
> >
>
> Brian Feldman
> > On Wed, 11 Nov 1998, Jordan K. Hubbard wrote:
> >
> > > > the ability to run on old bootblocks is how shall I say...
> > > > "required".
> > >
> > > Well, you have and have always had just two options the minute we pull
> > > the elf kernel switch: You switch customers to the 3-stage boot by
> > > dropping a /boot.conf file into place which calls /boot/loader (which
> > > you also install along with the 3.0 upgrade) or you relabel them so
> > > they look just like freshly installed 3.0.x systems; it's your choice
> > > whether you want to go for minimal impact or minimal difference.
> > >
> > > - Jordan
> > >
> >
> >
> > 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 Nov 11 18:05:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA06419
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:05: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 SAA06406
for <freebsd-current@FreeBSD.ORG>; Wed, 11 Nov 1998 18:05:03 -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.1/8.9.1/Spinner) with ESMTP id KAA13751;
Thu, 12 Nov 1998 10:04:13 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811120204.KAA13751@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Blaz Zupan <blaz@gold.amis.net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: modules vs. LKM's
In-reply-to: Your message of "Wed, 11 Nov 1998 23:26:57 +0100."
<Pine.BSF.4.05.9811112325330.895-100000@gold.amis.net>
Date: Thu, 12 Nov 1998 10:04:12 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Blaz Zupan wrote:
> The latest makefile changes install a /usr/bin/linux.sh instead of
> /usr/bin/linux. They also install a joy.sh and ibcs2.sh in /usr/bin. I
> hope this is not intentional ;)
Yes.. :-] My mind was on other nightmares at the time..
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 18:09:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA06877
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:09:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06872
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 18:09:35 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id VAA03616;
Wed, 11 Nov 1998 21:11:49 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Wed, 11 Nov 1998 21:11:49 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Brian Feldman <green@unixhelp.org>
cc: Mike Smith <mike@smith.net.au>, obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <Pine.BSF.4.05.9811112056130.725-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.4.05.9811112110170.370-100000@porkfriedrice.ny.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, 11 Nov 1998, Brian Feldman wrote:
> > > > I can see we are simply of two minds on this issue. :) What do some of
> > > > the others think?
> > >
> > > While I agree with the silly name, I think we are approaching another
> > > gratuitous change. It is our history, /usr/mdec is where people are used
> > > to looking, ...
> >
> > It is our history to have buggy NFS. It is our history to have a
> > bogus kernel module subsystem. It is our history to play catch-up to
> > Linux.
>
> When we "catch up" to Linux, for every advance, we always have a
> better-implemented version of whatever new has been gotten on Linux. Maybe
> except for NFS.... but that's being working on, eh?
I hope you are refering to Linux NFS being far inferior to FreeBSD's
impelementation. If you are not then where do we fall behind? I haven't
seen Linux outperform FreeBSD in any NFS work i've done.
Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com
-- There are operating systems, and then there's FreeBSD.
-- http://www.freebsd.org/ 3.0-current
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 18:16:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA07587
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:16:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ifi.uio.no (ifi.uio.no [129.240.64.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07574
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 18:16:47 -0800 (PST)
(envelope-from dag-erli@ifi.uio.no)
Received: from grjottunagard.ifi.uio.no (2602@grjottunagard.ifi.uio.no [129.240.64.131])
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id DAA15864;
Thu, 12 Nov 1998 03:15:46 +0100 (MET)
Received: (from dag-erli@localhost) by grjottunagard.ifi.uio.no ; Thu, 12 Nov 1998 03:15:46 +0100 (MET)
Mime-Version: 1.0
To: Julian Elischer <julian@whistle.com>
Cc: Brian Feldman <green@unixhelp.org>,
"Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
References: <Pine.BSF.3.95.981111174824.16843B-100000@current1.whistle.com>
Organization: University of Oslo, Department of Informatics
X-url: http://www.stud.ifi.uio.no/~dag-erli/
X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list
X-disclaimer-1: The views expressed in this article are mine alone, and do
X-disclaimer-2: not necessarily coincide with those of any organisation or
X-disclaimer-3: company with which I am or have been affiliated.
X-Stop-Spam: http://www.cauce.org/
From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= )
Date: 12 Nov 1998 03:15:45 +0100
In-Reply-To: Julian Elischer's message of "Wed, 11 Nov 1998 17:51:21 -0800 (PST)"
Message-ID: <xzpd86tvepa.fsf@grjottunagard.ifi.uio.no>
Lines: 24
X-Mailer: Gnus v5.5/Emacs 19.34
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id SAA07583
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Julian Elischer <julian@whistle.com> writes:
> These are "embedded" FreeBSD machines.
> they are all over the world.
> We are certainly not in the position of bringing each back to the factory!
Do they work?
If they do, why upgrade them?
If they don't, you have to fix them anyway.
If you have the option of upgrading them at all (through remote
administration), is it really that hard to run the *one* *single*
command that's needed to upgrade the boot blocks?
# disklabel -B -b /boot/boot1 -s /boot/boot2 /dev/foo0s1
Even *I* can do that ;)
(OBTW, I assume you're talking about Interjets...?)
DES
--
Dag-Erling Smørgrav - dag-erli@ifi.uio.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 18:20:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA07958
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:19:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from picnic.mat.net (picnic.mat.net [206.246.122.117])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07952
for <freebsd-current@FreeBSD.ORG>; Wed, 11 Nov 1998 18:19:57 -0800 (PST)
(envelope-from chuckr@mat.net)
Received: from localhost (chuckr@localhost)
by picnic.mat.net (8.9.1/8.8.5) with ESMTP id VAA23692;
Wed, 11 Nov 1998 21:16:52 -0500 (EST)
Date: Wed, 11 Nov 1998 21:16:52 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Graham Menhennitt <gfm@mira.net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Doco on installing new boot blocks (was: Is it soup yet?)
In-Reply-To: <364b0d4f.176091736@mira.net>
Message-ID: <Pine.BSF.4.05.9811112106520.10145-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, 12 Nov 1998, Graham Menhennitt wrote:
> On Wed, 11 Nov 1998 00:18:39 -0800, "Jordan K. Hubbard"
> <jkh@zippy.cdrom.com> wrote:
>
> >> the ability to run on old bootblocks is how shall I say...
> >> "required".
> >
> >Well, you have and have always had just two options the minute we pull
> >the elf kernel switch: You switch customers to the 3-stage boot by
> >dropping a /boot.conf file into place which calls /boot/loader (which
> >you also install along with the 3.0 upgrade) or you relabel them so
> >they look just like freshly installed 3.0.x systems; it's your choice
> >whether you want to go for minimal impact or minimal difference.
>
> As somebody who has just upgraded from 2.2-STABLE to 3.0-RELEASE but is
> still using the old boot blocks (actually, probably those from 2.1.5), I
> would like to know what's involved in upgrading them. Can someone please
> point me to some doco.
Having recently done just that, the disklabel man page is what I used,
and it's remarkably clear on this:
disklabel -B [-b boot1 [-s boot2]] disk [disktype]
I didn't need [disktype], and boot1/boot2 are in /boot, disk is your
boot disk (mine was rda0s1a). It just worked fine, no problem, then I
was booting my elf kernel.
There are other new issues (like new flags to strip, for those that
install /var/crash/kernel.debug's) and setting up a /boot/boot.conf. A
buildworld now installs your new modules for you, and new bootblocks
also, making at least that part simpler. Those with smallish /
filesystems may want to watch this part carefully ... but lkms won't be
needed anymore, so things aren't growing out of bounds.
----------------------------+-----------------------------------------------
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 Nov 11 18:24:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA08412
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:24:03 -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 SAA08391;
Wed, 11 Nov 1998 18:23: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 VAA02060;
Wed, 11 Nov 1998 21:23:20 -0500 (EST)
Date: Wed, 11 Nov 1998 21:23:19 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Chuck Robey <chuckr@mat.net>
cc: Satoshi Asami <asami@FreeBSD.ORG>, nate@mt.sri.com, jkh@zippy.cdrom.com,
mike@smith.net.au, obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <Pine.BSF.4.05.9811111846200.10145-100000@picnic.mat.net>
Message-ID: <Pine.BSF.4.05.9811112119330.725-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
> No, Nate's got a point. How many times have you hand-mounted /usr?
> I know darned well I have (I *hate* using ex to edit files!). As long
Ex is part of nvi/nex, and is in /usr/bin. Do you mean ed? BTW, as I bring
this up, I'd like to propose moving nvi/nex to /bin. And of course, why
don't we add setenv("TERM", "cons25") before the sh spawn in /sbin/init?
It would prevent the following error in a single-user boot:
# vi
ex/vi: Error: unknown: No such file or directory
> Chuck Robey | Interests include any kind of voice or data
Just my two cents,
Brian Feldman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 18:26:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA08705
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:26:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ifi.uio.no (ifi.uio.no [129.240.64.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08694
for <freebsd-current@FreeBSD.ORG>; Wed, 11 Nov 1998 18:26:12 -0800 (PST)
(envelope-from dag-erli@ifi.uio.no)
Received: from grjottunagard.ifi.uio.no (2602@grjottunagard.ifi.uio.no [129.240.64.131])
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id DAA16735;
Thu, 12 Nov 1998 03:25:40 +0100 (MET)
Received: (from dag-erli@localhost) by grjottunagard.ifi.uio.no ; Thu, 12 Nov 1998 03:25:39 +0100 (MET)
Mime-Version: 1.0
To: Chuck Robey <chuckr@mat.net>
Cc: Graham Menhennitt <gfm@mira.net>, freebsd-current@FreeBSD.ORG
Subject: Re: Doco on installing new boot blocks (was: Is it soup yet?)
References: <Pine.BSF.4.05.9811112106520.10145-100000@picnic.mat.net>
Organization: University of Oslo, Department of Informatics
X-url: http://www.stud.ifi.uio.no/~dag-erli/
X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list
X-disclaimer-1: The views expressed in this article are mine alone, and do
X-disclaimer-2: not necessarily coincide with those of any organisation or
X-disclaimer-3: company with which I am or have been affiliated.
X-Stop-Spam: http://www.cauce.org/
From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= )
Date: 12 Nov 1998 03:25:38 +0100
In-Reply-To: Chuck Robey's message of "Wed, 11 Nov 1998 21:16:52 -0500 (EST)"
Message-ID: <xzp90hhve8t.fsf@grjottunagard.ifi.uio.no>
Lines: 13
X-Mailer: Gnus v5.5/Emacs 19.34
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id SAA08699
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Chuck Robey <chuckr@mat.net> writes:
> disklabel -B [-b boot1 [-s boot2]] disk [disktype]
>
> I didn't need [disktype], and boot1/boot2 are in /boot, disk is your
> boot disk (mine was rda0s1a). It just worked fine, no problem, then I
> was booting my elf kernel.
Mind you, disklabel works with *slices*, not with partitions, so you
should use rda0s1 (without the trailing 'a').
DES
--
Dag-Erling Smørgrav - dag-erli@ifi.uio.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 18:30:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA08988
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:30:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ifi.uio.no (ifi.uio.no [129.240.64.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08978;
Wed, 11 Nov 1998 18:30:25 -0800 (PST)
(envelope-from dag-erli@ifi.uio.no)
Received: from grjottunagard.ifi.uio.no (2602@grjottunagard.ifi.uio.no [129.240.64.131])
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id DAA16944;
Thu, 12 Nov 1998 03:29:12 +0100 (MET)
Received: (from dag-erli@localhost) by grjottunagard.ifi.uio.no ; Thu, 12 Nov 1998 03:29:12 +0100 (MET)
Mime-Version: 1.0
To: Brian Feldman <green@unixhelp.org>
Cc: Chuck Robey <chuckr@mat.net>, Satoshi Asami <asami@FreeBSD.ORG>,
nate@mt.sri.com, jkh@zippy.cdrom.com, mike@smith.net.au,
obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
References: <Pine.BSF.4.05.9811112119330.725-100000@janus.syracuse.net>
Organization: University of Oslo, Department of Informatics
X-url: http://www.stud.ifi.uio.no/~dag-erli/
X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list
X-disclaimer-1: The views expressed in this article are mine alone, and do
X-disclaimer-2: not necessarily coincide with those of any organisation or
X-disclaimer-3: company with which I am or have been affiliated.
X-Stop-Spam: http://www.cauce.org/
From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= )
Date: 12 Nov 1998 03:29:11 +0100
In-Reply-To: Brian Feldman's message of "Wed, 11 Nov 1998 21:23:19 -0500 (EST)"
Message-ID: <xzp7lx1ve2w.fsf@grjottunagard.ifi.uio.no>
Lines: 19
X-Mailer: Gnus v5.5/Emacs 19.34
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id SAA08981
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Feldman <green@unixhelp.org> writes:
> Ex is part of nvi/nex, and is in /usr/bin. Do you mean ed? BTW, as I bring
> this up, I'd like to propose moving nvi/nex to /bin. And of course, why
> don't we add setenv("TERM", "cons25") before the sh spawn in /sbin/init?
> It would prevent the following error in a single-user boot:
> # vi
> ex/vi: Error: unknown: No such file or directory
Well, instead you'll get
ex/vi: Error: cons25: No such file or directory
because for $TERM to be meaningful, you need /usr/share/misc/termcap,
and /usr probably isn't mounted yet (assuming you've moved vi to /bin,
which means linking it statically)
DES
--
Dag-Erling Smørgrav - dag-erli@ifi.uio.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 18:31:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA09028
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:31: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 SAA09016
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 18:30: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 VAA02118;
Wed, 11 Nov 1998 21:28:56 -0500 (EST)
Date: Wed, 11 Nov 1998 21:28:56 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Peter Wemm <peter@netplex.com.au>
cc: Julian Elischer <julian@whistle.com>,
"Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <199811120100.JAA13377@spinner.netplex.com.au>
Message-ID: <Pine.BSF.4.05.9811112128210.725-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, 12 Nov 1998, Peter Wemm wrote:
> Call be crazy, but I think I'd almost like to move the "real" kernel to
> /boot/kernel, providing the search paths were ok.
>
You're absolutely nuts.
>
> Cheers,
> -Peter
>
Brian
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 18:37:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA09667
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:37:42 -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 SAA09657;
Wed, 11 Nov 1998 18:37:36 -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.1/8.9.1/Spinner) with ESMTP id KAA13939;
Thu, 12 Nov 1998 10:37:09 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811120237.KAA13939@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: asami@FreeBSD.ORG (Satoshi Asami)
cc: chuckr@mat.net, nate@mt.sri.com, jkh@zippy.cdrom.com, mike@smith.net.au,
obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 15:12:56 PST."
<199811112312.PAA16909@silvia.hip.berkeley.edu>
Date: Thu, 12 Nov 1998 10:37:09 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Satoshi Asami wrote:
> * No, you forget, there's 2 reasons to have things in /. One, they're
> * needed for boot. Two, they qualify as emergency repair tools.
> * Diskalbel falls into the 2nd category (note I agree with Nate's original
> * position here).
>
> And the bootblocks might be needed for emergency repair. Consider, if
> you have a disk that's failing all over the place, you managed to boot
> single-user from it (or booted from a floppy) and mounted root, you
> now need to somehow set up a bootable FreeBSD installation on your
> second hard drive. You are toast if the bootblocks are in the broken
> /usr.
Mind if I ask a question? What is going to get put on this bootable
installation on the second disk if you can't mount /usr? You're going to
have a pretty rotten time trying to use the new disk when /usr is empty.
If your source (and objects) are (were) in /usr/src and /usr/obj, then
you're still cactus because you can't rebuild /usr on the new disk.
If they were on /home/src or something like that and you can still mount
/home, then you can use disklabel to install the bootblocks from
/home/obj/where/ever.
Anyway, I find the easiest way of preparing and partitioning new disks is
to use a sysinstall floppy. :-)
Somebody else talked about the same argument applying to /sbin/disklabel
vs. /usr/sbin/disklabel. That is a different situation, disklabel belongs
in / because it's purpose is partition editing - bootblock installation is
a convenient add-on, not it's sole purpose.
My original complaint was about the (apparent) suggestion that /usr/mdec
was going away and the contents moved to /boot. We presently have a heap
of crud installed into /usr/mdec, which I object to installing on /. Since
it looks like what is actually proposed is that the stuff that presently
goes into /usr/mdec is going away and the present /boot/boot{0,1,2} that
is already in /boot will stay - I can live with that.
What about disklabel though? It's presently got rules for generating boot
names from the prefixes of the devices. ie: a boot1 for fd0 comes from "/
usr/mdec/fdboot", while boot2 comes from /usr/mdec/bootfd. This allows
implied (without disktab) support for having different bootcode on
different devices. Are we talking about changing this so that
#ifdef i386
defboot1 = "/boot/boot1";
defboot2 = "/boot/boot2";
#endif
#ifdef alpha
defboot1 = "/boot/boot1";
defboot2 = NULL; /* alpha has only one boot block set */
#endif
? Of course this would be overrideable by disktab and the command line,
but I want to make sure we're not talking about a symlink tree in /boot..
> Satoshi
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 18:40:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA10232
for freebsd-current-outgoing; Wed, 11 Nov 1998 18: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 SAA10226
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 18:40: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 VAA02290;
Wed, 11 Nov 1998 21:39:45 -0500 (EST)
Date: Wed, 11 Nov 1998 21:39:45 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Julian Elischer <julian@whistle.com>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <Pine.BSF.3.95.981111174824.16843B-100000@current1.whistle.com>
Message-ID: <Pine.BSF.4.05.9811112136300.725-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, 11 Nov 1998, Julian Elischer wrote:
> hackish or not here's the picture..
> The automatic upgrade provedure cannot replace bootblocks.
> however we will soon only be able to profuce kernels the existing
> bootblocks can't read/load.
>
> they look for a a.out file called /kernel
>
> we give them one.
>
> These are "embedded" FreeBSD machines.
> they are all over the world.
> We are certainly not in the position of bringing each back to the factory!
>
> julian
>
What exactly was wrong about having the old boot loader run (via
boot.config) /boot/loader, and /boot/loader loading either an ELF or a.out
/kernel? It works perfectly in this case, where I'm using all defaults in
this case. And in an "embedded" system, wouldn't the
partitioning/slicing/drive scheme be simplistic anyway?
Cheers,
Brian Feldman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 18:41:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA10333
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:41:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles78.castles.com [208.214.165.78])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10326
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 18:41:42 -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 SAA06936;
Wed, 11 Nov 1998 18:36:10 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811120236.SAA06936@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: The Hermit Hacker <scrappy@hub.org>
cc: Andrzej Bialecki <abial@nask.pl>,
=?ISO-8859-2?Q?S=F8ren_Schmidt?= <sos@freebsd.dk>,
daeron@Wit401305.student.utwente.nl, shawn@cpl.net, osa@etrust.ru,
current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-reply-to: Your message of "Wed, 11 Nov 1998 19:54:23 -0400."
<Pine.BSF.4.05.9811111952370.337-100000@thelab.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Date: Wed, 11 Nov 1998 18:36:09 -0800
From: Mike Smith <mike@smith.net.au>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id SAA10329
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Just curious, but what exactly does that '/proc/*/cmdline' thing
> "do", and is there any reason why it is inappropriate for it to be a
> standard part of our /proc?
It duplicates the contents of the argv[] array. It's not entirely
clear why they feel that argv[] isn't good enough.
> When talkign with friends that use Linux, and talking about our
> /proc file system, they think its hilarious that I can't go into proc and
> find out what irqs are being used by the system...maybe I'm missing
> something, but about the only way I can do it currently is to look through
> dmesg output? Is there another way?
I have to ask - why do you care? I can think of much better things to
do with my time than stare at the list of IRQ's in use - what do they
expect them to do? A little song and dance number perhaps?
(If you need the information, try 'systat -vmstat'.)
--
\\ 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 Nov 11 18:42:25 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA10393
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:42: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 SAA10384
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 18:42:20 -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 VAA02337;
Wed, 11 Nov 1998 21:41:53 -0500 (EST)
Date: Wed, 11 Nov 1998 21:41:53 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Alfred Perlstein <bright@hotjobs.com>
cc: Mike Smith <mike@smith.net.au>, obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <Pine.BSF.4.05.9811112110170.370-100000@porkfriedrice.ny.genx.net>
Message-ID: <Pine.BSF.4.05.9811112140340.725-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, 11 Nov 1998, Alfred Perlstein wrote:
> On Wed, 11 Nov 1998, Brian Feldman wrote:
>
> > > > > I can see we are simply of two minds on this issue. :) What do some of
> > > > > the others think?
> > > >
> > > > While I agree with the silly name, I think we are approaching another
> > > > gratuitous change. It is our history, /usr/mdec is where people are used
> > > > to looking, ...
> > >
> > > It is our history to have buggy NFS. It is our history to have a
> > > bogus kernel module subsystem. It is our history to play catch-up to
> > > Linux.
> >
> > When we "catch up" to Linux, for every advance, we always have a
> > better-implemented version of whatever new has been gotten on Linux. Maybe
> > except for NFS.... but that's being working on, eh?
>
> I hope you are refering to Linux NFS being far inferior to FreeBSD's
> impelementation. If you are not then where do we fall behind? I haven't
> seen Linux outperform FreeBSD in any NFS work i've done.
Last I had heard, NFS was still too unstable to be used heavily in
FreeBSD, but "worked" in Linux. But, who knows for sure? I don't run any
Linux systems, and I don't really use NFS in FreeBSD.
>
> Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com
> -- There are operating systems, and then there's FreeBSD.
> -- http://www.freebsd.org/ 3.0-current
>
Cheers,
Brian Feldman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 18:47:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA10679
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:47:22 -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 SAA10672
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 18:47:19 -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.1/8.9.1/Spinner) with ESMTP id KAA14006;
Thu, 12 Nov 1998 10:46:20 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811120246.KAA14006@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman <green@unixhelp.org>
cc: Julian Elischer <julian@whistle.com>,
"Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 21:28:56 EST."
<Pine.BSF.4.05.9811112128210.725-100000@janus.syracuse.net>
Date: Thu, 12 Nov 1998 10:46:19 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Feldman wrote:
> On Thu, 12 Nov 1998, Peter Wemm wrote:
> > Call be crazy, but I think I'd almost like to move the "real" kernel to
> > /boot/kernel, providing the search paths were ok.
>
> You're absolutely nuts.
I feel better already... I think.. :-)
> Brian
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 18:53:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA11269
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:53:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles78.castles.com [208.214.165.78])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11238
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 18:53: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 SAA07015;
Wed, 11 Nov 1998 18:48:18 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811120248.SAA07015@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman <green@unixhelp.org>
cc: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= <sos@freebsd.dk>,
Andrzej Bialecki <abial@nask.pl>, daeron@Wit401305.student.utwente.nl,
shawn@cpl.net, osa@etrust.ru, current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-reply-to: Your message of "Wed, 11 Nov 1998 20:53:57 EST."
<Pine.BSF.4.05.9811112050420.725-100000@janus.syracuse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Date: Wed, 11 Nov 1998 18:48:18 -0800
From: Mike Smith <mike@smith.net.au>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id SAA11255
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> >
> > Hmm, if we should have a Linsux compatible /proc, it really should be
> > a beast mounted on /compat/linux/proc. If you provide this, I'm sure
> > it will be received with open arms :)
>
> Linux_procfs sounds good, but if a Linux procfs is implemented... erm....
> you see, wouldn't this waste resources? unless we'd be emulating the
> ENTIRE linux proc (which is total crap, and shouldn't exist), it's
> probably better just to add it to the standard procfs.
It's hideously crap, and unfortunately syntax-incompatible with ours,
which is why we'd have to have a complete emulation.
Unfortunately, the Linux procfs is also baroque beyond the abilities of
the structure of our relatively simple-minded procfs to handle. It's
more like a filesystem manifestation of the sysctl tree.
--
\\ 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 Nov 11 18:54:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA11385
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:54:21 -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 SAA11374;
Wed, 11 Nov 1998 18:54:16 -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 VAA02500;
Wed, 11 Nov 1998 21:53:45 -0500 (EST)
Date: Wed, 11 Nov 1998 21:53:45 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" <dag-erli@ifi.uio.no>
cc: Chuck Robey <chuckr@mat.net>, Satoshi Asami <asami@FreeBSD.ORG>,
nate@mt.sri.com, jkh@zippy.cdrom.com, mike@smith.net.au,
obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <xzp7lx1ve2w.fsf@grjottunagard.ifi.uio.no>
Message-ID: <Pine.BSF.4.05.9811112143390.725-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id SAA11380
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 12 Nov 1998, Dag-Erling C. [iso-8859-1] Smørgrav wrote:
> Brian Feldman <green@unixhelp.org> writes:
> > Ex is part of nvi/nex, and is in /usr/bin. Do you mean ed? BTW, as I bring
> > this up, I'd like to propose moving nvi/nex to /bin. And of course, why
> > don't we add setenv("TERM", "cons25") before the sh spawn in /sbin/init?
> > It would prevent the following error in a single-user boot:
> > # vi
> > ex/vi: Error: unknown: No such file or directory
>
> Well, instead you'll get
>
> ex/vi: Error: cons25: No such file or directory
>
> because for $TERM to be meaningful, you need /usr/share/misc/termcap,
> and /usr probably isn't mounted yet (assuming you've moved vi to /bin,
> which means linking it statically)
True... what are feelings on a "tinytermcap" if well-implemented (with
libtermcap)? It would be really simple to add to
src/lib/libtermcap/pathnames.h /etc/tinytermcap...
{"/home/green"}$ l tinytermcap
-rw-r--r-- 1 green green 1382 Nov 11 21:51 tinytermcap
tinytermcap would have consoles cons25{,w,r,l1}.
>
> DES
> --
> Dag-Erling Smørgrav - dag-erli@ifi.uio.no
>
Cheers,
Brian Feldman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 18:55:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA11516
for freebsd-current-outgoing; Wed, 11 Nov 1998 18:55:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ifi.uio.no (ifi.uio.no [129.240.64.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11501
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 18:55:39 -0800 (PST)
(envelope-from dag-erli@ifi.uio.no)
Received: from grjottunagard.ifi.uio.no (2602@grjottunagard.ifi.uio.no [129.240.64.131])
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id DAA18289;
Thu, 12 Nov 1998 03:48:00 +0100 (MET)
Received: (from dag-erli@localhost) by grjottunagard.ifi.uio.no ; Thu, 12 Nov 1998 03:48:00 +0100 (MET)
Mime-Version: 1.0
To: Mike Smith <mike@smith.net.au>
Cc: The Hermit Hacker <scrappy@hub.org>, Andrzej Bialecki <abial@nask.pl>,
=?ISO-8859-2?Q?S=F8ren_Schmidt?= <sos@freebsd.dk>,
daeron@Wit401305.student.utwente.nl, shawn@cpl.net, osa@etrust.ru,
current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
References: <199811120236.SAA06936@dingo.cdrom.com>
Organization: University of Oslo, Department of Informatics
X-url: http://www.stud.ifi.uio.no/~dag-erli/
X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list
X-disclaimer-1: The views expressed in this article are mine alone, and do
X-disclaimer-2: not necessarily coincide with those of any organisation or
X-disclaimer-3: company with which I am or have been affiliated.
X-Stop-Spam: http://www.cauce.org/
From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= )
Date: 12 Nov 1998 03:47:59 +0100
In-Reply-To: Mike Smith's message of "Wed, 11 Nov 1998 18:36:09 -0800"
Message-ID: <xzp67clvd7k.fsf@grjottunagard.ifi.uio.no>
Lines: 17
X-Mailer: Gnus v5.5/Emacs 19.34
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id SAA11509
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Smith <mike@smith.net.au> writes:
> I have to ask - why do you care? I can think of much better things to
> do with my time than stare at the list of IRQ's in use - what do they
> expect them to do? A little song and dance number perhaps?
>
> (If you need the information, try 'systat -vmstat'.)
...or vmstat -i.
BTW, there is a really obnoxious piece of software called xperfmon
that uses this Linux "feature" to flash a red square on your screen
every time an interrupt fires. As if you've nothing better to do with
your CPU time, and as if it were useful.
DES
--
Dag-Erling Smørgrav - dag-erli@ifi.uio.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 19:02:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA12146
for freebsd-current-outgoing; Wed, 11 Nov 1998 19:02:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12141
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 19:02:06 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id WAA03672;
Wed, 11 Nov 1998 22:04:43 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Wed, 11 Nov 1998 22:04:43 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Brian Feldman <green@unixhelp.org>
cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <Pine.BSF.4.05.9811112140340.725-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.4.05.9811112154240.370-100000@porkfriedrice.ny.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, 11 Nov 1998, Brian Feldman wrote:
> > > When we "catch up" to Linux, for every advance, we always have a
> > > better-implemented version of whatever new has been gotten on Linux. Maybe
> > > except for NFS.... but that's being working on, eh?
> >
> > I hope you are refering to Linux NFS being far inferior to FreeBSD's
> > impelementation. If you are not then where do we fall behind? I haven't
> > seen Linux outperform FreeBSD in any NFS work i've done.
>
> Last I had heard, NFS was still too unstable to be used heavily in
> FreeBSD, but "worked" in Linux. But, who knows for sure? I don't run any
> Linux systems, and I don't really use NFS in FreeBSD.
Then perhaps you should stay quiet on the issue.
FreeBSD has outperformed linux by several orders of magnitude in client
side NFS for a long time. The newer linux development kernels come close,
but when concurrent NFS requests are made Linux chokes while FreeBSD
maintains a broadband'ish state.
I know i posted several times about problems with NFS (about a month ago)
but since McKusik's fixes I've yet to have a problem.
In so far as serving NFS... the Linux userland NFS server is hardly a
match to the FreeBSD kernel impelementation. Stability is another matter
and I haven't seen enough to say anything conclusive for either side.
Both implementations suffer from lack of support for files > 2gb in
client side requests which should be addressed, somehow/somewhen.
A recent Linux article suggests that Linux NFS will bipass the "mbuf"
layer, ie. the NFS code will directly reassemble packets into RPC requests
thereby saving _one_ copy of memory. This is really neat, but then makes
NFS dependant on the protocols which it is supposed to be independant of.
Btw, Mike Smith's new ACCESS caching seems quite stable and i was
wondering if it had been commited.
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 19:05:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA12714
for freebsd-current-outgoing; Wed, 11 Nov 1998 19:05:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12703
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 19:05:48 -0800 (PST)
(envelope-from karl@Genesis.Denninger.Net)
Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id VAA06045; Wed, 11 Nov 1998 21:05:19 -0600 (CST)
Message-ID: <19981111210519.A6032@Denninger.Net>
Date: Wed, 11 Nov 1998 21:05:19 -0600
From: Karl Denninger <karl@Denninger.Net>
To: Alfred Perlstein <bright@hotjobs.com>, Brian Feldman <green@unixhelp.org>
Cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
References: <Pine.BSF.4.05.9811112140340.725-100000@janus.syracuse.net> <Pine.BSF.4.05.9811112154240.370-100000@porkfriedrice.ny.genx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.05.9811112154240.370-100000@porkfriedrice.ny.genx.net>; from Alfred Perlstein on Wed, Nov 11, 1998 at 10:04:43PM -0500
Organization: Karl's Sushi and Packet Smashers
X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Nov 11, 1998 at 10:04:43PM -0500, Alfred Perlstein wrote:
> On Wed, 11 Nov 1998, Brian Feldman wrote:
>
> > > > When we "catch up" to Linux, for every advance, we always have a
> > > > better-implemented version of whatever new has been gotten on Linux. Maybe
> > > > except for NFS.... but that's being working on, eh?
> > >
> > > I hope you are refering to Linux NFS being far inferior to FreeBSD's
> > > impelementation. If you are not then where do we fall behind? I haven't
> > > seen Linux outperform FreeBSD in any NFS work i've done.
> >
> > Last I had heard, NFS was still too unstable to be used heavily in
> > FreeBSD, but "worked" in Linux. But, who knows for sure? I don't run any
> > Linux systems, and I don't really use NFS in FreeBSD.
>
> Then perhaps you should stay quiet on the issue.
>
> FreeBSD has outperformed linux by several orders of magnitude in client
> side NFS for a long time. The newer linux development kernels come close,
> but when concurrent NFS requests are made Linux chokes while FreeBSD
> maintains a broadband'ish state.
>
> I know i posted several times about problems with NFS (about a month ago)
> but since McKusik's fixes I've yet to have a problem.
Have these fixes been committed, and if so, when?
--
--
Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl
I ain't even *authorized* to speak for anyone other than myself, so give
up now on trying to associate my words with any particular organization.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 19:10:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA13185
for freebsd-current-outgoing; Wed, 11 Nov 1998 19:10:07 -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 TAA13174
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 19:10: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 WAA02714;
Wed, 11 Nov 1998 22:06:07 -0500 (EST)
Date: Wed, 11 Nov 1998 22:06:07 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Mike Smith <mike@smith.net.au>
cc: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= <sos@freebsd.dk>,
Andrzej Bialecki <abial@nask.pl>, daeron@Wit401305.student.utwente.nl,
shawn@cpl.net, osa@etrust.ru, current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <199811120248.SAA07015@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811112204070.725-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, 11 Nov 1998, Mike Smith wrote:
> > >
> > > Hmm, if we should have a Linsux compatible /proc, it really should be
> > > a beast mounted on /compat/linux/proc. If you provide this, I'm sure
> > > it will be received with open arms :)
> >
> > Linux_procfs sounds good, but if a Linux procfs is implemented... erm....
> > you see, wouldn't this waste resources? unless we'd be emulating the
> > ENTIRE linux proc (which is total crap, and shouldn't exist), it's
> > probably better just to add it to the standard procfs.
>
> It's hideously crap, and unfortunately syntax-incompatible with ours,
> which is why we'd have to have a complete emulation.
>
> Unfortunately, the Linux procfs is also baroque beyond the abilities of
> the structure of our relatively simple-minded procfs to handle. It's
> more like a filesystem manifestation of the sysctl tree.
Any new plans for kernfs? This is the kinda thing (the Linux procfs stuff)
that would go in kernfs. HEY! I know! Why don't we actually implement the
whole sysctl tree itself in /kern/sysctl? ;) Sorry, Linux has forced me to
go insane.
>
> --
> \\ 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
>
Cheers,
Brian Feldman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 19:50:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA17714
for freebsd-current-outgoing; Wed, 11 Nov 1998 19:50:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from papillon.lemis.com (freebie.lemis.com [139.130.136.133] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17707
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 19:50:15 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by papillon.lemis.com (8.9.1/8.6.12) with ESMTP
id MAA00741; Thu, 12 Nov 1998 12:17:55 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.1/8.9.0) id MAA04041;
Thu, 12 Nov 1998 12:18:21 +1030 (CST)
Message-ID: <19981112121821.G463@freebie.lemis.com>
Date: Thu, 12 Nov 1998 12:18:21 +1030
From: Greg Lehey <grog@lemis.com>
To: Alexander Litvin <archer@lucky.net>
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <199811101456.QAA28210@grape.carrier.kiev.ua> <199811110038.CAA01861@grape.carrier.kiev.ua> <19981111133212.B20374@freebie.lemis.com> <19981111112620.20264@carrier.kiev.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.91.1i
In-Reply-To: <19981111112620.20264@carrier.kiev.ua>; from Alexander Litvin on Wed, Nov 11, 1998 at 11:26:20AM +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 Wednesday, 11 November 1998 at 11:26:20 +0200, Alexander Litvin wrote:
> On Wed, Nov 11, 1998 at 01:32:12PM +1030, Greg Lehey wrote:
>
>>> Brought up old kernel without kludge.
>>>
>>> It appears that memory corruption leading to 'daemons dying' may take
>>> different forms. E.g., once it appears that sendmail continues to
>>> fork for queue runs successfully, but when I do 'telnet localhost 25',
>>> it just accepts connection, forks, changes proctitle ('startup with ...'),
>>> and goes into some strange state -- no EHLO, just accepts all I type
>>> in telnet and that's all. In that state kill -1 restarts sendmail ok.
>>> Other time I exhaust memory, sendmail segfaults every child forked
>>> for queue run, again restarts ok on SIGHUP. Once I even got in responce
>>> to 'telnet localhost 25':
>>>
>>> Trying 127.0.0.1...
>>> Connected to localhost.carrier.kiev.ua.
>>> Escape character is '^]'.
>>> archer... Recipient names must be specified
>>>
>>> As if I started sendmail without arguments on command prompt!
>>>
>>> I think it is ehough evidence that 'daemons dying' is caused by
>>> memory corruption.
>>
>> Well, no, I had an alternative explanation: for me, this problem
>> started with sendmail 8.9. I think I even went back and tried
>> sendmail 8.8.<mumble> and it didn't cause any problems. It could be a
>> bug in sendmail, possibly related to the config I'm using (it often
>> refuses connections because it thinks some test on the domain name
>> succeeds, when in fact it should have failed).
>
> Oh, come on!
Where?
> Just installed 8.8.8 -- same stuff, dies on queue runs and when
> accepting connection. And AFAIR the whole story had started before
> 8.9 was released and merged to CURRENT.
Well, this could mean that I'm wrong. Or it could mean that we have
two different SIGSEGV problems with sendmail, one which possibly
doesn't relate to the "dying daemons" problem. As I said above, I
suspect my config file.
> Why people still try to pretend that this definitely kernel-related
> problem may be explained by user-level bugs? Yes, inetd is buggy
> (it was for ages), sendmail is buggy, etc. But on 2.x.x it seems
> nobody ever saw anything similar.
Why are you trying to insist that this is all just one bug? Yes, I'm
sure we have a kernel bug somewhere. I'm not sure that my dying
sendmail is caused by this bug.
> And why Dima's kludge make it go away all at once?
It hasn't made my dying sendmail go away, because I didn't install it.
BTW, we've had a massive phone cable failure here (4½ of 5 lines), and
I'm off the Net for a few days until they repair 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 Wed Nov 11 19:52:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA18065
for freebsd-current-outgoing; Wed, 11 Nov 1998 19:52:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18059
for <current@FreeBSD.org>; Wed, 11 Nov 1998 19:52:11 -0800 (PST)
(envelope-from gibbs@narnia.plutotech.com)
Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id UAA06531; Wed, 11 Nov 1998 20:45:04 -0700 (MST)
Date: Wed, 11 Nov 1998 20:45:04 -0700 (MST)
From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Message-Id: <199811120345.UAA06531@narnia.plutotech.com>
To: mjacob@feral.com
cc: current@FreeBSD.ORG
Subject: Re: sorry if I missed a thread here...
X-Newsgroups: pluto.freebsd.current
In-Reply-To: <Pine.LNX.4.02.9811090932220.13717-100000@feral-gw>
User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386))
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <Pine.LNX.4.02.9811090932220.13717-100000@feral-gw> you wrote:
>
> I'm having problems with 3.0-current (as of a day or so ago) where
> there are panics in the ffs code where a 'supervisor page not present'
> panic occurs (it occurred in ffs_fragextend for me).
I've seen this kind of thing happen if the disk driver returns EIO
to the filesystem at just the right time. I haven't found the time
to look into this any further though.
--
Justin
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 19:58:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA18471
for freebsd-current-outgoing; Wed, 11 Nov 1998 19:57: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 TAA18464
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 19:57:38 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id TAA05146;
Wed, 11 Nov 1998 19:52:35 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdzF5135; Thu Nov 12 03:52:29 1998
Date: Wed, 11 Nov 1998 19:51:48 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= " <dag-erli@ifi.uio.no>
cc: Brian Feldman <green@unixhelp.org>,
"Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <xzpd86tvepa.fsf@grjottunagard.ifi.uio.no>
Message-ID: <Pine.BSF.3.95.981111194903.16947A-100000@current1.whistle.com>
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 TAA18465
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 12 Nov 1998, Dag-Erling C. [iso-8859-1] Smørgrav wrote:
> Julian Elischer <julian@whistle.com> writes:
> > These are "embedded" FreeBSD machines.
> > they are all over the world.
> > We are certainly not in the position of bringing each back to the factory!
>
> Do they work?
>
> If they do, why upgrade them?
Security patches etc.
>
> If they don't, you have to fix them anyway.
they fetch updates overr the net.
but they don't have code to replace the bootblocks
to do that would mean 2 upgrades, one to get the new software that CAN do
so, and one to replace them.
>
> If you have the option of upgrading them at all (through remote
> administration), is it really that hard to run the *one* *single*
> command that's needed to upgrade the boot blocks?
>
> # disklabel -B -b /boot/boot1 -s /boot/boot2 /dev/foo0s1
>
> Even *I* can do that ;)
You assume there is a shell available.. (which there definitly is not).
>
> (OBTW, I assume you're talking about Interjets...?)
of course...
>
> DES
> --
> Dag-Erling Smørgrav - dag-erli@ifi.uio.no
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 20:00:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA18718
for freebsd-current-outgoing; Wed, 11 Nov 1998 20:00:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18713
for <current@FreeBSD.org>; Wed, 11 Nov 1998 20:00:28 -0800 (PST)
(envelope-from gibbs@narnia.plutotech.com)
Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id UAA06548; Wed, 11 Nov 1998 20:53:19 -0700 (MST)
Date: Wed, 11 Nov 1998 20:53:19 -0700 (MST)
From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Message-Id: <199811120353.UAA06548@narnia.plutotech.com>
To: The Hermit Hacker <scrappy@hub.org>
cc: current@FreeBSD.ORG
Subject: Re: SCSI Bus errors spewing on console...
X-Newsgroups: pluto.freebsd.current
In-Reply-To: <Pine.BSF.4.05.9811110012450.337-100000@thelab.hub.org>
User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386))
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <Pine.BSF.4.05.9811110012450.337-100000@thelab.hub.org> you wrote:
>
> Can someone tell me *what* this means?
It looks like one of your drives went nuts and started performing
reconnects with an invalid tag. What kind of drive do you have?
--
Justin
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 20:10:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA19814
for freebsd-current-outgoing; Wed, 11 Nov 1998 20:10: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 UAA19809
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 20:10:33 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id UAA05440;
Wed, 11 Nov 1998 20:03:06 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdfN5436; Thu Nov 12 04:03:02 1998
Date: Wed, 11 Nov 1998 20:02:27 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Brian Feldman <green@unixhelp.org>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <Pine.BSF.4.05.9811112136300.725-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.3.95.981111195924.16947C-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, 11 Nov 1998, Brian Feldman wrote:
> On Wed, 11 Nov 1998, Julian Elischer wrote:
>
> > hackish or not here's the picture..
> > The automatic upgrade provedure cannot replace bootblocks.
> > however we will soon only be able to profuce kernels the existing
> > bootblocks can't read/load.
> >
> > they look for a a.out file called /kernel
> >
> > we give them one.
> >
> > These are "embedded" FreeBSD machines.
> > they are all over the world.
> > We are certainly not in the position of bringing each back to the factory!
> >
> > julian
> >
> What exactly was wrong about having the old boot loader run (via
> boot.config) /boot/loader, and /boot/loader loading either an ELF or a.out
> /kernel? It works perfectly in this case, where I'm using all defaults in
> this case. And in an "embedded" system, wouldn't the
> partitioning/slicing/drive scheme be simplistic anyway?
the existing bootblocks predate "Boot.conf"
I think just changing the name of the 3rd stage boot to /kernel will do
the job nicely. There are lots of issues I can't really go into.
>
> Cheers,
> Brian Feldman
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 20:13:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA20073
for freebsd-current-outgoing; Wed, 11 Nov 1998 20:13: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 UAA20068
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 20:13: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.1/8.9.1) with ESMTP id UAA22701;
Wed, 11 Nov 1998 20:11:16 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
To: Brian Feldman <green@unixhelp.org>
cc: Peter Wemm <peter@netplex.com.au>, Julian Elischer <julian@whistle.com>,
Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 21:28:56 EST."
<Pine.BSF.4.05.9811112128210.725-100000@janus.syracuse.net>
Date: Wed, 11 Nov 1998 20:11:15 -0800
Message-ID: <22697.910843875@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On Thu, 12 Nov 1998, Peter Wemm wrote:
> > Call be crazy, but I think I'd almost like to move the "real" kernel to
> > /boot/kernel, providing the search paths were ok.
> >
>
> You're absolutely nuts.
Can we get postings in -current back on track? I'm seeing enough
Brian Feldman posts to justify a filter.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 20:14:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA20247
for freebsd-current-outgoing; Wed, 11 Nov 1998 20:14:02 -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 UAA20220
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 20:13:59 -0800 (PST)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.9.1/8.9.1) id PAA08645;
Thu, 12 Nov 1998 15:15:00 +1100 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199811120415.PAA08645@cimlogic.com.au>
Subject: Re: Is it soup yet? :-)
In-Reply-To: <Pine.BSF.3.95.981111194903.16947A-100000@current1.whistle.com> from Julian Elischer at "Nov 11, 98 07:51:48 pm"
To: julian@whistle.com (Julian Elischer)
Date: Thu, 12 Nov 1998 15:15:00 +1100 (EST)
Cc: dag-erli@ifi.uio.no, green@unixhelp.org, jkh@zippy.cdrom.com,
peter@netplex.com.au, mike@smith.net.au, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL40 (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:
> they fetch updates overr the net.
> but they don't have code to replace the bootblocks
> to do that would mean 2 upgrades, one to get the new software that CAN do
> so, and one to replace them.
So why can't you do that?!
Do you have dependencies between your upgrade versions (or whatever you
call them)?
It seems to me that there is little pain to be experienced due to
upgrading the boot blocks provided you can be sure that the new
blocks will work. And this is something that Whistle /can/ test in the
lab because you don't have to deal with unknown hardware.
Keeping hacked things around and having to support them in a.out format
long term when FreeBSD has moved on is unwise IMHO. As one burger chain
says: "resistance is useless" 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 Nov 11 20:14:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA20332
for freebsd-current-outgoing; Wed, 11 Nov 1998 20:14:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from feral-gw.feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20327
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 20:14:51 -0800 (PST)
(envelope-from mjacob@feral.com)
Received: from localhost (mjacob@localhost)
by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id TAA23633;
Wed, 11 Nov 1998 19:53:13 -0800
Date: Wed, 11 Nov 1998 19:53:13 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
X-Sender: mjacob@feral-gw
Reply-To: mjacob@feral.com
To: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
cc: current@FreeBSD.ORG
Subject: Re: sorry if I missed a thread here...
In-Reply-To: <199811120345.UAA06531@narnia.plutotech.com>
Message-ID: <Pine.LNX.4.02.9811111951550.23615-100000@feral-gw>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Yes- this might have been what happened (I had a port logout on that
disk).
However- other folks are seeing this panic w/o any other errors (that I
can tell). I'm stil gathering details as well as trying to run the 75
other threads currently being gang mis-scheduled in my mind.
-matt
On Wed, 11 Nov 1998, Justin T. Gibbs wrote:
> In article <Pine.LNX.4.02.9811090932220.13717-100000@feral-gw> you wrote:
> >
> > I'm having problems with 3.0-current (as of a day or so ago) where
> > there are panics in the ffs code where a 'supervisor page not present'
> > panic occurs (it occurred in ffs_fragextend for me).
>
> I've seen this kind of thing happen if the disk driver returns EIO
> to the filesystem at just the right time. I haven't found the time
> to look into this any further though.
>
> --
> Justin
>
> 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 Nov 11 20:16:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA20510
for freebsd-current-outgoing; Wed, 11 Nov 1998 20:16:13 -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 UAA20500;
Wed, 11 Nov 1998 20:16:11 -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.1/8.9.1) with ESMTP id UAA22742;
Wed, 11 Nov 1998 20:16:24 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
To: Peter Wemm <peter@netplex.com.au>
cc: asami@FreeBSD.ORG (Satoshi Asami), chuckr@mat.net, nate@mt.sri.com,
mike@smith.net.au, obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Thu, 12 Nov 1998 10:37:09 +0800."
<199811120237.KAA13939@spinner.netplex.com.au>
Date: Wed, 11 Nov 1998 20:16:24 -0800
Message-ID: <22738.910844184@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> of crud installed into /usr/mdec, which I object to installing on /. Since
> it looks like what is actually proposed is that the stuff that presently
> goes into /usr/mdec is going away and the present /boot/boot{0,1,2} that
> is already in /boot will stay - I can live with that.
Given Mike's recent (and much needed) reduction of the contents of
/usr/mdec stuff into a pile which is 95% obsolete or otherwise
insufficiently general to merit installation into /usr/<sometopleveldir>
and 5% which has already moved, I think we might just have the basis
for an agreement here. :-)
- Jordan
> different devices. Are we talking about changing this so that
> #ifdef i386
> defboot1 = "/boot/boot1";
> defboot2 = "/boot/boot2";
> #endif
> #ifdef alpha
> defboot1 = "/boot/boot1";
> defboot2 = NULL; /* alpha has only one boot block set */
> #endif
> ? Of course this would be overrideable by disktab and the command line,
> but I want to make sure we're not talking about a symlink tree in /boot..
Works for me. Other bits of code, like sysinstall, also have their
own dependencies on this.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 20:20:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA20878
for freebsd-current-outgoing; Wed, 11 Nov 1998 20:20:07 -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 UAA20871
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 20:20:05 -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.1/8.9.1) with ESMTP id UAA22781;
Wed, 11 Nov 1998 20:20:17 -0800 (PST)
(envelope-from jkh@zippy.cdrom.com)
To: Julian Elischer <julian@whistle.com>
cc: Brian Feldman <green@unixhelp.org>, Peter Wemm <peter@netplex.com.au>,
Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Wed, 11 Nov 1998 20:02:27 PST."
<Pine.BSF.3.95.981111195924.16947C-100000@current1.whistle.com>
Date: Wed, 11 Nov 1998 20:20:16 -0800
Message-ID: <22777.910844416@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Can we just end this thread? It's gotten more than a little bit
tiresome and if people have specific concerns about upgrading machines
in the field, they can take it up with the release engineers and/or
the core team. I don't think this is a -current topic with wide
interest, however.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 20:31:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA22193
for freebsd-current-outgoing; Wed, 11 Nov 1998 20:31:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.dyn.ml.org (sf3-53.ppp.wenet.net [206.15.84.53])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22185
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 20:31:30 -0800 (PST)
(envelope-from garbanzo@hooked.net)
Received: from localhost (garbanzo@localhost)
by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id UAA00648;
Wed, 11 Nov 1998 20:30:56 -0800 (PST)
(envelope-from garbanzo@hooked.net)
X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs
Date: Wed, 11 Nov 1998 20:30:55 -0800 (PST)
From: Alex Zepeda <garbanzo@hooked.net>
X-Sender: garbanzo@zippy.dyn.ml.org
To: The Hermit Hacker <scrappy@hub.org>
cc: Andrzej Bialecki <abial@nask.pl>,
=?ISO-8859-2?Q?S=F8ren_Schmidt?= <sos@freebsd.dk>,
daeron@Wit401305.student.utwente.nl, shawn@cpl.net, osa@etrust.ru,
current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <Pine.BSF.4.05.9811111952370.337-100000@thelab.hub.org>
Message-ID: <Pine.BSF.4.05.9811112024030.299-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 Wed, 11 Nov 1998, The Hermit Hacker wrote:
> Just curious, but what exactly does that '/proc/*/cmdline' thing
> "do", and is there any reason why it is inappropriate for it to be a
> standard part of our /proc?
It's a copy of argv[]. It's inappropiate for nearly anything, because
it's just bloat. Sh scripts can access argv via $0..$x, and a well
written C/C++ program does this in main.
> When talkign with friends that use Linux, and talking about our
> /proc file system, they think its hilarious that I can't go into proc and
> find out what irqs are being used by the system...maybe I'm missing
> something, but about the only way I can do it currently is to look through
> dmesg output? Is there another way?
OTOH I think it's hilarious that someone can crash a Linux system trying
to find info about their aic7xxx scsi adatper*. Perhaps extending kernfs
to mirror the sysctl tree, and a machfs for other hardware related
things (and then doing a union mount with/of devfs..) would be a good
idea. But extending procfs to mirror every ounce of Linux bloatware is
hardly a good thing, besides how are irqs an integral part of a process?
* Yes, older versions of the Linux aic7xxx driver did have problems like
this (2+ adapters created some sort of buffer overflow IIRC), obviously
it's fixed now.
- 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 Wed Nov 11 21:14:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA25655
for freebsd-current-outgoing; Wed, 11 Nov 1998 21:14:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles205.castles.com [208.214.165.205])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25650
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 21:14:38 -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 TAA07333;
Wed, 11 Nov 1998 19:45:56 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811120345.TAA07333@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Alfred Perlstein <bright@hotjobs.com>
cc: Brian Feldman <green@unixhelp.org>, current@FreeBSD.ORG
Subject: FreeBSD NFS (was Re: Is it soup yet? FreeBSD NFS)
In-reply-to: Your message of "Wed, 11 Nov 1998 22:04:43 EST."
<Pine.BSF.4.05.9811112154240.370-100000@porkfriedrice.ny.genx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 19:45:56 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> A recent Linux article suggests that Linux NFS will bipass the "mbuf"
> layer, ie. the NFS code will directly reassemble packets into RPC requests
> thereby saving _one_ copy of memory. This is really neat, but then makes
> NFS dependant on the protocols which it is supposed to be independant of.
The BSD kernel NFS code already does this; it contains some quite
frightening macros which directly manipulate mbuf state.
> Btw, Mike Smith's new ACCESS caching seems quite stable and i was
> wondering if it had been commited.
No, I haven't had time to commit it yet. I've been given a cleaner
version by a contributor, and I'm still investigating cases where it's
possible that the cached mode should be invalidated.
I'd love to hear from anyone that can conclusively confirm that nfsnode
structures are *always* obtained via nfs_nget when attached to a new
vnode, or when the vnode is retargetted. The cache hit rates that have
been reported have me wondering if they're not actually being maintained
(in the name cache maybe?) across multiple references to the same file.
After my exam tomorrow morning, I hope to be able to clear a few
low-overhead tasks such as this from my stack. So far all the feedback
I've received has been very positive; the though of reducing wire
traffic for an NFS-mounted world build by several hundred MB is quite
appealing. 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 Wed Nov 11 21:26:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA27166
for freebsd-current-outgoing; Wed, 11 Nov 1998 21:26:00 -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 VAA27142
for <current@freebsd.org>; Wed, 11 Nov 1998 21:25:57 -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 0zdpGE-0005qh-00; Wed, 11 Nov 1998 22:25: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 WAA20659; Wed, 11 Nov 1998 22:25:54 -0700 (MST)
Message-Id: <199811120525.WAA20659@harmony.village.org>
To: Andreas Klemm <andreas@klemm.gtn.com>
Subject: Re: Travan TR4 dump/restore
Cc: Tony Maher <tonym@angis.usyd.edu.au>, current@FreeBSD.ORG
In-reply-to: Your message of "Tue, 10 Nov 1998 14:57:43 +0100."
<19981110145743.A23087@klemm.gtn.com>
References: <19981110145743.A23087@klemm.gtn.com> <199811101144.WAA29147@morgan.angis.su.OZ.AU>
Date: Wed, 11 Nov 1998 22:25:54 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <19981110145743.A23087@klemm.gtn.com> Andreas Klemm writes:
: On Tue, Nov 10, 1998 at 10:44:04PM +1100, Tony Maher wrote:
: > dump 0uabf 64 /dev/nrsa0 /n/02
: > Dumps run without any errors, but trying to restore get
: > "resync restore, skipped 33 blocks"
:
: What if you use 32 blocks ?
:
: dump 0uabf 32 /dev/nrsa0 /
I know that I do my atapi ide tr-4 can only handle i/os up to 56k
before it starts barfing. Given that it is skipping 33 blocks, I'd
suggest a blocksize of 30 or 28.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 21:27:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA27326
for freebsd-current-outgoing; Wed, 11 Nov 1998 21:27:44 -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 VAA27321
for <current@freebsd.org>; Wed, 11 Nov 1998 21:27: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 0zdpHu-0005ql-00; Wed, 11 Nov 1998 22:27:22 -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 WAA20677; Wed, 11 Nov 1998 22:27:38 -0700 (MST)
Message-Id: <199811120527.WAA20677@harmony.village.org>
To: Andreas Klemm <andreas@klemm.gtn.com>
Subject: Re: Travan TR4 dump/restore
Cc: Tony Maher <tonym@angis.usyd.edu.au>, current@FreeBSD.ORG,
mjacob@feral-gw.FreeBSD.ORG
In-reply-to: Your message of "Tue, 10 Nov 1998 21:38:17 +0100."
<19981110213817.A13182@klemm.gtn.com>
References: <19981110213817.A13182@klemm.gtn.com> <199811101953.GAA10195@morgan.angis.su.OZ.AU>
Date: Wed, 11 Nov 1998 22:27:38 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <19981110213817.A13182@klemm.gtn.com> Andreas Klemm writes:
: my personal experience was, that it's now safe with CAM to use
: blocksizes over 32 .... Since physio (if I remember right) was
: done in 32 blocks chunks even is you choose 64 or more ...
I think it may be a buggy implementation of the scsi spec in this tape
drive rather than a problem with the cam code.... tr-4 drives tend
to be junk...
Warner
P.S. I use a tr-4 for backups myself...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 21:38:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA28304
for freebsd-current-outgoing; Wed, 11 Nov 1998 21:38:44 -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 VAA28297
for <current@freebsd.org>; Wed, 11 Nov 1998 21:38:43 -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 0zdpSZ-0005r8-00; Wed, 11 Nov 1998 22:38:24 -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 WAA20759; Wed, 11 Nov 1998 22:38:40 -0700 (MST)
Message-Id: <199811120538.WAA20759@harmony.village.org>
To: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= )
Subject: Re: Is it soup yet? :-)
Cc: current@FreeBSD.ORG
In-reply-to: Your message of "12 Nov 1998 02:22:41 +0100."
<xzpn25xvh5q.fsf@grjottunagard.ifi.uio.no>
References: <xzpn25xvh5q.fsf@grjottunagard.ifi.uio.no> <Pine.BSF.3.95.981111112705.16498A-100000@current1.whistle.com>
Date: Wed, 11 Nov 1998 22:38:40 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <xzpn25xvh5q.fsf@grjottunagard.ifi.uio.no> Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= writes:
: For originality's sake, how about vmunix? :)
Nah, originality would require vmduck....
Warner
P.S. This is the only thing I'm going to post on this thread...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 22:27:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA02442
for freebsd-current-outgoing; Wed, 11 Nov 1998 22:27:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.webspan.net (mail.webspan.net [206.154.70.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02437
for <freebsd-current@FreeBSD.ORG>; Wed, 11 Nov 1998 22:27:27 -0800 (PST)
(envelope-from opsys@mail.webspan.net)
Received: from orion.webspan.net (orion.webspan.net [206.154.70.5])
by mail.webspan.net (WEBSPAN/970608) with SMTP id BAA00607;
Thu, 12 Nov 1998 01:27:03 -0500 (EST)
Date: Thu, 12 Nov 1998 01:26:59 -0500 (EST)
From: Open Systems Networking <opsys@mail.webspan.net>
X-Sender: opsys@orion.webspan.net
To: Luoqi Chen <luoqi@watermarkgroup.com>
cc: Don.Lewis@tsc.tdk.com, freebsd-current@FreeBSD.ORG
Subject: Re: Softupdates in current problem..
In-Reply-To: <199811112324.SAA15367@lor.watermarkgroup.com>
Message-ID: <Pine.BSF.4.02.9811120124001.18248-100000@orion.webspan.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, 11 Nov 1998, Luoqi Chen wrote:
> Chris has a stale copy of ffs_softdep.c (it's better to make it a symlink
> to contrib/sys/softupdates/ffs_softdep.c). A couple of weeks ago, the
> clean/dirty buf queues were changed from LISTQ to TAILQ.
*sigh* someone removed my freakin symlinks from
/usr/src/contrib/sys/softupdates to /sys/ufs/ffs and they were not
updating. Sorry. *WHACK* *WHACK* *WHACK*
Chris
--
"You both seem to be ignoring the fact that the networking market is
driven by so-called 'IT professionals' these days, most of whom can't
tell the difference between an ARP and a carp." --Wes Peters
===================================| Open Systems FreeBSD Consulting.
FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186
-----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134
FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net
http://www.freebsd.org | Consulting, Network Engineering, Security
===================================| http://open-systems.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 22:46:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA04071
for freebsd-current-outgoing; Wed, 11 Nov 1998 22:46:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mx2.ews.uiuc.edu (mx2.ews.uiuc.edu [130.126.161.238])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04066
for <current@freebsd.org>; Wed, 11 Nov 1998 22:46:35 -0800 (PST)
(envelope-from pljohnsn@uiuc.edu)
Received: from petedorm (isr3193.urh.uiuc.edu [130.126.64.183])
by mx2.ews.uiuc.edu (8.8.8/8.8.8) with SMTP id AAA20720
for <current@freebsd.org>; Thu, 12 Nov 1998 00:46:10 -0600
Message-Id: <3.0.5.32.19981112004611.00965100@ews.uiuc.edu>
X-Sender: pljohnsn@ews.uiuc.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Thu, 12 Nov 1998 00:46:11 -0600
To: current@FreeBSD.ORG
From: Peter Johnson <pljohnsn@uiuc.edu>
Subject: XFree86 nonstandard server / ELF compat problem
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 is _hopefully_ only a temporary problem (should be fixed when
next version of XF86 comes out).
Well, I finally was able to upgrade my system to ELF (yay). I love it, the
only problem is that X causes some rather bizzare things with my system.
I'm certain it's due to the fact that I'm using an a.out X server binary
(which I can't update because no source will be available until XFree86
3.3.3). The X server worked perfectly before upgrading to ELF..
Amazingly, the server actually starts up and seems to run ok (window
manager, xterm prompts start, etc), but I immediately am almost flooded by
kernel messages "calcru: negative time of -48128 usec for pid 342 (xterm)"
[with the time/pid/name changing]. Exiting the X server returns me to text
mode prompt, but I continue getting the calcru messages. If I try to run
top or do anything other than just list files, it seems, I get a nasty
message "cputime limit exceeded". End up not being able to shutdown
(because every process dies with a whole bunch of calcru messsages followed
immediately by a cputime message) and need to reset.
Ugh.. now I _need_ XF86 3.3.3 so I can compile the whole darn thing as ELF!!
(note: I'm using the SuSe ELSA GLORIA server for FreeBSD 2.1.5--tried to
use the Linux ELF binary, with no success)
I got the same messages right after upgrading to ELF, so I
recompiled/reinstalled the XFree86 port (compiling as ELF).. didn't fix it
*sigh*
Regards,
Peter Johnson
locke@mcs.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 22:51:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA04387
for freebsd-current-outgoing; Wed, 11 Nov 1998 22:51:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles205.castles.com [208.214.165.205])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04382
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 22:51: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 WAA08374;
Wed, 11 Nov 1998 22:48:42 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811120648.WAA08374@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Peter Johnson <pljohnsn@uiuc.edu>
cc: current@FreeBSD.ORG
Subject: Re: XFree86 nonstandard server / ELF compat problem
In-reply-to: Your message of "Thu, 12 Nov 1998 00:46:11 CST."
<3.0.5.32.19981112004611.00965100@ews.uiuc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 22:48:41 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
The symptoms you're seeing are typically indicative of an interrupt
storm - the driver is enabling interrupts on the card but there is no
handler for them.
This is most likely a bug in the server.
> Note--this is _hopefully_ only a temporary problem (should be fixed when
> next version of XF86 comes out).
>
> Well, I finally was able to upgrade my system to ELF (yay). I love it, the
> only problem is that X causes some rather bizzare things with my system.
> I'm certain it's due to the fact that I'm using an a.out X server binary
> (which I can't update because no source will be available until XFree86
> 3.3.3). The X server worked perfectly before upgrading to ELF..
>
> Amazingly, the server actually starts up and seems to run ok (window
> manager, xterm prompts start, etc), but I immediately am almost flooded by
> kernel messages "calcru: negative time of -48128 usec for pid 342 (xterm)"
> [with the time/pid/name changing]. Exiting the X server returns me to text
> mode prompt, but I continue getting the calcru messages. If I try to run
> top or do anything other than just list files, it seems, I get a nasty
> message "cputime limit exceeded". End up not being able to shutdown
> (because every process dies with a whole bunch of calcru messsages followed
> immediately by a cputime message) and need to reset.
>
> Ugh.. now I _need_ XF86 3.3.3 so I can compile the whole darn thing as ELF!!
>
> (note: I'm using the SuSe ELSA GLORIA server for FreeBSD 2.1.5--tried to
> use the Linux ELF binary, with no success)
>
> I got the same messages right after upgrading to ELF, so I
> recompiled/reinstalled the XFree86 port (compiling as ELF).. didn't fix it
> *sigh*
>
> Regards,
> Peter Johnson
> locke@mcs.net
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
--
\\ 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 Nov 11 22:53:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA04631
for freebsd-current-outgoing; Wed, 11 Nov 1998 22:53:23 -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 WAA04626
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 22:53:22 -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.1a/8.9.1) with ESMTP id WAA00600;
Wed, 11 Nov 1998 22:54:14 -0800 (PST)
To: Peter Johnson <pljohnsn@uiuc.edu>
cc: current@FreeBSD.ORG
Subject: Re: XFree86 nonstandard server / ELF compat problem
In-reply-to: Your message of "Thu, 12 Nov 1998 00:46:11 CST."
<3.0.5.32.19981112004611.00965100@ews.uiuc.edu>
Date: Wed, 11 Nov 1998 22:54:14 -0800
Message-ID: <596.910853654@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Well, I finally was able to upgrade my system to ELF (yay). I love it, the
> only problem is that X causes some rather bizzare things with my system.
> I'm certain it's due to the fact that I'm using an a.out X server binary
I don't think it's that - your a.out X server binary should be fine.
I have a Riva TNT based card myself (STB 4400) using the XF86_RIVA
binary on the net which is a.out and works just great. 1600x1200x32
is no problem with this beast. :)
> Amazingly, the server actually starts up and seems to run ok (window
> manager, xterm prompts start, etc), but I immediately am almost flooded by
> kernel messages "calcru: negative time of -48128 usec for pid 342 (xterm)"
I think this is a different symptom of a different (kernel) problem
but I don't know enough about the new clock code to suggest remedies.
Perhaps phk or Mike will speak up.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 22:54:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA04758
for freebsd-current-outgoing; Wed, 11 Nov 1998 22:54: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 WAA04752
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 22:54:17 -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.1a/8.9.1) with ESMTP id WAA00625;
Wed, 11 Nov 1998 22:54:59 -0800 (PST)
To: Mike Smith <mike@smith.net.au>
cc: Peter Johnson <pljohnsn@uiuc.edu>, current@FreeBSD.ORG
Subject: Re: XFree86 nonstandard server / ELF compat problem
In-reply-to: Your message of "Wed, 11 Nov 1998 22:48:41 PST."
<199811120648.WAA08374@dingo.cdrom.com>
Date: Wed, 11 Nov 1998 22:54:58 -0800
Message-ID: <622.910853698@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> This is most likely a bug in the server.
Are you sure he wasn't using the same server before without problems
before the upgrade? That's the way I read it, anyway.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 23:06:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA05401
for freebsd-current-outgoing; Wed, 11 Nov 1998 23:06:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles205.castles.com [208.214.165.205])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05396
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 23:06:46 -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 XAA08543;
Wed, 11 Nov 1998 23:04:10 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811120704.XAA08543@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: Peter Johnson <pljohnsn@uiuc.edu>, current@FreeBSD.ORG
Subject: Re: XFree86 nonstandard server / ELF compat problem
In-reply-to: Your message of "Wed, 11 Nov 1998 22:54:58 PST."
<622.910853698@zippy.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 11 Nov 1998 23:04:10 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > This is most likely a bug in the server.
>
> Are you sure he wasn't using the same server before without problems
> before the upgrade? That's the way I read it, anyway.
No, I'm not. But the symptoms are indeed indicative of an interrupt
storm, or something else that's seriously screwing up interrupt
delivery, and the finger is pointed fairly squarely at the X server.
Peter, are you using an ELF kernel?
--
\\ 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 Nov 11 23:27:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA06736
for freebsd-current-outgoing; Wed, 11 Nov 1998 23:27:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from wcug.wwu.edu (sloth.wcug.wwu.edu [140.160.164.200])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA06731
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 23:27:03 -0800 (PST)
(envelope-from tcole@wcug.wwu.edu)
Received: (qmail 9409 invoked by uid 1085); 12 Nov 1998 07:26:47 -0000
Message-ID: <19981111232647.B9024@wcug.wwu.edu>
Date: Wed, 11 Nov 1998 23:26:47 -0800
From: Travis Cole <tcole@wcug.wwu.edu>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: current@FreeBSD.ORG
Subject: Re: XFree86 nonstandard server / ELF compat problem
References: <3.0.5.32.19981112004611.00965100@ews.uiuc.edu> <596.910853654@zippy.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <596.910853654@zippy.cdrom.com>; from Jordan K. Hubbard on Wed, Nov 11, 1998 at 10:54:14PM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Nov 11, 1998 at 10:54:14PM -0800, Jordan K. Hubbard wrote:
>
> I don't think it's that - your a.out X server binary should be fine.
> I have a Riva TNT based card myself (STB 4400) using the XF86_RIVA
> binary on the net which is a.out and works just great. 1600x1200x32
> is no problem with this beast. :)
>
Where did you get that XF86_RIVA binary? I haven't had the time (nor
the skill?) to get a Riva TNT patched XF86 3.3.2 source to completely
build on -CURRENT.
Thanks....
--
--Travis
"Microsoft: This is where you will go today!"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 23:36:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA07571
for freebsd-current-outgoing; Wed, 11 Nov 1998 23:36:24 -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 XAA07566
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 23:36:23 -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.1a/8.9.1) with ESMTP id XAA00778;
Wed, 11 Nov 1998 23:37:16 -0800 (PST)
To: Travis Cole <tcole@wcug.wwu.edu>
cc: current@FreeBSD.ORG
Subject: Re: XFree86 nonstandard server / ELF compat problem
In-reply-to: Your message of "Wed, 11 Nov 1998 23:26:47 PST."
<19981111232647.B9024@wcug.wwu.edu>
Date: Wed, 11 Nov 1998 23:37:16 -0800
Message-ID: <774.910856236@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Where did you get that XF86_RIVA binary? I haven't had the time (nor
Erm, I don't remember. :) I found it by alta vista searching with
the usual obvious parameters..
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 11 23:40:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA07877
for freebsd-current-outgoing; Wed, 11 Nov 1998 23:40:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mx2.ews.uiuc.edu (mx2.ews.uiuc.edu [130.126.161.238])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07872
for <current@freebsd.org>; Wed, 11 Nov 1998 23:40:07 -0800 (PST)
(envelope-from pljohnsn@uiuc.edu)
Received: from petedorm (isr3193.urh.uiuc.edu [130.126.64.183])
by mx2.ews.uiuc.edu (8.8.8/8.8.8) with SMTP id BAA16030;
Thu, 12 Nov 1998 01:39:39 -0600
Message-Id: <3.0.5.32.19981112013941.00a0fb30@ews.uiuc.edu>
X-Sender: pljohnsn@ews.uiuc.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Thu, 12 Nov 1998 01:39:41 -0600
To: Mike Smith <mike@smith.net.au>
From: Peter Johnson <pljohnsn@uiuc.edu>
Subject: Re: XFree86 nonstandard server / ELF compat problem
Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, 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
Not to my knowledge :)
I rebuilt the kernel after going to ELF, but I didn't do anything special
(should it default to ELF or a.out on a ELF system?)
BTW, this is the XFCom_3DLabs XuSe server...
Thanks,
Peter Johnson
locke@mcs.net
At 11:04 PM 11/11/98 -0800, you wrote:
>> > This is most likely a bug in the server.
>>
>> Are you sure he wasn't using the same server before without problems
>> before the upgrade? That's the way I read it, anyway.
>
>No, I'm not. But the symptoms are indeed indicative of an interrupt
>storm, or something else that's seriously screwing up interrupt
>delivery, and the finger is pointed fairly squarely at the X server.
>
>Peter, are you using an ELF kernel?
>
>--
>\\ 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 Nov 11 23:42:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA08171
for freebsd-current-outgoing; Wed, 11 Nov 1998 23:42:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mx2.ews.uiuc.edu (mx2.ews.uiuc.edu [130.126.161.238])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08166
for <current@FreeBSD.ORG>; Wed, 11 Nov 1998 23:42:06 -0800 (PST)
(envelope-from locke@mcs.net)
Received: from petedorm (isr3193.urh.uiuc.edu [130.126.64.183])
by mx2.ews.uiuc.edu (8.8.8/8.8.8) with SMTP id BAA16842;
Thu, 12 Nov 1998 01:41:37 -0600
Message-Id: <3.0.5.32.19981112014138.00958e40@popmail.mcs.net>
X-Sender: locke@popmail.mcs.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Thu, 12 Nov 1998 01:41:38 -0600
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
From: Peter Johnson <locke@mcs.net>
Subject: Re: XFree86 nonstandard server / ELF compat problem
Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
In-Reply-To: <622.910853698@zippy.cdrom.com>
References: <Your message of "Wed, 11 Nov 1998 22:48:41 PST." <199811120648.WAA08374@dingo.cdrom.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, I was, but now (doh) I've upgraded to the newest one (and now no way
to test the new server on the old a.out system..) *sigh*
Thanks,
Peter Johnson
locke@mcs.net
At 10:54 PM 11/11/98 -0800, Jordan K. Hubbard wrote:
>> This is most likely a bug in the server.
>
>Are you sure he wasn't using the same server before without problems
>before the upgrade? That's the way I read it, anyway.
>
>- Jordan
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-current" in the body of the message
>
>
-------------------------------------
Peter Johnson
-------------------------------------
locke@mcs.net
http://locke.home.ml.org
PGP Keys available from above address.
-------------------------------------
Freelance C/C++/Java/Pascal/Asm programmer
for DJGPP, Borland, and Watcom compilers
Member of BiLogic demo group
-> http://BiLogic.home.ml.org/
-------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 00:05:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA09838
for freebsd-current-outgoing; Thu, 12 Nov 1998 00:05:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mx2.ews.uiuc.edu (mx2.ews.uiuc.edu [130.126.161.238])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09833
for <current@freebsd.org>; Thu, 12 Nov 1998 00:05:22 -0800 (PST)
(envelope-from pljohnsn@uiuc.edu)
Received: from petedorm (isr3193.urh.uiuc.edu [130.126.64.183])
by mx2.ews.uiuc.edu (8.8.8/8.8.8) with SMTP id CAA16808;
Thu, 12 Nov 1998 02:05:01 -0600
Message-Id: <3.0.5.32.19981112020503.009dfeb0@ews.uiuc.edu>
X-Sender: pljohnsn@ews.uiuc.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Thu, 12 Nov 1998 02:05:03 -0600
To: current@FreeBSD.ORG
From: Peter Johnson <pljohnsn@uiuc.edu>
Subject: Eurika! (Re: XFree86 nonstandard server / ELF compat problem)
Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, Mike Smith <mike@smith.net.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Well, got it to work. The problem _was_ the X server. XuSe has made
available 3 versions of their 3DLabs (ELSA GLoria/XL) X server: 4.01, 4.1,
and 4.31. The first two work. The latest (4.31) does NOT (it gives me the
nasty messages :). Someone needs to tell the XuSe folks about this before
it gets merged into XFree86 and causes problems for other FreeBSD people.
I have no way to tell if this version works under a.out FreeBSD, but it
sure doesn't under ELF (I can say that the other two versions work under
both a.out and ELF, however).
For me, at the moment, I'm just glad I got it working. :) Hope it gets
fixed, though (I like to stay updated with current versions of things as
much as possible).
Thanks for your help!
Peter Johnson
locke@mcs.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 00:28:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA11371
for freebsd-current-outgoing; Thu, 12 Nov 1998 00:28:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from omnix.net (omnix.net [194.183.217.130])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11366
for <freebsd-current@FreeBSD.ORG>; Thu, 12 Nov 1998 00:28:51 -0800 (PST)
(envelope-from didier@omnix.net)
Received: from localhost (didier@localhost)
by omnix.net (8.8.7/8.8.7) with SMTP id IAA01461;
Thu, 12 Nov 1998 08:28:17 GMT
(envelope-from didier@omnix.net)
Date: Thu, 12 Nov 1998 09:28:14 +0100 (CET)
From: Didier Derny <didier@omnix.net>
To: jack <jack@germanium.xtalwind.net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Tekram DC-390 and 3.0
In-Reply-To: <Pine.BSF.4.05.9811111510340.24083-100000@germanium.xtalwind.net>
Message-ID: <Pine.BSF.3.96.981112092722.1183A-100000@omnix.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
It works fine for me,
I'm using the ncr0 driver.
On Wed, 11 Nov 1998, jack wrote:
>
> Before I order one, can anyone verify that the Tekram DC-390
> controller still works with current?
>
> Thanks.
>
> --------------------------------------------------------------------------
> Jack O'Neill Systems Administrator / Systems Analyst
> jack@germanium.xtalwind.net Crystal Wind Communications, Inc.
> Finger jack@germanium.xtalwind.net for my PGP key.
> PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD
> enriched, vcard, HTML messages > /dev/null
> --------------------------------------------------------------------------
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
--
Didier Derny
didier@omnix.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 00:29:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA11617
for freebsd-current-outgoing; Thu, 12 Nov 1998 00:29:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11603;
Thu, 12 Nov 1998 00:29:27 -0800 (PST)
(envelope-from dv@dv.ru)
Received: from localhost (dv@localhost)
by xkis.kis.ru (8.9.0/8.9.0) with SMTP id LAA13810;
Thu, 12 Nov 1998 11:28:48 +0300 (MSK)
Date: Thu, 12 Nov 1998 11:28:45 +0300 (MSK)
From: Dmitry Valdov <dv@dv.ru>
X-Sender: dv@xkis.kis.ru
To: Brian Somers <brian@Awfulhak.org>
cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
In-Reply-To: <199811120112.BAA04700@woof.lan.awfulhak.org>
Message-ID: <Pine.BSF.3.95q.981112111129.13038A-100000@xkis.kis.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, 12 Nov 1998, Brian Somers wrote:
> Date: Thu, 12 Nov 1998 01:12:37 +0000
> From: Brian Somers <brian@Awfulhak.org>
> To: Dmitry Valdov <dv@dv.ru>
> Cc: Brian Somers <brian@freebsd.org>, current@freebsd.org
> Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
>
> In the log, does it mention something like:
>
> deflink: /dev/cuaa0 doesn't support CD
No. I've aready said that the problem exists periodicaly (~ in 5-10% cases).
Once again - I'm really sure that modem is configured properly, port/modem
correctly handles CD signal and it connected when script finished.. Just
believe me because I've experience with modems since 1990 :)
>
> ? This will happen if your modem doesn't show a CD signal at all
> when LCP is started. If this is the case, your modem is
> misconfigured, or isn't connected when your dial/login scripts have
> finished.
>
> > Hi!
> >
> > Just have this problem again. With debug set on. ppp thinks that
> > everything is ok, but modem already hanged up. When I kill it with -1 it
> > says that
> > it normally terminated the connection then exit.
> > I think the workaround is to send ate0 to modem because it sends something
> > to modem and receiving it :) But default config has ATE1 in it.
> > I'm *really* sure that my modem is configured properly and it's not a user
> > error :)
> >
> > What can I do to help you to resolve the problem? I'm using dial-on-demand
> > (pmdemand section) and running ppp with a command ppp -auto pmdemand.
> >
> >
> > On Wed, 11 Nov 1998, Dmitry Valdov wrote:
> >
> > >
> > >
> > > ---------- Forwarded message ----------
> > > Date: Tue, 10 Nov 1998 21:32:53 +0000
> > > From: Brian Somers <brian@Awfulhak.org>
> > > To: Kris Kennaway <kkennawa@physics.adelaide.edu.au>
> > > Cc: Dmitry Valdov <dv@dv.ru>, Brian Somers <brian@freebsd.org>,
> > > current@freebsd.org
> > > Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
> > >
> > > > On Tue, 10 Nov 1998, Dmitry Valdov wrote:
> > > >
> > > > > Also there is one more bug - sometimes ppp don't detect carrier lost and
> > > > > stays in open state for a long time. :(
> > > >
> > > > Sorry for the "implicit bug report", Brian, but I've been meaning to track
> > > > this down for a long time and make sure it's not user error. I often see this
> > > > as well - it's noticeable for me because I have ipfw installed and when the
> > > > modem drops carrier I see packets being 'reflected' by the modem's local echo
> > > > (I assume), and bouncing off the ipfw 'incoming address of myself' filter.
> > >
> > > Try ``set log +debug''. You should see the online/offline status of
> > > the link at frequent intervals. If this doesn't agree with your
> > > modem, then you modem may be misconfigured.
> > >
> > > > Kris
>
> --
> 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 Nov 12 00:40:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA12724
for freebsd-current-outgoing; Thu, 12 Nov 1998 00:40:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from poboxer.pobox.com ([208.141.230.127])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12712
for <current@freebsd.org>; Thu, 12 Nov 1998 00:40:52 -0800 (PST)
(envelope-from alk@poboxer.pobox.com)
Received: (from alk@localhost) by poboxer.pobox.com (8.9.1/8.7.3) id CAA11255; Thu, 12 Nov 1998 02:39:53 -0600 (CST)
From: Tony Kimball <anthony.kimball@east.sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 12 Nov 1998 02:39:52 -0600 (CST)
X-Face: O9M"E%K;(f-Go/XDxL+pCxI5<W_e*r7B8ojMD.5+qDgOp4/\gTQEgbOoBqf:Vtl*aW:<;9/
UIVk'U^XhYg+v#r~*X<$Q=_ik@5:%E}pl]9|9|:]WLW8n:fLgg0~cfwWRBQxK/HSG0b1D/gljJC$qp
b=HDF@+"H<|fXy`w#$8#6A"!F:>*gr[=FN@Y`cl1.Tn
Reply-To: alk@pobox.com
To: current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <13898.40443.642502.918589@avalon.east>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 12 Nov 1998, Peter Wemm wrote:
> Call be crazy, but I think I'd almost like to move the "real" kernel to
> /boot/kernel, providing the search paths were ok.
Now that would be a substantial improvement: No more files in /.
This suggests that / could go away. I like it!
Further quoth Peter Wemm:
: > And the bootblocks might be needed for emergency repair.
...
: What is going to get put on this bootable
: installation on the second disk if you can't mount /usr?
FreeBSD. Remember /stand?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 00:58:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA14742
for freebsd-current-outgoing; Thu, 12 Nov 1998 00:58:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from myrddin.demon.co.uk (myrddin.demon.co.uk [158.152.54.180])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14737
for <current@freebsd.org>; Thu, 12 Nov 1998 00:58:48 -0800 (PST)
(envelope-from dom@myrddin.demon.co.uk)
Received: from localhost (myrddin.demon.co.uk) [127.0.0.1]
by myrddin.demon.co.uk with esmtp (Exim 1.92 #1)
id 0zdr1S-00005B-00; Thu, 12 Nov 1998 07:18:30 +0000
To: Terry Lambert <tlambert@primenet.com>
Cc: mike@smith.net.au (Mike Smith), abial@nask.pl, current@FreeBSD.ORG
Subject: Re: BootForth (was Re: New boot loader and alternate kernels)
References: <199811041949.MAA12999@usr07.primenet.com>
From: Dom Mitchell <dom@myrddin.demon.co.uk>
In-Reply-To: Terry Lambert's message of "Wed, 4 Nov 1998 19:49:08 +0000 (GMT)"
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Date: Thu, 12 Nov 1998 07:18:30 +0000
Message-Id: <E0zdr1S-00005B-00.qmail@myrddin.demon.co.uk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
[Sorry for popping in late - been on hols]
Terry Lambert <tlambert@primenet.com> writes:
> I will admit to having a cartridge for my C64, and having
> fought with the Sun Console (and lost) a long time ago...
Please note that there is extensive documentation on the Sun Open Boot
Prom over on <URL:http://docs.sun.com/>. Have a look for the OBP
Reference Manual. Some of it may well prove interesting.
There has also been a couple of articles about it in Sunworld. You
may also wish to search there.
--
``Bernstein versus Venema Celebrity Deathmatch: I see a great need.'' -- MR
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 01:23:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA16549
for freebsd-current-outgoing; Thu, 12 Nov 1998 01:23:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles205.castles.com [208.214.165.205])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16544
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 01:23:13 -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 BAA09287;
Thu, 12 Nov 1998 01:20:44 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811120920.BAA09287@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Peter Johnson <pljohnsn@uiuc.edu>
cc: current@FreeBSD.ORG
Subject: Re: Eurika! (Re: XFree86 nonstandard server / ELF compat problem)
In-reply-to: Your message of "Thu, 12 Nov 1998 02:05:03 CST."
<3.0.5.32.19981112020503.009dfeb0@ews.uiuc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 12 Nov 1998 01:20:44 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Well, got it to work. The problem _was_ the X server. XuSe has made
> available 3 versions of their 3DLabs (ELSA GLoria/XL) X server: 4.01, 4.1,
> and 4.31. The first two work. The latest (4.31) does NOT (it gives me the
> nasty messages :). Someone needs to tell the XuSe folks about this before
> it gets merged into XFree86 and causes problems for other FreeBSD people.
That would be you, since you have the hardware and all the symptoms to
hand...
--
\\ 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 Nov 12 01:27:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA16863
for freebsd-current-outgoing; Thu, 12 Nov 1998 01:27:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16853
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 01:27:46 -0800 (PST)
(envelope-from ulf@Gatekeeper.Alameda.net)
Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id BAA29782;
Thu, 12 Nov 1998 01:27:20 -0800 (PST)
Message-ID: <19981112012720.A29150@Alameda.net>
Date: Thu, 12 Nov 1998 01:27:20 -0800
From: Ulf Zimmermann <ulf@Alameda.net>
To: Mike Smith <mike@smith.net.au>, Peter Johnson <pljohnsn@uiuc.edu>
Cc: current@FreeBSD.ORG
Subject: Re: Eurika! (Re: XFree86 nonstandard server / ELF compat problem)
Reply-To: ulf@Alameda.net
References: <3.0.5.32.19981112020503.009dfeb0@ews.uiuc.edu> <199811120920.BAA09287@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199811120920.BAA09287@dingo.cdrom.com>; from Mike Smith on Thu, Nov 12, 1998 at 01:20:44AM -0800
Organization: Alameda Networks, Inc.
X-Operating-System: FreeBSD 2.2.6-STABLE
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, Nov 12, 1998 at 01:20:44AM -0800, Mike Smith wrote:
> > Well, got it to work. The problem _was_ the X server. XuSe has made
> > available 3 versions of their 3DLabs (ELSA GLoria/XL) X server: 4.01, 4.1,
> > and 4.31. The first two work. The latest (4.31) does NOT (it gives me the
> > nasty messages :). Someone needs to tell the XuSe folks about this before
> > it gets merged into XFree86 and causes problems for other FreeBSD people.
>
> That would be you, since you have the hardware and all the symptoms to
> hand...
I installed the Suse XFCom_3DLabs server binary for FreeBSD 2.2.5 on
a FreeBSD 3.0-RELEASE. It is the version 4.31 and it works fine.
>
> --
> \\ 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
--
Regards, Ulf.
---------------------------------------------------------------------
Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936
Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 02:07:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA19600
for freebsd-current-outgoing; Thu, 12 Nov 1998 02:07:40 -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 CAA19595
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 02:07:36 -0800 (PST)
(envelope-from geoffb@gti.noc.demon.net)
Received: by server.noc.demon.net; id KAA17677; Thu, 12 Nov 1998 10:07:16 GMT
Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2)
id xma017654; Thu, 12 Nov 98 10:07:02 GMT
Received: (from geoffb@localhost)
by gti.noc.demon.net (8.8.8/8.8.8) id KAA29247
for current@FreeBSD.ORG; Thu, 12 Nov 1998 10:07:01 GMT
From: Geoff Buckingham <geoffb@gti.noc.demon.net>
Message-Id: <199811121007.KAA29247@gti.noc.demon.net>
Subject: DEC Multia support
To: current@FreeBSD.ORG
Date: Thu, 12 Nov 1998 10:07:01 +0000 (GMT)
Reply-To: geoffb@demon.net
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
How well are the onboard IDE/floppy/ethernet of the Multia supported in
current at the moment?
--
GeoffB
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 02:55:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA23762
for freebsd-current-outgoing; Thu, 12 Nov 1998 02:55:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from marathon.tekla.fi (marathon.tekla.fi [192.98.7.5])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23754
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 02:55:22 -0800 (PST)
(envelope-from sja@tekla.fi)
Received: from poveri.tekla.fi (poveri.tekla.fi [192.98.7.19])
by marathon.tekla.fi (8.8.7/8.8.7) with SMTP id MAA15108
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 12:55:00 +0200
From: Sakari Jalovaara <sja@tekla.fi>
Received: by poveri.tekla.fi; (5.65v3.2/1.1.8.2/20Aug96-0557PM)
id AA29632; Thu, 12 Nov 1998 12:55:11 +0200
Date: Thu, 12 Nov 1998 12:55:11 +0200
Message-Id: <9811121055.AA29632@poveri.tekla.fi>
To: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Could someone who can reproduce the dying daemons problem try a little
> experiment: kill syslogd and then induce the out-of-memory condition.
> Do other daemons still start dying?
There is a sort of a point to this experiment, too :-)
The kernel printf() does stuff to wake up syslogd. What I was
wondering, is every place (such as the swapper) prepared for whatever
the wakeup does? Not having syslogd around should usually make the
wakeup a no-op.
++sja
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 02:58:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA23924
for freebsd-current-outgoing; Thu, 12 Nov 1998 02:58:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from tibatong.ihf.rwth-aachen.de (tibatong.ihf.RWTH-Aachen.DE [134.130.90.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23914
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 02:58:01 -0800 (PST)
(envelope-from tg@tibatong.ihf.rwth-aachen.de)
Received: (from tg@localhost)
by tibatong.ihf.rwth-aachen.de (8.8.8/8.8.8) id LAA00374;
Thu, 12 Nov 1998 11:57:00 +0100 (CET)
(envelope-from tg)
To: Mike Smith <mike@smith.net.au>
Cc: Peter Johnson <pljohnsn@uiuc.edu>, current@FreeBSD.ORG, x@suse.de
Subject: Re: XFree86 nonstandard server / ELF compat problem
References: <199811120648.WAA08374@dingo.cdrom.com>
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Thomas Gellekum <tg@ihf.rwth-aachen.de>
Date: 12 Nov 1998 11:57:00 +0100
In-Reply-To: Mike Smith's message of "Wed, 11 Nov 1998 22:48:41 -0800"
Message-ID: <87u305p4ar.fsf@tibatong.ihf.rwth-aachen.de>
Lines: 42
X-Mailer: Gnus v5.6.34/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Smith <mike@smith.net.au> writes:
> The symptoms you're seeing are typically indicative of an interrupt
> storm - the driver is enabling interrupts on the card but there is no
> handler for them.
>
> This is most likely a bug in the server.
[...]
> > Amazingly, the server actually starts up and seems to run ok (window
> > manager, xterm prompts start, etc), but I immediately am almost flooded by
> > kernel messages "calcru: negative time of -48128 usec for pid 342 (xterm)"
> > [with the time/pid/name changing]. Exiting the X server returns me to text
> > mode prompt, but I continue getting the calcru messages. If I try to run
> > top or do anything other than just list files, it seems, I get a nasty
> > message "cputime limit exceeded". End up not being able to shutdown
> > (because every process dies with a whole bunch of calcru messsages followed
> > immediately by a cputime message) and need to reset.
> >
> > Ugh.. now I _need_ XF86 3.3.3 so I can compile the whole darn thing as ELF!!
> >
> > (note: I'm using the SuSe ELSA GLORIA server for FreeBSD 2.1.5--tried to
> > use the Linux ELF binary, with no success)
> >
> > I got the same messages right after upgrading to ELF, so I
> > recompiled/reinstalled the XFree86 port (compiling as ELF).. didn't fix it
> > *sigh*
> >
> > Regards,
> > Peter Johnson
> > locke@mcs.net
[...]
Just a ``me too'', Cc'd to x@suse.de. I've gone back to
XFCom_3DLabs-4.1-FreeBSD and all is well again after a reboot. The
4.31 version does not behave on 2.2.7-stable either (same symptoms as
above) and should probably be removed from the ftp sites.
tg
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 06:29:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA11896
for freebsd-current-outgoing; Thu, 12 Nov 1998 06:29:51 -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 GAA11886
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 06:29:28 -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.1/8.9.1/Spinner) with ESMTP id WAA16462;
Thu, 12 Nov 1998 22:27:46 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811121427.WAA16462@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: alk@pobox.com
cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-reply-to: Your message of "Thu, 12 Nov 1998 02:39:52 CST."
<13898.40443.642502.918589@avalon.east>
Date: Thu, 12 Nov 1998 22:27:45 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Tony Kimball wrote:
> On Thu, 12 Nov 1998, Peter Wemm wrote:
> > Call be crazy, but I think I'd almost like to move the "real" kernel to
> > /boot/kernel, providing the search paths were ok.
>
> Now that would be a substantial improvement: No more files in /.
> This suggests that / could go away. I like it!
Don't joke too loudly.. :-) There are (or were) implementations of this
sort of thing kicking around a while ago.
> Further quoth Peter Wemm:
> : > And the bootblocks might be needed for emergency repair.
> ...
> : What is going to get put on this bootable
> : installation on the second disk if you can't mount /usr?
>
> FreeBSD. Remember /stand?
Yes, but if your original /usr is gone and preventing you from getting to
the bootblocks to build your new disk, you are going to have to source a
/usr from somewhere. Sure, use the /stand tools to do it (ftp enough
binaries to do a make world or whatever), but if you're going to do that
you can *also* get the bootblocks from the same source in order to make
the new disk self bootable.
Anyway, this has been overdone to death now. It looks like there's some
sort of agreement given that what is really being proposed is having a
file copy of the disk bootblocks in /boot (ie: boot0,1,2, a total of
8.5kb). This isn't quite the same thing as "moving the contents of /usr/
mdec into /boot" (ie: the 1.4MB cdboot, bootroms, fbsdboot.exe etc).
As long as "disklabel -B da0" etc still works without having to spell out
the boot1/boot2 pathnames (ie: as it worked before), I don't mind.
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 Nov 12 06:43:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA12878
for freebsd-current-outgoing; Thu, 12 Nov 1998 06:43:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12873
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 06:43:11 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id JAA04398;
Thu, 12 Nov 1998 09:45:50 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Thu, 12 Nov 1998 09:45:50 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Karl Denninger <karl@Denninger.Net>
cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <19981111210519.A6032@Denninger.Net>
Message-ID: <Pine.BSF.4.05.9811120944110.370-100000@porkfriedrice.ny.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 know i posted several times about problems with NFS (about a month ago)
> > but since McKusik's fixes I've yet to have a problem.
>
> Have these fixes been committed, and if so, when?
I'd say almost a month ago, it was really neat to see "mckusik" in the
cvsup log. :)
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 07:37:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA18776
for freebsd-current-outgoing; Thu, 12 Nov 1998 07:37:47 -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 HAA18768
for <current@freebsd.org>; Thu, 12 Nov 1998 07:37:45 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2])
by nlsystems.com (8.9.1/8.8.5) with SMTP id PAA12094;
Thu, 12 Nov 1998 15:37:10 GMT
Date: Thu, 12 Nov 1998 15:37:10 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: geoffb@demon.net
cc: current@FreeBSD.ORG
Subject: Re: DEC Multia support
In-Reply-To: <199811121007.KAA29247@gti.noc.demon.net>
Message-ID: <Pine.BSF.4.01.9811121535560.11371-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, 12 Nov 1998, Geoff Buckingham wrote:
>
> How well are the onboard IDE/floppy/ethernet of the Multia supported in
> current at the moment?
Ethernet should work. Floppy will work when I find time to port the
floppy driver over. IDE will probably have to wait until the new atapi
code is ready.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 951 1891
Fax: +44 181 381 1039
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 08:14:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA23604
for freebsd-current-outgoing; Thu, 12 Nov 1998 08:14:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.intercom.com ([207.51.55.117])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23599
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 08:14:25 -0800 (PST)
(envelope-from jason@intercom.com)
Received: from intercom.com (shagalicious.com [206.98.165.250])
by mail.intercom.com (8.9.0/8.9.0) with ESMTP id LAA10533
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 11:14:04 -0500 (EST)
Message-ID: <364B08C3.27FE59A4@intercom.com>
Date: Thu, 12 Nov 1998 11:11:47 -0500
From: "Jason J. Horton" <jason@intercom.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
References: <Pine.BSF.4.05.9811112154240.370-100000@porkfriedrice.ny.genx.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Everyone seems to be talking about using FreeBSD as an NFS client,
how does FreeBSD do as a NFS server?
-J
Alfred Perlstein wrote:
> On Wed, 11 Nov 1998, Brian Feldman wrote:
>
> > > > When we "catch up" to Linux, for every advance, we always have a
> > > > better-implemented version of whatever new has been gotten on Linux. Maybe
> > > > except for NFS.... but that's being working on, eh?
> > >
> > > I hope you are refering to Linux NFS being far inferior to FreeBSD's
> > > impelementation. If you are not then where do we fall behind? I haven't
> > > seen Linux outperform FreeBSD in any NFS work i've done.
> >
> > Last I had heard, NFS was still too unstable to be used heavily in
> > FreeBSD, but "worked" in Linux. But, who knows for sure? I don't run any
> > Linux systems, and I don't really use NFS in FreeBSD.
>
> Then perhaps you should stay quiet on the issue.
>
> FreeBSD has outperformed linux by several orders of magnitude in client
> side NFS for a long time. The newer linux development kernels come close,
> but when concurrent NFS requests are made Linux chokes while FreeBSD
> maintains a broadband'ish state.
>
> I know i posted several times about problems with NFS (about a month ago)
> but since McKusik's fixes I've yet to have a problem.
>
> In so far as serving NFS... the Linux userland NFS server is hardly a
> match to the FreeBSD kernel impelementation. Stability is another matter
> and I haven't seen enough to say anything conclusive for either side.
> Both implementations suffer from lack of support for files > 2gb in
> client side requests which should be addressed, somehow/somewhen.
>
> A recent Linux article suggests that Linux NFS will bipass the "mbuf"
> layer, ie. the NFS code will directly reassemble packets into RPC requests
> thereby saving _one_ copy of memory. This is really neat, but then makes
> NFS dependant on the protocols which it is supposed to be independant of.
>
> Btw, Mike Smith's new ACCESS caching seems quite stable and i was
> wondering if it had been commited.
>
> -Alfred
>
> 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 Nov 12 08:22:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA24464
for freebsd-current-outgoing; Thu, 12 Nov 1998 08:22:32 -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 IAA24459
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 08:22:30 -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 RAA22534;
Thu, 12 Nov 1998 17:22:04 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id RAA04201;
Thu, 12 Nov 1998 17:22:03 +0100 (MET)
Message-ID: <19981112172202.43911@follo.net>
Date: Thu, 12 Nov 1998 17:22:02 +0100
From: Eivind Eklund <eivind@yes.no>
To: "Justin M. Seger" <jseger@freebsd.scds.com>, current@FreeBSD.ORG
Subject: Re: Problems building in a chroot'ed environment
References: <199811111644.LAA27758@freebsd.scds.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <199811111644.LAA27758@freebsd.scds.com>; from Justin M. Seger on Wed, Nov 11, 1998 at 11:44:06AM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Nov 11, 1998 at 11:44:06AM -0500, Justin M. Seger wrote:
> Hi guys. I've been having this problem doing a make world in a
> chroot'ed environment for about a week now. The real world is
> up-to-date and the /usr/src in the chroot'ed environment is also
> up-to-date.
>
[... compile including core dump removed ...]
>
> If anyone has any ideas, please send them my way ASAP. I need to get
> this working to do a new packages-current run.
Examine the core dump. I think you're the only person that have
enough information to fix this at this point. :-(
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 08:25:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA24813
for freebsd-current-outgoing; Thu, 12 Nov 1998 08:25:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24807
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 08:25:42 -0800 (PST)
(envelope-from psalzman@gamefish.pcola.gulf.net)
Received: from localhost (psalzman@localhost)
by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id QAA04079;
Thu, 12 Nov 1998 16:25:15 GMT
(envelope-from psalzman@gamefish.pcola.gulf.net)
Date: Thu, 12 Nov 1998 16:25:14 +0000 (GMT)
From: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
To: "Jason J. Horton" <jason@intercom.com>
cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <364B08C3.27FE59A4@intercom.com>
Message-ID: <Pine.BSF.4.05.9811121622550.4025-100000@gamefish.pcola.gulf.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Check out:
http://www.spatula.net/proc/linux|142401dc8b9c927d821519d547d9a0fa8200/linux.lame.nfs.src
which was written by Alfred Perlstein
--
Phillip Salzman
On Thu, 12 Nov 1998, Jason J. Horton wrote:
> Everyone seems to be talking about using FreeBSD as an NFS client,
> how does FreeBSD do as a NFS server?
>
> -J
>
> Alfred Perlstein wrote:
>
> > On Wed, 11 Nov 1998, Brian Feldman wrote:
> >
> > > > > When we "catch up" to Linux, for every advance, we always have a
> > > > > better-implemented version of whatever new has been gotten on Linux. Maybe
> > > > > except for NFS.... but that's being working on, eh?
> > > >
> > > > I hope you are refering to Linux NFS being far inferior to FreeBSD's
> > > > impelementation. If you are not then where do we fall behind? I haven't
> > > > seen Linux outperform FreeBSD in any NFS work i've done.
> > >
> > > Last I had heard, NFS was still too unstable to be used heavily in
> > > FreeBSD, but "worked" in Linux. But, who knows for sure? I don't run any
> > > Linux systems, and I don't really use NFS in FreeBSD.
> >
> > Then perhaps you should stay quiet on the issue.
> >
> > FreeBSD has outperformed linux by several orders of magnitude in client
> > side NFS for a long time. The newer linux development kernels come close,
> > but when concurrent NFS requests are made Linux chokes while FreeBSD
> > maintains a broadband'ish state.
> >
> > I know i posted several times about problems with NFS (about a month ago)
> > but since McKusik's fixes I've yet to have a problem.
> >
> > In so far as serving NFS... the Linux userland NFS server is hardly a
> > match to the FreeBSD kernel impelementation. Stability is another matter
> > and I haven't seen enough to say anything conclusive for either side.
> > Both implementations suffer from lack of support for files > 2gb in
> > client side requests which should be addressed, somehow/somewhen.
> >
> > A recent Linux article suggests that Linux NFS will bipass the "mbuf"
> > layer, ie. the NFS code will directly reassemble packets into RPC requests
> > thereby saving _one_ copy of memory. This is really neat, but then makes
> > NFS dependant on the protocols which it is supposed to be independant of.
> >
> > Btw, Mike Smith's new ACCESS caching seems quite stable and i was
> > wondering if it had been commited.
> >
> > -Alfred
> >
> > 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
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 08:47:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA26634
for freebsd-current-outgoing; Thu, 12 Nov 1998 08:47:06 -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 IAA26624
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 08:47:05 -0800 (PST)
(envelope-from ambrisko@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id IAA21890
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 08:46:04 -0800 (PST)
Received: from crab.whistle.com(207.76.205.112), claiming to be "whistle.com"
via SMTP by alpo.whistle.com, id smtpdn21871; Thu Nov 12 16:45:53 1998
Received: (from ambrisko@localhost)
by whistle.com (8.9.1/8.9.1) id IAA11177
for current@FreeBSD.ORG; Thu, 12 Nov 1998 08:45:51 -0800 (PST)
(envelope-from ambrisko)
From: Doug Ambrisko <ambrisko@whistle.com>
Message-Id: <199811121645.IAA11177@whistle.com>
Subject: Re: Is it soup yet? :-)
In-Reply-To: <xzpd86tvepa.fsf@grjottunagard.ifi.uio.no> from =?ISO-8859-1?Q?Dag=2DErling_C=2E_Sm=F8rgrav?= at "Nov 12, 98 03:15:45 am"
To: current@FreeBSD.ORG
Date: Thu, 12 Nov 1998 08:45:50 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL29 (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
Dag-Erling C. Smørgrav writes:
| Julian Elischer <julian@whistle.com> writes:
| > These are "embedded" FreeBSD machines.
| > they are all over the world.
| > We are certainly not in the position of bringing each back to the factory!
|
| Do they work?
|
| If they do, why upgrade them?
Customer's sometimes pay for new better features. This is usually
encouraged :-)
Doug A.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 08:47:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA26713
for freebsd-current-outgoing; Thu, 12 Nov 1998 08:47:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from srv1inet.tba.com.br (srv1inet.tba.com.br [200.202.37.2])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA26232
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 08:45:09 -0800 (PST)
(envelope-from mailleux@tba.com.br)
Received: from cipea.ipea.gov.br (cipea.ipea.gov.br [200.130.48.11]) by srv1inet.tba.com.br (NTMail 3.02.13) with ESMTP id za007435 for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 14:35:02 -0300
X-Sender: mailleux@mail.tba.com.br
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Thu, 12 Nov 1998 14:34:08 -0200
To: current@FreeBSD.ORG
From: "Thomas Mailleux Sant'ana" <mailleux@tba.com.br>
In-Reply-To: <199811120254.SAA11392@hub.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <17350264010002@tba.com.br>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
unsubscribe freebsd-current
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 09:37:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA01066
for freebsd-current-outgoing; Thu, 12 Nov 1998 09:37:32 -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 JAA01061;
Thu, 12 Nov 1998 09:37:30 -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 SAA31700;
Thu, 12 Nov 1998 18:37:36 +0100
From: Marco van Hylckama Vlieg <fatal@pc2-c804.uibk.ac.at>
Message-Id: <199811121737.SAA31700@pc2-c804.uibk.ac.at>
Subject: Re: Upgrade from 2.2-STABLE to -CURRENT
To: dwhite@resnet.uoregon.edu (Doug White)
Date: Thu, 12 Nov 1998 18:37:35 +0100 (MET)
Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
In-Reply-To: <Pine.BSF.4.03.9811111653530.16040-100000@resnet.uoregon.edu> from "Doug White" at Nov 11, 98 04:58:19 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
>
> On Wed, 11 Nov 1998, Florian Nigsch wrote:
>
> > cp strip maybe_stripped
> > strip maybe_stripped
> > *** Error code 1
> > ...and five more "*** Error code 1".
>
> Hm, it's running the wrong strip(1), I'm guessing. Revision 1.9 of
> strip's Makefile claims to fix this bug.
>
So what do I do to get it going?
I'm experiencing the exact same thing.
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://global.uibk.ac.at/~fatal/wmaker/
. ]QQQQQQQ@
L )WQQQQQQ( Marco van Hylckama Vlieg
!`_ajQQQQQ@( fatal@global.uibk.ac.at (NeXTmail OK)
"?TUVY"` ------------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 09:39:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA01155
for freebsd-current-outgoing; Thu, 12 Nov 1998 09:39:16 -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 JAA01142
for <current@freebsd.org>; Thu, 12 Nov 1998 09:39:02 -0800 (PST)
(envelope-from geoffb@gti.noc.demon.net)
Received: by server.noc.demon.net; id RAA11295; Thu, 12 Nov 1998 17:38:38 GMT
Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2)
id xma011277; Thu, 12 Nov 98 17:38:30 GMT
Received: (from geoffb@localhost)
by gti.noc.demon.net (8.8.8/8.8.8) id RAA04974;
Thu, 12 Nov 1998 17:38:28 GMT
From: Geoff Buckingham <geoffb@gti.noc.demon.net>
Message-Id: <199811121738.RAA04974@gti.noc.demon.net>
Subject: Re: DEC Multia support
In-Reply-To: <Pine.BSF.4.01.9811121535560.11371-100000@herring.nlsystems.com> from Doug Rabson at "Nov 12, 98 03:37:10 pm"
To: dfr@nlsystems.com (Doug Rabson)
Date: Thu, 12 Nov 1998 17:38:28 +0000 (GMT)
Cc: current@FreeBSD.ORG
Reply-To: geoffb@demon.net
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
> On Thu, 12 Nov 1998, Geoff Buckingham wrote:
>
> >
> > How well are the onboard IDE/floppy/ethernet of the Multia supported in
> > current at the moment?
>
> Ethernet should work. Floppy will work when I find time to port the
> floppy driver over. IDE will probably have to wait until the new atapi
> code is ready.
>
Given the above is my best route to installing FreeBSD to start with
NetBSD and migrate?
--
GeoffB
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 09:42:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA01403
for freebsd-current-outgoing; Thu, 12 Nov 1998 09:42:24 -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 JAA01394
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 09:42:21 -0800 (PST)
(envelope-from lists@tar.com)
Received: from ppro.tar.com (ppro.tar.com [204.95.187.9])
by ns.tar.com (8.9.1/8.8.7) with SMTP id LAA14562;
Thu, 12 Nov 1998 11:41:40 -0600 (CST)
Message-Id: <199811121741.LAA14562@ns.tar.com>
From: "Richard Seaman, Jr." <lists@tar.com>
To: "Brian Feldman" <green@unixhelp.org>
Cc: "current@freebsd.org" <current@FreeBSD.ORG>
Date: Thu, 12 Nov 98 11:41:39 -0600
Reply-To: "Richard Seaman, Jr." <lists@tar.com>
X-Mailer: PMMail 1.92 For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: RFSIGSHARE ready?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian --
I've done some more thinking about making linux threads work in
linux emulation. Here are some thoughts:
1) I think you need to take p_sigmask out of your new procsig
structure and put it back into the proc structure. Linux threads
does lots of signal mask manipulation, and I'm pretty sure that
it expects p_sigmask to be "per thread", and not shared among
all the threads.
2) linux threads creates stacks for each thread it creates via
mmap. It decides on where to start allocating them using the
following algorithm (I think).
It gets the stack pointer of the initial thread,
figures the initial thread can get by with 2*STACK_SIZE
bytes (4MB in this case), and then starts allocating
thread user stacks 2*STACK_SIZE below the initial
thread stack.
I don't pretend to really understand FreeBSD vm, to the following
is just a guess on my part. Maybe someone else can shed more
light on this.
The problem is that FreeBSD dedicates 64MB for a process stack
(ie. for the initial thread), so that linux threads starts out
mmaping into the initial thread stack region. I don't know
exactly what happens at that point, but it doesn't seem to
be good.
I'm not sure why FreeBSD mmap allows a mmap into the process
user stack to succeed (but it appears to).
You could consider patching either linux_mmap or the FreeBSD
mmap to reject attempts to mmap at virtual addresses above
p->p->vmspace->vm_maxaddr. I haven't tried this, so I don't
know if it will work.
What this would do to an unmodified linux threads implementation
would be (I think) that the first 31 or 32 stack addresses it
tries to create would fail since they are trying to map into
the initial thread stack. But, after that, mmaps should succeed
and maybe the addresses will be ok. You'd loose the ability to
create 31 or 32 threads out of the total 1024 that linux threads
allows, but that wouldn't be the end of the world.
3) You need to deal with the fact that linux threads mmaps the
thread stacks with the MAP_GROWSDOWN option. Your choices would
appear to be to re-write the FreeBSD mmap syscall to implement
this feature, or to hack linux_mmap. A hack to linux_mmap that
might work (but its a bad hack) would be that when linux_mmap
detects the MAP_GROWSDOWN option it would expand the size
of the mmap request by STACK_SIZE - INITIAL_STACKSIZE, and
relocate the address requested down by the same amount.
I haven't tried any of these ideas, so I have no clue if they
will work.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 10:54:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA08370
for freebsd-current-outgoing; Thu, 12 Nov 1998 10:54:35 -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 KAA08347
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 10:54:14 -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 SAA04349;
Thu, 12 Nov 1998 18:52:17 GMT
Date: Thu, 12 Nov 1998 18:52:17 GMT
Message-Id: <199811121852.SAA04349@cogsci.ed.ac.uk>
From: Richard Tobin <richard@cogsci.ed.ac.uk>
Subject: Re: Is it soup yet? :-)
To: mjacob@feral.com, Dan Strick <dan@math.berkeley.edu>
In-Reply-To: Matthew Jacob's message of Wed, 11 Nov 1998 13:51:29 -0800 (PST)
Organization: just say no
Cc: sthaug@nethelp.no, current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> m in mdec was short for 'machine' IIRC. It wasn't in /usr originally I
> believe.
It was /usr/mdec in third edition, 1973.
-- Richard
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 10:57:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA08663
for freebsd-current-outgoing; Thu, 12 Nov 1998 10:57:05 -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 KAA08652
for <current@freebsd.org>; Thu, 12 Nov 1998 10:57:00 -0800 (PST)
(envelope-from info@highwind.com)
Received: (from info@localhost)
by highwind.com (8.8.6/8.8.6) id NAA23101;
Thu, 12 Nov 1998 13:56:41 -0500 (EST)
Date: Thu, 12 Nov 1998 13:56:41 -0500 (EST)
Message-Id: <199811121856.NAA23101@highwind.com>
From: HighWind Software Information <info@highwind.com>
To: current@FreeBSD.ORG
Subject: aio_write() doesn't work!
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Is is me or does "aio_write()" under FreeBSD 3.0 simply NOT work?
This prints all x's. Considering I used aio_write() to write a 'y' in
there, why doesn't it work??
-Rob
---
/*****************************************************************************
File: aioTest.c
Contents: Simple Test of the aio_write() function
gcc -o aioTest aioTest.c -Wall -Werror
*****************************************************************************/
#include <assert.h>
#include <fcntl.h>
#include <memory.h>
#include <time.h>
#include <sys/aio.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
int main(int argc, char **argv)
{
int fd;
char before[10], after[11], y;
struct aiocb token;
const struct aiocb *tlist;
/* Open the test file */
fd = open("test", O_RDWR | O_CREAT | O_TRUNC, 0666);
assert(fd != -1);
/* Write 10 x's */
memset(before, 'x', 10);
assert(write(fd, &before, 10) == 10);
/* Use aio_write() to write a 'Y' at offset 5 */
y = 'Y';
memset(&token, 0, sizeof(struct aiocb));
token.aio_fildes = fd;
token.aio_offset = 5;
token.aio_buf = &y;
token.aio_nbytes = 1;
token.aio_sigevent.sigev_notify = SIGEV_NONE;
/* Enqueue the write */
assert(aio_write(&token) == 0);
/* Wait for completion */
tlist = &token;
assert(aio_suspend(&tlist, 1, 0) == 0);
/* Ensure the write worked! */
assert(aio_return(&token) == 1);
/* Read back the whole file */
memset(after, 0, 11);
assert(lseek(fd, 0, SEEK_SET) == 0);
assert(read(fd, &after, 10) == 10);
printf("%s\n", after);
return EXIT_SUCCESS;
}
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 11:11:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA09755
for freebsd-current-outgoing; Thu, 12 Nov 1998 11:11:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alive.znep.com (207-178-54-226.go2net.com [207.178.54.226])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09750
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 11:11:43 -0800 (PST)
(envelope-from marcs@znep.com)
Received: from localhost (marcs@localhost)
by alive.znep.com (8.9.1/8.9.1) with ESMTP id LAA22879;
Thu, 12 Nov 1998 11:06:47 -0800 (PST)
(envelope-from marcs@znep.com)
Date: Thu, 12 Nov 1998 11:06:47 -0800 (PST)
From: Marc Slemko <marcs@znep.com>
To: HighWind Software Information <info@highwind.com>
cc: current@FreeBSD.ORG
Subject: Re: aio_write() doesn't work!
In-Reply-To: <199811121856.NAA23101@highwind.com>
Message-ID: <Pine.BSF.4.05.9811121106050.12077-100000@alive.znep.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, 12 Nov 1998, HighWind Software Information wrote:
>
> Is is me or does "aio_write()" under FreeBSD 3.0 simply NOT work?
>
> This prints all x's. Considering I used aio_write() to write a 'y' in
> there, why doesn't it work??
It works, it is just the aio_offset is being ignored. Shouldn't be
too hard to fix.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 11:18:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA10598
for freebsd-current-outgoing; Thu, 12 Nov 1998 11:18:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10584
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 11:18:05 -0800 (PST)
(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
by lor.watermarkgroup.com (8.8.8/8.8.8) id OAA24040;
Thu, 12 Nov 1998 14:17:43 -0500 (EST)
(envelope-from luoqi)
Date: Thu, 12 Nov 1998 14:17:43 -0500 (EST)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <199811121917.OAA24040@lor.watermarkgroup.com>
To: green@unixhelp.org, lists@tar.com
Subject: Re: RFSIGSHARE ready?
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> 2) linux threads creates stacks for each thread it creates via
> mmap. It decides on where to start allocating them using the
> following algorithm (I think).
>
> It gets the stack pointer of the initial thread,
> figures the initial thread can get by with 2*STACK_SIZE
> bytes (4MB in this case), and then starts allocating
> thread user stacks 2*STACK_SIZE below the initial
> thread stack.
>
> I don't pretend to really understand FreeBSD vm, to the following
> is just a guess on my part. Maybe someone else can shed more
> light on this.
>
> The problem is that FreeBSD dedicates 64MB for a process stack
> (ie. for the initial thread), so that linux threads starts out
> mmaping into the initial thread stack region. I don't know
> exactly what happens at that point, but it doesn't seem to
> be good.
>
I don't see anything bad, if the initial thread doesn't use more than
2*STACK_SIZE.
> I'm not sure why FreeBSD mmap allows a mmap into the process
> user stack to succeed (but it appears to).
>
Why not? The only difference user stack from other user memory is
the kernel imposes an autogrow policy.
> You could consider patching either linux_mmap or the FreeBSD
> mmap to reject attempts to mmap at virtual addresses above
> p->p->vmspace->vm_maxaddr. I haven't tried this, so I don't
> know if it will work.
>
> What this would do to an unmodified linux threads implementation
> would be (I think) that the first 31 or 32 stack addresses it
> tries to create would fail since they are trying to map into
> the initial thread stack. But, after that, mmaps should succeed
> and maybe the addresses will be ok. You'd loose the ability to
> create 31 or 32 threads out of the total 1024 that linux threads
> allows, but that wouldn't be the end of the world.
>
The first 31 threads are fine, in fact, they will enjoy the benefit
of the autogrow policy on the user stack.
> 3) You need to deal with the fact that linux threads mmaps the
> thread stacks with the MAP_GROWSDOWN option. Your choices would
> appear to be to re-write the FreeBSD mmap syscall to implement
> this feature, or to hack linux_mmap. A hack to linux_mmap that
> might work (but its a bad hack) would be that when linux_mmap
> detects the MAP_GROWSDOWN option it would expand the size
> of the mmap request by STACK_SIZE - INITIAL_STACKSIZE, and
> relocate the address requested down by the same amount.
>
This is good enough, it's just a little more VM overcommit.
A MAP_GROWSDOWN option without specifying how far it can grow
is IMHO a bad idea.
> I haven't tried any of these ideas, so I have no clue if they
> will work.
>
-lq
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 11:22:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA11076
for freebsd-current-outgoing; Thu, 12 Nov 1998 11:22:40 -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 LAA11056
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 11:22:15 -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 TAA04867;
Thu, 12 Nov 1998 19:10:20 GMT
Date: Thu, 12 Nov 1998 19:10:20 GMT
Message-Id: <199811121910.TAA04867@cogsci.ed.ac.uk>
From: Richard Tobin <richard@cogsci.ed.ac.uk>
Subject: Re: Is it soup yet? :-)
To: Richard Tobin <richard@cogsci.ed.ac.uk>, mjacob@feral.com,
Dan Strick <dan@math.berkeley.edu>
In-Reply-To: Richard Tobin's message of Thu, 12 Nov 1998 18:52:17 GMT
Organization: just say no
Cc: sthaug@nethelp.no, current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> It was /usr/mdec in third edition, 1973.
Sorry, I should have said:
It was /usr/mdec in sixth edition (1975); the mkfs man page which refers
to it is dated 11/1/73.
It was /sys/mdec in third edition; the 20boot man page which refers to
it is dated 1/25/73.
So it looks like it's been /usr/mdec for 25 years.
-- Richard
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 11:28:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA11636
for freebsd-current-outgoing; Thu, 12 Nov 1998 11:28:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from yonge.cs.toronto.edu (yonge.cs.toronto.edu [128.100.1.8])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA11631
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 11:28:49 -0800 (PST)
(envelope-from dholland@cs.toronto.edu)
Received: from qew.cs.toronto.edu ([128.100.2.15]) by yonge.cs.toronto.edu with SMTP id <86508-8537>; Thu, 12 Nov 1998 14:28:16 -0500
Received: by qew.cs.toronto.edu id <37768-2936>; Thu, 12 Nov 1998 14:28:01 -0500
Subject: Re: Is it soup yet? FreeBSD NFS
From: David Holland <dholland@cs.toronto.edu>
To: psalzman@gamefish.pcola.gulf.net (Phillip Salzman)
Date: Thu, 12 Nov 1998 14:27:50 -0500
Cc: jason@intercom.com, current@FreeBSD.ORG
In-Reply-To: <Pine.BSF.4.05.9811121622550.4025-100000@gamefish.pcola.gulf.net> from "Phillip Salzman" at Nov 12, 98 11:25:14 am
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <98Nov12.142801edt.37768-2936@qew.cs.toronto.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Check out:
>
> http://www.spatula.net/proc/linux|142401dc8b9c927d821519d547d9a0fa8200/linux.lame.nfs.src
>
This URL does not work, but suggests a slightly varying version, which
returns
"Fat chance, jerk."
I take it this isn't what you meant...
--
- David A. Holland | (please continue to send non-list mail to
dholland@cs.utoronto.ca | dholland@hcs.harvard.edu. yes, I moved.)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 11:34:25 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA12104
for freebsd-current-outgoing; Thu, 12 Nov 1998 11:34:25 -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 LAA12095;
Thu, 12 Nov 1998 11:34:18 -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 LAA20079;
Thu, 12 Nov 1998 11:33:40 -0800 (PST)
(envelope-from dwhite@resnet.uoregon.edu)
Date: Thu, 12 Nov 1998 11:33:39 -0800 (PST)
From: Doug White <dwhite@resnet.uoregon.edu>
To: Marco van Hylckama Vlieg <fatal@pc2-c804.uibk.ac.at>
cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: Re: Upgrade from 2.2-STABLE to -CURRENT
In-Reply-To: <199811121737.SAA31700@pc2-c804.uibk.ac.at>
Message-ID: <Pine.BSF.4.03.9811121133220.8018-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 Thu, 12 Nov 1998, Marco van Hylckama Vlieg wrote:
> >
> > On Wed, 11 Nov 1998, Florian Nigsch wrote:
> >
> > > cp strip maybe_stripped
> > > strip maybe_stripped
> > > *** Error code 1
> > > ...and five more "*** Error code 1".
> >
> > Hm, it's running the wrong strip(1), I'm guessing. Revision 1.9 of
> > strip's Makefile claims to fix this bug.
> >
> So what do I do to get it going?
> I'm experiencing the exact same thing.
When was the last time you CVSupped?
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 Nov 12 11:36:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA12269
for freebsd-current-outgoing; Thu, 12 Nov 1998 11:36:16 -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 LAA12262
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 11:36:14 -0800 (PST)
(envelope-from info@highwind.com)
Received: (from info@localhost)
by highwind.com (8.8.6/8.8.6) id OAA23382;
Thu, 12 Nov 1998 14:35:23 -0500 (EST)
Date: Thu, 12 Nov 1998 14:35:23 -0500 (EST)
Message-Id: <199811121935.OAA23382@highwind.com>
From: HighWind Software Information <info@highwind.com>
To: marcs@znep.com
CC: current@FreeBSD.ORG
In-reply-to: <Pine.BSF.4.05.9811121106050.12077-100000@alive.znep.com>
(message from Marc Slemko on Thu, 12 Nov 1998 11:06:47 -0800 (PST))
Subject: Re: aio_write() doesn't work!
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> It works, it is just the aio_offset is being ignored. Shouldn't be
> too hard to fix.
Well.. That is the whole reason we are going to use it. We need a way
to do thread-safe offset read's and write's.
FreeBSD 3.0 doesn't have pread()/pwrite() yet. And it seems that most
I/O isn't counted toward a thread's time slice. Our hope is that by
doing async I/O's we can get around that problem.
Unfortunately, it appears that the system call doesn't work.
Where does that code live?
I guess I'll open a bug report.
-Rob
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 11:40:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA12710
for freebsd-current-outgoing; Thu, 12 Nov 1998 11:40:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA12702
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 11:40:11 -0800 (PST)
(envelope-from jrs@enteract.com)
Received: (qmail 8124 invoked from network); 12 Nov 1998 19:39:51 -0000
Received: from adam.enteract.com (jrs@206.54.252.1)
by thor.enteract.com with SMTP; 12 Nov 1998 19:39:51 -0000
Date: Thu, 12 Nov 1998 13:39:51 -0600 (CST)
From: John Sconiers <jrs@enteract.com>
To: David Holland <dholland@cs.toronto.edu>
cc: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>, jason@intercom.com,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <98Nov12.142801edt.37768-2936@qew.cs.toronto.edu>
Message-ID: <Pine.BSF.3.96.981112133849.29291B-100000@adam.enteract.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Check out:
> > http://www.spatula.net/proc/linux|142401dc8b9c927d821519d547d9a0fa8200/linux.lame.nfs.src
> This URL does not work, but suggests a slightly varying version, which
> returns
> I take it this isn't what you meant...
go to http://www.spatula.net
you'll fimnd it.
JOHN
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 11:44:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA13203
for freebsd-current-outgoing; Thu, 12 Nov 1998 11:44:22 -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 LAA13196
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 11:44:21 -0800 (PST)
(envelope-from dhw@whistle.com)
Received: (from dhw@localhost)
by pau-amma.whistle.com (8.8.8/8.8.7) id LAA28198
for current@FreeBSD.ORG; Thu, 12 Nov 1998 11:42:00 -0800 (PST)
(envelope-from dhw)
Date: Thu, 12 Nov 1998 11:42:00 -0800 (PST)
From: David Wolfskill <dhw@whistle.com>
Message-Id: <199811121942.LAA28198@pau-amma.whistle.com>
To: current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
In-Reply-To: <199811120236.SAA06936@dingo.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>Date: Wed, 11 Nov 1998 18:36:09 -0800
>From: Mike Smith <mike@smith.net.au>
>> When talkign with friends that use Linux, and talking about our
>> /proc file system, they think its hilarious that I can't go into proc and
>> find out what irqs are being used by the system...maybe I'm missing
>> something, but about the only way I can do it currently is to look through
>> dmesg output? Is there another way?
>I have to ask - why do you care? I can think of much better things to
>do with my time than stare at the list of IRQ's in use - what do they
>expect them to do? A little song and dance number perhaps?
Well, one example of something I would like to be able to do is to have
an automatic procedure (say, a script) that I could run on a box and get
enough information that I could squirrel away (off-site, for example) so
that, given the list and enough money, I could specify what parts to buy
so the machine could be re-created (and so that once the off-site
backups were restored, I'd have a fairly good approximation to the
original machine).
Even better: I'd like for a person who is not necessarily a FreeBSD
wizard be able to read the list, specify the parts, and assemble them
into a working whole.
>(If you need the information, try 'systat -vmstat'.)
That may well be useful for many purposes. It's not at all obvious that
it's useful for what I'm trying to do. So far, looking at
/var/run/dmesg.boot comes closest that I've been able to find, but
there's very little there about the video card(s?), for example.
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 Nov 12 11:48:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA13558
for freebsd-current-outgoing; Thu, 12 Nov 1998 11:48:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from yonge.cs.toronto.edu (yonge.cs.toronto.edu [128.100.1.8])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA13553
for <current@freebsd.org>; Thu, 12 Nov 1998 11:48:32 -0800 (PST)
(envelope-from dholland@cs.toronto.edu)
Received: from qew.cs.toronto.edu ([128.100.2.15]) by yonge.cs.toronto.edu with SMTP id <86508-8537>; Thu, 12 Nov 1998 14:48:04 -0500
Received: by qew.cs.toronto.edu id <37768-2936>; Thu, 12 Nov 1998 14:48:01 -0500
Subject: Re: Is it soup yet? FreeBSD NFS
From: David Holland <dholland@cs.toronto.edu>
To: jrs@enteract.com (John Sconiers)
Date: Thu, 12 Nov 1998 14:47:59 -0500
Cc: current@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.96.981112133849.29291B-100000@adam.enteract.com> from "John Sconiers" at Nov 12, 98 02:39:51 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <98Nov12.144801edt.37768-2936@qew.cs.toronto.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > > Check out:
> > > http://www.spatula.net/proc/linux|142401dc8b9c927d821519d547d9a0fa8200/linux.lame.nfs.src
> > This URL does not work, but suggests a slightly varying version, which
> > returns
> > I take it this isn't what you meant...
>
> go to http://www.spatula.net
> you'll fimnd it.
All I see there are some anti-linux polemics; nothing having to do
with freebsd nfs-serving.
(If you wish to discuss anti-linux polemics, please don't do it on the
list.)
--
- David A. Holland | (please continue to send non-list mail to
dholland@cs.utoronto.ca | dholland@hcs.harvard.edu. yes, I moved.)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 11:58:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA14395
for freebsd-current-outgoing; Thu, 12 Nov 1998 11:58:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA14390
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 11:58:39 -0800 (PST)
(envelope-from jrs@enteract.com)
Received: (qmail 10394 invoked from network); 12 Nov 1998 19:58:19 -0000
Received: from adam.enteract.com (jrs@206.54.252.1)
by thor.enteract.com with SMTP; 12 Nov 1998 19:58:19 -0000
Date: Thu, 12 Nov 1998 13:58:19 -0600 (CST)
From: John Sconiers <jrs@enteract.com>
To: David Holland <dholland@cs.toronto.edu>
cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <98Nov12.144801edt.37768-2936@qew.cs.toronto.edu>
Message-ID: <Pine.BSF.3.96.981112135536.23365A-100000@adam.enteract.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > > > Check out:
> > > > http://www.spatula.net/proc/linux|142401dc8b9c927d821519d547d9a0fa8200/linux.lame.nfs.src
> > > This URL does not work, but suggests a slightly varying version, which
> > > returns
> > > I take it this isn't what you meant...
> > go to http://www.spatula.net
> > you'll fimnd it.
> All I see there are some anti-linux polemics; nothing having to do
> with freebsd nfs-serving.
> (If you wish to discuss anti-linux polemics, please don't do it on the
> list.)
I believe we know what this list is for .... and the topic was .......
The part he refered you to was...
.....................snip........
From: Alfred Perlstein
time dd if=www2_otherlocal.tar.gz of=/dev/null bs=128k
219+1 records in
219+1 records out
28760021 bytes transferred in 3.411756 secs (8429683 bytes/sec)
0.000u 0.443s 0:03.42 12.8% 91+667k 0+17io 0pf+0w
(that's freebsd)
time dd if=www2_otherlocal.tar.gz of=/dev/null bs=128k
219+1 records in
219+1 records out
0.010u 1.550s 0:16.00 9.7% 0+0k 0+0io 84pf+0w
(linsux) [Redhat 5.1]
this is on the same 100mbit segment.
i'm using NFS over TCP and linux is using UDP
both to the same Solaris 5.6 box.
also, note how much linux dd sucks ass.
(still smirking)
Alfred Perlstein
............................snip................................
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 12:03:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA14887
for freebsd-current-outgoing; Thu, 12 Nov 1998 12:03:01 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from feral-gw.feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14879
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 12:02:58 -0800 (PST)
(envelope-from mjacob@feral.com)
Received: from localhost (mjacob@localhost)
by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id MAA26003;
Thu, 12 Nov 1998 12:01:21 -0800
Date: Thu, 12 Nov 1998 12:01:21 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
X-Sender: mjacob@feral-gw
Reply-To: mjacob@feral.com
To: John Sconiers <jrs@enteract.com>
cc: David Holland <dholland@cs.toronto.edu>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <Pine.BSF.3.96.981112135536.23365A-100000@adam.enteract.com>
Message-ID: <Pine.LNX.4.02.9811121158530.25310-100000@feral-gw>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
It may be useful and exhilarating to 'dis' other systems, but it's
pointless. Rather than spending time knocking down the other system, you
should spend time addressing the problems in the system you like. Anything
else just encourages the adherents of other systems to make you look like
an idiot (which I guarantee that they will, one way or the other).
-matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 12:03:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA14923
for freebsd-current-outgoing; Thu, 12 Nov 1998 12:03:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14907
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 12:03:17 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id PAA23095;
Thu, 12 Nov 1998 15:05:50 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Thu, 12 Nov 1998 15:05:49 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: David Holland <dholland@cs.toronto.edu>
cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <98Nov12.144801edt.37768-2936@qew.cs.toronto.edu>
Message-ID: <Pine.BSF.4.05.9811121500140.4484-100000@porkfriedrice.ny.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, 12 Nov 1998, David Holland wrote:
> > > > Check out:
> > > > http://www.spatula.net/proc/linux|142401dc8b9c927d821519d547d9a0fa8200/linux.lame.nfs.src
> > > This URL does not work, but suggests a slightly varying version, which
> > > returns
> > > I take it this isn't what you meant...
> >
> > go to http://www.spatula.net
> > you'll fimnd it.
>
> All I see there are some anti-linux polemics; nothing having to do
> with freebsd nfs-serving.
>
> (If you wish to discuss anti-linux polemics, please don't do it on the
> list.)
I'm not particularly proud of this page making it onto this list. It's
something set up for the amusement of a few close friends.
I _sorta_ apologize for its appearance here. ( i didn't post the URL )
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 12:06:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA15320
for freebsd-current-outgoing; Thu, 12 Nov 1998 12:06:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from home.dv.ru (home.dv.ru [195.98.33.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14962;
Thu, 12 Nov 1998 12:03:55 -0800 (PST)
(envelope-from dv@dv.ru)
Received: from localhost (dv@localhost)
by home.dv.ru (8.9.1/8.9.1) with SMTP id XAA12472;
Thu, 12 Nov 1998 23:03:11 +0300 (MSK)
(envelope-from dv@dv.ru)
X-Authentication-Warning: home.dv.ru: dv owned process doing -bs
Date: Thu, 12 Nov 1998 23:03:10 +0300 (MSK)
From: Dmitry Valdov <dv@dv.ru>
X-Sender: dv@localhost
To: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
Message-ID: <Pine.BSF.4.02A.9811122249450.12434-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi!
There is gdb's output:
0x280d7ea4 in _poll ()
(gdb) bt
#0 0x280d7ea4 in _poll ()
#1 0x280f4f11 in res_send ()
#2 0x280f1c57 in res_query ()
#3 0x280f2101 in __res_querydomain ()
#4 0x280f1e55 in res_search ()
#5 0x280eb5c8 in _gethostbydnsname ()
#6 0x280ea23f in gethostbyname2 ()
#7 0x280ea1c3 in gethostbyname ()
#8 0x805cd4e in ipcp_Init (ipcp=0x8078714, bundle=0x80785f0, l=0x80a3000,
parent=0x8078648) at ipcp.c:359
#9 0x804c1d1 in bundle_Create (prefix=0x807366d "/dev/tun", type=1,
argv=0xefbfdc44) at bundle.c:858
#10 0x8061df5 in main (argc=1, argv=0xefbfdc44) at main.c:324
#11 0x804a34d in _start ()
There is a part of my config file. There IS "delete! default":
default:
delete! default
set log Phase Chat LCP IPCP CCP tun command +debug
set device /dev/modem
set speed 57600
set reconnect 1 50
set timeout 300
set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK-AT-OK
ATE0Q0S0=1
pmdemand:
delete! default
set phone 777777
set login "TIMEOUT 120 ogin:--ogin: cbdv word: XXXX string: YYYYY
CONNECT
set log +debug
set timeout 300
set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
add default HISADDR
enable dns
There is netstat -rn:
home# netstat -rn
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif
Expire
default 10.0.0.2 UGSc 0 0 tun0
127.0.0.1 127.0.0.1 UH 0 33 lo0
When I delete default, ppp works OK:
home# ppp -auto pmdemand
Working in auto mode
^C
home# route delete default
delete net default
home# ppp -auto pmdemand
Working in auto mode
Using interface: tun0
home#
Is it enought to make you sure that it isn't user error? :)
You can reprodyce the problem by:
1. uncommenting 'pmdemand' section and add there delete! default
2. starting ppp with 'ppp -auto pmdemand'
3. killing it with -9
4. starting it again
---------- Forwarded message ----------
Date: Thu, 12 Nov 1998 11:30:04 +0300 (MSK)
From: Dmitry Valdov <dv@dv.ru>
To: dv@home.dv.ru
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
---------- Forwarded message ----------
Date: Thu, 12 Nov 1998 01:08:05 +0000
From: Brian Somers <brian@Awfulhak.org>
To: Dmitry Valdov <dv@dv.ru>
Cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
Are you doing anything funny with ``hostname'' on your machine ?
The only reports I've heard where ppp hangs at startup is when your
``hostname'' won't resolve (see http://www.FreeBSD.org/FAQ/userppp.html).
If this isn't the problem, I'd appreciate if you could build ppp with
-g and when it hangs, run ``gdb -p whatever'' and do a ``bt''.
Cheers.
> I've just tried to put
> "delete! default" in ppp.conf file and it has no effect. ppp hangs when
> default route exists.
>
>
> On Wed, 11 Nov 1998, Dmitry Valdov wrote:
>
> >
> >
> > ---------- Forwarded message ----------
> > Date: Tue, 10 Nov 1998 21:40:53 +0000
> > From: Brian Somers <brian@Awfulhak.org>
> > To: Jason Fesler <jfesler@gigo.com>
> > Cc: Kris Kennaway <kkennawa@physics.adelaide.edu.au>,
> > Dmitry Valdov <dv@dv.ru>, Brian Somers <brian@FreeBSD.ORG>,
> > current@FreeBSD.ORG
> > Subject: Re: cvs commit: src/usr.sbin/ppp ip.c
> >
> > > > Sorry for the "implicit bug report", Brian, but I've been meaning to track
> > > > this down for a long time and make sure it's not user error. I often see this
> > >
> > > I've had this since the 2.2.2 days when I first started running ppp.
> > > After a while (hours, days, weeks - random) either carrier isn't noticed
> > > as being missing, or all outgoing packets don't cross the serial cable to
> > > to the other side. After a while I kinda gave up.
> >
> > Ppp won't expect carrier if it's not detected when ppp starts doing
> > LCP. This allows null-modem cables without the correct wiring to
> > work.
> >
> > As I've said to a couple of these posts - enable debug logging and
> > you'll see the carrier status reported every second. You can also
> > ``show modem'' to see what things look like.
> >
> > > I now every few minutes fping a few hosts on the nearby remote side. If
> > > they _all_ fail (a good 10 second timeout is given) then I kill -9 the ppp
> > > session, wait 2 seconds, then restart ppp. It's caught every strange
> > > random bug on either side soon enough that I no longer have to try and
> > > call home and walk the wife through ppp..
> >
> > Ppp should be a lot more reliable these days.
--
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 Nov 12 12:20:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA17079
for freebsd-current-outgoing; Thu, 12 Nov 1998 12:20:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.webspan.net (mail.webspan.net [206.154.70.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17062
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 12:20:32 -0800 (PST)
(envelope-from opsys@mail.webspan.net)
Received: from orion.webspan.net (orion.webspan.net [206.154.70.5])
by mail.webspan.net (WEBSPAN/970608) with SMTP id PAA19749;
Thu, 12 Nov 1998 15:19:42 -0500 (EST)
Date: Thu, 12 Nov 1998 15:19:39 -0500 (EST)
From: Open Systems Networking <opsys@mail.webspan.net>
X-Sender: opsys@orion.webspan.net
To: Matthew Jacob <mjacob@feral.com>
cc: John Sconiers <jrs@enteract.com>, David Holland <dholland@cs.toronto.edu>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <Pine.LNX.4.02.9811121158530.25310-100000@feral-gw>
Message-ID: <Pine.BSF.4.02.9811121512560.14339-100000@orion.webspan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Just out of curiosity, is NFS a big deal because you HAVE to have it for
existing NFS implementations or is it becasue you WANT NFS.
I ask because im wondering if anyone uses CODA instead?
It is at least actively maintained. Like I said if its because you HAVE to
have NFS thats cool. But im wondering if people are just using NFS
because that may be all they think there is or all they know of.
Just curious
Chris
--
"You both seem to be ignoring the fact that the networking market is
driven by so-called 'IT professionals' these days, most of whom can't
tell the difference between an ARP and a carp." --Wes Peters
===================================| Open Systems FreeBSD Consulting.
FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186
-----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134
FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net
http://www.freebsd.org | Consulting, Network Engineering, Security
===================================| http://open-systems.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 12:22:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA17339
for freebsd-current-outgoing; Thu, 12 Nov 1998 12:22:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from feral-gw.feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17333
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 12:22:50 -0800 (PST)
(envelope-from mjacob@feral.com)
Received: from localhost (mjacob@localhost)
by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id MAA26105;
Thu, 12 Nov 1998 12:20:52 -0800
Date: Thu, 12 Nov 1998 12:20:52 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
X-Sender: mjacob@feral-gw
Reply-To: mjacob@feral.com
To: Open Systems Networking <opsys@mail.webspan.net>
cc: John Sconiers <jrs@enteract.com>, David Holland <dholland@cs.toronto.edu>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <Pine.BSF.4.02.9811121512560.14339-100000@orion.webspan.net>
Message-ID: <Pine.LNX.4.02.9811121219330.25310-100000@feral-gw>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Just out of curiosity, is NFS a big deal because you HAVE to have it for
> existing NFS implementations or is it becasue you WANT NFS.
It's required for interoperability with other systems.
> I ask because im wondering if anyone uses CODA instead?
> It is at least actively maintained. Like I said if its because you HAVE to
> have NFS thats cool. But im wondering if people are just using NFS
> because that may be all they think there is or all they know of.
No. Not necessarily. I use SMB a lot (for interoperability with Win32
systems).
I haven't tried the CODA stuff. Is it any good?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 12:26:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA17719
for freebsd-current-outgoing; Thu, 12 Nov 1998 12:26:50 -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 MAA17714
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 12:26:48 -0800 (PST)
(envelope-from lists@tar.com)
Received: from ppro.tar.com (ppro.tar.com [204.95.187.9])
by ns.tar.com (8.9.1/8.8.7) with SMTP id OAA17559;
Thu, 12 Nov 1998 14:26:22 -0600 (CST)
Message-Id: <199811122026.OAA17559@ns.tar.com>
From: "Richard Seaman, Jr." <lists@tar.com>
To: "green@unixhelp.org" <green@unixhelp.org>,
"Luoqi Chen" <luoqi@watermarkgroup.com>
Cc: "current@FreeBSD.ORG" <current@FreeBSD.ORG>
Date: Thu, 12 Nov 98 14:26:22 -0600
Reply-To: "Richard Seaman, Jr." <lists@tar.com>
X-Mailer: PMMail 1.92 For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: RFSIGSHARE ready?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 12 Nov 1998 14:17:43 -0500 (EST), Luoqi Chen wrote:
>> 2) linux threads creates stacks for each thread it creates via
>> mmap. It decides on where to start allocating them using the
>> following algorithm (I think).
>>
>> It gets the stack pointer of the initial thread,
>> figures the initial thread can get by with 2*STACK_SIZE
>> bytes (4MB in this case), and then starts allocating
>> thread user stacks 2*STACK_SIZE below the initial
>> thread stack.
>>
>> I don't pretend to really understand FreeBSD vm, to the following
>> is just a guess on my part. Maybe someone else can shed more
>> light on this.
>>
>> The problem is that FreeBSD dedicates 64MB for a process stack
>> (ie. for the initial thread), so that linux threads starts out
>> mmaping into the initial thread stack region. I don't know
>> exactly what happens at that point, but it doesn't seem to
>> be good.
>>
>I don't see anything bad, if the initial thread doesn't use more than
>2*STACK_SIZE.
>
>> I'm not sure why FreeBSD mmap allows a mmap into the process
>> user stack to succeed (but it appears to).
>>
>Why not? The only difference user stack from other user memory is
>the kernel imposes an autogrow policy.
>
>> You could consider patching either linux_mmap or the FreeBSD
>> mmap to reject attempts to mmap at virtual addresses above
>> p->p->vmspace->vm_maxaddr. I haven't tried this, so I don't
>> know if it will work.
>>
>> What this would do to an unmodified linux threads implementation
>> would be (I think) that the first 31 or 32 stack addresses it
>> tries to create would fail since they are trying to map into
>> the initial thread stack. But, after that, mmaps should succeed
>> and maybe the addresses will be ok. You'd loose the ability to
>> create 31 or 32 threads out of the total 1024 that linux threads
>> allows, but that wouldn't be the end of the world.
>>
>The first 31 threads are fine, in fact, they will enjoy the benefit
>of the autogrow policy on the user stack.
Well, you no doubt are right. I only said what I did because I've
tried running linux threads in FreeBSD "native". Granted, the
signal handling wasn't quite right, and maybe that was and still
is the problem I experienced.
But, my experience was that my test app would hang during the
creation of the first thread *unless* I *both* increased
the stack size to a non-zero value *and* moved it out of the
process stack area. That's why I said it didn't seem to be
a good idea to put zero size (or larger) thread stacks into
the process stack area.
I'll try it all again when the signal handling is fixed.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 12:30:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA18105
for freebsd-current-outgoing; Thu, 12 Nov 1998 12:30:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.webspan.net (mail.webspan.net [206.154.70.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18100
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 12:30:04 -0800 (PST)
(envelope-from opsys@mail.webspan.net)
Received: from orion.webspan.net (orion.webspan.net [206.154.70.5])
by mail.webspan.net (WEBSPAN/970608) with SMTP id PAA22050;
Thu, 12 Nov 1998 15:29:12 -0500 (EST)
Date: Thu, 12 Nov 1998 15:29:08 -0500 (EST)
From: Open Systems Networking <opsys@mail.webspan.net>
X-Sender: opsys@orion.webspan.net
To: Matthew Jacob <mjacob@feral.com>
cc: John Sconiers <jrs@enteract.com>, David Holland <dholland@cs.toronto.edu>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <Pine.LNX.4.02.9811121219330.25310-100000@feral-gw>
Message-ID: <Pine.BSF.4.02.9811121525130.14339-100000@orion.webspan.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, 12 Nov 1998, Matthew Jacob wrote:
> It's required for interoperability with other systems.
I was just curious.
> No. Not necessarily. I use SMB a lot (for interoperability with Win32
> systems).
I think pretty much everyone does on that end. I dont thinkI have ever
seen NFS to windows. I know the software exists I just dont think I have
ever seen anyone use it in a windows network. But samba yes.
> I haven't tried the CODA stuff. Is it any good?
I don't have alot experience with it but I have a client running it
on their small'ish network. They don't complain. BTW has anyone seen or
have any ideas on NFS v4? Just an RFC right now but wondered if anyone had
read it and had any thoughts on it?
Chris
--
"You both seem to be ignoring the fact that the networking market is
driven by so-called 'IT professionals' these days, most of whom can't
tell the difference between an ARP and a carp." --Wes Peters
===================================| Open Systems FreeBSD Consulting.
FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186
-----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134
FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net
http://www.freebsd.org | Consulting, Network Engineering, Security
===================================| http://open-systems.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 12:36:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA18535
for freebsd-current-outgoing; Thu, 12 Nov 1998 12:36:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18529
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 12:36:24 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id PAA23203;
Thu, 12 Nov 1998 15:39:02 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Thu, 12 Nov 1998 15:39:01 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: "Jason J. Horton" <jason@intercom.com>
cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <364B08C3.27FE59A4@intercom.com>
Message-ID: <Pine.BSF.4.05.9811121536291.4484-100000@porkfriedrice.ny.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, 12 Nov 1998, Jason J. Horton wrote:
> Everyone seems to be talking about using FreeBSD as an NFS client,
> how does FreeBSD do as a NFS server?
>
> -J
>
I'm going to be using NFS extensively at home for a while, I'll let you
know.
Last time I used it, it wasn't the most stable thing. A NFS mounted
buildworld crashed the server once, but then worked fine after that.
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 12:41:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA19167
for freebsd-current-outgoing; Thu, 12 Nov 1998 12:41:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19160
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 12:41:04 -0800 (PST)
(envelope-from psalzman@gamefish.pcola.gulf.net)
Received: from localhost (psalzman@localhost)
by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id UAA05318;
Thu, 12 Nov 1998 20:40:31 GMT
(envelope-from psalzman@gamefish.pcola.gulf.net)
Date: Thu, 12 Nov 1998 20:40:31 +0000 (GMT)
From: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
To: Alfred Perlstein <bright@hotjobs.com>
cc: "Jason J. Horton" <jason@intercom.com>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <Pine.BSF.4.05.9811121536291.4484-100000@porkfriedrice.ny.genx.net>
Message-ID: <Pine.BSF.4.05.9811122039130.5242-100000@gamefish.pcola.gulf.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> Last time I used it, it wasn't the most stable thing. A NFS mounted
> buildworld crashed the server once, but then worked fine after that.
I was able to do it fine while bringing a machine from 2.2.2-R
to 2.2.6-STABLE. The server was a 2.2.6-STABLE machine. It used a good
amount of CPU, tho. And it went rather slowly.
--
Phillip Salzman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 12:43:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA19355
for freebsd-current-outgoing; Thu, 12 Nov 1998 12:43:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19338
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 12:43:32 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id PAA23213;
Thu, 12 Nov 1998 15:46:09 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Thu, 12 Nov 1998 15:46:08 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
cc: "Jason J. Horton" <jason@intercom.com>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <Pine.BSF.4.05.9811122039130.5242-100000@gamefish.pcola.gulf.net>
Message-ID: <Pine.BSF.4.05.9811121545200.4484-100000@porkfriedrice.ny.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
> > Last time I used it, it wasn't the most stable thing. A NFS mounted
> > buildworld crashed the server once, but then worked fine after that.
>
>
> I was able to do it fine while bringing a machine from 2.2.2-R
> to 2.2.6-STABLE. The server was a 2.2.6-STABLE machine. It used a good
> amount of CPU, tho. And it went rather slowly.
2.2.2 client -> 3.0-current server (pre-mckusik patches)
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 12:56:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA20462
for freebsd-current-outgoing; Thu, 12 Nov 1998 12:56:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from post.mail.demon.net (post-12.mail.demon.net [194.217.242.41])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20396
for <freebsd-current@freebsd.org>; Thu, 12 Nov 1998 12:55:36 -0800 (PST)
(envelope-from james@westongold.com)
Received: from [158.152.96.124] (helo=wgp01.wgold.demon.co.uk)
by post.mail.demon.net with esmtp (Exim 2.05demon1 #1)
id 0ze3lg-0005xc-00; Thu, 12 Nov 1998 20:55:04 +0000
Received: by WGP01 with Internet Mail Service (5.5.1960.3)
id <W2PQAPPG>; Mon, 9 Nov 1998 08:51:37 -0000
Message-ID: <32BABEF63EAED111B2C5204C4F4F50201810@WGP01>
From: James Mansion <james@westongold.com>
To: Tom <tom@uniserve.com>, Mike Smith <mike@smith.net.au>
Cc: sporkl@ix.netcom.com, freebsd-current@FreeBSD.ORG
Subject: RE: SparQ Drive and 3.0 upgrade
Date: Mon, 9 Nov 1998 08:51:30 -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
Out of interest, is there a 'recommended' high-capacity
removable device that can be used to boot different OSs on
a single PC?
Jazz???
James
> -----Original Message-----
> From: Tom [mailto:tom@uniserve.com]
> Sent: Monday, November 09, 1998 1:17 AM
> To: Mike Smith
> Cc: sporkl@ix.netcom.com; freebsd-current@FreeBSD.ORG
> Subject: Re: SparQ Drive and 3.0 upgrade
>
>
>
> On Sun, 8 Nov 1998, Mike Smith wrote:
>
> > >
> > > I recently got a SparQ EIDE 1.0GB drive, and my 2.2.7-STABLE
> > > system doesn't detect it. I downloaded the 3.0 boot
> floppy and booting
> > > that it got detected. If I upgrade to 3.0-RELEASE right
> now, on my PII
> > > w/an AHA-2940UW, AGP video card, etc., will I completely
> regret it? What
> > > is the cvsup tag for 3.0? Thanks.
> >
> > 3.0-RELEASE has the same format release tag as all the
> other releases.
> > You'd be better off supping straight to -current though.
> >
> > What you'll regret most however is buying one of those
> disgusting Sparq
> > drives.
>
> Especially now that SyQuest has just gone out of business.
>
> > --
> > \\ 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
>
> Tom
>
>
> 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 Nov 12 13:12:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA22208
for freebsd-current-outgoing; Thu, 12 Nov 1998 13:12:53 -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 NAA22199
for <freebsd-current@FreeBSD.ORG>; Thu, 12 Nov 1998 13:12:30 -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 WAA00698;
Thu, 12 Nov 1998 22:10:01 +0100 (CET)
To: James Mansion <james@westongold.com>
cc: Tom <tom@uniserve.com>, Mike Smith <mike@smith.net.au>,
sporkl@ix.netcom.com, freebsd-current@FreeBSD.ORG
Subject: Re: SparQ Drive and 3.0 upgrade
In-reply-to: Your message of "Mon, 09 Nov 1998 08:51:30 GMT."
<32BABEF63EAED111B2C5204C4F4F50201810@WGP01>
Date: Thu, 12 Nov 1998 22:10:00 +0100
Message-ID: <696.910905000@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 <32BABEF63EAED111B2C5204C4F4F50201810@WGP01>, James Mansion writes:
>Out of interest, is there a 'recommended' high-capacity
>removable device that can be used to boot different OSs on
>a single PC?
standard hard disk in plastic or metal removable tray ?
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 13:14:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA22453
for freebsd-current-outgoing; Thu, 12 Nov 1998 13:14:28 -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 NAA22442
for <freebsd-current@FreeBSD.ORG>; Thu, 12 Nov 1998 13:14:25 -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 NAA00623;
Thu, 12 Nov 1998 13:12:36 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811122112.NAA00623@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: James Mansion <james@westongold.com>
cc: Tom <tom@uniserve.com>, Mike Smith <mike@smith.net.au>,
sporkl@ix.netcom.com, freebsd-current@FreeBSD.ORG
Subject: Re: SparQ Drive and 3.0 upgrade
In-reply-to: Your message of "Mon, 09 Nov 1998 08:51:30 GMT."
<32BABEF63EAED111B2C5204C4F4F50201810@WGP01>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 12 Nov 1998 13:12:36 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Out of interest, is there a 'recommended' high-capacity
> removable device that can be used to boot different OSs on
> a single PC?
>
> Jazz???
Jaz drives are the best of the magnetic bunch. They require careful
care and feeding, like any such device.
I'd recommend MO if you're serious about reliability. The Fujitsu
3.5" drives are down around the same price as Jaz units these days.
--
\\ 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 Nov 12 13:18:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA22906
for freebsd-current-outgoing; Thu, 12 Nov 1998 13:18:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from london.physics.purdue.edu (london.physics.purdue.edu [128.210.67.35])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22892
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 13:18:34 -0800 (PST)
(envelope-from ajk@physics.purdue.edu)
Received: from poynting.physics.purdue.edu (poynting.physics.purdue.edu [128.210.146.58])
by london.physics.purdue.edu (8.8.8/8.8.8) with SMTP id QAA20273;
Thu, 12 Nov 1998 16:18:03 -0500 (EST)
Date: Thu, 12 Nov 1998 16:18:03 -0500 (EST)
From: "Andrew J. Korty" <ajk@physics.purdue.edu>
To: Alfred Perlstein <bright@hotjobs.com>
cc: "Jason J. Horton" <jason@intercom.com>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <Pine.BSF.4.05.9811121536291.4484-100000@porkfriedrice.ny.genx.net>
Message-ID: <Pine.BSF.3.96.981112161525.15875J-100000@poynting.physics.purdue.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 Thu, 12 Nov 1998, Alfred Perlstein wrote:
> On Thu, 12 Nov 1998, Jason J. Horton wrote:
>
> > Everyone seems to be talking about using FreeBSD as an NFS client,
> > how does FreeBSD do as a NFS server?
> >
> > -J
> >
>
> I'm going to be using NFS extensively at home for a while, I'll let you
> know.
>
> Last time I used it, it wasn't the most stable thing. A NFS mounted
> buildworld crashed the server once, but then worked fine after that.
We've been able to crash FreeBSD 3.0 NFS (both versions 2 and 3)
servers repeatably by starting KDE on a FreeBSD (any version) client
that mounts one's home directory off the server. See kern/8515.
Hope this helps ...
Andrew J. Korty, Director http://www.physics.purdue.edu/~ajk/
Physics Computer Network 85 73 1F 04 63 D9 9D 65
Purdue University 65 2E 7A A8 81 8C 45 75
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 13:51:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA26267
for freebsd-current-outgoing; Thu, 12 Nov 1998 13:51:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail2.tor.accglobal.net (mail2.tor.accglobal.net [204.92.55.104])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26262
for <current@freebsd.org>; Thu, 12 Nov 1998 13:51:00 -0800 (PST)
(envelope-from josh@ican.net)
Received: from staff.tor.acc.ca ([204.92.55.27])
by mail2.tor.accglobal.net with esmtp (Exim 2.02 #1)
id 0ze4dU-0002NS-02
for current@freebsd.org; Thu, 12 Nov 1998 16:50:40 -0500
Received: from josh by staff.tor.acc.ca with local (Exim 1.92 #1)
for current@freebsd.org
id 0ze4dT-0003Q2-00; Thu, 12 Nov 1998 16:50:39 -0500
Message-ID: <19981112165039.32105@ican.net>
Date: Thu, 12 Nov 1998 16:50:39 -0500
From: Josh Tiefenbach <josh@ican.net>
To: current@FreeBSD.ORG
Subject: Problems/questions about boot blocks
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.74
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'm having some problems setting up my machine to dual boot between FreeBSD
and Win98.
Specifics:
In the machine, there are two 2gig drives hooked up to the onboard ahc
controller (its an ASUS P2B-S board). I've installed 3.0-RELEASE onto
the first drive (ID 0), and I've formatted and sys'd the second drive (ID 1)
with win98.
Problem is, that no matter what I've tried, I havent been unable to get the
machine to boot from the win98 disk.
When the machine initially boots, I get the
F1: FreeBSD
prompt. Which is kinda odd, since I would have expected that the boot blocks
would have noted the existance of the second disk. When I try hitting F5 to
try to force booting off the second disk, I get a "Missing operating system"
message.
I *think* that I'm using the old boot-blocks, 'cause when I boot into FreeBSD,
I get the big honking instruction message, and its honoring the directives in
/boot.config, and firing up /boot/loader
Would using the new boot0 bootblocks help? How would I get them installed?
fdisk shows:
da0: <Quantum XP32150W L915> Fixed Direct Access SCSI2 device
madoff:~# fdisk -t /dev/rda0
******* Working on device /dev/rda0 *******
parameters extracted from in-core disklabel are:
cylinders=720 heads=108 sectors/track=54 (5832 blks/cyl)
parameters to be used for BIOS calculations are:
cylinders=720 heads=108 sectors/track=54 (5832 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 54, size 4198986 (2050 Meg), flag 80 (active)
beg: cyl 0/ sector 1/ head 1;
end: cyl 719/ sector 54/ head 107
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
da1: <Quantum XP32150W L915> Fixed Direct Access SCSI2 device
madoff:~# fdisk -t /dev/rda1
******* Working on device /dev/rda1 *******
parameters extracted from in-core disklabel are:
cylinders=261 heads=255 sectors/track=63 (16065 blks/cyl)
parameters to be used for BIOS calculations are:
cylinders=261 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 6,(Primary 'big' DOS (> 32MB))
start 63, size 4192902 (2047 Meg), flag 80 (active)
beg: cyl 0/ sector 1/ head 1;
end: cyl 260/ sector 63/ head 254
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
josh
--
Josh Tiefenbach - Member - ACC Corps of Internet Engineers - josh@ican.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 14:14:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA29955
for freebsd-current-outgoing; Thu, 12 Nov 1998 14:14:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mnw.eas.slu.edu (mnw.eas.slu.edu [165.134.8.248])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29897
for <current@freebsd.org>; Thu, 12 Nov 1998 14:13:55 -0800 (PST)
(envelope-from ejh@mnw.eas.slu.edu)
Received: (from ejh@localhost)
by mnw.eas.slu.edu (8.8.8/8.8.8) id QAA22227
for current@freebsd.org; Thu, 12 Nov 1998 16:13:26 -0600 (CST)
Date: Thu, 12 Nov 1998 16:13:26 -0600 (CST)
From: Eric Haug <ejh@eas.slu.edu>
Message-Id: <199811122213.QAA22227@mnw.eas.slu.edu>
To: current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS Server
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I have been using FreeBSD 3.0-CURRENT Mon Nov 2
as a NFS server to our network of Sparcs
Since the patch for freeing a null pointer was applied
it has not crashed.
We do get quite a few of the following messages on the various
Sparc that access it
Nov 9 13:39:50 thor.eas.slu.edu unix: NFS server tds not responding still trying
Nov 9 13:39:50 thor.eas.slu.edu unix: NFS server tds ok
All Maxtor 91190D7 IDE disks.
Using softupdates as well.
/dev/wd0s1a 78103 22022 49833 31% /
/dev/wd0s1e 745342 643151 42564 94% /usr
/dev/wd0s1f 10546816 1222856 8480216 13% /d0
procfs 4 4 0 100% /proc
/dev/wd4s1f 10546816 24 9703048 0% /d1
/dev/wd5s1f 10546816 3106656 6596416 32% /d2
/dev/wd6s1f 10546816 1792792 7910280 18% /d3
/dev/wd7s1f 10546816 8116600 1586472 84% /d4
/dev/ccd0a 3477480 763056 2436232 24% /cvs
Eric Haug
Saint Louis University
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 14:22:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA00815
for freebsd-current-outgoing; Thu, 12 Nov 1998 14:22:02 -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 OAA00783
for <current@freebsd.org>; Thu, 12 Nov 1998 14:21:33 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2])
by nlsystems.com (8.9.1/8.8.5) with SMTP id WAA12973;
Thu, 12 Nov 1998 22:20:26 GMT
Date: Thu, 12 Nov 1998 22:20:26 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: geoffb@demon.net
cc: current@FreeBSD.ORG
Subject: Re: DEC Multia support
In-Reply-To: <199811121738.RAA04974@gti.noc.demon.net>
Message-ID: <Pine.BSF.4.01.9811122218470.11371-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, 12 Nov 1998, Geoff Buckingham wrote:
> > On Thu, 12 Nov 1998, Geoff Buckingham wrote:
> >
> > >
> > > How well are the onboard IDE/floppy/ethernet of the Multia supported in
> > > current at the moment?
> >
> > Ethernet should work. Floppy will work when I find time to port the
> > floppy driver over. IDE will probably have to wait until the new atapi
> > code is ready.
> >
>
> Given the above is my best route to installing FreeBSD to start with
> NetBSD and migrate?
If you have SCSI disks, then the best route is to install using the floppy
images from the regular snapshots. We can boot from a floppy without
problems. There isn't a floppy driver to use after boot yet though.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 951 1891
Fax: +44 181 381 1039
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 14:43:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA03541
for freebsd-current-outgoing; Thu, 12 Nov 1998 14:43:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03509
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 14:42:46 -0800 (PST)
(envelope-from son@teaser.fr)
Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40])
by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id XAA26892;
Thu, 12 Nov 1998 23:41:57 +0100 (MET)
Received: (from son@localhost)
by teaser.fr (8.9.1/8.8.5) id XAA00958;
Thu, 12 Nov 1998 23:28:34 GMT
Message-ID: <19981112232834.48551@breizh.prism.uvsq.fr>
Date: Thu, 12 Nov 1998 23:28:34 +0000
From: Nicolas Souchu <nsouch@teaser.fr>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Cc: FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: ZIP+ and NatSemi parallel port chipst (was Re: ZIP, again)
References: <19981108220152.06173@breizh.prism.uvsq.fr> <XFMail.981109231327.asmodai@wxs.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81e
In-Reply-To: <XFMail.981109231327.asmodai@wxs.nl>; from Jeroen Ruigrok/Asmodai on Mon, Nov 09, 1998 at 11:13:27PM +0100
X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Nov 09, 1998 at 11:13:27PM +0100, Jeroen Ruigrok/Asmodai wrote:
>
>ppc: parallel port found at 0x378
>ppc0 at 0x378 irq 7 on isa
>ppc0: W83877F chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
>nlpt0: <generic printer> on ppbus 0
>nlpt0: Interrupt-driven port
>ppi0: <generic parallel i/o> on ppbus 0
>imm0: <Iomega Matchmaker Parallel to SCSI interface> on ppbus 0
>imm0: EPP 1.9 mode
>
>There ye goes...
>
>
>> In fact, we have some problems with NSC chips here.
>>
>> Anybody could report successfull ZIP+ detection with NatSemi chips?
>
>So I guess it's detected alright... Now to know how to use it *G*
You can't use it?
>
>Can ye define NatSemi chips? Or is that short for National Semiconductor?
Yes I meant National Semiconductor. Yours is a Winbond. Thanks anyway for your
logs.
>
>---
>Jeroen Ruigrok van der Werven/Asmodai
>asmodai(at)wxs.nl | Cum angelis et pueris,
>Junior Network/Security Specialist | fideles inveniamur
>*BSD & picoBSD: The Power to Serve... <http://www.freebsd.org>
>
--
nsouch@teaser.fr / nsouch@freebsd.org
FreeBSD - Turning PCs into workstations - 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 Thu Nov 12 14:46:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA04223
for freebsd-current-outgoing; Thu, 12 Nov 1998 14:46:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04218
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 14:46:23 -0800 (PST)
(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
by lor.watermarkgroup.com (8.8.8/8.8.8) id RAA25462;
Thu, 12 Nov 1998 17:46:01 -0500 (EST)
(envelope-from luoqi)
Date: Thu, 12 Nov 1998 17:46:01 -0500 (EST)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <199811122246.RAA25462@lor.watermarkgroup.com>
To: green@unixhelp.org, lists@tar.com, luoqi@watermarkgroup.com
Subject: Re: RFSIGSHARE ready?
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> But, my experience was that my test app would hang during the
> creation of the first thread *unless* I *both* increased
> the stack size to a non-zero value *and* moved it out of the
> process stack area. That's why I said it didn't seem to be
> a good idea to put zero size (or larger) thread stacks into
> the process stack area.
>
I wrote a test problem myself, and I found that mapping into
user stack area interfered with the stack autogrow function.
To work around this problem, in i386/i386/trap.c around line 632,
ignore the return from grow(), and let the page fault still be
handled by vm_fault().
-lq
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 15:12:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA07739
for freebsd-current-outgoing; Thu, 12 Nov 1998 15:12:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sphinx.lovett.com (sphinx.lovett.com [38.155.241.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07728
for <current@freebsd.org>; Thu, 12 Nov 1998 15:12:32 -0800 (PST)
(envelope-from ade@supernews.net)
Received: from [38.155.241.8] (helo=xanadu)
by sphinx.lovett.com with smtp (Exim 2.05 #1)
id 0ze5uP-0005AB-00
for current@freebsd.org; Thu, 12 Nov 1998 17:12:13 -0600
From: "Ade Lovett" <ade@supernews.net>
To: <current@FreeBSD.ORG>
Subject: ATAPI CD/R driver and Mitsumi CR-2600TE
Date: Thu, 12 Nov 1998 17:10:15 -0600
Message-ID: <002301be0e91$9b948040$08f19b26@xanadu.lovett.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi all,
I recently acquired (at no cost) a Mitsumi CR-2600TE cd burner, and
plugged it in to my 3.0-CURRENT system to try out the acd driver.
Unfortunately, there appears to be something of a problem.. when the
burncd script gets around to doing the dd(1) it completely fails with
acd0: rezero failed
Cranking up the atapi debug code, the failure appears as follows:
atapi1.1: req w 1-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0 len=0
atapi1.1: start
atapi1.1: intr ireason=0x1, len=0, status=58<ready,opdone,drq>, error=0
atapi1.1: send cmd REZERO_UNIT 1-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0
atapi1.1: intr ireason=0x3, len=0, status=51<ready,opdone,check>, error=50
atapi1.1: illegal request
acd0: rezero failed
this little lot then repeats itself (so it looks like the driver is trying
two REZERO_UNIT commands), before it finally gives up.
I've verified that the unit works on the same machine under Win98 with the
supplied Adaptec burning software, and I've tried multiple blank disks
from different vendors, so it's unlikely to be that.
Any suggestions on making this puppy work? Or should I just throw it away?
-aDe
--
Ade Lovett, Supernews Inc., San Jose, CA.
ade@supernews.net http://www.supernews.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 16:10:58 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA18277
for freebsd-current-outgoing; Thu, 12 Nov 1998 16:10:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from papillon.lemis.com (papillon.lemis.com [192.109.197.159])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18261
for <freebsd-current@freebsd.org>; Thu, 12 Nov 1998 16:10:53 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by papillon.lemis.com (8.9.1/8.6.12) with ESMTP
id IAA02921; Fri, 13 Nov 1998 08:30:02 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.1/8.9.0) id IAA24182;
Fri, 13 Nov 1998 08:30:28 +1030 (CST)
Message-ID: <19981113083028.O463@freebie.lemis.com>
Date: Fri, 13 Nov 1998 08:30:28 +1030
From: Greg Lehey <grog@lemis.com>
To: Steve Kiernan <stevek@tis.com>, freebsd-current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <Pine.BSF.3.96.981111131906.15869B-100000@mufasa.va.tis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <Pine.BSF.3.96.981111131906.15869B-100000@mufasa.va.tis.com>; from Steve Kiernan on Wed, Nov 11, 1998 at 01:24:41PM -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, 11 November 1998 at 13:24:41 -0500, Steve Kiernan wrote:
>
> Since there's no a.out gdb compiled I went to compile the latest gdb with
> a.out support, but it blew up in syntax errors. What version of gdb will
> actually build on 3.0 with a.out support so I can debug my crash dumps?
Well, I didn't have any trouble. You can (theoretically) pick up a
copy from ftp://ftp.lemis.com/pub/vinum/gdb-aout, but at the moment
we're off the net due to a phone cable fault which might be fixed in
the next few hours. If you don't get a connection, assume it's still
down: normally we have a good connection to the net.
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 Nov 12 16:31:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA20745
for freebsd-current-outgoing; Thu, 12 Nov 1998 16:31:38 -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 QAA20734
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 16:31:32 -0800 (PST)
(envelope-from doconnor@gsoft.com.au)
Received: from cain.gsoft.com.au (cain [203.38.152.97])
by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA21865;
Fri, 13 Nov 1998 11:00:56 +1030 (CST)
(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.981113110056.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: <199811121942.LAA28198@pau-amma.whistle.com>
Date: Fri, 13 Nov 1998 11:00:56 +1030 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: David Wolfskill <dhw@whistle.com>
Subject: Re: StarOffice-5.0...
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 12-Nov-98 David Wolfskill wrote:
> Well, one example of something I would like to be able to do is to have
> an automatic procedure (say, a script) that I could run on a box and get
> enough information that I could squirrel away (off-site, for example) so
> that, given the list and enough money, I could specify what parts to buy
> so the machine could be re-created (and so that once the off-site
> backups were restored, I'd have a fairly good approximation to the
> original machine).
How about...
ssh user@machine 'mail -s "dmesg from machine" my@email.com
</var/run/dmesg.boot'
> Even better: I'd like for a person who is not necessarily a FreeBSD
> wizard be able to read the list, specify the parts, and assemble them
> into a working whole.
Well, dmesg isn't that hard to read...
> That may well be useful for many purposes. It's not at all obvious that
> it's useful for what I'm trying to do. So far, looking at
> /var/run/dmesg.boot comes closest that I've been able to find, but
> there's very little there about the video card(s?), for example.
And what irq's it uses are going to be any better?
IMHO the only way you could do that would be to read the X output..
---
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 Thu Nov 12 16:47:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA22746
for freebsd-current-outgoing; Thu, 12 Nov 1998 16:47:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22734
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 16:47:03 -0800 (PST)
(envelope-from drosih@rpi.edu)
Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47])
by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id TAA101462
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 19:47:39 -0500
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: drosih@pop1.rpi.edu
Message-Id: <v0401170ab2712eb7c0fb@[128.113.24.47]>
In-Reply-To: <199811122213.QAA22227@mnw.eas.slu.edu>
Date: Thu, 12 Nov 1998 19:46:48 -0500
To: current@FreeBSD.ORG
From: Garance A Drosihn <drosih@rpi.edu>
Subject: Re: Is it soup yet? FreeBSD NFS Server
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
At 4:13 PM -0600 11/12/98, Eric Haug wrote:
> I have been using FreeBSD 3.0-CURRENT Mon Nov 2
> as a NFS server to our network of Sparcs. Since the
> patch for freeing a null pointer was applied it has
> not crashed.
Our CS dept has a number of freebsd machines which are
NFS servers for some sparc, irix, and freebsd boxes. I
think the servers are all freebsd 2.2.6 or later (but
not 3.<anything>). If they're doing version 2 NFS,
then everything is quite fine. If they're setup to
do version 3 NFS, then access from the sparcs (or irix,
I forget) would regularly cause the freebsd servers to
crash.
I don't know if the version 3 NFS problems have been
addressed in 3.0-current. Seems to me that someone
(Terry Lambert?) had some patches which were an initial
stab of fixing these problems, but I might be getting
mixed up on that.
---
Garance Alistair Drosehn = gad@eclipse.its.rpi.edu
Senior Systems Programmer or drosih@rpi.edu
Rensselaer Polytechnic Institute
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 16:51:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA23304
for freebsd-current-outgoing; Thu, 12 Nov 1998 16:51:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cassiopeia.hkstar.com (cassiopeia.hkstar.com [202.82.3.11])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23292
for <freebsd-current@freebsd.org>; Thu, 12 Nov 1998 16:51:23 -0800 (PST)
(envelope-from c5666305@b1.hkstar.com)
Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87])
by cassiopeia.hkstar.com (8.9.1/8.9.1) with ESMTP id IAA09952
for <freebsd-current@freebsd.org>; Fri, 13 Nov 1998 08:50:57 +0800 (HKT)
Received: (from c5666305@localhost)
by b1.hkstar.com (8.8.8/8.8.8) id IAA03437
for freebsd-current@freebsd.org; Fri, 13 Nov 1998 08:53:19 +0800 (HKT)
From: Chan Yiu Wah <c5666305@b1.hkstar.com>
Message-Id: <199811130053.IAA03437@b1.hkstar.com>
Subject: Where can I get the xform (elf version)
To: freebsd-current@FreeBSD.ORG
Date: Fri, 13 Nov 1998 08:53:18 +0800 (HKT)
X-Mailer: ELM [version 2.5 PL0b1]
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,
I recently tried to install lyx and found that the xform in elf format was
missing. Can anyone tell me where can I get it ? thanks.
Clarence
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 16:54:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA23841
for freebsd-current-outgoing; Thu, 12 Nov 1998 16:54:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from papillon.lemis.com (papillon.lemis.com [192.109.197.159])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23831
for <current@FreeBSD.org>; Thu, 12 Nov 1998 16:54:43 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by papillon.lemis.com (8.9.1/8.6.12) with ESMTP
id VAA02411; Thu, 12 Nov 1998 21:29:22 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.1/8.9.0) id VAA23065;
Thu, 12 Nov 1998 21:29:48 +1030 (CST)
Message-ID: <19981112212947.N463@freebie.lemis.com>
Date: Thu, 12 Nov 1998 21:29:47 +1030
From: Greg Lehey <grog@lemis.com>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Julian Elischer <julian@whistle.com>
Cc: Brian Feldman <green@unixhelp.org>, Peter Wemm <peter@netplex.com.au>,
Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
References: <Pine.BSF.3.95.981111195924.16947C-100000@current1.whistle.com> <22777.910844416@zippy.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <22777.910844416@zippy.cdrom.com>; from Jordan K. Hubbard on Wed, Nov 11, 1998 at 08:20:16PM -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 Wednesday, 11 November 1998 at 20:20:16 -0800, Jordan K. Hubbard wrote:
> Can we just end this thread?
Amen.
If anything useful came out if it, would somebody please summarize?
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 Nov 12 17:17:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA26392
for freebsd-current-outgoing; Thu, 12 Nov 1998 17:17:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from 207.240.250.178 (04-178.015.popsite.net [207.240.250.178])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA26367
for <freebsd-current@freebsd.org>; Thu, 12 Nov 1998 17:17:47 -0800 (PST)
(envelope-from dizzy_Blond@mindless.com)
Date: Thu, 12 Nov 1998 17:17:47 -0800 (PST)
Message-Id: <199811130117.RAA26367@hub.freebsd.org>
From: dizzy_Blond@mindless.com
To: freebsd-current@FreeBSD.ORG
Subject: Welcome -XROU
X-Reply-To: dizzy_blond@mindles.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello freebsd-current
You are receiving this email because your name
appeared on a list of Business opportunity seekers
I purchased or we have had correspondence in the past.
In any event to be removed from the list reply with "remove"
in the subject of the message if you do not wish to receive further messages from me.
Now on to the good stuff!
Banner Exchange goes MLM! That's right.
Advertise your site and get paid for referrals.
Click throughs are MUCH better than the other
banner exchanges we have used and we are
building additional residual income FAST!
Bring your downline for a fast start! http://bighits.net/?dizzy
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 17:45:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA29643
for freebsd-current-outgoing; Thu, 12 Nov 1998 17:45:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29636
for <freebsd-current@freebsd.org>; Thu, 12 Nov 1998 17:45:37 -0800 (PST)
(envelope-from ckempf@singularity.enigami.com)
Received: (from ckempf@localhost)
by singularity.enigami.com (8.9.1/8.9.1) id UAA24511;
Thu, 12 Nov 1998 20:45:12 -0500 (EST)
To: Chan Yiu Wah <c5666305@b1.hkstar.com>, freebsd-current@FreeBSD.ORG
Subject: Re: Where can I get the xform (elf version)
References: <199811130053.IAA03437@b1.hkstar.com>
From: Cory Kempf <ckempf@enigami.com>
Date: 12 Nov 1998 20:45:11 -0500
In-Reply-To: Chan Yiu Wah's message of "Fri, 13 Nov 1998 08:53:18 +0800 (HKT)"
Message-ID: <x7vhkk4b88.fsf@singularity.enigami.com>
Lines: 15
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Chan Yiu Wah <c5666305@b1.hkstar.com> writes:
> I recently tried to install lyx and found that the xform in elf format was
> missing. Can anyone tell me where can I get it ? thanks.
freebsd/elf is now available thru http://bragg.phys.uwm.edu/xforms
+C
--
Thinking of purchasing RAM from the Chip Merchant?
Please read this first: <http://www.enigami.com/~ckempf/chipmerchant.html>
Cory Kempf Macintosh / Unix Consulting & Software Development
ckempf@enigami.com <http://www.enigami.com/~ckempf/>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 17:48:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA00416
for freebsd-current-outgoing; Thu, 12 Nov 1998 17:48:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from aldan.algebra.com (kot.ne.mediaone.net [24.128.29.55])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00395
for <current@freebsd.org>; Thu, 12 Nov 1998 17:48:21 -0800 (PST)
(envelope-from mi@aldan.algebra.com)
Received: (from mi@localhost)
by aldan.algebra.com (8.8.8/8.8.7) id BAA24474
for current@freebsd.org; Fri, 13 Nov 1998 01:47:33 GMT
(envelope-from mi)
From: Mikhail Teterin <mi@aldan.algebra.com>
Message-Id: <199811130147.BAA24474@aldan.algebra.com>
Subject: Re: Where can I get the xform (elf version)
In-Reply-To: <x7vhkk4b88.fsf@singularity.enigami.com> from Cory Kempf at "Nov 12, 1998 08:45:11 pm"
To: current@FreeBSD.ORG
Date: Fri, 13 Nov 1998 01:47:33 +0000 (GMT)
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
Cory Kempf once stated:
=> I recently tried to install lyx and found that the xform in elf format was
=> missing. Can anyone tell me where can I get it ? thanks.
=
=freebsd/elf is now available thru http://bragg.phys.uwm.edu/xforms
What about Motif? Any ideas?
-mi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 18:51:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA07969
for freebsd-current-outgoing; Thu, 12 Nov 1998 18:51:31 -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 SAA07964
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 18:51:26 -0800 (PST)
(envelope-from fullermd@futuresouth.com)
Received: (from fullermd@localhost)
by shell.futuresouth.com (8.8.8/8.8.8) id UAA08988;
Thu, 12 Nov 1998 20:51:05 -0600 (CST)
Message-ID: <19981112205105.31196@futuresouth.com>
Date: Thu, 12 Nov 1998 20:51:05 -0600
From: "Matthew D. Fuller" <fullermd@futuresouth.com>
To: Open Systems Networking <opsys@mail.webspan.net>
Cc: current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
References: <Pine.LNX.4.02.9811121158530.25310-100000@feral-gw> <Pine.BSF.4.02.9811121512560.14339-100000@orion.webspan.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.88
In-Reply-To: <Pine.BSF.4.02.9811121512560.14339-100000@orion.webspan.net>; from Open Systems Networking on Thu, Nov 12, 1998 at 03:19:39PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, Nov 12, 1998 at 03:19:39PM -0500, Open Systems Networking woke me up to tell me:
>
> Just out of curiosity, is NFS a big deal because you HAVE to have it for
> existing NFS implementations or is it becasue you WANT NFS.
> I ask because im wondering if anyone uses CODA instead?
> It is at least actively maintained. Like I said if its because you HAVE to
> have NFS thats cool. But im wondering if people are just using NFS
> because that may be all they think there is or all they know of.
I'm waiting to get a decent motherboard for a fileserver I have at home,
then I'm going to be going slightly hog-wild on this. Have a couple
systems I picked up for a song, and their hard drive controllers
(onboard, more's the pity) have gone to the great big bitbucket in the
sky, and a few other systems with micro-harddrives. I haven't had time
to do much looking at CODA, so I'm not sure how easy doing any of this
with it would be, but I've got time to play...
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| FreeBSD; the way computers were meant to be |
* "The only reason I'm burning my candle at both ends, is *
| that I haven't figured out how to light the middle yet."|
* fullermd@futuresouth.com :-} MAtthew Fuller *
| http://keystone.westminster.edu/~fullermd |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 18:57:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA08594
for freebsd-current-outgoing; Thu, 12 Nov 1998 18:57:26 -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 SAA08568
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 18:57:04 -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 VAA18037;
Thu, 12 Nov 1998 21:46:51 -0500 (EST)
Date: Thu, 12 Nov 1998 21:46:51 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Julian Elischer <julian@whistle.com>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <Pine.BSF.3.95.981111195924.16947C-100000@current1.whistle.com>
Message-ID: <Pine.BSF.4.05.9811122146120.17981-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, 11 Nov 1998, Julian Elischer wrote:
>
> the existing bootblocks predate "Boot.conf"
Yes. They do not predate boot.config.
>
> >
> > Cheers,
> > Brian Feldman
> >
> >
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 19:02:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA09438
for freebsd-current-outgoing; Thu, 12 Nov 1998 19:02:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mordred.cs.ucla.edu (Mordred.CS.UCLA.EDU [131.179.48.34])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09432
for <freebsd-current@freebsd.org>; Thu, 12 Nov 1998 19:02:31 -0800 (PST)
(envelope-from scottm@mordred.cs.ucla.edu)
Received: from mordred.cs.ucla.edu (localhost [127.0.0.1])
by mordred.cs.ucla.edu (8.9.1/8.9.1) with ESMTP id TAA00315
for <freebsd-current@freebsd.org>; Thu, 12 Nov 1998 19:02:11 -0800 (PST)
(envelope-from scottm@mordred.cs.ucla.edu)
Message-Id: <199811130302.TAA00315@mordred.cs.ucla.edu>
X-Mailer: exmh version 2.0.2 2/24/98
To: freebsd-current@FreeBSD.ORG
Subject: disklabel and changing boot blocks
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 12 Nov 1998 19:02:11 -0800
From: Scott Michel <scottm@cs.ucla.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Sorry if this completely dippy or paranoid, but do you need
to rerun disklabel each time there's a new boot[12]?
-scooter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 19:07:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA10164
for freebsd-current-outgoing; Thu, 12 Nov 1998 19:07:19 -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 TAA10018
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 19:07:14 -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 WAA18313;
Thu, 12 Nov 1998 22:06:53 -0500 (EST)
Date: Thu, 12 Nov 1998 22:06:52 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: "Richard Seaman, Jr." <lists@tar.com>
cc: "current@freebsd.org" <current@FreeBSD.ORG>
Subject: Re: RFSIGSHARE ready?
In-Reply-To: <199811121741.LAA14562@ns.tar.com>
Message-ID: <Pine.BSF.4.05.9811122204160.17981-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
Would you mind actually trying moving the signal masks out of struct
procsig then? It would be easy, but I don't have time to be testing new
kernels, I've got school to deal with. I'm still thinking about how
exactly I should deal with the stack mmap problem, but so far, I am
doubting it will be problematic at all. When I see that it is problematic
( valid LinuxThreads program using gobs of stack?) I will most definitely
implement a change of behavior for this case.
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
On Thu, 12 Nov 1998, Richard Seaman, Jr. wrote:
> Brian --
>
> I've done some more thinking about making linux threads work in
> linux emulation. Here are some thoughts:
>
> 1) I think you need to take p_sigmask out of your new procsig
> structure and put it back into the proc structure. Linux threads
> does lots of signal mask manipulation, and I'm pretty sure that
> it expects p_sigmask to be "per thread", and not shared among
> all the threads.
>
> 2) linux threads creates stacks for each thread it creates via
> mmap. It decides on where to start allocating them using the
> following algorithm (I think).
>
> It gets the stack pointer of the initial thread,
> figures the initial thread can get by with 2*STACK_SIZE
> bytes (4MB in this case), and then starts allocating
> thread user stacks 2*STACK_SIZE below the initial
> thread stack.
>
> I don't pretend to really understand FreeBSD vm, to the following
> is just a guess on my part. Maybe someone else can shed more
> light on this.
>
> The problem is that FreeBSD dedicates 64MB for a process stack
> (ie. for the initial thread), so that linux threads starts out
> mmaping into the initial thread stack region. I don't know
> exactly what happens at that point, but it doesn't seem to
> be good.
>
> I'm not sure why FreeBSD mmap allows a mmap into the process
> user stack to succeed (but it appears to).
>
> You could consider patching either linux_mmap or the FreeBSD
> mmap to reject attempts to mmap at virtual addresses above
> p->p->vmspace->vm_maxaddr. I haven't tried this, so I don't
> know if it will work.
>
> What this would do to an unmodified linux threads implementation
> would be (I think) that the first 31 or 32 stack addresses it
> tries to create would fail since they are trying to map into
> the initial thread stack. But, after that, mmaps should succeed
> and maybe the addresses will be ok. You'd loose the ability to
> create 31 or 32 threads out of the total 1024 that linux threads
> allows, but that wouldn't be the end of the world.
>
> 3) You need to deal with the fact that linux threads mmaps the
> thread stacks with the MAP_GROWSDOWN option. Your choices would
> appear to be to re-write the FreeBSD mmap syscall to implement
> this feature, or to hack linux_mmap. A hack to linux_mmap that
> might work (but its a bad hack) would be that when linux_mmap
> detects the MAP_GROWSDOWN option it would expand the size
> of the mmap request by STACK_SIZE - INITIAL_STACKSIZE, and
> relocate the address requested down by the same amount.
>
> I haven't tried any of these ideas, so I have no clue if they
> will work.
>
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 19:20:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA11746
for freebsd-current-outgoing; Thu, 12 Nov 1998 19:20:30 -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 TAA11737
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 19:20:19 -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 WAA18437;
Thu, 12 Nov 1998 22:20:00 -0500 (EST)
Date: Thu, 12 Nov 1998 22:20:00 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Mikhail Teterin <mi@aldan.algebra.com>
cc: current@FreeBSD.ORG
Subject: Re: Where can I get the xform (elf version)
In-Reply-To: <199811130147.BAA24474@aldan.algebra.com>
Message-ID: <Pine.BSF.4.05.9811122218590.17981-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
If you have a Motif license, you can recompile it for ELF yourself. If you
have a binary-only license, I do have a set of FreeBSD 3.0-ELF Motif 2.0.0
libraries.
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
On Fri, 13 Nov 1998, Mikhail Teterin wrote:
> Cory Kempf once stated:
> What about Motif? Any ideas?
> -mi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 19:22:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA12040
for freebsd-current-outgoing; Thu, 12 Nov 1998 19:22:24 -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 TAA12030
for <current@FreeBSD.org>; Thu, 12 Nov 1998 19:22:11 -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 WAA18421;
Thu, 12 Nov 1998 22:18:27 -0500 (EST)
Date: Thu, 12 Nov 1998 22:18:27 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Greg Lehey <grog@lemis.com>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Julian Elischer <julian@whistle.com>,
Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <19981112212947.N463@freebie.lemis.com>
Message-ID: <Pine.BSF.4.05.9811122216410.17981-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
The only thing useful that came out of this thread was a few attempts at
humor. The consensus is basically to not worry about it, and don't move
things around anytime soon. The way it is now isn't bad, so it's okay to
leave alone, and any more discussion is a waste, since all possible
avenues have been explored (verbally, as well).
Brian Feldman _ __ ___ ___ ___
green@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
On Thu, 12 Nov 1998, Greg Lehey wrote:
> On Wednesday, 11 November 1998 at 20:20:16 -0800, Jordan K. Hubbard wrote:
> > Can we just end this thread?
>
> Amen.
>
> If anything useful came out if it, would somebody please summarize?
>
> 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 Nov 12 20:28:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA18665
for freebsd-current-outgoing; Thu, 12 Nov 1998 20:28:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18660
for <freebsd-current@freebsd.org>; Thu, 12 Nov 1998 20:28:11 -0800 (PST)
(envelope-from ckempf@singularity.enigami.com)
Received: (from ckempf@localhost)
by singularity.enigami.com (8.9.1/8.9.1) id XAA25780;
Thu, 12 Nov 1998 23:27:51 -0500 (EST)
To: freebsd-current@FreeBSD.ORG
Subject: Kernel doesn't want to compile anymore :-(
From: Cory Kempf <ckempf@enigami.com>
Date: 12 Nov 1998 23:27:51 -0500
Message-ID: <x7sofo43p4.fsf@singularity.enigami.com>
Lines: 173
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
cvsup'd / buildworld / installworld sometime today...
make depend in my kernel directory gives an error:
perl ../../kern/makedevops.pl -c ../../kern/device_if.m
Can't locate File/Basename.pm in @INC (@INC contains: /usr/local/lib/perl5/i386-freebsd/5.00404 /usr/local/lib/perl5 /usr/local/lib/perl5/site_perl/i386-freebsd /usr/local/lib/perl5/site_perl .) at ../../kern/makedevops.pl line 50.
BEGIN failed--compilation aborted at ../../kern/makedevops.pl line 50.
*** Error code 2
Doing a find on "Basename.pm" produces the following:
/usr/libdata/perl/5.00502/File/Basename.pm
/usr/obj/aout/usr/src/gnu/usr.bin/perl/perl/lib/File/Basename.pm
/usr/obj/aout/usr/src/gnu/usr.bin/perl/suidperl/lib/File/Basename.pm
/usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/File/Basename.pm
/usr/obj/elf/usr/src/gnu/usr.bin/perl/suidperl/lib/File/Basename.pm
/usr/src/contrib/perl5/lib/File/Basename.pm
None of which seem to be in the above @INC paths
Unfortunately, my knowledge of perl is pretty minimal...
So, suggestions?
Thanks,
+C
My kernel config file, on the off chance it helps...
#
# SIN
#
machine "i386"
cpu "I686_CPU"
ident SIN
maxusers 32
options INET #InterNETworking
options FFS #Berkeley Fast Filesystem
options NFS #Network Filesystem
options MFS
options MSDOSFS #MSDOS Filesystem
options "CD9660" #ISO 9660 Filesystem
options PROCFS #Process filesystem
options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!]
options UCONSOLE #Allow users to grab the console
options KTRACE #kernel tracing
options SYSVSHM
options DDB
#options BOUNCE_BUFFERS #For ADV controller
options "AHC_ALLOW_MEMIO"
options CONSPEED=115200 #default speed for serial console
options "MSGBUF_SIZE=32768"
config kernel root on da0s1a
controller isa0
controller pci0
controller eisa0
controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fdc0 drive 0
#disk fd1 at fdc0 drive 1
#controller aic0
controller ahc0
controller ahc1
#controller adv0
#controller adv1 at isa? port ? cam irq ? vector adv_isa_intr
#controller bt0
#controller ncr0 at isa? port ? cam irq ? vector adv_isa_intr
controller scbus0 at ahc0 bus 0
controller scbus1 at ahc1 bus 0
#controller scbus2 at ncr0 bus 0
device da0 # direct access: disk
device sa0 # sequential access: tape
device pass0 # passthrough device
#device da0 at scbus0 target 0
#device da8 at scbus1 target 0
#device da9 at scbus1 target 1
#device da10 at scbus1 target 2
#device da11 at scbus1 target 3
#device od0
device cd0
#device pt0
#device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr
# for the Sony CDU31/33A CDROM
#device scd0 at isa? port 0x230 bio
#controller matcd0 at isa? port 0x230 bio
#device wcd0
# syscons is the default console driver, resembling an SCO console
device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr
# Mandatory, don't remove
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr
#device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr
device sio0 at isa? port "IO_COM1" tty irq 4 flags 0x10 vector siointr
device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr
device lpt0 at isa? port? tty irq 7 vector lptintr
device fxp0
device de0
pseudo-device loop
pseudo-device ether
pseudo-device pty 16
pseudo-device bpfilter 4
pseudo-device tun 4
# keep this if you want to be able to continue to use /stand/sysinstall
pseudo-device gzip # Exec gzipped a.out's
#pseudo-device ccd 4 #Concatenated disk driver
options DEVFS
options NETATALK
options "MD5"
options KERNFS
options FFS_ROOT
options PPS_SYNC
# Sound
#controller snd0
#device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 vector pcmintr
#device pcm1 at isa? port ? tty irq 10 drq 1 flags 0x0 vector pcmintr
#device sb0 at isa? port 0x220 irq 5 drq 1
#device sbxvi0 at isa? drq 5
#device sbmidi0 at isa? port 0x330
# mouse
device psm0 at isa? port IO_KBD conflicts tty irq 12 vector psmintr
pseudo-device vn # VNode Driver (turns a file into a device)
options SYSVSEM
options SYSVMSG
#SMP:
options SMP
options APIC_IO
options NCPU=2
options NBUS=3
options NAPIC=1
options NINTR=24
#
# for WINE
#
options USER_LDT
#
# PNP
#
#controller pnp0
--
Thinking of purchasing RAM from the Chip Merchant?
Please read this first: <http://www.enigami.com/~ckempf/chipmerchant.html>
Cory Kempf Macintosh / Unix Consulting & Software Development
ckempf@enigami.com <http://www.enigami.com/~ckempf/>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 22:30:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA29548
for freebsd-current-outgoing; Thu, 12 Nov 1998 22:30: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 WAA29538
for <freebsd-current@FreeBSD.ORG>; Thu, 12 Nov 1998 22:30:28 -0800 (PST)
(envelope-from mark@grondar.za)
Received: from greenpeace.grondar.za (IDENT:oWKjqZioV6T3tjJ2FqyRhPFbqx2zFbnx@greenpeace.grondar.za [196.7.18.132])
by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA03207;
Fri, 13 Nov 1998 08:29:51 +0200 (SAST)
(envelope-from mark@grondar.za)
Received: from grondar.za (IDENT:3QG/Bzm87ys/Y2e6Kl/DnNleh5bBtBI8@localhost [127.0.0.1])
by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id IAA05361;
Fri, 13 Nov 1998 08:29:50 +0200 (SAST)
(envelope-from mark@grondar.za)
Message-Id: <199811130629.IAA05361@greenpeace.grondar.za>
To: Cory Kempf <ckempf@enigami.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Kernel doesn't want to compile anymore :-(
In-Reply-To: Your message of " 12 Nov 1998 23:27:51 EST." <x7sofo43p4.fsf@singularity.enigami.com>
References: <x7sofo43p4.fsf@singularity.enigami.com>
Date: Fri, 13 Nov 1998 08:29:49 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Remove your Perl5 _port_, and let the system perl5 do its thing.
In cleaning out your system, you may break Perl5, so another
make world may be a good idea.
M
Cory Kempf wrote:
> cvsup'd / buildworld / installworld sometime today...
> make depend in my kernel directory gives an error:
>
> perl ../../kern/makedevops.pl -c ../../kern/device_if.m
> Can't locate File/Basename.pm in @INC (@INC contains: /usr/local/lib/perl5/i3
86-freebsd/5.00404 /usr/local/lib/perl5 /usr/local/lib/perl5/site_perl/i386-fre
ebsd /usr/local/lib/perl5/site_perl .) at ../../kern/makedevops.pl line 50.
> BEGIN failed--compilation aborted at ../../kern/makedevops.pl line 50.
> *** Error code 2
>
> Doing a find on "Basename.pm" produces the following:
>
> /usr/libdata/perl/5.00502/File/Basename.pm
> /usr/obj/aout/usr/src/gnu/usr.bin/perl/perl/lib/File/Basename.pm
> /usr/obj/aout/usr/src/gnu/usr.bin/perl/suidperl/lib/File/Basename.pm
> /usr/obj/elf/usr/src/gnu/usr.bin/perl/perl/lib/File/Basename.pm
> /usr/obj/elf/usr/src/gnu/usr.bin/perl/suidperl/lib/File/Basename.pm
> /usr/src/contrib/perl5/lib/File/Basename.pm
>
> None of which seem to be in the above @INC paths
>
> Unfortunately, my knowledge of perl is pretty minimal...
>
> So, suggestions?
>
> Thanks,
>
> +C
>
>
>
> My kernel config file, on the off chance it helps...
>
> #
> # SIN
> #
>
> machine "i386"
> cpu "I686_CPU"
> ident SIN
> maxusers 32
>
> options INET #InterNETworking
> options FFS #Berkeley Fast Filesystem
> options NFS #Network Filesystem
> options MFS
> options MSDOSFS #MSDOS Filesystem
> options "CD9660" #ISO 9660 Filesystem
> options PROCFS #Process filesystem
> options "COMPAT_43" #Compatible with BSD 4.3 [KEEP
THIS!]
> options UCONSOLE #Allow users to grab the consol
e
> options KTRACE #kernel tracing
>
> options SYSVSHM
> options DDB
> #options BOUNCE_BUFFERS #For ADV controller
> options "AHC_ALLOW_MEMIO"
> options CONSPEED=115200 #default speed for serial conso
le
> options "MSGBUF_SIZE=32768"
>
> config kernel root on da0s1a
>
> controller isa0
> controller pci0
> controller eisa0
>
> controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
> disk fd0 at fdc0 drive 0
> #disk fd1 at fdc0 drive 1
>
> #controller aic0
> controller ahc0
> controller ahc1
> #controller adv0
> #controller adv1 at isa? port ? cam irq ? vector adv_isa_intr
> #controller bt0
> #controller ncr0 at isa? port ? cam irq ? vector adv_isa_intr
>
> controller scbus0 at ahc0 bus 0
> controller scbus1 at ahc1 bus 0
> #controller scbus2 at ncr0 bus 0
>
> device da0 # direct access: disk
> device sa0 # sequential access: tape
> device pass0 # passthrough device
>
> #device da0 at scbus0 target 0
> #device da8 at scbus1 target 0
> #device da9 at scbus1 target 1
> #device da10 at scbus1 target 2
> #device da11 at scbus1 target 3
>
> #device od0
>
> device cd0
>
> #device pt0
>
> #device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr
> # for the Sony CDU31/33A CDROM
> #device scd0 at isa? port 0x230 bio
> #controller matcd0 at isa? port 0x230 bio
> #device wcd0
>
> # syscons is the default console driver, resembling an SCO console
> device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr
>
> # Mandatory, don't remove
> device npx0 at isa? port "IO_NPX" irq 13 vector npxintr
>
> #device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr
> device sio0 at isa? port "IO_COM1" tty irq 4 flags 0x10 vec
tor siointr
> device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr
>
> device lpt0 at isa? port? tty irq 7 vector lptintr
>
> device fxp0
> device de0
>
>
> pseudo-device loop
> pseudo-device ether
> pseudo-device pty 16
> pseudo-device bpfilter 4
> pseudo-device tun 4
> # keep this if you want to be able to continue to use /stand/sysinstall
> pseudo-device gzip # Exec gzipped a.out's
> #pseudo-device ccd 4 #Concatenated disk driver
> options DEVFS
> options NETATALK
> options "MD5"
> options KERNFS
> options FFS_ROOT
> options PPS_SYNC
>
> # Sound
> #controller snd0
> #device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 vector pcmintr
> #device pcm1 at isa? port ? tty irq 10 drq 1 flags 0x0 vector pcmintr
> #device sb0 at isa? port 0x220 irq 5 drq 1
> #device sbxvi0 at isa? drq 5
> #device sbmidi0 at isa? port 0x330
>
>
> # mouse
> device psm0 at isa? port IO_KBD conflicts tty irq 12 vector psmintr
>
> pseudo-device vn # VNode Driver (turns a file into a device)
> options SYSVSEM
> options SYSVMSG
>
> #SMP:
> options SMP
> options APIC_IO
> options NCPU=2
> options NBUS=3
> options NAPIC=1
> options NINTR=24
> #
> # for WINE
> #
> options USER_LDT
> #
> # PNP
> #
> #controller pnp0
>
>
>
> --
> Thinking of purchasing RAM from the Chip Merchant?
> Please read this first: <http://www.enigami.com/~ckempf/chipmerchant.html>
>
> Cory Kempf Macintosh / Unix Consulting & Software Development
> ckempf@enigami.com <http://www.enigami.com/~ckempf/>
>
> 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 Thu Nov 12 22:58:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA01636
for freebsd-current-outgoing; Thu, 12 Nov 1998 22:58:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01628
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 22:58:17 -0800 (PST)
(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
by freebsd.dk (8.9.1/8.9.1) id HAA02051;
Fri, 13 Nov 1998 07:57:47 +0100 (CET)
(envelope-from sos)
From: Søren Schmidt <sos@freebsd.dk>
Message-Id: <199811130657.HAA02051@freebsd.dk>
Subject: Re: ATAPI CD/R driver and Mitsumi CR-2600TE
In-Reply-To: <002301be0e91$9b948040$08f19b26@xanadu.lovett.com> from Ade Lovett at "Nov 12, 1998 5:10:15 pm"
To: ade@supernews.net (Ade Lovett)
Date: Fri, 13 Nov 1998 07:57:47 +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 Ade Lovett wrote:
> Hi all,
>
> I recently acquired (at no cost) a Mitsumi CR-2600TE cd burner, and
> plugged it in to my 3.0-CURRENT system to try out the acd driver.
>
> Unfortunately, there appears to be something of a problem.. when the
> burncd script gets around to doing the dd(1) it completely fails with
>
> acd0: rezero failed
>
> I've verified that the unit works on the same machine under Win98 with the
> supplied Adaptec burning software, and I've tried multiple blank disks
> from different vendors, so it's unlikely to be that.
>
> Any suggestions on making this puppy work? Or should I just throw it away?
That drive does apparently not support the rezero cmd. You could use
the stop/start cmd instead. I did get a patch once for that, but it
dissapeared together with my machine lately.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 12 23:06:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA02657
for freebsd-current-outgoing; Thu, 12 Nov 1998 23:06:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m1-60-dbn.dial-up.net [196.34.155.60])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02652
for <current@FreeBSD.ORG>; Thu, 12 Nov 1998 23:06:25 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id JAA08765; Fri, 13 Nov 1998 09:04:36 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199811130704.JAA08765@ceia.nordier.com>
Subject: Re: Problems/questions about boot blocks
In-Reply-To: <19981112165039.32105@ican.net> from Josh Tiefenbach at "Nov 12, 98 04:50:39 pm"
To: josh@ican.net (Josh Tiefenbach)
Date: Fri, 13 Nov 1998 09:04:34 +0200 (SAT)
Cc: 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
Josh Tiefenbach wrote:
> I'm having some problems setting up my machine to dual boot between FreeBSD
> and Win98.
>
> Specifics:
>
> In the machine, there are two 2gig drives hooked up to the onboard ahc
> controller (its an ASUS P2B-S board). I've installed 3.0-RELEASE onto
> the first drive (ID 0), and I've formatted and sys'd the second drive (ID 1)
> with win98.
>
> Problem is, that no matter what I've tried, I havent been unable to get the
> machine to boot from the win98 disk.
>
> When the machine initially boots, I get the
>
> F1: FreeBSD
>
> prompt. Which is kinda odd, since I would have expected that the boot blocks
> would have noted the existance of the second disk. When I try hitting F5 to
> try to force booting off the second disk, I get a "Missing operating system"
> message.
It appears you have boot0 rather than booteasy installed on drive 0.
This doesn't display F5 (though it apparently needs to: a number of
folks seem to expect this).
The message "Missing operating system" is a standard Microsoft error
message. It indicates that the FreeBSD partition manager *is* passing
control to the drive 1 master boot record. However, standard Microsoft
MBRs won't boot from drive 1 only from drive 0. So you need to put
boot0 or booteasy or something similar on drive 1.
> I *think* that I'm using the old boot-blocks, 'cause when I boot into FreeBSD,
> I get the big honking instruction message, and its honoring the directives in
> /boot.config, and firing up /boot/loader
Both the new and the old bootblocks do this. One way to distinguish
them is:
[Old] >> FreeBSD BOOT @ 0x10000 ...
[New] >> FreeBSD/i386 BOOT
> Would using the new boot0 bootblocks help? How would I get them installed?
The standard way to install booteasy is to use a DOS program called
bootinst.com (or maybe bootinst.exe). Anyway, it is available in the
tools directory on CDROMs or ftp.freebsd.org. For boot0, there is a
simple FreeBSD utility at
http://www.freebsd.org/~rnordier/boot0inst-1.0.tar.gz
that does the same thing. You can also use sysinstall.
--
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 Nov 12 23:07:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA02769
for freebsd-current-outgoing; Thu, 12 Nov 1998 23:07:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m1-60-dbn.dial-up.net [196.34.155.60])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02749
for <freebsd-current@FreeBSD.ORG>; Thu, 12 Nov 1998 23:07:34 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id IAA08703; Fri, 13 Nov 1998 08:16:32 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199811130616.IAA08703@ceia.nordier.com>
Subject: Re: disklabel and changing boot blocks
In-Reply-To: <199811130302.TAA00315@mordred.cs.ucla.edu> from Scott Michel at "Nov 12, 98 07:02:11 pm"
To: scottm@cs.ucla.edu (Scott Michel)
Date: Fri, 13 Nov 1998 08:16:31 +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
Scott Michel wrote:
> Sorry if this completely dippy or paranoid, but do you need
> to rerun disklabel each time there's a new boot[12]?
If you want to keep up to date with the latest versions, yes.
Installing the bootblocks only copies them to /boot, it doesn't
replace the active copies.
--
Robert Nordier
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 00:22:58 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA08140
for freebsd-current-outgoing; Fri, 13 Nov 1998 00:22:58 -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 AAA08135
for <current@FreeBSD.ORG>; Fri, 13 Nov 1998 00:22:56 -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 JAA19870;
Fri, 13 Nov 1998 09:22:35 +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 AAA06561;
Fri, 13 Nov 1998 00:25:15 +0100 (MET)
(envelope-from w)
Message-ID: <19981113002514.A6534@panke.de.freebsd.org>
Date: Fri, 13 Nov 1998 00:25:14 +0100
From: Wolfram Schneider <wosch@panke.de.freebsd.org>
To: Andreas Klemm <andreas@klemm.gtn.com>, current@FreeBSD.ORG
Subject: Re: ${MACHINE_ARCH} is still a show stopper in make aout-to-elf-build
References: <19981105085114.A1125@klemm.gtn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <19981105085114.A1125@klemm.gtn.com>; from Andreas Klemm on Thu, Nov 05, 1998 at 08:51:14AM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 1998-11-05 08:51:14 +0100, Andreas Klemm wrote:
> The upgrade process still doesn't work, because MACHINE_ARCH
> isn't defined in -STABLE ;-)
>
> root{540} /usr/src time make aout-to-elf-build | & tee make.log
>
> --------------------------------------------------------------
> Doing an aout buildworld to get an up-to-date set of tools
> --------------------------------------------------------------
> "Makefile.inc1", line 755: Need an operator
> "Makefile.inc1", line 1000: 1 open conditional
> make: fatal errors encountered -- cannot continue
> *** Error code 1
You must check if the variable MACHINE_ARCH is defined before accessing the
variable, e.g.:
.if defined(MACHINE_ARCH) && ${MACHINE_ARCH} == "i386" && ${OBJFORMAT} == "aout"
Wolfram
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 00:36:08 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA09604
for freebsd-current-outgoing; Fri, 13 Nov 1998 00:36:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from echonyc.com (echonyc.com [198.67.15.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09599
for <current@freebsd.org>; Fri, 13 Nov 1998 00:36:07 -0800 (PST)
(envelope-from benedict@echonyc.com)
Received: from localhost by echonyc.com (8.9.1/8.9.1) with SMTP id DAA02110
for <current@freebsd.org>; Fri, 13 Nov 1998 03:35:43 -0500 (EST)
Date: Fri, 13 Nov 1998 03:35:43 -0500 (EST)
From: Snob Art Genre <benedict@echonyc.com>
Reply-To: ben@rosengart.com
To: current@FreeBSD.ORG
Subject: bt errors on boot
Message-ID: <Pine.GSO.4.02.9811130332530.17675-100000@echonyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Upen booting a kernel compiled at 10 pm UTC 11/11, I saw the following
errors, appearing immediately after detection of npx0 and interspersed
through the SCSI drive detection and ffs_mountfs: superblock updated for
soft updates messages.
bt: ccb 0xf4a2d240 - error 4 occured. btstat = 11, sdstat = 0
bt: ccb 0xf4a2d280 - error 4 occured. btstat = 11, sdstat = 0
bt: ccb 0xf4a2d2c0 - error 4 occured. btstat = 11, sdstat = 0
bt: ccb 0xf4a2d200 - error 4 occured. btstat = 0, sdstat = 2
bt: ccb 0xf4a2d340 - error 4 occured. btstat = 11, sdstat = 0
bt: ccb 0xf4a2d300 - error 4 occured. btstat = 0, sdstat = 2
bt: ccb 0xf4a2d380 - error 4 occured. btstat = 0, sdstat = 2
bt: ccb 0xf4a2d300 - error 4 occured. btstat = 0, sdstat = 2
bt: ccb 0xf4a2d300 - error 4 occured. btstat = 0, sdstat = 2
bt: ccb 0xf4a2d380 - error 4 occured. btstat = 0, sdstat = 2
bt: ccb 0xf4a2d380 - error 4 occured. btstat = 0, sdstat = 2
bt: ccb 0xf4a2d380 - error 4 occured. btstat = 0, sdstat = 2
Is this anything to be concerned about?
Ben
"You have your mind on computers, it seems."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 00:59:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA10784
for freebsd-current-outgoing; Fri, 13 Nov 1998 00:59:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cassiopeia.hkstar.com (cassiopeia.hkstar.com [202.82.3.11])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10779
for <freebsd-current@freebsd.org>; Fri, 13 Nov 1998 00:59:49 -0800 (PST)
(envelope-from c5666305@b1.hkstar.com)
Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87])
by cassiopeia.hkstar.com (8.9.1/8.9.1) with ESMTP id QAA29297
for <freebsd-current@freebsd.org>; Fri, 13 Nov 1998 16:59:19 +0800 (HKT)
Received: (from c5666305@localhost)
by b1.hkstar.com (8.8.8/8.8.8) id RAA07317
for freebsd-current@freebsd.org; Fri, 13 Nov 1998 17:01:40 +0800 (HKT)
From: Chan Yiu Wah <c5666305@b1.hkstar.com>
Message-Id: <199811130901.RAA07317@b1.hkstar.com>
Subject: elf version of xforms
To: freebsd-current@FreeBSD.ORG
Date: Fri, 13 Nov 1998 17:01:40 +0800 (HKT)
X-Mailer: ELM [version 2.5 PL0b1]
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,
Thanks for information to obtain the elf version from
http://bragg.phys.uwm.edu/xforms. However I cannot uncompress it.
I have tried the following ways:-
1. tar xvfz bxform-freebsd-elf.tgz
- format violated.
2. gzip -d bxform-freebsd-elf.tgz
- format violated.
Any idea how to fix it.
Thanks.
Clarence
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 01:54:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA16311
for freebsd-current-outgoing; Fri, 13 Nov 1998 01:54:19 -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 BAA16286
for <current@freebsd.org>; Fri, 13 Nov 1998 01:54:16 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2])
by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA15045;
Fri, 13 Nov 1998 09:53:39 GMT
Date: Fri, 13 Nov 1998 09:53:39 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: "Andrew J. Korty" <ajk@physics.purdue.edu>
cc: Alfred Perlstein <bright@hotjobs.com>,
"Jason J. Horton" <jason@intercom.com>, current@FreeBSD.ORG
Subject: Re: Is it soup yet? FreeBSD NFS
In-Reply-To: <Pine.BSF.3.96.981112161525.15875J-100000@poynting.physics.purdue.edu>
Message-ID: <Pine.BSF.4.01.9811130953160.11371-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, 12 Nov 1998, Andrew J. Korty wrote:
> On Thu, 12 Nov 1998, Alfred Perlstein wrote:
>
> > On Thu, 12 Nov 1998, Jason J. Horton wrote:
> >
> > > Everyone seems to be talking about using FreeBSD as an NFS client,
> > > how does FreeBSD do as a NFS server?
> > >
> > > -J
> > >
> >
> > I'm going to be using NFS extensively at home for a while, I'll let you
> > know.
> >
> > Last time I used it, it wasn't the most stable thing. A NFS mounted
> > buildworld crashed the server once, but then worked fine after that.
>
> We've been able to crash FreeBSD 3.0 NFS (both versions 2 and 3)
> servers repeatably by starting KDE on a FreeBSD (any version) client
> that mounts one's home directory off the server. See kern/8515.
>
> Hope this helps ...
I just committed a fix for this one.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 951 1891
Fax: +44 181 381 1039
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 03:18:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA22442
for freebsd-current-outgoing; Fri, 13 Nov 1998 03:18:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from enterprise.synchroline.ru (enterprise.sl.ru [195.16.101.4] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA22422;
Fri, 13 Nov 1998 03:18:44 -0800 (PST)
(envelope-from tarkhil@synchroline.ru)
Received: from enterprise.synchroline.ru (tarkhil@localhost.synchroline.ru [127.0.0.1])
by enterprise.synchroline.ru (8.9.1/8.8.8) with ESMTP id OAA29400;
Fri, 13 Nov 1998 14:19:51 +0300 (MSK)
(envelope-from tarkhil@enterprise.synchroline.ru)
Message-Id: <199811131119.OAA29400@enterprise.synchroline.ru>
X-Mailer: exmh version 2.0.2 2/24/98
To: current@FreeBSD.ORG
cc: net@FreeBSD.ORG
Reply-To: tarkhil@synchroline.ru
Subject: opt_bdg.h and opt_ipdn.h
X-URL: http://freebsd.svib.ru
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 13 Nov 1998 14:19:48 +0300
From: "Alexander B. Povolotsky" <tarkhil@synchroline.ru>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello!
I'm trying to set up DUMMYNET, but I can't find thesefiles neither in patch
nor in -current tree.
Where can I get them?
Alex.
--
Alexander B. Povolotsky, System Administrator
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 04:56:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA02415
for freebsd-current-outgoing; Fri, 13 Nov 1998 04:56:06 -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 EAA02406
for <current@freebsd.org>; Fri, 13 Nov 1998 04:56:02 -0800 (PST)
(envelope-from netchild@wurzelausix.CS.Uni-SB.DE)
Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31])
by uni-sb.de (8.9.0/1998052000) with ESMTP
id NAA09710 for <current@freebsd.org>; Fri, 13 Nov 1998 13:55:34 +0100 (CET)
Received: from wurzelausix.cs.uni-sb.de (xyu4Fx9xeu9cq15PqmoMZE2XVtgR10dD@wurzelausix.cs.uni-sb.de [134.96.247.1])
by cs.uni-sb.de (8.9.0/1998060300) with ESMTP
id NAA16537 for <current@freebsd.org>; Fri, 13 Nov 1998 13:55:34 +0100 (CET)
Received: from wurzelausix.cs.uni-sb.de (IDENT:fm9tGocLwXvE375OYOQ9uFSdwJ/llvBJ@localhost [127.0.0.1])
by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) with ESMTP id NAA08333
for <current@freebsd.org>; Fri, 13 Nov 1998 13:55:26 +0100 (CET)
Message-Id: <199811131255.NAA08333@wurzelausix.cs.uni-sb.de>
Date: Fri, 13 Nov 1998 13:55:22 +0100 (CET)
From: Alexander Leidinger <netchild@wurzelausix.CS.Uni-SB.DE>
Subject: en0 + ed0 + indirect X :(
To: 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,
Setup:
atm over en0 with route to systems of type A (atm_myname)
ethernet over ed0 with route to system of type B (myname)
X -indirect TypeB_host (x_serv)
cvsup: Nov, 12.
Standard kernel:
x_serv tries to open the dtlogin on atm_myname:0, but it can't because
there's no route from systems of type B to the atm interface.
Patched kernel:
Everything works fine (x_serv didn't try to open the display on
atm_myname:0).
Patch:
/sys/i386/i386/autoconf.c
Changing
eisa_configure();
pci_configure();
pnp_configure();
isa_configure();
to
eisa_configure();
isa_configure();
pci_configure();
pnp_configure();
I didn't know why x_serv tries to open the display on atm_myname:0
instead of myname:0. x_serv hasn't an atm interface and myname has a
default route over ed0, but if I patch the kernel as shown it works.
As you guess, I didn't want to patch the kernel everytime I update the
sources.
Someone out there who knows
- why I see such a behavior (perhaps it's a misconfiguration)?
- a solution (if it is a misconfiguration)?
Bye,
Alexander.
--
2^{F_{h+1}-1} z^{F_{h+2}-1} + 2^{F_{h+1}-2} L_{h-1} z^{F_{h+2}}
+ complicated terms + 2^{h-1} z^{2^h - 2} + z^{2^h - 1}
Donald E. Knuth, "The Art of Computer Programming"
http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 05:24:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA05280
for freebsd-current-outgoing; Fri, 13 Nov 1998 05:24:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA05271
for <current@FreeBSD.org>; Fri, 13 Nov 1998 05:24:48 -0800 (PST)
(envelope-from gibbs@narnia.plutotech.com)
Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id GAA19695; Fri, 13 Nov 1998 06:17:41 -0700 (MST)
Date: Fri, 13 Nov 1998 06:17:41 -0700 (MST)
From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Message-Id: <199811131317.GAA19695@narnia.plutotech.com>
To: ben@rosengart.com
cc: current@FreeBSD.ORG
Subject: Re: bt errors on boot
X-Newsgroups: pluto.freebsd.current
In-Reply-To: <Pine.GSO.4.02.9811130332530.17675-100000@echonyc.com>
User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386))
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <Pine.GSO.4.02.9811130332530.17675-100000@echonyc.com> you wrote:
> Upen booting a kernel compiled at 10 pm UTC 11/11, I saw the following
> errors, appearing immediately after detection of npx0 and interspersed
> through the SCSI drive detection and ffs_mountfs: superblock updated for
> soft updates messages.
>
> bt: ccb 0xf4a2d240 - error 4 occured. btstat = 11, sdstat = 0
> bt: ccb 0xf4a2d280 - error 4 occured. btstat = 11, sdstat = 0
> bt: ccb 0xf4a2d2c0 - error 4 occured. btstat = 11, sdstat = 0
> bt: ccb 0xf4a2d200 - error 4 occured. btstat = 0, sdstat = 2
> bt: ccb 0xf4a2d340 - error 4 occured. btstat = 11, sdstat = 0
> bt: ccb 0xf4a2d300 - error 4 occured. btstat = 0, sdstat = 2
> bt: ccb 0xf4a2d380 - error 4 occured. btstat = 0, sdstat = 2
> bt: ccb 0xf4a2d300 - error 4 occured. btstat = 0, sdstat = 2
> bt: ccb 0xf4a2d300 - error 4 occured. btstat = 0, sdstat = 2
> bt: ccb 0xf4a2d380 - error 4 occured. btstat = 0, sdstat = 2
> bt: ccb 0xf4a2d380 - error 4 occured. btstat = 0, sdstat = 2
> bt: ccb 0xf4a2d380 - error 4 occured. btstat = 0, sdstat = 2
>
> Is this anything to be concerned about?
Nope. It's just some logging that I inadvertantly left enabled
in my last checkin. Should be silenced now assuming you don't
boot with the -v flag.
--
Justin
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 08:01:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA23277
for freebsd-current-outgoing; Fri, 13 Nov 1998 08:01:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sphinx.lovett.com (sphinx.lovett.com [38.155.241.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23272
for <current@freebsd.org>; Fri, 13 Nov 1998 08:01:22 -0800 (PST)
(envelope-from ade@supernews.net)
Received: from [38.155.241.8] (helo=xanadu)
by sphinx.lovett.com with smtp (Exim 2.05 #1)
id 0zeLc1-0005ay-00; Fri, 13 Nov 1998 09:58:17 -0600
From: "Ade Lovett" <ade@supernews.net>
To: "=?iso-8859-1?Q?S=F8ren_Schmidt?=" <sos@freebsd.dk>
Cc: <current@FreeBSD.ORG>
Subject: RE: ATAPI CD/R driver and Mitsumi CR-2600TE
Date: Fri, 13 Nov 1998 09:56:11 -0600
Message-ID: <003001be0f1e$22830540$08f19b26@xanadu.lovett.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26
In-Reply-To: <199811130657.HAA02051@freebsd.dk>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> That drive does apparently not support the rezero cmd. You could use
> the stop/start cmd instead. I did get a patch once for that, but it
> dissapeared together with my machine lately.
Ok. What does rezero actually do? Can I simply add in a hack to
simulate it with:
acd_request_wait( ..., ATAPI_START_STOP, 1,0,0,0,0,0,0,0,0,0,0 );
acd_request_wait( ..., ATAPI_START_STOP, 1,0,0,1,0,0,0,0,0,0,0 );
ie: doing the equivalent of the CDIOCSTOP, CDIOCSTART ioctls?
-aDe
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 08:03:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA23545
for freebsd-current-outgoing; Fri, 13 Nov 1998 08:03:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ifi.uio.no (ifi.uio.no [129.240.64.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23526
for <current@FreeBSD.ORG>; Fri, 13 Nov 1998 08:03:13 -0800 (PST)
(envelope-from dag-erli@ifi.uio.no)
Received: from heptifili.ifi.uio.no (2602@heptifili.ifi.uio.no [129.240.65.12])
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with SMTP id RAA08962;
Fri, 13 Nov 1998 17:02:41 +0100 (MET)
Received: from localhost (dag-erli@localhost) by heptifili.ifi.uio.no ; Fri, 13 Nov 1998 16:02:40 GMT
Mime-Version: 1.0
To: "Daniel O'Connor" <doconnor@gsoft.com.au>
Cc: David Wolfskill <dhw@whistle.com>, current@FreeBSD.ORG
Subject: Re: StarOffice-5.0...
References: <XFMail.981113110056.doconnor@gsoft.com.au>
Organization: University of Oslo, Department of Informatics
X-url: http://www.stud.ifi.uio.no/~dag-erli/
X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list
X-disclaimer-1: The views expressed in this article are mine alone, and do
X-disclaimer-2: not necessarily coincide with those of any organisation or
X-disclaimer-3: company with which I am or have been affiliated.
X-Stop-Spam: http://www.cauce.org/
From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= )
Date: 13 Nov 1998 17:02:32 +0100
In-Reply-To: "Daniel O'Connor"'s message of "Fri, 13 Nov 1998 11:00:56 +1030 (CST)"
Message-ID: <xzpbtmbins7.fsf@heptifili.ifi.uio.no>
Lines: 15
X-Mailer: Gnus v5.5/Emacs 19.34
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id IAA23538
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"Daniel O'Connor" <doconnor@gsoft.com.au> writes:
> On 12-Nov-98 David Wolfskill wrote:
> > That may well be useful for many purposes. It's not at all obvious that
> > it's useful for what I'm trying to do. So far, looking at
> > /var/run/dmesg.boot comes closest that I've been able to find, but
> > there's very little there about the video card(s?), for example.
> And what irq's it uses are going to be any better?
> IMHO the only way you could do that would be to read the X output..
What's the point anyway? If it's critical it probably doesn't have (or
need) a graphics adapter worthy of the name.
DES
--
Dag-Erling Smørgrav - dag-erli@ifi.uio.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 08:06:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA24067
for freebsd-current-outgoing; Fri, 13 Nov 1998 08:06:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23921
for <freebsd-current@freebsd.org>; Fri, 13 Nov 1998 08:05:46 -0800 (PST)
(envelope-from cejkar@dcse.fee.vutbr.cz)
Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12])
by boco.fee.vutbr.cz (8.9.1/8.9.1) with ESMTP id RAA07804
for <freebsd-current@freebsd.org>; Fri, 13 Nov 1998 17:04:48 +0100 (CET)
Received: (from cejkar@localhost)
by kazi.dcse.fee.vutbr.cz (8.8.8/8.8.8) id RAA08265
for freebsd-current@freebsd.org; Fri, 13 Nov 1998 17:04:46 +0100 (CET)
From: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>
Message-Id: <199811131604.RAA08265@kazi.dcse.fee.vutbr.cz>
Subject: Re: Is it soup yet? FreeBSD NFS
To: freebsd-current@FreeBSD.ORG (freebsd-current@freebsd.org)
Date: Fri, 13 Nov 1998 17:04:46 +0100 (CET)
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
> > Everyone seems to be talking about using FreeBSD as an NFS client,
> > how does FreeBSD do as a NFS server?
> >
> > -J
> >
>
> I'm going to be using NFS extensively at home for a while, I'll let you
> know.
>
> Last time I used it, it wasn't the most stable thing. A NFS mounted
> buildworld crashed the server once, but then worked fine after that.
>
> - -Alfred
We have long-time problems (not critical) with NFS server running
on FreeBSD 2.2.6/2.2.7/3.0 against Solaris 2.5/2.6 clients there.
Our problem:
FreeBSD: NFS server without any special parameters.
Solaris: NFS client without any special parameters.
Example - working on Solaris above mounted filesystem from FreeBSD:
$ gzcat less-332.tar.gz | tar xvf - # This creates 74 files in
# directory less-332
$ rm -r less-332 # This _leaves_ 43 files!
rm: Unable to remove directory less-332: File exists
$ rm -r less-332 # This _still leaves_ 15 files!
rm: Unable to remove directory less-332: File exists
$ rm -r less-332 # Uff, directory is removed now...
I think, problem is in different versions (NFSv2 vs. NFSv3) - but it
looks very trivial (?). If I mount NFS exported filesystem (exports
FreeBSD) on Solaris with option "vers=2" (it says "use NFSv2"),
problems disappear. But we are using cachefs (cached filesystem) over
NFS with automounting feature and we have no change to say "cachefs,
mount NFS filesystem with 'vers=2' option". There isn't any parameter
for this on Solaris...
I have tried to use "mountd -2" on FreeBSD server part, but it
caused Solaris hangs...
--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--
Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar)
Technical University of Brno, Faculty of El. Engineering and Comp. Science
Bozetechova 2, 612 66 Brno, Czech Republic
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 08:43:08 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA00477
for freebsd-current-outgoing; Fri, 13 Nov 1998 08:43:08 -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 IAA00454
for <current@freebsd.org>; Fri, 13 Nov 1998 08:42:54 -0800 (PST)
(envelope-from geoffb@gti.noc.demon.net)
Received: by server.noc.demon.net; id QAA02225; Fri, 13 Nov 1998 16:42:20 GMT
Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2)
id xmab02208; Fri, 13 Nov 98 16:42:09 GMT
Received: (from geoffb@localhost)
by gti.noc.demon.net (8.8.8/8.8.8) id QAA19674;
Fri, 13 Nov 1998 16:42:06 GMT
From: Geoff Buckingham <geoffb@gti.noc.demon.net>
Message-Id: <199811131642.QAA19674@gti.noc.demon.net>
Subject: Re: DEC Multia support
In-Reply-To: <Pine.BSF.4.01.9811122218470.11371-100000@herring.nlsystems.com> from Doug Rabson at "Nov 12, 98 10:20:26 pm"
To: dfr@nlsystems.com (Doug Rabson)
Date: Fri, 13 Nov 1998 16:42:06 +0000 (GMT)
Cc: current@FreeBSD.ORG
Reply-To: geoffb@demon.net
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
> On Thu, 12 Nov 1998, Geoff Buckingham wrote:
>
> > > On Thu, 12 Nov 1998, Geoff Buckingham wrote:
> > >
> > > >
> > > > How well are the onboard IDE/floppy/ethernet of the Multia supported in
> > > > current at the moment?
> > >
> > > Ethernet should work. Floppy will work when I find time to port the
> > > floppy driver over. IDE will probably have to wait until the new atapi
> > > code is ready.
> > >
> >
> > Given the above is my best route to installing FreeBSD to start with
> > NetBSD and migrate?
>
> If you have SCSI disks, then the best route is to install using the floppy
> images from the regular snapshots. We can boot from a floppy without
> problems. There isn't a floppy driver to use after boot yet though.
>
>
Sorry I'm not with the machine now so cant experiment. Do I not need a
2.8MB floppy for the above to work? (The above seems to imply booting
kern.flp will result in a kernel that can't read its mfs. Please
forgive me if I'm missing something.
If i dd the boot.flp onto a pcmcia flash could I boot from that?
Or boot kern.flp from floppy and take mfsroot.gz from the flash?
--
GeoffB
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 10:57:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA14950
for freebsd-current-outgoing; Fri, 13 Nov 1998 10:57:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14943
for <current@FreeBSD.ORG>; Fri, 13 Nov 1998 10:57:30 -0800 (PST)
(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
by freebsd.dk (8.9.1/8.9.1) id TAA03099;
Fri, 13 Nov 1998 19:54:46 +0100 (CET)
(envelope-from sos)
From: Søren Schmidt <sos@freebsd.dk>
Message-Id: <199811131854.TAA03099@freebsd.dk>
Subject: Re: ATAPI CD/R driver and Mitsumi CR-2600TE
In-Reply-To: <003001be0f1e$22830540$08f19b26@xanadu.lovett.com> from Ade Lovett at "Nov 13, 1998 9:56:11 am"
To: ade@supernews.net (Ade Lovett)
Date: Fri, 13 Nov 1998 19:54:46 +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 Ade Lovett wrote:
> > That drive does apparently not support the rezero cmd. You could use
> > the stop/start cmd instead. I did get a patch once for that, but it
> > dissapeared together with my machine lately.
>
> Ok. What does rezero actually do? Can I simply add in a hack to
> simulate it with:
>
> acd_request_wait( ..., ATAPI_START_STOP, 1,0,0,0,0,0,0,0,0,0,0 );
> acd_request_wait( ..., ATAPI_START_STOP, 1,0,0,1,0,0,0,0,0,0,0 );
>
> ie: doing the equivalent of the CDIOCSTOP, CDIOCSTART ioctls?
IIRC yes.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 12:16:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA23803
for freebsd-current-outgoing; Fri, 13 Nov 1998 12:16:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23795
for <freebsd-current@freebsd.org>; Fri, 13 Nov 1998 12:16:49 -0800 (PST)
(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id PAA03864
for <freebsd-current@freebsd.org>; Fri, 13 Nov 1998 15:16:26 -0500 (EST)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.1/8.9.1) id PAA02406;
Fri, 13 Nov 1998 15:16:26 -0500 (EST)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 13 Nov 1998 15:16:25 -0500 (EST)
To: freebsd-current@FreeBSD.ORG
Subject: nfs_rename() panic
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <13900.36889.417269.577335@grasshopper.cs.duke.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'm getting a 100% reproducible panic in nfs_rename. This is on a
system with sources cvsupped this morning about 10am EST. NFS is
compiled in statically, not an LKM. The new access caching stuff is
off. This panic does not happen in a kernel built from 1 week old
sources.
The panic happens when trn renames .newsrc in a filesystem mounted via
NFSv3/tcp from a Solaris 2.5 server.
I've appended a partial stack trace. The problem seems to be that
fvp->v_data is somehow becoming NULL.
Cheers,
Drew
------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
Duke University Email: gallatin@cs.duke.edu
Department of Computer Science Phone: (919) 660-6590
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x7c
fault code = supervisor read, page not present
instruction pointer = 0x8:0xf01b0384
stack pointer = 0x10:0xf65f6e78
frame pointer = 0x10:0xf65f6e90
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 366 (trn)
interrupt mask =
syncing disks... 8 8 3 done
<...>
#8 0xf01f021c in trap_pfault (frame=0xf65f6e3c, usermode=0)
at ../../i386/i386/trap.c:772
#9 0xf01efe6f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -161754304,
tf_esi = 0, tf_ebp = -161517936, tf_isp = -161517980, tf_ebx = 0,
tf_edx = -161475840, tf_ecx = -260659200, tf_eax = -161452960,
tf_trapno = 12, tf_err = 0, tf_eip = -266665084, tf_cs = 8,
tf_eflags = 66199, tf_esp = -161754304, tf_ss = -161517836})
at ../../i386/i386/trap.c:396
#10 0xf01b0384 in nfs_rename (ap=0xf65f6eb0) at ../../nfs/nfs_vnops.c:1676
#11 0xf016b436 in rename (p=0xf657b340, uap=0xf65f6f94) at vnode_if.h:583
(kgdb) frame 10
#10 0xf01b0384 in nfs_rename (ap=0xf65f6eb0) at ../../nfs/nfs_vnops.c:1676
1676 VTONFS(fvp)->n_modestamp = 0;
(kgdb) p fvp->v_data
$1 = (void *) 0x0
(kgdb) p fvp
$2 = (struct vnode *) 0xf6601300
(kgdb) p &fvp->v_data
$3 = (void **) 0xf660137c
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 12:53:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA27692
for freebsd-current-outgoing; Fri, 13 Nov 1998 12:53:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from myrddin.demon.co.uk (myrddin.demon.co.uk [158.152.54.180])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27687
for <freebsd-current@freebsd.org>; Fri, 13 Nov 1998 12:53:26 -0800 (PST)
(envelope-from dom@myrddin.demon.co.uk)
Received: from localhost (myrddin.demon.co.uk) [127.0.0.1]
by myrddin.demon.co.uk with esmtp (Exim 1.92 #1)
id 0zeQBs-0001XF-00; Fri, 13 Nov 1998 20:51:36 +0000
To: Chan Yiu Wah <c5666305@b1.hkstar.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: elf version of xforms
References: <199811130901.RAA07317@b1.hkstar.com>
From: Dom Mitchell <dom@myrddin.demon.co.uk>
In-Reply-To: Chan Yiu Wah's message of "Fri, 13 Nov 1998 17:01:40 +0800 (HKT)"
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Date: Fri, 13 Nov 1998 20:51:35 +0000
Message-Id: <E0zeQBs-0001XF-00.qmail@myrddin.demon.co.uk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Chan Yiu Wah <c5666305@b1.hkstar.com> writes:
> Thanks for information to obtain the elf version from
> http://bragg.phys.uwm.edu/xforms. However I cannot uncompress it.
>
> I have tried the following ways:-
>
> 1. tar xvfz bxform-freebsd-elf.tgz
> - format violated.
>
> 2. gzip -d bxform-freebsd-elf.tgz
> - format violated.
>
> Any idea how to fix it.
Have you tried "file bxform-freebsd-elf.tgz" to see what that makes of
it?
--
``Bernstein versus Venema Celebrity Deathmatch: I see a great need.'' -- MR
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 13:51:08 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA06691
for freebsd-current-outgoing; Fri, 13 Nov 1998 13:51:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from sphinx.lovett.com (sphinx.lovett.com [38.155.241.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06684
for <current@freebsd.org>; Fri, 13 Nov 1998 13:51:03 -0800 (PST)
(envelope-from ade@supernews.net)
Received: from [38.155.241.8] (helo=xanadu)
by sphinx.lovett.com with smtp (Exim 2.05 #1)
id 0zeR3g-0005pI-00; Fri, 13 Nov 1998 15:47:12 -0600
From: "Ade Lovett" <ade@supernews.net>
To: "=?iso-8859-1?Q?S=F8ren_Schmidt?=" <sos@freebsd.dk>
Cc: <current@FreeBSD.ORG>
Subject: RE: ATAPI CD/R driver and Mitsumi CR-2600TE
Date: Fri, 13 Nov 1998 15:45:03 -0600
Message-ID: <005601be0f4e$df1df220$08f19b26@xanadu.lovett.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26
In-Reply-To: <199811131854.TAA03099@freebsd.dk>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Ok. What does rezero actually do? Can I simply add in a hack to
> > simulate it with:
> >
> > acd_request_wait( ..., ATAPI_START_STOP, 1,0,0,0,0,0,0,0,0,0,0 );
> > acd_request_wait( ..., ATAPI_START_STOP, 1,0,0,1,0,0,0,0,0,0,0 );
> >
> > ie: doing the equivalent of the CDIOCSTOP, CDIOCSTART ioctls?
>
> IIRC yes.
Hmm.. well, I tried that.. it failed on the first acd_request_wait
(for the CDIOCSTOP equivalent), left the disk spinning inside the drive,
and I couldn't get the disk out unless I halted the machine and hit
the physical eject button whilst the machine was at the BIOS.
-aDe
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 14:54:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA14887
for freebsd-current-outgoing; Fri, 13 Nov 1998 14:54:51 -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 OAA14882
for <freebsd-current@FreeBSD.ORG>; Fri, 13 Nov 1998 14:54:50 -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 OAA00889;
Fri, 13 Nov 1998 14:53:07 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811132253.OAA00889@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Andrew Gallatin <gallatin@cs.duke.edu>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: nfs_rename() panic
In-reply-to: Your message of "Fri, 13 Nov 1998 15:16:25 EST."
<13900.36889.417269.577335@grasshopper.cs.duke.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 13 Nov 1998 14:53:07 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> I'm getting a 100% reproducible panic in nfs_rename. This is on a
> system with sources cvsupped this morning about 10am EST. NFS is
> compiled in statically, not an LKM. The new access caching stuff is
> off. This panic does not happen in a kernel built from 1 week old
> sources.
>
> The panic happens when trn renames .newsrc in a filesystem mounted via
> NFSv3/tcp from a Solaris 2.5 server.
>
> I've appended a partial stack trace. The problem seems to be that
> fvp->v_data is somehow becoming NULL.
Weird. I can't work out why the nfsnode would have been revoked at
that point, but it looks like it must have. There are some other bugs
in the code though, as tvp may be NULL if it was open and has been
sillyrenamed. I'll add some sanity checking, but it would be useful if
you could check that it's definitely fvp->v_data that's NULL.
Thanks for the report.
> Cheers,
>
> Drew
> ------------------------------------------------------------------------------
> Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
> Duke University Email: gallatin@cs.duke.edu
> Department of Computer Science Phone: (919) 660-6590
>
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x7c
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xf01b0384
> stack pointer = 0x10:0xf65f6e78
> frame pointer = 0x10:0xf65f6e90
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, def32 1, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 366 (trn)
> interrupt mask =
>
> syncing disks... 8 8 3 done
> <...>
> #8 0xf01f021c in trap_pfault (frame=0xf65f6e3c, usermode=0)
> at ../../i386/i386/trap.c:772
> #9 0xf01efe6f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -161754304,
> tf_esi = 0, tf_ebp = -161517936, tf_isp = -161517980, tf_ebx = 0,
> tf_edx = -161475840, tf_ecx = -260659200, tf_eax = -161452960,
> tf_trapno = 12, tf_err = 0, tf_eip = -266665084, tf_cs = 8,
> tf_eflags = 66199, tf_esp = -161754304, tf_ss = -161517836})
> at ../../i386/i386/trap.c:396
> #10 0xf01b0384 in nfs_rename (ap=0xf65f6eb0) at ../../nfs/nfs_vnops.c:1676
> #11 0xf016b436 in rename (p=0xf657b340, uap=0xf65f6f94) at vnode_if.h:583
>
> (kgdb) frame 10
> #10 0xf01b0384 in nfs_rename (ap=0xf65f6eb0) at ../../nfs/nfs_vnops.c:1676
> 1676 VTONFS(fvp)->n_modestamp = 0;
> (kgdb) p fvp->v_data
> $1 = (void *) 0x0
> (kgdb) p fvp
> $2 = (struct vnode *) 0xf6601300
> (kgdb) p &fvp->v_data
> $3 = (void **) 0xf660137c
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
--
\\ 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 Nov 13 15:02:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA16256
for freebsd-current-outgoing; Fri, 13 Nov 1998 15:02: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 PAA16249
for <current@FreeBSD.ORG>; Fri, 13 Nov 1998 15:02:39 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id OAA15313;
Fri, 13 Nov 1998 14:49:26 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdg15302; Fri Nov 13 22:49:16 1998
Date: Fri, 13 Nov 1998 14:48:39 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Brian Feldman <green@unixhelp.org>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
Peter Wemm <peter@netplex.com.au>, Mike Smith <mike@smith.net.au>,
current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
In-Reply-To: <Pine.BSF.4.05.9811122146120.17981-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.3.95.981113144748.19321F-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, 12 Nov 1998, Brian Feldman wrote:
> On Wed, 11 Nov 1998, Julian Elischer wrote:
> >
> > the existing bootblocks predate "Boot.conf"
>
> Yes. They do not predate boot.config.
in context.. the existing bootblocks on all our machines in the field
predate boot.config
>
> >
> > >
> > > Cheers,
> > > Brian Feldman
> > >
> > >
> >
> >
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 13 15:59:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA23178
for freebsd-current-outgoing; Fri, 13 Nov 1998 15:59:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA23155
for <freebsd-current@FreeBSD.ORG>; Fri, 13 Nov 1998 15:58:53 -0800 (PST)
(envelope-from shimon@simon-shapiro.org)
Received: (qmail 14997 invoked by uid 1000); 14 Nov 1998 01:02:26 -0000
Message-ID: <XFMail.981113200226.shimon@simon-shapiro.org>
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: <199811132253.OAA00889@dingo.cdrom.com>
Date: Fri, 13 Nov 1998 20:02:26 -0500 (EST)
X-Face: (&r=uR0&yvh>h^ZL4"-T<Ako6fc!xyO!<qETO3]"NFbiV!}=/kj5G1L>H61PD}/|Y'~58Z#
Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'<b{Ioa^9\-Z$3!Z7-
;\X0`\'JZI~c>\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+
O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc?
Reply-To: shimon@simon-shapiro.org
Organization: The Simon Shapiro Foundation
From: Simon Shapiro <shimon@simon-shapiro.org>
To: Mike Smith <mike@smith.net.au>
Subject: Re: nfs_rename() panic
Cc: freebsd-current@FreeBSD.ORG, Andrew Gallatin <gallatin@cs.duke.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Smith, On 13-Nov-98 you wrote:
> >
> > I'm getting a 100% reproducible panic in nfs_rename. This is on a
> > system with sources cvsupped this morning about 10am EST. NFS is
> > compiled in statically, not an LKM. The new access caching stuff is
> > off. This panic does not happen in a kernel built from 1 week old
> > sources.
> >
> > The panic happens when trn renames .newsrc in a filesystem mounted via
> > NFSv3/tcp from a Solaris 2.5 server.
> >
> > I've appended a partial stack trace. The problem seems to be that
> > fvp->v_data is somehow becoming NULL.
>
> Weird. I can't work out why the nfsnode would have been revoked at
> that point, but it looks like it must have. There are some other bugs
> in the code though, as tvp may be NULL if it was open and has been
> sillyrenamed. I'll add some sanity checking, but it would be useful if
> you could check that it's definitely fvp->v_data that's NULL.
I am getting essentially the same result on nickel (alpha) using nomis
(i386) as NFS server. Any make activity does that.
Simon
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 01:05:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA26563
for freebsd-current-outgoing; Sat, 14 Nov 1998 01:05:59 -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 BAA26557
for <current@freebsd.org>; Sat, 14 Nov 1998 01:05:56 -0800 (PST)
(envelope-from dfr@nlsystems.com)
Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2])
by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA21638;
Sat, 14 Nov 1998 09:05:49 GMT
Date: Sat, 14 Nov 1998 09:05:49 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: geoffb@demon.net
cc: current@FreeBSD.ORG
Subject: Re: DEC Multia support
In-Reply-To: <199811131642.QAA19674@gti.noc.demon.net>
Message-ID: <Pine.BSF.4.01.9811140904161.11371-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, 13 Nov 1998, Geoff Buckingham wrote:
> > On Thu, 12 Nov 1998, Geoff Buckingham wrote:
> >
> > > > On Thu, 12 Nov 1998, Geoff Buckingham wrote:
> > > >
> > > > >
> > > > > How well are the onboard IDE/floppy/ethernet of the Multia supported in
> > > > > current at the moment?
> > > >
> > > > Ethernet should work. Floppy will work when I find time to port the
> > > > floppy driver over. IDE will probably have to wait until the new atapi
> > > > code is ready.
> > > >
> > >
> > > Given the above is my best route to installing FreeBSD to start with
> > > NetBSD and migrate?
> >
> > If you have SCSI disks, then the best route is to install using the floppy
> > images from the regular snapshots. We can boot from a floppy without
> > problems. There isn't a floppy driver to use after boot yet though.
> >
> >
> Sorry I'm not with the machine now so cant experiment. Do I not need a
> 2.8MB floppy for the above to work? (The above seems to imply booting
> kern.flp will result in a kernel that can't read its mfs. Please
> forgive me if I'm missing something.
>
> If i dd the boot.flp onto a pcmcia flash could I boot from that?
> Or boot kern.flp from floppy and take mfsroot.gz from the flash?
I think you can put mfsroot.gz on one (UFS formatted) floppy and use
kern.flp to boot with. I haven't actually tried this since I can't write
floppies at the moment for various reasons.
--
Doug Rabson Mail: dfr@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 951 1891
Fax: +44 181 381 1039
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 01:26:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA27789
for freebsd-current-outgoing; Sat, 14 Nov 1998 01:26:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gw.start.nl (gw.start.nl [193.67.139.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27784
for <current@freebsd.org>; Sat, 14 Nov 1998 01:26:31 -0800 (PST)
(envelope-from ruigrjer@start.nl)
Received: from start.nl (mail.start.nl [172.16.0.32])
by gw.start.nl (8.8.7/8.8.7) with SMTP id KAA26648
for <current@freebsd.org>; Sat, 14 Nov 1998 10:26:02 +0100 (CET)
(envelope-from ruigrjer@start.nl)
Received: from HOOFDKANTOOR_START-Message_Server by start.nl
with Novell_GroupWise; Sat, 14 Nov 1998 10:28:06 +0100
Message-Id: <s64d5b36.007@start.nl>
X-Mailer: Novell GroupWise 5.2
Date: Sat, 14 Nov 1998 10:13:52 +0100
From: "Jeroen Ruigrok van der Werven" <ruigrjer@start.nl>
To: current@FreeBSD.ORG
Subject: Ick, Help! Booting problem?
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA27785
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi guys,
when I woke up this morning I wanted to dial in to my ISP to get my mail. So I had ppp running in one window and just did a dial ISP. Nothing happened. I looked at all the connectors, nothing weird. So I 'quit'ted ppp and then started it again. Curiously enough I mentioned that not enough inodes were available.
This has never happened before, so I thought (Windows 95 thinking, I admit), well let's reboot the sucker then. OK, it all detected the devices and other things again, but at the point where it was supposed to come up with the login: prompt, I got /stand/sysinstall.
OK, I thought, could be a glitch in CURRENT, so I tried rebooting with -s and that got me the same /stand/sysinstall! Also when I tried to 'Exit Install' I never got to rebooting, it just caught a lot of SIG 11's.
Anyone have any idea how to solve this, as I am unable to use my FreeBSD box as of now.
For information, this is the same setup I have been using for about 2 weeks now, no changes in the configuration on either hardware or software level, just a 'make world' on the 11th of November.
Could I use a bootdisk to get to my partitions? But even if I do, I have no idea where the problem might lie...
Thanks in advance guys,
Jeroen Ruigrok van der Werven
Infrastructure & Networks Start
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 02:23:58 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA00279
for freebsd-current-outgoing; Sat, 14 Nov 1998 02:23:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pc-micha.mc.hp.com (dialin-stg3-130.arcor-ip.de [145.253.74.130])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00263
for <current@freebsd.org>; Sat, 14 Nov 1998 02:23:21 -0800 (PST)
(envelope-from michaelc@bbn.hp.com)
Received: from localhost (michaelc@localhost)
by pc-micha.mc.hp.com (8.9.1/8.9.1) with ESMTP id LAA00436
for <current@freebsd.org>; Sat, 14 Nov 1998 11:23:14 +0100 (MET)
(envelope-from michaelc@bbn.hp.com)
X-Authentication-Warning: pc-micha.mc.hp.com: michaelc owned process doing -bs
Date: Sat, 14 Nov 1998 11:23:14 +0100 (MET)
From: Michael Class <michaelc@bbn.hp.com>
X-Sender: michaelc@pc-micha.mc.hp.com
Reply-To: michael_class@gmx.net
To: current@FreeBSD.ORG
Subject: SMP-System panics after recent ffs_alloc changes
Message-ID: <Pine.BSF.4.05.9811141122300.432-100000@pc-micha.mc.hp.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello,
the recent changes in vfs_cluster.c, buf.h and ffs_alloc.c cause a
panic on my SMP-System.
This is the commitlog of the changes:
dg 1998/11/12 17:01:45 PST
Modified files:
sys/kern vfs_cluster.c
sys/sys buf.h
sys/ufs/ffs ffs_alloc.c
Log:
Restored the "reallocblks" code to its former glory. What this does is
basically do a on-the-fly defragmentation of the FFS filesystem, changing
file block allocations to make them contiguous. Thanks to Kirk McKusick
for providing hints on what needed to be done to get this working.
Revision Changes Path
1.72 +4 -15 src/sys/kern/vfs_cluster.c
1.61 +15 -1 src/sys/sys/buf.h
1.54 +4 -14 src/sys/ufs/ffs/ffs_alloc.c
Backing out these changes solves the problem.
The panic is"ffs_blkfree: bad size"
mp_lock=01000001; cpuid=1; lapic_id=01000000
This is the Stacktrace:
#9 0xf014b8ab in panic (fmt=0xf02340b1 "ffs_blkfree: bad size")
at ../../kern/kern_shutdown.c:428
#10 0xf01cd75a in ffs_blkfree (ip=0xf0b94600, bno=231, size=8192)
at ../../ufs/ffs/ffs_alloc.c:1300
#11 0xf01cc0b4 in ffs_reallocblks (ap=0xf6573e14)
at ../../ufs/ffs/ffs_alloc.c:523
#12 0xf01692df in cluster_write (bp=0xf34eb208, filesize=3842048)
at vnode_if.h:1035
#13 0xf01d2ee7 in ffs_write (ap=0xf6573eec)
at ../../ufs/ufs/ufs_readwrite.c:368
#14 0xf0172be7 in vn_write (fp=0xf0b87600, uio=0xf6573f30, cred=0xf0ba9600)
at vnode_if.h:331
#15 0xf0153b0a in write (p=0xf64f1a80, uap=0xf6573f84)
at ../../kern/sys_generic.c:270
#16 0xf01fd53b in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 134701056,
tf_esi = 134600264, tf_ebp = -272642528, tf_isp = -162054188,
tf_ebx = 671950492, tf_edx = 134600264, tf_ecx = 0, tf_eax = 4,
tf_trapno = 7, tf_err = 2, tf_eip = 671702536, tf_cs = 31,
tf_eflags = 518, tf_esp = -272642552, tf_ss = 39})
at ../../i386/i386/trap.c:1031
#17 0xf01ed02c in Xint0x80_syscall ()
The panic is reproducable with a make -j4 world. I do have a dump!
The System is a Gigabyte SMP-MB 2x 350Mhz P-II, 128MB-RAM.
Here is the output of dmesg:
Copyright (c) 1992-1998 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 3.0-CURRENT #0: Fri Nov 13 15:29:46 MET 1998
michaelc@pc-micha.mc.hp.com:/usr/src/sys/compile/MCSMP
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium II (quarter-micron) (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,CMOV,PAT,PSE36,MMX,<b24>>
real memory = 134217728 (131072K bytes)
config> quit
avail memory = 127606784 (124616K bytes)
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
Preloaded elf kernel "kernel" at 0xf02c1000.
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 255 on pci0.7.2
chip4: <Intel 82371AB Power management controller> rev 0x02 on pci0.7.3
vga0: <Matrox MGA 2164W graphics accelerator> rev 0x00 int a irq 16 on pci0.8.0
ed1: <NE2000 PCI Ethernet (Winbond W89C940)> rev 0x39 int a irq 17 on pci0.9.0
ed1: address 90:00:30:00:52:54, type NE2000 (16 bit)
ahc0: <Adaptec aic7895 Ultra SCSI adapter> rev 0x04 int a irq 16 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 16 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 PnP devices:
CSN 1 Vendor ID: CTL0048 [0x48008c0e] Serial 0x00044475 Comp ID: PNP0600 [0x0006d041]
pcm1 (SB16pnp <SB16 PnP> sn 0x00044475) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
ed0 not found at 0x280
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
sio2 at 0x3e8-0x3ef irq 9 on isa
sio2: type 16550A
ppc: parallel port found at 0x378
ppc0 at 0x378 irq 7 on isa
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
nlpt0: <generic printer> on ppbus 0
nlpt0: Interrupt-driven port
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
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via pin 2
IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry
Waiting 10 seconds for SCSI devices to settle
SMP: AP CPU #1 Launched!
sa0 at ahc0 bus 0 target 4 lun 0
sa0: <HP C1533A A612> Removable Sequential Access SCSI2 device
sa0: 10.0MB/s transfers (10.0MHz, offset 15)
da1 at ahc1 bus 0 target 1 lun 0
da1: <Quantum XP34300W L915> Fixed Direct Access SCSI2 device
da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da1: 4101MB (8399520 512 byte sectors: 64H 32S/T 4101C)
da0 at ahc1 bus 0 target 0 lun 0
da0: <MICROP 3391WS X502> Fixed Direct Access SCSI2 device
da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled
da0: 8681MB (17780058 512 byte sectors: 64H 32S/T 8681C)
cd0 at ahc0 bus 0 target 5 lun 0
cd0: <TOSHIBA CD-ROM XM-3701TA 3615> Removable CD-ROM SCSI2 device
cd0: 4.901MB/s transfers (4.901MHz, offset 15)
cd0: cd present [328222 x 2048 byte records]
changing root device to da0s2a
And the output of mptable:
===============================================================================
MPTable, version 2.0.15
-------------------------------------------------------------------------------
MP Floating Pointer Structure:
location: BIOS
physical address: 0x000f5a60
signature: '_MP_'
length: 16 bytes
version: 1.1
checksum: 0x80
mode: Virtual Wire
-------------------------------------------------------------------------------
MP Config Table Header:
physical address: 0x000f1400
signature: 'PCMP'
base table length: 300
version: 1.1
checksum: 0xf9
OEM ID: 'OEM00000'
Product ID: 'PROD00000000'
OEM table pointer: 0x00000000
OEM table size: 0
entry count: 29
local APIC address: 0xfee00000
extended table length: 0
extended table checksum: 0
-------------------------------------------------------------------------------
MP Config Base Table Entries:
--
Processors: APIC ID Version State Family Model Step Flags
0 0x11 BSP, usable 6 5 2 0xfbff
1 0x11 AP, usable 6 5 2 0xfbff
--
Bus: Bus ID Type
0 PCI
1 PCI
2 ISA
--
I/O APICs: APIC ID Version State Address
2 0x11 usable 0xfec00000
--
I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN#
ExtINT conforms conforms 2 0 2 0
INT conforms conforms 2 1 2 1
INT conforms conforms 2 0 2 2
INT conforms conforms 2 3 2 3
INT conforms conforms 2 4 2 4
INT conforms conforms 2 5 2 5
INT conforms conforms 2 6 2 6
INT conforms conforms 2 7 2 7
INT active-hi edge 2 8 2 8
INT conforms conforms 2 9 2 9
INT conforms conforms 2 10 2 10
INT conforms conforms 2 11 2 11
INT conforms conforms 2 12 2 12
INT conforms conforms 2 13 2 13
INT conforms conforms 2 14 2 14
INT conforms conforms 2 15 2 15
INT active-lo level 0 8:A 2 16
INT active-lo level 0 9:A 2 17
INT active-lo level 0 12:A 2 16
INT active-lo level 0 12:B 2 16
SMI active-lo edge 2 0 2 23
--
Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN#
ExtINT conforms conforms 0 0:A 255 0
NMI conforms conforms 0 0:A 255 1
-------------------------------------------------------------------------------
# SMP kernel config file options:
# Required:
options SMP # Symmetric MultiProcessor Kernel
options APIC_IO # Symmetric (APIC) I/O
# Optional (built-in defaults will work in most cases):
#options NCPU=2 # number of CPUs
#options NBUS=3 # number of busses
#options NAPIC=1 # number of IO APICs
#options NINTR=24 # number of INTs
===============================================================================
In this case I was not using softupdates. The panic appears with and without
async mounts of the filesystems.
Michael
-------------------------------------------------------------------------
michael class, viktor-renner str. 39, 72074 tuebingen, frg
E-Mail: michael_class@gmx.net
Phone: +49 7031 14-3707 (work) +49 7071 81950 (private)
-------------------------------------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 02:49:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA01995
for freebsd-current-outgoing; Sat, 14 Nov 1998 02:49:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01986
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 02:49:04 -0800 (PST)
(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
by freebsd.dk (8.9.1/8.9.1) id LAA17625;
Sat, 14 Nov 1998 11:48:37 +0100 (CET)
(envelope-from sos)
From: Søren Schmidt <sos@freebsd.dk>
Message-Id: <199811141048.LAA17625@freebsd.dk>
Subject: Re: ATAPI CD/R driver and Mitsumi CR-2600TE
In-Reply-To: <005601be0f4e$df1df220$08f19b26@xanadu.lovett.com> from Ade Lovett at "Nov 13, 1998 3:45: 3 pm"
To: ade@supernews.net (Ade Lovett)
Date: Sat, 14 Nov 1998 11:48:37 +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 Ade Lovett wrote:
> > > Ok. What does rezero actually do? Can I simply add in a hack to
> > > simulate it with:
> > >
> > > acd_request_wait( ..., ATAPI_START_STOP, 1,0,0,0,0,0,0,0,0,0,0 );
> > > acd_request_wait( ..., ATAPI_START_STOP, 1,0,0,1,0,0,0,0,0,0,0 );
> > >
> > > ie: doing the equivalent of the CDIOCSTOP, CDIOCSTART ioctls?
> >
> > IIRC yes.
>
> Hmm.. well, I tried that.. it failed on the first acd_request_wait
> (for the CDIOCSTOP equivalent), left the disk spinning inside the drive,
> and I couldn't get the disk out unless I halted the machine and hit
> the physical eject button whilst the machine was at the BIOS.
OK, I'll see what I can do, it seems my memory isn't that good after
all :), I'll dig into the docs asap...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 02:50:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA02343
for freebsd-current-outgoing; Sat, 14 Nov 1998 02:50:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA02327
for <current@freebsd.org>; Sat, 14 Nov 1998 02:50:48 -0800 (PST)
(envelope-from itfs!nnd%itfs.nsk.su@gw.itfs.nsk.su)
Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id QAA02070 for current@freebsd.org; Sat, 14 Nov 1998 16:50:11 +0600
Received: by itfs.nsk.su; Sat, 14 Nov 98 16:48:33 +0600 (NSK)
To: current@FreeBSD.ORG
Message-ID: <AA10MJseG9@itfs.nsk.su>
Organization: Scientific & Technical Enterprise INFOTEKA
From: nnd@itfs.nsk.su (Nickolay Dudorov)
Date: Sat, 14 Nov 98 16:48:33 +0600 (NSK)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=koi8-r
Content-Transfer-Encoding: 8BIT
Subject: CTM-deltas generation problems ?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
What is an estimation time for CTM-deltas
generation process restart ?
N.Dudorov
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 03:00:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA02657
for freebsd-current-outgoing; Sat, 14 Nov 1998 03:00:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02652
for <freebsd-current@freebsd.org>; Sat, 14 Nov 1998 03:00:20 -0800 (PST)
(envelope-from andrsn@andrsn.stanford.edu)
Received: from localhost (andrsn@localhost.Stanford.EDU [127.0.0.1])
by andrsn.stanford.edu (8.9.1/8.9.1) with SMTP id CAA12047
for <freebsd-current@freebsd.org>; Sat, 14 Nov 1998 02:53:56 -0800 (PST)
Date: Sat, 14 Nov 1998 02:53:56 -0800 (PST)
From: Annelise Anderson <andrsn@andrsn.stanford.edu>
To: freebsd-current@FreeBSD.ORG
Subject: aout-elf-build error: ld-elf.so.1 not found
Message-ID: <Pine.BSF.3.96.981114021539.11953B-100000@andrsn.stanford.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 make aout-to-elf-build with sources supped
11/13 in the afternoon and got lots of errors that
"/usr/libexec/ld-elf.so.1 not found." The build completed,
although I understand from some other message in the morrass
of -current mail that it's a bug for it to have done so.
It installed all right too, but I had to add all the
library paths with ldconfig -elf -m and ldconfig -aout -m,
even though I updated rc.conf and rc with the new library
information. I finally got X to run by assuming that the
libraries in /usr/local/lib were aout libraries instead of
elf ones. However, WordPerfect 7, a linux version, used to
run and now doesn't, and no longer believes that FreeBSD 3.0
is installed. (I may have "branded" it as elf before.)
I am not sure whether this build should be considered
damaged (perhaps missing some elf libraries) and redone with
newer sources; some things (ppp and ssh) run as expected.
Others like ps and top do not, finding some mismatch,
a difficulty that would (I think )require a new kernel. I did
build a new kernel with some of the new scsi terminology in it
and I created the devices in /dev with the new MAKEDEV file and put
them in /etc/fstab but this didn't work (the kernel couldn't
fsck the files systems) apparently because I had neglected to
put the CAM lines in the kernel. So I have been using the old
kernel and old /etc/fstab.
This was all done on a system that was up to date (as
an aout system) around September 4; it was happily running
softupdates then and still does. It also still runs the tcl/tk
stuff I've had a chance to try, and it runs ppp and ssh.
So, does the build error, not finding /usr/libexec/ld-elf.so.1,
mean that I should resup and redo it, or does it just need some
configuration to get it running right?
I thought someone might be interested in knowing about
this problem and perhaps might be willing to suggest what I ought
to do next.
Not a real easy process, is it?
Annelise
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 03:07:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA03106
for freebsd-current-outgoing; Sat, 14 Nov 1998 03:07: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 DAA03098
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 03:07:46 -0800 (PST)
(envelope-from mark@grondar.za)
Received: from greenpeace.grondar.za (IDENT:YwYzKGHkIXSw2O0IGs7eLH2oZ9+W0ek7@greenpeace.grondar.za [196.7.18.132])
by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id NAA08098;
Sat, 14 Nov 1998 13:07:21 +0200 (SAST)
(envelope-from mark@grondar.za)
Received: from grondar.za (IDENT:rVXMBgJWUMNZ0eRjoWxtGfqX7xy1aUJk@localhost [127.0.0.1])
by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id NAA01891;
Sat, 14 Nov 1998 13:07:20 +0200 (SAST)
(envelope-from mark@grondar.za)
Message-Id: <199811141107.NAA01891@greenpeace.grondar.za>
To: nnd@itfs.nsk.su (Nickolay Dudorov)
cc: current@FreeBSD.ORG
Subject: Re: CTM-deltas generation problems ?
In-Reply-To: Your message of " Sat, 14 Nov 1998 16:48:33 +0600." <AA10MJseG9@itfs.nsk.su>
References: <AA10MJseG9@itfs.nsk.su>
Date: Sat, 14 Nov 1998 13:07:19 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
wrote:
>
> What is an estimation time for CTM-deltas
> generation process restart ?
I do not understand your question?
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 Sat Nov 14 03:20:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA03860
for freebsd-current-outgoing; Sat, 14 Nov 1998 03:20:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA03855
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 03:20:33 -0800 (PST)
(envelope-from itfs!nnd%itfs.nsk.su@gw.itfs.nsk.su)
Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id RAA02151; Sat, 14 Nov 1998 17:20:08 +0600
Received: by itfs.nsk.su; Sat, 14 Nov 98 17:15:19 +0600 (NSK)
To: mark@grondar.za, nnd@itfs.nsk.su
Cc: current@FreeBSD.ORG
References: <199811141107.NAA01891@greenpeace.grondar.za>
Message-ID: <AB7PMJsKQ9@itfs.nsk.su>
Organization: Scientific & Technical Enterprise INFOTEKA
From: nnd@itfs.nsk.su (Nickolay Dudorov)
Date: Sat, 14 Nov 98 17:15:19 +0600 (NSK)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=koi8-r
Content-Transfer-Encoding: 8BIT
Subject: Re: CTM-deltas generation problems ?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>From: Mark Murray <mark@grondar.za>
>
> wrote:
>>
>> What is an estimation time for CTM-deltas
>> generation process restart ?
>
>I do not understand your question?
Sorry.
I mean that on "ctm.freebsd.org" last delta in "cvs-cur"
directory is 'cvs-cur.4807.gz' from 12 Nov. 1998 09:30.
The same is the last delta I've received by mail.
N.Dudorov
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 03:28:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA04261
for freebsd-current-outgoing; Sat, 14 Nov 1998 03:28:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04256
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 03:28:40 -0800 (PST)
(envelope-from ulf@Gatekeeper.Alameda.net)
Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id DAA25662;
Sat, 14 Nov 1998 03:27:48 -0800 (PST)
Message-ID: <19981114032748.A23569@Alameda.net>
Date: Sat, 14 Nov 1998 03:27:48 -0800
From: Ulf Zimmermann <ulf@Alameda.net>
To: Nickolay Dudorov <nnd@itfs.nsk.su>, mark@grondar.za
Cc: current@FreeBSD.ORG
Subject: Re: CTM-deltas generation problems ?
Reply-To: ulf@Alameda.net
References: <199811141107.NAA01891@greenpeace.grondar.za> <AB7PMJsKQ9@itfs.nsk.su>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <AB7PMJsKQ9@itfs.nsk.su>; from Nickolay Dudorov on Sat, Nov 14, 1998 at 05:15:19PM +0600
Organization: Alameda Networks, Inc.
X-Operating-System: FreeBSD 2.2.6-STABLE
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, Nov 14, 1998 at 05:15:19PM +0600, Nickolay Dudorov wrote:
> >From: Mark Murray <mark@grondar.za>
> >
> > wrote:
> >>
> >> What is an estimation time for CTM-deltas
> >> generation process restart ?
> >
> >I do not understand your question?
>
> Sorry.
>
> I mean that on "ctm.freebsd.org" last delta in "cvs-cur"
> directory is 'cvs-cur.4807.gz' from 12 Nov. 1998 09:30.
> The same is the last delta I've received by mail.
My error. I had to move the machine and it seems another ctm build already
started as I shutdown the machine. because of that there was a lock file
and no ctm restarted.
>
> N.Dudorov
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
--
Regards, Ulf.
---------------------------------------------------------------------
Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936
Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 04:07:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA10540
for freebsd-current-outgoing; Sat, 14 Nov 1998 04:07:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rmstar.campus.luth.se (rmstar.campus.luth.se [130.240.197.32])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10534
for <freebsd-current@freebsd.org>; Sat, 14 Nov 1998 04:07:03 -0800 (PST)
(envelope-from murduth@rmstar.campus.luth.se)
Received: from rmstar.campus.luth.se (murduth@localhost [127.0.0.1])
by rmstar.campus.luth.se (8.9.1/8.9.1) with ESMTP id NAA08312
for <freebsd-current@freebsd.org>; Sat, 14 Nov 1998 13:06:36 +0100 (CET)
(envelope-from murduth@rmstar.campus.luth.se)
Message-Id: <199811141206.NAA08312@rmstar.campus.luth.se>
X-Mailer: exmh version 2.0.2 2/24/98
To: freebsd-current@FreeBSD.ORG
Subject: MFS strangeness.
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 14 Nov 1998 13:06:36 +0100
From: Joakim Henriksson <murduth@ludd.luth.se>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I usually mount my /tmp and /var/tmp as MFS on the swap, but ocasionally most
of my swap is allocated by the MFS without any reason i could detect. Anyone
else seen this? When this happens MFS is unusable, since it hogs all the swap
so i would like to find out why if anyone knows...
--
regards/ Joakim
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 06:25:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA16852
for freebsd-current-outgoing; Sat, 14 Nov 1998 06:25:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16841;
Sat, 14 Nov 1998 06:25:13 -0800 (PST)
(envelope-from ticso@cicely5.cicely.de)
Received: from cicely.cicely.de (cicely.de [194.231.9.142])
by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id PAA15338;
Sat, 14 Nov 1998 15:24:36 +0100 (MET)
Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.1.7])
by cicely.cicely.de (8.8.8/8.8.8) with ESMTP id PAA09804;
Sat, 14 Nov 1998 15:25:03 +0100 (CET)
Received: (from ticso@localhost)
by cicely5.cicely.de (8.9.0/8.9.0) id PAA00773;
Sat, 14 Nov 1998 15:24:53 +0100 (CET)
Message-ID: <19981114152452.13292@cicely.de>
Date: Sat, 14 Nov 1998 15:24:52 +0100
From: Bernd Walter <ticso@cicely.de>
To: Brian Feldman <green@unixhelp.org>,
=?iso-8859-1?Q?Dag-Erling_C=2E_Sm=F8rgrav?= <dag-erli@ifi.uio.no>
Cc: Chuck Robey <chuckr@mat.net>, Satoshi Asami <asami@FreeBSD.ORG>,
nate@mt.sri.com, jkh@zippy.cdrom.com, mike@smith.net.au,
obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
References: <xzp7lx1ve2w.fsf@grjottunagard.ifi.uio.no> <Pine.BSF.4.05.9811112143390.725-100000@janus.syracuse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.89i
In-Reply-To: <Pine.BSF.4.05.9811112143390.725-100000@janus.syracuse.net>; from Brian Feldman on Wed, Nov 11, 1998 at 09:53:45PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Nov 11, 1998 at 09:53:45PM -0500, Brian Feldman wrote:
> On 12 Nov 1998, Dag-Erling C. [iso-8859-1] Smørgrav wrote:
>
> > Brian Feldman <green@unixhelp.org> writes:
> > > Ex is part of nvi/nex, and is in /usr/bin. Do you mean ed? BTW, as I bring
> > > this up, I'd like to propose moving nvi/nex to /bin. And of course, why
> > > don't we add setenv("TERM", "cons25") before the sh spawn in /sbin/init?
> > > It would prevent the following error in a single-user boot:
> > > # vi
> > > ex/vi: Error: unknown: No such file or directory
> >
> > Well, instead you'll get
> >
> > ex/vi: Error: cons25: No such file or directory
> >
> > because for $TERM to be meaningful, you need /usr/share/misc/termcap,
> > and /usr probably isn't mounted yet (assuming you've moved vi to /bin,
> > which means linking it statically)
>
> True... what are feelings on a "tinytermcap" if well-implemented (with
> libtermcap)? It would be really simple to add to
> src/lib/libtermcap/pathnames.h /etc/tinytermcap...
>
> {"/home/green"}$ l tinytermcap
> -rw-r--r-- 1 green green 1382 Nov 11 21:51 tinytermcap
> tinytermcap would have consoles cons25{,w,r,l1}.
Not very helpfull when using a seriel console
In my case I'm using an esprit type terminal and sometimes vt100 ...
>
> >
> > DES
> > --
> > Dag-Erling Smørgrav - dag-erli@ifi.uio.no
> >
>
>
> Cheers,
> Brian Feldman
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
--
B.Walter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 06:31:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA17274
for freebsd-current-outgoing; Sat, 14 Nov 1998 06:31:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from root.com (root.com [198.145.90.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17268
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 06:31:39 -0800 (PST)
(envelope-from root@root.com)
Received: from root.com (localhost [127.0.0.1])
by root.com (8.8.8/8.8.5) with ESMTP id GAA13419;
Sat, 14 Nov 1998 06:32:26 -0800 (PST)
Message-Id: <199811141432.GAA13419@root.com>
To: michael_class@gmx.net
cc: current@FreeBSD.ORG, mckusick@mckusick.com
Subject: Re: SMP-System panics after recent ffs_alloc changes
In-reply-to: Your message of "Sat, 14 Nov 1998 11:23:14 +0100."
<Pine.BSF.4.05.9811141122300.432-100000@pc-micha.mc.hp.com>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sat, 14 Nov 1998 06:32:26 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>the recent changes in vfs_cluster.c, buf.h and ffs_alloc.c cause a
>panic on my SMP-System.
...
>Backing out these changes solves the problem.
>
>The panic is"ffs_blkfree: bad size"
No need to back out the changes - there is a sysctl knob to shut off the
code called "vfs.ffs.doreallocblks"...just set it to 0.
Is there anything unusual about your filesystems? Are you using the
standard 8K/1K block/fragment size?
-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 Sat Nov 14 07:02:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA19499
for freebsd-current-outgoing; Sat, 14 Nov 1998 07:02:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from k6n1.znh.org (dialup5.gaffaneys.com [208.155.161.55])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19480;
Sat, 14 Nov 1998 07:02:04 -0800 (PST)
(envelope-from zach@gaffaneys.com)
Received: (from zach@localhost)
by k6n1.znh.org (8.9.1/8.9.1) id OAA03749;
Sat, 14 Nov 1998 14:57:03 GMT
(envelope-from zach)
Message-ID: <19981114085703.A3720@znh.org>
Date: Sat, 14 Nov 1998 08:57:03 -0600
From: Zach Heilig <zach@gaffaneys.com>
To: Bernd Walter <ticso@cicely.de>, Brian Feldman <green@unixhelp.org>,
=?iso-8859-1?Q?Dag-Erling_C=2E_Sm=F8rgrav?= <dag-erli@ifi.uio.no>
Cc: Chuck Robey <chuckr@mat.net>, Satoshi Asami <asami@FreeBSD.ORG>,
nate@mt.sri.com, jkh@zippy.cdrom.com, mike@smith.net.au,
obrien@NUXI.com, current@FreeBSD.ORG
Subject: Re: Is it soup yet? :-)
References: <xzp7lx1ve2w.fsf@grjottunagard.ifi.uio.no> <Pine.BSF.4.05.9811112143390.725-100000@janus.syracuse.net> <19981114152452.13292@cicely.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93.2i
In-Reply-To: <19981114152452.13292@cicely.de>; from Bernd Walter on Sat, Nov 14, 1998 at 03:24:52PM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, Nov 14, 1998 at 03:24:52PM +0100, Bernd Walter wrote:
> On Wed, Nov 11, 1998 at 09:53:45PM -0500, Brian Feldman wrote:
> > True... what are feelings on a "tinytermcap" if well-implemented (with
> > libtermcap)? It would be really simple to add to
> > src/lib/libtermcap/pathnames.h /etc/tinytermcap...
Check out /usr/src/etc/termcap.small (also usually installed in
/etc/termcap.small).
> > {"/home/green"}$ l tinytermcap
> > -rw-r--r-- 1 green green 1382 Nov 11 21:51 tinytermcap
> > tinytermcap would have consoles cons25{,w,r,l1}.
> Not very helpfull when using a seriel console
> In my case I'm using an esprit type terminal and sometimes vt100 ...
It only has:
cons25w|ansiw|ansi80x25-raw:\
cons25|ansis|ansi80x25:\
cons25-m|ansis-mono|ansi80x25-mono:\
cons50|ansil|ansi80x50:\
cons50-m|ansil-mono|ansi80x50-mono:\
cons25r|pc3r|ibmpc3r|cons25-koi8-r:\
cons25r-m|pc3r-m|ibmpc3r-mono|cons25-koi8-r-mono:\
cons50r|cons50-koi8-r:\
cons50r-m|cons50-koi8-r-mono:\
cons25l1|cons25-iso8859-1:\
cons25l1-m|cons25-iso8859-1-mono:\
cons50l1|cons50-iso8859-1:\
cons50l1-m|cons50-iso8859-1-mono:\
dosansi|ANSI.SYS standard crt:\
pc|ibmpc|ibm pc PC/IX:\
pc3mono|IBM PC 386BSD Console with monochrome monitor:\
pc3|ibmpc3|IBM PC 386BSD Console:\
(Obviously, you can add whatever terminals you want...).
--
Zach Heilig <zach@gaffaneys.com>
If it looks like a duck, and quacks like a duck, we have to at least consider
the possibility that we have a small aquatic bird of the family Anatidæ on
our hands (Douglas Adams -- Dirk Gently's Holistic Detective Agency)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 07:09:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA20020
for freebsd-current-outgoing; Sat, 14 Nov 1998 07:09:34 -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 HAA19812
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 07:08:46 -0800 (PST)
(envelope-from mark@greenpeace.grondar.za)
Received: from greenpeace.grondar.za (IDENT:ZeSKI1Ku9rIZWLlz6BFM+BK6HEmO4pLi@greenpeace.grondar.za [196.7.18.132])
by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id RAA08354;
Sat, 14 Nov 1998 17:07:46 +0200 (SAST)
(envelope-from mark@greenpeace.grondar.za)
Received: from greenpeace.grondar.za (IDENT:HMMlrFyCsnyYWmdLxVyfiN5Qy7bDa+ii@localhost [127.0.0.1])
by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id RAA13549;
Sat, 14 Nov 1998 17:07:30 +0200 (SAST)
(envelope-from mark@greenpeace.grondar.za)
Message-Id: <199811141507.RAA13549@greenpeace.grondar.za>
To: ulf@Alameda.net
cc: Nickolay Dudorov <nnd@itfs.nsk.su>, mark@grondar.za, current@FreeBSD.ORG
Subject: Re: CTM-deltas generation problems ?
In-Reply-To: Your message of " Sat, 14 Nov 1998 03:27:48 PST." <19981114032748.A23569@Alameda.net>
References: <199811141107.NAA01891@greenpeace.grondar.za> <AB7PMJsKQ9@itfs.nsk.su> <19981114032748.A23569@Alameda.net>
Date: Sat, 14 Nov 1998 17:07:20 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Ulf Zimmermann wrote:
> > I mean that on "ctm.freebsd.org" last delta in "cvs-cur"
> > directory is 'cvs-cur.4807.gz' from 12 Nov. 1998 09:30.
> > The same is the last delta I've received by mail.
>
> My error. I had to move the machine and it seems another ctm build already
> started as I shutdown the machine. because of that there was a lock file
> and no ctm restarted.
Lock removed. Things should be OK.
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 Sat Nov 14 08:23:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA23963
for freebsd-current-outgoing; Sat, 14 Nov 1998 08:23:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pc-micha.mc.hp.com ([145.253.107.25])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23953
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 08:23:48 -0800 (PST)
(envelope-from michaelc@bbn.hp.com)
Received: from localhost (michaelc@localhost)
by pc-micha.mc.hp.com (8.9.1/8.9.1) with ESMTP id RAA02430;
Sat, 14 Nov 1998 17:23:37 +0100 (MET)
(envelope-from michaelc@bbn.hp.com)
X-Authentication-Warning: pc-micha.mc.hp.com: michaelc owned process doing -bs
Date: Sat, 14 Nov 1998 17:23:36 +0100 (MET)
From: Michael Class <michaelc@bbn.hp.com>
X-Sender: michaelc@pc-micha.mc.hp.com
Reply-To: michael_class@gmx.net
To: David Greenman <dg@root.com>
cc: michael_class@gmx.net, current@FreeBSD.ORG, mckusick@mckusick.com
Subject: Re: SMP-System panics after recent ffs_alloc changes
In-Reply-To: <199811141432.GAA13419@root.com>
Message-ID: <Pine.BSF.4.05.9811141720040.2421-100000@pc-micha.mc.hp.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, 14 Nov 1998, David Greenman wrote:
> >the recent changes in vfs_cluster.c, buf.h and ffs_alloc.c cause a
> >panic on my SMP-System.
> ...
> >Backing out these changes solves the problem.
> >
> >The panic is"ffs_blkfree: bad size"
>
> No need to back out the changes - there is a sysctl knob to shut off the
> code called "vfs.ffs.doreallocblks"...just set it to 0.
Thank you, this seems to be a workaroundr; make -j4 world succeeded.
> Is there anything unusual about your filesystems? Are you using the
> standard 8K/1K block/fragment size?
Yes, this are the partions of the two disks on the system:
6 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 81920 0 4.2BSD 1024 8192 8192 # (Cyl. 0 - 5*)
b: 262144 81920 swap # (Cyl. 5*- 21*)
c: 12434310 0 unused 1024 8192 # (Cyl. 0 - 773)
d: 409600 344064 4.2BSD 1024 8192 8192 # (Cyl. 21*- 46*)
e: 819200 753664 4.2BSD 1024 8192 8192 # (Cyl. 46*- 97*)
f: 10861446 1572864 4.2BSD 1024 8192 8192 # (Cyl. 97*- 773*)
4 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 8252 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 0*)
b: 327680 8253 swap # (Cyl. 1 - 40*)
c: 4194304 0 unused 0 0 # (Cyl. 0 - 508*)
d: 3858371 335933 4.2BSD 1024 8192 16 # (Cyl. 40*- 508*)
Michael
-------------------------------------------------------------------------
michael class, viktor-renner str. 39, 72074 tuebingen, frg
E-Mail: michael_class@gmx.net
Phone: +49 7031 14-3707 (work) +49 7071 81950 (private)
-------------------------------------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 09:13:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA28430
for freebsd-current-outgoing; Sat, 14 Nov 1998 09:13:00 -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 JAA28321
for <current@freebsd.org>; Sat, 14 Nov 1998 09:11:25 -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.1a.NOMIME/8.9.1) with ESMTP id UAA02649
for <current@freebsd.org>; Sat, 14 Nov 1998 20:14:31 +0300 (MSK)
(envelope-from romanp@wuppy.rcs.ru)
Date: Sat, 14 Nov 1998 20:14:30 +0300 (MSK)
From: "Roman V. Palagin" <romanp@wuppy.rcs.ru>
To: current@FreeBSD.ORG
Subject: Small inconsistency in fresh AMD import
Message-ID: <Pine.BSF.4.05.SK+PRV.9811051249580.239-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!
output of just compiled am-utils:
$ amd -v
Copyright (c) 1997-1998 Erez Zadok
Copyright (c) 1990 Jan-Simon Pendry
Copyright (c) 1990 Imperial College of Science, Technology & Medicine
Copyright (c) 1990 The Regents of the University of California.
am-utils version 6.0a16 (build 300006).
^^^^^^^ but version is 6.0b1
Problem lies in src/usr.sbin/amd/include/config.h, line 930:
#define VERSION "6.0a16"
should be
#define VERSION "6.0b1".
-------------------------------------------------------------------------
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 Sat Nov 14 10:05:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA03409
for freebsd-current-outgoing; Sat, 14 Nov 1998 10:05:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03404
for <current@freebsd.org>; Sat, 14 Nov 1998 10:05:10 -0800 (PST)
(envelope-from donegan@oldnews.quick.net)
Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id KAA06493; Sat, 14 Nov 1998 10:04:48 -0800 (PST)
Date: Sat, 14 Nov 1998 10:04:48 -0800 (PST)
From: "Steven P. Donegan" <donegan@quick.net>
To: current@FreeBSD.ORG
Subject: top/w/vmstat weirdness :-)
Message-ID: <Pine.BSI.3.91.981114100231.6441A-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
I am running a kernel compiled from today's sources - the whole make
world/kernel recompile. I get errors from 'w' and 'top' won't run. 'w'
reports:
10:02AM up 1:08, 1 user, load averages: 0.31, 0.17, 0.26
USER TTY FROM LOGIN@ IDLE WHAT
w: proc size mismatch (25384 total, 672 chunks): Undefined error: 0
What have I done wrong :-)
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 Sat Nov 14 10:06:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA03485
for freebsd-current-outgoing; Sat, 14 Nov 1998 10:06:23 -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 KAA03480
for <current@freebsd.org>; Sat, 14 Nov 1998 10:06:21 -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 KAA03824;
Sat, 14 Nov 1998 10:05:59 -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 KAA12841;
Sat, 14 Nov 1998 10:05:59 -0800 (PST)
(envelope-from jdp@polstra.com)
Date: Sat, 14 Nov 1998 10:05:59 -0800 (PST)
Message-Id: <199811141805.KAA12841@vashon.polstra.com>
To: techie@tantivy.stanford.edu
Subject: Re: make release fails
Newsgroups: polstra.freebsd.stable
In-Reply-To: <199811140506.VAA29699@tantivy.stanford.edu>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <199811140506.VAA29699@tantivy.stanford.edu>,
Bob Vaughan <techie@tantivy.stanford.edu> wrote:
> I'm trying to build a release for local use, and I keep running into the
> following problem.. (all sources cvs'd this week, several times..)
I hear you saying it, but to me it looks like your sources are not
up to date.
> it appears to be choking on the following line in /usr/src/etc/Makefile:
>
>
> BIN1= aliases amd.map crontab csh.cshrc csh.login csh.logout dm.conf \
> ftpusers gettytab group hosts host.conf hosts.equiv hosts.lpd \
> inetd.conf login.conf login.access motd modems networks \
> newsyslog.conf phones pccard.conf.sample printcap profile protocols \
> rc rc.conf rc.firewall rc.local rc.network rc.pccard rc.serial \
> >>>> etc.${MACHINE}/rc.${MACHINE} \
This line has said "MACHINE_ARCH" instead of "MACHINE" since around
the end of August.
Make sure your sources are really up to date. Also, do a make world
first, before you do your make release.
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 Nov 14 10:08:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA03700
for freebsd-current-outgoing; Sat, 14 Nov 1998 10:08:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.webspan.net (mail.webspan.net [206.154.70.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03690
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 10:08:41 -0800 (PST)
(envelope-from opsys@mail.webspan.net)
Received: from orion.webspan.net (orion.webspan.net [206.154.70.5])
by mail.webspan.net (WEBSPAN/970608) with SMTP id NAA18563;
Sat, 14 Nov 1998 13:08:11 -0500 (EST)
Date: Sat, 14 Nov 1998 13:08:10 -0500 (EST)
From: Open Systems Networking <opsys@mail.webspan.net>
X-Sender: opsys@orion.webspan.net
To: "Steven P. Donegan" <donegan@quick.net>
cc: current@FreeBSD.ORG
Subject: Re: top/w/vmstat weirdness :-)
In-Reply-To: <Pine.BSI.3.91.981114100231.6441A-100000@oldnews.quick.net>
Message-ID: <Pine.BSF.4.02.9811141306350.14586-100000@orion.webspan.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, 14 Nov 1998, Steven P. Donegan wrote:
> I am running a kernel compiled from today's sources - the whole make
> world/kernel recompile. I get errors from 'w' and 'top' won't run. 'w'
> reports:
>
> 10:02AM up 1:08, 1 user, load averages: 0.31, 0.17, 0.26
> USER TTY FROM LOGIN@ IDLE WHAT
> w: proc size mismatch (25384 total, 672 chunks): Undefined error: 0
>
> What have I done wrong :-)
You simply missed don's post about rebuilding libkvm, top, ps, w, vmstat
and family. Just rebuild libkvm and install it then rebuild the tools that
are breaking and build a new kernel against the new libkvm. No big deal.
Youll be back in shape in no time.
Chris
--
"You both seem to be ignoring the fact that the networking market is
driven by so-called 'IT professionals' these days, most of whom can't
tell the difference between an ARP and a carp." --Wes Peters
===================================| Open Systems FreeBSD Consulting.
FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186
-----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134
FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net
http://www.freebsd.org | Consulting, Network Engineering, Security
===================================| http://open-systems.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 10:11:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA03878
for freebsd-current-outgoing; Sat, 14 Nov 1998 10:11:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from matrix.42.org (matrix.42.org [194.246.250.200])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03871
for <freebsd-current@freebsd.org>; Sat, 14 Nov 1998 10:10:51 -0800 (PST)
(envelope-from sec@42.org)
Received: (from sec@localhost)
by matrix.42.org (8.8.8/8.8.5) id TAA07198
for freebsd-current@freebsd.org (sender <sec>);
Sat, 14 Nov 1998 19:10:23 +0100 (CET)
Date: Sat, 14 Nov 1998 19:10:23 +0100
From: Stefan `Sec` Zehl <sec@42.org>
To: freebsd-current@FreeBSD.ORG
Subject: make release (RELENG_3_0_0_RELEASE)
Message-ID: <19981114191022.A7112@matrix.42.org>
X-Current-Backlog: 329 messages
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.10i
I-love-doing-this: really
Accept-Languages: de, en
X-URL: http://sec.42.org/
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
I'm running 2.2-stable(aout) any try to make a 3.0-release right now. So far
it looks promising, i just wonder if the release i get will be ELF or
AOUT ?
Do i have to do something magic to make an 3.0-elf-release ?
CU,
Sec
--
"Computers make very fast, very accurate, mistakes."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 10:18:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA04243
for freebsd-current-outgoing; Sat, 14 Nov 1998 10:18:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04238
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 10:18:53 -0800 (PST)
(envelope-from donegan@oldnews.quick.net)
Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id KAA06531; Sat, 14 Nov 1998 10:18:29 -0800 (PST)
Date: Sat, 14 Nov 1998 10:18:29 -0800 (PST)
From: "Steven P. Donegan" <donegan@quick.net>
To: Open Systems Networking <opsys@mail.webspan.net>
cc: current@FreeBSD.ORG
Subject: Re: top/w/vmstat weirdness :-)
In-Reply-To: <Pine.BSF.4.02.9811141306350.14586-100000@orion.webspan.net>
Message-ID: <Pine.BSI.3.91.981114101518.6441B-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
On Sat, 14 Nov 1998, Open Systems Networking wrote:
> On Sat, 14 Nov 1998, Steven P. Donegan wrote:
>
> > I am running a kernel compiled from today's sources - the whole make
> > world/kernel recompile. I get errors from 'w' and 'top' won't run. 'w'
> > reports:
> >
> > 10:02AM up 1:08, 1 user, load averages: 0.31, 0.17, 0.26
> > USER TTY FROM LOGIN@ IDLE WHAT
> > w: proc size mismatch (25384 total, 672 chunks): Undefined error: 0
> >
> > What have I done wrong :-)
>
> You simply missed don's post about rebuilding libkvm, top, ps, w, vmstat
> and family. Just rebuild libkvm and install it then rebuild the tools that
> are breaking and build a new kernel against the new libkvm. No big deal.
> Youll be back in shape in no time.
>
> Chris
Shouldn't a 'make world' really make the entire world? If I need to
rebuild those libraries and individual components the question becomes how?
Thanks - since my mailbox usually includes over 100 emails daily (cisco
mailing list, freebsd mailing list(s), detomaso pantera list, etc. I tend
to prune many times without reading - so sorry if this is something
that's been discussed before).
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 10:52:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA06546
for freebsd-current-outgoing; Sat, 14 Nov 1998 10:52:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nms.optonline.net (nms.optonline.net [167.206.1.107])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06541
for <freebsd-current@FreeBSD.ORG>; Sat, 14 Nov 1998 10:52:18 -0800 (PST)
(envelope-from lross@optonline.net)
Received: from default (Italy@hunt186-23.optonline.net [167.206.186.23])
by nms.optonline.net (8.9.1/8.9.1) with ESMTP id NAA00863
for <freebsd-current@FreeBSD.ORG>; Sat, 14 Nov 1998 13:51:46 -0500 (EST)
Message-ID: <000701be0fff$d3fe7b60$17bacea7@default.optonline.net>
From: "Lou" <lross@optonline.net>
To: <freebsd-current@FreeBSD.ORG>
Subject: join
Date: Sat, 14 Nov 1998 13:51:45 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0004_01BE0FD5.EA9904A0"
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
This is a multi-part message in MIME format.
------=_NextPart_000_0004_01BE0FD5.EA9904A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
PLS ADD ME TO THE LIST
------=_NextPart_000_0004_01BE0FD5.EA9904A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3510.1400"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>PLS ADD ME TO THE=20
LIST</FONT></DIV></BODY></HTML>
------=_NextPart_000_0004_01BE0FD5.EA9904A0--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 11:00:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA07212
for freebsd-current-outgoing; Sat, 14 Nov 1998 11:00:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.webspan.net (mail.webspan.net [206.154.70.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07207
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 11:00:34 -0800 (PST)
(envelope-from opsys@mail.webspan.net)
Received: from orion.webspan.net (orion.webspan.net [206.154.70.5])
by mail.webspan.net (WEBSPAN/970608) with SMTP id OAA26311;
Sat, 14 Nov 1998 14:00:11 -0500 (EST)
Date: Sat, 14 Nov 1998 14:00:10 -0500 (EST)
From: Open Systems Networking <opsys@mail.webspan.net>
X-Sender: opsys@orion.webspan.net
To: "Steven P. Donegan" <donegan@quick.net>
cc: current@FreeBSD.ORG
Subject: Re: top/w/vmstat weirdness :-)
In-Reply-To: <Pine.BSI.3.91.981114101518.6441B-100000@oldnews.quick.net>
Message-ID: <Pine.BSF.4.02.9811141354510.2273-100000@orion.webspan.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, 14 Nov 1998, Steven P. Donegan wrote:
> rebuild those libraries and individual components the question becomes how?
>
> Thanks - since my mailbox usually includes over 100 emails daily (cisco
> mailing list, freebsd mailing list(s), detomaso pantera list, etc. I tend
> to prune many times without reading - so sorry if this is something
> that's been discussed before).
No all you need to do is rebuild, /usr/src/lib/libkvm and install it.
cd /usr/src/lib/libkvm ; make ; make install
then do the same for each util. cd /usr/src/bin/ps ; make ; make install
...
Wash rinse repeat for the rest of the utils.
A complete make world is not needed.
Chris
--
"You both seem to be ignoring the fact that the networking market is
driven by so-called 'IT professionals' these days, most of whom can't
tell the difference between an ARP and a carp." --Wes Peters
===================================| Open Systems FreeBSD Consulting.
FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186
-----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134
FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net
http://www.freebsd.org | Consulting, Network Engineering, Security
===================================| http://open-systems.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 11:12:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA07924
for freebsd-current-outgoing; Sat, 14 Nov 1998 11:12:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07919
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 11:12:55 -0800 (PST)
(envelope-from bright@hotjobs.com)
Received: from localhost (bright@localhost)
by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id OAA27526;
Sat, 14 Nov 1998 14:15:34 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Sat, 14 Nov 1998 14:15:34 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Open Systems Networking <opsys@mail.webspan.net>
cc: "Steven P. Donegan" <donegan@quick.net>, current@FreeBSD.ORG
Subject: Re: top/w/vmstat weirdness :-)
In-Reply-To: <Pine.BSF.4.02.9811141354510.2273-100000@orion.webspan.net>
Message-ID: <Pine.BSF.4.05.9811141412170.27294-100000@porkfriedrice.ny.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 Sat, 14 Nov 1998, Open Systems Networking wrote:
> On Sat, 14 Nov 1998, Steven P. Donegan wrote:
>
> > rebuild those libraries and individual components the question becomes how?
> >
> > Thanks - since my mailbox usually includes over 100 emails daily (cisco
> > mailing list, freebsd mailing list(s), detomaso pantera list, etc. I tend
> > to prune many times without reading - so sorry if this is something
> > that's been discussed before).
>
> No all you need to do is rebuild, /usr/src/lib/libkvm and install it.
> cd /usr/src/lib/libkvm ; make ; make install
> then do the same for each util. cd /usr/src/bin/ps ; make ; make install
> ...
> Wash rinse repeat for the rest of the utils.
>
> A complete make world is not needed.
Generally when i see a "HEADS UP" on the list about some system change
happening, (specifically the change to the proc struct a few days ago) I:
1) READ IT
2) decided I still want to track -current without sounding silly on the
list, then I
3) "make buildworld"
4) make the kernel
5) make installworld
6) install the new kernel
7) reboot
-Alfred
>
> Chris
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 14:08:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA19722
for freebsd-current-outgoing; Sat, 14 Nov 1998 14:08:49 -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 OAA19714;
Sat, 14 Nov 1998 14:08:34 -0800 (PST)
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (root@woof.lan.Awfulhak.org [172.16.0.7])
by awfulhak.org (8.8.8/8.8.8) with ESMTP id FAA16825;
Sat, 14 Nov 1998 05:48:44 GMT
(envelope-from brian@Awfulhak.org)
Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1])
by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id AAA12862;
Sat, 14 Nov 1998 00:22:03 GMT
(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199811140022.AAA12862@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Dmitry Valdov <dv@dv.ru>
cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
In-reply-to: Your message of "Thu, 12 Nov 1998 23:03:10 +0300."
<Pine.BSF.4.02A.9811122249450.12434-100000@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 14 Nov 1998 00:22:03 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Hi!
>
>
> There is gdb's output:
>
> 0x280d7ea4 in _poll ()
> (gdb) bt
> #0 0x280d7ea4 in _poll ()
> #1 0x280f4f11 in res_send ()
> #2 0x280f1c57 in res_query ()
> #3 0x280f2101 in __res_querydomain ()
> #4 0x280f1e55 in res_search ()
> #5 0x280eb5c8 in _gethostbydnsname ()
> #6 0x280ea23f in gethostbyname2 ()
> #7 0x280ea1c3 in gethostbyname ()
> #8 0x805cd4e in ipcp_Init (ipcp=0x8078714, bundle=0x80785f0, l=0x80a3000,
> parent=0x8078648) at ipcp.c:359
> #9 0x804c1d1 in bundle_Create (prefix=0x807366d "/dev/tun", type=1,
> argv=0xefbfdc44) at bundle.c:858
> #10 0x8061df5 in main (argc=1, argv=0xefbfdc44) at main.c:324
> #11 0x804a34d in _start ()
The gethostbyname() is the only thing I know in ppp that causes ppp
to hang - hence my previous message:
[.....]
> ---------- Forwarded message ----------
> Date: Thu, 12 Nov 1998 01:08:05 +0000
> From: Brian Somers <brian@Awfulhak.org>
> To: Dmitry Valdov <dv@dv.ru>
> Cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
> Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
>
> Are you doing anything funny with ``hostname'' on your machine ?
> The only reports I've heard where ppp hangs at startup is when your
> ``hostname'' won't resolve (see http://www.FreeBSD.org/FAQ/userppp.html).
>
> If this isn't the problem, I'd appreciate if you could build ppp with
> -g and when it hangs, run ``gdb -p whatever'' and do a ``bt''.
[.....]
This is what's causing the problem here.
--
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 Sat Nov 14 14:30:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA21088
for freebsd-current-outgoing; Sat, 14 Nov 1998 14:30:20 -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 OAA21083
for <freebsd-current@FreeBSD.ORG>; Sat, 14 Nov 1998 14:30:18 -0800 (PST)
(envelope-from jcwells@u.washington.edu)
Received: from saul9.u.washington.edu (root@saul9.u.washington.edu [140.142.82.7])
by jason04.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP
id OAA17014; Sat, 14 Nov 1998 14:29:56 -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.8.4+UW97.07/8.8.4+UW98.06) with ESMTP
id OAA29095; Sat, 14 Nov 1998 14:29:56 -0800 (PST)
Date: Sat, 14 Nov 1998 14:29:34 -0800 (PST)
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: Lou <lross@optonline.net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: join
In-Reply-To: <000701be0fff$d3fe7b60$17bacea7@default.optonline.net>
Message-ID: <Pine.BSF.4.05.9811141427580.2756-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 Sat, 14 Nov 1998, Lou wrote:
>PLS ADD ME TO THE LIST
http://www.freebsd.org/
Please follow the instructions for being added to the list and you will be
added. Also, Please spell and use proper capitalizatoin. It will make your
message more effective.
Catchya Later, | UW Mechanical Engineering
Jason Wells | http://weber.u.washington.edu/~jcwells/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 14:30:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA21110
for freebsd-current-outgoing; Sat, 14 Nov 1998 14:30:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21105
for <freebsd-current@FreeBSD.ORG>; Sat, 14 Nov 1998 14:30:22 -0800 (PST)
(envelope-from andrsn@andrsn.stanford.edu)
Received: from localhost (andrsn@localhost.Stanford.EDU [127.0.0.1])
by andrsn.stanford.edu (8.9.1/8.9.1) with SMTP id OAA16856
for <freebsd-current@FreeBSD.ORG>; Sat, 14 Nov 1998 14:21:58 -0800 (PST)
Date: Sat, 14 Nov 1998 14:21:58 -0800 (PST)
From: Annelise Anderson <andrsn@andrsn.stanford.edu>
To: freebsd-current@FreeBSD.ORG
Subject: Re: aout-elf-build error: ld-elf.so.1 not found
In-Reply-To: <Pine.BSF.3.96.981114021539.11953B-100000@andrsn.stanford.edu>
Message-ID: <Pine.BSF.3.96.981114142124.16829A-100000@andrsn.stanford.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Sorry to have bothered you, it's all working fine now.
Annelise
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 14:51:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA22977
for freebsd-current-outgoing; Sat, 14 Nov 1998 14:51:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22972
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 14:51:32 -0800 (PST)
(envelope-from donegan@oldnews.quick.net)
Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id OAA06852; Sat, 14 Nov 1998 14:51:09 -0800 (PST)
Date: Sat, 14 Nov 1998 14:51:08 -0800 (PST)
From: "Steven P. Donegan" <donegan@quick.net>
To: Open Systems Networking <opsys@mail.webspan.net>
cc: current@FreeBSD.ORG
Subject: Re: top/w/vmstat weirdness :-)
In-Reply-To: <Pine.BSF.4.02.9811141354510.2273-100000@orion.webspan.net>
Message-ID: <Pine.BSI.3.91.981114144925.6441D-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
The question is - why did a make world NOT do these things. I do a make
world on this development box just about daily, and for some reason that
does not seem to really make the world.
Thanks, I'm doing the manual makes - but the question still stands...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 14:55:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23353
for freebsd-current-outgoing; Sat, 14 Nov 1998 14:55:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23348
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 14:55:11 -0800 (PST)
(envelope-from donegan@oldnews.quick.net)
Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id OAA06865; Sat, 14 Nov 1998 14:54:43 -0800 (PST)
Date: Sat, 14 Nov 1998 14:54:42 -0800 (PST)
From: "Steven P. Donegan" <donegan@quick.net>
To: Alfred Perlstein <bright@hotjobs.com>
cc: Open Systems Networking <opsys@mail.webspan.net>, current@FreeBSD.ORG
Subject: Re: top/w/vmstat weirdness :-)
In-Reply-To: <Pine.BSF.4.05.9811141412170.27294-100000@porkfriedrice.ny.genx.net>
Message-ID: <Pine.BSI.3.91.981114145257.6441E-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
On Sat, 14 Nov 1998, Alfred Perlstein wrote:
> Generally when i see a "HEADS UP" on the list about some system change
> happening, (specifically the change to the proc struct a few days ago) I:
>
> 1) READ IT
> 2) decided I still want to track -current without sounding silly on the
> list, then I
> 3) "make buildworld"
> 4) make the kernel
> 5) make installworld
> 6) install the new kernel
> 7) reboot
Thanks for the menu - I'll try it - but - I did kind of think all that
was what a make world did. Obviously incorrect. Thanks!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 14:57:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23644
for freebsd-current-outgoing; Sat, 14 Nov 1998 14:57:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.webspan.net (mail.webspan.net [206.154.70.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23637
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 14:57:08 -0800 (PST)
(envelope-from opsys@mail.webspan.net)
Received: from orion.webspan.net (orion.webspan.net [206.154.70.5])
by mail.webspan.net (WEBSPAN/970608) with SMTP id RAA00294;
Sat, 14 Nov 1998 17:56:42 -0500 (EST)
Date: Sat, 14 Nov 1998 17:56:41 -0500 (EST)
From: Open Systems Networking <opsys@mail.webspan.net>
X-Sender: opsys@orion.webspan.net
To: "Steven P. Donegan" <donegan@quick.net>
cc: current@FreeBSD.ORG
Subject: Re: top/w/vmstat weirdness :-)
In-Reply-To: <Pine.BSI.3.91.981114144925.6441D-100000@oldnews.quick.net>
Message-ID: <Pine.BSF.4.02.9811141755580.10120-100000@orion.webspan.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, 14 Nov 1998, Steven P. Donegan wrote:
> The question is - why did a make world NOT do these things. I do a make
> world on this development box just about daily, and for some reason that
> does not seem to really make the world.
Erm a make world doesnt update them?
Try a make clean then a make world?
Chris
--
"You both seem to be ignoring the fact that the networking market is
driven by so-called 'IT professionals' these days, most of whom can't
tell the difference between an ARP and a carp." --Wes Peters
===================================| Open Systems FreeBSD Consulting.
FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186
-----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134
FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net
http://www.freebsd.org | Consulting, Network Engineering, Security
===================================| http://open-systems.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 15:03:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA24070
for freebsd-current-outgoing; Sat, 14 Nov 1998 15:03:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24064
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 15:03:36 -0800 (PST)
(envelope-from donegan@oldnews.quick.net)
Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id PAA06894; Sat, 14 Nov 1998 15:03:13 -0800 (PST)
Date: Sat, 14 Nov 1998 15:03:12 -0800 (PST)
From: "Steven P. Donegan" <donegan@quick.net>
To: Open Systems Networking <opsys@mail.webspan.net>
cc: current@FreeBSD.ORG
Subject: Re: top/w/vmstat weirdness :-)
In-Reply-To: <Pine.BSF.4.02.9811141755580.10120-100000@orion.webspan.net>
Message-ID: <Pine.BSI.3.91.981114145930.6441F-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
If make world did the proper things I wouldn't have wasted everyone's
time :-)
I cvsup the tree daily, make world every few days, and today was the
first time utilities like w, top, ps didn't function correctly. It's not
a big deal - this IS a development box so I don't care that things don't
work correctly - I'm just curious as to why a make world really doesn't.
On Sat, 14 Nov 1998, Open Systems Networking wrote:
> On Sat, 14 Nov 1998, Steven P. Donegan wrote:
>
> > The question is - why did a make world NOT do these things. I do a make
> > world on this development box just about daily, and for some reason that
> > does not seem to really make the world.
>
> Erm a make world doesnt update them?
> Try a make clean then a make world?
>
> Chris
> --
> "You both seem to be ignoring the fact that the networking market is
> driven by so-called 'IT professionals' these days, most of whom can't
> tell the difference between an ARP and a carp." --Wes Peters
>
> ===================================| Open Systems FreeBSD Consulting.
> FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186
> -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134
> FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net
> http://www.freebsd.org | Consulting, Network Engineering, Security
> ===================================| http://open-systems.net
>
>
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 Sat Nov 14 15:14:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA24744
for freebsd-current-outgoing; Sat, 14 Nov 1998 15:14:46 -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 PAA24739
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 15:14:43 -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.1a/8.9.1) with ESMTP id PAA04901;
Sat, 14 Nov 1998 15:15:16 -0800 (PST)
To: "Steven P. Donegan" <donegan@quick.net>
cc: Open Systems Networking <opsys@mail.webspan.net>, current@FreeBSD.ORG
Subject: Re: top/w/vmstat weirdness :-)
In-reply-to: Your message of "Sat, 14 Nov 1998 15:03:12 PST."
<Pine.BSI.3.91.981114145930.6441F-100000@oldnews.quick.net>
Date: Sat, 14 Nov 1998 15:15:15 -0800
Message-ID: <4897.911085315@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I cvsup the tree daily, make world every few days, and today was the
> first time utilities like w, top, ps didn't function correctly. It's not
> a big deal - this IS a development box so I don't care that things don't
> work correctly - I'm just curious as to why a make world really doesn't.
But it does. I haven't seen anything about your postings to suggest
that it does not.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 15:15:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA24998
for freebsd-current-outgoing; Sat, 14 Nov 1998 15:15:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mx2.ews.uiuc.edu (mx2.ews.uiuc.edu [130.126.161.238])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24986
for <freebsd-current@freebsd.org>; Sat, 14 Nov 1998 15:15:39 -0800 (PST)
(envelope-from locke@mcs.net)
Received: from petedorm (isr3193.urh.uiuc.edu [130.126.64.183])
by mx2.ews.uiuc.edu (8.8.8/8.8.8) with SMTP id RAA18548
for <freebsd-current@freebsd.org>; Sat, 14 Nov 1998 17:15:13 -0600
Message-Id: <3.0.5.32.19981114171514.00a154f0@popmail.mcs.net>
X-Sender: locke@popmail.mcs.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Sat, 14 Nov 1998 17:15:14 -0600
To: freebsd-current@FreeBSD.ORG
From: Peter Johnson <locke@mcs.net>
Subject: Help! Recovering from a ELF kernel moveover that didn't work!!
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I decided to move to an ELF kernel today--mistake, as it turns out:
I compiled the kernel as ELF and installed as /kernel.elf, then manually
did a "/boot/loader" at the boot: prompt, aborted the kernel boot, and
typed "boot kernel.elf". That worked perfectly, booting fine with no errors.
Then I did the following: "disklabel -B -b /boot/boot1 -s /boot/boot2 da0a"
(da0a is my / slice).
Now my system just reboots when I try to boot FreeBSD..
note: I'm booting from the Windows NT boot manager.. do I need to update
the boot sector NT keeps in order for this to work?
How can I reverse the disklabel command without being able to boot into
FreeBSD? Should I grab a bootdisk?
Help!! :)
Thanks,
Pete Johnson
locke@mcs.net
-------------------------------------
Peter Johnson
-------------------------------------
locke@mcs.net
http://locke.home.ml.org
PGP Keys available from above address.
-------------------------------------
Freelance C/C++/Java/Pascal/Asm programmer
for DJGPP, Borland, and Watcom compilers
Member of BiLogic demo group
-> http://BiLogic.home.ml.org/
-------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 15:25:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA25702
for freebsd-current-outgoing; Sat, 14 Nov 1998 15:25:33 -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 PAA25696
for <freebsd-current@FreeBSD.ORG>; Sat, 14 Nov 1998 15:25:32 -0800 (PST)
(envelope-from brian@CSUA.Berkeley.EDU)
Received: from localhost (localhost [127.0.0.1])
by smarter.than.nu (8.9.1/8.8.8) with ESMTP id PAA06664;
Sat, 14 Nov 1998 15:25:09 -0800 (PST)
(envelope-from brian@CSUA.Berkeley.EDU)
Date: Sat, 14 Nov 1998 15:25:09 -0800 (PST)
From: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>
X-Sender: brian@smarter.than.nu
To: Peter Johnson <locke@mcs.net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Help! Recovering from a ELF kernel moveover that didn't work!!
In-Reply-To: <3.0.5.32.19981114171514.00a154f0@popmail.mcs.net>
Message-ID: <Pine.BSF.4.05.9811141522440.6244-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 Sat, 14 Nov 1998, Peter Johnson wrote:
> Then I did the following: "disklabel -B -b /boot/boot1 -s /boot/boot2 da0a"
> (da0a is my / slice).
>
> Now my system just reboots when I try to boot FreeBSD..
Your system is like mine (and those of several others), which doesn't like
the new bootblocks. Boot from a FreeBSD floppy and do
"0:wd(0,a)/boot/loader" and the boot prompt, then "disklabel -B da0a" as
root to reinstall the old boot blocks. You can put "/boot/loader" in
boot.config to use the new bootloader until the new bootblocks are fixed.
--
Brian Buchanan brian@smarter.than.nu
brian@CSUA.Berkeley.EDU
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-- Benjamin Franklin, 1759
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 15:32:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA26198
for freebsd-current-outgoing; Sat, 14 Nov 1998 15:32:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.ida.net (mail.ida.net [204.228.203.4])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26193
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 15:32:03 -0800 (PST)
(envelope-from muck@ida.net)
Received: from falcon.hinterlands.com (tc-if7-1.ida.net [208.141.175.106])
by mail.ida.net (8.8.7/8.8.7) with SMTP id QAA01628;
Sat, 14 Nov 1998 16:32:22 -0700 (MST)
Date: Sat, 14 Nov 1998 16:30:41 -0700 (MST)
From: Mike <muck@ida.net>
X-Sender: muck@falcon.hinterlands.com
To: "Steven P. Donegan" <donegan@quick.net>
cc: Open Systems Networking <opsys@mail.webspan.net>, current@FreeBSD.ORG
Subject: Re: top/w/vmstat weirdness :-)
In-Reply-To: <Pine.BSI.3.91.981114145930.6441F-100000@oldnews.quick.net>
Message-ID: <Pine.BSF.3.96.981114162924.4538A-100000@falcon.hinterlands.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, 14 Nov 1998, Steven P. Donegan wrote:
Are you doing a:
cd /usr/obj
chflags -R noschg *
rm -rf *
before you make world?
> If make world did the proper things I wouldn't have wasted everyone's
> time :-)
>
> I cvsup the tree daily, make world every few days, and today was the
> first time utilities like w, top, ps didn't function correctly. It's not
> a big deal - this IS a development box so I don't care that things don't
> work correctly - I'm just curious as to why a make world really doesn't.
>
>
> On Sat, 14 Nov 1998, Open Systems Networking wrote:
>
> > On Sat, 14 Nov 1998, Steven P. Donegan wrote:
> >
> > > The question is - why did a make world NOT do these things. I do a make
> > > world on this development box just about daily, and for some reason that
> > > does not seem to really make the world.
> >
> > Erm a make world doesnt update them?
> > Try a make clean then a make world?
> >
> > Chris
> > --
> > "You both seem to be ignoring the fact that the networking market is
> > driven by so-called 'IT professionals' these days, most of whom can't
> > tell the difference between an ARP and a carp." --Wes Peters
> >
> > ===================================| Open Systems FreeBSD Consulting.
> > FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186
> > -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134
> > FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net
> > http://www.freebsd.org | Consulting, Network Engineering, Security
> > ===================================| http://open-systems.net
> >
> >
>
> 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 Sat Nov 14 15:33:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA26457
for freebsd-current-outgoing; Sat, 14 Nov 1998 15:33:51 -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 PAA26452
for <freebsd-current@FreeBSD.ORG>; Sat, 14 Nov 1998 15:33:50 -0800 (PST)
(envelope-from brian@CSUA.Berkeley.EDU)
Received: from localhost (localhost [127.0.0.1])
by smarter.than.nu (8.9.1/8.8.8) with ESMTP id PAA06678;
Sat, 14 Nov 1998 15:33:28 -0800 (PST)
(envelope-from brian@CSUA.Berkeley.EDU)
Date: Sat, 14 Nov 1998 15:33:28 -0800 (PST)
From: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>
X-Sender: brian@smarter.than.nu
To: Peter Johnson <locke@mcs.net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Help! Recovering from a ELF kernel moveover that didn't work!!
In-Reply-To: <Pine.BSF.4.05.9811141522440.6244-100000@smarter.than.nu>
Message-ID: <Pine.BSF.4.05.9811141532230.6244-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 Sat, 14 Nov 1998, Brian W. Buchanan wrote:
> Your system is like mine (and those of several others), which doesn't like
> the new bootblocks. Boot from a FreeBSD floppy and do
> "0:wd(0,a)/boot/loader" and the boot prompt, then "disklabel -B da0a" as
^^^
s/and/at
--
Brian Buchanan brian@smarter.than.nu
brian@CSUA.Berkeley.EDU
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-- Benjamin Franklin, 1759
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 15:37:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA27075
for freebsd-current-outgoing; Sat, 14 Nov 1998 15:37:05 -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 PAA27070
for <current@freebsd.org>; Sat, 14 Nov 1998 15:37:02 -0800 (PST)
(envelope-from wosch@panke.de.freebsd.org)
Received: (from uucp@localhost)
by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id AAA05949
for current@freebsd.org; Sun, 15 Nov 1998 00:36:40 +0100 (CET)
(envelope-from wosch@panke.de.freebsd.org)
Received: (from wosch@localhost)
by campa.panke.de.freebsd.org (8.8.8/8.8.8) id UAA27356;
Sat, 14 Nov 1998 20:50:04 +0100 (MET)
(envelope-from wosch)
Message-ID: <19981114205002.A27346@panke.de.freebsd.org>
Date: Sat, 14 Nov 1998 20:50:02 +0100
From: Wolfram Schneider <wosch@panke.de.freebsd.org>
To: current@FreeBSD.ORG
Subject: sort option for find
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=azLHFNyN32YCQGCU
X-Mailer: Mutt 0.93.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
--azLHFNyN32YCQGCU
Content-Type: text/plain; charset=us-ascii
I want add a sort option to find(1).
The sort option make it possible to build the locate
database without large (usually 20-100MB) temp files.
`find -s /dir' is a little bit slower than `find /dir | sort'. I don't
think users care if locate.updated runs 5% longer if they save
disk space and error mails.
-s The -s option cause find to traverse the file hierarchies in lex-
icographical order. The output will be sorted too.
--azLHFNyN32YCQGCU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="d.find"
Index: find.1
===================================================================
RCS file: /a/ncvs/src/usr.bin/find/find.1,v
retrieving revision 1.15
diff -u -r1.15 find.1
--- find.1 1998/05/15 11:22:36 1.15
+++ find.1 1998/11/14 19:27:39
@@ -44,7 +44,7 @@
.Sh SYNOPSIS
.Nm find
.Op Fl H | Fl L | Fl P
-.Op Fl Xdx
+.Op Fl Xdsx
.Op Fl f Ar file
.Op Ar file ...
.Ar expression
@@ -121,6 +121,13 @@
to traverse.
File hierarchies may also be specified as the operands immediately
following the options.
+.It Fl s
+The
+.Fl s
+option cause
+.Nm find
+to traverse the file hierarchies in lexicographical order. The
+output will be sorted too.
.It Fl x
The
.Fl x
Index: find.c
===================================================================
RCS file: /a/ncvs/src/usr.bin/find/find.c,v
retrieving revision 1.4
diff -u -r1.4 find.c
--- find.c 1997/03/11 13:48:23 1.4
+++ find.c 1998/11/14 18:43:09
@@ -50,6 +50,8 @@
#include "find.h"
+static int find_compare(const FTSENT **s1, const FTSENT **s2);
+
/*
* find_formplan --
* process the command line and create a "plan" corresponding to the
@@ -140,6 +142,19 @@
}
FTS *tree; /* pointer to top of FTS hierarchy */
+extern int sflag;
+
+/*
+ * find_compare --
+ * A function which be used in fts_open() to order the
+ * traversal of the hierarchy.
+ * This function give you a lexicographical sorted output.
+ */
+static int find_compare(s1, s2)
+ const FTSENT **s1, **s2;
+{
+ return strcoll( (*s1)->fts_name, (*s2)->fts_name );
+}
/*
* find_execute --
@@ -155,7 +170,8 @@
PLAN *p;
int rval;
- if ((tree = fts_open(paths, ftsoptions, (int (*)())NULL)) == NULL)
+ if ((tree = fts_open(paths, ftsoptions,
+ (sflag ? find_compare : NULL) )) == NULL)
err(1, "ftsopen");
for (rval = 0; (entry = fts_read(tree)) != NULL;) {
Index: main.c
===================================================================
RCS file: /a/ncvs/src/usr.bin/find/main.c,v
retrieving revision 1.6
diff -u -r1.6 main.c
--- main.c 1997/05/19 18:16:29 1.6
+++ main.c 1998/11/14 18:23:19
@@ -66,6 +66,7 @@
int isdepth; /* do directories on post-order visit */
int isoutput; /* user specified output operator */
int isxargs; /* don't permit xargs delimiting chars */
+int sflag; /* travel the file hierarchy lexicographical order */
static void usage __P((void));
@@ -84,7 +85,7 @@
p = start = argv;
Hflag = Lflag = 0;
ftsoptions = FTS_NOSTAT | FTS_PHYSICAL;
- while ((ch = getopt(argc, argv, "HLPXdf:x")) != -1)
+ while ((ch = getopt(argc, argv, "HLPXdf:sx")) != -1)
switch (ch) {
case 'H':
Hflag = 1;
@@ -105,6 +106,9 @@
break;
case 'f':
*p++ = optarg;
+ break;
+ case 's':
+ sflag = 1;
break;
case 'x':
ftsoptions |= FTS_XDEV;
--azLHFNyN32YCQGCU--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 17:03:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA04940
for freebsd-current-outgoing; Sat, 14 Nov 1998 17:03:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thelab.hub.org (nat0069.mpoweredpc.net [142.177.188.69])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04935
for <freebsd-current@freebsd.org>; Sat, 14 Nov 1998 17:03:34 -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 VAA21346
for <freebsd-current@freebsd.org>; Sat, 14 Nov 1998 21:03:10 -0400 (AST)
(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Sat, 14 Nov 1998 21:03:10 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: freebsd-current@FreeBSD.ORG
Subject: What file system...
Message-ID: <Pine.BSF.4.05.9811142102370.337-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
MOrning...
Is there any way of finding out which file system is generating
the following error:
swap_pager: I/O error - pagein failed; blkno 26848, size 16384, error 6
vm_fault: pager read error, pid 24135 (ps)
swap_pager: I/O error - pagein failed; blkno 25936, size 16384, error 6
vm_fault: pager read error, pid 24135 (ps)
swap_pager: I/O error - pagein failed; blkno 8328, size 28672, error 6
vm_fault: pager read error, pid 24135 (ps)
swap_pager: I/O error - pagein failed; blkno 14464, size 20480, error 6
vm_fault: pager read error, pid 24135 (ps)
swap_pager: I/O error - pagein failed; blkno 19960, size 4096, error 6
vm_fault: pager read error, pid 24135 (ps)
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 Sat Nov 14 17:18:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA06088
for freebsd-current-outgoing; Sat, 14 Nov 1998 17:18:02 -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 RAA06058
for <freebsd-current@FreeBSD.ORG>; Sat, 14 Nov 1998 17:17:57 -0800 (PST)
(envelope-from lee@st-lcremean.tidalwave.net)
Received: (from lee@localhost)
by st-lcremean.tidalwave.net (8.9.1/8.8.8) id UAA13560;
Sat, 14 Nov 1998 20:17:32 -0500 (EST)
(envelope-from lee)
Message-ID: <19981114201732.A13551@tidalwave.net>
Date: Sat, 14 Nov 1998 20:17:32 -0500
From: Lee Cremeans <lee@st-lcremean.tidalwave.net>
To: The Hermit Hacker <scrappy@hub.org>, freebsd-current@FreeBSD.ORG
Subject: Re: What file system...
Reply-To: lcremean@tidalwave.net
References: <Pine.BSF.4.05.9811142102370.337-100000@thelab.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.05.9811142102370.337-100000@thelab.hub.org>; from The Hermit Hacker on Sat, Nov 14, 1998 at 09:03:10PM -0400
X-OS: FreeBSD 3.0-CURRENT
X-Evil: microsoft.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, Nov 14, 1998 at 09:03:10PM -0400, The Hermit Hacker wrote:
>
> MOrning...
>
> Is there any way of finding out which file system is generating
> the following error:
>
> swap_pager: I/O error - pagein failed; blkno 26848, size 16384, error 6
> vm_fault: pager read error, pid 24135 (ps)
> swap_pager: I/O error - pagein failed; blkno 25936, size 16384, error 6
> vm_fault: pager read error, pid 24135 (ps)
> swap_pager: I/O error - pagein failed; blkno 8328, size 28672, error 6
> vm_fault: pager read error, pid 24135 (ps)
> swap_pager: I/O error - pagein failed; blkno 14464, size 20480, error 6
> vm_fault: pager read error, pid 24135 (ps)
> swap_pager: I/O error - pagein failed; blkno 19960, size 4096, error 6
> vm_fault: pager read error, pid 24135 (ps)
THat's the swap_pager talking, not filesystem code. Messages like this
usually mean you have bad blocks somewhere in your swap partition(s)--in
other words, one of your disks is dying.
--
Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)
A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did
$++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net
http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 17:18:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA06107
for freebsd-current-outgoing; Sat, 14 Nov 1998 17:18:09 -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 RAA06101
for <current@freebsd.org>; Sat, 14 Nov 1998 17:18:05 -0800 (PST)
(envelope-from ggm@azure.dstc.edu.au)
Received: from azure.dstc.edu.au (azure.dstc.edu.au [130.102.176.27])
by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id LAA25223
for <current@freebsd.org>; Sun, 15 Nov 1998 11:17:42 +1000 (EST)
Received: (from ggm@localhost)
by azure.dstc.edu.au (8.8.5/8.8.4)
id LAA01412 for current@freebsd.org; Sun, 15 Nov 1998 11:17:40 +1000 (EST)
Date: Sun, 15 Nov 1998 11:17:40 +1000 (EST)
From: George Michaelson <ggm@dstc.edu.au>
Message-Id: <199811150117.LAA01412@azure.dstc.edu.au>
To: current@FreeBSD.ORG
Subject: once elf transited, does /usr/src/obj/{aout,elf} need to exist?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I've completed the elf transition. If I blow away obj/{aout,elf,usr}
will I get them back?
I assume the aout build is a once-only, and there won't be a need to keep
re-making the compat state?
Hang on. if somebody tweaks something that requires a new libc in elfland
to work, then non-upgraded aout binaries would need to see the change too
wouldn't they?
Bummer. that 150+mb isn't headroom after all...
-George
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 18:00:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA08843
for freebsd-current-outgoing; Sat, 14 Nov 1998 18:00:15 -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 SAA08835
for <freebsd-current@FreeBSD.ORG>; Sat, 14 Nov 1998 18:00:13 -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 UAA20052;
Sat, 14 Nov 1998 20:59:36 -0500 (EST)
Date: Sat, 14 Nov 1998 20:59:36 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: lcremean@tidalwave.net
cc: The Hermit Hacker <scrappy@hub.org>, freebsd-current@FreeBSD.ORG
Subject: Re: What file system...
In-Reply-To: <19981114201732.A13551@tidalwave.net>
Message-ID: <Pine.BSF.4.05.9811142058060.19800-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
Reboot in single-user mode. dd if=/dev/rswap0s1b of=/dev/null for each
swap slice. Stop when you've found out which one it is.
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 Nov 14 18:50:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA11993
for freebsd-current-outgoing; Sat, 14 Nov 1998 18:50:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gw1.pl.cp (ppp-pw23.nttca.com [204.160.176.113])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11986
for <current@freebsd.org>; Sat, 14 Nov 1998 18:50:35 -0800 (PST)
(envelope-from astralblue@usa.net)
Received: from localhost (gene@localhost)
by gw1.pl.cp (8.9.1/8.9.1) with SMTP id SAA02856
for <current@freebsd.org>; Sat, 14 Nov 1998 18:50:10 -0800 (PST)
(envelope-from astralblue@usa.net)
X-Authentication-Warning: gw1.pl.cp: gene owned process doing -bs
Date: Sat, 14 Nov 1998 18:50:10 -0800 (PST)
From: "Eugene M. Kim" <astralblue@usa.net>
X-Sender: gene@gw1.pl.cp
To: FreeBSD-current Mailing List <current@FreeBSD.ORG>
Subject: ``ps: proc size mismatch'' (was Re: top/w/vmstat weirdness :-))
In-Reply-To: <Pine.BSI.3.91.981114100231.6441A-100000@oldnews.quick.net>
Message-ID: <Pine.BSF.4.02A.9811141835080.2806-100000@gw1.pl.cp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
As most of you know, this same question has been asked on this list
several times. (Maybe more than 10 times?) Wouldn't it be helpful to
make the programs that use libkvmstat more friendly? The error message
like:
ps: proc size mismatch (xxxx total, yyyy chunks)
ps: Please consult the manual page for details.
and the manpage like:
CAVEATS
If you see the ``ps: proc size mismatch'' message, you have
to either rebuild the kernel or rebuild the programs that
use libkvmstat (among which ps is included). Refer to the
FreeBSD handbook on how to rebuild them.
will definitely make the users less frustrated.
Thank you,
Eugene
--
Eugene M. Kim <astralblue@usa.net>
"Is your music unpopular? Make it popular; make music
which people like, or make people who like your music."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 20:08:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA17936
for freebsd-current-outgoing; Sat, 14 Nov 1998 20:08:28 -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 UAA17931
for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 20:08: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.1a/8.9.1) with ESMTP id UAA10713;
Sat, 14 Nov 1998 20:09:01 -0800 (PST)
To: "Eugene M. Kim" <astralblue@usa.net>
cc: FreeBSD-current Mailing List <current@FreeBSD.ORG>
Subject: Re: ``ps: proc size mismatch'' (was Re: top/w/vmstat weirdness :-))
In-reply-to: Your message of "Sat, 14 Nov 1998 18:50:10 PST."
<Pine.BSF.4.02A.9811141835080.2806-100000@gw1.pl.cp>
Date: Sat, 14 Nov 1998 20:09:01 -0800
Message-ID: <10710.911102941@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> As most of you know, this same question has been asked on this list
> several times. (Maybe more than 10 times?) Wouldn't it be helpful to
> make the programs that use libkvmstat more friendly? The error message
Yes, it would be. Unfortunately, none of the 10 people who complained
remembered to attach diffs which would abstract the needs of libkvm
consumers to the point where there was no longer a dependency. Make
that 11 people. :-)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 22:29:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA25524
for freebsd-current-outgoing; Sat, 14 Nov 1998 22:29:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25514;
Sat, 14 Nov 1998 22:29:28 -0800 (PST)
(envelope-from dv@dv.ru)
Received: from localhost (dv@localhost)
by xkis.kis.ru (8.9.0/8.9.0) with SMTP id JAA05951;
Sun, 15 Nov 1998 09:29:01 +0300 (MSK)
Date: Sun, 15 Nov 1998 09:29:01 +0300 (MSK)
From: Dmitry Valdov <dv@dv.ru>
X-Sender: dv@xkis.kis.ru
To: Brian Somers <brian@Awfulhak.org>
cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
In-Reply-To: <199811140022.AAA12862@woof.lan.awfulhak.org>
Message-ID: <Pine.BSF.3.95q.981115091659.5678D-100000@xkis.kis.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hmmm. I don't did anything with my 'hostname'. It valid..
I think, I understand the problem. Look here:
If default route exists and connection isn't established than gethostbyname
() trying to get host by name via DNS server which isn't here.
I think You should do anything with it. Please don't advice me to insert my
hostname to /etc/hosts and set 'hosts' first in /etc/host.conf just because
FreeBSD has default with 'bind' prior to 'hosts'.
For what do You want to call function gethostbyname ()? May be it will
better to call it after executing ppp.conf to make user able to 'delete!
default' before gethostbyname () called?
On Sat, 14 Nov 1998, Brian Somers wrote:
> Date: Sat, 14 Nov 1998 00:22:03 +0000
> From: Brian Somers <brian@Awfulhak.org>
> To: Dmitry Valdov <dv@dv.ru>
> Cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
> Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
>
> > Hi!
> >
> >
> > There is gdb's output:
> >
> > 0x280d7ea4 in _poll ()
> > (gdb) bt
> > #0 0x280d7ea4 in _poll ()
> > #1 0x280f4f11 in res_send ()
> > #2 0x280f1c57 in res_query ()
> > #3 0x280f2101 in __res_querydomain ()
> > #4 0x280f1e55 in res_search ()
> > #5 0x280eb5c8 in _gethostbydnsname ()
> > #6 0x280ea23f in gethostbyname2 ()
> > #7 0x280ea1c3 in gethostbyname ()
> > #8 0x805cd4e in ipcp_Init (ipcp=0x8078714, bundle=0x80785f0, l=0x80a3000,
> > parent=0x8078648) at ipcp.c:359
> > #9 0x804c1d1 in bundle_Create (prefix=0x807366d "/dev/tun", type=1,
> > argv=0xefbfdc44) at bundle.c:858
> > #10 0x8061df5 in main (argc=1, argv=0xefbfdc44) at main.c:324
> > #11 0x804a34d in _start ()
>
> The gethostbyname() is the only thing I know in ppp that causes ppp
> to hang - hence my previous message:
>
> [.....]
> > ---------- Forwarded message ----------
> > Date: Thu, 12 Nov 1998 01:08:05 +0000
> > From: Brian Somers <brian@Awfulhak.org>
> > To: Dmitry Valdov <dv@dv.ru>
> > Cc: Brian Somers <brian@FreeBSD.ORG>, current@FreeBSD.ORG
> > Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd)
> >
> > Are you doing anything funny with ``hostname'' on your machine ?
> > The only reports I've heard where ppp hangs at startup is when your
> > ``hostname'' won't resolve (see http://www.FreeBSD.org/FAQ/userppp.html).
> >
> > If this isn't the problem, I'd appreciate if you could build ppp with
> > -g and when it hangs, run ``gdb -p whatever'' and do a ``bt''.
> [.....]
>
> This is what's causing the problem here.
> --
> 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 Sat Nov 14 22:36:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA25931
for freebsd-current-outgoing; Sat, 14 Nov 1998 22:36: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 WAA25911;
Sat, 14 Nov 1998 22:35: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.1a/8.9.1) with ESMTP id WAA26956;
Sat, 14 Nov 1998 22:36:15 -0800 (PST)
To: current@FreeBSD.ORG
cc: peter@FreeBSD.ORG
Subject: hosts before bind in /etc/host.conf?
Date: Sat, 14 Nov 1998 22:36:14 -0800
Message-ID: <26948.911111774@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
A lot of folks dive in and change this first thing since it's annoying
to have a non-connected host bring up a ppp connection just to resolve
your own hostname, and sysinstall is careful about putting entries
into /etc/hosts for this. Any objection to changing the default? For
most folks, it won't even make a difference since all the entries in
/etc/hosts are commented out by default. To shoot yourself in the
foot here still requires deliberate action, and at least /etc/hosts is
a better known location than /etc/host.conf - I still have to explain
that one to folks in this day and age.
Comments?
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 22:47:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA26548
for freebsd-current-outgoing; Sat, 14 Nov 1998 22:47:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from superior.mooseriver.com (superior.mooseriver.com [208.138.27.81])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26521;
Sat, 14 Nov 1998 22:46:15 -0800 (PST)
(envelope-from jgrosch@superior.mooseriver.com)
Received: (from jgrosch@localhost)
by superior.mooseriver.com (8.8.8/8.8.8) id WAA21867;
Sat, 14 Nov 1998 22:45:52 -0800 (PST)
(envelope-from jgrosch)
Message-ID: <19981114224552.A21589@mooseriver.com>
Date: Sat, 14 Nov 1998 22:45:52 -0800
From: Josef Grosch <jgrosch@mooseriver.com>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@FreeBSD.ORG
Cc: peter@FreeBSD.ORG
Subject: Re: hosts before bind in /etc/host.conf?
Reply-To: jgrosch@mooseriver.com
References: <26948.911111774@zippy.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <26948.911111774@zippy.cdrom.com>; from Jordan K. Hubbard on Sat, Nov 14, 1998 at 10:36:14PM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, Nov 14, 1998 at 10:36:14PM -0800, Jordan K. Hubbard wrote:
> A lot of folks dive in and change this first thing since it's annoying
> to have a non-connected host bring up a ppp connection just to resolve
> your own hostname, and sysinstall is careful about putting entries
> into /etc/hosts for this. Any objection to changing the default? For
> most folks, it won't even make a difference since all the entries in
> /etc/hosts are commented out by default. To shoot yourself in the
> foot here still requires deliberate action, and at least /etc/hosts is
> a better known location than /etc/host.conf - I still have to explain
> that one to folks in this day and age.
>
> Comments?
The order should be hosts, named, and then NIS with NIS commented out. The
way we currently have it setup assumes that the machine is running DNS and
that network connectivity is up at the time the machine is coming up. This
is not always the case. I vote YES to fixing this.
Josef
--
Josef Grosch | Another day closer to a | FreeBSD 3.0
jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 14 23:03:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA28100
for freebsd-current-outgoing; Sat, 14 Nov 1998 23:03:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from myname.my.domain (kel237.silk.net [204.244.76.237])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28085;
Sat, 14 Nov 1998 23:03:41 -0800 (PST)
(envelope-from eddie@silk.net)
Received: from localhost (eddie@localhost)
by myname.my.domain (8.8.8/8.8.8) with SMTP id XAA08791;
Sat, 14 Nov 1998 23:09:11 GMT
(envelope-from eddie@silk.net)
X-Authentication-Warning: myname.my.domain: eddie owned process doing -bs
Date: Sat, 14 Nov 1998 23:09:11 +0000 (GMT)
From: Eddie Lawhead <eddie@silk.net>
X-Sender: eddie@myname.my.domain
To: Josef Grosch <jgrosch@mooseriver.com>
cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@FreeBSD.ORG,
peter@FreeBSD.ORG
Subject: Re: hosts before bind in /etc/host.conf?
In-Reply-To: <19981114224552.A21589@mooseriver.com>
Message-ID: <Pine.BSF.4.01.9811142306540.8766-100000@myname.my.domain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I don't know too much about anything but it seems to me that
hosts should be the first one.
My 2 cents
-Eddie
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Eddie H. Lawhead FreeBSD, The Power to Serve.
<eddie@Silk.net> Kelowna, BC, Canada
<eddie@X11.org> #include <stddisclaimer.h>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
On Sat, 14 Nov 1998, Josef Grosch wrote:
#On Sat, Nov 14, 1998 at 10:36:14PM -0800, Jordan K. Hubbard wrote:
#> A lot of folks dive in and change this first thing since it's annoying
#> to have a non-connected host bring up a ppp connection just to resolve
#> your own hostname, and sysinstall is careful about putting entries
#> into /etc/hosts for this. Any objection to changing the default? For
#> most folks, it won't even make a difference since all the entries in
#> /etc/hosts are commented out by default. To shoot yourself in the
#> foot here still requires deliberate action, and at least /etc/hosts is
#> a better known location than /etc/host.conf - I still have to explain
#> that one to folks in this day and age.
#>
#> Comments?
#
#The order should be hosts, named, and then NIS with NIS commented out. The
#way we currently have it setup assumes that the machine is running DNS and
#that network connectivity is up at the time the machine is coming up. This
#is not always the case. I vote YES to fixing this.
#
#
#Josef
#
#--
#Josef Grosch | Another day closer to a | FreeBSD 3.0
#jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses
#
#
#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