From owner-freebsd-hackers  Sun Sep 12  0:16: 4 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from jason.argos.org (a1-3a123.neo.rr.com [24.93.180.123])
	by hub.freebsd.org (Postfix) with ESMTP id 4C0131525C
	for <hackers@FreeBSD.ORG>; Sun, 12 Sep 1999 00:15:57 -0700 (PDT)
	(envelope-from mike@argos.org)
Received: from localhost (mike@localhost)
	by jason.argos.org (8.9.1/8.9.1) with ESMTP id DAA23162;
	Sun, 12 Sep 1999 03:15:42 -0400
Date: Sun, 12 Sep 1999 03:15:42 -0400 (EDT)
From: Mike Nowlin <mike@argos.org>
To: Kevin Day <toasty@dragondata.com>
Cc: hackers@FreeBSD.ORG
Subject: Re: damn ATX power supplies...
In-Reply-To: <199909120658.BAA43940@celery.dragondata.com>
Message-ID: <Pine.LNX.4.05.9909120310450.23083-100000@jason.argos.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> Yeah, you're supposed to tie PE low when you want power... However, in a
> system I'm working with now, we've discovered that some inexpensive ATX
> power supplies don't expect to have PE come up immediately when they're
> given power. If you see the symptom that all the LED's on your system dim
> about 1-2 seconds after you give the power supply AC for a second or so, you
> need to make a small timer circuit to wait 5 seconds or so before turning
> the PE line on.

Related info: if you have external devices (printer, and especially modem)
attached, try turning them off and then applying pwr to the computer.  In
some of the cheaper systems we have around here, the modem needs to be
turned off, or the computer flashes on for a second and then turns off...
(486 boards, AT power supplies)...  I did a bit of measuring, and on these
cheap ones, some of the +12V from the modem serial lines gets leaked back
into the power supply, causing it to wig out...

--mike




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  2: 7:44 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from inet-vrs-02.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by hub.freebsd.org (Postfix) with SMTP id 321B514BD4
	for <hackers@freebsd.org>; Sun, 12 Sep 1999 02:07:40 -0700 (PDT)
	(envelope-from simonmar@microsoft.com)
Received: from 157.54.9.104 by inet-vrs-02.microsoft.com (InterScan E-Mail VirusWall NT); Sun, 12 Sep 1999 02:07:16 -0700 (Pacific Daylight Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2448.0)
	id <S3061V2B>; Sun, 12 Sep 1999 02:07:15 -0700
Message-ID: <8B57882C41A0D1118F7100805F9F68B51232C0E2@RED-MSG-45>
From: Simon Marlow <simonmar@microsoft.com>
To: "'hackers@freebsd.org'" <hackers@freebsd.org>
Subject: How to go about making a compiler port
Date: Sun, 12 Sep 1999 02:07:15 -0700
X-Mailer: Internet Mail Service (5.5.2448.0)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[originally sent to ports, resending to hackers at the suggestion of someone
on that list.]

Hi Folks,

I'd like to make a port for our Haskell compiler, GHC (see
http://research.microsoft.com/users/t-simonm/ghc).  There are some subtle
problems with this:

	- GHC depends on itself.  That is, you need GHC
	  installed in order to build GHC.

	- GHC depends on Happy, our parser generator.
	
	- Happy depends on GHC (it's written in Haskell).

So, one solution would be to provide a binary port, say ghc-bin, which would
install a binary distribution.  I checked the modula-3 port, and it doesn't
seem to have a binary port, so what's the accepted way of doing this?

It's possible to bootstrap GHC from intermediate C files, but it's a bit
fiddly and I'd prefer not to do this if possible.  However, one thing that
occurs to me is that the port could bootstrap itself from C if you say 'make
BOOTSTRAP=YES', and otherwise attempt to build using an installed GHC.

Any thoughts greatly appreciated.

I'm not on this list, BTW.

Cheers,
	Simon


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  2:35:21 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from ns.skylink.it (ns.skylink.it [194.177.113.1])
	by hub.freebsd.org (Postfix) with ESMTP id A56C415017
	for <hackers@FreeBSD.ORG>; Sun, 12 Sep 1999 02:35:17 -0700 (PDT)
	(envelope-from hibma@skylink.it)
Received: from heidi.plazza.it (va-132.skylink.it [194.185.55.132])
	by ns.skylink.it (8.9.1/8.8.8) with ESMTP id LAA23105;
	Sun, 12 Sep 1999 11:35:22 +0200
Received: from localhost (localhost [127.0.0.1])
	by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id JAA18643;
	Sun, 12 Sep 1999 09:35:48 GMT
X-No-Spam: Neither the receipients nor the senders email address(s) are
	to be used for Unsolicited (Commercial) Email without the
	explicit written consent of either party; as a per-message
	fee is incurred for inbound and outbound traffic to the originator.
Posted-Date: Sun, 12 Sep 1999 09:35:48 GMT
Date: Sun, 12 Sep 1999 11:35:48 +0200 (CEST)
From: Nick Hibma <hibma@skylink.it>
X-Sender: n_hibma@heidi.plazza.it
Reply-To: Nick Hibma <hibma@skylink.it>
To: Simon Marlow <simonmar@microsoft.com>
Cc: "'hackers@freebsd.org'" <hackers@FreeBSD.ORG>
Subject: Re: How to go about making a compiler port
In-Reply-To: <8B57882C41A0D1118F7100805F9F68B51232C0E2@RED-MSG-45>
Message-ID: <Pine.BSF.4.10.9909121134460.18636-100000@heidi.plazza.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


What about providing a package (binary only distribution) and a port?
And the port could include the possibility to bootstrap the
installation.

See the handbook on how to build a package.

Nick


On Sun, 12 Sep 1999, Simon Marlow wrote:

> [originally sent to ports, resending to hackers at the suggestion of someone
> on that list.]
> 
> Hi Folks,
> 
> I'd like to make a port for our Haskell compiler, GHC (see
> http://research.microsoft.com/users/t-simonm/ghc).  There are some subtle
> problems with this:
> 
> 	- GHC depends on itself.  That is, you need GHC
> 	  installed in order to build GHC.
> 
> 	- GHC depends on Happy, our parser generator.
> 	
> 	- Happy depends on GHC (it's written in Haskell).
> 
> So, one solution would be to provide a binary port, say ghc-bin, which would
> install a binary distribution.  I checked the modula-3 port, and it doesn't
> seem to have a binary port, so what's the accepted way of doing this?
> 
> It's possible to bootstrap GHC from intermediate C files, but it's a bit
> fiddly and I'd prefer not to do this if possible.  However, one thing that
> occurs to me is that the port could bootstrap itself from C if you say 'make
> BOOTSTRAP=YES', and otherwise attempt to build using an installed GHC.
> 
> Any thoughts greatly appreciated.
> 
> I'm not on this list, BTW.
> 
> Cheers,
> 	Simon
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 
> 

-- 
e-Mail: hibma@skylink.it



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  3:41: 3 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dfw-ix14.ix.netcom.com (dfw-ix14.ix.netcom.com [206.214.98.14])
	by hub.freebsd.org (Postfix) with ESMTP id 6216114E0E
	for <hackers@freebsd.org>; Sun, 12 Sep 1999 03:41:01 -0700 (PDT)
	(envelope-from asami@stampede.cs.berkeley.edu)
Received: (from smap@localhost)
          by dfw-ix14.ix.netcom.com (8.8.4/8.8.4)
	  id FAA09275; Sun, 12 Sep 1999 05:40:59 -0500 (CDT)
Received: from sji-ca6-118.ix.netcom.com(205.186.213.118) by dfw-ix14.ix.netcom.com via smap (V1.3)
	id rma009256; Sun Sep 12 05:40:27 1999
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id DAA13996; Sun, 12 Sep 1999 03:40:25 -0700 (PDT)
To: Simon Marlow <simonmar@microsoft.com>
Cc: "'hackers@freebsd.org'" <hackers@freebsd.org>
Subject: Re: How to go about making a compiler port
References: <8B57882C41A0D1118F7100805F9F68B51232C0E2@RED-MSG-45>
From: asami@freebsd.org (Satoshi - Ports Wraith - Asami)
Date: 12 Sep 1999 03:40:24 -0700
In-Reply-To: Simon Marlow's message of "Sun, 12 Sep 1999 02:07:15 -0700"
Message-ID: <vqcaeqs4dlz.fsf@silvia.hip.berkeley.edu>
Lines: 28
X-Mailer: Gnus v5.7/Emacs 20.4
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

 * From: Simon Marlow <simonmar@microsoft.com>

 * [originally sent to ports, resending to hackers at the suggestion of someone
 * on that list.]

Sorry, you probably caught us at the busiest time right before the
release....

 * Hi Folks,
 * 
 * I'd like to make a port for our Haskell compiler, GHC (see
 * http://research.microsoft.com/users/t-simonm/ghc).  There are some subtle
 * problems with this:
 * 
 * 	- GHC depends on itself.  That is, you need GHC
 * 	  installed in order to build GHC.
 * 
 * 	- GHC depends on Happy, our parser generator.
 * 	
 * 	- Happy depends on GHC (it's written in Haskell).
 * 
 * So, one solution would be to provide a binary port, say ghc-bin, which would
 * install a binary distribution.  I checked the modula-3 port, and it doesn't
 * seem to have a binary port, so what's the accepted way of doing this?

Look at lang/gnat.  It has a similar situation.

Satoshi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  5:50:50 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from musashi.et.bocholt.fh-ge.de (reserve.et.bocholt.fh-gelsenkirchen.de [193.175.197.95])
	by hub.freebsd.org (Postfix) with ESMTP id D78B114FAD
	for <hackers@FreeBSD.ORG>; Sun, 12 Sep 1999 05:50:43 -0700 (PDT)
	(envelope-from hank@musashi.et.bocholt.fh-ge.de)
Received: from localhost (localhost.et.bocholt.fh-ge.de [127.0.0.1])
	by musashi.et.bocholt.fh-ge.de (8.9.3/8.9.3) with ESMTP id OAA09438;
	Sun, 12 Sep 1999 14:50:35 +0200 (CEST)
	(envelope-from hank@musashi.et.bocholt.fh-ge.de)
Message-Id: <199909121250.OAA09438@musashi.et.bocholt.fh-ge.de>
To: Wes Peters <wes@softweyr.com>
Cc: hackers@FreeBSD.ORG
Subject: Re: More press 
In-reply-to: Your message of "Fri, 10 Sep 1999 15:42:55 MDT."
             <37D97B5F.1AEC5CCD@softweyr.com> 
Date: Sun, 12 Sep 1999 14:50:35 +0200
From: Dirk GOUDERS <hank@musashi.et.bocholt.fh-ge.de>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


 > > 
 > >  > There is a short but sweet[1] article on ZDNet today regarding FreeBSD:
 > >  >
 > >  > http://www.zdnet.com/zdtv/screensavers/answerstips/story/0,3656,2324624,00.html
 > > 
 > > Hmm, can't find that sweet thing -- typo?
 > 
 > Nope, it worked fine for me.  Given how short it is, this article really packs
 > a POSITIVE punch for FreeBSD.  Here's the text:
 > 
 > *SNIP*

Oh, sorry -- my "browse-url-at-mouse" function made

http://www.zdnet.com/zdtv/screensavers/answerstips/story/02c36562c23246242c00.html

of it...

Anyway, thanks for the text :-)

Dirk


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  6:13:52 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60])
	by hub.freebsd.org (Postfix) with ESMTP id 0CF3A14A06
	for <hackers@freebsd.org>; Sun, 12 Sep 1999 06:13:43 -0700 (PDT)
	(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.196.148]) by smtp02.wxs.nl
          (Netscape Messaging Server 3.61)  with ESMTP id AAA5E17;
          Sun, 12 Sep 1999 15:13:42 +0200
Received: (from asmodai@localhost)
	by daemon.ninth-circle.org (8.9.3/8.9.3) id OAA82864;
	Sun, 12 Sep 1999 14:47:21 +0200 (CEST)
	(envelope-from asmodai)
Date: Sun, 12 Sep 1999 14:47:21 +0200
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Simon Marlow <simonmar@microsoft.com>
Cc: "'hackers@freebsd.org'" <hackers@freebsd.org>
Subject: Re: How to go about making a compiler port
Message-ID: <19990912144720.C81750@daemon.ninth-circle.org>
References: <8B57882C41A0D1118F7100805F9F68B51232C0E2@RED-MSG-45>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.7i
In-Reply-To: <8B57882C41A0D1118F7100805F9F68B51232C0E2@RED-MSG-45>
Organisation: Ninth-Circle Enterprises
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

* Simon Marlow (simonmar@microsoft.com) [990912 13:05]:

>I'd like to make a port for our Haskell compiler, GHC (see
>http://research.microsoft.com/users/t-simonm/ghc).  There are some subtle
>problems with this:
>
>	- GHC depends on itself.  That is, you need GHC
>	  installed in order to build GHC.
>	- GHC depends on Happy, our parser generator.
>	- Happy depends on GHC (it's written in Haskell).

>So, one solution would be to provide a binary port, say ghc-bin, which would
>install a binary distribution.  I checked the modula-3 port, and it doesn't
>seem to have a binary port, so what's the accepted way of doing this?

Well, you could also take a peek at net/cvsup-bin
Another binary used a lot. It might give some ideas.

>It's possible to bootstrap GHC from intermediate C files, but it's a bit
>fiddly and I'd prefer not to do this if possible.  However, one thing that
>occurs to me is that the port could bootstrap itself from C if you say 'make
>BOOTSTRAP=YES', and otherwise attempt to build using an installed GHC.

*nod*
That could be a solution. Although it requires a clue.
Normally one does:
make
make install
make clean

What could be a solution would be to make and after the make go
interactive and ask to try to bootstrap from C or use the GHC-binary.
print/apsfilter is a good example of interactive stuff...

>Any thoughts greatly appreciated.

These are just some random thoughts. Surely I am missing some pitfalls,
but these might spark some ideas.

-- 
Jeroen Ruigrok van der Werven/Asmodai                  asmodai(at)wxs.nl
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
Network/Security Specialist        BSD: Technical excellence at its best
If I am telling you the Truth now, do you believe it?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  6:23: 6 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id A954814A06
	for <hackers@FreeBSD.ORG>; Sun, 12 Sep 1999 06:23:03 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.3) id PAA13935;
	Sun, 12 Sep 1999 15:22:55 +0200 (CEST)
	(envelope-from des)
To: Dirk GOUDERS <hank@musashi.et.bocholt.fh-ge.de>
Cc: Wes Peters <wes@softweyr.com>, hackers@FreeBSD.ORG
Subject: Re: More press
References: <199909121250.OAA09438@musashi.et.bocholt.fh-ge.de>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 12 Sep 1999 15:22:55 +0200
In-Reply-To: Dirk GOUDERS's message of "Sun, 12 Sep 1999 14:50:35 +0200"
Message-ID: <xzp671g2rio.fsf@flood.ping.uio.no>
Lines: 15
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dirk GOUDERS <hank@musashi.et.bocholt.fh-ge.de> writes:
> Oh, sorry -- my "browse-url-at-mouse" function made
> 
> http://www.zdnet.com/zdtv/screensavers/answerstips/story/02c36562c23246242c00.html
> 
> of it...

Netscape uses commans to separate parameters to the OpenURL command.
Fortunately, the API is open and documented, so there's nothing to
stop someone from writing a small command-line util that does the
equivalent of "netscape -remote" except faster and better.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  6:25:15 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id 4A8B814A06
	for <freebsd-hackers@FreeBSD.ORG>; Sun, 12 Sep 1999 06:25:11 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.3) id PAA13950;
	Sun, 12 Sep 1999 15:25:04 +0200 (CEST)
	(envelope-from des)
To: chris@calldei.com
Cc: Narvi <narvi@haldjas.folklore.ee>,
	Julian Elischer <julian@whistle.com>,
	Chuck Robey <chuckr@picnic.mat.net>,
	Gustavo V G C Rios <grios@ddsecurity.com.br>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: CS Project
References: <Pine.BSF.3.95.990909005604.958A-100000@current1.whistle.com>  <Pine.BSF.3.96.990909222730.30127B-100000@haldjas.folklore.ee> <19990909144235.E1834@holly.calldei.com>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 12 Sep 1999 15:25:03 +0200
In-Reply-To: Chris Costello's message of "Thu, 09 Sep 1999 14:42:35 -0500"
Message-ID: <xzp4sh02rf4.fsf@flood.ping.uio.no>
Lines: 12
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Chris Costello <chris@calldei.com> writes:
> On Thu, Sep 09, 1999, Narvi wrote:
> > It sounds like a "FreeBSD VM", VM taken to mean virtual machine. Anybody
> > in such a 'jar' would not notice (be able to notice) the existence of
> > others at all. 
>    In Texas we call that a chroot.

ITYM jail(2), which is only available in -CURRENT.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  6:33: 6 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from tinker.com (troll.tinker.com [204.214.7.146])
	by hub.freebsd.org (Postfix) with ESMTP id E307415188
	for <hackers@FreeBSD.ORG>; Sun, 12 Sep 1999 06:32:55 -0700 (PDT)
	(envelope-from kim@tinker.com)
Received: by localhost (8.8.5/8.8.5)
Received: by mail.tinker.com via smap (V2.0)
	id xma007008; Sun Sep 12 08:11:06 1999
Received: by localhost (8.8.8/8.8.8) id IAA00498; Sun, 12 Sep 1999 08:32:26 -0500 (CDT)
Message-ID: <37DBABEC.CEEA2844@tinker.com>
Date: Sun, 12 Sep 1999 08:34:36 -0500
From: Kim Shrier <kim@tinker.com>
Organization: Shrier and Deihl
X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Simon Marlow <simonmar@microsoft.com>
Cc: "'hackers@freebsd.org'" <hackers@FreeBSD.ORG>
Subject: Re: How to go about making a compiler port
References: <8B57882C41A0D1118F7100805F9F68B51232C0E2@RED-MSG-45>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The Objective C port in lang/objc has the same problem.  The Makefile
detects if there is an Objective C compiler and if not, it downloads
a bootstrap version of the compiler as C source and builds that first.
It then uses the bootstrap compiler to build the Objective C compiler
and support libraries.  This way, you don't have to add a
"make bootstrap" step.

Kim Shrier
-- 
 Kim Shrier - principal, Shrier and Deihl - mailto:kim@tinker.com
Remote Unix Network Admin, Security, Internet Software Development
  Tinker Internet Services - Superior FreeBSD-based Web Hosting
                     http://www.tinker.com/

Simon Marlow wrote:
> 
> [originally sent to ports, resending to hackers at the suggestion of someone
> on that list.]
> 
> Hi Folks,
> 
> I'd like to make a port for our Haskell compiler, GHC (see
> http://research.microsoft.com/users/t-simonm/ghc).  There are some subtle
> problems with this:
> 
>         - GHC depends on itself.  That is, you need GHC
>           installed in order to build GHC.
> 
>         - GHC depends on Happy, our parser generator.
> 
>         - Happy depends on GHC (it's written in Haskell).
> 
> So, one solution would be to provide a binary port, say ghc-bin, which would
> install a binary distribution.  I checked the modula-3 port, and it doesn't
> seem to have a binary port, so what's the accepted way of doing this?
> 
> It's possible to bootstrap GHC from intermediate C files, but it's a bit
> fiddly and I'd prefer not to do this if possible.  However, one thing that
> occurs to me is that the port could bootstrap itself from C if you say 'make
> BOOTSTRAP=YES', and otherwise attempt to build using an installed GHC.
> 
> Any thoughts greatly appreciated.
> 
> I'm not on this list, BTW.
> 
> Cheers,
>         Simon
>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  7: 2:25 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.go2france.com (go2france.com [209.51.193.70])
	by hub.freebsd.org (Postfix) with SMTP id 73B2D14E85
	for <freebsd-hackers@freebsd.org>; Sun, 12 Sep 1999 07:02:17 -0700 (PDT)
	(envelope-from lconrad@Go2France.com)
Received: from superviseur [62.161.63.210] by mail.go2france.com with ESMTP
  (SMTPD32-4.03) id AD5F1C9401C4; Sun, 12 Sep 1999 08:32:31 EDT
Message-Id: <4.2.0.58.19990912155649.00d52340@go2france.com>
X-Sender: lconrad@go2france.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Sun, 12 Sep 1999 16:01:57 +0200
To: freebsd-hackers@freebsd.org
From: Len Conrad <lconrad@Go2France.com>
Subject: Ariel RS 2000 T1/EI card
In-Reply-To: <37DBABEC.CEEA2844@tinker.com>
References: <8B57882C41A0D1118F7100805F9F68B51232C0E2@RED-MSG-45>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

A few weeks ago...

R Cramer <rcramer@sytex.net> and Niall Smart <niall@pobox.com>

told me they were working on, or wanted to work on, a RAS server using the 
2000. Now, neither one responds to several mails.

Anybody know of anybody ELSE looking at this card or how else to contact 
these guys?

tia,
Len





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  8: 2:20 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from www.crb-web.com (ns1.crb-web.com [209.70.120.131])
	by hub.freebsd.org (Postfix) with SMTP id 5B53514EFE
	for <freebsd-hackers@FreeBSD.ORG>; Sun, 12 Sep 1999 08:02:16 -0700 (PDT)
	(envelope-from wayne@crb.crb-web.com)
Received: (qmail 7956 invoked by uid 1001); 12 Sep 1999 15:53:33 -0000
Date: Sun, 12 Sep 1999 11:53:33 -0400 (EDT)
From: Wayne Cuddy <wayne@crb-web.com>
Reply-To: wayne@crb-web.com
Cc: FreeBSD Hackers List <freebsd-hackers@FreeBSD.ORG>
Subject: more info Re: how did I manage this?
In-Reply-To: <19990911160425.B13033@holly.calldei.com>
Message-ID: <Pine.LNX.4.10.9909121133280.7847-100000@crb.crb-web.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 11 Sep 1999, Chris Costello wrote:

> Date: Sat, 11 Sep 1999 16:04:25 -0500
> From: Chris Costello <chris@calldei.com>
> To: Wayne Cuddy <wayne@crb-web.com>
> Cc: FreeBSD Hackers List <freebsd-hackers@FreeBSD.ORG>
> Subject: Re: how did I manage this? (fwd)
> 
> On Sat, Sep 11, 1999, Wayne Cuddy wrote:
> > I tried this on questions with no response and wanted give you guys a shot.
> 
> ls -li /path/to/your/alleged/hardlink
> ls -li /
> 
>    Are the inode numbers the same?
> 
> > Thanks,
> > Wayne
> 
> -- 
> |Chris Costello <chris@calldei.com>
> |In the field of observation, chance favors only the prepared minds.
> `-------------------------------------------------------------------
>
Here is my directory listing:
drwxrwxr-x  3 wcuddy  wcuddy   512 Sep  5 17:29 $DEST_DIR
-rwxr-xr-x  1 wcuddy  wcuddy  2324 Sep  6 22:51 do_install.sh
-rw-rw-r--  1 wcuddy  wcuddy   533 Sep  5 21:12 file_list.txt
-rw-rw-r--  1 wcuddy  wcuddy   155 Sep  5 21:58 install.conf
-rw-rw-r--  1 wcuddy  wcuddy   145 Sep  6 22:27 post-install
-rw-rw-r--  1 wcuddy  wcuddy   144 Sep  6 22:24 pre-install

Here is the output of my mount:
/dev/da0s1a on / (asynchronous, NFS exported, local, writes: sync 26 async
22259)
/dev/da2s1e on /home (asynchronous, local, writes: sync 8 async 5181)
/dev/da1s1e on /usr (asynchronous, local, writes: sync 3 async 20654)
procfs on /proc (local)

Since /home is on a separate file system I don't think it is a hard link.
However, if do a 'cd \$DEST_DIR' I end up in the root directory.  If I do a
'rm $DEST_DIR/', I get 'rm: /: is a directory'.  If it can't be a hard link I
have no idea what it is.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  8: 6:59 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mta2.rcsntx.swbell.net (mta2.rcsntx.swbell.net [151.164.30.26])
	by hub.freebsd.org (Postfix) with ESMTP id 2580614EFE
	for <freebsd-hackers@FreeBSD.ORG>; Sun, 12 Sep 1999 08:06:51 -0700 (PDT)
	(envelope-from chris@holly.dyndns.org)
Received: from holly.dyndns.org (adsl-216-62-157-60.dsl.hstntx.swbell.net)
 by mta2.rcsntx.swbell.net
 (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7)
 with ESMTP id <0FHY003XBCLZU5@mta2.rcsntx.swbell.net> for
 freebsd-hackers@FreeBSD.ORG; Sun, 12 Sep 1999 10:06:00 -0500 (CDT)
Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3)
 id KAA15958; Sun, 12 Sep 1999 10:05:58 -0500 (CDT envelope-from chris)
Date: Sun, 12 Sep 1999 10:05:57 -0500
From: Chris Costello <chris@calldei.com>
Subject: Re: more info Re: how did I manage this?
In-reply-to: <Pine.LNX.4.10.9909121133280.7847-100000@crb.crb-web.com>
To: Wayne Cuddy <wayne@crb-web.com>
Cc: FreeBSD Hackers List <freebsd-hackers@FreeBSD.ORG>
Reply-To: chris@calldei.com
Message-id: <19990912100557.E14022@holly.calldei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
User-Agent: Mutt/0.96.6i
References: <19990911160425.B13033@holly.calldei.com>
 <Pine.LNX.4.10.9909121133280.7847-100000@crb.crb-web.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 12, 1999, Wayne Cuddy wrote:
> Here is my directory listing:
> drwxrwxr-x  3 wcuddy  wcuddy   512 Sep  5 17:29 $DEST_DIR
> -rwxr-xr-x  1 wcuddy  wcuddy  2324 Sep  6 22:51 do_install.sh
> -rw-rw-r--  1 wcuddy  wcuddy   533 Sep  5 21:12 file_list.txt
> -rw-rw-r--  1 wcuddy  wcuddy   155 Sep  5 21:58 install.conf
> -rw-rw-r--  1 wcuddy  wcuddy   145 Sep  6 22:27 post-install
> -rw-rw-r--  1 wcuddy  wcuddy   144 Sep  6 22:24 pre-install
> 
> Here is the output of my mount:
> /dev/da0s1a on / (asynchronous, NFS exported, local, writes: sync 26 async
> 22259)
> /dev/da2s1e on /home (asynchronous, local, writes: sync 8 async 5181)
> /dev/da1s1e on /usr (asynchronous, local, writes: sync 3 async 20654)
> procfs on /proc (local)
> 
> Since /home is on a separate file system I don't think it is a hard link.
> However, if do a 'cd \$DEST_DIR' I end up in the root directory.  If I do a
> 'rm $DEST_DIR/', I get 'rm: /: is a directory'.  If it can't be a hard link I
> have no idea what it is.

   That's because $DEST_DIR is expanding to "/".

   Try unsetting that variable and then enclosing it in single
quotes in your rm command.

-- 
|Chris Costello <chris@calldei.com>
|Managing programmers is like herding cats.
`------------------------------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  8:14:13 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mta2.rcsntx.swbell.net (mta2.rcsntx.swbell.net [151.164.30.26])
	by hub.freebsd.org (Postfix) with ESMTP id 8A12614D70
	for <hackers@FreeBSD.org>; Sun, 12 Sep 1999 08:14:11 -0700 (PDT)
	(envelope-from chris@holly.dyndns.org)
Received: from holly.dyndns.org (adsl-216-62-157-60.dsl.hstntx.swbell.net)
 by mta2.rcsntx.swbell.net
 (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7)
 with ESMTP id <0FHY0040YCYZ6O@mta2.rcsntx.swbell.net> for hackers@FreeBSD.org;
 Sun, 12 Sep 1999 10:13:47 -0500 (CDT)
Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3)
 id KAA16016; Sun, 12 Sep 1999 10:13:46 -0500 (CDT envelope-from chris)
Date: Sun, 12 Sep 1999 10:13:45 -0500
From: Chris Costello <chris@calldei.com>
Subject: Re: more info Re: how did I manage this?
In-reply-to: <19990912100557.E14022@holly.calldei.com>
To: Wayne Cuddy <wayne@crb-web.com>
Cc: hackers@FreeBSD.org
Reply-To: chris@calldei.com
Message-id: <19990912101345.F14022@holly.calldei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
User-Agent: Mutt/0.96.6i
References: <19990911160425.B13033@holly.calldei.com>
 <Pine.LNX.4.10.9909121133280.7847-100000@crb.crb-web.com>
 <19990912100557.E14022@holly.calldei.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 12, 1999, Chris Costello wrote:
> > However, if do a 'cd \$DEST_DIR' I end up in the root directory.  If I do a
> > 'rm $DEST_DIR/', I get 'rm: /: is a directory'.  If it can't be a hard link I
> > have no idea what it is.
> 
>    That's because $DEST_DIR is expanding to "/".

   Oops!  No it's not.  It's expanding to nothing because it's
unset.  See my second paragraph (sentence):

>    Try unsetting that variable and then enclosing it in single
> quotes in your rm command.

-- 
|Chris Costello <chris@calldei.com>
|A low level language is one whose programs
|require attention to the irrelevant.
`------------------------------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  8:20:10 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37])
	by hub.freebsd.org (Postfix) with ESMTP id 385A514D70
	for <freebsd-hackers@freebsd.org>; Sun, 12 Sep 1999 08:20:05 -0700 (PDT)
	(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.196.148]) by smtp03.wxs.nl
          (Netscape Messaging Server 3.61)  with ESMTP id AAA6AEE;
          Sun, 12 Sep 1999 17:20:03 +0200
Received: (from asmodai@localhost)
	by daemon.ninth-circle.org (8.9.3/8.9.3) id RAA83274;
	Sun, 12 Sep 1999 17:20:52 +0200 (CEST)
	(envelope-from asmodai)
Date: Sun, 12 Sep 1999 17:20:51 +0200
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Len Conrad <lconrad@Go2France.com>
Cc: freebsd-hackers@freebsd.org
Subject: Re: Ariel RS 2000 T1/EI card
Message-ID: <19990912172051.J81750@daemon.ninth-circle.org>
References: <8B57882C41A0D1118F7100805F9F68B51232C0E2@RED-MSG-45> <37DBABEC.CEEA2844@tinker.com> <4.2.0.58.19990912155649.00d52340@go2france.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.7i
In-Reply-To: <4.2.0.58.19990912155649.00d52340@go2france.com>
Organisation: Ninth-Circle Enterprises
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[snip]

Please people. When posting messages DON'T reply to other messages
if the topic has NOTHING to do with the topic being discussed.

This obviously messes up reply-to headers, makes the archives less
useful as well and generally screws up threading in MUA's.

Thanks.

-- 
Jeroen Ruigrok van der Werven/Asmodai                  asmodai(at)wxs.nl
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
Network/Security Specialist        BSD: Technical excellence at its best
...fools rush in where Daemons fear to tread.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  8:38:43 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from www.crb-web.com (ns1.crb-web.com [209.70.120.131])
	by hub.freebsd.org (Postfix) with SMTP id 4B65814F49
	for <hackers@FreeBSD.org>; Sun, 12 Sep 1999 08:38:38 -0700 (PDT)
	(envelope-from wayne@crb.crb-web.com)
Received: (qmail 8192 invoked by uid 1001); 12 Sep 1999 16:29:55 -0000
Date: Sun, 12 Sep 1999 12:29:55 -0400 (EDT)
From: Wayne Cuddy <wayne@crb-web.com>
Reply-To: wayne@crb-web.com
Cc: hackers@FreeBSD.org
Subject: Re: more info Re: how did I manage this?
In-Reply-To: <19990912101345.F14022@holly.calldei.com>
Message-ID: <Pine.LNX.4.10.9909121224360.7847-100000@crb.crb-web.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, 12 Sep 1999, Chris Costello wrote:

> Date: Sun, 12 Sep 1999 10:13:45 -0500
> From: Chris Costello <chris@calldei.com>
> To: Wayne Cuddy <wayne@crb-web.com>
> Cc: hackers@FreeBSD.org
> Subject: Re: more info Re: how did I manage this?
> 
> On Sun, Sep 12, 1999, Chris Costello wrote:
> > > However, if do a 'cd \$DEST_DIR' I end up in the root directory.  If I do a
> > > 'rm $DEST_DIR/', I get 'rm: /: is a directory'.  If it can't be a hard link I
> > > have no idea what it is.
> > 
> >    That's because $DEST_DIR is expanding to "/".
> 
>    Oops!  No it's not.  It's expanding to nothing because it's
> unset.  See my second paragraph (sentence):
> 
> >    Try unsetting that variable and then enclosing it in single
> > quotes in your rm command.
> 
> -- 
> |Chris Costello <chris@calldei.com>
> |A low level language is one whose programs
> |require attention to the irrelevant.
> `------------------------------------------
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 
It is not set but also it will not expand to nothing as I prefixed it with the
'\' character.  For instance if you do 'ls \$HOME' the ls command will look
for an entry of $HOME.  However I went ahead and tried the single quotes and
some more commands (output below):

>rm '$DEST_DIR'
rm: $DEST_DIR: is a directory

>ls '$DEST_DIR'
$2

Interestingly enough 2 is the inode number of both the root directory and the root
directory of the /home partition.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12  9:22: 9 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28])
	by hub.freebsd.org (Postfix) with ESMTP id EA9BE14CCD
	for <hackers@FreeBSD.ORG>; Sun, 12 Sep 1999 09:22:07 -0700 (PDT)
	(envelope-from chris@holly.dyndns.org)
Received: from holly.dyndns.org (adsl-216-62-157-60.dsl.hstntx.swbell.net)
 by mta4.rcsntx.swbell.net
 (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7)
 with ESMTP id <0FHY00DS1G4TX7@mta4.rcsntx.swbell.net> for hackers@FreeBSD.ORG;
 Sun, 12 Sep 1999 11:22:05 -0500 (CDT)
Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3)
 id LAA16137; Sun, 12 Sep 1999 11:22:03 -0500 (CDT envelope-from chris)
Date: Sun, 12 Sep 1999 11:22:03 -0500
From: Chris Costello <chris@calldei.com>
Subject: Re: more info Re: how did I manage this?
In-reply-to: <Pine.LNX.4.10.9909121224360.7847-100000@crb.crb-web.com>
To: Wayne Cuddy <wayne@crb-web.com>
Cc: hackers@FreeBSD.ORG
Reply-To: chris@calldei.com
Message-id: <19990912112202.G14022@holly.calldei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
User-Agent: Mutt/0.96.6i
References: <19990912101345.F14022@holly.calldei.com>
 <Pine.LNX.4.10.9909121224360.7847-100000@crb.crb-web.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 12, 1999, Wayne Cuddy wrote:
> >ls '$DEST_DIR'
> $2
> 
> Interestingly enough 2 is the inode number of both the root directory and the root
> directory of the /home partition.

   That's not all too interesting.  It seems to be normal:

$ ls -ldi /usr / /var
2 drwxr-xr-x  20 root  wheel  1024 Aug 20 21:15 /
2 drwxr-xr-x  27 root  wheel   512 Sep  9 15:58 /usr
2 drwxr-xr-x  18 root  wheel   512 May 27 06:13 /var

-- 
|Chris Costello <chris@calldei.com>
|Programming Department:  Mistakes made while you wait.
`------------------------------------------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 11:39:20 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [209.145.74.241])
	by hub.freebsd.org (Postfix) with ESMTP id 9777B14C29
	for <freebsd-hackers@FreeBSD.ORG>; Sun, 12 Sep 1999 11:39:16 -0700 (PDT)
	(envelope-from adrian@ubergeeks.com)
Received: from localhost (adrian@localhost)
	by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id OAA00487;
	Sun, 12 Sep 1999 14:39:01 -0400 (EDT)
	(envelope-from adrian@ubergeeks.com)
Date: Sun, 12 Sep 1999 14:39:01 -0400 (EDT)
From: Adrian Filipi-Martin <adrian@ubergeeks.com>
Reply-To: Adrian Filipi-Martin <adrian@ubergeeks.com>
To: Chris Costello <chris@calldei.com>
Cc: Wayne Cuddy <wayne@crb-web.com>,
	FreeBSD Hackers List <freebsd-hackers@FreeBSD.ORG>
Subject: Re: more info Re: how did I manage this?
In-Reply-To: <19990912100557.E14022@holly.calldei.com>
Message-ID: <Pine.BSF.3.96.990912142121.290H-100000@lorax.ubergeeks.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, 12 Sep 1999, Chris Costello wrote:

> On Sun, Sep 12, 1999, Wayne Cuddy wrote:
> > Here is my directory listing:
> > drwxrwxr-x  3 wcuddy  wcuddy   512 Sep  5 17:29 $DEST_DIR
> > -rwxr-xr-x  1 wcuddy  wcuddy  2324 Sep  6 22:51 do_install.sh
> > -rw-rw-r--  1 wcuddy  wcuddy   533 Sep  5 21:12 file_list.txt
> > -rw-rw-r--  1 wcuddy  wcuddy   155 Sep  5 21:58 install.conf
> > -rw-rw-r--  1 wcuddy  wcuddy   145 Sep  6 22:27 post-install
> > -rw-rw-r--  1 wcuddy  wcuddy   144 Sep  6 22:24 pre-install
> > 
> > Here is the output of my mount:
> > /dev/da0s1a on / (asynchronous, NFS exported, local, writes: sync 26 async
> > 22259)
> > /dev/da2s1e on /home (asynchronous, local, writes: sync 8 async 5181)
> > /dev/da1s1e on /usr (asynchronous, local, writes: sync 3 async 20654)
> > procfs on /proc (local)
> > 
> > Since /home is on a separate file system I don't think it is a hard link.
> > However, if do a 'cd \$DEST_DIR' I end up in the root directory.  If I do a
> > 'rm $DEST_DIR/', I get 'rm: /: is a directory'.  If it can't be a hard link I
> > have no idea what it is.

	[This is actually  aresponse to two messages.  Sorry, but I didn't
	 want to repeat myself. ]

	The root inode number of any filesystem is '2'.  I forget why, but
that's the way it is. 

	Now, first I doubt the above is a hard link to / because the
ownership is in the inode and unless you tell me that / is owned by
wcuddy:wcuddy, it cannot be linked to the same inode. 

	What does 'pwd' and 'df .' give you back as your current directory
and physical device?  You alos ought to include the '-i' in the ls command
because it will add the inode number to the listing.

	Try 'ls -l '$DEST_DIR/kernel'".  Unless you get the same output as
"ls -l /kernel", you probably just have a bad directory name.

	If you really have a a directory with a link count of three, it
ought to be a directory with exactly one subdirectory.  Given that root has
a bunch of subdirectories, a link count more like the 20 shown above is
typical.

	After reading your other messages, I think you have a "wierdly" 
named directory with another "wierdly" named directory in it.  In
particular both have $'s in their names.  I bet it looks somehting like the
following.  Note the link count for '$DEST_DIR' is 3 as in your listing
above. 

> : ubergeek@terrafirma; mkdir -p \$DEST_DIR/\$2
> : ubergeek@terrafirma; ls -laRi
> total 3
> 6020 drwxrwxr-x  3 ubergeek  wheel  512 Sep 12 14:21 $DEST_DIR/
> 6018 drwxrwxr-x  3 ubergeek  wheel  512 Sep 12 14:21 ./
>    2 drwxrwxrwt  6 root      wheel  512 Sep 12 14:12 ../
> 
> ./$DEST_DIR:
> total 3
> 6026 drwxrwxr-x  2 ubergeek  wheel  512 Sep 12 14:21 $2/
> 6020 drwxrwxr-x  3 ubergeek  wheel  512 Sep 12 14:21 ./
> 6018 drwxrwxr-x  3 ubergeek  wheel  512 Sep 12 14:21 ../
> 
> ./$DEST_DIR/$2:
> total 2
> 6026 drwxrwxr-x  2 ubergeek  wheel  512 Sep 12 14:21 ./
> 6020 drwxrwxr-x  3 ubergeek  wheel  512 Sep 12 14:21 ../

	Now your shell is probably causing you the problems.  Make sure you
are properly quoting the paths.  single and double quotes make a big
difference here.

> : ubergeek@terrafirma; \ls -ild '$DEST_DIR/$2'
> 6026 drwxrwxr-x  2 ubergeek  wheel  512 Sep 12 14:21 $DEST_DIR/$2
> : ubergeek@terrafirma; \ls -lid "$DEST_DIR/$2"
> 2 drwxr-xr-x  20 root  wheel  512 Aug  7 16:28 /

	Notice the last line.  This is probably what is happening.  Try 'rm
-rfi *' and see if you can remove all these bad directory names and start
over.  e.g.

> : ubergeek@terrafirma; rm -rfi *
> remove $DEST_DIR? y
> remove $DEST_DIR/$2? y

	If this thread is to continue, I suggest moving it to -questions,
because I'm pretty certain it's not an actual filesystem corruption issue.

cheers,

	Adrian
--
[ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ]




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 11:45:57 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8B4BE14C10; Sun, 12 Sep 1999 11:45:50 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.3) id UAA15125;
	Sun, 12 Sep 1999 20:45:44 +0200 (CEST)
	(envelope-from des)
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: hackers@freebsd.org
Subject: Re: How to prevent motd including os info
References: <199909121749.KAA31199@gndrsh.dnsmgr.net>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 12 Sep 1999 20:45:43 +0200
In-Reply-To: "Rodney W. Grimes"'s message of "Sun, 12 Sep 1999 10:49:37 -0700 (PDT)"
Message-ID: <xzpaeqs0y08.fsf@flood.ping.uio.no>
Lines: 42
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[moving to -hackers]

"Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> writes:
> So when can we see this commited....

Already done (-CURRENT only). I've had requests (notably from Yan
Koum) to backport it to -STABLE, but I won't do it so close to a
release.

>                                      the only thing I would like
> changed is actually a general format of output change in /etc/rc.network,
> if you have a few of the ``tcp_*'' knobs set the line length gets
> a bit long, could be change the ``echo -n'''s to ``echo \t'' and loose
> the trailing ``echo '.'''.  

I don't consider that much of a problem, except in cases where
individual scripts / options produce output which breaks the line
(this is mostly a problem with ports). I wouldn't mind the changes you
suggest, but I don't care enough to actually go ahead and do it.

One thing I'd like very much, though, would be to have the output of
fsck -p logged somehow - but since we don't have anything mounted rw
when fsck runs, it's a bit hard to log to disk. You could of course
do something like this:

 fsck_output="$(/sbin/fsck -p)"
 /sbin/mount -at nonfs
 echo "${fsck_output}" >/var/run/fsck.boot

but then you wouldn't be able to see the output while it runs. The
only solution I can think of is the following:

 fsck_output="$(/sbin/fsck -p | /bin/tee /dev/console)"
 /sbin/mount -at nonfs
 echo "${fsck_output}" >/var/run/fsck.boot

but I don't expect people to be happy about moving tee(1) from
/usr/bin to /bin.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 12: 4:30 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id 23F5514DD9
	for <hackers@freebsd.org>; Sun, 12 Sep 1999 12:04:26 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id MAA31397;
	Sun, 12 Sep 1999 12:04:22 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909121904.MAA31397@gndrsh.dnsmgr.net>
Subject: Re: How to prevent motd including os info
In-Reply-To: <xzpaeqs0y08.fsf@flood.ping.uio.no> from Dag-Erling Smorgrav at "Sep 12, 1999 08:45:43 pm"
To: des@flood.ping.uio.no (Dag-Erling Smorgrav)
Date: Sun, 12 Sep 1999 12:04:22 -0700 (PDT)
Cc: hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> [moving to -hackers]
[I'm going to loose the rest of this thread since I am not on hackers :-(]

> 
> "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> writes:
> > So when can we see this commited....
> 
> Already done (-CURRENT only). I've had requests (notably from Yan
> Koum) to backport it to -STABLE, but I won't do it so close to a
> release.

I've already done the ``backport'', but your correct in that it is
a wee bit close to release, actually too late as we are in code freeze
and this is a new feature :-).

> 
> >                                      the only thing I would like
> > changed is actually a general format of output change in /etc/rc.network,
> > if you have a few of the ``tcp_*'' knobs set the line length gets
> > a bit long, could be change the ``echo -n'''s to ``echo \t'' and loose
> > the trailing ``echo '.'''.  
> 
> I don't consider that much of a problem, except in cases where
> individual scripts / options produce output which breaks the line
> (this is mostly a problem with ports). I wouldn't mind the changes you
> suggest, but I don't care enough to actually go ahead and do it.
> 
> One thing I'd like very much, though, would be to have the output of
> fsck -p logged somehow - but since we don't have anything mounted rw
> when fsck runs, it's a bit hard to log to disk. You could of course
> do something like this:

Actually I would like _all_ the output from /etc/rc* to be avaliable
after boot.  It should be in the syscons scroll back buffer, we just
need a little program to go grab it and stuff it away at the end of
/etc/rc runs.  This would be a big win for remote admining and trying
to figure out what went wrong during the last boot without having to
drive down and hook up a console of some form.  I know we could hang
serial consoles on all of them, but why spend money on hardware when
the problem can be solved with software :-).

> 
>  fsck_output="$(/sbin/fsck -p)"
>  /sbin/mount -at nonfs
>  echo "${fsck_output}" >/var/run/fsck.boot
> 
> but then you wouldn't be able to see the output while it runs. The
> only solution I can think of is the following:
> 
>  fsck_output="$(/sbin/fsck -p | /bin/tee /dev/console)"
>  /sbin/mount -at nonfs
>  echo "${fsck_output}" >/var/run/fsck.boot
> 
> but I don't expect people to be happy about moving tee(1) from
> /usr/bin to /bin.

And solving only 1 piece of output from /etc/rc is an incomplete
concept.  I really like to know if ntpdate stepped my clock 230000 seconds
for some reason, thats why this (usually means a clock chip has gone
zonkers :-)):
Index: rc.network
===================================================================
RCS file: /home/ncvs/src/etc/rc.network,v
retrieving revision 1.39.2.11
diff -u -r1.39.2.11 rc.network
--- rc.network	1999/09/03 08:57:26	1.39.2.11
+++ rc.network	1999/09/12 19:02:01
@@ -257,7 +257,7 @@
     fi
 
     if [ "X${ntpdate_enable}" = X"YES" ]; then
-	    echo -n ' ntpdate';	${ntpdate_program} ${ntpdate_flags} >/dev/null 2>&1
+	    echo -n ' ntpdate';	${ntpdate_program} ${ntpdate_flags} >>/var/log/ntpdate 2>&1
     fi
 
     if [ "X${xntpd_enable}" = X"YES" ]; then

And a whole slew of others... they just has to be a better way!!


-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 12:10:46 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id 41DA214DBB
	for <hackers@freebsd.org>; Sun, 12 Sep 1999 12:10:43 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.3) id VAA15244;
	Sun, 12 Sep 1999 21:10:39 +0200 (CEST)
	(envelope-from des)
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: hackers@freebsd.org
Subject: Re: How to prevent motd including os info
References: <199909121904.MAA31397@gndrsh.dnsmgr.net>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 12 Sep 1999 21:10:39 +0200
In-Reply-To: "Rodney W. Grimes"'s message of "Sun, 12 Sep 1999 12:04:22 -0700 (PDT)"
Message-ID: <xzp671g0wuo.fsf@flood.ping.uio.no>
Lines: 22
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> writes:
> > One thing I'd like very much, though, would be to have the output of
> > fsck -p logged somehow [...]
> Actually I would like _all_ the output from /etc/rc* to be avaliable
> after boot.  It should be in the syscons scroll back buffer, [...]

No. The scrollback may be too short (especially after an fsck of a
large filesystem after a crash), and it may even be empty (if you put
something like VESA_132x60 in allscreens_flags in rc.conf)

> And solving only 1 piece of output from /etc/rc is an incomplete
> concept.  I really like to know if ntpdate stepped my clock 230000 seconds
> for some reason, thats why this (usually means a clock chip has gone
> zonkers :-)):

Doesn't ntpdate log what it does with syslog? If not, I think
whichever syscall it is that ntpdate uses to adjust the time should
printf() or log() the change.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 14:25:43 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19])
	by hub.freebsd.org (Postfix) with ESMTP id A209E14DCE
	for <hackers@FreeBSD.ORG>; Sun, 12 Sep 1999 14:25:39 -0700 (PDT)
	(envelope-from areilly@nsw.bigpond.net.au)
Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20])
	by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id HAA15114
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 07:25:38 +1000 (EST)
X-BPC-Relay-Envelope-From: areilly@nsw.bigpond.net.au 
X-BPC-Relay-Envelope-To: <hackers@FreeBSD.ORG>
X-BPC-Relay-Sender-Host: m5.c2.telstra-mm.net.au [24.192.3.20]
X-BPC-Relay-Info: Message delivered directly.
Received: from areilly.bpc-users.org (CPE-24-192-49-170.nsw.bigpond.net.au [24.192.49.170])
	by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id HAA29249
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 07:25:37 +1000 (EST)
Received: (qmail 51738 invoked by uid 1000); 12 Sep 1999 21:25:36 -0000
From: "Andrew Reilly" <areilly@nsw.bigpond.net.au>
Date: Mon, 13 Sep 1999 07:25:36 +1000
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Cc: Simon Marlow <simonmar@microsoft.com>,
	"'hackers@freebsd.org'" <hackers@FreeBSD.ORG>
Subject: Re: How to go about making a compiler port
Message-ID: <19990913072536.A51526@gurney.reilly.home>
References: <8B57882C41A0D1118F7100805F9F68B51232C0E2@RED-MSG-45> <19990912144720.C81750@daemon.ninth-circle.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre1i
In-Reply-To: <19990912144720.C81750@daemon.ninth-circle.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 12, 1999 at 02:47:21PM +0200, Jeroen Ruigrok/Asmodai wrote:
> * Simon Marlow (simonmar@microsoft.com) [990912 13:05]:
> 
> >I'd like to make a port for our Haskell compiler, GHC (see
> >http://research.microsoft.com/users/t-simonm/ghc).  There are some subtle
> >problems with this:
> >
> >	- GHC depends on itself.  That is, you need GHC
> >	  installed in order to build GHC.
> >	- GHC depends on Happy, our parser generator.
> >	- Happy depends on GHC (it's written in Haskell).
> 
> >So, one solution would be to provide a binary port, say ghc-bin, which would
> >install a binary distribution.  I checked the modula-3 port, and it doesn't
> >seem to have a binary port, so what's the accepted way of doing this?

It's not a port yet, but compiles from it's distribuiton without
problems: SmallEiffel is also written in itself, but has a
natural intermediate compilation phase which is ANSI C.  The
distribution just includes the C, from which the compiler and
tools is built.

That seems to work pretty well.

-- 
Andrew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 14:51:33 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from fanf.noc.demon.net (fanf.noc.demon.net [195.11.55.83])
	by hub.freebsd.org (Postfix) with ESMTP id EFC8814D7A
	for <hackers@freebsd.org>; Sun, 12 Sep 1999 14:51:31 -0700 (PDT)
	(envelope-from fanf@demon.net)
Received: from fanf by fanf.noc.demon.net with local (Exim 3.02 #13)
	id 11QHWj-000Cbr-00; Sun, 12 Sep 1999 22:51:13 +0100
To: peter@netplex.com.au
From: Tony Finch <dot@dotat.at>
Cc: hackers@freebsd.org
Subject: Re: damn ATX power supplies... 
In-Reply-To: <19990911103119.4253B1CB1@overcee.netplex.com.au>
References: <Pine.BSF.4.10.9909110020500.28670-100000@picnic.mat.net>
Message-Id: <E11QHWj-000Cbr-00@fanf.noc.demon.net>
Date: Sun, 12 Sep 1999 22:51:13 +0100
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Peter Wemm <peter@netplex.com.au> wrote:
>
>On newer motherboards, it's addressable on the SMB bus (along with
>the SIMMS, the LM78/LM75/etc, the embedded LM75 in the newer CPU,
>etc). Anyway, the newer devices are programmable to do things like
>the 4-second power off delay, auto-on with AC, maintain previous
>state when AC restored, alarm clock time auto start, as well as the
>usual "turn off now" command from the APM bios.

Is there any software out there that speaks to /dev/smb?
intelligently? We have some Dell boxen with loads of SMB stuff in
them; it'd be nice to be able to see what's going on there.

Alternatively, are there freely-available SMB specs?

Tony.
-- 
f.a.n.finch    dot@dotat.at    fanf@demon.net    e pluribus unix


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 15:30:48 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id 94E4E14D84
	for <hackers@freebsd.org>; Sun, 12 Sep 1999 15:30:44 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id PAA31675;
	Sun, 12 Sep 1999 15:30:39 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909122230.PAA31675@gndrsh.dnsmgr.net>
Subject: Re: How to prevent motd including os info
In-Reply-To: <xzp671g0wuo.fsf@flood.ping.uio.no> from Dag-Erling Smorgrav at "Sep 12, 1999 09:10:39 pm"
To: des@flood.ping.uio.no (Dag-Erling Smorgrav)
Date: Sun, 12 Sep 1999 15:30:38 -0700 (PDT)
Cc: hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> writes:
> > > One thing I'd like very much, though, would be to have the output of
> > > fsck -p logged somehow [...]
> > Actually I would like _all_ the output from /etc/rc* to be avaliable
> > after boot.  It should be in the syscons scroll back buffer, [...]
> 
> No. The scrollback may be too short (especially after an fsck of a
> large filesystem after a crash), and it may even be empty (if you put
> something like VESA_132x60 in allscreens_flags in rc.conf)

We can tune the size of the scroll back buffer can't we?  And fsck output
even after a crash is usually not that long, if it gets long it usually
has more problems than fsck -p can deal with and stops any way.

Why does switching display mode screw up the scroll back buffer?  That
sounds broken to me.

> 
> > And solving only 1 piece of output from /etc/rc is an incomplete
> > concept.  I really like to know if ntpdate stepped my clock 230000 seconds
> > for some reason, thats why this (usually means a clock chip has gone
> > zonkers :-)):
> 
> Doesn't ntpdate log what it does with syslog?  If not, I think
> whichever syscall it is that ntpdate uses to adjust the time should
> printf() or log() the change.

If you give it the -s option, yes it will syslog it.  But doing that
to everything in /etc/rc* seems like a pain in the *ss...


-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 15:53: 3 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dotat.at (dotat.at [212.240.134.130])
	by hub.freebsd.org (Postfix) with ESMTP id E35CA14C43
	for <hackers@freebsd.org>; Sun, 12 Sep 1999 15:53:01 -0700 (PDT)
	(envelope-from fanf@dotat.at)
Received: from fanf by dotat.at with local (Exim 1.92 #1 (Debian))
	id 11QIUW-0006zu-00; Sun, 12 Sep 1999 23:53:00 +0100
From: Tony Finch <fanf@demon.net>
To: hackers@freebsd.org
Subject: mounting a partition more than once
Message-Id: <E11QIUW-0006zu-00@dotat.at>
Date: Sun, 12 Sep 1999 23:53:00 +0100
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Is there a reason for disallowing concurrent read-only mounts of the
same disk device? i.e. would things go pear-shaped if I added this
capability? 

Tony.
-- 
f.a.n.finch    fanf@demon.net    dot@dotat.at    e pluribus unix


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 18:13:48 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161])
	by hub.freebsd.org (Postfix) with ESMTP id 30B7714D84
	for <hackers@FreeBSD.ORG>; Sun, 12 Sep 1999 18:13:43 -0700 (PDT)
	(envelope-from doconnor@gsoft.com.au)
Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97])
	by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA00267;
	Mon, 13 Sep 1999 10:43:31 +0930 (CST)
	(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.990913104331.doconnor@gsoft.com.au>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
MIME-Version: 1.0
Content-Type: multipart/signed;
 boundary="_=XFMail.1.3.p0.FreeBSD:990913104331:7396=_";
 micalg=pgp-md5; protocol="application/pgp-signature"
In-Reply-To: <Pine.BSF.4.05.9909100620290.25719-100000@paprika.michvhf.com>
Date: Mon, 13 Sep 1999 10:43:31 +0930 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: Vince Vielhaber <vev@michvhf.com>
Subject: Re: X mailers (was Re: ANNOUNCE: Linux ABI/SDK standards for Ope
Cc: hackers@FreeBSD.ORG, Lutz Albers <lutz@muc.de>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This message is in MIME format
--_=XFMail.1.3.p0.FreeBSD:990913104331:7396=_
Content-Type: text/plain; charset=us-ascii


On 10-Sep-99 Vince Vielhaber wrote:
> > It claims to do IMAP4, but it just fetches all messages from the server
> > (and by default deleting it from the server). There are very few good IMAP4
> > clients out there :-(
>  
>  xfmail?  Doesn't do that here and I use it daily for all of my internal
>  stuff.

No.. I meant that XFMail worked properly, but Pine didn't.
 
---
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

--_=XFMail.1.3.p0.FreeBSD:990913104331:7396=_
Content-Type: application/pgp-signature

-----BEGIN PGP MESSAGE-----
Version: 2.6.3ia

iQCVAwUBN9xPu1bYW/HEoF9pAQFKZQQAuaZc9ShTvd1J8wulNid6c0aztBLnVqnh
CJdT1WorFwd07v8vgDpveaJFRDVRq5Qdg+uyexmXny71aeVXcw/4jMeNF3l6Qs2H
5WhupcG08MqpILwuZtGiDcgT4uDY5n4qd5RO687dw4BFCKCy/aA879LoL/IADULa
3EC/JI6MS14=
=crc8
-----END PGP MESSAGE-----

--_=XFMail.1.3.p0.FreeBSD:990913104331:7396=_--
End of MIME message


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 18:26:57 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dt014nb6.san.rr.com (dt014nb6.san.rr.com [24.30.129.182])
	by hub.freebsd.org (Postfix) with ESMTP id 1BCCC14D84
	for <hackers@freebsd.org>; Sun, 12 Sep 1999 18:26:54 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from gorean.org (master [10.0.0.2])
	by dt014nb6.san.rr.com (8.9.3/8.8.8) with ESMTP id SAA08264;
	Sun, 12 Sep 1999 18:26:43 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Message-ID: <37DC52D3.D69781D3@gorean.org>
Date: Sun, 12 Sep 1999 18:26:43 -0700
From: Doug <Doug@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0912 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, hackers@freebsd.org
Subject: Re: How to prevent motd including os info
References: <199909121904.MAA31397@gndrsh.dnsmgr.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Rodney W. Grimes" wrote:
> 
> > [moving to -hackers]
> [I'm going to loose the rest of this thread since I am not on hackers :-(]

	Shame on you. :)

> > "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> writes:

> Actually I would like _all_ the output from /etc/rc* to be avaliable
> after boot. 

	One of the things discussed on -hackers recently is my rc* (et al) cleanup
effort. You can see the results at http://gorean.org/rcfiles/. If I can get
the current set of patches committed the next step in my proposal is to
change as many of the 'echo' statements as humanly possible to use 'logger'
instead. This is somewhat controversial because it will (for some items)
require moving 'logger' to /bin, but I think it's worth it. 

> This would be a big win for remote admining and trying
> to figure out what went wrong during the last boot without having to
> drive down and hook up a console of some form.  I know we could hang
> serial consoles on all of them, but why spend money on hardware when
> the problem can be solved with software :-).

	I agree, both that it would be a huge benefit for remote admins (I'm one
too) and that there are some problems that a serial console doesn't solve
where having a hard copy is your best bet (such as jr. asst. cow orker
rebooted a machine he should not have, and now it's borked and no one knows
why). 

> >  fsck_output="$(/sbin/fsck -p)"
> >  /sbin/mount -at nonfs
> >  echo "${fsck_output}" >/var/run/fsck.boot
> >
> > but then you wouldn't be able to see the output while it runs. The
> > only solution I can think of is the following:
> >
> >  fsck_output="$(/sbin/fsck -p | /bin/tee /dev/console)"
> >  /sbin/mount -at nonfs
> >  echo "${fsck_output}" >/var/run/fsck.boot
> >
> > but I don't expect people to be happy about moving tee(1) from
> > /usr/bin to /bin.

	Another possible solution to this would be giving fsck a flag to copy it's
output to a file, STDOUT, or what have you. Since the rest of the cases
could be handled with 'logger' and/or redirction we wouldn't have to bring
'tee' into /bin. 

Doug


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 19:17:23 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4])
	by hub.freebsd.org (Postfix) with ESMTP id 82A8814C7F
	for <hackers@freebsd.org>; Sun, 12 Sep 1999 19:17:18 -0700 (PDT)
	(envelope-from freebsd@gndrsh.dnsmgr.net)
Received: (from freebsd@localhost)
	by gndrsh.dnsmgr.net (8.9.3/8.9.3) id TAA31971;
	Sun, 12 Sep 1999 19:17:06 -0700 (PDT)
	(envelope-from freebsd)
From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Message-Id: <199909130217.TAA31971@gndrsh.dnsmgr.net>
Subject: Re: How to prevent motd including os info
In-Reply-To: <37DC52D3.D69781D3@gorean.org> from Doug at "Sep 12, 1999 06:26:43 pm"
To: Doug@gorean.org (Doug)
Date: Sun, 12 Sep 1999 19:17:05 -0700 (PDT)
Cc: des@flood.ping.uio.no (Dag-Erling Smorgrav), hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> "Rodney W. Grimes" wrote:
> > 
> > > [moving to -hackers]
> > [I'm going to loose the rest of this thread since I am not on hackers :-(]
> 
> 	Shame on you. :)

The volume of mail became too high for my time a long while ago.  :-(

> > > "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> writes:
> 
> > Actually I would like _all_ the output from /etc/rc* to be avaliable
> > after boot. 
> 
> 	One of the things discussed on -hackers recently is my rc* (et al) cleanup
> effort. You can see the results at http://gorean.org/rcfiles/. If I can get
> the current set of patches committed the next step in my proposal is to
> change as many of the 'echo' statements as humanly possible to use 'logger'
> instead. This is somewhat controversial because it will (for some items)
> require moving 'logger' to /bin, but I think it's worth it. 

I don't like that idea, don't get me wrong, it's not the moving of logger
to /bin that bothers me, it just seems like this is using the splitting
mall for what a ballpean hammer could do.

It dawned on me what can be done.  Look, we get all the kernel printf's
from the dmesg output saved in a buffer and pull that out later with
syslog, looks like we could just slip a pipe fitting into /dev/console
that copies all it's output into the mesgbuf as well, until we smack it
wth the ballpean and tell it to stop doing that (Either getty lanching the
login: on ttyv0 could cause this, or something at the end of /etc/rc).

What do you think of that idea?  I think this is what HPUX does, as I do
know I can get the complete console output from a boot on it.

> 
> > This would be a big win for remote admining and trying
> > to figure out what went wrong during the last boot without having to
> > drive down and hook up a console of some form.  I know we could hang
> > serial consoles on all of them, but why spend money on hardware when
> > the problem can be solved with software :-).
> 
> 	I agree, both that it would be a huge benefit for remote admins (I'm one
> too) and that there are some problems that a serial console doesn't solve
> where having a hard copy is your best bet (such as jr. asst. cow orker
> rebooted a machine he should not have, and now it's borked and no one knows
> why). 

Been there, fixed that, and Jr's now missing his left pointer finger
so he only types ``eoo'' when he tries a reboot :-) :-)

> 
> > >  fsck_output="$(/sbin/fsck -p)"
> > >  /sbin/mount -at nonfs
> > >  echo "${fsck_output}" >/var/run/fsck.boot
> > >
> > > but then you wouldn't be able to see the output while it runs. The
> > > only solution I can think of is the following:
> > >
> > >  fsck_output="$(/sbin/fsck -p | /bin/tee /dev/console)"
> > >  /sbin/mount -at nonfs
> > >  echo "${fsck_output}" >/var/run/fsck.boot
> > >
> > > but I don't expect people to be happy about moving tee(1) from
> > > /usr/bin to /bin.
> 
> 	Another possible solution to this would be giving fsck a flag to
> copy it's
> output to a file, STDOUT, or what have you. Since the rest of the cases
> could be handled with 'logger' and/or redirction we wouldn't have to bring
> 'tee' into /bin. 

Adding a flag to fsck to duplicate it's output is even worse than bringing
tee(1) to bin, it's putting tee(1) inside fsck(8) :-(.

-- 
Rod Grimes - KD7CAX - (RWG25)                    rgrimes@gndrsh.dnsmgr.net


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 20: 9: 4 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7])
	by hub.freebsd.org (Postfix) with ESMTP id 4ADFF154E9
	for <freebsd-hackers@FreeBSD.ORG>; Sun, 12 Sep 1999 20:09:02 -0700 (PDT)
	(envelope-from drosih@rpi.edu)
Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47])
	by mail1.its.rpi.edu (8.9.3/8.9.3) with ESMTP id XAA17914;
	Sun, 12 Sep 1999 23:08:52 -0400
Mime-Version: 1.0
X-Sender: drosih@mail.rpi.edu
Message-Id: <v04210103b40219bda4ae@[128.113.24.47]>
In-Reply-To: <19990910104243.A1612@home.com>
References: <19990910104243.A1612@home.com>
Date: Sun, 12 Sep 1999 23:09:31 -0400
To: Sanjay Waghray <sw@home.com>, freebsd-hackers@FreeBSD.ORG
From: Garance A Drosihn <drosih@rpi.edu>
Subject: Re: Wall Street Journal on Open source OS (9/10/99)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 10:42 AM -0700 9/10/99, Sanjay Waghray wrote:
>Attached is an article from the Wall Street Journal Online Edition.
>
>-------------------------------------------------------------------
>
>September 10, 1999
>
>               Beyond Linux, Free Systems
>               Do Their Bit to Build Web
>
>               By LEE GOMES
>               Staff Reporter of THE WALL STREET JOURNAL

Unless you got the "express prior written consent of Dow Jones",
as stated in the "Terms of Use" of their web site, it would be
much better to point people at:
  - - - -
There's also a link to the online version at
http://freebsd.tesserae.com/
  - - - -
than to copy the entire article and mail it to everyone on this
mailing list.


---
Garance Alistair Drosehn           =   gad@eclipse.acs.rpi.edu
Senior Systems Programmer          or  drosih@rpi.edu
Rensselaer Polytechnic Institute


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 20:21:35 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 92774154E9; Sun, 12 Sep 1999 20:21:21 -0700 (PDT)
	(envelope-from bmilekic@dsuper.net)
Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1])
	by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id XAA30870;
	Sun, 12 Sep 1999 23:19:14 -0400 (EDT)
Date: Sun, 12 Sep 1999 23:19:13 -0400 (EDT)
From: Bosko Milekic <bmilekic@dsuper.net>
To: Stas Kisel <stas@sonet.crimea.ua>
Cc: avalon@coombs.anu.edu.au, freebsd-hackers@FreeBSD.ORG,
	freebsd-security@FreeBSD.ORG
Subject: Re: mbuf shortage situations (followup)
In-Reply-To: <199909091447.SAA24055@sonet.crimea.ua>
Message-ID: <Pine.OSF.4.05.9909122304470.18795-300000@oracle.dsuper.net>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-750191660-937192753=:18795"
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-750191660-937192753=:18795
Content-Type: TEXT/PLAIN; charset=US-ASCII


Hello (again),

On Thu, 9 Sep 1999, Stas Kisel wrote:

!>> From avalon@cheops.anu.edu.au Thu Sep  9 16:17:27 1999
!>
!>> > Probably it is not self-evident why we HAVE to drop this connection.
!>>
!>> So what if someone manages to crash a program due to a DOS attack ?
!>> An easy one that comes to mind is syslogd.  It's often stuck in disk-wait
!>> and can easily be targetted with a large number of packets.
!>
!>1. If ever syslog used (or will use) TCP, it should drop the connection
!>which is logging data too quickly.
!>OS shouldn't kill process, only drop connection. So no crash.
!>More examples?
!>
!>2. udp_drain() may either drop all packets or intellectually select
!>"offending" socket and try to avoid deletion of "right" packets and
!>simplifying spoofing. RFC allows 1st way, but 2-nd can improve OS.
!>
!>3. Another idea. Apart from the *_drain() method. Probably I ever will
!>try to implement it somedays (quite low probability, though).
!>Set TCP window in a packets according to really available kernel
!>memory. Available memory should be distributed non-uniformly
!>between maximum number of sockets. So 1-st socket has window=
!>=64k-still_not_read_data, and 1024-th has window=MIN_WINDOW-
!>-still_not_read_data. 
!>MIN_WINDOW should be determined for max efficiency. About 2k.
!>Distribution can not be linear - it isapproximately like min(NORM*1/x,64k).
!>Exactly it can be determined via functional equation. Something like
!>\integral_0^maxsockets{dist(x)dx}=kernel_memory and several
!>conditions. (sorry for my poor TeX).
!>
!>In a case of attack new sockets will be created with a very small
!>window - about 2k.
!>
!>Please blame me as much as possible - probably I have missed some significant
!>detail.
!>Probably all this math suxx and the best is a "stair" function -
!>somebody already works on lowering TCP window, if I didn't mistaken.
!>
!>
!>--
!>Stas Kisel. UNIX, security, C, TCP/IP, Web. UNIX - the best adventure game
!>http://www.tekmetrics.com/transcript.shtml?pid=20053 http://www.crimea.edu
!>+380(652)510222,230238 ; stas@crimea.edu stas@sonet.crimea.ua ; 2:460/54.4
!>

	These are all interesting ideas.

	However, when I initially posted regarding this, I was
disappointed in seeing that we simply handle MGET()s, MGETHDR()s, and
MCLALLOC()s by storing a null _even_ if we are M_WAIT. What basically
ended up happening (and, the last time I checked, it's like this even in
--CURRENT), is m_retry() -- or m_retryhdr() (this is in the case of no
mbufs beings available) would simply panic().
	I have produced patches (see attached -- they are seperated into
two different patches, mbuf.patch which patches kern/uipc_mbuf.c and
mbuf2.patch which patches sys/mbuf.h) that will basically tsleep() in the
case of an M_WAIT and mbuf or mbuf cluster shortage. I wanted something
that would make sure that we will get a non-NULL result when we called
with M_WAIT. Obviously, this isn't the definite solution to the DoS
problem that seemed to have become the main idea of discussion in this
thread.
	However, I've kept that in mind, and I am now starting work (when
time permits) on some code which will enable us to warn the network
protocol module code that we're out of mbufs (or mbuf clusters) when the
situation occurs. This way, if we can't get anything even with m_reclaim
(which would be called from m_retry if we are M_WAIT), we could have the
protocols figure out what to drop.
	I'm also aware of the possiblity of some people not liking the
fact that we tsleep() forever (e.g. tsleep(x,x,x,0)). Thus, I am open to
modifying the diffs to add a counter and have the tsleep expire every once
in a while so that finally, when the counter would expire, we would return
a deffinate null _even_ if we are M_WAIT, but this can only be implemented
if we make sure that ALL the MGET and company callers check for this
(which would be annoying to do).


Cheers,
Bosko Milekic.


--0-750191660-937192753=:18795
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="mbuf.patch"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.OSF.4.05.9909122319130.18795@oracle.dsuper.net>
Content-Description: 
Content-Disposition: attachment; filename="mbuf.patch"

LS0tIC91c3Ivc3JjL3N5cy9rZXJuLm9sZC91aXBjX21idWYuYwlXZWQgU2Vw
ICA4IDIwOjQ1OjUwIDE5OTkNCisrKyAvdXNyL3NyYy9zeXMva2Vybi91aXBj
X21idWYuYwlTdW4gU2VwIDEyIDIyOjQ0OjIzIDE5OTkNCkBAIC02MCw2ICs2
MCw4IEBADQogaW50CW1heF9oZHI7DQogaW50CW1heF9kYXRhbGVuOw0KIA0K
K3N0YXRpYyBpbnQgbV9tYmFsbG9jX3dpZCA9IDAsIG1fY2xhbGxvY193aWQg
PSAwOw0KKw0KIFNZU0NUTF9JTlQoX2tlcm5faXBjLCBLSVBDX01BWF9MSU5L
SERSLCBtYXhfbGlua2hkciwgQ1RMRkxBR19SVywNCiAJICAgJm1heF9saW5r
aGRyLCAwLCAiIik7DQogU1lTQ1RMX0lOVChfa2Vybl9pcGMsIEtJUENfTUFY
X1BST1RPSERSLCBtYXhfcHJvdG9oZHIsIENUTEZMQUdfUlcsDQpAQCAtMTUz
LDYgKzE1NSw1NyBAQA0KIAlyZXR1cm4gKDEpOw0KIH0NCiANCisvKg0KKyAq
IEZ1bmN0aW9uIHVzZWQgZm9yIHdhaXRpbmcgb24gc29tZSBtYnVmIHRvIGJl
IGZyZWVkIGFuZCwgdXBvbiB3YWtldXAsDQorICogdG8gZ28gZ2V0IHRoYXQg
bWJ1ZiBhbmQgdXNlIGl0Lg0KKyAqLw0KK3N0cnVjdCBtYnVmICoNCittX21i
YWxsb2Nfd2FpdChjYWxsZXIsIHR5cGUpDQorCWludCBjYWxsZXI7DQorCWlu
dCB0eXBlOw0KK3sNCisJc3RydWN0IG1idWYgKnA7DQorDQorUmV0cnlGZXRj
aDoNCisJLyogU2xlZXAgaGVyZSB1bnRpbCBzb21ldGhpbmcncyBhdmFpbGFi
bGUuICovDQorCW1fbWJhbGxvY193aWQrKzsNCisJdHNsZWVwKCZtX21iYWxs
b2Nfd2lkLCBQVk0sICJtYmFsbGMiLCAwKTsNCisJDQorCS8qDQorCSAqIE5v
dyB0aGF0IHdlICh0aGluaykgdGhhdCB3ZSd2ZSBnb3Qgc29tZXRoaW5nLCB3
ZSB3aWxsIHJlZG8gYW4NCisJICogTUdFVCwgYnV0IGF2b2lkIGdldHRpbmcg
aW50byBhbm90aGVyIGluc3RhbmNlIG9mIG1fbWJhbGxvY193YWl0KCkNCisJ
ICogV2UgZG8gdGhpcyBieSBkZWZpbmluZyB0aGlzIGZ1bmN0aW9uIGFzIG51
bGwuDQorCSAqLw0KKyNkZWZpbmUgbV9tYmFsbG9jX3dhaXQoY2FsbGVyLHR5
cGUpIChzdHJ1Y3QgbWJ1ZiAqKTAgDQorCWlmIChjYWxsZXIgPT0gTUdFVF9D
KSB7DQorCQlNR0VUKHAsTV9XQUlULHR5cGUpOw0KKwl9IGVsc2Ugew0KKwkJ
TUdFVEhEUihwLE1fV0FJVCx0eXBlKTsNCisJfQ0KKyN1bmRlZiBtX21iYWxs
b2Nfd2FpdA0KKyANCisJLyoNCisJICogSWYgd2UgZmFpbCB5ZXQgYWdhaW4s
IGdvIGJhY2sgdG8gc2xlZXBpbmcuDQorCSAqIFhYWCBQZXJoYXBzIHdlIHNo
b3VsZCBpbXBsZW1lbnQgYSBsaW1pdCBzb21ld2hlcmUgaGVyZS4gDQorCSAq
Lw0KKwlpZiAocCA9PSBOVUxMKQ0KKwkJZ290byBSZXRyeUZldGNoOw0KKw0K
KwlyZXR1cm4gKHApOw0KK30NCisNCisvKg0KKyAqIEZ1bmN0aW9uIHVzZWQg
dG8gd2FrZXVwIHNsZWVwZXJzIHdhaXRpbmcgZm9yIG1idWZzLi4uDQorICov
DQordm9pZA0KK21fbWJhbGxvY193YWtldXAodm9pZCkNCit7DQorCWlmICht
X21iYWxsb2Nfd2lkKSB7DQorCQltX21iYWxsb2Nfd2lkID0gMDsNCisJCXdh
a2V1cCgmbV9tYmFsbG9jX3dpZCk7DQorCX0NCit9DQorDQogI2lmIE1DTEJZ
VEVTID4gUEFHRV9TSVpFDQogc3RhdGljIGludCBpX3dhbnRfbXlfbWNsOw0K
IA0KQEAgLTI0Miw2ICsyOTUsNTMgQEANCiB9DQogDQogLyoNCisgKiBUaGlz
IGZ1bmN0aW9uIHdpbGwgYmUgdXNlZCB0byBzbGVlcCBhbmQgd2FpdCB1bnRp
bCB3ZSBoYXZlIGEgZnJlZQ0KKyAqIG1idWYgY2x1c3Rlci4gVGhpcyBpcyBm
b3IgY2FsbGVycyB3aXRoIE1fV0FJVCB3aG8nZCBsaWtlIHRvIGF2b2lkDQor
ICogcmV0dXJuaW5nIE5VTEwgYW5kIHRha2UgdGhlIGhlYXQsIHdhaXRpbmcg
KHdoaWNoIGlzIGxvZ2ljYWxseSB3aGF0DQorICogc2hvdWxkIGhhcHBlbiBh
bnl3YXkgd2l0aCBhbiBNX1dBSVQpLg0KKyAqLw0KK2NhZGRyX3QNCittX2Ns
YWxsb2Nfd2FpdCh2b2lkKQ0KK3sNCisJY2FkZHJfdCBwOw0KKw0KK1JldHJ5
Q2x1c3Q6DQorCS8qIFNsZWVwIGhlcmUgdW50aWwgc29tZXRoaW5nJ3MgYXZh
aWxhYmxlLiAqLw0KKwltX2NsYWxsb2Nfd2lkKys7DQorCXRzbGVlcCgmbV9j
bGFsbG9jX3dpZCwgUFZNLCAibWNsYWxjIiwgMCk7DQorDQorCS8qDQorCSAq
IE5vdyB0aGF0IHdlICh0aGluaykgdGhhdCB3ZSd2ZSBnb3Qgc29tZXRoaW5n
LCB3ZSB3aWxsIHJlZG8gYW5kDQorCSAqIE1HRVQsIGJ1dCBhdm9pZCBnZXR0
aW5nIGludG8gYW5vdGhlciBpbnN0YW5jZSBvZiBtX2NsYWxsb2Nfd2FpdCgp
DQorCSAqIFdlIGRvIHRoaXMgYnkgZGVmaW5pbmcgdGhpcyBmdW5jdGlvbiBh
cyBudWxsLg0KKwkgKi8NCisjZGVmaW5lIG1fY2xhbGxvY193YWl0KCkgKGNh
ZGRyX3QpMA0KKwlNQ0xBTExPQyhwLE1fV0FJVCk7DQorI3VuZGVmIG1fY2xh
bGxvY193YWl0DQorDQorCS8qDQorCSAqIElmIHdlIGZhaWwgeWV0IGFnYWlu
LCBnbyBiYWNrIHRvIHNsZWVwaW5nLg0KKwkgKiBYWFggUGVyaGFwcyB3ZSBz
aG91bGQgaW1wbGVtZW50IGEgbGltaXQgc29tZXdoZXJlIGhlcmUuDQorCSAq
Lw0KKwlpZiAocCA9PSBOVUxMKQ0KKwkJZ290byBSZXRyeUNsdXN0Ow0KKw0K
KwlyZXR1cm4gKHApOw0KK30NCisNCisvKg0KKyAqIEZ1bmN0aW9uIHVzZWQg
dG8gd2FrZXVwIHNsZWVwZXJzIHdhaXRpbmcgZm9yIG1idWYgY2x1c3RlcnMu
Li4NCisgKi8NCit2b2lkDQorbV9jbGFsbG9jX3dha2V1cCh2b2lkKQ0KK3sN
CisJaWYgKG1fY2xhbGxvY193aWQpIHsNCisJCW1fY2xhbGxvY193aWQgPSAw
Ow0KKwkJd2FrZXVwKCZtX2NsYWxsb2Nfd2lkKTsNCisJfQ0KK30NCisNCisv
Kg0KICAqIFdoZW4gTUdFVCBmYWlscywgYXNrIHByb3RvY29scyB0byBmcmVl
IHNwYWNlIHdoZW4gc2hvcnQgb2YgbWVtb3J5LA0KICAqIHRoZW4gcmUtYXR0
ZW1wdCB0byBhbGxvY2F0ZSBhbiBtYnVmLg0KICAqLw0KQEAgLTI2MSwxMiAr
MzYxLDkgQEANCiAjdW5kZWYgbV9yZXRyeQ0KIAlpZiAobSAhPSBOVUxMKSB7
DQogCQltYnN0YXQubV93YWl0Kys7DQotCX0gZWxzZSB7DQotCQlpZiAoaSA9
PSBNX0RPTlRXQUlUKQ0KLQkJCW1ic3RhdC5tX2Ryb3BzKys7DQotCQllbHNl
DQotCQkJcGFuaWMoIk91dCBvZiBtYnVmIGNsdXN0ZXJzIik7DQotCX0NCisJ
fSBlbHNlIA0KKwkJbWJzdGF0Lm1fZHJvcHMrKzsNCisNCiAJcmV0dXJuICht
KTsNCiB9DQogDQpAQCAtMjg5LDEyICszODYsOSBAQA0KICN1bmRlZiBtX3Jl
dHJ5aGRyDQogCWlmIChtICE9IE5VTEwpIHsNCiAJCW1ic3RhdC5tX3dhaXQr
KzsNCi0JfSBlbHNlIHsNCi0JCWlmIChpID09IE1fRE9OVFdBSVQpDQotCQkJ
bWJzdGF0Lm1fZHJvcHMrKzsNCi0JCWVsc2UNCi0JCQlwYW5pYygiT3V0IG9m
IG1idWYgY2x1c3RlcnMiKTsNCi0JfQ0KKwl9IGVsc2UgDQorCQltYnN0YXQu
bV9kcm9wcysrOw0KKw0KIAlyZXR1cm4gKG0pOw0KIH0NCiANCg==
--0-750191660-937192753=:18795
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="mbuf2.patch"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.OSF.4.05.9909122319131.18795@oracle.dsuper.net>
Content-Description: 
Content-Disposition: attachment; filename="mbuf2.patch"

LS0tIC91c3Ivc3JjL3N5cy9zeXMub2xkL21idWYuaAkJU2F0IFNlcCAxMSAx
OToxMDo0NCAxOTk5DQorKysgL3Vzci9zcmMvc3lzL3N5cy9tYnVmLmgJCVN1
biBTZXAgMTIgMjI6NDQ6NDQgMTk5OQ0KQEAgLTE1Myw2ICsxNTMsMTMgQEAN
CiAjZGVmaW5lCU1fRE9OVFdBSVQJMQ0KICNkZWZpbmUJTV9XQUlUCQkwDQog
DQorLyogDQorICogRmxhZ3MgdG8gcGFzcyB0byB0aGUgKl93YWl0IGZ1bmN0
aW9ucyAod2hlbiB3ZSBoYXZlIHRvIHdhaXQgZm9yIGFuDQorICogbWJ1ZiB0
byBiZSBmcmVlZCkuDQorICovDQorI2RlZmluZSBNR0VUX0MJCTENCisjZGVm
aW5lIE1HRVRIRFJfQwkyDQorDQogLyogRnJlZWxpc3RzOg0KICAqDQogICog
Tm9ybWFsIG1idWYgY2x1c3RlcnMgYXJlIG5vcm1hbGx5IHRyZWF0ZWQgYXMg
Y2hhcmFjdGVyIGFycmF5cw0KQEAgLTIwMyw3ICsyMTAsOCBAQA0KIAkJc3Bs
eChfbXMpOyBcDQogCX0gZWxzZSB7IFwNCiAJCXNwbHgoX21zKTsgXA0KLQkJ
KG0pID0gbV9yZXRyeSgoaG93KSwgKHR5cGUpKTsgXA0KKwkJaWYgKCgobSk9
bV9yZXRyeSgoaG93KSwgKHR5cGUpKSk9PU5VTEwgJiYgKGhvdyk9PU1fV0FJ
VCkgXA0KKwkJCShtKSA9IG1fbWJhbGxvY193YWl0KE1HRVRfQywodHlwZSkp
OyBcDQogCX0gXA0KIH0NCiANCkBAIC0yMjMsNyArMjMxLDggQEANCiAJCXNw
bHgoX21zKTsgXA0KIAl9IGVsc2UgeyBcDQogCQlzcGx4KF9tcyk7IFwNCi0J
CShtKSA9IG1fcmV0cnloZHIoKGhvdyksICh0eXBlKSk7IFwNCisJCWlmICgo
KG0pPW1fcmV0cnloZHIoKGhvdyksKHR5cGUpKSk9PU5VTEwgJiYgKGhvdyk9
PU1fV0FJVCkgXA0KKwkJCShtKSA9IG1fbWJhbGxvY193YWl0KE1HRVRIRFJf
QywodHlwZSkpOyBcDQogCX0gXA0KIH0NCiANCkBAIC0yMzUsMTYgKzI0NCwy
MCBAQA0KICAqIE1DTEZSRUUgcmVsZWFzZXMgYSByZWZlcmVuY2UgdG8gYSBj
bHVzdGVyIGFsbG9jYXRlZCBieSBNQ0xBTExPQywNCiAgKiBmcmVlaW5nIHRo
ZSBjbHVzdGVyIGlmIHRoZSByZWZlcmVuY2UgY291bnQgaGFzIHJlYWNoZWQg
MC4NCiAgKi8NCi0jZGVmaW5lCU1DTEFMTE9DKHAsIGhvdykgXA0KLQlNQlVG
TE9DSyggXA0KLQkgIGlmIChtY2xmcmVlID09IDApIFwNCisjZGVmaW5lCU1D
TEFMTE9DKHAsIGhvdykgeyBcDQorCWludCBfbXMgPSBzcGxpbXAoKTsgXA0K
KwlpZiAobWNsZnJlZSA9PSAwKSBcDQogCQkodm9pZCltX2NsYWxsb2MoMSwg
KGhvdykpOyBcDQotCSAgaWYgKCgocCkgPSAoY2FkZHJfdCltY2xmcmVlKSAh
PSAwKSB7IFwNCisJaWYgKCgocCkgPSAoY2FkZHJfdCltY2xmcmVlKSAhPSAw
KSB7IFwNCiAJCSsrbWNscmVmY250W210b2NsKHApXTsgXA0KIAkJbWJzdGF0
Lm1fY2xmcmVlLS07IFwNCiAJCW1jbGZyZWUgPSAoKHVuaW9uIG1jbHVzdGVy
ICopKHApKS0+bWNsX25leHQ7IFwNCi0JICB9IFwNCi0JKQ0KKwkJc3BseChf
bXMpOyBcDQorIAl9IGVsc2UgaWYgKChob3cpID09IE1fV0FJVCkgeyBcDQor
CQlzcGx4KF9tcyk7IFwNCisJCShwKSA9IG1fY2xhbGxvY193YWl0KCk7IFwN
CisJfSBcDQorfQ0KIA0KICNkZWZpbmUJTUNMR0VUKG0sIGhvdykgXA0KIAl7
IE1DTEFMTE9DKChtKS0+bV9leHQuZXh0X2J1ZiwgKGhvdykpOyBcDQpAQCAt
MjYzLDYgKzI3Niw3IEBADQogCQkoKHVuaW9uIG1jbHVzdGVyICopKHApKS0+
bWNsX25leHQgPSBtY2xmcmVlOyBcDQogCQltY2xmcmVlID0gKHVuaW9uIG1j
bHVzdGVyICopKHApOyBcDQogCQltYnN0YXQubV9jbGZyZWUrKzsgXA0KKwkJ
KHZvaWQpbV9jbGFsbG9jX3dha2V1cCgpOyBcDQogCSAgfSBcDQogCSkNCiAN
CkBAIC0yODQsNiArMjk4LDcgQEANCiAJCQkJKCh1bmlvbiBtY2x1c3RlciAq
KShwKSktPm1jbF9uZXh0ID0gbWNsZnJlZTsgXA0KIAkJCQltY2xmcmVlID0g
KHVuaW9uIG1jbHVzdGVyICopKHApOyBcDQogCQkJCW1ic3RhdC5tX2NsZnJl
ZSsrOyBcDQorCQkJCSh2b2lkKW1fY2xhbGxvY193YWtldXAoKTsgXA0KIAkJ
CX0gXA0KIAkJfSBcDQogCSAgfSBcDQpAQCAtMjkyLDYgKzMwNyw3IEBADQog
CSAgbWJzdGF0Lm1fbXR5cGVzW01UX0ZSRUVdKys7IFwNCiAJICAobSktPm1f
bmV4dCA9IG1tYmZyZWU7IFwNCiAJICBtbWJmcmVlID0gKG0pOyBcDQorCSAg
KHZvaWQpbV9tYmFsbG9jX3dha2V1cCgpOyBcDQogCSkNCiANCiAvKg0KQEAg
LTQwOCwxNiArNDI0LDIwIEBADQogc3RydWN0CW1idWYgKm1fZ2V0aGRyIF9f
UCgoaW50LCBpbnQpKTsNCiBzdHJ1Y3QJbWJ1ZiAqbV9wcmVwZW5kIF9fUCgo
c3RydWN0IG1idWYgKixpbnQsaW50KSk7DQogc3RydWN0CW1idWYgKm1fcHVs
bHVwIF9fUCgoc3RydWN0IG1idWYgKiwgaW50KSk7DQorc3RydWN0CW1idWYg
Km1fbWJhbGxvY193YWl0IF9fUCgoaW50LGludCkpOw0KIHN0cnVjdAltYnVm
ICptX3JldHJ5IF9fUCgoaW50LCBpbnQpKTsNCiBzdHJ1Y3QJbWJ1ZiAqbV9y
ZXRyeWhkciBfX1AoKGludCwgaW50KSk7DQogc3RydWN0CW1idWYgKm1fc3Bs
aXQgX19QKChzdHJ1Y3QgbWJ1ZiAqLGludCxpbnQpKTsNCiB2b2lkCW1fYWRq
IF9fUCgoc3RydWN0IG1idWYgKiwgaW50KSk7DQogdm9pZAltX2NhdCBfX1Ao
KHN0cnVjdCBtYnVmICosc3RydWN0IG1idWYgKikpOw0KK3ZvaWQJbV9tYmFs
bG9jX3dha2V1cCBfX1AoKHZvaWQpKTsNCit2b2lkCW1fY2xhbGxvY193YWtl
dXAgX19QKCh2b2lkKSk7DQogaW50CW1fbWJhbGxvYyBfX1AoKGludCwgaW50
KSk7DQogaW50CW1fY2xhbGxvYyBfX1AoKGludCwgaW50KSk7DQogdm9pZAlt
X2NvcHliYWNrIF9fUCgoc3RydWN0IG1idWYgKiwgaW50LCBpbnQsIGNhZGRy
X3QpKTsNCiB2b2lkCW1fY29weWRhdGEgX19QKChzdHJ1Y3QgbWJ1ZiAqLGlu
dCxpbnQsY2FkZHJfdCkpOw0KIHZvaWQJbV9mcmVlbSBfX1AoKHN0cnVjdCBt
YnVmICopKTsNCitjYWRkcl90CW1fY2xhbGxvY193YWl0IF9fUCgodm9pZCkp
Ow0KICNlbmRpZiAvKiBLRVJORUwgKi8NCiANCiAjZW5kaWYgLyogIV9TWVNf
TUJVRl9IXyAqLw0K
--0-750191660-937192753=:18795--


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sun Sep 12 20:54: 7 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dt014nb6.san.rr.com (dt014nb6.san.rr.com [24.30.129.182])
	by hub.freebsd.org (Postfix) with ESMTP id B08C814D91
	for <hackers@freebsd.org>; Sun, 12 Sep 1999 20:54:05 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from gorean.org (master [10.0.0.2])
	by dt014nb6.san.rr.com (8.9.3/8.8.8) with ESMTP id UAA09362;
	Sun, 12 Sep 1999 20:53:59 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Message-ID: <37DC7556.82A77322@gorean.org>
Date: Sun, 12 Sep 1999 20:53:58 -0700
From: Doug <Doug@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0912 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, hackers@freebsd.org
Subject: Re: How to prevent motd including os info
References: <199909130217.TAA31971@gndrsh.dnsmgr.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Rodney W. Grimes" wrote:

> It dawned on me what can be done.  Look, we get all the kernel printf's
> from the dmesg output saved in a buffer and pull that out later with
> syslog, looks like we could just slip a pipe fitting into /dev/console
> that copies all it's output into the mesgbuf as well, until we smack it
> wth the ballpean and tell it to stop doing that (Either getty lanching the
> login: on ttyv0 could cause this, or something at the end of /etc/rc).
> 
> What do you think of that idea? 

	I think that's a fine idea, and it's a lot cleaner than mine for a number
of reasons. Completely beyond me to code, but very nice from the design
standpoint. 

Doug


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  0:14:59 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60])
	by hub.freebsd.org (Postfix) with ESMTP id D8B931500B
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 00:14:56 -0700 (PDT)
	(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.196.52]) by smtp02.wxs.nl
          (Netscape Messaging Server 3.61)  with ESMTP id AAB70A5;
          Mon, 13 Sep 1999 09:14:55 +0200
Received: (from asmodai@localhost)
	by daemon.ninth-circle.org (8.9.3/8.9.3) id JAA89531;
	Mon, 13 Sep 1999 09:07:39 +0200 (CEST)
	(envelope-from asmodai)
Date: Mon, 13 Sep 1999 09:07:38 +0200
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: "James E . Housley" <jim@thehousleys.net>
Cc: freebsd-hackers@FreeBSD.ORG, Nate Williams <nate@mt.sri.com>
Subject: Re: A Challenge
Message-ID: <19990913090738.G89309@daemon.ninth-circle.org>
References: <37D87080.4D44E9C4@thehousleys.net> <199909100504.XAA09058@mt.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.7i
In-Reply-To: <199909100504.XAA09058@mt.sri.com>
Organisation: Ninth-Circle Enterprises
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

* Nate Williams (nate@mt.sri.com) [990910 07:14]:
>In any case, if you install a recent version of FreeBSD, I doubt Mr. NT
>is capable of crashing FreeBSD from externally.  Just make sure he
>doesn't have an account on it, since it's much easier to cause Denial Of
>Service attacks if you don't spend alot of time setting up limits and
>such.

Going even further than what Nate said, remove all accounts you don't
need. Give only accounts to those who need to admin the box, other than
that DO NOT give away accounts.

Make sure the security log files sent by email are being sent to the
correct persons.

Remove /usr/src and compile kernels on a secondary host so you are sure
that compiling stuff on the firewall is hard after a compromise.

Use ssh and ditch telnet.

read security(9)

-- 
Jeroen Ruigrok van der Werven/Asmodai                  asmodai(at)wxs.nl
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
Network/Security Specialist        BSD: Technical excellence at its best
If Winter comes, can Spring be far behind?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  0:14:59 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60])
	by hub.freebsd.org (Postfix) with ESMTP id 5858C14FD6
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 00:14:55 -0700 (PDT)
	(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.196.52]) by smtp02.wxs.nl
          (Netscape Messaging Server 3.61)  with ESMTP id AAA70A5;
          Mon, 13 Sep 1999 09:14:54 +0200
Received: (from asmodai@localhost)
	by daemon.ninth-circle.org (8.9.3/8.9.3) id JAA89522;
	Mon, 13 Sep 1999 09:03:18 +0200 (CEST)
	(envelope-from asmodai)
Date: Mon, 13 Sep 1999 09:03:18 +0200
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Gustavo V G C Rios <grios@ddsecurity.com.br>
Cc: hackers@freebsd.org
Subject: Re: submiting source code ?
Message-ID: <19990913090318.F89309@daemon.ninth-circle.org>
References: <37D86506.4247EF3A@ddsecurity.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.7i
In-Reply-To: <37D86506.4247EF3A@ddsecurity.com.br>
Organisation: Ninth-Circle Enterprises
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

* Gustavo V G C Rios (grios@ddsecurity.com.br) [990910 04:14]:
>I use freebsd about +- 12 months ago. I have never did any thing serious
>at kernel level, nor i know anything about kernel desgin.

Start with:

Modern Operating Systems by Andrew S. Tanenbaum
The Design and Implementation of 4.4BSD by Marshall Kirk McKusick et al.
Unix Internals: The New Frontiers

Then you probably need more special in-depth books such as:

TCP/IP Illustrated by (R.I.P.) W. Richard Stevens
Unix Network Programming by W. Richard Stevens
The Unix Programming Environment by Rob Pike and Ritchie Kerninghan
Advanced Programming in the Unix Environment by W. Richard Stevens

>Suppose, i would like to spend time and patience learnig Fbsd internals.
>If, later, i were able to code something to freebsd, and suppose i do,
>what (or better, how) should i do to have my source accepted by the core
>team?

send-pr after you have tested, style(9)'d, documented your code and
tested you patches against a clean checked out source base.

>What about coding style ?

As Chris said, style(9)

>What are the golden rules to have my sources widely accepted by freebsd
>community?

Don't go the Linux way which tends to favor bloat over solid code.
Portability and correctness of code is more important than features.

>PS: This is my first attempt to start touching the kernel, so, don't
>blame, if i wrote something wrong.

That's ok, it's a long way before you actually will start touching the
sources though, it involves a lot of RTFM'ing and UTSL'ing first.

-- 
Jeroen Ruigrok van der Werven/Asmodai                  asmodai(at)wxs.nl
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
Network/Security Specialist        BSD: Technical excellence at its best
Workers of the world, unite!


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  1:23:45 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58])
	by hub.freebsd.org (Postfix) with ESMTP id 70CD514A06
	for <freebsd-hackers@freebsd.org>; Mon, 13 Sep 1999 01:23:42 -0700 (PDT)
	(envelope-from Dom.Mitchell@palmerharvey.co.uk)
Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk
 (Content Technologies SMTPRS 4.0.1) with ESMTP id <B3eac6d3a4742c0d6df@mail.palmerharvey.co.uk>;
 Mon, 13 Sep 1999 09:23:32 +0100
Received: from voodoo.pandhm.co.uk (10.100.35.12 [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id SNZVMND4; Mon, 13 Sep 1999 09:22:25 +0100
Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1)
	id 11QROi-000C1o-00; Mon, 13 Sep 1999 09:23:36 +0100
Date: Mon, 13 Sep 1999 09:23:36 +0100
To: Parag Patel <parag@cgt.com>
Cc: "Matthew N. Dodd" <winter@jurai.net>,
	Daniel O'Connor <darius@dons.net.au>, freebsd-hackers@FreeBSD.ORG
Subject: Re: NetWare client in -current
Message-ID: <19990913092335.A35751@voodoo.pandhm.co.uk>
References: <winter@jurai.net> <24320.936987312@pinhead.parag.codegen.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <24320.936987312@pinhead.parag.codegen.com>
From: Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Sep 10, 1999 at 11:15:12AM -0700, Parag Patel wrote:
> Growing up programming on a KL-10, I still think the correct place for
> line-editing is in the driver.  Hell - it's already doing basic
> erase/kill line editing as it is.  Then you don't have to hack every
> command-line app to get line-editing.

Yeah, but how do you specify completion then?

Unix went here a long time ago and backed out of it.  Have a look at the
paper http://www.cs.princeton.edu/~jlk/kornshell/doc/vhll.ps.gz (linked
from www.kornshell.com) in particular, the history section.
-- 
Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator

"vi has two modes the one in which it beeps and the one in which it doesnt."
	-- Anon.


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  1:44:36 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id 0415C14F78
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 01:44:33 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.3) id KAA16989;
	Mon, 13 Sep 1999 10:44:28 +0200 (CEST)
	(envelope-from des)
To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc: hackers@freebsd.org
Subject: Re: How to prevent motd including os info
References: <199909122230.PAA31675@gndrsh.dnsmgr.net>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 13 Sep 1999 10:44:28 +0200
In-Reply-To: "Rodney W. Grimes"'s message of "Sun, 12 Sep 1999 15:30:38 -0700 (PDT)"
Message-ID: <xzp3dwj19qr.fsf@flood.ping.uio.no>
Lines: 32
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> writes:
> > No. The scrollback may be too short (especially after an fsck of a
> > large filesystem after a crash), and it may even be empty (if you put
> > something like VESA_132x60 in allscreens_flags in rc.conf)
> We can tune the size of the scroll back buffer can't we?

Yes, but we don't want to increase the default size too much.

>                                                           And fsck output
> even after a crash is usually not that long, if it gets long it usually
> has more problems than fsck -p can deal with and stops any way.

You've obviously never fsck'ed a largish soft-updated filesystem after
a power outage.

> Why does switching display mode screw up the scroll back buffer?  That
> sounds broken to me.

Because you have to resize the scrollback to accomodate the new line
width. You're welcome to fix it. I've tried, and decided that it was
far from a SMOP and that it would have to wait until I have more than
a few hours' continuous free time.

> > Doesn't ntpdate log what it does with syslog?
> If you give it the -s option, yes it will syslog it.  But doing that
> to everything in /etc/rc* seems like a pain in the *ss...

Lazy people never achieve much.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  2:10:19 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13])
	by hub.freebsd.org (Postfix) with ESMTP id D34931553D
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 02:09:55 -0700 (PDT)
	(envelope-from kuku@gilberto.physik.RWTH-Aachen.DE)
Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240])
	by nets5.rz.rwth-aachen.de (8.9.1a/8.9.1/7) with ESMTP id LAA20993
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 11:09:54 +0200 (MET DST)
Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2])
	by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id KAA20585
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 10:56:08 +0200 (MET DST)
Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.2/8.6.9) id KAA33966 for hackers@freebsd.org; Mon, 13 Sep 1999 10:56:09 +0200 (CEST)
Date: Mon, 13 Sep 1999 10:56:09 +0200 (CEST)
From: Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>
Message-Id: <199909130856.KAA33966@gil.physik.rwth-aachen.de>
To: hackers@freebsd.org
Subject: de0 strangenesses
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On a 3.0-current of October 1998 I'm having often trouble with de0.
The machine often reboots over night (when either the locate db is built or
some other big job - like mirror - is running). Anyway, after the reboot,
often de0 is dead.

This happend today again. When I came into the office I could not
ping said machine. I sat at the console, logged in. The machine was
perfectly alive, only the de0 interface didn't work at the BNC network.

I did a ifconfig de0 down and exactly with doing that I got a kernel message
from the driver: de0 BNC interface enabled (or something like that).
Doing an ifconfig de0 up right after that the interface continued working
at the BNC port.

Can the driver writer(s) comment whether there have been changes to the driver
WRT that behaviour so I can expect that with either 3.2 or -current
the problem would be gone?

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


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  2:21:36 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from musashi.et.bocholt.fh-ge.de (reserve.et.bocholt.fh-gelsenkirchen.de [193.175.197.95])
	by hub.freebsd.org (Postfix) with ESMTP id 2E8D514A07
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 02:21:28 -0700 (PDT)
	(envelope-from hank@musashi.et.bocholt.fh-ge.de)
Received: from localhost (localhost.et.bocholt.fh-ge.de [127.0.0.1])
	by musashi.et.bocholt.fh-ge.de (8.9.3/8.9.3) with ESMTP id LAA13019;
	Mon, 13 Sep 1999 11:21:02 +0200 (CEST)
	(envelope-from hank@musashi.et.bocholt.fh-ge.de)
Message-Id: <199909130921.LAA13019@musashi.et.bocholt.fh-ge.de>
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
From: Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>
Reply-To: Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>
Cc: Wes Peters <wes@softweyr.com>, hackers@FreeBSD.ORG
Subject: Re: More press 
In-reply-to: Your message of "12 Sep 1999 15:22:55 +0200."
             <xzp671g2rio.fsf@flood.ping.uio.no> 
Date: Mon, 13 Sep 1999 11:21:02 +0200
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


 > Dirk GOUDERS <hank@musashi.et.bocholt.fh-ge.de> writes:
 > > Oh, sorry -- my "browse-url-at-mouse" function made
 > > 
 > > http://www.zdnet.com/zdtv/screensavers/answerstips/story/02c36562c23246242
c00.html
 > > 
 > > of it...
 > 
 > Netscape uses commans to separate parameters to the OpenURL command.
 > Fortunately, the API is open and documented, so there's nothing to
 > stop someone from writing a small command-line util that does the
 > equivalent of "netscape -remote" except faster and better.

Well, having read all of your remarks, I noticed, that emacs' lisp
code "browse-url.el" causes the generation of 

http://www.zdnet.com/zdtv/screensavers/answerstips/story/02c36562c23246242
c00.html

instead of 

http://www.zdnet.com/zdtv/screensavers/answerstips/story/0%2c3656%2c2324624%2
c00.html

I fixed that (little) problem on my machine and sent a bug-report.
Now, I enjoy loading URLs containing commas :-)

Dirk


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  2:32: 5 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58])
	by hub.freebsd.org (Postfix) with ESMTP id 13FCD14A07
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 02:32:02 -0700 (PDT)
	(envelope-from Dom.Mitchell@palmerharvey.co.uk)
Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk
 (Content Technologies SMTPRS 4.0.1) with ESMTP id <B3eac6d3a4742ff54cc@mail.palmerharvey.co.uk>;
 Mon, 13 Sep 1999 10:31:47 +0100
Received: from voodoo.pandhm.co.uk (10.100.35.12 [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id SNZVMNG5; Mon, 13 Sep 1999 10:30:40 +0100
Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1)
	id 11QSSm-000CcS-00; Mon, 13 Sep 1999 10:31:52 +0100
Date: Mon, 13 Sep 1999 10:31:51 +0100
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: Dirk GOUDERS <hank@musashi.et.bocholt.fh-ge.de>,
	Wes Peters <wes@softweyr.com>, hackers@FreeBSD.ORG
Subject: Re: More press
Message-ID: <19990913103151.B48248@voodoo.pandhm.co.uk>
References: <199909121250.OAA09438@musashi.et.bocholt.fh-ge.de> <xzp671g2rio.fsf@flood.ping.uio.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <xzp671g2rio.fsf@flood.ping.uio.no>
From: Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 12, 1999 at 03:22:55PM +0200, Dag-Erling Smorgrav wrote:
> Dirk GOUDERS <hank@musashi.et.bocholt.fh-ge.de> writes:
> > Oh, sorry -- my "browse-url-at-mouse" function made
> > 
> > http://www.zdnet.com/zdtv/screensavers/answerstips/story/02c36562c23246242c00.html
> > 
> > of it...
> 
> Netscape uses commans to separate parameters to the OpenURL command.
> Fortunately, the API is open and documented, so there's nothing to
> stop someone from writing a small command-line util that does the
> equivalent of "netscape -remote" except faster and better.

If you follow the link from "netscape -help", you end up at:

http://home.netscape.com/newsref/std/remote.c

Which is a small C program to do just that.  I really should turn it
into a port...
-- 
Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator

"vi has two modes the one in which it beeps and the one in which it doesnt."
	-- Anon.


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  2:45:59 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id F247514DB1
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 02:45:56 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.3) id LAA17222;
	Mon, 13 Sep 1999 11:45:51 +0200 (CEST)
	(envelope-from des)
To: Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk>
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>,
	Dirk GOUDERS <hank@musashi.et.bocholt.fh-ge.de>,
	Wes Peters <wes@softweyr.com>, hackers@FreeBSD.ORG
Subject: Re: More press
References: <199909121250.OAA09438@musashi.et.bocholt.fh-ge.de> <xzp671g2rio.fsf@flood.ping.uio.no> <19990913103151.B48248@voodoo.pandhm.co.uk>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 13 Sep 1999 11:45:50 +0200
In-Reply-To: Dominic Mitchell's message of "Mon, 13 Sep 1999 10:31:51 +0100"
Message-ID: <xzpvh9fywj5.fsf@flood.ping.uio.no>
Lines: 13
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk> writes:
> If you follow the link from "netscape -help", you end up at:
> 
> http://home.netscape.com/newsref/std/remote.c

The page you attempted to access was not found on Netscape's web site.
You may have typed its location incorrectly, or it may have been
moved, deleted, or incorporated into another part of Netscape's site.
To report a broken link, please send a message to feedback.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  3: 1:23 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from aha.ru (bird.M9-Farm.zenon.net [195.2.83.227])
	by hub.freebsd.org (Postfix) with ESMTP id 7664E15034
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 03:01:20 -0700 (PDT)
	(envelope-from tolyar@ru.ru)
Received: from boer.demos.su ([194.87.2.129] verified)
  by aha.ru (CommuniGate Pro SMTP 3.1b9)
  with ESMTP id 2753503 for hackers@freebsd.org; Mon, 13 Sep 1999 14:01:17 +0400
Date: Mon, 13 Sep 1999 14:00:56 +0400
From: Tolyar <tolyar@ru.ru>
X-Mailer: The Bat! (v1.35) UNREG / CD5BF9353B3B7091
Reply-To: Tolyar <tolyar@ru.ru>
X-Priority: 3 (Normal)
Message-ID: <18583.990913@ru.ru>
To: hackers@freebsd.org
Subject: Problem with FreeBSD
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello All.

I try install FreeBSD on HP Vectra VA/200DT - Pentium Pro/128Mb-RAM/
Quantum Fireball CR 4.3Gb/CirrusLogic5446PCI PCI/NE2000.

When I try install FreeBSD (I'm tried 3.2-release/3.3-19990909-rc/snapshot-4.0-19990827-current)
i have some trouble. On second floppy (mfsroot.flp) before kernel setup,
FreeBSD write "zf_read: error". After this, I configured kernel (i kept only fdc0, wdc0, atkbd0, sc0)
and when system wrote "changing root device to fd0c" and after this
"rootfs is 2880Kbyte compiled in MFS" system stilled and doesn't run
install proces, but "Pause" key and scrolling was working.


Best regards,
Zherdev Anatoly  tolyar@ru.ru




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  3:12:54 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.rdc2.occa.home.com (ha1.rdc2.occa.home.com [24.2.8.66])
	by hub.freebsd.org (Postfix) with ESMTP id E5B8114FEA
	for <freebsd-hackers@FreeBSD.org>; Mon, 13 Sep 1999 03:12:52 -0700 (PDT)
	(envelope-from msides@machineshop.net)
Received: from cx801562 ([24.8.136.246]) by mail.rdc2.occa.home.com
          (InterMail v4.01.01.00 201-229-111) with SMTP
          id <19990913101251.OSFH15959.mail.rdc2.occa.home.com@cx801562>
          for <freebsd-hackers@FreeBSD.org>;
          Mon, 13 Sep 1999 03:12:51 -0700
From: "Matt" <msides@machineshop.net>
To: <freebsd-hackers@FreeBSD.org>
Subject: 
Date: Mon, 13 Sep 1999 03:12:39 -0700
Message-ID: <NDBBLHAOGLGGOGGCKGGOCECGCAAA.msides@machineshop.net>
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 IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  3:47:21 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from lindt.fat.dotat.at (lindt.fat.dotat.at [195.173.172.169])
	by hub.freebsd.org (Postfix) with ESMTP id BCB6815004
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 03:47:07 -0700 (PDT)
	(envelope-from mike@lindt.fat.dotat.at)
Received: from mike by lindt.fat.dotat.at with local (Exim 2.05 #1)
	id 11QTcb-0000rk-00; Mon, 13 Sep 1999 11:46:05 +0100
Date: Mon, 13 Sep 1999 11:46:04 +0100
From: Mike Bristow <mike@fat.dotat.at>
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk>,
	Dirk GOUDERS <hank@musashi.et.bocholt.fh-ge.de>,
	Wes Peters <wes@softweyr.com>, hackers@FreeBSD.ORG
Subject: Re: More press
Message-ID: <19990913114604.A3272@fat.dotat.at>
References: <199909121250.OAA09438@musashi.et.bocholt.fh-ge.de> <xzp671g2rio.fsf@flood.ping.uio.no> <19990913103151.B48248@voodoo.pandhm.co.uk> <xzpvh9fywj5.fsf@flood.ping.uio.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <xzpvh9fywj5.fsf@flood.ping.uio.no>; from Dag-Erling Smorgrav on Mon, Sep 13, 1999 at 11:45:50AM +0200
X-Rated: cracking, security
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Sep 13, 1999 at 11:45:50AM +0200, Dag-Erling Smorgrav wrote:
> Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk> writes:
> > If you follow the link from "netscape -help", you end up at:
> > 
> > http://home.netscape.com/newsref/std/remote.c
> 
> The page you attempted to access was not found on Netscape's web site.
> You may have typed its location incorrectly, or it may have been
> moved, deleted, or incorporated into another part of Netscape's site.
> To report a broken link, please send a message to feedback.


It works from here.  Yell if you want me to mail it to you.



michaelb@singsing:~$ wget http://home.netscape.com/newsref/std/remote.c
--11:41:07--  http://home.netscape.com:80/newsref/std/remote.c
           => `remote.c'
Connecting to home.netscape.com:80... connected!
HTTP request sent, awaiting response... 200 OK
Length: 18,579 [text/plain]

    0K -> .......... ........                                    [100%]

11:41:08 (29.55 KB/s) - `remote.c' saved [18579/18579]

michaelb@singsing:~$ head -3 remote.c 
/* -*- Mode:C; tab-width: 8 -*-
 * remote.c --- remote control of Netscape Navigator for Unix.
 * version 1.1.3, for Netscape Navigator 1.1 and newer.
michaelb@singsing:~$ 

-- 
Mike Bristow, Geek At Large			     GK/RM0501
		     Nobody's ugly after 2AM



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  4: 3:14 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mpp.pro-ns.net (pppdsle45.mpls.uswest.net [216.160.23.45])
	by hub.freebsd.org (Postfix) with ESMTP id 2052D14D79
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 04:03:06 -0700 (PDT)
	(envelope-from mpp@mpp.pro-ns.net)
Received: (from mpp@localhost)
	by mpp.pro-ns.net (8.9.3/8.9.3) id GAA03636;
	Mon, 13 Sep 1999 06:01:11 -0500 (CDT)
	(envelope-from mpp)
From: Mike Pritchard <mpp@FreeBSD.org>
Message-Id: <199909131101.GAA03636@mpp.pro-ns.net>
Subject: Re: How to prevent motd including os info
In-Reply-To: <37DC7556.82A77322@gorean.org> from Doug at "Sep 12, 1999 08:53:58 pm"
To: Doug@gorean.org (Doug)
Date: Mon, 13 Sep 1999 06:01:11 -0500 (CDT)
Cc: freebsd@gndrsh.dnsmgr.net (Rodney W. Grimes),
	des@flood.ping.uio.no (Dag-Erling Smorgrav), hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> "Rodney W. Grimes" wrote:
> 
> > It dawned on me what can be done.  Look, we get all the kernel printf's
> > from the dmesg output saved in a buffer and pull that out later with
> > syslog, looks like we could just slip a pipe fitting into /dev/console
> > that copies all it's output into the mesgbuf as well, until we smack it
> > wth the ballpean and tell it to stop doing that (Either getty lanching the
> > login: on ttyv0 could cause this, or something at the end of /etc/rc).
> > 
> > What do you think of that idea? 
> 
> 	I think that's a fine idea, and it's a lot cleaner than mine for a number
> of reasons. Completely beyond me to code, but very nice from the design
> standpoint. 

Most of the time I could care less what /etc/rc spits out.  However,
in the past, I have had to go add sleep(###) calls in various spots
in rc to that I could actually read some of the error output to figure
out why something was failing.  I wouldn't mind having all of the
/etc/rc output sent to the message buffer (and /dev/console) until a 
getty is running on ttyv0.  Or at least make it a boot option.  If you 
are having problems, boot the kernel with "boot -l" in the boot loader.

Now, adding an option doesn't help in the case of fsck suddenly
generating a million lines of output during boot, since that might not
be expected, but it does help some cases.  And scrollback buffers and 
message buffers only help if you have enough memory to hold all of 
that information.

Right now I have 3 FreeBSD machine.  1 has 192MB of RAM.  I have the
message buffer set to some very large value (because of some boot 
problem I bumped it up a lot), so I at least see all of the kernel
messages that were generating during a boot.  This helped me
debug a couple of problems.

The other two machines only have 16MB, so they still run with
a standard message buffer (geez, I remember when 16MB was *A LOT*).

Perhaps we need a "boot message buffer" (just eat up free memory minus
some protected space that is reserved for letting /etc/rc run
without swapping).  Keep sending data to that buffer during the boot 
process, and just before going multi-user, dump it off to disk and
free it.  On a 16MB machine, that shouldn't be a problem.  For those 
people still running FreeBSD machines on 4MB, that is another story, 
but even in those cases, I would bet you could still be able to record 
and store at least some of the /etc/rc output.

Its been a few years since I've seen fsck generate a couple of 
megabytes of output, so I know it is possible, but I think this 
idea could work, and solve most peoples problem of fsck generating 
MANY pages of output that just scroll by.

-Mike
-- 
Mike Pritchard
mpp@FreeBSD.org or mpp@mpp.pro-ns.net


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  5:49:24 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
	by hub.freebsd.org (Postfix) with ESMTP
	id AA42114C9D; Mon, 13 Sep 1999 05:49:22 -0700 (PDT)
	(envelope-from louie@whizzo.transsys.com)
Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1])
	by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id IAA31697;
	Mon, 13 Sep 1999 08:49:21 -0400 (EDT)
	(envelope-from louie@whizzo.transsys.com)
Message-Id: <199909131249.IAA31697@whizzo.transsys.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mike Pritchard <mpp@FreeBSD.ORG>
Cc: Doug@gorean.org (Doug),
	freebsd@gndrsh.dnsmgr.net (Rodney W. Grimes),
	des@flood.ping.uio.no (Dag-Erling Smorgrav), hackers@FreeBSD.ORG
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: How to prevent motd including os info 
References: <199909131101.GAA03636@mpp.pro-ns.net> 
In-reply-to: Your message of "Mon, 13 Sep 1999 06:01:11 CDT."
             <199909131101.GAA03636@mpp.pro-ns.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 13 Sep 1999 08:49:21 -0400
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


[I'm catching up on a bunch of FreeBSD mail since being out on vacation, so
perhaps I've missed the essence of this thread..]

I've also had the desire to capture the output produced when /etc/rc is 
run for all the reasons mentioned.  I always thought that perhaps init
would simply capture stdout on the other end of a pipe, and logically do
the "tee" thing with it.  In fact, couldn't init logically exec a

	sh /etc/rc | tee /tmp/rc-output

when invoking /etc/rc?  (Where to put the output would seem to be one
of the more difficult choices since you don't start with a writable file system
mounted anywhere..)

Or perhaps init could capture the output on the end of a pipe and 
subsequently syslog it while it's echoing it to /dev/console.

louie






To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  6:17:47 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from caxton.correionet.com.br (caxton.correionet.com.br [200.246.35.7])
	by hub.freebsd.org (Postfix) with ESMTP id 711E814F8B
	for <freebsd-hackers@freebsd.org>; Mon, 13 Sep 1999 06:17:27 -0700 (PDT)
	(envelope-from morte@correionet.com.br)
Received: from caxton.correionet.com.br (caxton.correionet.com.br [200.246.35.7])
	by caxton.correionet.com.br (8.9.3/8.9.3) with ESMTP id KAA93431;
	Mon, 13 Sep 1999 10:16:30 -0300 (EST)
Date: Mon, 13 Sep 1999 10:16:30 -0300 (EST)
From: Luiz Morte da Costa Junior <morte@correionet.com.br>
To: freebsd-hackers@freebsd.org
Cc: Luiz Morte da Costa Junior <morte@correionet.com.br>
Subject: L440GX+ Server Board
Message-ID: <Pine.BSF.4.10.9909131001030.69311-100000@caxton.correionet.com.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Hi list,

I can't solve the problem yet.

When I runnig the dmesg command, I have:

---
da0 at ahc0 bus 0 target 0 lun 0
da0: <SEAGATE ST39140LW 1483> Fixed Direct Access SCSI-2 device 
da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing
Enabled
da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
da1 at ahc0 bus 0 target 1 lun 0
da1: <SEAGATE ST39140LW 1483> Fixed Direct Access SCSI-2 device 
da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing
Enabled
da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
---

I did a test, changing only the SCSI disk, using the same motherboard
(L440GX+). I ran the dmesg command again and I received:

--
da0 at ahc0 bus 0 target 0 lun 0
 da0: <QUANTUM QM39100TD-SW N491> Fixed Direct Access SCSI-2 device 
 da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing
Enabled
 da0: 8683MB (17783250 512 byte sectors: 255H 63S/T 1106C)
--


I realized that the quantum disk have a 80.000MB/s transfers.
Does someone use a SEAGATE ST39140LW disk and have I/O problems?

Regards,
Luiz Morte.

PS:
Someone told me that vipw doens't have much I/O disk, but when I run it
with 12000 accounts, my disk have a lot off access.

On Sun, 22 Aug 1999, Luiz Morte da Costa Junior wrote:
> 
> Hi all,
> 
> I have a problem with a server running a FreeBSD 3.2.
> 
> My Server has a L440GX+ Serber Board (intel), with network card 10/100,
> SCSI AIC 7896 (80MB/s), 2 SCSI disk with 9GB (80MB/s), 2 pentium III
> 450Mhz (not overclocked). The NIC and SCSI are onboard.
> 
> I recompiled a kernel to SMP, and it worked. The server is ok, but when
I
> run a comand with disk access (whith vipw or mysql), the performance of
> server goes down. My server stays very very very slow. If I use pine to
> read my messages, it doesn't work. When the comand finishes, the server
> stays "ok" again.
> 
> I recompiled the kernel with "maxusers 128", but it doesn't work.
> 
> My SCSI cable has a terminator and the scsi setup is ok (I think :) ).
> 
> The dmesg command output is in attchmnt.
> 
> I appreciate any help.

[]s,

Luiz Morte da Costa Junior
Analista de Redes                E-mail: morte@correionet.com.br
Telefone: +55 19 754-2532        Fax: +55 19 255-7576
CorreioNet - Correio Popular     Campinas - SP - Brazil



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  6:26:37 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from aaz.links.ru (aaz.links.ru [193.125.152.37])
	by hub.freebsd.org (Postfix) with ESMTP id 7C3B5155A9
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 06:26:30 -0700 (PDT)
	(envelope-from babolo@links.ru)
Received: (from babolo@localhost)
	by aaz.links.ru (8.9.3/8.9.3) id RAA17028;
	Mon, 13 Sep 1999 17:26:19 +0400 (MSD)
Message-Id: <199909131326.RAA17028@aaz.links.ru>
Subject: Re: de0 strangenesses
In-Reply-To: <199909130856.KAA33966@gil.physik.rwth-aachen.de> from "Christoph Kukulies" at "Sep 13, 99 10:56:09 am"
To: kuku@gilberto.physik.RWTH-Aachen.DE (Christoph Kukulies)
Date: Mon, 13 Sep 1999 17:26:18 +0400 (MSD)
Cc: hackers@FreeBSD.ORG
From: "Aleksandr A.Babaylov" <babolo@links.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Christoph Kukulies writes:
> 
> On a 3.0-current of October 1998 I'm having often trouble with de0.
> The machine often reboots over night (when either the locate db is built or
> some other big job - like mirror - is running). Anyway, after the reboot,
> often de0 is dead.
> 
> This happend today again. When I came into the office I could not
> ping said machine. I sat at the console, logged in. The machine was
> perfectly alive, only the de0 interface didn't work at the BNC network.
> 
> I did a ifconfig de0 down and exactly with doing that I got a kernel message
> from the driver: de0 BNC interface enabled (or something like that).
> Doing an ifconfig de0 up right after that the interface continued working
> at the BNC port.
> 
> Can the driver writer(s) comment whether there have been changes to the driver
> WRT that behaviour so I can expect that with either 3.2 or -current
> the problem would be gone?
this is old problem - I have it in 2.2.7-RELEASE too

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

-- 
@BABOLO      http://links.ru/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  6:26:37 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from kalypso.iqm.unicamp.br (kalypso.iqm.unicamp.br [143.106.51.1])
	by hub.freebsd.org (Postfix) with ESMTP id 0FFAE1559B
	for <freebsd-hackers@freebsd.org>; Mon, 13 Sep 1999 06:26:20 -0700 (PDT)
	(envelope-from vazquez@iqm.unicamp.br)
Received: by kalypso.iqm.unicamp.br (V-MTA, from userid 105)
	id 029F8537; Mon, 13 Sep 1999 10:26:18 -0300 (EST)
Date: Mon, 13 Sep 1999 10:26:18 -0300
From: Pedro A M Vazquez <vazquez@iqm.unicamp.br>
To: Luiz Morte da Costa Junior <morte@correionet.com.br>
Cc: freebsd-hackers@freebsd.org
Subject: Re: L440GX+ Server Board
Message-ID: <19990913102618.C54562@kalypso.iqm.unicamp.br>
References: <Pine.BSF.4.10.9909131001030.69311-100000@caxton.correionet.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <Pine.BSF.4.10.9909131001030.69311-100000@caxton.correionet.com.br>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

|o|... Mon, Sep 13, 1999 at 10:16:30AM -0300, Luiz Morte da Costa Junior ...|o| wrote:
> 
> Hi list,
> 
> I can't solve the problem yet.
> 
> When I runnig the dmesg command, I have:
> 
> ---
> da0 at ahc0 bus 0 target 0 lun 0
> da0: <SEAGATE ST39140LW 1483> Fixed Direct Access SCSI-2 device 
> da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing
> Enabled
> da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
> da1 at ahc0 bus 0 target 1 lun 0
> da1: <SEAGATE ST39140LW 1483> Fixed Direct Access SCSI-2 device 
> da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing
> Enabled
> da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
> ---
> 
> I did a test, changing only the SCSI disk, using the same motherboard
> (L440GX+). I ran the dmesg command again and I received:
> 
> --
> da0 at ahc0 bus 0 target 0 lun 0
>  da0: <QUANTUM QM39100TD-SW N491> Fixed Direct Access SCSI-2 device 
>  da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing
> Enabled
>  da0: 8683MB (17783250 512 byte sectors: 255H 63S/T 1106C)
> --
> 
> 
> I realized that the quantum disk have a 80.000MB/s transfers.
> Does someone use a SEAGATE ST39140LW disk and have I/O problems?
> 
> Regards,
> Luiz Morte.
> 
> PS:
> Someone told me that vipw doens't have much I/O disk, but when I run it
> with 12000 accounts, my disk have a lot off access.

da uma olhada se ele nao ta paginando, a geracao do dbm novo e'
rapida se vc disser para ele fazer tudo em ram, senao ele faz
em disco
O pwd_mkdb tem esta opcao para evitar isso:

   -s cachesize
           Specify in megabytes the size of the memory cache used by the hash-
           ing library.  On systems with a large user base, a small cache size
           can lead to prohibitively long database file rebuild times.  As a
           rough guide, the memory usage of pwd_mkdb in megabytes will be a
           little bit more than twice the figure specified here.  The default
           is 2 megabytes.

poe ai 16M e testa pra ver, o vipw que chama ele nao tem, vc pode
recompilar o pwd_mkdb c/ um default de 16M se for o caso


> 
> On Sun, 22 Aug 1999, Luiz Morte da Costa Junior wrote:
> > 
> > Hi all,
> > 
> > I have a problem with a server running a FreeBSD 3.2.
> > 
> > My Server has a L440GX+ Serber Board (intel), with network card 10/100,
> > SCSI AIC 7896 (80MB/s), 2 SCSI disk with 9GB (80MB/s), 2 pentium III
> > 450Mhz (not overclocked). The NIC and SCSI are onboard.
> > 
> > I recompiled a kernel to SMP, and it worked. The server is ok, but when
> I
> > run a comand with disk access (whith vipw or mysql), the performance of
> > server goes down. My server stays very very very slow. If I use pine to
> > read my messages, it doesn't work. When the comand finishes, the server
> > stays "ok" again.
> > 
> > I recompiled the kernel with "maxusers 128", but it doesn't work.
> > 
> > My SCSI cable has a terminator and the scsi setup is ok (I think :) ).
> > 
> > The dmesg command output is in attchmnt.
> > 
> > I appreciate any help.
> 
> []s,
> 
> Luiz Morte da Costa Junior
> Analista de Redes                E-mail: morte@correionet.com.br
> Telefone: +55 19 754-2532        Fax: +55 19 255-7576
> CorreioNet - Correio Popular     Campinas - SP - Brazil
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message

-- 
.sig: license expired, contact your vendor


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  7:48:15 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22])
	by hub.freebsd.org (Postfix) with ESMTP id 53AC015029
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 07:48:09 -0700 (PDT)
	(envelope-from kbyanc@alcnet.com)
X-Provider: ALC Communications, Inc.  http://www.alcnet.com/
Received: from kbyanc (ws-41.alcnet.com [63.69.28.41])
	by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id KAA59240;
	Mon, 13 Sep 1999 10:48:08 -0400 (EDT)
From: "Kelly Yancey" <kbyanc@alcnet.com>
To: <hackers@FreeBSD.ORG>
Cc: <Dom.Mitchell@palmerharvey.co.uk>
Subject: RE: More Press
Date: Mon, 13 Sep 1999 10:48:07 -0400
Message-ID: <004401befdf6$fe71b700$291c453f@kbyanc.alcnet.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
In-Reply-To: <bulk.2573.19990913061751@hub.freebsd.org>
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Date: Mon, 13 Sep 1999 10:31:51 +0100
> From: Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk>
> Subject: Re: More press
>
> On Sun, Sep 12, 1999 at 03:22:55PM +0200, Dag-Erling Smorgrav wrote:
> > Dirk GOUDERS <hank@musashi.et.bocholt.fh-ge.de> writes:
> > > Oh, sorry -- my "browse-url-at-mouse" function made
> > >
> > >
http://www.zdnet.com/zdtv/screensavers/answerstips/story/02c36562c23246242c0
0.html
> > >
> > > of it...
> >
> > Netscape uses commans to separate parameters to the OpenURL command.
> > Fortunately, the API is open and documented, so there's nothing to
> > stop someone from writing a small command-line util that does the
> > equivalent of "netscape -remote" except faster and better.
>
> If you follow the link from "netscape -help", you end up at:
>
> http://home.netscape.com/newsref/std/remote.c
>
> Which is a small C program to do just that.  I really should turn it
> into a port...

  If you haven't already, I've just about finished a port for this (it is
pretty nifty). The only problem I have currently is that I have to fetch 2
files for the port (the file listed above, as well as
http://home.netscape.com/newsref/std/vroot.h). Without making a separate
port just for vroot.h, if there a way to have the port fetch 2 files? Should
I just list it using PATCH_SITES/PATCHFILES even though it isn't really a
patch? Other than that I have to write a few patches of my own (the netscape
source segfaults if no command is given and apparently presumes netscape
1.1). If I can find out the answer to fetching the 2 files, I'll send-pr the
port right away.

  Thanks,

  Kelly
 ~kbyanc@posi.net~
  FreeBSD - The Power To Serve - http://www.freebsd.org/
  Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD/





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  7:57:39 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from ddsecurity.com.br (vitoria.ddsecurity.com.br [200.18.130.93])
	by hub.freebsd.org (Postfix) with SMTP id B92BC15077
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 07:56:34 -0700 (PDT)
	(envelope-from grios@ddsecurity.com.br)
Received: (qmail 64017 invoked from network); 13 Sep 1999 14:56:22 -0000
Received: from unknown (HELO ddsecurity.com.br) (200.236.148.122)
  by vitoria.ddsecurity.com.br with SMTP; 13 Sep 1999 14:56:22 -0000
Message-ID: <37DD1093.546946D2@ddsecurity.com.br>
Date: Mon, 13 Sep 1999 11:56:19 -0300
From: Gustavo V G C Rios <grios@ddsecurity.com.br>
X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.3-RC i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Cc: hackers@freebsd.org
Subject: Re: submiting source code ?
References: <37D86506.4247EF3A@ddsecurity.com.br> <19990913090318.F89309@daemon.ninth-circle.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hay, thaaaaaaaaaaaaaaank youuuuuuuuu!
I really glad to receive your message!
It will really shelp.


Again, thanks a lot!

Jeroen Ruigrok/Asmodai wrote:
> 
> * Gustavo V G C Rios (grios@ddsecurity.com.br) [990910 04:14]:
> >I use freebsd about +- 12 months ago. I have never did any thing serious
> >at kernel level, nor i know anything about kernel desgin.
> 
> Start with:
> 
> Modern Operating Systems by Andrew S. Tanenbaum
> The Design and Implementation of 4.4BSD by Marshall Kirk McKusick et al.
> Unix Internals: The New Frontiers
> 
> Then you probably need more special in-depth books such as:
> 
> TCP/IP Illustrated by (R.I.P.) W. Richard Stevens
> Unix Network Programming by W. Richard Stevens
> The Unix Programming Environment by Rob Pike and Ritchie Kerninghan
> Advanced Programming in the Unix Environment by W. Richard Stevens
> 
> >Suppose, i would like to spend time and patience learnig Fbsd internals.
> >If, later, i were able to code something to freebsd, and suppose i do,
> >what (or better, how) should i do to have my source accepted by the core
> >team?
> 
> send-pr after you have tested, style(9)'d, documented your code and
> tested you patches against a clean checked out source base.
> 
> >What about coding style ?
> 
> As Chris said, style(9)
> 
> >What are the golden rules to have my sources widely accepted by freebsd
> >community?
> 
> Don't go the Linux way which tends to favor bloat over solid code.
> Portability and correctness of code is more important than features.
> 
> >PS: This is my first attempt to start touching the kernel, so, don't
> >blame, if i wrote something wrong.
> 
> That's ok, it's a long way before you actually will start touching the
> sources though, it involves a lot of RTFM'ing and UTSL'ing first.
> 
> --
> Jeroen Ruigrok van der Werven/Asmodai                  asmodai(at)wxs.nl
> The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
> Network/Security Specialist        BSD: Technical excellence at its best
> Workers of the world, unite!


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  7:57:57 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25])
	by hub.freebsd.org (Postfix) with ESMTP id 124E3155C8
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 07:57:42 -0700 (PDT)
	(envelope-from joe@florence.pavilion.net)
Received: (from joe@localhost)
	by florence.pavilion.net (8.9.3/8.8.8) id PAA06963;
	Mon, 13 Sep 1999 15:57:28 +0100 (BST)
	(envelope-from joe)
Date: Mon, 13 Sep 1999 15:57:28 +0100
From: Josef Karthauser <joe@pavilion.net>
To: Kelly Yancey <kbyanc@alcnet.com>
Cc: hackers@FreeBSD.ORG, Dom.Mitchell@palmerharvey.co.uk
Subject: Re: More Press
Message-ID: <19990913155728.D89466@florence.pavilion.net>
References: <bulk.2573.19990913061751@hub.freebsd.org> <004401befdf6$fe71b700$291c453f@kbyanc.alcnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <004401befdf6$fe71b700$291c453f@kbyanc.alcnet.com>
X-NCC-RegID: uk.pavilion
Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England
Phone: +44-845-333-5000
Fax: +44-845-333-5001
Mobile: +44-403-596893
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Sep 13, 1999 at 10:48:07AM -0400, Kelly Yancey wrote:
> 
>   If you haven't already, I've just about finished a port for this (it is
> pretty nifty). The only problem I have currently is that I have to fetch 2
> files for the port (the file listed above, as well as
> http://home.netscape.com/newsref/std/vroot.h). Without making a separate
> port just for vroot.h, if there a way to have the port fetch 2 files? Should
> I just list it using PATCH_SITES/PATCHFILES even though it isn't really a
> patch? Other than that I have to write a few patches of my own (the netscape
> source segfaults if no command is given and apparently presumes netscape
> 1.1). If I can find out the answer to fetching the 2 files, I'll send-pr the
> port right away.
> 

Take a look at the XFree86 port in x11.  That fetches two large tarballs, and
therefore probably does the right thing.

Joe
-- 
Josef Karthauser	FreeBSD: How many times have you booted today?
Technical Manager	Viagra for your server (http://www.uk.freebsd.org)
Pavilion Internet plc.  [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk]


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  7:59:18 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from androcles.com (androcles.com [204.57.240.10])
	by hub.freebsd.org (Postfix) with ESMTP id F14B11559E
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 07:59:11 -0700 (PDT)
	(envelope-from alex@androcles.com)
Received: (from dhh@localhost)
	by androcles.com (8.9.3/8.9.3) id HAA08514;
	Mon, 13 Sep 1999 07:59:03 -0700 (PDT)
Message-ID: <XFMail.990913075903.dhh@androcles.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <19990913114604.A3272@fat.dotat.at>
Date: Mon, 13 Sep 1999 07:59:03 -0700 (PDT)
From: "Duane H. Hesser" <dhh@androcles.com>
To: hackers@FreeBSD.ORG
Subject: Re: More press
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 13-Sep-99 Mike Bristow wrote:
> On Mon, Sep 13, 1999 at 11:45:50AM +0200, Dag-Erling Smorgrav wrote:
>> Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk> writes:
>> > If you follow the link from "netscape -help", you end up at:
>> > 
>> > http://home.netscape.com/newsref/std/remote.c
>> 
>> The page you attempted to access was not found on Netscape's web site.
>> You may have typed its location incorrectly, or it may have been
>> moved, deleted, or incorporated into another part of Netscape's site.
>> To report a broken link, please send a message to feedback.
> 
> 
> It works from here.  Yell if you want me to mail it to you.
> 

You probably already have it, as
    /usr/src/contrib/global/gozilla/remote.c

--------------
Duane H. Hesser
dhh@androcles.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  8: 1:50 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22])
	by hub.freebsd.org (Postfix) with ESMTP id 2E6F514A2F
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 08:01:41 -0700 (PDT)
	(envelope-from kbyanc@alcnet.com)
X-Provider: ALC Communications, Inc.  http://www.alcnet.com/
Received: from kbyanc (ws-41.alcnet.com [63.69.28.41])
	by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id LAA59544;
	Mon, 13 Sep 1999 11:01:38 -0400 (EDT)
From: "Kelly Yancey" <kbyanc@alcnet.com>
To: "'Josef Karthauser'" <joe@pavilion.net>
Cc: <hackers@FreeBSD.ORG>, <Dom.Mitchell@palmerharvey.co.uk>
Subject: RE: More Press
Date: Mon, 13 Sep 1999 11:01:37 -0400
Message-ID: <004501befdf8$e15df320$291c453f@kbyanc.alcnet.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
In-Reply-To: <19990913155728.D89466@florence.pavilion.net>
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> -----Original Message-----
> From: Josef Karthauser [mailto:joe@pavilion.net]
> Sent: Monday, September 13, 1999 10:57 AM
> To: Kelly Yancey
> Cc: hackers@FreeBSD.ORG; Dom.Mitchell@palmerharvey.co.uk
> Subject: Re: More Press
> 
> 
> On Mon, Sep 13, 1999 at 10:48:07AM -0400, Kelly Yancey wrote:
> > 
> >   If you haven't already, I've just about finished a port 
> for this (it is
> > pretty nifty). The only problem I have currently is that I 
> have to fetch 2
> > files for the port (the file listed above, as well as
> > http://home.netscape.com/newsref/std/vroot.h). Without 
> making a separate
> > port just for vroot.h, if there a way to have the port 
> fetch 2 files? Should
> > I just list it using PATCH_SITES/PATCHFILES even though it 
> isn't really a
> > patch? Other than that I have to write a few patches of my 
> own (the netscape
> > source segfaults if no command is given and apparently 
> presumes netscape
> > 1.1). If I can find out the answer to fetching the 2 files, 
> I'll send-pr the
> > port right away.
> > 
> 
> Take a look at the XFree86 port in x11.  That fetches two 
> large tarballs, and
> therefore probably does the right thing.
> 

  Bingo...that did the trick, port coming soon...

  Kelly
 ~kbyanc@posi.net~
  FreeBSD - The Power To Serve - http://www.freebsd.org/
  Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD/



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  8:13:10 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58])
	by hub.freebsd.org (Postfix) with ESMTP id 7E87615680
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 08:12:45 -0700 (PDT)
	(envelope-from Dom.Mitchell@palmerharvey.co.uk)
Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk
 (Content Technologies SMTPRS 4.0.1) with ESMTP id <B3eac6d3a47443751be@mail.palmerharvey.co.uk>;
 Mon, 13 Sep 1999 16:12:34 +0100
Received: from voodoo.pandhm.co.uk (10.100.35.12 [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id SNZVMNTC; Mon, 13 Sep 1999 16:11:27 +0100
Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1)
	id 11QXmY-000DFH-00; Mon, 13 Sep 1999 16:12:38 +0100
Date: Mon, 13 Sep 1999 16:12:38 +0100
To: "Duane H. Hesser" <dhh@androcles.com>
Cc: hackers@FreeBSD.ORG, Dag-Erling Smorgrav <des@flood.ping.uio.no>
Subject: Re: More press
Message-ID: <19990913161237.A50757@voodoo.pandhm.co.uk>
References: <19990913114604.A3272@fat.dotat.at> <XFMail.990913075903.dhh@androcles.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <XFMail.990913075903.dhh@androcles.com>
From: Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Sep 13, 1999 at 07:59:03AM -0700, Duane H. Hesser wrote:
> You probably already have it, as
>     /usr/src/contrib/global/gozilla/remote.c

Blimey!
-- 
Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator

"vi has two modes the one in which it beeps and the one in which it doesnt."
	-- Anon.


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  8:23:32 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from www.crb-web.com (ns1.crb-web.com [209.70.120.131])
	by hub.freebsd.org (Postfix) with SMTP id 1CE6614C12
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 08:23:29 -0700 (PDT)
	(envelope-from wayne@crb.crb-web.com)
Received: (qmail 16078 invoked by uid 1001); 13 Sep 1999 16:15:20 -0000
Date: Mon, 13 Sep 1999 12:15:20 -0400 (EDT)
From: Wayne Cuddy <wayne@crb-web.com>
Reply-To: wayne@crb-web.com
To: FreeBSD Hackers List <freebsd-hackers@FreeBSD.ORG>
Subject: device driver interface
Message-ID: <Pine.LNX.4.10.9909131204520.16008-100000@crb.crb-web.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I am trying to understand how to integrate device drivers with the kernel.
(this is my first crack at device drivers) I have a few books on device
drivers but they are a little old and have a slightly different interface with
the kernel than FreeBSD.  I figured the best place to start would be to try to
building one of the samples.  So did I did 
>/usr/share/examples/drivers/make_device_drivers.sh WDC.  The script will
attempt to build the kernel and I get the following errors:


cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes  -Wpointer-arith
-Winline -Wuninitialized -Wformat -Wunused  -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I/usr/include  -DKERNEL -DVM_STACK -include
opt_global.h -elf  ../../i386/isa/WCD.c
../../i386/isa/WCD.c: In function `WCDattach':
../../i386/isa/WCD.c:137: `WCDintr' undeclared (first use this function)
../../i386/isa/WCD.c:137: (Each undeclared identifier is reported only once
../../i386/isa/WCD.c:137: for each function it appears in.)
../../i386/isa/WCD.c: At top level:
../../i386/isa/WCD.c:177: `WCDintr' used prior to declaration
../../i386/isa/WCD.c: In function `WCDintr':
../../i386/isa/WCD.c:178: warning: unused variable `scp'
../../i386/isa/WCD.c: At top level:
../../i386/isa/WCD.c:188: conflicting types for `WCDioctl'
../../i386/isa/WCD.c:30: previous declaration of `WCDioctl'
../../i386/isa/WCD.c: In function `WCDclose':
../../i386/isa/WCD.c:226: warning: unused variable `scp'
../../i386/isa/WCD.c: In function `WCDread':
../../i386/isa/WCD.c:250: dereferencing pointer to incomplete type
../../sys/libkern.h:57: warning: inlining failed in call to `min'
../../i386/isa/WCD.c:250: warning: called from here
../../i386/isa/WCD.c:251: warning: implicit declaration of function `uiomove'
../../i386/isa/WCD.c: In function `WCDwrite':
../../i386/isa/WCD.c:267: dereferencing pointer to incomplete type
../../i386/isa/WCD.c: At top level:
../../i386/isa/WCD.c:273: conflicting types for `WCDmmap'
../../i386/isa/WCD.c:31: previous declaration of `WCDmmap'
../../i386/isa/WCD.c: In function `WCDmmap':
../../i386/isa/WCD.c:275: warning: unused variable `scp'
../../i386/isa/WCD.c: In function `WCDpoll':
../../i386/isa/WCD.c:296: warning: unused variable `scp'
../../i386/isa/WCD.c: At top level:
../../i386/isa/WCD.c:177: warning: `WCDintr' defined but not used
*** Error code 1

Why does this fail?  This script was installed of off my 3.2 cd set.

Does anyone know of an existing driver that would be a good place to start for
a newbie to understand these things?

Any and all help is appreciated,
Wayne



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  8:56: 7 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22])
	by hub.freebsd.org (Postfix) with ESMTP id DF62C14D21
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 08:56:03 -0700 (PDT)
	(envelope-from kbyanc@alcnet.com)
X-Provider: ALC Communications, Inc.  http://www.alcnet.com/
Received: from kbyanc (ws-41.alcnet.com [63.69.28.41])
	by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id LAA61888
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 11:56:03 -0400 (EDT)
From: "Kelly Yancey" <kbyanc@alcnet.com>
To: <hackers@freebsd.org>
Subject: RE: More Press
Date: Mon, 13 Sep 1999 11:56:02 -0400
Message-ID: <004601befe00$7b30bf80$291c453f@kbyanc.alcnet.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
In-Reply-To: <19990913155728.D89466@florence.pavilion.net>
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Mon, Sep 13, 1999 at 10:48:07AM -0400, Kelly Yancey wrote:
> >
> >   If you haven't already, I've just about finished a port
> for this (it is
> > pretty nifty). The only problem I have currently is that I
> have to fetch 2
> > files for the port (the file listed above, as well as
> > http://home.netscape.com/newsref/std/vroot.h). Without
> making a separate
> > port just for vroot.h, if there a way to have the port
> fetch 2 files? Should
> > I just list it using PATCH_SITES/PATCHFILES even though it
> isn't really a
> > patch? Other than that I have to write a few patches of my
> own (the netscape
> > source segfaults if no command is given and apparently
> presumes netscape
> > 1.1). If I can find out the answer to fetching the 2 files,
> I'll send-pr the
> > port right away.
> >

  (Yep, quoting myself :) )

  Alright, anyone who wants to give it a whirl, the port has been submitted
as ports/13727. It works well, but I must say it required a little bit of
effort to escape the netscape-remote commands from the command-line.

  Kelly
 ~kbyanc@posi.net~
  FreeBSD - The Power To Serve - http://www.freebsd.org/
  Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD/



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  9:12:28 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id 8530114F38
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 09:12:21 -0700 (PDT)
	(envelope-from mjacob@feral.com)
Received: from feral.com (mjacob@feral.com [192.67.166.1])
	by feral.com (8.8.7/8.8.7) with ESMTP id JAA10992;
	Mon, 13 Sep 1999 09:09:52 -0700
Date: Mon, 13 Sep 1999 09:09:52 -0700 (PWT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk>
Cc: Parag Patel <parag@cgt.com>,
	"Matthew N. Dodd" <winter@jurai.net>,
	"Daniel O'Connor" <darius@dons.net.au>, freebsd-hackers@FreeBSD.ORG
Subject: Re: NetWare client in -current
In-Reply-To: <19990913092335.A35751@voodoo.pandhm.co.uk>
Message-ID: <Pine.LNX.4.04.9909130908090.10872-100000@feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



> On Fri, Sep 10, 1999 at 11:15:12AM -0700, Parag Patel wrote:
> > Growing up programming on a KL-10, I still think the correct place for
> > line-editing is in the driver.  Hell - it's already doing basic
> > erase/kill line editing as it is.  Then you don't have to hack every
> > command-line app to get line-editing.

Yeah, and this is why VMS 4.X (early) had a terrific security bug- if you
type '#' (or was it '&') as the first character after you logged in, your
accounting records for that session were wiped.

No, a driver is *not* the place to put this kind of fooling around.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13  9:30:49 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from fanf.noc.demon.net (fanf.noc.demon.net [195.11.55.83])
	by hub.freebsd.org (Postfix) with ESMTP id 7832215076
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 09:30:43 -0700 (PDT)
	(envelope-from fanf@demon.net)
Received: from fanf by fanf.noc.demon.net with local (Exim 3.02 #13)
	id 11QZ03-000DDr-00
	for hackers@freebsd.org; Mon, 13 Sep 1999 17:30:39 +0100
To: hackers@freebsd.org
From: Tony Finch <fanf@demon.net>
Subject: Re: mounting a partition more than once
In-Reply-To: <E11QIUW-0006zu-00@dotat.at>
Message-Id: <E11QZ03-000DDr-00@fanf.noc.demon.net>
Date: Mon, 13 Sep 1999 17:30:39 +0100
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Tony Finch <fanf@demon.net> wrote:
>
>Is there a reason for disallowing concurrent read-only mounts of the
>same disk device? i.e. would things go pear-shaped if I added this
>capability? 

Well, in the absence of any comments I hacked around a bit and ended
up with the following patch (against 3.3-RC), which permits the same
block device to be mounted read-only more than once. The motivation
for this is to permit multiple chrooted environments to share the same
/usr partition.

Some things I wonder about this change is whether the mounts will share
the same pages in the buffer cache, and whether the resource
accounting is still right. I've subtly funted the meaning of
v_specmountpoint when multiple mounts happen; does this matter?

Tony.
-- 
f.a.n.finch    dot@dotat.at    fanf@demon.net    e pluribus unix


--- /usr/src/sys/sys/fcntl.h.orig	Mon Sep 13 15:21:29 1999
+++ /usr/src/sys/sys/fcntl.h	Mon Sep 13 17:04:46 1999
@@ -93,6 +93,7 @@
 #define	FMARK		0x1000		/* mark during gc() */
 #define	FDEFER		0x2000		/* defer for next gc pass */
 #define	FHASLOCK	0x4000		/* descriptor holds advisory lock */
+#define	FMOUNTING	0x8000		/* a block device is being mounted */
 #endif
 
 /* Defined by POSIX 1003.1; BSD default, but must be distinct from O_RDONLY. */
--- /usr/src/sys/miscfs/specfs/spec_vnops.c.orig	Mon Sep 13 17:11:17 1999
+++ /usr/src/sys/miscfs/specfs/spec_vnops.c	Mon Sep 13 15:37:22 1999
@@ -229,7 +229,7 @@
 		 * Do not allow opens of block devices that are
 		 * currently mounted.
 		 */
-		error = vfs_mountedon(vp);
+		error = (ap->a_mode & FMOUNTING) ? 0 : vfs_mountedon(vp);
 		if (error)
 			return (error);
 		return ((*bdevsw[maj]->d_open)(dev, ap->a_mode, S_IFBLK, p));
--- /usr/src/sys/kern/vfs_subr.c.orig	Mon Sep 13 11:44:59 1999
+++ /usr/src/sys/kern/vfs_subr.c	Mon Sep 13 11:55:06 1999
@@ -1886,6 +1886,39 @@
 	simple_unlock(&spechash_slock);
 	return (count);
 }
+
+/*
+ * Calculate the total number of writers on a special device.
+ */
+int
+vwritecount(vp)
+	register struct vnode *vp;
+{
+	struct vnode *vq, *vnext;
+	int count;
+
+loop:
+	if ((vp->v_flag & VALIASED) == 0)
+		return (vp->v_writecount);
+	simple_lock(&spechash_slock);
+	for (count = 0, vq = *vp->v_hashchain; vq; vq = vnext) {
+		vnext = vq->v_specnext;
+		if (vq->v_rdev != vp->v_rdev || vq->v_type != vp->v_type)
+			continue;
+		/*
+		 * Alias, but not in use, so flush it out.
+		 */
+		if (vq->v_writecount == 0 && vq != vp) {
+			simple_unlock(&spechash_slock);
+			vgone(vq);
+			goto loop;
+		}
+		count += vq->v_writecount;
+	}
+	simple_unlock(&spechash_slock);
+	return (count);
+}
+
 /*
  * Print out a description of a vnode.
  */
--- /usr/src/sys/ufs/ffs/ffs_vfsops.c.orig	Mon Sep 13 11:21:07 1999
+++ /usr/src/sys/ufs/ffs/ffs_vfsops.c	Mon Sep 13 17:08:23 1999
@@ -586,28 +586,33 @@
 	struct ucred *cred;
 	u_int64_t maxfilesize;					/* XXX */
 	size_t strsize;
-	int ncount;
+	int ncount, nwritecount;
 
 	dev = devvp->v_rdev;
 	cred = p ? p->p_ucred : NOCRED;
+	ronly = (mp->mnt_flag & MNT_RDONLY) != 0;
 	/*
-	 * Disallow multiple mounts of the same device.
+	 * Only allow multiple read-only mounts of the same device.
 	 * Disallow mounting of a device that is currently in use
 	 * (except for root, which might share swap device for miniroot).
 	 * Flush out any old buffers remaining from a previous use.
 	 */
-	error = vfs_mountedon(devvp);
+	error = ronly ? 0 : vfs_mountedon(devvp);
 	if (error)
 		return (error);
+	nwritecount = vwritecount(devvp);
+	if (nwritecount)
+		return (EBUSY);
 	ncount = vcount(devvp);
-
-	if (ncount > 1 && devvp != rootvp)
+	if (!ronly && ncount > 1 && devvp != rootvp)
 		return (EBUSY);
-	vn_lock(devvp, LK_EXCLUSIVE | LK_RETRY, p);
-	error = vinvalbuf(devvp, V_SAVE, cred, p, 0, 0);
-	VOP_UNLOCK(devvp, 0, p);
-	if (error)
-		return (error);
+	if (ncount <= 1) {
+		vn_lock(devvp, LK_EXCLUSIVE | LK_RETRY, p);
+		error = vinvalbuf(devvp, V_SAVE, cred, p, 0, 0);
+		VOP_UNLOCK(devvp, 0, p);
+		if (error)
+			return (error);
+	}
 
 	/*
 	 * Only VMIO the backing device if the backing device is a real
@@ -622,8 +627,8 @@
 		VOP_UNLOCK(devvp, LK_INTERLOCK, p);
 	}
 
-	ronly = (mp->mnt_flag & MNT_RDONLY) != 0;
-	error = VOP_OPEN(devvp, ronly ? FREAD : FREAD|FWRITE, FSCRED, p);
+	error = VOP_OPEN(devvp,
+		ronly ? FMOUNTING|FREAD : FMOUNTING|FREAD|FWRITE, FSCRED, p);
 	if (error)
 		return (error);
 
@@ -726,6 +731,7 @@
 	for (i = 0; i < MAXQUOTAS; i++)
 		ump->um_quotas[i] = NULLVP;
 	devvp->v_specmountpoint = mp;
+	if (!ronly) devvp->v_writecount++;
 	ffs_oldfscompat(fs);
 
 	/*
@@ -838,10 +844,12 @@
 			fs->fs_clean = 0;
 			return (error);
 		}
+		ump->um_devvp->v_writecount--;
+	}
+	if (vcount(ump->um_devvp) <= 1) {
+		ump->um_devvp->v_specmountpoint = NULL;
+		vinvalbuf(ump->um_devvp, V_SAVE, NOCRED, p, 0, 0);
 	}
-	ump->um_devvp->v_specmountpoint = NULL;
-
-	vinvalbuf(ump->um_devvp, V_SAVE, NOCRED, p, 0, 0);
 	error = VOP_CLOSE(ump->um_devvp, fs->fs_ronly ? FREAD : FREAD|FWRITE,
 		NOCRED, p);
 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 10:30: 4 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16])
	by hub.freebsd.org (Postfix) with ESMTP id 9964414F2B
	for <freebsd-hackers@freebsd.org>; Mon, 13 Sep 1999 10:28:09 -0700 (PDT)
	(envelope-from crossd@cs.rpi.edu)
Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2])
	by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA67883
	for <freebsd-hackers@freebsd.org>; Mon, 13 Sep 1999 13:27:47 -0400 (EDT)
Message-Id: <199909131727.NAA67883@cs.rpi.edu>
To: freebsd-hackers@freebsd.org
Subject: softupdates panic in 3.3-RC
Date: Mon, 13 Sep 1999 13:27:46 -0400
From: "David E. Cross" <crossd@cs.rpi.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Our ftp server crashed early this morning with what appears to be a softupdates
error:

> Sep 13 09:56:19 stumble /kernel: pid 41477 (perl), uid 0 on /exports/share3/ftp/.2: file system full
> 
> panic: softdep_write_inodeblock: indirect pointer #0 mismatch 0 != 15597568
> syncing disks... panic: softdep_lock: locking against myself

'perl' would have been the nightly mirror(1) run to sync up our ftp site.

What additional details would be usefull?  We didn't have crashdumps enabled
on this machine, so a backtrace is not fully possible, although it would seem
the contextual evidence for what went wrong is strong.

--
David Cross                               | email: crossd@cs.rpi.edu 
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
Rensselaer Polytechnic Institute,         | Ph: 518.276.2860            
Department of Computer Science            | Fax: 518.276.4033
I speak only for myself.                  | WinNT:Linux::Linux:FreeBSD


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 10:39:14 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from bingnet2.cc.binghamton.edu (mailbox.adm.binghamton.edu [128.226.10.60])
	by hub.freebsd.org (Postfix) with ESMTP id 55A5315669
	for <freebsd-hackers@freebsd.org>; Mon, 13 Sep 1999 10:39:09 -0700 (PDT)
	(envelope-from zzhang@cs.binghamton.edu)
Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72])
	by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id NAA24100
	for <freebsd-hackers@freebsd.org>; Mon, 13 Sep 1999 13:39:08 -0400 (EDT)
Date: Mon, 13 Sep 1999 13:25:09 -0400 (EDT)
From: Zhihui Zhang <zzhang@cs.binghamton.edu>
To: freebsd-hackers@freebsd.org
Subject: Let a daemon process print a message
Message-ID: <Pine.GSO.3.96.990913132102.8408A-100000@sol.cs.binghamton.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Can anyone tell me how to let a daemon process print a message to the
console?  Adding printf() does not work (I wonder if a daemon process
has been cut of relationship with stdout).  Thanks for any help.

--------------------------------------------------
Zhihui Zhang.  Please visit http://www.freebsd.org
--------------------------------------------------



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 10:47:39 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from itagua.prolan.com.br (itagua.prolan.com.br [200.231.176.137])
	by hub.freebsd.org (Postfix) with ESMTP id 828DB155B0
	for <freebsd-hackers@freebsd.org>; Mon, 13 Sep 1999 10:47:23 -0700 (PDT)
	(envelope-from armandoj@prolan.com.br)
X-Internal-ID: 37DCD275000007CF
Received: from prolan.com.br (200.196.67.69) by itagua.prolan.com.br (NPlex 2.0.123) for freebsd-hackers@freebsd.org; Mon, 13 Sep 1999 14:47:21 -0300
Message-ID: <37DD388F.3E89571E@prolan.com.br>
Date: Mon, 13 Sep 1999 14:46:56 -0300
From: Armando Santana <armandoj@prolan.com.br>
X-Mailer: Mozilla 4.61 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
Subject: subscribe
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

subscribe



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 10:49: 2 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from loki.iss.net (loki.iss.net [208.21.0.3])
	by hub.freebsd.org (Postfix) with ESMTP id 9B3A0156A9
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 10:48:16 -0700 (PDT)
	(envelope-from bmitchel@iss.net)
Received: from egon.iss.net (egon.iss.net [208.21.4.146])
	by loki.iss.net (8.9.3/8.9.3) with SMTP id NAA02351;
	Mon, 13 Sep 1999 13:46:03 -0400
Date: Mon, 13 Sep 1999 13:57:03 -0400 (EDT)
From: "Brian Mitchell (ISSATL)" <bmitchel@iss.net>
To: Zhihui Zhang <zzhang@cs.binghamton.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Let a daemon process print a message
In-Reply-To: <Pine.GSO.3.96.990913132102.8408A-100000@sol.cs.binghamton.edu>
Message-ID: <Pine.BSF.3.96.990913135151.367F-100000@egon.iss.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

syslog() with the proper facility is probably the best way to do this.
Another possibility is opening /dev/console, but I think that will aquire
a controlling terminal.

On Mon, 13 Sep 1999, Zhihui Zhang wrote:

> 
> Can anyone tell me how to let a daemon process print a message to the
> console?  Adding printf() does not work (I wonder if a daemon process
> has been cut of relationship with stdout).  Thanks for any help.
> 
> --------------------------------------------------
> Zhihui Zhang.  Please visit http://www.freebsd.org
> --------------------------------------------------
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 11: 4:18 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from voyager.fisicc-ufm.edu (ip-198-202.guate.net [209.198.197.202])
	by hub.freebsd.org (Postfix) with ESMTP id 5C52315955
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 11:02:29 -0700 (PDT)
	(envelope-from obonilla@voyager.fisicc-ufm.edu)
Received: (from obonilla@localhost)
	by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id MAA08547;
	Mon, 13 Sep 1999 12:01:13 -0600 (CST)
	(envelope-from obonilla)
Date: Mon, 13 Sep 1999 12:01:13 -0600
From: Oscar Bonilla <obonilla@fisicc-ufm.edu>
To: Wayne Cuddy <wayne@crb-web.com>
Cc: hackers@FreeBSD.ORG
Subject: Re: more info Re: how did I manage this?
Message-ID: <19990913120113.A8431@fisicc-ufm.edu>
References: <19990912101345.F14022@holly.calldei.com> <Pine.LNX.4.10.9909121224360.7847-100000@crb.crb-web.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre1i
In-Reply-To: <Pine.LNX.4.10.9909121224360.7847-100000@crb.crb-web.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 12, 1999 at 12:29:55PM -0400, Wayne Cuddy wrote:
> >rm '$DEST_DIR'
> rm: $DEST_DIR: is a directory
> 
> >ls '$DEST_DIR'
> $2
> 

rm doesn't work on directories.. go for 
$ rm -rf '$DEST_DIR'
or
$ rm '$DEST_DIR'/'$2'
$ rmdir '$DEST_DIR'

regards,

-Oscar

-- 
For PGP Public Key: finger obonilla@fisicc-ufm.edu


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 11:42:31 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP
	id F338A14FD5; Mon, 13 Sep 1999 11:42:23 -0700 (PDT)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA31048;
	Mon, 13 Sep 1999 14:40:53 -0400 (EDT)
	(envelope-from wollman)
Date: Mon, 13 Sep 1999 14:40:53 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199909131840.OAA31048@khavrinen.lcs.mit.edu>
To: Bosko Milekic <bmilekic@dsuper.net>
Cc: Stas Kisel <stas@sonet.crimea.ua>, avalon@coombs.anu.edu.au,
	freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG
Subject: Re: mbuf shortage situations (followup)
In-Reply-To: <Pine.OSF.4.05.9909122304470.18795-300000@oracle.dsuper.net>
References: <199909091447.SAA24055@sonet.crimea.ua>
	<Pine.OSF.4.05.9909122304470.18795-300000@oracle.dsuper.net>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<<On Sun, 12 Sep 1999 23:19:13 -0400 (EDT), Bosko Milekic <bmilekic@dsuper.net> said:

>   This message is in MIME format.  The first part should be readable text,
>   while the remaining parts are likely unreadable without MIME-aware tools.
>   Send mail to mime@docserver.cac.washington.edu for more info.

It would be preferable if text were sent as text, since MIME-encoded
patches require more effort to read.

> 	I'm also aware of the possiblity of some people not liking the
> fact that we tsleep() forever (e.g. tsleep(x,x,x,0)). 


I don't have any problem with sleeping forever -- but I am concerned
about the possibility of deadlock, especially when client-NFS is
involved.  If the problem just moves around and has harder-to-recover
symptoms, the change isn't helping.

The 4.3BSD code had two different behaviors:

	- For clusters, if M_WAIT was specified and there was no space
left in mb_map, it panicked.  However, m_clalloc was never called with
M_WAIT, so that panic was effectively dead code.

	- For mbufs, if M_WAIT was specified and there were no mbufs
available, it would sleep at PZERO - 1 (which was interruptible).

In 4.3, the code was able to deal with cluster allocation failing.  We
have a somewhat different situation now, because many network
interface devices have less-flexible DMA mechanisms which don't allow
packet reception into non-contiguous buffers, so we need to have at
least a certain number of clusters available for this purpose.

-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-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 12: 8:28 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP id A8FA014F8C
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 12:08:22 -0700 (PDT)
	(envelope-from ambrisko@whistle.com)
Received: from whistle.com (crab.whistle.com [207.76.205.112])
	by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA70271
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 12:08:22 -0700 (PDT)
Received: (from ambrisko@localhost)
	by whistle.com (8.9.1/8.9.1) id MAA91915
	for hackers@FreeBSD.ORG; Mon, 13 Sep 1999 12:07:42 -0700 (PDT)
	(envelope-from ambrisko)
From: Doug Ambrisko <ambrisko@whistle.com>
Message-Id: <199909131907.MAA91915@whistle.com>
Subject: Re: damn ATX power supplies...
In-Reply-To: <19990911103119.4253B1CB1@overcee.netplex.com.au> from Peter Wemm at "Sep 11, 99 06:31:19 pm"
To: hackers@FreeBSD.ORG
Date: Mon, 13 Sep 1999 12:07:42 -0700 (PDT)
X-Mailer: ELM [version 2.4ME+ PL29 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Just my 2 cents and a staple ...

A staple bent properly and wedged in the crimp part of the pin between
the green wire to a black wire does the trick for me.  Now I turn that
machine on via the power switch on the back of the power supply which 
ATX power supply people are now adding.

I have a devel motherboard that I'm using without a manual and without
a working on button.

For more info just look at the various ATX spec's online.

Doug A.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 12:44: 2 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25])
	by hub.freebsd.org (Postfix) with SMTP id A441714EEE
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 12:43:57 -0700 (PDT)
	(envelope-from atrn@zeta.org.au)
Received: (qmail 17213 invoked from network); 13 Sep 1999 19:43:50 -0000
Received: from d219.syd2.zeta.org.au (HELO ska.bsn) (203.26.9.91)
  by gidora.zeta.org.au with SMTP; 13 Sep 1999 19:43:50 -0000
Received: (from andy@localhost)
	by ska.bsn (8.9.3/8.9.3) id FAA79103;
	Tue, 14 Sep 1999 05:57:16 +1000 (EST)
	(envelope-from andy)
Message-Id: <199909131957.FAA79103@ska.bsn>
Date: Tue, 14 Sep 1999 05:57:13 +1000 (EST)
From: atrn@zeta.org.au
Reply-To: atrn@zeta.org.au
Subject: Re: damn ATX power supplies...
To: Doug Ambrisko <ambrisko@whistle.com>
Cc: hackers@FreeBSD.ORG
In-Reply-To: <199909131907.MAA91915@whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On 13 Sep, Doug Ambrisko wrote:
> A staple bent properly and wedged in the crimp part of the pin between
> the green wire to a black wire does the trick for me.

When building a box of disks (no m/b) we used a paper clip.  No m/b
meant we could just short the pins and not worry about plugging it
in.  Damm lab tech. saw it and did it properly (even used heat shrink
on the patched wires, sigh... how "tidy" and h/w like is that). Oh,
and watch our for the Canon "ATX Motherboard Emulator" patent ;)

--
Andy Newman



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 13:26:49 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18])
	by hub.freebsd.org (Postfix) with ESMTP id 4969915121
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 13:26:45 -0700 (PDT)
	(envelope-from zzhang@cs.binghamton.edu)
Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72])
	by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id QAA07094;
	Mon, 13 Sep 1999 16:26:42 -0400 (EDT)
Date: Mon, 13 Sep 1999 16:12:44 -0400 (EDT)
From: Zhihui Zhang <zzhang@cs.binghamton.edu>
To: "Brian Mitchell (ISSATL)" <bmitchel@iss.net>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Let a daemon process print a message
In-Reply-To: <Pine.BSF.3.96.990913135151.367F-100000@egon.iss.net>
Message-ID: <Pine.GSO.3.96.990913160828.9633A-100000@sol.cs.binghamton.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Mon, 13 Sep 1999, Brian Mitchell (ISSATL) wrote:

> syslog() with the proper facility is probably the best way to do this.
> Another possibility is opening /dev/console, but I think that will aquire
> a controlling terminal.
> 
> On Mon, 13 Sep 1999, Zhihui Zhang wrote:
> 
> > 
> > Can anyone tell me how to let a daemon process print a message to the
> > console?  Adding printf() does not work (I wonder if a daemon process
> > has been cut of relationship with stdout).  Thanks for any help.
> > 

I have tested syslog().  I find out:  (1) The log messages will go into
/var/log/messages and appear on the console only after I login in (as
root).  (2) The LOG_INFO priority does not cause the messages to appear on
the console or to be written into file /var/log/messages. 

Can anyone explain the reason for me?  Thanks a lot.

-Zhihui



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 13:50: 6 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from bantu.cl.msu.edu (bantu.cl.msu.edu [35.8.3.18])
	by hub.freebsd.org (Postfix) with ESMTP id 412D615121
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 13:50:02 -0700 (PDT)
	(envelope-from dervish@bantu.cl.msu.edu)
Received: (from dervish@localhost)
	by bantu.cl.msu.edu (8.9.3/8.9.3) id QAA48611;
	Mon, 13 Sep 1999 16:49:16 -0400 (EDT)
	(envelope-from dervish)
Date: Mon, 13 Sep 1999 16:49:15 -0400
From: bush doctor <dervish@bantu.cl.msu.edu>
To: Zhihui Zhang <zzhang@cs.binghamton.edu>
Cc: "Brian Mitchell (ISSATL)" <bmitchel@iss.net>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: Let a daemon process print a message
Message-ID: <19990913164915.A44185@bantu.cl.msu.edu>
References: <Pine.BSF.3.96.990913135151.367F-100000@egon.iss.net> <Pine.GSO.3.96.990913160828.9633A-100000@sol.cs.binghamton.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <Pine.GSO.3.96.990913160828.9633A-100000@sol.cs.binghamton.edu>; from Zhihui Zhang on Mon, Sep 13, 1999 at 04:12:44PM -0400
X-Operating-System: FreeBSD 4.0-CURRENT i386
X-PGP-Fingerprint: 35 95 F8 63 DA 5B 32 51  8F A9 AC 3C B4 74 F3 BA
WWW-Home-Page: http://www.msu.edu/~ikhala
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Out of da blue Zhihui Zhang aka (zzhang@cs.binghamton.edu) said:
> 
> On Mon, 13 Sep 1999, Brian Mitchell (ISSATL) wrote:
> 
> > syslog() with the proper facility is probably the best way to do this.
> > Another possibility is opening /dev/console, but I think that will aquire
> > a controlling terminal.
> > 
> > On Mon, 13 Sep 1999, Zhihui Zhang wrote:
> > 
> > > 
> > > Can anyone tell me how to let a daemon process print a message to the
> > > console?  Adding printf() does not work (I wonder if a daemon process
> > > has been cut of relationship with stdout).  Thanks for any help.
> > > 
> 
> I have tested syslog().  I find out:  (1) The log messages will go into
> /var/log/messages and appear on the console only after I login in (as
> root).  (2) The LOG_INFO priority does not cause the messages to appear on
> the console or to be written into file /var/log/messages. 
> 
> Can anyone explain the reason for me?  Thanks a lot.
Did you add an entry in /etc/syslog.conf for your daemon?
If not check the man page for syslog.conf(5) for details ...


> 
> -Zhihui
> 
> 

#:^)
-- 
So ya want ta here da roots?
Dem that feels it knows it ...
bush doctor <dervish@bantu.cl.msu.edu>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 14:53: 9 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from fanf.noc.demon.net (fanf.noc.demon.net [195.11.55.83])
	by hub.freebsd.org (Postfix) with ESMTP id DA37D14CEE
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 14:52:54 -0700 (PDT)
	(envelope-from fanf@demon.net)
Received: from fanf by fanf.noc.demon.net with local (Exim 3.02 #13)
	id 11Qe1j-000DRT-00; Mon, 13 Sep 1999 22:52:43 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Tony Finch <fanf@demon.net>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Tony Finch <fanf@demon.net>, hackers@FreeBSD.ORG
Subject: Re: mounting a partition more than once
In-Reply-To: <199909132116.OAA25920@apollo.backplane.com>
References: <E11QZ03-000DDr-00@fanf.noc.demon.net>
	<199909132116.OAA25920@apollo.backplane.com>
X-Mailer: VM 6.34 under Emacs 19.34.1
Message-Id: <E11Qe1j-000DRT-00@fanf.noc.demon.net>
Date: Mon, 13 Sep 1999 22:52:43 +0100
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Matthew Dillon <dillon@apollo.backplane.com> wrote:
> :Tony Finch <fanf@demon.net> wrote:
> :
> :Well, in the absence of any comments I hacked around a bit and ended
> :up with the following patch (against 3.3-RC), which permits the same
> :block device to be mounted read-only more than once. The motivation
> :for this is to permit multiple chrooted environments to share the same
> :/usr partition.
> 
>     Hmm... well, there is a problem here.  I believe this will allow
>     you to open the underlying block device read-only as well as mount
>     the filesystem read-only.  This will confuse the buffer cache badly.

I don't think so -- spec_open checks whether the block device has been
mounted in order to prevent this, and I made sure that that check
remains in force except when spec_open is called by ffs_mountfs (by
adding the FMOUNTING flag). I assumed that the buffer cache will
handle multiple read-only mounts because it handles multiple userland
reading file descriptors.

>     Also, this may not be the best place to put the code.  It make sense
>     to be able to mount a block device multiple times in a read-only
>     fashion, but the code should be in the open for the block device
>     rather then in UFS/FFS, so it can be used with other filesystems
>     and for other purposes.

Yes, it's evident that this is true because I had to hack around
essentially the same test in both spec_open and ffs_mountfs; removing
the checks down from ffs_mountfs so it relies on spec_mount to DTRT
would be neater, I think.

Tony.
-- 
f.a.n.finch    dot@dotat.at    fanf@demon.net    e pluribus unix


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 16:51:25 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from bingnet2.cc.binghamton.edu (mailbox.adm.binghamton.edu [128.226.10.60])
	by hub.freebsd.org (Postfix) with ESMTP id 32B18153F8
	for <freebsd-hackers@freebsd.org>; Mon, 13 Sep 1999 16:51:17 -0700 (PDT)
	(envelope-from zzhang@cs.binghamton.edu)
Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72])
	by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id TAA21176
	for <freebsd-hackers@freebsd.org>; Mon, 13 Sep 1999 19:51:16 -0400 (EDT)
Date: Mon, 13 Sep 1999 19:37:18 -0400 (EDT)
From: Zhihui Zhang <zzhang@cs.binghamton.edu>
To: freebsd-hackers@freebsd.org
Subject: NFS authentication
Message-ID: <Pine.GSO.3.96.990913193434.10215A-100000@sol.cs.binghamton.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I am wondering where the NFS authentication is done in FreeBSD. Is it done
by the NFS daemon mountd (or other daemon) or within the kernel?  Can
anyone give me a pointer?  Thanks a lot. 

--------------------------------------------------
Zhihui Zhang.  Please visit http://www.freebsd.org
--------------------------------------------------



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 16:52:52 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22])
	by hub.freebsd.org (Postfix) with ESMTP id D39DC153F8
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 16:52:42 -0700 (PDT)
	(envelope-from kbyanc@alcnet.com)
X-Provider: ALC Communications, Inc.  http://www.alcnet.com/
Received: from kbyanc (ws-41.alcnet.com [63.69.28.41])
	by kronos.alcnet.com (8.9.3/8.9.3/antispam) with SMTP id TAA70977
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 19:52:40 -0400 (EDT)
From: "Kelly Yancey" <kbyanc@alcnet.com>
To: <hackers@freebsd.org>
Subject: RE: Dell PERC LVD card (Power Edge Raid Controller)
Date: Mon, 13 Sep 1999 19:52:39 -0400
Message-ID: <005201befe43$10130b20$291c453f@kbyanc.alcnet.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
In-Reply-To: <37D556A7.2916BE51@softweyr.com>
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> > Thomas Uhrfelt wrote:
> >
> > An excellent initiative!
> >
> > I think there are many administrators/system managers out
> > there with a huge stack of unused goods lying on the shelves to
> > no use at all. Perhaps there should be a database where
> > interested devicedriver programmers could post their needs and
> > sysadminds could post their unneeded hardware on. Perhaps in
> > that way we could speed up the development of HW drivers
> > for FreeBSD? Any thoughts on this one?
>
> Kelly Yancey wrote:
>
>   This is indeed a good idea. If nobody else has stepped up to the
> challenge, I will try to have such a site up by the end of
> the week (Well, let's make it Sunday...gives me the weekend to work
> on it too :) ). I'll keep everyone posted.
>
>   Kelly
>
>

  I have gotten a few e-mail today pointing out that I didn't post anything
about my progress on this web site on Sunday (like I promised above). I'm
not dead, just a little delayed. :) Anyway, I'm making pretty good headway
on the site and should have it wrapped up over the next couple of days. When
I'm done, I'll let everyone know so maybe we can start geting more hardware
into developers' hands!

  Kelly
 ~kbyanc@posi.net~
  FreeBSD - The Power To Serve - http://www.freebsd.org/
  Join Team FreeBSD - http://www.posi.net/freebsd/Team-FreeBSD/



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 16:59:51 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from jules.res.cmu.edu (JULES.RES.CMU.EDU [128.2.144.56])
	by hub.freebsd.org (Postfix) with ESMTP id C47AF14E8C
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 16:59:47 -0700 (PDT)
	(envelope-from greg@jules.res.cmu.edu)
Received: from jules.res.cmu.edu (localhost [127.0.0.1])
	by jules.res.cmu.edu (8.9.3/8.9.2) with ESMTP id UAA11296
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 20:00:02 GMT
	(envelope-from greg@jules.res.cmu.edu)
Message-Id: <199909132000.UAA11296@jules.res.cmu.edu>
X-Mailer: exmh version 2.0.2 2/24/98
To: hackers@FreeBSD.ORG
Subject: debugging a proc's kernel stack...
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 13 Sep 1999 20:00:02 +0000
From: greg <greg@jules.res.cmu.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi, I want to see where some a deadlock is occurring in the kernel.  I've got 
a dump with a bunch of processes in the inode or namecache state.

Can anybody give me a hint about how to find a proc's "kernel stack" - so that 
I can find out what these kernel was doing for these processes when it locked 
up...

(see "repeated deadlocks in FS ..." on the smp list for more info about the problem)...

thanks alot,
greg 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 17: 3: 6 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5246C14F45; Mon, 13 Sep 1999 17:02:55 -0700 (PDT)
	(envelope-from bmilekic@dsuper.net)
Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1])
	by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id UAA04903;
	Mon, 13 Sep 1999 20:02:52 -0400 (EDT)
Date: Mon, 13 Sep 1999 20:02:50 -0400 (EDT)
From: Bosko Milekic <bmilekic@dsuper.net>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG
Subject: Re: mbuf shortage situations (followup)
In-Reply-To: <199909130336.UAA20252@apollo.backplane.com>
Message-ID: <Pine.OSF.4.05.9909131942360.7389-100000@oracle.dsuper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



!>    I think that what needs to be done is to split the problem in two.  First,
!>    allow the mbuf routines to return a failure even with M_WAIT.  If M_WAIT
!>    is used, it simply means 'try harder, sleeping a bit if necessary'.  This 
!>    requires ensuring that all the networking code deal with the failure
!>    case - a time consuming but straightforward task.  If a failure occurs,
!>    one simply drops the packet, not the connection or anything else drastic.
!>    just the packet.

	Yes, these is mainly the part I've been working on recently. The
sleeping and what not (as I'm sure you've seen from the patches if you
looked at them) has already been completed. Adding a counter that will
expire and return a pre-defined error is trivial, in this case.

	The only real issue here (if we can call it that) is get _all_ the
networking code to recognize this. Anyone want to help? :-)


!>
!>    The second problem that needs to be addressed is resource exhaustion.
!>    For example, allocating thousands of connections and socket-opting their
!>    buffers as large as possible, or programs such as syslog accepting new
!>    connections ad-infinitum.  This is a harder problem to fix properly,
!>    but a lot of the various issues such as those with syslog can be dealt 
!>    with in userland rather then the kernel.
!>
!>						-Matt
!>

	I agree. The issue here is somewhat related (if I understand your
explanation correctly) to [local] processes attempting to grab a lot of
socket buffer space. I was a little less concerned with this issue since,
as I previously mentionned, Brian Feldman is working on limiting socket
buffer space. Nonetheless, if we do not consider limiting, here's what I
believe will need to be done:

	As explained above, when we run out of mbufs and/or mbuf
clusters (and some are needed), if we are M_WAIT (when processes socket
opt their buffers as large as possible, the call is usually with M_WAIT),
we will end up tsleep()ing for certain periods of time, until our counter
expires and we return our pre-defined error (as mentionned above). When we
do return this error, however, the caller (for instance, we can consider
sosend() the caller -- which, if I remember correctly, is one of the
callers to MGET() when we setsockopt a large buffer and consequently
write() to this socket), will also have to know how to properly deal with
this error (e.g.: kill the process?).

	Killing the process may seem somewhat sadistic to some ( :-) ),
but remember that if we do get to the point where 'normal' local processes
eat up so much buffer space that we run out, we should probably be
increasing NMBCLUSTERS and/or maxusers anyway.

	As for script weenies, I hope that Brian (and whomever else may be
working on it) gets that sockbuf limiting code done, because, to be quite
honest, I don't think that script kids having to comprimise more than one
account just so they can DoS a box will be much of an issue (if worse
comes to worse, we can limit per gid -as opposed to per uid). With
exhaustion attacks such as these, we're better off just limiting.

Regards,
Bosko Milekic.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 17:19:56 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 566A515251; Mon, 13 Sep 1999 17:19:46 -0700 (PDT)
	(envelope-from bmilekic@dsuper.net)
Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1])
	by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id UAA12720;
	Mon, 13 Sep 1999 20:19:44 -0400 (EDT)
Date: Mon, 13 Sep 1999 20:19:44 -0400 (EDT)
From: Bosko Milekic <bmilekic@dsuper.net>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc: freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG
Subject: Re: mbuf shortage situations (followup)
In-Reply-To: <199909131840.OAA31048@khavrinen.lcs.mit.edu>
Message-ID: <Pine.OSF.4.05.9909132010200.7389-100000@oracle.dsuper.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Mon, 13 Sep 1999, Garrett Wollman wrote:

!><<On Sun, 12 Sep 1999 23:19:13 -0400 (EDT), Bosko Milekic <bmilekic@dsuper.net> said:
!>
!>>   This message is in MIME format.  The first part should be readable text,
!>>   while the remaining parts are likely unreadable without MIME-aware tools.
!>>   Send mail to mime@docserver.cac.washington.edu for more info.
!>
!>It would be preferable if text were sent as text, since MIME-encoded
!>patches require more effort to read.
!>

	I deffinately agree. This is obviously my mistake, and I was
somewhat in a rush, very lagged (modem, eurgh), using pine, and made
several [dumb] typos in the 'Attatchement' field.


!>> 	I'm also aware of the possiblity of some people not liking the
!>> fact that we tsleep() forever (e.g. tsleep(x,x,x,0)). 
!>
!>
!>I don't have any problem with sleeping forever -- but I am concerned
!>about the possibility of deadlock, especially when client-NFS is
!>involved.  If the problem just moves around and has harder-to-recover
!>symptoms, the change isn't helping.

	Well, the main purpose of the code is to basically sleep until
something is freed after we've already exhausted the mb_map arena (as I'm
sure you've seen if you were able to grab the attachements). This is
really a-la-limite stuff. In other words, if 'normal' local programs are
having trouble because of mb_map exhaustion, then maxusers && nmbclusters
would have to be augmented.

!>
!>The 4.3BSD code had two different behaviors:
!>
!>	- For clusters, if M_WAIT was specified and there was no space
!>left in mb_map, it panicked.  However, m_clalloc was never called with
!>M_WAIT, so that panic was effectively dead code.

	Hmmm. If m_clalloc was never called with M_WAIT, then all the code
calling m_clalloc deffinately checked its return value. It probably had
specific ways to deal with m_clalloc returning failures, too?

!>
!>	- For mbufs, if M_WAIT was specified and there were no mbufs
!>available, it would sleep at PZERO - 1 (which was interruptible).
!>
!>In 4.3, the code was able to deal with cluster allocation failing.  We
!>have a somewhat different situation now, because many network
!>interface devices have less-flexible DMA mechanisms which don't allow
!>packet reception into non-contiguous buffers, so we need to have at
!>least a certain number of clusters available for this purpose.

	Exactly. This is the next challenge. As for things being
interruptable, as I mentionned to a reply to Matt Dillon just a few
seconds ago, getting the tsleep to occasionally expire is trivial. As you
say above, it's dealing with the failure that is the issue.

!>
!>-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
!>

Cheers,
Bosko Milekic.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 17:48:14 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32])
	by hub.freebsd.org (Postfix) with ESMTP id 8C22514F2D
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 17:48:12 -0700 (PDT)
	(envelope-from dwhite@resnet.uoregon.edu)
Received: from localhost (dwhite@localhost)
	by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id RAA04382
	for <hackers@freebsd.org>; Mon, 13 Sep 1999 17:48:11 -0700 (PDT)
	(envelope-from dwhite@resnet.uoregon.edu)
Date: Mon, 13 Sep 1999 17:48:11 -0700 (PDT)
From: Doug White <dwhite@resnet.uoregon.edu>
To: hackers@freebsd.org
Subject: Multiple NAT alias addresses
Message-ID: <Pine.BSF.4.10.9909131744020.88005-100000@resnet.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

hello ..

We're trying to turn up a firewall box running NAT with multiple external
IPs.  I added the alias and set up natd.conf as follows:

use_sockets yes
same_ports yes
#
# machine1 redirections 
#redirect_port tcp 192.168.2.237:ssh 1.2.3.4:ssh
#redirect_port tcp 192.168.2.237:smtp 1.2.3.4:smtp
#redirect_port tcp 192.168.2.237:pop3 1.2.3.4:pop3
#redirect_port tcp 192.168.2.237:imap4 1.2.3.4:imap4

# machine2 redirections
redirect_port tcp 192.168.2.201:ssh 1.2.3.5:ssh
redirect_port tcp 192.168.2.201:http 1.2.3.5:http

I start natd with:

natd -f /etc/natd.conf -n fxp0  where fxp0 is the public-side interface.

Restarting natd with this configuration causes it to block everything.
Does natd support multiple alias addresses, or am I missing something
obvious?

This is a production situation so doing test runs for logs is difficult.
I can get more info in ~30 minutes, but if someone can note any
inconsistencies that would be great.

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-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 18: 3:37 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1])
	by hub.freebsd.org (Postfix) with ESMTP id BBF6015535
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 18:03:07 -0700 (PDT)
	(envelope-from ru@ucb.crimea.ua)
Received: (from ru@localhost)
	by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id EAA77794;
	Tue, 14 Sep 1999 04:02:20 +0300 (EEST)
	(envelope-from ru)
Date: Tue, 14 Sep 1999 04:02:20 +0300
From: Ruslan Ermilov <ru@ucb.crimea.ua>
To: Doug White <dwhite@resnet.uoregon.edu>
Cc: hackers@FreeBSD.ORG
Subject: Re: Multiple NAT alias addresses
Message-ID: <19990914040220.B71293@relay.ucb.crimea.ua>
Mail-Followup-To: Doug White <dwhite@resnet.uoregon.edu>,
	hackers@FreeBSD.ORG
References: <Pine.BSF.4.10.9909131744020.88005-100000@resnet.uoregon.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <Pine.BSF.4.10.9909131744020.88005-100000@resnet.uoregon.edu>; from Doug White on Mon, Sep 13, 1999 at 05:48:11PM -0700
X-Operating-System: FreeBSD 3.2-STABLE i386
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Sep 13, 1999 at 05:48:11PM -0700, Doug White wrote:
> hello ..
> 
> We're trying to turn up a firewall box running NAT with multiple external
> IPs.  I added the alias and set up natd.conf as follows:
> 
> use_sockets yes
> same_ports yes
> #
> # machine1 redirections 
> #redirect_port tcp 192.168.2.237:ssh 1.2.3.4:ssh
> #redirect_port tcp 192.168.2.237:smtp 1.2.3.4:smtp
> #redirect_port tcp 192.168.2.237:pop3 1.2.3.4:pop3
> #redirect_port tcp 192.168.2.237:imap4 1.2.3.4:imap4
> 
> # machine2 redirections
> redirect_port tcp 192.168.2.201:ssh 1.2.3.5:ssh
> redirect_port tcp 192.168.2.201:http 1.2.3.5:http
> 
> I start natd with:
> 
> natd -f /etc/natd.conf -n fxp0  where fxp0 is the public-side interface.
> 
> Restarting natd with this configuration causes it to block everything.
> 
So, without redirect_port's it works OK?
Have you tried to run it in the foreground? (`natd -v')

> Does natd support multiple alias addresses, or am I missing something
> obvious?
> 
Definitely supports!

BTW, what version you are on?


-- 
Ruslan Ermilov		Sysadmin and DBA of the
ru@ucb.crimea.ua	United Commercial Bank,
ru@FreeBSD.org		FreeBSD committer,
+380.652.247.647	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 19:25:27 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
	by hub.freebsd.org (Postfix) with ESMTP id 530AF14F15
	for <hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 19:25:21 -0700 (PDT)
	(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 LAA17890;
	Tue, 14 Sep 1999 11:55:22 +0930 (CST)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id LAA26081;
	Tue, 14 Sep 1999 11:55:20 +0930 (CST)
Date: Tue, 14 Sep 1999 11:55:20 +0930
From: Greg Lehey <grog@lemis.com>
To: greg <greg@jules.res.cmu.edu>
Cc: hackers@FreeBSD.ORG
Subject: Re: debugging a proc's kernel stack...
Message-ID: <19990914115519.A10106@freebie.lemis.com>
References: <199909132000.UAA11296@jules.res.cmu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <199909132000.UAA11296@jules.res.cmu.edu>; from greg on Mon, Sep 13, 1999 at 08:00:02PM +0000
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
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-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Monday, 13 September 1999 at 20:00:02 +0000, greg wrote:
> Hi, I want to see where some a deadlock is occurring in the kernel.  I've got
> a dump with a bunch of processes in the inode or namecache state.
>
> Can anybody give me a hint about how to find a proc's "kernel stack" - so that
> I can find out what these kernel was doing for these processes when it locked
> up...
>
> (see "repeated deadlocks in FS ..." on the smp list for more info about the problem)...

Take a look at the .gdbinits in /usr/src/sys/modules/vinum.  There's a
little bit of documentation in vinum(4), but not really enough.  The
functions you might want are (extracted from gdb's "help user"):

btp -- Show a backtrace for the process whose pid is specified as a parameter
btpa -- Show backtraces for all processes in the system
btpp -- Show a backtrace for the process previously selected with 'defproc'
btr -- Show a backtrace from the ebp address specified
defproc -- Specify a process for btpp and fr commands
fr -- Show the frame of the stack of the process previously selected with 'defproc'

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-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 20:35:22 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154])
	by hub.freebsd.org (Postfix) with ESMTP id 030E815147
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 13 Sep 1999 20:35:18 -0700 (PDT)
	(envelope-from parag@pinhead.parag.codegen.com)
Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1])
	by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id UAA02142;
	Mon, 13 Sep 1999 20:34:59 -0700 (PDT)
	(envelope-from parag@pinhead.parag.codegen.com)
To: Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk>
Cc: "Matthew N. Dodd" <winter@jurai.net>,
	"Daniel O'Connor" <darius@dons.net.au>, freebsd-hackers@FreeBSD.ORG
Subject: Command-line editing [was NetWare client in -current]
In-Reply-To: Message from Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk> 
   of "Mon, 13 Sep 1999 09:23:36 BST." <19990913092335.A35751@voodoo.pandhm.co.uk> 
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
Date: Mon, 13 Sep 1999 20:34:59 -0700
Message-ID: <2138.937280099@pinhead.parag.codegen.com>
From: Parag Patel <parag@cgt.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 13 Sep 1999 09:23:36 BST, Dominic Mitchell wrote:
>
>On Fri, Sep 10, 1999 at 11:15:12AM -0700, Parag Patel wrote:
>> Growing up programming on a KL-10, I still think the correct place for
>> line-editing is in the driver.  Hell - it's already doing basic
>> erase/kill line editing as it is.  Then you don't have to hack every
>> command-line app to get line-editing.
>
>Yeah, but how do you specify completion then?

Same way termcap/termlib would be handled. :)

I was toying with an ioctl or some-such that gave the termcap info to
the driver in one block.  Shouldn't be any harder to run a small daemon
responsible for returning file-name completion info to the driver,
assuming it can't get the info by itself from the file-system layer.

The KL even did command *option* completion.  It partly loaded an
executable - just enough to run its command-line parsing stuff - to
handle expanding options and displaying help.  'Course it cheated on the
termcap/lib stuff.  You could use any terminal as long as it was a
VT100-compatible one.  Pity most OSes don't even match TOPS in many areas.


>Unix went here a long time ago and backed out of it.  Have a look at the
>paper http://www.cs.princeton.edu/~jlk/kornshell/doc/vhll.ps.gz (linked
>from www.kornshell.com) in particular, the history section.

Yeah, I read it, but it doesn't say why they never put it in the driver.
Just that he put it in ksh because the driver work had stalled for
whatever reason.



On Mon, 13 Sep 1999 09:09:52 PDT, Matthew Jacob wrote:
>
>Yeah, and this is why VMS 4.X (early) had a terrific security bug- if you
>type '#' (or was it '&') as the first character after you logged in, your
>accounting records for that session were wiped.

Strawman.  Really, just because one crappy OS has a crappy driver with
one bug is no reason to completely throw out the idea.


>No, a driver is *not* the place to put this kind of fooling around.

But making each and every complex command-line app have to deal with
this itself or link to N different command-line editing libraries *is*
OK?  And why is the driver performing backspace and kill processing and
all sorts of other complicated crap like cooked vs raw?

Either the driver should be really dumb and hand off *everything*
through some user-level filter/app, or it should be capable of doing
everything itself.  Moving vpty handling out of the kernel would be a
good start.


	-- Parag Patel


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 22: 3:23 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201])
	by hub.freebsd.org (Postfix) with SMTP id 423FE1516C
	for <freebsd-hackers@freebsd.org>; Mon, 13 Sep 1999 22:02:58 -0700 (PDT)
	(envelope-from nordwick@scam.xcf.berkeley.edu)
Received: (qmail 40382 invoked by uid 27268); 14 Sep 1999 05:02:40 -0000
Message-ID: <19990914050240.40381.qmail@scam.xcf.berkeley.edu>
To: freebsd-hackers@freebsd.org
Subject: aio_*
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <40380.937285360.1@scam.XCF.Berkeley.EDU>
Date: Mon, 13 Sep 1999 22:02:40 -0700
From: "Jayson Nordwick" <nordwick@scam.xcf.berkeley.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

While reading through (at least trying to... I wish there was some sort of
kernel documentation available, the entry fee is very high) the aio_* calls,
I had a few questions to clear up my understanding: 

1) Do they only work on files?  The only implementation I see is in 
the VFS layer.
  
2) It is my understanding that it uses an aio daemon running as a kernel
thread (the aio_daemon() call kind of give that one away).  It seems as
if this can be almost entirely done in user space.  More important to what
I am trying to do, it seems as if aio_* does not give peak latency     
or throughput performace, since the aio_daemon has to compete for resources
along with all other processes.
   
Should aio_* be used for applications that have high performance
requirements?  What does aio_* get you above having a seperate 
thread pumping in/out data?

-jason



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Mon Sep 13 23:51:22 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from hermes.mixx.net (hermes.mixx.net [194.152.58.71])
	by hub.freebsd.org (Postfix) with ESMTP id D783D14DD7
	for <hackers@FreeBSD.org>; Mon, 13 Sep 1999 23:51:19 -0700 (PDT)
	(envelope-from graichen@innominate.de)
Received: from innominate.de (gatekeeper.innominate.de [212.5.16.129])
	by hermes.mixx.net (8.9.3/8.9.3) with SMTP id IAA19145
	for <hackers@FreeBSD.org>; Tue, 14 Sep 1999 08:51:18 +0200
Received: (qmail 15420 invoked from network); 14 Sep 1999 06:49:46 -0000
Received: from cello.innominate.local (192.168.0.13)
  by lingo01.innominate.local with SMTP; 14 Sep 1999 06:49:46 -0000
Received: from localhost (graichen@localhost)
	by cello.innominate.local (8.9.3/8.9.3) with ESMTP id IAA03358
	for <hackers@FreeBSD.org>; Tue, 14 Sep 1999 08:51:17 +0200 (CEST)
	(envelope-from graichen@innominate.de)
X-Authentication-Warning: cello.innominate.local: graichen owned process doing -bs
Date: Tue, 14 Sep 1999 08:51:16 +0200 (CEST)
From: Thomas Graichen <graichen@innominate.de>
X-Sender: graichen@cello.innominate.local
To: hackers@FreeBSD.org
Subject: SOFTUPDATES and fsck
Message-ID: <Pine.BSF.4.10.9909140849530.3347-100000@cello.innominate.local>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

hello ...

maybe this belongs more to fs than to hackers - but maybe this is
the correct place here for it ...

i've just read the soft updates paper from:

  http://www.ece.cmu.edu/~ganger/papers/CSE-TR-254-95/

at which the soft updates README's in the FreeBSD tree point and ran
across the following lines in the section 5.1 "file system recovery":

"With the conventional implementation, the fsck utility must be run on
a file system before it can be mounted after any system failure. By
guarateeing that the on-disk metadata can always be used safely (except
when media corruption destroys live metadata), our soft updates im-
plementation lifts this requirement. A file system can be safely
mounted and used immedeately after most system failures, but may
contain several inconsistencies:

* unused blocks may not appear in the free space maps

* inode link counts may exceed the numer of associated directory
  entries

* unreferenced inodes may not appear in the free inode maps

One can run the fsck utility on the filesystem, when convenient, to
reclaim unreferenced ressources and correct link counts. ..."

at another point it is mentioned that it should be doable to write
an fsck tool which can do those corrections in background while the
filesystem is mountet read/write ...

now my question: how much of this applies to the soft updates im-
plementation in FreeBSD ? - might this eventually open the door
to an fsck free bootup after a system crash without having to
write a journaled filesystem for FreeBSD ? - i think this is
one point which gets more and more important on systems with
several 100 gb disk space and thus enormous fsck times after
a failure

can anyone - who is deep in the details of the FreeBSD soft updates
implementation (julian, matt, kirk) give some comments on this ?

a lot of thanks in advance

t

-- 
graichen@innominate.de
                                                        innominate AG
                                                    networking people
fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  0:52:50 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71])
	by hub.freebsd.org (Postfix) with ESMTP
	id 980F614F91; Tue, 14 Sep 1999 00:52:02 -0700 (PDT)
	(envelope-from stas@sonet.crimea.ua)
Received: (from stas@localhost)
	by sonet.crimea.ua (8.8.8/8.8.8) id KAA08988;
	Tue, 14 Sep 1999 10:50:43 +0400 (MSD)
	(envelope-from stas)
Date: Tue, 14 Sep 1999 10:50:43 +0400 (MSD)
From: Stas Kisel <stas@sonet.crimea.ua>
Message-Id: <199909140650.KAA08988@sonet.crimea.ua>
To: bmilekic@dsuper.net, wollman@khavrinen.lcs.mit.edu
Subject: Re: mbuf shortage situations (followup)
Cc: avalon@coombs.anu.edu.au, freebsd-hackers@FreeBSD.ORG,
	freebsd-security@FreeBSD.ORG, stas@sonet.crimea.ua
In-Reply-To: <199909131840.OAA31048@khavrinen.lcs.mit.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> From wollman@khavrinen.lcs.mit.edu Mon Sep 13 22:39:37 1999
> > 	I'm also aware of the possiblity of some people not liking the
> > fact that we tsleep() forever (e.g. tsleep(x,x,x,0)). 
>
> I don't have any problem with sleeping forever -- but I am concerned
> about the possibility of deadlock, especially when client-NFS is
> involved.  If the problem just moves around and has harder-to-recover
> symptoms, the change isn't helping.

IMHO merely sleeping can't help if we deal with a DoS. Instead of
sleeping, kernel should find out where all kernel memory is wasted
and free some memory (and, probably, remove/log reason). And, partially,
this mechanism is already implemented in ip_drain() and tp_drain().

--
Stas Kisel. UNIX, security, C, TCP/IP, Web. UNIX - the best adventure game
http://www.tekmetrics.com/transcript.shtml?pid=20053 http://www.crimea.edu
+380(652)510222,230238 ; stas@crimea.edu stas@sonet.crimea.ua ; 2:460/54.4



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  1: 5:38 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP id B4E3314F91
	for <hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 01:05:36 -0700 (PDT)
	(envelope-from julian@whistle.com)
Received: from home.elischer.org (home.elischer.org [207.76.204.203])
	by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id BAA98152;
	Tue, 14 Sep 1999 01:05:30 -0700 (PDT)
Date: Tue, 14 Sep 1999 01:05:39 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@home.elischer.org
To: Thomas Graichen <graichen@innominate.de>
Cc: hackers@FreeBSD.ORG
Subject: Re: SOFTUPDATES and fsck
In-Reply-To: <Pine.BSF.4.10.9909140849530.3347-100000@cello.innominate.local>
Message-ID: <Pine.BSF.4.05.9909140059310.10150-100000@home.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Tue, 14 Sep 1999, Thomas Graichen wrote:

> hello ...
> 
> maybe this belongs more to fs than to hackers - but maybe this is
> the correct place here for it ...
> 
> i've just read the soft updates paper from:
> 
>   http://www.ece.cmu.edu/~ganger/papers/CSE-TR-254-95/
> 
> at which the soft updates README's in the FreeBSD tree point and ran
> across the following lines in the section 5.1 "file system recovery":
> 
> "With the conventional implementation, the fsck utility must be run on
> a file system before it can be mounted after any system failure. By
> guarateeing that the on-disk metadata can always be used safely (except
> when media corruption destroys live metadata), our soft updates im-
> plementation lifts this requirement. A file system can be safely
> mounted and used immedeately after most system failures, but may
> contain several inconsistencies:
> 
> * unused blocks may not appear in the free space maps
> 
> * inode link counts may exceed the numer of associated directory
>   entries
> 
> * unreferenced inodes may not appear in the free inode maps
> 
> One can run the fsck utility on the filesystem, when convenient, to
> reclaim unreferenced ressources and correct link counts. ..."
> 
> at another point it is mentioned that it should be doable to write
> an fsck tool which can do those corrections in background while the
> filesystem is mountet read/write ...
> 
> now my question: how much of this applies to the soft updates im-
> plementation in FreeBSD ? - might this eventually open the door
> to an fsck free bootup after a system crash without having to
> write a journaled filesystem for FreeBSD ? - i think this is
> one point which gets more and more important on systems with
> several 100 gb disk space and thus enormous fsck times after
> a failure
> 
> can anyone - who is deep in the details of the FreeBSD soft updates
> implementation (julian, matt, kirk) give some comments on this ?

The trouble is that any fsck is a user process, and can not therefore get
an single instantanious snapshot of the filesystem.
teh delays make it impossible to do this 'online background' fsck without
serious risk of actually freeing blocks that the filesystem is busy
marking in use, due to race conditions....

Kirk is working on this. His scheme is to actually checkpoint the
filesystem, and record all metadata changes that occur after the
checkpoint, in a file INSTEAD OF in the filesystem.
the result is that the filesystem is in effect frozen, even though
metadata changes are happenning.
tehn when the fsck complets and the filesystem is marked clean,
all updates in the log file are played back into the live filesystem,
so that it 'catches up'. When all logged actions have been played out, 
then the filesystem is 'unfrozen' and continues a sper normal.
New metadata actions occuring while the log is being replayed
might be placed on the end of the log, or allowed directly into the
filesystem. I don't know which....


julian


> 
> a lot of thanks in advance
> 
> t
> 
> -- 
> graichen@innominate.de
>                                                         innominate AG
>                                                     networking people
> fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  1:40:19 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id 9DF9B15672
	for <freebsd-hackers@freebsd.org>; Tue, 14 Sep 1999 01:40:15 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA85298;
	Tue, 14 Sep 1999 09:41:22 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Tue, 14 Sep 1999 09:41:22 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Zhihui Zhang <zzhang@cs.binghamton.edu>
Cc: freebsd-hackers@freebsd.org
Subject: Re: NFS authentication
In-Reply-To: <Pine.GSO.3.96.990913193434.10215A-100000@sol.cs.binghamton.edu>
Message-ID: <Pine.BSF.4.10.9909140933460.333-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 13 Sep 1999, Zhihui Zhang wrote:

> 
> I am wondering where the NFS authentication is done in FreeBSD. Is it done
> by the NFS daemon mountd (or other daemon) or within the kernel?  Can
> anyone give me a pointer?  Thanks a lot. 

Kerberos authentication is done by nfsd. The kernel returns ENEEDAUTH from
the nfssvc() call and nfsd does the authentication, passing the results
back via nfssvc(). I don't think this code is actually used by anyone so
there is a strong possibility that it doesn't work at all.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  2:21: 0 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
	by hub.freebsd.org (Postfix) with ESMTP id 4228E156E2
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 02:20:57 -0700 (PDT)
	(envelope-from bright@wintelcom.net)
Received: from localhost (bright@localhost)
	by fw.wintelcom.net (8.8.8/8.8.8) with ESMTP id TAA15372;
	Mon, 13 Sep 1999 19:39:37 -0700 (PDT)
	(envelope-from bright@wintelcom.net)
Date: Tue, 14 Sep 1999 02:39:37 +0000 (GMT)
From: Alfred Perlstein <bright@wintelcom.net>
To: Doug Rabson <dfr@nlsystems.com>
Cc: Zhihui Zhang <zzhang@cs.binghamton.edu>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: NFS authentication
In-Reply-To: <Pine.BSF.4.10.9909140933460.333-100000@salmon.nlsystems.com>
Message-ID: <Pine.BSF.4.05.9909140238080.6392-100000@fw.wintelcom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Tue, 14 Sep 1999, Doug Rabson wrote:

> On Mon, 13 Sep 1999, Zhihui Zhang wrote:
> 
> > 
> > I am wondering where the NFS authentication is done in FreeBSD. Is it done
> > by the NFS daemon mountd (or other daemon) or within the kernel?  Can
> > anyone give me a pointer?  Thanks a lot. 
> 
> Kerberos authentication is done by nfsd. The kernel returns ENEEDAUTH from
> the nfssvc() call and nfsd does the authentication, passing the results
> back via nfssvc(). I don't think this code is actually used by anyone so
> there is a strong possibility that it doesn't work at all.

nfs_socket.c:#ifdef NFSKERB
nfs_socket.c-                   XXX
nfs_socket.c-#endif

There is some work already there, it's just incomplete.

-Alfred



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  2:26:54 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id 11DE815765
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 02:26:46 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA28993;
	Tue, 14 Sep 1999 10:28:00 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Tue, 14 Sep 1999 10:28:00 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Alfred Perlstein <bright@wintelcom.net>
Cc: Zhihui Zhang <zzhang@cs.binghamton.edu>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: NFS authentication
In-Reply-To: <Pine.BSF.4.05.9909140238080.6392-100000@fw.wintelcom.net>
Message-ID: <Pine.BSF.4.10.9909141027290.333-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 14 Sep 1999, Alfred Perlstein wrote:

> 
> On Tue, 14 Sep 1999, Doug Rabson wrote:
> 
> > On Mon, 13 Sep 1999, Zhihui Zhang wrote:
> > 
> > > 
> > > I am wondering where the NFS authentication is done in FreeBSD. Is it done
> > > by the NFS daemon mountd (or other daemon) or within the kernel?  Can
> > > anyone give me a pointer?  Thanks a lot. 
> > 
> > Kerberos authentication is done by nfsd. The kernel returns ENEEDAUTH from
> > the nfssvc() call and nfsd does the authentication, passing the results
> > back via nfssvc(). I don't think this code is actually used by anyone so
> > there is a strong possibility that it doesn't work at all.
> 
> nfs_socket.c:#ifdef NFSKERB
> nfs_socket.c-                   XXX
> nfs_socket.c-#endif
> 
> There is some work already there, it's just incomplete.

I have a feeling that it was once complete but was ripped out for
crypto-export reasons.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  3:50: 1 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from not.demophon.com (ns.demophon.com [193.65.70.13])
	by hub.freebsd.org (Postfix) with ESMTP id D94A7150BE
	for <hackers@freebsd.org>; Tue, 14 Sep 1999 03:49:57 -0700 (PDT)
	(envelope-from will@not.demophon.com)
Received: (from will@localhost)
	by not.demophon.com (8.9.3/8.8.7) id NAA34462;
	Tue, 14 Sep 1999 13:49:46 +0300 (EEST)
	(envelope-from will)
To: nordwick@scam.xcf.berkeley.edu (Jayson Nordwick)
Cc: hackers@freebsd.org
Subject: Re: aio_*
References: <19990914050240.40381.qmail@scam.xcf.berkeley.edu>
From: Ville-Pertti Keinonen <will@iki.fi>
Date: 14 Sep 1999 13:49:45 +0300
In-Reply-To: nordwick@scam.xcf.berkeley.edu's message of "14 Sep 1999 08:03:55 +0300"
Message-ID: <867lltix86.fsf@not.demophon.com>
Lines: 32
X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


nordwick@scam.xcf.berkeley.edu (Jayson Nordwick) writes:

> While reading through (at least trying to... I wish there was some sort of
> kernel documentation available, the entry fee is very high) the aio_* calls,
> I had a few questions to clear up my understanding: 

> 1) Do they only work on files?  The only implementation I see is in 
> the VFS layer.

AIO is not in the VFS layer.  The source file containing the
implementation is improperly named.

It works on any file descriptor that you could do the equivalent
read(2)/write(2) calls on.

> 2) It is my understanding that it uses an aio daemon running as a kernel
> thread (the aio_daemon() call kind of give that one away).  It seems as
> if this can be almost entirely done in user space.  More important to what
> I am trying to do, it seems as if aio_* does not give peak latency     
> or throughput performace, since the aio_daemon has to compete for resources
> along with all other processes.

> Should aio_* be used for applications that have high performance
> requirements?  What does aio_* get you above having a seperate 
> thread pumping in/out data?

The implementation in FreeBSD probably isn't a particularly efficient
one.

It should be faster than threads, though.  You'll need fewer switches
between user and kernel mode and synchronization is simpler.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  5:11:30 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id CFDCA151A2
	for <hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 05:11:23 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.3) id OAA21812;
	Tue, 14 Sep 1999 14:11:18 +0200 (CEST)
	(envelope-from des)
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Cc: Gustavo V G C Rios <grios@ddsecurity.com.br>, hackers@FreeBSD.ORG
Subject: Re: submiting source code ?
References: <37D86506.4247EF3A@ddsecurity.com.br> <19990913090318.F89309@daemon.ninth-circle.org>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 14 Sep 1999 14:11:18 +0200
In-Reply-To: Jeroen Ruigrok/Asmodai's message of "Mon, 13 Sep 1999 09:03:18 +0200"
Message-ID: <xzpbtb5zo9l.fsf@flood.ping.uio.no>
Lines: 8
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> writes:
> The Unix Programming Environment by Rob Pike and Ritchie Kerninghan

Ritchie Kernighan? Who's Ritchie Kernighan?

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  6:37:15 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from ddsecurity.com.br (vitoria.ddsecurity.com.br [200.18.130.93])
	by hub.freebsd.org (Postfix) with SMTP id 17FA215094
	for <hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 06:37:07 -0700 (PDT)
	(envelope-from grios@ddsecurity.com.br)
Received: (qmail 70305 invoked by uid 1001); 14 Sep 1999 13:37:06 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 14 Sep 1999 13:37:06 -0000
Date: Tue, 14 Sep 1999 10:37:06 -0300 (EST)
From: Gustavo Rios <grios@ddsecurity.com.br>
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>, hackers@FreeBSD.ORG
Subject: Re: submiting source code ?
In-Reply-To: <xzpbtb5zo9l.fsf@flood.ping.uio.no>
Message-ID: <Pine.BSF.4.10.9909141036220.70296-100000@vitoria.ddsecurity.com.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Shouldn't it be Dennis Ritchie or Brian Kernigham ?

--
What's the similarity between an air
conditioner and a computer? They both
stop working when you open windows.

On 14 Sep 1999, Dag-Erling Smorgrav wrote:

> Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> writes:
> > The Unix Programming Environment by Rob Pike and Ritchie Kerninghan
> 
> Ritchie Kernighan? Who's Ritchie Kernighan?
> 
> DES
> -- 
> Dag-Erling Smorgrav - des@flood.ping.uio.no
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  6:37:44 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from ddsecurity.com.br (vitoria.ddsecurity.com.br [200.18.130.93])
	by hub.freebsd.org (Postfix) with SMTP id CC35F14C57
	for <hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 06:36:31 -0700 (PDT)
	(envelope-from grios@ddsecurity.com.br)
Received: (qmail 70298 invoked by uid 1001); 14 Sep 1999 13:36:15 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 14 Sep 1999 13:36:15 -0000
Date: Tue, 14 Sep 1999 10:36:15 -0300 (EST)
From: Gustavo Rios <grios@ddsecurity.com.br>
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>, hackers@FreeBSD.ORG
Subject: Re: submiting source code ?
In-Reply-To: <xzpbtb5zo9l.fsf@flood.ping.uio.no>
Message-ID: <Pine.BSF.4.10.9909141035570.70296-100000@vitoria.ddsecurity.com.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I don't know ether!

--
What's the similarity between an air
conditioner and a computer? They both
stop working when you open windows.

On 14 Sep 1999, Dag-Erling Smorgrav wrote:

> Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> writes:
> > The Unix Programming Environment by Rob Pike and Ritchie Kerninghan
> 
> Ritchie Kernighan? Who's Ritchie Kernighan?
> 
> DES
> -- 
> Dag-Erling Smorgrav - des@flood.ping.uio.no
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  6:42:56 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from ddsecurity.com.br (vitoria.ddsecurity.com.br [200.18.130.93])
	by hub.freebsd.org (Postfix) with SMTP id DD1891518E
	for <hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 06:38:18 -0700 (PDT)
	(envelope-from grios@ddsecurity.com.br)
Received: (qmail 70328 invoked by uid 1001); 14 Sep 1999 13:38:14 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 14 Sep 1999 13:38:14 -0000
Date: Tue, 14 Sep 1999 10:38:14 -0300 (EST)
From: Gustavo Rios <grios@ddsecurity.com.br>
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>, hackers@FreeBSD.ORG
Subject: Re: submiting source code ?
In-Reply-To: <xzpbtb5zo9l.fsf@flood.ping.uio.no>
Message-ID: <Pine.BSF.4.10.9909141037300.70324-100000@vitoria.ddsecurity.com.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ops, now i know, Ritchie Kernigham is the son of Brian and Dennis!

--
What's the similarity between an air
conditioner and a computer? They both
stop working when you open windows.

On 14 Sep 1999, Dag-Erling Smorgrav wrote:

> Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> writes:
> > The Unix Programming Environment by Rob Pike and Ritchie Kerninghan
> 
> Ritchie Kernighan? Who's Ritchie Kernighan?
> 
> DES
> -- 
> Dag-Erling Smorgrav - des@flood.ping.uio.no
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  7:48:16 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from ockle.nanoteq.co.za (ockle.nanoteq.co.za [196.37.91.54])
	by hub.freebsd.org (Postfix) with ESMTP
	id A074315297; Tue, 14 Sep 1999 07:47:55 -0700 (PDT)
	(envelope-from jkruger@oskar.nanoteq.co.za)
Received: from oskar.nanoteq.co.za (localhost.nanoteq.co.za [127.0.0.1])
	by ockle.nanoteq.co.za (8.9.3/8.9.3) with ESMTP id QAA00883;
	Tue, 14 Sep 1999 16:45:23 +0200 (SAST)
	(envelope-from jkruger@oskar.nanoteq.co.za)
Message-ID: <37DE5F82.92A87782@oskar.nanoteq.co.za>
Date: Tue, 14 Sep 1999 16:45:22 +0200
From: Johan Kruger <jkruger@oskar.nanoteq.co.za>
Reply-To: jkruger@oskar.nanoteq.co.za
Organization: Nanoteq
X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-STABLE-990722 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
Subject: Custom boot.flp
Content-Type: multipart/mixed;
 boundary="------------DDFFC85A344002AED0D1217E"
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a multi-part message in MIME format.
--------------DDFFC85A344002AED0D1217E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I mounted the boot.flp image and replaced kernel.gz with my own, for use
of bootable CD.
I don't want the default sysinstall ( presumably compiled into the
kernel ) to come up on screen, instead i want a command prompt only. I
will insert my scripts into .profile.
The PROBLEM is that i get the message mounting root on fd0c while i am
actually booting from CDROM. In my kernel the default root device is
wd0, but i tried to change kernel root to acd0 , and to no avail.

I get :
----------------------
Mounting root device on fd0c
error mounting root on fd0c
-- will reboot in 15 seconds -- bla bla
----------------------
How do i tell it to mount it on CDROM ( probably wcd0a ) say for
instance /MYMOUNT_DIR ??
--------------DDFFC85A344002AED0D1217E
Content-Type: text/x-vcard; charset=us-ascii;
 name="jkruger.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Johan Kruger
Content-Disposition: attachment;
 filename="jkruger.vcf"

begin:vcard 
n:Kruger;Johan
tel;cell:+27 83 3015923
tel;fax:+27 12 6651343
tel;home:+27 83 3015923
tel;work:+27 12 6651338
x-mozilla-html:FALSE
org:Nanoteq;Development
version:2.1
email;internet:jkruger@oskar.nanoteq.co.za
title:Mr
adr;quoted-printable:;;P.O BOX 12872=0D=0AOnderstepoort=0D=0A0110=0D=0ASouth Africa;Pretoria;Gauteng;0110;South Africa
x-mozilla-cpt:;0
fn:Johan Kruger
end:vcard

--------------DDFFC85A344002AED0D1217E--



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  7:49: 7 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from fanf.noc.demon.net (fanf.noc.demon.net [195.11.55.83])
	by hub.freebsd.org (Postfix) with ESMTP id 25E55150E8
	for <hackers@freebsd.org>; Tue, 14 Sep 1999 07:49:04 -0700 (PDT)
	(envelope-from fanf@demon.net)
Received: from fanf by fanf.noc.demon.net with local (Exim 3.02 #13)
	id 11QttA-000E4G-00; Tue, 14 Sep 1999 15:48:56 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Tony Finch <fanf@demon.net>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Tony Finch <fanf@demon.net>, hackers@FreeBSD.ORG
Subject: Re: mounting a partition more than once
In-Reply-To: <199909140504.WAA27333@apollo.backplane.com>
References: <E11QZ03-000DDr-00@fanf.noc.demon.net>
	<199909132116.OAA25920@apollo.backplane.com>
	<E11Qe1j-000DRT-00@fanf.noc.demon.net>
	<199909140504.WAA27333@apollo.backplane.com>
X-Mailer: VM 6.34 under Emacs 19.34.1
Message-Id: <E11QttA-000E4G-00@fanf.noc.demon.net>
Date: Tue, 14 Sep 1999 15:48:56 +0100
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Matthew Dillon <dillon@apollo.backplane.com> wrote:
> Tony Finch <fanf@demon.net> wrote:
> :Matthew Dillon <dillon@apollo.backplane.com> wrote:
> :>
> :>     Also, this may not be the best place to put the code.  It make sense
> :>     to be able to mount a block device multiple times in a read-only
> :>     fashion, but the code should be in the open for the block device
> :>     rather then in UFS/FFS, so it can be used with other filesystems
> :>     and for other purposes.
> :
> :Yes, it's evident that this is true because I had to hack around
> :essentially the same test in both spec_open and ffs_mountfs; removing
> :the checks down from ffs_mountfs so it relies on spec_mount to DTRT
> :would be neater, I think.
> 
>     Yes.  I think this is the right track to take.  The result will be
>     more useful to the system and probably a cleaner patch as well.

I found some problems with the patch last night (after some
suggestions from a colleague). There needs to be some additional
checking at the level of the syscall code, I think, to prevent
mounting the same partition at the same point more than once -- this
causes a "lockmgr: locking against myself" panic when unmounting. I
also missed out some checks from the remount code...

Tony.
-- 
f.a.n.finch    dot@dotat.at    fanf@demon.net    e pluribus unix


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  8:41:57 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from biggusdiskus.flyingfox.com (parker-T1-2-gw.sf3d.best.net [209.157.165.30])
	by hub.freebsd.org (Postfix) with ESMTP id 2C43714BFD
	for <hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 08:41:55 -0700 (PDT)
	(envelope-from jas@flyingfox.com)
Received: (from jas@localhost)
	by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id JAA06487;
	Tue, 14 Sep 1999 09:31:46 -0700 (PDT)
Date: Tue, 14 Sep 1999 09:31:46 -0700 (PDT)
From: Jim Shankland <jas@flyingfox.com>
Message-Id: <199909141631.JAA06487@biggusdiskus.flyingfox.com>
To: des@flood.ping.uio.no, grios@ddsecurity.com.br
Subject: Re: submiting source code ?
Cc: asmodai@wxs.nl, hackers@FreeBSD.ORG
In-Reply-To: <Pine.BSF.4.10.9909141037300.70324-100000@vitoria.ddsecurity.com.br>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Ops, now i know, Ritchie Kernigham is the son of Brian and Dennis!

Illegitimate offspring.  Banished after proposing the addition
of the "noalias" keyword to C.

Jim Shankland
NLynx Systems, Inc.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  8:51: 0 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32])
	by hub.freebsd.org (Postfix) with ESMTP id 43D121516A
	for <hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 08:50:58 -0700 (PDT)
	(envelope-from dwhite@resnet.uoregon.edu)
Received: from localhost (dwhite@localhost)
	by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id IAA68411;
	Tue, 14 Sep 1999 08:49:21 -0700 (PDT)
	(envelope-from dwhite@resnet.uoregon.edu)
Date: Tue, 14 Sep 1999 08:49:21 -0700 (PDT)
From: Doug White <dwhite@resnet.uoregon.edu>
To: Ruslan Ermilov <ru@ucb.crimea.ua>
Cc: hackers@FreeBSD.ORG
Subject: Re: Multiple NAT alias addresses
In-Reply-To: <19990914040220.B71293@relay.ucb.crimea.ua>
Message-ID: <Pine.BSF.4.10.9909140846130.65695-100000@resnet.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 14 Sep 1999, Ruslan Ermilov wrote:

> > hello ..
> > 
> > We're trying to turn up a firewall box running NAT with multiple external
> > IPs.  I added the alias and set up natd.conf as follows:
> > 
> > use_sockets yes
> > same_ports yes
> > #
> > # machine1 redirections 
> > #redirect_port tcp 192.168.2.237:ssh 1.2.3.4:ssh
> > #redirect_port tcp 192.168.2.237:smtp 1.2.3.4:smtp
> > #redirect_port tcp 192.168.2.237:pop3 1.2.3.4:pop3
> > #redirect_port tcp 192.168.2.237:imap4 1.2.3.4:imap4
> > 
> > # machine2 redirections
> > redirect_port tcp 192.168.2.201:ssh 1.2.3.5:ssh
> > redirect_port tcp 192.168.2.201:http 1.2.3.5:http
> > 
> > I start natd with:
> > 
> > natd -f /etc/natd.conf -n fxp0  where fxp0 is the public-side interface.
> > 
> > Restarting natd with this configuration causes it to block everything.
> > 
> So, without redirect_port's it works OK?

Yes, and the redirect_port's work if the alias address is not specified.

> Have you tried to run it in the foreground? (`natd -v')

Not on the target machine but I did test it from home.  It looks like NAT
stops matching packets when the alias addr is provided; it lets them fall
through to the local system, where they generally get 'connection
refused'.  I am going to try it without alias addresses for the default
address (the first bank) and see if those work.

I can't attach gdb to a running -g'd version of natd, it just segfaults.
:(

> > Does natd support multiple alias addresses, or am I missing something
> > obvious?
> > 
> Definitely supports!
> 
> BTW, what version you are on?

3.2-RELEASE.

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-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  8:59:39 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
	by hub.freebsd.org (Postfix) with ESMTP id 7FCBD14CA8
	for <freebsd-hackers@freebsd.org>; Tue, 14 Sep 1999 08:59:36 -0700 (PDT)
	(envelope-from aron@cs.rice.edu)
Received: (from aron@localhost)
	by cs.rice.edu (8.9.0/8.9.0) id KAA05204
	for freebsd-hackers@freebsd.org; Tue, 14 Sep 1999 10:59:35 -0500 (CDT)
From: Mohit Aron <aron@cs.rice.edu>
Message-Id: <199909141559.KAA05204@cs.rice.edu>
Subject: fxp driver for alpha
To: freebsd-hackers@freebsd.org
Date: Tue, 14 Sep 1999 10:59:35 -0500 (CDT)
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-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,
	I'm using the latest available snapshot (4.0-19990808-CURRENT) for
an Alphaserver 500 workstation. Unfortunately, this version of FreeBSD 
panics upon seeing an fxp network interface. Does anyone have an updated driver
for the Alpha that supports the fxp interface ?

There is also a "de" interface on the Alpha that works with FreeBSD but the
performance is rather dismal. A webserver running on the machine gives only
120 req/s on this machine (as opposed to 800 req/s on a Pentium III). Moreover,
most of the time the OS shows that its idle - looks like the problem lies in
the "de" driver. An updated de driver would also be appreciated.


- Mohit


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  9:10:31 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
	by hub.freebsd.org (Postfix) with SMTP
	id 17A86151E9; Tue, 14 Sep 1999 09:10:19 -0700 (PDT)
	(envelope-from wpaul@skynet.ctr.columbia.edu)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id MAA19753; Tue, 14 Sep 1999 12:12:25 -0400
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199909141612.MAA19753@skynet.ctr.columbia.edu>
Subject: Call for testers: Aironet wireless adapters
To: hackers@freebsd.org, hardware@freebsd.org
Date: Tue, 14 Sep 1999 12:12:23 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 3086      
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a call for testers for users with Aironet 4500 or 4800 series
wireless adapters. A device driver for these NICs is now available.
PCMCIA, PCI and ISA devices should all be supported. Note however that
I personally only have access to the 4800 series cards so I may have
missed some of the PCI and/or ISA Plug and Play IDs for the 4500 cards.

The Aironet cards are 802.11 devices. The 4500 series cards have a maximum
data rate of 2Mbps. The 4800 series have a maximum speed of 11Mbps, or so
they claim. In my tests, I tend to see around 600KB/sec (kilobytes per
second). This is in ad-hoc mode only; I don't know if infrastructure mode
would be faster since I don't have an access point.

Driver support is currently available for FreeBSD 3.2 and up. I plan
to make a 4.0 driver once the plug and play code in -current settles down
a little. The driver is available aT:

	http://www.freebsd.org/~wpaul/Aironet

There is a README which explains how to add the driver to an existing
system and configure a new kernel. Pay careful attention to the step
marked *IMPORTANT* if you have a PCMCIA card: you must make a small
change to /sys/pccard/pccard.c in order to get the PCMCIA card activated
correctly (you have to apply +5 volts to the vpp1 and vpp2 pins, which
FreeBSD doesn't do by default).

The Aironet ISA and PCI cards appear to the host as ordinary ISA or PCI
devices. This is a big improvement over the WaveLAN/IEEE ISA card which
looks like a PCMCIA controller with a PCMCIA card inserted, and required
pccard support even on a desktop system. The ISA card can be set for Plug
and Play mode or hard-wired to a particular I/O address or IRQ; the driver
supports both modes. If your system supports ISA Plug and Play devices,
then it should "just work" without any tweaking.

Sharp-eyed readers may notice a striking similarity between the Aironet
driver code and the WaveLAN code. Strangely, they have very similar
programming interfaces. I don't know why.

Note that the Aironet supports multicast reception, but it has no
multicast filter: the only possible option is 'receive all multicasts'
mode. Also, promiscuous mode only seems to work when the NIC is in
infrastructure mode, not in ad-hoc mode. Also, unlike the WaveLAN/IEEE
cards, Aironet stations in ad-hoc mode must be on the same SSID in order
to communicate. This can be done with the ancontrol utility (i.e.
ancontrol -i an0 -n "MY_NETWORK").

As usual, report problems or send free large bags of cash to
wpaul@skynet.columbia.edu. Include lots of details.

-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-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  9:27:17 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1])
	by hub.freebsd.org (Postfix) with ESMTP id B4669152D5
	for <hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 09:26:07 -0700 (PDT)
	(envelope-from ru@ucb.crimea.ua)
Received: (from ru@localhost)
	by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id TAA11619;
	Tue, 14 Sep 1999 19:23:36 +0300 (EEST)
	(envelope-from ru)
Date: Tue, 14 Sep 1999 19:23:36 +0300
From: Ruslan Ermilov <ru@ucb.crimea.ua>
To: Doug White <dwhite@resnet.uoregon.edu>
Cc: hackers@FreeBSD.ORG
Subject: Re: Multiple NAT alias addresses
Message-ID: <19990914192335.A3257@relay.ucb.crimea.ua>
Mail-Followup-To: Doug White <dwhite@resnet.uoregon.edu>,
	hackers@FreeBSD.ORG
References: <19990914040220.B71293@relay.ucb.crimea.ua> <Pine.BSF.4.10.9909140846130.65695-100000@resnet.uoregon.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <Pine.BSF.4.10.9909140846130.65695-100000@resnet.uoregon.edu>; from Doug White on Tue, Sep 14, 1999 at 08:49:21AM -0700
X-Operating-System: FreeBSD 3.2-STABLE i386
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Sep 14, 1999 at 08:49:21AM -0700, Doug White wrote:
> On Tue, 14 Sep 1999, Ruslan Ermilov wrote:
> 
> > > hello ..
> > > 
> > > We're trying to turn up a firewall box running NAT with multiple external
> > > IPs.  I added the alias and set up natd.conf as follows:
> > > 
> > > use_sockets yes
> > > same_ports yes
> > > #
> > > # machine1 redirections 
> > > #redirect_port tcp 192.168.2.237:ssh 1.2.3.4:ssh
> > > #redirect_port tcp 192.168.2.237:smtp 1.2.3.4:smtp
> > > #redirect_port tcp 192.168.2.237:pop3 1.2.3.4:pop3
> > > #redirect_port tcp 192.168.2.237:imap4 1.2.3.4:imap4
> > > 
> > > # machine2 redirections
> > > redirect_port tcp 192.168.2.201:ssh 1.2.3.5:ssh
> > > redirect_port tcp 192.168.2.201:http 1.2.3.5:http
> > > 
> > > I start natd with:
> > > 
> > > natd -f /etc/natd.conf -n fxp0  where fxp0 is the public-side interface.
> > > 
> > > Restarting natd with this configuration causes it to block everything.
> > > 
> > So, without redirect_port's it works OK?
> 
> Yes, and the redirect_port's work if the alias address is not specified.
> 
Strange, I just run 3.2-RELEASE's natd(8) with your configuration file
and everything works as expected:

Firewall rules were:
00001 divert 8668 ip from any to 1.2.3.5 via fxp2
00001 divert 8668 ip from 192.168.2.201 to any via fxp2

Natd(8) was run as:
natd -v -f natd.cf -n fxp2 (fxp2 in an external interface)


telnet 1.2.3.5 123 (from 212.110.138.4):
In  [TCP]  [TCP] 212.110.138.4:49964 -> 1.2.3.5:123 aliased to
           [TCP] 212.110.138.4:49964 -> 1.2.3.5:123
In  [TCP]  [TCP] 212.110.138.4:49964 -> 1.2.3.5:123 aliased to
           [TCP] 212.110.138.4:49964 -> 1.2.3.5:123
In  [TCP]  [TCP] 212.110.138.4:49964 -> 1.2.3.5:123 aliased to
           [TCP] 212.110.138.4:49964 -> 1.2.3.5:123
Redirections not happening.



telnet 1.2.3.5 80 (from 212.110.138.4):
In  [TCP]  [TCP] 212.110.138.4:49960 -> 1.2.3.5:80 aliased to
           [TCP] 212.110.138.4:49960 -> 192.168.2.201:80
Out [TCP]  [TCP] 192.168.2.201:80 -> 212.110.138.4:49960 aliased to
           [TCP] 1.2.3.5:80 -> 212.110.138.4:49960
In  [TCP]  [TCP] 212.110.138.4:49960 -> 1.2.3.5:80 aliased to
           [TCP] 212.110.138.4:49960 -> 192.168.2.201:80
In  [TCP]  [TCP] 212.110.138.4:49960 -> 1.2.3.5:80 aliased to
           [TCP] 212.110.138.4:49960 -> 192.168.2.201:80
Out [TCP]  [TCP] 192.168.2.201:80 -> 212.110.138.4:49960 aliased to
           [TCP] 1.2.3.5:80 -> 212.110.138.4:49960
Out [TCP]  [TCP] 192.168.2.201:80 -> 212.110.138.4:49960 aliased to
           [TCP] 1.2.3.5:80 -> 212.110.138.4:49960
In  [TCP]  [TCP] 212.110.138.4:49960 -> 1.2.3.5:80 aliased to
           [TCP] 212.110.138.4:49960 -> 192.168.2.201:80
Redirections are happening.



> > Have you tried to run it in the foreground? (`natd -v')
> 
> Not on the target machine but I did test it from home.  It looks like NAT
> stops matching packets when the alias addr is provided; it lets them fall
> through to the local system, where they generally get 'connection
> refused'.  I am going to try it without alias addresses for the default
> address (the first bank) and see if those work.
> 
> I can't attach gdb to a running -g'd version of natd, it just segfaults.
> :(
> 
This is a known problem, it is fixed in -STABLE:

dfr         1999/05/22 01:29:24 PDT

  Modified files:        (Branch: RELENG_3)
    contrib/gdb/gdb      solib.c
  Log:
  MFC: Problems with coredumps from static programs.

  Revision  Changes    Path
  1.3.2.2   +1 -1      src/contrib/gdb/gdb/solib.c



-- 
Ruslan Ermilov		Sysadmin and DBA of the
ru@ucb.crimea.ua	United Commercial Bank,
ru@FreeBSD.org		FreeBSD committer,
+380.652.247.647	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14  9:39:53 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58])
	by hub.freebsd.org (Postfix) with ESMTP id E736F15264
	for <freebsd-hackers@freebsd.org>; Tue, 14 Sep 1999 09:39:44 -0700 (PDT)
	(envelope-from Dom.Mitchell@palmerharvey.co.uk)
Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk
 (Content Technologies SMTPRS 4.0.1) with ESMTP id <B3eac6d3a4749ad3db1@mail.palmerharvey.co.uk>;
 Tue, 14 Sep 1999 17:39:28 +0100
Received: from voodoo.pandhm.co.uk (10.100.35.12 [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id SNZVM3S1; Tue, 14 Sep 1999 17:38:21 +0100
Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1)
	id 11QvcE-0004o3-00; Tue, 14 Sep 1999 17:39:34 +0100
Date: Tue, 14 Sep 1999 17:39:34 +0100
To: Parag Patel <parag@cgt.com>
Cc: "Matthew N. Dodd" <winter@jurai.net>,
	Daniel O'Connor <darius@dons.net.au>, freebsd-hackers@FreeBSD.ORG
Subject: Re: Command-line editing [was NetWare client in -current]
Message-ID: <19990914173933.B17847@voodoo.pandhm.co.uk>
References: <Dom.Mitchell@palmerharvey.co.uk> <2138.937280099@pinhead.parag.codegen.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <2138.937280099@pinhead.parag.codegen.com>
From: Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Sep 13, 1999 at 08:34:59PM -0700, Parag Patel wrote:
> On Mon, 13 Sep 1999 09:23:36 BST, Dominic Mitchell wrote:
> >
> >On Fri, Sep 10, 1999 at 11:15:12AM -0700, Parag Patel wrote:
> >> Growing up programming on a KL-10, I still think the correct place for
> >> line-editing is in the driver.  Hell - it's already doing basic
> >> erase/kill line editing as it is.  Then you don't have to hack every
> >> command-line app to get line-editing.
> >
> >Yeah, but how do you specify completion then?
> 
> Same way termcap/termlib would be handled. :)

Would that allow for the flexibility of, say zsh's programmable
completion?  And then combined with my right hand side prompt?

It gets complicated very quickly.
-- 
Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator

"vi has two modes the one in which it beeps and the one in which it doesnt."
	-- Anon.


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 10:17:48 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154])
	by hub.freebsd.org (Postfix) with ESMTP id D216714C1B
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 10:17:45 -0700 (PDT)
	(envelope-from parag@pinhead.parag.codegen.com)
Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1])
	by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id KAA05631;
	Tue, 14 Sep 1999 10:17:35 -0700 (PDT)
	(envelope-from parag@pinhead.parag.codegen.com)
To: Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk>
Cc: "Matthew N. Dodd" <winter@jurai.net>,
	"Daniel O'Connor" <darius@dons.net.au>, freebsd-hackers@FreeBSD.ORG
Subject: Re: Command-line editing [was NetWare client in -current] 
In-Reply-To: Message from Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk> 
   of "Tue, 14 Sep 1999 17:39:34 BST." <19990914173933.B17847@voodoo.pandhm.co.uk> 
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
Date: Tue, 14 Sep 1999 10:17:35 -0700
Message-ID: <5627.937329455@pinhead.parag.codegen.com>
From: Parag Patel <parag@cgt.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 14 Sep 1999 17:39:34 BST, Dominic Mitchell wrote:

>Would that allow for the flexibility of, say zsh's programmable
>completion?  And then combined with my right hand side prompt?
>
>It gets complicated very quickly.

Oh I agree - but I still think it should only need to be in one place
rather than in a library or in each individual app.  I should be able to
plug-in my command-line-editing of choice (I may want to launch vi).

Wouldn't you like to see your custom zsh-style bindings and prompts
inside gdb, for instance?  How about ftp?  pgsql?


	-- Parag Patel


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 10:44:49 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37])
	by hub.freebsd.org (Postfix) with ESMTP id 5D7B81524C
	for <hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 10:44:46 -0700 (PDT)
	(envelope-from asmodai@wxs.nl)
Received: from daemon.ninth-circle.org ([195.121.196.108]) by smtp03.wxs.nl
          (Netscape Messaging Server 3.61)  with ESMTP id AAA3FD9;
          Tue, 14 Sep 1999 19:44:42 +0200
Received: (from asmodai@localhost)
	by daemon.ninth-circle.org (8.9.3/8.9.3) id TAA32858;
	Tue, 14 Sep 1999 19:31:31 +0200 (CEST)
	(envelope-from asmodai)
Date: Tue, 14 Sep 1999 19:31:31 +0200
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: Gustavo V G C Rios <grios@ddsecurity.com.br>, hackers@FreeBSD.ORG
Subject: Re: submiting source code ?
Message-ID: <19990914193131.A32851@daemon.ninth-circle.org>
References: <37D86506.4247EF3A@ddsecurity.com.br> <19990913090318.F89309@daemon.ninth-circle.org> <xzpbtb5zo9l.fsf@flood.ping.uio.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.7i
In-Reply-To: <xzpbtb5zo9l.fsf@flood.ping.uio.no>
Organisation: Ninth-Circle Enterprises
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

* Dag-Erling Smorgrav (des@flood.ping.uio.no) [990914 16:44]:
>Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> writes:
>> The Unix Programming Environment by Rob Pike and Ritchie Kerninghan
>
>Ritchie Kernighan? Who's Ritchie Kernighan?

Thanks for you concern about my apparant inability to remember big
names correctly Erling-Dag =P

*grin*

-- 
Jeroen Ruigrok van der Werven/Asmodai                  asmodai(at)wxs.nl
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
Network/Security Specialist        BSD: Technical excellence at its best
If Winter comes, can Spring be far behind?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 11:22:45 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from gfc-mad-proxy.gflesch.com (gfc-mad-proxy.gflesch.com [208.212.82.194])
	by hub.freebsd.org (Postfix) with ESMTP
	id C95A315026; Tue, 14 Sep 1999 11:22:34 -0700 (PDT)
	(envelope-from kwills@gflesch.com)
Received: from gfc-mad-mail.gflesch.com (gfc-mad-mail.gflesch.int [10.1.1.25])
	by gfc-mad-proxy.gflesch.com (8.9.2/8.9.1) with ESMTP id NAA78043;
	Tue, 14 Sep 1999 13:15:01 -0500 (CDT)
	(envelope-from kwills@gflesch.com)
Received: by gfc-mad-mail.gflesch.int with Internet Mail Service (5.5.2448.0)
	id <SQND0R18>; Tue, 14 Sep 1999 13:21:10 -0500
Message-ID: <058BE165CBA8D111A82E0008C79F9E35024828@gfc-mad-dc.gflesch.int>
From: "Wills, Ken" <kwills@gflesch.com>
To: jkruger@oskar.nanoteq.co.za, freebsd-questions@FreeBSD.ORG,
	freebsd-hackers@FreeBSD.ORG
Subject: RE: Custom boot.flp
Date: Tue, 14 Sep 1999 13:21:00 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Johan Kruger
> Sent: Tuesday, September 14, 1999 9:45 AM
> To: freebsd-questions@FreeBSD.ORG; freebsd-hackers@FreeBSD.ORG
> Subject: Custom boot.flp
> 
> I get :
> ----------------------
> Mounting root device on fd0c
> error mounting root on fd0c
> -- will reboot in 15 seconds -- bla bla
> ----------------------
> How do i tell it to mount it on CDROM ( probably wcd0a ) say for
> instance /MYMOUNT_DIR ??

Check the kernel config. You may need to build a new GENERIC kernel.
Also you'd check for any rc* or /etc/fstab entries that mount the floppy
as the root fs.

As a disclaimer, I've never done or tried to do this, but thats the
general idea <:)

Ken


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 11:41:19 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from medulla.hippocampus.net (medulla.hippocampus.net [204.138.241.6])
	by hub.freebsd.org (Postfix) with ESMTP
	id 08BE514EDA; Tue, 14 Sep 1999 11:40:33 -0700 (PDT)
	(envelope-from marc@netstor.com)
Received: from localhost (marc@localhost)
	by medulla.hippocampus.net (8.9.3/8.9.2) with ESMTP id OAA17910;
	Tue, 14 Sep 1999 14:38:45 -0400 (EDT)
Date: Tue, 14 Sep 1999 14:38:45 -0400 (EDT)
From: Marc Nicholas <marc@netstor.com>
X-Sender: marc@medulla.hippocampus.net
To: "Wills, Ken" <kwills@gflesch.com>
Cc: jkruger@oskar.nanoteq.co.za, freebsd-questions@FreeBSD.ORG,
	freebsd-hackers@FreeBSD.ORG
Subject: RE: Custom boot.flp
In-Reply-To: <058BE165CBA8D111A82E0008C79F9E35024828@gfc-mad-dc.gflesch.int>
Message-ID: <Pine.BSF.4.05.9909141437390.17897-100000@medulla.hippocampus.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Doesn't the boot.flp actually use sysinstall and a custom init process?
Therefore, you'd have to replace sysinstall with an init process of some
sort...

Someone correct me if I'm talking out of my a.out ;-)

-marc

-------------------------------------------------------------------
Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com
"Fast, Expandable and Affordable Internet Caching Products"
1.877.464.4776 416.979.9000x11 fax: 416.979.8223 cell: 416.346.9255

On Tue, 14 Sep 1999, Wills, Ken wrote:

> 
> > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Johan Kruger
> > Sent: Tuesday, September 14, 1999 9:45 AM
> > To: freebsd-questions@FreeBSD.ORG; freebsd-hackers@FreeBSD.ORG
> > Subject: Custom boot.flp
> > 
> > I get :
> > ----------------------
> > Mounting root device on fd0c
> > error mounting root on fd0c
> > -- will reboot in 15 seconds -- bla bla
> > ----------------------
> > How do i tell it to mount it on CDROM ( probably wcd0a ) say for
> > instance /MYMOUNT_DIR ??
> 
> Check the kernel config. You may need to build a new GENERIC kernel.
> Also you'd check for any rc* or /etc/fstab entries that mount the floppy
> as the root fs.
> 
> As a disclaimer, I've never done or tried to do this, but thats the
> general idea <:)
> 
> Ken
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 11:53:43 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66])
	by hub.freebsd.org (Postfix) with ESMTP id B299214C94
	for <freebsd-hackers@freebsd.org>; Tue, 14 Sep 1999 11:53:29 -0700 (PDT)
	(envelope-from nik@nothing-going-on.demon.co.uk)
Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18])
	by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id TAA54191;
	Tue, 14 Sep 1999 19:48:59 +0100 (BST)
	(envelope-from nik@catkin.nothing-going-on.org)
Received: (from nik@localhost)
	by kilt.nothing-going-on.org (8.9.3/8.9.3) id HAA60895;
	Tue, 14 Sep 1999 07:59:27 +0100 (BST)
	(envelope-from nik@catkin.nothing-going-on.org)
Date: Tue, 14 Sep 1999 07:59:27 +0100
From: Nik Clayton <nik@freebsd.org>
To: Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>
Cc: freebsd-hackers@freebsd.org
Subject: Re: aio_*
Message-ID: <19990914075926.A60617@kilt.nothing-going-on.org>
References: <19990914050240.40381.qmail@scam.xcf.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <19990914050240.40381.qmail@scam.xcf.berkeley.edu>; from Jayson Nordwick on Mon, Sep 13, 1999 at 10:02:40PM -0700
Organization: FreeBSD Project <URL:http://www.freebsd.org/>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Sep 13, 1999 at 10:02:40PM -0700, Jayson Nordwick wrote:
> While reading through (at least trying to... I wish there was some sort of
> kernel documentation available, the entry fee is very high) 

What we need is people like yourself, who are having to go through the 
learning curve, to document stuff as you're finding it out.  It doesn't
matter if your notes are a bit rough and ready, because the next person
to use them can improve on them, and the next person, and the next person,
and so on, until we have great kernel documentation.

Any takers?

N
-- 
 [intentional self-reference] can be easily accommodated using a blessed,
 non-self-referential dummy head-node whose own object destructor severs
 the links.
    -- Tom Christiansen in <375143b5@cs.colorado.edu>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 12:20:45 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id 063E814FFD
	for <freebsd-hackers@freebsd.org>; Tue, 14 Sep 1999 12:20:36 -0700 (PDT)
	(envelope-from rene@canyon.demon.nl)
Received: from [212.238.15.212] (helo=canyon.demon.nl)
	by post.mail.nl.demon.net with esmtp (Exim 2.02 #1)
	id 11Qy83-00018N-00; Tue, 14 Sep 1999 19:20:35 +0000
Received: (from rene@localhost)
	by canyon.demon.nl (8.9.3/8.9.3) id UAA00578;
	Thu, 14 Sep 2000 20:10:54 +0200 (CEST)
	(envelope-from rene)
From: Rene de Vries <rene@canyon.demon.nl>
Message-Id: <200009141810.UAA00578@canyon.demon.nl>
Subject: Re: de0 strangenesses
In-Reply-To: <199909130856.KAA33966@gil.physik.rwth-aachen.de> from Christoph Kukulies at "Sep 13, 1999 10:56:09 am"
To: kuku@gilberto.physik.RWTH-Aachen.DE (Christoph Kukulies)
Date: Thu, 14 Sep 2000 20:10:54 +0200 (CEST)
Cc: freebsd-hackers@freebsd.org (FreeBSD hackers)
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I think i've got a similar problem. This involves a DE500 (de0 driver)
ethernet card and a 100 Mbit UTP. The problem was that somehow the driver
didn't detect the 100Mbit and always switched to 10Mbit. The workaround that
I use is a simple script "/etc/start_if.de0" with the following contents:

# workaround 10/100Mbit start problem
ifconfig de0 192.168.1.2 media 100baseTX
ifconfig de0 down
sleep 2
ifconfig de0 up

Since I started using this script the machine always started with the
100baseTX interface active.

Rene

> On a 3.0-current of October 1998 I'm having often trouble with de0.
> The machine often reboots over night (when either the locate db is built or
> some other big job - like mirror - is running). Anyway, after the reboot,
> often de0 is dead.
> 
> This happend today again. When I came into the office I could not
> ping said machine. I sat at the console, logged in. The machine was
> perfectly alive, only the de0 interface didn't work at the BNC network.
> 
> I did a ifconfig de0 down and exactly with doing that I got a kernel message
> from the driver: de0 BNC interface enabled (or something like that).
> Doing an ifconfig de0 up right after that the interface continued working
> at the BNC port.
> 
> Can the driver writer(s) comment whether there have been changes to the driver
> WRT that behaviour so I can expect that with either 3.2 or -current
> the problem would be gone?

-- 
Rene de Vries                    http://www.tcja.nl/~rene; mailto:rene@tcja.nl


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 12:53:29 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250])
	by hub.freebsd.org (Postfix) with ESMTP id 746731521F
	for <hackers@freebsd.org>; Tue, 14 Sep 1999 12:53:03 -0700 (PDT)
	(envelope-from jobaldwi@vt.edu)
Received: from mailrelay.vt.edu (gkar.cc.vt.edu [128.173.16.40])
	by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id PAA19566;
	Tue, 14 Sep 1999 15:52:57 -0400 (EDT)
Received: from john.baldwin.cx (jobaldwi.campus.vt.edu)
 by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7)
 with ESMTP id <0FI2004HTF88RI@gkar.cc.vt.edu>; Tue,
 14 Sep 1999 15:52:56 -0400 (EDT)
Date: Tue, 14 Sep 1999 15:53:03 -0400 (EDT)
From: John Baldwin <jobaldwi@vt.edu>
Subject: RE: Problem with FreeBSD
In-reply-to: <18583.990913@ru.ru>
To: Tolyar <tolyar@ru.ru>
Cc: hackers@freebsd.org
Message-id: <0FI2004HUF88RI@gkar.cc.vt.edu>
MIME-version: 1.0
X-Mailer: XFMail 1.3 [p0] on FreeBSD
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 8bit
X-Priority: 3 (Normal)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 13-Sep-99 Tolyar wrote:
> Hello All.
> 
> I try install FreeBSD on HP Vectra VA/200DT - Pentium Pro/128Mb-RAM/
> Quantum Fireball CR 4.3Gb/CirrusLogic5446PCI PCI/NE2000.
> 
> When I try install FreeBSD (I'm tried
> 3.2-release/3.3-19990909-rc/snapshot-4.0-19990827-current)
> i have some trouble. On second floppy (mfsroot.flp) before kernel
> setup,
> FreeBSD write "zf_read: error". After this, I configured kernel (i
> kept only fdc0, wdc0, atkbd0, sc0)
> and when system wrote "changing root device to fd0c" and after this
> "rootfs is 2880Kbyte compiled in MFS" system stilled and doesn't run
> install proces, but "Pause" key and scrolling was working.

Your mfsroot floppy has a bad sector.  Try a different floppy.

---

John Baldwin <jobaldwi@vt.edu> -- http://www.cslab.vt.edu/~jobaldwi/
PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 13:40:52 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29])
	by hub.freebsd.org (Postfix) with ESMTP id C689815337
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 13:40:38 -0700 (PDT)
	(envelope-from cmsedore@mailbox.syr.edu)
Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.E1CCBFD0@mailer.syr.edu>; Tue, 14 Sep 1999 16:40:41 -0400
Received: from localhost (cmsedore@localhost)
	by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id QAA00135;
	Tue, 14 Sep 1999 16:40:37 -0400 (EDT)
X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs
Date: Tue, 14 Sep 1999 16:40:37 -0400 (EDT)
From: Christopher Sedore <cmsedore@mailbox.syr.edu>
X-Sender: cmsedore@rodan.syr.edu
To: Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: aio_*
In-Reply-To: <19990914050240.40381.qmail@scam.xcf.berkeley.edu>
Message-ID: <Pine.SOL.4.10.9909141613170.1425-100000@rodan.syr.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Mon, 13 Sep 1999, Jayson Nordwick wrote:

> While reading through (at least trying to... I wish there was some sort of
> kernel documentation available, the entry fee is very high) the aio_* calls,
> I had a few questions to clear up my understanding: 
> 
> 1) Do they only work on files?  The only implementation I see is in 
> the VFS layer.

Any read()/write()'able descriptor should work.

> 2) It is my understanding that it uses an aio daemon running as a kernel
> thread (the aio_daemon() call kind of give that one away).  It seems as
> if this can be almost entirely done in user space.  More important to what
> I am trying to do, it seems as if aio_* does not give peak latency     
> or throughput performace, since the aio_daemon has to compete for resources
> along with all other processes.
>    
> Should aio_* be used for applications that have high performance
> requirements?  What does aio_* get you above having a seperate 
> thread pumping in/out data?

The aio_* stuff (I use a custom patched version in 4.x) offers performance
advantages over select() with large numbers of descriptors.  In terms of
efficiency, I don't have any trouble saturating full-duplex 100mbit link
with aio routines on a reasonably fast box (PII-400 512MB).

As more work gets done to the aio stuff, there are some potential early
advantages available to multiprocessor machines (since the program
'driving' the aio could run concurrently with the kernel code moving
network or disk data).

-Chris



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 14:15: 6 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32])
	by hub.freebsd.org (Postfix) with ESMTP id 634D714F15
	for <hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 14:15:02 -0700 (PDT)
	(envelope-from dwhite@resnet.uoregon.edu)
Received: from localhost (dwhite@localhost)
	by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id OAA61128;
	Tue, 14 Sep 1999 14:14:14 -0700 (PDT)
	(envelope-from dwhite@resnet.uoregon.edu)
Date: Tue, 14 Sep 1999 14:14:14 -0700 (PDT)
From: Doug White <dwhite@resnet.uoregon.edu>
To: Ruslan Ermilov <ru@ucb.crimea.ua>
Cc: hackers@FreeBSD.ORG
Subject: Re: Multiple NAT alias addresses
In-Reply-To: <19990914192335.A3257@relay.ucb.crimea.ua>
Message-ID: <Pine.BSF.4.10.9909141411350.58561-100000@resnet.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 14 Sep 1999, Ruslan Ermilov wrote:

> > > > use_sockets yes
> > > > same_ports yes
> > > > #
> > > > # machine1 redirections 
> > > > #redirect_port tcp 192.168.2.237:ssh 1.2.3.4:ssh
> > > > #redirect_port tcp 192.168.2.237:smtp 1.2.3.4:smtp
> > > > #redirect_port tcp 192.168.2.237:pop3 1.2.3.4:pop3
> > > > #redirect_port tcp 192.168.2.237:imap4 1.2.3.4:imap4
> > > > 
> > > > # machine2 redirections
> > > > redirect_port tcp 192.168.2.201:ssh 1.2.3.5:ssh
> > > > redirect_port tcp 192.168.2.201:http 1.2.3.5:http
> > > > 
> > > > I start natd with:
> > > > 
> > > > natd -f /etc/natd.conf -n fxp0  where fxp0 is the public-side interface.
> > > > 
> > > > Restarting natd with this configuration causes it to block everything.
> > > > 
> > > So, without redirect_port's it works OK?
> > 
> > Yes, and the redirect_port's work if the alias address is not specified.
> > 
> Strange, I just run 3.2-RELEASE's natd(8) with your configuration file
> and everything works as expected:

Hm, rev. 1.21 of natd.c is worrisome:

1.21 Tue Sep 7 15:34:12 1999 UTC by ru 
CVS Tags: HEAD
Diffs to 1.20 

Config file parser changes:

- Trailing spaces and empty lines are ignored.
- A `#' sign will mark the remaining of the line as a comment.

Reviewed by:    Ari Suutari <ari@suutari.iki.fi>

Perhaps the parser is skipping my redirect_port lines?

> Firewall rules were:
> 00001 divert 8668 ip from any to 1.2.3.5 via fxp2
> 00001 divert 8668 ip from 192.168.2.201 to any via fxp2

Hm, I'm using the default divert rule 'divert 8668 all from any to any via
fxp0' instead of grabbing specific traffic.

> Natd(8) was run as:
> natd -v -f natd.cf -n fxp2 (fxp2 in an external interface)
> 
> 
> telnet 1.2.3.5 123 (from 212.110.138.4):
> In  [TCP]  [TCP] 212.110.138.4:49964 -> 1.2.3.5:123 aliased to
>            [TCP] 212.110.138.4:49964 -> 1.2.3.5:123
> In  [TCP]  [TCP] 212.110.138.4:49964 -> 1.2.3.5:123 aliased to
>            [TCP] 212.110.138.4:49964 -> 1.2.3.5:123
> In  [TCP]  [TCP] 212.110.138.4:49964 -> 1.2.3.5:123 aliased to
>            [TCP] 212.110.138.4:49964 -> 1.2.3.5:123
> Redirections not happening.
> 
> 
> 
> telnet 1.2.3.5 80 (from 212.110.138.4):
> In  [TCP]  [TCP] 212.110.138.4:49960 -> 1.2.3.5:80 aliased to
>            [TCP] 212.110.138.4:49960 -> 192.168.2.201:80
> Out [TCP]  [TCP] 192.168.2.201:80 -> 212.110.138.4:49960 aliased to
>            [TCP] 1.2.3.5:80 -> 212.110.138.4:49960
> In  [TCP]  [TCP] 212.110.138.4:49960 -> 1.2.3.5:80 aliased to
>            [TCP] 212.110.138.4:49960 -> 192.168.2.201:80
> In  [TCP]  [TCP] 212.110.138.4:49960 -> 1.2.3.5:80 aliased to
>            [TCP] 212.110.138.4:49960 -> 192.168.2.201:80
> Out [TCP]  [TCP] 192.168.2.201:80 -> 212.110.138.4:49960 aliased to
>            [TCP] 1.2.3.5:80 -> 212.110.138.4:49960
> Out [TCP]  [TCP] 192.168.2.201:80 -> 212.110.138.4:49960 aliased to
>            [TCP] 1.2.3.5:80 -> 212.110.138.4:49960
> In  [TCP]  [TCP] 212.110.138.4:49960 -> 1.2.3.5:80 aliased to
>            [TCP] 212.110.138.4:49960 -> 192.168.2.201:80
> Redirections are happening.

Very odd.  I'm going to adjust the configfile so that it has no comments
or blank space.  Can you send me your file exactly as you wrote it?  

> This is a known problem, it is fixed in -STABLE:
> 
> dfr         1999/05/22 01:29:24 PDT
> 
>   Modified files:        (Branch: RELENG_3)
>     contrib/gdb/gdb      solib.c
>   Log:
>   MFC: Problems with coredumps from static programs.

argh :(

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-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 14:33:59 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10])
	by hub.freebsd.org (Postfix) with ESMTP
	id E608914C8E; Tue, 14 Sep 1999 14:33:54 -0700 (PDT)
	(envelope-from abial@webgiro.com)
Received: by freja.webgiro.com (Postfix, from userid 1001)
	id EC3AF1916; Tue, 14 Sep 1999 23:34:43 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by freja.webgiro.com (Postfix) with ESMTP
	id EB54949D3; Tue, 14 Sep 1999 23:34:43 +0200 (CEST)
Date: Tue, 14 Sep 1999 23:34:43 +0200 (CEST)
From: Andrzej Bialecki <abial@webgiro.com>
To: Marc Nicholas <marc@netstor.com>
Cc: "Wills, Ken" <kwills@gflesch.com>, jkruger@oskar.nanoteq.co.za,
	freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
Subject: RE: Custom boot.flp
In-Reply-To: <Pine.BSF.4.05.9909141437390.17897-100000@medulla.hippocampus.net>
Message-ID: <Pine.BSF.4.05.9909142332150.44901-100000@freja.webgiro.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 14 Sep 1999, Marc Nicholas wrote:

> Doesn't the boot.flp actually use sysinstall and a custom init process?
> Therefore, you'd have to replace sysinstall with an init process of some
> sort...

No, sysinstall is THE custom init. Yes, you'd have to replace it with your
own init, if you really want to. You can take a look at
src/release/picobsd/tinyware/oinit. Or, you can take a look at scripting
abilities in sysinstall, if they are enough for your needs.

> Someone correct me if I'm talking out of my a.out ;-)

I thought you were an elf...

Andrzej Bialecki

//  <abial@webgiro.com> WebGiro AB, Sweden (http://www.webgiro.com)
// -------------------------------------------------------------------
// ------ FreeBSD: The Power to Serve. http://www.freebsd.org --------
// --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ----



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 14:45:12 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252])
	by hub.freebsd.org (Postfix) with ESMTP id 5A97014BD7
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 14:44:55 -0700 (PDT)
	(envelope-from olli@dorifer.heim3.tu-clausthal.de)
Received: (from olli@localhost)
	by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id XAA05633
	for freebsd-hackers@FreeBSD.ORG; Tue, 14 Sep 1999 23:44:50 +0200 (CEST)
	(envelope-from olli)
Date: Tue, 14 Sep 1999 23:44:50 +0200 (CEST)
From: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>
Message-Id: <199909142144.XAA05633@dorifer.heim3.tu-clausthal.de>
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: Command-line editing [was NetWare client in -current]
Organization: Administration Heim 3
Reply-To: freebsd-hackers@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: TIN [version 1.2 RZTUC(3) PL2]
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Parag Patel wrote in list.freebsd-hackers:
 > On Tue, 14 Sep 1999 17:39:34 BST, Dominic Mitchell wrote:
 > >It gets complicated very quickly.
 > 
 > Oh I agree - but I still think it should only need to be in one place
 > rather than in a library or in each individual app.

It _is_ in one place if it's in a library.  And personally
I think that's exatly where it belongs.  Does libedit ring
a bell...?

 > Wouldn't you like to see your custom zsh-style bindings and prompts
 > inside gdb, for instance?  How about ftp?  pgsql?

That's exactly what libedit could be used for (although it
could need a few technical improvements, IMO, but the basic
concept is there).

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
                                         (Terry Pratchett)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 15:55: 6 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154])
	by hub.freebsd.org (Postfix) with ESMTP id 25165152C4
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 15:54:51 -0700 (PDT)
	(envelope-from parag@pinhead.parag.codegen.com)
Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1])
	by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id PAA07899
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 15:54:50 -0700 (PDT)
	(envelope-from parag@pinhead.parag.codegen.com)
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: Command-line editing [was NetWare client in -current] 
In-Reply-To: Message from Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de> 
   of "Tue, 14 Sep 1999 23:44:50 +0200." <199909142144.XAA05633@dorifer.heim3.tu-clausthal.de> 
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
Date: Tue, 14 Sep 1999 15:54:50 -0700
Message-ID: <7895.937349690@pinhead.parag.codegen.com>
From: Parag Patel <parag@cgt.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 14 Sep 1999 23:44:50 +0200, Oliver Fromme wrote:

>It _is_ in one place if it's in a library.  And personally
>I think that's exatly where it belongs.  Does libedit ring
>a bell...?

Yes, I know about libedit and libreadline.  My point is I shouldn't have
to alter any command-line app to link to and use some library just to
get command-line editing in it.

Worse, each app uses a different library with different configuration,
syntax, API, and so on.  If your zsh is configured to put the prompt on
the right, why shouldn't everything else do the same?

Yet another library is not an answer - it just adds to the problem.

Anyway, command-line apps have been obsolete for years, so I guess we
should go on and find better things to argue about.  :)


	-- Parag Patel


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 16:41:57 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194])
	by hub.freebsd.org (Postfix) with ESMTP id A187F14D51
	for <hackers@freebsd.org>; Tue, 14 Sep 1999 16:41:50 -0700 (PDT)
	(envelope-from sa-list@avantgo.com)
Received: from avantgo.com ([10.0.128.109]) by bomber.avantgo.com
          (Netscape Messaging Server 3.5)  with ESMTP id 306
          for <hackers@freebsd.org>; Tue, 14 Sep 1999 16:36:59 -0700
Message-ID: <37DEDD59.6FFDFEAD@avantgo.com>
Date: Tue, 14 Sep 1999 16:42:17 -0700
From: Stevan Arychuk <sa-list@avantgo.com>
Reply-To: sa-list@avantgo.com
Organization: AvantGo Inc.
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: help with flaky reboot on 3.1
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Greetings,

We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the
RELENG_3 branch (used this to take advantage of the KVA modifications
that were rolled in after the release).

The machines are dual PII 450's (N440BX) with 512MB RAM.  We are also
using built in ethernet and SCSI controllers.

Our kernel configuration is fairly standard with the following
exceptions:
maxusers     512
options      NMBCLUSTERS=33280
options      SMP
options      APIC_IO
options     "VM_KMEM_SIZE=(128*1024*1024)"
options     "VM_KMEM_SIZE_MAX=(128*1024*1024)"

Here are the symptoms we are seeing:

1 machine running a caching squid reverse proxy would spontaneously
reboot with no error messages every week or so.  This machine was a
single CPU only.  

We were seeing an excessive number of sockets in the CLOSING state, via
netstat.  The reboots seemed to be co-related to having many such
sockets.  Suspecting bad TCP stack on the Internet, we did 'sysctl -w
net.inet.tcp.always_keepalive=1'  This fixed the many CLOSING sockets
problem, but did not fix the reboots.

Other machines running custom software (Dual CPU) would also
spontaneously reboot also with no error messages.  The reboots are
happening on an increasing frequency, almost to the point of a couple
times a day.  Sometimes a machine would reboot a couple times a day,
then be ok for another week or so.  

Our software excercies the disk, CPU and network quite a bit, but not
excessively.  The only machines that are having problems, are production
machines directly connected to the Internet.  We've had the same
machines running internally with longer uptimes, and heavier volumes.

Any suggestions/idea's?

Sorry about the super-post, I thought detail was important.

- Stevan Arychuk


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 16:45:53 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235])
	by hub.freebsd.org (Postfix) with ESMTP id B9B4D14D51
	for <hackers@freebsd.org>; Tue, 14 Sep 1999 16:45:50 -0700 (PDT)
	(envelope-from jedgar@fxp.org)
Received: by pawn.primelocation.net (Postfix, from userid 1003)
	id 8A26CF817; Tue, 14 Sep 1999 19:45:48 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by pawn.primelocation.net (Postfix) with ESMTP
	id 7C4879B17; Tue, 14 Sep 1999 19:45:48 -0400 (EDT)
Date: Tue, 14 Sep 1999 19:45:48 -0400 (EDT)
From: "Chris D. Faulhaber" <jedgar@fxp.org>
X-Sender: jedgar@pawn.primelocation.net
To: Stevan Arychuk <sa-list@avantgo.com>
Cc: hackers@freebsd.org
Subject: Re: help with flaky reboot on 3.1
In-Reply-To: <37DEDD59.6FFDFEAD@avantgo.com>
Message-ID: <Pine.BSF.4.10.9909141945040.879-100000@pawn.primelocation.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 14 Sep 1999, Stevan Arychuk wrote:

> Greetings,
> 
> We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the
> RELENG_3 branch (used this to take advantage of the KVA modifications
> that were rolled in after the release).
> 
> 
> Here are the symptoms we are seeing:
> 
> 1 machine running a caching squid reverse proxy would spontaneously
> reboot with no error messages every week or so.  This machine was a
> single CPU only.  
> 
> We were seeing an excessive number of sockets in the CLOSING state, via
> netstat.  The reboots seemed to be co-related to having many such
> sockets.  Suspecting bad TCP stack on the Internet, we did 'sysctl -w
> net.inet.tcp.always_keepalive=1'  This fixed the many CLOSING sockets
> problem, but did not fix the reboots.
> 
> Other machines running custom software (Dual CPU) would also
> spontaneously reboot also with no error messages.  The reboots are
> happening on an increasing frequency, almost to the point of a couple
> times a day.  Sometimes a machine would reboot a couple times a day,
> then be ok for another week or so.  
> 
> Our software excercies the disk, CPU and network quite a bit, but not
> excessively.  The only machines that are having problems, are production
> machines directly connected to the Internet.  We've had the same
> machines running internally with longer uptimes, and heavier volumes.
> 
> Any suggestions/idea's?
> 
> Sorry about the super-post, I thought detail was important.
> 
> - Stevan Arychuk
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 

-----
Chris D. Faulhaber <jedgar@fxp.org>  |  All the true gurus I've met never
System/Network Administrator,        |  claimed they were one, and always
Reality Check Information, Inc.      |  pointed to someone better.






To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 16:48: 5 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235])
	by hub.freebsd.org (Postfix) with ESMTP id AB3B615241
	for <hackers@freebsd.org>; Tue, 14 Sep 1999 16:48:03 -0700 (PDT)
	(envelope-from jedgar@fxp.org)
Received: by pawn.primelocation.net (Postfix, from userid 1003)
	id AB3B5F818; Tue, 14 Sep 1999 19:48:02 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by pawn.primelocation.net (Postfix) with ESMTP
	id 9FEC39B17; Tue, 14 Sep 1999 19:48:02 -0400 (EDT)
Date: Tue, 14 Sep 1999 19:48:02 -0400 (EDT)
From: "Chris D. Faulhaber" <jedgar@fxp.org>
X-Sender: jedgar@pawn.primelocation.net
To: Stevan Arychuk <sa-list@avantgo.com>
Cc: hackers@freebsd.org
Subject: Re: help with flaky reboot on 3.1
In-Reply-To: <37DEDD59.6FFDFEAD@avantgo.com>
Message-ID: <Pine.BSF.4.10.9909141946200.896-100000@pawn.primelocation.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 14 Sep 1999, Stevan Arychuk wrote:

> Greetings,
> 
> We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the
> RELENG_3 branch (used this to take advantage of the KVA modifications
> that were rolled in after the release).
> 

Are the kernel and user-land out of sync (kernel sources newer than system
sources)?

Cheers,
Chris

p.s. sorry about the prev. reply without comments...Pine's send and cancel
keys are too close together :)

-----
Chris D. Faulhaber <jedgar@fxp.org>  |  All the true gurus I've met never
System/Network Administrator,        |  claimed they were one, and always
Reality Check Information, Inc.      |  pointed to someone better.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 16:57:32 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194])
	by hub.freebsd.org (Postfix) with ESMTP id 5A1321513A
	for <hackers@freebsd.org>; Tue, 14 Sep 1999 16:57:29 -0700 (PDT)
	(envelope-from sa-list@avantgo.com)
Received: from avantgo.com ([10.0.128.109]) by bomber.avantgo.com
          (Netscape Messaging Server 3.5)  with ESMTP id 345;
          Tue, 14 Sep 1999 16:52:39 -0700
Message-ID: <37DEE105.8793D2A6@avantgo.com>
Date: Tue, 14 Sep 1999 16:57:57 -0700
From: Stevan Arychuk <sa-list@avantgo.com>
Reply-To: sa-list@avantgo.com
Organization: AvantGo Inc.
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Chris D. Faulhaber" <jedgar@fxp.org>
Cc: hackers@freebsd.org
Subject: Re: help with flaky reboot on 3.1
References: <Pine.BSF.4.10.9909141946200.896-100000@pawn.primelocation.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Yes,

The KVA patches were introduced after the initial release of 3.1, so I
guess you could say we're running 3.1 1/2 - RELEASE.

We held off on upgrading to 3.2 as there was still a problem with GDB. 
I'm testing 3.3-19990909-RC and I've been able to do a back trace on a
core dump from a SMP-enabled kernel 4 out of 6 times.  

I haven't been following the other lists, does anyone know how close
this latest RC is, will it be 3.3-RELEASE by tommorow?

- Stevan

"Chris D. Faulhaber" wrote:
> 
> On Tue, 14 Sep 1999, Stevan Arychuk wrote:
> 
> > Greetings,
> >
> > We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the
> > RELENG_3 branch (used this to take advantage of the KVA modifications
> > that were rolled in after the release).
> >
> 
> Are the kernel and user-land out of sync (kernel sources newer than system
> sources)?
> 
> Cheers,
> Chris
> 
> p.s. sorry about the prev. reply without comments...Pine's send and cancel
> keys are too close together :)
> 
> -----
> Chris D. Faulhaber <jedgar@fxp.org>  |  All the true gurus I've met never
> System/Network Administrator,        |  claimed they were one, and always
> Reality Check Information, Inc.      |  pointed to someone better.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 19: 5:36 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46])
	by hub.freebsd.org (Postfix) with ESMTP id 1B8D4155EE
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 19:05:22 -0700 (PDT)
	(envelope-from beattie@aracnet.com)
Received: from shell2.aracnet.com (IDENT:1728@shell2.aracnet.com [216.99.193.20])
	by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id TAA24501;
	Tue, 14 Sep 1999 19:05:25 -0700
Received: from localhost by shell2.aracnet.com (8.8.7)  id TAA19593; Tue, 14 Sep 1999 19:05:24 -0700
X-Authentication-Warning: shell2.aracnet.com: beattie owned process doing -bs
Date: Tue, 14 Sep 1999 19:05:24 -0700 (PDT)
From: Brian Beattie <beattie@aracnet.com>
To: Parag Patel <parag@cgt.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Command-line editing [was NetWare client in -current] 
In-Reply-To: <7895.937349690@pinhead.parag.codegen.com>
Message-ID: <Pine.LNX.4.10.9909141856060.18914-100000@shell2.aracnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 14 Sep 1999, Parag Patel wrote:
> Anyway, command-line apps have been obsolete for years,

According to whom, Microsoft?  I would claim that any functionality that
is not fully supported by a command line interface (except, perhaps,  for
specifically graphical functionality) is not fully supported.

As for line-editing in the kernel, let put ISAM and support for record
structured files while we are cramming stuff into the kernel.  THen we
will be that much closer to Multics.  Yuck!

Brian Beattie            | The only problem with
beattie@aracnet.com      | winning the rat race ...
www.aracnet.com/~beattie | in the end you're still a rat



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 19:54:11 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154])
	by hub.freebsd.org (Postfix) with ESMTP id C0C1F156A7
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 19:53:53 -0700 (PDT)
	(envelope-from parag@pinhead.parag.codegen.com)
Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1])
	by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id TAA09223
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 14 Sep 1999 19:53:53 -0700 (PDT)
	(envelope-from parag@pinhead.parag.codegen.com)
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: Command-line editing [was NetWare client in -current] 
In-Reply-To: Message from Parag Patel <parag@pinhead.parag.codegen.com> 
   of "Tue, 14 Sep 1999 15:54:50 PDT." <7895.937349690@pinhead.parag.codegen.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
Date: Tue, 14 Sep 1999 19:53:52 -0700
Message-ID: <9219.937364032@pinhead.parag.codegen.com>
From: Parag Patel <parag@cgt.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I said:

>Anyway, command-line apps have been obsolete for years, so I guess we
>should go on and find better things to argue about.  :)

I guess people missed the ":)" so I'd better explain.

Most computers are embedded and becoming both more ubiquitous and
invisble.  Most of these don't even *have* interfaces, GUI or CLI.
CLIs are pretty much useful only for developers, sysadmins, and support.

That said, I'd prefer a Mac MPW-style shell/editor where the tools
themselves don't know nor care about command-line editing and vptys are
a thing of the past.  Sort of like a less linear xterm with more powerful
cut/paste/exec facilities.  Someday I may even finish writing it...

Hm - come to think of it, I guess there is no good reason to put CLI
stuff into the driver.  Nor "cooked" modes.  Apologies for wasting time.


	-- Parag Patel


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 21:54:39 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232])
	by hub.freebsd.org (Postfix) with ESMTP id 357EB156DE
	for <hackers@freebsd.org>; Tue, 14 Sep 1999 21:54:35 -0700 (PDT)
	(envelope-from leifn@neland.dk)
Received: from localhost (localhost [127.0.0.1])
	by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id GAA19797
	for <hackers@freebsd.org>; Wed, 15 Sep 1999 06:57:54 +0200 (CEST)
	(envelope-from leifn@neland.dk)
Date: Wed, 15 Sep 1999 06:57:54 +0200 (CEST)
From: Leif Neland <leifn@neland.dk>
To: hackers@freebsd.org
Subject: USB cameras
Message-ID: <Pine.BSF.4.05.9909150655320.18600-100000@arnold.neland.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

A simple question: Are USB cameras supported? Is anybody working on it?

Oh, btw, how long can USB be extended?

Leif




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Tue Sep 14 21:59:51 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id 3AA4F157A2
	for <freebsd-hackers@freebsd.org>; Tue, 14 Sep 1999 21:59:36 -0700 (PDT)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id AAA13567;
	Wed, 15 Sep 1999 00:59:35 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.9.3/8.9.1) id AAA17634;
	Wed, 15 Sep 1999 00:59:05 -0400 (EDT)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 15 Sep 1999 00:59:04 -0400 (EDT)
To: Mohit Aron <aron@cs.rice.edu>
Cc: freebsd-hackers@freebsd.org
Subject: Re: fxp driver for alpha
In-Reply-To: <199909141559.KAA05204@cs.rice.edu>
References: <199909141559.KAA05204@cs.rice.edu>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14303.9197.654682.486382@grasshopper.cs.duke.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



Hi, 

Small world, the same thing happened to me today.  I've appended some very
preliminary patches to -current -- I've just gotten it to work & not
had a chance to do more than comment out my debugging printfs. Also,
be warned that I have not tested it beyond a simple telnet.


Mohit Aron writes:
 > Hi,
 > 	I'm using the latest available snapshot (4.0-19990808-CURRENT) for
 > an Alphaserver 500 workstation. Unfortunately, this version of FreeBSD 
 > panics upon seeing an fxp network interface. Does anyone have an updated driver
 > for the Alpha that supports the fxp interface ?
 > 
 > There is also a "de" interface on the Alpha that works with FreeBSD but the
 > performance is rather dismal. A webserver running on the machine gives only
 > 120 req/s on this machine (as opposed to 800 req/s on a Pentium III). Moreover,
 > most of the time the OS shows that its idle - looks like the problem lies in
 > the "de" driver. An updated de driver would also be appreciated.

Is this an AlphaStation 500?  Eg, a kn20aa kernel?  And is the de0 in
question the built-in 10Mb 21040?

Or is this a "miata" (Digital Personal Workstation 500a{,u})?  On
miatas, the on-board de0 uses the 21143 chipset.  I've yet to find a
free OS that can get the duplex mode right.  If this is the case, you
should throw the switch port into 100Mb, 1/2 duplex mode, or ignore
the de0 and proceed on with the fxp.

{\begin shameless-plug} Also, if you're doing performance analysis on
FreeBSD/alpha, you should have a peek at iprobe.  Its not quite DCPI,
but it is free ;-) See http://www.cs.duke.edu/ari/iprobe.html {\end
shameless-plug}

Cheers,

Drew
------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer	http://www.cs.duke.edu/~gallatin
Duke University				Email: gallatin@cs.duke.edu
Department of Computer Science		Phone: (919) 660-6590


Index: if_fxp.c
===================================================================
RCS file: /home/ncvs/src/sys/pci/if_fxp.c,v
retrieving revision 1.72
diff -u -b -B -r1.72 if_fxp.c
--- if_fxp.c	1999/09/06 06:15:18	1.72
+++ if_fxp.c	1999/09/14 21:18:53
@@ -80,11 +80,6 @@
 #include <dev/pci/pcireg.h>
 #include <dev/pci/pcidevs.h>
 
-#ifdef __alpha__		/* XXX */
-/* XXX XXX NEED REAL DMA MAPPING SUPPORT XXX XXX */
-#undef vtophys
-#define	vtophys(va)	alpha_XXX_dmamap((vm_offset_t)(va))
-#endif /* __alpha__ */
 
 #else /* __FreeBSD__ */
 
@@ -108,6 +103,13 @@
 
 #endif /* __NetBSD__ */
 
+#ifdef __alpha__		/* XXX */
+/* XXX XXX NEED REAL DMA MAPPING SUPPORT XXX XXX */
+#undef vtophys
+#define	vtophys(va)	alpha_XXX_dmamap((vm_offset_t)(va))
+#endif /* __alpha__ */
+
+
 #include "opt_bdg.h"
 #ifdef BRIDGE
 #include <net/if_types.h>
@@ -548,6 +550,12 @@
 		goto fail;
         }
 	sc->csr = rman_get_virtual(sc->mem); /* XXX use bus_space */
+	sc->sc_st = rman_get_bustag(sc->mem);
+	sc->sc_sh = rman_get_bushandle(sc->mem);
+#ifdef __alpha__
+        sc->csr = (caddr_t)pci_cvt_to_dense((vm_offset_t)sc->csr);
+        sc->csr = (caddr_t)ALPHA_PHYS_TO_K0SEG((vm_offset_t)sc->csr);
+#endif
 
 	/*
 	 * Allocate our interrupt.
@@ -1716,7 +1724,15 @@
 	 */
 	rfa = mtod(m, struct fxp_rfa *);
 	m->m_data += sizeof(struct fxp_rfa);
-	rfa->size = MCLBYTES - sizeof(struct fxp_rfa) - RFA_ALIGNMENT_FUDGE;
+/*printf("rfa=%p\n", rfa);
+printf("&rfa->status = %p\n", &rfa->rfa_status);
+printf("&rfa->control = %p\n", &rfa->rfa_control);
+printf("&rfa->link_addr = %p\n", &rfa->link_addr);
+printf("&rfa->rbd_addr = %p\n", &rfa->rbd_addr);
+printf("&rfa->actual_size = %p\n", &rfa->actual_size);
+printf("&rfa->size = %p\n", &rfa->size);
+Debugger("About to panic");*/
+	rfa->size = (u_int16_t)(MCLBYTES - sizeof(struct fxp_rfa) - RFA_ALIGNMENT_FUDGE);
 
 	/*
 	 * Initialize the rest of the RFA.  Note that since the RFA
@@ -1728,8 +1745,8 @@
 	rfa->actual_size = 0;
 
 	v = -1;
-	fxp_lwcopy(&v, &rfa->link_addr);
-	fxp_lwcopy(&v, &rfa->rbd_addr);
+	fxp_lwcopy(&v, (volatile u_int32_t *) &rfa->link_addr[0]);
+	fxp_lwcopy(&v, (volatile u_int32_t *) &rfa->rbd_addr[0]);
 
 	/*
 	 * If there are other buffers already on the list, attach this
@@ -1740,7 +1757,7 @@
 		    RFA_ALIGNMENT_FUDGE);
 		sc->rfa_tailm->m_next = m;
 		v = vtophys(rfa);
-		fxp_lwcopy(&v, &p_rfa->link_addr);
+		fxp_lwcopy(&v, (volatile u_int32_t *) &p_rfa->link_addr[0]);
 		p_rfa->rfa_control &= ~FXP_RFA_CONTROL_EL;
 	} else {
 		sc->rfa_headm = m;
Index: if_fxpreg.h
===================================================================
RCS file: /home/ncvs/src/sys/pci/if_fxpreg.h,v
retrieving revision 1.17
diff -u -b -B -r1.17 if_fxpreg.h
--- if_fxpreg.h	1999/09/06 06:15:18	1.17
+++ if_fxpreg.h	1999/09/14 20:14:30
@@ -245,8 +245,8 @@
 struct fxp_rfa {
 	volatile u_int16_t rfa_status;
 	volatile u_int16_t rfa_control;
-	volatile u_int32_t link_addr;
-	volatile u_int32_t rbd_addr;
+        volatile u_int8_t link_addr[4];
+        volatile u_int8_t rbd_addr[4];
 	volatile u_int16_t actual_size;
 	volatile u_int16_t size;
 };
Index: if_fxpvar.h
===================================================================
RCS file: /home/ncvs/src/sys/pci/if_fxpvar.h,v
retrieving revision 1.8
diff -u -b -B -r1.8 if_fxpvar.h
--- if_fxpvar.h	1999/08/28 00:50:51	1.8
+++ if_fxpvar.h	1999/09/14 20:46:14
@@ -42,8 +42,6 @@
 #if defined(__NetBSD__)
 	struct device sc_dev;		/* generic device structures */
 	void *sc_ih;			/* interrupt handler cookie */
-	bus_space_tag_t sc_st;		/* bus space tag */
-	bus_space_handle_t sc_sh;	/* bus space handle */
 	struct ethercom sc_ethercom;	/* ethernet common part */
 #else
 	struct arpcom arpcom;		/* per-interface network data */
@@ -52,6 +50,8 @@
 	struct resource *irq;		/* resource descriptor for interrupt */
 	void *ih;			/* interrupt handler cookie */
 #endif /* __NetBSD__ */
+	bus_space_tag_t sc_st;		/* bus space tag */
+	bus_space_handle_t sc_sh;	/* bus space handle */
 	struct mbuf *rfa_headm;		/* first mbuf in receive frame area */
 	struct mbuf *rfa_tailm;		/* last mbuf in receive frame area */
 	struct fxp_cb_tx *cbl_first;	/* first active TxCB in list */
@@ -71,7 +71,7 @@
 };
 
 /* Macros to ease CSR access. */
-#if defined(__NetBSD__)
+#if defined(__NetBSD__) || defined(__FreeBSD__)
 #define	CSR_READ_1(sc, reg)						\
 	bus_space_read_1((sc)->sc_st, (sc)->sc_sh, (reg))
 #define	CSR_READ_2(sc, reg)						\


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15  0: 8:20 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201])
	by hub.freebsd.org (Postfix) with SMTP id 0328014D72
	for <freebsd-hackers@freebsd.org>; Wed, 15 Sep 1999 00:08:16 -0700 (PDT)
	(envelope-from nordwick@scam.xcf.berkeley.edu)
Received: (qmail 34513 invoked by uid 27268); 15 Sep 1999 07:08:00 -0000
Message-ID: <19990915070800.34512.qmail@scam.xcf.berkeley.edu>
To: freebsd-hackers@freebsd.org
Subject: High Performance I/O (more)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <34511.937379280.1@scam.XCF.Berkeley.EDU>
Date: Wed, 15 Sep 1999 00:08:00 -0700
From: "Jayson Nordwick" <nordwick@scam.xcf.berkeley.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I did research this weekend on high performance I/O.  I looked at differerent
approaches and to me they all appear the same (I know that I will get some
flamage for this).  The two most prominent models that I saw were IO
Completion Ports and Synchronous Events (such as the Gaurav
http://www.cs.rice.edu/~gaurav/papers/usenix99.ps).

I think that both of these models are basically the same.  They both have
an event queue that you pick up events from.  The only way that they differ
is in what they call an event.  Completion ports take asynchronous opperations
and queue an event when the opperation completes (hence the name).  Synchronous
events do the opposite: they queue an event when an opperation is possible
and then the synchronous (usually, non-blocking) opperation is performed.
From this, you can decouple and event queue from what you call an event.

From what I can see either model will give roughly the same performance,
as they both do roughly the same amount of work.  The one benefit that seems
to exist for the Completion Ports model is that there are fewer contex
switches.

Now, looking at POSIX.1b signals and signal queues and getting some
information from Stephen Tweedie it looks like completion ports are doable
without anything new, I think that I have decided.

If you find an available signal, set the handler for it, the block it,
this signal number now effectively becomes the completion port.  You then
can fcntl() a file descriptor with F_SETSIG and the signal number.  Then to
fetch the blocked signals, use sigwaitinfo().  I guess you could also use
aio_{read,write}() and set sigevent appropriately.  This actually seems
preferable since you can then use aio_return() to find the return value
out and use aio_cancel() to cancel the request if wanted.

The one drawback that I see to this is that it can only really handle
aio_{read,write}() and {read,write}()/fcntl().  Any other events such as
thread/child deaths cannot really be worked into this scheme unless you
could set the signal they deliver on termination.

If you really wanted to, you could have signals delivered for the ability
to read/write to a file descriptor and then you would have Gaurav's model.

Basically, unless anybody can see anything wrong with this get to work
implementing!

-jason



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15  0:16:39 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1])
	by hub.freebsd.org (Postfix) with ESMTP id 12D2414DAF
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 00:13:53 -0700 (PDT)
	(envelope-from ru@ucb.crimea.ua)
Received: (from ru@localhost)
	by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id KAA89701;
	Wed, 15 Sep 1999 10:06:19 +0300 (EEST)
	(envelope-from ru)
Date: Wed, 15 Sep 1999 10:06:19 +0300
From: Ruslan Ermilov <ru@ucb.crimea.ua>
To: Christopher Sedore <cmsedore@mailbox.syr.edu>
Cc: Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: kern/13075 (was: Re: aio_*)
Message-ID: <19990915100619.C86648@relay.ucb.crimea.ua>
Mail-Followup-To: Christopher Sedore <cmsedore@mailbox.syr.edu>,
	Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>,
	freebsd-hackers@FreeBSD.ORG
References: <19990914050240.40381.qmail@scam.xcf.berkeley.edu> <Pine.SOL.4.10.9909141613170.1425-100000@rodan.syr.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <Pine.SOL.4.10.9909141613170.1425-100000@rodan.syr.edu>; from Christopher Sedore on Tue, Sep 14, 1999 at 04:40:37PM -0400
X-Operating-System: FreeBSD 3.2-STABLE i386
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Sep 14, 1999 at 04:40:37PM -0400, Christopher Sedore wrote:
> 
> 
> On Mon, 13 Sep 1999, Jayson Nordwick wrote:
> 
> > While reading through (at least trying to... I wish there was some sort of
> > kernel documentation available, the entry fee is very high) the aio_* calls,
> > I had a few questions to clear up my understanding: 
> > 
> > 1) Do they only work on files?  The only implementation I see is in 
> > the VFS layer.
> 
> Any read()/write()'able descriptor should work.
> 
> > 2) It is my understanding that it uses an aio daemon running as a kernel
> > thread (the aio_daemon() call kind of give that one away).  It seems as
> > if this can be almost entirely done in user space.  More important to what
> > I am trying to do, it seems as if aio_* does not give peak latency     
> > or throughput performace, since the aio_daemon has to compete for resources
> > along with all other processes.
> >    
> > Should aio_* be used for applications that have high performance
> > requirements?  What does aio_* get you above having a seperate 
> > thread pumping in/out data?
> 
> The aio_* stuff (I use a custom patched version in 4.x) offers performance
> advantages over select() with large numbers of descriptors.  In terms of
> efficiency, I don't have any trouble saturating full-duplex 100mbit link
> with aio routines on a reasonably fast box (PII-400 512MB).
> 
> As more work gets done to the aio stuff, there are some potential early
> advantages available to multiprocessor machines (since the program
> 'driving' the aio could run concurrently with the kernel code moving
> network or disk data).
> 
> -Chris

Do you by any change have an idea how to fix PR kern/13075
(signal is not posted for async I/O on raw devices)


Thanks,
-- 
Ruslan Ermilov		Sysadmin and DBA of the
ru@ucb.crimea.ua	United Commercial Bank,
ru@FreeBSD.org		FreeBSD committer,
+380.652.247.647	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15  0:44:46 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1])
	by hub.freebsd.org (Postfix) with ESMTP id 2C19814CE8
	for <hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 00:44:24 -0700 (PDT)
	(envelope-from ru@ucb.crimea.ua)
Received: (from ru@localhost)
	by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id KAA00245;
	Wed, 15 Sep 1999 10:43:51 +0300 (EEST)
	(envelope-from ru)
Date: Wed, 15 Sep 1999 10:43:50 +0300
From: Ruslan Ermilov <ru@ucb.crimea.ua>
To: Doug White <dwhite@resnet.uoregon.edu>
Cc: hackers@FreeBSD.ORG
Subject: Re: Multiple NAT alias addresses
Message-ID: <19990915104350.G86648@relay.ucb.crimea.ua>
Mail-Followup-To: Doug White <dwhite@resnet.uoregon.edu>,
	hackers@FreeBSD.ORG
References: <19990914192335.A3257@relay.ucb.crimea.ua> <Pine.BSF.4.10.9909141411350.58561-100000@resnet.uoregon.edu>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=mojUlQ0s9EVzWg2t
X-Mailer: Mutt 0.95.3i
In-Reply-To: <Pine.BSF.4.10.9909141411350.58561-100000@resnet.uoregon.edu>; from Doug White on Tue, Sep 14, 1999 at 02:14:14PM -0700
X-Operating-System: FreeBSD 3.2-STABLE i386
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--mojUlQ0s9EVzWg2t
Content-Type: text/plain; charset=us-ascii

On Tue, Sep 14, 1999 at 02:14:14PM -0700, Doug White wrote:
> On Tue, 14 Sep 1999, Ruslan Ermilov wrote:
> 
> > > > > use_sockets yes
> > > > > same_ports yes
> > > > > #
> > > > > # machine1 redirections 
> > > > > #redirect_port tcp 192.168.2.237:ssh 1.2.3.4:ssh
> > > > > #redirect_port tcp 192.168.2.237:smtp 1.2.3.4:smtp
> > > > > #redirect_port tcp 192.168.2.237:pop3 1.2.3.4:pop3
> > > > > #redirect_port tcp 192.168.2.237:imap4 1.2.3.4:imap4
> > > > > 
> > > > > # machine2 redirections
> > > > > redirect_port tcp 192.168.2.201:ssh 1.2.3.5:ssh
> > > > > redirect_port tcp 192.168.2.201:http 1.2.3.5:http
> > > > > 
> > > > > I start natd with:
> > > > > 
> > > > > natd -f /etc/natd.conf -n fxp0  where fxp0 is the public-side interface.
> > > > > 
> > > > > Restarting natd with this configuration causes it to block everything.
> > > > > 
> > > > So, without redirect_port's it works OK?
> > > 
> > > Yes, and the redirect_port's work if the alias address is not specified.
> > > 
> > Strange, I just run 3.2-RELEASE's natd(8) with your configuration file
> > and everything works as expected:
> 
> Hm, rev. 1.21 of natd.c is worrisome:
> 
> 1.21 Tue Sep 7 15:34:12 1999 UTC by ru 
> CVS Tags: HEAD
> Diffs to 1.20 
> 
> Config file parser changes:
> 
> - Trailing spaces and empty lines are ignored.
> - A `#' sign will mark the remaining of the line as a comment.
> 
> Reviewed by:    Ari Suutari <ari@suutari.iki.fi>
> 
> Perhaps the parser is skipping my redirect_port lines?
> 
Yeah, I committed this change after one guy had the problems with
redirect_port's not happening.  He had `#' after `redirect_port' line,
and natd(8) silently ignored it.  But you said that it works for you
without specifying publicIP, so this shouldn't be the case here.

> > Firewall rules were:
> > 00001 divert 8668 ip from any to 1.2.3.5 via fxp2
> > 00001 divert 8668 ip from 192.168.2.201 to any via fxp2
> 
> Hm, I'm using the default divert rule 'divert 8668 all from any to any via
> fxp0' instead of grabbing specific traffic.
> 
I understand.  My rules look so, because I have another natd(8) (production)
running on my outside interface, so I grabbed only those packets that were
sufficient to experiment with your config file.

[...]
> Very odd.  I'm going to adjust the configfile so that it has no comments
> or blank space.  Can you send me your file exactly as you wrote it?  
> 
I just copied your config file from your original posting, see attached.
But PLEASE MAKE SURE you have no trailing whitespaces at the end of
your redirect_port rules!


Later,
-- 
Ruslan Ermilov		Sysadmin and DBA of the
ru@ucb.crimea.ua	United Commercial Bank,
ru@FreeBSD.org		FreeBSD committer,
+380.652.247.647	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age

--mojUlQ0s9EVzWg2t
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="natd.cf"

use_sockets yes
same_ports yes
#
# machine1 redirections
#redirect_port tcp 192.168.2.237:ssh 1.2.3.4:ssh
#redirect_port tcp 192.168.2.237:smtp 1.2.3.4:smtp
#redirect_port tcp 192.168.2.237:pop3 1.2.3.4:pop3
#redirect_port tcp 192.168.2.237:imap4 1.2.3.4:imap4

# machine2 redirections
redirect_port tcp 192.168.2.201:ssh 1.2.3.5:ssh
redirect_port tcp 192.168.2.201:http 1.2.3.5:http

--mojUlQ0s9EVzWg2t--


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15  1:33:43 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id 3C93414CC7
	for <hackers@freebsd.org>; Wed, 15 Sep 1999 01:33:38 -0700 (PDT)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1)
	id 11RAVP-000BAM-00; Wed, 15 Sep 1999 10:33:31 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: John Baldwin <jobaldwi@vt.edu>
Cc: hackers@FreeBSD.ORG
Subject: Re: Problem with FreeBSD 
In-reply-to: Your message of "Tue, 14 Sep 1999 15:53:03 -0400."
             <0FI2004HUF88RI@gkar.cc.vt.edu> 
Date: Wed, 15 Sep 1999 10:33:31 +0200
Message-ID: <42925.937384411@axl.noc.iafrica.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Tue, 14 Sep 1999 15:53:03 -0400, John Baldwin wrote:

> > FreeBSD write "zf_read: error".
> 
> Your mfsroot floppy has a bad sector.  Try a different floppy.

Actually, as with many such cases, the floppy disk driver turned out to
be flakey. We resolved this via private mail.

Something to keep in mind in future when you see this problem report.

If I see it again, I'll hack up an FAQ entry.

Ciao,
Sheldon.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15  2:39:34 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58])
	by hub.freebsd.org (Postfix) with ESMTP id 93E271517E
	for <freebsd-hackers@freebsd.org>; Wed, 15 Sep 1999 02:39:30 -0700 (PDT)
	(envelope-from Dom.Mitchell@palmerharvey.co.uk)
Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk
 (Content Technologies SMTPRS 4.0.1) with ESMTP id <B3eac6d3a474d52d9df@mail.palmerharvey.co.uk>;
 Wed, 15 Sep 1999 10:39:13 +0100
Received: from voodoo.pandhm.co.uk (10.100.35.12 [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id SNZVMPBL; Wed, 15 Sep 1999 10:38:05 +0100
Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1)
	id 11RBX6-000Lgi-00; Wed, 15 Sep 1999 10:39:20 +0100
Date: Wed, 15 Sep 1999 10:39:19 +0100
To: Parag Patel <parag@cgt.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Command-line editing [was NetWare client in -current]
Message-ID: <19990915103919.A83264@voodoo.pandhm.co.uk>
References: <olli@dorifer.heim3.tu-clausthal.de> <7895.937349690@pinhead.parag.codegen.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <7895.937349690@pinhead.parag.codegen.com>
From: Dominic Mitchell <Dom.Mitchell@palmerharvey.co.uk>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Sep 14, 1999 at 03:54:50PM -0700, Parag Patel wrote:
> Anyway, command-line apps have been obsolete for years, so I guess we
> should go on and find better things to argue about.  :)

Heh.

So far, I've only found one GUI that I would really miss without X
Windows:  SWAT in netscape.
-- 
Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator

"vi has two modes the one in which it beeps and the one in which it doesnt."
	-- Anon.


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15  8: 1:47 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from chai.torrentnet.com (chai.torrentnet.com [198.78.51.73])
	by hub.freebsd.org (Postfix) with ESMTP id 2462C153E8
	for <freebsd-hackers@freebsd.org>; Wed, 15 Sep 1999 07:53:10 -0700 (PDT)
	(envelope-from bakul@torrentnet.com)
Received: from chai.torrentnet.com (localhost [127.0.0.1])
	by chai.torrentnet.com (8.8.8/8.8.5) with ESMTP id KAA17729
	for <freebsd-hackers@freebsd.org>; Wed, 15 Sep 1999 10:53:10 -0400 (EDT)
Message-Id: <199909151453.KAA17729@chai.torrentnet.com>
To: freebsd-hackers@freebsd.org
Subject: Bug in dd seeking beyond 2G
Date: Wed, 15 Sep 1999 10:53:10 -0400
From: Bakul Shah <bakul@torrentnet.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

PR bin/6509 (submitted in May 1998) already has a patch to
fix this but it was rejected because off_t was assumed by the
bug fixer/submitter to be a quat (int64_t).  I can't even get
an IDE disk below 2G byte easily!  And we are still years
away from zettabyte disks.  So I don't see the point of
blocking a _useful_ change that *considerably* improves the
situation just because it is not done the `right way'.

Let me say it another way.  The bugfix should be accepted and
another PR be filed that says there needs to be a constant
defining the largest possible off_t value.  Also note that
traditionally Unix does not define max values for every
derived scalar type (ANSI C does, unix does not).  Whether
that is a good idea or not is a separate discussion and
anyway such a change is much more global.  [IMHO it is better
to avoid an explosion of silly names by extending the
language with operators `maxof' and `minof' (analogous to
`sizeof') that return the max and min legal value for any
scalar type but that is not likely to happen.]

-- bakul


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15  8:28:54 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252])
	by hub.freebsd.org (Postfix) with ESMTP id A2138153A7
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 08:25:55 -0700 (PDT)
	(envelope-from olli@dorifer.heim3.tu-clausthal.de)
Received: (from olli@localhost)
	by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id RAA21673
	for freebsd-hackers@FreeBSD.ORG; Wed, 15 Sep 1999 17:25:54 +0200 (CEST)
	(envelope-from olli)
Date: Wed, 15 Sep 1999 17:25:54 +0200 (CEST)
From: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>
Message-Id: <199909151525.RAA21673@dorifer.heim3.tu-clausthal.de>
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: USB cameras
Organization: Administration Heim 3
Reply-To: freebsd-hardware@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: TIN [version 1.2 RZTUC(3) PL2]
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I think this rather belongs to -hardware...

Leif Neland wrote in list.freebsd-hackers:
 > A simple question: Are USB cameras supported? Is anybody working on it?

Do you mean photo cameras (i.e. for still images) or video
cameras?  Those are two completely different things.

The Kodak DC240 digital camera is supported by "oPhoto"
(http://www.fromme.com/ophoto/).  I'm not aware of any
support for USB video cameras.

 > Oh, btw, how long can USB be extended?

There should be information about that on www.usb.org.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
                                         (Terry Pratchett)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15  8:41: 2 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from www.crb-web.com (ns1.crb-web.com [209.70.120.131])
	by hub.freebsd.org (Postfix) with SMTP id 0C8E31532D
	for <freebsd-hackers@freebsd.org>; Wed, 15 Sep 1999 08:36:59 -0700 (PDT)
	(envelope-from wayne@crb.crb-web.com)
Received: (qmail 31599 invoked by uid 1001); 15 Sep 1999 16:29:54 -0000
Date: Wed, 15 Sep 1999 12:29:54 -0400 (EDT)
From: Wayne Cuddy <wayne@crb-web.com>
Reply-To: wayne@crb-web.com
Cc: FreeBSD Hackers List <freebsd-hackers@freebsd.org>
Subject: Re: aio_*
In-Reply-To: <19990914075926.A60617@kilt.nothing-going-on.org>
Message-ID: <Pine.LNX.4.10.9909151141150.31373-100000@crb.crb-web.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 14 Sep 1999, Nik Clayton wrote:

> What we need is people like yourself, who are having to go through the 
> learning curve, to document stuff as you're finding it out.  It doesn't
> matter if your notes are a bit rough and ready, because the next person
> to use them can improve on them, and the next person, and the next person,
> and so on, until we have great kernel documentation.
> 
> Any takers?

I would be down for this especially since I need some help with the device
driver interface to the kernel.  There was a tutorial on the web site that
cannot locate any longer.  I certainly would not mind putting together a
tutorial/API doc if I could get help on some of the details.

Wayne



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15  9:21:23 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from hermes.mixx.net (hermes.mixx.net [194.152.58.71])
	by hub.freebsd.org (Postfix) with ESMTP id A86CB15595
	for <hackers@FreeBSD.org>; Wed, 15 Sep 1999 08:55:41 -0700 (PDT)
	(envelope-from graichen@innominate.de)
Received: from innominate.de (gatekeeper.innominate.de [212.5.16.129])
	by hermes.mixx.net (8.9.3/8.9.3) with SMTP id RAA20653
	for <hackers@FreeBSD.org>; Wed, 15 Sep 1999 17:55:28 +0200
Received: (qmail 23761 invoked from network); 15 Sep 1999 15:53:37 -0000
Received: from cello.innominate.local (192.168.0.13)
  by lingo01.innominate.local with SMTP; 15 Sep 1999 15:53:37 -0000
Received: (from graichen@localhost)
	by cello.innominate.local (8.9.3/8.9.3) id RAA05745;
	Wed, 15 Sep 1999 17:55:18 +0200 (CEST)
	(envelope-from graichen)
Date: Wed, 15 Sep 1999 17:55:18 +0200 (CEST)
Message-Id: <199909151555.RAA05745@cello.innominate.local>
From: Thomas Graichen <graichen@innominate.de>
To: hackers@FreeBSD.org
Subject: (fwd) Re: dynamically growing ffs
Reply-To: graichen@innominate.de
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

wouldn't this be also interesting to see for FreeBSD ? - anyone
with the required skills having time to have a look at it ?

t

-- forwarded message --
From: der Mouse  <mouse@Rodents.Montreal.QC.CA>
Subject: Re: dynamically growing ffs

> Is there anything to prevent someone hacking up fsck_ffs to increase
> fs->fs_size and everything else that is calculated from it, in order
> to add addotopma; unstriped ccd or raidframe space?

"addotopma;"?  You need to move your right hand one key left. :-)

Well, it's not fsck_ffs, but quite a while ago I wrote a program
fsresize to resize FFS filesystems on-disk.  It turned up a bug in the
rotational layout code, which as I recall was in fsck - my code was not
generating correct layout tables, fsck didn't notice, and the kernel
panicked.

I thought I'd created a version which deliberately corrupts the
cylinder group data to force fsck to recompute them, but I can't find
it now.  (Obviously, it would be better to make fsresize DTRT; since
this was discovered (IIRC, credit for this discovery belongs to bouyer)
I haven't had time to mess with it much.)

Modulo that bug, it's believed to work, and can also shrink
filesystems, though this tends to be slow because it (in general) has
to move data, not just write new cg header blocks.

In case any of you developers want to do anything with it, I've put
copies of the program and its manpage in ~mouse on cvs.netbsd.org,
under the names fsresize.c and fsresize.8; for the non-developers among
you, I'll be happy to mail out copies.

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B
-- end of forwarded message --

-- 
graichen@innominate.de
                                                        innominate AG
                                                    networking people
fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15  9:50:36 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29])
	by hub.freebsd.org (Postfix) with ESMTP id 857FE15753
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 09:45:37 -0700 (PDT)
	(envelope-from cmsedore@mailbox.syr.edu)
Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.B053D360@mailer.syr.edu>; Wed, 15 Sep 1999 12:34:44 -0400
Received: from localhost (cmsedore@localhost)
	by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id MAA19770;
	Wed, 15 Sep 1999 12:34:37 -0400 (EDT)
X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs
Date: Wed, 15 Sep 1999 12:34:37 -0400 (EDT)
From: Christopher Sedore <cmsedore@mailbox.syr.edu>
X-Sender: cmsedore@rodan.syr.edu
To: Ruslan Ermilov <ru@ucb.crimea.ua>
Cc: Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: kern/13075 (was: Re: aio_*)
In-Reply-To: <19990915100619.C86648@relay.ucb.crimea.ua>
Message-ID: <Pine.SOL.4.10.9909151232330.1425-100000@rodan.syr.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Wed, 15 Sep 1999, Ruslan Ermilov wrote:

> > The aio_* stuff (I use a custom patched version in 4.x) offers performance
> > advantages over select() with large numbers of descriptors.  In terms of
> > efficiency, I don't have any trouble saturating full-duplex 100mbit link
> > with aio routines on a reasonably fast box (PII-400 512MB).
> > 
> > As more work gets done to the aio stuff, there are some potential early
> > advantages available to multiprocessor machines (since the program
> > 'driving' the aio could run concurrently with the kernel code moving
> > network or disk data).
> > 
> > -Chris
> 
> Do you by any change have an idea how to fix PR kern/13075
> (signal is not posted for async I/O on raw devices)

Yes.  There is no code to post the signal unless the job is of the lio
variety.  Writing a fix took about 15 minutes (including reboot).
Extensive testing not included, though the test program provided with the
PR now functions.

-Chris



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15  9:50:37 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29])
	by hub.freebsd.org (Postfix) with ESMTP id 93E6115378
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 09:45:37 -0700 (PDT)
	(envelope-from cmsedore@mailbox.syr.edu)
Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.32EB1C60@mailer.syr.edu>; Wed, 15 Sep 1999 12:45:33 -0400
Received: from localhost (cmsedore@localhost)
	by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id MAA25149;
	Wed, 15 Sep 1999 12:45:30 -0400 (EDT)
X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs
Date: Wed, 15 Sep 1999 12:45:29 -0400 (EDT)
From: Christopher Sedore <cmsedore@mailbox.syr.edu>
X-Sender: cmsedore@rodan.syr.edu
To: Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: High Performance I/O (more)
In-Reply-To: <19990915070800.34512.qmail@scam.xcf.berkeley.edu>
Message-ID: <Pine.SOL.4.10.9909151235280.1425-100000@rodan.syr.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Wed, 15 Sep 1999, Jayson Nordwick wrote:

> I did research this weekend on high performance I/O.  I looked at differerent
> approaches and to me they all appear the same (I know that I will get some
> flamage for this).  The two most prominent models that I saw were IO
> Completion Ports and Synchronous Events (such as the Gaurav
> http://www.cs.rice.edu/~gaurav/papers/usenix99.ps).
> 
> I think that both of these models are basically the same.  They both have
> an event queue that you pick up events from.  The only way that they differ
> is in what they call an event.  Completion ports take asynchronous opperations
> and queue an event when the opperation completes (hence the name).  Synchronous
> events do the opposite: they queue an event when an opperation is possible
> and then the synchronous (usually, non-blocking) opperation is performed.
> From this, you can decouple and event queue from what you call an event.
> 
> >From what I can see either model will give roughly the same performance,
> as they both do roughly the same amount of work.  The one benefit that seems
> to exist for the Completion Ports model is that there are fewer contex
> switches.
> 
> Now, looking at POSIX.1b signals and signal queues and getting some
> information from Stephen Tweedie it looks like completion ports are doable
> without anything new, I think that I have decided.
> 
> If you find an available signal, set the handler for it, the block it,
> this signal number now effectively becomes the completion port.  You then
> can fcntl() a file descriptor with F_SETSIG and the signal number.  Then to
> fetch the blocked signals, use sigwaitinfo().  I guess you could also use
> aio_{read,write}() and set sigevent appropriately.  This actually seems
> preferable since you can then use aio_return() to find the return value
> out and use aio_cancel() to cancel the request if wanted.
> 
> The one drawback that I see to this is that it can only really handle
> aio_{read,write}() and {read,write}()/fcntl().  Any other events such as
> thread/child deaths cannot really be worked into this scheme unless you
> could set the signal they deliver on termination.
> 
> If you really wanted to, you could have signals delivered for the ability
> to read/write to a file descriptor and then you would have Gaurav's model.
> 
> Basically, unless anybody can see anything wrong with this get to work
> implementing!

As you note, IOCPs and the event scheme suggested by Gaurav et al have
some differences related to whether they occur after an async operation
completes, or when a descriptor is ready for a particular activity.  The
differences may not seem important, but for implementing high performance
io systems, they probably do matter.  

The signal approach has some limitations, in that (correct me if I am
wrong), FreeBSD doesn't have realtime signals yet, and POSIX specifies how
signals and aio operations are to work already.

I read with interest a post a week or three back talking about some
efforts in the Linux community to come up with a standardized way of doing
this.  

My ideas for this are a little different than what I've seen proposed thus
far, more along the lines of creating something that acts as both an event
queue and a IOCP.  Ideally this would be a descriptor that could be shared
across processes (or threads), and could be accessed using read().  I
don't much care for the suggestion that threads ought to have an event
queue of their own--rather if you want a per-thread completion
notification, simply create a descriptor for each thread that needs this
function.  What ever is created, it should be sufficiently extensible to
allow for all the events we can imagine now, as well as being flexible for
future enhancement.  (FWIW, I've also been thinking that I might like to
be able to submit aio requests by write()ing said descriptor.  Just a
thought.)

I hope we'll see an update on where the Linux efforts are--I'd be
interested in joining the conversation.

-Chris



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 10:13:23 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13])
	by hub.freebsd.org (Postfix) with ESMTP id 5333A14EED
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 10:13:16 -0700 (PDT)
	(envelope-from danhil@cwnt.com)
Received: from unspecified.host (ras5-p132.hfa.netvision.net.il [62.0.147.132] (may be forged))
	by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id TAA12798
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 19:13:13 +0200 (IST)
Received: from 192.168.0.46 ([192.168.0.46]) by 192.168.0.1 (WinRoute 3.04g) with SMTP; Wed, 15 Sep 1999 19:12:26 +0300
Message-ID: <013e01beffa5$e9adf0d0$2e00a8c0@nt46>
From: "Daniel Hilevich" <danhil@cwnt.com>
To: <freebsd-hackers@FreeBSD.ORG>
Subject: How can I send signals to a network interface
Date: Wed, 15 Sep 1999 19:12:46 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_013B_01BEFFAE.4B618FF0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a multi-part message in MIME format.

------=_NextPart_000_013B_01BEFFAE.4B618FF0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Hi,
I need to send signals to a network interface I worte but I can't find =
how.
I know that in some other Bsd flavours you can use the sysctl functions =
which is part
of the ifnet struct. In FreeBsd I didn't find anything similiar to it.
I need to send custom directions to the interface so I can't use the =
ioctl mechanism.

Please send the answer to me.

Thank you
--
Daniel Hilevich  =20
mailto:danhil@cwnt.com
Charlotte's Web Networks LTD.
Tel: +972-4-9592203 ext. 214    =20

------=_NextPart_000_013B_01BEFFAE.4B618FF0
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1255" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3D"Arial (Hebrew)" size=3D2>I need to send signals to a =
network=20
interface I worte but I can't find how.</FONT></DIV>
<DIV><FONT face=3D"Arial (Hebrew)" size=3D2>I know that in some other =
Bsd flavours=20
you can use the sysctl functions which is part</FONT></DIV>
<DIV><FONT face=3D"Arial (Hebrew)" size=3D2>of the ifnet struct. In =
FreeBsd I didn't=20
find anything similiar to it.</FONT></DIV>
<DIV><FONT face=3D"Arial (Hebrew)" size=3D2>I need to send custom =
directions to the=20
interface so I can't use the ioctl mechanism.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3D"Arial (Hebrew)" size=3D2>Please send the answer to=20
me.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3D"Arial (Hebrew)" size=3D2>Thank you</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>--<BR>Daniel Hilevich&nbsp;&nbsp; =
<BR><A=20
href=3D"mailto:danhil@cwnt.com">mailto:danhil@cwnt.com</A><BR>Charlotte's=
 Web=20
Networks LTD.<BR>Tel: +972-4-9592203 ext. 214&nbsp;&nbsp;&nbsp;&nbsp;=20
</FONT></DIV></BODY></HTML>

------=_NextPart_000_013B_01BEFFAE.4B618FF0--




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 10:15:21 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
	by hub.freebsd.org (Postfix) with ESMTP id B691914F49
	for <hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 10:15:10 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id KAA00864;
	Wed, 15 Sep 1999 10:06:59 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199909151706.KAA00864@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Sheldon Hearn <sheldonh@uunet.co.za>
Cc: John Baldwin <jobaldwi@vt.edu>, hackers@FreeBSD.ORG
Subject: Re: Problem with FreeBSD 
In-reply-to: Your message of "Wed, 15 Sep 1999 10:33:31 +0200."
             <42925.937384411@axl.noc.iafrica.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 15 Sep 1999 10:06:59 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > > FreeBSD write "zf_read: error".
> > 
> > Your mfsroot floppy has a bad sector.  Try a different floppy.
> 
> Actually, as with many such cases, the floppy disk driver turned out to
> be flakey. We resolved this via private mail.

Driver, or drive?  The BIOS is the driver at this point in time.

-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 10:34:14 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126])
	by hub.freebsd.org (Postfix) with ESMTP id 7B81714FF3
	for <hackers@freebsd.org>; Wed, 15 Sep 1999 10:33:57 -0700 (PDT)
	(envelope-from roger@cs.strath.ac.uk)
Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10])
	by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id SAA23188
	Wed, 15 Sep 1999 18:33:56 +0100 (BST)
Message-ID: <37DFD883.1CFB@cs.strath.ac.uk>
Date: Wed, 15 Sep 1999 18:33:55 +0100
From: Roger Hardiman <roger@cs.strath.ac.uk>
Organization: University of Strathclyde
X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha)
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: Attn AVerMedia Bt878 owners
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,
Attn AVerMedia owners of TV cards with Bt878's

(sorry - not the 848 users)

I've got the specs from AVerMedia which mean I can
finally get the Tuner Type autoselected for your cards.

If you have an AVerMedia card which is one of the newer
ones with a Bt878, can you please email me.
I do not have one myself and need some test beds for my
new code before I commit it to -current.

Cheers
Roger
--
Roger Hardiman
Bt848/878 driver maintainer
roger@cs.strath.ac.uk
roger@freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 10:35:52 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from xylan.com (postal.xylan.com [208.8.0.248])
	by hub.freebsd.org (Postfix) with ESMTP id 7B8511515F
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 10:35:49 -0700 (PDT)
	(envelope-from wes@softweyr.com)
Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT]))
	id KAA25173; Wed, 15 Sep 1999 10:35:10 -0700 (PDT)
Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB]))
	id KAA14226; Wed, 15 Sep 1999 10:23:29 -0700
Received: from softweyr.com (dyn4.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL]))
	id AA28547; Wed, 15 Sep 99 10:35:08 PDT
Message-Id: <37DFD8CC.DB009150@softweyr.com>
Date: Wed, 15 Sep 1999 11:35:08 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386)
X-Accept-Language: en
Mime-Version: 1.0
To: Parag Patel <parag@cgt.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Command-line editing [was NetWare client in -current]
References: <9219.937364032@pinhead.parag.codegen.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Parag Patel wrote:
> 
> I said:
> 
> >Anyway, command-line apps have been obsolete for years, so I guess we
> >should go on and find better things to argue about.  :)
> 
> I guess people missed the ":)" so I'd better explain.
> 
> Most computers are embedded and becoming both more ubiquitous and
> invisble.  Most of these don't even *have* interfaces, GUI or CLI.

Yes, they do, the UI just runs on another computer.  Or, more properly, the
embedded device has a PUI -- protocol user interface.  I like the TLA.

-- 
            "Where am I, and what am I doing in this handbasket?"

Wes Peters                                                         Softweyr LLC
http://softweyr.com/                                           wes@softweyr.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 10:43:55 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
	by hub.freebsd.org (Postfix) with ESMTP id 0EC2515176
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 10:43:31 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id KAA01010;
	Wed, 15 Sep 1999 10:33:51 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199909151733.KAA01010@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Christopher Sedore <cmsedore@mailbox.syr.edu>
Cc: Ruslan Ermilov <ru@ucb.crimea.ua>,
	Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: kern/13075 (was: Re: aio_*) 
In-reply-to: Your message of "Wed, 15 Sep 1999 12:34:37 EDT."
             <Pine.SOL.4.10.9909151232330.1425-100000@rodan.syr.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 15 Sep 1999 10:33:51 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> 
> On Wed, 15 Sep 1999, Ruslan Ermilov wrote:
> 
> > > The aio_* stuff (I use a custom patched version in 4.x) offers performance
> > > advantages over select() with large numbers of descriptors.  In terms of
> > > efficiency, I don't have any trouble saturating full-duplex 100mbit link
> > > with aio routines on a reasonably fast box (PII-400 512MB).
> > > 
> > > As more work gets done to the aio stuff, there are some potential early
> > > advantages available to multiprocessor machines (since the program
> > > 'driving' the aio could run concurrently with the kernel code moving
> > > network or disk data).
> > > 
> > > -Chris
> > 
> > Do you by any change have an idea how to fix PR kern/13075
> > (signal is not posted for async I/O on raw devices)
> 
> Yes.  There is no code to post the signal unless the job is of the lio
> variety.  Writing a fix took about 15 minutes (including reboot).
> Extensive testing not included, though the test program provided with the
> PR now functions.

You plan to file a followup to the PR, I hope.  8)

-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 11:56:54 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
	by hub.freebsd.org (Postfix) with ESMTP id 556D914DFD
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 11:56:51 -0700 (PDT)
	(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
	by dan.emsphone.com (8.9.3/8.9.3) id NAA84374;
	Wed, 15 Sep 1999 13:56:47 -0500 (CDT)
	(envelope-from dan)
Date: Wed, 15 Sep 1999 13:56:47 -0500
From: Dan Nelson <dnelson@emsphone.com>
To: Bakul Shah <bakul@torrentnet.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Bug in dd seeking beyond 2G
Message-ID: <19990915135647.A84130@dan.emsphone.com>
References: <199909151453.KAA17729@chai.torrentnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre1i
In-Reply-To: <199909151453.KAA17729@chai.torrentnet.com>
X-OS: FreeBSD 4.0-CURRENT
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In the last episode (Sep 15), Bakul Shah said:
> PR bin/6509 (submitted in May 1998) already has a patch to fix this
> but it was rejected because off_t was assumed by the bug
> fixer/submitter to be a quat (int64_t).  I can't even get an IDE disk
> below 2G byte easily!  And we are still years away from zettabyte
> disks.  So I don't see the point of blocking a _useful_ change that
> *considerably* improves the situation just because it is not done the
> `right way'.

RCS file: /home/ncvs/src/bin/dd/dd.c,v                                          

revision 1.17
date: 1999/06/19 19:49:32;  author: green;  state: Exp;  lines: +25 -21
Miscellaneous dd(1) changes: mainly fixing variable types (size_t,
ssize_t, off_t, int, u_int64_t, etc.). dd(1) should now work properly
with REALLY big amounts of data.

Should be a -stable candidate by now (3 months of testing?)
 
-- 
	Dan Nelson
	dnelson@emsphone.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 12:15:33 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from chai.torrentnet.com (chai.torrentnet.com [198.78.51.73])
	by hub.freebsd.org (Postfix) with ESMTP id 6D82614E2B
	for <freebsd-hackers@freebsd.org>; Wed, 15 Sep 1999 12:15:30 -0700 (PDT)
	(envelope-from bakul@torrentnet.com)
Received: from chai.torrentnet.com (localhost [127.0.0.1])
	by chai.torrentnet.com (8.8.8/8.8.5) with ESMTP id PAA18418;
	Wed, 15 Sep 1999 15:15:22 -0400 (EDT)
Message-Id: <199909151915.PAA18418@chai.torrentnet.com>
To: Dan Nelson <dnelson@emsphone.com>
Cc: freebsd-hackers@freebsd.org
Subject: Re: Bug in dd seeking beyond 2G 
In-reply-to: Your message of "Wed, 15 Sep 1999 13:56:47 CDT."
             <19990915135647.A84130@dan.emsphone.com> 
Date: Wed, 15 Sep 1999 15:15:21 -0400
From: Bakul Shah <bakul@torrentnet.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> date: 1999/06/19 19:49:32;  author: green;  state: Exp;  lines: +25 -21
> Miscellaneous dd(1) changes: mainly fixing variable types (size_t,
> ssize_t, off_t, int, u_int64_t, etc.). dd(1) should now work properly
> with REALLY big amounts of data.
> 
> Should be a -stable candidate by now (3 months of testing?)

Thanks!  I should've checked the source instead of checking
PRs!


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 12:21: 7 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from luna.lyris.net (luna.shelby.com [207.90.155.6])
	by hub.freebsd.org (Postfix) with ESMTP
	id BA83414C0B; Wed, 15 Sep 1999 12:21:01 -0700 (PDT)
	(envelope-from kip@lyris.com)
Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4)
	id MAA07984; Wed, 15 Sep 1999 12:20:49 -0700 (PDT)
Received: from  (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Wed, 15 Sep 1999 12:20:49 -0700
Date: Wed, 15 Sep 1999 12:20:49 -0700 (PDT)
From: Kip Macy <kip@lyris.com>
X-Sender: kip@luna
To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org
Subject: does gdb on 3.3RC have thread support?
Message-ID: <Pine.SOL.4.05.9909151219410.7805-100000@luna>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-SMTP-HELO: luna
X-SMTP-MAIL-FROM: kip@lyris.com
X-SMTP-RCPT-TO: freebsd-stable@freebsd.org,freebsd-hackers@freebsd.org
X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6]
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

When I run my program under ddd, press Ctrl-C to return control to gdb and
then type info threads at the gdb prompt it returns nothing.

When I run it under gdb on the command line and do the same as above, gdb
dumps core.

How should I proceed? Should I grab the source for uthreads from current?


                                -Kip





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 12:28:27 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252])
	by hub.freebsd.org (Postfix) with ESMTP id DD9F515311
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 12:28:20 -0700 (PDT)
	(envelope-from olli@dorifer.heim3.tu-clausthal.de)
Received: (from olli@localhost)
	by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA26499
	for freebsd-hackers@FreeBSD.ORG; Wed, 15 Sep 1999 21:28:18 +0200 (CEST)
	(envelope-from olli)
Date: Wed, 15 Sep 1999 21:28:18 +0200 (CEST)
From: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>
Message-Id: <199909151928.VAA26499@dorifer.heim3.tu-clausthal.de>
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: Bug in dd seeking beyond 2G
Organization: Administration Heim 3
Reply-To: freebsd-hackers@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: TIN [version 1.2 RZTUC(3) PL2]
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bakul Shah wrote in list.freebsd-hackers:
 > [...]
 > Let me say it another way.  The bugfix should be accepted and
 > another PR be filed that says there needs to be a constant
 > defining the largest possible off_t value.  Also note that
 > traditionally Unix does not define max values for every
 > derived scalar type (ANSI C does, unix does not).

So the only problem is that there is no maximum value defined
for off_t?  The following piece of code will find the maximum
value for any (signed or unsigned) integer type:

    #include <limits.h>
    
    int i;
    
    max = ((type) -1 < 0) ? SCHAR_MAX : UCHAR_MAX;
    for (i = 1; i < sizeof(type); i++)
            max = (max << CHAR_BIT) + UCHAR_MAX;

It only works on two's-complement machines, though, but I'm not
aware of any FreeBSD port to an architecture that doesn't use
two's-complement numbers...

On the other hand, I wonder why dd needs to know the maxium
value of an off_t.  That sounds broken to me.  I haven't looked
at the patch, but if it's dependant on the exact size of an
off_t, then the patch is no good.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
                                         (Terry Pratchett)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 12:31:30 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
	by hub.freebsd.org (Postfix) with ESMTP id 2CCF214E2B
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 12:31:29 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA01558;
	Wed, 15 Sep 1999 12:24:50 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199909151924.MAA01558@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Daniel Hilevich" <danhil@cwnt.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: How can I send signals to a network interface 
In-reply-to: Your message of "Wed, 15 Sep 1999 19:12:46 BST."
             <013e01beffa5$e9adf0d0$2e00a8c0@nt46> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 15 Sep 1999 12:24:48 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> This is a multi-part message in MIME format.

Don't do this.  Plain text, please.

> Hi,
> I need to send signals to a network interface I worte but I can't find
> how.

ioctl()

> I know that in some other Bsd flavours you can use the sysctl functions =
> which is part
> of the ifnet struct. In FreeBsd I didn't find anything similiar to it.

Sysctl functions aren't "part of the ifnet struct".  You can define 
sysctls for your driver, if you wish, but that's the wrong way to go 
about doing it.

> I need to send custom directions to the interface so I can't use the =
> ioctl mechanism.

I can't see why you think this is the case.  See the wl(4) driver for 
example of exactly what you're talking about, using ioctl().  See 
wlconfig(8) for the user-space portion of the interface.
-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 12:40: 3 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from tepsa.lame.pl (tepsa.lame.pl [195.117.126.177])
	by hub.freebsd.org (Postfix) with ESMTP id 9D8D81532D
	for <hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 12:39:48 -0700 (PDT)
	(envelope-from cys@denied.cx)
Received: from localhost (cys@localhost)
	by tepsa.lame.pl (8.9.3/+++ATH) with ESMTP id VAA78567
	for <hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 21:39:43 +0200 (CEST)
Date: Wed, 15 Sep 1999 21:39:42 +0200 (CEST)
From: Krzysztof Krawczyk <cys@denied.cx>
X-Sender: cys@tepsa.lame.pl
To: hackers@FreeBSD.ORG
Subject: ping: sendto: Message too long
In-Reply-To: <Pine.BSF.4.10.9909131744020.88005-100000@resnet.uoregon.edu>
Message-ID: <Pine.BSF.4.05.9909152130470.78516-100000@tepsa.lame.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

Could someone say me, why the maximum packetsize in ping command is 8184
(ping -s 8184)? If I want to do a bigger packetsize than this i got
message like this:

   tepsa:cys:/home# ping -s 65000 127.0.0.1
   PING 127.0.0.1 (127.0.0.1): 65000 data bytes
   ping: sendto: Message too long
   ping: sendto: Message too long
   ping: sendto: Message too long
   ping: sendto: Message too long
   ping: sendto: Message too long
   ^C
   --- 127.0.0.1 ping statistics ---
   5 packets transmitted, 0 packets received, 100% packet loss

Is there any way to bypass this limit? Should I recompile my
kernel/ping.c?


     Cys - Krzysztof Krawczyk
     IRC on DALnet: #polska #polcafe #wroclaw

     cys@for.lames.access.is.denied.cx

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
        "What sane person could live in this world and not be crazy?"
                                           -- Ursula K. LeGuin
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 13: 0:57 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16])
	by hub.freebsd.org (Postfix) with ESMTP id DD31314D6C
	for <freebsd-hackers@freebsd.org>; Wed, 15 Sep 1999 12:59:56 -0700 (PDT)
	(envelope-from crossd@cs.rpi.edu)
Received: from cs.rpi.edu (z.cs.rpi.edu [128.213.7.2])
	by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id PAA22581
	for <freebsd-hackers@freebsd.org>; Wed, 15 Sep 1999 15:59:55 -0400 (EDT)
Message-Id: <199909151959.PAA22581@cs.rpi.edu>
To: freebsd-hackers@freebsd.org
Subject: perl stangeness on 3.3-RC
Date: Wed, 15 Sep 1999 15:59:55 -0400
From: "David E. Cross" <crossd@cs.rpi.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

We have a very hetergenous environment here (even among the FreeBSD boxes).
Each PC tends to be just a little bit different.  This expecially causes
problems since we wish to have XDM on each machine on boot and have X
on a NFS partition.  TO alleviate this we invented a simple Perl script
to replace /usr/X11R6/bin/X to run the correct program on each machine:


#!/usr/bin/perl -w
use Sys::Hostname;

read_servers();
$commandline="/usr/X11R6/bin/XF86_VGA16";
$host=hostname();
print STDERR "host is $host\n";
$screen=$ARGV[0];
$display= $host . $screen;
print STDERR "display is $display\n";
if ($server{$display}) {
 $commandline = join (' ', $server{$display}, @ARGV);
}
elsif ($server{$host}) {
 $commandline = join (' ',$server{$host}, @ARGV);
}
exec $commandline;

sub read_servers {
 open (XSERVERLIST, "/usr/local/etc/xservers");
 while ($hostline = <XSERVERLIST>) {
  chomp ($hostline);
  @fields = split ' ', $hostline, 2;
  $server{$fields[0]} = $fields[1];
 }
}

This worked fine up until about 3.3-RC, then it stopped with the following
error:

Use of uninitialized value at /usr/libdata/perl/5.00503/Sys/Hostname.pm line 100, <XSERVERLIST> chunk 13.
Use of uninitialized value at /usr/libdata/perl/5.00503/Sys/Hostname.pm line 109, <XSERVERLIST> chunk 13.
Can't exec "/com/host": No such file or directory at /usr/libdata/perl/5.00503/Sys/Hostname.pm line 115, <XSERVERLIST> chunk 13.
Cannot get host name of local machine at /usr/X11R6/bin/X line 6

Note that this is *only* a problem when this script is run by xdm by init.
If I run the script by hand, or I run xdm by hand it works OK.  Also consider
the results of a ktrace on init (PID 1) when xdm was started (alot of stuff
has been deleted to ease readability:


   445 perl     RET   execve 0

   445 perl forks and execs 'hostname'
	
   447 hostname RET   execve 0
   447 hostname CALL  __sysctl(0xbfbfdcd0,0x2,0xbfbfdcf8,0xbfbfdcd8,0,0)
   447 hostname RET   __sysctl 0
   447 hostname CALL  fstat(0x1,0xbfbfd9e4)
   447 hostname RET   fstat 0
   447 hostname CALL  readlink(0x8050a1c,0xbfbfd9e4,0x3f)
   447 hostname NAMI  "/etc/malloc.conf"
   447 hostname RET   readlink -1 errno 2 No such file or directory
   447 hostname CALL  mmap(0,0x1000,0x3,0x1002,0xffffffff,0,0,0)
   447 hostname RET   mmap 671424512/0x28052000
   447 hostname CALL  break(0x8055000)
   447 hostname RET   break 0
   447 hostname CALL  break(0x8059000)
   447 hostname RET   break 0
   447 hostname CALL  write(0x1,0x8055000,0x10)
   447 hostname GIO   fd 1 wrote 16 bytes
       "loot.cs.rpi.edu
       "
   445 perl     GIO   fd 1 read 16 bytes
       "loot.cs.rpi.edu
       "
   445 perl     RET   read 16/0x10
   445 perl     CALL  read(0x1,0x80e0000,0x4000)
   447 hostname RET   write 16/0x10
   447 hostname CALL  exit(0)
   446 sh       RET   wait4 447/0x1bf
   446 sh       CALL  exit(0)
   445 perl     GIO   fd 1 read 0 bytes
       ""
   445 perl     RET   read 0
   445 perl     CALL  close(0x1)
   445 perl     RET   close 0
   445 perl     GIO   fd 2 wrote 106 bytes
       "Use of uninitialized value at /usr/libdata/perl/5.00503/Sys/Hostname.p\
	m line 100, <XSERVERLIST> chunk 13.
       "
	.
	.
	.
   448 sh       NAMI  "/bin/uname"
   448 sh       RET   stat -1 errno 2 No such file or directory
   448 sh       CALL  stat(0x809ccb8,0xbfbfdc54)
   448 sh       NAMI  "/usr/bin/uname"
   448 sh       RET   stat 0
   448 sh       CALL  break(0x80a3000)

	.
	.
	.

   449 uname    RET   execve 0
   449 uname    GIO   fd 1 wrote 16 bytes
       "loot.cs.rpi.edu
       "
   445 perl     GIO   fd 1 read 16 bytes
       "loot.cs.rpi.edu
       "
   448 sh       RET   wait4 449/0x1c1
   448 sh       CALL  exit(0)
   445 perl     GIO   fd 1 read 0 bytes
       ""
   445 perl     RET   read 0
   445 perl     CALL  close(0x1)
   445 perl     RET   close 0
   445 perl     GIO   fd 2 wrote 106 bytes
       "Use of uninitialized value at /usr/libdata/perl/5.00503/Sys/Hostname.p\
	m line 109, <XSERVERLIST> chunk 13.
       "
   450 perl     CALL  execve(0x80dd140,0x808c2e0,0x8076e80)
   450 perl     NAMI  "/com/host"
   450 perl     RET   execve -1 errno 2 No such file or directory
   450 perl     CALL  write(0x2,0x8070e00,0x81)
   450 perl     GIO   fd 2 wrote 129 bytes
       "Can't exec "/com/host": No such file or directory at /usr/libdata/perl\
	/5.00503/Sys/Hostname.pm line 115, <XSERVERLIST> chunk 13.
       "
   450 perl     RET   write 129/0x81
   450 perl     CALL  exit(0x1)
       "Cannot get host name of local machine at /usr/X11R6/bin/X line 6
       "

Any ideas what is going on here?  It looks like it gets what it wants and then
just ignores it?!?

--
David Cross                               | email: crossd@cs.rpi.edu 
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
Rensselaer Polytechnic Institute,         | Ph: 518.276.2860            
Department of Computer Science            | Fax: 518.276.4033
I speak only for myself.                  | WinNT:Linux::Linux:FreeBSD


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 13: 7: 3 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91])
	by hub.freebsd.org (Postfix) with ESMTP id E30C314C3D
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 13:06:59 -0700 (PDT)
	(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.9.3/8.9.3) with SMTP id OAA28343;
	Wed, 15 Sep 1999 14:06:53 -0600 (MDT)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id OAA04769; Wed, 15 Sep 1999 14:06:52 -0600
Date: Wed, 15 Sep 1999 14:06:52 -0600
Message-Id: <199909152006.OAA04769@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: "Daniel Hilevich" <danhil@cwnt.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: How can I send signals to a network interface 
In-Reply-To: <199909151924.MAA01558@dingo.cdrom.com>
References: <013e01beffa5$e9adf0d0$2e00a8c0@nt46>
	<199909151924.MAA01558@dingo.cdrom.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: nate@mt.sri.com (Nate Williams)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > I know that in some other Bsd flavours you can use the sysctl functions =
> > which is part
> > of the ifnet struct. In FreeBsd I didn't find anything similiar to it.
> 
> Sysctl functions aren't "part of the ifnet struct".  You can define 
> sysctls for your driver, if you wish, but that's the wrong way to go 
> about doing it.

Especially since sysctl's are still not yet able to deal with multiple
interfaces very easily.  (Feel free to correct me if I'm wrong).

Therefore, if you have two 'network interfaces' that are serviced by the
same driver, it's hard to not have a sysctl change effect them both.


Nate


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 13:11:20 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
	by hub.freebsd.org (Postfix) with ESMTP id 9B4C714D9A
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 13:11:19 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id NAA01789;
	Wed, 15 Sep 1999 13:04:05 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199909152004.NAA01789@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: nate@mt.sri.com (Nate Williams)
Cc: "Daniel Hilevich" <danhil@cwnt.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: How can I send signals to a network interface 
In-reply-to: Your message of "Wed, 15 Sep 1999 14:06:52 MDT."
             <199909152006.OAA04769@mt.sri.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 15 Sep 1999 13:04:05 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > > I know that in some other Bsd flavours you can use the sysctl functions =
> > > which is part
> > > of the ifnet struct. In FreeBsd I didn't find anything similiar to it.
> > 
> > Sysctl functions aren't "part of the ifnet struct".  You can define 
> > sysctls for your driver, if you wish, but that's the wrong way to go 
> > about doing it.
> 
> Especially since sysctl's are still not yet able to deal with multiple
> interfaces very easily.  (Feel free to correct me if I'm wrong).

You can do it, but it's not pretty, and certainly not something I'd 
recommend in the face of a fully functional alternative.

> Therefore, if you have two 'network interfaces' that are serviced by the
> same driver, it's hard to not have a sysctl change effect them both.

Actually, you can.  Have a look at the way that the kernel environment 
code handles retrieval of individual variables, and apply the same 
principle to indexing interfaces.

-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 13:39:13 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from luna.lyris.net (luna.shelby.com [207.90.155.6])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2DB8D14D00; Wed, 15 Sep 1999 13:39:10 -0700 (PDT)
	(envelope-from kip@lyris.com)
Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4)
	id NAA08935; Wed, 15 Sep 1999 13:38:56 -0700 (PDT)
Received: from  (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Wed, 15 Sep 1999 13:38:56 -0700
Date: Wed, 15 Sep 1999 13:38:56 -0700 (PDT)
From: Kip Macy <kip@lyris.com>
X-Sender: kip@luna
To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org
Subject: gdb broken on 3.3RC?
In-Reply-To: <Pine.SOL.4.05.9909151219410.7805-100000@luna>
Message-ID: <Pine.SOL.4.05.9909151337480.7805-100000@luna>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-SMTP-HELO: luna
X-SMTP-MAIL-FROM: kip@lyris.com
X-SMTP-RCPT-TO: freebsd-stable@freebsd.org,freebsd-hackers@freebsd.org
X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6]
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

When I run my program under ddd, press Ctrl-C to return control to gdb and
then type info threads at the gdb prompt it returns nothing.
 
When I run it under gdb on the command line and do the same as above, gdb
dumps core.
 
How should I proceed? Should I grab the source for uthreads from current?
 
 
                                 -Kip
 




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 13:43:31 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52])
	by hub.freebsd.org (Postfix) with ESMTP id 16C6214FFE
	for <hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 13:43:29 -0700 (PDT)
	(envelope-from justin@rhapture.apple.com)
Received: from scv2.apple.com (A17-129-100-139.apple.com [17.129.100.139])
	by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id NAA09614
	for <hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 13:43:28 -0700 (PDT)
Received: from rhapture.apple.com (rhapture.apple.com [17.202.40.59])
	by scv2.apple.com (8.9.3/8.9.3) with ESMTP id NAA16281
	for <hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 13:43:28 -0700 (PDT)
Received: (from justin@localhost)
	by rhapture.apple.com (8.9.1/8.9.1) id NAA00772
	for hackers@FreeBSD.ORG; Wed, 15 Sep 1999 13:43:28 -0700 (PDT)
Message-Id: <199909152043.NAA00772@rhapture.apple.com>
To: hackers@FreeBSD.ORG
Subject: Re: ping: sendto: Message too long
In-Reply-To: <Pine.BSF.4.10.9909131744020.88005-100000@resnet.uoregon.edu>
Date: Wed, 15 Sep 1999 13:43:26 -0700
From: "Justin C. Walker" <justin@apple.com>
Reply-To: justin@apple.com
X-Mailer: by Apple MailViewer (2.105.dev)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> From: Krzysztof Krawczyk <cys@denied.cx>
> Date: 1999-09-15 13:12:21 -0700
> To: hackers@FreeBSD.ORG
> Subject: ping: sendto: Message too long
> In-reply-to:
> <Pine.BSF.4.10.9909131744020.88005-100000@resnet.uoregon.edu>
> Delivered-to: freebsd-hackers@freebsd.org
> X-Sender: cys@tepsa.lame.pl
> X-Loop: FreeBSD.ORG
>
> Hi,
>
> Could someone say me, why the maximum packetsize in ping command  
is 8184
> (ping -s 8184)? If I want to do a bigger packetsize than this i got 
> message like this:
   My guess: this is a "socket buffer size" issue.  There should be  
two ways around this:
   - change the code to have 'ping' set its socket buffer sizes based
     on the requested size
   - use 'sysctl' to change the system's default send/receive buffer 
     sizes (see net.inet.raw.maxdgram, net.inet.raw.recvspace).

Naturally, I haven't tried this, or eyeballed the code, so treat  
this with some caution.

Regards,

Justin

--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics       |
Manager, CoreOS Networking            |   Men are from Earth.
Apple Computer, Inc.                  |   Women are from Earth.
2 Infinite Loop                       |       Deal with it.
Cupertino, CA 95014                   |
*-------------------------------------*-------------------------------*


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 14: 3:12 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from ns.skylink.it (ns.skylink.it [194.177.113.1])
	by hub.freebsd.org (Postfix) with ESMTP id ACD6F1538B
	for <hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 14:03:08 -0700 (PDT)
	(envelope-from hibma@skylink.it)
Received: from heidi.plazza.it (va-184.skylink.it [194.185.55.184])
	by ns.skylink.it (8.9.1/8.8.8) with ESMTP id XAA25788;
	Wed, 15 Sep 1999 23:03:06 +0200
Received: from localhost (localhost [127.0.0.1])
	by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id HAA27803;
	Wed, 15 Sep 1999 07:26:51 GMT
X-No-Spam: Neither the receipients nor the senders email address(s) are
	to be used for Unsolicited (Commercial) Email without the
	explicit written consent of either party; as a per-message
	fee is incurred for inbound and outbound traffic to the originator.
Posted-Date: Wed, 15 Sep 1999 07:26:51 GMT
Date: Wed, 15 Sep 1999 09:26:51 +0200 (CEST)
From: Nick Hibma <hibma@skylink.it>
X-Sender: n_hibma@heidi.plazza.it
Reply-To: Nick Hibma <hibma@skylink.it>
To: Leif Neland <leifn@neland.dk>
Cc: hackers@FreeBSD.ORG
Subject: Re: USB cameras
In-Reply-To: <Pine.BSF.4.05.9909150655320.18600-100000@arnold.neland.dk>
Message-ID: <Pine.BSF.4.10.9909150922590.24014-100000@heidi.plazza.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> A simple question: Are USB cameras supported? Is anybody working on it?

No. Isochronous pipes are not supported yet, but work is underway.

> Oh, btw, how long can USB be extended?

Hm, the mechanical specification of the cable is confusing before
coffee. I think it was 6ft / 2m.

You'll notice that when connecting full speed devices they will drop
packets and get unwanted timeouts. Low speed devices are more tolerant.

Nick
-- 
e-Mail: hibma@skylink.it



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 14:16: 2 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from assaris.sics.se (assaris.sics.se [193.10.66.108])
	by hub.freebsd.org (Postfix) with ESMTP id E2888150CD
	for <hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 14:15:53 -0700 (PDT)
	(envelope-from assar@sics.se)
Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id XAA47903; Wed, 15 Sep 1999 23:15:42 +0200 (CEST)
To: Krzysztof Krawczyk <cys@denied.cx>
Cc: hackers@FreeBSD.ORG
Subject: Re: ping: sendto: Message too long
References: <Pine.BSF.4.05.9909152130470.78516-100000@tepsa.lame.pl>
Mime-Version: 1.0 (generated by tm-edit 7.68)
Content-Type: text/plain; charset=US-ASCII
From: Assar Westerlund <assar@sics.se>
Date: 15 Sep 1999 23:15:37 +0200
In-Reply-To: Krzysztof Krawczyk's message of "Wed, 15 Sep 1999 21:39:42 +0200 (CEST)"
Message-ID: <5l3dwf27wm.fsf@assaris.sics.se>
Lines: 8
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Krzysztof Krawczyk <cys@denied.cx> writes:
> Could someone say me, why the maximum packetsize in ping command is 8184
> (ping -s 8184)? If I want to do a bigger packetsize than this i got
> message like this:

Look at the sysctl variable `net.inet.raw.maxdgram'.

/assar


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 14:22:28 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16])
	by hub.freebsd.org (Postfix) with ESMTP id EF0D114CC0
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 14:22:19 -0700 (PDT)
	(envelope-from crossd@cs.rpi.edu)
Received: from cs.rpi.edu (z.cs.rpi.edu [128.213.7.2])
	by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA25660;
	Wed, 15 Sep 1999 17:22:14 -0400 (EDT)
Message-Id: <199909152122.RAA25660@cs.rpi.edu>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: "David E. Cross" <crossd@cs.rpi.edu>,
	freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu
Subject: Re: softupdates panic in 3.3-RC 
In-Reply-To: Message from Matthew Dillon <dillon@apollo.backplane.com> 
   of "Mon, 13 Sep 1999 14:11:17 PDT." <199909132111.OAA25887@apollo.backplane.com> 
Date: Wed, 15 Sep 1999 17:22:14 -0400
From: "David E. Cross" <crossd@cs.rpi.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>     Softupdates has known bugs relating to filesystem full conditions which
>     I believe Kirk is working on.  There isn't much you can do until then
>     other then either disable softupdates or work to avoid the disk-full 
>     condition.  The panic does not occur very frequently so working
>     to avoid the disk-full condition is what I would recommend.

Ok, sort-a what I figured.  Thanks.

--
David Cross                               | email: crossd@cs.rpi.edu 
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
Rensselaer Polytechnic Institute,         | Ph: 518.276.2860            
Department of Computer Science            | Fax: 518.276.4033
I speak only for myself.                  | WinNT:Linux::Linux:FreeBSD


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 14:43:17 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from pogo.caustic.org (pogo.caustic.org [216.69.69.123])
	by hub.freebsd.org (Postfix) with ESMTP id 3753314DEF
	for <freebsd-hackers@freebsd.org>; Wed, 15 Sep 1999 14:43:13 -0700 (PDT)
	(envelope-from jan@caustic.org)
Received: from localhost (jan@localhost)
	by pogo.caustic.org (8.9.3/ignatz) with ESMTP id OAA35871
	for <freebsd-hackers@freebsd.org>; Wed, 15 Sep 1999 14:43:41 -0700 (PDT)
Date: Wed, 15 Sep 1999 14:43:41 -0700 (PDT)
From: "f.johan.beisser" <jan@caustic.org>
To: freebsd-hackers@freebsd.org
Subject: Re: does gdb on 3.3RC have thread support? (fwd)
Message-ID: <Pine.BSF.4.05.9909151442550.31678-100000@pogo.caustic.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


sorry folks, i passed this on to someone who should know..

jan

---------- Forwarded message ----------
Date: Wed, 15 Sep 1999 17:07:33 -0400 (EDT)
From: Chris Doherty <cdoherty@wopr.skidmore.EDU>
To: f.johan.beisser <jan@caustic.org>
Subject: Re: does gdb on 3.3RC have thread support? (fwd)

Kip--

I'm not actually on the lists; your message was forwarded to me.

the first place to check is the documentation at www.gnu.org; that
will tell you that thread support in gdb is sketchy--"present on some
platforms" is what I think it says. I wrote an application this past
summer using pthreads and had no debugging support; I know nothing
about uthreads but wouldn't be surprised if the same thing was true.

things you *can* do:

1. printf() is, as always, your friend.
2. gdb will happily set breakpoints at arbitrary lines in arbitrary
files, or simply at the beginning of a function. since each of my
threads ran a separate function, I could set a breakpoint at that
function and there gdb would stop. inefficient and somewhat painful,
but it worked. although I didn't go into it, you may be able to set a
breakpoint in another thread while the program is running.

this was all on 3.2 and 3.1, but afaik the versions of gdb are roughly
the same.

HTH, sorry I didn't have better news...

Chris


> Date: Wed, 15 Sep 1999 12:20:49 -0700 (PDT)
> From: Kip Macy <kip@lyris.com>
> To: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
> Subject: does gdb on 3.3RC have thread support?
> 
> When I run my program under ddd, press Ctrl-C to return control to gdb and
> then type info threads at the gdb prompt it returns nothing.
> 
> When I run it under gdb on the command line and do the same as above, gdb
> dumps core.
> 
> How should I proceed? Should I grab the source for uthreads from current?
> 
> 
>                                 -Kip
> 
> 

--------------------------------------
Only this, THIS!
	Soen
--------------------------------------
Chris	cdoherty@skidmore.edu
a.k.a. Fuzzy Logic
--------------------------------------




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 14:52:24 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from luna.lyris.net (luna.shelby.com [207.90.155.6])
	by hub.freebsd.org (Postfix) with ESMTP id BE0BA14F44
	for <freebsd-hackers@freebsd.org>; Wed, 15 Sep 1999 14:52:21 -0700 (PDT)
	(envelope-from kip@lyris.com)
Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4)
	id OAA09879; Wed, 15 Sep 1999 14:52:04 -0700 (PDT)
Received: from  (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Wed, 15 Sep 1999 14:52:04 -0700
Date: Wed, 15 Sep 1999 14:52:04 -0700 (PDT)
From: Kip Macy <kip@lyris.com>
X-Sender: kip@luna
To: "f.johan.beisser" <jan@caustic.org>
Cc: freebsd-hackers@freebsd.org
Subject: Re: does gdb on 3.3RC have thread support? (fwd)
In-Reply-To: <Pine.BSF.4.05.9909151442550.31678-100000@pogo.caustic.org>
Message-ID: <Pine.SOL.4.05.9909151447470.9601-100000@luna>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-SMTP-HELO: luna
X-SMTP-MAIL-FROM: kip@lyris.com
X-SMTP-RCPT-TO: jan@caustic.org,freebsd-hackers@freebsd.org
X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6]
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thanks, I figured as much. I just thought I remember being told at one
point that gdb's thread support on FreeBSD had improved. Given a choice
between adding thread support to GDB myself and developing my application
on NT, which by the way has very good thread debugging support on MSVC6.0.
I think I would rather just spend a weekend adding support to GDB.


					-Kip
On Wed, 15 Sep 1999, f.johan.beisser wrote:

> 
> sorry folks, i passed this on to someone who should know..
> 
> jan
> 
> ---------- Forwarded message ----------
> Date: Wed, 15 Sep 1999 17:07:33 -0400 (EDT)
> From: Chris Doherty <cdoherty@wopr.skidmore.EDU>
> To: f.johan.beisser <jan@caustic.org>
> Subject: Re: does gdb on 3.3RC have thread support? (fwd)
> 
> Kip--
> 
> I'm not actually on the lists; your message was forwarded to me.
> 
> the first place to check is the documentation at www.gnu.org; that
> will tell you that thread support in gdb is sketchy--"present on some
> platforms" is what I think it says. I wrote an application this past
> summer using pthreads and had no debugging support; I know nothing
> about uthreads but wouldn't be surprised if the same thing was true.
> 
> things you *can* do:
> 
> 1. printf() is, as always, your friend.
> 2. gdb will happily set breakpoints at arbitrary lines in arbitrary
> files, or simply at the beginning of a function. since each of my
> threads ran a separate function, I could set a breakpoint at that
> function and there gdb would stop. inefficient and somewhat painful,
> but it worked. although I didn't go into it, you may be able to set a
> breakpoint in another thread while the program is running.
> 
> this was all on 3.2 and 3.1, but afaik the versions of gdb are roughly
> the same.
> 
> HTH, sorry I didn't have better news...
> 
> Chris
> 
> 
> > Date: Wed, 15 Sep 1999 12:20:49 -0700 (PDT)
> > From: Kip Macy <kip@lyris.com>
> > To: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
> > Subject: does gdb on 3.3RC have thread support?
> > 
> > When I run my program under ddd, press Ctrl-C to return control to gdb and
> > then type info threads at the gdb prompt it returns nothing.
> > 
> > When I run it under gdb on the command line and do the same as above, gdb
> > dumps core.
> > 
> > How should I proceed? Should I grab the source for uthreads from current?
> > 
> > 
> >                                 -Kip
> > 
> > 
> 
> --------------------------------------
> Only this, THIS!
> 	Soen
> --------------------------------------
> Chris	cdoherty@skidmore.edu
> a.k.a. Fuzzy Logic
> --------------------------------------
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 
> 




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 15: 1:25 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250])
	by hub.freebsd.org (Postfix) with ESMTP id AB2E614F86
	for <freebsd-hackers@freebsd.org>; Wed, 15 Sep 1999 15:01:20 -0700 (PDT)
	(envelope-from jobaldwi@vt.edu)
Received: from mailrelay.vt.edu (gkar.cc.vt.edu [128.173.16.40])
	by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id SAA20933;
	Wed, 15 Sep 1999 18:01:15 -0400 (EDT)
Received: from john.baldwin.cx (jobaldwi.campus.vt.edu)
 by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7)
 with ESMTP id <0FI4005LCFU3PL@gkar.cc.vt.edu>; Wed,
 15 Sep 1999 18:01:15 -0400 (EDT)
Date: Wed, 15 Sep 1999 18:01:19 -0400 (EDT)
From: John Baldwin <jobaldwi@vt.edu>
Subject: RE: perl stangeness on 3.3-RC
In-reply-to: <199909151959.PAA22581@cs.rpi.edu>
To: "David E. Cross" <crossd@cs.rpi.edu>
Cc: freebsd-hackers@freebsd.org
Message-id: <0FI4005LDFU3PL@gkar.cc.vt.edu>
MIME-version: 1.0
X-Mailer: XFMail 1.3 [p0] on FreeBSD
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 8bit
X-Priority: 3 (Normal)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 15-Sep-99 David E. Cross wrote:
> We have a very hetergenous environment here (even among the FreeBSD
> boxes).
> Each PC tends to be just a little bit different.  This expecially
> causes
> problems since we wish to have XDM on each machine on boot and have X
> on a NFS partition.  TO alleviate this we invented a simple Perl
> script
> to replace /usr/X11R6/bin/X to run the correct program on each
> machine:

Umm, you can edit /usr/X11R6/lib/X11/xdm/Xservers to configure xdm to
run say /usr/config/X (which would be stored on the local machiens hard
drive) instead of /usr/X11R6/bin/X.  This is a much simpler solution.
:)  (Just symlink /usr/config/X to /usr/X11R6/bin/XF86_Whatever.)
 
---

John Baldwin <jobaldwi@vt.edu> -- http://www.cslab.vt.edu/~jobaldwi/
PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 15:26: 1 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
	by hub.freebsd.org (Postfix) with ESMTP id 0B7F015291
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 15:25:59 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
	by pcnet1.pcnet.com (8.8.7/PCNet) id SAA04978;
	Wed, 15 Sep 1999 18:24:48 -0400 (EDT)
Date: Wed, 15 Sep 1999 18:24:48 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
Message-Id: <199909152224.SAA04978@pcnet1.pcnet.com>
To: jan@caustic.org, kip@lyris.com
Subject: Re: does gdb on 3.3RC have thread support? (fwd)
Cc: freebsd-hackers@FreeBSD.ORG
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Thanks, I figured as much. I just thought I remember being told at one
> point that gdb's thread support on FreeBSD had improved. Given a choice
> between adding thread support to GDB myself and developing my application
> on NT, which by the way has very good thread debugging support on MSVC6.0.
> I think I would rather just spend a weekend adding support to GDB.

Search the mailing list archives.  Doug Rabson had already done most
of the work to make FreeBSDs gdb thread-aware.  It hasn't been committed,
but diffs were submitted to one of the mailing lists (probably -hackers
or -current).

Dan Eischen
eischen@vigrid.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 15:55:46 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16])
	by hub.freebsd.org (Postfix) with ESMTP id 31AA114DE4
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 15:55:43 -0700 (PDT)
	(envelope-from crossd@cs.rpi.edu)
Received: from cs.rpi.edu (z.cs.rpi.edu [128.213.7.2])
	by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id SAA27625;
	Wed, 15 Sep 1999 18:37:35 -0400 (EDT)
Message-Id: <199909152237.SAA27625@cs.rpi.edu>
To: John Baldwin <jobaldwi@vt.edu>
Cc: "David E. Cross" <crossd@cs.rpi.edu>,
	freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu
Subject: Re: perl stangeness on 3.3-RC 
In-Reply-To: Message from John Baldwin <jobaldwi@vt.edu> 
   of "Wed, 15 Sep 1999 18:01:19 EDT." <0FI4005LDFU3PL@gkar.cc.vt.edu> 
Date: Wed, 15 Sep 1999 18:37:34 -0400
From: "David E. Cross" <crossd@cs.rpi.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Umm, you can edit /usr/X11R6/lib/X11/xdm/Xservers to configure xdm to
> run say /usr/config/X (which would be stored on the local machiens hard
> drive) instead of /usr/X11R6/bin/X.  This is a much simpler solution.
> :)  (Just symlink /usr/config/X to /usr/X11R6/bin/XF86_Whatever.)

Simpler?  It has modifications made on each machine rather in one file in 
a central location.  Plus many things expect to find /usr/X11R6/bin/X
(ala startx and xinit), and we use this on multiple architectures, and some
network/diskless booting systems where mutliple machines share the same
root partition.   This is kinda moot however, since I am more interested in
what caused it to stop working in the first place.  It really seems to be an
a bug.  At glancing through the perl module that does this (Sys/hostname.pm)
it would appear that there is no PATH environ variable set when init is run,
and that is causing the last statemnt in each function block to fail, thus
making the whole block fail.  It is interesting however that the syscall
method isn't working.  FreeBSD doesn't have a gethostname _system_ call, but
it does have the gethostname() library call (which uses sysctl(2)).  Any
ideas how to get perl to use this?

--
David Cross                               | email: crossd@cs.rpi.edu 
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
Rensselaer Polytechnic Institute,         | Ph: 518.276.2860            
Department of Computer Science            | Fax: 518.276.4033
I speak only for myself.                  | WinNT:Linux::Linux:FreeBSD


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 16:11:42 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
	by hub.freebsd.org (Postfix) with ESMTP id 5B35B14FC6
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 16:11:41 -0700 (PDT)
	(envelope-from bright@wintelcom.net)
Received: from localhost (bright@localhost)
	by fw.wintelcom.net (8.8.8/8.8.8) with ESMTP id JAA06105;
	Wed, 15 Sep 1999 09:31:10 -0700 (PDT)
	(envelope-from bright@wintelcom.net)
Date: Wed, 15 Sep 1999 16:31:09 +0000 (GMT)
From: Alfred Perlstein <bright@wintelcom.net>
To: Christopher Sedore <cmsedore@mailbox.syr.edu>
Cc: Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: High Performance I/O (more)
In-Reply-To: <Pine.SOL.4.10.9909151235280.1425-100000@rodan.syr.edu>
Message-ID: <Pine.BSF.4.05.9909151621520.6392-100000@fw.wintelcom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Wed, 15 Sep 1999, Christopher Sedore wrote:

> My ideas for this are a little different than what I've seen proposed thus
> far, more along the lines of creating something that acts as both an event
> queue and a IOCP.  Ideally this would be a descriptor that could be shared
> across processes (or threads), and could be accessed using read().  I
> don't much care for the suggestion that threads ought to have an event
> queue of their own--rather if you want a per-thread completion
> notification, simply create a descriptor for each thread that needs this
> function.  What ever is created, it should be sufficiently extensible to
> allow for all the events we can imagine now, as well as being flexible for
> future enhancement.  (FWIW, I've also been thinking that I might like to
> be able to submit aio requests by write()ing said descriptor.  Just a
> thought.)

I thought it'd be very useful to be able to give the kernel a pointer
to a pollfd struct in your (userland) address space, when events occur
SIGIO (or maybe some other signal?) is posted to the process after
updating the process's pollfd.

This makes queing not nessesary because if a signal is 'lost' somehow
the pollfd is still updated, it also reduces the amount of syscalls
needed by at least one.

From what I understand your methodology of async IO involves this
type of cycle:

syscall_register_descriptor -> SIGIO -> \
 syscall_read_from_event_queue -> syscall_read/write/lock/etc

Being able to register the pollfd allows for a minimal amount
of memory overhead and one less syscall, infact it doesn't even
require much of a new subsystem:

syscall_register_pollfd -> SIGIO -> kernel to userland write \
  userland_pollscan -> syscal_read/write/lock/etc

You would have to have a refresh the kernel pollfd array if
what you were interested in changed.

How does this sound to you?

-Alfred



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 19: 6:48 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id A36C314A26
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 19:06:44 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id UAA75279
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 20:06:43 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id UAA17542 for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 20:06:06 -0600 (MDT)
Message-Id: <199909160206.UAA17542@harmony.village.org>
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: Bug in dd seeking beyond 2G 
In-reply-to: Your message of "Wed, 15 Sep 1999 21:28:18 +0200."
		<199909151928.VAA26499@dorifer.heim3.tu-clausthal.de> 
References: <199909151928.VAA26499@dorifer.heim3.tu-clausthal.de>  
Date: Wed, 15 Sep 1999 20:06:06 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <199909151928.VAA26499@dorifer.heim3.tu-clausthal.de> Oliver Fromme writes:
: It only works on two's-complement machines, though, but I'm not
: aware of any FreeBSD port to an architecture that doesn't use
: two's-complement numbers...

I'm not aware of any one's-complement machine that was manufacture
after about 1980...  Not even NetBSD has any one's-complement machines
that it supports :-)

Warner


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 21:10:24 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
	by hub.freebsd.org (Postfix) with ESMTP
	id 72F751541A; Wed, 15 Sep 1999 21:05:39 -0700 (PDT)
	(envelope-from green@FreeBSD.org)
Received: from localhost (green@localhost)
	by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id AAA01306;
	Thu, 16 Sep 1999 00:05:37 -0400 (EDT)
X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs
Date: Thu, 16 Sep 1999 00:05:37 -0400 (EDT)
From: "Brian F. Feldman" <green@FreeBSD.org>
X-Sender: green@janus.syracuse.net
To: Dan Nelson <dnelson@emsphone.com>
Cc: Bakul Shah <bakul@torrentnet.com>, bde@FreeBSD.org,
	freebsd-hackers@FreeBSD.org
Subject: Re: Bug in dd seeking beyond 2G
In-Reply-To: <19990915135647.A84130@dan.emsphone.com>
Message-ID: <Pine.BSF.4.10.9909160000380.99133-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 15 Sep 1999, Dan Nelson wrote:

> RCS file: /home/ncvs/src/bin/dd/dd.c,v                                          
> 
> revision 1.17
> date: 1999/06/19 19:49:32;  author: green;  state: Exp;  lines: +25 -21
> Miscellaneous dd(1) changes: mainly fixing variable types (size_t,
> ssize_t, off_t, int, u_int64_t, etc.). dd(1) should now work properly
> with REALLY big amounts of data.
> 
> Should be a -stable candidate by now (3 months of testing?)

I think so. It would be nice to have all dd(1) excepting the "file typing"
changes backported to 3.3-STABLE (or is it -RELEASE?) All I'd like is
Bruce's okay on it, as well as Jordan's.

Hmm, I noticed that I don't use two spaces after the end of sentences as
many others do and I always _thought_ I did. I guess it's mainly LyX/TeX's
fault :)

-- 
 Brian Fundakowski Feldman           /  "Any sufficiently advanced bug is    \
 green@FreeBSD.org                   |   indistinguishable from a feature."  |
     FreeBSD: The Power to Serve!    \        -- Rich Kulawiec               /



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 21:17:59 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3C19A14A08; Wed, 15 Sep 1999 21:17:56 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
Received: from localhost (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA91231;
	Wed, 15 Sep 1999 21:17:36 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
To: "Brian F. Feldman" <green@FreeBSD.ORG>
Cc: Dan Nelson <dnelson@emsphone.com>,
	Bakul Shah <bakul@torrentnet.com>, bde@FreeBSD.ORG,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: Bug in dd seeking beyond 2G 
In-reply-to: Your message of "Thu, 16 Sep 1999 00:05:37 EDT."
             <Pine.BSF.4.10.9909160000380.99133-100000@janus.syracuse.net> 
Date: Wed, 15 Sep 1999 21:17:36 -0700
Message-ID: <91228.937455456@localhost>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It can go in after the freeze - it's a bit late to be asking now. :)

> On Wed, 15 Sep 1999, Dan Nelson wrote:
> 
> > RCS file: /home/ncvs/src/bin/dd/dd.c,v                                     
     
> > 
> > revision 1.17
> > date: 1999/06/19 19:49:32;  author: green;  state: Exp;  lines: +25 -21
> > Miscellaneous dd(1) changes: mainly fixing variable types (size_t,
> > ssize_t, off_t, int, u_int64_t, etc.). dd(1) should now work properly
> > with REALLY big amounts of data.
> > 
> > Should be a -stable candidate by now (3 months of testing?)
> 
> I think so. It would be nice to have all dd(1) excepting the "file typing"
> changes backported to 3.3-STABLE (or is it -RELEASE?) All I'd like is
> Bruce's okay on it, as well as Jordan's.
> 
> Hmm, I noticed that I don't use two spaces after the end of sentences as
> many others do and I always _thought_ I did. I guess it's mainly LyX/TeX's
> fault :)
> 
> -- 
>  Brian Fundakowski Feldman           /  "Any sufficiently advanced bug is    
\
>  green@FreeBSD.org                   |   indistinguishable from a feature."  
|
>      FreeBSD: The Power to Serve!    \        -- Rich Kulawiec               
/
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 21:29:51 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
	by hub.freebsd.org (Postfix) with ESMTP
	id 368B814A1D; Wed, 15 Sep 1999 21:29:44 -0700 (PDT)
	(envelope-from green@FreeBSD.org)
Received: from localhost (green@localhost)
	by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id AAA01929;
	Thu, 16 Sep 1999 00:29:43 -0400 (EDT)
X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs
Date: Thu, 16 Sep 1999 00:29:43 -0400 (EDT)
From: "Brian F. Feldman" <green@FreeBSD.org>
X-Sender: green@janus.syracuse.net
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: Dan Nelson <dnelson@emsphone.com>,
	Bakul Shah <bakul@torrentnet.com>, bde@FreeBSD.org,
	freebsd-hackers@FreeBSD.org
Subject: Re: Bug in dd seeking beyond 2G 
In-Reply-To: <91228.937455456@localhost>
Message-ID: <Pine.BSF.4.10.9909160021080.99133-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 15 Sep 1999, Jordan K. Hubbard wrote:

> It can go in after the freeze - it's a bit late to be asking now. :)

I was guessing as much :) I didn't specifically see anyone requesting
for these things in -STABLE, so I didn't really pay much attention to
merging these things.  It makes me wonder why this tool has been neglected
as much as it has when there's no real replacement.

-- 
 Brian Fundakowski Feldman           /  "Any sufficiently advanced bug is    \
 green@FreeBSD.org                   |   indistinguishable from a feature."  |
     FreeBSD: The Power to Serve!    \        -- Rich Kulawiec               /



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 22:50:20 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32])
	by hub.freebsd.org (Postfix) with SMTP id D84801589C
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 22:48:13 -0700 (PDT)
	(envelope-from dscheidt@enteract.com)
Received: (qmail 36904 invoked from network); 16 Sep 1999 05:48:12 -0000
Received: from shell-1.enteract.com (dscheidt@207.229.143.40)
  by pop3-3.enteract.com with SMTP; 16 Sep 1999 05:48:12 -0000
Date: Thu, 16 Sep 1999 00:48:12 -0500 (CDT)
From: David Scheidt <dscheidt@enteract.com>
To: Warner Losh <imp@village.org>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Bug in dd seeking beyond 2G 
In-Reply-To: <199909160206.UAA17542@harmony.village.org>
Message-ID: <Pine.NEB.3.96.990916002348.89656B-100000@shell-1.enteract.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 15 Sep 1999, Warner Losh wrote:

> In message <199909151928.VAA26499@dorifer.heim3.tu-clausthal.de> Oliver Fromme writes:
> : It only works on two's-complement machines, though, but I'm not
> : aware of any FreeBSD port to an architecture that doesn't use
> : two's-complement numbers...
> 
> I'm not aware of any one's-complement machine that was manufacture
> after about 1980...  Not even NetBSD has any one's-complement machines
> that it supports :-)

Aren't the the Bull GCOS 7 machines ones complement?  Or the Unisys
1100/2200 36 bit machines?  I do know that some CDC 6600 clones were put
together in the '80s, and they would have been ones complement.  Software is
expensive, building machines out of FPGAs isn't...

Negative zero isn't dead yet!




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Wed Sep 15 23:26:22 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140])
	by hub.freebsd.org (Postfix) with ESMTP id 54C6B14BE4
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 15 Sep 1999 23:26:19 -0700 (PDT)
	(envelope-from chris@cheddar.netmonger.net)
Received: (from chris@localhost)
	by cheddar.netmonger.net (8.8.8/8.8.8) id CAA08073;
	Thu, 16 Sep 1999 02:26:16 -0400 (EDT)
Message-ID: <19990916022616.A6037@netmonger.net>
Date: Thu, 16 Sep 1999 02:26:16 -0400
From: Christopher Masto <chris@netmonger.net>
To: "David E. Cross" <crossd@cs.rpi.edu>,
	John Baldwin <jobaldwi@vt.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: perl stangeness on 3.3-RC
Mail-Followup-To: "David E. Cross" <crossd@cs.rpi.edu>,
	John Baldwin <jobaldwi@vt.edu>, freebsd-hackers@FreeBSD.ORG
References: <jobaldwi@vt.edu> <199909152237.SAA27625@cs.rpi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <199909152237.SAA27625@cs.rpi.edu>; from David E. Cross on Wed, Sep 15, 1999 at 06:37:34PM -0400
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Sep 15, 1999 at 06:37:34PM -0400, David E. Cross wrote:
> method isn't working.  FreeBSD doesn't have a gethostname _system_ call, but
> it does have the gethostname() library call (which uses sysctl(2)).  Any
> ideas how to get perl to use this?

Write a small xs module?
-- 
Christopher Masto         Senior Network Monkey      NetMonger Communications
chris@netmonger.net        info@netmonger.net        http://www.netmonger.net

Free yourself, free your machine, free the daemon -- http://www.freebsd.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16  0:34:49 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id 040F714BDA
	for <hackers@freebsd.org>; Thu, 16 Sep 1999 00:34:43 -0700 (PDT)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1)
	id 11RW3Y-000EJd-00; Thu, 16 Sep 1999 09:34:12 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Mike Smith <mike@smith.net.au>
Cc: John Baldwin <jobaldwi@vt.edu>, hackers@FreeBSD.ORG
Subject: Re: Problem with FreeBSD 
In-reply-to: Your message of "Wed, 15 Sep 1999 10:06:59 MST."
             <199909151706.KAA00864@dingo.cdrom.com> 
Date: Thu, 16 Sep 1999 09:34:12 +0200
Message-ID: <55032.937467252@axl.noc.iafrica.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Wed, 15 Sep 1999 10:06:59 MST, Mike Smith wrote:

> > Actually, as with many such cases, the floppy disk driver turned out to
> > be flakey. We resolved this via private mail.
> 
> Driver, or drive?  The BIOS is the driver at this point in time.

Argh! Thanks. I meant the floppy drive.

Ciao,
Sheldon.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16  1:42:27 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id C25571544F
	for <freebsd-hackers@freebsd.org>; Thu, 16 Sep 1999 01:42:23 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA83383;
	Thu, 16 Sep 1999 09:43:08 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Thu, 16 Sep 1999 09:43:08 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Daniel Eischen <eischen@vigrid.com>
Cc: jan@caustic.org, kip@lyris.com, freebsd-hackers@freebsd.org
Subject: Re: does gdb on 3.3RC have thread support? (fwd)
In-Reply-To: <199909152224.SAA04978@pcnet1.pcnet.com>
Message-ID: <Pine.BSF.4.10.9909160941160.440-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 15 Sep 1999, Daniel Eischen wrote:

> > Thanks, I figured as much. I just thought I remember being told at one
> > point that gdb's thread support on FreeBSD had improved. Given a choice
> > between adding thread support to GDB myself and developing my application
> > on NT, which by the way has very good thread debugging support on MSVC6.0.
> > I think I would rather just spend a weekend adding support to GDB.
> 
> Search the mailing list archives.  Doug Rabson had already done most
> of the work to make FreeBSDs gdb thread-aware.  It hasn't been committed,
> but diffs were submitted to one of the mailing lists (probably -hackers
> or -current).

Unfortunately, I had to drop this for a while to fight fires in other
places. There is a small amount of work to do to make the gdb interface
more robust in the face of changes to the uthread structures but even
without that, my current set of patches seem to work fairly well.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16  2:43:59 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8751914F2E; Thu, 16 Sep 1999 02:43:56 -0700 (PDT)
	(envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp)
Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:t5xIauT29h9+Kj+XHYEy1jU5vj1P/aCH@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1])
	by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id SAA14729;
	Thu, 16 Sep 1999 18:43:54 +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 SAA02636; Thu, 16 Sep 1999 18:48:14 +0900 (JST)
Message-Id: <199909160948.SAA02636@zodiac.mech.utsunomiya-u.ac.jp>
To: hackers@freebsd.org
Cc: sos@freebsd.org, bde@freebsd.org,
	yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: panic() the system from the console (was: Re: kern/13721: There is
	 no way to force system panic from console)
Date: Thu, 16 Sep 1999 18:48:13 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>>Number:         13721
>>Category:       kern
>>Synopsis:       There is no way to force system panic from console
[...]
>>Release:        FreeBSD 3.3-RC
>>Organization:
>Server
>>Environment:
>>Description:
>Under some rare circumstances there is a real need to reboot system via kernel
>'s panic from the system console. For example: if any process has ran out of m
>emory nobody can login and even Ctrl-Alt-Del does not work and there is no way
> to find out source of the problem after cold boot.
>And if reboot is not disabled the panic will not decrease the system's securit
>y especially; where enabling kernel debugger is not acceptable.

I tend to agree with the PR originator that this feature won't
particularly jeopardize security in the kernel for which reboot key
sequence is not disabled.

As the originator suggested in his subsequent posting to the PR
database, we can defined "panic" key and handle it in syscons
as follows:

	case _PANIC_KEY_
#if !defined(SC_DISABLE_REBOOT) && !defined(SC_DISABLE_PANIC)
		panic();
#endif
		break;

We can restrict this feature, by checking `securelevel' too.

	case _PANIC_KEY_
#if !defined(SC_DISABLE_REBOOT) && !defined(SC_DISABLE_PANIC)
		if (securelevel <= 0)
			panic();
#endif
		break;

Any opinions?

Kazu

>On Sun it is the only way to reboot the working system: OpenBoot prom on boot 
>and reset commands at first checks whether Solaris is running and if it is run
>ning - calls its panic routine.
>>How-To-Repeat:



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16  4:33:46 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29])
	by hub.freebsd.org (Postfix) with ESMTP id 11F8E14DDD
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 04:33:43 -0700 (PDT)
	(envelope-from cmsedore@mailbox.syr.edu)
Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.D0AB1750@mailer.syr.edu>; Thu, 16 Sep 1999 7:33:48 -0400
Received: from localhost (cmsedore@localhost)
	by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id HAA01738;
	Thu, 16 Sep 1999 07:33:41 -0400 (EDT)
X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs
Date: Thu, 16 Sep 1999 07:33:41 -0400 (EDT)
From: Christopher Sedore <cmsedore@mailbox.syr.edu>
X-Sender: cmsedore@rodan.syr.edu
To: Alfred Perlstein <bright@wintelcom.net>
Cc: Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: High Performance I/O (more)
In-Reply-To: <Pine.BSF.4.05.9909151621520.6392-100000@fw.wintelcom.net>
Message-ID: <Pine.SOL.4.10.9909160720220.1042-100000@rodan.syr.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Wed, 15 Sep 1999, Alfred Perlstein wrote:

> 
> On Wed, 15 Sep 1999, Christopher Sedore wrote:
> 
> > My ideas for this are a little different than what I've seen proposed thus
> > far, more along the lines of creating something that acts as both an event
> > queue and a IOCP.  Ideally this would be a descriptor that could be shared
> > across processes (or threads), and could be accessed using read().  I
> > don't much care for the suggestion that threads ought to have an event
> > queue of their own--rather if you want a per-thread completion
> > notification, simply create a descriptor for each thread that needs this
> > function.  What ever is created, it should be sufficiently extensible to
> > allow for all the events we can imagine now, as well as being flexible for
> > future enhancement.  (FWIW, I've also been thinking that I might like to
> > be able to submit aio requests by write()ing said descriptor.  Just a
> > thought.)
> 
> I thought it'd be very useful to be able to give the kernel a pointer
> to a pollfd struct in your (userland) address space, when events occur
> SIGIO (or maybe some other signal?) is posted to the process after
> updating the process's pollfd.
> 
> This makes queing not nessesary because if a signal is 'lost' somehow
> the pollfd is still updated, it also reduces the amount of syscalls
> needed by at least one.

Unfortunately, I think queueing would still be necessary since you would
not be able to update the userland pollfd until that proc became curproc
again.  Unless you mapped the pollfd space into the kernel and wired it.

This still has the problem of scanning all the pollfd structs.  For up to
a the low hundreds, this probably is OK, somewhere after that it becomes
expensive.  The nice thing about the event queue is that it scales
(virtually) linearly to any number of descriptors.

> >From what I understand your methodology of async IO involves this
> type of cycle:
> 
> syscall_register_descriptor -> SIGIO -> \
>  syscall_read_from_event_queue -> syscall_read/write/lock/etc
> 
> Being able to register the pollfd allows for a minimal amount
> of memory overhead and one less syscall, infact it doesn't even
> require much of a new subsystem:
> 
> syscall_register_pollfd -> SIGIO -> kernel to userland write \
>   userland_pollscan -> syscal_read/write/lock/etc
> 
> You would have to have a refresh the kernel pollfd array if
> what you were interested in changed.
> 
> How does this sound to you?

I would propose a system more like this:

syscall_register_fdinterest->[eventloop:
syscall_wait_for_events/syscall_read()/syscall_write()/syscall_accept()/etc]

I don't see any particular advantage to using SIGIO or signals in general.

The nice thing is that the same loop works for async io (aio_*) if done
right--somethine like having wait_for_events returning a union with a key
value so you know what kind of event you've picked up and how to proceed.
In other words, you could freely intermix aio with event driven io in the
same loop.  This would be handy in some of the code I've been messing
with--right now I depend on an implementation detail to allow me to do an
aio_read() on a listening socket.  When said read completes (always with
failure, of course), I know that the socket is 'ready' for an accept().
Events would let me do the same without the ugliness.

Events could also (I haven't thought this out, so please forgive me if
there's an obvious bugaboo here) return additional information about the
descriptor/whatever.  One nice possibility would be outgoing buffer space
on sockets.  This may or may not be worth the coding effort.  

If implemented in a multiprocessor aware manner, events could also allow
for more parallelism that we have now.  

-Chris



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16  7:25: 5 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13])
	by hub.freebsd.org (Postfix) with ESMTP
	id EE1EA14DED; Thu, 16 Sep 1999 07:21:12 -0700 (PDT)
	(envelope-from wosch@cs.tu-berlin.de)
Received: from freno.cs.tu-berlin.de (wosch@freno.cs.tu-berlin.de [130.149.17.167])
	by mail.cs.tu-berlin.de (8.9.1/8.9.1) with ESMTP id QAA04602;
	Thu, 16 Sep 1999 16:19:04 +0200 (MET DST)
Received: (from wosch@localhost)
	by freno.cs.tu-berlin.de (8.9.1/8.9.0) id QAA05223;
	Thu, 16 Sep 1999 16:19:03 +0200 (MET DST)
Date: Thu, 16 Sep 1999 16:19:03 +0200
From: Wolfram Schneider <wosch@cs.tu-berlin.de>
To: hackers@freebsd.org
Subject: pmake binaries for Solaris
Message-ID: <19990916161903.A5138@freno.cs.tu-berlin.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I ported pmake to SunOS 5.5.1, 5.6, and 5.7. The port based on the
FreeBSD-4.0-current make version from 9th September 1999.

I successfully compiled pmake itself and the FreeBSD Web server.

The binaries are available at
http://www.de.freebsd.org/~wosch/src/pmake/

-- 
Wolfram Schneider <wosch@freebsd.org> http://wolfram.schneider.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16  7:43:53 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from bantu.cl.msu.edu (bantu.cl.msu.edu [35.8.3.18])
	by hub.freebsd.org (Postfix) with ESMTP id B0F5D15744
	for <hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 07:43:51 -0700 (PDT)
	(envelope-from dervish@bantu.cl.msu.edu)
Received: (from dervish@localhost)
	by bantu.cl.msu.edu (8.9.3/8.9.3) id KAA21744;
	Thu, 16 Sep 1999 10:42:50 -0400 (EDT)
	(envelope-from dervish)
Date: Thu, 16 Sep 1999 10:42:50 -0400
From: bush doctor <dervish@bantu.cl.msu.edu>
To: Wolfram Schneider <wosch@cs.tu-berlin.de>
Cc: hackers@FreeBSD.ORG
Subject: Re: pmake binaries for Solaris
Message-ID: <19990916104250.A21719@bantu.cl.msu.edu>
References: <19990916161903.A5138@freno.cs.tu-berlin.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <19990916161903.A5138@freno.cs.tu-berlin.de>; from Wolfram Schneider on Thu, Sep 16, 1999 at 04:19:03PM +0200
X-Operating-System: FreeBSD 4.0-CURRENT i386
X-PGP-Fingerprint: 35 95 F8 63 DA 5B 32 51  8F A9 AC 3C B4 74 F3 BA
WWW-Home-Page: http://www.msu.edu/~ikhala
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Out of da blue Wolfram Schneider aka (wosch@cs.tu-berlin.de) said:
> I ported pmake to SunOS 5.5.1, 5.6, and 5.7. The port based on the
> FreeBSD-4.0-current make version from 9th September 1999.
> 
> I successfully compiled pmake itself and the FreeBSD Web server.
> 
> The binaries are available at
> http://www.de.freebsd.org/~wosch/src/pmake/
This should be nice.  The number of solaris boxen I administering
seems to be growing faster that the FBSD boxen.  Nice work & thanxs ...

> 
> -- 
> Wolfram Schneider <wosch@freebsd.org> http://wolfram.schneider.org
> 
> 

#:^)
-- 
So ya want ta here da roots?
Dem that feels it knows it ...
bush doctor <dervish@bantu.cl.msu.edu>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16  7:47: 7 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29])
	by hub.freebsd.org (Postfix) with ESMTP id 2B7EA1542B
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 07:47:03 -0700 (PDT)
	(envelope-from cmsedore@mailbox.syr.edu)
Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.CFBF8A90@mailer.syr.edu>; Thu, 16 Sep 1999 10:47:03 -0400
Received: from localhost (cmsedore@localhost)
	by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id KAA11397;
	Thu, 16 Sep 1999 10:47:02 -0400 (EDT)
X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs
Date: Thu, 16 Sep 1999 10:47:02 -0400 (EDT)
From: Christopher Sedore <cmsedore@mailbox.syr.edu>
X-Sender: cmsedore@rodan.syr.edu
To: Mike Smith <mike@smith.net.au>
Cc: Ruslan Ermilov <ru@ucb.crimea.ua>,
	Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: kern/13075 (was: Re: aio_*) 
In-Reply-To: <199909151733.KAA01010@dingo.cdrom.com>
Message-ID: <Pine.SOL.4.10.9909161046060.1425-100000@rodan.syr.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I filed a followup with a patch (against 4.x, but it will probably work
just as well against 3.x, but I don't have a handy way to try it).

-Chris

On Wed, 15 Sep 1999, Mike Smith wrote:

> > 
> > 
> > On Wed, 15 Sep 1999, Ruslan Ermilov wrote:
> > 
> > > > The aio_* stuff (I use a custom patched version in 4.x) offers performance
> > > > advantages over select() with large numbers of descriptors.  In terms of
> > > > efficiency, I don't have any trouble saturating full-duplex 100mbit link
> > > > with aio routines on a reasonably fast box (PII-400 512MB).
> > > > 
> > > > As more work gets done to the aio stuff, there are some potential early
> > > > advantages available to multiprocessor machines (since the program
> > > > 'driving' the aio could run concurrently with the kernel code moving
> > > > network or disk data).
> > > > 
> > > > -Chris
> > > 
> > > Do you by any change have an idea how to fix PR kern/13075
> > > (signal is not posted for async I/O on raw devices)
> > 
> > Yes.  There is no code to post the signal unless the job is of the lio
> > variety.  Writing a fix took about 15 minutes (including reboot).
> > Extensive testing not included, though the test program provided with the
> > PR now functions.
> 
> You plan to file a followup to the PR, I hope.  8)
> 
> -- 
> \\  The mind's the standard       \\  Mike Smith
> \\  of the man.                   \\  msmith@freebsd.org
> \\    -- Joseph Merrick           \\  msmith@cdrom.com
> 
> 
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16  7:53:43 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP
	id E493A156FC; Thu, 16 Sep 1999 07:53:40 -0700 (PDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id IAA77463;
	Thu, 16 Sep 1999 08:53:38 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id IAA21647; Thu, 16 Sep 1999 08:53:08 -0600 (MDT)
Message-Id: <199909161453.IAA21647@harmony.village.org>
To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Subject: Re: panic() the system from the console (was: Re: kern/13721: There is no way to force system panic from console) 
Cc: hackers@FreeBSD.ORG, sos@FreeBSD.ORG, bde@FreeBSD.ORG
In-reply-to: Your message of "Thu, 16 Sep 1999 18:48:13 +0900."
		<199909160948.SAA02636@zodiac.mech.utsunomiya-u.ac.jp> 
References: <199909160948.SAA02636@zodiac.mech.utsunomiya-u.ac.jp>  
Date: Thu, 16 Sep 1999 08:53:08 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <199909160948.SAA02636@zodiac.mech.utsunomiya-u.ac.jp> Kazutaka YOKOTA writes:
: 	case _PANIC_KEY_
: #if !defined(SC_DISABLE_REBOOT) && !defined(SC_DISABLE_PANIC)
: 		if (securelevel <= 0)
: 			panic();
: #endif
: 		break;
: 
: Any opinions?

I can see this being useful only for systems that have a problem
coming up.  Otherwise, adding options SC_DISABLE_{PANIC,REBOOT} would
accomplish this as well.  So I'm mildly opposed to this since it hangs
yet another thing on securelevel...

Warner


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16  8:28:53 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from thelab.hub.org (nat203.199.mpoweredpc.net [142.177.203.199])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9860E153FA; Thu, 16 Sep 1999 08:28:47 -0700 (PDT)
	(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by thelab.hub.org (8.9.3/8.9.1) with ESMTP id MAA36365;
	Thu, 16 Sep 1999 12:28:29 -0300 (ADT)
	(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Thu, 16 Sep 1999 12:28:29 -0300 (ADT)
From: The Hermit Hacker <scrappy@hub.org>
To: bush doctor <dervish@bantu.cl.msu.edu>
Cc: Wolfram Schneider <wosch@cs.tu-berlin.de>, hackers@FreeBSD.ORG,
	smp@freebsd.org
Subject: Re: pmake binaries for Solaris
In-Reply-To: <19990916104250.A21719@bantu.cl.msu.edu>
Message-ID: <Pine.BSF.4.10.9909161223380.27097-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 16 Sep 1999, bush doctor wrote:

> Out of da blue Wolfram Schneider aka (wosch@cs.tu-berlin.de) said:
> > I ported pmake to SunOS 5.5.1, 5.6, and 5.7. The port based on the
> > FreeBSD-4.0-current make version from 9th September 1999.
> > 
> > I successfully compiled pmake itself and the FreeBSD Web server.
> > 
> > The binaries are available at
> > http://www.de.freebsd.org/~wosch/src/pmake/
> This should be nice.  The number of solaris boxen I administering
> seems to be growing faster that the FBSD boxen.  Nice work & thanxs ...

I'm still fighting to get a FBSD boxen into the office...have my immediate
boss convinced that we should, but her boss is still convinced that
Solaris is the only Unix OS out there *sigh*

Does anyone have any *good* comparisons between the two?  Something like
the work that Brad Knowles (?) did recently with Vinum vs DPT SmartCache
controllers?

If nobody...I'm just working on a Dual PIII upgrade to one of our servers
here...if someone could suggest a 'test suite' that I could run on FreeBSD
(SMP) before I switched things over to Solaris, I'd be more then willing
to run it through so that it was a 'same hardware' scenario.  The system
(hardware-wise) I'm building is such that it is 'FreeBSD-friendly', as
are all the x86 systems I'm building...


Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16  9:25:12 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from jules.res.cmu.edu (JULES.RES.CMU.EDU [128.2.144.56])
	by hub.freebsd.org (Postfix) with ESMTP
	id 698BB151B9; Thu, 16 Sep 1999 09:25:08 -0700 (PDT)
	(envelope-from greg@jules.res.cmu.edu)
Received: from jules.res.cmu.edu (localhost [127.0.0.1])
	by jules.res.cmu.edu (8.9.3/8.9.2) with ESMTP id MAA14962;
	Thu, 16 Sep 1999 12:25:52 GMT
	(envelope-from greg@jules.res.cmu.edu)
Message-Id: <199909161225.MAA14962@jules.res.cmu.edu>
X-Mailer: exmh version 2.0.2 2/24/98
To: freebsd-smp@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: cache-friendly scheduling for SMP
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 16 Sep 1999 12:25:52 +0000
From: greg <greg@jules.res.cmu.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm trying to run 1-2 processes with very large memory footprints on my P2 SMP 
machine.  I'm finding that the process switches cpu's quite often, which 
obviously isn't good for the caches on the CPU.

Can anybody point me to a paper, mailing list discussion, etc. that discusses 
scheduling processes to not thrash the cpu caches?  Or if there's anything in 
place, how I can take advantage of it, etc.  I got stumped on the idea a while 
ago, so I'm really curious...

thanks,
Greg





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16  9:28:15 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dfw-proxy3.ext.raytheon.com (dfw-gate3.raytheon.com [138.126.255.195])
	by hub.freebsd.org (Postfix) with ESMTP id C269C153CA
	for <Freebsd-hackers@FreeBSD.org>; Thu, 16 Sep 1999 09:28:11 -0700 (PDT)
	(envelope-from Gregory_D_Moncreaff@res.raytheon.com)
Received: from ressud-as01.res.ray.com (ressud-as01.res.ray.com [138.125.97.69])
	by dfw-proxy3.ext.raytheon.com (8.9.3/8.9.3) with SMTP id LAA00036
	for <Freebsd-hackers@FreeBSD.org>; Thu, 16 Sep 1999 11:28:09 -0500 (CDT)
From: Gregory_D_Moncreaff@res.raytheon.com
Received: by ressud-as01.res.ray.com(Lotus SMTP MTA Internal build v4.6.2  (651.2 6-10-1998))  id 852567EE.005A7377 ; Thu, 16 Sep 1999 12:27:57 -0400
X-Lotus-FromDomain: RES
To: Freebsd-hackers@FreeBSD.org
Message-ID: <852567EE.005A71C3.00@ressud-as01.res.ray.com>
Date: Thu, 16 Sep 1999 12:27:37 -0400
Subject: boston globe article....
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

http://www.boston.com/dailyglobe2/259/business/Even_better_than_Linux+.shtm
l




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16  9:51: 8 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201])
	by hub.freebsd.org (Postfix) with SMTP id AE05A155AC
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 09:51:06 -0700 (PDT)
	(envelope-from nordwick@scam.xcf.berkeley.edu)
Received: (qmail 349 invoked by uid 27268); 16 Sep 1999 16:50:49 -0000
Message-ID: <19990916165049.348.qmail@scam.xcf.berkeley.edu>
To: Christopher Sedore <cmsedore@mailbox.syr.edu>
Cc: Alfred Perlstein <bright@wintelcom.net>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: High Performance I/O (more)
In-Reply-To: Your message of "Thu, 16 Sep 1999 07:33:41 EDT." <Pine.SOL.4.10.9909160720220.1042-100000@rodan.syr.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <346.937500648.1@scam.XCF.Berkeley.EDU>
Date: Thu, 16 Sep 1999 09:50:49 -0700
From: "Jayson Nordwick" <nordwick@scam.xcf.berkeley.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>Events could also (I haven't thought this out, so please forgive me if
>there's an obvious bugaboo here) return additional information about the
>descriptor/whatever.  One nice possibility would be outgoing buffer space
>on sockets.  This may or may not be worth the coding effort.  
>

First, If you are using POSIX real time signals, you can get extra
information by using sigwaitinfo().

In a somewhat nonportable fashion, the Linux people (Stephen Tweedie, in
particular) added two things: (1) An fcntl() value called F_SETSIG that
delivers a real time signal whenever data to the file descriptor is ready
for read or write, (2) when the signal is delivered the si_band of the
signal is filled in with the poll() values.

>If implemented in a multiprocessor aware manner, events could also allow
>for more parallelism that we have now.  
>

Two of the strong benefits of asynchronous I/O over the nonblocking/select()
is that (1) there is no context switch to send the data, since the kernle
takes care (as opposed to the select() philosophy of the program taking
care of it) and (2) if you are running on an MP machine, the kernel can be
using one processor to take care of asynchronous data while the application
uses the other.

>-Chris
>

-jason



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 10:23:33 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from bantu.cl.msu.edu (bantu.cl.msu.edu [35.8.3.18])
	by hub.freebsd.org (Postfix) with ESMTP id 9058514E66
	for <hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 10:23:31 -0700 (PDT)
	(envelope-from dervish@bantu.cl.msu.edu)
Received: (from dervish@localhost)
	by bantu.cl.msu.edu (8.9.3/8.9.3) id NAA22010;
	Thu, 16 Sep 1999 13:23:22 -0400 (EDT)
	(envelope-from dervish)
Date: Thu, 16 Sep 1999 13:23:22 -0400
From: bush doctor <dervish@bantu.cl.msu.edu>
To: The Hermit Hacker <scrappy@hub.org>
Cc: hackers@FreeBSD.ORG
Subject: Re: pmake binaries for Solaris
Message-ID: <19990916132322.B21952@bantu.cl.msu.edu>
References: <19990916104250.A21719@bantu.cl.msu.edu> <Pine.BSF.4.10.9909161223380.27097-100000@thelab.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <Pine.BSF.4.10.9909161223380.27097-100000@thelab.hub.org>; from The Hermit Hacker on Thu, Sep 16, 1999 at 12:28:29PM -0300
X-Operating-System: FreeBSD 4.0-CURRENT i386
X-PGP-Fingerprint: 35 95 F8 63 DA 5B 32 51  8F A9 AC 3C B4 74 F3 BA
WWW-Home-Page: http://www.msu.edu/~ikhala
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Out of da blue The Hermit Hacker aka (scrappy@hub.org) said:
> On Thu, 16 Sep 1999, bush doctor wrote:
> 
> > Out of da blue Wolfram Schneider aka (wosch@cs.tu-berlin.de) said:
> > > I ported pmake to SunOS 5.5.1, 5.6, and 5.7. The port based on the
> > > FreeBSD-4.0-current make version from 9th September 1999.
> > > 
> > > I successfully compiled pmake itself and the FreeBSD Web server.
> > > 
> > > The binaries are available at
> > > http://www.de.freebsd.org/~wosch/src/pmake/
> > This should be nice.  The number of solaris boxen I administering
> > seems to be growing faster that the FBSD boxen.  Nice work & thanxs ...
> 
> I'm still fighting to get a FBSD boxen into the office...have my immediate
> boss convinced that we should, but her boss is still convinced that
> Solaris is the only Unix OS out there *sigh*
Take a look here http://www.scnc.k12.mi.us/.  This is a project managed by
the Technical Support Services Group in the Computer Lab here at MSU.  FreeBSD
is run on all the S.C.N.C. servers.  Many of the tech staff within the Technical
Services run FreeBSD on our desktops.  Contact Matt Kolb at muk@bender.cl.msu.edu
for more info on what they're doing.  Cheuck Henrich who use to head the project
when he was the leader of the Special Projects group could also tell you more.
I don't have his email address at hand, but search the hackers mailing list 
and you'll find some postings from him.  He's no longer at MSU, but the company
he's working for used FreeBSD for some graphics rendering engine for the movie
"The Matrix" ...

> 
> Does anyone have any *good* comparisons between the two?  Something like
> the work that Brad Knowles (?) did recently with Vinum vs DPT SmartCache
> controllers?
> 
> If nobody...I'm just working on a Dual PIII upgrade to one of our servers
> here...if someone could suggest a 'test suite' that I could run on FreeBSD
> (SMP) before I switched things over to Solaris, I'd be more then willing
> to run it through so that it was a 'same hardware' scenario.  The system
> (hardware-wise) I'm building is such that it is 'FreeBSD-friendly', as
> are all the x86 systems I'm building...
> 
> 
> Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
> Systems Administrator @ hub.org 
> primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 
> 
Keep plugging away scrappy, you'll get FBSD in there.  Also check the main web site
for large companies (like yahoo)  that are using freebsd ...

#:^)
-- 
So ya want ta here da roots?
Dem that feels it knows it ...
bush doctor <dervish@bantu.cl.msu.edu>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 10:32:30 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from bantu.cl.msu.edu (bantu.cl.msu.edu [35.8.3.18])
	by hub.freebsd.org (Postfix) with ESMTP id DA9E514E66
	for <Freebsd-hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 10:32:27 -0700 (PDT)
	(envelope-from dervish@bantu.cl.msu.edu)
Received: (from dervish@localhost)
	by bantu.cl.msu.edu (8.9.3/8.9.3) id NAA22066;
	Thu, 16 Sep 1999 13:32:09 -0400 (EDT)
	(envelope-from dervish)
Date: Thu, 16 Sep 1999 13:32:09 -0400
From: bush doctor <dervish@bantu.cl.msu.edu>
To: Gregory_D_Moncreaff@res.raytheon.com
Cc: Freebsd-hackers@FreeBSD.ORG
Subject: Re: boston globe article....
Message-ID: <19990916133209.D21952@bantu.cl.msu.edu>
References: <852567EE.005A71C3.00@ressud-as01.res.ray.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <852567EE.005A71C3.00@ressud-as01.res.ray.com>; from Gregory_D_Moncreaff@res.raytheon.com on Thu, Sep 16, 1999 at 12:27:37PM -0400
X-Operating-System: FreeBSD 4.0-CURRENT i386
X-PGP-Fingerprint: 35 95 F8 63 DA 5B 32 51  8F A9 AC 3C B4 74 F3 BA
WWW-Home-Page: http://www.msu.edu/~ikhala
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Out of da blue Gregory_D_Moncreaff@res.raytheon.com aka (Gregory_D_Moncreaff@res.raytheon.com) said:
> http://www.boston.com/dailyglobe2/259/business/Even_better_than_Linux+.shtml
Looks like that url should be ...

	http://www.boston.com/technology/plugged.shtml

#:^)
-- 
So ya want ta here da roots?
Dem that feels it knows it ...
bush doctor <dervish@bantu.cl.msu.edu>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 11:37:52 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from unix1.it-datacntr.louisville.edu (unix1.it-datacntr.louisville.edu [136.165.4.27])
	by hub.freebsd.org (Postfix) with ESMTP id 20C6314D61
	for <freebsd-hackers@freebsd.org>; Thu, 16 Sep 1999 11:37:41 -0700 (PDT)
	(envelope-from k.stevenson@louisville.edu)
Received: from homer.louisville.edu (ktstev01@homer.louisville.edu [136.165.1.20])
	by unix1.it-datacntr.louisville.edu (8.8.8/8.8.7) with ESMTP id OAA28444
	for <freebsd-hackers@freebsd.org>; Thu, 16 Sep 1999 14:37:25 -0400
Received: (from ktstev01@localhost)
	by homer.louisville.edu (8.8.8/8.8.8) id OAA11989
	for freebsd-hackers@freebsd.org; Thu, 16 Sep 1999 14:37:24 -0400 (EDT)
Message-ID: <19990916143724.F17119@homer.louisville.edu>
Date: Thu, 16 Sep 1999 14:37:24 -0400
From: Keith Stevenson <k.stevenson@louisville.edu>
To: freebsd-hackers@freebsd.org
Subject: Re: cache-friendly scheduling for SMP
References: <199909161225.MAA14962@jules.res.cmu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199909161225.MAA14962@jules.res.cmu.edu>; from greg on Thu, Sep 16, 1999 at 12:25:52PM +0000
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Sep 16, 1999 at 12:25:52PM +0000, greg wrote:
> I'm trying to run 1-2 processes with very large memory footprints on my P2 SMP 
> machine.  I'm finding that the process switches cpu's quite often, which 
> obviously isn't good for the caches on the CPU.
> 
> Can anybody point me to a paper, mailing list discussion, etc. that discusses 
> scheduling processes to not thrash the cpu caches?  Or if there's anything in 
> place, how I can take advantage of it, etc.  I got stumped on the idea a while 
> ago, so I'm really curious...

<Disclaimer>
All I've heard is a marketing presentation.  I haven't seen this is the real
world yet.
</Disclaimer>

IBM just released a new version of AIX (4.3.3).  One of the big features is
CPU affinity in order to made better use of the CPU caches.  They claim to
have done this be having a separate run queue for each CPU.

Just food for thought,
--Keith Stevenson--

-- 
Keith Stevenson
System Programmer - Data Center Services - University of Louisville
k.stevenson@louisville.edu
PGP key fingerprint =  4B 29 A8 95 A8 82 EA A2  29 CE 68 DE FC EE B6 A0


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 11:44:48 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32])
	by hub.freebsd.org (Postfix) with SMTP id 8EFA814E03
	for <freebsd-hackers@freebsd.org>; Thu, 16 Sep 1999 11:44:45 -0700 (PDT)
	(envelope-from dscheidt@enteract.com)
Received: (qmail 94177 invoked from network); 16 Sep 1999 18:44:44 -0000
Received: from shell-3.enteract.com (dscheidt@207.229.143.42)
  by pop3-3.enteract.com with SMTP; 16 Sep 1999 18:44:44 -0000
Date: Thu, 16 Sep 1999 13:44:44 -0500 (CDT)
From: David Scheidt <dscheidt@enteract.com>
To: Keith Stevenson <k.stevenson@louisville.edu>
Cc: freebsd-hackers@freebsd.org
Subject: Re: cache-friendly scheduling for SMP
In-Reply-To: <19990916143724.F17119@homer.louisville.edu>
Message-ID: <Pine.NEB.3.96.990916134320.32436A-100000@shell-3.enteract.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 16 Sep 1999, Keith Stevenson wrote:

> On Thu, Sep 16, 1999 at 12:25:52PM +0000, greg wrote:
> > I'm trying to run 1-2 processes with very large memory footprints on my P2 SMP 
> > machine.  I'm finding that the process switches cpu's quite often, which 
> > obviously isn't good for the caches on the CPU.
> > 
> > Can anybody point me to a paper, mailing list discussion, etc. that discusses 
> > scheduling processes to not thrash the cpu caches?  Or if there's anything in 
> > place, how I can take advantage of it, etc.  I got stumped on the idea a while 
> > ago, so I'm really curious...
> 
> <Disclaimer>
> All I've heard is a marketing presentation.  I haven't seen this is the real
> world yet.
> </Disclaimer>
> 
> IBM just released a new version of AIX (4.3.3).  One of the big features is
> CPU affinity in order to made better use of the CPU caches.  They claim to
> have done this be having a separate run queue for each CPU.

Someone posted some stuff about this to -SMP a bit ago.  They had produced a
cheduler that prefereed to run a process on the cpu it last ran on.  Go
check the archives.  Would have been 6 or 8 weeks ago, I think

David



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 11:59:24 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from xylan.com (postal.xylan.com [208.8.0.248])
	by hub.freebsd.org (Postfix) with ESMTP id 89D6414D61
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 11:59:17 -0700 (PDT)
	(envelope-from wes@softweyr.com)
Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT]))
	id LAA12576; Thu, 16 Sep 1999 11:56:46 -0700 (PDT)
Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB]))
	id LAA28364; Thu, 16 Sep 1999 11:44:52 -0700
Received: from softweyr.com (dyn4.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL]))
	id AA17205; Thu, 16 Sep 99 11:56:39 PDT
Message-Id: <37E13D66.AB9889B8@softweyr.com>
Date: Thu, 16 Sep 1999 12:56:38 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386)
X-Accept-Language: en
Mime-Version: 1.0
To: Christopher Sedore <cmsedore@mailbox.syr.edu>
Cc: Ruslan Ermilov <ru@ucb.crimea.ua>,
	Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: kern/13075 (was: Re: aio_*)
References: <Pine.SOL.4.10.9909151232330.1425-100000@rodan.syr.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Christopher Sedore wrote:
> 
> On Wed, 15 Sep 1999, Ruslan Ermilov wrote:
> >
> > Do you by any change have an idea how to fix PR kern/13075
> > (signal is not posted for async I/O on raw devices)
> 
> Yes.  There is no code to post the signal unless the job is of the lio
> variety.  Writing a fix took about 15 minutes (including reboot).
> Extensive testing not included, though the test program provided with the
> PR now functions.

Great, now do you want to tackle aio_cancel?  ;^)

-- 
            "Where am I, and what am I doing in this handbasket?"

Wes Peters                                                         Softweyr LLC
http://softweyr.com/                                           wes@softweyr.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 12: 3:30 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29])
	by hub.freebsd.org (Postfix) with ESMTP id 41B7514F6F
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 12:03:26 -0700 (PDT)
	(envelope-from cmsedore@mailbox.syr.edu)
Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.9FE6A910@mailer.syr.edu>; Thu, 16 Sep 1999 15:03:24 -0400
Received: from localhost (cmsedore@localhost)
	by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id PAA22627;
	Thu, 16 Sep 1999 15:03:21 -0400 (EDT)
X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs
Date: Thu, 16 Sep 1999 15:03:21 -0400 (EDT)
From: Christopher Sedore <cmsedore@mailbox.syr.edu>
X-Sender: cmsedore@rodan.syr.edu
To: Wes Peters <wes@softweyr.com>
Cc: Ruslan Ermilov <ru@ucb.crimea.ua>,
	Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: kern/13075 (was: Re: aio_*)
In-Reply-To: <37E13D66.AB9889B8@softweyr.com>
Message-ID: <Pine.SOL.4.10.9909161501270.1425-100000@rodan.syr.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG




On Thu, 16 Sep 1999, Wes Peters wrote:

> Christopher Sedore wrote:
> > 
> > On Wed, 15 Sep 1999, Ruslan Ermilov wrote:
> > >
> > > Do you by any change have an idea how to fix PR kern/13075
> > > (signal is not posted for async I/O on raw devices)
> > 
> > Yes.  There is no code to post the signal unless the job is of the lio
> > variety.  Writing a fix took about 15 minutes (including reboot).
> > Extensive testing not included, though the test program provided with the
> > PR now functions.
> 
> Great, now do you want to tackle aio_cancel?  ;^)

I've been holding off to see whether I can get the other aio patches for
improved socket io committed.  I don't want to do two versions of
aio_cancel (the changes for sockets alter the way things are queued and
hence the way that cancels have to be done).

-Chris



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 12:56:17 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dt014nb6.san.rr.com (dt014nb6.san.rr.com [24.30.129.182])
	by hub.freebsd.org (Postfix) with ESMTP
	id 51BDF154A4; Thu, 16 Sep 1999 12:56:12 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from localhost (doug@localhost)
	by dt014nb6.san.rr.com (8.9.3/8.8.8) with ESMTP id NAA26232;
	Thu, 16 Sep 1999 13:30:30 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Date: Thu, 16 Sep 1999 13:30:30 -0700 (PDT)
From: Doug <Doug@gorean.org>
X-Sender: doug@dt014nb6.san.rr.com
To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Cc: hackers@freebsd.org, sos@freebsd.org, bde@freebsd.org
Subject: Re: panic() the system from the console (was: Re: kern/13721: There
 is  no way to force system panic from console)
In-Reply-To: <199909160948.SAA02636@zodiac.mech.utsunomiya-u.ac.jp>
Message-ID: <Pine.BSF.4.10.9909161329200.26117-100000@dt014nb6.san.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> As the originator suggested in his subsequent posting to the PR
> database, we can defined "panic" key and handle it in syscons
> as follows:

	Would not the 'panic' option in DDB be enough to handle this, or
am I missing something? I'm not opposed to adding a panic() key combo,
just wondering if it's duplicating existing technology.

Doug
-- 
"My mama told me, my mama said, 'don't cry.' She said, 'you're too young a man
to have as many women you got.' I looked at my mother dear and didn't even
crack a smile. I said, 'If women kill me, I don't mind dyin!'" 

    - John Belushi as "Joliet" Jake Blues, "I Don't Know"



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 13: 1: 9 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp2.free.fr (smtp2.free.fr [212.27.32.6])
	by hub.freebsd.org (Postfix) with ESMTP id CBA0B14E02
	for <hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 13:01:03 -0700 (PDT)
	(envelope-from nsouch@free.fr)
Received: from free.fr (paris11-53-229.dial.proxad.net [212.27.53.229])
	by smtp2.free.fr (8.9.3/8.9.3/Debian/GNU) with ESMTP id WAA07869;
	Thu, 16 Sep 1999 22:00:39 +0200
Received: (from nsouch@localhost)
	by free.fr (8.9.3/8.9.1) id WAA08091;
	Thu, 16 Sep 1999 22:04:26 +0200 (CEST)
	(envelope-from nsouch)
Message-ID: <19990916220426.04913@breizh.free.fr>
Date: Thu, 16 Sep 1999 22:04:26 +0200
From: Nicolas Souchu <nsouch@free.fr>
To: Tony Finch <dot@dotat.at>
Cc: peter@netplex.com.au, hackers@FreeBSD.ORG
Subject: Re: damn ATX power supplies...
References: <Pine.BSF.4.10.9909110020500.28670-100000@picnic.mat.net> <19990911103119.4253B1CB1@overcee.netplex.com.au> <E11QHWj-000Cbr-00@fanf.noc.demon.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81e
In-Reply-To: <E11QHWj-000Cbr-00@fanf.noc.demon.net>; from Tony Finch on Sun, Sep 12, 1999 at 10:51:13PM +0100
X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT 
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 12, 1999 at 10:51:13PM +0100, Tony Finch wrote:
>
>Peter Wemm <peter@netplex.com.au> wrote:
>>
>>On newer motherboards, it's addressable on the SMB bus (along with
>>the SIMMS, the LM78/LM75/etc, the embedded LM75 in the newer CPU,
>>etc). Anyway, the newer devices are programmable to do things like
>>the 4-second power off delay, auto-on with AC, maintain previous
>>state when AC restored, alarm clock time auto start, as well as the
>>usual "turn off now" command from the APM bios.
>
>Is there any software out there that speaks to /dev/smb?
>intelligently? We have some Dell boxen with loads of SMB stuff in
>them; it'd be nice to be able to see what's going on there.
>
>Alternatively, are there freely-available SMB specs?

Most is at http://www.freebsd.org/~nsouch/iicbus.html

Nicholas

>
>Tony.
>-- 
>f.a.n.finch    dot@dotat.at    fanf@demon.net    e pluribus unix
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-hackers" in the body of the message
>

-- 
nsouch@free.fr / nsouch@freebsd.org
FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 14:33:31 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from ns.skylink.it (ns.skylink.it [194.177.113.1])
	by hub.freebsd.org (Postfix) with ESMTP id C37F214DD0
	for <hackers@freebsd.org>; Thu, 16 Sep 1999 14:33:25 -0700 (PDT)
	(envelope-from hibma@skylink.it)
Received: from heidi.plazza.it (va-165.skylink.it [194.185.55.165])
	by ns.skylink.it (8.9.1/8.8.8) with ESMTP id XAA10237
	for <hackers@freebsd.org>; Thu, 16 Sep 1999 23:33:22 +0200
Received: from localhost (localhost [127.0.0.1])
	by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id VAA31655
	for <hackers@freebsd.org>; Thu, 16 Sep 1999 21:22:49 GMT
X-No-Spam: Neither the receipients nor the senders email address(s) are
	to be used for Unsolicited (Commercial) Email without the
	explicit written consent of either party; as a per-message
	fee is incurred for inbound and outbound traffic to the originator.
Posted-Date: Thu, 16 Sep 1999 21:22:49 GMT
Date: Thu, 16 Sep 1999 23:22:49 +0200 (CEST)
From: Nick Hibma <hibma@skylink.it>
X-Sender: n_hibma@heidi.plazza.it
Reply-To: Nick Hibma <hibma@skylink.it>
To: FreeBSD Hackers mailing list <hackers@freebsd.org>
Subject: nuking a vnode
Message-ID: <Pine.BSF.4.10.9909162322170.30216-100000@heidi.plazza.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


How do I nuke vnodes? This is the NetBSD code that needs to be emulated:

        /* locate the major number */
        for (maj = 0; maj < nchrdev; maj++)
                if (cdevsw[maj].d_open == ulptopen)
                        break;

        /* Nuke the vnodes for any open instances (calls close). */
        mn = self->dv_unit;
        vdevgone(maj, mn, mn, VCHR);


-- 
e-Mail: hibma@skylink.it



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 14:56:43 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
	by hub.freebsd.org (Postfix) with ESMTP id 16DF6151B9
	for <hackers@FreeBSD.org>; Thu, 16 Sep 1999 14:56:38 -0700 (PDT)
	(envelope-from green@FreeBSD.org)
Received: from localhost (green@localhost)
	by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id RAA31653;
	Thu, 16 Sep 1999 17:56:25 -0400 (EDT)
X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs
Date: Thu, 16 Sep 1999 17:56:25 -0400 (EDT)
From: "Brian F. Feldman" <green@FreeBSD.org>
X-Sender: green@janus.syracuse.net
To: Nick Hibma <hibma@skylink.it>
Cc: FreeBSD Hackers mailing list <hackers@FreeBSD.org>
Subject: Re: nuking a vnode
In-Reply-To: <Pine.BSF.4.10.9909162322170.30216-100000@heidi.plazza.it>
Message-ID: <Pine.BSF.4.10.9909161753180.29724-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 16 Sep 1999, Nick Hibma wrote:

> 
> How do I nuke vnodes? This is the NetBSD code that needs to be emulated:
> 
>         /* locate the major number */
>         for (maj = 0; maj < nchrdev; maj++)
>                 if (cdevsw[maj].d_open == ulptopen)
>                         break;
> 
>         /* Nuke the vnodes for any open instances (calls close). */
>         mn = self->dv_unit;
>         vdevgone(maj, mn, mn, VCHR);
> 

Did you try taking a look at VOP_REVOKE()? It seems to be what you're
looking for.

-- 
 Brian Fundakowski Feldman           /  "Any sufficiently advanced bug is    \
 green@FreeBSD.org                   |   indistinguishable from a feature."  |
     FreeBSD: The Power to Serve!    \        -- Rich Kulawiec               /



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 16:11:49 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP id 764BC15486
	for <hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 16:11:40 -0700 (PDT)
	(envelope-from julian@whistle.com)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
	by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id QAA23763;
	Thu, 16 Sep 1999 16:11:37 -0700 (PDT)
Date: Thu, 16 Sep 1999 16:11:36 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
To: Nick Hibma <hibma@skylink.it>
Cc: FreeBSD Hackers mailing list <hackers@FreeBSD.ORG>
Subject: Re: nuking a vnode
In-Reply-To: <Pine.BSF.4.10.9909162322170.30216-100000@heidi.plazza.it>
Message-ID: <Pine.BSF.3.95.990916160744.295A-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Thu, 16 Sep 1999, Nick Hibma wrote:

> 
> How do I nuke vnodes? This is the NetBSD code that needs to be emulated:
> 
>         /* locate the major number */
>         for (maj = 0; maj < nchrdev; maj++)
>                 if (cdevsw[maj].d_open == ulptopen)
>                         break;
> 
>         /* Nuke the vnodes for any open instances (calls close). */
>         mn = self->dv_unit;
>         vdevgone(maj, mn, mn, VCHR);

In -current something like:

int major;
dev_t dev;
struct vnode *vp;

major = ultp_cdevsw.d_maj;
dev = makedev(major, self->dv_unit)
vp = SLIST_FIRST(&dev->si_hlist);
if (vp) {
	VOP_REVOKE(vp. REVOKEALL);
}
remove_dev(dev);

3.3 will be considerably different.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 16:16:44 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP id 239E314FBC
	for <hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 16:16:34 -0700 (PDT)
	(envelope-from julian@whistle.com)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
	by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id QAA23938;
	Thu, 16 Sep 1999 16:16:32 -0700 (PDT)
Date: Thu, 16 Sep 1999 16:16:32 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
To: Nick Hibma <hibma@skylink.it>
Cc: FreeBSD Hackers mailing list <hackers@FreeBSD.ORG>
Subject: Re: nuking a vnode
In-Reply-To: <Pine.BSF.3.95.990916160744.295A-100000@current1.whistle.com>
Message-ID: <Pine.BSF.3.95.990916161558.295B-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Thu, 16 Sep 1999, Julian Elischer wrote:

> 
> On Thu, 16 Sep 1999, Nick Hibma wrote:
> 
> > 
> > How do I nuke vnodes? This is the NetBSD code that needs to be emulated:
> > 
> >         /* locate the major number */
> >         for (maj = 0; maj < nchrdev; maj++)
> >                 if (cdevsw[maj].d_open == ulptopen)
> >                         break;
> > 
> >         /* Nuke the vnodes for any open instances (calls close). */
> >         mn = self->dv_unit;
> >         vdevgone(maj, mn, mn, VCHR);
> 
> In -current something like:
> 
> int major;
> dev_t dev;
> struct vnode *vp;
> 
> major = ultp_cdevsw.d_maj;
> dev = makedev(major, self->dv_unit)
> vp = SLIST_FIRST(&dev->si_hlist);
> if (vp) {
> 	VOP_REVOKE(vp. REVOKEALL);
                     ^  comma (,)

> }
> remove_dev(dev);
> 
> 3.3 will be considerably different.
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 16:55:39 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from xylan.com (postal.xylan.com [208.8.0.248])
	by hub.freebsd.org (Postfix) with ESMTP id 18AA915594
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 16:55:36 -0700 (PDT)
	(envelope-from wes@softweyr.com)
Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT]))
	id QAA17829; Thu, 16 Sep 1999 16:52:07 -0700 (PDT)
Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB]))
	id QAA10300; Thu, 16 Sep 1999 16:40:09 -0700
Received: from softweyr.com (dyn4.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL]))
	id AA04321; Thu, 16 Sep 99 16:52:01 PDT
Message-Id: <37E182A1.7F84BCD0@softweyr.com>
Date: Thu, 16 Sep 1999 17:52:01 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386)
X-Accept-Language: en
Mime-Version: 1.0
To: Christopher Sedore <cmsedore@mailbox.syr.edu>
Cc: Ruslan Ermilov <ru@ucb.crimea.ua>,
	Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: kern/13075 (was: Re: aio_*)
References: <Pine.SOL.4.10.9909161501270.1425-100000@rodan.syr.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Christopher Sedore wrote:
> 
> On Thu, 16 Sep 1999, Wes Peters wrote:
> 
> > Christopher Sedore wrote:
> > >
> > > On Wed, 15 Sep 1999, Ruslan Ermilov wrote:
> > > >
> > > > Do you by any change have an idea how to fix PR kern/13075
> > > > (signal is not posted for async I/O on raw devices)
> > >
> > > Yes.  There is no code to post the signal unless the job is of the lio
> > > variety.  Writing a fix took about 15 minutes (including reboot).
> > > Extensive testing not included, though the test program provided with the
> > > PR now functions.
> >
> > Great, now do you want to tackle aio_cancel?  ;^)
> 
> I've been holding off to see whether I can get the other aio patches for
> improved socket io committed.  I don't want to do two versions of
> aio_cancel (the changes for sockets alter the way things are queued and
> hence the way that cancels have to be done).

Good to hear.  OK, show of hands: who's using aio_* and has the time to
test patches for Christopher?

-- 
            "Where am I, and what am I doing in this handbasket?"

Wes Peters                                                         Softweyr LLC
http://softweyr.com/                                           wes@softweyr.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 19:34:17 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200])
	by hub.freebsd.org (Postfix) with ESMTP id 1E5E714E8A
	for <hackers@freebsd.org>; Thu, 16 Sep 1999 19:34:09 -0700 (PDT)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1])
	by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id LAA10868
	for <hackers@freebsd.org>; Fri, 17 Sep 1999 11:33:54 +0900 (JST)
Message-Id: <199909170233.LAA10868@shidahara1.planet.sci.kobe-u.ac.jp>
To: hackers@freebsd.org
Dcc: 
Subject: Re: damn ATX power supplies... 
In-reply-to: Your message of "Thu, 16 Sep 1999 22:04:26 +0200"
References: <Pine.BSF.4.10.9909110020500.28670-100000@picnic.mat.net> <19990911103119.4253B1CB1@overcee.netplex.com.au>
	 <E11QHWj-000Cbr-00@fanf.noc.demon.net>  <19990916220426.04913@breizh.free.fr> 
Date: Fri, 17 Sep 1999 11:33:53 +0900
From: Takanori Watanabe <takawata@shidahara1.planet.sci.kobe-u.ac.jp>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <19990916220426.04913@breizh.free.fr>, Nicolas Souchu wrote:
>On Sun, Sep 12, 1999 at 10:51:13PM +0100, Tony Finch wrote:
>>
>>Peter Wemm <peter@netplex.com.au> wrote:
>>>
>>>On newer motherboards, it's addressable on the SMB bus (along with
>>>the SIMMS, the LM78/LM75/etc, the embedded LM75 in the newer CPU,
>>>etc). Anyway, the newer devices are programmable to do things like
>>>the 4-second power off delay, auto-on with AC, maintain previous
>>>state when AC restored, alarm clock time auto start, as well as the
>>>usual "turn off now" command from the APM bios.

I think 4-second power off delay etc. is not so related with SMBus but power 
management controller on PCI.And that should be probed via ACPI BIOS table,not 
PCI probe,though I wrote a patch for intpm so that it install
 power off handler.
<URL:http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/sys/intpmpm.tar.gz>

>>Is there any software out there that speaks to /dev/smb?
>>intelligently? We have some Dell boxen with loads of SMB stuff in
>>them; it'd be nice to be able to see what's going on there.
>>
>>Alternatively, are there freely-available SMB specs?
>

I have some piece of program.(Accessing SPD,LM75/LM78)
<URL:http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/>
But general problem is that there is no way to probe from hardware.
And on PIIX4, most hardware monitoring chip have ISA interface and accessable
at port 0x295,0x296.

BTW I looked datasheet of i810 chipset 
<URL:http://developer.intel.com/design/chipsets/datashts/29065503.pdf>
and find SMBus functional and Power Management functional is separated.
Though I don't write the driver for it  because I don't have it.

Takanori Watanabe
<a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html">
Public Key</a>
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 

P.S. Are there any people to work on audio and telephony device on i810?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 20:25:52 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP id A1F3C14EBD
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 20:25:47 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id MAA62780;
	Fri, 17 Sep 1999 12:54:19 +0930 (CST)
Date: Fri, 17 Sep 1999 12:54:19 +0930
From: Greg Lehey <grog@lemis.com>
To: Assar Westerlund <assar@sics.se>
Cc: Zhihui Zhang <zzhang@cs.binghamton.edu>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: Kernel debugging questions
Message-ID: <19990917125419.G55065@freebie.lemis.com>
References: <Pine.GSO.3.96.990819213328.29326A-100000@sol.cs.binghamton.edu> <5lvha945ln.fsf@assaris.sics.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <5lvha945ln.fsf@assaris.sics.se>; from Assar Westerlund on Sat, Aug 21, 1999 at 03:37:40PM +0200
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
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-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Saturday, 21 August 1999 at 15:37:40 +0200, Assar Westerlund wrote:
> Zhihui Zhang <zzhang@cs.binghamton.edu> writes:
>> Thanks for your response.  I can not think of those points myself.
>> However, on page 7 of the book "Panic! Unix system crash dump analysis",
>> it says that a debugger named kadb in SunOS can load the real kernel
>> during boot and treat the latter like a great, big, user program, stepping
>> through its execution, examining and modifying values on the fly.
>>
>> It seems to me that FreeBSD does not have such a debugger. Maybe ddb can
>> do so, but it works with assembly.
>
> kadb also works with assembly.  That being said, I much prefer ddb to
> kadb, and of course remote gdb is *much* nicer.

[catching up]

The nice thing about kadb is that it has a usable macro languge.

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-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 21:10:30 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
	by hub.freebsd.org (Postfix) with ESMTP id 9421815432
	for <freebsd-hackers@freebsd.org>; Thu, 16 Sep 1999 21:10:22 -0700 (PDT)
	(envelope-from aron@cs.rice.edu)
Received: (from aron@localhost)
	by cs.rice.edu (8.9.0/8.9.0) id XAA11255
	for freebsd-hackers@freebsd.org; Thu, 16 Sep 1999 23:10:21 -0500 (CDT)
Date: Thu, 16 Sep 1999 23:10:21 -0500 (CDT)
From: Mohit Aron <aron@cs.rice.edu>
Message-Id: <199909170410.XAA11255@cs.rice.edu>
To: freebsd-hackers@freebsd.org
Subject: TLB miss handler for alpha running FreeBSD-4.0
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,
	as I understand it, TLB misses on the alpha are handled by the 
software (as opposed to x86 where they are handled in hardware). Can someone
help me with the FreeBSD code. I'm trying to locate the kernel code that
implements the TLB handler. I'd appreciate if someone can tell me how the 
control is given to the software (i.e. what trap is generated), how the
handler is called and finally how does the control return back. Thanks,



- Mohit


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 22: 3:47 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66])
	by hub.freebsd.org (Postfix) with ESMTP
	id 547F615893; Thu, 16 Sep 1999 22:03:43 -0700 (PDT)
	(envelope-from adsharma@c62443-a.frmt1.sfba.home.com)
Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165])
          by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111)
          with ESMTP
          id <19990917050343.EHXE29487.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>;
          Thu, 16 Sep 1999 22:03:43 -0700
Received: (from adsharma@localhost)
	by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id WAA07157;
	Thu, 16 Sep 1999 22:03:43 -0700
Date: Thu, 16 Sep 1999 22:03:42 -0700
From: Arun Sharma <adsharma@home.com>
To: greg <greg@jules.res.cmu.edu>
Cc: freebsd-smp@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: Re: cache-friendly scheduling for SMP
Message-ID: <19990916220342.A7136@home.com>
References: <199909161225.MAA14962@jules.res.cmu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <199909161225.MAA14962@jules.res.cmu.edu>; from greg on Thu, Sep 16, 1999 at 12:25:52PM +0000
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Sep 16, 1999 at 12:25:52PM +0000, greg wrote:

> Can anybody point me to a paper, mailing list discussion, etc. that discusses 
> scheduling processes to not thrash the cpu caches?  Or if there's anything in 
> place, how I can take advantage of it, etc.  I got stumped on the idea
> a while ago, so I'm really curious...

In -current, there is already code to do trivial CPU affinity. Basically,
given multiple processes in the same priority queue to choose from, the
scheduler will pick the one that last ran on the same CPU.

	-Arun


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Thu Sep 16 23:27:26 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32])
	by hub.freebsd.org (Postfix) with ESMTP id 6E00114EEF
	for <hackers@FreeBSD.ORG>; Thu, 16 Sep 1999 23:27:23 -0700 (PDT)
	(envelope-from dwhite@resnet.uoregon.edu)
Received: from localhost (dwhite@localhost)
	by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id XAA74562;
	Thu, 16 Sep 1999 23:25:53 -0700 (PDT)
	(envelope-from dwhite@resnet.uoregon.edu)
Date: Thu, 16 Sep 1999 23:25:53 -0700 (PDT)
From: Doug White <dwhite@resnet.uoregon.edu>
To: Ruslan Ermilov <ru@ucb.crimea.ua>
Cc: hackers@FreeBSD.ORG
Subject: Re: Multiple NAT alias addresses
In-Reply-To: <19990915104350.G86648@relay.ucb.crimea.ua>
Message-ID: <Pine.BSF.4.10.9909162320300.66443-100000@resnet.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 15 Sep 1999, Ruslan Ermilov wrote:

> > - Trailing spaces and empty lines are ignored.
> > - A `#' sign will mark the remaining of the line as a comment.
> > 
> > Reviewed by:    Ari Suutari <ari@suutari.iki.fi>
> > 
> > Perhaps the parser is skipping my redirect_port lines?
> > 
> Yeah, I committed this change after one guy had the problems with
> redirect_port's not happening.  He had `#' after `redirect_port' line,
> and natd(8) silently ignored it.  But you said that it works for you
> without specifying publicIP, so this shouldn't be the case here.

Ah, ok.

An update:

I set up a test config at work with some spare boxes.  I found that if you
specify an aliasIP that is the primary alias address (as determined by the
-n or -a options), those redirections will be ignored.  Others continue to
work.  I don't know why they weren't working on the real box, I may had
made a mistake there.

So this file is wrong:

interface fxp0  
redirect_port 10.0.0.1:ssh 128.1.1.1:ssh
redirect_port 10.0.0.2:ssh 128.1.1.2:ssh

But this correct:

interface fxp0
redirect_port 10.0.0.1:ssh ssh
redirect_port 10.0.0.2:ssh 128.1.1.2:ssh

There is some logic in natd to handle the wrong case so that it is
equivalent to the right case, but that logic may be flawed.

> I just copied your config file from your original posting, see attached.
> But PLEASE MAKE SURE you have no trailing whitespaces at the end of
> your redirect_port rules!

I'll be sure to keep the whitespace pollution down.

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-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17  0:16:16 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65])
	by hub.freebsd.org (Postfix) with ESMTP id D813E14D65
	for <hackers@freebsd.org>; Fri, 17 Sep 1999 00:16:12 -0700 (PDT)
	(envelope-from nick.hibma@jrc.it)
Received: from elect8 (elect8.jrc.it [139.191.71.152])
	by mrelay.jrc.it (LMC5692) with ESMTP id JAA10076; Fri, 17 Sep 1999 09:16:03 +0200 (MET DST)
Date: Fri, 17 Sep 1999 09:16:03 +0200 (MET DST)
From: Nick Hibma <nick.hibma@jrc.it>
X-Sender: n_hibma@elect8
Reply-To: Nick Hibma <nick.hibma@jrc.it>
To: Julian Elischer <julian@whistle.com>
Cc: FreeBSD Hackers mailing list <hackers@FreeBSD.ORG>
Subject: Re: nuking a vnode
In-Reply-To: <Pine.BSF.3.95.990916160744.295A-100000@current1.whistle.com>
Message-ID: <Pine.GS4.4.10.9909170914210.9900-100000@elect8>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

 > int major;
 > dev_t dev;
 > struct vnode *vp;
 > 
 > major = ultp_cdevsw.d_maj;
 > dev = makedev(major, self->dv_unit)
 > vp = SLIST_FIRST(&dev->si_hlist);

if (vfinddev(dev, VCHR, &vp))
	VOP_REVOKE(vp, REVOKEALL);

#if 0
 > if (vp) {
 > 	VOP_REVOKE(vp. REVOKEALL);
 > }
#endif

 > remove_dev(dev);

/* Good one! I had not yet thought about that one */

 > 3.3 will be considerably different.

Not one of my main concerns.

Nick

-- 
ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17  1:21:57 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from ns.itga.com.au (ns.itga.com.au [192.83.119.129])
	by hub.freebsd.org (Postfix) with ESMTP id 73F8C14D2A
	for <hackers@freebsd.org>; Fri, 17 Sep 1999 01:21:38 -0700 (PDT)
	(envelope-from gnb@itga.com.au)
Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20])
	by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id SAA07482
	for <hackers@freebsd.org>; Fri, 17 Sep 1999 18:21:35 +1000 (EST)
Received: from lightning (lightning [192.168.71.20])
	by lightning.itga.com.au (8.9.1a/8.9.1) with ESMTP id SAA15276;
	Fri, 17 Sep 1999 18:21:35 +1000 (EST)
Message-Id: <199909170821.SAA15276@lightning.itga.com.au>
X-Mailer: exmh version 2.0.1 12/23/97
From: Gregory Bond <gnb@itga.com.au>
To: hackers@freebsd.org
Subject: "style" question
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 17 Sep 1999 18:21:35 +1000
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm looking at cleaning up a few compile nits and I'm wondering what the
officially approved way of silencing "may not be used" warnings:

int
foo(int flag)
{
        int j;

        if (flag) 
                j = 1;

        /* 
         * This noop statement is enough to confuse the optimiser so it 
         * forgets that j is initialised iff flag != 0 
         */
        flag = !!flag; 

        if (flag)
                return j;
        return 0;
}

Us humans can see that j is not used without being set, but cc can't. How do I 
remove this warning in a style(9)-compatible way?




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17  1:32: 6 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
	by hub.freebsd.org (Postfix) with ESMTP id 61C1414F90
	for <freebsd-hackers@freebsd.org>; Fri, 17 Sep 1999 01:32:02 -0700 (PDT)
	(envelope-from dfr@nlsystems.com)
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA69574;
	Fri, 17 Sep 1999 09:33:58 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Fri, 17 Sep 1999 09:33:57 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Mohit Aron <aron@cs.rice.edu>
Cc: freebsd-hackers@freebsd.org
Subject: Re: TLB miss handler for alpha running FreeBSD-4.0
In-Reply-To: <199909170410.XAA11255@cs.rice.edu>
Message-ID: <Pine.BSF.4.10.9909170930470.440-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 16 Sep 1999, Mohit Aron wrote:

> Hi,
> 	as I understand it, TLB misses on the alpha are handled by the 
> software (as opposed to x86 where they are handled in hardware). Can someone
> help me with the FreeBSD code. I'm trying to locate the kernel code that
> implements the TLB handler. I'd appreciate if someone can tell me how the 
> control is given to the software (i.e. what trap is generated), how the
> handler is called and finally how does the control return back. Thanks,

TLB misses are handled by the PALcode on the alpha (which is often part of
the firmware). There is no trap handler in the FreeBSD code which needs to
handle TLB misses as the PALcode deals with it transparently.

PALcode is 'special' software which runs at a higher privilege level than
the kernel and handles low-level traps, interrupts, etc., translating them
into a standard form for the kernel's consumption. If a later processor
revision needs different handling for low-level issues, it will use a
different PALcode but will generally present the same interface to the
kernel.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17  1:34: 9 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129])
	by hub.freebsd.org (Postfix) with ESMTP id C478014F90
	for <hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 01:34:02 -0700 (PDT)
	(envelope-from patrykz@mycenae.ilion.eu.org)
Received: from mycenae.ilion.eu.org (localhost [127.0.0.1])
	by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id SAA55426;
	Fri, 17 Sep 1999 18:33:49 +1000 (EST)
	(envelope-from patrykz@mycenae.ilion.eu.org)
Message-Id: <199909170833.SAA55426@mycenae.ilion.eu.org>
To: Gregory Bond <gnb@itga.com.au>
Cc: hackers@FreeBSD.ORG
Subject: Re: "style" question 
In-reply-to: Your message of "Fri, 17 Sep 1999 18:21:35 +1000."
             <199909170821.SAA15276@lightning.itga.com.au> 
Date: Fri, 17 Sep 1999 18:33:48 +1000
From: Patryk Zadarnowski <patrykz@mycenae.ilion.eu.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I'm looking at cleaning up a few compile nits and I'm wondering what the
> officially approved way of silencing "may not be used" warnings:
> 
> int
> foo(int flag)
> {
>         int j;
> 
>         if (flag) 
>                 j = 1;
> 
>         /* 
>          * This noop statement is enough to confuse the optimiser so it 
>          * forgets that j is initialised iff flag != 0 
>          */
>         flag = !!flag; 

I don't know about the "official"  way to silence the compiler (a well
placed  else statement  or a  "default" switch  case usually  does the
trick for  me) That is  to say, I'm  willing to argue that  fixing the
flow  of  control is  the  only  clean way  of  getting  rid of  these
warnings, unless  you know something special about  the allowed values
of  the offending variable  (eg.  you  know that  your switch  case is
exhaustive),  in which case  a dummy  "default" or  initializer cannot
hurt you much.

Also !!x IS NOT  a noop. For example, !!5 == 1.   I think you meant to
say `flag = ~~flag', which indeed is a NOP.

Pat.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17  2:46:12 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP
	id CEA3714F9F; Fri, 17 Sep 1999 02:46:04 -0700 (PDT)
	(envelope-from sheldonh@axl.noc.iafrica.com)
Received: from sheldonh (helo=axl.noc.iafrica.com)
	by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1)
	id 11RuaG-000J4D-00; Fri, 17 Sep 1999 11:45:36 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Doug <Doug@gorean.org>
Cc: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>,
	hackers@FreeBSD.ORG, sos@FreeBSD.ORG, bde@FreeBSD.ORG
Subject: Re: panic() the system from the console (was: Re: kern/13721: There is no way to force system panic from console) 
In-reply-to: Your message of "Thu, 16 Sep 1999 13:30:30 MST."
             <Pine.BSF.4.10.9909161329200.26117-100000@dt014nb6.san.rr.com> 
Date: Fri, 17 Sep 1999 11:45:36 +0200
Message-ID: <73296.937561536@axl.noc.iafrica.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Thu, 16 Sep 1999 13:30:30 MST, Doug wrote:

> 	Would not the 'panic' option in DDB be enough to handle this, or
> am I missing something?

He wanted a to be able to panic() a machine from console without being
able to drop to DDB from console. I think this is because he believes
that DDB is a security problem. :-)

Ciao,
Sheldon.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17  4:58:58 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id C0095156A5
	for <hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 04:58:52 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.3) id NAA58321;
	Fri, 17 Sep 1999 13:58:39 +0200 (CEST)
	(envelope-from des)
To: Gregory Bond <gnb@itga.com.au>
Cc: hackers@FreeBSD.ORG
Subject: Re: "style" question
References: <199909170821.SAA15276@lightning.itga.com.au>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 17 Sep 1999 13:58:38 +0200
In-Reply-To: Gregory Bond's message of "Fri, 17 Sep 1999 18:21:35 +1000"
Message-ID: <xzpwvtprbpt.fsf@flood.ping.uio.no>
Lines: 9
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Gregory Bond <gnb@itga.com.au> writes:
> Us humans can see that j is not used without being set, but cc can't. How do I 
> remove this warning in a style(9)-compatible way?

Initialize j.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17  5:13:26 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2])
	by hub.freebsd.org (Postfix) with SMTP id 8CB8B1588D
	for <hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 05:13:18 -0700 (PDT)
	(envelope-from nbm@rucus.ru.ac.za)
Received: (qmail 86248 invoked by uid 1003); 17 Sep 1999 12:15:10 -0000
Date: Fri, 17 Sep 1999 14:15:10 +0200
From: Neil Blakey-Milner <nbm@mithrandr.moria.org>
To: Gregory Bond <gnb@itga.com.au>
Cc: hackers@FreeBSD.ORG
Subject: Re: "style" question
Message-ID: <19990917141510.A85883@rucus.ru.ac.za>
References: <199909170821.SAA15276@lightning.itga.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <199909170821.SAA15276@lightning.itga.com.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri 1999-09-17 (18:21), Gregory Bond wrote:
> I'm looking at cleaning up a few compile nits and I'm wondering what the
> officially approved way of silencing "may not be used" warnings:
> 
> int
> foo(int flag)
> {
>         int j;
	j = 0;
>         if (flag) 
>                 j = 1;
> 
	return j;
> }

Or, if you really want to, use your other return scheme.

In other words, initialize j, probably to 0.

Neil
-- 
Neil Blakey-Milner
nbm@rucus.ru.ac.za


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17  5:51:13 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1])
	by hub.freebsd.org (Postfix) with ESMTP id 8B9B514A0E
	for <hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 05:49:49 -0700 (PDT)
	(envelope-from ru@ucb.crimea.ua)
Received: (from ru@localhost)
	by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id PAA03722;
	Fri, 17 Sep 1999 15:46:00 +0300 (EEST)
	(envelope-from ru)
Date: Fri, 17 Sep 1999 15:45:59 +0300
From: Ruslan Ermilov <ru@ucb.crimea.ua>
To: Doug White <dwhite@resnet.uoregon.edu>
Cc: hackers@FreeBSD.ORG
Subject: Re: Multiple NAT alias addresses
Message-ID: <19990917154559.A72386@relay.ucb.crimea.ua>
Mail-Followup-To: Doug White <dwhite@resnet.uoregon.edu>,
	hackers@FreeBSD.ORG
References: <19990915104350.G86648@relay.ucb.crimea.ua> <Pine.BSF.4.10.9909162320300.66443-100000@resnet.uoregon.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <Pine.BSF.4.10.9909162320300.66443-100000@resnet.uoregon.edu>; from Doug White on Thu, Sep 16, 1999 at 11:25:53PM -0700
X-Operating-System: FreeBSD 3.2-STABLE i386
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Sep 16, 1999 at 11:25:53PM -0700, Doug White wrote:
[...]
> An update:
> 
> I set up a test config at work with some spare boxes.  I found that if you
> specify an aliasIP that is the primary alias address (as determined by the
> -n or -a options), those redirections will be ignored.  Others continue to
> work.  I don't know why they weren't working on the real box, I may had
> made a mistake there.
> 
> So this file is wrong:
> 
> interface fxp0  
> redirect_port 10.0.0.1:ssh 128.1.1.1:ssh
> redirect_port 10.0.0.2:ssh 128.1.1.2:ssh
> 
> But this correct:
> 
> interface fxp0
> redirect_port 10.0.0.1:ssh ssh
> redirect_port 10.0.0.2:ssh 128.1.1.2:ssh
> 
> There is some logic in natd to handle the wrong case so that it is
> equivalent to the right case, but that logic may be flawed.
> 
You know, natd(8) is not guilty, this is a bug in libalias(3) :-(
I have made a patch for this and yet another bug and will send my
patch for review to Brian Somers and Eivind Eklund.

Please let me know if you would like to test these patches, and
THANK YOU VERY MUCH for digging this out, there was a cool hacking!


Cheers,
-- 
Ruslan Ermilov		Sysadmin and DBA of the
ru@ucb.crimea.ua	United Commercial Bank,
ru@FreeBSD.org		FreeBSD committer,
+380.652.247.647	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17  6:40:48 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126])
	by hub.freebsd.org (Postfix) with ESMTP id A774414CE5
	for <hackers@freebsd.org>; Fri, 17 Sep 1999 06:40:41 -0700 (PDT)
	(envelope-from roger@cs.strath.ac.uk)
Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10])
	by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id OAA23179
	Fri, 17 Sep 1999 14:40:39 +0100 (BST)
Message-ID: <37E244D7.31DF@cs.strath.ac.uk>
Date: Fri, 17 Sep 1999 14:40:39 +0100
From: Roger Hardiman <roger@cs.strath.ac.uk>
Organization: University of Strathclyde
X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha)
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: Moving bt848 driver to /sys/dev/bktr
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I want to move the Bt848 driver to /sys/dev/bktr

Here is why.....
The Bt848 driver (bktr) is contained in one file
(/sys/pci/brooktree848.c) and currently runs to about 7000 lines.


I've broken the driver down into 4 smaller files which cleanly
splits the functionality (tuner, audio, card probing, Bt848 programming)
With all the new .c and .h files, the new Bt848 driver consists
of about 9 files now instead of 1.

Rather than commit 8 new files to /sys/pci I would rather move
the whole lot to /sys/dev/bktr and keep them neatly in their
own directory (just like all the USB files are in one place)

Splitting the files up makes it easier to maintain, easier to
understand and easier to update.


So, does anyone see any problems with this?

Thanks
Roger
-- 
Roger Hardiman        | Telepresence Research Group
roger@cs.strath.ac.uk | DMEM, University of Strathclyde
tel: 0141 548 2897    | Glasgow, Scotland, G1 1XJ, UK
fax: 0141 552 0557    | http://telepresence.dmem.strath.ac.uk


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17  6:50:49 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 2735014BCC
	for <hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 06:50:45 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id PAA77267;
	Fri, 17 Sep 1999 15:50:36 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199909171350.PAA77267@freebsd.dk>
Subject: Re: Moving bt848 driver to /sys/dev/bktr
In-Reply-To: <37E244D7.31DF@cs.strath.ac.uk> from Roger Hardiman at "Sep 17, 1999 02:40:39 pm"
To: roger@cs.strath.ac.uk (Roger Hardiman)
Date: Fri, 17 Sep 1999 15:50:36 +0200 (CEST)
Cc: hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Roger Hardiman wrote:
> Hi,
> 
> I want to move the Bt848 driver to /sys/dev/bktr
> 
> So, does anyone see any problems with this?

Nope, go for it I'd say, and could we then have some of all the
version text and stuff put away too, thats why we have CVS :)

-Soren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17  7:52:33 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18])
	by hub.freebsd.org (Postfix) with ESMTP
	id E2F6715168; Fri, 17 Sep 1999 07:52:29 -0700 (PDT)
	(envelope-from zzhang@cs.binghamton.edu)
Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72])
	by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id KAA11222;
	Fri, 17 Sep 1999 10:52:29 -0400 (EDT)
Date: Fri, 17 Sep 1999 10:38:24 -0400 (EDT)
From: Zhihui Zhang <zzhang@cs.binghamton.edu>
To: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org
Subject: Multiple routes to the same destination
Message-ID: <Pine.GSO.3.96.990917103133.26160A-100000@sol.cs.binghamton.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


As said by the 4.4 BSD book (page 423), 4.4 BSD does not support multiple
routes to the same destination (identical key and mask). Does the radix
tree code in FreeBSD - 4.0 has the same limitation?  I am wondering if
there is already a solution for this? 

Any help is appreciated.

--------------------------------------------------
Zhihui Zhang.  Please visit http://www.freebsd.org
--------------------------------------------------



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17  9:32:11 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
	by hub.freebsd.org (Postfix) with ESMTP id C69B614E07
	for <hackers@FreeBSD.org>; Fri, 17 Sep 1999 09:32:07 -0700 (PDT)
	(envelope-from green@FreeBSD.org)
Received: from localhost (green@localhost)
	by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id MAA64502
	for <hackers@FreeBSD.org>; Fri, 17 Sep 1999 12:32:01 -0400 (EDT)
X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs
Date: Fri, 17 Sep 1999 12:32:01 -0400 (EDT)
From: "Brian F. Feldman" <green@FreeBSD.org>
X-Sender: green@janus.syracuse.net
To: hackers@FreeBSD.org
Subject: socket buffer DoS/administrative limits
Message-ID: <Pine.BSF.4.10.9909171158420.62333-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

   Yes folks, it's that time again: time for more administrative limits!
I've worked out a resource limit (for FreeBSD in this case, but not
non-portable) which allows prevention of DoS by mbuf starvation.  Others
are working on making the networking code more resilient, while this is
a general resource limit which can be used in any case.
   I've chosen the name "sbsize" (RLIMIT_SBSIZE) for this. Here's what
happens with the limit in action (note that the pdksh in use has been
patched to include the ulimit):

{"/home/green"}$ ulimit -b 2000000 ; ulimit -a | grep sbsize
sbsize(bytes)        2000000
{"/home/green"}$ ./testsockbuf
socketpair: No buffer space available
14 sockets had been allocated

   And another DoS attempt has been foiled with administrative limits :)
I'm sorry for not having something working sooner, but I ran into the problem
of my KASSERT() being tripped, which ended up being caused by me not
grokking an evil local define (look for "#define (snd|rcv) "...) correctly.
After fixing that, everything is wonderful.
   The patch, which applies to FreeBSD 4.0-CURRENT, and should be easily
portable or backportable, can be found at:

		http://www.FreeBSD.org/~green/sbsize4.patch

-- 
 Brian Fundakowski Feldman           \  FreeBSD: The Power to Serve!  /
 green@FreeBSD.org                    `------------------------------'




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 10:16: 3 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mushi.colo.neosoft.com (mushi.colo.neosoft.com [206.109.6.82])
	by hub.freebsd.org (Postfix) with SMTP id 23A6614FCA
	for <hackers@freebsd.org>; Fri, 17 Sep 1999 10:16:00 -0700 (PDT)
	(envelope-from peter@bonkers.taronga.com)
Received: (qmail 13485 invoked from network); 17 Sep 1999 17:15:59 -0000
Received: from bonkers.in.taronga.com (HELO bonkers.taronga.com) (10.0.0.1)
  by mushi.in.taronga.com with SMTP; 17 Sep 1999 17:15:59 -0000
Received: (from peter@localhost)
          by bonkers.taronga.com (8.9.1/8.9.1) id MAA24311
          for hackers@freebsd.org; Fri, 17 Sep 1999 12:15:58 -0500 (CDT)
          (envelope-from peter)
Date: Fri, 17 Sep 1999 12:15:58 -0500 (CDT)
From: Peter da Silva <peter@Taronga.COM>
Message-Id: <199909171715.MAA24311@bonkers.taronga.com>
To: hackers@freebsd.org
Subject: Minor numbers in shared libraries.
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In a discussion with Nate Williams, I have learned that the reason FreeBSD
doesn't use minor numbers with shared libraries because standard ELF doesn't
support it. Is this a hard-and-fast unbreakable rule, or is this something
that could be implemented if it can be done in a way that's compatible with
standard ELF?

It seems to me that there should be a way of working around this, by adding
a field (either in a new section or an unused field (properly flagged with a
magic number) in the header) to communicate the minor version number to ld.so,
and having ld.so modify its search path by looking for X.so.M.N (where N >=
the number in the header), before X.so.M. This shouldn't break any "foreign"
libraries, nor break libraries created under FreeBSD when used on "foreign"
systems.

Am I missing something really obvious here?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 11:11:11 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
	by hub.freebsd.org (Postfix) with ESMTP id 9FE35154CF
	for <FreeBSD-hackers@freebsd.org>; Fri, 17 Sep 1999 11:11:00 -0700 (PDT)
	(envelope-from wilko@yedi.iaf.nl)
Received: from yedi.iaf.nl (uucp@localhost)
	  by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA27496
	  for FreeBSD-hackers@freebsd.org; Fri, 17 Sep 1999 19:58:49 +0200 (MET DST)
Received: (from wilko@localhost)
	by yedi.iaf.nl (8.9.3/8.9.3) id UAA03411
	for FreeBSD-hackers@freebsd.org; Fri, 17 Sep 1999 20:00:53 +0200 (CEST)
	(envelope-from wilko)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199909171800.UAA03411@yedi.iaf.nl>
Subject:  looking for older (< V1.1) mtv
To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list)
Date: Fri, 17 Sep 1999 20:00:53 +0200 (CEST)
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As mtv 1.1 is producing unusable stuttering audio on 3.3-RC (I know,
I'll cvsup tonite..) I wonder if someone has an older version for
me to try.

W/
-- 
|   / o / /  _  	 Arnhem, The Netherlands	- Powered by FreeBSD -
|/|/ / / /( (_) Bulte 	 WWW  : http://www.tcja.nl 	http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 12: 7:15 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127])
	by hub.freebsd.org (Postfix) with ESMTP id 400961582E
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 12:05:25 -0700 (PDT)
	(envelope-from thorpej@lestat.nas.nasa.gov)
Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id MAA18944; Fri, 17 Sep 1999 12:05:20 -0700 (PDT)
Message-Id: <199909171905.MAA18944@lestat.nas.nasa.gov>
To: Mohit Aron <aron@cs.rice.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: TLB miss handler for alpha running FreeBSD-4.0 
Reply-To: Jason Thorpe <thorpej@nas.nasa.gov>
From: Jason Thorpe <thorpej@nas.nasa.gov>
Date: Fri, 17 Sep 1999 12:05:20 -0700
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 16 Sep 1999 23:10:21 -0500 (CDT) 
 Mohit Aron <aron@cs.rice.edu> wrote:

...well, I'm speaking from the NetBSD perspective, but it's the same
in FreeBSD, because both use the OSF/1 PALcode...

 > 	as I understand it, TLB misses on the alpha are handled by the 
 > software (as opposed to x86 where they are handled in hardware). Can someone

They're handled by software, but not the operating system software (at least
not under the OSF/1 PALcode).  TLB misses are serviced by the PALcode, which
presents a 3-level page table interface to the operating system.

 > help me with the FreeBSD code. I'm trying to locate the kernel code that
 > implements the TLB handler. I'd appreciate if someone can tell me how the 
 > control is given to the software (i.e. what trap is generated), how the
 > handler is called and finally how does the control return back. Thanks,

You should start by reading the `Alpha AXP Architecture Reference Manual',
which is in the Third Edition now, I believe.  It will describe to you
in detail the interface the operating system has to the processor.

        -- Jason R. Thorpe <thorpej@nas.nasa.gov>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 12:40:41 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from hermes.mixx.net (hermes.mixx.net [194.152.58.71])
	by hub.freebsd.org (Postfix) with ESMTP id F03EE14CD2
	for <hackers@FreeBSD.org>; Fri, 17 Sep 1999 12:40:35 -0700 (PDT)
	(envelope-from graichen@innominate.de)
Received: from innominate.de (gatekeeper.innominate.de [212.5.16.129])
	by hermes.mixx.net (8.9.3/8.9.3) with SMTP id VAA29282
	for <hackers@FreeBSD.org>; Fri, 17 Sep 1999 21:40:33 +0200
Received: (qmail 19901 invoked from network); 17 Sep 1999 19:40:30 -0000
Received: from cello.innominate.local (192.168.0.13)
  by lingo01.innominate.local with SMTP; 17 Sep 1999 19:40:30 -0000
Received: from localhost (graichen@localhost)
	by cello.innominate.local (8.9.3/8.9.3) with ESMTP id VAA02784
	for <hackers@FreeBSD.org>; Fri, 17 Sep 1999 21:40:26 +0200 (CEST)
	(envelope-from graichen@innominate.de)
X-Authentication-Warning: cello.innominate.local: graichen owned process doing -bs
Date: Fri, 17 Sep 1999 21:40:25 +0200 (CEST)
From: Thomas Graichen <graichen@innominate.de>
X-Sender: graichen@cello.innominate.local
To: hackers@FreeBSD.org
Subject: booting current with ata0 etc.
Message-ID: <Pine.BSF.4.10.9909172137240.2777-100000@cello.innominate.local>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

i've just upgraded one of my machines here at work to -current
and enabled the ata stuff - but after rebooting it says "cannot
mount root" - earlier then i tried this with -current it was
working fine and transparent (i.e. without anything to change
from wd0 to ad0) - so the question - did anything of this
change ? (btw. the machine is an old 486 with isa ide controller
and the disk and cdrom are found fine by the ata driver)

a lot of thanks in advance for any hint

t

-- 
graichen@innominate.de
                                                        innominate AG
                                                    networking people
fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 14:49:50 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31])
	by hub.freebsd.org (Postfix) with ESMTP id AA03614D40
	for <hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 14:49:42 -0700 (PDT)
	(envelope-from rivers@dignus.com)
Received: from dignus.com (ponds.vnet.net [166.82.177.48])
	by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id RAA13715;
	Fri, 17 Sep 1999 17:49:38 -0400 (EDT)
Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3])
	by dignus.com (8.9.2/8.8.5) with ESMTP id RAA80466;
	Fri, 17 Sep 1999 17:49:37 -0400 (EDT)
Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id RAA96311; Fri, 17 Sep 1999 17:49:37 -0400 (EDT)
Date: Fri, 17 Sep 1999 17:49:37 -0400 (EDT)
From: Thomas David Rivers <rivers@dignus.com>
Message-Id: <199909172149.RAA96311@lakes.dignus.com>
To: hackers@FreeBSD.ORG, peter@Taronga.COM
Subject: Re: Minor numbers in shared libraries.
In-Reply-To: <199909171715.MAA24311@bonkers.taronga.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> In a discussion with Nate Williams, I have learned that the reason FreeBSD
> doesn't use minor numbers with shared libraries because standard ELF doesn't
> support it. Is this a hard-and-fast unbreakable rule, or is this something
> that could be implemented if it can be done in a way that's compatible with
> standard ELF?
> 
> It seems to me that there should be a way of working around this, by adding
> a field (either in a new section or an unused field (properly flagged with a
> magic number) in the header) to communicate the minor version number to ld.so,
> and having ld.so modify its search path by looking for X.so.M.N (where N >=
> the number in the header), before X.so.M. This shouldn't break any "foreign"
> libraries, nor break libraries created under FreeBSD when used on "foreign"
> systems.
> 
> Am I missing something really obvious here?
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 

 I would also add that you can "fake" a minor number by simple
multiplication.  You have to assume how many digits you want
to allow in minor numbers.

 For example, if we assume a minor number has no more than 3
digits (allowing the minor numbers to grow to 999) then, 
M.N can readily be encoded as M*100+N.

 So, if M = 2 and N = 50, the Elf library number would be 2050.

 It doesn't look pretty when you do an ls.

 Also, you would want to "teach" the loaded about this.

 Just a thought - not really a suggestion - just a thought.

	- Dave Rivers -


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 16: 2:30 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mushi.colo.neosoft.com (mushi.colo.neosoft.com [206.109.6.82])
	by hub.freebsd.org (Postfix) with SMTP id 1D21814FCA
	for <hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 16:02:16 -0700 (PDT)
	(envelope-from peter@taronga.com)
Received: (qmail 8634 invoked from network); 17 Sep 1999 22:59:00 -0000
Received: from citadel.in.taronga.com (10.0.0.43)
  by mushi.in.taronga.com with SMTP; 17 Sep 1999 22:59:00 -0000
Received: by citadel.in.taronga.com (Postfix, from userid 100)
	id 887AF322E3; Fri, 17 Sep 1999 17:56:19 -0500 (CDT)
Subject: Re: Minor numbers in shared libraries.
In-Reply-To: <199909172149.RAA96311@lakes.dignus.com> from Thomas David Rivers at "Sep 17, 1999 05:49:37 pm"
To: rivers@dignus.com (Thomas David Rivers)
Date: Fri, 17 Sep 1999 17:56:19 -0500 (CDT)
Cc: hackers@FreeBSD.ORG, peter@Taronga.COM
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <19990917225619.887AF322E3@citadel.in.taronga.com>
From: peter@taronga.com (Peter da Silva)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>  I would also add that you can "fake" a minor number by simple
> multiplication.  You have to assume how many digits you want
> to allow in minor numbers.
> 
>  For example, if we assume a minor number has no more than 3
> digits (allowing the minor numbers to grow to 999) then, 
> M.N can readily be encoded as M*100+N.
> 
>  So, if M = 2 and N = 50, the Elf library number would be 2050.

250, I think you mean. This is good, but you would still need to modify
ld.so to know about this, so it'll load ld.so.208 (or version 2.8) when
you specified 204 (v 2.4), but won't load ld.so.301 (v 3.1).

>  It doesn't look pretty when you do an ls.

Since ld.so knows about it anyway, you could have it parse file names
appropriately, so the version number on the file itself can remain
dotted, with a symlink like X.so.2 -> X.so.2.8 to make things easier
for mere humans.

The problem is that this is less compatible with forign version numbers,
unless you had a patch program that applied the appropriate multiplicative
factor to the version number when you imported it.

How big is the version number field in elf anyway? If it's big enough, you
could just arbitrarily say something like "version numbers below 10000 are
treated literally, otherwise subtract 10000 and divide by 100 then take
the quotient and remainder as the major and minor numbers".



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 16:14: 4 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14])
	by hub.freebsd.org (Postfix) with ESMTP id 9668114FCA
	for <Freebsd-hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 16:13:55 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: from apollo.backplane.com ([209.157.86.2])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id QAA04293
	for <Freebsd-hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 16:12:35 -0700 (PDT)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id LAA46019;
	Thu, 16 Sep 1999 11:59:18 -0700 (PDT)
	(envelope-from dillon)
Date: Thu, 16 Sep 1999 11:59:18 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199909161859.LAA46019@apollo.backplane.com>
To: Gregory_D_Moncreaff@res.raytheon.com
Cc: Freebsd-hackers@FreeBSD.ORG
Subject: Re: boston globe article....
References:  <852567EE.005A71C3.00@ressud-as01.res.ray.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:
:http://www.boston.com/dailyglobe2/259/business/Even_better_than_Linux+.shtm
:l

    Neato!  But next time don't line-break the URL :-)

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 16:15:21 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14])
	by hub.freebsd.org (Postfix) with ESMTP id 8CA3615A14
	for <hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 16:15:07 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: from apollo.backplane.com ([209.157.86.2])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id QAA04451
	for <hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 16:12:40 -0700 (PDT)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id OAA25920;
	Mon, 13 Sep 1999 14:16:25 -0700 (PDT)
	(envelope-from dillon)
Date: Mon, 13 Sep 1999 14:16:25 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199909132116.OAA25920@apollo.backplane.com>
To: Tony Finch <fanf@demon.net>
Cc: hackers@FreeBSD.ORG
Subject: Re: mounting a partition more than once
References:  <E11QZ03-000DDr-00@fanf.noc.demon.net>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:Tony Finch <fanf@demon.net> wrote:
:
:Well, in the absence of any comments I hacked around a bit and ended
:up with the following patch (against 3.3-RC), which permits the same
:block device to be mounted read-only more than once. The motivation
:for this is to permit multiple chrooted environments to share the same
:/usr partition.
:
:Some things I wonder about this change is whether the mounts will share
:the same pages in the buffer cache, and whether the resource
:accounting is still right. I've subtly funted the meaning of
:v_specmountpoint when multiple mounts happen; does this matter?
:
:Tony.
:-- 
:f.a.n.finch    dot@dotat.at    fanf@demon.net    e pluribus unix

    Hmm... well, there is a problem here.  I believe this will allow
    you to open the underlying block device read-only as well as mount
    the filesystem read-only.  This will confuse the buffer cache badly.

    Also, this may not be the best place to put the code.  It make sense
    to be able to mount a block device multiple times in a read-only
    fashion, but the code should be in the open for the block device
    rather then in UFS/FFS, so it can be used with other filesystems
    and for other purposes.

					-Matt


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 16:15:22 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14])
	by hub.freebsd.org (Postfix) with ESMTP id 9DF3C15A72
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 16:15:12 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: from apollo.backplane.com ([209.157.86.2])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id QAA04461
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 16:12:40 -0700 (PDT)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id OAA25887;
	Mon, 13 Sep 1999 14:11:17 -0700 (PDT)
	(envelope-from dillon)
Date: Mon, 13 Sep 1999 14:11:17 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199909132111.OAA25887@apollo.backplane.com>
To: "David E. Cross" <crossd@cs.rpi.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: softupdates panic in 3.3-RC
References:  <199909131727.NAA67883@cs.rpi.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:Our ftp server crashed early this morning with what appears to be a softupdates
:error:
:
:> Sep 13 09:56:19 stumble /kernel: pid 41477 (perl), uid 0 on /exports/share3/ftp/.2: file system full
:> 
:> panic: softdep_write_inodeblock: indirect pointer #0 mismatch 0 != 15597568
:> syncing disks... panic: softdep_lock: locking against myself
:
:'perl' would have been the nightly mirror(1) run to sync up our ftp site.
:
:What additional details would be usefull?  We didn't have crashdumps enabled
:on this machine, so a backtrace is not fully possible, although it would seem
:the contextual evidence for what went wrong is strong.
:
:--
:David Cross                               | email: crossd@cs.rpi.edu 
:Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
:Rensselaer Polytechnic Institute,         | Ph: 518.276.2860            

    Softupdates has known bugs relating to filesystem full conditions which
    I believe Kirk is working on.  There isn't much you can do until then
    other then either disable softupdates or work to avoid the disk-full 
    condition.  The panic does not occur very frequently so working
    to avoid the disk-full condition is what I would recommend.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 16:15:34 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14])
	by hub.freebsd.org (Postfix) with ESMTP id DF80B15AEF
	for <hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 16:15:29 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: from apollo.backplane.com ([209.157.86.2])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id QAA04422
	for <hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 16:12:39 -0700 (PDT)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id WAA27333;
	Mon, 13 Sep 1999 22:04:15 -0700 (PDT)
	(envelope-from dillon)
Date: Mon, 13 Sep 1999 22:04:15 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199909140504.WAA27333@apollo.backplane.com>
To: Tony Finch <fanf@demon.net>
Cc: Tony Finch <fanf@demon.net>, hackers@FreeBSD.ORG
Subject: Re: mounting a partition more than once
References: <E11QZ03-000DDr-00@fanf.noc.demon.net>
	<199909132116.OAA25920@apollo.backplane.com> <E11Qe1j-000DRT-00@fanf.noc.demon.net>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:Matthew Dillon <dillon@apollo.backplane.com> wrote:
:> :Tony Finch <fanf@demon.net> wrote:
:...
:> 
:>     Hmm... well, there is a problem here.  I believe this will allow
:>     you to open the underlying block device read-only as well as mount
:>     the filesystem read-only.  This will confuse the buffer cache badly.
:
:I don't think so -- spec_open checks whether the block device has been
:mounted in order to prevent this, and I made sure that that check
:remains in force except when spec_open is called by ffs_mountfs (by
:adding the FMOUNTING flag). I assumed that the buffer cache will
:handle multiple read-only mounts because it handles multiple userland
:reading file descriptors.

    Ah, I see it now!

:>     Also, this may not be the best place to put the code.  It make sense
:>     to be able to mount a block device multiple times in a read-only
:>     fashion, but the code should be in the open for the block device
:>     rather then in UFS/FFS, so it can be used with other filesystems
:>     and for other purposes.
:
:Yes, it's evident that this is true because I had to hack around
:essentially the same test in both spec_open and ffs_mountfs; removing
:the checks down from ffs_mountfs so it relies on spec_mount to DTRT
:would be neater, I think.
:
:Tony.
:-- 
:f.a.n.finch    dot@dotat.at    fanf@demon.net    e pluribus unix

    Yes.  I think this is the right track to take.  The result will be
    more useful to the system and probably a cleaner patch as well.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 16:16:52 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3FDA415567; Fri, 17 Sep 1999 16:16:21 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: from apollo.backplane.com ([209.157.86.2])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id QAA04468;
	Fri, 17 Sep 1999 16:12:41 -0700 (PDT)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id NAA25509;
	Mon, 13 Sep 1999 13:17:56 -0700 (PDT)
	(envelope-from dillon)
Date: Mon, 13 Sep 1999 13:17:56 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199909132017.NAA25509@apollo.backplane.com>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc: Bosko Milekic <bmilekic@dsuper.net>,
	Stas Kisel <stas@sonet.crimea.ua>, avalon@coombs.anu.edu.au,
	freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG
Subject: Re: mbuf shortage situations (followup)
References: <199909091447.SAA24055@sonet.crimea.ua>
	<Pine.OSF.4.05.9909122304470.18795-300000@oracle.dsuper.net> <199909131840.OAA31048@khavrinen.lcs.mit.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:In 4.3, the code was able to deal with cluster allocation failing.  We
:have a somewhat different situation now, because many network
:interface devices have less-flexible DMA mechanisms which don't allow
:packet reception into non-contiguous buffers, so we need to have at
:least a certain number of clusters available for this purpose.
:
:-GAWollman
:
:--
:Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same

    This is an interrupt level mechanism.  The mbuf code is *already* allowed
    to (and does) return NULL in this case so I don't think it applies to
    the problem under discussion.

    The case that is causing the panics is with the non-interrupt mbuf
    allocation mechanism.  Specifically, the case where M_WAIT is used.

    The second problem under discussion, which really ought to be separated
    out from the mbuf panic problem, is the potential for a deadlock or 
    denial of service attack when the system is attacked in a manner that
    eats all available mbufs.
    
:wollman@lcs.mit.edu  | O Siem / The fires of freedom 
:Opinions not those of| Dance in the burning flame

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 16:17:16 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1880115B68; Fri, 17 Sep 1999 16:16:20 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: from apollo.backplane.com ([209.157.86.2])
	by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id QAA04542;
	Fri, 17 Sep 1999 16:12:46 -0700 (PDT)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id UAA20252;
	Sun, 12 Sep 1999 20:36:59 -0700 (PDT)
	(envelope-from dillon)
Date: Sun, 12 Sep 1999 20:36:59 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199909130336.UAA20252@apollo.backplane.com>
To: Bosko Milekic <bmilekic@dsuper.net>
Cc: Stas Kisel <stas@sonet.crimea.ua>, avalon@coombs.anu.edu.au,
	freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG
Subject: Re: mbuf shortage situations (followup)
References:  <Pine.OSF.4.05.9909122304470.18795-300000@oracle.dsuper.net>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

    I think that what needs to be done is to split the problem in two.  First,
    allow the mbuf routines to return a failure even with M_WAIT.  If M_WAIT
    is used, it simply means 'try harder, sleeping a bit if necessary'.  This 
    requires ensuring that all the networking code deal with the failure
    case - a time consuming but straightforward task.  If a failure occurs,
    one simply drops the packet, not the connection or anything else drastic.
    just the packet.

    The second problem that needs to be addressed is resource exhaustion.
    For example, allocating thousands of connections and socket-opting their
    buffers as large as possible, or programs such as syslog accepting new
    connections ad-infinitum.  This is a harder problem to fix properly,
    but a lot of the various issues such as those with syslog can be dealt 
    with in userland rather then the kernel.

						-Matt



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 19:59:59 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
	by hub.freebsd.org (Postfix) with ESMTP
	id 592DA14E6C; Fri, 17 Sep 1999 19:59:48 -0700 (PDT)
	(envelope-from green@FreeBSD.org)
Received: from localhost (green@localhost)
	by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id WAA83493;
	Fri, 17 Sep 1999 22:58:30 -0400 (EDT)
X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs
Date: Fri, 17 Sep 1999 22:58:30 -0400 (EDT)
From: "Brian F. Feldman" <green@FreeBSD.org>
X-Sender: green@janus.syracuse.net
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>,
	Bosko Milekic <bmilekic@dsuper.net>,
	Stas Kisel <stas@sonet.crimea.ua>, avalon@coombs.anu.edu.au,
	freebsd-hackers@FreeBSD.org, freebsd-security@FreeBSD.org
Subject: Re: mbuf shortage situations (followup)
In-Reply-To: <199909132017.NAA25509@apollo.backplane.com>
Message-ID: <Pine.BSF.4.10.9909172256200.82747-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 13 Sep 1999, Matthew Dillon wrote:

>     The case that is causing the panics is with the non-interrupt mbuf
>     allocation mechanism.  Specifically, the case where M_WAIT is used.
> 
>     The second problem under discussion, which really ought to be separated
>     out from the mbuf panic problem, is the potential for a deadlock or 
>     denial of service attack when the system is attacked in a manner that
>     eats all available mbufs.
>     

The traditional way to prevent resource-starvation DoSes from the user
populus has been to add administrative limits.  Using RLIMIT_SBSIZE does
this nicely.  Yes, this isn't actually fixing the panics, but it is
good preventative medicine.

> 					-Matt
> 					Matthew Dillon 
> 					<dillon@backplane.com>
> 

-- 
 Brian Fundakowski Feldman           \  FreeBSD: The Power to Serve!  /
 green@FreeBSD.org                    `------------------------------'



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 22: 9:29 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from hermes.mixx.net (hermes.mixx.net [194.152.58.71])
	by hub.freebsd.org (Postfix) with ESMTP id E72EB14CEB
	for <hackers@FreeBSD.org>; Fri, 17 Sep 1999 22:09:22 -0700 (PDT)
	(envelope-from graichen@innominate.de)
Received: from innominate.de (gatekeeper.innominate.de [212.5.16.129])
	by hermes.mixx.net (8.9.3/8.9.3) with SMTP id HAA18816
	for <hackers@FreeBSD.org>; Sat, 18 Sep 1999 07:09:20 +0200
Received: (qmail 14163 invoked from network); 18 Sep 1999 05:09:20 -0000
Received: from cello.innominate.local (192.168.0.13)
  by lingo01.innominate.local with SMTP; 18 Sep 1999 05:09:20 -0000
Received: from localhost (graichen@localhost)
	by cello.innominate.local (8.9.3/8.9.3) with ESMTP id HAA06149
	for <hackers@FreeBSD.org>; Sat, 18 Sep 1999 07:09:19 +0200 (CEST)
	(envelope-from graichen@innominate.de)
X-Authentication-Warning: cello.innominate.local: graichen owned process doing -bs
Date: Sat, 18 Sep 1999 07:09:19 +0200 (CEST)
From: Thomas Graichen <graichen@innominate.de>
X-Sender: graichen@cello.innominate.local
To: hackers@FreeBSD.org
Subject: mysterious FreeBSD hardware problems
Message-ID: <Pine.BSF.4.10.9909180707280.6145-100000@cello.innominate.local>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

(sorry if this appears here twice - but as far as i can see the first
try didn't make it here due to non optimal configuration of my news
to mailinglist gateway :-)

i'm a bit at the end of my phantasie with this machine i'm writing
this here on ... something mystically seems to be broken with
running FreeBSD on it ... first mystical thing is that the moused
takes about a minute to start but workes then fine ... ok after
that it boots on into x and works - but everything is very slow
somehow as if the machine is under heavy load - but it isn't - one
other thing noticable is that it produces very high rates of
interupts on the serial ports with the mouse sometimes ... ok - and
in addition to all this it won't reboot - if i try to reboot it
via reboot/halt/shutdown - it starts to kill processes and nothing
more happens - but via ctrl-alt-del or an "kill -INT 1" which that
does it reboots fine ... has anyone ever seen this on any machine
or any idea where this might come from ? - some more details: the
machine runs fine with linux - also i've had another machine
(different board) with exacly the same symptoms and there turning
on apm in the bios and in the kernel fixed the problems all together
but on this board i can't turn on apm - because it does not detect
the amd cpu and i think thus refuses to turn on apm (it prints apm
disabled at bootup even if i set it to enabled in the bios) - i
would really like to see FreeBSD running completely on this machine

here are some more details - first a "boot -v" output and second
a ktrace of the hanging "halt" ...

Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
	The Regents of the University of California. All rights reserved.
FreeBSD 3.2-RELEASE #1: Mon Sep 13 05:43:35 CEST 1999
    root@battus.at.home:/usr/src/sys/compile/BATTUS
Calibrating clock(s) ... TSC clock: 74378519 Hz, i8254 clock: 1193729 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254"  frequency 1193182 Hz
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
Timecounter "TSC"  frequency 74345070 Hz
CPU: AMD K5 model 0 (74.35-MHz 586-class CPU)
  Origin = "AuthenticAMD"  Id = 0x500  Stepping=0
  Features=0x3bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC>
real memory  = 41943040 (40960K bytes)
Physical memory chunk(s):
0x00001000 - 0x0009ffff, 651264 bytes (159 pages)
0x0027d000 - 0x027fdfff, 39325696 bytes (9601 pages)
avail memory = 38395904 (37496K bytes)
Found BIOS32 Service Directory header at 0xc00f6f10
Entry = 0xf6f20 (0xc00f6f20)  Rev = 0  Len = 1
PCI BIOS entry at 0x6f41
Other BIOS signatures found:
ACPI: 00000000
$PnP: 000f9500
Preloaded elf kernel "kernel" at 0xc0270000.
Preloaded elf module "if_tun.ko" at 0xc027009c.
pci_open(1):	mode 1 addr port (0x0cf8) is 0x8000384c
pci_open(1a):	mode1res=0x80000000 (0x80000000)
pci_cfgcheck:	device 0 [class=060000] [hdr=00] is there (id=122d8086)
Probing for devices on PCI bus 0:
found->	vendor=0x8086, dev=0x122d, revid=0x01
	class=06-00-00, hdrtype=0x00, mfdev=0
	subordinatebus=0 	secondarybus=0
chip0: <Intel 82437FX PCI cache memory controller> rev 0x01 on pci0.0.0
	CPU Inactivity timer:  clocks
	Peer Concurrency: enabled
	CPU-to-PCI Write Bursting: enabled
	PCI Streaming: enabled
	Bus Concurrency: enabled
	Cache: 256K pipelined-burst secondary; L1 enabled
	DRAM: no memory hole, 50 MHz refresh
	Read burst timing: x-2-2-2/x-3-3-3
	Write burst timing: x-3-3-3
	RAS-CAS delay: 2 clocks
found->	vendor=0x8086, dev=0x122e, revid=0x02
	class=06-01-00, hdrtype=0x00, mfdev=1
	subordinatebus=0 	secondarybus=0
chip1: <Intel 82371FB PCI to ISA bridge> rev 0x02 on pci0.7.0
	I/O Recovery Timing: 8-bit 8 clocks, 16-bit 4 clocks
	Extended BIOS: disabled
	Lower BIOS: disabled
	Coprocessor IRQ13: enabled
	Mouse IRQ12: disabled
	Interrupt Routing: A: disabled, B: IRQ12, C: disabled, D: disabled
		MB0: disabled, MB1: disabled
found->	vendor=0x8086, dev=0x1230, revid=0x02
	class=01-01-80, hdrtype=0x00, mfdev=0
	subordinatebus=0 	secondarybus=0
	map[0]: type 4, range 32, base 00008000, size  4
ide_pci0: <Intel PIIX Bus-master IDE controller> rev 0x02 on pci0.7.1
intel_piix_status: primary master/slave sample = 3, master/slave recovery = 2
intel_piix_status: primary master fastDMAonly disabled, pre/post enabled,
intel_piix_status:  IORDY sampling enabled,
intel_piix_status:  fast PIO enabled
intel_piix_status: primary master/slave sample = 3, master/slave recovery = 2
intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled,
intel_piix_status:  IORDY sampling disabled,
intel_piix_status:  fast PIO disabled
ide_pci: busmaster 0 status: 04 from port: 00008002
intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4
intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled,
intel_piix_status:  IORDY sampling disabled,
intel_piix_status:  fast PIO disabled
intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4
intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled,
intel_piix_status:  IORDY sampling disabled,
intel_piix_status:  fast PIO disabled
ide_pci: busmaster 1 status: 04 from port: 0000800a
found->	vendor=0x5333, dev=0x8811, revid=0x00
	class=03-00-00, hdrtype=0x00, mfdev=0
	subordinatebus=0 	secondarybus=0
	intpin=a, irq=12
	map[0]: type 1, range 32, base ff000000, size 23
vga0: <S3 Trio graphics accelerator> rev 0x00 int a irq 12 on pci0.19.0
Initializing PnP override table
Probing for PnP devices:
Trying Read_Port at 203
Trying Read_Port at 243
Trying Read_Port at 283
Trying Read_Port at 2c3
Trying Read_Port at 303
Trying Read_Port at 343
Trying Read_Port at 383
Trying Read_Port at 3c3
No Plug-n-Play devices were found
Probing for devices on the ISA bus:
atkbd: the current kbd controller command byte 0045
atkbd: keyboard ID 0x41ab (2)
kbdc: RESET_KBD return code:00fa
kbdc: RESET_KBD status:00aa
sc0 on isa
sc0: fb0 kbd0
sc0: VGA color <12 virtual consoles, flags=0x0>
ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 16384 on isa
ed0: address 00:00:c0:12:fa:ae, type SMC8216/SMC8216C (16 bit) 
bpf: ed0 attached
npx0 on motherboard
npx0: INT 16 interface
i586_bzero() bandwidth = 9782438 bytes/sec
bzero() bandwidth = 32901230 bytes/sec
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
fb0: vga0, vga, type:VGA (5), flags:0x7007f
fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000
fb0: init mode:24, bios mode:3, current mode:24
fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k
VGA parameters upon power-up
50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 
bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
VGA parameters in BIOS for mode 24
50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
EGA/VGA parameters to be used for mode 24
50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000
sio0: irq maps: 0x1 0x11 0x1 0x1
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1: irq maps: 0x1 0x9 0x1 0x1
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
mss0 at 0x530 irq 11 drq 1 on isa
snd0: <MS Sound System0 (AD1845)> 
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa
wdc0: unit 0 (wd0): <FUJITSU MPB3021ATU>, 32-bit, multi-block-16
wd0: 2062MB (4224150 sectors), 4470 cyls, 15 heads, 63 S/T, 512 B/S
wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007
wdc1 at 0x170-0x177 irq 15 flags 0x80ff80ff on isa
wdc1: unit 0 (atapi): <LTN204/KL43>, removable, intr, dma, iordis
acd0: drive speed 3617KB/sec, 120KB cache
acd0: supported read types: CD-DA
acd0: Audio: play, 255 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: no/blank disc inside, unlocked
ppc: parallel port found at 0x378
ppc0: SPP
ppc0 at 0x378 irq 7 on isa
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppi0: <generic parallel i/o> on ppbus 0
vpo0: can't connect to the drive
imm0: (disconnect) s1=0x38 s2=0x38, s3=0x38
imm0: (connect) s1=0x38 s2=0x38, s3=0x38
imm0: can't connect to the drive
imasks: bio c008c040, tty c003081a, net c0060480
BIOS Geometries:
 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors
 0 accounted for
Device configuration finished.
bpf: lo0 attached
Considering FFS root f/s.
changing root device to wd0s1a
wd0s1: type 0xa5, start 63, end = 4217471, size 4217409 : OK
ffs_mountfs: superblock updated for soft updates


   500 halt     GIO   fd 3 wrote 44 bytes
       "~\0\0\0\0\0\0\0shutdown\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
	\0Y\M^N\M-b7"
   500 halt     RET   write 44/0x2c
   500 halt     CALL  close(0x3)
   500 halt     RET   close 0
   500 halt     CALL  sync
   500 halt     RET   sync 0
   500 halt     CALL  kill(0x1,0x12)
   500 halt     RET   kill 0
   500 halt     CALL  sigaction(0x1,0xbfbfdbf8,0xbfbfdbec)
   500 halt     RET   sigaction 0
   500 halt     CALL  kill(0xffffffff,0xf)
   500 halt     RET   kill 0
   500 halt     CALL  nanosleep(0xbfbfdc00,0xbfbfdbf8)
   500 halt     PSIG  SIGINT SIG_DFL

... and here it does nothing more - i can interrupt the halt simply by
ctrl-c and i'm back at the console ...

does anyone have any idea what it might be or what i can do to find it
out - any help is really apreciated ...

a lot of thanks in advance

t

-- 
graichen@innominate.de
                                                        innominate AG
                                                    networking people
fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Fri Sep 17 23:56:48 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mg136-146.ricochet.net (mg136-146.ricochet.net [204.179.136.146])
	by hub.freebsd.org (Postfix) with ESMTP id EFAE015552
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 17 Sep 1999 23:56:17 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by hydrogen.fircrest.net (8.9.1/8.8.7) id AAA03922;
          Fri, 17 Sep 1999 00:21:30 -0700 (PDT)
Message-ID: <19990917002124.23278@hydrogen.fircrest.net>
Date: Fri, 17 Sep 1999 00:21:24 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Julian Elischer <julian@whistle.com>
Cc: Robert Sexton <robert@kudra.com>, Alex Le Heux <alexlh@funk.org>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: Superblock.
References: <19990910102612.C31537@tabby.kudra.com> <Pine.BSF.4.05.9909100950060.1186-100000@home.elischer.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <Pine.BSF.4.05.9909100950060.1186-100000@home.elischer.org>; from Julian Elischer on Fri, Sep 10, 1999 at 09:51:50AM -0700
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Julian Elischer scribbled this message on Sep 10:
> At least one person has already written this program...
> 
> THeey have mentionned this  in the hackers list so maybe a search of the
> list may turn something up..
> withing th last 2 years from memory.

actually, it should be part of my ffsrecov program that I wrote... I'm
not sure how well it works, but it should do what most people want to
find the super block...

> On Fri, 10 Sep 1999, Robert Sexton wrote:
> 
> > On Fri, Sep 10, 1999 at 10:26:26AM +0200, Alex Le Heux wrote:
> > > Hi,
> > > 
> > > I once had a similar situation: I had wiped my disklabel.
> > 
> > <Useful help deleted>
> > 
> > I know its easy to suggest somebody else do things, but turning this
> > into software might make for a very handy salvage tool, without a lot
> > of work for the author.  We seem to have folks popping up often
> > looking for little projects.  
> > 
> > I wonder how many folks have toasted drives in a recoverable way and
> > not bothered to ask for help....

[why can't people learn to delete sig's?]

-- 
  John-Mark Gurney				Voice: +1 541 684 8449
  Cu Networking					  P.O. Box 5693, 97405

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18  6:32:54 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3])
	by hub.freebsd.org (Postfix) with ESMTP id 68A4614EE6
	for <freebsd-hackers@freebsd.org>; Sat, 18 Sep 1999 06:32:41 -0700 (PDT)
	(envelope-from bigeye.rhein-neckar.de!naddy@mips.rhein-neckar.de)
Received: from mips.rhein-neckar.de (uucp@localhost)
	by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id PAA26891
	for freebsd-hackers@freebsd.org; Sat, 18 Sep 1999 15:32:40 +0200 (CEST)
	(envelope-from bigeye.rhein-neckar.de!naddy@mips.rhein-neckar.de)
Received: by mips.rhein-neckar.de
	id m11SIw7-000WyWC
	(Debian Smail-3.2.0.101 1997-Dec-17 #2); Sat, 18 Sep 1999 13:45:47 +0200 (CEST)
From: naddy@mips.rhein-neckar.de (Christian Weisgerber)
Subject: PAPERSIZE in /etc/make.conf?
Date: 18 Sep 1999 13:45:29 +0200
Message-ID: <7rvu0p$1lfr$1@bigeye.rhein-neckar.de>
To: freebsd-hackers@freebsd.org
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Should we have a PAPERSIZE variable (A4 vs. letter) in /etc/make.conf?

- groff has the paper size set as compile time option.

- Various ports that now exist in two versions or require the
  user to define the paper size at build time could automatically
  pull the value in.

-- 
Christian "naddy" Weisgerber                  naddy@mips.rhein-neckar.de



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18  6:50:57 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp.dti.ne.jp (smtp.dti.ne.jp [210.170.128.120])
	by hub.freebsd.org (Postfix) with ESMTP id 2FEA314DB0
	for <hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 06:50:54 -0700 (PDT)
	(envelope-from shigio@tamacom.com)
Received: from choota.signet.or.jp (PPP44.tama-ap5.dti.ne.jp [210.170.192.44]) by smtp.dti.ne.jp (8.9.0/3.7W) with ESMTP id WAA09976; Sat, 18 Sep 1999 22:50:49 +0900 (JST)
Received: from choota.signet.or.jp (localhost [127.0.0.1]) by choota.signet.or.jp (8.8.8/) with ESMTP id WAA02472; Sat, 18 Sep 1999 22:48:19 +0900 (JST)
Message-Id: <199909181348.WAA02472@tamacom.com>
To: hackers@FreeBSD.ORG
Cc: shigio@tamacom.com
Subject: GNU GLOBAL
Date: Sat, 18 Sep 1999 22:48:19 +0900
From: Shigio Yamaguchi <shigio@tamacom.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm the author of GLOBAL source code tag system.

I have decided to release next version of GLOBAL as a GNU software.
It means that it will be released under GPL instead of BSD license.

This decision was made by practical reason, not by doctrine reason.
It is advantageous for GLOBAL, because

o GNU softwares are distributed to widespread environments.
o The developers of GNU software pay some attention to making the program
  work well with the rest of GNU software.

That makes it easy for GLOBAL to reach the goal, that is, becoming
a common source code tag system in various environments.

Since FreeBSD already includes GNU softwares, it seems no problem.
GLOBAL itself will be as it be.

I'm concerned about whether or not FreeBSD community accept GNU GLOBAL.
I hope you not to reject it, because the rejection splits GLOBAL and it
makes it hard for GLOBAL to be a common source code tag system.

By the way, I have released GLOBAL-3.53 today. <http://www.tamacom.com/unix/>
It supports C++, XEmacs and WIN32 and includes improved gtags.el.
(Of course, it's BSD licensed).

Thank you.
--
Shigio Yamaguchi - Tama Communications Corporation
Mail: shigio@tamacom.com, WWW: http://www.tamacom.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18  7: 9:37 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142])
	by hub.freebsd.org (Postfix) with ESMTP id 7254814D1C
	for <freebsd-hackers@freebsd.org>; Sat, 18 Sep 1999 07:09:31 -0700 (PDT)
	(envelope-from mike@laurasia.com.au)
Received: (from mike@localhost)
	by laurasia.com.au (8.9.3/8.9.3) id WAA22184;
	Sat, 18 Sep 1999 22:09:17 +0800 (WST)
	(envelope-from mike)
From: Michael Kennett <mike@laurasia.com.au>
Message-Id: <199909181409.WAA22184@laurasia.com.au>
Subject: Re: GNU GLOBAL
In-Reply-To: <199909181348.WAA02472@tamacom.com> from Shigio Yamaguchi at "Sep 18, 1999 10:48:19 pm"
To: shigio@tamacom.com (Shigio Yamaguchi)
Date: Sat, 18 Sep 1999 22:09:17 +0800 (WST)
Cc: freebsd-hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi Shigio,

As the owner/author of a piece of software, you can distribute the source
code under any license that you like (GNU/BSD/Artistic etc...). Indeed, there
is no reason to choose just a single license under which you distribute your
code -- it should be possible for you to distribute the code under *both*
the GPL and the BSD licenses.

E.g. you could distribute a BSD version of GLOBAL-3.53 at the same time that
you distribute a GNU License version of GLOBAL-3.53.

If you want to assign copyright to the Free Software Foundation (so that
global becomes gnu-global?), I think you will lose the right to distribute
later versions under the BSD license. Whether this is what you want or not
is only for you to decide!

Best of Luck,

Mike Kennett.

Usual Disclaimer: I'm not a legal expert, and the above represents my
opinion only.

Potential Flamebait (:-)) [[Feel free to ignore this comment]]
Does the license really matter? Surely the important consideration is quality
of the code?

> I'm the author of GLOBAL source code tag system.
> 
> I have decided to release next version of GLOBAL as a GNU software.
> It means that it will be released under GPL instead of BSD license.
> 
> This decision was made by practical reason, not by doctrine reason.
> It is advantageous for GLOBAL, because
> 
> o GNU softwares are distributed to widespread environments.
> o The developers of GNU software pay some attention to making the program
>   work well with the rest of GNU software.
> 
> That makes it easy for GLOBAL to reach the goal, that is, becoming
> a common source code tag system in various environments.
> 
> Since FreeBSD already includes GNU softwares, it seems no problem.
> GLOBAL itself will be as it be.
> 
> I'm concerned about whether or not FreeBSD community accept GNU GLOBAL.
> I hope you not to reject it, because the rejection splits GLOBAL and it
> makes it hard for GLOBAL to be a common source code tag system.
> 
> By the way, I have released GLOBAL-3.53 today. <http://www.tamacom.com/unix/>
> It supports C++, XEmacs and WIN32 and includes improved gtags.el.
> (Of course, it's BSD licensed).
> 
> Thank you.
> --
> Shigio Yamaguchi - Tama Communications Corporation
> Mail: shigio@tamacom.com, WWW: http://www.tamacom.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 10:24:53 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
	by hub.freebsd.org (Postfix) with ESMTP id 0741C14D3B
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 10:24:42 -0700 (PDT)
	(envelope-from wilko@yedi.iaf.nl)
Received: from yedi.iaf.nl (uucp@localhost)
	  by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA11079;
	  Sat, 18 Sep 1999 19:14:41 +0200 (MET DST)
Received: (from wilko@localhost)
	by yedi.iaf.nl (8.9.3/8.9.3) id RAA04290;
	Sat, 18 Sep 1999 17:49:57 +0200 (CEST)
	(envelope-from wilko)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199909181549.RAA04290@yedi.iaf.nl>
Subject: Re: PAPERSIZE in /etc/make.conf?
In-Reply-To: <7rvu0p$1lfr$1@bigeye.rhein-neckar.de> from Christian Weisgerber at "Sep 18, 1999  1:45:29 pm"
To: naddy@mips.rhein-neckar.de (Christian Weisgerber)
Date: Sat, 18 Sep 1999 17:49:57 +0200 (CEST)
Cc: freebsd-hackers@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As Christian Weisgerber wrote ...

Sounds like a good idea, But I'd say it would be even better if it where
part of /etc/profile (or something similar) so that it can be picked
up from a reliable place at runtime.

This would obfuscate the need for different compiled products. 

Wilko

> Should we have a PAPERSIZE variable (A4 vs. letter) in /etc/make.conf?
> 
> - groff has the paper size set as compile time option.
> 
> - Various ports that now exist in two versions or require the
>   user to define the paper size at build time could automatically
>   pull the value in.

-- 
|   / o / /  _  	 Arnhem, The Netherlands	- Powered by FreeBSD -
|/|/ / / /( (_) Bulte 	 WWW  : http://www.tcja.nl 	http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 10:46: 0 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail2.atl.bellsouth.net (mail2.atl.bellsouth.net [205.152.0.22])
	by hub.freebsd.org (Postfix) with ESMTP id 106D414E6F
	for <freebsd-hackers@freebsd.org>; Sat, 18 Sep 1999 10:45:46 -0700 (PDT)
	(envelope-from wghicks@bellsouth.net)
Received: from wghicks.bellsouth.net (host-216-78-101-3.asm.bellsouth.net [216.78.101.3])
	by mail2.atl.bellsouth.net (8.9.3/8.9.3) with ESMTP id NAA15438;
	Sat, 18 Sep 1999 13:45:44 -0400 (EDT)
Received: from wghicks.bellsouth.net (wghicks@localhost [127.0.0.1])
	by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id NAA03329;
	Sat, 18 Sep 1999 13:50:31 -0400 (EDT)
	(envelope-from wghicks@wghicks.bellsouth.net)
Message-Id: <199909181750.NAA03329@bellsouth.net>
To: Shigio Yamaguchi <shigio@tamacom.com>
Cc: freebsd-hackers@freebsd.org
Subject: Re: GNU GLOBAL 
In-reply-to: Your message of "Sat, 18 Sep 1999 22:48:19 +0900."
             <199909181348.WAA02472@tamacom.com> 
Date: Sat, 18 Sep 1999 13:50:31 -0400
From: W Gerald Hicks <wghicks@bellsouth.net>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I don't see much of a problem, other than requiring its removal
from the FreeBSD source tree.  Although FreeBSD has a 'contrib'
and 'gnu' hierarchy in the source tree, I believe the trend
should be to reduce the existing members there and also to avoid
adding new ones.

imho, global (a fine software package) shouldn't have been in the
OS source tree anyway.  To me, the proper place seems to be in the
ports collection along with many other development utilities.

I don't agree with your perceptions of the GNU license but do
respect your decision as the author to choose whatever license
you wish.

I'll be preparing a port for global this afternoon and submitting
a change request to have it removed from the source tree in favor
of using the port on FreeBSD.

Thank you very much for global!  :-)

Cheers,

Jerry Hicks
wghicks@bellsouth.net


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 11: 0:34 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mg-20425426-100.ricochet.net (mg-20425426-100.ricochet.net [204.254.26.100])
	by hub.freebsd.org (Postfix) with ESMTP id 039E01500C
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 11:00:26 -0700 (PDT)
	(envelope-from gurney_j@efn.org)
Received: (from jmg@localhost)
          by mg-20425426-100.ricochet.net (8.9.1/8.8.7) id KAA04370;
          Sat, 18 Sep 1999 10:59:13 -0700 (PDT)
Message-ID: <19990918105837.36361@hydrogen.fircrest.net>
Date: Sat, 18 Sep 1999 10:58:37 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Christopher Sedore <cmsedore@mailbox.syr.edu>
Cc: Wes Peters <wes@softweyr.com>, Ruslan Ermilov <ru@ucb.crimea.ua>,
	Jayson Nordwick <nordwick@scam.xcf.berkeley.edu>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: kern/13075 (was: Re: aio_*)
References: <37E13D66.AB9889B8@softweyr.com> <Pine.SOL.4.10.9909161501270.1425-100000@rodan.syr.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <Pine.SOL.4.10.9909161501270.1425-100000@rodan.syr.edu>; from Christopher Sedore on Thu, Sep 16, 1999 at 03:03:21PM -0400
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 3.0-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31  96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Christopher Sedore scribbled this message on Sep 16:
> > Great, now do you want to tackle aio_cancel?  ;^)
> 
> I've been holding off to see whether I can get the other aio patches for
> improved socket io committed.  I don't want to do two versions of
> aio_cancel (the changes for sockets alter the way things are queued and
> hence the way that cancels have to be done).

sorry for the long delay, I've just completed a move down to San Jose,
and I still need a bit more work to get my test box up and running (it
panics just after booting kernel.GENERIC in process 1(swapper), but once
I do, I plan on testing and committing his changes...

-- 
  John-Mark Gurney				Voice: +1 408 975 9651
  Cu Networking					  

  "The soul contains in itself the event that shall presently befall it.
  The event is only the actualizing of its thought." -- Ralph Waldo Emerson


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 11:48:13 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.rp-plus.de (clubserv.rp-online.de [149.221.232.11])
	by hub.freebsd.org (Postfix) with ESMTP id 5BD5314D3B
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 11:47:17 -0700 (PDT)
	(envelope-from alex@cichlids.com)
Received: from neutron.cichlids.com (as8-pri5.rp-plus.de [149.221.239.133])
	by mail.rp-plus.de (8.9.1a/8.9.1) with ESMTP id UAA11184;
	Sat, 18 Sep 1999 20:47:17 +0200 (METDST)
Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10])
	by neutron.cichlids.com (8.9.3/8.9.1) with ESMTP id UAA63292;
	Sat, 18 Sep 1999 20:47:48 +0200 (CEST)
Received: (from alex@localhost)
	by cichlids.cichlids.com (8.9.3/8.9.3) id UAA61977;
	Sat, 18 Sep 1999 20:49:02 +0200 (CEST)
	(envelope-from alex)
From: Alexander Langer <alex@cichlids.com>
Date: Sat, 18 Sep 1999 20:49:02 +0200
To: Wilko Bulte <wilko@yedi.iaf.nl>
Cc: Christian Weisgerber <naddy@mips.rhein-neckar.de>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: PAPERSIZE in /etc/make.conf?
Message-ID: <19990918204902.A54837@cichlids.cichlids.com>
References: <7rvu0p$1lfr$1@bigeye.rhein-neckar.de> <199909181549.RAA04290@yedi.iaf.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <199909181549.RAA04290@yedi.iaf.nl>
X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8  A8 E3 BA F3 4E 60 7D 7F
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thus spake Wilko Bulte (wilko@yedi.iaf.nl):

Read again.

> part of /etc/profile (or something similar) so that it can be picked
> up from a reliable place at runtime.

> > - groff has the paper size set as compile time option.

Alex

-- 
I doubt, therefore I might be. 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 11:59:55 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id DE3BC14EE8
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 11:59:52 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA27334; Sun, 19 Sep 1999 03:59:47 +0900 (JST)
Message-ID: <37E3C6E4.90306F8@newsguy.com>
Date: Sun, 19 Sep 1999 02:07:48 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Keith Stevenson <k.stevenson@louisville.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: cache-friendly scheduling for SMP
References: <199909161225.MAA14962@jules.res.cmu.edu> <19990916143724.F17119@homer.louisville.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Keith Stevenson wrote:
> 
> IBM just released a new version of AIX (4.3.3).  One of the big features is
> CPU affinity in order to made better use of the CPU caches.  They claim to
> have done this be having a separate run queue for each CPU.

? Are they recycling marketing statements now? They have had cpu
affinity for ever!

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	"Thus, over the years my wife and I have physically diverged. While
I have zoomed toward a crusty middle-age, she has instead clung
doggedly to the sweet bloom of youth. Naturally I think this unfair.
Yet, if it was the other way around, I confess I wouldn't be happy
either."




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 12:25:55 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from www.crb-web.com (ns1.crb-web.com [209.70.120.131])
	by hub.freebsd.org (Postfix) with SMTP id 9825814DBA
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 12:25:52 -0700 (PDT)
	(envelope-from wayne@crb.crb-web.com)
Received: (qmail 22482 invoked by uid 1001); 18 Sep 1999 19:29:08 -0000
Date: Sat, 18 Sep 1999 15:29:08 -0400 (EDT)
From: Wayne Cuddy <wayne@crb-web.com>
Reply-To: wayne@crb-web.com
To: FreeBSD Hackers List <freebsd-hackers@FreeBSD.ORG>
Subject: what is devfs?
Message-ID: <Pine.LNX.4.10.9909181421550.22037-100000@crb.crb-web.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In the examples device drivers I see the inclusion of devfsext.h.  I read the
README in the devfs directory but I am still a little unsure what devfs would
be used for.  Can anyone give me some examples here.  Is there any more
information pertaining to devfs?

Thanks in advance,
Wayne 




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 13:42:36 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP id 08D1314A14
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 13:42:33 -0700 (PDT)
	(envelope-from julian@whistle.com)
Received: from home.elischer.org (home.elischer.org [207.76.204.203])
	by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA93169;
	Sat, 18 Sep 1999 13:42:15 -0700 (PDT)
Date: Sat, 18 Sep 1999 13:42:20 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
X-Sender: julian@home.elischer.org
To: Wayne Cuddy <wayne@crb-web.com>
Cc: FreeBSD Hackers List <freebsd-hackers@FreeBSD.ORG>
Subject: Re: what is devfs?
In-Reply-To: <Pine.LNX.4.10.9909181421550.22037-100000@crb.crb-web.com>
Message-ID: <Pine.BSF.4.05.9909181322590.19831-100000@home.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

DEVFS is an experimental idea.

Both FreeBSD and Linux are experimenting with the concept
of a filesystem type that is used by the  kernel to export it's view of
what devices are present and capable of being used.

in -current, the devfsext.h file is no longer required as the functions it
defines are no longer directly called by the driver (I need to fix the
example drivers) and instead, a function "make_device()" is called . This
is done regradless of whether DEVFS is compiled in, and this function then
calls the DEVFS functions if DEVFS is required.

The theory is that DEVFS allows totally dynamic registration of devices.
This is required in several cases..

1/ many new device drivers, are written and co-ordinating/assigning major
numbers becomes infeasible.. (not happenned yet, but might in the future)

2/ Subdividing devices for sub functions may need to be arbitrary in form,
and it may be infeasible to assign minor numbers in a predefinable
manner... Think of a disk concatination scheme which is doen in the same
framework as a disk partition scheme. Is a BSD partition within a dos
partition the same minor number ans a dos partition within a BSD
partition? And what minor number is a partition of an concattinated drive
made from sub partitions of 3 differnt drives, one of which is divided
using DOS partitions and the other using a BSD partiton within a DOS
partition?  his is presently done with a major hack of assigning a
different major number to the concatinated device.

3/ NFS mounting a / filesystem from (say) NT which can NFS export a
filesystem but cannot export device nodes means that the local system
needs to provide it's own /dev. (this is getting to be less of a problem)
Or, getting a /dev/from Linux, where all the minors are wrong for BSD and
we need to get our own from "somewhere".

DEVFS itself works fine however a subsystem it required to be a useful
abstraction was vandalised and stripped out by some people who "didn't get
it" and it has not yet been replaced by equivalent code. That
functionality is required if you want to mount several local filesystems.
However the current devfs is quite capable of being used in NFS mounted
(netbooted) scenareos.





On Sat, 18 Sep 1999, Wayne Cuddy wrote:

> In the examples device drivers I see the inclusion of devfsext.h.  I read the
> README in the devfs directory but I am still a little unsure what devfs would
> be used for.  Can anyone give me some examples here.  Is there any more
> information pertaining to devfs?
> 
> Thanks in advance,
> Wayne 
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 13:57:28 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id C757414D9B
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 13:57:26 -0700 (PDT)
	(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
	by feral.com (8.8.7/8.8.7) with ESMTP id NAA29459;
	Sat, 18 Sep 1999 13:55:45 -0700
Date: Sat, 18 Sep 1999 13:57:20 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Julian Elischer <julian@whistle.com>
Cc: Wayne Cuddy <wayne@crb-web.com>,
	FreeBSD Hackers List <freebsd-hackers@FreeBSD.ORG>
Subject: Re: what is devfs?
In-Reply-To: <Pine.BSF.4.05.9909181322590.19831-100000@home.elischer.org>
Message-ID: <Pine.BSF.4.05.9909181356320.40709-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


For some alternative perspective- DEVFS has been around in many systems
for a long time. Solaris attempted to go this way, but has taken a decade
to move out a year's worth of progress.





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 14:24:59 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
	by hub.freebsd.org (Postfix) with ESMTP id DC0A014D59
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 14:24:55 -0700 (PDT)
	(envelope-from wilko@yedi.iaf.nl)
Received: from yedi.iaf.nl (uucp@localhost)
	  by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA19841;
	  Sat, 18 Sep 1999 23:14:51 +0200 (MET DST)
Received: (from wilko@localhost)
	by yedi.iaf.nl (8.9.3/8.9.3) id VAA89091;
	Sat, 18 Sep 1999 21:56:20 +0200 (CEST)
	(envelope-from wilko)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199909181956.VAA89091@yedi.iaf.nl>
Subject: Re: PAPERSIZE in /etc/make.conf?
In-Reply-To: <19990918204902.A54837@cichlids.cichlids.com> from Alexander Langer at "Sep 18, 1999  8:49: 2 pm"
To: alex@cichlids.com (Alexander Langer)
Date: Sat, 18 Sep 1999 21:56:20 +0200 (CEST)
Cc: naddy@mips.rhein-neckar.de, freebsd-hackers@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As Alexander Langer wrote ...
> Thus spake Wilko Bulte (wilko@yedi.iaf.nl):
> 
> Read again.
> 
> > part of /etc/profile (or something similar) so that it can be picked
> > up from a reliable place at runtime.
> 
> > > - groff has the paper size set as compile time option.

I read that. And I happen to think that compiled-in things for (e.g.)
papersize are a bad thing.

-- 
|   / o / /  _  	 Arnhem, The Netherlands	- Powered by FreeBSD -
|/|/ / / /( (_) Bulte 	 WWW  : http://www.tcja.nl 	http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 14:37:13 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from dt014nb6.san.rr.com (dt014nb6.san.rr.com [24.30.129.182])
	by hub.freebsd.org (Postfix) with ESMTP id 023FB14D62
	for <hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 14:37:10 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from gorean.org (master [10.0.0.2])
	by dt014nb6.san.rr.com (8.9.3/8.8.8) with ESMTP id PAA48027;
	Sat, 18 Sep 1999 15:41:29 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Message-ID: <37E40874.976C5523@gorean.org>
Date: Sat, 18 Sep 1999 14:47:32 -0700
From: Doug <Doug@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0913 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Shigio Yamaguchi <shigio@tamacom.com>
Cc: hackers@FreeBSD.ORG
Subject: Re: GNU GLOBAL
References: <199909181348.WAA02472@tamacom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	You state that you have made up your mind about this decision, so I won't
try to persuade you otherwise. I do think that there are some things that
you should think about though. 

Shigio Yamaguchi wrote:
> 
> I'm the author of GLOBAL source code tag system.
> 
> I have decided to release next version of GLOBAL as a GNU software.
> It means that it will be released under GPL instead of BSD license.

	Have you consulted an attorney about this decision? Are you sure that you
understand everything that this decision means? Do you realize that by
going with the GNU license you seriously hurt any chances you might have of
ever making any money off of your product? 

> This decision was made by practical reason, not by doctrine reason.
> It is advantageous for GLOBAL, because
> 
> o GNU softwares are distributed to widespread environments.

	I can't argue with this point. However with the growth of popularity of
the various *BSD's, that market is becoming more "widespread" as we speak. 

[snip]

> That makes it easy for GLOBAL to reach the goal, that is, becoming
> a common source code tag system in various environments.

	Hmmm... Well if your goal is to have a lot of people using your product,
in the short term going GNU is probably right. However, if you achieve your
goal, but your software is under the GNU license, what does that get for
you? 

> Since FreeBSD already includes GNU softwares, it seems no problem.
> GLOBAL itself will be as it be.

	I agree with the previous poster that our stated goal is (and should be)
eliminating as much GNU licensed software from the FreeBSD base as
possible. To my (albeit limited) knowledge nothing in the base depends on
GLOBAL, so I would be one of those who would be calling for its removal
from the base. Of course, a port of your program would be welcome, and in
fact if you are already settled in this decision you should start working
on a port now and beat the crowd. 
 
> I'm concerned about whether or not FreeBSD community accept GNU GLOBAL.
> I hope you not to reject it, because the rejection splits GLOBAL and it
> makes it hard for GLOBAL to be a common source code tag system.

	But that's YOUR goal. Our goals are different, and the GNU license
interferes with the goals of the FreeBSD project. Unfortunately we have
come to the point in time where those in the GNU camp have as their stated
goal the destruction of all other types of software licensing. It is sad
that people who should be working together to create the best tools
possible instead have to waste time with rhetoric and political
maneuvering. However, things are what they are. The likelihood of being
accepted by the GNU people is much smaller if you use a BSD license. At the
same time, by using a GNU license you prevent the BSD people from accepting
you at all. Of course, at this point in time such things as gcc are
necessary evils, however as already stated many of us are working on making
them less necessary. Your tool isn't "necessary" for anything at all at
this point, therefore it's easily disposed of. 
 
	I am sorry if my words sound harsh or argumentative, because that is not
my intention. For all I know, you product could be the best thing since
sliced bread. However the current state of the political aspects of
software development is what it is, so we are better served by not ignoring
it. 

Good luck,

Doug (who speaks only for himself)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 15:31:35 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from hermes.mixx.net (hermes.mixx.net [194.152.58.71])
	by hub.freebsd.org (Postfix) with ESMTP id 16BDF14D9B
	for <hackers@FreeBSD.org>; Sat, 18 Sep 1999 15:31:31 -0700 (PDT)
	(envelope-from graichen@innominate.de)
Received: from innominate.de (gatekeeper.innominate.de [212.5.16.129])
	by hermes.mixx.net (8.9.3/8.9.3) with SMTP id AAA24954
	for <hackers@FreeBSD.org>; Sun, 19 Sep 1999 00:31:27 +0200
Received: (qmail 19099 invoked from network); 18 Sep 1999 22:31:27 -0000
Received: from cello.innominate.local (192.168.0.13)
  by lingo01.innominate.local with SMTP; 18 Sep 1999 22:31:27 -0000
Received: from localhost (graichen@localhost)
	by cello.innominate.local (8.9.3/8.9.3) with ESMTP id AAA07118;
	Sun, 19 Sep 1999 00:31:25 +0200 (CEST)
	(envelope-from graichen@innominate.de)
X-Authentication-Warning: cello.innominate.local: graichen owned process doing -bs
Date: Sun, 19 Sep 1999 00:31:25 +0200 (CEST)
From: Thomas Graichen <graichen@innominate.de>
X-Sender: graichen@cello.innominate.local
To: Juha.Nurmela@quicknet.inet.fi
Cc: hackers@FreeBSD.org
Subject: Re: mysterious FreeBSD hardware problems
In-Reply-To: <Pine.BSF.4.10.9909181343220.45247-100000@pena.oh5nxo.ampr.org>
Message-ID: <Pine.BSF.4.10.9909190028270.7097-100000@cello.innominate.local>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 18 Sep 1999, Juha Nurmela wrote:
> 
> Your message at freebsd-hackers:
> 
> Hello,
> 
> This looks like the 'timecounter.method' problem,
> with AMD K5 model 0 sugar.
> I have had good result from a single patch,
> not touching the timecounter stuff, but instead:
> 
> If you can find file sys/i386/i386/switch.s
> and there a single operation
> hlt
> 
> try deleting that op, recompile/install kernel and reboot
> and see what happens. I'm curious to hear about the result.
> 
yes it works perfectly - it solved all the problems at once ...

how did you find that solution ? - maybe this should be added as
one of the cpu specific options to LINT - so that the next one will
find that easier ... a lot of thanks

t

-- 
graichen@innominate.de
                                                        innominate AG
                                                    networking people
fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 16:29: 6 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222])
	by hub.freebsd.org (Postfix) with ESMTP id 31CB214FF4
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 16:29:02 -0700 (PDT)
	(envelope-from mph@wopr.caltech.edu)
Received: (from mph@localhost)
	by wopr.caltech.edu (8.9.3/8.9.1) id QAA96560;
	Sat, 18 Sep 1999 16:27:55 -0700 (PDT)
	(envelope-from mph)
Date: Sat, 18 Sep 1999 16:27:55 -0700
From: Matthew Hunt <mph@astro.caltech.edu>
To: Wilko Bulte <wilko@yedi.iaf.nl>
Cc: Alexander Langer <alex@cichlids.com>, naddy@mips.rhein-neckar.de,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: PAPERSIZE in /etc/make.conf?
Message-ID: <19990918162754.A96449@wopr.caltech.edu>
References: <19990918204902.A54837@cichlids.cichlids.com> <199909181956.VAA89091@yedi.iaf.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <199909181956.VAA89091@yedi.iaf.nl>; from Wilko Bulte on Sat, Sep 18, 1999 at 09:56:20PM +0200
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Sep 18, 1999 at 09:56:20PM +0200, Wilko Bulte wrote:

> I read that. And I happen to think that compiled-in things for (e.g.)
> papersize are a bad thing.

In many cases, it's just a default that can be overriden by other
methods (command-line, environment, config file, etc.).

But if you really want to do it...

wopr:/usr/ports$ grep -l PAPERSIZE */*/Makefile | wc -l      
      21

Those, plus groff, I guess.  Don't forget to send your patches to
the authors of the programs in the Ports Collection, in the hope
that they'll integrate them.

-- 
Matthew Hunt <mph@astro.caltech.edu> * Stay close to the Vorlon.
http://www.pobox.com/~mph/           *


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 17: 7:56 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mta3.rcsntx.swbell.net (mta3.rcsntx.swbell.net [151.164.30.27])
	by hub.freebsd.org (Postfix) with ESMTP id 85E2914D35
	for <hackers@FreeBSD.org>; Sat, 18 Sep 1999 17:07:53 -0700 (PDT)
	(envelope-from chris@holly.dyndns.org)
Received: from holly.dyndns.org (adsl-216-62-157-60.dsl.hstntx.swbell.net)
 by mta3.rcsntx.swbell.net
 (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7)
 with ESMTP id <0FIA00ACQ5NAZV@mta3.rcsntx.swbell.net> for hackers@FreeBSD.org;
 Sat, 18 Sep 1999 19:06:47 -0500 (CDT)
Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3)
 id TAA23072; Sat, 18 Sep 1999 19:06:57 -0500 (CDT envelope-from chris)
Date: Sat, 18 Sep 1999 19:06:57 -0500
From: Chris Costello <chris@calldei.com>
Subject: Re: what is devfs?
In-reply-to: <Pine.BSF.4.05.9909181322590.19831-100000@home.elischer.org>
To: Julian Elischer <julian@whistle.com>
Cc: hackers@FreeBSD.org
Reply-To: chris@calldei.com
Message-id: <19990918190657.I12328@holly.calldei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
User-Agent: Mutt/0.96.6i
References: <Pine.LNX.4.10.9909181421550.22037-100000@crb.crb-web.com>
 <Pine.BSF.4.05.9909181322590.19831-100000@home.elischer.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Sep 18, 1999, Julian Elischer wrote:
> DEVFS is an experimental idea.

   I must also say that DEVFS is an excellent idea.

   I honestly didn't really understand it until recently, though
I've heard about it for a while.

-- 
|Chris Costello <chris@calldei.com>
|Watch out for off-by-one errors.
`----------------------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 17:14:32 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id 933E014D35
	for <hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 17:14:25 -0700 (PDT)
	(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
	by feral.com (8.8.7/8.8.7) with ESMTP id RAA29821;
	Sat, 18 Sep 1999 17:12:38 -0700
Date: Sat, 18 Sep 1999 17:14:12 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Chris Costello <chris@calldei.com>
Cc: Julian Elischer <julian@whistle.com>, hackers@FreeBSD.ORG
Subject: Re: what is devfs?
In-Reply-To: <19990918190657.I12328@holly.calldei.com>
Message-ID: <Pine.BSF.4.05.9909181713260.40848-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> On Sat, Sep 18, 1999, Julian Elischer wrote:
> > DEVFS is an experimental idea.
> 
>    I must also say that DEVFS is an excellent idea.

It's a marvelous idea, and is going to be very necessary when large Fibre
fabrics become more common. The problems of making it stable and
meaningful are enormous though.





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 18:45:11 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.xmission.com (mail.xmission.com [198.60.22.22])
	by hub.freebsd.org (Postfix) with ESMTP id AECBB14CAE
	for <hackers@freebsd.org>; Sat, 18 Sep 1999 18:45:09 -0700 (PDT)
	(envelope-from wes@softweyr.com)
Received: from [204.68.178.39] (helo=softweyr.com)
	by mail.xmission.com with esmtp (Exim 2.12 #2)
	id 11SW2N-0001f6-00; Sat, 18 Sep 1999 19:45:08 -0600
Message-ID: <37E44022.9126EB3F@softweyr.com>
Date: Sat, 18 Sep 1999 19:45:06 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Shigio Yamaguchi <shigio@tamacom.com>
Cc: hackers@FreeBSD.ORG
Subject: Re: GNU GLOBAL
References: <199909181348.WAA02472@tamacom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Shigio Yamaguchi wrote:
> 
> I'm the author of GLOBAL source code tag system.
> 
> I have decided to release next version of GLOBAL as a GNU software.
> It means that it will be released under GPL instead of BSD license.
> 
> This decision was made by practical reason, not by doctrine reason.

There are some types of software for which the GPL is the best license.
In my opinion, programming tools of many sorts -- compilers, linkers,
editors, assemblers -- fit into this category.  Contrary to what some
believe, we BSD'ers are not rabid GPL haters, we just don't like to see
it attached to important pieces of software that developers might want
to turn into a product, because that limits the audience.

Thank you for telling us about your product.

-- 
            "Where am I, and what am I doing in this handbasket?"

Wes Peters                                                         Softweyr LLC
wes@softweyr.com                                           http://softweyr.com/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 18:47: 4 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.xmission.com (mail.xmission.com [198.60.22.22])
	by hub.freebsd.org (Postfix) with ESMTP id 10F8614CAE
	for <freebsd-hackers@freebsd.org>; Sat, 18 Sep 1999 18:47:02 -0700 (PDT)
	(envelope-from wes@softweyr.com)
Received: from [204.68.178.39] (helo=softweyr.com)
	by mail.xmission.com with esmtp (Exim 2.12 #2)
	id 11SW4D-0001lc-00; Sat, 18 Sep 1999 19:47:01 -0600
Message-ID: <37E44093.ABBA1C5@softweyr.com>
Date: Sat, 18 Sep 1999 19:46:59 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: W Gerald Hicks <wghicks@bellsouth.net>
Cc: Shigio Yamaguchi <shigio@tamacom.com>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: GNU GLOBAL
References: <199909181750.NAA03329@bellsouth.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

W Gerald Hicks wrote:
> 
> I don't see much of a problem, other than requiring its removal
> from the FreeBSD source tree.  Although FreeBSD has a 'contrib'
> and 'gnu' hierarchy in the source tree, I believe the trend
> should be to reduce the existing members there and also to avoid
> adding new ones.
> 
> imho, global (a fine software package) shouldn't have been in the
> OS source tree anyway.  To me, the proper place seems to be in the
> ports collection along with many other development utilities.
> 
> [...]
> 
> I'll be preparing a port for global this afternoon and submitting
> a change request to have it removed from the source tree in favor
> of using the port on FreeBSD.

Yes, quite appropriate.  Thanks for the idea *and* the bits, Jerry.

-- 
            "Where am I, and what am I doing in this handbasket?"

Wes Peters                                                         Softweyr LLC
wes@softweyr.com                                           http://softweyr.com/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 19: 0:55 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.xmission.com (mail.xmission.com [198.60.22.22])
	by hub.freebsd.org (Postfix) with ESMTP id 1E7FF14DD1
	for <freebsd-hackers@freebsd.org>; Sat, 18 Sep 1999 19:00:52 -0700 (PDT)
	(envelope-from wes@softweyr.com)
Received: from [204.68.178.39] (helo=softweyr.com)
	by mail.xmission.com with esmtp (Exim 2.12 #2)
	id 11SWHa-0003AO-00; Sat, 18 Sep 1999 20:00:51 -0600
Message-ID: <37E443D0.AB9C0881@softweyr.com>
Date: Sat, 18 Sep 1999 20:00:48 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Weisgerber <naddy@mips.rhein-neckar.de>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: PAPERSIZE in /etc/make.conf?
References: <7rvu0p$1lfr$1@bigeye.rhein-neckar.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Christian Weisgerber wrote:
> 
> Should we have a PAPERSIZE variable (A4 vs. letter) in /etc/make.conf?
> 
> - groff has the paper size set as compile time option.
> 
> - Various ports that now exist in two versions or require the
>   user to define the paper size at build time could automatically
>   pull the value in.

Yes.  I think I encountered this with enscript the other day, too.  Sent
the LaserJam into a blinking fit, displaying "PC LOAD A4".

-- 
            "Where am I, and what am I doing in this handbasket?"

Wes Peters                                                         Softweyr LLC
wes@softweyr.com                                           http://softweyr.com/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 19: 1:48 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7CDAD153D1; Sat, 18 Sep 1999 19:01:34 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id LAA98076;
	Sun, 19 Sep 1999 11:31:06 +0930 (CST)
Date: Sun, 19 Sep 1999 11:31:06 +0930
From: Greg Lehey <grog@lemis.com>
To: Sheldon Hearn <sheldonh@uunet.co.za>
Cc: Doug <Doug@gorean.org>, FreeBSD-committers@FreeBSD.org,
	Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>,
	hackers@FreeBSD.org, sos@FreeBSD.org, bde@FreeBSD.org
Subject: Re: panic() the system from the console (was: Re: kern/13721: There is no way to force system panic from console)
Message-ID: <19990919113105.X55065@freebie.lemis.com>
References: <Pine.BSF.4.10.9909161329200.26117-100000@dt014nb6.san.rr.com> <73296.937561536@axl.noc.iafrica.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <73296.937561536@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, Sep 17, 1999 at 11:45:36AM +0200
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
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-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[including -committers for political correctness]

On Friday, 17 September 1999 at 11:45:36 +0200, Sheldon Hearn wrote:
> On Thu, 16 Sep 1999 13:30:30 MST, Doug wrote:
>> 	Would not the 'panic' option in DDB be enough to handle this, or
>> am I missing something?
>
> He wanted a to be able to panic() a machine from console without being
> able to drop to DDB from console. I think this is because he believes
> that DDB is a security problem. :-)

Well, I'm missing something: the beginning of this thread, so this may
not be 100% relevant, but I've just had the situation. So:

I believe that panicing the system is also a security problem.  But
sometimes people have hangs and just want to get a dump.  Installing
DDB is overkill for this situation; how about a key attribute that
panics the system?  It would probably make sense to have a sysctl or
some such to enable it.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 19:50:21 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from explorer.tip.CSIRO.AU (explorer.tip.CSIRO.AU [130.155.191.10])
	by hub.freebsd.org (Postfix) with ESMTP id 9FD2A1501E
	for <hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 19:50:13 -0700 (PDT)
	(envelope-from amy@explorer.tip.CSIRO.AU)
Received: from explorer.tip.CSIRO.AU (localhost [127.0.0.1])
	by explorer.tip.CSIRO.AU (8.9.3/8.9.1) with ESMTP id MAA00555
	for <hackers@FreeBSD.ORG>; Sun, 19 Sep 1999 12:50:10 +1000 (EST)
	(envelope-from amy@explorer.tip.CSIRO.AU)
Message-Id: <199909190250.MAA00555@explorer.tip.CSIRO.AU>
From: amy@magellan.tip.CSIRO.AU
To: hackers@FreeBSD.ORG
Subject: StarOffice 5.1 (Sun version) on 3.3-STABLE
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <551.937709409.1@explorer.tip.CSIRO.AU>
Date: Sun, 19 Sep 1999 12:50:09 +1000
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I am attempting to install the Sun version of StarOffice 5.1 (for Linux) on
my FreeBSD 3.3-STABLE (CVSup'ed on the 18-SEP-1999) SMP box.  The "net"
install worked fine (into /usr/local/Office51).  The problem happens when
running the per-user setup.  It gets about 99% into the setup and then
hangs.

As far as I can tell it isn't an X11 problem, my home directory is NFS
mounted of a 2.2.8-STABLE box but the problem still exists with a local home
directory (so it isn't an NFS or locking issue - a long shot anyway).

I get a ton of kernel messages such as:

   /kernel: shared address space fork attempted: pid: 281
   /kernel: cmd setup.bin pid 281 tried to use non-present sched_yield
   last message repeated 1926 times

Has anyone seen this and more importantly does anyone have any ideas on how
to work around this.

It all seemed to be going so well - I thought one I got the "net" setup to
work the user side of things would be trivial :-)  So close and yet so far!

Many thanks, Shaun.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 20:39:58 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id 7A1A014D25
	for <freebsd-hackers@freebsd.org>; Sat, 18 Sep 1999 20:39:53 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id CE26C1CA7; Sun, 19 Sep 1999 11:39:52 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: Shigio Yamaguchi <shigio@tamacom.com>
Cc: W Gerald Hicks <wghicks@bellsouth.net>,
	freebsd-hackers@freebsd.org
Subject: Re: GNU GLOBAL 
In-reply-to: Your message of "Sat, 18 Sep 1999 13:50:31 -0400."
             <199909181750.NAA03329@bellsouth.net> 
Date: Sun, 19 Sep 1999 11:39:52 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990919033952.CE26C1CA7@overcee.netplex.com.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

W Gerald Hicks wrote:
> I don't see much of a problem, other than requiring its removal
> from the FreeBSD source tree.  Although FreeBSD has a 'contrib'
> and 'gnu' hierarchy in the source tree, I believe the trend
> should be to reduce the existing members there and also to avoid
> adding new ones.
> 
> imho, global (a fine software package) shouldn't have been in the
> OS source tree anyway.  To me, the proper place seems to be in the
> ports collection along with many other development utilities.
> 
> I don't agree with your perceptions of the GNU license but do
> respect your decision as the author to choose whatever license
> you wish.
> 
> I'll be preparing a port for global this afternoon and submitting
> a change request to have it removed from the source tree in favor
> of using the port on FreeBSD.

I think we should also remove the nvi patches as it contains global derived
code.  Since GPL is incompatable with the (bsd-style) nvi license and the
global patches add code to nvi, then it would be better to remove the
conflicting code.

Also, have you considered doing something like what was used on
/usr/src/sys/dev/aic7xxx/aic7xxx.seq ?

Will you be assigning the copyright to the FSF?  (ie: you'll never be able
to change your mind?  50 years is a long time...)

Cheers,
-Peter




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 21: 7:16 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from lcremeans.erols.com (lcremeans.erols.com [216.164.87.29])
	by hub.freebsd.org (Postfix) with ESMTP id 491B914D30
	for <hackers@FreeBSD.ORG>; Sat, 18 Sep 1999 21:07:12 -0700 (PDT)
	(envelope-from lee@lcremeans.erols.com)
Received: (from lee@localhost)
	by lcremeans.erols.com (8.9.3/8.9.3) id AAA43559;
	Sun, 19 Sep 1999 00:04:41 -0400 (EDT)
	(envelope-from lee)
Message-ID: <19990919000440.A43549@erols.com>
Date: Sun, 19 Sep 1999 00:04:40 -0400
From: Lee Cremeans <lcremeans@erols.com>
To: amy@magellan.tip.CSIRO.AU, hackers@FreeBSD.ORG
Subject: Re: StarOffice 5.1 (Sun version) on 3.3-STABLE
References: <199909190250.MAA00555@explorer.tip.CSIRO.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199909190250.MAA00555@explorer.tip.CSIRO.AU>; from amy@magellan.tip.CSIRO.AU on Sun, Sep 19, 1999 at 12:50:09PM +1000
X-OS: FreeBSD 3.0-STABLE
Organization: My room? Are you crazy? :)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Sep 19, 1999 at 12:50:09PM +1000, amy@magellan.tip.CSIRO.AU wrote:
> Hi,
> 
> 
>    /kernel: shared address space fork attempted: pid: 281
>    /kernel: cmd setup.bin pid 281 tried to use non-present sched_yield
>    last message repeated 1926 times
> 
> Has anyone seen this and more importantly does anyone have any ideas on how
> to work around this.


sched_yield...your kernel probably doesn't have the POSIX real-time
scheduling stuff compiled in. Make sure these lines are in your config file:

options         "P1003_1B"
options         "_KPOSIX_PRIORITY_SCHEDULING"
options         "_KPOSIX_VERSION=199309L"

reconfig, recompile, install and reboot. 

-lee

-- 
+--------------------------------------------------------------------+
|      Lee Cremeans -- Manassas, VA, USA  (WakkyMouse on WTnet)      |  
|         lcremeans@erols.com | http://wakky.dyndns.org/~lee         |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message


From owner-freebsd-hackers  Sat Sep 18 22:20:19 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
	by hub.freebsd.org (Postfix) with ESMTP
	id C736915049; Sat, 18 Sep 1999 22:20:13 -0700 (PDT)
	(envelope-from aron@cs.rice.edu)
Received: (from aron@localhost)
	by cs.rice.edu (8.9.0/8.9.0) id AAA20766;
	Sun, 19 Sep 1999 00:20:12 -0500 (CDT)
Date: Sun, 19 Sep 1999 00:20:12 -0500 (CDT)
From: Mohit Aron <aron@cs.rice.edu>
Message-Id: <199909190520.AAA20766@cs.rice.edu>
To: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org
Subject: limit on number of sockets by zone allocator
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,
	I was recently doing some throughput tests with the Apache webserver
on FreeBSD-4.0. It seems that the recently introduced (after FreeBSD-2) zone
allocator limits the maximum number of socket structures to about 8000 (I 
configured my kernel with 256 MAXUSERS). A busy webserver can have about
50000 connections primarily due to TCP's TIME-WAIT state (see 
http://cs-tr.cs.rice.edu/Dienst/UI/2.0/Describe/ncstrl.rice_cs/TR99-335/). 
A limit of 8000 on socket descriptors would thus prevent a webserver from
achieving full throughput. Perhaps the maxsockets variable defined in
sys/uipc_socket2.c should be increased.



- Mohit


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message