From owner-freebsd-current Sun Nov 1 00:59:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA00523
for freebsd-current-outgoing; Sun, 1 Nov 1998 00:59:19 -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 AAA00513
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 00:59:16 -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 TAA05952;
Sun, 1 Nov 1998 19:29:10 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.1/8.9.0) id TAA19428;
Sun, 1 Nov 1998 19:29:08 +1030 (CST)
Message-ID: <19981101192908.D19187@freebie.lemis.com>
Date: Sun, 1 Nov 1998 19:29:08 +1030
From: Greg Lehey <grog@lemis.com>
To: "Kenneth D. Merry" <ken@plutotech.com>,
"John W. DeBoskey" <jwd@unx.sas.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: scsi disk (cam?) problems
References: <199811010132.UAA04810@bb01f39.unx.sas.com> <199811010208.TAA27408@panzer.plutotech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199811010208.TAA27408@panzer.plutotech.com>; from Kenneth D. Merry on Sat, Oct 31, 1998 at 07:08:50PM -0700
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Saturday, 31 October 1998 at 19:08:50 -0700, Kenneth D. Merry wrote:
> John W. DeBoskey wrote...
>> Hi,
>>
>> My -CURRENT system has been experiencing problems since I converted
>> it to cam awhile back. The following show up on my console, and then
>> my disks are useless until I completely shutdown, powerdown my drive
>> array, power it back on, and reboot. I have 4 identical drives configured
>> as a ccd. They have been serving me well more about a year...
>>
>> If anyone has any ideas on how I can track down the problem, please
>> let me know!
>>
>> Thanks,
>> John
>>
>> /dev/ccd0a 2155550 1268428 714678 64% /snap
>> /dev/ccd0b 2155550 1020154 962952 51% /usr/obj
>> /dev/ccd0d 17244630 12876242 2988818 81% /pub
>>
>> Snipped from messages: (This kernel was built on the 28th), I'm now on
>> a kernel built Oct 31.
> [ ... ]
>
>> Oct 30 10:52:35 FreeBSD /kernel: (da2:ahc0:0:3:0): Invalidating pack
>> Oct 30 10:52:35 FreeBSD /kernel: (da2:ahc0:0:3:0): Invalidating pack
>
> Well, what's happening here is that one of your disks is returning an
> error, and keeps returning that error. Reads and writes in the da driver
> have a retry count of 4. So by the time we print out the message above,
> the command has already been retried four times. We may also have taken a
> number of error recovery actions to try to bring the device back.
>
> Because your disk is in a CCD array, though, you won't be able to access
> the CCD array when one disk in the array is marked as invalid.
>
> For some reason, though, the sense information for the error in question
> isn't getting printed out. It may be that there's a bug in the sense code
> table somewhere.
>
> How often does this happen?
FWIW, I can reproduce this message (and usually lack of sense
information) at will by pulling a data connector during a transfer
(why? I'm testing Vinum, which *can* recover from this situation :-).
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 1 01:22:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA02957
for freebsd-current-outgoing; Sun, 1 Nov 1998 01:22:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02950
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 01:22:52 -0800 (PST)
(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id LAA05107;
Sun, 1 Nov 1998 11:22:18 +0200 (SAT)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199811010922.LAA05107@zibbi.mikom.csir.co.za>
Subject: Re: IPv6 in -current
In-Reply-To: <199810301848.NAA04753@khavrinen.lcs.mit.edu> from Garrett Wollman at "Oct 30, 98 01:48:39 pm"
To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman)
Date: Sun, 1 Nov 1998 11:22:18 +0200 (SAT)
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
>
> >> > * Full IPv6 implementation in-kernel and libc!
> >> * Complete single-copy TCP/IP implementation
>
> > And even better if we could list both. :-) I think the needs of the
> > FreeBSD group is diverse enough that this isn't unreasonable.
>
> The needs are one thing; the capabilities quite another.
Well I'm not sure what you mean with this, but if it is lack of manpower
to do it, Itojun from the Kame team did say that he would do the
integration into FreeBSD and maintain it (and he already is a committer)
and someone said that the INRIA guys was also prepared to do it. So it
shouldn't take up your or any of the other's (that aren't interested in
IPv6 yet) time, except maybe in the beginning to help decide which stack to
use and maybe where in the tree to put things or things like that.
It's not a question of "if we are going to support IPv6", but "when are
we going to support IPv6"... except if we are going to obsolete ourselves.
And at the pace some of our things take, I think the sooner we do it, the
better, because then we do get more time to integrate everything, like
adding support for IPv6 to the rest of our code like ipfw and ipfilter.
But I give up for now and will try again in a few months time, although
I expect that we will see a IPv6 stack committed in the middle of one of
out BETA cycles in the future. :-)
John
--
John Hay -- John.Hay@mikom.csir.co.za
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 01:34:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA03804
for freebsd-current-outgoing; Sun, 1 Nov 1998 01:34:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from marvin.spacequest.hs (in17.fto.de [193.197.153.146])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03798
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 01:34:49 -0800 (PST)
(envelope-from hschaefer@fto.de)
Received: from daneel.spacequest.hs (daneel.spacequest.hs [192.168.0.98])
by marvin.spacequest.hs (8.8.8/8.8.7) with ESMTP id VAA25122;
Sat, 31 Oct 1998 21:40:48 +0100 (CET)
(envelope-from hschaefer@fto.de)
Date: Sat, 31 Oct 1998 21:39:38 +0100 (CET)
From: Heiko Schaefer <hschaefer@fto.de>
X-Sender: heiko@daneel.spacequest.hs
To: Heiko Schaefer <hschaefer@fto.de>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Problem with SCSI Harddisk
In-Reply-To: <Pine.BSF.4.05.9810241527150.253-100000@daneel.spacequest.hs>
Message-ID: <Pine.BSF.4.05.9810312124590.1011-100000@daneel.spacequest.hs>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi FreeBSD-current comunity again,
as no one answered to my question (that i posted here a week ago), i
figured out that either this is the wrong place to ask, or no one found
this important or no one had anything to say about it.
...just in case anyone has a similar problem sometime, i wanted to write
about what i tried, and how i finally found a 'workaround' to my problem
today (though it feels a bit funny replying to one's own mails :)).
here's the problem once again:
> I am using FreeBSD 3.0-CURRENT (of today), and have a problem with one of
> my scsi-harddisks. /var/log/messages says:
>
> Oct 24 10:00:56 daneel /kernel: (da3:ahc0:0:3:0): SCB 0xe1 - timed out
> while idle, LASTPHASE == 0x1, SCSISIGI == 0x0
> Oct 24 10:00:56 daneel /kernel: SEQADDR == 0xb
> Oct 24 10:00:56 daneel /kernel: SSTAT1 == 0xa
> Oct 24 10:00:56 daneel /kernel: (da3:ahc0:0:3:0): Queuing a BDR SCB
> Oct 24 10:00:56 daneel /kernel: (da3:ahc0:0:3:0): Bus Device Reset Message
> Sent
> Oct 24 10:00:56 daneel /kernel: (da3:ahc0:0:3:0): no longer in timeout,
> status = 34b
> Oct 24 10:00:56 daneel /kernel: ahc0: Bus Device Reset on A:3. 64 SCBs
> aborted
> Oct 24 10:00:56 daneel /kernel: (da3:ahc0:0:3:0): tagged openings now 64
>
>
> this message is then repeated for zillions of times (exactly once every
> 60 seconds), once it has occured once (it occurs for the first time, when
> the harddisk is used a bit more heavily). eventually the whole system
> hangs (responds to ping, but not to telnet or anything similar, although
> the filesystem on the harddisk contains no part of the system, just data
> of a samba-fileserver).
i am now quite sure, that the problem started occuring, when i switched
from 2.2-STABLE to 3.0-CURRENT (i.e. from the old scsi driver to cam ?!).
the first thing i tried to get rid of the messages (and system hangs), i
downgraded my system from 3.0-CURRENT (of about 25.10.98) to 3.0-RELEASE
by cvsup'ing and making world and a new kernel, but that did not help.
then i decided to use another scsi controller.
after replacing the 2940UW (a bit older) with a 2940U (quite new), the
problem seems to have disappeard.
the problem occured when using this one:
> ahc0: <Adaptec 2940 Ultra SCSI adapter> rev 0x00 int a irq 10 on pci0.12.0
> ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
(but funnily only with one of my four harddisks - a cheap 5 1/4" seagate
9GB harddisk: da3: <SEAGATE SX910800N 8511> ... somehow the 2940UW
didn't 'like' this harddisk ?! :> ).
the controller that i now use is:
ahc0: <Adaptec 2940A Ultra SCSI adapter> rev 0x01 int a irq 10 on
pci0.12.0
ahc0: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs
maybe this is a known problem ?!
if not, is it likely to be a hardware defect of some kind, or is it a bug
in freebsd ?
am i supposed (would it help) to report this to some developer (or are all
developers reading this list ?)
have a nice day,
Heiko
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 02:00:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA05924
for freebsd-current-outgoing; Sun, 1 Nov 1998 02:00:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05908
for <freebsd-current@freebsd.org>; Sun, 1 Nov 1998 02:00:01 -0800 (PST)
(envelope-from jabley@buddha.clear.net.nz)
Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id WAA08030; Sun, 1 Nov 1998 22:59:55 +1300 (NZDT)
Received: (from jabley@localhost)
by buddha.clear.net.nz (8.9.1/8.9.1) id WAA29924
for freebsd-current@freebsd.org; Sun, 1 Nov 1998 22:59:54 +1300 (NZDT)
Message-ID: <19981101225954.A29897@clear.co.nz>
Date: Sun, 1 Nov 1998 22:59:54 +1300
From: Joe Abley <jabley@clear.co.nz>
To: freebsd-current@FreeBSD.ORG
Subject: Re: kernel compile problem
References: <XFMail.981031201737.asmodai@wxs.nl> <Pine.BSF.4.05.9811010654560.3668-100000@gina.swimsuit.internet.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.05.9811010654560.3668-100000@gina.swimsuit.internet.dk>; from Leif Neland on Sun, Nov 01, 1998 at 07:44:52AM +0100
X-Files: the Truth is Out There
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 01, 1998 at 07:44:52AM +0100, Leif Neland wrote:
>
> Is the problem that committing isn't 'atomical'?
>
> How about if the committer started by committing
> /usr/src/DONT_MAKE_WORLD_NOW
> then committed various stuff, then removed
> /usr/src/DONT_MAKE_WORLD_NOW
> This file could contain an explanation why the world shouldn't be made.
>
> The makefile should then check for the existance of this file.
>
> This could be implemented right now. It won't require updating cvsup and
> cvsupd.
>
> But this will give problems when several people are updating different
> parts of the tree...
So we need a semaphore; however, a single lock file with a counter in it
doesn't sound very practical for cvsup.
How about a directory called "lock" in whatever part of the source tree
is appropriate, into which committers deposit a file named with their e-mail
address, containing a description of why the source tree is locked?
bsd.subdir.mk could check for files within this subdirectory and fail
quoting the contents of any files that are present.
The same branch of the tree could be locked by more than one committer
(since their respective lock files would have different names).
Having lock directories at appropriate depths in the source tree would
be better than one "don't make world" lock file -- that way if I want
to rebuild and reinstall /usr/src/usr.bin/ I won't be affected by a
transient commit lock in /usr/src/usr.sbin/ (for example).
If no "lock" subdirectory is present, this should be interpreted as
"there are no locks for this branch".
Just an idea :) Whaddayathink?
Joe
--
Joe Abley <jabley@clear.co.nz> Tel +64 9 912-4065, Fax +64 9 912-5008
Network Architect, CLEAR Net http://www.clear.net.nz/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 03:17:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA16956
for freebsd-current-outgoing; Sun, 1 Nov 1998 03:17:12 -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 DAA16932
for <current@freebsd.org>; Sun, 1 Nov 1998 03:16:58 -0800 (PST)
(envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp)
Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:hzbWdVmtCo2n79KURaAD1jcvc3lmwvry@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 UAA27736;
Sun, 1 Nov 1998 20:16:20 +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 UAA15627; Sun, 1 Nov 1998 20:17:43 +0900 (JST)
Message-Id: <199811011117.UAA15627@zodiac.mech.utsunomiya-u.ac.jp>
To: Dan Nelson <dnelson@emsphone.com>
cc: Alfred Perlstein <bright@hotjobs.com>, current@FreeBSD.ORG,
Mike Smith <mike@smith.net.au>, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: if anyone is interested VESA seems broken.
In-reply-to: Your message of "Fri, 30 Oct 1998 15:47:41 CST."
<19981030154741.A18571@emsphone.com>
References: <Pine.BSF.4.05.9810301442320.389-100000@porkfriedrice.ny.genx.net>
<19981030154741.A18571@emsphone.com>
Date: Sun, 01 Nov 1998 20:17:42 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> VESA: mode:0x109, flags:0x000b, T 132x25, font:8x16
>> VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k
>> VESA: mode:0x10b, flags:0x000b, T 132x50, font:8x8
>> VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k
>> VESA: mode:0x10c, flags:0x000b, T 132x60, font:8x8
>> VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k
>
>Your card definitely should be able to do 132x50, since it claims to
>support it here. Maybe check to see that vidcontrol and syscons.c
>handle them correctly (I don't have access to 3.0 at the moment)
So long as 132x50 and 132x60 modes are listed in "vidcontrol -i mode"
and you have loaded 8x8 font, vidcontrol and syscons should be able
to set these modes.
Kazu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 03:39:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA20733
for freebsd-current-outgoing; Sun, 1 Nov 1998 03:39:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA20720
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 03:39:08 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from diabolique.ninth-circle.org ([195.121.59.238])
by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA19B9; Sun, 1 Nov 1998 11:39:02 +0100
Message-ID: <XFMail.981101124252.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: <199810311915.DAA21351@spinner.netplex.com.au>
Date: Sun, 01 Nov 1998 12:42:52 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Peter Wemm <peter@netplex.com.au>
Subject: Re: sys/msdosfs problems?
Cc: FreeBSD Current <current@FreeBSD.ORG>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
OK Peter,
no more problems in the msdosfs as far as I am able to determine...
so ye can spend more time with yer kid ;)
Thanks mate,
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 1 05:02:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA02667
for freebsd-current-outgoing; Sun, 1 Nov 1998 05:02:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02659
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 05:02:18 -0800 (PST)
(envelope-from rkw@nomad.dataplex.net)
Received: from localhost (rkw@localhost)
by nomad.dataplex.net (8.9.1/8.9.1) with ESMTP id HAA08685;
Sun, 1 Nov 1998 07:02:10 -0600 (CST)
(envelope-from rkw@nomad.dataplex.net)
Date: Sun, 1 Nov 1998 07:02:10 -0600 (CST)
From: User RKW <rkw@nomad.dataplex.net>
To: Joe Abley <jabley@clear.co.nz>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: kernel compile problem
In-Reply-To: <19981101225954.A29897@clear.co.nz>
Message-ID: <Pine.BSF.4.05.9811010633120.8635-100000@nomad.dataplex.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>From the point of view of the users, a locking mechanism along these lines
would be fine. However, there are SERIOUS complications relating to the
archiving and distribution of the source tree. If the locks are maintained
as files in the tree, they would further bloat the already unwieldly tree.
I do like the idea of having bsd.subdir.mk recognize parts of the tree to
avoid. However, the locks, as described, are likely to get in the way of
the developer who is testing his changes in order to decide if he can
release the lock.
On Sun, 1 Nov 1998, Joe Abley wrote:
> On Sun, Nov 01, 1998 at 07:44:52AM +0100, Leif Neland wrote:
> >
> > Is the problem that committing isn't 'atomical'?
Generally, yes.
Worse, a commiter sometimes makes faulty updates which, although he
thinks that they are complete, are missing something. This may well
be the result of differences in his environment and that of someone
who is extracting from the master tree.
> How about a directory called "lock" in whatever part of the source tree
> is appropriate,
".locks" might be more appropriate.
> into which committers deposit a file named with their e-mail
> address, containing a description of why the source tree is locked?
>
> bsd.subdir.mk could check for files within this subdirectory and fail
> quoting the contents of any files that are present.
>
> The same branch of the tree could be locked by more than one committer
> (since their respective lock files would have different names).
>
> Having lock directories at appropriate depths in the source tree would
> be better than one "don't make world" lock file -- that way if I want
> to rebuild and reinstall /usr/src/usr.bin/ I won't be affected by a
> transient commit lock in /usr/src/usr.sbin/ (for example).
>
> If no "lock" subdirectory is present, this should be interpreted as
> "there are no locks for this branch".
>
> Just an idea :) Whaddayathink?
Terry (and I) would argue that the committer should not be allowed to
remove the lock himself. That privledge/duty would belong to the QA
dept whose daemon would make at least some rudimentary checks before
pulling the lock.
Another approach would be to place the cvsup distribution behind a
transaction processor which would serially commit atomic changes.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 05:24:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA07094
for freebsd-current-outgoing; Sun, 1 Nov 1998 05:24:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07084
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 05:24:27 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from diabolique.ninth-circle.org ([195.121.58.216])
by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA47FA; Sun, 1 Nov 1998 13:24:19 +0100
Message-ID: <XFMail.981101142809.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: <199811010226.SAA24541@austin.polstra.com>
Date: Sun, 01 Nov 1998 14:28:09 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: John Polstra <jdp@polstra.com>
Subject: Re: cvsup .4.2
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi John,
On 01-Nov-98 John Polstra wrote:
>
> Please let me know what version of FreeBSD you're running. Also
3.0-CURRENT, cvsupped every day.
> please send me the output of:
>
> ident /usr/include/sys/sem.h
[diabolique] asmodai $ ident /usr/include/sys/sem.h
/usr/include/sys/sem.h:
$Id: sem.h,v 1.15 1998/07/15 02:32:32 bde Exp $
$NetBSD: sem.h,v 1.5 1994/06/29 06:45:15 cgd Exp $
> and
>
> grep define /usr/include/osreldate.h
[diabolique] asmodai $ grep define /usr/include/osreldate.h
#define __FreeBSD_version 300006
> Then I can help you fix it.
Might also be relevant to my Attic/cvsup make world problems... Gonna do yer
suggestion and then try it all again... I'll let ye know. In the mean time:
thanks.
> PS - CVSup problems really should be reported to <cvsup-bugs@polstra.com>.
Ah, okies, thanks for telling =)
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 1 05:24:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA07095
for freebsd-current-outgoing; Sun, 1 Nov 1998 05:24:30 -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 FAA07079
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 05:24:24 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from diabolique.ninth-circle.org ([195.121.58.216])
by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA4901; Sun, 1 Nov 1998 14:24:16 +0100
Message-ID: <XFMail.981101142806.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: <199810311902.LAA22746@austin.polstra.com>
Date: Sun, 01 Nov 1998 14:28:06 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: John Polstra <jdp@polstra.com>
Subject: Re: Another compile error
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi John,
On 31-Oct-98 John Polstra wrote:
> But there shouldn't be any directories in your tree named "Attic", and
> there shouldn't be any files named "*,v". I think that at some
> point when you were first experimenting with CVSup, you must have
> done an update without the "tag=." statement in your supfile.
Hmmm... Noting =)
> I recommend that you do this to clean it up:
>
> cd /src
> find . \( -name '*,v' -o -name .depend -o -type l \) -print | xargs rm -f
I went from 78% capacity to 33% on my 1 GB slice for cvsup ;)
> find -d . -name Attic | xargs rm -rf
that also cleaned some stuff...
> cd /usr/obj
> rm -rf * # (You will get some error messages -- don't worry
Jups, with the libs...
> chflags -R 0 *
> rm -rf * # (Yes, again)
to get rid of the last remnants... gotcha ;)
> Now do another CVSup update just for good measure. Then try your
> make world, and I think it will work this time.
OK, going to do it while I am sending this mail...
> Good luck,
I needed it? =)
Thanks, let ye know how it went...
> --
> 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
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 1 05:38:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA08203
for freebsd-current-outgoing; Sun, 1 Nov 1998 05:38:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08197
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 05:38:49 -0800 (PST)
(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
by pcnet1.pcnet.com (8.8.7/PCNet) id IAA02419;
Sun, 1 Nov 1998 08:38:39 -0500 (EST)
Date: Sun, 1 Nov 1998 08:38:39 -0500 (EST)
From: Daniel Eischen <eischen@vigrid.com>
Message-Id: <199811011338.IAA02419@pcnet1.pcnet.com>
To: jkh@time.cdrom.com, lists@tar.com
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
Cc: current@FreeBSD.ORG, jb@cimlogic.com.au
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Richard Seaman, Jr. wrote:
> On Sat, 31 Oct 1998 14:08:43 -0800, Jordan K. Hubbard wrote:
>
> >I agree. While not perhaps adopting the perfect approach, at least
> >Richard brings some very welcome *movement* to an issue which has been
> >stalled for a regrettably long period of time. Let's try to run
> >(cooperatively) with this and hopefully arrive at some working,
> >architecturally clean kernel threads for FreeBSD!
>
> Just to be clear. I'm happy to co-operate and share code with anyone.
> In fact, I'd be happy for someone else to just handle it all. In the
> absence of someone else will to handle it all, I'm happy to contribute
> what I can.
>
> The *only* reason I'd be hesitant to share any code at this moment
> is that its still pretty messy, and I'd be embarrassed, and since
> its barely tested, people would rightfully shoot all kinds of holes
> in it. When its in a better state I'd be happy to post it somewhere
> where anyone can whack at it.
>
I'd like to help in this effort, but I'd first like to see
exactly what threading model is desired. Do we want a Solaris
lightweight process model with the ability have both bound
and unbound user threads? Or do we want libpthread to keep
a one-one mapping of threads to kernel threads?
After some decision on what direction kernel threads should
take, we can then talk about the design and implementation.
Dan Eischen
eischen@vigrid.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 1 05: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 FAA10069
for freebsd-current-outgoing; Sun, 1 Nov 1998 05:53:56 -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 FAA10057
for <current@freebsd.org>; Sun, 1 Nov 1998 05:53:54 -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 0zZEbk-00004B-00; Fri, 30 Oct 1998 13:28:52 +0000
To: chet@po.CWRU.Edu
Cc: chuckr@mat.net, Kurt@OpenLDAP.Org, current@FreeBSD.ORG
Subject: Re: Changing sh for compatibility sake
References: <981027145600.AA08055.SM@nike.ins.cwru.edu>
From: Dom Mitchell <dom@myrddin.demon.co.uk>
In-Reply-To: Chet Ramey's message of "Tue, 27 Oct 1998 09:56:00 -0500"
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Date: Fri, 30 Oct 1998 13:28:52 +0000
Message-Id: <E0zZEbk-00004B-00.qmail@myrddin.demon.co.uk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Chet Ramey <chet@nike.ins.cwru.edu> writes:
> > Have you ever seen an installer script written by a company that
> > *didn't* supply the entire OS, be written in any shell BUT sh?
>
> Checkpoint writes all of its Firewall-1 installation (and other)
> scripts in csh.
As did the veritas netbackup I recently installed at work; it's quite
a disturbing trend.
-Dom
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 06:19:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA12934
for freebsd-current-outgoing; Sun, 1 Nov 1998 06:19:39 -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 GAA12928
for <current@freebsd.org>; Sun, 1 Nov 1998 06:19:38 -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 JAA14768;
Sun, 1 Nov 1998 09:22:20 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Sun, 1 Nov 1998 09:22:20 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
cc: current@FreeBSD.ORG
Subject: Re: if anyone is interested VESA seems broken.
In-Reply-To: <199811011117.UAA15627@zodiac.mech.utsunomiya-u.ac.jp>
Message-ID: <Pine.BSF.4.05.9811010921260.9417-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 i don't think freebsd by default loads a 8x8 font, i didn't realize
this. it'd be nice however if vidcontrol had some way to report this.
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 Sun, 1 Nov 1998, Kazutaka YOKOTA wrote:
>
> >> VESA: mode:0x109, flags:0x000b, T 132x25, font:8x16
> >> VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k
> >> VESA: mode:0x10b, flags:0x000b, T 132x50, font:8x8
> >> VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k
> >> VESA: mode:0x10c, flags:0x000b, T 132x60, font:8x8
> >> VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k
> >
> >Your card definitely should be able to do 132x50, since it claims to
> >support it here. Maybe check to see that vidcontrol and syscons.c
> >handle them correctly (I don't have access to 3.0 at the moment)
>
> So long as 132x50 and 132x60 modes are listed in "vidcontrol -i mode"
> and you have loaded 8x8 font, vidcontrol and syscons should be able
> to set these modes.
>
> Kazu
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 06:22:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA13160
for freebsd-current-outgoing; Sun, 1 Nov 1998 06:22:04 -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 GAA13153
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 06:22:02 -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 GAA18897;
Sun, 1 Nov 1998 06:22:00 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Mike Smith <mike@smith.net.au>
cc: Andrzej Bialecki <abial@nask.pl>, current@FreeBSD.ORG
Subject: Re: BootForth (was Re: New boot loader and alternate kernels)
In-reply-to: Your message of "Sat, 31 Oct 1998 21:37:12 PST."
<199811010537.VAA01330@dingo.cdrom.com>
Date: Sun, 01 Nov 1998 06:21:59 -0800
Message-ID: <18893.909930119@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> So, how do I integrate it into the loader? Do we want to make it
> optional? Do we want to strip the loader back to the bare essentials
> and use BootFORTH for as much as possible? Is a "middle road" approach
> preferred?
Well, you could probably save some space by registering all your existing
builtins as forth words and chucking the existing interpreter in favor
of the more traditional INTERPRET word. Not sure how you'd do that initial
timeout behavior thing though - probably some gross hack. :-)
> Any Forth hackers want to play with something new and funky? In
> particular, some ideas on "standard" system-interface words would be
> handy.
If you get it to the point where it's launching from the boot blocks,
I'd certainly be willing to look into some of the ergnonomic and
extensibility issues.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 06:38:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA14351
for freebsd-current-outgoing; Sun, 1 Nov 1998 06:38:52 -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 GAA14345
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 06:38:50 -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 JAA01424;
Sun, 1 Nov 1998 09:37:41 -0500 (EST)
Date: Sun, 1 Nov 1998 09:37:41 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: John Hay <jhay@mikom.csir.co.za>
cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, current@FreeBSD.ORG
Subject: Re: IPv6 in -current
In-Reply-To: <199811010922.LAA05107@zibbi.mikom.csir.co.za>
Message-ID: <Pine.BSF.4.05.9811010922160.306-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, 1 Nov 1998, John Hay wrote:
> >
> > >> > * Full IPv6 implementation in-kernel and libc!
> > >> * Complete single-copy TCP/IP implementation
> >
> > > And even better if we could list both. :-) I think the needs of the
> > > FreeBSD group is diverse enough that this isn't unreasonable.
> >
> > The needs are one thing; the capabilities quite another.
OK, is this all true then?
1) We all want IPv6 added to the kernel.
2) There are two good contenders for the role of provider for this code,
and they've both given quite a bit of work. They both could and
would have their own committer do the work.
3) One reason for the delay, then, is a reasonable unwillingness to
choose between 2 good possibilities (and possibly insult the losing
team of developers, who clearly don't deserve any kind of insult).
Would it be a reasonable thing to ask, that there be held an electronic
debate? It need not be broadcast realtime ... the idea being that each
team of developers be given the clearest possible chance to put forward
their ideas in a sort of a debate-type encounter. This could be done
via email to a 3rd party, a moderator, who would accumulate the results.
If it was done via email, then (although it would be slower) it would
not turn on momentary mistakes in phrasing so much as ability to present
themselves; such a dialog could take up to a week or more to actually
accumulate some presentable weight.
At the end of some prearranged time, or on agreement (earlier) of both
participants that they've given their best shots, the results could be
made public. A decision could be made by a prequalified user base,
either everyone who registers (register for voting? what an idea) or
maybe committers.
This would serve to give the ideas their best airing, allow the
developers to present their cases in the lowest possible pressure
consistent with public disclosure, and probably give the loser at least
the feeling that they'd certainly been listened to, so their would be
less likelihood of injured feelings. And, FreeBSD would most likely to
get the best IPv6 implementation from it.
----------------------------+-----------------------------------------------
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 1 06:52:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA16246
for freebsd-current-outgoing; Sun, 1 Nov 1998 06:52:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16239
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 06:52:36 -0800 (PST)
(envelope-from karpen@ocean.campus.luth.se)
Received: (from karpen@localhost)
by ocean.campus.luth.se (8.9.1/8.9.1) id PAA21479;
Sun, 1 Nov 1998 15:47:20 +0100 (CET)
(envelope-from karpen)
From: Mikael Karpberg <karpen@ocean.campus.luth.se>
Message-Id: <199811011447.PAA21479@ocean.campus.luth.se>
Subject: Re: New boot loader and alternate kernels
In-Reply-To: <199810302013.MAA01772@dingo.cdrom.com> from Mike Smith at "Oct 30, 98 12:13:09 pm"
To: mike@smith.net.au (Mike Smith)
Date: Sun, 1 Nov 1998 15:47:20 +0100 (CET)
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
According to Mike Smith:
> > > (Yes, I agree that Forth would be more powerful. Compromises...)
> >
> > Ah, well. I guess I'm proposing Forth so strongly because it's so powerful
> > and compact, and fast... and so incredibly extensible when you need it. No
> > need to reinvent the same things each time, writing yet another
> > incompatible language...
> >
> > I think this is important opportunity - let's not miss it without good
> > reasons... As I said, there are people among us who can even write small
> > enough Forth kernel for our purposes.
>
> I have no desire to miss it. Give me a compact Forth interpreter that
> links against libstand and you'll be seeing it everywhere Real Soon.
Eeep! Umm... what exactly does this mean? I mean... I don't know anyone
that knows forth... lots of people know sh. And a logical special
language (whic resembles sh and the other script languages) is not
real hard to learn either. Why mess it up and get forth in there? And
to do what exactly?
/Mikael
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 07:03:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA18002
for freebsd-current-outgoing; Sun, 1 Nov 1998 07:03:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17996
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 07:03:02 -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 QAA18028;
Sun, 1 Nov 1998 16:01:01 +0100 (CET)
To: Mikael Karpberg <karpen@ocean.campus.luth.se>
cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Sun, 01 Nov 1998 15:47:20 +0100."
<199811011447.PAA21479@ocean.campus.luth.se>
Date: Sun, 01 Nov 1998 16:01:00 +0100
Message-ID: <18026.909932460@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>Eeep! Umm... what exactly does this mean? I mean... I don't know anyone
>that knows forth... lots of people know sh. And a logical special
>language (whic resembles sh and the other script languages) is not
>real hard to learn either. Why mess it up and get forth in there? And
>to do what exactly?
The scoop about forth is that you can implement it in virtually
no bytes (well, physically too of course.)
The "Open" boot prom on Suns and the various spinoffs from that use
forth for that reason. It's compact, it can be made machine independent
and there is a standard (several actually) so you don't have to invent
the host plate and the deep water all over again.
--
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 1 07: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 HAA19644
for freebsd-current-outgoing; Sun, 1 Nov 1998 07:18:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19638
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 07:18:48 -0800 (PST)
(envelope-from rkw@nomad.dataplex.net)
Received: from localhost (rkw@localhost)
by nomad.dataplex.net (8.9.1/8.9.1) with ESMTP id JAA17201;
Sun, 1 Nov 1998 09:18:28 -0600 (CST)
(envelope-from rkw@nomad.dataplex.net)
Date: Sun, 1 Nov 1998 09:18:28 -0600 (CST)
From: User RKW <rkw@nomad.dataplex.net>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: Mike Smith <mike@smith.net.au>, Andrzej Bialecki <abial@nask.pl>,
current@FreeBSD.ORG
Subject: Re: BootForth (was Re: New boot loader and alternate kernels)
In-Reply-To: <18893.909930119@time.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811010910270.17193-100000@nomad.dataplex.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, 1 Nov 1998, Jordan K. Hubbard wrote:
> > So, how do I integrate it into the loader? Do we want to make it
> > optional? Do we want to strip the loader back to the bare essentials
> > and use BootFORTH for as much as possible? Is a "middle road" approach
> > preferred?
>
> Well, you could probably save some space by registering all your existing
> builtins as forth words and chucking the existing interpreter in favor
> of the more traditional INTERPRET word. Not sure how you'd do that initial
> timeout behavior thing though - probably some gross hack. :-)
To make it small, that is the approach I would follow. Mixing languages
leads to "bloat" because you end up supporting multiple ways to accomplish
the same thing. KISS.
As for the timeout, run a "word" that delays until its counter runs out or
it finds a key. When that routine returns, test ?KEY to either read the
actual input or fake it in the case of a timeout.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 07:30:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA20741
for freebsd-current-outgoing; Sun, 1 Nov 1998 07:30:18 -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 HAA20734
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 07:30:14 -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 XAA25055;
Sun, 1 Nov 1998 23:29:40 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811011529.XAA25055@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Daniel Eischen <eischen@vigrid.com>
cc: lists@tar.com, current@FreeBSD.ORG, jb@cimlogic.com.au
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
In-reply-to: Your message of "Sun, 01 Nov 1998 08:38:39 EST."
<199811011338.IAA02419@pcnet1.pcnet.com>
Date: Sun, 01 Nov 1998 23:29:39 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Daniel Eischen wrote:
> Richard Seaman, Jr. wrote:
> > On Sat, 31 Oct 1998 14:08:43 -0800, Jordan K. Hubbard wrote:
> >
> > >I agree. While not perhaps adopting the perfect approach, at least
> > >Richard brings some very welcome *movement* to an issue which has been
> > >stalled for a regrettably long period of time. Let's try to run
> > >(cooperatively) with this and hopefully arrive at some working,
> > >architecturally clean kernel threads for FreeBSD!
> >
> > Just to be clear. I'm happy to co-operate and share code with anyone.
> > In fact, I'd be happy for someone else to just handle it all. In the
> > absence of someone else will to handle it all, I'm happy to contribute
> > what I can.
> >
> > The *only* reason I'd be hesitant to share any code at this moment
> > is that its still pretty messy, and I'd be embarrassed, and since
> > its barely tested, people would rightfully shoot all kinds of holes
> > in it. When its in a better state I'd be happy to post it somewhere
> > where anyone can whack at it.
> >
>
> I'd like to help in this effort, but I'd first like to see
> exactly what threading model is desired. Do we want a Solaris
> lightweight process model with the ability have both bound
> and unbound user threads? Or do we want libpthread to keep
> a one-one mapping of threads to kernel threads?
I'm not familiar with Solaris threads but have seen the man pages for the
SVR4.2-whatever-it-is-this-week as used in Unixware.
What I had in mind was something along the lines of:
- the kernel context switching entity would become a 'thread' rather than
a 'proc'.
- a "process" (struct proc) would have one or more threads, all using the
same address space, pid, signals, etc.
- The logistics of doing this are ugly. I don't expect that a global
's/sturct proc/struct thread/g' would go down well.
- the boundaries between the present 'struct proc', pcb, upages, etc would
get muddied a bit in the process. The context that a thread would need
would be something like a superset of the pcb at present.
- A thread would have just enough context for making syscalls etc.
- context switching between threads would be bloody quick, as good or
better than switching between rfork shared address space siblings.
- There would be one kernel stack per thread, up to a limit of the number
of present CPU in operation. If you had 4 cpus and 1000 threads, you
still only need 4 stacks and other associated things (PTD etc).
- It would be nice to have some sort of cooperative kernel<->user
scheduling interface so that it would be possible to have the libpthread
"engine" schedule it's pthreads onto kernel threads. Suppose one wants a
few thousand pthreads, but only realistically needs 10 or 20 of them to
block in syscalls at any given time.
I'd love to get more involved in this from the kernel side of this, but
surviving from day to day is number one priority at the moment.
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 1 07:41:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA22344
for freebsd-current-outgoing; Sun, 1 Nov 1998 07:41:10 -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 HAA22329
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 07:41:06 -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 KAA01571
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 10:40:24 -0500 (EST)
Date: Sun, 1 Nov 1998 10:40:24 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: freebsd-current@FreeBSD.ORG
Subject: boot flags
Message-ID: <Pine.BSF.4.05.9811011038220.306-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
My boot.conf looks like:
load kernel
autoboot 10
so far (I'll add modules next), but what's the syntax in that file to
add boot flags? I specifically (right now) want to add -v. If this is
defined somewhere, a pointer there would be fine.
Thanks.
----------------------------+-----------------------------------------------
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 1 07:47:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA23271
for freebsd-current-outgoing; Sun, 1 Nov 1998 07:47:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23259
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 07:47:28 -0800 (PST)
(envelope-from louie@whizzo.transsys.com)
Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1])
by whizzo.transsys.com (8.9.1/8.9.1) with ESMTP id KAA15557
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 10:47:15 -0500 (EST)
(envelope-from louie@whizzo.transsys.com)
Message-Id: <199811011547.KAA15557@whizzo.transsys.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: freebsd-current@FreeBSD.ORG
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: boot flags
References: <Pine.BSF.4.05.9811011038220.306-100000@picnic.mat.net>
In-reply-to: Your message of "Sun, 01 Nov 1998 10:40:24 EST."
<Pine.BSF.4.05.9811011038220.306-100000@picnic.mat.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 01 Nov 1998 10:47:14 -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> My boot.conf looks like:
>
> load kernel
> autoboot 10
>
> so far (I'll add modules next), but what's the syntax in that file to
> add boot flags? I specifically (right now) want to add -v. If this is
> defined somewhere, a pointer there would be fine.
And while the question is being asked.. is there a way with the new
3 stage boot loader to pass in a USERCONFIG configuration file? I used to
do this to configure some PNP peripherals. I'm guessing that this
function will probably now happen in /boot/loader, but that code doesn't
seem to be functional for this purpose yet. I'd be happy to hear otherwise.
louie
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 07:55:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA24615
for freebsd-current-outgoing; Sun, 1 Nov 1998 07:55:54 -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 HAA24608
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 07:55:50 -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 KAA01590;
Sun, 1 Nov 1998 10:54:28 -0500 (EST)
Date: Sun, 1 Nov 1998 10:54:28 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Peter Wemm <peter@netplex.com.au>
cc: Daniel Eischen <eischen@vigrid.com>, lists@tar.com, current@FreeBSD.ORG,
jb@cimlogic.com.au
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
In-Reply-To: <199811011529.XAA25055@spinner.netplex.com.au>
Message-ID: <Pine.BSF.4.05.9811011041430.306-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, 1 Nov 1998, Peter Wemm wrote:
> > I'd like to help in this effort, but I'd first like to see
> > exactly what threading model is desired. Do we want a Solaris
> > lightweight process model with the ability have both bound
> > and unbound user threads? Or do we want libpthread to keep
> > a one-one mapping of threads to kernel threads?
>
> I'm not familiar with Solaris threads but have seen the man pages for the
> SVR4.2-whatever-it-is-this-week as used in Unixware.
>
> What I had in mind was something along the lines of:
> - the kernel context switching entity would become a 'thread' rather than
> a 'proc'.
> - a "process" (struct proc) would have one or more threads, all using the
> same address space, pid, signals, etc.
> - The logistics of doing this are ugly. I don't expect that a global
> 's/sturct proc/struct thread/g' would go down well.
> - the boundaries between the present 'struct proc', pcb, upages, etc would
> get muddied a bit in the process. The context that a thread would need
> would be something like a superset of the pcb at present.
> - A thread would have just enough context for making syscalls etc.
> - context switching between threads would be bloody quick, as good or
> better than switching between rfork shared address space siblings.
> - There would be one kernel stack per thread, up to a limit of the number
> of present CPU in operation. If you had 4 cpus and 1000 threads, you
> still only need 4 stacks and other associated things (PTD etc).
> - It would be nice to have some sort of cooperative kernel<->user
> scheduling interface so that it would be possible to have the libpthread
> "engine" schedule it's pthreads onto kernel threads. Suppose one wants a
> few thousand pthreads, but only realistically needs 10 or 20 of them to
> block in syscalls at any given time.
The way it's put, it *seems* like you're saying that a thread needs more
context than a proc, but since the proc context really must be shared
among all it's threads, you wouldn't want to duplicate the proc context,
you'd just want to make the right proc context available to the right
threads, right?
The idea is that threads have less context, meaning less complicated
context switching (and lower overhead for that context switching),
right?
The idea about each thread having it's own kernel stack seems
unavoidable, but that stack could be pretty limited in size, and
actually settable size, right? I'm wondering about memory allocation
here for threads ... in a proc now, if you run out of stack, it grows
for you. I think that would be too big a hammer on the system for each
thread, wouldn't it? If a thread ran out of stack, would it just give a
signal indicating the problem, and let the thread itself (or a thread
managing thread) handle new stack problems. I mean, threads handle
stack setup themselves, when they start, unlike processes, and it ought
to be as lightweight as possible.
I'm not an expert, these are questions. I don't want threads to become
little processes with implicitly shared memories, I want them to be
lightweight, as they were originally intended. The only reason to move
to kernel threads at all is to make the signal management lighter in
weight, and get single thread blocking on syscalls, right?
I guess I'm trying to emphasize "lightweight".
I'm going to go hunting in the mail archives, Terry *must have* written
one of his email-books on this sometime.
>
> I'd love to get more involved in this from the kernel side of this, but
> surviving from day to day is number one priority at the moment.
>
> Cheers,
> -Peter
>
>
>
> 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 Sun Nov 1 08: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 IAA26497
for freebsd-current-outgoing; Sun, 1 Nov 1998 08:14:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lamb.sas.com (lamb.sas.com [192.35.83.8])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26489
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 08:14:43 -0800 (PST)
(envelope-from jwd@unx.sas.com)
Received: from mozart (mozart.unx.sas.com [192.58.184.8])
by lamb.sas.com (8.9.1/8.9.1) with SMTP id LAA23712;
Sun, 1 Nov 1998 11:14:38 -0500 (EST)
Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90)
id AA17727; Sun, 1 Nov 1998 11:14:38 -0500
Received: (from jwd@localhost)
by bb01f39.unx.sas.com (8.9.1/8.9.1) id LAA13897;
Sun, 1 Nov 1998 11:14:38 -0500 (EST)
(envelope-from jwd)
From: "John W. DeBoskey" <jwd@unx.sas.com>
Message-Id: <199811011614.LAA13897@bb01f39.unx.sas.com>
Subject: Re: scsi disk (cam?) problems (inodes & swap?)
In-Reply-To:
To: freebsd-current@FreeBSD.ORG
Date: Sun, 1 Nov 1998 11:14:37 -0500 (EST)
Cc: ken@plutotech.com
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
Hello,
Since rebooting last evenning and running:
cd /usr/src && make world && cd release && make release
my system hasn't died, but the following have shown up in messages.
fyi: my system has 256Meg of memory and I seriously doubt it ran out
of swap, and the ccd filesystems fsck'd clean twice before I started
the build.
The cvsup msgs are normal, and left in for timing info only.
Comments, critiques, & useful ideas are welcome...
Thanks!
John
FreeBSD FreeBSD.pc.sas.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0:
Sat Oct 31 13:51:35 EST 1998
Oct 31 21:18:41 FreeBSD cvsupd[225]: CVSup server started
Oct 31 21:18:41 FreeBSD cvsupd[225]: Software version: REL_15_2
Oct 31 21:18:41 FreeBSD cvsupd[225]: Protocol version: 15.4
Oct 31 21:18:41 FreeBSD cvsupd[225]: Ready to service requests
Nov 1 02:22:21 FreeBSD /kernel: (da0:ahc0:0:1:0): tagged openings now 64
Nov 1 02:22:21 FreeBSD /kernel: (da0:ahc0:0:1:0): tagged openings now 63
Nov 1 02:22:53 FreeBSD /kernel: (da1:ahc0:0:2:0): tagged openings now 64
Nov 1 02:22:53 FreeBSD /kernel: (da1:ahc0:0:2:0): tagged openings now 63
Nov 1 02:23:58 FreeBSD /kernel: (da2:ahc0:0:3:0): tagged openings now 64
Nov 1 02:23:58 FreeBSD /kernel: (da2:ahc0:0:3:0): tagged openings now 63
Nov 1 02:26:07 FreeBSD /kernel: (da3:ahc0:0:4:0): tagged openings now 64
Nov 1 02:26:07 FreeBSD /kernel: (da3:ahc0:0:4:0): tagged openings now 63
Nov 1 04:31:32 FreeBSD /kernel: free inode /snap/47709 had 208 blocks
Nov 1 04:32:51 FreeBSD /kernel: free inode /snap/119072 had 4672 blocks
.
. Lots of 'free inode' msgs deleted ::: NOTE the pager msg below
.
Nov 1 08:33:01 FreeBSD /kernel: free inode /snap/51301 had 224 blocks
Nov 1 08:35:54 FreeBSD /kernel: swap_pager: suggest more swap space: 513 MB
Nov 1 08:37:53 FreeBSD /kernel: free inode /snap/265813 had 96 blocks
Nov 1 09:23:12 FreeBSD /kernel: free inode /snap/35330 had 32 blocks
Nov 1 10:27:36 FreeBSD /kernel: free inode /pub/1745922 had 288 blocks
Nov 1 10:27:38 FreeBSD /kernel: free inode /pub/1785601 had 288 blocks
.
. Lots of 'free inode' msgs deleted
.
Nov 1 10:40:23 FreeBSD /kernel: free inode /pub/1706322 had 128 blocks
Nov 1 10:55:53 FreeBSD /kernel: free inode /pub/1777665 had 2688 blocks
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 08:23:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA27573
for freebsd-current-outgoing; Sun, 1 Nov 1998 08:23:16 -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 IAA27560
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 08:23:08 -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 AAA25247;
Mon, 2 Nov 1998 00:22:11 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811011622.AAA25247@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Chuck Robey <chuckr@mat.net>
cc: Daniel Eischen <eischen@vigrid.com>, lists@tar.com, current@FreeBSD.ORG,
jb@cimlogic.com.au
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
In-reply-to: Your message of "Sun, 01 Nov 1998 10:54:28 EST."
<Pine.BSF.4.05.9811011041430.306-100000@picnic.mat.net>
Date: Mon, 02 Nov 1998 00:22:11 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Chuck Robey wrote:
> On Sun, 1 Nov 1998, Peter Wemm wrote:
>
> > > I'd like to help in this effort, but I'd first like to see
> > > exactly what threading model is desired. Do we want a Solaris
> > > lightweight process model with the ability have both bound
> > > and unbound user threads? Or do we want libpthread to keep
> > > a one-one mapping of threads to kernel threads?
> >
> > I'm not familiar with Solaris threads but have seen the man pages for the
> > SVR4.2-whatever-it-is-this-week as used in Unixware.
> >
> > What I had in mind was something along the lines of:
> > - the kernel context switching entity would become a 'thread' rather than
> > a 'proc'.
> > - a "process" (struct proc) would have one or more threads, all using the
> > same address space, pid, signals, etc.
> > - The logistics of doing this are ugly. I don't expect that a global
> > 's/sturct proc/struct thread/g' would go down well.
> > - the boundaries between the present 'struct proc', pcb, upages, etc would
> > get muddied a bit in the process. The context that a thread would need
> > would be something like a superset of the pcb at present.
> > - A thread would have just enough context for making syscalls etc.
> > - context switching between threads would be bloody quick, as good or
> > better than switching between rfork shared address space siblings.
> > - There would be one kernel stack per thread, up to a limit of the number
> > of present CPU in operation. If you had 4 cpus and 1000 threads, you
> > still only need 4 stacks and other associated things (PTD etc).
> > - It would be nice to have some sort of cooperative kernel<->user
> > scheduling interface so that it would be possible to have the libpthread
> > "engine" schedule it's pthreads onto kernel threads. Suppose one wants a
> > few thousand pthreads, but only realistically needs 10 or 20 of them to
> > block in syscalls at any given time.
>
> The way it's put, it *seems* like you're saying that a thread needs more
> context than a proc, but since the proc context really must be shared
> among all it's threads, you wouldn't want to duplicate the proc context,
> you'd just want to make the right proc context available to the right
> threads, right?
Err, a thread needs much less context than a proc, otherwise large numbers
of them become very expensive.
A process, as it presently exists, consists of all the VM, permissions,
state, execution context, signals, etc etc. Part of the process context
is in the struct proc, part is in the pcb and upages with the kernel stack.
What would be ideal would be that a 'process' could gain multiple
execution contexts, and each of these could make syscalls and block on IO
etc.
> The idea is that threads have less context, meaning less complicated
> context switching (and lower overhead for that context switching),
> right?
Yes.
> The idea about each thread having it's own kernel stack seems
> unavoidable, but that stack could be pretty limited in size, and
> actually settable size, right? I'm wondering about memory allocation
> here for threads ... in a proc now, if you run out of stack, it grows
> for you. I think that would be too big a hammer on the system for each
> thread, wouldn't it? If a thread ran out of stack, would it just give a
> signal indicating the problem, and let the thread itself (or a thread
> managing thread) handle new stack problems. I mean, threads handle
> stack setup themselves, when they start, unlike processes, and it ought
> to be as lightweight as possible.
The tricky part comes when you try and get this to fly on a SMP system,
where the same process could really be executing in parallel on multiple
cpus at once.
The kernel stack and user stack are two different things. The processes
switch to the kernel stack for interrupts, traps and syscalls. This is in
the UPAGES at present, 8K of kvm per process. The pcb and signal state
live in the first part of the first page, so there's less than 8K of
kernel stack per process - actually there is no guard at all, the kernel
stack could conceivably grow down and clobber the snot out of the signal
handlers and the pcb, but the system would be in big trouble by then and a
process coredump would be the last thing on your mind.
You need a kernel stack per thread in the lightweight model, up to a limit
of the number of cpus running, because it's needed for each possibly
active thread to make a syscall.
> I'm not an expert, these are questions. I don't want threads to become
> little processes with implicitly shared memories, I want them to be
> lightweight, as they were originally intended. The only reason to move
> to kernel threads at all is to make the signal management lighter in
> weight, and get single thread blocking on syscalls, right?
Two reasons.. blocking on syscalls, and SMP support. A select() buzz
loop scheduler like in libc_r gets no gain from a SMP system, and that's
the main gain to be had.
There are other problems that need to be resolved for SMP address space
sharing. Activating the same PTD from a single address space blows away
the per-cpu private pages and this really screws things up since both cpus
aquire the same cpuid and explode. Teaching the pmap code about multiple
PTD's per process (per shared rfork() thread, up to a max of numcpus again)
is an interesting problem - I wonder if it might be easier to simply have
a different PTD for the kernel for each CPU and switch from the user PTD
to the kernel one at trap/syscall/interrupt time. This means major
changes to the protection interface, copyin/out etc are presently done by
having the kernel read the user pages and faulting if needed. Under a
per-cpu kernel space PTD, the kernel would have to do much more work to
access the current user process address space.
> I guess I'm trying to emphasize "lightweight".
I know, so am I.
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 Sun Nov 1 08:40:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA00558
for freebsd-current-outgoing; Sun, 1 Nov 1998 08:40:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00550
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 08:40:24 -0800 (PST)
(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id RAA08027
for freebsd-current@FreeBSD.ORG; Sun, 1 Nov 1998 17:40:18 +0100 (CET)
(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (VMailer, from userid 101)
id 14DAB145A; Sun, 1 Nov 1998 16:59:53 +0100 (CET)
Date: Sun, 1 Nov 1998 16:59:52 +0100
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: freebsd-current@FreeBSD.ORG
Subject: Re: boot flags
Message-ID: <19981101165952.A8580@keltia.freenix.fr>
Mail-Followup-To: freebsd-current@FreeBSD.ORG
References: <Pine.BSF.4.05.9811011038220.306-100000@picnic.mat.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.4i
In-Reply-To: <Pine.BSF.4.05.9811011038220.306-100000@picnic.mat.net>; from Chuck Robey on Sun, Nov 01, 1998 at 10:40:24AM -0500
X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4772 AMD-K6 MMX @ 200 MHz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
According to Chuck Robey:
> load kernel
> autoboot 10
>
> so far (I'll add modules next), but what's the syntax in that file to
> add boot flags? I specifically (right now) want to add -v. If this is
> defined somewhere, a pointer there would be fine.
Add a line like the following:
set verbose
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-BETA #4: Thu Oct 15 01:36:57 CEST 1998
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 08:53:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA01941
for freebsd-current-outgoing; Sun, 1 Nov 1998 08:53:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01934
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 08:53:29 -0800 (PST)
(envelope-from jdp@austin.polstra.com)
Received: from austin.polstra.com (jdp@localhost)
by austin.polstra.com (8.9.1/8.9.1) with ESMTP id IAA29300;
Sun, 1 Nov 1998 08:53:22 -0800 (PST)
(envelope-from jdp)
Message-Id: <199811011653.IAA29300@austin.polstra.com>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: current@FreeBSD.ORG
Subject: Re: cvsup .4.2
In-reply-to: Your message of "Sun, 01 Nov 1998 14:28:09 +0100."
<XFMail.981101142809.asmodai@wxs.nl>
Date: Sun, 01 Nov 1998 08:53:22 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Please let me know what version of FreeBSD you're running. Also
>
> 3.0-CURRENT, cvsupped every day.
>
> > please send me the output of:
> >
> > ident /usr/include/sys/sem.h
>
> [diabolique] asmodai $ ident /usr/include/sys/sem.h
> /usr/include/sys/sem.h:
> $Id: sem.h,v 1.15 1998/07/15 02:32:32 bde Exp $
> $NetBSD: sem.h,v 1.5 1994/06/29 06:45:15 cgd Exp $
>
>
> > and
> >
> > grep define /usr/include/osreldate.h
>
> [diabolique] asmodai $ grep define /usr/include/osreldate.h
> #define __FreeBSD_version 300006
Thanks, that clears it up. I think your modula-3-lib port must be
out of date. I fixed this problem in early June. Check your file
"modula-3-lib/patches/patch-ab" with /sbin/md5 and you should get
this:
vashon$ /sbin/md5 patch-ab
MD5 (patch-ab) = d15b35461b0e8df99ae9d2707e2660dd
But I don't think that's what you'll see. :-)
Grab the current modula-3-lib port from the web site. While you're
at it, get the latest modula-3 and cvsup ports too. Then I think it
will all work fine.
> Might also be relevant to my Attic/cvsup make world problems...
Nope, I don't think there's any connection between the two problems.
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 Sun Nov 1 08:56:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA02375
for freebsd-current-outgoing; Sun, 1 Nov 1998 08:56:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lamb.sas.com (lamb.sas.com [192.35.83.8])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02368
for <freebsd-current@freebsd.org>; Sun, 1 Nov 1998 08:56:46 -0800 (PST)
(envelope-from jwd@unx.sas.com)
Received: from mozart (mozart.unx.sas.com [192.58.184.8])
by lamb.sas.com (8.9.1/8.9.1) with SMTP id LAA29976;
Sun, 1 Nov 1998 11:56:36 -0500 (EST)
Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90)
id AA19182; Sun, 1 Nov 1998 11:56:35 -0500
Received: (from jwd@localhost)
by bb01f39.unx.sas.com (8.9.1/8.9.1) id LAA14169;
Sun, 1 Nov 1998 11:56:31 -0500 (EST)
(envelope-from jwd)
From: "John W. DeBoskey" <jwd@unx.sas.com>
Message-Id: <199811011656.LAA14169@bb01f39.unx.sas.com>
Subject: Re: Changing sh for compatibility sake
In-Reply-To: From Brian Feldman at "Oct 27, 98 07:31:15 am"
To: green@zone.syracuse.net (Brian Feldman)
Date: Sun, 1 Nov 1998 11:56:31 -0500 (EST)
Cc: freebsd-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
Hi,
I sent mail to this list a few months ago... pdksh doesn't run
the tail-end of a pipe in the current shell environment, thus the
following doesn't work as expected:
export FOUND=0
ls | wc -l | while read fcnt; do
export FOUND=$fcnt
done
echo $FOUND
So, the comment below might need a slight modification to say
which scripts don't break... :-)
Thanks!
John
> Let me repeat this once more: not a SINGLE script breaks with pdksh!
>
> Brian Feldman
>
> On Mon, 26 Oct 1998, Kurt D. Zeilenga wrote:
>
> > Chuck wrote:
> > >I'm sorry, that's not true. Ask anyone who writes shell scripts that
> > >install software (or perform any necessarily portable function) across
> > >multiple platforms. sh is the shell to use ONLY BECAUSE it's the lowest
> > >common denominator. Why else would they use the dumbest shell?
> >
> > I've written numerous system/install sh scripts. But it's not to
> > one specific implementation, its many. It seems like every OS
> > has it's own variant of sh. I do not know of any version of sh
> > that can reliable used as a golden target sh. Each and very
> > implementation of sh has its quirks that have to be dealt with.
> > FreeBSD sh definitely has its, as do the others.
> >
> > Any change will likely cause problems in some existing scripts.
> > Also, any change will cause developers to deal with additional
> > portability issues. This is life. Most multiple platform sh
> > developers have already adapted to specific quicks of popular
> > sh implementations. Changing from one to another should not
> > be that big of a deal. I suspect a few FreeBSD-only sh scripts
> > will choke.
> >
> > Don't change sh for compatibility sake, our scripts are already
> > compatible! Do change for functionality sake, we'll adapt as
> > necessary.
> >
> > Kurt
> >
> > 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 1 09:11:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA03996
for freebsd-current-outgoing; Sun, 1 Nov 1998 09:11:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lamb.sas.com (lamb.sas.com [192.35.83.8])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03988
for <freebsd-current@freebsd.org>; Sun, 1 Nov 1998 09:11:13 -0800 (PST)
(envelope-from jwd@unx.sas.com)
Received: from mozart (mozart.unx.sas.com [192.58.184.8])
by lamb.sas.com (8.9.1/8.9.1) with SMTP id MAA01486;
Sun, 1 Nov 1998 12:10:57 -0500 (EST)
Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90)
id AA19576; Sun, 1 Nov 1998 12:10:57 -0500
Received: (from jwd@localhost)
by bb01f39.unx.sas.com (8.9.1/8.9.1) id MAA14627;
Sun, 1 Nov 1998 12:10:54 -0500 (EST)
(envelope-from jwd)
From: "John W. DeBoskey" <jwd@unx.sas.com>
Message-Id: <199811011710.MAA14627@bb01f39.unx.sas.com>
Subject: Re: scsi disk (cam?) problems (inodes & swap?)
In-Reply-To: <199811011628.AAA25291@spinner.netplex.com.au> from Peter Wemm at "Nov 2, 98 00:28:55 am"
To: peter@netplex.com.au (Peter Wemm)
Date: Sun, 1 Nov 1998 12:10:54 -0500 (EST)
Cc: freebsd-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
Hi,
I do not use softupdates, and my machine is not smp.
The build completed to the end of the 'make release', requiring
9 hours. However, I have not verified the contents of the distribution
area.
Yes, this build process works/worked correctly... I've been running
it for about a year... failures are usually related to bad code... :-)
# ls /pub/FreeBSD
3.0-19981027-SNAP
3.0-19981029-SNAP
3.0-19981030-SNAP
3.0-19981101-SNAP
I'm more than happy to put some tracing code in, I'm just not
real familiar with where it really needs to go to track these
problems down...
Thanks!
John
> "John W. DeBoskey" wrote:
> > Hello,
> >
> > Since rebooting last evenning and running:
> >
> > cd /usr/src && make world && cd release && make release
> >
> > my system hasn't died, but the following have shown up in messages.
> > fyi: my system has 256Meg of memory and I seriously doubt it ran out
> > of swap, and the ccd filesystems fsck'd clean twice before I started
> > the build.
> >
> > The cvsup msgs are normal, and left in for timing info only.
> >
> > Comments, critiques, & useful ideas are welcome...
> > Thanks!
> > John
>
> Did you have softupdates on? SMP?
>
> If you do not, then my immediate suspicion would be the changes I made
> yesterday, perhaps loosing some metadata updates.
>
> On the other hand, the swap pager message is worrying, we've seen this
> turning up before in the middle of other "strange" events. Did this
> release build process work before the changes yesterday?
>
> 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 1 10: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 KAA10384
for freebsd-current-outgoing; Sun, 1 Nov 1998 10:01:16 -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 KAA10370
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 10:01:13 -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 TAA00655;
Sun, 1 Nov 1998 19:06:43 +0100 (CET)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Sun, 1 Nov 1998 19:06:42 +0100 (CET)
From: Andrzej Bialecki <abial@nask.pl>
X-Sender: abial@korin.warman.org.pl
To: Mike Smith <mike@smith.net.au>
cc: current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-Reply-To: <199811010315.TAA00686@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.02A.9811011858200.18422-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 Sat, 31 Oct 1998, Mike Smith wrote:
> > abial# size libficl.a
> > text data bss dec hex filename
> > 2403 0 0 2403 963 dict.o (ex libficl.a)
> > 989 20 0 1009 3f1 ficl.o (ex libficl.a)
> > 892 0 0 892 37c math64.o (ex libficl.a)
> > 63 3130 0 3193 c79 softcore.o (ex libficl.a)
> > 674 0 0 674 2a2 stack.o (ex libficl.a)
> > 253 0 0 253 fd sysdep.o (ex libficl.a)
> > 2154 44 0 2198 896 vm.o (ex libficl.a)
> > 18222 92 0 18314 478a words.o (ex libficl.a)
> >
> > (this can be still reduced if we limit ourselves to CORE words - I think
> > 1/3 of words.o would go away).
>
> It builds a little bigger here; it weighs in at about 40k. If you
> strip the OO extensions out it comes down to about 22k. I don't know
I stripped LOCALS, multithreading, stack checking, but added KEY... Well,
this is still around 20k.
> whether there's much we can strip from the core wordset; I'll leave
> that for the FORTH guruen to argue over. At 22k (plus whatever it
As I said above, we probably can strip CORE-EXT and SEARCH - I wouldn't
touch the CORE itself, however.
> costs to bind it in) I think we have a goer. Doug's resolved the Alpha
> space issues too, so it should be comfy.
Great! I think we won't regret it...
> > U __assert
>
> We need an assert.
You mean: "anyway"? Because it's only as a diagnostics and can be defined
as no-op.
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 Sun Nov 1 10:40:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA15060
for freebsd-current-outgoing; Sun, 1 Nov 1998 10:40:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15054
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 10:40:41 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from diabolique.ninth-circle.org ([195.121.59.72])
by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA5CC; Sun, 1 Nov 1998 19:40:34 +0100
Message-ID: <XFMail.981101194426.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.9811010654560.3668-100000@gina.swimsuit.internet.dk>
Date: Sun, 01 Nov 1998 19:44:26 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Leif Neland <leifn@swimsuit.internet.dk>
Subject: Re: kernel compile problem
Cc: Dmitry Valdov <dv@dv.ru>, freebsd-current@FreeBSD.ORG,
Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 01-Nov-98 Leif Neland wrote:
>> > You got a cvsup in between commits.. Try again and you should be OK.
>>
>> just spotted this one too ;)
>>
>> How can ye make sure ye ain't between commits? cvsup it about 15-30 minutes
>> later and try again to make?
>>
> How about if the committer started by committing
> /usr/src/DONT_MAKE_WORLD_NOW
> then committed various stuff, then removed
> /usr/src/DONT_MAKE_WORLD_NOW
> This file could contain an explanation why the world shouldn't be made.
Nah, that wouldn't work that well...
> The makefile should then check for the existance of this file.
>
> This could be implemented right now. It won't require updating cvsup and
> cvsupd.
>
> But this will give problems when several people are updating different
> parts of the tree...
Exactly, then ye are going against what makes the commit system of cvsup work.
> To make it more clean, it should be done in cvsupd and perhaps cvsup.
>
> It could be implemented by modifying using cvsupd's ability to check out
> the version of the tree as it were on a certain time.
>
> The committer sends it a command/file/signal, and then new additions
> made after that time is not seen by someone who requests the latest
> versions.
Exactly, does the term commit-relay express the idea completely?
> After everything is committed, the committer removes the lock.
Why the commiter? Make it so that the cvsupd places a lock temporarily whenever
a commit finds place. Then after the person is through with his or her commits
it makes all those updated files available to the public for cvsup. Make it so
that the daemon does the work and not the commiter. This saves hassle.
> Perhaps this should lock be on committer-resolution, so one committer
> forgetting a lock/being hit by an 18-wheeler won't lock the entire tree.
Well, what does cvsup do? It monitors versions. So the lock must be based on
versioning too...
> If somebody _really_ wants the latest versions, one could specify an
> date=-1 or something instead of date=.
>
> What happens if somebody starts a cvsup, and files gets committed before
> the cvsup is finished? Are those updates seen?
If the lock is removed within the current session it might. Depends on what the
cvsup already fetched...
> The tag date=. shouldn't mean "as late as possible", but "at the start of
> this cvsup-run", so to get a consistent snapshot of the tree.
That will solve the above problem. But the daemon must tag all the files or
queue them for every cvsup to know which files to send to which connection.
> cvsupd should keep track of each clients starttime, and not supply later
> checkouts.
Indeed. This may require significant improvements to cvsupd and cvsup. But they
might make the whole process more stable at any given point in time.
Comments?
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 1 10:52:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA16175
for freebsd-current-outgoing; Sun, 1 Nov 1998 10:52:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16160
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 10:52:28 -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 TAA21109;
Sun, 1 Nov 1998 19:52:09 +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 TAA20650;
Sun, 1 Nov 1998 19:52:53 +0100 (CET)
Received: (from ticso@localhost)
by cicely5.cicely.de (8.9.0/8.9.0) id TAA15719;
Sun, 1 Nov 1998 19:52:47 +0100 (CET)
Message-ID: <19981101195246.10586@cicely.de>
Date: Sun, 1 Nov 1998 19:52:46 +0100
From: Bernd Walter <ticso@cicely.de>
To: "Kenneth D. Merry" <ken@plutotech.com>,
"John W. DeBoskey" <jwd@unx.sas.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: scsi disk (cam?) problems
References: <199811010132.UAA04810@bb01f39.unx.sas.com> <199811010208.TAA27408@panzer.plutotech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89i
In-Reply-To: <199811010208.TAA27408@panzer.plutotech.com>; from Kenneth D. Merry on Sat, Oct 31, 1998 at 07:08:50PM -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, Oct 31, 1998 at 07:08:50PM -0700, Kenneth D. Merry wrote:
> John W. DeBoskey wrote...
> > Hi,
> >
> > My -CURRENT system has been experiencing problems since I converted
> > it to cam awhile back. The following show up on my console, and then
> > my disks are useless until I completely shutdown, powerdown my drive
> > array, power it back on, and reboot. I have 4 identical drives configured
> > as a ccd. They have been serving me well more about a year...
> >
> > If anyone has any ideas on how I can track down the problem, please
> > let me know!
> >
> > Thanks,
> > John
> >
> > /dev/ccd0a 2155550 1268428 714678 64% /snap
> > /dev/ccd0b 2155550 1020154 962952 51% /usr/obj
> > /dev/ccd0d 17244630 12876242 2988818 81% /pub
> >
> > Snipped from messages: (This kernel was built on the 28th), I'm now on
> > a kernel built Oct 31.
> [ ... ]
>
> > Oct 30 10:52:35 FreeBSD /kernel: (da2:ahc0:0:3:0): Invalidating pack
> > Oct 30 10:52:35 FreeBSD /kernel: (da2:ahc0:0:3:0): Invalidating pack
>
> Well, what's happening here is that one of your disks is returning an
> error, and keeps returning that error. Reads and writes in the da driver
> have a retry count of 4. So by the time we print out the message above,
> the command has already been retried four times. We may also have taken a
> number of error recovery actions to try to bring the device back.
>
Very interesting.
I've saw the same message yesterday:
Oct 31 20:10:18 cicely5 /kernel: (da23:ahc4:0:1:0): Invalidating pack
I was writing to a mounted fs on da23 <SHARP JY800 MODC 2.45>
during that I received this message.
Can't unmount:
root@cicely5# umount /mnt
umount: /mnt: Device not configured
But I can send commands via camcontrol to the drive.
Rescan won't help.
Havn't rebooted yet.
Is there any way to get this drive working again without rebooting?
> How often does this happen? Could you try booting with -v, and see if you
> can reproduce the problem? I think that that (booting with -v) should
> cause the error to be printed out. If I know the error, I may be able to
> help you work around it, or at least tell you that one of your disks is on
> the blink.
For me it's the first and only one till now.
--
Mfg B.Walter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 11:03:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA17652
for freebsd-current-outgoing; Sun, 1 Nov 1998 11:03:02 -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 LAA17647
for <current@FreeBSD.org>; Sun, 1 Nov 1998 11:03:01 -0800 (PST)
(envelope-from gibbs@narnia.plutotech.com)
Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id LAA08811; Sun, 1 Nov 1998 11:56:01 -0700 (MST)
Date: Sun, 1 Nov 1998 11:56:01 -0700 (MST)
From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Message-Id: <199811011856.LAA08811@narnia.plutotech.com>
To: Heiko Schaefer <hschaefer@fto.de>
cc: current@FreeBSD.ORG
Subject: Re: Problem with SCSI Harddisk
X-Newsgroups: pluto.freebsd.current
In-Reply-To: <Pine.BSF.4.05.9810241527150.253-100000@daneel.spacequest.hs>
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.9810241527150.253-100000@daneel.spacequest.hs> you wrote:
> Hello all,
>
> after checking the archives of this list (as well as freebsd-scsi), i
> finally decided to post a problem that i have here.
> i hope this is the right place and way to search for advice (and/or help).
You should have posted to FreeBSD-scsi. The SCSI developers pay much
more attention to that list (lower volume you know) than this one.
> i have used this harddisk for quite some time without any problems that i
> could notice under 2.2-STABLE. the problem seems to have started exactly
> when updating my system to 3.0-CURRENT.
> (by the way is there a 3.0-STABLE or will there be sometime soon ?!)
...
> da3: <SEAGATE SX910800N 8511> Fixed Direct Access SCSI2 device
> da3: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
> da3: 8669MB (17755614 512 byte sectors: 255H 63S/T 1105C)
Seagate's web page doesn't list this drive model number... do you know the
'family name' for the drive?
This drive shows a similar problem to the Seagate Elite 9 with
certain levels of firmware. Essentially it wedges when you hit it
wil a high tag load. I would suggest contacting Seagate technical
support about this drive to see if later firmware is available.
In the mean time, you should try adding a quirk entry to the table
in sys/cam/cam_xpt.c that matches your drive. It may be that simply
reducing the number of transactions to something less than 64 will
prevent the drive from going nuts. Once you have a quirk entry
that works for you, I'll commit it to the tree.
BTW, the reason the 2940AU worked for you and the 2940UW did not is
that the 2940AU cannot dish out transactions as quickly as the 2940UW.
If you want high performance, I would suggest switching back to the
2940UW. See the chip comparison chart in the ahc(4) man page for
more details.
--
Justin
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 11:03:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA17716
for freebsd-current-outgoing; Sun, 1 Nov 1998 11:03:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17703
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 11:03:14 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from diabolique.ninth-circle.org ([195.121.59.72])
by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA1C03; Sun, 1 Nov 1998 19:03:07 +0100
Message-ID: <XFMail.981101200659.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: <19981101225954.A29897@clear.co.nz>
Date: Sun, 01 Nov 1998 20:06:59 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Joe Abley <jabley@clear.co.nz>, John Polstra <jdp@polstra.com>
Subject: CVSup(d) (was: Re: kernel compile problem)
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 01-Nov-98 Joe Abley wrote:
> On Sun, Nov 01, 1998 at 07:44:52AM +0100, Leif Neland wrote:
>>
>> Is the problem that committing isn't 'atomical'?
>>
>> How about if the committer started by committing
>> /usr/src/DONT_MAKE_WORLD_NOW
>> then committed various stuff, then removed
>> /usr/src/DONT_MAKE_WORLD_NOW
>> This file could contain an explanation why the world shouldn't be made.
>>
>> The makefile should then check for the existance of this file.
>>
>> This could be implemented right now. It won't require updating cvsup and
>> cvsupd.
>>
>> But this will give problems when several people are updating different
>> parts of the tree...
>
> So we need a semaphore; however, a single lock file with a counter in it
> doesn't sound very practical for cvsup.
>
> How about a directory called "lock" in whatever part of the source tree
> is appropriate, into which committers deposit a file named with their e-mail
> address, containing a description of why the source tree is locked?
This will generate extra overhead and deletion of files.
> bsd.subdir.mk could check for files within this subdirectory and fail
> quoting the contents of any files that are present.
>
> The same branch of the tree could be locked by more than one committer
> (since their respective lock files would have different names).
>
> Having lock directories at appropriate depths in the source tree would
> be better than one "don't make world" lock file -- that way if I want
> to rebuild and reinstall /usr/src/usr.bin/ I won't be affected by a
> transient commit lock in /usr/src/usr.sbin/ (for example).
Ye need to have it configurable at the lowest leaves possible instead of
branches...
> If no "lock" subdirectory is present, this should be interpreted as
> "there are no locks for this branch".
OK, what can we discern?
1) Need for multiple locks
2) The ability to cvsup a source tree that is commit free
3) The ability to commit changes regardless of the state of the tree
4) The ability for cvsupd to monitor versions every more carefully
Did I miss somthing?
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 1 11:09:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA18551
for freebsd-current-outgoing; Sun, 1 Nov 1998 11:09:48 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18486
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 11:09:39 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from diabolique.ninth-circle.org ([195.121.59.72])
by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA20F5; Sun, 1 Nov 1998 19:09:30 +0100
Message-ID: <XFMail.981101201322.asmodai@wxs.nl>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <XFMail.981101142806.asmodai@wxs.nl>
Date: Sun, 01 Nov 1998 20:13:22 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: current@FreeBSD.ORG
Subject: Re: Another compile error
Cc: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
OK, that did the trick, I haven't spotted Attic in the make run no more
Now I am stuck with this:
install -c -o root -g wheel -m 644 lkm/syscall/test/testsyscall.c
/usr/share/examples/lkm/syscall/test/testsyscall.c
install -c -o root -g wheel -m 644 lkm/syscall/TRANS.TBL
/usr/share/examples/lkm/syscall/TRANS.TBL
install -c -o root -g wheel -m 644 lkm/syscall/Makefile
/usr/share/examples/lkm/syscall/Makefile
install -c -o root -g wheel -m 644 lkm/syscall/README
/usr/share/examples/lkm/syscall/README
install -c -o root -g wheel -m 644 lkm/vfs/module/TRANS.TBL
/usr/share/examples/lkm/vfs/module/TRANS.TBL
install: /usr/share/examples/lkm/vfs/module/TRANS.TBL: No such file or directory
*** Error code 71
Stop.
*** Error code 1
If I look in src/share/examples/lkm/vfs/module/ of my cvs slice I see TRANS.TBL
What could cause this error then?
Thanks in advance,
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 1 11: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 LAA20679
for freebsd-current-outgoing; Sun, 1 Nov 1998 11:23:08 -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 LAA20672
for <current@FreeBSD.org>; Sun, 1 Nov 1998 11:23:07 -0800 (PST)
(envelope-from gibbs@narnia.plutotech.com)
Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id MAA08880; Sun, 1 Nov 1998 12:16:00 -0700 (MST)
Date: Sun, 1 Nov 1998 12:16:00 -0700 (MST)
From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Message-Id: <199811011916.MAA08880@narnia.plutotech.com>
To: Peter Wemm <peter@netplex.com.au>
cc: current@FreeBSD.ORG
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
X-Newsgroups: pluto.freebsd.current
In-Reply-To: <199811011622.AAA25247@spinner.netplex.com.au>
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 <199811011622.AAA25247@spinner.netplex.com.au> you wrote:
>
> You need a kernel stack per thread in the lightweight model, up to a limit
> of the number of cpus running, because it's needed for each possibly
> active thread to make a syscall.
I don't see how you can achieve such a limited number of stacks
without a thread continuation model. If a thread calls tsleep
while in kernel context, where does it's kernel stack go? If you
always restart the thread from a thread continuation point, you
can throw its stack away. This is certainly very desirable, but
the impact on the kernel would be extremely large.
--
Justin
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 11:25:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA20909
for freebsd-current-outgoing; Sun, 1 Nov 1998 11:25:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pimout1-int.prodigy.net (pimout1-ext.prodigy.net [207.115.58.53])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20903
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 11:25:28 -0800 (PST)
(envelope-from ttran@usa.net)
Received: from bigdog (HRFRB102-37.splitrock.net [209.156.68.37])
by pimout1-int.prodigy.net (8.8.5/8.8.5) with SMTP id OAA10310
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 14:23:16 -0500
Reply-To: <ttran@usa.net>
From: "Tho Tran" <ttran@usa.net>
To: <freebsd-current@FreeBSD.ORG>
Date: Sun, 1 Nov 1998 14:31:19 -0500
Message-ID: <000001be05ce$33440450$010201c0@bigdog.shaolin.org>
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
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 11:26:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA21127
for freebsd-current-outgoing; Sun, 1 Nov 1998 11:26: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 LAA21121
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 11:26:50 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id LAA18368;
Sun, 1 Nov 1998 11:25:29 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpds18365; Sun Nov 1 19:25:28 1998
Date: Sun, 1 Nov 1998 11:25:06 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: "Richard Seaman, Jr." <lists@tar.com>
cc: John Birrell <jb@cimlogic.com.au>,
"current@freebsd.org" <current@FreeBSD.ORG>
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
In-Reply-To: <199810312126.PAA23692@ns.tar.com>
Message-ID: <Pine.BSF.3.95.981101112220.5087D-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
I disagree slightly with the thought that syscalls can be unwrapped
with kernel threads. The thread implementation I've seen discussed before
is that where new threads are spawned by the kernel, until a limit is
reached, after which user-level threading techniques are used to multiplex
userlevel threads over a number of kernel level threads.
julian
On Sat, 31 Oct 1998, Richard Seaman, Jr. wrote:
> On Sun, 1 Nov 1998 07:43:04 +1100 (EST), John Birrell wrote:
>
> >Richard Seaman, Jr. wrote:
>
> >Kernel threads should use libpthread and libc, not libc_r.
>
> Agreed, sort of. I don't use libc_r. If you're going to implement
> deferred cancellation points, I think you still need to wrap some
> syscalls, so you still need to generate a separate libc somewhere.
> The "kernel" syscalls drop into libpthread, in a manner analagous
> to what happens in libc_r, but the wrappers are different, and the
> syscalls that are wrapped are different.
>
> >You can't mix
> >kernel thread syscalls with user-thread syscalls because the styles are
> >incompatible (blocking vs non-blocking).
>
> Agreed. A pure kernel thread implementation seems much simpler because
> you just get rid of all the syscall wrapping that's needed to implement
> user thread blocking i/o. Or, am I missing something?
>
> >You can't mix kernel thread
> >scheduling with user-thread scheduling.
>
> Agreed. In kernel threads the kernel scheduler does all the work.
> You can get rid of all the 19 pages of user thread scheduling code.
>
> >It doesn't sound like you have
> >made any attempt to update the user-space knowledge of the running thread.
> >As a result you will mix all errno codes and all user-space locking. This
> >is a fundamental issue that needs to be designed, not hacked.
>
> Well, the user-space knowledge of the running thread comes from pthread_self,
> which in the case I've implemented this comes from the code John Dyson
> provided to the list a while back. errno codes are returned on the
> thread stack, if I understand his code.
>
>
>
>
> 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 1 11:29:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA21328
for freebsd-current-outgoing; Sun, 1 Nov 1998 11:29:24 -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 LAA21322
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 11:29:22 -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 OAA05742;
Sun, 1 Nov 1998 14:29:09 -0500 (EST)
(envelope-from wollman)
Date: Sun, 1 Nov 1998 14:29:09 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199811011929.OAA05742@khavrinen.lcs.mit.edu>
To: Chuck Robey <chuckr@mat.net>
Cc: John Hay <jhay@mikom.csir.co.za>,
Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, current@FreeBSD.ORG
Subject: Re: IPv6 in -current
In-Reply-To: <Pine.BSF.4.05.9811010922160.306-100000@picnic.mat.net>
References: <199811010922.LAA05107@zibbi.mikom.csir.co.za>
<Pine.BSF.4.05.9811010922160.306-100000@picnic.mat.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Sun, 1 Nov 1998 09:37:41 -0500 (EST), Chuck Robey <chuckr@mat.net> said:
> This would serve to give the ideas their best airing, allow the
> developers to present their cases in the lowest possible pressure
> consistent with public disclosure, and probably give the loser at least
> the feeling that they'd certainly been listened to, so their would be
> less likelihood of injured feelings. And, FreeBSD would most likely to
> get the best IPv6 implementation from it.
I frankly don't care that much which IPv6 implementation is chosen.
My concerns are the following:
2) that we don't screw any of the existing developers
1) that we make whatever necessary fundamental advances we can in the
network stack before taking on additional deadweight
-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 1 11:31:08 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA21533
for freebsd-current-outgoing; Sun, 1 Nov 1998 11:31:08 -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 LAA21527
for <current@FreeBSD.org>; Sun, 1 Nov 1998 11:31:07 -0800 (PST)
(envelope-from gibbs@narnia.plutotech.com)
Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id MAA08917; Sun, 1 Nov 1998 12:24:09 -0700 (MST)
Date: Sun, 1 Nov 1998 12:24:09 -0700 (MST)
From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Message-Id: <199811011924.MAA08917@narnia.plutotech.com>
To: Bernd Walter <ticso@cicely.de>
cc: current@FreeBSD.ORG
Subject: Re: scsi disk (cam?) problems
X-Newsgroups: pluto.freebsd.current
In-Reply-To: <199811010132.UAA04810@bb01f39.unx.sas.com> <199811010208.TAA27408@panzer.plutotech.com> <19981101195246.10586@cicely.de>
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 <19981101195246.10586@cicely.de> you wrote:
> Very interesting.
> I've saw the same message yesterday:
> Oct 31 20:10:18 cicely5 /kernel: (da23:ahc4:0:1:0): Invalidating pack
What kinds of power supplies are all of you using? The reason the
pack is being invalidated is that the drive in question is not
responding within a selection timeout period (250ms). This is
usually because of a device no being there, but I suspect in this
case the cause is a parallel I/O load that pushes your drives
to their maximum power rating, saturating your power supply leaving
one or more devices starving for power. Any I/O attempted while
the drive is going through a power-on reset is likely to fail with
a selection timeout.
I will change the error handler for the selection timeout case to
return EIO instead of ENXIO, but this is just a temporary work around
until we can provide a better pack invalidation scheme in the system.
--
Justin
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 11:57:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA26194
for freebsd-current-outgoing; Sun, 1 Nov 1998 11:57:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles355.castles.com [208.214.167.55])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26186
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 11:57: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 LAA05322;
Sun, 1 Nov 1998 11:57:16 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811011957.LAA05322@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Chuck Robey <chuckr@mat.net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: boot flags
In-reply-to: Your message of "Sun, 01 Nov 1998 10:40:24 EST."
<Pine.BSF.4.05.9811011038220.306-100000@picnic.mat.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 01 Nov 1998 11:57:15 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> My boot.conf looks like:
>
> load kernel
> autoboot 10
>
> so far (I'll add modules next), but what's the syntax in that file to
> add boot flags? I specifically (right now) want to add -v. If this is
> defined somewhere, a pointer there would be fine.
You can supply arguments when you load the kernel:
load kernel -v
You can also set many of them using environment variables:
set boot_verbose
and if you're using the 'boot' command, you can pass them there too:
boot -v
--
\\ 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 1 12: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 MAA26651
for freebsd-current-outgoing; Sun, 1 Nov 1998 12:00:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles355.castles.com [208.214.167.55])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26641
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 12:00:18 -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 LAA05344;
Sun, 1 Nov 1998 11:59:50 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811011959.LAA05344@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Louis A. Mamakos" <louie@TransSys.COM>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: boot flags
In-reply-to: Your message of "Sun, 01 Nov 1998 10:47:14 EST."
<199811011547.KAA15557@whizzo.transsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 01 Nov 1998 11:59:50 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > My boot.conf looks like:
> >
> > load kernel
> > autoboot 10
> >
> > so far (I'll add modules next), but what's the syntax in that file to
> > add boot flags? I specifically (right now) want to add -v. If this is
> > defined somewhere, a pointer there would be fine.
>
> And while the question is being asked.. is there a way with the new
> 3 stage boot loader to pass in a USERCONFIG configuration file? I used to
> do this to configure some PNP peripherals. I'm guessing that this
> function will probably now happen in /boot/loader, but that code doesn't
> seem to be functional for this purpose yet. I'd be happy to hear otherwise.
There isn't at this point in time. Unless you're constantly cycling
kernels, the PnP information is saved into the booted kernel by dset,
so you only need to set it once.
Now that the kernel can receive arbitrary information passed in from
the loader, you'll do something like this:
load -t userconfig_script /boot/userconfi.script
and userconfig will just run down the list of userconfig_script
objects, executing commands out of them.
I'll aim to get this done today.
--
\\ 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 1 12:11:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA28547
for freebsd-current-outgoing; Sun, 1 Nov 1998 12:11:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pinhead.parag.codegen.com (ppp-asfm08--202.sirius.net [205.134.241.202])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28538
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 12:11:02 -0800 (PST)
(envelope-from parag@pinhead.parag.codegen.com)
Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1])
by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id MAA17513;
Sun, 1 Nov 1998 12:06:35 -0800 (PST)
(envelope-from parag@pinhead.parag.codegen.com)
Message-Id: <199811012006.MAA17513@pinhead.parag.codegen.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: Mikael Karpberg <karpen@ocean.campus.luth.se>,
mike@smith.net.au (Mike Smith), current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Sun, 01 Nov 1998 16:01:00 +0100."
<18026.909932460@critter.freebsd.dk>
X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X
]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm
X-URL: http://www.codegen.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 01 Nov 1998 12:06:35 -0800
From: Parag Patel <parag@cgt.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <18026.909932460@critter.freebsd.dk>, Poul-Henning Kamp
writes:
>The "Open" boot prom on Suns and the various spinoffs from that use
>forth for that reason. It's compact, it can be made machine
independent
>and there is a standard (several actually) so you don't have to invent
>the host plate and the deep water all over again.
Well, that was the original intention, but if you look at the OpenFirmware standard (IEEE-1275), the added stuff greatly expands the size. Our C implementation (SmartFirmware) is actually smaller than their native Forth implementation, both in code size and run-time data size (which was a big surprise to us) but is still bigger than a traditional Forth implementation.
IEEE-1275 adds quite a lot on top of the ANS Forth spec.
I think the main reason they went to Forth is to support plug-in boot ROMs using a byte-coded Forth called Fcode. It's the best choice if you want to have a machine-independent boot ROM on a plug-in card. They could have gone with a byte-encoded Lisp or BASIC or anything else, but Sun has a tendancy to base systems around Forth for some reason (Openview, Java, etc :-).
-- Parag Patel
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 12:29:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA01287
for freebsd-current-outgoing; Sun, 1 Nov 1998 12:29:00 -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 MAA01281
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 12:28:57 -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 VAA21674;
Sun, 1 Nov 1998 21:28:48 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id VAA28186;
Sun, 1 Nov 1998 21:28:47 +0100 (MET)
Message-ID: <19981101212847.14447@follo.net>
Date: Sun, 1 Nov 1998 21:28:47 +0100
From: Eivind Eklund <eivind@yes.no>
To: Chuck Robey <chuckr@mat.net>, John Hay <jhay@mikom.csir.co.za>
Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, current@FreeBSD.ORG
Subject: Re: IPv6 in -current
References: <199811010922.LAA05107@zibbi.mikom.csir.co.za> <Pine.BSF.4.05.9811010922160.306-100000@picnic.mat.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <Pine.BSF.4.05.9811010922160.306-100000@picnic.mat.net>; from Chuck Robey on Sun, Nov 01, 1998 at 09:37:41AM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 01, 1998 at 09:37:41AM -0500, Chuck Robey wrote:
> On Sun, 1 Nov 1998, John Hay wrote:
> Would it be a reasonable thing to ask, that there be held an electronic
> debate? It need not be broadcast realtime ... the idea being that each
> team of developers be given the clearest possible chance to put forward
> their ideas in a sort of a debate-type encounter. This could be done
> via email to a 3rd party, a moderator, who would accumulate the results.
> If it was done via email, then (although it would be slower) it would
> not turn on momentary mistakes in phrasing so much as ability to present
> themselves; such a dialog could take up to a week or more to actually
> accumulate some presentable weight.
This kind of debate is what I would like to see in freebsd-arch (with
its new status as moderated but open to subscription by anybody). I
don't think a moderated but open discussion would be a problem; I hope
all of us (including the developers of each of the stacks) want to get
an as good as possible result for FreeBSD, not just a result in the
favour of ones 'original horse'.
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 1 12:37:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA02642
for freebsd-current-outgoing; Sun, 1 Nov 1998 12:37:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02636
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 12:37:16 -0800 (PST)
(envelope-from louie@whizzo.transsys.com)
Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1])
by whizzo.transsys.com (8.9.1/8.9.1) with ESMTP id PAA16366;
Sun, 1 Nov 1998 15:37:03 -0500 (EST)
(envelope-from louie@whizzo.transsys.com)
Message-Id: <199811012037.PAA16366@whizzo.transsys.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mike Smith <mike@smith.net.au>
cc: freebsd-current@FreeBSD.ORG
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: boot flags
References: <199811011959.LAA05344@dingo.cdrom.com>
In-reply-to: Your message of "Sun, 01 Nov 1998 11:59:50 PST."
<199811011959.LAA05344@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 01 Nov 1998 15:37:02 -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
This is exactly what I had in mind, thanks!
louie
> Now that the kernel can receive arbitrary information passed in from
> the loader, you'll do something like this:
>
>
> load -t userconfig_script /boot/userconfi.script
>
> and userconfig will just run down the list of userconfig_script
> objects, executing commands out of them.
>
> I'll aim to get this done today.
>
> --
> \\ 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 1 13:21:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA07864
for freebsd-current-outgoing; Sun, 1 Nov 1998 13:21:13 -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 NAA07858
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 13:21:11 -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 QAA02201;
Sun, 1 Nov 1998 16:19:57 -0500 (EST)
Date: Sun, 1 Nov 1998 16:19:57 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: John Hay <jhay@mikom.csir.co.za>, current@FreeBSD.ORG
Subject: Re: IPv6 in -current
In-Reply-To: <199811011929.OAA05742@khavrinen.lcs.mit.edu>
Message-ID: <Pine.BSF.4.05.9811011613140.306-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, 1 Nov 1998, Garrett Wollman wrote:
> <<On Sun, 1 Nov 1998 09:37:41 -0500 (EST), Chuck Robey <chuckr@mat.net> said:
>
> > This would serve to give the ideas their best airing, allow the
> > developers to present their cases in the lowest possible pressure
> > consistent with public disclosure, and probably give the loser at least
> > the feeling that they'd certainly been listened to, so their would be
> > less likelihood of injured feelings. And, FreeBSD would most likely to
> > get the best IPv6 implementation from it.
>
> I frankly don't care that much which IPv6 implementation is chosen.
> My concerns are the following:
>
> 2) that we don't screw any of the existing developers
>
> 1) that we make whatever necessary fundamental advances we can in the
> network stack before taking on additional deadweight
That's true ... however, we need a balance between making sure things
are right, and very long delays in getting things to that point.
Garrett, you're obviously point man on #1, and we recognize it's a good
point. Do you think we're in some sort of condition to wait for the
kernel improvements (will some reasonable extra delay give us those
fundamental advances, or just extra delay)?
Are we talking a month, 3 months, a year, what? Need at least a
feeling, I know asking for accuracy is ludicrous. Can't really evaluate
the weight of your statement without some feeling about the chances of
delay versus the chances of getting the improvements.
----------------------------+-----------------------------------------------
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 1 13:31:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA09099
for freebsd-current-outgoing; Sun, 1 Nov 1998 13:31:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns11.rim.or.jp (ns11.rim.or.jp [202.247.130.230])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09094
for <current@freebsd.org>; Sun, 1 Nov 1998 13:31:37 -0800 (PST)
(envelope-from masafumi@aslm.rim.or.jp)
Received: from rayearth.rim.or.jp (rayearth.rim.or.jp [202.247.130.242]) by ns11.rim.or.jp (8.8.5/3.5Wpl2-ns11/RIMNET-2) with ESMTP
id GAA00223; Mon, 2 Nov 1998 06:31:32 +0900 (JST)
Received: (from uucp@localhost) by rayearth.rim.or.jp (8.8.5/3.5Wpl2-uucp1/RIMNET) with UUCP
id GAA28121; Mon, 2 Nov 1998 06:31:31 +0900 (JST)
Received: from localhost (localhost [127.0.0.1]) by mail.aslm.rim.or.jp (8.9.1/3.5Wpl3-SMTP) with ESMTP id GAA01110; Mon, 2 Nov 1998 06:28:43 +0900 (JST)
To: current@FreeBSD.ORG
Cc: max@wide.ad.jp
Subject: Panic on -current kernel
From: Masafumi =?iso-2022-jp?B?TkFLQU5FLxskQkNmOiwybUo4GyhC?= <max@wide.ad.jp>
X-Mailer: Mew version 1.93 on Emacs 20.3 / Mule 4.0 (HANANOEN)
X-PGP-Fingerprint: 00 D8 2C CA C7 75 D4 40 5C 34 39 BA A5 46 C0 CC
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <19981102062842J.masafumi@aslm.rim.or.jp>
Date: Mon, 02 Nov 1998 06:28:42 +0900
X-Dispatcher: imput version 980905(IM100)
Lines: 189
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
As I updated my system to -current as of about a week ago, it started
to fail to boot up. I'm using a custom kernel and it dies as
follows. It didn't have any problem before the update, and the
situation remained the same when I tried to boot the box with kernel
built from the latest sources.
The latest GENERIC kernel, however, worked. The only major difference
between the GENERIC and my custom one is the use of softupdates. So I
disabled and retried, but it was not successful. The kernel
configuration file is attached following the resulting output of the
failure.
If anyone has any idea what I may be doing wrong, I appreciate your
suggestion.
----------------------------------------------------------------------
boot:
Booting 0:sd(0,a)kernel @ 0x100000
text=0xff000 data=0x17000 bss=0x221f0
symbols=[+0xe10+0x4+0x135cc+0x4+0x1d134]
total=0x269708 entry point=0x100000
BIOS basemem (637K) != RTC basemem (640K), setting to BIOS value
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 #34: Mon Nov 2 05:59:45 JST 1998
max@monster.jp.FreeBSD.ORG:/usr/src/sys/compile/MONSTER
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 299608746 Hz
CPU: Pentium II (299.61-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x633 Stepping=3
Features=0x80fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,MMX>
real memory = 268435456 (262144K bytes)
avail memory = 258940928 (252872K bytes)
Probing for devices on PCI bus 0:
Correcting Natoma config for non-SMP
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.1.0
chip2: <PCI to PCI bridge (vendor=1011 device=0024)> rev 0x02 on
pci0.13.0
vga0: <ATI Mach64-GT graphics accelerator> rev 0x41 on pci0.14.0
Probing for devices on PCI bus 1:
de0: <Digital 21040 Ethernet> rev 0x23 int a irq 10 on pci1.6.0
de0: ACCTON EN1203 21040 [10Mb/s] pass 2.3
de0: address 00:00:e8:0d:7d:e3
ncr0: <ncr 53c875 fast20 wide scsi> rev 0x04 int a irq 0 on pci1.8.0
ncr1: <ncr 53c875 fast20 wide scsi> rev 0x04 int a irq 11 on pci1.9.0
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, console
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
npx0 on motherboard
npx0: INT 16 interface
Waiting 8 seconds for SCSI devices to settle
de0: enabling 10baseT port
changing root devida0 at ncr1 bus 0 target 1 lun 0
da0: <IBM DCAS-34330 S65A> Fixed Direct Access SCSI2 device
da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled
da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
da1 at ncr1 bus 0 target 2 lun 0
da1: <IBM DCAS-34330 S65A> Fixed Direct Access SCSI2 device
da1: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled
da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
ce to da0s1a
swapon: adding /dev/sd0s1b as swap device
swapon: /dev/sd2s1b: Device not configured
Automatic reboot in progress...
/dev/rsd0s1a: clean, 9712 free (216 frags, 1187 blocks, 0.7%
fragmentation)
/dev/rsd0s1h: clean, 708954 free (13898 frags, 86882 blocks, 0.8%
fragmentation)
/dev/rsd0s1f: clean, 63502 free (14 frags, 7936 blocks, 0.0%
fragmentation)
/dev/rsd0s1g: clean, 549642 free (53154 frags, 62061 blocks, 3.3%
fragmentation)
/dev/rsd0s1e: clean, 251010 free (162 frags, 31356 blocks, 0.1%
fragmentation)
ffs_mountfs: superblock updated for soft updates
ffs_mountfs: superblock updated for soft updates
Doing initial network setup: hostname.
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
de0: flags=8c43<UP,BROADCAST,RUNNING,OACTIVE,SIMPLEX,MULTICAST> mtu
1500
inet 203.178.141.172 netmask 0xffffffe0 broadcast
203.178.141.191
ether 00:00:e8:0d:7d:e3
media: autoselect (10baseT/UTP) status: active
supported media: autoselect 10base5/AUI manual 10baseT/UTP
<full-duplex> 10baseT/UTP
add net default: gateway 203.178.141.161
Additional routing options: tcp extensions=NO.
routing daemons:.
Mounting NFS file systems.
clearing /tmp
recording kernel -c changes
additional daemons: syslogd.
Doing additional network setup: ntpdate xntpd portmap.
Starting final network daemons: mountd nfsd rpc.statd
Fatal double fault:
eip = 0xf01e1f40
esp = 0xf8802fb8
ebp = 0xefbfddb4
panic: double fault
syncing disks...
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xb8
fault code = supervisor read, page not present
instruction pointer = 0x8:0xf0129f6f
stack pointer = 0x10:0xf022eec8
frame pointer = 0x10:0xf022eedc
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = nested task, resume, IOPL = 0
current process = Idle
interrupt mask = net tty bio cam
trap number = 12
panic: page fault
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...
----------------------------------------------------------------------
The kernel config with all comment lines stripped.
----------------------------------------------------------------------
machine "i386"
cpu "I686_CPU"
ident MONSTER
maxusers 50
options INET #InterNETworking
options FFS #Berkeley Fast Filesystem
options SOFTUPDATES
options NFS #Network Filesystem
options MFS #Memory File System
options MSDOSFS #MSDOS Filesystem
options "CD9660" #ISO 9660 Filesystem
options PROCFS #Process filesystem
options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=8000 #Be pessimistic about Joe SCSI device
options UCONSOLE #Allow users to grab the console
options FAILSAFE #Be conservative
options USERCONFIG #boot -c editor
options VISUAL_USERCONFIG #visual boot -c editor
config kernel root on da0
controller isa0
controller eisa0
controller pci0
controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk fd0 at fdc0 drive 0
disk fd1 at fdc0 drive 1
options "CMD640" # work around CMD640 chip deficiency
controller ncr0
controller scbus0
device da0
device cd0 #Only need one of these, the code dynamically grows
device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr
device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 vector siointr
device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr
device lpt0 at isa? port? tty irq 7 vector lptintr
device de0
pseudo-device loop
pseudo-device ether
pseudo-device pty 128
pseudo-device gzip # Exec gzipped a.out's
pseudo-device bpfilter 16 #Berkeley packet filter
options SYSVSHM
options SYSVSEM
options SYSVMSG
options KTRACE #kernel tracing
----------------------------------------------------------------------
Cheers,
Max
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 14:10:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA14942
for freebsd-current-outgoing; Sun, 1 Nov 1998 14:10:22 -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 OAA14921
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 14:10:16 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from diabolique.ninth-circle.org ([195.121.59.131])
by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA2EDE for <current@FreeBSD.ORG>;
Sun, 1 Nov 1998 23:10:07 +0100
Message-ID: <XFMail.981101231401.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, 01 Nov 1998 23:14:01 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: FreeBSD Current <current@FreeBSD.ORG>
Subject: make install world problems
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Sorry to bug ye guys again, but make installworld is being a meanie to me ;)
Apparantly from time to time the install goes well untill it reaches certain
directories that do not exist:
install -c -o root -g wheel -m 644 removeuser/TRANS.TBL
/usr/share/examples/removeuser/TRANS.TBL
install: /usr/share/examples/removeuser/TRANS.TBL: No such file or directory
*** Error code 71
Stop.
*** Error code 1
This is the same problem as the lkm/vfs/module directory problem I mentioned
earlier.
For some reasons these directories are not created. Any reason why they are
being forgotten in the creation process? Because after I manually mkdir the
directory the make installworld continues...
install -c -o root -g wheel -m 644 sup/TRANS.TBL
/usr/share/examples/sup/TRANS.TBL
install: /usr/share/examples/sup/TRANS.TBL: No such file or directory
*** Error code 71
And then it fails on a next one... It's not for every directory however... So I
think I'll manage =)
Hope someone can explain this behaviour.
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 1 14:18:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA15865
for freebsd-current-outgoing; Sun, 1 Nov 1998 14:18:27 -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 OAA15859
for <current@freebsd.org>; Sun, 1 Nov 1998 14:18:26 -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 OAA16854;
Sun, 1 Nov 1998 14:17:09 -0800 (PST)
(envelope-from scottm@mordred.cs.ucla.edu)
Message-Id: <199811012217.OAA16854@mordred.cs.ucla.edu>
X-Mailer: exmh version 2.0.2 2/24/98
To: Chuck Robey <chuckr@mat.net>
cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
John Hay <jhay@mikom.csir.co.za>, current@FreeBSD.ORG
Subject: Re: IPv6 in -current
In-reply-to: Your message of "Sun, 01 Nov 1998 16:19:57 EST."
<Pine.BSF.4.05.9811011613140.306-100000@picnic.mat.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 01 Nov 1998 14:17:08 -0800
From: Scott Michel <scottm@cs.ucla.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
There are a couple of people at UCLA CS in Lixia Zhang's lab who
have experience working on the INRIA IPv6 code, as well as the
CAIRN people who have been actively doing IPv6 and IPSEC in their
version of the FreeBSD kernel (http://www.cairn.net/).
I've posted a message to our UCLA Internet Research Lab list to
see if anyone's interested/willing to do the integration.
-scooter
> On Sun, 1 Nov 1998, Garrett Wollman wrote:
>
> > <<On Sun, 1 Nov 1998 09:37:41 -0500 (EST), Chuck Robey <chuckr@mat.net> said:
> >
> > > This would serve to give the ideas their best airing, allow the
> > > developers to present their cases in the lowest possible pressure
> > > consistent with public disclosure, and probably give the loser at least
> > > the feeling that they'd certainly been listened to, so their would be
> > > less likelihood of injured feelings. And, FreeBSD would most likely to
> > > get the best IPv6 implementation from it.
> >
> > I frankly don't care that much which IPv6 implementation is chosen.
> > My concerns are the following:
> >
> > 2) that we don't screw any of the existing developers
> >
> > 1) that we make whatever necessary fundamental advances we can in the
> > network stack before taking on additional deadweight
>
> That's true ... however, we need a balance between making sure things
> are right, and very long delays in getting things to that point.
>
> Garrett, you're obviously point man on #1, and we recognize it's a good
> point. Do you think we're in some sort of condition to wait for the
> kernel improvements (will some reasonable extra delay give us those
> fundamental advances, or just extra delay)?
>
> Are we talking a month, 3 months, a year, what? Need at least a
> feeling, I know asking for accuracy is ludicrous. Can't really evaluate
> the weight of your statement without some feeling about the chances of
> delay versus the chances of getting the improvements.
>
> ----------------------------+-----------------------------------------------
> 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 Sun Nov 1 14:52:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA20288
for freebsd-current-outgoing; Sun, 1 Nov 1998 14:52:14 -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 OAA20282
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 14:52:11 -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 XAA01606;
Sun, 1 Nov 1998 23:48:54 +0100 (CET)
(envelope-from leifn@swimsuit.internet.dk)
Date: Sun, 1 Nov 1998 23:48:54 +0100 (CET)
From: Leif Neland <leifn@swimsuit.internet.dk>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: Dmitry Valdov <dv@dv.ru>, freebsd-current@FreeBSD.ORG,
Peter Wemm <peter@netplex.com.au>
Subject: Re: kernel compile problem
In-Reply-To: <XFMail.981101194426.asmodai@wxs.nl>
Message-ID: <Pine.BSF.4.05.9811012343110.1311-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
> > It could be implemented by modifying using cvsupd's ability to check out
> > the version of the tree as it were on a certain time.
> >
> > The committer sends it a command/file/signal, and then new additions
> > made after that time is not seen by someone who requests the latest
> > versions.
>
> Exactly, does the term commit-relay express the idea completely?
>
Nah, not really... I don't understand the word...
> > After everything is committed, the committer removes the lock.
>
> Why the commiter? Make it so that the cvsupd places a lock temporarily whenever
> a commit finds place. Then after the person is through with his or her commits
> it makes all those updated files available to the public for cvsup. Make it so
> that the daemon does the work and not the commiter. This saves hassle.
>
Not having done any committing, I guess a committer could make several
changes in different parts of the tree, in smaller chunks. Only the
committer will know when all the chunks have been committed. So only the
committer should unlock the changes.
As equivalent in the Oracle database, one session could make several
changesin different table, but only after issuing a commit, all changes
get visible for other sessions, and all at the same time.
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 1 15:04:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA21540
for freebsd-current-outgoing; Sun, 1 Nov 1998 15:04:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp.datacomm.ch (unix.datacomm.ch [212.40.5.52])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21532
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 15:04:16 -0800 (PST)
(envelope-from tseidmann@simultan.ch)
Received: from simultan.ch (line327.datacomm.ch [212.254.1.147])
by smtp.datacomm.ch (8.9.0/8.9.0) with ESMTP id AAA27777;
Mon, 2 Nov 1998 00:02:22 +0100
Message-ID: <363CE849.B76F70FF@simultan.ch>
Date: Mon, 02 Nov 1998 00:01:29 +0100
From: Thomas Seidmann <tseidmann@simultan.ch>
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Scott Michel <scottm@cs.ucla.edu>
CC: current@FreeBSD.ORG
Subject: Re: IPv6 in -current
References: <199811012217.OAA16854@mordred.cs.ucla.edu>
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:
>
> There are a couple of people at UCLA CS in Lixia Zhang's lab who
> have experience working on the INRIA IPv6 code, as well as the
> CAIRN people who have been actively doing IPv6 and IPSEC in their
> version of the FreeBSD kernel (http://www.cairn.net/).
>
> I've posted a message to our UCLA Internet Research Lab list to
> see if anyone's interested/willing to do the integration.
No matter how this discussion ends up, I'm starting to integrate INRIA
IPv6 into current (on my local src tree, of course) starting from
tomorrow. Whatever it will be used for :-) I am the one who started this
thread and you'll hear from me.
> -scooter
Regards, Thomas
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 15:11:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA22581
for freebsd-current-outgoing; Sun, 1 Nov 1998 15:11:43 -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 PAA22573
for <current@FreeBSD.org>; Sun, 1 Nov 1998 15:11:36 -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 AAA01037;
Mon, 2 Nov 1998 00:11:08 +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 AAA21882;
Mon, 2 Nov 1998 00:10:59 +0100 (CET)
Received: (from ticso@localhost)
by cicely5.cicely.de (8.9.0/8.9.0) id AAA15927;
Mon, 2 Nov 1998 00:10:59 +0100 (CET)
Message-ID: <19981102001058.41129@cicely.de>
Date: Mon, 2 Nov 1998 00:10:58 +0100
From: Bernd Walter <ticso@cicely.de>
To: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Cc: current@FreeBSD.ORG
Subject: Re: scsi disk (cam?) problems
References: <199811010132.UAA04810@bb01f39.unx.sas.com> <199811011924.MAA08917@narnia.plutotech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89i
In-Reply-To: <199811011924.MAA08917@narnia.plutotech.com>; from Justin T. Gibbs on Sun, Nov 01, 1998 at 12:24:09PM -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, Nov 01, 1998 at 12:24:09PM -0700, Justin T. Gibbs wrote:
> In article <19981101195246.10586@cicely.de> you wrote:
> > Very interesting.
> > I've saw the same message yesterday:
> > Oct 31 20:10:18 cicely5 /kernel: (da23:ahc4:0:1:0): Invalidating pack
>
> What kinds of power supplies are all of you using? The reason the
It's a new Power-Supply so maybe it's broken.
The supply has only this SCSI-Chain with 4-CDOMs 1 Streamer 1 HDD
and this MO Drive.
Only the MO Drive was used from this Supply at the time of the error.
Don't shure about the cabeling, because it's only up for 2 days.
I'll check it.
> pack is being invalidated is that the drive in question is not
> responding within a selection timeout period (250ms). This is
That's long - but I don't know how the drive handles media-errors.
At least my Win-NT Host on which the drive was connected before
has done serveral bus-resets in case of an media-problem.
They were reproduceable on the same sectors.
So maybe the firmware s broken.
> usually because of a device no being there, but I suspect in this
> case the cause is a parallel I/O load that pushes your drives
> to their maximum power rating, saturating your power supply leaving
> one or more devices starving for power. Any I/O attempted while
> the drive is going through a power-on reset is likely to fail with
> a selection timeout.
If it was a complete power-on reset the old SCSI-code would have given
me some information about during the next access - I asume CAM is doing
the same.
In case of a bus-problem I'm used to see things like bus-resets.
I don't realy like them - especialy with Streamers on the same bus - but
I'm shure sometimes they are sensefull.
What I don't understand is why the system can't recover from that failure.
as mentioned earlier the drive is still accessable via camcontrol but not
via the mounted fsdriver.
>
> I will change the error handler for the selection timeout case to
> return EIO instead of ENXIO, but this is just a temporary work around
By the way I'm not so deep into this - what are the differences?
> until we can provide a better pack invalidation scheme in the system.
>
> --
> Justin
--
Mfg B.Walter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 15:19:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA24008
for freebsd-current-outgoing; Sun, 1 Nov 1998 15:19:57 -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 PAA24000
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 15:19:55 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from diabolique.ninth-circle.org ([195.121.59.131])
by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA54E3; Mon, 2 Nov 1998 00:19:48 +0100
Message-ID: <XFMail.981102002342.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.9811012343110.1311-100000@gina.swimsuit.internet.dk>
Date: Mon, 02 Nov 1998 00:23:42 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Leif Neland <leifn@swimsuit.internet.dk>
Subject: Re: kernel compile problem
Cc: Peter Wemm <peter@netplex.com.au>, freebsd-current@FreeBSD.ORG,
Dmitry Valdov <dv@dv.ru>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 01-Nov-98 Leif Neland wrote:
>> > After everything is committed, the committer removes the lock.
>>
>> Why the commiter? Make it so that the cvsupd places a lock temporarily
>> whenever
>> a commit finds place. Then after the person is through with his or her
>> commits
>> it makes all those updated files available to the public for cvsup. Make it
>> so
>> that the daemon does the work and not the commiter. This saves hassle.
>>
> Not having done any committing, I guess a committer could make several
> changes in different parts of the tree, in smaller chunks. Only the
> committer will know when all the chunks have been committed. So only the
> committer should unlock the changes.
>
> As equivalent in the Oracle database, one session could make several
> changesin different table, but only after issuing a commit, all changes
> get visible for other sessions, and all at the same time.
That's what I meant =)
Except the Daemon (in this case the Oracle database) allowed the changes.
That's what I meant with the CVSupd too... The committer is expected to comm
it. The Daemon is expected to handle all the administivia of the
allowance/versioning. Hope this makes it clearer for the both of us. And the
others offcourse =)
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 1 15:34:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA25645
for freebsd-current-outgoing; Sun, 1 Nov 1998 15:34:55 -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 PAA25639
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 15:34:53 -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 AAA23004;
Mon, 2 Nov 1998 00:34:27 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id AAA29055;
Mon, 2 Nov 1998 00:34:26 +0100 (MET)
Message-ID: <19981102003426.04544@follo.net>
Date: Mon, 2 Nov 1998 00:34:26 +0100
From: Eivind Eklund <eivind@yes.no>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>,
Leif Neland <leifn@swimsuit.internet.dk>
Cc: Peter Wemm <peter@netplex.com.au>, freebsd-current@FreeBSD.ORG,
Dmitry Valdov <dv@dv.ru>
Subject: Re: kernel compile problem
References: <Pine.BSF.4.05.9811012343110.1311-100000@gina.swimsuit.internet.dk> <XFMail.981102002342.asmodai@wxs.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <XFMail.981102002342.asmodai@wxs.nl>; from Jeroen Ruigrok/Asmodai on Mon, Nov 02, 1998 at 12:23:42AM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Nov 02, 1998 at 12:23:42AM +0100, Jeroen Ruigrok/Asmodai wrote:
> Except the Daemon (in this case the Oracle database) allowed the changes.
> That's what I meant with the CVSupd too... The committer is expected to comm
> it. The Daemon is expected to handle all the administivia of the
> allowance/versioning. Hope this makes it clearer for the both of us. And the
> others offcourse =)
Sorry - this discussion is getting sort of useless. It _is_ possible
to handle this within cvs/cvsup, but if we are to do that, we will
have to create a lock for a single commit, and have cvsup grab the
previous version if this lock is present (a commit is in progress).
Making this will be a large set of changes both to cvs and cvsup. Due
to the time available to the relevant developers, I believe this is to
be very unlikely to happen. Besides this, I believe it would be less
work to replace all of cvs and cvsup than to implement this within the
present framework (if we allow the replacement to work against a real
database instead of working with a self-made database).
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 1 15:49:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA27439
for freebsd-current-outgoing; Sun, 1 Nov 1998 15:49:15 -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 PAA27416
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 15:49:11 -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 XAA21034;
Sun, 1 Nov 1998 23:47:53 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 XAA29687;
Sun, 1 Nov 1998 23:48:29 GMT
(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199811012348.XAA29687@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: "John W. DeBoskey" <jwd@unx.sas.com>
cc: green@zone.syracuse.net (Brian Feldman), freebsd-current@FreeBSD.ORG
Subject: Re: Changing sh for compatibility sake
In-reply-to: Your message of "Sun, 01 Nov 1998 11:56:31 EST."
<199811011656.LAA14169@bb01f39.unx.sas.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 01 Nov 1998 23:48:28 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Hi,
>
> I sent mail to this list a few months ago... pdksh doesn't run
> the tail-end of a pipe in the current shell environment, thus the
> following doesn't work as expected:
>
> export FOUND=0
> ls | wc -l | while read fcnt; do
> export FOUND=$fcnt
> done
> echo $FOUND
[.....]
The *only* shell I've ever seen that does this is the original ksh.
I think it's a *great* feature, but it's also non-standard. With it,
you can also
echo hello there | read a b
and get $a and $b back. Certainly, any version of sh, ash, zsh, bash
and pdksh that I've seen execute everything in the pipe in a subshell.
--
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 Sun Nov 1 16:10:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA02534
for freebsd-current-outgoing; Sun, 1 Nov 1998 16:10:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02528
for <current@FreeBSD.org>; Sun, 1 Nov 1998 16:10:22 -0800 (PST)
(envelope-from gibbs@plutotech.com)
Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130])
by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id RAA04209;
Sun, 1 Nov 1998 17:10:12 -0700 (MST)
Message-Id: <199811020010.RAA04209@pluto.plutotech.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bernd Walter <ticso@cicely.de>
cc: "Justin T. Gibbs" <gibbs@plutotech.com>, current@FreeBSD.ORG
Subject: Re: scsi disk (cam?) problems
In-reply-to: Your message of "Mon, 02 Nov 1998 00:10:58 +0100."
<19981102001058.41129@cicely.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 01 Nov 1998 17:03:23 -0700
From: "Justin T. Gibbs" <gibbs@plutotech.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> pack is being invalidated is that the drive in question is not
>> responding within a selection timeout period (250ms). This is
>That's long - but I don't know how the drive handles media-errors.
>At least my Win-NT Host on which the drive was connected before
>has done serveral bus-resets in case of an media-problem.
>They were reproduceable on the same sectors.
>So maybe the firmware s broken.
A media error may result in a command timeout, but not a selection timeout.
A selection timeout occurs when you attempt to select a device in order
to pass it a command. A command timeout occurs once you have issues a
command to a device and are waiting for it to complete. If this MO
device does not support tagged queuing, the selection timeout could
only occur when we attempted to select it and the device was idle.
>If it was a complete power-on reset the old SCSI-code would have given
>me some information about during the next access - I asume CAM is doing
>the same.
It should print out an error, yes. In this case, we get the selection
timeout first and stop talking to the device before we can even see
that a unit attention event has occurred.
>What I don't understand is why the system can't recover from that failure.
>as mentioned earlier the drive is still accessable via camcontrol but not
>via the mounted fsdriver.
Because the driver wants to be sure you, the user, validate that the
device has not been changed. You must unmount the device and remount
it in order to use it. Only once all clients that had the da device open
when the 'catastrophic' error occurred have closed the device will it
accept and open and I/O again.
The pass-thru device, as used by camcontrol, just passes commands directly
to the device, and it doesn't perform the same kinds of tracking that the
'da' block device driver does. Just because the underlying device is the
same does not mean that you are talking through the same driver. Multiple
drivers can share the same underlying SCSI device in CAM.
>> I will change the error handler for the selection timeout case to
>> return EIO instead of ENXIO, but this is just a temporary work around
>
>By the way I'm not so deep into this - what are the differences?
One says that there is no device there. The other indicates a per
-transaction I/O error. EIO is retried, ENXIO is not.
--
Justin
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 16:46:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA07836
for freebsd-current-outgoing; Sun, 1 Nov 1998 16:46:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles33.castles.com [208.214.165.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07826
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 16:46:18 -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 QAA06857;
Sun, 1 Nov 1998 16:45:47 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811020045.QAA06857@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mikael Karpberg <karpen@ocean.campus.luth.se>
cc: current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Sun, 01 Nov 1998 15:47:20 +0100."
<199811011447.PAA21479@ocean.campus.luth.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 01 Nov 1998 16:45:47 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> According to Mike Smith:
> > I have no desire to miss it. Give me a compact Forth interpreter that
> > links against libstand and you'll be seeing it everywhere Real Soon.
>
> Eeep! Umm... what exactly does this mean? I mean... I don't know anyone
> that knows forth... lots of people know sh. And a logical special
> language (whic resembles sh and the other script languages) is not
> real hard to learn either. Why mess it up and get forth in there? And
> to do what exactly?
Forth is a candidate because it can be implemented in a very compact
fashion, and bytecoded Forth is also very compact. In situations where
space is an issue, this gives it an enormous advantage. eg. the current
trivial interpreter is about 10k (minus command implementations); this
is about the same size as the complete Forth interpreter we're looking
at.
Using Forth gives us two major advantages:
- Because we can construct bindings between primitives economically,
additional functionality can be added with a correspondingly smaller
accumulation of bloat.
- The behaviour of the bootloader can be extended without having to
rebuild it. It becomes possible to attach extra intelligence to
the boot process allowing customisation eg. on a per-product or
per-module basis.
This is all very experimental, and I take your point about the learning
curve very seriously. If you can propose an extensible language with a
"traditional" syntax which can compete on a size basis (code, runtime
usage and bytecode size) then I would be happy to consider it.
--
\\ 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 1 16:47:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA07968
for freebsd-current-outgoing; Sun, 1 Nov 1998 16:47:45 -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 QAA07959
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 16:47:43 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id QAA22872;
Sun, 1 Nov 1998 16:47:33 -0800 (PST)
(envelope-from obrien)
Message-ID: <19981101164732.A22829@nuxi.com>
Date: Sun, 1 Nov 1998 16:47:32 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: Dom Mitchell <dom@myrddin.demon.co.uk>
Cc: current@FreeBSD.ORG
Subject: Re: Shells for you and shells for me
Reply-To: obrien@NUXI.com
References: <3633C8F8.EF8E14D5@null.net> <Pine.BSF.4.05.9810252016090.375-100000@picnic.mat.net> <19981026125133.A2717@netmonger.net> <19981029012621.A26396@nuxi.com> <E0zZEYK-000047-00.qmail@myrddin.demon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <E0zZEYK-000047-00.qmail@myrddin.demon.co.uk>; from Dom Mitchell on Fri, Oct 30, 1998 at 01:25:20PM +0000
X-Operating-System: FreeBSD 3.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Oct 30, 1998 at 01:25:20PM +0000, Dom Mitchell wrote:
> To be frank, I think that pdksh is definitely something that we should
> be looking at for that reason alone. If we import it into the tree
> and leave it installed as /bin/ksh, then people can test it at their
> leisure to see if it is worth replacing /bin/sh, and we also gain a
> ksh. It's a good situation.
This sounds like a good compromise. Unless there is serious objections,
I'll look into doing this.
--
-- 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 Sun Nov 1 17:04:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA09808
for freebsd-current-outgoing; Sun, 1 Nov 1998 17:04:01 -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 RAA09789
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 17:03:56 -0800 (PST)
(envelope-from logix@foobar.franken.de)
Received: (from logix@localhost)
by foobar.franken.de (8.8.8/8.8.5) id CAA19372
for freebsd-current@FreeBSD.ORG; Mon, 2 Nov 1998 02:03:47 +0100 (CET)
Message-ID: <19981102020346.A19337@foobar.franken.de>
Date: Mon, 2 Nov 1998 02:03:46 +0100
From: Harold Gutch <logix@foobar.franken.de>
To: freebsd-current@FreeBSD.ORG
Subject: ELF-kgdb on a.out-kernel
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
X-Organisation: BatmanSystemDistribution
X-Mission: To free the world from the Penguin
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
how do i use an ELF-gdb on an a.out-kernel ? Setting OBJFORMAT to
"aout" doesn't help and gdb doesn't recognize the
commandline-switch "-aout" (as other tools like nm do).
--
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 Sun Nov 1 17: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 RAA10612
for freebsd-current-outgoing; Sun, 1 Nov 1998 17:14:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10605
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 17:14:01 -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 UAA08774;
Sun, 1 Nov 1998 20:13:51 -0500 (EST)
(envelope-from wollman)
Date: Sun, 1 Nov 1998 20:13:51 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199811020113.UAA08774@khavrinen.lcs.mit.edu>
To: Chuck Robey <chuckr@mat.net>
Cc: current@FreeBSD.ORG
Subject: Re: IPv6 in -current
In-Reply-To: <Pine.BSF.4.05.9811011613140.306-100000@picnic.mat.net>
References: <199811011929.OAA05742@khavrinen.lcs.mit.edu>
<Pine.BSF.4.05.9811011613140.306-100000@picnic.mat.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Sun, 1 Nov 1998 16:19:57 -0500 (EST), Chuck Robey <chuckr@mat.net> said:
> Are we talking a month, 3 months, a year, what? Need at least a
Hard to tell -- it depends on a lot of external factors. I'm
currently working on a number of other things, and I know David
Greenman has his own agenda as well.
-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 1 17:32:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA12162
for freebsd-current-outgoing; Sun, 1 Nov 1998 17:32:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles33.castles.com [208.214.165.33])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12154
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 17:32: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 RAA07047;
Sun, 1 Nov 1998 17:31:52 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811020131.RAA07047@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Andrzej Bialecki <abial@nask.pl>
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Sun, 01 Nov 1998 19:06:42 +0100."
<Pine.BSF.4.02A.9811011858200.18422-100000@korin.warman.org.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 01 Nov 1998 17:31:51 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > It builds a little bigger here; it weighs in at about 40k. If you
> > strip the OO extensions out it comes down to about 22k. I don't know
>
> I stripped LOCALS, multithreading, stack checking, but added KEY... Well,
> this is still around 20k.
Ok. Should I commit my working version so that we have a central place
to perform the strip-down and integration?
> > whether there's much we can strip from the core wordset; I'll leave
> > that for the FORTH guruen to argue over. At 22k (plus whatever it
>
> As I said above, we probably can strip CORE-EXT and SEARCH - I wouldn't
> touch the CORE itself, however.
Again, being not much of a Forth head it's not clear whether we should
keep all of the compiled-in functionality and just strip the things
that can be reloaded at runtime.
I guess that items that are of principal interest to a programmer should
be conditionalised out, ie. produce a BFDK and a BFRT. 8)
> > costs to bind it in) I think we have a goer. Doug's resolved the Alpha
> > space issues too, so it should be comfy.
>
> Great! I think we won't regret it...
I hope not. 8) I'm all in favour of extension languages but I'm still
in two minds about whether Forth is going to be the right one for this
job.
> > > U __assert
> >
> > We need an assert.
>
> You mean: "anyway"? Because it's only as a diagnostics and can be defined
> as no-op.
I noticed. It should certainly be enabled in the BFDK.
--
\\ 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 1 17:39:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA12608
for freebsd-current-outgoing; Sun, 1 Nov 1998 17:39:14 -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 RAA12601;
Sun, 1 Nov 1998 17:39:09 -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 CAA26891;
Mon, 2 Nov 1998 02:39:04 +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 VAA03612;
Sun, 1 Nov 1998 21:47:27 +0100 (MET)
(envelope-from wosch)
Message-ID: <19981101214725.A3577@panke.de.freebsd.org>
Date: Sun, 1 Nov 1998 21:47:25 +0100
From: Wolfram Schneider <wosch@panke.de.freebsd.org>
To: current@FreeBSD.ORG
Cc: wosch@FreeBSD.ORG
Subject: Re: Missing IDE CD-ROM after 3.0 upgrade
References: <19981025183809.A1096@panke.de.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <19981025183809.A1096@panke.de.freebsd.org>; from Wolfram Schneider on Sun, Oct 25, 1998 at 06:38:09PM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 1998-10-25 18:38:09 +0100, Wolfram Schneider wrote:
> I just updated from 2.2.6R to 3.0. The new 3.0 kernel
> does not find the CD-ROM anymore ;-(
I tracked down the problem to a patch in Sep 1997. Before
the patch my IDE CD-ROM was detected by the kernel. After the
commit not ... Any change to fix this?
Wolfram
dyson 1997/09/20 00:41:58 PDT
Modified files:
sys/i386/conf LINT
sys/i386/isa wd.c wdreg.h
sys/pci ide_pci.c pcireg.h
Log:
Addition of support of the slightly rogue Promise IDE interface(Dyson), support
of multiple PCI IDE controllers(Dyson), and some updates and cleanups from
John Hood, who originally made our IDE DMA stuff work :-).
I have run tests with 7 IDE drives connected to my system, all in DMA
mode, with no errors. Modulo any bugs, this stuff makes IDE look
really good (within it's limitations.)
Submitted by: John Hood <cgull@smoke.marlboro.vt.us>
Revision Changes Path
1.368 +17 -2 src/sys/i386/conf/LINT
1.139 +55 -33 src/sys/i386/isa/wd.c
1.20 +7 -3 src/sys/i386/isa/wdreg.h
1.4 +1092 -614 src/sys/pci/ide_pci.c
1.19 +2 -1 src/sys/pci/pcireg.h
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 18:46:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA18714
for freebsd-current-outgoing; Sun, 1 Nov 1998 18:46:44 -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 SAA18701
for <freebsd-current@freebsd.org>; Sun, 1 Nov 1998 18:46:40 -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 MAA19222
for freebsd-current@freebsd.org; Mon, 2 Nov 1998 12:45:45 +1000 (EST)
(envelope-from akm)
From: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Message-Id: <199811020245.MAA19222@zeus.theinternet.com.au>
Subject: Booting Elf Kernel
To: freebsd-current@FreeBSD.ORG
Date: Mon, 2 Nov 1998 12:45:45 +1000 (EST)
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
Is it possible to boot an ELF kernel?
The Release Notes say that the kernel is still in aout format, but, is
there a way? I don't have any active LKM's to worry about, and I'm
reinstalling most of my stuff in ELF format anyway.
--
Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew
The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton
ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig
PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 19:07:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA20822
for freebsd-current-outgoing; Sun, 1 Nov 1998 19:07:36 -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 TAA20809
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 19:07:32 -0800 (PST)
(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
by dan.emsphone.com (8.9.1/8.9.1) id VAA21370;
Sun, 1 Nov 1998 21:05:12 -0600 (CST)
Date: Sun, 1 Nov 1998 21:05:12 -0600
From: Dan Nelson <dnelson@emsphone.com>
To: Brian Somers <brian@Awfulhak.org>, "John W. DeBoskey" <jwd@unx.sas.com>
Cc: Brian Feldman <green@zone.syracuse.net>, freebsd-current@FreeBSD.ORG
Subject: Re: Changing sh for compatibility sake
Message-ID: <19981101210512.A21213@emsphone.com>
References: <199811011656.LAA14169@bb01f39.unx.sas.com> <199811012348.XAA29687@woof.lan.awfulhak.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.3i
In-Reply-To: <199811012348.XAA29687@woof.lan.awfulhak.org>; from "Brian Somers" on Sun Nov 1 23:48:28 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 01), Brian Somers said:
> The *only* shell I've ever seen that does this is the original ksh.
> I think it's a *great* feature, but it's also non-standard. With it,
> you can also
>
> echo hello there | read a b
>
> and get $a and $b back. Certainly, any version of sh, ash, zsh, bash
> and pdksh that I've seen execute everything in the pipe in a subshell.
? I thought standard procedure was to execute the last command in a
pipe in the parent shell. Your command runs fine on zsh and bash (not
ash though).
-Dan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 19:22:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA22123
for freebsd-current-outgoing; Sun, 1 Nov 1998 19:22:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lamb.sas.com (lamb.sas.com [192.35.83.8])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22116
for <freebsd-current@freebsd.org>; Sun, 1 Nov 1998 19:22:09 -0800 (PST)
(envelope-from jwd@unx.sas.com)
Received: from mozart (mozart.unx.sas.com [192.58.184.8])
by lamb.sas.com (8.9.1/8.9.1) with SMTP id WAA07719;
Sun, 1 Nov 1998 22:21:48 -0500 (EST)
Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90)
id AA14761; Sun, 1 Nov 1998 22:21:47 -0500
Received: (from jwd@localhost)
by bb01f39.unx.sas.com (8.9.1/8.9.1) id WAA16023;
Sun, 1 Nov 1998 22:21:40 -0500 (EST)
(envelope-from jwd)
From: "John W. DeBoskey" <jwd@unx.sas.com>
Message-Id: <199811020321.WAA16023@bb01f39.unx.sas.com>
Subject: Re: scsi disk (cam?) problems (inodes & swap?)
In-Reply-To: <199811011628.AAA25291@spinner.netplex.com.au> from Peter Wemm at "Nov 2, 98 00:28:55 am"
To: peter@netplex.com.au (Peter Wemm)
Date: Sun, 1 Nov 1998 22:21:40 -0500 (EST)
Cc: freebsd-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
Hi,
A 2nd reply to this same msg:
Softupdates: No SMP: No
Anyways, just for grins, I 'umount'ed the 3 file systems I have
on the ccd (they went down cleanly). Then I fsck'd them. The 1st
two went fine. The 3rd gave:
FreeBSD# umount /snap
FreeBSD# fsck -y /dev/ccd0a
** /dev/rccd0a
** Last Mounted on /snap
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
LINK COUNT FILE I=146063 OWNER=root MODE=100444
SIZE=1771 MTIME=Oct 30 08:00 1998 COUNT 2 SHOULD BE 1
ADJUST? yes
LINK COUNT FILE I=146065 OWNER=root MODE=100444
SIZE=2311 MTIME=Oct 30 08:00 1998 COUNT 2 SHOULD BE 1
ADJUST? yes
..... About 50 more of these deleted ...
LINK COUNT FILE I=251568 OWNER=root MODE=100444
SIZE=1461 MTIME=Oct 30 08:00 1998 COUNT 2 SHOULD BE 1
ADJUST? yes
LINK COUNT FILE I=257185 OWNER=root MODE=100444
SIZE=3727 MTIME=Oct 30 07:58 1998 COUNT 2 SHOULD BE 1
ADJUST? yes
** Phase 5 - Check Cyl groups
1628 files, 32592 used, 1045183 free (4143 frags, 130130 blocks, 0.4% fragmentation)
***** FILE SYSTEM WAS MODIFIED *****
FreeBSD#
So, this make me wonder if we're really getting all the data
to disk properly (and this from a clean umount).
Comments, Critiques, and even stupid user remarks are welcome.
Thanks!
John
> "John W. DeBoskey" wrote:
> > Hello,
> >
> > Since rebooting last evenning and running:
> >
> > cd /usr/src && make world && cd release && make release
> >
> > my system hasn't died, but the following have shown up in messages.
> > fyi: my system has 256Meg of memory and I seriously doubt it ran out
> > of swap, and the ccd filesystems fsck'd clean twice before I started
> > the build.
> >
> > The cvsup msgs are normal, and left in for timing info only.
> >
> > Comments, critiques, & useful ideas are welcome...
> > Thanks!
> > John
>
> Did you have softupdates on? SMP?
>
> If you do not, then my immediate suspicion would be the changes I made
> yesterday, perhaps loosing some metadata updates.
>
> On the other hand, the swap pager message is worrying, we've seen this
> turning up before in the middle of other "strange" events. Did this
> release build process work before the changes yesterday?
>
> 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 1 19:43:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA24429
for freebsd-current-outgoing; Sun, 1 Nov 1998 19:43:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24421
for <freebsd-current@freebsd.org>; Sun, 1 Nov 1998 19:43:11 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (651 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m0zaAtV-0008G3C@rip.psg.com>
for <freebsd-current@freebsd.org>; Sun, 1 Nov 1998 19:43:05 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m0zaAtV-0008G3C@rip.psg.com>
Date: Sun, 1 Nov 1998 19:43:05 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: freebsd-current@FreeBSD.ORG
Subject: kerberos rlogin requires auth.conf
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
in kerberized rlogin there is the following fragment:
k = auth_getval("auth_list");
if (k && !strstr(k, "kerberos"))
use_kerberos = 0;
this means that, for me to do a kerberos login from A to B, that A must
have
auth_list = .* kerberos
in /etc/auth.conf
i thought that auth.conf controlled how folk get access TO the system,
not from it.
randy
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 20:12:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA28953
for freebsd-current-outgoing; Sun, 1 Nov 1998 20:12:54 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28925
for <current@freebsd.org>; Sun, 1 Nov 1998 20:12:51 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id XAA06386
for <current@freebsd.org>; Sun, 1 Nov 1998 23:12:39 -0500 (EST)
Date: Sun, 1 Nov 1998 23:12:38 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: current@FreeBSD.ORG
Subject: Linux clone()
Message-ID: <Pine.BSF.4.05.9811012304170.5699-100000@zone.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
Okay, guys, I think I've gotten a linux clone() syscall implemented... As
of now, I have nothing to test it with :( The only thing I have to try it
with is MpegTV, and for some really crazy reason:
linux_clone()->(1569, 1570); child eip=0xf00, esp=0x80ed0b4
Now come on, passing 0xf00 as the void *fn (really int (*fn)(void *)) is
pretty damned bogus (but hey, it's not zero, so it turns into the child's
instruction pointer...) If anyone has any REALY examples of programs to
test with this, let me know.... This is a pretty important thing to have,
when lots more apps use linuxthreads (i.e. StarOffice 5.0). Oh, BTW,
someone tell me if this would be something really terrible to accidentally
do in kernel space:
printf("%d %d %#x %#x");
note no arguments... so far I don't notice any destabilization but I sure
hope I didn't fudge up the kernel stack!
Cheers,
Brian Feldman
---patch follows---
diff -ur /usr/src/sys/i386/linux/linux_dummy.c
usr/src/sys/i386/linux/linux_dummy.c
--- /usr/src/sys/i386/linux/linux_dummy.c Thu Nov 6 14:28:52 1997
+++ usr/src/sys/i386/linux/linux_dummy.c Sun Nov 1 17:07:31 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);
diff -ur /usr/src/sys/i386/linux/linux_misc.c
usr/src/sys/i386/linux/linux_misc.c
--- /usr/src/sys/i386/linux/linux_misc.c Mon Oct 5 08:40:42 1998
+++ usr/src/sys/i386/linux/linux_misc.c Sun Nov 1 23:06:00 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>
@@ -557,6 +558,31 @@
return error;
if (p->p_retval[1] == 1)
p->p_retval[0] = 0;
+ return 0;
+}
+
+int
+linux_clone(struct proc *p, struct linux_clone_args *args)
+{
+ int error;
+ struct proc *p2;
+
+ if (error = fork1(p, RFPROC | RFMEM))
+ return error;
+ p2 = pfind(p->p_retval[0]);
+ if (p2 == 0)
+ return ESRCH;
+ if (args->stack)
+ p2->p_md.md_regs->tf_esp = (int)args->stack;
+ if (args->fn) {
+ p2->p_md.md_regs->tf_eip = (int)args->fn;
+ copyout(&args->arg, (void *)p2->p_md.md_regs->tf_esp, sizeof(void
*));
+ p2->p_md.md_regs->tf_esp -= sizeof(void *);
+ }
+#ifdef DEBUG_CLONE
+ printf("linux_clone()->(%d, %d); child eip=%#x, esp=%#x\n", p->p_pid,
+ p2->p_pid, p2->p_md.md_regs->tf_eip, p2->p_md.md_regs->tf_esp);
+#endif
return 0;
}
diff -ur /usr/src/sys/i386/linux/linux_proto.h
usr/src/sys/i386/linux/linux_proto.h
--- /usr/src/sys/i386/linux/linux_proto.h Fri Jul 10 18:30:04 1998
+++ usr/src/sys/i386/linux/linux_proto.h Sun Nov 1 17:07:31 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,10 @@
struct linux_sigcontext * scp; char scp_[PAD_(struct
linux_sigcontext *)];
};
struct linux_clone_args {
- register_t dummy;
+ void * fn; char fn_[PAD_(void *)];
+ void * stack; char stack_[PAD_(void *)];
+ int flags; char flags_[PAD_(int)];
+ void * arg; char arg_[PAD_(void *)];
};
struct linux_newuname_args {
struct linux_newuname_t * buf; char buf_[PAD_(struct
linux_newuname_t *)];
Only in usr/src/sys/i386/linux/: linux_proto.h.bak
diff -ur /usr/src/sys/i386/linux/linux_syscall.h
usr/src/sys/i386/linux/linux_syscall.h
--- /usr/src/sys/i386/linux/linux_syscall.h Fri Jul 10 18:30:06 1998
+++ usr/src/sys/i386/linux/linux_syscall.h Sun Nov 1 17:07:31 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
Only in usr/src/sys/i386/linux/: linux_syscall.h.bak
diff -ur /usr/src/sys/i386/linux/linux_sysent.c
usr/src/sys/i386/linux/linux_sysent.c
--- /usr/src/sys/i386/linux/linux_sysent.c Fri Jul 10 18:30:07 1998
+++ usr/src/sys/i386/linux/linux_sysent.c Sun Nov 1 17:07:31 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 */
+ { 4, (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 */
Only in usr/src/sys/i386/linux/: linux_sysent.c.bak
diff -ur /usr/src/sys/i386/linux/syscalls.master
usr/src/sys/i386/linux/syscalls.master
--- /usr/src/sys/i386/linux/syscalls.master Fri Jul 10 18:30:08 1998
+++ usr/src/sys/i386/linux/syscalls.master Sun Nov 1 17:07:31 1998
@@ -171,7 +171,8 @@
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(void *fn, void *stack,\
+ int flags, void *arg); }
121 NOPROTO LINUX { int setdomainname(char *name, \
int len); }
122 STD LINUX { int linux_newuname(struct linux_newuname_t
*buf); }
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 20:15:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA29245
for freebsd-current-outgoing; Sun, 1 Nov 1998 20:15:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29233
for <freebsd-current@freebsd.org>; Sun, 1 Nov 1998 20:15:14 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id XAA06405;
Sun, 1 Nov 1998 23:15:06 -0500 (EST)
Date: Sun, 1 Nov 1998 23:15:05 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: "John W. DeBoskey" <jwd@unx.sas.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Changing sh for compatibility sake
In-Reply-To: <199811011656.LAA14169@bb01f39.unx.sas.com>
Message-ID: <Pine.BSF.4.05.9811012313320.5699-100000@zone.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 this is an interesting matter of discussion that is currently going
around among pdksh developers, and is f course known. The "problem" is
that pdksh uses seperate processes for reading, so they wouldn't be able
to send data back. Stay tuned to pdksh development team news :)
Cheers,
Brian Feldman
On Sun, 1 Nov 1998, John W. DeBoskey wrote:
> Hi,
>
> I sent mail to this list a few months ago... pdksh doesn't run
> the tail-end of a pipe in the current shell environment, thus the
> following doesn't work as expected:
>
> export FOUND=0
> ls | wc -l | while read fcnt; do
> export FOUND=$fcnt
> done
> echo $FOUND
>
> So, the comment below might need a slight modification to say
> which scripts don't break... :-)
>
> Thanks!
> John
>
> > Let me repeat this once more: not a SINGLE script breaks with pdksh!
> >
> > Brian Feldman
> >
> > On Mon, 26 Oct 1998, Kurt D. Zeilenga wrote:
> >
> > > Chuck wrote:
> > > >I'm sorry, that's not true. Ask anyone who writes shell scripts that
> > > >install software (or perform any necessarily portable function) across
> > > >multiple platforms. sh is the shell to use ONLY BECAUSE it's the lowest
> > > >common denominator. Why else would they use the dumbest shell?
> > >
> > > I've written numerous system/install sh scripts. But it's not to
> > > one specific implementation, its many. It seems like every OS
> > > has it's own variant of sh. I do not know of any version of sh
> > > that can reliable used as a golden target sh. Each and very
> > > implementation of sh has its quirks that have to be dealt with.
> > > FreeBSD sh definitely has its, as do the others.
> > >
> > > Any change will likely cause problems in some existing scripts.
> > > Also, any change will cause developers to deal with additional
> > > portability issues. This is life. Most multiple platform sh
> > > developers have already adapted to specific quicks of popular
> > > sh implementations. Changing from one to another should not
> > > be that big of a deal. I suspect a few FreeBSD-only sh scripts
> > > will choke.
> > >
> > > Don't change sh for compatibility sake, our scripts are already
> > > compatible! Do change for functionality sake, we'll adapt as
> > > necessary.
> > >
> > > Kurt
> > >
> > > 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 1 20:56:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA04097
for freebsd-current-outgoing; Sun, 1 Nov 1998 20:56:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04085
for <freebsd-current@freebsd.org>; Sun, 1 Nov 1998 20:56:41 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (2831 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m0zaC2Y-0008G3C@rip.psg.com>
for <freebsd-current@freebsd.org>; Sun, 1 Nov 1998 20:56:30 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m0zaC2Y-0008G3C@rip.psg.com>
Date: Sun, 1 Nov 1998 20:56:30 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: freebsd-current@FreeBSD.ORG
Subject: screen not restored on exit of (less|more|vi|.*)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
xserver on CURRENT, two xterms, each running current bash etc.
o one to a bsdi 3.1 system (same on sunos, ...)
o one to the same freebsd host
say 'less foo' (or vi foo, or ...)
o quit less on bsdi and the screen is restored. i.e., you see
foo% more iddd.patch
foo%
i.e. all the remnants of less's output are gone, and the screen is
restored exactly as it was before the command ran, with a new prompt
right below the one that issued the command, even if it is mid-screen.
o after running less on freebsd the screen is not restored. i.e. the
remnants of less fill the screen with the new prompt on the bottom
line of the xterm, and the previous prompt and screen obliterated.
i prefer the former behavior, but do not understand how to cause the freebsd
system to adopt it.
looking at stty parms, the only differences are as follows:
bsdi
oflags: opost onlcr oxtabs
^^^^^^
cflags: cread cs8 -parenb -parodd hupcl -clocal -noclocal -cstopb
^^^^^^^^^
-cts_oflow -rts_iflow -mdmbuf
^^^^^^^^^^^^^^^^^^^^^
freebsd
oflags: opost onlcr -oxtabs
^^^^^^^
cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb
-crtscts -dsrflow -dtrflow -mdmbuf
^^^^^^^^^^^^^^^^^^^^^^^^^^
nothing tasty there. how about termcap?
bsdi
:al@:dl@:im=:ei=:mi@:ic=\E[@:\
:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:UP=\E[%dA:\
:al=\E[L:am:\
:bs:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:co#80:\
:cs=\E[%i%d;%dr:ct=\E[3k:\
:dc=\E[P:dl=\E[M:\
:im=\E[4h:ei=\E[4l:mi:\
:ho=\E[H:\
:is=\E[m\E[?7h\E[?1;3;4l\E[4l:\
:rs=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l\E<:\
:kb=^H:kd=\EOB:ke=\E[?1l\E>:\
:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
:k6=\E[16~:k7=\E[17~:k8=\E[18~:\
:kl=\EOD:km:kn#8:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:\
:li#65:md=\E[1m:me=\E[m:mr=\E[7m:ms:nd=\E[C:pt:\
:sc=\E7:rc=\E8:sf=\n:so=\E[7m:se=\E[m:sr=\EM:\
:te=\E[2J\E[?47l\E8:ti=\E7\E[?47h:\
:up=\E[A:us=\E[4m:ue=\E[m:xn:
freebsd
:li#65:\
:kh=\EOH:@7=\EOF:kb=^H:kD=^?:\
:k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:\
:hs:km:ts=\E[?E\E[?%i%dT:fs=\E[?F:es:ds=\E[?E:\
:is=\E>\E[?1;3;4;5l\E[?7;8h\E[1;65r\E[65;1H:\
:rs=\E>\E[?1;3;4;5l\E[?7;8h:\
:tc=vt220:
but
o replacing freebsd's with bsdi's (noting the te/ti)
o rebuilding termcap.db
o and starting a new xterm
gives me the same result.
any clues?
randy
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 21:07:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA05722
for freebsd-current-outgoing; Sun, 1 Nov 1998 21:07:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from garman.dyn.ml.org (pm106-19.dialip.mich.net [192.195.231.221])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA05715
for <current@freebsd.org>; Sun, 1 Nov 1998 21:07:25 -0800 (PST)
(envelope-from garman@garman.dyn.ml.org)
Message-Id: <199811020507.VAA05715@hub.freebsd.org>
Received: (qmail 22392 invoked from smtpd); 2 Nov 1998 05:08:08 -0000
Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1)
by localhost.garman.net with SMTP; 2 Nov 1998 05:08:08 -0000
Date: Mon, 2 Nov 1998 00:08:07 -0500 (EST)
From: garman@earthling.net
Reply-To: garman@earthling.net
Subject: still problems with inetd & malloc...
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
on my home machine (running -current as of yesterday) i'm still having
problems with inetd...
bash# telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
inetd in realloc(): warning: junk pointer, too low to make sense.
inetd in free(): warning: junk pointer, too low to make sense.
...
this is with only:
bash# uptime
12:07AM up 7:23, 8 users, load averages: 0.34, 0.29, 0.21
is there anything I can do to help diagnose this? My machine is a
pentiumII/300 with 96MB of memory, 150MB of swap (~50-60% in use at any
time) running -current aout (haven't had the guts to upgrade to elf yet
:))
my machine is not heavily loaded, it is simply my home workstation.
inetd is used for the most part simply to invoke qmail for my
incoming mail- around 200 msgs/day average.
compiling inetd with debugging symbols and attaching gdb to it while
running doesn't seem to resolve the symbols right... is there something
i'm missing there?
thanks
--
Jason Garman http://garman.dyn.ml.org/
Student, University of Maryland garman@earthling.net
And now... for the stupid-patent-of-the-week: Whois: JAG145
"...an attache case with destruct means for destroying the contents
therein in response to a signal" -- patent no. US3643609, filed in 1969
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 21:13:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA06551
for freebsd-current-outgoing; Sun, 1 Nov 1998 21:13:06 -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 VAA06545
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 21:13:04 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id VAA03306;
Sun, 1 Nov 1998 21:12:57 -0800 (PST)
(envelope-from obrien)
Message-ID: <19981101211257.A3217@nuxi.com>
Date: Sun, 1 Nov 1998 21:12:57 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc: current@FreeBSD.ORG
Subject: Re: IPv6 in -current
Reply-To: obrien@NUXI.com
References: <199811010922.LAA05107@zibbi.mikom.csir.co.za> <Pine.BSF.4.05.9811010922160.306-100000@picnic.mat.net> <199811011929.OAA05742@khavrinen.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199811011929.OAA05742@khavrinen.lcs.mit.edu>; from Garrett Wollman on Sun, Nov 01, 1998 at 02:29:09PM -0500
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 frankly don't care that much which IPv6 implementation is chosen.
> My concerns are the following:
So is sounds like those interested in IPv6 have the go-ahead to bring it
into -CURRENT.
--
-- 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 Sun Nov 1 21:23:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA08362
for freebsd-current-outgoing; Sun, 1 Nov 1998 21:23:50 -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 VAA08350
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 21:23:48 -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 AAA18222;
Mon, 2 Nov 1998 00:23:38 -0500 (EST)
(envelope-from wollman)
Date: Mon, 2 Nov 1998 00:23:38 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199811020523.AAA18222@khavrinen.lcs.mit.edu>
To: obrien@NUXI.com
Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, current@FreeBSD.ORG
Subject: Re: IPv6 in -current
In-Reply-To: <19981101211257.A3217@nuxi.com>
References: <199811010922.LAA05107@zibbi.mikom.csir.co.za>
<Pine.BSF.4.05.9811010922160.306-100000@picnic.mat.net>
<199811011929.OAA05742@khavrinen.lcs.mit.edu>
<19981101211257.A3217@nuxi.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Sun, 1 Nov 1998 21:12:57 -0800, "David O'Brien" <obrien@NUXI.com> said:
>> I frankly don't care that much which IPv6 implementation is chosen.
>> My concerns are the following:
> So is sounds like those interested in IPv6 have the go-ahead to bring it
> into -CURRENT.
No, they don't. Read what I wrote (and you oh-so-conveniently deleted).
-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 1 22:42:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA19490
for freebsd-current-outgoing; Sun, 1 Nov 1998 22:42:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA19386
for <freebsd-current@FreeBSD.ORG>; Sun, 1 Nov 1998 22:42:51 -0800 (PST)
(envelope-from ab@paert.tse-online.de)
Received: (qmail 7179 invoked by uid 1000); 2 Nov 1998 06:42:07 -0000
Message-ID: <19981102074207.B471@paert.tse-online.de>
Date: Mon, 2 Nov 1998 07:42:07 +0100
From: Andreas Braukmann <braukmann@tse-online.de>
To: freebsd-current@FreeBSD.ORG
Subject: Re: Changing sh for compatibility sake
Mail-Followup-To: freebsd-current@FreeBSD.ORG
References: <199811011656.LAA14169@bb01f39.unx.sas.com> <199811012348.XAA29687@woof.lan.awfulhak.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93i
In-Reply-To: <199811012348.XAA29687@woof.lan.awfulhak.org>; from Brian Somers on Sun, Nov 01, 1998 at 11:48:28PM +0000
Organization: TSE TeleService GmbH
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
On Sun, Nov 01, 1998 at 11:48:28PM +0000, Brian Somers wrote:
> > pdksh doesn't run the tail-end of a pipe in the current shell
> > environment,
> you can also
> echo hello there | read a b
> and get $a and $b back.
> Certainly, any version of sh, ash, zsh, bash and pdksh that
> I've seen execute everything in the pipe in a subshell.
Since I'm using constructions like this all the time (it is definitely
a great feature), I just have to state:
paert:[~] > echo hello there | read a b
paert:[~] > echo $a $b
hello there
paert:[~] >
I'm running zsh 3.0.5 as my interactive shell.
-ab
--
/// TSE TeleService GmbH | Gsf: Arne Reuter |
/// Hovestrasse 14 | Andreas Braukmann | We do it with
/// D-48351 Everswinkel | HRB: 1430, AG WAF | FreeBSD/SMP
/// -------------------------------------------------------------------
/// PGP-Key: http://www.tse-online.de/~ab/public-key
/// Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 23:17:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA23042
for freebsd-current-outgoing; Sun, 1 Nov 1998 23:17:22 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23032
for <current@FreeBSD.ORG>; Sun, 1 Nov 1998 23:17:19 -0800 (PST)
(envelope-from vallo@myhakas.matti.ee)
Received: from myhakas.matti.ee (vallo@myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id JAA04570; Mon, 2 Nov 1998 09:17:12 +0200 (EET)
Received: (from vallo@localhost)
by myhakas.matti.ee (8.9.1/8.9.1) id JAA02732;
Mon, 2 Nov 1998 09:17:12 +0200 (EET)
(envelope-from vallo)
Message-ID: <19981102091712.A2614@matti.ee>
Date: Mon, 2 Nov 1998 09:17:12 +0200
From: Vallo Kallaste <vallo@matti.ee>
To: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Cc: current@FreeBSD.ORG
Subject: Re: scsi disk (cam?) problems
Reply-To: vallo@matti.ee
References: <199811010132.UAA04810@bb01f39.unx.sas.com> <199811011924.MAA08917@narnia.plutotech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199811011924.MAA08917@narnia.plutotech.com>; from Justin T. Gibbs on Sun, Nov 01, 1998 at 12:24:09PM -0700
Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?=
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"Justin T. Gibbs" <gibbs@narnia.plutotech.com> wrote:
> What kinds of power supplies are all of you using? The reason the
> pack is being invalidated is that the drive in question is not
> responding within a selection timeout period (250ms). This is
I'm using new ATX power supply and it may be defective. I don't know
exactly because I have only 48 hours of uptime using this supply. If
my hardware configuration matters anyhow, I have dual processor
motherboard with two processors inserted, two Quantum UW disks,
Toshiba cdrom and floppy. Nothing extraordinary which can suck all the
power the supply can provide. I forgot to explain one thing while
reporting error: I got the panic just after executing copy command
'copy -R * /opt2'. I mounted Windows95 cd and tried to copy all
contents to hard drive. My cdrom drive is connected to an ncr scsi
controller and hard disks to onboard adaptec. At that time all the
filesystems were mounted with softupdates enabled.
Vallo Kallaste
vallo@matti.ee
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sun Nov 1 23: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 XAA24387
for freebsd-current-outgoing; Sun, 1 Nov 1998 23:30:59 -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 XAA24373
for <current@FreeBSD.org>; Sun, 1 Nov 1998 23:30:52 -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 PAA17256;
Mon, 2 Nov 1998 15:30:17 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811020730.PAA17256@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
cc: current@FreeBSD.ORG
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
In-reply-to: Your message of "Sun, 01 Nov 1998 12:16:00 MST."
<199811011916.MAA08880@narnia.plutotech.com>
Date: Mon, 02 Nov 1998 15:30:16 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"Justin T. Gibbs" wrote:
> In article <199811011622.AAA25247@spinner.netplex.com.au> you wrote:
> >
> > You need a kernel stack per thread in the lightweight model, up to a limit
> > of the number of cpus running, because it's needed for each possibly
> > active thread to make a syscall.
>
> I don't see how you can achieve such a limited number of stacks
> without a thread continuation model. If a thread calls tsleep
> while in kernel context, where does it's kernel stack go? If you
> always restart the thread from a thread continuation point, you
> can throw its stack away. This is certainly very desirable, but
> the impact on the kernel would be extremely large.
Yes, sorry about that, I managed to confuse myself. I wasn't talking
about thread continuation points, that's just too much work.
I was more thinking more how the present arrangement of having the PCB,
signal vectors, and pstats and kstack co-habitating the same pages would
have to be revisited and that only a maximum of numcpu kstacks would be in
memory at once.
The hassle is the signal vectors etc would be per process, some of the
pstats per thread, the rest per process, the pcb per thread, kstack per
thread, etc. Trying to seperate it all out, keeping track of what goes
where, while still perserving the ability to swap out the process and all
it's stacks, upages, etc to keep the unswappable per-thread and per-process
state to a minimum. The way to do this is probably to take the UPAGES out
of kvm managed space and have a chunk of address space (next to the
per-cpu pages perhaps) at a fixed address that holds swappable process
state, all the kstacks wired in as needed etc. Doing swapping would be
pretty easy then, and all this would be machdep parts right next to the
existing UPAGES swap support. It would probably be worthwhile having
idle thread kstack pages individually pageable, as well as 'swap the
whole damn lot out'. Going down this path would probably require some
sort of 'max kthreads per process' limit to enable address space layout.
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 2 00:11:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA29512
for freebsd-current-outgoing; Mon, 2 Nov 1998 00:11:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles312.castles.com [208.214.167.12])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29506
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 00:11:32 -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 AAA08861;
Mon, 2 Nov 1998 00:10:39 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811020810.AAA08861@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Randy Bush <randy@psg.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: screen not restored on exit of (less|more|vi|.*)
In-reply-to: Your message of "Sun, 01 Nov 1998 20:56:30 PST."
<m0zaC2Y-0008G3C@rip.psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 00:10:38 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> xserver on CURRENT, two xterms, each running current bash etc.
> o one to a bsdi 3.1 system (same on sunos, ...)
> o one to the same freebsd host
>
> say 'less foo' (or vi foo, or ...)
>
> o quit less on bsdi and the screen is restored. i.e., you see
>
> foo% more iddd.patch
> foo%
>
> i.e. all the remnants of less's output are gone, and the screen is
> restored exactly as it was before the command ran, with a new prompt
> right below the one that issued the command, even if it is mid-screen.
>
> o after running less on freebsd the screen is not restored. i.e. the
> remnants of less fill the screen with the new prompt on the bottom
> line of the xterm, and the previous prompt and screen obliterated.
>
> i prefer the former behavior, but do not understand how to cause the freebsd
> system to adopt it.
[... termcap ...]
> but
> o replacing freebsd's with bsdi's (noting the te/ti)
> o rebuilding termcap.db
> o and starting a new xterm
> gives me the same result.
>
> any clues?
It is indeed the te/ti escapes. I don't know what you've done, but it
was decided by many people that the use of te/ti was basically ugly
(and it has some bad associated bugs) so it was disabled.
--
\\ 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 2 00:14:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA29788
for freebsd-current-outgoing; Mon, 2 Nov 1998 00:14:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles312.castles.com [208.214.167.12])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29781
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 00:14: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 AAA08887;
Mon, 2 Nov 1998 00:14:08 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811020814.AAA08887@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman <green@zone.syracuse.net>
cc: current@FreeBSD.ORG
Subject: Re: Linux clone()
In-reply-to: Your message of "Sun, 01 Nov 1998 23:12:38 EST."
<Pine.BSF.4.05.9811012304170.5699-100000@zone.syracuse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 00:14:08 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Okay, guys, I think I've gotten a linux clone() syscall implemented... As
Neat. Wrong list perhaps though. (-emulation)
> of now, I have nothing to test it with :( The only thing I have to try it
> with is MpegTV, and for some really crazy reason:
> linux_clone()->(1569, 1570); child eip=0xf00, esp=0x80ed0b4
> Now come on, passing 0xf00 as the void *fn (really int (*fn)(void *)) is
> pretty damned bogus (but hey, it's not zero, so it turns into the child's
> instruction pointer...) If anyone has any REALY examples of programs to
> test with this, let me know....
First off; what do you get if you trace it on a Linux system? Are you
sure the args are formatted correctly?
> This is a pretty important thing to have,
> when lots more apps use linuxthreads (i.e. StarOffice 5.0).
No kidding.
> Oh, BTW,
> someone tell me if this would be something really terrible to accidentally
> do in kernel space:
> printf("%d %d %#x %#x");
> note no arguments... so far I don't notice any destabilization but I sure
> hope I didn't fudge up the kernel stack!
Nope; that's generally harmless, just prints lots of garbage.
As for test apps; someone ought to be able to build you a trivial
clone() test program on a Linux system.
--
\\ 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 2 00: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 AAA00681
for freebsd-current-outgoing; Mon, 2 Nov 1998 00:18:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles312.castles.com [208.214.167.12])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00675
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 00:18:23 -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 AAA08915;
Mon, 2 Nov 1998 00:17:37 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811020817.AAA08915@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-reply-to: Your message of "Mon, 02 Nov 1998 12:45:45 +1000."
<199811020245.MAA19222@zeus.theinternet.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 00:17:36 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Is it possible to boot an ELF kernel?
Yes.
> The Release Notes say that the kernel is still in aout format, but, is
> there a way? I don't have any active LKM's to worry about, and I'm
> reinstalling most of my stuff in ELF format anyway.
You probably want to update to -current first. Following a 'make world',
build an ELF kernel by setting KERNFORMAT to 'elf' in the environment
before doing the kernel build. Install the kernel as /kernel.elf
Reboot, and at the boot: prompt type '/boot/loader', then abort the
kernel load and type 'boot kernel.elf'.
If this works for you, the next step is to update the bootblocks with
'disklabel -B -b /boot/boot1 -s /boot/boot2 <disk>' where <disk> is
your boot slice. Remove any existing /boot.config file.
This will now default to using the new loader to boot your system.
Note that the new loader is still under development, so YMMV.
--
\\ 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 2 00: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 AAA02191
for freebsd-current-outgoing; Mon, 2 Nov 1998 00:25:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles312.castles.com [208.214.167.12])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02176;
Mon, 2 Nov 1998 00:25:41 -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 AAA08974;
Mon, 2 Nov 1998 00:25:04 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811020825.AAA08974@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Wolfram Schneider <wosch@panke.de.freebsd.org>
cc: current@FreeBSD.ORG, wosch@FreeBSD.ORG
Subject: Re: Missing IDE CD-ROM after 3.0 upgrade
In-reply-to: Your message of "Sun, 01 Nov 1998 21:47:25 +0100."
<19981101214725.A3577@panke.de.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 00:25:04 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On 1998-10-25 18:38:09 +0100, Wolfram Schneider wrote:
> > I just updated from 2.2.6R to 3.0. The new 3.0 kernel
> > does not find the CD-ROM anymore ;-(
>
> I tracked down the problem to a patch in Sep 1997. Before
> the patch my IDE CD-ROM was detected by the kernel. After the
> commit not ... Any change to fix this?
Er, no idea. You may have to break this down into several components
to work out which one(s) break you. I'd have to guess it was the
Promise controller changes. Then we'd need to work out a compromise
fix.
> Wolfram
>
> dyson 1997/09/20 00:41:58 PDT
>
> Modified files:
> sys/i386/conf LINT
> sys/i386/isa wd.c wdreg.h
> sys/pci ide_pci.c pcireg.h
> Log:
> Addition of support of the slightly rogue Promise IDE interface(Dyson), support
> of multiple PCI IDE controllers(Dyson), and some updates and cleanups from
> John Hood, who originally made our IDE DMA stuff work :-).
>
> I have run tests with 7 IDE drives connected to my system, all in DMA
> mode, with no errors. Modulo any bugs, this stuff makes IDE look
> really good (within it's limitations.)
>
> Submitted by: John Hood <cgull@smoke.marlboro.vt.us>
>
> Revision Changes Path
> 1.368 +17 -2 src/sys/i386/conf/LINT
> 1.139 +55 -33 src/sys/i386/isa/wd.c
> 1.20 +7 -3 src/sys/i386/isa/wdreg.h
> 1.4 +1092 -614 src/sys/pci/ide_pci.c
> 1.19 +2 -1 src/sys/pci/pcireg.h
>
>
>
> 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 Mon Nov 2 00: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 AAA05567
for freebsd-current-outgoing; Mon, 2 Nov 1998 00:51:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05560
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 00:51:24 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id DAA09336;
Mon, 2 Nov 1998 03:50:53 -0500 (EST)
Date: Mon, 2 Nov 1998 03:50:53 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: Mike Smith <mike@smith.net.au>
cc: current@FreeBSD.ORG
Subject: Re: Linux clone()
In-Reply-To: <199811020814.AAA08887@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811020346560.9280-100000@zone.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
Okay, thanks a bunch! I was worried about munging up my esp there :)
Anyway, I think it's about time to get a Linux user to a. make me a
program that uses clone and b. make me a ptrace of it. I suppose I'll post
the finished patch to freebsd-emulation when I get it finished, because
I'm not entirely certain why I posted it here in the first place... except
maybe that -current has the most generous testers usually!
Cheers,
Brian Feldman
On Mon, 2 Nov 1998, Mike Smith wrote:
> > Okay, guys, I think I've gotten a linux clone() syscall implemented... As
>
> Neat. Wrong list perhaps though. (-emulation)
>
> > of now, I have nothing to test it with :( The only thing I have to try it
> > with is MpegTV, and for some really crazy reason:
> > linux_clone()->(1569, 1570); child eip=0xf00, esp=0x80ed0b4
> > Now come on, passing 0xf00 as the void *fn (really int (*fn)(void *)) is
> > pretty damned bogus (but hey, it's not zero, so it turns into the child's
> > instruction pointer...) If anyone has any REALY examples of programs to
> > test with this, let me know....
>
> First off; what do you get if you trace it on a Linux system? Are you
> sure the args are formatted correctly?
>
> > This is a pretty important thing to have,
> > when lots more apps use linuxthreads (i.e. StarOffice 5.0).
>
> No kidding.
>
> > Oh, BTW,
> > someone tell me if this would be something really terrible to accidentally
> > do in kernel space:
> > printf("%d %d %#x %#x");
> > note no arguments... so far I don't notice any destabilization but I sure
> > hope I didn't fudge up the kernel stack!
>
> Nope; that's generally harmless, just prints lots of garbage.
>
> As for test apps; someone ought to be able to build you a trivial
> clone() test program on a Linux system.
>
> --
> \\ 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 2 01:07:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA07243
for freebsd-current-outgoing; Mon, 2 Nov 1998 01:07:50 -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 BAA07238
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 01:07:49 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id BAA05123;
Mon, 2 Nov 1998 01:07:43 -0800 (PST)
(envelope-from obrien)
Message-ID: <19981102010742.A5101@nuxi.com>
Date: Mon, 2 Nov 1998 01:07:42 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc: current@FreeBSD.ORG
Subject: Re: IPv6 in -current
Reply-To: obrien@NUXI.com
References: <199811010922.LAA05107@zibbi.mikom.csir.co.za> <Pine.BSF.4.05.9811010922160.306-100000@picnic.mat.net> <199811011929.OAA05742@khavrinen.lcs.mit.edu> <19981101211257.A3217@nuxi.com> <199811020523.AAA18222@khavrinen.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199811020523.AAA18222@khavrinen.lcs.mit.edu>; from Garrett Wollman on Mon, Nov 02, 1998 at 12:23:38AM -0500
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 frankly don't care that much which IPv6 implementation is chosen.
> >> My concerns are the following:
>
> > So is sounds like those interested in IPv6 have the go-ahead to bring it
> > into -CURRENT.
>
> No, they don't. Read what I wrote (and you oh-so-conveniently deleted).
And why not?
For review they were:
2) that we don't screw any of the existing developers
1) that we make whatever necessary fundamental advances we can in the
network stack before taking on additional deadweight
It is assumed you are working on (1).
So all that those that care about IPv6 need to do is adhear to (2) above.
--
-- 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 Mon Nov 2 01:29:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA09573
for freebsd-current-outgoing; Mon, 2 Nov 1998 01:29:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09555
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 01:29:20 -0800 (PST)
(envelope-from itojun@itojun.org)
Received: from localhost (itojun@localhost.itojun.org [127.0.0.1])
by coconut.itojun.org (8.9.1+3.1W/3.7W/smtpfeed 0.89) with ESMTP id SAA03071;
Mon, 2 Nov 1998 18:29:09 +0900 (JST)
To: enkhyl@hayseed.net
cc: Brian Feldman <green@zone.syracuse.net>, Mike Smith <mike@smith.net.au>,
John Hay <jhay@mikom.csir.co.za>,
Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, current@FreeBSD.ORG
In-reply-to: enkhyl's message of Fri, 30 Oct 1998 00:04:23 PST.
<Pine.BSF.4.05.9810292239520.324-100000@ender.sf.scient.com>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2
Subject: Re: IPv6 in -current
From: Jun-ichiro itojun Itoh <itojun@iijlab.net>
Date: Mon, 02 Nov 1998 18:29:09 +0900
Message-ID: <3068.909998949@coconut.itojun.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>I talked to the KAME folks a while back about helping to integrate their
>work into -current. The response I received was that they were integrating
>into one of the 3.0-BETA snapshots (unsure of which one), and that any
>patches I had to bring it up to -current would be useful once that
>integration was complete. My life's been kinda turned upside down
>recently, so I've been too busy to work on this (and other things I sorta
>committed to for FreeBSD) I'm not sure of the status on their integration.
>I'd certainly be willing to help out with testing, and when my life
>settles down a bit, I might be able to help with implementation, too. I'm
>another one that would really like to see IPv6 and IPSEC in FreeBSD.
This is itojun (the KAME team guy mentioned above).
Sorry that I was dead silent on this thread, I was really busy
this several weeks...
The current status and short-term plan for "KAME on freebsd3.0" is:
- we are doing the porting of KAME changes from 2.2.7 to 3.0-RELEASE
- it is not yet working with "options INET6" and "options IPSEC"
specified
- we'll open up our cvsup access to our repository (and probably
providing snapshot kit every week) when we can, at least, boot
INET6/IPSEC ready kernel
We have no problem merging this into repository in freefall,
other than the repository management issues for our side (KAME
team will have two maintain two separate repository in sync).
Cheers,
itojun@kame.net
itojun@itojun.org
jun-ichiro itoh
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 01:52:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA11766
for freebsd-current-outgoing; Mon, 2 Nov 1998 01:52:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cons.org (knight.cons.org [194.233.237.86])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11760
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 01:52:35 -0800 (PST)
(envelope-from cracauer@cons.org)
Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id KAA11938; Mon, 2 Nov 1998 10:52:05 +0100 (CET)
Message-ID: <19981102105205.A11918@cons.org>
Date: Mon, 2 Nov 1998 10:52:05 +0100
From: Martin Cracauer <cracauer@cons.org>
To: chet@po.cwru.edu, cracauer@cons.org
Cc: green@zone.syracuse.net, Studded@gorean.org, dag-erli@ifi.uio.no,
current@FreeBSD.ORG
Subject: Re: sh and ~ expansion
References: <19981028185553.A18168@cons.org> <981029145713.AA16764.SM@nike.ins.cwru.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <981029145713.AA16764.SM@nike.ins.cwru.edu>; from Chet Ramey on Thu, Oct 29, 1998 at 09:57:13AM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In <981029145713.AA16764.SM@nike.ins.cwru.edu>, Chet Ramey wrote:
> > Also, like bash pdksh fails to execute traps while a child that blocks
> > signals is running. Consider this:
> >
> > #! /bin/sh
> > trap 'echo aborting ; exit 1' 2
> > ./hardguy-that-blocks-sigint
> >
> > In bash and pdksh, the trap will be run *after* the blocking child
> > exited, while in our sh it will run the trap immediatly.
>
> The bash/pdksh behavior is required by POSIX.2, section 3.11. The
> FreeBSD sh is non-compliant.
Thanks for the information. I'd better protect this functionaly by a
switch, then.
Nothingtheless, we need the non-posix behaviour to keep an
interruptable /etc/rc in case a started program hangs with signals
blocked.
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer
Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536
Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 01:59:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA12852
for freebsd-current-outgoing; Mon, 2 Nov 1998 01:59:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cons.org (knight.cons.org [194.233.237.86])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12846
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 01:59:54 -0800 (PST)
(envelope-from cracauer@cons.org)
Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id KAA11960; Mon, 2 Nov 1998 10:59:36 +0100 (CET)
Message-ID: <19981102105935.B11918@cons.org>
Date: Mon, 2 Nov 1998 10:59:35 +0100
From: Martin Cracauer <cracauer@cons.org>
To: obrien@NUXI.com, Martin Cracauer <cracauer@cons.org>
Cc: current@FreeBSD.ORG
Subject: Re: sh and ~ expansion
References: <362B74B6.B9B256B4@gorean.org> <Pine.BSF.4.05.9810250920150.18224-100000@zone.syracuse.net> <19981028185553.A18168@cons.org> <19981029014317.C26396@nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <19981029014317.C26396@nuxi.com>; from David O'Brien on Thu, Oct 29, 1998 at 01:43:17AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In <19981029014317.C26396@nuxi.com>, David O'Brien wrote:
> > pdksh has a number of (IMHO) bugs with respect to signal handling. The
> > problem here is "what happens when a sh child uses SIGINT and/or
>
> So, lets fix them and submit the patches back to the pdksh developers.
Some problems:
1) It way be easier to fix the remaining syntax problems in ash
2) The signal behaviour of pdksh is probably intended (although most
other shells behave like ours and bash). If we had a pdksh as default
shell, people would be confused if it didn't behave as the normal
pdksh does.
3) Someone acutally had to do it. I'm certainly not doing all the
signal fixes a second time and the people who helped me are likely not
to be amused, either.
> > If you through away your shell and use a new one, you'll use a
> > valuable resource: All the PRs collected over the years.
>
> Why are old PRs so valuable?
They document remaining problems. This make it easier/possible to fix
them and to tell people exactly what they have to work around.
We could even claim them features if the documentation is good enough
:-)
> > For pdksh, you'll start from scratch
>
> So? For 3.0+ we added so many new things that we had to start from
> scratch on. ELF, new boot loader, Amd, 4.4Lite2 in the kernel, etc...
That isn't a reason to reset everything.
I can understand your point, you're maintainer of a lot of ports and
many of them depend on sh or even bash behaviour.
However, currently pdksh is not an alternative to the current FreeBSD
sh, especially for system startup.
Wouldn't it be easier to change port's scripts to #!/usr/local/bin/ksh
and require pdksh for build/run respectivly.
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer
Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536
Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 02:36:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA17302
for freebsd-current-outgoing; Mon, 2 Nov 1998 02:36:33 -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 CAA17293
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 02:36:29 -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 LAA25076;
Mon, 2 Nov 1998 11:41:12 +0100 (CET)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Mon, 2 Nov 1998 11:41:11 +0100 (CET)
From: Andrzej Bialecki <abial@nask.pl>
X-Sender: abial@korin.warman.org.pl
To: Mike Smith <mike@smith.net.au>
cc: current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-Reply-To: <199811020131.RAA07047@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.02A.9811021135260.20428-100000@korin.warman.org.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sun, 1 Nov 1998, Mike Smith wrote:
> > > It builds a little bigger here; it weighs in at about 40k. If you
> > > strip the OO extensions out it comes down to about 22k. I don't know
> >
> > I stripped LOCALS, multithreading, stack checking, but added KEY... Well,
> > this is still around 20k.
>
> Ok. Should I commit my working version so that we have a central place
> to perform the strip-down and integration?
Yes, that would be convenient.
> > > whether there's much we can strip from the core wordset; I'll leave
> > > that for the FORTH guruen to argue over. At 22k (plus whatever it
> >
> > As I said above, we probably can strip CORE-EXT and SEARCH - I wouldn't
> > touch the CORE itself, however.
>
> Again, being not much of a Forth head it's not clear whether we should
> keep all of the compiled-in functionality and just strip the things
> that can be reloaded at runtime.
>
> I guess that items that are of principal interest to a programmer should
> be conditionalised out, ie. produce a BFDK and a BFRT. 8)
Ehm... What?
> > Great! I think we won't regret it...
>
> I hope not. 8) I'm all in favour of extension languages but I'm still
> in two minds about whether Forth is going to be the right one for this
> job.
Well, most of things the bootloader currently does is pretty
straightforward in terms of "words", and would require only very few magic
incantations. Then, the next part could be hidden behind non-Forth-like
words after loading some /boot/forth_haters.4th...
Andrzej Bialecki
-------------------- ++-------++ -------------------------------------
<abial@nask.pl> ||PicoBSD|| FreeBSD in your pocket? Go and see:
Research & Academic |+-------+| "Small & Embedded FreeBSD"
Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/
-------------------- ~-+==---+-+ -------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 02:43:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA18015
for freebsd-current-outgoing; Mon, 2 Nov 1998 02:43:00 -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 CAA18009
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 02:42:57 -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 UAA23800;
Mon, 2 Nov 1998 20:41:16 +1000 (EST)
(envelope-from akm)
From: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Message-Id: <199811021041.UAA23800@zeus.theinternet.com.au>
Subject: Re: Booting Elf Kernel
In-Reply-To: <199811020817.AAA08915@dingo.cdrom.com> from Mike Smith at "Nov 2, 98 00:17:36 am"
To: mike@smith.net.au (Mike Smith)
Date: Mon, 2 Nov 1998 20:41:16 +1000 (EST)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
+----[ Mike Smith ]---------------------------------------------
| > Is it possible to boot an ELF kernel?
|
| Yes.
|
| > The Release Notes say that the kernel is still in aout format, but, is
| > there a way? I don't have any active LKM's to worry about, and I'm
| > reinstalling most of my stuff in ELF format anyway.
|
| You probably want to update to -current first. Following a 'make world',
| build an ELF kernel by setting KERNFORMAT to 'elf' in the environment
| before doing the kernel build. Install the kernel as /kernel.elf
I'd got this far... of course it wouldn't boot :-)
| Reboot, and at the boot: prompt type '/boot/loader', then abort the
| kernel load and type 'boot kernel.elf'.
I did some mucking around today.
I got to the point of putting /boot/loader into boot.config
and then got very confused... as it didn't want to load
',kernel.old'
I've got it booted now in time to read this email...
| If this works for you, the next step is to update the bootblocks with
| 'disklabel -B -b /boot/boot1 -s /boot/boot2 <disk>' where <disk> is
| your boot slice. Remove any existing /boot.config file.
This is my final step :-)
--
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 Mon Nov 2 02:47:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA18459
for freebsd-current-outgoing; Mon, 2 Nov 1998 02:47:27 -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 CAA18448
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 02:47:25 -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 CAA01511;
Mon, 2 Nov 1998 02:48:51 -0800 (PST)
Message-Id: <199811021048.CAA01511@implode.root.com>
To: obrien@NUXI.com
cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, current@FreeBSD.ORG
Subject: Re: IPv6 in -current
In-reply-to: Your message of "Mon, 02 Nov 1998 01:07:42 PST."
<19981102010742.A5101@nuxi.com>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 02 Nov 1998 02:48:51 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> >> I frankly don't care that much which IPv6 implementation is chosen.
>> >> My concerns are the following:
>>
>> > So is sounds like those interested in IPv6 have the go-ahead to bring it
>> > into -CURRENT.
>>
>> No, they don't. Read what I wrote (and you oh-so-conveniently deleted).
>
>And why not?
>
>
>For review they were:
>
> 2) that we don't screw any of the existing developers
>
> 1) that we make whatever necessary fundamental advances we can in the
> network stack before taking on additional deadweight
>
>It is assumed you are working on (1).
>So all that those that care about IPv6 need to do is adhear to (2) above.
We haven't made any decisions yet on which stack to go with. The KAME
implementation is compelling because of the dedication (to FreeBSD) of the
people working on it. INRIA is interesting because of rumors that it is
somehow "better" than KAME. The point Garrett is trying to make is that
once we decide on one, that leaves the other(s) out in the cold, which is
not a good thing.
With the above said, I disagree with waiting forever and think that a
decision on this should be made relatively soon (this year). I feel this
way mainly because I want to see FreeBSD more widely used as the basis
for further research in IPv6, and I think having IPv6 as part of the standard
system is the best way to acheive that. I think you'll find similar sentiment
in the rest of core team (minus Garrett).
-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 Mon Nov 2 03:16:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA22509
for freebsd-current-outgoing; Mon, 2 Nov 1998 03:16:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA22501
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 03:16:39 -0800 (PST)
(envelope-from itojun@itojun.org)
Received: from localhost (itojun@localhost.itojun.org [127.0.0.1])
by coconut.itojun.org (8.9.1+3.1W/3.7W) with ESMTP id UAA04616;
Mon, 2 Nov 1998 20:16:03 +0900 (JST)
To: dg@root.com
cc: obrien@NUXI.com, Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
current@FreeBSD.ORG
In-reply-to: dg's message of Mon, 02 Nov 1998 02:48:51 PST.
<199811021048.CAA01511@implode.root.com>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2
Subject: Re: IPv6 in -current
Date: Mon, 02 Nov 1998 20:16:03 +0900
Message-ID: <4612.910005363@coconut.itojun.org>
From: Jun-ichiro itojun Itoh <itojun@itojun.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> We haven't made any decisions yet on which stack to go with. The KAME
>implementation is compelling because of the dedication (to FreeBSD) of the
>people working on it. INRIA is interesting because of rumors that it is
>somehow "better" than KAME. The point Garrett is trying to make is that
>once we decide on one, that leaves the other(s) out in the cold, which is
>not a good thing.
NOTE: this is independent from the merging issues.
Could I hear about the technical reasons for the above "rumor"?
Could someone send me the details of what you felt?
I would like to fix that ASAP, if it really is a technical issues.
We are trying to catch up to latest IPv6 specs (I believe KAME is
most aggressive in this point), making coments to where specs seems
to be wrong, and so forth. We really are putting our 7x24 hours:-)
to KAME.
If it is packaging issues, I would like to state the following for
KAME 2.2.7 kit:
- we intentionally NOT overwriting existing tools,
like /usr/bin/ftp. This surprises people too much, especially
in multiuser installations.
- we are trying NOT to require "make World" for installation.
therefore, we do not use /usr/src tree for this.
It can be changed for KAME 3.0, of course.
If it is irrelevant for current@freebsd, plese reply me personally.
itojun@kame.net
itojun@itojun.org
jun-ichiro itoh
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 03:26:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA23664
for freebsd-current-outgoing; Mon, 2 Nov 1998 03:26:28 -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 DAA23658
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 03:26:26 -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 MAA02669;
Mon, 2 Nov 1998 12:26:12 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id MAA02588;
Mon, 2 Nov 1998 12:26:11 +0100 (MET)
Message-ID: <19981102122611.56328@follo.net>
Date: Mon, 2 Nov 1998 12:26:11 +0100
From: Eivind Eklund <eivind@yes.no>
To: Jun-ichiro itojun Itoh <itojun@itojun.org>, dg@root.com
Cc: obrien@NUXI.com, Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
current@FreeBSD.ORG
Subject: Re: IPv6 in -current
References: <199811021048.CAA01511@implode.root.com> <4612.910005363@coconut.itojun.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <4612.910005363@coconut.itojun.org>; from Jun-ichiro itojun Itoh on Mon, Nov 02, 1998 at 08:16:03PM +0900
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Nov 02, 1998 at 08:16:03PM +0900, Jun-ichiro itojun Itoh wrote:
[On KAME vs Inria]
> If it is packaging issues, I would like to state the following for
> KAME 2.2.7 kit:
> - we intentionally NOT overwriting existing tools,
> like /usr/bin/ftp. This surprises people too much, especially
> in multiuser installations.
> - we are trying NOT to require "make World" for installation.
> therefore, we do not use /usr/src tree for this.
> It can be changed for KAME 3.0, of course.
Everything negative towards KAME that I've seen has been on the
packaging - that it is not fully integrated. If you are willing to
fully integrate it, that issue seems moot.
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 2 03:40:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA25177
for freebsd-current-outgoing; Mon, 2 Nov 1998 03:40:09 -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 DAA25170
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 03:40:06 -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 DAA01931;
Mon, 2 Nov 1998 03:41:26 -0800 (PST)
Message-Id: <199811021141.DAA01931@implode.root.com>
To: Jun-ichiro itojun Itoh <itojun@itojun.org>
cc: obrien@NUXI.com, Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
current@FreeBSD.ORG
Subject: Re: IPv6 in -current
In-reply-to: Your message of "Mon, 02 Nov 1998 20:16:03 +0900."
<4612.910005363@coconut.itojun.org>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 02 Nov 1998 03:41:26 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> We haven't made any decisions yet on which stack to go with. The KAME
>>implementation is compelling because of the dedication (to FreeBSD) of the
>>people working on it. INRIA is interesting because of rumors that it is
>>somehow "better" than KAME. The point Garrett is trying to make is that
>>once we decide on one, that leaves the other(s) out in the cold, which is
>>not a good thing.
>
> NOTE: this is independent from the merging issues.
>
> Could I hear about the technical reasons for the above "rumor"?
It's just a rumor - I've heard no technical arguments to back it up. For
all that I know, KAME might very well be far superior to INRIA in every
respect.
> If it is packaging issues, I would like to state the following for
> KAME 2.2.7 kit:
> - we intentionally NOT overwriting existing tools,
> like /usr/bin/ftp. This surprises people too much, especially
> in multiuser installations.
> - we are trying NOT to require "make World" for installation.
> therefore, we do not use /usr/src tree for this.
> It can be changed for KAME 3.0, of course.
I actually would like to see a more thorough integration with the standard
tools being able to deal with both IPv4 and IPv6 simultaneously. It probably
makes sense to hold off on doing that work until KAME becomes a standard part
of the system, however - doing so now would make it a lot more difficult to
track FreeBSD-current.
-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 Mon Nov 2 03:48:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA26130
for freebsd-current-outgoing; Mon, 2 Nov 1998 03:48:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26123
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 03:48:23 -0800 (PST)
(envelope-from itojun@itojun.org)
Received: from localhost (itojun@localhost.itojun.org [127.0.0.1])
by coconut.itojun.org (8.9.1+3.1W/3.7W) with ESMTP id UAA05052;
Mon, 2 Nov 1998 20:48:03 +0900 (JST)
To: dg@root.com
cc: obrien@NUXI.com, Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
current@FreeBSD.ORG
In-reply-to: dg's message of Mon, 02 Nov 1998 03:41:26 PST.
<199811021141.DAA01931@implode.root.com>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2
Subject: Re: IPv6 in -current
Date: Mon, 02 Nov 1998 20:48:03 +0900
Message-ID: <5048.910007283@coconut.itojun.org>
From: Jun-ichiro itojun Itoh <itojun@itojun.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> If it is packaging issues, I would like to state the following for
>> KAME 2.2.7 kit:
>> - we intentionally NOT overwriting existing tools,
>> like /usr/bin/ftp. This surprises people too much, especially
>> in multiuser installations.
>> - we are trying NOT to require "make World" for installation.
>> therefore, we do not use /usr/src tree for this.
>> It can be changed for KAME 3.0, of course.
> I actually would like to see a more thorough integration with the standard
>tools being able to deal with both IPv4 and IPv6 simultaneously. It probably
>makes sense to hold off on doing that work until KAME becomes a standard part
>of the system, however - doing so now would make it a lot more difficult to
>track FreeBSD-current.
Actually *ALL* the KAME userland tools are dual stack ready.
KAME userland tools are installed into, say, /usr/local/v6/bin/ftp,
You can perform BOTH IPv4/v6 imply adding search path to
/usr/local/v6/{bin,sbin,whatever}.
ftp host.v4.freebsd.org makes IPv4 ftp,
ftp host.v4.freebsd.org makes IPv6 ftp.
If our document is silent about this, we'll add more comments into
documents.
(We feared to surprise people by tiny differences in /usr/bin/ftp
and /usr/local/v6/bin/ftp, and we have chosen to install userland
tools into /usr/local/v6)
itojun
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 03:50:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA26464
for freebsd-current-outgoing; Mon, 2 Nov 1998 03:50:48 -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 DAA26456
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 03:50:46 -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 DAA23727;
Mon, 2 Nov 1998 03:50:50 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: dg@root.com
cc: Jun-ichiro itojun Itoh <itojun@itojun.org>, obrien@NUXI.com,
Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, current@FreeBSD.ORG
Subject: Re: IPv6 in -current
In-reply-to: Your message of "Mon, 02 Nov 1998 03:41:26 PST."
<199811021141.DAA01931@implode.root.com>
Date: Mon, 02 Nov 1998 03:50:50 -0800
Message-ID: <23723.910007450@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I actually would like to see a more thorough integration with the standard
> tools being able to deal with both IPv4 and IPv6 simultaneously. It probably
> makes sense to hold off on doing that work until KAME becomes a standard part
> of the system, however - doing so now would make it a lot more difficult to
> track FreeBSD-current.
Yeah, if I had my druthers (and what the hell are "druthers" anyway,
and who here has ever had any that they knew of? Why is English such
a peculiar language? And why... Erm, excuse me, I guess that's not
really important right now), I'd want to see the IPv6 bits integrated
with the following provisos:
1. If you make the world with NOIPV6, the tools are built in the
traditional fashion without any support for IPv6 at all. This
would let the solution-in-a-box folks continue to compile binaries
with the smallest possible footprint, assuming that some of them
will have no need for IPv6.
2. If a binary (like ping) has been compiled with both v4/v6 support
and you simply want to turn its IPv6 behavior off for some reason,
it should check a well-known environment variable from its main()
to switch the relevant code in and out. Purists might even
argue that IPv6 should be turned off by default and only enabled
through such an environment variable (or compiler flag) rather than
the other way around. I guess I don't care either way so long as
IPv6 eventually, at the suitable time, becomes a desirable out-of-box
default for FreeBSD.
3. It interoperates with the other *BSDs and whatever form of IPv6
they've chosen.
I also agree that I don't think we can fence-sit on this one too much
longer, as much as I also *hate* the idea of alienating some other
group of hard-working IPv6 people. Not all decisions are either easy
or avoidable.
- 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 2 03:50:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA26474
for freebsd-current-outgoing; Mon, 2 Nov 1998 03:50:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26457
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 03:50:46 -0800 (PST)
(envelope-from itojun@itojun.org)
Received: from localhost (itojun@localhost.itojun.org [127.0.0.1])
by coconut.itojun.org (8.9.1+3.1W/3.7W) with ESMTP id UAA05119;
Mon, 2 Nov 1998 20:50:31 +0900 (JST)
To: dg@root.com, obrien@NUXI.com,
Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, current@FreeBSD.ORG
In-reply-to: itojun's message of Mon, 02 Nov 1998 20:48:03 JST.
<5048.910007283@coconut.itojun.org>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2
Subject: Re: IPv6 in -current
From: Jun-ichiro itojun Itoh <itojun@iijlab.net>
Date: Mon, 02 Nov 1998 20:50:31 +0900
Message-ID: <5115.910007431@coconut.itojun.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
typo fix:
> Actually *ALL* the KAME userland tools are dual stack ready.
> KAME userland tools are installed into, say, /usr/local/v6/bin/ftp,
> You can perform BOTH IPv4/v6 imply adding search path to
The last line should be:
... BOTH IPv4/v6 ftp by simply adding ...
itojun
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 03:54:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA26786
for freebsd-current-outgoing; Mon, 2 Nov 1998 03:54:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fgwnews.fujitsu.co.jp (fgwnews.fujitsu.co.jp [164.71.1.134])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26778
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 03:54:23 -0800 (PST)
(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from fdmnews.fujitsu.co.jp by fgwnews.fujitsu.co.jp (8.9.1a/3.7W-MX9810-Fujitsu Gateway)
id UAA23842; Mon, 2 Nov 1998 20:54:15 +0900 (JST)
Received: from chisato.nd.net.fujitsu.co.jp by fdmnews.fujitsu.co.jp (8.8.8+2.7Wbeta7/3.6W-980929-Fujitsu Domain Master)
id UAA05884; Mon, 2 Nov 1998 20:54:14 +0900 (JST)
Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.6.12+2.4W/3.3W8chisato-970826) with ESMTP id UAA10716; Mon, 2 Nov 1998 20:54:14 +0900
To: current@FreeBSD.ORG
Cc: kame@kame.net
Subject: Re: IPv6 in -current
X-Mailer: Mew version 1.93b38 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <19981102205353K.shin@nd.net.fujitsu.co.jp>
Date: Mon, 02 Nov 1998 20:53:53 +0900
From: Yoshinobu Inoue (=?ISO-2022-JP?B?GyRCMGY+ZU5JPy4bKEI=?=)
<shin@nd.net.fujitsu.co.jp>
X-Dispatcher: imput version 980905(IM100)
Lines: 16
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Just FYI.
I am a member of KAME project (for whom don't know it well, it is a
project which implements IPv6 and IPSEC ready free source code for BSD
variants). And I am a new comer to this list.
We are preparing FreeBSD 3.0 KAME kit. Currently, IPSEC began to
work, but needs more time for INET6, because we are also trying to
integrate KAME kernel's IPv4 and IPv6 transport modules into one, in
this opportunity. (now they are separated in netinet and netinet6)
But we began it and keep on working on it. We'll let you know as soon
as it become ready. Please wait a while.
Yoshinobu Inoue
shin@kame.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 04: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 EAA01143
for freebsd-current-outgoing; Mon, 2 Nov 1998 04:13:04 -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 EAA01137
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 04:13:03 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from diabolique.ninth-circle.org ([195.121.59.0])
by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA25FE; Mon, 2 Nov 1998 13:12:55 +0100
Message-ID: <XFMail.981102131654.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: <19981102003426.04544@follo.net>
Date: Mon, 02 Nov 1998 13:16:54 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Eivind Eklund <eivind@yes.no>, John Polstra <jdp@polstra.com>
Subject: Re: kernel compile problem
Cc: Dmitry Valdov <dv@dv.ru>, freebsd-current@FreeBSD.ORG,
Peter Wemm <peter@netplex.com.au>,
Leif Neland <leifn@swimsuit.internet.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 01-Nov-98 Eivind Eklund wrote:
> On Mon, Nov 02, 1998 at 12:23:42AM +0100, Jeroen Ruigrok/Asmodai wrote:
>> Except the Daemon (in this case the Oracle database) allowed the changes.
>> That's what I meant with the CVSupd too... The committer is expected to comm
>> it. The Daemon is expected to handle all the administivia of the
>> allowance/versioning. Hope this makes it clearer for the both of us. And the
>> others offcourse =)
>
> Sorry - this discussion is getting sort of useless. It _is_ possible
> to handle this within cvs/cvsup, but if we are to do that, we will
> have to create a lock for a single commit, and have cvsup grab the
> previous version if this lock is present (a commit is in progress).
> Making this will be a large set of changes both to cvs and cvsup. Due
> to the time available to the relevant developers, I believe this is to
> be very unlikely to happen. Besides this, I believe it would be less
> work to replace all of cvs and cvsup than to implement this within the
> present framework (if we allow the replacement to work against a real
> database instead of working with a self-made database).
Well, then my vote for starting on a new cvsup(d) which uses a real database is
in. Not that I am not satisfied with the current version, but as ye all know:
most things can be improved upon.
However the problem is the gradual migration from one cvsup platform to
another. People will always complain about why it had to change. I will be most
happy to donate time and work on this effort should others care to do likewise.
Then again, with the migration of ELF nearing, why shouldn't we scare the world
some more? *g*
regards,
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Mon Nov 2 04:29:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA03265
for freebsd-current-outgoing; Mon, 2 Nov 1998 04:29:19 -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 EAA03258
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 04:29:18 -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 EAA23985;
Mon, 2 Nov 1998 04:29:07 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Andrzej Bialecki <abial@nask.pl>
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Mon, 02 Nov 1998 11:41:11 +0100."
<Pine.BSF.4.02A.9811021135260.20428-100000@korin.warman.org.pl>
Date: Mon, 02 Nov 1998 04:29:07 -0800
Message-ID: <23981.910009747@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Well, most of things the bootloader currently does is pretty
> straightforward in terms of "words", and would require only very few magic
> incantations. Then, the next part could be hidden behind non-Forth-like
> words after loading some /boot/forth_haters.4th...
This is very true - I've seen 4th systems which offered both LISP and
"Tiny C" interpreters, both written in native 4th, and once you have a
genuine language underneath, you can put all kinds of nifty
abstractions on top. It's not hard to put an algebraic parser on top,
especially if you're already using stack-based arithmetic. ;-)
- 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 2 04:30:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA03534
for freebsd-current-outgoing; Mon, 2 Nov 1998 04:30:12 -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 EAA03525
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 04:30:10 -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 EAA24006;
Mon, 2 Nov 1998 04:30:21 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Brian Feldman <green@zone.syracuse.net>
cc: current@FreeBSD.ORG
Subject: Re: Linux clone()
In-reply-to: Your message of "Sun, 01 Nov 1998 23:12:38 EST."
<Pine.BSF.4.05.9811012304170.5699-100000@zone.syracuse.net>
Date: Mon, 02 Nov 1998 04:30:21 -0800
Message-ID: <24003.910009821@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Okay, guys, I think I've gotten a linux clone() syscall implemented... As
> of now, I have nothing to test it with :( The only thing I have to try it
Staroffice 5.0? :-)
- 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 2 04:37:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA04392
for freebsd-current-outgoing; Mon, 2 Nov 1998 04:37:10 -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 EAA04382
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 04:37:08 -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 EAA24086;
Mon, 2 Nov 1998 04:37:01 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Mike Smith <mike@smith.net.au>
cc: Andrzej Bialecki <abial@nask.pl>, current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Sun, 01 Nov 1998 17:31:51 PST."
<199811020131.RAA07047@dingo.cdrom.com>
Date: Mon, 02 Nov 1998 04:37:01 -0800
Message-ID: <24082.910010221@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Ok. Should I commit my working version so that we have a central place
> to perform the strip-down and integration?
Sounds good to me.
> Again, being not much of a Forth head it's not clear whether we should
> keep all of the compiled-in functionality and just strip the things
> that can be reloaded at runtime.
I think we should strip pretty much anything that can't be expressed
in high level forth. Now that I've found my 4th roadmap URL again, I
can look at some of the minimalist forths and grab or reference their
HLL implementations of various words from the forth83 spec.
> I hope not. 8) I'm all in favour of extension languages but I'm still
> in two minds about whether Forth is going to be the right one for this
> job.
Given the space constraints, one has to wonder whether you have any
choice. :-) It would be easy enough to add some simple conditional
expression parsing to the existing tiny interpreter, but that wouldn't
be anywhere near as flexible.
- 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 2 04:57:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA06285
for freebsd-current-outgoing; Mon, 2 Nov 1998 04:57:31 -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 EAA06278
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 04:57:29 -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 IAA16027;
Mon, 2 Nov 1998 08:00:18 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Mon, 2 Nov 1998 08:00:18 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Brian Feldman <green@zone.syracuse.net>
cc: current@FreeBSD.ORG
Subject: Re: Linux clone()
In-Reply-To: <199811020814.AAA08887@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811020759000.14876-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, 2 Nov 1998, Mike Smith wrote:
> > Oh, BTW,
> > someone tell me if this would be something really terrible to accidentally
> > do in kernel space:
> > printf("%d %d %#x %#x");
> > note no arguments... so far I don't notice any destabilization but I sure
> > hope I didn't fudge up the kernel stack!
>
> Nope; that's generally harmless, just prints lots of garbage.
>
> As for test apps; someone ought to be able to build you a trivial
> clone() test program on a Linux system.
>
Most of the developers here run linux boxen (well all of them except me)
send me code and i'll compile it.
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 2 05: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 FAA08063
for freebsd-current-outgoing; Mon, 2 Nov 1998 05: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 FAA08057
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 05:11:01 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id OAA22255;
Mon, 2 Nov 1998 14:08:55 +0100 (CET)
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: Mike Smith <mike@smith.net.au>, Andrzej Bialecki <abial@nask.pl>,
current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Mon, 02 Nov 1998 04:37:01 PST."
<24082.910010221@time.cdrom.com>
Date: Mon, 02 Nov 1998 14:08:54 +0100
Message-ID: <22253.910012134@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>Given the space constraints, one has to wonder whether you have any
>choice. :-) It would be easy enough to add some simple conditional
>expression parsing to the existing tiny interpreter, but that wouldn't
>be anywhere near as flexible.
What exactly are the the space constraints ?
How many [kK][bB] can we suffer ?
--
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 2 05:23:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA09522
for freebsd-current-outgoing; Mon, 2 Nov 1998 05:23:43 -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 FAA09511
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 05:23:40 -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 FAA24288;
Mon, 2 Nov 1998 05:23:46 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-reply-to: Your message of "Mon, 02 Nov 1998 12:45:45 +1000."
<199811020245.MAA19222@zeus.theinternet.com.au>
Date: Mon, 02 Nov 1998 05:23:46 -0800
Message-ID: <24284.910013026@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Is it possible to boot an ELF kernel?
Ayup. You gotta have the new boot blocks installed and /boot/loader
installed from the /sys/boot srcs, then set KERNFORMAT=elf in
/etc/make.conf and you're on your way.
- 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 2 05:53:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA13549
for freebsd-current-outgoing; Mon, 2 Nov 1998 05:53:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from qix (cabri.obs-besancon.fr [193.52.184.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13538
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 05:53:34 -0800 (PST)
(envelope-from jmz@FreeBSD.ORG)
Received: (from jmz@localhost)
by qix (8.9.1/8.8.7) id OAA09972;
Mon, 2 Nov 1998 14:54:18 +0100 (MET)
Date: Mon, 2 Nov 1998 14:54:18 +0100 (MET)
Message-Id: <199811021354.OAA09972@qix>
X-Authentication-Warning: qix: jmz set sender to jmz@qix using -f
From: Jean-Marc Zucconi <jmz@FreeBSD.ORG>
To: garman@earthling.net
CC: current@FreeBSD.ORG
In-reply-to: <199811020507.VAA05715@hub.freebsd.org> (garman@earthling.net)
Subject: Re: still problems with inetd & malloc...
X-Mailer: Emacs
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>>>>> garman writes:
> on my home machine (running -current as of yesterday) i'm still having
> problems with inetd...
> bash# telnet localhost 25
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> inetd in realloc(): warning: junk pointer, too low to make sense.
> inetd in free(): warning: junk pointer, too low to make sense.
> ...
There is a fix (it works for me). Look for
Subject: Re: bin/8183: Signal handlers in inetd.c are unsafe
in the archives.
Jean-Marc
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 05: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 FAA14450
for freebsd-current-outgoing; Mon, 2 Nov 1998 05:58:01 -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 FAA14410
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 05:57:58 -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 JAA16134;
Mon, 2 Nov 1998 09:00:46 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Mon, 2 Nov 1998 09:00:46 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-Reply-To: <24284.910013026@time.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811020900100.14876-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, 2 Nov 1998, Jordan K. Hubbard wrote:
> > Is it possible to boot an ELF kernel?
>
> Ayup. You gotta have the new boot blocks installed and /boot/loader
> installed from the /sys/boot srcs, then set KERNFORMAT=elf in
> /etc/make.conf and you're on your way.
>
> - Jordan
crashdump, kdb, ddb support yet?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 06: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 GAA17858
for freebsd-current-outgoing; Mon, 2 Nov 1998 06:18:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17850
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 06:18:49 -0800 (PST)
(envelope-from cracauer@gilgamesch.bik-gmbh.de)
Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id PAA28929; Mon, 2 Nov 1998 15:17:34 +0100 (MET)
Message-ID: <19981102151734.A25766@cons.org>
Date: Mon, 2 Nov 1998 15:17:34 +0100
From: Martin Cracauer <cracauer@cons.org>
To: obrien@NUXI.com, Dom Mitchell <dom@myrddin.demon.co.uk>
Cc: current@FreeBSD.ORG
Subject: Re: Shells for you and shells for me
References: <3633C8F8.EF8E14D5@null.net> <Pine.BSF.4.05.9810252016090.375-100000@picnic.mat.net> <19981026125133.A2717@netmonger.net> <19981029012621.A26396@nuxi.com> <E0zZEYK-000047-00.qmail@myrddin.demon.co.uk> <19981101164732.A22829@nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <19981101164732.A22829@nuxi.com>; from David O'Brien on Sun, Nov 01, 1998 at 04:47:32PM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In <19981101164732.A22829@nuxi.com>, David O'Brien wrote:
> On Fri, Oct 30, 1998 at 01:25:20PM +0000, Dom Mitchell wrote:
> > To be frank, I think that pdksh is definitely something that we should
> > be looking at for that reason alone. If we import it into the tree
> > and leave it installed as /bin/ksh, then people can test it at their
> > leisure to see if it is worth replacing /bin/sh, and we also gain a
> > ksh. It's a good situation.
>
> This sounds like a good compromise. Unless there is serious objections,
> I'll look into doing this.
Well, the only objection is that this doesn't offer much over having a
ksh port/package that is marked required by ports that can't live with
FreeBSD's sh.
On the other hand, it bloats the base system by ~320 KB (statically
linked) and since it isn't used by anything in the base system, people
will probably object against it.
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer
BSD User Group Hamburg, Germany http://www.bsdhh.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 2 06:20:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA18046
for freebsd-current-outgoing; Mon, 2 Nov 1998 06:20:28 -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 GAA18008
for <freebsd-current@freebsd.org>; Mon, 2 Nov 1998 06:20:09 -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 AAA25420
for freebsd-current@freebsd.org; Tue, 3 Nov 1998 00:18:54 +1000 (EST)
(envelope-from akm)
From: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Message-Id: <199811021418.AAA25420@zeus.theinternet.com.au>
Subject: Memory Usage under -current
To: freebsd-current@FreeBSD.ORG
Date: Tue, 3 Nov 1998 00:18:54 +1000 (EST)
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
I'm just comparing the sizes of processes under an ELF -current
and a 2.2.5 system, and my recollections of what my machine used to look
like.
It seems that a lot more memory is being consumed by the ELF system..
I expected there to be more used by the ELF system, but, not quite
that much...
e.g.
2.2.5 - Release.
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
294 root 3 0 180K 88K ttyin 0:00 0.00% 0.00% getty
295 root 3 0 180K 88K ttyin 0:00 0.00% 0.00% getty
296 root 3 0 180K 88K ttyin 0:00 0.00% 0.00% getty
18784 akm 18 0 572K 200K pause 0:00 0.00% 0.00% zsh
3.0 - Current.
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
224 root 3 0 1004K 340K ttyin 0:00 0.00% 0.00% getty
223 root 3 0 1004K 340K ttyin 0:00 0.00% 0.00% getty
243 akm 2 0 14084K 10772K select 5:45 7.29% 7.29% XF86_S3V
259 akm 18 0 1228K 592K pause 0:00 0.00% 0.00% zsh
Even with more used, I would expect the resident portion to be pretty
close to the 2.2.5 a.out.
Pre-elf upgrade I'm sure my X server was about half the size, although
all the X-libs are pretty big, so I guess it's not that surprising.
The X-server is ELF, but the zsh is a.out.
Under ELF everything but data is shareable? So most of that 340K (for
getty) is actually shared?
Should the memory limits in login.conf be upped (doubled?) for ELF
systems?
--
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 Mon Nov 2 06:27:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA18852
for freebsd-current-outgoing; Mon, 2 Nov 1998 06:27:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA18842
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 06:27:43 -0800 (PST)
(envelope-from jose@we.lc.ehu.es)
Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4)
id PAA26593; Mon, 2 Nov 1998 15:27:18 +0100
Message-ID: <363DC146.67C421D8@we.lc.ehu.es>
Date: Mon, 02 Nov 1998 15:27:18 +0100
From: "José Mª Alcaide" <jose@we.lc.ehu.es>
Organization: Universidad del PaÃs Vasco - Dept. de Electricidad y Electrónica
X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.7-STABLE i386)
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
CC: freebsd-current@FreeBSD.ORG
Subject: Re: screen not restored on exit of (less|more|vi|.*)
References: <m0zaC2Y-0008G3C@rip.psg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Randy Bush wrote:
>
> xserver on CURRENT, two xterms, each running current bash etc.
> o one to a bsdi 3.1 system (same on sunos, ...)
> o one to the same freebsd host
>
> say 'less foo' (or vi foo, or ...)
>
> o quit less on bsdi and the screen is restored. i.e., you see
>
> foo% more iddd.patch
> foo%
>
> i.e. all the remnants of less's output are gone, and the screen is
> restored exactly as it was before the command ran, with a new prompt
> right below the one that issued the command, even if it is mid-screen.
>
> o after running less on freebsd the screen is not restored. i.e. the
> remnants of less fill the screen with the new prompt on the bottom
> line of the xterm, and the previous prompt and screen obliterated.
>
> i prefer the former behavior, but do not understand how to cause the freebsd
> system to adopt it.
>
You should substitute the contents of the file
/usr/X11R6/lib/X11/etc/xterm.termcap for the xterm entries in
/usr/share/misc/termcap. Once done, run "cap_mkdb" to rebuild
the termcap.db database. This works for me. NOTE: The xterm.termcap
file distributed with XFree86 3.3.2 has a little bug: search for
the string "39m;49m" and change it to "39;49m".
However, there is a nasty secondary effect with "more": when you reach
the end of a file, "more" terminates, and the contents of the
last screen is lost. This effect can be avoided using the "-e"
option or, still better, defining the environment variable "MORE=-e".
Hope this helps,
-- JMA
-----------------------------------------------------------------------
Jose M. Alcaide | mailto:jose@we.lc.ehu.es
Universidad del Pais Vasco | http://www.we.lc.ehu.es/~jose
Dpto. de Electricidad y Electronica |
Facultad de Ciencias - Campus de Lejona | Tel.: +34-944647700 x2624
48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139
-----------------------------------------------------------------------
"Go ahead... make my day." - H. Callahan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 07:13:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA25788
for freebsd-current-outgoing; Mon, 2 Nov 1998 07:13:31 -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 HAA25781
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 07:13:27 -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 BAA25817;
Tue, 3 Nov 1998 01:12:25 +1000 (EST)
(envelope-from akm)
From: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
Message-Id: <199811021512.BAA25817@zeus.theinternet.com.au>
Subject: Re: Booting Elf Kernel
In-Reply-To: <199811020817.AAA08915@dingo.cdrom.com> from Mike Smith at "Nov 2, 98 00:17:36 am"
To: mike@smith.net.au (Mike Smith)
Date: Tue, 3 Nov 1998 01:12:25 +1000 (EST)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
+----[ Mike Smith ]---------------------------------------------
|
| If this works for you, the next step is to update the bootblocks with
| 'disklabel -B -b /boot/boot1 -s /boot/boot2 <disk>' where <disk> is
| your boot slice. Remove any existing /boot.config file.
|
| This will now default to using the new loader to boot your system.
| Note that the new loader is still under development, so YMMV.
It seems to be working ok so far...
--
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 Mon Nov 2 07:18:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA26160
for freebsd-current-outgoing; Mon, 2 Nov 1998 07:18:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fledge.watson.org (COPLAND.CODA.CS.CMU.EDU [128.2.222.48])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26154
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 07:18:18 -0800 (PST)
(envelope-from robert@cyrus.watson.org)
Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3])
by fledge.watson.org (8.8.8/8.8.8) with SMTP id KAA15423;
Mon, 2 Nov 1998 10:17:32 -0500 (EST)
Date: Mon, 2 Nov 1998 10:17:31 -0500 (EST)
From: Robert Watson <robert@cyrus.watson.org>
X-Sender: robert@fledge.watson.org
Reply-To: Robert Watson <robert+freebsd@cyrus.watson.org>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: dg@root.com, Jun-ichiro itojun Itoh <itojun@itojun.org>, obrien@NUXI.com,
Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, current@FreeBSD.ORG
Subject: Re: IPv6 in -current
In-Reply-To: <23723.910007450@time.cdrom.com>
Message-ID: <Pine.BSF.3.96.981102100920.15227E-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 2 Nov 1998, Jordan K. Hubbard wrote:
> Yeah, if I had my druthers (and what the hell are "druthers" anyway,
> and who here has ever had any that they knew of? Why is English such
> a peculiar language? And why... Erm, excuse me, I guess that's not
> really important right now), I'd want to see the IPv6 bits integrated
> with the following provisos:
English is a truly bizarre language. I'll dig up my OED this evening and
let you know :-P.
> 1. If you make the world with NOIPV6, the tools are built in the
> traditional fashion without any support for IPv6 at all. This
> would let the solution-in-a-box folks continue to compile binaries
> with the smallest possible footprint, assuming that some of them
> will have no need for IPv6.
Actually, I think a far more exciting option at some point in the process
would be NOIPV4, as that would imply that our network code was pretty
modular. :) The other cool thing would be to see NAT capable of IPv4/IPv6
translation so that we could market FreeBSD as an easy solution the the v6
enclave problem. Yet another case where BSD networking is the best choice
(or something).
> 2. If a binary (like ping) has been compiled with both v4/v6 support
> and you simply want to turn its IPv6 behavior off for some reason,
> it should check a well-known environment variable from its main()
> to switch the relevant code in and out. Purists might even
> argue that IPv6 should be turned off by default and only enabled
> through such an environment variable (or compiler flag) rather than
> the other way around. I guess I don't care either way so long as
> IPv6 eventually, at the suitable time, becomes a desirable out-of-box
> default for FreeBSD.
I suppose a useful one might actually be an environmental variable that
specifies what the 'default' IP version is for interpretting hostnames
that have both IPv4 and IPv6 addresses. That is, if my /etc/hosts (or
eventually DNS) returns both an IPv4 for my.friendly.host and an IPv6
address, which should get priority for use in programs (such as ping).
>From the point of view of IP addresses, ping should be able to distinguish
just fine which one you need.
> I also agree that I don't think we can fence-sit on this one too much
> longer, as much as I also *hate* the idea of alienating some other
> group of hard-working IPv6 people. Not all decisions are either easy
> or avoidable.
Heh. Good thing you core people are in the hot seat, not me. :)
Robert N Watson
Carnegie Mellon University http://www.cmu.edu/
TIS Labs at Network Associates, Inc. http://www.tis.com/
SafePort Network Services http://www.safeport.com/
robert@fledge.watson.org http://www.watson.org/~robert/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 07:57:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA29532
for freebsd-current-outgoing; Mon, 2 Nov 1998 07:57:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29526
for <freebsd-current@freebsd.org>; Mon, 2 Nov 1998 07:57:01 -0800 (PST)
(envelope-from patl@phoenix.volant.org)
From: patl@phoenix.volant.org
Received: from asimov.phoenix.volant.org ([205.179.79.65])
by phoenix.volant.org with smtp (Exim 1.92 #8)
id 0zaMLg-0000b2-00; Mon, 2 Nov 1998 07:56:56 -0800
Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4)
id HAA17034; Mon, 2 Nov 1998 07:56:50 -0800
Date: Mon, 2 Nov 1998 07:56:50 -0800 (PST)
Reply-To: patl@phoenix.volant.org
Subject: Re: screen not restored on exit of (less|more|vi|.*)
To: Randy Bush <randy@psg.com>
cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <m0zaC2Y-0008G3C@rip.psg.com>
Message-ID: <ML-3.3.910022210.2085.patl@asimov>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> say 'less foo' (or vi foo, or ...)
>
> o quit less on bsdi and the screen is restored. i.e., you see
>
> foo% more iddd.patch
> foo%
>
> i.e. all the remnants of less's output are gone, and the screen is
> restored exactly as it was before the command ran, with a new prompt
> right below the one that issued the command, even if it is mid-screen.
>
> o after running less on freebsd the screen is not restored. i.e. the
> remnants of less fill the screen with the new prompt on the bottom
> line of the xterm, and the previous prompt and screen obliterated.
>
> i prefer the former behavior, but do not understand how to cause the
> freebsd system to adopt it.
And I prefer the later. I find it extremely useful to be able to keep
the last screenful viewed in the scrollable history area while entering
new commands. Or to suspend emacs for long enough to issue a few commands,
and still see the text I was editing.
PLEASE don't force your preference on the rest of us. If you don't
want to lose the previous commands, make an alias or function for
more, less, etc. that emits a suitable number of linefeeds before
invoking the real thing.
-Pat
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 08:03:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA00698
for freebsd-current-outgoing; Mon, 2 Nov 1998 08:03:45 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00689
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 08:03:42 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (2048 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m0zaMS5-0008G3C@rip.psg.com>
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 08:03:33 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m0zaMS5-0008G3C@rip.psg.com>
Date: Mon, 2 Nov 1998 08:03:33 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "José Mª Alcaide" <jose@we.lc.ehu.es>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: screen not restored on exit of (less|more|vi|.*)
References: <m0zaC2Y-0008G3C@rip.psg.com>
<363DC146.67C421D8@we.lc.ehu.es>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> xserver on CURRENT, two xterms, each running current bash etc.
>> o one to a bsdi 3.1 system (same on sunos, ...)
>> o one to the same freebsd host
>>
>> say 'less foo' (or vi foo, or ...)
>>
>> o quit less on bsdi and the screen is restored. i.e., you see
>>
>> foo% more iddd.patch
>> foo%
>>
>> i.e. all the remnants of less's output are gone, and the screen is
>> restored exactly as it was before the command ran, with a new prompt
>> right below the one that issued the command, even if it is mid-screen.
>>
>> o after running less on freebsd the screen is not restored. i.e. the
>> remnants of less fill the screen with the new prompt on the bottom
>> line of the xterm, and the previous prompt and screen obliterated.
>>
>> i prefer the former behavior, but do not understand how to cause the freebsd
>> system to adopt it.
>
> You should substitute the contents of the file
> /usr/X11R6/lib/X11/etc/xterm.termcap for the xterm entries in
> /usr/share/misc/termcap. Once done, run "cap_mkdb" to rebuild
> the termcap.db database. This works for me. NOTE: The xterm.termcap
> file distributed with XFree86 3.3.2 has a little bug: search for
> the string "39m;49m" and change it to "39;49m".
YESSSSSSSSSSSSSSSSS!!!!!
> However, there is a nasty secondary effect with "more": when you reach
> the end of a file, "more" terminates, and the contents of the
> last screen is lost. This effect can be avoided using the "-e"
> option or, still better, defining the environment variable "MORE=-e".
yes yes. i actually use less with
LESS=-aCeiM -P %i/%m %f %lt/%L %pb\%
THANK YOU!
randy
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 08:08:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA01371
for freebsd-current-outgoing; Mon, 2 Nov 1998 08:08:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01361
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 08:08:52 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from diabolique.ninth-circle.org ([195.121.59.227])
by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA25A1 for <current@FreeBSD.ORG>;
Mon, 2 Nov 1998 16:08:36 +0100
Message-ID: <XFMail.981102171237.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: Mon, 02 Nov 1998 17:12:37 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: FreeBSD Current <current@FreeBSD.ORG>
Subject: Success!
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Yeehaw!
make world went alright today =)
Although it still had some quirks in certain sourcefiles (which I shall post
later on).
Now the next step is confusing for me, I might have missed something in all the
documentation I have read.
I have a slice /src in which I cvsup everything (wrong name, might convert it
to /ncvs) and have /src/ports /src/src /src/doc and /src/distrib
Now I did a make world in the /src/src directory. But this doesn't update
/usr/src right?
What do I have to do to update that all? Or am I suppose to cvsup everything in
/usr/src and then make world?
Also, one cannot start a new kernel config without setting up the proper tools
(e.g. make the new config and such...) Any more steps I am forgetting?
Thanks,
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Mon Nov 2 08:38:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA05006
for freebsd-current-outgoing; Mon, 2 Nov 1998 08:38:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04994
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 08:38:09 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA14156;
Mon, 2 Nov 1998 11:37:38 -0500 (EST)
Date: Mon, 2 Nov 1998 11:37:38 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: current@FreeBSD.ORG
Subject: Re: Linux clone()
In-Reply-To: <24003.910009821@time.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811021133380.13943-100000@zone.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
Yeah, that's what I'd want to try it out with, but I don't really have
the time-transportation necessary to pry it from that darn Star Division
:) If you can find me a good program to test out clone() with in the
meantime (hopefully compiled since it seems that the Linux toolchain is
majorly fudged path-wise on an ELF system... I fixed the includes problems
with wrappers, but linking still is wrong :( ) Find me a program to test
this with, make sure it works under Linux first, and I'll do my Damn Best
(TM) to get this system call working!
Cheers,
Brian Feldman
On Mon, 2 Nov 1998, Jordan K. Hubbard wrote:
> > Okay, guys, I think I've gotten a linux clone() syscall implemented... As
> > of now, I have nothing to test it with :( The only thing I have to try it
>
> Staroffice 5.0? :-)
>
> - 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 2 08:39:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA05137
for freebsd-current-outgoing; Mon, 2 Nov 1998 08:39:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05115
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 08:39:16 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA14163;
Mon, 2 Nov 1998 11:38:29 -0500 (EST)
Date: Mon, 2 Nov 1998 11:38:29 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: current@FreeBSD.ORG
Subject: Re: Linux clone()
In-Reply-To: <24003.910009821@time.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811021137590.13943-100000@zone.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
Oh, and I need the app that I can test with's source to refer to. NEED!
Cheers yet again,
Brian Feldman
On Mon, 2 Nov 1998, Jordan K. Hubbard wrote:
> > Okay, guys, I think I've gotten a linux clone() syscall implemented... As
> > of now, I have nothing to test it with :( The only thing I have to try it
>
> Staroffice 5.0? :-)
>
> - 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 Mon Nov 2 08:41:58 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA05520
for freebsd-current-outgoing; Mon, 2 Nov 1998 08:41:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05506
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 08:41:46 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA14224;
Mon, 2 Nov 1998 11:41:22 -0500 (EST)
Date: Mon, 2 Nov 1998 11:41:22 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>,
freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-Reply-To: <24284.910013026@time.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811021140280.13943-100000@zone.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
Be sure to let me know when ELF kernels can autoload kld modules like the
current a.out kernel does with lkm's.
Brian Feldman
On Mon, 2 Nov 1998, Jordan K. Hubbard wrote:
> > Is it possible to boot an ELF kernel?
>
> Ayup. You gotta have the new boot blocks installed and /boot/loader
> installed from the /sys/boot srcs, then set KERNFORMAT=elf in
> /etc/make.conf and you're on your way.
>
> - 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 Mon Nov 2 08:43:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA05752
for freebsd-current-outgoing; Mon, 2 Nov 1998 08:43:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05741
for <current@freebsd.org>; Mon, 2 Nov 1998 08:43:21 -0800 (PST)
(envelope-from jdp@austin.polstra.com)
Received: from austin.polstra.com (jdp@localhost)
by austin.polstra.com (8.9.1/8.9.1) with ESMTP id IAA07301;
Mon, 2 Nov 1998 08:43:08 -0800 (PST)
(envelope-from jdp)
Message-Id: <199811021643.IAA07301@austin.polstra.com>
To: asmodai@wxs.nl
Subject: Re: Another compile error
In-Reply-To: <XFMail.981101201322.asmodai@wxs.nl>
References: <XFMail.981101201322.asmodai@wxs.nl>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Date: Mon, 02 Nov 1998 08:43:08 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <XFMail.981101201322.asmodai@wxs.nl>,
Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> wrote:
> OK, that did the trick, I haven't spotted Attic in the make run no more
>
> Now I am stuck with this:
>
> install -c -o root -g wheel -m 644 lkm/syscall/test/testsyscall.c
> /usr/share/examples/lkm/syscall/test/testsyscall.c
> install -c -o root -g wheel -m 644 lkm/syscall/TRANS.TBL
> /usr/share/examples/lkm/syscall/TRANS.TBL
> install -c -o root -g wheel -m 644 lkm/syscall/Makefile
> /usr/share/examples/lkm/syscall/Makefile
> install -c -o root -g wheel -m 644 lkm/syscall/README
> /usr/share/examples/lkm/syscall/README
> install -c -o root -g wheel -m 644 lkm/vfs/module/TRANS.TBL
> /usr/share/examples/lkm/vfs/module/TRANS.TBL
> install: /usr/share/examples/lkm/vfs/module/TRANS.TBL: No such file or directory
> *** Error code 71
>
> Stop.
> *** Error code 1
>
> If I look in src/share/examples/lkm/vfs/module/ of my cvs slice I see TRANS.TBL
>
> What could cause this error then?
OK, let's face it. Your source tree is a hopeless mess, and it's not
worth wasting any more time trying to fix it. Delete all of /usr/src
and /usr/obj, fetch yourself a complete new source tree, and start
over. Anything else would be a waste of time and stomach acid at
this point. Sorry for the bad news, but that's the reality of the
situation on this particular machine.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 08:46:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA06077
for freebsd-current-outgoing; Mon, 2 Nov 1998 08:46:40 -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 IAA06071
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 08:46:39 -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 IAA25318;
Mon, 2 Nov 1998 08:46:31 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Brian Feldman <green@zone.syracuse.net>
cc: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>,
freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-reply-to: Your message of "Mon, 02 Nov 1998 11:41:22 EST."
<Pine.BSF.4.05.9811021140280.13943-100000@zone.syracuse.net>
Date: Mon, 02 Nov 1998 08:46:30 -0800
Message-ID: <25315.910025190@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Be sure to let me know when ELF kernels can autoload kld modules like the
> current a.out kernel does with lkm's.
Not my job - you can bloody well read -current like everybody else! :-)
- 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 2 08:47:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA06188
for freebsd-current-outgoing; Mon, 2 Nov 1998 08:47:47 -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 IAA06181
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 08:47:44 -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 IAA25336;
Mon, 2 Nov 1998 08:47:49 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: John Polstra <jdp@polstra.com>
cc: asmodai@wxs.nl, current@FreeBSD.ORG
Subject: Re: Another compile error
In-reply-to: Your message of "Mon, 02 Nov 1998 08:43:08 PST."
<199811021643.IAA07301@austin.polstra.com>
Date: Mon, 02 Nov 1998 08:47:49 -0800
Message-ID: <25333.910025269@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> OK, let's face it. Your source tree is a hopeless mess, and it's not
> worth wasting any more time trying to fix it. Delete all of /usr/src
Seconded. He seems to have ISO 9660 translation files in there which
makes me think somebody might have just blindly copied a live
filesystem's /usr/src or something at some point and the tree in
question is well and truly cactus. Time to push the big red Erase
button and start over!
- 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 2 08:49:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA06375
for freebsd-current-outgoing; Mon, 2 Nov 1998 08:49:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06369
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 08:49:27 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA14302;
Mon, 2 Nov 1998 11:48:53 -0500 (EST)
Date: Mon, 2 Nov 1998 11:48:53 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>,
freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-Reply-To: <25315.910025190@time.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811021147330.13943-100000@zone.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'm bringing up a valid point here, hey! You say we're ready for an ELF
kernel, but when mount can load FS's on the fly, then we're ready...
Brian Feldman
On Mon, 2 Nov 1998, Jordan K. Hubbard wrote:
> > Be sure to let me know when ELF kernels can autoload kld modules like the
> > current a.out kernel does with lkm's.
>
> Not my job - you can bloody well read -current like everybody else! :-)
>
> - 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 Mon Nov 2 09:27:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA10361
for freebsd-current-outgoing; Mon, 2 Nov 1998 09:27:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10335
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 09:27:05 -0800 (PST)
(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id TAA03714;
Mon, 2 Nov 1998 19:26:32 +0200 (SAT)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199811021726.TAA03714@zibbi.mikom.csir.co.za>
Subject: Re: Booting Elf Kernel
In-Reply-To: <Pine.BSF.4.05.9811021140280.13943-100000@zone.syracuse.net> from Brian Feldman at "Nov 2, 98 11:41:22 am"
To: green@zone.syracuse.net (Brian Feldman)
Date: Mon, 2 Nov 1998 19:26:31 +0200 (SAT)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Be sure to let me know when ELF kernels can autoload kld modules like the
> current a.out kernel does with lkm's.
It's not the kernel that loads them. Go and look in lib/libc/gen/getvfsent.c
John
--
John Hay -- John.Hay@mikom.csir.co.za
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 09:29:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA10533
for freebsd-current-outgoing; Mon, 2 Nov 1998 09:29:18 -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 JAA10526
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 09:29:15 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from diabolique.ninth-circle.org ([195.121.58.172])
by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA4EE6; Mon, 2 Nov 1998 18:29:08 +0100
Message-ID: <XFMail.981102183310.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: <25333.910025269@time.cdrom.com>
Date: Mon, 02 Nov 1998 18:33:10 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: Another compile error
Cc: current@FreeBSD.ORG, John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 02-Nov-98 Jordan K. Hubbard wrote:
>> OK, let's face it. Your source tree is a hopeless mess, and it's not
>> worth wasting any more time trying to fix it. Delete all of /usr/src
>
> Seconded. He seems to have ISO 9660 translation files in there which
> makes me think somebody might have just blindly copied a live
> filesystem's /usr/src or something at some point and the tree in
> question is well and truly cactus. Time to push the big red Erase
> button and start over!
OK, so the start was messed up... =)
Shall I write a newbie's point of view on cvsup then to contribute to
clearing things not that obvious?
[ lame attempt at humor: Ehm Jordan, what big red erase button? ]
thanks, I will update all tonight after I rm -rf'd the /usr/src and
/usr/obj plus know what to do with that /src slice I made...
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Mon Nov 2 09:29:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA10563
for freebsd-current-outgoing; Mon, 2 Nov 1998 09:29:22 -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 JAA10542
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 09:29:20 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from diabolique.ninth-circle.org ([195.121.58.172])
by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA4EF8; Mon, 2 Nov 1998 18:29:12 +0100
Message-ID: <XFMail.981102183314.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: <199811021643.IAA07301@austin.polstra.com>
Date: Mon, 02 Nov 1998 18:33:14 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: John Polstra <jdp@polstra.com>
Subject: Re: Another compile error
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 02-Nov-98 John Polstra wrote:
> OK, let's face it. Your source tree is a hopeless mess, and it's not
> worth wasting any more time trying to fix it. Delete all of /usr/src
> and /usr/obj, fetch yourself a complete new source tree, and start
> over. Anything else would be a waste of time and stomach acid at
> this point. Sorry for the bad news, but that's the reality of the
> situation on this particular machine.
Bad news? It ain't bad news for me if ye thought that =)
I always look on the bright side.
But this brings me to a thing I want to verify with you guys. rm -rf of
/usr/src and /usr/obj will not interfere the system as it is now right?
But where do I cvsup my files in? In /usr/src or on a seperate slice, this
has me wondering up till now.
Right now I cvsup into slice /src (wrong name, I know ;) and make world
from /src/src, but obviously /usr/src doesn't get updated that way. Am I
missing something stated with a 30 pt font on the webpages/manuals/handbook?
Thanks in advance for clearing that up,
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Mon Nov 2 09:40:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12138
for freebsd-current-outgoing; Mon, 2 Nov 1998 09:40:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12133
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 09:40:39 -0800 (PST)
(envelope-from jdp@austin.polstra.com)
Received: from austin.polstra.com (jdp@localhost)
by austin.polstra.com (8.9.1/8.9.1) with ESMTP id JAA07718;
Mon, 2 Nov 1998 09:40:29 -0800 (PST)
(envelope-from jdp)
Message-Id: <199811021740.JAA07718@austin.polstra.com>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: current@FreeBSD.ORG
Subject: Re: Another compile error
In-reply-to: Your message of "Mon, 02 Nov 1998 18:33:14 +0100."
<XFMail.981102183314.asmodai@wxs.nl>
Date: Mon, 02 Nov 1998 09:40:28 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> But this brings me to a thing I want to verify with you guys. rm -rf
> of /usr/src and /usr/obj will not interfere the system as it is now
> right?
Right. Then after that, be sure to "mkdir /usr/obj /usr/src" again.
> But where do I cvsup my files in? In /usr/src or on a seperate
> slice, this has me wondering up till now.
>
> Right now I cvsup into slice /src (wrong name, I know ;) and make
> world from /src/src, but obviously /usr/src doesn't get updated that
> way.
I recommend that you CVSup your sources to "/usr/src". That's the
standard place for the system sources.
--
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 2 09:42:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12334
for freebsd-current-outgoing; Mon, 2 Nov 1998 09:42:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12328
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 09:42:18 -0800 (PST)
(envelope-from jdp@austin.polstra.com)
Received: from austin.polstra.com (jdp@localhost)
by austin.polstra.com (8.9.1/8.9.1) with ESMTP id JAA07742;
Mon, 2 Nov 1998 09:42:09 -0800 (PST)
(envelope-from jdp)
Message-Id: <199811021742.JAA07742@austin.polstra.com>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, current@FreeBSD.ORG
Subject: Re: Another compile error
In-reply-to: Your message of "Mon, 02 Nov 1998 18:33:10 +0100."
<XFMail.981102183310.asmodai@wxs.nl>
Date: Mon, 02 Nov 1998 09:42:09 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Shall I write a newbie's point of view on cvsup then to contribute
> to clearing things not that obvious?
If you could distill the problems you encountered down to a few
questions and answers for the CVSup FAQ, I'd find that very useful.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 09:44:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12613
for freebsd-current-outgoing; Mon, 2 Nov 1998 09:44:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12604
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 09:44:40 -0800 (PST)
(envelope-from randy@psg.com)
Received: from localhost (708 bytes) by rip.psg.com
via sendmail with P:stdio/R:inet_resolve/T:smtp
(sender: <randy>) (ident <randy> using unix)
id <m0zaO1f-0008G4C@rip.psg.com>
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 09:44:23 -0800 (PST)
(Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13)
Message-Id: <m0zaO1f-0008G4C@rip.psg.com>
Date: Mon, 2 Nov 1998 09:44:23 -0800 (PST)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
To: Mike Smith <mike@smith.net.au>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: screen not restored on exit of (less|more|vi|.*)
References: <m0zaC2Y-0008G3C@rip.psg.com>
<199811020810.AAA08861@dingo.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> It is indeed the te/ti escapes. I don't know what you've done, but it
> was decided by many people that the use of te/ti was basically ugly
> (and it has some bad associated bugs) so it was disabled.
seems to work for me now that "José Mª Alcaide" <jose@we.lc.ehu.es>
showed me the hack.
randy
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 09:50:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA13074
for freebsd-current-outgoing; Mon, 2 Nov 1998 09:50:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13000;
Mon, 2 Nov 1998 09:49:58 -0800 (PST)
(envelope-from gmarco@giovannelli.it)
Received: from suzy (modem03.masternet.it [194.184.65.13])
by www.giovannelli.it (8.8.8/8.8.5) with SMTP id SAA00799;
Mon, 2 Nov 1998 18:44:28 +0100 (MET)
Message-Id: <199811021744.SAA00799@www.giovannelli.it>
From: "Gianmarco Giovannelli" <gmarco@giovannelli.it>
To: current@FreeBSD.ORG
Date: Mon, 2 Nov 1998 18:57:27 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: bt848 broken ?
Reply-to: gmarco@giovannelli.it
CC: multimedia@FreeBSD.ORG
X-mailer: Pegasus Mail for Win32 (v3.01b)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
It's a couple of days that I receive this error when I try to compile the kernel
(cvsupped twice a day, last five minutes ago 981102 18:45 CET)
.c ../../libkern/strcat.c ../../libkern/strcmp.c ../../libkern/strcpy.c
../../libkern/strlen.c ../../libkern/strncmp.c ../../libkern/strncpy.c
../../libkern/udivdi3.c ../../libkern/umoddi3.c swapkernel.c ioconf.c param.c
vnode_if.c config.c
../../pci/brooktree848.c:361: smbus_if.h: No such file or directory
../../pci/brooktree848.c:362: iicbus_if.h: No such file or directory
../../pci/bt848_i2c.c:61: iicbb_if.h: No such file or directory
../../pci/bt848_i2c.c:62: smbus_if.h: No such file or directory
mkdep: compile failed
*** Error code 1
Stop.
Have I missed something ?
Best Regards,
Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco)
"Unix expert since yesterday"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 10:20:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA15356
for freebsd-current-outgoing; Mon, 2 Nov 1998 10:20:26 -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 KAA15348
for <current@freebsd.org>; Mon, 2 Nov 1998 10:20:22 -0800 (PST)
(envelope-from fanf@demon.net)
Received: by server.noc.demon.net; id SAA09830; Mon, 2 Nov 1998 18:20:12 GMT
Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2)
id xmaa09821; Mon, 2 Nov 98 18:20:06 GMT
Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2)
id 0zaOmm-0004U0-00; Mon, 2 Nov 1998 18:33:04 +0000
To: current@FreeBSD.ORG
From: Tony Finch <dot@dotat.at>
Subject: Re: Linux clone()
Newsgroups: chiark.mail.freebsd.current
In-Reply-To: <Pine.BSF.4.05.9811012304170.5699-100000@zone.syracuse.net>
Organization: Deliberate Obfuscation To Amuse Tony
Message-Id: <E0zaOmm-0004U0-00@fanf.noc.demon.net>
Date: Mon, 2 Nov 1998 18:33:04 +0000
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Feldman <green@zone.syracuse.net> wrote:
>
>Okay, guys, I think I've gotten a linux clone() syscall
>implemented... As of now, I have nothing to test it with :( [...]
>This is a pretty important thing to have, when lots more apps use
>linuxthreads (i.e. StarOffice 5.0).
A good example of this is Squid compiled up to use async IO. I can put
a tar file or something together for you if you like. I'll also try
out your patch one one of our test machines.
Tony.
--
ocmcocmcocmk**f.a.n.finch
dot@dotat.at
fanf@demon.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 10:26:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA15712
for freebsd-current-outgoing; Mon, 2 Nov 1998 10:26:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15702
for <current@freebsd.org>; Mon, 2 Nov 1998 10:26:05 -0800 (PST)
(envelope-from jdp@austin.polstra.com)
Received: from austin.polstra.com (jdp@localhost)
by austin.polstra.com (8.9.1/8.9.1) with ESMTP id KAA07897;
Mon, 2 Nov 1998 10:25:52 -0800 (PST)
(envelope-from jdp)
Message-Id: <199811021825.KAA07897@austin.polstra.com>
To: akm@zeus.theinternet.com.au
Subject: Re: Memory Usage under -current
In-Reply-To: <199811021418.AAA25420@zeus.theinternet.com.au>
References: <199811021418.AAA25420@zeus.theinternet.com.au>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Date: Mon, 02 Nov 1998 10:25:52 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <199811021418.AAA25420@zeus.theinternet.com.au>,
Andrew Kenneth Milton <akm@zeus.theinternet.com.au> wrote:
> I'm just comparing the sizes of processes under an ELF -current
> and a 2.2.5 system, and my recollections of what my machine used to look
> like.
>
> It seems that a lot more memory is being consumed by the ELF system..
>
> I expected there to be more used by the ELF system, but, not quite
> that much...
>
> e.g.
>
> 2.2.5 - Release.
>
> PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
> 294 root 3 0 180K 88K ttyin 0:00 0.00% 0.00% getty
> 295 root 3 0 180K 88K ttyin 0:00 0.00% 0.00% getty
> 296 root 3 0 180K 88K ttyin 0:00 0.00% 0.00% getty
> 18784 akm 18 0 572K 200K pause 0:00 0.00% 0.00% zsh
>
>
> 3.0 - Current.
>
> PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
> 224 root 3 0 1004K 340K ttyin 0:00 0.00% 0.00% getty
> 223 root 3 0 1004K 340K ttyin 0:00 0.00% 0.00% getty
> 243 akm 2 0 14084K 10772K select 5:45 7.29% 7.29% XF86_S3V
> 259 akm 18 0 1228K 592K pause 0:00 0.00% 0.00% zsh
>
> Even with more used, I would expect the resident portion to be pretty
> close to the 2.2.5 a.out.
I submit that some of these numbers are bogus -- probably the ones
from 2.2.5. To do a valid comparison, you have to compare a.out and
ELF on the same system. I built an a.out getty and installed it as
"agetty". (The ELF version is "getty".) Here's what "top" showed:
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
1482 root 3 0 804K 556K ttyin 0:00 0.00% 0.00% agetty
230 root 3 0 824K 440K ttyin 0:00 0.00% 0.00% getty
232 root 3 0 824K 440K ttyin 0:00 0.00% 0.00% getty
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 10:29:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA15857
for freebsd-current-outgoing; Mon, 2 Nov 1998 10:29:00 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from circe.bonn-online.com (circe.bonn-online.com [195.52.214.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15851
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 10:28:58 -0800 (PST)
(envelope-from lederer@bonn-online.com)
Received: from bonn-online.com (ppp136.dialin.bonn-online.com [194.162.223.136])
by circe.bonn-online.com (8.8.8/8.8.7) with ESMTP id TAA11554;
Mon, 2 Nov 1998 19:27:55 +0100
Message-ID: <363DF9C6.45C26C7C@bonn-online.com>
Date: Mon, 02 Nov 1998 19:28:22 +0100
From: Sebastian Lederer <lederer@bonn-online.com>
X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386)
MIME-Version: 1.0
To: Thomas Seidmann <tseidmann@simultan.ch>
CC: Scott Michel <scottm@cs.ucla.edu>, current@FreeBSD.ORG
Subject: Re: IPv6 in -current
References: <199811012217.OAA16854@mordred.cs.ucla.edu> <363CE849.B76F70FF@simultan.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Thomas Seidmann wrote:
> Scott Michel wrote:
> >
> > There are a couple of people at UCLA CS in Lixia Zhang's lab who
> > have experience working on the INRIA IPv6 code, as well as the
> > CAIRN people who have been actively doing IPv6 and IPSEC in their
> > version of the FreeBSD kernel (http://www.cairn.net/).
> >
> > I've posted a message to our UCLA Internet Research Lab list to
> > see if anyone's interested/willing to do the integration.
>
> No matter how this discussion ends up, I'm starting to integrate INRIA
> IPv6 into current (on my local src tree, of course) starting from
> tomorrow. Whatever it will be used for :-) I am the one who started this
> thread and you'll hear from me.
>
FWIW, the last time I tried INRIA IPv6 (about four months ago), it broke
some userland IPv4 stuff. I had some NIS problems/crashes, also NFS export
control lists and /etc/lpd.hosts didn't work anymore. KAME IPv6 does not
have these problems (but INRIA's kernel code might be more stable).
Best regards,
Sebastian Lederer
--
Sebastian Lederer
lederer@bonn-online.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 2 10:51:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA17869
for freebsd-current-outgoing; Mon, 2 Nov 1998 10:51:14 -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 KAA17864
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 10:51: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 GAA10950;
Mon, 2 Nov 1998 06:53:44 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811021453.GAA10950@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, Mike Smith <mike@smith.net.au>,
Andrzej Bialecki <abial@nask.pl>, current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Mon, 02 Nov 1998 14:08:54 +0100."
<22253.910012134@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 06:53:43 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> >Given the space constraints, one has to wonder whether you have any
> >choice. :-) It would be easy enough to add some simple conditional
> >expression parsing to the existing tiny interpreter, but that wouldn't
> >be anywhere near as flexible.
>
> What exactly are the the space constraints ?
> How many [kK][bB] can we suffer ?
Well, text goes in the low moby, the bss and heap in the high moby.
Seriously, a 512kB execution context limit is reasonable; this is what
we get on the Alpha now that Doug's tweaked the memory allocation. On
the '386 we have just about everything below the 640k mark, so I figure
512 is a reasonable limit.
For on-disk usage, the key issue to me is avoiding anti-bloatist
complaint (which have their fair justification). I'd like to think we
can stabilise at an object under the 100k mark, although there are of
course no real hard limits yet.
--
\\ 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 2 11:03:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA19301
for freebsd-current-outgoing; Mon, 2 Nov 1998 11:03:35 -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 LAA19294
for <current@FreeBSD.org>; Mon, 2 Nov 1998 11:03:33 -0800 (PST)
(envelope-from gibbs@narnia.plutotech.com)
Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id LAA14593; Mon, 2 Nov 1998 11:56:31 -0700 (MST)
Date: Mon, 2 Nov 1998 11:56:31 -0700 (MST)
From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Message-Id: <199811021856.LAA14593@narnia.plutotech.com>
To: "John W. DeBoskey" <jwd@unx.sas.com>
cc: current@FreeBSD.ORG
Subject: Re: scsi disk (cam?) problems (inodes & swap?)
X-Newsgroups: pluto.freebsd.current
In-Reply-To: <199811020321.WAA16023@bb01f39.unx.sas.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 <199811020321.WAA16023@bb01f39.unx.sas.com> you wrote:
> Hi,
>
> A 2nd reply to this same msg:
>
> Softupdates: No SMP: No
>
> Anyways, just for grins, I 'umount'ed the 3 file systems I have
> on the ccd (they went down cleanly). Then I fsck'd them. The 1st
> two went fine. The 3rd gave:
...
Are you positive that this corruption is not from a previous
failure? I've seen fsck mark systems clean that really weren't.
I'm hopeful that the new version of fsck that Kirk has put out
addresses these issues.
--
Justin
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 11:51:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA24423
for freebsd-current-outgoing; Mon, 2 Nov 1998 11:51:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24418
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 11:51:42 -0800 (PST)
(envelope-from mjacob@feral.com)
Received: from localhost (mjacob@localhost)
by feral.com (8.8.6/8.8.6) with SMTP id LAA12160;
Mon, 2 Nov 1998 11:51:00 -0800
Date: Mon, 2 Nov 1998 11:51:00 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
X-Sender: mjacob@feral-gw
Reply-To: mjacob@feral.com
To: Johan Granlund <johan@granlund.nu>
cc: "Kenneth D. Merry" <ken@plutotech.com>, freebsd-current@FreeBSD.ORG
Subject: Re: Exabyte EXB-8200 and CAM, Take3
In-Reply-To: <199810250938.KAA23114@phoenix.granlund.nu>
Message-ID: <Pine.LNX.4.02.9811021149100.11600-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 finally working on this .. .sorry about the delay...
There are definitely a couple of things broken for 8200 support
(I haven't tracked down the residual error, but I *have* fixed
but not integrated the bug where you can't set variable blocksize
mode (0x7f does not apply to device that are earlier to SCSI-2))
More later, I'll take this to freebsd-scsi for followups...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 11:56:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA25035
for freebsd-current-outgoing; Mon, 2 Nov 1998 11:56:55 -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 LAA25028
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 11:56:52 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id UAA25009;
Mon, 2 Nov 1998 20:54:24 +0100 (CET)
To: Mike Smith <mike@smith.net.au>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, Andrzej Bialecki <abial@nask.pl>,
current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Mon, 02 Nov 1998 06:53:43 PST."
<199811021453.GAA10950@dingo.cdrom.com>
Date: Mon, 02 Nov 1998 20:54:24 +0100
Message-ID: <25007.910036464@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>For on-disk usage, the key issue to me is avoiding anti-bloatist
>complaint (which have their fair justification). I'd like to think we
>can stabilise at an object under the 100k mark, although there are of
>course no real hard limits yet.
Sigh, If Satoshi hadn't yanked tcl out, we could have used that...
--
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 2 12:00:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA25562
for freebsd-current-outgoing; Mon, 2 Nov 1998 12:00:24 -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 MAA25554
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 12:00:22 -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 LAA00963
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 11:59:57 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811021959.LAA00963@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Mon, 02 Nov 1998 20:54:24 +0100."
<25007.910036464@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 11:59:57 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> >For on-disk usage, the key issue to me is avoiding anti-bloatist
> >complaint (which have their fair justification). I'd like to think we
> >can stabilise at an object under the 100k mark, although there are of
> >course no real hard limits yet.
>
> Sigh, If Satoshi hadn't yanked tcl out, we could have used that...
Nah; it was waaaay too big last time I looked, and again, no bytecode.
--
\\ 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 2 12:20:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA28487
for freebsd-current-outgoing; Mon, 2 Nov 1998 12:20:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28480
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 12:20:55 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA01119;
Mon, 2 Nov 1998 12:18:29 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811022018.MAA01119@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: John Hay <jhay@mikom.csir.co.za>
cc: green@zone.syracuse.net (Brian Feldman), freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-reply-to: Your message of "Sat, 02 Nov 1998 19:26:31 +0200."
<199811021726.TAA03714@zibbi.mikom.csir.co.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 12:18:29 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Be sure to let me know when ELF kernels can autoload kld modules like the
> > current a.out kernel does with lkm's.
>
> It's not the kernel that loads them. Go and look in lib/libc/gen/getvfsent.c
No, but it should.
--
\\ 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 2 12:21:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA28634
for freebsd-current-outgoing; Mon, 2 Nov 1998 12:21:14 -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 MAA28612
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 12:21:11 -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 VAA23550;
Mon, 2 Nov 1998 21:19:13 +0100 (CET)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Mon, 2 Nov 1998 21:19:12 +0100 (CET)
From: Andrzej Bialecki <abial@nask.pl>
X-Sender: abial@korin.warman.org.pl
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: Mike Smith <mike@smith.net.au>, "Jordan K. Hubbard" <jkh@time.cdrom.com>,
current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-Reply-To: <25007.910036464@critter.freebsd.dk>
Message-ID: <Pine.BSF.4.02A.9811022115450.2746-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 Mon, 2 Nov 1998, Poul-Henning Kamp wrote:
>
> >For on-disk usage, the key issue to me is avoiding anti-bloatist
> >complaint (which have their fair justification). I'd like to think we
> >can stabilise at an object under the 100k mark, although there are of
> >course no real hard limits yet.
>
> Sigh, If Satoshi hadn't yanked tcl out, we could have used that...
You must mean tcl4 or even earlier, then... Newer versions of tcl are
somewhere around 300kB. Besides, you talk about 100k mark as of tcl object
limit, whereas Mike was talking probably about the whole bootloader
size, right?
Andrzej Bialecki
-------------------- ++-------++ -------------------------------------
<abial@nask.pl> ||PicoBSD|| FreeBSD in your pocket? Go and see:
Research & Academic |+-------+| "Small & Embedded FreeBSD"
Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/
-------------------- ~-+==---+-+ -------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 12:21:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA28690
for freebsd-current-outgoing; Mon, 2 Nov 1998 12:21:48 -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 MAA28685
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 12:21:47 -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 MAA01166;
Mon, 2 Nov 1998 12:20:45 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811022020.MAA01166@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-reply-to: Your message of "Mon, 02 Nov 1998 20:41:16 +1000."
<199811021041.UAA23800@zeus.theinternet.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 12:20:45 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> | Reboot, and at the boot: prompt type '/boot/loader', then abort the
> | kernel load and type 'boot kernel.elf'.
>
> I did some mucking around today.
>
> I got to the point of putting /boot/loader into boot.config
> and then got very confused... as it didn't want to load
> ',kernel.old'
>
> I've got it booted now in time to read this email...
I goofed updating the syntax for the kernel search path; that's fixed
now.
--
\\ 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 2 12:27:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA29294
for freebsd-current-outgoing; Mon, 2 Nov 1998 12:27:10 -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 MAA29287
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 12:27:05 -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 VAA25314;
Mon, 2 Nov 1998 21:24:43 +0100 (CET)
To: Andrzej Bialecki <abial@nask.pl>
cc: Mike Smith <mike@smith.net.au>, "Jordan K. Hubbard" <jkh@time.cdrom.com>,
current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Mon, 02 Nov 1998 21:19:12 +0100."
<Pine.BSF.4.02A.9811022115450.2746-100000@korin.warman.org.pl>
Date: Mon, 02 Nov 1998 21:24:43 +0100
Message-ID: <25312.910038283@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 <Pine.BSF.4.02A.9811022115450.2746-100000@korin.warman.org.pl>, Andr
zej Bialecki writes:
>On Mon, 2 Nov 1998, Poul-Henning Kamp wrote:
>
>>
>> >For on-disk usage, the key issue to me is avoiding anti-bloatist
>> >complaint (which have their fair justification). I'd like to think we
>> >can stabilise at an object under the 100k mark, although there are of
>> >course no real hard limits yet.
>>
>> Sigh, If Satoshi hadn't yanked tcl out, we could have used that...
>
>You must mean tcl4 or even earlier, then... Newer versions of tcl are
>somewhere around 300kB. Besides, you talk about 100k mark as of tcl object
>limit, whereas Mike was talking probably about the whole bootloader
>size, right?
If you par down tcl to "just the language" it is about 80k still I
think.
--
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 2 12: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 MAA01263
for freebsd-current-outgoing; Mon, 2 Nov 1998 12:37:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01250
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 12:37:28 -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 MAA01244;
Mon, 2 Nov 1998 12:30:05 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811022030.MAA01244@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: Andrzej Bialecki <abial@nask.pl>, Mike Smith <mike@smith.net.au>,
"Jordan K. Hubbard" <jkh@time.cdrom.com>, current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Mon, 02 Nov 1998 21:24:43 +0100."
<25312.910038283@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 12:30:05 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> >>
> >> Sigh, If Satoshi hadn't yanked tcl out, we could have used that...
> >
> >You must mean tcl4 or even earlier, then... Newer versions of tcl are
> >somewhere around 300kB. Besides, you talk about 100k mark as of tcl object
> >limit, whereas Mike was talking probably about the whole bootloader
> >size, right?
>
> If you par down tcl to "just the language" it is about 80k still I
> think.
That doesn't get you the bytecoder though. One of Forth's undeniable
advantages is that its internal bytecoded representation is pretty damn
compact.
--
\\ 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 2 12:38:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA01440
for freebsd-current-outgoing; Mon, 2 Nov 1998 12:38:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns1.yes.no (ns1.yes.no [195.204.136.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01432
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 12:38:44 -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 VAA16440;
Mon, 2 Nov 1998 21:38:28 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id VAA04509;
Mon, 2 Nov 1998 21:38:28 +0100 (MET)
Message-ID: <19981102213827.00944@follo.net>
Date: Mon, 2 Nov 1998 21:38:27 +0100
From: Eivind Eklund <eivind@yes.no>
To: John Polstra <jdp@polstra.com>, Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Cc: current@FreeBSD.ORG
Subject: Re: Another compile error
References: <XFMail.981102183314.asmodai@wxs.nl> <199811021740.JAA07718@austin.polstra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <199811021740.JAA07718@austin.polstra.com>; from John Polstra on Mon, Nov 02, 1998 at 09:40:28AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Nov 02, 1998 at 09:40:28AM -0800, John Polstra wrote:
> > Right now I cvsup into slice /src (wrong name, I know ;) and make
> > world from /src/src, but obviously /usr/src doesn't get updated that
> > way.
>
> I recommend that you CVSup your sources to "/usr/src". That's the
> standard place for the system sources.
I disagree. I think it would be very good if more people had their
sources in non-standard location, as it make it more likely that
somebody introducing a new location dependency get caught. Bruce did
a lot of work to eliminate all the dependencies on the location.
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 2 12:43:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA02013
for freebsd-current-outgoing; Mon, 2 Nov 1998 12:43:11 -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 MAA01991
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 12:43:00 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from diabolique.ninth-circle.org ([195.121.58.142])
by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA6606; Mon, 2 Nov 1998 21:42:27 +0100
Message-ID: <XFMail.981102214619.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: <19981102213827.00944@follo.net>
Date: Mon, 02 Nov 1998 21:46:19 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Eivind Eklund <eivind@yes.no>
Subject: Re: Another compile error
Cc: current@FreeBSD.ORG, John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 02-Nov-98 Eivind Eklund wrote:
> On Mon, Nov 02, 1998 at 09:40:28AM -0800, John Polstra wrote:
>> > Right now I cvsup into slice /src (wrong name, I know ;) and make
>> > world from /src/src, but obviously /usr/src doesn't get updated that
>> > way.
>>
>> I recommend that you CVSup your sources to "/usr/src". That's the
>> standard place for the system sources.
>
> I disagree. I think it would be very good if more people had their
> sources in non-standard location, as it make it more likely that
> somebody introducing a new location dependency get caught. Bruce did
> a lot of work to eliminate all the dependencies on the location.
Heh, so now I am back at square #1. =)
If I have a seperate slice, let's say /cvs which I would like to use for
cvsup that all goes well. Now when I do a make world in /cvs/src does it
update the /usr/src as well? Or does this require additional fiddling? That
is what keeps evading my mind...
Thanks,
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Mon Nov 2 12: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 MAA02055
for freebsd-current-outgoing; Mon, 2 Nov 1998 12:43:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02032
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 12:43:14 -0800 (PST)
(envelope-from jdp@austin.polstra.com)
Received: from austin.polstra.com (jdp@localhost)
by austin.polstra.com (8.9.1/8.9.1) with ESMTP id MAA08533;
Mon, 2 Nov 1998 12:41:57 -0800 (PST)
(envelope-from jdp)
Message-Id: <199811022041.MAA08533@austin.polstra.com>
To: Eivind Eklund <eivind@yes.no>
cc: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>, current@FreeBSD.ORG
Subject: Re: Another compile error
In-reply-to: Your message of "Mon, 02 Nov 1998 21:38:27 +0100."
<19981102213827.00944@follo.net>
Date: Mon, 02 Nov 1998 12:41:57 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I disagree. I think it would be very good if more people had their
> sources in non-standard location, as it make it more likely that
> somebody introducing a new location dependency get caught. Bruce
> did a lot of work to eliminate all the dependencies on the location.
That's fine advice for experienced FreeBSD developers. This poor
fellow has already been through the mill just trying to get a make
world to complete. The last thing we want for him is one more
potential source of problems.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 12:43:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA02073
for freebsd-current-outgoing; Mon, 2 Nov 1998 12:43:26 -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 MAA02024;
Mon, 2 Nov 1998 12:43:13 -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 VAA16530;
Mon, 2 Nov 1998 21:42:56 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id VAA04549;
Mon, 2 Nov 1998 21:42:56 +0100 (MET)
Message-ID: <19981102214256.36935@follo.net>
Date: Mon, 2 Nov 1998 21:42:56 +0100
From: Eivind Eklund <eivind@yes.no>
To: gmarco@giovannelli.it, current@FreeBSD.ORG
Cc: multimedia@FreeBSD.ORG
Subject: Re: bt848 broken ?
References: <199811021744.SAA00799@www.giovannelli.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <199811021744.SAA00799@www.giovannelli.it>; from Gianmarco Giovannelli on Mon, Nov 02, 1998 at 06:57:27PM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Nov 02, 1998 at 06:57:27PM +0100, Gianmarco Giovannelli wrote:
> It's a couple of days that I receive this error when I try to compile the kernel
> (cvsupped twice a day, last five minutes ago 981102 18:45 CET)
>
> .c ../../libkern/strcat.c ../../libkern/strcmp.c ../../libkern/strcpy.c
> ../../libkern/strlen.c ../../libkern/strncmp.c ../../libkern/strncpy.c
> ../../libkern/udivdi3.c ../../libkern/umoddi3.c swapkernel.c ioconf.c param.c
> vnode_if.c config.c
> ../../pci/brooktree848.c:361: smbus_if.h: No such file or directory
> ../../pci/brooktree848.c:362: iicbus_if.h: No such file or directory
> ../../pci/bt848_i2c.c:61: iicbb_if.h: No such file or directory
> ../../pci/bt848_i2c.c:62: smbus_if.h: No such file or directory
> mkdep: compile failed
> *** Error code 1
>
> Stop.
>
> Have I missed something ?
You have to re-configure your kernel before attempting to recompile
it. If you do, and you're up to date, I think it should work...
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 2 12:46:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA02431
for freebsd-current-outgoing; Mon, 2 Nov 1998 12:46: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 MAA02412
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 12:45:56 -0800 (PST)
(envelope-from enkhyl@scient.com)
Received: from mg137-090.ricochet.net (mg137-090.ricochet.net [204.179.137.90])
by rgate2.ricochet.net (8.8.8/8.8.8) with ESMTP id OAA18980;
Mon, 2 Nov 1998 14:44:42 -0600 (CST)
Date: Mon, 2 Nov 1998 12:43:55 -0800 (PST)
From: Christopher Nielsen <enkhyl@scient.com>
X-Sender: enkhyl@ender.sf.scient.com
Reply-To: enkhyl@hayseed.net
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: Chuck Robey <chuckr@mat.net>, John Hay <jhay@mikom.csir.co.za>,
current@FreeBSD.ORG
Subject: Re: IPv6 in -current
In-Reply-To: <199811011929.OAA05742@khavrinen.lcs.mit.edu>
Message-ID: <Pine.BSF.4.05.9811021240570.318-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, 1 Nov 1998, Garrett Wollman wrote:
> I frankly don't care that much which IPv6 implementation is chosen.
> My concerns are the following:
>
> 2) that we don't screw any of the existing developers
>
> 1) that we make whatever necessary fundamental advances we can in the
> network stack before taking on additional deadweight
If both IPv6 contenders have commit privs, why can't these things be done
in parallel, as long as proper regression testing is done?
(if I'm being outright stupid, please whack me over the head with a big
stick)
--
Christopher Nielsen
Scient: The Art and Science of Electronic Business
<http://www.scient.com>
cnielsen@scient.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 12:56:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA03320
for freebsd-current-outgoing; Mon, 2 Nov 1998 12:56:43 -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 MAA03312
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 12:56: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 VAA16671;
Mon, 2 Nov 1998 21:56:33 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id VAA04649;
Mon, 2 Nov 1998 21:56:32 +0100 (MET)
Message-ID: <19981102215631.17752@follo.net>
Date: Mon, 2 Nov 1998 21:56:31 +0100
From: Eivind Eklund <eivind@yes.no>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Cc: current@FreeBSD.ORG, John Polstra <jdp@polstra.com>
Subject: Re: Another compile error
References: <19981102213827.00944@follo.net> <XFMail.981102214619.asmodai@wxs.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <XFMail.981102214619.asmodai@wxs.nl>; from Jeroen Ruigrok/Asmodai on Mon, Nov 02, 1998 at 09:46:19PM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Nov 02, 1998 at 09:46:19PM +0100, Jeroen Ruigrok/Asmodai wrote:
> On 02-Nov-98 Eivind Eklund wrote:
> > On Mon, Nov 02, 1998 at 09:40:28AM -0800, John Polstra wrote:
> >> I recommend that you CVSup your sources to "/usr/src". That's the
> >> standard place for the system sources.
> >
> > I disagree. I think it would be very good if more people had their
> > sources in non-standard location, as it make it more likely that
> > somebody introducing a new location dependency get caught. Bruce did
> > a lot of work to eliminate all the dependencies on the location.
>
> Heh, so now I am back at square #1. =)
>
> If I have a seperate slice, let's say /cvs which I would like to use for
> cvsup that all goes well. Now when I do a make world in /cvs/src does it
> update the /usr/src as well? Or does this require additional fiddling? That
> is what keeps evading my mind...
I pull my advice. Run it in /usr/src for the time being.
'make world' updates the binaries; cvsup just updates the sources in
the place you specify. So no, 'make world' will not update /usr/src.
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 2 13:25:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA07785
for freebsd-current-outgoing; Mon, 2 Nov 1998 13:25:54 -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 NAA07760
for <current@freebsd.org>; Mon, 2 Nov 1998 13:25:48 -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 QAA16701
for <current@freebsd.org>; Mon, 2 Nov 1998 16:28:39 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Mon, 2 Nov 1998 16:28:39 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: current@FreeBSD.ORG
Subject: wondering about DEVFS & MFS?
Message-ID: <Pine.BSF.4.05.9811021627050.14876-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
mfs is working fine for me as my /tmp, i used to be a big fan of DEVFS,
how is it coming along? usable again? any caveats?
i know LINT says DEVFS+MFS is a no-no, is this still true?
thanks,
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 2 13:49:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA11028
for freebsd-current-outgoing; Mon, 2 Nov 1998 13:49:27 -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 NAA11017
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 13:49:21 -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 QAA01997
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 16:48:38 -0500 (EST)
Date: Mon, 2 Nov 1998 16:48:37 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: freebsd-current@FreeBSD.ORG
Subject: modules
Message-ID: <Pine.BSF.4.05.9811021647080.304-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
Why aren't elf kernel modules installed into /modules in a 'make
installworld' ? The old lkms STILL are, and installing the modules
isn't going to hurt folks who are still running aout kernels.
----------------------------+-----------------------------------------------
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 2 13:53:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA12021
for freebsd-current-outgoing; Mon, 2 Nov 1998 13:53:59 -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 NAA12016
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 13:53:57 -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 NAA01663;
Mon, 2 Nov 1998 13:52:46 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811022152.NAA01663@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Chuck Robey <chuckr@mat.net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: modules
In-reply-to: Your message of "Mon, 02 Nov 1998 16:48:37 EST."
<Pine.BSF.4.05.9811021647080.304-100000@picnic.mat.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 13:52:46 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Why aren't elf kernel modules installed into /modules in a 'make
> installworld' ? The old lkms STILL are, and installing the modules
> isn't going to hurt folks who are still running aout kernels.
Nobody has gotten around to it yet. Feel free to connect /sys/modules
and make sure that /modules is created correctly.
--
\\ 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 2 14:05:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA13711
for freebsd-current-outgoing; Mon, 2 Nov 1998 14:05:32 -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 OAA13699
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 14:05:27 -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 IAA11470;
Tue, 3 Nov 1998 08:34:36 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.1/8.9.0) id IAA12779;
Tue, 3 Nov 1998 08:34:11 +1030 (CST)
Message-ID: <19981103083410.S354@freebie.lemis.com>
Date: Tue, 3 Nov 1998 08:34:10 +1030
From: Greg Lehey <grog@lemis.com>
To: Harold Gutch <logix@foobar.franken.de>, freebsd-current@FreeBSD.ORG
Subject: Re: ELF-kgdb on a.out-kernel
References: <19981102020346.A19337@foobar.franken.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <19981102020346.A19337@foobar.franken.de>; from Harold Gutch on Mon, Nov 02, 1998 at 02:03:46AM +0100
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Monday, 2 November 1998 at 2:03:46 +0100, Harold Gutch wrote:
> Hi,
>
> how do i use an ELF-gdb on an a.out-kernel ? Setting OBJFORMAT to
> "aout" doesn't help and gdb doesn't recognize the
> commandline-switch "-aout" (as other tools like nm do).
You don't. In fact, gdb should recognize the object format and adapt
automatically, but it currently doesn't. You need to build an a.out
version of gdb. You can pick on up at
ftp://ftp.lemis.com/pub/vinum/gdb-aout.
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 2 14:38:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA19052
for freebsd-current-outgoing; Mon, 2 Nov 1998 14:36:05 -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 OAA18969
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 14:36:01 -0800 (PST)
(envelope-from peter.jeremy@auss2.alcatel.com.au)
Received: by border.alcanet.com.au id <40322>; Tue, 3 Nov 1998 09:35:15 +1100
Date: Tue, 3 Nov 1998 09:35:43 +1100
From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Subject: Re: New boot loader and alternate kernels
To: current@FreeBSD.ORG
Message-Id: <98Nov3.093515est.40322@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
To join in the general discussion: I support the idea of FORTH in the
bootloader. It's small, reasonably fast and extensible. I like the
idea of a bootloader that fits into the bootblocks - which puts a
hard upper limit on the size.
As a general comment, once you start cutting down a standard, well-
known language, it gets harder to work with. You have to remember
which features no longer work (or, worse, behave differently). I
would not like to see a mini-sh, mini-tcl, mini-perl or tiny-C as
a bootloader language.
Whilst shell is well known, it is much larger - and relies on external
code (which assumes the kernel is running) for most commands. The
more commands you build into the shell, the bigger it gets. It's not
readily extensible, so it's difficult to hide the underlying language.
Similarly, tcl is large and non-extensible.
On a slightly related issue, some time ago, Greg Lemis and I were
discussing the possibility of replacing DDB with something that
included a command language. This is another area where bloat is
undesirable and I suggested FORTH. There would be obvious benefits
in having a common extension language used by the bootloader and
kernel debugger.
FORTH does have a decent pedigree as a bootloader - Sun have been
using it for at least 6 years. Most user interaction is covered
by "boot FILE FLAGS", "reset" and "sync" - you don't have to be
a FORTH guru to use it.
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 Mon Nov 2 14:58:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA21820
for freebsd-current-outgoing; Mon, 2 Nov 1998 14:58:49 -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 OAA21815
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 14:58:48 -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 OAA02025;
Mon, 2 Nov 1998 14:58:19 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811022258.OAA02025@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
cc: current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Tue, 03 Nov 1998 09:35:43 +1100."
<98Nov3.093515est.40322@border.alcanet.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 14:58:19 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> To join in the general discussion: I support the idea of FORTH in the
> bootloader. It's small, reasonably fast and extensible. I like the
> idea of a bootloader that fits into the bootblocks - which puts a
> hard upper limit on the size.
It will never fit in the "bootblocks". It's all we can do to locate a
file in the filesystem and read it in. Before being too dim about
this, bear in mind that no other operating system bootstrap manages to
achieve this much with so little.
> As a general comment, once you start cutting down a standard, well-
> known language, it gets harder to work with. You have to remember
> which features no longer work (or, worse, behave differently). I
> would not like to see a mini-sh, mini-tcl, mini-perl or tiny-C as
> a bootloader language.
Good points, and why we haven't made any effort to expand the current
interpreter lately.
> Whilst shell is well known, it is much larger - and relies on external
> code (which assumes the kernel is running) for most commands. The
> more commands you build into the shell, the bigger it gets. It's not
> readily extensible, so it's difficult to hide the underlying language.
> Similarly, tcl is large and non-extensible.
Tcl is quite extensible (very extensible actually), but much too large.
> On a slightly related issue, some time ago, Greg Lemis and I were
> discussing the possibility of replacing DDB with something that
> included a command language. This is another area where bloat is
> undesirable and I suggested FORTH. There would be obvious benefits
> in having a common extension language used by the bootloader and
> kernel debugger.
There would be little trouble including the FICL Forth engine in the
kernel; I had actually considered the not insubstantial advantages to
doing this (most importantly the ability to attach Forth to modules to
do specialised load/unload operations), but I suspect that this will be
viewed too much like heresy by many people.
> FORTH does have a decent pedigree as a bootloader - Sun have been
> using it for at least 6 years. Most user interaction is covered
> by "boot FILE FLAGS", "reset" and "sync" - you don't have to be
> a FORTH guru to use it.
That's my hope. We also have enough manifest Forth talent to get us
bootstrapped to that stage, so I don't view it as technically
impossible. The philosophical issues are still bugging me.
--
\\ 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 2 15:01:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA22034
for freebsd-current-outgoing; Mon, 2 Nov 1998 15:01:51 -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 PAA22029
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 15:01:50 -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 PAA27131;
Mon, 2 Nov 1998 15:01:43 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Mike Smith <mike@smith.net.au>
cc: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>, current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Mon, 02 Nov 1998 14:58:19 PST."
<199811022258.OAA02025@dingo.cdrom.com>
Date: Mon, 02 Nov 1998 15:01:42 -0800
Message-ID: <27127.910047702@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> That's my hope. We also have enough manifest Forth talent to get us
> bootstrapped to that stage, so I don't view it as technically
> impossible. The philosophical issues are still bugging me.
Damn the philosophy, just provide the functionality and let anyone
with a competing philosophy come up with some better alternative if
they don't like it. :-)
- 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 2 15:05:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA22589
for freebsd-current-outgoing; Mon, 2 Nov 1998 15:05: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 PAA22582
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 15:05:25 -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 SAA02212;
Mon, 2 Nov 1998 18:04:29 -0500 (EST)
Date: Mon, 2 Nov 1998 18:04:29 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Mike Smith <mike@smith.net.au>
cc: current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-Reply-To: <199811021959.LAA00963@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811021800280.304-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, 2 Nov 1998, Mike Smith wrote:
> >
> > >For on-disk usage, the key issue to me is avoiding anti-bloatist
> > >complaint (which have their fair justification). I'd like to think we
> > >can stabilise at an object under the 100k mark, although there are of
> > >course no real hard limits yet.
> >
> > Sigh, If Satoshi hadn't yanked tcl out, we could have used that...
>
> Nah; it was waaaay too big last time I looked, and again, no bytecode.
Geeze, guys, we're talking about something that works in the boot
process, before anything else gets going. It's got to run by itself,
because there's no shared libs at that point; it's got to be small, and
self contained.
It's much more a choice of nothing at all, or something like Forth.
Things like tcl, or any kind of *sh, don't even offer themselves as
options. This stuff has to be viewed kinda like embedded software, like
what goes into hand calculators, not system software.
When you're offered a choice of nothing at all, or Forth, suddenly Forth
begins looking pretty good. Of course, that's often why Forth gets
used.
>
> --
> \\ 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 Mon Nov 2 15:06:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA22758
for freebsd-current-outgoing; Mon, 2 Nov 1998 15:06:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22752
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 15:06:31 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA02107;
Mon, 2 Nov 1998 15:05:35 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811022305.PAA02107@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Mon, 02 Nov 1998 15:01:42 PST."
<27127.910047702@time.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 15:05:35 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > That's my hope. We also have enough manifest Forth talent to get us
> > bootstrapped to that stage, so I don't view it as technically
> > impossible. The philosophical issues are still bugging me.
>
> Damn the philosophy, just provide the functionality and let anyone
> with a competing philosophy come up with some better alternative if
> they don't like it. :-)
Ok. It's at home, so I'll commit the framework tonight. I'm still
experimenting with integration and things like "who controls getting
input?", so it'll be playfodder for a while.
Meanwhile I've just implemented a tiny block cache, and the improvement
on disk performance (especially floppy) is very desirable.
--
\\ 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 2 15:10:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA23376
for freebsd-current-outgoing; Mon, 2 Nov 1998 15:10:38 -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 PAA23368
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 15:10:36 -0800 (PST)
(envelope-from peter.jeremy@auss2.alcatel.com.au)
Received: by border.alcanet.com.au id <40322>; Tue, 3 Nov 1998 10:09:55 +1100
Date: Tue, 3 Nov 1998 10:10:22 +1100
From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Subject: Apology to Greg Lehey
To: grog@lemis.com
Cc: current@FreeBSD.ORG
Message-Id: <98Nov3.100955est.40322@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I recently wrote:
>On a slightly related issue, some time ago, Greg Lemis and I were...
Ooops. I'd like to apologize to Greg Lehey <grog@lemis.com> for
confusing his surname with his domain name :-(. I do realise they're
not interchangeable.
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 2 15:25:58 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA24635
for freebsd-current-outgoing; Mon, 2 Nov 1998 15:25:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mcfs.whowhere.com (mcfs.whowhere.com [209.1.236.44])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA24627
for <current@freebsd.org>; Mon, 2 Nov 1998 15:25:57 -0800 (PST)
(envelope-from erkaf@my-dejanews.com)
Received: from Unknown/Local ([?.?.?.?]) by my-dejanews.com; Mon Nov 2 15:25:44 1998
To: current@FreeBSD.ORG
Date: Mon, 02 Nov 1998 15:25:44 -0700
From: "Kelvin Farmer" <erkaf@my-dejanews.com>
Message-ID: <JLDKNEAIOFIOHAAA@my-dejanews.com>
Mime-Version: 1.0
X-Sent-Mail: off
X-Mailer: MailCity Service
Subject: make kernel fails:booktree848.c
X-Sender-Ip: 192.75.12.156
Organization: Deja News Mail (http://www.my-dejanews.com:80)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I just updated my src tree (cvsup) but now I can't make a kernel, since i get the following error:
../../pci/brooktree848.c:361: smbus_if.h: No such file or directory
../../pci/brooktree848.c:362: iicbus_if.h: No such file or directory
../../pci/bt848_i2c.c:61: iicbb_if.h: No such file or directory
../../pci/bt848_i2c.c:62: smbus_if.h: No such file or directory
the kernel makes okay if i remove device bktr0.
Thanks
Kelvin.
-----== Sent via Deja News, The Discussion Network ==-----
http://www.dejanews.com/ Easy access to 50,000+ discussion forums
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 16:27:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA05818
for freebsd-current-outgoing; Mon, 2 Nov 1998 16:27:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from garman.dyn.ml.org (pm106-19.dialip.mich.net [192.195.231.221])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA05770
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 16:27:12 -0800 (PST)
(envelope-from garman@garman.dyn.ml.org)
Message-Id: <199811030027.QAA05770@hub.freebsd.org>
Received: (qmail 24964 invoked from smtpd); 3 Nov 1998 00:28:02 -0000
Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1)
by localhost.garman.net with SMTP; 3 Nov 1998 00:28:02 -0000
Date: Mon, 2 Nov 1998 19:28:01 -0500 (EST)
From: garman@earthling.net
Reply-To: garman@earthling.net
Subject: Re: bt848 broken ?
To: gmarco@giovannelli.it
cc: current@FreeBSD.ORG, multimedia@FreeBSD.ORG
In-Reply-To: <199811021744.SAA00799@www.giovannelli.it>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 2 Nov, Gianmarco Giovannelli wrote:
> It's a couple of days that I receive this error when I try to compile the kernel
> (cvsupped twice a day, last five minutes ago 981102 18:45 CET)
>
> .c ../../libkern/strcat.c ../../libkern/strcmp.c ../../libkern/strcpy.c
> ../../libkern/strlen.c ../../libkern/strncmp.c ../../libkern/strncpy.c
> ../../libkern/udivdi3.c ../../libkern/umoddi3.c swapkernel.c ioconf.c param.c
> vnode_if.c config.c
> ../../pci/brooktree848.c:361: smbus_if.h: No such file or directory
> ../../pci/brooktree848.c:362: iicbus_if.h: No such file or directory
> ../../pci/bt848_i2c.c:61: iicbb_if.h: No such file or directory
> ../../pci/bt848_i2c.c:62: smbus_if.h: No such file or directory
> mkdep: compile failed
> *** Error code 1
>
you need to add the smbus0 and iicbus0 devices, like so:
controller smbus0
device smb0 at smbus?
controller iicbus0
device ic0 at iicbus?
device iic0 at iicbus?
device iicsmb0 at iicbus?
device iicbb0 at iicbus?
i don't know if you need all of the devices, but they converted the
bktr driver to use thew common iicbus code.
enjoy
--
Jason Garman http://garman.dyn.ml.org/
Student, University of Maryland garman@earthling.net
And now... for the stupid-patent-of-the-week: Whois: JAG145
"...an attache case with destruct means for destroying the contents
therein in response to a signal" -- patent no. US3643609, filed in 1969
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 16:27:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA05820
for freebsd-current-outgoing; Mon, 2 Nov 1998 16:27:20 -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 QAA05786
for <freebsd-current@freebsd.org>; Mon, 2 Nov 1998 16:27:15 -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 QAA06179
for <freebsd-current@freebsd.org>; Mon, 2 Nov 1998 16:27:08 -0800 (PST)
(envelope-from scottm@mordred.cs.ucla.edu)
Message-Id: <199811030027.QAA06179@mordred.cs.ucla.edu>
X-Mailer: exmh version 2.0.2 2/24/98
To: freebsd-current@FreeBSD.ORG
Subject: Persistent buildworld error
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 16:27:07 -0800
From: Scott Michel <scottm@cs.ucla.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
===> sys/boot/i386/libi386
make: don't know how to make machine/ansi.h. Stop
*** Error code 2
Been through a few cvsups over the last week, and buildworld
bombs here consistently. I have a feeling I can do an installworld
but before the less courageous freak out, here's a head's up.
My buildworld is ELF.
-scooter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 16:36:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA07141
for freebsd-current-outgoing; Mon, 2 Nov 1998 16:36:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07135
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 16:36:48 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA19230;
Mon, 2 Nov 1998 19:36:27 -0500 (EST)
Date: Mon, 2 Nov 1998 19:36:27 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: John Hay <jhay@mikom.csir.co.za>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-Reply-To: <199811021726.TAA03714@zibbi.mikom.csir.co.za>
Message-ID: <Pine.BSF.4.05.9811021935420.19187-100000@zone.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
Ahhhh, that's where it is! I have no good idea on how to allow, with this
code, lkm's and kld's to coexist.... so is it time to completely phase out
lkm's yet?
Brian Feldman
On Mon, 2 Nov 1998, John Hay wrote:
> > Be sure to let me know when ELF kernels can autoload kld modules like the
> > current a.out kernel does with lkm's.
>
> It's not the kernel that loads them. Go and look in lib/libc/gen/getvfsent.c
>
> John
> --
> John Hay -- John.Hay@mikom.csir.co.za
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 16:43:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA07945
for freebsd-current-outgoing; Mon, 2 Nov 1998 16:43:38 -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 QAA07940
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 16:43:35 -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 TAA02464;
Mon, 2 Nov 1998 19:42:42 -0500 (EST)
Date: Mon, 2 Nov 1998 19:42:42 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Scott Michel <scottm@cs.ucla.edu>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Persistent buildworld error
In-Reply-To: <199811030027.QAA06179@mordred.cs.ucla.edu>
Message-ID: <Pine.BSF.4.05.9811021940390.304-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, 2 Nov 1998, Scott Michel wrote:
> ===> sys/boot/i386/libi386
> make: don't know how to make machine/ansi.h. Stop
> *** Error code 2
>
> Been through a few cvsups over the last week, and buildworld
> bombs here consistently. I have a feeling I can do an installworld
> but before the less courageous freak out, here's a head's up.
>
> My buildworld is ELF.
Did one Sunday, ran fine. ELF, and ELF kernel. You must have some
kinda source corruption, Scott, or your cvsup timing *really* sucks (you
could have just come in halfway during commits).
>
>
> -scooter
>
>
> 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 Mon Nov 2 16:44:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA08063
for freebsd-current-outgoing; Mon, 2 Nov 1998 16:44:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08054
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 16:44:23 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA19332;
Mon, 2 Nov 1998 19:44:08 -0500 (EST)
Date: Mon, 2 Nov 1998 19:44:08 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: Tony Finch <dot@dotat.at>
cc: current@FreeBSD.ORG
Subject: Re: Linux clone()
In-Reply-To: <E0zaOmm-0004U0-00@fanf.noc.demon.net>
Message-ID: <Pine.BSF.4.05.9811021941340.19187-100000@zone.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
Hmmm.. okay this would be a good test. Right now I'm going thru the
various linuxthreads example programs.... The patch seems to be doing
something wrong, and I'm unable to figure out what to do, due to Linux's
humongously gross syscall system (so the kernel doesn't help me). It also
seems now I was implementing a LIBRARY function, which is just a wrapper.
If I could get my hands on what the real system calls' args are it would
be great.
Brian Feldman
On Mon, 2 Nov 1998, Tony Finch wrote:
> Brian Feldman <green@zone.syracuse.net> wrote:
> >
> >Okay, guys, I think I've gotten a linux clone() syscall
> >implemented... As of now, I have nothing to test it with :( [...]
> >This is a pretty important thing to have, when lots more apps use
> >linuxthreads (i.e. StarOffice 5.0).
>
> A good example of this is Squid compiled up to use async IO. I can put
> a tar file or something together for you if you like. I'll also try
> out your patch one one of our test machines.
>
> Tony.
> --
> ocmcocmcocmk**f.a.n.finch
> dot@dotat.at
> fanf@demon.net
>
> 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 2 16:45:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA08173
for freebsd-current-outgoing; Mon, 2 Nov 1998 16:45:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.kar.net (n188.cdialup.kar.net [195.178.130.188])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07788
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 16:42:40 -0800 (PST)
(envelope-from kushn@mail.kar.net)
Received: from localhost (volodya@localhost)
by mail.kar.net (8.9.1/8.8.8) with ESMTP id CAA23530;
Tue, 3 Nov 1998 02:41:43 +0200 (EET)
(envelope-from kushn@mail.kar.net)
Date: Tue, 3 Nov 1998 02:41:42 +0200 (EET)
From: Vladimir Kushnir <kushn@mail.kar.net>
X-Sender: volodya@kushnir.kiev.ua
To: Scott Michel <scottm@cs.ucla.edu>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Persistent buildworld error
In-Reply-To: <199811030027.QAA06179@mordred.cs.ucla.edu>
Message-ID: <Pine.BSF.4.05.9811030238140.23523-100000@kushnir.kiev.ua>
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, 2 Nov 1998, Scott Michel wrote:
> ===> sys/boot/i386/libi386
> make: don't know how to make machine/ansi.h. Stop
> *** Error code 2
>
> Been through a few cvsups over the last week, and buildworld
> bombs here consistently. I have a feeling I can do an installworld
> but before the less courageous freak out, here's a head's up.
>
> My buildworld is ELF.
>
Are you sure everything's all right with your source tree? I've just a
couple of hours finished buildworld with no hassle at all. Here's CTM, not
CVSup'd sources, though. But you say the last week...
>
> -scooter
>
Regards,
Vladimir
===========================|=======================
Vladimir Kushnir |
kushn@mail.kar.net, | Powered by FreeBSD
kushnir@ap3.bitp.kiev.ua |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 16:49:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA08491
for freebsd-current-outgoing; Mon, 2 Nov 1998 16:49: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 QAA08482
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 16:49:03 -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 TAA07008;
Mon, 2 Nov 1998 19:51:47 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Mon, 2 Nov 1998 19:51:47 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Brian Feldman <green@zone.syracuse.net>
cc: Tony Finch <dot@dotat.at>, current@FreeBSD.ORG
Subject: Re: Linux clone()
In-Reply-To: <Pine.BSF.4.05.9811021941340.19187-100000@zone.syracuse.net>
Message-ID: <Pine.BSF.4.05.9811021951000.14876-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
have you looked at linux-ktrace? it's in the ports, i don't know if it's
functional as of yet.
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 Mon, 2 Nov 1998, Brian Feldman wrote:
> Hmmm.. okay this would be a good test. Right now I'm going thru the
> various linuxthreads example programs.... The patch seems to be doing
> something wrong, and I'm unable to figure out what to do, due to Linux's
> humongously gross syscall system (so the kernel doesn't help me). It also
> seems now I was implementing a LIBRARY function, which is just a wrapper.
> If I could get my hands on what the real system calls' args are it would
> be great.
>
> Brian Feldman
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 16:53:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA09080
for freebsd-current-outgoing; Mon, 2 Nov 1998 16:53:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09075
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 16:53:08 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA19415;
Mon, 2 Nov 1998 19:52:56 -0500 (EST)
Date: Mon, 2 Nov 1998 19:52:56 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: Alfred Perlstein <bright@hotjobs.com>
cc: Tony Finch <dot@dotat.at>, current@FreeBSD.ORG
Subject: Re: Linux clone()
In-Reply-To: <Pine.BSF.4.05.9811021951000.14876-100000@porkfriedrice.ny.genx.net>
Message-ID: <Pine.BSF.4.05.9811021951130.19187-100000@zone.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I don't know, but I do know I need a real Linux syscall trace, not one of
MY syscall.
Brian Feldman
On Mon, 2 Nov 1998, Alfred Perlstein wrote:
>
> have you looked at linux-ktrace? it's in the ports, i don't know if it's
> functional as of yet.
>
> 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 Mon, 2 Nov 1998, Brian Feldman wrote:
>
> > Hmmm.. okay this would be a good test. Right now I'm going thru the
> > various linuxthreads example programs.... The patch seems to be doing
> > something wrong, and I'm unable to figure out what to do, due to Linux's
> > humongously gross syscall system (so the kernel doesn't help me). It also
> > seems now I was implementing a LIBRARY function, which is just a wrapper.
> > If I could get my hands on what the real system calls' args are it would
> > be great.
> >
> > Brian Feldman
> >
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 16: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 QAA09807
for freebsd-current-outgoing; Mon, 2 Nov 1998 16:59:24 -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 QAA09736
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 16:59:01 -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 UAA07032;
Mon, 2 Nov 1998 20:01:40 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Mon, 2 Nov 1998 20:01:40 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Brian Feldman <green@zone.syracuse.net>
cc: Tony Finch <dot@dotat.at>, current@FreeBSD.ORG
Subject: Re: Linux clone()
In-Reply-To: <Pine.BSF.4.05.9811021951130.19187-100000@zone.syracuse.net>
Message-ID: <Pine.BSF.4.05.9811021956560.14876-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
afaik that's what linux-ktrace does, it sees how you call the kernel
function? maybe i'm wrong that it will trunc the arguments.... or perform
implicit convertions to "fit" them into what the kernel says the syscall
takes. meanwhile i just downloaded glibc to have a peek at it for you :)
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 Mon, 2 Nov 1998, Brian Feldman wrote:
> I don't know, but I do know I need a real Linux syscall trace, not one of
> MY syscall.
>
> Brian Feldman
>
> On Mon, 2 Nov 1998, Alfred Perlstein wrote:
>
> >
> > have you looked at linux-ktrace? it's in the ports, i don't know if it's
> > functional as of yet.
> >
> > 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 Mon, 2 Nov 1998, Brian Feldman wrote:
> >
> > > Hmmm.. okay this would be a good test. Right now I'm going thru the
> > > various linuxthreads example programs.... The patch seems to be doing
> > > something wrong, and I'm unable to figure out what to do, due to Linux's
> > > humongously gross syscall system (so the kernel doesn't help me). It also
> > > seems now I was implementing a LIBRARY function, which is just a wrapper.
> > > If I could get my hands on what the real system calls' args are it would
> > > be great.
> > >
> > > Brian Feldman
> > >
> >
> >
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 17:03:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA10280
for freebsd-current-outgoing; Mon, 2 Nov 1998 17:03:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10268
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 17:03:06 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id UAA19559;
Mon, 2 Nov 1998 20:02:27 -0500 (EST)
Date: Mon, 2 Nov 1998 20:02:27 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: Alfred Perlstein <bright@hotjobs.com>
cc: Tony Finch <dot@dotat.at>, current@FreeBSD.ORG
Subject: Re: Linux clone()
In-Reply-To: <Pine.BSF.4.05.9811021956560.14876-100000@porkfriedrice.ny.genx.net>
Message-ID: <Pine.BSF.4.05.9811022000420.19187-100000@zone.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
Ktrace/kdump work inside the kernel more than outside, so they can't
figure out how many arguments there are in a system call, witout special
kernel handholding. Let me know what you learn in glibc, otherwise I'll
try to find someone witha Linux box to give me an account, so I can try
out ptrace.
Brian Feldman
On Mon, 2 Nov 1998, Alfred Perlstein wrote:
>
> afaik that's what linux-ktrace does, it sees how you call the kernel
> function? maybe i'm wrong that it will trunc the arguments.... or perform
> implicit convertions to "fit" them into what the kernel says the syscall
> takes. meanwhile i just downloaded glibc to have a peek at it for you :)
>
> 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 Mon, 2 Nov 1998, Brian Feldman wrote:
>
> > I don't know, but I do know I need a real Linux syscall trace, not one of
> > MY syscall.
> >
> > Brian Feldman
> >
> > On Mon, 2 Nov 1998, Alfred Perlstein wrote:
> >
> > >
> > > have you looked at linux-ktrace? it's in the ports, i don't know if it's
> > > functional as of yet.
> > >
> > > 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 Mon, 2 Nov 1998, Brian Feldman wrote:
> > >
> > > > Hmmm.. okay this would be a good test. Right now I'm going thru the
> > > > various linuxthreads example programs.... The patch seems to be doing
> > > > something wrong, and I'm unable to figure out what to do, due to Linux's
> > > > humongously gross syscall system (so the kernel doesn't help me). It also
> > > > seems now I was implementing a LIBRARY function, which is just a wrapper.
> > > > If I could get my hands on what the real system calls' args are it would
> > > > be great.
> > > >
> > > > Brian Feldman
> > > >
> > >
> > >
> >
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 17:15:17 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA12287
for freebsd-current-outgoing; Mon, 2 Nov 1998 17:15:17 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mcfs.whowhere.com (mcfs.whowhere.com [209.1.236.44])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA12276
for <current@freebsd.org>; Mon, 2 Nov 1998 17:15:14 -0800 (PST)
(envelope-from erkaf@my-dejanews.com)
Received: from Unknown/Local ([?.?.?.?]) by my-dejanews.com; Mon Nov 2 17:08:22 1998
To: current@FreeBSD.ORG
Date: Mon, 02 Nov 1998 17:08:22 -0700
From: "Kelvin Farmer" <erkaf@my-dejanews.com>
Message-ID: <HLNHMEEEIPNOHAAA@my-dejanews.com>
Mime-Version: 1.0
X-Sent-Mail: off
X-Mailer: MailCity Service
Subject: Re: make kernel fails:booktree848.c
X-Sender-Ip: 192.75.12.156
Organization: Deja News Mail (http://www.my-dejanews.com:80)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
--
On Mon, 02 Nov 1998 15:25:44 Kelvin Farmer wrote:
>I just updated my src tree (cvsup) but now I can't make a kernel, since i get the following error:
Nevermind... I saw the re:bktro broken thread and figured it out. The instructions in LINT are NOT clear about what to add to make bktr0 work.
adding:controller smbus0
device smb0 at smbus?
controller iicbus0
controller icbb0
device ic0 at iicbus?
device iic0 at iicbus?
device iicsmb0 at iicbus?
device iicbb0 at iicbus?
device bktr0
to the config file works, and produces on bootup:
bktr0: <BrookTree 848> rev 0x11 int a irq 10 on pci0.19.0
bti2c0: <bt848 Hard/Soft I2C controller>
iicbb0: <I2C generic bit-banging driver> on bti2c0
iicbus0: <Philips I2C bus> on iicbb0 addr 0xf0
Probing for devices on iicbus0: <c0> <c1> <c2> <c3>
iicsmb0: <I2C to SMB bridge> on iicbus0
smbus0: <System Management Bus> on iicsmb0
smbus1: <System Management Bus> on bti2c0
Miro TV, Temic NTSC tuner.
I suppose detailed info on what exactly IS needed is yet to come... =)
Cheers
Kelvin.
-----== Sent via Deja News, The Discussion Network ==-----
http://www.dejanews.com/ Easy access to 50,000+ discussion forums
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 17:37:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA14867
for freebsd-current-outgoing; Mon, 2 Nov 1998 17:37:38 -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 RAA14832
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 17:37:25 -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 XAA05989;
Mon, 2 Nov 1998 23:57:24 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 XAA03594;
Mon, 2 Nov 1998 23:57:59 GMT
(envelope-from brian@woof.lan.awfulhak.org)
Message-Id: <199811022357.XAA03594@woof.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Dan Nelson <dnelson@emsphone.com>
cc: Brian Somers <brian@Awfulhak.org>, "John W. DeBoskey" <jwd@unx.sas.com>,
Brian Feldman <green@zone.syracuse.net>, freebsd-current@FreeBSD.ORG
Subject: Re: Changing sh for compatibility sake
In-reply-to: Your message of "Sun, 01 Nov 1998 21:05:12 CST."
<19981101210512.A21213@emsphone.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 23:57:59 +0000
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> In the last episode (Nov 01), Brian Somers said:
> > The *only* shell I've ever seen that does this is the original ksh.
> > I think it's a *great* feature, but it's also non-standard. With it,
> > you can also
> >
> > echo hello there | read a b
> >
> > and get $a and $b back. Certainly, any version of sh, ash, zsh, bash
> > and pdksh that I've seen execute everything in the pipe in a subshell.
>
> ? I thought standard procedure was to execute the last command in a
> pipe in the parent shell. Your command runs fine on zsh and bash (not
> ash though).
I haven't got an installed zsh handy, but:
dev:~ $ bash
dev:~ $ echo hello there | read a b
dev:~ $ echo $a $b
dev:~ $ echo $BASH_VERSION
2.01.0(1)-release
dev:~ $
>From the man page:
Each command in a pipeline is executed as a separate pro-
cess (i.e., in a subshell).
Zsh behaved the same with the latest release from about 3 months ago.
> -Dan
--
Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <brian@OpenBSD.org>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour....
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 17:40:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA15213
for freebsd-current-outgoing; Mon, 2 Nov 1998 17:40:05 -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 RAA15208
for <freebsd-current@freebsd.org>; Mon, 2 Nov 1998 17:40:03 -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 RAA06721;
Mon, 2 Nov 1998 17:39:04 -0800 (PST)
(envelope-from scottm@mordred.cs.ucla.edu)
Message-Id: <199811030139.RAA06721@mordred.cs.ucla.edu>
X-Mailer: exmh version 2.0.2 2/24/98
To: Vladimir Kushnir <kushn@mail.kar.net>
cc: Scott Michel <scottm@CS.UCLA.EDU>, freebsd-current@FreeBSD.ORG
Subject: Re: Persistent buildworld error
In-reply-to: Your message of "Tue, 03 Nov 1998 02:41:42 +0200."
<Pine.BSF.4.05.9811030238140.23523-100000@kushnir.kiev.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 02 Nov 1998 17:39:04 -0800
From: Scott Michel <scottm@CS.UCLA.EDU>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
My last cvsup was from last night, ca. 4pm Pacific.
> On Mon, 2 Nov 1998, Scott Michel wrote:
>
> > ===> sys/boot/i386/libi386
> > make: don't know how to make machine/ansi.h. Stop
> > *** Error code 2
> >
> > Been through a few cvsups over the last week, and buildworld
> > bombs here consistently. I have a feeling I can do an installworld
> > but before the less courageous freak out, here's a head's up.
> >
> > My buildworld is ELF.
> >
>
> Are you sure everything's all right with your source tree? I've just a
> couple of hours finished buildworld with no hassle at all. Here's CTM, not
> CVSup'd sources, though. But you say the last week...
>
> >
> > -scooter
> >
>
> Regards,
> Vladimir
>
>
> ===========================|=======================
> Vladimir Kushnir |
> kushn@mail.kar.net, | Powered by FreeBSD
> kushnir@ap3.bitp.kiev.ua |
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 17:57:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA17798
for freebsd-current-outgoing; Mon, 2 Nov 1998 17:57:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.kar.net (n188.cdialup.kar.net [195.178.130.188])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17750
for <freebsd-current@freebsd.org>; Mon, 2 Nov 1998 17:56:45 -0800 (PST)
(envelope-from kushn@mail.kar.net)
Received: from localhost (volodya@localhost)
by mail.kar.net (8.9.1/8.8.8) with ESMTP id DAA24150;
Tue, 3 Nov 1998 03:56:06 +0200 (EET)
(envelope-from kushn@mail.kar.net)
Date: Tue, 3 Nov 1998 03:56:05 +0200 (EET)
From: Vladimir Kushnir <kushn@mail.kar.net>
X-Sender: volodya@kushnir.kiev.ua
To: Scott Michel <scottm@CS.UCLA.EDU>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Persistent buildworld error
In-Reply-To: <199811030139.RAA06721@mordred.cs.ucla.edu>
Message-ID: <Pine.BSF.4.05.9811030349220.23905-100000@kushnir.kiev.ua>
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, 2 Nov 1998, Scott Michel wrote:
> My last cvsup was from last night, ca. 4pm Pacific.
>
> > On Mon, 2 Nov 1998, Scott Michel wrote:
> >
> > > ===> sys/boot/i386/libi386
> > > make: don't know how to make machine/ansi.h. Stop
> > > *** Error code 2
> > >
> > > Been through a few cvsups over the last week, and buildworld
> > > bombs here consistently. I have a feeling I can do an installworld
> > > but before the less courageous freak out, here's a head's up.
> > >
> > > My buildworld is ELF.
> > >
> >
Ok, it seems I've got it. It looks there's an old .depend in there, but no
link
machine -> /usr/src/sys/boot/i386/libi386/../../../i386/include
(from previous build, perhaps). And (possibly) buildworld doesn't do it
there automatically. Do "make cleandepend" in /usr/src/sys/boot first
(sorry, I'm telling an obvious things, but that's the most common
overlooks which are the most trivial).
Hope this helps,
Vladimir
===========================|=======================
Vladimir Kushnir |
kushn@mail.kar.net, | Powered by FreeBSD
kushnir@ap3.bitp.kiev.ua |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 18:04:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA19020
for freebsd-current-outgoing; Mon, 2 Nov 1998 18:04:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from garman.dyn.ml.org (pm106-19.dialip.mich.net [192.195.231.221])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA18996
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 18:04:48 -0800 (PST)
(envelope-from garman@garman.dyn.ml.org)
Message-Id: <199811030204.SAA18996@hub.freebsd.org>
Received: (qmail 25587 invoked from smtpd); 3 Nov 1998 02:05:40 -0000
Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1)
by localhost.garman.net with SMTP; 3 Nov 1998 02:05:40 -0000
Date: Mon, 2 Nov 1998 21:05:39 -0500 (EST)
From: garman@earthling.net
Reply-To: garman@earthling.net
Subject: Re: still problems with inetd & malloc...
To: jmz@FreeBSD.ORG
cc: current@FreeBSD.ORG
In-Reply-To: <199811021354.OAA09972@qix>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 2 Nov, Jean-Marc Zucconi wrote:
> There is a fix (it works for me). Look for
> Subject: Re: bin/8183: Signal handlers in inetd.c are unsafe
> in the archives.
>
thanks for the pointer. it's working so far... so now the $64,000
question is: why hasn't this been committed?
enjoy
--
Jason Garman http://garman.dyn.ml.org/
Student, University of Maryland garman@earthling.net
And now... for the stupid-patent-of-the-week: Whois: JAG145
"...an attache case with destruct means for destroying the contents
therein in response to a signal" -- patent no. US3643609, filed in 1969
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 19:14:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA27763
for freebsd-current-outgoing; Mon, 2 Nov 1998 19:14:15 -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 TAA27756
for <freebsd-current@freebsd.org>; Mon, 2 Nov 1998 19:14:14 -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 0zaWus-0001ZT-00; Mon, 2 Nov 1998 19:13:58 -0800
Date: Mon, 2 Nov 1998 19:13:54 -0800 (PST)
From: Tom <tom@uniserve.com>
X-Sender: tom@shell.uniserve.ca
To: Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Memory Usage under -current
In-Reply-To: <199811021418.AAA25420@zeus.theinternet.com.au>
Message-ID: <Pine.BSF.4.02A.9811021906480.6356-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, 3 Nov 1998, Andrew Kenneth Milton wrote:
> I'm just comparing the sizes of processes under an ELF -current
> and a 2.2.5 system, and my recollections of what my machine used to look
> like.
>
> It seems that a lot more memory is being consumed by the ELF system..
You should compare a 3.0 aout to a 3.0 elf system. I belive the memory
size reporting has changed significantly between 2.2.x and 3.0, and these
reporting changes are what you are seeing. I don't think 2.2.x included
certain shared objects in its count.
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 2 19:24:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA28570
for freebsd-current-outgoing; Mon, 2 Nov 1998 19:24:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cheshire.dynip.com (pm-wsh1-39.coastalnet.com [205.245.121.39])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28543
for <current@freebsd.org>; Mon, 2 Nov 1998 19:23:56 -0800 (PST)
(envelope-from ryan@cheshire.dynip.com)
Received: (from ryan@localhost)
by cheshire.dynip.com (8.9.1/8.9.1) id WAA25340
for current@freebsd.org; Mon, 2 Nov 1998 22:23:35 -0500 (EST)
(envelope-from ryan)
Message-Id: <199811030323.WAA25340@cheshire.dynip.com>
Subject: Current 'make world' warnings cleanup
To: current@FreeBSD.ORG
Date: Mon, 2 Nov 1998 22:23:33 -0500 (EST)
From: Ryan Younce <ryany@pobox.com>
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi all,
I'm not 100% certain if this is the right place to be asking this, but:
I noticed on the FreeBSD projects page that running a make world with extra
warnings enabled, and then clean up the warnings, although not a high priority
project, would be a good thing to do.
Well, seeing as how my count of all instances of ' warning: ' within my log
of my most recent make world totals to about 85,000 lines, I figure this
might be as good a place as any to burn my weekend/weeknight time.
Is there a coordinator for this? As this is my first time sending anything
to any of the mailing lists, let alone contributing, I figure lowering the
above number would be as good a place to start as any. What is the best way
to go about cleaning up the warnings out of code? Fixing up a diff and
submitting it via send-pr(1) like normal? Or would this be overkill in this
situation?
Thanks in advance,
Ryan Younce
ryany@pobox.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 2 19:36:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA29795
for freebsd-current-outgoing; Mon, 2 Nov 1998 19:33:04 -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 TAA29790
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 19:33:03 -0800 (PST)
(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
by lor.watermarkgroup.com (8.8.8/8.8.8) id WAA24322;
Mon, 2 Nov 1998 22:32:55 -0500 (EST)
(envelope-from luoqi)
Date: Mon, 2 Nov 1998 22:32:55 -0500 (EST)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <199811030332.WAA24322@lor.watermarkgroup.com>
To: dot@dotat.at, green@zone.syracuse.net
Subject: Re: Linux clone()
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Hmmm.. okay this would be a good test. Right now I'm going thru the
> various linuxthreads example programs.... The patch seems to be doing
> something wrong, and I'm unable to figure out what to do, due to Linux's
> humongously gross syscall system (so the kernel doesn't help me). It also
> seems now I was implementing a LIBRARY function, which is just a wrapper.
> If I could get my hands on what the real system calls' args are it would
> be great.
>
> Brian Feldman
>
It seems that clone() the syscall takes two arguments:
struct linux_clone_args {
int flags;
void *stack;
};
the wrapper in library takes care of pushing the function address and its
argument on to the stack. You probably also want to map linux clone flags
to that of rfork's: CLONE_FILES -> RFFDG, CLONE_VM -> RFMEM.
-lq
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 19:59:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA02866
for freebsd-current-outgoing; Mon, 2 Nov 1998 19:59:32 -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 TAA02861
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 19:59:30 -0800 (PST)
(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
by lor.watermarkgroup.com (8.8.8/8.8.8) id WAA24618;
Mon, 2 Nov 1998 22:59:24 -0500 (EST)
(envelope-from luoqi)
Date: Mon, 2 Nov 1998 22:59:24 -0500 (EST)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <199811030359.WAA24618@lor.watermarkgroup.com>
To: dot@dotat.at, green@zone.syracuse.net
Subject: Re: Linux clone()
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Hmmm.. okay this would be a good test. Right now I'm going thru the
> > various linuxthreads example programs.... The patch seems to be doing
> > something wrong, and I'm unable to figure out what to do, due to Linux's
> > humongously gross syscall system (so the kernel doesn't help me). It also
> > seems now I was implementing a LIBRARY function, which is just a wrapper.
> > If I could get my hands on what the real system calls' args are it would
> > be great.
> >
> > Brian Feldman
> >
> It seems that clone() the syscall takes two arguments:
> struct linux_clone_args {
> int flags;
> void *stack;
> };
> the wrapper in library takes care of pushing the function address and its
> argument on to the stack. You probably also want to map linux clone flags
> to that of rfork's: CLONE_FILES -> RFFDG, CLONE_VM -> RFMEM.
I made a mistake, it should be !CLONE_FILES -> RFFDG. And there's no rfork()
counterpart for CLONE_SIGHAND, default rfork behavior corresponds to
!CLONE_SIGHAND.
-lq
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 19:59:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA02891
for freebsd-current-outgoing; Mon, 2 Nov 1998 19:59:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [36.118.0.70])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02884
for <current@freebsd.org>; Mon, 2 Nov 1998 19:59:38 -0800 (PST)
(envelope-from techie@tantivy.stanford.edu)
Received: (from techie@localhost)
by tantivy.stanford.edu (8.8.8/8.8.5) id TAA25359
for current@freebsd.org; Mon, 2 Nov 1998 19:59:31 -0800 (PST)
Date: Mon, 2 Nov 1998 19:59:31 -0800 (PST)
From: Bob Vaughan <techie@tantivy.stanford.edu>
Message-Id: <199811030359.TAA25359@tantivy.stanford.edu>
To: current@FreeBSD.ORG
Subject: pccard ethernet breakage between 2.2-stable and 3.0-current
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
cvs update as of saturday (both trees).
my sthernet card (a SVEC ne2000 compatable) breaks under 3.0-current only,
but 2.2-stable works fine.
I noticed the same type of breakage in PAO when i tried it back in july/august.
symptoms: my ethernet card returns a bogus hardware address the first couple
of times it is probed, but the third time it returns the correct address.
the 2.2-stable code properly deals with this, while the 3.0-current code
accepts the bogus address..
hardware: chembook 3300 (p233mmx, 96mb ram, 4gb disk), SVEC ne2000 compatable
ethernet card.
-- Welcome My Son, Welcome To The Machine --
Bob Vaughan | techie@w6yx.stanford.edu | kc6sxc@w6yx.ampr.org
| techie@t.stanford.edu | KC6SXC@W6YX.#NCA.CA.USA.NOAM
| P.O. Box 9792, Stanford, Ca 94309-9792
-- I am Me, I am only Me, And no one else is Me, What could be simpler? --
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 20:17:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA05461
for freebsd-current-outgoing; Mon, 2 Nov 1998 20:17:02 -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 UAA05456
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 20:17: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 XAA02355
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 23:16:52 -0500 (EST)
Date: Mon, 2 Nov 1998 23:16:52 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: freebsd-current@FreeBSD.ORG
Subject: Re: Memory Usage under -current
In-Reply-To: <Pine.BSF.4.02A.9811021906480.6356-100000@shell.uniserve.ca>
Message-ID: <Pine.BSF.4.05.9811022309260.2272-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, 2 Nov 1998, Tom wrote:
> You should compare a 3.0 aout to a 3.0 elf system. I belive the memory
> size reporting has changed significantly between 2.2.x and 3.0, and these
> reporting changes are what you are seeing. I don't think 2.2.x included
> certain shared objects in its count.
Which reminds me....I posted a question about this some time ago
and didn't get an answer. On my 64MB+128MB swap system, systat
reports like this:
Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER
Tot Share Tot Share Free in out in out
Act 20116 2128 3819008 3480 4724 count
All 63892 11452 904292 19628 pages
The figure for Total Active Virtual strikes me as being just a little
out of whack. Curiously, it gives a more believable figure in single
user mode.
This isn't 3.0 specific...it happend in the 2.2.x series as well, but
it only does it on this one machine.
-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 2 20:30:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA07443
for freebsd-current-outgoing; Mon, 2 Nov 1998 20:30:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from daphne.bogus (dialup8.black-hole.com [206.145.13.28])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07291
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 20:29:38 -0800 (PST)
(envelope-from hank@black-hole.com)
Received: from localhost (hank@localhost)
by daphne.bogus (8.9.1/8.8.8) with SMTP id XAA02127;
Mon, 2 Nov 1998 23:28:30 -0600 (CST)
(envelope-from hank@black-hole.com)
X-Authentication-Warning: daphne.bogus: hank owned process doing -bs
Date: Mon, 2 Nov 1998 23:28:30 -0600 (CST)
From: Henry Miller <hank@black-hole.com>
X-Sender: hank@daphne.bogus
To: Ryan Younce <ryany@pobox.com>
cc: current@FreeBSD.ORG
Subject: Re: Current 'make world' warnings cleanup
In-Reply-To: <199811030323.WAA25340@cheshire.dynip.com>
Message-ID: <Pine.BSF.3.96.981102232057.1392A-100000@daphne.bogus>
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, 2 Nov 1998, Ryan Younce wrote:
> Hi all,
>
> I'm not 100% certain if this is the right place to be asking this, but:
> I noticed on the FreeBSD projects page that running a make world with extra
> warnings enabled, and then clean up the warnings, although not a high priority
> project, would be a good thing to do.
Very good. I've seen this myself, and considered a go at it. Like you
I'm not sure how to procede. I know how to program, but I don't know how
to extend that to FreeBSD.
> Well, seeing as how my count of all instances of ' warning: ' within my log
> of my most recent make world totals to about 85,000 lines, I figure this
> might be as good a place as any to burn my weekend/weeknight time.
Try compiling a LINT kernel with -Wall. The goal is LINT compiles
without warnings. (note, this may be impossiable. LINT isn't supposed to
be bootable, and the warning might catch a conflict)
> Is there a coordinator for this? As this is my first time sending anything
> to any of the mailing lists, let alone contributing, I figure lowering the
> above number would be as good a place to start as any. What is the best way
> to go about cleaning up the warnings out of code? Fixing up a diff and
> submitting it via send-pr(1) like normal? Or would this be overkill in this
> situation?
What I want to know is how devolpers configure their src tree. What I
don't want to do is
cd /usr/src/something
ed bad_file.c
Get about half done, and then go to bed overnight the following happens:
cvsup (from cron)
overwrites bad_file.c with some change not related to what I'm doing,
causing a loss of work.
And on the related note I need to get the proper diff's when I'm ready to
submit a patch.
I have used RCS before, and I know CVS can put RCS files on my system.
The question is can Make read RCS files, and extract the right version,
and can cvs do the right thing? I obviously would like to test a kernel
before I submit a patch, and once in a while I like to get the latest
sources.
So how do devolpers setup their build enviroment? (understanding this is
a personal thing)
--
http://blugill.home.ml.org/
hank@black-hole.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 2 21:23:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA13770
for freebsd-current-outgoing; Mon, 2 Nov 1998 21:23:04 -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 VAA13762
for <freebsd-current@FreeBSD.ORG>; Mon, 2 Nov 1998 21:23:00 -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 NAA21942;
Tue, 3 Nov 1998 13:21:44 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811030521.NAA21942@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman <green@zone.syracuse.net>
cc: John Hay <jhay@mikom.csir.co.za>, freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-reply-to: Your message of "Mon, 02 Nov 1998 19:36:27 EST."
<Pine.BSF.4.05.9811021935420.19187-100000@zone.syracuse.net>
Date: Tue, 03 Nov 1998 13:21:43 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Feldman wrote:
> Ahhhh, that's where it is! I have no good idea on how to allow, with this
> code, lkm's and kld's to coexist.... so is it time to completely phase out
> lkm's yet?
I think the best way is to have mount(2) initiate a kldload if needed. We
will need this functionality sooner or later. If mount(2) does it, we can
garbage collect unused, unmounted filesystems after a while and unload
them.
> Brian Feldman
>
> On Mon, 2 Nov 1998, John Hay wrote:
>
> > > Be sure to let me know when ELF kernels can autoload kld modules like the
> > > current a.out kernel does with lkm's.
> >
> > It's not the kernel that loads them. Go and look in lib/libc/gen/getvfsent.
c
> >
> > John
> > --
> > John Hay -- John.Hay@mikom.csir.co.za
> >
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
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 Mon Nov 2 22:06:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA18999
for freebsd-current-outgoing; Mon, 2 Nov 1998 22:06:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fire.starkreality.com (fire.starkreality.com [208.24.48.226])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18973
for <freebsd-current@freebsd.org>; Mon, 2 Nov 1998 22:05:59 -0800 (PST)
(envelope-from caesar@starkreality.com)
Received: from armageddon (armageddon.starkreality.com [208.24.48.227])
by fire.starkreality.com (8.9.1/8.9.1) with SMTP id AAA01332
for <freebsd-current@freebsd.org>; Tue, 3 Nov 1998 00:05:48 -0600 (CST)
(envelope-from caesar@starkreality.com)
Message-Id: <4.1.19981102235947.052f0100@fire.starkreality.com>
X-Sender: caesar@fire.starkreality.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Tue, 03 Nov 1998 00:05:40 -0600
To: freebsd-current@FreeBSD.ORG
From: "William S. Duncanson" <caesar@starkreality.com>
Subject: Err...something fishy going on in top.
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
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?
William S. Duncanson caesar@starkreality.com
The driving force behind the NC is the belief that the companies who brought us
things like Unix, relational databases, and Windows can make an appliance that
is inexpensive and easy to use if they choose to do that. -- Scott Adams
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Mon Nov 2 22:41:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA24880
for freebsd-current-outgoing; Mon, 2 Nov 1998 22:41:32 -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 WAA24873
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 22:41:28 -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 RAA26382;
Tue, 3 Nov 1998 17:10:53 +1030 (CST)
(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.981103171052.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: <Pine.BSF.3.96.981102232057.1392A-100000@daphne.bogus>
Date: Tue, 03 Nov 1998 17:10:52 +1030 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: Henry Miller <hank@black-hole.com>
Subject: Re: Current 'make world' warnings cleanup
Cc: current@FreeBSD.ORG, Ryan Younce <ryany@pobox.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 03-Nov-98 Henry Miller wrote:
> So how do devolpers setup their build enviroment? (understanding this is
> a personal thing)
Instead cvsuping a given version, cvsup the cvs repo instead, so that way you
can keep up to date, but you have the choice about wether you update a given
file or not. The idea is that you checkout a give version of the code and then
mangle it however you like and get it working. Then you get CVS to generate the
diff's from your modifications which you send to a commiter who reviews it,
etc..
If you go this road, I'd recommend copying the CVS repo of a FreeBSD CD (if
you have one of course :) and then updating it.. Muuuuch quicker :)
---
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 Mon Nov 2 22:53:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA26939
for freebsd-current-outgoing; Mon, 2 Nov 1998 22:53:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26929
for <current@FreeBSD.ORG>; Mon, 2 Nov 1998 22:53:37 -0800 (PST)
(envelope-from tseidmann@simultan.ch)
Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53])
by SIMULTAN.CH (8.9.1a/8.9.1) with ESMTP id HAA13991;
Tue, 3 Nov 1998 07:53:19 +0100 (CET)
Message-ID: <363EA85E.8CB9A118@simultan.ch>
Date: Tue, 03 Nov 1998 07:53:18 +0100
From: Thomas Seidmann <tseidmann@simultan.ch>
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Sebastian Lederer <lederer@bonn-online.com>
CC: current@FreeBSD.ORG
Subject: Re: IPv6 in -current
References: <199811012217.OAA16854@mordred.cs.ucla.edu> <363CE849.B76F70FF@simultan.ch> <363DF9C6.45C26C7C@bonn-online.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Sebastian Lederer wrote:
> FWIW, the last time I tried INRIA IPv6 (about four months ago), it broke
> some userland IPv4 stuff. I had some NIS problems/crashes, also NFS export
> control lists and /etc/lpd.hosts didn't work anymore. KAME IPv6 does not
> have these problems (but INRIA's kernel code might be more stable).
I encuntered problems with NFS exports from a INRIA IPv6 enable machine
during the time of the relaease for 2.2.5-RELEASE (about 6 moths ago).
No problems with NIS nor hosts.lpd, however (YMMV). The above mentioned
problems are gone in the present release according to my experiences.
Regards,
Thomas
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 00:30:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA06694
for freebsd-current-outgoing; Tue, 3 Nov 1998 00:30:04 -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 AAA06633
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 00:29:59 -0800 (PST)
(envelope-from john.saunders@scitec.com.au)
Received: by firewall.scitec.com.au; id TAA01686; Tue, 3 Nov 1998 19:29:42 +1100 (EST)
Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2)
id xma001682; Tue, 3 Nov 98 19:29:26 +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 TAA01865; Tue, 3 Nov 1998 19:29:19 +1100
From: "John Saunders" <john.saunders@scitec.com.au>
To: "Mike Smith" <mike@smith.net.au>
Cc: <current@FreeBSD.ORG>
Subject: RE: New boot loader and alternate kernels
Date: Tue, 3 Nov 1998 19:29:18 +1100
Message-ID: <000601be0704$0cda76a0$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
In-Reply-To: <199811022258.OAA02025@dingo.cdrom.com>
X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4
Importance: Normal
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Smith wrote:
> > FORTH does have a decent pedigree as a bootloader - Sun have been
> > using it for at least 6 years. Most user interaction is covered
> > by "boot FILE FLAGS", "reset" and "sync" - you don't have to be
> > a FORTH guru to use it.
>
> That's my hope. We also have enough manifest Forth talent to get us
> bootstrapped to that stage, so I don't view it as technically
> impossible. The philosophical issues are still bugging me.
While not being a FORTH fan (horrible syntax :-) I can see that
it has very desirable attributes for a boot loader. If it can
provide a "boot kernel flags" style interface then who cares
if FORTH is behind it.
I also see things in the future like probing hardware and booting
custom kernels. Certainly a good tool for creating install
distributions.
It's good that the "philosophical issues" are bugging you. That
means that should FORTH get the go-ahead it will be on technical
merit rather than due to advocacy issues :-)
Cheers.
-- . +-------------------------------------------------------+
,--_|\ | 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 Tue Nov 3 01:05:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA11704
for freebsd-current-outgoing; Tue, 3 Nov 1998 01:05:26 -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 BAA11687
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 01:05:24 -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 BAA13428;
Tue, 3 Nov 1998 01:05:58 -0800 (PST)
Message-Id: <199811030905.BAA13428@implode.root.com>
To: "William S. Duncanson" <caesar@starkreality.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Err...something fishy going on in top.
In-reply-to: Your message of "Tue, 03 Nov 1998 00:05:40 CST."
<4.1.19981102235947.052f0100@fire.starkreality.com>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 03 Nov 1998 01:05:58 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>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
cached file pages are always put onto the inactive queue rather than just
some of the time (they previously would also be put onto the cache queue).
This actually improves performance because it keeps the pages better LRU
sorted. When memory becomes short, the pagedaemon will move the pages to
the cache queue (and then to the free queue) as needed. This will not
significantly increase CPU usage and will increase overall system
performance by a measurable amount.
-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 Tue Nov 3 01:06:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA11973
for freebsd-current-outgoing; Tue, 3 Nov 1998 01:06:43 -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 BAA11966
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 01:06:40 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id BAA15199;
Tue, 3 Nov 1998 01:00:12 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdo15193; Tue Nov 3 09:00:09 1998
Date: Tue, 3 Nov 1998 00:59:44 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Alfred Perlstein <bright@hotjobs.com>
cc: current@FreeBSD.ORG
Subject: Re: wondering about DEVFS & MFS?
In-Reply-To: <Pine.BSF.4.05.9811021627050.14876-100000@porkfriedrice.ny.genx.net>
Message-ID: <Pine.BSF.3.95.981103005457.404B-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 can't use an MFS root and DEVFS together due to the fact that MFS
synthesizes a device node which needless to say, devfs doesn't know
anything about.
If you've got an ffs root and just put devfs over the top of your
existing /dev/you'll be ok but with and MFS ROOT you're screwed..
I still have devfs fixes to put in but am busy on other things.
It works in the situation I mentionned.
On Mon, 2 Nov 1998, Alfred Perlstein wrote:
>
> mfs is working fine for me as my /tmp, i used to be a big fan of DEVFS,
> how is it coming along? usable again? any caveats?
>
> i know LINT says DEVFS+MFS is a no-no, is this still true?
in some particular cases ... yes.
>
> thanks,
> 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 Tue Nov 3 01:48:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA16614
for freebsd-current-outgoing; Tue, 3 Nov 1998 01:48:37 -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 BAA16609
for <current@freebsd.org>; Tue, 3 Nov 1998 01:48:35 -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 JAA06671;
Tue, 3 Nov 1998 09:47:20 GMT
Date: Tue, 3 Nov 1998 09:47:20 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Robert Watson <robert+freebsd@cyrus.watson.org>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, dg@root.com,
Jun-ichiro itojun Itoh <itojun@itojun.org>, obrien@NUXI.com,
Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, current@FreeBSD.ORG
Subject: Re: IPv6 in -current
In-Reply-To: <Pine.BSF.3.96.981102100920.15227E-100000@fledge.watson.org>
Message-ID: <Pine.BSF.4.01.9811030946560.3018-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, 2 Nov 1998, Robert Watson wrote:
> On Mon, 2 Nov 1998, Jordan K. Hubbard wrote:
>
> > Yeah, if I had my druthers (and what the hell are "druthers" anyway,
> > and who here has ever had any that they knew of? Why is English such
> > a peculiar language? And why... Erm, excuse me, I guess that's not
> > really important right now), I'd want to see the IPv6 bits integrated
> > with the following provisos:
>
> English is a truly bizarre language. I'll dig up my OED this evening and
> let you know :-P.
Its some kind of bizarre contraction of 'would rather' I think.
--
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 Tue Nov 3 04:11:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA29456
for freebsd-current-outgoing; Tue, 3 Nov 1998 04:11:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29428;
Tue, 3 Nov 1998 04:11:00 -0800 (PST)
(envelope-from semen@iclub.nsu.ru)
Received: from localhost (semen@localhost)
by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id SAA02403;
Tue, 3 Nov 1998 18:15:39 +0600 (NS)
Date: Tue, 3 Nov 1998 18:15:39 +0600 (NS)
From: Ustimenko Semen <semen@iclub.nsu.ru>
To: current@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: Another NTFS RO driver
Message-ID: <Pine.BSF.3.96.981103180545.2205A-100000@iclub.nsu.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello!
Here is another new Windows NT filesystem (NTFS) driver.
It is read-only, and of couse aim to become read-write...
If you have any info on NTFS structure and especially on it's
$LogFile... i love to have a look at it. Please.
source:
http://www.iclub.nsu.ru/~semen/ntfs/ntfs-0.1beta.tgz
Thank you.
P.S. Drop me a message if you tryed this one or have already used
another. Please.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 04: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 EAA00515
for freebsd-current-outgoing; Tue, 3 Nov 1998 04:20:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA00187;
Tue, 3 Nov 1998 04:19:37 -0800 (PST)
(envelope-from semen@iclub.nsu.ru)
Received: from localhost (semen@localhost)
by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id SAA02517;
Tue, 3 Nov 1998 18:24:37 +0600 (NS)
Date: Tue, 3 Nov 1998 18:24:37 +0600 (NS)
From: Ustimenko Semen <semen@iclub.nsu.ru>
To: current@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: SMC9432TX driver (tx) users
Message-ID: <Pine.BSF.3.96.981103181729.2205B-100000@iclub.nsu.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello!
If you use tx driver under FreeBSD, can you send me private
message if you have ANY problems useing it.
Even if the problem is only
tx0: timeout %d packets, ...
Thank you.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 05:06:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA04859
for freebsd-current-outgoing; Tue, 3 Nov 1998 05:06:21 -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 FAA04854
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 05:06:18 -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 IAA00463;
Tue, 3 Nov 1998 08:03:28 -0500 (EST)
Date: Tue, 3 Nov 1998 08:03:28 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Peter Wemm <peter@netplex.com.au>
cc: Brian Feldman <green@zone.syracuse.net>, John Hay <jhay@mikom.csir.co.za>,
freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-Reply-To: <199811030521.NAA21942@spinner.netplex.com.au>
Message-ID: <Pine.BSF.4.05.9811030759560.300-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, 3 Nov 1998, Peter Wemm wrote:
> Brian Feldman wrote:
> > Ahhhh, that's where it is! I have no good idea on how to allow, with this
> > code, lkm's and kld's to coexist.... so is it time to completely phase out
> > lkm's yet?
>
> I think the best way is to have mount(2) initiate a kldload if needed. We
> will need this functionality sooner or later. If mount(2) does it, we can
> garbage collect unused, unmounted filesystems after a while and unload
> them.
Peter, you once told me that the new elf kernel has both aout and elf
linkers in it. Does an elf kernel have the ability to load lkm modules,
not the .ko things? If so, then the mount stuff is going to need to
know which kind of module to hunt for, to load, right? Or, if they both
work, maybe find both, and load the newest? With maybe a kld bias for a
tiebreaker?
----------------------------+-----------------------------------------------
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 3 05: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 FAA06844
for freebsd-current-outgoing; Tue, 3 Nov 1998 05:25:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from top.worldcontrol.com (surf40.cruzers.com [205.215.232.40])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA06839
for <freebsd-current@freebsd.org>; Tue, 3 Nov 1998 05:25:19 -0800 (PST)
(envelope-from brian@worldcontrol.com)
From: brian@worldcontrol.com
Received: (qmail 3313 invoked by uid 100); 3 Nov 1998 13:25:39 -0000
Date: Tue, 3 Nov 1998 05:25:39 -0800
To: freebsd-current@FreeBSD.ORG
Subject: PC Cards services without an IRQ?
Message-ID: <19981103052539.A3306@top.worldcontrol.com>
Mail-Followup-To: freebsd-current@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.9i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'm short IRQs on my laptop. Would it be feasible to have
the pccard services manager not rely on having one for itself?
I'm suggesting that instead, when I change cards, I run a
program so the system will rescan the cardbus.
Unless this is impossible, or already implemented in some way
I have not discovered, I'd like to take a stab at implementing
it.
On the other hand, if there is "no f*cking way" it will every
be accepted into the source tree, let me know, and I'll look
for another solution.
(I've given up on maintaining changes outside of the main tree)
--
Brian Litzinger <brian@litzinger.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 06:04:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA11355
for freebsd-current-outgoing; Tue, 3 Nov 1998 06:04:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from momus.tatrahome.sk (momus.tatrahome.sk [195.168.47.34])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11295
for <freebsd-current@freebsd.org>; Tue, 3 Nov 1998 06:04:29 -0800 (PST)
(envelope-from tomas@hodan.sk)
Received: from th-pc.traco.sk (frodo.traco.sk [195.168.45.193])
by momus.tatrahome.sk (8.8.8/8.8.8) with SMTP id PAA24786
for <freebsd-current@freebsd.org>; Tue, 3 Nov 1998 15:01:04 +0100 (CET)
(envelope-from tomas@hodan.sk)
Reply-To: <tomas@hodan.sk>
From: "Tomas Hodan" <tomas@hodan.sk>
To: <freebsd-current@FreeBSD.ORG>
Subject: AIC 6x60
Date: Tue, 3 Nov 1998 15:03:20 +0100
Message-ID: <001101be0732$b6717280$4000000a@th-pc.traco.sk>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-2"
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
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi all,
it is any possibilit to use Adapec APA-1460 PCMCIA SCSI Adapter with 3.0 ?
thanks
tomas
mouse:/sys/compile/MOUSE# make depend
rm -f .newdep
mkdep -a -f
newdep -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-ext
erns -Wstrict-prototypes -Wmissing-prototyc
cc: ../../dev/aic6x60/aic.c: No such file or directory
cc: ../../i386/isa/aic_isa.c: No such file or directory
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 06: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 GAA13026
for freebsd-current-outgoing; Tue, 3 Nov 1998 06:16:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13021
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 06:16:10 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id JAA27776;
Tue, 3 Nov 1998 09:15:55 -0500 (EST)
Date: Tue, 3 Nov 1998 09:15:55 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: Luoqi Chen <luoqi@watermarkgroup.com>
cc: dot@dotat.at, current@FreeBSD.ORG
Subject: Re: Linux clone()
In-Reply-To: <199811030332.WAA24322@lor.watermarkgroup.com>
Message-ID: <Pine.BSF.4.05.9811030911450.27548-100000@zone.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
Hmm.. AH! Now we're getting somewhere! I was planning to add that flag
mapping before I had a final version of the patch, and still am. Okay,
wonderful, I only get a stack pointer... I shouldn't fiddle with p2's eip
then, or should I set it to a copyin of the long function pointer from the
end of the stack... sorry, I never knew assembly :(
Brian Feldman
On Mon, 2 Nov 1998, Luoqi Chen wrote:
> > Hmmm.. okay this would be a good test. Right now I'm going thru the
> > various linuxthreads example programs.... The patch seems to be doing
> > something wrong, and I'm unable to figure out what to do, due to Linux's
> > humongously gross syscall system (so the kernel doesn't help me). It also
> > seems now I was implementing a LIBRARY function, which is just a wrapper.
> > If I could get my hands on what the real system calls' args are it would
> > be great.
> >
> > Brian Feldman
> >
> It seems that clone() the syscall takes two arguments:
> struct linux_clone_args {
> int flags;
> void *stack;
> };
> the wrapper in library takes care of pushing the function address and its
> argument on to the stack. You probably also want to map linux clone flags
> to that of rfork's: CLONE_FILES -> RFFDG, CLONE_VM -> RFMEM.
>
> -lq
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 06:23:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA13840
for freebsd-current-outgoing; Tue, 3 Nov 1998 06:23:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13835
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 06:23:33 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id JAA27875;
Tue, 3 Nov 1998 09:23:18 -0500 (EST)
Date: Tue, 3 Nov 1998 09:23:18 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: Luoqi Chen <luoqi@watermarkgroup.com>
cc: dot@dotat.at, current@FreeBSD.ORG
Subject: Re: Linux clone()
In-Reply-To: <199811030359.WAA24618@lor.watermarkgroup.com>
Message-ID: <Pine.BSF.4.05.9811030921570.27548-100000@zone.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'll be able to handle all this, don't worry :) Right now I'm just
figureing out how to pop the stuff off, if I should... I'll know in a few
ins.
Brian Feldman
On Mon, 2 Nov 1998, Luoqi Chen wrote:
> > > Hmmm.. okay this would be a good test. Right now I'm going thru the
> > > various linuxthreads example programs.... The patch seems to be doing
> > > something wrong, and I'm unable to figure out what to do, due to Linux's
> > > humongously gross syscall system (so the kernel doesn't help me). It also
> > > seems now I was implementing a LIBRARY function, which is just a wrapper.
> > > If I could get my hands on what the real system calls' args are it would
> > > be great.
> > >
> > > Brian Feldman
> > >
> > It seems that clone() the syscall takes two arguments:
> > struct linux_clone_args {
> > int flags;
> > void *stack;
> > };
> > the wrapper in library takes care of pushing the function address and its
> > argument on to the stack. You probably also want to map linux clone flags
> > to that of rfork's: CLONE_FILES -> RFFDG, CLONE_VM -> RFMEM.
> I made a mistake, it should be !CLONE_FILES -> RFFDG. And there's no rfork()
> counterpart for CLONE_SIGHAND, default rfork behavior corresponds to
> !CLONE_SIGHAND.
>
> -lq
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 06:30:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA14860
for freebsd-current-outgoing; Tue, 3 Nov 1998 06:30:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14851
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 06:30:14 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id JAA27908;
Tue, 3 Nov 1998 09:29:17 -0500 (EST)
Date: Tue, 3 Nov 1998 09:29:17 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: Peter Wemm <peter@netplex.com.au>
cc: John Hay <jhay@mikom.csir.co.za>, freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-Reply-To: <199811030521.NAA21942@spinner.netplex.com.au>
Message-ID: <Pine.BSF.4.05.9811030927260.27548-100000@zone.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
So should we take the VFS loading out of libc and add it to mount? Or
should there be a wrapper function in libc, getkldbyname (char *name) and
return "/modules/name.ko"?
Brian Feldman
On Tue, 3 Nov 1998, Peter Wemm wrote:
> Brian Feldman wrote:
> > Ahhhh, that's where it is! I have no good idea on how to allow, with this
> > code, lkm's and kld's to coexist.... so is it time to completely phase out
> > lkm's yet?
>
> I think the best way is to have mount(2) initiate a kldload if needed. We
> will need this functionality sooner or later. If mount(2) does it, we can
> garbage collect unused, unmounted filesystems after a while and unload
> them.
>
> > Brian Feldman
> >
> > On Mon, 2 Nov 1998, John Hay wrote:
> >
> > > > Be sure to let me know when ELF kernels can autoload kld modules like the
> > > > current a.out kernel does with lkm's.
> > >
> > > It's not the kernel that loads them. Go and look in lib/libc/gen/getvfsent.
> c
> > >
> > > John
> > > --
> > > John Hay -- John.Hay@mikom.csir.co.za
> > >
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-current" in the body of the message
> >
>
> 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
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 06:44:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA16006
for freebsd-current-outgoing; Tue, 3 Nov 1998 06:41:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15993
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 06:41:19 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id JAA28065;
Tue, 3 Nov 1998 09:40:40 -0500 (EST)
Date: Tue, 3 Nov 1998 09:40:40 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: Peter Wemm <peter@netplex.com.au>
cc: John Hay <jhay@mikom.csir.co.za>, freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel : replying to myself
In-Reply-To: <Pine.BSF.4.05.9811030927260.27548-100000@zone.syracuse.net>
Message-ID: <Pine.BSF.4.05.9811030937540.27548-100000@zone.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I am referring also that it would check to see if this file exists, and
return a malloced answer, else return NULL. This way it would be asy to
say something like
char *name;
if ((name = getkldbyname("mfs")) != NULL {
kldload(name);
free(name);
} else {
fprintf(stderr, "Could not load mfs.\n");
exit(1);
}
Brian Feldman
On Tue, 3 Nov 1998, Brian Feldman wrote:
> So should we take the VFS loading out of libc and add it to mount? Or
> should there be a wrapper function in libc, getkldbyname (char *name) and
> return "/modules/name.ko"?
>
> Brian Feldman
>
> On Tue, 3 Nov 1998, Peter Wemm wrote:
>
> > Brian Feldman wrote:
> > > Ahhhh, that's where it is! I have no good idea on how to allow, with this
> > > code, lkm's and kld's to coexist.... so is it time to completely phase out
> > > lkm's yet?
> >
> > I think the best way is to have mount(2) initiate a kldload if needed. We
> > will need this functionality sooner or later. If mount(2) does it, we can
> > garbage collect unused, unmounted filesystems after a while and unload
> > them.
> >
> > > Brian Feldman
> > >
> > > On Mon, 2 Nov 1998, John Hay wrote:
> > >
> > > > > Be sure to let me know when ELF kernels can autoload kld modules like the
> > > > > current a.out kernel does with lkm's.
> > > >
> > > > It's not the kernel that loads them. Go and look in lib/libc/gen/getvfsent.
> > c
> > > >
> > > > John
> > > > --
> > > > John Hay -- John.Hay@mikom.csir.co.za
> > > >
> > >
> > >
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-current" in the body of the message
> > >
> >
> > 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
> >
>
>
> 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 3 07: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 HAA19026
for freebsd-current-outgoing; Tue, 3 Nov 1998 07:07:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from www.scancall.no (www.scancall.no [195.139.183.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA19020
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 07:07:18 -0800 (PST)
(envelope-from Marius.Bendiksen@scancall.no)
Received: from super2.langesund.scancall.no [195.139.183.29]
by www with smtp
id JQZXKCMJ; Tue, 03 Nov 98 15:07:10 GMT
(PowerWeb version 4.04r6)
Message-Id: <3.0.5.32.19981103160708.00979100@mail.scancall.no>
X-Sender: Marius@mail.scancall.no
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Tue, 03 Nov 1998 16:07:08 +0100
To: "Kelvin Farmer" <erkaf@my-dejanews.com>, current@FreeBSD.ORG
From: Marius Bendiksen <Marius.Bendiksen@scancall.no>
Subject: Re: make kernel fails:booktree848.c
In-Reply-To: <HLNHMEEEIPNOHAAA@my-dejanews.com>
Mime-Version: 1.0
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 HAA19022
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Is there any particular reason why this works fine with -RELEASE?
.oO[¨ Marius Bendiksen ¨]Oo.
Dead girls don't say 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 3 07:16:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA19995
for freebsd-current-outgoing; Tue, 3 Nov 1998 07:16:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from www.scancall.no (www.scancall.no [195.139.183.5])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA19990
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 07:16:55 -0800 (PST)
(envelope-from Marius.Bendiksen@scancall.no)
Received: from super2.langesund.scancall.no [195.139.183.29]
by www with smtp
id JQZZQGBJ; Tue, 03 Nov 98 15:16:48 GMT
(PowerWeb version 4.04r6)
Message-Id: <3.0.5.32.19981103161646.0097a780@mail.scancall.no>
X-Sender: Marius@mail.scancall.no
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Tue, 03 Nov 1998 16:16:46 +0100
To: Mike Smith <mike@smith.net.au>,
Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
From: Marius Bendiksen <Marius.Bendiksen@scancall.no>
Subject: Re: New boot loader and alternate kernels
Cc: current@FreeBSD.ORG
In-Reply-To: <199811022258.OAA02025@dingo.cdrom.com>
References: <Your message of "Tue, 03 Nov 1998 09:35:43 +1100." <98Nov3.093515est.40322@border.alcanet.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>It will never fit in the "bootblocks". It's all we can do to locate a
>file in the filesystem and read it in. Before being too dim about
>this, bear in mind that no other operating system bootstrap manages to
>achieve this much with so little.
Quite true. Actually being able to locate a file in the file system is
pretty hard, especially with complex filesystems, as I suppose FFS most
likely is.
>There would be little trouble including the FICL Forth engine in the
>kernel; I had actually considered the not insubstantial advantages to
>doing this (most importantly the ability to attach Forth to modules to
>do specialised load/unload operations), but I suspect that this will be
>viewed too much like heresy by many people.
Anything that helps increase flexibility is good, if it doesn't bring
excessive bloat with it. From what I've heard so far, this would be a good
idea. Alternately, might it not be possible to add an option for it?
---
Marius Bendiksen, IT-Trainee, ScanCall AS <marius@scancall.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 3 07:34:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA22629
for freebsd-current-outgoing; Tue, 3 Nov 1998 07:34:06 -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 HAA22622
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 07:34:03 -0800 (PST)
(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA10104;
Tue, 3 Nov 1998 08:33:54 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id IAA09144; Tue, 3 Nov 1998 08:33:54 -0700
Date: Tue, 3 Nov 1998 08:33:54 -0700
Message-Id: <199811031533.IAA09144@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: brian@worldcontrol.com
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: PC Cards services without an IRQ?
In-Reply-To: <19981103052539.A3306@top.worldcontrol.com>
References: <19981103052539.A3306@top.worldcontrol.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I'm short IRQs on my laptop. Would it be feasible to have
> the pccard services manager not rely on having one for itself?
Sure.
> I'm suggesting that instead, when I change cards, I run a
> program so the system will rescan the cardbus.
The problem is not in the rescan, it's when you 'yank' them from the
system it can cause problems.
> Unless this is impossible, or already implemented in some way
> I have not discovered, I'd like to take a stab at implementing
> it.
Make sure it's not a kernel config option, and that there is a way for
it to be configured on a per-controller basis.
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 3 08:37:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA01200
for freebsd-current-outgoing; Tue, 3 Nov 1998 08:37:35 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fledge.watson.org (COPLAND.CODA.CS.CMU.EDU [128.2.222.48])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01194
for <current@freebsd.org>; Tue, 3 Nov 1998 08:37:31 -0800 (PST)
(envelope-from robert@cyrus.watson.org)
Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3])
by fledge.watson.org (8.8.8/8.8.8) with SMTP id LAA22488;
Tue, 3 Nov 1998 11:34:37 -0500 (EST)
Date: Tue, 3 Nov 1998 11:34:37 -0500 (EST)
From: Robert Watson <robert@cyrus.watson.org>
X-Sender: robert@fledge.watson.org
Reply-To: Robert Watson <robert+freebsd@cyrus.watson.org>
To: Doug Rabson <dfr@nlsystems.com>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, dg@root.com,
Jun-ichiro itojun Itoh <itojun@itojun.org>, obrien@NUXI.com,
Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, current@FreeBSD.ORG
Subject: Re: IPv6 in -current
In-Reply-To: <Pine.BSF.4.01.9811030946560.3018-100000@herring.nlsystems.com>
Message-ID: <Pine.BSF.3.96.981103112903.22463A-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 3 Nov 1998, Doug Rabson wrote:
> > > Yeah, if I had my druthers (and what the hell are "druthers" anyway,
> > > and who here has ever had any that they knew of? Why is English such
> > > a peculiar language? And why... Erm, excuse me, I guess that's not
> > > really important right now), I'd want to see the IPv6 bits integrated
> > > with the following provisos:
> >
> > English is a truly bizarre language. I'll dig up my OED this evening and
> > let you know :-P.
>
> Its some kind of bizarre contraction of 'would rather' I think.
So, finally having found an OED, here is some etymology:
1895 Dialect Notes I. 388 Bein's I caint have my druthers an' set still,
I cal 'late I'd better pearten up an' go 'long.
1896 'Mark Twain' Tom Sawyer, Detective ix. 74 'Any way you druther
have it, that is the way I druther have it. He' .' 'There ain't any
druthers about it, Huck Finn; nobody said anything about druthers.'
1941 W. A. Percy Lanterns on Levee (1948) xxii. 292 'Your ruthers is my
ruthers' (what you would rather is what I would rather). Certainly the most
amiable and appeasing phrase in any language, the language used being not
English but deep Southern.
This suggests, "I'd Rather". But it's a little hard to say. I wonder
whether we couldn't rename sysctl to druther.
druther -w net.inet.ip.forwarding=1
Maybe all followups should be sent to freebsd-chat. :)
Robert N Watson
Carnegie Mellon University http://www.cmu.edu/
TIS Labs at Network Associates, Inc. http://www.tis.com/
SafePort Network Services http://www.safeport.com/
robert@fledge.watson.org http://www.watson.org/~robert/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 08:52:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA03618
for freebsd-current-outgoing; Tue, 3 Nov 1998 08:52:40 -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 IAA03608
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 08:52:33 -0800 (PST)
(envelope-from ken@panzer.plutotech.com)
Received: (from ken@localhost)
by panzer.plutotech.com (8.9.1/8.8.5) id JAA11612;
Tue, 3 Nov 1998 09:52:01 -0700 (MST)
From: "Kenneth D. Merry" <ken@plutotech.com>
Message-Id: <199811031652.JAA11612@panzer.plutotech.com>
Subject: Re: AIC 6x60
In-Reply-To: <001101be0732$b6717280$4000000a@th-pc.traco.sk> from Tomas Hodan at "Nov 3, 98 03:03:20 pm"
To: tomas@hodan.sk
Date: Tue, 3 Nov 1998 09:52:01 -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
Tomas Hodan wrote...
> Hi all,
> it is any possibilit to use Adapec APA-1460 PCMCIA SCSI Adapter with 3.0 ?
>
> thanks
> tomas
>
> mouse:/sys/compile/MOUSE# make depend
> rm -f .newdep
> mkdep -a -f
> newdep -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-ext
> erns -Wstrict-prototypes -Wmissing-prototyc
> cc: ../../dev/aic6x60/aic.c: No such file or directory
> cc: ../../i386/isa/aic_isa.c: No such file or directory
The "aic" (aic6260/6360) driver hasn't been ported to CAM yet. Brian
Beattie <beattie@aracnet.com> is working on it, but I don't know how far
along he is on it.
For now, I'd suggest going with 2.2.7 or the -stable tree in general if you
want support for that card.
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 Tue Nov 3 08:56:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA04273
for freebsd-current-outgoing; Tue, 3 Nov 1998 08:56:04 -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 IAA04199
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 08:55: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 AAA24458;
Wed, 4 Nov 1998 00:53:52 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811031653.AAA24458@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman <green@zone.syracuse.net>
cc: John Hay <jhay@mikom.csir.co.za>, freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel : replying to myself
In-reply-to: Your message of "Tue, 03 Nov 1998 09:40:40 EST."
<Pine.BSF.4.05.9811030937540.27548-100000@zone.syracuse.net>
Date: Wed, 04 Nov 1998 00:53:51 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Feldman wrote:
> I am referring also that it would check to see if this file exists, and
> return a malloced answer, else return NULL. This way it would be asy to
> say something like
> char *name;
> if ((name = getkldbyname("mfs")) != NULL {
> kldload(name);
> free(name);
> } else {
> fprintf(stderr, "Could not load mfs.\n");
> exit(1);
> }
Well, it would have to parse the module path:
$ sysctl kern.module_path
kern.module_path: /;/boot/;/modules/
The kernel searches the path already, the best way to do the code above is:
if (kldload("mfs") == -1) {
fprintf(stderr, "Could not load mfs.\n");
exit(1);
}
.. but the kernel will already try this in mount(2) now. I have already
got one "What???" response about having just made mount do this, so I
guess we'll have to wait and see if this is going to stay.
> Brian Feldman
>
> On Tue, 3 Nov 1998, Brian Feldman wrote:
>
> > So should we take the VFS loading out of libc and add it to mount? Or
> > should there be a wrapper function in libc, getkldbyname (char *name) and
> > return "/modules/name.ko"?
> >
> > Brian Feldman
> >
> > On Tue, 3 Nov 1998, Peter Wemm wrote:
> >
> > > Brian Feldman wrote:
> > > > Ahhhh, that's where it is! I have no good idea on how to allow, with th
is
> > > > code, lkm's and kld's to coexist.... so is it time to completely phase
out
> > > > lkm's yet?
> > >
> > > I think the best way is to have mount(2) initiate a kldload if needed. W
e
> > > will need this functionality sooner or later. If mount(2) does it, we ca
n
> > > garbage collect unused, unmounted filesystems after a while and unload
> > > them.
> > >
> > > > Brian Feldman
> > > >
> > > > On Mon, 2 Nov 1998, John Hay wrote:
> > > >
> > > > > > Be sure to let me know when ELF kernels can autoload kld modules li
ke the
> > > > > > current a.out kernel does with lkm's.
> > > > >
> > > > > It's not the kernel that loads them. Go and look in lib/libc/gen/getv
fsent.
> > > c
> > > > >
> > > > > John
> > > > > --
> > > > > John Hay -- John.Hay@mikom.csir.co.za
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 3 09:13:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA06829
for freebsd-current-outgoing; Tue, 3 Nov 1998 09:13:52 -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 JAA06819
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 09:13:40 -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 BAA24549;
Wed, 4 Nov 1998 01:09:30 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811031709.BAA24549@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Chuck Robey <chuckr@mat.net>
cc: Brian Feldman <green@zone.syracuse.net>, John Hay <jhay@mikom.csir.co.za>,
freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-reply-to: Your message of "Tue, 03 Nov 1998 08:03:28 EST."
<Pine.BSF.4.05.9811030759560.300-100000@picnic.mat.net>
Date: Wed, 04 Nov 1998 01:09:29 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Chuck Robey wrote:
> On Tue, 3 Nov 1998, Peter Wemm wrote:
>
> > Brian Feldman wrote:
> > > Ahhhh, that's where it is! I have no good idea on how to allow, with this
> > > code, lkm's and kld's to coexist.... so is it time to completely phase ou
t
> > > lkm's yet?
> >
> > I think the best way is to have mount(2) initiate a kldload if needed. We
> > will need this functionality sooner or later. If mount(2) does it, we can
> > garbage collect unused, unmounted filesystems after a while and unload
> > them.
>
> Peter, you once told me that the new elf kernel has both aout and elf
> linkers in it. Does an elf kernel have the ability to load lkm modules,
> not the .ko things? If so, then the mount stuff is going to need to
> know which kind of module to hunt for, to load, right? Or, if they both
> work, maybe find both, and load the newest? With maybe a kld bias for a
> tiebreaker?
The in-kernel linkers can only load kld modules. LKM's are out, they
require too much userland support and are too limited because the symbol
table is not normally kept for incremental linking. kld modules very
closely resemble shared libraries, and the in-kernel linker resembles a
lightweight ld.so.
I believe that an ELF kernel can load an a.out kld module, but I have not
tested it - it has code to convert the symbol prefixes. I am not sure if
an a.out kernel can load an ELF kld module, I do not recall seeing code to
convert the symbols.. In any case, the safest thing to do is use a.out kld
modules on a.out kernels and ELF on ELF kernels.
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 3 09:15:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA07032
for freebsd-current-outgoing; Tue, 3 Nov 1998 09:15:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA07027
for <current@freebsd.org>; Tue, 3 Nov 1998 09:15:50 -0800 (PST)
(envelope-from alk@East.Sun.COM)
Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id JAA25838 for <current@freebsd.org>; Tue, 3 Nov 1998 09:15:42 -0800
Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3)
id MAA01113; Tue, 3 Nov 1998 12:15:37 -0500
Received: from east.sun.com (hobo33.Central.Sun.COM [129.147.8.33])
by suneast.East.Sun.COM (8.8.8+Sun/8.8.8) with ESMTP id MAA00141
for <current@freebsd.org>; Tue, 3 Nov 1998 12:14:50 -0500 (EST)
Received: (from alk@localhost) by east.sun.com (8.9.1/8.7.3) id LAA29122; Tue, 3 Nov 1998 11:13:29 -0600 (CST)
From: Tony Kimball <anthony.kimball@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 3 Nov 1998 11:13:19 -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: SMP with VESA sauce
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <13887.14710.412673.630140@avalon.east>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Has this brew been rendered non-poisonous? LINT still warns against
it, but I thought it worthwhile to check...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 09:28:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA09427
for freebsd-current-outgoing; Tue, 3 Nov 1998 09:28:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pinhead.parag.codegen.com (ppp-asfm10--073.sirius.net [205.134.242.73])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09419
for <current@freebsd.org>; Tue, 3 Nov 1998 09:28:45 -0800 (PST)
(envelope-from parag@pinhead.parag.codegen.com)
Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1])
by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id JAA06455
for <current@freebsd.org>; Tue, 3 Nov 1998 09:28:29 -0800 (PST)
(envelope-from parag@pinhead.parag.codegen.com)
Message-Id: <199811031728.JAA06455@pinhead.parag.codegen.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Tue, 03 Nov 1998 19:29:18 +1100."
<000601be0704$0cda76a0$6cb611cb@saruman.scitec.com.au>
X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X
]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm
X-URL: http://www.codegen.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 03 Nov 1998 09:28:29 -0800
From: Parag Patel <parag@cgt.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Another option occurred to me the other day: siod - a very small and
simple Scheme implementation. Well, it used to be quite a bit smaller.
Ripping out the bits useless for embedded systems (like most of
slibu.c) should help trim it down quite a bit. It used to be about
30-40k on most machines.
I guess it's a matter if you prefer postfix (Forth) or prefix (Lisp)
syntax. :-)
-- Parag
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 09: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 JAA11327
for freebsd-current-outgoing; Tue, 3 Nov 1998 09:43:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11317
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 09:43:09 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id MAA29898;
Tue, 3 Nov 1998 12:42:18 -0500 (EST)
Date: Tue, 3 Nov 1998 12:42:18 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: Peter Wemm <peter@netplex.com.au>
cc: John Hay <jhay@mikom.csir.co.za>, freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel : replying to myself
In-Reply-To: <199811031653.AAA24458@spinner.netplex.com.au>
Message-ID: <Pine.BSF.4.05.9811031241060.29837-100000@zone.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I am suggesting, rather, that a cleaner interface to it be made, and used,
in the hopes of simplification. And using /modules/*.ko, and kldload(2)..
Brian Feldman
On Wed, 4 Nov 1998, Peter Wemm wrote:
> Brian Feldman wrote:
> > I am referring also that it would check to see if this file exists, and
> > return a malloced answer, else return NULL. This way it would be asy to
> > say something like
> > char *name;
> > if ((name = getkldbyname("mfs")) != NULL {
> > kldload(name);
> > free(name);
> > } else {
> > fprintf(stderr, "Could not load mfs.\n");
> > exit(1);
> > }
>
> Well, it would have to parse the module path:
> $ sysctl kern.module_path
> kern.module_path: /;/boot/;/modules/
>
> The kernel searches the path already, the best way to do the code above is:
>
> if (kldload("mfs") == -1) {
> fprintf(stderr, "Could not load mfs.\n");
> exit(1);
> }
>
> .. but the kernel will already try this in mount(2) now. I have already
> got one "What???" response about having just made mount do this, so I
> guess we'll have to wait and see if this is going to stay.
>
> > Brian Feldman
> >
> > On Tue, 3 Nov 1998, Brian Feldman wrote:
> >
> > > So should we take the VFS loading out of libc and add it to mount? Or
> > > should there be a wrapper function in libc, getkldbyname (char *name) and
> > > return "/modules/name.ko"?
> > >
> > > Brian Feldman
> > >
> > > On Tue, 3 Nov 1998, Peter Wemm wrote:
> > >
> > > > Brian Feldman wrote:
> > > > > Ahhhh, that's where it is! I have no good idea on how to allow, with th
> is
> > > > > code, lkm's and kld's to coexist.... so is it time to completely phase
> out
> > > > > lkm's yet?
> > > >
> > > > I think the best way is to have mount(2) initiate a kldload if needed. W
> e
> > > > will need this functionality sooner or later. If mount(2) does it, we ca
> n
> > > > garbage collect unused, unmounted filesystems after a while and unload
> > > > them.
> > > >
> > > > > Brian Feldman
> > > > >
> > > > > On Mon, 2 Nov 1998, John Hay wrote:
> > > > >
> > > > > > > Be sure to let me know when ELF kernels can autoload kld modules li
> ke the
> > > > > > > current a.out kernel does with lkm's.
> > > > > >
> > > > > > It's not the kernel that loads them. Go and look in lib/libc/gen/getv
> fsent.
> > > > c
> > > > > >
> > > > > > John
> > > > > > --
> > > > > > John Hay -- John.Hay@mikom.csir.co.za
>
> 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 3 09:49:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12024
for freebsd-current-outgoing; Tue, 3 Nov 1998 09:49:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bfc.dk ([194.192.110.140])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA12019
for <freebsd-current@freebsd.org>; Tue, 3 Nov 1998 09:49:04 -0800 (PST)
(envelope-from npe@bfc.dk)
From: npe@bfc.dk
Received: by bfc.dk(Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) id 412566B1.00617E94 ; Tue, 3 Nov 1998 18:44:53 +0100
X-Lotus-FromDomain: BFC-DATA@BFC
To: freebsd-current@FreeBSD.ORG
Message-ID: <412566B1.0066887C.00@bfc.dk>
Date: Tue, 3 Nov 1998 19:45:58 +0100
Subject: Experiences with Compaq SMP machines ?
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I have the great honor to set up a Compaq 7000 4xXEON machine as a web
server.
But how stable will it be under FreeBSD 3 ?? (release/current?)
I'm looking for whatever info there is .. The problem is that it's a
temporary server. So I don't have it more than a couple of days before the
switch to online happens.
comments ?
Cheers,
Nicolai Petri
WM-data BFC - Denmark
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 09:52:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA12653
for freebsd-current-outgoing; Tue, 3 Nov 1998 09:52:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12642
for <current@freebsd.org>; Tue, 3 Nov 1998 09:52:45 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id MAA00131
for <current@freebsd.org>; Tue, 3 Nov 1998 12:52:35 -0500 (EST)
Date: Tue, 3 Nov 1998 12:52:35 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: current@FreeBSD.ORG
Subject: linux_clone news
Message-ID: <Pine.BSF.4.05.9811031248150.29837-100000@zone.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
Linux_clone() works! Or at least it seems to work correctly now. I have
a proper patchset now as well, attached at the end of this message. Bad
news: linuxthreads still does not work right. Altho I seem to have
corrected and redone the inaccurate parts of my code (thanks SO MUCH
Luoqi, you were really key in helping me here :), there seems to be some
kind of spinning pthread_create(). If anyone would like to apply my Linux
emulation patches, download LinuxThreads, and work on helping the state of
FreeBSD's Linux emulation out here, please do!
Cheers,
Brian Feldman
--cut here---patch begins---
diff -u usr/src/sys/i386/linux/linux_dummy.c
/usr/src/sys/i386/linux/linux_dummy.c
--- usr/src/sys/i386/linux/linux_dummy.c Thu Nov 6 14:28:52 1997
+++ /usr/src/sys/i386/linux/linux_dummy.c Mon Nov 2 20:40:16 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);
diff -u usr/src/sys/i386/linux/linux_misc.c
/usr/src/sys/i386/linux/linux_misc.c
--- usr/src/sys/i386/linux/linux_misc.c Mon Oct 5 08:40:42 1998
+++ /usr/src/sys/i386/linux/linux_misc.c Tue Nov 3 10:55:49 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>
@@ -557,6 +558,50 @@
return error;
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 DEBUG_CLONE
+ printf("linux_clone(%#x, %#x)\n", ((int *)args)[0],
+ ((int *)args)[1]);
+ if (args->flags & CLONE_PID)
+ printf("linux_clone: CLONE_PID not yet supported\n");
+ if (args->flags & CLONE_FS)
+ printf("linux_clone: CLONE_FS not yet supported\n");
+ if (args->flags & CLONE_SIGHAND)
+ printf("linux_clone: CLONE_SIGHAND not yet supported\n");
+#endif
+ if (args->flags & CLONE_VM)
+ ff |= RFMEM;
+ ff |= (args->flags & CLONE_FILES) ? RFFDG : RFCFDG;
+ 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;
+ }
+#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;
}
diff -u usr/src/sys/i386/linux/linux_proto.h
/usr/src/sys/i386/linux/linux_proto.h
--- usr/src/sys/i386/linux/linux_proto.h Fri Jul 10 18:30:04 1998
+++ /usr/src/sys/i386/linux/linux_proto.h Tue Nov 3 09:31:51 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 *)];
Only in usr/src/sys/i386/linux/: linux_proto.h.bak
diff -u usr/src/sys/i386/linux/linux_syscall.h
/usr/src/sys/i386/linux/linux_syscall.h
--- usr/src/sys/i386/linux/linux_syscall.h Fri Jul 10 18:30:06 1998
+++ /usr/src/sys/i386/linux/linux_syscall.h Tue Nov 3 09:31:51 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
Only in usr/src/sys/i386/linux/: linux_syscall.h.bak
diff -u usr/src/sys/i386/linux/linux_sysent.c
/usr/src/sys/i386/linux/linux_sysent.c
--- usr/src/sys/i386/linux/linux_sysent.c Fri Jul 10 18:30:07 1998
+++ /usr/src/sys/i386/linux/linux_sysent.c Tue Nov 3 09:31:51 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 */
Only in usr/src/sys/i386/linux/: linux_sysent.c.bak
diff -u usr/src/sys/i386/linux/syscalls.master
/usr/src/sys/i386/linux/syscalls.master
--- usr/src/sys/i386/linux/syscalls.master Fri Jul 10 18:30:08 1998
+++ /usr/src/sys/i386/linux/syscalls.master Tue Nov 3 09:31:44 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); }
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 09:56:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA13336
for freebsd-current-outgoing; Tue, 3 Nov 1998 09:56:52 -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 JAA13330
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 09:56:51 -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 JAA01226;
Tue, 3 Nov 1998 09:57:04 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: npe@bfc.dk
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Experiences with Compaq SMP machines ?
In-reply-to: Your message of "Tue, 03 Nov 1998 19:45:58 +0100."
<412566B1.0066887C.00@bfc.dk>
Date: Tue, 03 Nov 1998 09:57:04 -0800
Message-ID: <1221.910115824@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I have the great honor to set up a Compaq 7000 4xXEON machine as a web
> server.
> But how stable will it be under FreeBSD 3 ?? (release/current?)
Can't speak for the Compaq model, but having used one of the Intel
4xXEON systems with FreeBSD 3.0 I can say that it works pretty nicely.
- 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 3 11:11:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA23296
for freebsd-current-outgoing; Tue, 3 Nov 1998 11:11:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23282;
Tue, 3 Nov 1998 11:11:02 -0800 (PST)
(envelope-from thorpej@lestat.nas.nasa.gov)
Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id LAA25745; Tue, 3 Nov 1998 11:08:02 -0800 (PST)
Message-Id: <199811031908.LAA25745@lestat.nas.nasa.gov>
X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol
To: Ustimenko Semen <semen@iclub.nsu.ru>
Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG, current-users@netbsd.org
Subject: Re: SMC9432TX driver (tx) users
Reply-To: Jason Thorpe <thorpej@nas.nasa.gov>
From: Jason Thorpe <thorpej@nas.nasa.gov>
Date: Tue, 03 Nov 1998 11:08:02 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
[ I've added current-users@netbsd.org, because NetBSD users have seen
timeouts with the driver for the EPIC that I wrote, and I believe it
is a hardware problem... ]
On Tue, 3 Nov 1998 18:24:37 +0600 (NS)
Ustimenko Semen <semen@iclub.nsu.ru> wrote:
> If you use tx driver under FreeBSD, can you send me private
> message if you have ANY problems useing it.
>
> Even if the problem is only
> tx0: timeout %d packets, ...
With my 9432TX (in an AlphaStation 500 running NetBSD/alpha) I have seen
these device timeouts. Note, NetBSD's "epic" driver is NOT the same as
FreeBSD's "tx" driver; I wrote "epic" from scratch. However, I have NOT
been able to find the source of these timeouts. People have reported to
me that they are more common in 10Mbps mode, apparently. Sometimes the
card just wedges completely, and I have to reboot to get it to come back.
Sometimes, not even a reboot solves the problem.
There is an application note which describes a hardware bug, and a work
around for it. Here is the workaround from my "epic" driver:
/*
* Fixup the clock source on the EPIC.
*/
void
epic_fixup_clock_source(sc)
struct epic_softc *sc;
{
int i;
/*
* According to SMC Application Note 7-15, the EPIC's clock
* source is incorrect following a reset. This manifests itself
* as failure to recognize when host software has written to
* a register on the EPIC. The appnote recommends issuing at
* least 16 consecutive writes to the CLOCK TEST bit to correctly
* configure the clock source.
*/
for (i = 0; i < 16; i++)
bus_space_write_4(sc->sc_st, sc->sc_sh, EPIC_TEST,
TEST_CLOCKTEST);
}
This function is called in various places when we think the chip might
be catatonic. See src/sys/dev/ic/smc83c170.c in NetBSD-current.
This may not be the only problem the hardware has, or I may not be
fixing up the clock source in all the right places...
I would be VERY interested to know the FreeBSD experience with this
hardware, even given the completely different driver software being
used.
Thanks!
Jason R. Thorpe thorpej@nas.nasa.gov
NASA Ames Research Center Home: +1 408 866 1912
NAS: M/S 258-5 Work: +1 650 604 0935
Moffett Field, CA 94035 Pager: +1 650 940 5942
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 12:17:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA03559
for freebsd-current-outgoing; Tue, 3 Nov 1998 12:17:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03500
for <current@freebsd.org>; Tue, 3 Nov 1998 12:17:11 -0800 (PST)
(envelope-from gmarco@scotty.masternet.it)
Received: from suzy (modem29.masternet.it [194.184.65.39])
by scotty.masternet.it (8.8.8/8.8.8) with SMTP id VAA02799
for <current@freebsd.org>; Tue, 3 Nov 1998 21:14:19 +0100 (CET)
(envelope-from gmarco@scotty.masternet.it)
Message-Id: <199811032014.VAA02799@scotty.masternet.it>
From: "Gianmarco Giovannelli" <gmarco@scotty.masternet.it>
To: current@FreeBSD.ORG
Date: Tue, 3 Nov 1998 21:24:42 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: gensetdefs: not found (error code 1)
Reply-to: gmarco@giovannelli.it
X-mailer: Pegasus Mail for Win32 (v3.01b)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
It's about two days that the cvsup is not able to correct this make
world breakage...
===> sys/modules
===> sys/modules/atapi
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
echo "#define NWDC 2" > wdc.h
echo "#define ATAPI 1"> opt_atapi.h
cc -O -pipe -DATAPI_MODULE -DKERNEL -Wreturn-type -Wcomment -
Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -
Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -
Wformat -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -
I/usr/obj/elf/usr/src/sys/modules/atapi -
I/usr/obj/elf/usr/src/sys/modules/atapi/@ -
I/usr/obj/elf/usr/src/tmp/usr/include -c
/usr/src/sys/modules/atapi/../../i386/isa/atapi.c
gensetdefs atapi.o
gensetdefs: not found
*** Error code 1
I have cvsupped also about an hour ago... so I very -current ...
Have I miss something (like the bktr0 of the previous message :-) ?
Best Regards,
Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco)
"Unix expert since yesterday"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 12:47:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA07886
for freebsd-current-outgoing; Tue, 3 Nov 1998 12:47:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07875
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 12:47:17 -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 MAA00344;
Tue, 3 Nov 1998 12:46:12 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811032046.MAA00344@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Parag Patel <parag@cgt.com>
cc: current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Tue, 03 Nov 1998 09:28:29 PST."
<199811031728.JAA06455@pinhead.parag.codegen.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 03 Nov 1998 12:46:12 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> Another option occurred to me the other day: siod - a very small and
> simple Scheme implementation. Well, it used to be quite a bit smaller.
> Ripping out the bits useless for embedded systems (like most of
> slibu.c) should help trim it down quite a bit. It used to be about
> 30-40k on most machines.
>
> I guess it's a matter if you prefer postfix (Forth) or prefix (Lisp)
> syntax. :-)
bmake'd library can be downloaded from where?
--
\\ 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 3 12: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 MAA08095
for freebsd-current-outgoing; Tue, 3 Nov 1998 12:48:30 -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 MAA08090
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 12:48:29 -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 MAA00328;
Tue, 3 Nov 1998 12:44:57 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811032044.MAA00328@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: alk@pobox.com
cc: current@FreeBSD.ORG
Subject: Re: SMP with VESA sauce
In-reply-to: Your message of "Tue, 03 Nov 1998 11:13:19 CST."
<13887.14710.412673.630140@avalon.east>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 03 Nov 1998 12:44:56 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Has this brew been rendered non-poisonous? LINT still warns against
> it, but I thought it worthwhile to check...
I understand it's been passed as potable.
--
\\ 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 3 12:50:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA08297
for freebsd-current-outgoing; Tue, 3 Nov 1998 12:50:16 -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 MAA08290
for <freebsd-current@freebsd.org>; Tue, 3 Nov 1998 12:50:12 -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 0zanOi-0003DM-00; Tue, 3 Nov 1998 13:49:52 -0700
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id NAA23082; Tue, 3 Nov 1998 13:49:42 -0700 (MST)
Message-Id: <199811032049.NAA23082@harmony.village.org>
To: tomas@hodan.sk
Subject: Re: AIC 6x60
Cc: freebsd-current@FreeBSD.ORG
In-reply-to: Your message of "Tue, 03 Nov 1998 15:03:20 +0100."
<001101be0732$b6717280$4000000a@th-pc.traco.sk>
References: <001101be0732$b6717280$4000000a@th-pc.traco.sk>
Date: Tue, 03 Nov 1998 13:49:41 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In message <001101be0732$b6717280$4000000a@th-pc.traco.sk> "Tomas Hodan" writes:
: it is any possibilit to use Adapec APA-1460 PCMCIA SCSI Adapter with 3.0 ?
No. The driver hasn't been ported to CAM yet.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 12: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 MAA08360
for freebsd-current-outgoing; Tue, 3 Nov 1998 12:51:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from jumping-spider.aracnet.com (jumping-spider.aracnet.com [205.159.88.14])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08353
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 12:51:26 -0800 (PST)
(envelope-from beattie@aracnet.com)
Received: from shell2.aracnet.com (IDENT:1728@shell2.aracnet.com [205.159.88.20])
by jumping-spider.aracnet.com (8.9.1/8.9.0) with ESMTP id MAA00577;
Tue, 3 Nov 1998 12:51:16 -0800
Received: from localhost by shell2.aracnet.com (8.8.7) id MAA16177; Tue, 3 Nov 1998 12:51:15 -0800
Date: Tue, 3 Nov 1998 12:51:15 -0800 (PST)
From: Brian Beattie <beattie@aracnet.com>
To: "Kenneth D. Merry" <ken@plutotech.com>
cc: tomas@hodan.sk, freebsd-current@FreeBSD.ORG
Subject: Re: AIC 6x60
In-Reply-To: <199811031652.JAA11612@panzer.plutotech.com>
Message-ID: <Pine.LNX.3.96.981103123715.14947A-100000@shell2.aracnet.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, Kenneth D. Merry wrote:
> Tomas Hodan wrote...
> > Hi all,
> > it is any possibilit to use Adapec APA-1460 PCMCIA SCSI Adapter with 3.0 ?
>
> The "aic" (aic6260/6360) driver hasn't been ported to CAM yet. Brian
> Beattie <beattie@aracnet.com> is working on it, but I don't know how far
> along he is on it.
I have heard that Brian is currently trying to buy a house. For some
unknown reason this seems to be taking up much of his spare time. I do
believe he is still working on it though.
>
> For now, I'd suggest going with 2.2.7 or the -stable tree in general if you
> want support for that card.
This is unfortunately true for the time being.
Brian Beattie | If my corporate life has taught me anything,
beattie@aracnet.com | it was that running multi-million dollar
www.aracnet.com/~beattie | projects in no way implied managerial competence.
| Tony Porczyk ( in comp.unix.bsd.freebsd.misc )
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 13: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 NAA10851
for freebsd-current-outgoing; Tue, 3 Nov 1998 13:12:56 -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 NAA10840
for <current@freebsd.org>; Tue, 3 Nov 1998 13:12:48 -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 0zankS-0000Cn-00; Tue, 3 Nov 1998 21:12:21 +0000
Received: by WGP01 with Internet Mail Service (5.5.1960.3)
id <V08CSWFK>; Mon, 2 Nov 1998 20:01:59 -0000
Message-ID: <32BABEF63EAED111B2C5204C4F4F50201804@WGP01>
From: James Mansion <james@westongold.com>
To: Peter Wemm <peter@netplex.com.au>, Daniel Eischen <eischen@vigrid.com>
Cc: lists@tar.com, current@FreeBSD.ORG, jb@cimlogic.com.au
Subject: RE: Kernel threading (was Re: Thread Scheduler bug)
Date: Mon, 2 Nov 1998 20:01:50 -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
> From: Peter Wemm [mailto:peter@netplex.com.au]
> Sent: Sunday, November 01, 1998 3:30 PM
> ...
> - a "process" (struct proc) would have one or more threads,
> all using the
> same address space, pid, signals, etc.
> ...
I'd like to suggest that threads (at least kernel threads)
should share an address space EXCEPT for a page (or maybe
more than one) that will have a common address in each thread.
This is how OS/2 (at least) handles thread specific data,
and so far as I can tell it is potentially much cleaner
for TSD, including errno.
Any user-level multiplexing would need to save/restore this
data on task switch of course and a kernel-assist that changes
the memory map might be faster (or might not, dunno).
Can I ask (plead, really) for any effort in this area to
consider the support for inter-process synchronisation as well
as intra-process?
James
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 13:17:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA11443
for freebsd-current-outgoing; Tue, 3 Nov 1998 13:17:11 -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 NAA11432
for <current@freebsd.org>; Tue, 3 Nov 1998 13:17:08 -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 NAA00460
for <current@freebsd.org>; Tue, 3 Nov 1998 13:16:40 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811032116.NAA00460@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: current@FreeBSD.ORG
Subject: USERCONFIG_BOOT, heads up!
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 03 Nov 1998 13:16:39 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I've just committed a change which alters the way that scripts are
passed to userconfig.
Previously, you would specify USERCONFIG_BOOT in your kernel
configuration, and the bootstrap would load /kernename.config and pass
it to the kernel.
Now, to load a userconfig script you must be using the new 3-stage
bootloader. To load a script, either execute this command manually,
or insert it in /boot/boot.conf:
'load -t userconfig_script <scriptfile>'
The USERCONFIG_BOOT option is no longer used (or required).
--
\\ 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 3 13:19:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA11861
for freebsd-current-outgoing; Tue, 3 Nov 1998 13:19:34 -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 NAA11856
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 13:19:33 -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 NAA00471;
Tue, 3 Nov 1998 13:18:01 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811032118.NAA00471@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Marius Bendiksen <Marius.Bendiksen@scancall.no>
cc: Mike Smith <mike@smith.net.au>,
Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>, current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Tue, 03 Nov 1998 16:16:46 +0100."
<3.0.5.32.19981103161646.0097a780@mail.scancall.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 03 Nov 1998 13:18:01 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> >There would be little trouble including the FICL Forth engine in the
> >kernel; I had actually considered the not insubstantial advantages to
> >doing this (most importantly the ability to attach Forth to modules to
> >do specialised load/unload operations), but I suspect that this will be
> >viewed too much like heresy by many people.
>
> Anything that helps increase flexibility is good, if it doesn't bring
> excessive bloat with it. From what I've heard so far, this would be a good
> idea. Alternately, might it not be possible to add an option for it?
Making it optional would make it worthless; if it's to be useful for
anything it needs to be a standard component. I'm by no means sure
that it should.
--
\\ 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 3 13:30:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA13932
for freebsd-current-outgoing; Tue, 3 Nov 1998 13:30:45 -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 NAA13925
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 13:30:44 -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 NAA00500;
Tue, 3 Nov 1998 13:24:08 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811032124.NAA00500@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Chuck Robey <chuckr@mat.net>
cc: Peter Wemm <peter@netplex.com.au>, Brian Feldman <green@zone.syracuse.net>,
John Hay <jhay@mikom.csir.co.za>, freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-reply-to: Your message of "Tue, 03 Nov 1998 08:03:28 EST."
<Pine.BSF.4.05.9811030759560.300-100000@picnic.mat.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 03 Nov 1998 13:24:08 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On Tue, 3 Nov 1998, Peter Wemm wrote:
>
> > Brian Feldman wrote:
> > > Ahhhh, that's where it is! I have no good idea on how to allow, with this
> > > code, lkm's and kld's to coexist.... so is it time to completely phase out
> > > lkm's yet?
> >
> > I think the best way is to have mount(2) initiate a kldload if needed. We
> > will need this functionality sooner or later. If mount(2) does it, we can
> > garbage collect unused, unmounted filesystems after a while and unload
> > them.
>
> Peter, you once told me that the new elf kernel has both aout and elf
> linkers in it. Does an elf kernel have the ability to load lkm modules,
> not the .ko things? If so, then the mount stuff is going to need to
> know which kind of module to hunt for, to load, right? Or, if they both
> work, maybe find both, and load the newest? With maybe a kld bias for a
> tiebreaker?
Peter has already answered this pretty well; let me just clarify a few
things which will hopefully help understanding.
The old LKM model was somewhat ugly; it worked like this:
LKM's were built as relocatable objects. To load an LKM, you used the
a.linker to link the LKM object against the kernel file. The newly
relocated object was then copied into kernel space. This procedure was
dependant on having writable disk space (for the relocated object), the
a.out linker present, and could not be initiated from inside the kernel.
In contrast, the new (KLD) approach works like this:
A KLD module load is initiated by passing the pathname of the module to
the kernel. The kernel itself reads the object into memory, relocates
it at the new location, resolves any dependancies, connects SYSINITs,
etc. This can be done off a completely read-only filestore, and in
fact the kernel doesn't even have to read the modules in; they can be
placed in advance by the bootloader.
You could, theoretically, load both LKMs and KLD modules into an a.out
kernel. You can't do anything with LKMs that involves an ELF object,
either the LKM or the 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 Tue Nov 3 13:33:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA14195
for freebsd-current-outgoing; Tue, 3 Nov 1998 13:33:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14186
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 13:33:49 -0800 (PST)
(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
by pcnet1.pcnet.com (8.8.7/PCNet) id QAA22300;
Tue, 3 Nov 1998 16:33:32 -0500 (EST)
Date: Tue, 3 Nov 1998 16:33:32 -0500 (EST)
From: Daniel Eischen <eischen@vigrid.com>
Message-Id: <199811032133.QAA22300@pcnet1.pcnet.com>
To: eischen@vigrid.com, james@westongold.com, peter@netplex.com.au
Subject: RE: Kernel threading (was Re: Thread Scheduler bug)
Cc: current@FreeBSD.ORG, jb@cimlogic.com.au, lists@tar.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > From: Peter Wemm [mailto:peter@netplex.com.au]
> > Sent: Sunday, November 01, 1998 3:30 PM
> > ...
> > - a "process" (struct proc) would have one or more threads,
> > all using the
> > same address space, pid, signals, etc.
> > ...
>
> I'd like to suggest that threads (at least kernel threads)
> should share an address space EXCEPT for a page (or maybe
> more than one) that will have a common address in each thread.
What about same process threads executing on multiple processors?
common_address[MAX_CPUS] ?
> This is how OS/2 (at least) handles thread specific data,
> and so far as I can tell it is potentially much cleaner
> for TSD, including errno.
>
>
> Any user-level multiplexing would need to save/restore this
> data on task switch of course and a kernel-assist that changes
> the memory map might be faster (or might not, dunno).
>
> Can I ask (plead, really) for any effort in this area to
> consider the support for inter-process synchronisation as well
> as intra-process?
Dan Eischen
eischen@vigrid.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 3 13:34:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA14363
for freebsd-current-outgoing; Tue, 3 Nov 1998 13:34:43 -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 NAA14357
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 13:34:40 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.59.178])
by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA56F2; Tue, 3 Nov 1998 22:34:25 +0100
Message-ID: <XFMail.981103223809.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: <199811022041.MAA08533@austin.polstra.com>
Date: Tue, 03 Nov 1998 22:38:09 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: John Polstra <jdp@polstra.com>
Subject: Re: Another compile error
Cc: current@FreeBSD.ORG, Eivind Eklund <eivind@yes.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 02-Nov-98 John Polstra wrote:
>> I disagree. I think it would be very good if more people had their
>> sources in non-standard location, as it make it more likely that
>> somebody introducing a new location dependency get caught. Bruce
>> did a lot of work to eliminate all the dependencies on the location.
>
> That's fine advice for experienced FreeBSD developers. This poor
> fellow has already been through the mill just trying to get a make
> world to complete. The last thing we want for him is one more
> potential source of problems.
*chuckles*
Thanks for the concern guys =)
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Tue Nov 3 13:55:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA17698
for freebsd-current-outgoing; Tue, 3 Nov 1998 13:55:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17683
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 13:55:44 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.59.178])
by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA181B; Tue, 3 Nov 1998 22:55:25 +0100
Message-ID: <XFMail.981103225915.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: <199811021742.JAA07742@austin.polstra.com>
Date: Tue, 03 Nov 1998 22:59:15 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: John Polstra <jdp@polstra.com>
Subject: Re: Another compile error
Cc: current@FreeBSD.ORG, "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 02-Nov-98 John Polstra wrote:
>> Shall I write a newbie's point of view on cvsup then to contribute
>> to clearing things not that obvious?
>
> If you could distill the problems you encountered down to a few
> questions and answers for the CVSup FAQ, I'd find that very useful.
OK, what I can tell is this:
The technical background/FAQ is very good, although what's missing IMHO is
the lack of slightly advanced information. It's either WAAAAY technical or
too newbie. I mean, afaik the questions I have asked weren't that
newbie-like. (at least I hope not =)
Q. What does the average person want to cvsup?
A. The ports, docs and sources.
Q. What would be the best place for cvsup files?
A. /usr/src
Q. What would the average person use for cvsup mode?
A. checkout mode, to avoid all those cryptic ,v and Attic files ( ;) )
Q. To monitor the compilation/build process what would I use?
A. simply use commands like 2>&1, tee, and the likes.
Q. What exactly does 'make world' do?
A. executes make buildworld and make installworld
Q. OK, so what does make buildworld do?
A. ?
Q. And how about make installworld?
A. ?
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Tue Nov 3 14:13:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA21424
for freebsd-current-outgoing; Tue, 3 Nov 1998 14:13:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21416
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 14:13:44 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.59.178])
by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA1542 for <current@FreeBSD.ORG>;
Tue, 3 Nov 1998 22:13:36 +0100
Message-ID: <XFMail.981103231727.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: Tue, 03 Nov 1998 23:17:27 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: FreeBSD Current <current@FreeBSD.ORG>
Subject: cvsup server down?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
just to get this verified:
cvsup.internat.freebsd.org down for maintnance?
I keep getting connection refused's...
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Tue Nov 3 14:23:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23167
for freebsd-current-outgoing; Tue, 3 Nov 1998 14:23: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 OAA23162
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 14:23:43 -0800 (PST)
(envelope-from julian@whistle.com)
Received: (from daemon@localhost)
by alpo.whistle.com (8.8.5/8.8.5) id OAA09847;
Tue, 3 Nov 1998 14:07:20 -0800 (PST)
Received: from current1.whistle.com(207.76.205.22)
via SMTP by alpo.whistle.com, id smtpdnG9843; Tue Nov 3 22:07:09 1998
Date: Tue, 3 Nov 1998 14:06:45 -0800 (PST)
From: Julian Elischer <julian@whistle.com>
To: Daniel Eischen <eischen@vigrid.com>
cc: james@westongold.com, peter@netplex.com.au, current@FreeBSD.ORG,
jb@cimlogic.com.au, lists@tar.com
Subject: RE: Kernel threading (was Re: Thread Scheduler bug)
In-Reply-To: <199811032133.QAA22300@pcnet1.pcnet.com>
Message-ID: <Pine.BSF.3.95.981103135641.1112F-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
here's the trick..
the address space is presently a separate entity from the process
scheduling structures.
the two are linked by a single pointer really.
The address space structures have a reference count and
'threads' are implemented by simply making many scheduling entities
point to the same addres space structure..
if you make the threads have differnt pages, then either the addres space
needs to be 'munged' on each reschedule (where is the page swapped out to
since where it's swapped to depends on the object mapped into the address
space), or you need to have multiple different address spaces
sharing a lot of 'objects' which is a lot less efficient.
On Tue, 3 Nov 1998, Daniel Eischen wrote:
> > > From: Peter Wemm [mailto:peter@netplex.com.au]
> > > Sent: Sunday, November 01, 1998 3:30 PM
> > > ...
> > > - a "process" (struct proc) would have one or more threads,
> > > all using the
> > > same address space, pid, signals, etc.
> > > ...
> >
> > I'd like to suggest that threads (at least kernel threads)
> > should share an address space EXCEPT for a page (or maybe
> > more than one) that will have a common address in each thread.
easier to simply have a single pointer in a known address
that gets rewritten by the kernel on scheduling.. probably actually an
array of them, (one per cpu) with a 'getcpunumber()' to allow
the thread to work out which it should use.
in MACH they had several techniques..
one of which was used in the user-land threads, whuch was that each stack
was alligned on some boundary (e.g. 0x100000 byte alligned)
and the thread specific storage was always at (e.g. SP & 0xfff00000)
(or some similar thing).
>
> What about same process threads executing on multiple processors?
>
> common_address[MAX_CPUS] ?
>
> > This is how OS/2 (at least) handles thread specific data,
> > and so far as I can tell it is potentially much cleaner
> > for TSD, including errno.
> >
> >
> > Any user-level multiplexing would need to save/restore this
> > data on task switch of course and a kernel-assist that changes
> > the memory map might be faster (or might not, dunno).
> >
> > Can I ask (plead, really) for any effort in this area to
> > consider the support for inter-process synchronisation as well
> > as intra-process?
>
> Dan Eischen
> eischen@vigrid.com
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 14:38:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA25192
for freebsd-current-outgoing; Tue, 3 Nov 1998 14:38:55 -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 OAA25183
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 14:38:52 -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 XAA19065;
Tue, 3 Nov 1998 23:38:24 +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 UAA10957;
Tue, 3 Nov 1998 20:41:00 +0100 (MET)
(envelope-from w)
Message-ID: <19981103204058.A10945@panke.de.freebsd.org>
Date: Tue, 3 Nov 1998 20:40:59 +0100
From: Wolfram Schneider <wosch@panke.de.freebsd.org>
To: dg@root.com, "William S. Duncanson" <caesar@starkreality.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Err...something fishy going on in top.
References: <4.1.19981102235947.052f0100@fire.starkreality.com> <199811030905.BAA13428@implode.root.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <199811030905.BAA13428@implode.root.com>; from David Greenman on Tue, Nov 03, 1998 at 01:05:58AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 1998-11-03 01:05:58 -0800, David Greenman wrote:
> between depending on their priority. A change was made recently so that
> cached file pages are always put onto the inactive queue rather than just
> some of the time (they previously would also be put onto the cache queue).
> This actually improves performance because it keeps the pages better LRU
> sorted. When memory becomes short, the pagedaemon will move the pages to
> the cache queue (and then to the free queue) as needed. This will not
> significantly increase CPU usage and will increase overall system
> performance by a measurable amount.
Make world is now a little bit faster on my machine, from in average
95 min real time down to 93 min real time. user and system
time did not changed.
Wolfram
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 15:07:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA29364
for freebsd-current-outgoing; Tue, 3 Nov 1998 15:07:39 -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 PAA29357
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 15:07:37 -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 PAA02332;
Tue, 3 Nov 1998 15:07:35 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Mike Smith <mike@smith.net.au>
cc: Parag Patel <parag@cgt.com>, current@FreeBSD.ORG
Subject: Re: New boot loader and alternate kernels
In-reply-to: Your message of "Tue, 03 Nov 1998 12:46:12 PST."
<199811032046.MAA00344@dingo.cdrom.com>
Date: Tue, 03 Nov 1998 15:07:34 -0800
Message-ID: <2329.910134454@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> bmake'd library can be downloaded from where?
Erm, it's just one or two .c files. :-)
I'd forgotten about siod, but it is indeed very easy to integrate.
The earlier versions aren't even more than one .c file long.
- 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 3 15:08:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA29682
for freebsd-current-outgoing; Tue, 3 Nov 1998 15:08:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29651
for <current@freebsd.org>; Tue, 3 Nov 1998 15:08:53 -0800 (PST)
(envelope-from karpen@ocean.campus.luth.se)
Received: (from karpen@localhost)
by ocean.campus.luth.se (8.9.1/8.9.1) id AAA02645
for current@freebsd.org; Wed, 4 Nov 1998 00:03:25 +0100 (CET)
(envelope-from karpen)
From: Mikael Karpberg <karpen@ocean.campus.luth.se>
Message-Id: <199811032303.AAA02645@ocean.campus.luth.se>
Subject: config option VESA
To: current@FreeBSD.ORG
Date: Wed, 4 Nov 1998 00:03:25 +0100 (CET)
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
Hi!
After a bunch of "edit configfile, run config, make, install, reboot, repeat"
cycles I finally narrowed down a problem.
Take a GENERIC config file, add ``option "VM86"'' and config, make, install.
Reboot. Works fine. Add ``option VESA'' too. Repeat. Boots and crashes what
looks like just before starting the rc scripts. "Page not present" panic.
It says in LINT to not use VESA with SMP. But I have a UP Pentium.
Facts, if it makes any difference, this is what it has:
64MBmemory , 8MB WinFast 2300 gfxcard, Aw37 sndcard, ncr810 (I think it was).
Current as of Nov 1.
Is this a know problem?
I can provide more info... it's 100% repeatable, and I can crash it into
the debugger if needed, and give dumps, or whatever. But I can't cut'n'paste
there, so I'll avaoid that if it's not needed, Just ask and I'll hand copy it.
/Mikael
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 15:11:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA00478
for freebsd-current-outgoing; Tue, 3 Nov 1998 15:11:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from under.suspicion.org ([216.27.37.14])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00434
for <current@freebsd.org>; Tue, 3 Nov 1998 15:11:35 -0800 (PST)
(envelope-from ventrex@UNDER.suspicion.org)
Received: from UNDER.SUSPICION.ORG (root@UNDER.SUSPICION.ORG [216.27.37.14])
by under.suspicion.org (8.9.1/8.9.1) with ESMTP id SAA15369
for <current@freebsd.org>; Tue, 3 Nov 1998 18:11:20 -0500 (EST)
(envelope-from ventrex@UNDER.suspicion.org)
Date: Tue, 3 Nov 1998 18:11:16 -0500 (EST)
From: Thomas Stromberg <ventrex.freebsd@UNDER.suspicion.org>
X-Sender: ventrex@under.suspicion.org
To: current@FreeBSD.ORG
Subject: Hitting my pty limit of 256 with only 46 open?
Message-ID: <Pine.BSF.4.05.9811031804520.15264-100000@under.suspicion.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've got a private shellbox/workstation running 3.0-CURRENT. I'm not sure
why, but I keep hitting a pty limit, where no one can login/make new
screen sessions, etc. I've changed all the settings I know of to allow for
256 ptys to be open, but with no result.
Whenever I hit this limit, lsof reports I only have 44-46 of them in use:
[root(98NOV)]> lsof -n|grep -c pty
45
System:
FreeBSD under.suspicion.org 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Mon Nov 2
12:36:47 EST 1998
ventrex@under.suspicion.org:/vol/1/usr/src/sys/compile/blowntoad i386
But Here is the applicable kernel settings:
maxusers 128
options NMBCLUSTERS=8192
pseudo-device pty 256
/dev also has entries for pty:
[ventrex(98NOV)]> ls /dev/pty*|wc
256 256 2816
[ventrex(98NOV)]> ls /dev/tty*|wc
273 273 3009
I'm presuming that there is something I'm missing, but I havent yet been
able to figure it out. Any pointers/help would be much appreciated.
========================================================================
Thomas Stromberg | smtp -> thomas@stromberg.org
System Administrator, RTC Inc. | http -> thomas.stromberg.org
(919) 380-9771 ext. 3210 : talk -> ventrex@stromberg.org
"the more we know, the less we are" . irc -> ventrex@EFnet
========================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 15:21:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA02101
for freebsd-current-outgoing; Tue, 3 Nov 1998 15:21:38 -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 PAA02093
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 15:21:37 -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 PAA00900;
Tue, 3 Nov 1998 15:19:27 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811032319.PAA00900@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: Mike Smith <mike@smith.net.au>, Parag Patel <parag@cgt.com>,
current@FreeBSD.ORG
Subject: lisp vs. Forth (was Re: New boot loader and alternate kernels )
In-reply-to: Your message of "Tue, 03 Nov 1998 15:07:34 PST."
<2329.910134454@time.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 03 Nov 1998 15:19:27 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > bmake'd library can be downloaded from where?
>
> Erm, it's just one or two .c files. :-)
>
> I'd forgotten about siod, but it is indeed very easy to integrate.
> The earlier versions aren't even more than one .c file long.
About 75k according to:
http://www.cs.indiana.edu/scheme-repository/imp/siod.html
Anyone want to cut it "down to size" and see?
What's the feeling on the lisp vs. Forth argument?
--
\\ 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 3 15:41:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA04837
for freebsd-current-outgoing; Tue, 3 Nov 1998 15:41:28 -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 PAA04831
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 15:41:27 -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 PAA02612;
Tue, 3 Nov 1998 15:41:35 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Mike Smith <mike@smith.net.au>
cc: Parag Patel <parag@cgt.com>, current@FreeBSD.ORG
Subject: Re: lisp vs. Forth (was Re: New boot loader and alternate kernels )
In-reply-to: Your message of "Tue, 03 Nov 1998 15:19:27 PST."
<199811032319.PAA00900@dingo.cdrom.com>
Date: Tue, 03 Nov 1998 15:41:34 -0800
Message-ID: <2608.910136494@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> About 75k according to:
>
> http://www.cs.indiana.edu/scheme-repository/imp/siod.html
>
> Anyone want to cut it "down to size" and see?
I don't think you'd gain that much. Sure, you could snip out the Unix
programmer's functions and maybe some of the math stuff but then you'd
have to add back in some sort of I/O system for talking to the
keyboard, disk, and perhaps even various serial devices and that would
rapidly bloat things back up. Forth, on the other hand, has the
benefit of an I/O model so simplistic that it's (by design) not very
hard to just plug it straight into the relevant hardware. I worked on
a fig-forth system for the pc532 boot rom and talking straight to SCSI
devices and the serial ports from that system was a hell of a lot
easier than any 10 other solutions I might be able to think up.
> What's the feeling on the lisp vs. Forth argument?
lisp is cool, but I think perhaps a bit too weighty for a boot system
which is really only looking at the extention language as a way of
getting highly custom/conditional behavior for an incredibly small
number of applications which need it. Most users, I suspect, will
never even see a need to get much beyond the "boot" command. :-)
Lisp would be something I'd go more out of my way to implement if I
felt that people would be writing short scripts in it frequently, ala
the GIMP and its filter plug-ins or GNU emacs or, for that matter, a
game called Abuse. If you gotta write a fair amount of code, give me
lisp any day. If it's half a page of infrequent customization or
testing work, forth is equally godly. I'd put this particular task
more in the latter category.
- 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 3 17:05:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA18961
for freebsd-current-outgoing; Tue, 3 Nov 1998 17:05:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pinhead.parag.codegen.com (ppp-asfm10--087.sirius.net [205.134.242.87])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18952
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 17:05:50 -0800 (PST)
(envelope-from parag@pinhead.parag.codegen.com)
Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1])
by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id RAA07550;
Tue, 3 Nov 1998 17:05:42 -0800 (PST)
(envelope-from parag@pinhead.parag.codegen.com)
Message-Id: <199811040105.RAA07550@pinhead.parag.codegen.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mike Smith <mike@smith.net.au>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, current@FreeBSD.ORG
Subject: Re: lisp vs. Forth (was Re: New boot loader and alternate
kernels )
In-reply-to: Your message of "Tue, 03 Nov 1998 15:19:27 PST."
<199811032319.PAA00900@dingo.cdrom.com>
X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X
]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm
X-URL: http://www.codegen.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 03 Nov 1998 17:05:42 -0800
From: Parag Patel <parag@cgt.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>Anyone want to cut it "down to size" and see?
Here's the size from the much older v2.9 release just recompiled as ELF:
$ size siod *.o
text data bss dec hex filename
30065 444 3576 34085 8525 siod
246 0 0 246 f6 siod.o
17882 140 0 18022 4666 slib.o
8363 4 0 8367 20af sliba.o
1149 12 0 1161 489 trace.o
And for comparision, the latest v3.4:
$ size siod *.o
text data bss dec hex filename
83495 996 3660 88151 15857 siod
2229 64 0 2293 8f5 md5.o
1411 4 0 1415 587 sample.o
89 24 0 113 71 siod.o
28276 192 108 28576 6fa0 slib.o
25304 24 0 25328 62f0 sliba.o
18817 16 0 18833 4991 slibu.o
1299 16 0 1315 523 trace.o
I'd probably start with the v2.9 version for embedded use. If you
can't dig one up, I can put mine up on ftp.codegen.com.
As for Lisp vs Forth, Jordan covered it pretty well. If you're going
to do most of the work in C code and just want it callable from the
interpreter, either will work fine. Forth lets you get to more
low-level things, and if built as a byte-coded interpreter, can be
smaller, but Forth tends to be write-only in large quantities.
Personally, I guess I'd go with FOCAL or BCPL or TECO or some other
ancient language, just to keep it alive. :-)
The siod v3.4 README has this to say about where to get it:
The most recent version can usually be obtained from
the location http://people.delphi.com/gjc/siod.html or
ftp://ftp.std.com/pub/gjc/siod.tgz
There are probably other places to get it.
-- Parag
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 17:52:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA25023
for freebsd-current-outgoing; Tue, 3 Nov 1998 17:52:49 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from locnar.eng.mindspring.net (locnar.eng.mindspring.net [207.69.192.106])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25015
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 17:52:44 -0800 (PST)
(envelope-from sevn@mindspring.net)
Received: from localhost (localhost [127.0.0.1])
by locnar.eng.mindspring.net (8.9.1/8.9.1) with SMTP id UAA11853;
Tue, 3 Nov 1998 20:48:53 -0500 (EST)
(envelope-from sevn@mindspring.net)
Date: Tue, 3 Nov 1998 20:48:52 -0500 (EST)
From: Scott Wilson <sevn@mindspring.net>
X-Sender: sevn@locnar.eng.mindspring.net
To: Thomas Stromberg <ventrex.freebsd@UNDER.suspicion.org>
cc: current@FreeBSD.ORG
Subject: Re: Hitting my pty limit of 256 with only 46 open?
In-Reply-To: <Pine.BSF.4.05.9811031804520.15264-100000@under.suspicion.org>
Message-ID: <Pine.BSF.4.02A.9811032047560.10971-100000@locnar.eng.mindspring.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
There's plenty of stuff in /etc/login.conf that could be bitting you in
the ass on this one.
Scott
On Tue, 3 Nov 1998, Thomas Stromberg wrote:
> I've got a private shellbox/workstation running 3.0-CURRENT. I'm not sure
> why, but I keep hitting a pty limit, where no one can login/make new
> screen sessions, etc. I've changed all the settings I know of to allow for
> 256 ptys to be open, but with no result.
>
> Whenever I hit this limit, lsof reports I only have 44-46 of them in use:
> [root(98NOV)]> lsof -n|grep -c pty
> 45
>
> System:
> FreeBSD under.suspicion.org 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Mon Nov 2
> 12:36:47 EST 1998
> ventrex@under.suspicion.org:/vol/1/usr/src/sys/compile/blowntoad i386
>
>
> But Here is the applicable kernel settings:
> maxusers 128
> options NMBCLUSTERS=8192
> pseudo-device pty 256
>
>
> /dev also has entries for pty:
> [ventrex(98NOV)]> ls /dev/pty*|wc
> 256 256 2816
> [ventrex(98NOV)]> ls /dev/tty*|wc
> 273 273 3009
>
>
> I'm presuming that there is something I'm missing, but I havent yet been
> able to figure it out. Any pointers/help would be much appreciated.
>
>
> ========================================================================
> Thomas Stromberg | smtp -> thomas@stromberg.org
> System Administrator, RTC Inc. | http -> thomas.stromberg.org
> (919) 380-9771 ext. 3210 : talk -> ventrex@stromberg.org
> "the more we know, the less we are" . irc -> ventrex@EFnet
> ========================================================================
>
>
> 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 3 17:57:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA25467
for freebsd-current-outgoing; Tue, 3 Nov 1998 17:57:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from trouble.concentric.net (trouble.concentric.net [207.155.161.32])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA25455
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 17:57:35 -0800 (PST)
(envelope-from cbehrens@concentric.net)
Received: (qmail 16359 invoked by uid 5018); 4 Nov 1998 01:33:14 -0000
Date: Tue, 3 Nov 1998 17:33:14 -0800 (PST)
From: Chris Behrens <cbehrens@concentric.net>
Reply-To: Chris Behrens <cbehrens@concentric.net>
To: John Irwin <jdi@ninthwave.com>
cc: Manfred Antar <mantar@netcom.com>, current@FreeBSD.ORG
Subject: Re: DSL ?
In-Reply-To: <3638158C.9D253C0E@ninthwave.com>
Message-ID: <Pine.GSO.3.96.981103172739.7028L-100000@trouble.concentric.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, 28 Oct 1998, John Irwin wrote:
>
>
> Manfred Antar wrote:
>
> > Quick question
> > Does anybody have any experience using PacBell DSL with FreeBSD ?
>
> I've been using FreeBSD as my DSL firewall/NAT/web-server/mail-server
> since I got the DSL line installed. I chose Concentric over PacBell for
> an
> ISP -- their service has in general been fine.
>
> Ipfilter rewls.
Hey, what do you know...me too...of course, I work for Concentric. :)
With DSL, it shouldn't matter what OS you run or anything. You will
be given a DSL "router" which you can plug straight into an ethernet
card of a machine...or plug into a hub. I have this sort of setup:
DSL router -> freebsd with bridging patches -> hub -> other machines
^^^ being used as firewall
my "other machines" are many different OSes :)
- Chris
--
Chris Behrens
Senior Software Architect
Concentric Network Corporation
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 18:27:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA29236
for freebsd-current-outgoing; Tue, 3 Nov 1998 18:27:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from garman.dyn.ml.org (pm106-15.dialip.mich.net [192.195.231.217])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA29231
for <current@freebsd.org>; Tue, 3 Nov 1998 18:27:23 -0800 (PST)
(envelope-from garman@garman.dyn.ml.org)
Message-Id: <199811040227.SAA29231@hub.freebsd.org>
Received: (qmail 1297 invoked from smtpd); 4 Nov 1998 02:28:15 -0000
Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1)
by localhost.garman.net with SMTP; 4 Nov 1998 02:28:15 -0000
Date: Tue, 3 Nov 1998 21:28:14 -0500 (EST)
From: garman@earthling.net
Reply-To: garman@earthling.net
Subject: samba smbd core dumps & -current
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
i'm having problems with smbd coredumping on -current (as of a week ago
or so)... this has been happening for a while. i've upgraded to
samba1.9.18p10 to no avail.
it seems to happen whenever a user authenticates to it; guest access
seems to work okay. strange thing it is...
any tips? i haven't seen any discussion of this on here... same
configuration as before: pentiumII/300, aout system, 96MB of ram, no
problems with smbd before recent -current's.
if nobody else has seen this, i'll compile with debugging information
and attempt to track this thing down.
btw- the inetd patch has kept inetd from dying so far, thankfully. it
would have died by now without it.
enjoy
--
Jason Garman http://garman.dyn.ml.org/
Student, University of Maryland garman@earthling.net
And now... for the stupid-patent-of-the-week: Whois: JAG145
"...an attache case with destruct means for destroying the contents
therein in response to a signal" -- patent no. US3643609, filed in 1969
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 18:42:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA00882
for freebsd-current-outgoing; Tue, 3 Nov 1998 18:42:34 -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 SAA00876
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 18:42:33 -0800 (PST)
(envelope-from karl@Genesis.Denninger.Net)
Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id UAA07016; Tue, 3 Nov 1998 20:42:23 -0600 (CST)
Message-ID: <19981103204223.C6943@Denninger.Net>
Date: Tue, 3 Nov 1998 20:42:23 -0600
From: Karl Denninger <karl@Denninger.Net>
To: garman@earthling.net, current@FreeBSD.ORG
Subject: Re: samba smbd core dumps & -current
References: <199811040227.SAA29231@hub.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199811040227.SAA29231@hub.freebsd.org>; from garman@earthling.net on Tue, Nov 03, 1998 at 09:28:14PM -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
I have Samba running on -current and have not run into this - at al.
--
--
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.
On Tue, Nov 03, 1998 at 09:28:14PM -0500, garman@earthling.net wrote:
>
> i'm having problems with smbd coredumping on -current (as of a week ago
> or so)... this has been happening for a while. i've upgraded to
> samba1.9.18p10 to no avail.
>
> it seems to happen whenever a user authenticates to it; guest access
> seems to work okay. strange thing it is...
>
> any tips? i haven't seen any discussion of this on here... same
> configuration as before: pentiumII/300, aout system, 96MB of ram, no
> problems with smbd before recent -current's.
>
> if nobody else has seen this, i'll compile with debugging information
> and attempt to track this thing down.
>
> btw- the inetd patch has kept inetd from dying so far, thankfully. it
> would have died by now without it.
>
> enjoy
> --
> Jason Garman http://garman.dyn.ml.org/
> Student, University of Maryland garman@earthling.net
> And now... for the stupid-patent-of-the-week: Whois: JAG145
> "...an attache case with destruct means for destroying the contents
> therein in response to a signal" -- patent no. US3643609, filed in 1969
>
>
> 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 3 18:46:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA01157
for freebsd-current-outgoing; Tue, 3 Nov 1998 18:46:54 -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 SAA01148
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 18:46:48 -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 KAA27110;
Wed, 4 Nov 1998 10:45:23 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811040245.KAA27110@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman <green@zone.syracuse.net>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>,
Andrew Kenneth Milton <akm@zeus.theinternet.com.au>,
freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-reply-to: Your message of "Mon, 02 Nov 1998 11:41:22 EST."
<Pine.BSF.4.05.9811021140280.13943-100000@zone.syracuse.net>
Date: Wed, 04 Nov 1998 10:45:22 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Feldman wrote:
> Be sure to let me know when ELF kernels can autoload kld modules like the
> current a.out kernel does with lkm's.
It does now BTW..
However, libc gets in the way.. The mount_* commands look for the
requested vfs and want to call vfsload(). IMHO, this should go.
> Brian Feldman
>
> On Mon, 2 Nov 1998, Jordan K. Hubbard wrote:
>
> > > Is it possible to boot an ELF kernel?
> >
> > Ayup. You gotta have the new boot blocks installed and /boot/loader
> > installed from the /sys/boot srcs, then set KERNFORMAT=elf in
> > /etc/make.conf and you're on your way.
> >
> > - Jordan
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 3 19:02:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA02645
for freebsd-current-outgoing; Tue, 3 Nov 1998 19:02:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02640
for <freebsd-current@FreeBSD.ORG>; Tue, 3 Nov 1998 19:02:12 -0800 (PST)
(envelope-from green@zone.syracuse.net)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA05820;
Tue, 3 Nov 1998 21:56:21 -0500 (EST)
Date: Tue, 3 Nov 1998 21:56:21 -0500 (EST)
From: Brian Feldman <green@zone.syracuse.net>
To: Mike Smith <mike@smith.net.au>
cc: Chuck Robey <chuckr@mat.net>, Peter Wemm <peter@netplex.com.au>,
John Hay <jhay@mikom.csir.co.za>, freebsd-current@FreeBSD.ORG
Subject: Re: Booting Elf Kernel
In-Reply-To: <199811032124.NAA00500@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811032155120.5761-100000@zone.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
Not to be rude, but I did know this. I meant, tho, how a system to handle
both lkm's and kld's could exist (user-level, like mount(8) etc.). It
seems peter knows, according to his commits ;)
Cheers,
Brian Feldman
On Tue, 3 Nov 1998, Mike Smith wrote:
> > On Tue, 3 Nov 1998, Peter Wemm wrote:
> >
> > > Brian Feldman wrote:
> > > > Ahhhh, that's where it is! I have no good idea on how to allow, with this
> > > > code, lkm's and kld's to coexist.... so is it time to completely phase out
> > > > lkm's yet?
> > >
> > > I think the best way is to have mount(2) initiate a kldload if needed. We
> > > will need this functionality sooner or later. If mount(2) does it, we can
> > > garbage collect unused, unmounted filesystems after a while and unload
> > > them.
> >
> > Peter, you once told me that the new elf kernel has both aout and elf
> > linkers in it. Does an elf kernel have the ability to load lkm modules,
> > not the .ko things? If so, then the mount stuff is going to need to
> > know which kind of module to hunt for, to load, right? Or, if they both
> > work, maybe find both, and load the newest? With maybe a kld bias for a
> > tiebreaker?
>
> Peter has already answered this pretty well; let me just clarify a few
> things which will hopefully help understanding.
>
> The old LKM model was somewhat ugly; it worked like this:
>
> LKM's were built as relocatable objects. To load an LKM, you used the
> a.linker to link the LKM object against the kernel file. The newly
> relocated object was then copied into kernel space. This procedure was
> dependant on having writable disk space (for the relocated object), the
> a.out linker present, and could not be initiated from inside the kernel.
>
> In contrast, the new (KLD) approach works like this:
>
> A KLD module load is initiated by passing the pathname of the module to
> the kernel. The kernel itself reads the object into memory, relocates
> it at the new location, resolves any dependancies, connects SYSINITs,
> etc. This can be done off a completely read-only filestore, and in
> fact the kernel doesn't even have to read the modules in; they can be
> placed in advance by the bootloader.
>
> You could, theoretically, load both LKMs and KLD modules into an a.out
> kernel. You can't do anything with LKMs that involves an ELF object,
> either the LKM or the 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 Tue Nov 3 19:12:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA04092
for freebsd-current-outgoing; Tue, 3 Nov 1998 19:11:41 -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 TAA04084
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 19:11:30 -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 LAA27286;
Wed, 4 Nov 1998 11:10:56 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811040310.LAA27286@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman <green@zone.syracuse.net>
cc: current@FreeBSD.ORG
Subject: Re: linux_clone news
In-reply-to: Your message of "Tue, 03 Nov 1998 12:52:35 EST."
<Pine.BSF.4.05.9811031248150.29837-100000@zone.syracuse.net>
Date: Wed, 04 Nov 1998 11:10:56 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Feldman wrote:
> Linux_clone() works! Or at least it seems to work correctly now. I have
> a proper patchset now as well, attached at the end of this message. Bad
> news: linuxthreads still does not work right. Altho I seem to have
> corrected and redone the inaccurate parts of my code (thanks SO MUCH
> Luoqi, you were really key in helping me here :), there seems to be some
> kind of spinning pthread_create(). If anyone would like to apply my Linux
> emulation patches, download LinuxThreads, and work on helping the state of
> FreeBSD's Linux emulation out here, please do!
I think the bit that is going to bite you is the lack of support for
sharing the signal handlers. linuxthreads uses signals for internal
management from memory. With the emulated clone(), a child changing it's
signal handler will not change the global vectors, and things could get
upset.
It might be possible to implement a bit more glue in the rfork() code and
child management so that rfork children can set their p_sigacts to a common
shared vector. This would have to malloced rather than in the UPAGES
because the implications of a swapout of the leader would be devastating.
> Cheers,
> Brian Feldman
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 3 19:13:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA04225
for freebsd-current-outgoing; Tue, 3 Nov 1998 19:13:15 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA04213
for <current@freebsd.org>; Tue, 3 Nov 1998 19:13:05 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id WAA06095
for <current@freebsd.org>; Tue, 3 Nov 1998 22:12:48 -0500 (EST)
Date: Tue, 3 Nov 1998 22:12:47 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@zone.syracuse.net
To: current@FreeBSD.ORG
Subject: mount_msdos is dead :(
Message-ID: <Pine.BSF.4.05.9811032212030.5761-100000@zone.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'm attaching a script that shows this.
Brian Feldman
Script started on Tue Nov 3 22:07:44 1998
{"/home/green"}# mount_msdos /dev/fd0 /m^H ^Hfloppy^M^M
mount_msdos: /dev/fd0: Block device required^M
{"/home/green"}# ls -l /dev/fd0^M^M
brw------- 1 root operator 2, 0 Nov 3 20:47 /dev/fd0^M
{"/home/green"}# dd if=/dev/rfd0 of=flop^M^M
2880+0 records in^M
2880+0 records out^M
1474560 bytes transferred in 52.781845 secs (27937 bytes/sec)^M
{"/home/green"}# vnconfig -c /dev/vn0 /home/green/flop^M^M
{"/home/green"}# mount_msdos /dev/vn0 /floppy^M^M
mount_msdos: /dev/vn0: Block device required^M
{"/home/green"}# ls -l /dev/vn0^M^M
brw-r----- 1 root operator 15, 0x00010002 Jul 24 08:52 /dev/vn0^M
{"/home/green"}# ^D^M^M
Script done on Tue Nov 3 22:11:16 1998
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 19:16:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA04427
for freebsd-current-outgoing; Tue, 3 Nov 1998 19:16:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA04422
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 19:16:03 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id WAA06117;
Tue, 3 Nov 1998 22:15:40 -0500 (EST)
Date: Tue, 3 Nov 1998 22:15:40 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@zone.syracuse.net
To: Peter Wemm <peter@netplex.com.au>
cc: current@FreeBSD.ORG
Subject: Re: linux_clone news
In-Reply-To: <199811040310.LAA27286@spinner.netplex.com.au>
Message-ID: <Pine.BSF.4.05.9811032214310.5761-100000@zone.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I think that this patch should be committed for now, since it does add a
working system call.... okay, maybe not. I'll work on this signal things,
I've got linuxthreads code lying here to look at (lotsa junk with USR1 and
USR2 :(
Cheers,
Brian Feldman
On Wed, 4 Nov 1998, Peter Wemm wrote:
> Brian Feldman wrote:
> > Linux_clone() works! Or at least it seems to work correctly now. I have
> > a proper patchset now as well, attached at the end of this message. Bad
> > news: linuxthreads still does not work right. Altho I seem to have
> > corrected and redone the inaccurate parts of my code (thanks SO MUCH
> > Luoqi, you were really key in helping me here :), there seems to be some
> > kind of spinning pthread_create(). If anyone would like to apply my Linux
> > emulation patches, download LinuxThreads, and work on helping the state of
> > FreeBSD's Linux emulation out here, please do!
>
> I think the bit that is going to bite you is the lack of support for
> sharing the signal handlers. linuxthreads uses signals for internal
> management from memory. With the emulated clone(), a child changing it's
> signal handler will not change the global vectors, and things could get
> upset.
>
> It might be possible to implement a bit more glue in the rfork() code and
> child management so that rfork children can set their p_sigacts to a common
> shared vector. This would have to malloced rather than in the UPAGES
> because the implications of a swapout of the leader would be devastating.
>
> > Cheers,
> > Brian Feldman
>
> Cheers,
> -Peter
>
>
>
> 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 3 19:57:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA09423
for freebsd-current-outgoing; Tue, 3 Nov 1998 19:57:15 -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 TAA09418
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 19:57:12 -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 UAA13521;
Tue, 3 Nov 1998 20:57:03 -0700 (MST)
Received: from wdl1.wdl.lmco.com ([137.249.32.1]) by lmco.com (PMDF V5.1-10 #20543)
with SMTP id <0F1V00GZMPN3FG@lmco.com>; Tue, 3 Nov 1998 20:57:03 -0700 (MST)
Received: from lmco.com by wdl1.wdl.lmco.com (SMI-8.6/WDL-5.0) id TAA23276; Tue, 03 Nov 1998 19:56:56 -0800
Date: Tue, 03 Nov 1998 19:57:11 -0800
From: "George W. Dinolt" <george.w.dinolt@lmco.com>
Subject: Re: mount_msdos is dead :(
To: Brian Feldman <green@unixhelp.org>
Cc: current@FreeBSD.ORG
Message-id: <363FD097.F2336E50@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: <Pine.BSF.4.05.9811032212030.5761-100000@zone.syracuse.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I
Brian Feldman wrote:
> I'm attaching a script that shows this.
>
> Brian Feldman
>
> Script started on Tue Nov 3 22:07:44 1998
> {"/home/green"}# mount_msdos /dev/fd0 /m^H ^Hfloppy^M^M
> mount_msdos: /dev/fd0: Block device required^M
> {"/home/green"}# ls -l /dev/fd0^M^M
> brw------- 1 root operator 2, 0 Nov 3 20:47 /dev/fd0^M
> {"/home/green"}# dd if=/dev/rfd0 of=flop^M^M
> 2880+0 records in^M
> 2880+0 records out^M
> 1474560 bytes transferred in 52.781845 secs (27937 bytes/sec)^M
> {"/home/green"}# vnconfig -c /dev/vn0 /home/green/flop^M^M
> {"/home/green"}# mount_msdos /dev/vn0 /floppy^M^M
> mount_msdos: /dev/vn0: Block device required^M
> {"/home/green"}# ls -l /dev/vn0^M^M
> brw-r----- 1 root operator 15, 0x00010002 Jul 24 08:52 /dev/vn0^M
> {"/home/green"}# ^D^M^M
>
> Script done on Tue Nov 3 22:11:16 1998
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
I ran into similar problems several days ago after some large changes to
the kernel were committed. I think that if you rebuild your lkm modules
so they match the kernel you are running things will work. At least they
did for me. I haven't tried an elf kernel for a while, but I suspect the
same would happen if the '.ko' modules were not in sync with the kernel.
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 Tue Nov 3 21:35:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA21452
for freebsd-current-outgoing; Tue, 3 Nov 1998 21:35:07 -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 VAA21442
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 21:35:01 -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 QAA01741;
Wed, 4 Nov 1998 16:04:12 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.1/8.9.0) id QAA03255;
Wed, 4 Nov 1998 16:04:12 +1030 (CST)
Message-ID: <19981104160411.S784@freebie.lemis.com>
Date: Wed, 4 Nov 1998 16:04:11 +1030
From: Greg Lehey <grog@lemis.com>
To: Mike Smith <mike@smith.net.au>, "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: Parag Patel <parag@cgt.com>, current@FreeBSD.ORG
Subject: Re: lisp vs. Forth (was Re: New boot loader and alternate kernels )
References: <2329.910134454@time.cdrom.com> <199811032319.PAA00900@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199811032319.PAA00900@dingo.cdrom.com>; from Mike Smith on Tue, Nov 03, 1998 at 03:19:27PM -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, 3 November 1998 at 15:19:27 -0800, Mike Smith wrote:
>>> bmake'd library can be downloaded from where?
>>
>> Erm, it's just one or two .c files. :-)
>>
>> I'd forgotten about siod, but it is indeed very easy to integrate.
>> The earlier versions aren't even more than one .c file long.
>
> About 75k according to:
>
> http://www.cs.indiana.edu/scheme-repository/imp/siod.html
>
> Anyone want to cut it "down to size" and see?
I'm playing with it instead of doing my real work. Don't hold your
breath.
> What's the feeling on the lisp vs. Forth argument?
I think jkh put it well: I prefer LISP, but for what we're doing here
it may be overkill (for that matter, so may Forth, but it's less
overkill than LISP).
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 3 21:36:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA21716
for freebsd-current-outgoing; Tue, 3 Nov 1998 21:36:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from chaotic.oz.org (chaotic.oz.org [203.20.237.203])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21686
for <current@freebsd.org>; Tue, 3 Nov 1998 21:36:30 -0800 (PST)
(envelope-from simon@oz.org)
Received: from localhost (localhost [127.0.0.1])
by chaotic.oz.org (8.9.1/8.8.8) with SMTP id PAA14821
for <current@freebsd.org>; Wed, 4 Nov 1998 15:36:15 +1000 (EST)
(envelope-from simon@oz.org)
Date: Wed, 4 Nov 1998 15:36:15 +1000 (EST)
From: Simon Coggins <simon@oz.org>
Reply-To: chaos@ultra.net.au
To: current@FreeBSD.ORG
Subject: Problems with make aout-to-elf-buld
Message-ID: <Pine.BSF.4.02.9811041534490.14808-100000@chaotic.oz.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Heya
While trying to do a make aout-to-elf-build I'm getting this error:
===> sys/modules/atapi
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
echo "#define NWDC 2" > wdc.h
echo "#define ATAPI 1"> opt_atapi.h
cc -O -pipe -DATAPI_MODULE -DKERNEL -Wreturn-type -Wcomment
-Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat
-fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/elf/usr/src/sys/modules/atapi
-I/usr/obj/elf/usr/src/sys/modules/atapi/@ -I/usr/obj/elf/usr/src/tmp/usr/include -c
/usr/src/sys/modules/atapi/../../i386/isa/atapi.c
gensetdefs atapi.o
gensetdefs: not found
*** Error code 1
Any ideas?
Regards
Simon
---
+---------------------------------------------------------------+
| Email: chaos@ultra.net.au, chaos@oz.org, simon@bofh.com.au |
| http://www.ultra.net.au/~chaos Simon.Coggins@jcu.edu.au. |
| Chaos on IRC, IRC Operator for the OzORG Network |
+---------------------------------------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 21:41:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA22534
for freebsd-current-outgoing; Tue, 3 Nov 1998 21:41:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22529
for <current@freebsd.org>; Tue, 3 Nov 1998 21:41:34 -0800 (PST)
(envelope-from jdp@austin.polstra.com)
Received: from austin.polstra.com (jdp@localhost)
by austin.polstra.com (8.9.1/8.9.1) with ESMTP id VAA18498;
Tue, 3 Nov 1998 21:41:25 -0800 (PST)
(envelope-from jdp)
Message-Id: <199811040541.VAA18498@austin.polstra.com>
To: ryany@pobox.com
Subject: Re: Current 'make world' warnings cleanup
In-Reply-To: <199811030323.WAA25340@cheshire.dynip.com>
References: <199811030323.WAA25340@cheshire.dynip.com>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Date: Tue, 03 Nov 1998 21:41:24 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <199811030323.WAA25340@cheshire.dynip.com>,
Ryan Younce <ryany@pobox.com> wrote:
> I'm not 100% certain if this is the right place to be asking this, but:
> I noticed on the FreeBSD projects page that running a make world with extra
> warnings enabled, and then clean up the warnings, although not a high priority
> project, would be a good thing to do.
>
> Well, seeing as how my count of all instances of ' warning: ' within my log
> of my most recent make world totals to about 85,000 lines, I figure this
> might be as good a place as any to burn my weekend/weeknight time.
Sounds good. Just one thing: don't fall prey to the temptation to
fix all the pointer mismatch warnings by blindly inserting casts just
to make the compiler shut up. That's a common mistake, and as often
as not it simply hides the real problem from the compiler rather than
fixing it.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 22:05:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA25501
for freebsd-current-outgoing; Tue, 3 Nov 1998 22:05:30 -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 WAA25496
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 22:05:23 -0800 (PST)
(envelope-from mark@grondar.za)
Received: from grondar.za (localhost [127.0.0.1])
by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA23594;
Wed, 4 Nov 1998 08:05:03 +0200 (SAST)
(envelope-from mark@grondar.za)
Message-Id: <199811040605.IAA23594@gratis.grondar.za>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: cvsup server down?
In-Reply-To: Your message of " Tue, 03 Nov 1998 23:17:27 +0100." <XFMail.981103231727.asmodai@wxs.nl>
References: <XFMail.981103231727.asmodai@wxs.nl>
Date: Wed, 04 Nov 1998 08:05:02 +0200
From: Mark Murray <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Jeroen Ruigrok/Asmodai wrote:
> Hi,
>
> just to get this verified:
>
> cvsup.internat.freebsd.org down for maintnance?
Keep trying, and also try cvsup2.internet.freebsd.org; these are busy
machines.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 22:12:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA26569
for freebsd-current-outgoing; Tue, 3 Nov 1998 22:12:09 -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 WAA26564
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 22:12:05 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA22223; Tue, 3 Nov 1998 22:11:55 -0800 (PST)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
id sma022219; Tue Nov 3 22:11:34 1998
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA20667; Tue, 3 Nov 1998 22:11:34 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199811040611.WAA20667@bubba.whistle.com>
Subject: Re: Current 'make world' warnings cleanup
In-Reply-To: <199811040541.VAA18498@austin.polstra.com> from John Polstra at "Nov 3, 98 09:41:24 pm"
To: jdp@polstra.com (John Polstra)
Date: Tue, 3 Nov 1998 22:11:34 -0800 (PST)
Cc: ryany@pobox.com, 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
John Polstra writes:
> > I'm not 100% certain if this is the right place to be asking this, but:
> > I noticed on the FreeBSD projects page that running a make world with extra
> > warnings enabled, and then clean up the warnings, although not a high priority
> > project, would be a good thing to do.
> >
> > Well, seeing as how my count of all instances of ' warning: ' within my log
> > of my most recent make world totals to about 85,000 lines, I figure this
> > might be as good a place as any to burn my weekend/weeknight time.
>
> Sounds good. Just one thing: don't fall prey to the temptation to
> fix all the pointer mismatch warnings by blindly inserting casts just
> to make the compiler shut up. That's a common mistake, and as often
> as not it simply hides the real problem from the compiler rather than
> fixing it.
Another gotcha when doing this.. often "unused variable" warnings
happen because there is a variable declared that is only used
when certain #ifdef's are true. The solution in these cases is
not to remove the variable, but to enclose it's declaration
within equivalent #ifdef's..
-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 3 22:55:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA02375
for freebsd-current-outgoing; Tue, 3 Nov 1998 22:55:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from owl.org (owl.org [198.206.215.91])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02351;
Tue, 3 Nov 1998 22:55:14 -0800 (PST)
(envelope-from cgull@owl.org)
Received: (from cgull@localhost)
by owl.org (8.9.1/8.9.1/cgull) id BAA08977;
Wed, 4 Nov 1998 01:54:47 -0500 (EST)
Message-ID: <19981104015447.11838@owl.org>
Date: Wed, 4 Nov 1998 01:54:47 -0500
From: john hood <cgull@owl.org>
To: wosch@FreeBSD.ORG
Cc: current@FreeBSD.ORG, wosch@FreeBSD.ORG, mike@smith.net.au
Subject: Re: Missing IDE CD-ROM after 3.0 upgrade
References: <19981101214725.A3577@panke.de.freebsd.org> <199811020825.AAA08974@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1
In-Reply-To: <199811020825.AAA08974@dingo.cdrom.com>; from Mike Smith on Mon, Nov 02, 1998 at 12:25:04AM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Mon, Nov 02, 1998 at 12:25:04AM -0800, Mike Smith wrote:
> > On 1998-10-25 18:38:09 +0100, Wolfram Schneider wrote:
> > > I just updated from 2.2.6R to 3.0. The new 3.0 kernel
> > > does not find the CD-ROM anymore ;-(
> >
> > I tracked down the problem to a patch in Sep 1997. Before
> > the patch my IDE CD-ROM was detected by the kernel. After the
> > commit not ... Any change to fix this?
>
> Er, no idea. You may have to break this down into several components
> to work out which one(s) break you. I'd have to guess it was the
> Promise controller changes. Then we'd need to work out a compromise
> fix.
Erm, there's problems with the way the code remembers its probes of
both PCI controllers and drives, and given the right combinations, it
won't see them or the drive doesn't work. The data structures in
there are a mess and I misused them in a couple of places. And no,
the Promise code isn't specifically responsible, it's just a
participant in the general lossage. :) I can't remember the exact
sequences of controllers and drives that caused these problems to rear
up, but try rearranging drives on the controllers. :(.
I've got code that fixes that problem, but it causes all sorts of new
problems with the Promise controller I recently got and have been
beating on (the problems seem to be related to the shared &
level-triggered interrupt for primary and secondary controllers on the
Promise), and Soren tells me they've also manage to hang his computer
a couple of times and severely eat his filesystems once. Sigh. I'll
work on it some more.
If rearranging things doesn't work, and you aren't using a Promise
controller, and you feel like living a little dangerously (at least
according to Soren), then I can pass the current patches along to you
and you can try them out.
--jh
--
Mr. Belliveau said, "the difference was the wise, John Hood, cgull
intelligent look on the face of the cow." He was @
*so* right. --Ofer Inbar owl.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 3 23:08:08 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA04477
for freebsd-current-outgoing; Tue, 3 Nov 1998 23:08:08 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04468
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 23:08:02 -0800 (PST)
(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id IAA18195
for current@FreeBSD.ORG; Wed, 4 Nov 1998 08:07:50 +0100 (CET)
(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (VMailer, from userid 101)
id 97B871513; Wed, 4 Nov 1998 08:03:04 +0100 (CET)
Date: Wed, 4 Nov 1998 08:03:04 +0100
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: current@FreeBSD.ORG
Subject: Re: config option VESA
Message-ID: <19981104080304.A5272@keltia.freenix.fr>
Mail-Followup-To: current@FreeBSD.ORG
References: <199811032303.AAA02645@ocean.campus.luth.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.4i
In-Reply-To: <199811032303.AAA02645@ocean.campus.luth.se>; from Mikael Karpberg on Wed, Nov 04, 1998 at 12:03:25AM +0100
X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4772 AMD-K6 MMX @ 200 MHz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
According to Mikael Karpberg:
> I can provide more info... it's 100% repeatable, and I can crash it into
> the debugger if needed, and give dumps, or whatever. But I can't
> cut'n'paste there, so I'll avaoid that if it's not needed, Just ask and
> I'll hand copy it.
But in my PPro/200 it is working fine with both options.
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-BETA #4: Thu Oct 15 01:36:57 CEST 1998
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 23: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 XAA06273
for freebsd-current-outgoing; Tue, 3 Nov 1998 23:18:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06248;
Tue, 3 Nov 1998 23:18:35 -0800 (PST)
(envelope-from semen@iclub.nsu.ru)
Received: from localhost (semen@localhost)
by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id NAA14688;
Wed, 4 Nov 1998 13:15:30 +0600 (NS)
Date: Wed, 4 Nov 1998 13:15:29 +0600 (NS)
From: Ustimenko Semen <semen@iclub.nsu.ru>
To: Jason Thorpe <thorpej@nas.nasa.gov>
cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG, current-users@netbsd.org
Subject: Re: SMC9432TX driver (tx) users
In-Reply-To: <199811031908.LAA25745@lestat.nas.nasa.gov>
Message-ID: <Pine.BSF.3.96.981104123906.13573B-100000@iclub.nsu.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, 3 Nov 1998, Jason Thorpe wrote:
> [ I've added current-users@netbsd.org, because NetBSD users have seen
> timeouts with the driver for the EPIC that I wrote, and I believe it
> is a hardware problem... ]
>
> With my 9432TX (in an AlphaStation 500 running NetBSD/alpha) I have seen
> these device timeouts. Note, NetBSD's "epic" driver is NOT the same as
> FreeBSD's "tx" driver; I wrote "epic" from scratch. However, I have NOT
> been able to find the source of these timeouts. People have reported to
> me that they are more common in 10Mbps mode, apparently. Sometimes the
> card just wedges completely, and I have to reboot to get it to come back.
> Sometimes, not even a reboot solves the problem.
Not long time ago, there was a problem with card. It hangs just after
initialization, on first outgoing packet. I have added check of
link status before queueing packets, and the problem (i hope) has
disappeared.
The problems often appear at slow computers (like 486-DX4 (100)) at
100Mbps under heavy load, like ping -f -s 65000 ... from some quicker
station. Internal buffer and rx ring overflow, sometimes following
with card shutup. Usually fixed with ifconfig tx0 down up.
If only we can make driver spend less time in interrupt...
But at least we need to recopy received packet or allocate place
for new one.
> There is an application note which describes a hardware bug, and a work
> around for it. Here is the workaround from my "epic" driver:
> ...
>
Application Note says that we need to set clock source only
at initialization... Thank you for pointing me on it, this
may be better solution that link checkup before transmition.
> I would be VERY interested to know the FreeBSD experience with this
> hardware, even given the completely different driver software being
> used.
They said that this card works fine both at 10 and 100 Mbps.
Even without timeouts. But sometimes it fails to autoselect
10Mbps modes, sometimes to force card to 10Mbps mode. I think
this is the bug(s) in PHY used (QS6612, have You seen another?).
I'll ask OpenBSD users too.
Thenk you.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Tue Nov 3 23:46:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA11274
for freebsd-current-outgoing; Tue, 3 Nov 1998 23:46:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11268
for <current@FreeBSD.ORG>; Tue, 3 Nov 1998 23:46:43 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.59.98]) by smtp01.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAA459F;
Wed, 4 Nov 1998 08:46:33 +0100
Message-ID: <XFMail.981104085028.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: <199811040605.IAA23594@gratis.grondar.za>
Date: Wed, 04 Nov 1998 08:50:28 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Mark Murray <mark@grondar.za>
Subject: Re: cvsup server down?
Cc: FreeBSD Current <current@FreeBSD.ORG>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 04-Nov-98 Mark Murray wrote:
> Jeroen Ruigrok/Asmodai wrote:
>> Hi,
>>
>> just to get this verified:
>>
>> cvsup.internat.freebsd.org down for maintnance?
>
> Keep trying, and also try cvsup2.internet.freebsd.org; these are busy
> machines.
Thanks Mark,
I just got worried since I got no pings back and it never failed on me
before...
working right now, so I'll shut up now =)
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Tue Nov 3 23: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 XAA12301
for freebsd-current-outgoing; Tue, 3 Nov 1998 23:53:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12293
for <current@freebsd.org>; Tue, 3 Nov 1998 23:53:38 -0800 (PST)
(envelope-from shocking@ariadne.prth.tensor.pgs.com)
Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36])
by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id PAA24300
for <current@freebsd.org>; Wed, 4 Nov 1998 15:53:28 +0800 (WST)
Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4)
id PAA08326; Wed, 4 Nov 1998 15:53:28 +0800
Message-Id: <199811040753.PAA08326@ariadne.tensor.pgs.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: current@FreeBSD.ORG
Subject: Weird make world error
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 04 Nov 1998 15:53:28 +0800
From: Stephen Hocking-Senior Programmer PGS Tensor Perth <shocking@prth.pgs.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
When doing a make world, it dies with....
===> sys/modules
===> sys/modules/atapi
@ -> /data/src/sys
machine -> /data/src/sys/i386/include
echo "#define NWDC 2" > wdc.h
echo "#define ATAPI 1"> opt_atapi.h
cc -O -m486 -pipe -DATAPI_MODULE -DKERNEL -Wreturn-type -Wcomment
-Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat
-fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-
-I/usr/obj/elf/data/src/sys/modules/atapi -I/usr/obj/elf/data/src/sys/modules/a
tapi/@ -I/usr/obj/elf/data/src/tmp/usr/include -c /data/src/sys/modules/atapi/.
./../i386/isa/atapi.c
gensetdefs atapi.o
gensetdefs: not found
*** Error code 1
Stop.
Where's this mysterious gensetdefs supposed to be found?
Stephen
--
The views expressed above are not those of PGS Tensor.
"We've heard that a million monkeys at a million keyboards could produce
the Complete Works of Shakespeare; now, thanks to the Internet, we know
this is not true." Robert Wilensky, University of California
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 00:06:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA14134
for freebsd-current-outgoing; Wed, 4 Nov 1998 00:06:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14128
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 00:06:40 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.59.98]) by smtp01.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAA56CE;
Wed, 4 Nov 1998 09:06:30 +0100
Message-ID: <XFMail.981104091025.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: <199811040611.WAA20667@bubba.whistle.com>
Date: Wed, 04 Nov 1998 09:10:25 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Archie Cobbs <archie@whistle.com>
Subject: Re: Current 'make world' warnings cleanup
Cc: current@FreeBSD.ORG, ryany@pobox.com, (John Polstra) <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 04-Nov-98 Archie Cobbs wrote:
> John Polstra writes:
>> Sounds good. Just one thing: don't fall prey to the temptation to
>> fix all the pointer mismatch warnings by blindly inserting casts just
>> to make the compiler shut up. That's a common mistake, and as often
>> as not it simply hides the real problem from the compiler rather than
>> fixing it.
>
> Another gotcha when doing this.. often "unused variable" warnings
> happen because there is a variable declared that is only used
> when certain #ifdef's are true. The solution in these cases is
> not to remove the variable, but to enclose it's declaration
> within equivalent #ifdef's..
So in general someone forgot to put them between the appropriate definition
statements right? Either by mistake or whatever...
---
Jeroen Ruigrok van der Werven/Asmodai [trying to get his C on par]
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Wed Nov 4 00:11:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA15142
for freebsd-current-outgoing; Wed, 4 Nov 1998 00:11:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles146.castles.com [208.214.165.146])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15121
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 00:11:53 -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 AAA01013;
Wed, 4 Nov 1998 00:11:03 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811040811.AAA01013@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Stephen Hocking-Senior Programmer PGS Tensor Perth <shocking@prth.pgs.com>
cc: current@FreeBSD.ORG
Subject: Re: Weird make world error
In-reply-to: Your message of "Wed, 04 Nov 1998 15:53:28 +0800."
<199811040753.PAA08326@ariadne.tensor.pgs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 04 Nov 1998 00:11:03 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> When doing a make world, it dies with....
>
>
>
> ===> sys/modules
> ===> sys/modules/atapi
> @ -> /data/src/sys
> machine -> /data/src/sys/i386/include
> echo "#define NWDC 2" > wdc.h
> echo "#define ATAPI 1"> opt_atapi.h
> cc -O -m486 -pipe -DATAPI_MODULE -DKERNEL -Wreturn-type -Wcomment
> -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat
> -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-
> -I/usr/obj/elf/data/src/sys/modules/atapi -I/usr/obj/elf/data/src/sys/modules/a
> tapi/@ -I/usr/obj/elf/data/src/tmp/usr/include -c /data/src/sys/modules/atapi/.
> ./../i386/isa/atapi.c
> gensetdefs atapi.o
> gensetdefs: not found
> *** Error code 1
>
> Stop.
>
> Where's this mysterious gensetdefs supposed to be found?
In /usr/bin. It probably should have been made a bootstrap tool,
except that there's hope that the new linker-set technique that John
Polstra has developed will make it obsolete.
You should learn about 'whereis'.
--
\\ 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 4 00:32:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA17414
for freebsd-current-outgoing; Wed, 4 Nov 1998 00:32:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles146.castles.com [208.214.165.146])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17409
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 00:32:27 -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 AAA01159;
Wed, 4 Nov 1998 00:31:15 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811040831.AAA01159@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bob Vaughan <techie@tantivy.stanford.edu>
cc: current@FreeBSD.ORG
Subject: Re: pccard ethernet breakage between 2.2-stable and 3.0-current
In-reply-to: Your message of "Mon, 02 Nov 1998 19:59:31 PST."
<199811030359.TAA25359@tantivy.stanford.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 04 Nov 1998 00:31:15 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> cvs update as of saturday (both trees).
> my sthernet card (a SVEC ne2000 compatable) breaks under 3.0-current only,
> but 2.2-stable works fine.
> I noticed the same type of breakage in PAO when i tried it back in july/august.
>
> symptoms: my ethernet card returns a bogus hardware address the first couple
> of times it is probed, but the third time it returns the correct address.
> the 2.2-stable code properly deals with this, while the 3.0-current code
> accepts the bogus address..
>
> hardware: chembook 3300 (p233mmx, 96mb ram, 4gb disk), SVEC ne2000 compatable
> ethernet card.
Can you be more specific about "properly deals with this"? We had a
previous tester give up on the svec card in total disgust after being
unable to make it do anything useful, so any insight that would help us
to support them properly would be useful.
In particular, are there any code changes between 2.2 and 3.0's 'ed'
driver that you think might account for the different behaviour?
--
\\ 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 4 00:57:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA20360
for freebsd-current-outgoing; Wed, 4 Nov 1998 00:57:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20349
for <freebsd-current@freebsd.org>; Wed, 4 Nov 1998 00:56:58 -0800 (PST)
(envelope-from vallo@myhakas.matti.ee)
Received: from myhakas.matti.ee (vallo@myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id KAA25707 for <freebsd-current@freebsd.org>; Wed, 4 Nov 1998 10:56:41 +0200 (EET)
Received: (from vallo@localhost)
by myhakas.matti.ee (8.9.1/8.9.1) id KAA08396
for freebsd-current@freebsd.org; Wed, 4 Nov 1998 10:56:44 +0200 (EET)
(envelope-from vallo)
Message-ID: <19981104105644.A8372@matti.ee>
Date: Wed, 4 Nov 1998 10:56:44 +0200
From: Vallo Kallaste <vallo@matti.ee>
To: freebsd-current@FreeBSD.ORG
Subject: kld: green saver module
Reply-To: vallo@matti.ee
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?=
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello !
I compiled and loaded the green_saver kld module, but no saving was
happened. I tried to set different timeout values too with vidcontrol
without success. Nothing happens, only module loads. Should the
green_saver module work or is it abandoned ?
Thanks
Vallo Kallaste
vallo@matti.ee
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 02: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 CAA29692
for freebsd-current-outgoing; Wed, 4 Nov 1998 02:20:07 -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 CAA29615
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 02:19:49 -0800 (PST)
(envelope-from peter.jeremy@auss2.alcatel.com.au)
Received: by border.alcanet.com.au id <40336>; Wed, 4 Nov 1998 21:19:07 +1100
Date: Wed, 4 Nov 1998 21:19:33 +1100
From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Subject: Re: lisp vs. Forth
To: current@FreeBSD.ORG
Message-Id: <98Nov4.211907est.40336@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Smith <mike@smith.net.au> wrote:
[siod is]
>About 75k according to:
I feel that's excessive for an embedded language in a bootloader. Even
if it won't fit into the bootblocks, it still needs to fit onto a floppy
with a kernel (unless we want to have separate boot and root floppies as
some other Unices do).
>What's the feeling on the lisp vs. Forth argument?
I prefer lisp for non-trivial work, but can get by in forth. You
can write illegible code in any language, so I don't think that
argument holds much weight. A forth kernel is much smaller than
lisp because there's no need for garbage collection or tagged pointers.
(The downside is that forth doesn't have garbage collection or
runtime typing :-).
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 4 03:14:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA04904
for freebsd-current-outgoing; Wed, 4 Nov 1998 03:14:38 -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 DAA04898
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 03:14:34 -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 MAA14656;
Wed, 4 Nov 1998 12:20:33 +0100 (CET)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Wed, 4 Nov 1998 12:20:31 +0100 (CET)
From: Andrzej Bialecki <abial@nask.pl>
X-Sender: abial@korin.warman.org.pl
To: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
cc: current@FreeBSD.ORG
Subject: Re: lisp vs. Forth
In-Reply-To: <98Nov4.211907est.40336@border.alcanet.com.au>
Message-ID: <Pine.BSF.4.02A.9811041217350.9870-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, 4 Nov 1998, Peter Jeremy wrote:
> I prefer lisp for non-trivial work, but can get by in forth. You
> can write illegible code in any language, so I don't think that
> argument holds much weight. A forth kernel is much smaller than
> lisp because there's no need for garbage collection or tagged pointers.
> (The downside is that forth doesn't have garbage collection or
> runtime typing :-).
...and some people consider it an advantage of Forth :-). You simply
fetch/put an N-bit value, and _you_ should know what it means.
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 4 03:26:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA06064
for freebsd-current-outgoing; Wed, 4 Nov 1998 03:26:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [36.118.0.70])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA06059
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 03:26:39 -0800 (PST)
(envelope-from techie@tantivy.stanford.edu)
Received: (from techie@localhost)
by tantivy.stanford.edu (8.8.8/8.8.5) id DAA22772;
Wed, 4 Nov 1998 03:26:14 -0800 (PST)
From: Bob Vaughan <techie@tantivy.stanford.edu>
Message-Id: <199811041126.DAA22772@tantivy.stanford.edu>
Subject: Re: pccard ethernet breakage between 2.2-stable and 3.0-current
In-Reply-To: <199811040831.AAA01159@dingo.cdrom.com> from Mike Smith at "Nov 4, 1998 0:31:15 am"
To: mike@smith.net.au (Mike Smith)
Date: Wed, 4 Nov 1998 03:26:13 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA06060
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > cvs update as of saturday (both trees).
> > my sthernet card (a SVEC ne2000 compatable) breaks under 3.0-current only,
> > but 2.2-stable works fine.
> > I noticed the same type of breakage in PAO when i tried it back in july/august.
> >
> > symptoms: my ethernet card returns a bogus hardware address the first couple
> > of times it is probed, but the third time it returns the correct address.
> > the 2.2-stable code properly deals with this, while the 3.0-current code
> > accepts the bogus address..
> >
> > hardware: chembook 3300 (p233mmx, 96mb ram, 4gb disk), SVEC ne2000 compatable
> > ethernet card.
>
> Can you be more specific about "properly deals with this"? We had a
> previous tester give up on the svec card in total disgust after being
> unable to make it do anything useful, so any insight that would help us
> to support them properly would be useful.
>
> In particular, are there any code changes between 2.2 and 3.0's 'ed'
> driver that you think might account for the different behaviour?
>
sure.. now that I have that machine back to 2.2-stable, I can communicate
with it again..
I should note that the pccard code in 2.2-stable works with my modem,
while the PAO code, and 3.0 do not.
here is a copy of my /etc/pccard.conf, and messages from both 3.0 and 2.2.7.
# $Id: pccard.conf.sample,v 1.4 1996/06/19 01:28:07 nate Exp $
# Generally available IO ports
io 0x240-0x2f7 0x300-0x360 0x3e0-0x3ef
# Generally available IRQs (Built-in sound-card owners remove 5)
irq 3 10 11 13
# Available memory slots
memory 0xd4000 96k
#SVEC NE2000 compatable
card "Ethernet" "Adapter"
config 0x1 "ed0" 11
ether 0xff0
insert echo SVEC PCMCIA Ethernet inserted
insert /etc/pccard_ether ed0
insert /usr/local/bin/pc-ether
remove echo SVEC PCMCIA Ethernet removed
remove /sbin/umount -a -f -t nfs
remove /sbin/ifconfig ed0 delete
# generic 33.6K FAX/Data Modem
card "RI PICA B" "RC336ACL"
config 0x22 "sio2" 5
insert echo generic 33.6 FaxModem inserted
remove echo generic 33.6 FaxModem removed
3.0-current
Nov 2 05:13:35 roadwarrior /kernel: FreeBSD 3.0-CURRENT #2: Mon Nov 2 04:30:35 PST 1998
Nov 2 05:13:35 roadwarrior /kernel: techie@roadwarrior.stanford.edu:/c1/3.0-current.t/src/sys/compile/ROADWARRIOR
Nov 2 05:13:35 roadwarrior /kernel: Timecounter "i8254" frequency 1193182 Hz
Nov 2 05:13:35 roadwarrior /kernel: CPU: Pentium/P55C (233.88-MHz 586-class CPU)
Nov 2 05:13:35 roadwarrior /kernel: Origin = "GenuineIntel" Id = 0x543 Stepping=3
Nov 2 05:13:35 roadwarrior /kernel: Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX>
Nov 2 05:13:35 roadwarrior /kernel: real memory = 100663296 (98304K bytes)
Nov 2 05:13:35 roadwarrior /kernel: avail memory = 95182848 (92952K bytes)
Nov 2 05:13:35 roadwarrior /kernel: Probing for devices on PCI bus 0:
Nov 2 05:13:35 roadwarrior /kernel: chip0: <Intel 82439TX System Controller (MTXC)> rev 0x01 on pci0.0.0
Nov 2 05:13:36 roadwarrior /kernel: chip1: <Intel 82371AB PCI to ISA bridge> rev 0x01 on pci0.1.0
Nov 2 05:13:36 roadwarrior /kernel: ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on pci0.1.1
Nov 2 05:13:36 roadwarrior /kernel: chip2: <Intel 82371AB USB host controller> rev 0x01 int d irq 0 on pci0.1.2
Nov 2 05:13:36 roadwarrior /kernel: chip3: <Intel 82371AB Power management controller> rev 0x01 on pci0.1.3
Nov 2 05:13:36 roadwarrior /kernel: vga0: <Trident model 9660 VGA-compatible display device> rev 0xd3 int a irq 255 on pci0.2.0
Nov 2 05:13:36 roadwarrior /kernel: chip4: <PCI to CardBus bridge (vendor=104c device=ac17)> rev 0x02 int a irq 10 on pci0.3.0
Nov 2 05:13:36 roadwarrior /kernel: chip5: <PCI to CardBus bridge (vendor=104c device=ac17)> rev 0x02 int b irq 10 on pci0.3.1
Nov 2 05:13:37 roadwarrior /kernel: apm0 flags 0x31 on isa
Nov 2 05:13:37 roadwarrior /kernel: apm: found APM BIOS version 1.2
Nov 2 05:13:37 roadwarrior /kernel: PC-Card VLSI 82C146 (5 mem & 2 I/O windows)
Nov 2 05:13:37 roadwarrior /kernel: pcic: controller irq 3
Nov 2 05:13:37 roadwarrior /kernel: Initializing PC-card drivers: ed sio
Nov 2 05:13:37 roadwarrior /kernel: Card inserted, slot 0
Nov 2 05:13:37 roadwarrior /kernel: Card inserted, slot 1
Nov 2 05:13:38 roadwarrior pccardd[46]: Ether=18:08:00:00:00:00
Nov 2 05:13:44 roadwarrior /kernel: ed0: address 18:08:00:00:00:00, type NE2000 (16 bit)
Nov 2 05:13:54 roadwarrior /kernel: sio2: type 16550A
Nov 2 05:13:54 roadwarrior pccardd[46]: pccardd started
(doesn't work. wrong hardware address.)
2.2-stable
Nov 2 06:08:09 roadwarrior /kernel: FreeBSD 2.2.7-STABLE #0: Sun Nov 1 16:39:08 PST 1998
Nov 2 06:08:09 roadwarrior /kernel: techie@roadwarrior.stanford.edu:/usr/src/sys/compile/ROADWARRIOR
Nov 2 06:08:10 roadwarrior /kernel: CPU: Pentium/P55C (233.89-MHz 586-class CPU)
Nov 2 06:08:10 roadwarrior /kernel: Origin = "GenuineIntel" Id = 0x543 Stepping=3
Nov 2 06:08:10 roadwarrior /kernel: Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX>
Nov 2 06:08:10 roadwarrior /kernel: real memory = 100663296 (98304K bytes)
Nov 2 06:08:10 roadwarrior /kernel: avail memory = 95899648 (93652K bytes)
Nov 2 06:08:10 roadwarrior /kernel: Probing for devices on PCI bus 0:
Nov 2 06:08:10 roadwarrior /kernel: chip0 <Intel 82439TX PCI cache memory controller> rev 1 on pci0:0:0
Nov 2 06:08:10 roadwarrior /kernel: chip1 <Intel 82371AB PCI-ISA bridge> rev 1 on pci0:1:0
Nov 2 06:08:10 roadwarrior /kernel: chip2 <Intel 82371AB IDE interface> rev 1 on pci0:1:1
Nov 2 06:08:10 roadwarrior /kernel: chip3 <Intel 82371AB USB interface> rev 1 int d irq ?? on pci0:1:2
Nov 2 06:08:10 roadwarrior /kernel: chip4 <Intel 82371AB Power management controller> rev 1 on pci0:1:3
Nov 2 06:08:10 roadwarrior /kernel: vga0 <VGA-compatible display device> rev 211 int a irq ?? on pci0:2:0
Nov 2 06:08:10 roadwarrior /kernel: chip5 <generic PCI bridge (vendor=104c device=ac17 subclass=7)> rev 2 int a irq 10 on pci0:3:0
Nov 2 06:08:10 roadwarrior /kernel: chip6 <generic PCI bridge (vendor=104c device=ac17 subclass=7)> rev 2 int b irq 10 on pci0:3:1
Nov 2 06:08:11 roadwarrior /kernel: apm0 on isa
Nov 2 06:08:11 roadwarrior /kernel: apm: found APM BIOS version 1.1
Nov 2 06:08:11 roadwarrior /kernel: PC-Card VLSI 82C146 (5 mem & 2 I/O windows)
Nov 2 06:08:11 roadwarrior /kernel: pcic: controller irq 3
Nov 2 06:08:11 roadwarrior /kernel: Initializing PC-card drivers: ed sio
Nov 2 06:08:11 roadwarrior /kernel: Card inserted, slot 1
Nov 2 06:08:12 roadwarrior /kernel: Card inserted, slot 0
Nov 2 06:08:18 roadwarrior /kernel: Slot 0, unfielded interrupt (0)
Nov 2 06:08:18 roadwarrior /kernel: sio2: type 16550A
Nov 2 06:08:23 roadwarrior pccardd[46]: Ether=18:08:00:00:00:00
Nov 2 06:08:28 roadwarrior /kernel: Slot 1, unfielded interrupt (0)
Nov 2 06:08:28 roadwarrior /kernel: ed0: address 00:e0:98:01:a0:6c, type NE2000 (16 bit)
Nov 2 06:08:28 roadwarrior pccardd[46]: pccardd started
(works fine.)
--
-- Welcome My Son, Welcome To The Machine --
Bob Vaughan | techie@w6yx.stanford.edu | kc6sxc@w6yx.ampr.org
| techie@t.stanford.edu | KC6SXC@W6YX.#NCA.CA.USA.NOAM
| P.O. Box 9792, Stanford, Ca 94309-9792
-- I am Me, I am only Me, And no one else is Me, What could be simpler? --
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 03:32:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA06652
for freebsd-current-outgoing; Wed, 4 Nov 1998 03:32:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from chaotic.oz.org (chaotic.oz.org [203.20.237.203])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA06647
for <current@freebsd.org>; Wed, 4 Nov 1998 03:32:10 -0800 (PST)
(envelope-from simon@oz.org)
Received: from localhost (localhost [127.0.0.1])
by chaotic.oz.org (8.9.1/8.8.8) with SMTP id VAA00159
for <current@freebsd.org>; Wed, 4 Nov 1998 21:31:50 +1000 (EST)
(envelope-from simon@oz.org)
Date: Wed, 4 Nov 1998 21:31:50 +1000 (EST)
From: Simon Coggins <simon@oz.org>
Reply-To: chaos@ultra.net.au
To: current@FreeBSD.ORG
Subject: Latest -current
Message-ID: <Pine.BSF.4.02.9811042131070.114-100000@chaotic.oz.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 just cvsup'd about an 40 mins ago, Now I'm getting this error:
===> lib/libstand
"/usr/src/lib/libstand/Makefile", line 98: if-less endif
"/usr/src/lib/libstand/Makefile", line 98: Need an operator
make: fatal errors encountered -- cannot continue
*** Error code 1
Someone break something?
Regards
Simon
---
+---------------------------------------------------------------+
| Email: chaos@ultra.net.au, chaos@oz.org, simon@bofh.com.au |
| http://www.ultra.net.au/~chaos Simon.Coggins@jcu.edu.au. |
| Chaos on IRC, IRC Operator for the OzORG Network |
+---------------------------------------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 03:46:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA07431
for freebsd-current-outgoing; Wed, 4 Nov 1998 03:46:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vss.sci-nnov.ru (vss.sci-nnov.ru [193.125.71.26])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA07351
for <freebsd-current@freebsd.org>; Wed, 4 Nov 1998 03:44:50 -0800 (PST)
(envelope-from dmiter@sci-nnov.ru)
Received: from winhome (home.sci-nnov.ru [194.190.176.102]) by vss.sci-nnov.ru (8.8.8/Dmiter-4.2vss) with SMTP id OAA20097 for <freebsd-current@freebsd.org>; Wed, 4 Nov 1998 14:44:23 +0300 (MSK)
Message-ID: <02e701be07e8$5aa78e10$0200000a@winhome.sci-nnov.ru>
Reply-To: "Dmitry Eremin" <dmiter@sci-nnov.ru>
From: "Dmitry Eremin" <dmiter@sci-nnov.ru>
To: <freebsd-current@FreeBSD.ORG>
Subject: amd 53c974 scsi
Date: Wed, 4 Nov 1998 14:43:33 +0300
MIME-Version: 1.0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>Tomas Hodan wrote...
>> Hi all,
>> it is any possibilit to use Adapec APA-1460 PCMCIA SCSI Adapter with 3.0
?
>>
>> thanks
>> tomas
>>
>> mouse:/sys/compile/MOUSE# make depend
>> rm -f .newdep
>> mkdep -a -f
>>
ewdep -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-ext
>> erns -Wstrict-prototypes -Wmissing-prototyc
>> cc: ../../dev/aic6x60/aic.c: No such file or directory
>> cc: ../../i386/isa/aic_isa.c: No such file or directory
>
>The "aic" (aic6260/6360) driver hasn't been ported to CAM yet. Brian
>Beattie <beattie@aracnet.com> is working on it, but I don't know how far
>along he is on it.
What about amd0: <amd 53c974 scsi>???? Is still rewriting too???
Best regards Dmitry.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 04:05:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA11414
for freebsd-current-outgoing; Wed, 4 Nov 1998 04:05:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from hen.scotland.net ([194.247.65.128])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11407
for <current@freebsd.org>; Wed, 4 Nov 1998 04:05:28 -0800 (PST)
(envelope-from freebsd@timog.prestel.co.uk)
Received: from e1c2p25.scotland.net ([148.176.232.89] helo=timog.prestel.co.uk)
by hen.scotland.net with esmtp (Exim 1.90 #5)
for current@FreeBSD.ORG
id 0zb1gc-0002YK-00; Wed, 4 Nov 1998 12:05:18 +0000
Received: (qmail 10066 invoked by uid 1002); 4 Nov 1998 08:35:31 -0000
Message-ID: <19981104083530.A739@prestel.co.uk>
Date: Wed, 4 Nov 1998 08:35:30 +0000
From: Timo Geusch <freebsd@timog.prestel.co.uk>
To: current@FreeBSD.ORG
Subject: Re: Another compile error
References: <199811021742.JAA07742@austin.polstra.com> <XFMail.981103225915.asmodai@wxs.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <XFMail.981103225915.asmodai@wxs.nl>; from Jeroen Ruigrok/Asmodai on Tue, Nov 03, 1998 at 10:59:15PM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, Nov 03, 1998 at 10:59:15PM +0100, Jeroen Ruigrok/Asmodai wrote:
[big snip]
> Q. OK, so what does make buildworld do?
> A. ?
Rebuild the whole FreeBSD base system aprt from the kernel, that is the whole
system minus ports and the kernel (which has to be built separately).
> Q. And how about make installworld?
Install the system built with buildworld over your current FreeBSD system.
Don't forget to rebuild the kernel afterwards, though.
Timo
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 04: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 EAA17455
for freebsd-current-outgoing; Wed, 4 Nov 1998 04:48:39 -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 EAA17450
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 04:48:37 -0800 (PST)
(envelope-from shimon@simon-shapiro.org)
Received: (qmail 6874 invoked by uid 1000); 4 Nov 1998 13:52:18 -0000
Message-ID: <XFMail.981104085218.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: <199811040811.AAA01013@dingo.cdrom.com>
Date: Wed, 04 Nov 1998 08:52:18 -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: Weird make world error
Cc: current@FreeBSD.ORG,
Stephen Hocking-Senior Programmer PGS Tensor Perth <shocking@prth.pgs.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Mike Smith, On 04-Nov-98 you wrote:
> > When doing a make world, it dies with....
> >
> >
> >
> > ===> sys/modules
> > ===> sys/modules/atapi
> > @ -> /data/src/sys
> > machine -> /data/src/sys/i386/include
> > echo "#define NWDC 2" > wdc.h
> > echo "#define ATAPI 1"> opt_atapi.h
> > cc -O -m486 -pipe -DATAPI_MODULE -DKERNEL -Wreturn-type -Wcomment
> > -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes
> > -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat
> > -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-
> > -I/usr/obj/elf/data/src/sys/modules/atapi
> > -I/usr/obj/elf/data/src/sys/modules/a
> > tapi/@ -I/usr/obj/elf/data/src/tmp/usr/include -c
> > /data/src/sys/modules/atapi/.
> > ./../i386/isa/atapi.c
> > gensetdefs atapi.o
> > gensetdefs: not found
> > *** Error code 1
> >
> > Stop.
> >
> > Where's this mysterious gensetdefs supposed to be found?
>
> In /usr/bin. It probably should have been made a bootstrap tool,
> except that there's hope that the new linker-set technique that John
> Polstra has developed will make it obsolete.
>
> You should learn about 'whereis'.
Not so simple. Whereis finds it. cd /usr/src/sys/modules;make finds it
and build fine. Make buildworld produces this error. It is relatively new
(the build of the 1st did not have this problem.
Simon
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 04: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 EAA17598
for freebsd-current-outgoing; Wed, 4 Nov 1998 04:49:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17587
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 04:49:39 -0800 (PST)
(envelope-from cracauer@gilgamesch.bik-gmbh.de)
Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id NAA24726; Wed, 4 Nov 1998 13:49:00 +0100 (MET)
Message-ID: <19981104134859.A24574@cons.org>
Date: Wed, 4 Nov 1998 13:48:59 +0100
From: Martin Cracauer <cracauer@cons.org>
To: Mike Smith <mike@smith.net.au>, "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: Parag Patel <parag@cgt.com>, current@FreeBSD.ORG
Subject: Re: lisp vs. Forth (was Re: New boot loader and alternate kernels )
References: <2329.910134454@time.cdrom.com> <199811032319.PAA00900@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <199811032319.PAA00900@dingo.cdrom.com>; from Mike Smith on Tue, Nov 03, 1998 at 03:19:27PM -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In <199811032319.PAA00900@dingo.cdrom.com>, Mike Smith wrote:
> What's the feeling on the lisp vs. Forth argument?
If you take the pure languages, without any existing implementations
or standards mostly implemented, they are very similar.
Both languages have very simple syntax that keeps a minimal
interpreter down in size.
What I like more about Lisp is that it's syntax is:
- more readable than RPN
- easier to verify that you got the arguments right, especially in
math expressions.
And most important the Lisp syntax allows you to be more flexible:
- It's easy to have functions that take a variable number of arguments
without encoding the number of arguments in in your source tree.
- It's easy to implement "keyword arguments" (Lisp equivalent to the
commandline switches in Unix commands), virtually impossible in RPN
- Something like printf is easy to do in Lisp syntax, not in Forth.
Every rescent Lisp except elisp implements static scope, a big plus
for readability and espcially for source-constructing tools. Macros
are also very handy for this task but don't make sense in RPN.
You could use the syntax of Lisp to take and evaluate expressions from
the user (from the keyboard or out of files). Lisp isn't everyone's
taste, but with keywoard arguments it will be a lot better than RPN to
enter at a boot prompt.
A big plus for the task are also exceptions that take you back through
the call tree savely. Don't know about Forth, but it's handy in Lisp.
I'd say that a script to bootstrap a system by talking to hardware is
a lot more readable in Lisp syntax. Imagine booting from a SCSI
scanner using a piece of paper with a heavily ECC'ed barcode
printing. You don't want to write that in Forth :-)
To keep the size down, you probably can't (and don't have for the
task) even implement all of Scheme (tail-recursive call elimination,
the full number tree - we don't need complex numbers in bootstrapping
:-), but even with a minimal subset you can use much of slib if you
just keep the function names of the primitive compatible to
Scheme. http://www-swiss.ai.mit.edu/~jaffer/slib_toc.html
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer
BSD User Group Hamburg, Germany http://www.bsdhh.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 4 05:15:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA20258
for freebsd-current-outgoing; Wed, 4 Nov 1998 05:15:57 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from bfc.dk ([194.192.110.140])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA20253
for <freebsd-current@freebsd.org>; Wed, 4 Nov 1998 05:15:53 -0800 (PST)
(envelope-from npe@bfc.dk)
From: npe@bfc.dk
Received: by bfc.dk(Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) id 412566B2.00487B51 ; Wed, 4 Nov 1998 14:11:41 +0100
X-Lotus-FromDomain: BFC-DATA@BFC
To: garman@earthling.net
cc: freebsd-current@FreeBSD.ORG
Message-ID: <412566B2.004DC9C6.00@bfc.dk>
Date: Wed, 4 Nov 1998 15:12:46 +0100
Subject: Re: samba smbd core dumps & -current
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I have the same problems with current now.. And the error seems to have bin
there atleast a month. smbd simply dies with signal 11.
I had a feeling that it was my fault in the conf. file.. But now I don't
think so..
If anyone have clue please help poor us !
Regards,
Nicolai Petri
WM-Data BFC
garman@earthling.net on 11/04/98 03:28:14 AM
Please respond to garman@earthling.net
To: current@FreeBSD.ORG
cc: (bcc: Nicolai Petri/BFC-DATA)
Subject: samba smbd core dumps & -current
i'm having problems with smbd coredumping on -current (as of a week ago
or so)... this has been happening for a while. i've upgraded to
samba1.9.18p10 to no avail.
it seems to happen whenever a user authenticates to it; guest access
seems to work okay. strange thing it is...
any tips? i haven't seen any discussion of this on here... same
configuration as before: pentiumII/300, aout system, 96MB of ram, no
problems with smbd before recent -current's.
if nobody else has seen this, i'll compile with debugging information
and attempt to track this thing down.
btw- the inetd patch has kept inetd from dying so far, thankfully. it
would have died by now without it.
enjoy
--
Jason Garman http://garman.dyn.ml.org/
Student, University of Maryland garman@earthling.net
And now... for the stupid-patent-of-the-week: Whois: JAG145
"...an attache case with destruct means for destroying the contents
therein in response to a signal" -- patent no. US3643609, filed in 1969
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 4 05:25:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA21648
for freebsd-current-outgoing; Wed, 4 Nov 1998 05:25:52 -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 FAA21623
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 05:25:47 -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 VAA29986;
Wed, 4 Nov 1998 21:23:25 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811041323.VAA29986@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: shimon@simon-shapiro.org
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG,
Stephen Hocking-Senior Programmer PGS Tensor Perth <shocking@prth.pgs.com>
Subject: Re: Weird make world error
In-reply-to: Your message of "Wed, 04 Nov 1998 08:52:18 EST."
<XFMail.981104085218.shimon@simon-shapiro.org>
Date: Wed, 04 Nov 1998 21:23:25 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Simon Shapiro wrote:
>
> Mike Smith, On 04-Nov-98 you wrote:
> > > When doing a make world, it dies with....
> > >
> > >
> > >
> > > ===> sys/modules
> > > ===> sys/modules/atapi
> > > @ -> /data/src/sys
> > > machine -> /data/src/sys/i386/include
> > > echo "#define NWDC 2" > wdc.h
> > > echo "#define ATAPI 1"> opt_atapi.h
> > > cc -O -m486 -pipe -DATAPI_MODULE -DKERNEL -Wreturn-type -Wcomment
> > > -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes
> > > -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat
> > > -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-
> > > -I/usr/obj/elf/data/src/sys/modules/atapi
> > > -I/usr/obj/elf/data/src/sys/modules/a
> > > tapi/@ -I/usr/obj/elf/data/src/tmp/usr/include -c
> > > /data/src/sys/modules/atapi/.
> > > ./../i386/isa/atapi.c
> > > gensetdefs atapi.o
> > > gensetdefs: not found
> > > *** Error code 1
> > >
> > > Stop.
> > >
> > > Where's this mysterious gensetdefs supposed to be found?
> >
> > In /usr/bin. It probably should have been made a bootstrap tool,
> > except that there's hope that the new linker-set technique that John
> > Polstra has developed will make it obsolete.
> >
> > You should learn about 'whereis'.
>
> Not so simple. Whereis finds it. cd /usr/src/sys/modules;make finds it
> and build fine. Make buildworld produces this error. It is relatively new
> (the build of the 1st did not have this problem.
The buildworld environment builds (completely) it's own toolchain and
restricts the $PATH to the tools that it has built. When I turned on the
src/sys/modules SUBDIR, it (for the first time) needed the gensetdefs
command, which was missing from the list of tools needed. "oops". Sorry
folks.
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 4 05:35:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA23660
for freebsd-current-outgoing; Wed, 4 Nov 1998 05:35:42 -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 FAA23655
for <freebsd-current@freebsd.org>; Wed, 4 Nov 1998 05:35:39 -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 OAA00127
for <freebsd-current@freebsd.org>; Wed, 4 Nov 1998 14:35:21 +0100 (MET)
Received: (from cejkar@localhost)
by kazi.dcse.fee.vutbr.cz (8.8.8/8.8.8) id OAA12936
for freebsd-current@freebsd.org; Wed, 4 Nov 1998 14:35:20 +0100 (CET)
From: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>
Message-Id: <199811041335.OAA12936@kazi.dcse.fee.vutbr.cz>
Subject: ELFoized xtt-SVGA-1.0 & TrueType fonts => HANG
To: freebsd-current@FreeBSD.ORG (freebsd-current@freebsd.org)
Date: Wed, 4 Nov 1998 14:35:20 +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
I have ELFoized -current:
Main system (/usr/src): 98/09/28
XFree86: 98/10/23
and I'm trying to use TrueType X server:
XF86_SVGA.xtt: 98/11/04
With a.out, there was everything good. But in ELFoized version,
during attempt to display any TrueType font Xserver
hangs - ant it eats up to 80 % of system time.
Is this problem public or personal only?
Here is ktrace-dump just before hang (with running xfontsel):
403 XF86_SVGA.xtt RET writev 128/0x80
403 XF86_SVGA.xtt CALL gettimeofday(0xefbfd77c,0)
403 XF86_SVGA.xtt RET gettimeofday 0
403 XF86_SVGA.xtt CALL select(0x80,0x82af750,0,0,0xefbfd7c8)
403 XF86_SVGA.xtt RET select 2
403 XF86_SVGA.xtt CALL read(0xa,0x841a008,0x1000)
403 XF86_SVGA.xtt GIO fd 10 read 136 bytes
"......-ttf-*-*-*-*-*-*-*-*-*-*-*-*-*......"
403 XF86_SVGA.xtt RET read 136/0x88
403 XF86_SVGA.xtt CALL madvise(0x8470000,0x1000,0x5)
403 XF86_SVGA.xtt RET madvise 0
403 XF86_SVGA.xtt CALL madvise(0x846f000,0x1000,0x5)
403 XF86_SVGA.xtt RET madvise 0
403 XF86_SVGA.xtt CALL munmap(0x28683000,0x5000)
403 XF86_SVGA.xtt RET munmap 0
403 XF86_SVGA.xtt CALL madvise(0x846e000,0x1000,0x5)
403 XF86_SVGA.xtt RET madvise 0
403 XF86_SVGA.xtt CALL gettimeofday(0xefbfd8bc,0)
403 XF86_SVGA.xtt RET gettimeofday 0
403 XF86_SVGA.xtt CALL break(0x8496000)
403 XF86_SVGA.xtt RET break 0
403 XF86_SVGA.xtt CALL open(0x846e000,0,0x282dda14)
403 XF86_SVGA.xtt NAMI "/usr/X11R6/lib/X11/fonts/TrueType/ariblk.ttf"
403 XF86_SVGA.xtt RET open 11/0xb
403 XF86_SVGA.xtt CALL fstat(0xb,0xefbfb55c)
403 XF86_SVGA.xtt RET fstat 0
403 XF86_SVGA.xtt CALL mmap(0,0x19638,0x1,0x2,0xb,0,0,0)
403 XF86_SVGA.xtt RET mmap 677953536/0x2868c000
403 XF86_SVGA.xtt CALL close(0xb)
403 XF86_SVGA.xtt RET close 0
403 XF86_SVGA.xtt CALL stat(0x282bf581,0xefbfb584)
403 XF86_SVGA.xtt NAMI "/usr/X11R6/lib/modules/codeconv"
403 XF86_SVGA.xtt RET stat 0
403 XF86_SVGA.xtt CALL open(0x282bf581,0x4,0x283743a0)
403 XF86_SVGA.xtt NAMI "/usr/X11R6/lib/modules/codeconv"
403 XF86_SVGA.xtt RET open 11/0xb
403 XF86_SVGA.xtt CALL fstat(0xb,0xefbfb584)
403 XF86_SVGA.xtt RET fstat 0
403 XF86_SVGA.xtt CALL fcntl(0xb,0x2,0x1)
403 XF86_SVGA.xtt RET fcntl 0
403 XF86_SVGA.xtt CALL fstatfs(0xb,0xefbfb484)
403 XF86_SVGA.xtt RET fstatfs 0
403 XF86_SVGA.xtt CALL getdirentries(0xb,0x847b000,0x1000,0x8452294)
403 XF86_SVGA.xtt RET getdirentries 512/0x200
403 XF86_SVGA.xtt CALL open(0x28271040,0,0x4000f930)
403 XF86_SVGA.xtt NAMI "/usr/X11R6/lib/modules/codeconv/ISO8859_1.so"
403 XF86_SVGA.xtt RET open 12/0xc
403 XF86_SVGA.xtt CALL read(0xc,0xefbfa5b8,0x1000)
403 XF86_SVGA.xtt GIO fd 12 read 4096 bytes
"......"
403 XF86_SVGA.xtt RET read 4096/0x1000
403 XF86_SVGA.xtt CALL mmap(0,0x2000,0x5,0x2,0xc,0,0,0)
403 XF86_SVGA.xtt RET mmap 677339136/0x285f6000
403 XF86_SVGA.xtt CALL mmap(0x285f7000,0x1000,0x3,0x12,0xc,0,0,0)
403 XF86_SVGA.xtt RET mmap 677343232/0x285f7000
403 XF86_SVGA.xtt CALL close(0xc)
403 XF86_SVGA.xtt RET close 0
403 XF86_SVGA.xtt CALL munmap(0x285f6000,0x2000)
403 XF86_SVGA.xtt RET munmap 0
403 XF86_SVGA.xtt CALL open(0x28271040,0,0x4000f930)
403 XF86_SVGA.xtt NAMI "/usr/X11R6/lib/modules/codeconv/BIG5.so"
403 XF86_SVGA.xtt RET open 12/0xc
403 XF86_SVGA.xtt CALL read(0xc,0xefbfa5b8,0x1000)
403 XF86_SVGA.xtt GIO fd 12 read 4096 bytes
"......"
403 XF86_SVGA.xtt RET read 4096/0x1000
403 XF86_SVGA.xtt CALL mmap(0,0xa000,0x5,0x2,0xc,0,0,0)
403 XF86_SVGA.xtt RET mmap 678060032/0x286a6000
403 XF86_SVGA.xtt CALL mmap(0x286a7000,0x9000,0x3,0x12,0xc,0,0,0)
403 XF86_SVGA.xtt RET mmap 678064128/0x286a7000
403 XF86_SVGA.xtt CALL close(0xc)
403 XF86_SVGA.xtt RET close 0
And why there are loaded modules "ISO8859_1.so" and "BIG5.so"?
In my fonts.dir there is only one line for ariblk.ttf:
ariblk.ttf -ttf-arial black-medium-r-normal-tt-0-0-0-0-p-0-iso8859-2
Why nodule "ISO8859_2.so" is not loaded?
Thanks.
--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--
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 Wed Nov 4 05: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 FAA26214
for freebsd-current-outgoing; Wed, 4 Nov 1998 05:59:30 -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 FAA26208
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 05:59:27 -0800 (PST)
(envelope-from karl@Genesis.Denninger.Net)
Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id HAA08959; Wed, 4 Nov 1998 07:58:28 -0600 (CST)
Message-ID: <19981104075828.C8935@Denninger.Net>
Date: Wed, 4 Nov 1998 07:58:28 -0600
From: Karl Denninger <karl@Denninger.Net>
To: npe@bfc.dk, garman@earthling.net
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: samba smbd core dumps & -current
References: <412566B2.004DC9C6.00@bfc.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <412566B2.004DC9C6.00@bfc.dk>; from npe@bfc.dk on Wed, Nov 04, 1998 at 03:12:46PM +0100
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
Again, I've not seen this, I run -CURRENT, and I rebuilt SAMBA recently (a
couple of weeks ago) to be an ELF-ized binary.
I use this VERY heavily on my home network; I replaced an NT server with
Samba.
--
--
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.
On Wed, Nov 04, 1998 at 03:12:46PM +0100, npe@bfc.dk wrote:
> I have the same problems with current now.. And the error seems to have bin
> there atleast a month. smbd simply dies with signal 11.
> I had a feeling that it was my fault in the conf. file.. But now I don't
> think so..
>
> If anyone have clue please help poor us !
>
> Regards,
> Nicolai Petri
> WM-Data BFC
>
>
>
>
>
> garman@earthling.net on 11/04/98 03:28:14 AM
>
> Please respond to garman@earthling.net
>
> To: current@FreeBSD.ORG
> cc: (bcc: Nicolai Petri/BFC-DATA)
> Subject: samba smbd core dumps & -current
>
>
>
>
>
> i'm having problems with smbd coredumping on -current (as of a week ago
> or so)... this has been happening for a while. i've upgraded to
> samba1.9.18p10 to no avail.
> it seems to happen whenever a user authenticates to it; guest access
> seems to work okay. strange thing it is...
> any tips? i haven't seen any discussion of this on here... same
> configuration as before: pentiumII/300, aout system, 96MB of ram, no
> problems with smbd before recent -current's.
> if nobody else has seen this, i'll compile with debugging information
> and attempt to track this thing down.
> btw- the inetd patch has kept inetd from dying so far, thankfully. it
> would have died by now without it.
> enjoy
> --
> Jason Garman http://garman.dyn.ml.org/
> Student, University of Maryland garman@earthling.net
> And now... for the stupid-patent-of-the-week: Whois: JAG145
> "...an attache case with destruct means for destroying the contents
> therein in response to a signal" -- patent no. US3643609, filed in 1969
>
> 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 Wed Nov 4 06:38:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA03245
for freebsd-current-outgoing; Wed, 4 Nov 1998 06:38:07 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03156
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 06:38:02 -0800 (PST)
(envelope-from tseidmann@simultan.ch)
Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53])
by SIMULTAN.CH (8.9.1a/8.9.1) with ESMTP id PAA20391
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 15:37:51 +0100 (CET)
Message-ID: <364066BF.715E7EFC@simultan.ch>
Date: Wed, 04 Nov 1998 15:37:51 +0100
From: Thomas Seidmann <tseidmann@simultan.ch>
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-current@FreeBSD.ORG
Subject: Re: samba smbd core dumps & -current
References: <412566B2.004DC9C6.00@bfc.dk> <19981104075828.C8935@Denninger.Net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'm using ELFed samba 1.9.18pl10 on -current very heavily and haven't
seen any of the problems you describe. BTW, I'm using authentication
with ewncrypted passwords as documented in samba's ENCRYPTION.TXT file.
Cheers,
Thomas
--
==========================================================
Thomas Seidmann
Simultan AG, CH-6246 Altishofen, Switzerland
mailto:tseidmann@simultan.ch tel +41.62.7489000
http://www.simultan.ch/~thomas fax +41.62.7489010
==========================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 06:49:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA05295
for freebsd-current-outgoing; Wed, 4 Nov 1998 06:49:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from cbgw2.lucent.com (cbgw2.lucent.com [207.24.196.52])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA05290
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 06:49:13 -0800 (PST)
(envelope-from dmobrien@cbgw2.lucent.com)
Received: from emsr2.emsr.lucent.com by cbig2.firewall.lucent.com (SMI-8.6/EMS-L sol2)
id JAA01547; Wed, 4 Nov 1998 09:21:06 -0500
Received: by emsr2.emsr.lucent.com (SMI-8.6/EMS-1.2 Solaris/emsr)
id JAA04636 for current@FreeBSD.ORG.smtp; Wed, 4 Nov 1998 09:20:38 -0500
Received: from cbsms1.cb.lucent.com by emsr2.emsr.lucent.com (SMI-8.6/EMS-1.2 Solaris/emsr)
id JAA04631 for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 09:20:37 -0500
Received: from lucent.com (llama.cb.lucent.com) by cbsms1.cb.lucent.com with ESMTP
(1.37.109.20/16.2) id AA005649290; Wed, 4 Nov 1998 09:21:30 -0500
Message-Id: <364062AD.7FCE8291@lucent.com>
Date: Wed, 04 Nov 1998 09:20:29 -0500
From: "Dan O'Brien" <dmobrien@lucent.com>
X-Mailer: Mozilla 4.05 [en] (Win95; U)
Mime-Version: 1.0
To: "current@FreeBSD.ORG" <current@FreeBSD.ORG>
Subject: Interesting diversion - M$ vs OSS
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
http://tuxedo.org/~esr/halloween.html
plus some harsh criticism of *BSD development model...
Enjoy,
Dan O'Brien (dmobrien@lucent.com)
Work: 614-860-2392 Page: 614-520-5001
Home: 740-927-2178 Home2: 740-927-2955
----------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 07:37:25 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA12149
for freebsd-current-outgoing; Wed, 4 Nov 1998 07:37: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 HAA12144
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 07:37:24 -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 IAA19466;
Wed, 4 Nov 1998 08:37:02 -0700 (MST)
(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
id IAA13391; Wed, 4 Nov 1998 08:37:01 -0700
Date: Wed, 4 Nov 1998 08:37:01 -0700
Message-Id: <199811041537.IAA13391@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: "Jordan K. Hubbard" <jkh@time.cdrom.com>, Parag Patel <parag@cgt.com>,
current@FreeBSD.ORG
Subject: Re: lisp vs. Forth (was Re: New boot loader and alternate kernels )
In-Reply-To: <199811032319.PAA00900@dingo.cdrom.com>
References: <2329.910134454@time.cdrom.com>
<199811032319.PAA00900@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
> > > bmake'd library can be downloaded from where?
> >
> > Erm, it's just one or two .c files. :-)
> >
> > I'd forgotten about siod, but it is indeed very easy to integrate.
> > The earlier versions aren't even more than one .c file long.
>
...
> What's the feeling on the lisp vs. Forth argument?
Stick with Forth, since it doesn't require a color-syntax editor to
read. :)
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 4 07:49:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA13479
for freebsd-current-outgoing; Wed, 4 Nov 1998 07:49:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from garman.dyn.ml.org (pm106-12.dialip.mich.net [192.195.231.214])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA13468
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 07:49:05 -0800 (PST)
(envelope-from garman@garman.dyn.ml.org)
Message-Id: <199811041549.HAA13468@hub.freebsd.org>
Received: (qmail 4169 invoked from smtpd); 4 Nov 1998 15:49:27 -0000
Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1)
by localhost.garman.net with SMTP; 4 Nov 1998 15:49:27 -0000
Date: Wed, 4 Nov 1998 10:49:26 -0500 (EST)
From: garman@earthling.net
Reply-To: garman@earthling.net
Subject: Re: samba smbd core dumps & -current
To: karl@Denninger.Net
cc: npe@bfc.dk, freebsd-current@FreeBSD.ORG
In-Reply-To: <19981104075828.C8935@Denninger.Net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 08:24:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA18508
for freebsd-current-outgoing; Wed, 4 Nov 1998 08:24:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18440
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 08:23:47 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA17280;
Wed, 4 Nov 1998 11:23:13 -0500 (EST)
Date: Wed, 4 Nov 1998 11:23:13 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@zone.syracuse.net
To: "George W. Dinolt" <george.w.dinolt@lmco.com>
cc: current@FreeBSD.ORG
Subject: Re: mount_msdos is dead :(
In-Reply-To: <363FD097.F2336E50@lmco.com>
Message-ID: <Pine.BSF.4.05.9811041122380.17234-100000@zone.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I completely rebuilt an ELF kernel and all modules yesterday. I verify
that this problem did not exist on 3.0-RELEASE.
Cheers,
Brian Feldman
On Tue, 3 Nov 1998, George W. Dinolt wrote:
> I
> Brian Feldman wrote:
>
> > I'm attaching a script that shows this.
> >
> > Brian Feldman
> >
> > Script started on Tue Nov 3 22:07:44 1998
> > {"/home/green"}# mount_msdos /dev/fd0 /m^H ^Hfloppy^M^M
> > mount_msdos: /dev/fd0: Block device required^M
> > {"/home/green"}# ls -l /dev/fd0^M^M
> > brw------- 1 root operator 2, 0 Nov 3 20:47 /dev/fd0^M
> > {"/home/green"}# dd if=/dev/rfd0 of=flop^M^M
> > 2880+0 records in^M
> > 2880+0 records out^M
> > 1474560 bytes transferred in 52.781845 secs (27937 bytes/sec)^M
> > {"/home/green"}# vnconfig -c /dev/vn0 /home/green/flop^M^M
> > {"/home/green"}# mount_msdos /dev/vn0 /floppy^M^M
> > mount_msdos: /dev/vn0: Block device required^M
> > {"/home/green"}# ls -l /dev/vn0^M^M
> > brw-r----- 1 root operator 15, 0x00010002 Jul 24 08:52 /dev/vn0^M
> > {"/home/green"}# ^D^M^M
> >
> > Script done on Tue Nov 3 22:11:16 1998
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-current" in the body of the message
>
> I ran into similar problems several days ago after some large changes to
> the kernel were committed. I think that if you rebuild your lkm modules
> so they match the kernel you are running things will work. At least they
> did for me. I haven't tried an elf kernel for a while, but I suspect the
> same would happen if the '.ko' modules were not in sync with the kernel.
>
> Regards,
> George Dinolt
>
>
> 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 4 08:34:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA19819
for freebsd-current-outgoing; Wed, 4 Nov 1998 08:34:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19797
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 08:34:21 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA17441;
Wed, 4 Nov 1998 11:34:05 -0500 (EST)
Date: Wed, 4 Nov 1998 11:34:05 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@zone.syracuse.net
To: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>
cc: "freebsd-current@freebsd.org" <freebsd-current@FreeBSD.ORG>
Subject: Re: ELFoized xtt-SVGA-1.0 & TrueType fonts => HANG
In-Reply-To: <199811041335.OAA12936@kazi.dcse.fee.vutbr.cz>
Message-ID: <Pine.BSF.4.05.9811041133220.17234-100000@zone.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
Xtt is slow to load fonts, and hangs while loading them for a sec. Same
with plain X fonts, too (X itself, not Xtt)
Brian Feldman
On Wed, 4 Nov 1998, Cejka Rudolf wrote:
>
> I have ELFoized -current:
> Main system (/usr/src): 98/09/28
> XFree86: 98/10/23
> and I'm trying to use TrueType X server:
> XF86_SVGA.xtt: 98/11/04
>
> With a.out, there was everything good. But in ELFoized version,
> during attempt to display any TrueType font Xserver
> hangs - ant it eats up to 80 % of system time.
>
> Is this problem public or personal only?
>
> Here is ktrace-dump just before hang (with running xfontsel):
>
> 403 XF86_SVGA.xtt RET writev 128/0x80
> 403 XF86_SVGA.xtt CALL gettimeofday(0xefbfd77c,0)
> 403 XF86_SVGA.xtt RET gettimeofday 0
> 403 XF86_SVGA.xtt CALL select(0x80,0x82af750,0,0,0xefbfd7c8)
> 403 XF86_SVGA.xtt RET select 2
> 403 XF86_SVGA.xtt CALL read(0xa,0x841a008,0x1000)
> 403 XF86_SVGA.xtt GIO fd 10 read 136 bytes
> "......-ttf-*-*-*-*-*-*-*-*-*-*-*-*-*......"
> 403 XF86_SVGA.xtt RET read 136/0x88
> 403 XF86_SVGA.xtt CALL madvise(0x8470000,0x1000,0x5)
> 403 XF86_SVGA.xtt RET madvise 0
> 403 XF86_SVGA.xtt CALL madvise(0x846f000,0x1000,0x5)
> 403 XF86_SVGA.xtt RET madvise 0
> 403 XF86_SVGA.xtt CALL munmap(0x28683000,0x5000)
> 403 XF86_SVGA.xtt RET munmap 0
> 403 XF86_SVGA.xtt CALL madvise(0x846e000,0x1000,0x5)
> 403 XF86_SVGA.xtt RET madvise 0
> 403 XF86_SVGA.xtt CALL gettimeofday(0xefbfd8bc,0)
> 403 XF86_SVGA.xtt RET gettimeofday 0
> 403 XF86_SVGA.xtt CALL break(0x8496000)
> 403 XF86_SVGA.xtt RET break 0
> 403 XF86_SVGA.xtt CALL open(0x846e000,0,0x282dda14)
> 403 XF86_SVGA.xtt NAMI "/usr/X11R6/lib/X11/fonts/TrueType/ariblk.ttf"
> 403 XF86_SVGA.xtt RET open 11/0xb
> 403 XF86_SVGA.xtt CALL fstat(0xb,0xefbfb55c)
> 403 XF86_SVGA.xtt RET fstat 0
> 403 XF86_SVGA.xtt CALL mmap(0,0x19638,0x1,0x2,0xb,0,0,0)
> 403 XF86_SVGA.xtt RET mmap 677953536/0x2868c000
> 403 XF86_SVGA.xtt CALL close(0xb)
> 403 XF86_SVGA.xtt RET close 0
> 403 XF86_SVGA.xtt CALL stat(0x282bf581,0xefbfb584)
> 403 XF86_SVGA.xtt NAMI "/usr/X11R6/lib/modules/codeconv"
> 403 XF86_SVGA.xtt RET stat 0
> 403 XF86_SVGA.xtt CALL open(0x282bf581,0x4,0x283743a0)
> 403 XF86_SVGA.xtt NAMI "/usr/X11R6/lib/modules/codeconv"
> 403 XF86_SVGA.xtt RET open 11/0xb
> 403 XF86_SVGA.xtt CALL fstat(0xb,0xefbfb584)
> 403 XF86_SVGA.xtt RET fstat 0
> 403 XF86_SVGA.xtt CALL fcntl(0xb,0x2,0x1)
> 403 XF86_SVGA.xtt RET fcntl 0
> 403 XF86_SVGA.xtt CALL fstatfs(0xb,0xefbfb484)
> 403 XF86_SVGA.xtt RET fstatfs 0
> 403 XF86_SVGA.xtt CALL getdirentries(0xb,0x847b000,0x1000,0x8452294)
> 403 XF86_SVGA.xtt RET getdirentries 512/0x200
> 403 XF86_SVGA.xtt CALL open(0x28271040,0,0x4000f930)
> 403 XF86_SVGA.xtt NAMI "/usr/X11R6/lib/modules/codeconv/ISO8859_1.so"
> 403 XF86_SVGA.xtt RET open 12/0xc
> 403 XF86_SVGA.xtt CALL read(0xc,0xefbfa5b8,0x1000)
> 403 XF86_SVGA.xtt GIO fd 12 read 4096 bytes
> "......"
> 403 XF86_SVGA.xtt RET read 4096/0x1000
> 403 XF86_SVGA.xtt CALL mmap(0,0x2000,0x5,0x2,0xc,0,0,0)
> 403 XF86_SVGA.xtt RET mmap 677339136/0x285f6000
> 403 XF86_SVGA.xtt CALL mmap(0x285f7000,0x1000,0x3,0x12,0xc,0,0,0)
> 403 XF86_SVGA.xtt RET mmap 677343232/0x285f7000
> 403 XF86_SVGA.xtt CALL close(0xc)
> 403 XF86_SVGA.xtt RET close 0
> 403 XF86_SVGA.xtt CALL munmap(0x285f6000,0x2000)
> 403 XF86_SVGA.xtt RET munmap 0
> 403 XF86_SVGA.xtt CALL open(0x28271040,0,0x4000f930)
> 403 XF86_SVGA.xtt NAMI "/usr/X11R6/lib/modules/codeconv/BIG5.so"
> 403 XF86_SVGA.xtt RET open 12/0xc
> 403 XF86_SVGA.xtt CALL read(0xc,0xefbfa5b8,0x1000)
> 403 XF86_SVGA.xtt GIO fd 12 read 4096 bytes
> "......"
> 403 XF86_SVGA.xtt RET read 4096/0x1000
> 403 XF86_SVGA.xtt CALL mmap(0,0xa000,0x5,0x2,0xc,0,0,0)
> 403 XF86_SVGA.xtt RET mmap 678060032/0x286a6000
> 403 XF86_SVGA.xtt CALL mmap(0x286a7000,0x9000,0x3,0x12,0xc,0,0,0)
> 403 XF86_SVGA.xtt RET mmap 678064128/0x286a7000
> 403 XF86_SVGA.xtt CALL close(0xc)
> 403 XF86_SVGA.xtt RET close 0
>
> And why there are loaded modules "ISO8859_1.so" and "BIG5.so"?
> In my fonts.dir there is only one line for ariblk.ttf:
>
> ariblk.ttf -ttf-arial black-medium-r-normal-tt-0-0-0-0-p-0-iso8859-2
>
> Why nodule "ISO8859_2.so" is not loaded?
>
> Thanks.
>
> --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--
> 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
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 08:44:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA20810
for freebsd-current-outgoing; Wed, 4 Nov 1998 08:44:32 -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 IAA20760
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 08:44:22 -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 AAA00847;
Thu, 5 Nov 1998 00:42:45 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811041642.AAA00847@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman <green@unixhelp.org>
cc: "George W. Dinolt" <george.w.dinolt@lmco.com>, current@FreeBSD.ORG
Subject: Re: mount_msdos is dead :(
In-reply-to: Your message of "Wed, 04 Nov 1998 11:23:13 EST."
<Pine.BSF.4.05.9811041122380.17234-100000@zone.syracuse.net>
Date: Thu, 05 Nov 1998 00:42:45 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Feldman wrote:
> I completely rebuilt an ELF kernel and all modules yesterday. I verify
> that this problem did not exist on 3.0-RELEASE.
>
> Cheers,
> Brian Feldman
Hmm, it works for me..
# mount -tmsdos /dev/fd0 /mnt
# df
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/da0s1a 31775 28613 620 98% /
/dev/da0s1e 297423 204048 69582 75% /usr
/dev/da0s1f 78975 5092 67565 7% /var
/dev/da0s1g 3521630 3067266 172634 95% /home
procfs 4 4 0 100% /proc
spinner:/usr/X11R6 1214255 899466 217649 81% /usr/X11R6
spinner:/home 1589119 1211184 250806 83% /spinner/home
spinner:/home2 1214255 899466 217649 81% /spinner/home2
haywire:/home 3098894 2563044 287939 90% /haywire/home
/dev/fd0 1423 102 1321 7% /mnt
#
I can't for the life of me imagine what might be causing this.. ENOTBLK
comes from the per-FS mount code and it's a result of discovering the
device vnode is not type VBLK. The mount_msdos code is essentially the
same as the ffs mount code.
I assume this is with a statically configured kernel.. ELF? aout? Can
you do a 'kldstat -v' and see what's loaded?
>
>
> On Tue, 3 Nov 1998, George W. Dinolt wrote:
>
> > I
> > Brian Feldman wrote:
> >
> > > I'm attaching a script that shows this.
> > >
> > > Brian Feldman
> > >
> > > Script started on Tue Nov 3 22:07:44 1998
> > > {"/home/green"}# mount_msdos /dev/fd0 /m^H ^Hfloppy^M^M
> > > mount_msdos: /dev/fd0: Block device required^M
> > > {"/home/green"}# ls -l /dev/fd0^M^M
> > > brw------- 1 root operator 2, 0 Nov 3 20:47 /dev/fd0^M
> > > {"/home/green"}# dd if=/dev/rfd0 of=flop^M^M
> > > 2880+0 records in^M
> > > 2880+0 records out^M
> > > 1474560 bytes transferred in 52.781845 secs (27937 bytes/sec)^M
> > > {"/home/green"}# vnconfig -c /dev/vn0 /home/green/flop^M^M
> > > {"/home/green"}# mount_msdos /dev/vn0 /floppy^M^M
> > > mount_msdos: /dev/vn0: Block device required^M
> > > {"/home/green"}# ls -l /dev/vn0^M^M
> > > brw-r----- 1 root operator 15, 0x00010002 Jul 24 08:52 /dev/vn0^M
> > > {"/home/green"}# ^D^M^M
> > >
> > > Script done on Tue Nov 3 22:11:16 1998
> > >
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-current" in the body of the message
> >
> > I ran into similar problems several days ago after some large changes to
> > the kernel were committed. I think that if you rebuild your lkm modules
> > so they match the kernel you are running things will work. At least they
> > did for me. I haven't tried an elf kernel for a while, but I suspect the
> > same would happen if the '.ko' modules were not in sync with the kernel.
> >
> > Regards,
> > George Dinolt
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 4 09:14:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA25695
for freebsd-current-outgoing; Wed, 4 Nov 1998 09:14:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25686
for <current@freebsd.org>; Wed, 4 Nov 1998 09:14:09 -0800 (PST)
(envelope-from jdp@austin.polstra.com)
Received: from austin.polstra.com (jdp@localhost)
by austin.polstra.com (8.9.1/8.9.1) with ESMTP id JAA22690;
Wed, 4 Nov 1998 09:13:41 -0800 (PST)
(envelope-from jdp)
Message-Id: <199811041713.JAA22690@austin.polstra.com>
To: karl@Denninger.Net
Subject: Re: samba smbd core dumps & -current
In-Reply-To: <19981104075828.C8935@Denninger.Net>
References: <412566B2.004DC9C6.00@bfc.dk> <19981104075828.C8935@Denninger.Net>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Date: Wed, 04 Nov 1998 09:13:41 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <19981104075828.C8935@Denninger.Net>,
Karl Denninger <karl@Denninger.Net> wrote:
> Again, I've not seen this, I run -CURRENT, and I rebuilt SAMBA recently (a
> couple of weeks ago) to be an ELF-ized binary.
Different /etc/malloc.conf settings, maybe?
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 09:28:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA28648
for freebsd-current-outgoing; Wed, 4 Nov 1998 09:28:47 -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 JAA28623
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 09:28: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 MAA13243;
Wed, 4 Nov 1998 12:26:45 -0500 (EST)
Date: Wed, 4 Nov 1998 12:26:45 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Brian Feldman <green@unixhelp.org>
cc: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>,
"freebsd-current@freebsd.org" <freebsd-current@FreeBSD.ORG>
Subject: Re: ELFoized xtt-SVGA-1.0 & TrueType fonts => HANG
In-Reply-To: <Pine.BSF.4.05.9811041133220.17234-100000@zone.syracuse.net>
Message-ID: <Pine.BSF.4.05.9811041219260.523-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 Wed, 4 Nov 1998, Brian Feldman wrote:
> Xtt is slow to load fonts, and hangs while loading them for a sec. Same
> with plain X fonts, too (X itself, not Xtt)
I found Xtt to be extremely flakey and astonishingly complicated.
Meanwhile, these patches for X11 are pretty simple and work
great: http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/
I haven't tried the 1.0.2 version yet, but the 1.0.1 version was
easy to build into the XFree86 port. Just "make extract", then
unpack the TrueType redering code in the specified directory,
apply path and then "make" the port. Then your X servers and xfs
magically handle truetype fonts.
Then go grab the "Web Fonts" package from Microsoft and all the
web pages out there designed on Windows platforms look right on
Unix. :)
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 09:51:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA01531
for freebsd-current-outgoing; Wed, 4 Nov 1998 09:51:39 -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 JAA01510
for <freebsd-current@freebsd.org>; Wed, 4 Nov 1998 09:51:33 -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 SAA19517;
Wed, 4 Nov 1998 18:51:22 +0100 (MET)
Received: (from cejkar@localhost)
by kazi.dcse.fee.vutbr.cz (8.8.8/8.8.8) id SAA22212;
Wed, 4 Nov 1998 18:51:22 +0100 (CET)
From: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>
Message-Id: <199811041751.SAA22212@kazi.dcse.fee.vutbr.cz>
Subject: Re: ELFoized xtt-SVGA-1.0 & TrueType fonts => HANG
In-Reply-To: <Pine.BSF.4.05.9811041219260.523-100000@fallout.campusview.indiana.edu> from John Fieber at "Nov 4, 98 12:26:45 pm"
To: jfieber@indiana.edu (John Fieber)
Date: Wed, 4 Nov 1998 18:51:22 +0100 (CET)
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
> I found Xtt to be extremely flakey and astonishingly complicated.
>
> Meanwhile, these patches for X11 are pretty simple and work
> great: http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/
So somebody can make official port xfsft...
Yes - there are alternatives, but I want to know if ports
XttXF86srv-* are for ELF really broken or not. Has anybody XttXF86srv-*
(in ELF form) working? (Better: With iso8859-2 exported fonts.)
--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--
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 Wed Nov 4 09:57:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA02897
for freebsd-current-outgoing; Wed, 4 Nov 1998 09:57:23 -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 JAA02891
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 09:57:19 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id JAA27747; Wed, 4 Nov 1998 09:57:10 -0800 (PST)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
id sma027739; Wed Nov 4 09:56:43 1998
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id JAA12092; Wed, 4 Nov 1998 09:56:43 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199811041756.JAA12092@bubba.whistle.com>
Subject: Re: Current 'make world' warnings cleanup
In-Reply-To: <XFMail.981104091025.asmodai@wxs.nl> from Jeroen Ruigrok/Asmodai at "Nov 4, 98 09:10:25 am"
To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai)
Date: Wed, 4 Nov 1998 09:56:43 -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
Jeroen Ruigrok/Asmodai writes:
> >> Sounds good. Just one thing: don't fall prey to the temptation to
> >> fix all the pointer mismatch warnings by blindly inserting casts just
> >> to make the compiler shut up. That's a common mistake, and as often
> >> as not it simply hides the real problem from the compiler rather than
> >> fixing it.
> >
> > Another gotcha when doing this.. often "unused variable" warnings
> > happen because there is a variable declared that is only used
> > when certain #ifdef's are true. The solution in these cases is
> > not to remove the variable, but to enclose it's declaration
> > within equivalent #ifdef's..
>
> So in general someone forgot to put them between the appropriate definition
> statements right? Either by mistake or whatever...
Not sure what you mean by that.. I think so..
The point is.. depending on what #ifdef's you have, a variable
may go from used to unused or vice versa. This can be avoided by
having the declaration of the variable happen if-and-only-if the
variable is used. Same goes for static functions in a file.
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 09:57:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA02931
for freebsd-current-outgoing; Wed, 4 Nov 1998 09:57:41 -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 JAA02926
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 09:57:39 -0800 (PST)
(envelope-from karl@Genesis.Denninger.Net)
Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id LAA09608; Wed, 4 Nov 1998 11:57:21 -0600 (CST)
Message-ID: <19981104115721.C9568@Denninger.Net>
Date: Wed, 4 Nov 1998 11:57:21 -0600
From: Karl Denninger <karl@Denninger.Net>
To: John Polstra <jdp@polstra.com>
Cc: current@FreeBSD.ORG
Subject: Re: samba smbd core dumps & -current
References: <412566B2.004DC9C6.00@bfc.dk> <19981104075828.C8935@Denninger.Net> <199811041713.JAA22690@austin.polstra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199811041713.JAA22690@austin.polstra.com>; from John Polstra on Wed, Nov 04, 1998 at 09:13:41AM -0800
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
Possibly. I have no such file, ergo, I take the defaults :-)
--
--
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.
On Wed, Nov 04, 1998 at 09:13:41AM -0800, John Polstra wrote:
> In article <19981104075828.C8935@Denninger.Net>,
> Karl Denninger <karl@Denninger.Net> wrote:
>
> > Again, I've not seen this, I run -CURRENT, and I rebuilt SAMBA recently (a
> > couple of weeks ago) to be an ELF-ized binary.
>
> Different /etc/malloc.conf settings, maybe?
>
> John
> --
> John Polstra jdp@polstra.com
> John D. Polstra & Co., Inc. Seattle, Washington USA
> "Nobody ever went broke underestimating the taste of the American public."
> -- H. L. Mencken
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 10:05:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA03953
for freebsd-current-outgoing; Wed, 4 Nov 1998 10:05:15 -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 KAA03947;
Wed, 4 Nov 1998 10:05:09 -0800 (PST)
(envelope-from larry@marso.com)
Received: (from larry@localhost)
by second.dialup.access.net (8.9.1/8.8.8) id NAA05164;
Wed, 4 Nov 1998 13:04:00 -0500 (EST)
(envelope-from larry)
Date: Wed, 4 Nov 1998 13:04:00 -0500
From: "Larry S. Marso" <larry@marso.com>
To: freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: 3.0-Release breaks pt0 (scanner) working under Aug. current
Message-ID: <19981104130400.A5152@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 just upgraded from an August 3.0-current (non-CAMed) to 3.0-Release
(CAMed).
I run xvscan to operate my HP ScanJet 6100C using the /dev/pt0 driver,
which works great on the August 3.0-current system.
However, on 3.0-Release, the software doesn't recognize the scanner on
/dev/pt0.
I'm jumping back and froth between the new and old kernels. Here are
my log entries while booting up. Is this a known problem? What other
information can I provide to track this down? Thank you.
Non-CAM'd August 3.0-current:
Nov 4 12:53:35 lsmarso /kernel.old: pt0 at scbus0 target 5 lun 0
Nov 4 12:53:35 lsmarso /kernel.old: pt0: <HP C2520A 3644> type 3 fixed
SCSI 2
Nov 4 12:53:35 lsmarso /kernel.old: pt0: Processor
//////////////
CAM'd 3.0-release:
Nov 4 12:10:39 lsmarso /kernel: pt0 at ahc0 bus 0 target 5 lun 0
Nov 4 12:10:39 lsmarso /kernel: pt0: <HP C2520A 3644> Fixed Processor
SCSI2 device
Nov 4 12:10:39 lsmarso /kernel: pt0: 3.300MB/s transfers
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 Wed Nov 4 10: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 KAA04927
for freebsd-current-outgoing; Wed, 4 Nov 1998 10:16: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 KAA04915
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 10:16:12 -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 CAA01590;
Thu, 5 Nov 1998 02:15:20 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811041815.CAA01590@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>
cc: jfieber@indiana.edu (John Fieber), freebsd-current@FreeBSD.ORG
Subject: Re: ELFoized xtt-SVGA-1.0 & TrueType fonts => HANG
In-reply-to: Your message of "Wed, 04 Nov 1998 18:51:22 +0100."
<199811041751.SAA22212@kazi.dcse.fee.vutbr.cz>
Date: Thu, 05 Nov 1998 02:15:19 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Cejka Rudolf wrote:
>
> > I found Xtt to be extremely flakey and astonishingly complicated.
> >
> > Meanwhile, these patches for X11 are pretty simple and work
> > great: http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/
>
> So somebody can make official port xfsft...
I use the freetype (ft) libs built directly into the server. Ariel on X11
is disturbing at first. :-) I had a lot of trouble with xfstt, but that
was around the same that a change to the socket system disturbed X11 in
general.
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 4 10:33:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA07364
for freebsd-current-outgoing; Wed, 4 Nov 1998 10:33:07 -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 KAA07352
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 10:33:00 -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 TAA17598;
Wed, 4 Nov 1998 19:30:06 +0100 (MET)
Received: (from andreas@localhost)
by klemm.gtn.com (8.8.8/8.8.8) id TAA07816;
Wed, 4 Nov 1998 19:07:42 +0100 (CET)
(envelope-from andreas)
Message-ID: <19981104190741.A994@klemm.gtn.com>
Date: Wed, 4 Nov 1998 19:07:41 +0100
From: Andreas Klemm <andreas@klemm.gtn.com>
To: Peter Wemm <peter@netplex.com.au>, shimon@simon-shapiro.org
Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG,
Stephen Hocking-Senior Programmer PGS Tensor Perth <shocking@prth.pgs.com>
Subject: Re: Weird make world error
References: <XFMail.981104085218.shimon@simon-shapiro.org> <199811041323.VAA29986@spinner.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199811041323.VAA29986@spinner.netplex.com.au>; from Peter Wemm on Wed, Nov 04, 1998 at 09:23:25PM +0800
X-Disclaimer: A free society is one where it is safe to be unpopular
X-Operating-System: FreeBSD 2.2.7-STABLE SMP
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Nov 04, 1998 at 09:23:25PM +0800, Peter Wemm wrote:
> The buildworld environment builds (completely) it's own toolchain and
> restricts the $PATH to the tools that it has built. When I turned on the
> src/sys/modules SUBDIR, it (for the first time) needed the gensetdefs
> command, which was missing from the list of tools needed. "oops". Sorry
> folks.
The aout to elf update is also broken by this
===> sys/modules
===> sys/modules/atapi
@ -> /home/src/sys
machine -> /home/src/sys/i386/include
echo "#define NWDC 2" > wdc.h
echo "#define ATAPI 1"> opt_atapi.h
cc -O -pipe -DATAPI_MODULE -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -
Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-
arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -DKLD_MODULE
-nostdinc -I- -I/usr/obj/elf/home/src/sys/modules/atapi -I/usr/obj/elf/home/src
/sys/modules/atapi/@ -I/usr/obj/elf/home/src/tmp/usr/include -c /home/src/sys/mo
dules/atapi/../../i386/isa/atapi.c
gensetdefs atapi.o
gensetdefs: not found
*** 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 Wed Nov 4 10:36:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA07892
for freebsd-current-outgoing; Wed, 4 Nov 1998 10:36:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07773
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 10:36:04 -0800 (PST)
(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id UAA19209;
Wed, 4 Nov 1998 20:35:39 +0200 (SAT)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199811041835.UAA19209@zibbi.mikom.csir.co.za>
Subject: Re: cvsup server down?
In-Reply-To: <199811040605.IAA23594@gratis.grondar.za> from Mark Murray at "Nov 4, 98 08:05:02 am"
To: mark@grondar.za (Mark Murray)
Date: Wed, 4 Nov 1998 20:35:39 +0200 (SAT)
Cc: asmodai@wxs.nl, 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 wrote:
> > Hi,
> >
> > just to get this verified:
> >
> > cvsup.internat.freebsd.org down for maintnance?
>
> Keep trying, and also try cvsup2.internet.freebsd.org; these are busy
> machines.
Well this time it wasn't because it was busy. Lightning knocked out our
link and it took a while for Telkom to fix it. :-/
John
--
John Hay -- John.Hay@mikom.csir.co.za
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 10:45:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA09266
for freebsd-current-outgoing; Wed, 4 Nov 1998 10:45:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from spa.kuis.kyoto-u.ac.jp (lab4imgw.kuis.kyoto-u.ac.jp [130.54.23.230])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09238
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 10:45:10 -0800 (PST)
(envelope-from shige@kuis.kyoto-u.ac.jp)
Received: from localhost (sirahama.kuis.kyoto-u.ac.jp [130.54.22.177])
by spa.kuis.kyoto-u.ac.jp (8.8.8/3.6Wspa) with ESMTP id DAA09650;
Thu, 5 Nov 1998 03:43:46 +0900 (JST)
To: cejkar@dcse.fee.vutbr.cz
Cc: freebsd-current@FreeBSD.ORG
Cc: shige@kuis.kyoto-u.ac.jp
Subject: Re: ELFoized xtt-SVGA-1.0 & TrueType fonts => HANG
In-Reply-To: Your message of "Wed, 4 Nov 1998 14:35:20 +0100 (CET)"
<199811041335.OAA12936@kazi.dcse.fee.vutbr.cz>
References: <199811041335.OAA12936@kazi.dcse.fee.vutbr.cz>
X-Mailer: Mew version 1.93 on Emacs 20.3 / Mule 4.0
=?iso-2022-jp?B?KBskQjJWMWMbKEIp?=
X-Prom-Mew: Prom-Mew 1.93 (procmail reader for Mew)
X-URL: http://www.yuasa.kuis.kyoto-u.ac.jp/~shige/
X-fingerprint: C8 BD 6A A7 CF FF 74 88 A4 B2 CC 5F C7 61 5C 9A
X-Pgp-Public-Key-URL: http://pgp5.ai.mit.edu:11371/pks/lookup?op=get&search=0x56B99BF9
X-Face-Version: X-Face utility v1.3.2 - "The Fool On The Hill"
X-Face: 34/1@t8]M!wP}sAw$~XQMzl5'O=lCIM]8=_8CE,|S)Vs4Wy@tU~A'wRi\lgWh-o&'|:zg<S
g%%4BRt%M~>>Gc?0?{^jo8(|5'Tg`yBH81.:!N9tSq*Sp6>C0q@{|&+FaM;R;KkoW1jA?QIWQ3:gNq
{O%`:ww
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <19981105034432N.shige@kuis.kyoto-u.ac.jp>
Date: Thu, 05 Nov 1998 03:44:32 +0900 (JST)
From: Shigeyuki FUKUSHIMA <shige@kuis.kyoto-u.ac.jp>
X-Dispatcher: imput version 980905(IM100)
Lines: 17
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
From: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>
Date: Wed, 4 Nov 1998 14:35:20 +0100 (CET)
Title: ELFoized xtt-SVGA-1.0 & TrueType fonts => HANG
Message-ID: <199811041335.OAA12936@kazi.dcse.fee.vutbr.cz>
> I have ELFoized -current:
> Main system (/usr/src): 98/09/28
It's old. If you use 98/10/13 or later -current, I think
you can use Xtt with no trouble!
# I can use Xtt on the latest -current.
---------
Shigeyuki FUKUSHIMA <shige@kuis.kyoto-u.ac.jp>
Dept. of Information Science, Kyoto Univ,. JAPAN
PGP Public Key:
http://pgp5.ai.mit.edu:11371/pks/lookup?op=get&search=0x56B99BF9
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 10:50:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA10101
for freebsd-current-outgoing; Wed, 4 Nov 1998 10:50:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10092
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 10:50:47 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.58.58]) by smtp05.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAA5F1F
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 18:50:34 +0100
Message-ID: <XFMail.981104195424.asmodai@wxs.nl>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Wed, 04 Nov 1998 19:54:24 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: FreeBSD Current <current@FreeBSD.ORG>
Subject: IPX Maintaner(s)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
just a few quick questions:
How is/are the maintainer(s) for the IPX stuff in FreeBSD?
Also is NLSP supported?
Thanks,
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Wed Nov 4 10:55:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA11560
for freebsd-current-outgoing; Wed, 4 Nov 1998 10:55:52 -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 KAA11541
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 10:55:49 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.58.58]) by smtp02.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAA4DB6;
Wed, 4 Nov 1998 19:55:35 +0100
Message-ID: <XFMail.981104195925.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: <199811041835.UAA19209@zibbi.mikom.csir.co.za>
Date: Wed, 04 Nov 1998 19:59:25 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: John Hay <jhay@mikom.csir.co.za>
Subject: Re: cvsup server down?
Cc: current@FreeBSD.ORG, (Mark Murray) <mark@grondar.za>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 04-Nov-98 John Hay wrote:
>> Jeroen Ruigrok/Asmodai wrote:
>> > Hi,
>> >
>> > just to get this verified:
>> >
>> > cvsup.internat.freebsd.org down for maintnance?
>>
>> Keep trying, and also try cvsup2.internet.freebsd.org; these are busy
>> machines.
>
> Well this time it wasn't because it was busy. Lightning knocked out our
> link and it took a while for Telkom to fix it. :-/
Icky!
No UPS's ?
Or did it hit the more central stuff directly?
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Wed Nov 4 10:58:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA12202
for freebsd-current-outgoing; Wed, 4 Nov 1998 10:58:06 -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 KAA12130
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 10:58:01 -0800 (PST)
(envelope-from shimon@simon-shapiro.org)
Received: (qmail 26715 invoked by uid 1000); 4 Nov 1998 20:01:38 -0000
Message-ID: <XFMail.981104150138.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: <19981104190741.A994@klemm.gtn.com>
Date: Wed, 04 Nov 1998 15:01:38 -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: Andreas Klemm <andreas@klemm.gtn.com>
Subject: Re: Weird make world error
Cc: Stephen Hocking-Senior Programmer PGS Tensor Perth <shocking@prth.pgs.com>,
current@FreeBSD.ORG, Mike Smith <mike@smith.net.au>,
Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Andreas Klemm, On 04-Nov-98 you wrote:
> On Wed, Nov 04, 1998 at 09:23:25PM +0800, Peter Wemm wrote:
> > The buildworld environment builds (completely) it's own toolchain and
> > restricts the $PATH to the tools that it has built. When I turned on
> > the
> > src/sys/modules SUBDIR, it (for the first time) needed the gensetdefs
> > command, which was missing from the list of tools needed. "oops".
> > Sorry
> > folks.
>
> The aout to elf update is also broken by this
The fix is already in and working.
Simon
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 11:05:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA13281
for freebsd-current-outgoing; Wed, 4 Nov 1998 11:05:19 -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 LAA13271
for <freebsd-current@freebsd.org>; Wed, 4 Nov 1998 11:05:15 -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 OAA13560;
Wed, 4 Nov 1998 14:05:03 -0500 (EST)
Date: Wed, 4 Nov 1998 14:05:03 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: ELFoized xtt-SVGA-1.0 & TrueType fonts => HANG
In-Reply-To: <199811041751.SAA22212@kazi.dcse.fee.vutbr.cz>
Message-ID: <Pine.BSF.4.05.9811041355160.523-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 Wed, 4 Nov 1998, Cejka Rudolf wrote:
>
> > I found Xtt to be extremely flakey and astonishingly complicated.
> >
> > Meanwhile, these patches for X11 are pretty simple and work
> > great: http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/
>
> So somebody can make official port xfsft...
It would be best as a build option of the XFree86 port as it is
basically a patch...making a separate port would probably be a
more complicated.
> Yes - there are alternatives, but I want to know if ports
> XttXF86srv-* are for ELF really broken or not.
I never got it to work right pre-elf; it crashed on about half of
the fonts I tried it with. I haven't felt a need to try it since
then because the xfsft patch to the XFree86 port works just fine.
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 11:05:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA13499
for freebsd-current-outgoing; Wed, 4 Nov 1998 11:05:45 -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 LAA13469
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 11:05:43 -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 LAA12713;
Wed, 4 Nov 1998 11:05:38 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: John Hay <jhay@mikom.csir.co.za>, current@FreeBSD.ORG,
mark@grondar.za (Mark Murray)
Subject: Re: cvsup server down?
In-reply-to: Your message of "Wed, 04 Nov 1998 19:59:25 +0100."
<XFMail.981104195925.asmodai@wxs.nl>
Date: Wed, 04 Nov 1998 11:05:37 -0800
Message-ID: <12710.910206337@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Can we get freebsd-current@freebsd.org back to being a relatively
low-traffic mailing list, folks? We can chat about lightning
strikes over in -chat, you know! :-)
Thanks...
- Jordan
> On 04-Nov-98 John Hay wrote:
> >> Jeroen Ruigrok/Asmodai wrote:
> >> > Hi,
> >> >
> >> > just to get this verified:
> >> >
> >> > cvsup.internat.freebsd.org down for maintnance?
> >>
> >> Keep trying, and also try cvsup2.internet.freebsd.org; these are busy
> >> machines.
> >
> > Well this time it wasn't because it was busy. Lightning knocked out our
> > link and it took a while for Telkom to fix it. :-/
>
> Icky!
>
> No UPS's ?
>
> Or did it hit the more central stuff directly?
>
> ---
> Jeroen Ruigrok van der Werven/Asmodai
> asmodai(at)wxs.nl
> Junior Network/Security Specialist
> FreeBSD & picoBSD: The Power to Serve...
>
> 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 4 11:21:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA16332
for freebsd-current-outgoing; Wed, 4 Nov 1998 11:21:40 -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 LAA16312
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 11:21:30 -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 UAA19185;
Wed, 4 Nov 1998 20:15:12 +0100 (MET)
Received: (from andreas@localhost)
by klemm.gtn.com (8.8.8/8.8.8) id UAA17076;
Wed, 4 Nov 1998 20:10:41 +0100 (CET)
(envelope-from andreas)
Message-ID: <19981104201041.B17059@klemm.gtn.com>
Date: Wed, 4 Nov 1998 20:10:41 +0100
From: Andreas Klemm <andreas@klemm.gtn.com>
To: shimon@simon-shapiro.org
Cc: Stephen Hocking-Senior Programmer PGS Tensor Perth <shocking@prth.pgs.com>,
current@FreeBSD.ORG, Mike Smith <mike@smith.net.au>,
Peter Wemm <peter@netplex.com.au>
Subject: Re: Weird make world error
References: <19981104190741.A994@klemm.gtn.com> <XFMail.981104150138.shimon@simon-shapiro.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <XFMail.981104150138.shimon@simon-shapiro.org>; from Simon Shapiro on Wed, Nov 04, 1998 at 03:01:38PM -0500
X-Disclaimer: A free society is one where it is safe to be unpopular
X-Operating-System: FreeBSD 2.2.7-STABLE SMP
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Wed, Nov 04, 1998 at 03:01:38PM -0500, Simon Shapiro wrote:
>
> Andreas Klemm, On 04-Nov-98 you wrote:
> > On Wed, Nov 04, 1998 at 09:23:25PM +0800, Peter Wemm wrote:
> > > The buildworld environment builds (completely) it's own toolchain and
> > > restricts the $PATH to the tools that it has built. When I turned on
> > > the
> > > src/sys/modules SUBDIR, it (for the first time) needed the gensetdefs
> > > command, which was missing from the list of tools needed. "oops".
> > > Sorry
> > > folks.
> >
> > The aout to elf update is also broken by this
>
> The fix is already in and working.
I saw it too late, the mail was already out,
thanks anyway ;-)
--
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 Wed Nov 4 11: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 LAA16628
for freebsd-current-outgoing; Wed, 4 Nov 1998 11:22:58 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16601;
Wed, 4 Nov 1998 11:22:52 -0800 (PST)
(envelope-from tlambert@usr07.primenet.com)
Received: (from daemon@localhost)
by smtp02.primenet.com (8.8.8/8.8.8) id MAA02667;
Wed, 4 Nov 1998 12:22:42 -0700 (MST)
Received: from usr07.primenet.com(206.165.6.207)
via SMTP by smtp02.primenet.com, id smtpd002642; Wed Nov 4 12:22:41 1998
Received: (from tlambert@localhost)
by usr07.primenet.com (8.8.5/8.8.5) id MAA11958;
Wed, 4 Nov 1998 12:22:38 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199811041922.MAA11958@usr07.primenet.com>
Subject: Re: Who built XFree86 with Kerberos?
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Wed, 4 Nov 1998 19:22:38 +0000 (GMT)
Cc: asami@FreeBSD.ORG, mike@smith.net.au, mark@grondar.za, sos@FreeBSD.ORG,
current@FreeBSD.ORG, ports@FreeBSD.ORG
In-Reply-To: <15699.909845800@time.cdrom.com> from "Jordan K. Hubbard" at Oct 31, 98 06:56:40 am
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I know I am weighing in way late with my 2 cents here, but...
> Thoughts?
I think there needs to be a "package-dist" constraint that you
can set on the makefiles to make them ignore the fact that
<whatever> is installed, and "build the right thing linked to
the right things".
This would let anyone do the job (or several anyones), and you
would get platform configuration independent results.
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 Wed Nov 4 11:41:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA20734
for freebsd-current-outgoing; Wed, 4 Nov 1998 11:41:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20726
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 11:41:07 -0800 (PST)
(envelope-from tlambert@usr07.primenet.com)
Received: (from daemon@localhost)
by smtp02.primenet.com (8.8.8/8.8.8) id MAA09245;
Wed, 4 Nov 1998 12:40:57 -0700 (MST)
Received: from usr07.primenet.com(206.165.6.207)
via SMTP by smtp02.primenet.com, id smtpd009216; Wed Nov 4 12:40:55 1998
Received: (from tlambert@localhost)
by usr07.primenet.com (8.8.5/8.8.5) id MAA12697;
Wed, 4 Nov 1998 12:40:49 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199811041940.MAA12697@usr07.primenet.com>
Subject: Re: lisp vs. Forth (was Re: New boot loader and alternate kernels )
To: mike@smith.net.au (Mike Smith)
Date: Wed, 4 Nov 1998 19:40:49 +0000 (GMT)
Cc: jkh@time.cdrom.com, mike@smith.net.au, parag@cgt.com, current@FreeBSD.ORG
In-Reply-To: <199811032319.PAA00900@dingo.cdrom.com> from "Mike Smith" at Nov 3, 98 03:19:27 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
> What's the feeling on the lisp vs. Forth argument?
If the FORTH Interpreter were OpenBoot syntax compliant, we
could use it to interpret ROM code on a number of cards
designed to be usable in both Intel and PPC systems.
Also, there's the whole OpenFirmware standard thing...
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 Wed Nov 4 11:49:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA21723
for freebsd-current-outgoing; Wed, 4 Nov 1998 11:49:32 -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 LAA21707
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 11:49:27 -0800 (PST)
(envelope-from tlambert@usr07.primenet.com)
Received: (from daemon@localhost)
by smtp04.primenet.com (8.8.8/8.8.8) id MAA15661;
Wed, 4 Nov 1998 12:49:19 -0700 (MST)
Received: from usr07.primenet.com(206.165.6.207)
via SMTP by smtp04.primenet.com, id smtpd015611; Wed Nov 4 12:49:10 1998
Received: (from tlambert@localhost)
by usr07.primenet.com (8.8.5/8.8.5) id MAA12999;
Wed, 4 Nov 1998 12:49:09 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199811041949.MAA12999@usr07.primenet.com>
Subject: Re: BootForth (was Re: New boot loader and alternate kernels)
To: mike@smith.net.au (Mike Smith)
Date: Wed, 4 Nov 1998 19:49:08 +0000 (GMT)
Cc: mike@smith.net.au, abial@nask.pl, current@FreeBSD.ORG
In-Reply-To: <199811010537.VAA01330@dingo.cdrom.com> from "Mike Smith" at Oct 31, 98 09:37:12 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Any Forth hackers want to play with something new and funky? In
> particular, some ideas on "standard" system-interface words would be
> handy.
You may wish to explicitly tap Wes Peters on the shoulder
(he's most often seen over on -advocacy and in Daemon News),
since he is an old FORTH hack.
I will admit to having a cartridge for my C64, and having
fought with the Sun Console (and lost) a long time ago...
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 Wed Nov 4 12: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 MAA23651
for freebsd-current-outgoing; Wed, 4 Nov 1998 12:00:21 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pinhead.parag.codegen.com (ppp-asfm10--081.sirius.net [205.134.242.81])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23614
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 12:00:12 -0800 (PST)
(envelope-from parag@pinhead.parag.codegen.com)
Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1])
by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id LAA22507;
Wed, 4 Nov 1998 11:59:27 -0800 (PST)
(envelope-from parag@pinhead.parag.codegen.com)
Message-Id: <199811041959.LAA22507@pinhead.parag.codegen.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Terry Lambert <tlambert@primenet.com>
cc: mike@smith.net.au (Mike Smith), jkh@time.cdrom.com, current@FreeBSD.ORG
Subject: Re: lisp vs. Forth (was Re: New boot loader and alternate
kernels )
In-reply-to: Your message of "Wed, 04 Nov 1998 19:40:49 GMT."
<199811041940.MAA12697@usr07.primenet.com>
X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X
]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm
X-URL: http://www.codegen.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 04 Nov 1998 11:59:27 -0800
From: Parag Patel <parag@cgt.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>If the FORTH Interpreter were OpenBoot syntax compliant, we
>could use it to interpret ROM code on a number of cards
>designed to be usable in both Intel and PPC systems.
>
>Also, there's the whole OpenFirmware standard thing...
Well, the standard's kinda big. You're going to be well into 300-400k
of code (Forth or C) to meet it. You have to start with the ANS Forth
spec, add IEEE-1275, then go through most of the recommended practices
at <http://playground.sun.com/pub/1275/home.html> plus other assorted
items.
The I2O 1.5 spec is now downloadable for free, so that's going to throw
another level of driver fun into the mix.
-- Parag
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 13:01:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA03951
for freebsd-current-outgoing; Wed, 4 Nov 1998 13:01:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03925;
Wed, 4 Nov 1998 13:01:25 -0800 (PST)
(envelope-from archie@whistle.com)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA29952; Wed, 4 Nov 1998 13:01:15 -0800 (PST)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
id sma029948; Wed Nov 4 13:01:09 1998
Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id NAA00730; Wed, 4 Nov 1998 13:01:09 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199811042101.NAA00730@bubba.whistle.com>
Subject: Re: still problems with inetd & malloc...
In-Reply-To: <199811030204.SAA18996@hub.freebsd.org> from "garman@earthling.net" at "Nov 2, 98 09:05:39 pm"
To: garman@earthling.net
Date: Wed, 4 Nov 1998 13:01:09 -0800 (PST)
Cc: jmz@FreeBSD.ORG, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
garman@earthling.net writes:
> On 2 Nov, Jean-Marc Zucconi wrote:
> > There is a fix (it works for me). Look for
> > Subject: Re: bin/8183: Signal handlers in inetd.c are unsafe
> > in the archives.
> >
> thanks for the pointer. it's working so far... so now the $64,000
> question is: why hasn't this been committed?
According to http://www.freebsd.org/cgi/query-pr.cgi?pr=8183,
des@freebsd.org is handling it.. maybe he's still working on 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 Wed Nov 4 13:59:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA13986
for freebsd-current-outgoing; Wed, 4 Nov 1998 13:59:53 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from garman.dyn.ml.org (pm106-12.dialip.mich.net [192.195.231.214])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA13976
for <current@freebsd.org>; Wed, 4 Nov 1998 13:59:50 -0800 (PST)
(envelope-from garman@garman.dyn.ml.org)
Message-Id: <199811042159.NAA13976@hub.freebsd.org>
Received: (qmail 5069 invoked from smtpd); 4 Nov 1998 22:01:04 -0000
Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1)
by localhost.garman.net with SMTP; 4 Nov 1998 22:01:04 -0000
Date: Wed, 4 Nov 1998 17:01:03 -0500 (EST)
From: garman@earthling.net
Reply-To: garman@earthling.net
Subject: Re: samba smbd core dumps & -current
To: current@FreeBSD.ORG
cc: npe@bfc.dk
In-Reply-To: <412566B2.004DC9C6.00@bfc.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 14:01:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA14379
for freebsd-current-outgoing; Wed, 4 Nov 1998 14:01:15 -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 OAA14360
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 14:01:09 -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 XAA25054
for current@FreeBSD.ORG; Wed, 4 Nov 1998 23:00:11 +0100 (MET)
Received: (from andreas@localhost)
by klemm.gtn.com (8.8.8/8.8.8) id WAA06070
for current@FreeBSD.ORG; Wed, 4 Nov 1998 22:52:29 +0100 (CET)
(envelope-from andreas)
Message-ID: <19981104225229.A6063@klemm.gtn.com>
Date: Wed, 4 Nov 1998 22:52:29 +0100
From: Andreas Klemm <andreas@klemm.gtn.com>
To: current@FreeBSD.ORG
Subject: make aout-to-elf-build: ELF interpreter /usr/libexec/ld-elf.so.1 not found
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 2.2.7-STABLE SMP
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
===> sys/modules/linux
@ -> /home/src/sys
machine -> /home/src/sys/i386/include
cc -c -O -pipe -DCOMPAT_LINUX -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/elf/home/src/sys/modules/linux -I/usr/obj/elf/home/src/sys/modules/linux/@ -I/usr/obj/elf/home/src/tmp/usr/include -UKERNEL /home/src/sys/modules/linux/../../i386/linux/linux_genassym.c
cc -O -pipe -DCOMPAT_LINUX -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/elf/home/src/sys/modules/linux -I/usr/obj/elf/home/src/sys/modules/linux/@ -I/usr/obj/elf/home/src/tmp/usr/include -o linux_genassym linux_genassym.o
./linux_genassym > linux_assym.h
ELF interpreter /usr/libexec/ld-elf.so.1 not found
Abort trap
*** Error code 134
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
--
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 Wed Nov 4 14: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 OAA14397
for freebsd-current-outgoing; Wed, 4 Nov 1998 14:01:19 -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 OAA14382
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 14:01:15 -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 XAA25048
for current@FreeBSD.ORG; Wed, 4 Nov 1998 23:00:08 +0100 (MET)
Received: (from andreas@localhost)
by klemm.gtn.com (8.8.8/8.8.8) id WAA00896
for current@FreeBSD.ORG; Wed, 4 Nov 1998 22:46:06 +0100 (CET)
(envelope-from andreas)
Message-ID: <19981104224604.A28969@klemm.gtn.com>
Date: Wed, 4 Nov 1998 22:46:04 +0100
From: Andreas Klemm <andreas@klemm.gtn.com>
To: current@FreeBSD.ORG
Subject: ELF interpreter /usr/libexec/ld-elf.so.1 not found, Abort trap
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 2.2.7-STABLE SMP
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
When doing a make aout-to-elf-build from a 2.2.7 system
[...]
>>> Cleaning up the temporary aout build tree
>>> Making make
>>> Making mtree
>>> Making hierarchy
>>> Cleaning up the aout obj tree
>>> Rebuilding the aout obj tree
>>> Rebuilding aout bootstrap tools
>>> Rebuilding tools necessary to build the include files
>>> Rebuilding /usr/include
>>> Rebuilding bootstrap libraries
>>> Rebuilding tools needed to build libraries
>>> Rebuilding all other tools needed to build the aout world
>>> Building aout libraries
>>> Building everything..
>>> Cleaning up the temporary elf build tree
>>> Making hierarchy
>>> Cleaning up the elf obj tree
>>> Rebuilding the elf obj tree
>>> Rebuilding /usr/include
>>> Rebuilding bootstrap libraries
>>> Building elf libraries
>>> Building everything..
[...]
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
Manifying B::Xref.3
ELF interpreter /usr/libexec/ld-elf.so.1 not found
Abort trap
Manifying B.3
ELF interpreter /usr/libexec/ld-elf.so.1 not found
Abort trap
Manifying O.3
ELF interpreter /usr/libexec/ld-elf.so.1 not found
Abort trap
Manifying DB_File.3
ELF interpreter /usr/libexec/ld-elf.so.1 not found
Abort trap
Manifying Data::Dumper.3
ELF interpreter /usr/libexec/ld-elf.so.1 not found
Abort trap
Manifying DynaLoader.3
ELF interpreter /usr/libexec/ld-elf.so.1 not found
Abort trap
Manifying Fcntl.3
ELF interpreter /usr/libexec/ld-elf.so.1 not found
Abort trap
Manifying GDBM_File.3
--
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 Wed Nov 4 14:07:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA15087
for freebsd-current-outgoing; Wed, 4 Nov 1998 14:07:43 -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 OAA15080
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 14:07:39 -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 XAA09937;
Wed, 4 Nov 1998 23:07:12 +0100 (MET)
Received: (from son@localhost)
by teaser.fr (8.9.1/8.8.5) id XAA00946;
Wed, 4 Nov 1998 23:38:58 GMT
Message-ID: <19981104233858.62040@breizh.prism.uvsq.fr>
Date: Wed, 4 Nov 1998 23:38:58 +0000
From: Nicolas Souchu <nsouch@teaser.fr>
To: Kelvin Farmer <erkaf@my-dejanews.com>
Cc: current@FreeBSD.ORG, Marc Bouget <mbouget@club-internet.fr>
Subject: Re: make kernel fails:booktree848.c
References: <HLNHMEEEIPNOHAAA@my-dejanews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81e
In-Reply-To: <HLNHMEEEIPNOHAAA@my-dejanews.com>; from Kelvin Farmer on Mon, Nov 02, 1998 at 05:08:22PM -0700
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 Mon, Nov 02, 1998 at 05:08:22PM -0700, Kelvin Farmer wrote:
>
>
>--
>
>On Mon, 02 Nov 1998 15:25:44 Kelvin Farmer wrote:
>>I just updated my src tree (cvsup) but now I can't make a kernel, since i get the following error:
>
>Nevermind... I saw the re:bktro broken thread and figured it out. The instructions in LINT are NOT clear about what to add to make bktr0 work.
LINT is now updated.
>
>adding:controller smbus0
>device smb0 at smbus?
>
>controller iicbus0
>controller icbb0
>device ic0 at iicbus?
>device iic0 at iicbus?
>device iicsmb0 at iicbus?
>device iicbb0 at iicbus?
>device bktr0
>
>to the config file works, and produces on bootup:
>
>bktr0: <BrookTree 848> rev 0x11 int a irq 10 on pci0.19.0
>bti2c0: <bt848 Hard/Soft I2C controller>
>iicbb0: <I2C generic bit-banging driver> on bti2c0
>iicbus0: <Philips I2C bus> on iicbb0 addr 0xf0
>Probing for devices on iicbus0: <c0> <c1> <c2> <c3>
>iicsmb0: <I2C to SMB bridge> on iicbus0
>smbus0: <System Management Bus> on iicsmb0
>smbus1: <System Management Bus> on bti2c0
>Miro TV, Temic NTSC tuner.
Hmm, it seems to work then.
>
>I suppose detailed info on what exactly IS needed is yet to come... =)
iicbus, iicbb, smbus are madatory. They have manpages.
>Cheers
>Kelvin.
>
>
>
>-----== Sent via Deja News, The Discussion Network ==-----
>http://www.dejanews.com/ Easy access to 50,000+ discussion forums
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-current" in the body of the message
>
--
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 Wed Nov 4 14:10:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA15626
for freebsd-current-outgoing; Wed, 4 Nov 1998 14:10:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from garman.dyn.ml.org (pm106-12.dialip.mich.net [192.195.231.214])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA15609
for <current@freebsd.org>; Wed, 4 Nov 1998 14:10:16 -0800 (PST)
(envelope-from garman@garman.dyn.ml.org)
Message-Id: <199811042210.OAA15609@hub.freebsd.org>
Received: (qmail 5163 invoked from smtpd); 4 Nov 1998 22:11:29 -0000
Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1)
by localhost.garman.net with SMTP; 4 Nov 1998 22:11:29 -0000
Date: Wed, 4 Nov 1998 17:11:28 -0500 (EST)
From: garman@earthling.net
Reply-To: garman@earthling.net
Subject: Re: samba smbd core dumps & -current
To: current@FreeBSD.ORG
In-Reply-To: <412566B2.004DC9C6.00@bfc.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 14:11:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA15789
for freebsd-current-outgoing; Wed, 4 Nov 1998 14:11: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 OAA15666;
Wed, 4 Nov 1998 14:10:37 -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 XAA04822;
Wed, 4 Nov 1998 23:07:21 +0100 (MET)
Received: (from son@localhost)
by teaser.fr (8.9.1/8.8.5) id XAA00938;
Wed, 4 Nov 1998 23:36:20 GMT
Message-ID: <19981104233620.20933@breizh.prism.uvsq.fr>
Date: Wed, 4 Nov 1998 23:36:20 +0000
From: Nicolas Souchu <nsouch@teaser.fr>
To: garman@earthling.net
Cc: gmarco@giovannelli.it, current@FreeBSD.ORG, multimedia@FreeBSD.ORG
Subject: Re: bt848 broken ?
References: <199811021744.SAA00799@www.giovannelli.it> <199811030027.QAA05770@hub.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81e
In-Reply-To: <199811030027.QAA05770@hub.freebsd.org>; from garman@earthling.net on Mon, Nov 02, 1998 at 07:28:01PM -0500
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 Mon, Nov 02, 1998 at 07:28:01PM -0500, garman@earthling.net wrote:
Thanks Jason. I forgot to update LINT when commiting bktr changes. done.
>
>On 2 Nov, Gianmarco Giovannelli wrote:
>> It's a couple of days that I receive this error when I try to compile the kernel
>> (cvsupped twice a day, last five minutes ago 981102 18:45 CET)
>>
>> .c ../../libkern/strcat.c ../../libkern/strcmp.c ../../libkern/strcpy.c
>> ../../libkern/strlen.c ../../libkern/strncmp.c ../../libkern/strncpy.c
>> ../../libkern/udivdi3.c ../../libkern/umoddi3.c swapkernel.c ioconf.c param.c
>> vnode_if.c config.c
>> ../../pci/brooktree848.c:361: smbus_if.h: No such file or directory
>> ../../pci/brooktree848.c:362: iicbus_if.h: No such file or directory
>> ../../pci/bt848_i2c.c:61: iicbb_if.h: No such file or directory
>> ../../pci/bt848_i2c.c:62: smbus_if.h: No such file or directory
>> mkdep: compile failed
>> *** Error code 1
>>
>you need to add the smbus0 and iicbus0 devices, like so:
>
>controller smbus0
>device smb0 at smbus?
>
>controller iicbus0
>device ic0 at iicbus?
>device iic0 at iicbus?
>device iicsmb0 at iicbus?
>device iicbb0 at iicbus?
This last declaration should be rather 'controller iicbb0'
>
>i don't know if you need all of the devices, but they converted the
>bktr driver to use thew common iicbus code.
Actually, "only" iicbus, smbus, iicbb are mandatory.
--
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 Wed Nov 4 14:11:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA15851
for freebsd-current-outgoing; Wed, 4 Nov 1998 14:11:37 -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 OAA15840
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 14:11:34 -0800 (PST)
(envelope-from yds@ingress.com)
Received: (qmail 18925 invoked from network); 4 Nov 1998 22:11:20 -0000
Received: from ichiban.ingress.com (HELO ichiban) (205.230.64.31)
by paris.dppl.com with SMTP; 4 Nov 1998 22:11:20 -0000
Message-ID: <030501be0840$0d261000$1f40e6cd@ichiban.ingress.com>
From: "Yarema" <yds@ingress.com>
To: <current@FreeBSD.ORG>
Subject: Re: Problems with make aout-to-elf-buld
Date: Wed, 4 Nov 1998 17:11:20 -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.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>While trying to do a make aout-to-elf-build I'm getting this error:
>
>===> sys/modules/atapi
>@ -> /usr/src/sys
>machine -> /usr/src/sys/i386/include
>echo "#define NWDC 2" > wdc.h
>echo "#define ATAPI 1"> opt_atapi.h
>cc -O -pipe -DATAPI_MODULE -DKERNEL -Wreturn-type -Wcomment
>-Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes
>-Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat
>-fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/elf/usr/src
/sys/modules/atapi
>-I/usr/obj/elf/usr/src/sys/modules/atapi/@ -I/usr/obj/elf/usr/src/tmp/usr/i
nclude -c
>/usr/src/sys/modules/atapi/../../i386/isa/atapi.c
>gensetdefs atapi.o
>gensetdefs: not found
>*** Error code 1
>
>
>Any ideas?
Yeah, I ran into the same problem last night. For some reason
/usr/obj/aout/usr/src/usr.bin/gensetdefs/gensetdefs doesn't get installed
into /usr/obj/aout/usr/src/tmp/usr/bin/
After manually copying the file and running
make -DNOCLEAN aout-to-elf-build
I got past that hurdle although I still wasn't able to do a 2.2.7-STABLE to
3.0-CURRENT aout-to-elf upgrade in one shot. I settled for installing a
3.0-CURRENT aout and converting to elf once I'm more familiar with 3.0 :(
--
Yarema
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 14:34:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA20026
for freebsd-current-outgoing; Wed, 4 Nov 1998 14:34:14 -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 OAA20017
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 14:34:12 -0800 (PST)
(envelope-from yds@ingress.com)
Received: (qmail 19228 invoked from network); 4 Nov 1998 22:34:03 -0000
Received: from ichiban.ingress.com (HELO ichiban) (205.230.64.31)
by paris.dppl.com with SMTP; 4 Nov 1998 22:34:03 -0000
Message-ID: <035901be0843$39a63ee0$1f40e6cd@ichiban.ingress.com>
From: "Yarema" <yds@ingress.com>
To: <current@FreeBSD.ORG>
Subject: 3.0-CURRENT kernel gets stuck on "config>" prompt
Date: Wed, 4 Nov 1998 17:34:03 -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.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I just upgraded a test machine from 2.2.7-STABLE to 3.0-CURRENT aout from
source. For the most part that worked. Now with a freshly compiled GENERIC
kernel it gets stuck at:
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: Wed Nov 4 16:34:20 EST 1998
root@webber.ingress.net:/usr/src/sys/compile/GENERIC
Timecounter "i8254" frequency 1193182 Hz
CPU: \^E (267.27-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x570 Stepping=0
Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX>
real memory = 67043328 (65472K bytes)
config> autocheck gives assize=0 asp=0
until I hit Enter or q a couple of times. Specifically if I hit Enter once I
get the following line:
do quit
Hitting enter again produces:
quit
avail memory = 62263296 (60804K bytes)
Probing for devices on PCI bus 0:
... and so on and the machine continues to boot normally.
This is disturbing cuz I can't rely on the machine rebooting unattended. Any
idea why the kernel is dropping into the USERCONFIG editor when I haven't
asked for it? The GENERIC file was CVSuped Nov. 4 02:06.
--
Yarema
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 14:40:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA21221
for freebsd-current-outgoing; Wed, 4 Nov 1998 14:40: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 OAA21216
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 14:40:09 -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 OAA02317;
Wed, 4 Nov 1998 14:38:47 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811042238.OAA02317@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Yarema" <yds@ingress.com>
cc: current@FreeBSD.ORG
Subject: Re: 3.0-CURRENT kernel gets stuck on "config>" prompt
In-reply-to: Your message of "Wed, 04 Nov 1998 17:34:03 EST."
<035901be0843$39a63ee0$1f40e6cd@ichiban.ingress.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 04 Nov 1998 14:38:47 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I just upgraded a test machine from 2.2.7-STABLE to 3.0-CURRENT aout from
> source. For the most part that worked. Now with a freshly compiled GENERIC
> kernel it gets stuck at:
I left some debugging cruft in; resup and rebuild, sorry.
--
\\ 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 4 14: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 OAA22827
for freebsd-current-outgoing; Wed, 4 Nov 1998 14:51:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22795
for <current@freebsd.org>; Wed, 4 Nov 1998 14:51:36 -0800 (PST)
(envelope-from reg@shale.csir.co.za)
Received: (from reg@localhost)
by shale.csir.co.za (8.9.1/8.9.1) id AAA14469
for current@freebsd.org; Thu, 5 Nov 1998 00:51:22 +0200 (SAT)
(envelope-from reg)
Message-ID: <19981105005122.A13038@shale.csir.co.za>
Date: Thu, 5 Nov 1998 00:51:22 +0200
From: Jeremy Lea <reg@shale.csir.co.za>
To: current@FreeBSD.ORG
Subject: poll() for pthreads?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
I've been playing some with getting Mozilla to compile under FreeBSD,
and have succeeded (to some extent - it's a moving target). One thing
which I would like to do is enable NSPR (the NetScape Portable Runtime)
to use poll() under FreeBSD-current. With a few changes to ifdef's I
can get it to work.
However, when I compile NSPR to use pthreads, then poll is not available
and I must use the fake poll() provided in NSPR. The pthreaded version
of NSPR requires a poll() call of some form.
The CVS logs show that poll() is being hidden in libc_r because a
wrapper has not been written... However, this is way out of my league.
Does anyone have such a wrapper in their local tree, or is it a hard
thing to write? And would looking at the NSPR thread-safe wrapper for
poll() help?
http://cvs-mirror.mozilla.org/webtools/lxr/source/nsprpub/pr/src/md/unix/uxwrap.c
Is there anyone who can help? I'd like to see poll() used in official
ELF releases of Netscape in the future, especially if someone makes
kernel threads work...
Regards,
-Jeremy
PS: pthread.h prototypes pthread_attr_setinheritsched(), but there is
no such function. In NSPR calls to any pthread_*sched* functions are
surrounded by _POSIX_THREAD_PRIORITY_SCHEDULING, which is a commented
out define in pthreads.h. Maybe the prototypes should be hidden behind
this define? At lease it will give a compile error, not a link error...
--
| "In this world of temptation, I will stand for what is right.
--+-- With a heart of salvation, I will hold up the light.
| If I live or if I die, if I laugh or if I cry,
| in this world of temptation, I will stand." -Pam Thum
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 14:56:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA23937
for freebsd-current-outgoing; Wed, 4 Nov 1998 14:56:46 -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 OAA23920
for <current@freebsd.org>; Wed, 4 Nov 1998 14:56:43 -0800 (PST)
(envelope-from garman@garman.dyn.ml.org)
Message-Id: <199811042256.OAA23920@hub.freebsd.org>
Received: (qmail 545 invoked from smtpd); 4 Nov 1998 22:57:22 -0000
Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1)
by localhost.garman.net with SMTP; 4 Nov 1998 22:57:22 -0000
Date: Wed, 4 Nov 1998 17:57:21 -0500 (EST)
From: garman@earthling.net
Reply-To: garman@earthling.net
Subject: Re: samba smbd core dumps & -current
To: current@FreeBSD.ORG
In-Reply-To: <412566B2.004DC9C6.00@bfc.dk>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
sorry about the recent null messages; it appears this problem is more
system wide :(
it seems to be a swap related problem.
even with only 70% swap usage, programs complain that they cannot
allocate any more memory. this is with any user... but i'll try
fiddling with the login.conf values anyhow.
to summarize, smbd was trying to allocate 46 bytes but couldn't... this
resulted in later dereferencing a NULL pointer. very reproducible, and
i can re-do the gdb backtrace dumps and so forth if theres interest.
ugh...
--
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 Wed Nov 4 15: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 PAA24921
for freebsd-current-outgoing; Wed, 4 Nov 1998 15:00:36 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.kar.net (n185.cdialup.kar.net [195.178.130.185])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24599
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 14:59:47 -0800 (PST)
(envelope-from kushn@mail.kar.net)
Received: from localhost (volodya@localhost)
by mail.kar.net (8.9.1/8.8.8) with ESMTP id AAA10875
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 00:58:22 +0200 (EET)
(envelope-from kushn@mail.kar.net)
Date: Thu, 5 Nov 1998 00:58:17 +0200 (EET)
From: Vladimir Kushnir <kushn@mail.kar.net>
X-Sender: volodya@kushnir.kiev.ua
To: freebsd-current@FreeBSD.ORG
Subject: xforms-elf: compiled-in soname.
Message-ID: <Pine.BSF.4.05.9811050047490.10816-100000@kushnir.kiev.ua>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello,
Well, the subject sais it all:
strings /usr/X11R6/lib/libxforms.so.0 | grep libforms
libforms.so.0.88
~~
So, for anything compiled with "-lxforms":
libforms.so.0.88 => not found
There's another link needed (or we can use just name libforms - there's
no another libforms here except an ancient compat20).
Regards,
Vladimir
===========================|=======================
Vladimir Kushnir |
kushn@mail.kar.net, | Powered by FreeBSD
kushnir@ap3.bitp.kiev.ua |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 15:13:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA27767
for freebsd-current-outgoing; Wed, 4 Nov 1998 15:13:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27690;
Wed, 4 Nov 1998 15:12:52 -0800 (PST)
(envelope-from jdp@austin.polstra.com)
Received: from austin.polstra.com (jdp@localhost)
by austin.polstra.com (8.9.1/8.9.1) with ESMTP id PAA25274;
Wed, 4 Nov 1998 15:12:43 -0800 (PST)
(envelope-from jdp)
Message-Id: <199811042312.PAA25274@austin.polstra.com>
To: current@FreeBSD.ORG
Cc: msmith@FreeBSD.ORG, peter@FreeBSD.ORG
Subject: make installworld problem in src/sys/modules
Date: Wed, 04 Nov 1998 15:12:43 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
A "make -k installworld" on a recent ELF -current system failed today
in 3 places:
===> sys/modules/ibcs2
install -c -o root -g wheel -m 555 ibcs2.ko /modules
install -c -o root -g wheel -m 444 ibcs2.8.gz /usr/share/man/man8
install -c -o root -g wheel -m 555 /usr/src/sys/modules/ibcs2/ibcs2 /usr/bin
install: /usr/src/sys/modules/ibcs2/ibcs2: No such file or directory
*** Error code 71 (continuing)
`install' not remade because of errors.
===> sys/modules/joy
install -c -o root -g wheel -m 555 joy.ko /modules
install -c -o root -g wheel -m 444 joy.8.gz /usr/share/man/man8
install -c -o root -g wheel -m 555 /usr/src/sys/modules/joy/joy /usr/bin
install: /usr/src/sys/modules/joy/joy: No such file or directory
*** Error code 71 (continuing)
`install' not remade because of errors.
===> sys/modules/linux
install -c -o root -g wheel -m 555 linux.ko /modules
install -c -o root -g wheel -m 444 linux.8.gz /usr/share/man/man8
install -c -o root -g wheel -m 555 /usr/src/sys/modules/linux/linux /usr/bin
install: /usr/src/sys/modules/linux/linux: No such file or directory
*** Error code 71 (continuing)
`install' not remade because of errors.
I think I understand why it failed. The failing files "ibcs2", "joy",
and "linux" are all shell scripts in the source tree (not in the
object tree). But the "make clean" rule deletes them, e.g.:
===> sys/modules/ibcs2
rm -f vnode_if.h vnode_if.c opt_spx_hack.h setdef0.c setdef1.c setdefs.h setdef0.o setdef1.o ibcs2.8.gz ibcs2.8.cat.gz ibcs2 ibcs2.ko ibcs2.o ibcs2_errno.o ibcs2_ipc.o ibcs2_stat.o ibcs2_misc.o ibcs2_fcntl.o ibcs2_signal.o ibcs2_sysent.o ibcs2_ioctl.o ibcs2_socksys.o ibcs2_util.o ibcs2_xenix.o ibcs2_xenix_sysent.o ibcs2_isc.o ibcs2_isc_sysent.o ibcs2_msg.o ibcs2_other.o ibcs2_sysi86.o ibcs2_sysvec.o @ machine lkm_verify_tmp symb.tmp tmp.o
(Look carefully in there, and you'll find "ibcs2".)
This is all fine and dandy if you've got a populated /usr/obj tree
when the make clean gets run. But I started out in this case with
an empty /usr/obj tree. As a result, the make clean step removed my
source file.
I'm not quite sure what the right fix is. Maybe rename the source
files to "ibcs2.sh", etc.
On a related note, I don't think the shell scripts are correct anyway.
They invoke "modload", which is for LKMs, not the new-style kernel
modules.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 16:05:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA08155
for freebsd-current-outgoing; Wed, 4 Nov 1998 16:05:51 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08147
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 16:05:47 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.59.131])
by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA1B23 for <current@FreeBSD.ORG>;
Thu, 5 Nov 1998 01:05:33 +0100
Message-ID: <XFMail.981105010920.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: Thu, 05 Nov 1998 01:09:20 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: FreeBSD Current <current@FreeBSD.ORG>
Subject: cvs intricities (well not really ;)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
I might have missed the obvious (again), but where can I find the most up to
date list of which src, doc, ports etc can be mentioned in the cvsupfile for
inclusion of the cvsup process?
Thanks,
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Wed Nov 4 16:15:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA10360
for freebsd-current-outgoing; Wed, 4 Nov 1998 16:15:34 -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 QAA10333
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 16:15:23 -0800 (PST)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.9.1/8.9.1) id LAA24698;
Thu, 5 Nov 1998 11:22:36 +1100 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199811050022.LAA24698@cimlogic.com.au>
Subject: Re: poll() for pthreads?
In-Reply-To: <19981105005122.A13038@shale.csir.co.za> from Jeremy Lea at "Nov 5, 98 00:51:22 am"
To: reg@shale.csir.co.za (Jeremy Lea)
Date: Thu, 5 Nov 1998 11:22:36 +1100 (EST)
Cc: 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
Jeremy Lea wrote:
> The CVS logs show that poll() is being hidden in libc_r because a
> wrapper has not been written... However, this is way out of my league.
> Does anyone have such a wrapper in their local tree, or is it a hard
> thing to write? And would looking at the NSPR thread-safe wrapper for
> poll() help?
To implement poll(2) properly, the internal use of select(2) as the
blocking mechanism needs to be changed to use poll. It's not just a matter
of a wrapper, since you can implement true poll functionality with
select.
I thought Netscape were using their own threads.
--
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 4 16:16:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA10505
for freebsd-current-outgoing; Wed, 4 Nov 1998 16:16:39 -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 QAA10497
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 16:16:31 -0800 (PST)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.9.1/8.9.1) id LAA24709;
Thu, 5 Nov 1998 11:25:07 +1100 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199811050025.LAA24709@cimlogic.com.au>
Subject: Re: ELF interpreter /usr/libexec/ld-elf.so.1 not found, Abort trap
In-Reply-To: <19981104224604.A28969@klemm.gtn.com> from Andreas Klemm at "Nov 4, 98 10:46:04 pm"
To: andreas@klemm.gtn.com (Andreas Klemm)
Date: Thu, 5 Nov 1998 11:25:07 +1100 (EST)
Cc: 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
Andreas Klemm wrote:
> [...]
> 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).
--
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 4 17:24:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA18865
for freebsd-current-outgoing; Wed, 4 Nov 1998 17:24:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lionking.org (blacker-99.caltech.edu [131.215.86.99])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18860
for <freebsd-current@freebsd.org>; Wed, 4 Nov 1998 17:24:22 -0800 (PST)
(envelope-from btman@ugcs.caltech.edu)
Received: from localhost (btman@localhost)
by lionking.org (8.9.1a/8.9.1) with ESMTP id RAA04887
for <freebsd-current@freebsd.org>; Wed, 4 Nov 1998 17:24:13 -0800 (PST)
X-Authentication-Warning: lionking.org: btman owned process doing -bs
Date: Wed, 4 Nov 1998 17:24:13 -0800 (PST)
From: Brian Tiemann <btman@ugcs.caltech.edu>
X-Sender: btman@lionking.org
To: freebsd-current@FreeBSD.ORG
Subject: OSS sound support
Message-ID: <Pine.BSF.4.05.9811041719150.8123-100000@lionking.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
So what's the deal with OSS on -current?
I've had it panicking my installation repeatedly; I got the
following recently from their (4Front's) tech support:
> We've found a major bug in FreeBSD's VM architecture and have sent off
> the demo which will crash FreeBSD 3 + Netscape. This is the same problem
> affecting OSS and so until we hear from the kernel developers' we're not
> going to do any work arounds. If you like, I can send you the test
> program.
I wrote back asking whether there was an OSS mailing list I could
follow so I would know when this problem had been addressed, but I still
haven't heard back; I also haven't seen any discussion of it on this list
or in any of the archives (or if I have, I haven't been watching closely
enough).
So, where (if anywhere) would this discussion be going on? What
options do I have for finding out when I can use sound again? :)
Thanks in advance for any input--
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 4 18:34:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA00149
for freebsd-current-outgoing; Wed, 4 Nov 1998 18:34:59 -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 SAA00139
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 18:34:55 -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 NAA18785; Thu, 5 Nov 1998 13:31:12 +1100 (EST)
Message-ID: <19981105133112.I15681@rf900.physics.usyd.edu.au>
Date: Thu, 5 Nov 1998 13:31:12 +1100
From: David Dawes <dawes@rf900.physics.usyd.edu.au>
To: Peter Wemm <peter@netplex.com.au>, Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>
Cc: John Fieber <jfieber@indiana.edu>, freebsd-current@FreeBSD.ORG
Subject: Re: ELFoized xtt-SVGA-1.0 & TrueType fonts => HANG
References: <199811041751.SAA22212@kazi.dcse.fee.vutbr.cz> <199811041815.CAA01590@spinner.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199811041815.CAA01590@spinner.netplex.com.au>; from Peter Wemm on Thu, Nov 05, 1998 at 02:15:19AM +0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, Nov 05, 1998 at 02:15:19AM +0800, Peter Wemm wrote:
>Cejka Rudolf wrote:
>>
>> > I found Xtt to be extremely flakey and astonishingly complicated.
>> >
>> > Meanwhile, these patches for X11 are pretty simple and work
>> > great: http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/
>>
>> So somebody can make official port xfsft...
>
>I use the freetype (ft) libs built directly into the server. Ariel on X11
>is disturbing at first. :-) I had a lot of trouble with xfstt, but that
>was around the same that a change to the socket system disturbed X11 in
>general.
xfstt and xfsft are different. The latter uses the FreeType library
and the former doesn't. There is a summary of the options at
http://www.xfree86.org/FAQ#TTF.
David
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 19:14:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA05161
for freebsd-current-outgoing; Wed, 4 Nov 1998 19:14: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 TAA05152
for <current@freebsd.org>; Wed, 4 Nov 1998 19:14:23 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id WAA25929
for <current@freebsd.org>; Wed, 4 Nov 1998 22:14:18 -0500 (EST)
Date: Wed, 4 Nov 1998 22:14:18 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: current@FreeBSD.ORG
Subject: LinuxThreads and life with the FreeBSD kernel
Message-ID: <Pine.BSF.4.05.9811042202310.25785-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, I thought I'd fixed everything all up ready for LinuxThreads, but
instead, I've gotten a nice unkillable process:
398 green 18 0 1068K 436K pause 2:46 0.00% 0.00% ex5
Anyway, I've gotten a full shared signal flag now, called RFSIGSHARE, so I
think most of the work for LinuxThreads support _is_ done. I've got the
patches here, and I need _REAL_ developers to come try this out and help
me with it. The brunt of the work _is_ done, it would seem :) However, the
unkillable process is strange, and LinuxThreads still does not 'work'.
However, if someone has a test box, to test shared signals with RFMEM and
RFSIGSHARE, I'd be grateful. And this changes struct proc, so all
proc-using things MUST be compiled (libkvm, ps, top, modules), but if you
don't know this you're probably not someone who should be doing this
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 4 19:16:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA05334
for freebsd-current-outgoing; Wed, 4 Nov 1998 19:16: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 TAA05261
for <current@freebsd.org>; Wed, 4 Nov 1998 19:15: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 WAA25958
for <current@freebsd.org>; Wed, 4 Nov 1998 22:15:53 -0500 (EST)
Date: Wed, 4 Nov 1998 22:15:53 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: current@FreeBSD.ORG
Subject: RFSIGSHARE: forgot patch ;)
Message-ID: <Pine.BSF.4.05.9811042214220.25785-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
Woops, sorry, here is the patchset :)
--- ./i386/linux/linux_dummy.c.orig Thu Nov 6 14:28:52 1997
+++ ./i386/linux/linux_dummy.c Wed Nov 4 20:48:40 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);
--- ./i386/linux/linux_misc.c.orig Mon Oct 5 08:40:42 1998
+++ ./i386/linux/linux_misc.c Wed Nov 4 21:13:31 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>
@@ -557,6 +558,56 @@
return error;
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);
+#endif
+#ifdef DEBUG_CLONE
+ printf("linux_clone(%#x, %#x)\n", ((int *)args)[0],
+ ((int *)args)[1]);
+ if (args->flags & CLONE_PID)
+ printf("linux_clone: CLONE_PID not yet supported\n");
+ if (args->flags & CLONE_FS)
+ printf("linux_clone: CLONE_FS not yet supported\n");
+#endif
+ if (args->flags & CLONE_VM)
+ ff |= RFMEM;
+ if (args->flags & CLONE_SIGHAND)
+ ff |= RFSIGSHARE;
+ ff |= (args->flags & CLONE_FILES) ? RFFDG : RFCFDG;
+ 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;
+ }
+ if (args->flags & CLONE_SIGHAND)
+ p2->p_sigacts = p->p_sigacts;
+#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;
}
--- ./i386/linux/linux_proto.h.orig Fri Jul 10 18:30:04 1998
+++ ./i386/linux/linux_proto.h Wed Nov 4 20:48:40 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 *)];
--- ./i386/linux/linux_syscall.h.orig Fri Jul 10 18:30:06 1998
+++ ./i386/linux/linux_syscall.h Wed Nov 4 20:48:40 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
--- ./i386/linux/linux_sysent.c.orig Fri Jul 10 18:30:07 1998
+++ ./i386/linux/linux_sysent.c Wed Nov 4 20:48:40 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 */
--- ./i386/linux/syscalls.master.orig Fri Jul 10 18:30:08 1998
+++ ./i386/linux/syscalls.master Wed Nov 4 20:48:40 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); }
--- ./kern/kern_fork.c.orig Wed Nov 4 20:33:11 1998
+++ ./kern/kern_fork.c Wed Nov 4 20:44:29 1998
@@ -151,6 +151,10 @@
p1->p_pid);
return (EOPNOTSUPP);
}
+ if (flags & RFSIGSHARE) {
+ printf("shared signal space attemped: pid: %d\n",
p1->p_pid);
+ return (EOPNOTSUPP);
+ }
#endif
/*
@@ -320,6 +324,16 @@
bcopy(p1->p_cred, p2->p_cred, sizeof(*p2->p_cred));
p2->p_cred->p_refcnt = 1;
crhold(p1->p_ucred);
+
+ if (flags & RFSIGSHARE) {
+ p2->p_sig->p_refcnt++;
+ } else {
+ p2->p_sig = malloc(sizeof(struct procsig), M_TEMP,
M_WAITOK);
+ p2->p_sig->p_refcnt = 1;
+ p2->p_sigmask = p1->p_sigmask;
+ p2->p_sigignore = p1->p_sigignore;
+ p2->p_sigcatch = p1->p_sigcatch;
+ }
/* bump references to the text vnode (for procfs) */
p2->p_textvp = p1->p_textvp;
--- ./kern/kern_exit.c.orig Wed Nov 4 20:45:09 1998
+++ ./kern/kern_exit.c Wed Nov 4 20:46:50 1998
@@ -333,6 +333,11 @@
p->p_limit = NULL;
}
+ if (--p->p_sig->p_refcnt == 0) {
+ free(p->p_sig, M_TEMP);
+ p->p_sig = NULL;
+ }
+
/*
* Finally, call machine-dependent code to release the remaining
* resources including address space, the kernel stack and pcb.
--- ./kern/init_main.c.orig Wed Nov 4 16:27:04 1998
+++ ./kern/init_main.c Wed Nov 4 16:41:15 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;
@@ -414,6 +415,11 @@
p->p_cred = &cred0;
p->p_ucred = crget();
p->p_ucred->cr_ngroups = 1; /* group 0 */
+
+ /* Create procsig. */
+ p->p_sig = &procsig0;
+ p->p_sig->p_refcnt = 2;
+ p->p_sigmask = p->p_sigcatch = p->p_sigignore = 0;
/* Create the file descriptor table. */
fdp = &filedesc0;
--- ./sys/proc.h.orig Wed Nov 4 20:22:32 1998
+++ ./sys/proc.h Wed Nov 4 20:30:41 1998
@@ -75,6 +75,13 @@
int pg_jobc; /* # procs qualifying pgrp for job control
*/
};
+struct procsig {
+ int p_refcnt;
+ sigset_t p_sigmask; /* Current signal mask. */
+ sigset_t p_sigignore; /* Signals being ignored. */
+ sigset_t p_sigcatch; /* Signals being caught by user. */
+};
+
/*
* Description of a process.
*
@@ -165,12 +172,12 @@
#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->p_sigmask
+#define p_sigignore p_sig->p_sigignore
+#define p_sigcatch p_sig->p_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. */
--- ./sys/unistd.h.orig Wed Nov 4 20:32:28 1998
+++ ./sys/unistd.h Wed Nov 4 20:33:00 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 */
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 19:53:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA09695
for freebsd-current-outgoing; Wed, 4 Nov 1998 19:53:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from chaotic.oz.org (chaotic.oz.org [203.20.237.203])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09690
for <current@freebsd.org>; Wed, 4 Nov 1998 19:53:25 -0800 (PST)
(envelope-from simon@oz.org)
Received: from localhost (localhost [127.0.0.1])
by chaotic.oz.org (8.9.1/8.8.8) with SMTP id NAA09805
for <current@freebsd.org>; Thu, 5 Nov 1998 13:53:16 +1000 (EST)
(envelope-from simon@oz.org)
Date: Thu, 5 Nov 1998 13:53:16 +1000 (EST)
From: Simon Coggins <simon@oz.org>
Reply-To: chaos@ultra.net.au
To: current@FreeBSD.ORG
Subject: Next aout-to-elf-build problem:
Message-ID: <Pine.BSF.4.02.9811051352430.2762-100000@chaotic.oz.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
===> sys/modules/linux
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
cc -c -O -pipe -DCOMPAT_LINUX -DKERNEL -Wreturn-type -Wcomment
-Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat
-fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-
-I/usr/obj/elf/usr/src/sys/modules/linux
-I/usr/obj/elf/usr/src/sys/modules/linux/@
-I/usr/obj/elf/usr/src/tmp/usr/include -UKERNEL
/usr/src/sys/modules/linux/../../i386/linux/linux_genassym.c
cc -O -pipe -DCOMPAT_LINUX -DKERNEL -Wreturn-type -Wcomment
-Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat
-fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-
-I/usr/obj/elf/usr/src/sys/modules/linux
-I/usr/obj/elf/usr/src/sys/modules/linux/@
-I/usr/obj/elf/usr/src/tmp/usr/include -o linux_genassym linux_genassym.o
./linux_genassym > linux_assym.h
/usr/libexec/ld-elf.so.1: Shared object "libc.so.3" not found
*** Error code 1
Regards
Simon
---
+---------------------------------------------------------------+
| Email: chaos@ultra.net.au, chaos@oz.org, simon@bofh.com.au |
| http://www.ultra.net.au/~chaos Simon.Coggins@jcu.edu.au. |
| Chaos on IRC, IRC Operator for the OzORG Network |
+---------------------------------------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 19:57:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA09946
for freebsd-current-outgoing; Wed, 4 Nov 1998 19:57:47 -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 TAA09937
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 19:57:42 -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 LAA03894;
Thu, 5 Nov 1998 11:57:11 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811050357.LAA03894@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman <green@unixhelp.org>
cc: current@FreeBSD.ORG
Subject: Re: RFSIGSHARE: forgot patch ;)
In-reply-to: Your message of "Wed, 04 Nov 1998 22:15:53 EST."
<Pine.BSF.4.05.9811042214220.25785-100000@janus.syracuse.net>
Date: Thu, 05 Nov 1998 11:57:10 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Feldman wrote:
[..]
> --- ./kern/kern_fork.c.orig Wed Nov 4 20:33:11 1998
> +++ ./kern/kern_fork.c Wed Nov 4 20:44:29 1998
> @@ -151,6 +151,10 @@
> p1->p_pid);
> return (EOPNOTSUPP);
> }
> + if (flags & RFSIGSHARE) {
> + printf("shared signal space attemped: pid: %d\n",
> p1->p_pid);
> + return (EOPNOTSUPP);
> + }
> #endif
>
> /*
RFSIGSHARE should work fine on SMP.
> @@ -320,6 +324,16 @@
> bcopy(p1->p_cred, p2->p_cred, sizeof(*p2->p_cred));
> p2->p_cred->p_refcnt = 1;
> crhold(p1->p_ucred);
> +
> + if (flags & RFSIGSHARE) {
> + p2->p_sig->p_refcnt++;
> + } else {
> + p2->p_sig = malloc(sizeof(struct procsig), M_TEMP,
> M_WAITOK);
> + p2->p_sig->p_refcnt = 1;
> + p2->p_sigmask = p1->p_sigmask;
> + p2->p_sigignore = p1->p_sigignore;
> + p2->p_sigcatch = p1->p_sigcatch;
> + }
>
> /* bump references to the text vnode (for procfs) */
> p2->p_textvp = p1->p_textvp;
Umm, you are sharing the signal masks, not the signal handler vectors
themselves. Think p_sigacts.. Those are stored after the PCB and are
paged out.
Assuming you take a shot at sharing them, try this: Keep p_sigacts there
by default. If a process attempts to share the signals during a fork,
then malloc a copy and attach it to both the child and parent. When the
reference count drops to 1, the remaining process should probably have
it's vectors copied to the upages again and the malloc space freed. But
good stuff so far! :-)
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 4 19:59:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA10285
for freebsd-current-outgoing; Wed, 4 Nov 1998 19:59:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from tohokugw.tohoku.iij.ad.jp ([202.232.14.98])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10276
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 19:59:09 -0800 (PST)
(envelope-from taguchi@tohoku.iij.ad.jp)
Received: by tohokugw.tohoku.iij.ad.jp; id MAA20495; Thu, 5 Nov 1998 12:58:43 +0900 (JST)
Received: from unknown(192.168.144.10) by tohokugw.tohoku.iij.ad.jp via smap (4.1)
id xma020493; Thu, 5 Nov 98 12:58:29 +0900
Received: from localhost (hirose.tohoku.iij.ad.jp [192.168.144.2])
by ayashi.tohoku.iij.ad.jp (8.8.8/3.7W-98102615) with ESMTP id MAA02956
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 12:57:16 +0900 (JST)
To: freebsd-current@FreeBSD.ORG
Subject: Re: ELFoized xtt-SVGA-1.0 & TrueType fonts => HANG
From: Taguchi Takeshi <taguchi@tohoku.iij.ad.jp>
In-Reply-To: Your message of "Thu, 5 Nov 1998 13:31:12 +1100"
<19981105133112.I15681@rf900.physics.usyd.edu.au>
References: <19981105133112.I15681@rf900.physics.usyd.edu.au>
X-Mailer: Mew version 1.93b38 on XEmacs 20.4 (Emerald)
X-Prom-Mew: Prom-Mew 1.92.9 (procmail reader for Mew)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <19981105125804E.taguchi@tohoku.iij.ad.jp>
Date: Thu, 05 Nov 1998 12:58:04 +0900
X-Dispatcher: imput version 980522
Lines: 18
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> xfstt and xfsft are different. The latter uses the FreeType library
> and the former doesn't. There is a summary of the options at
> http://www.xfree86.org/FAQ#TTF.
Additionaly, xfstt and xfsft supports very few encodings.
But X-TrueType support many kind of encodings include
Asian/Europian fonts.
> > I have ELFoized -current:
> > Main system (/usr/src): 98/09/28
>
> It's old. If you use 98/10/13 or later -current, I think
> you can use Xtt with no trouble!
Thanks, Fukushima-san.
At old -current (befor 98/10/13), dynamic loading has a bug.
So you should use *TURE* -current, or 3.0-RELEASE for using Xtt.
apache-1.3.x has same probrem.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 20:06:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA10968
for freebsd-current-outgoing; Wed, 4 Nov 1998 20:06:05 -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 UAA10935
for <freebsd-current@freebsd.org>; Wed, 4 Nov 1998 20:06:01 -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 SMTP id UAA00438
for <freebsd-current@freebsd.org>; Wed, 4 Nov 1998 20:05:55 -0800 (PST)
(envelope-from brian@CSUA.Berkeley.EDU)
Date: Wed, 4 Nov 1998 20:05:55 -0800 (PST)
From: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>
X-Sender: brian@smarter.than.nu
To: freebsd-current@FreeBSD.ORG
Subject: Netscape crashes (was: Re: OSS sound support)
In-Reply-To: <Pine.BSF.4.05.9811041719150.8123-100000@lionking.org>
Message-ID: <Pine.BSF.4.02A.9811042003140.333-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 Wed, 4 Nov 1998, Brian Tiemann wrote:
>
> So what's the deal with OSS on -current?
>
> I've had it panicking my installation repeatedly; I got the
> following recently from their (4Front's) tech support:
>
> > We've found a major bug in FreeBSD's VM architecture and have sent off
> > the demo which will crash FreeBSD 3 + Netscape. This is the same problem
> > affecting OSS and so until we hear from the kernel developers' we're not
> > going to do any work arounds. If you like, I can send you the test
> > program.
I get the "Pinstripe screen of death" from AccelX + Netscape occasionally.
I'd thought this was an AccelX bug, but I'd been too lazy to report it as
it happens so infrequently. I'm running current built Oct 12.
--
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 Wed Nov 4 20:30:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA13277
for freebsd-current-outgoing; Wed, 4 Nov 1998 20:30: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 UAA13270
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 20:30: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 XAA09689;
Wed, 4 Nov 1998 23:29:26 -0500 (EST)
Date: Wed, 4 Nov 1998 23:29:26 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Netscape crashes (was: Re: OSS sound support)
In-Reply-To: <Pine.BSF.4.02A.9811042003140.333-100000@smarter.than.nu>
Message-ID: <Pine.BSF.4.05.9811042327520.300-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, 4 Nov 1998, Brian W. Buchanan wrote:
> On Wed, 4 Nov 1998, Brian Tiemann wrote:
>
> >
> > So what's the deal with OSS on -current?
> >
> > I've had it panicking my installation repeatedly; I got the
> > following recently from their (4Front's) tech support:
> >
> > > We've found a major bug in FreeBSD's VM architecture and have sent off
> > > the demo which will crash FreeBSD 3 + Netscape. This is the same problem
> > > affecting OSS and so until we hear from the kernel developers' we're not
> > > going to do any work arounds. If you like, I can send you the test
> > > program.
>
> I get the "Pinstripe screen of death" from AccelX + Netscape occasionally.
> I'd thought this was an AccelX bug, but I'd been too lazy to report it as
> it happens so infrequently. I'm running current built Oct 12.
What you guys have posted so far amounts (as far as I can see) to little
more that gossip. Is there any hard facts that one can verify?
----------------------------+-----------------------------------------------
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 4 20:32:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA13396
for freebsd-current-outgoing; Wed, 4 Nov 1998 20:32:37 -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 UAA13387
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 20:32:33 -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 PAA19267; Thu, 5 Nov 1998 15:32:08 +1100 (EST)
Message-ID: <19981105153208.P15681@rf900.physics.usyd.edu.au>
Date: Thu, 5 Nov 1998 15:32:08 +1100
From: David Dawes <dawes@rf900.physics.usyd.edu.au>
To: Taguchi Takeshi <taguchi@tohoku.iij.ad.jp>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: ELFoized xtt-SVGA-1.0 & TrueType fonts => HANG
References: <19981105133112.I15681@rf900.physics.usyd.edu.au> <19981105125804E.taguchi@tohoku.iij.ad.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <19981105125804E.taguchi@tohoku.iij.ad.jp>; from Taguchi Takeshi on Thu, Nov 05, 1998 at 12:58:04PM +0900
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, Nov 05, 1998 at 12:58:04PM +0900, Taguchi Takeshi wrote:
>> xfstt and xfsft are different. The latter uses the FreeType library
>> and the former doesn't. There is a summary of the options at
>> http://www.xfree86.org/FAQ#TTF.
>
>Additionaly, xfstt and xfsft supports very few encodings.
>But X-TrueType support many kind of encodings include
>Asian/Europian fonts.
The encoding support in xfsft has recently been extended (and users can
add additional encodings). The entry in the XFree86 FAQ I'm referring
to says that X-TrueType is better when using ideographic scripts (but
for other reasons).
We at XFree86 are hoping to have a FreeType-based solution that uses
the best features of xfsft and X-TrueType included as part of XFree86 4.0.
David
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 20:34:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA13613
for freebsd-current-outgoing; Wed, 4 Nov 1998 20:34:23 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lionking.org (blacker-99.caltech.edu [131.215.86.99])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13605
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 20:34:22 -0800 (PST)
(envelope-from btman@ugcs.caltech.edu)
Received: from localhost (btman@localhost)
by lionking.org (8.9.1a/8.9.1) with ESMTP id UAA25506
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 20:34:13 -0800 (PST)
X-Authentication-Warning: lionking.org: btman owned process doing -bs
Date: Wed, 4 Nov 1998 20:34:13 -0800 (PST)
From: Brian Tiemann <btman@ugcs.caltech.edu>
X-Sender: btman@lionking.org
To: freebsd-current@FreeBSD.ORG
Subject: Re: Netscape crashes (was: Re: OSS sound support)
In-Reply-To: <Pine.BSF.4.05.9811042327520.300-100000@picnic.mat.net>
Message-ID: <Pine.BSF.4.05.9811042032590.15817-100000@lionking.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, 4 Nov 1998, Chuck Robey wrote:
> What you guys have posted so far amounts (as far as I can see) to little
> more that gossip. Is there any hard facts that one can verify?
OSS said that they had submitted an exploit to the kernel
developers, and that they were awaiting a reply.
I was just trying to find out where that might have been posted,
which kernel developers have heard about this, whether there's anything
being done, etc...
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 4 20:42:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA14334
for freebsd-current-outgoing; Wed, 4 Nov 1998 20:42: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 UAA14323
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 20:42:07 -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 UAA04001;
Wed, 4 Nov 1998 20:41:27 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811050441.UAA04001@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Tiemann <btman@ugcs.caltech.edu>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Netscape crashes (was: Re: OSS sound support)
In-reply-to: Your message of "Wed, 04 Nov 1998 20:34:13 PST."
<Pine.BSF.4.05.9811042032590.15817-100000@lionking.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 04 Nov 1998 20:41:27 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> > What you guys have posted so far amounts (as far as I can see) to little
> > more that gossip. Is there any hard facts that one can verify?
>
> OSS said that they had submitted an exploit to the kernel
> developers, and that they were awaiting a reply.
>
> I was just trying to find out where that might have been posted,
> which kernel developers have heard about this, whether there's anything
> being done, etc...
If such a thing had been submitted, in a fashion obviously intended to
keep it relatively quiet, do you think that anyone that knows anything
is going to tell you one way or the other?
Under the circumstances, this is something betwen the OSS folks and
whichever developers they contacted.
--
\\ 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 4 20:47:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA14884
for freebsd-current-outgoing; Wed, 4 Nov 1998 20:47:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lionking.org (blacker-99.caltech.edu [131.215.86.99])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14877
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 20:47:02 -0800 (PST)
(envelope-from btman@ugcs.caltech.edu)
Received: from localhost (btman@localhost)
by lionking.org (8.9.1a/8.9.1) with ESMTP id UAA26456
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 20:46:54 -0800 (PST)
X-Authentication-Warning: lionking.org: btman owned process doing -bs
Date: Wed, 4 Nov 1998 20:46:53 -0800 (PST)
From: Brian Tiemann <btman@ugcs.caltech.edu>
X-Sender: btman@lionking.org
To: freebsd-current@FreeBSD.ORG
Subject: Re: Netscape crashes (was: Re: OSS sound support)
In-Reply-To: <199811050441.UAA04001@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811042044180.15817-100000@lionking.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, 4 Nov 1998, Mike Smith wrote:
> If such a thing had been submitted, in a fashion obviously intended to
> keep it relatively quiet, do you think that anyone that knows anything
> is going to tell you one way or the other?
>
> Under the circumstances, this is something betwen the OSS folks and
> whichever developers they contacted.
Well, okay-- fair enough (though they did offer to send me the
exploit as well).
I was just trying to get an idea of where an announcement of a fix
might be made, since the OSS website isn't terribly up-to-date, and they
seem to have no mailing list for such things.
I'll just hang around here and keep quiet. :P
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 4 20: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 UAA15190
for freebsd-current-outgoing; Wed, 4 Nov 1998 20:51:33 -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 UAA15185
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 20:51:31 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA04092;
Wed, 4 Nov 1998 20:50:55 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811050450.UAA04092@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Tiemann <btman@ugcs.caltech.edu>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Netscape crashes (was: Re: OSS sound support)
In-reply-to: Your message of "Wed, 04 Nov 1998 20:46:53 PST."
<Pine.BSF.4.05.9811042044180.15817-100000@lionking.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 04 Nov 1998 20:50:55 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
>
> On Wed, 4 Nov 1998, Mike Smith wrote:
>
> > If such a thing had been submitted, in a fashion obviously intended to
> > keep it relatively quiet, do you think that anyone that knows anything
> > is going to tell you one way or the other?
> >
> > Under the circumstances, this is something betwen the OSS folks and
> > whichever developers they contacted.
>
> Well, okay-- fair enough (though they did offer to send me the
> exploit as well).
>
> I was just trying to get an idea of where an announcement of a fix
> might be made, since the OSS website isn't terribly up-to-date, and they
> seem to have no mailing list for such things.
The fix is likely to be announced once it exists. When it exists,
it'll be announced. 8)
> I'll just hang around here and keep quiet. :P
Best thing you can do is check with the FreeBSD Security Officer to
ensure that the problem is known (they should be able to give you a
private yes/no answer).
--
\\ 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 4 20: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 UAA15289
for freebsd-current-outgoing; Wed, 4 Nov 1998 20:52:20 -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 UAA15280
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 20:52:18 -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 UAA17462;
Wed, 4 Nov 1998 20:52:39 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Brian Tiemann <btman@ugcs.caltech.edu>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Netscape crashes (was: Re: OSS sound support)
In-reply-to: Your message of "Wed, 04 Nov 1998 20:34:13 PST."
<Pine.BSF.4.05.9811042032590.15817-100000@lionking.org>
Date: Wed, 04 Nov 1998 20:52:39 -0800
Message-ID: <17458.910241559@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I was just trying to find out where that might have been posted,
> which kernel developers have heard about this, whether there's anything
> being done, etc...
There isn't anyone currently available to work on this though we are
aware of the problem and will get to it as soon as we can. I make
absolutely no predictions as to when that will be since it's not an
easy problem to fix and, as I said, there's nobody to do it at the
moment. I certainly hope/expect the OSS folks to make it known once a
fix has been found since this will no doubt be the result of some
private dialog between them and developer X and I doubt that they will
necessarily post a public confirmation of that here.
- 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 4 20: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 UAA15407
for freebsd-current-outgoing; Wed, 4 Nov 1998 20:53:23 -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 UAA15400
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 20:53:21 -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 UAA17490;
Wed, 4 Nov 1998 20:53:26 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Mike Smith <mike@smith.net.au>
cc: Brian Tiemann <btman@ugcs.caltech.edu>, freebsd-current@FreeBSD.ORG
Subject: Re: Netscape crashes (was: Re: OSS sound support)
In-reply-to: Your message of "Wed, 04 Nov 1998 20:50:55 PST."
<199811050450.UAA04092@dingo.cdrom.com>
Date: Wed, 04 Nov 1998 20:53:26 -0800
Message-ID: <17487.910241606@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Best thing you can do is check with the FreeBSD Security Officer to
> ensure that the problem is known (they should be able to give you a
> private yes/no answer).
It's not an "exploit" so much as a crash and I seriously doubt
that the FreeBSD security officer will ever be involved with this.
Brian simply used the wrong terminology in describing the problem.
- 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 4 21:46:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA18840
for freebsd-current-outgoing; Wed, 4 Nov 1998 21:46:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lionking.org (blacker-99.caltech.edu [131.215.86.99])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18835
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 21:46:30 -0800 (PST)
(envelope-from btman@ugcs.caltech.edu)
Received: from localhost (btman@localhost)
by lionking.org (8.9.1a/8.9.1) with ESMTP id VAA00136
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 21:46:22 -0800 (PST)
X-Authentication-Warning: lionking.org: btman owned process doing -bs
Date: Wed, 4 Nov 1998 21:46:22 -0800 (PST)
From: Brian Tiemann <btman@ugcs.caltech.edu>
X-Sender: btman@lionking.org
To: freebsd-current@FreeBSD.ORG
Subject: Re: Netscape crashes (was: Re: OSS sound support)
In-Reply-To: <17487.910241606@time.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811042145500.15817-100000@lionking.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, 4 Nov 1998, Jordan K. Hubbard wrote:
> It's not an "exploit" so much as a crash and I seriously doubt
> that the FreeBSD security officer will ever be involved with this.
> Brian simply used the wrong terminology in describing the problem.
Roger. I'll bear that in mind-- thanks for the clarification. :)
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 4 21:55:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA19390
for freebsd-current-outgoing; Wed, 4 Nov 1998 21:55:27 -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 VAA19383
for <freebsd-current@FreeBSD.ORG>; Wed, 4 Nov 1998 21:55:22 -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 NAA04409;
Thu, 5 Nov 1998 13:54:38 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811050554.NAA04409@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: Brian Tiemann <btman@ugcs.caltech.edu>, freebsd-current@FreeBSD.ORG
Subject: Re: Netscape crashes (was: Re: OSS sound support)
In-reply-to: Your message of "Wed, 04 Nov 1998 20:52:39 PST."
<17458.910241559@time.cdrom.com>
Date: Thu, 05 Nov 1998 13:54:37 +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 was just trying to find out where that might have been posted,
> > which kernel developers have heard about this, whether there's anything
> > being done, etc...
>
> There isn't anyone currently available to work on this though we are
> aware of the problem and will get to it as soon as we can. I make
> absolutely no predictions as to when that will be since it's not an
> easy problem to fix and, as I said, there's nobody to do it at the
> moment. I certainly hope/expect the OSS folks to make it known once a
> fix has been found since this will no doubt be the result of some
> private dialog between them and developer X and I doubt that they will
> necessarily post a public confirmation of that here.
I'll be having a look at this this afternoon if all goes well. While
it's not unreasonable for the contig page allocator to be unable to pull
the rabbit out of the hat, it is most definately unreasonable that it
crashes the system.
> - 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 Wed Nov 4 22:14:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA20840
for freebsd-current-outgoing; Wed, 4 Nov 1998 22:14: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 WAA20835
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 22:13: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 BAA28151;
Thu, 5 Nov 1998 01:13:34 -0500 (EST)
Date: Thu, 5 Nov 1998 01:13:34 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Peter Wemm <peter@netplex.com.au>
cc: current@FreeBSD.ORG
Subject: Re: RFSIGSHARE: forgot patch ;)
In-Reply-To: <199811050357.LAA03894@spinner.netplex.com.au>
Message-ID: <Pine.BSF.4.05.9811050110520.28066-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
Hrmm.... I don't see why this doesn't work:
+ if (args->flags & CLONE_SIGHAND)
+ p2->p_sigacts = p->p_sigacts;
don't tell me it's pointing into user-space, or some other neglected part
of proc? I'll investigate I suppose. This is certainly helping me
familiarize myself with the kernel, even if these specific patches cause a
trap eventually (probably all the mallocing/freeing). I _really_ need to
buy a copy of the BSD book... quick question: zalloc and malloc should
each be used in what situations?
Cheers,
Brian Feldman
"gaining lots of experience"
On Thu, 5 Nov 1998, Peter Wemm wrote:
> Brian Feldman wrote:
> [..]
> > --- ./kern/kern_fork.c.orig Wed Nov 4 20:33:11 1998
> > +++ ./kern/kern_fork.c Wed Nov 4 20:44:29 1998
> > @@ -151,6 +151,10 @@
> > p1->p_pid);
> > return (EOPNOTSUPP);
> > }
> > + if (flags & RFSIGSHARE) {
> > + printf("shared signal space attemped: pid: %d\n",
> > p1->p_pid);
> > + return (EOPNOTSUPP);
> > + }
> > #endif
> >
> > /*
>
> RFSIGSHARE should work fine on SMP.
>
> > @@ -320,6 +324,16 @@
> > bcopy(p1->p_cred, p2->p_cred, sizeof(*p2->p_cred));
> > p2->p_cred->p_refcnt = 1;
> > crhold(p1->p_ucred);
> > +
> > + if (flags & RFSIGSHARE) {
> > + p2->p_sig->p_refcnt++;
> > + } else {
> > + p2->p_sig = malloc(sizeof(struct procsig), M_TEMP,
> > M_WAITOK);
> > + p2->p_sig->p_refcnt = 1;
> > + p2->p_sigmask = p1->p_sigmask;
> > + p2->p_sigignore = p1->p_sigignore;
> > + p2->p_sigcatch = p1->p_sigcatch;
> > + }
> >
> > /* bump references to the text vnode (for procfs) */
> > p2->p_textvp = p1->p_textvp;
>
> Umm, you are sharing the signal masks, not the signal handler vectors
> themselves. Think p_sigacts.. Those are stored after the PCB and are
> paged out.
>
> Assuming you take a shot at sharing them, try this: Keep p_sigacts there
> by default. If a process attempts to share the signals during a fork,
> then malloc a copy and attach it to both the child and parent. When the
> reference count drops to 1, the remaining process should probably have
> it's vectors copied to the upages again and the malloc space freed. But
> good stuff so far! :-)
>
> Cheers,
> -Peter
>
>
>
>
> 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 4 22:35:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA22168
for freebsd-current-outgoing; Wed, 4 Nov 1998 22:35:49 -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 WAA22154;
Wed, 4 Nov 1998 22:35:43 -0800 (PST)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by relay.nuxi.com (8.9.1/8.9.1) id WAA05353;
Wed, 4 Nov 1998 22:35:26 -0800 (PST)
(envelope-from obrien)
Message-ID: <19981104223526.A5176@nuxi.com>
Date: Wed, 4 Nov 1998 22:35:26 -0800
From: "David O'Brien" <obrien@NUXI.com>
To: dg@root.com
Cc: current@FreeBSD.ORG, itojun@FreeBSD.ORG
Subject: Re: IPv6 in -current
Reply-To: obrien@NUXI.com
References: <19981102010742.A5101@nuxi.com> <199811021048.CAA01511@implode.root.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199811021048.CAA01511@implode.root.com>; from David Greenman on Mon, Nov 02, 1998 at 02:48:51AM -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
> With the above said, I disagree with waiting forever and think that a
> decision on this should be made relatively soon (this year).
So do we have a plan for making this happen? Give each group a few
months to make a case for there stack? What qualities should each group
be trying to meet?
Which group of people will make the choice? core? The users on on this
list? etc...
--
-- 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 4 23:35:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA28403
for freebsd-current-outgoing; Wed, 4 Nov 1998 23:35:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from emma.eng.uct.ac.za (emma.eng.uct.ac.za [137.158.128.160])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28354
for <current@freebsd.org>; Wed, 4 Nov 1998 23:34:50 -0800 (PST)
(envelope-from shaun@emma.eng.uct.ac.za)
Received: (from shaun@localhost)
by emma.eng.uct.ac.za (8.8.8/8.8.8) id JAA10712
for current@freebsd.org; Thu, 5 Nov 1998 09:34:25 +0200 (SAT)
(envelope-from shaun)
Message-ID: <19981105093424.A10708@emma.eng.uct.ac.za>
Date: Thu, 5 Nov 1998 09:34:24 +0200
From: Shaun Courtney <shaun@emma.eng.uct.ac.za>
To: current@FreeBSD.ORG
Subject: Error in 1.38 Makefile.inc1
Mail-Followup-To: current@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi
There is a ,endif instead of a .endif on line 755
Cheers
Shaun
--
Department of Electrical Engineering and CERECAM
System Administrator and Unix/NT support
http://www.eng.uct.ac.za
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 23:41:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA29055
for freebsd-current-outgoing; Wed, 4 Nov 1998 23:41:26 -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 XAA29050
for <current@freebsd.org>; Wed, 4 Nov 1998 23:41:23 -0800 (PST)
(envelope-from will@ns.oeno.com)
Received: (qmail 24486 invoked by uid 1001); 5 Nov 1998 07:41:13 -0000
To: James Mansion <james@westongold.com>
Cc: current@FreeBSD.ORG
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
References: <32BABEF63EAED111B2C5204C4F4F50201804@WGP01.newsgate.clinet.fi>
From: Ville-Pertti Keinonen <will@iki.fi>
Date: 05 Nov 1998 09:39:06 +0200
In-Reply-To: James Mansion's message of "4 Nov 1998 18:54:39 +0200"
Message-ID: <8667cud1wl.fsf@not.oeno.com>
Lines: 40
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
James Mansion <james@westongold.com> writes:
> I'd like to suggest that threads (at least kernel threads)
> should share an address space EXCEPT for a page (or maybe
> more than one) that will have a common address in each thread.
> This is how OS/2 (at least) handles thread specific data,
> and so far as I can tell it is potentially much cleaner
> for TSD, including errno.
It's a kludge.
> Any user-level multiplexing would need to save/restore this
> data on task switch of course and a kernel-assist that changes
> the memory map might be faster (or might not, dunno).
Entering and leaving the kernel is expensive, it would certainly not
be faster.
It's not a good idea for kernel threads, either.
The kernel either needs to change a page mapping in the process map or
switch to a thread-specific map. The latter would make threads almost
equivalent to processes and the former is not good for SMP, because
the process memory map is prepared to run only one thread at any given
time.
As a "fix", each process could have as many page directories as there
are CPUs, but creating them "on-the-fly" each time would be too slow
and letting them exist while not running the process could end up
costing two pages per extra cpu per multithreaded process in addition
to the actual thread-specific pages. It doesn't scale well.
> Can I ask (plead, really) for any effort in this area to
> consider the support for inter-process synchronisation as well
> as intra-process?
Non-Unix-like synchronization semantics can easily break the level of
isolation of Unix processes that makes them manageable.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 23:49:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA29789
for freebsd-current-outgoing; Wed, 4 Nov 1998 23:49:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles186.castles.com [208.214.165.186])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29784
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 23:49:36 -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 XAA00669;
Wed, 4 Nov 1998 23:48:39 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811050748.XAA00669@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Parag Patel <parag@cgt.com>
cc: Terry Lambert <tlambert@primenet.com>, mike@smith.net.au (Mike Smith),
jkh@time.cdrom.com, current@FreeBSD.ORG
Subject: Re: lisp vs. Forth (was Re: New boot loader and alternate kernels )
In-reply-to: Your message of "Wed, 04 Nov 1998 11:59:27 PST."
<199811041959.LAA22507@pinhead.parag.codegen.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 04 Nov 1998 23:48:38 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> >If the FORTH Interpreter were OpenBoot syntax compliant, we
> >could use it to interpret ROM code on a number of cards
> >designed to be usable in both Intel and PPC systems.
> >
> >Also, there's the whole OpenFirmware standard thing...
>
> Well, the standard's kinda big. You're going to be well into 300-400k
> of code (Forth or C) to meet it. You have to start with the ANS Forth
> spec, add IEEE-1275, then go through most of the recommended practices
> at <http://playground.sun.com/pub/1275/home.html> plus other assorted
> items.
Ficl is ANS-compliant in about 20k, using perhaps 8k or so for the
dictionary, but TBH I'm not sure that OpenFirmware compatibility would
actually win us. If you want an OF system, get one. The goal *here*
is to achieve the goals of a bootstrap loader:
- Enumerate hardware
- Load the kernel
- Load drivers for enumerated hardware
- Prepare the kernel execution environment
- Offload as much once-off boot-time crud from the kernel as is
sensible
- Allow the user a broad degree of control over the above steps
> The I2O 1.5 spec is now downloadable for free, so that's going to throw
> another level of driver fun into the mix.
With any luck there will be a fairly straightforward high-level
interface to I2O services; again, we really don't need to dive too deep
into it to meet the bootstrap goals. I'm waiting for my password to
show up in the mail...
--
\\ 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 4 23:55:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA00885
for freebsd-current-outgoing; Wed, 4 Nov 1998 23:55:15 -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 XAA00870
for <current@freebsd.org>; Wed, 4 Nov 1998 23:55:10 -0800 (PST)
(envelope-from will@ns.oeno.com)
Received: (qmail 24773 invoked by uid 1001); 5 Nov 1998 07:55:01 -0000
To: Julian Elischer <julian@whistle.com>
Cc: current@FreeBSD.ORG
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
References: <Pine.BSF.3.95.981103135641.1112F-100000@current1.whistle.com.newsgate.clinet.fi>
From: Ville-Pertti Keinonen <will@iki.fi>
Date: 05 Nov 1998 09:52:55 +0200
In-Reply-To: Julian Elischer's message of "4 Nov 1998 07:15:50 +0200"
Message-ID: <864ssed19k.fsf@not.oeno.com>
Lines: 21
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Julian Elischer <julian@whistle.com> writes:
> easier to simply have a single pointer in a known address
> that gets rewritten by the kernel on scheduling.. probably actually an
> array of them, (one per cpu) with a 'getcpunumber()' to allow
> the thread to work out which it should use.
Do I understand you correctly that you're suggesting this for
user-space code?
Finding out which cpu you're running on in user mode isn't easier than
finding out what thread you're running unless you mmap the local apic.
Even then, how do you prevent the kernel from switching while you're
holding the index? The i386 doesn't indirect deep enough in one insn.
An m68k (from 68020 up) could do it. ;--)
You know it can't switch threads because you wouldn't be executing in
that context, but each instruction executed as the thread could be
executed by a different cpu.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Wed Nov 4 23:59:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA01138
for freebsd-current-outgoing; Wed, 4 Nov 1998 23:59:54 -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 XAA01129
for <current@FreeBSD.ORG>; Wed, 4 Nov 1998 23:59:40 -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 PAA05054;
Thu, 5 Nov 1998 15:58:07 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811050758.PAA05054@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman <green@unixhelp.org>
cc: current@FreeBSD.ORG
Subject: Re: RFSIGSHARE: forgot patch ;)
In-reply-to: Your message of "Thu, 05 Nov 1998 01:13:34 EST."
<Pine.BSF.4.05.9811050110520.28066-100000@janus.syracuse.net>
Date: Thu, 05 Nov 1998 15:58:06 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Brian Feldman wrote:
> Hrmm.... I don't see why this doesn't work:
> + if (args->flags & CLONE_SIGHAND)
> + p2->p_sigacts = p->p_sigacts;
> don't tell me it's pointing into user-space, or some other neglected part
> of proc? I'll investigate I suppose. This is certainly helping me
> familiarize myself with the kernel, even if these specific patches cause a
> trap eventually (probably all the mallocing/freeing). I _really_ need to
> buy a copy of the BSD book... quick question: zalloc and malloc should
> each be used in what situations?
p_sigacts points into the UPAGES, beyond the pcb.. Check the p_addr
pointers for examples.
The reason you can't do this is because the old proc could go away at any
time, the parent process's UPAGES could get swapped out, etc. To do this,
you need to stop the parent from exiting until all children are gone (or
keep it's state around), and stop it being swapped.
> Cheers,
> Brian Feldman
> "gaining lots of experience"
>
> On Thu, 5 Nov 1998, Peter Wemm wrote:
>
> > Brian Feldman wrote:
> > [..]
> > > --- ./kern/kern_fork.c.orig Wed Nov 4 20:33:11 1998
> > > +++ ./kern/kern_fork.c Wed Nov 4 20:44:29 1998
> > > @@ -151,6 +151,10 @@
> > > p1->p_pid);
> > > return (EOPNOTSUPP);
> > > }
> > > + if (flags & RFSIGSHARE) {
> > > + printf("shared signal space attemped: pid: %d\n",
> > > p1->p_pid);
> > > + return (EOPNOTSUPP);
> > > + }
> > > #endif
> > >
> > > /*
> >
> > RFSIGSHARE should work fine on SMP.
> >
> > > @@ -320,6 +324,16 @@
> > > bcopy(p1->p_cred, p2->p_cred, sizeof(*p2->p_cred));
> > > p2->p_cred->p_refcnt = 1;
> > > crhold(p1->p_ucred);
> > > +
> > > + if (flags & RFSIGSHARE) {
> > > + p2->p_sig->p_refcnt++;
> > > + } else {
> > > + p2->p_sig = malloc(sizeof(struct procsig), M_TEMP,
> > > M_WAITOK);
> > > + p2->p_sig->p_refcnt = 1;
> > > + p2->p_sigmask = p1->p_sigmask;
> > > + p2->p_sigignore = p1->p_sigignore;
> > > + p2->p_sigcatch = p1->p_sigcatch;
> > > + }
> > >
> > > /* bump references to the text vnode (for procfs) */
> > > p2->p_textvp = p1->p_textvp;
> >
> > Umm, you are sharing the signal masks, not the signal handler vectors
> > themselves. Think p_sigacts.. Those are stored after the PCB and are
> > paged out.
> >
> > Assuming you take a shot at sharing them, try this: Keep p_sigacts there
> > by default. If a process attempts to share the signals during a fork,
> > then malloc a copy and attach it to both the child and parent. When the
> > reference count drops to 1, the remaining process should probably have
> > it's vectors copied to the upages again and the malloc space freed. But
> > good stuff so far! :-)
> >
> > Cheers,
> > -Peter
> >
> >
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-current" in the body of the message
> >
>
Cheers,
-Peter
--
Peter Wemm <peter@netplex.com.au> Netplex Consulting
"No coffee, No workee!" :-)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 00: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 AAA01208
for freebsd-current-outgoing; Thu, 5 Nov 1998 00:00:42 -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 AAA01203
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 00:00:40 -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 JAA14050
for current@FreeBSD.ORG; Thu, 5 Nov 1998 09:00:04 +0100 (MET)
Received: (from andreas@localhost)
by klemm.gtn.com (8.8.8/8.8.8) id IAA01683
for current@FreeBSD.ORG; Thu, 5 Nov 1998 08:51:14 +0100 (CET)
(envelope-from andreas)
Message-ID: <19981105085114.A1125@klemm.gtn.com>
Date: Thu, 5 Nov 1998 08:51:14 +0100
From: Andreas Klemm <andreas@klemm.gtn.com>
To: current@FreeBSD.ORG
Subject: ${MACHINE_ARCH} is still a show stopper in make aout-to-elf-build
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 2.2.7-STABLE SMP
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
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
Stop.
*** Error code 1
I "merged" this locally from -current, but it didn't help:
--- bsd.own.mk.orig Thu Nov 5 08:45:54 1998
+++ bsd.own.mk Thu Nov 5 08:46:06 1998
@@ -116,6 +116,10 @@
#
# INCLUDEDIR Base path for standard C include files [/usr/include]
+# This is only here for bootstrapping and is not officially exported
+# from here. It has normally already been defined in sys.mk.
+MACHINE_ARCH?= i386
+
# Binaries
BINOWN?= bin
BINGRP?= bin
--- sys.mk.orig Thu Nov 5 08:46:44 1998
+++ sys.mk Thu Nov 5 08:47:14 1998
@@ -94,6 +94,12 @@
YFLAGS ?= -d
.endif
+# FreeBSD/i386 as traditionally been built with a version of make
+# which knows MACHINE, but not MACHINE_ARCH. When building on other
+# architectures, assume that the version of make being used has an
+# explicit MACHINE_ARCH setting and treat a missing MACHINE_ARCH# as an i386 architecture.
+MACHINE_ARCH ?= i386
+
# For tags rule.
GTAGSFLAGS= -se
HTAGSFLAGS=
Even a
make -DMACHINE_ARCH=i386 aout-to-elf-build
doesn't work.
Well, where have these magic runes to go in ???
Sorry no time left, have to go to work.
Andreas ///
--
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 Thu Nov 5 01:05:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA08959
for freebsd-current-outgoing; Thu, 5 Nov 1998 01:05:47 -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 BAA08938
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 01:05: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 RAA05396;
Thu, 5 Nov 1998 17:02:30 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811050902.RAA05396@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Ville-Pertti Keinonen <will@iki.fi>
cc: James Mansion <james@westongold.com>, current@FreeBSD.ORG
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
In-reply-to: Your message of "05 Nov 1998 09:39:06 +0200."
<8667cud1wl.fsf@not.oeno.com>
Date: Thu, 05 Nov 1998 17:02:29 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Ville-Pertti Keinonen wrote:
[..]
> As a "fix", each process could have as many page directories as there
> are CPUs, but creating them "on-the-fly" each time would be too slow
> and letting them exist while not running the process could end up
> costing two pages per extra cpu per multithreaded process in addition
> to the actual thread-specific pages. It doesn't scale well.
Not quite.. Each process could have one page directory for each thread,
up to the number of cpus. If you only have two threads, but 4 cpus, then
you still only need 2 directories.
We have to do something like this already because of the per-cpu pages in
kernel space. However, the PTD slot is outside the reach of the user
process segment limits so we can't use one of the unused page table page
slots because the address that it corresponds to is outside the user
address space.
The only option would be to take over another PTD slot in reach of user
space, that would cost 256K of virtual address space from the user and
would cost a 4K page for the PTP as well as the data page.
Hmmmmm.. I wonder.. We might be able to create a GDT slot that maps up
into the per-cpu pages with user priviliges, then have an assembler
routine that (say) loads %fs with the descriptor index, accesses the data
relative to the %fs segment, then restores the %fs register. We could get
16 bytes of Thread Local Storage very cheaply which would not require
traps, kernel entry, etc to get access to.
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 Thu Nov 5 03:11:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA22924
for freebsd-current-outgoing; Thu, 5 Nov 1998 03:11:59 -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 DAA22904
for <current@freebsd.org>; Thu, 5 Nov 1998 03:11:46 -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 MAA04840 for current@freebsd.org; Thu, 5 Nov 1998 12:11:33 +0100 (MET)
Message-ID: <XFMail.981105121133.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: Thu, 05 Nov 1998 12:11:33 +0100 (MET)
Organization: University of bayreuth
From: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
To: current@FreeBSD.ORG
Subject: ficl broken
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
----------------------------------
Buildworld from today ( Thu Nov 5 ) failed for me with:
===> sys/boot/ficl
cc -O -pipe -I/spare2/F/src/sys/boot/ficl
-I/usr/obj/elf/spare2/F/src/tmp/usr/include -c
/spare2/F/src/sys/boot/ficl/dict.c -o dict.o
cc -O -pipe -I/spare2/F/src/sys/boot/ficl
-I/usr/obj/elf/spare2/F/src/tmp/usr/include -c
/spare2/F/src/sys/boot/ficl/ficl.c -o ficl.o
cc -O -pipe -I/spare2/F/src/sys/boot/ficl
-I/usr/obj/elf/spare2/F/src/tmp/usr/include -c
/spare2/F/src/sys/boot/ficl/math64.c -o math64.o
cc -O -pipe -I/spare2/F/src/sys/boot/ficl
-I/usr/obj/elf/spare2/F/src/tmp/usr/include -c
/spare2/F/src/sys/boot/ficl/stack.c -o stack.o
cc -O -pipe -I/spare2/F/src/sys/boot/ficl
-I/usr/obj/elf/spare2/F/src/tmp/usr/include -c
/spare2/F/src/sys/boot/ficl/sysdep.c -o sysdep.o
cc -O -pipe -I/spare2/F/src/sys/boot/ficl
-I/usr/obj/elf/spare2/F/src/tmp/usr/include -c /spare2/F/src/sys/boot/ficl/vm.c
-o vm.o
cc -O -pipe -I/spare2/F/src/sys/boot/ficl
-I/usr/obj/elf/spare2/F/src/tmp/usr/include -c
/spare2/F/src/sys/boot/ficl/words.c -o words.o
(cd /spare2/F/src/sys/boot/ficl/softwords; softcore.pl softcore.fr jhlocal.fr
marker.fr) > softcore.c
softcore.pl: not found
*** Error code 127
Werner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 03:20:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA23943
for freebsd-current-outgoing; Thu, 5 Nov 1998 03:20:57 -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 DAA23938
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 03:20:55 -0800 (PST)
(envelope-from will@ns.oeno.com)
Received: (qmail 671 invoked by uid 1001); 5 Nov 1998 11:20:45 -0000
Date: 5 Nov 1998 11:20:45 -0000
Message-ID: <19981105112045.668.qmail@ns.oeno.com>
From: Ville-Pertti Keinonen <will@iki.fi>
To: peter@netplex.com.au
CC: james@westongold.com, current@FreeBSD.ORG
In-reply-to: <199811050902.RAA05396@spinner.netplex.com.au> (message from
Peter Wemm on Thu, 05 Nov 1998 17:02:29 +0800)
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Not quite.. Each process could have one page directory for each thread,
> up to the number of cpus. If you only have two threads, but 4 cpus, then
> you still only need 2 directories.
True, I was silently assuming that there are more threads than cpus.
It doesn't change the fact that the resource requirements don't seem
reasonable. Pages are huge.
> We have to do something like this already because of the per-cpu pages in
> kernel space. However, the PTD slot is outside the reach of the user
> process segment limits so we can't use one of the unused page table page
> slots because the address that it corresponds to is outside the user
> address space.
The existing per-cpu pages might be worth getting rid of.
I'm not sure how much data is currently kept there, but the overhead
of APIC ID indexing shouldn't be too bad.
> The only option would be to take over another PTD slot in reach of user
> space, that would cost 256K of virtual address space from the user and
> would cost a 4K page for the PTP as well as the data page.
256k? Don't you mean 4MB?
I don't think a user address space should contain magic unless it has
been explicitly requested by the program.
Multithreaded programs are going to have to perform user-space
initialization, in any case. Explicitly mmapping special kernel pages
might not be out of the question.
It still wouldn't be nice to either waste a whole page for a bit of
thread-specific data or reveal inconsistent information on the rest of
the page.
> Hmmmmm.. I wonder.. We might be able to create a GDT slot that maps up
> into the per-cpu pages with user priviliges, then have an assembler
> routine that (say) loads %fs with the descriptor index, accesses the data
> relative to the %fs segment, then restores the %fs register. We could get
That's starting to sound like a reasonable idea.
Didn't FreeBSD not even save %fs? The kernel could always set it
before going into user mode, so that it doesn't need to be loaded for
each access. The kernel must either save or set it to make it usable
at all.
Setting it in the kernel is probably better, to avoid changing things
like sigcontext, and if per-cpu pages are not used, things can still
work since the kernel can set the register to a cpu-specific segment.
IMHO the alternative of using aligned thread stacks is not a bad idea,
either. It's fast and portable and it doesn't require anything evil
to be done by the kernel. The restrictions placed on what can be done
with the threads are a bit nasty, though.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 04:12:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA01812
for freebsd-current-outgoing; Thu, 5 Nov 1998 04:12:52 -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 EAA01806;
Thu, 5 Nov 1998 04:12:50 -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 EAA02997;
Thu, 5 Nov 1998 04:11:20 -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 EAA11046;
Thu, 5 Nov 1998 04:11:19 -0800 (PST)
Received: (from gdonl@localhost)
by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id EAA13769;
Thu, 5 Nov 1998 04:11:18 -0800 (PST)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199811051211.EAA13769@salsa.gv.tsc.tdk.com>
Date: Thu, 5 Nov 1998 04:11:17 -0800
In-Reply-To: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
"ficl broken" (Nov 5, 12:11pm)
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>, current@FreeBSD.ORG
Subject: Re: ficl broken
Cc: msmith@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
${PERL} isn't defined in sys/boot/ficl/Makefile. It should either be defined
(in sys.mk?) or 'perl' should be used instead.
Hmn, I also see both ${CC} and 'cc' being used ...
On Nov 5, 12:11pm, Werner Griessl wrote:
} Subject: ficl broken
}
} ----------------------------------
}
} Buildworld from today ( Thu Nov 5 ) failed for me with:
}
} ===> sys/boot/ficl
} cc -O -pipe -I/spare2/F/src/sys/boot/ficl
} -I/usr/obj/elf/spare2/F/src/tmp/usr/include -c
} /spare2/F/src/sys/boot/ficl/dict.c -o dict.o
} cc -O -pipe -I/spare2/F/src/sys/boot/ficl
} -I/usr/obj/elf/spare2/F/src/tmp/usr/include -c
} /spare2/F/src/sys/boot/ficl/ficl.c -o ficl.o
} cc -O -pipe -I/spare2/F/src/sys/boot/ficl
} -I/usr/obj/elf/spare2/F/src/tmp/usr/include -c
} /spare2/F/src/sys/boot/ficl/math64.c -o math64.o
} cc -O -pipe -I/spare2/F/src/sys/boot/ficl
} -I/usr/obj/elf/spare2/F/src/tmp/usr/include -c
} /spare2/F/src/sys/boot/ficl/stack.c -o stack.o
} cc -O -pipe -I/spare2/F/src/sys/boot/ficl
} -I/usr/obj/elf/spare2/F/src/tmp/usr/include -c
} /spare2/F/src/sys/boot/ficl/sysdep.c -o sysdep.o
} cc -O -pipe -I/spare2/F/src/sys/boot/ficl
} -I/usr/obj/elf/spare2/F/src/tmp/usr/include -c /spare2/F/src/sys/boot/ficl/vm.c
} -o vm.o
} cc -O -pipe -I/spare2/F/src/sys/boot/ficl
} -I/usr/obj/elf/spare2/F/src/tmp/usr/include -c
} /spare2/F/src/sys/boot/ficl/words.c -o words.o
} (cd /spare2/F/src/sys/boot/ficl/softwords; softcore.pl softcore.fr jhlocal.fr
} marker.fr) > softcore.c
} softcore.pl: not found
} *** Error code 127
}
} Werner
}
}
}
}
} To Unsubscribe: send mail to majordomo@FreeBSD.org
} with "unsubscribe freebsd-current" in the body of the message
}-- End of excerpt from Werner Griessl
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 06: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 GAA16578
for freebsd-current-outgoing; Thu, 5 Nov 1998 06:13:58 -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 GAA16571
for <freebsd-current@freebsd.org>; Thu, 5 Nov 1998 06:13:48 -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 PAA24738
for <freebsd-current@freebsd.org>; Thu, 5 Nov 1998 15:13:16 +0100 (MET)
Received: (from cejkar@localhost)
by kazi.dcse.fee.vutbr.cz (8.8.8/8.8.8) id PAA16305
for freebsd-current@freebsd.org; Thu, 5 Nov 1998 15:13:16 +0100 (CET)
From: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>
Message-Id: <199811051413.PAA16305@kazi.dcse.fee.vutbr.cz>
Subject: Re: ELFoized xtt-SVGA-1.0 & TrueType fonts => HANG
To: freebsd-current@freebsd.org (freebsd-current@freebsd.org)
Date: Thu, 5 Nov 1998 15:13:16 +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
> > I have ELFoized -current:
> > Main system (/usr/src): 98/09/28
>
> It's old. If you use 98/10/13 or later -current, I think
> you can use Xtt with no trouble!
>
> # I can use Xtt on the latest -current.
> - ---------
> Shigeyuki FUKUSHIMA <shige@kuis.kyoto-u.ac.jp>
> Dept. of Information Science, Kyoto Univ,. JAPAN
Yes! Thanks! This was my problem.
I have today's -current (98/11/05) now and XF86_SVGA.xtt has returned
back to me...
--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--
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 Thu Nov 5 06:30:17 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA18100
for freebsd-current-outgoing; Thu, 5 Nov 1998 06:30:17 -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 GAA18095
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 06:30:13 -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 WAA06376;
Thu, 5 Nov 1998 22:28:47 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811051428.WAA06376@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Ville-Pertti Keinonen <will@iki.fi>
cc: james@westongold.com, current@FreeBSD.ORG
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
In-reply-to: Your message of "05 Nov 1998 11:20:45 GMT."
<19981105112045.668.qmail@ns.oeno.com>
Date: Thu, 05 Nov 1998 22:28:46 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Ville-Pertti Keinonen wrote:
>
> > Not quite.. Each process could have one page directory for each thread,
> > up to the number of cpus. If you only have two threads, but 4 cpus, then
> > you still only need 2 directories.
>
> True, I was silently assuming that there are more threads than cpus.
> It doesn't change the fact that the resource requirements don't seem
> reasonable. Pages are huge.
Yes.
> > We have to do something like this already because of the per-cpu pages in
> > kernel space. However, the PTD slot is outside the reach of the user
> > process segment limits so we can't use one of the unused page table page
> > slots because the address that it corresponds to is outside the user
> > address space.
>
> The existing per-cpu pages might be worth getting rid of.
>
> I'm not sure how much data is currently kept there, but the overhead
> of APIC ID indexing shouldn't be too bad.
We've done it that way before and it was a real pain in the backside. There
are a number of disincentives:
- apic id's are all over the place. 0, 12 and 13 are common with P6's.
Having 16 slots in arrays for all the per-cpu variables is not nice.
- converting physical id's back into compacted logical id's is OK from
C but a pain in assembler.
- converting things from variables to macros shows up other things. I
seem to recall some places where "curproc" was referenced over and
over again in loops and the like.
- we have to have different binaries modules/lkm's for SMP and non-smp
kernels.
- accessing the local apic is *much* slower than a memory access (according
to one of the intel people who told us to try and do it this way if we
could).
- it was a lot of pain to get working in the first place.
> > The only option would be to take over another PTD slot in reach of user
> > space, that would cost 256K of virtual address space from the user and
> > would cost a 4K page for the PTP as well as the data page.
>
> 256k? Don't you mean 4MB?
Sorry, yes.
> I don't think a user address space should contain magic unless it has
> been explicitly requested by the program.
>
> Multithreaded programs are going to have to perform user-space
> initialization, in any case. Explicitly mmapping special kernel pages
> might not be out of the question.
>
> It still wouldn't be nice to either waste a whole page for a bit of
> thread-specific data or reveal inconsistent information on the rest of
> the page.
Yep.
> > Hmmmmm.. I wonder.. We might be able to create a GDT slot that maps up
> > into the per-cpu pages with user priviliges, then have an assembler
> > routine that (say) loads %fs with the descriptor index, accesses the data
> > relative to the %fs segment, then restores the %fs register. We could get
>
> That's starting to sound like a reasonable idea.
>
> Didn't FreeBSD not even save %fs? The kernel could always set it
> before going into user mode, so that it doesn't need to be loaded for
> each access. The kernel must either save or set it to make it usable
> at all.
It used to not be preserved or context switched. It is now.
> Setting it in the kernel is probably better, to avoid changing things
> like sigcontext, and if per-cpu pages are not used, things can still
> work since the kernel can set the register to a cpu-specific segment.
It still needs assembler support in the user land threading system,
because gcc will not (I think) generate code to use segment loads and
prefixes by itself. The point is that if a descriptor table slot is
available, any segment register can be used to select it.
John wrote something to use the LDT on a per-thread basis, I never really
sat down to see what he did.
But, if we provide a void *thread_getpointer() and
void thread_setpointer(void *) in libc, this just has to be a few
assembler instructions for setting %fs, using a %fs data reference,
restoring %fs and returning the data.
rfork() could "set" %fs for the child to tell it what slot to use. If it
wished to leave %fs untouched, it could use it at any time. Otherwise it
would have to store it somewhere. It would be the same value for all
processes on the system.
> IMHO the alternative of using aligned thread stacks is not a bad idea,
> either. It's fast and portable and it doesn't require anything evil
> to be done by the kernel. The restrictions placed on what can be done
> with the threads are a bit nasty, though.
The bit that I don't like about it is that it forces all the stacks to have
the same upper limit size. That could be a bit wasteful of address space,
or could leave you short on room to grow the stack. Incidently, I'd like a
special mmap() option to provide a real grow-down stack in a specified
region. mmap()ing a few hundred kb of stack from anonymous swap times a
few hundred threads adds up on the size counter.
Also, while on the subject, something Julian said has got me thinking about
creating kernel threads on the fly when and if a user thread happens to
block. This sounds rather interesting.. - async IO is done this way too I
think. It would require a fair amount of cooperation between the thread
"engine" and the kernel, perhaps by having an executive thread of sorts
that handled the kernel interation and thread activation.
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 5 06:58:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA21338
for freebsd-current-outgoing; Thu, 5 Nov 1998 06:58:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21332
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 06:58:11 -0800 (PST)
(envelope-from reg@shale.csir.co.za)
Received: (from reg@localhost)
by shale.csir.co.za (8.9.1/8.9.1) id QAA27243;
Thu, 5 Nov 1998 16:56:49 +0200 (SAT)
(envelope-from reg)
Message-ID: <19981105165649.B303@shale.csir.co.za>
Date: Thu, 5 Nov 1998 16:56:49 +0200
From: Jeremy Lea <reg@shale.csir.co.za>
To: John Birrell <jb@cimlogic.com.au>
Cc: current@FreeBSD.ORG
Subject: Re: poll() for pthreads?
References: <19981105005122.A13038@shale.csir.co.za> <199811050022.LAA24698@cimlogic.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199811050022.LAA24698@cimlogic.com.au>; from John Birrell on Thu, Nov 05, 1998 at 11:22:36AM +1100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
On Thu, Nov 05, 1998 at 11:22:36AM +1100, John Birrell wrote:
> To implement poll(2) properly, the internal use of select(2) as the
> blocking mechanism needs to be changed to use poll. It's not just a matter
> of a wrapper, since you can implement true poll functionality with
> select.
OK, well I'll leave it then. As I said, it's way out of my league.
> I thought Netscape were using their own threads.
NSPR is their threading library, along with providing a uniform platform
for their software (Mozilla, servers, etc.) on Unix, Win, Mac, etc. It
can be compiled to wrap the native threads for the platform, since it
can then use kernel threads.
Even though it would be a net loss under the current pthreads, it would
be nice if we ever get kernel threads. NSPR (and Mozilla) are known to
work on other platforms so they could show up bugs in our thread code.
Plus I'm just one of those people who wants to try all the buttons...
Regards,
-Jeremy
--
| "In this world of temptation, I will stand for what is right.
--+-- With a heart of salvation, I will hold up the light.
| If I live or if I die, if I laugh or if I cry,
| in this world of temptation, I will stand." -Pam Thum
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 07: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 HAA26225
for freebsd-current-outgoing; Thu, 5 Nov 1998 07:47:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from atena.eurocontrol.fr (atena.uneec.eurocontrol.fr [147.196.69.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26215
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 07:47:31 -0800 (PST)
(envelope-from roberto@eurocontrol.fr)
Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.30.193])
by atena.eurocontrol.fr (8.9.1/8.9.1/atena-1.1/nospam) with ESMTP id QAA28784
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 16:47:02 +0100 (MET)
(envelope-from roberto@caerdonn.eurocontrol.fr)
Received: by caerdonn.eurocontrol.fr (VMailer, from userid 1193)
id 95354103; Thu, 5 Nov 1998 16:47:01 +0100 (CET)
Date: Thu, 5 Nov 1998 16:47:00 +0100
From: Ollivier Robert <roberto@eurocontrol.fr>
To: "FreeBSD Current Users' list" <freebsd-current@FreeBSD.ORG>
Subject: make world breakage
Message-ID: <19981105164700.C359@caerdonn.eurocontrol.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.4i
X-Operating-System: FreeBSD 3.0-CURRENT
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
cc -O -pipe -I/src/src/sys/boot/ficl -I/usr/obj/elf/src/src/tmp/usr/include -c /src/src/sys/boot/ficl/words.c -o words.o
(cd /src/src/sys/boot/ficl/softwords; perl softcore.pl softcore.fr jhlocal.fr marker.fr) > softcore.c
perl: not found
*** Error code 127
Stop.
The perl binary is not found/built at this time.
--
Ollivier ROBERT -=- Eurocontrol EEC/TS -=- Ollivier.Robert@eurocontrol.fr
The Postman hits! The Postman hits! You have new mail.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 08:38:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA01395
for freebsd-current-outgoing; Thu, 5 Nov 1998 08:38:30 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles325.castles.com [208.214.167.25])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01386
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 08:38:26 -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 IAA03234;
Thu, 5 Nov 1998 08:35:52 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811051635.IAA03234@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
cc: current@FreeBSD.ORG
Subject: Re: ficl broken
In-reply-to: Your message of "Thu, 05 Nov 1998 12:11:33 +0100."
<XFMail.981105121133.werner@btp1da.phy.uni-bayreuth.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Nov 1998 08:35:52 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> (cd /spare2/F/src/sys/boot/ficl/softwords; softcore.pl softcore.fr jhlocal.fr
> marker.fr) > softcore.c
^^
There should be 'perl' here.
> softcore.pl: not found
> *** Error code 127
Can you check src/sys/boot/ficl/Makefile whence that invocation comes
and verify whether it's got the 'perl' word there?
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 09:00:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA02949
for freebsd-current-outgoing; Thu, 5 Nov 1998 09:00: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 JAA02939
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 09:00:22 -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 RAA12255; Thu, 5 Nov 1998 17:59:42 +0100 (MET)
Message-ID: <XFMail.981105175942.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
In-Reply-To: <199811051635.IAA03234@dingo.cdrom.com>
Date: Thu, 05 Nov 1998 17:59:42 +0100 (MET)
Organization: University of bayreuth
From: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
To: Mike Smith <mike@smith.net.au>
Subject: Re: ficl broken
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 05-Nov-98 Mike Smith wrote:
>>
>> (cd /spare2/F/src/sys/boot/ficl/softwords; softcore.pl softcore.fr
>> jhlocal.fr
>> marker.fr) > softcore.c
> ^^
> There should be 'perl' here.
>> softcore.pl: not found
>> *** Error code 127
>
> Can you check src/sys/boot/ficl/Makefile whence that invocation comes
> and verify whether it's got the 'perl' word there?
> --
> \\ Sometimes you're ahead, \\ Mike Smith
> \\ sometimes you're behind. \\ mike@smith.net.au
> \\ The race is long, and in the \\ msmith@freebsd.org
> \\ end it's only with yourself. \\ msmith@cdrom.com
----------------------------------
I cvsupped the tree again and now 'perl' is there (wasn't before).
Buildworld is currently already building the 'aout'-part
(passed 'ficl' successfully) .
Thanks for the quick fix.
Werner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 09:12:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA03750
for freebsd-current-outgoing; Thu, 5 Nov 1998 09:12: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 JAA03741;
Thu, 5 Nov 1998 09:12:14 -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 JAA19811;
Thu, 5 Nov 1998 09:12:07 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Don Lewis <Don.Lewis@tsc.tdk.com>
cc: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>, current@FreeBSD.ORG,
msmith@FreeBSD.ORG
Subject: Re: ficl broken
In-reply-to: Your message of "Thu, 05 Nov 1998 04:11:17 PST."
<199811051211.EAA13769@salsa.gv.tsc.tdk.com>
Date: Thu, 05 Nov 1998 09:12:07 -0800
Message-ID: <19807.910285927@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> ${PERL} isn't defined in sys/boot/ficl/Makefile. It should either be defined
> (in sys.mk?) or 'perl' should be used instead.
Very temporary abberation - I fixed it about 10 minutes later. :)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 10:09:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA08784
for freebsd-current-outgoing; Thu, 5 Nov 1998 10:09:52 -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 KAA08779
for <freebsd-current@freebsd.org>; Thu, 5 Nov 1998 10:09:48 -0800 (PST)
(envelope-from shimon@simon-shapiro.org)
Received: (qmail 27194 invoked by uid 1000); 5 Nov 1998 19:13:29 -0000
Message-ID: <XFMail.981105141329.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
Date: Thu, 05 Nov 1998 14:13:29 -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: freebsd-current@FreeBSD.ORG
Subject: Make Release Failure...
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
This I am getting for two or three days in a row. Any idea?
loading kernel
text data bss dec hex filename
1455152 104816 112652 1672620 1985ac kernel
./dumpnlist /R/stage/boot.std/kernel > /tmp/mnt_xx/stand/symbols
kzip -v /R/stage/boot.std/kernel
kzip: bad magic in file /R/stage/boot.std/kernel, probably not a kernel
kzip: extract returned 200
real kernel start address will be: 0x1
real kernel end address will be: 0x65aac68a
*** Error code 3
Stop.
Sincerely Yours, Shimon@Simon-Shapiro.ORG
770.265.7340
Simon Shapiro
Unwritten code has no bugs and executes at twice the speed of mouth
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 10:43:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA12247
for freebsd-current-outgoing; Thu, 5 Nov 1998 10:43:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12241
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 10:43:48 -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 KAA03840;
Thu, 5 Nov 1998 10:42:53 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811051842.KAA03840@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Ollivier Robert <roberto@eurocontrol.fr>
cc: "FreeBSD Current Users' list" <freebsd-current@FreeBSD.ORG>
Subject: Re: make world breakage
In-reply-to: Your message of "Thu, 05 Nov 1998 16:47:00 +0100."
<19981105164700.C359@caerdonn.eurocontrol.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Nov 1998 10:42:52 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> cc -O -pipe -I/src/src/sys/boot/ficl -I/usr/obj/elf/src/src/tmp/usr/include -c /src/src/sys/boot/ficl/words.c -o words.o
> (cd /src/src/sys/boot/ficl/softwords; perl softcore.pl softcore.fr jhlocal.fr marker.fr) > softcore.c
> perl: not found
> *** Error code 127
>
> Stop.
>
> The perl binary is not found/built at this time.
Funny; it works elsewhere. You don't have perl in /usr/bin?
--
\\ 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 5 10:44:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA12368
for freebsd-current-outgoing; Thu, 5 Nov 1998 10:44:47 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12362
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 10:44:39 -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 KAA03854;
Thu, 5 Nov 1998 10:43:51 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811051843.KAA03854@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: shimon@simon-shapiro.org
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Make Release Failure...
In-reply-to: Your message of "Thu, 05 Nov 1998 14:13:29 EST."
<XFMail.981105141329.shimon@simon-shapiro.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Nov 1998 10:43:50 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> This I am getting for two or three days in a row. Any idea?
You're trying to build a release with KERNFORMAT set to elf. You can't
do that yet.
> loading kernel
> text data bss dec hex filename
> 1455152 104816 112652 1672620 1985ac kernel
> ./dumpnlist /R/stage/boot.std/kernel > /tmp/mnt_xx/stand/symbols
> kzip -v /R/stage/boot.std/kernel
> kzip: bad magic in file /R/stage/boot.std/kernel, probably not a kernel
> kzip: extract returned 200
> real kernel start address will be: 0x1
> real kernel end address will be: 0x65aac68a
> *** Error code 3
>
> Stop.
>
>
> Sincerely Yours, Shimon@Simon-Shapiro.ORG
> 770.265.7340
> Simon Shapiro
>
> Unwritten code has no bugs and executes at twice the speed of mouth
>
>
> 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 Thu Nov 5 10:48:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA12882
for freebsd-current-outgoing; Thu, 5 Nov 1998 10:48:43 -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 KAA12875
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 10:48:42 -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 NAA20928;
Thu, 5 Nov 1998 13:51:48 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Thu, 5 Nov 1998 13:51:48 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Simon Shapiro <shimon@simon-shapiro.org>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Make Release Failure...
In-Reply-To: <XFMail.981105141329.shimon@simon-shapiro.org>
Message-ID: <Pine.BSF.4.05.9811051350400.10448-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, 5 Nov 1998, Simon Shapiro wrote:
> This I am getting for two or three days in a row. Any idea?
>
> loading kernel
> text data bss dec hex filename
> 1455152 104816 112652 1672620 1985ac kernel
> ./dumpnlist /R/stage/boot.std/kernel > /tmp/mnt_xx/stand/symbols
> kzip -v /R/stage/boot.std/kernel
> kzip: bad magic in file /R/stage/boot.std/kernel, probably not a kernel
> kzip: extract returned 200
> real kernel start address will be: 0x1
> real kernel end address will be: 0x65aac68a
> *** Error code 3
>
do you have KERNFORMAT=elf?
i don't think it's supported as of yet.
-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 5 11:01:08 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA14335
for freebsd-current-outgoing; Thu, 5 Nov 1998 11:01:08 -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 LAA14327
for <current@freebsd.org>; Thu, 5 Nov 1998 11:01:06 -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 SMTP id LAA00343
for <current@freebsd.org>; Thu, 5 Nov 1998 11:00:57 -0800 (PST)
(envelope-from brian@CSUA.Berkeley.EDU)
Date: Thu, 5 Nov 1998 11:00:56 -0800 (PST)
From: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>
X-Sender: brian@smarter.than.nu
To: current@FreeBSD.ORG
Subject: Re: USERCONFIG_BOOT, heads up!
In-Reply-To: <199811032116.NAA00460@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.02A.9811051054490.314-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 Tue, 3 Nov 1998, Mike Smith wrote:
> Now, to load a userconfig script you must be using the new 3-stage
> bootloader. To load a script, either execute this command manually,
> or insert it in /boot/boot.conf:
>
> 'load -t userconfig_script <scriptfile>'
I tried the following:
disklabel -B /dev/wd0s1
mv /kernel.config /pnp.setup
echo "load -t userconfig_script pnp.setup" > /boot/boot.conf
However, it doesn't seem that the script is getting executed, as my PNP
AWE64 isn't being properly set up.
pnp.setup contains:
USERCONFIG
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
quit
Ideas?
--
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 Thu Nov 5 11: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 LAA15476
for freebsd-current-outgoing; Thu, 5 Nov 1998 11:09:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15466
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 11:09:29 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA04040;
Thu, 5 Nov 1998 11:08:42 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811051908.LAA04040@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: USERCONFIG_BOOT, heads up!
In-reply-to: Your message of "Thu, 05 Nov 1998 11:00:56 PST."
<Pine.BSF.4.02A.9811051054490.314-100000@smarter.than.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Nov 1998 11:08:42 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On Tue, 3 Nov 1998, Mike Smith wrote:
>
> > Now, to load a userconfig script you must be using the new 3-stage
> > bootloader. To load a script, either execute this command manually,
> > or insert it in /boot/boot.conf:
> >
> > 'load -t userconfig_script <scriptfile>'
>
> I tried the following:
>
> disklabel -B /dev/wd0s1
What's that for?
> mv /kernel.config /pnp.setup
> echo "load -t userconfig_script pnp.setup" > /boot/boot.conf
>
> However, it doesn't seem that the script is getting executed, as my PNP
> AWE64 isn't being properly set up.
>
> pnp.setup contains:
> USERCONFIG
> 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
> quit
>
> Ideas?
Are you running the new loader? The 'disklabel' command you gave
will have written the old boot1/boot2 out, which don't default to
running the loader.
Incidentally, you should only have to run the above 'pnp' commands once;
they should be saved by 'dset' back into the kernel during the boot
process.
--
\\ 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 5 11:13:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA16067
for freebsd-current-outgoing; Thu, 5 Nov 1998 11:13:57 -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 LAA16053
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 11:13:43 -0800 (PST)
(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id OAA27151;
Thu, 5 Nov 1998 14:13:11 -0500 (EST)
(envelope-from wollman)
Date: Thu, 5 Nov 1998 14:13:11 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199811051913.OAA27151@khavrinen.lcs.mit.edu>
To: Mike Smith <mike@smith.net.au>
Cc: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>, current@FreeBSD.ORG
Subject: Re: USERCONFIG_BOOT, heads up!
In-Reply-To: <199811051908.LAA04040@dingo.cdrom.com>
References: <Pine.BSF.4.02A.9811051054490.314-100000@smarter.than.nu>
<199811051908.LAA04040@dingo.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Thu, 05 Nov 1998 11:08:42 -0800, Mike Smith <mike@smith.net.au> said:
> Incidentally, you should only have to run the above 'pnp' commands once;
> they should be saved by 'dset' back into the kernel during the boot
> process.
Unless you're like me and have permanently disabled the evil dset
program.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 11:14:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA16194
for freebsd-current-outgoing; Thu, 5 Nov 1998 11:14:07 -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 LAA16189
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 11:14:06 -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 SMTP id LAA00401;
Thu, 5 Nov 1998 11:13:46 -0800 (PST)
(envelope-from brian@CSUA.Berkeley.EDU)
Date: Thu, 5 Nov 1998 11:13:46 -0800 (PST)
From: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>
X-Sender: brian@smarter.than.nu
To: Mike Smith <mike@smith.net.au>
cc: current@FreeBSD.ORG
Subject: Re: USERCONFIG_BOOT, heads up!
In-Reply-To: <199811051908.LAA04040@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.02A.9811051111170.314-100000@smarter.than.nu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 5 Nov 1998, Mike Smith wrote:
> > On Tue, 3 Nov 1998, Mike Smith wrote:
> >
> > > Now, to load a userconfig script you must be using the new 3-stage
> > > bootloader. To load a script, either execute this command manually,
> > > or insert it in /boot/boot.conf:
> > >
> > > 'load -t userconfig_script <scriptfile>'
> >
> > I tried the following:
> >
> > disklabel -B /dev/wd0s1
>
> What's that for?
I really had no clue how to install the new loader, and I couldn't find
any docs for it. The manpage for disklabel said that -B would install the
standard loader, so... :)
> Are you running the new loader? The 'disklabel' command you gave
> will have written the old boot1/boot2 out, which don't default to
> running the loader.
I suppose not. How do I install it?
> Incidentally, you should only have to run the above 'pnp' commands once;
> they should be saved by 'dset' back into the kernel during the boot
> process.
Right, but wouldn't I have to reissue them every time I built a new
kernel?
--
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 Thu Nov 5 11:21:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA17364
for freebsd-current-outgoing; Thu, 5 Nov 1998 11:21:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17320
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 11:21:11 -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 LAA04146;
Thu, 5 Nov 1998 11:19:59 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811051919.LAA04146@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: USERCONFIG_BOOT, heads up!
In-reply-to: Your message of "Thu, 05 Nov 1998 11:13:46 PST."
<Pine.BSF.4.02A.9811051111170.314-100000@smarter.than.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Nov 1998 11:19:58 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > > > Now, to load a userconfig script you must be using the new 3-stage
> > > > bootloader. To load a script, either execute this command manually,
> > > > or insert it in /boot/boot.conf:
> > > >
> > > > 'load -t userconfig_script <scriptfile>'
> > >
> > > I tried the following:
> > >
> > > disklabel -B /dev/wd0s1
> >
> > What's that for?
>
> I really had no clue how to install the new loader, and I couldn't find
> any docs for it. The manpage for disklabel said that -B would install the
> standard loader, so... :)
Ah, OK. The best way to switch is probably to install the new
bootstrap. There's some terminology fog here; there are four
components in the new boot path:
- boot0 (looks like booteasy, optional)
- boot1
- boot2
- /boot/loader
These are all new, although boot1 and boot2 share names with the old
bootstrap components.
You don't need to update boot0 if you already have something like it
installed, or you're not doing the multiple OS thing.
To install the new boot1/boot2, say:
disklabel -B -b /boot/boot1 -s /boot/boot2 wd0s1
You should remove any existing /boot.config file.
> > Incidentally, you should only have to run the above 'pnp' commands once;
> > they should be saved by 'dset' back into the kernel during the boot
> > process.
>
> Right, but wouldn't I have to reissue them every time I built a new
> kernel?
Yes.
--
\\ 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 5 11:22:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA17528
for freebsd-current-outgoing; Thu, 5 Nov 1998 11:22:03 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles232.castles.com [208.214.165.232])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17405
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 11:21: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 LAA04161;
Thu, 5 Nov 1998 11:20:41 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811051920.LAA04161@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: Mike Smith <mike@smith.net.au>,
"Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>, current@FreeBSD.ORG
Subject: Re: USERCONFIG_BOOT, heads up!
In-reply-to: Your message of "Thu, 05 Nov 1998 14:13:11 EST."
<199811051913.OAA27151@khavrinen.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Nov 1998 11:20:41 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> <<On Thu, 05 Nov 1998 11:08:42 -0800, Mike Smith <mike@smith.net.au> said:
>
> > Incidentally, you should only have to run the above 'pnp' commands once;
> > they should be saved by 'dset' back into the kernel during the boot
> > process.
>
> Unless you're like me and have permanently disabled the evil dset
> program.
It'll do until we get a persistent kernel registry going.
--
\\ 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 5 11:36:45 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA19855
for freebsd-current-outgoing; Thu, 5 Nov 1998 11:36:45 -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 LAA19846
for <freebsd-current@freebsd.org>; Thu, 5 Nov 1998 11:36:35 -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 UAA03071
for <freebsd-current@freebsd.org>; Thu, 5 Nov 1998 20:42:34 +0100 (CET)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Thu, 5 Nov 1998 20:42:34 +0100 (CET)
From: Andrzej Bialecki <abial@nask.pl>
X-Sender: abial@korin.warman.org.pl
To: freebsd-current@FreeBSD.ORG
Subject: BootForth strange behaviour
Message-ID: <Pine.BSF.4.02A.9811052038500.1165-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
Hi,
One of last commits to /sys/boot (I'm not sure which) caused that Forth
interpreter accepts only one-liners, i.e.:
> : test ." hello world" cr ;
works, but
> :test
> ." hello world"
barfs that ." is a compile-only word...
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 Thu Nov 5 11: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 LAA20111
for freebsd-current-outgoing; Thu, 5 Nov 1998 11:39:16 -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 LAA20103
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 11:39:15 -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 SMTP id LAA00314;
Thu, 5 Nov 1998 11:38:58 -0800 (PST)
(envelope-from brian@CSUA.Berkeley.EDU)
Date: Thu, 5 Nov 1998 11:38:58 -0800 (PST)
From: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>
X-Sender: brian@smarter.than.nu
To: Mike Smith <mike@smith.net.au>
cc: current@FreeBSD.ORG
Subject: Re: USERCONFIG_BOOT, heads up!
In-Reply-To: <199811051919.LAA04146@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.02A.9811051137380.311-100000@smarter.than.nu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, 5 Nov 1998, Mike Smith wrote:
> disklabel -B -b /boot/boot1 -s /boot/boot2 wd0s1
Ack. I did exactly that, then rebooted. At the point where the boot
prompt would, normally appear, the system simply rebooted itself. I had
to dig up an install floppy and restore the old bootloader.
--
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 Thu Nov 5 11:56:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA22336
for freebsd-current-outgoing; Thu, 5 Nov 1998 11:56:52 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from Gambit.Msk.SU (gambit.msk.su [194.190.206.62])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22122
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 11:55:52 -0800 (PST)
(envelope-from laskavy@Gambit.Msk.SU)
Received: (from laskavy@localhost)
by Gambit.Msk.SU (8.0/8.9.1) id WAA16357;
Thu, 5 Nov 1998 22:55:31 +0300 (MSK)
Message-ID: <19981105225531.A16317@gambit.msk.su>
Date: Thu, 5 Nov 1998 22:55:31 +0300
From: Sergei Laskavy <laskavy@Gambit.Msk.SU>
To: Andrzej Bialecki <abial@nask.pl>, freebsd-current@FreeBSD.ORG
Subject: Re: BootForth strange behaviour
Mail-Followup-To: Andrzej Bialecki <abial@nask.pl>,
freebsd-current@FreeBSD.ORG
References: <Pine.BSF.4.02A.9811052038500.1165-100000@korin.warman.org.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.02A.9811052038500.1165-100000@korin.warman.org.pl>; from Andrzej Bialecki on Thu, Nov 05, 1998 at 08:42:34PM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Thu, Nov 05, 1998 at 08:42:34PM +0100, Andrzej Bialecki wrote:
> One of last commits to /sys/boot (I'm not sure which) caused that Forth
> interpreter accepts only one-liners, i.e.:
>
> > : test ." hello world" cr ;
>
> works, but
>
> > :test
> > ." hello world"
>
> barfs that ." is a compile-only word...
You want to use
: test
." hello world"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 12:01:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA22957
for freebsd-current-outgoing; Thu, 5 Nov 1998 12:01:31 -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 MAA22945
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 12:01:26 -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 VAA09450
for current@FreeBSD.ORG; Thu, 5 Nov 1998 21:00:08 +0100 (MET)
Received: (from andreas@localhost)
by klemm.gtn.com (8.8.8/8.8.8) id UAA07645
for current@FreeBSD.ORG; Thu, 5 Nov 1998 20:46:10 +0100 (CET)
(envelope-from andreas)
Message-ID: <19981105204609.A5684@klemm.gtn.com>
Date: Thu, 5 Nov 1998 20:46:09 +0100
From: Andreas Klemm <andreas@klemm.gtn.com>
To: current@FreeBSD.ORG
Subject: make aout-to-elf-install, mv: rename /usr/lib/libc.so.3.1 to /usr/lib/aout/libc.so.3.1: Operation not permitted
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 2.2.7-STABLE SMP
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi !
During make aout-to-elf-install:
Do we have to add a
chflags -noschg .....
???????
Because of these errors:
Move libc.so.3.1 from /usr/lib to /usr/lib/aout
mv: rename /usr/lib/libc.so.3.1 to /usr/lib/aout/libc.so.3.1: Operation not permitted
Move libc_r.so.3.0 from /usr/lib to /usr/lib/aout
mv: rename /usr/lib/libc_r.so.3.0 to /usr/lib/aout/libc_r.so.3.0: Operation not permitted
Move libcalendar.so.2.0 from /usr/lib to /usr/lib/aout
Move libcipher.so.2.0 from /usr/lib to /usr/lib/aout
mv: rename /usr/lib/libcipher.so.2.0 to /usr/lib/aout/libcipher.so.2.0: Operation not permitted
Move libcom_err.so.2.0 from /usr/lib to /usr/lib/aout
Move libcurses.so.2.0 from /usr/lib to /usr/lib/aout
Move libdes.so.3.0 from /usr/lib to /usr/lib/aout
Move libdescrypt.so.2.0 from /usr/lib to /usr/lib/aout
mv: rename /usr/lib/libdescrypt.so.2.0 to /usr/lib/aout/libdescrypt.so.2.0: Operation not permitted
Move libdialog.so.3.0 from /usr/lib to /usr/lib/aout
Move libdialog.so.3.1 from /usr/lib to /usr/lib/aout
Move libedit.so.2.0 from /usr/lib to /usr/lib/aout
Move libf2c.so.2.0 from /usr/lib to /usr/lib/aout
--
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 Thu Nov 5 12:34:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA26768
for freebsd-current-outgoing; Thu, 5 Nov 1998 12:34:59 -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 MAA26721
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 12:34:43 -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 OAA14134;
Thu, 5 Nov 1998 14:34:03 -0600 (CST)
Message-Id: <199811052034.OAA14134@ns.tar.com>
From: "Richard Seaman, Jr." <lists@tar.com>
To: "Peter Wemm" <peter@netplex.com.au>
Cc: "current@FreeBSD.ORG" <current@FreeBSD.ORG>
Date: Thu, 05 Nov 98 14:34:03 -0600
Reply-To: "Richard Seaman, Jr." <lists@tar.com>
X-Mailer: PMMail 1.92 For OS/2
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="_=_=_=IMA.BOUNDARY.F1YROR138764=_=_=_"
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
--_=_=_=IMA.BOUNDARY.F1YROR138764=_=_=_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
On Thu, 05 Nov 1998 22:28:46 +0800, Peter Wemm wrote:
>Also, while on the subject, something Julian said has got me thinking about
>creating kernel threads on the fly when and if a user thread happens to
>block. This sounds rather interesting.. - async IO is done this way too I
>think. It would require a fair amount of cooperation between the thread
>"engine" and the kernel, perhaps by having an executive thread of sorts
>that handled the kernel interation and thread activation.
I attached a message from Martin Cracauer (and the attachment to that
message) from about 2 1/2 months ago on this subject.
--_=_=_=IMA.BOUNDARY.F1YROR138764=_=_=_
Content-Type: application/octet-stream; name="m"
Content-Transfer-Encoding: base64
UmV0dXJuLVBhdGg6IG93bmVyLWZyZWVic2QtY3VycmVudEBGcmVlQlNELk9SRwpSZXR1cm4tUGF0
aDogPG93bmVyLWZyZWVic2QtY3VycmVudEBGcmVlQlNELk9SRz4KUmVjZWl2ZWQ6IGZyb20gc2Fy
aXAuc29sLm5ldCAobWFpbEBzYXJpcC5zb2wubmV0IFsxNjkuMjA3LjMwLjEyMF0pCglieSBucy50
YXIuY29tICg4LjguOC84LjguNykgd2l0aCBFU01UUCBpZCBIQUEwNDU1MAoJZm9yIDxsaXN0c0B0
YXIuY29tPjsgV2VkLCAyNiBBdWcgMTk5OCAwNzozNjoyMiAtMDUwMCAoQ0RUKQpSZWNlaXZlZDog
ZnJvbSBodWIuZnJlZWJzZC5vcmcgKGh1Yi5GcmVlQlNELk9SRyBbMjA0LjIxNi4yNy4xOF0pCgli
eSBzYXJpcC5zb2wubmV0ICg4LjguOC84LjguOC9TTk5TLTEuMDIpIHdpdGggRVNNVFAgaWQgSEFB
MTAxOTk7CglXZWQsIDI2IEF1ZyAxOTk4IDA3OjMyOjIwIC0wNTAwIChDRFQpClJlY2VpdmVkOiBm
cm9tIGxvY2FsaG9zdCAoZGFlbW9uQGxvY2FsaG9zdCkKICAgICAgICAgIGJ5IGh1Yi5mcmVlYnNk
Lm9yZyAoOC44LjgvOC44LjgpIHdpdGggU01UUCBpZCBGQUExOTQ1NzsKICAgICAgICAgIFdlZCwg
MjYgQXVnIDE5OTggMDU6MDk6NTEgLTA3MDAgKFBEVCkKICAgICAgICAgIChlbnZlbG9wZS1mcm9t
IG93bmVyLWZyZWVic2QtY3VycmVudCkKUmVjZWl2ZWQ6IGJ5IGh1Yi5mcmVlYnNkLm9yZyAoYnVs
a19tYWlsZXIgdjEuNik7IFdlZCwgMjYgQXVnIDE5OTggMDU6MDc6NTQgLTA3MDAKUmVjZWl2ZWQ6
IChmcm9tIG1ham9yZG9tQGxvY2FsaG9zdCkKICAgICAgICAgIGJ5IGh1Yi5mcmVlYnNkLm9yZyAo
OC44LjgvOC44LjgpIGlkIEZBQTE5MTU5CiAgICAgICAgICBmb3IgZnJlZWJzZC1jdXJyZW50LW91
dGdvaW5nOyBXZWQsIDI2IEF1ZyAxOTk4IDA1OjA3OjUzIC0wNzAwIChQRFQpCiAgICAgICAgICAo
ZW52ZWxvcGUtZnJvbSBvd25lci1mcmVlYnNkLWN1cnJlbnRARnJlZUJTRC5PUkcpClJlY2VpdmVk
OiBmcm9tIGdpbGdhbWVzY2guYmlrLWdtYmguZGUgKGdpbGdhbWVzY2guYmlrLWdtYmguZGUgWzE5
NC4yMzMuMjM3LjkxXSkKICAgICAgICAgIGJ5IGh1Yi5mcmVlYnNkLm9yZyAoOC44LjgvOC44Ljgp
IHdpdGggRVNNVFAgaWQgRkFBMTkxNTA7CiAgICAgICAgICBXZWQsIDI2IEF1ZyAxOTk4IDA1OjA3
OjUwIC0wNzAwIChQRFQpCiAgICAgICAgICAoZW52ZWxvcGUtZnJvbSBjcmFjYXVlckBnaWxnYW1l
c2NoLmJpay1nbWJoLmRlKQpSZWNlaXZlZDogKGZyb20gY3JhY2F1ZXJAbG9jYWxob3N0KSBieSBn
aWxnYW1lc2NoLmJpay1nbWJoLmRlICg4LjguOC84LjcuMykgaWQgT0FBMjA5MTM7IFdlZCwgMjYg
CkF1ZyAxOTk4IDE0OjA2OjQzICswMjAwIChNRVQgRFNUKQpNZXNzYWdlLUlEOiA8MTk5ODA4MjYx
NDA2NDIuQTIwNTExQGNvbnMub3JnPgpEYXRlOiBXZWQsIDI2IEF1ZyAxOTk4IDE0OjA2OjQyICsw
MjAwCkZyb206IE1hcnRpbiBDcmFjYXVlciA8Y3JhY2F1ZXJAY29ucy5vcmc+ClRvOiBNaWtlIFNt
aXRoIDxtaWtlQHNtaXRoLm5ldC5hdT4sIE1pY2hhZWwgSGFuY29jayA8bWljaGFlbGhAY2V0LmNv
LmpwPgpDYzogR2FyeSBQYWxtZXIgPGdwYWxtZXJARnJlZUJTRC5PUkc+LCBDaHVjayBSb2JleSA8
Y2h1Y2tyQGdsdWUudW1kLmVkdT4sCiAgICAgICAgZnJlZWJzZC1jdXJyZW50QEZyZWVCU0QuT1JH
ClN1YmplY3Q6IFJlOiBUaHJlYWRzIGFjcm9zcyBwcm9jZXNzb3JzClJlZmVyZW5jZXM6IDxQaW5l
LlNWNC4zLjk1Ljk4MDgyNjAwMDIwNC4xOTE1N0MtMTAwMDAwQHBhcmtwbGFjZS5jZXQuY28uanA+
IAo8MTk5ODA4MjUxMzM4Lk5BQTAyNTMzQGRpbmdvLmNkcm9tLmNvbT4KTWltZS1WZXJzaW9uOiAx
LjAKQ29udGVudC1UeXBlOiBtdWx0aXBhcnQvbWl4ZWQ7IGJvdW5kYXJ5PTJvUzVZYXhXQ2NRalRF
eU8KWC1NYWlsZXI6IE11dHQgMC45My4xaQpJbi1SZXBseS1UbzogPDE5OTgwODI1MTMzOC5OQUEw
MjUzM0BkaW5nby5jZHJvbS5jb20+OyBmcm9tIE1pa2UgU21pdGggb24gVHVlLCBBdWcgMjUsIDE5
OTggYXQgCjAxOjM4OjE4UE0gKzAwMDAKU2VuZGVyOiBvd25lci1mcmVlYnNkLWN1cnJlbnRARnJl
ZUJTRC5PUkcKWC1Mb29wOiBGcmVlQlNELk9SRwpYLVVJREw6IDA1NjZiOTEwMjdiN2Q5MjJiNjFj
ZjYzZjVhY2Y2YTIzCgpJbiA8MTk5ODA4MjUxMzM4Lk5BQTAyNTMzQGRpbmdvLmNkcm9tLmNvbT4s
IE1pa2UgU21pdGggd3JvdGU6IAo+ID4gT24gVHVlLCAyNSBBdWcgMTk5OCwgR2FyeSBQYWxtZXIg
d3JvdGU6Cj4gPiAKPiA+ID4gSGVjaywgU01JIHdyb3RlIGBkb29ycycgZm9yIHRoZSB2ZXJ5IHJl
YXNvbiB0aGF0IElQQyAqYmxvd3MqIGluIGFsbCBjYXNlcywgYW5kIAo+ID4gPiB0aGF0IHRvIHB1
bGwgb2ZmIHRoZSBzcGVlZHVwcyB3aXRoIE5TQ0QgdGhhdCB0aGV5IHdhbnRlZCwgdGhleSBoYWQg
dG8gZ2V0IHRoZSAKPiA+ID4gSVBDIG92ZXJoZWFkIHJlZHVjZWQgYSBsb3QuIEkgdGhpbmsgSSBl
dmVuIGhhdmUgc2xpZGVzIHNvbWV3aGVyZSBjb21wYXJpbmcgCj4gPiA+IHBpcGVzLCBTWVNWIFNI
TSwgZXRjIHRpbWVzIGZvciBtZXNzYWdlIHBhc3NpbmcgaW4gdGVybXMgb2YgdHJhbnNpdCB0aW1l
Lgo+ID4gCj4gPiBPdXIgcGlwZXMgYXJlIHZlcnkgZmFzdC4gIFNZU1YgU0hNJ3MgYmx1bmRlciBp
cyB0aGF0IGl0IHVzZXMgZnVsbCBibG93bgo+ID4gc3lzdGVtIGNhbGxzIGZvciBzeW5jaHJvbml6
YXRpb24uCgpBZWhtLCBhbmQgcGlwZXMgZG9uJ3QgcmVxdWlyZSBmdWxsLWJsb3duIHN5c3RlbSBj
YWxscyB0byBzZW5kL3JlY2VpdmUKbm90aWZpY2F0aW9ucyBhbmQgcmVxdWlyZSBrZXJuZWwgcmVz
aGVkdWxpbmcgYmVmb3JlIGFueXRoaW5nIGhhcHBlbnMKYWZ0ZXIgc2VuZGluZyBhIG1lc3NhZ2U/
CiAKPiBZZXMuICBBbnlvbmUgdGhhdCB0aGlua3MgaW4gdGVybXMgb2YgYSBjb250ZXh0IHN3aXRj
aCBwZXIgdHJhbnNhY3Rpb24gCj4gYmV0d2VlbiBjb3Byb2Nlc3NlcyBpcyBub3QgZGVzaWduaW5n
IHByb3Blcmx5LiAgCgpGb3IgeW91ciBhbXVzZW1lbnQsIEkgYXBwZW5kZWQgYSBtZXNzYWdlIEkg
b25jZSBmb3J3YXJkZWQgdG8gLWhhY2tlcnMsCnJlZ2FyZGluZyBtYXBwaW5nIG9mIHVzZXJsZXZl
bCB0aHJlYWRzIHRvIGtlcm5lbCBzaGVkdWxhYmxlIGVudGl0aWVzLgoKQnV0IGluIGEgd2F5IHRo
YXQgaXMgbGlrZSBzZW5kZmlsZSBhbmQgb3RoZXIgY29tYmluZWQgc3lzdGVtIGNhbGxzOgpEaWQg
YW55b25lIGFjdHVhbGx5IGdhaW4gYW55IGRhdGEgaG93IG11Y2ggc2xvd2VyIGEKb25lLXByb2Nl
c3MtcGVyLXRocmVhZCBtb2RlbCBpcz8gRm9yIGFueSBhcHBsaWNhdGlvbj8KCj4gVXNpbmcgYSBz
aGFyZWQgbW1hcCgpIAo+IHJlZ2lvbiBhbmQgZGF0YXN0cnVjdHVyZXMgdGhhdCBkb24ndCByZXF1
aXJlIGxvY2tpbmcgaXMgYW5vdGhlciAKPiBjb3N0LWVmZmVjdGl2ZSB0ZWNobmlxdWUuCgpJJ20g
YWZyYWlkIEkgaGF2ZSB0byBjb3VudCB0aGlzIGFzICp2ZXJ5KiBjaGVhcCBzaG90IDotKQoKTWFy
dGluCi0tIAolJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl
JSUlJSUlJSUlJSUlJSUlCk1hcnRpbiBDcmFjYXVlciA8Y3JhY2F1ZXJAY29ucy5vcmc+IGh0dHA6
Ly93d3cuY29ucy5vcmcvY3JhY2F1ZXIKQlNEIFVzZXIgR3JvdXAgSGFtYnVyZywgR2VybWFueSAg
ICAgaHR0cDovL3d3dy5ic2RoaC5vcmcvCgo=
--_=_=_=IMA.BOUNDARY.F1YROR138764=_=_=_
Content-Type: application/octet-stream; name="l"
Content-Transfer-Encoding: base64
CgpJIHdyb3RlOgoKPiA+IEkgc3RpbGwgbGlrZSB0aGUgc2ltcGxpdGljaXR5IG9mIGEga2VybmVs
LW9ubHkgdGhyZWFkIHNvbHV0aW9uLiBJZgo+ID4gdGhhdCB3YXkgdHVybnMgb3V0IHRvIGJlIHRv
byBpbmVmZmljaWVudCwgdGhlIERFQyB3YXkgc2VlbXMgdG8gYmUgYQo+ID4gc29sdXRpb24gdGhh
dCBkb2Vzbid0IG5lZWQgYXN5bmMgc3lzdGVtIGNhbGxzIGFuZCBoYXMgbm8gZWZmaWNpZW5jeQo+
ID4gZGlzYWR2YW50YWdlIEkgY2FuIHNlZSAoY29tcGFyZWQgdG8gYSBzeXN5ZW0gd2l0aCBhc3lu
YyBzeXNjYWxscwo+ID4gb25seSkuCj4gPiAKPiA+IEkgaG9wZSB0byBnZXQgZnVydGhlciBkZXRh
aWxzIG9uIHRoZSBERUMgaW1wbGVtZW50YXRpb24uCgpIZXJlJ3Mgd2hhdCBEYXZlIEJ1dGVuaG9m
IDxidXRlbmhvZkB6a28uZGVjLmNvbT4gdG9sZCBtZSBhYm91dCBERUMncwppbnRlcmZhY2UuIERh
dmUgaW1wbGVtZW50cyB0aGUgdXNlcmxldmVsIHBhcnQgb2YgREVDJ3MgdGhyZWFkCmludGVyZmFj
ZS4gVGhpcyBhbnN3ZXIgaXMgYSBiaXQgb3V0IG9mIGNvbnRleHQsIGlmIHlvdSBuZWVkIHRoZQpw
cmV2aW91cyBkaXNjdXNzaW9uLCBwbGVhc2UgbGV0IG1lIGtub3cuCgpNeSBvcmlnaW5hbCBxdWVz
dGlvbiB3YXMgaG93IGJsb2NraW5nIHN5c2NhbGxzIGFyZSB0cmVhdGVkLiBJbiBEaWdpdGFsClVu
aXgsIHRoZSBrZXJuZWwgcmVwb3J0cyBhIGJsb2NraW5nIHN5c2NhbGwgaW4gb25lIHRocmVhZCBi
YWNrIHRvIHRoZQp1c2VybGV2ZWwgbGlicmFyeSwgd2hpY2ggcmVzaGVkdWxlcyBhbm90aGVyIHRo
cmVhZCBvbiB0aGF0ICJrZXJuZWwiCnRocmVhZC4gSSBhc2tlZCBmb3IgZnVydGhlciBkZXRhaWxz
IGhvdyBhIHVzZXJsZXZlbCBsaWJyYXJ5IGNvdWxkIGdldApyaWQgb2YgYW4gYWxyZWFkeSBibG9j
a2luZyBzeXNjYWxsLCBhbmQgaGVyZSdzIHdoYXQgSSBoZWFyZWQ6Cgo+IH5NZXNzYWdlLUlkOiA8
MzJBNTc5N0MuNjIzMUB6a28uZGVjLmNvbT4KPiB+RGF0ZTogV2VkLCAwNCBEZWMgMTk5NiAwODox
NTo0MCAtMDUwMAo+IH5Gcm9tOiBEYXZlIEJ1dGVuaG9mIDxidXRlbmhvZkB6a28uZGVjLmNvbT4K
PiB+T3JnYW5pemF0aW9uOiBEaWdpdGFsIEVxdWlwbWVudCBDb3Jwb3JhdGlvbgo+IH5UbzogY3Jh
Y2F1ZXJAd2F2ZWhoLmhhbnNlLmRlCj4gfkNjOiAiQnV0ZW5ob2YsIERhdmUiIDxidXRlbmhvZkB6
a28uZGVjLmNvbT4KPiB+U3ViamVjdDogUmU6IEJsb2NraW5nIHN5c2NhbGwgaGFuZGxpbmcgaW4g
b25lLXRvLW1hbnkgdGhyZWFkIGltcGxlbWVudGF0aW9ucwo+IAo+IFsuLi5dCj4gCj4gW1RoaXMg
d2FzIG15LCBNYXJ0aW5zLCBxdWVzdGlvbl0KPiA+IEJ1dCBob3cgZXhhY3RseSBpcyByZXNoZWR1
bGluZyBvbiB5b3VyIEtFQ3MgZG9uZT8gSWYgYSBLRUNzIGlzIHdhaXRpbmcKPiA+IGluIGEgYmxv
Y2tpbmcgc3lzY2FsbCwgaG93IGNhbiB0aGUgdXNlcmxldmVsIHNoZWR1bGVyIHJlYXNzaWduIGl0
PyBIb3cKPiA+IGNhbiB0aGUgdXNlcmxldmVsIGxpYnJhcnkgZnJlZSBpdCBmcm9tIHRoZSBzeXNj
YWxsPyAKPiA+IAo+ID4gQW5kIHdoYXQgaGFwcGVucyB0byB0aGUgc3lzY2FsbD8gSXMgaXQgdHJh
bnNsYXRlZCBpbnRvIGEgbm9uLWJsb2NraW5nCj4gPiB2ZXJzaW9uIGFuZCB0aGUga2VybmVsIGlu
Zm9ybXMgdGhlIHVzZXJsZXZlbCBzaGVkdWxlciB3aGVuIGl0IGFycml2ZXM/Cj4gCj4gSSB3YXMg
dHJ5aW5nIHRvIGRlc2NyaWJlIHdoYXQgaGFwcGVucyBmcm9tIFlPVVIgcGVyc3BlY3RpdmUsIG1v
cmUgdGhhbgo+IHdoYXQgYWN0dWFsbHkgaGFwcGVucyBpbiB0aGUgdGhyZWFkIGxpYnJhcnkgJiBr
ZXJuZWwuIFRoZSBpbnRlcm5hbHMgYXJlLAo+IGFzIGFsd2F5cywgYSBsaXR0bGUgbW9yZSBjb21w
bGljYXRlZC4KPiAKPiBUaGUgdGhyZWFkIGxpYnJhcnkgbWFpbnRhaW5zIGEgY29uc3RhbnQgcG9v
bCBvZiAodXAgdG8pIDxuPiBLRUNzLCB3aGVyZQo+IDxuPiBpcyBub3JtYWxseSBzZXQgYnkgdGhl
IG51bWJlciBvZiBwaHlzaWNhbCBwcm9jZXNzb3JzIGluIHRoZSBzeXN0ZW0uCj4gKEl0IG1heSBi
ZSBzbWFsbGVyLCBpZiB5b3VyIHByb2Nlc3MgaXMgbG9ja2VkIGludG8gYSBwcm9jZXNzb3Igc2V0
LikKPiBUaGVzZSBhcmUgdGhlICJ2aXJ0dWFsIHByb2Nlc3NvcnMiIChWUHMpLiBUaGUgdGhyZWFk
IGxpYnJhcnkgc2NoZWR1bGVzCj4gdXNlciB0aHJlYWRzIG9uIHRoZSBwb29sIG9mIFZQcywgdHJ5
aW5nIHRvIGtlZXAgYWxsIDxuPiBvZiB0aGVtIGJ1c3kuIElmCj4geW91IGRvbid0IGhhdmUgZW5v
dWdoIHVzZXIgdGhyZWFkcyB0byBrZWVwIHRoYXQgbWFueSBWUHMgYnVzeSwgdGhleSBtYXkKPiBu
b3QgYWxsIGdldCBzdGFydGVkLCBvciBWUHMgYWxyZWFkeSBydW5uaW5nIG1heSBnbyBpbnRvIHRo
ZSAibnVsbAo+IHRocmVhZCIgbG9vcCBhbmQgaWRsZSAtLSB3aGljaCByZXR1cm5zIHRoZSBLRUMg
dG8gdGhlIGtlcm5lbCdzIHBvb2wgZm9yCj4gcmV1c2UuIFdlJ2xsIGdldCBpdCBiYWNrIGlmIHdl
IG5lZWQgaXQgbGF0ZXIuCj4gCj4gV2hlbiBhIHRocmVhZCBibG9ja3MgaW4gdGhlIGtlcm5lbCwg
dGhlIEtFQyBzdGF5cyBpbiB0aGUga2VybmVsLCBidXQgaXQKPiBnaXZlcyB1cyBhbiB1cGNhbGwg
aW4gYSAqbmV3KiAob3IgcmVjeWNsZWQpIEtFQyB0byByZXBsYWNlIHRoZSBWUC4gV2hlbgo+IHRo
ZSBibG9ja2luZyBvcGVyYXRpb24gZmluaXNoZXMsIHRoZSBrZXJuZWwgZ2l2ZXMgdXMgYSBjb21w
bGV0aW9uIHVwY2FsbAo+IGluIHRoZSBvcmlnaW5hbCBLRUMuIEl0J3Mgbm8gbG9uZ2VyIGEgVlAs
IHNvIHdlIGp1c3Qgc2F2ZSB0aGUgY29udGV4dAo+IGFuZCBkaXNtaXNzIGl0Lgo+IAo+IFRoZSBr
ZXkgaXMgdGhlIGRpc3RpbmN0aW9uIGJldHdlZW4gIktFQyIgYW5kICJWUCIuIFRoZXJlIG1heSBi
ZSAxMDAgS0VDcwo+IGF0dGFjaGVkIHRvIGEgcHJvY2VzcywgYnV0LCBvbiBhIHR5cGljYWwgcXVh
ZC1DUFUgc3lzdGVtLCBvbmx5ICh1cCB0bykgNAo+IG9mIHRoZW0gYXQgYW55IHRpbWUgYXJlICJW
UHMiLiBUaGUgcmVzdCBhcmUganVzdCBob2xkaW5nIGtlcm5lbCBjb250ZXh0Cj4gYWNyb3NzIHNv
bWUgYmxvY2tpbmcgb3BlcmF0aW9uLiBXaGVyZWFzLCBpbiBhIHN0cmljdCBrZXJuZWwtbW9kZQo+
IGltcGxlbWVudGF0aW9uLCBlYWNoIHVzZXIgdGhyZWFkIGlzIGEgS0VDLCB3ZSBoYXZlIGEgS0VD
IG9ubHkgZm9yIGVhY2gKPiBydW5uaW5nIHRocmVhZCBhbmQgZWFjaCB0aHJlYWQgYmxvY2tlZCBp
biB0aGUga2VybmVsLiBUaGUgbnVtYmVyIG9mIEtFQ3MKPiB3aWxsIGZsdWN0dWF0ZSAtLSBhbmQs
IGlmIHlvdSBoaXQgeW91ciBxdW90YSBmb3IgS0VDcyAoTWFjaCB0aHJlYWRzKSwKPiBhbnkgYWRk
aXRpb25hbCBrZXJuZWwgYmxvY2tpbmcgb3BlcmF0aW9ucyB3aWxsIHN0YXJ0IHRvIGxvd2VyCj4g
Y29uY3VycmVuY3kuIFRoZSBtb3N0IGNvbW1vbiBibG9ja2luZyBvcGVyYXRpb25zLCBtdXRleGVz
ICYgY29uZGl0aW9uCj4gdmFyaWFibGVzIChhbmQgc29tZSBvdGhlcnMpLCBob3dldmVyLCBhcmUg
Y29tcGxldGVseSBpbiB1c2VyIG1vZGUuCj4gCj4gV2UncmUgZ29pbmcgdG8gY29udGludWUgc3Ry
ZWFtbGluaW5nIHRoZSBwcm9jZXNzIGFzIHdlIGdvIChsaWtlIG1vdmluZwo+IHNvbWUga2VybmVs
IGJsb2NraW5nIHN0YXRlcyBvdXQgaW50byB1c2VyIG1vZGUsIGFuZCByZWR1Y2luZyB0aGUgY29u
dGV4dAo+IHRoYXQgdGhlIGtlcm5lbCBuZWVkcyB0byBrZWVwIGJlbG93IGEgZnVsbCBLRUMpLCBi
dXQsIGluIGdlbmVyYWwsIGl0Cj4gd29ya3MgdmVyeSB3ZWxsLiBUaGUga2VybmVsIGRldmVsb3Bl
ciBhbmQgSSAoSSB3b3JrIG1vc3RseSBpbiB0aGUKPiBsaWJyYXJ5KSBoYXZlIGtpY2tlZCBhcm91
bmQgdGhlIGlkZWEgb2YgZG9pbmcgYSBwYXBlciBvbiB0aGUgZGVzaWduLgo+IE1vc3RseSwgSSd2
ZSBiZWVuIHRvbyBidXN5IHdpdGggYSBib29rIGZvciBhIHJpZGljdWxvdXNseSBsb25nIHRpbWUs
IGFuZAo+IHRoZSBkZXZlbG9wbWVudCByZXF1aXJlbWVudHMgbmV2ZXIgc3RvcC4gTWF5YmUgc29t
ZSBkYXkuIFBvc3NpYmx5IG9uY2UKPiB3ZSd2ZSBnb25lIHRocm91Z2ggYSBmdWxsIHJlbGVhc2Ug
Y3ljbGUgYW5kIGhhdmUgdGhlIGFyY2hpdGVjdHVyZQo+IHN0YWJpbGl6ZWQgYmV0dGVyLgo+IAo+
IC8tLS1bIERhdmUgQnV0ZW5ob2YgXS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tWyBidXRlbmhvZkB6
a28uZGVjLmNvbSBdLS0tXAo+IHwgRGlnaXRhbCBFcXVpcG1lbnQgQ29ycG9yYXRpb24gICAgICAg
ICAgIDExMCBTcGl0IEJyb29rIFJkIFpLTzItMy9RMTggfAo+IHwgNjAzLjg4MS4yMjE4LCBGQVgg
NjAzLjg4MS4wMTIwICAgICAgICAgICAgICAgICAgTmFzaHVhIE5IIDAzMDYyLTI2OTggfAo+IFwt
LS0tLS0tLS0tLS0tLS0tLVsgQmV0dGVyIExpdmluZyBUaHJvdWdoIENvbmN1cnJlbmN5IF0tLS0t
LS0tLS0tLS0tLS0tLwo+IAo+IAoKCg==
--_=_=_=IMA.BOUNDARY.F1YROR138764=_=_=_--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 12:35:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA26953
for freebsd-current-outgoing; Thu, 5 Nov 1998 12:35:53 -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 MAA26941
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 12:35:49 -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 VAA21682;
Thu, 5 Nov 1998 21:41:12 +0100 (CET)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Thu, 5 Nov 1998 21:41:11 +0100 (CET)
From: Andrzej Bialecki <abial@nask.pl>
X-Sender: abial@korin.warman.org.pl
To: Sergei Laskavy <laskavy@Gambit.Msk.SU>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: BootForth strange behaviour
In-Reply-To: <19981105225531.A16317@gambit.msk.su>
Message-ID: <Pine.BSF.4.02A.9811052140340.19880-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 Thu, 5 Nov 1998, Sergei Laskavy wrote:
> On Thu, Nov 05, 1998 at 08:42:34PM +0100, Andrzej Bialecki wrote:
>
> > One of last commits to /sys/boot (I'm not sure which) caused that Forth
> > interpreter accepts only one-liners, i.e.:
> >
> > > : test ." hello world" cr ;
> >
> > works, but
> >
> > > :test
> > > ." hello world"
> >
> > barfs that ." is a compile-only word...
>
> You want to use
> : test
> ." hello world"
Yeah, I know - this was typo.. :-( Anyway, it doesn't work.
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 Thu Nov 5 13:10:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA02331
for freebsd-current-outgoing; Thu, 5 Nov 1998 13:10:31 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m2-3-dbn.dial-up.net [196.34.155.67])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02308
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 13:10:20 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA13236; Thu, 5 Nov 1998 23:07:57 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199811052107.XAA13236@ceia.nordier.com>
Subject: Re: USERCONFIG_BOOT, heads up!
In-Reply-To: <Pine.BSF.4.02A.9811051137380.311-100000@smarter.than.nu> from "Brian W. Buchanan" at "Nov 5, 98 11:38:58 am"
To: brian@CSUA.Berkeley.EDU (Brian W. Buchanan)
Date: Thu, 5 Nov 1998 23:07:54 +0200 (SAT)
Cc: mike@smith.net.au, 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
Brian W. Buchanan wrote:
> On Thu, 5 Nov 1998, Mike Smith wrote:
>
> > disklabel -B -b /boot/boot1 -s /boot/boot2 wd0s1
>
> Ack. I did exactly that, then rebooted. At the point where the boot
> prompt would, normally appear, the system simply rebooted itself. I had
> to dig up an install floppy and restore the old bootloader.
Your BIOS may have a problem doing enhanced rather than conventional
disk access: a fair number seem to. Microsoft apparently runs a series
of tests before enabling enhanced access, and we will probably be
forced to do something similar.
I've just committed a change disabling enhanced access by default, and
this may make a difference.
--
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 5 13:29:17 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA04606
for freebsd-current-outgoing; Thu, 5 Nov 1998 13:29:17 -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 NAA04599
for <freebsd-current@freebsd.org>; Thu, 5 Nov 1998 13:29:11 -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.1a/8.9.1) with ESMTP id WAA01512
for <freebsd-current@freebsd.org>; Thu, 5 Nov 1998 22:18:13 +0100 (CET)
(envelope-from leifn@swimsuit.internet.dk)
Date: Thu, 5 Nov 1998 22:18:13 +0100 (CET)
From: Leif Neland <leifn@swimsuit.internet.dk>
To: freebsd-current@FreeBSD.ORG
Subject: sendmail.8.9.1a patch
Message-ID: <Pine.BSF.4.05.9811052216001.29212-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
Could somebody please apply the sendmail-8.9.1a patch to
/usr/src/contrib/sendmail?
I just applied the patch, but cvsup promptly unpatched the patch :-(
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 13:57:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA08137
for freebsd-current-outgoing; Thu, 5 Nov 1998 13:57:01 -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 NAA08131
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 13:56:58 -0800 (PST)
(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
by cimlogic.com.au (8.9.1/8.9.1) id JAA27533;
Fri, 6 Nov 1998 09:05:45 +1100 (EST)
(envelope-from jb)
From: John Birrell <jb@cimlogic.com.au>
Message-Id: <199811052205.JAA27533@cimlogic.com.au>
Subject: Re: make aout-to-elf-install, mv: rename /usr/lib/libc.so.3.1 to /usr/lib/aout/libc.so.3.1: Operation not permitted
In-Reply-To: <19981105204609.A5684@klemm.gtn.com> from Andreas Klemm at "Nov 5, 98 08:46:09 pm"
To: andreas@klemm.gtn.com (Andreas Klemm)
Date: Fri, 6 Nov 1998 09:05:44 +1100 (EST)
Cc: 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
Andreas Klemm wrote:
> Hi !
>
> During make aout-to-elf-install:
>
> Do we have to add a
> chflags -noschg .....
> ???????
Looks like it.
--
John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 14:10:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA09261
for freebsd-current-outgoing; Thu, 5 Nov 1998 14:10: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 OAA09174
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 14:10: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 RAA06209;
Thu, 5 Nov 1998 17:08:28 -0500 (EST)
Date: Thu, 5 Nov 1998 17:08:28 -0500 (EST)
From: jack <jack@germanium.xtalwind.net>
To: Leif Neland <leifn@swimsuit.internet.dk>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: sendmail.8.9.1a patch
In-Reply-To: <Pine.BSF.4.05.9811052216001.29212-100000@gina.swimsuit.internet.dk>
Message-ID: <Pine.BSF.4.05.9811051703370.6164-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 Thu, 5 Nov 1998, Leif Neland wrote:
> Could somebody please apply the sendmail-8.9.1a patch to
> /usr/src/contrib/sendmail?
Let's hope not, at least not as the default. From
sendmail.8.9.1a.patch.README
Introduction
[snip]
It is important to note that sendmail itself is not
vulnerable to these attacks.
[snip]
Tradeoffs
As this patch requires scanning the body of the message for
MIME indicators, there will be a performance penalty to run
this code.
--------------------------------------------------------------------------
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 Thu Nov 5 14:22:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA10761
for freebsd-current-outgoing; Thu, 5 Nov 1998 14:22:49 -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 OAA10751
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 14:22:47 -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 OAA00407;
Thu, 5 Nov 1998 14:21:35 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811052221.OAA00407@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: USERCONFIG_BOOT, heads up!
In-reply-to: Your message of "Thu, 05 Nov 1998 11:38:58 PST."
<Pine.BSF.4.02A.9811051137380.311-100000@smarter.than.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Nov 1998 14:21:35 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On Thu, 5 Nov 1998, Mike Smith wrote:
>
> > disklabel -B -b /boot/boot1 -s /boot/boot2 wd0s1
>
> Ack. I did exactly that, then rebooted. At the point where the boot
> prompt would, normally appear, the system simply rebooted itself. I had
> to dig up an install floppy and restore the old bootloader.
Very ack; this isn't supposed to happen like this.
Can you give us some more system details? How recently did you rebuild
the world?
--
\\ 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 5 15:08:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA15868
for freebsd-current-outgoing; Thu, 5 Nov 1998 15:08: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 PAA15797
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 15:08: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 SAA09547;
Thu, 5 Nov 1998 18:07:17 -0500 (EST)
Date: Thu, 5 Nov 1998 18:07:17 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Peter Wemm <peter@netplex.com.au>
cc: current@FreeBSD.ORG
Subject: Re: RFSIGSHARE: forgot patch ;)
In-Reply-To: <199811050758.PAA05054@spinner.netplex.com.au>
Message-ID: <Pine.BSF.4.05.9811051806430.9519-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
*Really needs to get the BSD book* In what space do UPAGES lie?
-Brian Feldman
On Thu, 5 Nov 1998, Peter Wemm wrote:
> Brian Feldman wrote:
> > Hrmm.... I don't see why this doesn't work:
> > + if (args->flags & CLONE_SIGHAND)
> > + p2->p_sigacts = p->p_sigacts;
> > don't tell me it's pointing into user-space, or some other neglected part
> > of proc? I'll investigate I suppose. This is certainly helping me
> > familiarize myself with the kernel, even if these specific patches cause a
> > trap eventually (probably all the mallocing/freeing). I _really_ need to
> > buy a copy of the BSD book... quick question: zalloc and malloc should
> > each be used in what situations?
>
> p_sigacts points into the UPAGES, beyond the pcb.. Check the p_addr
> pointers for examples.
>
> The reason you can't do this is because the old proc could go away at any
> time, the parent process's UPAGES could get swapped out, etc. To do this,
> you need to stop the parent from exiting until all children are gone (or
> keep it's state around), and stop it being swapped.
>
> > Cheers,
> > Brian Feldman
> > "gaining lots of experience"
> >
> > On Thu, 5 Nov 1998, Peter Wemm wrote:
> >
> > > Brian Feldman wrote:
> > > [..]
> > > > --- ./kern/kern_fork.c.orig Wed Nov 4 20:33:11 1998
> > > > +++ ./kern/kern_fork.c Wed Nov 4 20:44:29 1998
> > > > @@ -151,6 +151,10 @@
> > > > p1->p_pid);
> > > > return (EOPNOTSUPP);
> > > > }
> > > > + if (flags & RFSIGSHARE) {
> > > > + printf("shared signal space attemped: pid: %d\n",
> > > > p1->p_pid);
> > > > + return (EOPNOTSUPP);
> > > > + }
> > > > #endif
> > > >
> > > > /*
> > >
> > > RFSIGSHARE should work fine on SMP.
> > >
> > > > @@ -320,6 +324,16 @@
> > > > bcopy(p1->p_cred, p2->p_cred, sizeof(*p2->p_cred));
> > > > p2->p_cred->p_refcnt = 1;
> > > > crhold(p1->p_ucred);
> > > > +
> > > > + if (flags & RFSIGSHARE) {
> > > > + p2->p_sig->p_refcnt++;
> > > > + } else {
> > > > + p2->p_sig = malloc(sizeof(struct procsig), M_TEMP,
> > > > M_WAITOK);
> > > > + p2->p_sig->p_refcnt = 1;
> > > > + p2->p_sigmask = p1->p_sigmask;
> > > > + p2->p_sigignore = p1->p_sigignore;
> > > > + p2->p_sigcatch = p1->p_sigcatch;
> > > > + }
> > > >
> > > > /* bump references to the text vnode (for procfs) */
> > > > p2->p_textvp = p1->p_textvp;
> > >
> > > Umm, you are sharing the signal masks, not the signal handler vectors
> > > themselves. Think p_sigacts.. Those are stored after the PCB and are
> > > paged out.
> > >
> > > Assuming you take a shot at sharing them, try this: Keep p_sigacts there
> > > by default. If a process attempts to share the signals during a fork,
> > > then malloc a copy and attach it to both the child and parent. When the
> > > reference count drops to 1, the remaining process should probably have
> > > it's vectors copied to the upages again and the malloc space freed. But
> > > good stuff so far! :-)
> > >
> > > Cheers,
> > > -Peter
> > >
> > >
> > >
> > >
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-current" in the body of the message
> > >
> >
>
> Cheers,
> -Peter
> --
> Peter Wemm <peter@netplex.com.au> Netplex Consulting
> "No coffee, No workee!" :-)
>
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 15:11:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA16359
for freebsd-current-outgoing; Thu, 5 Nov 1998 15:11:22 -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 PAA16351
for <current@freebsd.org>; Thu, 5 Nov 1998 15:11:20 -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 PAA26496
for <current@freebsd.org>; Thu, 5 Nov 1998 15:11:45 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: current@FreeBSD.ORG
Subject: Latest alpha-current breakage
Date: Thu, 05 Nov 1998 15:11:45 -0800
Message-ID: <26492.910307505@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
cc -I/usr/src/sys/modules/vinum/../../../lkm/vinum -O -g -I/usr/include/machine
-DDEBUG -Wall -Wno-unused -Wno-parentheses -DKERNEL -Wreturn-type -Wcomment -Wr
edundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-protot
ypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -an
si -DKLD_MODULE -nostdinc -I- -I/usr/src/sys/modules/vinum/../../../lkm/vinum -I
/usr/include/machine -I/usr/obj/elf/usr/src/sys/modules/vinum -I/usr/obj/elf/usr
/src/sys/modules/vinum/@ -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/sys/
modules/vinum/../../../lkm/vinum/memory.c
In file included from /usr/src/sys/modules/vinum/../../../lkm/vinum/memory.c:41:
/usr/src/sys/modules/vinum/../../../lkm/vinum/vinumhdr.h:87: machine/cputypes.h:
No such file or directory
*** Error code 1
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 15:15:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA17101
for freebsd-current-outgoing; Thu, 5 Nov 1998 15:15:36 -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 PAA17091
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 15:15:34 -0800 (PST)
(envelope-from peter.jeremy@auss2.alcatel.com.au)
Received: by border.alcanet.com.au id <40365>; Fri, 6 Nov 1998 10:14:47 +1100
Date: Fri, 6 Nov 1998 10:14:51 +1100
From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
To: current@FreeBSD.ORG
Message-Id: <98Nov6.101447est.40365@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Julian Elischer <julian@whistle.com> writes:
> easier to simply have a single pointer in a known address
> that gets rewritten by the kernel on scheduling.. probably actually an
> array of them, (one per cpu) with a 'getcpunumber()' to allow
> the thread to work out which it should use.
If I remember correctly, Sun have a per-CPU address space in Solaris
kernel space (or maybe it was SunOS). I can't remember the exact size
or address, but it went something like:
0xffe0000 - current CPU always mapped here
0xfffN000 - cpu N mapped here for all CPUs.
This allows the kernel to have per-CPU data structures that can be
readily accessed either for the CPU the thread is on, or for any
other CPU. The CPU number could be a constant within the per-CPU
space.
A similar approach is possible for user space, but the cost of updating
the PTEs may make it unacceptably expensive (as someone else mentioned).
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 Thu Nov 5 15:21:17 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA18085
for freebsd-current-outgoing; Thu, 5 Nov 1998 15:21:17 -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 PAA18072
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 15:21: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 SAA09741;
Thu, 5 Nov 1998 18:20:49 -0500 (EST)
Date: Thu, 5 Nov 1998 18:20:49 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>
cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: USERCONFIG_BOOT, heads up!
In-Reply-To: <Pine.BSF.4.02A.9811051137380.311-100000@smarter.than.nu>
Message-ID: <Pine.BSF.4.05.9811051820370.9519-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
Exactly the same here.
Cheers,
Brian Feldman
On Thu, 5 Nov 1998, Brian W. Buchanan wrote:
> On Thu, 5 Nov 1998, Mike Smith wrote:
>
> > disklabel -B -b /boot/boot1 -s /boot/boot2 wd0s1
>
> Ack. I did exactly that, then rebooted. At the point where the boot
> prompt would, normally appear, the system simply rebooted itself. I had
> to dig up an install floppy and restore the old bootloader.
>
> --
> 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
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 15:21:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA18121
for freebsd-current-outgoing; Thu, 5 Nov 1998 15:21:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18116
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 15:21:24 -0800 (PST)
(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA25470
for freebsd-current@FreeBSD.ORG; Fri, 6 Nov 1998 00:21:12 +0100 (CET)
(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (VMailer, from userid 101)
id D5B1D155C; Thu, 5 Nov 1998 23:42:53 +0100 (CET)
Date: Thu, 5 Nov 1998 23:42:53 +0100
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: "FreeBSD Current Users' list" <freebsd-current@FreeBSD.ORG>
Subject: Re: make world breakage
Message-ID: <19981105234253.A15131@keltia.freenix.fr>
Mail-Followup-To: FreeBSD Current Users' list <freebsd-current@FreeBSD.ORG>
References: <19981105164700.C359@caerdonn.eurocontrol.fr> <199811051842.KAA03840@dingo.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.4i
In-Reply-To: <199811051842.KAA03840@dingo.cdrom.com>; from Mike Smith on Thu, Nov 05, 1998 at 10:42:52AM -0800
X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4772 AMD-K6 MMX @ 200 MHz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
According to Mike Smith:
> Funny; it works elsewhere. You don't have perl in /usr/bin?
Isn't "make world" supposed to be kinda self-sufficient ? (all right, it is
within "/sys/boot"). I'll check tomorrow on the machine. Generally
"/usr/bin/perl" is either the standard Perl5 or a link to my own 5.005_02
like on my home machine :
242 [23:34] roberto@keltia:zsh-3.1.4/Misc> ll /usr/bin/perl
lrwxr-xr-x 1 root staff 11 Sep 11 23:15 /usr/bin/perl@ -> perl5.00502
lrwxr-xr-x 1 root staff 26 Sep 11 23:15 /usr/bin/perl5.00502@ -> /opt/perl5/bin/perl5.00502
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-BETA #4: Thu Oct 15 01:36:57 CEST 1998
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 15:21:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA18163
for freebsd-current-outgoing; Thu, 5 Nov 1998 15:21:44 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18131
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 15:21:30 -0800 (PST)
(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA25471
for freebsd-current@FreeBSD.ORG; Fri, 6 Nov 1998 00:21:18 +0100 (CET)
(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (VMailer, from userid 101)
id EFA22155C; Thu, 5 Nov 1998 23:44:56 +0100 (CET)
Date: Thu, 5 Nov 1998 23:44:56 +0100
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: freebsd-current@FreeBSD.ORG
Subject: Re: sendmail.8.9.1a patch
Message-ID: <19981105234456.B15131@keltia.freenix.fr>
Mail-Followup-To: freebsd-current@FreeBSD.ORG
References: <Pine.BSF.4.05.9811052216001.29212-100000@gina.swimsuit.internet.dk> <Pine.BSF.4.05.9811051703370.6164-100000@germanium.xtalwind.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.4i
In-Reply-To: <Pine.BSF.4.05.9811051703370.6164-100000@germanium.xtalwind.net>; from jack on Thu, Nov 05, 1998 at 05:08:28PM -0500
X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4772 AMD-K6 MMX @ 200 MHz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
According to jack:
> Let's hope not, at least not as the default. From
> sendmail.8.9.1a.patch.README
And if you run 8.9.1a, you _need_ to install another patch that fix the
multiple Content-Transfer-Encoding:" bug introduced by the "a" patch...
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-BETA #4: Thu Oct 15 01:36:57 CEST 1998
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 15:22:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA18339
for freebsd-current-outgoing; Thu, 5 Nov 1998 15:22:42 -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 PAA18332
for <current@freebsd.org>; Thu, 5 Nov 1998 15:22:40 -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 PAA00713
for <current@freebsd.org>; Thu, 5 Nov 1998 15:22:01 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811052322.PAA00713@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: current@FreeBSD.ORG
Subject: Cyrix M2 (6x86MX) tester required
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Nov 1998 15:22:01 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Simple call; I have a code change that I need to test on a Cyrix M2 -
if you have one and are able to build a kernel and try booting it, I'd
be very pleased to hear from you.
--
\\ 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 5 15:33:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA19545
for freebsd-current-outgoing; Thu, 5 Nov 1998 15:33: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 PAA19539
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 15:33:09 -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 PAA00784;
Thu, 5 Nov 1998 15:30:59 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811052330.PAA00784@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Brian Feldman <green@unixhelp.org>
cc: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>,
Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG
Subject: Re: USERCONFIG_BOOT, heads up!
In-reply-to: Your message of "Thu, 05 Nov 1998 18:20:49 EST."
<Pine.BSF.4.05.9811051820370.9519-100000@janus.syracuse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Nov 1998 15:30:59 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Exactly the same here.
Ok. Fooey on extended BIOS disk I/O support. Robert has just disabled
it; you might want to try again.
> Cheers,
> Brian Feldman
>
> On Thu, 5 Nov 1998, Brian W. Buchanan wrote:
>
> > On Thu, 5 Nov 1998, Mike Smith wrote:
> >
> > > disklabel -B -b /boot/boot1 -s /boot/boot2 wd0s1
> >
> > Ack. I did exactly that, then rebooted. At the point where the boot
> > prompt would, normally appear, the system simply rebooted itself. I had
> > to dig up an install floppy and restore the old bootloader.
> >
> > --
> > 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
> >
>
>
> 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 Thu Nov 5 15:33:58 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA19599
for freebsd-current-outgoing; Thu, 5 Nov 1998 15:33:58 -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 PAA19594
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 15:33:56 -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 PAA00800;
Thu, 5 Nov 1998 15:32:41 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811052332.PAA00800@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Ollivier Robert <roberto@keltia.freenix.fr>
cc: "FreeBSD Current Users' list" <freebsd-current@FreeBSD.ORG>
Subject: Re: make world breakage
In-reply-to: Your message of "Thu, 05 Nov 1998 23:42:53 +0100."
<19981105234253.A15131@keltia.freenix.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Nov 1998 15:32:41 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> According to Mike Smith:
> > Funny; it works elsewhere. You don't have perl in /usr/bin?
>
> Isn't "make world" supposed to be kinda self-sufficient ? (all right, it is
> within "/sys/boot"). I'll check tomorrow on the machine. Generally
> "/usr/bin/perl" is either the standard Perl5 or a link to my own 5.005_02
> like on my home machine :
It probably should be. I've been seriously thinking about various
options here; I don't think that the current approach (take group of
files, feed through perl script to produce C file, compile C file,
parse string in C file into runtime bytecode) is acceptably efficient.
There are many alternatives and we need to look at more of them again.
--
\\ 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 5 15:47:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA21051
for freebsd-current-outgoing; Thu, 5 Nov 1998 15:47:21 -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 PAA21029
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 15:47:13 -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.1a/8.9.1) with ESMTP id AAA06705;
Fri, 6 Nov 1998 00:46:43 +0100 (CET)
(envelope-from leifn@swimsuit.internet.dk)
Date: Fri, 6 Nov 1998 00:46:42 +0100 (CET)
From: Leif Neland <leifn@swimsuit.internet.dk>
To: jack <jack@germanium.xtalwind.net>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: sendmail.8.9.1a patch
In-Reply-To: <Pine.BSF.4.05.9811051703370.6164-100000@germanium.xtalwind.net>
Message-ID: <Pine.BSF.4.05.9811060043160.6421-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
On Thu, 5 Nov 1998, jack wrote:
> On Thu, 5 Nov 1998, Leif Neland wrote:
>
> > Could somebody please apply the sendmail-8.9.1a patch to
> > /usr/src/contrib/sendmail?
>
> Let's hope not, at least not as the default. From
> sendmail.8.9.1a.patch.README
>
> Introduction
>
> [snip]
> It is important to note that sendmail itself is not
> vulnerable to these attacks.
> [snip]
>
> Tradeoffs
>
> As this patch requires scanning the body of the message for
> MIME indicators, there will be a performance penalty to run
> this code.
>
But it doesn't hurt to compile it in (it will probably be in 8.9.2
anyway). If you dont put the
LOCAL_CONFIG
O MaxMimeHeaderLength=256/128
in sendmail.mc, it will not be used, anf performance shouldn't be hurt.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 15:52:25 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA21730
for freebsd-current-outgoing; Thu, 5 Nov 1998 15:52:25 -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 PAA21724
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 15:52:22 -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.1a/8.9.1) with ESMTP id AAA06740;
Fri, 6 Nov 1998 00:51:57 +0100 (CET)
(envelope-from leifn@swimsuit.internet.dk)
Date: Fri, 6 Nov 1998 00:51:56 +0100 (CET)
From: Leif Neland <leifn@swimsuit.internet.dk>
To: Ollivier Robert <roberto@keltia.freenix.fr>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: sendmail.8.9.1a patch
In-Reply-To: <19981105234456.B15131@keltia.freenix.fr>
Message-ID: <Pine.BSF.4.05.9811060048570.6421-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
On Thu, 5 Nov 1998, Ollivier Robert wrote:
> According to jack:
> > Let's hope not, at least not as the default. From
> > sendmail.8.9.1a.patch.README
>
> And if you run 8.9.1a, you _need_ to install another patch that fix the
> multiple Content-Transfer-Encoding:" bug introduced by the "a" patch...
> --
Which patch? There isn't any at ftp.sendmail.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 5 16:19:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA25498
for freebsd-current-outgoing; Thu, 5 Nov 1998 16:19:55 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA25489
for <current@freebsd.org>; Thu, 5 Nov 1998 16:19:46 -0800 (PST)
(envelope-from wpaul@skynet.ctr.columbia.edu)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id TAA14156 for current@freebsd.org; Thu, 5 Nov 1998 19:24:55 -0500
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199811060024.TAA14156@skynet.ctr.columbia.edu>
Subject: Grrr... calcru: negative time blah blah blah
To: current@FreeBSD.ORG
Date: Thu, 5 Nov 1998 19:24:54 -0500 (EST)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Recently, the EE department got a bunch of new Dell machines with
450Mhz PII CPUs. This one particular system is an SMP box with 512MB
of RAM and a 3D Labs Fire GL 100 <mumble> adapter. Somebody installed
FreeBSD 3.0-RELEASE on this system (my brainwashing scheme is working!
Soon I will rule the wor--! Uh, wait. You didn't hear that.) and
discovered that this display adapter isn't supported by XFree86 (yet)
so they downloaded the XFCom_3DLabs server from somewhere.
The system seems to run fin until they start this X server. The
server loads, but it does something unfriendly to the system that
produces the following errors:
calcru: negative time of -36857 usec for pid 4036 (csh)
calcru: negative time of -51744 usec for pid 4043 (w)
calcru: negative time of -26704 usec for pid 4044 (ps)
calcru: negative time of -47557 usec for pid 4046 (reboot)
calcru: negative time of -46489 usec for pid 304 (hostname)
calcru: negative time of -24935 usec for pid 310 (ps)
Also, the system becomes really slow at this point: keystrokes
are echoed on the console very slowly. Naturally, there's no source
for the XFCom_3DLabs X server.
I built a kernel from the 3.0-19981103-SNAP distribution: this
changes the behavior slightly in that the calcru messages no longer
appear, however the X server crashes shortly after startup:
pid 254 (XFCom_3DLabs), uid 0: exited on signal 6 (core dumped)
And the system once again feels very slow and sluggish. This slowness
doesn't go away until the system is rebooted.
I know this has been talked about before. This problem is 100%
reproducible with this X server. It happens with both an SMP kernel
and a UP kernel on the same hardware. Anybody have any clues how
to go about tracking this down?
As an aside, I've only seen these messages once before on the Dell
PowerEdge 2300/400 machine that I've been using for driver development.
With the tulip clone chips, I managed to generate an interrupt storm
on several occasions which would foul up the machine pretty good.
Basically, the driver code would trigger an error interrupt of sorts
and the code that was meant to handle the interrupt would inadvertently
trigger the same interrupt over again, resulting in an infinite loop
condition. Once or twice I've done this late at night while sitting
at my terminal at home trying to remote test a driver on the machine
in the lab; since the machine is stuck and I can't reboot it from home,
I have to wait until I come to work the next morning to clobber it.
At times, when I come in, I see these same messages on the console.
I took this to mean that the interrupt storm was interfering with
the processing of clock ticks which botched the CPU accounting for
some of the daemon processes that were running when I triggered the
problem.
Anyway. If anyone has any clues as to how to deal with this problem,
I'd love to hear of it. We may be stuck with these cards, and the
Powers That Be (tm) want to use FreeBSD on these systems for a course;
I'd hate to have to tell them that they'll have to make due with console
only mode.
-Bill
--
=============================================================================
-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu
Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
"It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=============================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 16:35:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA26655
for freebsd-current-outgoing; Thu, 5 Nov 1998 16:35:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26650
for <current@freebsd.org>; Thu, 5 Nov 1998 16:35:32 -0800 (PST)
(envelope-from jdp@austin.polstra.com)
Received: from austin.polstra.com (jdp@localhost)
by austin.polstra.com (8.9.1/8.9.1) with ESMTP id QAA04895;
Thu, 5 Nov 1998 16:34:00 -0800 (PST)
(envelope-from jdp)
Message-Id: <199811060034.QAA04895@austin.polstra.com>
To: leifn@swimsuit.internet.dk
Subject: Re: sendmail.8.9.1a patch
In-Reply-To: <Pine.BSF.4.05.9811052216001.29212-100000@gina.swimsuit.internet.dk>
References: <Pine.BSF.4.05.9811052216001.29212-100000@gina.swimsuit.internet.dk>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Date: Thu, 05 Nov 1998 16:34:00 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <Pine.BSF.4.05.9811052216001.29212-100000@gina.swimsuit.internet.dk>,
Leif Neland <leifn@swimsuit.internet.dk> wrote:
> Could somebody please apply the sendmail-8.9.1a patch to
> /usr/src/contrib/sendmail?
>
> I just applied the patch, but cvsup promptly unpatched the patch :-(
Hey, that's a feature! :-)
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 16:39:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA27037
for freebsd-current-outgoing; Thu, 5 Nov 1998 16:39:34 -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 QAA27032
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 16:39:33 -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 QAA26856;
Thu, 5 Nov 1998 16:39:49 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Ryan Younce <ryany@pobox.com>
cc: current@FreeBSD.ORG
Subject: Re: Current 'make world' warnings cleanup
In-reply-to: Your message of "Mon, 02 Nov 1998 22:23:33 EST."
<199811030323.WAA25340@cheshire.dynip.com>
Date: Thu, 05 Nov 1998 16:39:48 -0800
Message-ID: <26852.910312788@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Well, seeing as how my count of all instances of ' warning: ' within my log
> of my most recent make world totals to about 85,000 lines, I figure this
> might be as good a place as any to burn my weekend/weeknight time.
Hmmm. Maybe. :)
> Is there a coordinator for this? As this is my first time sending anything
> to any of the mailing lists, let alone contributing, I figure lowering the
The problem with this task is that it requires either a committer or
someone who's got a suitable arrangement with some committer to get
these changes in on a timely basis, otherwise the work quickly goes
stale as stuff changes. I'd recommend that you find a committer willing
to play "patch filter" before taking something like this on. :-)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 16:45:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA27617
for freebsd-current-outgoing; Thu, 5 Nov 1998 16:45:18 -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 QAA27612
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 16:45:17 -0800 (PST)
(envelope-from shimon@simon-shapiro.org)
Received: (qmail 23932 invoked by uid 1000); 6 Nov 1998 01:49:00 -0000
Message-ID: <XFMail.981105204900.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: <Pine.BSF.4.05.9811051350400.10448-100000@porkfriedrice.ny.genx.net>
Date: Thu, 05 Nov 1998 20:49:00 -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: Alfred Perlstein <bright@hotjobs.com>
Subject: Re: Make Release Failure...
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Alfred Perlstein, On 05-Nov-98 you wrote:
> On Thu, 5 Nov 1998, Simon Shapiro wrote:
>
> > This I am getting for two or three days in a row. Any idea?
> >
> > loading kernel
> > text data bss dec hex filename
> > 1455152 104816 112652 1672620 1985ac kernel
> > ./dumpnlist /R/stage/boot.std/kernel > /tmp/mnt_xx/stand/symbols
> > kzip -v /R/stage/boot.std/kernel
> > kzip: bad magic in file /R/stage/boot.std/kernel, probably not a kernel
> > kzip: extract returned 200
> > real kernel start address will be: 0x1
> > real kernel end address will be: 0x65aac68a
> > *** Error code 3
> >
>
> do you have KERNFORMAT=elf?
>
> i don't think it's supported as of yet.
>
> -Alfred
Yup, yes, I admit, beat me, gag me. I made a mistake. Sorry :-)
simon
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 17:04:34 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA29204
for freebsd-current-outgoing; Thu, 5 Nov 1998 17:04:34 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from under.suspicion.org (UNDER.SUSPICION.ORG [216.27.37.14])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29189
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 17:04:24 -0800 (PST)
(envelope-from ventrex@UNDER.suspicion.org)
Received: from UNDER.SUSPICION.ORG (root@UNDER.SUSPICION.ORG [216.27.37.14])
by under.suspicion.org (8.9.1/8.9.1) with ESMTP id VAA02370;
Thu, 5 Nov 1998 21:03:33 -0400 (EWT)
(envelope-from ventrex@UNDER.suspicion.org)
Date: Thu, 5 Nov 1998 20:03:28 -0500 (EST)
From: Thomas Stromberg <ventrex@UNDER.suspicion.org>
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
cc: current@FreeBSD.ORG
Subject: Re: Grrr... calcru: negative time blah blah blah
In-Reply-To: <199811060024.TAA14156@skynet.ctr.columbia.edu>
Message-ID: <Pine.BSF.4.05.9811052002340.1378-100000@under.suspicion.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Try adding apm0 into your kernel. On my 3.0 machine I had to do that, even
if I had Advanced Power Management turned off in the BIOS. Hopefully this
solution will work for you.
========================================================================
Thomas Stromberg | smtp -> thomas@stromberg.org
System Administrator, RTC Inc. | http -> thomas.stromberg.org
Cary, NC. : talk -> ventrex@stromberg.org
(919) 380-9771 ext. 3210 : icq -> 17468041/ventrex
"the more we know, the less we are" . irc -> ventrex@EFnet
========================================================================
On Thu, 5 Nov 1998, Bill Paul wrote:
> Recently, the EE department got a bunch of new Dell machines with
> 450Mhz PII CPUs. This one particular system is an SMP box with 512MB
> of RAM and a 3D Labs Fire GL 100 <mumble> adapter. Somebody installed
> FreeBSD 3.0-RELEASE on this system (my brainwashing scheme is working!
> Soon I will rule the wor--! Uh, wait. You didn't hear that.) and
> discovered that this display adapter isn't supported by XFree86 (yet)
> so they downloaded the XFCom_3DLabs server from somewhere.
>
> The system seems to run fin until they start this X server. The
> server loads, but it does something unfriendly to the system that
> produces the following errors:
>
> calcru: negative time of -36857 usec for pid 4036 (csh)
> calcru: negative time of -51744 usec for pid 4043 (w)
> calcru: negative time of -26704 usec for pid 4044 (ps)
> calcru: negative time of -47557 usec for pid 4046 (reboot)
> calcru: negative time of -46489 usec for pid 304 (hostname)
> calcru: negative time of -24935 usec for pid 310 (ps)
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 17:53:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA02899
for freebsd-current-outgoing; Thu, 5 Nov 1998 17:53:33 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA02894
for <current@freebsd.org>; Thu, 5 Nov 1998 17:53:28 -0800 (PST)
(envelope-from wpaul@skynet.ctr.columbia.edu)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id UAA14301; Thu, 5 Nov 1998 20:58:19 -0500
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199811060158.UAA14301@skynet.ctr.columbia.edu>
Subject: Re: Grrr... calcru: negative time blah blah blah
To: ventrex@UNDER.suspicion.org (Thomas Stromberg)
Date: Thu, 5 Nov 1998 20:58:17 -0500 (EST)
Cc: current@FreeBSD.ORG
In-Reply-To: <Pine.BSF.4.05.9811052002340.1378-100000@under.suspicion.org> from "Thomas Stromberg" at Nov 5, 98 08:03:28 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Of all the gin joints in all the towns in all the world, Thomas
Stromberg had to walk into mine and say:
> Try adding apm0 into your kernel. On my 3.0 machine I had to do that, even
> if I had Advanced Power Management turned off in the BIOS. Hopefully this
> solution will work for you.
No, sorry: no go. No APM device is detected. With APM support in
the kernel, the X server dies with 'Cpu time limit exceeded' and
the 'calcru: negative time...' errors are back. The 3.0-RELEASE
GENERIC kernel had APM support too and it also had the errors.
My money says this has something to do with the server writing to
/dev/io.
-Bill
--
=============================================================================
-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu
Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
"It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=============================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 17:58:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA03286
for freebsd-current-outgoing; Thu, 5 Nov 1998 17:58:03 -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 RAA03281
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 17:58:02 -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 RAA01542;
Thu, 5 Nov 1998 17:56:44 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811060156.RAA01542@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
cc: current@FreeBSD.ORG
Subject: Re: Grrr... calcru: negative time blah blah blah
In-reply-to: Your message of "Thu, 05 Nov 1998 19:24:54 EST."
<199811060024.TAA14156@skynet.ctr.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Nov 1998 17:56:44 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Recently, the EE department got a bunch of new Dell machines with
> 450Mhz PII CPUs. This one particular system is an SMP box with 512MB
> of RAM and a 3D Labs Fire GL 100 <mumble> adapter. Somebody installed
> FreeBSD 3.0-RELEASE on this system (my brainwashing scheme is working!
> Soon I will rule the wor--! Uh, wait. You didn't hear that.) and
> discovered that this display adapter isn't supported by XFree86 (yet)
> so they downloaded the XFCom_3DLabs server from somewhere.
>
> The system seems to run fin until they start this X server. The
> server loads, but it does something unfriendly to the system that
> produces the following errors:
>
> calcru: negative time of -36857 usec for pid 4036 (csh)
> calcru: negative time of -51744 usec for pid 4043 (w)
> calcru: negative time of -26704 usec for pid 4044 (ps)
> calcru: negative time of -47557 usec for pid 4046 (reboot)
> calcru: negative time of -46489 usec for pid 304 (hostname)
> calcru: negative time of -24935 usec for pid 310 (ps)
>
> Also, the system becomes really slow at this point: keystrokes
> are echoed on the console very slowly. Naturally, there's no source
> for the XFCom_3DLabs X server.
Sounds like it's starting an interrupt storm.
> I built a kernel from the 3.0-19981103-SNAP distribution: this
> changes the behavior slightly in that the calcru messages no longer
> appear, however the X server crashes shortly after startup:
>
> pid 254 (XFCom_3DLabs), uid 0: exited on signal 6 (core dumped)
>
> And the system once again feels very slow and sluggish. This slowness
> doesn't go away until the system is rebooted.
Definitely sounds like the card is generating endless interrupts. Can
you turn interrupts off on the card? (I doubt it.)
Any chance of an Xi server for this card?
> I know this has been talked about before. This problem is 100%
> reproducible with this X server. It happens with both an SMP kernel
> and a UP kernel on the same hardware. Anybody have any clues how
> to go about tracking this down?
Check the system stats for interrupt counts.
> Anyway. If anyone has any clues as to how to deal with this problem,
> I'd love to hear of it. We may be stuck with these cards, and the
> Powers That Be (tm) want to use FreeBSD on these systems for a course;
> I'd hate to have to tell them that they'll have to make due with console
> only mode.
Tell the Powers that they may want to consider more sensible video
cards; you want good *2d* performance for X, not 3d.
--
\\ 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 5 17:59:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA03350
for freebsd-current-outgoing; Thu, 5 Nov 1998 17:59:18 -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 RAA03344;
Thu, 5 Nov 1998 17:59:16 -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 RAA15731;
Thu, 5 Nov 1998 17:58:58 -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 RAA25323;
Thu, 5 Nov 1998 17:58:57 -0800 (PST)
Received: (from gdonl@localhost)
by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id RAA16003;
Thu, 5 Nov 1998 17:58:56 -0800 (PST)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199811060158.RAA16003@salsa.gv.tsc.tdk.com>
Date: Thu, 5 Nov 1998 17:58:55 -0800
In-Reply-To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
"Re: ficl broken" (Nov 5, 9:12am)
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>,
Don Lewis <Don.Lewis@tsc.tdk.com>
Subject: Re: ficl broken
Cc: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>, current@FreeBSD.ORG,
msmith@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Nov 5, 9:12am, "Jordan K. Hubbard" wrote:
} Subject: Re: ficl broken
} > ${PERL} isn't defined in sys/boot/ficl/Makefile. It should either be defined
} > (in sys.mk?) or 'perl' should be used instead.
}
} Very temporary abberation - I fixed it about 10 minutes later. :)
Hmn, isn't this going to be a problem if you build with NOPERL defined?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 19:08:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA08671
for freebsd-current-outgoing; Thu, 5 Nov 1998 19:08:59 -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 TAA08665
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 19:08:58 -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 VAA24238;
Thu, 5 Nov 1998 21:09:48 GMT
(envelope-from psalzman@gamefish.pcola.gulf.net)
Date: Thu, 5 Nov 1998 21:09:48 +0000 (GMT)
From: Phillip Salzman <psalzman@gamefish.pcola.gulf.net>
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
cc: current@FreeBSD.ORG
Subject: Re: Grrr... calcru: negative time blah blah blah
In-Reply-To: <199811060024.TAA14156@skynet.ctr.columbia.edu>
Message-ID: <Pine.BSF.4.05.9811052108060.24174-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 get those same calcu errors. Except, I get them when I
attempt to ``make buildworld'' or compile a lot of stuff that raises
my load. This stops me, obviously.
I am told they are a problem with APM, but took it all out of
my kernel - still no luck.
--
PhillipSalzman
On Thu, 5 Nov 1998, Bill Paul wrote:
> Recently, the EE department got a bunch of new Dell machines with
> 450Mhz PII CPUs. This one particular system is an SMP box with 512MB
> of RAM and a 3D Labs Fire GL 100 <mumble> adapter. Somebody installed
> FreeBSD 3.0-RELEASE on this system (my brainwashing scheme is working!
> Soon I will rule the wor--! Uh, wait. You didn't hear that.) and
> discovered that this display adapter isn't supported by XFree86 (yet)
> so they downloaded the XFCom_3DLabs server from somewhere.
>
> The system seems to run fin until they start this X server. The
> server loads, but it does something unfriendly to the system that
> produces the following errors:
>
> calcru: negative time of -36857 usec for pid 4036 (csh)
> calcru: negative time of -51744 usec for pid 4043 (w)
> calcru: negative time of -26704 usec for pid 4044 (ps)
> calcru: negative time of -47557 usec for pid 4046 (reboot)
> calcru: negative time of -46489 usec for pid 304 (hostname)
> calcru: negative time of -24935 usec for pid 310 (ps)
>
> Also, the system becomes really slow at this point: keystrokes
> are echoed on the console very slowly. Naturally, there's no source
> for the XFCom_3DLabs X server.
>
> I built a kernel from the 3.0-19981103-SNAP distribution: this
> changes the behavior slightly in that the calcru messages no longer
> appear, however the X server crashes shortly after startup:
>
> pid 254 (XFCom_3DLabs), uid 0: exited on signal 6 (core dumped)
>
> And the system once again feels very slow and sluggish. This slowness
> doesn't go away until the system is rebooted.
>
> I know this has been talked about before. This problem is 100%
> reproducible with this X server. It happens with both an SMP kernel
> and a UP kernel on the same hardware. Anybody have any clues how
> to go about tracking this down?
>
> As an aside, I've only seen these messages once before on the Dell
> PowerEdge 2300/400 machine that I've been using for driver development.
> With the tulip clone chips, I managed to generate an interrupt storm
> on several occasions which would foul up the machine pretty good.
> Basically, the driver code would trigger an error interrupt of sorts
> and the code that was meant to handle the interrupt would inadvertently
> trigger the same interrupt over again, resulting in an infinite loop
> condition. Once or twice I've done this late at night while sitting
> at my terminal at home trying to remote test a driver on the machine
> in the lab; since the machine is stuck and I can't reboot it from home,
> I have to wait until I come to work the next morning to clobber it.
> At times, when I come in, I see these same messages on the console.
> I took this to mean that the interrupt storm was interfering with
> the processing of clock ticks which botched the CPU accounting for
> some of the daemon processes that were running when I triggered the
> problem.
>
> Anyway. If anyone has any clues as to how to deal with this problem,
> I'd love to hear of it. We may be stuck with these cards, and the
> Powers That Be (tm) want to use FreeBSD on these systems for a course;
> I'd hate to have to tell them that they'll have to make due with console
> only mode.
>
> -Bill
>
> --
> =============================================================================
> -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu
> Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research
> Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
> =============================================================================
> "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
> =============================================================================
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 22:07:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA21468
for freebsd-current-outgoing; Thu, 5 Nov 1998 22:07:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from gravy.kishka.net (dyn-13.blackbox-2.netaxs.com [207.106.60.13])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21462
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 22:07:29 -0800 (PST)
(envelope-from bleez@netaxs.com)
Received: from gravy.kishka.net (root@gravy.kishka.net [10.0.0.1])
by gravy.kishka.net (8.9.1/8.8.8) with ESMTP id BAA00512;
Fri, 6 Nov 1998 01:06:56 -0500 (EST)
(envelope-from bleez@netaxs.com)
Date: Fri, 6 Nov 1998 01:06:56 -0500 (EST)
From: Bryan Liesner <bleez@netaxs.com>
To: Mike Smith <mike@smith.net.au>
cc: current@FreeBSD.ORG
Subject: Re: Cyrix M2 (6x86MX) tester required
In-Reply-To: <199811052322.PAA00713@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811060058310.487-100000@gravy.kishka.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, 5 Nov 1998, Mike Smith wrote:
<>
<> Simple call; I have a code change that I need to test on a Cyrix M2 -
<> if you have one and are able to build a kernel and try booting it, I'd
<> be very pleased to hear from you.
<>
Mike, I have a Cyrix 6x86MX PR 266 (see below). If this is useful to you,
I'll give it a go.
A snip from 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 #6: Thu Nov 5 00:19:33 EST 1998
bryan@gravy.kishka.net:/usr/src/sys/compile/GRAVY
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 205766676 Hz
CPU: Cyrix 6x86MX (205.77-MHz 686-class CPU)
Origin = "CyrixInstead" Id = 0x600 Stepping=0 DIR=0x0752
Features=0x80a135<FPU,DE,TSC,MSR,CX8,PGE,CMOV,MMX>
=======================================================================
-----------------------------------------
| Bryan D. Liesner LeezSoft Inc. |
-----------------------------------------
| Powered by FreeBSD Composed with vi |
-----------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 22:35:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA23036
for freebsd-current-outgoing; Thu, 5 Nov 1998 22:35:09 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23014
for <freebsd-current@FreeBSD.ORG>; Thu, 5 Nov 1998 22:35:04 -0800 (PST)
(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id HAA25664
for freebsd-current@FreeBSD.ORG; Fri, 6 Nov 1998 07:34:36 +0100 (CET)
(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (VMailer, from userid 101)
id 32269155C; Fri, 6 Nov 1998 07:19:31 +0100 (CET)
Date: Fri, 6 Nov 1998 07:19:31 +0100
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: freebsd-current@FreeBSD.ORG
Subject: Re: sendmail.8.9.1a patch
Message-ID: <19981106071931.A17320@keltia.freenix.fr>
Mail-Followup-To: freebsd-current@FreeBSD.ORG
References: <19981105234456.B15131@keltia.freenix.fr> <Pine.BSF.4.05.9811060048570.6421-100000@gina.swimsuit.internet.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.4i
In-Reply-To: <Pine.BSF.4.05.9811060048570.6421-100000@gina.swimsuit.internet.dk>; from Leif Neland on Fri, Nov 06, 1998 at 12:51:56AM +0100
X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4772 AMD-K6 MMX @ 200 MHz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
According to Leif Neland:
> Which patch? There isn't any at ftp.sendmail.org
Look on DejaNews, Usenet is the only place I've seen the patch...
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-BETA #4: Thu Oct 15 01:36:57 CEST 1998
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 22:35:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA23057
for freebsd-current-outgoing; Thu, 5 Nov 1998 22:35:14 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23048
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 22:35:11 -0800 (PST)
(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id HAA25665
for current@FreeBSD.ORG; Fri, 6 Nov 1998 07:35:00 +0100 (CET)
(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (VMailer, from userid 101)
id 9E2EC155C; Fri, 6 Nov 1998 07:34:41 +0100 (CET)
Date: Fri, 6 Nov 1998 07:34:41 +0100
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: current@FreeBSD.ORG
Subject: Re: ficl broken
Message-ID: <19981106073441.A17359@keltia.freenix.fr>
Mail-Followup-To: current@FreeBSD.ORG
References: <jkh@time.cdrom.com> <199811060158.RAA16003@salsa.gv.tsc.tdk.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.4i
In-Reply-To: <199811060158.RAA16003@salsa.gv.tsc.tdk.com>; from Don Lewis on Thu, Nov 05, 1998 at 05:58:55PM -0800
X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4772 AMD-K6 MMX @ 200 MHz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
According to Don Lewis:
> Hmn, isn't this going to be a problem if you build with NOPERL defined?
It is. It will fail (as my other message shows). I'm using NOPERL on some
of my machines because I already have an up-to-date perl in /usr/local...
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-BETA #4: Thu Oct 15 01:36:57 CEST 1998
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 22:52:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA24651
for freebsd-current-outgoing; Thu, 5 Nov 1998 22:52:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles159.castles.com [208.214.165.159])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24646
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 22:52:34 -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 WAA00421;
Thu, 5 Nov 1998 22:51:38 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811060651.WAA00421@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Ollivier Robert <roberto@keltia.freenix.fr>
cc: current@FreeBSD.ORG
Subject: Re: ficl broken
In-reply-to: Your message of "Fri, 06 Nov 1998 07:34:41 +0100."
<19981106073441.A17359@keltia.freenix.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Nov 1998 22:51:37 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> According to Don Lewis:
> > Hmn, isn't this going to be a problem if you build with NOPERL defined?
>
> It is. It will fail (as my other message shows). I'm using NOPERL on some
> of my machines because I already have an up-to-date perl in /usr/local...
Yup. I'll probably just commit the generated file and let people mung
around it to suit.
--
\\ 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 5 22:55:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA25059
for freebsd-current-outgoing; Thu, 5 Nov 1998 22:55:50 -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 WAA25052
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 22:55:49 -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 WAA29928;
Thu, 5 Nov 1998 22:55:48 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Mike Smith <mike@smith.net.au>
cc: Ollivier Robert <roberto@keltia.freenix.fr>, current@FreeBSD.ORG
Subject: Re: ficl broken
In-reply-to: Your message of "Thu, 05 Nov 1998 22:51:37 PST."
<199811060651.WAA00421@dingo.cdrom.com>
Date: Thu, 05 Nov 1998 22:55:48 -0800
Message-ID: <29924.910335348@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > It is. It will fail (as my other message shows). I'm using NOPERL on some
> > of my machines because I already have an up-to-date perl in /usr/local...
>
> Yup. I'll probably just commit the generated file and let people mung
> around it to suit.
Hmph. Is NOPERL really supposed to work for a world build? If done
in a properly chrooted environment, such builds generally fall over
anyway when makewhatis (a perl script) is run.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Thu Nov 5 23:20:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA27374
for freebsd-current-outgoing; Thu, 5 Nov 1998 23:20:12 -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 XAA27366
for <current@FreeBSD.ORG>; Thu, 5 Nov 1998 23:20:08 -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 IAA02915;
Fri, 6 Nov 1998 08:18:37 +0100 (CET)
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
cc: current@FreeBSD.ORG
Subject: Re: Grrr... calcru: negative time blah blah blah
In-reply-to: Your message of "Thu, 05 Nov 1998 19:24:54 EST."
<199811060024.TAA14156@skynet.ctr.columbia.edu>
Date: Fri, 06 Nov 1998 08:18:37 +0100
Message-ID: <2913.910336717@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'm still banging my head against this one. I'm working with a
handfull of people who has this problem, trying to identify what
the heck is happening. I can't reproduce it on any of my machines
here.
If you have an interrupt storm which could lock out hardclock()
that will certainly screw things up badly.
I have put some diagnostic patches at:
http://www.freebsd.org/~phk/tc_diag.diff
Please notice the patch to sysctl in there too, it is needed to
print out all of the "delta history buffer".
Please try these patches out, they will not panic the machine if
the tests trigger, merely report some applicable details.
If any of the tests trigger, please email me:
/var/run/dmesg.boot
`dmesg`
`sysctl kern.timecounter`
`sysctl debug`
Mike, Shimon & Warner: There is one new check compared to the
patch you have, but it is not critical (yet).
Poul-Henning
In message <199811060024.TAA14156@skynet.ctr.columbia.edu>, Bill Paul writes:
>Recently, the EE department got a bunch of new Dell machines with
>450Mhz PII CPUs. This one particular system is an SMP box with 512MB
>of RAM and a 3D Labs Fire GL 100 <mumble> adapter. Somebody installed
>FreeBSD 3.0-RELEASE on this system (my brainwashing scheme is working!
>Soon I will rule the wor--! Uh, wait. You didn't hear that.) and
>discovered that this display adapter isn't supported by XFree86 (yet)
>so they downloaded the XFCom_3DLabs server from somewhere.
>
>The system seems to run fin until they start this X server. The
>server loads, but it does something unfriendly to the system that
>produces the following errors:
>
>calcru: negative time of -36857 usec for pid 4036 (csh)
>calcru: negative time of -51744 usec for pid 4043 (w)
>calcru: negative time of -26704 usec for pid 4044 (ps)
>calcru: negative time of -47557 usec for pid 4046 (reboot)
>calcru: negative time of -46489 usec for pid 304 (hostname)
>calcru: negative time of -24935 usec for pid 310 (ps)
--
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 Fri Nov 6 01:18:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA06739
for freebsd-current-outgoing; Fri, 6 Nov 1998 01:18:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from chaotic.oz.org (chaotic.oz.org [203.20.237.203])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06730
for <current@freebsd.org>; Fri, 6 Nov 1998 01:18:38 -0800 (PST)
(envelope-from simon@oz.org)
Received: from localhost (localhost [127.0.0.1])
by chaotic.oz.org (8.9.1/8.8.8) with ESMTP id TAA03849
for <current@freebsd.org>; Fri, 6 Nov 1998 19:18:28 +1000 (EST)
(envelope-from simon@oz.org)
Date: Fri, 6 Nov 1998 19:18:28 +1000 (EST)
From: Simon Coggins <simon@oz.org>
Reply-To: chaos@ultra.net.au
To: current@FreeBSD.ORG
Subject: dynamic libs on elf.
Message-ID: <Pine.BSF.4.05.9811061911410.3815-100000@chaotic.oz.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,
Well I finally got my system changed from aout to elf and now I notice that
dynamic libs are handled totaly differently on ELF and have broken all of my
dynamic lib'ed programs. Here's what it's doing differently now and
hopefully someone can tell me how to fix it.
When loading a dynamic lib with RTLD_NOW, it always fails if the module
calls a function that is in the main progran that is loading the module. Now
this use to work on aout but now it won't work anymore.
There is some example code at the end of this message which is the code I'm
using.
[simon@chaotic]:/tmp/p> gcc -o dynamic dynamic.c
[simon@chaotic]:/tmp/p> gcc -c -DMOD dynamic.c
[simon@chaotic]:/tmp/p> ld -Bshareable dynamic.o -o dynamic.so
[simon@chaotic]:/tmp/p> ./dynamic
dlopen(): ./dynamic.so: Undefined symbol "print_data"
So when loading the module it couldn't find the function print_data which is
in the main program.
HELP! :)
Regards
Simon
---
+---------------------------------------------------------------+
| Email: chaos@ultra.net.au, chaos@oz.org, simon@bofh.com.au |
| http://www.ultra.net.au/~chaos Simon.Coggins@jcu.edu.au. |
| Chaos on IRC, IRC Operator for the OzORG Network |
+---------------------------------------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 01:27:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA07629
for freebsd-current-outgoing; Fri, 6 Nov 1998 01:27:33 -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 BAA07624
for <current@freebsd.org>; Fri, 6 Nov 1998 01:27:30 -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 EAA06890
for <current@freebsd.org>; Fri, 6 Nov 1998 04:30:04 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Fri, 6 Nov 1998 04:30:03 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: current@FreeBSD.ORG
Subject: latest kernel breaks linux netscape.
Message-ID: <Pine.BSF.4.05.9811060414080.756-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
cvsup as of a few hours ago and netscape-linux gets a sigbus when starting
up. linux_kdump is broken on 3.0 can i do anything to show a trace?
I totally forgot i was running linux netscape until i did a kdump and it
looked all odd. :)
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 Fri Nov 6 01:40:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA08607
for freebsd-current-outgoing; Fri, 6 Nov 1998 01:40:29 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from chaotic.oz.org (chaotic.oz.org [203.20.237.203])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08602
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 01:40:20 -0800 (PST)
(envelope-from simon@oz.org)
Received: from localhost (localhost [127.0.0.1])
by chaotic.oz.org (8.9.1/8.8.8) with ESMTP id TAA03945
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 19:40:13 +1000 (EST)
(envelope-from simon@oz.org)
Date: Fri, 6 Nov 1998 19:40:13 +1000 (EST)
From: Simon Coggins <simon@oz.org>
Reply-To: chaos@ultra.net.au
To: current@FreeBSD.ORG
Subject: Re: dynamic libs on elf.
In-Reply-To: <Pine.BSF.4.05.9811061911410.3815-100000@chaotic.oz.org>
Message-ID: <Pine.BSF.4.05.9811061939450.3928-100000@chaotic.oz.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
For the record I just found out what it is. gcc -rdynamic fixes this. Sorry
for wasting bandwidth.
On Fri, 6 Nov 1998, Simon Coggins wrote:
>
> Hi,
>
> Well I finally got my system changed from aout to elf and now I notice that
> dynamic libs are handled totaly differently on ELF and have broken all of my
> dynamic lib'ed programs. Here's what it's doing differently now and
> hopefully someone can tell me how to fix it.
>
> When loading a dynamic lib with RTLD_NOW, it always fails if the module
> calls a function that is in the main progran that is loading the module. Now
> this use to work on aout but now it won't work anymore.
>
> There is some example code at the end of this message which is the code I'm
> using.
>
> [simon@chaotic]:/tmp/p> gcc -o dynamic dynamic.c
> [simon@chaotic]:/tmp/p> gcc -c -DMOD dynamic.c
> [simon@chaotic]:/tmp/p> ld -Bshareable dynamic.o -o dynamic.so
> [simon@chaotic]:/tmp/p> ./dynamic
> dlopen(): ./dynamic.so: Undefined symbol "print_data"
>
> So when loading the module it couldn't find the function print_data which is
> in the main program.
>
> HELP! :)
>
> Regards
> Simon
>
> ---
> +---------------------------------------------------------------+
> | Email: chaos@ultra.net.au, chaos@oz.org, simon@bofh.com.au |
> | http://www.ultra.net.au/~chaos Simon.Coggins@jcu.edu.au. |
> | Chaos on IRC, IRC Operator for the OzORG Network |
> +---------------------------------------------------------------+
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
Regards
Simon
---
+---------------------------------------------------------------+
| Email: chaos@ultra.net.au, chaos@oz.org, simon@bofh.com.au |
| http://www.ultra.net.au/~chaos Simon.Coggins@jcu.edu.au. |
| Chaos on IRC, IRC Operator for the OzORG Network |
+---------------------------------------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 02:48:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA14558
for freebsd-current-outgoing; Fri, 6 Nov 1998 02:48:37 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vss.sci-nnov.ru (vss.sci-nnov.ru [193.125.71.26])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14172;
Fri, 6 Nov 1998 02:43:33 -0800 (PST)
(envelope-from dmiter@sci-nnov.ru)
Received: from winhome (home.sci-nnov.ru [194.190.176.102]) by vss.sci-nnov.ru (8.8.8/Dmiter-4.2vss) with SMTP id NAA06955; Fri, 6 Nov 1998 13:42:38 +0300 (MSK)
Message-ID: <000301be0972$10f05460$0200000a@winhome.sci-nnov.ru>
Reply-To: "Dmitry Eremin" <dmiter@sci-nnov.ru>
From: "Dmitry Eremin" <dmiter@sci-nnov.ru>
To: <freebsd-current@FreeBSD.ORG>
Cc: <freebsd-bugs@FreeBSD.ORG>
Subject: /kernel: arp: 192.168.1.188 is on de1 but got reply from 00:c0:4f:a4:81:2d on de0
Date: Fri, 6 Nov 1998 13:41:43 +0300
MIME-Version: 1.0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I have cvsuped version FreeBSD 3.0-CURRENT #6: Fri Nov 6 10:24:07 MSK 1998
and following configuration. Interface de0 have real IP address and
connected to Internet router. In this network only two address, our computer
and router. Interface de1 connected to our Intranet.
$ Ifconfig -a
de0: flags=88c3<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet xx.xx.xx.xx netmask 0xfffffffc broadcast xx.xx.xx.xx
ether 00:00:c0:b2:9f:d0
media: 10baseT/UTP status: active
supported media: 100baseTX <full-duplex> 100baseTX 10baseT/UTP
<full-duplex> 10baseT/UTP
de1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.239 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:00:c0:b8:a1:d0
media: 10baseT/UTP status: active
supported media: 100baseTX <full-duplex> 100baseTX 10baseT/UTP
<full-duplex> 10baseT/UTP
I have the following messages in the syslog:
/kernel: arp: 192.168.1.188 is on de1 but got reply from 00:c0:4f:a4:81:2d
on de0
$ tcpdump -i de1 arp
arp who-has 192.168.1.188 tell 192.168.1.231
arp reply 192.168.1.188 is-at 0:c0:4f:a4:81:2d
$ tcpdump -i de0 arp
arp who-has 192.168.1.188 tell 192.168.1.231
As you see, into de0 relay hasn't been received.
What is happening? What I do not right? Help me please.
Best regards, Dmitry.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 03:58:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA18858
for freebsd-current-outgoing; Fri, 6 Nov 1998 03:58:37 -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 DAA18847
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 03:58:33 -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 GAA10122;
Fri, 6 Nov 1998 06:56:48 -0500 (EST)
Date: Fri, 6 Nov 1998 06:56:48 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: Mike Smith <mike@smith.net.au>
cc: freebsd-current@FreeBSD.ORG
Subject: ficl
Message-ID: <Pine.BSF.4.05.9811060653440.300-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 watching all your work using ficl with a lot of interest, but I
don't understand the operating environment of programs at that early
stage of boot too well. Is the filesystem available? Can any use be
made of other Unix utils at all? What devices are available?
Obviously, screen input/output is *somewhat* available, right?
Thanks
----------------------------+-----------------------------------------------
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 Fri Nov 6 04:02:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA19674
for freebsd-current-outgoing; Fri, 6 Nov 1998 04:02:20 -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 EAA19537
for <freebsd-current@freebsd.org>; Fri, 6 Nov 1998 04:01:44 -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 MAA24056
for <freebsd-current@freebsd.org>; Fri, 6 Nov 1998 12:14:57 +0100 (CET)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Fri, 6 Nov 1998 12:14:56 +0100 (CET)
From: Andrzej Bialecki <abial@nask.pl>
X-Sender: abial@korin.warman.org.pl
To: freebsd-current@FreeBSD.ORG
Subject: nfs.ko panics on unloading
Message-ID: <Pine.BSF.4.02A.9811061205320.21136-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
Hi,
With latest sources, running ELF kernel (and yes, I rebuilt kernel _and_
modules) loading nfs.ko works ok, but unloading results in immediate panic
(page fault in kernel mode) and stack corruption. Is this a bug or a
feature?
This is very repeatable here, but if anyone wants a coredump, I've got
one.
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 Fri Nov 6 04:19:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA22789
for freebsd-current-outgoing; Fri, 6 Nov 1998 04:19:53 -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 EAA22782
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 04:19:48 -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 NAA16265; Fri, 6 Nov 1998 13:19:00 +0100 (MET)
Message-ID: <XFMail.981106131900.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
In-Reply-To: <Pine.BSF.4.05.9811060414080.756-100000@porkfriedrice.ny.genx.net>
Date: Fri, 06 Nov 1998 13:19:00 +0100 (MET)
Organization: University of bayreuth
From: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
To: Alfred Perlstein <bright@hotjobs.com>
Subject: RE: latest kernel breaks linux netscape.
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 06-Nov-98 Alfred Perlstein wrote:
>
> cvsup as of a few hours ago and netscape-linux gets a sigbus when starting
> up. linux_kdump is broken on 3.0 can i do anything to show a trace?
>
> I totally forgot i was running linux netscape until i did a kdump and it
> looked all odd. :)
>
> 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
----------------------------------
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 .
Werner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 04:45:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA25950
for freebsd-current-outgoing; Fri, 6 Nov 1998 04:45:24 -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 EAA25937
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 04:45:20 -0800 (PST)
(envelope-from will@ns.oeno.com)
Received: (qmail 13548 invoked by uid 1001); 6 Nov 1998 12:45:03 -0000
Date: 6 Nov 1998 12:44:58 -0000
Message-ID: <19981106124458.13542.qmail@ns.oeno.com>
From: Ville-Pertti Keinonen <will@iki.fi>
To: peter@netplex.com.au
CC: james@westongold.com, current@FreeBSD.ORG
In-reply-to: <199811051428.WAA06376@spinner.netplex.com.au> (message from
Peter Wemm on Thu, 05 Nov 1998 22:28:46 +0800)
Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> We've done it that way before and it was a real pain in the backside. There
> are a number of disincentives:
> - apic id's are all over the place. 0, 12 and 13 are common with P6's.
> Having 16 slots in arrays for all the per-cpu variables is not nice.
You only need one per-cpu structure for the variables and one array of
slots that point to those structures.
> - converting things from variables to macros shows up other things. I
> seem to recall some places where "curproc" was referenced over and
> over again in loops and the like.
Don't do that, then.
> - we have to have different binaries modules/lkm's for SMP and non-smp
> kernels.
Unless you change the way the kernel works without SMP. I think the
current SMP code goes too far in ensuring that a non-SMP kernel isn't
affected. You can't continue that way indefinitely, certainly not if
you want kernel threads.
> - accessing the local apic is *much* slower than a memory access (according
> to one of the intel people who told us to try and do it this way if we
> could).
Kernel stacks certainly have a fixed size, are they also aligned? ;--)
> - it was a lot of pain to get working in the first place.
That's natural when you do something like SMP in a system that wasn't
designed for it.
You can't expect the remaining stuff to be painless, either. Locking
is still supposed to become finer-grained eventually, right? ;--)
> rfork() could "set" %fs for the child to tell it what slot to use. If it
> wished to leave %fs untouched, it could use it at any time. Otherwise it
> would have to store it somewhere. It would be the same value for all
> processes on the system.
Having a single segment still assumes cpu-specific page directories.
Of course they aren't *that* expensive.
> The bit that I don't like about it is that it forces all the stacks to have
> the same upper limit size. That could be a bit wasteful of address space,
> or could leave you short on room to grow the stack. Incidently, I'd like a
> special mmap() option to provide a real grow-down stack in a specified
> region. mmap()ing a few hundred kb of stack from anonymous swap times a
> few hundred threads adds up on the size counter.
I think multithreaded programs should be quite conservative in terms
of stack usage. Reasonably-written programs that don't allocate
buffers at several nesting levels on the stack shouldn't typically use
more than a couple of kB of stack. I haven't looked at what the
actual case is in the real world, multithreaded programs still aren't
common (most of them are commercial).
On the Amiga, 4k was how much stack you allocated for somewhat
stack-hungry programs...until programs ported from Unix came along...
Multithreaded programs can't generally expect to allocate huge amounts
of stack the way many traditional programs (such as GNU C) do. Even
with variable stack sizes, a stack-hungry program is probably going to
have several stack-hungry threads.
But yes, there are lots of other problems, including the fact that
setting the stack size limit using the POSIX thread API becomes
difficult...
> Also, while on the subject, something Julian said has got me thinking about
> creating kernel threads on the fly when and if a user thread happens to
> block. This sounds rather interesting.. - async IO is done this way too I
That sounds like the opposite of what I did in bpmk (where kernel
threads are detached from user threads when they block on message
passing -- of course the kernel knows about both kernel and user
threads, "kernel" threads just mean runnable threads).
> think. It would require a fair amount of cooperation between the thread
> "engine" and the kernel, perhaps by having an executive thread of sorts
> that handled the kernel interation and thread activation.
That could be good.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 05:00:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA27088
for freebsd-current-outgoing; Fri, 6 Nov 1998 05:00:48 -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 FAA27083
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 05:00:44 -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 IAA12956;
Fri, 6 Nov 1998 08:02:43 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Fri, 6 Nov 1998 08:02:43 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
cc: current@FreeBSD.ORG
Subject: RE: latest kernel breaks linux netscape.
In-Reply-To: <XFMail.981106131900.werner@btp1da.phy.uni-bayreuth.de>
Message-ID: <Pine.BSF.4.05.9811060801560.756-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
4.5-freebsd-fullversion works fine, fast and peppy. exits fine.
4.5-linux sigbus on startup.
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 Fri, 6 Nov 1998, Werner Griessl wrote:
>
> On 06-Nov-98 Alfred Perlstein wrote:
> >
> > cvsup as of a few hours ago and netscape-linux gets a sigbus when starting
> > up. linux_kdump is broken on 3.0 can i do anything to show a trace?
> >
> > I totally forgot i was running linux netscape until i did a kdump and it
> > looked all odd. :)
> >
> > 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
>
> ----------------------------------
>
> 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 .
>
> Werner
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 05:39:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA00626
for freebsd-current-outgoing; Fri, 6 Nov 1998 05:39:29 -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 FAA00620
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 05:39:27 -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 IAA13065;
Fri, 6 Nov 1998 08:41:42 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Fri, 6 Nov 1998 08:41:41 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
cc: current@FreeBSD.ORG
Subject: RE: latest kernel breaks linux netscape.
In-Reply-To: <Pine.BSF.4.05.9811060801560.756-100000@porkfriedrice.ny.genx.net>
Message-ID: <Pine.BSF.4.05.9811060833200.756-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
> > 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 .
> >
> > Werner
> >
someone recommended i recompile my lkms/klds, i'm still aout kernel at
the moment.
what are we using currently for aout kernels? do ELF kernels produce
a crash dump you can analyze yet?
why wasn't this done automagically from
"make buildworld ; make installworld"
?
thanks,
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 06:02:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA01978
for freebsd-current-outgoing; Fri, 6 Nov 1998 06:02:05 -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 GAA01911
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 06:01:45 -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 PAA21054; Fri, 6 Nov 1998 15:00:40 +0100 (MET)
Message-ID: <XFMail.981106150040.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
In-Reply-To: <Pine.BSF.4.05.9811060833200.756-100000@porkfriedrice.ny.genx.net>
Date: Fri, 06 Nov 1998 15:00:40 +0100 (MET)
Organization: University of bayreuth
From: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
To: Alfred Perlstein <bright@hotjobs.com>
Subject: RE: latest kernel breaks linux netscape.
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 06-Nov-98 Alfred Perlstein 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 .
>> >
>> > Werner
>> >
>
> someone recommended i recompile my lkms/klds, i'm still aout kernel at
> the moment.
>
> what are we using currently for aout kernels? do ELF kernels produce
> a crash dump you can analyze yet?
I can try to make an ELF kernel.
>
> why wasn't this done automagically from
> "make buildworld ; make installworld"
> ?
does it automagically !
>
> thanks,
> -Alfred
Werner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 06:14:54 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA03315
for freebsd-current-outgoing; Fri, 6 Nov 1998 06:14:54 -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 GAA03310
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 06:14:53 -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 JAA13113;
Fri, 6 Nov 1998 09:17:18 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Fri, 6 Nov 1998 09:17:18 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
cc: current@FreeBSD.ORG
Subject: RE: latest kernel breaks linux netscape.
In-Reply-To: <XFMail.981106150040.werner@btp1da.phy.uni-bayreuth.de>
Message-ID: <Pine.BSF.4.05.9811060915590.756-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 Fri, 6 Nov 1998, Werner Griessl wrote:
>
> On 06-Nov-98 Alfred Perlstein 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 .
> >> >
> >> > Werner
> >> >
> >
> > someone recommended i recompile my lkms/klds, i'm still aout kernel at
> > the moment.
> >
> > what are we using currently for aout kernels? do ELF kernels produce
> > a crash dump you can analyze yet?
>
> I can try to make an ELF kernel.
no no no :) this was being asked to the -current developers :)
but if you want to...
> > why wasn't this done automagically from
> > "make buildworld ; make installworld"
> > ?
>
> does it automagically !
this hasn't been my experiance as of lately...
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 06:23:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA04580
for freebsd-current-outgoing; Fri, 6 Nov 1998 06:23:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA04575
for <freebsd-current@freebsd.org>; Fri, 6 Nov 1998 06:23:39 -0800 (PST)
(envelope-from root@zappa.demon.nl)
Received: (from root@localhost)
by zappa.demon.nl (8.9.1/8.8.8) id PAA28838
for freebsd-current@freebsd.org; Fri, 6 Nov 1998 15:24:35 +0100 (CET)
(envelope-from root)
Message-ID: <19981106152435.A28822@demon.nl>
Date: Fri, 6 Nov 1998 15:24:35 +0100
From: Ron Klinkien <root@demon.nl>
To: freebsd-current@FreeBSD.ORG
Subject: make buildworld question
Reply-To: ron@zappa.demon.nl
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
After some bad starts with the huge Linux distributions
i'm a happy FreeBSD user for some weeks now, ;-)
and I started to get current with cvsup for a few days in a row .
But when doing make a buildworld I get the following problems in
the /usr/share/doc area.
---cut---
===> share/doc/psd
===> share/doc/psd/title
touch _stamp.extraobjs
(cd /usr/src/share/doc/psd/title; groff -mtty-char -Tascii -ms -o /usr/src/share/doc/psd/title/Title) | gzip -cn > Title.ascii.gz
troff: bad output page list
---cut---
Strange enough the build just hangs there until I do a CTRL-C
If I edit the Makefile in /usr/src/share/ and leave out the doc part
the build and install runs fine so there is nothing much wrong with the system
it seems...
Anybody have a pointer where to look...?
Sorry if i'm mis-using the wrong mailinglist.
Ron.
FreeBSD zappa.demon.nl 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Thu Nov 5 22:07:59 CET 1998
root@zappa.demon.nl:/usr/src/sys/compile/UMRK4 i386
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 06:49:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA07276
for freebsd-current-outgoing; Fri, 6 Nov 1998 06:49:59 -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 GAA07268
for <current@freebsd.org>; Fri, 6 Nov 1998 06:49:51 -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.1a/8.8.8) with ESMTP id RAA21718
for <current@freebsd.org>; Fri, 6 Nov 1998 17:50:59 +0300 (MSK)
(envelope-from tarkhil@enterprise.sl.ru)
Message-Id: <199811061450.RAA21718@enterprise.sl.ru>
X-Mailer: exmh version 2.0.2 2/24/98
To: current@FreeBSD.ORG
Reply-To: tarkhil@synchroline.ru
Subject: What is wrong?
X-URL: http://freebsd.svib.ru
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 06 Nov 1998 17:50:58 +0300
From: "Alexander B. Povolotsky" <tarkhil@synchroline.ru>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello!
on
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
attempt to run cvsup (extracted from ports/net/cvsup-binary) leads to
ELF interpreter /usr/libexec/ld-elf.so.1 not found
What can be wrong?
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 6 06:55:23 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA07571
for freebsd-current-outgoing; Fri, 6 Nov 1998 06:55:23 -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 GAA07564
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 06:55:15 -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 PAA22023; Fri, 6 Nov 1998 15:54:27 +0100 (MET)
Message-ID: <XFMail.981106155427.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
In-Reply-To: <Pine.BSF.4.05.9811060915590.756-100000@porkfriedrice.ny.genx.net>
Date: Fri, 06 Nov 1998 15:54:27 +0100 (MET)
Organization: University of bayreuth
From: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
To: Alfred Perlstein <bright@hotjobs.com>
Subject: RE: latest kernel breaks linux netscape.
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 06-Nov-98 Alfred Perlstein wrote:
> On Fri, 6 Nov 1998, Werner Griessl wrote:
>
>>
>> On 06-Nov-98 Alfred Perlstein 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 .
>> >> >
>> >> > Werner
>> >> >
>> >
>> > someone recommended i recompile my lkms/klds, i'm still aout kernel at
>> > the moment.
>> >
>> > what are we using currently for aout kernels? do ELF kernels produce
>> > a crash dump you can analyze yet?
>>
>> I can try to make an ELF kernel.
>
> no no no :) this was being asked to the -current developers :)
>
> but if you want to...
No problem, the ELF-kernel is up and running.
I installed also the new boot-blocks and removed /kernel.config.
Had also to install linux.ko and vinum.ko manually via rc.local.
Works like a charm now.
But the netscape problem still exists:
system freeze, no access to keyboard, no panic, no kernel-debugger,
but responds to ping from the net.
But now I know, that's a nfs related problem !!!
Only with nfs-homed-users the freeze occurs on netscape exit.
Any idea ?
>
>> > why wasn't this done automagically from
>> > "make buildworld ; make installworld"
>> > ?
>>
>> does it automagically !
>
> this hasn't been my experiance as of lately...
>
> -Alfred
Werner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 08:28:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA20574
for freebsd-current-outgoing; Fri, 6 Nov 1998 08:28:09 -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 IAA20512
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 08:28:06 -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 IAA01606;
Fri, 6 Nov 1998 08:28:15 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Chuck Robey <chuckr@mat.net>
cc: Mike Smith <mike@smith.net.au>, freebsd-current@FreeBSD.ORG
Subject: Re: ficl
In-reply-to: Your message of "Fri, 06 Nov 1998 06:56:48 EST."
<Pine.BSF.4.05.9811060653440.300-100000@picnic.mat.net>
Date: Fri, 06 Nov 1998 08:28:14 -0800
Message-ID: <1602.910369694@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I'm watching all your work using ficl with a lot of interest, but I
> don't understand the operating environment of programs at that early
> stage of boot too well. Is the filesystem available? Can any use be
> made of other Unix utils at all? What devices are available?
> Obviously, screen input/output is *somewhat* available, right?
You can open() files and do read() calls on them; I don't think
write() is supported yet. You can't rely on anything outside of the
bootstrap unless it can be open()'d and you certainly can't run
ordinary unix utilities from it. I'm not sure about devices and
filesystems available - that's more of a Mike/Robert question.
As far as screen I/O is concerned, you can read characters from the
keyboard and you can emit them to the console device. That's your
interface. ;) On top of that, one could probably implement a very
rudimentary screen I/O library that assumed ANSI compatability or
something and get a reasonable curses type environment.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 08:29:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA20861
for freebsd-current-outgoing; Fri, 6 Nov 1998 08:29: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 IAA20854
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 08:29:28 -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 LAA29551;
Fri, 6 Nov 1998 11:28:13 -0500 (EST)
Date: Fri, 6 Nov 1998 11:28:13 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Werner Griessl <werner@btp1da.phy.uni-bayreuth.de>
cc: Alfred Perlstein <bright@hotjobs.com>, current@FreeBSD.ORG
Subject: RE: latest kernel breaks linux netscape.
In-Reply-To: <XFMail.981106131900.werner@btp1da.phy.uni-bayreuth.de>
Message-ID: <Pine.BSF.4.05.9811061127450.29441-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
Netscape 4.5 for FreeBSD Works fine on my box at home, running -CURRENT,
but I got an odd lockup with a large xterm with ssh running....
Brian
On Fri, 6 Nov 1998, Werner Griessl wrote:
>
> On 06-Nov-98 Alfred Perlstein wrote:
> >
> > cvsup as of a few hours ago and netscape-linux gets a sigbus when starting
> > up. linux_kdump is broken on 3.0 can i do anything to show a trace?
> >
> > I totally forgot i was running linux netscape until i did a kdump and it
> > looked all odd. :)
> >
> > 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
>
> ----------------------------------
>
> 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 .
>
> Werner
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 08: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 IAA21255
for freebsd-current-outgoing; Fri, 6 Nov 1998 08:30:54 -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 IAA21233
for <freebsd-current@freebsd.org>; Fri, 6 Nov 1998 08:30:44 -0800 (PST)
(envelope-from ckempf@singularity.enigami.com)
Received: (from ckempf@localhost)
by singularity.enigami.com (8.9.1/8.9.1) id LAA04103;
Fri, 6 Nov 1998 11:30:32 -0500 (EST)
To: freebsd-current@FreeBSD.ORG
Subject: bad time slicing? Priorities?
X-Copyright: Copyright (C) 1998 Cory Kempf. All Rights Reserved
X-PGP-Fingerprint: 191E 2FB7 E27D 76C3 8E79 4D26 2B3B B20F 2A9C 1E1A
X-PGP-Keyloc: <http://www.enigami.com/pgp/> ; finger ckempf@enigami.com
From: Cory Kempf <ckempf@enigami.com>
Date: 06 Nov 1998 11:30:32 -0500
Message-ID: <x7sofwokbb.fsf@singularity.enigami.com>
Lines: 38
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I have a system running 3.0 SMP, with 2 333MHz PII's.
On this system, I am running two copies of the Bovine RSA client (rc5des)
(essentially two endless CPU bound tasks, niced down to 19)
>From top:
PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND
23593 root 105 19 832K 344K RUN 0 23.4H 98.15% 98.15% rc5des
23726 root 105 19 832K 336K CPU1 0 22.7H 97.89% 97.89% rc5des
We are not swapping, or anything else obvious.
If I run xgalaga (a game), which is being run at nice=5 for some
reason (not sure why, haven't looked into it), It doesn't seem to be
getting enough CPU time.
Play is jerky and slow.
This isn't what I expected. Expecially with two CPUs to play with.
The rc5des programs, should essentially not be running if higher
priority things are waiting to run, right? Certainly with two CPUs, I
would expect that the game would get time pretty much as soon as it
was ready to run, while the other tasks would fight over what was
left.
So, do I just not understand how BSD does its scheduling? Or is there
actually something wrong?
Thanks,
+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 Fri Nov 6 08:39:12 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA22841
for freebsd-current-outgoing; Fri, 6 Nov 1998 08:39:12 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA22829;
Fri, 6 Nov 1998 08:39:06 -0800 (PST)
(envelope-from fenner@parc.xerox.com)
Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <430726(3)>; Fri, 6 Nov 1998 08:38:50 PST
Received: from mango.parc.xerox.com (localhost.parc.xerox.com [127.0.0.1])
by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id IAA28819;
Fri, 6 Nov 1998 08:38:43 -0800 (PST)
(envelope-from fenner@mango.parc.xerox.com)
Message-Id: <199811061638.IAA28819@mango.parc.xerox.com>
To: "Dmitry Eremin" <dmiter@sci-nnov.ru>
cc: freebsd-current@FreeBSD.ORG, freebsd-bugs@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 "Fri, 06 Nov 1998 02:41:43 PST."
<000301be0972$10f05460$0200000a@winhome.sci-nnov.ru>
Date: Fri, 6 Nov 1998 08:38:43 PST
From: Bill Fenner <fenner@parc.xerox.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Did the message get printed during your tcpdump, or was the tcpdump taken
at a different time? Could you try to replicate this with both tcpdumps
running at the same time (on different screens to not intersperse the
output) and include the timestamps?
Does the ARP entry get installed correctly? i.e.
1) Does "arp 192.168.1.188" show the right MAC address?
2) Does "route get 192.168.1.188" list the correct interface?
Do you have any idea why the ARP request shows up on both interfaces?
FreeBSD doesn't send ARP requests out multiple interfaces, so perhaps
you have something funny going on at layer 2 (e.g. shared hub between
the two different networks, or a broken switch)?
Bill
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 08:41:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id IAA23101
for freebsd-current-outgoing; Fri, 6 Nov 1998 08:41: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 IAA23083
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 08:41:08 -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 LAA29726;
Fri, 6 Nov 1998 11:40:45 -0500 (EST)
Date: Fri, 6 Nov 1998 11:40:44 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Cory Kempf <ckempf@enigami.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: bad time slicing? Priorities?
In-Reply-To: <x7sofwokbb.fsf@singularity.enigami.com>
Message-ID: <Pine.BSF.4.05.9811061139160.29441-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
You don't really understand the scheduling. Nice the xgalaga to 0 or -1,
and try again. Plus, rc5des is running on BOTH CPU's (FreeBSD splits it of
course and switches them around to have the best performance), FreeBSD is
not "magic".
Brian Feldman
On 6 Nov 1998, Cory Kempf wrote:
> I have a system running 3.0 SMP, with 2 333MHz PII's.
>
> On this system, I am running two copies of the Bovine RSA client (rc5des)
> (essentially two endless CPU bound tasks, niced down to 19)
>
> >From top:
> PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND
> 23593 root 105 19 832K 344K RUN 0 23.4H 98.15% 98.15% rc5des
> 23726 root 105 19 832K 336K CPU1 0 22.7H 97.89% 97.89% rc5des
>
> We are not swapping, or anything else obvious.
>
> If I run xgalaga (a game), which is being run at nice=5 for some
> reason (not sure why, haven't looked into it), It doesn't seem to be
> getting enough CPU time.
>
> Play is jerky and slow.
>
> This isn't what I expected. Expecially with two CPUs to play with.
> The rc5des programs, should essentially not be running if higher
> priority things are waiting to run, right? Certainly with two CPUs, I
> would expect that the game would get time pretty much as soon as it
> was ready to run, while the other tasks would fight over what was
> left.
>
> So, do I just not understand how BSD does its scheduling? Or is there
> actually something wrong?
>
> Thanks,
>
> +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
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 09:01:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA25639
for freebsd-current-outgoing; Fri, 6 Nov 1998 09:01: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 JAA25634
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 09:01:47 -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 MAA13379;
Fri, 6 Nov 1998 12:03:48 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Fri, 6 Nov 1998 12:03:48 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Brian Feldman <green@unixhelp.org>
cc: Cory Kempf <ckempf@enigami.com>, freebsd-current@FreeBSD.ORG
Subject: Re: bad time slicing? Priorities?
In-Reply-To: <Pine.BSF.4.05.9811061139160.29441-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.4.05.9811061159310.756-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 Fri, 6 Nov 1998, Brian Feldman wrote:
> You don't really understand the scheduling. Nice the xgalaga to 0 or -1,
> and try again. Plus, rc5des is running on BOTH CPU's (FreeBSD splits it of
> course and switches them around to have the best performance), FreeBSD is
> not "magic".
>
> Brian Feldman
More like the fact that for every screen update you have a context switch
between the game and the X server several times a second, with 2 CPU
hungry monsters in the background they are bound to steal cycles. The
granularity of the scheduler is for interactive typing (ie. at a terminal
you wouldn't notice the 2 rc5's), not hi-rez/fast context switching gfx
games. It's something expected afaik.
-Alfred
>
> On 6 Nov 1998, Cory Kempf wrote:
>
> > I have a system running 3.0 SMP, with 2 333MHz PII's.
> >
> > On this system, I am running two copies of the Bovine RSA client (rc5des)
> > (essentially two endless CPU bound tasks, niced down to 19)
> >
> > >From top:
> > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND
> > 23593 root 105 19 832K 344K RUN 0 23.4H 98.15% 98.15% rc5des
> > 23726 root 105 19 832K 336K CPU1 0 22.7H 97.89% 97.89% rc5des
> >
> > We are not swapping, or anything else obvious.
> >
> > If I run xgalaga (a game), which is being run at nice=5 for some
> > reason (not sure why, haven't looked into it), It doesn't seem to be
> > getting enough CPU time.
> >
> > Play is jerky and slow.
> >
> > This isn't what I expected. Expecially with two CPUs to play with.
> > The rc5des programs, should essentially not be running if higher
> > priority things are waiting to run, right? Certainly with two CPUs, I
> > would expect that the game would get time pretty much as soon as it
> > was ready to run, while the other tasks would fight over what was
> > left.
> >
> > So, do I just not understand how BSD does its scheduling? Or is there
> > actually something wrong?
> >
> > Thanks,
> >
> > +C
> >
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 09:12:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA28318
for freebsd-current-outgoing; Fri, 6 Nov 1998 09:12:37 -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 JAA28286
for <current@freebsd.org>; Fri, 6 Nov 1998 09:12:29 -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 MAA01208
for <current@freebsd.org>; Fri, 6 Nov 1998 12:12:14 -0500 (EST)
Date: Fri, 6 Nov 1998 12:12:14 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: current@FreeBSD.ORG
Subject: The infamous dying daemons bug
Message-ID: <Pine.BSF.4.05.9811061149210.429-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
I've now figured out that it must be the infamous dying daemons
bug that is biting me, and pretty bad. Inetd won't run more than
a day without falling over. Sendmail and apache last longer, but
not a lot.
So, to date, what is known about the bug?
Are there people running 3.0/Current that have not encountered
this bug?
Are there any known factors in a system configuration that
aggrivate the problem? More to the point, is there anything
known to suppress the problem to any degree? Some say it was
present in 2.2.x, but I never encountered it.
Here are some relevant email postings on the topic:
http://www.freebsd.org/cgi/getmsg.cgi?fetch=2099086+2101942+/usr/local/www/db/text/1998/freebsd-current/19980920.freebsd-current
http://www.freebsd.org/cgi/getmsg.cgi?fetch=649095+653248+/usr/local/www/db/text/1998/freebsd-current/19980823.freebsd-current
http://www.freebsd.org/cgi/getmsg.cgi?fetch=786702+0+/usr/local/www/db/text/1998/freebsd-current/19980823.freebsd-current
http://www.freebsd.org/cgi/getmsg.cgi?fetch=579190+582585+/usr/local/www/db/text/1998/freebsd-current/19980823.freebsd-current
http://www.freebsd.org/cgi/getmsg.cgi?fetch=543833+547747+/usr/local/www/db/text/1998/freebsd-current/19980705.freebsd-current
And some relevant PRs:
http://www.freebsd.org/cgi/query-pr.cgi?pr=7925
http://www.freebsd.org/cgi/query-pr.cgi?pr=6858
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 09:31:51 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; Fri, 6 Nov 1998 09:31:51 -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 JAA01060
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 09:31:47 -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 SAA05469;
Fri, 6 Nov 1998 18:31:12 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id SAA04858;
Fri, 6 Nov 1998 18:31:12 +0100 (MET)
Message-ID: <19981106183112.27770@follo.net>
Date: Fri, 6 Nov 1998 18:31:12 +0100
From: Eivind Eklund <eivind@yes.no>
To: John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <Pine.BSF.4.05.9811061149210.429-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.9811061149210.429-100000@fallout.campusview.indiana.edu>; from John Fieber on Fri, Nov 06, 1998 at 12:12:14PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Nov 06, 1998 at 12:12:14PM -0500, John Fieber wrote:
> I've now figured out that it must be the infamous dying daemons
> bug that is biting me, and pretty bad. Inetd won't run more than
> a day without falling over. Sendmail and apache last longer, but
> not a lot.
>
> So, to date, what is known about the bug?
It strike when you run out of memory, usually.
> Are there people running 3.0/Current that have not encountered
> this bug?
>
> Are there any known factors in a system configuration that
> aggrivate the problem? More to the point, is there anything
> known to suppress the problem to any degree? Some say it was
> present in 2.2.x, but I never encountered it.
Run with insane amounts of swap. 2GB ought to do the trick. I'm not
guaranteeing this will stop the problem, but it will make it _much_
less frequent.
Eivind, who increased from 128MB to 256MB swap, and had the problem
almost go away...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 09:50:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA03289
for freebsd-current-outgoing; Fri, 6 Nov 1998 09:50:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03245
for <current@freebsd.org>; Fri, 6 Nov 1998 09:50:07 -0800 (PST)
(envelope-from jdp@austin.polstra.com)
Received: from austin.polstra.com (jdp@localhost)
by austin.polstra.com (8.9.1/8.9.1) with ESMTP id JAA10237;
Fri, 6 Nov 1998 09:49:37 -0800 (PST)
(envelope-from jdp)
Message-Id: <199811061749.JAA10237@austin.polstra.com>
To: asmodai@wxs.nl
Subject: Re: cvs intricities (well not really ;)
In-Reply-To: <XFMail.981105010920.asmodai@wxs.nl>
References: <XFMail.981105010920.asmodai@wxs.nl>
Organization: Polstra & Co., Seattle, WA
Cc: current@FreeBSD.ORG
Date: Fri, 06 Nov 1998 09:49:37 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <XFMail.981105010920.asmodai@wxs.nl>,
Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> wrote:
> Hi,
>
> I might have missed the obvious (again), but where can I find the most up to
> date list of which src, doc, ports etc can be mentioned in the cvsupfile for
> inclusion of the cvsup process?
The FreeBSD Handbook, around section 18.3.3.5.
--
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 Fri Nov 6 10:11:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA05935
for freebsd-current-outgoing; Fri, 6 Nov 1998 10:11:13 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.eecis.udel.edu (ntp.udel.edu [128.175.2.33])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA05928
for <current@freebsd.org>; Fri, 6 Nov 1998 10:11:11 -0800 (PST)
(envelope-from alexandr@mail.eecis.udel.edu)
Received: from ren.eecis.udel.edu by mail.eecis.udel.edu id aa10592;
6 Nov 1998 13:03 EST
To: current@FreeBSD.ORG
Subject: ThinkPad 600E
Organization: Mos Eisley Candy Store
Reply-To: alexandr@mail.eecis.udel.edu
Date: Fri, 06 Nov 1998 13:03:50 -0500
From: Jerry Alexandratos <alexandr@mail.eecis.udel.edu>
Message-ID: <199811061303.aa10592@mail.eecis.udel.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Work is getting me a new laptop. So it looks as though the 760E is
about to enter retirement.
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?
Thanks.
--Jerry
8) Jerry Alexandratos % - % "Nothing inhabits my (8
8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8
8) darkstar@strauss.udel.edu % - % drives my desires." (8
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 10:27:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA08284
for freebsd-current-outgoing; Fri, 6 Nov 1998 10:27:06 -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 KAA08279
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 10:27:04 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.58.54]) by smtp04.wxs.nl
(Netscape Messaging Server 3.6) with ESMTP id AAA13BE
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 19:26:52 +0100
Message-ID: <XFMail.981106193054.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: Fri, 06 Nov 1998 19:30:54 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: FreeBSD Current <current@FreeBSD.ORG>
Subject: YAQ (Yet Another Question)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
As part of my ever-continuing role as antagoniser for CURRENT I was wondering
about this:
Why do some options in LINT have quotes ("") and others not? In my eyes that
just isn't consistent. Or is this one of the "Shut up, it's been like that for
years" questions? =)
But seriously I am really wondering about it...
On a sidenote: make world and make kernel all go wonderwell on this box... With
the presence of some warnings and such...
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Fri Nov 6 10:32:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA09294
for freebsd-current-outgoing; Fri, 6 Nov 1998 10:32:15 -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 KAA09287
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 10:32:11 -0800 (PST)
(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
by dan.emsphone.com (8.9.1/8.9.1) id MAA22440;
Fri, 6 Nov 1998 12:31:54 -0600 (CST)
Date: Fri, 6 Nov 1998 12:31:54 -0600
From: Dan Nelson <dnelson@emsphone.com>
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>,
FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: YAQ (Yet Another Question)
Message-ID: <19981106123154.A22408@emsphone.com>
References: <XFMail.981106193054.asmodai@wxs.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.3i
In-Reply-To: <XFMail.981106193054.asmodai@wxs.nl>; from "Jeroen Ruigrok/Asmodai" on Fri Nov 6 19:30:54 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 06), Jeroen Ruigrok/Asmodai said:
> As part of my ever-continuing role as antagoniser for CURRENT I was
> wondering about this:
>
> Why do some options in LINT have quotes ("") and others not? In my
> eyes that just isn't consistent. Or is this one of the "Shut up, it's
> been like that for years" questions? =)
I think any option that has a number in it has to be in quotes.
-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 Fri Nov 6 10: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 KAA10074
for freebsd-current-outgoing; Fri, 6 Nov 1998 10:36:16 -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 KAA09989
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 10:36:05 -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 NAA09515;
Fri, 6 Nov 1998 13:35:51 -0500 (EST)
Received: from localhost (crossd@localhost)
by o2.cs.rpi.edu (8.9.1a/8.9.1) with ESMTP id NAA00811;
Fri, 6 Nov 1998 13:33:42 -0500 (EST)
X-Authentication-Warning: o2.cs.rpi.edu: crossd owned process doing -bs
Date: Fri, 6 Nov 1998 13:33:41 -0500
From: "David E. Cross" <crossd@cs.rpi.edu>
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: <19981106183112.27770@follo.net>
Message-ID: <Pine.SGI.4.05.9811061258001.810-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
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.
On Fri, 6 Nov 1998, Eivind Eklund wrote:
> It strike when you run out of memory, usually.
>
> > Are there people running 3.0/Current that have not encountered
> > this bug?
> >
> > Are there any known factors in a system configuration that
> > aggrivate the problem? More to the point, is there anything
> > known to suppress the problem to any degree? Some say it was
> > present in 2.2.x, but I never encountered it.
>
> Run with insane amounts of swap. 2GB ought to do the trick. I'm not
> guaranteeing this will stop the problem, but it will make it _much_
> less frequent.
>
> Eivind, who increased from 128MB to 256MB swap, and had the problem
> almost go away...
--
David Cross
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 10:55:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA12610
for freebsd-current-outgoing; Fri, 6 Nov 1998 10:55:36 -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 KAA12591
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 10:55:30 -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 NAA01103;
Fri, 6 Nov 1998 13:55:09 -0500 (EST)
Date: Fri, 6 Nov 1998 13:55:09 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: "David E. Cross" <crossd@cs.rpi.edu>
cc: Eivind Eklund <eivind@yes.no>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.SGI.4.05.9811061258001.810-100000@o2.cs.rpi.edu>
Message-ID: <Pine.BSF.4.05.9811061348550.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 Fri, 6 Nov 1998, David E. Cross wrote:
> 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.
If it was happening to everyone as much as it was happening to
me, I seriously doubt 3.0 would have ever reached release
status...having inetd die every 6 to 24 hours, httpd and sendmail
every couple days is pretty intolerable.
I've bumped my swap from 128 to 256 (I have 64 of real ram) and
will see how that goes...it will take a couple days to tell.
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 10:57:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id KAA12878
for freebsd-current-outgoing; Fri, 6 Nov 1998 10:57:02 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA12856
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 10:56:47 -0800 (PST)
(envelope-from wpaul@skynet.ctr.columbia.edu)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA15525; Fri, 6 Nov 1998 13:55:12 -0500
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199811061855.NAA15525@skynet.ctr.columbia.edu>
Subject: Re: Grrr... calcru: negative time blah blah blah
To: phk@critter.freebsd.dk (Poul-Henning Kamp)
Date: Fri, 6 Nov 1998 13:55:10 -0500 (EST)
Cc: current@FreeBSD.ORG
In-Reply-To: <2913.910336717@critter.freebsd.dk> from "Poul-Henning Kamp" at Nov 6, 98 08:18:37 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Of all the gin joints in all the towns in all the world, Poul-Henning
Kamp had to walk into mine and say:
> I'm still banging my head against this one. I'm working with a
> handfull of people who has this problem, trying to identify what
> the heck is happening. I can't reproduce it on any of my machines
> here.
>
> If you have an interrupt storm which could lock out hardclock()
> that will certainly screw things up badly.
>
> I have put some diagnostic patches at:
>
> http://www.freebsd.org/~phk/tc_diag.diff
>
> Please notice the patch to sysctl in there too, it is needed to
> print out all of the "delta history buffer".
>
> Please try these patches out, they will not panic the machine if
> the tests trigger, merely report some applicable details.
>
> If any of the tests trigger, please email me:
>
> /var/run/dmesg.boot
> `dmesg`
> `sysctl kern.timecounter`
> `sysctl debug`
I placed a file on ~wpaul on freefall called phk.tar.gz which contains
the information from two tests, one with the apm0 device in the kernel
(test1) and one without (test2). The behavior was the same in both
cases.
Basically all I did was boot the system and run xinit. The X server
comes partway up, then crashes with a CPU time limit expired error.
The whole dmesg is in the file. Here's part of it:
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 = 536870912 (524288K bytes)
avail memory = 520142848 (507952K 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
Probing for devices on PCI bus 0:
Devices are:
3Com 3c905B XL integrated 10/100 ethernet
Adaptec 7890/91 Ultra2 adapter
Adaptec 7880 Ultra SCSI adapter
Two QUANTUM VIKING II 9.1WLS 3506 drives on the Ultra2 controller
NEC CD-ROM DRIVE:465 1.03 on the 7880 controller
ATAPI IOMEGA ZIP on the secondary IDE controller
512MB RAM
Here are the sysctl results for test1:
sysctl kern.timecounter:
kern.timecounter.frequency: 1193182
kern.timecounter.adjustment: 0
sysctl debug:
debug.elf_trace: 0
debug.tc_diag_buffer: 11932 11932 11932 11937 11927 11931 11933 11932 11932 11931 11933 11931 11933 11932 11932 11932 11932 11932 89 740 11934 11933 11931 11930 11932 11932 11932 11932 11932 11932 11932 11931 11933 11931 11933 11932 11932 11931 11936 1192
9 11932 11932 11932 11932 11932 11932 11931 11933 11932 11932 11932 11932 11932 11932 11932 11932 11931 11932 11933 11931 11933 11931 11933 11931 11933 11931 11934 11931 11933 11930 11932 11935 11930 11932 11931 11933 11932 11932 11932 49982 50184 50259 1
1934 11930 11932 11936 11928 11932 11932 11931 11932 11933 11931 11933 11931 11933 11932 11932 11934 11930 11932 11932 11932 11932 11931 11933 11932 11928 11936 11932 11932 11932 11932 11933 11931 11932 11932 11937 11932 11927 11939 11926 11933 101 111 11
931 3356 3877 3885 5168 5189 5614 5731 5817 23370 23693 24128 24318 11936 11928 11930 11933 11932 11932 11931 11933 11932 11931 11933 73025 73176 73243 11938 11927 11931 11932 18499 18610 18682 11933 11934 11928 11932 11933 11932 11932 11932 11932 11931 1
1933 11932 11931 11933 11932 11932 11932 11932 11932 11932 11931 11933 11932 11932 11932 11932 11932 11931 11933 11932 11932 11931 11933 11932 11933 11931 11932 29733 31132 31195 11933 11936 11927 11932 11931 11932 11933 11931 11933 11931 11933 11932 1193
2 11932 11932 11932 11931 11933 11932 11932 11932 11932 11932 11932 11932 11934 11930 11933 11931 11932 11932 47338 47978 47986 48807 50401 51051 51072 51518 51730 1556 1658 1863 1950 2198 8500 8578 18966 19741 11920 11930 11931 11933 161 170 11932 11931
debug.tc_diag_index: 19695
debug.tc_diag_stop: 0
debug.tc_diag_maxforward: -30361
debug.fdexpand: 0
debug.debugger_on_panic: 1
debug.ttydebug: 0
debug.nchash: 65535
debug.ncnegfactor: 16
debug.numneg: 19
debug.numcache: 307
debug.vfscache: 1
debug.vnsize: 164
debug.ncsize: 36
debug.numvnodes: 302
debug.wantfreevnodes: 25
debug.freevnodes: 24
debug.disablecwd: 0
debug.bpf_bufsize: 4096
Here are the sysctl results for test2 (with no apm0 device):
sysctl kern.timecounter:
kern.timecounter.frequency: 1193182
kern.timecounter.adjustment: 0
sysctl debug:
debug.elf_trace: 0
debug.tc_diag_buffer: 11932 11932 11932 11932 11931 11933 11933 11933 11930 11931 11933 11932 11932 11932 11933 11931 11932 11931 11934 11933 11932 11930 11932 11931 11934 11931 11933 11931 11932 11932 11932 11933 11931 11931 11933 37 45 11932 11933 11931
11932 11933 11933 11934 11928 11936 11927 11933 11932 11932 11932 11932 11932 11931 11936 11929 11933 11931 11934 11931 11931 11932 11932 11932 11933 11931 11932 11934 11928 11934 11932 11933 11931 11933 11932 11933 11930 11936 11928 11936 11933 11929 11
930 11936 11933 11927 44950 45524 45532 46430 48518 49258 49280 49747 49873 11933 11930 11932 11933 11931 11932 11932 11932 11936 11928 11932 11933 11932 11936 11928 11931 11936 11928 11932 11933 11931 11932 11932 11932 11932 11931 11933 11931 11933 11932
11932 11931 11933 11935 11931 11930 11933 11931 11931 11933 11932 11932 11932 11932 11932 11933 11931 11933 11931 11933 11934 11930 11933 11930 11933 11931 11932 11933 11931 11931 11933 11931 11933 11933 11931 11933 11934 11929 11937 11927 11933 11931 11
932 11933 11935 11929 11931 11936 11932 11928 11932 11932 11933 11932 11931 11932 11933 11931 11934 11931 11933 11931 11932 59 68 77 11932 11931 11932 11932 11932 11932 11934 11930 11932 11935 11929 11934 11930 11932 11932 11932 11932 11932 11932 11932 11
931 11933 11932 11932 11933 11931 11932 11936 11928 11933 11936 11927 11932 11931 11933 11933 11932 11931 11933 11934 11933 11928 11932 11932 11932 11932 11932 11932 11932 11932 11932 11933 11931 11932 11932 11932 11932 11932 11935 11930 11931 11932 11932
11933 11931
debug.tc_diag_index: 26463
debug.tc_diag_stop: 0
debug.tc_diag_maxforward: -41672
debug.fdexpand: 0
debug.debugger_on_panic: 1
debug.ttydebug: 0
debug.nchash: 65535
debug.ncnegfactor: 16
debug.numneg: 18
debug.numcache: 302
debug.vfscache: 1
debug.vnsize: 164
debug.ncsize: 36
debug.numvnodes: 309
debug.wantfreevnodes: 25
debug.freevnodes: 24
debug.disablecwd: 0
debug.bpf_bufsize: 4096
I don't know what any of these numbers mean. If you need me to run more
tests, let me know.
-Bill
--
=============================================================================
-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu
Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
"It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=============================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 11:00:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA13452
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:00:46 -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 LAA13422
for <current@freebsd.org>; Fri, 6 Nov 1998 11:00:41 -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 WAA01279
for <current@freebsd.org>; Fri, 6 Nov 1998 22:01:46 +0300 (MSK)
(envelope-from tarkhil@enterprise.sl.ru)
Message-Id: <199811061901.WAA01279@enterprise.sl.ru>
To: current@FreeBSD.ORG
Reply-To: tarkhil@synchroline.ru
Subject: Problem with dummynet on RELEASE
X-URL: http://freebsd.svib.ru
Date: Fri, 06 Nov 1998 22:01:46 +0300
From: "Alexander B. Povolotsky" <tarkhil@synchroline.ru>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hello!
dummynet patch added references to two include files, opt_bdg.h and
opt_ipdn.h. Where should I find them?...
Alex.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 11:00:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA13523
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:00:56 -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 LAA13507
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 11:00:54 -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 KAA02829;
Fri, 6 Nov 1998 10:59:48 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: John Fieber <jfieber@indiana.edu>
cc: "David E. Cross" <crossd@cs.rpi.edu>, Eivind Eklund <eivind@yes.no>,
current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-reply-to: Your message of "Fri, 06 Nov 1998 13:55:09 EST."
<Pine.BSF.4.05.9811061348550.482-100000@fallout.campusview.indiana.edu>
Date: Fri, 06 Nov 1998 10:59:48 -0800
Message-ID: <2826.910378788@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> If it was happening to everyone as much as it was happening to
> me, I seriously doubt 3.0 would have ever reached release
> status...having inetd die every 6 to 24 hours, httpd and sendmail
> every couple days is pretty intolerable.
Have you tried that new inetd.c replacement that was posted awhile
back? I'm just wondering if it affects the problem. David's looked
at this one a bit and he can neither reproduce it nor come up with any
good ideas right now as to how to go about fixing it.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 11:02:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA13904
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:02:29 -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 LAA13503
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 11:00:54 -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 UAA06343;
Fri, 6 Nov 1998 20:00:29 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id UAA05256;
Fri, 6 Nov 1998 20:00:28 +0100 (MET)
Message-ID: <19981106200028.23174@follo.net>
Date: Fri, 6 Nov 1998 20:00:28 +0100
From: Eivind Eklund <eivind@yes.no>
To: "David E. Cross" <crossd@cs.rpi.edu>
Cc: John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <19981106183112.27770@follo.net> <Pine.SGI.4.05.9811061258001.810-100000@o2.cs.rpi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <Pine.SGI.4.05.9811061258001.810-100000@o2.cs.rpi.edu>; from David E. Cross on Fri, Nov 06, 1998 at 01:33:41PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Nov 06, 1998 at 01:33:41PM -0500, David E. Cross wrote:
>
> 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.
David committed some patches a while back that he said _might_ help it
- I've not yet upgraded to test this.
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 11:02:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA13966
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:02:59 -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 LAA13956
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 11:02:57 -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 OAA13520;
Fri, 6 Nov 1998 14:05:12 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Fri, 6 Nov 1998 14:05:12 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: "David E. Cross" <crossd@cs.rpi.edu>
cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.SGI.4.05.9811061258001.810-100000@o2.cs.rpi.edu>
Message-ID: <Pine.BSF.4.05.9811061404280.756-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
"Not I." said the 3.0-current user.
-Alfred
On Fri, 6 Nov 1998, David E. Cross wrote:
>
> 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.
>
> On Fri, 6 Nov 1998, Eivind Eklund wrote:
>
> > It strike when you run out of memory, usually.
> >
> > > Are there people running 3.0/Current that have not encountered
> > > this bug?
> > >
> > > Are there any known factors in a system configuration that
> > > aggrivate the problem? More to the point, is there anything
> > > known to suppress the problem to any degree? Some say it was
> > > present in 2.2.x, but I never encountered it.
> >
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 11:06:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA14375
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:06:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA14367
for <current@freebsd.org>; Fri, 6 Nov 1998 11:06:34 -0800 (PST)
(envelope-from wpaul@skynet.ctr.columbia.edu)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id OAA15554; Fri, 6 Nov 1998 14:05:08 -0500
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199811061905.OAA15554@skynet.ctr.columbia.edu>
Subject: Re: Grrr... calcru: negative time blah blah blah
To: phk@critter.freebsd.dk (Poul-Henning Kamp)
Date: Fri, 6 Nov 1998 14:05:07 -0500 (EST)
Cc: current@FreeBSD.ORG
In-Reply-To: <2913.910336717@critter.freebsd.dk> from "Poul-Henning Kamp" at Nov 6, 98 08:18:37 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Of all the gin joints in all the towns in all the world, Poul-Henning
Kamp had to walk into mine and say:
> I'm still banging my head against this one. I'm working with a
> handfull of people who has this problem, trying to identify what
> the heck is happening. I can't reproduce it on any of my machines
> here.
>
> If you have an interrupt storm which could lock out hardclock()
> that will certainly screw things up badly.
>
> I have put some diagnostic patches at:
>
> http://www.freebsd.org/~phk/tc_diag.diff
>
> Please notice the patch to sysctl in there too, it is needed to
> print out all of the "delta history buffer".
>
> Please try these patches out, they will not panic the machine if
> the tests trigger, merely report some applicable details.
Actually, looking at the patch closer, I realize now that none of the
warning messages actually triggered. However each time, the calcru
messages did appear and the system console response became sluggish.
I'm starting to think the problem in this case is an interrupt storm,
but I'm not sure how to debug it. If I set up a second system to do
a remote gdb of the first one, can I single step through things like
interrupt handlers without Weird Things (tm) happening?
-Bill
--
=============================================================================
-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu
Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
"It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=============================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 11:21:27 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA16471
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:21:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m2-54-dbn.dial-up.net [196.34.155.118])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16461
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 11:21:19 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id VAA02364; Fri, 6 Nov 1998 21:19:07 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199811061919.VAA02364@ceia.nordier.com>
Subject: Re: ficl
In-Reply-To: <1602.910369694@time.cdrom.com> from "Jordan K. Hubbard" at "Nov 6, 98 08:28:14 am"
To: chuckr@mat.net (Chuck Robey)
Date: Fri, 6 Nov 1998 21:18:58 +0200 (SAT)
Cc: jkh@time.cdrom.com, 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
Jordan K. Hubbard wrote:
> > I'm watching all your work using ficl with a lot of interest, but I
> > don't understand the operating environment of programs at that early
> > stage of boot too well. Is the filesystem available? Can any use be
> > made of other Unix utils at all? What devices are available?
> > Obviously, screen input/output is *somewhat* available, right?
>
> You can open() files and do read() calls on them; I don't think
> write() is supported yet. You can't rely on anything outside of the
> bootstrap unless it can be open()'d and you certainly can't run
> ordinary unix utilities from it. I'm not sure about devices and
> filesystems available - that's more of a Mike/Robert question.
Really more Mike's area than mine, which is mostly the low-level
i386 stuff.
Devices: Apart from video and serial consoles, disk and net devices
are currently provided for. Though, at least on the i386, it should
be reasonably easy to add access to anything that has BIOS or other
firmware support.
Filesystems: cd9960, dosfs, nfs, and ufs; as well as zipfs and
tftp. Adding read-only support for a local filesystem needs ~700
lines of C at the moment.
--
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 6 11:26:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA16953
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:26:53 -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 LAA16948
for <freebsd-current@freebsd.org>; Fri, 6 Nov 1998 11:26:51 -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 0zbrVP-0006OJ-00; Fri, 6 Nov 1998 11:25:11 -0800
Date: Fri, 6 Nov 1998 11:25:09 -0800 (PST)
From: Tom <tom@uniserve.com>
X-Sender: tom@shell.uniserve.ca
To: Brian Feldman <green@unixhelp.org>
cc: Cory Kempf <ckempf@enigami.com>, freebsd-current@FreeBSD.ORG
Subject: Re: bad time slicing? Priorities?
In-Reply-To: <Pine.BSF.4.05.9811061139160.29441-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.4.02A.9811061122280.8479-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 Fri, 6 Nov 1998, Brian Feldman wrote:
> You don't really understand the scheduling. Nice the xgalaga to 0 or -1,
> and try again. Plus, rc5des is running on BOTH CPU's (FreeBSD splits it of
> course and switches them around to have the best performance), FreeBSD is
> not "magic".
>
> Brian Feldman
Yes, and rc5des should probably be run under idprio. No matter how much
you "nice" a process it will still be run, even if other processes are
waiting. Howerver, a idprio process only runs when idle. A idprio
process may never run at all if your system never has idle time.
Tom
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 11:28:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA17200
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:28:09 -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 LAA17184
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 11:28:01 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id UAA05112;
Fri, 6 Nov 1998 20:26:03 +0100 (CET)
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
cc: current@FreeBSD.ORG
Subject: Re: Grrr... calcru: negative time blah blah blah
In-reply-to: Your message of "Fri, 06 Nov 1998 13:55:10 EST."
<199811061855.NAA15525@skynet.ctr.columbia.edu>
Date: Fri, 06 Nov 1998 20:26:00 +0100
Message-ID: <5110.910380360@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
The numbers in the tc_diag_buffer are basically the number of ticks
on the timecounter between each use of it.
>Timecounter "i8254" frequency 1193182 Hz
Normally, the largest number of ticks should be the frequency of
the timecounter divided by 100, in this case 11931, (plus or minus
epsilon).
When smaller counts are in the buffer it means that one of the *time()
functions were called, so that is normal.
>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.
Further bogosity:
>[...] 5817 23370 23693 24128 24318 11936 [...]
>[...] 11932 29733 31132 31195 11933 [...]
>[...] 11932 47338 47978 47986 48807 50401 51051 51072 51518 51730 1556
>1658 1863 1950 2198 8500 8578 18966 19741 11920 11930 11931 11933 161
>170 11932 11931 [...]
>Here are the sysctl results for test2 (with no apm0 device):
>kern.timecounter.frequency: 1193182
Which didn't make a difference for SMP, since we always use the i8254
>debug.tc_diag_buffer: [...]
>[...] 11927 44950 45524 45532 46430 48518 49258 49280 49747 49873 11933 [...]
Neither of the two tests seems to have triggered any of my tests
since "debug.tc_diag_stop" is still zero.
This is consistent with a model of "lost interrupts", which I think the
above data support. A "reading the i8254 wrong" theory doesn't match
the values you have here, more +/- 256 values should have been present.
Does the problem also exist for a !SMP case ?
--
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 Fri Nov 6 11:32:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA17471
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:32: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 LAA17451
for <current@freebsd.org>; Fri, 6 Nov 1998 11:32:00 -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 UAA05142;
Fri, 6 Nov 1998 20:30:23 +0100 (CET)
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
cc: current@FreeBSD.ORG
Subject: Re: Grrr... calcru: negative time blah blah blah
In-reply-to: Your message of "Fri, 06 Nov 1998 14:05:07 EST."
<199811061905.OAA15554@skynet.ctr.columbia.edu>
Date: Fri, 06 Nov 1998 20:30:23 +0100
Message-ID: <5140.910380623@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>Actually, looking at the patch closer, I realize now that none of the
>warning messages actually triggered. However each time, the calcru
>messages did appear and the system console response became sluggish.
>
>I'm starting to think the problem in this case is an interrupt storm,
>but I'm not sure how to debug it.
(Already answered in more detail), but yes, this sounds very probable
for this (and maybe other cases as well).
The difference between the timecounter code and the previous "tick++"
code is that the former would just loose track of 10 msec per lost
hardclock(), whereas the timecounter code fails less gracefully.
I have no good advise on debugging a problem like this, except to
try to disable the interrupt in hardware. We're talking video card,
right ? Cut the trace on the board, you don't need that interrupt...
--
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 Fri Nov 6 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 LAA19743
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:47:38 -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 LAA19734
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 11:47:36 -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 LAA03055;
Fri, 6 Nov 1998 11:47:10 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Robert Nordier <rnordier@nordier.com>
cc: chuckr@mat.net (Chuck Robey), mike@smith.net.au,
freebsd-current@FreeBSD.ORG
Subject: Re: ficl
In-reply-to: Your message of "Sat, 06 Nov 1998 21:18:58 +0200."
<199811061919.VAA02364@ceia.nordier.com>
Date: Fri, 06 Nov 1998 11:47:09 -0800
Message-ID: <3051.910381629@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Devices: Apart from video and serial consoles, disk and net devices
> are currently provided for. Though, at least on the i386, it should
> be reasonably easy to add access to anything that has BIOS or other
> firmware support.
Hmmm. CDs must be a bitch, however, since they're not mapped into the
BIOS drive list. Do you support talking to them outside of the El
Torrito bios hack? I'm not really sure what you mean by "net devices"
either - how does one configure and use a typical NIC from the BTX
environment?
> Filesystems: cd9960, dosfs, nfs, and ufs; as well as zipfs and
> tftp. Adding read-only support for a local filesystem needs ~700
> lines of C at the moment.
Could you perhaps say a few words on the filename space issues around
this?
Let's say I have the following scenario: I've booted the loader off a
floppy on a system which also has 2 hard drives, one of which has a
DOS file system on it and a FreeBSD partition, the other being devoted
solely to FreeBSD. I also have a SCSI CDROM and a PCI network adaptor
(call it a DECchip NIC, just for arguments sake) in the machine.
In this environment, what exactly are my options? I know I can
open /foo/bar in order to grab /foo/bar off the floppy, but what
about the DOS partition? The FreeBSD root filesystem? An NFS or
TFTP host? Questions questions! :-)
Thanks!
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 11:50:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA20223
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:50:22 -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 LAA20199
for <current@freebsd.org>; Fri, 6 Nov 1998 11:50:11 -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 0zbrtL-0004Zk-00; Fri, 6 Nov 1998 19:49:56 +0000
Received: by WGP01 with Internet Mail Service (5.5.1960.3)
id <W2PQAPB3>; Fri, 6 Nov 1998 08:56:45 -0000
Message-ID: <32BABEF63EAED111B2C5204C4F4F5020180A@WGP01>
From: James Mansion <james@westongold.com>
To: Ville-Pertti Keinonen <will@iki.fi>,
James Mansion
<james@westongold.com>
Cc: current@FreeBSD.ORG
Subject: RE: Kernel threading (was Re: Thread Scheduler bug)
Date: Fri, 6 Nov 1998 08:56:36 -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
> From: Ville-Pertti Keinonen [mailto:will@iki.fi]
> Subject: Re: Kernel threading (was Re: Thread Scheduler bug)
>
> James Mansion <james@westongold.com> writes:
>
> > This is how OS/2 (at least) handles thread specific data,
>
> It's a kludge.
>
...
>
> Entering and leaving the kernel is expensive, it would certainly not
> be faster.
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.
Given that we only really need a single pointer, then adjusting a well-
known location in the currently executing kernel thread when it changes
its binding to a user thread (whether this change is instigated by the
kernel scheduler or the user-land part of the thread library) is fine
and I feel stupid that it hadn't occurred to me before. ;-)
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.
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.
But, an ABI change that banished a difference between libc and libc_r
and meant that I could write a thread-hot library subsystem without
inflicting thread-aware compiles and links on the whole process would
be a Good Thing IMO, and while this doesn't necessarily follow it would
at least start to look more realistic.
>
> Non-Unix-like synchronization semantics can easily break the level of
> isolation of Unix processes that makes them manageable.
>
Huh? I'm asking for pthread_*_[sg]etpshared, for P1003.1-1996. Are you
objecting to them in principal?
I can see some problems (say, can I close and reopen a mapped file which
has an inter-process synch object in it and expect it to work?) but even
if there are fairly stringent limits on the lifetimes they're still
useful.
James
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 11:50:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA20257
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:50:31 -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 LAA20217
for <current@freebsd.org>; Fri, 6 Nov 1998 11:50:21 -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 0zbrtQ-0004aG-00; Fri, 6 Nov 1998 19:50:00 +0000
Received: by WGP01 with Internet Mail Service (5.5.1960.3)
id <V08CSWPF>; Wed, 4 Nov 1998 09:16:11 -0000
Message-ID: <32BABEF63EAED111B2C5204C4F4F50201807@WGP01>
From: James Mansion <james@westongold.com>
To: Julian Elischer <julian@whistle.com>,
Daniel Eischen
<eischen@vigrid.com>
Cc: James Mansion <james@westongold.com>, peter@netplex.com.au,
current@FreeBSD.ORG, jb@cimlogic.com.au, lists@tar.com
Subject: RE: Kernel threading (was Re: Thread Scheduler bug)
Date: Wed, 4 Nov 1998 09:16:11 -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
Hmm - why does the page need to be 'swapped out'? Can't it
just be swapped into another part of the processes' existing
space by frigging the mapping when the thread becomes scheduled?
After all, each (user land) thread already has a stack area
malloced or otherwise mapped into the address space.
If you would rather just have a single pointer that's changed
on a schedule, and the pointer has a well-known address, then
fine.
My understanding is that on some systems the thread's private
data is accessed via value stored in a reserved register. I
think that would be a mistake on an x86 where the number of
registers is quite small, unless one of the segment base
registers could be reserved without stuffing compilers, ABIs
etc.
Thread rescheduling should happen relatively infrequently
compared to access to the thread-specific data.
(I'm only here because I'm trying to guage whether it is worth
trying to support FreeBSD as a reference SMP/threaded platform,
so I'll not pretend any kernel (or ABI, or ...) expertise. I
just need pthread_*, aio_*, and lio_* to work as advertised and
be fast. Oh, and thread-safe STL and exception handling.)
James
> -----Original Message-----
> From: Julian Elischer [mailto:julian@whistle.com]
>...
> if you make the threads have differnt pages, then either the
> addres space
> needs to be 'munged' on each reschedule (where is the page
> swapped out to
> since where it's swapped to depends on the object mapped into
> the address
> space), or you need to have multiple different address spaces
> sharing a lot of 'objects' which is a lot less efficient.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 11:50:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA20258
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:50:32 -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 LAA20218
for <current@freebsd.org>; Fri, 6 Nov 1998 11:50:21 -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 0zbrtO-0004aG-00; Fri, 6 Nov 1998 19:49:58 +0000
Received: by WGP01 with Internet Mail Service (5.5.1960.3)
id <V08CSWP1>; Wed, 4 Nov 1998 09:03:12 -0000
Message-ID: <32BABEF63EAED111B2C5204C4F4F50201806@WGP01>
From: James Mansion <james@westongold.com>
To: Daniel Eischen <eischen@vigrid.com>,
James Mansion
<james@westongold.com>, peter@netplex.com.au
Cc: current@FreeBSD.ORG, jb@cimlogic.com.au, lists@tar.com
Subject: RE: Kernel threading (was Re: Thread Scheduler bug)
Date: Wed, 4 Nov 1998 09:03:10 -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
Perhaps I'm being very dense, but you'll have to explain to me what
you are concerned about here.
*My* concern is that pthread_self, and access to thread-specific data,
should be as fast as possible. Writing thread-hot libraries without
good thread specific data is irksome to say the least.
I'd guess that each 'kernel thread' would benefit from a private page
too.
James
> -----Original Message-----
> From: Daniel Eischen [mailto:eischen@vigrid.com]
>...
> > I'd like to suggest that threads (at least kernel threads)
> > should share an address space EXCEPT for a page (or maybe
> > more than one) that will have a common address in each thread.
>
> What about same process threads executing on multiple processors?
>
> common_address[MAX_CPUS] ?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 11:56:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA21527
for freebsd-current-outgoing; Fri, 6 Nov 1998 11:56:38 -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 LAA21474
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 11:56:15 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.58.164])
by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA5486; Fri, 6 Nov 1998 20:53:26 +0100
Message-ID: <XFMail.981106205728.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: <199811061749.JAA10237@austin.polstra.com>
Date: Fri, 06 Nov 1998 20:57:28 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: John Polstra <jdp@polstra.com>
Subject: Re: cvs intricities (well not really ;)
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 06-Nov-98 John Polstra wrote:
> In article <XFMail.981105010920.asmodai@wxs.nl>,
> Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> wrote:
>> Hi,
>>
>> I might have missed the obvious (again), but where can I find the most up to
>> date list of which src, doc, ports etc can be mentioned in the cvsupfile for
>> inclusion of the cvsup process?
>
> The FreeBSD Handbook, around section 18.3.3.5.
Cheers mate!
thanks... (slapping forehead repeatedly whilst saying: "D'oh")
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Fri Nov 6 12:00:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA22065
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:00: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 MAA22059
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:00:17 -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 LAA00404;
Fri, 6 Nov 1998 11:59:29 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811061959.LAA00404@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: YAQ (Yet Another Question)
In-reply-to: Your message of "Fri, 06 Nov 1998 19:30:54 +0100."
<XFMail.981106193054.asmodai@wxs.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 06 Nov 1998 11:59:28 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> As part of my ever-continuing role as antagoniser for CURRENT I was wondering
> about this:
>
> Why do some options in LINT have quotes ("") and others not? In my eyes that
> just isn't consistent. Or is this one of the "Shut up, it's been like that for
> years" questions? =)
The ones that don't have quotes take advantage of a misfeature of
config(8). They should all have quotes.
--
\\ 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 6 12:03:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA22741
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:03:56 -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 MAA22724
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:03:49 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.58.164])
by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA2DBC; Fri, 6 Nov 1998 21:03:30 +0100
Message-ID: <XFMail.981106210732.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: <199811061959.LAA00404@dingo.cdrom.com>
Date: Fri, 06 Nov 1998 21:07:32 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Mike Smith <mike@smith.net.au>
Subject: Re: YAQ (Yet Another Question)
Cc: FreeBSD Current <current@FreeBSD.ORG>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 06-Nov-98 Mike Smith wrote:
>> Why do some options in LINT have quotes ("") and others not? In my eyes that
>> just isn't consistent. Or is this one of the "Shut up, it's been like that
>> for
>> years" questions? =)
>
> The ones that don't have quotes take advantage of a misfeature of
> config(8). They should all have quotes.
Then my obviously (dumb) to be expected question is, can that be changed?
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Fri Nov 6 12:10:44 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA24427
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:10:44 -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 MAA24418
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:10:42 -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 MAA00446;
Fri, 6 Nov 1998 12:04:30 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811062004.MAA00446@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
cc: phk@critter.freebsd.dk (Poul-Henning Kamp), current@FreeBSD.ORG
Subject: Re: Grrr... calcru: negative time blah blah blah
In-reply-to: Your message of "Fri, 06 Nov 1998 14:05:07 EST."
<199811061905.OAA15554@skynet.ctr.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 06 Nov 1998 12:04:30 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> I'm starting to think the problem in this case is an interrupt storm,
> but I'm not sure how to debug it. If I set up a second system to do
> a remote gdb of the first one, can I single step through things like
> interrupt handlers without Weird Things (tm) happening?
Throw in a hack to register null interrupt handlers for all the free
interrupts, then watch the interrupt stats.
--
\\ 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 6 12:13:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA24834
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:13:24 -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 MAA24826
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:13:21 -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 MAA03287;
Fri, 6 Nov 1998 12:13:33 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: Mike Smith <mike@smith.net.au>, FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: YAQ (Yet Another Question)
In-reply-to: Your message of "Fri, 06 Nov 1998 21:07:32 +0100."
<XFMail.981106210732.asmodai@wxs.nl>
Date: Fri, 06 Nov 1998 12:13:33 -0800
Message-ID: <3284.910383213@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Then my obviously (dumb) to be expected question is, can that be changed?
Assuming someone was willing to do the work, sure - "it's only a
matter of coding." Do I see a volunteer over there in Holland? :)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 12:14:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA25136
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:14:37 -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 MAA25128
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:14:33 -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 MAA00524;
Fri, 6 Nov 1998 12:13:06 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811062013.MAA00524@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
cc: Mike Smith <mike@smith.net.au>, FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: YAQ (Yet Another Question)
In-reply-to: Your message of "Fri, 06 Nov 1998 21:07:32 +0100."
<XFMail.981106210732.asmodai@wxs.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 06 Nov 1998 12:13:06 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On 06-Nov-98 Mike Smith wrote:
> >> Why do some options in LINT have quotes ("") and others not? In my eyes that
> >> just isn't consistent. Or is this one of the "Shut up, it's been like that
> >> for
> >> years" questions? =)
> >
> > The ones that don't have quotes take advantage of a misfeature of
> > config(8). They should all have quotes.
>
> Then my obviously (dumb) to be expected question is, can that be changed?
We have the .45 in config(8)'s mouth. No point in major exterior
surgery at this point in time.
--
\\ 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 6 12:20:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA26159
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:20:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26151
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:20:38 -0800 (PST)
(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
by pcnet1.pcnet.com (8.8.7/PCNet) id PAA12622;
Fri, 6 Nov 1998 15:20:17 -0500 (EST)
Date: Fri, 6 Nov 1998 15:20:17 -0500 (EST)
From: Daniel Eischen <eischen@vigrid.com>
Message-Id: <199811062020.PAA12622@pcnet1.pcnet.com>
To: eischen@vigrid.com, james@westongold.com, peter@netplex.com.au
Subject: RE: Kernel threading (was Re: Thread Scheduler bug)
Cc: current@FreeBSD.ORG, jb@cimlogic.com.au, lists@tar.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Perhaps I'm being very dense, but you'll have to explain to me what
> you are concerned about here.
>
> *My* concern is that pthread_self, and access to thread-specific data,
> should be as fast as possible. Writing thread-hot libraries without
> good thread specific data is irksome to say the least.
My point was that you can't have just one common pointer (address)
to TSD that is changed on thread schedule as it would limit you
to being able to execute only one thread per process at a time.
To take advantage of multiple processors, you'd need at least
as many TSD pointers as CPUs. Julian discussed this in a previous
response.
> I'd guess that each 'kernel thread' would benefit from a private page
> too.
>
> James
>
> > -----Original Message-----
> > From: Daniel Eischen [mailto:eischen@vigrid.com]
> >...
> > > I'd like to suggest that threads (at least kernel threads)
> > > should share an address space EXCEPT for a page (or maybe
> > > more than one) that will have a common address in each thread.
> >
> > What about same process threads executing on multiple processors?
> >
> > common_address[MAX_CPUS] ?
Dan Eischen
eischen@vigrid.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 6 12:21:35 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA26248
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:21:35 -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 MAA26235
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:21:31 -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 MAA03409;
Fri, 6 Nov 1998 12:21:47 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Mike Smith <mike@smith.net.au>
cc: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>,
FreeBSD Current <current@FreeBSD.ORG>
Subject: Re: YAQ (Yet Another Question)
In-reply-to: Your message of "Fri, 06 Nov 1998 12:13:06 PST."
<199811062013.MAA00524@dingo.cdrom.com>
Date: Fri, 06 Nov 1998 12:21:47 -0800
Message-ID: <3406.910383707@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> We have the .45 in config(8)'s mouth. No point in major exterior
> surgery at this point in time.
Hmmm, that's another good point. Ignore my previous arrow fired at
Jeroen - he can volunteer to do whatever next issue he raises
instead. :-)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 12:29:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA27144
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:29:16 -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 MAA27139
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:29:15 -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 MAA00622;
Fri, 6 Nov 1998 12:26:37 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811062026.MAA00622@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: Robert Nordier <rnordier@nordier.com>, chuckr@mat.net (Chuck Robey),
mike@smith.net.au, freebsd-current@FreeBSD.ORG
Subject: Re: ficl
In-reply-to: Your message of "Fri, 06 Nov 1998 11:47:09 PST."
<3051.910381629@time.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 06 Nov 1998 12:26:36 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > Devices: Apart from video and serial consoles, disk and net devices
> > are currently provided for. Though, at least on the i386, it should
> > be reasonably easy to add access to anything that has BIOS or other
> > firmware support.
>
> Hmmm. CDs must be a bitch, however, since they're not mapped into the
> BIOS drive list. Do you support talking to them outside of the El
> Torrito bios hack?
There's no CD support on the i386 at the moment, and not likely to be
for some time; we'd have to grow an ATAPI driver and probably drivers
for the Adaptec and NCR SCSI BIOS interfaces too.
> I'm not really sure what you mean by "net devices"
> either - how does one configure and use a typical NIC from the BTX
> environment?
BTX has nothing to do with it. Again, there's no low-level NIC support
in the i386 code at the moment, but basically you provide a low-level
hardware driver, and then the IP stack in lib stand does the Bootp
Thing. From there, it's just another device, eg.
'load net:/kernel'
will do "what you expect it to do".
> > Filesystems: cd9960, dosfs, nfs, and ufs; as well as zipfs and
> > tftp. Adding read-only support for a local filesystem needs ~700
> > lines of C at the moment.
>
> Could you perhaps say a few words on the filename space issues around
> this?
>
> Let's say I have the following scenario: I've booted the loader off a
> floppy on a system which also has 2 hard drives, one of which has a
> DOS file system on it and a FreeBSD partition, the other being devoted
> solely to FreeBSD. I also have a SCSI CDROM and a PCI network adaptor
> (call it a DECchip NIC, just for arguments sake) in the machine.
> In this environment, what exactly are my options? I know I can
> open /foo/bar in order to grab /foo/bar off the floppy, but what
> about the DOS partition? The FreeBSD root filesystem? An NFS or
> TFTP host? Questions questions! :-)
If we assume that the first disk is all DOS, and the second is half DOS
and half FreeBSD, you'll have devices like this:
disk0: Floppy.
disk1s1: DOS partition on first disk.
disk2s1: DOS partition on second disk.
disk2s2a: FreeBSD root filesystem.
...
net: Root of TFTP space on TFTP server or NFS mount.
I'm not optomistic about CDROMs in the short term; there's a *lot* of
work there. It's possible that we can use the Forth support to write
loadable BIOS interface routines, which will keep code size down.
The "which network filesystem do you use" issue is unsubtle; the code
will simply run down the list of filesystems, passing them the pathname
until it succeeds or falls off the end. This means that ordering is
significant. There's room for improvement here, but one thing at a
time.
--
\\ 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 6 12:32:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA27681
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:32:40 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27664
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:32:34 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.58.164])
by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA51C2; Fri, 6 Nov 1998 21:32:19 +0100
Message-ID: <XFMail.981106213622.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: <3284.910383213@time.cdrom.com>
Date: Fri, 06 Nov 1998 21:36:22 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: YAQ (Yet Another Question)
Cc: FreeBSD Current <current@FreeBSD.ORG>, Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 06-Nov-98 Jordan K. Hubbard wrote:
>> Then my obviously (dumb) to be expected question is, can that be changed?
>
> Assuming someone was willing to do the work, sure - "it's only a
> matter of coding." Do I see a volunteer over there in Holland? :)
Dunno how much knowledge of C it requires? =)
Getting my C up to par again after a 2-3 year hiat(sp?)
But I am willing to look into it if it's ok with you guys?
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Fri Nov 6 12:32:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA27682
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:32:41 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27666
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:32:38 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.58.164])
by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA51BB; Fri, 6 Nov 1998 21:32:17 +0100
Message-ID: <XFMail.981106213619.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: <199811062013.MAA00524@dingo.cdrom.com>
Date: Fri, 06 Nov 1998 21:36:19 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Mike Smith <mike@smith.net.au>
Subject: Re: YAQ (Yet Another Question)
Cc: FreeBSD Current <current@FreeBSD.ORG>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 06-Nov-98 Mike Smith wrote:
>> On 06-Nov-98 Mike Smith wrote:
>> > The ones that don't have quotes take advantage of a misfeature of
>> > config(8). They should all have quotes.
>>
>> Then my obviously (dumb) to be expected question is, can that be changed?
>
> We have the .45 in config(8)'s mouth. No point in major exterior
> surgery at this point in time.
ROFL, aside from being techjunks ye people also crack up me at times... =)
Mayhaps I can take a peek at it...
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Fri Nov 6 12: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 MAA27872
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:34:21 -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 MAA27859
for <current@freebsd.org>; Fri, 6 Nov 1998 12:34:18 -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 UAA28492;
Fri, 6 Nov 1998 20:28:00 GMT
Date: Fri, 6 Nov 1998 20:28:00 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: Bill Paul <wpaul@skynet.ctr.columbia.edu>, current@FreeBSD.ORG
Subject: Re: Grrr... calcru: negative time blah blah blah
In-Reply-To: <5140.910380623@critter.freebsd.dk>
Message-ID: <Pine.BSF.4.01.9811062027030.19324-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, 6 Nov 1998, Poul-Henning Kamp wrote:
>
> >Actually, looking at the patch closer, I realize now that none of the
> >warning messages actually triggered. However each time, the calcru
> >messages did appear and the system console response became sluggish.
> >
> >I'm starting to think the problem in this case is an interrupt storm,
> >but I'm not sure how to debug it.
>
> (Already answered in more detail), but yes, this sounds very probable
> for this (and maybe other cases as well).
>
> The difference between the timecounter code and the previous "tick++"
> code is that the former would just loose track of 10 msec per lost
> hardclock(), whereas the timecounter code fails less gracefully.
>
> I have no good advise on debugging a problem like this, except to
> try to disable the interrupt in hardware. We're talking video card,
> right ? Cut the trace on the board, you don't need that interrupt...
Don't do that if you ever want to use this card for 3D graphics. The
3Dlabs cards work best when doing interrupt driven DMA for 3D.
--
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 6 12:34:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA27929
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:34:57 -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 MAA27922
for <freebsd-current@freebsd.org>; Fri, 6 Nov 1998 12:34:53 -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 UAA28581;
Fri, 6 Nov 1998 20:33:55 GMT
Date: Fri, 6 Nov 1998 20:33:55 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Andrzej Bialecki <abial@nask.pl>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: nfs.ko panics on unloading
In-Reply-To: <Pine.BSF.4.02A.9811061205320.21136-100000@korin.warman.org.pl>
Message-ID: <Pine.BSF.4.01.9811062028450.19324-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, 6 Nov 1998, Andrzej Bialecki wrote:
> Hi,
>
> With latest sources, running ELF kernel (and yes, I rebuilt kernel _and_
> modules) loading nfs.ko works ok, but unloading results in immediate panic
> (page fault in kernel mode) and stack corruption. Is this a bug or a
> feature?
>
> This is very repeatable here, but if anyone wants a coredump, I've got
> one.
There is a mistake in mount.h's module hooks for loading and initialising
a filesystem. It calls vfs_register() at both load and unload time. I
have some patches which I haven't got around to testing which disables
unloading (and factor out some of the common vfs module registration
code). Unfortunately the vfs system itself doesn't support unloading yet
(a project for someone there).
--
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 6 12:38:22 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA28388
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:38:22 -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 MAA28383
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:38:21 -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 MAA00726;
Fri, 6 Nov 1998 12:37:07 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811062037.MAA00726@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Cory Kempf <ckempf@enigami.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: bad time slicing? Priorities?
In-reply-to: Your message of "06 Nov 1998 11:30:32 EST."
<x7sofwokbb.fsf@singularity.enigami.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 06 Nov 1998 12:37:07 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I have a system running 3.0 SMP, with 2 333MHz PII's.
...
> So, do I just not understand how BSD does its scheduling? Or is there
> actually something wrong?
There appears to be something wrong, actually. Can you replace all the
instances of 'cpu ?? CPU_686' in sys/i386/i386/pmap.c with
'cpu_class ?? CPUCLASS_686' (where ?? may be == or !=) and see if this
makes any sort of improvement?
--
\\ 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 6 12: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 MAA28536
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:39:57 -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 MAA28528
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:39:55 -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 PAA01859;
Fri, 6 Nov 1998 15:39:24 -0500 (EST)
(envelope-from wollman)
Date: Fri, 6 Nov 1998 15:39:24 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199811062039.PAA01859@khavrinen.lcs.mit.edu>
To: Doug Rabson <dfr@nlsystems.com>
Cc: Andrzej Bialecki <abial@nask.pl>, freebsd-current@FreeBSD.ORG
Subject: Re: nfs.ko panics on unloading
In-Reply-To: <Pine.BSF.4.01.9811062028450.19324-100000@herring.nlsystems.com>
References: <Pine.BSF.4.02A.9811061205320.21136-100000@korin.warman.org.pl>
<Pine.BSF.4.01.9811062028450.19324-100000@herring.nlsystems.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
<<On Fri, 6 Nov 1998 20:33:55 +0000 (GMT), Doug Rabson <dfr@nlsystems.com> said:
> code). Unfortunately the vfs system itself doesn't support unloading yet
> (a project for someone there).
It certainly did before! NFS never did, no, because there was no way
to undefine a syscall, but when I first implemented VFS LKMs, you
definitely could unload them (provided that the reference count was
zero).
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu | O Siem / The fires of freedom
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 12: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 MAA28949
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:42:54 -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 MAA28942
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:42:52 -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 PAA01565;
Fri, 6 Nov 1998 15:42:28 -0500 (EST)
Date: Fri, 6 Nov 1998 15:42:28 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: "David E. Cross" <crossd@cs.rpi.edu>, Eivind Eklund <eivind@yes.no>,
current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <2826.910378788@time.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811061533160.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 Fri, 6 Nov 1998, Jordan K. Hubbard wrote:
> > If it was happening to everyone as much as it was happening to
> > me, I seriously doubt 3.0 would have ever reached release
> > status...having inetd die every 6 to 24 hours, httpd and sendmail
> > every couple days is pretty intolerable.
>
> Have you tried that new inetd.c replacement that was posted awhile
> back? I'm just wondering if it affects the problem.
Yes and it was proven ineffectual inside of about 8 hours.
With respect to the inetd patch, it may well be a case of two
separate problems that manifest themselves in the same way, so
fixing one doesn't necessairly remove the symptom.
Since other daemons (sendmail, httpd) exhibit the same symptom,
something outside of inetd is likely to be involved.
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 12: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 MAA29251
for freebsd-current-outgoing; Fri, 6 Nov 1998 12: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 MAA29245
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 12: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 MAA18819;
Fri, 6 Nov 1998 12:45:24 -0800 (PST)
Date: Fri, 6 Nov 1998 12:45:24 -0800 (PST)
From: dan@math.berkeley.edu (Dan Strick)
Message-Id: <199811062045.MAA18819@math.berkeley.edu>
To: werner@btp1da.phy.uni-bayreuth.de
Subject: RE: latest kernel breaks linux netscape.
Cc: current@FreeBSD.ORG, dan@math.berkeley.edu
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> 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
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 12:52:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA00454
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:52:42 -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 MAA00449
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:52:41 -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 MAA00840
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:52:02 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811062052.MAA00840@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: freebsd-current@FreeBSD.ORG
Subject: Re: ficl
In-reply-to: Your message of "Fri, 06 Nov 1998 06:56:48 EST."
<Pine.BSF.4.05.9811060653440.300-100000@picnic.mat.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 06 Nov 1998 12:52:01 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I'm watching all your work using ficl with a lot of interest, but I
> don't understand the operating environment of programs at that early
> stage of boot too well. Is the filesystem available? Can any use be
> made of other Unix utils at all? What devices are available?
> Obviously, screen input/output is *somewhat* available, right?
See the libstand(9) manpage for a succinct summary of the environment.
You have read-only filesystem access, and a subset of the standard Unix
API.
There's no kernel running, so no, you can't run anything else; this is
one compelling reason for adding Forth - it lets you load and run stuff
on an as-required basis.
--
\\ 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 6 12:55:41 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA00885
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:55:41 -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 MAA00875
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:55:36 -0800 (PST)
(envelope-from asmodai@wxs.nl)
Received: from chronias.ninth-circle.org ([195.121.58.164])
by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP
id AAA54F8; Fri, 6 Nov 1998 21:55:23 +0100
Message-ID: <XFMail.981106215926.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: <3406.910383707@time.cdrom.com>
Date: Fri, 06 Nov 1998 21:59:26 +0100 (CET)
Organization: Ninth Circle Enterprises
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: YAQ (Yet Another Question)
Cc: FreeBSD Current <current@FreeBSD.ORG>, Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On 06-Nov-98 Jordan K. Hubbard wrote:
>> We have the .45 in config(8)'s mouth. No point in major exterior
>> surgery at this point in time.
>
> Hmmm, that's another good point. Ignore my previous arrow fired at
> Jeroen - he can volunteer to do whatever next issue he raises
> instead. :-)
*Decides not to mention anything about NFS* =)
Well I willing to look at any neglected areas that are left to look at ;)
---
Jeroen Ruigrok van der Werven/Asmodai
asmodai(at)wxs.nl
Junior Network/Security Specialist
FreeBSD & 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 Fri Nov 6 12:56:58 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA01122
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:56:58 -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 MAA01110
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:56:53 -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 PAA11065;
Fri, 6 Nov 1998 15:50:30 -0500 (EST)
Date: Fri, 6 Nov 1998 15:50:30 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
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: <19981106183112.27770@follo.net>
Message-ID: <Pine.BSF.4.05.9811061549150.300-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 Fri, 6 Nov 1998, Eivind Eklund wrote:
> On Fri, Nov 06, 1998 at 12:12:14PM -0500, John Fieber wrote:
> > I've now figured out that it must be the infamous dying daemons
> > bug that is biting me, and pretty bad. Inetd won't run more than
> > a day without falling over. Sendmail and apache last longer, but
> > not a lot.
> >
> > So, to date, what is known about the bug?
>
> It strike when you run out of memory, usually.
>
> > Are there people running 3.0/Current that have not encountered
> > this bug?
> >
> > Are there any known factors in a system configuration that
> > aggrivate the problem? More to the point, is there anything
> > known to suppress the problem to any degree? Some say it was
> > present in 2.2.x, but I never encountered it.
>
> Run with insane amounts of swap. 2GB ought to do the trick. I'm not
> guaranteeing this will stop the problem, but it will make it _much_
> less frequent.
>
> Eivind, who increased from 128MB to 256MB swap, and had the problem
> almost go away...
David Greenman committed some fixes a couple weeks back which he
speculated *might* have an effect on this. John, is your stuff newer
than that? Or any anyone noticed the inetd thing since then?
I can dig up the commit message, if you need it.
>
> 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 Fri Nov 6 12:58:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA01440
for freebsd-current-outgoing; Fri, 6 Nov 1998 12:58:49 -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 MAA01427
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 12:58:44 -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 VAA26826;
Fri, 6 Nov 1998 21:59:47 +0100 (CET)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Fri, 6 Nov 1998 21:59:46 +0100 (CET)
From: Andrzej Bialecki <abial@nask.pl>
X-Sender: abial@korin.warman.org.pl
To: Mike Smith <mike@smith.net.au>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>,
Robert Nordier <rnordier@nordier.com>, Chuck Robey <chuckr@mat.net>,
freebsd-current@FreeBSD.ORG
Subject: Re: ficl
In-Reply-To: <199811062026.MAA00622@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.02A.9811062153200.23415-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 Fri, 6 Nov 1998, Mike Smith wrote:
> > > Devices: Apart from video and serial consoles, disk and net devices
> > > are currently provided for. Though, at least on the i386, it should
> > > be reasonably easy to add access to anything that has BIOS or other
> > > firmware support.
(As a side note: I recently act as a panic detector :-) /boot/loader with
Forth enabled dies on me after your recent changes).
I have a question concerning at-xy, cls, and perhaps get-xy words. They
are clearly arch dependent, so if I come to implementing them (I said:
"IF" ;-), where I should add them? And, is this so simple as
vidc_getchar() suggests?
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 Fri Nov 6 13:02:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA02166
for freebsd-current-outgoing; Fri, 6 Nov 1998 13:02:51 -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 NAA02159
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 13:02:48 -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 VAA28704;
Fri, 6 Nov 1998 21:01:39 GMT
Date: Fri, 6 Nov 1998 21:01:39 +0000 (GMT)
From: Doug Rabson <dfr@nlsystems.com>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
cc: Andrzej Bialecki <abial@nask.pl>, freebsd-current@FreeBSD.ORG
Subject: Re: nfs.ko panics on unloading
In-Reply-To: <199811062039.PAA01859@khavrinen.lcs.mit.edu>
Message-ID: <Pine.BSF.4.01.9811062059170.19324-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, 6 Nov 1998, Garrett Wollman wrote:
> <<On Fri, 6 Nov 1998 20:33:55 +0000 (GMT), Doug Rabson <dfr@nlsystems.com> said:
>
> > code). Unfortunately the vfs system itself doesn't support unloading yet
> > (a project for someone there).
>
> It certainly did before! NFS never did, no, because there was no way
> to undefine a syscall, but when I first implemented VFS LKMs, you
> definitely could unload them (provided that the reference count was
> zero).
I must be blind! I didn't even see vfs_unregister(). I'll tweak my patch
and try to find time to test it. I think that NFS should define two
modules, one for the vfs and one for the syscall (there isn't a predefined
module type for syscalls 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 Fri Nov 6 13:08:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA02710
for freebsd-current-outgoing; Fri, 6 Nov 1998 13:08:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from vss.sci-nnov.ru (vss.sci-nnov.ru [193.125.71.26])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02690;
Fri, 6 Nov 1998 13:08:03 -0800 (PST)
(envelope-from dmiter@sci-nnov.ru)
Received: from winhome (home.sci-nnov.ru [194.190.176.102]) by vss.sci-nnov.ru (8.8.8/Dmiter-4.2vss) with SMTP id AAA25453; Sat, 7 Nov 1998 00:07:18 +0300 (MSK)
Message-ID: <001a01be09c9$510c0010$0200000a@winhome.sci-nnov.ru>
Reply-To: "Dmitry Eremin" <dmiter@sci-nnov.ru>
From: "Dmitry Eremin" <dmiter@sci-nnov.ru>
To: "Bill Fenner" <fenner@parc.xerox.com>
Cc: <freebsd-current@FreeBSD.ORG>, <freebsd-bugs@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
Date: Sat, 7 Nov 1998 00:06:08 +0300
MIME-Version: 1.0
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>Did the message get printed during your tcpdump, or was the tcpdump taken
>at a different time? Could you try to replicate this with both tcpdumps
>running at the same time (on different screens to not intersperse the
>output) and include the timestamps?
Both tcpdump runing in same time in defferent window.
$ tcpdump -tvvi de1 arp
22:55:35.096038 arp who-has 192.168.1.205 tell 192.168.1.48
22:55:35.096517 arp reply 192.168.1.205 is-at 0:10:4b:35:60:6c
$ tcpdump -tvvi de0 arp
22:55:35.096107 arp who-has 192.168.1.205 tell 192.168.1.48
>Does the ARP entry get installed correctly? i.e.
>1) Does "arp 192.168.1.188" show the right MAC address?
# arp 192.168.1.205
192.168.1.205 (192.168.1.205) -- no entry
>2) Does "route get 192.168.1.188" list the correct interface?
# route get 192.168.1.205
route to: 192.168.1.205
destination: 192.168.1.0
mask: 255.255.255.0
interface: de1
flags: <UP,DONE,CLONING>
recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu
expire
0 0 0 0 0 0
1500 -24616
>Do you have any idea why the ARP request shows up on both interfaces?
I don't known hay this happening. This system has working as router.
May be it is forwarding?
sysctl say:
[...skip...]
net.inet.ip.forwarding: 1
net.inet.ip.redirect: 1
net.inet.ip.ttl: 64
net.inet.ip.sourceroute: 0
[...skip...]
net.link.ether.inet.prune_intvl: 300
net.link.ether.inet.max_age: 1200
net.link.ether.inet.host_down_time: 20
net.link.ether.inet.maxtries: 5
net.link.ether.inet.useloopback: 1
net.link.ether.inet.proxyall: 0
[...skip...]
>FreeBSD doesn't send ARP requests out multiple interfaces, so perhaps
>you have something funny going on at layer 2 (e.g. shared hub between
>the two different networks, or a broken switch)?
NO. We have't any devices between these networks.
de0: flags=88c3<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet xx.xx.xx.xx netmask 0xfffffffc broadcast xx.xx.xx.xx
^^^^^^^^^^^^^^^^^^
In the net de0 we have only TWO address. One have my FreeBSD computer and
second have Internet router!!!!
I want to attract you attention on my Ethernet cards. This is identical
card.
de0: <Digital 21140 Fast Ethernet> rev 0x12 int a irq 11 on pci0.12.0
de0: SMC 9332DST 21140 [10-100Mb/s] pass 1.2
de0: address 00:00:c0:b2:9f:d0
de0: enabling 10baseT port
de1: <Digital 21140 Fast Ethernet> rev 0x12 int a irq 10 on pci0.13.0
de1: SMC 9332DST 21140 [10-100Mb/s] pass 1.2
de1: address 00:00:c0:b8:a1:d0
de1: enabling 10baseT port
I think kernel doesn't correct work in this case.
Best regards, Dmitry.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 13: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 NAA02730
for freebsd-current-outgoing; Fri, 6 Nov 1998 13:08:21 -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 NAA02700
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 13:08:17 -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 NAA00965;
Fri, 6 Nov 1998 13:07:03 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811062107.NAA00965@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Andrzej Bialecki <abial@nask.pl>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: ficl
In-reply-to: Your message of "Fri, 06 Nov 1998 21:59:46 +0100."
<Pine.BSF.4.02A.9811062153200.23415-100000@korin.warman.org.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 06 Nov 1998 13:07:03 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> On Fri, 6 Nov 1998, Mike Smith wrote:
>
> > > > Devices: Apart from video and serial consoles, disk and net devices
> > > > are currently provided for. Though, at least on the i386, it should
> > > > be reasonably easy to add access to anything that has BIOS or other
> > > > firmware support.
>
> (As a side note: I recently act as a panic detector :-) /boot/loader with
> Forth enabled dies on me after your recent changes).
My recent changes? Which ones?
> I have a question concerning at-xy, cls, and perhaps get-xy words. They
> are clearly arch dependent, so if I come to implementing them (I said:
> "IF" ;-), where I should add them? And, is this so simple as
> vidc_getchar() suggests?
You should always use getchar() and putchar(), and assume a minimal ANSI
terminal. vidc_putchar will have to become a minimal ANSI terminal
emulator.
--
\\ 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 6 13:14:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA03539
for freebsd-current-outgoing; Fri, 6 Nov 1998 13:14:31 -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 NAA03473
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 13:13:46 -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 WAA02816;
Fri, 6 Nov 1998 22:19:00 +0100 (CET)
X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs
Date: Fri, 6 Nov 1998 22:19:00 +0100 (CET)
From: Andrzej Bialecki <abial@nask.pl>
X-Sender: abial@korin.warman.org.pl
To: Mike Smith <mike@smith.net.au>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: ficl
In-Reply-To: <199811062107.NAA00965@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.02A.9811062215420.23415-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 Fri, 6 Nov 1998, Mike Smith wrote:
> > On Fri, 6 Nov 1998, Mike Smith wrote:
> >
> > > > > Devices: Apart from video and serial consoles, disk and net devices
> > > > > are currently provided for. Though, at least on the i386, it should
> > > > > be reasonably easy to add access to anything that has BIOS or other
> > > > > firmware support.
> >
> > (As a side note: I recently act as a panic detector :-) /boot/loader with
> > Forth enabled dies on me after your recent changes).
>
> My recent changes? Which ones?
Erhm... You're right, it was jkh... anyway, it screams and dies.
> > I have a question concerning at-xy, cls, and perhaps get-xy words. They
> > are clearly arch dependent, so if I come to implementing them (I said:
> > "IF" ;-), where I should add them? And, is this so simple as
> > vidc_getchar() suggests?
>
> You should always use getchar() and putchar(), and assume a minimal ANSI
> terminal. vidc_putchar will have to become a minimal ANSI terminal
> emulator.
ANSI.SYS or cons25 -compatible? This also means keeping some state inside
get/putchar() so that it recognizes esc sequences...
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 Fri Nov 6 13:18:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA04123
for freebsd-current-outgoing; Fri, 6 Nov 1998 13:18:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA04102
for <current@freebsd.org>; Fri, 6 Nov 1998 13:18:28 -0800 (PST)
(envelope-from wpaul@skynet.ctr.columbia.edu)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA15892; Fri, 6 Nov 1998 16:16:49 -0500
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199811062116.QAA15892@skynet.ctr.columbia.edu>
Subject: Re: Grrr... calcru: negative time blah blah blah
To: phk@critter.freebsd.dk (Poul-Henning Kamp)
Date: Fri, 6 Nov 1998 16:16:47 -0500 (EST)
Cc: current@FreeBSD.ORG
In-Reply-To: <5110.910380360@critter.freebsd.dk> from "Poul-Henning Kamp" at Nov 6, 98 08:26:00 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Of all the gin joints in all the towns in all the world, Poul-Henning
Kamp had to walk into mine and say:
> The numbers in the tc_diag_buffer are basically the number of ticks
> on the timecounter between each use of it.
>
> >Timecounter "i8254" frequency 1193182 Hz
>
> Normally, the largest number of ticks should be the frequency of
> the timecounter divided by 100, in this case 11931, (plus or minus
> epsilon).
>
> When smaller counts are in the buffer it means that one of the *time()
> functions were called, so that is normal.
Okay. Was wondering about that.
> >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...
[chop]
> Neither of the two tests seems to have triggered any of my tests
> since "debug.tc_diag_stop" is still zero.
>
> This is consistent with a model of "lost interrupts", which I think the
> above data support. A "reading the i8254 wrong" theory doesn't match
> the values you have here, more +/- 256 values should have been present.
>
> 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.
The dmesg is different this time:
FreeBSD 3.0-19981103-SNAP #0: Fri Nov 6 15:00:49 EST 1998
root@wormhole.ee.columbia.edu:/usr/src2/sys/compile/TEST
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 448623175 Hz
CPU: Pentium II (quarter-micron) (448.62-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x652 Stepping=2
Features=0x183fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,<b24>>
real memory = 536870912 (524288K bytes)
avail memory = 519811072 (507628K bytes)
The display adapter is on IRQ 11:
vga0: <VGA-compatible display device> rev 0x01 int a irq 11 on pci1.0.0
sysctl kern.timecounter shows this:
kern.timecounter.frequency: 448623175
kern.timecounter.adjustment: 0
Running sysctl debug _BEFORE_ triggering the problem by running the
X server shows this:
debug.elf_trace: 0
debug.tc_diag_buffer: 4486306 5056 5895 4486672 4485895 4486284 4486227 4486290 4486255 4486280 4486266 4486401 4486576 4485848 4486279 4486280 4486266 4486279 4486280 4486317 4486228 4486712 4485845 4486268 4486280 4486266 4486279 4486280 4486266 4486279
4486712 4485834 4486279 4486280 4486266 4486279 4486280 4486266 4486401 4486549 4485875 4486279 4486280 4486266 4486279 4486280 4486266 4486401 4486576 4485848 4486279 4486280 4486266 4486279 4486317 4486229 4486279 4486671 4485875 4486279 4486280 448626
6 4486279 4486280 2920176 2992441 2993279 3055877 3791199 3903903 3913227 3918977 4486298 4486685 4485834 4486335 4486224 4486266 4486279 4486343 4486203 4486401 4486576 4485848 4486279 4486280 4486266 4486279 4486280 4486369 4486176 4486671 4485875 44862
79 4486280 4486266 4486279 4486280 4486266 4486306 4486658 4485861 4486279 4486294 4486272 4486259 4486280 4486266 4486401 4486576 4485848 4486279 4486280 4486266 4486279 4486280 4486266 4486401 4486552 4485872 4486279 4486280 4486266 4486279 4486280 4486
290 4486255 4486685 4485861 4486279 4486280 4486266 4486279 4486283 4486263 4486306 4486685 4485834 4486279 4486283 4486263 4486279 4486280 4486266 4486279 4486698 4485848 4486282 4486277 4486266 4486279 4486280 4486266 6057 7051 4486416 4486598 4485811 4
486279 4486348 4486198 4486279 4486280 4486266 4486401 4486576 4485848 4486282 4486277 4486266 4486279 4486280 4486266 4486279 4486671 4485875 4486279 4486289 4486257 4486279 4486280 4486266 4486401 4486600 4485824 4486279 4486280 4486266 4486279 4486280
4486266 4486401 4486576 4485848 4486279 4486280 4486266 4486279 4486280 4486266 4486401 4486576 4485848 4486279 4486280 4486266 4486315 4486244 4486266 4486279 4486712 4485834 4486279 4486280 4486266 4486279 4486280 4486266 4486309 4486679 4485837 4486279
4486280 4486290 4486255 4486294 4486252 4486279 4486712 2422 3425 4485857 4486256 4486280 4486266 4486279 4486280 4486266 4486401 4486587 4485837 4486279 4486318 4486228 4486279 4486303 4486243 4486279 4486671 4485875 4486282 4486277 4486266 4486303 4486
285 4486237
debug.tc_diag_index: 10825
debug.tc_diag_stop: 0
debug.tc_diag_maxforward: -692379806
debug.fdexpand: 0
debug.debugger_on_panic: 1
debug.ttydebug: 0
debug.nchash: 32767
debug.ncnegfactor: 16
debug.numneg: 12
debug.numcache: 215
debug.vfscache: 1
debug.vnsize: 164
debug.ncsize: 36
debug.numvnodes: 235
debug.wantfreevnodes: 25
debug.freevnodes: 24
debug.disablecwd: 0
debug.if_tun_debug: 0
debug.ncr_debug: 0
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
24640686 24640659 24640686 24640673 24640659 24640686 24640775 24640988 24640268 24640659 24640672 24640784 24640572 24640772 24640600 24640756 24640997 24640240 24640673 24640686 24640659 24640672 24640686 24640659 24640686 24641105 24640227 24640686 246
40672 24640673 24640686 24640659 24640686 24640672 24641078 24640267 24640694 24640638 24640687 24640671 24640673 24640726 24640740 24640970 24640257 24640692 24640666 24640674 24640669 24640693 24640651 24640673 24641077 24640268 24640686 24640659 246406
72 24640686 24640713 24640632 24640673 24641064 24640281 6230 7513 24640980 24640468 24640607 24640638 24640669 6715434 6807259 6808209 6981571 6991770 6997735 24640744 24640614 24641091 24640292 24640638 24640669 24640719 24640773 24640539 24640673 24640
693 24641084 24640584 24640332 24640683 24640659 24640672 24640686 24640659 24640746 24641078 24640217 24640789 24640587 24640632 24640686 24640714 24640631 24640718 7359 8943 9843 24641105 24640293 24640597 24640636 24640686 24640672 24640714 24640729 24
640575 24641091 24640254 24640672 24640686 24640659 24640686 24640715 24640617 24640686 24641181 24640164 24640786 24640584 24640657 24640676 24640692 24640653 24640715 24641035 24640268 24640672 24640715 24640644 24640659 24640672 24640713 24640632 24641
078 24640281 24640684 24640661 24640672 24640673 24640686 24640659 24640794 24640996 24640251 24640662 24640673 24640659 24640686 24640708 24640637 24640686 24641064 24640281 24640672 24640659 24640686 24640673 24640659 24640686 24640722 24641055 24640240
24640673 24640738 24640607 24640732 24640626 24640662 24640721 24641053 24640254 24640698 24640647 24640673 24640686 24640662 24640669 24640689 24641088 24640277 24640650 24640659 24640686 24640675 24640670 24640686 24640659 24641116 24640242 24640670
debug.tc_diag_index: 17027
debug.tc_diag_stop: 0
debug.tc_diag_maxforward: -692379806
debug.fdexpand: 0
debug.debugger_on_panic: 1
debug.ttydebug: 0
debug.nchash: 32767
debug.ncnegfactor: 16
debug.numneg: 20
debug.numcache: 332
debug.vfscache: 1
debug.vnsize: 164
debug.ncsize: 36
debug.numvnodes: 332
debug.wantfreevnodes: 25
debug.freevnodes: 28
debug.disablecwd: 0
debug.if_tun_debug: 0
debug.ncr_debug: 0
Everything seems to have been divided in half. The machine still runs
but the console is sluggish. Unfortunately, I don't see any way in the
BIOS setup to disable any of the interrupts, and slicing a brand new
board probably wouldn't sit well with the EE faculty, largely because
these machines (and many others) were donations from Intel (they dropped
a couple million dollars worth of stuff on Columbia and a couple other
universities).
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.
-Bill
--
=============================================================================
-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu
Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
"It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=============================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 13:19:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA04167
for freebsd-current-outgoing; Fri, 6 Nov 1998 13:19:04 -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 NAA04161
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 13:19:03 -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 NAA01041;
Fri, 6 Nov 1998 13:17:06 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811062117.NAA01041@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Andrzej Bialecki <abial@nask.pl>
cc: Mike Smith <mike@smith.net.au>, freebsd-current@FreeBSD.ORG
Subject: Re: ficl
In-reply-to: Your message of "Fri, 06 Nov 1998 22:19:00 +0100."
<Pine.BSF.4.02A.9811062215420.23415-100000@korin.warman.org.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 06 Nov 1998 13:17:06 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> > > (As a side note: I recently act as a panic detector :-) /boot/loader with
> > > Forth enabled dies on me after your recent changes).
> >
> > My recent changes? Which ones?
>
> Erhm... You're right, it was jkh... anyway, it screams and dies.
Ok. He's awake, but I'll look at it as well. He did say there'd be
more commits, so I was waiting to check it out.
> > > I have a question concerning at-xy, cls, and perhaps get-xy words. They
> > > are clearly arch dependent, so if I come to implementing them (I said:
> > > "IF" ;-), where I should add them? And, is this so simple as
> > > vidc_getchar() suggests?
> >
> > You should always use getchar() and putchar(), and assume a minimal ANSI
> > terminal. vidc_putchar will have to become a minimal ANSI terminal
> > emulator.
>
> ANSI.SYS or cons25 -compatible? This also means keeping some state inside
> get/putchar() so that it recognizes esc sequences...
*much* more minimal; I'd expect:
- move cursor
- standout on/off
- clear screen
It might be feasible to add a few more. Maintaining state's not all
that difficult. 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 Fri Nov 6 13:20:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA04479
for freebsd-current-outgoing; Fri, 6 Nov 1998 13:20:31 -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 NAA04469
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 13:20:30 -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 NAA04003;
Fri, 6 Nov 1998 13:18:51 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Andrzej Bialecki <abial@nask.pl>
cc: Mike Smith <mike@smith.net.au>, Robert Nordier <rnordier@nordier.com>,
Chuck Robey <chuckr@mat.net>, freebsd-current@FreeBSD.ORG
Subject: Re: ficl
In-reply-to: Your message of "Fri, 06 Nov 1998 21:59:46 +0100."
<Pine.BSF.4.02A.9811062153200.23415-100000@korin.warman.org.pl>
Date: Fri, 06 Nov 1998 13:18:51 -0800
Message-ID: <3999.910387131@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> (As a side note: I recently act as a panic detector :-) /boot/loader with
> Forth enabled dies on me after your recent changes).
Fixed this morning. fexists and fload still need just a bit more
work before they'll work properly from compile state, but at leat
they don't crash. :)
> I have a question concerning at-xy, cls, and perhaps get-xy words. They
> are clearly arch dependent, so if I come to implementing them (I said:
When I thought about this, I figured on simply wimping-out and
assuming an ANSI compat terminal. :-) It wouldn't be elegant, but it
would also pretty much work for simple screen I/O on both VTYs and
serial consoles at very minimal programming cost..
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 13:25:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA04887
for freebsd-current-outgoing; Fri, 6 Nov 1998 13:25:28 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m2-20-dbn.dial-up.net [196.34.155.84])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04875
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 13:25:22 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA03311; Fri, 6 Nov 1998 23:18:31 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199811062118.XAA03311@ceia.nordier.com>
Subject: Re: ficl
In-Reply-To: <199811062026.MAA00622@dingo.cdrom.com> from Mike Smith at "Nov 6, 98 12:26:36 pm"
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Fri, 6 Nov 1998 23:18:23 +0200 (SAT)
Cc: chuckr@mat.net, 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
Mike Smith wrote:
> > I'm not really sure what you mean by "net devices"
> > either - how does one configure and use a typical NIC from the BTX
> > environment?
>
> BTX has nothing to do with it. Again, there's no low-level NIC support
> in the i386 code at the moment, but basically you provide a low-level
> hardware driver, and then the IP stack in lib stand does the Bootp
> Thing. From there, it's just another device, eg.
>
> 'load net:/kernel'
>
> will do "what you expect it to do".
Intel has been working on a PXE (Preboot Execution Environment)
specification which offers access to a NIC through something called
UNDI (Universal Network Driver Interface). At one stage this seemed
to promise BIOS support at a fairly similar level to the PC int 0x13
services provided for hard drives.
Unfortunately, the spec has mostly been too fluid and confused (the
entire API changed at least once) to warrant taking very seriously.
--
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 6 13:28:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA05206
for freebsd-current-outgoing; Fri, 6 Nov 1998 13:28:16 -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 NAA05198
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 13:28:14 -0800 (PST)
(envelope-from benedict@echonyc.com)
Received: from localhost by echonyc.com (8.9.1/8.9.1) with SMTP id QAA01771;
Fri, 6 Nov 1998 16:27:51 -0500 (EST)
Date: Fri, 6 Nov 1998 16:27:51 -0500 (EST)
From: Snob Art Genre <benedict@echonyc.com>
Reply-To: ben@rosengart.com
To: Cory Kempf <ckempf@enigami.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: bad time slicing? Priorities?
In-Reply-To: <x7sofwokbb.fsf@singularity.enigami.com>
Message-ID: <Pine.GSO.4.02.9811061626390.6081-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
On 6 Nov 1998, Cory Kempf wrote:
> If I run xgalaga (a game), which is being run at nice=5 for some
> reason (not sure why, haven't looked into it), It doesn't seem to be
> getting enough CPU time.
>
> Play is jerky and slow.
I find that X games play best if I renice both the X server and the game
to a negative value.
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 6 13: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 NAA05249
for freebsd-current-outgoing; Fri, 6 Nov 1998 13:28:32 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05241
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 13:28:31 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01098;
Fri, 6 Nov 1998 13:22:43 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811062122.NAA01098@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
cc: phk@critter.freebsd.dk (Poul-Henning Kamp), current@FreeBSD.ORG
Subject: Re: Grrr... calcru: negative time blah blah blah
In-reply-to: Your message of "Fri, 06 Nov 1998 16:16:47 EST."
<199811062116.QAA15892@skynet.ctr.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 06 Nov 1998 13:22:43 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>
> 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.
You can poke the PIC, sure. You need to find out which interrupt it is
first though; look for the IRQ number on the vga0 device.
--
\\ 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 6 13:41:25 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA06697
for freebsd-current-outgoing; Fri, 6 Nov 1998 13:41:25 -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 NAA06685
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 13:41:21 -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 QAA01705;
Fri, 6 Nov 1998 16:40:58 -0500 (EST)
Date: Fri, 6 Nov 1998 16:40:58 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Chuck Robey <chuckr@mat.net>
cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.BSF.4.05.9811061549150.300-100000@picnic.mat.net>
Message-ID: <Pine.BSF.4.05.9811061634550.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 Fri, 6 Nov 1998, Chuck Robey wrote:
> David Greenman committed some fixes a couple weeks back which he
> speculated *might* have an effect on this. John, is your stuff newer
> than that? Or any anyone noticed the inetd thing since then?
I was runing a kernel from around Nov 1, but it seemed like I was
having more daemon fatalities than before so I have just
regressed to a 3.0-RELEASE kernel (plus ip_input.c fixes and a
cam_xpt.c quirk addition).
If you can spot the exact commit, I can build before and after
kernels to see if there is a any change.
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 13:42:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA06775
for freebsd-current-outgoing; Fri, 6 Nov 1998 13:42:01 -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 NAA06755
for <current@freebsd.org>; Fri, 6 Nov 1998 13:41:52 -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 XAA14346
for <current@freebsd.org>; Fri, 6 Nov 1998 23:41:22 +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 XAA22795
for current@freebsd.org; Fri, 6 Nov 1998 23:40:55 +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 XAA06359;
Fri, 6 Nov 1998 23:33:37 +0200 (EET)
(envelope-from archer)
Date: Fri, 6 Nov 1998 23:33:37 +0200 (EET)
From: Alexander Litvin <archer@lucky.net>
Message-Id: <199811062133.XAA06359@grape.carrier.kiev.ua>
To: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
X-Newsgroups: grape.freebsd.current
In-Reply-To: <19981106183112.27770@follo.net> <Pine.SGI.4.05.9811061258001.810-100000@o2.cs.rpi.edu> <19981106200028.23174@follo.net>
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 <19981106200028.23174@follo.net> you wrote:
EE> On Fri, Nov 06, 1998 at 01:33:41PM -0500, David E. Cross wrote:
>>
>> 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.
EE> No. Unfortunately, we've not found any (or I at least don't know of
EE> any) common factors between all the machines that have this problem.
EE> David committed some patches a while back that he said _might_ help it
EE> - I've not yet upgraded to test this.
Unfortunately, DG's patches didn't solve the problem. May be,
there are more than one bug "contributing".
BTW, it seems that either 'make -j# buildworld' fires out more
parallel jobs than it used to, or the total system memory footprint
has increased. I mean, some three months ago my system easily
survived -j32, without daemons dying, even without 'Suggest more
swap space' -- it is for me a first sign that soon I'll have
them dying. But now it needs only -j14 to be out of swap on the
same system.
EE> Eivind.
---
Your lucky number has been disconnected.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 14:06:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA10128
for freebsd-current-outgoing; Fri, 6 Nov 1998 14:06:24 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10110
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 14:06:15 -0800 (PST)
(envelope-from roberto@keltia.freenix.fr)
Received: (from uucp@localhost)
by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA00684
for freebsd-current@FreeBSD.ORG; Fri, 6 Nov 1998 23:05:45 +0100 (CET)
(envelope-from roberto@keltia.freenix.fr)
Received: by keltia.freenix.fr (VMailer, from userid 101)
id ABC5F1514; Fri, 6 Nov 1998 23:00:51 +0100 (CET)
Date: Fri, 6 Nov 1998 23:00:51 +0100
From: Ollivier Robert <roberto@keltia.freenix.fr>
To: "FreeBSD Current Users' list" <freebsd-current@FreeBSD.ORG>
Subject: iBCS2 module legacy build broken
Message-ID: <19981106230051.A21406@keltia.freenix.fr>
Mail-Followup-To: FreeBSD Current Users' list <freebsd-current@FreeBSD.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.94.4i
X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4772 AMD-K6 MMX @ 200 MHz
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Apart from that small error below, I built an ELF kernel and loaded KLD
modules just fine. The new loader is working fine, congrats.
-=-=-=-
--- ibcs2_mod.o ---
ld -r -aout -o tmp.o ibcs2.o ibcs2_errno.o ibcs2_ipc.o ibcs2_stat.o ibcs2_misc.o ibcs2_fcntl.o ibcs2_signal.o ibcs2_sysent.o ibcs2_ioctl.o ibcs2_socksys.o ibcs2_util.o ibcs2_xenix.o ibcs2_xenix_sysent.o ibcs2_isc.o ibcs2_isc_sysent.o ibcs2_msg.o ibcs2_other.o ibcs2_sysi86.o ibcs2_sysvec.o
ibcs2.o: Definition of symbol `_ibcs2_mod' (multiply defined)
ibcs2_sysvec.o: Definition of symbol `_ibcs2_mod' (multiply defined)
*** Error code 1
1 error
...
-=-=-=-
203 [22:48] roberto@tara:~> kldstat
Id Refs Address Size Name
1 4 0xf0100000 14bf48 kernel.elf
2 1 0xf024c000 48690 nfs.ko
3 1 0xf0295000 f74c linux.ko
4 1 0xf0895000 3000 daemon_saver.ko (even working right now ! :-))
205 [22:49] roberto@tara:~> ll /boot
-r--r--r-- 1 root wheel 512 Oct 28 08:31 boot0
-r--r--r-- 1 root wheel 512 Nov 6 22:08 boot1
-r--r--r-- 1 root wheel 7680 Nov 6 22:08 boot2
-r-xr-xr-x 1 root wheel 86016 Nov 6 22:08 loader*
-=-=-=-
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 #2: Fri Nov 6 22:27:23 CET 1998
roberto@tara.freenix.org:/src/src/sys/compile/TARA_ELF
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 198656520 Hz
CPU: Pentium Pro (198.66-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x619 Stepping=9
Features=0xfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV>
real memory = 67108864 (65536K bytes)
config> quit
avail memory = 62509056 (61044K bytes)
Preloaded elf kernel "kernel.elf" at 0xf02a6000.
Preloaded elf module "nfs.ko" at 0xf02a60a0.
Preloaded elf module "linux.ko" at 0xf02a613c.
Probing for devices on PCI bus 0:
...
-=-=-=-
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-BETA #4: Thu Oct 15 01:36:57 CEST 1998
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 14:07:37 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA10336
for freebsd-current-outgoing; Fri, 6 Nov 1998 14:07:37 -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 OAA10329
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 14:07:35 -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 RAA11278;
Fri, 6 Nov 1998 17:06:23 -0500 (EST)
Date: Fri, 6 Nov 1998 17:06:23 -0500 (EST)
From: Chuck Robey <chuckr@mat.net>
To: John Fieber <jfieber@indiana.edu>
cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.BSF.4.05.9811061634550.482-100000@fallout.campusview.indiana.edu>
Message-ID: <Pine.BSF.4.05.9811061705550.300-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 Fri, 6 Nov 1998, John Fieber wrote:
> On Fri, 6 Nov 1998, Chuck Robey wrote:
>
> > David Greenman committed some fixes a couple weeks back which he
> > speculated *might* have an effect on this. John, is your stuff newer
> > than that? Or any anyone noticed the inetd thing since then?
>
> I was runing a kernel from around Nov 1, but it seemed like I was
> having more daemon fatalities than before so I have just
> regressed to a 3.0-RELEASE kernel (plus ip_input.c fixes and a
> cam_xpt.c quirk addition).
>
> If you can spot the exact commit, I can build before and after
> kernels to see if there is a any change.
[sent dg's 10/13 commit separately]
>
> -john
>
>
> 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 Fri Nov 6 14:08:05 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA10406
for freebsd-current-outgoing; Fri, 6 Nov 1998 14:08:05 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10360;
Fri, 6 Nov 1998 14:07:57 -0800 (PST)
(envelope-from mike@seidata.com)
From: mike@seidata.com
Received: from localhost (mike@localhost)
by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id RAA20780;
Fri, 6 Nov 1998 17:07:04 -0500 (EST)
Date: Fri, 6 Nov 1998 17:07:00 -0500 (EST)
To: Bill Fenner <fenner@parc.xerox.com>
cc: Dmitry Eremin <dmiter@sci-nnov.ru>, freebsd-current@FreeBSD.ORG,
freebsd-bugs@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: <199811061638.IAA28819@mango.parc.xerox.com>
Message-ID: <Pine.BSF.4.05.9811061654360.17661-100000@ns1.seidata.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, 6 Nov 1998, Bill Fenner wrote:
> FreeBSD doesn't send ARP requests out multiple interfaces, so perhaps
> you have something funny going on at layer 2 (e.g. shared hub between
> the two different networks, or a broken switch)?
Broken switch? *sigh* I've got (they've died off lately, but were
much more frequent when I first implemented the BSD-based NAT box) the
same sort of error here with the following setup:
+---------------+
LAN1--| Catalyst 1900 |
+---------------+ +-------------+ +---------------+
LAN2--| Catalyst 1900 |--| FreeBSD 3.0 |--| Catalyst 2940 |--INET
+---------------+ +-------------+ +---------------+
LAN3--| Catalyst 1900 | | Catalyst 1900 |
+---------------+ +---------------+
The Catalyst 1900's on the left provide 10BT connectivity to three
local nets (10.0.1, 10.0.2, 10.0.3) and connect to the BSD box via
100BT. They are daisey-chained via standard cross over cables using
their 100BT uplink ports. LAN's 1-3 and Windows 95, Windows NT and
Macintosh LANs. They undergo packet filtering and NAT at the BSD box.
The Catalyst 2940 and 1900 switches on the right provide 100BT and
10BT connectivity (repsectively) for servers I have 'outside' of my
firewall (FreeBSD shell, FTP, personal WWW, etc. servers).
Just FYI, maybe my setup will be similar to his in some way and
present an obvious design flaw.
Later,
-mike
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 14:34:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA13516
for freebsd-current-outgoing; Fri, 6 Nov 1998 14:32:56 -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 OAA13509
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 14:32:50 -0800 (PST)
(envelope-from dag-erli@ifi.uio.no)
Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15])
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id XAA20634;
Fri, 6 Nov 1998 23:32:18 +0100 (MET)
Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 6 Nov 1998 23:32:17 +0100 (MET)
Mime-Version: 1.0
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: John Fieber <jfieber@indiana.edu>, "David E. Cross" <crossd@cs.rpi.edu>,
Eivind Eklund <eivind@yes.no>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <2826.910378788@time.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: 06 Nov 1998 23:32:16 +0100
In-Reply-To: "Jordan K. Hubbard"'s message of "Fri, 06 Nov 1998 10:59:48 -0800"
Message-ID: <xzp1zngmozz.fsf@hrotti.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 OAA13512
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"Jordan K. Hubbard" <jkh@time.cdrom.com> writes:
> > If it was happening to everyone as much as it was happening to
> > me, I seriously doubt 3.0 would have ever reached release
> > status...having inetd die every 6 to 24 hours, httpd and sendmail
> > every couple days is pretty intolerable.
> Have you tried that new inetd.c replacement that was posted awhile
> back? I'm just wondering if it affects the problem. David's looked
> at this one a bit and he can neither reproduce it nor come up with any
> good ideas right now as to how to go about fixing it.
It only addresses the "junk pointerm, too low to make sense" bug, not
the "dying daemons" bug which John is complaining about. ISTR we
identified that as a VM bug.
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 6 14: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 OAA15267
for freebsd-current-outgoing; Fri, 6 Nov 1998 14:48:39 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m1-7-dbn.dial-up.net [196.34.155.7])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15212
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 14:48:31 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id AAA04580; Sat, 7 Nov 1998 00:45:55 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199811062245.AAA04580@ceia.nordier.com>
Subject: Re: ficl
In-Reply-To: <Pine.BSF.4.02A.9811062153200.23415-100000@korin.warman.org.pl> from Andrzej Bialecki at "Nov 6, 98 09:59:46 pm"
To: abial@nask.pl (Andrzej Bialecki)
Date: Sat, 7 Nov 1998 00:45:53 +0200 (SAT)
Cc: mike@smith.net.au, jkh@time.cdrom.com, rnordier@nordier.com,
chuckr@mat.net, 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
Andrzej Bialecki wrote:
>
> I have a question concerning at-xy, cls, and perhaps get-xy words. They
> are clearly arch dependent, so if I come to implementing them (I said:
> "IF" ;-), where I should add them? And, is this so simple as
> vidc_getchar() suggests?
I'd suppose in libi386/vidconsole.c.
The actual primitive should be fairly simple, anyway. One way to clear
(actually reinitialize) the screen is to "get video mode, set video
mode" (mov ah,0xf; int 0x10; and ax,0x7f; int 0x10), so:
static void
vidc_cls(void)
{
v86.ctl = 0;
v86.addr = 0x10;
v86.eax = 0xf << 8;
v86int();
v86.eax &= 0x7f;
v86int();
}
I suppose that, at least with the present struct console, you'd need
to complicate the present vidc_putchar() and vidc_getchar()
considerably, though.
--
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 6 15: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 PAA17327
for freebsd-current-outgoing; Fri, 6 Nov 1998 15:02:46 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17322
for <current@freebsd.org>; Fri, 6 Nov 1998 15:02:44 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by zone.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA03334
for <current@freebsd.org>; Fri, 6 Nov 1998 18:02:14 -0500 (EST)
Date: Fri, 6 Nov 1998 18:02:14 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@zone.syracuse.net
To: current@FreeBSD.ORG
Subject: linux_clone things
Message-ID: <Pine.BSF.4.05.9811061756080.3189-100000@zone.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I need to figure out WHY this system has gotten less stable than before,
with these patches or without. When I can be sure this system itself is
stable (then I'll have to verify the patches as they are now are stable,
since they seemed to lock up relatively soon after boot...), I'll continue
work on this.
Cheers,
Brian Feldman
P.S. When I continue work on this (maybe tonight), I will be probably
using a new malloc for sigacts... 304 bytes is a pretty expensive malloc,
don't you think? OHHH now I just figured out why my patches made the
system unstable:
+ if (args->flags & CLONE_SIGHAND)
+ p2->p_sigacts = p->p_sigacts;
I'll fix this tonight.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 15: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 PAA18330
for freebsd-current-outgoing; Fri, 6 Nov 1998 15:08:49 -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 PAA18324
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 15:08:44 -0800 (PST)
(envelope-from cattelan@lupo.thebarn.com)
Received: (from cattelan@localhost)
by lupo.thebarn.com (8.9.1/8.9.1) id QAA21596;
Fri, 6 Nov 1998 16:28:08 -0600 (CST)
From: Russell Cattelan <cattelan@thebarn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 6 Nov 1998 16:28:07 -0600 (CST)
To: John Fieber <jfieber@indiana.edu>
Cc: "David E. Cross" <crossd@cs.rpi.edu>, Eivind Eklund <eivind@yes.no>,
current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.BSF.4.05.9811061348550.482-100000@fallout.campusview.indiana.edu>
References: <Pine.SGI.4.05.9811061258001.810-100000@o2.cs.rpi.edu>
<Pine.BSF.4.05.9811061348550.482-100000@fallout.campusview.indiana.edu>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <13891.30546.555159.254752@lupo.thebarn.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I've been complaining about this problem since January.
John Fieber writes:
> On Fri, 6 Nov 1998, David E. Cross wrote:
>
> > 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.
>
> If it was happening to everyone as much as it was happening to
> me, I seriously doubt 3.0 would have ever reached release
> status...having inetd die every 6 to 24 hours, httpd and sendmail
> every couple days is pretty intolerable.
>
> I've bumped my swap from 128 to 256 (I have 64 of real ram) and
> will see how that goes...it will take a couple days to tell.
>
> -john
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
--
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 Fri Nov 6 15:15:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA19206
for freebsd-current-outgoing; Fri, 6 Nov 1998 15:15:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19191
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 15:14: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 SAA06426;
Fri, 6 Nov 1998 18:14:17 -0500 (EST)
Date: Fri, 6 Nov 1998 18:14:16 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Alfred Perlstein <bright@hotjobs.com>
cc: Cory Kempf <ckempf@enigami.com>, freebsd-current@FreeBSD.ORG
Subject: Re: bad time slicing? Priorities?
In-Reply-To: <Pine.BSF.4.05.9811061159310.756-100000@porkfriedrice.ny.genx.net>
Message-ID: <Pine.BSF.4.05.9811061813001.6415-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
Of course, noone would expect the kernel to spend all of that time in the
scheduler, so for it to be real-time, people would be wondering why their
CPU was at 40% when idle.
Brian
On Fri, 6 Nov 1998, Alfred Perlstein wrote:
>
> On Fri, 6 Nov 1998, Brian Feldman wrote:
>
> > You don't really understand the scheduling. Nice the xgalaga to 0 or -1,
> > and try again. Plus, rc5des is running on BOTH CPU's (FreeBSD splits it of
> > course and switches them around to have the best performance), FreeBSD is
> > not "magic".
> >
> > Brian Feldman
>
> More like the fact that for every screen update you have a context switch
> between the game and the X server several times a second, with 2 CPU
> hungry monsters in the background they are bound to steal cycles. The
> granularity of the scheduler is for interactive typing (ie. at a terminal
> you wouldn't notice the 2 rc5's), not hi-rez/fast context switching gfx
> games. It's something expected afaik.
>
> -Alfred
>
>
> >
> > On 6 Nov 1998, Cory Kempf wrote:
> >
> > > I have a system running 3.0 SMP, with 2 333MHz PII's.
> > >
> > > On this system, I am running two copies of the Bovine RSA client (rc5des)
> > > (essentially two endless CPU bound tasks, niced down to 19)
> > >
> > > >From top:
> > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND
> > > 23593 root 105 19 832K 344K RUN 0 23.4H 98.15% 98.15% rc5des
> > > 23726 root 105 19 832K 336K CPU1 0 22.7H 97.89% 97.89% rc5des
> > >
> > > We are not swapping, or anything else obvious.
> > >
> > > If I run xgalaga (a game), which is being run at nice=5 for some
> > > reason (not sure why, haven't looked into it), It doesn't seem to be
> > > getting enough CPU time.
> > >
> > > Play is jerky and slow.
> > >
> > > This isn't what I expected. Expecially with two CPUs to play with.
> > > The rc5des programs, should essentially not be running if higher
> > > priority things are waiting to run, right? Certainly with two CPUs, I
> > > would expect that the game would get time pretty much as soon as it
> > > was ready to run, while the other tasks would fight over what was
> > > left.
> > >
> > > So, do I just not understand how BSD does its scheduling? Or is there
> > > actually something wrong?
> > >
> > > Thanks,
> > >
> > > +C
> > >
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 15:15:39 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA19258
for freebsd-current-outgoing; Fri, 6 Nov 1998 15:15:39 -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 PAA19251
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 15:15: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 SAA06452;
Fri, 6 Nov 1998 18:15:00 -0500 (EST)
Date: Fri, 6 Nov 1998 18:15:00 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: John Fieber <jfieber@indiana.edu>
cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.BSF.4.05.9811061149210.429-100000@fallout.campusview.indiana.edu>
Message-ID: <Pine.BSF.4.05.9811061814370.6415-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I haven't had this bug. And a 3.0 box at school doesn't have it either...
it's not as common as you think.
Brian Feldman
On Fri, 6 Nov 1998, John Fieber wrote:
> I've now figured out that it must be the infamous dying daemons
> bug that is biting me, and pretty bad. Inetd won't run more than
> a day without falling over. Sendmail and apache last longer, but
> not a lot.
>
> So, to date, what is known about the bug?
>
> Are there people running 3.0/Current that have not encountered
> this bug?
>
> Are there any known factors in a system configuration that
> aggrivate the problem? More to the point, is there anything
> known to suppress the problem to any degree? Some say it was
> present in 2.2.x, but I never encountered it.
>
> Here are some relevant email postings on the topic:
>
> http://www.freebsd.org/cgi/getmsg.cgi?fetch=2099086+2101942+/usr/local/www/db/text/1998/freebsd-current/19980920.freebsd-current
> http://www.freebsd.org/cgi/getmsg.cgi?fetch=649095+653248+/usr/local/www/db/text/1998/freebsd-current/19980823.freebsd-current
> http://www.freebsd.org/cgi/getmsg.cgi?fetch=786702+0+/usr/local/www/db/text/1998/freebsd-current/19980823.freebsd-current
> http://www.freebsd.org/cgi/getmsg.cgi?fetch=579190+582585+/usr/local/www/db/text/1998/freebsd-current/19980823.freebsd-current
> http://www.freebsd.org/cgi/getmsg.cgi?fetch=543833+547747+/usr/local/www/db/text/1998/freebsd-current/19980705.freebsd-current
>
> And some relevant PRs:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=7925
> http://www.freebsd.org/cgi/query-pr.cgi?pr=6858
>
> -john
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 15:58:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA24737
for freebsd-current-outgoing; Fri, 6 Nov 1998 15:58:38 -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 PAA24732
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 15:58:34 -0800 (PST)
(envelope-from zach@gaffaneys.com)
Received: (from zach@localhost)
by k6n1.znh.org (8.9.1/8.9.1) id XAA02958;
Fri, 6 Nov 1998 23:59:47 GMT
(envelope-from zach)
Message-ID: <19981106175947.A2065@znh.org>
Date: Fri, 6 Nov 1998 17:59:47 -0600
From: Zach Heilig <zach@gaffaneys.com>
To: Eivind Eklund <eivind@yes.no>, John Fieber <jfieber@indiana.edu>,
current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <Pine.BSF.4.05.9811061149210.429-100000@fallout.campusview.indiana.edu> <19981106183112.27770@follo.net>
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: <19981106183112.27770@follo.net>; from Eivind Eklund on Fri, Nov 06, 1998 at 06:31:12PM +0100
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Fri, Nov 06, 1998 at 06:31:12PM +0100, Eivind Eklund wrote:
> > Are there any known factors in a system configuration that
> > aggrivate the problem? More to the point, is there anything
> > known to suppress the problem to any degree? Some say it was
> > present in 2.2.x, but I never encountered it.
>
> Run with insane amounts of swap. 2GB ought to do the trick. I'm not
> guaranteeing this will stop the problem, but it will make it _much_
> less frequent.
>
> Eivind, who increased from 128MB to 256MB swap, and had the problem
> almost go away...
It may be interesting to know that mounting the same swap paritition twice
causes the exact same symptoms.
I didn't do this on purpose... it happened when we switched over to CAM,
both /dev/sd0s1b and /dev/da0s1b were mounted... (I let it boot, and
made my configuration changes, then went to single user and back to make
sure everything in /etc worked properly).
--
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 Fri Nov 6 16:00:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA25018
for freebsd-current-outgoing; Fri, 6 Nov 1998 16:00:50 -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 QAA25001
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 16:00:45 -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 KAA01546;
Sat, 7 Nov 1998 10:29:39 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.1/8.9.0) id KAA00850;
Sat, 7 Nov 1998 10:29:39 +1030 (CST)
Message-ID: <19981107102939.I499@freebie.lemis.com>
Date: Sat, 7 Nov 1998 10:29:39 +1030
From: Greg Lehey <grog@lemis.com>
To: Eivind Eklund <eivind@yes.no>, John Fieber <jfieber@indiana.edu>,
current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <Pine.BSF.4.05.9811061149210.429-100000@fallout.campusview.indiana.edu> <19981106183112.27770@follo.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <19981106183112.27770@follo.net>; from Eivind Eklund on Fri, Nov 06, 1998 at 06:31:12PM +0100
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Friday, 6 November 1998 at 18:31:12 +0100, Eivind Eklund wrote:
> On Fri, Nov 06, 1998 at 12:12:14PM -0500, John Fieber wrote:
>> I've now figured out that it must be the infamous dying daemons
>> bug that is biting me, and pretty bad. Inetd won't run more than
>> a day without falling over. Sendmail and apache last longer, but
>> not a lot.
>>
>> So, to date, what is known about the bug?
>
> It strike when you run out of memory, usually.
This is not a requirement. It happened again to me last night without
any memory problems. And then we had a 5 hour power blackout and my
UPS died :-(
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 16:34:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA00488
for freebsd-current-outgoing; Fri, 6 Nov 1998 16:34:53 -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 QAA00483
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 16:34:47 -0800 (PST)
(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA01701;
Sat, 7 Nov 1998 11:04:00 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.1/8.9.0) id LAA00912;
Sat, 7 Nov 1998 11:03:58 +1030 (CST)
Message-ID: <19981107110358.K499@freebie.lemis.com>
Date: Sat, 7 Nov 1998 11:03:58 +1030
From: Greg Lehey <grog@lemis.com>
To: =?iso-8859-1?Q?Dag-Erling_C=2E_Sm=F8rgrav_?= <dag-erli@ifi.uio.no>,
"Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: John Fieber <jfieber@indiana.edu>, "David E. Cross" <crossd@cs.rpi.edu>,
Eivind Eklund <eivind@yes.no>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <2826.910378788@time.cdrom.com> <xzp1zngmozz.fsf@hrotti.ifi.uio.no>
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: =?iso-8859-1?Q?=3Cxzp1zngmozz=2Efsf=40hrotti=2Eifi=2Euio=2Eno=3E=3B_from?=
=?iso-8859-1?Q?_Dag-Erling_C=2E_Sm=F8rgrav__on_Fri=2C_Nov_06=2C_1998_at_?=
=?iso-8859-1?Q?11:32:16PM_+0100?=
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Friday, 6 November 1998 at 23:32:16 +0100, Dag-Erling C. Smørgrav wrote:
> "Jordan K. Hubbard" <jkh@time.cdrom.com> writes:
>>> If it was happening to everyone as much as it was happening to
>>> me, I seriously doubt 3.0 would have ever reached release
>>> status...having inetd die every 6 to 24 hours, httpd and sendmail
>>> every couple days is pretty intolerable.
>> Have you tried that new inetd.c replacement that was posted awhile
>> back? I'm just wondering if it affects the problem. David's looked
>> at this one a bit and he can neither reproduce it nor come up with any
>> good ideas right now as to how to go about fixing it.
>
> It only addresses the "junk pointerm, too low to make sense" bug, not
> the "dying daemons" bug which John is complaining about. ISTR we
> identified that as a VM bug.
Ah. In that case, I retract my last statement, which was a junk
pointer.
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 16:35:24 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA00536
for freebsd-current-outgoing; Fri, 6 Nov 1998 16:35:24 -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 QAA00524
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 16:35:18 -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 LAA01732;
Sat, 7 Nov 1998 11:04:53 +1030 (CST)
Received: (from grog@localhost)
by freebie.lemis.com (8.9.1/8.9.0) id LAA00920;
Sat, 7 Nov 1998 11:04:53 +1030 (CST)
Message-ID: <19981107110452.L499@freebie.lemis.com>
Date: Sat, 7 Nov 1998 11:04:52 +1030
From: Greg Lehey <grog@lemis.com>
To: Eivind Eklund <eivind@yes.no>, "David E. Cross" <crossd@cs.rpi.edu>
Cc: John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <19981106183112.27770@follo.net> <Pine.SGI.4.05.9811061258001.810-100000@o2.cs.rpi.edu> <19981106200028.23174@follo.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <19981106200028.23174@follo.net>; from Eivind Eklund on Fri, Nov 06, 1998 at 08:00:28PM +0100
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Friday, 6 November 1998 at 20:00:28 +0100, Eivind Eklund wrote:
> On Fri, Nov 06, 1998 at 01:33:41PM -0500, David E. Cross wrote:
>>
>> 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.
>
> David committed some patches a while back that he said _might_ help it
> - I've not yet upgraded to test this.
Now that we seem to have identified two distinct problems, I can
confirm that David's patches did not fix the junk pointer problem.
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 18:05:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA08297
for freebsd-current-outgoing; Fri, 6 Nov 1998 18:05:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226] (may be forged))
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08288
for <current@freebsd.org>; Fri, 6 Nov 1998 18:05:03 -0800 (PST)
(envelope-from mi@video-collage.com)
X-Relay-IP:
Received: (from mi@localhost)
by xxx.video-collage.com (8.9.1a/8.9.1) id VAA10749
for current@freebsd.org; Fri, 6 Nov 1998 21:04:48 -0500 (EST)
Message-Id: <199811070204.VAA10749@xxx.video-collage.com>
Subject: same swap twice (was Re: The infamous dying daemons bug)
In-Reply-To: <19981106175947.A2065@znh.org> from Zach Heilig at "Nov 6, 1998 5:59:47 pm"
To: current@FreeBSD.ORG
Date: Fri, 6 Nov 1998 21:04:48 -0500 (EST)
From: Mikhail Teterin <mi@video-collage.com>
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+ PL48 (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
Zach Heilig once stated:
=It may be interesting to know that mounting the same swap paritition
=twice causes the exact same symptoms.
Some time back, I submitted a PR about ``swapon'' and/or underlying
calls being not picky enough to prevent this sort of mistakes from
happening. One of the gods closed the PR promptly with "Don't do it
then"...
-mi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 18: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 SAA10490
for freebsd-current-outgoing; Fri, 6 Nov 1998 18:27:59 -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 SAA10480
for <current@freebsd.org>; Fri, 6 Nov 1998 18:27: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 VAA13237
for <current@freebsd.org>; Fri, 6 Nov 1998 21:27:50 -0500 (EST)
Date: Fri, 6 Nov 1998 21:27:50 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: current@FreeBSD.ORG
Subject: RFSIGSHARE ready?
Message-ID: <Pine.BSF.4.05.9811062123460.13093-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I suppose it is. LinuxThreads don't work tho... I need %@#!^ testers!
Cheers,
Brian Feldman
--- ./i386/linux/linux_dummy.c.orig Wed Nov 4 18:04:02 1998
+++ ./i386/linux/linux_dummy.c Fri Nov 6 18:20:26 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);
--- ./i386/linux/linux_misc.c.orig Wed Nov 4 18:04:02 1998
+++ ./i386/linux/linux_misc.c Fri Nov 6 19:33:02 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,54 @@
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
+ 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);
+ 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;
+ }
+ if (args->flags & CLONE_SIGHAND)
+ p2->p_sigacts = p->p_sigacts;
+#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 */
--- ./i386/linux/linux_proto.h.orig Wed Nov 4 18:04:02 1998
+++ ./i386/linux/linux_proto.h Fri Nov 6 18:20:26 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 *)];
--- ./i386/linux/linux_syscall.h.orig Wed Nov 4 18:04:02 1998
+++ ./i386/linux/linux_syscall.h Fri Nov 6 18:20:26 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
--- ./i386/linux/linux_sysent.c.orig Wed Nov 4 18:04:02 1998
+++ ./i386/linux/linux_sysent.c Fri Nov 6 18:20:26 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 */
--- ./i386/linux/syscalls.master.orig Wed Nov 4 18:04:02 1998
+++ ./i386/linux/syscalls.master Fri Nov 6 18:20:26 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); }
--- ./kern/kern_fork.c.orig Wed Nov 4 18:04:03 1998
+++ ./kern/kern_fork.c Fri Nov 6 19:06:57 1998
@@ -321,6 +321,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)
--- ./kern/kern_exit.c.orig Wed Nov 4 18:04:03 1998
+++ ./kern/kern_exit.c Fri Nov 6 19:01:06 1998
@@ -333,6 +333,9 @@
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
* resources including address space, the kernel stack and pcb.
--- ./kern/init_main.c.orig Wed Nov 4 18:04:03 1998
+++ ./kern/init_main.c Fri Nov 6 19:00:10 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.
--- ./sys/proc.h.orig Wed Nov 4 18:04:03 1998
+++ ./sys/proc.h Fri Nov 6 18:58:45 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
@@ -75,6 +76,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.
*
@@ -165,12 +176,12 @@
#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. */
--- ./sys/unistd.h.orig Wed Nov 4 18:04:03 1998
+++ ./sys/unistd.h Fri Nov 6 18:20:27 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 */
--- ./sys/user.h.orig Fri Nov 6 18:32:09 1998
+++ ./sys/user.h Fri Nov 6 18:32:23 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!)
*/
/*
--- ./vm/vm_glue.c.orig Fri Nov 6 18:20:41 1998
+++ ./vm/vm_glue.c Fri Nov 6 18:56:12 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 Fri Nov 6 18:41:32 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA12405
for freebsd-current-outgoing; Fri, 6 Nov 1998 18:41:32 -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 SAA12400
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 18:41:31 -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 SAA05459;
Fri, 6 Nov 1998 18:41:35 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Brian Feldman <green@unixhelp.org>
cc: current@FreeBSD.ORG
Subject: Re: RFSIGSHARE ready?
In-reply-to: Your message of "Fri, 06 Nov 1998 21:27:50 EST."
<Pine.BSF.4.05.9811062123460.13093-100000@janus.syracuse.net>
Date: Fri, 06 Nov 1998 18:41:35 -0800
Message-ID: <5455.910406495@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I suppose it is. LinuxThreads don't work tho... I need %@#!^ testers!
Sounds to me like you need a developer who actually understands this
stuff a lot more than you need testers - if you already know Linux
threads don't work then what's to test? :-)
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 19:12:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA16074
for freebsd-current-outgoing; Fri, 6 Nov 1998 19:12:18 -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 TAA16069
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 19:12: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 WAA13794;
Fri, 6 Nov 1998 22:11:58 -0500 (EST)
Date: Fri, 6 Nov 1998 22:11:58 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: current@FreeBSD.ORG
Subject: Re: RFSIGSHARE ready?
In-Reply-To: <5455.910406495@time.cdrom.com>
Message-ID: <Pine.BSF.4.05.9811062211030.13730-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
Okay, touche!
Developers, I need %$#@^ developers! :)
Someone who's familiar with LinuxThreads should try helping out ;)
Cheers,
Brian Feldman
On Fri, 6 Nov 1998, Jordan K. Hubbard wrote:
> > I suppose it is. LinuxThreads don't work tho... I need %@#!^ testers!
>
> Sounds to me like you need a developer who actually understands this
> stuff a lot more than you need testers - if you already know Linux
> threads don't work then what's to test? :-)
>
> - 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 Fri Nov 6 20:45:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA23565
for freebsd-current-outgoing; Fri, 6 Nov 1998 20:45:16 -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 UAA23559
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 20:45:13 -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 VAA20290;
Fri, 6 Nov 1998 21:45:02 -0700 (MST)
Received: from wdl1.wdl.lmco.com ([137.249.32.1]) by lmco.com (PMDF V5.1-10 #20543)
with SMTP id <0F2100E07BV11J@lmco.com>; Fri, 6 Nov 1998 21:45:01 -0700 (MST)
Received: from lmco.com by wdl1.wdl.lmco.com (SMI-8.6/WDL-5.0) id UAA27165; Fri, 06 Nov 1998 20:44:58 -0800
Date: Fri, 06 Nov 1998 20:45:12 -0800
From: "George W. Dinolt" <george.w.dinolt@lmco.com>
Subject: libfetch Makefile Question
To: dag-erli@ifi.uio.no, current@FreeBSD.ORG
Message-id: <3643D057.9384BF81@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
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Dag:
I assume you are supposed to get this since your name is on the source
files. If not, would you forward to whoever is supposed to get it?
I noticed that attempting to install fetch_err.h failed in
lib/libfetch. I have most things compiled in /usr/obj/elf/src/... (left
over from a buildworld). The file fetch_err.h was constructed there as
part of the make process. The Makefile uses
${INSTALL} -C -o ${BINOWN} -g ${BINGRP} -m 444
${.CURDIR}/fetch_err.h \
${DESTDIR}/usr/include
to install the file, and of course can't find it in ${.CURDIR}. Removing
"${.CURDIR}/" from the command seems to fix things, but there might be a
better way.
Though you would like to know.
George Dinolt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 20:48:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA24073
for freebsd-current-outgoing; Fri, 6 Nov 1998 20:48:43 -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 UAA24058
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 20:48:32 -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 MAA18044;
Sat, 7 Nov 1998 12:42:14 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811070442.MAA18044@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bill Paul <wpaul@skynet.ctr.columbia.edu>
cc: phk@critter.freebsd.dk (Poul-Henning Kamp), current@FreeBSD.ORG
Subject: Re: Grrr... calcru: negative time blah blah blah
In-reply-to: Your message of "Fri, 06 Nov 1998 14:05:07 EST."
<199811061905.OAA15554@skynet.ctr.columbia.edu>
Date: Sat, 07 Nov 1998 12:42:13 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Bill Paul wrote:
[..]
> Actually, looking at the patch closer, I realize now that none of the
> warning messages actually triggered. However each time, the calcru
> messages did appear and the system console response became sluggish.
>
> I'm starting to think the problem in this case is an interrupt storm,
> but I'm not sure how to debug it. If I set up a second system to do
> a remote gdb of the first one, can I single step through things like
> interrupt handlers without Weird Things (tm) happening?
Just a thought that might be worth checking into.. Is the kstack growing
down into struct pstats, the sigacts, and perhaps pcb? This would be
highly dependent on interrupt handlers, machine load (amount of nesting)
etc and could explain why it hits some more than others.
I've talked with a couple of people about moving the pcb, sigacts, pstats
etc to the top of the two upages and have the kstack grow down from
underneath it, and possibly allow for an unmapped page below the first
UPAGE as a diagnostic tool (that will force a double panic on a kstack
overflow).
The top of stack can be tested on full stack unwind and return to user
mode if we need to.
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 21:06:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA25567
for freebsd-current-outgoing; Fri, 6 Nov 1998 21:06:43 -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 VAA25557
for <freebsd-current@freebsd.org>; Fri, 6 Nov 1998 21:06:37 -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 WAA23220
for <freebsd-current@freebsd.org>; Fri, 6 Nov 1998 22:06:25 -0700 (MST)
Received: from wdl1.wdl.lmco.com ([137.249.32.1]) by lmco.com (PMDF V5.1-10 #20543) with SMTP id <0F2100E4GCUP1J@lmco.com> for
freebsd-current@freebsd.org; Fri, 6 Nov 1998 22:06:25 -0700 (MST)
Received: from lmco.com by wdl1.wdl.lmco.com (SMI-8.6/WDL-5.0) id VAA27299; Fri, 06 Nov 1998 21:06:23 -0800
Date: Fri, 06 Nov 1998 21:06:36 -0800
From: "George W. Dinolt" <george.w.dinolt@lmco.com>
Subject: Boot Loader question
To: freebsd-current@FreeBSD.ORG
Message-id: <3643D55C.DE98C1E7@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
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I have a question about the new bootloader. I have been using the
loader successfully including preloading .ko files and "load -t
userconfig_script..." commands with great success. The process seems to
work very well. The problem is that I boot several different versions of
FreeBSD and like to use a "floppy" to start the boot process off.
Different floppies point to different disks or diskpartitions. Currently
I have configured a floppy using
disklabel -B /dev/fd0
and a boot.config file which contains, for example, the command
3:da(0,a)boot/loader
When I boot from the floppy, this causes the loader on my 3rd scsi disk
to run. This all works great.
I would like to be able to use the boot1 and boot2 from /boot on the
floppy. This does not seem to work. When I try the command
disklabel -B -b /boot/boot1 -s /boot/boot2 /dev/fd0
and then boot off the floppy I get an error and the system hangs in the
first boot phase. I can, of course, just ignore the problem for the
time being, but if/when the new files replace the current ones in
/usr/mdec, there could be problems.
Anyone have any suggestions?
George Dinolt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 21:58:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA28591
for freebsd-current-outgoing; Fri, 6 Nov 1998 21:58:28 -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 VAA28582
for <current@freebsd.org>; Fri, 6 Nov 1998 21:58:27 -0800 (PST)
(envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
by cheddar.netmonger.net (8.8.8/8.8.8) id AAA09441;
Sat, 7 Nov 1998 00:58:14 -0500 (EST)
Message-ID: <19981107005814.A8603@netmonger.net>
Date: Sat, 7 Nov 1998 00:58:14 -0500
From: Christopher Masto <chris@netmonger.net>
To: current@FreeBSD.ORG
Subject: Lock up on accessing sio?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
A friend of mine has had a 486 running 2.2.5-STABLE as a router and
fax server for over a year. Tonight we decided to upgrade it to
3.0-CURRENT as a prelude to experimenting with ipfw. Unfortunately,
now the machine locks up tight whenever we access the modem. This
machine has an interal el-cheapo of some kind (probably an old USR
14.4).. the internal serial port has been turned off in the BIOS. It
worked perfectly under the 2.2.5-STABLE it had (I don't know the exact
date offhand), but now even a "cu -l /dev/cuaa0" will instantly freeze
the machine. DDB is compiled in, but Ctrl-Alt-Esc does nothing. It
is very much buried under other equipment, and it got late, so I
haven't had a chance to try turning the serial port back on to see if
I can get a stack trace. I'm hoping that maybe this sounds familiar
to someone.
As another data point, we had previously tried putting 2.2.7-STABLE on
it, and it was locking up right after booting.. it's possible that the
faxgetty in /etc/ttys is what was doing it. The kernel on it now is
from yesterday afternoon's cvsup, but we see the same lockup with the
3.0-RELEASE kernel.
Here are the boot messages:
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 6 21:17:05 EST 1998
chris@lion-around.at.yiff.net:/usr/local/usr-src/sys/compile/ITGATE
Timecounter "i8254" frequency 1193182 Hz
CPU: AMD Enhanced Am486DX4 Write-Back (486-class CPU)
Origin = "AuthenticAMD" Id = 0x494 Stepping=4
Features=0x1<FPU>
real memory = 16777216 (16384K bytes)
config> quit
avail memory = 14184448 (13852K bytes)
Preloaded a.out kernel "kernel" at 0xf0267000.
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
ed0 at 0x300-0x31f irq 3 on isa
ed0: address 00:60:67:00:2a:35, type NE2000 (16 bit)
ed1 at 0x280-0x29f irq 5 on isa
ed1: address 00:60:67:00:2a:3d, type NE2000 (16 bit)
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 8250
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <SAMSUNG SHD-30560A (APRO-5) SSI>
wd0: 534MB (1094688 sectors), 1086 cyls, 16 heads, 63 S/T, 512 B/S
npx0 on motherboard
npx0: INT 16 interface
WARNING: / was not properly dismounted
The "configured irq 4 not in bitmap" line also appeared when booting
2.2.5.. I don't think it's significant.
Any ideas? I've got to go away for the weekend, but when I get back,
I'll be able to pull the machine out of the pile and start
experimenting.
--
Christopher Masto Director of Operations S NetMonger Communications
chris@netmonger.net info@netmonger.net SSS http://www.netmonger.net
\_/
- - - --- --- --- - - - - - - --- --- --- - - -
DO YOU DOIDY!!!!!!!!!!!!
Get your free beable beable beable at Schenectady
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Fri Nov 6 23:35:46 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA05650
for freebsd-current-outgoing; Fri, 6 Nov 1998 23:35:46 -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 XAA05641
for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 23:35:44 -0800 (PST)
(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id IAA10255;
Sat, 7 Nov 1998 08:32:38 +0100 (CET)
To: Peter Wemm <peter@netplex.com.au>
cc: Bill Paul <wpaul@skynet.ctr.columbia.edu>, current@FreeBSD.ORG
Subject: Re: Grrr... calcru: negative time blah blah blah
In-reply-to: Your message of "Sat, 07 Nov 1998 12:42:13 +0800."
<199811070442.MAA18044@spinner.netplex.com.au>
Date: Sat, 07 Nov 1998 08:32:38 +0100
Message-ID: <10253.910423958@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 <199811070442.MAA18044@spinner.netplex.com.au>, Peter Wemm writes:
>> I'm starting to think the problem in this case is an interrupt storm,
>> but I'm not sure how to debug it. If I set up a second system to do
>> a remote gdb of the first one, can I single step through things like
>> interrupt handlers without Weird Things (tm) happening?
>
>Just a thought that might be worth checking into.. Is the kstack growing
>down into struct pstats, the sigacts, and perhaps pcb? This would be
>highly dependent on interrupt handlers, machine load (amount of nesting)
>etc and could explain why it hits some more than others.
Peter, this would probably lead to much more bogosity than what we see
here, but you suggestion for a trapdoor under the stack is certainly
worthwhile in its own right.
--
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 Fri Nov 6 23:51:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id XAA06388
for freebsd-current-outgoing; Fri, 6 Nov 1998 23:51:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles131.castles.com [208.214.165.131])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06382
for <freebsd-current@FreeBSD.ORG>; Fri, 6 Nov 1998 23:51:01 -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 XAA00452;
Fri, 6 Nov 1998 23:50:17 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811070750.XAA00452@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "George W. Dinolt" <george.w.dinolt@lmco.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Boot Loader question
In-reply-to: Your message of "Fri, 06 Nov 1998 21:06:36 PST."
<3643D55C.DE98C1E7@lmco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 06 Nov 1998 23:50:16 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I have a question about the new bootloader. I have been using the
> loader successfully including preloading .ko files and "load -t
> userconfig_script..." commands with great success. The process seems to
> work very well. The problem is that I boot several different versions of
> FreeBSD and like to use a "floppy" to start the boot process off.
> Different floppies point to different disks or diskpartitions. Currently
> I have configured a floppy using
> disklabel -B /dev/fd0
> and a boot.config file which contains, for example, the command
> 3:da(0,a)boot/loader
> When I boot from the floppy, this causes the loader on my 3rd scsi disk
> to run. This all works great.
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 would like to be able to use the boot1 and boot2 from /boot on the
> floppy. This does not seem to work. When I try the command
> disklabel -B -b /boot/boot1 -s /boot/boot2 /dev/fd0
> and then boot off the floppy I get an error and the system hangs in the
> first boot phase. I can, of course, just ignore the problem for the
> time being, but if/when the new files replace the current ones in
> /usr/mdec, there could be problems.
Firstly, the new files won't be replacing the old ones in /usr/mdec;
the directory will be going away.
However, to help you we need to know *what* the error is.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 00:12:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA07857
for freebsd-current-outgoing; Sat, 7 Nov 1998 00:12:20 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m1-44-dbn.dial-up.net [196.34.155.44])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07846
for <freebsd-current@FreeBSD.ORG>; Sat, 7 Nov 1998 00:12:13 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id KAA07985; Sat, 7 Nov 1998 10:11:02 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199811070811.KAA07985@ceia.nordier.com>
Subject: Re: Boot Loader question
In-Reply-To: <3643D55C.DE98C1E7@lmco.com> from "George W. Dinolt" at "Nov 6, 98 09:06:36 pm"
To: george.w.dinolt@lmco.com (George W. Dinolt)
Date: Sat, 7 Nov 1998 10:10:59 +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
George W. Dinolt wrote:
> I would like to be able to use the boot1 and boot2 from /boot on the
> floppy. This does not seem to work. When I try the command
> disklabel -B -b /boot/boot1 -s /boot/boot2 /dev/fd0
> and then boot off the floppy I get an error and the system hangs in the
> first boot phase. I can, of course, just ignore the problem for the
> time being, but if/when the new files replace the current ones in
> /usr/mdec, there could be problems.
When you say "I get an error" do you mean a diagnostic, or are you
just emphasizing that things aren't working right?
I have substantially revised boot1 and should be committing this
within the next day or two. Until now, we've been making use of
a new set of BIOS extended disk services, but it has become painfully
evident that a few BIOSes have problems with this approach, and they
really weren't much of a win, anyway.
>
> Anyone have any suggestions?
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.
--
Robert Nordier
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 00:23:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA08505
for freebsd-current-outgoing; Sat, 7 Nov 1998 00:23: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 AAA08499
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 00:23:49 -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 AAA08224;
Sat, 7 Nov 1998 00:22:12 -0800 (PST)
(envelope-from dwhite@resnet.uoregon.edu)
Date: Sat, 7 Nov 1998 00:22:11 -0800 (PST)
From: Doug White <dwhite@resnet.uoregon.edu>
To: "Alexander B. Povolotsky" <tarkhil@synchroline.ru>
cc: current@FreeBSD.ORG
Subject: Re: What is wrong?
In-Reply-To: <199811061450.RAA21718@enterprise.sl.ru>
Message-ID: <Pine.BSF.4.03.9811070021230.6949-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 Fri, 6 Nov 1998, Alexander B. Povolotsky wrote:
> Hello!
>
> on
>
> 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
>
> attempt to run cvsup (extracted from ports/net/cvsup-binary) leads to
>
> ELF interpreter /usr/libexec/ld-elf.so.1 not found
>
> What can be wrong?
The cvsup binary you extracted is in ELF format and your systemhasn't been
transitioned to ELF yet. Grab a new -CURRENT and run 'make aout-to-elf'
to update yourself.
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 Sat Nov 7 00:59:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id AAA10642
for freebsd-current-outgoing; Sat, 7 Nov 1998 00:59:01 -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 AAA10637
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 00:58:56 -0800 (PST)
(envelope-from dag-erli@ifi.uio.no)
Received: from hvergelmir.ifi.uio.no (2602@hvergelmir.ifi.uio.no [129.240.64.129])
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id JAA04441;
Sat, 7 Nov 1998 09:58:42 +0100 (MET)
Received: (from dag-erli@localhost) by hvergelmir.ifi.uio.no ; Sat, 7 Nov 1998 09:58:42 +0100 (MET)
Mime-Version: 1.0
To: "George W. Dinolt" <george.w.dinolt@lmco.com>
Cc: current@FreeBSD.ORG
Subject: Re: libfetch Makefile Question
References: <3643D057.9384BF81@lmco.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: 07 Nov 1998 09:58:40 +0100
In-Reply-To: "George W. Dinolt"'s message of "Fri, 06 Nov 1998 20:45:12 -0800"
Message-ID: <xzpd86zj2v3.fsf@hvergelmir.ifi.uio.no>
Lines: 29
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 AAA10638
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
"George W. Dinolt" <george.w.dinolt@lmco.com> writes:
> I assume you are supposed to get this since your name is on the source
> files. If not, would you forward to whoever is supposed to get it?
Yes, I am the author of libfetch.
> I noticed that attempting to install fetch_err.h failed in
> lib/libfetch. I have most things compiled in /usr/obj/elf/src/... (left
> over from a buildworld). The file fetch_err.h was constructed there as
> part of the make process. The Makefile uses
>
> ${INSTALL} -C -o ${BINOWN} -g ${BINGRP} -m 444
> ${.CURDIR}/fetch_err.h \
> ${DESTDIR}/usr/include
>
> to install the file, and of course can't find it in ${.CURDIR}. Removing
> "${.CURDIR}/" from the command seems to fix things, but there might be a
> better way.
Yes, I forgot that since fetch_err.h is a generated file it resides in
${OBJDIR}, not ${.CURDIR}.
> Though you would like to know.
Yes, thank you very much.
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 Sat Nov 7 02:10:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id CAA17288
for freebsd-current-outgoing; Sat, 7 Nov 1998 02:10:42 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from limes.NIC.DTAG.DE (limes.NIC.DTAG.DE [194.25.1.113])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17278
for <freebsd-current@FreeBSD.ORG>; Sat, 7 Nov 1998 02:10:37 -0800 (PST)
(envelope-from bm@Reineke.malepartus.de)
Received: from kronos.NIC.DTAG.DE (kronos.NIC.DTAG.DE [194.25.1.92])
by limes.NIC.DTAG.DE (8.8.5/8.8.3) with ESMTP id LAA19623
for <freebsd-current@FreeBSD.ORG>; Sat, 7 Nov 1998 11:09:03 +0100 (MET)
Received: from Reineke.malepartus.de (reineke.malepartus.de [194.25.4.66])
by kronos.NIC.DTAG.DE (8.8.5/8.7.1) with ESMTP id LAA24531
for <freebsd-current@FreeBSD.ORG>; Sat, 7 Nov 1998 11:10:19 +0100 (MET)
Received: from Reineke.malepartus.de (localhost.Malepartus.de [127.0.0.1])
by Reineke.malepartus.de (8.8.8/8.8.8) with ESMTP id LAA03344
for <freebsd-current@FreeBSD.ORG>; Sat, 7 Nov 1998 11:10:17 +0100 (MET)
(envelope-from bm@Reineke.malepartus.de)
Message-Id: <199811071010.LAA03344@Reineke.malepartus.de>
X-Mailer: exmh version 2.0.2 2/24/98
From: Burkard Meyendriesch <bm@malepartus.de>
Subject: upgrading from -stable to -current
To: freebsd-current@FreeBSD.ORG
Reply-To: bm@malepartus.de
X-organization: The home of Reineke Fuchs
X-GPOS: 52.0844N 7.9081E
X-phone: +49 5484 96097
X-pgp-fingerprint: DF 83 04 CD B5 D1 10 43 57 4C AD 9A B1 02 28 17
X-face: "[-;]oI+8gP9>*J%knDN8d%DuhvJS2Lj4L\bRb7gz(pcT?2Zh6_Vam_6csAum3$<&lhAFd^
jt|!&Ut1C~Vg*E/q}+#cbFg-GU]c.bB8Ad,L'W$'9{^0y'AzM4#hS[C[F-1'|O;Kg3V<ZJKG3g9Fs-
kuovqp|S7(.wC"D@/O5xcb^PSDJU#jyt`tp^7Trg239:o9bDVm\{6J,`P<>rq5q6dsU*TmJ@}+QPM\
b[^<zL1qL^&)o'{%T@Q&p)N$OZ:aDa(r2f5?52HuGmO'm>9Rhd,UoMpRpd5k[X=h.Dom*kbT`cNQ
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 07 Nov 1998 11:10:16 +0100
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA17282
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi,
last night I tried to upgrade my -stable system (CTM src-2.2 799) with
CAM-Patches 2.2CAM-19980716-SNAP.diffs.gz to the -current tree. I made
a new /usr/src directory and got (CTM src-cur 3605).
But when trying do "make buildworld" exactly NOTHING happens; a ktrace -di
of the make process shows that "objformat" is waiting for stdin:
...
3322 objformat CALL readlink(0x200733e2,0xefbfd8a4,0x3f)
3322 objformat NAMI "/etc/malloc.conf"
3322 objformat RET readlink -1 errno 2 No such file or directory
3322 objformat CALL mmap(0,0x1000,0x3,0x1002,0xffffffff,0,0,0)
3322 objformat RET mmap 537001984/0x20020000
3322 objformat CALL break(0xa000)
3322 objformat RET break 0
3322 objformat CALL break(0x1a000)
3322 objformat RET break 0
3322 objformat CALL ioctl(0,TIOCGETA,0xefbfd8e4)
3322 objformat RET ioctl 0
3322 objformat CALL read(0,0xa000,0x10000)
What's going wrong here? Can anybody please help me?
Burkard
--
* Burkard Meyendriesch ___ bm@malepartus.de *
* Hauptstrasse 45 ________|________ tel +49 5484 96097 *
* D-49219 Glandorf-Schwege 0 52 05'05"N 07 54'29"E *
* PGP-Fingerprint DF 83 04 CD B5 D1 10 43 57 4C AD 9A B1 02 28 17 *
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 03:38:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id DAA22372
for freebsd-current-outgoing; Sat, 7 Nov 1998 03:38:47 -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 DAA22364
for <current@freebsd.org>; Sat, 7 Nov 1998 03:38:41 -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 OAA15356
for <current@freebsd.org>; Sat, 7 Nov 1998 14:38:28 +0300 (MSK)
Date: Sat, 7 Nov 1998 14:38:28 +0300 (MSK)
From: Dmitry Valdov <dv@dv.ru>
X-Sender: dv@xkis.kis.ru
To: current@FreeBSD.ORG
Subject: make world problem
Message-ID: <Pine.BSF.3.95q.981107143734.15346A-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!
===> libfetch
install -C -o root -g wheel -m 444 /usr/src/lib/libfetch/fetch.h
/usr/obj/elf/usr/src/tmp/usr/include
install -C -o root -g wheel -m 444 /usr/src/lib/libfetch/fetch_err.h
/usr/obj/elf/usr/src/tmp/usr/include
install: /usr/src/lib/libfetch/fetch_err.h: No such file or directory
*** Error code 71
Dmitry.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 04:29:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA29837
for freebsd-current-outgoing; Sat, 7 Nov 1998 04:29:49 -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 EAA29832
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 04:29:47 -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 NAA09636;
Sat, 7 Nov 1998 13:34:09 +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 NAA09535;
Sat, 7 Nov 1998 13:53:51 +0100 (CET)
Received: (from uucp@localhost)
by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) with UUCP id NAA20071;
Sat, 7 Nov 1998 13:28:51 +0100 (CET)
Received: (from regnauld@localhost)
by stimpy.prosa.dk (8.9.1/8.9.1/stimpy-1.0) id BAA18178;
Sat, 7 Nov 1998 01:15:10 +0100 (CET)
(envelope-from regnauld)
Message-ID: <19981107011509.07130@stimpy.prosa.dk>
Date: Sat, 7 Nov 1998 01:15:09 +0100
From: Phil Regnauld <regnauld@EU.org>
To: Mikael Karpberg <karpen@ocean.campus.luth.se>
Cc: current@FreeBSD.ORG
Subject: Re: config option VESA
References: <199811032303.AAA02645@ocean.campus.luth.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.88e
In-Reply-To: <199811032303.AAA02645@ocean.campus.luth.se>; from Mikael Karpberg on Wed, Nov 04, 1998 at 12:03:25AM +0100
X-Operating-System: FreeBSD 3.0-RELEASE 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
Mikael Karpberg writes:
> Hi!
>
> Take a GENERIC config file, add ``option "VM86"'' and config, make, install.
> Reboot. Works fine. Add ``option VESA'' too. Repeat. Boots and crashes what
> looks like just before starting the rc scripts. "Page not present" panic.
Same here.
> It says in LINT to not use VESA with SMP. But I have a UP Pentium.
Yup. I tried it on my Libretto 70 (which I'm quite sure is not
multiprocessor :-)
VM86 -> ok (I use it to run some dos based dictionary)
VM86 + VESA -> boom.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 04:31:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA00235
for freebsd-current-outgoing; Sat, 7 Nov 1998 04:31:28 -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 EAA00230
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 04:31:26 -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 NAA09640;
Sat, 7 Nov 1998 13:34:11 +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 NAA09539;
Sat, 7 Nov 1998 13:53:52 +0100 (CET)
Received: (from uucp@localhost)
by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) with UUCP id NAA20072;
Sat, 7 Nov 1998 13:28:52 +0100 (CET)
Received: (from regnauld@localhost)
by stimpy.prosa.dk (8.9.1/8.9.1/stimpy-1.0) id BAA18211;
Sat, 7 Nov 1998 01:20:11 +0100 (CET)
(envelope-from regnauld)
Message-ID: <19981107012011.41885@stimpy.prosa.dk>
Date: Sat, 7 Nov 1998 01:20:11 +0100
From: Phil Regnauld <regnauld@EU.org>
To: tarkhil@synchroline.ru
Cc: current@FreeBSD.ORG
Subject: Re: Problem with dummynet on RELEASE
References: <199811061901.WAA01279@enterprise.sl.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.88e
In-Reply-To: <199811061901.WAA01279@enterprise.sl.ru>; from Alexander B. Povolotsky on Fri, Nov 06, 1998 at 10:01:46PM +0300
X-Operating-System: FreeBSD 3.0-RELEASE 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
Alexander B. Povolotsky writes:
> Hello!
>
> dummynet patch added references to two include files, opt_bdg.h and
> opt_ipdn.h. Where should I find them?...
Yes, the stuff included in the xperimnt is missing a patch
to /sys/conf/files and/or /sys/conf/options (have to check)
to create those two files.
Luigi will be releasing a new version soon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 04:44:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id EAA01198
for freebsd-current-outgoing; Sat, 7 Nov 1998 04:44:48 -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 EAA01189
for <current@freebsd.org>; Sat, 7 Nov 1998 04:44:46 -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 0zc7j7-0004tN-00; Sat, 7 Nov 1998 12:44:26 +0000
Received: by WGP01 with Internet Mail Service (5.5.1960.3)
id <W2PQAPHH>; Sat, 7 Nov 1998 12:57:15 -0000
Message-ID: <32BABEF63EAED111B2C5204C4F4F5020180B@WGP01>
From: James Mansion <james@westongold.com>
To: Daniel Eischen <eischen@vigrid.com>,
James Mansion
<james@westongold.com>, peter@netplex.com.au
Cc: current@FreeBSD.ORG, jb@cimlogic.com.au, lists@tar.com
Subject: RE: Kernel threading (was Re: Thread Scheduler bug)
Date: Sat, 7 Nov 1998 12:57:08 -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
> From: Daniel Eischen [mailto:eischen@vigrid.com]
> > *My* concern is that pthread_self, and access to
> thread-specific data,
> > should be as fast as possible. Writing thread-hot libraries without
> > good thread specific data is irksome to say the least.
>
> My point was that you can't have just one common pointer (address)
> to TSD that is changed on thread schedule as it would limit you
> to being able to execute only one thread per process at a time.
> To take advantage of multiple processors, you'd need at least
> as many TSD pointers as CPUs. Julian discussed this in a previous
> response.
Sure you can. But you can't share the same page map between all
the threads (or at least between all the kernel threads that are
executing in the process).
The costs have been discussed. I didn't say it was going to be
convenient or that it wouldn't make a difference to the cost of
rescheduling a kernel thread onto a new user thread.
Whether these costs are worthwhile, or whether the same effect can
be achieved more effectively, is surely the point of the discussion.
James
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 05:21:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA02656
for freebsd-current-outgoing; Sat, 7 Nov 1998 05:21:19 -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 FAA02651
for <current@freebsd.org>; Sat, 7 Nov 1998 05:21:15 -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 PAA06608;
Sat, 7 Nov 1998 15:20:59 +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 PAA29803;
Sat, 7 Nov 1998 15:20:39 +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 PAA23544;
Sat, 7 Nov 1998 15:14:49 +0200 (EET)
(envelope-from archer)
Date: Sat, 7 Nov 1998 15:14:49 +0200 (EET)
From: Alexander Litvin <archer@lucky.net>
Message-Id: <199811071314.PAA23544@grape.carrier.kiev.ua>
To: Brian Feldman <green@unixhelp.org>
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
X-Newsgroups: grape.freebsd.current
In-Reply-To: <Pine.BSF.4.05.9811061814370.6415-100000@janus.syracuse.net>
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 <Pine.BSF.4.05.9811061814370.6415-100000@janus.syracuse.net> you wrote:
BF> I haven't had this bug. And a 3.0 box at school doesn't have it either...
BF> it's not as common as you think.
Have you beaten your systems to "swap_pager: out of swap space"?
My system may run for months without any problem. It's home box
-- 32M RAM + 128M swap, and it is enough for day-to-day operation.
But when I artificially overload it, it easily shows all that
sendmails exiting on signal 11, cron jobs not run, etc.
BF> Brian Feldman
---
Did you know ...
That no-one ever reads these things?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 05:41:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id FAA04133
for freebsd-current-outgoing; Sat, 7 Nov 1998 05:41:38 -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 FAA04128
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 05:41:36 -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 IAA19833;
Sat, 7 Nov 1998 08:44:13 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Sat, 7 Nov 1998 08:44:13 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: Brian Feldman <green@unixhelp.org>
cc: John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.BSF.4.05.9811061814370.6415-100000@janus.syracuse.net>
Message-ID: <Pine.BSF.4.05.9811070842320.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
Simple idea, ask everyone with this bug to please show every piece of
hardware in thier box (dmesg) after boot -v.
If it is a hardware device or a driver misbehaving it shouldn't be that
hard to find a commonality considering how much PC hardware varies.
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 Fri, 6 Nov 1998, Brian Feldman wrote:
> I haven't had this bug. And a 3.0 box at school doesn't have it either...
> it's not as common as you think.
>
> Brian Feldman
>
> On Fri, 6 Nov 1998, John Fieber wrote:
>
> > I've now figured out that it must be the infamous dying daemons
> > bug that is biting me, and pretty bad. Inetd won't run more than
> > a day without falling over. Sendmail and apache last longer, but
> > not a lot.
> >
> > So, to date, what is known about the bug?
> >
> > Are there people running 3.0/Current that have not encountered
> > this bug?
> >
> > Are there any known factors in a system configuration that
> > aggrivate the problem? More to the point, is there anything
> > known to suppress the problem to any degree? Some say it was
> > present in 2.2.x, but I never encountered it.
> >
> > Here are some relevant email postings on the topic:
> >
> > http://www.freebsd.org/cgi/getmsg.cgi?fetch=2099086+2101942+/usr/local/www/db/text/1998/freebsd-current/19980920.freebsd-current
> > http://www.freebsd.org/cgi/getmsg.cgi?fetch=649095+653248+/usr/local/www/db/text/1998/freebsd-current/19980823.freebsd-current
> > http://www.freebsd.org/cgi/getmsg.cgi?fetch=786702+0+/usr/local/www/db/text/1998/freebsd-current/19980823.freebsd-current
> > http://www.freebsd.org/cgi/getmsg.cgi?fetch=579190+582585+/usr/local/www/db/text/1998/freebsd-current/19980823.freebsd-current
> > http://www.freebsd.org/cgi/getmsg.cgi?fetch=543833+547747+/usr/local/www/db/text/1998/freebsd-current/19980705.freebsd-current
> >
> > And some relevant PRs:
> >
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=7925
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=6858
> >
> > -john
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-current" in the body of the message
> >
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 06:16:53 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA06171
for freebsd-current-outgoing; Sat, 7 Nov 1998 06:16:53 -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 GAA06166
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 06:16:52 -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 JAA09667;
Sat, 7 Nov 1998 09:16:27 -0500 (EST)
Date: Sat, 7 Nov 1998 09:16:27 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Alexander Litvin <archer@lucky.net>
cc: Brian Feldman <green@unixhelp.org>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <199811071314.PAA23544@grape.carrier.kiev.ua>
Message-ID: <Pine.BSF.4.05.9811070904250.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 Sat, 7 Nov 1998, Alexander Litvin wrote:
> In article <Pine.BSF.4.05.9811061814370.6415-100000@janus.syracuse.net> you wrote:
> BF> I haven't had this bug. And a 3.0 box at school doesn't have it either...
> BF> it's not as common as you think.
>
> Have you beaten your systems to "swap_pager: out of swap space"?
The meaning of this messages is reasonably clean and I have seen
it before (although not since upgrading to 3.0 and meeting the
dying daemons bug), but I have on occasion seen:
smap_pager: suggest more swap space: 125 MB
I assume it is a warning that I'm about to run out, but what does
the 125MB mean? I have 128MB of swap. If it means that 125MB is
used, it would be much less cryptic to qualify it along the lines
of "only 3MB free" or "125MB out of 128MB used" or "98% used" or
"2% free". To be consistent with "out of swap space", maybe it
should say "almost out of swap space".
So, what is the correct interpretation of this message, and the
125MB in particular?
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 06: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 GAA06880
for freebsd-current-outgoing; Sat, 7 Nov 1998 06:28:00 -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 GAA06875
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 06:27:54 -0800 (PST)
(envelope-from dag-erli@ifi.uio.no)
Received: from hvergelmir.ifi.uio.no (2602@hvergelmir.ifi.uio.no [129.240.64.129])
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id PAA26525;
Sat, 7 Nov 1998 15:27:32 +0100 (MET)
Received: (from dag-erli@localhost) by hvergelmir.ifi.uio.no ; Sat, 7 Nov 1998 15:27:32 +0100 (MET)
Mime-Version: 1.0
To: Dmitry Valdov <dv@dv.ru>
Cc: current@FreeBSD.ORG
Subject: Re: make world problem
References: <Pine.BSF.3.95q.981107143734.15346A-100000@xkis.kis.ru>
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: 07 Nov 1998 15:27:31 +0100
In-Reply-To: Dmitry Valdov's message of "Sat, 7 Nov 1998 14:38:28 +0300 (MSK)"
Message-ID: <xzppvazh92k.fsf@hvergelmir.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 GAA06876
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Dmitry Valdov <dv@dv.ru> writes:
> ===> libfetch
> install -C -o root -g wheel -m 444 /usr/src/lib/libfetch/fetch.h
> /usr/obj/elf/usr/src/tmp/usr/include
> install -C -o root -g wheel -m 444 /usr/src/lib/libfetch/fetch_err.h
> /usr/obj/elf/usr/src/tmp/usr/include
> install: /usr/src/lib/libfetch/fetch_err.h: No such file or directory
> *** Error code 71
Fixed. The Makefile looked for fetch_err.h in ${.CURDIR}, even though
it's generated and therefore lives in ${OBJDIR}.
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 Sat Nov 7 06:55:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id GAA08718
for freebsd-current-outgoing; Sat, 7 Nov 1998 06:55:10 -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 GAA08703
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 06:55:06 -0800 (PST)
(envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id JAA20657;
Sat, 7 Nov 1998 09:54:44 -0500 (EST)
Date: Sat, 7 Nov 1998 09:54:44 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Alexander Litvin <archer@lucky.net>
cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <199811071314.PAA23544@grape.carrier.kiev.ua>
Message-ID: <Pine.BSF.4.05.9811070954270.20572-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I'll do that right now. I'll tell you if inetd/exim/whatever die.
Brian feldman
On Sat, 7 Nov 1998, Alexander Litvin wrote:
> In article <Pine.BSF.4.05.9811061814370.6415-100000@janus.syracuse.net> you wrote:
> BF> I haven't had this bug. And a 3.0 box at school doesn't have it either...
> BF> it's not as common as you think.
>
> Have you beaten your systems to "swap_pager: out of swap space"?
>
> My system may run for months without any problem. It's home box
> -- 32M RAM + 128M swap, and it is enough for day-to-day operation.
> But when I artificially overload it, it easily shows all that
> sendmails exiting on signal 11, cron jobs not run, etc.
>
> BF> Brian Feldman
>
> ---
> Did you know ...
>
>
>
>
>
>
>
> That no-one ever reads these things?
>
> 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 7 07:15:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id HAA09783
for freebsd-current-outgoing; Sat, 7 Nov 1998 07:15:52 -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 HAA09770
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 07:15:46 -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 KAA20842;
Sat, 7 Nov 1998 10:15:28 -0500 (EST)
Date: Sat, 7 Nov 1998 10:15:28 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Alexander Litvin <archer@lucky.net>
cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <199811071314.PAA23544@grape.carrier.kiev.ua>
Message-ID: <Pine.BSF.4.05.9811071011530.20572-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
avail memory = 78680064 (76836K bytes)
Device 1K-blocks Used Avail Capacity Type
/dev/wd0s1b 102400 13940 88332 14% Interleaved
/dev/wd1s1b 102400 13608 88664 13% Interleaved
Total 204544 27548 176996 13%
swap_pager: suggest more swap space: 157 MB
swap_pager: out of swap space
pid 14846 (memory), uid 1000, was killed: out of swap space
pid 14846 (memory), uid 1000, was killed: out of swap space
No problems at all. Cron runs (at works), inetd works, exim works...
Cheers,
Brian Feldman
On Sat, 7 Nov 1998, Alexander Litvin wrote:
> In article <Pine.BSF.4.05.9811061814370.6415-100000@janus.syracuse.net> you wrote:
> BF> I haven't had this bug. And a 3.0 box at school doesn't have it either...
> BF> it's not as common as you think.
>
> Have you beaten your systems to "swap_pager: out of swap space"?
>
> My system may run for months without any problem. It's home box
> -- 32M RAM + 128M swap, and it is enough for day-to-day operation.
> But when I artificially overload it, it easily shows all that
> sendmails exiting on signal 11, cron jobs not run, etc.
>
> BF> Brian Feldman
>
> ---
> Did you know ...
>
>
>
>
>
>
>
> That no-one ever reads these things?
>
> 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 7 08: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 IAA12778
for freebsd-current-outgoing; Sat, 7 Nov 1998 08:07:09 -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 IAA12765
for <freebsd-current@FreeBSD.ORG>; Sat, 7 Nov 1998 08:07:04 -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 DAA02999;
Sun, 8 Nov 1998 03:06:27 +1100
Date: Sun, 8 Nov 1998 03:06:27 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811071606.DAA02999@godzilla.zeta.org.au>
To: dfr@nlsystems.com, wollman@khavrinen.lcs.mit.edu
Subject: Re: nfs.ko panics on unloading
Cc: abial@nask.pl, freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>> > code). Unfortunately the vfs system itself doesn't support unloading yet
>> > (a project for someone there).
>>
>> It certainly did before! NFS never did, no, because there was no way
>> to undefine a syscall, but when I first implemented VFS LKMs, you
>> definitely could unload them (provided that the reference count was
>> zero).
>
>I must be blind! I didn't even see vfs_unregister(). I'll tweak my patch
I fixed most of the unloading problems in the NFS LKM before 3.0R. See
nfs_uninit().
Most vfs's, including nfs, don't actually support unloading, because
of bitrot in malloc() -- malloc_init() creates pointers that are left
dangling after unload.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 09:15:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA16482
for freebsd-current-outgoing; Sat, 7 Nov 1998 09:15:28 -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 JAA16476
for <current@freebsd.org>; Sat, 7 Nov 1998 09:15:27 -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 MAA20011
for <current@freebsd.org>; Sat, 7 Nov 1998 12:18:06 -0500 (EST)
(envelope-from bright@hotjobs.com)
X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs
Date: Sat, 7 Nov 1998 12:18:06 -0500 (EST)
From: Alfred Perlstein <bright@hotjobs.com>
X-Sender: bright@porkfriedrice.ny.genx.net
To: current@FreeBSD.ORG
Subject: O_SYNC
Message-ID: <Pine.BSF.4.05.9811071213160.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
this is defined on a lot of archs in include/sys/fnctl.h
fcntl.h:#define O_SYNC 0x10 /* synchronized file update option
*/
is there a similar op for freebsd? and if so, why is it different than
everyone else?
afaik it implies fsync() on every write().
when i come across and app that uses it i usually just #define it to zero
and things work, although it might cause a loss of robustness of certain
apps. Can someone commit this as a synonym to what we use?
thanks,
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 Sat Nov 7 09:44:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA19323
for freebsd-current-outgoing; Sat, 7 Nov 1998 09:44:06 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19318
for <current@freebsd.org>; Sat, 7 Nov 1998 09:44:05 -0800 (PST)
(envelope-from jdp@austin.polstra.com)
Received: from austin.polstra.com (jdp@localhost)
by austin.polstra.com (8.9.1/8.9.1) with ESMTP id JAA21951;
Sat, 7 Nov 1998 09:42:23 -0800 (PST)
(envelope-from jdp)
Message-Id: <199811071742.JAA21951@austin.polstra.com>
To: dwhite@resnet.uoregon.edu
Subject: Re: What is wrong?
In-Reply-To: <Pine.BSF.4.03.9811070021230.6949-100000@resnet.uoregon.edu>
References: <Pine.BSF.4.03.9811070021230.6949-100000@resnet.uoregon.edu>
Organization: Polstra & Co., Seattle, WA
Cc: "Alexander B. Povolotsky" <tarkhil@synchroline.ru>, current@FreeBSD.ORG
Date: Sat, 07 Nov 1998 09:42:23 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
In article <Pine.BSF.4.03.9811070021230.6949-100000@resnet.uoregon.edu>,
Doug White <dwhite@resnet.uoregon.edu> wrote:
> On Fri, 6 Nov 1998, Alexander B. Povolotsky wrote:
>
> > attempt to run cvsup (extracted from ports/net/cvsup-binary) leads to
> >
> > ELF interpreter /usr/libexec/ld-elf.so.1 not found
> >
> > What can be wrong?
>
> The cvsup binary you extracted is in ELF format and your systemhasn't been
> transitioned to ELF yet. Grab a new -CURRENT and run 'make aout-to-elf'
> to update yourself.
Hrm, Alexander, are you sure you grabbed the "cvsup-bin" port? (You
said "cvsup-binary, but there is no port with that name.) The
executable in the "cvsup-bin" port is statically linked, and it's also
a.out. I wouldn't expect the problems you reported, if you used that
port.
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 7 09:53:57 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id JAA20434
for freebsd-current-outgoing; Sat, 7 Nov 1998 09:53:57 -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 JAA20429
for <current@freebsd.org>; Sat, 7 Nov 1998 09:53: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 SAA13034;
Sat, 7 Nov 1998 18:58:24 +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 TAA09857;
Sat, 7 Nov 1998 19:18:08 +0100 (CET)
Received: (from uucp@localhost)
by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) with UUCP id SAA24836;
Sat, 7 Nov 1998 18:53:09 +0100 (CET)
Received: (from regnauld@localhost)
by stimpy.prosa.dk (8.9.1/8.9.1/stimpy-1.0) id SAA22018;
Sat, 7 Nov 1998 18:56:41 +0100 (CET)
(envelope-from regnauld)
Message-ID: <19981107185641.55737@stimpy.prosa.dk>
Date: Sat, 7 Nov 1998 18:56:41 +0100
From: Phil Regnauld <regnauld@EU.org>
To: Brian Feldman <green@unixhelp.org>
Cc: current@FreeBSD.ORG
Subject: Re: RFSIGSHARE ready?
References: <5455.910406495@time.cdrom.com> <Pine.BSF.4.05.9811062211030.13730-100000@janus.syracuse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.88e
In-Reply-To: <Pine.BSF.4.05.9811062211030.13730-100000@janus.syracuse.net>; from Brian Feldman on Fri, Nov 06, 1998 at 10:11:58PM -0500
X-Operating-System: FreeBSD 3.0-RELEASE 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
Brian Feldman writes:
> Okay, touche!
> Developers, I need %$#@^ developers! :)
> Someone who's familiar with LinuxThreads should try helping out ;)
Err... Ever thought of posting to -emulation ? :-)
You're more likely to get support for this work, and I'd be
ready to _test_ the stuff.
The StarOffice 5.0 .tar is sitting on my disk, waiting to be
opened :-P
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 11:23:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA00667
for freebsd-current-outgoing; Sat, 7 Nov 1998 11:23:10 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00661
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 11:23:05 -0800 (PST)
(envelope-from seggers@semyam.dinoco.de)
Received: (from uucp@localhost)
by tim.xenologics.com (8.8.5/8.8.8) with UUCP id UAA18983;
Sat, 7 Nov 1998 20:20:45 +0100 (MET)
Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1])
by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id TAA07868;
Sat, 7 Nov 1998 19:38:50 +0100 (CET)
(envelope-from seggers@semyam.dinoco.de)
Message-Id: <199811071838.TAA07868@semyam.dinoco.de>
To: Mikhail Teterin <mi@video-collage.com>
cc: current@FreeBSD.ORG, seggers@semyam.dinoco.de
Subject: Re: same swap twice (was Re: The infamous dying daemons bug)
In-reply-to: Your message of "Fri, 06 Nov 1998 21:04:48 EST."
<199811070204.VAA10749@xxx.video-collage.com>
Date: Sat, 07 Nov 1998 19:38:49 +0100
From: Stefan Eggers <seggers@semyam.dinoco.de>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> =It may be interesting to know that mounting the same swap paritition
> =twice causes the exact same symptoms.
>
> Some time back, I submitted a PR about ``swapon'' and/or underlying
> calls being not picky enough to prevent this sort of mistakes from
And how do you think shall it be prevented? Making swapon know about
partitions and compatibility slice would be insane.
Maybe one could add functionality to the device drivers to allow
checking for "being the same thing" which gets callend whenever the
major device numbers are the same. A driver not supporting this has
all the minors being "different things" by default.
The "thing" not necessarily being a partition of course as for example
the rewinding and non-rewinding minors of a tape device driver use the
same hardware and there this might get used for something, too.
> happening. One of the gods closed the PR promptly with "Don't do it
> then"...
Maybe you want to implement it the way suggested above and do the
testing? A reasonably simple solution probably has a chance of
getting added.
W/o code such a PR hardly has a chance. It's as if you complain about
config not preventing you from creating a non-compiling kernel config.
I once managed to do so by trying to exclude INET from a 2.2 kernel
which failed to compile and there are numerous other ways of doing
things wrong.
Or take another example. Put "reboot" into /boot/boot.config and it
will be fun to watch the boot loader starting again all the time.
Shall code be added to prevent that? Is it worth the investment of
time? Probably not unless someone already has working code to do it.
Stefan.
--
Stefan Eggers Lu4 yao2 zhi1 ma3 li4,
Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1.
51109 Koeln
Federal Republic of Germany
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 11:33:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id LAA01845
for freebsd-current-outgoing; Sat, 7 Nov 1998 11:33:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from dingo.cdrom.com (castles356.castles.com [208.214.167.56])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01840
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 11:33:09 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost [127.0.0.1])
by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA05660;
Sat, 7 Nov 1998 11:32:09 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811071932.LAA05660@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Phil Regnauld <regnauld@EU.org>
cc: Mikael Karpberg <karpen@ocean.campus.luth.se>, current@FreeBSD.ORG
Subject: Re: config option VESA
In-reply-to: Your message of "Sat, 07 Nov 1998 01:15:09 +0100."
<19981107011509.07130@stimpy.prosa.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 07 Nov 1998 11:32:08 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
These reports are worthless, and both of you ought to know better.
Now class, who can tell me how you report a problem like this?
> > Take a GENERIC config file, add ``option "VM86"'' and config, make, install.
> > Reboot. Works fine. Add ``option VESA'' too. Repeat. Boots and crashes what
> > looks like just before starting the rc scripts. "Page not present" panic.
>
> Same here.
>
> > It says in LINT to not use VESA with SMP. But I have a UP Pentium.
>
> Yup. I tried it on my Libretto 70 (which I'm quite sure is not
> multiprocessor :-)
>
> VM86 -> ok (I use it to run some dos based dictionary)
> VM86 + VESA -> boom.
>
> 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 Sat Nov 7 12:51:56 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA08943
for freebsd-current-outgoing; Sat, 7 Nov 1998 12:51:56 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.kersur.net (mail.kersur.net [199.79.199.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08927
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 12:51:49 -0800 (PST)
(envelope-from dswartz@druber.com)
Received: from manticore (manticore.druber.com [207.180.95.108])
by mail.kersur.net (8.9.1/8.9.1) with SMTP id PAA15309;
Sat, 7 Nov 1998 15:52:11 -0500 (EST)
Message-Id: <3.0.5.32.19981107155117.00979370@mail.kersur.net>
X-Sender: druber@mail.kersur.net
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Sat, 07 Nov 1998 15:51:17 -0500
To: Stefan Eggers <seggers@semyam.dinoco.de>
From: Dan Swartzendruber <dswartz@druber.com>
Subject: Re: same swap twice (was Re: The infamous dying daemons bug)
Cc: Mikhail Teterin <mi@video-collage.com>, current@FreeBSD.ORG,
seggers@semyam.dinoco.de
In-Reply-To: <199811071838.TAA07868@semyam.dinoco.de>
References: <Your message of "Fri, 06 Nov 1998 21:04:48 EST." <199811070204.VAA10749@xxx.video-collage.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
At 07:38 PM 11/7/98 +0100, Stefan Eggers wrote:
>> =It may be interesting to know that mounting the same swap paritition
>> =twice causes the exact same symptoms.
>>
>> Some time back, I submitted a PR about ``swapon'' and/or underlying
>> calls being not picky enough to prevent this sort of mistakes from
>
>And how do you think shall it be prevented? Making swapon know about
>partitions and compatibility slice would be insane.
Why?
>Maybe one could add functionality to the device drivers to allow
>checking for "being the same thing" which gets callend whenever the
>major device numbers are the same. A driver not supporting this has
>all the minors being "different things" by default.
>
>The "thing" not necessarily being a partition of course as for example
>the rewinding and non-rewinding minors of a tape device driver use the
>same hardware and there this might get used for something, too.
>
>> happening. One of the gods closed the PR promptly with "Don't do it
>> then"...
>
>Maybe you want to implement it the way suggested above and do the
>testing? A reasonably simple solution probably has a chance of
>getting added.
>
>W/o code such a PR hardly has a chance. It's as if you complain about
>config not preventing you from creating a non-compiling kernel config.
>I once managed to do so by trying to exclude INET from a 2.2 kernel
>which failed to compile and there are numerous other ways of doing
>things wrong.
>
>Or take another example. Put "reboot" into /boot/boot.config and it
>will be fun to watch the boot loader starting again all the time.
>Shall code be added to prevent that? Is it worth the investment of
>time? Probably not unless someone already has working code to do it.
I think these are in a different category from a sysadmin typing
the same name twice. Granted there are things (like newfs and such)
that you can't help but screw yourself. On the other hand, I find
it hard to believe that a simple check of "do I have block device
N/Y active as swap currently?" can possibly be that hard. And the
fact that whoever closed the PR did so without apparently thinking
for more than 10 seconds about this is not real encouraging.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 13:21:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA11317
for freebsd-current-outgoing; Sat, 7 Nov 1998 13:21:04 -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 NAA11303
for <current@freebsd.org>; Sat, 7 Nov 1998 13:21:02 -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 SMTP id NAA06466
for <current@freebsd.org>; Sat, 7 Nov 1998 13:20:50 -0800 (PST)
(envelope-from brian@CSUA.Berkeley.EDU)
Date: Sat, 7 Nov 1998 13:20:50 -0800 (PST)
From: "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>
X-Sender: brian@smarter.than.nu
To: current@FreeBSD.ORG
Subject: meaning of "file: table is full" kernel log messages?
Message-ID: <Pine.BSF.4.02A.9811071314400.1428-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
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>
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.
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?)
--
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 7 13:40:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA12726
for freebsd-current-outgoing; Sat, 7 Nov 1998 13:40:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12717
for <freebsd-current@FreeBSD.ORG>; Sat, 7 Nov 1998 13:40:17 -0800 (PST)
(envelope-from adrian@lorax.ubergeeks.com)
Received: from localhost (adrian@localhost)
by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id QAA06380;
Sat, 7 Nov 1998 16:40:03 -0500 (EST)
(envelope-from adrian@lorax.ubergeeks.com)
Date: Sat, 7 Nov 1998 16:40:03 -0500 (EST)
From: ADRIAN Filipi-Martin <adrian@ubergeeks.com>
Reply-To: Adrian Filipi-Martin <adrian@ubergeeks.com>
To: Robert Nordier <rnordier@nordier.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Boot Loader question
In-Reply-To: <199811070811.KAA07985@ceia.nordier.com>
Message-ID: <Pine.BSF.3.96.981107163312.6140H-100000@lorax.ubergeeks.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 Nordier wrote:
> I have substantially revised boot1 and should be committing this
> within the next day or two. Until now, we've been making use of
> a new set of BIOS extended disk services, but it has become painfully
> evident that a few BIOSes have problems with this approach, and they
> really weren't much of a win, anyway.
When do you expect to commit your changes. I bagan hacking on the
stage 1 boot block a few days ago to try and make it behave properly when
using a serial console.
The -current ones end up with garbage in the boot prompt after it
reads a boot.config with just a '-h' in it. After it switches to the
serial console, I have to backspace and type 'kernel', and it boots just
fine. If boot.config is empty, it boots fine but of course, I don't get a
chance to boot an alternate kernel since it doesn't switch to the serial
console until the kernel starts probing.
If you need a tester for the serial functionality, I'm willing. I
have 6 rackmounted machines with serial consoles and I will be fixing this
on my own if it isn't already fixed.
Also, are the boot blocks going to be built using elf or aout in
the long run? I'm just getting into -current and I figired out that I
need tom compile them as aout or they don't fit.
cheers,
Adrian
--
[ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 13:40:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA12735
for freebsd-current-outgoing; Sat, 7 Nov 1998 13:40:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from chiron.ringworld.com.au ([202.0.102.65])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12715
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 13:40:12 -0800 (PST)
(envelope-from lee@ringworld.com.au)
From: lee@ringworld.com.au
Received: by chiron.ringworld.com.au with Internet Mail Service (5.5.2232.9)
id <W3H8PPAD>; Sun, 8 Nov 1998 08:39:28 +1100
Message-ID: <37BC9CD65406D111AB5400E029071934030FF9@chiron.ringworld.com.au>
To: current@FreeBSD.ORG
Subject: RE: The infamous dying daemons bug
Date: Sun, 8 Nov 1998 08:39:20 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
charset="iso-8859-1"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
I look after 2 FreeBSD machines. The SCSI-based machine (vallona) gets the
"signal 11" error when the swap utilisation goes above 75%. The second
machine which has a single IDE disk never has the problem.
I have included the dmesg output for each and yes the problem has been going
on for many months.
Hope the additional info helps track it down.
Regards,
Lee
----
VALLONA dmesg output
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 #26: Fri Nov 6 20:53:12 EST 1998
root@vallona.csccs.com.au:/usr/src/sys/compile/VALLONA
<mailto:root@vallona.csccs.com.au:/usr/src/sys/compile/VALLONA>
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium/P54C (132.96-MHz 586-class CPU)
Origin = "GenuineIntel" Id = 0x52b Stepping=11
Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
real memory = 25165824 (24576K bytes)
config> quit
avail memory = 21684224 (21176K bytes)
Probing for devices on PCI bus 0:
chip0: <Intel 82437FX PCI cache memory controller> rev 0x02 on pci0.0.0
chip1: <Intel 82371FB PCI to ISA bridge> rev 0x02 on pci0.7.0
de0: <Digital 21040 Ethernet> rev 0x23 int a irq 10 on pci0.14.0
de0: DEC 21040 [10Mb/s] pass 2.3
de0: address 08:00:2b:e5:9d:f9
ahc0: <Adaptec 2940 SCSI adapter> rev 0x00 int a irq 11 on pci0.15.0
ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs
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
fe0 not found at 0x300
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
psm0 not found at 0x60
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
wdc0 not found at 0x1f0
wdc1 not found at 0x170
wt0 not found at 0x300
mcd0 not found at 0x300
matcdc0 not found at 0x230
scd0 not found at 0x230
ie0: unknown board_id: f000
ie0 not found at 0x300
ep0 not found at 0x300
ex0 not found
le0 not found at 0x300
lnc0 not found at 0x280
ze0 not found at 0x300
zp0 not found at 0x300
cs0 not found at 0x300
adv0 not found at 0x330
bt0 not found at 0x134
aha0 not found at 0x134
npx0 on motherboard
npx0: INT 16 interface
Intel Pentium F00F detected, installing workaround
Waiting 15 seconds for SCSI devices to settle
de0: enabling 10baseT port
sa0 at ahc0 bus 0 target 5 lun 0
sa0: <HP HP35480A T603> Removable Sequential Access SCSI2 device
sa0: 5.0MB/s transfers (5.0MHz, offset 8)
da2 at ahc0 bus 0 target 6 lun 0
da2: <QUANTUM FIREBALL1080S 1Q09> Fixed Direct Access SCSI2 device
da2: 10.0MB/s transfers (10.0MHz, offset 8)
da2: 1042MB (2134305 512 byte sectors: 64H 32S/T 1042C)
da0 at ahc0 bus 0 target 0 lun 0
da0: <SEAGATE ST31230N 0300> Fixed Direct Access SCSI2 device
da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
da0: 1010MB (2069860 512 byte sectors: 64H 32S/T 1010C)
changing root device to da0s1a
da1 at ahc0 bus 0 target 2 lun 0
da1: <IBM DORS-32160 S83B> Fixed Direct Access SCSI1 device
da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled
da1: 2015MB (4127761 512 byte sectors: 64H 32S/T 2015C)
de0: enabling 10baseT port
de0: enabling Full Duplex 10baseT port
/proxy: optimization changed from TIME to SPACE
(da1:ahc0:0:2:0): tagged openings now 32
(da0:ahc0:0:0:0): tagged openings now 64
(da0:ahc0:0:0:0): tagged openings now 63
-------
SNOOPY 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 #84: Thu Nov 5 18:58:30 EST 1998
root@snoopy.ringworld.com.au:/usr/src/sys/compile/SNOOPY
<mailto:root@snoopy.ringworld.com.au:/usr/src/sys/compile/SNOOPY>
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium/P54C (119.75-MHz 586-class CPU)
Origin = "GenuineIntel" Id = 0x526 Stepping=6
Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
real memory = 16777216 (16384K bytes)
config> quit
avail memory = 13406208 (13092K bytes)
Preloaded a.out kernel "kernel" at 0xf032f000.
Probing for devices on PCI bus 0:
chip0: <Intel 82437VX PCI cache memory controller> rev 0x01 on pci0.0.0
chip1: <Intel 82371SB PCI to ISA bridge> rev 0x00 on pci0.7.0
ide_pci0: <Intel PIIX3 Bus-master IDE controller> rev 0x00 on pci0.7.1
chip2: <Intel 82371SB USB host controller> rev 0x00 int d irq 11 on pci0.7.2
tx0: <SMC 83c170> rev 0x06 int a irq 9 on pci0.9.0
tx0: address 00:e0:29:07:19:34, type SMC9432TX, Auto-Neg 10Mbps
ahc0: <Adaptec 2940A Ultra SCSI adapter> rev 0x03 int a irq 5 on pci0.10.0
ahc0: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs
vga0: <S3 Trio graphics accelerator> rev 0x54 int a irq 11 on pci0.11.0
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
fe0 not found at 0x300
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
psm0 not found at 0x60
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <QUANTUM FIREBALL_TM2100A>
wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 not found at 0x170
wt0 not found at 0x300
mcd0 not found at 0x300
matcdc0 not found at 0x230
scd0 not found at 0x230
ie0: unknown board_id: f000
ie0 not found at 0x300
ep0 not found at 0x300
ex0 not found
le0 not found at 0x300
lnc0 not found at 0x280
ze0 not found at 0x300
zp0 not found at 0x300
cs0 not found at 0x300
adv0 not found at 0x330
bt0 not found at 0x134
aha0 not found at 0x134
npx0 on motherboard
npx0: INT 16 interface
Intel Pentium F00F detected, installing workaround
Waiting 15 seconds for SCSI devices to settle
sa0 at ahc0 bus 0 target 4 lun 0
sa0: <HP HP35480A T603> Removable Sequential Access SCSI2 device
sa0: 5.0MB/s transfers (5.0MHz, offset 8)
changing root device to wd0s1a
fd0: Seek to cyl 0, but not really there (ST3 = 28<drdy,two_side>)
fd0: Seek to cyl 0, but not really there (ST3 = 28<drdy,two_side>)
fd0: Seek to cyl 0, but not really there (ST3 = 28<drdy,two_side>)
fd0: Seek to cyl 0, but not really there (ST3 = 28<drdy,two_side>)
-----Original Message-----
From: owner-freebsd-current@FreeBSD.ORG
[mailto:owner-freebsd-current@FreeBSD.ORG] On Behalf Of Brian Feldman
Sent: Sunday, November 08, 1998 2:15 AM
To: Alexander Litvin
Cc: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
avail memory = 78680064 (76836K bytes)
Device 1K-blocks Used Avail Capacity Type
/dev/wd0s1b 102400 13940 88332 14%
Interleaved
/dev/wd1s1b 102400 13608 88664 13%
Interleaved
Total 204544 27548 176996 13%
swap_pager: suggest more swap space: 157 MB
swap_pager: out of swap space
pid 14846 (memory), uid 1000, was killed: out of swap space
pid 14846 (memory), uid 1000, was killed: out of swap space
No problems at all. Cron runs (at works), inetd works, exim
works...
Cheers,
Brian Feldman
On Sat, 7 Nov 1998, Alexander Litvin wrote:
> In article
<Pine.BSF.4.05.9811061814370.6415-100000@janus.syracuse.net> you wrote:
> BF> I haven't had this bug. And a 3.0 box at school
doesn't have it either...
> BF> it's not as common as you think.
>
> Have you beaten your systems to "swap_pager: out of swap
space"?
>
> My system may run for months without any problem. It's
home box
> -- 32M RAM + 128M swap, and it is enough for day-to-day
operation.
> But when I artificially overload it, it easily shows all
that
> sendmails exiting on signal 11, cron jobs not run, etc.
>
> BF> Brian Feldman
>
> ---
> Did you know ...
>
>
>
>
>
>
>
> That no-one ever reads these things?
>
> 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 Sat Nov 7 13:54:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id NAA14421
for freebsd-current-outgoing; Sat, 7 Nov 1998 13:54:59 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from phoenix.cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14416
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 13:54:58 -0800 (PST)
(envelope-from crossd@phoenix.cs.rpi.edu)
Received: (from crossd@localhost)
by phoenix.cs.rpi.edu (8.9.1/8.9.1) id QAA00324;
Sat, 7 Nov 1998 16:54:32 -0500 (EST)
(envelope-from crossd)
Date: Sat, 7 Nov 1998 16:54:32 -0500 (EST)
From: "David E. Cross" <crossd@phoenix.cs.rpi.edu>
Message-Id: <199811072154.QAA00324@phoenix.cs.rpi.edu>
To: bright@hotjobs.com, current@FreeBSD.ORG
Subject: Re: O_SYNC
In-Reply-To: <Pine.BSF.4.05.9811071213160.19817-100000@porkfriedrice.ny.genx.net>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
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 Sat Nov 7 14: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 OAA17513
for freebsd-current-outgoing; Sat, 7 Nov 1998 14:36: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 OAA17508
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 14:36:06 -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 RAA15894;
Sat, 7 Nov 1998 17:35:46 -0500 (EST)
Date: Sat, 7 Nov 1998 17:35:45 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: lee@ringworld.com.au
cc: current@FreeBSD.ORG
Subject: RE: The infamous dying daemons bug
In-Reply-To: <37BC9CD65406D111AB5400E029071934030FF9@chiron.ringworld.com.au>
Message-ID: <Pine.BSF.4.05.9811071730430.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 lee@ringworld.com.au wrote:
> I look after 2 FreeBSD machines. The SCSI-based machine (vallona) gets the
> "signal 11" error when the swap utilisation goes above 75%. The second
> machine which has a single IDE disk never has the problem.
Interesting, but I think that if it was something in the SCSI
code, something would have happened to the bug (for better or
worse) during switch to CAM. I jumped on the 3.0 bandwagon
post-CAM.
-john
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 14:39:59 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA17923
for freebsd-current-outgoing; Sat, 7 Nov 1998 14:39:59 -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 OAA17918
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 14:39:49 -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 RAA25280;
Sat, 7 Nov 1998 17:39:25 -0500 (EST)
Date: Sat, 7 Nov 1998 17:39:25 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Phil Regnauld <regnauld@EU.org>
cc: current@FreeBSD.ORG
Subject: Re: RFSIGSHARE ready?
In-Reply-To: <19981107185641.55737@stimpy.prosa.dk>
Message-ID: <Pine.BSF.4.05.9811071737440.25210-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
It requires more than a passing familiarity with FreeBSD, and needs real
dvelopers, so the preferred audience should be -current. It's not
"patches to test", it's a real-life problem that needs to be _worked_ on,
and I seem to have done most of the work already, so if anyone can help
figure out more with the LinuxThreads, we'd all be happy.
Cheers,
Brian Feldman
On Sat, 7 Nov 1998, Phil Regnauld wrote:
> Brian Feldman writes:
> > Okay, touche!
> > Developers, I need %$#@^ developers! :)
> > Someone who's familiar with LinuxThreads should try helping out ;)
>
> Err... Ever thought of posting to -emulation ? :-)
>
> You're more likely to get support for this work, and I'd be
> ready to _test_ the stuff.
>
> The StarOffice 5.0 .tar is sitting on my disk, waiting to be
> opened :-P
>
>
> 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 7 14:57:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id OAA19617
for freebsd-current-outgoing; Sat, 7 Nov 1998 14:57:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from badlans.lanminds.com (badlans.lanminds.com [208.25.91.253])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19612
for <freebsd-current@freebsd.org>; Sat, 7 Nov 1998 14:57:42 -0800 (PST)
(envelope-from rrs@badlans.lanminds.com)
Received: (from rrs@localhost)
by badlans.lanminds.com (8.8.6/8.8.6) id OAA22536
for freebsd-current@freebsd.org; Sat, 7 Nov 1998 14:58:54 -0800 (PST)
Date: Sat, 7 Nov 1998 14:58:54 -0800 (PST)
From: Robert Schulhof <rrs@LMI.Net>
Message-Id: <199811072258.OAA22536@badlans.lanminds.com>
To: freebsd-current@FreeBSD.ORG
Subject: libc_r link error
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
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'
Thanks!
Rob
Robert Schulhof
UNIX System Administrator
LanMinds Internet. (LMI Net)
rrs@lmi.net
http://www.lmi.net
(510) 843-6389 VOX
(510) 843-6390 FAX
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 15:03:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA19943
for freebsd-current-outgoing; Sat, 7 Nov 1998 15:03:18 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19938
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 15:03:16 -0800 (PST)
(envelope-from seggers@semyam.dinoco.de)
Received: (from uucp@localhost)
by tim.xenologics.com (8.8.5/8.8.8) with UUCP id AAA07898;
Sun, 8 Nov 1998 00:01:56 +0100 (MET)
Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1])
by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id AAA17493;
Sun, 8 Nov 1998 00:01:08 +0100 (CET)
(envelope-from seggers@semyam.dinoco.de)
Message-Id: <199811072301.AAA17493@semyam.dinoco.de>
To: Dan Swartzendruber <dswartz@druber.com>
cc: Mikhail Teterin <mi@video-collage.com>, current@FreeBSD.ORG,
seggers@semyam.dinoco.de
Subject: Re: same swap twice (was Re: The infamous dying daemons bug)
In-reply-to: Your message of "Sat, 07 Nov 1998 15:51:17 EST."
<3.0.5.32.19981107155117.00979370@mail.kersur.net>
Date: Sun, 08 Nov 1998 00:01:08 +0100
From: Stefan Eggers <seggers@semyam.dinoco.de>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> >And how do you think shall it be prevented? Making swapon know about
> >partitions and compatibility slice would be insane.
>
> Why?
Swapon operates on whatever block device you hand it. It doesn't know
what slices and partitions are. Especially teaching it about slices is
insane as this is a PC thing. Other machines might have the partitions
only for example. It would unnecessarily add complications and depen-
dencies to the VM code. The propper abstraction is a block device which
does everything the VM code needs for its operation.
> that you can't help but screw yourself. On the other hand, I find
> it hard to believe that a simple check of "do I have block device
> N/Y active as swap currently?" can possibly be that hard. And the
This simple check is in the code as far as I know and remember and
is in -stable, too. If not adding it were a matter of minutes.
The trouble maker was swapping to /dev/wd0b and /dev/wd0s1b at the
same time which is a different thing as comparing major and minor
device numbers is not enough in this case.
It's the old compatibility slice thing which makes this imperfect.
How should swapon know that your /dev/wd0b is on the same disk space
as /dev/wd0s1b? They have different minor numbers after all and
that's what we can check. Once we give the compatibility slice
eternal rest we don't have his problem anymore.
> fact that whoever closed the PR did so without apparently thinking
> for more than 10 seconds about this is not real encouraging.
The compatibility slice thing will go away as far as I know and the
first step was also done in -stable by deamding the full name for
these partitions in the fstab.
Is it worth to add support for catching a rather obscure mistake
which will soon not be possible anymore anyway? I can understand
that nobody wants to bother with *that* as it is pretty much a waste
of time and solves itself hopefully soon.
Stefan.
--
Stefan Eggers Lu4 yao2 zhi1 ma3 li4,
Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1.
51109 Koeln
Federal Republic of Germany
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 15:34:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA22613
for freebsd-current-outgoing; Sat, 7 Nov 1998 15:34:50 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from mail.kersur.net (mail.kersur.net [199.79.199.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22606
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 15:34:44 -0800 (PST)
(envelope-from dswartz@druber.com)
Received: from manticore (manticore.druber.com [207.180.95.108])
by mail.kersur.net (8.9.1/8.9.1) with SMTP id SAA19979;
Sat, 7 Nov 1998 18:35:17 -0500 (EST)
Message-Id: <3.0.5.32.19981107183422.009a3c40@mail.kersur.net>
X-Sender: druber@mail.kersur.net
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Sat, 07 Nov 1998 18:34:22 -0500
To: Stefan Eggers <seggers@semyam.dinoco.de>
From: Dan Swartzendruber <dswartz@druber.com>
Subject: Re: same swap twice (was Re: The infamous dying daemons bug)
Cc: Mikhail Teterin <mi@video-collage.com>, current@FreeBSD.ORG,
seggers@semyam.dinoco.de
In-Reply-To: <199811072301.AAA17493@semyam.dinoco.de>
References: <Your message of "Sat, 07 Nov 1998 15:51:17 EST." <3.0.5.32.19981107155117.00979370@mail.kersur.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
At 12:01 AM 11/8/98 +0100, Stefan Eggers wrote:
>
>> that you can't help but screw yourself. On the other hand, I find
>> it hard to believe that a simple check of "do I have block device
>> N/Y active as swap currently?" can possibly be that hard. And the
>
>This simple check is in the code as far as I know and remember and
>is in -stable, too. If not adding it were a matter of minutes.
>
>The trouble maker was swapping to /dev/wd0b and /dev/wd0s1b at the
>same time which is a different thing as comparing major and minor
>device numbers is not enough in this case.
Sigh. I wasn't aware of that. The problem that was complained about
(at least what I heard, which aren't always the same :]) was "I added
the same swap device twice and hosed my system").
>It's the old compatibility slice thing which makes this imperfect.
>How should swapon know that your /dev/wd0b is on the same disk space
>as /dev/wd0s1b? They have different minor numbers after all and
>that's what we can check. Once we give the compatibility slice
>eternal rest we don't have his problem anymore.
>
>> fact that whoever closed the PR did so without apparently thinking
>> for more than 10 seconds about this is not real encouraging.
>
>The compatibility slice thing will go away as far as I know and the
>first step was also done in -stable by deamding the full name for
>these partitions in the fstab.
>
>Is it worth to add support for catching a rather obscure mistake
>which will soon not be possible anymore anyway? I can understand
>that nobody wants to bother with *that* as it is pretty much a waste
>of time and solves itself hopefully soon.
Okay, I can dig that. It would be nice if someone had made this as
clear as you just did (unless they did, and the person who started
this thread wasn't clear about it).
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 15:43:00 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA23550
for freebsd-current-outgoing; Sat, 7 Nov 1998 15:43:00 -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 PAA23539
for <freebsd-current@freebsd.org>; Sat, 7 Nov 1998 15:42:55 -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.1a/8.9.1) with ESMTP id AAA08825
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 00:42:36 +0100 (CET)
(envelope-from root@swimsuit.internet.dk)
Date: Sun, 8 Nov 1998 00:42:36 +0100 (CET)
From: Leif Neland <root@swimsuit.internet.dk>
To: freebsd-current@FreeBSD.ORG
Subject: How to make /dev/da0
Message-ID: <Pine.BSF.4.05.9811080026310.8500-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
I try to mount a linux-scsi disk, but fails miserably.
FreeBSD 3.0-CURRENT #2: Sun Nov 8 00:00:38 CET 1998
root@gina.swimsuit.internet.dk:/usr/src/sys/compile/REAL
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
These seems to know something, but not enough.
-r-xr-xr-x 1 root wheel 30602 13 Okt 19:08 /usr/release/dev/MAKEDEV
-rwxr-xr-x 1 root wheel 30673 31 Okt 07:38 /usr/src/etc/etc.i386/MAKEDEV
gina//dev $ /usr/src/etc/etc.i386/MAKEDEV da0
da0s0h - no such device name
da0s1 - no such device name
da0s2 - no such device name
da0s3 - no such device name
da0s4 - no such device name
Fdisk can see /dev/sd0
Script started on Sun Nov 8 00:36:26 1998
gina//dev $ fdisk /dev/sd0
******* Working on device /dev/sd0 *******
parameters extracted from in-core disklabel are:
cylinders=1019 heads=134 sectors/track=62 (8308 blks/cyl)
parameters to be used for BIOS calculations are:
cylinders=1019 heads=134 sectors/track=62 (8308 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 131,(Linux filesystem)
start 62, size 3073898 (1500 Meg), flag 80 (active)
beg: cyl 0/ sector 1/ head 1;
end: cyl 369/ sector 62/ head 133
The data for partition 2 is:
sysid 130,(Linux swap or Solaris x86)
start 3073960, size 249240 (121 Meg), flag 0
beg: cyl 370/ sector 1/ head 0;
end: cyl 399/ sector 62/ head 133
The data for partition 3 is:
sysid 131,(Linux filesystem)
start 3323200, size 5142652 (2511 Meg), flag 0
beg: cyl 400/ sector 1/ head 0;
end: cyl 1018/ sector 62/ head 133
The data for partition 4 is:
<UNUSED>
Fdisk doesn't see a /dev/da0
gina//dev $ fdisk /dev/da0
fdisk: can't get file status of /dev/da0
fdisk: cannot open disk /dev/da0: No such file or directory
I cant mount /dev/sd0s1 or /dev/da0s1
gina//dev $ mount_ext2fs /dev/sd0s1 /sd1
mount_ext2fs: vfsload(ext2fs): No such file or directory
If I boot from a 2.2.7-RELEASE boot.flp, the disk gets recognized as
/dev/sd0s1
Must I create /dev/da0 etc myself, and if so, what major/minor number?
Leif
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 15:44:09 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id PAA23787
for freebsd-current-outgoing; Sat, 7 Nov 1998 15:44:09 -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 PAA23776
for <freebsd-current@freebsd.org>; Sat, 7 Nov 1998 15:44:06 -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.1a/8.9.1) with ESMTP id AAA08847
for <freebsd-current@freebsd.org>; Sun, 8 Nov 1998 00:43:52 +0100 (CET)
(envelope-from root@swimsuit.internet.dk)
Date: Sun, 8 Nov 1998 00:43:51 +0100 (CET)
From: Leif Neland <root@swimsuit.internet.dk>
To: freebsd-current@FreeBSD.ORG
Subject: 3.0, real audio server
Message-ID: <Pine.BSF.4.05.9811080042400.8500-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
Can 3.0, or perhaps 2.2.7 be a real audio SERVER?
Leif
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 16:04:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA26138
for freebsd-current-outgoing; Sat, 7 Nov 1998 16:04:18 -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 QAA26125
for <freebsd-current@FreeBSD.ORG>; Sat, 7 Nov 1998 16:04:16 -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 QAA13489;
Sat, 7 Nov 1998 16:03:24 -0800 (PST)
(envelope-from jkh@time.cdrom.com)
To: Leif Neland <root@swimsuit.internet.dk>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: 3.0, real audio server
In-reply-to: Your message of "Sun, 08 Nov 1998 00:43:51 +0100."
<Pine.BSF.4.05.9811080042400.8500-100000@gina.swimsuit.internet.dk>
Date: Sat, 07 Nov 1998 16:03:23 -0800
Message-ID: <13485.910483403@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Can 3.0, or perhaps 2.2.7 be a real audio SERVER?
1. Yes.
2. Please address questions of this nature to questions@freebsd.org; this
mailing list is just for discussing issues specific to -current.
Thanks.
- 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 7 16:17:42 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA28608
for freebsd-current-outgoing; Sat, 7 Nov 1998 16:17:42 -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 QAA28599
for <current@freebsd.org>; Sat, 7 Nov 1998 16:17:39 -0800 (PST)
(envelope-from mi@aldan.algebra.com)
Received: (from mi@localhost)
by aldan.algebra.com (8.8.8/8.8.7) id AAA17617
for current@freebsd.org; Sun, 8 Nov 1998 00:17:05 GMT
(envelope-from mi)
From: Mikhail Teterin <mi@aldan.algebra.com>
Message-Id: <199811080017.AAA17617@aldan.algebra.com>
Subject: Re: same swap twice (was Re: The infamous dying daemons bug)
In-Reply-To: <199811072301.AAA17493@semyam.dinoco.de> from Stefan Eggers at "Nov 8, 1998 00:01:08 am"
To: current@FreeBSD.ORG
Date: Sun, 8 Nov 1998 00:17:05 +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
Stefan Eggers once stated:
=This simple check is in the code as far as I know and remember and
=is in -stable, too. If not adding it were a matter of minutes.
Yes, it already prevents you from adding the exact same device.
=The trouble maker was swapping to /dev/wd0b and /dev/wd0s1b at the
=same time which is a different thing as comparing major and minor
=device numbers is not enough in this case.
I thought, the swapon, or, rather, whatever the kernel code it
triggers, can look at the new partition's content and check of it
is already being paged onto. Another possibly even more usefull
precautions would be to check if the partition is marked as swap
in the disklabel (if any), and, may be, does it look like a
filesystem.
-mi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 16:30:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA00569
for freebsd-current-outgoing; Sat, 7 Nov 1998 16:30:26 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ceia.nordier.com (m1-1-dbn.dial-up.net [196.34.155.1])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00550
for <freebsd-current@FreeBSD.ORG>; Sat, 7 Nov 1998 16:30:17 -0800 (PST)
(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id CAA00278; Sun, 8 Nov 1998 02:28:27 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199811080028.CAA00278@ceia.nordier.com>
Subject: Re: Boot Loader question
In-Reply-To: <Pine.BSF.3.96.981107163312.6140H-100000@lorax.ubergeeks.com> from ADRIAN Filipi-Martin at "Nov 7, 98 04:40:03 pm"
To: adrian@ubergeeks.com
Date: Sun, 8 Nov 1998 02:28:23 +0200 (SAT)
Cc: rnordier@nordier.com, 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
ADRIAN Filipi-Martin wrote:
> On Sat, 7 Nov 1998, Robert Nordier wrote:
>
> > I have substantially revised boot1 and should be committing this
> > within the next day or two. Until now, we've been making use of
> > a new set of BIOS extended disk services, but it has become painfully
> > evident that a few BIOSes have problems with this approach, and they
> > really weren't much of a win, anyway.
>
> When do you expect to commit your changes. I bagan hacking on the
> stage 1 boot block a few days ago to try and make it behave properly when
> using a serial console.
Around late Sunday, most likely; I'm still testing here at the moment.
> The -current ones end up with garbage in the boot prompt after it
> reads a boot.config with just a '-h' in it. After it switches to the
> serial console, I have to backspace and type 'kernel', and it boots just
> fine. If boot.config is empty, it boots fine but of course, I don't get a
> chance to boot an alternate kernel since it doesn't switch to the serial
> console until the kernel starts probing.
The boot.config is currently being parsed twice if it boots with no
intervention. This became a problem when the option behavior changed
from `or' to `xor'. The patch below gives a temporary fix (the printf
statement is changed just to make space).
I'm not sure about the garbage, though, I'm not seeing it here. What
kind of garbage (like random line noise or more like a garbled prompt)?
Index: boot2.c
===================================================================
RCS file: /home/ncvs/src/sys/boot/i386/boot2/boot2.c,v
retrieving revision 1.13
diff -u -r1.13 boot2.c
--- boot2.c 1998/10/27 20:16:36 1.13
+++ boot2.c 1998/11/07 23:45:08
@@ -157,9 +157,10 @@
readfile(PATH_HELP, help, sizeof(help));
readfile(PATH_CONFIG, cmd, sizeof(cmd));
if (*cmd) {
- printf("%s: %s", PATH_CONFIG, cmd);
+ printf("%s", cmd);
if (parse(cmd))
autoboot = 0;
+ *cmd = 0;
}
if (autoboot && !*kname) {
if (autoboot == 2) {
> If you need a tester for the serial functionality, I'm willing. I
> have 6 rackmounted machines with serial consoles and I will be fixing this
> on my own if it isn't already fixed.
Thanks, testing is always very welcome; and any fixes that work for
you would be handy too, particularly if it is something that can't be
reproduced here.
> Also, are the boot blocks going to be built using elf or aout in
> the long run? I'm just getting into -current and I figired out that I
> need tom compile them as aout or they don't fit.
Definitely as ELF: aout has never been an option (IIRC, sio.s shouldn't
even assemble with the aout version of gas). They should fit, though;
they fit here, and would breaking "make world" for a lot of folks
otherwise.
--
Robert Nordier
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 16:35:17 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id QAA01482
for freebsd-current-outgoing; Sat, 7 Nov 1998 16:35:17 -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 QAA01477
for <current@freebsd.org>; Sat, 7 Nov 1998 16:35:15 -0800 (PST)
(envelope-from mi@aldan.algebra.com)
Received: (from mi@localhost)
by aldan.algebra.com (8.8.8/8.8.7) id AAA17877
for current@freebsd.org; Sun, 8 Nov 1998 00:34:45 GMT
(envelope-from mi)
From: Mikhail Teterin <mi@aldan.algebra.com>
Message-Id: <199811080034.AAA17877@aldan.algebra.com>
Subject: LD_LIBRARYELF_PATH
To: current@FreeBSD.ORG
Date: Sun, 8 Nov 1998 00:34:44 +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
What about the subject? Can the LD_LIBRARY${TYPE}_PATH variables
be checked for the executables of the appropriate type before
checking the LD_LIBRARY_PATH itself? The idea comes from Irix,
which has LD_LIBRARY32_PATH and LD_LIBRARY64_PATH in addition to
LD_LIBRARY_PATH.
Than, of course, LD_PRELOADELF and LD_PRELOADAOUT...
It would appear, that this only requires modifying libexec/rtld-*/rtld.c
and the man-pages...
The immediate benefits would be in things like runsocks, but not only...
-mi
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 17:14:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA05278
for freebsd-current-outgoing; Sat, 7 Nov 1998 17:14:43 -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 RAA05273
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 17:14:37 -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 CAA27718;
Sun, 8 Nov 1998 02:14:15 +0100 (CET)
Received: (from eivind@localhost)
by bitbox.follo.net (8.8.8/8.8.6) id CAA15217;
Sun, 8 Nov 1998 02:14:14 +0100 (MET)
Message-ID: <19981108021413.48676@follo.net>
Date: Sun, 8 Nov 1998 02:14:13 +0100
From: Eivind Eklund <eivind@yes.no>
To: John Fieber <jfieber@indiana.edu>, Alexander Litvin <archer@lucky.net>
Cc: Brian Feldman <green@unixhelp.org>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <199811071314.PAA23544@grape.carrier.kiev.ua> <Pine.BSF.4.05.9811070904250.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.9811070904250.482-100000@fallout.campusview.indiana.edu>; from John Fieber on Sat, Nov 07, 1998 at 09:16:27AM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, Nov 07, 1998 at 09:16:27AM -0500, John Fieber wrote:
> On Sat, 7 Nov 1998, Alexander Litvin wrote:
>
> > In article <Pine.BSF.4.05.9811061814370.6415-100000@janus.syracuse.net> you wrote:
> > BF> I haven't had this bug. And a 3.0 box at school doesn't have it either...
> > BF> it's not as common as you think.
> >
> > Have you beaten your systems to "swap_pager: out of swap space"?
>
> The meaning of this messages is reasonably clean and I have seen
> it before (although not since upgrading to 3.0 and meeting the
> dying daemons bug), but I have on occasion seen:
>
> smap_pager: suggest more swap space: 125 MB
>
> I assume it is a warning that I'm about to run out, but what does
> the 125MB mean?
I believe (and this is not confirmed) that this mean that you are
overcommitting 125MB of memory - that is, there are 125MB of allocated
pages that don't have backing swap space if you dirty them.
Looking at sys/vm/swap_pager.c, it looks like this guess is correct -
but there is a 2x multiplier in there that seems to mean it is
suggesting 2x the amount of overcommit. This is the relevant
code-fragment:
if (!suggest_more_swap && (vm_swap_size < btodb(cnt.v_page_count * PAGE_
SIZE))) {
printf("swap_pager: suggest more swap space: %d MB\n",
(2 * cnt.v_page_count * (PAGE_SIZE / 1024)) / 1000);
suggest_more_swap = 1;
}
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 17:21:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id RAA05820
for freebsd-current-outgoing; Sat, 7 Nov 1998 17:21:51 -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 RAA05811
for <current@freebsd.org>; Sat, 7 Nov 1998 17:21:44 -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 DAA20091
for <current@freebsd.org>; Sun, 8 Nov 1998 03:21:25 +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 DAA15186
for current@freebsd.org; Sun, 8 Nov 1998 03:20:40 +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 DAA11053;
Sun, 8 Nov 1998 03:13:45 +0200 (EET)
(envelope-from archer)
Date: Sun, 8 Nov 1998 03:13:45 +0200 (EET)
From: Alexander Litvin <archer@lucky.net>
Message-Id: <199811080113.DAA11053@grape.carrier.kiev.ua>
To: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
X-Newsgroups: grape.freebsd.current
In-Reply-To: <Pine.BSF.4.05.9811071730430.482-100000@fallout.campusview.indiana.edu>
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 <Pine.BSF.4.05.9811071730430.482-100000@fallout.campusview.indiana.edu> you wrote:
JF> On Sun, 8 Nov 1998 lee@ringworld.com.au wrote:
>> I look after 2 FreeBSD machines. The SCSI-based machine (vallona) gets the
>> "signal 11" error when the swap utilisation goes above 75%. The second
>> machine which has a single IDE disk never has the problem.
JF> Interesting, but I think that if it was something in the SCSI
JF> code, something would have happened to the bug (for better or
JF> worse) during switch to CAM. I jumped on the 3.0 bandwagon
JF> post-CAM.
True. My box, which can easily show 'daemons dying', has only
IDE disks (two, former -- one).
JF> -john
---
According to Kentucky state law, every person must take a bath at least
once a year.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 18:28:20 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA13673
for freebsd-current-outgoing; Sat, 7 Nov 1998 18:28: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 SAA13666;
Sat, 7 Nov 1998 18:28:18 -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 SAA01132;
Sat, 7 Nov 1998 18:27:00 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811080227.SAA01132@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: John Capo <jc@irbs.com>
cc: smp@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: Dog Sloooow SMP
In-reply-to: Your message of "Thu, 05 Nov 1998 15:36:07 EST."
<19981105153607.32581@irbs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 07 Nov 1998 18:27:00 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Quoting Mike Smith (mike@smith.net.au):
> > > Turns out that SMP broke for me on 5/21/98 in identcpu.c version
> > > 1.47 when code was added to identify PIIs. Not setting cpu = CPU_II
> > > fixes the problem.
> > >
> > > I suspect the real breakage is in pmap.c where cpu is used.
> >
> > If you change all of the 'cpu == CPU_686' tests to include CPU_PII, do
> > you get your performance back? It looks like at the very least it will
> > be costing you some performance optimisations.
> >
>
> Restoring cpu = CPU_PII in indentcpu.c and testing for CPU_686 and
> CPU_PII in pmap.c does fix the problem.
>
> I have an LX chipset and 233 Mhz PIIs bought around April of this
> year. I wonder why noone else has seen this problem.
No idea. I've received verification that fixing this for all 686-class
CPUs seems to work (ie. it's OK on the Cyrix MII and doesn't appear to
impact performance there), so the tests are now generalised for the
entire 686-class.
I hope this resolves your problems.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 18:44:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id SAA15389
for freebsd-current-outgoing; Sat, 7 Nov 1998 18:44:19 -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 SAA15371;
Sat, 7 Nov 1998 18:44:15 -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 NAA32642;
Sun, 8 Nov 1998 13:43:52 +1100
Date: Sun, 8 Nov 1998 13:43:52 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811080243.NAA32642@godzilla.zeta.org.au>
To: jc@irbs.com, mike@smith.net.au
Subject: Re: Dog Sloooow SMP
Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>No idea. I've received verification that fixing this for all 686-class
>CPUs seems to work (ie. it's OK on the Cyrix MII and doesn't appear to
>impact performance there), so the tests are now generalised for the
>entire 686-class.
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.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 19:15:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA19096
for freebsd-current-outgoing; Sat, 7 Nov 1998 19:15:15 -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 TAA19089
for <freebsd-current@FreeBSD.ORG>; Sat, 7 Nov 1998 19:15:14 -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 UAA27618;
Sat, 7 Nov 1998 20:15:00 -0700 (MST)
Received: from wdl1.wdl.lmco.com ([137.249.32.1]) by lmco.com (PMDF V5.1-10 #20543)
with SMTP id <0F23003NE2D0VE@lmco.com>; Sat, 7 Nov 1998 20:15:00 -0700 (MST)
Received: from lmco.com by wdl1.wdl.lmco.com (SMI-8.6/WDL-5.0) id TAA04678; Sat, 07 Nov 1998 19:14:57 -0800
Date: Sat, 07 Nov 1998 19:15:12 -0800
From: "George W. Dinolt" <george.w.dinolt@lmco.com>
Subject: Re: libc_r link error
To: Robert Schulhof <rrs@LMI.Net>
Cc: freebsd-current@FreeBSD.ORG
Message-id: <36450CC0.7F05F71A@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: <199811072258.OAA22536@badlans.lanminds.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
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'
>
> Thanks!
>
> Rob
>
>
> Robert Schulhof
> UNIX System Administrator
> LanMinds Internet. (LMI Net)
> rrs@lmi.net
> http://www.lmi.net
> (510) 843-6389 VOX
> (510) 843-6390 FAX
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
I can confirm that the problem is there. It happend for me when I tried
to execute python, which is linked with libc_r. It arose for me
yesterday when I recompiled libc_r using several ctm updates
(src-cur.360[0-9].gz). A little investigation showed that sendfile.S is
a generated file, that is it "defines" (I am not sure what the correct
word is) a system call. More investigation showed that SYS_sendfile is
defined in /usr/src/sys/sys/syscall.h
as
#define SYS_sendfile 336
so, in theory, it should not appear as an undefined symbol.
The following happened to me which may explain the problem. I recompiled
libc_r by just cd'ing to the libc_r directory and typing make. (Probably
not a good thing to do.) cc referenced the version of syscall.h in
/usr/include/sys rather than the one in /usr/src/sys/sys. The version in
/usr/include/sys had not been updated with the new define. (In fact, the
update was to syscalls.master in /usr/src/sys/kern. syscalls.h should be
generated from that master file. In my case, though, it was updated
through a ctm-file).
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.
This does bring up some interesting make dependencies problems, but I am
not expert enough to even consider what should be done here. (Should the
makefiles be set up to reference /usr/src/sys/sys/syscall.h rather than
the one in /usr/include/sys?)
Hope this helps.
George Dinolt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 19:28:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA20533
for freebsd-current-outgoing; Sat, 7 Nov 1998 19:28:38 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20511;
Sat, 7 Nov 1998 19:28: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 LAA22362;
Sun, 8 Nov 1998 11:25:49 +0800 (WST)
(envelope-from peter@spinner.netplex.com.au)
Message-Id: <199811080325.LAA22362@spinner.netplex.com.au>
X-Mailer: exmh version 2.0.2 2/24/98
To: Bruce Evans <bde@zeta.org.au>
cc: jc@irbs.com, mike@smith.net.au, current@FreeBSD.ORG, smp@FreeBSD.ORG
Subject: Re: Dog Sloooow SMP
In-reply-to: Your message of "Sun, 08 Nov 1998 13:43:52 +1100."
<199811080243.NAA32642@godzilla.zeta.org.au>
Date: Sun, 08 Nov 1998 11:25:48 +0800
From: Peter Wemm <peter@netplex.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Bruce Evans wrote:
> >No idea. I've received verification that fixing this for all 686-class
> >CPUs seems to work (ie. it's OK on the Cyrix MII and doesn't appear to
> >impact performance there), so the tests are now generalised for the
> >entire 686-class.
>
> 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.
> 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 Sat Nov 7 19:33:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA21466
for freebsd-current-outgoing; Sat, 7 Nov 1998 19:33:30 -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 TAA21447;
Sat, 7 Nov 1998 19:33:28 -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 TAA01507;
Sat, 7 Nov 1998 19:30:47 -0800 (PST)
(envelope-from mike@dingo.cdrom.com)
Message-Id: <199811080330.TAA01507@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Peter Wemm <peter@netplex.com.au>
cc: Bruce Evans <bde@zeta.org.au>, jc@irbs.com, mike@smith.net.au,
current@FreeBSD.ORG, smp@FreeBSD.ORG
Subject: Re: Dog Sloooow SMP
In-reply-to: Your message of "Sun, 08 Nov 1998 11:25:48 +0800."
<199811080325.LAA22362@spinner.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 07 Nov 1998 19:30:47 -0800
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> Bruce Evans wrote:
> > >No idea. I've received verification that fixing this for all 686-class
> > >CPUs seems to work (ie. it's OK on the Cyrix MII and doesn't appear to
> > >impact performance there), so the tests are now generalised for the
> > >entire 686-class.
> >
> > 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.
*shrug*
If you have better documentation for what should and shouldn't be based
on the CPU class vs. CPU functionality, please illuminate us poor
mortals. Meanwhile I'm simply trying to get back some of the
performance that seems to have been lost; I'll pull it back to two
comparisons against the P6 and PII if that's considered safer.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 19:55:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA23199
for freebsd-current-outgoing; Sat, 7 Nov 1998 19:55:04 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: (from jmb@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id TAA23192
for current; Sat, 7 Nov 1998 19:55:02 -0800 (PST)
(envelope-from jmb)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199811080355.TAA23192@hub.freebsd.org>
Subject: duplicate messages
To: current
Date: Sat, 7 Nov 1998 19:55:02 -0800 (PST)
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
in upgrading the mail system tonight, i created a situation
that resulted in people subscribed to current receiving
multiple copies of one or more email messages.
i have backed out the changes that i made.
please forgive the unintentional duplicate messages.
jmb
--
Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG
FreeBSD--The Power to Serve http://www.freebsd.org/
PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 20: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 UAA25985
for freebsd-current-outgoing; Sat, 7 Nov 1998 20:35:19 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: (from root@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA25981
for current; Sat, 7 Nov 1998 20:35:18 -0800 (PST)
(envelope-from jmb)
Date: Sat, 7 Nov 1998 20:35:18 -0800 (PST)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199811080435.UAA25981@hub.freebsd.org>
To: current
Subject: test messages
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
well hopefully the deluge is over
time to test the waters
sent forth the raven
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 20:48:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA27063
for freebsd-current-outgoing; Sat, 7 Nov 1998 20:48:38 -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 UAA27054;
Sat, 7 Nov 1998 20:48:35 -0800 (PST)
(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA06981;
Sun, 8 Nov 1998 15:48:20 +1100
Date: Sun, 8 Nov 1998 15:48:20 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811080448.PAA06981@godzilla.zeta.org.au>
To: current@FreeBSD.ORG, jmb@FreeBSD.ORG
Subject: Re: duplicate messages
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> please forgive the unintentional duplicate messages.
Please ignore my previous mail.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 20:56:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA27838
for freebsd-current-outgoing; Sat, 7 Nov 1998 20:56:13 -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 UAA27833
for <current@FreeBSD.ORG>; Sat, 7 Nov 1998 20:56:09 -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 PAA07388;
Sun, 8 Nov 1998 15:55:48 +1100
Date: Sun, 8 Nov 1998 15:55:48 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811080455.PAA07388@godzilla.zeta.org.au>
To: chris@netmonger.net, current@FreeBSD.ORG
Subject: Re: Lock up on accessing sio?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
>As another data point, we had previously tried putting 2.2.7-STABLE on
>it, and it was locking up right after booting.. it's possible that the
2.2.7 probably suffers from the same change as 3.0.
>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.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 21:02:25 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA28905
for freebsd-current-outgoing; Sat, 7 Nov 1998 21:02:25 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: (from jmb@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA28897
for current; Sat, 7 Nov 1998 21:02:23 -0800 (PST)
(envelope-from jmb)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199811080502.VAA28897@hub.freebsd.org>
Subject: problem fixed--test
To: current
Date: Sat, 7 Nov 1998 21:02:23 -0800 (PST)
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
having found a problem, its time to return current
to vmailer. i had switched it to bulk_mailer for
the interim
jmb
--
Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG
FreeBSD--The Power to Serve http://www.freebsd.org/
PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 21:38:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA01094
for freebsd-current-outgoing; Sat, 7 Nov 1998 21:38:11 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from detlev.UUCP (tex-48.camalott.com [208.229.74.48])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01070
for <freebsd-current@FreeBSD.ORG>; Sat, 7 Nov 1998 21:38:06 -0800 (PST)
(envelope-from joelh@gnu.org)
Received: (from joelh@localhost)
by detlev.UUCP (8.9.1/8.9.1) id XAA08172;
Sat, 7 Nov 1998 23:36:17 -0600 (CST)
(envelope-from joelh)
To: Leif Neland <root@swimsuit.internet.dk>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: How to make /dev/da0
References: <Pine.BSF.4.05.9811080026310.8500-100000@gina.swimsuit.internet.dk>
From: Joel Ray Holveck <joelh@gnu.org>
Date: 07 Nov 1998 22:42:25 -0600
In-Reply-To: Leif Neland's message of "Sun, 8 Nov 1998 00:42:36 +0100 (CET)"
Message-ID: <86n262rbjn.fsf@detlev.UUCP>
Lines: 95
X-Mailer: Gnus v5.5/Emacs 20.3
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> I try to mount a linux-scsi disk, but fails miserably.
> No MAKEDEV will make a dev0
\-- I'll assume you meant 'da0'.
You don't need a da0 yet, although it is the preferred way to specify
that disk. (Please, no holy wars on this issue.) You may use sd0s1
for a device name. (See below for why this failed.)
> 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
You must update your MAKEDEV when you install a new kernel.
> These seems to know something, but not enough.
> -r-xr-xr-x 1 root wheel 30602 13 Okt 19:08 /usr/release/dev/MAKEDEV
> -rwxr-xr-x 1 root wheel 30673 31 Okt 07:38 /usr/src/etc/etc.i386/MAKEDEV
> gina//dev $ /usr/src/etc/etc.i386/MAKEDEV da0
> da0s0h - no such device name
> da0s1 - no such device name
> da0s2 - no such device name
> da0s3 - no such device name
> da0s4 - no such device name
MAKEDEV was designed to be run from /dev. In many cases, including
da0, it will call itself recursively out of the current path. In your
case, the MAKEDEV you specified ran the MAKEDEV in the current
directory.
Anybody know why we shouldn't s/sh MAKEDEV/$0/ throughout MAKEDEV?
> Fdisk can see /dev/sd0
> Script started on Sun Nov 8 00:36:26 1998
> gina//dev $ fdisk /dev/sd0
> ******* Working on device /dev/sd0 *******
fdisk uses what you specify. (By default, it tries wd0, then sd0,
then od0. We need to s/sd0/da0/ in there.)
> Fdisk doesn't see a /dev/da0
> gina//dev $ fdisk /dev/da0
> fdisk: can't get file status of /dev/da0
> fdisk: cannot open disk /dev/da0: No such file or directory
That's because the MAKEDEV failed. fdisk uses devices same as
everything else.
> 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?
> If I boot from a 2.2.7-RELEASE boot.flp, the disk gets recognized as
> /dev/sd0s1
2.2.7 uses the sd0 names instead of the da0 names.
> Must I create /dev/da0 etc myself, and if so, what major/minor number?
No, it is not necessary. Find out why ext2fs isn't being loaded.
The preferred method of creating devices is *always* with MAKEDEV
(unless it's not, but you'll know when that is). Update your MAKEDEV
to make the da0 devices. However, for the sake of completeness:
brw-r----- 1 root operator 4, 0x00010002 Oct 4 12:57 /dev/da0
brw-r----- 1 root operator 4, 0 Oct 4 12:57 /dev/da0a
brw-r----- 1 root operator 4, 1 Oct 4 12:57 /dev/da0b
brw-r----- 1 root operator 4, 2 Oct 4 12:57 /dev/da0c
brw-r----- 1 root operator 4, 3 Oct 4 12:57 /dev/da0d
brw-r----- 1 root operator 4, 4 Oct 4 12:57 /dev/da0e
brw-r----- 1 root operator 4, 5 Oct 4 12:57 /dev/da0f
brw-r----- 1 root operator 4, 6 Oct 4 12:57 /dev/da0g
brw-r----- 1 root operator 4, 7 Oct 4 12:57 /dev/da0h
brw-r----- 1 root operator 4, 0x00020002 Oct 4 12:57 /dev/da0s1
brw-r----- 1 root operator 4, 0x00030002 Oct 4 12:57 /dev/da0s2
brw-r----- 1 root operator 4, 0x00040002 Oct 4 12:57 /dev/da0s3
brw-r----- 1 root operator 4, 0x00050002 Oct 4 12:57 /dev/da0s4
Note that these are identical to sd0's values; you can (for the
moment) continue to use sd0.
Cheers,
joelh
--
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 Sat Nov 7 21: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 VAA01672
for freebsd-current-outgoing; Sat, 7 Nov 1998 21:44:27 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: (from jmb@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id VAA01666
for current; Sat, 7 Nov 1998 21:44:23 -0800 (PST)
(envelope-from jmb)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199811080544.VAA01666@hub.freebsd.org>
Subject: release the mail
To: current
Date: Sat, 7 Nov 1998 21:44:23 -0800 (PST)
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
during this episode, i moved the mail queue aside.
i have just restored the mail queue to its place.
some duplicates will surely be sent out.
please ignore them.
jmb
--
Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG
FreeBSD--The Power to Serve http://www.freebsd.org/
PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 22:03:43 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA05046
for freebsd-current-outgoing; Sat, 7 Nov 1998 22:03:43 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from hotmail.com (f239.hotmail.com [207.82.251.130])
by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA05004
for <current@FreeBSD.org>; Sat, 7 Nov 1998 22:03:38 -0800 (PST)
(envelope-from beavix@hotmail.com)
Received: (qmail 1628 invoked by uid 0); 8 Nov 1998 06:03:18 -0000
Message-ID: <19981108060318.1627.qmail@hotmail.com>
Received: from 203.33.252.180 by www.hotmail.com with HTTP;
Sat, 07 Nov 1998 22:03:18 PST
X-Originating-IP: [203.33.252.180]
From: "the beavix" <beavix@hotmail.com>
To: current@FreeBSD.ORG
Cc: hackers@FreeBSD.ORG
Subject: Serial port oddnesses in -CURRENT
MIME-Version: 1.0
Content-Type: text/plain
Date: Sat, 07 Nov 1998 22:03:18 PST
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
Hi guys,
I've got an Intel PR440FX dual-PPro motherboard, and am having some
problems regarding serial ports in -CURRENT (which I built 3 days ago).
Nov 8 13:53:34 ether /kernel: sio1: 1 more silo overflow (total 121)
That's the 121st message I've got so far, and pppd has only been running
for <10 minutes. I think I might have traced the problem, here's a quick
snippet from dmesg:
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 8250
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
Now what puzzles me if that any serial port should complain, it should
be sio0, not sio1. What is similarly strange is that sio1 is not being
used, it's been disabled in the BIOS.
All I am running is an external Banksia 56k modem (connecting at 33k6),
which hangs off of sio0 on the board. For one reason or another, BIOS
won't let me set sio0 to use COM1 (even though I have a PS/2 mouse), so
I'm stuck with COM2 for sio0. sio1 has been set to disabled in the BIOS,
and there's nothing hanging off of the connector.
Here I am puzzled. You can't use an external modem on a serial port if
it's disabled, so why am I getting sio1 errors when the modem is using
sio0?
I've tried disabling sio0 and using sio1 from the BIOS, but this hasn't
worked either. sio1 can take COM2 if sio0 is disabled; and when I try
this, cu just sits there with "Connected" but doesn't take input. The
modem doesn't seem to respond.
Any ideas? Info would be greatly appreciated!
--
beav.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
From owner-freebsd-current Sat Nov 7 22:27:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id WAA07645
for freebsd-current-outgoing; Sat, 7 Nov 1998 22:27:11 -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 WAA07626;
Sat, 7 Nov 1998 22:27:08 -0800 (PST)
(envelope-from ulf@Gatekeeper.Alameda.net)
Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id WAA09353;
Sat, 7 Nov 1998 22:26:59 -0800 (PST)
Message-ID: <19981107222659.L25743@Alameda.net>
Date: Sat, 7 Nov 1998 22:26:59 -0800
From: Ulf Zimmermann <ulf@Alameda.net>
To: the beavix <beavix@hotmail.com>, current@FreeBSD.ORG
Cc: hackers@FreeBSD.ORG
Subject: Re: Serial port oddnesses in -CURRENT
Reply-To: ulf@Alameda.net
References: <19981108060318.1627.qmail@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <19981108060318.1627.qmail@hotmail.com>; from the beavix on Sat, Nov 07, 1998 at 10:03:18PM -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
I have an Intel DK440LX motherboard, there if I disable the serial
ports, they get seen, but don't work when I try to use them.
On Sat, Nov 07, 1998 at 10:03:18PM -0800, the beavix wrote:
> Hi guys,
>
> I've got an Intel PR440FX dual-PPro motherboard, and am having some
> problems regarding serial ports in -CURRENT (which I built 3 days ago).
>
> Nov 8 13:53:34 ether /kernel: sio1: 1 more silo overflow (total 121)
>
> That's the 121st message I've got so far, and pppd has only been running
> for <10 minutes. I think I might have traced the problem, here's a quick
> snippet from dmesg:
>
> sio0: configured irq 4 not in bitmap of probed irqs 0
> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
> sio0: type 8250
> sio1 at 0x2f8-0x2ff irq 3 on isa
> sio1: type 16550A
>
> Now what puzzles me if that any serial port should complain, it should
> be sio0, not sio1. What is similarly strange is that sio1 is not being
> used, it's been disabled in the BIOS.
>
> All I am running is an external Banksia 56k modem (connecting at 33k6),
> which hangs off of sio0 on the board. For one reason or another, BIOS
> won't let me set sio0 to use COM1 (even though I have a PS/2 mouse), so
> I'm stuck with COM2 for sio0. sio1 has been set to disabled in the BIOS,
> and there's nothing hanging off of the connector.
>
> Here I am puzzled. You can't use an external modem on a serial port if
> it's disabled, so why am I getting sio1 errors when the modem is using
> sio0?
>
> I've tried disabling sio0 and using sio1 from the BIOS, but this hasn't
> worked either. sio1 can take COM2 if sio0 is disabled; and when I try
> this, cu just sits there with "Connected" but doesn't take input. The
> modem doesn't seem to respond.
>
> Any ideas? Info would be greatly appreciated!
>
> --
>
> beav.
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.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