From owner-freebsd-hackers Sun Jun 24 0:43:34 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
by hub.freebsd.org (Postfix) with ESMTP
id 2077537B406; Sun, 24 Jun 2001 00:43:21 -0700 (PDT)
(envelope-from obrien@nuxi.ucdavis.edu)
Received: from dragon.nuxi.com (root@trang.muxi.com [206.40.252.115] (may be forged))
by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f5O7hKR28689;
Sun, 24 Jun 2001 00:43:20 -0700 (PDT)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by dragon.nuxi.com (8.11.3/8.11.1) id f5O7hGf33384;
Sun, 24 Jun 2001 00:43:16 -0700 (PDT)
(envelope-from obrien)
Date: Sun, 24 Jun 2001 00:43:15 -0700
From: freebsd-hackers@FreeBSD.ORG
To: Matthew Jacob <mjacob@feral.com>
Cc: John Baldwin <jhb@FreeBSD.ORG>, freebsd-hackers@FreeBSD.ORG
Subject: Re: Two Junior Kernel Hacker tasks..
Message-ID: <20010624004315.A27083@dragon.nuxi.com>
Reply-To: freebsd-hackers@FreeBSD.ORG
References: <XFMail.010622105201.jhb@FreeBSD.org> <20010622104940.P20923-100000@wonky.feral.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010622104940.P20923-100000@wonky.feral.com>; from mjacob@feral.com on Fri, Jun 22, 2001 at 10:50:00AM -0700
X-Operating-System: FreeBSD 5.0-CURRENT
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Fri, Jun 22, 2001 at 10:50:00AM -0700, Matthew Jacob wrote:
> Why can't we do it like NetBSD and have
>
> sys/${MACHINE_ARCH}/compile?
It makes it harder to make src/sys/compile a single simple symlink to
writable storage.
Our /sys layout is suffiently different from NetBSD, I don't think there
is any benefit from following them (nad it would be
sys/arch/${MACHINE_ARCH}/compile anyway).
--
-- David (obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 0:45:41 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
by hub.freebsd.org (Postfix) with ESMTP
id 474E337B401; Sun, 24 Jun 2001 00:45:39 -0700 (PDT)
(envelope-from obrien@nuxi.ucdavis.edu)
Received: from dragon.nuxi.com (root@trang.muxi.com [206.40.252.115] (may be forged))
by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f5O7jcR28697;
Sun, 24 Jun 2001 00:45:38 -0700 (PDT)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by dragon.nuxi.com (8.11.3/8.11.1) id f5O7jc533438;
Sun, 24 Jun 2001 00:45:38 -0700 (PDT)
(envelope-from obrien)
Date: Sun, 24 Jun 2001 00:45:38 -0700
From: hackers@FreeBSD.ORG
To: Will Andrews <will@physics.purdue.edu>
Cc: Matthew Jacob <mjacob@feral.com>, John Baldwin <jhb@FreeBSD.ORG>,
hackers@FreeBSD.ORG
Subject: Re: Two Junior Kernel Hacker tasks..
Message-ID: <20010624004538.B27083@dragon.nuxi.com>
Reply-To: hackers@FreeBSD.ORG
References: <20010622134229.I74316@bohr.physics.purdue.edu> <20010622114328.R20923-100000@wonky.feral.com> <20010622135154.J74316@bohr.physics.purdue.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010622135154.J74316@bohr.physics.purdue.edu>; from will@physics.purdue.edu on Fri, Jun 22, 2001 at 01:51:54PM -0500
X-Operating-System: FreeBSD 5.0-CURRENT
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Fri, Jun 22, 2001 at 01:51:54PM -0500, Will Andrews wrote:
> On Fri, Jun 22, 2001 at 11:43:58AM -0700, Matthew Jacob (mjacob@feral.com) wrote:
> > Yes, and you're right. But we'll probably never do this (tm).
>
> Never say never. I for one am in favor of that system. =)
Yuck! Puke! I for one am not in favor of that system.
--
-- David (obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 0:48:30 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
by hub.freebsd.org (Postfix) with ESMTP
id 7CDD937B401; Sun, 24 Jun 2001 00:48:28 -0700 (PDT)
(envelope-from obrien@nuxi.ucdavis.edu)
Received: from dragon.nuxi.com (root@trang.muxi.com [206.40.252.115] (may be forged))
by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f5O7mRR28730;
Sun, 24 Jun 2001 00:48:28 -0700 (PDT)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by dragon.nuxi.com (8.11.3/8.11.1) id f5O7mR133466;
Sun, 24 Jun 2001 00:48:27 -0700 (PDT)
(envelope-from obrien)
Date: Sun, 24 Jun 2001 00:48:27 -0700
From: hackers@FreeBSD.ORG
To: Warner Losh <imp@harmony.village.org>
Cc: John Baldwin <jhb@FreeBSD.ORG>, hackers@FreeBSD.ORG
Subject: Re: Two Junior Kernel Hacker tasks..
Message-ID: <20010624004826.C27083@dragon.nuxi.com>
Reply-To: hackers@FreeBSD.ORG
References: <XFMail.010622105201.jhb@FreeBSD.org> <200106221842.f5MIgaV58508@harmony.village.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200106221842.f5MIgaV58508@harmony.village.org>; from imp@harmony.village.org on Fri, Jun 22, 2001 at 12:42:36PM -0600
X-Operating-System: FreeBSD 5.0-CURRENT
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Fri, Jun 22, 2001 at 12:42:36PM -0600, Warner Losh wrote:
> Please use ${MACHINE}, not ${MACHINE_ARCH}. That way I can build
> GENERIC for both i386 and pc98 at the same time without resorting to
> the GENERIC98 hack I use now.
...
> I'd be up for doing this, so long as I got to choose where to build
> into :-)
>
> sys/arch/${MACHINE}/compile/FOO
>
> but that would start the arch bikeshed. I'd love to just do it.
Which is another good reason for sys/compile/${MACHINE}/FOO
Otherwise where DOES the pc98 kernel builds happen? Under the
non-existant sys/pc98/ ?
> With powerpc, we are going to have a lot of different ports ala
> i386/pc98 (that have the same MAHINCE_ARCH, but different MACHINE) if
> NetBSD is any indication.
Even more data that IMHO makes sys/compile/${MACHINE}/FOO make more
sense.
--
-- David (obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 0:52:42 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
by hub.freebsd.org (Postfix) with ESMTP
id 7BA4C37B401; Sun, 24 Jun 2001 00:52:39 -0700 (PDT)
(envelope-from obrien@nuxi.ucdavis.edu)
Received: from dragon.nuxi.com (root@trang.muxi.com [206.40.252.115] (may be forged))
by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f5O7qdR28748;
Sun, 24 Jun 2001 00:52:39 -0700 (PDT)
(envelope-from obrien@NUXI.com)
Received: (from obrien@localhost)
by dragon.nuxi.com (8.11.3/8.11.1) id f5O7qc933507;
Sun, 24 Jun 2001 00:52:38 -0700 (PDT)
(envelope-from obrien)
Date: Sun, 24 Jun 2001 00:52:38 -0700
From: freebsd-hackers@FreeBSD.org
To: John Baldwin <jhb@FreeBSD.org>
Cc: Warner Losh <imp@harmony.village.org>,
freebsd-hackers@FreeBSD.org
Subject: Re: Two Junior Kernel Hacker tasks..
Message-ID: <20010624005238.D27083@dragon.nuxi.com>
Reply-To: freebsd-hackers@FreeBSD.org
References: <200106221842.f5MIgaV58508@harmony.village.org> <XFMail.010622121136.jhb@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <XFMail.010622121136.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Fri, Jun 22, 2001 at 12:11:36PM -0700
X-Operating-System: FreeBSD 5.0-CURRENT
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Fri, Jun 22, 2001 at 12:11:36PM -0700, John Baldwin wrote:
> On 22-Jun-01 Warner Losh wrote:
> > In message <XFMail.010622105201.jhb@FreeBSD.org> John Baldwin writes:
> >: 2) Build kernels in sys/compile/${MACHINE_ARCH}/FOO rather than
> >: sys/compile/FOO.
> >
> > Please use ${MACHINE}, not ${MACHINE_ARCH}. That way I can build
> > GENERIC for both i386 and pc98 at the same time without resorting to
> > the GENERIC98 hack I use now.
>
> Sure, sounds good. Actually, with mjacob's suggestion, I would go with
> sys/${MACHINE}/compile/FOO
pc98 and powerpc variations will make this ugly.
> I would tackle the sys/arch bikeshed on its own merits for now. (BTW,
> I favor sys/arch FWIW). If we use the path I proposed above
> (sys/MACHINE/compile/FOO) then if we do a sys/MACHINE ->
> sys/arch/MACHINE move we get the compile directory move for free.
PUKE, GROSS. NO.
--
-- David (obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 3:25:18 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ringworld.nanolink.com (beleriand.online.bg [217.75.129.181])
by hub.freebsd.org (Postfix) with SMTP id 1147037B407
for <hackers@FreeBSD.org>; Sun, 24 Jun 2001 03:25:11 -0700 (PDT)
(envelope-from roam@orbitel.bg)
Received: (qmail 2080 invoked by uid 1000); 24 Jun 2001 10:23:29 -0000
Date: Sun, 24 Jun 2001 13:23:29 +0300
From: Peter Pentchev <roam@orbitel.bg>
To: John Baldwin <jhb@FreeBSD.org>
Cc: hackers@FreeBSD.org, Valentin Nechayev <netch@iv.nn.kiev.ua>,
Terry Lambert <tlambert2@mindspring.com>
Subject: Re: Two Junior Kernel Hacker tasks..
Message-ID: <20010624132329.A507@ringworld.oblivion.bg>
Mail-Followup-To: John Baldwin <jhb@FreeBSD.org>,
hackers@FreeBSD.org, Valentin Nechayev <netch@iv.nn.kiev.ua>,
Terry Lambert <tlambert2@mindspring.com>
References: <20010623225526.A564@ringworld.oblivion.bg> <XFMail.010623224451.jhb@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <XFMail.010623224451.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Sat, Jun 23, 2001 at 10:44:51PM -0700
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Sat, Jun 23, 2001 at 10:44:51PM -0700, John Baldwin wrote:
>
> On 23-Jun-01 Peter Pentchev wrote:
> > On Sat, Jun 23, 2001 at 12:23:35PM -0700, Terry Lambert wrote:
> >> > make buildkernel is rather easy way to work it around: in
> >> > any case object tree is machine-dependent, and one yet
> >> > another directory does not destroy anything. ;|
> >>
> >> The "make buildkernel" approach sucks for incremental
> >> builds, since you are unable to avoid the "config" run
> >> each time, and a lot of unnecessary stuff gets compiled
> >> again because of opt_*.h files whose contents have not
> >> changed (even if you defeat the clean of the compile
> >> directory).
> >
> > About the release process, you are right, it is a bit harder
> > to restart without some tweaks, but the buildkernel target
> > is about as restartable as it can be. (I really don't think
> > anyone would ever advocate skipping the config(8) or
> > the 'make depend' stage..)
>
> Actually, make depend takes a relatively long time, and when
> I'm hacking on a kernel, I don't want to wait 15 minutes to
> build a kernel after changing one file. I compile kernels
> w/o config or make depend a lot.
OK, so if you're really really sure your changes do not affect
the dependency graph, use -DNOKERNELDEPEND :)
G'luck,
Peter
--
This sentence contains exactly threee erors.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 3:25:43 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from nef.ens.fr (nef.ens.fr [129.199.96.32])
by hub.freebsd.org (Postfix) with ESMTP id 8E44037B405
for <hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 03:25:39 -0700 (PDT)
(envelope-from Rahul.Siddharthan@lpt.ens.fr)
Received: from corto.lpt.ens.fr (corto.lpt.ens.fr [129.199.122.2])
by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id f5OAPb626070
; Sun, 24 Jun 2001 12:25:37 +0200 (CEST)
Received: from (rsidd@localhost)
by corto.lpt.ens.fr (8.9.3/jtpda-5.3.1) id MAA15864
; Sun, 24 Jun 2001 12:26:32 +0200 (CEST)
Date: Sun, 24 Jun 2001 12:26:32 +0200
From: Rahul Siddharthan <rsidd@physics.iisc.ernet.in>
To: Wes Peters <wes@softweyr.com>
Cc: "Koster K.J." <K.J.Koster@kpn.com>,
"'Jordan Hubbard'" <jkh@osd.bsdi.com>, hackers@FreeBSD.ORG
Subject: Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
Message-ID: <20010624122632.C15588@lpt.ens.fr>
References: <59063B5B4D98D311BC0D0001FA7E452205FD9CD5@l04.research.kpn.com> <20010621120034.A63133@lpt.ens.fr> <3B357A8A.E7E704F3@softweyr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3B357A8A.E7E704F3@softweyr.com>; from wes@softweyr.com on Sat, Jun 23, 2001 at 11:28:42PM -0600
X-Operating-System: FreeBSD 3.4-STABLE 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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Wes Peters said on Jun 23, 2001 at 23:28:42:
> > Plenty of GNU stuff there, though it doesn't say so explicitly.
> > Of course, they say it's all meant only for "legacy Unix" stuff.
>
> Can you substantiate your claim there is "plenty of GNU stuff" in
> Interix, or are you just talking out your ass as usual?
Why should I substantiate it? Do it yourself if it bothers you.
R
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 8:42:10 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18])
by hub.freebsd.org (Postfix) with ESMTP id C5C6B37B405
for <freebsd-hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 08:42:07 -0700 (PDT)
(envelope-from zzhang@cs.binghamton.edu)
Received: from opal (cs.binghamton.edu [128.226.123.101])
by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f5OFg5H25636;
Sun, 24 Jun 2001 11:42:05 -0400 (EDT)
Date: Sun, 24 Jun 2001 11:42:04 -0400 (EDT)
From: Zhihui Zhang <zzhang@cs.binghamton.edu>
X-Sender: zzhang@opal
To: Terry Lambert <tlambert2@mindspring.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Confusion with mknod() and devfs
In-Reply-To: <3B350150.E6175A61@mindspring.com>
Message-ID: <Pine.SOL.4.21.0106241124300.22184-100000@opal>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Sat, 23 Jun 2001, Terry Lambert wrote:
> Zhihui Zhang wrote:
> > I think you got me wrong. I was talking about a device
> > with more than one names. So we can have more than one
> > vnode for the same device. (If there is more than one name
> > to the same device in the same FS, they can share the vnode,
> > otherwise, they cannot.)
>
> This is not how it works. The specfs/devfs will return
> the same vnode.
>
> A "special device" file type in the traditional sense is
> a major/minor/{block|character} tuple.
>
> The entry in an FS that references this is _not_ where
> the vnode comes from, it's a hint to tell the system to
> get the vnode from a single place, instead (specfs in a
> traditional system, vfs in a less traditional system).
>
>
> > Specifically, I fail to understand why we reload the inode
> > in ufs_mknod():
>
> Because when you make the node, you may have an exiting
> open reference to the same major/minor/{block|character}
> tuple, and you don't want to duplicate it in the ihash
> cache.
>
Thanks. But I still don't get it. The ihash is keyed on i_dev (the
device where the filesystem is mounted on) and i_number.
If I have two names in a filesystem refer to the same device, then their
inode number must be different.
if two names from different filesystems refer to the same device, then
their i_dev is different even if their inode number may happen to be the
same.
So I do not see how can we avoid duplicate entries in the ihash cache.
-Zhihui
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 8:49: 2 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
by hub.freebsd.org (Postfix) with ESMTP
id 166B937B405; Sun, 24 Jun 2001 08:48:56 -0700 (PDT)
(envelope-from des@ofug.org)
Received: (from des@localhost)
by flood.ping.uio.no (8.9.3/8.9.3) id RAA82575;
Sun, 24 Jun 2001 17:48:48 +0200 (CEST)
(envelope-from des@ofug.org)
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: Soren Kristensen <soren@soekris.com>
Cc: hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
References: <3B33A891.EC712701@soekris.com>
From: Dag-Erling Smorgrav <des@ofug.org>
Date: 24 Jun 2001 17:48:47 +0200
In-Reply-To: <3B33A891.EC712701@soekris.com>
Message-ID: <xzpn16x7uao.fsf@flood.ping.uio.no>
Lines: 27
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Soren Kristensen <soren@soekris.com> writes:
> As I now has prototypes avaliable of low cost PCI and MiniPCI boards,
> moving to production in a couple of weeks, I would like to check up on
> the work, as I would really like to see FreeBSD support. The boards are
> now supported in OpenBSD 2.9.
OK, so if I understand correctly, the encryption hardware in question
offers a high-speed hardware implementation of the encryption
algorithms used by IPSec, so it's a matter of a) having support code
that interfaces with the hardware, possibly with a device interface to
allow userland apps access to the encryption hardware and b) making
our (well, KAME's) IPSec code use that instead of doing the encryption
in software. Is that it, or did I misunderstand something?
Now, if you want FreeBSD support for your hardware, all you have to do
is find a willing developer <whistles innocently>, send him a sample
board (or preferably two, for a full circuit, but one will do) with
complete documentation and any additional resources you are willing
and able to provide, and then wait a bit. Simply asking for someone
to port the OpenBSD driver will not do - OpenBSD and FreeBSD are not
very similar at the kernel level, and as others have stated before in
a different context, driver source does not constitute adequate
documentation. It helps, but it's neither sufficient nor necessary.
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 Sun Jun 24 9:10: 0 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209])
by hub.freebsd.org (Postfix) with SMTP id 80E0B37B409
for <hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 09:09:51 -0700 (PDT)
(envelope-from karsten@rohrbach.de)
Received: (qmail 53678 invoked by uid 1000); 24 Jun 2001 16:10:07 -0000
Date: Sun, 24 Jun 2001 18:10:07 +0200
From: "Karsten W. Rohrbach" <karsten@rohrbach.de>
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: Soren Kristensen <soren@soekris.com>, hackers@FreeBSD.ORG,
freebsd-security@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
Message-ID: <20010624181007.C52432@mail.webmonster.de>
Mail-Followup-To: "Karsten W. Rohrbach" <karsten@rohrbach.de>,
Dag-Erling Smorgrav <des@ofug.org>,
Soren Kristensen <soren@soekris.com>, hackers@FreeBSD.ORG,
freebsd-security@FreeBSD.ORG
References: <3B33A891.EC712701@soekris.com> <xzpn16x7uao.fsf@flood.ping.uio.no>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="PuGuTyElPB9bOcsM"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <xzpn16x7uao.fsf@flood.ping.uio.no>; from des@ofug.org on Sun, Jun 24, 2001 at 05:48:47PM +0200
X-Arbitrary-Number-Of-The-Day: 42
X-URL: http://www.webmonster.de/
X-Disclaimer: My opinions do not necessarily represent those of my employer
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
--PuGuTyElPB9bOcsM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Dag-Erling Smorgrav(des@ofug.org)@2001.06.24 17:48:47 +0000:
> Soren Kristensen <soren@soekris.com> writes:
> > As I now has prototypes avaliable of low cost PCI and MiniPCI boards,
> > moving to production in a couple of weeks, I would like to check up on
> > the work, as I would really like to see FreeBSD support. The boards are
> > now supported in OpenBSD 2.9.
>=20
> OK, so if I understand correctly, the encryption hardware in question
> offers a high-speed hardware implementation of the encryption
> algorithms used by IPSec, so it's a matter of a) having support code
> that interfaces with the hardware, possibly with a device interface to
> allow userland apps access to the encryption hardware and b) making
> our (well, KAME's) IPSec code use that instead of doing the encryption
> in software. Is that it, or did I misunderstand something?
i think ipsec crypto abstraction into hardware is one side of the medal,
but the other side -- to be polished first -- ist getting openssl onto
the iron. for my former employer i had my hands on rainbow crupto
hardware. it is a pci card called cryptoswift with a number, indicating
the amount of ssl handshakes per second. the company has been renamed to
ivea (http://www.ivea.com/). i came across this board since it is used
in several "appliance" style boxes such as the intel netsctructure ssl
accelerators (drop-in https->http ethernet bridge). they had working
support and drivers for 3.x, developed in-house and i started hacking up
the code for 4.x, but then i left the company (had to leave the hardware
there, of course).
as far as i got, my experience with ssl handshake processing in hardware
showed me a great improvement, since openssl plugs in the hardware to
create random and to create session keys. stream crypto is spoken on the
host, but this is done fast and very effieciently. if you offload the
handshakes to the iron, most of you sysload goes away, of course.
i did not find another vendor in europe that provides a similar chip on
a pci card, doing the stuff on the iron on a very high level (the card
speaks x.50x ascii armored certificates natively, as far as i could see.
it would be interesting if somebody from the u.s. could join in and
present a list of available hardware and corresponding vendor. if there
is hardware available from a crypto-relaxed country, such as south
africa or similar, this would also be _very_ interesting, IMHO.
>=20
> Now, if you want FreeBSD support for your hardware, all you have to do
> is find a willing developer <whistles innocently>, send him a sample
> board (or preferably two, for a full circuit, but one will do) with
> complete documentation and any additional resources you are willing
> and able to provide, and then wait a bit. Simply asking for someone
> to port the OpenBSD driver will not do - OpenBSD and FreeBSD are not
> very similar at the kernel level, and as others have stated before in
> a different context, driver source does not constitute adequate
> documentation. It helps, but it's neither sufficient nor necessary.
as i said, there is a 3.x freebsd driver, would this help?
i am not into writing drivers ;-)
/k
--=20
> Sex is one of the nine reasons for reincarnation ... the other eight
> are unimportant. --Henry Miller
KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie
http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.n=
et/
karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- catch@spam.de
GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 B=
F46
Please do not remove my address from To: and Cc: fields in mailing lists. 1=
0x
--PuGuTyElPB9bOcsM
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iD8DBQE7NhDfM0BPTilkv0YRAq8KAKCtBtfnTgl5cleVcAHUe58TPa9v3gCgudOe
Dn+Yw0/NEpr2UbNJZEjnjeQ=
=jx0g
-----END PGP SIGNATURE-----
--PuGuTyElPB9bOcsM--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 9:21: 1 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
by hub.freebsd.org (Postfix) with ESMTP
id F044D37B407; Sun, 24 Jun 2001 09:20:55 -0700 (PDT)
(envelope-from des@ofug.org)
Received: (from des@localhost)
by flood.ping.uio.no (8.9.3/8.9.3) id SAA82714;
Sun, 24 Jun 2001 18:20:54 +0200 (CEST)
(envelope-from des@ofug.org)
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: "Karsten W. Rohrbach" <karsten@rohrbach.de>
Cc: Soren Kristensen <soren@soekris.com>, hackers@FreeBSD.ORG,
freebsd-security@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
References: <3B33A891.EC712701@soekris.com>
<xzpn16x7uao.fsf@flood.ping.uio.no>
<20010624181007.C52432@mail.webmonster.de>
From: Dag-Erling Smorgrav <des@ofug.org>
Date: 24 Jun 2001 18:20:53 +0200
In-Reply-To: <20010624181007.C52432@mail.webmonster.de>
Message-ID: <xzpd77t7st6.fsf@flood.ping.uio.no>
Lines: 23
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
"Karsten W. Rohrbach" <karsten@rohrbach.de> writes:
> i think ipsec crypto abstraction into hardware is one side of the medal,
> but the other side -- to be polished first -- ist getting openssl onto
> the iron.
What you're basically trying to say is that you want a userland
interface to the crypto hardware, so that OpenSSL can take advatange
of it if it's present?
> as i said, there is a 3.x freebsd driver, would this help?
> i am not into writing drivers ;-)
Allow me to repeat myself: "driver source does not constitute adequate
documentation. It helps, but it's neither sufficient nor necessary."
A 3.x driver *could* be ported forward to 4.x and 5.x, but the
required changes are not trivial (newbus, SMPng...) and you'd still
need sample boards for testing and debugging, and docs for reference
when you don't understand what the existing driver is trying to do.
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 Sun Jun 24 9:30:24 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4])
by hub.freebsd.org (Postfix) with ESMTP id B400E37B405
for <freebsd-hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 09:30:18 -0700 (PDT)
(envelope-from netch@iv.nn.kiev.ua)
Received: (from uucp@localhost)
by segfault.kiev.ua (8) with UUCP id TLQ96678
for freebsd-hackers@FreeBSD.ORG; Sun, 24 Jun 2001 19:30:15 +0300 (EEST)
(envelope-from netch@iv.nn.kiev.ua)
Received: (from netch@localhost)
by iv.nn.kiev.ua (8.11.4/8.11.4) id f5OGQfO00612
for freebsd-hackers@FreeBSD.ORG; Sun, 24 Jun 2001 19:26:41 +0300 (EEST)
(envelope-from netch)
Date: Sun, 24 Jun 2001 19:26:41 +0300
From: Valentin Nechayev <netch@iv.nn.kiev.ua>
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: Two Junior Kernel Hacker tasks..
Message-ID: <20010624192641.A555@iv.nn.kiev.ua>
References: <XFMail.010622105201.jhb@FreeBSD.org> <20010622104940.P20923-100000@wonky.feral.com> <20010624004315.A27083@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010624004315.A27083@dragon.nuxi.com>; from freebsd-hackers@FreeBSD.ORG on Sun, Jun 24, 2001 at 12:43:15AM -0700
X-42: On
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> > sys/${MACHINE_ARCH}/compile?
> It makes it harder to make src/sys/compile a single simple symlink to
> writable storage.
There is no need to make symlink in src tree.
> -- David (obrien@FreeBSD.org)
Are you David O'Brien or freebsd-hackers list itself?
/netch
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 9:31:45 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209])
by hub.freebsd.org (Postfix) with SMTP id 446D637B405
for <hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 09:31:28 -0700 (PDT)
(envelope-from karsten@rohrbach.de)
Received: (qmail 54605 invoked by uid 1000); 24 Jun 2001 16:31:47 -0000
Date: Sun, 24 Jun 2001 18:31:47 +0200
From: "Karsten W. Rohrbach" <karsten@rohrbach.de>
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: Soren Kristensen <soren@soekris.com>, hackers@FreeBSD.ORG,
freebsd-security@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
Message-ID: <20010624183147.F52432@mail.webmonster.de>
Mail-Followup-To: "Karsten W. Rohrbach" <karsten@rohrbach.de>,
Dag-Erling Smorgrav <des@ofug.org>,
Soren Kristensen <soren@soekris.com>, hackers@FreeBSD.ORG,
freebsd-security@FreeBSD.ORG
References: <3B33A891.EC712701@soekris.com> <xzpn16x7uao.fsf@flood.ping.uio.no> <20010624181007.C52432@mail.webmonster.de> <xzpd77t7st6.fsf@flood.ping.uio.no>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="B0nZA57HJSoPbsHY"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <xzpd77t7st6.fsf@flood.ping.uio.no>; from des@ofug.org on Sun, Jun 24, 2001 at 06:20:53PM +0200
X-Arbitrary-Number-Of-The-Day: 42
X-URL: http://www.webmonster.de/
X-Disclaimer: My opinions do not necessarily represent those of my employer
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
--B0nZA57HJSoPbsHY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Dag-Erling Smorgrav(des@ofug.org)@2001.06.24 18:20:53 +0000:
> "Karsten W. Rohrbach" <karsten@rohrbach.de> writes:
> > i think ipsec crypto abstraction into hardware is one side of the medal,
> > but the other side -- to be polished first -- ist getting openssl onto
> > the iron.
>=20
> What you're basically trying to say is that you want a userland
> interface to the crypto hardware, so that OpenSSL can take advatange
> of it if it's present?
yup, exactly. to me it seems to be a major problem to get some unified
api out of openssl adressing fucnctions on the hardware -- i simply do
not know how other crypto chipsets do it, i just investigated the
rainbow board. they got a patch against openssl 0.9.5 i think, that
glues in the driver calls instead of standard lib functions.
>=20
> > as i said, there is a 3.x freebsd driver, would this help?
> > i am not into writing drivers ;-)
>=20
> Allow me to repeat myself: "driver source does not constitute adequate
> documentation. It helps, but it's neither sufficient nor necessary."
yes yes yes ;-) you are perfectly right here. i just wanrted to mention
that there is an _existant_ driver and patch against the openssl lib,
also some test programs to look if the driver works, for freebsd 3.x.
> A 3.x driver *could* be ported forward to 4.x and 5.x, but the
> required changes are not trivial (newbus, SMPng...) and you'd still
> need sample boards for testing and debugging, and docs for reference
> when you don't understand what the existing driver is trying to do.
sure. my impression with the rainbow guys was, that they are very open
to the opensource community. they supplied a board, (user) docs and the
unreleased driver/openssl code to us and i was very impressed about
their attitude towards people hacking up their stuff *grin*.
alas, i quit the company and i did not even start really hacking on the
code to take it to a place even near to production. i see from their web
page, that they now support freebsd 4.1-release, so it sounds rather
appealing to me...
/k
--=20
> Captain Hook died of jock itch.
KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie
http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.n=
et/
karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- catch@spam.de
GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 B=
F46
Please do not remove my address from To: and Cc: fields in mailing lists. 1=
0x
--B0nZA57HJSoPbsHY
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iD8DBQE7NhXzM0BPTilkv0YRAsndAJ9N8aGLN2PqQ9JnBnKtyOGQ/uiTzQCgw88h
Js4cenYHfd03bh5Hb2wgQ7s=
=BUvX
-----END PGP SIGNATURE-----
--B0nZA57HJSoPbsHY--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 9:31:39 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34])
by hub.freebsd.org (Postfix) with ESMTP
id B5F8737B406; Sun, 24 Jun 2001 09:31:25 -0700 (PDT)
(envelope-from ume@mahoroba.org)
Received: from localhost (IDENT:OH2hwKyzlYgzEtWJ5iprGG7pdQxUFRRL2H3OOkMuttbmbv7BXTD1U8iQX2Qag7pz@localhost [::1])
(authenticated as ume with CRAM-MD5)
by peace.mahoroba.org (8.11.4/8.11.4/peace) with ESMTP/inet6 id f5OGV9R76497;
Mon, 25 Jun 2001 01:31:09 +0900 (JST)
(envelope-from ume@mahoroba.org)
Date: Mon, 25 Jun 2001 01:31:06 +0900 (JST)
Message-Id: <20010625.013106.78752396.ume@mahoroba.org>
To: brooks@one-eyed-alien.net
Cc: hackers@FreeBSD.ORG, brian@Awfulhak.org, phk@critter.freebsd.dk,
arch@FreeBSD.ORG
Subject: Re: cloning network interfaces
From: Hajimu UMEMOTO <ume@mahoroba.org>
In-Reply-To: <20010622125113.A30459@Odin.AC.HMC.Edu>
References: <20010611142030.A15283@Odin.AC.HMC.Edu>
<20010613.040716.115941864.ume@mahoroba.org>
<20010622125113.A30459@Odin.AC.HMC.Edu>
X-Mailer: xcite1.38> Mew version 1.95b119 on Emacs 20.7 / Mule 4.0
=?iso-2022-jp?B?KBskQjJWMWMbKEIp?=
X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc
X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC
X-URL: http://www.imasy.org/~ume/
X-Operating-System: FreeBSD 5.0-CURRENT
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
>>>>> On Fri, 22 Jun 2001 12:51:13 -0700
>>>>> Brooks Davis <brooks@one-eyed-alien.net> said:
brooks> Ok, after a week and a half of doing other things, I've got a patch
brooks> together which adds interface cloning based on NetBSD's code. The
brooks> difference is that you may pass an interface of the from gif# if you
brooks> don't need a specific number. The ioctl now returns a potentialy
brooks> modified ifreq which contains the new interface name. This changes the
brooks> way drivers implement cloning in that they may return a different unit
brooks> then they were passed and they must do their own resource management
brooks> rather then relying on the clone functionality in sys/net/if.c to do it
brooks> for them.
brooks> The patch is at:
brooks> http://people.freebsd.org/~brooks/patches/gif.diff
brooks> The patch can be applied as follows (you need to make the directories):
brooks> cd /usr/src
brooks> mkdir sys/modules/if_gif sys/modules/if_stf
brooks> patch < /tmp/gif.diff
brooks> The patch does the following:
brooks> - adds interface cloning support to the kernel
brooks> - adds interface cloning support to ifconfig
brooks> - makes gif clonable
brooks> - makes gif usable as a module
brooks> - removes the need for NGIF and gif.h
brooks> - removes va_args usage in in_gif_input to remove a warning
brooks> - removes gif dependencies from stf
brooks> - makes stf usable as a module
It seems fine to me.
I just tried it on my box. You forget to include prototype change of
in_gif_input() in sys/net/if_gif.h.
BTW, why did you change gif_ioctl() to gif_ifioctl()? gif related
modules are shared among *BSDs and maintained in KAME CVS repository.
Could you please keep local changes small as possible?
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 9:38:39 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
by hub.freebsd.org (Postfix) with ESMTP
id A0D4C37B401; Sun, 24 Jun 2001 09:38:33 -0700 (PDT)
(envelope-from des@ofug.org)
Received: (from des@localhost)
by flood.ping.uio.no (8.9.3/8.9.3) id SAA82832;
Sun, 24 Jun 2001 18:38:31 +0200 (CEST)
(envelope-from des@ofug.org)
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: "Karsten W. Rohrbach" <karsten@rohrbach.de>
Cc: Soren Kristensen <soren@soekris.com>, hackers@FreeBSD.ORG,
freebsd-security@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
References: <3B33A891.EC712701@soekris.com>
<xzpn16x7uao.fsf@flood.ping.uio.no>
<20010624181007.C52432@mail.webmonster.de>
<xzpd77t7st6.fsf@flood.ping.uio.no>
<20010624183147.F52432@mail.webmonster.de>
From: Dag-Erling Smorgrav <des@ofug.org>
Date: 24 Jun 2001 18:38:31 +0200
In-Reply-To: <20010624183147.F52432@mail.webmonster.de>
Message-ID: <xzpzoax6dfc.fsf@flood.ping.uio.no>
Lines: 21
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
"Karsten W. Rohrbach" <karsten@rohrbach.de> writes:
> yup, exactly. to me it seems to be a major problem to get some unified
> api out of openssl adressing fucnctions on the hardware -- i simply do
> not know how other crypto chipsets do it, i just investigated the
> rainbow board. they got a patch against openssl 0.9.5 i think, that
> glues in the driver calls instead of standard lib functions.
Can you dig out this patch for me? It would be a big win if the
userland interface to Soren's hardware were compatible with Rainbow's
driver.
> yes yes yes ;-) you are perfectly right here. i just wanrted to mention
> that there is an _existant_ driver and patch against the openssl lib,
> also some test programs to look if the driver works, for freebsd 3.x.
This would be useful for ensuring compatibility with Rainbow's stuff,
especially if, as you say, they have a 4.1 version out now.
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 Sun Jun 24 9:49:11 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from netbank.com.br (garrincha.netbank.com.br [200.203.199.88])
by hub.freebsd.org (Postfix) with ESMTP id EB36C37B405
for <hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 09:49:07 -0700 (PDT)
(envelope-from riel@conectiva.com.br)
Received: from surriel.ddts.net (1-150.ctame701-1.telepar.net.br [200.181.137.150])
by netbank.com.br (Postfix) with ESMTP
id 24DE546805; Sun, 24 Jun 2001 13:45:42 -0300 (BRST)
Received: from localhost (mguztu@localhost [127.0.0.1])
by surriel.ddts.net (8.11.4/8.11.2) with ESMTP id f5OGmqC25667;
Sun, 24 Jun 2001 13:48:55 -0300
Date: Sun, 24 Jun 2001 13:48:52 -0300 (BRST)
From: Rik van Riel <riel@conectiva.com.br>
X-Sender: riel@imladris.rielhome.conectiva
To: Rahul Siddharthan <rsidd@physics.iisc.ernet.in>
Cc: Wes Peters <wes@softweyr.com>,
"Koster K.J." <K.J.Koster@kpn.com>,
"'Jordan Hubbard'" <jkh@osd.bsdi.com>, hackers@FreeBSD.ORG
Subject: Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
In-Reply-To: <20010624122632.C15588@lpt.ens.fr>
Message-ID: <Pine.LNX.4.21.0106241348310.7419-100000@imladris.rielhome.conectiva>
X-spambait: aardvark@kernelnewbies.org
X-spammeplease: aardvark@nl.linux.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Sun, 24 Jun 2001, Rahul Siddharthan wrote:
> Wes Peters said on Jun 23, 2001 at 23:28:42:
> > > Plenty of GNU stuff there, though it doesn't say so explicitly.
> > > Of course, they say it's all meant only for "legacy Unix" stuff.
> >
> > Can you substantiate your claim there is "plenty of GNU stuff" in
> > Interix, or are you just talking out your ass as usual?
gcc, gdb, bash, gnu emacs and a bunch more.
Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...
http://www.surriel.com/ http://distro.conectiva.com/
Send all your spam to aardvark@nl.linux.org (spam digging piggy)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 10: 7: 7 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9])
by hub.freebsd.org (Postfix) with ESMTP id A23B737B407
for <hackers@freebsd.org>; Sun, 24 Jun 2001 10:07:04 -0700 (PDT)
(envelope-from jlemon@flugsvamp.com)
Received: (from jlemon@localhost)
by prism.flugsvamp.com (8.11.0/8.11.0) id f5OH5a060211;
Sun, 24 Jun 2001 12:05:36 -0500 (CDT)
(envelope-from jlemon)
Date: Sun, 24 Jun 2001 12:05:36 -0500 (CDT)
From: Jonathan Lemon <jlemon@flugsvamp.com>
Message-Id: <200106241705.f5OH5a060211@prism.flugsvamp.com>
To: karsten@rohrbach.de, hackers@freebsd.org
Subject: Re: Status of encryption hardware support in FreeBSD
X-Newsgroups: local.mail.freebsd-hackers
In-Reply-To: <local.mail.freebsd-hackers/20010624183147.F52432@mail.webmonster.de>
References: <local.mail.freebsd-hackers/3B33A891.EC712701@soekris.com>
<local.mail.freebsd-hackers/xzpn16x7uao.fsf@flood.ping.uio.no>
<local.mail.freebsd-hackers/20010624181007.C52432@mail.webmonster.de>
<local.mail.freebsd-hackers/xzpd77t7st6.fsf@flood.ping.uio.no>
Organization:
Cc:
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In article <local.mail.freebsd-hackers/20010624183147.F52432@mail.webmonster.de> you write:
>sure. my impression with the rainbow guys was, that they are very open
>to the opensource community. they supplied a board, (user) docs and the
>unreleased driver/openssl code to us and i was very impressed about
>their attitude towards people hacking up their stuff *grin*.
>alas, i quit the company and i did not even start really hacking on the
>code to take it to a place even near to production. i see from their web
>page, that they now support freebsd 4.1-release, so it sounds rather
>appealing to me...
Do you have a contact address? I am going to start implementing
crypto offload in the next month and would like to be able to get
support for as many devices as possible.
--
Jonathan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 10:48:19 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from imo-m03.mx.aol.com (imo-m03.mx.aol.com [64.12.136.6])
by hub.freebsd.org (Postfix) with ESMTP id 4124D37B401
for <hackers@freebsd.org>; Sun, 24 Jun 2001 10:48:17 -0700 (PDT)
(envelope-from Bsdguru@aol.com)
Received: from Bsdguru@aol.com
by imo-m03.mx.aol.com (mail_out_v30.22.) id n.a2.15e39041 (3966)
for <hackers@freebsd.org>; Sun, 24 Jun 2001 13:48:05 -0400 (EDT)
From: Bsdguru@aol.com
Message-ID: <a2.15e39041.286781d5@aol.com>
Date: Sun, 24 Jun 2001 13:48:05 EDT
Subject: Re: Status of encryption hardware support in FreeBSD
To: hackers@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 5.0 for Windows sub 138
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In a message dated 6/24/01 12:33:25 PM Eastern Daylight Time,
karsten@rohrbach.de writes:
> > A 3.x driver *could* be ported forward to 4.x and 5.x, but the
> > required changes are not trivial (newbus, SMPng...) and you'd still
> > need sample boards for testing and debugging, and docs for reference
> > when you don't understand what the existing driver is trying to do.
>
I'd suggest doing a study on the benefits as well. With 1+Ghz processors, the
advantages of doing this in hardware become less than in the old days. We did
a study on compression hardware, and at 400Mhz is was faster to do it in
software than with external hardware. The setup, write to hardware, read from
hardware cycles were more than the software processing requirements.
Bryan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 11:14:44 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209])
by hub.freebsd.org (Postfix) with SMTP id AAF1337B40C
for <hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 11:14:36 -0700 (PDT)
(envelope-from karsten@rohrbach.de)
Received: (qmail 57928 invoked by uid 1000); 24 Jun 2001 18:14:56 -0000
Date: Sun, 24 Jun 2001 20:14:56 +0200
From: "Karsten W. Rohrbach" <karsten@rohrbach.de>
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: Soren Kristensen <soren@soekris.com>, hackers@FreeBSD.ORG,
freebsd-security@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
Message-ID: <20010624201456.A57877@mail.webmonster.de>
Mail-Followup-To: "Karsten W. Rohrbach" <karsten@rohrbach.de>,
Dag-Erling Smorgrav <des@ofug.org>,
Soren Kristensen <soren@soekris.com>, hackers@FreeBSD.ORG,
freebsd-security@FreeBSD.ORG
References: <3B33A891.EC712701@soekris.com> <xzpn16x7uao.fsf@flood.ping.uio.no> <20010624181007.C52432@mail.webmonster.de> <xzpd77t7st6.fsf@flood.ping.uio.no> <20010624183147.F52432@mail.webmonster.de> <xzpzoax6dfc.fsf@flood.ping.uio.no>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <xzpzoax6dfc.fsf@flood.ping.uio.no>; from des@ofug.org on Sun, Jun 24, 2001 at 06:38:31PM +0200
X-Arbitrary-Number-Of-The-Day: 42
X-URL: http://www.webmonster.de/
X-Disclaimer: My opinions do not necessarily represent those of my employer
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
--tThc/1wpZn/ma/RB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Dag-Erling Smorgrav(des@ofug.org)@2001.06.24 18:38:31 +0000:
> "Karsten W. Rohrbach" <karsten@rohrbach.de> writes:
> > yup, exactly. to me it seems to be a major problem to get some unified
> > api out of openssl adressing fucnctions on the hardware -- i simply do
> > not know how other crypto chipsets do it, i just investigated the
> > rainbow board. they got a patch against openssl 0.9.5 i think, that
> > glues in the driver calls instead of standard lib functions.
>=20
> Can you dig out this patch for me? It would be a big win if the
> userland interface to Soren's hardware were compatible with Rainbow's
> driver.
i think it would be a wise choice to ask rainbow for the current stuff,
as they are stating 4.1-rel would be supported. i get back with the
contact addresses to you guys off-list.
/k
--=20
> Life is a sexually transmitted disease.
KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie
http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.n=
et/
karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- catch@spam.de
GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 B=
F46
Please do not remove my address from To: and Cc: fields in mailing lists. 1=
0x
--tThc/1wpZn/ma/RB
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iD8DBQE7Ni4gM0BPTilkv0YRAqjGAJ0ZZGVPeGSBMKNpUdpeVyJsP8baoQCfRPFn
ASEQhWh4CnJboT4Iw+auPDs=
=xkKz
-----END PGP SIGNATURE-----
--tThc/1wpZn/ma/RB--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 11:53:22 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from server.soekris.com (soekris.com [216.15.61.44])
by hub.freebsd.org (Postfix) with ESMTP
id BFC6537B401; Sun, 24 Jun 2001 11:53:14 -0700 (PDT)
(envelope-from soren@soekris.com)
Received: from soekris.com (soren.soekris.com [192.168.1.4])
by server.soekris.com (8.9.2/8.9.2) with ESMTP id LAA53569;
Sun, 24 Jun 2001 11:53:26 -0700 (PDT)
(envelope-from soren@soekris.com)
Message-ID: <3B363713.2849219@soekris.com>
Date: Sun, 24 Jun 2001 11:53:07 -0700
From: Soren Kristensen <soren@soekris.com>
Organization: Soekris Engineering
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Karsten W. Rohrbach" <karsten@rohrbach.de>
Cc: Dag-Erling Smorgrav <des@ofug.org>, hackers@FreeBSD.ORG,
freebsd-security@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
References: <3B33A891.EC712701@soekris.com> <xzpn16x7uao.fsf@flood.ping.uio.no> <20010624181007.C52432@mail.webmonster.de> <xzpd77t7st6.fsf@flood.ping.uio.no> <20010624183147.F52432@mail.webmonster.de> <xzpzoax6dfc.fsf@flood.ping.uio.no> <20010624201456.A57877@mail.webmonster.de>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi,
Thanks for the responses so far. First, let me say that I'm a hardware
guy, and don't know all the details of FreeBSD's network stack.
There is two common kind of hardware encryption acceleration, and I
think they're being mixed a little here.
SSL is for secure web access, and the main need is for Public Key
generating. This don't really have anything to do with the IP stack.
Afaik, OpenSSL is more like a extension to the web server software.
IPSec is for secure communication, and the main need is for symmetric
data encryption, typically using 3-DES. This need to be closely
integrated in the IP stack.
The boards I'm doing now, is based on a Hi/fn 7951, with is designed for
VPM routers doing IPSec. It's supported in OpenBSD 2.9.
And btw, hardware beats software anytime. The fastest PC processor right
now is about the same speed as the slowest hardware....
The reason why I posted originally was the figure out who are working on
these things, as I remember seing a post some time ago about work being
done to import some of the IPSec work from OpenBSD.
The Kame project people might be the ones to talk to, but isn't there a
need for a FreeBSD specifec hardware driver anyway ?
I will be happy to donate hardware to the FreeBSD project.
Regards,
Soren
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 11:59:57 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from logatome.francenet.fr (logatome-2.francenet.fr [193.149.96.2])
by hub.freebsd.org (Postfix) with ESMTP id D010237B405
for <hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 11:59:53 -0700 (PDT)
(envelope-from e-masson@kisoft-services.com)
Received: from notbsdems.nantes.kisoft-services.com (pppA196.francenet.fr [193.149.100.106])
by logatome.francenet.fr (8.10.1/8.11.1) with ESMTP id f5OIxo020487;
Sun, 24 Jun 2001 20:59:51 +0200 (CEST)
Received: by notbsdems.nantes.kisoft-services.com (Postfix, from userid 1001)
id B026FE6971; Sun, 24 Jun 2001 20:52:32 +0200 (CEST)
To: Bsdguru@aol.com
Cc: hackers@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
References: <a2.15e39041.286781d5@aol.com>
From: Eric Masson <e-masson@kisoft-services.com>
In-Reply-To: <a2.15e39041.286781d5@aol.com> (Bsdguru@aol.com's message of "Sun, 24 Jun 2001 13:48:05 EDT")
X-Operating-System: FreeBSD 4.3-STABLE i386
Date: 24 Jun 2001 20:52:30 +0200
Message-ID: <86ithld829.fsf@notbsdems.nantes.kisoft-services.com>
Lines: 15
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.1 (Cuyahoga Valley)
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
>>>>> "Bsdguru" == Bsdguru <Bsdguru@aol.com> writes:
Bsdguru> I'd suggest doing a study on the benefits as well. With 1+Ghz
Bsdguru> processors, the advantages of doing this in hardware become
Bsdguru> less than in the old days.
Think about the embedded market, where 486 class processors are still
widely used (just like Soren's net4501)
Eric Masson
--
> Je cherche une methode pour verifier si le port 515 est a l'ecoute.
> Cette requete est a envoyer d'une station Solaris vers un serveur NT.
use Net::TCP; $object = new Net::TCP "playstation", 515;
$ok = $object->connect; -- SB in Guide du linuxien pervers
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 12: 5:22 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp6.port.ru (mx6.port.ru [194.67.23.42])
by hub.freebsd.org (Postfix) with ESMTP id 6198B37B405
for <freebsd-hackers@freebsd.org>; Sun, 24 Jun 2001 12:05:17 -0700 (PDT)
(envelope-from e-marketing@mail.ru)
Received: from bmstu-icn.bmstu.ru ([195.19.33.92] helo=localhost)
by smtp6.port.ru with smtp (Exim 3.14 #2)
id 15EFC7-000MjH-00
for freebsd-hackers@FreeBSD.org; Sun, 24 Jun 2001 23:05:16 +0400
X-Sender: e-marketing@mail.ru
Subject: Job Offer
From: e-marketing@mail.ru
To: "freebsd-hackers@FreeBSD.org" <freebsd-hackers@FreeBSD.org>
X-Priority: 1
Reply-To: e-marketing@mail.ru
Date: Sat, 23 Jun 2001 23:05:59 +0400
MIME-Version: 1.0
X-MailLibrary: Internet Mail Template 3.03, http://www.Princen-IT.nl/Clarion
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Message-Id: <E15EFC7-000MjH-00@smtp6.port.ru>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
=C7=E4=F0=E0=E2=F1=F2=E2=F3=E9=F2=E5!!
=C2=E0=F1 =EF=F0=E8=E2=E5=F2=F1=F2=E2=F3=E5=F2 e-Marketing Center.
=CF=F0=E5=E4=EB=E0=E3=E0=E5=EC =C2=E0=EC =F0=E5=E0=EB=FC=ED=FB=E5 =F1=EF=EE=
=F1=EE=E1=FB =E7=E0=F0=EE=E1=EE=F2=EA=E0.
=CA=EE=ED=F2=E5=ED=F2 =ED=E0=F8=E5=E3=EE =EF=F0=E5=E4=EB=EE=E6=E5=ED=E8=FF=
:
-Multi-Level-Marketing-=EF=F0=EE=E3=F0=E0=EC=EC=E0 =EC=E3=ED=EE=E2=E5=ED=ED=
=EE=E3=EE =E7=E0=F0=EE=E1=EE=F2=EA=E0
-=C2=EE=E7=EC=EE=E6=ED=EE=F1=F2=FC =EF=EE=EB=F3=F7=E5=ED=E8=FF =E1=E5=F1=EF=
=EB=E0=F2=ED=FB=F5 =EA=E0=F0=F2 Visa, American Express, Master Card
-=C1=E5=F1=EF=EB=E0=F2=ED=FB=E5 e-Marketing Books-=F2=E5=F5=ED=EE=EB=EE=E3=
=E8=FF =F0=E0=F1=EF=F0=EE=F1=F2=F0=E0=ED=E5=ED=E8=FF =E8 =EF=F0=EE=E4=E0=E6=
=E8
-=CB=F3=F7=F8=E8=E5 =EF=F0=EE=E3=F0=E0=EC=EC=FB =EF=F0=E8=E2=EB=E5=F7=E5=ED=
=E8=FF =F0=E5=F4=F4=E5=F0=E0=EB=EE=E2
-=CF=EE=E4=EF=E8=F1=EA=E0 =ED=E0 =F1=F0=E0=F1=F1=FB=EB=EA=F3 =EF=E8=F1=E5=
=EC =EE =E2=E8=F0=F2=F3=E0=EB=FC=ED=EE=EC =EC=E0=F0=EA=E5=F2=E8=ED=E3=E5-=
=E1=E5=F1=EF=EB=E0=F2=ED=FB=E5 =F0=E5=EA=EE=EC=E5=ED=E4=E0=F6=E8=E8
=E8 =F2.=E4.
=CF=EE=E4=F0=EE=E1=ED=E0=FF =E8=ED=F4=EE=F0=EC=E0=F6=E8=FF =ED=E0 =ED=E0=F8=
=E5=EC =F1=E0=E9=F2=E5
http://www.e-marketing.boom.ru
=D1 =F3=E2=E0=E6=E5=ED=E8=E5=EC,
e-Marketing Center
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
=D1=EE=EE=E1=F9=E5=ED=E8=E5 =F1=E3=E5=ED=E5=F0=E8=F0=EE=E2=E0=ED=EE =EF=EE=
=F7=F2=EE=E2=EE=E9 =EF=F0=EE=E3=F0=E0=EC=EC=EE=E9 =E4=EB=FF =F0=E0=F1=F1=FB=
=EB=EA=E8
=ED=EE=E2=EE=F1=F2=E5=E9 NewsMailer v1.3
Download: http://www.softtrade.ru/filez/emailer.zip
Please go to http://www.softtrade.ru=
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 12: 8:14 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from obsecurity.dyndns.org (adsl-63-207-60-13.dsl.lsan03.pacbell.net [63.207.60.13])
by hub.freebsd.org (Postfix) with ESMTP
id 1319F37B401; Sun, 24 Jun 2001 12:08:08 -0700 (PDT)
(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
id F293A66BF7; Sun, 24 Jun 2001 12:08:05 -0700 (PDT)
Date: Sun, 24 Jun 2001 12:08:05 -0700
From: Kris Kennaway <kris@obsecurity.org>
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: "Karsten W. Rohrbach" <karsten@rohrbach.de>,
Soren Kristensen <soren@soekris.com>, hackers@FreeBSD.ORG,
freebsd-security@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
Message-ID: <20010624120805.A67128@xor.obsecurity.org>
References: <3B33A891.EC712701@soekris.com> <xzpn16x7uao.fsf@flood.ping.uio.no> <20010624181007.C52432@mail.webmonster.de> <xzpd77t7st6.fsf@flood.ping.uio.no> <20010624183147.F52432@mail.webmonster.de> <xzpzoax6dfc.fsf@flood.ping.uio.no>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <xzpzoax6dfc.fsf@flood.ping.uio.no>; from des@ofug.org on Sun, Jun 24, 2001 at 06:38:31PM +0200
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
--2fHTh5uZTiUOsy+g
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Jun 24, 2001 at 06:38:31PM +0200, Dag-Erling Smorgrav wrote:
> "Karsten W. Rohrbach" <karsten@rohrbach.de> writes:
> > yup, exactly. to me it seems to be a major problem to get some unified
> > api out of openssl adressing fucnctions on the hardware -- i simply do
> > not know how other crypto chipsets do it, i just investigated the
> > rainbow board. they got a patch against openssl 0.9.5 i think, that
> > glues in the driver calls instead of standard lib functions.
>=20
> Can you dig out this patch for me? It would be a big win if the
> userland interface to Soren's hardware were compatible with Rainbow's
> driver.
I believe there is support in OpenSSL for this now (though not in the
version we currently have imported; it's the OpenSSL-engine branch
which supports hardware offload). Once there's a point to do so
(e.g. whatever relevant kernel support), I can import this into
FreeBSD.
Kris
--2fHTh5uZTiUOsy+g
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iD8DBQE7NjqUWry0BWjoQKURAg+fAJ4iaUF0+6iPxnB/HtTkX5sHVnH1cgCggmiu
t0KU2V7aB9tszwdu7tHmj8g=
=xAkK
-----END PGP SIGNATURE-----
--2fHTh5uZTiUOsy+g--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 12:25:57 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from hotmail.com (f228.law14.hotmail.com [64.4.21.228])
by hub.freebsd.org (Postfix) with ESMTP id 57C1737B409
for <hackers@FreeBSD.org>; Sun, 24 Jun 2001 12:25:46 -0700 (PDT)
(envelope-from list_tracker@hotmail.com)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
Sun, 24 Jun 2001 12:25:46 -0700
Received: from 151.197.205.152 by lw14fd.law14.hotmail.msn.com with HTTP; Sun, 24 Jun 2001 19:25:45 GMT
X-Originating-IP: [151.197.205.152]
From: "list tracker" <list_tracker@hotmail.com>
To: hackers@FreeBSD.org
Subject: trouble with 802.11 and kernel bridging....
Date: Sun, 24 Jun 2001 19:25:45 -0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F22861LEdyt3cew8k690000061e@hotmail.com>
X-OriginalArrivalTime: 24 Jun 2001 19:25:46.0227 (UTC) FILETIME=[77B17C30:01C0FCE3]
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
I have compiled options BRIDGE into my kernel. (also options IPFIREWALL,
and IPSTEALTH, but probably not important).
So I booted up with ep0 and wi0 in their slots, everything is great. I set
up bridging with:
sysctl -w net.link.ether.bridge=1
then made sure everything was wide open:
ipfw add 65500 allow all from any to any
then I opened up the wireless card. First, I named it "Laptop":
wicontrol -q "Laptop"
wicontrol -n "Laptop"
wicontrol -s "Laptop"
then I set it to Port Type = BSS (value 1)
then I set "Create IBSS" to "on" (wicontrol -c 1)
for good measure, made sure WEP was off: wicontrol -e 0
------
So, with it in this configuration, I plugged ep0 into my wired network, and
then told a friend to try to use my laptop as a base station. Their
computer "saw" me just fine...although it asked for a password to get on,
which was odd - I ended up having to `wicontrol -k 12345 1` and then have
him use that as his password, and then he got on just fine.
Two problems I would like help with:
1. He could not talk to the wired network - even though he was "on" my
wireless LAN and I had bridging properly set up on the machine. I feel as
if he should have just talked right through to the network on the other side
as if my laptop was not even there (being just the wireless access point and
nothing more)
2. (this is more minor) how come his client (macOS 9.1) thought it needed a
password to get onto my link ? I had just booted the machine, so all key
values were set to default of " ", and _further_, as you can see above, I
turned WEP off anyway ... I should not have had to set the 12345 key like I
did. It did work when I did that, but it is odd. And even when it did
work, it still didn't do the bridging I am talking about in question 1.
-----
A few ideas....first, perhaps I need to be in peer-to-peer mode to do this
instead of port type=BSS ?
However, I would really like this laptop to _act like_ a base station and
have multiple clients to connect to it simultaneously - it is my
understanding that if I want that I should do "port type=BSS" _and_ I should
do "Create IBSS=1 (yes)" ... should I not do this same thing for when I only
have one person connecting ? I would think not.
And yes, I did see in the man page where "create IBSS=1" is sometimes not
functional - is it totally broken, or should I at least be able to use it
like I am trying.. ?
any comments, help appreciated,
LT
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 13: 9:52 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from rover.village.org (rover.bsdimp.com [204.144.255.66])
by hub.freebsd.org (Postfix) with ESMTP
id BEA1537B405; Sun, 24 Jun 2001 13:09:48 -0700 (PDT)
(envelope-from imp@billy-club.village.org)
Received: from billy-club.village.org (billy-club.village.org [10.0.0.3])
by rover.village.org (8.11.3/8.11.3) with ESMTP id f5OK9l623836;
Sun, 24 Jun 2001 14:09:47 -0600 (MDT)
(envelope-from imp@billy-club.village.org)
Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.2/8.8.3) with ESMTP id f5OKAjl85824; Sun, 24 Jun 2001 14:10:45 -0600 (MDT)
Message-Id: <200106242010.f5OKAjl85824@billy-club.village.org>
To: hackers@FreeBSD.ORG
Subject: Re: Two Junior Kernel Hacker tasks..
Cc: John Baldwin <jhb@FreeBSD.ORG>
In-reply-to: Your message of "Sun, 24 Jun 2001 00:48:27 PDT."
<20010624004826.C27083@dragon.nuxi.com>
References: <20010624004826.C27083@dragon.nuxi.com> <XFMail.010622105201.jhb@FreeBSD.org> <200106221842.f5MIgaV58508@harmony.village.org>
Date: Sun, 24 Jun 2001 14:10:45 -0600
From: Warner Losh <imp@village.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In message <20010624004826.C27083@dragon.nuxi.com> hackers@FreeBSD.ORG writes:
: On Fri, Jun 22, 2001 at 12:42:36PM -0600, Warner Losh wrote:
: > Please use ${MACHINE}, not ${MACHINE_ARCH}. That way I can build
: > GENERIC for both i386 and pc98 at the same time without resorting to
: > the GENERIC98 hack I use now.
: ...
: > I'd be up for doing this, so long as I got to choose where to build
: > into :-)
: >
: > sys/arch/${MACHINE}/compile/FOO
: >
: > but that would start the arch bikeshed. I'd love to just do it.
:
:
: Which is another good reason for sys/compile/${MACHINE}/FOO
: Otherwise where DOES the pc98 kernel builds happen? Under the
: non-existant sys/pc98/ ?
sys/pc98 does exist.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 13:10:25 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from rover.village.org (rover.bsdimp.com [204.144.255.66])
by hub.freebsd.org (Postfix) with ESMTP
id BE2CF37B401; Sun, 24 Jun 2001 13:10:22 -0700 (PDT)
(envelope-from imp@billy-club.village.org)
Received: from billy-club.village.org (billy-club.village.org [10.0.0.3])
by rover.village.org (8.11.3/8.11.3) with ESMTP id f5OKAL623846;
Sun, 24 Jun 2001 14:10:21 -0600 (MDT)
(envelope-from imp@billy-club.village.org)
Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.2/8.8.3) with ESMTP id f5OKBJl85837; Sun, 24 Jun 2001 14:11:19 -0600 (MDT)
Message-Id: <200106242011.f5OKBJl85837@billy-club.village.org>
To: freebsd-hackers@FreeBSD.org
Subject: Re: Two Junior Kernel Hacker tasks..
Cc: John Baldwin <jhb@FreeBSD.org>
In-reply-to: Your message of "Sun, 24 Jun 2001 00:52:38 PDT."
<20010624005238.D27083@dragon.nuxi.com>
References: <20010624005238.D27083@dragon.nuxi.com> <200106221842.f5MIgaV58508@harmony.village.org> <XFMail.010622121136.jhb@FreeBSD.org>
Date: Sun, 24 Jun 2001 14:11:19 -0600
From: Warner Losh <imp@village.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In message <20010624005238.D27083@dragon.nuxi.com> freebsd-hackers@FreeBSD.org writes:
: > Sure, sounds good. Actually, with mjacob's suggestion, I would go with
: > sys/${MACHINE}/compile/FOO
:
: pc98 and powerpc variations will make this ugly.
No they won't. pc98 is the reason that this *MAKES* sense.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 13:32:11 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
by hub.freebsd.org (Postfix) with ESMTP
id C287437B401; Sun, 24 Jun 2001 13:32:08 -0700 (PDT)
(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1])
by harmony.village.org (8.11.3/8.11.1) with ESMTP id f5OKVwV91130;
Sun, 24 Jun 2001 14:32:06 -0600 (MDT)
(envelope-from imp@harmony.village.org)
Message-Id: <200106242032.f5OKVwV91130@harmony.village.org>
To: Dima Dorfman <dima@unixfreak.org>
Subject: Re: "include" directive in config(8) (was: Two Junior Kernel Hacker tasks..)
Cc: John Baldwin <jhb@FreeBSD.ORG>, hackers@FreeBSD.ORG,
peter@FreeBSD.ORG
In-reply-to: Your message of "Sat, 23 Jun 2001 23:20:02 PDT."
<20010624062002.1DC013E28@bazooka.unixfreak.org>
References: <20010624062002.1DC013E28@bazooka.unixfreak.org>
Date: Sun, 24 Jun 2001 14:31:58 -0600
From: Warner Losh <imp@harmony.village.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Is there a way to "undef" an option?
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 13:33:37 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
by hub.freebsd.org (Postfix) with ESMTP
id CAEAC37B401; Sun, 24 Jun 2001 13:33:34 -0700 (PDT)
(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1])
by harmony.village.org (8.11.3/8.11.1) with ESMTP id f5OKXXV91156;
Sun, 24 Jun 2001 14:33:33 -0600 (MDT)
(envelope-from imp@harmony.village.org)
Message-Id: <200106242033.f5OKXXV91156@harmony.village.org>
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: Two Junior Kernel Hacker tasks..
Cc: Matthew Jacob <mjacob@feral.com>, John Baldwin <jhb@FreeBSD.ORG>
In-reply-to: Your message of "Sun, 24 Jun 2001 00:43:15 PDT."
<20010624004315.A27083@dragon.nuxi.com>
References: <20010624004315.A27083@dragon.nuxi.com> <XFMail.010622105201.jhb@FreeBSD.org> <20010622104940.P20923-100000@wonky.feral.com>
Date: Sun, 24 Jun 2001 14:33:33 -0600
From: Warner Losh <imp@harmony.village.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In message <20010624004315.A27083@dragon.nuxi.com> freebsd-hackers@FreeBSD.ORG writes:
: On Fri, Jun 22, 2001 at 10:50:00AM -0700, Matthew Jacob wrote:
: > Why can't we do it like NetBSD and have
: >
: > sys/${MACHINE_ARCH}/compile?
:
: It makes it harder to make src/sys/compile a single simple symlink to
: writable storage.
Generally, most people will have at most one or two architectures, so
the symlink isn't that hard to do. Also, since most people wanting to
do this could also just specify the command line option to config.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 13:36:15 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
by hub.freebsd.org (Postfix) with ESMTP
id 5098537B405; Sun, 24 Jun 2001 13:36:12 -0700 (PDT)
(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1])
by harmony.village.org (8.11.3/8.11.1) with ESMTP id f5OKaBV91200;
Sun, 24 Jun 2001 14:36:11 -0600 (MDT)
(envelope-from imp@harmony.village.org)
Message-Id: <200106242036.f5OKaBV91200@harmony.village.org>
To: hackers@FreeBSD.ORG
Subject: Re: Two Junior Kernel Hacker tasks..
Cc: John Baldwin <jhb@FreeBSD.ORG>
In-reply-to: Your message of "Sun, 24 Jun 2001 00:48:27 PDT."
<20010624004826.C27083@dragon.nuxi.com>
References: <20010624004826.C27083@dragon.nuxi.com> <XFMail.010622105201.jhb@FreeBSD.org> <200106221842.f5MIgaV58508@harmony.village.org>
Date: Sun, 24 Jun 2001 14:36:11 -0600
From: Warner Losh <imp@harmony.village.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In message <20010624004826.C27083@dragon.nuxi.com> hackers@FreeBSD.ORG writes:
: Which is another good reason for sys/compile/${MACHINE}/FOO
: Otherwise where DOES the pc98 kernel builds happen? Under the
: non-existant sys/pc98/ ?
David, a simple ls to sys/pc98 shows that it is populated with lots of
files.
% ls ~/FreeBSD/src/sys/pc98
CVS apm conf i386 pc98
So that's not an argument against it.
: > With powerpc, we are going to have a lot of different ports ala
: > i386/pc98 (that have the same MAHINCE_ARCH, but different MACHINE) if
: > NetBSD is any indication.
:
: Even more data that IMHO makes sys/compile/${MACHINE}/FOO make more
: sense.
Actually, I don't think it argues in favor of
sys/compile/${MACHINE}/FOO at all. *ALL* ${MACHINE} ports must have a
sys/${MACHINE} in the current scheme. That's by definition.
I also think that as we get more and more ports for power pc, we'll
see more people that need/want to do cross compiling or having one
tree for multiple ports.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 13:41:17 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138])
by hub.freebsd.org (Postfix) with ESMTP
id 589AC37B401; Sun, 24 Jun 2001 13:41:14 -0700 (PDT)
(envelope-from dima@unixfreak.org)
Received: from hornet.unixfreak.org (hornet [63.198.170.140])
by bazooka.unixfreak.org (Postfix) with ESMTP
id F2B913E28; Sun, 24 Jun 2001 13:41:13 -0700 (PDT)
To: Warner Losh <imp@harmony.village.org>
Cc: John Baldwin <jhb@FreeBSD.ORG>, hackers@FreeBSD.ORG,
peter@FreeBSD.ORG
Subject: Re: "include" directive in config(8) (was: Two Junior Kernel Hacker tasks..)
In-Reply-To: <200106242032.f5OKVwV91130@harmony.village.org>; from imp@harmony.village.org on "Sun, 24 Jun 2001 14:31:58 -0600"
Date: Sun, 24 Jun 2001 13:41:13 -0700
From: Dima Dorfman <dima@unixfreak.org>
Message-Id: <20010624204114.F2B913E28@bazooka.unixfreak.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Warner Losh <imp@harmony.village.org> writes:
> Is there a way to "undef" an option?
I thought about this, too. Right now there isn't a way to do that,
and neither OpenBSD nor NetBSD have one AFAIK. That said, I think it
would be trivial to implement. The list of options and devices is a
simple linked list (mind you, it's a home-grown one, not queue(3)); it
shouldn't be too hard to implement "unoption" and "undevice"
directives.
Dima Dorfman
dima@unixfreak.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 14:22:10 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2])
by hub.freebsd.org (Postfix) with SMTP id 6FE6137B406
for <hackers@freebsd.org>; Sun, 24 Jun 2001 14:22:06 -0700 (PDT)
(envelope-from reichert@natto.numachi.com)
Received: (qmail 4797 invoked by uid 3001); 24 Jun 2001 21:22:05 -0000
Received: from natto.numachi.com (198.175.254.216)
by numachi.numachi.com with SMTP; 24 Jun 2001 21:22:05 -0000
Received: (qmail 64333 invoked by uid 1001); 24 Jun 2001 21:22:05 -0000
Date: Sun, 24 Jun 2001 17:22:05 -0400
From: Brian Reichert <reichert@numachi.com>
To: hackers@freebsd.org
Subject: auto-detect an inserted audio cd?
Message-ID: <20010624172205.K40337@numachi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
I poked though the archives, but didn't see anything that pointed
to this: is there proscribed method for auto-detecting the
insertion/ejection of an audio CD?
I'm hoping for some daemon that provides notification events, rather
than me having to write my on C code. :/
I'm looking for something like 'vold', but for BSD.
Any ideas?
--
Brian 'you Bastard' Reichert <reichert@numachi.com>
37 Crystal Ave. #303 Daytime number: (603) 434-6842
Derry NH 03038-1713 USA Intel architecture: the left-hand path
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 14:52:59 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66])
by hub.freebsd.org (Postfix) with ESMTP id 8430337B405
for <freebsd-hackers@freebsd.org>; Sun, 24 Jun 2001 14:52:56 -0700 (PDT)
(envelope-from dgilbert@office.tor.velocet.net)
Received: from office.tor.velocet.net (trooper.velocet.net [204.138.45.2])
by sabre.velocet.net (Postfix) with ESMTP id C5ABF137F33
for <freebsd-hackers@freebsd.org>; Sun, 24 Jun 2001 17:52:55 -0400 (EDT)
Received: (from dgilbert@localhost)
by office.tor.velocet.net (8.11.2/8.9.3) id f5OLqtp67210;
Sun, 24 Jun 2001 17:52:55 -0400 (EDT)
(envelope-from dgilbert)
From: David Gilbert <dgilbert@velocet.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15158.24886.958193.121109@trooper.velocet.net>
Date: Sun, 24 Jun 2001 17:52:54 -0400
To: freebsd-hackers@freebsd.org
Subject: DVD IOCTLs on IDE?
X-Mailer: VM 6.92 under 20.4 "Emerald" 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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Has anyone looked at DVD ioctls on IDE? It took me some time to
realize (even after reading the source a couple of times) that the
current DVD ioctls only apply to SCSI.
Dave.
--
============================================================================
|David Gilbert, Velocet Communications. | Two things can only be |
|Mail: dgilbert@velocet.net | equal if and only if they |
|http://www.velocet.net/~dgilbert | are precisely opposite. |
=========================================================GLO================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 15: 0:13 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2])
by hub.freebsd.org (Postfix) with SMTP id 4072037B401
for <freebsd-hackers@freebsd.org>; Sun, 24 Jun 2001 15:00:09 -0700 (PDT)
(envelope-from reichert@natto.numachi.com)
Received: (qmail 4985 invoked by uid 3001); 24 Jun 2001 22:00:07 -0000
Received: from natto.numachi.com (198.175.254.216)
by numachi.numachi.com with SMTP; 24 Jun 2001 22:00:07 -0000
Received: (qmail 64495 invoked by uid 1001); 24 Jun 2001 22:00:07 -0000
Date: Sun, 24 Jun 2001 18:00:07 -0400
From: Brian Reichert <reichert@numachi.com>
To: David Gilbert <dgilbert@velocet.ca>
Cc: freebsd-hackers@freebsd.org
Subject: Re: DVD IOCTLs on IDE?
Message-ID: <20010624180007.Z23601@numachi.com>
References: <15158.24886.958193.121109@trooper.velocet.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <15158.24886.958193.121109@trooper.velocet.net>; from dgilbert@velocet.ca on Sun, Jun 24, 2001 at 05:52:54PM -0400
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Sun, Jun 24, 2001 at 05:52:54PM -0400, David Gilbert wrote:
> Has anyone looked at DVD ioctls on IDE? It took me some time to
> realize (even after reading the source a couple of times) that the
> current DVD ioctls only apply to SCSI.
'Looked at'? What do you mean? People have been making use of
IDE DVD-ROM drives for quite a while now...
>
> Dave.
>
--
Brian 'you Bastard' Reichert <reichert@numachi.com>
37 Crystal Ave. #303 Daytime number: (603) 434-6842
Derry NH 03038-1713 USA Intel architecture: the left-hand path
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 15: 5:45 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.noos.fr (descartes.noos.net [212.198.2.74])
by hub.freebsd.org (Postfix) with ESMTP id 26DEB37B405
for <hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 15:05:42 -0700 (PDT)
(envelope-from clefevre@redirect.to)
Received: (qmail 8350412 invoked by uid 0); 24 Jun 2001 22:05:38 -0000
Received: from unknown (HELO gits.dyndns.org) ([212.198.231.187]) (envelope-sender <clefevre@redirect.to>)
by 212.198.2.74 (qmail-ldap-1.03) with SMTP
for <imp@harmony.village.org>; 24 Jun 2001 22:05:38 -0000
Received: (from root@localhost)
by gits.dyndns.org (8.11.4/8.11.4) id f5OM5bU86275;
Mon, 25 Jun 2001 00:05:37 +0200 (CEST)
(envelope-from clefevre@redirect.to)
To: Dima Dorfman <dima@unixfreak.org>
Cc: Warner Losh <imp@harmony.village.org>,
John Baldwin <jhb@FreeBSD.ORG>, hackers@FreeBSD.ORG,
peter@FreeBSD.ORG
Subject: Re: "include" directive in config(8) (was: Two Junior Kernel Hacker tasks..)
References: <20010624204114.F2B913E28@bazooka.unixfreak.org>
X-Face: V|+c;4!|B?E%BE^{E6);aI.[<<r#uCVjK"~Ke!@0vxS/.,wki/c|uVnNV!BA-_gY2sfoGc3
f{#/$PT>97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C
la*Zv'5NA,=963bM%J^o]C
Reply-To: Cyrille Lefevre <clefevre@redirect.to>
In-Reply-To: <20010624204114.F2B913E28@bazooka.unixfreak.org>
Mail-Copies-To: never
From: Cyrille Lefevre <clefevre-lists@noos.fr>
Date: 25 Jun 2001 00:05:36 +0200
Message-ID: <66dlbkjz.fsf@gits.dyndns.org>
Lines: 18
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley)
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Dima Dorfman <dima@unixfreak.org> writes:
> Warner Losh <imp@harmony.village.org> writes:
> > Is there a way to "undef" an option?
>
> I thought about this, too. Right now there isn't a way to do that,
> and neither OpenBSD nor NetBSD have one AFAIK. That said, I think it
> would be trivial to implement. The list of options and devices is a
> simple linked list (mind you, it's a home-grown one, not queue(3)); it
> shouldn't be too hard to implement "unoption" and "undevice"
> directives.
how about "undef options XXX" and "undef device XXX", etc. ?
Cyrille.
--
home: mailto:clefevre@redirect.to UNIX is user-friendly; it's just particular
work: mailto:Cyrille.Lefevre@edf.fr about who it chooses to be friends with.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 15: 6:24 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from hotmail.com (law2-f5.hotmail.com [216.32.181.5])
by hub.freebsd.org (Postfix) with ESMTP id B228737B406
for <freebsd-hackers@freebsd.org>; Sun, 24 Jun 2001 15:06:20 -0700 (PDT)
(envelope-from wgshi@hotmail.com)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
Sun, 24 Jun 2001 15:06:20 -0700
Received: from 129.128.4.121 by lw2fd.hotmail.msn.com with HTTP; Sun, 24 Jun 2001 22:06:20 GMT
X-Originating-IP: [129.128.4.121]
From: "Weiguang Shi" <wgshi@hotmail.com>
To: freebsd-hackers@freebsd.org
Subject: help on mounting linux partition
Date: Sun, 24 Jun 2001 22:06:20
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <LAW2-F5UpuabjKoMFYs0000e1d5@hotmail.com>
X-OriginalArrivalTime: 24 Jun 2001 22:06:20.0490 (UTC) FILETIME=[E6295AA0:01C0FCF9]
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi,
I've sent this to freebsd-questions but no luck yet.
I am using freebsd 4.0. and failed to mount a Linux partition on
the second hard disk. Could you please shed some light?
Thanks very much
Weiguang
==================================================================
bash-2.04# fdisk /dev/ad1
******* Working on device /dev/ad1 *******
parameters extracted from in-core disklabel are:
cylinders=1653 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1653 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 131,(Linux filesystem)
start 63, size 8225217 (4016 Meg), flag 0
beg: cyl 0/ sector 1/ head 1;
end: cyl 511/ sector 63/ head 254
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
bash-2.04# /bin/ls /dev/ad1*
/dev/ad1 /dev/ad1c /dev/ad1f /dev/ad1s1 /dev/ad1s4
/dev/ad1a /dev/ad1d /dev/ad1g /dev/ad1s2
/dev/ad1b /dev/ad1e /dev/ad1h /dev/ad1s3
bash-2.04# mount -t ext2fs /dev/ad1s1 /mnt/work
ext2fs: /dev/ad1s1: Invalid argument
bash-2.04# uname -a
FreeBSD newby-nfr.cs.ualberta.ca 4.0-RELEASE FreeBSD 4.0-RELEASE #1: Tue May
i386 unknown
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 17:12:36 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66])
by hub.freebsd.org (Postfix) with ESMTP id 52F7237B405
for <freebsd-hackers@freebsd.org>; Sun, 24 Jun 2001 17:12:33 -0700 (PDT)
(envelope-from dgilbert@office.tor.velocet.net)
Received: from office.tor.velocet.net (trooper.velocet.net [204.138.45.2])
by sabre.velocet.net (Postfix) with ESMTP
id 9DCDF137F32; Sun, 24 Jun 2001 20:12:29 -0400 (EDT)
Received: (from dgilbert@localhost)
by office.tor.velocet.net (8.11.2/8.9.3) id f5P0CTR87319;
Sun, 24 Jun 2001 20:12:29 -0400 (EDT)
(envelope-from dgilbert)
From: David Gilbert <dgilbert@velocet.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15158.33260.976403.782709@trooper.velocet.net>
Date: Sun, 24 Jun 2001 20:12:28 -0400
To: Brian Reichert <reichert@numachi.com>
Cc: David Gilbert <dgilbert@velocet.ca>, freebsd-hackers@freebsd.org
Subject: Re: DVD IOCTLs on IDE?
In-Reply-To: <20010624180007.Z23601@numachi.com>
References: <15158.24886.958193.121109@trooper.velocet.net>
<20010624180007.Z23601@numachi.com>
X-Mailer: VM 6.92 under 20.4 "Emerald" 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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
>>>>> "Brian" == Brian Reichert <reichert@numachi.com> writes:
Brian> On Sun, Jun 24, 2001 at 05:52:54PM -0400, David Gilbert wrote:
>> Has anyone looked at DVD ioctls on IDE? It took me some time to
>> realize (even after reading the source a couple of times) that the
>> current DVD ioctls only apply to SCSI.
Brian> 'Looked at'? What do you mean? People have been making use of
Brian> IDE DVD-ROM drives for quite a while now...
From the dvdio.h CVS comment:
MFC, DVD ioctls.
scsi_cd.c rev 1.36
scsi_cd.h rev 1.4
dvdio.h rev 1.3
... One issue is that dvdio.h seems to be missing structure items that
are required by dvd software. I have attempted to compile livid (oms)
and videolan ... both which at least talk about working on BSD. Livid
refuses to compile because dvdio.h is missing certain structure
members.
videolan compiles and runs, but refuses to recognise a DVD in the
player (I've tried several DVDs). My IDE DVD player probes as:
acd0: DVD-ROM <TOSHIBA DVD-ROM SD-M1502> at ata2-master using PIO4
... and can successfully mount a DVD-ROM... they just don't play with
any of the software I've been able to find. Most recently, I
downloaded a copy of another package mentioned on /., but it dies
looking for libdl.so ... which I assume is a stupid linux dependancy,
so I havn't been chasing it.
Dave.
--
============================================================================
|David Gilbert, Velocet Communications. | Two things can only be |
|Mail: dgilbert@velocet.net | equal if and only if they |
|http://www.velocet.net/~dgilbert | are precisely opposite. |
=========================================================GLO================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 17:48:59 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailout1.nyroc.rr.com (mailout1-0.nyroc.rr.com [24.92.226.81])
by hub.freebsd.org (Postfix) with ESMTP id C248A37B401
for <freebsd-hackers@freebsd.org>; Sun, 24 Jun 2001 17:48:56 -0700 (PDT)
(envelope-from James_Bond_79@yahoo.com)
Received: from halstead007 (roc-24-169-196-57.rochester.rr.com [24.169.196.57])
by mailout1.nyroc.rr.com (8.11.2/RoadRunner 1.03) with SMTP id f5P0lRf25379;
Sun, 24 Jun 2001 20:47:28 -0400 (EDT)
Content-Type: text/plain;
charset="iso-8859-1"
From: James Halstead <James_Bond_79@yahoo.com>
To: David Gilbert <dgilbert@velocet.ca>,
Brian Reichert <reichert@numachi.com>
Subject: Re: DVD IOCTLs on IDE?
Date: Sun, 24 Jun 2001 20:55:56 -0400
X-Mailer: KMail [version 1.2]
Cc: freebsd-hackers@freebsd.org
References: <15158.24886.958193.121109@trooper.velocet.net> <20010624180007.Z23601@numachi.com> <15158.33260.976403.782709@trooper.velocet.net>
In-Reply-To: <15158.33260.976403.782709@trooper.velocet.net>
MIME-Version: 1.0
Message-Id: <01062420555600.00449@halstead007>
Content-Transfer-Encoding: 8bit
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Sunday 24 June 2001 20:12, David Gilbert wrote:
> ... One issue is that dvdio.h seems to be missing structure items that
> are required by dvd software. I have attempted to compile livid (oms)
> and videolan ... both which at least talk about working on BSD. Livid
> refuses to compile because dvdio.h is missing certain structure
> members.
>
> videolan compiles and runs, but refuses to recognise a DVD in the
> player (I've tried several DVDs). My IDE DVD player probes as:
>
I have also noticed that the FreeBSD dvdio.h is different then the NetBSD and
Linux versions (possibly the OpenBSD as well) Is there any reason that linux
and the other *bsd's seem to have one setup and ours is different?
I have had moderate success using xine with captiancss, but it is rather
crashprone. I have also been able to get the libcss from livid to compile
using patches i found on a list somewhere, but it never seemed to work for me.
Does anbody know of a good, stable way to play dvd movies on FreeBSD?
> Dave.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 19:15: 5 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9])
by hub.freebsd.org (Postfix) with ESMTP
id 852CB37B40A; Sun, 24 Jun 2001 19:14:59 -0700 (PDT)
(envelope-from jlemon@flugsvamp.com)
Received: (from jlemon@localhost)
by prism.flugsvamp.com (8.11.0/8.11.0) id f5P2DS676781;
Sun, 24 Jun 2001 21:13:28 -0500 (CDT)
(envelope-from jlemon)
Date: Sun, 24 Jun 2001 21:13:28 -0500 (CDT)
From: Jonathan Lemon <jlemon@flugsvamp.com>
Message-Id: <200106250213.f5P2DS676781@prism.flugsvamp.com>
To: soren@soekris.com, hackers@freebsd.org, jlemon@freebsd.org
Subject: Re: Status of encryption hardware support in FreeBSD
X-Newsgroups: local.mail.freebsd-hackers
In-Reply-To: <local.mail.freebsd-hackers/3B363713.2849219@soekris.com>
References: <local.mail.freebsd-hackers/3B33A891.EC712701@soekris.com>
<local.mail.freebsd-hackers/xzpn16x7uao.fsf@flood.ping.uio.no>
<local.mail.freebsd-hackers/20010624181007.C52432@mail.webmonster.de>
<local.mail.freebsd-hackers/xzpd77t7st6.fsf@flood.ping.uio.no>
<local.mail.freebsd-hackers/20010624183147.F52432@mail.webmonster.de>
<local.mail.freebsd-hackers/xzpzoax6dfc.fsf@flood.ping.uio.no>
<local.mail.freebsd-hackers/20010624201456.A57877@mail.webmonster.de>
Organization:
Cc:
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In article <local.mail.freebsd-hackers/3B363713.2849219@soekris.com> you write:
>Hi,
>
>Thanks for the responses so far. First, let me say that I'm a hardware
>guy, and don't know all the details of FreeBSD's network stack.
>
>There is two common kind of hardware encryption acceleration, and I
>think they're being mixed a little here.
>
>SSL is for secure web access, and the main need is for Public Key
>generating. This don't really have anything to do with the IP stack.
>Afaik, OpenSSL is more like a extension to the web server software.
>
>IPSec is for secure communication, and the main need is for symmetric
>data encryption, typically using 3-DES. This need to be closely
>integrated in the IP stack.
>
>The boards I'm doing now, is based on a Hi/fn 7951, with is designed for
>VPM routers doing IPSec. It's supported in OpenBSD 2.9.
>
>And btw, hardware beats software anytime. The fastest PC processor right
>now is about the same speed as the slowest hardware....
>
>The reason why I posted originally was the figure out who are working on
>these things, as I remember seing a post some time ago about work being
>done to import some of the IPSec work from OpenBSD.
>The Kame project people might be the ones to talk to, but isn't there a
>need for a FreeBSD specifec hardware driver anyway ?
Yes; the hardware will need a specific driver for the board. Also,
the interface into the IP stack needs to be defined as well, this
depends on what capabilities the board can provide. ISTR that various
boards have different requirements from the stack, and one item that
I'm focusing on is to try to work out an approach that will work for
various chips on the market.
Hopefully, this can be done in much the same way as the TCP/UDP/IP hardware
checksum offload code that I did earlier.
As such, the more information I get about the the interfaces the hardware
requires the better. Of course, in order to write a driver for FreeBSD,
I'd need complete programming details as well.
>I will be happy to donate hardware to the FreeBSD project.
I'll contact you offline about this.
--
Jonathan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 19:27:16 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from hotmail.com (f156.law14.hotmail.com [64.4.21.156])
by hub.freebsd.org (Postfix) with ESMTP id 2532E37B406
for <hackers@freebsd.org>; Sun, 24 Jun 2001 19:27:13 -0700 (PDT)
(envelope-from list_tracker@hotmail.com)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
Sun, 24 Jun 2001 19:27:13 -0700
Received: from 138.88.44.98 by lw14fd.law14.hotmail.msn.com with HTTP; Mon, 25 Jun 2001 02:27:12 GMT
X-Originating-IP: [138.88.44.98]
From: "list tracker" <list_tracker@hotmail.com>
To: ambrisko@ambrisko.com
Cc: hackers@freebsd.org
Subject: Re: trouble with 802.11 and kernel bridging (more)
Date: Mon, 25 Jun 2001 02:27:12 -0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F156NH2cv0aGltFBNlJ00001ece@hotmail.com>
X-OriginalArrivalTime: 25 Jun 2001 02:27:13.0015 (UTC) FILETIME=[57CB2070:01C0FD1E]
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
ok, thank you! This explains my inability to perform bridging like I
expected to....
>I've been told the "wi" driver can't do bridging. The Cisco/Aironet
>"an" driver can. Patches were submitted so you can do this. They are
>in the tree.
If I want to turn a PC into a full-blown "access point", should I set
wicontrol to peer to peer (3) or BSS (1) ?
Secondly, should I turn on the "create BSS" (I am almost positive I should)
- but this leads me to:
thirdly, are the fixes that allow wi to "create BSS" also "in the tree" ?
or does the man page warning that it does not work still valid ?
(I was using 4.3-RELEASE, btw)
thanks.
LT
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 19:59:18 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.tgd.net (rand.tgd.net [64.81.67.117])
by hub.freebsd.org (Postfix) with SMTP id 3964F37B405
for <freebsd-hackers@freebsd.org>; Sun, 24 Jun 2001 19:59:16 -0700 (PDT)
(envelope-from sean@mailhost.tgd.net)
Received: (qmail 55722 invoked by uid 1001); 25 Jun 2001 02:59:10 -0000
Date: Sun, 24 Jun 2001 19:59:10 -0700
From: Sean Chittenden <sean-freebsd-hackers@chittenden.org>
To: freebsd-hackers@freebsd.org
Subject: What happens to a connection between a select and accept...
Message-ID: <20010624195910.A44590@rand.tgd.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl"
Content-Disposition: inline
X-PGP-Key: 0x1EDDFAAD
X-PGP-Fingerprint: C665 A17F 9A56 286C 5CFB 1DEA 9F4F 5CEF 1EDD FAAD
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
--BXVAT5kNtrzKuDFl
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Quick question. Anyone know how gracefully the kernel handles a
socket connection that is killed by the client between a select and
accept call? I don't expect any problems, but I know there was a race
condition in Linux that caused all kinds of nasty bugs and problems.
Granted it's like comparing apples and oranges but, I'm
wondering if anyone has any words of wisdom regarding this. Debugging=20
this kind of a race condition isn't exactly my idea of a good time. ;~) =
=20
-sc
--=20
Sean Chittenden
--BXVAT5kNtrzKuDFl
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Comment: Sean Chittenden <sean@chittenden.org>
iEYEARECAAYFAjs2qN0ACgkQn09c7x7d+q2fgACeJ8m/j3VaI1q4upssjE44Tbxd
ikcAoMDdWzix9flPakc0IfbxnAUJGjYR
=shu/
-----END PGP SIGNATURE-----
--BXVAT5kNtrzKuDFl--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 22:27:34 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9])
by hub.freebsd.org (Postfix) with ESMTP id 71D1237B405
for <hackers@freebsd.org>; Sun, 24 Jun 2001 22:27:31 -0700 (PDT)
(envelope-from julian@elischer.org)
Received: from elischer.org (InterJet.elischer.org [192.168.1.1])
by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA77555;
Sun, 24 Jun 2001 23:53:37 -0700 (PDT)
Message-ID: <3B36C99B.8B64F299@elischer.org>
Date: Sun, 24 Jun 2001 22:18:19 -0700
From: Julian Elischer <julian@elischer.org>
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en, hu
MIME-Version: 1.0
To: list tracker <list_tracker@hotmail.com>
Cc: ambrisko@ambrisko.com, hackers@freebsd.org
Subject: Re: trouble with 802.11 and kernel bridging (more)
References: <F156NH2cv0aGltFBNlJ00001ece@hotmail.com>
Content-Type: text/plain; charset=iso-8859-2
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
list tracker wrote:
>
> ok, thank you! This explains my inability to perform bridging like I
> expected to....
>
> >I've been told the "wi" driver can't do bridging. The Cisco/Aironet
> >"an" driver can. Patches were submitted so you can do this. They are
> >in the tree.
>
> If I want to turn a PC into a full-blown "access point", should I set
> wicontrol to peer to peer (3) or BSS (1) ?
AP functions require the card to act TOTALLY DIFFERENTLY.
It requires diferent firmware in the card.
There is in development (it was shown atthe FreeBSD user's group this month)
a version of the wi driver that loads in the AP firmware and runs the card
as an AP but it is not completed yet.
>
> Secondly, should I turn on the "create BSS" (I am almost positive I should)
> - but this leads me to:
>
> thirdly, are the fixes that allow wi to "create BSS" also "in the tree" ?
> or does the man page warning that it does not work still valid ?
>
> (I was using 4.3-RELEASE, btw)
>
> thanks.
>
> LT
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
--
+------------------------------------+ ______ _ __
| __--_|\ Julian Elischer | \ U \/ / hard at work in
| / \ julian@elischer.org +------>x USA \ a very strange
| ( OZ ) \___ ___ | country !
+- X_.---._/ presently in San Francisco \_/ \\
v
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 22:32:52 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4])
by hub.freebsd.org (Postfix) with ESMTP id 2A71537B405
for <hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 22:32:48 -0700 (PDT)
(envelope-from netch@iv.nn.kiev.ua)
Received: (from uucp@localhost)
by segfault.kiev.ua (8) with UUCP id IMO23775;
Mon, 25 Jun 2001 08:32:36 +0300 (EEST)
(envelope-from netch@iv.nn.kiev.ua)
Received: (from netch@localhost)
by iv.nn.kiev.ua (8.11.4/8.11.4) id f5P5RZt00930;
Mon, 25 Jun 2001 08:27:35 +0300 (EEST)
(envelope-from netch)
Date: Mon, 25 Jun 2001 08:27:35 +0300
From: Valentin Nechayev <netch@iv.nn.kiev.ua>
To: Cyrille Lefevre <clefevre@redirect.to>
Cc: hackers@FreeBSD.ORG
Subject: Re: "include" directive in config(8) (was: Two Junior Kernel Hacker tasks..)
Message-ID: <20010625082735.A909@iv.nn.kiev.ua>
References: <20010624204114.F2B913E28@bazooka.unixfreak.org> <66dlbkjz.fsf@gits.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <66dlbkjz.fsf@gits.dyndns.org>; from clefevre-lists@noos.fr on Mon, Jun 25, 2001 at 12:05:36AM +0200
X-42: On
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Mon, Jun 25, 2001 at 00:05:36, clefevre-lists (Cyrille Lefevre) wrote about "Re: "include" directive in config(8) (was: Two Junior Kernel Hacker tasks..)":
> how about "undef options XXX" and "undef device XXX", etc. ?
s/undef/no/
I like Cisco style ;)))
/netch
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 23: 3:17 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
by hub.freebsd.org (Postfix) with ESMTP
id EA1FE37B401; Sun, 24 Jun 2001 23:03:12 -0700 (PDT)
(envelope-from des@ofug.org)
Received: (from des@localhost)
by flood.ping.uio.no (8.9.3/8.9.3) id IAA85599;
Mon, 25 Jun 2001 08:03:07 +0200 (CEST)
(envelope-from des@ofug.org)
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: Soren Kristensen <soren@soekris.com>
Cc: "Karsten W. Rohrbach" <karsten@rohrbach.de>, hackers@FreeBSD.ORG,
freebsd-security@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
References: <3B33A891.EC712701@soekris.com>
<xzpn16x7uao.fsf@flood.ping.uio.no>
<20010624181007.C52432@mail.webmonster.de>
<xzpd77t7st6.fsf@flood.ping.uio.no>
<20010624183147.F52432@mail.webmonster.de>
<xzpzoax6dfc.fsf@flood.ping.uio.no>
<20010624201456.A57877@mail.webmonster.de>
<3B363713.2849219@soekris.com>
From: Dag-Erling Smorgrav <des@ofug.org>
Date: 25 Jun 2001 08:03:07 +0200
In-Reply-To: <3B363713.2849219@soekris.com>
Message-ID: <xzp66dl14h0.fsf@flood.ping.uio.no>
Lines: 10
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Soren Kristensen <soren@soekris.com> writes:
> SSL is for secure web access, and the main need is for Public Key
> generating. This don't really have anything to do with the IP stack.
> Afaik, OpenSSL is more like a extension to the web server software.
Try 'man openssl', or just 'openssl -help'. You'll be surprised...
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 Sun Jun 24 23: 5: 6 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4])
by hub.freebsd.org (Postfix) with ESMTP id D4EC137B406
for <freebsd-hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 23:04:59 -0700 (PDT)
(envelope-from netch@iv.nn.kiev.ua)
Received: (from uucp@localhost)
by segfault.kiev.ua (8) with UUCP id JBV26520;
Mon, 25 Jun 2001 09:04:47 +0300 (EEST)
(envelope-from netch@iv.nn.kiev.ua)
Received: (from netch@localhost)
by iv.nn.kiev.ua (8.11.4/8.11.4) id f5P63Wg01525;
Mon, 25 Jun 2001 09:03:32 +0300 (EEST)
(envelope-from netch)
Date: Mon, 25 Jun 2001 09:03:32 +0300
From: Valentin Nechayev <netch@iv.nn.kiev.ua>
To: Louis-Philippe Gagnon <louisphilippe@macadamian.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: pthread/longjmp/signal problem
Message-ID: <20010625090332.A416@iv.nn.kiev.ua>
References: <0db001c0fa62$2b567800$2964a8c0@macadamian.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0db001c0fa62$2b567800$2964a8c0@macadamian.com>; from louisphilippe@macadamian.com on Thu, Jun 21, 2001 at 10:55:10AM -0400
X-42: On
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Thu, Jun 21, 2001 at 10:55:10, louisphilippe (Louis-Philippe Gagnon) wrote about "pthread/longjmp/signal problem":
> I've been trying to implement a IsBadReadPtr-style function in FreeBSD by
> using signal handlers and longjmp/setjmp. It seemed to work as expected,
> until I started using the -pthread option to gcc (thus linking against
> libc_r). Now the function only works on the first call; subsequent calls
> hang on the segmentation fault.
libc_r provides its own signal handling. sigaction() called by you
is libc_r function which replaces your handler with its own and record
your handler in its private data. On SIGSEGV, not your handler is called,
but libc_r's:
1370 lou CALL write(0x2,0xbfbff050,0xf)
1370 lou GIO fd 2 wrote 15 bytes
"before sigsegv
"
1370 lou RET write 15/0xf
1370 lou PSIG SIGSEGV caught handler=0x28072444 mask=0x0 code=0x0
1370 lou CALL sigprocmask(0x3,0x2807f0d8,0)
1370 lou RET sigprocmask 0
1370 lou CALL sigaltstack(0x28084aa0,0)
1370 lou RET sigaltstack 0
1370 lou CALL write(0x2,0xbfbfecf0,0xb)
1370 lou GIO fd 2 wrote 11 bytes
"in handler
"
1370 lou RET write 11/0xb
1370 lou CALL write(0x2,0xbfbff050,0x13)
1370 lou GIO fd 2 wrote 19 bytes
"longjmp successful
"
Your handler doesn't contain sigaltstack() call, does it? ;)
With longjmp, you destruct libc_r's internals because it can't do
needed cleanups.
> Basically, the app registers a signal handler for SIGSEGV, initializes a
> setjmp() buffer, then provokes a segmentation fault. The expected behavior
> is for the signal handler to get called, which will longjmp() bask to main,
> where another segmentation fault will occur, which repeats the process.
> After 10 times, the if(y>=10) condition makes the program exit.
You cannot do longjmp() out from signal handler with libc_r.
If you nevertheless want to implement your function, you should
1) Block all signals except SIGSERV via sigprocmask();
especially block SIGVTALRM (libc_r on-timer switching signal)
2) Call __sys_sigaction() instead of sigaction(), to call real syscall
and not libc_r wrapper. Don't forget to restore previous handler
with the same call after restoring.
3) Really call test and handle return from signal handler.
4) Restore kernel's sigaction and sigprocmask.
And this way uses undocumented implementation details of libc_r
and can stop to work in any moment.
> Out of curiosity, I tried installing the linuxthreads port and using that :
> this actually works, but I may not be able to use it as a permanent
> solution.
linuxthreads uses another approach. But it also deals with signal handlers.
/netch
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 23: 9:10 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
by hub.freebsd.org (Postfix) with ESMTP id 7810437B405
for <freebsd-hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 23:09:06 -0700 (PDT)
(envelope-from des@ofug.org)
Received: (from des@localhost)
by flood.ping.uio.no (8.9.3/8.9.3) id IAA85624;
Mon, 25 Jun 2001 08:09:01 +0200 (CEST)
(envelope-from des@ofug.org)
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: Sean Chittenden <sean-freebsd-hackers@chittenden.org>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: What happens to a connection between a select and accept...
References: <20010624195910.A44590@rand.tgd.net>
From: Dag-Erling Smorgrav <des@ofug.org>
Date: 25 Jun 2001 08:09:01 +0200
In-Reply-To: <20010624195910.A44590@rand.tgd.net>
Message-ID: <xzp1yo91476.fsf@flood.ping.uio.no>
Lines: 12
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Sean Chittenden <sean-freebsd-hackers@chittenden.org> writes:
> Quick question. Anyone know how gracefully the kernel handles a
> socket connection that is killed by the client between a select and
> accept call? I don't expect any problems, but I know there was a race
> condition in Linux that caused all kinds of nasty bugs and problems.
There was one in FreeBSD too. It's been fixed; accept(2) will return
-1 and set errno to ECONNABORTED, which you'd know if you'd RTFM.
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 Sun Jun 24 23:16:26 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.tgd.net (rand.tgd.net [64.81.67.117])
by hub.freebsd.org (Postfix) with SMTP id 86F8237B401
for <freebsd-hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 23:16:23 -0700 (PDT)
(envelope-from sean@mailhost.tgd.net)
Received: (qmail 66435 invoked by uid 1001); 25 Jun 2001 06:16:17 -0000
Date: Sun, 24 Jun 2001 23:16:17 -0700
From: Sean Chittenden <sean-freebsd-hackers@chittenden.org>
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: What happens to a connection between a select and accept...
Message-ID: <20010624231617.C44590@rand.tgd.net>
References: <20010624195910.A44590@rand.tgd.net> <xzp1yo91476.fsf@flood.ping.uio.no>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="O3RTKUHj+75w1tg5"
Content-Disposition: inline
In-Reply-To: <xzp1yo91476.fsf@flood.ping.uio.no>; from "des@ofug.org" on Mon, Jun 25, 2001 at = 08:09:01AM
X-PGP-Key: 0x1EDDFAAD
X-PGP-Fingerprint: C665 A17F 9A56 286C 5CFB 1DEA 9F4F 5CEF 1EDD FAAD
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
--O3RTKUHj+75w1tg5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
> There was one in FreeBSD too. It's been fixed; accept(2) will return
> -1 and set errno to ECONNABORTED, which you'd know if you'd RTFM.
Already RTFM'd. The following was a tad vague and it led me to
be a skeptic.
It is possible to select(2) a socket for the purposes of doing an
accept() by selecting it for read.
Thanks for your help though, that was what I was hoping to hear! =20
-sc
--=20
Sean Chittenden
--O3RTKUHj+75w1tg5
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Comment: Sean Chittenden <sean@chittenden.org>
iEYEARECAAYFAjs21zEACgkQn09c7x7d+q2CuQCffGtSk488XvgWWmyA50KKi2ZR
XZIAmQHlOQ0FYm8xQ1Sw472XqsAx4SLp
=F/UD
-----END PGP SIGNATURE-----
--O3RTKUHj+75w1tg5--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 23:20:14 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from elvis.franken.de (elvis.franken.de [193.175.24.41])
by hub.freebsd.org (Postfix) with ESMTP id 4C61A37B405
for <freebsd-hackers@freebsd.org>; Sun, 24 Jun 2001 23:20:10 -0700 (PDT)
(envelope-from tanis@gaspode.franken.de)
Received: from uucp by elvis.franken.de with local-rmail (Exim 3.22 #1)
id 15EPjE-0000F9-00; Mon, 25 Jun 2001 08:20:08 +0200
Received: from gaspode.franken.de (lengfeld.core.main.franken.de [193.141.110.4])
by karnickel.franken.de (8.11.3/8.11.3) with ESMTP id f5P6ICA86520;
Mon, 25 Jun 2001 08:18:12 +0200 (CEST)
(envelope-from tanis@gaspode.franken.de)
Received: (from tanis@localhost)
by gaspode.franken.de (8.11.3/8.11.1) id f5P6ID000844;
Mon, 25 Jun 2001 08:18:13 +0200 (CEST)
(envelope-from tanis)
Date: Mon, 25 Jun 2001 08:18:13 +0200
From: German Tischler <tanis@gaspode.franken.de>
To: David Gilbert <dgilbert@velocet.ca>
Cc: Brian Reichert <reichert@numachi.com>,
freebsd-hackers@FreeBSD.ORG
Subject: Re: DVD IOCTLs on IDE?
Message-ID: <20010625081813.A615@gaspode.franken.de>
References: <15158.24886.958193.121109@trooper.velocet.net> <20010624180007.Z23601@numachi.com> <15158.33260.976403.782709@trooper.velocet.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp"
Content-Disposition: inline
User-Agent: Mutt/1.2.5-current-20010403i
In-Reply-To: <15158.33260.976403.782709@trooper.velocet.net>; from dgilbert@velocet.ca on Sun, Jun 24, 2001 at 08:12:28PM -0400
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
--LQksG6bCIzRHxTLp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Jun 24, 2001 at 08:12:28PM -0400, David Gilbert wrote:
> >>>>> "Brian" =3D=3D Brian Reichert <reichert@numachi.com> writes:
>=20
> Brian> On Sun, Jun 24, 2001 at 05:52:54PM -0400, David Gilbert wrote:
> >> Has anyone looked at DVD ioctls on IDE? It took me some time to
> >> realize (even after reading the source a couple of times) that the
> >> current DVD ioctls only apply to SCSI.
>=20
> Brian> 'Looked at'? What do you mean? People have been making use of
> Brian> IDE DVD-ROM drives for quite a while now...
>=20
> >From the dvdio.h CVS comment:
>=20
> MFC, DVD ioctls.
>=20
> scsi_cd.c rev 1.36
> scsi_cd.h rev 1.4
> dvdio.h rev 1.3
>=20
> ... One issue is that dvdio.h seems to be missing structure items that=20
> are required by dvd software. I have attempted to compile livid (oms)=20
> and videolan ... both which at least talk about working on BSD. Livid=20
> refuses to compile because dvdio.h is missing certain structure
> members.
>=20
> videolan compiles and runs, but refuses to recognise a DVD in the
> player (I've tried several DVDs). My IDE DVD player probes as:
Try getting the latest videolan source from their CVS repository.
I have vlc working here quite nicely after sending the vlc guys
a patch for using only sector aligned reads on DVDs. Unfortunately
the patch didn't make it into the current release, but is in CVS now.
--gt
--LQksG6bCIzRHxTLp
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iQEVAwUBOzbXpL7hO6NLB/FvAQHY8QgAkuydf/47khoC2Msf4zA4d7gqpTo2tKuF
DAbyup7vUf4mPoyz7ZDm/XOVaomiKNuSsGj2wHJCltFCW6dAkvUD3SSFDvq5U+SE
S/giuX2OR5QOgNgcWLLlCEH12YM2D7PK2D2g5TL3GBbd1HCUFxOpSvXeOrwIyCIW
ksC8npKxelC3qqRlUHOvDUF7MJaoic2tgkV/4z+yXKcXZMGbZ0SGVYBdbS1wSqOo
VsMi9Q2y2pGOaitYuMvGyePeeIx3+839q2JNKCGt7vkNNIHmBF8t5yT+FT5Ywpb4
zlEP9/oVWeLrSvUSFr034YTVxjuxkL3K4ZKpyq7HSvdjtoQrKWkUEg==
=0iUd
-----END PGP SIGNATURE-----
--LQksG6bCIzRHxTLp--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 23:26:20 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
by hub.freebsd.org (Postfix) with ESMTP id CA20437B401
for <freebsd-hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 23:26:16 -0700 (PDT)
(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
by pcnet1.pcnet.com (8.8.7/PCNet) id CAA07184;
Mon, 25 Jun 2001 02:25:09 -0400 (EDT)
Date: Mon, 25 Jun 2001 02:25:08 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
To: Valentin Nechayev <netch@iv.nn.kiev.ua>
Cc: Louis-Philippe Gagnon <louisphilippe@macadamian.com>,
freebsd-hackers@FreeBSD.ORG
Subject: Re: pthread/longjmp/signal problem
In-Reply-To: <20010625090332.A416@iv.nn.kiev.ua>
Message-ID: <Pine.SUN.3.91.1010625022147.6848A-100000@pcnet1.pcnet.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Mon, 25 Jun 2001, Valentin Nechayev wrote:
> Thu, Jun 21, 2001 at 10:55:10, louisphilippe (Louis-Philippe Gagnon) wrote about "pthread/longjmp/signal problem":
>
> > I've been trying to implement a IsBadReadPtr-style function in FreeBSD by
> > using signal handlers and longjmp/setjmp. It seemed to work as expected,
> > until I started using the -pthread option to gcc (thus linking against
> > libc_r). Now the function only works on the first call; subsequent calls
> > hang on the segmentation fault.
>
> libc_r provides its own signal handling. sigaction() called by you
> is libc_r function which replaces your handler with its own and record
> your handler in its private data. On SIGSEGV, not your handler is called,
> but libc_r's:
>
> 1370 lou CALL write(0x2,0xbfbff050,0xf)
> 1370 lou GIO fd 2 wrote 15 bytes
> "before sigsegv
> "
> 1370 lou RET write 15/0xf
> 1370 lou PSIG SIGSEGV caught handler=0x28072444 mask=0x0 code=0x0
> 1370 lou CALL sigprocmask(0x3,0x2807f0d8,0)
> 1370 lou RET sigprocmask 0
> 1370 lou CALL sigaltstack(0x28084aa0,0)
> 1370 lou RET sigaltstack 0
> 1370 lou CALL write(0x2,0xbfbfecf0,0xb)
> 1370 lou GIO fd 2 wrote 11 bytes
> "in handler
> "
> 1370 lou RET write 11/0xb
> 1370 lou CALL write(0x2,0xbfbff050,0x13)
> 1370 lou GIO fd 2 wrote 19 bytes
> "longjmp successful
> "
>
> Your handler doesn't contain sigaltstack() call, does it? ;)
>
> With longjmp, you destruct libc_r's internals because it can't do
> needed cleanups.
This is suppose to work as long as you are jumping to the current
threads stack.
> > Basically, the app registers a signal handler for SIGSEGV, initializes a
> > setjmp() buffer, then provokes a segmentation fault. The expected behavior
> > is for the signal handler to get called, which will longjmp() bask to main,
> > where another segmentation fault will occur, which repeats the process.
> > After 10 times, the if(y>=10) condition makes the program exit.
>
> You cannot do longjmp() out from signal handler with libc_r.
You are suppose to be able to do this. I will look at it when I
get the chance.
> If you nevertheless want to implement your function, you should
>
> 1) Block all signals except SIGSERV via sigprocmask();
> especially block SIGVTALRM (libc_r on-timer switching signal)
> 2) Call __sys_sigaction() instead of sigaction(), to call real syscall
> and not libc_r wrapper. Don't forget to restore previous handler
> with the same call after restoring.
__sys_sigaction is only in current, -stable still has
_thread_sys_sigaction. But you don't really want to know
that -- it is suppose to work correctly.
> 3) Really call test and handle return from signal handler.
> 4) Restore kernel's sigaction and sigprocmask.
>
> And this way uses undocumented implementation details of libc_r
> and can stop to work in any moment.
>
> > Out of curiosity, I tried installing the linuxthreads port and using that :
> > this actually works, but I may not be able to use it as a permanent
> > solution.
>
> linuxthreads uses another approach. But it also deals with signal handlers.
--
Dan Eischen
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 23:35: 7 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114])
by hub.freebsd.org (Postfix) with ESMTP id 2653637B40A
for <freebsd-hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 23:35:04 -0700 (PDT)
(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
by freebsd.dk (8.11.3/8.11.3) id f5P6YxR08707;
Mon, 25 Jun 2001 08:34:59 +0200 (CEST)
(envelope-from sos)
From: Søren Schmidt <sos@freebsd.dk>
Message-Id: <200106250634.f5P6YxR08707@freebsd.dk>
Subject: Re: DVD IOCTLs on IDE?
In-Reply-To: <15158.24886.958193.121109@trooper.velocet.net> "from David Gilbert
at Jun 24, 2001 05:52:54 pm"
To: David Gilbert <dgilbert@velocet.ca>
Date: Mon, 25 Jun 2001 08:34:59 +0200 (CEST)
Cc: freebsd-hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL88 (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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
It seems David Gilbert wrote:
> Has anyone looked at DVD ioctls on IDE? It took me some time to
> realize (even after reading the source a couple of times) that the
> current DVD ioctls only apply to SCSI.
Hmm, I "grew" those ioctls in our ATA (IDE) driver way before they
where even considered for the SCSI driver:
atapi-cd.c revision 1.25
date: 1999/12/07 22:25:24; author: sos; state: Exp; lines: +278 -2
Commit the kernel part of our DVD support. Nothing much to say really,
its just a number of new ioctl's, the rest is done in userland.
Versus:
scsi_cd.c revision 1.36
date: 2000/05/12 03:35:57; author: ken; state: Exp; lines: +587 -2
Add support for the DVD ioctl interface.
So, there it is :)
-Søre
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sun Jun 24 23:50:40 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
by hub.freebsd.org (Postfix) with ESMTP id 00BE937B405
for <freebsd-hackers@FreeBSD.ORG>; Sun, 24 Jun 2001 23:50:36 -0700 (PDT)
(envelope-from des@ofug.org)
Received: (from des@localhost)
by flood.ping.uio.no (8.9.3/8.9.3) id IAA85798;
Mon, 25 Jun 2001 08:50:32 +0200 (CEST)
(envelope-from des@ofug.org)
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: Sean Chittenden <sean-freebsd-hackers@chittenden.org>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: What happens to a connection between a select and accept...
References: <20010624195910.A44590@rand.tgd.net>
<xzp1yo91476.fsf@flood.ping.uio.no>
<20010624231617.C44590@rand.tgd.net>
From: Dag-Erling Smorgrav <des@ofug.org>
Date: 25 Jun 2001 08:50:32 +0200
In-Reply-To: <20010624231617.C44590@rand.tgd.net>
Message-ID: <xzpwv61yrwn.fsf@flood.ping.uio.no>
Lines: 11
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Sean Chittenden <sean-freebsd-hackers@chittenden.org> writes:
> It is possible to select(2) a socket for the purposes of doing an
> accept() by selecting it for read.
This simply means that select(2) will consider a listen socket
readable when there's at least one incoming connection in that
socket's listen queue.
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 Jun 25 0:28:42 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119])
by hub.freebsd.org (Postfix) with ESMTP
id 8EDCB37B401; Mon, 25 Jun 2001 00:28:38 -0700 (PDT)
(envelope-from adsharma@sharmas.dhs.org)
Received: by sharmas.dhs.org (Postfix, from userid 500)
id 7A11F5E110; Mon, 25 Jun 2001 00:28:42 -0700 (PDT)
Date: Mon, 25 Jun 2001 00:28:42 -0700
From: Arun Sharma <arun@sharmas.dhs.org>
To: freebsd-hackers@freebsd.org
Cc: freebsd-mobile@freebsd.org
Subject: libwi and KWireless
Message-ID: <20010625002842.A23058@sharmas.dhs.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.15i
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
KWireless is a KDE kicker applet to display the signal qualtiy of a IEEE
802.11b wireless network.
http://www.sharma-home.net/~adsharma/projects/KWireless/
It depends on libwi, a library version of wicontrol(8).
http://www.sharma-home.net/~adsharma/projects/libwi/
I know this is not in a commitable state and would appreciate some
feedback on what I need to do, before it can be commited.
Enjoy!
-Arun
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 1:54:48 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13])
by hub.freebsd.org (Postfix) with SMTP id A6F6F37B401
for <hackers@FreeBSD.ORG>; Mon, 25 Jun 2001 01:54:37 -0700 (PDT)
(envelope-from roam@orbitel.bg)
Received: (qmail 10771 invoked by uid 1000); 25 Jun 2001 08:52:50 -0000
Date: Mon, 25 Jun 2001 11:52:50 +0300
From: Peter Pentchev <roam@orbitel.bg>
To: Valentin Nechayev <netch@iv.nn.kiev.ua>
Cc: Cyrille Lefevre <clefevre@redirect.to>, hackers@FreeBSD.ORG
Subject: Re: "include" directive in config(8) (was: Two Junior Kernel Hacker tasks..)
Message-ID: <20010625115250.D934@ringworld.oblivion.bg>
Mail-Followup-To: Valentin Nechayev <netch@iv.nn.kiev.ua>,
Cyrille Lefevre <clefevre@redirect.to>, hackers@FreeBSD.ORG
References: <20010624204114.F2B913E28@bazooka.unixfreak.org> <66dlbkjz.fsf@gits.dyndns.org> <20010625082735.A909@iv.nn.kiev.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010625082735.A909@iv.nn.kiev.ua>; from netch@iv.nn.kiev.ua on Mon, Jun 25, 2001 at 08:27:35AM +0300
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Mon, Jun 25, 2001 at 08:27:35AM +0300, Valentin Nechayev wrote:
> Mon, Jun 25, 2001 at 00:05:36, clefevre-lists (Cyrille Lefevre) wrote about "Re: "include" directive in config(8) (was: Two Junior Kernel Hacker tasks..)":
>
> > how about "undef options XXX" and "undef device XXX", etc. ?
>
> s/undef/no/
> I like Cisco style ;)))
This sounds nice.
G'luck,
Peter
--
This inert sentence is my body, but my soul is alive, dancing in the sparks of your brain.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 3:56:45 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106])
by hub.freebsd.org (Postfix) with ESMTP id 2A85737B406
for <freebsd-hackers@FreeBSD.ORG>; Mon, 25 Jun 2001 03:56:41 -0700 (PDT)
(envelope-from ticso@mail.cicely.de)
Received: from mail.cicely.de (cicely20 [10.1.1.22])
by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f5PAuc624202;
Mon, 25 Jun 2001 12:56:38 +0200 (CEST)
Received: (from ticso@localhost)
by mail.cicely.de (8.11.0/8.11.0) id f5PAvS300348;
Mon, 25 Jun 2001 12:57:28 +0200 (CEST)
Date: Mon, 25 Jun 2001 12:57:27 +0200
From: Bernd Walter <ticso@mail.cicely.de>
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: Sean Chittenden <sean-freebsd-hackers@chittenden.org>,
freebsd-hackers@FreeBSD.ORG
Subject: Re: What happens to a connection between a select and accept...
Message-ID: <20010625125727.A340@cicely20.cicely.de>
References: <20010624195910.A44590@rand.tgd.net> <xzp1yo91476.fsf@flood.ping.uio.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <xzp1yo91476.fsf@flood.ping.uio.no>; from des@ofug.org on Mon, Jun 25, 2001 at 08:09:01AM +0200
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Mon, Jun 25, 2001 at 08:09:01AM +0200, Dag-Erling Smorgrav wrote:
> Sean Chittenden <sean-freebsd-hackers@chittenden.org> writes:
> > Quick question. Anyone know how gracefully the kernel handles a
> > socket connection that is killed by the client between a select and
> > accept call? I don't expect any problems, but I know there was a race
> > condition in Linux that caused all kinds of nasty bugs and problems.
>
> There was one in FreeBSD too. It's been fixed; accept(2) will return
> -1 and set errno to ECONNABORTED, which you'd know if you'd RTFM.
And even if it is not a problem with FreeBSD the portable way is to set
the listen socket to non-blocking so accept will always return.
--
B.Walter COSMO-Project http://www.cosmo-project.de
ticso@cicely.de Usergroup info@cosmo-project.de
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 4:36: 1 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailgate2.Cadence.COM (mailgate2.Cadence.COM [158.140.2.31])
by hub.freebsd.org (Postfix) with ESMTP id 360DE37B406
for <hackers@freebsd.org>; Mon, 25 Jun 2001 04:35:57 -0700 (PDT)
(envelope-from dmlb@dmlb.org)
Received: from symnt3.Cadence.COM (symnt3.Cadence.COM [194.32.101.100])
by mailgate2.Cadence.COM (8.9.3/8.9.3) with ESMTP id EAA06220;
Mon, 25 Jun 2001 04:34:32 -0700 (PDT)
Received: from pc598cam (pc598-cam.cadence.com [194.32.96.179]) by symnt3.Cadence.COM with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
id M383QYA9; Mon, 25 Jun 2001 12:33:28 +0100
Message-ID: <00a901c0fd6a$c44375d0$b36020c2@pc598cam>
From: "Duncan Barclay" <dmlb@dmlb.org>
To: "list tracker" <list_tracker@hotmail.com>,
<ambrisko@ambrisko.com>
Cc: <hackers@freebsd.org>
References: <F156NH2cv0aGltFBNlJ00001ece@hotmail.com>
Subject: Re: trouble with 802.11 and kernel bridging (more)
Date: Mon, 25 Jun 2001 12:34:16 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Received: By mailgate2.Cadence.COM as EAA06220 at Mon Jun 25 04:34:32 2001
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
----- Original Message -----
From: "list tracker" <list_tracker@hotmail.com>
To: <ambrisko@ambrisko.com>
Cc: <hackers@freebsd.org>
Sent: Monday, June 25, 2001 3:27 AM
Subject: Re: trouble with 802.11 and kernel bridging (more)
>
> ok, thank you! This explains my inability to perform bridging like I
> expected to....
>
> >I've been told the "wi" driver can't do bridging. The Cisco/Aironet
> >"an" driver can. Patches were submitted so you can do this. They are
> >in the tree.
>
> If I want to turn a PC into a full-blown "access point", should I set
> wicontrol to peer to peer (3) or BSS (1) ?
As Julian said an AP is very different to a standard station in either IBSS
or BSS mode.
If you want to:
have a FreeBSD box with a card in it
get the FreeBSD box to be a bridge/router between multiple wireless
users and wired networks
then
Set the card into IBSS mode
Turn on "create BSS" (if it works)
Either:
Use BRIDGEing
Take a wired n/w performance hit
Or Use routing and set two subnets up
Turn on ipforwarding in /etc/rc.conf
Make's moving a node from wired to wireless a little harder.
I use IBSS and routing at home (with DHCP on a short timeout) to create
seperate wired and wireless IP subnets. The FreeBSD box routes between the
two and the external Cable Modem seamlessly.
What disadvantages does this setup have compared with using a true access
point? True APs can double the range for two
wireless stations (the hidden node problem) - if both stations can see the
AP but not each other they can still do peer to peer networking. True APs
allow roaming between APs in an extended service set. True APs can do power
saving to stations.
I contend that the above are not necessary for a typical home user. An IBSS
network with IP routing will serve many home users.
> Secondly, should I turn on the "create BSS" (I am almost positive I
should)
> - but this leads me to:
>
> thirdly, are the fixes that allow wi to "create BSS" also "in the tree" ?
> or does the man page warning that it does not work still valid ?
>
> (I was using 4.3-RELEASE, btw)
>
> thanks.
>
> LT
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 4:43:13 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailout4-0.nyroc.rr.com (mailout4-1.nyroc.rr.com [24.92.226.166])
by hub.freebsd.org (Postfix) with ESMTP id 8A70F37B401
for <freebsd-hackers@freebsd.org>; Mon, 25 Jun 2001 04:42:59 -0700 (PDT)
(envelope-from James_Bond_79@yahoo.com)
Received: from halstead007 (roc-24-169-196-57.rochester.rr.com [24.169.196.57])
by mailout4-0.nyroc.rr.com (8.11.2/RoadRunner 1.03) with SMTP id f5PBfZ823907;
Mon, 25 Jun 2001 07:41:35 -0400 (EDT)
Content-Type: Multipart/Mixed;
charset="iso-8859-1";
boundary="------------Boundary-00=_C7IHYKFQN29DWWVL1GHJ"
From: James Halstead <James_Bond_79@yahoo.com>
To: David Gilbert <dgilbert@velocet.ca>
Subject: Re: DVD IOCTLs on IDE?
Date: Mon, 25 Jun 2001 07:50:00 -0400
X-Mailer: KMail [version 1.2]
References: <15158.24886.958193.121109@trooper.velocet.net> <01062420555600.00449@halstead007> <15158.36689.918629.862331@trooper.velocet.net>
In-Reply-To: <15158.36689.918629.862331@trooper.velocet.net>
Cc: freebsd-hackers@freebsd.org
MIME-Version: 1.0
Message-Id: <01062507500001.00449@halstead007>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
--------------Boundary-00=_C7IHYKFQN29DWWVL1GHJ
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
On Sunday 24 June 2001 21:09, David Gilbert wrote:
> Could I have a copy of your patches? Where do I get xine?
The attached is a shell archive for a port I made out of the libcss from
livid. It compiles but i have no idea if it works. Please do not submit it to
the ports collection! all the patches are in the files/patch-* files.
As for xine, go to xine.sourceforge.net, hit the how to link, then choose
browseable html. Select the playing dvd's and there will be a link to the
captiancss page. It compiles cleanly on my 4.x system with ./configure
--prefix=/usr/X11R6; gmake; gmake install. If I remember right the makefiles
will work with the regular make as well if you don't have gmake installed.
There is also a link to the linux video site (where libcss comes from) and a
plugin to use libcss. However I cannot get the plugin for this one to compile
yet.
If you have any luck tell me. I have been able to watch encrypted dvd's but
it seems to like crashing when changing tracks. Also i have had a problem
where xine will stop running after a while, seems to be running out of shared
memory maps, something is not getting cleaned up properly.
> Dave.
James
--------------Boundary-00=_C7IHYKFQN29DWWVL1GHJ
Content-Type: text/plain;
charset="iso-8859-1";
name="libcss.shar"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="libcss.shar"
IyBUaGlzIGlzIGEgc2hlbGwgYXJjaGl2ZS4gIFNhdmUgaXQgaW4gYSBmaWxlLCByZW1vdmUgYW55
dGhpbmcgYmVmb3JlCiMgdGhpcyBsaW5lLCBhbmQgdGhlbiB1bnBhY2sgaXQgYnkgZW50ZXJpbmcg
InNoIGZpbGUiLiAgTm90ZSwgaXQgbWF5CiMgY3JlYXRlIGRpcmVjdG9yaWVzOyBmaWxlcyBhbmQg
ZGlyZWN0b3JpZXMgd2lsbCBiZSBvd25lZCBieSB5b3UgYW5kCiMgaGF2ZSBkZWZhdWx0IHBlcm1p
c3Npb25zLgojCiMgVGhpcyBhcmNoaXZlIGNvbnRhaW5zOgojCiMJbGliY3NzCiMJbGliY3NzL3Br
Zy1kZXNjcgojCWxpYmNzcy9wa2ctcGxpc3QKIwlsaWJjc3MvZmlsZXMKIwlsaWJjc3MvZmlsZXMv
cGF0Y2gtYWEKIwlsaWJjc3MvZmlsZXMvcGF0Y2gtYWcKIwlsaWJjc3MvZmlsZXMvcGF0Y2gtYWIK
IwlsaWJjc3MvZmlsZXMvcGF0Y2gtYWMKIwlsaWJjc3MvZmlsZXMvcGF0Y2gtYWQKIwlsaWJjc3Mv
ZmlsZXMvcGF0Y2gtYWUKIwlsaWJjc3MvZmlsZXMvcGF0Y2gtYWYKIwlsaWJjc3MvZmlsZXMvcGF0
Y2hlcy1haAojCWxpYmNzcy9kaXN0aW5mbwojCWxpYmNzcy9wa2ctY29tbWVudAojCWxpYmNzcy9N
YWtlZmlsZQojCmVjaG8gYyAtIGxpYmNzcwpta2RpciAtcCBsaWJjc3MgPiAvZGV2L251bGwgMj4m
MQplY2hvIHggLSBsaWJjc3MvcGtnLWRlc2NyCnNlZCAncy9eWC8vJyA+bGliY3NzL3BrZy1kZXNj
ciA8PCAnRU5ELW9mLWxpYmNzcy9wa2ctZGVzY3InClhMaWJjc3MgbGlicmFyeSBhcyBpbXBsZW1l
bnRlZCBpbiB0aGUgbGl2aWQgcHJvamVjdC4gU2hvdWxkIHdvcmsgd2l0aCB4aW5lIHRvClhwbGF5
IGVuY3J5cHRlZCBkdmQncwpFTkQtb2YtbGliY3NzL3BrZy1kZXNjcgplY2hvIHggLSBsaWJjc3Mv
cGtnLXBsaXN0CnNlZCAncy9eWC8vJyA+bGliY3NzL3BrZy1wbGlzdCA8PCAnRU5ELW9mLWxpYmNz
cy9wa2ctcGxpc3QnClhiaW4vdHN0ZHZkClhiaW4vZHZkaW5mbwpYYmluL3Jlc2V0X2R2ZApYaW5j
bHVkZS9jc3MuaApYbGliL2xpYmNzcy5zby4xClhsaWIvbGliY3NzLnNvClhsaWIvbGliY3NzLmxh
ClhsaWIvbGliY3NzLmEKWHNoYXJlL2FjbG9jYWwvZHZkLm00CkVORC1vZi1saWJjc3MvcGtnLXBs
aXN0CmVjaG8gYyAtIGxpYmNzcy9maWxlcwpta2RpciAtcCBsaWJjc3MvZmlsZXMgPiAvZGV2L251
bGwgMj4mMQplY2hvIHggLSBsaWJjc3MvZmlsZXMvcGF0Y2gtYWEKc2VkICdzL15YLy8nID5saWJj
c3MvZmlsZXMvcGF0Y2gtYWEgPDwgJ0VORC1vZi1saWJjc3MvZmlsZXMvcGF0Y2gtYWEnClgtLS0g
Y29uZmlndXJlLmluLm9yaWcJV2VkIEZlYiAxNCAxOTo0MDowMiAyMDAxClgrKysgY29uZmlndXJl
LmluCVdlZCBKdW4gMjAgMTY6MzM6MjQgMjAwMQpYQEAgLTQzLDE1ICs0MywxOSBAQApYIGlmIHRl
c3QgIngkZW5hYmxlX2RldmVsIiA9ICJ4eWVzIjsgdGhlbgpYICAgICAgICAgQ0ZMQUdTPSIkQ0ZM
QUdTIC1nMyAtRERFVkVMIC1EREVCVUciClggZWxzZQpYLSAgICAgICAgQ0ZMQUdTPSIkQ0ZMQUdT
IC1PNiAtZm9taXQtZnJhbWUtcG9pbnRlciAtZnVucm9sbC1hbGwtbG9vcHMgLURfX09QVElNSVpF
X18gLURfX1VTRV9TVFJJTkdfSU5MSU5FUyIKWCsgICAgICAgIENGTEFHUz0iJENGTEFHUyAtTzYg
LWZvbWl0LWZyYW1lLXBvaW50ZXIgLWZ1bnJvbGwtYWxsLWxvb3BzIC1EX19PUFRJTUlaRV9fIC1E
X19VU0VfU1RSSU5HX0lOTElORVMgXCQoRVhUUkFfREVGUykiClggZmkgICAgIApYIApYLQpYIGRu
bCA9PT09PT09PT09ClggZG5sIGdldCBsb2NhdGlvbiBvZiBrZXJuZWwgaGVhZGVycwpYIGRubCA9
PT09PT09PT09ClggClggQUNfQ19LRVJORUxfSU5DTFVERVMKWCsKWCtkbmwgPT09PT09PT09PQpY
K2RubCBDaGVjayBpZiB3ZSdyZSBvbiBGcmVlQlNEClgrZG5sID09PT09PT09PT0KWCtBTV9DT05E
SVRJT05BTChGUkVFQlNELCB0ZXN0IGB1bmFtZSAtc2AgPSAiRnJlZUJTRCIpClggClggZG5sID09
PT09PT09PT0KWCBkbmwgT3V0cHV0IGNvbmZpZ3VyYXRpb24gZmlsZXMKRU5ELW9mLWxpYmNzcy9m
aWxlcy9wYXRjaC1hYQplY2hvIHggLSBsaWJjc3MvZmlsZXMvcGF0Y2gtYWcKc2VkICdzL15YLy8n
ID5saWJjc3MvZmlsZXMvcGF0Y2gtYWcgPDwgJ0VORC1vZi1saWJjc3MvZmlsZXMvcGF0Y2gtYWcn
ClgtLS0gc3JjL3RzdGR2ZC5jLm9yaWcJVHVlIEZlYiAxMyAxNjo1OToyNyAyMDAxClgrKysgc3Jj
L3RzdGR2ZC5jCVdlZCBKdW4gMjAgMTY6MzM6MjQgMjAwMQpYQEAgLTY1LDExICs2NSwxOSBAQApY
IAkJcGVycm9yKCJEVkQgdm9iIGZpbGUiKTsKWCAJCXJldHVybiAwOwpYIAl9ClgrI2lmbmRlZiBf
X0ZyZWVCU0RfXwpYIAlpZiAoaW9jdGwoZmQsIEZJQk1BUCwgJmxiYSkgIT0gMCkgewpYIAkJcGVy
cm9yICgiaW9jdGwgRklCTUFQIik7ClggCQljbG9zZShmZCk7ClggCQlyZXR1cm4gMDsKWCAJfQpY
KyNlbHNlClgrCWlmIChpb2N0bChmZCwgRklPR0VUTEJBLCAmbGJhKSAhPSAwKSB7ClgrCQlwZXJy
b3IgKCJpb2N0bCBGSU9HRVRMQkEiKTsKWCsJCWNsb3NlKGZkKTsKWCsJCXJldHVybiAwOwpYKwl9
ClgrI2VuZGlmClggClggCWNsb3NlKGZkKTsKWCAKRU5ELW9mLWxpYmNzcy9maWxlcy9wYXRjaC1h
ZwplY2hvIHggLSBsaWJjc3MvZmlsZXMvcGF0Y2gtYWIKc2VkICdzL15YLy8nID5saWJjc3MvZmls
ZXMvcGF0Y2gtYWIgPDwgJ0VORC1vZi1saWJjc3MvZmlsZXMvcGF0Y2gtYWInClgtLS0gc3JjL01h
a2VmaWxlLmFtLm9yaWcJVGh1IE5vdiAgMiAxNDowNjo0MSAyMDAwClgrKysgc3JjL01ha2VmaWxl
LmFtCQlXZWQgSnVuIDIwIDE2OjMzOjI0IDIwMDEKWEBAIC0xMCwxNyArMTAsMzAgQEAKWCBiaW5f
UFJPR1JBTVMgPSB0c3RkdmQgZHZkaW5mbyByZXNldF9kdmQKWCBub2luc3RfUFJPR1JBTVMgPSBj
c3NfY2F0ClggClgraWYgRlJFRUJTRApYK0VYVFJBX0RFRlMgPSAtRF9USFJFQURfU0FGRQpYK0xJ
QlBUSFJFQUQgPSAtcHRocmVhZApYK0xJQkRMID0KWCtlbHNlClgrRVhUUkFfREVGUyA9ClgrTElC
UFRIUkVBRCA9ClgrTElCREwgPSAtbGRsClgrZW5kaWYKWCsKWCB0c3RkdmRfU09VUkNFUyA9IHRz
dGR2ZC5jClggdHN0ZHZkX0RFUEVOREVOQ0lFUyA9IGxpYmNzcy5sYQpYLXRzdGR2ZF9MREFERCA9
IGxpYmNzcy5sYSAtbGRsClgrdHN0ZHZkX0xERkxBR1MgPSAkKExJQlBUSFJFQUQpClgrdHN0ZHZk
X0xEQUREID0gbGliY3NzLmxhICQoTElCREwpClggClggY3NzX2NhdF9TT1VSQ0VTID0gY3NzX2Nh
dC5jClggY3NzX2NhdF9ERVBFTkRFTkNJRVMgPSBsaWJjc3MubGEKWC1jc3NfY2F0X0xEQUREID0g
bGliY3NzLmxhIC1sZGwKWCtjc3NfY2F0X0xERkxBR1MgPSAkKExJQlBUSFJFQUQpClgrY3NzX2Nh
dF9MREFERCA9IGxpYmNzcy5sYSAkKExJQkRMKQpYIApYIGR2ZGluZm9fU09VUkNFUyA9IGR2ZGlu
Zm8uYwpYIGR2ZGluZm9fREVQRU5ERU5DSUVTID0gbGliY3NzLmxhClgtZHZkaW5mb19MREFERCA9
IGxpYmNzcy5sYSAtbGRsClgrZHZkaW5mb19MREZMQUdTID0gJChMSUJQVEhSRUFEKQpYK2R2ZGlu
Zm9fTERBREQgPSBsaWJjc3MubGEgJChMSUJETCkKWCAKWCByZXNldF9kdmRfU09VUkNFUyA9IHJl
c2V0X2R2ZC5jClggCkVORC1vZi1saWJjc3MvZmlsZXMvcGF0Y2gtYWIKZWNobyB4IC0gbGliY3Nz
L2ZpbGVzL3BhdGNoLWFjCnNlZCAncy9eWC8vJyA+bGliY3NzL2ZpbGVzL3BhdGNoLWFjIDw8ICdF
TkQtb2YtbGliY3NzL2ZpbGVzL3BhdGNoLWFjJwpYLS0tIHNyYy9jc3MuYy5vcmlnCVR1ZSBGZWIg
MTMgMTY6NTk6MjcgMjAwMQpYKysrIHNyYy9jc3MuYwkJV2VkIEp1biAyMCAxNjozMzoyNCAyMDAx
ClhAQCAtMzAsNyArMzAsNyBAQApYICNpbmNsdWRlIDxzeXMvc3RhdC5oPgpYICNpbmNsdWRlIDxz
eXMvdHlwZXMuaD4KWCAjaW5jbHVkZSA8ZXJybm8uaD4KWC0jaWYgZGVmaW5lZChfX05ldEJTRF9f
KSB8fCBkZWZpbmVkKF9fT3BlbkJTRF9fKQpYKyNpZiBkZWZpbmVkKF9fTmV0QlNEX18pIHx8IGRl
ZmluZWQoX19PcGVuQlNEX18pIHx8IGRlZmluZWQoX19GcmVlQlNEX18pClggIyBpbmNsdWRlIDxz
eXMvZHZkaW8uaD4KWCAjZWxpZiBkZWZpbmVkKF9fbGludXhfXykKWCAjIGluY2x1ZGUgPGxpbnV4
L2Nkcm9tLmg+ClhAQCAtNDEsMTMgKzQxLDE3IEBAClggI2luY2x1ZGUgImNzc19hdXRoLmgiClgg
I2luY2x1ZGUgImNzcy5oIgpYIApYKyNpZmRlZiBfX0ZyZWVCU0RfXwpYK3R5cGVkZWYgc3RydWN0
IGR2ZF9zdHJ1Y3QgICBkdmRfc3RydWN0OwpYK3R5cGVkZWYgc3RydWN0IGR2ZF9hdXRoaW5mbyBk
dmRfYXV0aGluZm87ClgrI2VuZGlmClggClggdHlwZWRlZiBzdHJ1Y3QgewpYIAl1aW50OF90IENo
YWxsZW5nZVsxMF07ClggCXVpbnQ4X3QgS2V5MVtMRU5fS0VZXTsKWCAJdWludDhfdCBLZXkyW0xF
Tl9LRVldOwpYIAl1aW50OF90IEtleUNoZWNrW0xFTl9LRVldOwpYLQl1aW50OF90IHZhcmllbnQ7
ClgrCXVpbnQ4X3QgdmFyaWFudDsKWCB9IERpc2NLZXlzOwpYIApYIERpc2NLZXlzIGRpc2NLZXlz
OwpYQEAgLTcwLDEyICs3NCwxMyBAQApYICNlbHNlClggI2RlZmluZSBfQ1NTUHJpbnREZWJ1Zyhh
cmdzLi4uKQpYICNkZWZpbmUgX0NTU1ByaW50RGVidWdCeXRlcyhkZXNjciwgdmFsLCBsZW4pClgr
I2RlZmluZSBfQ1NTUHJpbnRCeXRlcyh2YWwsIGxlbikKWCAjZW5kaWYKWCAKWCAvKioKWCAgKiBD
U1NBdXRoRHJpdmUKWCAgKiBEZXRlcm1pbmUgaWYgZHJpdmUgaXMgYXV0aGVudGljClgtICogUmV0
dXJuOiAtMSBpZiBmYWlsZWQsIDAuLjMyID0gdmFyaWVudCBvZiBDU1MKWCsgKiBSZXR1cm46IC0x
IGlmIGZhaWxlZCwgMC4uMzIgPSB2YXJpYW50IG9mIENTUwpYICAqKi8KWCAKWCAKWEBAIC05MCw4
ICs5NSw4IEBAClggCQlDcnlwdEtleTEoIGksIGRpc2MtPkNoYWxsZW5nZSwgZGlzYy0+S2V5Q2hl
Y2spOwpYIApYIAkJaWYgKG1lbWNtcCAoZGlzYy0+S2V5Q2hlY2ssIGRpc2MtPktleTEsIExFTl9L
RVkpID09IDApIHsKWC0JCQlfQ1NTUHJpbnREZWJ1ZyAoIkRyaXZlIEF1dGhlbnRpYyAtIHVzaW5n
IHZhcmllbnQgJWRcbiIsIGkpOwpYLQkJCWRpc2MtPnZhcmllbnQgPSBpOwpYKwkJCV9DU1NQcmlu
dERlYnVnICgiRHJpdmUgQXV0aGVudGljIC0gdXNpbmcgdmFyaWFudCAlZFxuIiwgaSk7ClgrCQkJ
ZGlzYy0+dmFyaWFudCA9IGk7ClggCQkJcmV0dXJuIGk7ClggCQl9ClggCX0KWEBAIC0xMTksNiAr
MTI0LDcgQEAKWCAJZHZkX3N0cnVjdCBzOwpYIAlpbnQgaTsKWCAKWCsjaWZuZGVmIF9fRnJlZUJT
RF9fClggCXMudHlwZSA9IERWRF9TVFJVQ1RfRElTQ0tFWTsKWCAJcy5kaXNja2V5LmFnaWQgPSBh
Z2lkOwpYIAltZW1zZXQgKHMuZGlzY2tleS52YWx1ZSwgMCwgMjA0OCk7ClhAQCAtMTM0LDYgKzE0
MCwyOSBAQApYIAlfQ1NTUHJpbnREZWJ1Z0J5dGVzICgiUmVjZWl2ZWQgRGlzYyBLZXkiLCBzLmRp
c2NrZXkudmFsdWUsIDEwKTsKWCAKWCAJbWVtY3B5IChrZXlfZGlzYywgcy5kaXNja2V5LnZhbHVl
LCAyMDQ4KTsKWCsjZWxzZQpYKwkvKgpYKwkgKiBGcmVlQlNEJ3MgZHZkX3N0cnVjdCBpcyBub3Qg
YSB1bmlvbiBhcyBpdCBpcyB3aXRoIHRoZSBvdGhlcgpYKwkgKiBwbGF0Zm9ybXM7IGhlbmNlLCB0
aGVyZSBhcmUgbm8gYWRkaXRpb25hbCBzdWItbWVtYmVyClgrCSAqIGRlcmVmZXJlbmNlcy4KWCsJ
ICovClgrClgrCXMuZm9ybWF0ID0gRFZEX1NUUlVDVF9ESVNDS0VZOwpYKwlzLmFnaWQgICA9IGFn
aWQ7ClgrCW1lbXNldCggcy5kYXRhLCAwLCAyMDQ4KTsKWCsKWCsJaWYgKGlvY3RsKCBmZCwgRFZE
SU9DUkVBRFNUUlVDVFVSRSwgJnMpIDwgMCkgewpYKwkJcGVycm9yKCAiQ291bGQgbm90IHJlYWQg
RGlzYyBLZXkiKTsKWCsJCXJldHVybiAtMTsKWCsJfQpYKwpYKwlmb3IoIGk9MDsgaTxzaXplb2Yo
cy5kYXRhKTsgaSsrKQpYKwkJcy5kYXRhW2ldIF49IGtleVs0IC0gKGkgJSBMRU5fS0VZKV07Clgr
ClgrCV9DU1NQcmludERlYnVnQnl0ZXMoICJSZWNlaXZlZCBEaXNjIEtleSIsIHMuZGF0YSwgMTAp
OwpYKwpYKwltZW1jcHkoIGtleV9kaXNjLCBzLmRhdGEsIDIwNDgpOwpYKyNlbmRpZgpYIApYIAly
ZXR1cm4gMDsKWCB9ClhAQCAtMTU2LDYgKzE4NSw3IEBAClggCWR2ZF9hdXRoaW5mbyBhaTsKWCAJ
aW50IGk7ClggClgrI2lmbmRlZiBfX0ZyZWVCU0RfXwpYIAlhaS50eXBlID0gRFZEX0xVX1NFTkRf
VElUTEVfS0VZOwpYIApYIAlhaS5sc3RrLmFnaWQgPSBhZ2lkOwpYQEAgLTE3Myw2ICsyMDMsMjUg
QEAKWCAJX0NTU1ByaW50RGVidWcgKCIgQ1BNPSVkLCBDUF9TRUM9JWQsIENHTVM9JWRcbiIsIGFp
LmxzdGsuY3BtLCBhaS5sc3RrLmNwX3NlYywgYWkubHN0ay5jZ21zKTsKWCAKWCAJbWVtY3B5IChr
ZXlfdGl0bGUsIGFpLmxzdGsudGl0bGVfa2V5LCBMRU5fS0VZKTsKWCsjZWxzZQpYKwlhaS5mb3Jt
YXQgPSBEVkRfUkVQT1JUX1RJVExFX0tFWTsKWCsJYWkuYWdpZCAgID0gYWdpZDsKWCsJYWkubGJh
ICAgID0gbGJhOwpYKwltZW1zZXQoIGFpLmtleWNoYWwsIDAsIDEwKTsKWCsKWCsJaWYgKGlvY3Rs
KCBmZCwgRFZESU9DUkVQT1JUS0VZLCAmYWkpKSB7ClgrCQlwZXJyb3IoICJHZXRUaXRsZUtleSBm
YWlsZWQiKTsKWCsJCXJldHVybiAtMTsKWCsJfQpYKyAKWCsJZm9yKCBpPTA7IGk8TEVOX0tFWTsg
aSsrKQpYKwkJYWkua2V5Y2hhbFtpXSBePSBrZXlbNCAtIChpJUxFTl9LRVkpXTsKWCsKWCsJX0NT
U1ByaW50RGVidWdCeXRlcyggIlJlY2VpdmVkIFRpdGxlIEtleSIsIGFpLmtleWNoYWwsIExFTl9L
RVkpOwpYKwlfQ1NTUHJpbnREZWJ1ZygiIENQTT0lZCwgQ1BfU0VDPSVkLCBDR01TPSVkXG4iLCBh
aS5jcG0sIGFpLmNwX3NlYywgYWkuY2dtcyk7ClgrClgrCW1lbWNweSgga2V5X3RpdGxlLCBhaS5r
ZXljaGFsLCBMRU5fS0VZKTsKWCsjZW5kaWYKWCAKWCAJcmV0dXJuIDA7ClggfQpYQEAgLTE4OSw2
ICsyMzgsNyBAQApYIHsKWCAJZHZkX2F1dGhpbmZvIGFpOwpYIApYKyNpZm5kZWYgX19GcmVlQlNE
X18KWCAJYWkudHlwZSA9IERWRF9MVV9TRU5EX0FTRjsKWCAJYWkubHNhc2YuYXNmID0gMDsKWCAK
WEBAIC0xOTgsNiArMjQ4LDE2IEBAClggCQkJcmV0dXJuIDA7ClggCQl9ClggCX0KWCsjZWxzZQpY
KwlhaS5mb3JtYXQgPSBEVkRfUkVQT1JUX0FTRjsKWCsJYWkuYWdpZCAgID0gMDsKWCsJYWkuYXNm
ICAgID0gMDsKWCsKWCsJaWYgKCEoaW9jdGwoZmQsIERWRElPQ1JFUE9SVEtFWSwgJmFpKSkpIHsK
WCsJCV9DU1NQcmludERlYnVnICgiJXNBdXRoZW50aWNhdGVkXG4iLCAoYWkuYXNmKSA/ICIiIDog
Im5vdCIpOwpYKwkJcmV0dXJuIDA7ClgrCX0KWCsjZW5kaWYKWCAJcGVycm9yICgiR2V0QVNGIik7
ClggCXJldHVybiAtMTsKWCB9ClhAQCAtMjE0LDE4ICsyNzQsMzQgQEAKWCAKWCAJLyogSW5pdCBz
ZXF1ZW5jZSwgcmVxdWVzdCBBR0lEICovClggCWZvciAodHJpZXMgPSAxOyB0cmllcyA8IDQ7ICsr
dHJpZXMpIHsKWC0JCV9DU1NQcmludERlYnVnICgiUmVxdWVzdCBBR0lEIFslZF0uLi5cbiIsIHRy
aWVzKTsKWCsJCV9DU1NQcmludERlYnVnICgiUmVxdWVzdCBBR0lEIFslZF0uLi4iLCB0cmllcyk7
ClgrI2lmbmRlZiBfX0ZyZWVCU0RfXwpYIAkJYWktPnR5cGUgPSBEVkRfTFVfU0VORF9BR0lEOwpY
IAkJYWktPmxzYS5hZ2lkID0gMDsKWCAJCXJ2ID0gIGlvY3RsIChmZCwgRFZEX0FVVEgsIGFpKTsK
WCsjZWxzZQpYKwkJYWktPmZvcm1hdCA9IERWRF9SRVBPUlRfQUdJRDsKWCsJCWFpLT5hZ2lkICAg
PSAwOwpYKwkJcnYgICAgICAgICA9IGlvY3RsKCBmZCwgRFZESU9DUkVQT1JUS0VZLCBhaSk7Clgr
I2VuZGlmClggCQlpZiAocnYgIT0gLTEpIHsKWCAJCQkvLyBmb3VuZCBrZXkKWCsJCQlfQ1NTUHJp
bnREZWJ1ZyggIkFHSUQgJWRcbiIsIGFpLT5hZ2lkKTsKWCAJCQlyZXR1cm4oIHRyaWVzKTsKWCAJ
CX0KWCsJCWVsc2UgewpYKwkJCV9DU1NQcmludERlYnVnKCJcbiIpOwpYKwkJfQpYIAkJcGVycm9y
ICgiTi9BLCBpbnZhbGlkYXRpbmciKTsKWCsjaWZuZGVmIF9fRnJlZUJTRF9fClggCQlhaS0+dHlw
ZSA9IERWRF9JTlZBTElEQVRFX0FHSUQ7ClggCQlhaS0+bHNhLmFnaWQgPSAwOwpYIAkJaW9jdGwg
KGZkLCBEVkRfQVVUSCwgYWkpOwpYKyNlbHNlClgrCQlhaS0+Zm9ybWF0ID0gRFZEX0lOVkFMSURB
VEVfQUdJRDsKWCsJCWFpLT5hZ2lkICAgPSAwOwpYKwkJaW9jdGwgKGZkLCBEVkRJT0NSRVBPUlRL
RVksIGFpKTsKWCsjZW5kaWYKWCAJfQpYIApYIAlfQ1NTUHJpbnREZWJ1ZyAoIkNhbm5vdCBnZXQg
QUdJRFxuIik7ClhAQCAtMjM0LDYgKzMxMCw3IEBAClggfQpYIApYIApYKyNpZm5kZWYgX19GcmVl
QlNEX18KWCAvKioKWCAgKiBTaW11bGF0aW9uIG9mIGEgbm9uLUNTUyBjb21wbGlhbnQgaG9zdCAo
aS5lLiB0aGUgYXV0aGVudGljYXRpb24gZmFpbHMsClggICogYnV0IGlkZWEgaXMgaGVyZSBmb3Ig
YSByZWFsIENTUyBjb21wbGlhbnQgYXV0aGVudGljYXRpb24gc2NoZW1lKS4KWEBAIC0yNjcsNyAr
MzQ0LDcgQEAKWCAKWCAJCV9DU1NQcmludERlYnVnQnl0ZXMgKCJMVSBzZW50IGNoYWxsZW5nZSIs
IGFpLT5oc2MuY2hhbCwgMTApOwpYIApYLQkJQ3J5cHRLZXkyIChkaXNjLT52YXJpZW50LCBkaXNj
LT5DaGFsbGVuZ2UsIGRpc2MtPktleTIpOwpYKwkJQ3J5cHRLZXkyIChkaXNjLT52YXJpYW50LCBk
aXNjLT5DaGFsbGVuZ2UsIGRpc2MtPktleTIpOwpYIAkJYWktPnR5cGUgPSBEVkRfSE9TVF9TRU5E
X0tFWTI7ClggCQlicmVhazsKWCAKWEBAIC0yOTgsNiArMzc1LDcgQEAKWCAKWCAJcmV0dXJuIDA7
ClggfQpYKyNlbmRpZgpYIApYIApYIC8qKgpYQEAgLTMxOSw2ICszOTcsNyBAQApYIAlmb3IgKGkg
PSAwOyBpIDwgMTA7ICsraSkKWCAJCWRpc2MtPkNoYWxsZW5nZVtpXSA9IGk7ClggClgrI2lmbmRl
ZiBfX0ZyZWVCU0RfXwpYIAkvKiBTZW5kIEFHSUQgdG8gaG9zdCAqLwpYIAlpZiAoX0NTU0F1dGhI
b3N0KCZhaSwgZGlzYykgPCAwKSB7ClggCQlfQ1NTUHJpbnREZWJ1ZyAoIlNlbmQgQUdJRCB0byBo
b3N0IGZhaWxlZFxuIik7ClhAQCAtMzcwLDEwICs0NDksODUgQEAKWCAJCV9DU1NQcmludERlYnVn
ICgiRFZEIGlzIGF1dGhlbnRpY2F0ZWRcbiIpOwpYIAllbHNlIGlmIChhaS50eXBlID09IERWRF9B
VVRIX0ZBSUxVUkUpClggCQlfQ1NTUHJpbnREZWJ1ZyAoIkRWRCBhdXRoZW50aWNhdGlvbiBmYWls
ZWRcbiIpOwpYKyNlbHNlClgrCWFnaWQgPSBhaS5hZ2lkOwpYKwpYKwkvKiBHZXQgY2hhbGxlbmdl
IGZyb20gaG9zdCAqLwpYKwpYKwlhaS5mb3JtYXQgPSBEVkRfU0VORF9DSEFMTEVOR0U7ClgrCWZv
ciAoaT0wOyBpPDEwOyArK2kpClgrCQlhaS5rZXljaGFsWzktaV0gPSBkaXNjLT5DaGFsbGVuZ2Vb
aV07ClgrClgrCV9DU1NQcmludERlYnVnKCJIb3N0IHNlbmRpbmcgY2hhbGxlbmdlOiAiKTsKWCsJ
X0NTU1ByaW50Qnl0ZXMoYWkua2V5Y2hhbCwgMTApOwpYKwlfQ1NTUHJpbnREZWJ1ZygiXG4iKTsK
WCsKWCsJLyogU2VuZCBjaGFsbGVuZ2UgdG8gTFUgKi8KWCsKWCsJaWYgKGlvY3RsKGZkLCBEVkRJ
T0NTRU5ES0VZLCAmYWkpIDwgMCkgewpYKwkJX0NTU1ByaW50RGVidWcoIlNlbmQgY2hhbGxlbmdl
IHRvIExVIGZhaWxlZFxuIik7ClgrCQlyZXR1cm4gLTE7ClgrCX0KWCsKWCsJLyogR2V0IGtleTEg
ZnJvbSBMVSAqLwpYKwpYKwlhaS5mb3JtYXQgPSBEVkRfUkVQT1JUX0tFWTE7ClgrCWlmIChpb2N0
bChmZCwgRFZESU9DUkVQT1JUS0VZLCAmYWkpIDwgMCkgewpYKwkJX0NTU1ByaW50RGVidWcoIkdl
dCBrZXkxIGZyb20gTFUgZmFpbGVkXG4iKTsKWCsJCXJldHVybiAtMTsKWCsJfQpYKwpYKwkvKiBT
ZW5kIGtleTEgdG8gaG9zdCAqLwpYKwpYKwlfQ1NTUHJpbnREZWJ1ZygiTFUgc2VudCBrZXkxOiAi
KTsKWCsJX0NTU1ByaW50Qnl0ZXMoYWkua2V5Y2hhbCwgTEVOX0tFWSk7ClgrCV9DU1NQcmludERl
YnVnKCJcbiIpOwpYKwpYKwlpZiAoX0NTU0F1dGhEcml2ZSggYWkua2V5Y2hhbCwgZGlzYykgPCAw
KSB7ClgrCQlfQ1NTUHJpbnREZWJ1ZygiU2VuZCBrZXkxIHRvIGhvc3QgZmFpbGVkXG4iKTsKWCsJ
CXJldHVybiAtMTsKWCsJfQpYKwpYKwkvKiBHZXQgY2hhbGxlbmdlIGZyb20gTFUgKi8KWCsKWCsJ
YWkuZm9ybWF0ID0gRFZEX1JFUE9SVF9DSEFMTEVOR0U7ClgrCWlmIChpb2N0bChmZCwgRFZESU9D
UkVQT1JUS0VZLCAmYWkpIDwgMCkgewpYKwkJX0NTU1ByaW50RGVidWcoIkdldCBjaGFsbGVuZ2Ug
ZnJvbSBMVSBmYWlsZWRcbiIpOwpYKwkJcmV0dXJuIC0xOwpYKwl9ClgrClgrCS8qIFNlbmQgY2hh
bGxlbmdlIHRvIGhvc3QgKi8KWCsKWCsJZm9yIChpPTA7IGk8MTA7ICsraSkKWCsJCWRpc2MtPkNo
YWxsZW5nZVtpXSA9IGFpLmtleWNoYWxbOS1pXTsKWCsKWCsJX0NTU1ByaW50RGVidWcoIkxVIHNl
bnQgY2hhbGxlbmdlOiAiKTsKWCsJX0NTU1ByaW50Qnl0ZXMoZGlzYy0+Q2hhbGxlbmdlLCAxMCk7
ClgrCV9DU1NQcmludERlYnVnKCJcbiIpOwpYKwpYKwlDcnlwdEtleTIoZGlzYy0+dmFyaWFudCwg
ZGlzYy0+Q2hhbGxlbmdlLCBkaXNjLT5LZXkyKTsKWCsKWCsJLyogR2V0IGtleTIgZnJvbSBob3N0
ICovClgrClgrCWFpLmZvcm1hdCA9IERWRF9TRU5EX0tFWTI7ClgrCWZvciAoaT0wOyBpPExFTl9L
RVk7ICsraSkKWCsJCWFpLmtleWNoYWxbNC1pXSA9IGRpc2MtPktleTJbaV07ClgrClgrCV9DU1NQ
cmludERlYnVnKCJIb3N0IHNlbmRpbmcga2V5IDI6ICIpOwpYKwlfQ1NTUHJpbnRCeXRlcyhkaXNj
LT5LZXkyLCBMRU5fS0VZKTsKWCsJX0NTU1ByaW50RGVidWcoIlxuIik7ClgrClgrCS8qIFNlbmQg
a2V5MiB0byBMVSAqLwpYKwlpZiAoaW9jdGwoZmQsIERWRElPQ1NFTkRLRVksICZhaSkgPCAwKSB7
ClgrCQlwcmludGYoIlNlbmQga2V5MiB0byBMVSBmYWlsZWQgKGV4cGVjdGVkKVxuIik7ClgrCQly
ZXR1cm4gLTE7ClgrCX0KWCsKWCsjZW5kaWYKWCAKWCAJbWVtY3B5IChkaXNjLT5DaGFsbGVuZ2Us
IGRpc2MtPktleTEsIExFTl9LRVkpOwpYIAltZW1jcHkgKGRpc2MtPkNoYWxsZW5nZStMRU5fS0VZ
LCBkaXNjLT5LZXkyLCBMRU5fS0VZKTsKWC0JQ3J5cHRCdXNLZXkgKGRpc2MtPnZhcmllbnQsIGRp
c2MtPkNoYWxsZW5nZSwgZGlzYy0+S2V5Q2hlY2spOwpYKwlDcnlwdEJ1c0tleSAoZGlzYy0+dmFy
aWFudCwgZGlzYy0+Q2hhbGxlbmdlLCBkaXNjLT5LZXlDaGVjayk7ClggClggCV9DU1NQcmludERl
YnVnQnl0ZXMgKCJSZWNlaXZlZCBTZXNzaW9uIEtleVxuIiwgJmRpc2MtPktleUNoZWNrWzBdLCBM
RU5fS0VZKTsKWCAKWEBAIC00NDUsNiArNTk5LDcgQEAKWCB7ClggCWR2ZF9zdHJ1Y3QgZHZkOwpY
IApYKyNpZm5kZWYgX19GcmVlQlNEX18KWCAJZHZkLmNvcHlyaWdodC50eXBlID0gRFZEX1NUUlVD
VF9DT1BZUklHSFQ7ClggCWR2ZC5jb3B5cmlnaHQubGF5ZXJfbnVtID0gMDsKWCAKWEBAIC00NTQs
NCArNjA5LDE1IEBAClggCX0KWCAKWCAJcmV0dXJuIGR2ZC5jb3B5cmlnaHQuY3BzdDsgICAgICAv
LyAwIC4uLiBub3QgZW5jcnlwdGVkClgrI2Vsc2UKWCsJZHZkLmZvcm1hdCAgICA9IERWRF9TVFJV
Q1RfQ09QWVJJR0hUOwpYKwlkdmQubGF5ZXJfbnVtID0gMDsKWCsKWCsJaWYgKGlvY3RsKCBmZCwg
RFZESU9DUkVBRFNUUlVDVFVSRSwgJmR2ZCkgPCAwKSB7ClgrCQlfQ1NTUHJpbnREZWJ1ZyAoImVy
cm9yIHVzaW5nIGlvY3RsIERWRElPQ1JFQURTVFJVQ1RVUkVcbiIpOwpYKwkJcmV0dXJuIC0xOwpY
Kwl9ClgrClgrCXJldHVybiBkdmQuY3BzdDsgICAgICAgICAgICAgICAgLy8gMCAuLi4gbm90IGVu
Y3J5cHRlZApYKyNlbmRpZgpYIH0KRU5ELW9mLWxpYmNzcy9maWxlcy9wYXRjaC1hYwplY2hvIHgg
LSBsaWJjc3MvZmlsZXMvcGF0Y2gtYWQKc2VkICdzL15YLy8nID5saWJjc3MvZmlsZXMvcGF0Y2gt
YWQgPDwgJ0VORC1vZi1saWJjc3MvZmlsZXMvcGF0Y2gtYWQnClgtLS0gc3JjL2Nzc19jYXQuYy5v
cmlnCVR1ZSBGZWIgMTMgMTY6NTk6MjcgMjAwMQpYKysrIHNyYy9jc3NfY2F0LmMJV2VkIEp1biAy
MCAxNjozMzoyNCAyMDAxClhAQCAtMjA4LDcgKzIwOCw5IEBAClggICoKWCAgKi8KWCAKWCsjaWZk
ZWYgX19saW51eF9fClggI2luY2x1ZGUgPGxpbnV4L2ZzLmg+ClgrI2VuZGlmClggClggaW50IHBh
dGhfdG9fbGJhIChjaGFyICpwKQpYIHsKWEBAIC0yMTksOCArMjIxLDEzIEBAClggCQlyZXR1cm4g
LTE7ClggCX0KWCAKWCsjaWZuZGVmIF9fRnJlZUJTRF9fClggCWlmIChpb2N0bChmZCwgRklCTUFQ
LCAmbGJhKSA8IDApIHsKWCAJCXBlcnJvciAoImlvY3RsIEZJQk1BUCIpOwpYKyNlbHNlClgrCWlm
IChpb2N0bChmZCwgRklPR0VUTEJBLCAmbGJhKSA8IDApIHsKWCsJCXBlcnJvciAoImlvY3RsIEZJ
T0dFVExCQSIpOwpYKyNlbmRpZgpYIAkJY2xvc2UoZmQpOwpYIAkJcmV0dXJuIC0xOwpYIAl9ClhA
QCAtMjUyLDYgKzI1OSwxNCBAQApYIAkJZ290byBjbGVhbl91cDsKWCAJfQpYICNlbmRpZgpYKwpY
KyNpZmRlZiBfX0ZyZWVCU0RfXwpYKwlpZiAoIXN0cmNtcCggYXJndlthcmdpXSwgIi0iKSkgewpY
KwkJYXJndlthcmdpXSA9IChjaGFyICopbWFsbG9jKCBzdHJsZW4oICIvZGV2L3N0ZGluIikgKyAx
KTsKWCsJCXN0cmNweSggYXJndlthcmdpXSwgIi9kZXYvc3RkaW4iKTsKWCsJfQpYKyNlbmRpZgpY
KwpYIAlpZiAoKGZkID0gb3BlbiAoYXJndlthcmdpXSwgT19SRE9OTFkpKSA9PSAtMSkgewpYIAkJ
cGVycm9yICgiY2FuJ3Qgb3BlbiBEVkQiKTsKWCAJCWdvdG8gY2xlYW5fdXA7CkVORC1vZi1saWJj
c3MvZmlsZXMvcGF0Y2gtYWQKZWNobyB4IC0gbGliY3NzL2ZpbGVzL3BhdGNoLWFlCnNlZCAncy9e
WC8vJyA+bGliY3NzL2ZpbGVzL3BhdGNoLWFlIDw8ICdFTkQtb2YtbGliY3NzL2ZpbGVzL3BhdGNo
LWFlJwpYLS0tIHNyYy9kdmRpbmZvLmMub3JpZwlUdWUgRmViIDEzIDE2OjU5OjI3IDIwMDEKWCsr
KyBzcmMvZHZkaW5mby5jCVdlZCBKdW4gMjAgMTY6NTk6MjQgMjAwMQpYQEAgLTI3LDcgKzI3LDcg
QEAKWCAjaW5jbHVkZSA8c3RkbGliLmg+ClggI2luY2x1ZGUgPGZjbnRsLmg+ClggI2luY2x1ZGUg
PHN0cmluZy5oPgpYLSNpZiBkZWZpbmVkKF9fTmV0QlNEX18pIHx8IGRlZmluZWQoX19PcGVuQlNE
X18pClgrI2lmIGRlZmluZWQoX19OZXRCU0RfXykgfHwgZGVmaW5lZChfX09wZW5CU0RfXykgfHwg
ZGVmaW5lZChfX0ZyZWVCU0RfXykKWCAjIGluY2x1ZGUgPHN5cy9kdmRpby5oPgpYICNlbGlmIGRl
ZmluZWQoX19saW51eF9fKQpYICMgaW5jbHVkZSA8bGludXgvY2Ryb20uaD4KWEBAIC0zOSw2ICsz
OSwxMCBAQApYIApYICNpbmNsdWRlICJjc3MuaCIKWCAKWCsjaWZkZWYgX19GcmVlQlNEX18KWCt0
eXBlZGVmIHN0cnVjdCBkdmRfc3RydWN0IGR2ZF9zdHJ1Y3Q7ClgrI2VuZGlmClgrClggI2RlZmlu
ZSBEVkQJIi9kZXYvY2Ryb20iClggClggLyoqClhAQCAtNTIsNiArNTYsNyBAQApYIAlpbnQgaTsK
WCAJaW50IGxheWVycyA9IDQ7ClggClgrI2lmbmRlZiBfX0ZyZWVCU0RfXwpYIAlkLnBoeXNpY2Fs
LnR5cGUgPSBEVkRfU1RSVUNUX1BIWVNJQ0FMOwpYIAlmb3IgKGk9MDsgaTxsYXllcnM7IGkrKykg
ewpYIAkJZC5waHlzaWNhbC5sYXllcl9udW0gPSBpOwpYQEAgLTYyLDEyICs2NywyOCBAQApYIAkJ
fQpYIApYIAkJbGF5ZXIgPSAmZC5waHlzaWNhbC5sYXllcltpXTsKWCsjZWxzZQpYKwlkLmZvcm1h
dCA9IERWRF9TVFJVQ1RfUEhZU0lDQUw7ClgrCW1lbXNldCggZC5kYXRhLCAwLCAyMDQ4KTsKWCsJ
Zm9yIChpPTA7IGk8bGF5ZXJzOyBpKyspIHsKWCsJCWQubGF5ZXJfbnVtID0gaTsKWCsJCWlmIChp
b2N0bCAoZmQsIERWRElPQ1JFQURTVFJVQ1RVUkUsICZkKTwwKSB7ClgrCQkJZnByaW50ZiAoc3Rk
ZXJyLCAiQ291bGQgbm90IHJlYWQgUGh5c2ljYWwgbGF5ZXIgJWRcbiIsIGkpOwpYKwkJCXJldHVy
biAwOwpYKwkJfQpYKwpYKwkJbGF5ZXIgPSAoc3RydWN0IGR2ZF9sYXllciAqKSgmKGQuZGF0YVtp
KnNpemVvZihzdHJ1Y3QgZHZkX2xheWVyKV0pKTsKWCsjZW5kaWYKWCAJCWxheWVycyA9IGxheWVy
LT5ubGF5ZXJzICsgMTsKWCAKWCAJCXByaW50ZiAoIkxheWVyICVkWyVkXVxuIiwgaSwgbGF5ZXJz
KTsKWCAJCXByaW50ZiAoIiBCb29rIFZlcnNpb246ICAgJWRcbiIsIGxheWVyLT5ib29rX3ZlcnNp
b24pOwpYIAkJcHJpbnRmICgiIEJvb2sgVHlwZTogICAgICAlZFxuIiwgbGF5ZXItPmJvb2tfdHlw
ZSk7ClgrI2lmbmRlZiBfX0ZyZWVCU0RfXwpYIAkJcHJpbnRmICgiIE1pbiBSYXRlOiAgICAgICAl
ZFxuIiwgbGF5ZXItPm1pbl9yYXRlKTsKWCsjZWxzZQpYKwkJcHJpbnRmICgiIE1heCBSYXRlOiAg
ICAgICAlZFxuIiwgbGF5ZXItPm1heF9yYXRlKTsKWCsjZW5kaWYKWCAJCXByaW50ZiAoIiBEaXNj
IFNpemU6ICAgICAgJWRcbiIsIGxheWVyLT5kaXNjX3NpemUpOwpYIAkJcHJpbnRmICgiIExheWVy
IFR5cGU6ICAgICAlZFxuIiwgbGF5ZXItPmxheWVyX3R5cGUpOwpYIAkJcHJpbnRmICgiIFRyYWNr
IFBhdGg6ICAgICAlZFxuIiwgbGF5ZXItPnRyYWNrX3BhdGgpOwpYQEAgLTkyLDYgKzExMyw3IEBA
ClggewpYIAlkdmRfc3RydWN0IGQ7ClggClgrI2lmbmRlZiBfX0ZyZWVCU0RfXwpYIAlkLmNvcHly
aWdodC50eXBlID0gRFZEX1NUUlVDVF9DT1BZUklHSFQ7ClggCWQuY29weXJpZ2h0LmxheWVyX251
bSA9IDA7ClggCQpYQEAgLTEwMSw2ICsxMjMsMTcgQEAKWCAJfQpYIApYIAlwcmludGYgKCJDb3B5
cmlnaHQ6IENQU1Q9JWQsIFJNST0lIzAyeFxuIiwgZC5jb3B5cmlnaHQuY3BzdCwgZC5jb3B5cmln
aHQucm1pKTsKWCsjZWxzZQpYKwlkLmZvcm1hdCAgICA9IERWRF9TVFJVQ1RfQ09QWVJJR0hUOwpY
KwlkLmxheWVyX251bSA9IDA7ClgrClgrCWlmIChpb2N0bChmZCwgRFZESU9DUkVBRFNUUlVDVFVS
RSwgJmQpPDApIHsKWCsJCWZwcmludGYgKHN0ZGVyciwgIkNvdWxkIG5vdCByZWFkIENvcHlyaWdo
dCBTdHJ1Y3RcbiIpOwpYKwkJcmV0dXJuIDA7ClgrCX0KWCsKWCsJcHJpbnRmICgiQ29weXJpZ2h0
OiBDUFNUPSVkLCBSTUk9JSMwMnhcbiIsIGQuY3BzdCwgZC5ybWkpOwpYKyNlbmRpZgpYIApYIAly
ZXR1cm4gMTsKWCB9ClhAQCAtMTE0LDYgKzE0Nyw3IEBAClggewpYIAlkdmRfc3RydWN0IGR2ZDsK
WCAKWCsjaWZuZGVmIF9fRnJlZUJTRF9fClggCWR2ZC5jb3B5cmlnaHQudHlwZSA9IERWRF9TVFJV
Q1RfQ09QWVJJR0hUOwpYIAlkdmQuY29weXJpZ2h0LmxheWVyX251bSA9IDA7ClggClhAQCAtMTI1
LDYgKzE1OSwxOSBAQApYIAlwcmludGYgKCJEaXNjIGlzICVzXG4iLCBkdmQuY29weXJpZ2h0LmNw
c3QgPyAiZW5jcnlwdGVkLiIgOiAiTk9UIGVuY3J5cHRlZCBhdCBhbGwgLSBubyBuZWVkIHRvIHVz
ZSBDU1MhISEiKTsKWCAKWCAJcmV0dXJuIGR2ZC5jb3B5cmlnaHQuY3BzdDsKWCsjZWxzZQpYKwlk
dmQuZm9ybWF0ID0gRFZEX1NUUlVDVF9DT1BZUklHSFQ7ClgrCWR2ZC5sYXllcl9udW0gPSAwOwpY
KwpYKwlpZiAoaW9jdGwgKGZkLCBEVkRJT0NSRUFEU1RSVUNUVVJFLCAmZHZkKSA8IDApIHsKWCsJ
CXBlcnJvciAoIkRWRElPQ1JFQURTVFJVQ1RVUkUiKTsKWCsJCXJldHVybiAtMTsKWCsJfQpYKwpY
KwlwcmludGYoICJEaXNjIGlzICVzXG4iLCBkdmQuY3BzdCA/ICJlbmNyeXB0ZWQuIiA6ICJOT1Qg
ZW5jcnlwdGVkIGF0IGFsbCAtIG5vIG5lZWQgdG8gdXNlIENTUyEhISIpOwpYKwpYKwlyZXR1cm4g
ZHZkLmNwc3Q7ClgrI2VuZGlmClggfQpYIApYIApFTkQtb2YtbGliY3NzL2ZpbGVzL3BhdGNoLWFl
CmVjaG8geCAtIGxpYmNzcy9maWxlcy9wYXRjaC1hZgpzZWQgJ3MvXlgvLycgPmxpYmNzcy9maWxl
cy9wYXRjaC1hZiA8PCAnRU5ELW9mLWxpYmNzcy9maWxlcy9wYXRjaC1hZicKWC0tLSBzcmMvcmVz
ZXRfZHZkLmMub3JpZwlUdWUgRmViIDEzIDE2OjU5OjI3IDIwMDEKWCsrKyBzcmMvcmVzZXRfZHZk
LmMJCVdlZCBKdW4gMjAgMTY6NTk6MzggMjAwMQpYQEAgLTI1LDcgKzI1LDcgQEAKWCAjaW5jbHVk
ZSA8c3RkaW8uaD4KWCAjaW5jbHVkZSA8c3RyaW5nLmg+ClggI2luY2x1ZGUgPGZjbnRsLmg+Clgt
I2lmIGRlZmluZWQoX19OZXRCU0RfXykgfHwgZGVmaW5lZChfX09wZW5CU0RfXykKWCsjaWYgZGVm
aW5lZChfX05ldEJTRF9fKSB8fCBkZWZpbmVkKF9fT3BlbkJTRF9fKSB8fCBkZWZpbmVkKF9fRnJl
ZUJTRF9fKQpYICMgaW5jbHVkZSA8c3lzL2R2ZGlvLmg+ClggI2VsaWYgZGVmaW5lZChfX2xpbnV4
X18pClggIyBpbmNsdWRlIDxsaW51eC9jZHJvbS5oPgpYQEAgLTM3LDYgKzM3LDEwIEBAClggClgg
c3RhdGljIGludCBmZDsKWCAKWCsjaWZkZWYgX19GcmVlQlNEX18KWCt0eXBlZGVmIHN0cnVjdCBk
dmRfYXV0aGluZm8gZHZkX2F1dGhpbmZvOwpYKyNlbmRpZgpYKwpYICNkZWZpbmUgRFZECSIvZGV2
L2Nkcm9tIgpYIApYIGludCBtYWluIChpbnQgYWMsIGNoYXIgKiphdikKWEBAIC01Nyw5ICs2MSwx
NSBAQApYIApYIAlmb3IgKGkgPSAwOyBpIDwgNDsgaSsrKSB7ClggCQltZW1zZXQoJmFpLCAwLCBz
aXplb2YoYWkpKTsKWCsjaWZuZGVmIF9fRnJlZUJTRF9fClggCQlhaS50eXBlID0gRFZEX0lOVkFM
SURBVEVfQUdJRDsKWCAJCWFpLmxzYS5hZ2lkID0gaTsKWCAJCWlvY3RsKGZkLCBEVkRfQVVUSCwg
JmFpKTsKWCsjZWxzZQpYKwkJYWkuZm9ybWF0ID0gRFZEX0lOVkFMSURBVEVfQUdJRDsKWCsJCWFp
LmFnaWQgPSBpOwpYKwkJaW9jdGwoZmQsIERWRElPQ1JFUE9SVEtFWSwgJmFpKTsKWCsjZW5kaWYK
WCAJfQpYIApYIAlyZXR1cm4gMDsKRU5ELW9mLWxpYmNzcy9maWxlcy9wYXRjaC1hZgplY2hvIHgg
LSBsaWJjc3MvZmlsZXMvcGF0Y2hlcy1haApzZWQgJ3MvXlgvLycgPmxpYmNzcy9maWxlcy9wYXRj
aGVzLWFoIDw8ICdFTkQtb2YtbGliY3NzL2ZpbGVzL3BhdGNoZXMtYWgnClgtLS0gbTQvZHZkLm00
Lm9yaWcJVGh1IE5vdiAyMyAxNzoyMToyMiAyMDAwClgrKysgbTQvZHZkLm00CQlXZWQgSnVuIDIw
IDE2OjMzOjI0IDIwMDEKWEBAIC00Miw3ICs0Miw3IEBAClggCQlDRkxBR1M9IiRDRkxBR1MgLUkk
S0VSTkVMX0lOQ0xVREVTIgpYIApYIAkJQUNfVFJZX0NPTVBJTEUoWwpYLQkJCSNpZiBkZWZpbmVk
KF9fTmV0QlNEX18pIHx8IGRlZmluZWQoX19PcGVuQlNEX18pClgrCQkJI2lmIGRlZmluZWQoX19O
ZXRCU0RfXykgfHwgZGVmaW5lZChfX09wZW5CU0RfXykgfHwgZGVmaW5lZChfX0ZyZWVCU0RfXykK
WCAJCQkjIGluY2x1ZGUgPHN5cy9kdmRpby5oPgpYIAkJCSNlbGlmIGRlZmluZWQoX19saW51eF9f
KQpYIAkJCSMgaW5jbHVkZSA8c3lzL3R5cGVzLmg+CkVORC1vZi1saWJjc3MvZmlsZXMvcGF0Y2hl
cy1haAplY2hvIHggLSBsaWJjc3MvZGlzdGluZm8Kc2VkICdzL15YLy8nID5saWJjc3MvZGlzdGlu
Zm8gPDwgJ0VORC1vZi1saWJjc3MvZGlzdGluZm8nClhNRDUgKGxpYmNzcy0wLjEuMC50YXIuZ3op
ID0gZjMyODA3N2Y1NmY2OTBkMDEzNmExMDYwODBjMzU5ZGYKRU5ELW9mLWxpYmNzcy9kaXN0aW5m
bwplY2hvIHggLSBsaWJjc3MvcGtnLWNvbW1lbnQKc2VkICdzL15YLy8nID5saWJjc3MvcGtnLWNv
bW1lbnQgPDwgJ0VORC1vZi1saWJjc3MvcGtnLWNvbW1lbnQnClhMaWJyYXJ5IHRvIGJydXRlIGZv
cmNlIGRlY3J5cHQgZHZkIHZpZGVvcwpFTkQtb2YtbGliY3NzL3BrZy1jb21tZW50CmVjaG8geCAt
IGxpYmNzcy9NYWtlZmlsZQpzZWQgJ3MvXlgvLycgPmxpYmNzcy9NYWtlZmlsZSA8PCAnRU5ELW9m
LWxpYmNzcy9NYWtlZmlsZScKWCMgTmV3IHBvcnRzIGNvbGxlY3Rpb24gbWFrZWZpbGUgZm9yOiAg
IGxpYmNzcwpYIyBEYXRlIGNyZWF0ZWQ6ICAgICAgICAyMCBKdW5lIDIwMDEKWCMgV2hvbTogICAg
ICAgICAgICAgICAgClgjClgjICRGcmVlQlNEJApYIwpYClhQT1JUTkFNRT0JbGliY3NzClhQT1JU
VkVSU0lPTj0JMC4xLjAKWENBVEVHT1JJRVM9CWdyYXBoaWNzClhNQVNURVJfU0lURVM9ICAgaHR0
cDovL3d3dy5saW51eHZpZGVvLm9yZy9vbXMvZGF0YS8KWApYTUFJTlRBSU5FUj0JSmFtZXNfQm9u
ZF83OUB5YWhvby5jb20KWApYSU5TVEFMTFNfU0hMSUI9CXllcwpYClhHTlVfQ09ORklHVVJFPQl5
ZXMKWFVTRV9HTUFLRT0JeWVzClgKWEJVSUxEX0RFUEVORFM9IGF1dG9tYWtlOiR7UE9SVFNESVJ9
L2RldmVsL2F1dG9jb25mClgKWHByZS1jb25maWd1cmU6ClgJQGNkICR7V1JLU1JDfSAmJiBhdXRv
bWFrZQpYClguaW5jbHVkZSA8YnNkLnBvcnQubWs+CkVORC1vZi1saWJjc3MvTWFrZWZpbGUKZXhp
dAoK
--------------Boundary-00=_C7IHYKFQN29DWWVL1GHJ--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 5:25:38 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29])
by hub.freebsd.org (Postfix) with ESMTP id BC3B637B401
for <freebsd-hackers@FreeBSD.ORG>; Mon, 25 Jun 2001 05:25:35 -0700 (PDT)
(envelope-from cmsedore@mailbox.syr.edu)
Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1b) with SMTP id <0.001E6CA0@mailer.syr.edu>; Mon, 25 Jun 2001 8:25:35 -0400
Received: from localhost (cmsedore@localhost)
by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id IAA04130;
Mon, 25 Jun 2001 08:25:34 -0400 (EDT)
X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs
Date: Mon, 25 Jun 2001 08:25:34 -0400 (EDT)
From: Christopher Sedore <cmsedore@mailbox.syr.edu>
X-Sender: cmsedore@rodan.syr.edu
To: Richard Hodges <rh@matriplex.com>
Cc: Josh Osborne <stripes@mac.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: question: aio / nbio / kqueue
In-Reply-To: <Pine.BSF.4.10.10106221717070.63905-100000@mail.matriplex.com>
Message-ID: <Pine.SOL.4.10.10106250822410.3561-100000@rodan.syr.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Fri, 22 Jun 2001, Richard Hodges wrote:
> On Fri, 22 Jun 2001, Josh Osborne wrote:
>
> > On Friday, June 22, 2001, at 07:01 PM, E.B. Dreger wrote:
> > > My question is, from a performance standpoint, in what situations are
> > > these techniques most appropriate?
>
> > AIO is good when you are not receiving much data (or not receiving
> > it very frequently), and presumably want very low latency.
>
> What if you want good performance with "moderate" disk IO, say ten
> to twenty megabytes per second continuously?
>
> I tried AIO some months ago (4.1R or 4.2R), but had some trouble
> with AIO, mainly that it seemed to lose track of half my files.
> Not any particular files, it seemed that at any moment it would
> just pick ten or so (out of maybe 20-25 files) to ignore at any
> given time.
>
I've done this at the 3-6 MB/sec continous (peaks at 10MB+/sec) range with
good success with aio, both the network and disk functions. Never had
trouble with it losing track of files (not sure what you mean here). If
you didn't tweak some of the default sysctl settings, you may have bumped
limits that caused unexpected behaviour (though you should have gotten
error returns to let you know).
-Chris
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 7:38:24 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92])
by hub.freebsd.org (Postfix) with ESMTP
id D030037B407; Mon, 25 Jun 2001 07:38:17 -0700 (PDT)
(envelope-from dfr@nlsystems.com)
Received: from [62.49.251.130] (helo=herring.nlsystems.com)
by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1)
id 15EXUq-000PhC-0Y; Mon, 25 Jun 2001 15:37:48 +0100
Received: from herring (herring [10.0.0.2])
by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f5PEb1788591;
Mon, 25 Jun 2001 15:37:01 +0100 (BST)
(envelope-from dfr@nlsystems.com)
Date: Mon, 25 Jun 2001 15:37:00 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Arun Sharma <arun@sharmas.dhs.org>
Cc: <freebsd-hackers@freebsd.org>, <freebsd-mobile@freebsd.org>
Subject: Re: libwi and KWireless
In-Reply-To: <20010625002842.A23058@sharmas.dhs.org>
Message-ID: <Pine.BSF.4.33.0106251535080.88301-100000@herring.nlsystems.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Mon, 25 Jun 2001, Arun Sharma wrote:
> KWireless is a KDE kicker applet to display the signal qualtiy of a IEEE
> 802.11b wireless network.
>
> http://www.sharma-home.net/~adsharma/projects/KWireless/
>
> It depends on libwi, a library version of wicontrol(8).
>
> http://www.sharma-home.net/~adsharma/projects/libwi/
>
> I know this is not in a commitable state and would appreciate some
> feedback on what I need to do, before it can be commited.
I can't configure it. It doesn't contain a configure script and autoconf
doesn't seem to like the (possible misnamed?) configure.in.in file. This
is from 4.3-stable with autoconf-2.13_1.
--
Doug Rabson Mail: dfr@nlsystems.com
Phone: +44 20 8348 6160
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 7:53:54 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from imo-r10.mx.aol.com (imo-r10.mx.aol.com [152.163.225.106])
by hub.freebsd.org (Postfix) with ESMTP id 7604B37B405
for <hackers@freebsd.org>; Mon, 25 Jun 2001 07:53:51 -0700 (PDT)
(envelope-from Bsdguru@aol.com)
Received: from Bsdguru@aol.com
by imo-r10.mx.aol.com (mail_out_v30.22.) id n.107.1bc2228 (4239)
for <hackers@freebsd.org>; Mon, 25 Jun 2001 10:53:46 -0400 (EDT)
From: Bsdguru@aol.com
Message-ID: <107.1bc2228.2868aa7a@aol.com>
Date: Mon, 25 Jun 2001 10:53:46 EDT
Subject: Re: Status of encryption hardware support in FreeBSD
To: hackers@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 5.0 for Windows sub 139
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In a message dated 06/24/2001 2:53:32 PM Eastern Daylight Time,
soren@soekris.com writes:
> And btw, hardware beats software anytime. The fastest PC processor right
> now is about the same speed as the slowest hardware.
what are the numbers? Are you accounting for the overhead in accessing the
hardware? the impact of the stop-and-wait requirements for hardware
processing? What about bus availability in a heavily utilized router? You are
going to double the bus requirement.
Most people take a rather trivial approach to such evaluations, and i suppose
im concerned about anyone who thinks that hardware is "always faster" than
software, because that argument is blatently wrong. a 33Mhz ASIC will not
always be faster than the host, particularly with transfer and setup
requirements. It has to be 3-5 times faster than the host just to break even.
Bryan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 7:59:43 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
by hub.freebsd.org (Postfix) with ESMTP id 0CB4B37B407
for <freebsd-hackers@freebsd.org>; Mon, 25 Jun 2001 07:59:39 -0700 (PDT)
(envelope-from jcm@freebsd-uk.eu.org)
Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root)
by serenity.mcc.ac.uk with esmtp (Exim 2.05 #6)
id 15EXpy-0009ES-00; Mon, 25 Jun 2001 15:59:38 +0100
Received: (from jcm@localhost)
by dogma.freebsd-uk.eu.org (8.11.3/8.11.1) id f5PExbK50333;
Mon, 25 Jun 2001 15:59:37 +0100 (BST)
(envelope-from jcm)
Date: Mon, 25 Jun 2001 15:59:36 +0100
From: j mckitrick <jcm@FreeBSD-uk.eu.org>
To: Matthew Jacob <mjacob@feral.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: how to invalidate scsi connection to driver module
Message-ID: <20010625155936.A50235@dogma.freebsd-uk.eu.org>
References: <20010623145429.D29940@ringworld.oblivion.bg> <Pine.BSF.4.21.0106231038440.79651-100000@beppo.feral.com> <20010623200945.A96038@dogma.freebsd-uk.eu.org> <20010623225536.B564@ringworld.oblivion.bg>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20010623225536.B564@ringworld.oblivion.bg>; from roam@orbitel.bg on Sat, Jun 23, 2001 at 10:55:36PM +0300
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
When using PCMCIA SCSI, how is the device destroyed when the card is
unloaded, so that the device can be re-created when the card is re-inserted
and the filesystem re-mounted?
Jonathon
--
Microsoft complaining about the source license used by
Linux is like the event horizon calling the kettle black.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 8: 5:34 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from beppo.feral.com (beppo.feral.com [192.67.166.79])
by hub.freebsd.org (Postfix) with ESMTP id A3B8537B40A
for <freebsd-hackers@FreeBSD.ORG>; Mon, 25 Jun 2001 08:05:29 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from beppo (mjacob@beppo [192.67.166.79])
by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f5PF2ng84172;
Mon, 25 Jun 2001 08:02:50 -0700 (PDT)
(envelope-from mjacob@feral.com)
Date: Mon, 25 Jun 2001 08:02:49 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: j mckitrick <jcm@freebsd-uk.eu.org>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: how to invalidate scsi connection to driver module
In-Reply-To: <20010625155936.A50235@dogma.freebsd-uk.eu.org>
Message-ID: <Pine.BSF.4.21.0106250802270.84115-100000@beppo.feral.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Umm- I dunno! Maybe you oughta look at the umass driver for USB as well..?
On Mon, 25 Jun 2001, j mckitrick wrote:
>
> When using PCMCIA SCSI, how is the device destroyed when the card is
> unloaded, so that the device can be re-created when the card is re-inserted
> and the filesystem re-mounted?
>
> Jonathon
> --
> Microsoft complaining about the source license used by
> Linux is like the event horizon calling the kettle black.
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 8:24:54 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from supernova.dimensional.com (supernova.dimensional.com [206.124.0.11])
by hub.freebsd.org (Postfix) with ESMTP id 8C75A37B406
for <hackers@FreeBSD.ORG>; Mon, 25 Jun 2001 08:24:52 -0700 (PDT)
(envelope-from element@Dim.com)
Received: from smtp.dimensional.com (64-204-110-66.client.dsl.net [64.204.110.66])
by supernova.dimensional.com (8.11.2/8.11.2) with SMTP id f5PFOo911216
for <hackers@FreeBSD.ORG>; Mon, 25 Jun 2001 09:24:50 -0600 (MDT)
Message-Id: <200106251524.f5PFOo911216@supernova.dimensional.com>
X-Mailer: Ultrafunk Popcorn release 1.04 (13.Jan.2001)
X-URL: http://www.ultrafunk.com/products/popcorn
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=iso-8859-1
Date: Mon, 25 Jun 2001 09:19:08 -0700 (Mountain Standard Time)
From: Adam <element@Dim.com>
To: hackers@FreeBSD.ORG
Subject: Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
Organization: NA
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
>> Can you substantiate your claim there is "plenty of GNU stuff" in
>> Interix, or are you just talking out your ass as usual?
Substantiate? Look at the component list:
http://www.microsoft.com/windows2000/interix/features.asp
>Why should I substantiate it? Do it yourself if it bothers you.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 8:42: 7 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119])
by hub.freebsd.org (Postfix) with ESMTP
id 2CFF237B401; Mon, 25 Jun 2001 08:42:02 -0700 (PDT)
(envelope-from adsharma@sharmas.dhs.org)
Received: by sharmas.dhs.org (Postfix, from userid 500)
id 133945E06E; Mon, 25 Jun 2001 08:42:07 -0700 (PDT)
Date: Mon, 25 Jun 2001 08:42:07 -0700
From: Arun Sharma <arun@sharmas.dhs.org>
To: Doug Rabson <dfr@nlsystems.com>
Cc: freebsd-hackers@freebsd.org, freebsd-mobile@freebsd.org
Subject: Re: libwi and KWireless
Message-ID: <20010625084206.A25446@sharmas.dhs.org>
References: <20010625002842.A23058@sharmas.dhs.org> <Pine.BSF.4.33.0106251535080.88301-100000@herring.nlsystems.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.15i
In-Reply-To: <Pine.BSF.4.33.0106251535080.88301-100000@herring.nlsystems.com>; from dfr@nlsystems.com on Mon, Jun 25, 2001 at 03:37:00PM +0100
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Mon, Jun 25, 2001 at 03:37:00PM +0100, Doug Rabson wrote:
> I can't configure it. It doesn't contain a configure script and autoconf
> doesn't seem to like the (possible misnamed?) configure.in.in file. This
> is from 4.3-stable with autoconf-2.13_1.
Try
$ gmake -f Makefile.dist
$ cat ~/bin/kdeconfig
MOC=moc2 LIBQT=-lqt2 ./configure --with-extra-libs=/usr/local/lib
--with-qt-includes=/usr/X11R6/include/qt2
--with-extra-includes=/usr/local/include --prefix=/usr/local
--with-qt-libraries=/usr/X11R6/lib
$ kdeconfig
$ make
# make install
The above configure line corresponds to a normal 4.3-stable box with
the basic KDE ports installed.
Once installed, K -> configure panel -> Add -> Applet -> Kwireless
should display an icon in your panel.
Let me know if you're having trouble with Makefile.dist. I'll put up
a tarball with a configure script.
-Arun
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 8:45:45 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from wilma.widomaker.com (wilma.widomaker.com [204.17.220.5])
by hub.freebsd.org (Postfix) with ESMTP id 1B13A37B40B
for <freebsd-hackers@freebsd.org>; Mon, 25 Jun 2001 08:45:43 -0700 (PDT)
(envelope-from shannon@daydream.shannon.net)
Received: from [206.246.249.248] (helo=escape.shannon.net)
by wilma.widomaker.com with esmtp (Exim 3.22 #2)
id 15EYYU-0007jG-00
for freebsd-hackers@freebsd.org; Mon, 25 Jun 2001 11:45:40 -0400
Received: from daydream (daydream.shannon.net [192.168.1.10])
by escape.shannon.net (8.11.0/8.8.8) with ESMTP id f5PFGGc12718
for <freebsd-hackers@freebsd.org>; Mon, 25 Jun 2001 11:16:16 -0400 (EDT)
Received: from shannon by daydream with local (Exim 3.12 #1 (Debian))
id 15EY63-0007ky-00
for <freebsd-hackers@freebsd.org>; Mon, 25 Jun 2001 11:16:15 -0400
Date: Mon, 25 Jun 2001 11:16:15 -0400
From: Shannon Hendrix <shannon@widomaker.com>
To: freebsd-hackers@freebsd.org
Subject: Re: DVD IOCTLs on IDE?
Message-ID: <20010625111614.A29680@widomaker.com>
Mail-Followup-To: freebsd-hackers@freebsd.org
References: <15158.24886.958193.121109@trooper.velocet.net> <20010624180007.Z23601@numachi.com> <15158.33260.976403.782709@trooper.velocet.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <15158.33260.976403.782709@trooper.velocet.net>
User-Agent: Mutt/1.3.18i
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Sun, Jun 24, 2001 at 08:12:28PM -0400, David Gilbert wrote:
> ... and can successfully mount a DVD-ROM... they just don't play with
> any of the software I've been able to find. Most recently, I
> downloaded a copy of another package mentioned on /., but it dies
> looking for libdl.so ... which I assume is a stupid linux dependancy,
> so I havn't been chasing it.
It's a dynamic load library, originally from Solaris. It's included in
all dynamically linked NetBSD programs, exists as a library in Linux.
Run "man dlopen" and see if the man page says at the top if it's a
library or is included in all dynamically linked programs.
I cannot get to my FreeBSD box to check right now.
--
"Secrecy is the beginning of tyranny." -- Unknown
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 10: 0: 3 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8])
by hub.freebsd.org (Postfix) with ESMTP id 4526837B401
for <freebsd-hackers@FreeBSD.ORG>; Mon, 25 Jun 2001 09:59:54 -0700 (PDT)
(envelope-from rh@matriplex.com)
Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9])
by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id JAA72855;
Mon, 25 Jun 2001 09:59:26 -0700 (PDT)
(envelope-from rh@matriplex.com)
Date: Mon, 25 Jun 2001 09:59:26 -0700 (PDT)
From: Richard Hodges <rh@matriplex.com>
To: Christopher Sedore <cmsedore@mailbox.syr.edu>
Cc: Josh Osborne <stripes@mac.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: question: aio / nbio / kqueue
In-Reply-To: <Pine.SOL.4.10.10106250822410.3561-100000@rodan.syr.edu>
Message-ID: <Pine.BSF.4.10.10106250858280.72662-100000@mail.matriplex.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> On Fri, 22 Jun 2001, Richard Hodges wrote:
> > I tried AIO some months ago (4.1R or 4.2R), but had some trouble
> > with AIO, mainly that it seemed to lose track of half my files.
> > Not any particular files, it seemed that at any moment it would
> > just pick ten or so (out of maybe 20-25 files) to ignore at any
> > given time.
> >
On Mon, 25 Jun 2001, Christopher Sedore wrote:
> I've done this at the 3-6 MB/sec continous (peaks at 10MB+/sec) range with
> good success with aio, both the network and disk functions. Never had
> trouble with it losing track of files (not sure what you mean here). If
> you didn't tweak some of the default sysctl settings, you may have bumped
> limits that caused unexpected behaviour (though you should have gotten
> error returns to let you know).
Going back to my notes, my first use of AIO was:
For every file to read:
1. Clear aiocb and fill all fields,
x->aio_sigevent.sigev_notify = SIGEV_NONE;
x->aio_sigevent.sigev_signo = 0;
2. Do an aio_read(), if no error, put pointer to aiocb
into an array
3. Do aio_suspend with pointers to the successful
aiocb's from the aio_read()'s
The idea is to queue up the requests and wait for one of them
to succeed. Then check all of the files, for each pending:
4. Get status with aio_error()
5. If EINPROGRESS, check next file
6. If zero or error, get status with aio_return
7. If successful, log new data and check next file
8. If error, log error and check next file
What I found out that aio_suspend() will fail with a rather low
number of file operations (AIO_LISTIO_MAX==16), so aio_suspend()
is not an option.
So instead of doing aio_suspend(), I had a loop that posted
new reads as neccessary with aio_read(), and another loop
that checks each pending operation with aio_error(). This
allowed some of the reads to succeed, but for some reason
AIO seemed to forget about some of them, as if AIO has some
internal limit to the number of pending read operations. This
was with only 20 files, and reading from UFS on vinum (striped).
This was about half a year ago, but I am sure this is reasonably
close to what really happened...
-Richard
-------------------------------------------
Richard Hodges | Matriplex, inc.
Product Manager | 769 Basque Way
rh@matriplex.com | Carson City, NV 89706
775-886-6477 | www.matriplex.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 10:40:10 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29])
by hub.freebsd.org (Postfix) with ESMTP id ED94F37B401
for <freebsd-hackers@FreeBSD.ORG>; Mon, 25 Jun 2001 10:40:01 -0700 (PDT)
(envelope-from cmsedore@mailbox.syr.edu)
Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1b) with SMTP id <0.001E7F3E@mailer.syr.edu>; Mon, 25 Jun 2001 13:40:01 -0400
Received: from localhost (cmsedore@localhost)
by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id NAA12619;
Mon, 25 Jun 2001 13:40:00 -0400 (EDT)
X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs
Date: Mon, 25 Jun 2001 13:40:00 -0400 (EDT)
From: Christopher Sedore <cmsedore@mailbox.syr.edu>
X-Sender: cmsedore@rodan.syr.edu
To: Richard Hodges <rh@matriplex.com>
Cc: Josh Osborne <stripes@mac.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: question: aio / nbio / kqueue
In-Reply-To: <Pine.BSF.4.10.10106250858280.72662-100000@mail.matriplex.com>
Message-ID: <Pine.SOL.4.10.10106251331210.3561-100000@rodan.syr.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
You might try using aio_waitcomplete instead of aio_suspend. I wrote it
because I hated the aio_suspend/array methodology. You should also make
sure you bzero the aiocb structure before use as some of the fields could
cause strange behavior if left with random data.
-Chris
On Mon, 25 Jun 2001, Richard Hodges wrote:
> > On Fri, 22 Jun 2001, Richard Hodges wrote:
>
> > > I tried AIO some months ago (4.1R or 4.2R), but had some trouble
> > > with AIO, mainly that it seemed to lose track of half my files.
> > > Not any particular files, it seemed that at any moment it would
> > > just pick ten or so (out of maybe 20-25 files) to ignore at any
> > > given time.
> > >
>
> On Mon, 25 Jun 2001, Christopher Sedore wrote:
>
> > I've done this at the 3-6 MB/sec continous (peaks at 10MB+/sec) range with
> > good success with aio, both the network and disk functions. Never had
> > trouble with it losing track of files (not sure what you mean here). If
> > you didn't tweak some of the default sysctl settings, you may have bumped
> > limits that caused unexpected behaviour (though you should have gotten
> > error returns to let you know).
>
> Going back to my notes, my first use of AIO was:
>
> For every file to read:
> 1. Clear aiocb and fill all fields,
> x->aio_sigevent.sigev_notify = SIGEV_NONE;
> x->aio_sigevent.sigev_signo = 0;
> 2. Do an aio_read(), if no error, put pointer to aiocb
> into an array
> 3. Do aio_suspend with pointers to the successful
> aiocb's from the aio_read()'s
>
> The idea is to queue up the requests and wait for one of them
> to succeed. Then check all of the files, for each pending:
>
> 4. Get status with aio_error()
> 5. If EINPROGRESS, check next file
> 6. If zero or error, get status with aio_return
> 7. If successful, log new data and check next file
> 8. If error, log error and check next file
>
> What I found out that aio_suspend() will fail with a rather low
> number of file operations (AIO_LISTIO_MAX==16), so aio_suspend()
> is not an option.
>
> So instead of doing aio_suspend(), I had a loop that posted
> new reads as neccessary with aio_read(), and another loop
> that checks each pending operation with aio_error(). This
> allowed some of the reads to succeed, but for some reason
> AIO seemed to forget about some of them, as if AIO has some
> internal limit to the number of pending read operations. This
> was with only 20 files, and reading from UFS on vinum (striped).
>
> This was about half a year ago, but I am sure this is reasonably
> close to what really happened...
>
> -Richard
>
> -------------------------------------------
> Richard Hodges | Matriplex, inc.
> Product Manager | 769 Basque Way
> rh@matriplex.com | Carson City, NV 89706
> 775-886-6477 | www.matriplex.com
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 10:43:40 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88])
by hub.freebsd.org (Postfix) with ESMTP id 473FB37B40B
for <hackers@FreeBSD.org>; Mon, 25 Jun 2001 10:43:28 -0700 (PDT)
(envelope-from jhb@FreeBSD.org)
Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241])
by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f5PHgwI18455;
Mon, 25 Jun 2001 10:42:58 -0700 (PDT)
(envelope-from jhb@FreeBSD.org)
Message-ID: <XFMail.010625121649.jhb@FreeBSD.org>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20010624132329.A507@ringworld.oblivion.bg>
Date: Mon, 25 Jun 2001 12:16:49 -0700 (PDT)
From: John Baldwin <jhb@FreeBSD.org>
To: Peter Pentchev <roam@orbitel.bg>
Subject: Re: Two Junior Kernel Hacker tasks..
Cc: Terry Lambert <tlambert2@mindspring.com>
Cc: Terry Lambert <tlambert2@mindspring.com>,
Valentin Nechayev <netch@iv.nn.kiev.ua>, hackers@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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On 24-Jun-01 Peter Pentchev wrote:
> On Sat, Jun 23, 2001 at 10:44:51PM -0700, John Baldwin wrote:
>>
>> On 23-Jun-01 Peter Pentchev wrote:
>> > On Sat, Jun 23, 2001 at 12:23:35PM -0700, Terry Lambert wrote:
>> >> > make buildkernel is rather easy way to work it around: in
>> >> > any case object tree is machine-dependent, and one yet
>> >> > another directory does not destroy anything. ;|
>> >>
>> >> The "make buildkernel" approach sucks for incremental
>> >> builds, since you are unable to avoid the "config" run
>> >> each time, and a lot of unnecessary stuff gets compiled
>> >> again because of opt_*.h files whose contents have not
>> >> changed (even if you defeat the clean of the compile
>> >> directory).
>> >
>> > About the release process, you are right, it is a bit harder
>> > to restart without some tweaks, but the buildkernel target
>> > is about as restartable as it can be. (I really don't think
>> > anyone would ever advocate skipping the config(8) or
>> > the 'make depend' stage..)
>>
>> Actually, make depend takes a relatively long time, and when
>> I'm hacking on a kernel, I don't want to wait 15 minutes to
>> build a kernel after changing one file. I compile kernels
>> w/o config or make depend a lot.
>
> OK, so if you're really really sure your changes do not affect
> the dependency graph, use -DNOKERNELDEPEND :)
make ; make install is a _lot_ shorter to type than:
make -DNOKERNELDEPEND -DDOWHATIWANTDANGIT -DDONTDOTHIS
-DDONTDOTHATOTHERTHINGEITHER buildkernel ; make -DDONTINSTALLFOO
-DDONTTRYTODOTHIS installkernel
And I won't even mention 'make reinstall'...
--
John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 10:53:53 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8])
by hub.freebsd.org (Postfix) with ESMTP id ADD8437B401
for <freebsd-hackers@FreeBSD.ORG>; Mon, 25 Jun 2001 10:53:51 -0700 (PDT)
(envelope-from rh@matriplex.com)
Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9])
by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id KAA72980;
Mon, 25 Jun 2001 10:53:49 -0700 (PDT)
(envelope-from rh@matriplex.com)
Date: Mon, 25 Jun 2001 10:53:48 -0700 (PDT)
From: Richard Hodges <rh@matriplex.com>
To: Christopher Sedore <cmsedore@mailbox.syr.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: question: aio / nbio / kqueue
In-Reply-To: <Pine.SOL.4.10.10106251331210.3561-100000@rodan.syr.edu>
Message-ID: <Pine.BSF.4.10.10106251048380.72662-100000@mail.matriplex.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Mon, 25 Jun 2001, Christopher Sedore wrote:
> You might try using aio_waitcomplete instead of aio_suspend. I wrote it
> because I hated the aio_suspend/array methodology.
That does look like a nice alternative to aio_suspend... I'll have to
have another look at AIO then.
> You should also make sure you bzero the aiocb structure before use as
> some of the fields could cause strange behavior if left with random
> data.
Did that. But it never hurts to double-check :-)
Thanks,
-Richard
-------------------------------------------
Richard Hodges | Matriplex, inc.
Product Manager | 769 Basque Way
rh@matriplex.com | Carson City, NV 89706
775-886-6477 | www.matriplex.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 11: 9:47 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11])
by hub.freebsd.org (Postfix) with ESMTP id 5126937B407
for <freebsd-hackers@freebsd.org>; Mon, 25 Jun 2001 11:09:45 -0700 (PDT)
(envelope-from jason.anderson@windriver.com)
Received: from peale.wrs.com (peale [147.11.36.41])
by mail.wrs.com (8.9.3/8.9.1) with ESMTP id LAA24142;
Mon, 25 Jun 2001 11:09:13 -0700 (PDT)
Message-Id: <5.0.2.1.2.20010625105826.04497b60@mail.wrs.com>
X-Sender: jasona@mail.wrs.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Mon, 25 Jun 2001 11:09:43 -0700
To: freebsd-hackers@freebsd.org
From: "Jason S. Anderson" <jason.anderson@windriver.com>
Subject: Wind River Q&A at Usenix
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
FreeBSD developers/users,
At this week's Usenix conference, Wind River will have a representative
(namely me :) at the FreeBSD booth to help answer questions about Wind and
our relationship to the FreeBSD project. It's an informal setting where you
should feel free to ask about any concerns or ideas you might have; I'll do
my best to answer as directly as possible.
Please bear in mind that there are many questions that we simply don't
have answers for yet. For example, questions on specific technology areas
that Wind may or may not make a contribution are very premature, and as much
as I'd like to be able to say what we're doing with PowerPC, network drivers,
installation technology and others we just don't know at this point. I
believe there are many other questions that I can answer, though, and I look
forward to meeting people from the community and learning more about your
needs and ideas.
If there are other common questions you're interested in hearing Wind's
perspective on feel free to email me; we're preparing a printed FAQ to be
distributed at the booth to help spread the message a little bit more
efficiently.
Regards,
-Jason Anderson
Manager, Wind River FreeBSD Engineering
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 13:16: 3 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75])
by hub.freebsd.org (Postfix) with ESMTP
id 9B26837B406; Mon, 25 Jun 2001 13:15:55 -0700 (PDT)
(envelope-from brdavis@odin.ac.hmc.edu)
Received: (from brdavis@localhost)
by odin.ac.hmc.edu (8.11.0/8.11.0) id f5PKFkH24121;
Mon, 25 Jun 2001 13:15:46 -0700
Date: Mon, 25 Jun 2001 13:15:46 -0700
From: Brooks Davis <brooks@one-eyed-alien.net>
To: Hajimu UMEMOTO <ume@mahoroba.org>
Cc: hackers@FreeBSD.ORG, brian@Awfulhak.org, phk@critter.freebsd.dk,
arch@FreeBSD.ORG
Subject: Re: cloning network interfaces
Message-ID: <20010625131546.C30423@Odin.AC.HMC.Edu>
References: <20010611142030.A15283@Odin.AC.HMC.Edu> <20010613.040716.115941864.ume@mahoroba.org> <20010622125113.A30459@Odin.AC.HMC.Edu> <20010625.013106.78752396.ume@mahoroba.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="DIOMP1UsTsWJauNi"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010625.013106.78752396.ume@mahoroba.org>; from ume@mahoroba.org on Mon, Jun 25, 2001 at 01:31:06AM +0900
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
--DIOMP1UsTsWJauNi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Jun 25, 2001 at 01:31:06AM +0900, Hajimu UMEMOTO wrote:
> It seems fine to me.
> I just tried it on my box. You forget to include prototype change of
> in_gif_input() in sys/net/if_gif.h.
It's defined in sys/netinet/in_gif.h and I forgot to include it in my
diff. Sorry about that.
> BTW, why did you change gif_ioctl() to gif_ifioctl()? gif related
> modules are shared among *BSDs and maintained in KAME CVS repository.
> Could you please keep local changes small as possible?
I had renamed it when I introduced the /dev/gif device and an ioctl for
that. I just forgot to rename it. Sorry about that.
-- 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
--DIOMP1UsTsWJauNi
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7N5vxXY6L6fI4GtQRAgnCAKCaI8FDrAFA9CCRLxnD9ZvWtpTrvwCfTYVP
FJVFlR2wEwoUYvhX9oRt5I4=
=ziAJ
-----END PGP SIGNATURE-----
--DIOMP1UsTsWJauNi--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 15:25:45 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106])
by hub.freebsd.org (Postfix) with ESMTP id 0080B37B401
for <freebsd-hackers@freebsd.org>; Mon, 25 Jun 2001 15:25:42 -0700 (PDT)
(envelope-from ticso@mail.cicely.de)
Received: from mail.cicely.de (cicely20 [10.1.1.22])
by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f5PMPd627857
for <freebsd-hackers@freebsd.org>; Tue, 26 Jun 2001 00:25:40 +0200 (CEST)
Received: (from ticso@localhost)
by mail.cicely.de (8.11.0/8.11.0) id f5PMQTR01814
for freebsd-hackers@freebsd.org; Tue, 26 Jun 2001 00:26:29 +0200 (CEST)
Date: Tue, 26 Jun 2001 00:26:28 +0200
From: Bernd Walter <ticso@mail.cicely.de>
To: freebsd-hackers@freebsd.org
Subject: How to write to multiple tape drives
Message-ID: <20010626002628.A1679@cicely20.cicely.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
I want to use multiple tapes drives at the same time so I
need a way to send or read data without having to block.
aio_* is not a solution because it's not portable to NetBSD.
Is there another portable solution than vfork?
--
B.Walter COSMO-Project http://www.cosmo-project.de
ticso@cicely.de Usergroup info@cosmo-project.de
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 15:42:56 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from softweyr.com (mail.dobox.com [208.187.122.44])
by hub.freebsd.org (Postfix) with ESMTP id 44C1B37B405
for <hackers@freebsd.org>; Mon, 25 Jun 2001 15:42:50 -0700 (PDT)
(envelope-from wes@softweyr.com)
Received: from localhost.softweyr.com
([127.0.0.1] helo=softweyr.com ident=a2fe3d39ca007853ff6e60cd8a024d4a)
by softweyr.com with esmtp (Exim 3.16 #1)
id 15E2Ru-00006c-00; Sat, 23 Jun 2001 23:28:42 -0600
Message-ID: <3B357A8A.E7E704F3@softweyr.com>
Date: Sat, 23 Jun 2001 23:28:42 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Rahul Siddharthan <rsidd@physics.iisc.ernet.in>
Cc: "Koster, K.J." <K.J.Koster@kpn.com>,
'Jordan Hubbard' <jkh@osd.bsdi.com>, hackers@FreeBSD.ORG
Subject: Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
References: <59063B5B4D98D311BC0D0001FA7E452205FD9CD5@l04.research.kpn.com> <20010621120034.A63133@lpt.ens.fr>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Rahul Siddharthan wrote:
>
> http://www.microsoft.com/windows2000/interix/interixinc.asp
> Plenty of GNU stuff there, though it doesn't say so explicitly.
> Of course, they say it's all meant only for "legacy Unix" stuff.
Can you substantiate your claim there is "plenty of GNU stuff" in
Interix, or are you just talking out your ass as usual?
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
wes@softweyr.com http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 15:42:57 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from softweyr.com (mail.dobox.com [208.187.122.44])
by hub.freebsd.org (Postfix) with ESMTP id B292437B401
for <hackers@freebsd.org>; Mon, 25 Jun 2001 15:42:49 -0700 (PDT)
(envelope-from wes@softweyr.com)
Received: from localhost.softweyr.com
([127.0.0.1] helo=softweyr.com ident=70b0b9e7c6e62d8eb00a69cdb15010ac)
by softweyr.com with esmtp (Exim 3.16 #1)
id 15E2X5-00006h-00; Sat, 23 Jun 2001 23:34:03 -0600
Message-ID: <3B357BCB.7DF29E75@softweyr.com>
Date: Sat, 23 Jun 2001 23:34:03 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Valentine <mark@thuvia.demon.co.uk>
Cc: Adam <element@Dim.com>, hackers@freebsd.org
Subject: Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
References: <200106200613.f5K6D7k33514@dotar-sojat.thuvia.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Mark Valentine wrote:
>
> No. The core SpiderTCP protocol implementation is _not_ derived
> from BSD. Some of the utilities which were added as the product
> was developed came from Net/1 or Net/2 (hence the FTP.EXE copyright
> string), but others such as route and netstat were written from
> scratch, and the BSD utilities were modified to work over TLI and
> STREAMS (SpiderTCP is a STREAMS implementation, which is why
> NT had STREAMS at least until 4.0; they also used it for their OSI
> and X.500 implementation, even though that was not Spider's).
>
> The STREAMS TCP/IP implementation was later replaced (the way
> Microsoft wedged SpiderSTREAMS into NT was not pretty), but large
> chunks of the utilities remain.
THAT was the stack that was reportedly based on NetBSD 1.3.3. The NT 5.0
(nee Windows 2000) Beta5 TCP/IP stack would be reported by various network
scanners as the NetBSD 1.3.3 stack, which led to widespread rumors that
the code was a port from NetBSD. I suspect you would need to look at the
code itself to determine that is true, or get someone at Microsoft to tell
the truth. Yeah, like that's gonna happen.
> (NOTE: this was never sockets over TLI like the stuff some UNIX
> vendors bought from a Spider competitor!)
*Cough*Lachman*cough*.
> SpiderTCP sockets used an old BSD API, but was a rewrite to work
> over a kernel STREAMS socket interface to the kernel TCP/IP drivers.
Neat hack.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
wes@softweyr.com http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 15:43:10 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from softweyr.com (mail.dobox.com [208.187.122.44])
by hub.freebsd.org (Postfix) with ESMTP
id BCB7937B406; Mon, 25 Jun 2001 15:42:50 -0700 (PDT)
(envelope-from wes@softweyr.com)
Received: from localhost.softweyr.com
([127.0.0.1] helo=softweyr.com ident=3275992477fe9dce3f28d2ebf29917fa)
by softweyr.com with esmtp (Exim 3.16 #1)
id 15E2fm-0000Bh-00; Sat, 23 Jun 2001 23:43:02 -0600
Message-ID: <3B357DE6.942BE412@softweyr.com>
Date: Sat, 23 Jun 2001 23:43:02 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: joel.sherrill@OARcorp.com
Cc: James Housley <jim@thehousleys.net>, hackers@freebsd.org,
questions@freebsd.org
Subject: Re: real time
References: <E14vlpX-0008Nr-00@bsdconspiracy.net> <3AF30CF8.FC28EDA1@thehousleys.net> <3AF5D1BF.93588882@softweyr.com> <3B31F2AD.E2850728@OARcorp.com>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Joel Sherrill wrote:
>
> Wes Peters wrote:
> >
> > James Housley wrote:
> > >
> > > Wes Peters wrote:
> > > >
> > > > Charles:
> > > > >
> > > > > -----Original Message-----
> > > > > > Joao Carlos <jcarlos@esbrasil.com> asked:
> > > > > >
> > > > > > Does FreeBSD has any related work about it as an real time operating
> > > > > > system?
> > > > > > Where can i find information about that ??
> > > > >
> > > > > Here's one starting point,
> > > > >
> > > > > http://www.rtmx.com/
> > > > >
> > > > > They offer extensions to OpenBSD.
> > > >
> > > > Used to. RTMX contributed the RTMX code base to OpenBSD and stopped
> > > > distributing it themselves over a year ago. Since then, it has
> > > > disappeared, with no mention of it on the OpenBSD web site. Neither
> > > > OpenBSD.org, rtmx.com, nor rtmx.net has a "search" feature, so
> > > > looking for it is nearly impossible. There is nothing in the OpenBSD
> > > > change logs mentioning RTMX, either.
> > > >
> > >
> > > RTEMS, http://www.oarcorp.com, does compile and run on FreeBSD. I have
> > > been contacted/contacting one of their main people about closer ties.
> > > The tools are in the ports tree.
> >
> > Tell Joel I said Hi. I like everything about RTEMS except the GPL that
> > has infested it. I wish we could convince OARcorp to shed this and come
> > up with a license that allows binary distribution. The licensing issue
> > is the primary advantage eCOS has over RTEMS at this time, doubly ironic
> > now that RootHack owns eCOS.
>
> I am sorry for missing this. I was out of town at the time
> and just now cleaning my inbox down to that point.
>
> RTEMS is not pure-GPL -- it does allow binary redistribution. It also
> has an exception that allows linking RTEMS with an application without
> causing the application to be covered by the GPL.
Which are the only two complaints I have about the GPL vis-a-vis embedded
code. Thanks for clearing this up, Joel. You will be (once again) featured
prominently in an upcoming Daemon's Advocate. In fact, you may have come
up with an almost perfect license, and certainly an interesting point of
conversation.
And, I've decided this weekend, RTEMS will be featured in at least some
part of my OpenSail project. I'm leaning towards Linux or BSD on the
"main" processor, mostly to make it easy for relatively untrained programmers
to add applications to the system, but we will be making some interesting
LCD displays, which will need a good, fast, tight embedded OS. Is there an
existing port of RTEMS to the DragonBall? In particulary, we've been eye-
balling the Lineo uCsimm development board.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
wes@softweyr.com http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 15:43:57 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from aries.ai.net (aries.ai.net [205.134.163.4])
by hub.freebsd.org (Postfix) with ESMTP
id C742837B40B; Mon, 25 Jun 2001 15:43:48 -0700 (PDT)
(envelope-from deepak@ai.net)
Received: from blood (adsl-138-88-48-248.bellatlantic.net [138.88.48.248])
by aries.ai.net (8.9.3/8.9.3) with SMTP id SAA18109;
Mon, 25 Jun 2001 18:44:49 -0400 (EDT)
(envelope-from deepak@ai.net)
Reply-To: <deepak@ai.net>
From: "Deepak Jain" <deepak@ai.net>
To: <freebsd-net@freebsd.org>,
"freebsd-hackers@FreeBSD. ORG" <freebsd-hackers@freebsd.org>
Subject: fastforwarding?
Date: Mon, 25 Jun 2001 18:47:41 -0400
Message-ID: <GPEOJKGHAMKFIOMAGMDICEOJDGAA.deepak@ai.net>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
sysctl -A |grep forward
net.inet.ip.forwarding: 1
net.inet.ip.fastforwarding: 0
machdep.forward_irq_enabled: 1
machdep.forward_signal_enabled: 1
machdep.forward_roundrobin_enabled: 1
What does the fastforwarding option do that the normal forwarding option
doesn't?
Thanks,
Deepak Jain
AiNET
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 15:49:20 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
by hub.freebsd.org (Postfix) with ESMTP id CB10A37B405
for <hackers@FreeBSD.ORG>; Mon, 25 Jun 2001 15:49:17 -0700 (PDT)
(envelope-from phk@critter.freebsd.dk)
Received: from critter (localhost [127.0.0.1])
by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f5PMl4n61647;
Tue, 26 Jun 2001 00:47:08 +0200 (CEST)
(envelope-from phk@critter.freebsd.dk)
To: Wes Peters <wes@softweyr.com>
Cc: Mark Valentine <mark@thuvia.demon.co.uk>, Adam <element@Dim.com>,
hackers@FreeBSD.ORG
Subject: Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
In-Reply-To: Your message of "Sat, 23 Jun 2001 23:34:03 MDT."
<3B357BCB.7DF29E75@softweyr.com>
Date: Tue, 26 Jun 2001 00:47:04 +0200
Message-ID: <61645.993509224@critter>
From: Poul-Henning Kamp <phk@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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In message <3B357BCB.7DF29E75@softweyr.com>, Wes Peters writes:
>Mark Valentine wrote:
>>
>> No. The core SpiderTCP protocol implementation is _not_ derived
>> from BSD. [...]
>
>> (NOTE: this was never sockets over TLI like the stuff some UNIX
>> vendors bought from a Spider competitor!)
>
>*Cough*Lachman*cough*.
*Cough*Wollongong*cough*hack*wheeze* (THUD!)
--
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 Mon Jun 25 15:52:42 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail1.javanet.com (mail1.javanet.com [205.219.162.10])
by hub.freebsd.org (Postfix) with ESMTP id 1A7FE37B405
for <freebsd-hackers@freebsd.org>; Mon, 25 Jun 2001 15:52:40 -0700 (PDT)
(envelope-from kaworu@sektor7.ath.cx)
Received: from wintermute.sekt7 (209-6-248-16.c3-0.lex-ubr1.sbo-lex.ma.cable.rcn.com [209.6.248.16])
by mail1.javanet.com (8.9.3/8.9.2) with ESMTP id SAA14673
for <freebsd-hackers@freebsd.org>; Mon, 25 Jun 2001 18:53:23 -0400 (EDT)
Date: Mon, 25 Jun 2001 18:53:23 -0400 (EDT)
Message-Id: <200106252253.SAA14673@mail1.javanet.com>
From: Evan Sarmiento <kaworu@sektor7.ath.cx>
To: freebsd-hackers@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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Subject: jailuser project
--text follows this line--
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I would like your input on a project I am currently working on called Jailuser. Jail, which is similar, chroots an enviornment and sets restrictions on processes forked within. However, problems arise: Inability to login to jail from console, hard to manage externally, have to reproduce base system for each jail (or an nfs mount, but insecure)
Therefore, I have created jailuser. Users with UID of 1000 have the same jail restrictions, eg. unable to use certain socket functions, sysv ipc, etc. Also, users are confined by a "kernel restricted shell", which I have yet to implement.
I have committed a few things, http://savannah.gnu.org/projects/jailuser/, please take a look.
Thanks,
Evan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (SunOS)
Comment: Processed by Mailcrypt 3.5.6 and Gnu Privacy Guard <http://www.gnupg.org/>
iEYEARECAAYFAjs3waAACgkQBLUKTEZ4y0bhNQCfYjgfmzM8R9GHdoIY0veoQUFF
7kkAn2Opz8H+RMIF1HIx73Sqw4stTR+J
=L2xv
-----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 Mon Jun 25 16:24:15 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66])
by hub.freebsd.org (Postfix) with ESMTP id 76D7337B407
for <hackers@FreeBSD.ORG>; Mon, 25 Jun 2001 16:24:07 -0700 (PDT)
(envelope-from nate@yogotech.com)
Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131])
by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id RAA15313;
Mon, 25 Jun 2001 17:23:32 -0600 (MDT)
(envelope-from nate@nomad.yogotech.com)
Received: (from nate@localhost)
by nomad.yogotech.com (8.8.8/8.8.8) id RAA17576;
Mon, 25 Jun 2001 17:23:31 -0600 (MDT)
(envelope-from nate)
From: Nate Williams <nate@yogotech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15159.51187.497633.491256@nomad.yogotech.com>
Date: Mon, 25 Jun 2001 17:23:31 -0600 (MDT)
To: Wes Peters <wes@softweyr.com>
Cc: Rahul Siddharthan <rsidd@physics.iisc.ernet.in>,
"Koster, K.J." <K.J.Koster@kpn.com>,
"'Jordan Hubbard'" <jkh@osd.bsdi.com>, hackers@FreeBSD.ORG
Subject: Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
In-Reply-To: <3B357A8A.E7E704F3@softweyr.com>
References: <59063B5B4D98D311BC0D0001FA7E452205FD9CD5@l04.research.kpn.com>
<20010621120034.A63133@lpt.ens.fr>
<3B357A8A.E7E704F3@softweyr.com>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Reply-To: nate@yogotech.com (Nate Williams)
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> > http://www.microsoft.com/windows2000/interix/interixinc.asp
> > Plenty of GNU stuff there, though it doesn't say so explicitly.
> > Of course, they say it's all meant only for "legacy Unix" stuff.
>
> Can you substantiate your claim there is "plenty of GNU stuff" in
> Interix, or are you just talking out your ass as usual?
That's uncalled for Wes. Interix contains *lots* of GNU code, but to be
fair to M$, the company that developed Interix was acquired by M$ long
before Linux was as big of a threat to it's business as it is now.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 17:38:59 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from hotmail.com (f33.law11.hotmail.com [64.4.17.33])
by hub.freebsd.org (Postfix) with ESMTP id 13AAB37B401
for <hackers@freebsd.org>; Mon, 25 Jun 2001 17:38:58 -0700 (PDT)
(envelope-from part_lion@hotmail.com)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
Mon, 25 Jun 2001 17:38:57 -0700
Received: from 64.242.6.171 by lw11fd.law11.hotmail.msn.com with HTTP; Tue, 26 Jun 2001 00:38:57 GMT
X-Originating-IP: [64.242.6.171]
From: "Joesh Juphland" <part_lion@hotmail.com>
To: hackers@freebsd.org
Subject: retrieving flash data from pcmcia cards in freeBSD ... possible ?
Date: Mon, 25 Jun 2001 18:38:57 -0600
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F33Oiy54DgI6bXmdMJO00014711@hotmail.com>
X-OriginalArrivalTime: 26 Jun 2001 00:38:57.0764 (UTC) FILETIME=[62BC3A40:01C0FDD8]
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Many pcmcia cards that I use have user-updateable firmware - basically a
flash region of some kind that you can update with newer firmwares.
When I want to update these items, I generally stick them in a windows
machine and get the new firmware from the manufacturer and use whatever
program they have to blow it in. Easy.
I have two questions:
1. is there any standard among pcmcia cards as to where that firmware exists
on the card ? That is, are all of those firmware-blow-in programs doing
about the same thing ?
2. is there any way, in FreeBSD, that I can at least _look at_ that firmware
and grab the data out of it - ideally I would also like to update it in
freeBSD as well ... are either of these possible ? I am hoping that I can
at least view/retrieve the firmware.
thanks.
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 17:47: 2 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mass.dis.org (dhcp44-21.dis.org [216.240.44.21])
by hub.freebsd.org (Postfix) with ESMTP id 83F7737B405
for <hackers@freebsd.org>; Mon, 25 Jun 2001 17:46:57 -0700 (PDT)
(envelope-from msmith@mass.dis.org)
Received: from mass.dis.org (localhost [127.0.0.1])
by mass.dis.org (8.11.4/8.11.3) with ESMTP id f5Q0wsH01827;
Mon, 25 Jun 2001 17:58:55 -0700 (PDT)
(envelope-from msmith@mass.dis.org)
Message-Id: <200106260058.f5Q0wsH01827@mass.dis.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "Joesh Juphland" <part_lion@hotmail.com>
Cc: hackers@freebsd.org
Subject: Re: retrieving flash data from pcmcia cards in freeBSD ... possible ?
In-reply-to: Your message of "Mon, 25 Jun 2001 18:38:57 MDT."
<F33Oiy54DgI6bXmdMJO00014711@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 25 Jun 2001 17:58:54 -0700
From: Mike Smith <msmith@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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
>
> Many pcmcia cards that I use have user-updateable firmware - basically a
> flash region of some kind that you can update with newer firmwares.
>
> When I want to update these items, I generally stick them in a windows
> machine and get the new firmware from the manufacturer and use whatever
> program they have to blow it in. Easy.
>
> I have two questions:
>
> 1. is there any standard among pcmcia cards as to where that firmware exists
> on the card ? That is, are all of those firmware-blow-in programs doing
> about the same thing ?
No.
> 2. is there any way, in FreeBSD, that I can at least _look at_ that firmware
> and grab the data out of it - ideally I would also like to update it in
> freeBSD as well ... are either of these possible ? I am hoping that I can
> at least view/retrieve the firmware.
Nope. Give up now. 8(
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 19:27:30 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ggong.harvestberkeley.org (ggong.baycis.com [209.133.107.121])
by hub.freebsd.org (Postfix) with ESMTP id 8443A37B405
for <hackers@freebsd.org>; Mon, 25 Jun 2001 19:27:28 -0700 (PDT)
(envelope-from ggong@cal.alumni.berkeley.edu)
Received: from ggongw2k (adsl-64-166-95-42.dsl.sntc01.pacbell.net [64.166.95.42])
by ggong.harvestberkeley.org (8.11.2/8.11.2) with SMTP id f5Q2RHW76791
for <hackers@freebsd.org>; Mon, 25 Jun 2001 19:27:17 -0700 (PDT)
(envelope-from ggong@cal.alumni.berkeley.edu)
Message-ID: <006601c0fde7$8522ffb0$2a5fa640@ggongw2k>
From: "Gilbert Gong" <ggong@cal.alumni.berkeley.edu>
To: <hackers@freebsd.org>
Subject: strange tcp behavior?
Date: Mon, 25 Jun 2001 19:27:06 -0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In the course of running some http load generators against apache on FreeBSD
4.3R, I have been seeing some strange behavior. I was finally able to find
a specific concrete weirdness (atleast I think it's a weirdness).
From test-client2, I am running http_load (installed from
/usr/ports/www/http_load):
http_load -p 20 -seconds 1800 /home/ggong/tmp/urls
The single url it is testing against is a very short page on the server.
This is what I see:
c206 - ggong@test-client2:~>netstat -na | grep 4670
tcp4 0 0 192.168.0.22.4670 192.168.0.10.80 SYN_SENT
c207 - ggong@test-client2:~>ssh root@ts "netstat -na | grep 4670"
tcp4 0 0 192.168.0.10.80 192.168.0.22.4670 TIME_WAIT
c208 - ggong@test-client2:~>netstat -na | grep 4670
tcp4 0 0 192.168.0.22.4670 192.168.0.10.80 SYN_SENT
c209 - ggong@test-client2:~>
If I am not mistaken, this should not happen..
I'm also relatively certain the TIME_WAIT is not from a previously closed
connection..
Any ideas what might cause this, or hints on how I can further investigate
this?
Gilbert
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 19:41:55 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39])
by hub.freebsd.org (Postfix) with ESMTP id 751B537B409
for <hackers@freebsd.org>; Mon, 25 Jun 2001 19:41:52 -0700 (PDT)
(envelope-from silby@silby.com)
Received: (qmail 49341 invoked by uid 1000); 26 Jun 2001 02:41:51 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
by localhost with SMTP; 26 Jun 2001 02:41:51 -0000
Date: Mon, 25 Jun 2001 21:41:50 -0500 (CDT)
From: Mike Silbersack <silby@silby.com>
To: Gilbert Gong <ggong@cal.alumni.berkeley.edu>
Cc: <hackers@freebsd.org>
Subject: Re: strange tcp behavior?
In-Reply-To: <006601c0fde7$8522ffb0$2a5fa640@ggongw2k>
Message-ID: <20010625213923.V43878-100000@achilles.silby.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Mon, 25 Jun 2001, Gilbert Gong wrote:
> If I am not mistaken, this should not happen..
> I'm also relatively certain the TIME_WAIT is not from a previously closed
> connection..
>
> Any ideas what might cause this, or hints on how I can further investigate
> this?
> Gilbert
That's a known bug with our current tcp sequence number generation scheme.
It may be some time before a new scheme is put in place, so you'll have to
live with it for a while.
Mike "Silby" Silbersack
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 21: 6: 5 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from jamesnt.iadfw.net (jamesnt.iadfw.net [206.66.13.48])
by hub.freebsd.org (Postfix) with ESMTP id BD15A37B405
for <freebsd-hackers@freebsd.org>; Mon, 25 Jun 2001 21:06:01 -0700 (PDT)
(envelope-from jamesn@jamesnt.iadfw.net)
Received: (from jamesn@localhost)
by jamesnt.iadfw.net (8.11.3/8.11.3) id f5Q46Oi88460;
Mon, 25 Jun 2001 23:06:24 -0500 (CDT)
(envelope-from jamesn)
Date: Mon, 25 Jun 2001 23:06:24 -0500 (CDT)
Message-Id: <200106260406.f5Q46Oi88460@jamesnt.iadfw.net>
From: James Nuckolls <jamesn@what.net>
To: Jordan Hubbard <jkh@osd.bsdi.com>
Subject: Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
In-Reply-To: <20010615144235I.jkh@osd.bsdi.com>
References: <Pine.BSO.4.33.0106151659470.8779-100000@Aphex.NewGold.NET> <Pine.BSO.4.33.0106151702350.8779-100000@Aphex.NewGold.NET> <20010615144235I.jkh@osd.bsdi.com>
Cc: freebsd-hackers@freebsd.org
Reply-To: jamesn@airmail.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In mailinglist.freebsd.hackers, you wrote:
> This is a good reference, but sadly it only really refers to "the
> sockets paradigm as first popularized by BSD", which means they could
> have followed the API without touching a single line of BSD code.
>
> To reiterate: What I'm looking for is some true, hard evidence that
> Microsoft has used BSD code in any of their operating systems. A
I assume you've carefully examined the NT 3.51 (and 4.0) license
agreement? If they did use anything that's from a BSD socket layer
there should be a clause 3 statement there[1][2].
I think I've got a NT 3.5 server kit at the office somewhere...
[1] I mention this because I sware I've seen an actual NT 3.51
manual, the front cover if which DID contain the Bezerkly license
agreement. Unfortunatly I've lost it.
[2] And knowing Microsoft's lawyers, it really is there even if
they were trying to cover the fact up.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 22:40: 6 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40])
by hub.freebsd.org (Postfix) with ESMTP id 84A7237B406
for <freebsd-hackers@freebsd.org>; Mon, 25 Jun 2001 22:39:58 -0700 (PDT)
(envelope-from lansil@rpi.edu)
Received: from vcmr-19.rcs.rpi.edu (vcmr-19.rcs.rpi.edu [128.113.113.12])
by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f5Q5dwC103286
for <freebsd-hackers@freebsd.org>; Tue, 26 Jun 2001 01:39:58 -0400
Received: from localhost (lansil@localhost)
by vcmr-19.rcs.rpi.edu (8.8.5/8.8.6) with SMTP id BAA80258
for <freebsd-hackers@freebsd.org>; Tue, 26 Jun 2001 01:39:42 -0400
X-Authentication-Warning: vcmr-19.rcs.rpi.edu: lansil owned process doing -bs
Date: Tue, 26 Jun 2001 01:39:42 -0400 (EDT)
From: "Lawrence S. Lansing" <lansil@rpi.edu>
X-Sender: lansil@vcmr-19.rcs.rpi.edu
Reply-To: "Lawrence S. Lansing" <lansil@rpi.edu>
To: freebsd-hackers@freebsd.org
Subject: custom bootable CD & /usr/src/sys/i386/boot/cdboot
Message-ID: <Pine.A41.3.96.1010626002910.64824A-100000@vcmr-19.rcs.rpi.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hello. I am trying to create a custom bootable FreeBSD CD with a "live"
filesystem. I have read all the mailing-list messages I could find
pertaining to this process, and I am still short of information. I will
sum up the situation, and hope someone can fill in the details I'm
missing.
Here's what I have so far:
There are several ways of making a bootable FreeBSD CD. All of these
methods seem to involve "El Torito", and a boot floppy image of some kind.
The contents of the boot floppy can image vary somewhat, but there appear
to be two primary approaches:
1 -- The boot image contains a gzipped kernel, MFS, loader, and other
relevant /boot stuff. The Kernel and MFS in the boot image are used to
mount the CD filesystem, and possibly chroot to the CD filesystem. The
FreeBSD install CD uses this method.
2 -- The boot image is created by running 'make' in
/usr/src/sys/i386/boot/cdboot. This image contains a smarter 'loader',
which is able to read an ISO9660 filesystem for the kernel and root
filesystem. I believe this boot image contains boot0/1 and /boot/cdboot.
/boot/cdboot appears to be created from /usr/src/sys/boot/i386/cdldr, a
'loader' wrapper which replaces boot2, and allows 'loader' to understand
ISO9660.
I am interested in using method 2, since it would eliminated several
complications. I would not need to worry about mounting/chrooting the CD
filesystem, nor would I have to worry about fitting a kernel, loader, and
/boot stuff onto a 2.88 meg image. If I understand this method correctly,
the 'cdboot' loader would find the kernel and root filesystem on my CD,
and everything would "just work".
Well, theory is great, but I've run into a problem. I used
/usr/src/sys/i386/boot/cdboot/ to create a boot image. I used mkisofs
with the '-b' option to put this image into the boot portion of my ISO
filesystem. I burned a CD, and attempted to boot from it. I was greeted
with this message, generated by 'cdboot':
---
Your BIOS int 0x13 extensions seem to be disabled.
It's impossible to boot a CD-ROM without them.
(BIOS int 0x13 fn 0x4b01 yielded error 75
---
The same message appears when the CD is booted in three different
machines, all with fairly recent hardware and BIOSes. I have the distinct
suspicion that the error message is bogus. I'm working with a recent
-STABLE source tree (within the last week), but it doesn't appear that any
of the boot-related files have been changed in almost a year.
My only lead, so far, is that I might need to specify the '-no-emul-boot'
option to mkisofs. I'll try this out tomorrow, when I have time to make
another burn.
If anyone can flesh out the boot procedure a bit more for me, I would
appreciate it. Specifically, I would like to know what
/usr/src/sys/i386/boot/cdboot/ does, and whether I am trying to use it
correctly. I found very little documentation on this directory, even when
I resorted to checking CVS commit messages.
Thanks for any help you can offer. I apologize for being so long-winded.
-Larry Lansing
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Mon Jun 25 23:36:19 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65])
by hub.freebsd.org (Postfix) with ESMTP
id 24D0637B405; Mon, 25 Jun 2001 23:36:04 -0700 (PDT)
(envelope-from ru@whale.sunbay.crimea.ua)
Received: (from ru@localhost)
by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f5Q6Zjf52352;
Tue, 26 Jun 2001 09:35:45 +0300 (EEST)
(envelope-from ru)
Date: Tue, 26 Jun 2001 09:35:45 +0300
From: Ruslan Ermilov <ru@FreeBSD.org>
To: Deepak Jain <deepak@ai.net>
Cc: net@FreeBSD.org, hackers@FreeBSD.org
Subject: Re: fastforwarding?
Message-ID: <20010626093545.D49992@sunbay.com>
Mail-Followup-To: Deepak Jain <deepak@ai.net>, net@FreeBSD.org,
hackers@FreeBSD.org
References: <GPEOJKGHAMKFIOMAGMDICEOJDGAA.deepak@ai.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <GPEOJKGHAMKFIOMAGMDICEOJDGAA.deepak@ai.net>; from deepak@ai.net on Mon, Jun 25, 2001 at 06:47:41PM -0400
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Mon, Jun 25, 2001 at 06:47:41PM -0400, Deepak Jain wrote:
> sysctl -A |grep forward
> net.inet.ip.forwarding: 1
> net.inet.ip.fastforwarding: 0
> machdep.forward_irq_enabled: 1
> machdep.forward_signal_enabled: 1
> machdep.forward_roundrobin_enabled: 1
>
> What does the fastforwarding option do that the normal forwarding option
> doesn't?
>
See inet(4).
Cheers,
--
Ruslan Ermilov Oracle Developer/DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 0:41:38 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74])
by hub.freebsd.org (Postfix) with ESMTP
id DD55737B405; Tue, 26 Jun 2001 00:41:35 -0700 (PDT)
(envelope-from tlambert2@mindspring.com)
Received: from mindspring.com (dialup-209.245.130.195.Dial1.SanJose1.Level3.net [209.245.130.195])
by falcon.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA25886;
Tue, 26 Jun 2001 00:41:33 -0700 (PDT)
Message-ID: <3B383CCF.4A149A79@mindspring.com>
Date: Tue, 26 Jun 2001 00:42:07 -0700
From: Terry Lambert <tlambert2@mindspring.com>
Reply-To: tlambert2@mindspring.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: John Baldwin <jhb@FreeBSD.org>
Cc: Peter Pentchev <roam@orbitel.bg>, hackers@FreeBSD.org,
Valentin Nechayev <netch@iv.nn.kiev.ua>
Subject: Re: Two Junior Kernel Hacker tasks..
References: <XFMail.010623224451.jhb@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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
John Baldwin wrote:
>
> Actually, make depend takes a relatively long time, and when
> I'm hacking on a kernel, I don't want to wait 15 minutes to
> build a kernel after changing one file. I compile kernels
> w/o config or make depend a lot.
Me too. I can make a small set of changes to a couple
of kernel files, rebuild, reinstall, and reboot, and
be running the new kernel in under 3 minutes. Adding
a "make depend" puts that a bit further out (annoyingly
so).
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 1:11: 9 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123])
by hub.freebsd.org (Postfix) with ESMTP id 905A337B401
for <hackers@FreeBSD.ORG>; Tue, 26 Jun 2001 01:11:06 -0700 (PDT)
(envelope-from tlambert2@mindspring.com)
Received: from mindspring.com (dialup-209.245.130.195.Dial1.SanJose1.Level3.net [209.245.130.195])
by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA06727;
Tue, 26 Jun 2001 01:10:53 -0700 (PDT)
Message-ID: <3B3843AE.395E88F1@mindspring.com>
Date: Tue, 26 Jun 2001 01:11:26 -0700
From: Terry Lambert <tlambert2@mindspring.com>
Reply-To: tlambert2@mindspring.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Duncan Barclay <dmlb@dmlb.org>
Cc: list tracker <list_tracker@hotmail.com>, ambrisko@ambrisko.com,
hackers@FreeBSD.ORG
Subject: Re: trouble with 802.11 and kernel bridging (more)
References: <F156NH2cv0aGltFBNlJ00001ece@hotmail.com> <00a901c0fd6a$c44375d0$b36020c2@pc598cam>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Duncan Barclay wrote:
> I use IBSS and routing at home (with DHCP on a short timeout)
> to create seperate wired and wireless IP subnets. The FreeBSD
> box routes between the two and the external Cable Modem seamlessly.
>
> What disadvantages does this setup have compared with using a
> true access point? True APs can double the range for two
> wireless stations (the hidden node problem) - if both stations
> can see the AP but not each other they can still do peer to
> peer networking. True APs allow roaming between APs in an
> extended service set. True APs can do power saving to stations.
>
> I contend that the above are not necessary for a typical home
> user. An IBSS network with IP routing will serve many home users.
FWIW: There are two mobileIP implementations for FreeBSD
4.x, which also handle hand-off, and can support "static"
IP addresses (via tunneling and short ARP timeouts for the
station handoff).
Being able to have the same setup for your laptop, no
matter where you are using it is nice.
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 1:23:36 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from sneakerz.org (sneakerz.org [216.33.66.254])
by hub.freebsd.org (Postfix) with ESMTP
id 0A19837B405; Tue, 26 Jun 2001 01:23:34 -0700 (PDT)
(envelope-from bright@sneakerz.org)
Received: by sneakerz.org (Postfix, from userid 1092)
id AC4985D010; Tue, 26 Jun 2001 03:23:12 -0500 (CDT)
Date: Tue, 26 Jun 2001 03:23:11 -0500
From: Alfred Perlstein <bright@sneakerz.org>
To: Terry Lambert <tlambert2@mindspring.com>
Cc: John Baldwin <jhb@FreeBSD.org>, Peter Pentchev <roam@orbitel.bg>,
hackers@FreeBSD.org, Valentin Nechayev <netch@iv.nn.kiev.ua>
Subject: Re: Two Junior Kernel Hacker tasks..
Message-ID: <20010626032311.I64836@sneakerz.org>
References: <XFMail.010623224451.jhb@FreeBSD.org> <3B383CCF.4A149A79@mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <3B383CCF.4A149A79@mindspring.com>; from tlambert2@mindspring.com on Tue, Jun 26, 2001 at 12:42:07AM -0700
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
* Terry Lambert <tlambert2@mindspring.com> [010626 02:41] wrote:
> John Baldwin wrote:
> >
> > Actually, make depend takes a relatively long time, and when
> > I'm hacking on a kernel, I don't want to wait 15 minutes to
> > build a kernel after changing one file. I compile kernels
> > w/o config or make depend a lot.
>
> Me too. I can make a small set of changes to a couple
> of kernel files, rebuild, reinstall, and reboot, and
> be running the new kernel in under 3 minutes. Adding
> a "make depend" puts that a bit further out (annoyingly
> so).
You guys are right, you just have to be watchful if new headers
are added to files that you don't forget to 'make depend' otherwise
it gets nasty real fast like if those headers change. :)
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 1:30:51 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123])
by hub.freebsd.org (Postfix) with ESMTP id F422F37B406
for <hackers@FreeBSD.ORG>; Tue, 26 Jun 2001 01:30:48 -0700 (PDT)
(envelope-from tlambert2@mindspring.com)
Received: from mindspring.com (dialup-209.245.130.195.Dial1.SanJose1.Level3.net [209.245.130.195])
by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA06286;
Tue, 26 Jun 2001 01:30:44 -0700 (PDT)
Message-ID: <3B384855.341FB05E@mindspring.com>
Date: Tue, 26 Jun 2001 01:31:17 -0700
From: Terry Lambert <tlambert2@mindspring.com>
Reply-To: tlambert2@mindspring.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mike Silbersack <silby@silby.com>
Cc: Gilbert Gong <ggong@cal.alumni.berkeley.edu>, hackers@FreeBSD.ORG
Subject: Re: strange tcp behavior?
References: <20010625213923.V43878-100000@achilles.silby.com>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Mike Silbersack wrote:
> On Mon, 25 Jun 2001, Gilbert Gong wrote:
> > If I am not mistaken, this should not happen..
> > I'm also relatively certain the TIME_WAIT is not from a
> > previously closed connection..
> >
> > Any ideas what might cause this, or hints on how I can
> > further investigate this?
>
> That's a known bug with our current tcp sequence number
> generation scheme. It may be some time before a new scheme
> is put in place, so you'll have to live with it for a while.
The problem is that the number doesn't increment monotonically.
You don't get an RST if the sequence number is less. The
idea that broke this was an attempt to make things "safer"
by making the sequence number non-predictable, to prevent
session hijack.
If the sequence number is higher, then the previous connection
is reset, and the new connection is established in its place.
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 1:48:40 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from softweyr.com (softweyr.com [208.247.99.111])
by hub.freebsd.org (Postfix) with ESMTP id 65DC237B401
for <hackers@freebsd.org>; Tue, 26 Jun 2001 01:48:37 -0700 (PDT)
(envelope-from wes@softweyr.com)
Received: from localhost.softweyr.com
([127.0.0.1] helo=softweyr.com ident=06b59a84160626d72dcf0eb079c8e2a4)
by softweyr.com with esmtp (Exim 3.16 #1)
id 15Eoa1-0000DP-00; Tue, 26 Jun 2001 02:52:17 -0600
Message-ID: <3B384D41.4C24BC09@softweyr.com>
Date: Tue, 26 Jun 2001 02:52:17 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Rik van Riel <riel@conectiva.com.br>
Cc: Rahul Siddharthan <rsidd@physics.iisc.ernet.in>,
hackers@FreeBSD.ORG
Subject: Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
References: <Pine.LNX.4.21.0106241348310.7419-100000@imladris.rielhome.conectiva>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Rik van Riel wrote:
>
> On Sun, 24 Jun 2001, Rahul Siddharthan wrote:
> > Wes Peters said on Jun 23, 2001 at 23:28:42:
> > > > Plenty of GNU stuff there, though it doesn't say so explicitly.
> > > > Of course, they say it's all meant only for "legacy Unix" stuff.
> > >
> > > Can you substantiate your claim there is "plenty of GNU stuff" in
> > > Interix, or are you just talking out your ass as usual?
>
> gcc, gdb, bash, gnu emacs and a bunch more.
Out of several hundred utilities? Gimme a break. Yeah, it's probably
half the binary distribution, but that just goes to show the difference
in bloat between the GPL and BSD derived bits.
They even have a "download the source" page right on the Interix product
page. You Linux weenies would cry over being hung with a brand new, GPL'd
rope.
</taunt weenies=Linux>
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
wes@softweyr.com http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 2: 4:40 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120])
by hub.freebsd.org (Postfix) with ESMTP id 1166337B406
for <freebsd-hackers@FreeBSD.ORG>; Tue, 26 Jun 2001 02:04:35 -0700 (PDT)
(envelope-from tlambert2@mindspring.com)
Received: from mindspring.com (dialup-209.245.130.195.Dial1.SanJose1.Level3.net [209.245.130.195])
by albatross.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id CAA09922;
Tue, 26 Jun 2001 02:04:28 -0700 (PDT)
Message-ID: <3B38503D.AD53EBCD@mindspring.com>
Date: Tue, 26 Jun 2001 02:05:01 -0700
From: Terry Lambert <tlambert2@mindspring.com>
Reply-To: tlambert2@mindspring.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Lawrence S. Lansing" <lansil@rpi.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: custom bootable CD & /usr/src/sys/i386/boot/cdboot
References: <Pine.A41.3.96.1010626002910.64824A-100000@vcmr-19.rcs.rpi.edu>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
"Lawrence S. Lansing" wrote:
>
> Hello. I am trying to create a custom bootable FreeBSD CD
> with a "live" filesystem.
[ ... ]
> 2 -- The boot image is created by running 'make' in
> /usr/src/sys/i386/boot/cdboot. This image contains a
> smarter 'loader', which is able to read an ISO9660
> filesystem for the kernel and root filesystem. I
> believe this boot image contains boot0/1 and /boot/cdboot.
> /boot/cdboot appears to be created from
> /usr/src/sys/boot/i386/cdldr, a 'loader' wrapper which
> replaces boot2, and allows 'loader' to understand ISO9660.
[ ... ]
> I burned a CD, and attempted to boot from it. I was greeted
> with this message, generated by 'cdboot':
>
> ---
> Your BIOS int 0x13 extensions seem to be disabled.
> It's impossible to boot a CD-ROM without them.
> (BIOS int 0x13 fn 0x4b01 yielded error 75
> ---
>
> The same message appears when the CD is booted in three
> different machines, all with fairly recent hardware and
> BIOSes. I have the distinct suspicion that the error
> message is bogus. I'm working with a recent -STABLE
> source tree (within the last week), but it doesn't appear
> that any of the boot-related files have been changed in
> almost a year.
The message means that it can't read your CDROM using
INT 13 BIOS calls, since your controller didn't hook INT
13 to install CDROM support.
Most "bootable CDROMs" that boot directly, without the
El Torito -> floppy image in memory hack, are SCSI (e.g.
on recent model Adaptec controllers, with the SCSI BIOS
set to make the CDROM look like a standard disk to the
INT 13 interface).
The only IDE CDROMs that I've seen that can do this need
you to reflash your BIOS with the extensions (there is an
AMI BIOS version 1.5 that has this capability, but it
only runs on certain SuperMicro motherboards). As far as
they are concerned, the CDROM then looks like a regular
disk to the BIOS.
The really old code you are looking at, from the Attic,
is, I think, a.out specific.
See also the comments in:
<http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/i386/boot/cdboot/Attic/bios.S>
[ ... ]
] Only SCSI CD-ROMs are supported, since i fail to see any
] possibility to determine the drive type using BIOS functions.
] (Even for hard disks, this determination is done by a big
] hack only.)
[ ... ]
You would be much better off doing the chroot onto the CD
after booting hack; that, at least, will work anywhere you
can boot the CDROM normally.
Mostly, the cdboot code is used for the DEC Alpha; See also:
http://www.FreeBSD.org/cgi/cvsweb.cgi/src/lib/libstand/cd9660.c
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 3: 2:50 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42])
by hub.freebsd.org (Postfix) with ESMTP id 8C7A137B406
for <hackers@freebsd.org>; Tue, 26 Jun 2001 03:02:46 -0700 (PDT)
(envelope-from matusita@jp.FreeBSD.org)
Received: from localhost (localhost [127.0.0.1])
by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f5QA2da24968;
Tue, 26 Jun 2001 19:02:39 +0900 (JST)
(envelope-from matusita@jp.FreeBSD.org)
Cc: hackers@freebsd.org
In-Reply-To: <Pine.A41.3.96.1010626002910.64824A-100000@vcmr-19.rcs.rpi.edu>
References: <Pine.A41.3.96.1010626002910.64824A-100000@vcmr-19.rcs.rpi.edu>
X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu
e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0
P\):.2}8jo-BiZ?X&t$V
X-User-Agent: Mew/1.94.2 XEmacs/21.5 (alfalfa)
X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Dispatcher: imput version 20000228(IM140)
Lines: 34
From: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>
To: "Lawrence S. Lansing" <lansil@rpi.edu>
Subject: Re: custom bootable CD & /usr/src/sys/i386/boot/cdboot
Date: Tue, 26 Jun 2001 19:02:27 +0900
Message-Id: <20010626190227C.matusita@jp.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
I also want to know how to use cdboot, however:
lansil> 1 -- The boot image contains a gzipped kernel, MFS, loader, and other
lansil> relevant /boot stuff. The Kernel and MFS in the boot image are used to
lansil> mount the CD filesystem, and possibly chroot to the CD filesystem. The
lansil> FreeBSD install CD uses this method.
The boot image shouldn't require MFS, as installation floppy does. The
minimal requirement for boot image is: /boot/loader and its
configulation file, kernel itself (gzipped kernel will be required,
since kernel tends to be large), and that's all.
You can mount CD filesystem as 'root filesystem' after booting a kernel.
check -C option of boot(8) (loader(8) has same functionality, boot_cdrom
but it's not described in its manpage). Be aware that this method
doesn't work with recent 5-current although 4-stable works fine.
***
Demonstrative bootable CD-ROM image you may want to make is available
our SNAPSHOTs project:
ftp://current.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/ISO-IMAGES/live-releng4.iso
This is bootable 'live filesystem' of recent 4-stable (simply goes to
the single-user mode).
... and you can easily checks '5-current kernel doesn't work with
CD9660 filesystem as root' with live-current.iso. I've already
reported to current@freebsd.org but no helps.
-- -
Makoto MATSUSHITA
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 6: 7: 5 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 789)
id 400C437B405; Tue, 26 Jun 2001 06:06:59 -0700 (PDT)
From: Marc van Woerkom <3d@hub.freebsd.org>
To: freebsd-hackers@freebsd.org
Subject: swapping bytes, fpos_t
Reply-To: 3d@freebsd.org
Message-Id: <20010626130659.400C437B405@hub.freebsd.org>
Date: Tue, 26 Jun 2001 06:06:59 -0700 (PDT)
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi,
while porting the ogle dvd player I faced the
problem of needing fast byte swap routines for
16, 32 and 64 bit words.
After grepping through the -CURRENT sources
I came up with at least three different
assembler implementations.
- one in NTOHS, NTOHL
- one undocumented swap16/swap32 used by USB driver
- perhaps swab() from the string lib (might need src!=dest)
I finally gave up and used the same solution that
the xine player porter took - taking code from
the ac3dec library.
What do you guys advice?
Oh yes, and I used fpos_t in all parts of libdvdread,
that were used for seeking.
Is this ugly, should better use the uint64 type
burried deep with the machine dependent headers?
What is good coding practice here?
Regards,
Marc
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 6:50:24 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13])
by hub.freebsd.org (Postfix) with SMTP id 8546F37B406
for <freebsd-hackers@FreeBSD.org>; Tue, 26 Jun 2001 06:50:19 -0700 (PDT)
(envelope-from roam@ringworld.nanolink.com)
Received: (qmail 686 invoked by uid 1000); 26 Jun 2001 13:55:01 -0000
Date: Tue, 26 Jun 2001 16:55:01 +0300
From: Peter Pentchev <roam@orbitel.bg>
To: freebsd-hackers@FreeBSD.org
Subject: Re: swapping bytes, fpos_t
Message-ID: <20010626165501.B549@ringworld.oblivion.bg>
Mail-Followup-To: freebsd-hackers@FreeBSD.org
References: <20010626130659.400C437B405@hub.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010626130659.400C437B405@hub.freebsd.org>; from 3d@hub.freebsd.org on Tue, Jun 26, 2001 at 06:06:59AM -0700
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Tue, Jun 26, 2001 at 06:06:59AM -0700, Marc van Woerkom wrote:
> Oh yes, and I used fpos_t in all parts of libdvdread,
> that were used for seeking.
> Is this ugly, should better use the uint64 type
> burried deep with the machine dependent headers?
> What is good coding practice here?
For seeking, use off_t. It is a 64-bit signed integer.
If you need real 64-bit offsets (unsigned), then you
might use uoff_t; but off_t should be enough, and it *is*
the standard type for seek offsets.
G'luck,
Peter
--
Thit sentence is not self-referential because "thit" is not a word.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 7:10:11 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from netbank.com.br (garrincha.netbank.com.br [200.203.199.88])
by hub.freebsd.org (Postfix) with ESMTP id BC59B37B409
for <hackers@FreeBSD.ORG>; Tue, 26 Jun 2001 07:10:07 -0700 (PDT)
(envelope-from riel@conectiva.com.br)
Received: from surriel.ddts.net (1-130.ctame701-1.telepar.net.br [200.181.137.130])
by netbank.com.br (Postfix) with ESMTP
id E060B4680A; Tue, 26 Jun 2001 11:06:16 -0300 (BRST)
Received: from localhost (vwokol@localhost [127.0.0.1])
by surriel.ddts.net (8.11.4/8.11.2) with ESMTP id f5QE9qC29406;
Tue, 26 Jun 2001 11:09:52 -0300
Date: Tue, 26 Jun 2001 11:09:52 -0300 (BRST)
From: Rik van Riel <riel@conectiva.com.br>
X-Sender: riel@imladris.rielhome.conectiva
To: Wes Peters <wes@softweyr.com>
Cc: Rahul Siddharthan <rsidd@physics.iisc.ernet.in>,
hackers@FreeBSD.ORG
Subject: Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
In-Reply-To: <3B384D41.4C24BC09@softweyr.com>
Message-ID: <Pine.LNX.4.21.0106261106450.7419-100000@imladris.rielhome.conectiva>
X-spambait: aardvark@kernelnewbies.org
X-spammeplease: aardvark@nl.linux.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Tue, 26 Jun 2001, Wes Peters wrote:
> Rik van Riel wrote:
> > On Sun, 24 Jun 2001, Rahul Siddharthan wrote:
> > > Wes Peters said on Jun 23, 2001 at 23:28:42:
> > > > > Plenty of GNU stuff there, though it doesn't say so explicitly.
> > > > > Of course, they say it's all meant only for "legacy Unix" stuff.
> > > >
> > > > Can you substantiate your claim there is "plenty of GNU stuff" in
> > > > Interix, or are you just talking out your ass as usual?
> >
> > gcc, gdb, bash, gnu emacs and a bunch more.
>
> Out of several hundred utilities?
[snip troll]
> </taunt weenies=Linux>
I hope you're having fun receiving flames from more
impressionable people ;)
Personally I don't care much about BSD vs. GPL and am
annoyed by Microsoft's hypocricy (sp?). The fact that
they're using open source software is great.
cheers,
Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...
http://www.surriel.com/ http://distro.conectiva.com/
Send all your spam to aardvark@nl.linux.org (spam digging piggy)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 11:30:41 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from hotmail.com (f162.law11.hotmail.com [64.4.17.162])
by hub.freebsd.org (Postfix) with ESMTP id 7CCE737B401
for <hackers@freebsd.org>; Tue, 26 Jun 2001 11:30:35 -0700 (PDT)
(envelope-from part_lion@hotmail.com)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
Tue, 26 Jun 2001 11:30:30 -0700
Received: from 64.242.6.171 by lw11fd.law11.hotmail.msn.com with HTTP; Tue, 26 Jun 2001 18:30:30 GMT
X-Originating-IP: [64.242.6.171]
From: "Joesh Juphland" <part_lion@hotmail.com>
To: hackers@freebsd.org
Subject: bridging with pcmcia cards
Date: Tue, 26 Jun 2001 12:30:30 -0600
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F162IBbT34IrPzq0sss0001adf6@hotmail.com>
X-OriginalArrivalTime: 26 Jun 2001 18:30:30.0245 (UTC) FILETIME=[140A4950:01C0FE6E]
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Recently on this list someone mentioned that you cannot bridge with the 'wi'
driver. This interests me and I have some questions:
(I am running strictly 4.3-RELEASE, btw)
1. is this just temporary - or will we _never_ be able to bridge with 'wi'
?
2. can I bridge with 'an' (cisco aironet cards) ?
3. can I bridge between two 'ep' cards (3com pcmcia) ?
4. Finally, if the answer to #2 was 'yes', can I bridge between ep0 and an0
?
I am just trying to figure out if the difficulties with 'wi' bridging are an
odd, isolated case, or if bridging on pcmcia cards is, in general,
difficult.
Any further comments / suggestions also appreciated.
thanks.
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 11:40: 6 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from sneakerz.org (sneakerz.org [216.33.66.254])
by hub.freebsd.org (Postfix) with ESMTP id B340437B401
for <hackers@freebsd.org>; Tue, 26 Jun 2001 11:40:01 -0700 (PDT)
(envelope-from bright@sneakerz.org)
Received: by sneakerz.org (Postfix, from userid 1092)
id 213B75D010; Tue, 26 Jun 2001 13:39:51 -0500 (CDT)
Date: Tue, 26 Jun 2001 13:39:51 -0500
From: Alfred Perlstein <bright@sneakerz.org>
To: Joesh Juphland <part_lion@hotmail.com>
Cc: hackers@freebsd.org
Subject: Re: bridging with pcmcia cards
Message-ID: <20010626133951.N64836@sneakerz.org>
References: <F162IBbT34IrPzq0sss0001adf6@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <F162IBbT34IrPzq0sss0001adf6@hotmail.com>; from part_lion@hotmail.com on Tue, Jun 26, 2001 at 12:30:30PM -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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
* Joesh Juphland <part_lion@hotmail.com> [010626 13:30] wrote:
>
> Recently on this list someone mentioned that you cannot bridge with the 'wi'
> driver. This interests me and I have some questions:
>
> (I am running strictly 4.3-RELEASE, btw)
>
> 1. is this just temporary - or will we _never_ be able to bridge with 'wi'
> ?
>
> 2. can I bridge with 'an' (cisco aironet cards) ?
>
> 3. can I bridge between two 'ep' cards (3com pcmcia) ?
>
> 4. Finally, if the answer to #2 was 'yes', can I bridge between ep0 and an0
> ?
>
> I am just trying to figure out if the difficulties with 'wi' bridging are an
> odd, isolated case, or if bridging on pcmcia cards is, in general,
> difficult.
Ethernet bridging should work, however we can't the wireless bridging
trick where you can wander around from access point to access point
and be connected properly.
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 11:45:33 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9])
by hub.freebsd.org (Postfix) with ESMTP id 49C5837B407
for <hackers@freebsd.org>; Tue, 26 Jun 2001 11:45:30 -0700 (PDT)
(envelope-from julian@elischer.org)
Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1])
by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA85573;
Tue, 26 Jun 2001 13:14:31 -0700 (PDT)
Date: Tue, 26 Jun 2001 13:14:30 -0700 (PDT)
From: Julian Elischer <julian@elischer.org>
To: Joesh Juphland <part_lion@hotmail.com>
Cc: hackers@freebsd.org
Subject: Re: bridging with pcmcia cards
In-Reply-To: <F162IBbT34IrPzq0sss0001adf6@hotmail.com>
Message-ID: <Pine.BSF.4.21.0106261313480.85371-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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
you WILL be able to bridge with WI cards
no time estimates though..
On Tue, 26 Jun 2001, Joesh Juphland wrote:
>
> Recently on this list someone mentioned that you cannot bridge with the 'wi'
> driver. This interests me and I have some questions:
>
> (I am running strictly 4.3-RELEASE, btw)
>
> 1. is this just temporary - or will we _never_ be able to bridge with 'wi'
> ?
>
> 2. can I bridge with 'an' (cisco aironet cards) ?
>
> 3. can I bridge between two 'ep' cards (3com pcmcia) ?
>
> 4. Finally, if the answer to #2 was 'yes', can I bridge between ep0 and an0
> ?
>
> I am just trying to figure out if the difficulties with 'wi' bridging are an
> odd, isolated case, or if bridging on pcmcia cards is, in general,
> difficult.
>
> Any further comments / suggestions also appreciated.
>
> thanks.
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 14: 9:46 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
by hub.freebsd.org (Postfix) with ESMTP id 6FED537B401
for <freebsd-hackers@FreeBSD.ORG>; Tue, 26 Jun 2001 14:09:37 -0700 (PDT)
(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
by pcnet1.pcnet.com (8.8.7/PCNet) id RAA12944;
Tue, 26 Jun 2001 17:08:56 -0400 (EDT)
Date: Tue, 26 Jun 2001 17:08:54 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
To: Louis-Philippe Gagnon <louisphilippe@macadamian.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: pthread/longjmp/signal problem
In-Reply-To: <0db001c0fa62$2b567800$2964a8c0@macadamian.com>
Message-ID: <Pine.SUN.3.91.1010626165947.10822A-100000@pcnet1.pcnet.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Thu, 21 Jun 2001, Louis-Philippe Gagnon wrote:
> No reactions the first time, let's try again.
>
> I've encountered a problem in the interaction betwen signals, longjmp and
> pthreads; I'm hoping someone can help me make sense of it.
>
> I've been trying to implement a IsBadReadPtr-style function in FreeBSD by
> using signal handlers and longjmp/setjmp. It seemed to work as expected,
> until I started using the -pthread option to gcc (thus linking against
> libc_r). Now the function only works on the first call; subsequent calls
> hang on the segmentation fault.
>
> Here's an example of the kind of code that causes problems :
Try this patch (to -stable). Only the patch to uthread_sig.c is
needed for -current.
--
Dan Eischen
Index: libc/i386/gen/setjmp.S
===================================================================
RCS file: /opt/FreeBSD/cvs/src/lib/libc/i386/gen/setjmp.S,v
retrieving revision 1.17.2.1
diff -u -r1.17.2.1 setjmp.S
--- libc/i386/gen/setjmp.S 2000/05/16 20:43:21 1.17.2.1
+++ libc/i386/gen/setjmp.S 2001/06/26 21:07:23
@@ -61,11 +61,7 @@
pushl %eax /* (sigset_t*)oset */
pushl $0 /* (sigset_t*)set */
pushl $1 /* SIG_BLOCK */
-#ifdef _THREAD_SAFE
- call PIC_PLT(CNAME(_thread_sys_sigprocmask))
-#else
call PIC_PLT(CNAME(sigprocmask))
-#endif
addl $12,%esp
PIC_EPILOGUE
movl 4(%esp),%ecx
@@ -91,11 +87,7 @@
leal 28(%edx), %eax
pushl %eax /* (sigset_t*)set */
pushl $3 /* SIG_SETMASK */
-#ifdef _THREAD_SAFE
- call PIC_PLT(CNAME(_thread_sys_sigprocmask))
-#else
call PIC_PLT(CNAME(sigprocmask))
-#endif
addl $12,%esp
PIC_EPILOGUE
movl 4(%esp),%edx
Index: libc/i386/gen/sigsetjmp.S
===================================================================
RCS file: /opt/FreeBSD/cvs/src/lib/libc/i386/gen/sigsetjmp.S,v
retrieving revision 1.19.2.1
diff -u -r1.19.2.1 sigsetjmp.S
--- libc/i386/gen/sigsetjmp.S 2000/05/16 20:43:21 1.19.2.1
+++ libc/i386/gen/sigsetjmp.S 2001/06/26 21:04:34
@@ -70,11 +70,7 @@
pushl %eax /* (sigset_t*)oset */
pushl $0 /* (sigset_t*)set */
pushl $1 /* SIG_BLOCK */
-#ifdef _THREAD_SAFE
- call PIC_PLT(CNAME(_thread_sys_sigprocmask))
-#else
call PIC_PLT(CNAME(sigprocmask))
-#endif
addl $12,%esp
PIC_EPILOGUE
movl 4(%esp),%ecx
@@ -102,11 +98,7 @@
leal 28(%edx), %eax
pushl %eax /* (sigset_t*)set */
pushl $3 /* SIG_SETMASK */
-#ifdef _THREAD_SAFE
- call PIC_PLT(CNAME(_thread_sys_sigprocmask))
-#else
call PIC_PLT(CNAME(sigprocmask))
-#endif
addl $12,%esp
PIC_EPILOGUE
movl 4(%esp),%edx
Index: libc_r/uthread/uthread_sig.c
===================================================================
RCS file: /opt/FreeBSD/cvs/src/lib/libc_r/uthread/uthread_sig.c,v
retrieving revision 1.25.2.7
diff -u -r1.25.2.7 uthread_sig.c
--- libc_r/uthread/uthread_sig.c 2001/06/23 00:47:05 1.25.2.7
+++ libc_r/uthread/uthread_sig.c 2001/06/26 20:56:52
@@ -931,6 +931,12 @@
thread->curframe = NULL;
PTHREAD_ASSERT(psf != NULL, "Invalid signal frame in signal handler");
+ /*
+ * We came here from the kernel scheduler; clear the in scheduler
+ * flag.
+ */
+ _thread_kern_in_sched = 0;
+
/* Check the threads previous state: */
if (psf->saved_state.psd_state != PS_RUNNING) {
/*
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 14:16:49 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from hotmail.com (f110.law11.hotmail.com [64.4.17.110])
by hub.freebsd.org (Postfix) with ESMTP id 6019737B406
for <hackers@freebsd.org>; Tue, 26 Jun 2001 14:16:35 -0700 (PDT)
(envelope-from part_lion@hotmail.com)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
Tue, 26 Jun 2001 14:16:30 -0700
Received: from 64.242.6.171 by lw11fd.law11.hotmail.msn.com with HTTP; Tue, 26 Jun 2001 21:16:30 GMT
X-Originating-IP: [64.242.6.171]
From: "Joesh Juphland" <part_lion@hotmail.com>
To: julian@elischer.org
Cc: hackers@freebsd.org
Subject: Re: bridging with pcmcia cards
Date: Tue, 26 Jun 2001 15:16:30 -0600
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F110wl3tTUqp2T0apMH0000d5db@hotmail.com>
X-OriginalArrivalTime: 26 Jun 2001 21:16:30.0171 (UTC) FILETIME=[449E62B0:01C0FE85]
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Great.
Can I already bridge with an* ? And does this mean that bridging in
general with pc cards is a-ok ?
thanks.
>you WILL be able to bridge with WI cards
>no time estimates though..
>
>
>On Tue, 26 Jun 2001, Joesh Juphland wrote:
>
> >
> > Recently on this list someone mentioned that you cannot bridge with the
>'wi'
> > driver. This interests me and I have some questions:
> >
> > (I am running strictly 4.3-RELEASE, btw)
> >
> > 1. is this just temporary - or will we _never_ be able to bridge with
>'wi'
> > ?
> >
> > 2. can I bridge with 'an' (cisco aironet cards) ?
> >
> > 3. can I bridge between two 'ep' cards (3com pcmcia) ?
> >
> > 4. Finally, if the answer to #2 was 'yes', can I bridge between ep0 and
>an0
> > ?
> >
> > I am just trying to figure out if the difficulties with 'wi' bridging
>are an
> > odd, isolated case, or if bridging on pcmcia cards is, in general,
> > difficult.
> >
> > Any further comments / suggestions also appreciated.
> >
> > thanks.
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at http://explorer.msn.com
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-hackers" in the body of the message
> >
>
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 14:19:44 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from coffee.q9media.com (coffee.q9media.com [216.94.229.19])
by hub.freebsd.org (Postfix) with ESMTP
id 2366B37B409; Tue, 26 Jun 2001 14:19:40 -0700 (PDT)
(envelope-from mike@q9media.com)
Received: from [192.168.1.10] (vega.tct.net [216.94.230.13])
by coffee.q9media.com (8.11.2/8.11.2) with ESMTP id f5QLWnL94357;
Tue, 26 Jun 2001 17:32:49 -0400 (EDT)
(envelope-from mike@q9media.com)
User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022
Date: Tue, 26 Jun 2001 17:19:41 -0400
Subject: Re: [RFC] whois(1) - recursive IP searches
From: Mike Barcroft <mike@q9media.com>
To: <hackers@freebsd.org>
Cc: <phk@freebsd.org>, <joe@freebsd.org>
Message-ID: <B75E74AD.DEC%mike@q9media.com>
In-Reply-To: <B758E9BD.D6B%mike@q9media.com>
Mime-version: 1.0
Organization: q9 media
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Mike Barcroft <mike@q9media.com> writes:
> I would appreciate comments on the following patch:
> http://testbed.q9media.net/freebsd/whois.20010622.patch
>
> It does the following:
>
> o Implement recursive IP Address searches based on the results of
> a query to ARIN. This allows a user to type 'whois 210.139.255.223'
> and get the expected results.
> [Requested by joe and phk]
> o Update documentation to reflect this.
> o Clean up some grammar nearby.
If anyone is interested in committing this, I've opened a PR.
PR #: bin/28426
Best regards,
Mike Barcroft
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 14:45:31 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9])
by hub.freebsd.org (Postfix) with ESMTP id 2DAAA37B409
for <hackers@freebsd.org>; Tue, 26 Jun 2001 14:45:26 -0700 (PDT)
(envelope-from julian@elischer.org)
Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1])
by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA86174;
Tue, 26 Jun 2001 16:04:57 -0700 (PDT)
Date: Tue, 26 Jun 2001 16:04:55 -0700 (PDT)
From: Julian Elischer <julian@elischer.org>
To: Joesh Juphland <part_lion@hotmail.com>
Cc: hackers@freebsd.org
Subject: Re: bridging with pcmcia cards
In-Reply-To: <F110wl3tTUqp2T0apMH0000d5db@hotmail.com>
Message-ID: <Pine.BSF.4.21.0106261604020.85692-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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
bridging is not a function of it being a pc-card..
actually bridging may already work with wi cards
also netgraph bridgiung may also work...
On Tue, 26 Jun 2001, Joesh Juphland wrote:
>
> Great.
>
> Can I already bridge with an* ? And does this mean that bridging in
> general with pc cards is a-ok ?
>
> thanks.
>
> >you WILL be able to bridge with WI cards
> >no time estimates though..
> >
> >
> >On Tue, 26 Jun 2001, Joesh Juphland wrote:
> >
> > >
> > > Recently on this list someone mentioned that you cannot bridge with the
> >'wi'
> > > driver. This interests me and I have some questions:
> > >
> > > (I am running strictly 4.3-RELEASE, btw)
> > >
> > > 1. is this just temporary - or will we _never_ be able to bridge with
> >'wi'
> > > ?
> > >
> > > 2. can I bridge with 'an' (cisco aironet cards) ?
> > >
> > > 3. can I bridge between two 'ep' cards (3com pcmcia) ?
> > >
> > > 4. Finally, if the answer to #2 was 'yes', can I bridge between ep0 and
> >an0
> > > ?
> > >
> > > I am just trying to figure out if the difficulties with 'wi' bridging
> >are an
> > > odd, isolated case, or if bridging on pcmcia cards is, in general,
> > > difficult.
> > >
> > > Any further comments / suggestions also appreciated.
> > >
> > > thanks.
> > > _________________________________________________________________
> > > Get your FREE download of MSN Explorer at http://explorer.msn.com
> > >
> > >
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-hackers" in the body of the message
> > >
> >
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 14:55:53 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75])
by hub.freebsd.org (Postfix) with ESMTP id B88F837B401
for <hackers@freebsd.org>; Tue, 26 Jun 2001 14:55:46 -0700 (PDT)
(envelope-from brdavis@odin.ac.hmc.edu)
Received: (from brdavis@localhost)
by odin.ac.hmc.edu (8.11.0/8.11.0) id f5QLtkC14190
for hackers@freebsd.org; Tue, 26 Jun 2001 14:55:46 -0700
Date: Tue, 26 Jun 2001 14:55:46 -0700
From: Brooks Davis <brooks@one-eyed-alien.net>
To: hackers@freebsd.org
Subject: rman wildcard question
Message-ID: <20010626145546.B7909@Odin.AC.HMC.Edu>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="kORqDWCi7qDJ0mEj"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
--kORqDWCi7qDJ0mEj
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In the gif interface cloning code I used the resource management code
like Brian did in the tun cloning code to manage unit numbers. When the
user requests an arbitrary unit, they get the first one available, but
I'm not convinced that's what we want because that has the potential to
interfere with static configurations with temporary holes in them. It
seems that a more logical policy would be to allocate the largest
available unit, but rman_reserve_resource doesn't seem to allow that.
Is there a way to do this that I'm just not seeing?
-- 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
--kORqDWCi7qDJ0mEj
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7OQThXY6L6fI4GtQRAvdsAJwMBsFJPL2Oh5edFHTiMNGymX0dCgCgkZEf
3p0REjCuX9z5l6hzC/FnX3Q=
=eBAv
-----END PGP SIGNATURE-----
--kORqDWCi7qDJ0mEj--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 15:38:13 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138])
by hub.freebsd.org (Postfix) with ESMTP id CB73E37B40A
for <hackers@freebsd.org>; Tue, 26 Jun 2001 15:38:10 -0700 (PDT)
(envelope-from dima@unixfreak.org)
Received: from hornet.unixfreak.org (hornet [63.198.170.140])
by bazooka.unixfreak.org (Postfix) with ESMTP id B70933E31
for <hackers@freebsd.org>; Tue, 26 Jun 2001 15:04:07 -0700 (PDT)
To: hackers@freebsd.org
Subject: ifmcstat(8) setgidness
Date: Tue, 26 Jun 2001 15:04:07 -0700
From: Dima Dorfman <dima@unixfreak.org>
Message-Id: <20010626220407.B70933E31@bazooka.unixfreak.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi folks,
Is there a particular reason, other than the desire for more setgid
programs, that ifmcstat(8) is setgid kmem? It seems that there's no
reason anyone but root would want to use it, anyway. OpenBSD and
NetBSD already nuked its setgid bit; any reason why we shouldn't
follow suit?
Thanks,
Dima Dorfman
dima@unixfreak.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 20:44:36 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from amant.pdl.cs.cmu.edu (AMANT.PDL.CS.CMU.EDU [128.2.189.84])
by hub.freebsd.org (Postfix) with ESMTP id 2E53637B401
for <freebsd-hackers@freebsd.org>; Tue, 26 Jun 2001 20:44:34 -0700 (PDT)
(envelope-from dpetrou@amant.pdl.cs.cmu.edu)
Received: (from dpetrou@localhost)
by amant.pdl.cs.cmu.edu (8.11.1/8.11.1) id f5R3h2W69094
for freebsd-hackers@freebsd.org; Tue, 26 Jun 2001 23:43:02 -0400 (EDT)
(envelope-from dpetrou)
Date: Tue, 26 Jun 2001 23:43:02 -0400
From: David Petrou <dpetrou@cs.cmu.edu>
To: freebsd-hackers@freebsd.org
Subject: what #define for thread-safeness?
Message-ID: <20010626234302.E68913@amant.pdl.cs.cmu.edu>
Reply-To: dpetrou@cs.cmu.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
X-Hit-Pick: Philip Glass / Songs From Liquid Days
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi. On linux, I know that when compiling threaded code I need to
#define _REENTRANT. What's the right thing to do on FreeBSD? I've
searched around the FreeBSD pages and have come up empty. I googled
around and found a post from a Mozilla page recommending I #define
_THREAD_SAFE. I'd just like an authoratative answer so I don't get
bit by some weirdness down the line.
thanks,
david
p.s.: please also respond to me since i'm not subscribed to this list.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Tue Jun 26 20:50:53 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42])
by hub.freebsd.org (Postfix) with ESMTP id C37A237B401
for <hackers@FreeBSD.ORG>; Tue, 26 Jun 2001 20:50:50 -0700 (PDT)
(envelope-from ambrisko@ambrisko.com)
Received: (from ambrisko@localhost)
by ambrisko.com (8.11.3/8.11.3) id f5R3nQd71266;
Tue, 26 Jun 2001 20:49:26 -0700 (PDT)
(envelope-from ambrisko)
From: Doug Ambrisko <ambrisko@ambrisko.com>
Message-Id: <200106270349.f5R3nQd71266@ambrisko.com>
Subject: Re: bridging with pcmcia cards
In-Reply-To: <F110wl3tTUqp2T0apMH0000d5db@hotmail.com> "from Joesh Juphland at
Jun 26, 2001 03:16:30 pm"
To: Joesh Juphland <part_lion@hotmail.com>
Date: Tue, 26 Jun 2001 20:49:25 -0700 (PDT)
Cc: julian@elischer.org, hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL82 (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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Joesh Juphland writes:
|
| Great.
|
| Can I already bridge with an* ? And does this mean that bridging in
| general with pc cards is a-ok ?
This has been reported to work with the "an" driver with netgraph
bridging.
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 Jun 27 1:15: 2 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65])
by hub.freebsd.org (Postfix) with ESMTP id 1877737B401
for <hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 01:14:57 -0700 (PDT)
(envelope-from ru@whale.sunbay.crimea.ua)
Received: (from ru@localhost)
by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f5R8EeB11998;
Wed, 27 Jun 2001 11:14:40 +0300 (EEST)
(envelope-from ru)
Date: Wed, 27 Jun 2001 11:14:40 +0300
From: Ruslan Ermilov <ru@FreeBSD.ORG>
To: Dima Dorfman <dima@unixfreak.org>
Cc: hackers@FreeBSD.ORG
Subject: Re: ifmcstat(8) setgidness
Message-ID: <20010627111440.F2097@sunbay.com>
Mail-Followup-To: Dima Dorfman <dima@unixfreak.org>,
hackers@FreeBSD.ORG
References: <20010626220407.B70933E31@bazooka.unixfreak.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010626220407.B70933E31@bazooka.unixfreak.org>; from dima@unixfreak.org on Tue, Jun 26, 2001 at 03:04:07PM -0700
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Tue, Jun 26, 2001 at 03:04:07PM -0700, Dima Dorfman wrote:
> Hi folks,
>
> Is there a particular reason, other than the desire for more setgid
> programs, that ifmcstat(8) is setgid kmem? It seems that there's no
> reason anyone but root would want to use it, anyway. OpenBSD and
> NetBSD already nuked its setgid bit; any reason why we shouldn't
> follow suit?
>
$ ifmcstat
kvm_openfiles: Permission denied
--
Ruslan Ermilov Oracle Developer/DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 1:29:30 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138])
by hub.freebsd.org (Postfix) with ESMTP
id 98A7B37B401; Wed, 27 Jun 2001 01:29:28 -0700 (PDT)
(envelope-from dima@unixfreak.org)
Received: from hornet.unixfreak.org (hornet [63.198.170.140])
by bazooka.unixfreak.org (Postfix) with ESMTP
id 47C933E31; Wed, 27 Jun 2001 01:29:28 -0700 (PDT)
To: ru@FreeBSD.org, hackers@FreeBSD.ORG
Subject: Re: ifmcstat(8) setgidness
In-Reply-To: <20010627111440.F2097@sunbay.com>; from ru@FreeBSD.ORG on "Wed, 27 Jun 2001 11:14:40 +0300"
Date: Wed, 27 Jun 2001 01:29:28 -0700
From: Dima Dorfman <dima@unixfreak.org>
Message-Id: <20010627082928.47C933E31@bazooka.unixfreak.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Ruslan Ermilov <ru@FreeBSD.ORG> writes:
> On Tue, Jun 26, 2001 at 03:04:07PM -0700, Dima Dorfman wrote:
> > Hi folks,
> >
> > Is there a particular reason, other than the desire for more setgid
> > programs, that ifmcstat(8) is setgid kmem? It seems that there's no
> > reason anyone but root would want to use it, anyway. OpenBSD and
> > NetBSD already nuked its setgid bit; any reason why we shouldn't
> > follow suit?
> >
> $ ifmcstat
> kvm_openfiles: Permission denied
I don't follow. Yes, it needs access to kmem to work. However, I
don't see why anyone other than root would need to run it, so why is
it setgid? root can access kmem either way.
>
> --
> Ruslan Ermilov Oracle Developer/DBA,
> ru@sunbay.com Sunbay Software AG,
> ru@FreeBSD.org FreeBSD committer,
> +380.652.512.251 Simferopol, Ukraine
>
> http://www.FreeBSD.org The Power To Serve
> http://www.oracle.com Enabling The Information Age
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 2: 5:43 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65])
by hub.freebsd.org (Postfix) with ESMTP id 1AF0C37B406
for <hackers@FreeBSD.org>; Wed, 27 Jun 2001 02:05:32 -0700 (PDT)
(envelope-from ru@whale.sunbay.crimea.ua)
Received: (from ru@localhost)
by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f5R95DH18317;
Wed, 27 Jun 2001 12:05:13 +0300 (EEST)
(envelope-from ru)
Date: Wed, 27 Jun 2001 12:05:13 +0300
From: Ruslan Ermilov <ru@FreeBSD.org>
To: Dima Dorfman <dima@unixfreak.org>
Cc: hackers@FreeBSD.org
Subject: Re: ifmcstat(8) setgidness
Message-ID: <20010627120513.B14399@sunbay.com>
Mail-Followup-To: Dima Dorfman <dima@unixfreak.org>,
hackers@FreeBSD.org
References: <20010627111440.F2097@sunbay.com> <20010627082928.47C933E31@bazooka.unixfreak.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010627082928.47C933E31@bazooka.unixfreak.org>; from dima@unixfreak.org on Wed, Jun 27, 2001 at 01:29:28AM -0700
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Wed, Jun 27, 2001 at 01:29:28AM -0700, Dima Dorfman wrote:
> Ruslan Ermilov <ru@FreeBSD.ORG> writes:
> > On Tue, Jun 26, 2001 at 03:04:07PM -0700, Dima Dorfman wrote:
> > > Hi folks,
> > >
> > > Is there a particular reason, other than the desire for more setgid
> > > programs, that ifmcstat(8) is setgid kmem? It seems that there's no
> > > reason anyone but root would want to use it, anyway. OpenBSD and
> > > NetBSD already nuked its setgid bit; any reason why we shouldn't
> > > follow suit?
> > >
> > $ ifmcstat
> > kvm_openfiles: Permission denied
>
> I don't follow. Yes, it needs access to kmem to work. However, I
> don't see why anyone other than root would need to run it, so why is
> it setgid? root can access kmem either way.
>
Could you please elaborate on why it should be restricted to root only?
OpenBSD's and NetBSD's commitlogs are too terse.
Cheers,
--
Ruslan Ermilov Oracle Developer/DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 3: 1:25 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from london.physics.purdue.edu (london.physics.purdue.edu [128.210.67.35])
by hub.freebsd.org (Postfix) with ESMTP id ED5F137B406
for <freebsd-hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 03:01:22 -0700 (PDT)
(envelope-from will@physics.purdue.edu)
Received: from bohr.physics.purdue.edu (bohr.physics.purdue.edu [128.210.67.12])
by london.physics.purdue.edu (8.8.8/8.8.8) with ESMTP id FAA09581;
Wed, 27 Jun 2001 05:01:21 -0500 (EST)
Received: by bohr.physics.purdue.edu (Postfix, from userid 12409)
id 9D6035BB5; Wed, 27 Jun 2001 05:01:21 -0500 (EST)
Date: Wed, 27 Jun 2001 05:01:21 -0500
From: Will Andrews <will@physics.purdue.edu>
To: David Petrou <dpetrou@cs.cmu.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: what #define for thread-safeness?
Message-ID: <20010627050121.B97456@bohr.physics.purdue.edu>
Reply-To: Will Andrews <will@physics.purdue.edu>
References: <20010626234302.E68913@amant.pdl.cs.cmu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <20010626234302.E68913@amant.pdl.cs.cmu.edu>; from dpetrou@cs.cmu.edu on Tue, Jun 26, 2001 at 11:43:02PM -0400
X-Operating-System: FreeBSD 4.3-STABLE 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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Tue, Jun 26, 2001 at 11:43:02PM -0400, David Petrou (dpetrou@cs.cmu.edu) wrote:
> Hi. On linux, I know that when compiling threaded code I need to
> #define _REENTRANT. What's the right thing to do on FreeBSD? I've
> searched around the FreeBSD pages and have come up empty. I googled
> around and found a post from a Mozilla page recommending I #define
> _THREAD_SAFE. I'd just like an authoratative answer so I don't get
> bit by some weirdness down the line.
-D_THREAD_SAFE is right. FreeBSD uses it in the ports collection.
--
wca
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 4: 5:19 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from carbon.btinternet.com (carbon.btinternet.com [194.73.73.92])
by hub.freebsd.org (Postfix) with ESMTP
id 6464E37B405; Wed, 27 Jun 2001 04:05:13 -0700 (PDT)
(envelope-from john.toon@btinternet.com)
Received: from host213-122-4-226.btinternet.com ([213.122.4.226] helo=btinternet.com)
by carbon.btinternet.com with esmtp (Exim 3.22 #9)
id 15FD89-0004gP-00; Wed, 27 Jun 2001 12:05:10 +0100
X-Mozilla-Status: 0801
Message-ID: <3B39BDED.6070609@btinternet.com>
Date: Wed, 27 Jun 2001 12:05:17 +0100
From: John Toon <john.toon@btinternet.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.1-RELEASE i386; en-US; rv:0.9.1) Gecko/20010621
X-Accept-Language: en-us
MIME-Version: 1.0
To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org
Subject: Linux Emulation Problems
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi,
I'm experiencing Linux emulation issues on my FreeBSD-4.1 setup.
Whenever I attempt to run a Linux binary, they try to access my FreeBSD
library /usr/X11R6/lib/libxalflaunch.so.0 - even for programs that
apparently have *no* need of this library (Linux version or otherwise).
In particular, neither the j2sdk-1_4_0-beta-linux-i386.bin archive
extracts, nor does does the setup program for the Linux binary of build
627 of OpenOffice run correctly. For example, the setup program reports:
./setup: error in loading shared libraries:
/usr/X11R6/lib/libxalflaunch.so.0: ELF file OS ABI invalid.
Doing a truss ./setup gives:
linux_brk(0x0) = 1 (0x1)
linux_open("/usr/X11R6/lib/libxalflaunch.so.0",0,03001520044) = 3 (0x3)
linux_newfstat(3,0xbfbff518) = 2 (0x2)
read(0x3,0xbfbfe56c,0x1000) = 3 (0x3)
close(3)
= 1 (0x1)
./setupwrite(2,0xbfbffc48,7) = 3 (0x3)
: error in loading shared libraries: write(2,0x18069820,37) = 3 (0x3)
/usr/X11R6/lib/libxalflaunch.so.0write(2,0xbfbff6fc,33) = 3 (0x3)
: write(2,0x18069816,2) = 3 (0x3)
ELF file OS ABI invalid.write(2,0x18068dc6,24) = 3 (0x3)
write(2,0x1806981b,0) = 3 (0x3)
write(2,0x1806981b,0) = 3 (0x3)
write(2,0x18069819,1) = 3 (0x3)
exit(0x7f)
process exit, rval = 32512
The Linux compatibility kernel module linux.ko is apparently loaded
correctly:
bash-2.04$ kldstat
Id Refs Address Size Name
1 3 0xc0100000 26da84 kernel
2 1 0xc131e000 17000 usb.ko
4 1 0xc1349000 10000 linux.ko
I tried reinstalling linux_base-6.1 to no effect.
I'm not sure why I'm getting these problems - Linux emulation ran
perfectly the last time I had a FreeBSD-4.x release installed on my
computer.
Anyone got any ideas/suggestions?
Regards,
John.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 4: 9:57 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from tungsten.btinternet.com (tungsten.btinternet.com [194.73.73.81])
by hub.freebsd.org (Postfix) with ESMTP id 7736037B401
for <freebsd-hackers@freebsd.org>; Wed, 27 Jun 2001 04:09:53 -0700 (PDT)
(envelope-from john.toon@btinternet.com)
Received: from host213-122-4-226.btinternet.com ([213.122.4.226] helo=btinternet.com)
by tungsten.btinternet.com with esmtp (Exim 3.22 #9)
id 15FDCf-0001qY-00
for freebsd-hackers@freebsd.org; Wed, 27 Jun 2001 12:09:50 +0100
Message-ID: <3B39BF38.4050405@btinternet.com>
Date: Wed, 27 Jun 2001 12:10:48 +0100
From: John Toon <john.toon@btinternet.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.1-RELEASE i386; en-US; rv:0.9.1) Gecko/20010621
X-Accept-Language: en-us
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
Subject: Linux Emulation Problems
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi,
I'm experiencing Linux emulation issues on my FreeBSD-4.1 setup.
Whenever I attempt to run a Linux binary, they try to access my FreeBSD
library /usr/X11R6/lib/libxalflaunch.so.0 - even for programs that
apparently have *no* need of this library (Linux version or otherwise).
In particular, neither the j2sdk-1_4_0-beta-linux-i386.bin archive
extracts, nor does does the setup program for the Linux binary of build
627 of OpenOffice run correctly. For example, the setup program reports:
./setup: error in loading shared libraries:
/usr/X11R6/lib/libxalflaunch.so.0: ELF file OS ABI invalid.
Doing a truss ./setup gives:
linux_brk(0x0) = 1 (0x1)
linux_open("/usr/X11R6/lib/libxalflaunch.so.0",0,03001520044) = 3 (0x3)
linux_newfstat(3,0xbfbff518) = 2 (0x2)
read(0x3,0xbfbfe56c,0x1000) = 3 (0x3)
close(3) = 1 (0x1)
./setupwrite(2,0xbfbffc48,7) = 3 (0x3)
: error in loading shared libraries: write(2,0x18069820,37) = 3 (0x3)
/usr/X11R6/lib/libxalflaunch.so.0write(2,0xbfbff6fc,33) = 3 (0x3)
: write(2,0x18069816,2) = 3 (0x3)
ELF file OS ABI invalid.write(2,0x18068dc6,24) = 3 (0x3)
write(2,0x1806981b,0) = 3 (0x3)
write(2,0x1806981b,0) = 3 (0x3)
write(2,0x18069819,1) = 3 (0x3)
exit(0x7f)
process exit, rval = 32512
The Linux compatibility kernel module linux.ko is apparently loaded
correctly:
bash-2.04$ kldstat
Id Refs Address Size Name
1 3 0xc0100000 26da84 kernel
2 1 0xc131e000 17000 usb.ko
4 1 0xc1349000 10000 linux.ko
I tried reinstalling linux_base-6.1 to no effect.
I'm not sure why I'm getting these problems - Linux emulation ran
perfectly the last time I had a FreeBSD-4.x release installed on my
computer.
Anyone got any ideas/suggestions?
Regards,
John.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 5:15:19 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
by hub.freebsd.org (Postfix) with ESMTP id 1BDEB37B406
for <freebsd-hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 05:15:13 -0700 (PDT)
(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
by pcnet1.pcnet.com (8.8.7/PCNet) id IAA11817;
Wed, 27 Jun 2001 08:14:28 -0400 (EDT)
Date: Wed, 27 Jun 2001 08:14:28 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
To: Will Andrews <will@physics.purdue.edu>
Cc: David Petrou <dpetrou@cs.cmu.edu>, freebsd-hackers@FreeBSD.ORG
Subject: Re: what #define for thread-safeness?
In-Reply-To: <20010627050121.B97456@bohr.physics.purdue.edu>
Message-ID: <Pine.SUN.3.91.1010627081043.11414A-100000@pcnet1.pcnet.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Wed, 27 Jun 2001, Will Andrews wrote:
> On Tue, Jun 26, 2001 at 11:43:02PM -0400, David Petrou (dpetrou@cs.cmu.edu) wrote:
> > Hi. On linux, I know that when compiling threaded code I need to
> > #define _REENTRANT. What's the right thing to do on FreeBSD? I've
> > searched around the FreeBSD pages and have come up empty. I googled
> > around and found a post from a Mozilla page recommending I #define
> > _THREAD_SAFE. I'd just like an authoratative answer so I don't get
> > bit by some weirdness down the line.
>
> -D_THREAD_SAFE is right. FreeBSD uses it in the ports collection.
This is (kinda) needed for -stable, but has no effect in -current. When
-current libc/libc_r stuff is merged to -stable, _THREAD_SAFE will go
bye-bye. If we need a thread safety flag in the future, it should
be _REENTRANT.
--
Dan Eischen
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 7:10:41 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from alphazed.com (magrathea.alphazed.com [209.181.49.240])
by hub.freebsd.org (Postfix) with SMTP id 96BF237B405
for <hackers@freebsd.org>; Wed, 27 Jun 2001 07:10:39 -0700 (PDT)
(envelope-from danny@alphazed.com)
Received: (qmail 16580 invoked by uid 1000); 27 Jun 2001 14:10:38 -0000
Date: Wed, 27 Jun 2001 15:10:38 +0100
From: daniel lawrence <danny@AlphaZed.com>
To: hackers@freebsd.org
Subject: HP9000/L1000
Message-ID: <20010627151038.I11787@alphazed.com>
Reply-To: danny@AlphaZed.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1us
Organization: AlphaZed, Ltd
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
This is probably a long shot, but I'll ask anyway. We have 3 HP9000/L1000
machines which we may be able to make available (serial console and network)
for some kind of BSD porting project.
I know it is probably off the beaten track a little, but would there be any
interest in this, or are resources already stretched too far?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 7:57: 9 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178])
by hub.freebsd.org (Postfix) with ESMTP
id 7A91C37B401; Wed, 27 Jun 2001 07:57:07 -0700 (PDT)
(envelope-from keichii@iteration.net)
Received: by peorth.iteration.net (Postfix, from userid 1001)
id CD68B59229; Wed, 27 Jun 2001 09:56:50 -0500 (CDT)
Date: Wed, 27 Jun 2001 09:56:50 -0500
From: "Michael C . Wu" <keichii@iteration.net>
To: daniel lawrence <danny@AlphaZed.com>, obrien@freebsd.org,
jhb@freebsd.org
Cc: hackers@freebsd.org
Subject: Re: HP9000/L1000
Message-ID: <20010627095650.B39552@peorth.iteration.net>
Reply-To: "Michael C . Wu" <keichii@peorth.iteration.net>
References: <20010627151038.I11787@alphazed.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010627151038.I11787@alphazed.com>; from danny@AlphaZed.com on Wed, Jun 27, 2001 at 03:10:38PM +0100
X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20
X-PGP-Key-ID: 0x8FA12E20
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Wed, Jun 27, 2001 at 03:10:38PM +0100, daniel lawrence scribbled:
| This is probably a long shot, but I'll ask anyway. We have 3 HP9000/L1000
| machines which we may be able to make available (serial console and network)
| for some kind of BSD porting project.
|
| I know it is probably off the beaten track a little, but would there be any
| interest in this, or are resources already stretched too far?
You should probably contact David O'Brien or John Baldwin @WindRiver
about this. obrien@freebsd.org and jhb@freebsd.org.
--
+-----------------------------------------------------------+
| keichii@iteration.net | keichii@freebsd.org |
| http://iteration.net/~keichii | Yes, BSD is a conspiracy. |
+-----------------------------------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 8: 1:25 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
by hub.freebsd.org (Postfix) with ESMTP id 6AE6B37B406
for <freebsd-hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 08:01:21 -0700 (PDT)
(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
by dan.emsphone.com (8.11.3/8.11.3) id f5RF1FJ04043;
Wed, 27 Jun 2001 10:01:15 -0500 (CDT)
(envelope-from dan)
Date: Wed, 27 Jun 2001 10:01:15 -0500
From: Dan Nelson <dnelson@emsphone.com>
To: John Toon <john.toon@btinternet.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Linux Emulation Problems
Message-ID: <20010627100115.A10463@dan.emsphone.com>
References: <3B39BF38.4050405@btinternet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B39BF38.4050405@btinternet.com>
User-Agent: Mutt/1.3.19i
X-OS: FreeBSD 5.0-CURRENT
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In the last episode (Jun 27), John Toon said:
> I'm experiencing Linux emulation issues on my FreeBSD-4.1 setup.
> Whenever I attempt to run a Linux binary, they try to access my
> FreeBSD library /usr/X11R6/lib/libxalflaunch.so.0 - even for programs
> that apparently have *no* need of this library (Linux version or
> otherwise). In particular, neither the
> j2sdk-1_4_0-beta-linux-i386.bin archive extracts, nor does does the
> setup program for the Linux binary of build 627 of OpenOffice run
> correctly. For example, the setup program reports:
Do you maybe have an LD_PRELOAD environment variable pulling in
libxalf? Or maybe those apps really need xalf, in which case you
should copy the Linux xalf libraries from a Linux box into your
/compat/linux tree.
> ./setup: error in loading shared libraries:
> /usr/X11R6/lib/libxalflaunch.so.0: ELF file OS ABI invalid.
--
Dan Nelson
dnelson@emsphone.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 9:23:51 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22])
by hub.freebsd.org (Postfix) with ESMTP id B59C137B405
for <freebsd-hackers@freebsd.org>; Wed, 27 Jun 2001 09:23:48 -0700 (PDT)
(envelope-from vel@bugz.infotecs.ru)
Received: (from vel@localhost)
by bugz.infotecs.ru (8.11.1/8.11.1) id f5RGH0243541
for freebsd-hackers@freebsd.org; Wed, 27 Jun 2001 20:17:00 +0400 (MSD)
(envelope-from vel)
From: "Eugene L. Vorokov" <vel@bugz.infotecs.ru>
Message-Id: <200106271617.f5RGH0243541@bugz.infotecs.ru>
Subject: accessing files from kld module
To: freebsd-hackers@freebsd.org
Date: Wed, 27 Jun 2001 20:17:00 +0400 (MSD)
X-Mailer: ELM [version 2.4ME+ PL82 (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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi,
probably this question was asked here many times before, but I'm new
to kernel mode hacks ... Is it somehow possible to access files from
my kld module ? I have seen functions like printf(), MALLOC() for
kernel mode, but nothing like open() ... using open() syscall
directly seems impossible too because generally I don't have struct proc
entry.
I would be very thankful for any information regarding this issue.
Regards,
Eugene
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 9:27:40 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp.bmi.net (smtp.bmi.net [204.57.191.31])
by hub.freebsd.org (Postfix) with ESMTP id EF75837B405
for <freebsd-hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 09:27:37 -0700 (PDT)
(envelope-from jmcoopr@webmail.bmi.net)
Received: from smtp.bmi.net (dsl-154.bmi.net [207.173.60.230])
by smtp.bmi.net (Pro-8.9.3/Pro-8.9.3) with SMTP id JAA16187;
Wed, 27 Jun 2001 09:27:29 -0700
Date: Wed, 27 Jun 2001 09:27:33 -0700
From: John Merryweather Cooper <jmcoopr@webmail.bmi.net>
To: Dan Nelson <dnelson@emsphone.com>
Cc: John Toon <john.toon@btinternet.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: Linux Emulation Problems
Message-ID: <20010627092733.E30605@johncoop>
References: <3B39BF38.4050405@btinternet.com> <20010627100115.A10463@dan.emsphone.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
In-Reply-To: <20010627100115.A10463@dan.emsphone.com>; from dnelson@emsphone.com on Wed, Jun 27, 2001 at 08:01:15 -0700
X-Mailer: Balsa 1.1.4
Lines: 35
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On 2001.06.27 08:01 Dan Nelson wrote:
> In the last episode (Jun 27), John Toon said:
> > I'm experiencing Linux emulation issues on my FreeBSD-4.1 setup.
> > Whenever I attempt to run a Linux binary, they try to access my
> > FreeBSD library /usr/X11R6/lib/libxalflaunch.so.0 - even for
> programs
> > that apparently have *no* need of this library (Linux version or
> > otherwise). In particular, neither the
> > j2sdk-1_4_0-beta-linux-i386.bin archive extracts, nor does does the
> > setup program for the Linux binary of build 627 of OpenOffice run
> > correctly. For example, the setup program reports:
>
> Do you maybe have an LD_PRELOAD environment variable pulling in
> libxalf? Or maybe those apps really need xalf, in which case you
> should copy the Linux xalf libraries from a Linux box into your
> /compat/linux tree.
>
> > ./setup: error in loading shared libraries:
> > /usr/X11R6/lib/libxalflaunch.so.0: ELF file OS ABI invalid.
>
> --
> Dan Nelson
> dnelson@emsphone.com
>
Helpful only if you have a Linux box . . . Xalf gets built/installed as
part of the Gnome-1.4 meta-port--but no corresponding support is built
into the /compat/linux stuff. For those of us without Linux boxes,
could some one update the XFree support in /compat/linux so I can start
WordPerfect, StarOffice, RealPlayer, and Linux-Netscape from a Gnome
menu. Currently, the only way to successfully start these apps is from
the command line of an xterm--otherwise, they all choke trying to find
Linux versions of the Xalf stuff. Major bummer . . .
jmc
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 10: 1:48 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from post.webmailer.de (natpost.webmailer.de [192.67.198.65])
by hub.freebsd.org (Postfix) with ESMTP id 6960137B409
for <freebsd-hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 10:01:45 -0700 (PDT)
(envelope-from freebsd-ml@econos.de)
Received: from stefan-bt (pD95024ED.dip.t-dialin.net [217.80.36.237])
by post.webmailer.de (8.9.3/8.8.7) with SMTP id TAA20838
for <freebsd-hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 19:01:43 +0200 (MET DST)
From: Stefan Hoffmeister <freebsd-ml@econos.de>
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: Linux Emulation Problems
Date: Wed, 27 Jun 2001 19:00:59 +0200
Organization: Econos
Message-ID: <j34kjt86lg84ar6sbundrtop0db34p568s@4ax.com>
References: <3B39BF38.4050405@btinternet.com>
In-Reply-To: <3B39BF38.4050405@btinternet.com>
X-Mailer: Forte Agent 1.8/32.548
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
: On Wed, 27 Jun 2001 12:10:48 +0100, John Toon wrote:
>./setup: error in loading shared libraries:
>/usr/X11R6/lib/libxalflaunch.so.0: ELF file OS ABI invalid.
You somewhere have an LD_PRELOAD variable set for that library. This is a
"busy cursor" library and it is popular with Gnome.
A truss / strace won't help you either, as "ELF file OS ABI invalid" is a
problem signalled by the kernel / dynamic linker - brandelf will tell you
more.
Suggestion: Simply get rid of that LD_PRELOAD.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 10: 6:39 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85])
by hub.freebsd.org (Postfix) with ESMTP
id 1139537B401; Wed, 27 Jun 2001 10:06:36 -0700 (PDT)
(envelope-from tlambert2@mindspring.com)
Received: from mindspring.com (dialup-209.245.141.189.Dial1.SanJose1.Level3.net [209.245.141.189])
by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id KAA01047;
Wed, 27 Jun 2001 10:06:34 -0700 (PDT)
Message-ID: <3B3A12BB.30EB8D80@mindspring.com>
Date: Wed, 27 Jun 2001 10:07:07 -0700
From: Terry Lambert <tlambert2@mindspring.com>
Reply-To: tlambert2@mindspring.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: 3d@FreeBSD.ORG
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: swapping bytes, fpos_t
References: <20010626130659.400C437B405@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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Marc van Woerkom wrote:
>
> Hi,
>
> while porting the ogle dvd player I faced the
> problem of needing fast byte swap routines for
> 16, 32 and 64 bit words.
>
> After grepping through the -CURRENT sources
> I came up with at least three different
> assembler implementations.
The networking implementations tend to be fastest,
and are clever.
On certain architectures (e.g. Transputer, which has a
barrel shifter), the assembly versions are going to be
faster, even at the cost of a function call overhead,
which the macro versions don't have.
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 10:11: 7 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp.bmi.net (smtp.bmi.net [204.57.191.31])
by hub.freebsd.org (Postfix) with ESMTP id 624B237B401
for <freebsd-hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 10:11:04 -0700 (PDT)
(envelope-from jmcoopr@webmail.bmi.net)
Received: from smtp.bmi.net (dsl-154.bmi.net [207.173.60.230])
by smtp.bmi.net (Pro-8.9.3/Pro-8.9.3) with SMTP id KAA17542;
Wed, 27 Jun 2001 10:10:57 -0700
Date: Wed, 27 Jun 2001 10:10:59 -0700
From: John Merryweather Cooper <jmcoopr@webmail.bmi.net>
To: Stefan Hoffmeister <freebsd-ml@econos.de>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Linux Emulation Problems
Message-ID: <20010627101059.G30605@johncoop>
References: <3B39BF38.4050405@btinternet.com> <j34kjt86lg84ar6sbundrtop0db34p568s@4ax.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
In-Reply-To: <j34kjt86lg84ar6sbundrtop0db34p568s@4ax.com>; from freebsd-ml@econos.de on Wed, Jun 27, 2001 at 10:00:59 -0700
X-Mailer: Balsa 1.1.4
Lines: 22
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On 2001.06.27 10:00 Stefan Hoffmeister wrote:
> : On Wed, 27 Jun 2001 12:10:48 +0100, John Toon wrote:
>
> >./setup: error in loading shared libraries:
> >/usr/X11R6/lib/libxalflaunch.so.0: ELF file OS ABI invalid.
>
> You somewhere have an LD_PRELOAD variable set for that library. This
> is a
> "busy cursor" library and it is popular with Gnome.
>
> A truss / strace won't help you either, as "ELF file OS ABI invalid"
> is a
> problem signalled by the kernel / dynamic linker - brandelf will tell
> you
> more.
>
> Suggestion: Simply get rid of that LD_PRELOAD.
>
Where am I likely to find it? I have a stock Gnome-1.4 setup--I
certainly didn't put LD_PRELOAD in . . . :)
jmc
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 10:15:48 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18])
by hub.freebsd.org (Postfix) with ESMTP id ED06237B401
for <hackers@FreeBSD.org>; Wed, 27 Jun 2001 10:15:39 -0700 (PDT)
(envelope-from brian@Awfulhak.org)
Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12])
by Awfulhak.org (8.11.4/8.11.4) with ESMTP id f5RHFxG20579;
Wed, 27 Jun 2001 18:15:59 +0100 (BST)
(envelope-from brian@lan.Awfulhak.org)
Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1])
by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f5RHFwV56441;
Wed, 27 Jun 2001 13:15:58 -0400 (EDT)
(envelope-from brian@hak.lan.Awfulhak.org)
Message-Id: <200106271715.f5RHFwV56441@hak.lan.Awfulhak.org>
X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4
To: Brooks Davis <brooks@one-eyed-alien.net>
Cc: hackers@FreeBSD.org, brian@Awfulhak.org
Subject: Re: rman wildcard question
In-Reply-To: Message from Brooks Davis <brooks@one-eyed-alien.net>
of "Tue, 26 Jun 2001 14:55:46 PDT." <20010626145546.B7909@Odin.AC.HMC.Edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 27 Jun 2001 13:15:58 -0400
From: Brian Somers <brian@Awfulhak.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> In the gif interface cloning code I used the resource management code
> like Brian did in the tun cloning code to manage unit numbers. When the
> user requests an arbitrary unit, they get the first one available, but
> I'm not convinced that's what we want because that has the potential to
> interfere with static configurations with temporary holes in them. It
> seems that a more logical policy would be to allocate the largest
> available unit, but rman_reserve_resource doesn't seem to allow that.
> Is there a way to do this that I'm just not seeing?
Not with rman AFAIK.
Bear in mind though, starting with 0x7fff as an interface unit number
will look pretty ugly when you ifconfig -a....
> -- Brooks
--
Brian <brian@freebsd-services.com> <brian@Awfulhak.org>
http://www.freebsd-services.com/ <brian@[uk.]FreeBSD.org>
Don't _EVER_ lose your sense of humour ! <brian@[uk.]OpenBSD.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 10:53:12 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22])
by hub.freebsd.org (Postfix) with ESMTP id 37DA237B407
for <freebsd-hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 10:53:09 -0700 (PDT)
(envelope-from tlambert2@mindspring.com)
Received: from mindspring.com (dialup-209.245.141.189.Dial1.SanJose1.Level3.net [209.245.141.189])
by hawk.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id KAA07563;
Wed, 27 Jun 2001 10:52:58 -0700 (PDT)
Message-ID: <3B3A1D94.5895DCD0@mindspring.com>
Date: Wed, 27 Jun 2001 10:53:24 -0700
From: Terry Lambert <tlambert2@mindspring.com>
Reply-To: tlambert2@mindspring.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Eugene L. Vorokov" <vel@bugz.infotecs.ru>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: accessing files from kld module
References: <200106271617.f5RGH0243541@bugz.infotecs.ru>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
"Eugene L. Vorokov" wrote:
> probably this question was asked here many times before,
> but I'm new to kernel mode hacks ... Is it somehow possible
> to access files from my kld module ? I have seen functions
> like printf(), MALLOC() for kernel mode, but nothing like
> open() ... using open() syscall directly seems impossible
> too because generally I don't have struct proc entry.
>
> I would be very thankful for any information regarding this issue.
Kernel file handling in FreeBSD is significantly inferior
to that of many other operating systems; notably, AIX has
vastly superior file handling, which can be used from its
kernel threads, etc. (AIX has the best I've seen).
For FreeBSD, you can do file handling, with some effort;
the main problem is that vnode pointer references are not
considered "opens" by the resource tracking system (as
they are in SVR4 and Solaris and several other SVR3/SVR4
derived OS's).
The place you want to look is:
/sys/kern/vfs_vnops.c
I/O is tricky; if you are reading/writing to a buffer in
kernel space, you have to use the combined vn_rdwr()
routine. Make sure you set segflg to UIO_SYSSPACE. This
really is easier than direct calls to VOP_WRITE(), or
trying to allocate and manage fp's without a real process,
and calling vn_read() or vn_write(), which, contrary to
their names, do not operate on vnodes, they operate on fp's.
You won't be able to use ioctl(), poll(), kqfilter(), etc.,
without at least consing up a fake fp, and since the parts
used vary, you'd be better off with a real one.
Good luck.
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 11:58:37 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45])
by hub.freebsd.org (Postfix) with ESMTP
id 1796237B407; Wed, 27 Jun 2001 11:58:33 -0700 (PDT)
(envelope-from scanner@jurai.net)
Received: from localhost (scanner@localhost)
by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id OAA96556;
Wed, 27 Jun 2001 14:58:26 -0400 (EDT)
Date: Wed, 27 Jun 2001 14:58:25 -0400 (EDT)
From: <scanner@jurai.net>
To: "Michael C . Wu" <keichii@iteration.net>
Cc: daniel lawrence <danny@AlphaZed.com>, obrien@FreeBSD.ORG,
jhb@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: Re: HP9000/L1000
In-Reply-To: <20010627095650.B39552@peorth.iteration.net>
Message-ID: <Pine.BSF.4.21.0106271447400.96113-100000@sasami.jurai.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Wed, 27 Jun 2001, Michael C . Wu wrote:
> On Wed, Jun 27, 2001 at 03:10:38PM +0100, daniel lawrence scribbled:
> | This is probably a long shot, but I'll ask anyway. We have 3 HP9000/L1000
> | machines which we may be able to make available (serial console and network)
> | for some kind of BSD porting project.
> You should probably contact David O'Brien or John Baldwin @WindRiver
> about this. obrien@freebsd.org and jhb@freebsd.org.
Actually, if anyone does take this up, I have a K class HP9000 sitting
here at TWA stuffed in a rack not being used at all for anything. It's not
even plugged in. I could ask my boss if we could loan it out or what kind
of access we can offer to it if anyone does get a wild notion to try a
port. 240Mhz PA-RISC 8200 CPU, 4GB of RAM, 18GB of disk :-) would make a
fast devel server :) Although im not sure how popular a PA-RISC port would
be. I'd much rather see ultrasparc support so I can get rid of that horrid
thing Sun sells called Solaris.
=============================================================================
-Chris Watson (816) 464-7780 | Sr. Unix Administrator
Work: chris.watson@twa.com | Trans World Airlines, Kansas City, MO
Home: scanner@jurai.net | http://www.twa.com
=============================================================================
WINDOWS: "Where do you want to go today?"
LINUX: "Where do you want to go tomorrow?"
BSD: "Are you guys coming or what?"
=============================================================================
irc.openprojects.net #FreeBSD -Join the revolution!
ICQ: 20016186
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 17:20: 6 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from server.soekris.com (soekris.com [216.15.61.44])
by hub.freebsd.org (Postfix) with ESMTP id 500AD37B401
for <hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 17:20:03 -0700 (PDT)
(envelope-from soren@soekris.com)
Received: from soekris.com (soren.soekris.com [192.168.1.4])
by server.soekris.com (8.9.2/8.9.2) with ESMTP id RAA62759;
Wed, 27 Jun 2001 17:19:55 -0700 (PDT)
(envelope-from soren@soekris.com)
Message-ID: <3B3A7823.337CA425@soekris.com>
Date: Wed, 27 Jun 2001 17:19:47 -0700
From: Soren Kristensen <soren@soekris.com>
Organization: Soekris Engineering
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Bsdguru@aol.com
Cc: hackers@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
References: <107.1bc2228.2868aa7a@aol.com>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Bsdguru@aol.com wrote:
>
> In a message dated 06/24/2001 2:53:32 PM Eastern Daylight Time,
> soren@soekris.com writes:
>
> > And btw, hardware beats software anytime. The fastest PC processor right
> > now is about the same speed as the slowest hardware.
>
> what are the numbers? Are you accounting for the overhead in accessing the
> hardware? the impact of the stop-and-wait requirements for hardware
> processing? What about bus availability in a heavily utilized router? You are
> going to double the bus requirement.
I'm not claiming any specific numbers, just that the chip I'm using, the
lowest end hi/fn 7951, is said to be faster than your typical highend
>1Ghz CPU doing 3-DES.
> Most people take a rather trivial approach to such evaluations, and i suppose
> im concerned about anyone who thinks that hardware is "always faster" than
> software, because that argument is blatently wrong. a 33Mhz ASIC will not
> always be faster than the host, particularly with transfer and setup
> requirements. It has to be 3-5 times faster than the host just to break even.
I'm only talking about this specific case of doing computing intensive
encryption.... As a hardware designer, I'm very well aware of all the
different bottlenecks.
Regards,
Soren
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 17:20:14 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75])
by hub.freebsd.org (Postfix) with ESMTP id 31F4937B426
for <hackers@FreeBSD.org>; Wed, 27 Jun 2001 17:20:10 -0700 (PDT)
(envelope-from brdavis@odin.ac.hmc.edu)
Received: (from brdavis@localhost)
by odin.ac.hmc.edu (8.11.0/8.11.0) id f5S0K0602642;
Wed, 27 Jun 2001 17:20:00 -0700
Date: Wed, 27 Jun 2001 17:20:00 -0700
From: Brooks Davis <brooks@one-eyed-alien.net>
To: Brian Somers <brian@Awfulhak.org>
Cc: hackers@FreeBSD.org
Subject: Re: rman wildcard question
Message-ID: <20010627172000.D30006@Odin.AC.HMC.Edu>
References: <brooks@one-eyed-alien.net> <200106271715.f5RHFwV56441@hak.lan.Awfulhak.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="ylS2wUBXLOxYXZFQ"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200106271715.f5RHFwV56441@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Wed, Jun 27, 2001 at 01:15:58PM -0400
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
--ylS2wUBXLOxYXZFQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Jun 27, 2001 at 01:15:58PM -0400, Brian Somers wrote:
> Bear in mind though, starting with 0x7fff as an interface unit number=20
> will look pretty ugly when you ifconfig -a....
The other idea I had as to define some sort of "first wildcard unit"
value to pass instead of 0 as the start of the rman call. I'd probably
put it under net.link and suggest that clone implementers use it (I
can't see any point in making it a per interface type value.) As the
other interface clone implementer, what do you think?
-- 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
--ylS2wUBXLOxYXZFQ
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7OngvXY6L6fI4GtQRApU0AJ9+NN0VO23qxYKhWKAD2KCmr7pdIwCeMH7h
1a3m4tDWm6i9RhCfEwbKJ70=
=6YmA
-----END PGP SIGNATURE-----
--ylS2wUBXLOxYXZFQ--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 18:29:18 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138])
by hub.freebsd.org (Postfix) with ESMTP
id 25D0B37B403; Wed, 27 Jun 2001 18:29:16 -0700 (PDT)
(envelope-from dima@unixfreak.org)
Received: from hornet.unixfreak.org (hornet [63.198.170.140])
by bazooka.unixfreak.org (Postfix) with ESMTP
id D2E1A3E2F; Wed, 27 Jun 2001 18:29:15 -0700 (PDT)
To: hackers@FreeBSD.org, ru@FreeBSD.org
Subject: Re: ifmcstat(8) setgidness
In-Reply-To: <20010627120513.B14399@sunbay.com>; from ru@FreeBSD.org on "Wed, 27 Jun 2001 12:05:13 +0300"
Date: Wed, 27 Jun 2001 18:29:15 -0700
From: Dima Dorfman <dima@unixfreak.org>
Message-Id: <20010628012915.D2E1A3E2F@bazooka.unixfreak.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Ruslan Ermilov <ru@FreeBSD.org> writes:
> On Wed, Jun 27, 2001 at 01:29:28AM -0700, Dima Dorfman wrote:
> > Ruslan Ermilov <ru@FreeBSD.ORG> writes:
> > > On Tue, Jun 26, 2001 at 03:04:07PM -0700, Dima Dorfman wrote:
> > > > Hi folks,
> > > >
> > > > Is there a particular reason, other than the desire for more setgid
> > > > programs, that ifmcstat(8) is setgid kmem? It seems that there's no
> > > > reason anyone but root would want to use it, anyway. OpenBSD and
> > > > NetBSD already nuked its setgid bit; any reason why we shouldn't
> > > > follow suit?
> > > >
> > > $ ifmcstat
> > > kvm_openfiles: Permission denied
> >
> > I don't follow. Yes, it needs access to kmem to work. However, I
> > don't see why anyone other than root would need to run it, so why is
> > it setgid? root can access kmem either way.
> >
> Could you please elaborate on why it should be restricted to root only?
Because it looks like it doesn't provide any information that anyone
other than the administrator would find useful (if I'm seeing things,
please let me know), and the less setgid programs in the system the
better our overworked security officer(s) sleep at night :-).
> OpenBSD's and NetBSD's commitlogs are too terse.
This is quite an understatement!
Dima Dorfman
dima@unixfreak.org
>
>
> Cheers,
> --
> Ruslan Ermilov Oracle Developer/DBA,
> ru@sunbay.com Sunbay Software AG,
> ru@FreeBSD.org FreeBSD committer,
> +380.652.512.251 Simferopol, Ukraine
>
> http://www.FreeBSD.org The Power To Serve
> http://www.oracle.com Enabling The Information Age
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 19:34:23 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18])
by hub.freebsd.org (Postfix) with ESMTP id 56F7A37B411
for <freebsd-hackers@freebsd.org>; Wed, 27 Jun 2001 19:34:18 -0700 (PDT)
(envelope-from zzhang@cs.binghamton.edu)
Received: from opal (cs.binghamton.edu [128.226.123.101])
by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f5S2YHU22478
for <freebsd-hackers@freebsd.org>; Wed, 27 Jun 2001 22:34:17 -0400 (EDT)
Date: Wed, 27 Jun 2001 22:34:16 -0400 (EDT)
From: Zhihui Zhang <zzhang@cs.binghamton.edu>
X-Sender: zzhang@opal
To: freebsd-hackers@freebsd.org
Subject: trace a library call
Message-ID: <Pine.SOL.4.21.0106272231010.22637-100000@opal>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Suppose I write a program that calls sbrk(). How can I trace into the
function sbrk()? In this particular case, I want to know whether
sbrk() calls the function in file lib/libstand/sbrk.c or sys/sbrk.S.
Sometimes it is nice to see what system call is eventually called as well.
I know dynamic linking may make this hard. But is there a way to do
this? Thanks.
-Zhihui
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 19:40:59 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from web10705.mail.yahoo.com (web10705.mail.yahoo.com [216.136.130.213])
by hub.freebsd.org (Postfix) with SMTP id 1ADFA37B401
for <hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 19:40:57 -0700 (PDT)
(envelope-from bhatt_manas@yahoo.com)
Message-ID: <20010628024057.71824.qmail@web10705.mail.yahoo.com>
Received: from [203.200.52.16] by web10705.mail.yahoo.com; Wed, 27 Jun 2001 19:40:57 PDT
Date: Wed, 27 Jun 2001 19:40:57 -0700 (PDT)
From: Manas Bhatt <bhatt_manas@yahoo.com>
Subject: does data overflow in pipes
To: hackers@FreeBSD.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
hi all,
pipes uses only direct blocks to store data. so
depending on the blocksize , a total data of
10*blocksize can be written in one go but what happens
if a writer process tries to write more 10*blocksize
of data in one go. Does the kernel overwrites the
data in pipe or not ? if yes, why? if not, then how
does it allow the writer to write more 10*blocksize of
data?
if someone can direct me to implementation
(source files), it would be great.
thanks
--manas
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 19:46:17 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18])
by hub.freebsd.org (Postfix) with ESMTP id 7E0F937B401
for <hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 19:46:14 -0700 (PDT)
(envelope-from zzhang@cs.binghamton.edu)
Received: from opal (cs.binghamton.edu [128.226.123.101])
by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f5S2jMU25391;
Wed, 27 Jun 2001 22:45:22 -0400 (EDT)
Date: Wed, 27 Jun 2001 22:45:21 -0400 (EDT)
From: Zhihui Zhang <zzhang@cs.binghamton.edu>
X-Sender: zzhang@opal
To: Manas Bhatt <bhatt_manas@yahoo.com>
Cc: hackers@FreeBSD.ORG
Subject: Re: does data overflow in pipes
In-Reply-To: <20010628024057.71824.qmail@web10705.mail.yahoo.com>
Message-ID: <Pine.SOL.4.21.0106272244150.23062-100000@opal>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
I guess the kernel will block the process trying to write more data than
that can be accommodated. Or if you are using non-blocking I/O, it will
return an error.
-Zhihui
On Wed, 27 Jun 2001, Manas Bhatt wrote:
> hi all,
> pipes uses only direct blocks to store data. so
> depending on the blocksize , a total data of
> 10*blocksize can be written in one go but what happens
> if a writer process tries to write more 10*blocksize
> of data in one go. Does the kernel overwrites the
> data in pipe or not ? if yes, why? if not, then how
> does it allow the writer to write more 10*blocksize of
> data?
> if someone can direct me to implementation
> (source files), it would be great.
> thanks
> --manas
>
> __________________________________________________
> Do You Yahoo!?
> Get personalized email addresses from Yahoo! Mail
> http://personal.mail.yahoo.com/
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 19:51:51 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from guru.mired.org (okc-27-141-144.mmcable.com [24.27.141.144])
by hub.freebsd.org (Postfix) with SMTP id 4C37137B401
for <hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 19:51:48 -0700 (PDT)
(envelope-from mwm@mired.org)
Received: (qmail 11070 invoked by uid 100); 28 Jun 2001 02:51:47 -0000
From: Mike Meyer <mwm@mired.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15162.39875.353224.757884@guru.mired.org>
Date: Wed, 27 Jun 2001 21:51:47 -0500
To: Soren Kristensen <soren@soekris.com>
Cc: hackers@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
In-Reply-To: <3B3A7823.337CA425@soekris.com>
References: <107.1bc2228.2868aa7a@aol.com>
<3B3A7823.337CA425@soekris.com>
X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid
X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG%
*h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Soren Kristensen <soren@soekris.com> types:
> I'm not claiming any specific numbers, just that the chip I'm using, the
> lowest end hi/fn 7951, is said to be faster than your typical highend
> >1Ghz CPU doing 3-DES.
[ ... ]
> I'm only talking about this specific case of doing computing intensive
> encryption.... As a hardware designer, I'm very well aware of all the
> different bottlenecks.
The crucial bottleneck for this kind of thing is the doubling
time. Unless your special purpose hardware doubles in speed as fast or
faster than general purpose CPUs, then eventually it's going to be
slow, then expensive, and finally dead. Given the two doubling times
and current relative speed, you can easily predict when general
purpose CPUs well be faster and then when they will be more cost
effective. At that point, your special purpose hardware is dead, and
just waiting for the rest of the world to realize it.
Given the predicted lifetime, you can make a rational decision about
whether it's worth the effort to support the hardware.
<mike
--
Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 20: 5:38 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from server.soekris.com (soekris.com [216.15.61.44])
by hub.freebsd.org (Postfix) with ESMTP id 1475737B401
for <hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 20:05:34 -0700 (PDT)
(envelope-from soren@soekris.com)
Received: from soekris.com (soren.soekris.com [192.168.1.4])
by server.soekris.com (8.9.2/8.9.2) with ESMTP id UAA63174;
Wed, 27 Jun 2001 20:05:40 -0700 (PDT)
(envelope-from soren@soekris.com)
Message-ID: <3B3A9EFA.E65C2DC8@soekris.com>
Date: Wed, 27 Jun 2001 20:05:30 -0700
From: Soren Kristensen <soren@soekris.com>
Organization: Soekris Engineering
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mike Meyer <mwm@mired.org>
Cc: hackers@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
References: <107.1bc2228.2868aa7a@aol.com>
<3B3A7823.337CA425@soekris.com> <15162.39875.353224.757884@guru.mired.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi,
That's not really the point here, I was talking about lowest end
hardware compared to high end CPU. If we compare with high end hardware,
then we're talking about factor >50 faster than software.... There are
chips out that can do >1Gbit 3-DES, given a 64bit/66Mhz PCI bus.
I'm just starting with a low end chip to complement my 133 Mhz 486 based
net4501 board, with the goal of low cost and low power, not absolute
performance.
Soren
Mike Meyer wrote:
>
> Soren Kristensen <soren@soekris.com> types:
> > I'm not claiming any specific numbers, just that the chip I'm using, the
> > lowest end hi/fn 7951, is said to be faster than your typical highend
> > >1Ghz CPU doing 3-DES.
> [ ... ]
> > I'm only talking about this specific case of doing computing intensive
> > encryption.... As a hardware designer, I'm very well aware of all the
> > different bottlenecks.
>
> The crucial bottleneck for this kind of thing is the doubling
> time. Unless your special purpose hardware doubles in speed as fast or
> faster than general purpose CPUs, then eventually it's going to be
> slow, then expensive, and finally dead. Given the two doubling times
> and current relative speed, you can easily predict when general
> purpose CPUs well be faster and then when they will be more cost
> effective. At that point, your special purpose hardware is dead, and
> just waiting for the rest of the world to realize it.
>
> Given the predicted lifetime, you can make a rational decision about
> whether it's worth the effort to support the hardware.
>
> <mike
> --
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 20:20: 0 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254])
by hub.freebsd.org (Postfix) with ESMTP id 076CE37B403
for <hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 20:19:57 -0700 (PDT)
(envelope-from steve@virtual-voodoo.com)
Received: (from steve@localhost)
by virtual-voodoo.com (8.11.4/8.11.4) id f5S3JjO86381;
Wed, 27 Jun 2001 22:19:45 -0500 (EST)
(envelope-from steve)
Date: Wed, 27 Jun 2001 22:19:45 -0500
From: Steve Ames <steve@virtual-voodoo.com>
To: Mike Meyer <mwm@mired.org>
Cc: Soren Kristensen <soren@soekris.com>, hackers@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
Message-ID: <20010627221945.B92559@virtual-voodoo.com>
References: <107.1bc2228.2868aa7a@aol.com> <3B3A7823.337CA425@soekris.com> <15162.39875.353224.757884@guru.mired.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <15162.39875.353224.757884@guru.mired.org>; from mwm@mired.org on Wed, Jun 27, 2001 at 09:51:47PM -0500
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Wed, Jun 27, 2001 at 09:51:47PM -0500, Mike Meyer wrote:
> The crucial bottleneck for this kind of thing is the doubling
> time. Unless your special purpose hardware doubles in speed as fast or
> faster than general purpose CPUs, then eventually it's going to be
> slow, then expensive, and finally dead. Given the two doubling times
> and current relative speed, you can easily predict when general
> purpose CPUs well be faster and then when they will be more cost
> effective. At that point, your special purpose hardware is dead, and
> just waiting for the rest of the world to realize it.
>
> Given the predicted lifetime, you can make a rational decision about
> whether it's worth the effort to support the hardware.
Can't you also make the assumption that hardware vendors will
be upgrading their product with equal vigor? Supporting hardware
now (when its faster than CPU) will make it much easier to support
it later (when its still faster than CPU).
-Steve
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 20:33:33 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from guru.mired.org (okc-27-141-144.mmcable.com [24.27.141.144])
by hub.freebsd.org (Postfix) with SMTP id 6A15637B403
for <hackers@FreeBSD.ORG>; Wed, 27 Jun 2001 20:33:23 -0700 (PDT)
(envelope-from mwm@mired.org)
Received: (qmail 12068 invoked by uid 100); 28 Jun 2001 03:33:22 -0000
From: Mike Meyer <mwm@mired.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15162.42370.469003.143882@guru.mired.org>
Date: Wed, 27 Jun 2001 22:33:22 -0500
To: Steve Ames <steve@virtual-voodoo.com>,
Soren Kristensen <soren@soekris.com>
Cc: hackers@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
In-Reply-To: <20010627221945.B92559@virtual-voodoo.com>
References: <107.1bc2228.2868aa7a@aol.com>
<3B3A7823.337CA425@soekris.com>
<15162.39875.353224.757884@guru.mired.org>
<3B3A9EFA.E65C2DC8@soekris.com>
<20010627221945.B92559@virtual-voodoo.com>
X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid
X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG%
*h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Steve Ames <steve@virtual-voodoo.com> types:
> On Wed, Jun 27, 2001 at 09:51:47PM -0500, Mike Meyer wrote:
> > The crucial bottleneck for this kind of thing is the doubling
> > time. Unless your special purpose hardware doubles in speed as fast or
> > faster than general purpose CPUs, then eventually it's going to be
> > slow, then expensive, and finally dead. Given the two doubling times
> > and current relative speed, you can easily predict when general
> > purpose CPUs well be faster and then when they will be more cost
> > effective. At that point, your special purpose hardware is dead, and
> > just waiting for the rest of the world to realize it.
> >
> > Given the predicted lifetime, you can make a rational decision about
> > whether it's worth the effort to support the hardware.
>
> Can't you also make the assumption that hardware vendors will
> be upgrading their product with equal vigor? Supporting hardware
> now (when its faster than CPU) will make it much easier to support
> it later (when its still faster than CPU).
Actually, I *did* assume that. The question isn't about vigor, it's
about results. That's why you need to know how fast the hardware
vendors can double the speed of their product, so you can predict the
points where software overtakes it and then becomes more cost
effective - or demonstrate that that isn't going to happen.
Past experience - LISP and Forth Machines, the Amiga graphics
hardware, etc. - indicate that special purpose hardware doesn't get
faster as fast as general purpose cpus. There's apparently more money
to be made in making general purpose CPUs faster than in making
special purpose hardware faster, so they throw more resources at it.
Soren Kristensen <soren@soekris.com> types:
> That's not really the point here, I was talking about lowest end
> hardware compared to high end CPU. If we compare with high end hardware,
> then we're talking about factor >50 faster than software.... There are
> chips out that can do >1Gbit 3-DES, given a 64bit/66Mhz PCI bus.
>
> I'm just starting with a low end chip to complement my 133 Mhz 486 based
> net4501 board, with the goal of low cost and low power, not absolute
> performance.
Replies below the quote if you want to keep context.
Low end, high end, and current relative speed are immaterial. If the
doubling time for your special purpose hardware isn't as good as that
for general purpose cpus, then it's a dead end. If you're planning a
product around it - or are deciding whether or not to support it -
then you need to take that into account.
This doesn't mean the product is useless; it just means you need to
plan on dealing with it being outpaced by general purpose CPUs at some
point.
<mike
--
Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 21:23: 7 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from softweyr.com (softweyr.com [208.247.99.111])
by hub.freebsd.org (Postfix) with ESMTP id 6F9E637B401
for <hackers@freebsd.org>; Wed, 27 Jun 2001 21:23:03 -0700 (PDT)
(envelope-from wes@softweyr.com)
Received: from localhost.softweyr.com
([127.0.0.1] helo=softweyr.com ident=ed846da409878a0935f5402cf8a62183)
by softweyr.com with esmtp (Exim 3.16 #1)
id 15FTON-00008K-00; Wed, 27 Jun 2001 22:27:00 -0600
Message-ID: <3B3AB213.ADBB0BF9@softweyr.com>
Date: Wed, 27 Jun 2001 22:26:59 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Rik van Riel <riel@conectiva.com.br>
Cc: Rahul Siddharthan <rsidd@physics.iisc.ernet.in>,
hackers@FreeBSD.ORG
Subject: Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
References: <Pine.LNX.4.21.0106261106450.7419-100000@imladris.rielhome.conectiva>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Rik van Riel wrote:
>
> On Tue, 26 Jun 2001, Wes Peters wrote:
> > Rik van Riel wrote:
> > > On Sun, 24 Jun 2001, Rahul Siddharthan wrote:
> > > > Wes Peters said on Jun 23, 2001 at 23:28:42:
> > > > > > Plenty of GNU stuff there, though it doesn't say so explicitly.
> > > > > > Of course, they say it's all meant only for "legacy Unix" stuff.
> > > > >
> > > > > Can you substantiate your claim there is "plenty of GNU stuff" in
> > > > > Interix, or are you just talking out your ass as usual?
> > >
> > > gcc, gdb, bash, gnu emacs and a bunch more.
> >
> > Out of several hundred utilities?
>
> [snip troll]
>
> > </taunt weenies=Linux>
>
> I hope you're having fun receiving flames from more
> impressionable people ;)
>
> Personally I don't care much about BSD vs. GPL and am
> annoyed by Microsoft's hypocricy (sp?). The fact that
> they're using open source software is great.
That was the point I was trying to make. Rather than be annoyed by this,
it should be splashed across /., lwn, etc. But I'm not gonna do it.
Maybe ESR will if you tell him.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
wes@softweyr.com http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 21:34:54 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from softweyr.com (softweyr.com [208.247.99.111])
by hub.freebsd.org (Postfix) with ESMTP
id B242C37B401; Wed, 27 Jun 2001 21:34:49 -0700 (PDT)
(envelope-from wes@softweyr.com)
Received: from localhost.softweyr.com
([127.0.0.1] helo=softweyr.com ident=b83b0451914e861ceb0e64216a91711c)
by softweyr.com with esmtp (Exim 3.16 #1)
id 15FTaK-000099-00; Wed, 27 Jun 2001 22:39:20 -0600
Message-ID: <3B3AB4F8.184A2EFE@softweyr.com>
Date: Wed, 27 Jun 2001 22:39:20 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Ruslan Ermilov <ru@FreeBSD.org>
Cc: Deepak Jain <deepak@ai.net>, net@FreeBSD.org, hackers@FreeBSD.org
Subject: Re: fastforwarding?
References: <GPEOJKGHAMKFIOMAGMDICEOJDGAA.deepak@ai.net> <20010626093545.D49992@sunbay.com>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Ruslan Ermilov wrote:
>
> On Mon, Jun 25, 2001 at 06:47:41PM -0400, Deepak Jain wrote:
> > sysctl -A |grep forward
> > net.inet.ip.forwarding: 1
> > net.inet.ip.fastforwarding: 0
> > machdep.forward_irq_enabled: 1
> > machdep.forward_signal_enabled: 1
> > machdep.forward_roundrobin_enabled: 1
> >
> > What does the fastforwarding option do that the normal forwarding option
> > doesn't?
> >
> See inet(4).
The description there isn't very forthcoming. fastforwarding caches
the results of a route lookup for destination addresses that are not
on the local machine, and uses the cached route to short-circuit the
normal (relatively slow) route lookup process. The packet flows
directly from one layer2 input routine directly to the opposing
layer2 output routine without traversing the IP layer.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
wes@softweyr.com http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Wed Jun 27 22:51:18 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
by hub.freebsd.org (Postfix) with ESMTP
id 2297437B405; Wed, 27 Jun 2001 22:51:15 -0700 (PDT)
(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1])
by harmony.village.org (8.11.3/8.11.1) with ESMTP id f5S5p8U99943;
Wed, 27 Jun 2001 23:51:08 -0600 (MDT)
(envelope-from imp@harmony.village.org)
Message-Id: <200106280551.f5S5p8U99943@harmony.village.org>
To: Dima Dorfman <dima@unixfreak.org>
Subject: Re: "include" directive in config(8) (was: Two Junior Kernel Hacker tasks..)
Cc: John Baldwin <jhb@FreeBSD.ORG>, hackers@FreeBSD.ORG,
peter@FreeBSD.ORG
In-reply-to: Your message of "Sun, 24 Jun 2001 13:41:13 PDT."
<20010624204114.F2B913E28@bazooka.unixfreak.org>
References: <20010624204114.F2B913E28@bazooka.unixfreak.org>
Date: Wed, 27 Jun 2001 23:51:08 -0600
From: Warner Losh <imp@harmony.village.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In message <20010624204114.F2B913E28@bazooka.unixfreak.org> Dima Dorfman writes:
: I thought about this, too. Right now there isn't a way to do that,
: and neither OpenBSD nor NetBSD have one AFAIK. That said, I think it
: would be trivial to implement. The list of options and devices is a
: simple linked list (mind you, it's a home-grown one, not queue(3)); it
: shouldn't be too hard to implement "unoption" and "undevice"
: directives.
I could have sworn that NetBSD and/or OpenBSD had this feature. But
if they do, I've been unable to find it in my searches. Maybe they
just talked about it.
Go forward with include after usenix. I've seen less objection to it
than my $MACHINE/compile proposal (so far two against: obrien who
wants it compile/$MACHINE and bde who wants something too weird for me
to understand).
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 0:36:29 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mailout02.sul.t-online.de (mailout02.sul.t-online.com [194.25.134.17])
by hub.freebsd.org (Postfix) with ESMTP id 18C4137B403
for <hackers@freebsd.org>; Thu, 28 Jun 2001 00:36:22 -0700 (PDT)
(envelope-from hm@kts.org)
Received: from fwd02.sul.t-online.de
by mailout02.sul.t-online.de with smtp
id 15FWLa-0004b9-04; Thu, 28 Jun 2001 09:36:18 +0200
Received: from ernie.kts.org (520021727764-0001@[217.80.9.122]) by fmrl02.sul.t-online.com
with esmtp id 15FWLK-1gLmgyC; Thu, 28 Jun 2001 09:36:02 +0200
Received: from bert.kts.org (bert.kts.org [194.55.156.2])
by ernie.kts.org (Postfix) with ESMTP
id E462952A87; Thu, 28 Jun 2001 09:36:00 +0200 (CEST)
Received: by bert.kts.org (Postfix, from userid 100)
id C87059B20; Thu, 28 Jun 2001 09:36:35 +0200 (CEST)
Subject: Re: HP9000/L1000
In-Reply-To: <20010627151038.I11787@alphazed.com> from daniel lawrence at "Jun 27, 2001 3:10:38 pm"
To: danny@AlphaZed.com
Date: Thu, 28 Jun 2001 09:36:35 +0200 (CEST)
Cc: hackers@freebsd.org
Organization: Kitchen Table Systems
#Reply-To: hm@kts.org
Reply-To: Hellmuth.Michaelis@t-online.de
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <20010628073635.C87059B20@bert.kts.org>
From: hm@kts.org (Hellmuth Michaelis)
X-Sender: 520021727764-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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
daniel lawrence wrote:
> This is probably a long shot, but I'll ask anyway. We have 3 HP9000/L1000
> machines which we may be able to make available (serial console and network)
> for some kind of BSD porting project.
I'm very interested in having a FreeBSD running on the newer HP9000 server
machines but i think the problem is getting the hardware documentation
from HP (tell me if i'm wrong) for the Series 800 machines. Hardware is
available here, if anyone is working on such a project and likes a helping
hand, please mail.
hellmuth
--
Hellmuth Michaelis hm@kts.org Hamburg, Europe
We all live in a yellow subroutine, yellow subroutine, yellow subroutine ...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 1:47:44 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13])
by hub.freebsd.org (Postfix) with SMTP id 68E8A37B406
for <hackers@FreeBSD.ORG>; Thu, 28 Jun 2001 01:47:41 -0700 (PDT)
(envelope-from roam@orbitel.bg)
Received: (qmail 81224 invoked by uid 1000); 28 Jun 2001 08:52:26 -0000
Date: Thu, 28 Jun 2001 11:52:26 +0300
From: Peter Pentchev <roam@orbitel.bg>
To: Zhihui Zhang <zzhang@cs.binghamton.edu>
Cc: Manas Bhatt <bhatt_manas@yahoo.com>, hackers@FreeBSD.ORG
Subject: Re: does data overflow in pipes
Message-ID: <20010628115226.D80342@ringworld.oblivion.bg>
Mail-Followup-To: Zhihui Zhang <zzhang@cs.binghamton.edu>,
Manas Bhatt <bhatt_manas@yahoo.com>, hackers@FreeBSD.ORG
References: <20010628024057.71824.qmail@web10705.mail.yahoo.com> <Pine.SOL.4.21.0106272244150.23062-100000@opal>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.SOL.4.21.0106272244150.23062-100000@opal>; from zzhang@cs.binghamton.edu on Wed, Jun 27, 2001 at 10:45:21PM -0400
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
It is also possible that it would only write as much as it can,
and return the amount written, leaving it to you to write the rest
later. (Uhm.. you do check the return values from write(2), right? :)
The relevant source is in src/sys/kern/sys_pipe.c, namely the pipe_write()
function. From a quick look, it would seem that writes behave exactly
the way I thought - only writing as much as there is space left in
the pipe buffer.
G'luck,
Peter
--
I am the meaning of this sentence.
On Wed, Jun 27, 2001 at 10:45:21PM -0400, Zhihui Zhang wrote:
>
> I guess the kernel will block the process trying to write more data than
> that can be accommodated. Or if you are using non-blocking I/O, it will
> return an error.
>
> -Zhihui
>
> On Wed, 27 Jun 2001, Manas Bhatt wrote:
>
> > hi all,
> > pipes uses only direct blocks to store data. so
> > depending on the blocksize , a total data of
> > 10*blocksize can be written in one go but what happens
> > if a writer process tries to write more 10*blocksize
> > of data in one go. Does the kernel overwrites the
> > data in pipe or not ? if yes, why? if not, then how
> > does it allow the writer to write more 10*blocksize of
> > data?
> > if someone can direct me to implementation
> > (source files), it would be great.
> > thanks
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 2:25:14 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123])
by hub.freebsd.org (Postfix) with ESMTP id 185F837B40B
for <freebsd-hackers@FreeBSD.ORG>; Thu, 28 Jun 2001 02:25:12 -0700 (PDT)
(envelope-from tlambert2@mindspring.com)
Received: from mindspring.com (dialup-209.244.104.249.Dial1.SanJose1.Level3.net [209.244.104.249])
by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id CAA19271;
Thu, 28 Jun 2001 02:25:09 -0700 (PDT)
Message-ID: <3B3AF816.3E752607@mindspring.com>
Date: Thu, 28 Jun 2001 02:25:42 -0700
From: Terry Lambert <tlambert2@mindspring.com>
Reply-To: tlambert2@mindspring.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Zhihui Zhang <zzhang@cs.binghamton.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: trace a library call
References: <Pine.SOL.4.21.0106272231010.22637-100000@opal>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Zhihui Zhang wrote:
>
> Suppose I write a program that calls sbrk(). How can I trace into the
> function sbrk()? In this particular case, I want to know whether
> sbrk() calls the function in file lib/libstand/sbrk.c or sys/sbrk.S.
> Sometimes it is nice to see what system call is eventually called as well.
> I know dynamic linking may make this hard. But is there a way to do
> this? Thanks.
sbrk() is a system call, not a library call. It has a
stub that just loads a register with the call ID and
does an INT 0x80.
You can't "trace into" it, since you are in a user space
program.
If you want to see how it works, the sources are in /sys;
but all it does is add pages to the end of the address
space, in the heap.
If you are having problems with it, you are probably using
sbrk() and malloc() in the same program. Don't do that;
malloc() traditionally calls sbrk() to get pages, so you
will have the same effect as trying to use fopen() and
open() in the same program: mainly, that fd manipulation
routines can close/open/etc. fd's out from under file
pointers. In the sbrk() case, there can be attempts to
(re)map pages to regions where they don't really belong.
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 4:50:46 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from Exchange2000.com-con.ag (exchange2000.com-con.net [212.6.164.8])
by hub.freebsd.org (Postfix) with ESMTP
id E69D937B406; Thu, 28 Jun 2001 04:50:40 -0700 (PDT)
(envelope-from rh@com-con.net)
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: how to compile bpf...
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Date: Thu, 28 Jun 2001 13:50:33 +0100
Message-ID: <F54B610C5BFDE546BBA2F6CC595ACC75084981@Exchange2000.com-con.ag>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: how to compile bpf...
Thread-Index: AcD/0Os8DzAqcDexTgGN2aRq1P2uNw==
From: "Heimes, Rene" <rh@com-con.net>
To: <freebsd-questions@freebsd.org>, <freebsd-hackers@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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
I =B4m using NeTraMet Vers. 4.3 on an FreeBSD 4.2 System (i386)
with libpcap-04.
NeTraMet uses libpcap for monitoring and get the packets on the LAN.
It could be that ethernet packets were dropped by the kernel and
NeTraMet, which happens when i capture some minutes of the LAN traffic
with tcpdump 3.5 .
Tcpdump gives an information about how many packets were filtered and
how many packet were dropped by the kernel.
NeTraMet doesn=B4t do this.
How could i be on the secure site, that NeTraMet get all packets.
If NeTraMet droppes the packets like tcpdump what can I do.
In the newsforum from NeTraMet someone says to boost the bpf buffer but
he didn=B4t know how.
(the counter it is referring to in /sys/net/bpf.c in the kernel.)
seems to be=20
# define BPF_BUFSIZE 4096
so i have to increase this.
And there for I have to recompile the c-source code, but which of the
source and how.
Where I have to put the binary??
Could you help me or give some hints??=20
Thanks in advance
Ren=E9 Heimes
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 6:13:14 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18])
by hub.freebsd.org (Postfix) with ESMTP id 59CF737B403
for <freebsd-hackers@FreeBSD.ORG>; Thu, 28 Jun 2001 06:13:11 -0700 (PDT)
(envelope-from zzhang@cs.binghamton.edu)
Received: from opal (cs.binghamton.edu [128.226.123.101])
by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f5SDDA500834;
Thu, 28 Jun 2001 09:13:10 -0400 (EDT)
Date: Thu, 28 Jun 2001 09:13:09 -0400 (EDT)
From: Zhihui Zhang <zzhang@cs.binghamton.edu>
X-Sender: zzhang@opal
To: Terry Lambert <tlambert2@mindspring.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: trace a library call
In-Reply-To: <3B3AF816.3E752607@mindspring.com>
Message-ID: <Pine.SOL.4.21.0106280909080.21305-100000@opal>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
sbrk() is not supported in FreeBSD as a system call (see file
vm/vm_mmap.c). However, sbrk(0) can reflect the latest end of the heap. I
am interested in how sbrk() interacts with malloc(). I know my question is
too specific. Thanks for your answer. I did learn a lesson: mixing
abstraction layers is really bad.
-Zhihui
On Thu, 28 Jun 2001, Terry Lambert wrote:
> Zhihui Zhang wrote:
> >
> > Suppose I write a program that calls sbrk(). How can I trace into the
> > function sbrk()? In this particular case, I want to know whether
> > sbrk() calls the function in file lib/libstand/sbrk.c or sys/sbrk.S.
> > Sometimes it is nice to see what system call is eventually called as well.
> > I know dynamic linking may make this hard. But is there a way to do
> > this? Thanks.
>
> sbrk() is a system call, not a library call. It has a
> stub that just loads a register with the call ID and
> does an INT 0x80.
>
> You can't "trace into" it, since you are in a user space
> program.
>
> If you want to see how it works, the sources are in /sys;
> but all it does is add pages to the end of the address
> space, in the heap.
>
> If you are having problems with it, you are probably using
> sbrk() and malloc() in the same program. Don't do that;
> malloc() traditionally calls sbrk() to get pages, so you
> will have the same effect as trying to use fopen() and
> open() in the same program: mainly, that fd manipulation
> routines can close/open/etc. fd's out from under file
> pointers. In the sbrk() case, there can be attempts to
> (re)map pages to regions where they don't really belong.
>
> -- Terry
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 6:41:55 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18])
by hub.freebsd.org (Postfix) with ESMTP id 11BD037B409
for <freebsd-hackers@FreeBSD.ORG>; Thu, 28 Jun 2001 06:41:52 -0700 (PDT)
(envelope-from zzhang@cs.binghamton.edu)
Received: from opal (cs.binghamton.edu [128.226.123.101])
by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f5SDfo516288;
Thu, 28 Jun 2001 09:41:50 -0400 (EDT)
Date: Thu, 28 Jun 2001 09:41:50 -0400 (EDT)
From: Zhihui Zhang <zzhang@cs.binghamton.edu>
X-Sender: zzhang@opal
To: Terry Lambert <tlambert2@mindspring.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: trace a library call
In-Reply-To: <Pine.SOL.4.21.0106280909080.21305-100000@opal>
Message-ID: <Pine.SOL.4.21.0106280938360.22558-100000@opal>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
I am sorry. It turns out when the argument is zero, sbrk() does not enter
into the kernel. If it does, it will return not supported.
-Zhihui
On Thu, 28 Jun 2001, Zhihui Zhang wrote:
>
> sbrk() is not supported in FreeBSD as a system call (see file
> vm/vm_mmap.c). However, sbrk(0) can reflect the latest end of the heap. I
> am interested in how sbrk() interacts with malloc(). I know my question is
> too specific. Thanks for your answer. I did learn a lesson: mixing
> abstraction layers is really bad.
>
> -Zhihui
>
> On Thu, 28 Jun 2001, Terry Lambert wrote:
>
> > Zhihui Zhang wrote:
> > >
> > > Suppose I write a program that calls sbrk(). How can I trace into the
> > > function sbrk()? In this particular case, I want to know whether
> > > sbrk() calls the function in file lib/libstand/sbrk.c or sys/sbrk.S.
> > > Sometimes it is nice to see what system call is eventually called as well.
> > > I know dynamic linking may make this hard. But is there a way to do
> > > this? Thanks.
> >
> > sbrk() is a system call, not a library call. It has a
> > stub that just loads a register with the call ID and
> > does an INT 0x80.
> >
> > You can't "trace into" it, since you are in a user space
> > program.
> >
> > If you want to see how it works, the sources are in /sys;
> > but all it does is add pages to the end of the address
> > space, in the heap.
> >
> > If you are having problems with it, you are probably using
> > sbrk() and malloc() in the same program. Don't do that;
> > malloc() traditionally calls sbrk() to get pages, so you
> > will have the same effect as trying to use fopen() and
> > open() in the same program: mainly, that fd manipulation
> > routines can close/open/etc. fd's out from under file
> > pointers. In the sbrk() case, there can be attempts to
> > (re)map pages to regions where they don't really belong.
> >
> > -- Terry
> >
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 6:45:18 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from euripides.enigma.ie (euripides.enigma.ie [194.106.143.89])
by hub.freebsd.org (Postfix) with ESMTP id 26DDB37B401
for <hackers@freebsd.org>; Thu, 28 Jun 2001 06:45:15 -0700 (PDT)
(envelope-from nick-fbsdhackers@netability.ie)
Received: (qmail 50859 invoked by uid 1009); 28 Jun 2001 13:45:11 -0000
From: "Nick Hilliard" <nick-fbsdhackers@netability.ie>
Date: Thu, 28 Jun 2001 14:45:11 +0100
To: hackers@freebsd.org
Subject: Re: trace a library call
Message-ID: <20010628144511.A50831@euripides.enigma.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Zhihui Zhang wrote:
> sbrk() is not supported in FreeBSD as a system call (see file
> vm/vm_mmap.c).
pancake:/sys> grep -w sbrk /usr/src/sys/kern/syscalls.master
69 STD BSD { int sbrk(int incr); }
If you use malloc() in your program, you shouldn't use sbrk, because doing
so will make the malloc() code lose count of what memory has been added to
the heap. The result of this is that your program will almost certainly
crash due to different memory objects being stored in the same area of
memory.
The version of sbrk in libstand is an emulation of the system call which is
not used for any programs running in multiuser mode (or at least, it
shouln't be, if it is).
Nick
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 8:29:25 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from relay.tecc.co.uk (luggage.tecc.co.uk [193.128.6.129])
by hub.freebsd.org (Postfix) with SMTP id 0D2C237B406
for <hackers@freebsd.org>; Thu, 28 Jun 2001 08:29:23 -0700 (PDT)
(envelope-from andy@tecc.co.uk)
Received: from southampton [195.217.37.155]
by relay.tecc.co.uk with smtp (Exim 1.70 #1)
id 15FdjN-0003WF-00; Thu, 28 Jun 2001 16:29:21 +0100
From: "Andy" <andy@tecc.co.uk>
To: <hackers@FreeBSD.ORG>
Subject: RE: Query: How to tell if Microsoft is using BSD TCP/IP code?
Date: Thu, 28 Jun 2001 16:29:22 +0100
Message-ID: <NDBBKOKIGKLFGGPFHCGBGEOEDDAA.andy@tecc.co.uk>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <3B3AB213.ADBB0BF9@softweyr.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
anyone seen this yet or am I slow as usual?
http://www.oreillynet.com/pub/a/dotnet/2001/06/27/dotnet.html
Ak
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 8:44:52 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22])
by hub.freebsd.org (Postfix) with ESMTP id 9194037B403
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 08:44:48 -0700 (PDT)
(envelope-from vel@bugz.infotecs.ru)
Received: (from vel@localhost)
by bugz.infotecs.ru (8.11.1/8.11.1) id f5SFvue68254
for freebsd-hackers@freebsd.org; Thu, 28 Jun 2001 19:57:56 +0400 (MSD)
(envelope-from vel)
From: "Eugene L. Vorokov" <vel@bugz.infotecs.ru>
Message-Id: <200106281557.f5SFvue68254@bugz.infotecs.ru>
Subject: allocating user space memory from kernel mode
To: freebsd-hackers@freebsd.org
Date: Thu, 28 Jun 2001 19:57:55 +0400 (MSD)
X-Mailer: ELM [version 2.4ME+ PL82 (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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hello,
is it possible to allocate and then maybe free memory in user space
from kernel mode, if I have struct proc of the process that memory should
belong to ? What is the easiest and safest method of doing this ?
I have seen some example that uses obreak(), but that seems very tricky
and suspicious ... I don't really understand what obreak() really does
and how to use it ...
Thanks for the information.
Regards,
Eugene
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 9:25:38 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139])
by hub.freebsd.org (Postfix) with ESMTP id D79C937B407
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 09:25:35 -0700 (PDT)
(envelope-from nsouch@alcove.fr)
Received: from avon.alcove-fr ([10.16.10.3])
by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian))
id 15Febl-0006nb-00
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 18:25:33 +0200
Received: from nsouch by avon.alcove-fr with local (Exim 3.12 #1 (Debian))
id 15Febl-0004ed-00
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 18:25:33 +0200
Date: Thu, 28 Jun 2001 18:25:33 +0200
From: Nicolas Souchu <nsouch@fr.alcove.com>
To: freebsd-hackers@freebsd.org
Subject: processes private data
Message-ID: <20010628182533.B17804@avon.alcove-fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.4i
Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Ecom?=
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi folks,
I have a char driver that must be opened by more than one process. The minor
index is not sufficient for this. Is there any process private data (void *)
in the devfs structure (or the opposite) I could point to with the minor index
of my device?
Nicholas
--
Alcôve Technical Manager - Nicolas.Souchu@fr.alcove.com - http://www.alcove.com
Open Source Software Developer - nsouch@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 Jun 28 10:54:40 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from revolt.poohsticks.org (revolt.poohsticks.org [63.227.60.74])
by hub.freebsd.org (Postfix) with ESMTP id 05E2A37B406
for <freebsd-hackers@FreeBSD.ORG>; Thu, 28 Jun 2001 10:54:38 -0700 (PDT)
(envelope-from drew@revolt.poohsticks.org)
Received: from revolt.poohsticks.org (localhost [127.0.0.1])
by revolt.poohsticks.org (8.11.3/8.11.3) with ESMTP id f5SHrqT05567;
Thu, 28 Jun 2001 11:53:52 -0600 (MDT)
(envelope-from drew@revolt.poohsticks.org)
Message-Id: <200106281753.f5SHrqT05567@revolt.poohsticks.org>
To: Nicolas Souchu <nsouch@fr.alcove.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: processes private data
In-reply-to: Your message of "Thu, 28 Jun 2001 18:25:33 +0200."
<20010628182533.B17804@avon.alcove-fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5564.993750832.1@revolt.poohsticks.org>
Date: Thu, 28 Jun 2001 11:53:52 -0600
From: Drew Eckhardt <drew@PoohSticks.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In message <20010628182533.B17804@avon.alcove-fr>, nsouch@fr.alcove.com writes:
>Hi folks,
>
>I have a char driver that must be opened by more than one process. The minor
>index is not sufficient for this. Is there any process private data (void *)
>in the devfs structure (or the opposite) I could point to with the minor index
>of my device?
No.
You want to split your minor number into separate unit and instance parts,
and allow each instance to be only opened once (return EBUSY). A quick fix
is to continue selecting the softc structure exclusively based on unit
number and to hang the necessary per instance data off that.
--
<a href="http://www.poohsticks.org/drew/">Home Page</a>
For those who do, no explanation is necessary.
For those who don't, no explanation is possible.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 11: 3:42 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from revolt.poohsticks.org (revolt.poohsticks.org [63.227.60.74])
by hub.freebsd.org (Postfix) with ESMTP id B9F6037B407
for <freebsd-hackers@FreeBSD.ORG>; Thu, 28 Jun 2001 11:03:39 -0700 (PDT)
(envelope-from drew@revolt.poohsticks.org)
Received: from revolt.poohsticks.org (localhost [127.0.0.1])
by revolt.poohsticks.org (8.11.3/8.11.3) with ESMTP id f5SI33T05601;
Thu, 28 Jun 2001 12:03:03 -0600 (MDT)
(envelope-from drew@revolt.poohsticks.org)
Message-Id: <200106281803.f5SI33T05601@revolt.poohsticks.org>
To: "Eugene L. Vorokov" <vel@bugz.infotecs.ru>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: allocating user space memory from kernel mode
In-reply-to: Your message of "Thu, 28 Jun 2001 19:57:55 +0400."
<200106281557.f5SFvue68254@bugz.infotecs.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5598.993751383.1@revolt.poohsticks.org>
Date: Thu, 28 Jun 2001 12:03:03 -0600
From: Drew Eckhardt <drew@PoohSticks.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In message <200106281557.f5SFvue68254@bugz.infotecs.ru>, vel@bugz.infotecs.ru w
rites:
>Hello,
>
>is it possible to allocate and then maybe free memory in user space
>from kernel mode, if I have struct proc of the process that memory should
>belong to ?
Yes.
>What is the easiest and safest method of doing this ?
Probably vm_mmap with the MAP_ANON flag and without MAP_FIXED.
>I have seen some example that uses obreak(), but that seems very tricky
>and suspicious ... I don't really understand what obreak() really does
>and how to use it ...
I wouldn't want to confuse the user land memory allocators by changing
heap size.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 11:31:26 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from imo-d07.mx.aol.com (imo-d07.mx.aol.com [205.188.157.39])
by hub.freebsd.org (Postfix) with ESMTP id DDCB737B403
for <hackers@freebsd.org>; Thu, 28 Jun 2001 11:31:18 -0700 (PDT)
(envelope-from Bsdguru@aol.com)
Received: from Bsdguru@aol.com
by imo-d07.mx.aol.com (mail_out_v31.6.) id n.121.f1f847 (16787)
for <hackers@freebsd.org>; Thu, 28 Jun 2001 14:31:17 -0400 (EDT)
From: Bsdguru@aol.com
Message-ID: <121.f1f847.286cd1f4@aol.com>
Date: Thu, 28 Jun 2001 14:31:16 EDT
Subject: Re: Status of encryption hardware support in FreeBSD
To: hackers@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 5.0 for Windows sub 139
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In a message dated 06/27/2001 11:06:12 PM Eastern Daylight Time,
soren@soekris.com writes:
> That's not really the point here, I was talking about lowest end
> hardware compared to high end CPU. If we compare with high end hardware,
> then we're talking about factor >50 faster than software.... There are
> chips out that can do >1Gbit 3-DES, given a 64bit/66Mhz PCI bus.
>
> I'm just starting with a low end chip to complement my 133 Mhz 486 based
> net4501 board, with the goal of low cost and low power, not absolute
> performance.
Its cheaper and more flexible to buy a faster motherboard, which is the point
to the rest of us who are deciding if we care about a hardware solution.
Bryan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 11:35:59 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from imo-m02.mx.aol.com (imo-m02.mx.aol.com [64.12.136.5])
by hub.freebsd.org (Postfix) with ESMTP id 35D0637B406
for <hackers@freebsd.org>; Thu, 28 Jun 2001 11:35:57 -0700 (PDT)
(envelope-from Bsdguru@aol.com)
Received: from Bsdguru@aol.com
by imo-m02.mx.aol.com (mail_out_v31.6.) id n.11b.eff6ca (16787)
for <hackers@freebsd.org>; Thu, 28 Jun 2001 14:35:54 -0400 (EDT)
From: Bsdguru@aol.com
Message-ID: <11b.eff6ca.286cd30a@aol.com>
Date: Thu, 28 Jun 2001 14:35:54 EDT
Subject: Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
To: hackers@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 5.0 for Windows sub 139
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In a message dated 06/28/2001 12:23:24 AM Eastern Daylight Time,
wes@softweyr.com writes:
> > Personally I don't care much about BSD vs. GPL and am
> > annoyed by Microsoft's hypocricy (sp?). The fact that
> > they're using open source software is great.
>
> That was the point I was trying to make. Rather than be annoyed by this,
> it should be splashed across /., lwn, etc. But I'm not gonna do it.
> Maybe ESR will if you tell him.
>
I dont think that microsoft is being hypocritical. They dont generally say
that open source has no value, only that they dont agree that its a viable
strategy for marketing commercial products. I dont think that the fact that
they use some code as a base for their products contradicts that position at
all.
Bryan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 11:47:20 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx2.magma.ca (mx2.magma.ca [206.191.0.250])
by hub.freebsd.org (Postfix) with ESMTP id C1A8E37B405
for <freebsd-hackers@FreeBSD.ORG>; Thu, 28 Jun 2001 11:47:13 -0700 (PDT)
(envelope-from louisphilippe@macadamian.com)
Received: from mail5.magma.ca (mail5.magma.ca [206.191.0.225])
by mx2.magma.ca (8.9.3/8.9.3) with ESMTP id OAA23786;
Thu, 28 Jun 2001 14:47:12 -0400 (EDT)
Received: from durandal (mothership.macadamian.com [206.191.21.204])
by mail5.magma.ca (8.11.2/8.11.2) with SMTP id f5SIlBj01042;
Thu, 28 Jun 2001 14:47:11 -0400 (EDT)
Message-ID: <067601c10002$a48811c0$2964a8c0@macadamian.com>
From: "Louis-Philippe Gagnon" <louisphilippe@macadamian.com>
To: "Daniel Eischen" <eischen@vigrid.com>
Cc: <freebsd-hackers@FreeBSD.ORG>
References: <Pine.SUN.3.91.1010626165947.10822A-100000@pcnet1.pcnet.com>
Subject: Re: pthread/longjmp/signal problem
Date: Thu, 28 Jun 2001 14:46:28 -0400
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Thanks! I'll try it as soon as possible (I don't have a -stable machine ready, and I'd rather not try my first "make world"
attempts on my production machine...)
Louis-Philippe Gagnon
----- Original Message -----
From: "Daniel Eischen" <eischen@vigrid.com>
To: "Louis-Philippe Gagnon" <louisphilippe@macadamian.com>
Cc: <freebsd-hackers@FreeBSD.ORG>
Sent: Tuesday, June 26, 2001 5:08 PM
Subject: Re: pthread/longjmp/signal problem
> On Thu, 21 Jun 2001, Louis-Philippe Gagnon wrote:
> > No reactions the first time, let's try again.
> >
> > I've encountered a problem in the interaction betwen signals, longjmp and
> > pthreads; I'm hoping someone can help me make sense of it.
> >
> > I've been trying to implement a IsBadReadPtr-style function in FreeBSD by
> > using signal handlers and longjmp/setjmp. It seemed to work as expected,
> > until I started using the -pthread option to gcc (thus linking against
> > libc_r). Now the function only works on the first call; subsequent calls
> > hang on the segmentation fault.
> >
> > Here's an example of the kind of code that causes problems :
>
> Try this patch (to -stable). Only the patch to uthread_sig.c is
> needed for -current.
>
> --
> Dan Eischen
>
>
> Index: libc/i386/gen/setjmp.S
> ===================================================================
> RCS file: /opt/FreeBSD/cvs/src/lib/libc/i386/gen/setjmp.S,v
> retrieving revision 1.17.2.1
> diff -u -r1.17.2.1 setjmp.S
> --- libc/i386/gen/setjmp.S 2000/05/16 20:43:21 1.17.2.1
> +++ libc/i386/gen/setjmp.S 2001/06/26 21:07:23
> @@ -61,11 +61,7 @@
> pushl %eax /* (sigset_t*)oset */
> pushl $0 /* (sigset_t*)set */
> pushl $1 /* SIG_BLOCK */
> -#ifdef _THREAD_SAFE
> - call PIC_PLT(CNAME(_thread_sys_sigprocmask))
> -#else
> call PIC_PLT(CNAME(sigprocmask))
> -#endif
> addl $12,%esp
> PIC_EPILOGUE
> movl 4(%esp),%ecx
> @@ -91,11 +87,7 @@
> leal 28(%edx), %eax
> pushl %eax /* (sigset_t*)set */
> pushl $3 /* SIG_SETMASK */
> -#ifdef _THREAD_SAFE
> - call PIC_PLT(CNAME(_thread_sys_sigprocmask))
> -#else
> call PIC_PLT(CNAME(sigprocmask))
> -#endif
> addl $12,%esp
> PIC_EPILOGUE
> movl 4(%esp),%edx
> Index: libc/i386/gen/sigsetjmp.S
> ===================================================================
> RCS file: /opt/FreeBSD/cvs/src/lib/libc/i386/gen/sigsetjmp.S,v
> retrieving revision 1.19.2.1
> diff -u -r1.19.2.1 sigsetjmp.S
> --- libc/i386/gen/sigsetjmp.S 2000/05/16 20:43:21 1.19.2.1
> +++ libc/i386/gen/sigsetjmp.S 2001/06/26 21:04:34
> @@ -70,11 +70,7 @@
> pushl %eax /* (sigset_t*)oset */
> pushl $0 /* (sigset_t*)set */
> pushl $1 /* SIG_BLOCK */
> -#ifdef _THREAD_SAFE
> - call PIC_PLT(CNAME(_thread_sys_sigprocmask))
> -#else
> call PIC_PLT(CNAME(sigprocmask))
> -#endif
> addl $12,%esp
> PIC_EPILOGUE
> movl 4(%esp),%ecx
> @@ -102,11 +98,7 @@
> leal 28(%edx), %eax
> pushl %eax /* (sigset_t*)set */
> pushl $3 /* SIG_SETMASK */
> -#ifdef _THREAD_SAFE
> - call PIC_PLT(CNAME(_thread_sys_sigprocmask))
> -#else
> call PIC_PLT(CNAME(sigprocmask))
> -#endif
> addl $12,%esp
> PIC_EPILOGUE
> movl 4(%esp),%edx
> Index: libc_r/uthread/uthread_sig.c
> ===================================================================
> RCS file: /opt/FreeBSD/cvs/src/lib/libc_r/uthread/uthread_sig.c,v
> retrieving revision 1.25.2.7
> diff -u -r1.25.2.7 uthread_sig.c
> --- libc_r/uthread/uthread_sig.c 2001/06/23 00:47:05 1.25.2.7
> +++ libc_r/uthread/uthread_sig.c 2001/06/26 20:56:52
> @@ -931,6 +931,12 @@
> thread->curframe = NULL;
> PTHREAD_ASSERT(psf != NULL, "Invalid signal frame in signal handler");
>
> + /*
> + * We came here from the kernel scheduler; clear the in scheduler
> + * flag.
> + */
> + _thread_kern_in_sched = 0;
> +
> /* Check the threads previous state: */
> if (psf->saved_state.psd_state != PS_RUNNING) {
> /*
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 11:49:41 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20])
by hub.freebsd.org (Postfix) with ESMTP id AC95637B40C
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 11:49:38 -0700 (PDT)
(envelope-from dfr@nlsystems.com)
Received: from [62.49.251.130] (helo=herring.nlsystems.com)
by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2)
id 15FgrB-0001WN-0K; Thu, 28 Jun 2001 18:49:37 +0000
Received: from herring (herring [10.0.0.2])
by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f5SImL700989;
Thu, 28 Jun 2001 19:48:21 +0100 (BST)
(envelope-from dfr@nlsystems.com)
Date: Thu, 28 Jun 2001 19:48:21 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Nicolas Souchu <nsouch@fr.alcove.com>
Cc: <freebsd-hackers@freebsd.org>
Subject: Re: processes private data
In-Reply-To: <20010628182533.B17804@avon.alcove-fr>
Message-ID: <Pine.BSF.4.33.0106281944210.866-100000@herring.nlsystems.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Thu, 28 Jun 2001, Nicolas Souchu wrote:
> Hi folks,
>
> I have a char driver that must be opened by more than one process. The minor
> index is not sufficient for this. Is there any process private data (void *)
> in the devfs structure (or the opposite) I could point to with the minor index
> of my device?
The only way I know of to do this is to get a new struct file with
falloc() and install your own fileops. You can then set p->p_dupfd to the
new file descriptor and return ENXIO. The caller will magically use the
new struct file. For an example, see streamsopen() in
sys/dev/streams/streams.c.
--
Doug Rabson Mail: dfr@nlsystems.com
Phone: +44 20 8348 6160
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 11:55:52 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from Exchange2000.com-con.ag (exchange2000.com-con.net [212.6.164.8])
by hub.freebsd.org (Postfix) with ESMTP
id C0BF937B403; Thu, 28 Jun 2001 11:55:46 -0700 (PDT)
(envelope-from rh@com-con.net)
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: again: how to compile bpf...
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Date: Thu, 28 Jun 2001 20:55:44 +0100
Message-ID: <F54B610C5BFDE546BBA2F6CC595ACC75084981@Exchange2000.com-con.ag>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: how to compile bpf...
Thread-Index: AcD/0Os8DzAqcDexTgGN2aRq1P2uNw==
From: "Heimes, Rene" <rh@com-con.net>
To: <freebsd-questions@freebsd.org>, <freebsd-hackers@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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
I =B4m using NeTraMet Vers. 4.3 on an FreeBSD 4.2 System (i386)
with libpcap-04.
NeTraMet uses libpcap for monitoring and get the packets on the LAN.
It could be that ethernet packets were dropped by the kernel and
NeTraMet, which happens when i capture some minutes of the LAN traffic
with tcpdump 3.5 .
Tcpdump gives an information about how many packets were filtered and
how many packet were dropped by the kernel.
NeTraMet doesn=B4t do this.
How could i be on the secure site, that NeTraMet get all packets.
If NeTraMet droppes the packets like tcpdump what can I do.
In the newsforum from NeTraMet someone says to boost the bpf buffer but
he didn=B4t know how.
(the counter it is referring to in /sys/net/bpf.c in the kernel.)
seems to be=20
# define BPF_BUFSIZE 4096
so i have to increase this.
And there for I have to recompile the c-source code, but which of the
source and how.
Where I have to put the binary??
Could you help me or give some hints??=20
Thanks in advance
Ren=E9 Heimes
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 13: 5:28 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from tcpns.com (dsl-64-192-239-221.telocity.com [64.192.239.221])
by hub.freebsd.org (Postfix) with ESMTP id 5F23737B40C
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 13:05:25 -0700 (PDT)
(envelope-from jcborkow@tcpns.com)
Received: from localhost (jcborkow@localhost)
by tcpns.com (8.11.4/8.11.4) with ESMTP id f5SK5Od22366
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 16:05:24 -0400 (EDT)
Date: Thu, 28 Jun 2001 16:05:24 -0400 (EDT)
From: Jason Borkowsky <jcborkow@tcpns.com>
To: freebsd-hackers@freebsd.org
Subject: Serial port control
Message-ID: <Pine.BSF.4.21.0106281559200.22355-100000@bemused.tcpns.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
I am looking to find a simple way to control a serial port through BSD
(such as raising and lowering DTR for a specified duration). I thought I
had it using ioctl() and wrote a simple program to test it, but it seems I
don't have a full understanding of ioctl(). Does anyone know of any
pre-written utilities I can use? Or where to get some really detailed
information about ioctl()? Thanks!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 13: 7:31 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40])
by hub.freebsd.org (Postfix) with ESMTP id A85D937B40C
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 13:07:24 -0700 (PDT)
(envelope-from cdf.lists@fxp.org)
Received: by peitho.fxp.org (Postfix, from userid 1501)
id C88C41360C; Thu, 28 Jun 2001 16:07:23 -0400 (EDT)
Date: Thu, 28 Jun 2001 16:07:23 -0400
From: Chris Faulhaber <jedgar@fxp.org>
To: Jason Borkowsky <jcborkow@tcpns.com>
Cc: freebsd-hackers@freebsd.org
Subject: Re: Serial port control
Message-ID: <20010628160723.C21188@peitho.fxp.org>
Mail-Followup-To: Chris Faulhaber <jedgar@fxp.org>,
Jason Borkowsky <jcborkow@tcpns.com>, freebsd-hackers@freebsd.org
References: <Pine.BSF.4.21.0106281559200.22355-100000@bemused.tcpns.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="iFRdW5/EC4oqxDHL"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.BSF.4.21.0106281559200.22355-100000@bemused.tcpns.com>; from jcborkow@tcpns.com on Thu, Jun 28, 2001 at 04:05:24PM -0400
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
--iFRdW5/EC4oqxDHL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Jun 28, 2001 at 04:05:24PM -0400, Jason Borkowsky wrote:
>=20
> I am looking to find a simple way to control a serial port through BSD
> (such as raising and lowering DTR for a specified duration). I thought I
> had it using ioctl() and wrote a simple program to test it, but it seems I
> don't have a full understanding of ioctl(). Does anyone know of any
> pre-written utilities I can use? Or where to get some really detailed
> information about ioctl()? Thanks!
>=20
Many links at: http://www.stokely.com/unix.serial.port.resources/
in particular: http://www.easysw.com/~mike/serial/serial.html
--=20
Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org
--------------------------------------------------------
FreeBSD: The Power To Serve - http://www.FreeBSD.org
--iFRdW5/EC4oqxDHL
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: FreeBSD: The Power To Serve
iEYEARECAAYFAjs7jnsACgkQObaG4P6BelA3GQCggfjbSd5KqQ143UP/38cyqlx2
F1QAnjXltbjP4Yf89lSD0lc/swmMBWHL
=tUvG
-----END PGP SIGNATURE-----
--iFRdW5/EC4oqxDHL--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 13:33:14 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
by hub.freebsd.org (Postfix) with ESMTP
id 14E3D37B406; Thu, 28 Jun 2001 13:33:08 -0700 (PDT)
(envelope-from des@ofug.org)
Received: (from des@localhost)
by flood.ping.uio.no (8.9.3/8.9.3) id WAA02680;
Thu, 28 Jun 2001 22:32:50 +0200 (CEST)
(envelope-from des@ofug.org)
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: Wes Peters <wes@softweyr.com>
Cc: Ruslan Ermilov <ru@FreeBSD.ORG>, Deepak Jain <deepak@ai.net>,
net@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: Re: fastforwarding?
References: <GPEOJKGHAMKFIOMAGMDICEOJDGAA.deepak@ai.net>
<20010626093545.D49992@sunbay.com> <3B3AB4F8.184A2EFE@softweyr.com>
From: Dag-Erling Smorgrav <des@ofug.org>
Date: 28 Jun 2001 22:32:50 +0200
In-Reply-To: <3B3AB4F8.184A2EFE@softweyr.com>
Message-ID: <xzp1yo4wdjh.fsf@flood.ping.uio.no>
Lines: 14
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Wes Peters <wes@softweyr.com> writes:
> The description there isn't very forthcoming. fastforwarding caches
> the results of a route lookup for destination addresses that are not
> on the local machine, and uses the cached route to short-circuit the
> normal (relatively slow) route lookup process. The packet flows
> directly from one layer2 input routine directly to the opposing
> layer2 output routine without traversing the IP layer.
And more importantly, without traversing ipfw or ipfilter. In other
words, don't use this on a firewall.
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 Thu Jun 28 14:31:55 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28])
by hub.freebsd.org (Postfix) with ESMTP
id 220D237B409; Thu, 28 Jun 2001 14:31:49 -0700 (PDT)
(envelope-from chris@holly.calldei.com)
Received: from holly.calldei.com ([208.191.149.190]) by mta4.rcsntx.swbell.net
(Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10)
with ESMTP id <0GFN004S7T4AWF@mta4.rcsntx.swbell.net>; Thu,
28 Jun 2001 16:31:55 -0500 (CDT)
Received: (from chris@localhost) by holly.calldei.com (8.11.1/8.9.3)
id f5SLUGc63434; Thu, 28 Jun 2001 16:30:16 -0500 (CDT envelope-from chris)
Date: Thu, 28 Jun 2001 16:29:30 -0500
From: Chris Costello <chris@calldei.com>
Subject: Re: FreeBSD Monthly Development Status Report, June 2001
In-reply-to: <20010614110703.A91909@ark.cris.net>; from phantom@ark.cris.net on
Thu, Jun 14, 2001 at 11:07:03AM +0300
To: Alexey Zelkin <phantom@ark.cris.net>
Cc: Dima Dorfman <dima@unixfreak.org>, rwatson@FreeBSD.ORG,
hackers@FreeBSD.ORG, doc@FreeBSD.ORG
Reply-To: chris@calldei.com
Message-id: <20010628162930.D55395@holly.calldei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
User-Agent: Mutt/1.2.5i
References: <Pine.NEB.3.96L.1010613185804.5910E-100000@fledge.watson.org>
<20010614024036.2B39F3E28@bazooka.unixfreak.org>
<20010613214752.C5865@holly.calldei.com> <20010614110703.A91909@ark.cris.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Thursday, June 14, 2001, Alexey Zelkin wrote:
> ps: But I think it can be good idea to put sgml'ified copy of this report (and
> others) to web site, like we had Really Quick Newsletter for some time. Any
> takers ?
Hmmm. I just noticed this email.
It sounds like a nice idea to keep it in www, actually. Do
you mean formatted using DocBook, or just HTML?
--
+-------------------+--------------------------------------------------------+
| Chris Costello | All new: |
| chris@calldei.com | The software is not compatible with previous versions. |
+-------------------+--------------------------------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 14:58:41 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from tcpns.com (dsl-64-192-239-221.telocity.com [64.192.239.221])
by hub.freebsd.org (Postfix) with ESMTP id E926737B406
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 14:58:32 -0700 (PDT)
(envelope-from jcborkow@tcpns.com)
Received: from localhost (jcborkow@localhost)
by tcpns.com (8.11.4/8.11.4) with ESMTP id f5SLwSB22979;
Thu, 28 Jun 2001 17:58:29 -0400 (EDT)
Date: Thu, 28 Jun 2001 17:58:28 -0400 (EDT)
From: Jason Borkowsky <jcborkow@tcpns.com>
To: Chris Faulhaber <jedgar@fxp.org>
Cc: freebsd-hackers@freebsd.org
Subject: Re: Serial port control
In-Reply-To: <20010628160723.C21188@peitho.fxp.org>
Message-ID: <Pine.BSF.4.21.0106281752090.22968-100000@bemused.tcpns.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> > I am looking to find a simple way to control a serial port through BSD
> > (such as raising and lowering DTR for a specified duration). I thought I
> > had it using ioctl() and wrote a simple program to test it, but it seems I
> > don't have a full understanding of ioctl(). Does anyone know of any
> > pre-written utilities I can use? Or where to get some really detailed
> > information about ioctl()? Thanks!
> >
>
> Many links at: http://www.stokely.com/unix.serial.port.resources/
>
> in particular: http://www.easysw.com/~mike/serial/serial.html
I thought I maybe had this under control, but not yet.
I am trying to control the serial control lines on a FreeBSD 4.2 box, and
wrote a simple program (included below). This program polls the serial
controller for its current state, displays the state, and then attempts to
set the state of two of the control lines (lower RTS and DTR). However,
after telling ioctl() to lower RTS and DTR, and then polling the status
again, RTS and DTR are still high. Does anyone know which serial control
lines FreeBSD allows you to manipulate and why this isn't working?
To compile the program, merely save it as text, gcc the text file, and
run. Any insight is greatly appreciated!
#include <stdio.h>
#include <fcntl.h>
#include <errno.h>
#include <termios.h>
main () {
int fd; /* File descriptor for serial port */
int status; /* Serial port status bitmask */
fd = open("/dev/cuaa0", O_RDWR | O_NOCTTY | O_NDELAY);
if (fd == -1)
perror("open_port: Unable to open /dev/ttyf1 - ");
else
fcntl(fd, F_SETFL, 0);
/* Get serial line status bits */
ioctl(fd,TIOCMGET,&status);
/* Signal Values, obtained from ttycom.h
*
* 1 - DSR (Data Set Ready)
* 2 - DTR (Data Terminal Ready)
* 4 - RTS (Request to Send)
* 8 - ST (Secondary Transmit)
* 16 - SR (Secondary Receive)
* 32 - CTS (Clear to Send)
* 64 - DCD (Data Carrier Detect)
* 128 - RNG (Ring)
* 256 - DSR (Data Set Ready)
*/
printf ("Current Serial Settings:");
if (status >= TIOCM_DSR) {
status -= TIOCM_DSR;
printf (" DSR ");
}
if (status >= TIOCM_RNG) {
status -= TIOCM_RNG;
printf (" Ring ");
}
if (status >= TIOCM_CD) {
status -= TIOCM_CD;
printf (" DCD ");
}
if (status >= TIOCM_CTS) {
status -= TIOCM_CTS;
printf (" CTS ");
}
if (status >= TIOCM_SR) {
status -= TIOCM_SR;
printf (" SR ");
}
if (status >= TIOCM_ST) {
status -= TIOCM_ST;
printf (" ST ");
}
if (status >= TIOCM_RTS) {
status -= TIOCM_RTS;
printf (" RTS ");
}
if (status >= TIOCM_DTR) {
status -= TIOCM_DTR;
printf (" DTR ");
}
if (status >= TIOCM_LE) {
status -= TIOCM_LE;
printf (" DSR ");
}
printf("\n");
/* SET STATUS to 1 (DTR and RTS lowered). Previous status was 7 (DSR, DTR,
* RTS high).
*/
status = 1;
ioctl(fd,TIOCMSET,status);
/* Check status after setting serial control bits */
ioctl(fd,TIOCMGET,&status);
printf ("Current Serial Settings:");
if (status >= TIOCM_DSR) {
status -= TIOCM_DSR;
printf (" DSR ");
}
if (status >= TIOCM_RNG) {
status -= TIOCM_RNG;
printf (" Ring ");
}
if (status >= TIOCM_CD) {
status -= TIOCM_CD;
printf (" DCD ");
}
if (status >= TIOCM_CTS) {
status -= TIOCM_CTS;
printf (" CTS ");
}
if (status >= TIOCM_SR) {
status -= TIOCM_SR;
printf (" SR ");
}
if (status >= TIOCM_ST) {
status -= TIOCM_ST;
printf (" ST ");
}
if (status >= TIOCM_RTS) {
status -= TIOCM_RTS;
printf (" RTS ");
}
if (status >= TIOCM_DTR) {
status -= TIOCM_DTR;
printf (" DTR ");
}
if (status >= TIOCM_LE) {
status -= TIOCM_LE;
printf (" DSR ");
}
printf("\n");
}
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 15:35:35 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from hotmail.com (law2-f146.hotmail.com [216.32.181.146])
by hub.freebsd.org (Postfix) with ESMTP id 94B9037B40D
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 15:35:33 -0700 (PDT)
(envelope-from vinupattery@hotmail.com)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
Thu, 28 Jun 2001 15:35:33 -0700
Received: from 128.193.55.43 by lw2fd.hotmail.msn.com with HTTP; Thu, 28 Jun 2001 22:35:32 GMT
X-Originating-IP: [128.193.55.43]
From: "vinu pattery" <vinupattery@hotmail.com>
To: freebsd-hackers@freebsd.org
Subject: interrupt on to Kernel
Date: Fri, 29 Jun 2001 04:05:32 +0530
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <LAW2-F146DbH8J0sca000004399@hotmail.com>
X-OriginalArrivalTime: 28 Jun 2001 22:35:33.0336 (UTC) FILETIME=[A4976D80:01C10022]
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Could some body let me know, how to hack the FReeBSD kernel to learn the
exact sequence of steps which happen when the device driver interrupts the
FreeBSD Kernel for resources. Is there a trace debugger available, with
which i can find out the steps.
thanx
Vinu
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 17:30:46 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from tcpns.com (dsl-64-192-239-221.telocity.com [64.192.239.221])
by hub.freebsd.org (Postfix) with ESMTP id BFA5337B40B
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 17:30:38 -0700 (PDT)
(envelope-from jcborkow@tcpns.com)
Received: from localhost (jcborkow@localhost)
by tcpns.com (8.11.4/8.11.4) with ESMTP id f5T0Ucg23360
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 20:30:39 -0400 (EDT)
Date: Thu, 28 Jun 2001 20:30:38 -0400 (EDT)
From: Jason Borkowsky <jcborkow@tcpns.com>
To: freebsd-hackers@freebsd.org
Subject: Re: Serial port control
In-Reply-To: <20010628160723.C21188@peitho.fxp.org>
Message-ID: <Pine.BSF.4.21.0106282024030.23341-100000@bemused.tcpns.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> > I am looking to find a simple way to control a serial port through BSD
> > (such as raising and lowering DTR for a specified duration). I thought I
> > had it using ioctl() and wrote a simple program to test it, but it seems I
> > don't have a full understanding of ioctl(). Does anyone know of any
> > pre-written utilities I can use? Or where to get some really detailed
> > information about ioctl()? Thanks!
After several responses, I thought I had it. From a software point of
view, my program, included below, works fine. But from a hardware point of
view, the signals I am trying to lower, RTS and DTR, are staying
high. Can anyone try to compile the below program and do a serial port
test with an RS-232 tester and see if anyone actually sees RTS and DTR
going low? Sorry for bothering everyone with this again, but this is
driving me nuts and I can't figure out the problem now. Thanks!
#include <stdio.h>
#include <fcntl.h>
#include <errno.h>
#include <termios.h>
main () {
int fd; /* File descriptor for serial port */
int status; /* Serial port status bitmask */
int error = 0;
fd = open("/dev/cuaa0", O_RDWR | O_NOCTTY | O_NDELAY);
if (fd == -1)
perror("open_port: Unable to open /dev/ttyf1 - ");
else
error = fcntl(fd, F_SETFL, 0);
if (error == -1)
perror("fcntl error - ");
/* Get serial line status bitmask */
error = 0;
error = ioctl(fd,TIOCMGET,&status);
if (error == -1)
perror("ioctl1 GET error - ");
/* Signal Values
*
* 1 - DSR (Data Set Ready)
* 2 - DTR (Data Terminal Ready)
* 4 - RTS (Request to Send)
* 8 - ST (Secondary Transmit)
* 16 - SR (Secondary Receive)
* 32 - CTS (Clear to Send)
* 64 - DCD (Data Carrier Detect)
* 128 - RNG (Ring)
* 256 - DSR (Data Set Ready)
*/
printf ("Current Serial Settings:");
if (status >= TIOCM_DSR) {
status -= TIOCM_DSR;
printf (" DSR ");
}
if (status >= TIOCM_RNG) {
status -= TIOCM_RNG;
printf (" Ring ");
}
if (status >= TIOCM_CD) {
status -= TIOCM_CD;
printf (" DCD ");
}
if (status >= TIOCM_CTS) {
status -= TIOCM_CTS;
printf (" CTS ");
}
if (status >= TIOCM_SR) {
status -= TIOCM_SR;
printf (" SR ");
}
if (status >= TIOCM_ST) {
status -= TIOCM_ST;
printf (" ST ");
}
if (status >= TIOCM_RTS) {
status -= TIOCM_RTS;
printf (" RTS ");
}
if (status >= TIOCM_DTR) {
status -= TIOCM_DTR;
printf (" DTR ");
}
if (status >= TIOCM_LE) {
status -= TIOCM_LE;
printf (" DSR ");
}
printf("\n");
/* Lower DTR and RTS */
status = 1;
error = 0;
error = ioctl(fd,TIOCMSET,&status);
if (error == -1)
perror ("ioctl SET error - ");
/* Hold the signals low, as they seem to reset when releasing the
* file descriptor
*/
sleep(10);
error = 0;
error = ioctl(fd,TIOCMGET,&status);
if (error == -1)
perror ("ioctl GET error - ");
printf ("Current Serial Settings:");
if (status >= TIOCM_DSR) {
status -= TIOCM_DSR;
printf (" DSR ");
}
if (status >= TIOCM_RNG) {
status -= TIOCM_RNG;
printf (" Ring ");
}
if (status >= TIOCM_CD) {
status -= TIOCM_CD;
printf (" DCD ");
}
if (status >= TIOCM_CTS) {
status -= TIOCM_CTS;
printf (" CTS ");
}
if (status >= TIOCM_SR) {
status -= TIOCM_SR;
printf (" SR ");
}
if (status >= TIOCM_ST) {
status -= TIOCM_ST;
printf (" ST ");
}
if (status >= TIOCM_RTS) {
status -= TIOCM_RTS;
printf (" RTS ");
}
if (status >= TIOCM_DTR) {
status -= TIOCM_DTR;
printf (" DTR ");
}
if (status >= TIOCM_LE) {
status -= TIOCM_LE;
printf (" DSR ");
}
printf("\n");
close(fd);
}
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 17:48:48 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from softweyr.com (softweyr.com [208.247.99.111])
by hub.freebsd.org (Postfix) with ESMTP
id ADA0637B406; Thu, 28 Jun 2001 17:48:42 -0700 (PDT)
(envelope-from wes@softweyr.com)
Received: from localhost.softweyr.com
([127.0.0.1] helo=softweyr.com ident=4d659b1d1b9d4945f14aaf3859ab2f6e)
by softweyr.com with esmtp (Exim 3.16 #1)
id 15FmX5-0000EY-00; Thu, 28 Jun 2001 18:53:15 -0600
Message-ID: <3B3BD17B.4DB9171B@softweyr.com>
Date: Thu, 28 Jun 2001 18:53:15 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: Ruslan Ermilov <ru@FreeBSD.ORG>, Deepak Jain <deepak@ai.net>,
net@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: Re: fastforwarding?
References: <GPEOJKGHAMKFIOMAGMDICEOJDGAA.deepak@ai.net>
<20010626093545.D49992@sunbay.com> <3B3AB4F8.184A2EFE@softweyr.com> <xzp1yo4wdjh.fsf@flood.ping.uio.no>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Dag-Erling Smorgrav wrote:
>
> Wes Peters <wes@softweyr.com> writes:
> > The description there isn't very forthcoming. fastforwarding caches
> > the results of a route lookup for destination addresses that are not
> > on the local machine, and uses the cached route to short-circuit the
> > normal (relatively slow) route lookup process. The packet flows
> > directly from one layer2 input routine directly to the opposing
> > layer2 output routine without traversing the IP layer.
>
> And more importantly, without traversing ipfw or ipfilter. In other
> words, don't use this on a firewall.
Excellent point, grashopper. Perhaps we should collect this verbiage
into the man page? Or, heaven forbid, stuff it into a comment in the
code somewhere?
Nah, that would be blasphemy.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
wes@softweyr.com http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 19:15:16 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3])
by hub.freebsd.org (Postfix) with ESMTP
id DF73237B409; Thu, 28 Jun 2001 19:15:10 -0700 (PDT)
(envelope-from eddy+public+spam@noc.everquick.net)
Received: from localhost (eddy@localhost)
by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f5T2F5J02161;
Fri, 29 Jun 2001 02:15:05 GMT
X-EverQuick-No-Abuse: Report any e-mail abuse to <abuse@noc.everquick.net>
Date: Fri, 29 Jun 2001 02:15:04 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: freebsd-smp@freebsd.org, freebsd-hackers@freebsd.org
Subject: libc_r locking... why?
Message-ID: <Pine.LNX.4.20.0106290112060.1425-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Please pardon the cross-posting; I'd rather keep responses on whichever
list is more appropriate.
Why are bind(2), accept(2), kevent(2), etc. wrapped in libc_r?
I thought that the spl() calls prevented kernel recursion in the current
SMP system, and that a mutex handled reentrance in SMPng. [Please correct
me if/where I am mistaken.]
I can understand things like malloc(3), lseek(2), read(2), and write(2)
being serialized, but I'm confused about [some of the other] syscall
wrappers. Can somebody please elaborate, or direct me to a reference?
Big TIA,
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc.
EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 19:19: 9 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx01-a.netapp.com (mx01-a.netapp.com [198.95.226.53])
by hub.freebsd.org (Postfix) with ESMTP id 5D56437B405
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 19:19:05 -0700 (PDT)
(envelope-from guy@netapp.com)
Received: from frejya.corp.netapp.com (frejya.corp.netapp.com [10.10.20.91])
by mx01-a.netapp.com (8.11.1/8.11.1/NTAP-1.2) with ESMTP id f5T2J3K13826;
Thu, 28 Jun 2001 19:19:03 -0700 (PDT)
Received: from cranford-fe.eng.netapp.com (localhost [127.0.0.1])
by frejya.corp.netapp.com (8.11.1/8.11.1/NTAP-1.2) with ESMTP id f5T2J3l21102;
Thu, 28 Jun 2001 19:19:03 -0700 (PDT)
Received: (from guy@localhost)
by cranford-fe.eng.netapp.com (8.8.8+Sun/8.8.8) id TAA03266;
Thu, 28 Jun 2001 19:19:01 -0700 (PDT)
From: Guy Harris <guy@netapp.com>
Message-Id: <200106290219.TAA03266@cranford-fe.eng.netapp.com>
Subject: Re: how to compile bpf...
To: rh@com-con.net
Date: Thu, 28 Jun 2001 19:19:01 -0700 (PDT)
Cc: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org
X-Mailer: ELM [version 2.4ME++ PL59 (25)]
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
The same question was asked by Ralf Knapp <rk@com-con.net> - in fact,
the text of the question appears to be identical to the text of your
question - who sent his question to libpcap@ee.lbl.gov and
tcpdump-workers@tcpdump.org.
The answer to that question was:
Date: Thu, 28 Jun 2001 11:34:10 -0500
From: Jon Dugan <jdugan@ncsa.uiuc.edu>
To: "Knapp, Ralf"
Cc: libpcap@ee.lbl.gov, tcpdump-workers@tcpdump.org
Subject: Re: [tcpdump-workers] droped packets ?! > how to increase the bpf buffer, or libpap buffer -
You can set the BPF bufsize via sysctl:
sysctl -w debug.bpf_bufsize=whatever
See sysctl.conf(5) for more info about how to set this as part of the boot
process. See sysctl(8) for more info on sysctl.
and, given that your question was identical, the answer to your question
is also identical - you don't have to recompile the kernel, just use
"sysctl".
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 19:30: 1 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29])
by hub.freebsd.org (Postfix) with ESMTP
id BD82A37B403; Thu, 28 Jun 2001 19:29:56 -0700 (PDT)
(envelope-from chris@holly.calldei.com)
Received: from holly.calldei.com ([208.191.149.190]) by mta5.rcsntx.swbell.net
(Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10)
with ESMTP id <0GFO00KIQ6SY0A@mta5.rcsntx.swbell.net>; Thu,
28 Jun 2001 21:26:59 -0500 (CDT)
Received: (from chris@localhost) by holly.calldei.com (8.11.1/8.9.3)
id f5T2TgL63943; Thu, 28 Jun 2001 21:29:43 -0500 (CDT envelope-from chris)
Date: Thu, 28 Jun 2001 21:28:56 -0500
From: Chris Costello <chris@calldei.com>
Subject: Re: libc_r locking... why?
In-reply-to: <Pine.LNX.4.20.0106290112060.1425-100000@www.everquick.net>; from
eddy+public+spam@noc.everquick.net on Fri, Jun 29, 2001 at 02:15:04AM +0000
To: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
Cc: freebsd-smp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
Reply-To: chris@calldei.com
Message-id: <20010628212856.E55395@holly.calldei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
User-Agent: Mutt/1.2.5i
References: <Pine.LNX.4.20.0106290112060.1425-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Friday, June 29, 2001, E.B. Dreger wrote:
> Please pardon the cross-posting; I'd rather keep responses on whichever
> list is more appropriate.
>
> Why are bind(2), accept(2), kevent(2), etc. wrapped in libc_r?
Currently, the pthreads implementation is done entirely in
userland. This means that a syscall which would normally block
needs to have code in it to check if it would block (write(2)
is a really simple example of this), and if it would, schedule
another thread (cancelling, or blocking, the calling thread) to
run, and eventually get back to the thread which is blocking on
write, check for/read more data, cancel again, etc., until the
requested amount of data has been read or an error occurs.
This example, of course, applies to instances where write() is
called on a file descriptor which does _NOT_ have O_NONBLOCK set.
kevent(2), bind(2), accept(2) etc. all do the same thing for the
same reasons.
--
+-------------------+-----------------------------------------+
| Chris Costello | Advanced design: |
| chris@calldei.com | Upper management doesn't understand it. |
+-------------------+-----------------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 20:16: 4 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
by hub.freebsd.org (Postfix) with ESMTP id 327BC37B405
for <hackers@FreeBSD.ORG>; Thu, 28 Jun 2001 20:16:01 -0700 (PDT)
(envelope-from louie@whizzo.transsys.com)
Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1])
by whizzo.transsys.com (8.11.3/8.11.3) with ESMTP id f5T3G0I95199
for <hackers@FreeBSD.ORG>; Thu, 28 Jun 2001 23:16:00 -0400 (EDT)
(envelope-from louie@whizzo.transsys.com)
Message-Id: <200106290316.f5T3G0I95199@whizzo.transsys.com>
X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4
To: hackers@FreeBSD.ORG
X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: Status of encryption hardware support in FreeBSD
References: <121.f1f847.286cd1f4@aol.com>
In-reply-to: Your message of "Thu, 28 Jun 2001 14:31:16 EDT."
<121.f1f847.286cd1f4@aol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 28 Jun 2001 23:16:00 -0400
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> In a message dated 06/27/2001 11:06:12 PM Eastern Daylight Time,
> soren@soekris.com writes:
>
> > That's not really the point here, I was talking about lowest end
> > hardware compared to high end CPU. If we compare with high end hardware,
> > then we're talking about factor >50 faster than software.... There are
> > chips out that can do >1Gbit 3-DES, given a 64bit/66Mhz PCI bus.
> >
> > I'm just starting with a low end chip to complement my 133 Mhz 486 based
> > net4501 board, with the goal of low cost and low power, not absolute
> > performance.
>
> Its cheaper and more flexible to buy a faster motherboard, which is the point
> to the rest of us who are deciding if we care about a hardware solution.
Really? Have you even looked at the net4501 board which was mentioned? It's
a single-board computer constructed for some specific communication
applications, with no VGA or keyboard support, or spinning fans, and is
pretty inexpensive and in a very small form factor. Why do I want to
replace this with "a new motherboard?"
Please consider that you probably can't imagine all the applications that
these platforms might be used in, an the availability of fire-breathing
Really Fast CPUs might not actually be applicable to some applications
with very specific requirements.
"A new motherboard" isn't going to be more flexible since it's likely
to require a power supply larger than the whole low-power computer
you propose to replace. I'd rather spend the $100 or $150 to add
crypto performance for some applications and maintain the small form
factor, low power consumption, and no moving parts.
The "rest of us" covers quite a few people, with a variety of interesting
applications.
louie
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 20:25:43 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from server.soekris.com (soekris.com [216.15.61.44])
by hub.freebsd.org (Postfix) with ESMTP id C477937B40C
for <hackers@FreeBSD.ORG>; Thu, 28 Jun 2001 20:25:35 -0700 (PDT)
(envelope-from soren@soekris.com)
Received: from soekris.com (soren.soekris.com [192.168.1.4])
by server.soekris.com (8.9.2/8.9.2) with ESMTP id UAA66293;
Thu, 28 Jun 2001 20:25:43 -0700 (PDT)
(envelope-from soren@soekris.com)
Message-ID: <3B3BF52C.29FB20C@soekris.com>
Date: Thu, 28 Jun 2001 20:25:32 -0700
From: Soren Kristensen <soren@soekris.com>
Organization: Soekris Engineering
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Louis A. Mamakos" <louie@TransSys.COM>
Cc: hackers@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
References: <121.f1f847.286cd1f4@aol.com> <200106290316.f5T3G0I95199@whizzo.transsys.com>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi,
Btw, did I say that I'm planning to sell the 7951 based crypto board for
around $80 in single unnit volume, both for the PCI and MiniPCI
version....
And Mike, if my answer is just a sentence, I like to keep it on top, so
people don't have to scroll all the way down to see what I'm writing....
Soren
"Louis A. Mamakos" wrote:
>
> > In a message dated 06/27/2001 11:06:12 PM Eastern Daylight Time,
> > soren@soekris.com writes:
> >
> > > That's not really the point here, I was talking about lowest end
> > > hardware compared to high end CPU. If we compare with high end hardware,
> > > then we're talking about factor >50 faster than software.... There are
> > > chips out that can do >1Gbit 3-DES, given a 64bit/66Mhz PCI bus.
> > >
> > > I'm just starting with a low end chip to complement my 133 Mhz 486 based
> > > net4501 board, with the goal of low cost and low power, not absolute
> > > performance.
> >
> > Its cheaper and more flexible to buy a faster motherboard, which is the point
> > to the rest of us who are deciding if we care about a hardware solution.
>
> Really? Have you even looked at the net4501 board which was mentioned? It's
> a single-board computer constructed for some specific communication
> applications, with no VGA or keyboard support, or spinning fans, and is
> pretty inexpensive and in a very small form factor. Why do I want to
> replace this with "a new motherboard?"
>
> Please consider that you probably can't imagine all the applications that
> these platforms might be used in, an the availability of fire-breathing
> Really Fast CPUs might not actually be applicable to some applications
> with very specific requirements.
>
> "A new motherboard" isn't going to be more flexible since it's likely
> to require a power supply larger than the whole low-power computer
> you propose to replace. I'd rather spend the $100 or $150 to add
> crypto performance for some applications and maintain the small form
> factor, low power consumption, and no moving parts.
>
> The "rest of us" covers quite a few people, with a variety of interesting
> applications.
>
> louie
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 21:21: 4 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3])
by hub.freebsd.org (Postfix) with ESMTP
id 5ED0E37B409; Thu, 28 Jun 2001 21:20:55 -0700 (PDT)
(envelope-from eddy+public+spam@noc.everquick.net)
Received: from localhost (eddy@localhost)
by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f5T4Kqw03424;
Fri, 29 Jun 2001 04:20:52 GMT
X-EverQuick-No-Abuse: Report any e-mail abuse to <abuse@noc.everquick.net>
Date: Fri, 29 Jun 2001 04:20:51 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: Chris Costello <chris@calldei.com>
Cc: freebsd-smp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
Subject: Re: libc_r locking... why?
In-Reply-To: <20010628212856.E55395@holly.calldei.com>
Message-ID: <Pine.LNX.4.20.0106290356480.3220-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> Date: Thu, 28 Jun 2001 21:28:56 -0500
> From: Chris Costello <chris@calldei.com>
>
> > Please pardon the cross-posting; I'd rather keep responses on whichever
> > list is more appropriate.
>
> Currently, the pthreads implementation is done entirely in
> userland. This means that a syscall which would normally block
> needs to have code in it to check if it would block (write(2)
> is a really simple example of this), and if it would, schedule
> another thread (cancelling, or blocking, the calling thread) to
> run, and eventually get back to the thread which is blocking on
> write, check for/read more data, cancel again, etc., until the
> requested amount of data has been read or an error occurs.
So it's a thunk/kludge not only to enforce "proper" behavior, but also to
prevent the process from blocking and stalling other threads? This makes
sense.
> This example, of course, applies to instances where write() is
> called on a file descriptor which does _NOT_ have O_NONBLOCK set.
> kevent(2), bind(2), accept(2) etc. all do the same thing for the
> same reasons.
The reason that I asked is because I'm writing a program that uses rfork()
in the same manner as the new rfork_thread(). I couldn't understand the
need to wrap kevent(2), bind(2), or accept(2)...
In my mind, I was thinking "data integrity", trying to prevent processes
in the same "thread family" from stepping on one another. Blocking is not
a problem; where I can't use non-blocking calls, I use a worker thread.
I guess that I was looking at man pages and bits of libc_r code without
understanding the pthread implementation. I knew that it was userland,
but I thought that it created multiple processes... if this is not the
case, then I was apparently comparing apples to mangoes.
Am I correct that libc_r does _not_ use multiple processes to create
threads? Grepping for "fork" in *.c files under /usr/src/lib/libc_r leads
me to believe that this is so...
...I think that, with your prompting, I've answered my question.
Thanks,
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc.
EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 21:24:31 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from quack.kfu.com (quack.kfu.com [205.178.90.194])
by hub.freebsd.org (Postfix) with ESMTP id 70B6637B403
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 21:24:28 -0700 (PDT)
(envelope-from nsayer@quack.kfu.com)
Received: from morpheus.kfu.com (morpheus.kfu.com [3ffe:1200:301b:1:2d0:b7ff:fe3f:bdd0])
by quack.kfu.com (8.11.3/8.11.3) with ESMTP id f5T4OMa49975
(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK);
Thu, 28 Jun 2001 21:24:28 -0700 (PDT)
(envelope-from nsayer@quack.kfu.com)
Received: from quack.kfu.com (localhost [::1])
by morpheus.kfu.com (8.11.4/8.11.4) with ESMTP id f5T4OM711794;
Thu, 28 Jun 2001 21:24:22 -0700 (PDT)
(envelope-from nsayer@quack.kfu.com)
Message-ID: <3B3C02F6.6090209@quack.kfu.com>
Date: Thu, 28 Jun 2001 21:24:22 -0700
From: Nick Sayer <nsayer@quack.kfu.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.3-STABLE i386; en-US; rv:0.9.1) Gecko/20010613
X-Accept-Language: en, en-US, en-GB
MIME-Version: 1.0
To: Julian Elischer <julian@elischer.org>,
freebsd-hackers@freebsd.org
Subject: Re: bridging with pcmcia cards
References: <Pine.BSF.4.21.0106261604020.85692-100000@InterJet.elischer.org>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Julian Elischer wrote:
> bridging is not a function of it being a pc-card..
This is true, particularly with netgraph bridging.
> actually bridging may already work with wi cards
> also netgraph bridgiung may also work...
>
Bridging cannot work with wi cards, since they do not support
promiscuous transmission (that is, sending frames with other than their
own MAC address). Moreover, anyone seriously desiring to bridge wi cards
very likely wants to actually do something that is more than bridging --
they probably want to be an access point (ala Apple's "virtual airport"
functionality). The difference between that and just bridging is that
the wireless clients can see each other with certainty (that is, no
hidden node issues) and they can turn on power saving (that is, having
the receiver duty cycle be less than 100%).
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 21:34:59 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29])
by hub.freebsd.org (Postfix) with ESMTP
id CEB7837B40C; Thu, 28 Jun 2001 21:34:54 -0700 (PDT)
(envelope-from chris@holly.calldei.com)
Received: from holly.calldei.com ([208.191.149.190]) by mta5.rcsntx.swbell.net
(Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10)
with ESMTP id <0GFO00255CL7R0@mta5.rcsntx.swbell.net>; Thu,
28 Jun 2001 23:31:56 -0500 (CDT)
Received: (from chris@localhost) by holly.calldei.com (8.11.1/8.9.3)
id f5T4Ych64342; Thu, 28 Jun 2001 23:34:39 -0500 (CDT envelope-from chris)
Date: Thu, 28 Jun 2001 23:33:56 -0500
From: Chris Costello <chris@calldei.com>
Subject: Re: libc_r locking... why?
In-reply-to: <Pine.LNX.4.20.0106290356480.3220-100000@www.everquick.net>; from
eddy+public+spam@noc.everquick.net on Fri, Jun 29, 2001 at 04:20:51AM +0000
To: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
Cc: freebsd-smp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
Reply-To: chris@calldei.com
Message-id: <20010628233355.F55395@holly.calldei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
User-Agent: Mutt/1.2.5i
References: <20010628212856.E55395@holly.calldei.com>
<Pine.LNX.4.20.0106290356480.3220-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Friday, June 29, 2001, E.B. Dreger wrote:
> Am I correct that libc_r does _not_ use multiple processes to create
> threads? Grepping for "fork" in *.c files under /usr/src/lib/libc_r leads
> me to believe that this is so...
That's correct. It's implemented using setjmp/longjmp, and
storing stack pointers and the like in thread-specific data
structures.
--
+-------------------+--------------------------------+
| Chris Costello | A bug in the code is worth two |
| chris@calldei.com | in the documentation. |
+-------------------+--------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Thu Jun 28 22:10:45 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3])
by hub.freebsd.org (Postfix) with ESMTP id E639C37B40B
for <freebsd-hackers@freebsd.org>; Thu, 28 Jun 2001 22:10:41 -0700 (PDT)
(envelope-from eddy+public+spam@noc.everquick.net)
Received: from localhost (eddy@localhost)
by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f5T5AdX04004;
Fri, 29 Jun 2001 05:10:39 GMT
X-EverQuick-No-Abuse: Report any e-mail abuse to <abuse@noc.everquick.net>
Date: Fri, 29 Jun 2001 05:10:39 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: Chris Costello <chris@calldei.com>
Cc: freebsd-hackers@freebsd.org
Subject: Re: libc_r locking... why?
In-Reply-To: <20010628233355.F55395@holly.calldei.com>
Message-ID: <Pine.LNX.4.20.0106290503360.3878-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
(on -hackers only, as this post is beyond the -smp charter)
> > Am I correct that libc_r does _not_ use multiple processes to create
> > threads? Grepping for "fork" in *.c files under /usr/src/lib/libc_r
> > leads me to believe that this is so...
>
> That's correct. It's implemented using setjmp/longjmp, and
> storing stack pointers and the like in thread-specific data
> structures.
Ah, okay. Thanks.
I use this approach, too, but not for threads; I relegate this type of
architecture to state machines. I guess that cramming multiple threads
into a single PID would be considered a state machine of sorts...
Sounds like I need to just ignore libc_r and stick to syscalls and what
I've been doing. I must note, however, that the "uthreads" source
directory for libc_r provides a handy checklist of functions that might
need a bit of TLC. :-)
Thanks again,
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc.
EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 0: 2:16 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65])
by hub.freebsd.org (Postfix) with ESMTP id D742937B409
for <hackers@FreeBSD.org>; Fri, 29 Jun 2001 00:02:08 -0700 (PDT)
(envelope-from ru@whale.sunbay.crimea.ua)
Received: (from ru@localhost)
by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f5T71p093546;
Fri, 29 Jun 2001 10:01:51 +0300 (EEST)
(envelope-from ru)
Date: Fri, 29 Jun 2001 10:01:51 +0300
From: Ruslan Ermilov <ru@FreeBSD.org>
To: Dima Dorfman <dima@unixfreak.org>
Cc: hackers@FreeBSD.org
Subject: Re: ifmcstat(8) setgidness
Message-ID: <20010629100151.C91115@sunbay.com>
Mail-Followup-To: Dima Dorfman <dima@unixfreak.org>,
hackers@FreeBSD.org
References: <20010627120513.B14399@sunbay.com> <20010628012915.D2E1A3E2F@bazooka.unixfreak.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010628012915.D2E1A3E2F@bazooka.unixfreak.org>; from dima@unixfreak.org on Wed, Jun 27, 2001 at 06:29:15PM -0700
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Wed, Jun 27, 2001 at 06:29:15PM -0700, Dima Dorfman wrote:
> Ruslan Ermilov <ru@FreeBSD.org> writes:
> > On Wed, Jun 27, 2001 at 01:29:28AM -0700, Dima Dorfman wrote:
> > > Ruslan Ermilov <ru@FreeBSD.ORG> writes:
> > > > On Tue, Jun 26, 2001 at 03:04:07PM -0700, Dima Dorfman wrote:
> > > > > Hi folks,
> > > > >
> > > > > Is there a particular reason, other than the desire for more setgid
> > > > > programs, that ifmcstat(8) is setgid kmem? It seems that there's no
> > > > > reason anyone but root would want to use it, anyway. OpenBSD and
> > > > > NetBSD already nuked its setgid bit; any reason why we shouldn't
> > > > > follow suit?
> > > > >
> > > > $ ifmcstat
> > > > kvm_openfiles: Permission denied
> > >
> > > I don't follow. Yes, it needs access to kmem to work. However, I
> > > don't see why anyone other than root would need to run it, so why is
> > > it setgid? root can access kmem either way.
> > >
> > Could you please elaborate on why it should be restricted to root only?
>
> Because it looks like it doesn't provide any information that anyone
> other than the administrator would find useful (if I'm seeing things,
> please let me know), and the less setgid programs in the system the
> better our overworked security officer(s) sleep at night :-).
>
Then why not make it installed with BINMODE=550 at least?
> > OpenBSD's and NetBSD's commitlogs are too terse.
>
> This is quite an understatement!
>
I meant these particular logs. If you don't find these terse, my apologies:
: revision 1.2
: date: 2001/06/23 00:50:33; author: deraadt; state: Exp; lines: +1 -1
: only root need apply
: revision 1.2
: date: 2001/06/26 17:10:33; author: itojun; state: Exp; lines: +2 -2
: drop setgid. suggested by deraadt
Cheers,
--
Ruslan Ermilov Oracle Developer/DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 0:29:32 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62])
by hub.freebsd.org (Postfix) with ESMTP id E106637B405
for <freebsd-hackers@FreeBSD.ORG>; Fri, 29 Jun 2001 00:29:29 -0700 (PDT)
(envelope-from tlambert2@mindspring.com)
Received: from mindspring.com (dialup-209.245.136.253.Dial1.SanJose1.Level3.net [209.245.136.253])
by snipe.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA02939;
Fri, 29 Jun 2001 00:29:10 -0700 (PDT)
Message-ID: <3B3C2E66.AD9B26F2@mindspring.com>
Date: Fri, 29 Jun 2001 00:29:42 -0700
From: Terry Lambert <tlambert2@mindspring.com>
Reply-To: tlambert2@mindspring.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Drew Eckhardt <drew@PoohSticks.ORG>
Cc: Nicolas Souchu <nsouch@fr.alcove.com>,
freebsd-hackers@FreeBSD.ORG
Subject: Re: processes private data
References: <200106281753.f5SHrqT05567@revolt.poohsticks.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Drew Eckhardt wrote:
>
> In message <20010628182533.B17804@avon.alcove-fr>, nsouch@fr.alcove.com writes:
> >Hi folks,
> >
> >I have a char driver that must be opened by more than one
> >process. The minor index is not sufficient for this. Is
> >there any process private data (void *) in the devfs
> >structure (or the opposite) I could point to with the minor
> >index of my device?
>
> No.
You need a cloning device. You would need to modify the
specfs code considerably, add a void * private device
insteance data structure that could be used each time
the device was referenced, and return different vnodes.
The first thing in your way will end up being the ihash
cache for FFS-hosted device nodes, struct fileops, for
lack of a reflexive entry point for open/close, and then
specfs itself.
There is a discussion about how you might approach doing
this in the devfs case, with some good input from phk;
check the mailing list archives for -arch.
At the present time, though, the code doesn't support it
directly.
> You want to split your minor number into separate unit
> and instance parts, and allow each instance to be only
> opened once (return EBUSY). A quick fix is to continue
> selecting the softc structure exclusively based on unit
> number and to hang the necessary per instance data off that.
Actually, this probably can't work.
And this approach (different minor numbers) can't work
for binary code that doesn't expect that behaviour (e.g.
this is why you can only run one instance of vmware at a
time on FreeBSD, but can run multiple instances at a time
under Linux: the Linux device driver has per open instance
data that is is used by the driver to distinguish the
instance of the program that has it open, and then acts
accordingly based on that).
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 0:50:13 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.121.50])
by hub.freebsd.org (Postfix) with ESMTP
id C860037B406; Fri, 29 Jun 2001 00:50:03 -0700 (PDT)
(envelope-from tlambert2@mindspring.com)
Received: from mindspring.com (dialup-209.245.136.253.Dial1.SanJose1.Level3.net [209.245.136.253])
by avocet.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA20681;
Fri, 29 Jun 2001 00:49:58 -0700 (PDT)
Message-ID: <3B3C3346.E5496485@mindspring.com>
Date: Fri, 29 Jun 2001 00:50:30 -0700
From: Terry Lambert <tlambert2@mindspring.com>
Reply-To: tlambert2@mindspring.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
Cc: Chris Costello <chris@calldei.com>, freebsd-smp@FreeBSD.ORG,
freebsd-hackers@FreeBSD.ORG
Subject: Re: libc_r locking... why?
References: <Pine.LNX.4.20.0106290356480.3220-100000@www.everquick.net>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
"E.B. Dreger" wrote:
[ ... wrapped fd using functions in libc_r ... ]
> So it's a thunk/kludge not only to enforce "proper"
> behavior, but also to prevent the process from blocking
> and stalling other threads? This makes sense.
It also permits locks on the descriptors, to ensure
that one thread does not modify a descriptor out from
under another thread while it is "blocked" on some
outstanding operation.
[ ... ]
> The reason that I asked is because I'm writing a program
> that uses rfork() in the same manner as the new
> rfork_thread(). I couldn't understand the need to wrap
> kevent(2), bind(2), or accept(2)...
>
> In my mind, I was thinking "data integrity", trying to
> prevent processes in the same "thread family" from stepping
> on one another. Blocking is not a problem; where I can't
> use non-blocking calls, I use a worker thread.
The threads scheduler is in user space. It converts a
blobking call into a non-blocking call plus a context
switch. THus blocking _IS_ a problem.
> I guess that I was looking at man pages and bits of
> libc_r code without understanding the pthread implementation.
> I knew that it was userland, but I thought that it created
> multiple processes... if this is not the case, then I was
> apparently comparing apples to mangoes.
This is not the case.
The user space threads library does what the original
idea of threads was intended to do, before people started
treating it as the only hammer they had to pound on the
SMP problem with in order to achieve SMP scalability: it
utilizes the full quantum of the process, and minimizes
context switch overhead. Kernel threads don't do either
of these things well, in almost all existing implementations
out there.
> Am I correct that libc_r does _not_ use multiple processes
> to create threads?
Yes. All threads run in a single process. The threads
are not intended as a workaround for the SMP scalability
problem.
Note that you are not going to be able to combine your
rfork approach with this, if your resulting processes
end up running on different CPUs: this is because the
locking primitives in the libc_r library do _NOT_ use
the "lock" prefix on the "cmpxchg" instruction, which
means that multiple processors are not forced to a
rendevous, there's no IPI, and the TLB and L1 cache
shootdown isn't moderated by the cache MP 1.4 specification
cache coherency protocol, and thus the locks it uses are
_NOT_ MP safe.
If you "need" kernel threads, look at the Linux kernel
threads in the ports collection (it's a kernel module
that builds and installs as a package). You probably
don't, since performance of kernel threads is really only
about a 20% increment, if you implement them the SVR4 or
Solaris (pre-2.7) or Linux way. It's probably better to
implement with FreeBSD threads as they currently exist,
and get massive SMP scalability when KSE's are brought
into the source tree.
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 1: 1:47 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.121.50])
by hub.freebsd.org (Postfix) with ESMTP id B5DCC37B40B
for <freebsd-hackers@FreeBSD.ORG>; Fri, 29 Jun 2001 01:01:44 -0700 (PDT)
(envelope-from tlambert2@mindspring.com)
Received: from mindspring.com (dialup-209.245.136.253.Dial1.SanJose1.Level3.net [209.245.136.253])
by avocet.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA22028;
Fri, 29 Jun 2001 01:01:42 -0700 (PDT)
Message-ID: <3B3C3608.FF89B31D@mindspring.com>
Date: Fri, 29 Jun 2001 01:02:16 -0700
From: Terry Lambert <tlambert2@mindspring.com>
Reply-To: tlambert2@mindspring.com
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: vinu pattery <vinupattery@hotmail.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: interrupt on to Kernel
References: <LAW2-F146DbH8J0sca000004399@hotmail.com>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
vinu pattery wrote:
>
> Could some body let me know, how to hack the FReeBSD kernel
> to learn the exact sequence of steps which happen when the
> device driver interrupts the FreeBSD Kernel for resources.
> Is there a trace debugger available, with which i can find
> out the steps.
It's not clear what you mean by "interrupt the Kernel for
resources"... the only resources you can grab at interrupt
are things that you pre-allocated, things you get from a
zalloci() from a previously established interrupt safe zone
in the zone allocator (e.g. mbufs), and CPU time.
As far as your tracing question: "man ddb"; you can set
breakpoints in the kernel, and step through them. You
probably _don't_ want to do this in an interrupt routine,
but you could.
You may want to look at the FreeBSD Handbook, and at the
device driver and bus articles on:
http://www.daemonnews.org/
There is also a (fairly old) "Device Driver Writer's Guide":
http://freebsd.dei.uc.pt/tutorials/ddwg/ddwg.html
-- Terry
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 1: 1:58 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119])
by hub.freebsd.org (Postfix) with ESMTP id DAB8337B405
for <freebsd-hackers@freebsd.org>; Fri, 29 Jun 2001 01:01:52 -0700 (PDT)
(envelope-from adsharma@sharmas.dhs.org)
Received: by sharmas.dhs.org (Postfix, from userid 500)
id 55A765E06E; Fri, 29 Jun 2001 01:01:59 -0700 (PDT)
Date: Fri, 29 Jun 2001 01:01:59 -0700
From: Arun Sharma <arun@sharmas.dhs.org>
To: freebsd-hackers@freebsd.org
Subject: NGPT 1.0.0 port to freebsd
Message-ID: <20010629010159.A8557@sharmas.dhs.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.15i
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
http://freshmeat.net/projects/ngpt
http://www.sharma-home.net/~adsharma/projects/freebsd/ngpt-1.0.0-freebsd.tar.gz
Notes:
- The project has gotten more Linux specific since the last port (0.9.4)
There are a lot of ugly hacks that need cleanup.
- Please commit 27489 to help this port
- There were many deviations from the freebsd pthread.h (specifically
the omission of "const" int vs size_t etc)
- The main point of this port is to have a reasonable native freebsd
pthread implementation till the scheduler activations stuff is ready.
- Java heads: does this help to pass the JCK ? Is that the main reason
we can't have a binary FreeBSD JDK distribution ? I've read -java for
several months now and I still can't find the answer.
To test the above port:
- make test_pthread; ./test_pthread
- You may want to turn off debugging in pth_p.h
- Tested only on a UP machine (my laptop) so far. Needs SMP testing.
The earliest I can do it is this weekend.
Disclaimer:
- I've mainly done the "monkey work" of fixing compile errors and making
sure that the test program works. Haven't had a chance to look at the
implementation specifics yet. I didn't like some design decisions in
0.9.4.
- Someone here had a makecontext() patch. I think commiting it would
surely help. The way GNU pth does context creation is really
inefficient, in order to be portable (read the pth paper).
-Arun
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 1:29: 3 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65])
by hub.freebsd.org (Postfix) with ESMTP
id 8C70437B403; Fri, 29 Jun 2001 01:28:48 -0700 (PDT)
(envelope-from ru@whale.sunbay.crimea.ua)
Received: (from ru@localhost)
by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f5T8Rvx03044;
Fri, 29 Jun 2001 11:27:57 +0300 (EEST)
(envelope-from ru)
Date: Fri, 29 Jun 2001 11:27:57 +0300
From: Ruslan Ermilov <ru@FreeBSD.ORG>
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: Wes Peters <wes@softweyr.com>, Deepak Jain <deepak@ai.net>,
net@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: Re: fastforwarding?
Message-ID: <20010629112757.F91115@sunbay.com>
Mail-Followup-To: Dag-Erling Smorgrav <des@ofug.org>,
Wes Peters <wes@softweyr.com>, Deepak Jain <deepak@ai.net>,
net@FreeBSD.ORG, hackers@FreeBSD.ORG
References: <GPEOJKGHAMKFIOMAGMDICEOJDGAA.deepak@ai.net> <20010626093545.D49992@sunbay.com> <3B3AB4F8.184A2EFE@softweyr.com> <xzp1yo4wdjh.fsf@flood.ping.uio.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <xzp1yo4wdjh.fsf@flood.ping.uio.no>; from des@ofug.org on Thu, Jun 28, 2001 at 10:32:50PM +0200
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Thu, Jun 28, 2001 at 10:32:50PM +0200, Dag-Erling Smorgrav wrote:
> Wes Peters <wes@softweyr.com> writes:
> > The description there isn't very forthcoming. fastforwarding caches
> > the results of a route lookup for destination addresses that are not
> > on the local machine, and uses the cached route to short-circuit the
> > normal (relatively slow) route lookup process. The packet flows
> > directly from one layer2 input routine directly to the opposing
> > layer2 output routine without traversing the IP layer.
>
> And more importantly, without traversing ipfw or ipfilter. In other
> words, don't use this on a firewall.
>
Doesn't this match exactly what's documented in the inet(4) manpage?
: IPCTL_FASTFORWARDING (ip.fastforwarding) Boolean: enable/disable the use
: of fast IP forwarding code. Defaults to off. When
: fast forwarding is enabled, IP packets are for-
: warded directly to the appropriate network inter-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
: face with a minimal validity checking, which
: greatly improves the throughput. On the other
: hand, they bypass the standard procedures, such as
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
: IP option processing and ipfirewall(4) checking.
^^^^^^^^^^
: It is not guaranteed that every packet will be
: fast-forwarded.
BTW, Wes, I'm still waiting for a working example of an indirect route
with also indirect gateway. All I can get myself here with such a
route is:
arplookup 5.6.7.8 failed: host is not on local network
arpresolve: can't allocate llinfo for 5.6.7.8rt
where 5.6.7.8 is that indirect gateway.
Cheers,
--
Ruslan Ermilov Oracle Developer/DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 2:16: 7 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139])
by hub.freebsd.org (Postfix) with ESMTP id 214A737B40C
for <freebsd-hackers@freebsd.org>; Fri, 29 Jun 2001 02:16:00 -0700 (PDT)
(envelope-from nsouch@alcove.fr)
Received: from avon.alcove-fr ([10.16.10.3])
by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian))
id 15FuE4-0002zg-00; Fri, 29 Jun 2001 11:06:08 +0200
Received: from nsouch by avon.alcove-fr with local (Exim 3.12 #1 (Debian))
id 15FuE3-0005R3-00; Fri, 29 Jun 2001 11:06:07 +0200
Date: Fri, 29 Jun 2001 11:06:07 +0200
From: Nicolas Souchu <nsouch@fr.alcove.com>
To: Doug Rabson <dfr@nlsystems.com>
Cc: freebsd-hackers@freebsd.org
Subject: Re: processes private data
Message-ID: <20010629110607.B19935@avon.alcove-fr>
References: <20010628182533.B17804@avon.alcove-fr> <Pine.BSF.4.33.0106281944210.866-100000@herring.nlsystems.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.4i
In-Reply-To: <Pine.BSF.4.33.0106281944210.866-100000@herring.nlsystems.com>; from dfr@nlsystems.com on Thu, Jun 28, 2001 at 07:48:21PM +0100
Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Ecom?=
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Thu, Jun 28, 2001 at 07:48:21PM +0100, Doug Rabson wrote:
> On Thu, 28 Jun 2001, Nicolas Souchu wrote:
>
> > Hi folks,
> >
> > I have a char driver that must be opened by more than one process. The minor
> > index is not sufficient for this. Is there any process private data (void *)
> > in the devfs structure (or the opposite) I could point to with the minor index
> > of my device?
>
> The only way I know of to do this is to get a new struct file with
> falloc() and install your own fileops. You can then set p->p_dupfd to the
> new file descriptor and return ENXIO. The caller will magically use the
> new struct file. For an example, see streamsopen() in
> sys/dev/streams/streams.c.
Ok, it seems to do part of the job. But this won't change the content of the
file struct. Does anything ensure that the f_data of the freshly allocated
struct file won't be used by vfs? Is the new struct file only local to my
device driver?
Otherwise, I could write my own falloc() which would allocate a struct file
compatible with the original one like this:
struct my_file {
struct file original;
void *my_private;
...
};
Nicholas
--
Alcôve Technical Manager - Nicolas.Souchu@fr.alcove.com - http://www.alcove.com
Open Source Software Developer - nsouch@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 Jun 29 2:54:56 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from gadolinium.btinternet.com (gadolinium.btinternet.com [194.73.73.111])
by hub.freebsd.org (Postfix) with ESMTP id B6B8D37B410
for <freebsd-hackers@freebsd.org>; Fri, 29 Jun 2001 02:54:54 -0700 (PDT)
(envelope-from john.toon@btinternet.com)
Received: from host213-122-174-93.btinternet.com ([213.122.174.93] helo=btinternet.com)
by gadolinium.btinternet.com with esmtp (Exim 3.22 #9)
id 15Fuz9-00028n-00
for freebsd-hackers@freebsd.org; Fri, 29 Jun 2001 10:54:48 +0100
Message-ID: <3B3C5E8C.5080100@btinternet.com>
Date: Fri, 29 Jun 2001 10:55:08 +0000
From: John Toon <john.toon@btinternet.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.1-RELEASE i386; en-US; rv:0.9.1) Gecko/20010621
X-Accept-Language: en-us
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
Subject: Re: FW: Linux Applications Over PPP
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
rod person wrote:
> here is my ppp.conf. also try using ppxp from the ports, which is
what I use in X.
> either way I have no problems
>
> Rod
My ppp.conf file is pretty much identical to yours, the only difference
being that I don't have the "ident user-ppp VERSION (built
COMPILATIONDATE)" line. I tried inserting this into my ppp.conf, but it
generated an error.
I suspect the problem is not in my ppp.conf file - I think it is more
subtle. For some bizarre reason, Linux apps don't seem to recognise my
tun0 interface...
John.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 2:57: 3 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from tungsten.btinternet.com (tungsten.btinternet.com [194.73.73.81])
by hub.freebsd.org (Postfix) with ESMTP id 607C137B401
for <freebsd-hackers@freebsd.org>; Fri, 29 Jun 2001 02:57:00 -0700 (PDT)
(envelope-from john.toon@btinternet.com)
Received: from host213-122-174-93.btinternet.com ([213.122.174.93] helo=btinternet.com)
by tungsten.btinternet.com with esmtp (Exim 3.22 #9)
id 15Fv1G-0006rQ-00
for freebsd-hackers@freebsd.org; Fri, 29 Jun 2001 10:56:58 +0100
Message-ID: <3B3C5F0E.9000704@btinternet.com>
Date: Fri, 29 Jun 2001 10:57:18 +0000
From: John Toon <john.toon@btinternet.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.1-RELEASE i386; en-US; rv:0.9.1) Gecko/20010621
X-Accept-Language: en-us
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
Subject: Re: FW: Linux Applications Over PPP
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
rod person wrote:
> here is my ppp.conf. also try using ppxp from the ports, which is
what I use in X.
> either way I have no problems
>
> Rod
My ppp.conf file is pretty much identical to yours, the only difference
being that I don't have the "ident user-ppp VERSION (built
COMPILATIONDATE)" line. I tried inserting this into my ppp.conf, but it
generated an error.
I suspect the problem is not in my ppp.conf file - I think it is more
subtle. For some bizarre reason, Linux apps don't seem to recognise my
tun0 interface...
John.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 2:58:58 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from tungsten.btinternet.com (tungsten.btinternet.com [194.73.73.81])
by hub.freebsd.org (Postfix) with ESMTP id 82F1B37B405
for <freebsd-hackers@freebsd.org>; Fri, 29 Jun 2001 02:58:53 -0700 (PDT)
(envelope-from john.toon@btinternet.com)
Received: from host213-122-174-93.btinternet.com ([213.122.174.93] helo=btinternet.com)
by tungsten.btinternet.com with esmtp (Exim 3.22 #9)
id 15Fv36-00070K-00
for freebsd-hackers@freebsd.org; Fri, 29 Jun 2001 10:58:52 +0100
Message-ID: <3B3C5F80.3020706@btinternet.com>
Date: Fri, 29 Jun 2001 10:59:12 +0000
From: John Toon <john.toon@btinternet.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.1-RELEASE i386; en-US; rv:0.9.1) Gecko/20010621
X-Accept-Language: en-us
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
Subject: Linux Applications Over PPP
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi,
Six million *.rpm files later, I've finally got the Linux version of
Mozilla working properly. However, neither the Linux versions of Mozilla
or Opera seem to be able use my PPP connection - they simply can't
connect to anything, even when I'm fully connected and browsing using
the FreeBSD version of Mozilla.
Why is this? What setting do I need to alter to enable Linux apps to use
my PPP connection?
Regards,
John.
ppp.conf (username/password hashed out!):
#################################################################
# PPP Sample Configuration File
# Originally written by Toshiharu OHNO
# Simplified 5/14/1999 by wself@cdrom.com
#
# $FreeBSD: src/etc/ppp/ppp.conf,v 1.2 1999/08/27 23:24:08 peter Exp $
#################################################################
default:
#
# Make sure that "device" references the correct serial port
# for your modem. (cuaa0 = COM1, cuaa1 = COM2)
#
set device /dev/cuaa0
set log Phase Chat LCP IPCP CCP tun command
set speed 57600
set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK-AT-OK
ATE1Q0M0 OK \\dATDT\\T TIMEOUT 40 CONNECT"
set timeout 120
set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
add default HISADDR
enable dns
anytime:
set phone 08089933001
set authname ####
set authkey ####
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 5:35:41 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20])
by hub.freebsd.org (Postfix) with ESMTP id 73CF437B40B
for <freebsd-hackers@freebsd.org>; Fri, 29 Jun 2001 05:35:37 -0700 (PDT)
(envelope-from dfr@nlsystems.com)
Received: from [62.49.251.130] (helo=herring.nlsystems.com)
by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2)
id 15FxUm-000Mt2-0K; Fri, 29 Jun 2001 12:35:36 +0000
Received: from herring (herring [10.0.0.2])
by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f5TCYK703458;
Fri, 29 Jun 2001 13:34:20 +0100 (BST)
(envelope-from dfr@nlsystems.com)
Date: Fri, 29 Jun 2001 13:34:19 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Nicolas Souchu <nsouch@fr.alcove.com>
Cc: <freebsd-hackers@freebsd.org>
Subject: Re: processes private data
In-Reply-To: <20010629110607.B19935@avon.alcove-fr>
Message-ID: <Pine.BSF.4.33.0106291329580.2969-100000@herring.nlsystems.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Fri, 29 Jun 2001, Nicolas Souchu wrote:
> On Thu, Jun 28, 2001 at 07:48:21PM +0100, Doug Rabson wrote:
> > On Thu, 28 Jun 2001, Nicolas Souchu wrote:
> >
> > > Hi folks,
> > >
> > > I have a char driver that must be opened by more than one process. The minor
> > > index is not sufficient for this. Is there any process private data (void *)
> > > in the devfs structure (or the opposite) I could point to with the minor index
> > > of my device?
> >
> > The only way I know of to do this is to get a new struct file with
> > falloc() and install your own fileops. You can then set p->p_dupfd to the
> > new file descriptor and return ENXIO. The caller will magically use the
> > new struct file. For an example, see streamsopen() in
> > sys/dev/streams/streams.c.
>
> Ok, it seems to do part of the job. But this won't change the content of the
> file struct. Does anything ensure that the f_data of the freshly allocated
> struct file won't be used by vfs? Is the new struct file only local to my
> device driver?
>
> Otherwise, I could write my own falloc() which would allocate a struct file
> compatible with the original one like this:
When you get a new struct file from falloc(), VFS has nothing to do with
it. As you can see from the streamsopen() code, you can change f_ops
(which by default points at &badfileops) and f_data (defaults to zero) to
point at your own functions and data.
The point is that you are creating a new file. The VFS-owned file which
ended up calling the open driver entrypoint will be discarded in favour of
your new one.
--
Doug Rabson Mail: dfr@nlsystems.com
Phone: +44 20 8348 6160
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 6:15:27 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [128.29.154.90])
by hub.freebsd.org (Postfix) with ESMTP id 9B4A537B409
for <freebsd-hackers@freebsd.org>; Fri, 29 Jun 2001 06:15:18 -0700 (PDT)
(envelope-from jandrese@mitre.org)
Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4])
by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id f5TDFE115672;
Fri, 29 Jun 2001 09:15:14 -0400 (EDT)
Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18])
by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id f5TDFDa17409;
Fri, 29 Jun 2001 09:15:13 -0400 (EDT)
Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub2.mitre.org with SMTP
id 7050686; Fri, 29 Jun 2001 09:15:11 -0400
Message-ID: <3B3C7F64.A4C5D7F0@mitre.org>
Date: Fri, 29 Jun 2001 09:15:16 -0400
From: Jason Andresen <jandrese@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jason Borkowsky <jcborkow@tcpns.com>
Cc: freebsd-hackers@freebsd.org
Subject: Re: Serial port control
References: <Pine.BSF.4.21.0106282024030.23341-100000@bemused.tcpns.com>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Jason Borkowsky wrote:
>
> > > I am looking to find a simple way to control a serial port through BSD
> > > (such as raising and lowering DTR for a specified duration). I thought I
> > > had it using ioctl() and wrote a simple program to test it, but it seems I
> > > don't have a full understanding of ioctl(). Does anyone know of any
> > > pre-written utilities I can use? Or where to get some really detailed
> > > information about ioctl()? Thanks!
>
> After several responses, I thought I had it. From a software point of
> view, my program, included below, works fine. But from a hardware point of
> view, the signals I am trying to lower, RTS and DTR, are staying
> high. Can anyone try to compile the below program and do a serial port
> test with an RS-232 tester and see if anyone actually sees RTS and DTR
> going low? Sorry for bothering everyone with this again, but this is
> driving me nuts and I can't figure out the problem now. Thanks!
<Nausicaa/p0> (77 ~): gcc -o serialioctl serialioctl.c
<Nausicaa/p0> (78 ~): sudo ./serialioctl
Password:
Current Serial Settings: Ring RTS DTR DSR
Current Serial Settings: Ring DSR
<Nausicaa/p0> (79 ~): uname -a
FreeBSD Nausicaa.mitre.org 4.3-RC FreeBSD 4.3-RC #2: Tue Apr 10 10:50:19
EDT 2001 root@Nausicaa.mitre.org:/usr/obj/usr/src/sys/NAUSICAA i386
Seems to work for me.
--
\ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org
|\/ | | | / _| Network and Distributed Systems Engineer
_| _|___| _| _|_\___| Office: 703-883-7755
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 6:43: 9 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9])
by hub.freebsd.org (Postfix) with ESMTP id 9489637B406
for <freebsd-hackers@freebsd.org>; Fri, 29 Jun 2001 06:43:06 -0700 (PDT)
(envelope-from julian@elischer.org)
Received: from elischer.org (InterJet.elischer.org [192.168.1.1])
by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id IAA98603;
Fri, 29 Jun 2001 08:14:08 -0700 (PDT)
Message-ID: <3B3C198F.F21EABB3@elischer.org>
Date: Thu, 28 Jun 2001 23:00:47 -0700
From: Julian Elischer <julian@elischer.org>
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386)
X-Accept-Language: en, hu
MIME-Version: 1.0
To: Nicolai Petri <freebsd@petri.cc>
Cc: freebsd-hackers@freebsd.org
Subject: Re: An netgraph firewall module ? Is this possible / good performing ?
References: <008e01c0fafd$034e8000$8632a8c0@atomic.dk>
Content-Type: text/plain; charset=iso-8859-2
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Nicolai Petri wrote:
>
> Hi hackers,
>
> I've used some time writing a custom natd like daemon which makes som
> speciel packet processing.
> One of the issues with the natd approach is the large amount of
> context-switches it gives.
> This can be a real performance problem on very loaded networks. Would it be
> possible to do this with netgraph instead. And what is the pro's and con's
> for this approach.
>
> As a second step in developement how should protocol verification
> (ftp/smtp/whatever) be added to a netgraph firewall approach in a structured
> and dynamic extendable way ?
Unfortunatly, the netgraph code does not have a hook into the IP
code so at this time you cannot pass packets into the
IP protocol and have them then go to netgraph.
You could however put a filter onto the ethernet interface, but then you'd have
to take into account the 14 byte header too.
>
> Best regards,
> Nicolai Petri
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
--
+------------------------------------+ ______ _ __
| __--_|\ Julian Elischer | \ U \/ / hard at work in
| / \ julian@elischer.org +------>x USA \ a very strange
| ( OZ ) \___ ___ | country !
+- X_.---._/ presently in San Francisco \_/ \\
v
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 7:41: 2 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from smtpproxy1.mitre.org (mb-20-100.mitre.org [129.83.20.100])
by hub.freebsd.org (Postfix) with ESMTP id C975737B408
for <freebsd-hackers@freebsd.org>; Fri, 29 Jun 2001 07:40:57 -0700 (PDT)
(envelope-from jandrese@mitre.org)
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id f5TEeiD23089;
Fri, 29 Jun 2001 10:40:45 -0400 (EDT)
Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18])
by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id f5TEehX25492;
Fri, 29 Jun 2001 10:40:43 -0400 (EDT)
Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub2.mitre.org with SMTP
id 7052458; Fri, 29 Jun 2001 10:40:41 -0400
Message-ID: <3B3C936E.81C0B23B@mitre.org>
Date: Fri, 29 Jun 2001 10:40:46 -0400
From: Jason Andresen <jandrese@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jason Borkowsky <jcborkow@tcpns.com>, roam@orbitel.bg,
freebsd-hackers@freebsd.org
Subject: Re: Serial port control
References: <Pine.BSF.4.21.0106291019200.25917-100000@bemused.tcpns.com>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Jason Borkowsky wrote:
>
> > <Nausicaa/p0> (77 ~): gcc -o serialioctl serialioctl.c
> > <Nausicaa/p0> (78 ~): sudo ./serialioctl
> > Password:
> > Current Serial Settings: Ring RTS DTR DSR
> > Current Serial Settings: Ring DSR
> > <Nausicaa/p0> (79 ~): uname -a
> > FreeBSD Nausicaa.mitre.org 4.3-RC FreeBSD 4.3-RC #2: Tue Apr 10 10:50:19
> > EDT 2001 root@Nausicaa.mitre.org:/usr/obj/usr/src/sys/NAUSICAA i386
>
> I get the identical output, but when I actually put a voltmeter on the
> serial port between DTR and GND, the voltage does not change.
Sorry, I misread your original message. I thought you were saying the
ioctls were returning cleanly but not changing the state of the ports.
Nevermind then.
--
\ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org
|\/ | | | / _| Network and Distributed Systems Engineer
_| _|___| _| _|_\___| Office: 703-883-7755
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 7:55:46 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from imo-r02.mx.aol.com (imo-r02.mx.aol.com [152.163.225.98])
by hub.freebsd.org (Postfix) with ESMTP id 4147837B407
for <hackers@freebsd.org>; Fri, 29 Jun 2001 07:55:44 -0700 (PDT)
(envelope-from Bsdguru@aol.com)
Received: from Bsdguru@aol.com
by imo-r02.mx.aol.com (mail_out_v31.6.) id n.102.53e94e2 (4240)
for <hackers@freebsd.org>; Fri, 29 Jun 2001 10:55:40 -0400 (EDT)
From: Bsdguru@aol.com
Message-ID: <102.53e94e2.286df0eb@aol.com>
Date: Fri, 29 Jun 2001 10:55:39 EDT
Subject: Re: Status of encryption hardware support in FreeBSD
To: hackers@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 5.0 for Windows sub 138
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In a message dated 6/28/01 11:16:31 PM Eastern Daylight Time,
louie@TransSys.COM writes:
> Really? Have you even looked at the net4501 board which was mentioned?
It's
> a single-board computer constructed for some specific communication
> applications, with no VGA or keyboard support, or spinning fans, and is
> pretty inexpensive and in a very small form factor. Why do I want to
> replace this with "a new motherboard?"
Because my motherboard is 20 times faster, has VGA support,doesnt require an
add-on board to do fast encryption and costs about the same as yours. Thats
why.
Bryan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 8: 1: 3 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13])
by hub.freebsd.org (Postfix) with SMTP id 84ADC37B408
for <hackers@freebsd.org>; Fri, 29 Jun 2001 08:00:44 -0700 (PDT)
(envelope-from roam@orbitel.bg)
Received: (qmail 1137 invoked by uid 1000); 29 Jun 2001 15:05:13 -0000
Date: Fri, 29 Jun 2001 18:05:13 +0300
From: Peter Pentchev <roam@orbitel.bg>
To: Bsdguru@aol.com
Cc: hackers@freebsd.org
Subject: Re: Status of encryption hardware support in FreeBSD
Message-ID: <20010629180513.C535@ringworld.oblivion.bg>
Mail-Followup-To: Bsdguru@aol.com, hackers@freebsd.org
References: <102.53e94e2.286df0eb@aol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <102.53e94e2.286df0eb@aol.com>; from Bsdguru@aol.com on Fri, Jun 29, 2001 at 10:55:39AM -0400
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Fri, Jun 29, 2001 at 10:55:39AM -0400, Bsdguru@aol.com wrote:
> In a message dated 6/28/01 11:16:31 PM Eastern Daylight Time,
> louie@TransSys.COM writes:
>
> > Really? Have you even looked at the net4501 board which was mentioned?
> It's
> > a single-board computer constructed for some specific communication
> > applications, with no VGA or keyboard support, or spinning fans, and is
> > pretty inexpensive and in a very small form factor. Why do I want to
> > replace this with "a new motherboard?"
>
> Because my motherboard is 20 times faster, has VGA support,doesnt require an
> add-on board to do fast encryption and costs about the same as yours. Thats
> why.
Again, you are only considering your personal case. If crypto should
be needed on an embedded appliance, I don't think they would need
a lightning-fast processor and VGA support, when crypto is all
they want.
G'luck,
Peter
--
"yields falsehood, when appended to its quotation." yields falsehood, when appended to its quotation.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 8: 5:33 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66])
by hub.freebsd.org (Postfix) with ESMTP id A5D8437B40A
for <freebsd-hackers@FreeBSD.ORG>; Fri, 29 Jun 2001 08:05:27 -0700 (PDT)
(envelope-from nate@yogotech.com)
Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131])
by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id JAA08546;
Fri, 29 Jun 2001 09:05:25 -0600 (MDT)
(envelope-from nate@nomad.yogotech.com)
Received: (from nate@localhost)
by nomad.yogotech.com (8.8.8/8.8.8) id JAA02231;
Fri, 29 Jun 2001 09:05:25 -0600 (MDT)
(envelope-from nate)
From: Nate Williams <nate@yogotech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15164.39221.111336.661501@nomad.yogotech.com>
Date: Fri, 29 Jun 2001 09:05:25 -0600 (MDT)
To: Arun Sharma <arun@sharmas.dhs.org>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: NGPT 1.0.0 port to freebsd
In-Reply-To: <20010629010159.A8557@sharmas.dhs.org>
References: <20010629010159.A8557@sharmas.dhs.org>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Reply-To: nate@yogotech.com (Nate Williams)
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
[ It would have been helpful to have a one-line description of what NGPT
is at the top of this, rather than requiring the folks to go to a URL. ]
> - The main point of this port is to have a reasonable native freebsd
> pthread implementation till the scheduler activations stuff is ready.
With the current license, this won't be installed as part of the base
kernel. (GPL and/or LGPL)
> - Java heads: does this help to pass the JCK ?
Nope. I suspect we could pass the JCK/TCK today, but we haven't run the
tests yet due to legal reasons.
> Is that the main reason
> we can't have a binary FreeBSD JDK distribution ? I've read -java for
> several months now and I still can't find the answer.
It's been answered time and time again over the past months, so you must
not be paying attention. The binary distribution hasn't been created
because we don't have a legal license to do so (yet). However, there is
(and has been) ongoing work with Sun to get something in place. The
BSDi->WindRiver acquisition did *NOT* help things, as it forced us to
start over from scratch as a number of folks at WindRiver who were
aiding the Java team are no longer involved (as they were laid off).
In summary, a Java binary distribution of JDK1.2.2 will come out *very
soon* after a usable license with Sun has been signed. Hopefully, we'll
have a JDK1.3 binary distribution soon after, as Greg Lewis has made
alot of progress on it and has it limping along right now.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 8:20:11 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3])
by hub.freebsd.org (Postfix) with ESMTP
id 24F6F37B401; Fri, 29 Jun 2001 08:19:55 -0700 (PDT)
(envelope-from eddy+public+spam@noc.everquick.net)
Received: from localhost (eddy@localhost)
by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f5TFJmY08950;
Fri, 29 Jun 2001 15:19:48 GMT
X-EverQuick-No-Abuse: Report any e-mail abuse to <abuse@noc.everquick.net>
Date: Fri, 29 Jun 2001 15:19:47 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: Terry Lambert <tlambert2@mindspring.com>
Cc: Chris Costello <chris@calldei.com>, freebsd-smp@FreeBSD.ORG,
freebsd-hackers@FreeBSD.ORG
Subject: Re: libc_r locking... why?
In-Reply-To: <3B3C3346.E5496485@mindspring.com>
Message-ID: <Pine.LNX.4.20.0106291334350.7587-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
(Warning: rather long message)
> Date: Fri, 29 Jun 2001 00:50:30 -0700
> From: Terry Lambert <tlambert2@mindspring.com>
>
> [ ... wrapped fd using functions in libc_r ... ]
[ fd locking, to prevent chopping feet from beneath ]
As-needed serialization to prevent breakage = "proper" behavior.
I should have been more clear.
> The threads scheduler is in user space. It converts a
> blobking call into a non-blocking call plus a context
> switch. THus blocking _IS_ a problem.
Bad wording on my part again; perhaps "a problem that I [think
that] I have handled" is better. I'm use nb calls if possible;
else I have a long-running worker thread.
After my recent question regarding AIO, it looks like it's time
to bite the bullet and use that as well.
> [ ... thinking that pthreads used multiple processes ... ]
>
> This is not the case.
So I've learned. I'm glad that I didn't use pthreads, then. :-)
> The user space threads library does what the original
> idea of threads was intended to do, before people started
> treating it as the only hammer they had to pound on the
> SMP problem with in order to achieve SMP scalability: it
> utilizes the full quantum of the process, and minimizes
> context switch overhead. Kernel threads don't do either
> of these things well, in almost all existing implementations
> out there.
Agreed on all counts.
I'm tempted to continue eschewing the pthread library. I've
unrolled code, and store state info in a purpose-specific FSM
control block. Maybe I reinvented the wheel, but it wasn't
that difficult.
> > Am I correct that libc_r does _not_ use multiple processes
> > to create threads?
>
> Yes. All threads run in a single process. The threads
> are not intended as a workaround for the SMP scalability
> problem.
A good thing, IMHO.
I was starting to look at libc_r to check my work; I _prefer_
launching multiple processess for SMP scalability, and having an
untainted threading model.
> Note that you are not going to be able to combine your
> rfork approach with this, if your resulting processes
> end up running on different CPUs: this is because the
Running processes on multiple CPUs is one goal.
[ libc_r locks don't assert "lock", not MP-safe ]
So the "lock" prefix is the only way to enforce cache coherency?
Do you have handy a good reference on IPIs, other than the kernel
APIC code (and, of course, Google and NorthernLight searches)?
Good to know, but, I'm not using libc_r... I was looking at
existing code to help me double-check mine as I go. I'm
synchronizing processes with a "giant lock" token that each
process cooperatively passes to the next... to simplify:
who_has_lock++ ;
who_has_lock %= process_count ;
Each processes' critical path first checks to see if it holds
the token; if so, it performs the tasks that require it, such as
locking a finer-grained lock or mutex. It then passes the token,
and continues through its critical path.
If a thread has nothing to do, I nanosleep(2) to prevent the critical
path from degenerating to an extended spin. I'm considering using
socketpair(2)s, with a process blocking indefinitely on read(2) until
another process write(2)s to awaken it...
> If you "need" kernel threads, look at the Linux kernel
> threads in the ports collection (it's a kernel module
> that builds and installs as a package). You probably
> don't, since performance of kernel threads is really only
Correct me if I'm wrong, but the only place in my model that really
might benefit from kthreads would be the scheduling? i.e., rather
than screwing around with nanosleep(2) or socket calls, I could cut
the cruft and interact more directly with the scheduler via kthread
mechanisms?
> about a 20% increment, if you implement them the SVR4 or
> Solaris (pre-2.7) or Linux way. It's probably better to
> implement with FreeBSD threads as they currently exist,
> and get massive SMP scalability when KSE's are brought
> into the source tree.
KSEs... where can I read up?
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc.
EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 8:24:47 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from hotmail.com (f81.law11.hotmail.com [64.4.17.81])
by hub.freebsd.org (Postfix) with ESMTP id D3CB337B406
for <freebsd-hackers@freebsd.org>; Fri, 29 Jun 2001 08:24:42 -0700 (PDT)
(envelope-from part_lion@hotmail.com)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
Fri, 29 Jun 2001 08:24:42 -0700
Received: from 208.254.3.3 by lw11fd.law11.hotmail.msn.com with HTTP; Fri, 29 Jun 2001 15:24:42 GMT
X-Originating-IP: [208.254.3.3]
From: "Joesh Juphland" <part_lion@hotmail.com>
To: nsayer@quack.kfu.com, julian@elischer.org,
freebsd-hackers@freebsd.org
Subject: Re: bridging with pcmcia cards
Date: Fri, 29 Jun 2001 09:24:42 -0600
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F81llNY30kkZIhTrBoe0000a092@hotmail.com>
X-OriginalArrivalTime: 29 Jun 2001 15:24:42.0599 (UTC) FILETIME=[9EC3BF70:01C100AF]
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
thank you - this was helpful. One last question - when you say that
bridging cannot work with wi cards because they do not support promiscuous
transmission, this makes me wonder two things:
1. Do you mean the wi driver does not support this, or you mean the actual
physical card itself is limited in this way
2. I know that there are two major firmware differences between "old" lucent
cards and "new" lucent cards, and that is that the old ones can be
_actually_ set to SSID of "" and then pick up base station in range. Is it
possible that (if the answer to #1 above is "it's a hardware problem") that
the old revision cards are better at this, or are they all like this ?
thanks a lot. I was actually _only_ interested in just plain old options
BRIDGE bridging, and not being a virtual AP (so far).
>Julian Elischer wrote:
>
>>bridging is not a function of it being a pc-card..
>
>
>This is true, particularly with netgraph bridging.
>
>
>>actually bridging may already work with wi cards
>>also netgraph bridgiung may also work...
>>
>
>
>Bridging cannot work with wi cards, since they do not support
>promiscuous transmission (that is, sending frames with other than their
>own MAC address). Moreover, anyone seriously desiring to bridge wi cards
>very likely wants to actually do something that is more than bridging --
>they probably want to be an access point (ala Apple's "virtual airport"
>functionality). The difference between that and just bridging is that
>the wireless clients can see each other with certainty (that is, no
>hidden node issues) and they can turn on power saving (that is, having
>the receiver duty cycle be less than 100%).
>
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-hackers" in the body of the message
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 8:29:47 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13])
by hub.freebsd.org (Postfix) with SMTP id CD6CA37B401
for <freebsd-hackers@FreeBSD.ORG>; Fri, 29 Jun 2001 08:29:25 -0700 (PDT)
(envelope-from roam@orbitel.bg)
Received: (qmail 3303 invoked by uid 1000); 29 Jun 2001 15:33:52 -0000
Date: Fri, 29 Jun 2001 18:33:52 +0300
From: Peter Pentchev <roam@orbitel.bg>
To: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
Cc: Terry Lambert <tlambert2@mindspring.com>,
Chris Costello <chris@calldei.com>, freebsd-smp@FreeBSD.ORG,
freebsd-hackers@FreeBSD.ORG
Subject: Re: libc_r locking... why?
Message-ID: <20010629183352.D535@ringworld.oblivion.bg>
Mail-Followup-To: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>,
Terry Lambert <tlambert2@mindspring.com>,
Chris Costello <chris@calldei.com>, freebsd-smp@FreeBSD.ORG,
freebsd-hackers@FreeBSD.ORG
References: <3B3C3346.E5496485@mindspring.com> <Pine.LNX.4.20.0106291334350.7587-100000@www.everquick.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.LNX.4.20.0106291334350.7587-100000@www.everquick.net>; from eddy+public+spam@noc.everquick.net on Fri, Jun 29, 2001 at 03:19:47PM +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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Fri, Jun 29, 2001 at 03:19:47PM +0000, E.B. Dreger wrote:
> > The threads scheduler is in user space. It converts a
> > blobking call into a non-blocking call plus a context
> > switch. THus blocking _IS_ a problem.
>
> Bad wording on my part again; perhaps "a problem that I [think
> that] I have handled" is better. I'm use nb calls if possible;
> else I have a long-running worker thread.
I hope you understand that when the worker thread blocks,
it's the process that blocks, and none of the other threads
can run until the end of the syscall.
> After my recent question regarding AIO, it looks like it's time
> to bite the bullet and use that as well.
G'luck,
Peter
--
If this sentence were in Chinese, it would say something else.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 8:44:16 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3])
by hub.freebsd.org (Postfix) with ESMTP
id D593537B403; Fri, 29 Jun 2001 08:44:08 -0700 (PDT)
(envelope-from eddy+public+spam@noc.everquick.net)
Received: from localhost (eddy@localhost)
by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f5TFi4D09415;
Fri, 29 Jun 2001 15:44:04 GMT
X-EverQuick-No-Abuse: Report any e-mail abuse to <abuse@noc.everquick.net>
Date: Fri, 29 Jun 2001 15:44:03 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: Peter Pentchev <roam@orbitel.bg>
Cc: Terry Lambert <tlambert2@mindspring.com>,
Chris Costello <chris@calldei.com>, freebsd-smp@FreeBSD.ORG,
freebsd-hackers@FreeBSD.ORG
Subject: Re: libc_r locking... why?
In-Reply-To: <20010629183352.D535@ringworld.oblivion.bg>
Message-ID: <Pine.LNX.4.20.0106291534530.9285-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> Date: Fri, 29 Jun 2001 18:33:52 +0300
> From: Peter Pentchev <roam@orbitel.bg>
>
> > > The threads scheduler is in user space. It converts a
> > > blobking call into a non-blocking call plus a context
> > > switch. THus blocking _IS_ a problem.
> >
> > Bad wording on my part again; perhaps "a problem that I [think
> > that] I have handled" is better. I'm use nb calls if possible;
> > else I have a long-running worker thread.
>
> I hope you understand that when the worker thread blocks,
> it's the process that blocks, and none of the other threads
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Yes.
> it's the process that blocks, and none of the other threads
^^^^^^^^^^^^^^^^^^^^^^^^^
> can run until the end of the syscall.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Again, I am *not* using pthreads. Worker thread = totally separate
process, created via rfork(2). One process blocks, others continue
running.
To reiterate: I'm *not* using pthreads or libc_r. I wanted to check my
work, and began looking at libc_r code, under the faulty ass-umption that
it ran multiple processes.
Now that I know that threads are implemented in a single process, and that
blocking calls are thunked to non-blocking calls, the locking that I
originally questioned makes sense.
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc.
EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 10:22:10 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119])
by hub.freebsd.org (Postfix) with ESMTP id BC3E837B403
for <freebsd-hackers@FreeBSD.ORG>; Fri, 29 Jun 2001 10:22:07 -0700 (PDT)
(envelope-from adsharma@sharmas.dhs.org)
Received: by sharmas.dhs.org (Postfix, from userid 500)
id 32B495E06E; Fri, 29 Jun 2001 10:22:14 -0700 (PDT)
Date: Fri, 29 Jun 2001 10:22:14 -0700
From: Arun Sharma <arun@sharmas.dhs.org>
To: Nate Williams <nate@yogotech.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Java (Was Re: NGPT 1.0.0 port to freebsd)
Message-ID: <20010629102214.A10651@sharmas.dhs.org>
References: <20010629010159.A8557@sharmas.dhs.org> <15164.39221.111336.661501@nomad.yogotech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.15i
In-Reply-To: <15164.39221.111336.661501@nomad.yogotech.com>; from nate@yogotech.com on Fri, Jun 29, 2001 at 09:05:25AM -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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Fri, Jun 29, 2001 at 09:05:25AM -0600, Nate Williams wrote:
> With the current license, this won't be installed as part of the base
> kernel. (GPL and/or LGPL)
I understand it'll continue to be a port. Am I hearing that it is
unacceptable even as a temporary solution because of the license ?
> It's been answered time and time again over the past months, so you must
> not be paying attention. The binary distribution hasn't been created
> because we don't have a legal license to do so (yet).
Yes, I've been reading that for a long time now, but it (what Sun is
doing) doesn't make any sense to me. Are Sun's reasons
(a) Technical ? Passing of JCK etc ?
(b) Political ? Yet another competitor to Solaris ?
>From your posting it appears that it's technical (not passing JCK), as
well as political (not getting the license to run JCK). What is their
answer reg: blackdown.org doing the same ?
May be getting Zdnet to publish an article on this is the right way to
go ? The bug parades and votes didn't seem to help much.
> In summary, a Java binary distribution of JDK1.2.2 will come out *very
> soon* after a usable license with Sun has been signed. Hopefully, we'll
> have a JDK1.3 binary distribution soon after, as Greg Lewis has made
> alot of progress on it and has it limping along right now.
That's good to hear. Eagerly awaiting the news.
-Arun
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 10:36:33 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3])
by hub.freebsd.org (Postfix) with ESMTP
id B045437B403; Fri, 29 Jun 2001 10:36:26 -0700 (PDT)
(envelope-from eddy+public+spam@noc.everquick.net)
Received: from localhost (eddy@localhost)
by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f5THaQB11205;
Fri, 29 Jun 2001 17:36:26 GMT
X-EverQuick-No-Abuse: Report any e-mail abuse to <abuse@noc.everquick.net>
Date: Fri, 29 Jun 2001 17:36:25 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: freebsd-smp@freebsd.org, freebsd-hackers@freebsd.org
Subject: CPU affinity hinting
Message-ID: <Pine.LNX.4.20.0106291709100.10723-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
(Cross-posting again... I'm willing to be larted with a herring if this is
unacceptable for the content presented.)
I was thinking about CPU affinity on SMP systems.... the following is
on-list brainstorming.
Take a two-way box running 10 httpd and 10 smtpd processes. Assuming
equal CPU time requirements, it would make sense to bind httpd to one CPU,
and smtpd to the other. Simple, but not realistic.
Maybe smtpd requires more CPU time. Fine... limit one processor to smtpd,
run leftover smtpd on the other CPU, and run httpd _only_ on the processor
handling leftover smtpd.
Or consider ten instances of a single program that uses four processes,
sort of like squid * 10: It would make more sense to have similar
processes grouped on the same CPU.
After watching processes switch CPUs via "top", I got to thinking... could
there be, and would it be useful to have, a mechanism where processes
could tell the kernel "my magic number is 6819732", and the kernel would
try to keep all processes with said magic number on the same CPU?
Is this "solution" worse than the problem (cache thrash and switching
CPUs)?
I suppose that the kernel could do a quick, numerically-simple hash of the
ELF metadata, as opposed to program-specified magic. This would handle
the httpd/smtpd case, with less fear of magic number collisions, but not
rfork(2)ed threads.
Or, instead of hashing ELF metadata, the kernel could compute a hash
based on all IP ports bind(2)ed by the program within the first few
seconds of operation. (Obviously unsuitable for short-lived programs,
but those could probably be handled via least-busy CPU assignment.)
Perhaps a hybrid approach:
cpu_hint = hash(elf_metadata, hint) % num_cpus ;
where "hint" is specified by the process in a group?
Thoughts? Criticisms? Flames? Beatings with a stinky fish?
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc.
EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 10:45:22 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66])
by hub.freebsd.org (Postfix) with ESMTP id 34E3137B403
for <freebsd-hackers@FreeBSD.ORG>; Fri, 29 Jun 2001 10:45:14 -0700 (PDT)
(envelope-from nate@yogotech.com)
Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131])
by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id LAA11201;
Fri, 29 Jun 2001 11:45:08 -0600 (MDT)
(envelope-from nate@nomad.yogotech.com)
Received: (from nate@localhost)
by nomad.yogotech.com (8.8.8/8.8.8) id LAA02942;
Fri, 29 Jun 2001 11:45:08 -0600 (MDT)
(envelope-from nate)
From: Nate Williams <nate@yogotech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15164.48804.197019.760751@nomad.yogotech.com>
Date: Fri, 29 Jun 2001 11:45:08 -0600 (MDT)
To: Arun Sharma <arun@sharmas.dhs.org>
Cc: Nate Williams <nate@yogotech.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: Java (Was Re: NGPT 1.0.0 port to freebsd)
In-Reply-To: <20010629102214.A10651@sharmas.dhs.org>
References: <20010629010159.A8557@sharmas.dhs.org>
<15164.39221.111336.661501@nomad.yogotech.com>
<20010629102214.A10651@sharmas.dhs.org>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Reply-To: nate@yogotech.com (Nate Williams)
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> > With the current license, this won't be installed as part of the base
> > kernel. (GPL and/or LGPL)
>
> I understand it'll continue to be a port. Am I hearing that it is
> unacceptable even as a temporary solution because of the license ?
>
> > It's been answered time and time again over the past months, so you must
> > not be paying attention. The binary distribution hasn't been created
> > because we don't have a legal license to do so (yet).
>
> Yes, I've been reading that for a long time now, but it (what Sun is
> doing) doesn't make any sense to me. Are Sun's reasons
>
> (a) Technical ? Passing of JCK etc ?
> (b) Political ? Yet another competitor to Solaris ?
Sun is very picky about the license they want to give us. In
particular, due to a recent fight in court they had with an well-known
company in the Pacific Northwest, the type of license they are proposing
protects them from just about everything, but doesn't give us enough
lee-way to actually distribute the license.
The difficulty has been trying to appease Sun's lawyers w/out overlying
restricting the team's ability to create and maintain the JDK long-term.
(In other words, we don't want to have to go through this over and over
again for each new JDK release).
> >From your posting it appears that it's technical (not passing JCK),
Passing the JCK/TCK is simply an excercise that we haven't done yet.
Basically, once you pass the TCK, you must ship the *EXACT* version of
the binary without any modifications. Since we are still doing
development of the port, it seemed a waste of time to run the TCK when
we may have to run it again if/when the license is signed. (Running the
TCK is a long, drawn out process that one doesn't want to repeat if at
all possible.)
> well as political (not getting the license to run JCK). What is their
> answer reg: blackdown.org doing the same ?
Blackdown was given access to the JDK before the recent lawsuit, and as
such has 'special' privileges that they are no longer willing to grant
to new licensees.
> May be getting Zdnet to publish an article on this is the right way to
> go ? The bug parades and votes didn't seem to help much.
Actually, it's the reason that Sun is doing the dance with us right
now. The whole Java affair has been a series of mis-steps by all
parties (myself, BSDi, and Sun), so no one party shares the entire
blame. The most recent issue was the BSDi/WindRiver acquisition, which
left us w/out any legal advisors (unless we wanted to pay out of the
pocket, which would have cost upwards of $2K to solve, not something I
can affort).
We're hoping to have something for you in the near future.
Unfortunately, my Sun contact went on vacation yesterday before I could
get some stuff ironed out, and when he gets back from vacation, I'm
going on vacation, so nothing can get done with this for at least
another month.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 11:33:24 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106])
by hub.freebsd.org (Postfix) with ESMTP
id 41CEF37B403; Fri, 29 Jun 2001 11:33:16 -0700 (PDT)
(envelope-from ticso@mail.cicely.de)
Received: from mail.cicely.de (cicely20 [10.1.1.22])
by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f5TIXD658164;
Fri, 29 Jun 2001 20:33:13 +0200 (CEST)
Received: (from ticso@localhost)
by mail.cicely.de (8.11.0/8.11.0) id f5TIXvJ17293;
Fri, 29 Jun 2001 20:33:57 +0200 (CEST)
Date: Fri, 29 Jun 2001 20:33:51 +0200
From: Bernd Walter <ticso@mail.cicely.de>
To: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
Cc: Peter Pentchev <roam@orbitel.bg>,
Terry Lambert <tlambert2@mindspring.com>,
Chris Costello <chris@calldei.com>, freebsd-smp@FreeBSD.ORG,
freebsd-hackers@FreeBSD.ORG
Subject: Re: libc_r locking... why?
Message-ID: <20010629203351.A16557@cicely20.cicely.de>
References: <20010629183352.D535@ringworld.oblivion.bg> <Pine.LNX.4.20.0106291534530.9285-100000@www.everquick.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.LNX.4.20.0106291534530.9285-100000@www.everquick.net>; from eddy+public+spam@noc.everquick.net on Fri, Jun 29, 2001 at 03:44:03PM +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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Fri, Jun 29, 2001 at 03:44:03PM +0000, E.B. Dreger wrote:
> Again, I am *not* using pthreads. Worker thread = totally separate
> process, created via rfork(2). One process blocks, others continue
> running.
I can't see how you make shure that on SMP systems all CPUs have
the same meaning from memory content.
Normaly you would use a mutex or similar before accessing a data range
from another thread which also enshures that the CPU specific caches
and buffers are syncronised.
If you don't do this it may happen that you write a variable and
another thread uses this variable using another CPU before the first
CPU has writen this memory seeable for others and works with an
outdated content.
A fresh rforked process with the same virtual memory should at least see
the version at the time of the rfork, so there is no problem if you
don't modify the common used content after rfork.
--
B.Walter COSMO-Project http://www.cosmo-project.de
ticso@cicely.de Usergroup info@cosmo-project.de
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 11:44:51 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3])
by hub.freebsd.org (Postfix) with ESMTP
id 3C2BF37B401; Fri, 29 Jun 2001 11:44:45 -0700 (PDT)
(envelope-from eddy+public+spam@noc.everquick.net)
Received: from localhost (eddy@localhost)
by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f5TIiXI12135;
Fri, 29 Jun 2001 18:44:33 GMT
X-EverQuick-No-Abuse: Report any e-mail abuse to <abuse@noc.everquick.net>
Date: Fri, 29 Jun 2001 18:44:29 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: Bernd Walter <ticso@mail.cicely.de>
Cc: Peter Pentchev <roam@orbitel.bg>,
Terry Lambert <tlambert2@mindspring.com>,
Chris Costello <chris@calldei.com>, freebsd-smp@FreeBSD.ORG,
freebsd-hackers@FreeBSD.ORG
Subject: Re: libc_r locking... why?
In-Reply-To: <20010629203351.A16557@cicely20.cicely.de>
Message-ID: <Pine.LNX.4.20.0106291838250.12068-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> Date: Fri, 29 Jun 2001 20:33:51 +0200
> From: Bernd Walter <ticso@mail.cicely.de>
>
> I can't see how you make shure that on SMP systems all CPUs have
> the same meaning from memory content.
> Normaly you would use a mutex or similar before accessing a data range
> from another thread which also enshures that the CPU specific caches
> and buffers are syncronised.
> If you don't do this it may happen that you write a variable and
> another thread uses this variable using another CPU before the first
> CPU has writen this memory seeable for others and works with an
> outdated content.
Passing a token between threads. When a thread has the token, it may
assert a lock or a mutex on an object. Again, I subscribe to threads
being lightweight; cooperative sharing is better than preemptive or trying
to grab a lock before another thread does.
Any good references on MP standard? Is the lock prefix the only way to
force cache coherency?
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc.
EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 12:17:52 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106])
by hub.freebsd.org (Postfix) with ESMTP
id 5B9AC37B405; Fri, 29 Jun 2001 12:17:44 -0700 (PDT)
(envelope-from ticso@mail.cicely.de)
Received: from mail.cicely.de (cicely20 [10.1.1.22])
by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f5TJHe658356;
Fri, 29 Jun 2001 21:17:42 +0200 (CEST)
Received: (from ticso@localhost)
by mail.cicely.de (8.11.0/8.11.0) id f5TJIO217420;
Fri, 29 Jun 2001 21:18:24 +0200 (CEST)
Date: Fri, 29 Jun 2001 21:18:18 +0200
From: Bernd Walter <ticso@mail.cicely.de>
To: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
Cc: Bernd Walter <ticso@mail.cicely.de>,
Peter Pentchev <roam@orbitel.bg>,
Terry Lambert <tlambert2@mindspring.com>,
Chris Costello <chris@calldei.com>, freebsd-smp@FreeBSD.ORG,
freebsd-hackers@FreeBSD.ORG
Subject: Re: libc_r locking... why?
Message-ID: <20010629211818.A17309@cicely20.cicely.de>
References: <20010629203351.A16557@cicely20.cicely.de> <Pine.LNX.4.20.0106291838250.12068-100000@www.everquick.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.LNX.4.20.0106291838250.12068-100000@www.everquick.net>; from eddy+public+spam@noc.everquick.net on Fri, Jun 29, 2001 at 06:44:29PM +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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Fri, Jun 29, 2001 at 06:44:29PM +0000, E.B. Dreger wrote:
> > Date: Fri, 29 Jun 2001 20:33:51 +0200
> > From: Bernd Walter <ticso@mail.cicely.de>
> >
> > I can't see how you make shure that on SMP systems all CPUs have
> > the same meaning from memory content.
> > Normaly you would use a mutex or similar before accessing a data range
> > from another thread which also enshures that the CPU specific caches
> > and buffers are syncronised.
> > If you don't do this it may happen that you write a variable and
> > another thread uses this variable using another CPU before the first
> > CPU has writen this memory seeable for others and works with an
> > outdated content.
>
> Passing a token between threads. When a thread has the token, it may
> assert a lock or a mutex on an object. Again, I subscribe to threads
> being lightweight; cooperative sharing is better than preemptive or trying
> to grab a lock before another thread does.
A Token may not be enough because writes may be reordered.
Usually a mutex is a lock with some kind of memory barrier.
If you can fetch the lock on a CPU you know that the CPU previous
owning the lock has flushed everything up to the point of coherence
of what was written until the lock was released.
Memory barriers and the read-modify-write operations (or locked
operations like on ALPHA) are accessible from user code - but I don't
know of any platform independend functions.
> Any good references on MP standard? Is the lock prefix the only way to
> force cache coherency?
A good explanation for this kind of thing was in "Programming with POSIX
Threads" in Chapter 3.4 "Memory visible between threads".
I know you are not usung pthreads but the memory problems are the same.
>
>
> Eddy
>
> ---------------------------------------------------------------------------
>
> Brotsman & Dreger, Inc.
> EverQuick Internet Division
>
> Phone: +1 (316) 794-8922 Wichita/(Inter)national
> Phone: +1 (785) 865-5885 Lawrence
>
> ---------------------------------------------------------------------------
>
> Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
> From: A Trap <blacklist@brics.com>
> To: blacklist@brics.com
> Subject: Please ignore this portion of my mail signature.
>
> These last few lines are a trap for address-harvesting spambots. Do NOT
> send mail to <blacklist@brics.com>, or you are likely to be blocked.
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
--
B.Walter COSMO-Project http://www.cosmo-project.de
ticso@cicely.de Usergroup info@cosmo-project.de
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 12:56:58 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3])
by hub.freebsd.org (Postfix) with ESMTP
id C049A37B401; Fri, 29 Jun 2001 12:56:47 -0700 (PDT)
(envelope-from eddy+public+spam@noc.everquick.net)
Received: from localhost (eddy@localhost)
by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f5TJue813575;
Fri, 29 Jun 2001 19:56:40 GMT
X-EverQuick-No-Abuse: Report any e-mail abuse to <abuse@noc.everquick.net>
Date: Fri, 29 Jun 2001 19:56:40 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: Bernd Walter <ticso@mail.cicely.de>
Cc: freebsd-smp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
Subject: Re: libc_r locking... why?
In-Reply-To: <20010629211818.A17309@cicely20.cicely.de>
Message-ID: <Pine.LNX.4.20.0106291940590.13439-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
(Personal CCs trimmed; back to Bernd and cross-posting -smp and -hackers)
> Date: Fri, 29 Jun 2001 21:18:18 +0200
> From: Bernd Walter <ticso@mail.cicely.de>
> > Passing a token between threads. When a thread has the token, it may
> > assert a lock or a mutex on an object. Again, I subscribe to threads
> > being lightweight; cooperative sharing is better than preemptive or
> > trying to grab a lock before another thread does.
>
> A Token may not be enough because writes may be reordered.
> Usually a mutex is a lock with some kind of memory barrier.
But it _is_ locked. The
thread_with_token++ ;
thread_with_token %= num_threads ;
was oversimplified. It's more like
xorl %ecx,%ecx
movl thread_with_token,%eax
incl %eax
cmpl %eax,num_threads
movzl %ecx,%eax
lock movl %eax,thread_with_token
to pass the token, where thread_with_token is in shared memory. Each
process does the above. When a process has the token, it's safe to claim
mutexes and such without worry of another thread (without token) accessing
simultaneously. Mutex/lock ops also have lock asserted.
If this is inadequate, then I need to do some head-scratching.
> If you can fetch the lock on a CPU you know that the CPU previous
> owning the lock has flushed everything up to the point of coherence
> of what was written until the lock was released.
Here is where I want to learn more about cache coherency, inter-processor
interrupts, and APIC programming. I'd imagine that the latter two are
lower-level than I'd be using, but I still want to know the "how and why"
beneath the scenes.
> Memory barriers and the read-modify-write operations (or locked
> operations like on ALPHA) are accessible from user code - but I don't
> know of any platform independend functions.
Nor do I.
> > Any good references on MP standard? Is the lock prefix the only way to
> > force cache coherency?
>
> A good explanation for this kind of thing was in "Programming with POSIX
> Threads" in Chapter 3.4 "Memory visible between threads".
I'll have to check it out. I [believe that I] understand about the
inherent races in SMP, but more reading is always better...
However, I'm still interested in x86-specific coherency mechanisms. Any
info?
> I know you are not usung pthreads but the memory problems are the same.
Correct. I just wanted to make certain that we were on the same page, no
pun intended.
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc.
EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 14:14:16 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3])
by hub.freebsd.org (Postfix) with ESMTP
id 36AFD37B405; Fri, 29 Jun 2001 14:14:09 -0700 (PDT)
(envelope-from eddy+public+spam@noc.everquick.net)
Received: from localhost (eddy@localhost)
by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f5TLE7U14825;
Fri, 29 Jun 2001 21:14:07 GMT
X-EverQuick-No-Abuse: Report any e-mail abuse to <abuse@noc.everquick.net>
Date: Fri, 29 Jun 2001 21:14:06 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: Matthew Rogers <matt@accelnet.net>
Cc: freebsd-smp@freebsd.org, freebsd-hackers@freebsd.org
Subject: RE: CPU affinity hinting
In-Reply-To: <002001c100d8$2c406c40$a2962640@bear>
Message-ID: <Pine.LNX.4.20.0106292104270.14702-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> Date: Fri, 29 Jun 2001 13:14:58 -0700
> From: Matthew Rogers <matt@accelnet.net>
>
> Why not just use First in line, Next processor available ? Then you
> wouldn't care what processor did which task.
That was my question: Would the added complexity of "CPU affinity
hinting" be worth the reduction in cache misses and switching processes,
by preventing long-running processes from constantly switching CPUs?
FILNPA is fine for short-lived processes, but longer-running ones switch
CPUs, perhaps unnecessarily.
> Hmm, maybe even have each processor a dedicated memory space, and
> programmable functionality.
>
> Oops, that's a Field Programmable Gate Array, and there going to make
> Legacy computing look stupid.
FPGAs, mmmm. Transputers, mmmm. Neuromatrix, mmmm.
> In my mind, you have a need for multiprocessing Non-specific and
> Specific tasking.
>
> In some ways we are multiprocessing anyway on some level. Videocard 3d
> processing, sound card.
You mean that Winmodems and main memory-based video aren't the keys to
high performance? You mean that Intel is being silly when they justify
faster chips by saying "now you can eliminate three $20 DSPs by buying
our latest architecture"? :-)
> So why do we need a GOD chip, ie the "chipset" controlling access to
> processors and busses ?
>
> That's because that's the way it was done before the 286.
>
> Time to leave the bus. :)
Arguably so from a hardware standpoint. But, in the mean time, I was
trying to think of ways to help SMP performance. :-)
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc.
EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 17:17:27 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from aries.ai.net (aries.ai.net [205.134.163.4])
by hub.freebsd.org (Postfix) with ESMTP
id 9F99137B403; Fri, 29 Jun 2001 17:17:20 -0700 (PDT)
(envelope-from deepak@ai.net)
Received: from blood (adsl-138-88-72-201.dc.adsl.bellatlantic.net [138.88.72.201])
by aries.ai.net (8.9.3/8.9.3) with SMTP id UAA28838;
Fri, 29 Jun 2001 20:19:23 -0400 (EDT)
(envelope-from deepak@ai.net)
Reply-To: <deepak@ai.net>
From: "Deepak Jain" <deepak@ai.net>
To: "Wes Peters" <wes@softweyr.com>,
"Ruslan Ermilov" <ru@FreeBSD.ORG>
Cc: <net@FreeBSD.ORG>, <hackers@FreeBSD.ORG>
Subject: RE: fastforwarding?
Date: Fri, 29 Jun 2001 20:21:11 -0400
Message-ID: <GPEOJKGHAMKFIOMAGMDIOEENDJAA.deepak@ai.net>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
In-Reply-To: <3B3AB4F8.184A2EFE@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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Thanks, this explanation is far more clear. It is much similar to fast
switching on a Cisco or similar piece of gear.
DJ
-----Original Message-----
From: owner-freebsd-hackers@FreeBSD.ORG
[mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Wes Peters
Sent: Thursday, June 28, 2001 12:39 AM
To: Ruslan Ermilov
Cc: Deepak Jain; net@FreeBSD.ORG; hackers@FreeBSD.ORG
Subject: Re: fastforwarding?
Ruslan Ermilov wrote:
>
> On Mon, Jun 25, 2001 at 06:47:41PM -0400, Deepak Jain wrote:
> > sysctl -A |grep forward
> > net.inet.ip.forwarding: 1
> > net.inet.ip.fastforwarding: 0
> > machdep.forward_irq_enabled: 1
> > machdep.forward_signal_enabled: 1
> > machdep.forward_roundrobin_enabled: 1
> >
> > What does the fastforwarding option do that the normal forwarding option
> > doesn't?
> >
> See inet(4).
The description there isn't very forthcoming. fastforwarding caches
the results of a route lookup for destination addresses that are not
on the local machine, and uses the cached route to short-circuit the
normal (relatively slow) route lookup process. The packet flows
directly from one layer2 input routine directly to the opposing
layer2 output routine without traversing the IP layer.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr
LLC
wes@softweyr.com
http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 18:39:31 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from RedDust.bluesky.net.au (CPE-61-9-143-86.vic.bigpond.net.au [61.9.143.86])
by hub.freebsd.org (Postfix) with ESMTP
id 8639F37B401; Fri, 29 Jun 2001 18:39:24 -0700 (PDT)
(envelope-from receiver@blueskybbs.yi.org)
Received: from localhost (receiver@localhost)
by RedDust.bluesky.net.au (8.11.4/8.11.0) with ESMTP id f5U1XJP08832;
Sat, 30 Jun 2001 11:33:20 +1000 (EST)
(envelope-from receiver@blueskybbs.yi.org)
Date: Sat, 30 Jun 2001 11:33:18 +1000 (EST)
From: Idea Receiver <receiver@blueskybbs.yi.org>
To: Terry Lambert <tlambert2@mindspring.com>
Cc: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>,
Chris Costello <chris@calldei.com>, freebsd-smp@FreeBSD.ORG,
freebsd-hackers@FreeBSD.ORG
Subject: Re: libc_r locking... why?
In-Reply-To: <3B3C3346.E5496485@mindspring.com>
Message-ID: <Pine.BSF.4.21.0106301129090.8701-100000@RedDust.BlueSky.net.au>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Fri, 29 Jun 2001, Terry Lambert wrote:
> "E.B. Dreger" wrote:
> If you "need" kernel threads, look at the Linux kernel
> threads in the ports collection (it's a kernel module
> that builds and installs as a package). You probably
> don't, since performance of kernel threads is really only
> about a 20% increment, if you implement them the SVR4 or
> Solaris (pre-2.7) or Linux way. It's probably better to
> implement with FreeBSD threads as they currently exist,
> and get massive SMP scalability when KSE's are brought
> into the source tree.
>
just a quick question...
I konw KSE will brought in after SMPng.
but it will be really helpful to konw when it will first appear
in the source tree?
or what other OS can help with SMP vs pthread problem?
thx.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 19:44:50 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178])
by hub.freebsd.org (Postfix) with ESMTP
id D1FB137B405; Fri, 29 Jun 2001 19:44:44 -0700 (PDT)
(envelope-from keichii@iteration.net)
Received: by peorth.iteration.net (Postfix, from userid 1001)
id 6E9C759229; Fri, 29 Jun 2001 21:44:43 -0500 (CDT)
Date: Fri, 29 Jun 2001 21:44:43 -0500
From: "Michael C . Wu" <keichii@iteration.net>
To: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
Cc: Matthew Rogers <matt@accelnet.net>, freebsd-smp@freebsd.org,
freebsd-hackers@freebsd.org
Subject: Re: CPU affinity hinting
Message-ID: <20010629214443.A69846@peorth.iteration.net>
Reply-To: "Michael C . Wu" <keichii@peorth.iteration.net>
Mail-Followup-To: "Michael C . Wu" <keichii@iteration.net>,
"E.B. Dreger" <eddy+public+spam@noc.everquick.net>,
Matthew Rogers <matt@accelnet.net>, freebsd-smp@freebsd.org,
freebsd-hackers@freebsd.org
References: <002001c100d8$2c406c40$a2962640@bear> <Pine.LNX.4.20.0106292104270.14702-100000@www.everquick.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.LNX.4.20.0106292104270.14702-100000@www.everquick.net>; from eddy+public+spam@noc.everquick.net on Fri, Jun 29, 2001 at 09:14:06PM +0000
X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20
X-PGP-Key-ID: 0x8FA12E20
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Fri, Jun 29, 2001 at 09:14:06PM +0000, E.B. Dreger scribbled:
| > Date: Fri, 29 Jun 2001 13:14:58 -0700
| > From: Matthew Rogers <matt@accelnet.net>
The issue is a lot more complicated than what you think.
This actually is a big issue in our future SMP implementation.
There are two types of processor affinity: user-configurable
and system automated. We have no implementation of the former,
and alfred-vm has a semblance of the latter. Please
wait patiently.....
Michael
--
+-----------------------------------------------------------+
| keichii@iteration.net | keichii@freebsd.org |
| http://iteration.net/~keichii | Yes, BSD is a conspiracy. |
+-----------------------------------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 21:14:55 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from imo-d04.mx.aol.com (imo-d04.mx.aol.com [205.188.157.36])
by hub.freebsd.org (Postfix) with ESMTP id E0CE437B401
for <freebsd-hackers@freebsd.org>; Fri, 29 Jun 2001 21:14:52 -0700 (PDT)
(envelope-from FastPathNow@netscape.net)
Received: from FastPathNow@netscape.net
by imo-d04.mx.aol.com (mail_out_v30.22.) id n.c7.6e45ec (16241)
for <freebsd-hackers@freebsd.org>; Sat, 30 Jun 2001 00:14:51 -0400 (EDT)
Received: from netscape.com (aimmail02.aim.aol.com [205.188.144.194]) by air-in03.mx.aol.com (v78_r3.8) with ESMTP; Sat, 30 Jun 2001 00:14:51 -0400
Date: Sat, 30 Jun 2001 00:14:51 -0400
From: FastPathNow@netscape.net
To: freebsd-hackers@freebsd.org
Subject: Quick question on kgdb
Mime-Version: 1.0
Message-ID: <3A8E33FD.61BB4DDA.375A6AF3@netscape.net>
X-Mailer: Franklin Webmailer 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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
if I wish to use Kgdb, I build the kernel with the following set of steps from
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html
Since I make my own modifications to the source code I do the following
Change to the /usr/src directory
# cd /usr/src
Compile the kernel.
# make buildkernel KERNCONF=MYKERNEL
Install the new kernel.
# make installkernel KERNCONF=MYKERNEL
MYKERNEL has the DEBUG=-g options for the make (I modified /usr/src/sys/i386/conf/MYKERNEL)
when I load up the installed kernel in / with 'gdb -k kernel' .. it says debugging symbols not found....
Am i loading up the right file ?. Is is supposed to have the symbols in it?
Regards
-AG
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 21:35:36 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3])
by hub.freebsd.org (Postfix) with ESMTP
id 5969B37B403; Fri, 29 Jun 2001 21:35:27 -0700 (PDT)
(envelope-from eddy+public+spam@noc.everquick.net)
Received: from localhost (eddy@localhost)
by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f5U4ZOG18906;
Sat, 30 Jun 2001 04:35:24 GMT
X-EverQuick-No-Abuse: Report any e-mail abuse to <abuse@noc.everquick.net>
Date: Sat, 30 Jun 2001 04:35:23 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: "Michael C . Wu" <keichii@peorth.iteration.net>
Cc: Matthew Rogers <matt@accelnet.net>, freebsd-smp@freebsd.org,
freebsd-hackers@freebsd.org
Subject: Re: CPU affinity hinting
In-Reply-To: <20010629214443.A69846@peorth.iteration.net>
Message-ID: <Pine.LNX.4.20.0106300344310.18448-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> Date: Fri, 29 Jun 2001 21:44:43 -0500
> From: Michael C . Wu <keichii@iteration.net>
>
> The issue is a lot more complicated than what you think.
How so? I know that idleproc and the new ipending / threaded INTs
enter the picture... and, after seeing the "HLT benchmark" page, it
would appear that simply doing nothing is sometimes better than
doing something, although I'm still scratching my head over that...
> This actually is a big issue in our future SMP implementation.
I presumed as much; the examples I gave were trivial.
I also assume that memory allocation is a major issue... to not waste time
with inter-CPU locking, I'd assume that memory would be split into pools,
a la Hoard. Maybe start with approx. NPROC count equally-sized pools,
which are roughly earmarked per hypothetical process.
For example: If MAXUSERS=80 --> NPROC=1300, a machine with 256 MB might
use 192 kB initial granularity for mmap() requests, giving 128 MB to each
processor as a first approximation.
Now, no locking is needed on mmap() until a given CPU's "pool" hits low
water, and steals from another pool. This would hopefully be infrequent,
particularly assuming that memory allocations would be distributed roughly
equally between CPUs.
I'm assuming that memory allocations are 1:1 mappable wrt processes. Yes,
I know that's faulty and oversimplified, particularly for things like
buffers and filesystem cache.
> There are two types of processor affinity: user-configurable
> and system automated. We have no implementation of the former,
Again, why not "hash(sys_auto, user_config) % NCPU"? Identical processes
would be on same CPU unless perturbed by user_config. Collisions from
identical user_config values in unrelated processes would be less likely
because of the sys_auto pertubation.
Granted: It Is Always More Complicated. (TM) But for a first pass...
> and alfred-vm has a semblance of the latter. Please wait
> patiently.....
Or, if impatient, would one continue to brainstorm, not expect a
response (i.e., not get disappointed when something basic is posted),
and track -current after the destabilization? :-)
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc.
EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 22:47:56 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3])
by hub.freebsd.org (Postfix) with ESMTP
id F325C37B405; Fri, 29 Jun 2001 22:47:50 -0700 (PDT)
(envelope-from eddy+public+spam@noc.everquick.net)
Received: from localhost (eddy@localhost)
by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f5U5lnV19618;
Sat, 30 Jun 2001 05:47:49 GMT
X-EverQuick-No-Abuse: Report any e-mail abuse to <abuse@noc.everquick.net>
Date: Sat, 30 Jun 2001 05:47:49 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: freebsd-smp@freebsd.org, freebsd-hackers@freebsd.org
Subject: Quick question: AIO / SMP / process-based threading
Message-ID: <Pine.LNX.4.20.0106300538250.19544-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Quick question(s):
1. Is AIO SMP-safe?
2. If not, how could one force coherency? (Read and rewrite locked
a word from each cache line?) Is it worth the effort, or should
one not use AIO across process boundaries?
I'm asking primarily about 4.x, unless anyone has good guesses of
how 5.x will be. ;-)
I'll also keep an eye out for KSEs... thanks to Terry and others
for alerting me to those. (KSEs really answer most of my recent
questions, but I don't think that I can wait that long, nor do I
have the kernel background to really offer any assistance in the
KSE project...)
TIA,
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc.
EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Fri Jun 29 22:57:55 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178])
by hub.freebsd.org (Postfix) with ESMTP
id 752F437B401; Fri, 29 Jun 2001 22:57:50 -0700 (PDT)
(envelope-from keichii@iteration.net)
Received: by peorth.iteration.net (Postfix, from userid 1001)
id A3CB959229; Sat, 30 Jun 2001 00:57:49 -0500 (CDT)
Date: Sat, 30 Jun 2001 00:57:49 -0500
From: "Michael C . Wu" <keichii@iteration.net>
To: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
Cc: freebsd-smp@freebsd.org, freebsd-hackers@freebsd.org
Subject: Re: Quick question: AIO / SMP / process-based threading
Message-ID: <20010630005749.A72545@peorth.iteration.net>
Reply-To: "Michael C . Wu" <keichii@peorth.iteration.net>
Mail-Followup-To: "Michael C . Wu" <keichii@iteration.net>,
"E.B. Dreger" <eddy+public+spam@noc.everquick.net>,
freebsd-smp@freebsd.org, freebsd-hackers@freebsd.org
References: <Pine.LNX.4.20.0106300538250.19544-100000@www.everquick.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.LNX.4.20.0106300538250.19544-100000@www.everquick.net>; from eddy+public+spam@noc.everquick.net on Sat, Jun 30, 2001 at 05:47:49AM +0000
X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20
X-PGP-Key-ID: 0x8FA12E20
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Sat, Jun 30, 2001 at 05:47:49AM +0000, E.B. Dreger scribbled:
| 1. Is AIO SMP-safe?
AIO is not safe, SMP or not.
| 2. If not, how could one force coherency? (Read and rewrite locked
| a word from each cache line?) Is it worth the effort, or should
| one not use AIO across process boundaries?
Don't use it.
| I'm asking primarily about 4.x, unless anyone has good guesses of
| how 5.x will be. ;-)
|
| I'll also keep an eye out for KSEs... thanks to Terry and others
| for alerting me to those. (KSEs really answer most of my recent
| questions, but I don't think that I can wait that long, nor do I
| have the kernel background to really offer any assistance in the
| KSE project...)
|
KSE won't be available for a long time.
--
+-----------------------------------------------------------+
| keichii@iteration.net | keichii@freebsd.org |
| http://iteration.net/~keichii | Yes, BSD is a conspiracy. |
+-----------------------------------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 0: 8:34 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from public.guangzhou.gd.cn (mail1-smtp.guangzhou.gd.cn [202.105.65.221])
by hub.freebsd.org (Postfix) with SMTP id 1809037B403
for <hackers@FreeBSD.org>; Sat, 30 Jun 2001 00:08:30 -0700 (PDT)
(envelope-from gzjyliu@public.guangzhou.gd.cn)
Received: from fatcow.home([203.93.59.244]) by public.guangzhou.gd.cn(JetMail 2.5.3.0)
with SMTP id jm143b3d8201; Sat, 30 Jun 2001 07:06:20 -0000
Received: (from jyliu@localhost)
by fatcow.home (8.11.3/8.11.3) id f5U78rj00338;
Sat, 30 Jun 2001 15:08:53 +0800 (CST)
(envelope-from gzjyliu@public.guangzhou.gd.cn)
X-Authentication-Warning: fatcow.home: jyliu set sender to gzjyliu@public.guangzhou.gd.cn using -f
To: hackers@FreeBSD.org
Subject: [PATCH]FSInfo Validation in mountmsdosfs()
From: Jiangyi Liu <gzjyliu@public.guangzhou.gd.cn>
Date: 30 Jun 2001 15:08:53 +0800
Message-ID: <87vglela0q.fsf@fatcow.home>
Lines: 25
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
--=-=-=
Hi all,
In -current and -stable, mountmsdosfs() doesn't not check if
pm_nxtfree exceeds the max cluster in the file system. So if a corrupted
msdos filesystem(which is not uncommon) is written, the following code
in updatefats()@msdosfs_fat.c will generate an unpleasure panic. :)
u_long cn = pmp->pm_nxtfree;
if (pmp->pm_freeclustercount
&& (pmp->pm_inusemap[cn / N_INUSEBITS]
& (1 << (cn % N_INUSEBITS)))) { .... }
A patch of primitive validation for pm_nxtfree in
mountmsdosfs()@msdosfs_vfsops.c is attached in this mail. BTW, does
anyone know why fsck_msdos is missing in FreeBSD?
Cheers,
Jiangyi
--=-=-=
Content-Type: text/x-patch
Content-Disposition: attachment; filename=msdosfs.diff
*** msdosfs_vfsops.c.orig Sat Jun 30 14:21:15 2001
--- msdosfs_vfsops.c Sat Jun 30 14:30:25 2001
***************
*** 681,686 ****
--- 681,692 ----
/*
* Check and validate (or perhaps invalidate?) the fsinfo structure? XXX
*/
+ if (pmp->pm_fsinfo && pmp->pm_nxtfree > pmp->pm_maxcluster) {
+ printf ("Next free cluster in FSInfo (%u) exceeds maxcluster (%u)\n",
+ pmp->pm_nxtfree, pmp->pm_maxcluster);
+ error = EINVAL;
+ goto error_exit;
+ }
/*
* Allocate memory for the bitmap of allocated clusters, and then
--=-=-=--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 0:48:46 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
by hub.freebsd.org (Postfix) with SMTP id 7ED7C37B409
for <freebsd-hackers@freebsd.org>; Sat, 30 Jun 2001 00:48:44 -0700 (PDT)
(envelope-from dwmalone@maths.tcd.ie)
Date: Sat, 30 Jun 2001 08:48:42 +0100
From: David Malone <dwmalone@maths.tcd.ie>
To: FastPathNow@netscape.net
Cc: freebsd-hackers@freebsd.org
Subject: Re: Quick question on kgdb
Message-ID: <20010630084842.A8926@salmon.maths.tcd.ie>
References: <3A8E33FD.61BB4DDA.375A6AF3@netscape.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3A8E33FD.61BB4DDA.375A6AF3@netscape.net>; from FastPathNow@netscape.net on Sat, Jun 30, 2001 at 12:14:51AM -0400
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Sat, Jun 30, 2001 at 12:14:51AM -0400, FastPathNow@netscape.net wrote:
> when I load up the installed kernel in / with 'gdb -k kernel' .. it says debugging symbols not found....
The kernel which is installed is stripped of debugging symbols -
you sound find a kernel.debug with symbols in teh compile directory.
David.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 3:51:27 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from roulen-gw.morning.ru (roulen-gw.morning.ru [195.161.98.242])
by hub.freebsd.org (Postfix) with ESMTP
id 857A337B401; Sat, 30 Jun 2001 03:51:16 -0700 (PDT)
(envelope-from poige@morning.ru)
Received: from NIC1 (seven.ld [192.168.11.7])
by roulen-gw.morning.ru (Postfix) with ESMTP
id 84DB82D; Sat, 30 Jun 2001 18:51:15 +0800 (KRAST)
Date: Sat, 30 Jun 2001 18:51:33 +0800
From: Igor Podlesny <poige@morning.ru>
X-Mailer: The Bat! (v1.52 Beta/7) UNREG / CD5BF9353B3B7091
Reply-To: Igor Podlesny <poige@morning.ru>
Organization: Morning Network
X-Priority: 3 (Normal)
Message-ID: <754836544.20010630185133@morning.ru>
To: freebsd-hackers@FreeBSD.ORG
Cc: freebsd-isp@freebsd.org
Subject: Flight of the rat, living wreck.....
X-Sender: Igor Podlesny <poige@morning.ru>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hello everybody!
This is relative to 4.3 for yet ;) so if you're using something older
you can skip it easily.
How it was started
------------------
For a long time I've been looking forward (and even trying to learn
freebsd internals enough to implement it by myself :) for newly
implemented ipfw's feature allowing easy filtering of non-transit
ip-packets, i.e., packets with destination address of one of the
interfaces. (You know in Linux it is done now with netfilter, which
separates ip flow into 3 different chains, BSDi's ipfw looks like a
programming language :) which allows such things for ages, if I'm not
mistaken ;). In short -- the feature is cool, and I get prepared to
start using it. At first it seemed to be okay, I felt security
comparable to "deny ip from any to any" ;)), but than, noticed that
something was going wrong.
And this was with Point-to-point interfaces. Everything was as if
remote peer ip-address matched 'me'. It's certainly wrong as far as I
can guess, so after applying fixes to my IPFW's rules allowing easy
going (passing) for packets to such addresses I started digging the
code.
ip_fw.c looks okay, but in_var.h with its INADDR_TO_IFP definition
which is a core for 'me'-feature
> if (f->fw_flg & IP_FW_F_SME) {
> INADDR_TO_IFP(src_ip, tif);
> if (tif == NULL)
> continue;
> }
> if (f->fw_flg & IP_FW_F_DME) {
> INADDR_TO_IFP(dst_ip, tif);
> if (tif == NULL)
> continue;
doesn't:
> /*
> * Macro for finding the interface (ifnet structure) corresponding to one
> * of our IP addresses.
> */
> #define INADDR_TO_IFP(addr, ifp) \
> /* struct in_addr addr; */ \
> /* struct ifnet *ifp; */ \
> { \
> register struct in_ifaddr *ia; \
> \
> for (ia = in_ifaddrhead.tqh_first; \
// so here we start looking through the queue
> ia != NULL
// sanity (I'd have written just (ia))
> && ((ia->ia_ifp->if_flags & IFF_POINTOPOINT)? \
// hm. special case if the interface is PTP
> IA_DSTSIN(ia):IA_SIN(ia))->sin_addr.s_addr != (addr).s_addr; \
// so it is like: if it is PTP, then we using DST address in comparison
// with addr.s_addr
// it is the time I started to ask myself why it is so? why we're (ok,
// they're) checking for remote ip-address if the head comment
// says:
// * Macro for finding the interface (ifnet structure) corresponding to one
// * of our IP addresses.
// ^^^
// ^^^
> ia = ia->ia_link.tqe_next) \
> continue; \
// as it's seen, the algo is: checking addresses of our ifaces or
// our remote ends in case of PTP until we get the matching or reach the end
// this is like vice versa: looking through the queue for exact matching
// and in case only ia is NULL after the first search. Also, this
// it's taking into consideration only PTP interfaces and only local
// addresses of them.
> if (ia == NULL) \
> for (ia = in_ifaddrhead.tqh_first; \
> ia != NULL; \
> ia = ia->ia_link.tqe_next) \
> if (ia->ia_ifp->if_flags & IFF_POINTOPOINT && \
> IA_SIN(ia)->sin_addr.s_addr == (addr).s_addr) \
> break; \
// the terminator: if we have found something we would come up with
// ia_ifp, or with NULL at least.
> (ifp) = (ia == NULL) ? NULL : ia->ia_ifp; \
> }
Now, getting down to IPFW's 'me'-keyword business:
IMHO, it breaks the sense in this way:
on first cycle-pass, the matching is found and ia isn't NULL. so the
second is skipped. and we got the matching, although we shouldn't.
I deem this is wrong.
Now, in conclusion
------------------
I'm a man who hasn't very deep knowledge of the BSD's bones, still be
learning it. So I can't say that the code INADDR_TO_IFP is completely
wrong because of lack of knowledge and all I say is just it doesn't
fit the purpose of IPFW's 'me'-keyword and the solution is to avoid
using it there.
Your ideas and opinions are really appreciated.
Good luck everybody and thank you in advance.
--
Best regards,
Igor mailto:poige@morning.ru
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 4: 5: 5 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ringworld.nanolink.com (diskworld.nanolink.com [195.24.48.189])
by hub.freebsd.org (Postfix) with SMTP id F019D37B403
for <freebsd-hackers@FreeBSD.ORG>; Sat, 30 Jun 2001 04:04:42 -0700 (PDT)
(envelope-from roam@orbitel.bg)
Received: (qmail 2036 invoked by uid 1000); 30 Jun 2001 11:09:08 -0000
Date: Sat, 30 Jun 2001 14:09:07 +0300
From: Peter Pentchev <roam@orbitel.bg>
To: Igor Podlesny <poige@morning.ru>
Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@freebsd.org
Subject: Re: Flight of the rat, living wreck.....
Message-ID: <20010630140907.A947@ringworld.oblivion.bg>
Mail-Followup-To: Igor Podlesny <poige@morning.ru>,
freebsd-hackers@FreeBSD.ORG, freebsd-isp@freebsd.org
References: <754836544.20010630185133@morning.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <754836544.20010630185133@morning.ru>; from poige@morning.ru on Sat, Jun 30, 2001 at 06:51:33PM +0800
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
No real knowledge of the ipfw code or the motives behind it here,
but just a comment..
On Sat, Jun 30, 2001 at 06:51:33PM +0800, Igor Podlesny wrote:
[snip]
> // so here we start looking through the queue
>
> > ia != NULL
>
> // sanity (I'd have written just (ia))
Yep, just (ia) would have worked, but style(9) mandates (ia != NULL),
which is much easier to understand and follow at a glance (clearly
showing that ia is not a flag, but a pointer).
G'luck,
Peter
--
I am the meaning of this sentence.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 4:27: 3 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from roulen-gw.morning.ru (roulen-gw.morning.ru [195.161.98.242])
by hub.freebsd.org (Postfix) with ESMTP
id 8E19837B407; Sat, 30 Jun 2001 04:26:55 -0700 (PDT)
(envelope-from poige@morning.ru)
Received: from NIC1 (seven.ld [192.168.11.7])
by roulen-gw.morning.ru (Postfix) with ESMTP
id DFFE02D; Sat, 30 Jun 2001 19:26:53 +0800 (KRAST)
Date: Sat, 30 Jun 2001 19:27:12 +0800
From: Igor Podlesny <poige@morning.ru>
X-Mailer: The Bat! (v1.52 Beta/7) UNREG / CD5BF9353B3B7091
Organization: Morning Network
X-Priority: 3 (Normal)
Message-ID: <1806975199.20010630192712@morning.ru>
To: Peter Pentchev <roam@orbitel.bg>
Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG
Subject: Re[2]: Flight of the rat, living wreck.....
In-Reply-To: <20010630140907.A947@ringworld.oblivion.bg>
References: <754836544.20010630185133@morning.ru>
<20010630140907.A947@ringworld.oblivion.bg>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
>> // so here we start looking through the queue
>>
>> > ia != NULL
>>
>> // sanity (I'd have written just (ia))
> Yep, just (ia) would have worked, but style(9) mandates (ia != NULL),
> which is much easier to understand
:)
Don't want to dispute about the 'right' style :), but :))
I prefer to say (read, write)
if (it_is_okay) {
...
}
and not
if (it_is_okay != 0) {
...
}
and the first is much more like using '? :', instead of 'if'. this is
the C-spirit :)
BTW, what do u think bout goto? ;))
(it's a joke, man 8-)
What's concerning to showing differences between flags and pointers,
if (the_next_node) {
}
if (the_next_node != NULL) {
}
yes, may be this is valuable, but practice shows that if you need to
understand the code, you're to see the declarations and definitions.
At least, you're to understand the context... And it's like dispute
about Microsoft style (LPSRZ, achMyCharArray) and so on... in common
words, the code shouldn't be written for all (this would be too
expensive and stupid) it's to be written for programmers. My opinion:
Programming languages are already too formalized, so syntax sugar is
worth adding. :)
> and follow at a glance (clearly
> showing that ia is not a flag, but a pointer).
> G'luck,
> Peter
p.s. Peter, it was off-topic :)
--
Igor mailto:poige@morning.ru
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 6:41:35 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ringworld.nanolink.com (diskworld.nanolink.com [195.24.48.189])
by hub.freebsd.org (Postfix) with SMTP id 5AE4837B7E2
for <freebsd-hackers@FreeBSD.org>; Sat, 30 Jun 2001 06:41:21 -0700 (PDT)
(envelope-from roam@orbitel.bg)
Received: (qmail 975 invoked by uid 1000); 30 Jun 2001 13:45:50 -0000
Date: Sat, 30 Jun 2001 16:45:50 +0300
From: Peter Pentchev <roam@orbitel.bg>
To: freebsd-hackers@FreeBSD.org
Subject: create executable images from core files?
Message-ID: <20010630164549.B507@ringworld.oblivion.bg>
Mail-Followup-To: freebsd-hackers@FreeBSD.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi,
While reading the perlrun(1) manpage today, I stumbled upon a reference
to an undump utility that could convert a core file into an executable
image (arguably much larger than the actual executable text, because it
would have to include the data portions, too). Is there anyhing similar
available for FreeBSD/ELF?
Yes, I've read the next sentence that says that the Perl-to-C compiler
is much more effective, but this reference to undump just piqued my
curiosity, and I just had to ask :)
G'luck,
Peter
--
If I had finished this sentence,
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 10:16:52 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75])
by hub.freebsd.org (Postfix) with ESMTP id 534A537C505
for <freebsd-hackers@freebsd.org>; Sat, 30 Jun 2001 08:48:32 -0700 (PDT)
(envelope-from LConrad@Go2France.com)
Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73])
by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 5C5D016B13
for <freebsd-hackers@freebsd.org>; Sat, 30 Jun 2001 17:48:30 +0200 (CEST)
Received: from IBM-HIRXKN66F0W.Go2France.com [195.115.185.184] by mail.Go2France.com with ESMTP
(SMTPD32-6.06) id A69A1F870128; Sat, 30 Jun 2001 17:56:10 +0200
Message-Id: <5.1.0.14.0.20010630174654.03c870c8@mail.Go2France.com>
X-Sender: LConrad@Go2France.com@mail.Go2France.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 30 Jun 2001 17:49:27 +0200
To: freebsd-hackers@freebsd.org
From: Len Conrad <LConrad@Go2France.com>
Subject: kern.maxproc
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
I need about 1000 processes for a high-volume mail gateway. I´m already
getting errors in peak periods with the default maxproc of 530.
It seems I can´t set this in loader.conf, as I can other read-only params.
Do I have to install the source and recompile?
Len
http://MenAndMice.com/DNS-training
http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K
http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 11:36:31 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from imo-m10.mx.aol.com (imo-m10.mx.aol.com [64.12.136.165])
by hub.freebsd.org (Postfix) with ESMTP id 6BAA537B59E
for <hackers@freebsd.org>; Sat, 30 Jun 2001 08:57:06 -0700 (PDT)
(envelope-from Bsdguru@aol.com)
Received: from Bsdguru@aol.com
by imo-m10.mx.aol.com (mail_out_v30.22.) id n.c3.12b62c09 (16788)
for <hackers@freebsd.org>; Sat, 30 Jun 2001 11:57:00 -0400 (EDT)
From: Bsdguru@aol.com
Message-ID: <c3.12b62c09.286f50cc@aol.com>
Date: Sat, 30 Jun 2001 11:57:00 EDT
Subject: Re: Status of encryption hardware support in FreeBSD
To: hackers@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 5.0 for Windows sub 139
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In a message dated 06/29/2001 11:01:16 AM Eastern Daylight Time,
roam@orbitel.bg writes:
> > > Really? Have you even looked at the net4501 board which was mentioned?
> > It's
> > > a single-board computer constructed for some specific communication
> > > applications, with no VGA or keyboard support, or spinning fans, and
is
> > > pretty inexpensive and in a very small form factor. Why do I want to
> > > replace this with "a new motherboard?"
> >
> > Because my motherboard is 20 times faster, has VGA support,doesnt
require
> an
> > add-on board to do fast encryption and costs about the same as yours.
> Thats
> > why.
>
> Again, you are only considering your personal case. If crypto should
> be needed on an embedded appliance, I don't think they would need
> a lightning-fast processor and VGA support, when crypto is all
> they want.
>
Your premise that "embedded appliances" are somehow doomed to use pitifully
outdated processors is simply wrong. Embedded MBs with speeds enough to
eliminate the requirement for 1) a slot and 2) an external board are
available for less than the delta in cost. So, logically speaking, anyone
with a requirement for crypto would simply chose a faster embedded MB
solution.
Listen, Im not trying to say that your project has no merit. My post was
originally meant to illustrate to others, who may have been unduly excited
about the prospects, that such a product does not buy you much in a normal
environment. I think that now we have established that its merits are limted
to low-speed embedded solutions, which is just was I was trying to say.
Bryan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 11:37:18 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8])
by hub.freebsd.org (Postfix) with ESMTP id 4EA1737B9D8
for <freebsd-hackers@FreeBSD.ORG>; Sat, 30 Jun 2001 09:59:18 -0700 (PDT)
(envelope-from rh@matriplex.com)
Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9])
by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id JAA87683;
Sat, 30 Jun 2001 09:59:03 -0700 (PDT)
(envelope-from rh@matriplex.com)
Date: Sat, 30 Jun 2001 09:59:03 -0700 (PDT)
From: Richard Hodges <rh@matriplex.com>
To: "Michael C . Wu" <keichii@iteration.net>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Quick question: AIO / SMP / process-based threading
In-Reply-To: <20010630005749.A72545@peorth.iteration.net>
Message-ID: <Pine.BSF.4.10.10106300953570.87618-100000@mail.matriplex.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
On Sat, 30 Jun 2001, Michael C . Wu wrote:
> On Sat, Jun 30, 2001 at 05:47:49AM +0000, E.B. Dreger scribbled:
> | 1. Is AIO SMP-safe?
>
> AIO is not safe, SMP or not.
That is a pretty strong statement. Could you add some more information
on this? I have had problems with AIO last year, but I would like to
think that I had some subtle logic error in my code, rather than
dismiss AIO as unusuable.
If you have specific knowlege of a problem in AIO, do you have any
suggestions on fixing it?
Thanks,
-Richard
-------------------------------------------
Richard Hodges | Matriplex, inc.
Product Manager | 769 Basque Way
rh@matriplex.com | Carson City, NV 89706
775-886-6477 | www.matriplex.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 11:37:54 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from hotmail.com (f232.law11.hotmail.com [64.4.17.232])
by hub.freebsd.org (Postfix) with ESMTP id 538D337BAD6
for <hackers@freebsd.org>; Sat, 30 Jun 2001 10:31:59 -0700 (PDT)
(envelope-from part_lion@hotmail.com)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
Sat, 30 Jun 2001 10:31:59 -0700
Received: from 207.204.127.70 by lw11fd.law11.hotmail.msn.com with HTTP; Sat, 30 Jun 2001 17:31:58 GMT
X-Originating-IP: [207.204.127.70]
From: "Joesh Juphland" <part_lion@hotmail.com>
To: hackers@freebsd.org
Subject: why not two ep pc-cards in one system ?
Date: Sat, 30 Jun 2001 11:31:58 -0600
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F232b4LepQP3TqjFGKP00013a88@hotmail.com>
X-OriginalArrivalTime: 30 Jun 2001 17:31:59.0123 (UTC) FILETIME=[90E69630:01C1018A]
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
I am trying to run two 3com 3c589 pc-cards in one system. Technically one
is a straight 3c589 and one is 3c589c.
irqs are good, since I can put any one of the two 3c589's into the laptop
along with a wavelan (wi) and both cards show up fine and work.
But when I put two 3c589's in, the first one works great (ep0) but during
startup the second one ends up:
hostname pccardd[87]: No free configuration for card 3Com Corporation
and consequently, only ep0 shows up in `ifconfig -a` - ep1 is nowhere to be
found. My /etc/rc.conf looks like:
pccard_enable="YES"
pccard_mem="DEFAULT"
pccard_flags=" -i 10 -i 15"
removable_interfaces="ep0 ep1"
my /etc/defaults/pccard.conf file has not been changed. Again, either card
will work on its own, and either card will work in conjunction with some
other card like the lucent wavelan...
thanks.
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 11:38:22 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from softweyr.com (softweyr.com [208.247.99.111])
by hub.freebsd.org (Postfix) with ESMTP
id 79F7737B710; Sat, 30 Jun 2001 11:03:58 -0700 (PDT)
(envelope-from wes@softweyr.com)
Received: from localhost.softweyr.com
([127.0.0.1] helo=softweyr.com ident=c39f7bcab758238b869b8ffa170e8727)
by softweyr.com with esmtp (Exim 3.16 #1)
id 15GOdH-00008m-00; Sat, 30 Jun 2001 11:34:11 -0600
Message-ID: <3B3E0D93.79738728@softweyr.com>
Date: Sat, 30 Jun 2001 11:34:11 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Igor Podlesny <poige@morning.ru>
Cc: freebsd-hackers@FreeBSD.ORG, freebsd-isp@freebsd.org
Subject: Re: Flight of the rat, living wreck.....
References: <754836544.20010630185133@morning.ru>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Igor Podlesny wrote:
> > /*
> > * Macro for finding the interface (ifnet structure) corresponding to one
> > * of our IP addresses.
> > */
> > #define INADDR_TO_IFP(addr, ifp) \
> > /* struct in_addr addr; */ \
> > /* struct ifnet *ifp; */ \
> > { \
> > register struct in_ifaddr *ia; \
> > \
> > for (ia = in_ifaddrhead.tqh_first; \
>
> // so here we start looking through the queue
>
> > ia != NULL
>
> // sanity (I'd have written just (ia))
>
> > && ((ia->ia_ifp->if_flags & IFF_POINTOPOINT)? \
>
> // hm. special case if the interface is PTP
>
> > IA_DSTSIN(ia):IA_SIN(ia))->sin_addr.s_addr != (addr).s_addr; \
>
> // so it is like: if it is PTP, then we using DST address in comparison
> // with addr.s_addr
>
> // it is the time I started to ask myself why it is so? why we're (ok,
> // they're) checking for remote ip-address if the head comment
> // says:
> // * Macro for finding the interface (ifnet structure) corresponding to one
> // * of our IP addresses.
> // ^^^
> // ^^^
With point-to-point connections, the address at the opposite end of the
connection is always used in the route table. When the interface is
created as a point-to-point interface, a route is automatically entered
from the local address to the opposite address. The "corresponding"
in the comment at the beginning of the macro is interpreted rather loosely.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
wes@softweyr.com http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 11:47:45 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from hotmail.com (law2-f120.hotmail.com [216.32.181.120])
by hub.freebsd.org (Postfix) with ESMTP id 7041637B405
for <freebsd-hackers@FreeBSD.ORG>; Sat, 30 Jun 2001 11:47:43 -0700 (PDT)
(envelope-from vinupattery@hotmail.com)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
Fri, 29 Jun 2001 11:51:22 -0700
Received: from 128.193.48.73 by lw2fd.hotmail.msn.com with HTTP; Fri, 29 Jun 2001 18:51:22 GMT
X-Originating-IP: [128.193.48.73]
From: "vinu pattery" <vinupattery@hotmail.com>
To: tlambert2@mindspring.com
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: interrupt on to Kernel
Date: Sat, 30 Jun 2001 00:21:22 +0530
Mime-Version: 1.0
Content-Type: text/html
Message-ID: <LAW2-F120mcarcR4ZDg00008df5@hotmail.com>
X-OriginalArrivalTime: 29 Jun 2001 18:51:22.0599 (UTC) FILETIME=[7DBD9770:01C100CC]
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
<html><DIV>
<P>Please scroll down</P></DIV>
<P>Please scroll down</P>
<P>------------------------------------------------------------</P>
<P>>It's not clear what you mean by "interrupt the Kernel for </P>
<P>>resources"... the only resources you can grab at interrupt </P>
<DIV></DIV>>are things that you pre-allocated, things you get from a
<DIV></DIV>>zalloci() from a previously established interrupt safe zone
<DIV></DIV>>in the zone allocator (e.g. mbufs), and CPU time.
<DIV></DIV>>
<DIV></DIV>
<P>Hello,</P>
<P>initially the processor of the computer is executing a particular program,.................then when the NICard gets data thru the network line it interrupts the hardware so that the data is processed and gets to the application layer.............................when this hardware interrupt comes in........................the Interrupt service routine of the NIC device driver is scheduled by the Free BSD kernel....................so now instead of the parent program..the ISR is running on the processor.............i wanted to know the sequence of steps which take place between the switching from parent program ---> to-->ISR and then back from ISR to parent program.</P>
<P>I would be very grateful if u could let me know how to go about this,</P>
<P>i am already looking at the links u suggested and trying to help myself,</P>
<P>thanx</P>
<P>Vinu</P>
<P> </P>
<P> </P><br clear=all><hr>Get Your Private, Free E-mail from MSN Hotmail at <a href="http://www.hotmail.com">http://www.hotmail.com</a>.<br></p></html>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 12:43:37 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66])
by hub.freebsd.org (Postfix) with ESMTP id 2FC1A37B401
for <hackers@FreeBSD.ORG>; Sat, 30 Jun 2001 12:43:32 -0700 (PDT)
(envelope-from nate@yogotech.com)
Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131])
by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id NAA07200;
Sat, 30 Jun 2001 13:43:30 -0600 (MDT)
(envelope-from nate@nomad.yogotech.com)
Received: (from nate@localhost)
by nomad.yogotech.com (8.8.8/8.8.8) id NAA09484;
Sat, 30 Jun 2001 13:43:30 -0600 (MDT)
(envelope-from nate)
From: Nate Williams <nate@yogotech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15166.11233.223309.96395@nomad.yogotech.com>
Date: Sat, 30 Jun 2001 13:43:29 -0600 (MDT)
To: Bsdguru@aol.com
Cc: hackers@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
In-Reply-To: <c3.12b62c09.286f50cc@aol.com>
References: <c3.12b62c09.286f50cc@aol.com>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Reply-To: nate@yogotech.com (Nate Williams)
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> > > > Really? Have you even looked at the net4501 board which was mentioned?
>
> > > It's
> > > > a single-board computer constructed for some specific communication
> > > > applications, with no VGA or keyboard support, or spinning fans, and
> is
> > > > pretty inexpensive and in a very small form factor. Why do I want to
> > > > replace this with "a new motherboard?"
> > >
> > > Because my motherboard is 20 times faster, has VGA support,doesnt
> require
> > an
> > > add-on board to do fast encryption and costs about the same as yours.
> > Thats
> > > why.
> >
> > Again, you are only considering your personal case. If crypto should
> > be needed on an embedded appliance, I don't think they would need
> > a lightning-fast processor and VGA support, when crypto is all
> > they want.
> >
>
> Your premise that "embedded appliances" are somehow doomed to use pitifully
> outdated processors is simply wrong.
Who said anything about pitifully outdated processors. I can buy a heck
of alot of CPU horsepower w/out buying the latest/greatest CPU.
As a matter of fact, in almost all cases, the best bang for the buck
would be for processorts that you imply to 'pitfully outdated'.
> Embedded MBs with speeds enough to eliminate the requirement for 1) a
> slot and 2) an external board are available for less than the delta in
> cost.
That's simply not true. If you are building 'truly embedded' systems
(ie; 100K+ boxes), you're not going to be using 'off the shelf' PC
parts. You're going to be specifying particular parts to be used, and
in general the difference in cost of $1-5 for the CPU makes a *huge*
difference in the price-point you are trying to make.
Often times it's easier to build a hierarchy of products, with each
individual tier having the same 'basic' setup (keeping costs low), and
by adding additional 'special purpose' boards, you can increase the
functionality of the box by only increasing the costs trivially.
> So, logically speaking, anyone
> with a requirement for crypto would simply chose a faster embedded MB
> solution.
You seem to have a different definition of embedded than many others do
Bryan. Have you ever been involved with specifying and building
embedded systems products, or are you just talking out of the side of
your mouth?
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 12:55:28 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52])
by hub.freebsd.org (Postfix) with ESMTP id D538237B403
for <freebsd-hackers@freebsd.org>; Sat, 30 Jun 2001 12:55:22 -0700 (PDT)
(envelope-from rbraun@apple.com)
Received: from apple.com (A17-129-100-225.apple.com [17.129.100.225])
by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id MAA07455
for <freebsd-hackers@freebsd.org>; Sat, 30 Jun 2001 12:55:22 -0700 (PDT)
Received: from scv2.apple.com (scv2.apple.com) by apple.com
(Content Technologies SMTPRS 4.2.1) with ESMTP id <T5475ce8678118164e15c0@apple.com> for <freebsd-hackers@freebsd.org>;
Sat, 30 Jun 2001 12:55:21 -0700
Received: from brauro.apple.com (brauro.apple.com [17.202.41.60])
by scv2.apple.com (8.11.3/8.11.3) with ESMTP id f5UJtLw21656
for <freebsd-hackers@freebsd.org>; Sat, 30 Jun 2001 12:55:21 -0700 (PDT)
Date: Sat, 30 Jun 2001 12:55:21 -0700
Content-Type: text/plain;
format=flowed;
charset=us-ascii
Subject: xinstall args to strip
X-Mailer: Apple Mail (2.402)
Mime-Version: 1.0 (Apple Message framework v402)
From: Rob Braun <rbraun@apple.com>
To: freebsd-hackers@freebsd.org
Content-Transfer-Encoding: 7bit
Message-Id: <D6E1C9DE-6D91-11D5-A64B-003065BADC60@brauro.apple.com.synack.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
FreeBSD's xinstall [install(1)] lacks a way to pass arguments to strip.
In non-ELF systems this can be important. Below is a patch to FreeBSD's
xinstall TOT that adds a -Z flag that takes an argument that can be
passed to strip(1) when it is exec'd. It also lets the user specify an
alternate strip program with the STRIP environment variable. This
functionality is based on NetBSD's xinstall -S flag. Unfortunately, -S
is already used by FreeBSD's xinstall as a "safe copy".
Rob
Index: install.1
===================================================================
RCS file: /cvs/Darwin/Commands/BSD/file_cmds/install/install.1,v
retrieving revision 1.1.1.3
diff -u -d -r1.1.1.3 install.1
--- install.1 2001/06/28 00:35:04 1.1.1.3
+++ install.1 2001/06/30 19:45:52
@@ -46,6 +46,7 @@
.Op Fl g Ar group
.Op Fl m Ar mode
.Op Fl o Ar owner
+.Op Fl Z Ar stripflags
.Ar file1 file2
.Nm
.Op Fl bCcMpSsv
@@ -54,6 +55,7 @@
.Op Fl g Ar group
.Op Fl m Ar mode
.Op Fl o Ar owner
+.Op Fl Z Ar stripflag
.Ar file1 ... fileN directory
.Nm
.Fl d
@@ -61,6 +63,7 @@
.Op Fl g Ar group
.Op Fl m Ar mode
.Op Fl o Ar owner
+.Op Fl Z Ar stripflag
.Ar directory ...
.Sh DESCRIPTION
The file(s) are copied
@@ -155,6 +158,23 @@
.Nm
can be portable over a large
number of systems and binary types.
+.It Fl Z Ar stripflags
+.Nm
+pases
+.Ar stripflags
+as option arguments to
+.Xr strip 1 .
+When -Z is used,
+.Xr strip 1
+is invoked via the
+.Xr sh 1
+shell, allowing a single -Z argument to be specified to
+.Nm
+which the shell can then tokenize. Normally,
+.Nm
+invokes
+.Xr strip 1
+directly. This flag implies -s
.It Fl v
Causes
.Nm
Index: xinstall.c
===================================================================
RCS file: /cvs/Darwin/Commands/BSD/file_cmds/install/xinstall.c,v
retrieving revision 1.2
diff -u -d -r1.2 xinstall.c
--- xinstall.c 2001/06/28 00:38:03 1.2
+++ xinstall.c 2001/06/30 19:45:52
@@ -84,6 +84,7 @@
int dobackup, docompare, dodir, dopreserve, dostrip, nommap, safecopy,
verbose;
mode_t mode = S_IRWXU | S_IRGRP | S_IXGRP | S_IROTH | S_IXOTH;
char *suffix = BACKUP_SUFFIX;
+char *stripArgs=NULL;
#ifdef __APPLE__
u_long string_to_flags __P((char **, u_long *, u_long *));
@@ -165,6 +166,12 @@
case 'v':
verbose = 1;
break;
+ case 'Z':
+ stripArgs =
(char*)malloc(sizeof(char)*(strlen(optarg)+1
+));
+ strcpy(stripArgs,optarg);
+ dostrip = 1;
+ break;
case '?':
default:
usage();
@@ -704,6 +711,7 @@
char *to_name;
{
int serrno, status;
+ char *stripprog;
switch (fork()) {
case -1:
@@ -712,8 +720,19 @@
errno = serrno;
err(EX_TEMPFAIL, "fork");
case 0:
- execlp("strip", "strip", to_name, NULL);
- err(EX_OSERR, "exec(strip)");
+ stripprog = getenv("STRIP");
+ if (stripprog == NULL)
+ stripprog = _PATH_STRIP;
+ if (stripArgs) {
+ char *cmd = (char*)malloc(sizeof(char)*
+ (3+strlen(stripprog)+
+ strlen(stripArgs)+
+ strlen(to_name)));
+ sprintf(cmd, "%s %s %s", stripprog, stripArgs,
to_name);
+ execl(_PATH_BSHELL, "sh", "-c", cmd, NULL);
+ } else
+ execlp(stripprog, "strip", to_name, NULL);
+ err(EX_OSERR, "exec(%s)", stripprog);
default:
if (wait(&status) == -1 || status) {
(void)unlink(to_name);
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 14:13:59 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from guru.mired.org (okc-27-141-144.mmcable.com [24.27.141.144])
by hub.freebsd.org (Postfix) with SMTP id 0C9C637B405
for <freebsd-hackers@FreeBSD.ORG>; Sat, 30 Jun 2001 14:13:54 -0700 (PDT)
(envelope-from mwm@mired.org)
Received: (qmail 72261 invoked by uid 100); 30 Jun 2001 21:13:53 -0000
From: Mike Meyer <mwm@mired.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15166.16657.406627.673835@guru.mired.org>
Date: Sat, 30 Jun 2001 16:13:53 -0500
To: Igor Podlesny <poige@morning.ru>
Cc: Peter Pentchev <roam@orbitel.bg>, freebsd-hackers@FreeBSD.ORG,
freebsd-isp@FreeBSD.ORG
Subject: Re: Re[2]: Flight of the rat, living wreck.....
In-Reply-To: <1806975199.20010630192712@morning.ru>
References: <754836544.20010630185133@morning.ru>
<20010630140907.A947@ringworld.oblivion.bg>
<1806975199.20010630192712@morning.ru>
X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid
X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG%
*h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Igor Podlesny <poige@morning.ru> types:
> >> // so here we start looking through the queue
> >>
> >> > ia != NULL
> >>
> >> // sanity (I'd have written just (ia))
>
> > Yep, just (ia) would have worked, but style(9) mandates (ia != NULL),
> > which is much easier to understand
>
> :)
>
> Don't want to dispute about the 'right' style :), but :))
> I prefer to say (read, write)
For FreeBSD code work, there is a "right" style. It's documented in
the style(9) man page. Having everyone using the same style makes
maintenance a lot saner.
I think in this case, it says to use "if (ia != NULL)" instead of "if
(ia)". It doesn't say so outright, but it strongly hints that tests
for 0 should compare against the appropriate 0 unless the value is a
boolean.
<mike
--
Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 14:21:49 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from imo-d05.mx.aol.com (imo-d05.mx.aol.com [205.188.157.37])
by hub.freebsd.org (Postfix) with ESMTP id 2D26137B401
for <hackers@freebsd.org>; Sat, 30 Jun 2001 14:21:47 -0700 (PDT)
(envelope-from Bsdguru@aol.com)
Received: from Bsdguru@aol.com
by imo-d05.mx.aol.com (mail_out_v30.22.) id k.81.c6bd74a (16783);
Sat, 30 Jun 2001 17:21:09 -0400 (EDT)
From: Bsdguru@aol.com
Message-ID: <81.c6bd74a.286f9cc5@aol.com>
Date: Sat, 30 Jun 2001 17:21:09 EDT
Subject: Re: Status of encryption hardware support in FreeBSD
To: nate@yogotech.com, hackers@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 5.0 for Windows sub 139
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
In a message dated 06/30/2001 3:44:04 PM Eastern Daylight Time,
nate@yogotech.com writes:
> > Your premise that "embedded appliances" are somehow doomed to use
pitifully
>
> > outdated processors is simply wrong.
>
> Who said anything about pitifully outdated processors. I can buy a heck
> of alot of CPU horsepower w/out buying the latest/greatest CPU.
>
> As a matter of fact, in almost all cases, the best bang for the buck
> would be for processorts that you imply to 'pitfully outdated'.
I think you've missed the fact that the '486 solution requires an add-on
board (priced at $80.) and the faster cpu solution doesnt. That adds a lot of
margin to get a faster MB, more than enough to compensate for the board.
Bryan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 14:25:42 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from saturn.bsdhome.com (unknown [24.25.2.193])
by hub.freebsd.org (Postfix) with ESMTP
id D931837B401; Sat, 30 Jun 2001 14:25:30 -0700 (PDT)
(envelope-from bsd@bsdhome.com)
Received: from neutrino.bsdhome.com (jupiter [192.168.220.13])
by saturn.bsdhome.com (8.11.3/8.11.3) with ESMTP id f5ULPRC09577;
Sat, 30 Jun 2001 17:25:28 -0400 (EDT)
Received: (from bsd@localhost)
by neutrino.bsdhome.com (8.11.4/8.11.4) id f5ULPMu64819;
Sat, 30 Jun 2001 17:25:22 -0400 (EDT)
(envelope-from bsd)
Date: Sat, 30 Jun 2001 17:25:22 -0400
From: Brian Dean <bsd@bsdhome.com>
To: freebsd-audit@freebsd.org
Cc: freebsd-hackers@freebsd.org
Subject: kernel ddb patch for setting hardware watchpoints
Message-ID: <20010630172522.A64393@neutrino.bsdhome.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi,
Please look over the following patch to ddb. This patch adds the
'hwatch' and 'dhwatch' commands to set and delete hardware
watchpoints. These commands allow one to utilize hardware watchpoints
without having to modify the debug registers directly (which can be
tricky).
I modified the 'show watch' command to display information about
hardware watchpoints as well. These commands result in no-ops for
architectures that don't support them.
I originally tried to overload the 'watch' and 'dwatch' command but
their operation was sufficiently different that I decided it best to
make a new command. For one thing, watchpoints are not actually
installed until a 'continue' command is given which makes it
impossible see the effects on the debug registers until after the next
break or watchpoint has been hit. More serious, though, the 'watch'
command really seems to be designed for watching addresses in user
address space and not the kernel.
To support the hwatch/dhwatch commands, I needed three machine
dependent hooks from ddb:
db_md_set_watchpoint()
db_md_clr_watchpoint()
db_md_list_watchpoints()
These are all called from within ddb/db_watch.c and are defined in
$arch/$arch/db_trace.c.
The patch is located at:
http://people.freebsd.org/~bsd/ddb/ddb.patch2
I've built an alpha kernel with the patch applied and it built ok. I
don't have hardware to actually run it, though, but since this ends up
as a no-op on alpha (and ia64), I suspect it is Ok (famous last
words). I don't know where I can build this on an ia64 machine. Do we
have a machine available for this kind of thing?
Caveats: This patch won't do the right thing on SMP systems. The
debug registers are set/cleared only for the CPU running ddb.
Since the debug registers are a per-cpu thing, they won't be
set for the other CPUs. I'll work on that next.
See below for a sample session.
Thanks,
-Brian
--
Brian Dean
bsd@FreeBSD.org
bsd@bsdhome.com
Example session:
login:
FreeBSD/i386 (stage.bsdhome.com) (ttyd1)
login: Debugger("manual escape to debugger")
Stopped at Debugger+0x44: pushl %ebx
db> show reg
cs 0x8
ds 0x10
es 0xc9a80010
fs 0xc0300018 harvestring+0x2b38
ss 0x10
eax 0x26
ecx 0x2fd
edx 0x2f9
ebx 0x202
esp 0xc9a8ded0
ebp 0xc9a8dedc
esi 0xc0cff400
edi 0xc0d16800
eip 0xc0276974 Debugger+0x44
efl 0x46
dr0 0
dr1 0
dr2 0
dr3 0
dr4 0xffff0ff0
dr5 0x400
dr6 0xffff0ff0
dr7 0x400
Debugger+0x44: pushl %ebx
db> hwatch 0xcaae6740,9
db> show watch
No watchpoints set
hardware watchpoints:
watch status type len address
----- -------- ---------- --- ----------
0 enabled write 4 0xcaae6740
1 enabled write 4 0xcaae6744
2 enabled write 1 0xcaae6748
3 disabled
debug register values:
dr0 0xcaae6740
dr1 0xcaae6744
dr2 0xcaae6748
dr3 0x00000000
dr4 0xffff0ff0
dr5 0x01dd042a
dr6 0xffff0ff0
dr7 0x01dd042a
db> cont
Stopped at runq_add+0x41: movl 0x4(%edx),%eax
db> dhwatch 0xcaae6740,9
db> show watch
No watchpoints set
hardware watchpoints:
watch status type len address
----- -------- ---------- --- ----------
0 disabled
1 disabled
2 disabled
3 disabled
debug register values:
dr0 0x00000000
dr1 0x00000000
dr2 0x00000000
dr3 0x00000000
dr4 0xffff0ff1
dr5 0x00000400
dr6 0xffff0ff1
dr7 0x00000400
db> cont
FreeBSD/i386 (stage.bsdhome.com) (ttyd1)
login:
--
Brian Dean bsd@bsdhome.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 15:17:36 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66])
by hub.freebsd.org (Postfix) with ESMTP id D1D6437B401
for <hackers@freebsd.org>; Sat, 30 Jun 2001 15:17:32 -0700 (PDT)
(envelope-from nate@yogotech.com)
Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131])
by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id QAA09552;
Sat, 30 Jun 2001 16:17:30 -0600 (MDT)
(envelope-from nate@nomad.yogotech.com)
Received: (from nate@localhost)
by nomad.yogotech.com (8.8.8/8.8.8) id QAA09769;
Sat, 30 Jun 2001 16:17:30 -0600 (MDT)
(envelope-from nate)
From: Nate Williams <nate@yogotech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15166.20474.32312.398813@nomad.yogotech.com>
Date: Sat, 30 Jun 2001 16:17:30 -0600 (MDT)
To: Bsdguru@aol.com
Cc: nate@yogotech.com, hackers@freebsd.org
Subject: Re: Status of encryption hardware support in FreeBSD
In-Reply-To: <81.c6bd74a.286f9cc5@aol.com>
References: <81.c6bd74a.286f9cc5@aol.com>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Reply-To: nate@yogotech.com (Nate Williams)
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> > > Your premise that "embedded appliances" are somehow doomed to use
> pitifully
> >
> > > outdated processors is simply wrong.
> >
> > Who said anything about pitifully outdated processors. I can buy a heck
> > of alot of CPU horsepower w/out buying the latest/greatest CPU.
> >
> > As a matter of fact, in almost all cases, the best bang for the buck
> > would be for processorts that you imply to 'pitfully outdated'.
>
> I think you've missed the fact that the '486 solution requires an
> add-on board (priced at $80.) and the faster cpu solution doesnt. That
> adds a lot of margin to get a faster MB, more than enough to
> compensate for the board.
Not necessarily. The upgraded motherboard also requires a faster
processor, and the two parts added together are almost certainly going
to be more than $80.
In any case, that's just one example. There are many more examples
where a PIII-400 is more than adequate to do most of the processing, if
you don't have to do encryption. If you involve encryption, we're
talking alot more CPU, memory, and such. You can easily get an add-on
board for *much* cheaper than to upgrade your memory, mboard, and CPU.
Nate
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 15:17:45 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from idiom.com (idiom.com [216.240.32.1])
by hub.freebsd.org (Postfix) with ESMTP id 82AD237B401
for <freebsd-hackers@FreeBSD.ORG>; Sat, 30 Jun 2001 15:17:43 -0700 (PDT)
(envelope-from rdm@cfcl.com)
Received: from cfcl.com (cpe-24-221-169-54.ca.sprintbbd.net [24.221.169.54])
by idiom.com (8.9.3/8.9.3) with ESMTP id PAA73015
for <freebsd-hackers@FreeBSD.ORG>; Sat, 30 Jun 2001 15:17:43 -0700 (PDT)
Received: from [192.168.168.205] (cerberus [192.168.168.205])
by cfcl.com (8.11.1/8.11.1) with ESMTP id f5UMJHK33354
for <freebsd-hackers@FreeBSD.ORG>; Sat, 30 Jun 2001 15:19:18 -0700 (PDT)
(envelope-from rdm@cfcl.com)
Mime-Version: 1.0
Message-Id: <p05100381b763fac319ff@[192.168.168.205]>
In-Reply-To: <15166.16657.406627.673835@guru.mired.org>
References: <754836544.20010630185133@morning.ru>
<20010630140907.A947@ringworld.oblivion.bg>
<1806975199.20010630192712@morning.ru>
<15166.16657.406627.673835@guru.mired.org>
Date: Sat, 30 Jun 2001 14:59:57 -0700
To: freebsd-hackers@FreeBSD.ORG
From: Rich Morin <rdm@cfcl.com>
Subject: compatibility of UFS-partitioned FireWire drives
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
I have a luggable FireWire drive which I am considering using for
backups and data mobility on a variety of machines and operating
systems (roughly, *BSD, Mac OS X, and (eventually) Linux).
I'd welcome any suggestions as to things to do or avoid. I'd rather
not get a ways down the road and discover that I need to repartition
the disc for some obscure reason...
-r
--
email: rdm@cfcl.com; phone: +1 650-873-7841
http://www.cfcl.com/rdm - home page, resume, etc.
http://www.cfcl.com/Meta/md_fb.html - The FreeBSD Browser
http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 15:19:49 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from server.soekris.com (soekris.com [216.15.61.44])
by hub.freebsd.org (Postfix) with ESMTP id A494037B401
for <hackers@FreeBSD.ORG>; Sat, 30 Jun 2001 15:19:45 -0700 (PDT)
(envelope-from soren@soekris.com)
Received: from soekris.com (soren.soekris.com [192.168.1.4])
by server.soekris.com (8.9.2/8.9.2) with ESMTP id PAA73522;
Sat, 30 Jun 2001 15:19:38 -0700 (PDT)
(envelope-from soren@soekris.com)
Message-ID: <3B3E5072.FEF9DF00@soekris.com>
Date: Sat, 30 Jun 2001 15:19:30 -0700
From: Soren Kristensen <soren@soekris.com>
Organization: Soekris Engineering
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Bsdguru@aol.com
Cc: nate@yogotech.com, hackers@FreeBSD.ORG
Subject: Re: Status of encryption hardware support in FreeBSD
References: <81.c6bd74a.286f9cc5@aol.com>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Hi,
Bryan, again you're missing the point :-) You're working out from just
processing power, in the embedded world you usually start from somewhere
else....
In the case of my products, the requirement are small size, low cost, no
moving parts (no fans or disks), long life, low power, meaning a power
budget of 10W incl everything.... The 133 Mhz 486 processor use <2W and
the encryption processor is also <2W.
You cannot get any x86 processor that can meet the performance of the
encryption processor without needing a fan.... And when you add the cost
of all the other parts you need beside your mainboard and 1Ghz
processor, it's also more expensive than my solution.
But anyway, we can probably agree to disagree, so maybe we should let
this tread die....
Soren
> I think you've missed the fact that the '486 solution requires an add-on
> board (priced at $80.) and the faster cpu solution doesnt. That adds a lot of
> margin to get a faster MB, more than enough to compensate for the board.
>
> Bryan
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 19:59:53 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from imo-d06.mx.aol.com (imo-d06.mx.aol.com [205.188.157.38])
by hub.freebsd.org (Postfix) with ESMTP id ADF2237B405
for <freebsd-hackers@freebsd.org>; Sat, 30 Jun 2001 19:59:51 -0700 (PDT)
(envelope-from FastPathNow@netscape.net)
Received: from FastPathNow@netscape.net
by imo-d06.mx.aol.com (mail_out_v30.22.) id t.1c.18f4ef6 (16237);
Sat, 30 Jun 2001 22:59:36 -0400 (EDT)
Received: from netscape.com (aimmail05.aim.aol.com [205.188.144.197]) by air-in03.mx.aol.com (v78_r3.8) with ESMTP; Sat, 30 Jun 2001 22:59:36 -0400
Date: Sat, 30 Jun 2001 22:59:35 -0400
From: FastPathNow@netscape.net
To: dwmalone@maths.tcd.ie
Cc: FastPathNow@netscape.net, freebsd-hackers@freebsd.org
Subject: Re: Quick question on kgdb
Mime-Version: 1.0
Message-ID: <1DEA2053.397C3278.375A6AF3@netscape.net>
References: <3A8E33FD.61BB4DDA.375A6AF3@netscape.net> <20010630084842.A8926@salmon.maths.tcd.ie>
X-Mailer: Franklin Webmailer 1.0
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
Both the kernel and kernel.debug files are of exactly the same size - about 3.3 Megs . This is inspite of having the DEBUG=-g option being set in the MYKERNEL directory. Any other clues, why this could be happening. I also tried the other procedure of using 'make depend' etc as outlined in the doc, but that produced the same results. What else could I be missing?
-AG
David Malone <dwmalone@maths.tcd.ie> wrote:
>
> On Sat, Jun 30, 2001 at 12:14:51AM -0400, FastPathNow@netscape.net wrote:
> > when I load up the installed kernel in / with 'gdb -k kernel' .. it says debugging symbols not found....
>
> The kernel which is installed is stripped of debugging symbols -
> you sound find a kernel.debug with symbols in teh compile directory.
>
> David.
>
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at http://webmail.netscape.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 20:28:43 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from sneakerz.org (sneakerz.org [216.33.66.254])
by hub.freebsd.org (Postfix) with ESMTP
id B8FE637B401; Sat, 30 Jun 2001 20:28:39 -0700 (PDT)
(envelope-from bright@sneakerz.org)
Received: by sneakerz.org (Postfix, from userid 1092)
id 30E755D020; Sat, 30 Jun 2001 22:28:29 -0500 (CDT)
Date: Sat, 30 Jun 2001 22:28:29 -0500
From: Alfred Perlstein <bright@sneakerz.org>
To: "Michael C . Wu" <keichii@peorth.iteration.net>
Cc: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>,
freebsd-smp@freebsd.org, freebsd-hackers@freebsd.org
Subject: Re: Quick question: AIO / SMP / process-based threading
Message-ID: <20010630222829.E84523@sneakerz.org>
References: <Pine.LNX.4.20.0106300538250.19544-100000@www.everquick.net> <20010630005749.A72545@peorth.iteration.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20010630005749.A72545@peorth.iteration.net>; from keichii@iteration.net on Sat, Jun 30, 2001 at 12:57:49AM -0500
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
* Michael C . Wu <keichii@iteration.net> [010630 14:05] wrote:
> On Sat, Jun 30, 2001 at 05:47:49AM +0000, E.B. Dreger scribbled:
> | 1. Is AIO SMP-safe?
>
> AIO is not safe, SMP or not.
>
> | 2. If not, how could one force coherency? (Read and rewrite locked
> | a word from each cache line?) Is it worth the effort, or should
> | one not use AIO across process boundaries?
>
> Don't use it.
Can you point to some specific PRs about this or crashdumps before
(or at least while) taking pot shots at the AIO implementation?
thanks,
--
-Alfred Perlstein [alfred@freebsd.org]
Ok, who wrote this damn function called '??'?
And why do my programs keep crashing in it?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 20:51:27 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3])
by hub.freebsd.org (Postfix) with ESMTP
id A052637B405; Sat, 30 Jun 2001 20:51:21 -0700 (PDT)
(envelope-from eddy+public+spam@noc.everquick.net)
Received: from localhost (eddy@localhost)
by a.mx.everquick.net (8.10.2/8.10.2) with ESMTP id f613pB429235;
Sun, 1 Jul 2001 03:51:11 GMT
X-EverQuick-No-Abuse: Report any e-mail abuse to <abuse@noc.everquick.net>
Date: Sun, 1 Jul 2001 03:51:10 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: Alfred Perlstein <bright@sneakerz.org>
Cc: "Michael C . Wu" <keichii@peorth.iteration.net>,
freebsd-smp@freebsd.org, freebsd-hackers@freebsd.org
Subject: Re: Quick question: AIO / SMP / process-based threading
In-Reply-To: <20010630222829.E84523@sneakerz.org>
Message-ID: <Pine.LNX.4.20.0107010345230.29177-100000@www.everquick.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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
> Date: Sat, 30 Jun 2001 22:28:29 -0500
> From: Alfred Perlstein <bright@sneakerz.org>
>
> Can you point to some specific PRs about this or crashdumps before
> (or at least while) taking pot shots at the AIO implementation?
In the mean time, until somebody can substantiate that claim... is AIO SMP
safe? I see that aiocb.aio_buf is declared as "volatile", so I would
presume so.
I just want to be sure that, if an aio call runs on one CPU, another CPU
can access *aio_buf and be 100% certain that the data are coherent.
aio_buf = mmap() using MAP_HASSEMAPHORE -- good idea, bad idea, pointless?
TIA,
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc.
EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@brics.com>, or you are likely to be blocked.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
From owner-freebsd-hackers Sat Jun 30 22:11:43 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from clmboh1-smtp3.columbus.rr.com (clmboh1-smtp3.columbus.rr.com [65.24.0.112])
by hub.freebsd.org (Postfix) with ESMTP id 6DFCF37B405
for <freebsd-hackers@FreeBSD.ORG>; Sat, 30 Jun 2001 22:11:40 -0700 (PDT)
(envelope-from wmoran@iowna.com)
Received: from iowna.com (dhcp065-024-023-038.columbus.rr.com [65.24.23.38])
by clmboh1-smtp3.columbus.rr.com (8.11.2/8.11.2) with ESMTP id f6158Hs15008;
Sun, 1 Jul 2001 01:08:17 -0400 (EDT)
Message-ID: <3B3EB0E9.60E942C9@iowna.com>
Date: Sun, 01 Jul 2001 01:11:05 -0400
From: Bill Moran <wmoran@iowna.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: FastPathNow@netscape.net
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Quick question on kgdb
References: <3A8E33FD.61BB4DDA.375A6AF3@netscape.net> <20010630084842.A8926@salmon.maths.tcd.ie> <1DEA2053.397C3278.375A6AF3@netscape.net>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG
FastPathNow@netscape.net wrote:
>
> Both the kernel and kernel.debug files are of exactly the same size -
> about 3.3 Megs . This is inspite of having the DEBUG=-g option being set
> in the MYKERNEL directory. Any other clues, why this could be happening.
> I also tried the other procedure of using 'make depend' etc as outlined
> in the doc, but that produced the same results. What else could I be missing?
The handbook claims that the build procedure strips the kernel before
installing.
Can you manually strip the kernel? Most optimized kernels I've seen are
less
than 2 meg, the generic kernel is slightly over three. A debug kernel is
usually
larger than 7 meg, so it seems like your kernel is already stripped, as
well
as the kernel.debug.
Verify your config file and try rebuilding the kernel.
--
If a bird in the hand is worth two in the bush,
then what can I get for two hands in the bush?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message