From owner-freebsd-hackers  Sun Mar  9  1: 7:53 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 658B837B401
	for <freebsd-hackers@FreeBSD.ORG>; Sun,  9 Mar 2003 01:07:51 -0800 (PST)
Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8C3D843FA3
	for <freebsd-hackers@FreeBSD.ORG>; Sun,  9 Mar 2003 01:07:49 -0800 (PST)
	(envelope-from sos@spider.deepcore.dk)
Received: (from sos@localhost)
	by spider.deepcore.dk (8.12.8/8.12.8) id h2997lV8091523;
	Sun, 9 Mar 2003 10:07:47 +0100 (CET)
	(envelope-from sos)
From: Soeren Schmidt <sos@spider.deepcore.dk>
Message-Id: <200303090907.h2997lV8091523@spider.deepcore.dk>
Subject: Re: 3 IDE devices on Promise card + FreeBSD == not possible?
In-Reply-To: <20030308162453.GB1436@bubba.toscano.org>
To: Pete <pete-freebsd-hackers@toscano.org>
Date: Sun, 9 Mar 2003 10:07:47 +0100 (CET)
Cc: freebsd-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL98b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=ISO-8859-1
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

It seems Pete wrote:
> Hello,
> 
> I've been posting about this since the beginning on the year.  A few
> times on freebsd-questions, once on freebsd-hackers, and submitted a PR
> (http://www.freebsd.org/cgi/query-pr.cgi?pr=48165).  I have never found
> a solution beyond replacing FreeBSD with Linux.  (Which is not something
> I'd like to do, but know I can, if need be.  I'm trying to learn about
> FreeBSD, not Linux.)

To make it short, the disklabel problem is probably due to the disk
containing what disklabel see as a bogus label, try to zero out the
label by using dd if=/dev/zero of=/dev/adN count=100.

Now if you have a promise fasttrak its beyond me why you want to use
vinum to make a mirror...

In the post you refer to you have:
ar0: 29314MB <ATA RAID0 array> [3737/255/63] status: READY subdisks:
 0 READY ad4: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata2-master UDMA100
ar1: 29314MB <ATA RAID0 array> [3737/255/63] status: READY subdisks:
 0 READY ad6: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata3-master UDMA100
ar2: 29314MB <ATA RAID0 array> [3737/255/63] status: READY subdisks:
 0 READY ad7: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata3-slave UDMA100

You use ar0 as a single disk and thats fine.
Then you need a mirror of ad6 and ad7 to get that you first need to
delete ar1 and ar2 (which you have defined in the Promise BIOS
to get it past probing right ?).

So doing:

atacontrol delete ar1
atacontrol delete ar2

Get you rid of those two 1 disk arrays, then do:

atacontrol create mirror ad6 ad7

and you get a new ar1 array thats the mirror of ad6 & ad7..

Disklabel & newfs ar1 and you are done (remember the dd trick above if
disklabel thinks the label is bogus)....

-Søren

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


From owner-freebsd-hackers  Sun Mar  9  9:39:38 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8682737B404
	for <freebsd-hackers@FreeBSD.ORG>; Sun,  9 Mar 2003 09:39:35 -0800 (PST)
Received: from toscano.org (ip68-100-184-64.nv.nv.cox.net [68.100.184.64])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 486AE43FAF
	for <freebsd-hackers@FreeBSD.ORG>; Sun,  9 Mar 2003 09:39:34 -0800 (PST)
	(envelope-from pete@toscano.org)
Received: from bubba.toscano.org (localhost.localdomain [127.0.0.1])
	by bubba.toscano.org (8.12.8/8.12.8) with ESMTP id h29Hcamo021323;
	Sun, 9 Mar 2003 12:38:36 -0500
Received: (from pete@localhost)
	by bubba.toscano.org (8.12.8/8.12.5/Submit) id h29HcZsj021321;
	Sun, 9 Mar 2003 12:38:35 -0500
Date: Sun, 9 Mar 2003 12:38:35 -0500
From: Pete <pete-freebsd-hackers@toscano.org>
To: Soeren Schmidt <sos@spider.deepcore.dk>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: 3 IDE devices on Promise card + FreeBSD == not possible?
Message-ID: <20030309173835.GA21146@bubba.toscano.org>
Mail-Followup-To: Soeren Schmidt <sos@spider.deepcore.dk>,
	freebsd-hackers@FreeBSD.ORG
References: <20030308162453.GB1436@bubba.toscano.org> <200303090907.h2997lV8091523@spider.deepcore.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200303090907.h2997lV8091523@spider.deepcore.dk>
X-Unexpected: The Spanish Inquisition
User-Agent: Mutt/1.5.3i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


On Sun, 09 Mar 2003, Soeren Schmidt wrote:

> To make it short, the disklabel problem is probably due to the disk
> containing what disklabel see as a bogus label, try to zero out the
> label by using dd if=/dev/zero of=/dev/adN count=100.

This is what I initially thought, but when I swapped the two data
drives, disklabel thought the previous ar2's (and now ar1's) disklabel
was fine.  The drive that used to be ar1 and that had a valid disklabel
before swapping now had a "bogus" label.  (Did that description make
sense?)

> Now if you have a promise fasttrak its beyond me why you want to use
> vinum to make a mirror...

Well... 

   a) I want to learn about FreeBSD, not the Promise controller.  Until
   this email, I was thinking the only way to do software RAID with
   FreeBSD was Vinum... Now, I'm (more) confused.

   b) The Fasttrak controller isn't that wonderful and from what I've
   read, just software RAID on the card's PROM.  I've also heard (and
   briefly confirmed) that Linux's software RAID is faster than the
   card's.  I'm betting that FreeBSD's is comparable to Linux's.

   c) I don't want to be tied to a specific vendor's RAID.  This machine
   is made from old, spare parts.  If the Fasttrak card were to die, I'd
   love to be able to stick in a different IDE controller and still have
   the RAID working with little or no fuss.

> In the post you refer to you have:
> ar0: 29314MB <ATA RAID0 array> [3737/255/63] status: READY subdisks:
>  0 READY ad4: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata2-master UDMA100
> ar1: 29314MB <ATA RAID0 array> [3737/255/63] status: READY subdisks:
>  0 READY ad6: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata3-master UDMA100
> ar2: 29314MB <ATA RAID0 array> [3737/255/63] status: READY subdisks:
>  0 READY ad7: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata3-slave UDMA100

FWIW, I'm currently using a 2 controller config with each drive on its
own dedicated IDE channel.  The second controller is just a straight
Promise controller, not a Fasttrak.

> You use ar0 as a single disk and thats fine.  Then you need a mirror
> of ad6 and ad7 to get that you first need to delete ar1 and ar2 (which
> you have defined in the Promise BIOS to get it past probing right ?).

When all three disks were on the Fasttrak, I did have them all defined
as single-disk, striped volumes.  I needed to do this to boot from
ar0/ad4.  Right now, I don't know why I set the other two to be
single-disk, striped volumes.  When I moved the latter two disks to the
second controller, they still booted as ar1 and ar2 (ad8 on ar1 and ad10
on ar2), but I had no controller BIOS to tweak.  I just guessed that
that was how FreeBSD treated drives on these controllers.

> So doing:
> 
> atacontrol delete ar1
> atacontrol delete ar2

Now this was interesting.  I did this, then rebooted.  This is what I
get now:

ad8: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata4-master UDMA100
ad10: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata5-master UDMA100
ar0: 29314MB <ATA RAID0 array> [3737/255/63] status: READY subdisks:
 0 READY ad4: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata2-master UDMA100

> atacontrol create mirror ad6 ad7

This is starting to _really_ confuse me. Does FreeBSD have two software
RAID systems?  Is there something built into the ATA controller drivers
that can do software RAID too?  It looks that way from that atacontrol
and ata man pages.  Where does Vinum fit in here or is Vinum extraneous
now?  Is Vinum just a front-end to the ata system?  I'm sooo confused... 

> and you get a new ar1 array thats the mirror of ad6 & ad7..

Indeed I do.

> Disklabel & newfs ar1 and you are done (remember the dd trick above if
> disklabel thinks the label is bogus)....

Excellent!  It looks like this is what I was looking for.  

Thank you so very much, Søren.

pete

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


From owner-freebsd-hackers  Sun Mar  9  9:46:55 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 797FE37B401
	for <freebsd-hackers@freebsd.org>; Sun,  9 Mar 2003 09:46:54 -0800 (PST)
Received: from popcs.cs.tin.it (popcs.cs.tin.it [194.243.155.125])
	by mx1.FreeBSD.org (Postfix) with SMTP id 627D243F3F
	for <freebsd-hackers@freebsd.org>; Sun,  9 Mar 2003 09:46:52 -0800 (PST)
	(envelope-from freebsd@cs.tin.it)
Received: (qmail 12594 invoked from network); 9 Mar 2003 17:46:48 -0000
Received: from unknown (HELO cruiser) (212.216.172.146)
  by popcs.cs.tin.it with SMTP; 9 Mar 2003 17:46:48 -0000
Date: Sun, 9 Mar 2003 18:46:22 +0100
From: Ferruccio Vitale <freebsd@cs.tin.it>
To: freebsd-hackers@freebsd.org
Subject: divert socket
Message-Id: <20030309184622.1ae7fe6a.freebsd@cs.tin.it>
X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i386-portbld-freebsd4.7)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hi hackers,

I've a daemon which create and open a divert socket, which is feeded by a 'tee rule' in ipfw rulset; my doubt is: what is it passed to this socket? entire packet or at least layer-3 information (tcp/udp/...)?

Regards,
Ferruccio

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


From owner-freebsd-hackers  Sun Mar  9 12:44: 7 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9494E37B401
	for <hackers@freebsd.org>; Sun,  9 Mar 2003 12:44:06 -0800 (PST)
Received: from mailout09.sul.t-online.com (mailout09.sul.t-online.com [194.25.134.84])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DCBA743FBD
	for <hackers@freebsd.org>; Sun,  9 Mar 2003 12:44:05 -0800 (PST)
	(envelope-from Robert.Eckardt@t-online.de)
Received: from fwd11.sul.t-online.de 
	by mailout09.sul.t-online.com with smtp 
	id 18s7eN-0007kc-06; Sun, 09 Mar 2003 21:44:03 +0100
Received: from eckardt.org (320073016804-0001@[217.81.161.132]) by fwd11.sul.t-online.com
	with esmtp id 18s7eH-26qnuiC; Sun, 9 Mar 2003 21:43:57 +0100
Received: from roberte.no-ip.org (localhost [127.0.0.1])
	by eckardt.org (8.11.6/8.11.6) with ESMTP id h29Ki0222222
	for <hackers@freebsd.org>; Sun, 9 Mar 2003 21:44:00 +0100 (CET)
	(envelope-from Robert.Eckardt@Robert-Eckardt.de)
From: Robert.Eckardt@t-online.de (Robert Eckardt)
To: hackers@freebsd.org
Subject: Guide to writing device drivers sought
Date: Sun, 9 Mar 2003 21:44:00 +0100
Message-Id: <20030309204400.M24984@Robert-Eckardt.de>
X-Mailer: Open WebMail 1.71 20020827
X-OriginatingIP: 217.81.161.132 (roberte)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
X-Sender: 320073016804-0001@t-dialin.net
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hi,

long ago I used the joy-driver as an example to integrate my own device
driver. I'm now trying (once again :-) to do the same in FreeBSD-4.7.
Unfortunately, joy no longer functions correctly (since 4.1) and so it is an
inappropriate example.
My driver is going to create two devices with different minor device numbers
(/dev/dcf and /dev/dcf100) (as joy should do too), which can be used
simultaneously (both accessing the same I/O port e.g. 0x201).

Where can I find an introduction to the currently used device framework?
(Things seem to be spreaad out over numerous man pages.)

How can I write a device driver that creates multiple devices with different
minor device numbers for each given I/O port?

Which driver is suited best as a simple example?

Where can I find an introduction how to deal with PnP- and Non-PnP-hardware
correctly?


Thanks,
Robert

--
Dr. Robert Eckardt    ---    Robert.Eckardt@Robert-Eckardt.de

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


From owner-freebsd-hackers  Sun Mar  9 14:31:17 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 703AE37B404
	for <freebsd-hackers@freebsd.org>; Sun,  9 Mar 2003 14:31:16 -0800 (PST)
Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A8E9543FD7
	for <freebsd-hackers@freebsd.org>; Sun,  9 Mar 2003 14:31:15 -0800 (PST)
	(envelope-from julian@elischer.org)
Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4])
          by sccrmhc03.attbi.com (sccrmhc03) with ESMTP
          id <2003030922311400300ajii5e>; Sun, 9 Mar 2003 22:31:14 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA98951;
	Sun, 9 Mar 2003 14:31:14 -0800 (PST)
Date: Sun, 9 Mar 2003 14:31:12 -0800 (PST)
From: Julian Elischer <julian@elischer.org>
To: Ferruccio Vitale <freebsd@cs.tin.it>
Cc: freebsd-hackers@freebsd.org
Subject: Re: divert socket
In-Reply-To: <20030309184622.1ae7fe6a.freebsd@cs.tin.it>
Message-ID: <Pine.BSF.4.21.0303091430090.98917-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG



On Sun, 9 Mar 2003, Ferruccio Vitale wrote:

> Hi hackers,
> 
> I've a daemon which create and open a divert socket, which is feeded
> by a 'tee rule' in ipfw rulset; my doubt is: what is it passed to
> this socket? entire packet or at least layer-3 information
> (tcp/udp/...)?

it should get an IP packet.
Any packet you send back will be given to ip for input processing.

> 
> Regards,
> Ferruccio
> 
> 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  Sun Mar  9 16:14:48 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 00F2C37B401
	for <hackers@freebsd.org>; Sun,  9 Mar 2003 16:14:47 -0800 (PST)
Received: from mail.darq.net (phear.darq.net [213.253.1.14])
	by mx1.FreeBSD.org (Postfix) with SMTP id 79B2B43F75
	for <hackers@freebsd.org>; Sun,  9 Mar 2003 16:14:45 -0800 (PST)
	(envelope-from kaneda@darq.net)
Received: (qmail 11742 invoked by uid 1010); 10 Mar 2003 00:14:45 -0000
Date: Mon, 10 Mar 2003 00:14:45 +0000
From: Richard Airlie <kaneda@darq.net>
To: Robert Eckardt <Robert.Eckardt@t-online.de>
Cc: hackers@freebsd.org
Subject: Re: Guide to writing device drivers sought
Message-ID: <20030310001444.GA14554@phear.darq.net>
References: <20030309204400.M24984@Robert-Eckardt.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030309204400.M24984@Robert-Eckardt.de>
User-Agent: Mutt/1.4i
X-Url: http://www.darq.net/
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

hi,

On Sun, Mar 09, 2003 at 09:44:00PM +0100, Robert Eckardt wrote:
> long ago I used the joy-driver as an example to integrate my own device
> driver. I'm now trying (once again :-) to do the same in FreeBSD-4.7.
> Unfortunately, joy no longer functions correctly (since 4.1) and so it is an
> inappropriate example.

i have submitted a PR including a patch for this problem:

<http://www.freebsd.org/cgi/query-pr.cgi?pr=46734>

(it would be really nice if someone could look at this and give it the 'thumbs
up' if its ok).

the patch allows for /dev/joy0 and /dev/joy1 to both exist, attached to the
same I/O port (0x201).

if you look at the patch you'll see there are only minor changes required to
achieve this.. its quite straightforward.

hope this is some use to you -

regards,
richard.

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


From owner-freebsd-hackers  Sun Mar  9 17:16: 9 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5B01537B401
	for <hackers@freebsd.org>; Sun,  9 Mar 2003 17:16:08 -0800 (PST)
Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D9FF543F85
	for <hackers@freebsd.org>; Sun,  9 Mar 2003 17:16:07 -0800 (PST)
	(envelope-from julian@elischer.org)
Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4])
          by rwcrmhc52.attbi.com (rwcrmhc52) with ESMTP
          id <2003031001160605200d3g6fe>; Mon, 10 Mar 2003 01:16:07 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA99931;
	Sun, 9 Mar 2003 17:16:06 -0800 (PST)
Date: Sun, 9 Mar 2003 17:16:05 -0800 (PST)
From: Julian Elischer <julian@elischer.org>
To: Richard Airlie <kaneda@darq.net>
Cc: Robert Eckardt <Robert.Eckardt@t-online.de>, hackers@freebsd.org
Subject: Re: Guide to writing device drivers sought
In-Reply-To: <20030310001444.GA14554@phear.darq.net>
Message-ID: <Pine.BSF.4.21.0303091713370.98917-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

At one stage the example driver in -current 
(/usr/share/examples/drivers) was correct for 4.x
but I don't know if that is true any more as
so many things have changed..

It's a shellscript that generates a skeleton driver for you.


On Mon, 10 Mar 2003, Richard Airlie wrote:

> hi,
> 
> On Sun, Mar 09, 2003 at 09:44:00PM +0100, Robert Eckardt wrote:
> > long ago I used the joy-driver as an example to integrate my own device
> > driver. I'm now trying (once again :-) to do the same in FreeBSD-4.7.
> > Unfortunately, joy no longer functions correctly (since 4.1) and so it is an
> > inappropriate example.
> 
> i have submitted a PR including a patch for this problem:
> 
> <http://www.freebsd.org/cgi/query-pr.cgi?pr=46734>
> 
> (it would be really nice if someone could look at this and give it the 'thumbs
> up' if its ok).
> 
> the patch allows for /dev/joy0 and /dev/joy1 to both exist, attached to the
> same I/O port (0x201).
> 
> if you look at the patch you'll see there are only minor changes required to
> achieve this.. its quite straightforward.
> 
> hope this is some use to you -
> 
> regards,
> richard.
> 
> 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  Sun Mar  9 23: 9: 4 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 164D037B40A
	for <freebsd-hackers@FreeBSD.org>; Sun,  9 Mar 2003 23:08:58 -0800 (PST)
Received: from web40812.mail.yahoo.com (web40812.mail.yahoo.com [66.218.78.189])
	by mx1.FreeBSD.org (Postfix) with SMTP id A5B9B43FEC
	for <freebsd-hackers@FreeBSD.org>; Sun,  9 Mar 2003 23:08:54 -0800 (PST)
	(envelope-from rimi4eva@yahoo.com)
Message-ID: <20030310070854.48360.qmail@web40812.mail.yahoo.com>
Received: from [217.146.9.213] by web40812.mail.yahoo.com via HTTP; Sun, 09 Mar 2003 23:08:54 PST
Date: Sun, 9 Mar 2003 23:08:54 -0800 (PST)
From: Ango A <rimi4eva@yahoo.com>
Reply-To: ango_a@yahoo.com
Subject: Mutual Investment proposal
To: rimi4eva@yahoo.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

DEAR SIR,

I HAVE THE HONOUR AND CONFIDENCE TO INTRODUCE TO YOU
THIS BUSSINESS IN VIEW OF THE FACT THAT YOU ARE
TRUSTWORTHY AND RELIABLE.

I AM MR. Ango A, THE EASTERN DISTRICT ACCOUNTANT OF
STANDARD TRUST BANK PLC (STB). THERE IS AN ACCOUNT
OPENED IN THIS BANK IN 1982 AND SINCE 1990 NOBODY HAS
OPERATED ON THIS ACCOUNT AGAIN. AFTER INTENSIVE
INVESTIGATION, I DISCOVERED THAT THE OWNER OF THIS
ACCOUNT WAS THE OWNER OF CREST MARTINS CO. LTD. A
FOREIGNER FROM SWEDEN, A CRUDE OIL MERCHANT, AND HE
DIED IN 1990 AND HAS NO NEXT OF KIN AND THE ACCOUNT
HAS NO BENEFICIARY, MY INVESTIGATION PROVED TO ME AS
WELL THAT HIS COMPANY DOES NOT KNOW ANYTHING ABOUT
THIS ACCOUNT. THE AMOUNT INVOLVED RUNS INTO SEVERAL
MILLIONS OF UNITED STATES DOLLARS, ABOUT US
$17,460,000.00 SEVENTEEN MILLION, FOUR HUNDRED AND
SIXTY THOUSAND DOLLARS.

IN THE LIGHT OF THE ABOVE FACT, I NEED YOUR ASSISTANCE
TO OPEN YOUR DOOR TO THIS OPPORTUNITY BY PROVIDING
YOUR ACCOUNT OR ANY ACCOUNT OF YOUR CHOICE WHERE THE
FUND WILL BE REMITTED.

YOUR ASSISTANCE AS A FOREIGNER IS NECESSARY BECAUSE
THIS MANAGEMENT IS READY TO WELCOME ANY PERSON, A
FOREIGNER WHO HAS CORRECT INFORMATION TO THIS ACCOUNT,
WHICH I WILL GIVE TO YOU IMMEDIATELY, IF YOU INTRESTED
TO CONCLUDE THIS TRANSACTION WITH ME. 

I WILL APPLY FOR AN ANNUAL LEAVE IMMEDIATELY I HEAR
FROM YOU THAT YOU ARE READY TO ACT AND RECEIVE THIS
FUND INTO YOUR ACCOUNT. THIS IS TO ENABLE ME USE MY
POSITION AND INFLUENCE TO EFFECT THE ONWARD
TRANSMISSION OF THIS MONEY TO YOUR DESIRED ACCOUNT.

AT THE CONCLUSION OF THIS BUSINESS, YOU WILL BE GIVEN
20% OF THE TOTAL AMOUNT, 75% WILL BE FOR US, WHILE 5%
BE SET ASIDE FOR CHARITY ORGANISATION AND EXPENSE WE
MIGHT INCURE DURING THE TRANSACTION.

I LOOK FORWARD TO YOUR EARNEST REPLY.

YOURS TRULY,
Mr. Ango A



__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

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


From owner-freebsd-hackers  Mon Mar 10  0:21: 3 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E775E37B408
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 00:20:59 -0800 (PST)
Received: from popcs.cs.tin.it (popcs.cs.tin.it [194.243.155.125])
	by mx1.FreeBSD.org (Postfix) with SMTP id AEEE243FE1
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 00:20:58 -0800 (PST)
	(envelope-from freebsd@cs.tin.it)
Received: (qmail 2928 invoked from network); 10 Mar 2003 08:20:56 -0000
Received: from cruiser.cs.tin.it (HELO cruiser) (212.216.178.193)
  by popcs.cs.tin.it with SMTP; 10 Mar 2003 08:20:56 -0000
Date: Mon, 10 Mar 2003 09:20:32 +0100
From: Ferruccio Vitale <freebsd@cs.tin.it>
To: freebsd-hackers@freebsd.org
Subject: Re: divert socket
Message-Id: <20030310092032.2fc71b8d.freebsd@cs.tin.it>
X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i386-portbld-freebsd4.7)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


I try to explain better my problem: when my daemon tries to read from this socket, recv tells me it read 68 bytes, for example, which is about message size at application layer, but what I read is not I expect (string without sense). Is there a particular way to read from a raw socket or a divert socket?

Ferruccio

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


From owner-freebsd-hackers  Mon Mar 10  2:19:25 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 293A237B404
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 02:19:24 -0800 (PST)
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9EE1143F75
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 02:19:22 -0800 (PST)
	(envelope-from des@ofug.org)
Received: by flood.ping.uio.no (Postfix, from userid 2602)
	id 844E15308; Mon, 10 Mar 2003 11:19:19 +0100 (CET)
X-URL: http://www.ofug.org/~des/
X-Disclaimer: The views expressed in this message do not necessarily
  coincide with those of any organisation or company with
  which I am or have been affiliated.
To: Pete <pete-freebsd-hackers@toscano.org>
Cc: Soeren Schmidt <sos@spider.deepcore.dk>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: 3 IDE devices on Promise card + FreeBSD == not possible?
From: Dag-Erling Smorgrav <des@ofug.org>
Date: Mon, 10 Mar 2003 11:19:19 +0100
In-Reply-To: <20030309173835.GA21146@bubba.toscano.org> (Pete's message of
 "Sun, 9 Mar 2003 12:38:35 -0500")
Message-ID: <xzpfzpvbk2g.fsf@flood.ping.uio.no>
User-Agent: Gnus/5.090014 (Oort Gnus v0.14) Emacs/21.2 (i386--freebsd)
References: <20030308162453.GB1436@bubba.toscano.org>
	<200303090907.h2997lV8091523@spider.deepcore.dk>
	<20030309173835.GA21146@bubba.toscano.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Pete <pete-freebsd-hackers@toscano.org> writes:
>> atacontrol create mirror ad6 ad7
> This is starting to _really_ confuse me. Does FreeBSD have two software
> RAID systems?

Yes (vinum and raidframe)

>                Is there something built into the ATA controller drivers
> that can do software RAID too?  It looks that way from that atacontrol
> and ata man pages.

No, but atacontrol knows how to configure hardware RAID controllers
such as your Promise FastTrack.

>                     Where does Vinum fit in here or is Vinum extraneous
> now?

Vinum is a volume manager with RAID functionality.

>       Is Vinum just a front-end to the ata system?

No, it's completely device independent.

DES
-- 
Dag-Erling Smorgrav - des@ofug.org

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


From owner-freebsd-hackers  Mon Mar 10  2:28:11 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B648237B401
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 02:28:10 -0800 (PST)
Received: from scribble.fsn.hu (scribble.fsn.hu [193.224.40.95])
	by mx1.FreeBSD.org (Postfix) with SMTP id 238A143FB1
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 02:28:09 -0800 (PST)
	(envelope-from bra@fsn.hu)
Received: (qmail 20495 invoked by uid 1000); 10 Mar 2003 10:28:06 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 10 Mar 2003 10:28:06 -0000
Date: Mon, 10 Mar 2003 11:28:06 +0100 (CET)
From: Attila Nagy <bra@fsn.hu>
To: "Peter J. Blok" <pblok@inter.NL.net>
Cc: freebsd-hackers@freebsd.org
Subject: Re: ng_fec on 4.7-RELEASE-p6
In-Reply-To: <200303082137.58864.pblok@inter.NL.net>
Message-ID: <Pine.LNX.4.53.0303101127170.11493@scribble.fsn.hu>
References: <200303052219.34832.pblok@inter.NL.net>
 <Pine.LNX.4.53.0303061033060.11493@scribble.fsn.hu> <200303082137.58864.pblok@inter.NL.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hello,

> Yes, I did ifconfig fxp[01] up. I didn't matter.
All I can say is that I am using this on an earlier STABLE and on CURRENT
with success...

----------[ Free Software ISOs - http://www.fsn.hu/?f=download ]----------
Attila Nagy					e-mail: Attila.Nagy@fsn.hu
Free Software Network (FSN.HU)		  phone @work: +361 210 1415 (194)
						cell.: +3630 306 6758

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


From owner-freebsd-hackers  Mon Mar 10  2:30:19 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0747B37B401
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 02:30:18 -0800 (PST)
Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E247B43F85
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 02:30:15 -0800 (PST)
	(envelope-from sos@spider.deepcore.dk)
Received: (from sos@localhost)
	by spider.deepcore.dk (8.12.8/8.12.8) id h2AAUE9r095348;
	Mon, 10 Mar 2003 11:30:14 +0100 (CET)
	(envelope-from sos)
From: Soeren Schmidt <sos@spider.deepcore.dk>
Message-Id: <200303101030.h2AAUE9r095348@spider.deepcore.dk>
Subject: Re: 3 IDE devices on Promise card + FreeBSD == not possible?
In-Reply-To: <xzpfzpvbk2g.fsf@flood.ping.uio.no>
To: Dag-Erling Smorgrav <des@ofug.org>
Date: Mon, 10 Mar 2003 11:30:14 +0100 (CET)
Cc: Pete <pete-freebsd-hackers@toscano.org>,
	freebsd-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL98b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=ISO-8859-1
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

It seems Dag-Erling Smorgrav wrote:
> Pete <pete-freebsd-hackers@toscano.org> writes:
> >> atacontrol create mirror ad6 ad7
> > This is starting to _really_ confuse me. Does FreeBSD have two software
> > RAID systems?
> 
> Yes (vinum and raidframe)

And ccd :)

> >                Is there something built into the ATA controller drivers
> > that can do software RAID too?  It looks that way from that atacontrol
> > and ata man pages.
> 
> No, but atacontrol knows how to configure hardware RAID controllers
> such as your Promise FastTrack.

No, thats not the case, the ATA driver has a built in RAID engine
to use with Promise and HighPoint controllers. The reason it is
like this is that it is nessesary to read the RAID config off the
disks in a vendor specific way, and neither of cdd/vinum could do
this when its was done.
ATA RAID's like the Promise Fasttrak are *not* HW RAID's its a
SW RAID engine in the BIOS on those cards. However that is only
used for booting from the RAID, and then the ATA driver picks up
the array config and uses that with its internal SW RAID engine.
Atacontrol just sees a generic ATA RAID interface, and the ATA
driver then knows how to r/w the config for a specific controller.

-Søren

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


From owner-freebsd-hackers  Mon Mar 10  5:24:53 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8BE4237B401
	for <hackers@FreeBSD.org>; Mon, 10 Mar 2003 05:24:51 -0800 (PST)
Received: from bart.LF.net (bart.LF.net [212.9.190.51])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DDBFD43F85
	for <hackers@FreeBSD.org>; Mon, 10 Mar 2003 05:24:50 -0800 (PST)
	(envelope-from ms@bart.LF.net)
Received: from ms by bart.LF.net with local (Exim 4.10)
	id 18sNG6-000OX2-00
	for hackers@FreeBSD.org; Mo, 10 Mär 2003 14:24:02 +0100
Date: Mon, 10 Mar 2003 14:24:02 +0100
From: Marc Schoechlin <ms@LF.net>
To: hackers@FreeBSD.org
Subject: mount_null evil ?
Message-ID: <20030310132402.GA93784@LF.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.4i
X-Ticket-Action: x
X-Ticket-Nr: x
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hi !

I´m currently developing a jail-management solution - I use a 
readonly mount_null for central software-management of the jails.

The manpage of mount_null says the following:

-----
-> man mount_null

BUGS
     THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK)
     AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM.  USE AT YOUR OWN
     RISK.  BEWARE OF DOG.  SLIPPERY WHEN WET.

     This code also needs an owner in order to be less dangerous - serious
     hackers can apply by sending mail to <hackers@FreeBSD.org> and announcing
     their intent to take it over.
-----

The manpage was written May 1, 1995 - is using this tool still dangerous ?

My experience up to now was very good....

Do you see any security or othe problems in using such a readonly 
mount_null within a jail ?

Regards

Marc Schöchlin 
 
-- 

Gruss / Best regards  |  LF.net GmbH        |  fon +49 711 90074-413
Marc Schoechlin       |  Ruppmannstr. 27    |  fax +49 711 90074-33
ms@LF.net             |  D-70565 Stuttgart  |  http://www.lf.net

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


From owner-freebsd-hackers  Mon Mar 10  7:39:44 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 15BBE37B401
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 07:39:43 -0800 (PST)
Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 864C043F93
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 07:39:42 -0800 (PST)
	(envelope-from tlambert2@mindspring.com)
Received: from dialup-209.244.104.52.dial1.sanjose1.level3.net ([209.244.104.52] helo=mindspring.com)
	by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128)
	(Exim 3.33 #1)
	id 18sPMX-0004aF-00; Mon, 10 Mar 2003 07:38:50 -0800
Message-ID: <3E6CB138.8254F6B6@mindspring.com>
Date: Mon, 10 Mar 2003 07:37:28 -0800
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Luigi Rizzo <rizzo@icir.org>
Cc: "Brandon D. Valentine" <brandon@dvalentine.com>,
	Doug Ambrisko <ambrisko@ambrisko.com>,
	Thierry Herbelot <thierry@herbelot.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: Realtek
References: <200303072134.26944.thierry@herbelot.com> <200303072117.h27LHoNL014430@www.ambrisko.com> <20030307214905.GI334@geekpunk.net> <20030308025549.A48905@xorpc.icir.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a427bda4a6d5514fe25c3fbd5c119b9dd0387f7b89c61deb1d350badd9bab72f9c350badd9bab72f9c
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Luigi Rizzo wrote:
> At this price level, you can also consider the Intel PRO1000/MT
> (part number is PWLA8492MT) which has two Gig-E ports (copper), is
> well supported under FreeBSD by the Intel-supported "em" driver,
> and costs $174 (list price, if you shop eg. on yahoo you can find
> it cheaper than that).
> 
> The good thing of this cart is that it works at Gig speed, and
> it is widely available so hopefully it won't disappear from
> the market by the time you place your order.

No, the best thing about all GigE is that you don't need a twisty
cable, It Just Works.  They should do the same thing for the 100Mbit,
IMO.  8-).

-- Terry

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


From owner-freebsd-hackers  Mon Mar 10  8: 3:44 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6920737B401; Mon, 10 Mar 2003 08:03:43 -0800 (PST)
Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id DFB0443F3F; Mon, 10 Mar 2003 08:03:42 -0800 (PST)
	(envelope-from tlambert2@mindspring.com)
Received: from dialup-209.244.104.52.dial1.sanjose1.level3.net ([209.244.104.52] helo=mindspring.com)
	by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128)
	(Exim 3.33 #1)
	id 18sPkV-0001Os-00; Mon, 10 Mar 2003 08:03:36 -0800
Message-ID: <3E6CB703.98FD0A2E@mindspring.com>
Date: Mon, 10 Mar 2003 08:02:11 -0800
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Craig Rodrigues <rodrigc@attbi.com>
Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org
Subject: Re: #warning must be protected by #if __GNUC__ in headers?
References: <20030308161943.GA54921@attbi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a41313399b37b9e09ee7a6b564a7512eed350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Craig Rodrigues wrote:
> In <sys/syslimits.h>, I see:
> 
> #if __GNUC__
> #warning "No user-serviceable parts inside."
> #endif
> 
> Does the use of #warning need to be protected by
> #if __GNUC__ in FreeBSD header files?

Yes.  It is a preprocessor directive specific the GCC preprocessor.
This was discussed in great detail about a month ago, when the
people trying to get TenDRA to compile FreeBSD discovered to their
horror that TenDRA's preprocessor incorrectly assigns meaning to
code that's #if'ed out, and blew chunks on the #warning, when it
should have ignored it.

> Some other header files check for __GNUC__ before using #warning,
> such as <sys/ioctl.h>, but <sys/dkstat.h> does not.

<sys/dkstat.h> is wrong.  Please see the original discussion for
more details.

-- Terry

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


From owner-freebsd-hackers  Mon Mar 10  8:11:38 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A1D8237B401
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 08:11:37 -0800 (PST)
Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D260C43FBD
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 08:11:36 -0800 (PST)
	(envelope-from ambrisko@www.ambrisko.com)
Received: from www.ambrisko.com (localhost [127.0.0.1])
	by ambrisko.com (8.12.6/8.12.6) with ESMTP id h2AGBahZ026869;
	Mon, 10 Mar 2003 08:11:36 -0800 (PST)
	(envelope-from ambrisko@www.ambrisko.com)
Received: (from ambrisko@localhost)
	by www.ambrisko.com (8.12.6/8.12.6/Submit) id h2AGBZKm026868;
	Mon, 10 Mar 2003 08:11:35 -0800 (PST)
	(envelope-from ambrisko)
From: Doug Ambrisko <ambrisko@ambrisko.com>
Message-Id: <200303101611.h2AGBZKm026868@www.ambrisko.com>
Subject: Re: Realtek
In-Reply-To: <3E6CB138.8254F6B6@mindspring.com>
To: Terry Lambert <tlambert2@mindspring.com>
Date: Mon, 10 Mar 2003 08:11:35 -0800 (PST)
Cc: freebsd-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL94b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Terry Lambert writes:
| No, the best thing about all GigE is that you don't need a twisty
| cable, It Just Works.  They should do the same thing for the 100Mbit,
| IMO.  8-).

They have started that.  Via has atleast one auto-mdi/mdi-x nic chip.
We'd like it if more companies start doing it but I wouldn't hold my
breath.

Caveat is that a Netgear auto mdi/mdi-x switch won't allways sync with 
the fxp0 in my laptop :-(  So looks like we are in for another round of
auto negotiation that doesn't always work.

I do like the Intel gig cards, since you can get dual fiber and copper 
version.

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 Mar 10  8:47:10 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BF7E837B401
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 08:47:07 -0800 (PST)
Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 777D843FCB
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 08:47:04 -0800 (PST)
	(envelope-from ambrisko@www.ambrisko.com)
Received: from www.ambrisko.com (localhost [127.0.0.1])
	by ambrisko.com (8.12.6/8.12.6) with ESMTP id h2AGl3hZ028762;
	Mon, 10 Mar 2003 08:47:03 -0800 (PST)
	(envelope-from ambrisko@www.ambrisko.com)
Received: (from ambrisko@localhost)
	by www.ambrisko.com (8.12.6/8.12.6/Submit) id h2AGl3ng028761;
	Mon, 10 Mar 2003 08:47:03 -0800 (PST)
	(envelope-from ambrisko)
From: Doug Ambrisko <ambrisko@ambrisko.com>
Message-Id: <200303101647.h2AGl3ng028761@www.ambrisko.com>
Subject: Re: Realtek
In-Reply-To: <200303072133.55358.wes@softweyr.com>
To: Wes Peters <wes@softweyr.com>
Date: Mon, 10 Mar 2003 08:47:03 -0800 (PST)
Cc: freebsd-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL94b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Wes Peters writes:
| On Friday 07 March 2003 09:16, Doug Ambrisko wrote:
| You did something truly bizarre.  I've tested similar cards on many 
| machines ranging from K6-2 400MHz to P4 2.4GHz and the RealTek 
| performance has always been at or near the bottom of the heap.  On the 
| slower processors, the overhead of aligning packets shows heavily, but it 
| can be noticed on any system.

Depends on what your systems is doing.  We are PCI bus limited.
 
| A number of the chips folded into the dc(4) driver are horrible and 
| perform right down there with the RealTek, but a few are fairly good.

Agreed.  We've tested the common 21143 and some clones.  We also ran
the tests a few times to the the dc(4) chip to get the TX delays 
right adjusted so they don't have FIFO under-runs since that adjustment
kill performance.
 
| The 3com 3c905s are generally quite good using the xl(4) driver, as are 
| the Intel EEPro's using fxp.  I've read of others struggling with both 
| but never encountered this myself.  I tend to be quite conservative about 
| throwing random versions of FreeBSD at systems, though, and many of those 
| complaints come from people at various points on -stable, rather than a 
| known release point.

We've had good success with the fxp(4) chips except for a strange bug
on an onboard motherboard version.  There seems to be a bug in the
eeprom setting for it that I patch in the fxp(4) driver.  Unfortunately
I'm guess at the correction since we haven't been able to get the 
definition of that register.  Since Intel sets to that value and makes
our bug go away we just do it.  Makes me nervous though.

| > So I'd say given a sufficiently fast CPU and memory the Realteks work
| > pretty darn good. 
| 
| For a sufficient engine RPM, that escort will do 85 MPH in first gear, 
| too.  ;^)

Yep, and if you never have to turn a corner and the engine can handle
it then it is okay.  Our '87 Porsche 911 can't turn in a "normal" sense 
very fast due to cronic understeer.  However, with a rear-weight bias
it spins very fast.  So to turn fast you just spin the car into the 
direction you need, gas it to stop the spin and off you go.  Side 
benefit it that you don't need to brake as much going into a corner
since when you are going side ways you are braking so you just factor that
in.

Is a Porsche 911 a performance car?  In the right hands it is otherwise
it's going backwards out of a corner which can be an interesting feeling!
Sounds like a Corvair.
 
| > To date we haven't had any trouble with them and we've shipped a bunch.
| 
| Give me 1 second and I can easily bring any of your systems to their 
| knees, regardless of which cards you have installed.  Everything is 
| relative.  Were you watching the system load while performing your 
| testing?  Was the cpu doing anything but routing?  Is it required to for 
| your application?  These and many others are all important questions, and 
| tend to have different answers for every application.  For a desktop 
| workstation with undemanding network application requirements (email, web 
| browsing, occasional software updates) RealTek or any other card that 
| successfully attach to the network and correctly autonegotiate with your 
| hub (shudder) or switch is fine.  Even a RealTek.  ;^)

Hmm, I thought I had said "benchmark in your environment".  We have a closed
box that is sort-of a router and a bridge.  So your only inputs is really
network traffic.  That is what we tune the box for.  So it would be interesting
to see you kill it in 1s.  Again our issue is PCI bus.  Now that the P4 
Serverworks chipset is out we finally have a machine that holds the current 
gig with crypto records by a lot (faster then a couple of P4 Xeon machines
we have).  With a 32bit/33Mhz we are pegged at the PCI chipset limits.  
One of the challenges of testing crypto (IPsec) stuff is having clients 
that can keep up.

I'be been told there is a paper in the works for HW crypto performance
based on this and other HW.  So results of this should be published.

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 Mar 10 10:39:50 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3B6AE37B401
	for <hackers@freebsd.org>; Mon, 10 Mar 2003 10:39:49 -0800 (PST)
Received: from smtp010.tiscali.dk (smtp010.tiscali.dk [212.54.64.103])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0191C43FB1
	for <hackers@freebsd.org>; Mon, 10 Mar 2003 10:39:48 -0800 (PST)
	(envelope-from dslb@tiscali.dk)
Received: from cpmail.dk.tiscali.com (mail.tiscali.dk [212.54.64.159])
	by smtp010.tiscali.dk (8.12.5/8.12.5) with ESMTP id h2AIdi50020589
	for <hackers@freebsd.org>; Mon, 10 Mar 2003 19:39:45 +0100 (MET)
Received: from [212.242.239.73] by cpmail.dk.tiscali.com with HTTP; Mon, 10 Mar 2003 19:39:13 +0100
Date: Mon, 10 Mar 2003 19:39:13 +0100
Message-ID: <3E4A9619000044DD@cpfe2.be.tisc.dk>
From: dslb@tiscali.dk
Subject: Insecure PHP installation?
To: hackers@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hi all

I know PHP is not in the base system, but I thought I could ask here anyw=
ay.
I have installed PHP on my FreeBSD 4.7 computer and did a "find / -perm
+0002". I could see that /usr/local/bin/pear is a script and world writab=
le,
isn't that a little dangerous?

br
socketd

ps: Please CC to me as I am not on the list (I think).


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


From owner-freebsd-hackers  Mon Mar 10 10:59:55 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 655EA37B404
	for <hackers@freebsd.org>; Mon, 10 Mar 2003 10:59:54 -0800 (PST)
Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9EA5843FA3
	for <hackers@freebsd.org>; Mon, 10 Mar 2003 10:59:53 -0800 (PST)
	(envelope-from DougB@freebsd.org)
Received: from master.gorean.org (12-234-22-23.client.attbi.com[12.234.22.23])
          by rwcrmhc52.attbi.com (rwcrmhc52) with SMTP
          id <2003031018595305200310qre>; Mon, 10 Mar 2003 18:59:53 +0000
Date: Mon, 10 Mar 2003 10:59:52 -0800 (PST)
From: Doug Barton <DougB@FreeBSD.org>
To: dslb@tiscali.dk
Cc: hackers@freebsd.org
Subject: Re: Insecure PHP installation?
In-Reply-To: <3E4A9619000044DD@cpfe2.be.tisc.dk>
Message-ID: <20030310105901.L11058@znfgre.tberna.bet>
References: <3E4A9619000044DD@cpfe2.be.tisc.dk>
Organization: http://www.FreeBSD.org/
X-message-flag: Outlook -- Not just for spreading viruses anymore!
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Mon, 10 Mar 2003 dslb@tiscali.dk wrote:

> Hi all
>
> I know PHP is not in the base system, but I thought I could ask here anyway.

You should have asked this on freebsd-ports@freebsd,org, and cc'ed the PHP
maintainer, FYI.

> I have installed PHP on my FreeBSD 4.7 computer and did a "find / -perm
> +0002". I could see that /usr/local/bin/pear is a script and world writable,
> isn't that a little dangerous?

That's definitely bad, yes. Please use send-pr to file a problem report
about this.

Doug

-- 

    This .signature sanitized for your protection

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


From owner-freebsd-hackers  Mon Mar 10 13:12:42 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3DFC837B401
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 13:12:41 -0800 (PST)
Received: from smtp10.wxs.nl (smtp10.wxs.nl [195.121.6.35])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5818B43F93
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 13:12:40 -0800 (PST)
	(envelope-from pblok@inter.NL.net)
Received: from bsdpc (ip503cf841.speed.planet.nl [80.60.248.65])
 by smtp10.wxs.nl (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002))
 with ESMTP id <0HBJ00IGRXK657@smtp10.wxs.nl> for freebsd-hackers@freebsd.org;
 Mon, 10 Mar 2003 22:12:07 +0100 (MET)
Date: Mon, 10 Mar 2003 22:11:32 +0100
From: "Peter J. Blok" <pblok@inter.NL.net>
Subject: patch for vinum
To: freebsd-hackers@freebsd.org
Message-id: <200303102211.32856.pblok@inter.NL.net>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_gBCpA4aS/zHcXV32pwZ6/w)"
User-Agent: KMail/1.5
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


--Boundary_(ID_gBCpA4aS/zHcXV32pwZ6/w)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline

Hi,

Can somebody commit the following patch for vinum. This is already inside 
FreeBSD-5.0, but seems to be forgotten in 4.X-STABLE.

It fixes a strange (and unknown) error code when doing vinum detach. The error 
variable is not set to 0.

Peter

--Boundary_(ID_gBCpA4aS/zHcXV32pwZ6/w)
Content-type: text/x-diff; charset=us-ascii; name=vinum.patch
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=vinum.patch

*** dev/vinum/vinumioctl.c.orig	Sun Feb  3 01:44:19 2002
--- dev/vinum/vinumioctl.c	Wed Jan  8 02:26:11 2003
***************
*** 629,634 ****
--- 629,635 ----
  	    give_plex_to_volume(msg->otherobject, msg->index); /* and give it to the volume */
  	    update_plex_config(plex->plexno, 0);
  	    save_config();
+ 	    reply->error = 0;
  	}
      }
  }

--Boundary_(ID_gBCpA4aS/zHcXV32pwZ6/w)--

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


From owner-freebsd-hackers  Mon Mar 10 13:14:20 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8FDB537B401
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 13:14:19 -0800 (PST)
Received: from bran.mc.mpls.visi.com (bran.mc.mpls.visi.com [208.42.156.103])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0161F43FA3
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 13:14:19 -0800 (PST)
	(envelope-from hawkeyd@visi.com)
Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193])
	by bran.mc.mpls.visi.com (Postfix) with ESMTP id 51DD449B8
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 15:14:18 -0600 (CST)
Received: (from hawkeyd@localhost)
	by sheol.localdomain (8.11.6/8.11.6) id h2ALEH224505
	for freebsd-hackers@freebsd.org; Mon, 10 Mar 2003 15:14:17 -0600 (CST)
	(envelope-from hawkeyd)
Date: Mon, 10 Mar 2003 15:14:17 -0600
From: D J Hawkey Jr <hawkeyd@visi.com>
To: freebsd-hackers@freebsd.org
Subject: [hawkeyd@visi.com: Patches for SA-03:02 (OpenSSL) and RELENG_4_6_2]
Message-ID: <20030310151417.A24481@sheol.localdomain>
Reply-To: hawkeyd@visi.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


Any sharpies out here that can verify whether OpenSSL under RELENG_4_5
is the same as RELENG_4_6_2?

I have a RELENG_4_5 box that needs the OpenSSL patch, and it appears that
only the FreeBSD CVS version numbers keep the patches from applying cleanly
in just seven of the modules affected.

Checking out some files in the RELENG_4_6_2 CVS tree, it looks to me as
though 4.6.2 was released with the same version of OpenSSL as 4.5 was.
Am I correct? And therefore, the RELENG_4_6_2 patches are appropriate for
RELENG_4_5? After applying said patches, does that make my RELENG_4_5
OpenSSL the same as CURRENT (just thinking ahead...)?

Thanks,
Dave

-- 
  ______________________                         ______________________
  \__________________   \    D. J. HAWKEY JR.   /   __________________/
     \________________/\     hawkeyd@visi.com    /\________________/
                      http://www.visi.com/~hawkeyd/


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


From owner-freebsd-hackers  Mon Mar 10 13:32:16 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2887337B401
	for <hackers@FreeBSD.org>; Mon, 10 Mar 2003 13:32:15 -0800 (PST)
Received: from mail.halplant.com (ip68-98-167-210.nv.nv.cox.net [68.98.167.210])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 77F7643F85
	for <hackers@FreeBSD.org>; Mon, 10 Mar 2003 13:32:14 -0800 (PST)
	(envelope-from A.J.Caines@halplant.com)
Received: by mail.halplant.com (Postfix, from userid 1001)
	id 9F994A8; Mon, 10 Mar 2003 16:32:13 -0500 (EST)
Date: Mon, 10 Mar 2003 16:32:13 -0500
From: Andrew J Caines <A.J.Caines@halplant.com>
To: hackers@FreeBSD.org
Subject: Re: mount_null evil ?
Message-ID: <20030310213213.GE87518@hal9000.halplant.com>
Reply-To: Andrew J Caines <A.J.Caines@halplant.com>
Mail-Followup-To: hackers@FreeBSD.org
References: <20030310132402.GA93784@LF.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030310132402.GA93784@LF.net>
Organization: H.A.L. Plant
X-PGP-Fingerprint: C59A 2F74 1139 9432 B457  0B61 DDF2 AA61 67C3 18A1
X-Powered-by: FreeBSD 4.8-RC
X-URL: http://halplant.com:88/
X-Yahoo-Profile: AJ_Z0
Importance: Normal
User-Agent: Mutt/1.5.3i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Marc,

> I?m currently developing a jail-management solution - I use a 
> readonly mount_null for central software-management of the jails.
> The manpage was written May 1, 1995 - is using this tool still dangerous 

I have used it for read-only mounts since way back and have not have any
problems, including brief periods of high I/O.

I'd have reservations allowing unique data on a read-write mount, however
I just did a few quick and simple tests of reads and writes on a rw null
mount on my 4.8-RC box with no apparent problem.


-Andrew-
-- 
 _______________________________________________________________________
| -Andrew J. Caines-   Unix Systems Engineer   A.J.Caines@halplant.com  |
| "They that can give up essential liberty to obtain a little temporary |
|  safety deserve neither liberty nor safety" - Benjamin Franklin, 1759 |

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


From owner-freebsd-hackers  Mon Mar 10 14:10: 9 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B82E837B404
	for <hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 14:10:07 -0800 (PST)
Received: from volans.palisadesys.com (volans.palisadesys.com [192.188.162.240])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 727C643FA3
	for <hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 14:10:06 -0800 (PST)
	(envelope-from ghelmer@palisadesys.com)
Received: from volans.palisadesys.com (ghelmer@localhost [127.0.0.1])
	by volans.palisadesys.com (8.12.7/8.12.7) with ESMTP id h2AMA5m4024647;
	Mon, 10 Mar 2003 16:10:05 -0600 (CST)
	(envelope-from ghelmer@palisadesys.com)
Received: (from ghelmer@localhost)
	by volans.palisadesys.com (8.12.7/8.12.7/Submit) id h2AMA57F024646;
	Mon, 10 Mar 2003 16:10:05 -0600 (CST)
X-Authentication-Warning: volans.palisadesys.com: ghelmer set sender to ghelmer@palisadesys.com using -f
Subject: Re: mount_null evil ?
From: Guy Helmer <ghelmer@palisadesys.com>
To: Andrew J Caines <A.J.Caines@halplant.com>
Cc: hackers@FreeBSD.ORG
In-Reply-To: <20030310213213.GE87518@hal9000.halplant.com>
References: <20030310132402.GA93784@LF.net>
	 <20030310213213.GE87518@hal9000.halplant.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: 
Message-Id: <1047334204.23435.26.camel@volans.palisadesys.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 
Date: 10 Mar 2003 16:10:04 -0600
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Mon, 2003-03-10 at 15:32, Andrew J Caines wrote:
> Marc,
> 
> > I?m currently developing a jail-management solution - I use a 
> > readonly mount_null for central software-management of the jails.
> > The manpage was written May 1, 1995 - is using this tool still dangerous 
> 
> I have used it for read-only mounts since way back and have not have any
> problems, including brief periods of high I/O.
> 
> I'd have reservations allowing unique data on a read-write mount, however
> I just did a few quick and simple tests of reads and writes on a rw null
> mount on my 4.8-RC box with no apparent problem.

I seemed to be able to crash the kernel regularly under FreeBSD 4.5 when
I used null mounts to share a read-only filesystem between jails.  My
application frequently rebuilt the jails by unmounting everything,
wiping out the old jail subdirectories, writing new jail subdirectories,
and remounting the shared read-only fs into each jail subdirectory.  I
gave up on null mounts and went back to having a separate copy of the
entire filesystem for each jail.

If null mounts work better now, I'll revisit it...

Guy

-- 
Guy Helmer <ghelmer@palisadesys.com>

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


From owner-freebsd-hackers  Mon Mar 10 14:43:25 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1493F37B405
	for <hackers@freebsd.org>; Mon, 10 Mar 2003 14:43:23 -0800 (PST)
Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 100CB43F85
	for <hackers@freebsd.org>; Mon, 10 Mar 2003 14:43:22 -0800 (PST)
	(envelope-from tlambert2@mindspring.com)
Received: from dialup-209.245.137.142.dial1.sanjose1.level3.net ([209.245.137.142] helo=mindspring.com)
	by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128)
	(Exim 3.33 #1)
	id 18sVzL-0003nI-00; Mon, 10 Mar 2003 14:43:20 -0800
Message-ID: <3E6D14B9.B66070E@mindspring.com>
Date: Mon, 10 Mar 2003 14:42:01 -0800
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Andrew J Caines <A.J.Caines@halplant.com>
Cc: hackers@FreeBSD.org
Subject: Re: mount_null evil ?
References: <20030310132402.GA93784@LF.net> <20030310213213.GE87518@hal9000.halplant.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a43a12c1fed3604dea81dab34d2bf979c13ca473d225a0f487350badd9bab72f9c350badd9bab72f9c
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Andrew J Caines wrote:
> > I?m currently developing a jail-management solution - I use a
> > readonly mount_null for central software-management of the jails.
> > The manpage was written May 1, 1995 - is using this tool still dangerous
> 
> I have used it for read-only mounts since way back and have not have any
> problems, including brief periods of high I/O.
> 
> I'd have reservations allowing unique data on a read-write mount, however
> I just did a few quick and simple tests of reads and writes on a rw null
> mount on my 4.8-RC box with no apparent problem.

R/O is fine.

R/W is a problem because there are explicit coherency problems
when stacking vnodes.  That's because each vnode has an associated
"struct vm_object *v_object" which is the backing store object.

When you stack vnodes, because of this, then it's possible, as a
result of mmap'ed I/O, that the top object in the stack will not
have the same data as the backing object in the underlying FS.

The nullfs code trys to avoid this (see null_getvobject()), but
there are certain places where, in a non-unified VM and buffer
cache implementation, previously, where there would be explicit
coherency enforced.  For this to work, you effectively need to
put back in the explicit coherency cycles that were removed in
the VM and buffer cache unification.  Actually, it was this set
of changes that make LFS no longer work on FreeBSD, as well.

One place where this is obviously problematic is the first call
to VOP_GETVOBJECT() in vinvalbuf() in /sys/kern/vfs_subr.c (see
the "XXX" block comment before the "do" loop).

Basically, to clean this up, you would need to implement both
getpages() and putpages() that used the read/write path, and
did explicit copies between the upper and lower objects.

Technically, you'd think that the VOP_GETVOBJECT() would be
enough to take care of this -- which is almost true, for a
linear mapping of uppr pages to lower pages, but definitely
not true for a translation mapping or an offset mapping or a
scatter mapping, but... there are still explicit references
to vp->v_object in various places (e.g. vlrureclaim(), and
vop_stdcreatevobject(), etc.) that should instead be calling
VOP_GETVOBJECT().

As long as you don't do R/W, though, read-through coherency
is pretty much guaranteed, as long as the underlying FS that
is being mounted over is also R/O (i.e. there are no notifications
up the stack for changes to the underlying FS; thus any cached
data in the upper layer v_object, if referenced by one of those
routines directly, instead of getting the underlying v_object,
could contain stale data).

-- Terry

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


From owner-freebsd-hackers  Mon Mar 10 15:16: 4 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D03E837B401
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 15:16:02 -0800 (PST)
Received: from stone.locallink.net (Stone.LocalLink.Net [65.170.77.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3F3EC43F3F
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 15:16:01 -0800 (PST)
	(envelope-from kpitcher@locallink.net)
Received: from 65.170.77.2 (av.LocalLink.Net [65.170.77.8])
	by viruscanner.locallink.net (Postfix) with SMTP id 64D2641C1A
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 18:16:01 -0500 (EST)
Received: by stone.locallink.net (Postfix, from userid 1001)
	id 69D3D41C69; Mon, 10 Mar 2003 18:16:00 -0500 (EST)
Date: Mon, 10 Mar 2003 18:16:00 -0500
From: Keith Pitcher <kpitcher@locallink.net>
To: freebsd-hackers@freebsd.org
Subject: redirect everything to socks5
Message-ID: <20030310231600.GA62069@stone.locallink.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.1i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


Living in rural slow connection land, I've been playing around with
satellite Internet. The problem is the company only has Win
drivers. (Linux driver is in the works, but no plans to open source it, will be
released as a binary - the bastards)

Anyhow, to get the download speed of the satellite it uses a http proxy and
a socks5 proxy. This works fine for things that allow proxies or socks. But
there are a lot of things that don't support it.

Is there a way to "socksify" everything my freebsd box does, so no
matter what I do, I can just point it to the socks machine and it works?

Would also be handy to have a way to "socksify" the box when it acts as a
network gateway, so I'd only have one really strangely configured machine and
the rest would be normal.

Thanks,

Keith


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


From owner-freebsd-hackers  Mon Mar 10 16:27:48 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6B38E37B401; Mon, 10 Mar 2003 16:27:46 -0800 (PST)
Received: from smtp-relay.omnis.com (smtp-relay.omnis.com [216.239.128.27])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id DCA0D43FD7; Mon, 10 Mar 2003 16:27:45 -0800 (PST)
	(envelope-from wes@softweyr.com)
Received: from softweyr.homeunix.net (66-75-151-22.san.rr.com [66.75.151.22])
	by smtp-relay.omnis.com (Postfix) with ESMTP
	id BCA904346D; Mon, 10 Mar 2003 16:27:44 -0800 (PST)
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr
To: Doug Barton <DougB@FreeBSD.org>, dslb@tiscali.dk
Subject: Re: Insecure PHP installation?
Date: Mon, 10 Mar 2003 16:27:44 -0800
User-Agent: KMail/1.5
Cc: hackers@freebsd.org
References: <3E4A9619000044DD@cpfe2.be.tisc.dk> <20030310105901.L11058@znfgre.tberna.bet>
In-Reply-To: <20030310105901.L11058@znfgre.tberna.bet>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200303101627.44459.wes@softweyr.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Monday 10 March 2003 10:59, Doug Barton wrote:
> On Mon, 10 Mar 2003 dslb@tiscali.dk wrote:
> > Hi all
> >
> > I know PHP is not in the base system, but I thought I could ask here
> > anyway.
>
> You should have asked this on freebsd-ports@freebsd,org, and cc'ed the
> PHP maintainer, FYI.
>
> > I have installed PHP on my FreeBSD 4.7 computer and did a "find /
> > -perm +0002". I could see that /usr/local/bin/pear is a script and
> > world writable, isn't that a little dangerous?
>
> That's definitely bad, yes. Please use send-pr to file a problem report
> about this.

I have PHP installed from the port on my system:

-bash-2.05b$ pkg_info | grep php
mod_php4-4.2.3      PHP4 module for Apache

It does not seem to exhibit this problem:

-bash-2.05b$ ls -l /usr/local/bin/pear
-rwxr-xr-x  1 root  wheel  5957 Dec 21 18:01 /usr/local/bin/pear

Did you install from the package?  If not, why not?  If so, is your 
package different from mine or has your installation been changed after 
the fact?

-- 

        Where am I, and what am I doing in this handbasket?

Wes Peters                                               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  Mon Mar 10 16:34:24 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3271A37B404; Mon, 10 Mar 2003 16:34:23 -0800 (PST)
Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5CB5843FDF; Mon, 10 Mar 2003 16:34:21 -0800 (PST)
	(envelope-from DougB@freebsd.org)
Received: from 12-234-22-23.client.attbi.com ([12.234.22.23])
          by rwcrmhc52.attbi.com (rwcrmhc52) with SMTP
          id <20030311003420052003s5aae>; Tue, 11 Mar 2003 00:34:20 +0000
Date: Mon, 10 Mar 2003 16:34:20 -0800 (PST)
From: Doug Barton <DougB@FreeBSD.org>
To: Wes Peters <wes@softweyr.com>
Cc: dslb@tiscali.dk, dirk@freebsd.org, hackers@freebsd.org
Subject: Re: Insecure PHP installation?
In-Reply-To: <200303101627.44459.wes@softweyr.com>
Message-ID: <20030310163120.A55907@12-234-22-23.pyvrag.nggov.pbz>
References: <3E4A9619000044DD@cpfe2.be.tisc.dk> <20030310105901.L11058@znfgre.tberna.bet>
 <200303101627.44459.wes@softweyr.com>
Organization: http://www.FreeBSD.org/
X-message-flag: Outlook -- Not just for spreading viruses anymore!
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Mon, 10 Mar 2003, Wes Peters wrote:

> -bash-2.05b$ pkg_info | grep php
> mod_php4-4.2.3      PHP4 module for Apache

EANCIENTPHP

I think that the problem is specific to 4.3.x. FYI dirk, I did the 'find /
-perms +0002' myself, and php is installing a whole bunch of stuff with
world write, so this is a bigger issue than just the one script.

Doug

-- 

    This .signature sanitized for your protection

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


From owner-freebsd-hackers  Mon Mar 10 17:28: 6 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 04EE237B404
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 17:28:05 -0800 (PST)
Received: from web14201.mail.yahoo.com (web14201.mail.yahoo.com [216.136.172.143])
	by mx1.FreeBSD.org (Postfix) with SMTP id 3520E43F85
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 17:28:04 -0800 (PST)
	(envelope-from neelnatu@yahoo.com)
Message-ID: <20030311012804.84570.qmail@web14201.mail.yahoo.com>
Received: from [208.2.250.35] by web14201.mail.yahoo.com via HTTP; Mon, 10 Mar 2003 17:28:04 PST
Date: Mon, 10 Mar 2003 17:28:04 -0800 (PST)
From: Neelkanth Natu <neelnatu@yahoo.com>
Subject: Re: divert socket
To: Ferruccio Vitale <freebsd@cs.tin.it>, freebsd-hackers@freebsd.org
In-Reply-To: <20030310092032.2fc71b8d.freebsd@cs.tin.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

--- Ferruccio Vitale <freebsd@cs.tin.it> wrote:
> 
> I try to explain better my problem: when my daemon tries to read from this socket, recv tells me
> it read 68 bytes, for example, which is about message size at application layer, but what I read
> is not I expect (string without sense). Is there a particular way to read from a raw socket or a
> divert socket?

Take a look at the tcpmssd code in the ports/net collection. In a nutshell, the data that
is read from the divert socket contains the IP header, typically followed by the TCP/UDP header,
followed by the application data.
http://www.freebsd.org/cgi/pds.cgi?ports/net/tcpmssd
http://www.freebsd.org/cgi/url.cgi?ports/net/tcpmssd/pkg-descr

best
Neel

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


__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

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


From owner-freebsd-hackers  Mon Mar 10 19: 2:27 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A31C037B401
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 19:02:26 -0800 (PST)
Received: from vlk.dyndns.org (BSN-77-9-161.dsl.siol.net [193.77.9.161])
	by mx1.FreeBSD.org (Postfix) with SMTP id E74E243FAF
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 19:02:24 -0800 (PST)
	(envelope-from borut@vlk.dyndns.org)
Received: (qmail 2309 invoked from network); 11 Mar 2003 03:02:23 -0000
Received: from borut3.vlk.local (10.10.10.10)
  by 0 with SMTP; 11 Mar 2003 03:02:23 -0000
Subject: Freebsd 5.0-RELEASE & named pipes
From: Borut Kurnik <borut@vlk.dyndns.org>
To: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 11 Mar 2003 04:04:06 +0100
Message-Id: <1047351847.17228.27.camel@borut3>
Mime-Version: 1.0
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hi!

I installed FreeBSD 5.0-RELEASE (generic kernel).

When I try to direct stream to a named pipe, I get:

Resource temporarily unavailable.

[root@bart root]# mkfifo f; find /etc > f &
[1] 2200
[root@bart root]# -bash: f: Resource temporarily unavailable

???

Thanks,

Borut



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


From owner-freebsd-hackers  Mon Mar 10 19:20:30 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A7FC337B401
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 19:20:28 -0800 (PST)
Received: from vlk.dyndns.org (BSN-77-9-161.dsl.siol.net [193.77.9.161])
	by mx1.FreeBSD.org (Postfix) with SMTP id B524E43F75
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 19:20:26 -0800 (PST)
	(envelope-from borut@vlk.dyndns.org)
Received: (qmail 2396 invoked from network); 11 Mar 2003 03:20:24 -0000
Received: from borut3.vlk.local (10.10.10.10)
  by 0 with SMTP; 11 Mar 2003 03:20:24 -0000
Subject: Re: Freebsd 5.0-RELEASE & named pipes
From: Borut Kurnik <borut@vlk.dyndns.org>
To: Lyndon Nerenberg {VE6BBM} <lyndon@orthanc.ab.ca>
Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org
In-Reply-To: <200303110310.h2B3AvKU025877@orthanc.ab.ca>
References: <200303110310.h2B3AvKU025877@orthanc.ab.ca>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 11 Mar 2003 04:22:08 +0100
Message-Id: <1047352928.17186.35.camel@borut3>
Mime-Version: 1.0
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hi!

The system doesn't wait for me to open the reader, I get the message 
instantly.

I worked on 4.7 & still does (also on linux, netbsd, ... :-) )

This is NetBSD 1.6 

[root@himler root]# echo "test" > f &
[1] 2383
[root@himler root]# cat < f
test
[1]+  Done                    echo "test" >f


And this is FreeBSD 5.0

[root@bart root]# echo "test" > f  &
[1] 2436
[root@bart root]# -bash: f: Resource temporarily unavailable

[1]+  Exit 1                  echo "test" >f

Borut


On Tue, 2003-03-11 at 04:10, Lyndon Nerenberg {VE6BBM} wrote:
> >[root@bart root]# mkfifo f; find /etc > f &
> >[1] 2200
> >[root@bart root]# -bash: f: Resource temporarily unavailable
> 
> You need a reader on the other side of the FIFO.



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


From owner-freebsd-hackers  Mon Mar 10 19:41:30 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AADF437B401
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 19:41:29 -0800 (PST)
Received: from toscano.org (ip68-100-184-64.nv.nv.cox.net [68.100.184.64])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D281143F85
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 19:41:28 -0800 (PST)
	(envelope-from pete@toscano.org)
Received: from bubba.toscano.org (localhost.localdomain [127.0.0.1])
	by bubba.toscano.org (8.12.8/8.12.8) with ESMTP id h2B3f8xH002267;
	Mon, 10 Mar 2003 22:41:08 -0500
Received: (from pete@localhost)
	by bubba.toscano.org (8.12.8/8.12.5/Submit) id h2B3f3bZ002265;
	Mon, 10 Mar 2003 22:41:03 -0500
Date: Mon, 10 Mar 2003 22:41:03 -0500
From: Pete <pete-freebsd-hackers@toscano.org>
To: Soeren Schmidt <sos@spider.deepcore.dk>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: 3 IDE devices on Promise card + FreeBSD == not possible?
Message-ID: <20030311034103.GC1912@bubba.toscano.org>
Mail-Followup-To: Soeren Schmidt <sos@spider.deepcore.dk>,
	freebsd-hackers@FreeBSD.ORG
References: <xzpfzpvbk2g.fsf@flood.ping.uio.no> <200303101030.h2AAUE9r095348@spider.deepcore.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200303101030.h2AAUE9r095348@spider.deepcore.dk>
X-Unexpected: The Spanish Inquisition
User-Agent: Mutt/1.5.3i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Mon, 10 Mar 2003, Søren Schmidt wrote:

> No, thats not the case, the ATA driver has a built in RAID engine
> to use with Promise and HighPoint controllers. The reason it is
> like this is that it is nessesary to read the RAID config off the
> disks in a vendor specific way, and neither of cdd/vinum could do
> this when its was done.

So, if I were to create the RAID-1 volume with atacontrol, I'm tied to
using the Promise controller?  Could I move the drives to a
Highpoint-based controller or just a plain on-board ATA interface and
still have the RAID volume accessible?  If I want this kind of
flexibility, should I move to Vinum?

Thanks again for taking the time to clear all of this up.  I really
appreciate it.

pete

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


From owner-freebsd-hackers  Mon Mar 10 19:46:19 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id A615A37B404; Mon, 10 Mar 2003 19:46:17 -0800 (PST)
Received: from smtp.acd.net (smtp.acd.net [207.179.102.146])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id DB52543F75; Mon, 10 Mar 2003 19:46:16 -0800 (PST)
	(envelope-from taxman@ACD.NET)
Received: from modem22.nas4.acd.net ([207.179.85.218]) by smtp.acd.net with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 10 Mar 2003 22:46:10 -0500
From: taxman <taxman@acd.net>
To: Borut Kurnik <borut@vlk.dyndns.org>,
	Lyndon Nerenberg {VE6BBM} <lyndon@orthanc.ab.ca>
Subject: Re: Freebsd 5.0-RELEASE & named pipes
Date: Mon, 10 Mar 2003 22:42:55 -0500
User-Agent: KMail/1.5
Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org
References: <200303110310.h2B3AvKU025877@orthanc.ab.ca> <1047352928.17186.35.camel@borut3>
In-Reply-To: <1047352928.17186.35.camel@borut3>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200303102242.55347.taxman@acd.net>
X-OriginalArrivalTime: 11 Mar 2003 03:46:10.0654 (UTC) FILETIME=[C16977E0:01C2E780]
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Monday 10 March 2003 10:22 pm, Borut Kurnik wrote:
> Hi!
>
> The system doesn't wait for me to open the reader, I get the message
> instantly.
>
> I worked on 4.7 & still does (also on linux, netbsd, ... :-) )

Ok then you may want to either use 4.7, or upgrade to -current and see how it 
does there.  If you still get an error, the best place to ask would be on the 
-current mailing list.  5.0-release was not meant as a production release.

Tim



as an aside, yes Mike, I'll get the FAQ writeup to you.





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


From owner-freebsd-hackers  Mon Mar 10 19:51: 8 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 33AA937B401; Mon, 10 Mar 2003 19:51:07 -0800 (PST)
Received: from midway.uchicago.edu (midway.uchicago.edu [128.135.12.12])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 9FC0D43FBF; Mon, 10 Mar 2003 19:51:05 -0800 (PST)
	(envelope-from dsyphers@uchicago.edu)
Received: from adsl-68-20-34-135.dsl.chcgil.ameritech.net (adsl-68-20-34-135.dsl.chcgil.ameritech.net [68.20.34.135])
	by midway.uchicago.edu (8.12.8/8.12.5) with ESMTP id h2B3p4LJ019927;
	Mon, 10 Mar 2003 21:51:04 -0600 (CST)
From: David Syphers <dsyphers@uchicago.edu>
To: Borut Kurnik <borut@vlk.dyndns.org>
Subject: Re: Freebsd 5.0-RELEASE & named pipes
Date: Mon, 10 Mar 2003 21:51:05 -0600
User-Agent: KMail/1.5
Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG
References: <200303110310.h2B3AvKU025877@orthanc.ab.ca> <1047352928.17186.35.camel@borut3>
In-Reply-To: <1047352928.17186.35.camel@borut3>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200303102151.05046.dsyphers@uchicago.edu>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Monday 10 March 2003 09:22 pm, Borut Kurnik wrote:
> I worked on 4.7 & still does (also on linux, netbsd, ... :-) )
>
> This is NetBSD 1.6
>
> [root@himler root]# echo "test" > f &
> [1] 2383
> [root@himler root]# cat < f
> test
> [1]+  Done                    echo "test" >f
>
>
> And this is FreeBSD 5.0
>
> [root@bart root]# echo "test" > f  &
> [1] 2436
> [root@bart root]# -bash: f: Resource temporarily unavailable
>
> [1]+  Exit 1                  echo "test" >f

This works fine on my system, which is -current from March 2, using both tcsh 
and bash. But since bash is not the default shell, but a port, isn't this 
dependent on the version of the port you have installed rather than the OS? I 
have bash-2.05b.004.

-David

-- 
http://www.seektruth.org

Astronomy and Astrophysics Center
The University of Chicago

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


From owner-freebsd-hackers  Mon Mar 10 19:58:30 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8482037B401
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 19:58:28 -0800 (PST)
Received: from vlk.dyndns.org (BSN-77-9-161.dsl.siol.net [193.77.9.161])
	by mx1.FreeBSD.org (Postfix) with SMTP id C954943FBD
	for <freebsd-hackers@freebsd.org>; Mon, 10 Mar 2003 19:58:26 -0800 (PST)
	(envelope-from borut@vlk.dyndns.org)
Received: (qmail 2516 invoked from network); 11 Mar 2003 03:58:24 -0000
Received: from borut3.vlk.local (10.10.10.10)
  by 0 with SMTP; 11 Mar 2003 03:58:24 -0000
Subject: Re: Freebsd 5.0-RELEASE & named pipes
From: Borut Kurnik <borut@vlk.dyndns.org>
To: David Syphers <dsyphers@uchicago.edu>
Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org
In-Reply-To: <200303102151.05046.dsyphers@uchicago.edu>
References: <200303110310.h2B3AvKU025877@orthanc.ab.ca>
	<1047352928.17186.35.camel@borut3> 
	<200303102151.05046.dsyphers@uchicago.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 11 Mar 2003 05:00:09 +0100
Message-Id: <1047355209.17228.42.camel@borut3>
Mime-Version: 1.0
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

bash-2.05b.004 here too. But -current might help.

Borut

On Tue, 2003-03-11 at 04:51, David Syphers wrote:
> On Monday 10 March 2003 09:22 pm, Borut Kurnik wrote:
> > I worked on 4.7 & still does (also on linux, netbsd, ... :-) )
> >
> > This is NetBSD 1.6
> >
> > [root@himler root]# echo "test" > f &
> > [1] 2383
> > [root@himler root]# cat < f
> > test
> > [1]+  Done                    echo "test" >f
> >
> >
> > And this is FreeBSD 5.0
> >
> > [root@bart root]# echo "test" > f  &
> > [1] 2436
> > [root@bart root]# -bash: f: Resource temporarily unavailable
> >
> > [1]+  Exit 1                  echo "test" >f
> 
> This works fine on my system, which is -current from March 2, using both tcsh 
> and bash. But since bash is not the default shell, but a port, isn't this 
> dependent on the version of the port you have installed rather than the OS? I 
> have bash-2.05b.004.
> 
> -David
> 
> -- 
> http://www.seektruth.org
> 
> Astronomy and Astrophysics Center
> The University of Chicago
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message



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


From owner-freebsd-hackers  Mon Mar 10 21: 2:51 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DD68B37B401
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 21:02:49 -0800 (PST)
Received: from smtp-relay.omnis.com (smtp-relay.omnis.com [216.239.128.27])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C4CBC43F75
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 10 Mar 2003 21:02:48 -0800 (PST)
	(envelope-from wes@softweyr.com)
Received: from softweyr.homeunix.net (66-75-151-22.san.rr.com [66.75.151.22])
	by smtp-relay.omnis.com (Postfix) with ESMTP
	id 77B8343425; Mon, 10 Mar 2003 21:02:36 -0800 (PST)
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr
To: Doug Ambrisko <ambrisko@ambrisko.com>
Subject: Re: Realtek
Date: Mon, 10 Mar 2003 21:02:33 -0800
User-Agent: KMail/1.5
Cc: freebsd-hackers@FreeBSD.ORG
References: <200303101647.h2AGl3ng028761@www.ambrisko.com>
In-Reply-To: <200303101647.h2AGl3ng028761@www.ambrisko.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200303102102.33694.wes@softweyr.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Monday 10 March 2003 08:47, Doug Ambrisko wrote:
>
> Hmm, I thought I had said "benchmark in your environment".  We have a
> closed box that is sort-of a router and a bridge.  So your only inputs
> is really network traffic.  That is what we tune the box for.  So it
> would be interesting to see you kill it in 1s.  Again our issue is PCI
> bus.

Flood it with wire speed 64-byte packets and drive it into receive 
interrupt livelock.  Yup, the PCI bus is (most of) the problem here too.

-- 

        Where am I, and what am I doing in this handbasket?

Wes Peters                                               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  Tue Mar 11  4:28:34 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4F4AC37B401
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 11 Mar 2003 04:28:33 -0800 (PST)
Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0B5F143F3F
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 11 Mar 2003 04:28:19 -0800 (PST)
	(envelope-from sos@spider.deepcore.dk)
Received: (from sos@localhost)
	by spider.deepcore.dk (8.12.8/8.12.8) id h2BCSGVI007922;
	Tue, 11 Mar 2003 13:28:16 +0100 (CET)
	(envelope-from sos)
From: Soeren Schmidt <sos@spider.deepcore.dk>
Message-Id: <200303111228.h2BCSGVI007922@spider.deepcore.dk>
Subject: Re: 3 IDE devices on Promise card + FreeBSD == not possible?
In-Reply-To: <20030311034103.GC1912@bubba.toscano.org>
To: Pete <pete-freebsd-hackers@toscano.org>
Date: Tue, 11 Mar 2003 13:28:16 +0100 (CET)
Cc: freebsd-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL98b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=ISO-8859-1
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

It seems Pete wrote:
> On Mon, 10 Mar 2003, Søren Schmidt wrote:
> 
> > No, thats not the case, the ATA driver has a built in RAID engine
> > to use with Promise and HighPoint controllers. The reason it is
> > like this is that it is nessesary to read the RAID config off the
> > disks in a vendor specific way, and neither of cdd/vinum could do
> > this when its was done.
> 
> So, if I were to create the RAID-1 volume with atacontrol, I'm tied to
> using the Promise controller?  Could I move the drives to a
> Highpoint-based controller or just a plain on-board ATA interface and
> still have the RAID volume accessible?  If I want this kind of
> flexibility, should I move to Vinum?

If you want to boot from the array you need to have the array config
in a way that fits the controller, if thats not needed you can move
around as you see fit, you can even make ATA RAID's on any ATA controller
not just Promise or Highpoint as loong as you wont boot from it.
I guess I should make an option to atacontrol that can convert between
HPT/Promise format or maybe just silently write both to the disks ;)

-Søren

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


From owner-freebsd-hackers  Tue Mar 11  4:54:59 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 96EAF37B401
	for <freebsd-hackers@freebsd.org>; Tue, 11 Mar 2003 04:54:58 -0800 (PST)
Received: from mail.com (ip-46-161-97-218.anlai.com [218.97.161.46])
	by mx1.FreeBSD.org (Postfix) with SMTP id 076BE43F3F
	for <freebsd-hackers@freebsd.org>; Tue, 11 Mar 2003 04:54:56 -0800 (PST)
	(envelope-from jinmai-sp@163.com)
From: "jinmai" <jinmai-sp@163.com>
To: freebsd-hackers@freebsd.org
Subject: ¾ÍµÈÄãÁË£¡
Mime-Version: 1.0
Content-Type: text/html; charset="gb2312"
Date: Tue, 11 Mar 2003 20:52:48
Message-Id: <20030311125456.076BE43F3F@mx1.FreeBSD.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

<html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
<title>New Page 1</title>
</head>

<body>

<p align="center"><a href="http://www.95168.com.cn"><img border="0" src="http://sms.95169.net/voicechat/a01.jpg" width="556" height="600"></a></p>

</body>

</html>

<p align="center"><span style="background-color: #FFFFFF"><font color="#FF0000" size="2">
-----------------------------------------------------------------</br>
<a href=http://www.kldns.net>200MÐéÄâÖ÷»ú+50MÆóÒµÓʾÖ+¶¥¼¶¹ú¼ÊÓòÃû  Ö»Ðè189Ôª/Äê</a></br>
<a href=http://www.cnkl.net>¹ú¼ÊÓ¢ÎÄÓòÃû 79Ôª/Äê  Ãâ·ÑÎÞÏ޴νâÎö</a></br>
»¶Ó­¹âÁÙ¿ÆÁ¦ÍøÂ磺<a href=http://www.kldns.net>http://www.kldns.net</a>  <a href=http://www.cnkl.net>http://www.cnkl.net</a></br>
-----------------------------------------------------------------</br></br>
:::::: JKLMailer PowerBy£º<a href="http://www.vrmo.com" target=_blank>www.VRMO.com</a> QQ:5009353 ::::::</br>
</font></span></p>


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


From owner-freebsd-hackers  Tue Mar 11 11:20:43 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C9FA337B401
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 11 Mar 2003 11:20:41 -0800 (PST)
Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C8CFD43F75
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 11 Mar 2003 11:20:40 -0800 (PST)
	(envelope-from ambrisko@www.ambrisko.com)
Received: from www.ambrisko.com (localhost [127.0.0.1])
	by ambrisko.com (8.12.6/8.12.6) with ESMTP id h2BJKehZ013587;
	Tue, 11 Mar 2003 11:20:40 -0800 (PST)
	(envelope-from ambrisko@www.ambrisko.com)
Received: (from ambrisko@localhost)
	by www.ambrisko.com (8.12.6/8.12.6/Submit) id h2BJKaEC013582;
	Tue, 11 Mar 2003 11:20:36 -0800 (PST)
	(envelope-from ambrisko)
From: Doug Ambrisko <ambrisko@ambrisko.com>
Message-Id: <200303111920.h2BJKaEC013582@www.ambrisko.com>
Subject: Re: Realtek
In-Reply-To: <200303102102.33694.wes@softweyr.com>
To: Wes Peters <wes@softweyr.com>
Date: Tue, 11 Mar 2003 11:20:36 -0800 (PST)
Cc: freebsd-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL94b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Wes Peters writes:
| On Monday 10 March 2003 08:47, Doug Ambrisko wrote:
| > Hmm, I thought I had said "benchmark in your environment".  We have a
| > closed box that is sort-of a router and a bridge.  So your only inputs
| > is really network traffic.  That is what we tune the box for.  So it
| > would be interesting to see you kill it in 1s.  Again our issue is PCI
| > bus.
| 
| Flood it with wire speed 64-byte packets and drive it into receive 
| interrupt livelock.  Yup, the PCI bus is (most of) the problem here too.

Can't reproduce it.  Maybe they fixed it in the 8100L rev.?

I tried a ping -f -s 22 to hit it with 64 byte packets.  I also had
traffic going to the onboard gig and it wasn't impacted (granted the
source was a 100bit link tied to the gig link).

I'm running variants of -stable (FreeBSD 4.7 and later) on this hardware.

Doug A.

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


From owner-freebsd-hackers  Tue Mar 11 13:17:28 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 820A137B401
	for <hackers@freebsd.org>; Tue, 11 Mar 2003 13:17:27 -0800 (PST)
Received: from priv-edtnes09-hme0.telusplanet.net (outbound02.telus.net [199.185.220.221])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8A0A343F75
	for <hackers@freebsd.org>; Tue, 11 Mar 2003 13:17:26 -0800 (PST)
	(envelope-from sh@bel.bc.ca)
Received: from REASON ([216.232.215.209])
          by priv-edtnes09-hme0.telusplanet.net
          (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with SMTP
          id <20030311211726.DJJL26116.priv-edtnes09-hme0.telusplanet.net@REASON>
          for <hackers@freebsd.org>; Tue, 11 Mar 2003 14:17:26 -0700
Message-ID: <000601c2e813$9d849650$d1d7e8d8@slugabed.org>
From: "Sean Hamilton" <sh@bel.bc.ca>
To: <hackers@freebsd.org>
Subject: IP addresses of bridge interfaces
Date: Tue, 11 Mar 2003 13:17:25 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Greetings,

I recently upgraded a FreeBSD 4.6.2 bridge to 5.0, and am having troubles
with how it handles IP addresses.

   router
     |
     | t1
     |
   [fxp0]
FreeBSD bridge
   [fxp1]
     |
  switch
     |
   hosts

The problem is that if the external interface is assigned an address, then
hosts on the same block can't access it. Likewise if the internal interface
is given an address, *only* hosts on the same block can access it! I have
verified that in both cases the bridge has its default route correctly set.

I won't be too suprised if this is due to screwey ISP routing, but I don't
recall this ever being a problem with 4.6.2.

Any tips?

thanks,

sh


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


From owner-freebsd-hackers  Tue Mar 11 13:25:13 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 72EFB37B401
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 11 Mar 2003 13:25:12 -0800 (PST)
Received: from mailscan.binghamton.edu (mailscan.binghamton.edu [128.226.8.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 3F49043FEA
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 11 Mar 2003 13:25:11 -0800 (PST)
	(envelope-from bf20761@binghamton.edu)
Received: from bingnet2.cc.binghamton.edu(128.226.1.18) by mailscan.binghamton.edu via csmap 
	 id 20014; Tue, 11 Mar 2003 16:28:55 -0500 (EST)
Received: from bingsun2.cc.binghamton.edu (bf20761@bingsun2.cc.binghamton.edu [128.226.6.4])
	by bingnet2.cc.binghamton.edu (8.12.8/8.12.8) with ESMTP id h2BLPAIC022212
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 11 Mar 2003 16:25:10 -0500 (EST)
Date: Tue, 11 Mar 2003 16:25:10 -0500 (EST)
From: Zhihui Zhang <bf20761@binghamton.edu>
X-X-Sender: bf20761@bingsun2.cc.binghamton.edu
To: freebsd-hackers@FreeBSD.ORG
Subject: long long sysctl possible?
Message-ID: <Pine.SOL.L4.44.0303111623340.25949-100000@bingsun2.cc.binghamton.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


Hi,

I notice that the SYSCTL_INT() only support integer. Is there a support of
things like 64-bit SYSCTL_LONGLONG()?  If so, where is the sample code?
Thanks.

-Zhihui

-- 



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


From owner-freebsd-hackers  Tue Mar 11 13:30:38 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0F13137B401
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 11 Mar 2003 13:30:36 -0800 (PST)
Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6E7DD43FD7
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 11 Mar 2003 13:30:35 -0800 (PST)
	(envelope-from brdavis@odin.ac.hmc.edu)
Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1])
	by odin.ac.hmc.edu (8.12.3/8.12.3) with ESMTP id h2BLUIJu016212;
	Tue, 11 Mar 2003 13:30:18 -0800
Received: (from brdavis@localhost)
	by odin.ac.hmc.edu (8.12.3/8.12.3/Submit) id h2BLUIV0016211;
	Tue, 11 Mar 2003 13:30:18 -0800
Date: Tue, 11 Mar 2003 13:30:18 -0800
From: Brooks Davis <brooks@one-eyed-alien.net>
To: Zhihui Zhang <bf20761@binghamton.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: long long sysctl possible?
Message-ID: <20030311133018.A15519@Odin.AC.HMC.Edu>
References: <Pine.SOL.L4.44.0303111623340.25949-100000@bingsun2.cc.binghamton.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
	protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw"
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.SOL.L4.44.0303111623340.25949-100000@bingsun2.cc.binghamton.edu>; from bf20761@binghamton.edu on Tue, Mar 11, 2003 at 04:25:10PM -0500
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


--wac7ysb48OaltWcw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 11, 2003 at 04:25:10PM -0500, Zhihui Zhang wrote:
>=20
> I notice that the SYSCTL_INT() only support integer. Is there a support of
> things like 64-bit SYSCTL_LONGLONG()?  If so, where is the sample code?
> Thanks.

A quick look at sys/sysctl.h shows that there's a type CTLTYPE_QUAD, but
not SYSCTL_QUAD or SYSCTL_INT64 macro.  You could add such a macro quite
easily though.

-- Brooks

--=20
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4

--wac7ysb48OaltWcw
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+blVpXY6L6fI4GtQRAiNhAKDalUG4NTgSmJQDGfz0d4RXDIrCzACg1QPk
3DMn6rbB+tM3yaHmu47PFxg=
=wrhQ
-----END PGP SIGNATURE-----

--wac7ysb48OaltWcw--

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


From owner-freebsd-hackers  Tue Mar 11 16:53:10 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AD2FF37B401
	for <hackers@freebsd.org>; Tue, 11 Mar 2003 16:53:08 -0800 (PST)
Received: from cocono.com.tw (170-142.kingnet.net.tw [61.57.170.142])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6D85C440B3
	for <hackers@freebsd.org>; Tue, 11 Mar 2003 16:52:35 -0800 (PST)
	(envelope-from ibenz@cocono.com.tw)
From: acom@cm.com.tw
To: hackers@freebsd.org
Subject: =?ISO-8859-1?B?pOmxYKXOq36kV7r0wco=?=
Reply-To: com@cc.com.tw
Date: 12 Mar 2003 08:51:16 +0800
MIME-Version: 1.0
Content-Type: text/html
Content-Transfer-Encoding: 8bit
Message-Id: <20030312005236.6D85C440B3@mx1.FreeBSD.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

<html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=big5">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>±z¦³¤U¦C¯S½è¶Ü</title>
</head>

<body>

<table width="600" border="0">
  <tbody>
    <tr>
      <td width="100%" bgColor="#ffccff"><font size="6"><b><a href="home.kimo.com.tw/amity508"><span style="BACKGROUND-COLOR: #ffccff">
        <marquee>«lÃz¡I¡I¾_¾Ù¡I¡I</marquee>
        </span></a></b></font></td>
    </tr>
    <tr>
      <td width="100%" bgColor="#ff9933"><font color="#800000" size="3"><b>±z¦³¤U¦C¯S½è¶Ü¡H</b></font></td>
    </tr>
    <tr>
      <td width="100%" bgColor="#ffcc00"><b><font color="#cc0000" size="5"><a href="http://home.kimo.com.tw/amity508">1.¨Æ·~¥ø¹Ï¤ß</a></font></b></td>
    </tr>
    <tr>
      <td width="100%" bgColor="#ffcc00"><b><font color="#cc0000" size="5"><a href="http://home.kimo.com.tw/amity508">2.¤£¥Ì¤ß¥­¤Z</a></font></b></td>
    </tr>
    <tr>
      <td width="100%" bgColor="#ffcc00"><b><font color="#cc0000" size="5"><a href="http://home.kimo.com.tw/amity508">3.¤£º¡©ó²{ª¬</a></font></b></td>
    </tr>
    <tr>
      <td width="100%" bgColor="#ffcc00"><b><font color="#cc0000" size="5"><a href="http://home.kimo.com.tw/amity508">4.«i©ó­±¹ï¥¼¨Ó</a></font></b></td>
    </tr>
    <tr>
      <td width="100%" bgColor="#ff9933"><b><font color="#800000">¥u­n±z¾Ö¦³¤W¦C¯S½è¡A§Ú­Ì±N<a href="http://home.kimo.com.tw/amity508"><font size="4">§K¶O°ö°V</font></a>±z©Ò¦³¬ÛÃö§Þ¾¯à¤O¡A´£¨Ñ±zµ²¦Xºô¸ô¡B¹êÅé¡A­¹¦ç¦í¦æ¡B   
        ¦Y³Üª±¼Öªº<a href="http://home.kimo.com.tw/amity508"><font size="4">³q¸ô¨Æ·~</font></a>¡I<a href="http://home.kimo.com.tw/amity508"><font size="4">ÂI¿ï§Ú</font></a>¡A±z´N¥i¥H±o¨ì¡I<br>
        ps:±N·|¦³±M¤H¬°±z¸Ô²Ó¸Ñ»¡³á¡I</font></b></td>
    </tr>
    <tr>
      <td width="100%" bgColor="#ffcc00"><span style="BACKGROUND-COLOR: #ffff00"><a href="http://home.kimo.com.tw/amity508"><img src="104_banner.gif" border="0" width="468" height="60"></a>  
        <a href="http://home.kimo.com.tw/amity508"><img src="AD1.gif" border="0" width="120" height="60"></a></span></td> 
    </tr>
  </tbody>
</table>

</body>

</html>



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


From owner-freebsd-hackers  Tue Mar 11 22:44:41 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 27F9A37B404
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 11 Mar 2003 22:44:40 -0800 (PST)
Received: from cirb503493.alcatel.com.au (c18609.belrs1.nsw.optusnet.com.au [210.49.80.204])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9091343F3F
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 11 Mar 2003 22:44:38 -0800 (PST)
	(envelope-from peterjeremy@optushome.com.au)
Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])
	by cirb503493.alcatel.com.au (8.12.6/8.12.5) with ESMTP id h2C6iRiM006464;
	Wed, 12 Mar 2003 17:44:27 +1100 (EST)
	(envelope-from jeremyp@cirb503493.alcatel.com.au)
Received: (from jeremyp@localhost)
	by cirb503493.alcatel.com.au (8.12.6/8.12.5/Submit) id h2C6iPrI006463;
	Wed, 12 Mar 2003 17:44:25 +1100 (EST)
Date: Wed, 12 Mar 2003 17:44:25 +1100
From: Peter Jeremy <peterjeremy@optushome.com.au>
To: Doug Ambrisko <ambrisko@ambrisko.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Realtek
Message-ID: <20030312064424.GB6336@cirb503493.alcatel.com.au>
References: <200303102102.33694.wes@softweyr.com> <200303111920.h2BJKaEC013582@www.ambrisko.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200303111920.h2BJKaEC013582@www.ambrisko.com>
User-Agent: Mutt/1.4i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Tue, Mar 11, 2003 at 11:20:36AM -0800, Doug Ambrisko wrote:
>Wes Peters writes:
>| Flood it with wire speed 64-byte packets and drive it into receive 
>| interrupt livelock.  Yup, the PCI bus is (most of) the problem here too.
>
>Can't reproduce it.  Maybe they fixed it in the 8100L rev.?
>
>I tried a ping -f -s 22 to hit it with 64 byte packets.  I also had
>traffic going to the onboard gig and it wasn't impacted (granted the
>source was a 100bit link tied to the gig link).

Are you sure you were generating "wire speed" packets - this is about
200,000 packets/sec at Fast speed.  "ping -f" runs at whatever rate
the remote end returns the packets at (or 100pps) - since it (mostly)
waits for a response before sending another packet, you will never see
livelock.

In order to get 200,000 pps, you're going to need 5-10 hosts
generating traffic, each with a good NIC and connected to the test
system via a decent switch.  You also need a proper network
benchmarking tool - netperf (ports/netperf) or similar rather than
ping. 

Peter

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


From owner-freebsd-hackers  Wed Mar 12  0:37:22 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9570C37B401
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 00:37:21 -0800 (PST)
Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 00EB743F3F
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 00:37:21 -0800 (PST)
	(envelope-from rizzo@xorpc.icir.org)
Received: from xorpc.icir.org (localhost [127.0.0.1])
	by xorpc.icir.org (8.12.3/8.12.3) with ESMTP id h2C8bEAq075548;
	Wed, 12 Mar 2003 00:37:14 -0800 (PST)
	(envelope-from rizzo@xorpc.icir.org)
Received: (from rizzo@localhost)
	by xorpc.icir.org (8.12.3/8.12.3/Submit) id h2C8bEWT075547;
	Wed, 12 Mar 2003 00:37:14 -0800 (PST)
	(envelope-from rizzo)
Date: Wed, 12 Mar 2003 00:37:14 -0800
From: Luigi Rizzo <rizzo@icir.org>
To: Peter Jeremy <peterjeremy@optushome.com.au>
Cc: Doug Ambrisko <ambrisko@ambrisko.com>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: Realtek
Message-ID: <20030312003713.A74419@xorpc.icir.org>
References: <200303102102.33694.wes@softweyr.com> <200303111920.h2BJKaEC013582@www.ambrisko.com> <20030312064424.GB6336@cirb503493.alcatel.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030312064424.GB6336@cirb503493.alcatel.com.au>; from peterjeremy@optushome.com.au on Wed, Mar 12, 2003 at 05:44:25PM +1100
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Wed, Mar 12, 2003 at 05:44:25PM +1100, Peter Jeremy wrote:
...
> Are you sure you were generating "wire speed" packets - this is about
> 200,000 packets/sec at Fast speed.  "ping -f" runs at whatever rate

148,800kpps

> In order to get 200,000 pps, you're going to need 5-10 hosts
> generating traffic, each with a good NIC and connected to the test

one is enough as long as it is sufficiently fast (750MHz and above
in my experiments), you use a C program to call sendto() and
generate UDP packets, and your network card can cope with the
outgoing traffic (e.g. there is no way the 'fxp' can transmit
over ~120kpps no matter how fast the CPU is; 'xl' and several 'dc'
supported chips can do the job. Haven't tried other cards.

Using polling on the sender side helps but it is not
fundamental.

	cheers
	luigi

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


From owner-freebsd-hackers  Wed Mar 12  4:59:36 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9457537B401
	for <hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 04:59:33 -0800 (PST)
Received: from x12.dk (xforce.dk [80.62.90.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B74B343F75
	for <hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 04:59:31 -0800 (PST)
	(envelope-from xride@x12.dk)
Received: from x12.dk (xride@localhost [127.0.0.1])
	by x12.dk (8.12.8/8.12.8) with ESMTP id h2CCxnkI079896;
	Wed, 12 Mar 2003 13:59:50 +0100 (CET)
	(envelope-from xride@x12.dk)
Received: from localhost (xride@localhost)
	by x12.dk (8.12.8/8.12.8/Submit) with ESMTP id h2CCxnTY079893;
	Wed, 12 Mar 2003 13:59:49 +0100 (CET)
Date: Wed, 12 Mar 2003 13:59:32 +0100 (CET)
From: Soeren Straarup <xride@x12.dk>
To: Sean Hamilton <sh@bel.bc.ca>
Cc: hackers@FreeBSD.ORG
Subject: Re: IP addresses of bridge interfaces
In-Reply-To: <000601c2e813$9d849650$d1d7e8d8@slugabed.org>
Message-ID: <20030312134116.G56904-100000@x12.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi

I had the same problem.
My solution was to add 'gateway_enable=3D"YES"' to my /etc/rc.conf
I don't know if that is the right way.. but it works.
I also had trouble getting the ip address set at boot time and had
to make a script that did that.

I would like to hear about any other ways to do it.

Best regards S=F8ren

*--------------------------------------------------------------------------=
-*
| Soeren Straarup                        Mobile: +45 20 27 62 44           =
 |
| FreeBSD wannabe since 2.2.6-R          http://xride.x12.dk               =
 |
| Also running OpenBSD and NetBSD                                          =
 |
*--------------------------------------------------------------------------=
-*

On Tue, 11 Mar 2003, Sean Hamilton wrote:

> Greetings,
>
> I recently upgraded a FreeBSD 4.6.2 bridge to 5.0, and am having troubles
> with how it handles IP addresses.
>
>    router
>      |
>      | t1
>      |
>    [fxp0]
> FreeBSD bridge
>    [fxp1]
>      |
>   switch
>      |
>    hosts
>
> The problem is that if the external interface is assigned an address, the=
n
> hosts on the same block can't access it. Likewise if the internal interfa=
ce
> is given an address, *only* hosts on the same block can access it! I have
> verified that in both cases the bridge has its default route correctly se=
t.
>
> I won't be too suprised if this is due to screwey ISP routing, but I don'=
t
> recall this ever being a problem with 4.6.2.
>
> Any tips?
>
> thanks,
>
> sh
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+by9FXTGeGCdlN14RAs9YAJ9eEkJ7BLGQF+sQkhpuza9jBqpRQgCfQfu9
tgh/cKCXwGFxgSLz9WY9q98=3D
=3D5aVH
-----END PGP SIGNATURE-----



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


From owner-freebsd-hackers  Wed Mar 12  6:38: 1 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A9F8837B401
	for <hackers@freebsd.org>; Wed, 12 Mar 2003 06:38:00 -0800 (PST)
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by mx1.FreeBSD.org (Postfix) with SMTP id 2A62B43FDD
	for <hackers@freebsd.org>; Wed, 12 Mar 2003 06:37:59 -0800 (PST)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa80410@salmon>; 12 Mar 2003 14:37:55 +0000 (GMT)
Date: Wed, 12 Mar 2003 14:37:54 +0000
From: David Malone <dwmalone@maths.tcd.ie>
To: Sean Hamilton <sh@bel.bc.ca>
Cc: hackers@freebsd.org
Subject: Re: IP addresses of bridge interfaces
Message-ID: <20030312143754.GA54896@walton.maths.tcd.ie>
References: <000601c2e813$9d849650$d1d7e8d8@slugabed.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000601c2e813$9d849650$d1d7e8d8@slugabed.org>
User-Agent: Mutt/1.5.3i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Tue, Mar 11, 2003 at 01:17:25PM -0800, Sean Hamilton wrote:
> I recently upgraded a FreeBSD 4.6.2 bridge to 5.0, and am having troubles
> with how it handles IP addresses.

This problem is due to a rather contraversial change, where packets
are only accepted to addressed to the interface they are recieved
on if:

	net.inet.ip.check_interface=1

This was left off in -stable, but was turned on by default in
-current 'cos some people felt it was a security hole. There was a
rather long thread about it when it was committed, and it was
discussed on bugtraq at some length. If you need to disable it, you
should be able to do:

	net.inet.ip.check_interface=0

in /etc/sysctl.conf.

	David.

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


From owner-freebsd-hackers  Wed Mar 12  7:44: 2 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AAEC937B401
	for <freebsd-hackers@FreeBSD.org>; Wed, 12 Mar 2003 07:44:00 -0800 (PST)
Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 150FC43F75
	for <freebsd-hackers@FreeBSD.org>; Wed, 12 Mar 2003 07:44:00 -0800 (PST)
	(envelope-from nectar@celabo.org)
Received: from madman.celabo.org (madman.celabo.org [10.0.1.111])
	by gw.nectar.cc (Postfix) with ESMTP id 8CEB438
	for <freebsd-hackers@FreeBSD.org>; Wed, 12 Mar 2003 09:43:59 -0600 (CST)
Received: by madman.celabo.org (Postfix, from userid 1001)
	id 5FA8678C47; Wed, 12 Mar 2003 09:43:59 -0600 (CST)
Date: Wed, 12 Mar 2003 09:43:59 -0600
From: "Jacques A. Vidrine" <nectar@FreeBSD.org>
To: freebsd-hackers@FreeBSD.org
Subject: pthread keys and resource leaks
Message-ID: <20030312154359.GA65434@madman.celabo.org>
Mail-Followup-To: "Jacques A. Vidrine" <nectar@FreeBSD.org>,
	freebsd-hackers@FreeBSD.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Url: http://www.celabo.org/
User-Agent: Mutt/1.5.3i-ja.1
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hi All,

Please show me how stupid I am :-)  There does not appear to be a way
to avoid resource leaks in a library that must manage thread-local
storage.

The problem appears to be that the destructor given to
pthread_key_create is not called for the `main thread' (uncertain
terminology).  Example:


library
   private freekey()
      free resources, like fds
      deallocate thread-local storage
   public foo()
      pthread_once -> initialize pthread_key
      pthread_getspecific -> fetch thread-local storage
      if there wasn't any already allocated,
          allocate thread-local storage
          maybe initialize some stuff, like fds
      do your thing
      pthread_setspecific -> update thread-local storage
      
main
   1. call foo()
   2. create thread that calls foo()
   3. pthread_join()


Both invocations of foo() will work correctly: they will each have
their own thread-local storage allocated.  When the thread created at
(2) exits, freekey() will be called.  But, when the process exits,
freekey() will NOT have been called for the invocation of foo at (1)
(what I am calling the `main thread').


I'm pretty certain I'm using pthread_(set|get)specific in the spirit
intended.  Am I misunderstanding something, or is this a flaw in our
implementation?  (BTW, this holds for -CURRENT and -STABLE.)

Cheers,
-- 
Jacques A. Vidrine <nectar@celabo.org>          http://www.celabo.org/
NTT/Verio SME          .     FreeBSD UNIX     .       Heimdal Kerberos
jvidrine@verio.net     .  nectar@FreeBSD.org  .          nectar@kth.se

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


From owner-freebsd-hackers  Wed Mar 12  8: 9:36 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5041637B405
	for <hackers@freebsd.org>; Wed, 12 Mar 2003 08:09:33 -0800 (PST)
Received: from aeimail.aei.ca (aeimail.aei.ca [206.123.6.14])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 12F4C43F3F
	for <hackers@freebsd.org>; Wed, 12 Mar 2003 08:09:32 -0800 (PST)
	(envelope-from anarcat@anarcat.ath.cx)
Received: from shall.anarcat.ath.cx (chagt311rjf2zjdn@dsl-134-230.aei.ca [66.36.134.230])
	by aeimail.aei.ca (8.11.6/8.10.1) with ESMTP id h2CG9M328640
	for <hackers@freebsd.org>; Wed, 12 Mar 2003 11:09:24 -0500 (EST)
Received: from lenny.anarcat.ath.cx (lenny.anarcat.ath.cx [192.168.0.4])
	by shall.anarcat.ath.cx (Postfix) with SMTP id 0876C260
	for <hackers@freebsd.org>; Wed, 12 Mar 2003 11:09:09 -0500 (EST)
Received: by lenny.anarcat.ath.cx (sSMTP sendmail emulation); Wed, 12 Mar 2003 11:09:23 -0500
Date: Wed, 12 Mar 2003 11:09:23 -0500
From: The Anarcat <anarcat@anarcat.ath.cx>
To: hackers@freebsd.org
Subject: pointers on how to debug a pppoe quirk
Message-ID: <20030312160923.GA77384@lenny.anarcat.ath.cx>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c"
Content-Disposition: inline
User-Agent: Mutt/1.5.3i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


--sm4nu43k4a2Rpi4c
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I recently started having big problems with my ADSL/pppoe
connection. When ppp gets tired of not having any LQR feedback, it
disconnects:

ppp[3839]: tun0: Phase: deflink: ** Too many LQR packets lost **

and the kernel spews out:

/kernel: session in wrong state

=2E..just after ppp prints out:

ppp[58]: tun0: Phase: deflink: dial -> carrier
ppp[58]: tun0: Phase: Received NGM_PPPOE_ACNAME (hook "62031110019965-")

which is usually followed by:

ppp[58]: tun0: Phase: Received NGM_PPPOE_SESSIONID
ppp[58]: tun0: Phase: Received NGM_PPPOE_SUCCESS
ppp[58]: tun0: Phase: deflink: carrier -> login
ppp[58]: tun0: Phase: deflink: login -> lcp
ppp[58]: tun0: Warning: deflink: Reducing configured MRU from 1500 to 1492
ppp[58]: tun0: Phase: bundle: Authenticate
ppp[58]: tun0: Phase: deflink: his =3D PAP, mine =3D none
ppp[58]: tun0: Phase: Pap Output: ******* ********
ppp[58]: tun0: Phase: Pap Input: SUCCESS ()

=2E..instead.

I've heard other people having similar problems last year (see google
for the "wrong state" message) but it's the first time it actually
happens to me. The other person that had this problem had it fixed by
switching NIC, so I might try this here too.

If I need to power cycle the modem in order to get it back into
shape. And I'm pretty sure it's not the modem's fault since I can
reliably trigger the error by generating a "down" event in ppp (pppctl
/var/run/tun down).

I suspect that a recent 4.6->4.8-RC upgrade is responsible for this
problem, since it started happening during an installworld (yes, a
live installworld).

Now I've started hacking the kernel, thinking it might be in
ng_pppoe.c that the problem is. I've replaced the error condition with
a "warning", hoping everything will resolve normally. I don't know
pppoe very much, however, and documentation on the modem (an external
Daewoo dw-8050) is not really available.

Any pointers on where to begin? I've started with a debug printf-style
thing in the guilty section, but I'm not sure it'll do anything:


                                /*
                                 * Check the session is in the right state.
                                 * It needs to be in PPPOE_SINIT.
                                 */
                                sp =3D sendhook->private;
                                if (sp->state !=3D PPPOE_SINIT) {
                                        printf("session in wrong state: %i\=
n", sp->state);
                                        /* LEAVE(ENETUNREACH);*/
                                        break;
                                }

I'm about to test those changes here. It is my intuition that the
session is indeed in the good state, and in fact that it is still
connected, and all fine, but the kernel thinks otherwise.

So... any idea?

A.



--=20
Nothing incites to money-crimes like great poverty or great wealth.
                        - Mark Twain

--sm4nu43k4a2Rpi4c
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+b1uzttcWHAnWiGcRAiOzAJwMBk/a5Gu5mklGfUioxen/nlfPbACfdUoz
YkQyMdjmFz8ub8G+Y31E3Bg=
=TDua
-----END PGP SIGNATURE-----

--sm4nu43k4a2Rpi4c--

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


From owner-freebsd-hackers  Wed Mar 12  9:48:48 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 142F737B401
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 09:48:46 -0800 (PST)
Received: from smtp-relay.omnis.com (smtp-relay.omnis.com [216.239.128.27])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5FE7143F3F
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 09:48:45 -0800 (PST)
	(envelope-from wes@softweyr.com)
Received: from softweyr.homeunix.net (66-75-151-22.san.rr.com [66.75.151.22])
	by smtp-relay.omnis.com (Postfix) with ESMTP
	id 47EC542F98; Wed, 12 Mar 2003 09:48:44 -0800 (PST)
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr
To: Luigi Rizzo <rizzo@icir.org>,
	Peter Jeremy <peterjeremy@optushome.com.au>
Subject: Re: Realtek
Date: Wed, 12 Mar 2003 09:48:43 -0800
User-Agent: KMail/1.5
Cc: Doug Ambrisko <ambrisko@ambrisko.com>,
	freebsd-hackers@FreeBSD.ORG
References: <200303102102.33694.wes@softweyr.com> <20030312064424.GB6336@cirb503493.alcatel.com.au> <20030312003713.A74419@xorpc.icir.org>
In-Reply-To: <20030312003713.A74419@xorpc.icir.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200303120948.43596.wes@softweyr.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Wednesday 12 March 2003 00:37, Luigi Rizzo wrote:
> On Wed, Mar 12, 2003 at 05:44:25PM +1100, Peter Jeremy wrote:
> ...
>
> > Are you sure you were generating "wire speed" packets - this is about
> > 200,000 packets/sec at Fast speed.  "ping -f" runs at whatever rate
>
> 148,800kpps
>
> > In order to get 200,000 pps, you're going to need 5-10 hosts
> > generating traffic, each with a good NIC and connected to the test
>
> one is enough as long as it is sufficiently fast (750MHz and above
> in my experiments), you use a C program to call sendto() and
> generate UDP packets, and your network card can cope with the
> outgoing traffic (e.g. there is no way the 'fxp' can transmit
> over ~120kpps no matter how fast the CPU is; 'xl' and several 'dc'
> supported chips can do the job. Haven't tried other cards.
>
> Using polling on the sender side helps but it is not
> fundamental.

Or you can cheat and use a SmartBits-2000 like I did.  It can send exactly 
148,800 packets per second, with very precise timing of the inter-packet 
gap, preamble, and actual packet data.  You can make a reasonable 
facsimile of this on FreeBSD with judicious use of -i and -l.  Note that 
these are blasted at a Win2K box because I don't have a FreeBSD box to 
beat up at the moment:

-bash-2.05b$ sudo ping -i 0.000001 -c 5000 204.68.178.2
...
64 bytes from 204.68.178.2: icmp_seq=4997 ttl=128 time=0.192 ms
64 bytes from 204.68.178.2: icmp_seq=4998 ttl=128 time=0.185 ms
64 bytes from 204.68.178.2: icmp_seq=4999 ttl=128 time=0.173 ms

--- 204.68.178.2 ping statistics ---
5000 packets transmitted, 5000 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.104/0.191/0.605/0.033 ms

So it seems to keep up reasonably well, but this is misleading.  Use -l to 
force the packets out as quickly as the card can generate them:

-bash-2.05b$ sudo ping -i 0.000001 -c 5000 -l 5000 204.68.178.2
...
64 bytes from 204.68.178.2: icmp_seq=92 ttl=128 time=14.855 ms
64 bytes from 204.68.178.2: icmp_seq=93 ttl=128 time=14.880 ms
64 bytes from 204.68.178.2: icmp_seq=4424 ttl=128 time=17.308 ms

--- 204.68.178.2 ping statistics ---
5000 packets transmitted, 95 packets received, 98% packet loss
round-trip min/avg/max/stddev = 11.929/14.520/17.308/0.682 ms

Wow.  The receiving side handled the first 93 packets and then rolled 
over, recovering for only the last packet.  (Look at the icmp_seq 
numbers.)  FreeBSD behaves similarly, but try the test on your own.  ;^)

-- 

        Where am I, and what am I doing in this handbasket?

Wes Peters                                               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 Mar 12 10:36: 5 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B73D137B401
	for <hackers@freebsd.org>; Wed, 12 Mar 2003 10:36:04 -0800 (PST)
Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A78AB43FBF
	for <hackers@freebsd.org>; Wed, 12 Mar 2003 10:36:03 -0800 (PST)
	(envelope-from marck@rinet.ru)
Received: from localhost (localhost [127.0.0.1])
	by woozle.rinet.ru (8.12.8/8.12.8) with ESMTP id h2CIa2J5021811
	for <hackers@freebsd.org>; Wed, 12 Mar 2003 21:36:02 +0300 (MSK)
	(envelope-from marck@rinet.ru)
Date: Wed, 12 Mar 2003 21:36:02 +0300 (MSK)
From: Dmitry Morozovsky <marck@rinet.ru>
To: hackers@freebsd.org
Subject: FreeBSD-specific CVS: tagexpand question 
Message-ID: <20030312213135.B17741@woozle.rinet.ru>
X-NCC-RegID: ru.rinet
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Colleagues,

I'm not sure this is the most correct place to ask, but it at least seems so.

Is there any way to tune FreeBSD-specific CVS (with CVSROOT/options support) to
provide the following functionality:

- ident keyword should be standard ($ Id $)
- it should be expanded as ($ CVSHeader $) to repo-relative path

Looking at cvs sources and peter's changes aroute versions 1.4-1.5 has not
enlightened me enough, unfortunately.

Any help will be greatly appreciated.

Sincerely,
D.Marck                                   [DM5020, DM268-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------

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


From owner-freebsd-hackers  Wed Mar 12 10:37:53 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 206AA37B404
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 10:37:46 -0800 (PST)
Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3411E43F3F
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 10:37:44 -0800 (PST)
	(envelope-from ambrisko@www.ambrisko.com)
Received: from www.ambrisko.com (localhost [127.0.0.1])
	by ambrisko.com (8.12.6/8.12.6) with ESMTP id h2CIbhhZ088158;
	Wed, 12 Mar 2003 10:37:43 -0800 (PST)
	(envelope-from ambrisko@www.ambrisko.com)
Received: (from ambrisko@localhost)
	by www.ambrisko.com (8.12.6/8.12.6/Submit) id h2CIbh0S088157;
	Wed, 12 Mar 2003 10:37:43 -0800 (PST)
	(envelope-from ambrisko)
From: Doug Ambrisko <ambrisko@ambrisko.com>
Message-Id: <200303121837.h2CIbh0S088157@www.ambrisko.com>
Subject: Re: Realtek
In-Reply-To: <200303120948.43596.wes@softweyr.com>
To: Wes Peters <wes@softweyr.com>
Date: Wed, 12 Mar 2003 10:37:43 -0800 (PST)
Cc: freebsd-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL94b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Wes Peters writes:
| Or you can cheat and use a SmartBits-2000 like I did.  It can send exactly 
| 148,800 packets per second, with very precise timing of the inter-packet 

Soon we should be getting an Ixia.

| So it seems to keep up reasonably well, but this is misleading.  Use -l to 
| force the packets out as quickly as the card can generate them:
| 
| -bash-2.05b$ sudo ping -i 0.000001 -c 5000 -l 5000 204.68.178.2
| ...
| 64 bytes from 204.68.178.2: icmp_seq=92 ttl=128 time=14.855 ms
| 64 bytes from 204.68.178.2: icmp_seq=93 ttl=128 time=14.880 ms
| 64 bytes from 204.68.178.2: icmp_seq=4424 ttl=128 time=17.308 ms
| 
| --- 204.68.178.2 ping statistics ---
| 5000 packets transmitted, 95 packets received, 98% packet loss
| round-trip min/avg/max/stddev = 11.929/14.520/17.308/0.682 ms
| 
| Wow.  The receiving side handled the first 93 packets and then rolled 
| over, recovering for only the last packet.  (Look at the icmp_seq 
| numbers.)  FreeBSD behaves similarly, but try the test on your own.  ;^)

I don't see any difference between the rl and fxp tests using the same
originating machine and dest machine.  The dest machine has both rl and fxp

the rl0 results (ping -i 0.000001 -c 5000 -l 5000 <IP>):
  PING 192.168.99.2 (192.168.99.2): 56 data bytes
  64 bytes from 192.168.99.2: icmp_seq=0 ttl=64 time=0.499 ms
  64 bytes from 192.168.99.2: icmp_seq=1 ttl=64 time=0.467 ms
  64 bytes from 192.168.99.2: icmp_seq=2 ttl=64 time=0.461 ms
  64 bytes from 192.168.99.2: icmp_seq=3 ttl=64 time=0.458 ms
  64 bytes from 192.168.99.2: icmp_seq=4 ttl=64 time=0.484 ms
  64 bytes from 192.168.99.2: icmp_seq=5 ttl=64 time=0.502 ms
  64 bytes from 192.168.99.2: icmp_seq=6 ttl=64 time=0.500 ms
  64 bytes from 192.168.99.2: icmp_seq=7 ttl=64 time=0.498 ms
  64 bytes from 192.168.99.2: icmp_seq=8 ttl=64 time=0.514 ms
  64 bytes from 192.168.99.2: icmp_seq=9 ttl=64 time=0.508 ms
  64 bytes from 192.168.99.2: icmp_seq=10 ttl=64 time=0.503 ms
  64 bytes from 192.168.99.2: icmp_seq=11 ttl=64 time=0.519 ms
  64 bytes from 192.168.99.2: icmp_seq=12 ttl=64 time=0.514 ms
  64 bytes from 192.168.99.2: icmp_seq=13 ttl=64 time=0.512 ms
  64 bytes from 192.168.99.2: icmp_seq=14 ttl=64 time=0.523 ms
  64 bytes from 192.168.99.2: icmp_seq=15 ttl=64 time=0.520 ms
  64 bytes from 192.168.99.2: icmp_seq=16 ttl=64 time=0.516 ms
  64 bytes from 192.168.99.2: icmp_seq=17 ttl=64 time=0.525 ms
  64 bytes from 192.168.99.2: icmp_seq=18 ttl=64 time=0.522 ms
  64 bytes from 192.168.99.2: icmp_seq=19 ttl=64 time=0.519 ms
  64 bytes from 192.168.99.2: icmp_seq=20 ttl=64 time=0.532 ms
  64 bytes from 192.168.99.2: icmp_seq=21 ttl=64 time=0.527 ms
  64 bytes from 192.168.99.2: icmp_seq=22 ttl=64 time=0.523 ms
  64 bytes from 192.168.99.2: icmp_seq=23 ttl=64 time=0.535 ms
  64 bytes from 192.168.99.2: icmp_seq=24 ttl=64 time=0.531 ms
  64 bytes from 192.168.99.2: icmp_seq=25 ttl=64 time=0.529 ms
  64 bytes from 192.168.99.2: icmp_seq=26 ttl=64 time=0.540 ms
  64 bytes from 192.168.99.2: icmp_seq=27 ttl=64 time=0.535 ms
  64 bytes from 192.168.99.2: icmp_seq=28 ttl=64 time=0.532 ms
  64 bytes from 192.168.99.2: icmp_seq=29 ttl=64 time=0.541 ms
  64 bytes from 192.168.99.2: icmp_seq=30 ttl=64 time=0.538 ms
  64 bytes from 192.168.99.2: icmp_seq=31 ttl=64 time=0.533 ms
  64 bytes from 192.168.99.2: icmp_seq=32 ttl=64 time=0.540 ms
  64 bytes from 192.168.99.2: icmp_seq=33 ttl=64 time=0.553 ms
  64 bytes from 192.168.99.2: icmp_seq=34 ttl=64 time=0.548 ms
  64 bytes from 192.168.99.2: icmp_seq=35 ttl=64 time=0.544 ms
  64 bytes from 192.168.99.2: icmp_seq=36 ttl=64 time=0.180 ms
  64 bytes from 192.168.99.2: icmp_seq=37 ttl=64 time=0.175 ms
  64 bytes from 192.168.99.2: icmp_seq=38 ttl=64 time=0.185 ms
  64 bytes from 192.168.99.2: icmp_seq=39 ttl=64 time=0.180 ms
  64 bytes from 192.168.99.2: icmp_seq=40 ttl=64 time=0.206 ms
  64 bytes from 192.168.99.2: icmp_seq=41 ttl=64 time=0.204 ms
  64 bytes from 192.168.99.2: icmp_seq=42 ttl=64 time=0.214 ms
  64 bytes from 192.168.99.2: icmp_seq=43 ttl=64 time=0.208 ms
  64 bytes from 192.168.99.2: icmp_seq=44 ttl=64 time=0.221 ms
  64 bytes from 192.168.99.2: icmp_seq=45 ttl=64 time=0.218 ms
  64 bytes from 192.168.99.2: icmp_seq=46 ttl=64 time=0.228 ms
  64 bytes from 192.168.99.2: icmp_seq=47 ttl=64 time=0.225 ms
  64 bytes from 192.168.99.2: icmp_seq=48 ttl=64 time=0.236 ms
  64 bytes from 192.168.99.2: icmp_seq=49 ttl=64 time=0.233 ms
  64 bytes from 192.168.99.2: icmp_seq=50 ttl=64 time=0.242 ms
  64 bytes from 192.168.99.2: icmp_seq=51 ttl=64 time=0.160 ms
  64 bytes from 192.168.99.2: icmp_seq=52 ttl=64 time=0.156 ms
  64 bytes from 192.168.99.2: icmp_seq=53 ttl=64 time=0.166 ms
  64 bytes from 192.168.99.2: icmp_seq=54 ttl=64 time=0.161 ms
  64 bytes from 192.168.99.2: icmp_seq=55 ttl=64 time=0.185 ms
  64 bytes from 192.168.99.2: icmp_seq=56 ttl=64 time=0.199 ms
  64 bytes from 192.168.99.2: icmp_seq=57 ttl=64 time=0.196 ms
  64 bytes from 192.168.99.2: icmp_seq=58 ttl=64 time=0.193 ms
  64 bytes from 192.168.99.2: icmp_seq=59 ttl=64 time=0.202 ms
  64 bytes from 192.168.99.2: icmp_seq=60 ttl=64 time=0.216 ms
  64 bytes from 192.168.99.2: icmp_seq=61 ttl=64 time=0.213 ms
  64 bytes from 192.168.99.2: icmp_seq=62 ttl=64 time=0.212 ms
  64 bytes from 192.168.99.2: icmp_seq=63 ttl=64 time=0.219 ms
  64 bytes from 192.168.99.2: icmp_seq=64 ttl=64 time=0.579 ms
  64 bytes from 192.168.99.2: icmp_seq=65 ttl=64 time=0.182 ms
  64 bytes from 192.168.99.2: icmp_seq=66 ttl=64 time=0.191 ms
  64 bytes from 192.168.99.2: icmp_seq=67 ttl=64 time=0.189 ms
  64 bytes from 192.168.99.2: icmp_seq=68 ttl=64 time=0.213 ms
  64 bytes from 192.168.99.2: icmp_seq=69 ttl=64 time=0.212 ms
  64 bytes from 192.168.99.2: icmp_seq=70 ttl=64 time=0.221 ms
  64 bytes from 192.168.99.2: icmp_seq=71 ttl=64 time=0.218 ms
  64 bytes from 192.168.99.2: icmp_seq=72 ttl=64 time=0.227 ms
  64 bytes from 192.168.99.2: icmp_seq=73 ttl=64 time=0.239 ms
  64 bytes from 192.168.99.2: icmp_seq=74 ttl=64 time=0.237 ms
  64 bytes from 192.168.99.2: icmp_seq=75 ttl=64 time=0.233 ms
  64 bytes from 192.168.99.2: icmp_seq=76 ttl=64 time=0.246 ms
  64 bytes from 192.168.99.2: icmp_seq=77 ttl=64 time=0.244 ms
  64 bytes from 192.168.99.2: icmp_seq=78 ttl=64 time=0.242 ms
  64 bytes from 192.168.99.2: icmp_seq=79 ttl=64 time=0.605 ms
  64 bytes from 192.168.99.2: icmp_seq=80 ttl=64 time=0.157 ms
  64 bytes from 192.168.99.2: icmp_seq=81 ttl=64 time=0.166 ms
  64 bytes from 192.168.99.2: icmp_seq=82 ttl=64 time=0.162 ms
  64 bytes from 192.168.99.2: icmp_seq=83 ttl=64 time=0.186 ms
  64 bytes from 192.168.99.2: icmp_seq=84 ttl=64 time=0.202 ms
  64 bytes from 192.168.99.2: icmp_seq=85 ttl=64 time=0.200 ms
  64 bytes from 192.168.99.2: icmp_seq=86 ttl=64 time=0.197 ms
  64 bytes from 192.168.99.2: icmp_seq=87 ttl=64 time=0.209 ms
  64 bytes from 192.168.99.2: icmp_seq=88 ttl=64 time=0.208 ms
  64 bytes from 192.168.99.2: icmp_seq=89 ttl=64 time=0.220 ms
  64 bytes from 192.168.99.2: icmp_seq=90 ttl=64 time=0.218 ms
  64 bytes from 192.168.99.2: icmp_seq=91 ttl=64 time=0.216 ms
  64 bytes from 192.168.99.2: icmp_seq=92 ttl=64 time=0.576 ms
  64 bytes from 192.168.99.2: icmp_seq=93 ttl=64 time=0.180 ms
  
  --- 192.168.99.2 ping statistics ---
  5000 packets transmitted, 94 packets received, 98% packet loss
  round-trip min/avg/max/stddev = 0.156/0.337/0.605/0.159 ms

the fxp results:
  PING 192.168.88.2 (192.168.88.2): 56 data bytes
  64 bytes from 192.168.88.2: icmp_seq=0 ttl=64 time=0.204 ms
  64 bytes from 192.168.88.2: icmp_seq=1 ttl=64 time=0.249 ms
  64 bytes from 192.168.88.2: icmp_seq=2 ttl=64 time=0.244 ms
  64 bytes from 192.168.88.2: icmp_seq=3 ttl=64 time=0.240 ms
  64 bytes from 192.168.88.2: icmp_seq=4 ttl=64 time=0.236 ms
  64 bytes from 192.168.88.2: icmp_seq=5 ttl=64 time=0.232 ms
  64 bytes from 192.168.88.2: icmp_seq=6 ttl=64 time=0.226 ms
  64 bytes from 192.168.88.2: icmp_seq=7 ttl=64 time=0.222 ms
  64 bytes from 192.168.88.2: icmp_seq=8 ttl=64 time=0.218 ms
  64 bytes from 192.168.88.2: icmp_seq=9 ttl=64 time=0.214 ms
  64 bytes from 192.168.88.2: icmp_seq=10 ttl=64 time=0.139 ms
  64 bytes from 192.168.88.2: icmp_seq=11 ttl=64 time=0.156 ms
  64 bytes from 192.168.88.2: icmp_seq=12 ttl=64 time=0.162 ms
  64 bytes from 192.168.88.2: icmp_seq=13 ttl=64 time=0.173 ms
  64 bytes from 192.168.88.2: icmp_seq=14 ttl=64 time=0.209 ms
  64 bytes from 192.168.88.2: icmp_seq=15 ttl=64 time=0.208 ms
  64 bytes from 192.168.88.2: icmp_seq=16 ttl=64 time=0.205 ms
  64 bytes from 192.168.88.2: icmp_seq=17 ttl=64 time=0.201 ms
  64 bytes from 192.168.88.2: icmp_seq=18 ttl=64 time=0.197 ms
  64 bytes from 192.168.88.2: icmp_seq=19 ttl=64 time=0.206 ms
  64 bytes from 192.168.88.2: icmp_seq=20 ttl=64 time=0.203 ms
  64 bytes from 192.168.88.2: icmp_seq=21 ttl=64 time=0.486 ms
  64 bytes from 192.168.88.2: icmp_seq=22 ttl=64 time=0.146 ms
  64 bytes from 192.168.88.2: icmp_seq=23 ttl=64 time=0.158 ms
  64 bytes from 192.168.88.2: icmp_seq=24 ttl=64 time=0.154 ms
  64 bytes from 192.168.88.2: icmp_seq=25 ttl=64 time=0.167 ms
  64 bytes from 192.168.88.2: icmp_seq=26 ttl=64 time=0.166 ms
  64 bytes from 192.168.88.2: icmp_seq=27 ttl=64 time=0.179 ms
  64 bytes from 192.168.88.2: icmp_seq=28 ttl=64 time=0.176 ms
  64 bytes from 192.168.88.2: icmp_seq=29 ttl=64 time=0.173 ms
  64 bytes from 192.168.88.2: icmp_seq=30 ttl=64 time=0.177 ms
  64 bytes from 192.168.88.2: icmp_seq=31 ttl=64 time=0.137 ms
  64 bytes from 192.168.88.2: icmp_seq=32 ttl=64 time=0.153 ms
  64 bytes from 192.168.88.2: icmp_seq=33 ttl=64 time=0.162 ms
  64 bytes from 192.168.88.2: icmp_seq=34 ttl=64 time=0.170 ms
  64 bytes from 192.168.88.2: icmp_seq=35 ttl=64 time=0.185 ms
  64 bytes from 192.168.88.2: icmp_seq=36 ttl=64 time=0.181 ms
  64 bytes from 192.168.88.2: icmp_seq=37 ttl=64 time=0.181 ms
  64 bytes from 192.168.88.2: icmp_seq=38 ttl=64 time=0.197 ms
  64 bytes from 192.168.88.2: icmp_seq=39 ttl=64 time=0.197 ms
  64 bytes from 192.168.88.2: icmp_seq=40 ttl=64 time=0.191 ms
  64 bytes from 192.168.88.2: icmp_seq=41 ttl=64 time=0.187 ms
  64 bytes from 192.168.88.2: icmp_seq=42 ttl=64 time=0.142 ms
  64 bytes from 192.168.88.2: icmp_seq=43 ttl=64 time=0.156 ms
  64 bytes from 192.168.88.2: icmp_seq=44 ttl=64 time=0.152 ms
  64 bytes from 192.168.88.2: icmp_seq=45 ttl=64 time=0.168 ms
  64 bytes from 192.168.88.2: icmp_seq=46 ttl=64 time=0.167 ms
  64 bytes from 192.168.88.2: icmp_seq=47 ttl=64 time=0.179 ms
  64 bytes from 192.168.88.2: icmp_seq=48 ttl=64 time=0.176 ms
  64 bytes from 192.168.88.2: icmp_seq=49 ttl=64 time=0.190 ms
  64 bytes from 192.168.88.2: icmp_seq=50 ttl=64 time=0.186 ms
  64 bytes from 192.168.88.2: icmp_seq=51 ttl=64 time=0.183 ms
  64 bytes from 192.168.88.2: icmp_seq=52 ttl=64 time=0.189 ms
  64 bytes from 192.168.88.2: icmp_seq=53 ttl=64 time=0.126 ms
  64 bytes from 192.168.88.2: icmp_seq=54 ttl=64 time=0.143 ms
  64 bytes from 192.168.88.2: icmp_seq=55 ttl=64 time=0.160 ms
  64 bytes from 192.168.88.2: icmp_seq=56 ttl=64 time=0.170 ms
  64 bytes from 192.168.88.2: icmp_seq=57 ttl=64 time=0.168 ms
  64 bytes from 192.168.88.2: icmp_seq=58 ttl=64 time=0.180 ms
  64 bytes from 192.168.88.2: icmp_seq=59 ttl=64 time=0.180 ms
  64 bytes from 192.168.88.2: icmp_seq=60 ttl=64 time=0.176 ms
  64 bytes from 192.168.88.2: icmp_seq=61 ttl=64 time=0.187 ms
  64 bytes from 192.168.88.2: icmp_seq=62 ttl=64 time=0.184 ms
  64 bytes from 192.168.88.2: icmp_seq=63 ttl=64 time=0.126 ms
  64 bytes from 192.168.88.2: icmp_seq=64 ttl=64 time=0.143 ms
  64 bytes from 192.168.88.2: icmp_seq=65 ttl=64 time=0.160 ms
  64 bytes from 192.168.88.2: icmp_seq=66 ttl=64 time=0.171 ms
  64 bytes from 192.168.88.2: icmp_seq=67 ttl=64 time=0.168 ms
  64 bytes from 192.168.88.2: icmp_seq=68 ttl=64 time=0.183 ms
  64 bytes from 192.168.88.2: icmp_seq=69 ttl=64 time=0.181 ms
  64 bytes from 192.168.88.2: icmp_seq=70 ttl=64 time=0.178 ms
  64 bytes from 192.168.88.2: icmp_seq=71 ttl=64 time=0.186 ms
  64 bytes from 192.168.88.2: icmp_seq=72 ttl=64 time=0.185 ms
  64 bytes from 192.168.88.2: icmp_seq=73 ttl=64 time=0.127 ms
  64 bytes from 192.168.88.2: icmp_seq=74 ttl=64 time=0.144 ms
  64 bytes from 192.168.88.2: icmp_seq=75 ttl=64 time=0.170 ms
  64 bytes from 192.168.88.2: icmp_seq=76 ttl=64 time=0.230 ms
  64 bytes from 192.168.88.2: icmp_seq=77 ttl=64 time=0.228 ms
  64 bytes from 192.168.88.2: icmp_seq=78 ttl=64 time=0.225 ms
  64 bytes from 192.168.88.2: icmp_seq=79 ttl=64 time=0.220 ms
  64 bytes from 192.168.88.2: icmp_seq=80 ttl=64 time=0.218 ms
  64 bytes from 192.168.88.2: icmp_seq=81 ttl=64 time=0.215 ms
  64 bytes from 192.168.88.2: icmp_seq=82 ttl=64 time=0.213 ms
  64 bytes from 192.168.88.2: icmp_seq=83 ttl=64 time=0.135 ms
  64 bytes from 192.168.88.2: icmp_seq=84 ttl=64 time=0.151 ms
  64 bytes from 192.168.88.2: icmp_seq=85 ttl=64 time=0.158 ms
  64 bytes from 192.168.88.2: icmp_seq=86 ttl=64 time=0.166 ms
  64 bytes from 192.168.88.2: icmp_seq=87 ttl=64 time=0.178 ms
  64 bytes from 192.168.88.2: icmp_seq=88 ttl=64 time=0.175 ms
  64 bytes from 192.168.88.2: icmp_seq=89 ttl=64 time=0.190 ms
  64 bytes from 192.168.88.2: icmp_seq=90 ttl=64 time=0.189 ms
  64 bytes from 192.168.88.2: icmp_seq=91 ttl=64 time=0.186 ms
  64 bytes from 192.168.88.2: icmp_seq=92 ttl=64 time=0.193 ms
  64 bytes from 192.168.88.2: icmp_seq=93 ttl=64 time=0.192 ms
  
  --- 192.168.88.2 ping statistics ---
  5000 packets transmitted, 94 packets received, 98% packet loss
  round-trip min/avg/max/stddev = 0.126/0.185/0.486/0.042 ms

Now the FreeBSD target whines about the icmp limits.  If I turn off
ICMP bandwith limit I see little difference except that end of the 
fxp0 case:
  64 bytes from 192.168.88.2: icmp_seq=99 ttl=64 time=0.262 ms
  64 bytes from 192.168.88.2: icmp_seq=100 ttl=64 time=0.259 ms
  64 bytes from 192.168.88.2: icmp_seq=101 ttl=64 time=0.230 ms
  64 bytes from 192.168.88.2: icmp_seq=102 ttl=64 time=0.202 ms
  64 bytes from 192.168.88.2: icmp_seq=4999 ttl=64 time=0.091 ms
  
  --- 192.168.88.2 ping statistics ---
  5000 packets transmitted, 95 packets received, 98% packet loss
  round-trip min/avg/max/stddev = 0.091/0.192/0.281/0.043 ms

rl0 case:
  64 bytes from 192.168.99.2: icmp_seq=98 ttl=64 time=0.251 ms
  64 bytes from 192.168.99.2: icmp_seq=99 ttl=64 time=0.248 ms
  64 bytes from 192.168.99.2: icmp_seq=100 ttl=64 time=0.247 ms
  64 bytes from 192.168.99.2: icmp_seq=101 ttl=64 time=0.634 ms
  64 bytes from 192.168.99.2: icmp_seq=4995 ttl=64 time=0.534 ms

  --- 192.168.99.2 ping statistics ---
  5000 packets transmitted, 95 packets received, 98% packet loss
  round-trip min/avg/max/stddev = 0.129/0.241/0.634/0.107 ms

I'm generating the traffic with a fxp0 device.

So I'm not see much difference.

Doug a

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


From owner-freebsd-hackers  Wed Mar 12 10:54:22 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 14D4037B401
	for <freebsd-hackers@freebsd.org>; Wed, 12 Mar 2003 10:54:21 -0800 (PST)
Received: from grsu.by (grsu.by [194.158.202.115])
	by mx1.FreeBSD.org (Postfix) with SMTP id 75E4843FA3
	for <freebsd-hackers@freebsd.org>; Wed, 12 Mar 2003 10:54:19 -0800 (PST)
	(envelope-from grog@grsu.by)
Received: (qmail 30868 invoked from network); 12 Mar 2003 18:52:45 -0000
Received: from unknown (HELO grsu.by) (grog@195.50.13.211)
  by grsu.by with SMTP; 12 Mar 2003 18:52:45 -0000
Message-ID: <3E6F74AD.3000306@grsu.by>
Date: Wed, 12 Mar 2003 19:55:57 +0200
From: Yury Tarasievich <grog@grsu.by>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20020829
X-Accept-Language: be, en
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
Subject: Re: Are there any on-going projects on v4l porting?
References: <20030308015609.R680@kushnir1.kiev.ua>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

At http://freebsddvb.narod.ru, there exists an adequately up-to-date 
port of linux DVB drivers, seemingly supporting DVB adapters up to rev.1.5.

Regarding porting of V4L. I may be utterly wrong, but isn't the whole 
V4L/V4L2/V4L2-whatever thing rather made ad hoc, not really designed? 
Could something reincarnating BeOS (or even OS/2) multimedia subsystem 
be better?

Vladimir Kushnir wrote:

>As subj. said - does anybody work on porting v4l & (especially!)
>drivers for non- bt8x based cards? Specifically saa7134 based (got one and
>would rather not have to reboot to Linux to watch TV :-)
>Yes, I know, the simplest answer would be "you're interested - you do" but
>that'd be quite beyond my skills. Still I'd happily help with
>testing/debugging/whatever else.
>
>  
>



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


From owner-freebsd-hackers  Wed Mar 12 11:47:39 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4107837B401
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 11:47:38 -0800 (PST)
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7315043FDF
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 11:47:37 -0800 (PST)
	(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
	by dan.emsphone.com (8.12.7/8.12.7) id h2CJlajb063651;
	Wed, 12 Mar 2003 13:47:36 -0600 (CST)
	(envelope-from dan)
Date: Wed, 12 Mar 2003 13:47:36 -0600
From: Dan Nelson <dnelson@allantgroup.com>
To: Yury Tarasievich <grog@grsu.by>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Are there any on-going projects on v4l porting?
Message-ID: <20030312194736.GM34322@dan.emsphone.com>
References: <20030308015609.R680@kushnir1.kiev.ua> <3E6F74AD.3000306@grsu.by>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E6F74AD.3000306@grsu.by>
X-OS: FreeBSD 5.0-CURRENT
X-message-flag: Outlook Error
User-Agent: Mutt/1.5.3i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

In the last episode (Mar 12), Yury Tarasievich said:
> At http://freebsddvb.narod.ru, there exists an adequately up-to-date
> port of linux DVB drivers, seemingly supporting DVB adapters up to
> rev.1.5.
> 
> Regarding porting of V4L. I may be utterly wrong, but isn't the whole
> V4L/V4L2/V4L2-whatever thing rather made ad hoc, not really designed? 
> Could something reincarnating BeOS (or even OS/2) multimedia
> subsystem be better?

I like the idea of putting this into the Xfree86 drivers and using the
XVideo extension to drive everything.  that doesn't require kernel
mods.  It does mean that you need to start X up to capture video,
though.

-- 
	Dan Nelson
	dnelson@allantgroup.com

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


From owner-freebsd-hackers  Wed Mar 12 14:26:37 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AA5CE37B401
	for <freebsd-hackers@freebsd.org>; Wed, 12 Mar 2003 14:26:34 -0800 (PST)
Received: from ariel.ucs.unimelb.edu.au (ariel.ucs.unimelb.edu.au [128.250.20.3])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4EA8A43FAF
	for <freebsd-hackers@freebsd.org>; Wed, 12 Mar 2003 14:26:33 -0800 (PST)
	(envelope-from jrhoden@unimelb.edu.au)
Received: from elkanah.its.unimelb.edu.au (elkanah.its.unimelb.edu.au [128.250.18.41])
	by ariel.ucs.unimelb.edu.au (8.12.8/8.12.8) with ESMTP id h2CMQWcl028836
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 09:26:32 +1100 (EST)
From: JacobRhoden <jrhoden@unimelb.edu.au>
Organization: University of Melbourne
To: freebsd-hackers@freebsd.org
Subject: usb not working on intel motherboard
Date: Thu, 13 Mar 2003 09:26:32 +1100
User-Agent: KMail/1.5
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200303130926.32296.jrhoden@unimelb.edu.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hi,

It seems that no matter what I do I can not get usb devices to even be 
recognised. (Yes usbd is running).  Relevant DMESG and usbd error messages 
below. Does anyone have any ideas? (I have tried usb mouse, keyboard, and 
camera).

Thanks,
Jacob

FreeBSD elkanah.its.unimelb.edu.au 4.8-RC FreeBSD 4.8-RC #1: Wed Mar 12 
15:00:01 EST 2003     
jrhoden@elkanah.its.unimelb.edu.au:/usr/obj/usr/src/sys/JOAB2  i386

uhci0: <Intel 82801DB (ICH4) USB controller USB-A> port 0xe800-0xe81f irq 11 
at device 29.0 on pci0
usb0: <Intel 82801DB (ICH4) USB controller USB-A> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <Intel 82801DB (ICH4) USB controller USB-B> port 0xe880-0xe89f irq 5 at 
device 29.1 on pci0
usb1: <Intel 82801DB (ICH4) USB controller USB-B> on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: <Intel 82801DB (ICH4) USB controller USB-C> port 0xec00-0xec1f irq 9 at 
device 29.2 on pci0
usb2: <Intel 82801DB (ICH4) USB controller USB-C> on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered

And verbose debug output from usbd:

%/usr/sbin/usbd -d -vv -f /dev/usb0 -f /dev/usb1 -f /dev/usb2
usbd: opened /dev/usb0
usbd: opened /dev/usb1
usbd: opened /dev/usb2
usbd: reading configuration file /etc/usbd.conf
usbd: action 1: ActiveWire board, firmware download
  vndr=0x0854 prdct=0x0100 rlse=0x0000
  attach='/usr/local/bin/ezdownload -f 
/usr/local/share/usb/firmware/0854.0100.0_01.hex ${DEVNAME}'
usbd: action 2: Entrega Serial with UART
  vndr=0x1645 prdct=0x8001 rlse=0x0101
  attach='/usr/sbin/ezdownload -v -f /usr/share/usb/firmware/1645.8001.0101 
/dev/${DEVNAME}'
usbd: action 3: USB ethernet
  devname: [ack]ue[0-9]+
  attach='dhclient ${DEVNAME}'
  detach='killall dhclient'
usbd: action 4: Mouse
  devname: ums[0-9]+
  attach='/usr/sbin/moused -p /dev/${DEVNAME} -I 
/var/run/moused.${DEVNAME}.pid'
usbd: action 5: USB device
usbd: 5 actions
usbd: opened /dev/usb
usbd: doing timeout discovery on /dev/usb0
usbd: doing timeout discovery on /dev/usb1
usbd: doing timeout discovery on /dev/usb2
usbd: processing event queue due to timeout on /dev/usb
usbd: doing timeout discovery on /dev/usb0
usbd: doing timeout discovery on /dev/usb1
usbd: doing timeout discovery on /dev/usb2
usbd: processing event queue due to timeout on /dev/usb


Jacob Rhoden            Phone: +61 3 8344 6102
ITS Division            Email: jrhoden@unimelb.edu.au
Melbourne University   Mobile: +61 403 788 386

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


From owner-freebsd-hackers  Wed Mar 12 15:33:24 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BFB0437B404
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 15:33:22 -0800 (PST)
Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5D41F43FBD
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 15:29:34 -0800 (PST)
	(envelope-from ambrisko@www.ambrisko.com)
Received: from www.ambrisko.com (localhost [127.0.0.1])
	by ambrisko.com (8.12.6/8.12.6) with ESMTP id h2CNTYhZ004122
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 15:29:34 -0800 (PST)
	(envelope-from ambrisko@www.ambrisko.com)
Received: (from ambrisko@localhost)
	by www.ambrisko.com (8.12.6/8.12.6/Submit) id h2CNSIUt004047;
	Wed, 12 Mar 2003 15:28:18 -0800 (PST)
	(envelope-from ambrisko)
From: Doug Ambrisko <ambrisko@ambrisko.com>
Message-Id: <200303122328.h2CNSIUt004047@www.ambrisko.com>
Subject: Re: redirect everything to socks5
In-Reply-To: <20030310231600.GA62069@stone.locallink.net>
To: Keith Pitcher <kpitcher@locallink.net>
Date: Wed, 12 Mar 2003 15:28:18 -0800 (PST)
Cc: freebsd-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL94b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Keith Pitcher writes:
| Living in rural slow connection land, I've been playing around with
| satellite Internet. The problem is the company only has Win
| drivers. (Linux driver is in the works, but no plans to open source it, will be
| released as a binary - the bastards)
| 
| Anyhow, to get the download speed of the satellite it uses a http proxy and
| a socks5 proxy. This works fine for things that allow proxies or socks. But
| there are a lot of things that don't support it.
| 
| Is there a way to "socksify" everything my freebsd box does, so no
| matter what I do, I can just point it to the socks machine and it works?

"runsocks" works for most apps as long as they use a shared libc and
don't link to libc_r.  If they use libc_r you need to make a libc_r shim
for that.  Also a libc shim for Linux would be needed for Linux apps
that use a shared libc.

Now I did find that Netscape and runsocks/socks gateway had trouble with
https type transfers.  Doing a packet capture it would do an unencrupted
request, fail and then reture with an encrypted request.  This confused
the state of the proxied connection.
 
| Would also be handy to have a way to "socksify" the box when it acts as a
| network gateway, so I'd only have one really strangely configured machine and
| the rest would be normal.

You might be able to do a nat like thing to a socks proxy via divert.

Another work-around is to run a "gateway/router" thing on a Windows box
and then point your machine to that gateway and it would socksify the
transfer to the other network.  This actually works well except for 
depending on a Windows box.

Not knowing enough about these things but slightly interested in DirectWay
for our trailer I've read about interfaces that go to Ethernet or 802.11b.
I wonder if these can automatically do that since I don't use Windows I
would need that type of solution.

Doug A.

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


From owner-freebsd-hackers  Wed Mar 12 16:39:56 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7A1E537B401
	for <freebsd-hackers@freebsd.org>; Wed, 12 Mar 2003 16:39:55 -0800 (PST)
Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3790143F93
	for <freebsd-hackers@freebsd.org>; Wed, 12 Mar 2003 16:39:54 -0800 (PST)
	(envelope-from jwd@bsdwins.com)
Received: from bsdone.bsdwins.com (localhost [127.0.0.1])
	by bsdone.bsdwins.com (8.12.5/8.12.5) with ESMTP id h2D0drW2001961
	for <freebsd-hackers@freebsd.org>; Wed, 12 Mar 2003 19:39:53 -0500 (EST)
	(envelope-from jwd@www.bsdwins.com)
Received: (from jwd@localhost)
	by bsdone.bsdwins.com (8.12.5/8.12.5/Submit) id h2D0dq82001960
	for freebsd-hackers@freebsd.org; Wed, 12 Mar 2003 19:39:52 -0500 (EST)
Date: Wed, 12 Mar 2003 19:39:52 -0500
From: John <jwd@bsdwins.com>
To: Hackers List <freebsd-hackers@freebsd.org>
Subject: magic symbolic links (ideas/patches?)
Message-ID: <20030313003952.GA1800@BSDWins.Com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hi Folks,

   I have a need to implement a highly specific variant usage of
what are commonly referred to as magic symlinks, ie:

   /src -> /.src/$ARCH/src

   where $ARCH needs to come from the user environment.

   A related patchset from NetBSD (1995) can be seen here:

http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=1781

   In my specific implementation, the value of $ARCH will ALWAYS
be 3 characters (Not having implemented anything yet, and to
avoid possibly playing the userland game, I was thinking of
adding a field to the proc structure and having the setenv/putenv
functions place the value there via a sysctl, thus allowing a
very simple interface... short sighted?).

   If anyone has any comments, or patches hanging around for
this type of implementation, I would appreciate a pointer to them.

Many, Many Thanks,
John

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


From owner-freebsd-hackers  Wed Mar 12 18:24:57 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3D14037B401
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 18:24:56 -0800 (PST)
Received: from 134.216-123-229-0.interbaun.com (134.216-123-229-0.interbaun.com [216.123.229.134])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B42CE43F93
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 18:24:52 -0800 (PST)
	(envelope-from soralx@cydem.org.ua)
Received: from vasya (vasya [192.168.0.3])
	by 134.216-123-229-0.interbaun.com (8.11.6/8.11.6) with ESMTP id h2D2OnU11357
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 19:24:51 -0700 (MST)
	(envelope-from soralx@cydem.org.ua)
From: <soralx@cydem.org.ua>
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: Realtek
Date: Wed, 12 Mar 2003 19:01:26 -0700
User-Agent: KMail/1.5
References: <200303121837.h2CIbh0S088157@www.ambrisko.com>
In-Reply-To: <200303121837.h2CIbh0S088157@www.ambrisko.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200303121901.26503.soralx@cydem.org.ua>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

>   5000 packets transmitted, 94 packets received, 98% packet loss
>   round-trip min/avg/max/stddev = 0.156/0.337/0.605/0.159 ms
> So I'm not see much difference.

are you sure it's not because of this:
'ping: sendto: No buffer space available'?

12.03.2003; 18:56:02
[SorAlx]  http://cydem.org.ua/

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


From owner-freebsd-hackers  Wed Mar 12 19:29:11 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0FAA037B404
	for <hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 19:29:10 -0800 (PST)
Received: from Princeton.EDU (postoffice.Princeton.EDU [128.112.129.120])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AC60843FBD
	for <hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 19:29:08 -0800 (PST)
	(envelope-from yruan@cs.princeton.edu)
Received: from smtpserver2.Princeton.EDU (smtpserver2.Princeton.EDU [128.112.129.148])
	by Princeton.EDU (8.12.8/8.12.6) with ESMTP id h2D3T7GO021397
	for <hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 22:29:07 -0500 (EST)
Received: from cs.princeton.edu (targe.CS.Princeton.EDU [128.112.139.194])
	(authenticated bits=0 netid=yruan)
	by smtpserver2.Princeton.EDU (8.12.6/8.12.6) with ESMTP id h2D3T4wq006771
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 22:29:07 -0500 (EST)
Message-ID: <3E6FFAAE.2B6108F8@cs.princeton.edu>
Date: Wed, 12 Mar 2003 22:27:42 -0500
From: Yaoping Ruan <yruan@cs.princeton.edu>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: hackers@FreeBSD.ORG
Subject: Kernel trace
References: <bulk.24288.20030308135115@hub.freebsd.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Does any one know the implementation of "ktrace" in FreeBSD? I would like to hack the
source code and have a relatively easy way to copy the kernel stack image when a
certain of thing happens, such as page fault. It should work like the breakpoints in
gdb. But kernel panic is too much trouble for just a single stack image, and kgdb is
not simple enough. Which source file(s) I should look at?

- Yaoping Ruan


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


From owner-freebsd-hackers  Wed Mar 12 19:35:30 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3DE7637B404
	for <hackers@freebsd.org>; Wed, 12 Mar 2003 19:35:29 -0800 (PST)
Received: from priv-edtnes09-hme0.telusplanet.net (outbound02.telus.net [199.185.220.221])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DDB3A43F3F
	for <hackers@freebsd.org>; Wed, 12 Mar 2003 19:35:27 -0800 (PST)
	(envelope-from sh@bel.bc.ca)
Received: from REASON ([216.232.215.209])
          by priv-edtnes09-hme0.telusplanet.net
          (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with SMTP
          id <20030313033527.VJGQ26116.priv-edtnes09-hme0.telusplanet.net@REASON>
          for <hackers@freebsd.org>; Wed, 12 Mar 2003 20:35:27 -0700
Message-ID: <000501c2e911$96ea79a0$d1d7e8d8@slugabed.org>
From: "Sean Hamilton" <sh@bel.bc.ca>
To: <hackers@freebsd.org>
Subject: first parameter to select
Date: Wed, 12 Mar 2003 19:35:27 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Greetings,

What is the first parameter to select(2) for? Microsoft's select ignores it,
and it does not appear to have any valid use since it only allows
constraints on values which are assigned by the system.

Purely historic?

sh


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


From owner-freebsd-hackers  Wed Mar 12 19:38: 4 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 661CB37B401
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 19:38:03 -0800 (PST)
Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A67AF43F85
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 19:38:02 -0800 (PST)
	(envelope-from ambrisko@www.ambrisko.com)
Received: from www.ambrisko.com (localhost [127.0.0.1])
	by ambrisko.com (8.12.6/8.12.6) with ESMTP id h2D3bMhZ017322;
	Wed, 12 Mar 2003 19:37:22 -0800 (PST)
	(envelope-from ambrisko@www.ambrisko.com)
Received: (from ambrisko@localhost)
	by www.ambrisko.com (8.12.6/8.12.6/Submit) id h2D3bKwN017317;
	Wed, 12 Mar 2003 19:37:20 -0800 (PST)
	(envelope-from ambrisko)
From: Doug Ambrisko <ambrisko@ambrisko.com>
Message-Id: <200303130337.h2D3bKwN017317@www.ambrisko.com>
Subject: Re: Realtek
In-Reply-To: <200303121901.26503.soralx@cydem.org.ua>
To: soralx@cydem.org.ua
Date: Wed, 12 Mar 2003 19:37:20 -0800 (PST)
Cc: freebsd-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL94b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

soralx@cydem.org.ua writes:
[ Charset ISO-8859-1 unsupported, converting... ]
| >   5000 packets transmitted, 94 packets received, 98% packet loss
| >   round-trip min/avg/max/stddev = 0.156/0.337/0.605/0.159 ms
| > So I'm not see much difference.
| 
| are you sure it's not because of this:
| 'ping: sendto: No buffer space available'?

No such messages appeared.

Doug A.

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


From owner-freebsd-hackers  Wed Mar 12 20:16:53 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8CC6937B401
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 20:16:52 -0800 (PST)
Received: from 134.216-123-229-0.interbaun.com (134.216-123-229-0.interbaun.com [216.123.229.134])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7A47F43FCB
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 20:16:51 -0800 (PST)
	(envelope-from soralx@cydem.org.ua)
Received: from vasya (vasya [192.168.0.3])
	by 134.216-123-229-0.interbaun.com (8.11.6/8.11.6) with ESMTP id h2D4GnU13682
	for <freebsd-hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 21:16:50 -0700 (MST)
	(envelope-from soralx@cydem.org.ua)
From: <soralx@cydem.org.ua>
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: Realtek
Date: Wed, 12 Mar 2003 20:53:20 -0700
User-Agent: KMail/1.5
References: <200303130337.h2D3bKwN017317@www.ambrisko.com>
In-Reply-To: <200303130337.h2D3bKwN017317@www.ambrisko.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200303122053.20383.soralx@cydem.org.ua>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

>| are you sure it's not because of this:
>| 'ping: sendto: No buffer space available'?
>No such messages appeared.

I forgot that I hooked it up to 10Mbit hub for
now, so nevermind 8)

are you piping it through 'less'? you won't see
this message in 'less' output

what's the value of your 'kern.ipc.nmbclusters'?

`sysctl kern.ipc.nmbclusters`: kern.ipc.nmbclusters: 4560
(FreeBSD 4.6.2-RELEASE)

I'll test 'rl' vs 'xl' later on 100Mbit/s.

12.03.2003; 20:16:35
[SorAlx]  http://cydem.org.ua/

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


From owner-freebsd-hackers  Wed Mar 12 20:58:46 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1880637B401
	for <hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 20:58:45 -0800 (PST)
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 56A4443F85
	for <hackers@FreeBSD.ORG>; Wed, 12 Mar 2003 20:58:44 -0800 (PST)
	(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
	by dan.emsphone.com (8.12.7/8.12.7) id h2D4wgst075271;
	Wed, 12 Mar 2003 22:58:42 -0600 (CST)
	(envelope-from dan)
Date: Wed, 12 Mar 2003 22:58:42 -0600
From: Dan Nelson <dnelson@allantgroup.com>
To: Sean Hamilton <sh@bel.bc.ca>
Cc: hackers@FreeBSD.ORG
Subject: Re: first parameter to select
Message-ID: <20030313045842.GG2336@dan.emsphone.com>
References: <000501c2e911$96ea79a0$d1d7e8d8@slugabed.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000501c2e911$96ea79a0$d1d7e8d8@slugabed.org>
X-OS: FreeBSD 5.0-CURRENT
X-message-flag: Outlook Error
User-Agent: Mutt/1.5.3i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

In the last episode (Mar 12), Sean Hamilton said:
> What is the first parameter to select(2) for? Microsoft's select
> ignores it, and it does not appear to have any valid use since it
> only allows constraints on values which are assigned by the system.

I'd hate to have the kernel scan a 6000-element (or whatever maxfiles
is on your system) array every time I called select with nfds=10.

If MS ignores the nfds parameter, it risks accessing uninitialized
memory or selecting on fds that the user no longer wants to look at. 
I'd call it a bug.
 
> Purely historic?

Performance.

-- 
	Dan Nelson
	dnelson@allantgroup.com

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


From owner-freebsd-hackers  Wed Mar 12 22:57:20 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9991137B401
	for <hackers@freebsd.org>; Wed, 12 Mar 2003 22:57:18 -0800 (PST)
Received: from pool-151-201-19-185.pitt.east.verizon.net (pool-151-201-19-185.pitt.east.verizon.net [151.201.19.185])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EDDAA43F93
	for <hackers@freebsd.org>; Wed, 12 Mar 2003 22:57:17 -0800 (PST)
	(envelope-from dacut@kanga.org)
Received: from kanga.org (unknown [127.0.0.1])
	by pool-151-201-19-185.pitt.east.verizon.net (Postfix) with ESMTP id 4A3C310C4B9
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 01:57:16 -0500 (EST)
Message-ID: <3E702BCC.3030208@kanga.org>
Date: Thu, 13 Mar 2003 01:57:16 -0500
From: David Cuthbert <dacut@kanga.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: Re: first parameter to select
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Sean Hamilton wrote:

 > What is the first parameter to select(2) for? Microsoft's select 
ignores it,
 > and it does not appear to have any valid use since it only allows
 > constraints on values which are assigned by the system.
 >
 > Purely historic?


Ah, you've been reading the Winsock documentation.

fd_set is usually a fixed-size bitmask of filedescriptors (this 
implementation isn't guaranteed, but I haven't seen another).  The 
number of bits corresponds to the maximum number of files a process can 
have open (according to your header files; tweaks to your kernel and 
process limits can dictate otherwise).

select() needs to know how many of those bits (descriptors) to scan. 
Passing in FD_SETSIZE will tell it to scan all of the bits.  But most 
processes only have a few handles open, so the majority of the scanning 
goes to waste.  Instead (except on Microsoft's Winsock, which always 
assumes FD_SETSIZE regardless of what you pass in), you can tell it to 
stop at bit/descriptor N, where N is the highest numbered descriptor in 
all of the fd_set bitmasks passed to select().

To be honest, I've never passed anything but FD_SETSIZE for this 
parameter.  When I'm writing a performance critical server, I use poll() 
instead.  It's faster and I don't have to reinitialize the fd_set 
bitmasks on each iteration.  It's technically less portable, but I've 
never had an issue across Solaris, HP-UX, Linux, or FreeBSD.



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


From owner-freebsd-hackers  Thu Mar 13  0:19:49 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BD58337B401
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 00:19:47 -0800 (PST)
Received: from smtp-relay.omnis.com (smtp-relay.omnis.com [216.239.128.27])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3331C43FAF
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 00:19:47 -0800 (PST)
	(envelope-from wes@softweyr.com)
Received: from softweyr.homeunix.net (66-75-151-22.san.rr.com [66.75.151.22])
	by smtp-relay.omnis.com (Postfix) with ESMTP
	id 9481842DD1; Thu, 13 Mar 2003 00:19:46 -0800 (PST)
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr
To: Doug Ambrisko <ambrisko@ambrisko.com>
Subject: Re: Realtek
Date: Thu, 13 Mar 2003 00:19:46 -0800
User-Agent: KMail/1.5
Cc: freebsd-hackers@FreeBSD.ORG
References: <200303121837.h2CIbh0S088157@www.ambrisko.com>
In-Reply-To: <200303121837.h2CIbh0S088157@www.ambrisko.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200303130019.46144.wes@softweyr.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Wednesday 12 March 2003 10:37, Doug Ambrisko wrote:
> Wes Peters writes:
> | Or you can cheat and use a SmartBits-2000 like I did.  It can send
> | exactly 148,800 packets per second, with very precise timing of the
> | inter-packet
>
> Soon we should be getting an Ixia.

That'll certainly do the trick.  That is, if they actually manage to 
deliver it before the SmartBits people buy them up and kill them off; 
they've done that with at least one other competitor.

> | So it seems to keep up reasonably well, but this is misleading.  Use
> | -l to force the packets out as quickly as the card can generate them:
> |
> | -bash-2.05b$ sudo ping -i 0.000001 -c 5000 -l 5000 204.68.178.2
> | ...
> | 64 bytes from 204.68.178.2: icmp_seq=92 ttl=128 time=14.855 ms
> | 64 bytes from 204.68.178.2: icmp_seq=93 ttl=128 time=14.880 ms
> | 64 bytes from 204.68.178.2: icmp_seq=4424 ttl=128 time=17.308 ms
> |
> | --- 204.68.178.2 ping statistics ---
> | 5000 packets transmitted, 95 packets received, 98% packet loss
> | round-trip min/avg/max/stddev = 11.929/14.520/17.308/0.682 ms
> |
> | Wow.  The receiving side handled the first 93 packets and then rolled
> | over, recovering for only the last packet.  (Look at the icmp_seq
> | numbers.)  FreeBSD behaves similarly, but try the test on your own. 
> | ;^)
>
> I don't see any difference between the rl and fxp tests using the same
> originating machine and dest machine.  The dest machine has both rl and
> fxp

You won't, this is a problem endemic to the PCI bus.  The problems with 
the RealTek chipset mostly have to do with CPU load doing real-world 
work, not silly-bugger tests.  This *is* why anyone who thinks they can 
make a real, reliable router by cramming a couple of PCI cards into a 
FreeBSD box is deluded.

-- 

        Where am I, and what am I doing in this handbasket?

Wes Peters                                               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 Mar 13  0:37:23 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E935E37B401
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 00:37:20 -0800 (PST)
Received: from cirb503493.alcatel.com.au (c18609.belrs1.nsw.optusnet.com.au [210.49.80.204])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 67ECD43FBF
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 00:37:18 -0800 (PST)
	(envelope-from peterjeremy@optushome.com.au)
Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])
	by cirb503493.alcatel.com.au (8.12.6/8.12.5) with ESMTP id h2D8bHiM008521;
	Thu, 13 Mar 2003 19:37:17 +1100 (EST)
	(envelope-from jeremyp@cirb503493.alcatel.com.au)
Received: (from jeremyp@localhost)
	by cirb503493.alcatel.com.au (8.12.6/8.12.5/Submit) id h2D8bAVe008520;
	Thu, 13 Mar 2003 19:37:10 +1100 (EST)
Date: Thu, 13 Mar 2003 19:37:10 +1100
From: Peter Jeremy <peterjeremy@optushome.com.au>
To: David Cuthbert <dacut@kanga.org>
Cc: hackers@FreeBSD.ORG
Subject: Re: first parameter to select
Message-ID: <20030313083710.GA8225@cirb503493.alcatel.com.au>
References: <3E702BCC.3030208@kanga.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E702BCC.3030208@kanga.org>
User-Agent: Mutt/1.4i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Thu, Mar 13, 2003 at 01:57:16AM -0500, David Cuthbert wrote:
>To be honest, I've never passed anything but FD_SETSIZE for this 
>parameter.  When I'm writing a performance critical server, I use poll() 
>instead.  It's faster

This is an interesting claim.  Do you have some pointers to back it up?
It would seem to be rather unreasonable to claim that poll() is faster
when (by your own admission) you've never used select() efficiently.
I could equally say that I always pass getdtablesize() as the second
argument of poll() and if I'm writing a performance-critical server,
I use select() instead - it's faster.

Effectively, the difference between poll() and select() is that poll()
uses an array with each element representing one file descriptor
whereas select() uses 1-3 bit arrays.  The underlying function to
test each FD within the kernel is the same in both cases (fo_poll()).
Any performance differences are therefore due to:
(1) The amount of data crossing the userland<->kernel barrier
(2) The time to scan the data to locate FD's of interest.

poll() optimises (2) at the expense of (1) - each FD requires 8 bytes to
be passed in and out of the kernel.

select() minimises (1) at the expense of (2) - though the actual
behaviour depends on the sparseness of the file descriptor sets (and
correctly setting nfds).  The FreeBSD implementation will also be less
efficient where the same file descriptor is set in more than one of
the FD sets.

In virtually all cases, poll() will need to copy more data in and out
of the kernel then select() would.  Likewise, in virtually all cases,
select() will need to scan more file descriptors than poll() does.
The overall performance comes down to the relative cost of copying
data vs testing bits.

> and I don't have to reinitialize the fd_set 
>bitmasks on each iteration.

This is 'convenience', not performance.  And this is offset by the
increased cost of updating the pollfd array when a connection is
closed.  I've found that in most of the servers I've written, the
actual events you need to test varies from iteration to iteration
in any case (eg you don't want to test for writable unless there
is currently some data to write).  I usually wind up scanning through
an internal list/array of connection structures/objects and creating
the fd_sets or pollfd array on the fly.

>  It's technically less portable, but I've
>never had an issue across Solaris, HP-UX, Linux, or FreeBSD. 

select() is the older mechanism, developed for BSD.  poll() is the
SystemV equivalent - and is therefore blessed by SVID etc.  (My guess
is that the API difference is more due to NIH than any technical
justification).

Peter

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


From owner-freebsd-hackers  Thu Mar 13  0:51: 6 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 12C9637B404
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 00:51:05 -0800 (PST)
Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C39D543FB1
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 00:51:03 -0800 (PST)
	(envelope-from brandt@fokus.fraunhofer.de)
Received: from beagle (beagle [193.175.132.100])
	by mailhub.fokus.fraunhofer.de (8.11.6/8.11.6) with ESMTP id h2D8p1M21147;
	Thu, 13 Mar 2003 09:51:01 +0100 (MET)
Date: Thu, 13 Mar 2003 09:51:01 +0100 (CET)
From: Harti Brandt <brandt@fokus.fraunhofer.de>
To: Yury Tarasievich <grog@grsu.by>
Cc: hackers@freebsd.org
Subject: Re: Are there any on-going projects on v4l porting?
In-Reply-To: <3E6F74AD.3000306@grsu.by>
Message-ID: <20030313094842.N641@beagle.fokus.fraunhofer.de>
References: <20030308015609.R680@kushnir1.kiev.ua> <3E6F74AD.3000306@grsu.by>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Wed, 12 Mar 2003, Yury Tarasievich wrote:

YT>At http://freebsddvb.narod.ru, there exists an adequately up-to-date
YT>port of linux DVB drivers, seemingly supporting DVB adapters up to rev.1.5.
YT>
YT>Regarding porting of V4L. I may be utterly wrong, but isn't the whole
YT>V4L/V4L2/V4L2-whatever thing rather made ad hoc, not really designed?
YT>Could something reincarnating BeOS (or even OS/2) multimedia subsystem
YT>be better?

Yes, last time I had a look at V4L2 it was utterly broken with regard
to ingeneering. Using a O_ flag to the open call to tell the system that
you are going to use only ioctl()s and stuff like that...

harti

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


From owner-freebsd-hackers  Thu Mar 13  0:53:35 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6904D37B401
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 00:53:34 -0800 (PST)
Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6514843F3F
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 00:53:33 -0800 (PST)
	(envelope-from brandt@fokus.fraunhofer.de)
Received: from beagle (beagle [193.175.132.100])
	by mailhub.fokus.fraunhofer.de (8.11.6/8.11.6) with ESMTP id h2D8rRM21554;
	Thu, 13 Mar 2003 09:53:27 +0100 (MET)
Date: Thu, 13 Mar 2003 09:53:27 +0100 (CET)
From: Harti Brandt <brandt@fokus.fraunhofer.de>
To: Dan Nelson <dnelson@allantgroup.com>
Cc: Yury Tarasievich <grog@grsu.by>, freebsd-hackers@FreeBSD.ORG
Subject: Re: Are there any on-going projects on v4l porting?
In-Reply-To: <20030312194736.GM34322@dan.emsphone.com>
Message-ID: <20030313095141.C641@beagle.fokus.fraunhofer.de>
References: <20030308015609.R680@kushnir1.kiev.ua> <3E6F74AD.3000306@grsu.by>
 <20030312194736.GM34322@dan.emsphone.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Wed, 12 Mar 2003, Dan Nelson wrote:

DN>In the last episode (Mar 12), Yury Tarasievich said:
DN>> At http://freebsddvb.narod.ru, there exists an adequately up-to-date
DN>> port of linux DVB drivers, seemingly supporting DVB adapters up to
DN>> rev.1.5.
DN>>
DN>> Regarding porting of V4L. I may be utterly wrong, but isn't the whole
DN>> V4L/V4L2/V4L2-whatever thing rather made ad hoc, not really designed?
DN>> Could something reincarnating BeOS (or even OS/2) multimedia
DN>> subsystem be better?
DN>
DN>I like the idea of putting this into the Xfree86 drivers and using the
DN>XVideo extension to drive everything.  that doesn't require kernel
DN>mods.  It does mean that you need to start X up to capture video,
DN>though.

The problem with this is probably the number of context switches and
copies or IPC you need to get a frame. With > 25 fps this is a problem.

harti
-- 
harti brandt,
http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private
brandt@fokus.fraunhofer.de, harti@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 Mar 13  1: 6:59 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2692F37B401
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 01:06:58 -0800 (PST)
Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C25F443F85
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 01:06:56 -0800 (PST)
	(envelope-from marck@rinet.ru)
Received: from localhost (localhost [127.0.0.1])
	by woozle.rinet.ru (8.12.8/8.12.8) with ESMTP id h2D96tJ5042335
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 12:06:55 +0300 (MSK)
	(envelope-from marck@rinet.ru)
Date: Thu, 13 Mar 2003 12:06:55 +0300 (MSK)
From: Dmitry Morozovsky <marck@rinet.ru>
To: hackers@FreeBSD.ORG
Subject: Re: FreeBSD-specific CVS: tagexpand question 
In-Reply-To: <20030312213135.B17741@woozle.rinet.ru>
Message-ID: <20030313115642.W39910@woozle.rinet.ru>
References: <20030312213135.B17741@woozle.rinet.ru>
X-NCC-RegID: ru.rinet
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Following up to myself:

On Wed, 12 Mar 2003, Dmitry Morozovsky wrote:

DM> Is there any way to tune FreeBSD-specific CVS (with CVSROOT/options support) to
DM> provide the following functionality:
DM>
DM> - ident keyword should be standard ($ Id $)
DM> - it should be expanded as ($ CVSHeader $) to repo-relative path

looking at rcs.c:3750+ it seems to me that exactly this functionality can't be
achieved without really ugly hacks. Or, am I overlooking something really
simple?

As always, thanks for cooperation.

Sincerely,
D.Marck                                   [DM5020, DM268-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------

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


From owner-freebsd-hackers  Thu Mar 13  1:34:48 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1177637B401
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 01:34:47 -0800 (PST)
Received: from park.rambler.ru (park.rambler.ru [81.19.64.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1C45F43F3F
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 01:34:45 -0800 (PST)
	(envelope-from is@rambler-co.ru)
Received: from is.park.rambler.ru (is.park.rambler.ru [81.19.64.102])
	by park.rambler.ru (8.12.6/8.12.6) with ESMTP id h2D9YZmF040826;
	Thu, 13 Mar 2003 12:34:35 +0300 (MSK)
Date: Thu, 13 Mar 2003 12:34:35 +0300 (MSK)
From: Igor Sysoev <is@rambler-co.ru>
X-Sender: is@is
To: Sean Hamilton <sh@bel.bc.ca>
Cc: hackers@FreeBSD.ORG
Subject: Re: first parameter to select
In-Reply-To: <000501c2e911$96ea79a0$d1d7e8d8@slugabed.org>
Message-ID: <Pine.BSF.4.21.0303131227100.91988-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Wed, 12 Mar 2003, Sean Hamilton wrote:

> What is the first parameter to select(2) for? Microsoft's select ignores it,
> and it does not appear to have any valid use since it only allows
> constraints on values which are assigned by the system.
> 
> Purely historic?

Winsock uses the integer array for fd_set instead of the bit array
as Unices do. Winsock socket's numbers are big enough, for example
I saw on NT as first created socket has number 96 and second has 42.
Bitmask is not effective for such numbers.


Igor Sysoev
http://sysoev.ru/en/


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


From owner-freebsd-hackers  Thu Mar 13  2:56: 2 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C813D37B401
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 02:56:00 -0800 (PST)
Received: from gvr.gvr.org (gvr.gvr.org [212.61.40.17])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6021843FDD
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 02:55:59 -0800 (PST)
	(envelope-from guido@gvr.org)
Received: by gvr.gvr.org (Postfix, from userid 657)
	id 8647C12; Thu, 13 Mar 2003 11:55:57 +0100 (CET)
Date: Thu, 13 Mar 2003 11:55:57 +0100
From: Guido van Rooij <guido@gvr.org>
To: John <jwd@bsdwins.com>
Cc: Hackers List <freebsd-hackers@freebsd.org>, wjw@withagen.nl
Subject: Re: magic symbolic links (ideas/patches?)
Message-ID: <20030313105557.GA84120@gvr.gvr.org>
References: <20030313003952.GA1800@BSDWins.Com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030313003952.GA1800@BSDWins.Com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

IIRC Willem-Jan Withagen has done this years ago.

I Cc ed him.

-Guido

On Wed, Mar 12, 2003 at 07:39:52PM -0500, John wrote:
> Hi Folks,
> 
>    I have a need to implement a highly specific variant usage of
> what are commonly referred to as magic symlinks, ie:
> 
>    /src -> /.src/$ARCH/src
> 
>    where $ARCH needs to come from the user environment.
> 
>    A related patchset from NetBSD (1995) can be seen here:
> 
> http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=1781
> 
>    In my specific implementation, the value of $ARCH will ALWAYS
> be 3 characters (Not having implemented anything yet, and to
> avoid possibly playing the userland game, I was thinking of
> adding a field to the proc structure and having the setenv/putenv
> functions place the value there via a sysctl, thus allowing a
> very simple interface... short sighted?).
> 
>    If anyone has any comments, or patches hanging around for
> this type of implementation, I would appreciate a pointer to them.
> 
> Many, Many Thanks,
> John
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message

-- 
Guido van Rooij		 	      |  Phone: ++31 653 994 773
Madison Gurkha, Technology Think-Tank |
guido@madison-gurkha.com 	      |  FreeBSD committer

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


From owner-freebsd-hackers  Thu Mar 13  7: 3: 2 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 236DA37B401
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 07:03:01 -0800 (PST)
Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [193.201.200.170])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 41C6F43F85
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 07:03:00 -0800 (PST)
	(envelope-from fanf@chiark.greenend.org.uk)
Received: from fanf by chiark.greenend.org.uk with local (Exim 3.12 #1)
	id 18tUEU-0001R8-00 (Debian); Thu, 13 Mar 2003 15:02:58 +0000
To: marck@rinet.ru
From: Tony Finch <dot@dotat.at>
Cc: hackers@freebsd.org
Subject: Re: FreeBSD-specific CVS: tagexpand question 
In-Reply-To: <20030312213135.B17741@woozle.rinet.ru>
Message-Id: <E18tUEU-0001R8-00@chiark.greenend.org.uk>
Date: Thu, 13 Mar 2003 15:02:58 +0000
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Dmitry Morozovsky <marck@rinet.ru> wrote:
>
>Is there any way to tune FreeBSD-specific CVS (with CVSROOT/options support) to
>provide the following functionality:
>- ident keyword should be standard ($ Id $)
>- it should be expanded as ($ CVSHeader $) to repo-relative path

Why do you want to do that? It seems like a bad idea to me -- you should
keep the semantics of CVS keywords constant, and you should keep per-
project keywords as distinctive as possible to avoid clashes as source
moves around.

Tony.
-- 
f.a.n.finch  <dot@dotat.at>  http://dotat.at/
THE WASH TO NORTH FORELAND: NORTHEAST 3 OR 4 OCCASIONALLY 5 VEERING EAST 3 OR
4 LATER. FAIR. GOOD. MODERATE, LOCALLY ROUGH AT FIRST IN NORTH, GRADUALLY
BECOMING SLIGHT TO MODERATE.

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


From owner-freebsd-hackers  Thu Mar 13  7:15:46 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 41ED237B401
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 07:15:42 -0800 (PST)
Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0FF6943FAF
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 07:15:41 -0800 (PST)
	(envelope-from marck@rinet.ru)
Received: from localhost (localhost [127.0.0.1])
	by woozle.rinet.ru (8.12.8/8.12.8) with ESMTP id h2DFFWJ5047120;
	Thu, 13 Mar 2003 18:15:32 +0300 (MSK)
	(envelope-from marck@rinet.ru)
Date: Thu, 13 Mar 2003 18:15:32 +0300 (MSK)
From: Dmitry Morozovsky <marck@rinet.ru>
To: Tony Finch <dot@dotat.at>
Cc: hackers@freebsd.org
Subject: Re: FreeBSD-specific CVS: tagexpand question 
In-Reply-To: <E18tUEU-0001R8-00@chiark.greenend.org.uk>
Message-ID: <20030313180755.Y46614@woozle.rinet.ru>
References: <E18tUEU-0001R8-00@chiark.greenend.org.uk>
X-NCC-RegID: ru.rinet
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Thu, 13 Mar 2003, Tony Finch wrote:

TF> >Is there any way to tune FreeBSD-specific CVS (with CVSROOT/options support) to
TF> >provide the following functionality:
TF> >- ident keyword should be standard ($ Id $)
TF> >- it should be expanded as ($ CVSHeader $) to repo-relative path
TF>
TF> Why do you want to do that? It seems like a bad idea to me -- you should
TF> keep the semantics of CVS keywords constant, and you should keep per-
TF> project keywords as distinctive as possible to avoid clashes as source
TF> moves around.

Well, AFAIThink the semantics do not change -- just extends a bit, and
thus allow to be extensively checked for example by FreeBSD-styled CVSROOT
scripts like commit_prep.pl

BTW, I've written a little patch to CVS similar to peter's patches: it adds
idexpmode options to CVSROOT/options -- attached just in case anyone
interested.

Sincerely,
D.Marck                                   [DM5020, DM268-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------



# $Id: FreeBSD/Patches/cvs-idexpmode.patch,v 1.1 2003/03/13 12:53:15 marck Exp $
#
#-DSC-#	idexpmode option for CVS

This patch adds new option for cvs. You can specify idexpmode=<MODE>
in CVSROOT/options admin file to select $ Id $ RCS keyword expansion mode.

MODE may be on of the following:

	Id		last path component; default
	Header		full path including repository root
	CVSHeader	path relative to repository root

Index: contrib/cvs/src/main.c
===================================================================
RCS file: /home/ncvs/src/contrib/cvs/src/main.c,v
retrieving revision 1.18.2.4
diff -u -r1.18.2.4 main.c
--- contrib/cvs/src/main.c	19 Dec 2002 21:17:56 -0000	1.18.2.4
+++ contrib/cvs/src/main.c	13 Mar 2003 12:26:14 -0000
@@ -1244,6 +1244,12 @@
 		rcs_incexc = buf + 10;
 		RCS_setincexc(rcs_incexc);
 	    }
+	    if (!strncmp(buf, "idexpmode=", 10)) {
+		char *rcs_idexpmode;
+
+		rcs_idexpmode = buf + 10;
+		RCS_setidexpmode(rcs_idexpmode);
+	    }
 	    /*
 	     * OpenBSD has a "umask=" and "dlimit=" command, we silently
 	     * ignore them here since they are not much use to us.  cvsumask
Index: contrib/cvs/src/rcs.c
===================================================================
RCS file: /home/ncvs/src/contrib/cvs/src/rcs.c,v
retrieving revision 1.19.2.5
diff -u -r1.19.2.5 rcs.c
--- contrib/cvs/src/rcs.c	21 Jan 2003 22:26:44 -0000	1.19.2.5
+++ contrib/cvs/src/rcs.c	13 Mar 2003 12:26:14 -0000
@@ -3519,6 +3519,7 @@
     KEYWORD_LOCALID
 };
 enum keyword keyword_local = KEYWORD_ID;
+enum keyword keyword_idexmode = KEYWORD_ID;

 /* Convert an RCS date string into a readable string.  This is like
    the RCS date2str function.  */
@@ -3757,11 +3758,15 @@
 		    old_path = NULL;
 		    if (kw == KEYWORD_HEADER ||
 			    (kw == KEYWORD_LOCALID &&
-			     keyword_local == KEYWORD_HEADER))
+			     keyword_local == KEYWORD_HEADER) ||
+			    (kw == KEYWORD_ID &&
+			     keyword_idexmode == KEYWORD_HEADER))
 			path = rcs->path;
 		    else if (kw == KEYWORD_CVSHEADER ||
 			     (kw == KEYWORD_LOCALID &&
-			      keyword_local == KEYWORD_CVSHEADER))
+			      keyword_local == KEYWORD_CVSHEADER) ||
+			     (kw == KEYWORD_ID &&
+			      keyword_idexmode == KEYWORD_CVSHEADER))
 			path = getfullCVSname(rcs->path, &old_path);
 		    else
 			path = last_component (rcs->path);
@@ -8627,6 +8632,25 @@
 	    error(1, 0, "Unknown LocalId mode: %s", key);
     }
     free(copy);
+}
+
+void
+RCS_setidexpmode (arg)
+    const char *arg;
+{
+    char *key;
+
+    key = xstrdup(arg);
+    if (!strcmp(key, keywords[KEYWORD_ID].string))
+	keyword_idexmode = KEYWORD_ID;
+    else if (!strcmp(key, keywords[KEYWORD_HEADER].string))
+	keyword_idexmode = KEYWORD_HEADER;
+    else if (!strcmp(key, keywords[KEYWORD_CVSHEADER].string))
+	keyword_idexmode = KEYWORD_CVSHEADER;
+    else
+	error(1, 0, "Unknown id expand mode: %s", key);
+
+    free(key);
 }

 void
Index: contrib/cvs/src/rcs.h
===================================================================
RCS file: /home/ncvs/src/contrib/cvs/src/rcs.h,v
retrieving revision 1.7.2.4
diff -u -r1.7.2.4 rcs.h
--- contrib/cvs/src/rcs.h	19 Dec 2002 21:17:56 -0000	1.7.2.4
+++ contrib/cvs/src/rcs.h	13 Mar 2003 12:26:14 -0000
@@ -243,6 +243,7 @@
 			enum rcs_delta_op, char **, size_t *,
 			char **, size_t *));
 void RCS_setincexc PROTO ((const char *arg));
+void RCS_setidexpmode PROTO ((const char *arg));
 void RCS_setlocalid PROTO ((const char *arg));
 char *make_file_label PROTO ((char *, char *, RCSNode *));


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


From owner-freebsd-hackers  Thu Mar 13  8:51:50 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id F387B37B401
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 08:51:48 -0800 (PST)
Received: from mail.rdslink.ro (mail.rdslink.ro [193.231.236.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 3058B43FCB
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 08:51:47 -0800 (PST)
	(envelope-from enache@rdslink.ro)
Received: (qmail 30063 invoked from network); 13 Mar 2003 16:52:40 -0000
Received: from unknown (HELO ratsnest.hole) (10.100.0.67)
  by mail.rdslink.ro with SMTP; 13 Mar 2003 16:52:40 -0000
Received: from ratsnest.hole (localhost [127.0.0.1])
	by ratsnest.hole (8.12.5/8.12.5) with ESMTP id h2DGoIAi000711;
	Thu, 13 Mar 2003 18:50:18 +0200
Received: (from adi@localhost)
	by ratsnest.hole (8.12.5/8.12.5/Submit) id h2DGoIpO000709;
	Thu, 13 Mar 2003 18:50:18 +0200
Date: Thu, 13 Mar 2003 18:50:18 +0200
From: Enache Adrian <enache@rdslink.ro>
To: Peter Jeremy <peterjeremy@optushome.com.au>
Cc: David Cuthbert <dacut@kanga.org>, hackers@FreeBSD.ORG
Subject: Re: first parameter to select
Message-ID: <20030313165018.GA703@ratsnest.hole>
References: <3E702BCC.3030208@kanga.org> <20030313083710.GA8225@cirb503493.alcatel.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030313083710.GA8225@cirb503493.alcatel.com.au>
User-Agent: Mutt/1.4i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Thu, Mar 13, 2003 at 07:37:10PM +1100, Peter Jeremy wrote:
> On Thu, Mar 13, 2003 at 01:57:16AM -0500, David Cuthbert wrote:
> >To be honest, I've never passed anything but FD_SETSIZE for this 
> >parameter.  When I'm writing a performance critical server, I use poll() 
> >instead.  It's faster
> 
> This is an interesting claim.  Do you have some pointers to back it up?
> It would seem to be rather unreasonable to claim that poll() is faster
> when (by your own admission) you've never used select() efficiently.
> I could equally say that I always pass getdtablesize() as the second
> argument of poll() and if I'm writing a performance-critical server,
> I use select() instead - it's faster.

I have no benchmarks, but judging after the way things are implemented
in the FreeBSD kernel, select() is definitely faster.

Please someone explain me what is meant in select(2) by:

  If nfds is greater than the number of open files, select() is not guaran-
  teed to examine the unused file descriptors.   For historical reasons,
  select() will always examine the first 256 descriptors.

Should it be that select() examines also _closed_ file descriptors which
are in the bitmaps ( closed_fd < nfds && closed_fd < 256 ) ?

(Of course, it won't do that :))

Regards
Adi

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


From owner-freebsd-hackers  Thu Mar 13  9: 5:53 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2E60F37B401
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 09:05:52 -0800 (PST)
Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E0E9A43FBD
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 09:05:50 -0800 (PST)
	(envelope-from brandt@fokus.fraunhofer.de)
Received: from beagle (beagle [193.175.132.100])
	by mailhub.fokus.fraunhofer.de (8.11.6/8.11.6) with ESMTP id h2DH5WM11226;
	Thu, 13 Mar 2003 18:05:32 +0100 (MET)
Date: Thu, 13 Mar 2003 18:05:32 +0100 (CET)
From: Harti Brandt <brandt@fokus.fraunhofer.de>
To: Enache Adrian <enache@rdslink.ro>
Cc: Peter Jeremy <peterjeremy@optushome.com.au>,
	David Cuthbert <dacut@kanga.org>, hackers@FreeBSD.ORG
Subject: Re: first parameter to select
In-Reply-To: <20030313165018.GA703@ratsnest.hole>
Message-ID: <20030313175543.E641@beagle.fokus.fraunhofer.de>
References: <3E702BCC.3030208@kanga.org> <20030313083710.GA8225@cirb503493.alcatel.com.au>
 <20030313165018.GA703@ratsnest.hole>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Thu, 13 Mar 2003, Enache Adrian wrote:

EA>On Thu, Mar 13, 2003 at 07:37:10PM +1100, Peter Jeremy wrote:
EA>> On Thu, Mar 13, 2003 at 01:57:16AM -0500, David Cuthbert wrote:
EA>> >To be honest, I've never passed anything but FD_SETSIZE for this
EA>> >parameter.  When I'm writing a performance critical server, I use poll()
EA>> >instead.  It's faster
EA>>
EA>> This is an interesting claim.  Do you have some pointers to back it up?
EA>> It would seem to be rather unreasonable to claim that poll() is faster
EA>> when (by your own admission) you've never used select() efficiently.
EA>> I could equally say that I always pass getdtablesize() as the second
EA>> argument of poll() and if I'm writing a performance-critical server,
EA>> I use select() instead - it's faster.
EA>
EA>I have no benchmarks, but judging after the way things are implemented
EA>in the FreeBSD kernel, select() is definitely faster.
EA>
EA>Please someone explain me what is meant in select(2) by:
EA>
EA>  If nfds is greater than the number of open files, select() is not guaran-
EA>  teed to examine the unused file descriptors.   For historical reasons,
EA>  select() will always examine the first 256 descriptors.
EA>
EA>Should it be that select() examines also _closed_ file descriptors which
EA>are in the bitmaps ( closed_fd < nfds && closed_fd < 256 ) ?

Isn't that what the EBADF return is for?

EA>(Of course, it won't do that :))

harti
-- 
harti brandt,
http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private
brandt@fokus.fraunhofer.de, harti@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 Mar 13  9:52:14 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6107837B401
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 09:52:13 -0800 (PST)
Received: from grsu.by (grsu.by [194.158.202.115])
	by mx1.FreeBSD.org (Postfix) with SMTP id 0B73B43FCB
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 09:52:12 -0800 (PST)
	(envelope-from grog@grsu.by)
Received: (qmail 39759 invoked from network); 13 Mar 2003 17:50:26 -0000
Received: from unknown (HELO grsu.by) (grog@195.50.13.205)
  by grsu.by with SMTP; 13 Mar 2003 17:50:26 -0000
Message-ID: <3E70C20C.1060100@grsu.by>
Date: Thu, 13 Mar 2003 19:38:20 +0200
From: Yury Tarasievich <grog@grsu.by>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20020829
X-Accept-Language: be, en
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
Subject: Re: Are there any on-going projects on v4l porting?
References: <20030308015609.R680@kushnir1.kiev.ua> <3E6F74AD.3000306@grsu.by> <20030312194736.GM34322@dan.emsphone.com> <20030313095141.C641@beagle.fokus.fraunhofer.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Performance is important, but I'd call having good design even more 
important, righteous API included. Having (potential) application 
developers mess with ioctl's and such doesn't seem good to me.
Now, to not to reimplement the wheel, I'd repeat the suggestion of 
basically copying and adapting something for start. Further details 
should be kept off this list, I think, perhaps in [-multimedia].

Harti Brandt wrote:

>On Wed, 12 Mar 2003, Dan Nelson wrote:
>
>DN>In the last episode (Mar 12), Yury Tarasievich said:
>DN>> At http://freebsddvb.narod.ru, there exists an adequately up-to-date
>DN>> port of linux DVB drivers, seemingly supporting DVB adapters up to
>DN>> rev.1.5.
>DN>>
>DN>> Regarding porting of V4L. I may be utterly wrong, but isn't the whole
>DN>> V4L/V4L2/V4L2-whatever thing rather made ad hoc, not really designed?
>DN>> Could something reincarnating BeOS (or even OS/2) multimedia
>DN>> subsystem be better?
>DN>
>DN>I like the idea of putting this into the Xfree86 drivers and using the
>DN>XVideo extension to drive everything.  that doesn't require kernel
>DN>mods.  It does mean that you need to start X up to capture video,
>DN>though.
>
>The problem with this is probably the number of context switches and
>copies or IPC you need to get a frame. With > 25 fps this is a problem.
>
>harti
>  
>



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


From owner-freebsd-hackers  Thu Mar 13  9:55:24 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2A30837B401
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 09:55:23 -0800 (PST)
Received: from mail.rdslink.ro (mail.rdslink.ro [193.231.236.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 652C843FCB
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 09:55:21 -0800 (PST)
	(envelope-from enache@rdslink.ro)
Received: (qmail 6667 invoked from network); 13 Mar 2003 17:56:17 -0000
Received: from unknown (HELO ratsnest.hole) (81.196.245.158)
  by mail.rdslink.ro with SMTP; 13 Mar 2003 17:56:17 -0000
Received: from ratsnest.hole (localhost [127.0.0.1])
	by ratsnest.hole (8.12.5/8.12.5) with ESMTP id h2DHxv8k000818;
	Thu, 13 Mar 2003 19:59:57 +0200
Received: (from adi@localhost)
	by ratsnest.hole (8.12.5/8.12.5/Submit) id h2DHxvV9000816;
	Thu, 13 Mar 2003 19:59:57 +0200
Date: Thu, 13 Mar 2003 19:59:57 +0200
From: Enache Adrian <enache@rdslink.ro>
To: Harti Brandt <brandt@fokus.fraunhofer.de>
Cc: Enache Adrian <enache@rdslink.ro>,
	Peter Jeremy <peterjeremy@optushome.com.au>,
	David Cuthbert <dacut@kanga.org>, hackers@FreeBSD.ORG
Subject: Re: first parameter to select
Message-ID: <20030313175957.GA810@ratsnest.hole>
References: <3E702BCC.3030208@kanga.org> <20030313083710.GA8225@cirb503493.alcatel.com.au> <20030313165018.GA703@ratsnest.hole> <20030313175543.E641@beagle.fokus.fraunhofer.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030313175543.E641@beagle.fokus.fraunhofer.de>
User-Agent: Mutt/1.4i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Thu, Mar 13, 2003 at 06:05:32PM +0100, Harti Brandt wrote:
> EA>Should it be that select() examines also _closed_ file descriptors which
> EA>are in the bitmaps ( closed_fd < nfds && closed_fd < 256 ) ?
> 
> Isn't that what the EBADF return is for?

Oops. examine <=> poll in my brain when I read that.

Regards
Adi

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


From owner-freebsd-hackers  Thu Mar 13  9:59:17 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8EC4637B401
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 09:59:16 -0800 (PST)
Received: from perrin.int.nxad.com (internal.ext.nxad.com [69.1.70.251])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2E36B43FB1
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 09:59:16 -0800 (PST)
	(envelope-from sean@perrin.int.nxad.com)
Received: by perrin.int.nxad.com (Postfix, from userid 1001)
	id B34B221085; Thu, 13 Mar 2003 09:58:41 -0800 (PST)
Date: Thu, 13 Mar 2003 09:58:41 -0800
From: Sean Chittenden <sean@chittenden.org>
To: Peter Jeremy <peterjeremy@optushome.com.au>
Cc: David Cuthbert <dacut@kanga.org>, hackers@FreeBSD.ORG
Subject: Re: first parameter to select
Message-ID: <20030313175841.GF79234@perrin.int.nxad.com>
References: <3E702BCC.3030208@kanga.org> <20030313083710.GA8225@cirb503493.alcatel.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030313083710.GA8225@cirb503493.alcatel.com.au>
User-Agent: Mutt/1.4i
X-PGP-Key: finger seanc@FreeBSD.org
X-PGP-Fingerprint: 3849 3760 1AFE 7B17 11A0  83A6 DD99 E31F BC84 B341
X-Web-Homepage: http://sean.chittenden.org/
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

> >To be honest, I've never passed anything but FD_SETSIZE for this
> >parameter.  When I'm writing a performance critical server, I use
> >poll() instead.  It's faster
> 
> This is an interesting claim.  Do you have some pointers to back it
> up?

http://www.kegel.com/dkftpbench/Poller_bench.html#results

If you want fast, use kqueue().  -sc

-- 
Sean Chittenden

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


From owner-freebsd-hackers  Thu Mar 13 10:13:33 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E138737B401
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 10:13:31 -0800 (PST)
Received: from diana.northnetworks.ca (att-ws20.switchview.com [216.13.70.20])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CE23E43F85
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 10:13:30 -0800 (PST)
	(envelope-from iaccounts@northnetworks.ca)
Received: from localhost (iaccounts@localhost)
	by diana.northnetworks.ca (8.11.6/8.11.6) with ESMTP id h2DIDTu74427
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 13:13:29 -0500 (EST)
	(envelope-from iaccounts@northnetworks.ca)
Date: Thu, 13 Mar 2003 13:13:29 -0500 (EST)
From: IAccounts <iaccounts@northnetworks.ca>
To: freebsd-hackers@freebsd.org
Subject: ether_input: drop bdg packet
Message-ID: <20030313130518.I50632-100000@diana.northnetworks.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

I have 5.0 running as a bridge/ipfw firewall configuration, which is
seemingly working very well in an ISP environment. However, there is
something that I don't know if it is an error, or normal. On the console,
I get the following message many times per second:

ether_input: drop bdg packet

I am suspecting that this is just a logging issue within part of the
bridge/ipfw code, but I would like some feeback if possible to what
exactly this is for.

I have looked through bridge.c, ipfw.c, bpf.c, bpf_filter.c and many
others for the answer. There is much reference to DROP in bridge.c, but
nothing that looks like the console message. I would really like to find
out why this is happening, and how to make some changes, so I would
appreciate it if someone could point me in the direction of the code for
this as opposed to or in addition to the answer.

Tks greatly!

Steve



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


From owner-freebsd-hackers  Thu Mar 13 11: 3:52 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3F6F237B401
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 11:03:50 -0800 (PST)
Received: from flood.neolinear.com (n5.neolinear.com [208.20.218.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8259043FAF
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 11:03:49 -0800 (PST)
	(envelope-from dacut@kanga.org)
Received: from ampere ([192.9.200.88])
	by flood.neolinear.com with esmtp (Exim 3.35 #1 (Debian))
	id 18tXu5-0007Cq-00
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 13:58:09 -0500
Received: from vodka ([192.9.200.61] helo=kanga.org)
	by ampere with esmtp (Exim 4.10)
	id 18tXwf-0006bx-00
	for hackers@freebsd.org; Thu, 13 Mar 2003 14:00:49 -0500
Message-ID: <3E70D561.1080001@kanga.org>
Date: Thu, 13 Mar 2003 14:00:49 -0500
From: David Cuthbert <dacut@kanga.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: Re: first parameter to select
References: <3E702BCC.3030208@kanga.org> <20030313083710.GA8225@cirb503493.alcatel.com.au>
In-Reply-To: <20030313083710.GA8225@cirb503493.alcatel.com.au>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Peter Jeremy wrote:
> On Thu, Mar 13, 2003 at 01:57:16AM -0500, David Cuthbert wrote:
>>To be honest, I've never passed anything but FD_SETSIZE for this 
>>parameter.  When I'm writing a performance critical server, I use poll() 
>>instead.  It's faster
> 
> This is an interesting claim.  Do you have some pointers to back it up?
> It would seem to be rather unreasonable to claim that poll() is faster
> when (by your own admission) you've never used select() efficiently.
> I could equally say that I always pass getdtablesize() as the second
> argument of poll() and if I'm writing a performance-critical server,
> I use select() instead - it's faster.

Admittedly, my experience is dated and refers to implementing servers on 
Solaris.  The man page for select(3c) on Solaris explicitly states:

"The poll(2) function is preferred over this function.  It must be used 
when the number of descriptors exceeds FD_SETSIZE."

I'll profess my ignorance: I have no idea how well this maps to FreeBSD. 
  On Solaris (well, with whatever combination of patchlevels we and our 
customers were running), you could time the difference with a stopwatch.

Though we did have some combinations of patchlevels where I'd swear it 
was faster if we communicated by telegraph. :-)

(Just now seeing the benchmark posted... hm... it's possible that I'm 
saying poll() and we ended up using /dev/poll...)

> In virtually all cases, poll() will need to copy more data in and out
> of the kernel then select() would.  Likewise, in virtually all cases,
> select() will need to scan more file descriptors than poll() does.
> The overall performance comes down to the relative cost of copying
> data vs testing bits.

Not sure what you mean by virtually all cases.

Given that a poll() descriptor is 12 bytes and fd_set is usually at 
least 128 bytes (does select() copy the entire fd_set?  I believe this 
is the case, but don't have access to the source atm), the savings kicks 
in at 12 descriptors.

We usually had no more than 6 connections (these were compute servers, 
not web servers), so YMMV.  At any rate, I'd argue that the time 
occupied by copying/scanning/setting is far overshadowed by the time 
spent in I/O.

> select() is the older mechanism, developed for BSD.  poll() is the
> SystemV equivalent - and is therefore blessed by SVID etc.  (My guess
> is that the API difference is more due to NIH than any technical
> justification).

Heh.  Yeah, there's definitely a case of "we know X better and thus 
focused all our optimisation efforts on X" in operation here.

I'd still argue that, when porting a program across platforms, the 
behaviour of select() is likely to be more consistent than poll(), 
usually (always?) in the cases where something unusual has occurred on a 
descriptor.


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


From owner-freebsd-hackers  Thu Mar 13 11:22:11 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1366237B404
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 11:22:09 -0800 (PST)
Received: from jkh-gw.queasyweasel.com (adsl-64-173-3-158.dsl.sntc01.pacbell.net [64.173.3.158])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AA24943F75
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 11:22:07 -0800 (PST)
	(envelope-from jkh@queasyweasel.com)
Received: from queasyweasel.com (narcissus.freebsd.com [64.173.15.99])
	by jkh-gw.queasyweasel.com (8.12.6/8.12.5) with ESMTP id h2DJLUsg034758;
	Thu, 13 Mar 2003 11:21:31 -0800 (PST)
	(envelope-from jkh@queasyweasel.com)
Date: Thu, 13 Mar 2003 11:22:19 -0800
Subject: Re: magic symbolic links (ideas/patches?)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: John <jwd@bsdwins.com>,
	Hackers List <freebsd-hackers@FreeBSD.ORG>, wjw@withagen.nlm,
	dg@root.com
To: Guido van Rooij <guido@gvr.org>
From: Jordan K Hubbard <jkh@queasyweasel.com>
In-Reply-To: <20030313105557.GA84120@gvr.gvr.org>
Message-Id: <1B9E0D7C-5589-11D7-B1F6-000393BB9222@queasyweasel.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

So did David Greenman.   He did a fully general variant symbolic link 
implementation but never, AFAIK, released it.  David? :-)

- Jordan

On Thursday, March 13, 2003, at 02:55 AM, Guido van Rooij wrote:

> IIRC Willem-Jan Withagen has done this years ago.
>
> I Cc ed him.
>
> -Guido
>
> On Wed, Mar 12, 2003 at 07:39:52PM -0500, John wrote:
>> Hi Folks,
>>
>>    I have a need to implement a highly specific variant usage of
>> what are commonly referred to as magic symlinks, ie:
>>
>>    /src -> /.src/$ARCH/src
>>
>>    where $ARCH needs to come from the user environment.
>>
>>    A related patchset from NetBSD (1995) can be seen here:
>>
>> http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=1781
>>
>>    In my specific implementation, the value of $ARCH will ALWAYS
>> be 3 characters (Not having implemented anything yet, and to
>> avoid possibly playing the userland game, I was thinking of
>> adding a field to the proc structure and having the setenv/putenv
>> functions place the value there via a sysctl, thus allowing a
>> very simple interface... short sighted?).
>>
>>    If anyone has any comments, or patches hanging around for
>> this type of implementation, I would appreciate a pointer to them.
>>
>> Many, Many Thanks,
>> John
>>
>> To Unsubscribe: send mail to majordomo@FreeBSD.org
>> with "unsubscribe freebsd-hackers" in the body of the message
>
> -- 
> Guido van Rooij		 	      |  Phone: ++31 653 994 773
> Madison Gurkha, Technology Think-Tank |
> guido@madison-gurkha.com 	      |  FreeBSD committer
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
>
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer


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


From owner-freebsd-hackers  Thu Mar 13 11:43:15 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 45EDE37B401
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 11:43:14 -0800 (PST)
Received: from mail.rdslink.ro (mail.rdslink.ro [193.231.236.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id BA50B43F75
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 11:43:12 -0800 (PST)
	(envelope-from enache@rdslink.ro)
Received: (qmail 7582 invoked from network); 13 Mar 2003 19:44:07 -0000
Received: from unknown (HELO ratsnest.hole) (81.196.245.3)
  by mail.rdslink.ro with SMTP; 13 Mar 2003 19:44:07 -0000
Received: from ratsnest.hole (localhost [127.0.0.1])
	by ratsnest.hole (8.12.5/8.12.5) with ESMTP id h2DJmoiN000971;
	Thu, 13 Mar 2003 21:48:50 +0200
Received: (from adi@localhost)
	by ratsnest.hole (8.12.5/8.12.5/Submit) id h2DJmow8000969;
	Thu, 13 Mar 2003 21:48:50 +0200
Date: Thu, 13 Mar 2003 21:48:50 +0200
From: Enache Adrian <enache@rdslink.ro>
To: David Cuthbert <dacut@kanga.org>
Cc: hackers@freebsd.org
Subject: Re: first parameter to select
Message-ID: <20030313194850.GA899@ratsnest.hole>
References: <3E702BCC.3030208@kanga.org> <20030313083710.GA8225@cirb503493.alcatel.com.au> <3E70D561.1080001@kanga.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E70D561.1080001@kanga.org>
User-Agent: Mutt/1.4i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Thu, Mar 13, 2003 at 02:00:49PM -0500, David Cuthbert wrote:
> Admittedly, my experience is dated and refers to implementing servers on 
> Solaris.  The man page for select(3c) on Solaris explicitly states:
> 
> "The poll(2) function is preferred over this function.  It must be used 
> when the number of descriptors exceeds FD_SETSIZE."

IIRC, in Solaris select() isn't a system call, but a library call
emulated in userland on top of poll(2). 
(I could be wrong, I never really used Solaris ).

Regards
Adi

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


From owner-freebsd-hackers  Thu Mar 13 11:44:37 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 77C1D37B404
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 11:44:36 -0800 (PST)
Received: from tinker.exit.com (tinker.exit.com [206.223.0.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1EC4243F75
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 11:44:33 -0800 (PST)
	(envelope-from frank@exit.com)
Received: from realtime.exit.com (realtime [206.223.0.5])
	by tinker.exit.com (8.12.7/8.12.6) with ESMTP id h2DJiVpP042724;
	Thu, 13 Mar 2003 11:44:32 -0800 (PST)
	(envelope-from frank@exit.com)
Received: from realtime.exit.com (localhost [127.0.0.1])
	by realtime.exit.com (8.12.6/8.12.6) with ESMTP id h2DJiVQu054554;
	Thu, 13 Mar 2003 11:44:31 -0800 (PST)
	(envelope-from frank@realtime.exit.com)
Received: (from frank@localhost)
	by realtime.exit.com (8.12.7/8.12.7/Submit) id h2DJiV7Q054553;
	Thu, 13 Mar 2003 11:44:31 -0800 (PST)
From: Frank Mayhar <frank@exit.com>
Message-Id: <200303131944.h2DJiV7Q054553@realtime.exit.com>
Subject: Re: first parameter to select
In-Reply-To: <20030313194850.GA899@ratsnest.hole>
To: Enache Adrian <enache@rdslink.ro>
Date: Thu, 13 Mar 2003 11:44:31 -0800 (PST)
Cc: David Cuthbert <dacut@kanga.org>, hackers@FreeBSD.ORG
Reply-To: frank@exit.com
X-Copyright0: Copyright 2003 Frank Mayhar.  All Rights Reserved.
X-Copyright1: Permission granted for electronic reproduction as Usenet News or
 email only.
X-Mailer: ELM [version 2.4ME+ PL99b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Enache Adrian wrote:
> IIRC, in Solaris select() isn't a system call, but a library call
> emulated in userland on top of poll(2). 
> (I could be wrong, I never really used Solaris ).

Dunno about Solaris but that's certainly true in Unixware.
-- 
Frank Mayhar frank@exit.com	http://www.exit.com/
Exit Consulting                 http://www.gpsclock.com/

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


From owner-freebsd-hackers  Thu Mar 13 11:45:29 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0099337B401
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 11:45:28 -0800 (PST)
Received: from 66-162-33-178.gen.twtelecom.net (66-162-33-181.gen.twtelecom.net [66.162.33.181])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 525A743F75
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 11:45:27 -0800 (PST)
	(envelope-from anshuman@expertcity.com)
Received: from [10.4.2.229] (helo=KANWAR2K)
	by 66-162-33-178.gen.twtelecom.net with esmtp (Exim 3.22 #4)
	id 18tYdr-0001Mv-00
	for freebsd-hackers@FreeBSD.ORG; Thu, 13 Mar 2003 11:45:27 -0800
Date: Thu, 13 Mar 2003 11:46:39 -0800 (Pacific Standard Time)
From: Anshuman Kanwar <anshuman@expertcity.com>
To: freebsd-hackers@FreeBSD.ORG
Subject: jumpstart for freebsd.
In-Reply-To: <1B9E0D7C-5589-11D7-B1F6-000393BB9222@queasyweasel.com>
Message-ID: <Pine.WNT.4.44.0303131141530.2964-100000@KANWAR2K>
X-X-Sender: anshuman@dopey.corp.expertcity.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


Greetings,

I've spent most of last year automating the installation of FreeBSD
systems at my workplace. I regularly have to install/upgrade FreeBSD at
remote datacenters on multiple machines.

We've been using 4.2 through 4.6.2 and plan to move to 4.8 as soon as it
is out. Doing the 'install/customizing the kernel/slapping on config
files'routine was taking too much overhead through all these upgrades.

Having worked with Solaris, I really appreciated the ease it offered to
SysAdmins like me with its setup_install_server and add_install_client
scripts.

As a result of all the above, I wrote a set of perl scripts that do a very
similar job for FreeBSD. The idea is:

1) make it easy to deploy large numbers of FreeBSD in various physical
locations
2) post-install configuration should be zero or minimum
3) each machine and each location can have a set of properties, these
should be correctly installed. (e.g. unique IP address for each machine,
custom ntp.conf for each location...)
4) maintain the identity (and maybe some data) of a machine across
upgrades (e.g. same network config before and after OS upgrade, even
though the disk has just been wiped)
5) be able to add custom packages/extend functionality to the install
system (e.g. custom kernel, funky login banner)
6) and most importantly...make machine downtime for upgrade as close to
the time required for copying the OS as possible :)

My scripts are just wrappers around DHCP/TFTP/NFS/pxeboot/sysinstall
script bits, that are already present and well documented.

If there is any interest in this work, I will be more than happy to
see it become one of the ways of installing FreeBSD. Of course, some
modifications would be required to make these scripts more generic, robust
and user
friendly.

The questions I have are:
1) Is this duplication of any prev. work ?
2) If no then how should I go about trying to integrate the code into
FreeBSD?

Thanks for your time,
Ansh Kanwar.




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


From owner-freebsd-hackers  Thu Mar 13 11:51: 7 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5BB2037B401
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 11:51:06 -0800 (PST)
Received: from pan.gwi.net (pan.gwi.net [207.5.128.165])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5EA6143F85
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 11:51:05 -0800 (PST)
	(envelope-from jcoombs@gwi.net)
Received: from junker.gwi (blake.gwi.net [207.5.142.8])
	by pan.gwi.net (8.12.6/8.12.6) with ESMTP id h2DJp40w021347
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 14:51:04 -0500 (EST)
	(envelope-from jcoombs@gwi.net)
From: Joshua Coombs <jcoombs@gwi.net>
Reply-To: jcoombs@gwi.net
To: freebsd-hackers@freebsd.org
Subject: Re: Realtek
Date: Thu, 13 Mar 2003 14:51:03 -0500
User-Agent: KMail/1.5
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200303131451.03953.jcoombs@gwi.net>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

I know some fxp's, along with others can offload parts of tcp to the card 
off the host cpu.  Given the speeds of current machines, is this really a 
gain or does it test out that the card is actually slower than line rate in 
which case offloading is actually a penalty?

Also interesting to hear the fxp's can't push the raw packet rates xl's can, 
anyone have any links with detailed benches covering the subject?

Joshua Coombs

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


From owner-freebsd-hackers  Thu Mar 13 12:19:11 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 326BB37B404
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 12:19:09 -0800 (PST)
Received: from creme-brulee.marcuscom.com (rdu57-17-158.nc.rr.com [66.57.17.158])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1E21643FB1
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 12:19:06 -0800 (PST)
	(envelope-from marcus@marcuscom.com)
Received: from [10.2.1.4] (vpn-client-4.marcuscom.com [10.2.1.4])
	by creme-brulee.marcuscom.com (8.12.8/8.12.8) with ESMTP id h2DKIRrI021046
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 15:18:27 -0500 (EST)
	(envelope-from marcus@marcuscom.com)
Subject: Question on gcc linker and -pthread
From: Joe Marcus Clarke <marcus@marcuscom.com>
To: hackers@freebsd.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-nDpBr0qyRi9GSsG+IAPg"
Organization: MarcusCom, Inc.
Message-Id: <1047586732.84063.10.camel@gyros>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 
Date: 13 Mar 2003 15:18:52 -0500
X-Spam-Status: No, hits=-6.0 required=5.0
	tests=HOT_NASTY,PGP_SIGNATURE_2
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


--=-nDpBr0qyRi9GSsG+IAPg
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I've noticed something I think is strange with gcc, the -shared flag,
and -pthread on -STABLE.  I'm hoping someone can enlighten me as to why
this happens or if it's a bug.  If I compile something with the
following command, I do not see libc_r.so linked in the resulting
object:

cc -shared -pthread -o xxx.so xxx.c

However, if I replace -pthread with -lc_r, it works.  Also, if I change
the command to:

cc -Wl,-shared -pthread -o xxx.so xxx.c

I also see libc_r.so linked in.  Is this expected behavior?  libtool
seems to like the former -shared syntax which is causing some problems
with some GTK themes.  Thanks.

Joe

--=20
PGP Key : http://www.marcuscom.com/pgp.asc



--=-nDpBr0qyRi9GSsG+IAPg
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQA+cOerb2iPiv4Uz4cRAteDAJwNg6RB/LeT/3S89KYeSZin0XMZSQCfUSZA
M28+1btQrG9L+e1x6DpSbnU=
=OC51
-----END PGP SIGNATURE-----

--=-nDpBr0qyRi9GSsG+IAPg--


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


From owner-freebsd-hackers  Thu Mar 13 12:32: 4 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id F0DC837B401
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 12:32:02 -0800 (PST)
Received: from red.tallence.de (red.tallence.de [212.77.172.74])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9304D43F93
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 12:32:01 -0800 (PST)
	(envelope-from stb@lassitu.de)
Received: from lassitu.de (unknown [212.77.172.82])
	by red.tallence.de (Postfix) with ESMTP
	id CBDF233D05; Thu, 13 Mar 2003 21:31:59 +0100 (CET)
Date: Thu, 13 Mar 2003 21:32:07 +0100
Subject: Re: jumpstart for freebsd.
Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: freebsd-hackers@FreeBSD.ORG
To: Anshuman Kanwar <anshuman@expertcity.com>
From: Stefan Bethke <stb@lassitu.de>
In-Reply-To: <Pine.WNT.4.44.0303131141530.2964-100000@KANWAR2K>
Message-Id: <DBC3888C-5592-11D7-999B-000393496BE8@lassitu.de>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Am Donnerstag, 13.03.03, um 20:46 Uhr (Europe/Berlin) schrieb Anshuman  
Kanwar:

> I've spent most of last year automating the installation of FreeBSD  
> systems at my workplace. [...]
> As a result of all the above, I wrote a set of perl scripts that do a  
> very similar job for FreeBSD.
> [...]
> If there is any interest in this work, I will be more than happy to  
> see it become one of the ways of installing FreeBSD. Of course, some  
> modifications would be required to make these scripts more generic,  
> robust and user friendly.
>
> The questions I have are:
> 1) Is this duplication of any prev. work ?

Can't speak to that, although I'm certain that many shops have custom  
scripts to do this.

> 2) If no then how should I go about trying to integrate the code into
> FreeBSD?

You should try to create a port for it. The Porter's Handbook explains  
how to do that.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ 
index.html

Also, you might want to compare your approach compares to FreeBSD From  
Scratch:  
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/fbsd-from-scratch/ 
index.html


Stefan

-- 
Stefan Bethke <stb@lassitu.de>   Fon +49 170 346 0140


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


From owner-freebsd-hackers  Thu Mar 13 13:52:12 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E923D37B404
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 13:52:11 -0800 (PST)
Received: from smtpb.ha-net.ptd.net (smtpb.ha-net.ptd.net [207.44.96.82])
	by mx1.FreeBSD.org (Postfix) with SMTP id A294A43FB1
	for <hackers@freebsd.org>; Thu, 13 Mar 2003 13:52:10 -0800 (PST)
	(envelope-from tms2@mail.ptd.net)
Received: (qmail 20958 invoked by uid 50005); 13 Mar 2003 21:19:23 -0000
Received: from tms2@mail.ptd.net by smtpb.ha-net.ptd.net by uid 50002 with qmail-scanner-1.15 
 (uvscan: v4.1.60/v4251. spamassassin: 2.43.  Clear:. 
 Processed in 0.825352 secs); 13 Mar 2003 21:19:23 -0000
Received: from du211002.cli.ptd.net (HELO mail.ptd.net) ([204.186.211.2]) (envelope-sender <tms2@mail.ptd.net>)
          by smtpb.ha-net.ptd.net (qmail-ldap-1.03) with SMTP
          for <enache@rdslink.ro>; 13 Mar 2003 21:19:22 -0000
Message-ID: <3E70FD71.6C5F2BC9@mail.ptd.net>
Date: Thu, 13 Mar 2003 16:51:45 -0500
From: "T.M. Sommers" <tms2@mail.ptd.net>
Organization: None
X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Enache Adrian <enache@rdslink.ro>
Cc: David Cuthbert <dacut@kanga.org>, hackers@freebsd.org
Subject: Re: first parameter to select
References: <3E702BCC.3030208@kanga.org> <20030313083710.GA8225@cirb503493.alcatel.com.au> <3E70D561.1080001@kanga.org> <20030313194850.GA899@ratsnest.hole>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Enache Adrian wrote:
> 
> On Thu, Mar 13, 2003 at 02:00:49PM -0500, David Cuthbert wrote:
> > Admittedly, my experience is dated and refers to implementing servers on
> > Solaris.  The man page for select(3c) on Solaris explicitly states:
> >
> > "The poll(2) function is preferred over this function.  It must be used
> > when the number of descriptors exceeds FD_SETSIZE."
> 
> IIRC, in Solaris select() isn't a system call, but a library call
> emulated in userland on top of poll(2).

That is correct (I just checked).

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


From owner-freebsd-hackers  Thu Mar 13 15: 5:41 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C885A37B401
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 15:05:39 -0800 (PST)
Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0D24543FA3
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 15:05:39 -0800 (PST)
	(envelope-from marcel@xcllnt.net)
Received: from ns1.xcllnt.net (localhost [127.0.0.1])
	by ns1.xcllnt.net (8.12.8/8.12.8) with ESMTP id h2DN5cSd058414;
	Thu, 13 Mar 2003 15:05:38 -0800 (PST)
	(envelope-from marcel@ns1.xcllnt.net)
Received: (from marcel@localhost)
	by ns1.xcllnt.net (8.12.8/8.12.8/Submit) id h2DN5cw1058413;
	Thu, 13 Mar 2003 15:05:38 -0800 (PST)
Date: Thu, 13 Mar 2003 15:05:38 -0800
From: Marcel Moolenaar <marcel@xcllnt.net>
To: Joe Marcus Clarke <marcus@marcuscom.com>
Cc: hackers@FreeBSD.ORG
Subject: Re: Question on gcc linker and -pthread
Message-ID: <20030313230538.GA58315@ns1.xcllnt.net>
References: <1047586732.84063.10.camel@gyros>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1047586732.84063.10.camel@gyros>
User-Agent: Mutt/1.5.1i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Thu, Mar 13, 2003 at 03:18:52PM -0500, Joe Marcus Clarke wrote:
> I've noticed something I think is strange with gcc, the -shared flag,
> and -pthread on -STABLE.  I'm hoping someone can enlighten me as to why
> this happens or if it's a bug.  If I compile something with the
> following command, I do not see libc_r.so linked in the resulting
> object:
> 
> cc -shared -pthread -o xxx.so xxx.c
> 
> However, if I replace -pthread with -lc_r, it works.  Also, if I change
> the command to:
> 
> cc -Wl,-shared -pthread -o xxx.so xxx.c
> 
> I also see libc_r.so linked in.  Is this expected behavior?  libtool
> seems to like the former -shared syntax which is causing some problems
> with some GTK themes.  Thanks.

The -shared option tells the compiler driver that you're trying to
create a shared object. In that case -lc_r is not added to the link
line. Adding -lc_r explicitly is dangerous, because now the linker
will construct a shared object that has code linked in from an
archive library that has not been compiled with PIC. Consequently,
some architectures (eg ia64) may barf when you try to link against
this shared object because it may contain invalid relocations.

Using -Wl,-shared tricks the compiler driver in thinking you are
creating an executable. It will therefore make sure dependencies
are correct by adding -lc_r on the link line. You tell the linker
however that you're creating a shared object, but now it also has
-lc_r explicitly. Again, this can result in a bad shared object.

I don't think there's a bug.

-- 
 Marcel Moolenaar	  USPA: A-39004		 marcel@xcllnt.net

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


From owner-freebsd-hackers  Thu Mar 13 15:15:57 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 92E6337B404
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 15:15:54 -0800 (PST)
Received: from creme-brulee.marcuscom.com (rdu57-17-158.nc.rr.com [66.57.17.158])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9765F43FB1
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 15:15:52 -0800 (PST)
	(envelope-from marcus@marcuscom.com)
Received: from [10.2.1.4] (vpn-client-4.marcuscom.com [10.2.1.4])
	by creme-brulee.marcuscom.com (8.12.8/8.12.8) with ESMTP id h2DNFDrI022043;
	Thu, 13 Mar 2003 18:15:13 -0500 (EST)
	(envelope-from marcus@marcuscom.com)
Subject: Re: Question on gcc linker and -pthread
From: Joe Marcus Clarke <marcus@marcuscom.com>
To: Marcel Moolenaar <marcel@xcllnt.net>
Cc: hackers@FreeBSD.ORG
In-Reply-To: <20030313230538.GA58315@ns1.xcllnt.net>
References: <1047586732.84063.10.camel@gyros>
	 <20030313230538.GA58315@ns1.xcllnt.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-AvF7j8uAzTab7OYaPJgx"
Organization: MarcusCom, Inc.
Message-Id: <1047597337.84063.43.camel@gyros>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 
Date: 13 Mar 2003 18:15:37 -0500
X-Spam-Status: No, hits=-32.7 required=5.0
	tests=EMAIL_ATTRIBUTION,HOT_NASTY,IN_REP_TO,PGP_SIGNATURE_2,
	      QUOTED_EMAIL_TEXT,QUOTE_TWICE_1,REFERENCES,
	      REPLY_WITH_QUOTES
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


--=-AvF7j8uAzTab7OYaPJgx
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2003-03-13 at 18:05, Marcel Moolenaar wrote:
> On Thu, Mar 13, 2003 at 03:18:52PM -0500, Joe Marcus Clarke wrote:
> > I've noticed something I think is strange with gcc, the -shared flag,
> > and -pthread on -STABLE.  I'm hoping someone can enlighten me as to why
> > this happens or if it's a bug.  If I compile something with the
> > following command, I do not see libc_r.so linked in the resulting
> > object:
> >=20
> > cc -shared -pthread -o xxx.so xxx.c
> >=20
> > However, if I replace -pthread with -lc_r, it works.  Also, if I change
> > the command to:
> >=20
> > cc -Wl,-shared -pthread -o xxx.so xxx.c
> >=20
> > I also see libc_r.so linked in.  Is this expected behavior?  libtool
> > seems to like the former -shared syntax which is causing some problems
> > with some GTK themes.  Thanks.
>=20
> The -shared option tells the compiler driver that you're trying to
> create a shared object. In that case -lc_r is not added to the link
> line. Adding -lc_r explicitly is dangerous, because now the linker
> will construct a shared object that has code linked in from an
> archive library that has not been compiled with PIC. Consequently,
> some architectures (eg ia64) may barf when you try to link against
> this shared object because it may contain invalid relocations.
>=20
> Using -Wl,-shared tricks the compiler driver in thinking you are
> creating an executable. It will therefore make sure dependencies
> are correct by adding -lc_r on the link line. You tell the linker
> however that you're creating a shared object, but now it also has
> -lc_r explicitly. Again, this can result in a bad shared object.

Thanks for the explanation.  After I sent the email, I looked at the
FreeBSD spec header for GCC.  I saw that -lc_r is only passed to the
linker if -shared is not specified. =20

I'm still a bit confused because for ports, ${PTHREAD_LIBS} is set to
-lc_r in -CURRENT which will result in shared objects having a libc_r.so
link.  However, in -STABLE, ${PTHREAD_LIBS} is set to -pthread.  If one
specifies -pthread in -CURRENT, they will get the -STABLE linking
behavior.  So, all -CURRENT users won't see the undefined symbol problem
I'm seeing in -STABLE.  Is this inconsistency by design?  Since ia64 is
a -CURRENT only architecture, your explanation makes me think using
-lc_r explicitly in -CURRENT is still a bad idea.

Joe

>=20
> I don't think there's a bug.
--=20
PGP Key : http://www.marcuscom.com/pgp.asc



--=-AvF7j8uAzTab7OYaPJgx
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQA+cREZb2iPiv4Uz4cRAnrhAKCPw9rlrNxrwqeR5goTHPi7XPTAZACfYtM5
NBafwYmV7++y9d7RuX92rcY=
=44zu
-----END PGP SIGNATURE-----

--=-AvF7j8uAzTab7OYaPJgx--


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


From owner-freebsd-hackers  Thu Mar 13 15:44:26 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D368C37B401
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 15:44:24 -0800 (PST)
Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DFD9743FB1
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 15:44:23 -0800 (PST)
	(envelope-from marcel@xcllnt.net)
Received: from ns1.xcllnt.net (localhost [127.0.0.1])
	by ns1.xcllnt.net (8.12.8/8.12.8) with ESMTP id h2DNiNSd058605;
	Thu, 13 Mar 2003 15:44:23 -0800 (PST)
	(envelope-from marcel@ns1.xcllnt.net)
Received: (from marcel@localhost)
	by ns1.xcllnt.net (8.12.8/8.12.8/Submit) id h2DNiNS4058604;
	Thu, 13 Mar 2003 15:44:23 -0800 (PST)
Date: Thu, 13 Mar 2003 15:44:23 -0800
From: Marcel Moolenaar <marcel@xcllnt.net>
To: Joe Marcus Clarke <marcus@marcuscom.com>
Cc: hackers@FreeBSD.ORG
Subject: Re: Question on gcc linker and -pthread
Message-ID: <20030313234423.GA58541@ns1.xcllnt.net>
References: <1047586732.84063.10.camel@gyros> <20030313230538.GA58315@ns1.xcllnt.net> <1047597337.84063.43.camel@gyros>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1047597337.84063.43.camel@gyros>
User-Agent: Mutt/1.5.1i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Thu, Mar 13, 2003 at 06:15:37PM -0500, Joe Marcus Clarke wrote:
> > Using -Wl,-shared tricks the compiler driver in thinking you are
> > creating an executable. It will therefore make sure dependencies
> > are correct by adding -lc_r on the link line. You tell the linker
> > however that you're creating a shared object, but now it also has
> > -lc_r explicitly. Again, this can result in a bad shared object.
> 
> Thanks for the explanation.  After I sent the email, I looked at the
> FreeBSD spec header for GCC.  I saw that -lc_r is only passed to the
> linker if -shared is not specified.  
> 
> I'm still a bit confused because for ports, ${PTHREAD_LIBS} is set to
> -lc_r in -CURRENT which will result in shared objects having a libc_r.so
> link.  However, in -STABLE, ${PTHREAD_LIBS} is set to -pthread.  If one
> specifies -pthread in -CURRENT, they will get the -STABLE linking
> behavior.  So, all -CURRENT users won't see the undefined symbol problem
> I'm seeing in -STABLE.  Is this inconsistency by design?

That's a good question. I tend to think it's not by design, as very
little really is :-)

> Since ia64 is
> a -CURRENT only architecture, your explanation makes me think using
> -lc_r explicitly in -CURRENT is still a bad idea.

Yes. We have the same problem with libobjc.a that's being linked into
a shared object (ports/lang/gnustep-base). The problem is not easily
resolved, although it's easy to come up with possible solutions.

-- 
 Marcel Moolenaar	  USPA: A-39004		 marcel@xcllnt.net

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


From owner-freebsd-hackers  Thu Mar 13 16:16:32 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E3FF937B401
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 16:16:29 -0800 (PST)
Received: from hobby.digiware.nl (hobby.digiware.nl [212.61.27.67])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 444F943FA3
	for <freebsd-hackers@freebsd.org>; Thu, 13 Mar 2003 16:16:28 -0800 (PST)
	(envelope-from wjw@withagen.nl)
Received: from dual (dual [212.61.27.71])
	by hobby.digiware.nl (8.12.8/8.12.8a) with SMTP id h2E0GqIt018822;
	Fri, 14 Mar 2003 01:16:56 +0100 (CET)
	(envelope-from wjw@withagen.nl)
Message-ID: <001e01c2e9bf$0849b9f0$471b3dd4@digiware.nl>
From: "Willem Jan Withagen" <wjw@withagen.nl>
To: "Guido van Rooij" <guido@gvr.org>, "John" <jwd@bsdwins.com>
Cc: "Hackers List" <freebsd-hackers@freebsd.org>
References: <20030313003952.GA1800@BSDWins.Com> <20030313105557.GA84120@gvr.gvr.org>
Subject: Re: magic symbolic links (ideas/patches?)
Date: Fri, 14 Mar 2003 01:16:54 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

V2VsbCBJIG9uY2UgZGlkIHRyeSB0byBnZXQgdGhpcyB3b3JraW5nLCBhbmQgZXZlbnR1YWxseSBn
b3QgaXQgd29ya2luZyB3aXRob3V0IG91emluZyBtYWxsb2MncyBpbiB0aGUga2VybmVsLi4uIFRo
YXQgd2FzIHNvbWV3aGVyZSBhcm91bmQgbWF5IDE5OTcgYW5kIEZCU0QgMi4yLjg/Pw0KSW4gZXNz
ZW5jZSB0aGUgY2hhbmdlIGluIHRoZSBGSUxFIHN5c3RlbSBpcyByZWFsdGl2ZWx5IG1pbm9yLCBu
b3QgY291bnRpbmcgdGhlIG1lYW5zIG9mIGdldHRpbmcgdGhlIHJlcGxhY2VtZW50IGluZm8gdGhl
cmUuIEFsbCB0aGF0IG5lZWRlZCBjaGFuZ2VzICB3YXMgdmZzX2xvb2t1cC5jLiBUaGUgbmV0YnNk
IGFydGljbGUgaGFzIGEgbG90IG1vcmUgZmlsZXMgY2hhbmdlZCwgYnV0IHRoZXkgaGF2ZSB0byBk
byB3aXRoIGhvbm91cmluZyBhIE1BR0lDIG1vdXQgb3B0aW9uIHRlbGxpbmcgdGhlIGtlcm5lbCB0
byByZXBsYWNlIG9yIG5vdC4NCg0KQnV0IHRoZW4gdGhlIG5leHQgc3RlcCB3YXMgdG8gZ2V0IHVz
ZWZ1bGwgaW5mbyBpbiB0aGUgcmVwbGFjZW1lbnQuDQoNClRoZSB3YXkgSSB3YXMgdXNlZCB0byB0
aGlzIG9uIERvbWFpbiBBcG9sbG8gc3RhdGlvbnMgd2FzIHRoYXQgY2hhbmdlcyBpbiB0aGUgZW52
aXJvbm1lbnQgd291bGQgd29yayBwZXIgcHJvY2VzcyBmb3IgdGhlIG1hZ2ljIHN5bWxpbmtzLiBU
aGV5IGNhbGxlZCB0aGVuIHZhcmlhbnQtbGlua3MNCg0KU28gdGhlbiBJIHdhcyBzdHVwcGlkIGVu
b3VnaCB0byBhc2sgd2hhdCBvdGhlciB0aG91Z2h0IHRoYXQgd291bGQgYmUgcmVxdWlyZWQuIFNv
IEkgZ290IHRoaXMgd2hvbGUgZmxhbWVmZXN0IHRoYXQgaXQgd2FzIGEgc2VjdXJpdHkgcmlzaywg
YmxhaCwgYmxhaCwgYmxhaC4uLi4uDQpNdWNoIGxpa2UgdGhlIGRpc2N1c3Npb24gaW4gbGluayB5
b3UgaGF2ZSBmcm9tIG5ldGJzZC4NCg0KSW4gdGhlIGVuZCBteSBjb25jbHVzaW9uIHdhcyB0byBn
ZXQgaW4gc3lzY3RsIGFzIGZhciBhcyB0byBjcmVhdGUgYSAibmFtZXNwYWNlIiB2YXJsaW5rIG9z
bGkuIFRoaXMgd291bGQgcmVzdHJpY3QgaGVhdnkgdHJpY2tzIHRvIHJvb3QuIA0KQW5kIHRoYXQg
aXMgd2hlcmUgSSBnb3Qgc3R1Y2s6DQogICAgVGhlIGNvbXBhbnkgSSB3YXMgd29ya2luZyBpbiB3
YXMgZ3Jvd2luZyByZWFsIGZhc3QuDQogICAgU3lzY3RsIHdhc24ndCBpbiBhIHRvbyBncmVhdCBh
IHN0YXRlDQoNCk5vdyB5b3UgYXJlIGNvbXBsaWNhdGluZyB0aGluZ3MgZXZlbiBtb3JlIGJ5IGhh
dmluZyB0aGluZ3MgcmVhY3QgdG8gY2hhbmdlcyBpbiB0aGUgdXNlciBwcm9jZXNzLiBJIGtuZXcg
SSBkaWQgbm90IGtub3cgZW5vdWdoIGFib3V0IEZCU0QgdG8gZXZlbiBzdGFydCB0cnlpbmcgdGhh
dC4gU28gSSBjYW5ub3QgaGVscCB5b3UgdGhlcmUuDQoNCi0tV2pXDQoNClBTOiBJIHN0aWxsIGhh
dmUgc3JjIGx5aW5nIGFyb3VuZCB1bmRlciBhIFZMIGRpcmVjdG9yeS4NCg0KLS0tLS0gT3JpZ2lu
YWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJHdWlkbyB2YW4gUm9vaWoiIDxndWlkb0BndnIub3Jn
Pg0KVG86ICJKb2huIiA8andkQGJzZHdpbnMuY29tPg0KQ2M6ICJIYWNrZXJzIExpc3QiIDxmcmVl
YnNkLWhhY2tlcnNAZnJlZWJzZC5vcmc+OyA8d2p3QHdpdGhhZ2VuLm5sPg0KU2VudDogVGh1cnNk
YXksIE1hcmNoIDEzLCAyMDAzIDExOjU1IEFNDQpTdWJqZWN0OiBSZTogbWFnaWMgc3ltYm9saWMg
bGlua3MgKGlkZWFzL3BhdGNoZXM/KQ0KDQoNCj4gSUlSQyBXaWxsZW0tSmFuIFdpdGhhZ2VuIGhh
cyBkb25lIHRoaXMgeWVhcnMgYWdvLg0KPiANCj4gSSBDYyBlZCBoaW0uDQo+IA0KPiAtR3VpZG8N
Cj4gDQo+IE9uIFdlZCwgTWFyIDEyLCAyMDAzIGF0IDA3OjM5OjUyUE0gLTA1MDAsIEpvaG4gd3Jv
dGU6DQo+ID4gSGkgRm9sa3MsDQo+ID4gDQo+ID4gICAgSSBoYXZlIGEgbmVlZCB0byBpbXBsZW1l
bnQgYSBoaWdobHkgc3BlY2lmaWMgdmFyaWFudCB1c2FnZSBvZg0KPiA+IHdoYXQgYXJlIGNvbW1v
bmx5IHJlZmVycmVkIHRvIGFzIG1hZ2ljIHN5bWxpbmtzLCBpZToNCj4gPiANCj4gPiAgICAvc3Jj
IC0+IC8uc3JjLyRBUkNIL3NyYw0KPiA+IA0KPiA+ICAgIHdoZXJlICRBUkNIIG5lZWRzIHRvIGNv
bWUgZnJvbSB0aGUgdXNlciBlbnZpcm9ubWVudC4NCj4gPiANCj4gPiAgICBBIHJlbGF0ZWQgcGF0
Y2hzZXQgZnJvbSBOZXRCU0QgKDE5OTUpIGNhbiBiZSBzZWVuIGhlcmU6DQo+ID4gDQo+ID4gaHR0
cDovL3d3dy5uZXRic2Qub3JnL2NnaS1iaW4vcXVlcnktcHItc2luZ2xlLnBsP251bWJlcj0xNzgx
DQo+ID4gDQo+ID4gICAgSW4gbXkgc3BlY2lmaWMgaW1wbGVtZW50YXRpb24sIHRoZSB2YWx1ZSBv
ZiAkQVJDSCB3aWxsIEFMV0FZUw0KPiA+IGJlIDMgY2hhcmFjdGVycyAoTm90IGhhdmluZyBpbXBs
ZW1lbnRlZCBhbnl0aGluZyB5ZXQsIGFuZCB0bw0KPiA+IGF2b2lkIHBvc3NpYmx5IHBsYXlpbmcg
dGhlIHVzZXJsYW5kIGdhbWUsIEkgd2FzIHRoaW5raW5nIG9mDQo+ID4gYWRkaW5nIGEgZmllbGQg
dG8gdGhlIHByb2Mgc3RydWN0dXJlIGFuZCBoYXZpbmcgdGhlIHNldGVudi9wdXRlbnYNCj4gPiBm
dW5jdGlvbnMgcGxhY2UgdGhlIHZhbHVlIHRoZXJlIHZpYSBhIHN5c2N0bCwgdGh1cyBhbGxvd2lu
ZyBhDQo+ID4gdmVyeSBzaW1wbGUgaW50ZXJmYWNlLi4uIHNob3J0IHNpZ2h0ZWQ/KS4NCj4gPiAN
Cj4gPiAgICBJZiBhbnlvbmUgaGFzIGFueSBjb21tZW50cywgb3IgcGF0Y2hlcyBoYW5naW5nIGFy
b3VuZCBmb3INCj4gPiB0aGlzIHR5cGUgb2YgaW1wbGVtZW50YXRpb24sIEkgd291bGQgYXBwcmVj
aWF0ZSBhIHBvaW50ZXIgdG8gdGhlbS4NCj4gPiANCj4gPiBNYW55LCBNYW55IFRoYW5rcywNCj4g
PiBKb2huDQo+ID4gDQo+ID4gVG8gVW5zdWJzY3JpYmU6IHNlbmQgbWFpbCB0byBtYWpvcmRvbW9A
RnJlZUJTRC5vcmcNCj4gPiB3aXRoICJ1bnN1YnNjcmliZSBmcmVlYnNkLWhhY2tlcnMiIGluIHRo
ZSBib2R5IG9mIHRoZSBtZXNzYWdlDQo+IA0KPiAtLSANCj4gR3VpZG8gdmFuIFJvb2lqICAgICAg
IHwgIFBob25lOiArKzMxIDY1MyA5OTQgNzczDQo+IE1hZGlzb24gR3Vya2hhLCBUZWNobm9sb2d5
IFRoaW5rLVRhbmsgfA0KPiBndWlkb0BtYWRpc29uLWd1cmtoYS5jb20gICAgICAgfCAgRnJlZUJT
RCBjb21taXR0ZXINCj4gDQo+IA==


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


From owner-freebsd-hackers  Thu Mar 13 17:23:47 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0188C37B401
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 17:23:46 -0800 (PST)
Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8109743FBF
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 17:23:44 -0800 (PST)
	(envelope-from grog@lemis.com)
Received: by wantadilla.lemis.com (Postfix, from userid 1004)
	id B89C051A60; Fri, 14 Mar 2003 11:55:14 +1030 (CST)
Date: Fri, 14 Mar 2003 11:55:14 +1030
From: Greg 'groggy' Lehey <grog@FreeBSD.org>
To: Yaoping Ruan <yruan@cs.princeton.edu>
Cc: hackers@FreeBSD.ORG
Subject: Re: Kernel trace
Message-ID: <20030314012514.GB37955@wantadilla.lemis.com>
References: <bulk.24288.20030308135115@hub.freebsd.org> <3E6FFAAE.2B6108F8@cs.princeton.edu>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="nVMJ2NtxeReIH9PS"
Content-Disposition: inline
In-Reply-To: <3E6FFAAE.2B6108F8@cs.princeton.edu>
User-Agent: Mutt/1.4i
Organization: The FreeBSD Project
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-418-838-708
WWW-Home-Page: http://www.FreeBSD.org/
X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F  09AC 22E6 F290 507A 4223
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


--nVMJ2NtxeReIH9PS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wednesday, 12 March 2003 at 22:27:42 -0500, Yaoping Ruan wrote:
> Does any one know the implementation of "ktrace" in FreeBSD? I would
> like to hack the source code and have a relatively easy way to copy
> the kernel stack image when a certain of thing happens, such as page
> fault. It should work like the breakpoints in gdb. But kernel panic
> is too much trouble for just a single stack image, and kgdb is not
> simple enough. Which source file(s) I should look at?

Start with kern/kern_ktrace.c.  Note that work is currently going on
with the implementation.

Greg
--
See complete headers for address and phone numbers

--nVMJ2NtxeReIH9PS
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (FreeBSD)

iD8DBQE+cS96IubykFB6QiMRAoNvAJ40T8K5ICC7tpRcuYh3txXLXb9QLgCeNMUf
AJbIsT86eKW7EbwMgQYebRk=
=jii6
-----END PGP SIGNATURE-----

--nVMJ2NtxeReIH9PS--

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


From owner-freebsd-hackers  Thu Mar 13 22:35:30 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2CD8B37B401
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 22:35:29 -0800 (PST)
Received: from cirb503493.alcatel.com.au (c18609.belrs1.nsw.optusnet.com.au [210.49.80.204])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E0A6F43F3F
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 22:35:27 -0800 (PST)
	(envelope-from peterjeremy@optushome.com.au)
Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])
	by cirb503493.alcatel.com.au (8.12.6/8.12.5) with ESMTP id h2E6ZPiM009930;
	Fri, 14 Mar 2003 17:35:26 +1100 (EST)
	(envelope-from jeremyp@cirb503493.alcatel.com.au)
Received: (from jeremyp@localhost)
	by cirb503493.alcatel.com.au (8.12.6/8.12.5/Submit) id h2E6ZHfq009929;
	Fri, 14 Mar 2003 17:35:17 +1100 (EST)
Date: Fri, 14 Mar 2003 17:35:16 +1100
From: Peter Jeremy <peterjeremy@optushome.com.au>
To: Enache Adrian <enache@rdslink.ro>
Cc: David Cuthbert <dacut@kanga.org>, hackers@FreeBSD.ORG
Subject: Re: first parameter to select
Message-ID: <20030314063516.GA9301@cirb503493.alcatel.com.au>
References: <3E702BCC.3030208@kanga.org> <20030313083710.GA8225@cirb503493.alcatel.com.au> <20030313165018.GA703@ratsnest.hole>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030313165018.GA703@ratsnest.hole>
User-Agent: Mutt/1.4i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Thu, Mar 13, 2003 at 06:50:18PM +0200, Enache Adrian wrote:
>I have no benchmarks, but judging after the way things are implemented
>in the FreeBSD kernel, select() is definitely faster.

Can you explain what leads you to make this statement please.

>Please someone explain me what is meant in select(2) by:
>
>  If nfds is greater than the number of open files, select() is not guaran-
>  teed to examine the unused file descriptors.   For historical reasons,
>  select() will always examine the first 256 descriptors.

The second sentence appears to be an error.  I can't find anything in
the current code (or previous versions) that suggests select() would
ever examine more than nfd FDs.  The only reference to 256 is can find
is that FD_SETSIZE used to be 256 and select() used to return EINVAL if
nfd > FD_SETSIZE.

As for the first sentence, select() should return EBADF if any of the
fd_set arguments has a set bit that references an invalid (eg closed)
FD.  The actual implementation restricts nfd to the highest open FD
plus one.  To explain further, consider a with FDs 0-60 open.  If you
pass a fd_set with FDs 0-61 set and nfd = 62, it will scan FDs 0-60
and ignore the bit for FD 61 (ie it will still be set on return).

Peter

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


From owner-freebsd-hackers  Thu Mar 13 23:20: 0 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8E7C237B404
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 23:19:58 -0800 (PST)
Received: from cirb503493.alcatel.com.au (c18609.belrs1.nsw.optusnet.com.au [210.49.80.204])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0245043F93
	for <hackers@FreeBSD.ORG>; Thu, 13 Mar 2003 23:19:57 -0800 (PST)
	(envelope-from peterjeremy@optushome.com.au)
Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])
	by cirb503493.alcatel.com.au (8.12.6/8.12.5) with ESMTP id h2E7JtiM009994;
	Fri, 14 Mar 2003 18:19:55 +1100 (EST)
	(envelope-from jeremyp@cirb503493.alcatel.com.au)
Received: (from jeremyp@localhost)
	by cirb503493.alcatel.com.au (8.12.6/8.12.5/Submit) id h2E7JtSo009993;
	Fri, 14 Mar 2003 18:19:55 +1100 (EST)
Date: Fri, 14 Mar 2003 18:19:55 +1100
From: Peter Jeremy <peterjeremy@optushome.com.au>
To: David Cuthbert <dacut@kanga.org>
Cc: hackers@FreeBSD.ORG
Subject: Re: first parameter to select
Message-ID: <20030314071954.GA9896@cirb503493.alcatel.com.au>
References: <3E702BCC.3030208@kanga.org> <20030313083710.GA8225@cirb503493.alcatel.com.au> <3E70D561.1080001@kanga.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E70D561.1080001@kanga.org>
User-Agent: Mutt/1.4i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Thu, Mar 13, 2003 at 02:00:49PM -0500, David Cuthbert wrote:
>Peter Jeremy wrote:
>>In virtually all cases, poll() will need to copy more data in and out
>>of the kernel then select() would.  Likewise, in virtually all cases,
>>select() will need to scan more file descriptors than poll() does.
>>The overall performance comes down to the relative cost of copying
>>data vs testing bits.
>
>Not sure what you mean by virtually all cases.
>
>Given that a poll() descriptor is 12 bytes and fd_set is usually at 
>least 128 bytes (does select() copy the entire fd_set?  I believe this 
>is the case, but don't have access to the source atm), the savings kicks 
>in at 12 descriptors.

The default fd_set size if 128 bytes - but this can be over-ridden at
compile time.  Select() only copies nfd bits (rounded up to a 32-bit
boundary).  There is no upper limit on nfd.

Working out the data copy savings is difficult because the amount of
data select() copies is defined by nfd (ie the highest FD number
referenced) and the number of masks passed in (exception, write,
read).  It is independent of the number of FDs to be examined.

The data copied in/out by poll() is 8 bytes per FD to be examined.

It you need to select on read+write+except for a single FD, or need to
select on few high-numbered FDs, poll() will copy less data.  In all
other cases, select() will copy less data.  For small amounts of data,
the copyin()/copyout() overheads will outweigh the actual copying.

Once you're in the kernel, poll() can just walk along the array,
checking each FD, whereas select() needs to check each bit from 0
to nfd-1 in each fd_set passed - though it can quickly skip high
0's in each long.

>I'd still argue that, when porting a program across platforms, the 
>behaviour of select() is likely to be more consistent than poll(), 
>usually (always?) in the cases where something unusual has occurred on a 
>descriptor.

Probably.  I know Tru64 incorrectly sets bits in poll() revents when
a socket is closed by the peer.  I said poll() was blessed by SVID,
I didn't say the implementations were actually consistent :-).

Peter

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


From owner-freebsd-hackers  Fri Mar 14  1:34:18 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 237D937B404
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 01:34:17 -0800 (PST)
Received: from accms33.physik.rwth-aachen.de (accms33.physik.RWTH-Aachen.DE [137.226.46.133])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4244E43F75
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 01:34:15 -0800 (PST)
	(envelope-from kuku@accms33.physik.rwth-aachen.de)
Received: (from kuku@localhost)
	by accms33.physik.rwth-aachen.de (8.11.6/8.9.3) id h2E9YD105192
	for freebsd-hackers@freebsd.org; Fri, 14 Mar 2003 10:34:13 +0100
Date: Fri, 14 Mar 2003 10:34:13 +0100
From: Christoph Kukulies <kuku@physik.rwth-aachen.de>
Message-Id: <200303140934.h2E9YD105192@accms33.physik.rwth-aachen.de>
To: freebsd-hackers@freebsd.org
Subject: 5.0R did (bad) things to my previous FS on ad0s1x
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


I installed 5.0R on a set of SCSI disks that ran in my box 
side by side with the 4.7 installed on the IDE drives.

I switched in the BIOS to boot the SCSI disks and installed
5.0R there. Then I fsck'ed /dev/ad0s1a,e,f,g and mounted them.

Already noticed that - although I shut down the machine smoothly -
5.0 didn't find ad0s1g clean and did a salvage on summary or something.

For some reason I booted back into 4.7 on the IDE drives
and 4.7 suddenly found all filesystems bad and forced into
a filesystem check where on every FS it had to search for an alternate
superblock since it detected a mismatch in the summary information
on the standard and first alternate superblock.

Strange. And I had no backup which I'm doing now quickly :-)

--
Chris Christoph P. U. Kukulies kukulies@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  Fri Mar 14  3:16:51 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 32C7537B404
	for <freebsd-hackers@FreeBSD.org>; Fri, 14 Mar 2003 03:16:50 -0800 (PST)
Received: from bol.com.br (200-163-046-058.cpece7003.dsl.brasiltelecom.net.br [200.163.46.58])
	by mx1.FreeBSD.org (Postfix) with SMTP id 983994408F
	for <freebsd-hackers@FreeBSD.org>; Fri, 14 Mar 2003 03:16:30 -0800 (PST)
	(envelope-from redacaocoml@bol.com.br)
From: "Redação Comercial" <redacaocoml@bol.com.br>
To: <freebsd-hackers@FreeBSD.org>
Subject: 300 Modelos de Cartas comerciais, avisos, convites, propostas, etc.
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Date: Fri, 14 Mar 2003 07:16:24 -0400
Content-Transfer-Encoding: 8bit
Message-Id: <20030314111630.983994408F@mx1.FreeBSD.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

COMUNICADO IMPORTANTE!!

Estamos lançando o KIT DE CARTAS COMERCIAIS, que sana suas dúvidas na
elaboração de: agradecimentos, atestados e declarações, avisos,  cartas de
cobrança, cartas em inglês, comunicados,  convites,  contratos, propostas,
empregos, solicitações e pedidos, telegramas, cartas por e-mail, etc.
Composto de 02 (dois) disquetes com 150 modelos de documentos cada um, mais
livreto 20 páginas, com técnicas de redação comercial. Indicado para:
secretárias em geral, gerências, Rh, executivos, estudantes e empresas de
toda ordem.
Este kit possui um preço ínfimo em relação ao que poderá gerar no
aperfeiçoamento da comunicação de sua empresa.

Acesse nossa Home Page para mais detalhes:

http://www.redacaocartas.ihp.com.br


Ps: Caso não queira receber novas mensagens e novidades sobre esse assunto,
acesse:

http://www.remova-me.ihp.com.br

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


From owner-freebsd-hackers  Fri Mar 14  5:31:51 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B49BF37B401
	for <hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 05:31:49 -0800 (PST)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F00AA43F93
	for <hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 05:31:48 -0800 (PST)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.8/8.12.3) with ESMTP id h2EDVlA7097181;
	Fri, 14 Mar 2003 06:31:48 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Fri, 14 Mar 2003 06:31:27 -0700 (MST)
Message-Id: <20030314.063127.60417991.imp@bsdimp.com>
To: dacut@kanga.org
Cc: hackers@FreeBSD.ORG
Subject: Re: first parameter to select
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <3E70D561.1080001@kanga.org>
References: <3E702BCC.3030208@kanga.org>
	<20030313083710.GA8225@cirb503493.alcatel.com.au>
	<3E70D561.1080001@kanga.org>
X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

In message: <3E70D561.1080001@kanga.org>
            David Cuthbert <dacut@kanga.org> writes:
: Given that a poll() descriptor is 12 bytes and fd_set is usually at 
: least 128 bytes (does select() copy the entire fd_set?  I believe this 
: is the case, but don't have access to the source atm), the savings kicks 
: in at 12 descriptors.

That's not the case.  The source clearly says so, and has been this
way since 4.2BSD.

int
kern_select(struct thread *td, int nd, fd_set *fd_in, fd_set *fd_ou,
    fd_set *fd_ex, struct timeval *tvp)
{
...
	/*
	 * Allocate just enough bits for the non-null fd_sets.  Use the
	 * preallocated auto buffer if possible.
	 */
	nfdbits = roundup(nd, NFDBITS);
	ncpbytes = nfdbits / NBBY;
...
#define	getbits(name, x) \
	do {								\
		if (name == NULL)					\
			ibits[x] = NULL;				\
		else {							\
			ibits[x] = sbp + nbufbytes / 2 / sizeof *sbp;	\
			obits[x] = sbp;					\
			sbp += ncpbytes / sizeof *sbp;			\
			error = copyin(name, ibits[x], ncpbytes);	\
			if (error != 0)					\
				goto done_nosellock;			\
		}							\
	} while (0)
	getbits(fd_in, 0);
	getbits(fd_ou, 1);
	getbits(fd_ex, 2);

So clearly only the part of the select set that's passed in with fd is
used.  Most programs I've seen actually pass in fn as max(fd,...) + 1.

So if you have only a few sockets, or less than 96/N (N is the number
of fd_sets you are using), select's copyin/out mechanism moves fewer
bits accross the kernel transom.

Warner


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


From owner-freebsd-hackers  Fri Mar 14  5:47: 7 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 20BD437B401
	for <hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 05:47:05 -0800 (PST)
Received: from mail.rdslink.ro (mail.rdslink.ro [193.231.236.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 6281E43FA3
	for <hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 05:47:03 -0800 (PST)
	(envelope-from enache@rdslink.ro)
Received: (qmail 8315 invoked from network); 14 Mar 2003 13:48:00 -0000
Received: from unknown (HELO ratsnest.hole) (10.100.0.123)
  by mail.rdslink.ro with SMTP; 14 Mar 2003 13:48:00 -0000
Received: from ratsnest.hole (localhost [127.0.0.1])
	by ratsnest.hole (8.12.5/8.12.5) with ESMTP id h2EDlLgO000844;
	Fri, 14 Mar 2003 15:47:21 +0200
Received: (from adi@localhost)
	by ratsnest.hole (8.12.5/8.12.5/Submit) id h2EDlLCW000842;
	Fri, 14 Mar 2003 15:47:21 +0200
Date: Fri, 14 Mar 2003 15:47:21 +0200
From: Enache Adrian <enache@rdslink.ro>
To: Peter Jeremy <peterjeremy@optushome.com.au>
Cc: David Cuthbert <dacut@kanga.org>, hackers@FreeBSD.ORG
Subject: Re: first parameter to select
Message-ID: <20030314134721.GA705@ratsnest.hole>
References: <3E702BCC.3030208@kanga.org> <20030313083710.GA8225@cirb503493.alcatel.com.au> <20030313165018.GA703@ratsnest.hole> <20030314063516.GA9301@cirb503493.alcatel.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030314063516.GA9301@cirb503493.alcatel.com.au>
User-Agent: Mutt/1.4i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Fri, Mar 14, 2003 at 05:35:16PM +1100, Peter Jeremy wrote:
> On Thu, Mar 13, 2003 at 06:50:18PM +0200, Enache Adrian wrote:
> >I have no benchmarks, but judging after the way things are implemented
> >in the FreeBSD kernel, select() is definitely faster.
> 
> Can you explain what leads you to make this statement please.

But poll() swaps a _LOT_ more data between the kernel and userland !

> >Please someone explain me what is meant in select(2) by:
> >
> >  If nfds is greater than the number of open files, select() is not guaran-
> >  teed to examine the unused file descriptors.   For historical reasons,
> >  select() will always examine the first 256 descriptors.
> 
> The second sentence appears to be an error.  I can't find anything in
> the current code (or previous versions) that suggests select() would
> ever examine more than nfd FDs.  The only reference to 256 is can find
> is that FD_SETSIZE used to be 256 and select() used to return EINVAL if
> nfd > FD_SETSIZE.

It probably wants to say ( in a manner quite confusing for a non
english speaker like me ) that select(2) won't bother to return EINVAL
for bad file descriptors which are in the bitmaps and are both greater
than the greatest open file descriptor and greater than 255.

That's only half wrong. :-)

select() won't bother to check them even if they are < 256. It's 
only the greatest open file descriptor that matters.

-- from kern/sys_generic.c:751 - kern_select()
	if (nd > td->td_proc->p_fd->fd_nfiles)
		nd = td->td_proc->p_fd->fd_nfiles;   /* forgiving; slightly wrong */
---

Take a look at this little program:
------------------------
#include <sys/select.h>
#include <unistd.h>

int main()
{
	fd_set set;
	FD_ZERO(&set);
	FD_SET(0,&set);
	FD_SET(20,&set);
	if (select(FD_SETSIZE,&set,0,0,0) == -1)
		err(1,"select");
	return 0;
}
------------------------

change 20 to 19 and select() will return EBADF.
Linux will return EBADF even if you put FD_SETSIZE-1 there.

I find FreeBSD's behaviour reasonable - and I wonder what
'historical' programs pass dummy, never opened fds to select()
in the hope of getting EBADF in return.

Regards
Adi

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


From owner-freebsd-hackers  Fri Mar 14  6:38: 1 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E587E37B401
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 06:38:00 -0800 (PST)
Received: from popcs.cs.tin.it (popcs.cs.tin.it [194.243.155.125])
	by mx1.FreeBSD.org (Postfix) with SMTP id 6C77E43F93
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 06:37:59 -0800 (PST)
	(envelope-from ferruccio.vitale@tin.it)
Received: (qmail 20257 invoked from network); 14 Mar 2003 14:37:57 -0000
Received: from cruiser.cs.tin.it (HELO cruiser) (212.216.178.193)
  by popcs.cs.tin.it with SMTP; 14 Mar 2003 14:37:57 -0000
Date: Fri, 14 Mar 2003 15:37:29 +0100
From: Ferruccio Vitale <ferruccio.vitale@tin.it>
To: freebsd-hackers@freebsd.org
Subject: variable size too large?
Message-Id: <20030314153729.3825d4fe.ferruccio.vitale@tin.it>
X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i386-portbld-freebsd4.8)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hi all,

I'm writing a little multithread program: in my thread function, I allocated a char variable of IP_MAXPACKET size; when I try to compile it, everything goes well, but when I run it, it dies, making a core file. 
Assume that:
1) the same code, with only one thread, linked to libc, runs normally
2) the same code, with a smaller variable size, linked to libc_r, runs normally
3) I tried to allocate two variables of 64000 bytes in this function (IP_MAXPACKET is equal to 65535), linked to libc_r and runs normally

Where am I wrong? :))

Regards,
Ferruccio

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


From owner-freebsd-hackers  Fri Mar 14  6:55:52 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AF24237B401
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 06:55:51 -0800 (PST)
Received: from mail-out.ukr.net (mail-out.ukr.net [212.42.65.71])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B838943F3F
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 06:55:50 -0800 (PST)
	(envelope-from najeiv@ukr.net)
Received: from hammer.ukr.net ([212.42.65.68]) by mail-out.ukr.net 
	with esmtp ID 18tqb4-000L0C-00; Fri, 14 Mar 2003 16:55:46 +0200
Received: from mail by hammer.ukr.net with local ID 18tqb4-000IEF-00
	; Fri, 14 Mar 2003 16:55:46 +0200
Received: from [81.17.128.1] by web.mail.ukr.net with HTTP;
	Fri, 14 Mar 2003 14:55:46 +0000 (GMT)
From: "÷ÉÔÁÌÉÊ áËÉÍÏ×" <najeiv@ukr.net>
To: ferruccio.vitale@tin.it
Cc: freebsd-hackers@freebsd.org
Subject: RE: variable size too large?
Mime-Version: 1.0
X-Mailer: mPOP Web-Mail 2.19
X-Originating-IP: unknown via proxy proxy.bigline.kharkov.ua [81.17.128.1]
Reply-To: "÷ÉÔÁÌÉÊ áËÉÍÏ×" <najeiv@ukr.net>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
Message-Id: <E18tqb4-000IEF-00@hammer.ukr.net>
Date: Fri, 14 Mar 2003 16:55:46 +0200
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *18tqb4-000IEF-00*a4yQRrbCrQ2*
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

default size of thread stack is 65536 bytes
you can change it by pthread_attr_setstacksize

Naje

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


From owner-freebsd-hackers  Fri Mar 14  7:11:53 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B184A37B401
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 07:11:51 -0800 (PST)
Received: from gandalf.online.bg (gandalf.online.bg [217.75.128.9])
	by mx1.FreeBSD.org (Postfix) with SMTP id 1495343FAF
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 07:11:50 -0800 (PST)
	(envelope-from roam@ringlet.net)
Received: (qmail 1970 invoked from network); 14 Mar 2003 15:07:20 -0000
Received: from office.sbnd.net (HELO straylight.ringlet.net) (217.75.140.130)
  by gandalf.online.bg with SMTP; 14 Mar 2003 15:07:19 -0000
Received: (qmail 9541 invoked by uid 1000); 14 Mar 2003 15:10:10 -0000
Date: Fri, 14 Mar 2003 17:10:10 +0200
From: Peter Pentchev <roam@ringlet.net>
To: Ferruccio Vitale <ferruccio.vitale@tin.it>
Cc: freebsd-hackers@freebsd.org
Subject: Re: variable size too large?
Message-ID: <20030314151010.GB452@straylight.oblivion.bg>
Mail-Followup-To: Ferruccio Vitale <ferruccio.vitale@tin.it>,
	freebsd-hackers@freebsd.org
References: <20030314153729.3825d4fe.ferruccio.vitale@tin.it>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="z4IKABJTiQIqPwmW"
Content-Disposition: inline
In-Reply-To: <20030314153729.3825d4fe.ferruccio.vitale@tin.it>
User-Agent: Mutt/1.5.3i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


--z4IKABJTiQIqPwmW
Content-Type: text/plain; charset=windows-1251
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Mar 14, 2003 at 03:37:29PM +0100, Ferruccio Vitale wrote:
> Hi all,
>=20
> I'm writing a little multithread program: in my thread function, I alloca=
ted a char variable of IP_MAXPACKET size; when I try to compile it, everyth=
ing goes well, but when I run it, it dies, making a core file.=20
> Assume that:
> 1) the same code, with only one thread, linked to libc, runs normally
> 2) the same code, with a smaller variable size, linked to libc_r, runs no=
rmally
> 3) I tried to allocate two variables of 64000 bytes in this function (IP_=
MAXPACKET is equal to 65535), linked to libc_r and runs normally
>=20
> Where am I wrong? :))

It would be very hard to say, without seeing your program and,
if possible, the output of a gdb session which shows where
exactly the program dies.

G'luck,
Peter

--=20
Peter Pentchev	roam@ringlet.net    roam@sbnd.net    roam@FreeBSD.org
PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint	FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
If you think this sentence is confusing, then change one pig.

--z4IKABJTiQIqPwmW
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+cfDS7Ri2jRYZRVMRAtS2AJ9qUHFiRNkByuYZSYsOYpDr8Jdc5QCffqQk
ixx6bIQjLcHM6e46yFMN/fY=
=+Jlq
-----END PGP SIGNATURE-----

--z4IKABJTiQIqPwmW--

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


From owner-freebsd-hackers  Fri Mar 14  9:47:57 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 501B837B401
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 09:47:56 -0800 (PST)
Received: from mailscan.binghamton.edu (mailscan.binghamton.edu [128.226.8.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id E052643FA3
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 09:47:54 -0800 (PST)
	(envelope-from bf20761@binghamton.edu)
Received: from bingnet2.cc.binghamton.edu(128.226.1.18) by mailscan.binghamton.edu via csmap 
	 id 20626; Fri, 14 Mar 2003 12:51:52 -0500 (EST)
Received: from bingsun2.cc.binghamton.edu (bf20761@bingsun2.cc.binghamton.edu [128.226.6.4])
	by bingnet2.cc.binghamton.edu (8.12.8/8.12.8) with ESMTP id h2EHlrMM021404
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 12:47:54 -0500 (EST)
Date: Fri, 14 Mar 2003 12:47:53 -0500 (EST)
From: Zhihui Zhang <bf20761@binghamton.edu>
X-X-Sender: bf20761@bingsun2.cc.binghamton.edu
To: freebsd-hackers@FreeBSD.ORG
Subject: Disk utilization command
Message-ID: <Pine.SOL.L4.44.0303141236300.4342-100000@bingsun2.cc.binghamton.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hi,

Can anyone please tell me what is the command and syntax of it that can
display how much time in percentage a disk is busy?  iostat is supposed to
do that, but I could not figure out the syntax.

Thanks,

-Zhihui

-- 



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


From owner-freebsd-hackers  Fri Mar 14 10:15:50 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4ECF337B40A
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 10:15:49 -0800 (PST)
Received: from mail1.qc.uunet.ca (mail1.qc.uunet.ca [198.168.54.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 475C143FA3
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 10:15:48 -0800 (PST)
	(envelope-from anarcat@espresso-com.com)
Received: from xtanbul.studio.espresso-com.com ([216.94.147.57])
	by mail1.qc.uunet.ca (8.12.8/8.12.8) with ESMTP id h2EIFXvD019641;
	Fri, 14 Mar 2003 13:15:34 -0500
Received: from anarcat by xtanbul.studio.espresso-com.com with local (Exim 3.36 #1 (Debian))
	id 18ttiO-0000kk-00; Fri, 14 Mar 2003 13:15:32 -0500
Date: Fri, 14 Mar 2003 13:15:32 -0500
From: The Anarcat <anarcat@anarcat.ath.cx>
To: Zhihui Zhang <bf20761@binghamton.edu>
Cc: freebsd-hackers@freebsd.org
Subject: Re: Disk utilization command
Message-ID: <20030314181531.GB620@xtanbul>
References: <Pine.SOL.L4.44.0303141236300.4342-100000@bingsun2.cc.binghamton.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.SOL.L4.44.0303141236300.4342-100000@bingsun2.cc.binghamton.edu>
User-Agent: Mutt/1.5.3i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

systat -vm gives that, along other useful info.

A.

On Fri Mar 14, 2003 at 12:47:53PM -0500, Zhihui Zhang wrote:
> Hi,
> 
> Can anyone please tell me what is the command and syntax of it that can
> display how much time in percentage a disk is busy?  iostat is supposed to
> do that, but I could not figure out the syntax.
> 
> Thanks,
> 
> -Zhihui
> 
> -- 
> 
> 
> 
> 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  Fri Mar 14 13: 2: 8 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 57DDE37B401
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 13:02:07 -0800 (PST)
Received: from smtp2.suscom.net (userweb.suscom.net [64.78.119.248])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 80B8A43F85
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 13:02:06 -0800 (PST)
	(envelope-from ath@niksun.com)
Received: from localhost (userweb.suscom.net [64.78.119.248])
	by smtp2.suscom.net (Postfix) with ESMTP id B9DA1111C1D
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 16:02:04 -0500 (EST)
Received: from celis.niksun.com (ip216.71.susc.suscom.net [64.78.71.216])
	by smtp2.suscom.net (Postfix) with ESMTP id 329E9111B1A
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 16:00:21 -0500 (EST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by celis.niksun.com (8.12.3/8.12.3) with ESMTP id h2EL0KnI001902
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 16:00:20 -0500 (EST)
	(envelope-from ath@niksun.com)
Subject: Quantum bigfoot drive doesn't like DMA?
From: Andrew Heybey <ath@niksun.com>
To: freebsd-hackers@freebsd.org
Content-Type: text/plain
Organization: 
Message-Id: <1047675620.1639.43.camel@celis>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 
Date: 14 Mar 2003 16:00:20 -0500
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS new-20020517
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

I recently installed an old Quantum bigfoot drive (CY4320A) in my SMP
box running 4.6.2 just to get a little extra space.  If I write heavily
to it when using WDMA2, the box silently crashes (no panic, just a
silent reboot).  The box has an DFI motherboard with an Intel BX
chipset.

It seems similar to problems others have had with this drive (or maybe
the combination of this drive and the PIIX4 controller).  From the
linux-kernel mailing list:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&th=efa3cf2a3a198ae0&seekm=fa.l5mj6dv.i2akim%40ifi.uio.no

and also with freebsd (though this guy did not actually suffer a crash):

http://www.freebsd.org/cgi/getmsg.cgi?fetch=17576+23166+/usr/local/www/db/text/1999/freebsd-current/19990214.freebsd-current

I did run across a Compaq "patch" for windows 95 and this drive that
says it detects the problem and turns off DMA if it happens...

It seems to work okay in PIO4 mode.  Are there any possible solutions,
or am I just stuck with PIO on this drive?  I didn't see any commits to
the ata code since 4.6.2 whose log message look like they might
workaround this problem.

thanks,
andrew



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


From owner-freebsd-hackers  Fri Mar 14 13:55:41 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D262F37B401
	for <freebsd-hackers@FreeBSD.org>; Fri, 14 Mar 2003 13:55:39 -0800 (PST)
Received: from sunfire.lclark.edu (sunfire.lclark.edu [149.175.1.5])
	by mx1.FreeBSD.org (Postfix) with SMTP id 00C3343F3F
	for <freebsd-hackers@FreeBSD.org>; Fri, 14 Mar 2003 13:55:39 -0800 (PST)
	(envelope-from eta@lclark.edu)
Received: from [149.175.30.191] ([149.175.30.191])
 by sunfire.lclark.edu (SAVSMTP 3.0.1.45) with SMTP id M2003031413553726694
 for <freebsd-hackers@FreeBSD.org>; Fri, 14 Mar 2003 13:55:37 -0800
Subject: per-open device private data, mmap
From: Eric Anholt <eta@lclark.edu>
To: freebsd-hackers@FreeBSD.org
Content-Type: text/plain
Organization: 
Message-Id: <1047679166.622.23.camel@leguin>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 
Date: 14 Mar 2003 13:59:26 -0800
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

To work properly, the DRM needs an area of memory per open of the device
which stores information on whether that fd is authenticated and also to
have a unique identifier for use in the lock.  Currently we use
drm_find_file_by_proc to get the private data and use the pid as the
unique identifier, but for example this causes problems if a fork occurs
(threaded linux programs).  This information is needed in the entry
points (open, close, ioctl). (read, write, and poll from the current
code are being stubbed out because they are unnecessary).

To do this, I'm working on following what dev/streams/streams.c does in
creating a new struct file and setting its own fileops and using the
f_data field for the pointer to the private data.  This looks pretty
good for open/close/ioctl, but there's a problem with mmap.  Currently
we use drm_find_file_by_proc in the mmap handler to see if that process
is authenticated, but there's no way from the mmap handler to get the
private data because the struct file * isn't passed in.  My initial
thought was to instead check the authentication in the DRM(mapbufs)
ioctl, where the vm_mmap is done by the X Server or clients.  The
problem with this is that a process could still do an mmap() on the fd
and avoid the authentication check.

What I'm wondering at this point is, is there any way to prevent the
mmap() from succeeding (nothing legitimate uses mmap -- it's all done
with the mapbufs ioctl), or a way to make it so from the device's mmap
handler I can detect whether mmap() or mapbufs made the mapping, or to
have different mmap handlers for those two vm_mmap callers.  What's the
best way to do this?

-- 
Eric Anholt                                eta@lclark.edu          
http://people.freebsd.org/~anholt/         anholt@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 Mar 14 14: 5:23 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1A78E37B401
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 14:05:22 -0800 (PST)
Received: from sunfire.lclark.edu (lclark.edu [149.175.1.5])
	by mx1.FreeBSD.org (Postfix) with SMTP id 4217743FA3
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 14:05:21 -0800 (PST)
	(envelope-from eta@lclark.edu)
Received: from [149.175.30.191] ([149.175.30.191])
 by sunfire.lclark.edu (SAVSMTP 3.0.1.45) with SMTP id M2003031414051919767
 for <freebsd-hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 14:05:19 -0800
Subject: Re: per-open device private data, mmap
From: Eric Anholt <eta@lclark.edu>
To: freebsd-hackers@FreeBSD.ORG
In-Reply-To: <1047679166.622.23.camel@leguin>
References: <1047679166.622.23.camel@leguin>
Content-Type: text/plain
Organization: 
Message-Id: <1047679748.622.30.camel@leguin>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 
Date: 14 Mar 2003 14:09:08 -0800
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Fri, 2003-03-14 at 13:59, Eric Anholt wrote:
> To work properly, the DRM needs an area of memory per open of the device
> which stores information on whether that fd is authenticated and also to
> have a unique identifier for use in the lock.  Currently we use
> drm_find_file_by_proc to get the private data and use the pid as the
> unique identifier, but for example this causes problems if a fork occurs
> (threaded linux programs).  This information is needed in the entry
> points (open, close, ioctl). (read, write, and poll from the current
> code are being stubbed out because they are unnecessary).
> 
> To do this, I'm working on following what dev/streams/streams.c does in
> creating a new struct file and setting its own fileops and using the
> f_data field for the pointer to the private data.  This looks pretty
> good for open/close/ioctl, but there's a problem with mmap.  Currently
> we use drm_find_file_by_proc in the mmap handler to see if that process
> is authenticated, but there's no way from the mmap handler to get the
> private data because the struct file * isn't passed in.  My initial
> thought was to instead check the authentication in the DRM(mapbufs)
> ioctl, where the vm_mmap is done by the X Server or clients.  The
> problem with this is that a process could still do an mmap() on the fd
> and avoid the authentication check.
> 
> What I'm wondering at this point is, is there any way to prevent the
> mmap() from succeeding (nothing legitimate uses mmap -- it's all done
> with the mapbufs ioctl), or a way to make it so from the device's mmap
> handler I can detect whether mmap() or mapbufs made the mapping, or to
> have different mmap handlers for those two vm_mmap callers.  What's the
> best way to do this?

Gah, and the instant I hit 'send' I realize that things /do/ use mmap
and mapbufs is only for agp/sg memory.  I guess it'll be okay to keep
drm_find_file_by_proc and grab authentication information from there; it
shouldn't be too big of an issue.  The unique identifier is the big
problem and the fileops trick should work for that.

However, is this going to get easier some day?  Are there any plans to
pass the struct file down to the drivers and have a void * in there for
private data?

Also, we need to be blocking SIGSTOP and such things while the lock is
held so that people don't hang the X Server by suspending a client while
it holds the lock.  Does anyone know about how to do this?

-- 
Eric Anholt                                eta@lclark.edu          
http://people.freebsd.org/~anholt/         anholt@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 Mar 14 14:34:42 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8720E37B404
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 14:34:37 -0800 (PST)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4A2FF43FBD
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 14:34:34 -0800 (PST)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.12.8/8.12.8) with ESMTP id h2EMYXRv017678
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 14 Mar 2003 17:34:33 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h2EMYSS91800;
	Fri, 14 Mar 2003 17:34:28 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15986.22772.414400.413308@grasshopper.cs.duke.edu>
Date: Fri, 14 Mar 2003 17:34:28 -0500 (EST)
To: Eric Anholt <eta@lclark.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: per-open device private data, mmap
In-Reply-To: <1047679748.622.30.camel@leguin>
References: <1047679166.622.23.camel@leguin>
	<1047679748.622.30.camel@leguin>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


Eric Anholt writes:
 > shouldn't be too big of an issue.  The unique identifier is the big
 > problem and the fileops trick should work for that.
 > 
 > However, is this going to get easier some day?  Are there any plans to
 > pass the struct file down to the drivers and have a void * in there for
 > private data?
 > 

I think that phk is working on this for 6.x

In the meantime, I have a new driver I"m developing which uses the
fileops trick you describe, but takes it a step further and conjurs up
a new vnode.  That makes it work with mmap.  I've not run into
any problems yet, but it is lightly tested.

Cheers,

Drew


/*
 * Conjure up our own vnode out of thin air.  We need the
 * vnode so that we can stash a pointer to the per-connection
 * priv struct for use in open/close/ioctl and mmap.  This is
 * tricky, because we need make it look enough like the device
 * vnode so that VOP_GETATTR() works on the slave vnode in mmap()
 */

static int
xxx_conjur_vnode(dev_t dev, struct thread *td)
{
  int error, fd;
  struct filedesc *fdp;
  struct file *fp;
  struct vnode *vn = NULL, *vd = NULL;
  struct cdev *rdev;

  fdp = td->td_proc->p_fd;
  if (fdp == NULL)
    return (0);

  if (td->td_dupfd >= 0)
    return ENODEV;

  rdev = xxx_malloc(sizeof(*rdev), M_WAITOK);

  if ((error = falloc(td, &fp, &fd)) != 0)
    goto abort_with_rdev;

  vd = SLIST_FIRST(&dev->si_hlist);

  if ((error = getnewvnode("none", vd->v_mount, vd->v_op, &vn)))
    goto abort_with_falloc;

  vn->v_type = VCHR;

  /* XXXX really should clone v_vdata & not copy pointer */
  vn->v_data = vd->v_data;        /* for VTOI in devfs_getattr() */

  /* copy our cdev info */
  vn->v_rdev = rdev;
  bcopy(vd->v_rdev, vn->v_rdev, sizeof(*rdev));

  /* finally, save the data pointer (our softc) */
  vn->v_rdev->si_drv2 = 0;

  fp->f_data = (caddr_t)vn;
  fp->f_flag = FREAD|FWRITE;
  fp->f_ops = &xxx_fileops;
  fp->f_type = DTYPE_VNODE;       /* so that we can mmap */

  /*
   * Save the new fd as dupfd in the proc structure, then we have
   * open() return the special error code (ENXIO).  Returning with a
   * dupfd and ENXIO causes magic things to happen in kern_open().
   */
  td->td_dupfd = fd;
  return 0;

 abort_with_rdev:
  xxx_free(rdev);

 abort_with_falloc:
  FILEDESC_LOCK(fdp);
  fdp->fd_ofiles[fd] = NULL;
  FILEDESC_UNLOCK(fdp);
  fdrop(fp, td);


  return (error);

}

static int
xxx_fileclose(struct file *fp, struct thread *td)
{
  int ready_to_close;
  struct vnode *vn;
  struct cdev *rdev;
  xxx_port_state_t *ps;

  vn = (struct vnode *)fp->f_data;
  rdev = vn->v_rdev;
  ps = rdev->si_drv2;
  rdev->si_drv2 = NULL;

  /* replace the vnode ops so that devfs doesn't try to reclaim
     anything */
  vn->v_op = spec_vnodeop_p;
  vn->v_type = VNON; /* don't want to freedev() in vgonel()*/
  vgone(vn);

  /* free our private rdev */
  xxx_free(rdev);

  if (ps) {
    xxx_mutex_enter(&ps->sync);

    /* Close the port if there are no more mappings */
    ready_to_close = ps->ref_count == 0;
    XXX_DEBUG_PRINT (XXX_DEBUG_OPENCLOSE,
                    ("Board %d, port %d closed\n", ps->is->id, ps->port));

    xxx_mutex_exit(&ps->sync);

    if (ready_to_close) {
      xxx_common_close (ps);
    } else {
      XXX_INFO (("Application closed file descriptor while "
                "mappings still alive: port destruct delayed\n"));
    }
  }

  return (0);
}


static int
xxx_mmap(dev_t dev, vm_offset_t offset,
#if MMAP_RETURNS_PINDEX == 0
        vm_offset_t *paddr,
#endif
        int nprot)
{
  int status;
  xxx_port_state_t *ps;
  void *kva;
#if MMAP_RETURNS_PINDEX
  vm_offset_t phys;
  vm_offset_t *paddr = &phys;
#endif

  ps = (xxx_port_state_t *)dev->si_drv2;
<...>


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


From owner-freebsd-hackers  Fri Mar 14 15:36:27 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9703B37B401
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 15:36:26 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9E9F743F75
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 14 Mar 2003 15:36:25 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.8/8.12.8) with ESMTP id h2ENaMh8013857;
	Sat, 15 Mar 2003 00:36:23 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: Eric Anholt <eta@lclark.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: per-open device private data, mmap 
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "14 Mar 2003 13:59:26 PST."
             <1047679166.622.23.camel@leguin> 
Date: Sat, 15 Mar 2003 00:36:22 +0100
Message-ID: <13856.1047684982@critter.freebsd.dk>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

In message <1047679166.622.23.camel@leguin>, Eric Anholt writes:
>To work properly, the DRM needs an area of memory per open of the device
>which stores information on whether that fd is authenticated and also to
>have a unique identifier for use in the lock.

I have some plans for this for 6.x but we would have multiple respiratory
failures in the re@ team if I even think about it until the RELENG_5
branch has been laid down, so for now you're on your own.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

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


From owner-freebsd-hackers  Fri Mar 14 15:51:35 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DAA2037B401
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 15:51:32 -0800 (PST)
Received: from office.advantagecom.net (office.advantagecom.net [207.109.186.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E67C243FA3
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 15:51:31 -0800 (PST)
	(envelope-from andykinney@advantagecom.net)
Received: from scsi-monster (andy.advantagecom.net [207.109.186.200] (may be forged))
	by office.advantagecom.net (8.9.3/8.9.3) with ESMTP id PAA25215
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 15:51:30 -0800
From: "Andrew Kinney" <andykinney@advantagecom.net>
Organization: Advantagecom Networks, Inc.
To: freebsd-hackers@freebsd.org
Date: Fri, 14 Mar 2003 15:54:13 -0800
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: increasing KVA_PAGES and broken pthreads
Reply-To: andykinney@advantagecom.net
Message-ID: <3E71FB25.27881.363E6F4@localhost>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hello,

I'm brand new to this list so feel free to tell me to search the 
archives if this question has already been answered.  I have already 
done some searching and only found limited and/or antiquated 
information on the subject, though, so I'm pretty sure this hasn't 
been addressed yet.

Does anyone know if a PR was ever submitted for the issue at:

http://www.mail-archive.com/freebsd-hackers@freebsd.org/msg38532.html

I know from reading the thread that a patch was created and sent 
to this list.  Was that patch ever made a part of the CVS tree?  If 
so, what branch would I have to track to pick up that patch?  I'd like 
to avoid adding patches that CVSup will clobber later.

I've seen this same issue with FreeBSD 4.5-RELEASE running on 
a heavily loaded web/mail/database server with dual CPU and 4GB 
of RAM and 8GB of available swap (no swapping activity).  Setting 
KVA_PAGES=512 rather than the default 256 caused MySQL to 
die repeatedly with signal 6 as fast as it could respawn itself.  The 
MySQL daemon was compiled on another FreeBSD 4.x system 
and was part of a prepackaged application from a commercial 
vendor.

I've already tuned the system quite a bit to get around a lot of the 
"large memory" issues.  However, because of all the tuning to avoid 
running out of various kernel resources before we ran out of 
physical RAM, we're now running out of KVM or will very soon.  

%sysctl -a |grep kvm
vm.kvm_size: 1065353216
vm.kvm_free: 4194304
%sysctl kern.maxusers
kern.maxusers: 384  (the autoscale max)

In particular, we had to take PMAP_SHPGPERPROC up to 1500 
from the default of 200 due to the large amount of shared memory 
pages that Apache needs to do its job efficiently.  That puts KVM 
usage by PV Entries alone to nearly 300MB.  We were getting 
kernel panics every time we ran out of available PV Entries 
(vm.zone: PV ENTRY), so this was very necessary.  We also had 
to increase NMBCLUSTERS to 12800 (higher than the autoscale 
max).  This also put some pressure on free KVM.

We're now tracking RELENG_4_7 (FreeBSD 4.7-RELEASE + 
security fixes).  I haven't tried changing KVA_PAGES since version 
4.5 and I'm a little gun-shy on changing that particular tunable 
since it has so many potential application gotchas, like with 
pthreads.

The RELENG_4_7 CVS tree (updated yesterday) doesn't appear to 
have the patch mentioned in the thread I referenced in the URL at 
the beginning of my message.  Our version string for that file:

* $FreeBSD: src/lib/libc_r/uthread/uthread_init.c,v 1.23.2.7 2001/11/03 00:33:07 peter Exp $

IMHO, this issue could be a royal pain in the butt when I start 
working on quad processor systems with 32GB of RAM (not 
unrealistic at this company).  I'd like to stay with FreeBSD, but the 
issues with large memory support are rapidly becoming more 
prominent due to the *huge* memory systems in use here, with 
even larger memory systems on the way in the near future.  I came 
from the Linux camp (back when 2.0/2.2 kernels were the newest 
in use) and I don't want to have to go back, though I no longer have 
any clue how those boys handle large memory systems.  Maybe 
they're not any better in that department.  I just happen to like 
FreeBSD better and would prefer to stick with it if possible.

So, to recap my questions, what branch would I have to track to 
pick up that patch to pthreads?  If there is no branch with that 
patch, has a PR been submitted so it can eventually be included in 
the source?  If so, what is the PR number?  If not, what's the best 
way to submit a PR?

Thanks in advance for any assistance in this matter.




Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net


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


From owner-freebsd-hackers  Fri Mar 14 16: 8:43 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9850A37B401
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 16:08:40 -0800 (PST)
Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4F30C43FD7
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 16:08:39 -0800 (PST)
	(envelope-from julian@elischer.org)
Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4])
          by sccrmhc03.attbi.com (sccrmhc03) with ESMTP
          id <2003031500083800300akcp9e>; Sat, 15 Mar 2003 00:08:38 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA45186;
	Fri, 14 Mar 2003 16:08:36 -0800 (PST)
Date: Fri, 14 Mar 2003 16:08:34 -0800 (PST)
From: Julian Elischer <julian@elischer.org>
To: Andrew Kinney <andykinney@advantagecom.net>
Cc: freebsd-hackers@freebsd.org
Subject: Re: increasing KVA_PAGES and broken pthreads
In-Reply-To: <3E71FB25.27881.363E6F4@localhost>
Message-ID: <Pine.BSF.4.21.0303141602150.44309-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG



On Fri, 14 Mar 2003, Andrew Kinney wrote:

> Hello,
> 
> I'm brand new to this list so feel free to tell me to search the 
> archives if this question has already been answered.  I have already 
> done some searching and only found limited and/or antiquated 
> information on the subject, though, so I'm pretty sure this hasn't 
> been addressed yet.
> 
> Does anyone know if a PR was ever submitted for the issue at:
> 
> http://www.mail-archive.com/freebsd-hackers@freebsd.org/msg38532.html
> 

That patch is in the RELENG_4 tree and will be included in 4.8




> I know from reading the thread that a patch was created and sent 
> to this list.  Was that patch ever made a part of the CVS tree?  If 
> so, what branch would I have to track to pick up that patch?  I'd like 
> to avoid adding patches that CVSup will clobber later.

yes it was.. but not in RELENG_4_7 because that is for security patches.

> 
> We're now tracking RELENG_4_7 (FreeBSD 4.7-RELEASE + 
> security fixes).  I haven't tried changing KVA_PAGES since version 
> 4.5 and I'm a little gun-shy on changing that particular tunable 
> since it has so many potential application gotchas, like with 
> pthreads.
> 
> The RELENG_4_7 CVS tree (updated yesterday) doesn't appear to 
> have the patch mentioned in the thread I referenced in the URL at 
> the beginning of my message.  Our version string for that file:
> 
> * $FreeBSD: src/lib/libc_r/uthread/uthread_init.c,v 1.23.2.7 2001/11/03 00:33:07 peter Exp $

4.7 is being left behind.. look at 4.8


> 
> IMHO, this issue could be a royal pain in the butt when I start 
> working on quad processor systems with 32GB of RAM (not 
> unrealistic at this company). 


Well we can't USE 32GB od RAM yet.. I doubt that 4.x will ever be able
to do that (though I could be proven wrong).

> I'd like to stay with FreeBSD, but the 
> issues with large memory support are rapidly becoming more 
> prominent due to the *huge* memory systems in use here, with 
> even larger memory systems on the way in the near future.  I came 
> from the Linux camp (back when 2.0/2.2 kernels were the newest 
> in use) and I don't want to have to go back, though I no longer have 
> any clue how those boys handle large memory systems.  Maybe 
> they're not any better in that department.  I just happen to like 
> FreeBSD better and would prefer to stick with it if possible.
>

track RELENG_4

 
> So, to recap my questions, what branch would I have to track to 
> pick up that patch to pthreads?  If there is no branch with that 
> patch, has a PR been submitted so it can eventually be included in 
> the source?  If so, what is the PR number?  If not, what's the best 
> way to submit a PR?
> 
> Thanks in advance for any assistance in this matter.
> 


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


From owner-freebsd-hackers  Fri Mar 14 16:54:45 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AEFC737B401
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 16:54:42 -0800 (PST)
Received: from office.advantagecom.net (office.advantagecom.net [207.109.186.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 02BC443F85
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 16:54:42 -0800 (PST)
	(envelope-from andykinney@advantagecom.net)
Received: from scsi-monster (andy.advantagecom.net [207.109.186.200] (may be forged))
	by office.advantagecom.net (8.9.3/8.9.3) with ESMTP id QAA26250;
	Fri, 14 Mar 2003 16:54:35 -0800
From: "Andrew Kinney" <andykinney@advantagecom.net>
Organization: Advantagecom Networks, Inc.
To: Julian Elischer <julian@elischer.org>
Date: Fri, 14 Mar 2003 16:57:18 -0800
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: increasing KVA_PAGES and broken pthreads
Reply-To: andykinney@advantagecom.net
Cc: freebsd-hackers@freebsd.org
Message-ID: <3E7209EE.8610.39DAB11@localhost>
References: <3E71FB25.27881.363E6F4@localhost>
In-reply-to: <Pine.BSF.4.21.0303141602150.44309-100000@InterJet.elischer.org>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On 14 Mar 2003, at 16:08, Julian Elischer wrote:

> 
> That patch is in the RELENG_4 tree and will be included in 4.8
> 

Great!  Thanks for the info.

> 
> yes it was.. but not in RELENG_4_7 because that is for security
> patches.
> 

I'm showing my newbieness here.  :-)  Apologies.  I knew that, but 
for some reason it didn't occur to me that patches such as this 
would only occur on the development branches.

> 
> 4.7 is being left behind.. look at 4.8
> 

I guess I'll just wait for 4.8 to reach "RELEASE" level then and 
work on reducing the workload of the system in the meantime, 
though the hardware is nowhere near overloaded.  I wish I could 
track CURRENT, but I'm squeamish about that for a production 
system such as this.

> > IMHO, this issue could be a royal pain in the butt when I start
> > working on quad processor systems with 32GB of RAM (not unrealistic
> > at this company). 
>
> Well we can't USE 32GB od RAM yet.. I doubt that 4.x will ever be able
> to do that (though I could be proven wrong).
> 

Really?  I was under the impression that FreeBSD was capable of 
addressing 8TB of RAM if the hardware supports it.  Don't 
remember which FreeBSD list archive I read that in, but it's not a 
topic that seems to come up often since most hardware is limited 
to 4GB of address space.  I've got access to hardware that can 
address 32GB of RAM.  Not sure of the exact details of how it 
works (multiple external memory managers?), but it's a quad Xeon 
board by SuperMicro.

If it's a question of "is there any application that can ever use that 
much RAM", we're certainly testing the limits here. :-)  We're not 
swapping at all with 4GB, but on several occasions we've gotten 
close or swapped a few hundred KB.  Our two little 2GHz CPUs 
are humming right along, but most of the time they're better than 
60% idle.  I imagine that if we pushed the CPUs a bit harder or got 
hit with a big traffic spike, we'd probably start swapping and want to 
start thinking about a system that can handle more RAM.  

Of course, that's assuming that the OS or applications don't break 
before the hardware gets up to a decent load.  Hence, I'm hoping to 
get a lot of the large memory OS issues resolved (many are by 
tuning) so we can at least get what we paid for out of the hardware.



Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net


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


From owner-freebsd-hackers  Fri Mar 14 17:13:43 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 679B437B401
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 17:13:41 -0800 (PST)
Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E0B9143F75
	for <freebsd-hackers@freebsd.org>; Fri, 14 Mar 2003 17:13:40 -0800 (PST)
	(envelope-from julian@elischer.org)
Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4])
          by rwcrmhc52.attbi.com (rwcrmhc52) with ESMTP
          id <2003031501134005200t41eee>; Sat, 15 Mar 2003 01:13:40 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA45589;
	Fri, 14 Mar 2003 17:13:34 -0800 (PST)
Date: Fri, 14 Mar 2003 17:13:32 -0800 (PST)
From: Julian Elischer <julian@elischer.org>
To: Andrew Kinney <andykinney@advantagecom.net>
Cc: freebsd-hackers@freebsd.org
Subject: Re: increasing KVA_PAGES and broken pthreads
In-Reply-To: <3E7209EE.8610.39DAB11@localhost>
Message-ID: <Pine.BSF.4.21.0303141709400.44309-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG



On Fri, 14 Mar 2003, Andrew Kinney wrote:

> On 14 Mar 2003, at 16:08, Julian Elischer wrote:
> 
> > 
> > That patch is in the RELENG_4 tree and will be included in 4.8
> > 
> 
> Great!  Thanks for the info.
> 
> > 
> > yes it was.. but not in RELENG_4_7 because that is for security
> > patches.
> > 
> 
> I'm showing my newbieness here.  :-)  Apologies.  I knew that, but 
> for some reason it didn't occur to me that patches such as this 
> would only occur on the development branches.
> 
> > 
> > 4.7 is being left behind.. look at 4.8
> > 
> 
> I guess I'll just wait for 4.8 to reach "RELEASE" level then and 
> work on reducing the workload of the system in the meantime, 
> though the hardware is nowhere near overloaded.  I wish I could 
> track CURRENT, but I'm squeamish about that for a production 
> system such as this.

look at RELENG_4 "NOW" because that will become 4.8.
if you have problems with it  then now is the time ot speak up before
4.8 is frozen in stone.


> 
> > > IMHO, this issue could be a royal pain in the butt when I start
> > > working on quad processor systems with 32GB of RAM (not unrealistic
> > > at this company). 
> >
> > Well we can't USE 32GB od RAM yet.. I doubt that 4.x will ever be able
> > to do that (though I could be proven wrong).
> > 
> 
> Really?  I was under the impression that FreeBSD was capable of 
> addressing 8TB of RAM if the hardware supports it.

On a ia64 machine I think (which i386 is not)

>  Don't 
> remember which FreeBSD list archive I read that in, but it's not a 
> topic that seems to come up often since most hardware is limited 
> to 4GB of address space.  I've got access to hardware that can 
> address 32GB of RAM.  Not sure of the exact details of how it 
> works (multiple external memory managers?), but it's a quad Xeon 
> board by SuperMicro.
> 
> If it's a question of "is there any application that can ever use that 
> much RAM", we're certainly testing the limits here. :-)  We're not 
> swapping at all with 4GB, but on several occasions we've gotten 
> close or swapped a few hundred KB.  Our two little 2GHz CPUs 
> are humming right along, but most of the time they're better than 
> 60% idle.  I imagine that if we pushed the CPUs a bit harder or got 
> hit with a big traffic spike, we'd probably start swapping and want to 
> start thinking about a system that can handle more RAM.  

There is a possibility that it could be done but not right now..
There are other things that are higher on the lists.


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


From owner-freebsd-hackers  Fri Mar 14 17:20: 9 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9F74337B401; Fri, 14 Mar 2003 17:20:07 -0800 (PST)
Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 80F0843FA3; Fri, 14 Mar 2003 17:20:05 -0800 (PST)
	(envelope-from keramida@ceid.upatras.gr)
Received: from gothmog.gr (patr530-b134.otenet.gr [212.205.244.142])
	by mailsrv.otenet.gr (8.12.8/8.12.8) with ESMTP id h2F1K15u000098;
	Sat, 15 Mar 2003 03:20:02 +0200 (EET)
Received: from gothmog.gr (gothmog [127.0.0.1])
	by gothmog.gr (8.12.8/8.12.8) with ESMTP id h2F1K0HG006334;
	Sat, 15 Mar 2003 03:20:00 +0200 (EET)
	(envelope-from keramida@ceid.upatras.gr)
Received: (from giorgos@localhost)
	by gothmog.gr (8.12.8/8.12.8/Submit) id h2EJfK0Q005264;
	Fri, 14 Mar 2003 21:41:20 +0200 (EET)
	(envelope-from keramida@ceid.upatras.gr)
Date: Fri, 14 Mar 2003 21:41:19 +0200
From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: Warner Losh <imp@freebsd.org>, freebsd-hackers@freebsd.org
Subject: style of sysctl description strings
Message-ID: <20030314194119.GA5226@gothmog.gr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed
Content-Disposition: inline
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (terpsi)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

While trying to write a small script that would help Tom Rhodes to
extract the list of sysctl names and descriptions from a running
kernel, I noticed the following (pardon the long lines):

hw.pci.enable_io_modes: Enable I/O and memory bits in the config register.  Some BIOSes do not
enable these bits correctly.  We'd like to do this all the time, but there
are some peripherals that this causes problems with.
hw.pci.allow_unsupported_io_range: Allows the PCI Bridge to pass through an unsupported memory range assigned by the BIOS.

The description of hw.pci.enable_io_modes uses embedded '\n'
characters to keep the length of the description below 80 columns.
It works fine.  But only for the description text, which doesn't
appear in the output of:

% sysctl -dna | cut -c 80- | grep -v '^[[:space:]]*$'

Strangely, this is the only sysctl that I could spot in the entire
tree with '\n' characters in the description.  The next sysctl in the
output of sysctl -ad is hw.pci.allow_unsupported_io_range as shown
above, which doesn't make any effort to keep the text below 80
columns.

Is there a reason for wrapping with '\n'?  If yes, what would that be?
I'm only asking because it would make my life simpler if the sysctl
descriptions didn't have embedded newlines, and this is a good
opportunity to learn something too :-)

- - Giorgos
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+cjBf1g+UGjGGA7YRAic3AJ0SgcgupeQiEqoOiBUWHbqzcMq1igCePFvC
9yg+XSZaqtXCpN3cKyyRjzU=
=6IkN
-----END PGP SIGNATURE-----

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


From owner-freebsd-hackers  Fri Mar 14 22: 8: 4 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0360837B404
	for <hackers@freebsd.org>; Fri, 14 Mar 2003 22:08:03 -0800 (PST)
Received: from freebsd.giovannelli.com (freebsd.giovannelli.com [194.184.65.139])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4C02943F75
	for <hackers@freebsd.org>; Fri, 14 Mar 2003 22:08:01 -0800 (PST)
	(envelope-from gmarco@giovannelli.it)
Received: from usul.giovannelli.it (usul.giovannelli.com [10.254.254.4])
	by freebsd.giovannelli.com (8.12.7/8.12.7) with ESMTP id h2G6A6kB002840
	for <hackers@freebsd.org>; Sun, 16 Mar 2003 07:10:08 +0100 (CET)
	(envelope-from gmarco@giovannelli.it)
Message-Id: <5.2.0.9.2.20030315065251.011c66c8@194.184.65.4>
X-Sender: gmarco@194.184.65.4 (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sat, 15 Mar 2003 07:09:13 +0100
To: hackers@freebsd.org
From: Gianmarco Giovannelli <gmarco@giovannelli.it>
Subject: locale setup, automagically  ? 
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hi,
this is more a whish ...
Sometime ago I was discussing with some friends about localization and we 
arrive to ask why not having all the locale settings configured in one 
place only.

I'll try to explain better...
I am italian. If I want to take advantage of everything the italian locale 
have to offer in FreeBSD I have to config a lot of files.

using a right terminal i.e:
cons25l1

/etc/rc.conf:
keymap="it.iso"
font8x8="iso15-8x8"
font8x14="iso15-8x14"
font8x16="iso15-8x16"

~/.login_conf
me:\
     :charset=iso-8859-15:\
     :lang=it_IT.ISO8859-15:

/etc/ttys
put cons25i (or 30i) in the ttys line


while I can have a db (like pccard.conf i.e) that can be set to exec all 
this tasks in one shot:

vidcontrol -f 8x16 iso15-8x16.fnt
kbdcontrol -l it.iso.kbd
setenv LANG it_IT.ISO8859-15
setenv MM_CHARSET iso-8859-15
setenv TERM cons25l1

so in my /etc/rc.conf I can have i.e:
locale=italy

and the during boot everything automagically is setup.

Thanks for attention.




Best Regards,
Gianmarco Giovannelli ,  "Unix expert since yesterday"
http://www.gufi.org/~gmarco



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


From owner-freebsd-hackers  Sat Mar 15  0:31:51 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3C35237B401
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 15 Mar 2003 00:31:50 -0800 (PST)
Received: from HAL9000.homeunix.com (12-233-57-224.client.attbi.com [12.233.57.224])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B387743FB1
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 15 Mar 2003 00:31:49 -0800 (PST)
	(envelope-from das@FreeBSD.ORG)
Received: from HAL9000.homeunix.com (localhost [127.0.0.1])
	by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id h2F8VlIX025896;
	Sat, 15 Mar 2003 00:31:47 -0800 (PST)
	(envelope-from das@FreeBSD.ORG)
Received: (from das@localhost)
	by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id h2F8VkHo025895;
	Sat, 15 Mar 2003 00:31:46 -0800 (PST)
	(envelope-from das@FreeBSD.ORG)
Date: Sat, 15 Mar 2003 00:31:46 -0800
From: David Schultz <das@FreeBSD.ORG>
To: Ferruccio Vitale <ferruccio.vitale@tin.it>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: variable size too large?
Message-ID: <20030315083146.GA25766@HAL9000.homeunix.com>
Mail-Followup-To: Ferruccio Vitale <ferruccio.vitale@tin.it>,
	freebsd-hackers@FreeBSD.ORG
References: <20030314153729.3825d4fe.ferruccio.vitale@tin.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030314153729.3825d4fe.ferruccio.vitale@tin.it>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Thus spake Ferruccio Vitale <ferruccio.vitale@tin.it>:
> I'm writing a little multithread program: in my thread function, I allocated a char variable of IP_MAXPACKET size; when I try to compile it, everything goes well, but when I run it, it dies, making a core file. 
> Assume that:
> 1) the same code, with only one thread, linked to libc, runs normally
> 2) the same code, with a smaller variable size, linked to libc_r, runs normally
> 3) I tried to allocate two variables of 64000 bytes in this function (IP_MAXPACKET is equal to 65535), linked to libc_r and runs normally
> 
> Where am I wrong? :))

Threads get much smaller stacks by default than monolithic
processes.  You should avoid making large allocations on the stack
in order to avoid this problem.  Use malloc()/free() instead.
(You can kludge around the problem by using larger stack sizes,
but you really shouldn't.)

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


From owner-freebsd-hackers  Sat Mar 15  1:55:20 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A1CA037B411
	for <hackers@freebsd.org>; Sat, 15 Mar 2003 01:55:08 -0800 (PST)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7F25443FB1
	for <hackers@freebsd.org>; Sat, 15 Mar 2003 01:55:07 -0800 (PST)
	(envelope-from scottl@FreeBSD.org)
Received: from freefall.freebsd.org (scottl@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h2F9t7NS062569
	for <hackers@freebsd.org>; Sat, 15 Mar 2003 01:55:07 -0800 (PST)
	(envelope-from scottl@freefall.freebsd.org)
Received: (from scottl@localhost)
	by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h2F9t7Ap062568
	for hackers@freebsd.org; Sat, 15 Mar 2003 01:55:07 -0800 (PST)
Date: Sat, 15 Mar 2003 01:55:07 -0800 (PST)
From: Scott Long <scottl@FreeBSD.org>
Message-Id: <200303150955.h2F9t7Ap062568@freefall.freebsd.org>
To: hackers@freebsd.org
Subject: January-February 2003 FreeBSD Bi-Monthly Status Report
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


January-February 2003 Status Report

                                 Introduction:

   Another busy two months have passed in the FreeBSD project. With 5.0
   released, attention is focusing on making it faster via more
   fine-grained locking, adding more high-end features like large memory
   (PAE) support for i386, and further progress on many other projects.
   FreeBSD 5.1 is expected to ship in late May or early June, with 5.2
   following at the end of summer. A roadmap for the push to 5-STABLE is
   available at [2]http://www.freebsd.org/doc/en/articles/5-roadmap.
   Although the 5.x series isn't expected to fully stabilize until the
   5.2 release, 5.1 promises to be an exciting release and a significant
   improvement over 5.0 in terms of speed and stability.

   Not to be forgotten, FreeBSD 4.8, the latest in the 4-STABLE series,
   is nearing release. Lots of last minute work is going into to it to
   deliver features like XFree86 4.3.0, Intel HyperThreading(tm) support,
   and of course many more bug fixes. Don't forget to support the FreeBSD
   vendors and developers by buying a copy of the CD set when it comes
   out!.

   Thanks,

   Scott Long, Robert Watson

Bluetooth stack for FreeBSD (Netgraph implementation)

   URL: http://www.geocities.com/m_evmenkin/
   URL: http://bluez.sf.net
   URL: http://sourceforge.net/projects/openobex/

   Contact: Maksim Yevmenkin <m_evmenkin@yahoo.com>

   I'm very pleased to announce that another release is available for
   download at
   http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030305.tar.gz

   This release features new in-kernel RFCOMM implementation that
   provides SOCK_STREAM sockets interface. This makes old user-space
   RFCOMM daemon obsolete. People should not use old user-space RFCOMM
   daemon any longer. The release features new RFCOMM PPP daemon that
   supports DUN and LAN profiles. Note: PPP patch (support for chat
   scripts in -direct mode) is required for DUN support. Look for it in
   the mailing list archive or contact me directly. People with Bluetooth
   enabled cell phones can now use them to access Internet.

   The Bluetooth sockets layer has been cleaned up. People should not see
   any WITNESS complains with new code. Locking issues have been
   revisited and code in much better shape now, although it probably is
   not 100% SMP ready just yet. The code should work on SMP system anyway
   because sockets layer is still under Giant.

   The simple OBEX server and client (based on OpenOBEX library) is
   complete. OBEX File Push and OBEX File Transfer profiles work and have
   been tested with Sony Ericsson T68i cell phone and Bluetooth 3COM
   stack on Windows2K. It is now possible to send pictures, address book
   and calendar entries from the cell phone via Bluetooth. Minor bug in
   OpenOBEX library has been fixed and OPEX Put-Empty command now works.

   Due to changes in API userland tools must be in sync with the kernel.
   People should install new include files, recompile and reinstall all
   userland tools as part of upgrade. I'm sorry about that.
     _________________________________________________________________

BSDCon 2003

   URL: http://www.usenix.org/events/bsdcon03/cfp/

   Contact: Gregory Shapiro <gshapiro@FreeBSD.org>

   The BSDCon 2003 Program Committee invites you to contribute original
   and innovative papers on topics related to BSD-derived systems and the
   Open Source world. Topics of interest include but are not limited to:
     * Embedded BSD application development and deployment
     * Real world experiences using BSD systems
     * Using BSD in a mixed OS environment
     * Comparison with non-BSD operating systems; technical, practical,
       licensing (GPL vs. BSD)
     * Tracking open source development on non-BSD systems
     * BSD on the desktop
     * I/O subsystem and device driver development
     * SMP and kernel threads
     * Kernel enhancements
     * Internet and networking services
     * Security
     * Performance analysis and tuning
     * System administration
     * Future of BSD

   Submissions in the form of extended abstracts are due by April 1,
   2003. Be sure to review the extended abstract expectations before
   submitting. Selection will be based on the quality of the written
   submission and whether the work is of interest to the community.

   We look forward to receiving your submissions!
     _________________________________________________________________

Buffer Cache lockdown

   Contact: Jeff Roberson <jeff@FreeBSD.org>

   Most of the file system buffer cache has been reviewed and protected.
   The vnode interlock was extended to cover some buffer flag fields so
   that a seperate interlock was not required. The global buffer queue
   data structures were locked and counters were converted to atomic ops.
   The BUF_*LOCK functions grew an interlock argument so that buffers
   could be safely removed from the vnode clean and dirty lists. The
   lockmgr lock is now required for all access to buf fields. This was
   not strictly followed before because splbio provided the needed
   protection.

   There are a few areas of code that need to be protected and cleaned up
   before giant can be pushed down. Most notably the back-ground write
   code is currently unsafe without giant. Also, many of the VM bits that
   the buffer cache relies on are not safe. This work has been done with
   the expectation that the VM and VFS subsystems will be giant free
   soon.
     _________________________________________________________________

Disk I/O improvements

   Contact: Poul-Henning Kamp <phk@FreeBSD.org>

   We have the first disk device driver (aac) out from under Giant now,
   and in certain scenarios it gives improvements up to 20%. The device
   drive API was pruned to reflect that NO_GEOM compatibility is
   unnecessary, this resulted in approx 1000 lines less source code, the
   majority of which were removed from the device drivers. The new API
   for cdevsw is a lot simpler and hopefully less likely to confuse
   people. A ability to automatically allocate a device major number has
   been introduced and is already used by a handful of drivers. Checks
   introduced with this facility has shown that the uniqueness of
   manually allocated major numbers had already broken down.

   Work continues on the statistics collection API and on a unified API
   for manual configuration of GEOM nodes.
     _________________________________________________________________

FreeBSD 4.8 Release Engineering

   URL: http://www.FreeBSD.org/releases/4.8R/schedule.html

   Contact: Murray Stokely <re@FreeBSD.org>

   The FreeBSD 4.8 Release Process is well underway. The RELENG_4 branch
   has been under code freeze since February 15, and the first release
   candidates were made available in early March. A testing guide has
   been put together and is available from
   http://www.FreeBSD.org/releases/4.8R/qa.html.

   Developers should coordinate with re@FreeBSD.org about any changes
   they would like to include in this release, and users are encouraged
   to try out the release candidates and help find as many bugs as
   possible now, before the final release is made.

   FreeBSD 4.8 represents the newest production release from the stable
   '4.X' branch. It does not include all of the features that were made
   available in the "new technology" 5.0 release in January.
     _________________________________________________________________

FreeBSD C99 & POSIX Conformance Project

   URL: http://www.FreeBSD.org/projects/c99/
   URL: http://people.FreeBSD.org/~schweikh/posix-utilities.html

   Contact: Mike Barcroft <mike@FreeBSD.org>
   Contact: FreeBSD-Standards Mailing List <standards@FreeBSD.org>

   January and February were quiet months that saw with them the addition
   of some C99 math functions and macros, which include: fpclassify(),
   isfinite(), isgreater(), isgreaterequal(), isinf(), isless(),
   islessequal(), islessgreater(), isnan(), isnormal(), and signbit().
   Additional C99 math library support is in the works.
     _________________________________________________________________

FreeBSD GNOME Project

   URL: http://www.freebsd.org/gnome/

   Contact: Joe Marcus <marcus@FreeBSD.org>
   Contact: Maxim Sobolev <sobomax@FreeBSD.org>
   Contact: Adam Weinberger <adamw@FreeBSD.org>

   FreeBSD 4.8-RELEASE will continue in the tradition of 5.0-RELEASE, and
   include GNOME 2 as the default GNOME desktop. This means that 4.8 will
   ship with GNOME 2.2.

   Following on the heels of the recent GNOME 2.2 release, GNOME 2.3
   snapshots are gearing up. The development schedule is available from
   http://www.gnome.org/start/2.3/. Ports will be made available the
   same way they were for the 2.1 development releases. Stay tuned to
   freebsd-gnome@ for more details.

   We are currently in another ports freeze in preparation for
   4.8-RELEASE. Following the freeze, a new bsd.gnome.mk will be
   committed that effectively removes the USE_GNOMENG macro. This new
   version will add support for GNOME 2 as well as setup backward
   compatibility for ports that have not yet been converted to the new
   GNOME infrastructure. People interested in testing this new Mk file,
   can check out the ``ports'' module following the instructions at
   http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi.
     _________________________________________________________________

FreeBSD Security Officer Team

   URL: http://www.freebsd.org/security/

   Contact: Jacques Vidrine <nectar@FreeBSD.org>

   In the period from September 2002 through February 2003, the FreeBSD
   Security Team email aliases saw 1297 messages, a much smaller volume
   than over the summer (remember the Apache and OpenSSL worms? 4.6.1
   oops I mean 4.6.2-RELEASE?).

   Also during this period: 95 items were added to the SO issue-tracking
   database; 39 of these involved the FreeBSD base system while the rest
   involved ports. 9 new Security Advisories were published, 2 of which
   covered issues unique to FreeBSD.

   In January, the SO published a new PGP key (ID 0xCA6CDFB2, found on
   the FTP site and in the Handbook). This aligned the set of those who
   possess the corresponding private key with the membership of the
   security-officer alias published on the FreeBSD Security web site. It
   also worked around an issue with the deprecated PGP key being found
   corrupted on some public key servers.

   In February, Mike Tancsa of Sentex donated two machines to the
   Security Officer. These have been a great help already in testing the
   security branches, preparing patches, and generating updated binaries.
   Thank you very much, Mike!
     _________________________________________________________________

FreeBSD/MIPS Status Report

   URL: http://www.FreeBSD.org/projects/mips/
   URL: http://www.FreeBSD.org/platforms/mips.html

   Contact: Juli Mallett <jmallett@FreeBSD.org>

   Large portions of headers have been filled in, all have been stubbed
   out. Minimal functions and data elements have been stubbed out or
   filled in. Machinery added to support some requisite tunables for
   building real kernels. GCC fixed to generate correct local label
   prefixes making it possible to link real kernels. Work begun on
   providing enough to create and boot real kernels, on real hardware.
   Decision to only support MIPS-III and above made.
     _________________________________________________________________

jpman project

   URL: http://www.jp.FreeBSD.org/man-jp/
   URL:
   ftp://daemon.jp.FreeBSD.org/pub/FreeBSD-jp/man-jp/packages-5.0.0/j
   a-man-doc-5.0.tbz

   Contact: Kazuo Horikawa <horikawa@FreeBSD.org>

   We have released Japanese translation of 5.0-RELEASE online manual
   pages on February 2nd. Most of entries which did not exist on RELENG_4
   were not yet translated. I hope we can finish such entries soon.
     _________________________________________________________________

KGI/FreeBSD Status Report

   URL: http://www.freebsd.org/~nsouch/ggiport.html
   URL: http://kgi-wip.sf.org

   Contact: Nicholas Souchu <nsouch@FreeBSD.org>

   The later months have been very busy on KGI. Most of the framework has
   been debugged for typical usage (fb, no accel). I got KII (the input
   interface) connected to syscons through atkbd. Opening /dev/graphic
   works and framebuffer resource access is permitted. Finally, the KGIM
   (KGI module) framework has a better building tree for board / monitor
   drivers and board drivers are now loading with resource allocation.

   Most important on the TODO list: 5.0-RELEASE move (I currently work
   with a May-2002 5.0-current). Most of debug is now done. Let's
   validate!

   Note that KGI project homepage has changed since the last report.
     _________________________________________________________________

New Doceng Body Formed

   URL: http://www.freebsd.org/internal/doceng.html

   Contact: Murray Stokely <doceng@FreeBSD.org>

   The doceng@ team is a new body to handle some of the meta-project
   issues associated with the FreeBSD Documentation Project. The main
   responsibilities of this team are to grant approval of new doc
   committers, to manage the doc release process, to ensure the
   documentation toolchains are functional, to maintain the doc project
   primer, and to maintain the sanctity of the doc/ and www/ trees. The
   current members of this team are Nik Clayton, Ruslan Ermilov, Jun
   Kuriyama, Bruce A. Mah, and Murray Stokely.
     _________________________________________________________________

PowerPC Port

   Contact: Peter Grehan <grehan@FreeBSD.org>

   Work on PowerPC is progressing steadily. The system can now boot
   multi-user from the net and disk. ATA-DMA is being integrated with the
   ATAng code, and support for older G3 machines is being added.
     _________________________________________________________________

Read-ahead performance

   Contact: Jeff Roberson <jeff@FreeBSD.org>

   Some improvements have been made to the clustered read ahead code.
   They allow for many more outstanding IO requests when an application
   does sequential access. This has a larger impact on RAID systems than
   on single disk systems. The maximum number of file system blocks that
   we will read ahead is tunable via the 'vfs.read_max' sysctl. This
   optimization has shown a 20% improvement in simple tests.
     _________________________________________________________________

SMP locking for network stack

   Contact: Jeffrey Hsu <hsu@FreeBSD.org>

   The list of subsystems locked up include IP, UDP, TCP, ifaddr
   reference counting, syncache, the ifnet list, routing radix trees, and
   ARP. These have already been committed into the tree. In addition, SMP
   locking for raw IP, divert socket processing, and Unix domain sockets
   have also recently been completed and tested. Work is currently being
   done in some of the subsystems required to make parallel networking
   processing SMP-safe.
     _________________________________________________________________

Status Report for Newbus lockdown

   Contact: Warner Losh <imp@FreeBSD.org>

   Locking of the non-obj parts of newbus is nearing completion. A single
   lock is used for the device tree. Minimal changes to subr_bus have so
   far been necessary to make this work, however some lock order issues
   remain. After this work, it will no longer be necessary to hold Giant
   to call device_* routines safely. kobj work is being done by others
   and will likely require more extensive design work to make smp
   friendly.
     _________________________________________________________________

Support for PAE and >4G ram on x86

   Contact: Jake Burkholder <jake@FreeBSD.org>

   Support for PAE is mostly complete, and has been checked into the
   jake_pae branch. The approach that is being taken to add support for
   PAE is to allow the pmap module to view the page table directory as 4
   pages instead of 1, and to avoid using the 3rd level structure, the
   page directory pointer table, as much as possible. Due to its small
   size, 32 bytes, the PDPT cannot be uniformly recursively mapped, and
   as such does not provide a regular multi level structure like the page
   tables used by the alpha or x86-64 architectures. What remains to be
   done for PAE support is to develop an API for manipulating page table
   entries which will allow idempotent 64 bit loads and stores to be used
   where necessary.

   Experimental support for >4G ram using PAE has been developed and
   checked into the jake_pae_test branch in Perforce. This involved
   adding a physical address type separate from virtual addresses, for
   use by the vm system and bus code which needs to use physical
   addresses directly. Initial testing has shown good results with device
   drivers that can dma to 64 bit physical addresses.

   Funding for this project is being provided by DARPA and Network
   Associate Laboratories, and hardware support by FreeBSD Systems.
     _________________________________________________________________

TCP congestion control

   Contact: Jeffrey Hsu <hsu@FreeBSD.org>

   The objective of this effort is to improve the performance, stability,
   and correctness of the BSD networking stack by adding support for new
   standards and standards track proposals while maintaining compliance
   with existing specifications. The upcoming 4.8 and 5.1 releases will
   be the first ones using the new NewReno logic. Recently, we
   implemented the Limited Transmit algorithm (RFC 3042) which benefits
   connections with small congestions windows, as happens, for example,
   on many short web connections. We also recently added support for
   larger sized starting congestion windows as described in RFC 3390.
   This helps short TCP connections as well as those with large
   round-trip delays, such as those over satellte links.
     _________________________________________________________________

ULE Scheduler

   Contact: Jeff Roberson <jeff@FreeBSD.org>

   The ULE scheduler has been commited to the 5.0-CURRENT branch. Early
   adopters and experimenters are welcome to try it and submit bug
   reports. It has shown noticable performance improvements over the old
   scheduler under some workloads. There are currently problems with nice
   fairness but otherwise the interactive performance is very good. More
   work to improve the load balancing algorithm is required as well. This
   should be ready for use by the general FreeBSD user base in the next
   month or so.

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


From owner-freebsd-hackers  Sat Mar 15  2: 4:42 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7A70137B40A
	for <freebsd-hackers@freebsd.org>; Sat, 15 Mar 2003 02:04:14 -0800 (PST)
Received: from 211-189-139-167.rev.krline.net (211-189-139-167.rev.krline.net [211.189.139.167])
	by mx1.FreeBSD.org (Postfix) with SMTP id 1995943F75
	for <freebsd-hackers@freebsd.org>; Sat, 15 Mar 2003 02:04:13 -0800 (PST)
	(envelope-from sender@refill.co.kr)
Received: from zOA (unverified [211.235.237.59]) by 211-189-139-167.rev.krline.net
 (EMWAC SMTPRS 0.83) with SMTP id <B0000154515@211-189-139-167.rev.krline.net>;
 Sat, 15 Mar 2003 06:54:52 +0900
Message-ID: <B0000154515@211-189-139-167.rev.krline.net>
Subject: =?ks_c_5601-1987?Q?(=B1=A4=B0=ED)=C0=FA=B7=C5=C7=D1_=C7=C1=B8=B0=C5=CD_=C5=E4=B3=CA_=BC=EE=C7=CE=B8=F4_REFILL=2ECO=2EKR__@?=
From: "=?ks_c_5601-1987?Q?REFILL=2ECO=2EKR?=" <sender@refill.co.kr>
Date: Sat, 15 Mar 2003 06:54:53 +0900
To: "=?ks_c_5601-1987?Q?freebsd-hackers@freebsd=2Eorg?=" <freebsd-hackers@freebsd.org>
X-Priority: 3
X-MSMail-Priority: Normal
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailer: JMail 4.3.1 by Dimac
Content-Type: text/html
X-Antirelay: Good relay from local net1 211.235.237.1/26      'Kiologic
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

DQo8aHRtbD4NCjxoZWFkPg0KPHRpdGxlPrTrx9G5zrG5ILTrx6UguK7Hyrvn
wMzGriA6Ojo6Ojo6Ojo6IFJlZmlsbC5jby5rcjwvdGl0bGU+DQo8bWV0YSBo
dHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9InRleHQvaHRtbDsg
Y2hhcnNldD1ldWMta3IiPg0KPHN0eWxlIHR5cGU9InRleHQvY3NzIj4NCjwh
LS0NCi5ub21fdHh0IHsgIGZvbnQtZmFtaWx5OiAitbi/8iI7IGZvbnQtc2l6
ZTogMTJweDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgY29sb3I6ICNBNUE1QTV9
DQotLT4NCjwvc3R5bGU+DQo8L2hlYWQ+DQoNCjxib2R5IGJnY29sb3I9IiNG
RkZGRkYiIGxlZnRtYXJnaW49IjAiIHRvcG1hcmdpbj0iMCIgbWFyZ2lud2lk
dGg9IjAiIG1hcmdpbmhlaWdodD0iMCI+DQo8YnI+DQo8dGFibGUgd2lkdGg9
IjYwMCIgYm9yZGVyPSIwIiBjZWxsc3BhY2luZz0iMCIgY2VsbHBhZGRpbmc9
IjAiIGFsaWduPSJjZW50ZXIiPg0KPHRyPg0KPHRkIHdpZHRoPSIxIiBiZ2Nv
bG9yPSIjQzZDNkM2Ij48aW1nIHNyYz0iaHR0cDovL3d3dy5yZWZpbGwuY28u
a3IvbWFpbC9uZXdzbGV0dGVyL2ltYWdlcy9ibGFuay5naWYiPjwvdGQ+DQo8
dGQgd2lkdGg9IjU5OCI+DQo8dGFibGUgd2lkdGg9IjU5OCIgYm9yZGVyPSIw
IiBjZWxsc3BhY2luZz0iMCIgY2VsbHBhZGRpbmc9IjAiPg0KPHRyPg0KPHRk
IGNvbHNwYW49IjIiPjxpbWcgc3JjPSJodHRwOi8vd3d3LnJlZmlsbC5jby5r
ci9tYWlsL25ld3NsZXR0ZXIvaW1hZ2VzL2Jhcl90b3AuZ2lmIiB3aWR0aD0i
NTk4IiBoZWlnaHQ9IjIxIj48L3RkPg0KPC90cj4NCjx0cj4NCjx0ZD48YSBo
cmVmPSJodHRwOi8vd3d3LnJlZmlsbC5jby5rci9pbmRleC5hc3AiIHRhcmdl
dD0iX2JsYW5rIj48aW1nIHNyYz0iaHR0cDovL3d3dy5yZWZpbGwuY28ua3Iv
bWFpbC9uZXdzbGV0dGVyL2ltYWdlcy9sb2dvLmdpZiIgd2lkdGg9IjE3MiIg
aGVpZ2h0PSI1NiIgYm9yZGVyPSIwIj48L2E+PC90ZD4NCjx0ZD48YSBocmVm
PSJodHRwOi8vd3d3LnJlZmlsbC5jby5rci9odG1sL1Byb1RvbmVyTGlzdC5h
c3A/aW1nY2hrPTIiIHRhcmdldD0iX2JsYW5rIj48aW1nIHNyYz0iaHR0cDov
L3d3dy5yZWZpbGwuY28ua3IvbWFpbC9uZXdzbGV0dGVyL2ltYWdlcy9iX3No
b3BwaW5nLmdpZiIgd2lkdGg9IjEzOSIgaGVpZ2h0PSI1NiIgYWxpZ249InJp
Z2h0IiBib3JkZXI9IjAiPjwvYT48L3RkPg0KPC90cj4NCjx0cj4NCjx0ZCBj
b2xzcGFuPSIyIj48aW1nIHNyYz0iaHR0cDovL3d3dy5yZWZpbGwuY28ua3Iv
bWFpbC9uZXdzbGV0dGVyL2ltYWdlcy9iYW5fbWFpbi5qcGciIHdpZHRoPSI1
OTgiIGhlaWdodD0iMTk1Ij48YnI+DQo8aW1nIHNyYz0iaHR0cDovL3d3dy5y
ZWZpbGwuY28ua3IvbWFpbC9uZXdzbGV0dGVyL2ltYWdlcy9leHAuZ2lmIiB3
aWR0aD0iNTk4IiBoZWlnaHQ9IjQ5Ij48L3RkPg0KPC90cj4NCjx0ciBhbGln
bj0iY2VudGVyIj4NCjx0ZCBjb2xzcGFuPSIyIj4NCjx0YWJsZSB3aWR0aD01
MjQgYm9yZGVyPTAgY2VsbHBhZGRpbmc9MCBjZWxsc3BhY2luZz0wPg0KPHRy
Pg0KPHRkPjxhIGhyZWY9Imh0dHA6Ly93d3cucmVmaWxsLmNvLmtyL2h0bWwv
UHJvVG9uZXJMaXN0LmFzcD9pbWdjaGs9MiIgdGFyZ2V0PSJfYmxhbmsiPjxp
bWcgc3JjPSJodHRwOi8vd3d3LnJlZmlsbC5jby5rci9tYWlsL25ld3NsZXR0
ZXIvaW1hZ2VzL2JyYW5kXzAxLmdpZiIgd2lkdGg9MTAxIGhlaWdodD01NiBh
bHQ9IiIgYm9yZGVyPSIwIj48L2E+PC90ZD4NCjx0ZD48YSBocmVmPSJodHRw
Oi8vd3d3LnJlZmlsbC5jby5rci9odG1sL1Byb1RvbmVyTGlzdC5hc3A/aW1n
Y2hrPTImYW1wO0NhdGVnb3J5PVQmYW1wO1NlbGVjdENvbXBhbnk9JUJCJUVG
JUJDJUJBIiB0YXJnZXQ9Il9ibGFuayI+PGltZyBzcmM9Imh0dHA6Ly93d3cu
cmVmaWxsLmNvLmtyL21haWwvbmV3c2xldHRlci9pbWFnZXMvYnJhbmRfMDIu
Z2lmIiB3aWR0aD0xMDkgaGVpZ2h0PTU2IGFsdD0iIiBib3JkZXI9IjAiPjwv
YT48L3RkPg0KPHRkPjxhIGhyZWY9Imh0dHA6Ly93d3cucmVmaWxsLmNvLmty
L2h0bWwvUHJvVG9uZXJMaXN0LmFzcD9pbWdjaGs9MiZhbXA7Q2F0ZWdvcnk9
VCZhbXA7U2VsZWN0Q29tcGFueT0lQzUlQTUlQjQlRDAlQkQlQkEiIHRhcmdl
dD0iX2JsYW5rIj48aW1nIHNyYz0iaHR0cDovL3d3dy5yZWZpbGwuY28ua3Iv
bWFpbC9uZXdzbGV0dGVyL2ltYWdlcy9icmFuZF8wMy5naWYiIHdpZHRoPTEx
NiBoZWlnaHQ9NTYgYWx0PSIiIGJvcmRlcj0iMCI+PC9hPjwvdGQ+DQo8dGQ+
PGEgaHJlZj0iaHR0cDovL3d3dy5yZWZpbGwuY28ua3IvaHRtbC9Qcm9Ub25l
ckxpc3QuYXNwP2ltZ2Noaz0yJmFtcDtDYXRlZ29yeT1UJmFtcDtTZWxlY3RD
b21wYW55PSVCRCVDNSVCNSVCNSVCOCVBRSVDNCVEQSIgdGFyZ2V0PSJfYmxh
bmsiPjxpbWcgc3JjPSJodHRwOi8vd3d3LnJlZmlsbC5jby5rci9tYWlsL25l
d3NsZXR0ZXIvaW1hZ2VzL2JyYW5kXzA0LmdpZiIgd2lkdGg9OTkgaGVpZ2h0
PTU2IGFsdD0iIiBib3JkZXI9IjAiPjwvYT48L3RkPg0KPHRkPjxhIGhyZWY9
Imh0dHA6Ly93d3cucmVmaWxsLmNvLmtyL2h0bWwvUHJvVG9uZXJMaXN0LmFz
cD9pbWdjaGs9MiZhbXA7Q2F0ZWdvcnk9VCZhbXA7U2VsZWN0Q29tcGFueT1F
UFNPTi8lQkIlRUYlQkElQjgiIHRhcmdldD0iX2JsYW5rIj48aW1nIHNyYz0i
aHR0cDovL3d3dy5yZWZpbGwuY28ua3IvbWFpbC9uZXdzbGV0dGVyL2ltYWdl
cy9icmFuZF8wNS5naWYiIHdpZHRoPTk5IGhlaWdodD01NiBhbHQ9IiIgYm9y
ZGVyPSIwIj48L2E+PC90ZD4NCjwvdHI+DQo8dHI+DQo8dGQ+PGEgaHJlZj0i
aHR0cDovL3d3dy5yZWZpbGwuY28ua3IvaHRtbC9Qcm9Ub25lckxpc3QuYXNw
P2ltZ2Noaz0yJmFtcDtDYXRlZ29yeT1UJmFtcDtTZWxlY3RDb21wYW55PSVD
MSVBNiVCNyVDRiVCRCVCQSIgdGFyZ2V0PSJfYmxhbmsiPjxpbWcgc3JjPSJo
dHRwOi8vd3d3LnJlZmlsbC5jby5rci9tYWlsL25ld3NsZXR0ZXIvaW1hZ2Vz
L2JyYW5kXzA2LmdpZiIgd2lkdGg9MTAxIGhlaWdodD00MCBhbHQ9IiIgYm9y
ZGVyPSIwIj48L2E+PC90ZD4NCjx0ZD48YSBocmVmPSJodHRwOi8vd3d3LnJl
ZmlsbC5jby5rci9odG1sL1Byb1RvbmVyTGlzdC5hc3A/aW1nY2hrPTImYW1w
O0NhdGVnb3J5PVQmYW1wO1NlbGVjdENvbXBhbnk9TEciIHRhcmdldD0iX2Js
YW5rIj48aW1nIHNyYz0iaHR0cDovL3d3dy5yZWZpbGwuY28ua3IvbWFpbC9u
ZXdzbGV0dGVyL2ltYWdlcy9icmFuZF8wNy5naWYiIHdpZHRoPTEwOSBoZWln
aHQ9NDAgYWx0PSIiIGJvcmRlcj0iMCI+PC9hPjwvdGQ+DQo8dGQ+PGEgaHJl
Zj0iaHR0cDovL3d3dy5yZWZpbGwuY28ua3IvaHRtbC9Qcm9Ub25lckxpc3Qu
YXNwP2ltZ2Noaz0yJmFtcDtDYXRlZ29yeT1UJmFtcDtTZWxlY3RDb21wYW55
PSVDNCVCMyVCMyVFRCIgdGFyZ2V0PSJfYmxhbmsiPjxpbWcgc3JjPSJodHRw
Oi8vd3d3LnJlZmlsbC5jby5rci9tYWlsL25ld3NsZXR0ZXIvaW1hZ2VzL2Jy
YW5kXzA4LmdpZiIgd2lkdGg9MTE2IGhlaWdodD00MCBhbHQ9IiIgYm9yZGVy
PSIwIj48L2E+PC90ZD4NCjx0ZD48YSBocmVmPSJodHRwOi8vd3d3LnJlZmls
bC5jby5rci9odG1sL1Byb1RvbmVyTGlzdC5hc3A/aW1nY2hrPTImYW1wO0Nh
dGVnb3J5PVQmYW1wO1NlbGVjdENvbXBhbnk9JUMxJUE2JUMwJUNGJUMxJUE0
JUI5JUQwIiB0YXJnZXQ9Il9ibGFuayI+PGltZyBzcmM9Imh0dHA6Ly93d3cu
cmVmaWxsLmNvLmtyL21haWwvbmV3c2xldHRlci9pbWFnZXMvYnJhbmRfMDku
Z2lmIiB3aWR0aD05OSBoZWlnaHQ9NDAgYWx0PSIiIGJvcmRlcj0iMCI+PC9h
PjwvdGQ+DQo8dGQ+PGEgaHJlZj0iaHR0cDovL3d3dy5yZWZpbGwuY28ua3Iv
aHRtbC9Qcm9Ub25lckxpc3QuYXNwP2ltZ2Noaz0yJmFtcDtDYXRlZ29yeT1U
JmFtcDtTZWxlY3RDb21wYW55PSVCMSVFMiVDNSVCOCIgdGFyZ2V0PSJfYmxh
bmsiPjxpbWcgc3JjPSJodHRwOi8vd3d3LnJlZmlsbC5jby5rci9tYWlsL25l
d3NsZXR0ZXIvaW1hZ2VzL2JyYW5kXzEwLmdpZiIgd2lkdGg9OTkgaGVpZ2h0
PTQwIGFsdD0iIiBib3JkZXI9IjAiPjwvYT48L3RkPg0KPC90cj4NCjwvdGFi
bGU+DQo8L3RkPg0KPC90cj4NCjx0cj4NCjx0ZCBjb2xzcGFuPSIyIj48aW1n
IHNyYz0iaHR0cDovL3d3dy5yZWZpbGwuY28ua3IvbWFpbC9uZXdzbGV0dGVy
L2ltYWdlcy9iYXJfZG90LmdpZiIgd2lkdGg9IjU5OCIgaGVpZ2h0PSIxNyI+
PC90ZD4NCjwvdHI+DQo8dHIgYWxpZ249ImNlbnRlciI+DQo8dGQgY29sc3Bh
bj0iMiI+DQo8dGFibGUgd2lkdGg9IjU3MiIgYm9yZGVyPSIwIiBjZWxsc3Bh
Y2luZz0iMCIgY2VsbHBhZGRpbmc9IjAiIGhlaWdodD0iOTAiPg0KPHRyPg0K
PHRkPjxhIGhyZWY9Imh0dHA6Ly93d3cucmVmaWxsLmNvLmtyL2h0bWwvcHJv
bWlzZS5hc3AiIHRhcmdldD0iX2JsYW5rIj48aW1nIHNyYz0iaHR0cDovL3d3
dy5yZWZpbGwuY28ua3IvbWFpbC9uZXdzbGV0dGVyL2ltYWdlcy9iYW5fc3Vi
MDEuZ2lmIiB3aWR0aD0iMTkxIiBoZWlnaHQ9Ijc1IiBib3JkZXI9IjAiPjwv
YT48L3RkPg0KPHRkPjxhIGhyZWY9Imh0dHA6Ly93d3cucmVmaWxsLmNvLmty
L2h0bWwvcG9wdXBfcmVjeWNsZS5odG0iIHRhcmdldD0iX2JsYW5rIj48aW1n
IHNyYz0iaHR0cDovL3d3dy5yZWZpbGwuY28ua3IvbWFpbC9uZXdzbGV0dGVy
L2ltYWdlcy9iYW5fc3ViMDIuZ2lmIiB3aWR0aD0iMTkwIiBoZWlnaHQ9Ijc1
IiBib3JkZXI9IjAiPjwvYT48L3RkPg0KPHRkPjxpbWcgc3JjPSJodHRwOi8v
d3d3LnJlZmlsbC5jby5rci9tYWlsL25ld3NsZXR0ZXIvaW1hZ2VzL2Jhbl9z
dWIwMy5naWYiIHdpZHRoPSIxOTEiIGhlaWdodD0iNzUiPjwvdGQ+DQo8L3Ry
Pg0KPC90YWJsZT4NCjwvdGQ+DQo8L3RyPg0KPHRyPg0KPHRkIGNvbHNwYW49
IjIiPjxpbWcgc3JjPSJodHRwOi8vd3d3LnJlZmlsbC5jby5rci9tYWlsL25l
d3NsZXR0ZXIvaW1hZ2VzL2Jhcl9kb3QuZ2lmIiB3aWR0aD0iNTk4IiBoZWln
aHQ9IjE3Ij48L3RkPg0KPC90cj4NCjx0cj4NCjx0ZCBjb2xzcGFuPSIyIj48
aW1nIHNyYz0iaHR0cDovL3d3dy5yZWZpbGwuY28ua3IvbWFpbC9uZXdzbGV0
dGVyL2ltYWdlcy90X2NhcnRvb24uZ2lmIiB3aWR0aD0iMTYzIiBoZWlnaHQ9
IjIxIj48L3RkPg0KPC90cj4NCjx0ciBhbGlnbj0iY2VudGVyIj4NCjx0ZCBj
b2xzcGFuPSIyIj4NCjx0YWJsZSB3aWR0aD01MTggYm9yZGVyPTAgY2VsbHBh
ZGRpbmc9MCBjZWxsc3BhY2luZz0wPg0KPHRyPg0KPHRkPjxpbWcgc3JjPSJo
dHRwOi8vd3d3LnJlZmlsbC5jby5rci9tYWlsL25ld3NsZXR0ZXIvaW1hZ2Vz
L2NhcnRvb25fMDEuZ2lmIiB3aWR0aD0yNzUgaGVpZ2h0PTIxNiBhbHQ9IiI+
PC90ZD4NCjx0ZD48aW1nIHNyYz0iaHR0cDovL3d3dy5yZWZpbGwuY28ua3Iv
bWFpbC9uZXdzbGV0dGVyL2ltYWdlcy9jYXJ0b29uXzAyLmdpZiIgd2lkdGg9
MjQzIGhlaWdodD0yMTYgYWx0PSIiPjwvdGQ+DQo8L3RyPg0KPHRyPg0KPHRk
PjxpbWcgc3JjPSJodHRwOi8vd3d3LnJlZmlsbC5jby5rci9tYWlsL25ld3Ns
ZXR0ZXIvaW1hZ2VzL2NhcnRvb25fMDMuZ2lmIiB3aWR0aD0yNzUgaGVpZ2h0
PTIxMiBhbHQ9IiI+PC90ZD4NCjx0ZD48aW1nIHNyYz0iaHR0cDovL3d3dy5y
ZWZpbGwuY28ua3IvbWFpbC9uZXdzbGV0dGVyL2ltYWdlcy9jYXJ0b29uXzA0
LmdpZiIgd2lkdGg9MjQzIGhlaWdodD0yMTIgYWx0PSIiPjwvdGQ+DQo8L3Ry
Pg0KPHRyPg0KPHRkPjxpbWcgc3JjPSJodHRwOi8vd3d3LnJlZmlsbC5jby5r
ci9tYWlsL25ld3NsZXR0ZXIvaW1hZ2VzL2NhcnRvb25fMDUuZ2lmIiB3aWR0
aD0yNzUgaGVpZ2h0PTE5MSBhbHQ9IiI+PC90ZD4NCjx0ZD48aW1nIHNyYz0i
aHR0cDovL3d3dy5yZWZpbGwuY28ua3IvbWFpbC9uZXdzbGV0dGVyL2ltYWdl
cy9jYXJ0b29uXzA2LmdpZiIgd2lkdGg9MjQzIGhlaWdodD0xOTEgYWx0PSIi
PjwvdGQ+DQo8L3RyPg0KPHRyPg0KPHRkPjxpbWcgc3JjPSJodHRwOi8vd3d3
LnJlZmlsbC5jby5rci9tYWlsL25ld3NsZXR0ZXIvaW1hZ2VzL2NhcnRvb25f
MDcuZ2lmIiB3aWR0aD0yNzUgaGVpZ2h0PTE4NiBhbHQ9IiI+PC90ZD4NCjx0
ZD48aW1nIHNyYz0iaHR0cDovL3d3dy5yZWZpbGwuY28ua3IvbWFpbC9uZXdz
bGV0dGVyL2ltYWdlcy9jYXJ0b29uXzA4LmdpZiIgd2lkdGg9MjQzIGhlaWdo
dD0xODYgYWx0PSIiPjwvdGQ+DQo8L3RyPg0KPC90YWJsZT4NCjwvdGQ+DQo8
L3RyPg0KPHRyPg0KPHRkIGNvbHNwYW49IjIiPjxpbWcgc3JjPSJodHRwOi8v
d3d3LnJlZmlsbC5jby5rci9tYWlsL25ld3NsZXR0ZXIvaW1hZ2VzL2Jhcl9k
b3QuZ2lmIiB3aWR0aD0iNTk4IiBoZWlnaHQ9IjE3Ij48L3RkPg0KPC90cj4N
Cjx0ciBhbGlnbj0iY2VudGVyIj4NCjx0ZCBjb2xzcGFuPSIyIj4NCjx0YWJs
ZSB3aWR0aD0iNTc4IiBib3JkZXI9IjAiIGNlbGxzcGFjaW5nPSIwIiBjZWxs
cGFkZGluZz0iMTAiPg0KPHRyPg0KPHRkIHdpZHRoPSI0NzQiIHZhbGlnbj0i
dG9wIiBjbGFzcz0ibm9tX3R4dCI+waS6uMXrvcW6ziCxx7DtILvnx9cguf23
/CDBpg0KNTDBtr+hIMDHsMXHz7+pIMGmuPG/oSAosaSw7Sm287DtIMelseLH
0SCxpLDtuN7Az8DMuOcsILHNx8/AxyC43sDPwda80rTCIMClILytx87B3yC+
y7DUILXIILDNwMy45ywgZU1haWwNCsHWvNIgv9y/oSCxzcfPwMcgvu62sMfR
IMGkuri1tSCwocH2sO0gwNbB9iC+ysC4tM8gvsi9ycfPvcOx5iC52bb4tM+0
2S4gursguN7Az8C6ILnfvNvA/L/rILjewM/A08C4t84sIL/4xKENCr7KwLi9
w7jpIFu89r3FsMW6zl0gufbGsMC7IENsaWNrIMfYIMHWvLy/5C48YnI+PGJy
Pg0KSWYgeW91IHdvdWxkIGxpa2UgdG8gYmUgcmVtb3ZlZCBmcm9tIGFueSBv
ZiBvdXIgZGlzdHJpYnV0aW9uIGxpc3RzLCBwbGVhc2UgY2xpY2sgJ1JFRlVT
RScuIEl0IHdpbGwgYmUgaGFuZGxlZCBwcm9tcHRseS4gVGhhbmsgeW91LiA8
YSBocmVmPSJodHRwOi8vd3d3LnJlZmlsbC5jby5rci9tYWlsL25ld3NsZXR0
ZXIvMDMwMnJlamVjdC5hc3A/TWFpbE51bT1mcmVlYnNkLWhhY2tlcnNAZnJl
ZWJzZC5vcmciIHRhcmdldD0iX2JsYW5rIj5bUkVGVVNFXTwvYT4NCjwvdGQ+
DQo8dGQgd2lkdGg9IjY0IiBhbGlnbj0iY2VudGVyIj48YSBocmVmPSJodHRw
Oi8vd3d3LnJlZmlsbC5jby5rci9tYWlsL25ld3NsZXR0ZXIvMDMwMnJlamVj
dC5hc3A/TWFpbE51bT1mcmVlYnNkLWhhY2tlcnNAZnJlZWJzZC5vcmciIHRh
cmdldD0iX2JsYW5rIj48aW1nIHNyYz0iaHR0cDovL3d3dy5yZWZpbGwuY28u
a3IvbWFpbC9uZXdzbGV0dGVyL2ltYWdlcy9iX25vbWFpbC5naWYiIHdpZHRo
PSI2MCIgaGVpZ2h0PSI2MCIgYm9yZGVyPSIwIj48L2E+PC90ZD4NCjwvdHI+
DQo8L3RhYmxlPg0KPC90ZD4NCjwvdHI+DQo8dHI+DQo8dGQgY29sc3Bhbj0i
MiI+PGltZyBzcmM9Imh0dHA6Ly93d3cucmVmaWxsLmNvLmtyL21haWwvbmV3
c2xldHRlci9pbWFnZXMvYmFyX2RvdC5naWYiIHdpZHRoPSI1OTgiIGhlaWdo
dD0iMTciPjwvdGQ+DQo8L3RyPg0KPHRyIGFsaWduPSJjZW50ZXIiPg0KPHRk
IGNvbHNwYW49IjIiPg0KPHRhYmxlIHdpZHRoPSI1NzgiIGJvcmRlcj0iMCIg
Y2VsbHNwYWNpbmc9IjAiIGNlbGxwYWRkaW5nPSIxMCI+DQo8dHI+DQo8dGQg
d2lkdGg9IjIyNyIgdmFsaWduPSJ0b3AiIGNsYXNzPSJub21fdHh0Ij48Yj6h
2CCw7bC0ILytuvG9uiC5rsDHIDogMDItMzI4MS03Nzc3IDwvYj48L3RkPg0K
PHRkIHdpZHRoPSIzMTEiIGFsaWduPSJyaWdodCIgY2xhc3M9Im5vbV90eHQi
PkNvcHlyaWdodCAxOTkxLTIwMDIuIEZ1dGVjaCBjbywuTHRkLiBBbGwgcmln
aHQgcmVzZXJ2ZWQuPC90ZD4NCjwvdHI+DQo8L3RhYmxlPg0KPC90ZD4NCjwv
dHI+DQo8dHI+PHRkIGNvbHNwYW49IjIiIGhlaWdodD0iMSIgYmdjb2xvcj0i
I0M2QzZDNiI+PGltZyBzcmM9Imh0dHA6Ly93d3cucmVmaWxsLmNvLmtyL21h
aWwvbmV3c2xldHRlci9pbWFnZXMvYmxhbmsuZ2lmIj48L3RkPjwvdHI+DQo8
L3RhYmxlPg0KPC90ZD4NCjx0ZCB3aWR0aD0iMSIgYmdjb2xvcj0iI0M2QzZD
NiI+PGltZyBzcmM9Imh0dHA6Ly93d3cucmVmaWxsLmNvLmtyL21haWwvbmV3
c2xldHRlci9pbWFnZXMvYmxhbmsuZ2lmIj48L3RkPg0KPC90cj4NCjwvdGFi
bGU+DQo8YnI+DQo8L2JvZHk+DQo8L2h0bWw+DQo=



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


From owner-freebsd-hackers  Sat Mar 15  6:48:14 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9DEB037B404
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 15 Mar 2003 06:48:13 -0800 (PST)
Received: from casselton.net (casselton.net [63.165.140.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2DDC343FBF
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 15 Mar 2003 06:48:08 -0800 (PST)
	(envelope-from tinguely@casselton.net)
Received: from casselton.net (localhost [127.0.0.1])
	by casselton.net (8.12.6/8.12.6) with ESMTP id h2FEm5jx089696;
	Sat, 15 Mar 2003 08:48:05 -0600 (CST)
	(envelope-from tinguely@casselton.net)
Received: (from tinguely@localhost)
	by casselton.net (8.12.6/8.12.6/Submit) id h2FEm4Mt089695;
	Sat, 15 Mar 2003 08:48:04 -0600 (CST)
Date: Sat, 15 Mar 2003 08:48:04 -0600 (CST)
From: Mark Tinguely <tinguely@casselton.net>
Message-Id: <200303151448.h2FEm4Mt089695@casselton.net>
To: andykinney@advantagecom.net
Subject: Re: increasing KVA_PAGES and broken pthreads
Cc: freebsd-hackers@FreeBSD.ORG
In-Reply-To: <Pine.BSF.4.21.0303141709400.44309-100000@InterJet.elischer.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


Intel x86 hardware allows windows of 4GB of virtual memory even if
you have the PSE-36 and the PAE extensions with more the 4GB of
physical memory. Sound a little like Intel's 64KB windows, but
if I remember correctly, the 4GB does not have to be contiguous.

It would require a true MMU such as those in the 64 bit architectures
(AMD opteron, Intel ia64, sparc64) to simulataneously be able to use
more than 4GB of RAM.

So far the thought it is better to go with a true 64 MMU than take
and get a flat address space than take the performance hit (, plus
the memory loss for the much larger page table without much benefit)
than try to shuffle in the 4GB windows. Check the thread on this topic
in the archives.

--Mark Tinguely.

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


From owner-freebsd-hackers  Sat Mar 15  9:14:30 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EDF6737B401
	for <freebsd-hackers@freebsd.org>; Sat, 15 Mar 2003 09:14:29 -0800 (PST)
Received: from guava.silverwraith.com (66-214-182-79.la-cbi.charterpipeline.net [66.214.182.79])
	by mx1.FreeBSD.org (Postfix) with SMTP id 2819143FAF
	for <freebsd-hackers@freebsd.org>; Sat, 15 Mar 2003 09:14:29 -0800 (PST)
	(envelope-from avleen@guava.silverwraith.com)
Received: (qmail 63388 invoked by uid 1001); 15 Mar 2003 17:14:28 -0000
Date: Sat, 15 Mar 2003 09:14:28 -0800
From: Avleen Vig <lists-freebsd@silverwraith.com>
To: freebsd-hackers@freebsd.org
Subject: make world + kernel with gcc 3.2?
Message-ID: <20030315171428.GL35096@silverwraith.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.3i
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Well, I installed 4.7-RELEASE a few months ago, and soon after installed
GCC3.2.
Since then, everything has worked fine, but I want to upgrade to -STABLE
or at least 4.8-RELEASE when it comes out.

I don't expect HUGE problems with making world, but am I asking for
trouble if I make a new kernel with GCC3.2?

I've tried searching archives but can only find old, vague references.
Hopefully someone here has experience.

-- 
Avleen Vig                   "Say no to cheese-eating surrender-monkeys"
Systems Admin                "Fast, Good, Cheap. Pick any two."
www.silverwraith.com         "Move BSD. For great justice!"

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


From owner-freebsd-hackers  Sat Mar 15 10: 3:13 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B330337B401
	for <freebsd-hackers@freebsd.org>; Sat, 15 Mar 2003 10:03:12 -0800 (PST)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8BAFC43F93
	for <freebsd-hackers@freebsd.org>; Sat, 15 Mar 2003 10:03:11 -0800 (PST)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.8/8.12.3) with ESMTP id h2FI2qA7007626;
	Sat, 15 Mar 2003 11:02:55 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Sat, 15 Mar 2003 11:02:42 -0700 (MST)
Message-Id: <20030315.110242.96686701.imp@bsdimp.com>
To: keramida@ceid.upatras.gr
Cc: freebsd-hackers@freebsd.org
Subject: Re: style of sysctl description strings
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20030314194119.GA5226@gothmog.gr>
References: <20030314194119.GA5226@gothmog.gr>
X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

In message: <20030314194119.GA5226@gothmog.gr>
            Giorgos Keramidas <keramida@ceid.upatras.gr> writes:
: Is there a reason for wrapping with '\n'?  If yes, what would that be?
: I'm only asking because it would make my life simpler if the sysctl
: descriptions didn't have embedded newlines, and this is a good
: opportunity to learn something too :-)

Habit.  There's a bunch of these with OLDCARD.  They all should be <
80 characters, however.

Warner

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


From owner-freebsd-hackers  Sat Mar 15 10: 8:52 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 460B237B401
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 15 Mar 2003 10:08:51 -0800 (PST)
Received: from herbelot.dyndns.org (herbelot.net1.nerim.net [62.212.117.213])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C765E43FA3
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 15 Mar 2003 10:08:49 -0800 (PST)
	(envelope-from thierry@herbelot.com)
Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6])
	by herbelot.dyndns.org (8.12.6/8.12.6) with ESMTP id h2FHuF0f019412;
	Sat, 15 Mar 2003 18:56:15 +0100 (CET)
From: Thierry Herbelot <thierry@herbelot.com>
To: Avleen Vig <lists-freebsd@silverwraith.com>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: make world + kernel with gcc 3.2?
Date: Sat, 15 Mar 2003 19:08:40 +0100
User-Agent: KMail/1.5
References: <20030315171428.GL35096@silverwraith.com>
In-Reply-To: <20030315171428.GL35096@silverwraith.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Message-Id: <200303151908.40852.thierry@herbelot.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Le Saturday 15 March 2003 18:14, Avleen Vig a écrit :
> I don't expect HUGE problems with making world, but am I asking for
> trouble if I make a new kernel with GCC3.2?

good luck to you !

just have a look at the differences in the source code between current and 
stable to enable the compilation of current with gcc3 (FriBi -Stable will not 
compile with anything other than gcc 2.95)

	TfH

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


From owner-freebsd-hackers  Sat Mar 15 11:58:57 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7A9AA37B401
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 15 Mar 2003 11:58:56 -0800 (PST)
Received: from mta05-svc.ntlworld.com (mta05-svc.ntlworld.com [62.253.162.45])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 398A843F93
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 15 Mar 2003 11:58:55 -0800 (PST)
	(envelope-from scott@fishballoon.org)
Received: from fishballoon.org ([81.104.195.199]) by mta05-svc.ntlworld.com
          (InterMail vM.4.01.03.37 201-229-121-137-20020806) with ESMTP
          id <20030315195853.QHRS310.mta05-svc.ntlworld.com@fishballoon.org>;
          Sat, 15 Mar 2003 19:58:53 +0000
Received: from tuatara.fishballoon.org (tuatara [192.168.1.6])
	by fishballoon.org (8.12.6/8.12.6) with ESMTP id h2FJwE9A043805;
	Sat, 15 Mar 2003 19:58:14 GMT
	(envelope-from scott@tuatara.fishballoon.org)
Received: (from scott@localhost)
	by tuatara.fishballoon.org (8.12.7/8.12.6/Submit) id h2FJwDQM004603;
	Sat, 15 Mar 2003 19:58:13 GMT
	(envelope-from scott)
Date: Sat, 15 Mar 2003 19:58:13 +0000
From: Scott Mitchell <scott+freebsd@fishballoon.org>
To: Thierry Herbelot <thierry@herbelot.com>
Cc: Avleen Vig <lists-freebsd@silverwraith.com>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: make world + kernel with gcc 3.2?
Message-ID: <20030315195813.GA4214@tuatara.fishballoon.org>
References: <20030315171428.GL35096@silverwraith.com> <200303151908.40852.thierry@herbelot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200303151908.40852.thierry@herbelot.com>
User-Agent: Mutt/1.4i
X-Operating-System: FreeBSD 4.8-PRERELEASE i386
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Sat, Mar 15, 2003 at 07:08:40PM +0100, Thierry Herbelot wrote:
> Le Saturday 15 March 2003 18:14, Avleen Vig a écrit :
> > I don't expect HUGE problems with making world, but am I asking for
> > trouble if I make a new kernel with GCC3.2?
> 
> good luck to you !
> 
> just have a look at the differences in the source code between current
> and stable to enable the compilation of current with gcc3 (FriBi -Stable
> will not compile with anything other than gcc 2.95)
> 
> 	TfH

I assume the OP installed gcc3 from ports...in this case the gcc2.95 system
compiler will still be installed as well.  I'm pretty sure that a kernel
build will explicitly use the system compiler, and buildworld/buildkernel
certainly do (I believe buildworld actually builds a fresh copy of gcc2.95
then uses that to build the rest of the system).

As Thierry says, trying to build -stable with gcc3 is probably doomed to
failure.

	Scott

-- 
===========================================================================
Scott Mitchell           | PGP Key ID | "Eagles may soar, but weasels
Cambridge, England       | 0x54B171B9 |  don't get sucked into jet engines"
scott at fishballoon.org | 0xAA775B8B |      -- Anon

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


From owner-freebsd-hackers  Sat Mar 15 12:52:22 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 69FA037B404
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 15 Mar 2003 12:52:21 -0800 (PST)
Received: from mailscan.binghamton.edu (mailscan.binghamton.edu [128.226.8.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 2204043FAF
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 15 Mar 2003 12:52:20 -0800 (PST)
	(envelope-from bf20761@binghamton.edu)
Received: from bingnet2.cc.binghamton.edu(128.226.1.18) by mailscan.binghamton.edu via csmap 
	 id 9685; Sat, 15 Mar 2003 13:16:58 -0500 (EST)
Received: from bingsun2.cc.binghamton.edu (bf20761@bingsun2.cc.binghamton.edu [128.226.6.4])
	by bingnet2.cc.binghamton.edu (8.12.8/8.12.8) with ESMTP id h2FICt0J026781
	for <freebsd-hackers@FreeBSD.ORG>; Sat, 15 Mar 2003 13:12:55 -0500 (EST)
Date: Sat, 15 Mar 2003 13:12:55 -0500 (EST)
From: Zhihui Zhang <bf20761@binghamton.edu>
X-X-Sender: bf20761@bingsun2.cc.binghamton.edu
To: freebsd-hackers@FreeBSD.ORG
Subject: high resolution kernel profiling
Message-ID: <Pine.SOL.L4.44.0303151304530.24275-100000@bingsun2.cc.binghamton.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


I try to use high resolution kernel profiling today on FreeBSD 4.6
release. I use config -p -p MYKERNEL and later kgmon -Br to start the
profiling.  However, the file generate by gprof contains many negative
numbers such as -0.00, -0.02 under the columns of self and descendents.
Why is the case? Does it mean we should not use high resolution profiling
at all?

Thanks for any enlightment.

-Zhihui

-- 



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


From owner-freebsd-hackers  Sat Mar 15 18:10: 5 2003
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1751D37B401
	for <hackers@freebsd.org>; Sat, 15 Mar 2003 18:10:03 -0800 (PST)
Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 59A5043FB1
	for <hackers@freebsd.org>; Sat, 15 Mar 2003 18:10:02 -0800 (PST)
	(envelope-from babkin@bellatlantic.net)
Received: from bellatlantic.net ([138.89.161.103]) by out001.verizon.net
          (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP
          id <20030316021001.RERE5518.out001.verizon.net@bellatlantic.net>
          for <hackers@freebsd.org>; Sat, 15 Mar 2003 20:10:01 -0600
Message-ID: <3E73DCF7.80490FA6@bellatlantic.net>
Date: Sat, 15 Mar 2003 21:09:59 -0500
From: Sergey Babkin <babkin@bellatlantic.net>
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.7-RELEASE i386)
X-Accept-Language: en, ru
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: making CVS more convenient
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [138.89.161.103] at Sat, 15 Mar 2003 20:10:00 -0600
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

Hi all,

I've been planning to send this message to the developers mailing
list, but it has mysteriously disappeared (and I haven't found
yet its replacement). So here it goes.

The idea is to support a "cache" repository (the one copied to a local machine
by CVSup or CTM) transparently. So that the reads from directory will go
from the local cache repository (and won't overstrain the remote server,
and will be fast too), while the commits and other changes will go into
the remote master repository.

A similar thing may be achieved by checking the files out from the local
repository and doing any modification command with option -d. But that's
troublesome and inconvenient.

This patch allows to deine the following configuration:

# so far everything is as usual
export CVS_RSH=Hssh1
export CVSROOT=user@ncvs.freebsd.org:/home/ncvs
# this is new
export CVSROOTCACHE=/arch/cacheroot

The value specified in CVSROOTCACHE is the local path to the cache
repository. All the check-outs, updates, diffs etc. will be obtained 
from there.  All the check-ins, tagging etc. will go into the master 
repository specified by CVSROOT. Naturally, to see these changes
in the cache repository, it needs to be updated by some outside
means such as CVSup or CTM.

BTW, if there is no chance of conflict between updating the cache
directories and check-outs from it, running check-outs with
"cvs -r" (read-only repository) will make it faster.

The patch (and the same description) are available from
http://people.freebsd.org/~babkin/cvs/

(If anyone wonders, yes, I do plan to submit this patch to the
CVS people).

-SB

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