From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 25 02:29:20 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56FB716A4CE; Sun, 25 Jul 2004 02:29:20 +0000 (GMT) Received: from afields.ca (afields.ca [216.194.67.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2110343D5E; Sun, 25 Jul 2004 02:29:20 +0000 (GMT) (envelope-from afields@afields.ca) Received: from afields.ca (localhost.afields.ca [127.0.0.1]) by afields.ca (8.12.11/8.12.11) with ESMTP id i6P2TEna054043; Sat, 24 Jul 2004 22:29:14 -0400 (EDT) (envelope-from afields@afields.ca) Received: (from afields@localhost) by afields.ca (8.12.11/8.12.11/Submit) id i6P2TEBH054042; Sat, 24 Jul 2004 22:29:14 -0400 (EDT) (envelope-from afields) Date: Sat, 24 Jul 2004 22:29:13 -0400 From: Allan Fields To: Jake Hamby Message-ID: <20040725022913.GA53935@afields.ca> References: <4101DC69.9030309@anobject.com> <20040724.160110.127665912.imp@bsdimp.com> <4102EEE6.3020805@anobject.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4102EEE6.3020805@anobject.com> User-Agent: Mutt/1.4i cc: freebsd-hackers@freebsd.org cc: freebsd-config@freebsd.org Subject: Re: "Next Generation" kernel configuration? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2004 02:29:20 -0000 On Sat, Jul 24, 2004 at 04:21:10PM -0700, Jake Hamby wrote: > M. Warner Losh wrote: > > > >What's wrong with adding: > > > >makeoptions MODULES_OVERRIDE="a b c" > >to your config file? It is already supported. Though, I've used this before to good effect (on slow crash-box): There's no mention to specify exclusions, only what to include. If you want only a few things excluded, would you not have to list everything else in each of the same subdirs? No biggy, and most systems build kernel/modules very quickly anyway. > Nothing, I just didn't know about it! Thanks to all who replied with > the answer... > > -Jake Allan Fields From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 25 11:38:53 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBDB516A4CE for ; Sun, 25 Jul 2004 11:38:53 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7091443D4C for ; Sun, 25 Jul 2004 11:38:53 +0000 (GMT) (envelope-from emilholt@gmail.com) Received: by mproxy.gmail.com with SMTP id 79so48008rnl for ; Sun, 25 Jul 2004 04:38:52 -0700 (PDT) Received: by 10.38.89.38 with SMTP id m38mr396066rnb; Sun, 25 Jul 2004 04:38:52 -0700 (PDT) Message-ID: Date: Sun, 25 Jul 2004 13:38:52 +0200 From: emil To: freebsd-hackers@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: X-Mailman-Approved-At: Sun, 25 Jul 2004 13:29:15 +0000 Subject: Fwd: 801.Q VLAN questions (potential bug?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2004 11:38:53 -0000 I don't know if this is more of a -hackers question or not, but I've come across something weird when trying to resolve the problem stated below; There's actually one single frame being sent across the network with a valid dot1q vlan tag, and that is being transmitted when a client signs on to the WLAN. Then all following traffic shows up as without any vlan tags. Is this a bug with IOS/FreeBSD 5.2.1 or just some other weirdness? regards /emil ---------- Forwarded message ---------- From: emil Date: Fri, 23 Jul 2004 13:47:39 +0200 Subject: 801.Q VLAN questions To: freebsd-questions@freebsd.org Hello, I'm currently in the middle of setting up a couple of Cisco Aironet 1100 802.11b/g access points. I've configured the APs so that they tag ethernet frames depending on what SSID is being used by the WLAN users. (One public and one private SSID). Behind the APs I've set up a FreeBSD 5.2.1p9 box with pf (/usr/ports/security/pf) installed. The FBSD machine currently has 3 intel (fxp) ethernet interfaces: fxp0, management interface. fxp1 interface connected to a small dumb switch which the APs are hooked up to, currently no IP adress configured. fxp2 interface connected to the "net", currently no IP adress configured. Then I also have 2 vlan interfaces with the respective VLAN ID's set, they use fxp1 as their parent interface. What I want to do is to bridge fxp1 and fxp2 and then have pf filter the traffic on the vlans. However, the FBSD machine seems to completely ignore the 802.1Q tags, and not separate the traffic coming to fxp1. So does the hive mind have any ideas of what to do? TIA From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 25 19:03:33 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3AC816A4CE; Sun, 25 Jul 2004 19:03:32 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4B2143D48; Sun, 25 Jul 2004 19:03:29 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6PJ26OF040420; Sun, 25 Jul 2004 13:02:11 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 25 Jul 2004 13:02:20 -0600 (MDT) Message-Id: <20040725.130220.85412071.imp@bsdimp.com> To: bsd@afields.ca From: "M. Warner Losh" In-Reply-To: <20040725022913.GA53935@afields.ca> References: <20040724.160110.127665912.imp@bsdimp.com> <4102EEE6.3020805@anobject.com> <20040725022913.GA53935@afields.ca> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: jhamby@anobject.com cc: freebsd-config@freebsd.org Subject: Re: "Next Generation" kernel configuration? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2004 19:03:33 -0000 In message: <20040725022913.GA53935@afields.ca> Allan Fields writes: : On Sat, Jul 24, 2004 at 04:21:10PM -0700, Jake Hamby wrote: : > M. Warner Losh wrote: : > > : > >What's wrong with adding: : > > : > >makeoptions MODULES_OVERRIDE="a b c" : > >to your config file? It is already supported. : : Though, I've used this before to good effect (on slow crash-box): : : There's no mention to specify exclusions, only what to include. If : you want only a few things excluded, would you not have to list : everything else in each of the same subdirs? : : No biggy, and most systems build kernel/modules very quickly anyway. I've found that typically there are a lot more you want to leave out than you want to leave in. Warner From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 25 21:04:06 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36A0616A4CE for ; Sun, 25 Jul 2004 21:04:06 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA25A43D49 for ; Sun, 25 Jul 2004 21:04:05 +0000 (GMT) (envelope-from espinafre@gmail.com) Received: by mproxy.gmail.com with SMTP id m69so56109rne for ; Sun, 25 Jul 2004 14:04:05 -0700 (PDT) Received: by 10.38.163.63 with SMTP id l63mr601rne; Sun, 25 Jul 2004 14:04:00 -0700 (PDT) Message-ID: <5ef8c2f0040725140372d192bb@mail.gmail.com> Date: Sun, 25 Jul 2004 18:03:57 -0300 From: =?ISO-8859-1?Q?Jos=E9_de_Paula?= To: freebsd-hackers@freebsd.org In-Reply-To: <20040719131503.GA12222@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <5ef8c2f004071419517bdc9f3e@mail.gmail.com> <20040718135541.GA28115@gothmog.gr> <5ef8c2f0040718144648b49ff6@mail.gmail.com> <20040719131503.GA12222@stack.nl> Subject: Re: [PATCH] basic modelines for contrib/nvi X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2004 21:04:06 -0000 On Mon, 19 Jul 2004 15:15:04 +0200, Jilles Tjoelker wrote: > > There are some options which can pose a security risk, including but not > limited to cdpath, tempdir, path and shell. You should make a list of > "safe" options and only allow those in modelines. Thanks for the feedback, stay tuned for nvi modelines improvement! As soon as I have enough time, I'm going to take some forbidden options (for now, they are cdpath, directory, shell, backup and path. Please tell me what other options would be unsafe) and quietly strip them from the modeline. From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 25 22:22:20 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5123716A4CE for ; Sun, 25 Jul 2004 22:22:20 +0000 (GMT) Received: from pc5.i.0x5.de (n.0x5.de [213.146.113.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F18143D53 for ; Sun, 25 Jul 2004 22:22:18 +0000 (GMT) (envelope-from nicolas@i.0x5.de) Received: from pc5.i.0x5.de (nicolas@localhost [127.0.0.1]) by pc5.i.0x5.de (8.12.11/8.12.11) with ESMTP id i6PMMFo0034610; Mon, 26 Jul 2004 00:22:15 +0200 (CEST) (envelope-from nicolas@pc5.i.0x5.de) Received: (from nicolas@localhost) by pc5.i.0x5.de (8.12.11/8.12.11/Submit) id i6PMMFMp034609; Mon, 26 Jul 2004 00:22:15 +0200 (CEST) (envelope-from nicolas) Date: Mon, 26 Jul 2004 00:22:15 +0200 From: Nicolas Rachinsky To: =?iso-8859-1?Q?Jos=E9?= de Paula Message-ID: <20040725222215.GB33560@pc5.i.0x5.de> Mail-Followup-To: =?iso-8859-1?Q?Jos=E9?= de Paula , freebsd-hackers@freebsd.org References: <5ef8c2f004071419517bdc9f3e@mail.gmail.com> <20040718135541.GA28115@gothmog.gr> <5ef8c2f0040718144648b49ff6@mail.gmail.com> <20040719131503.GA12222@stack.nl> <5ef8c2f0040725140372d192bb@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <5ef8c2f0040725140372d192bb@mail.gmail.com> X-Powered-by: FreeBSD X-Homepage: http://www.rachinsky.de X-PGP-Keyid: C11ABC0E X-PGP-Fingerprint: 19DB 8392 8FE0 814A 7362 EEBD A53B 526A C11A BC0E X-PGP-Key: http://www.rachinsky.de/nicolas/nicolas_rachinsky.asc User-Agent: Mutt/1.5.6i cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] basic modelines for contrib/nvi X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2004 22:22:20 -0000 * José de Paula [2004-07-25 18:03 -0300]: > On Mon, 19 Jul 2004 15:15:04 +0200, Jilles Tjoelker wrote: > > > > > There are some options which can pose a security risk, including but not > > limited to cdpath, tempdir, path and shell. You should make a list of > > "safe" options and only allow those in modelines. > > Thanks for the feedback, stay tuned for nvi modelines improvement! As > soon as I have enough time, I'm going to take some forbidden options > (for now, they are cdpath, directory, shell, backup and path. Please > tell me what other options would be unsafe) and quietly strip them > from the modeline. Please follow the above suggestion and make a list of safe options and disallow everything else. Nicolas From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 26 10:08:23 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0F8B16A4CE; Mon, 26 Jul 2004 10:08:23 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44DAD43D49; Mon, 26 Jul 2004 10:08:23 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i6QA8EGh081012 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Jul 2004 13:08:15 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.12.11/8.12.11) id i6QA8FhQ080658; Mon, 26 Jul 2004 13:08:15 +0300 (EEST) (envelope-from ru) Date: Mon, 26 Jul 2004 13:08:14 +0300 From: Ruslan Ermilov To: Alfred Perlstein Message-ID: <20040726100814.GF76937@ip.net.ua> References: <20040716071545.GW95729@elvis.mu.org> <20040716072341.GX95729@elvis.mu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WlEyl6ow+jlIgNUh" Content-Disposition: inline In-Reply-To: <20040716072341.GX95729@elvis.mu.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: hackers@freebsd.org Subject: Re: RFC: "-exit" option for find(1) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2004 10:08:24 -0000 --WlEyl6ow+jlIgNUh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 16, 2004 at 12:23:41AM -0700, Alfred Perlstein wrote: > I'm up too late, this doesn't work because find returns > success whenever it successfully runs thought everything. >=20 > Perhaps the primary change to just "-exit" which would > make find exit successfully, and if the primary is never > encountered (ie. our find logic never hits it) find would > exit with a non-zero exit status? >=20 > Ideas? Better ideas? >=20 > The reason I want this is to avoid extracting a tarball > over a directory that has files in it that are newer than > the tarball. >=20 > Neither tar nor find seem to make this easy... >=20 [ `find . -type f -newer ../src.tar.gz |head -1 |wc -l` -eq 0 ] && echo hi Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --WlEyl6ow+jlIgNUh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBBNgOqRfpzJluFF4RAhaLAJ4uHgRsn1EvadzuUZ29DXmuGfU4tQCglNDt 8cQPL70vRbzGcH44aDhH6So= =WoBq -----END PGP SIGNATURE----- --WlEyl6ow+jlIgNUh-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 25 17:05:04 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 886CC16A4CE for ; Sun, 25 Jul 2004 17:05:04 +0000 (GMT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 0826C43D2F for ; Sun, 25 Jul 2004 17:05:04 +0000 (GMT) (envelope-from jan@evation.com) Received: (qmail 21467 invoked from network); 25 Jul 2004 17:05:03 -0000 Received: from ip51cf88d9.direct-adsl.nl (81.207.136.217) by relay.pair.com with SMTP; 25 Jul 2004 17:05:03 -0000 X-pair-Authenticated: 81.207.136.217 Date: 25 Jul 2004 18:57:00 +0200 From: Jan Branbergen To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: MULTIPART/mixed; BOUNDARY="0-1804289383-1090775103=:9896" Message-Id: <20040725170504.0826C43D2F@mx1.FreeBSD.org> X-Mailman-Approved-At: Mon, 26 Jul 2004 11:52:12 +0000 Subject: Simulate device-file in userland? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2004 17:05:04 -0000 --0-1804289383-1090775103=:9896 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Description: body Dear Sirs, is it appreciated if i introduce myself first? if so, please let me know. i was wondering if it is possible to simulate a device-file ( for example a serial port or videograbbing device ) in userland? i have looked at mkfifo, but i think that does not suit my needs: i am interested in ioctl calls as well. are there any examples in ports? is this possible at all? regards, Jan --0-1804289383-1090775103=:9896-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 26 18:31:57 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E10316A4CE for ; Mon, 26 Jul 2004 18:31:57 +0000 (GMT) Received: from angryfist.fasttrackmonkey.com (angryfist.fasttrackmonkey.com [216.223.196.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B40CA43D70 for ; Mon, 26 Jul 2004 18:31:54 +0000 (GMT) (envelope-from spork@fasttrackmonkey.com) Received: (qmail 2264 invoked by uid 2003); 26 Jul 2004 18:30:28 -0000 Received: from spork@fasttrackmonkey.com by angryfist.fasttrackmonkey.com by uid 1001 with qmail-scanner-1.20 (clamscan: 0.65. Clear:RC:1(216.220.116.154):. Processed in 0.04492 secs); 26 Jul 2004 18:30:28 -0000 Received: from unknown (HELO toad.nat.fasttrackmonkey.com) (216.220.116.154) by 0 with (DHE-RSA-AES256-SHA encrypted) SMTP; 26 Jul 2004 18:30:26 -0000 Date: Mon, 26 Jul 2004 14:30:08 -0400 (EDT) From: Charles Sprickman X-X-Sender: spork@toad.nat.fasttrackmonkey.com To: Peter Jeremy In-Reply-To: <20040722075723.GE3001@cirb503493.alcatel.com.au> Message-ID: <20040726142446.P28049@toad.nat.fasttrackmonkey.com> References: <20040719191408.V28049@toad.nat.fasttrackmonkey.com> <20040720021432.O28049@toad.nat.fasttrackmonkey.com> <20040720092848.GD3001@cirb503493.alcatel.com.au> <20040720135157.Q28049@toad.nat.fasttrackmonkey.com> <20040722075723.GE3001@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: disk recovery help X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2004 18:31:57 -0000 On Thu, 22 Jul 2004, Peter Jeremy wrote: > >command does, but they are fairly certain that it writes it's config at > >the end of the disk, then zeros it from the outside in. > > Which puts an upper limit on the amount of damage done. The only > difficulty with this is that (ISTR) your filesystem begins at the > beginning of the array so the primary superblock should be the first > thing over-written - and fsck would whinge loudly about that. I did get confirmation from Adaptec that it does go from the outside sectors in. > >grabbed the dd "image" before that. An fsck on the problem partition ran > >for 12 hours and I don't know how far along it was. > > Ctrl-T (aka SIGINFO) is your friend - fsck will tell you how far > through its current phase it is. Ah. Hence the reference to stty in the fsck manpage. Thanks! > I was hoping it would also locate all the superblocks - which > would let you verify that the structure looked reasonably sane. > You might also try fsdb(8) - though I think it relies on the primary > superblock being sane. I ended up using sysutils/ffsrecov to grab the alternate superblocks. I have a reasonably OK fsck'd filesystem mounted now. I have another copy to work on, and my question there is this: When you run fsck it creates a "lost+found" directory to put files that are unreferenced anywhere (I think that's the terminology). At some point during the fsck, it starts spitting errors about there not being enough space in "lost+found". Is there any way to remedy that problem? Is there some way to "grow" the filesystem *before* fsck-ing it? The only bit about this in the fsck manpage is the following: "If the lost+found directory does not exist, it is created. If there is insufficient space its size is increased." Thanks to everyone for your help so far. This has been a good learning experience. Charles > Good luck. > > -- > Peter Jeremy > From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 26 19:51:05 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE9C716A4CE for ; Mon, 26 Jul 2004 19:51:05 +0000 (GMT) Received: from mailserv1.neuroflux.com (mailserv1.neuroflux.com [204.228.228.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 723DB43D1D for ; Mon, 26 Jul 2004 19:51:05 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 95926 invoked by uid 89); 26 Jul 2004 19:55:32 -0000 Received: from unknown (HELO www2.neuroflux.com) (127.0.0.1) by localhost with SMTP; 26 Jul 2004 19:55:32 -0000 Received: from 208.4.77.15 (SquirrelMail authenticated user ryans@gamersimpact.com) by www2.neuroflux.com with HTTP; Mon, 26 Jul 2004 13:55:32 -0600 (MDT) Message-ID: <49805.208.4.77.15.1090871732.squirrel@www2.neuroflux.com> Date: Mon, 26 Jul 2004 13:55:32 -0600 (MDT) From: "Ryan Sommers" To: hackers@freebsd.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Question for C++ Experts X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2004 19:51:06 -0000 Pardon my sending this to a FreeBSD list. After searching I couldn't find any other good mailings lists devoted to C++ and this was the only source I knew of that might have someone that could answer my question. I'm working on a project that uses about 3 different coordinate systems and all are closely related. The only differences are in the bounds and representation. As a way to represent all of these I came up with a base class representing the general case and then derived classes for all the specific systems. As part of my class I use constructors that take the coordinates as inputs. As a means of bounds checking I declared a pure virtual function that checks whether it is within the valid bounds of the derived class. The problem I am running into is that it seems to be illegal to call a pure virtual function from an abstract base contructor. I'm not sure exactly why this would be considered an eror; from what I can think of the dynamic binding would be no different than for a binding in a non-constructor function. Anyone know of any tricks to get around this? Or other methods that might allow me to do the correct bounds checking in the constructor as opposed to delaying it to a second 'init' type call? Ryan Sommers ryans@gamersimpact.com From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 26 20:09:48 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 516DA16A4CE for ; Mon, 26 Jul 2004 20:09:48 +0000 (GMT) Received: from tensor.xs4all.nl (tensor.xs4all.nl [194.109.160.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB9EB43D39 for ; Mon, 26 Jul 2004 20:09:47 +0000 (GMT) (envelope-from dimitry@andric.com) Received: from kilgore.dim (kilgore.dim [192.168.0.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.xs4all.nl (Postfix) with ESMTP id E7EF72284A; Mon, 26 Jul 2004 22:09:45 +0200 (CEST) Date: Mon, 26 Jul 2004 22:09:40 +0200 From: Dimitry Andric X-Mailer: The Bat! (v2.12.03) Business X-Priority: 3 (Normal) Message-ID: <629886387.20040726220940@andric.com> To: "Ryan Sommers" In-Reply-To: <49805.208.4.77.15.1090871732.squirrel@www2.neuroflux.com> References: <49805.208.4.77.15.1090871732.squirrel@www2.neuroflux.com> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="----------97961962E89D4F9" cc: hackers@freebsd.org Subject: Re: Question for C++ Experts X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2004 20:09:48 -0000 ------------97961962E89D4F9 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit On 2004-07-26 at 21:55:32 Ryan Sommers wrote: > The problem I am running into is that it seems to be illegal to call > a pure virtual function from an abstract base contructor. This is because you shouldn't call virtual functions from constructors, unless you know what you're doing. :) Try using exceptions, or two-phase initialization. And read a C++ FAQ for more info, i.e.: http://www.parashift.com/c++-faq-lite/strange-inheritance.html#faq-23.3 There's lots more in there, also explaining your other questions. But this is quite offtopic for this list... ------------97961962E89D4F9 Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: GnuPG v1.2.4 (MingW32) iD8DBQFBBWUEsF6jCi4glqMRAqZlAJ9emlYkrvEJankx+S1oeDBXZw6AGQCgkIZp 1T+UUzOZh88yydFtKBjfbYg= =FoFn -----END PGP MESSAGE----- ------------97961962E89D4F9-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 01:58:51 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6C5F16A4CF for ; Tue, 27 Jul 2004 01:58:51 +0000 (GMT) Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6651B43D55 for ; Tue, 27 Jul 2004 01:58:51 +0000 (GMT) (envelope-from chuck_tuffli@agilent.com) Received: from enccos4.cos.agilent.com (enccos4.cos.agilent.com [130.29.152.93]) by msgbas1x.cos.agilent.com (Postfix) with SMTP id E1E5926EC9 for ; Mon, 26 Jul 2004 19:58:50 -0600 (MDT) Received: from relcos2.cos.agilent.com (130.29.152.237) by enccos4.cos.agilent.com (Sigaba Gateway v3.83) with ESMTP id 16825207; Mon, 26 Jul 2004 19:59:16 -0600 Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos2.cos.agilent.com (Postfix) with ESMTP id 93AEA5E4 for ; Mon, 26 Jul 2004 19:58:50 -0600 (MDT) Received: from cre85086tuf.rose.agilent.com (cre85086tuf [130.30.174.150]) ESMTP id SAA09932 for ; Mon, 26 Jul 2004 18:58:49 -0700 (PDT) Received: by cre85086tuf.rose.agilent.com (Postfix, from userid 1001) id 62B2319E2B6; Mon, 26 Jul 2004 18:59:24 -0700 (PDT) Date: Mon, 26 Jul 2004 18:59:24 -0700 From: Chuck Tuffli To: hackers@freebsd.org Message-ID: <20040727015923.GA63284@cre85086tuf.rose.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: bus_alloc_resource question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 01:58:51 -0000 I'm having some trouble adding a bus resource and am hoping someone can point out where I goofed. The host bus to a new x86 chipset has a memory mapped region in PCI space that provides access to status and control registers. For a driver to get access to this region, I figured it should call bus_alloc_resource() the same as for any other memory mapped region. This currently doesn't "just work" as the region is not a part of any device's BARs. To add this region as a resource, I used bus_set_resource() device_t dev; uint32_t e_mem = 0xe0000000; struct resource *ecfg_res; dev = pci_find_device(PCI_VENDOR_INTEL, ...); bus_set_resource(dev, SYS_RES_MEMORY, e_mem, 0xe0000000, 0x10000000); but a subsequent call to bus_alloc_resource() returns NULL ecfg_res = bus_alloc_resource(dev, SYS_RES_MEMORY, &e_mem, 0, ~0, 1, RF_ACTIVE | RF_SHAREABLE); A call to bus_get_resource() shows that the resource did get set as the call returns the correct starting address and count. Is there something else that needs to happen between the set and the alloc? Is this even the correct approach? Thanks in advance! -- Chuck Tuffli Agilent Technologies, Storage Area Networking From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 03:55:34 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7955116A4CE for ; Tue, 27 Jul 2004 03:55:34 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCCB743D53 for ; Tue, 27 Jul 2004 03:55:33 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6R3sZ13003533; Mon, 26 Jul 2004 21:54:35 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 26 Jul 2004 21:54:53 -0600 (MDT) Message-Id: <20040726.215453.22504137.imp@bsdimp.com> To: chuck_tuffli@agilent.com From: "M. Warner Losh" In-Reply-To: <20040727015923.GA63284@cre85086tuf.rose.agilent.com> References: <20040727015923.GA63284@cre85086tuf.rose.agilent.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org Subject: Re: bus_alloc_resource question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 03:55:34 -0000 In message: <20040727015923.GA63284@cre85086tuf.rose.agilent.com> Chuck Tuffli writes: : I'm having some trouble adding a bus resource and am hoping someone : can point out where I goofed. : : The host bus to a new x86 chipset has a memory mapped region in PCI : space that provides access to status and control registers. For a : driver to get access to this region, I figured it should call : bus_alloc_resource() the same as for any other memory mapped region. : This currently doesn't "just work" as the region is not a part of any : device's BARs. To add this region as a resource, I used : bus_set_resource() : : device_t dev; : uint32_t e_mem = 0xe0000000; : struct resource *ecfg_res; : : dev = pci_find_device(PCI_VENDOR_INTEL, ...); : bus_set_resource(dev, SYS_RES_MEMORY, e_mem, 0xe0000000, 0x10000000); : : but a subsequent call to bus_alloc_resource() returns NULL : : ecfg_res = bus_alloc_resource(dev, SYS_RES_MEMORY, &e_mem, : 0, ~0, 1, RF_ACTIVE | RF_SHAREABLE); : : A call to bus_get_resource() shows that the resource did get set as : the call returns the correct starting address and count. Is there : something else that needs to happen between the set and the alloc? Is : this even the correct approach? Thanks in advance! Generally, one doesn't need to set the resource value. Doing so usually indicates the presence of some bug in the system. Also, just because you set a value doesn't mean that it will be honored. It is entirely possible that you picked a bogus resource and the system can't give it to you. The reasons for this are many: it could be in use by another device, it could be that it exceeds the range of the resource, it could be that it failed sanity checks. On the PCI bus, these sanity checks include 'can the address make it through the bridges between it and the host bridge'. If the answer is no, you'll not be able to allocate things. I'd just remove the bus_set_resource entirely. It is almost never needed for pci drivers. There is a bug in your code however: : uint32_t e_mem = 0xe0000000; : ecfg_res = bus_alloc_resource(dev, SYS_RES_MEMORY, &e_mem, : 0, ~0, 1, RF_ACTIVE | RF_SHAREABLE); The third argument is the rid. For the PCI bus, this is the offset in the config space of the BAR you wish to map/allocate. 0xe0000000 is not a valid offset into the config space. Numbers like 0x10 and 0x14 are valid offsets. Chances are this is the source of your problems. You may wish to remove the RF_SHAREABLE as well, since most device drivers aren't designed to share access to their hardware with other devices. Warner From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 07:52:42 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42E8416A4CE for ; Tue, 27 Jul 2004 07:52:42 +0000 (GMT) Received: from mail016.syd.optusnet.com.au (mail016.syd.optusnet.com.au [211.29.132.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B54B43D5C for ; Tue, 27 Jul 2004 07:52:41 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) i6R7qQG16388; Tue, 27 Jul 2004 17:52:28 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i6R7qQVd019716; Tue, 27 Jul 2004 17:52:26 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)i6R7qPqq019715; Tue, 27 Jul 2004 17:52:25 +1000 (EST) (envelope-from pjeremy) Date: Tue, 27 Jul 2004 17:52:25 +1000 From: Peter Jeremy To: Charles Sprickman Message-ID: <20040727075225.GL3001@cirb503493.alcatel.com.au> References: <20040719191408.V28049@toad.nat.fasttrackmonkey.com> <20040720021432.O28049@toad.nat.fasttrackmonkey.com> <20040720092848.GD3001@cirb503493.alcatel.com.au> <20040720135157.Q28049@toad.nat.fasttrackmonkey.com> <20040722075723.GE3001@cirb503493.alcatel.com.au> <20040726142446.P28049@toad.nat.fasttrackmonkey.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040726142446.P28049@toad.nat.fasttrackmonkey.com> User-Agent: Mutt/1.4.2i cc: freebsd-hackers@freebsd.org Subject: Re: disk recovery help X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 07:52:42 -0000 On Mon, 2004-Jul-26 14:30:08 -0400, Charles Sprickman wrote: >I did get confirmation from Adaptec that it does go from the outside >sectors in. In which case one of the first things to be over-written would have been the first superblock and fsck should complain and stop immediately if this is invalid. >I ended up using sysutils/ffsrecov to grab the alternate superblocks. Maybe that was the tool I was thinking of. >I have a reasonably OK fsck'd filesystem mounted now. I have another copy >to work on, and my question there is this: When you run fsck it creates a >"lost+found" directory to put files that are unreferenced anywhere (I >think that's the terminology). At some point during the fsck, it starts >spitting errors about there not being enough space in "lost+found". Is >there any way to remedy that problem? Is there some way to "grow" the >filesystem *before* fsck-ing it? fsck will grow the lost+found directory if necessary but it can only grow it to the limit of the direct blocks (12 filesystem blocks). The only way to pre-grow the lost+found directory would be to mount the filesystem read/write, create a large number of (preferably large) filenames and then delete them[1]. I'm not sure if the fsck code can understand indirect blocks in the lost+found directory so I don't know if this would work. It also relies on the filesystem to be sane enough for normal block allocation to work. One option might be to force a read/write mount, rename lost+found, umount the filesystem and redo the fsck until it fills the new lost+found. Renaming a directory entry is fairly safe, especially if you don't change the entry size. Alternatively, do this with fsdb - which is definitely safe. [1] Directories are only shrunk when an entry is created, not when one is deleted. -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 00:46:47 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07C4616A4CE; Tue, 27 Jul 2004 00:46:47 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20B0943D2D; Tue, 27 Jul 2004 00:46:46 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.2.73] (cpe.125.wat.v126.packetworks.net [64.235.97.125] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6R0rRfu085143; Mon, 26 Jul 2004 18:53:28 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4105A57E.8090708@samsco.org> Date: Mon, 26 Jul 2004 18:44:46 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040702 X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org, hackers@freebsd.org X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/mixed; boundary="------------070602010206010903090202" X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org X-Mailman-Approved-At: Tue, 27 Jul 2004 12:04:08 +0000 Subject: May-June 2004 FreeBSD Status Report X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 00:46:47 -0000 This is a multi-part message in MIME format. --------------070602010206010903090202 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit --------------070602010206010903090202 Content-Type: text/plain; name="report-may-2004-june-2004.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="report-may-2004-june-2004.txt" May-June 2004 Status Report Introduction This installment of the Bi-Monthly Status Report is a few days late, but I'm pleased to say that it is chocked full of over 30 articles. May and June were yet again busy months; the Netperf project passed major milestones and can now be run with the debug.mpsafenet tunable turned on from sources in CVS. The ARM, MIPS, and PPC ports saw quite a bit of progress, as did several other SMPng and Netgraph projects. FreeBSD 5.3 is just around the corner, so don't hesitate to grab a snapshot and test the progress! On a more serious note, it's very important to remember that code freeze for FreeBSD 5.3 will happen on August 15, 2004. This is only a few weeks away and there is still a lot to do. The TODO list for the release can be found at . If you are looking for a way to contribute to the release, this TODO list has several items that are in urgent and in need of attention. Testing is also very important. The tree has had some stability stability problems in the past few weeks, but there are work-arounds that should allow everyone to continue testing and using FreeBSD. We absolutely must have FreeBSD 5.3 be a rock-solid release, so every little bit of contributed effort helps! Thanks, Scott Long * Bluetooth stack for FreeBSD (Netgraph implementation) * ALTQ import * Buf Junta project * CAM Lockdown * Cronyx Adapters Drivers * EuroBSDCon 2004 registration now open * FreeBSD Brazilian Documentation Project * FreeBSD Dutch Documentation Project * FreeBSD Handbook, 3rd Edition, Volume II: Administrator Guide * FreeBSD ports monitoring system * FreeBSD profile.sh * FreeBSD/arm * FreeBSD/MIPS Status Report * HP Network Scanjet 5 * i386 Interrupt Code & PCI Interrupt Routing * Improved Multibyte/Wide Character Support * IPFilter Upgraded to 3.4.35 * KDE on FreeBSD * kgi4BSD * Low-overhead performance monitoring for FreeBSD * Network interface naming changes * Network Stack Locking * Packet Filter - pf * PowerPC Port * Project Mini-Evil * SMPng Status Report * Sync protocols (Netgraph and SPPP) * TTY subsystem realignment * Various GEOM classes and geom(8) utility * VuXML and portaudit Bluetooth stack for FreeBSD (Netgraph implementation) Contact: Maksim Yevmenkin Bluetooth code was marked as non-i386 specific. It is now possible to build it on all supported platforms. Please help with testing. Other then this there was not much progress during last few months. I've been very busy with Real Life. _________________________________________________________________ ALTQ import URL: http://www.csl.sony.co.jp/person/kjc/kjc/software.html#ALTQ URL: http://www.rofug.ro/projects/freebsd-altq/ URL: http://kerneltrap.org/node.php?id=505 URL: http://people.freebsd.org/~mlaier/ALTQ_driver/ Contact: Max Laier The ALTQ framework is part of KAME for more than 4 years and has been adopted by Net- and OpenBSD since more than 3 years. It provides means of managing outgoing packets to do QoS and bandwidth limitations. OpenBSD developed a different way to interact with ALTQ using pf, which was adopted by KAME as the "default for everyday use". The Romanian FreeBSD Users Group has had a project to work towards integration of ALTQ into FreeBSD, which provided a very good starting point for the final import. The import only provides the "pf mode" configuration and classification API as the older ALTQ3 API does not suit to our SMP approach. A reworked configuration API (decoupled from pf) is in the making as are additional driver modifications. Both should be done before 5-STABLE is branched, although additional drivers can be imported during the lifetime of 5-STABLE as well. _________________________________________________________________ Buf Junta project Contact: Poul-Henning Kamp The buf-junta project is underway, I am trying to bisect the code such that we get a struct bufobj which is the handle and method carrier for a buffer-cache object. All vnodes contain a bufobj, but as filesystems get migrated to GEOM backing, bufobj's will exist which do not have an associated vnode. The work is ongoing. _________________________________________________________________ CAM Lockdown Contact: Scott Long Not much coding has taken place on this lately, with the recent focus being on refining the design. We are currently investigating per-CPU completion queues and threads in order to reduce locks and increase concurrency. Also reviewing the BSD/OS CAM lockdown to see what ideas can be shared. Work should hopefully puck back up in late July. Development is taking place in the FreeBSD Perforce repository under the //depot/projects/scottl-camlock/... branch for now. _________________________________________________________________ Cronyx Adapters Drivers URL: http://www.cronyx.ru/hardware/wan.html Contact: Roman Kurakin cp(4) driver for Cronyx Tau-PCI was added. Cronyx Tau-PCI is family of synchronous WAN adapters with various set of interfaces such as V.35, RS-232, RS-530(449), X.21, E1, E3, T3, STS-1. This is a third family of Cronyx adapters that is supported by FreeBSD now. Now all three drivers cx(4), ctau(4) and cp(4) are on both major branches (HEAD and RELENG_4). Busdma conversion was recently finished. Current work is concentrated on locking both for adapters drivers and for sppp (see my other report for additional information). _________________________________________________________________ EuroBSDCon 2004 registration now open URL: http://www.eurobsdcon2004.de/ Contact: Patrick M. Hausen Registration for EuroBSDCon 2004 taking place in Karlsruhe, Germany, from Oct. 29th to 31st has just opened. An early bird discount will be offered to all registering until Aug. 15th. Please see the conference website for details. _________________________________________________________________ FreeBSD Brazilian Documentation Project URL: http://doc.fugspbr.org URL: http://lists.fugspbr.org/listinfo.cgi/doc-fugspbr.org URL: http://developer.berlios.de/projects/doc-br/ Contact: DOC-BR Discussion List The FreeBSD Brazilian Documentation Project is an effort of the Brazilian FreeBSD Users Group (FUG-BR) to translate the available documentation to pt_BR. We are proud to announce that we've finished the Handbook and FDP Primer translation and they are being revised. Both should be integrated to the FreeBSD CVS repository shortly. There are many other articles being translated and their status can be checked at our website. If you want to help please create an account at BerliOS, since our CVS repository is being hosted there, and contact us through our mailing list. Any help is welcome! _________________________________________________________________ FreeBSD Dutch Documentation Project URL: http://www.evilcoder.org/freebsd_html URL: http://www.evilcoder.org/freebsd/handbook.tbz URL: http://www.evilcoder.org/freebsd/html.tbz Contact: Remko Lodder The FreeBSD Dutch Documentation project is a ongoing project translating the FreeBSD handbook {and others} to the dutch language. We are still on the look for translators and people that are willing to check the current html documentation. If you are interested, contact me at the email address shown above. We currently are reading for some checkups and then insert the first documents into the documentation tree. _________________________________________________________________ FreeBSD Handbook, 3rd Edition, Volume II: Administrator Guide URL: http://www.freebsd.org/docproj/handbook3.html Contact: Murray Stokely The Third Edition of the FreeBSD Handbook has been split into two volumes. The first volume, the User Guide, has been published. Work is progressing on the second volume. The following chapters are included in the second volume : advanced-networking, network-servers, config, boot, cutting-edge, disks, l10n, mac, mail, ppp-and-slip, security, serialcomms, users, vinum, eresources, bibliography, mirrors. Please see the Task List for information about what work remains to be done. In addition to technical and grammatical review, a number of HTML output assumptions in the document need to be corrected. _________________________________________________________________ FreeBSD ports monitoring system URL: http://portsmon.firepipe.net/index.html Contact: Mark Linimon The system continues to function well. The accuracy of the automatic classification algorithm has been improved by assigning a higher priority to port names found in pieces of Makefiles. Several bugs had to be fixed due to the transition from bento to pointyhat. For about two weeks the URLs to the build errors were wrong. This has now been corrected (but note that some of the pointyhat summary pages themselves still show the broken links.) A report was added to show only PRs in the 'feedback' state, so that committers can focus on maintainer and/or responsible timeouts. (As a reminder, the policy is 2 weeks). Another report on 'ports that are in ports/MOVED, but still exist' has also been added to the Anomalies page. Sometimes these are actual errors but not always. Here are my latest observations about the trends in ports PRs: * We were (very briefly) down to 650 ports PRs. From looking at the graphs, this appears to be the lowest number since 2001. This is despite the fact that between the two time periods the number of ports had increased 70%. * We have made a little bit of progress on the number of PRs which apply to existing ports and have been assigned to a FreeBSD committer, from 400 to around 350. This is partly due to some committers going through the database, putting old PRs into the 'feedback' state, and then later invoking the 'maintainer timeout' rule mentioned above. (In some cases the PRs are now too old to still apply, and those are just closed.) * A few maintainers are currently responsible for one-third of those 350. Please, if you feel that you are over committed, consider asking for new volunteers to maintain these ports. * In terms of build errors, there is some new breakage from the preliminary testing with gcc3.4, which is even stricter with respect to the code it will accept than was gcc3.3. Many of these errors are shown as 'unknown' by the classification script. I have submitted a patch to fix this. * The majority of the build errors are still due to compilation problems, primarily from the gcc upgrades. Since FreeBSD tends to be at the forefront of gcc adaptation, this is to be expected, but IMHO we should really try to fix as many of these as possible before 5.3 is released. * The next highest number of build errors are caused by code that does not build on our 64-bit architectures due to the assumption that "all the world's a PC". Here is the entire list; the individual bars are clickable. _________________________________________________________________ FreeBSD profile.sh URL: https://projects.fsck.ch/profile/ Contact: Tobias Roth FreeBSD profile.sh is an enhancement to the FreeBSD 5 rcng boot system, targeted at laptops. One can configure multiple network environments (eg, home, work, university). After this initial configuration, the laptop detects automatically in what environment it is started and configures itself accordingly. Not only network settings, but almost everything from under /etc can be configured per environment. It is also possible to suspend the machine in one environment and wake it up in a different one, and reconfiguration will happen automatically. _________________________________________________________________ FreeBSD/arm Contact: Olivier Houchard Not much to report, Xscale support is in progress, and should boot at least single user really soon on an Intel IQ31244 Evaluation board. _________________________________________________________________ FreeBSD/MIPS Status Report URL: http://www.FreeBSD.org/projects/mips/ URL: http://www.mdstud.chalmers.se/~md1gavan/mips64emul/ Contact: Juli Mallett In the past two months, opportunities to perform a good chunk of work on FreeBSD/MIPS have arisen and significant issues with context switching, clocks, interrupts, and kernel virtual memory have been resolved. A number of issues with caches were fixed, however those are far from complete and at last check, there were issues when running cached which would prevent booting sometimes. Due to toolchain issues in progress, current kernels are no longer bootable on real hardware. A 64-bit MIPS emulator has arisen giving the ability to test and debug in an emulator, and much testing has taken place in it. It has been added to the FreeBSD ports tree, and the port will be actively tracking the main codebase as possible. In general, FreeBSD/MIPS kernels should run fine in it. Before toolchain and cache issues, the first kernel threads would run, busses and some devices would attach, and the system would boot to a mountroot prompt. _________________________________________________________________ HP Network Scanjet 5 URL: http://berklix.com/scanjet/ Contact: Julian Stacey HP Network Scanjet 5 can unobtrusively run FreeBSD inside the scanner. Those who miss their Unix at work can have a FreeBSD box, un-noticed & un-challenged by blinkered managers who block any non Microsoft PC in the building. http://berklix.com/scanjet/ _________________________________________________________________ i386 Interrupt Code & PCI Interrupt Routing Contact: John Baldwin Support for programming the polarity and trigger mode of interrupt sources at runtime was added. This includes a mini-driver for the ELCR register used to control the configuration for ISA and EISA interrupts. The atpic driver reprograms the ELCR as necessary, while the apic driver reprograms the interrupt pin associated with an interrupt source as necessary. The information about which configuration to use mostly comes from ACPI. However, non-ACPI systems also force any ISA interrupts used to route PCI interrupts to use active-low polarity and level trigger. Support for suspend and resume on i386 was also slightly improved. Suspend and resume support was added to the ELCR, $PIR, and apic drivers. The ACPI PCI-PCI bridge driver was fixed to fall back to the PCI-PCI bridge swizzle method for routing interrupts when a routing table was not provided by the BIOS. Mixed mode can now be disabled or enabled at boot time via a loader tunable. _________________________________________________________________ Improved Multibyte/Wide Character Support Contact: Tim Robbins Many more text-processing utilities in the FreeBSD base system have been updated to work with multibyte characters, including comm, cut, expand, fold, join, paste, unexpand, and uniq. New versions of GNU grep and GNU sort (from coreutils) have been imported, together with multibyte support patches from developers at IBM and Red Hat. Future work will focus on modifying the regular expression functions to work with multibyte characters, improving performance of the C library routines, and updating the remaining utilities (sed and tr are two important ones still remaining). _________________________________________________________________ IPFilter Upgraded to 3.4.35 URL: http://coombs.anu.edu.au/~avalon/ip-filter.html Contact: Darren Reed IPFilter has been upgraded in both FreeBSD-current and 4-STABLE (post 4.10) from version 3.4.31 to 3.4.35. _________________________________________________________________ KDE on FreeBSD URL: http://freebsd.kde.org Contact: Michael Nottebrock The work on converting the build switches/OPTIONS currently present in the ports of the main KDE modules into separate ports in order to make packages available for the software/features they provide is progressing. Porting of KOffice 1.3.2 are nearly completed. The swedish FreeBSD snapshot server , operated and maintained by members of the KDE/FreeBSD team, is back up and running at full steam. Additional amd64 hardware has been added and amd64 snapshots will be available soon. _________________________________________________________________ kgi4BSD URL: http://www.FreeBSD.org/~nsouch/kgi4BSD Contact: Nicholas Souchu KGI is going slowly but surely. The port of the KGI/Linux accel to FreeBSD is in progress. It's no more than a double buffering API for graphic command passing to the HW engine. Most of the work in the past months was about console management and more especially dual head console. Otherwise a new driver building tree is now ready to compile Linux and FreeBSD drivers in the same tree. Documentation about KGI design is in progress. _________________________________________________________________ Low-overhead performance monitoring for FreeBSD URL: Contact: Joseph Koshy The current design attempts to support both per-process and system-wide statistical profiling and per-process "virtual" performance counters. The userland API libpmc(3) is somewhat stable now, but the kernel module's design is being redone to handle MP better. Initial development is targeting the AMD Athlon CPUs, but the intent is to support all the CPUs that FreeBSD runs on. An early prototype is available under Perforce [under //depot/user/jkoshy/projects/pmc/]. _________________________________________________________________ Network interface naming changes Contact: Brooks Davis An enhanced network interface cloning API has been committed. It allows interfaces to support more complex names then the current name# style. This functionality has been used to enable interesting cloners like auto-configuring vlan interfaces. Other features include locking of cloner structures and the ability of drivers to reject destroy requests. Work on userland support for this functionality is ongoing. _________________________________________________________________ Network Stack Locking URL: http://www.freebsd.org/smp/ URL: http://www.watson.org/~robert/freebsd/netperf/ Contact: Robert Watson This project is aimed at converting the FreeBSD network stack from running under the single Giant kernel lock to permitting it to run in a fully parallel manner on multiple CPUs (i.e., a fully threaded network stack). This will improve performance/latency through reentrancy and preemption on single-processor machines, and also on multi-processor machines by permitting real parallelism in the processing of network traffic. As of FreeBSD 5.2, it was possible to run low level network functions, as well as the IP filtering and forwarding plane, without the Giant lock, as well as "process to completion" in the interrupt handler. This permitted both inbound and outbound traffic to run in parallel across multiple interfaces and CPUs. Work continues to improve the maturity and completeness of the locking (and performance) of the network stack for 5.3. The network stack development branch has been updated to the latest CVS HEAD, as well as the following and more. Many but not all of these changes have been merged to the FreeBSD CVS tree as of the writing of this report. Complete details and more minor changes are documented in the README file on the netperf web page. * Addition of hard-coded WITNESS lock orders for socket-related locks, route locks, interface locks, file descriptor locks, SLIP, and PCB locks for various protocols (UDP, TCP, UNIX domain sockets). (Merged) * Modifed MAC Framework to use inpcbs as the source for mbuf labels rather than reaching up to the socket layer, avoiding the additional acquisition of socket locks. Locked access to so_label and so_peerlabel using the socket lock throughout; assert socket lock in the MAC Framework where depended on. MAC Framework now makes a copy of the socket label before externalizing to prevent a copyout while holding the label lock (and potentially seeing an inconsistent label). (Merged) * Extensive annotation of locking state throughout the network stack, especially relating to sockets. * Several locking fixes for ng_base.c, the basic Netgraph infrastructure. (Merged) * Global accept filter list locking, especially during registration. (Partially merged) * Revise locking in socket state transition helpers, such as soisconnecting(), soisconnected(), etc, to simplify lock handling. (Merged) * Fix bugs in netatalk DDP locking, merge all netatalk locking to CVS. (Merged) * soref() socket locking assertions and associated fixes. (Merged) * Fifofs now uses its own mutex instead of the vnode interlock to synchronize fifo operations, avoiding lock order issues with socket buffer locking. (Merged) * Cleanup of locking related to file descriptor close and Giant requirements. Experimentation with reducing locking here. * Review and fix several instances of socket locking in the TCP code. (Merged) * NFS server locking merged to FreeBSD CVS. (Merged) * Accept locking merged to rwatson_netperf, and to FreeBSD CVS. A new global mutex, accept_mtx, now protects all socket related accept queue and state fields (SS_COMP, SS_INCOMP), and flags relating to accept are moved from the generic so_state field to so_qstate. accept1() rearranged, as with sonewconn() as a result, and a file descriptor leak fixed. Close a variety of races in socket referencing during accept. soabort() and other partially connected socket related functions updated to take locking into account. (Merged) * Issue associated with non-atomic setting of SS_NBIO in fifofs resolved by adding MSG_NBIO. (Merged) * Several flags from so_state moved to sb_state so they can be locked properly using the socket buffer mutex. (Merged) * Socket locks are now not held over calls into the protocol preventing many lock order issues between socket and protocol locks, and avoiding a substantial amount of conditional locking. (Merged) * mbuma, the UMA-based mbuf allocator, is merged to CVS. This reduces the kernel to one widely used memory allocator, improves performance, and allows memory from mbufs to be reclaimed and reused for other types of storage when pressure lowers. (Merged) * sb_flags now properly locked. (Merged) * Global MAC label ifnet lock introduced to protect labels on network interfaces. (Merged) * Rewrites of parts of soreceive() and sosend() to improve MP safety merged to CVS, including modifications to make sure socket buffer cache state is consistent when locks are released. sockbuf_pushsync() added to guarantee consistency of cached pointers. (Merged) * UNIX domain socket locking revised to use a subsystem lock due to inconsistencies in lock order and inconsistent coverage ofunpcb fields. Cleanup of global variable locking in UNIX domain sockets, Giant handling when entering VFS. All UNIX domain socket locking merged to CVS. (Merged) * netisr dispatch introduced in the routing code such that routing socket message delivery is performed asynchronously from routing events to avoid lock order issues. (Merged) * IGMP and multicast locking merged to CVS. (Merged) * Cleanup of lasting recursive Giant acquisition left over from forwarding/bridging plane only locking. (Merged) * ALTQ imported into the FreeBSD in a locked state. (Merged) * Conditional locking in sbdrop(), sbdroprecord(), sbrelease(), sbflush(), spappend(), sbappendstream(), sbappendrecord(), sbinsertoob(), sbappendaddr(), sbappendcontrol() eliminated. (Merged) * Some cleanup of IP stack management ioctls and lock order issues. (Merged) * Cleanup and annotation of sorflush() use of a temporary stack held socket buffer during flush. (Merged) * Substantial cleanup of socket wakeup mechanisms to drop locks in advance of wakeup, avoid holding locks over upcalls, and assertions of proper lock state. (Merged) * With the integration of revised ifnet cloning, cloning data structures are now better locked. (Merged) * Socket locking for portalfs. (Merged) * Global so_global_mtx introduced to protect generation numbers and socket counts. (Merged) * KAME IPSEC and FAST_IPSEC now use rawcb_mtx to protect raw socket list integration. More work required here. (Merged) * Socket locking around SO_SNDLOWAT and SO_RCVLOWAT. (Merged) * soreserve() and sbreserve() reformulation to improve locking and consistency. Similar cleanup in the use of reservation functions in tcp_mss(). (Merged) * Locking cost reduction in sbappend*(). (Merged) * Global locking for a number of Netgraph modules, including ng_iface, ng_ppp, ng_socket, ng_pppoe, ng_frame_relay, ng_tty, ng_eiface. (Merged) * IPv6 inpcb locking. Resulting cleanup of inpcb locking assertions, and enabling of inpcb locking assertions by default even with IPv6 compiled in. * if_xl now MPSAFE. (Merged) * soreceive() non-inline OOB support placed in its own function. (Merged) * NFS client socket locking. (Merged) * SLIP now uses a asynchronous task queue to prevent Giant-free entrance of the TTY code. * E-mail sent to current@ providing Giant-free operation guidelines and details. _________________________________________________________________ Packet Filter - pf URL: http://www.benzedrine.cx/pf.html Contact: Max Laier Contact: Daniel Hartmeier We imported pf as of OpenBSD 3.5 stable on June, 17th which will be the base for 5-STABLE pf (according to the current schedule). The most important improvement in this release is the new interface handling which makes it possible to write pf rule sets for hot-pluggable devices and pseudo cloning devices, before they exist. The import of the ALTQ framework enabled us to finally provide the related pf functions as well. Before 5-STABLE we will import some bug fixes from OpenBSD-current, which have not been merged to their stable branch, as well as some FreeBSD specific features. The planned ALTQ API make-over will also affect pf. We are (desperately) looking for non-manpage documentation for FreeBSD pf and somebody to write it. Few things have changed so a port of the excellent "PF FAQ" on the OpenBSD homepage should be fitting. There are, however, a couple of points that need conversion. A simple tutorial how to setup a NAT gateway with pf would also help. The in-kernel NAT engine is very easy to use, we should tell people about this alternative. This is even more true since the pf module now plugs into GENERIC without modifications. _________________________________________________________________ PowerPC Port Contact: Peter Grehan The port has been moving along steadily. There have been reports of buildworld running natively. Works is almost complete on make release so there will be bootable CD images in the near future. _________________________________________________________________ Project Mini-Evil Contact: Scott Long Project Mini-Evil is an attempt to extend Bill Paul's 'Project Evil' Windows NDIS wrapper layer to the SCSI MiniPort and StorePort layers. While drivers exist for most storage controllers that are on the market today, many companies are integrating software RAID into their products but not providing any source code or design specs. Instead of constantly reverse-engineering these raid layers and attempting to shoehorn them into the ata-raid driver, Project Mini-Evil will run the Windows drivers directly. It will hopefully also run most any SCSI/ATA/RAID drivers that conform to the SCSI Miniport or Storeport specification. Work on this project is split between making the NDIS wrapper code more general and implementing the new APIs. Development is taking place in the FreeBSD Perforce repository under the //depot/projects/sonofevil/... branch. _________________________________________________________________ SMPng Status Report URL: http://www.FreeBSD.org/smp/ Contact: John Baldwin Contact: Not a lot happened on the SMPng front outside of the work on locking the network stack (which is a large amount of work). The priorities of the various software interrupt threads were corrected and locking for taskqueues was improved. The return value of the sema_timedwait() function was adjusted to be more consistent with cv_timedwait(). A small fix was made to the sleepqueue code to shorten the amount of time that a sleepqueue chain lock is held when waking up threads. Some simple debug code for profiling the hash tables used in the sleep queue and turnstile code was added. This will allow developers to measure the impact of any tweaks to the hash table sizes or the hash algorithm. _________________________________________________________________ Sync protocols (Netgraph and SPPP) URL: http://www.freebsd.org/~rik Contact: Roman Kurakin Currently I work on two directions: if_spppfr.c and sppp locking (on behalf of netperf). At the moment of writing this sppp locking is not ready yet. But it would be ready in couple of days. Also you may find as a part of this work some user space fixes for rwatson netperf code (Only that I was able to catch while world compilation. If you know some others let me know and I'll try to fix them too). Since sppp code is quite big and state machine is very complicated, it would be difficult to test all code paths. I will glad to get any help in testing all this stuff. More tester more probability to test all possible cases. Work on FRF.12 (ng_frf12) is frozen since of low interest and lack of time. Current state of stable code: support of FRF.12 End-to-End fragmentation. Support of FRF.12 Interface (UNI and NNI) fragmentation is not tested. _________________________________________________________________ TTY subsystem realignment Contact: Poul-Henning Kamp An effort to get the tty subsystem out from under Giant has morphed into an more general effort to eliminate a lot of code which have been improperly copy & pasted into device drivers. In an ideal world, tty drivers would never get near a cdevsw, but since some drivers are more than just tty drivers (for instance sync) a more sensible compromise must be reached. The work is ongoing. _________________________________________________________________ Various GEOM classes and geom(8) utility Contact: Pawel Jakub Dawidek I'm working on various GEOM classes. Some of them are already committed and ready for use (GATE, CONCAT, STRIPE, LABEL, NOP). The MIRROR class is finished in 90% and will be committed in very near future. Next I want to work on RAID3 and RAID5 implementations. Userland utility to control GEOM classes (geom(8)) is already in the tree. _________________________________________________________________ VuXML and portaudit URL: http://www.vuxml.org URL: http://vuxml.FreeBSD.org URL: http://people.freebsd.org/ports/portaudit/ Contact: Tom Rhodes The portaudit utility is currently an add-on to FreeBSD designed to give administrators and users a heads up with regards to security vulnerabilities in third party software. The VuXML database keeps a record of these security vulnerabilities along with internal security holes. When installed, the portaudit utility periodically downloads a database with known issues and checks all installed ports or packages against it; should it find vulnerable software installed the administrator or user is notified during the daily run output of the periodic scripts. These utilities are considered to be of production quality and discussion is taking place over whether or not they should be included as part of the base system. All ports committers are urged to add entries when when a vulnerability is discovered; any questions may be sent to eik@ or myself. _________________________________________________________________ --------------070602010206010903090202-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 12:29:53 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B887816A4CE for ; Tue, 27 Jul 2004 12:29:53 +0000 (GMT) Received: from k6.locore.ca (k6.locore.ca [205.233.216.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7648A43D46 for ; Tue, 27 Jul 2004 12:29:53 +0000 (GMT) (envelope-from jake@locore.ca) Received: by k6.locore.ca (Postfix, from userid 1000) id C6C15A923; Tue, 27 Jul 2004 08:29:52 -0400 (EDT) Date: Tue, 27 Jul 2004 08:29:52 -0400 From: Jake Burkholder To: Chuck Tuffli Message-ID: <20040727122952.GC18793@locore.ca> References: <20040727015923.GA63284@cre85086tuf.rose.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040727015923.GA63284@cre85086tuf.rose.agilent.com> User-Agent: Mutt/1.4.2.1i cc: hackers@freebsd.org Subject: Re: bus_alloc_resource question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 12:29:53 -0000 Apparently, On Mon, Jul 26, 2004 at 06:59:24PM -0700, Chuck Tuffli said words to the effect of; > I'm having some trouble adding a bus resource and am hoping someone > can point out where I goofed. > > The host bus to a new x86 chipset has a memory mapped region in PCI > space that provides access to status and control registers. For a > driver to get access to this region, I figured it should call > bus_alloc_resource() the same as for any other memory mapped region. > This currently doesn't "just work" as the region is not a part of any > device's BARs. To add this region as a resource, I used > bus_set_resource() > > device_t dev; > uint32_t e_mem = 0xe0000000; > struct resource *ecfg_res; > > dev = pci_find_device(PCI_VENDOR_INTEL, ...); > bus_set_resource(dev, SYS_RES_MEMORY, e_mem, 0xe0000000, 0x10000000); > > but a subsequent call to bus_alloc_resource() returns NULL > > ecfg_res = bus_alloc_resource(dev, SYS_RES_MEMORY, &e_mem, > 0, ~0, 1, RF_ACTIVE | RF_SHAREABLE); > > A call to bus_get_resource() shows that the resource did get set as > the call returns the correct starting address and count. Is there > something else that needs to happen between the set and the alloc? Is > this even the correct approach? Thanks in advance! If this is anything like the soekris board where 0xe0000000 is just a physical address that you want to map in and read or write you can use pmap_mapdev as a quick way to do it, eg, volatile void *ptr = pmap_mapdev(0xe0000000, ...); Be warned that this, as well as bus_alloc_resource(SYS_RES_MEMORY), will allocate virtual address space for the mapping, so you should only map in exactly what you need, I imagine its just a page or 2. 0x10000000 is way too much, you will not be able to allocate that much virtual address space. Jake From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 15:39:00 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2A3B16A4CE for ; Tue, 27 Jul 2004 15:39:00 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53DE643D1D for ; Tue, 27 Jul 2004 15:39:00 +0000 (GMT) (envelope-from marks@dell-laptop.6bone.nl) Received: by postman.ripe.net (Postfix, from userid 8) id B90A94E5A9; Tue, 27 Jul 2004 17:38:59 +0200 (CEST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 7654B4E546; Tue, 27 Jul 2004 17:38:59 +0200 (CEST) Received: from dell-laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id i6RFcR1o032383; Tue, 27 Jul 2004 17:38:42 +0200 Received: (nullmailer pid 3061 invoked by uid 1001); Tue, 27 Jul 2004 15:38:25 -0000 Date: Tue, 27 Jul 2004 17:38:25 +0200 From: Mark Santcroos To: Jan Branbergen Message-ID: <20040727153825.GA2645@laptop.6bone.nl> References: <20040725170504.0826C43D2F@mx1.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040725170504.0826C43D2F@mx1.FreeBSD.org> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Status: N 0.000018 / 0.0 / 0.0 / disabled X-RIPE-Signature: 30db0b0205e94de856cc0a59a3d2d7e6 cc: freebsd-hackers@freebsd.org Subject: Re: Simulate device-file in userland? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 15:39:00 -0000 On Sun, Jul 25, 2004 at 06:57:00PM +0200, Jan Branbergen wrote: Content-Description: body > i was wondering if it is possible to simulate a device-file ( for example a serial port or videograbbing device ) in userland? You may want to look at ng_device. Be prepared for rough edges though ;) Mark From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 16:02:11 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BC6516A4CE for ; Tue, 27 Jul 2004 16:02:11 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51CF443D46 for ; Tue, 27 Jul 2004 16:02:10 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received-SPF: pass (eva.fit.vutbr.cz: domain of xdivac02@eva.fit.vutbr.cz designates 127.0.0.1 as permitted sender) receiver=eva.fit.vutbr.cz; client_ip=127.0.0.1; envelope-from=xdivac02@eva.fit.vutbr.cz; Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.12.11/8.12.11) with ESMTP id i6RG26Ra001823 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 27 Jul 2004 18:02:06 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.12.11/8.12.5/Submit) id i6RG26bp001822 for hackers@freebsd.org; Tue, 27 Jul 2004 18:02:06 +0200 (CEST) Date: Tue, 27 Jul 2004 18:02:06 +0200 From: Divacky Roman To: hackers@freebsd.org Message-ID: <20040727160206.GA1784@stud.fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Subject: new files in kernel build X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 16:02:11 -0000 Hi, If I want to add some files into kernel sources, what am I supposed to do to them compile? I added some into sys/net80211/ but they dont compile... I tried sys/conf/files but it does help, just prints a message about having it defined before... thnx for help roman From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 16:10:45 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1205516A4CE for ; Tue, 27 Jul 2004 16:10:45 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AAE843D31 for ; Tue, 27 Jul 2004 16:10:44 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6RG8USu011281; Tue, 27 Jul 2004 10:08:30 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 27 Jul 2004 10:08:48 -0600 (MDT) Message-Id: <20040727.100848.15611424.imp@bsdimp.com> To: xdivac02@stud.fit.vutbr.cz From: "M. Warner Losh" In-Reply-To: <20040727160206.GA1784@stud.fit.vutbr.cz> References: <20040727160206.GA1784@stud.fit.vutbr.cz> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org Subject: Re: new files in kernel build X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 16:10:45 -0000 In message: <20040727160206.GA1784@stud.fit.vutbr.cz> Divacky Roman writes: : Hi, : : If I want to add some files into kernel sources, what am I supposed to do to : them compile? I added some into sys/net80211/ but they dont compile... : : I tried sys/conf/files but it does help, just prints a message about having it : defined before... Exact error messages would be helpful. Generally, you put them in sys/conf/files, re-run config and life is good. Warner From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 16:50:56 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43BEC16A4CE for ; Tue, 27 Jul 2004 16:50:56 +0000 (GMT) Received: from msgbas2x.cos.agilent.com (msgbas2x.cos.agilent.com [192.25.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A9CC43D31 for ; Tue, 27 Jul 2004 16:50:56 +0000 (GMT) (envelope-from chuck_tuffli@agilent.com) Received: from enccos4.cos.agilent.com (enccos4.cos.agilent.com [130.29.152.93]) by msgbas2x.cos.agilent.com (Postfix) with SMTP id 6D6A07F9D; Tue, 27 Jul 2004 10:50:55 -0600 (MDT) Received: from relcos1.cos.agilent.com (130.29.152.239) by enccos4.cos.agilent.com (Sigaba Gateway v3.83) with ESMTP id 17118770; Tue, 27 Jul 2004 10:51:20 -0600 Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos1.cos.agilent.com (Postfix) with ESMTP id 09BFF15E; Tue, 27 Jul 2004 10:50:55 -0600 (MDT) Received: from cre85086tuf.rose.agilent.com (cre85086tuf [130.30.174.150]) ESMTP id JAA19892; Tue, 27 Jul 2004 09:50:51 -0700 (PDT) Received: by cre85086tuf.rose.agilent.com (Postfix, from userid 1001) id 3D15419E2B6; Tue, 27 Jul 2004 09:51:25 -0700 (PDT) Date: Tue, 27 Jul 2004 09:51:25 -0700 From: Chuck Tuffli To: "M. Warner Losh" , Jake Burkholder Message-ID: <20040727165124.GA64121@cre85086tuf.rose.agilent.com> References: <20040727015923.GA63284@cre85086tuf.rose.agilent.com> <20040726.215453.22504137.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040726.215453.22504137.imp@bsdimp.com> User-Agent: Mutt/1.4i cc: hackers@freebsd.org Subject: Re: bus_alloc_resource question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 16:50:56 -0000 On Mon, Jul 26, 2004 at 09:54:53PM -0600, M. Warner Losh wrote: ... > Generally, one doesn't need to set the resource value. Doing so > usually indicates the presence of some bug in the system. Also, just I realize now that the original email wasn't clear. This is a bus driver for a new bus. Think of the physical addresses from 0xe0000000 - 0xefffffff as being a memory mapped config space for devices. Each 4KB segment of this region maps the configuration space for every possible bus, device, function number combination. I was thinking that each of these segments was a bus resource, but maybe that isn't the right approach. Any thoughts as to a better approach? Jake Burkholder suggested using pmap_mapdev() for small sections of memory, but cautioned that this uses up virtual address space. The bus driver could map each segment to test if a device was there and unmap the segments that didn't contain devices. -- Chuck Tuffli Agilent Technologies, Storage Area Networking From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 17:15:25 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D81916A4CE for ; Tue, 27 Jul 2004 17:15:25 +0000 (GMT) Received: from k6.locore.ca (k6.locore.ca [205.233.216.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id C64E543D2D for ; Tue, 27 Jul 2004 17:15:24 +0000 (GMT) (envelope-from jake@locore.ca) Received: by k6.locore.ca (Postfix, from userid 1000) id D9E26A923; Tue, 27 Jul 2004 13:15:23 -0400 (EDT) Date: Tue, 27 Jul 2004 13:15:23 -0400 From: Jake Burkholder To: Chuck Tuffli Message-ID: <20040727171523.GE18793@locore.ca> References: <20040727015923.GA63284@cre85086tuf.rose.agilent.com> <20040726.215453.22504137.imp@bsdimp.com> <20040727165124.GA64121@cre85086tuf.rose.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040727165124.GA64121@cre85086tuf.rose.agilent.com> User-Agent: Mutt/1.4.2.1i cc: hackers@freebsd.org Subject: Re: bus_alloc_resource question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 17:15:25 -0000 Apparently, On Tue, Jul 27, 2004 at 09:51:25AM -0700, Chuck Tuffli said words to the effect of; > On Mon, Jul 26, 2004 at 09:54:53PM -0600, M. Warner Losh wrote: > ... > > Generally, one doesn't need to set the resource value. Doing so > > usually indicates the presence of some bug in the system. Also, just > > I realize now that the original email wasn't clear. This is a bus > driver for a new bus. Think of the physical addresses from 0xe0000000 > - 0xefffffff as being a memory mapped config space for devices. Each > 4KB segment of this region maps the configuration space for every > possible bus, device, function number combination. I was thinking that > each of these segments was a bus resource, but maybe that isn't the > right approach. Any thoughts as to a better approach? > > Jake Burkholder suggested using pmap_mapdev() for small sections of > memory, but cautioned that this uses up virtual address space. The bus > driver could map each segment to test if a device was there and unmap > the segments that didn't contain devices. Ok, I think what you want to do is make an rman (resource manager) that manages the device memory, and that child devices will allocate from. In your attach routine you would then probe the bus by mapping in portions of whatever size you need and adding the child device's resources to a resource list, for each child found. An example of this (oddly enough) is the sparc64 nexus (in -current), sparc64/sparc64/nexus.c, and the sparc64 sbus driver, sparc64/sbus/sbus.c. The MI pci bus drivers as well, but this is a bit closer to what you're doing, I think. You won't be able to allocate the region from pci unless its described by pci, but that doesn't really matter as long as no one else tries to use it. HTH, Jake From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 17:30:06 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEBB516A4CE for ; Tue, 27 Jul 2004 17:30:06 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D338E43D48 for ; Tue, 27 Jul 2004 17:30:06 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 09E1A7A481; Tue, 27 Jul 2004 10:30:06 -0700 (PDT) Message-ID: <4106911D.6090201@elischer.org> Date: Tue, 27 Jul 2004 10:30:05 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: "M. Warner Losh" References: <20040727160206.GA1784@stud.fit.vutbr.cz> <20040727.100848.15611424.imp@bsdimp.com> In-Reply-To: <20040727.100848.15611424.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: xdivac02@stud.fit.vutbr.cz cc: hackers@freebsd.org Subject: Re: new files in kernel build X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 17:30:07 -0000 M. Warner Losh wrote: >In message: <20040727160206.GA1784@stud.fit.vutbr.cz> > Divacky Roman writes: >: Hi, >: >: If I want to add some files into kernel sources, what am I supposed to do to >: them compile? I added some into sys/net80211/ but they dont compile... >: >: I tried sys/conf/files but it does help, just prints a message about having it >: defined before... > >Exact error messages would be helpful. > >Generally, you put them in sys/conf/files, re-run config and life is >good. > if you want to add these files without editing /sys/conf/files you can add them to /sys/conf//files.{YOURCONFIG} e.g. we backported the firewire to an older kernel and have a proprietary driver as well.. our files.VICOR looks like: %cat files.VICOR xdcpdrvr.o optional xdcp \ dependency "$S/dev/xdcp/xdcpdrvr.o.uu" \ compile-with "uudecode < $S/dev/xdcp/xdcpdrvr.o.uu" \ no-implicit-rule dev/firewire/firewire.c optional firewire dev/firewire/fwcrom.c optional firewire dev/firewire/fwdev.c optional firewire dev/firewire/fwmem.c optional firewire dev/firewire/fwohci.c optional firewire dev/firewire/fwohci_pci.c optional firewire pci dev/firewire/if_fwe.c optional fwe dev/firewire/sbp.c optional sbp without looking at the source to config, it seems to use teh entry on the 'ident' line to look for these files.. > >Warner >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 18:43:17 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B58DF16A4CE for ; Tue, 27 Jul 2004 18:43:17 +0000 (GMT) Received: from web21525.mail.yahoo.com (web21525.mail.yahoo.com [66.163.170.144]) by mx1.FreeBSD.org (Postfix) with SMTP id 8EB2743D5D for ; Tue, 27 Jul 2004 18:43:17 +0000 (GMT) (envelope-from time_to_hack@yahoo.com) Message-ID: <20040727184307.15471.qmail@web21525.mail.yahoo.com> Received: from [24.248.72.254] by web21525.mail.yahoo.com via HTTP; Tue, 27 Jul 2004 11:43:07 PDT Date: Tue, 27 Jul 2004 11:43:07 -0700 (PDT) From: bsd hack To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Kernel GENERIC config file X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 18:43:17 -0000 Hi, I need the kernel GENERIC config file for freebsd 4.7. I am able to find only the config file for freeBSD 5.2 online... can n'ybody either mail me the freeBSD 4.7 GENERIC file or gimme a link to it? Thank you. HKR --------------------------------- Do you Yahoo!? Y! Messenger - Communicate in real time. Download now. From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 19:06:06 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54D2016A4CE for ; Tue, 27 Jul 2004 19:06:06 +0000 (GMT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A48B43D4C for ; Tue, 27 Jul 2004 19:06:06 +0000 (GMT) (envelope-from dan@langille.org) Received: from xeon (xeon.unixathome.org [192.168.0.18]) by bast.unixathome.org (Postfix) with ESMTP id 4A52E3D34; Tue, 27 Jul 2004 15:06:05 -0400 (EDT) Date: Tue, 27 Jul 2004 15:06:05 -0400 (EDT) From: Dan Langille X-X-Sender: dan@xeon.unixathome.org To: bsd hack In-Reply-To: <20040727184307.15471.qmail@web21525.mail.yahoo.com> Message-ID: <20040727150522.K36300@xeon.unixathome.org> References: <20040727184307.15471.qmail@web21525.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: Kernel GENERIC config file X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 19:06:06 -0000 On Tue, 27 Jul 2004, bsd hack wrote: > I need the kernel GENERIC config file for freebsd 4.7. I am able to > find only the config file for freeBSD 5.2 online... can n'ybody either > mail me the freeBSD 4.7 GENERIC file or gimme a link to it? This doesn't belong on hackers. Get it yourself from CVS via the cvsweb interface: see http://www.freebsd.org/ -- Dan Langille - http://www.langille.org/ From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 19:06:36 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 935AE16A4CE for ; Tue, 27 Jul 2004 19:06:36 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E80043D48 for ; Tue, 27 Jul 2004 19:06:36 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 29756 invoked from network); 27 Jul 2004 19:06:35 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail3.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 27 Jul 2004 19:06:35 -0000 Received: from hydrogen.funkthat.com (kdapat@localhost.funkthat.com [127.0.0.1])i6RJ6YuU098000; Tue, 27 Jul 2004 12:06:35 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id i6RJ6YQF097999; Tue, 27 Jul 2004 12:06:34 -0700 (PDT) Date: Tue, 27 Jul 2004 12:06:34 -0700 From: John-Mark Gurney To: bsd hack Message-ID: <20040727190634.GQ991@funkthat.com> Mail-Followup-To: bsd hack , freebsd-hackers@freebsd.org References: <20040727184307.15471.qmail@web21525.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040727184307.15471.qmail@web21525.mail.yahoo.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: freebsd-hackers@freebsd.org Subject: Re: Kernel GENERIC config file X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 19:06:36 -0000 bsd hack wrote this message on Tue, Jul 27, 2004 at 11:43 -0700: > I need the kernel GENERIC config file for freebsd 4.7. I am able to find only the config file for freeBSD 5.2 online... can n'ybody either mail me the freeBSD 4.7 GENERIC file or gimme a link to it? http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/conf/GENERIC?f=u&only_with_tag=RELENG_4_7&logsort=date -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 27 22:45:51 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B2FB16A4D7 for ; Tue, 27 Jul 2004 22:45:51 +0000 (GMT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A05343D67 for ; Tue, 27 Jul 2004 22:45:51 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from pun.isi.edu (pun.isi.edu [128.9.160.150]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i6RMjDJ01100 for ; Tue, 27 Jul 2004 15:45:13 -0700 (PDT) Received: from pun.isi.edu (localhost [127.0.0.1]) by pun.isi.edu (8.12.11/8.12.11) with ESMTP id i6RMjDPB025007 for ; Tue, 27 Jul 2004 15:45:13 -0700 (PDT) (envelope-from faber@pun.isi.edu) Received: (from faber@localhost) by pun.isi.edu (8.12.11/8.12.11/Submit) id i6RMjDBE025006 for hackers@freebsd.org; Tue, 27 Jul 2004 15:45:13 -0700 (PDT) (envelope-from faber) Date: Tue, 27 Jul 2004 15:45:13 -0700 From: Ted Faber To: hackers@freebsd.org Message-ID: <20040727224513.GD21079@pun.isi.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DrWhICOqskFTAXiy" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-url: http://www.isi.edu/~faber X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: faber@isi.edu Subject: jdk13 native plugin stopped working on native mozilla on -CURRENT X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2004 22:45:51 -0000 --DrWhICOqskFTAXiy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I know this is off topic here, but I'm hoping that I can get a quick answer rather than tromping off to ports or java. I'm runiing a recent -CURRENT and ports cvsupped and compiled today and my native-mode jdk13 is no longer working as a plugin. I get an unresloved symbol at mozilla startup and no plugin. The relevant versions are: mozilla-1.7.1,2 The open source, standards compliant web browser jdk-1.3.1p9_4 Java Development Kit 1.3 and the errors from mozilla are: bug:~$ mozilla Error: No running window found. LoadPlugin: failed to initialize shared library /usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so [/usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so: Undefined symbol "_ZTV16nsQueryInterface"] LoadPlugin: failed to initialize shared library /usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so [/usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so: Undefined symbol "_ZTV16nsQueryInterface"] I also am running the linux shockwave plugin with no problem, if that's important. Any help would be great. Thanks. -- Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG --DrWhICOqskFTAXiy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBBtr5aUz3f+Zf+XsRAvkjAKDGBV9gF4pgvS+lSU1gq99XrRU3XgCglOWk 9GDMU5eCgLhvlQc2wru5c+0= =6Ymc -----END PGP SIGNATURE----- --DrWhICOqskFTAXiy-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 28 08:23:13 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1762C16A4E8 for ; Wed, 28 Jul 2004 08:23:13 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id A1EBD43D31 for ; Wed, 28 Jul 2004 08:23:09 +0000 (GMT) (envelope-from andreas.kohn@gmx.net) Received: (qmail 32155 invoked by uid 65534); 28 Jul 2004 08:23:08 -0000 Received: from unknown (EHLO [212.204.44.203]) (212.204.44.203) by mail.gmx.net (mp016) with SMTP; 28 Jul 2004 10:23:08 +0200 X-Authenticated: #2431876 From: Andreas Kohn To: Ted Faber In-Reply-To: <20040727224513.GD21079@pun.isi.edu> References: <20040727224513.GD21079@pun.isi.edu> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-YXDaMwjkXpsaxt1qG3Pu" Message-Id: <1091002987.871.4.camel@klamath.ankon.de.eu.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 28 Jul 2004 10:23:07 +0200 cc: hackers@freebsd.org Subject: Re: jdk13 native plugin stopped working on native mozilla on -CURRENT X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-java@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 08:23:13 -0000 --=-YXDaMwjkXpsaxt1qG3Pu Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-07-28 at 00:45, Ted Faber wrote: > I know this is off topic here, but I'm hoping that I can get a quick > answer rather than tromping off to ports or java.=20 Why don't you want to ask your question in a place where the chance for an answer is much higher? *puzzled* > I'm runiing a recent > -CURRENT and ports cvsupped and compiled today and my native-mode jdk13 > is no longer working as a plugin. I get an unresloved symbol at mozilla > startup and no plugin. =20 Did you recompile your jdk13 as well? HTH,=20 Andreas [Reply-To set to freebsd-java@freebsd.org] --=-YXDaMwjkXpsaxt1qG3Pu Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBB2JrYucd7Ow1ygwRArVgAJ4w8MLtuzXLMnFoJG0YIUYl0xFSWQCfcaaR c+PI/ITUiLRD1f192WfI9eM= =ecZZ -----END PGP SIGNATURE----- --=-YXDaMwjkXpsaxt1qG3Pu-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 28 09:36:06 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60C3F16A4CE for ; Wed, 28 Jul 2004 09:36:06 +0000 (GMT) Received: from cicero1.cybercity.dk (cicero1.cybercity.dk [212.242.40.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBE6043D41 for ; Wed, 28 Jul 2004 09:36:05 +0000 (GMT) (envelope-from db@traceroute.dk) Received: from user3.cybercity.dk (user3.cybercity.dk [212.242.41.36]) by cicero1.cybercity.dk (Postfix) with ESMTP id CD9E37E3719 for ; Wed, 28 Jul 2004 11:36:03 +0200 (CEST) Received: from main.trunet.dk (port132.ds1-arsy.adsl.cybercity.dk [212.242.239.73]) by user3.cybercity.dk (Postfix) with ESMTP id 8C27993D6A for ; Wed, 28 Jul 2004 11:36:03 +0200 (CEST) From: db To: hackers@freebsd.org Date: Wed, 28 Jul 2004 11:45:27 +0200 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200407281145.27824.db@traceroute.dk> Subject: Ready or not? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 09:36:06 -0000 Hi all Which of the following will be ready for production usage when 5.3 get's released? SMP (any i386 CPU recommendations?) PF with ALTQ GEOM Based Disk Encryption Oh and one last thing. If I want to backup everything on one computer to another, which program do you recommend for doing that? br db From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 28 13:04:49 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1760F16A4CE for ; Wed, 28 Jul 2004 13:04:49 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1862D43D54 for ; Wed, 28 Jul 2004 13:04:48 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.205] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1Bpo6x-0001lP-00; Wed, 28 Jul 2004 15:04:47 +0200 Received: from [217.83.14.28] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1Bpo6x-0001DC-00; Wed, 28 Jul 2004 15:04:47 +0200 From: Max Laier To: freebsd-hackers@freebsd.org Date: Wed, 28 Jul 2004 15:02:38 +0200 User-Agent: KMail/1.6.2 References: <200407281145.27824.db@traceroute.dk> In-Reply-To: <200407281145.27824.db@traceroute.dk> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_2P6BBhTzZm5NLwB"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407281502.46395.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 Subject: Re: Ready or not? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 13:04:49 -0000 --Boundary-02=_2P6BBhTzZm5NLwB Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 28 July 2004 11:45, db wrote: > Hi all > > Which of the following will be ready for production usage when 5.3 get's > released? > > SMP (any i386 CPU recommendations?) > PF with ALTQ I know many people who already use a (well chosen) 5-CURRENT snapshot to se= rve=20 as PF+ALTQ gateway in production environment. For ALTQ there is the problem= =20 of "will your driver be supported?". The only way to get this fixed is to=20 help me with the testing *now*, see: http://people.freebsd.org/~mlaier/ALTQ_driver/ for details. If your favorite driver is untested, test it. If it is not the= re=20 at all, send me a ping and I'll provide a testable patch. > GEOM Based Disk Encryption > > Oh and one last thing. If I want to backup everything on one computer to > another, which program do you recommend for doing that? =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --Boundary-02=_2P6BBhTzZm5NLwB Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBB6P2XyyEoT62BG0RAkWkAJ0TVRah8XkRnW6dc2xXIcqH5P3MPgCfT5cl ulecOG2Le8sIjzYXTVWFScs= =JaOK -----END PGP SIGNATURE----- --Boundary-02=_2P6BBhTzZm5NLwB-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 28 13:15:11 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CB7B16A4CF for ; Wed, 28 Jul 2004 13:15:11 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFF8643D66 for ; Wed, 28 Jul 2004 13:15:09 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received-SPF: pass (eva.fit.vutbr.cz: domain of xdivac02@eva.fit.vutbr.cz designates 127.0.0.1 as permitted sender) receiver=eva.fit.vutbr.cz; client_ip=127.0.0.1; envelope-from=xdivac02@eva.fit.vutbr.cz; Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.12.11/8.12.11) with ESMTP id i6SDEv1x048208 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 28 Jul 2004 15:14:57 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.12.11/8.12.5/Submit) id i6SDEvdp048207; Wed, 28 Jul 2004 15:14:57 +0200 (CEST) Date: Wed, 28 Jul 2004 15:14:57 +0200 From: Divacky Roman To: Julian Elischer Message-ID: <20040728131457.GA47773@stud.fit.vutbr.cz> References: <20040727160206.GA1784@stud.fit.vutbr.cz> <20040727.100848.15611424.imp@bsdimp.com> <4106911D.6090201@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4106911D.6090201@elischer.org> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: hackers@freebsd.org Subject: Re: new files in kernel build X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 13:15:11 -0000 On Tue, Jul 27, 2004 at 10:30:05AM -0700, Julian Elischer wrote: > > > M. Warner Losh wrote: > > >In message: <20040727160206.GA1784@stud.fit.vutbr.cz> > > Divacky Roman writes: > >: Hi, > >: > >: If I want to add some files into kernel sources, what am I supposed to > >do to > >: them compile? I added some into sys/net80211/ but they dont compile... > >: > >: I tried sys/conf/files but it does help, just prints a message about > >having it > >: defined before... > > > >Exact error messages would be helpful. > > > >Generally, you put them in sys/conf/files, re-run config and life is > >good. > > > > if you want to add these files without editing /sys/conf/files you can > add them to /sys/conf//files.{YOURCONFIG} > e.g. we backported the firewire to an older kernel and have a > proprietary driver as well.. > > our files.VICOR looks like: > > %cat files.VICOR > xdcpdrvr.o optional xdcp \ > dependency "$S/dev/xdcp/xdcpdrvr.o.uu" \ > compile-with "uudecode < $S/dev/xdcp/xdcpdrvr.o.uu" \ > no-implicit-rule > dev/firewire/firewire.c optional firewire > dev/firewire/fwcrom.c optional firewire > dev/firewire/fwdev.c optional firewire > dev/firewire/fwmem.c optional firewire > dev/firewire/fwohci.c optional firewire > dev/firewire/fwohci_pci.c optional firewire pci > dev/firewire/if_fwe.c optional fwe > dev/firewire/sbp.c optional sbp > > without looking at the source to config, it seems to use teh entry on > the 'ident' line to > look for these files.. I created this which could solve problem of wifi driver not being able to switch among speeds. I added two files into sys/net80211/ and change sys/conf/files to net80211/ieee80211_proto.c optional wlan + net80211/ieee80211_rssadapt.h optional wlan + net80211/ieee80211_rssadapt.c optional wlan netatalk/aarp.c optional netatalk (semi-diff, ie. I added that two files) and it gives me this message: "Makefile", line 3104: warning: duplicate script for target "ieee80211_rssadapt. ln" ignored "Makefile", line 3107: warning: duplicate script for target "ieee80211_rssadapt. o" ignored (but it proceeds further) and finally it fails with: link_elf: symbol ieee80211_rssadapt_raise_rate undefined simply said - the ieee80211_rssadapt.c didnt get compiled at all (so linker cannot find the symbol) By applying the patch and defining wi device you can get the same behaviour thnx for help roman From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 28 13:30:48 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0B3B16A4CE for ; Wed, 28 Jul 2004 13:30:48 +0000 (GMT) Received: from britannica.bec.de (wlan032106.uni-rostock.de [139.30.32.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id E660143D64 for ; Wed, 28 Jul 2004 13:30:46 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (localhost [127.0.0.1]) by britannica.bec.de (8.12.10/8.12.10) with ESMTP id i6SDU7et060973 for ; Wed, 28 Jul 2004 15:30:08 +0200 (CEST) (envelope-from joerg@britannica.bec.de) Received: (from joerg@localhost) by britannica.bec.de (8.12.10/8.12.10/Submit) id i6SDTuf5060773 for hackers@freebsd.org; Wed, 28 Jul 2004 15:29:56 +0200 (CEST) Date: Wed, 28 Jul 2004 15:29:55 +0200 From: Joerg Sonnenberger To: hackers@freebsd.org Message-ID: <20040728132955.GA57871@britannica.bec.de> Mail-Followup-To: hackers@freebsd.org References: <20040727160206.GA1784@stud.fit.vutbr.cz> <20040727.100848.15611424.imp@bsdimp.com> <4106911D.6090201@elischer.org> <20040728131457.GA47773@stud.fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040728131457.GA47773@stud.fit.vutbr.cz> User-Agent: Mutt/1.4.1i Subject: Re: new files in kernel build X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 13:30:49 -0000 On Wed, Jul 28, 2004 at 03:14:57PM +0200, Divacky Roman wrote: > and change sys/conf/files to > net80211/ieee80211_proto.c optional wlan > + net80211/ieee80211_rssadapt.h optional wlan remove this line. You only specify sources for object files in conf/files. Joerg > + net80211/ieee80211_rssadapt.c optional wlan > netatalk/aarp.c optional netatalk From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 28 15:17:47 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B2E716A4CE for ; Wed, 28 Jul 2004 15:17:47 +0000 (GMT) Received: from mps7.plala.or.jp (c150240.vh.plala.or.jp [210.150.150.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDB2543D46 for ; Wed, 28 Jul 2004 15:17:45 +0000 (GMT) (envelope-from e-kamo@trio.plala.or.jp) Received: from msvc1.plala.or.jp ([172.23.8.209]) by mps7.plala.or.jp with SMTP id <20040728151744.RLJL14861.mps7.plala.or.jp@msvc1.plala.or.jp> for ; Thu, 29 Jul 2004 00:17:44 +0900 Received: ( 15979 invoked from network); 29 Jul 2004 00:17:44 +0900 X-SVCK: Received: from unknown (HELO mpb1.plala.or.jp) (172.23.8.16) by msvc1 with SMTP; 29 Jul 2004 00:17:43 +0900 Received: from trio.plala.or.jp ([219.25.148.52]) by mpb1.plala.or.jp with ESMTP id <20040728151743.SGZO19716.mpb1.plala.or.jp@trio.plala.or.jp> for ; Thu, 29 Jul 2004 00:17:43 +0900 Message-ID: <4107C54E.1050504@trio.plala.or.jp> Date: Thu, 29 Jul 2004 00:25:02 +0900 From: Eitarou Kamo User-Agent: Mozilla/5.0 (Windows; U; Win98; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: ja MIME-Version: 1.0 To: hackers@freebsd.org X-Enigmail-Version: 0.76.8.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Subject: freebsd-gnats-submit@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 15:17:47 -0000 Hi guys, I have a problem with my mail env. My problem is that suddenly some mails for "freebsd-gnats-submit@FreeBSD.org" came to my mail client. What happened? I don't subscribe such a list. Eitarou -- *********************** Eitarou Kamo Tel. +81 75 7035997 Fax +81 75 7035997 VoIP 050 10585997(domestic only) e$B!>(Bmail e-kamo@trio.plala.or.jp For business: Feel free to mail me(above), please. Donation http://www.PayPal.Com GPG FingerPrint: 032D FDF9 D27B 23F7 9A81 BF4C 626C FBAA BC3A 9895 ************************************************************************ From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 28 15:26:35 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FDA216A4CE for ; Wed, 28 Jul 2004 15:26:35 +0000 (GMT) Received: from gandalf.online.bg (gandalf.online.bg [217.75.128.9]) by mx1.FreeBSD.org (Postfix) with SMTP id CD91943D64 for ; Wed, 28 Jul 2004 15:26:30 +0000 (GMT) (envelope-from roam@ringlet.net) Received: (qmail 14694 invoked from network); 28 Jul 2004 15:21:09 -0000 Received: from unknown (HELO straylight.m.ringlet.net) (217.75.134.254) by gandalf.online.bg with SMTP; 28 Jul 2004 15:21:09 -0000 Received: (qmail 44322 invoked by uid 1000); 28 Jul 2004 15:26:23 -0000 Date: Wed, 28 Jul 2004 18:26:23 +0300 From: Peter Pentchev To: Eitarou Kamo Message-ID: <20040728152623.GB1390@straylight.m.ringlet.net> Mail-Followup-To: Eitarou Kamo , hackers@freebsd.org References: <4107C54E.1050504@trio.plala.or.jp> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cmJC7u66zC7hs+87" Content-Disposition: inline In-Reply-To: <4107C54E.1050504@trio.plala.or.jp> User-Agent: Mutt/1.5.6i cc: hackers@freebsd.org Subject: Re: freebsd-gnats-submit@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 15:26:35 -0000 --cmJC7u66zC7hs+87 Content-Type: text/plain; charset=windows-1251 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 29, 2004 at 12:25:02AM +0900, Eitarou Kamo wrote: > Hi guys, >=20 > I have a problem with my mail env. >=20 > My problem is that suddenly some mails for > "freebsd-gnats-submit@FreeBSD.org" > came to my mail client. What happened? I don't subscribe such a list. GNATS is FreeBSD's problem report (PR) system. freebsd-gnats-submit is the address that PR's and followups to PR's should be sent to. Either you have filed a PR, or somebody has sent a follow-up message to one of your PR's. Alternatively, it could just be some spammer forging e-mail addresses and choosing them at random. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@cnsys.bg roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This sentence would be seven words long if it were six words shorter. --cmJC7u66zC7hs+87 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBB8Wf7Ri2jRYZRVMRAui4AKCHxPasmZZkC6Hb9XPO3rJWpxwa2ACeMYvN Pvj2oWhccHUvDsFtFC0M76M= =Crny -----END PGP SIGNATURE----- --cmJC7u66zC7hs+87-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 28 15:48:14 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F33D16A4CE for ; Wed, 28 Jul 2004 15:48:14 +0000 (GMT) Received: from mps10.plala.or.jp (c153126.vh.plala.or.jp [210.150.153.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7671F43D60 for ; Wed, 28 Jul 2004 15:48:13 +0000 (GMT) (envelope-from e-kamo@trio.plala.or.jp) Received: from msvc1.plala.or.jp ([172.23.8.209]) by mps10.plala.or.jp with SMTP id <20040728154812.WIEI7110.mps10.plala.or.jp@msvc1.plala.or.jp> for ; Thu, 29 Jul 2004 00:48:12 +0900 Received: ( 25021 invoked from network); 29 Jul 2004 00:48:12 +0900 X-SVCK: Received: from unknown (HELO mpb1.plala.or.jp) (172.23.8.16) by msvc1 with SMTP; 29 Jul 2004 00:48:11 +0900 Received: from trio.plala.or.jp ([219.25.148.52]) by mpb1.plala.or.jp with ESMTP id <20040728154810.SHNP19716.mpb1.plala.or.jp@trio.plala.or.jp>; Thu, 29 Jul 2004 00:48:10 +0900 Message-ID: <4107CC71.3040903@trio.plala.or.jp> Date: Thu, 29 Jul 2004 00:55:29 +0900 From: Eitarou Kamo User-Agent: Mozilla/5.0 (Windows; U; Win98; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: ja MIME-Version: 1.0 To: Peter Pentchev , hackers@freebsd.org References: <4107C54E.1050504@trio.plala.or.jp> <20040728152623.GB1390@straylight.m.ringlet.net> In-Reply-To: <20040728152623.GB1390@straylight.m.ringlet.net> X-Enigmail-Version: 0.76.8.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Subject: Re: freebsd-gnats-submit@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 15:48:14 -0000 Peter Pentchev wrote: > >GNATS is FreeBSD's problem report (PR) system. freebsd-gnats-submit is >the address that PR's and followups to PR's should be sent to. Either >you have filed a PR, or somebody has sent a follow-up message to one of >your PR's. Alternatively, it could just be some spammer forging e-mail >addresses and choosing them at random. > >G'luck, >Peter > > > It's the work of spamer , I guess. Eitarou -- From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 28 16:23:12 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AE3316A4CF for ; Wed, 28 Jul 2004 16:23:12 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9077243D45 for ; Wed, 28 Jul 2004 16:23:11 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6SGM96m026952; Wed, 28 Jul 2004 10:22:09 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 28 Jul 2004 10:22:30 -0600 (MDT) Message-Id: <20040728.102230.13026377.imp@bsdimp.com> To: xdivac02@stud.fit.vutbr.cz From: "M. Warner Losh" In-Reply-To: <20040728131457.GA47773@stud.fit.vutbr.cz> References: <20040727.100848.15611424.imp@bsdimp.com> <4106911D.6090201@elischer.org> <20040728131457.GA47773@stud.fit.vutbr.cz> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: julian@elischer.org Subject: Re: new files in kernel build X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 16:23:12 -0000 In message: <20040728131457.GA47773@stud.fit.vutbr.cz> Divacky Roman writes: : + net80211/ieee80211_rssadapt.h optional wlan No need for the .h files. That's likely what is confusing things. Warner From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 28 17:17:54 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5354216A4CE for ; Wed, 28 Jul 2004 17:17:54 +0000 (GMT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3219343D41 for ; Wed, 28 Jul 2004 17:17:54 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from pun.isi.edu (pun.isi.edu [128.9.160.150]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i6SHHfJ09782 for ; Wed, 28 Jul 2004 10:17:41 -0700 (PDT) Received: from pun.isi.edu (localhost [127.0.0.1]) by pun.isi.edu (8.12.11/8.12.11) with ESMTP id i6SHHfFG030606 for ; Wed, 28 Jul 2004 10:17:41 -0700 (PDT) (envelope-from faber@pun.isi.edu) Received: (from faber@localhost) by pun.isi.edu (8.12.11/8.12.11/Submit) id i6SHHflq030605 for hackers@freebsd.org; Wed, 28 Jul 2004 10:17:41 -0700 (PDT) (envelope-from faber) Date: Wed, 28 Jul 2004 10:17:41 -0700 From: Ted Faber To: hackers@freebsd.org Message-ID: <20040728171741.GE29578@pun.isi.edu> References: <20040727224513.GD21079@pun.isi.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8vCeF2GUdMpe9ZbK" Content-Disposition: inline In-Reply-To: <20040727224513.GD21079@pun.isi.edu> User-Agent: Mutt/1.4.2.1i X-url: http://www.isi.edu/~faber X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: faber@isi.edu Subject: Re: jdk13 native plugin stopped working on native mozilla on -CURRENT X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 17:17:54 -0000 --8vCeF2GUdMpe9ZbK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jul 27, 2004 at 03:45:13PM -0700, Ted Faber wrote: > I know this is off topic here, but I'm hoping that I can get a quick > answer rather than tromping off to ports or java. I'm runiing a recent > -CURRENT and ports cvsupped and compiled today and my native-mode jdk13 > is no longer working as a plugin. I get an unresloved symbol at mozilla > startup and no plugin. As someone helpfully pointed out off-list, mozilla 1.7 needs jdk1.4 . It wouldn't suck to have this in ports/UPDATING. -- Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG --8vCeF2GUdMpe9ZbK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBB9+1aUz3f+Zf+XsRAtuRAKCmbOh2UNDc64razdDh0/0SQpuFFgCeJpAl Svz0x5O1ftkeSUcakD1BndU= =8nHY -----END PGP SIGNATURE----- --8vCeF2GUdMpe9ZbK-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 28 18:15:03 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2F7016A4CE for ; Wed, 28 Jul 2004 18:15:03 +0000 (GMT) Received: from web21528.mail.yahoo.com (web21528.mail.yahoo.com [66.163.170.147]) by mx1.FreeBSD.org (Postfix) with SMTP id C445C43D4C for ; Wed, 28 Jul 2004 18:15:03 +0000 (GMT) (envelope-from time_to_hack@yahoo.com) Message-ID: <20040728181459.24126.qmail@web21528.mail.yahoo.com> Received: from [24.248.72.254] by web21528.mail.yahoo.com via HTTP; Wed, 28 Jul 2004 11:14:59 PDT Date: Wed, 28 Jul 2004 11:14:59 -0700 (PDT) From: bsd hack To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Kernel options X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 18:15:04 -0000 Hi, I am working with the Kernel config file to optimize it and also to improve the overall security of the system! I have the following quetions: (1) There are a few options that are not available in the default kernel... like the IPFIREWALL options(and the like)... I basically need to know all possible options I can add to the kernel config file! (2) I guess these options can be used to set the kernel variables accessible through the sysctl command. So can I create my own options so that I can set a few kernel variables as and when I build the custom kernel? (3) and also my aim includes optimizing the kernel... so by enabling only the options I need to I should get a get optimization... is there anything else that can be done? (4) My aim is to improve local and network security. I guess enabling IPFIREWALL helps with the network security part.... are there any special options for local security? Thank you. HKR --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 28 21:10:39 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD12116A4CE for ; Wed, 28 Jul 2004 21:10:39 +0000 (GMT) Received: from sp5.cs.ucdavis.edu (sp5.cs.ucdavis.edu [169.237.5.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6D0643D5C for ; Wed, 28 Jul 2004 21:10:39 +0000 (GMT) (envelope-from abkonstantinov@earthlink.net) Received: from sp5.cs.ucdavis.edu (localhost.localdomain [127.0.0.1]) by sp5.cs.ucdavis.edu (8.12.8/8.12.8) with ESMTP id i6SLAd5u004481 for ; Wed, 28 Jul 2004 14:10:39 -0700 Received: (from konstant@localhost) by sp5.cs.ucdavis.edu (8.12.8/8.12.8/Submit) id i6SLAdaL004479 for hackers@freebsd.org; Wed, 28 Jul 2004 14:10:39 -0700 X-Authentication-Warning: sp5.cs.ucdavis.edu: konstant set sender to abkonstantinov@earthlink.net using -f From: Andrew Konstantinov To: hackers@freebsd.org In-Reply-To: <20040728181459.24126.qmail@web21528.mail.yahoo.com> References: <20040728181459.24126.qmail@web21528.mail.yahoo.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1091049038.4409.25.camel@sp5.cs.ucdavis.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 28 Jul 2004 14:10:39 -0700 Subject: Re: Kernel options X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 21:10:39 -0000 On Wed, 2004-07-28 at 11:14, bsd hack wrote: > Hi, > I am working with the Kernel config file to optimize it and also to improve the overall security of the system! > > I have the following quetions: > (1) There are a few options that are not available in the default kernel... like the IPFIREWALL options(and the like)... I basically need to know all possible options I can add to the kernel config file! I think this is related to the thread about "next generation" kernel config stuff, but for starters you might want to take a look at the NOTES file. > (2) I guess these options can be used to set the kernel variables accessible through the sysctl command. So can I create my own options so that I can set a few kernel variables as and when I build the custom kernel? Perhaps what you are looking for is the tuning manual page? > (3) and also my aim includes optimizing the kernel... so by enabling only the options I need to I should get a get optimization... is there anything else that can be done? By excluding all the unnecessary code from the kernel you are performing kernel minimization. What you are really looking for is the run time system optimizaion (configuration process) for a particular task that it is going to perform. > (4) My aim is to improve local and network security. I guess enabling IPFIREWALL helps with the network security part.... are there any special options for local security? Enabling IPFIREWALL option won't help your security, but configuring your firewall properly will. Also, there is some useful theoretical information in the security manual page. Andrew From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 29 10:28:14 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22D5716A4CE for ; Thu, 29 Jul 2004 10:28:14 +0000 (GMT) Received: from britannica.bec.de (port-212-202-135-63.static.qsc.de [212.202.135.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6705543D62 for ; Thu, 29 Jul 2004 10:28:13 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (localhost [127.0.0.1]) by britannica.bec.de (8.12.10/8.12.10) with ESMTP id i6TAQfdb000970 for ; Thu, 29 Jul 2004 12:26:42 +0200 (CEST) (envelope-from joerg@britannica.bec.de) Received: (from joerg@localhost) by britannica.bec.de (8.12.10/8.12.10/Submit) id i6TAQQs4000969 for hackers@freebsd.org; Thu, 29 Jul 2004 12:26:26 +0200 (CEST) Date: Thu, 29 Jul 2004 12:26:25 +0200 From: Joerg Sonnenberger To: hackers@freebsd.org Message-ID: <20040729102625.GB849@britannica.bec.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: License of dev/arl X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 10:28:14 -0000 Hi all, what's the license under which arl(4) is distributed? The source doesn't contain any copyright or license header. I would appreciate it, if someone could fix that. Joerg From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 29 15:25:59 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4067616A4D0 for ; Thu, 29 Jul 2004 15:25:59 +0000 (GMT) Received: from wek4.com (c-24-16-241-139.client.comcast.net [24.16.241.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1213C43D62 for ; Thu, 29 Jul 2004 15:25:59 +0000 (GMT) (envelope-from bill@wek4.com) Received: from wek4.com (localhost.wek [127.0.0.1]) by wek4.com (8.12.10/8.12.10) with ESMTP id i6TFPrQ6016186; Thu, 29 Jul 2004 08:25:53 -0700 (PDT) (envelope-from bill@wek4.com) Received: (from bill@localhost) by wek4.com (8.12.10/8.12.10/Submit) id i6TFPr0n016185; Thu, 29 Jul 2004 08:25:53 -0700 (PDT) (envelope-from bill) From: William Kirkland Message-Id: <200407291525.i6TFPr0n016185@wek4.com> To: "Generationkernelconfiguration?]"@wek4.com, freebsd-hackers@freebsd.org Date: Thu, 29 Jul 2004 08:25:53 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Subject: Kernel Configuration script [was Re: Next X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 15:25:59 -0000 On Tue, Jul 20, 2004 at 07:39:31PM -0500, Conrad J. Sabatier wrote: > Just musing on an idea here: > > I've been thinking for a while now about trying to write a tool to make > kernel configuration easier, sort of a "make config" (as in ports) for > the kernel, similar to what's available on some of the Linux distros. Ok, I have attached some scripts I wrote, to make my life simpler. Though I do have some concerns that one should write their own, or use the existing structure and tools. I am willing to show what I use and share ideas. If you choose to use this, please give credit where it is due. As I have never previously published this, nor anything else. I find the GNU GPL (http://www.gnu.org/copyleft/gpl.html) acceptable. Use at your own risk. My scripts parces the boot information from /var/log/messages, then builds a kernel configuration file from that and a configuration file. I have, just now, written a brief overview of what is done and am willing to provide more information if you ask. I suppose I could even clean it up a bit and write proper documentation. The profile is a bit overly complex, though I use it for a number of other scripts as well. Sufice it to say, it searches (based upon the PATH environmental variable, replacing "/bin:" and "/sbin:" with "/etc:" for an appropriate configuration file (one that has the script name, minus an optional .sh and appending a .cfg, as a sufix). Once the file is found, appropriate variables are set. The performance can be enhanced by setting the "grep" variable, so that only the relevent boot entries are parced, or copying the message file somewhere else, then setting the "boot" variable to point to that file. Options and and device entries are included if a reference is found for them in the /var/log/messages file. The exclude and include configuration variables, modify this behavior, in that the script does not find references for everything in the boot record, and also finds references to things I do not use. You should probably uncomment line 34, and verify the results, prior to using. For that matter, there are a number of other things you should understand prior to use (review it before you use it!). #! /bin/sh #- -r-xr-xr-x 1 root wheel 1285 May 9 20:20 /wek/bin/kernel.sh . /wek/bin/_profile if [ ! -f "${_kernel_dst}" ]; then grep -E "${_kernel_grep:-.*}" ${_kernel_boot:-/var/log/messages} >${tmp} awk -v K=${_kernel} -v B=${tmp} -v P=${_kernel_prefix} \ -v I="${_kernel_include}" -v X="${_kernel_exclude}" ' BEGIN { while( getline ${_kernel_dst} if [ -f "${_kernel_add}" ]; then cat ${_kernel_add} >>${_kernel_dst} fi rm -f ${tmp} 2>/dev/null #- exit fi ( uname -a; date; set -o xtrace printenv | grep "^_${P}" | sort cd /usr/src && make -i depend \ && make buildkernel KERNCONF=${_kernel} \ && make installkernel KERNCONF=${_kernel} ) 2>&1 | tee ${_kernel_log} #- -r--r--r-- 1 operator wheel 126 Apr 23 15:50 /wek/etc/kernel.add #- options FAST_IPSEC # new IPsec options IPSEC options IPSEC_ESP options IPFIREWALL options IPDIVERT options DUMMYNET #- -r--r--r-- 1 operator wheel 372 May 9 13:59 /wek/etc/kernel.cfg wek-* boot=/tmp/boot boot=/var/log/messages src=/usr/src/sys/$( uname -m )/conf/GENERIC dst=/usr/src/sys/$( uname -m )/conf/${_kernel} include="atadisk atapicd atapifd atapist random loop ether pty md bpf miibus gif sis" exclude="INET6 MD_ROOT NFS_ROOT I486_CPU I586_CPU SMP plip" add=${home}/etc/${P}.add log=${home}/log/${_kernel} #! /bin/sh #- -rw-r--r-- 1 root wheel 742 May 11 14:39 /wek/bin/_profile P=$( basename ${0%.*} ) export home=/wek export tmp=/tmp/$$ export log=/tmp/${P}-$( date "+%y%m%d" ) for T in $( echo ${PATH}:${home}/etc \ | sed 's|/[s]*bin:|/etc |g' | tr ":" " " ); do if [ -z "${cfg}" -a -r ${T}/${P}.cfg ]; then cfg=${T}/${P}.cfg fi done awk -F = -v P=${P} -v M="${1:-$( date '+wek-%y%m%d' )}" ' /^[^ ]/ { ok=0; if ( M ~ $1 ) { print "export _" P "=" M; ok=1; next } } /^[ ]+[A-Z0-9a-z_]*[ ]*=/ { if ( ok ) { gsub( "^[ ]*", "export _" P "_" ); print } }' ${cfg:-/dev/null} >${tmp} . ${tmp} && rm ${tmp} export PATH=${home}/bin:${PATH} From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 29 15:28:09 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DD7416A4CE for ; Thu, 29 Jul 2004 15:28:09 +0000 (GMT) Received: from wek4.com (c-24-16-241-139.client.comcast.net [24.16.241.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3212E43D41 for ; Thu, 29 Jul 2004 15:28:09 +0000 (GMT) (envelope-from bill@wek4.com) Received: from wek4.com (localhost.wek [127.0.0.1]) by wek4.com (8.12.10/8.12.10) with ESMTP id i6TFS5Q6016222 for ; Thu, 29 Jul 2004 08:28:05 -0700 (PDT) (envelope-from bill@wek4.com) Received: (from bill@localhost) by wek4.com (8.12.10/8.12.10/Submit) id i6TFS59t016221 for freebsd-hackers@freebsd.org; Thu, 29 Jul 2004 08:28:05 -0700 (PDT) (envelope-from bill) From: William Kirkland Message-Id: <200407291528.i6TFS59t016221@wek4.com> To: freebsd-hackers@freebsd.org Date: Thu, 29 Jul 2004 08:28:05 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Subject: Kernel Configuration script [was Re: "Next Generation" kernel configuration?] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 15:28:09 -0000 On Tue, Jul 20, 2004 at 07:39:31PM -0500, Conrad J. Sabatier wrote: > Just musing on an idea here: > > I've been thinking for a while now about trying to write a tool to make > kernel configuration easier, sort of a "make config" (as in ports) for > the kernel, similar to what's available on some of the Linux distros. Ok, I have attached some scripts I wrote, to make my life simpler. Though I do have some concerns that one should write their own, or use the existing structure and tools. I am willing to show what I use and share ideas. If you choose to use this, please give credit where it is due. As I have never previously published this, nor anything else. I find the GNU GPL (http://www.gnu.org/copyleft/gpl.html) acceptable. Use at your own risk. My scripts parces the boot information from /var/log/messages, then builds a kernel configuration file from that and a configuration file. I have, just now, written a brief overview of what is done and am willing to provide more information if you ask. I suppose I could even clean it up a bit and write proper documentation. The profile is a bit overly complex, though I use it for a number of other scripts as well. Sufice it to say, it searches (based upon the PATH environmental variable, replacing "/bin:" and "/sbin:" with "/etc:" for an appropriate configuration file (one that has the script name, minus an optional .sh and appending a .cfg, as a sufix). Once the file is found, appropriate variables are set. The performance can be enhanced by setting the "grep" variable, so that only the relevent boot entries are parced, or copying the message file somewhere else, then setting the "boot" variable to point to that file. Options and and device entries are included if a reference is found for them in the /var/log/messages file. The exclude and include configuration variables, modify this behavior, in that the script does not find references for everything in the boot record, and also finds references to things I do not use. You should probably uncomment line 34, and verify the results, prior to using. For that matter, there are a number of other things you should understand prior to use (review it before you use it!). #! /bin/sh #- -r-xr-xr-x 1 root wheel 1285 May 9 20:20 /wek/bin/kernel.sh . /wek/bin/_profile if [ ! -f "${_kernel_dst}" ]; then grep -E "${_kernel_grep:-.*}" ${_kernel_boot:-/var/log/messages} >${tmp} awk -v K=${_kernel} -v B=${tmp} -v P=${_kernel_prefix} \ -v I="${_kernel_include}" -v X="${_kernel_exclude}" ' BEGIN { while( getline ${_kernel_dst} if [ -f "${_kernel_add}" ]; then cat ${_kernel_add} >>${_kernel_dst} fi rm -f ${tmp} 2>/dev/null #- exit fi ( uname -a; date; set -o xtrace printenv | grep "^_${P}" | sort cd /usr/src && make -i depend \ && make buildkernel KERNCONF=${_kernel} \ && make installkernel KERNCONF=${_kernel} ) 2>&1 | tee ${_kernel_log} #- -r--r--r-- 1 operator wheel 126 Apr 23 15:50 /wek/etc/kernel.add #- options FAST_IPSEC # new IPsec options IPSEC options IPSEC_ESP options IPFIREWALL options IPDIVERT options DUMMYNET #- -r--r--r-- 1 operator wheel 372 May 9 13:59 /wek/etc/kernel.cfg wek-* boot=/tmp/boot boot=/var/log/messages src=/usr/src/sys/$( uname -m )/conf/GENERIC dst=/usr/src/sys/$( uname -m )/conf/${_kernel} include="atadisk atapicd atapifd atapist random loop ether pty md bpf miibus gif sis" exclude="INET6 MD_ROOT NFS_ROOT I486_CPU I586_CPU SMP plip" add=${home}/etc/${P}.add log=${home}/log/${_kernel} #! /bin/sh #- -rw-r--r-- 1 root wheel 742 May 11 14:39 /wek/bin/_profile P=$( basename ${0%.*} ) export home=/wek export tmp=/tmp/$$ export log=/tmp/${P}-$( date "+%y%m%d" ) for T in $( echo ${PATH}:${home}/etc \ | sed 's|/[s]*bin:|/etc |g' | tr ":" " " ); do if [ -z "${cfg}" -a -r ${T}/${P}.cfg ]; then cfg=${T}/${P}.cfg fi done awk -F = -v P=${P} -v M="${1:-$( date '+wek-%y%m%d' )}" ' /^[^ ]/ { ok=0; if ( M ~ $1 ) { print "export _" P "=" M; ok=1; next } } /^[ ]+[A-Z0-9a-z_]*[ ]*=/ { if ( ok ) { gsub( "^[ ]*", "export _" P "_" ); print } }' ${cfg:-/dev/null} >${tmp} . ${tmp} && rm ${tmp} export PATH=${home}/bin:${PATH} From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 29 15:58:28 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFDE016A4CE for ; Thu, 29 Jul 2004 15:58:28 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id C304A43D2D for ; Thu, 29 Jul 2004 15:58:28 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.10) with ESMTP id i6TFwCOF010060; Thu, 29 Jul 2004 08:58:12 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i6TFwBtY010059; Thu, 29 Jul 2004 08:58:11 -0700 Date: Thu, 29 Jul 2004 08:58:11 -0700 From: Brooks Davis To: William Kirkland Message-ID: <20040729155811.GA5853@Odin.AC.HMC.Edu> References: <200407291525.i6TFPr0n016185@wek4.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline In-Reply-To: <200407291525.i6TFPr0n016185@wek4.com> User-Agent: Mutt/1.5.4i cc: freebsd-hackers@freebsd.org cc: "Generationkernelconfiguration?]"@wek4.com Subject: Re: Kernel Configuration script [was Re: Next X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 15:58:29 -0000 --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 29, 2004 at 08:25:53AM -0700, William Kirkland wrote: > On Tue, Jul 20, 2004 at 07:39:31PM -0500, Conrad J. Sabatier wrote: > > Just musing on an idea here: > >=20 > > I've been thinking for a while now about trying to write a tool to make > > kernel configuration easier, sort of a "make config" (as in ports) for > > the kernel, similar to what's available on some of the Linux distros. >=20 > Ok, I have attached some scripts I wrote, to make my life simpler. > Though I do have some concerns that one should write their own, or use > the existing structure and tools. I am willing to show what I use and > share ideas.=20 >=20 > If you choose to use this, please give credit where it is due. As I > have never previously published this, nor anything else. I find the GNU > GPL (http://www.gnu.org/copyleft/gpl.html) acceptable. Use at your own > risk. Anyone wishing to produce something to be included in the project, should STOP READING HERE to avoid GPL comtamination. -- 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 --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBCR6TXY6L6fI4GtQRAsXdAKDP1Kkk9ilSNS8/JBwlTDv5DM42MgCgqdZO 8X8AeW3zxKr8UaOx0XPWCI0= =0ATh -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 29 16:02:52 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0755B16A4CE for ; Thu, 29 Jul 2004 16:02:52 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91A7B43D53 for ; Thu, 29 Jul 2004 16:02:51 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6TG2BZg040977; Thu, 29 Jul 2004 10:02:11 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 29 Jul 2004 10:02:34 -0600 (MDT) Message-Id: <20040729.100234.29651746.imp@bsdimp.com> To: joerg@britannica.bec.de From: "M. Warner Losh" In-Reply-To: <20040729102625.GB849@britannica.bec.de> References: <20040729102625.GB849@britannica.bec.de> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org Subject: Re: License of dev/arl X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 16:02:52 -0000 In message: <20040729102625.GB849@britannica.bec.de> Joerg Sonnenberger writes: : what's the license under which arl(4) is distributed? The source doesn't : contain any copyright or license header. I would appreciate it, if someone : could fix that. I'll make sure that one gets affixed. Warner From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 29 20:21:43 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB37E16A4CE for ; Thu, 29 Jul 2004 20:21:43 +0000 (GMT) Received: from shellma.zin.lublin.pl (shellma.zin.lublin.pl [212.182.126.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2ACDC43D1D for ; Thu, 29 Jul 2004 20:21:38 +0000 (GMT) (envelope-from pawmal-posting@freebsd.lublin.pl) Received: by shellma.zin.lublin.pl (Postfix, from userid 1018) id 71B283474C2; Thu, 29 Jul 2004 22:19:09 +0200 (CEST) Date: Thu, 29 Jul 2004 22:19:09 +0200 From: Pawel Malachowski To: Max Laier Message-ID: <20040729201909.GA12370@shellma.zin.lublin.pl> References: <200407281145.27824.db@traceroute.dk> <200407281502.46395.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200407281502.46395.max@love2party.net> User-Agent: Mutt/1.4.2i cc: freebsd-hackers@freebsd.org Subject: Re: Ready or not? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-hackers@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 20:21:43 -0000 On Wed, Jul 28, 2004 at 03:02:38PM +0200, Max Laier wrote: Hello, > as PF+ALTQ gateway in production environment. For ALTQ there is the problem > of "will your driver be supported?". Could You please explain a bit, why ALTQ model is placed so close to network adapter driver (that they have to be modified) instead of placing it in upper layers (and leaving NIC drivers untouched)? TIA, -- Pawe³ Ma³achowski From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 30 05:57:45 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E723F16A4CE for ; Fri, 30 Jul 2004 05:57:45 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A9CB43D4C for ; Fri, 30 Jul 2004 05:57:45 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6U5sh0Q049142; Thu, 29 Jul 2004 23:54:43 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 29 Jul 2004 23:55:08 -0600 (MDT) Message-Id: <20040729.235508.112983217.imp@bsdimp.com> To: freebsd-hackers@freebsd.org, pawmal-posting@freebsd.lublin.pl From: "M. Warner Losh" In-Reply-To: <20040729201909.GA12370@shellma.zin.lublin.pl> References: <200407281145.27824.db@traceroute.dk> <200407281502.46395.max@love2party.net> <20040729201909.GA12370@shellma.zin.lublin.pl> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: max@love2party.net Subject: Re: Ready or not? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 05:57:46 -0000 In message: <20040729201909.GA12370@shellma.zin.lublin.pl> Pawel Malachowski writes: : On Wed, Jul 28, 2004 at 03:02:38PM +0200, Max Laier wrote: : : Hello, : : > as PF+ALTQ gateway in production environment. For ALTQ there is the problem : > of "will your driver be supported?". : : Could You please explain a bit, why ALTQ model is placed so close : to network adapter driver (that they have to be modified) instead : of placing it in upper layers (and leaving NIC drivers untouched)? The short answer is because there is buffering (queueing) in the NIC layer, and that limits the ability of of ALTQ to do its job. In order to do QoS type things, this queueing makes it harder without the help of the NIC driver. It is more complicated than this (I don't understand all the details), but that is the jist of a larger presentation of ALTQ that I had the pleasure of viewing at AsiaBSDcon. Warner From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 30 06:59:08 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 527AE16A4CE; Fri, 30 Jul 2004 06:59:08 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6025043D66; Fri, 30 Jul 2004 06:59:07 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i6U6uZOc090377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Jul 2004 09:56:37 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.12.11/8.12.11) id i6U6ucg3036648; Fri, 30 Jul 2004 09:56:38 +0300 (EEST) (envelope-from ru) Date: Fri, 30 Jul 2004 09:56:38 +0300 From: Ruslan Ermilov To: "Stas D.Myasnikov" Message-ID: <20040730065638.GE36338@ip.net.ua> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jTMWTj4UTAEmbWeb" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-hackers@freebsd.org cc: Warner Losh Subject: Re: How to clean out old files after 'make world'? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 06:59:08 -0000 --jTMWTj4UTAEmbWeb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 20, 2004 at 10:23:25PM +0300, Stas D.Myasnikov wrote: > Hello! >=20 > While doing 'make world' I used make.conf with couple on 'NO_*=3Dyes',=20 > e.g. NO_KERBEROS=3Dyes (I don't need Kerberos on my home computer). But= =20 > after rebuilding world and install I saw the old binaries, configs,=20 > etc. of Kerberos and other parts of base that I didn't build. I had=20 > thought that install script removes all unneeded files, but it don't.=20 > How can I clean out this old binaries, configs, etc?.. Is there any=20 > automatic way to do this? >=20 I routinely use find(1) and some secret knowledge about files that do not change their timestamps between installworlds to clean up stale files. Fortunately there are not too much files that install with -C, less in 5.x than in 4.x. Also, Warner Losh worked on a project that would allow to remove files obsoleted between releases. I don't know what the current status of this project is, or if it's still alive. ;) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --jTMWTj4UTAEmbWeb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBCfEmqRfpzJluFF4RAuH8AJsE6DdCOokwpfXQx4QuvZlesCtRxgCgnsTr HG/u+nIz9/6uB3+GKgpOJQ0= =HZ3m -----END PGP SIGNATURE----- --jTMWTj4UTAEmbWeb-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 30 09:19:39 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E078416A4CE; Fri, 30 Jul 2004 09:19:39 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2186543D5F; Fri, 30 Jul 2004 09:19:37 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BqTY5-0004KO-00; Fri, 30 Jul 2004 11:19:33 +0200 Received: from [84.128.140.215] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1BqTY5-0006hQ-00; Fri, 30 Jul 2004 11:19:33 +0200 From: Max Laier To: freebsd-hackers@freebsd.org Date: Fri, 30 Jul 2004 11:17:25 +0200 User-Agent: KMail/1.6.2 References: <20040730065638.GE36338@ip.net.ua> In-Reply-To: <20040730065638.GE36338@ip.net.ua> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_sIhCBMM+XbebzM0"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407301117.32470.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: Warner Losh Subject: Re: How to clean out old files after 'make world'? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 09:19:40 -0000 --Boundary-02=_sIhCBMM+XbebzM0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 30 July 2004 08:56, Ruslan Ermilov wrote: > On Tue, Jul 20, 2004 at 10:23:25PM +0300, Stas D.Myasnikov wrote: > > Hello! > > > > While doing 'make world' I used make.conf with couple on 'NO_*=3Dyes', > > e.g. NO_KERBEROS=3Dyes (I don't need Kerberos on my home computer). But > > after rebuilding world and install I saw the old binaries, configs, > > etc. of Kerberos and other parts of base that I didn't build. I had > > thought that install script removes all unneeded files, but it don't. > > How can I clean out this old binaries, configs, etc?.. Is there any > > automatic way to do this? > > I routinely use find(1) and some secret knowledge about files that > do not change their timestamps between installworlds to clean up > stale files. Fortunately there are not too much files that install > with -C, less in 5.x than in 4.x. > > Also, Warner Losh worked on a project that would allow to remove > files obsoleted between releases. I don't know what the current > status of this project is, or if it's still alive. ;) I am wondering, would it be possible to (automatically) create pkg-plist in= fo=20 for the NO_* targets in make.conf? We could put that into the ports-tree=20 somewhere and if you'd like to remove something completely you can install= =20 the dummy port & pkg-plist and use pkg_delete to clean up. It seems to me that it might be possible to add some kind of Makefile hint= =20 variables (i.e. define a variable in Makefiles/targets that depend on NO_*)= =20 that'd help to generate filelists for the NO_* targets. If this is the case= =20 it should be possible to place pkg descriptions into /var/db/pkg during the= =20 installworld pass. This would also make it easy to get rid of things after = a=20 CDROM install. What do you think? =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --Boundary-02=_sIhCBMM+XbebzM0 Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBChIsXyyEoT62BG0RAsyVAJ4ozAua4wfkV58ph3bpyQug4DzmqACfbVki fFoX+tLzjW2vyOHpGCxjMYw= =C7QE -----END PGP SIGNATURE----- --Boundary-02=_sIhCBMM+XbebzM0-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 30 09:56:03 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEE7A16A4CE; Fri, 30 Jul 2004 09:56:03 +0000 (GMT) Received: from pd3mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8227E43D41; Fri, 30 Jul 2004 09:56:03 +0000 (GMT) (envelope-from colin.percival@wadham.ox.ac.uk) Received: from pd3mr7so.prod.shaw.ca (pd3mr7so-qfe3.prod.shaw.ca [10.0.141.23])2003)) with ESMTP id <0I1N00IRZS6D9D@l-daemon>; Fri, 30 Jul 2004 03:39:49 -0600 (MDT) Received: from pn2ml4so.prod.shaw.ca ([10.0.121.148]) by pd3mr7so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0I1N00LN7S6DHHM0@pd3mr7so.prod.shaw.ca>; Fri, 30 Jul 2004 03:39:49 -0600 (MDT) Received: from piii600.wadham.ox.ac.uk (S0106006067227a4a.vc.shawcable.net [24.87.233.42])2003)) with ESMTP id <0I1N00J1ES6BX6@l-daemon>; Fri, 30 Jul 2004 03:39:49 -0600 (MDT) Date: Fri, 30 Jul 2004 02:36:36 -0700 From: Colin Percival In-reply-to: <200407301117.32470.max@love2party.net> X-Sender: cperciva@popserver.sfu.ca (Unverified) To: Max Laier Message-id: <6.1.0.6.1.20040730022305.03d48568@popserver.sfu.ca> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6 Content-type: text/plain; charset=us-ascii References: <20040730065638.GE36338@ip.net.ua> <200407301117.32470.max@love2party.net> cc: freebsd-hackers@freebsd.org cc: Warner Losh Subject: Re: How to clean out old files after 'make world'? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 09:56:04 -0000 At 02:17 30/07/2004, Max Laier wrote: >I am wondering, would it be possible to (automatically) create pkg-plist info >for the NO_* targets in make.conf? We could put that into the ports-tree >somewhere and if you'd like to remove something completely you can install >the dummy port & pkg-plist and use pkg_delete to clean up. > >It seems to me that it might be possible to add some kind of Makefile hint >variables (i.e. define a variable in Makefiles/targets that depend on NO_*) >that'd help to generate filelists for the NO_* targets. If this is the case >it should be possible to place pkg descriptions into /var/db/pkg during the >installworld pass. This would also make it easy to get rid of things after a >CDROM install. In March, I posted to freebsd-current (subject: Nuking parts of the world) offering a patch which makes it possible to remove some subsystems: http://docs.freebsd.org/cgi/mid.cgi?6.0.1.1.1.20040316023919.039fa5f0 Colin Percival From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 30 11:55:32 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21E5716A57B for ; Fri, 30 Jul 2004 11:55:32 +0000 (GMT) Received: from lakermmtao06.cox.net (lakermmtao06.cox.net [68.230.240.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 702F743D68 for ; Fri, 30 Jul 2004 11:55:31 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao06.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040730115529.YXTS9340.lakermmtao06.cox.net@dolphin.local.net>; Fri, 30 Jul 2004 07:55:29 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.12.11/8.12.11) with ESMTP id i6UBtSYD016553; Fri, 30 Jul 2004 06:55:28 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.12.11/8.12.11/Submit) id i6UBtSKo016552; Fri, 30 Jul 2004 06:55:28 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200407291528.i6TFS59t016221@wek4.com> Date: Fri, 30 Jul 2004 06:55:28 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: William Kirkland cc: freebsd-hackers@freebsd.org Subject: Re: Kernel Configuration script [was Re: "Next Generation" kernel configuration?] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: conrads@cox.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 11:55:32 -0000 On 29-Jul-2004 William Kirkland wrote: > On Tue, Jul 20, 2004 at 07:39:31PM -0500, Conrad J. Sabatier wrote: >> Just musing on an idea here: >> >> I've been thinking for a while now about trying to write a tool to >> make kernel configuration easier, sort of a "make config" (as in >> ports) for the kernel, similar to what's available on some of the >> Linux distros. > > Ok, I have attached some scripts I wrote, to make my life simpler. > Though I do have some concerns that one should write their own, or > use the existing structure and tools. I am willing to show what I > use and share ideas. > > If you choose to use this, please give credit where it is due. As I > have never previously published this, nor anything else. I find the > GNU GPL (http://www.gnu.org/copyleft/gpl.html) acceptable. Use at > your own risk. Well, at this point, I'm not at all sure I even want to try to proceed with working on something like this. I and several others are of the opinion that, in their current state, the files used to describe all of the available kernel options are simply not useable by an automated system, at least not for the sort of thing I had envisioned. And I don't expect that any sort of radical revision of the existing layout would be greeted too warmly by most of the developers. :-) But thanks, I'll take a look at your work. Conrad -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 29 13:22:42 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAEF416A4CE for ; Thu, 29 Jul 2004 13:22:42 +0000 (GMT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (80-219-174-97.dclient.hispeed.ch [80.219.174.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D91643D48 for ; Thu, 29 Jul 2004 13:22:41 +0000 (GMT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:50db:ae61:0:220:afff:fed4:dbcb]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id i6TDMPp01607 verified NO) for ; Thu, 29 Jul 2004 15:22:29 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id i6TDMOe01606; Thu, 29 Jul 2004 15:22:25 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Thu, 29 Jul 2004 15:22:25 +0200 (CEST) Message-Id: <200407291322.i6TDMOe01606@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma To: FreeBSD Hackers X-Mailman-Approved-At: Fri, 30 Jul 2004 12:10:41 +0000 Subject: man/cat pages, compressed/or not X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 13:22:43 -0000 Salutations, dudes. I've added an unsightly hack to `man' so that when it creates catpages from the compressed manpages, it's possible that they can be created uncompressed (for the benefit of older slower machines with newer big disks). But I'm wondering what's the best way to do this, if this is something that might be of general interest... (I think I also took a meatgrinder to `catman' some time back to get it to spit out uncompressed pages. I can't remember what problems I may have had, in that `man' didn't seem to want to use these pages, but that may be solved by my latest hacks.) There's a make.conf variable one can set to create uncompressed man pages; should there be something similar to decide whether man should create compressed or uncompressed catpages? Right now, I just let one define another option, which makes man put out uncompressed pages, in the Makefile (where the DO_COMPRESS is defined). Purely as a proof of concept. Is such an option desirable for anyone else as well? With this, one can have compressed manpages (to save space on seldom-accessed files), and uncompressed corresponding catpages for fast access... (I know, you'll tell me that if I have a big disk and a slow machine, there's no reason to want compressed manpages to go with the uncompressed catpages, so set NOMANCOMPRESS=true.) thanks barry bouwsma From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 30 14:31:45 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2879516A4CE; Fri, 30 Jul 2004 14:31:45 +0000 (GMT) Received: from minerva.int.gov.br (nat.int.gov.br [200.20.196.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F34C43D41; Fri, 30 Jul 2004 14:31:43 +0000 (GMT) (envelope-from jonny@jonny.eng.br) Received: from jonny.eng.br (jonny.int.gov.br [10.0.8.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by minerva.int.gov.br (Postfix) with ESMTP id 64AEFBE5AF; Fri, 30 Jul 2004 11:31:41 -0300 (BRT) Message-ID: <410A5BCD.6040204@jonny.eng.br> Date: Fri, 30 Jul 2004 11:31:41 -0300 From: =?ISO-8859-1?Q?Jo=E3o_Carlos_Mendes_Lu=EDs?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Max Laier References: <20040730065638.GE36338@ip.net.ua> <200407301117.32470.max@love2party.net> In-Reply-To: <200407301117.32470.max@love2party.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: Warner Losh Subject: Re: How to clean out old files after 'make world'? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 14:31:45 -0000 Max Laier wrote: > On Friday 30 July 2004 08:56, Ruslan Ermilov wrote: >>On Tue, Jul 20, 2004 at 10:23:25PM +0300, Stas D.Myasnikov wrote: >>>While doing 'make world' I used make.conf with couple on 'NO_*=yes', >>>e.g. NO_KERBEROS=yes (I don't need Kerberos on my home computer). But >>>after rebuilding world and install I saw the old binaries, configs, >>>etc. of Kerberos and other parts of base that I didn't build. I had >>>thought that install script removes all unneeded files, but it don't. >>>How can I clean out this old binaries, configs, etc?.. Is there any >>>automatic way to do this? >> >>I routinely use find(1) and some secret knowledge about files that >>do not change their timestamps between installworlds to clean up >>stale files. Fortunately there are not too much files that install >>with -C, less in 5.x than in 4.x. >> >>Also, Warner Losh worked on a project that would allow to remove >>files obsoleted between releases. I don't know what the current >>status of this project is, or if it's still alive. ;) > > I am wondering, would it be possible to (automatically) create pkg-plist info > for the NO_* targets in make.conf? We could put that into the ports-tree > somewhere and if you'd like to remove something completely you can install > the dummy port & pkg-plist and use pkg_delete to clean up. This resembles linux RPMs for system files. And the idea is not bad. Having system files registered just like ports would make it easier some operations, including binary upgrade. I think the ports system needs some work before this would be feasible, though. IIRC, Solaris also registers system files with the same mechanism used for applications. > It seems to me that it might be possible to add some kind of Makefile hint > variables (i.e. define a variable in Makefiles/targets that depend on NO_*) > that'd help to generate filelists for the NO_* targets. If this is the case > it should be possible to place pkg descriptions into /var/db/pkg during the > installworld pass. This would also make it easy to get rid of things after a > CDROM install. > > What do you think? I think the problem deserves attention, and any implementation tests are welcome. From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 30 16:35:20 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D14516A4CE for ; Fri, 30 Jul 2004 16:35:20 +0000 (GMT) Received: from mail.revolutionsp.com (ganymede.revolutionsp.com [64.246.0.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB39943D1D for ; Fri, 30 Jul 2004 16:35:19 +0000 (GMT) (envelope-from klr@6s-gaming.com) Received: from mail.revolutionsp.com (localhost [127.0.0.1]) by mail.revolutionsp.com (Postfix) with ESMTP id 24AFA15C95 for ; Fri, 30 Jul 2004 13:32:44 +0000 (GMT) Received: from 81.84.175.12 (SquirrelMail authenticated user klr@6s-gaming.com); by mail.revolutionsp.com with HTTP; Fri, 30 Jul 2004 13:32:44 -0000 (GMT) Message-ID: <49388.81.84.175.12.1091194364.squirrel@81.84.175.12> Date: Fri, 30 Jul 2004 13:32:44 -0000 (GMT) From: "Hugo Silva" To: freebsd-hackers@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: 5.2.1-p9 SMP kernel panic X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 16:35:20 -0000 Hi, I am getting a panic on a 5.2.1-p9 Dual Xeon 3.0ghz w/ SMP enabled. The panic always happens during high loads (create a new jail, compile something, etc) I know another user had this problem a while ago, and adding an option to the kernel solved his problem. But I can't locate this thread (could by freebsd-archives, but doesnt contain the reply I saw the last time, must have read it somewhere else) Does anyone know what is the magic option I have to add to the kernel to prevent these panics? I can't give details about the panic (datacenter still didn't mail me a copy of the text), but I'm pretty sure it's due to high loads -- I stopped seti@home and let the server idle, it's been up for 3 days when it wouldn't be up for more than 24 hours. Thanks in advance! Hugo -- www.6s-gaming.com