From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 03:03:55 2003 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 7BF3E37B401 for ; Sun, 25 May 2003 03:03:55 -0700 (PDT) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D7B943F85 for ; Sun, 25 May 2003 03:03:54 -0700 (PDT) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 95686530E; Sun, 25 May 2003 12:03:51 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: kientzle@acm.org References: <3ECEFA18.7060706@acm.org> <3ED04F27.5020102@acm.org> From: Dag-Erling Smorgrav Date: Sun, 25 May 2003 12:03:50 +0200 In-Reply-To: <3ED04F27.5020102@acm.org> (Tim Kientzle's message of "Sat, 24 May 2003 22:05:43 -0700") Message-ID: User-Agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-hackers@freebsd.org Subject: Re: fetchListFTP: implemented, but crippled 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 May 2003 10:03:55 -0000 Tim Kientzle writes: > Dag-Erling Smorgrav wrote: > > Tim Kientzle writes: > > > Easiest fix: move 'name' field to end (which > > > permits variably-sizing it) and redefine API > > > to return a linked-list > > That would work. > I'll implement a variation on this (create a new > structure to avoid breaking binary compat). You'll still have to break the API to make fetchList() return the new struct instead of the old. It's not a problem, really, considering that fetchList() was only implemented for local files. I'm not even sure we need bother bumping the library major. Though while you're at it, struct urlent should probably be renamed to struct url_ent for consistency. > Based on the copyright message, you are > the author. Thoughts? ;-) What, haven't had enough of me yet? :) DES -- Dag-Erling Smorgrav - des@ofug.org From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 07:56:18 2003 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 CC68837B401 for ; Sun, 25 May 2003 07:56:18 -0700 (PDT) Received: from bart.LF.net (bart.LF.net [212.9.190.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5117C43F3F for ; Sun, 25 May 2003 07:56:18 -0700 (PDT) (envelope-from root@bart.LF.net) Received: from root by bart.LF.net with local (Exim 4.10) id 19JwuU-000PQ7-00 for hackers@FreeBSD.org; So, 25 Mai 2003 16:55:42 +0200 Date: Sun, 25 May 2003 16:55:42 +0200 From: Marc Schoechlin To: hackers@FreeBSD.org Message-ID: <20030525145542.GA97711@LF.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Ticket-Action: x X-Ticket-Nr: x Subject: Change request for mount_null manpage 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 May 2003 14:56:19 -0000 I'm using mount_null now for some months - and i never had a problem with this. The manpage says the follwing about mount_null: -- ... BUGS THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET. This code also needs an owner in order to be less dangerous - serious hackers can apply by sending mail to and announcing their intent to take it over. ... -- Is this still true ? The manpage was written on May 1, 1995....thats eight years ago. I will be glad if, that will be removed in future releases. Best regards Marc Schoechlin -- Gruss / Best regards | LF.net GmbH | fon +49 711 90074-413 Marc Schoechlin | Ruppmannstr. 27 | fax +49 711 90074-33 ms@LF.net | D-70565 Stuttgart | http://www.lf.net From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 09:04:20 2003 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 3BA2637B401; Sun, 25 May 2003 09:04:20 -0700 (PDT) Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id D81F443F93; Sun, 25 May 2003 09:04:17 -0700 (PDT) (envelope-from andymac@bullseye.apana.org.au) Received: from bullseye.apana.org.au (dialup-2.aaa.net.au [203.14.230.67]) by posgate.acis.com.au (8.12.7/8.12.7) with ESMTP id h4PG4BGk012855; Mon, 26 May 2003 02:04:13 +1000 Received: from bullseye.apana.org.au (localhost.apana.org.au [127.0.0.1]) h4PG4W1F056979; Mon, 26 May 2003 02:04:35 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Received: from localhost (andymac@localhost)h4PDFGNn052350; Sun, 25 May 2003 23:15:16 +1000 (EST) Date: Sun, 25 May 2003 23:15:16 +1000 (EST) From: Andrew MacIntyre To: freebsd-hackers@FreeBSD.org Message-ID: <20030525220222.K52253@bullseye.apana.org.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang) cc: alane@FreeBSD.org Subject: setting stacksize in "initial" thread (pthreads, 4.8R) 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 May 2003 16:04:20 -0000 I have a situation with a Python interpreter built from Python CVS sources that is hitting the stack limit for the "initial" thread imposed by libc_r: PTHREAD_STACK_INITIAL in /usr/src/lib/libc_r/uthread/pthread_private.h is set to 1MB (0x100000). Compiler optimisation settings do affect whether Python's internal stack check activate before the hard limit bites, and more recent versions of gcc (than the stock gcc in 4.8R) are more aggressive users of stack. I have not been able to find any documented way to control the stacksize of the "initial" thread either programmatically, via a compile/link option or by way of a resource limit in login.conf. Is this possible without rebuilding libc_r? I don't yet have a 5.x install to check the situation - does the new libthr/libkse setup differ in respect to the above? Using the Linuxthreads port is a workaround for this situation, but I'd rather that it not be necessary to rely on an extra dependancy. Cc'ed to the Python port maintainer for info. Regards, Andrew. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac@pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 09:32:24 2003 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 C2A9E37B401; Sun, 25 May 2003 09:32:24 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17D8243F3F; Sun, 25 May 2003 09:32:24 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from pcnet1.pcnet.com (localhost [127.0.0.1]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h4PGWJwQ001114; Sun, 25 May 2003 12:32:19 -0400 (EDT) Received: from localhost (eischen@localhost)h4PGWIOG001110; Sun, 25 May 2003 12:32:18 -0400 (EDT) Date: Sun, 25 May 2003 12:32:18 -0400 (EDT) From: Daniel Eischen To: Andrew MacIntyre In-Reply-To: <20030525220222.K52253@bullseye.apana.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: alane@freebsd.org Subject: Re: setting stacksize in "initial" thread (pthreads, 4.8R) 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 May 2003 16:32:25 -0000 On Sun, 25 May 2003, Andrew MacIntyre wrote: > I have a situation with a Python interpreter built from Python > CVS sources that is hitting the stack limit for the "initial" thread > imposed by libc_r: PTHREAD_STACK_INITIAL in > /usr/src/lib/libc_r/uthread/pthread_private.h is set to 1MB (0x100000). This is not configurable without recompiling the library. > Compiler optimisation settings do affect whether Python's internal stack > check activate before the hard limit bites, and more recent versions of > gcc (than the stock gcc in 4.8R) are more aggressive users of stack. > > I have not been able to find any documented way to control the stacksize > of the "initial" thread either programmatically, via a compile/link > option or by way of a resource limit in login.conf. Is this possible > without rebuilding libc_r? No. > I don't yet have a 5.x install to check the situation - does the new > libthr/libkse setup differ in respect to the above? Libkse uses the same initial stack size; I can't speak for libthr. Is this something that is common to all python scripts, or is it just your own script(s) that is(are) getting caught. It seems 1MB is an awful lot to be on the stack, and perhaps some things are better malloc'd. -- Dan Eischen From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 10:58:05 2003 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 8087D37B401 for ; Sun, 25 May 2003 10:58:05 -0700 (PDT) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF28943FA3 for ; Sun, 25 May 2003 10:58:04 -0700 (PDT) (envelope-from kientzle@acm.org) Received: from acm.org (big.x.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id h4PHw3tJ066929; Sun, 25 May 2003 10:58:04 -0700 (PDT) (envelope-from kientzle@acm.org) Message-ID: <3ED1049B.8010409@acm.org> Date: Sun, 25 May 2003 10:59:55 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.6) Gecko/20011206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dag-Erling Smorgrav References: <3ECEFA18.7060706@acm.org> <3ED04F27.5020102@acm.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: fetchListFTP: implemented, but crippled X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kientzle@acm.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 May 2003 17:58:05 -0000 Dag-Erling Smorgrav wrote: > Tim Kientzle writes: >>Dag-Erling Smorgrav wrote: >>>Tim Kientzle writes: >>>>Easiest fix: move 'name' field to end (which >>>>permits variably-sizing it) and redefine API >>>>to return a linked-list >>>> >>>That would work. >>> >>I'll implement a variation on this (create a new >>structure to avoid breaking binary compat). > > You'll still have to break the API .... Sorry, let me spell it out in more detail: Proposal: New public functions to add to libfetch: fetchList2, fetchList2URL, fetchList2FTP, fetchList2File These are identical to the existing "fetchList*" functions except for the return type. New struct definition for fetch.h: struct url_ent_list { struct url_ent_list *next; struct url_stat stat; char name[PATH_MAX]; } No binary breakage, since existing functions are still there. The old fetchList/fetchListURL/fetchListFile are never used in /usr/src, but that doesn't mean they're unused. If there's consensus on removing them, let's do it right: modify those functions to emit a warning message whenever they're used (ideally, whenever they're linked with, which might be possible with gcc these days?): Warning: fetchList() is deprecated and will be removed from libfetch on January 1, 2004. Use fetchList2() instead. Then, follow through with the promise. ;-) Tim From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 11:23:36 2003 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 F421237B401 for ; Sun, 25 May 2003 11:23:35 -0700 (PDT) Received: from mail.auriga.ru (mail.auriga.ru [80.240.102.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61E7243F85 for ; Sun, 25 May 2003 11:23:35 -0700 (PDT) (envelope-from alex.neyman@auriga.ru) Received: from mail.loopback.interface ([127.0.0.1] helo=vagabond.auriga.ru) by mail.auriga.ru with esmtp (Exim 4.14) id 19K0CP-0005EN-Hq; Sun, 25 May 2003 22:26:25 +0400 From: Alexey Neyman Organization: Auriga, Inc. To: kientzle@acm.org, Dag-Erling Smorgrav Date: Sun, 25 May 2003 22:23:31 +0400 User-Agent: KMail/1.5.1 References: <3ECEFA18.7060706@acm.org> <3ED1049B.8010409@acm.org> In-Reply-To: <3ED1049B.8010409@acm.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305252223.31923.alex.neyman@auriga.ru> cc: freebsd-hackers@freebsd.org Subject: Re: fetchListFTP: implemented, but crippled 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 May 2003 18:23:36 -0000 Hi, there! On Sunday 25 May 2003 21:59, Tim Kientzle wrote: TK> right: modify those functions to emit a warning message TK> whenever they're used (ideally, whenever they're linked TK> with, which might be possible with gcc these days?): TK> Warning: fetchList() is deprecated and will be removed TK> from libfetch on January 1, 2004. Use fetchList2() instead. I believe that's what __warn_references() macro is for (sys/cdefs.h): __warn_references(fetchList, "It gonna die, die!") Regards, Alexey. -- A quoi ca sert d'etre sur la terre Si c'est pour faire nos vies a genoux? From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 12:09:00 2003 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 0B3A937B401 for ; Sun, 25 May 2003 12:09:00 -0700 (PDT) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BC8743F3F for ; Sun, 25 May 2003 12:08:59 -0700 (PDT) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 86E88530E; Sun, 25 May 2003 21:08:56 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: kientzle@acm.org References: <3ECEFA18.7060706@acm.org> <3ED04F27.5020102@acm.org> <3ED1049B.8010409@acm.org> From: Dag-Erling Smorgrav Date: Sun, 25 May 2003 21:08:55 +0200 In-Reply-To: <3ED1049B.8010409@acm.org> (Tim Kientzle's message of "Sun, 25 May 2003 10:59:55 -0700") Message-ID: User-Agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-hackers@freebsd.org Subject: Re: fetchListFTP: implemented, but crippled 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 May 2003 19:09:00 -0000 Tim Kientzle writes: > Proposal: > > New public functions to add to libfetch: > fetchList2, fetchList2URL, fetchList2FTP, fetchList2File > > These are identical to the existing "fetchList*" functions > except for the return type. There's no point. Nobody uses the existing fetchList* interface since it's never been implemented. DES -- Dag-Erling Smorgrav - des@ofug.org From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 15:58:28 2003 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 D2FED37B401; Sun, 25 May 2003 15:58:28 -0700 (PDT) Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95FDB43FAF; Sun, 25 May 2003 15:58:26 -0700 (PDT) (envelope-from andymac@bullseye.apana.org.au) Received: from bullseye.apana.org.au (dialup-1.aaa.net.au [203.14.230.66]) by posgate.acis.com.au (8.12.7/8.12.7) with ESMTP id h4PMwHGk006095; Mon, 26 May 2003 08:58:18 +1000 Received: from bullseye.apana.org.au (localhost.apana.org.au [127.0.0.1]) h4PMvV19057788; Mon, 26 May 2003 08:57:31 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Received: from localhost (andymac@localhost)h4PMvVcQ057785; Mon, 26 May 2003 08:57:31 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Date: Mon, 26 May 2003 08:57:31 +1000 (EST) From: Andrew MacIntyre To: Daniel Eischen In-Reply-To: Message-ID: <20030526084710.A57768@bullseye.apana.org.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang) cc: freebsd-hackers@freebsd.org cc: alane@freebsd.org Subject: Re: setting stacksize in "initial" thread (pthreads, 4.8R) 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 May 2003 22:58:29 -0000 On Sun, 25 May 2003, Daniel Eischen wrote: > On Sun, 25 May 2003, Andrew MacIntyre wrote: > > > I have a situation with a Python interpreter built from Python > > CVS sources that is hitting the stack limit for the "initial" thread > > imposed by libc_r: PTHREAD_STACK_INITIAL in > > /usr/src/lib/libc_r/uthread/pthread_private.h is set to 1MB (0x100000). {...} > Is this something that is common to all python scripts, or is > it just your own script(s) that is(are) getting caught. It > seems 1MB is an awful lot to be on the stack, and perhaps some > things are better malloc'd. The problem actually occurs with recursive matches in Python's regex engine. Python has a hardcoded regex recursion limit, which has trapped ballistic matches before running out of the default stack. However a couple of recent fixes to the regex engine have increased stack consumption, and the hard limit has to be lowered. The failures are being exhibited by the Python regex engine regression tests. Compiler optimisation plays a role here:- - gcc 2.95: -O3 hits the stack limit, -O2 doesn't; - gcc 3.2.2: -Os is the only optimisation setting that doesn't hit the stack limit. (these all with the default regex recursion depth). I was hoping there was a way to avoid FreeBSD having a recursion limit lower than any other OS in the presence of threads, but your response indicates there isn't - at least using libc_r. Using the Linuxthreads port instead of libc_r works fine. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac@pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 16:04:38 2003 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 4D30537B401; Sun, 25 May 2003 16:04:38 -0700 (PDT) Received: from mail.tel.fer.hr (zg05-198.dialin.iskon.hr [213.191.138.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CF4043F93; Sun, 25 May 2003 16:04:33 -0700 (PDT) (envelope-from zec@tel.fer.hr) Received: from tel.fer.hr (marko-tp.katoda.net [192.168.201.109]) by mail.tel.fer.hr (8.12.6/8.12.6) with ESMTP id h4PN0Rfa002359; Mon, 26 May 2003 01:00:31 +0200 (CEST) (envelope-from zec@tel.fer.hr) Message-ID: <3ED14BF3.139CAC32@tel.fer.hr> Date: Mon, 26 May 2003 01:04:19 +0200 From: Marko Zec X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org, net@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Network stack cloning / virtualization patches 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 May 2003 23:04:38 -0000 Hi all, at http://www.tel.fer.hr/zec/vimage/ you can find a set of patches against 4.8-RELEASE kernel that provide support for network stack cloning. The patched kernel allows multiple fully independent network stack instances to simultaneously coexist within a single OS kernel, providing a foundation for supporting diverse new applications, including: - Enhanced virtual hosting (think of jails with its own private set of network interfaces, IP addresses, routing tables, ipfw and dummynet instance etc.); - High-performance real-time network simulation / emulation; - Fully isolated overlay VPN provisioning (using IP tunnels), including the possibility of creating nested VPNs. The network stacks are embedded in new resource container entities named "virtual images". Each process and network stack instance within the system has to be associated with a virtual image, which in effect becomes a light or pseudo virtual machine entity. Additional goodies include the possibility to control some other resources besides the network stack, most notably the independent CPU load and usage accounting, as well as feedback-driven proportional share scheduling among virtual images. For more details, check the above URL. Note that the patch was designed to allow all existing applications and utilities to run unmodified on the patched kernel, so no recompiling of the userland is necessary. Hope you'll find use for the new framework :-) Cheers, Marko From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 16:44:46 2003 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 313DC37B404; Sun, 25 May 2003 16:44:46 -0700 (PDT) Received: from jkh-gw.queasyweasel.com (adsl-64-173-3-158.dsl.sntc01.pacbell.net [64.173.3.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2391543F75; Sun, 25 May 2003 16:44:45 -0700 (PDT) (envelope-from jkh@queasyweasel.com) Received: from queasyweasel.com (jkh@narcissus.queasyweasel.com [64.173.15.99])h4PNhb2J075547; Sun, 25 May 2003 16:43:37 -0700 (PDT) (envelope-from jkh@queasyweasel.com) Date: Sun, 25 May 2003 16:44:42 -0700 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: Marko Zec From: Jordan K Hubbard In-Reply-To: <3ED14BF3.139CAC32@tel.fer.hr> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) cc: hackers@freebsd.org cc: net@freebsd.org Subject: Re: Network stack cloning / virtualization patches 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 May 2003 23:44:46 -0000 Wow, this is VERY impressive! I wish all FreeBSD "research project" work of this nature was as complete, functional or compatible with existing applications as yours appears to be. Have you thought about extending this to the point to where each independent instance truly is a functionally independent kernel instance, similar to some of the "virtual Linux" work done by/for IBM so that you can run n "linuxes" on a single 3090 processor? - Jordan On Sunday, May 25, 2003, at 04:04 PM, Marko Zec wrote: > Hi all, > > at http://www.tel.fer.hr/zec/vimage/ you can find a set of patches > against 4.8-RELEASE kernel that provide support for network stack > cloning. The patched kernel allows multiple fully independent network > stack instances to simultaneously coexist within a single OS kernel, > providing a foundation for supporting diverse new applications, > including: > > - Enhanced virtual hosting (think of jails with its own private set of > network interfaces, IP addresses, routing tables, ipfw and dummynet > instance etc.); > - High-performance real-time network simulation / emulation; > - Fully isolated overlay VPN provisioning (using IP tunnels), including > the possibility of creating nested VPNs. > > The network stacks are embedded in new resource container entities > named "virtual images". Each process and network stack instance within > the system has to be associated with a virtual image, which in effect > becomes a light or pseudo virtual machine entity. Additional goodies > include the possibility to control some other resources besides the > network stack, most notably the independent CPU load and usage > accounting, as well as feedback-driven proportional share scheduling > among virtual images. For more details, check the above URL. > Note that the patch was designed to allow all existing applications and > utilities to run unmodified on the patched kernel, so no recompiling of > the userland is necessary. > Hope you'll find use for the new framework :-) > Cheers, > > Marko > > _______________________________________________ > 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" > -- Jordan K. Hubbard Engineering Manager, BSD technology group Apple Computer From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 17:19:13 2003 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 32CDA37B401; Sun, 25 May 2003 17:19:12 -0700 (PDT) Received: from mail.tel.fer.hr (zg05-198.dialin.iskon.hr [213.191.138.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91DF943F75; Sun, 25 May 2003 17:19:10 -0700 (PDT) (envelope-from zec@tel.fer.hr) Received: from tel.fer.hr (marko-tp.katoda.net [192.168.201.109]) by mail.tel.fer.hr (8.12.6/8.12.6) with ESMTP id h4Q0F3fa002376; Mon, 26 May 2003 02:15:08 +0200 (CEST) (envelope-from zec@tel.fer.hr) Message-ID: <3ED15D6F.1BF1BB37@tel.fer.hr> Date: Mon, 26 May 2003 02:18:55 +0200 From: Marko Zec X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Jordan K Hubbard References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: net@freebsd.org Subject: Re: Network stack cloning / virtualization patches 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 May 2003 00:19:13 -0000 Jordan K Hubbard wrote: > Have you thought about > extending this to the point to where each independent instance truly is > a functionally independent kernel instance, similar to some of the > "virtual Linux" work done by/for IBM so that you can run n "linuxes" > on a single 3090 processor? My model is much more in line with the pseudo-VM concepts, like the jail is (it actually reuses much of the jail code for userland separation between processes running in different virtual images). However, I'm only virtualizing certain resources _within_ the kernel, albeit the entire network stack is quite a big piece of resource :-) This is fundamentally different from what IBM does, as they virtualize the entire hardware and run fully contained OS images within the VMs. Each approach has its advantages and drawbacks, of course. IMO, the main benefits of the "light" VM model lie in near zero performance penalty compared to the unmodified OS, as well as in efficient usage of hardware resources (memory, filesystems). On the other hand, IBM's true VM shines in isolation between the VMs, but lags in efficiency... So, I'd certainly like to virtualize more system resources and make virtual images as independent from each other as possible, but they will always have to share the same kernel. Cheers, Marko From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 18:38:04 2003 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 4A0CB37B401; Sun, 25 May 2003 18:38:04 -0700 (PDT) Received: from jkh-gw.queasyweasel.com (adsl-64-173-3-158.dsl.sntc01.pacbell.net [64.173.3.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 960CB43F75; Sun, 25 May 2003 18:38:03 -0700 (PDT) (envelope-from jkh@queasyweasel.com) Received: from queasyweasel.com (jkh@narcissus.queasyweasel.com [64.173.15.99])h4Q1at2J075692; Sun, 25 May 2003 18:36:55 -0700 (PDT) (envelope-from jkh@queasyweasel.com) Date: Sun, 25 May 2003 18:38:01 -0700 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: Marko Zec From: Jordan K Hubbard In-Reply-To: <3ED15D6F.1BF1BB37@tel.fer.hr> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) cc: hackers@freebsd.org cc: net@freebsd.org Subject: Re: Network stack cloning / virtualization patches 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 May 2003 01:38:04 -0000 On Sunday, May 25, 2003, at 05:18 PM, Marko Zec wrote: > So, I'd certainly like to virtualize more system resources and make > virtual images as independent from each other as possible, but they > will always > have to share the same kernel. That's actually what I was talking about - my comparison to what IBM's done may have been a bad example since, as you say, they've virtualized the hardware in true IBM (shades of VM) fashion. I think that's actually overkill for many usage scenarios since all you really want is the ability to run an "instance" of the OS which allows for all the user-visible configuration knobs to be changed and the appropriate user-visible resource limits to be enforced independently. Essentially a jail where it's literally impossible to tell that you're not the only "OS" on the machine or to affect a user or resource running on another instance. -- Jordan K. Hubbard Engineering Manager, BSD technology group Apple Computer From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 20:32:09 2003 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 4FAED37B401; Sun, 25 May 2003 20:32:09 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7345743F75; Sun, 25 May 2003 20:32:08 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from pcnet1.pcnet.com (localhost [127.0.0.1]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h4Q3VfwQ014431; Sun, 25 May 2003 23:31:42 -0400 (EDT) Received: from localhost (eischen@localhost)h4Q3Vfh6014427; Sun, 25 May 2003 23:31:41 -0400 (EDT) Date: Sun, 25 May 2003 23:31:41 -0400 (EDT) From: Daniel Eischen To: Andrew MacIntyre In-Reply-To: <20030526084710.A57768@bullseye.apana.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: alane@freebsd.org Subject: Re: setting stacksize in "initial" thread (pthreads, 4.8R) 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 May 2003 03:32:09 -0000 On Mon, 26 May 2003, Andrew MacIntyre wrote: > On Sun, 25 May 2003, Daniel Eischen wrote: > > > On Sun, 25 May 2003, Andrew MacIntyre wrote: > > > > > I have a situation with a Python interpreter built from Python > > > CVS sources that is hitting the stack limit for the "initial" thread > > > imposed by libc_r: PTHREAD_STACK_INITIAL in > > > /usr/src/lib/libc_r/uthread/pthread_private.h is set to 1MB (0x100000). > > {...} > > > Is this something that is common to all python scripts, or is > > it just your own script(s) that is(are) getting caught. It > > seems 1MB is an awful lot to be on the stack, and perhaps some > > things are better malloc'd. > > The problem actually occurs with recursive matches in Python's regex > engine. Python has a hardcoded regex recursion limit, which has trapped > ballistic matches before running out of the default stack. However a > couple of recent fixes to the regex engine have increased stack > consumption, and the hard limit has to be lowered. How do you know it is the main thread stack and not a different thread stack that is getting exceeded? By default, threads other than main get a 64K stack, and this is totally configurable by the application. -- Dan Eischen From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 21:15:14 2003 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 CF17E37B401 for ; Sun, 25 May 2003 21:15:14 -0700 (PDT) Received: from procyon.firepipe.net (procyon.firepipe.net [198.78.66.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FC6543F3F for ; Sun, 25 May 2003 21:15:14 -0700 (PDT) (envelope-from will@csociety.org) Received: by procyon.firepipe.net (Postfix, from userid 1000) id C078920C52; Sun, 25 May 2003 21:15:13 -0700 (PDT) Date: Sun, 25 May 2003 21:15:13 -0700 From: Will Andrews To: freebsd-hackers@freebsd.org Message-ID: <20030526041513.GP81874@procyon.firepipe.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i cc: Will Andrews Subject: Best serial console server construction method? 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 May 2003 04:15:15 -0000 Hi all, In my quest to make my little network of computers more useful for kernel hacking and testing, I'm attempting to build a very cheap serial console server. Basically, the idea is that I'm going to use a computer that will be used for other purposes and add 8 serial ports. How am I going to do that cheaply? Well, N-port serial cards (where N is >= 4) cost a few hundred dollars from everywhere I could see (granted, they're niche items and are accordingly priced). So I came up with the following scheme. If the computer in question has two USB ports, I could purchase two 4-port USB hubs and get 8 single-port serial adapters. So far as I can tell, the total cost would be approximately: 8 x USB->RS232 DB9 Male @ $8/ea = $64 2 x 4-port USB hub @ $8/ea = $16 extra $ for misc. costs $20 Total: $100 Average per port: $12.50 So my question is: has anyone else done this kind of thing before? I am well aware of the flakiness in FreeBSD's USB stack, but supposedly USB hubs and USB->RS232 adapters work without a hitch. If so, this could be the most economical approach to building a serial console server. Thanks for any comments. Please Cc: me as I am not subscribed to freebsd-hackers at this space-time vector. Regards, -- wca From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 22:50:25 2003 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 93ED737B401 for ; Sun, 25 May 2003 22:50:25 -0700 (PDT) Received: from mail.halplant.com (ip68-98-167-210.nv.nv.cox.net [68.98.167.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCB9343F93 for ; Sun, 25 May 2003 22:50:24 -0700 (PDT) (envelope-from A.J.Caines@halplant.com) Received: by mail.halplant.com (Postfix, from userid 1001) id 32900A9; Mon, 26 May 2003 01:50:24 -0400 (EDT) Date: Mon, 26 May 2003 01:50:24 -0400 From: Andrew J Caines To: hackers@FreeBSD.org Message-ID: <20030526055024.GN383@hal9000.halplant.com> Mail-Followup-To: hackers@FreeBSD.org References: <20030525145542.GA97711@LF.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030525145542.GA97711@LF.net> Organization: H.A.L. Plant X-PGP-Fingerprint: C59A 2F74 1139 9432 B457 0B61 DDF2 AA61 67C3 18A1 X-Powered-by: FreeBSD 4.8-STABLE X-URL: http://halplant.com:88/ X-Yahoo-Profile: AJ_Z0 Importance: Normal User-Agent: Mutt/1.5.4i Subject: Re: Change request for mount_null manpage X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Andrew J Caines List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2003 05:50:25 -0000 Marc, > I'm using mount_null now for some months - and i never had a problem with this. Are you using it for rw mounts and if so, then what kind or write volume and sizes do you handle? Usually when this comes up, folks are using null ro mounts and the rare (and sometime unintentional) rw mounts do little or no writing. If anyone is doing significant volume or size writes, then I've not heared mention of it. Look through the sys/fs/nullfs cvsweb pages[1] to see what few changes have happened in the filesystem code in recent times. There are a few specific code changes (ie. not cleanup or restructuring), but I can't tell just from looking how significant they are. [1] http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/fs/nullfs/ -Andrew- -- _______________________________________________________________________ | -Andrew J. Caines- Unix Systems Engineer A.J.Caines@halplant.com | | "They that can give up essential liberty to obtain a little temporary | | safety deserve neither liberty nor safety" - Benjamin Franklin, 1759 | From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 23:24:17 2003 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 B7C4D37B401 for ; Sun, 25 May 2003 23:24:17 -0700 (PDT) Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id A69E743F75 for ; Sun, 25 May 2003 23:24:09 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from foem (IDENT:chuckwebweaving.org@foem [10.11.0.2]) h4Q6O4v7057478; Mon, 26 May 2003 08:24:04 +0200 (CEST) (envelope-from dirkx@webweaving.org) Date: Mon, 26 May 2003 08:24:04 +0200 (CEST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@foem To: Will Andrews In-Reply-To: <20030526041513.GP81874@procyon.firepipe.net> Message-ID: <20030526082236.C43487-100000@foem> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: Best serial console server construction method? 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 May 2003 06:24:18 -0000 > use a computer that will be used for other purposes and add 8 > serial ports. How am I going to do that cheaply? Well, N-port > serial cards (where N is >= 4) cost a few hundred dollars from > everywhere I could see (granted, they're niche items and are > accordingly priced). So I came up with the following scheme. You may want to check ebay (or its local ilk) for a serial terminal server. They are usually available there and in the 25-75 dollar range for a <16 port version. Dw. From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 23:57:27 2003 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 2211C37B401; Sun, 25 May 2003 23:57:27 -0700 (PDT) Received: from mwinf0403.wanadoo.fr (smtp5.wanadoo.fr [193.252.22.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id F361343FBD; Sun, 25 May 2003 23:57:25 -0700 (PDT) (envelope-from vjardin@wanadoo.fr) Received: from venus.vincentjardin.net (unknown [80.11.204.203]) by mwinf0403.wanadoo.fr (SMTP Server) with ESMTP id 7E97E5000340; Mon, 26 May 2003 08:57:24 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-1" From: Vincent Jardin To: Marko Zec , hackers@freebsd.org, net@freebsd.org Date: Mon, 26 May 2003 08:57:26 +0200 User-Agent: KMail/1.4.3 References: <3ED14BF3.139CAC32@tel.fer.hr> In-Reply-To: <3ED14BF3.139CAC32@tel.fer.hr> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200305260857.26994.vjardin@wanadoo.fr> cc: riccardo.scandariato@polito.it Subject: Re: Network stack cloning / virtualization patches 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 May 2003 06:57:27 -0000 Congratulation. Since the last EuroBSD 2002 conference, there are 2 architectures to supp= ort=20 VPNs with FreeBSD : your patch and the Riccardo Scandariato one=20 (http://softeng.polito.it/freebsd/) that is very good too. =46rom a VPN point of view, how could both projects be compared ? Do you think that both projects could be merged or are there too much=20 differences between your two projects ? Regards, Vincent Le Lundi 26 Mai 2003 01:04, Marko Zec a =E9crit : > Hi all, > > at http://www.tel.fer.hr/zec/vimage/ you can find a set of patches > against 4.8-RELEASE kernel that provide support for network stack > cloning. The patched kernel allows multiple fully independent network > stack instances to simultaneously coexist within a single OS kernel, > providing a foundation for supporting diverse new applications, > including: > > - Enhanced virtual hosting (think of jails with its own private set of > network interfaces, IP addresses, routing tables, ipfw and dummynet > instance etc.); > - High-performance real-time network simulation / emulation; > - Fully isolated overlay VPN provisioning (using IP tunnels), including > the possibility of creating nested VPNs. > > The network stacks are embedded in new resource container entities > named "virtual images". Each process and network stack instance within > the system has to be associated with a virtual image, which in effect > becomes a light or pseudo virtual machine entity. Additional goodies > include the possibility to control some other resources besides the > network stack, most notably the independent CPU load and usage > accounting, as well as feedback-driven proportional share scheduling > among virtual images. For more details, check the above URL. > Note that the patch was designed to allow all existing applications and > utilities to run unmodified on the patched kernel, so no recompiling of > the userland is necessary. > Hope you'll find use for the new framework :-) > Cheers, > > Marko > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 01:36:41 2003 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 84CCA37B401 for ; Mon, 26 May 2003 01:36:41 -0700 (PDT) Received: from c17443.thorn1.nsw.optusnet.com.au (c17443.thorn1.nsw.optusnet.com.au [210.49.151.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90E9C43F85 for ; Mon, 26 May 2003 01:36:40 -0700 (PDT) (envelope-from tonymaher@optushome.com.au) Received: from dt.home (localhost [127.0.0.1])h4Q8aho2021522; Mon, 26 May 2003 18:36:43 +1000 (EST) (envelope-from tonym@dt.home) Received: (from tonym@localhost) by dt.home (8.12.9/8.12.9/Submit) id h4Q8abgZ021438; Mon, 26 May 2003 18:36:37 +1000 (EST) (envelope-from tonym) Date: Mon, 26 May 2003 18:36:37 +1000 (EST) From: Tony Maher Message-Id: <200305260836.h4Q8abgZ021438@dt.home> To: A.J.Caines@halplant.com In-Reply-To: <20030526055024.GN383@hal9000.halplant.com> cc: hackers@freebsd.org Subject: Re: Change request for mount_null manpage 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 May 2003 08:36:41 -0000 Hello Andrew, > Andrew J Caines wrote: >> I'm using mount_null now for some months - and i never had a problem >> with this. > Are you using it for rw mounts and if so, then what kind or write volume > and sizes do you handle? > > Usually when this comes up, folks are using null ro mounts and the rare > (and sometime unintentional) rw mounts do little or no writing. If anyone > is doing significant volume or size writes, then I've not heared mention > of it. I also have been using nullfs (since Jun 30 2001) on a number of systems (from 4.3-> 4.8) including my main workstation and multiuser servers. The mounts are rw. FreeBSD dt.home 4.8-STABLE FreeBSD 4.8-STABLE #2: Wed Apr 16 13:00:01 EST 2003 /space/home/staff 4817509 2995755 1436354 68% /home/staff /space/db/mysql 4817509 2995755 1436354 68% /db/mysql /space/db/pgsql 4817509 2995755 1436354 68% /db/pgsql /space/usr/cvs 4817509 2995755 1436354 68% /usr/cvs /space/usr/doc 4817509 2995755 1436354 68% /usr/doc /space/usr/ports 4817509 2995755 1436354 68% /usr/ports /space/usr/src 4817509 2995755 1436354 68% /usr/src /var/obj 1016303 747549 187450 80% /usr/obj /space/usr/local/office52 4817509 2995755 1436354 68% /usr/local/office52 I have built world many times and compiled ports without problem. I have an outstanding PR regarding nullfs http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/28566 I have now removed /usr/hack nullfs mount and retested startx. It all works fine now and I think this PR can now be closed (I'll submit PR followup after some more testing). Also at the time of this PR I stopped using nullfs mounts for /home because linux binaries would not work (no PR for this). I have also retested this and everything works fine. I think the warning in mount_null man page could be toned down. As noted in the '5.1-RELEASE TODO' emails nullfs is somewhat broken in -current. cheers -- tonym From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 01:59:50 2003 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 9E78737B401 for ; Mon, 26 May 2003 01:59:50 -0700 (PDT) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82A7543F75 for ; Mon, 26 May 2003 01:59:49 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.9/8.12.9) with ESMTP id h4Q8xkEB070799; Mon, 26 May 2003 10:59:46 +0200 (CEST) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.9/8.12.9/Submit) id h4Q8xckf070796; Mon, 26 May 2003 10:59:38 +0200 (CEST) Date: Mon, 26 May 2003 10:59:38 +0200 From: Wilko Bulte To: Dirk-Willem van Gulik Message-ID: <20030526085938.GA70751@freebie.xs4all.nl> References: <20030526041513.GP81874@procyon.firepipe.net> <20030526082236.C43487-100000@foem> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030526082236.C43487-100000@foem> User-Agent: Mutt/1.4i X-OS: FreeBSD 4.8-STABLE X-PGP: finger wilko@freebsd.org cc: freebsd-hackers@freebsd.org cc: Will Andrews Subject: Re: Best serial console server construction method? 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 May 2003 08:59:50 -0000 On Mon, May 26, 2003 at 08:24:04AM +0200, Dirk-Willem van Gulik wrote: > > > use a computer that will be used for other purposes and add 8 > > serial ports. How am I going to do that cheaply? Well, N-port > > serial cards (where N is >= 4) cost a few hundred dollars from > > everywhere I could see (granted, they're niche items and are > > accordingly priced). So I came up with the following scheme. > > You may want to check ebay (or its local ilk) for a serial terminal > server. They are usually available there and in the 25-75 dollar range for > a <16 port version. Yup, that should work. Say an old DECserver 700 or so. Works with 'conserver' (in ports) just dandy. We run something like that at work (albeit from Tru64) Wilko -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 02:42:14 2003 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 1DD8337B401 for ; Mon, 26 May 2003 02:42:14 -0700 (PDT) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D9E743F3F for ; Mon, 26 May 2003 02:42:13 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc19i.dialup.mindspring.com ([209.86.5.50] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19KEUU-0004Pg-00; Mon, 26 May 2003 02:42:03 -0700 Message-ID: <3ED1E041.8ABA63A2@mindspring.com> Date: Mon, 26 May 2003 02:37:05 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Tony Maher References: <200305260836.h4Q8abgZ021438@dt.home> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a429612c4ced2c28b1a31d47d0e7ebc6572601a10902912494350badd9bab72f9c350badd9bab72f9c cc: hackers@freebsd.org Subject: Re: Change request for mount_null manpage 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 May 2003 09:42:14 -0000 Tony Maher wrote: > I have an outstanding PR regarding nullfs > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/28566 > > I have now removed /usr/hack nullfs mount and retested startx. > It all works fine now and I think this PR can now be closed (I'll submit > PR followup after some more testing). Also at the time of this PR I stopped > using nullfs mounts for /home because linux binaries would not work (no PR > for this). I have also retested this and everything works fine. This is because of the named pipe that's used for local clients; you can set an environment variable to disable local connections via the named pipe, but be sure to turn TCP back on, or you won't have any transport at all. 8-). Making connections via TCP will also prevent Netscape or Mozilla from eating all your memory for bitmaps, which are not cached on a window basis, so you basically "leak" them until you exit the application and it loses its connection to the X Server, if you use a local connection, which lets it use the shared memory extension. > I think the warning in mount_null man page could be toned down. Probably not a good idea, actually; in general, the reason the warning should stay is that there's still explicit cache coherency issues, when you stack a nullfs on top of an FS, and leave the original FS mount point visible in the namespace. FS stacking broke at the time of the VM and buffer cache unification, and it's only gotten more broken as time went on, unfortunately. The VM changes removed the explicit cache coherency, and replaced it with implicit, losing all the synchronization points that are still needed when you stack vnodes with real vmobject_t's; that those changes were not also made to LFS when they were made to FFS is pretty much why LFS died. -- Terry From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 02:47:19 2003 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 69A5637B401 for ; Mon, 26 May 2003 02:47:19 -0700 (PDT) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id C576943FA3 for ; Mon, 26 May 2003 02:47:18 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc19i.dialup.mindspring.com ([209.86.5.50] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19KEZX-0004je-00; Mon, 26 May 2003 02:47:15 -0700 Message-ID: <3ED1E174.1FF28676@mindspring.com> Date: Mon, 26 May 2003 02:42:12 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Wilko Bulte References: <20030526041513.GP81874@procyon.firepipe.net> <20030526085938.GA70751@freebie.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a429612c4ced2c28b1149638ff68345c3a2601a10902912494350badd9bab72f9c350badd9bab72f9c cc: Will Andrews cc: freebsd-hackers@freebsd.org Subject: Re: Best serial console server construction method? 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 May 2003 09:47:19 -0000 Wilko Bulte wrote: > On Mon, May 26, 2003 at 08:24:04AM +0200, Dirk-Willem van Gulik wrote: > > You may want to check ebay (or its local ilk) for a serial terminal > > server. They are usually available there and in the 25-75 dollar range for > > a <16 port version. > > Yup, that should work. Say an old DECserver 700 or so. Works with > 'conserver' (in ports) just dandy. We run something like that at work > (albeit from Tru64) Be careful buying old DEC Servers, if you don't have a VMS or Tru64 box around; when they boot, they ask for their MOP_MOM. 8-). Basically, their firmware gets downloaded via MOP, and they need something to talk to them to be able to boot (MOP = Maintenance Operations Protocol). Cute little 68K boxes, those DECServers. I actually have some terminal servers that have ROMs in them, but they won't do you any good, now that XNS has been tossed in the Attic (they only talk XNS). -- Terry From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 02:55:23 2003 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 D44B437B401 for ; Mon, 26 May 2003 02:55:23 -0700 (PDT) Received: from mail.distalzou.net (203.141.139.231.user.ad.il24.net [203.141.139.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C4B143F3F for ; Mon, 26 May 2003 02:55:23 -0700 (PDT) (envelope-from devin@spamcop.net) Received: from borosilicate.pun-pun.prv ([192.168.7.29]) by mail.distalzou.net with esmtp (TLSv1:AES256-SHA:256) (Exim 4.20) id 19KEhF-000Cvv-Qj; Mon, 26 May 2003 18:55:13 +0900 Date: Mon, 26 May 2003 18:55:13 +0900 (JST) From: Tod McQuillin X-X-Sender: devin@borosilicate.pun-pun.prv To: Terry Lambert In-Reply-To: <3ED1E174.1FF28676@mindspring.com> Message-ID: <20030526185421.G48601@borosilicate.pun-pun.prv> References: <20030526041513.GP81874@procyon.firepipe.net> <20030526085938.GA70751@freebie.xs4all.nl> <3ED1E174.1FF28676@mindspring.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Will Andrews Subject: Re: Best serial console server construction method? 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 May 2003 09:55:24 -0000 On Mon, 26 May 2003, Terry Lambert wrote: > Be careful buying old DEC Servers, if you don't have a VMS > or Tru64 box around; when they boot, they ask for their > MOP_MOM. 8-). Basically, their firmware gets downloaded > via MOP, and they need something to talk to them to be able > to boot (MOP = Maintenance Operations Protocol). See /usr/ports/net/mopd. I haven't used it but it seems to serve exactly the purpose you describe. -- Tod McQuillin From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 03:00:09 2003 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 14AE337B401 for ; Mon, 26 May 2003 03:00:09 -0700 (PDT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1031C43F3F for ; Mon, 26 May 2003 03:00:08 -0700 (PDT) (envelope-from dean@dragon.stack.nl) Received: by mailhost.stack.nl (Postfix, from userid 65534) id A59911F109; Mon, 26 May 2003 12:00:06 +0200 (CEST) Received: from dragon.stack.nl (dragon.stack.nl [2001:610:1108:5011:207:e9ff:fe09:230]) by mailhost.stack.nl (Postfix) with ESMTP id 96C721F106; Mon, 26 May 2003 12:00:01 +0200 (CEST) Received: by dragon.stack.nl (Postfix, from userid 1600) id 714425F176; Mon, 26 May 2003 12:00:01 +0200 (CEST) Date: Mon, 26 May 2003 12:00:01 +0200 From: Dean Strik To: Terry Lambert Message-ID: <20030526100001.GB19105@dragon.stack.nl> References: <20030526041513.GP81874@procyon.firepipe.net> <20030526085938.GA70751@freebie.xs4all.nl> <3ED1E174.1FF28676@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3ED1E174.1FF28676@mindspring.com> X-Editor: VIM Rulez! http://www.vim.org/ X-MUD: Outerspace - telnet://mud.stack.nl:3333 X-Really: Yes User-Agent: Mutt/1.5.4i X-Spam-Status: No, hits=-29.3 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT_MUTT version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: freebsd-hackers@freebsd.org cc: Will Andrews Subject: Re: Best serial console server construction method? 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 May 2003 10:00:09 -0000 Terry Lambert wrote: > Be careful buying old DEC Servers, if you don't have a VMS > or Tru64 box around; when they boot, they ask for their > MOP_MOM. 8-). Basically, their firmware gets downloaded > via MOP, and they need something to talk to them to be able > to boot (MOP = Maintenance Operations Protocol). There are DECserver 700s that boot using BOOTP, fortunately. Of course, one still needs the WWENG2 file... -- Dean C. Strik Eindhoven University of Technology dean@stack.nl | dean@ipnet6.org | http://www.ipnet6.org/ "This isn't right. This isn't even wrong." -- Wolfgang Pauli From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 03:12:29 2003 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 6AAFD37B401 for ; Mon, 26 May 2003 03:12:29 -0700 (PDT) Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B3DE43FCB for ; Mon, 26 May 2003 03:12:19 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from foem (IDENT:chuckwebweaving.org@foem [10.11.0.2]) h4QAC8v7062120; Mon, 26 May 2003 12:12:08 +0200 (CEST) (envelope-from dirkx@webweaving.org) Date: Mon, 26 May 2003 12:12:08 +0200 (CEST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@foem To: Terry Lambert In-Reply-To: <3ED1E174.1FF28676@mindspring.com> Message-ID: <20030526121129.J43487-100000@foem> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Will Andrews Subject: Re: Best serial console server construction method? 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 May 2003 10:12:29 -0000 > Be careful buying old DEC Servers, if you don't have a VMS > or Tru64 box around; when they boot, they ask for their > MOP_MOM. 8-). Basically, their firmware gets downloaded > via MOP, and they need something to talk to them to be able > to boot (MOP = Maintenance Operations Protocol). Some annex-es do the same; but they use bootp/tftp - so as long as you can get your mittens on the boot.bin code to put in your tftp directory you are fine. Dw From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 04:38:55 2003 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 9A13737B401 for ; Mon, 26 May 2003 04:38:55 -0700 (PDT) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65D0643F3F for ; Mon, 26 May 2003 04:38:54 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.9/8.12.9) with ESMTP id h4QBcpEB071319; Mon, 26 May 2003 13:38:51 +0200 (CEST) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.9/8.12.9/Submit) id h4QBccHL071318; Mon, 26 May 2003 13:38:38 +0200 (CEST) Date: Mon, 26 May 2003 13:38:38 +0200 From: Wilko Bulte To: Terry Lambert Message-ID: <20030526113838.GA71297@freebie.xs4all.nl> References: <20030526041513.GP81874@procyon.firepipe.net> <20030526082236.C43487-100000@foem> <20030526085938.GA70751@freebie.xs4all.nl> <3ED1E174.1FF28676@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <3ED1E174.1FF28676@mindspring.com> User-Agent: Mutt/1.4i X-OS: FreeBSD 4.8-STABLE X-PGP: finger wilko@freebsd.org cc: Will Andrews cc: freebsd-hackers@freebsd.org Subject: Re: Best serial console server construction method? 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 May 2003 11:38:55 -0000 On Mon, May 26, 2003 at 02:42:12AM -0700, Terry Lambert wrote: > Wilko Bulte wrote: > > On Mon, May 26, 2003 at 08:24:04AM +0200, Dirk-Willem van Gulik wrote: > > > You may want to check ebay (or its local ilk) for a serial terminal > > > server. They are usually available there and in the 25-75 dollar rang= e for > > > a <16 port version. > >=20 > > Yup, that should work. Say an old DECserver 700 or so. Works with > > 'conserver' (in ports) just dandy. We run something like that at work > > (albeit from Tru64) >=20 > Be careful buying old DEC Servers, if you don't have a VMS > or Tru64 box around; when they boot, they ask for their > MOP_MOM. 8-). Basically, their firmware gets downloaded > via MOP, and they need something to talk to them to be able No they don'=00 (have to). Just install a PCMCIA sized flashcard with firmware and they will never bother you again. TCP/IP is all you need to talk to them from there on. --=20 | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte =09 From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 04:39:45 2003 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 C09C737B401 for ; Mon, 26 May 2003 04:39:45 -0700 (PDT) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1976343FBD for ; Mon, 26 May 2003 04:39:44 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.9/8.12.9) with ESMTP id h4QBdfEB071338; Mon, 26 May 2003 13:39:41 +0200 (CEST) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.9/8.12.9/Submit) id h4QBdfKx071337; Mon, 26 May 2003 13:39:41 +0200 (CEST) Date: Mon, 26 May 2003 13:39:41 +0200 From: Wilko Bulte To: Dean Strik Message-ID: <20030526113941.GB71297@freebie.xs4all.nl> References: <20030526041513.GP81874@procyon.firepipe.net> <20030526085938.GA70751@freebie.xs4all.nl> <3ED1E174.1FF28676@mindspring.com> <20030526100001.GB19105@dragon.stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030526100001.GB19105@dragon.stack.nl> User-Agent: Mutt/1.4i X-OS: FreeBSD 4.8-STABLE X-PGP: finger wilko@freebsd.org cc: freebsd-hackers@freebsd.org cc: Will Andrews Subject: Re: Best serial console server construction method? 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 May 2003 11:39:46 -0000 On Mon, May 26, 2003 at 12:00:01PM +0200, Dean Strik wrote: > Terry Lambert wrote: > > Be careful buying old DEC Servers, if you don't have a VMS > > or Tru64 box around; when they boot, they ask for their > > MOP_MOM. 8-). Basically, their firmware gets downloaded > > via MOP, and they need something to talk to them to be able > > to boot (MOP = Maintenance Operations Protocol). > > There are DECserver 700s that boot using BOOTP, fortunately. > Of course, one still needs the WWENG2 file... Yes. Or a 2MB flash card with that image. Flashcards you can steal from a scrapped HSZ/HSG array controller.. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 05:25:04 2003 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 33C0937B401 for ; Mon, 26 May 2003 05:25:04 -0700 (PDT) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A88043FB1 for ; Mon, 26 May 2003 05:25:03 -0700 (PDT) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id DB8AD530E; Mon, 26 May 2003 14:25:00 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Will Andrews References: <20030526041513.GP81874@procyon.firepipe.net> From: Dag-Erling Smorgrav Date: Mon, 26 May 2003 14:24:59 +0200 In-Reply-To: <20030526041513.GP81874@procyon.firepipe.net> (Will Andrews's message of "Sun, 25 May 2003 21:15:13 -0700") Message-ID: User-Agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-hackers@freebsd.org Subject: Re: Best serial console server construction method? 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 May 2003 12:25:04 -0000 Will Andrews writes: > In my quest to make my little network of computers more useful for > kernel hacking and testing, I'm attempting to build a very cheap > serial console server. Just get an old Portmaster on eBay... DES -- Dag-Erling Smorgrav - des@ofug.org From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 06:20:46 2003 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 0A61337B401; Mon, 26 May 2003 06:20:46 -0700 (PDT) Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 525EC43F75; Mon, 26 May 2003 06:20:44 -0700 (PDT) (envelope-from andymac@bullseye.apana.org.au) Received: from bullseye.apana.org.au (dialup-1.acis.com.au [203.14.230.80] (may be forged)) by posgate.acis.com.au (8.12.7/8.12.7) with ESMTP id h4QDKVGk010666; Mon, 26 May 2003 23:20:33 +1000 Received: from bullseye.apana.org.au (localhost.apana.org.au [127.0.0.1]) h4QBH019058728; Mon, 26 May 2003 21:17:00 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Received: from localhost (andymac@localhost)h4QBH0B5058725; Mon, 26 May 2003 21:17:00 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Date: Mon, 26 May 2003 21:17:00 +1000 (EST) From: Andrew MacIntyre To: Daniel Eischen In-Reply-To: Message-ID: <20030526204036.D58689@bullseye.apana.org.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang) cc: freebsd-hackers@freebsd.org cc: alane@freebsd.org Subject: Re: setting stacksize in "initial" thread (pthreads, 4.8R) 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 May 2003 13:20:46 -0000 On Sun, 25 May 2003, Daniel Eischen wrote: > On Mon, 26 May 2003, Andrew MacIntyre wrote: > > > The problem actually occurs with recursive matches in Python's regex > > engine. Python has a hardcoded regex recursion limit, which has trapped > > ballistic matches before running out of the default stack. However a > > couple of recent fixes to the regex engine have increased stack > > consumption, and the hard limit has to be lowered. > > How do you know it is the main thread stack and not a different > thread stack that is getting exceeded? By default, threads > other than main get a 64K stack, and this is totally configurable > by the application. Activating threads in Python requires importing either of the threads support modules (theres a high level module & a low level module). The regex regression test doesn't import either threads module. Neither module supports setting the thread stack size from Python code. Python by default uses the system's default thread stack size, but this can be overridden at compile time. I've tried bumping the thread stack size up from the default to 1MB with no effect. Also, the recursive routine takes 3 arguments (2 pointers + 1 int, ie 12 bytes), and has at least 36 bytes worth of local variables. Failing with ~8100 levels of recursion means a minimum of ~380kB of stack consumption, not including overhead (frame pointer, registers pushed to the stack, etc), ie lots more than the default thread stack size. The routine in question can easily support a stack exhaustion check on each iteration, rather than relying on hard coded limits. Its just a matter of knowing how to do the check, and how expensive it is. Even moderately expensive could be more attactive than tempting bus errors. Regards, Andrew. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac@pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 06:36:02 2003 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 9B91037B401 for ; Mon, 26 May 2003 06:36:02 -0700 (PDT) Received: from smtp-out.comcast.net (smtp-out.comcast.net [24.153.64.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E96543F75 for ; Mon, 26 May 2003 06:36:02 -0700 (PDT) (envelope-from sjr@comcast.net) Received: from pcp325887pcs.catonv01.md.comcast.net (pcp01207798pcs.nrockv01.md.comcast.net [68.48.15.65]) by mtaout01.icomcast.net (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003)) with ESMTP id <0HFH00MXTXRSQO@mtaout01.icomcast.net> for freebsd-hackers@freebsd.org; Mon, 26 May 2003 09:35:53 -0400 (EDT) Received: from istari.comcast.net (localhost [127.0.0.1]) by pcp325887pcs.catonv01.md.comcast.net (8.12.9/8.12.9) with ESMTP id h4QDZiqe054675 for ; Mon, 26 May 2003 09:35:51 -0400 Date: Mon, 26 May 2003 09:35:44 -0400 (EDT) From: "Stephen J. Roznowski" To: freebsd-hackers@freebsd.org Message-id: <200305261335.h4QDZiqe054675@pcp325887pcs.catonv01.md.comcast.net> MIME-version: 1.0 Content-type: TEXT/plain; charset=us-ascii Content-transfer-encoding: 7BIT Subject: _POSIX_C_SOURCE 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: Mon, 26 May 2003 13:36:03 -0000 When compiling XFree86-4-libraries, I get the following warning: /usr/include/sys/cdefs.h:273: warning: `_POSIX_C_SOURCE' is not defined /usr/include/sys/cdefs.h:279: warning: `_POSIX_C_SOURCE' is not defined Should this section of cdefs.h be wrapped with a #ifdef _POSIX_C_SOURCE #endif section? Thanks, -- Stephen J. Roznowski (sjr@comcast.net) From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 07:21:08 2003 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 B618437B404 for ; Mon, 26 May 2003 07:21:08 -0700 (PDT) Received: from symonds.net (ca1.symonds.net [66.92.42.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 440A243FB1 for ; Mon, 26 May 2003 07:21:08 -0700 (PDT) (envelope-from ashish@symonds.net) Received: from localhost (symonds.net) [127.0.0.1] by symonds.net with smtp (Exim 3.35 #1 (Debian)) id 19KIqW-00020H-00; Mon, 26 May 2003 07:21:04 -0700 Received: from 203.192.199.30 (SquirrelMail authenticated user ashish) by secure.symonds.net with HTTP; Mon, 26 May 2003 19:51:04 +0530 (IST) Message-ID: <1116.203.192.199.30.1053958864.squirrel@secure.symonds.net> Date: Mon, 26 May 2003 19:51:04 +0530 (IST) From: "Ashish Kulkarni" To: Importance: Normal MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: changing the ToS in IP Header X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ashish@symonds.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2003 14:21:09 -0000 Hello, Is there any way in which I can manipulate the Type of Service (TOS) byte in the IPv4 header? I need to set the TOS bits on all outgoing packets from my box to the ISP to a particular pattern (0x02), as otherwise the ISP does not forward packets. I have been able to do this in Linux using the iptables mangle table: http://www.tldp.org/LDP/nag2/x-087-2-firewall.tos.manipulation.html but am unable to find a similiar packet-mangling feature in the firewalls running on FreeBSD...there are rules for matching on TOS pattern, but not on TOS manipulation. Does anyone know of any tool which can do this? As an alternative solution, is there any way to set the default TOS via a sysctl interface (similiar to that of TTL, namely net.inet.ip.ttl)? I'm planning to use this on my home box, so I have no problems in trying to patch and rebuild the kernel if I can get some feedback and/or tips on how to do so :-) Thanks, Ashish. ps: can you please CC any replies to me? thanks... From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 08:48:39 2003 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 1B5ED37B401 for ; Mon, 26 May 2003 08:48:39 -0700 (PDT) Received: from ruminary.org (chiku.ruminary.org [216.218.185.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id B54A943F3F for ; Mon, 26 May 2003 08:48:38 -0700 (PDT) (envelope-from clark@ruminary.org) Received: by ruminary.org (Postfix, from userid 1000) id 4A91C22E1A; Mon, 26 May 2003 08:48:38 -0700 (PDT) Date: Mon, 26 May 2003 08:48:38 -0700 From: clark shishido To: Will Andrews Message-ID: <20030526154838.GA41638@ruminary.org> References: <20030526041513.GP81874@procyon.firepipe.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030526041513.GP81874@procyon.firepipe.net> User-Agent: Mutt/1.4.1i cc: freebsd-hackers@freebsd.org Subject: Re: Best serial console server construction method? 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 May 2003 15:48:39 -0000 On Sun, May 25, 2003 at 09:15:13PM -0700, Will Andrews wrote: > Average per port: $12.50 If cost is a concern and you need less than 8 ports, I'd just daisy chain the serial ports with null modem cables. It's easy, simple, and cheap. Of course this assumes you have two serial ports on each machine and the "parent" machine is up. Then run conserver and a master conserver for a virtual console server. --clark From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 09:05:47 2003 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 A8C2537B401 for ; Mon, 26 May 2003 09:05:47 -0700 (PDT) Received: from mclean.mail.mindspring.net (mclean.mail.mindspring.net [207.69.200.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A3D843F75 for ; Mon, 26 May 2003 09:05:47 -0700 (PDT) (envelope-from jtoung@mindspring.com) Received: from h-68-164-29-16.snvacaid.covad.net ([68.164.29.16] helo=there) by mclean.mail.mindspring.net with esmtp (Exim 3.33 #1) id 19KKTo-0005XT-00; Mon, 26 May 2003 12:05:44 -0400 Content-Type: text/plain; charset="iso-8859-1" From: Jerry Toung To: ashish@symonds.net, Date: Mon, 26 May 2003 09:06:03 -0700 User-Agent: KMail/1.4.3 References: <1116.203.192.199.30.1053958864.squirrel@secure.symonds.net> In-Reply-To: <1116.203.192.199.30.1053958864.squirrel@secure.symonds.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200305260906.04023.jtoung@mindspring.com> Subject: Re: changing the ToS in IP Header 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 May 2003 16:05:48 -0000 Ashish, you can set the TOS bit when you create the socket in your program. int fd, tos; fd =3D socket(PF_INET, SOCK_DGRAM, 0) tos=3D3; setsockopt(fd,IPPROTO_IP,3, &tos, sizeof(tos)) On Monday 26 May 2003 07:21 am, Ashish Kulkarni wrote: > Hello, > > > Is there any way in which I can manipulate the Type of Service (TOS) by= te > in the IPv4 header? I need to set the TOS bits on all outgoing packets = from > my box to the ISP to a particular pattern (0x02), as otherwise the ISP = does > not forward packets. I have been able to do this in Linux using the > iptables mangle table: > > > http://www.tldp.org/LDP/nag2/x-087-2-firewall.tos.manipulation.html > > > but am unable to find a similiar packet-mangling feature in the firewal= ls > running on FreeBSD...there are rules for matching on TOS pattern, but n= ot > on TOS manipulation. Does anyone know of any tool which can do this? > > > As an alternative solution, is there any way to set the default TOS via= a > sysctl interface (similiar to that of TTL, namely net.inet.ip.ttl)? I'= m > planning to use this on my home box, so I have no problems in trying to > patch and rebuild the kernel if I can get some feedback and/or tips on = how > to do so :-) > > > Thanks, > Ashish. > > > ps: can you please CC any replies to me? thanks... > > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 09:45:11 2003 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 DF9B837B401; Mon, 26 May 2003 09:45:11 -0700 (PDT) Received: from premijer.tel.fer.hr (premijer.tel.fer.hr [161.53.19.221]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1249143F93; Mon, 26 May 2003 09:45:11 -0700 (PDT) (envelope-from zec@tel.fer.hr) Received: from tel.fer.hr (unknown [161.53.243.135]) by premijer.tel.fer.hr (Postfix) with ESMTP id 802151404; Mon, 26 May 2003 18:44:50 +0200 (MET DST) Message-ID: <3ED2448D.88E08DBB@tel.fer.hr> Date: Mon, 26 May 2003 18:45:01 +0200 From: Marko Zec X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Vincent Jardin References: <3ED14BF3.139CAC32@tel.fer.hr> <200305260857.26994.vjardin@wanadoo.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: riccardo.scandariato@polito.it cc: net@freebsd.org Subject: Re: Network stack cloning / virtualization patches 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 May 2003 16:45:12 -0000 Vincent Jardin wrote: > Since the last EuroBSD 2002 conference, there are 2 architectures to support > VPNs with FreeBSD : your patch and the Riccardo Scandariato one > (http://softeng.polito.it/freebsd/) that is very good too. > > From a VPN point of view, how could both projects be compared ? > Do you think that both projects could be merged or are there too much > differences between your two projects ? Riccardo's VPN patches were designed specifically for supporting VPNs by basically virtualizing only the IP routing tables. The network stack cloning model is more generic, as it doesn't stop at the virtualization of the routing tables, but rather also provides multiple independent network interface lists, inbound queues, hash & PCB tables, IPFW rulesets, sysctl tunables, traffic counters / statistics etc. But the basic implementation idea and the motivation is quite similar for both frameworks, and they can both support IP-tunnel based overlay VPNs with overlapping addresing spaces. >From the userland API perspective the two approaches are slightly different. Riccardo's patches extended the socket API, so that the applications which require to operate on virtualized routing tables have also to be modified and recompiled. My model provides a single management utility which can be used to spawn new processes bound to a specific network stack instance. Once the processes are assigned to a network stack, all existing userland applications and utilities can operate on that stack without any modifications. Although the described two approaches might seem to follow fundamentally different ideas, IMO both frameworks could be easily modified to adopt the userland API convention of the other, if necessary. Marko From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 09:54:12 2003 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 520C437B401; Mon, 26 May 2003 09:54:12 -0700 (PDT) Received: from premijer.tel.fer.hr (premijer.tel.fer.hr [161.53.19.221]) by mx1.FreeBSD.org (Postfix) with ESMTP id A552A43F85; Mon, 26 May 2003 09:54:11 -0700 (PDT) (envelope-from zec@tel.fer.hr) Received: from tel.fer.hr (unknown [161.53.243.135]) by premijer.tel.fer.hr (Postfix) with ESMTP id BA3E813C4; Mon, 26 May 2003 18:53:51 +0200 (MET DST) Message-ID: <3ED246AC.483FE6F4@tel.fer.hr> Date: Mon, 26 May 2003 18:54:04 +0200 From: Marko Zec X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Jordan K Hubbard References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: net@freebsd.org Subject: Re: Network stack cloning / virtualization patches 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 May 2003 16:54:12 -0000 Jordan K Hubbard wrote: > On Sunday, May 25, 2003, at 05:18 PM, Marko Zec wrote: > > > So, I'd certainly like to virtualize more system resources and make > > virtual images as independent from each other as possible, but they > > will always > > have to share the same kernel. > > That's actually what I was talking about - my comparison to what IBM's > done may have been a bad example since, as you say, they've virtualized > the hardware in true IBM (shades of VM) fashion. I think that's > actually overkill for many usage scenarios since all you really want is > the ability to run an "instance" of the OS which allows for all the > user-visible configuration knobs to be changed and the appropriate > user-visible resource limits to be enforced independently. Essentially > a jail where it's literally impossible to tell that you're not the only > "OS" on the machine or to affect a user or resource running on another > instance. Btw. there is a commercial product out there that also seems to offer such a functionality, check http://www.sw-soft.com/en/products/virtuozzo/ Marko From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 11:13:31 2003 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 D3C1F37B401 for ; Mon, 26 May 2003 11:13:31 -0700 (PDT) Received: from saga17.Stanford.EDU (saga17.Stanford.EDU [171.64.15.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B5F643F93 for ; Mon, 26 May 2003 11:13:31 -0700 (PDT) (envelope-from tedu@stanford.edu) Received: from localhost (tedu@localhost) by saga17.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h4QIDRQj001318; Mon, 26 May 2003 11:13:27 -0700 (PDT) X-Authentication-Warning: saga17.Stanford.EDU: tedu owned process doing -bs Date: Mon, 26 May 2003 11:13:27 -0700 (PDT) From: Ted Unangst To: Terry Lambert In-Reply-To: <3ED1E041.8ABA63A2@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hackers@freebsd.org Subject: Re: Change request for mount_null manpage 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 May 2003 18:13:32 -0000 On Mon, 26 May 2003, Terry Lambert wrote: > Making connections via TCP will also prevent Netscape or > Mozilla from eating all your memory for bitmaps, which are > not cached on a window basis, so you basically "leak" them > until you exit the application and it loses its connection > to the X Server, if you use a local connection, which lets > it use the shared memory extension. off topic, but this caught my eye. can you clarify what you mean? maybe using two sentences? :) -- "People blame me because these water mains break, but I ask you, if the water mains didn't break, would it be my responsibility to fix them then? WOULD IT!?!" - M. Barry, Mayor of Washington, DC From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 12:20:48 2003 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 33FBA37B401 for ; Mon, 26 May 2003 12:20:48 -0700 (PDT) Received: from symonds.net (ca1.symonds.net [66.92.42.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF73D43F85 for ; Mon, 26 May 2003 12:20:47 -0700 (PDT) (envelope-from ashish@symonds.net) Received: from localhost (symonds.net) [127.0.0.1] by symonds.net with smtp (Exim 3.35 #1 (Debian)) id 19KNWY-0004wB-00; Mon, 26 May 2003 12:20:46 -0700 Received: from 203.192.199.30 (SquirrelMail authenticated user ashish) by secure.symonds.net with HTTP; Tue, 27 May 2003 00:50:46 +0530 (IST) Message-ID: <1231.203.192.199.30.1053976846.squirrel@secure.symonds.net> Date: Tue, 27 May 2003 00:50:46 +0530 (IST) From: "Ashish Kulkarni" To: Importance: Normal MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: ashish@symonds.net Subject: Re: changing the ToS in IP Header X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ashish@symonds.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2003 19:20:48 -0000 as I mentioned earlier, I want to do it for all outgoing packets on an interface, not on per socket basis. I actually was hoping that somene would provide me pointers to where I should look in the source (me being a newcomer to BSD as such) to implement a sysctl that will allow me to change the tos, eg. "net.inet.ip.tos". I'd have prefered to use a packet mangling firewall, but afaik there are none which do that so I'll have to do it the hard way ;-) Thanks, Ashish ----- Original Message ----- From: "Jerry Toung" To: ; Sent: Monday, May 26, 2003 9:36 PM Subject: Re: changing the ToS in IP Header Ashish, you can set the TOS bit when you create the socket in your program. int fd, tos; fd = socket(PF_INET, SOCK_DGRAM, 0) tos=3; setsockopt(fd,IPPROTO_IP,3, &tos, sizeof(tos)) On Monday 26 May 2003 07:21 am, Ashish Kulkarni wrote: > Hello, > > > Is there any way in which I can manipulate the Type of Service (TOS) byte > in the IPv4 header? I need to set the TOS bits on all outgoing packets from > my box to the ISP to a particular pattern (0x02), as otherwise the ISP does > not forward packets. I have been able to do this in Linux using the > iptables mangle table: > > > http://www.tldp.org/LDP/nag2/x-087-2-firewall.tos.manipulation.html > > > but am unable to find a similiar packet-mangling feature in the firewalls > running on FreeBSD...there are rules for matching on TOS pattern, but not > on TOS manipulation. Does anyone know of any tool which can do this? > > > As an alternative solution, is there any way to set the default TOS via a > sysctl interface (similiar to that of TTL, namely net.inet.ip.ttl)? I'm > planning to use this on my home box, so I have no problems in trying to > patch and rebuild the kernel if I can get some feedback and/or tips on how > to do so :-) > > > Thanks, > Ashish. > > > ps: can you please CC any replies to me? thanks... >- From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 17:26:23 2003 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 8621A37B401 for ; Mon, 26 May 2003 17:26:23 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04FFA43F93 for ; Mon, 26 May 2003 17:26:23 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from dialup-67.30.96.194.dial1.sanjose1.level3.net ([67.30.96.194] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19KSIF-0003hK-00; Mon, 26 May 2003 17:26:20 -0700 Message-ID: <3ED2B05B.2D253DD3@mindspring.com> Date: Mon, 26 May 2003 17:24:59 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ted Unangst References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a430bda539ffca92863f113ffb034e7800548b785378294e88350badd9bab72f9c350badd9bab72f9c cc: hackers@freebsd.org Subject: Re: Change request for mount_null manpage 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 May 2003 00:26:23 -0000 Ted Unangst wrote: > On Mon, 26 May 2003, Terry Lambert wrote: > > Making connections via TCP will also prevent Netscape or > > Mozilla from eating all your memory for bitmaps, which are > > not cached on a window basis, so you basically "leak" them > > until you exit the application and it loses its connection > > to the X Server, if you use a local connection, which lets > > it use the shared memory extension. > > off topic, but this caught my eye. can you clarify what you mean? maybe > using two sentences? :) The shared memory extension is used to communicate bitmaps to the X server quickly. When Netscape does this, the bitmap is reference counted. If you are using the shared memory extension, the reference doesn't go away until the application beaks its connection to the X server. The browser case is the degenerate case of this, since it maintains its connection for pretty much forever. One fix for this is to close and open an X server connection per window, so the X server can do resource tracking on a window/connection basis, rather than doing it on an application/connection basis. Another is to quit and restart the program. A final one is to make it avoid using the shared memory extension at all by telling it the connection isn't local. -- Terry From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 18:12:13 2003 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 5818137B401 for ; Mon, 26 May 2003 18:12:13 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id B752643F75 for ; Mon, 26 May 2003 18:12:12 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from dialup-67.30.96.194.dial1.sanjose1.level3.net ([67.30.96.194] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19KT0b-0003MT-00; Mon, 26 May 2003 18:12:10 -0700 Message-ID: <3ED2BAF5.2B6EC508@mindspring.com> Date: Mon, 26 May 2003 18:10:13 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: ashish@symonds.net References: <1231.203.192.199.30.1053976846.squirrel@secure.symonds.net> Content-Type: multipart/mixed; boundary="------------CD4EAD0DFBF412668992335C" X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a49db6559609bc3f7572dd0e0a2da75257548b785378294e88350badd9bab72f9c350badd9bab72f9c cc: freebsd-hackers@freebsd.org Subject: [PATCH] Re: changing the ToS in IP Header 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 May 2003 01:12:13 -0000 This is a multi-part message in MIME format. --------------CD4EAD0DFBF412668992335C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Ashish Kulkarni wrote: > as I mentioned earlier, I want to do it for all outgoing packets on an > interface, not on per socket basis. I actually was hoping that somene > would provide me pointers to where I should look in the source (me being a > newcomer to BSD as such) to implement a sysctl that will allow me to > change the tos, eg. "net.inet.ip.tos". I'd have prefered to use a packet > mangling firewall, but afaik there are none which do that so I'll have to > do it the hard way ;-) The attached patch adds a new sysctl oid for support of a "net.inet.ip.default_tos" (default: 0). I sent it as a context diff, in case the kernel has changed more than a little since the last time I updated. Note: I only compile-tested this. -- Terry --------------CD4EAD0DFBF412668992335C Content-Type: text/plain; charset=us-ascii; name="iptos.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="iptos.diff" Index: in_pcb.c =================================================================== RCS file: /cvs/src/sys/netinet/in_pcb.c,v retrieving revision 1.120 diff -c -r1.120 in_pcb.c *** in_pcb.c 21 Feb 2003 05:28:27 -0000 1.120 --- in_pcb.c 26 May 2003 20:56:30 -0000 *************** *** 31,37 **** * SUCH DAMAGE. * * @(#)in_pcb.c 8.4 (Berkeley) 5/24/95 ! * $FreeBSD: src/sys/netinet/in_pcb.c,v 1.120 2003/02/21 05:28:27 cjc Exp $ */ #include "opt_ipsec.h" --- 31,37 ---- * SUCH DAMAGE. * * @(#)in_pcb.c 8.4 (Berkeley) 5/24/95 ! * $FreeBSD$ */ #include "opt_ipsec.h" *************** *** 104,109 **** --- 104,114 ---- int ipport_reservedhigh = IPPORT_RESERVED - 1; /* 1023 */ int ipport_reservedlow = 0; + /* + * Default type of service for all IP packets. + */ + int ip_default_tos = 0; + #define RANGECHK(var, min, max) \ if ((var) < (min)) { (var) = (min); } \ else if ((var) > (max)) { (var) = (max); } *************** *** 124,129 **** --- 129,145 ---- return error; } + static int + sysctl_net_iptos_check(SYSCTL_HANDLER_ARGS) + { + int error = sysctl_handle_int(oidp, + oidp->oid_arg1, oidp->oid_arg2, req); + if (!error) { + RANGECHK(ip_default_tos, 0, 255); + } + return error; + } + #undef RANGECHK SYSCTL_NODE(_net_inet_ip, IPPROTO_IP, portrange, CTLFLAG_RW, 0, "IP Ports"); *************** *** 144,149 **** --- 160,167 ---- CTLFLAG_RW|CTLFLAG_SECURE, &ipport_reservedhigh, 0, ""); SYSCTL_INT(_net_inet_ip_portrange, OID_AUTO, reservedlow, CTLFLAG_RW|CTLFLAG_SECURE, &ipport_reservedlow, 0, ""); + SYSCTL_PROC(_net_inet_ip, OID_AUTO, default_tos, CTLTYPE_INT|CTLFLAG_RW, + &ip_default_tos, 0, &sysctl_net_iptos_check, "I", ""); /* * in_pcb.c: manage the Protocol Control Blocks. *************** *** 174,179 **** --- 192,198 ---- inp->inp_gencnt = ++pcbinfo->ipi_gencnt; inp->inp_pcbinfo = pcbinfo; inp->inp_socket = so; + inp->inp_ip_tos = (u_char)ip_default_tos; #ifdef IPSEC error = ipsec_init_policy(so, &inp->inp_sp); if (error != 0) { --------------CD4EAD0DFBF412668992335C-- From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 20:13:40 2003 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 AC3CE37B401 for ; Mon, 26 May 2003 20:13:40 -0700 (PDT) Received: from linus.csl.sony.co.jp (linus.csl.sony.co.jp [133.138.1.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91E7D43F93 for ; Mon, 26 May 2003 20:13:39 -0700 (PDT) (envelope-from kjc@csl.sony.co.jp) Received: from localhost (localhost [127.0.0.1]) by linus.csl.sony.co.jp (8.12.9/8.12.6) with ESMTP id h4R3Daxj015174; Tue, 27 May 2003 12:13:36 +0900 (JST) (envelope-from kjc@csl.sony.co.jp) Date: Tue, 27 May 2003 12:13:36 +0900 (JST) Message-Id: <20030527.121336.41645344.kjc@csl.sony.co.jp> To: ashish@symonds.net From: Kenjiro Cho In-Reply-To: <1116.203.192.199.30.1053958864.squirrel@secure.symonds.net> References: <1116.203.192.199.30.1053958864.squirrel@secure.symonds.net> X-Mailer: Mew version 2.2 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: changing the ToS in IP Header 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 May 2003 03:13:41 -0000 Ashish Kulkarni wrote: > Is there any way in which I can manipulate the Type of Service (TOS) byte > in the IPv4 header? I need to set the TOS bits on all outgoing packets from > my box to the ISP to a particular pattern (0x02), as otherwise the ISP does > not forward packets. Tell your ISP not to use 0x02; it violates the standard. You may modify the upper 6 bits for an arbitrary value, though. The lower 2 bits of the (now deprecated) TOS field are officially assigned to ECN (RFC3168). 0x02, ECT(0), is used to indicate that the sender is ECN-capable. > I have been able to do this in Linux using the > iptables mangle table: > > http://www.tldp.org/LDP/nag2/x-087-2-firewall.tos.manipulation.html > > but am unable to find a similiar packet-mangling feature in the firewalls > running on FreeBSD...there are rules for matching on TOS pattern, but not > on TOS manipulation. Does anyone know of any tool which can do this? ALTQ supports diffserv and is capable of rewriting the upper 6 bits of the TOS field. http://www.csl.sony.co.jp/~kjc/software.html -Kenjiro From owner-freebsd-hackers@FreeBSD.ORG Mon May 26 23:51:51 2003 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 2D54937B401 for ; Mon, 26 May 2003 23:51:51 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-104-32.dsl.lsan03.pacbell.net [64.169.104.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A08143FD7 for ; Mon, 26 May 2003 23:51:50 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 02AE866B9B for ; Mon, 26 May 2003 23:51:50 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id DFBB6AEA; Mon, 26 May 2003 23:51:49 -0700 (PDT) Date: Mon, 26 May 2003 23:51:49 -0700 From: Kris Kennaway To: hackers@FreeBSD.org Message-ID: <20030527065149.GA84791@rot13.obsecurity.org> References: <20030525145542.GA97711@LF.net> <20030526055024.GN383@hal9000.halplant.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <20030526055024.GN383@hal9000.halplant.com> User-Agent: Mutt/1.4.1i Subject: Re: Change request for mount_null manpage 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 May 2003 06:51:51 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 26, 2003 at 01:50:24AM -0400, Andrew J Caines wrote: > Marc, >=20 > > I'm using mount_null now for some months - and i never had a problem wi= th this. >=20 > Are you using it for rw mounts and if so, then what kind or write volume > and sizes do you handle? >=20 > Usually when this comes up, folks are using null ro mounts and the rare > (and sometime unintentional) rw mounts do little or no writing. If anyone > is doing significant volume or size writes, then I've not heared mention > of it. nullfs may well work for some r/o workloads, but it is definitely broken for rw mounts. If anyone is seriously interested in fixing it, I can describe the usage pattern that causes a reliable deadlock on my machine (I've reported it before). Kris --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+0wsFWry0BWjoQKURAqJGAJ48BIm7FIXqfFikgVwIsWskAzq4VgCgyIt9 NksDSSsm9++snMF0ma/13n0= =QFIr -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 01:57:08 2003 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 A9A4937B401 for ; Tue, 27 May 2003 01:57:08 -0700 (PDT) Received: from herring.nlsystems.com (mailgate.nlsystems.com [62.49.251.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A40643F75 for ; Tue, 27 May 2003 01:57:07 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by herring.nlsystems.com (8.12.9/8.12.8) with ESMTP id h4R8uwRP080735; Tue, 27 May 2003 09:56:58 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-hackers@freebsd.org, Oliver Fromme Date: Tue, 27 May 2003 09:56:58 +0100 User-Agent: KMail/1.5 References: <200304280054.h3S0sTi2006266@lurza.secnetix.de> In-Reply-To: <200304280054.h3S0sTi2006266@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305270956.58065.dfr@nlsystems.com> X-Spam-Status: No, hits=-26.1 required=6.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT version=2.50 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Re: x86-64 support 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 May 2003 08:57:09 -0000 On Monday 28 April 2003 1:54 am, Oliver Fromme wrote: > Narvi wrote: > > On Sat, 26 Apr 2003, M. Warner Losh wrote: > > > In message: <20030427064014.H40030-100000@haldjas.folklore.ee> > > > > > > Narvi writes: > > > : option USE_PI_DIGITS 100 > > > > > > Only if you could implement it with integer math :-) > > > > where's the problem in that ? most mp libs use integer arithmetic, > > and x86-64 gives you 64x64->128 bit widening multiplies 8-) > > You don't need that; the digits of pi can be calculated > quite easily with integer math. This snippet is from my > signature collection: > > int f[9800],b,c=9814,g,i;long > a=1e4,d,e,h;main(){for(;b=c,c-=14;i=printf( > "%04d",e+d/a),e=d%a)while(g=--b*2)d=h*b+a*(i?f[b]:a/5),h=d/--g,f[b]=d >%g;} > > Of course it doesn't comply with style(9), otherwise it > wouldn't fit into two lines. Prettifying (de-obfuscating) > it to make it style(9)-compliant is left as an exercise to > the reader. ;-) Doesn't appear to work. When I run this, it prints '1877' followed by lots of zeros... -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 02:20:17 2003 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 737D537B401 for ; Tue, 27 May 2003 02:20:17 -0700 (PDT) Received: from cirb503493.alcatel.com.au (c18609.belrs1.nsw.optusnet.com.au [210.49.80.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E02D43F93 for ; Tue, 27 May 2003 02:20:16 -0700 (PDT) (envelope-from peterjeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])h4R9KDp9044635; Tue, 27 May 2003 19:20:13 +1000 (EST) (envelope-from jeremyp@cirb503493.alcatel.com.au) Received: (from jeremyp@localhost) by cirb503493.alcatel.com.au (8.12.8/8.12.8/Submit) id h4R9K700044634; Tue, 27 May 2003 19:20:07 +1000 (EST) Date: Tue, 27 May 2003 19:20:06 +1000 From: Peter Jeremy To: Doug Rabson Message-ID: <20030527092006.GB44520@cirb503493.alcatel.com.au> References: <200304280054.h3S0sTi2006266@lurza.secnetix.de> <200305270956.58065.dfr@nlsystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200305270956.58065.dfr@nlsystems.com> User-Agent: Mutt/1.4.1i cc: freebsd-hackers@freebsd.org Subject: Re: x86-64 support 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 May 2003 09:20:17 -0000 On Tue, May 27, 2003 at 09:56:58AM +0100, Doug Rabson wrote: >On Monday 28 April 2003 1:54 am, Oliver Fromme wrote: >> You don't need that; the digits of pi can be calculated >> quite easily with integer math. This snippet is from my >> signature collection: >> >> int f[9800],b,c=9814,g,i;long >> a=1e4,d,e,h;main(){for(;b=c,c-=14;i=printf( >> "%04d",e+d/a),e=d%a)while(g=--b*2)d=h*b+a*(i?f[b]:a/5),h=d/--g,f[b]=d >>%g;} >> >> Of course it doesn't comply with style(9), otherwise it >> wouldn't fit into two lines. Prettifying (de-obfuscating) >> it to make it style(9)-compliant is left as an exercise to >> the reader. ;-) > >Doesn't appear to work. When I run this, it prints '1877' followed by >lots of zeros... A followup pointed out that there is an error in the size of 'f': it should be f[9814] (matching c). With this change, the result looks reasonably close to pi. Peter From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 11:34:50 2003 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 98D4437B401 for ; Tue, 27 May 2003 11:34:50 -0700 (PDT) Received: from maeko.hayai.de (denver038.server4free.de [217.172.178.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 353B643F75 for ; Tue, 27 May 2003 11:34:47 -0700 (PDT) (envelope-from mail@maeko.hayai.de) Received: from maeko.hayai.de (localhost [127.0.0.1]) by maeko.hayai.de (8.12.7/8.12.7) with ESMTP id h4RIYko3025413 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Tue, 27 May 2003 20:34:46 +0200 Received: (from mail@localhost) by maeko.hayai.de (8.12.7/8.12.7/Submit) id h4RIYjja025412; Tue, 27 May 2003 20:34:45 +0200 Date: Tue, 27 May 2003 20:34:45 +0200 From: Marco Wertejuk To: Maxim Konovalov Message-ID: <20030527183445.GA25234@maeko> Mail-Followup-To: Maxim Konovalov , freebsd-hackers@freebsd.org References: <20030514184845.GA7573@maeko> <20030515114239.Y95792@news1.macomnet.ru> <20030516153333.GA29165@maeko> <20030520190746.P6042@news1.macomnet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030520190746.P6042@news1.macomnet.ru> User-Agent: Mutt/1.4i cc: freebsd-hackers@freebsd.org Subject: Re: vlan/bridging broken in 4.8-release? 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 May 2003 18:34:50 -0000 Hello Maxim, today I've tried your hack and it works, at least it seems so. It was not exactly the same setup but nearly the same. The bridge has two interfaces (fxp0, fxp1) and one host is connected to each interface (using crosslink cables, no other networking devices such as broken HP ProCurve switches). The host on fxp1 (10.10.10.16) does not use vlans, the host on fxp0 (10.10.10.18) is in vlan id 1. tcpdump -tni fxp0, fxp1, vlan0: (yes 10.10.10.18 has a strange mac address, because of a broken fxp0 card I guess ;) 6:0:ff:1:6:0 ff:ff:ff:ff:ff:ff 0806 56: arp who-has 10.10.10.16 tell 10.10.10.18 0:d0:b7:17:5:78 6:0:ff:1:6:0 0806 60: arp reply 10.10.10.16 is-at 0:d0:b7:17:5:78 6:0:ff:1:6:0 0:d0:b7:17:5:78 0800 98: 10.10.10.18 > 10.10.10.16: icmp: echo request 0:d0:b7:17:5:78 6:0:ff:1:6:0 0800 98: 10.10.10.16 > 10.10.10.18: icmp: echo reply 6:0:ff:1:6:0 ff:ff:ff:ff:ff:ff 8100 60: 802.1Q vlan#1 P0 arp who-has 10.10.10.16 tell 10.10.10.18 0:d0:b7:17:5:78 6:0:ff:1:6:0 8100 64: 802.1Q vlan#1 P0 arp reply 10.10.10.16 is-at 0:d0:b7:17:5:78 6:0:ff:1:6:0 0:d0:b7:17:5:78 8100 102: 802.1Q vlan#1 P0 10.10.10.18 > 10.10.10.16: icmp: echo request 0:d0:b7:17:5:78 6:0:ff:1:6:0 8100 102: 802.1Q vlan#1 P0 10.10.10.16 > 10.10.10.18: icmp: echo reply 6:0:ff:1:6:0 0:d0:b7:17:5:78 0800 98: 10.10.10.18 > 10.10.10.16: icmp: echo request 0:d0:b7:17:5:78 6:0:ff:1:6:0 0800 98: 10.10.10.16 > 10.10.10.18: icmp: echo reply 6:0:ff:1:6:0 0:d0:b7:17:5:78 8100 102: 802.1Q vlan#1 P0 10.10.10.18 > 10.10.10.16: icmp: echo request 0:d0:b7:17:5:78 6:0:ff:1:6:0 8100 102: 802.1Q vlan#1 P0 10.10.10.16 > 10.10.10.18: icmp: echo reply Two pings were send successfully with your hack and I guess everything else would work too, but I have no time for further testing, maybe the people who wrote the PR have more time ... Please make a real patch out of your hack and get it commited into -stable because I still want to use it for one of my customers :) Hopefully I did not forget anything in this email :) -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Consulting & Internet Solutions From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 12:08:22 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 8E08137B401; Tue, 27 May 2003 12:08:22 -0700 (PDT) To: hackers@freebsd.org Date: Tue, 27 May 2003 12:08:22 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20030527190822.8E08137B401@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Subject: Rrrrrr..... 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 May 2003 19:08:22 -0000 Ok, I've gotten enough e-mail about this now that it's starting to be annoying, so I'm going to nip this in the bud right now. People have started asking me about the Broadcom 4400 series chips. They have noticed that there's this "if_bge" driver with the word "Broadcom" associated with it, and seem to think it may somehow be coerced into working with the 44xx chipset, even though the documentation implies nothing of the sort. So everybody listen up: *NO*, the 44xx chips are *NOT* the same as the 57xx chips. The 57xx devices are 10/100/1000. The 44xx are 10/100 *ONLY*. *NO* they do *NOT* have the same programming API. *NO*, the bge(4) driver will *NOT* work with the 44xx chips. Ever. I don't care how much you whine. *NO* I don't have any programming manuals for the 44xx chips and don't know (or care) if I ever will. *NO* I will *NOT* port the Linux driver to FreeBSD. Is everyone clear on this now? Good, because any further questions along these lines will be summarily ignored. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 13:42:44 2003 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 60DB337B401 for ; Tue, 27 May 2003 13:42:44 -0700 (PDT) Received: from symonds.net (ca1.symonds.net [66.92.42.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB3CE43F85 for ; Tue, 27 May 2003 13:42:43 -0700 (PDT) (envelope-from ashish@symonds.net) Received: from localhost (symonds.net) [127.0.0.1] by symonds.net with smtp (Exim 3.35 #1 (Debian)) id 19KlHN-0001r2-00; Tue, 27 May 2003 13:42:41 -0700 Received: from 203.192.199.30 (SquirrelMail authenticated user ashish) by secure.symonds.net with HTTP; Wed, 28 May 2003 02:12:41 +0530 (IST) Message-ID: <1380.203.192.199.30.1054068161.squirrel@secure.symonds.net> Date: Wed, 28 May 2003 02:12:41 +0530 (IST) From: "Ashish Kulkarni" To: Importance: Normal MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: ashish@symonds.net Subject: Re: [PATCH] changing the ToS in IP Header X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ashish@symonds.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 20:42:44 -0000 > > The attached patch adds a new sysctl oid for support of a > "net.inet.ip.default_tos" (default: 0). > > I sent it as a context diff, in case the kernel has changed > more than a little since the last time I updated. > > Note: I only compile-tested this. > Thanks a lot for the help, and especially the quick response :-) The patch worked perfectly for me (had to do some very minor modifications as I was testing on 4.5-RELEASE). Would it be possible for this to be committed to 5-CURRENT, or is it frozen for 5.1? I can imagine this being useful to people ... Thanks, Ashish From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 13:54:05 2003 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 8878D37B404 for ; Tue, 27 May 2003 13:54:05 -0700 (PDT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1EB743FBD for ; Tue, 27 May 2003 13:54:04 -0700 (PDT) (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.9/8.12.3) with ESMTP id h4RKs2Hp004558 for ; Tue, 27 May 2003 13:54:02 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.9/8.12.3/Submit) id h4RKs24o004552 for hackers@freebsd.org; Tue, 27 May 2003 13:54:02 -0700 Date: Tue, 27 May 2003 13:54:02 -0700 From: Brooks Davis To: hackers@freebsd.org Message-ID: <20030527205402.GA30952@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu Subject: rc.diskless1/initdiskless change for review 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 May 2003 20:54:05 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable The following patch (against rc.diskless1 on STABLE, but the code is identical in rc.d/initdiskless) simplifies the likely common case for remounts in the /conf hierarchy. It allows you to specify a path (i.e. /etc) in the diskless_remount file rather then having to record the path to the NFS root. I'm using this to allow me to copy a the entire root to a new location on my NFS server to do an upgrade without breaking running hosts on the old root and without touching /conf at all. I'd like to commit this after the tree is thawed again. What do people think? -- Brooks Index: rc.diskless1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/cvs/src/etc/Attic/rc.diskless1,v retrieving revision 1.5.2.11 diff -u -r1.5.2.11 rc.diskless1 --- rc.diskless1 14 Apr 2003 18:12:05 -0000 1.5.2.11 +++ rc.diskless1 24 May 2003 00:33:19 -0000 @@ -121,6 +121,17 @@ done echo "Interface ${bootp_ifc} IP-Address ${bootp_ipa} Broadcast ${bootp_ipb= ca}" =20 +# Figure out our NFS root path +# +set `mount -t nfs` +while [ $# -ge 1 ] ; do + if [ "$2" =3D "on" -a "$3" =3D "/" ]; then + nfsroot=3D"$1" + break + fi + shift +done + # Resolve templates in /conf/base, /conf/default, /conf/${bootp_ipbca}, # and /conf/${bootp_ipa}. For each subdirectory found within these=20 # directories: @@ -136,6 +147,10 @@ # might contain 'myserver:/etc'. NFS remounts allow you to avoid # having to dup your system directories in /conf. Your server must # be sure to export those filesystems -alldirs, however. +# If the diskless_remount file contains a string beginning with a +# '/' it is assumed that the local nfsroot should be prepended to +# it before attemping to mount allowing the root to be relocated +# without needing to change the remount files. # for i in base default ${bootp_ipbca} ${bootp_ipa} ; do for j in /conf/$i/* ; do @@ -150,6 +165,9 @@ # if [ -d $j -a -f $j/diskless_remount ]; then nfspt=3D`/bin/cat $j/diskless_remount` + if [ `expr "$nfspt" : '\(.\)'` =3D "/" ]; then + nfspt=3D"${nfsroot}${nfspt}" + fi mount_nfs $nfspt $j chkerr $? "mount_nfs $nfspt $j" fi --=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 --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+09BpXY6L6fI4GtQRArfNAKDK/qwFPD4ZFibqWWr7MbsK45UuTgCfaVK7 IonXDf2sYgvvu8d9YbnTQSI= =xh51 -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 14:00:19 2003 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 62C9237B401 for ; Tue, 27 May 2003 14:00:19 -0700 (PDT) Received: from symonds.net (ca1.symonds.net [66.92.42.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id A495743F75 for ; Tue, 27 May 2003 14:00:18 -0700 (PDT) (envelope-from ashish@symonds.net) Received: from localhost (symonds.net) [127.0.0.1] by symonds.net with smtp (Exim 3.35 #1 (Debian)) id 19KlYO-000209-00; Tue, 27 May 2003 14:00:16 -0700 Received: from 203.192.199.30 (SquirrelMail authenticated user ashish) by secure.symonds.net with HTTP; Wed, 28 May 2003 02:30:16 +0530 (IST) Message-ID: <1392.203.192.199.30.1054069216.squirrel@secure.symonds.net> Date: Wed, 28 May 2003 02:30:16 +0530 (IST) From: "Ashish Kulkarni" To: Importance: Normal MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: ashish@symonds.net Subject: Re: changing the ToS in IP Header X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ashish@symonds.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 21:00:19 -0000 Kenjiro Cho wrote: > Tell your ISP not to use 0x02; it violates the standard. > You may modify the upper 6 bits for an arbitrary value, though. Well, my cable ISP provides a 3rd party Windows-only client that enables forwarding of packets only when logged in. I've reverse engineering that protocol sucessfully, and it requires the TOS to be 0x02 ... I imagine this TOS is only valid uptil the gateway, after which a different TOS is used. Anyway, all this is unofficial so I can't really go to my ISP and mention it ;-) > The lower 2 bits of the (now deprecated) TOS field are officially > assigned to ECN (RFC3168). 0x02, ECT(0), is used to indicate that the > sender is ECN-capable. > > ALTQ supports diffserv and is capable of rewriting the upper 6 bits of > the TOS field. > http://www.csl.sony.co.jp/~kjc/software.html I have one question: as you said, I can use ALTQ to reset all the upper 6 bits to zero, so as to get the pattern 0x02 (using the kernel patch by Terry Lambert). Will this have any implications for its working and for ECN? I need this because several protocols (ssh, etc) use a modified TOS, which I want to be reset to default value. Thanks, Ashish From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 14:03:31 2003 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 2A10837B401 for ; Tue, 27 May 2003 14:03:31 -0700 (PDT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A579043FDD for ; Tue, 27 May 2003 14:03:30 -0700 (PDT) (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.9/8.12.3) with ESMTP id h4RL3SHp006397 for ; Tue, 27 May 2003 14:03:28 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.9/8.12.3/Submit) id h4RL3SH0006396 for hackers@freebsd.org; Tue, 27 May 2003 14:03:28 -0700 Date: Tue, 27 May 2003 14:03:28 -0700 From: Brooks Davis To: hackers@freebsd.org Message-ID: <20030527210328.GB30952@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xXmbgvnjoT4axfJE" Content-Disposition: inline User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu Subject: doing things around rc.d/diskless 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 May 2003 21:03:31 -0000 --xXmbgvnjoT4axfJE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On some diskless 4.x systems, I've got the following patch in place to let me do things before and after rc.diskless2 does it's stuff: Index: rc.diskless2 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/cvs/src/etc/Attic/rc.diskless2,v retrieving revision 1.5.2.14 diff -u -r1.5.2.14 rc.diskless2 --- rc.diskless2 23 Dec 2002 17:39:06 -0000 1.5.2.14 +++ rc.diskless2 24 May 2003 00:33:22 -0000 @@ -51,6 +51,10 @@ . /etc/rc.conf fi =20 +if [ -r /etc/rc.diskless2_pre ]; then + . /etc/rc.diskless2_pre +fi + # If we do not have a writable /var, create a memory # filesystem for /var. We don't have /usr yet so # use mkdir instead of touch to test. We want mount @@ -135,3 +139,6 @@ rm -f /tmp/dev.cpio.gz fi =20 +if [ -r /etc/rc.diskless2_post ]; then + . /etc/rc.diskless2_post +fi In practice, I use rc.diskless2_pre to do some checks to make sure the system's disk is partitioned the way I want it, fix it if it's isn't, and mount /var so diskless2 won't make a new one that "mount -a" will immedialy hide. rc.diskless2_post is used to populate /var with non-standard things. What's the right way to do this in the rc.d world? It seems like I could add more scripts which will run before and after rc.d/diskless, but I don't understand rc.d all that well. Thanks, 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 --xXmbgvnjoT4axfJE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+09KbXY6L6fI4GtQRAt9qAKCqArC+m1vvlGNqtAGiKA0uk8TVKwCcDjBc PNye7YaYKwMqkaTM5eMUMGc= =zbEu -----END PGP SIGNATURE----- --xXmbgvnjoT4axfJE-- From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 14:44:40 2003 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 564B537B401; Tue, 27 May 2003 14:44:40 -0700 (PDT) Received: from dmlb.org (pc2-cmbg4-6-cust36.cmbg.cable.ntl.com [81.96.76.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F4EB43F85; Tue, 27 May 2003 14:44:39 -0700 (PDT) (envelope-from dmlb@dmlb.org) Received: from slave.my.domain ([192.168.200.39]) by dmlb.org with esmtp (Exim 3.36 #1) id 19KmFK-000I5K-00; Tue, 27 May 2003 22:44:38 +0100 Received: from dmlb by slave.my.domain with local (Exim 3.36 #1) id 19KmFK-000KSz-00; Tue, 27 May 2003 22:44:38 +0100 Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20030527190822.8E08137B401@hub.freebsd.org> Date: Tue, 27 May 2003 22:44:38 +0100 (BST) From: Duncan Barclay To: (Bill Paul) Sender: Duncan Barclay cc: hackers@freebsd.org Subject: RE: Rrrrrr..... 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 May 2003 21:44:40 -0000 Dear Bill, On 27-May-2003 Bill Paul wrote: > Ok, I've gotten enough e-mail about this now that it's starting to be > annoying, so I'm going to nip this in the bud right now. If this was prompted by my private email earlier today then I am sorry to have been the straw that broke your back. Having searched the archives over the past couple of days and not finding too much hard information on this chipset I decided a short note to you might speed up the effort I am making in porting the Linux driver. Maybe I didn't make that clear. I have been posting to -current and -mobile on the topic over the past week. The information below confirming that the API is different is all that I asked for. I will carry on with my porting effort. Thanks Duncan > People have started asking me about the Broadcom 4400 series chips. > They have noticed that there's this "if_bge" driver with the word > "Broadcom" associated with it, and seem to think it may somehow be > coerced into working with the 44xx chipset, even though the documentation > implies nothing of the sort. So everybody listen up: > > *NO*, the 44xx chips are *NOT* the same as the 57xx chips. The 57xx > devices are 10/100/1000. The 44xx are 10/100 *ONLY*. > > *NO* they do *NOT* have the same programming API. > > *NO*, the bge(4) driver will *NOT* work with the 44xx chips. Ever. I don't > care how much you whine. > > *NO* I don't have any programming manuals for the 44xx chips and don't > know (or care) if I ever will. > > *NO* I will *NOT* port the Linux driver to FreeBSD. > > Is everyone clear on this now? Good, because any further questions > along these lines will be summarily ignored. > > -Bill > > -- > ============================================================================= > -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu > wpaul@windriver.com | Wind River Systems > ============================================================================= > "If stupidity were a handicap, you'd have the best parking spot." > ============================================================================= -- ________________________________________________________________________ Duncan Barclay | dmlb@dmlb.org | dmlb@freebsd.org| From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 16:55:46 2003 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 88F7A37B401 for ; Tue, 27 May 2003 16:55:46 -0700 (PDT) Received: from arbornet.org (m-net.arbornet.org [209.142.209.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id D934F43F93 for ; Tue, 27 May 2003 16:55:45 -0700 (PDT) (envelope-from krylenko@m-net.arbornet.org) Received: from m-net.arbornet.org (localhost [127.0.0.1]) by arbornet.org (8.12.3p2/8.11.2) with ESMTP id h4RNwT5L020776; Tue, 27 May 2003 19:58:29 -0400 (EDT) (envelope-from krylenko@m-net.arbornet.org) Received: from localhost (krylenko@localhost)h4RNwTiS020773; Tue, 27 May 2003 23:58:29 GMT Date: Tue, 27 May 2003 23:58:29 +0000 (GMT) From: Nikolai Krylenko To: hackers@freebsd.org Message-ID: <20030527235734.L20621-100000@m-net.arbornet.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: MATT@FROUP.COM Subject: Hey, man 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 May 2003 23:55:46 -0000 What's up? I hear you use Debian! From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 16:55:53 2003 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 41CA137B40B; Tue, 27 May 2003 16:55:52 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D6F043F93; Tue, 27 May 2003 16:55:51 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by attbi.com (sccrmhc03) with ESMTP id <2003052723554900300igs1ae>; Tue, 27 May 2003 23:55:50 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA29921; Tue, 27 May 2003 16:55:48 -0700 (PDT) Date: Tue, 27 May 2003 16:55:47 -0700 (PDT) From: Julian Elischer To: hackers@freebsd.org, obrien@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: gcc problem/openoffice failure 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 May 2003 23:55:53 -0000 For the last month (more actually)(and after completely rebuilding my system and all the ports on it) I have not been able to compile the openoffice port due to gcc failures. (I have posted the message earlier several times) Has anyone been able to compile the openoffice port recently? somewhere in it's private compilation of mozilla (why does it do that? I already have mozilla running?) gcc (doing c++) has a heart attach and keels over dead. This has been reproducible for me for at least a month and probably more. Has anyone else seen this? Is the openoffice port working for everyone else? (on FreeBSD 4.8++) (4.8-RELEASE had the same problem for me) julian From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 17:06:37 2003 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 D527A37B401 for ; Tue, 27 May 2003 17:06:37 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-104-32.dsl.lsan03.pacbell.net [64.169.104.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A3C943F85 for ; Tue, 27 May 2003 17:06:37 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id CD1AF66B9B for ; Tue, 27 May 2003 17:06:36 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 7B919AF0; Tue, 27 May 2003 17:06:36 -0700 (PDT) Date: Tue, 27 May 2003 17:06:36 -0700 From: Kris Kennaway Message-ID: <20030528000636.GA88887@rot13.obsecurity.org> References: <20030527235734.L20621-100000@m-net.arbornet.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZPt4rx8FFjLCG7dd" Content-Disposition: inline In-Reply-To: <20030527235734.L20621-100000@m-net.arbornet.org> User-Agent: Mutt/1.4.1i cc: hackers@freebsd.org Subject: Re: Hey, man 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 May 2003 00:06:38 -0000 --ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, May 27, 2003 at 11:58:29PM +0000, Nikolai Krylenko wrote: > What's up? I hear you use Debian! WORST TROLL EVER! Kris --ZPt4rx8FFjLCG7dd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+0/2MWry0BWjoQKURAlEOAKCqXmLEjLsMu/msRHkoORCiifTQNgCeMIom Y1/jSR5opgrL3x2Hj1gE1Hs= =HUvu -----END PGP SIGNATURE----- --ZPt4rx8FFjLCG7dd-- From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 18:08:23 2003 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 1275237B401 for ; Tue, 27 May 2003 18:08:23 -0700 (PDT) Received: from mail.cruzio.com (mail.cruzio.com [63.249.95.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A44643FA3 for ; Tue, 27 May 2003 18:08:22 -0700 (PDT) (envelope-from brucem@cruzio.com) Received: from cruzio.com (dsl3-63-249-85-132.cruzio.com [63.249.85.132]) by mail.cruzio.com with ESMTP id h4S1FPRC022691; Tue, 27 May 2003 18:15:25 -0700 (PDT) Received: (from brucem@localhost) by cruzio.com (8.11.3/8.11.3) id h4S0Z8000399; Tue, 27 May 2003 17:35:08 -0700 (PDT) (envelope-from brucem) Date: Tue, 27 May 2003 17:35:08 -0700 (PDT) From: "Bruce R. Montague" Message-Id: <200305280035.h4S0Z8000399@cruzio.com> To: julian@elischer.org cc: hackers@freebsd.org Subject: Re: gcc problem/openoffice failure 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 May 2003 01:08:23 -0000 Julian Elischer wrote: > ... I have not been able to compile the openoffice port ... > ... Has anyone else seen this? I tried to build openoffice on a "clean" -current system, built from a recent cvsup, and it failed to compile... This was perhaps a week and a half ago, kept meaning to get back and look at it, but time seems to have got the best of me. - bruce From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 19:40:13 2003 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 62C5637B401; Tue, 27 May 2003 19:40:13 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A270C43FA3; Tue, 27 May 2003 19:40:12 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h4S2dVM7090522; Tue, 27 May 2003 19:39:34 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200305280239.h4S2dVM7090522@gw.catspoiler.org> Date: Tue, 27 May 2003 19:39:31 -0700 (PDT) From: Don Lewis To: julian@elischer.org In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: hackers@FreeBSD.org cc: obrien@FreeBSD.org Subject: Re: gcc problem/openoffice failure 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 May 2003 02:40:13 -0000 On 27 May, Julian Elischer wrote: > > For the last month (more actually)(and after completely rebuilding my > system and all the ports on it) I have not been able to compile > the openoffice port due to gcc failures. > (I have posted the message earlier several times) > Has anyone been able to compile the openoffice port recently? > > somewhere in it's private compilation of mozilla (why does it do that? I > already have mozilla running?) gcc (doing c++) has a heart attach and > keels over dead. I think the reason to make the build take longer. Lots of fun on 400 MHz PII. > This has been reproducible for me for at least a month and probably > more. > > Has anyone else seen this? > Is the openoffice port working for everyone else? > (on FreeBSD 4.8++) (4.8-RELEASE had the same problem for me) I was able to build it on April 22. I don't know when the previous cvsup and buildworld was. My kernel.old dates to April 25th, so I don't have any history before that time. From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 20:13:47 2003 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 2EAEA37B401 for ; Tue, 27 May 2003 20:13:47 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63D6E43F85 for ; Tue, 27 May 2003 20:13:46 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h4S3DTkA059417; Tue, 27 May 2003 21:13:29 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 27 May 2003 21:13:12 -0600 (MDT) Message-Id: <20030527.211312.108985092.imp@bsdimp.com> To: brucem@cruzio.com From: "M. Warner Losh" In-Reply-To: <200305280035.h4S0Z8000399@cruzio.com> References: <200305280035.h4S0Z8000399@cruzio.com> X-Mailer: Mew version 2.1 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: gcc problem/openoffice failure 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 May 2003 03:13:47 -0000 In message: <200305280035.h4S0Z8000399@cruzio.com> "Bruce R. Montague" writes: : : Julian Elischer wrote: : : > ... I have not been able to compile the openoffice port ... : : > ... Has anyone else seen this? : : : I tried to build openoffice on a "clean" -current system, : built from a recent cvsup, and it failed to compile... This : was perhaps a week and a half ago, kept meaning to get back : and look at it, but time seems to have got the best of me. I wouldn't attempt something this complex without portupgrade... Warner From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 21:33:13 2003 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 58FDB37B401 for ; Tue, 27 May 2003 21:33:13 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id A86BE43F75 for ; Tue, 27 May 2003 21:33:12 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by attbi.com (sccrmhc01) with ESMTP id <20030528043311001003tra5e>; Wed, 28 May 2003 04:33:11 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id VAA31627; Tue, 27 May 2003 21:33:10 -0700 (PDT) Date: Tue, 27 May 2003 21:33:09 -0700 (PDT) From: Julian Elischer To: "M. Warner Losh" In-Reply-To: <20030527.211312.108985092.imp@bsdimp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hackers@freebsd.org cc: brucem@cruzio.com Subject: Re: gcc problem/openoffice failure 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 May 2003 04:33:13 -0000 On Tue, 27 May 2003, M. Warner Losh wrote: > In message: <200305280035.h4S0Z8000399@cruzio.com> > "Bruce R. Montague" writes: > : > : Julian Elischer wrote: > : > : > ... I have not been able to compile the openoffice port ... > : > : > ... Has anyone else seen this? > : > : > : I tried to build openoffice on a "clean" -current system, > : built from a recent cvsup, and it failed to compile... This > : was perhaps a week and a half ago, kept meaning to get back > : and look at it, but time seems to have got the best of me. > > I wouldn't attempt something this complex without portupgrade... > > Warner this WAS under port-upgrade.. run 3 times sequentially of course now that I've said this, it may have decided to go past the spot where it failed last time. From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 22:12:49 2003 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 B5B6337B401; Tue, 27 May 2003 22:12:49 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 148DC43F85; Tue, 27 May 2003 22:12:49 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h4S5BmM7090715; Tue, 27 May 2003 22:11:52 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200305280511.h4S5BmM7090715@gw.catspoiler.org> Date: Tue, 27 May 2003 22:11:48 -0700 (PDT) From: Don Lewis To: imp@bsdimp.com In-Reply-To: <20030527.211312.108985092.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: hackers@FreeBSD.org cc: brucem@cruzio.com cc: julian@elischer.org cc: openoffice@FreeBSD.org Subject: Re: gcc problem/openoffice failure 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 May 2003 05:12:50 -0000 On 27 May, M. Warner Losh wrote: > In message: <200305280035.h4S0Z8000399@cruzio.com> > "Bruce R. Montague" writes: > : > : Julian Elischer wrote: > : > : > ... I have not been able to compile the openoffice port ... > : > : > ... Has anyone else seen this? > : > : > : I tried to build openoffice on a "clean" -current system, > : built from a recent cvsup, and it failed to compile... This > : was perhaps a week and a half ago, kept meaning to get back > : and look at it, but time seems to have got the best of me. > > I wouldn't attempt something this complex without portupgrade... That reminds me ... the openoffice port ignores non-zero exit status in too many places. More than once I've had the install phase (and maybe even the build phase fail which then proceeded to the install phase which then failed), but the the exit status was ignored, make exited with a zero status, and portupgrade thought that the installation succeeded and then nuked the working backup copy of openoffice and did a make clean. A build from scratch takes more than 24 hours on my -stable box ... From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 23:35:10 2003 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 A7FB337B401 for ; Tue, 27 May 2003 23:35:10 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEFE443F85 for ; Tue, 27 May 2003 23:35:09 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38ldvsn.dialup.mindspring.com ([209.86.255.151] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19KuWh-00050O-00; Tue, 27 May 2003 23:35:07 -0700 Message-ID: <3ED45855.D9CE8A7@mindspring.com> Date: Tue, 27 May 2003 23:33:57 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: ashish@symonds.net References: <1380.203.192.199.30.1054068161.squirrel@secure.symonds.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4655026cd4cd81ad652c7da4f445d0e073ca473d225a0f487350badd9bab72f9c350badd9bab72f9c cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] changing the ToS in IP Header 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 May 2003 06:35:11 -0000 Ashish Kulkarni wrote: > > The attached patch adds a new sysctl oid for support of a > > "net.inet.ip.default_tos" (default: 0). > > > > I sent it as a context diff, in case the kernel has changed > > more than a little since the last time I updated. > > > > Note: I only compile-tested this. > > Thanks a lot for the help, and especially the quick response :-) > > The patch worked perfectly for me (had to do some very minor modifications > as I was testing on 4.5-RELEASE). Would it be possible for this to be > committed to 5-CURRENT, or is it frozen for 5.1? I can imagine this being > useful to people ... The best place to send it is to a committer who lives in the networking code. The easiest way to find one is to go to the web page and do a CVS annotate on the file to see who touched it last in that area (or just look at recent commit log messages). Your best bet for something like this is probably the people who have modified it's names, followed by "@freebsd.org"; fo this file, see: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/in_pcb.c kan, cjc, jlemon, imp, hsu, and sam are all @freebsd.org email addresses who have touched this file so far this year. -- Terry From owner-freebsd-hackers@FreeBSD.ORG Tue May 27 23:44:24 2003 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 176DE37B401 for ; Tue, 27 May 2003 23:44:24 -0700 (PDT) Received: from smtp-relay.omnis.com (smtp-relay.omnis.com [216.239.128.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id C055A43F3F for ; Tue, 27 May 2003 23:44:20 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.homeunix.net (66-91-236-204.san.rr.com [66.91.236.204]) by smtp-relay.omnis.com (Postfix) with ESMTP id B59521BD93; Tue, 27 May 2003 23:44:19 -0700 (PDT) From: Wes Peters Organization: Softweyr To: Julian Elischer , hackers@freebsd.org Date: Fri, 23 May 2003 20:40:30 -0700 User-Agent: KMail/1.5.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305232040.30367.wes@softweyr.com> Subject: Re: gcc bug? Openoffice port impossibel to compile on 4.8 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 May 2003 06:44:24 -0000 On Thursday 22 May 2003 10:23 am, Julian Elischer wrote: > I have rebuilt my system several times and rebuilt all ports.. > /usr/ports/editors/openoffice always ends up with: GCC 3.2 is broken by design. It insists, amongst other stupidities, on type-checking arguments using old style declarations like: int foo(bar) char *bar; {} rendering most UNIX software from before 1996 uncompilable. This is biting one of my ports, I can't figure out how to shut the fscking thing up, and am pretty much beyond caring. The Powers That Be in GCC-land seem to have decided for us the world doesn't need any stinking 20-year-old software. -- Where am I, and what am I doing in this handbasket? Wes Peters wes@softweyr.com From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 01:08:40 2003 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 DDAEA37B407 for ; Wed, 28 May 2003 01:08:40 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.74.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id A238443F3F for ; Wed, 28 May 2003 01:08:39 -0700 (PDT) (envelope-from molter@tin.it) Received: from tin.it (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 28 May 2003 10:07:54 +0100 Received: from cisco.com (localhost [127.0.0.1])h4S86fbY023274 for ; Wed, 28 May 2003 10:06:41 +0200 (MET DST) Received: from www.example.org (ssh-ams-1.cisco.com [144.254.74.55]) by cisco.com (8.8.8+Sun/8.8.8) with SMTP id KAA18081 for ; Wed, 28 May 2003 10:08:37 +0200 (MET DST) Received: (qmail 1797 invoked by uid 1000); 28 May 2003 08:08:29 -0000 Date: Wed, 28 May 2003 10:08:29 +0200 From: Marco Molteni To: hackers@freebsd.org Message-ID: <20030528080829.GB1682@cobweb.example.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: Julian Elischer Subject: Re: gcc problem/openoffice failure 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 May 2003 08:08:41 -0000 Julian Elischer wrote [2003-05-27]: > > For the last month (more actually)(and after completely rebuilding my > system and all the ports on it) I have not been able to compile > the openoffice port due to gcc failures. > (I have posted the message earlier several times) > Has anyone been able to compile the openoffice port recently? [..] I assume you tried to compile the elephant because you weren't aware that there exist a fbsd package for it. I did the same thing until I got tired ;-) http://projects.imp.ch/openoffice/ has packages for -stable and -current. On my -stable I run openoffice-1.0.3_2. On my -current, after trying to run openoffice-1.1Beta1 and being bitten by all sort of bugs, I just installed the compat libraries for -stable and then the same openoffice-1.0.3_2 for -stable. Runs like a charm :-) marco From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 02:38:03 2003 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 B9C2237B401 for ; Wed, 28 May 2003 02:38:03 -0700 (PDT) Received: from cirb503493.alcatel.com.au (c18609.belrs1.nsw.optusnet.com.au [210.49.80.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 596E243F93 for ; Wed, 28 May 2003 02:38:02 -0700 (PDT) (envelope-from peterjeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])h4S9bQp9046362; Wed, 28 May 2003 19:37:26 +1000 (EST) (envelope-from jeremyp@cirb503493.alcatel.com.au) Received: (from jeremyp@localhost) by cirb503493.alcatel.com.au (8.12.8/8.12.8/Submit) id h4S9bMxL046361; Wed, 28 May 2003 19:37:22 +1000 (EST) Date: Wed, 28 May 2003 19:37:22 +1000 From: Peter Jeremy To: Julian Elischer Message-ID: <20030528093722.GA46290@cirb503493.alcatel.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: hackers@freebsd.org Subject: Re: gcc problem/openoffice failure 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 May 2003 09:38:04 -0000 On Tue, May 27, 2003 at 04:55:47PM -0700, Julian Elischer wrote: >Has anyone been able to compile the openoffice port recently? It built successfully for me on 25th April in -STABLE. Are you using any non-default flags or options? Last time I tried to build it with debugging enabled (beginning of February), it failed (reproducably) inside Mozilla but no-one seemed interested. (The OO maintainer claimed it was a Mozilla problem but that side-stepped the fact that the OO port explicitly over-rides the "no debugging" flags in Mozilla). I know that I previously compiled OO with debugging but it seems that one of the OO or Mozilla upgrades broke it. Peter From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 05:12:38 2003 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 AF85837B407 for ; Wed, 28 May 2003 05:12:38 -0700 (PDT) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A24A43F85 for ; Wed, 28 May 2003 05:12:38 -0700 (PDT) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id B13C0530E; Wed, 28 May 2003 14:12:35 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Wes Peters References: <200305232040.30367.wes@softweyr.com> From: Dag-Erling Smorgrav Date: Wed, 28 May 2003 14:12:34 +0200 In-Reply-To: <200305232040.30367.wes@softweyr.com> (Wes Peters's message of "Fri, 23 May 2003 20:40:30 -0700") Message-ID: User-Agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: hackers@freebsd.org cc: Julian Elischer Subject: Re: gcc bug? Openoffice port impossibel to compile on 4.8 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 May 2003 12:12:39 -0000 Wes Peters writes: > GCC 3.2 is broken by design. It insists, amongst other stupidities, on > type-checking arguments using old style declarations like: > > int foo(bar) > char *bar; > {} > > rendering most UNIX software from before 1996 uncompilable. have you tried -traditional? DES -- Dag-Erling Smorgrav - des@ofug.org From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 06:34:38 2003 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 211BD37B401 for ; Wed, 28 May 2003 06:34:38 -0700 (PDT) Received: from tensor.xs4all.nl (tensor.xs4all.nl [194.109.160.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4809143F85 for ; Wed, 28 May 2003 06:34:37 -0700 (PDT) (envelope-from dim@xs4all.nl) Received: from kilgore.dim (kilgore.dim [192.168.0.3]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by tensor.xs4all.nl (Postfix) with ESMTP id EEBFD555C; Wed, 28 May 2003 15:34:34 +0200 (CEST) Date: Wed, 28 May 2003 15:34:08 +0200 From: Dimitry Andric X-Mailer: The Bat! (v1.62r) Business X-Priority: 3 (Normal) Message-ID: <1211535294.20030528153408@xs4all.nl> To: Dag-Erling Smorgrav In-Reply-To: References: <200305232040.30367.wes@softweyr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: Julian Elischer Subject: Re: gcc bug? Openoffice port impossibel to compile on 4.8 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 May 2003 13:34:38 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2003-05-28 at 14:12:34 Dag-Erling Smorgrav wrote: > have you tried -traditional? gcc 3.1 release notes: The -traditional C compiler option has been deprecated and will be removed in GCC 3.3. (It remains possible to preprocess non-C code with the traditional preprocessor.) gcc 3.3 release notes: The -traditional C compiler option has been removed. It was deprecated in 3.1 and 3.2. (Traditional preprocessing remains available.) So, I'd guess in gcc 3.x, this whole option is completely unmaintained and therefore you'd be quite on your own if you try to compile anything seriously with -traditional... :( 2.95.x is probably not going to go away for a long time. :) -----BEGIN PGP SIGNATURE----- Version: 6.5.8ckt iQA/AwUBPtSsxbBeowouIJajEQLSLgCaAzFTNq08M0cFkBXBHfOWMW9EVnoAoJYH Y1nnQdgORVP5+olXw+VekOYm =CJj2 -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 06:57:01 2003 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 04CE537B401 for ; Wed, 28 May 2003 06:57:01 -0700 (PDT) Received: from comp.chem.msu.su (comp-ext.chem.msu.su [158.250.32.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E22843F93 for ; Wed, 28 May 2003 06:56:56 -0700 (PDT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.12.3p2/8.12.3) with ESMTP id h4SDuoSH031530; Wed, 28 May 2003 17:56:50 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.12.3p2/8.12.3/Submit) id h4SDulsT031525; Wed, 28 May 2003 17:56:47 +0400 (MSD) (envelope-from yar) Date: Wed, 28 May 2003 17:56:47 +0400 From: Yar Tikhiy To: "Simon L. Nielsen" Message-ID: <20030528135646.GD30273@comp.chem.msu.su> References: <200305231907.h4NJ7ubu089890@manor.msen.com> <200305231542.36266.bmilekic@unixdaemons.com> <20030523195346.GA66202@nitro.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030523195346.GA66202@nitro.dk> User-Agent: Mutt/1.5.3i cc: Bosko Milekic cc: freebsd-hackers@freebsd.org Subject: Re: mbuf reference? (and missing man page) 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 May 2003 13:57:01 -0000 On Fri, May 23, 2003 at 09:53:48PM +0200, Simon L. Nielsen wrote: > On 2003.05.23 15:42:36 +0000, Bosko Milekic wrote: > > > > On May 23, 2003 07:07 pm, Michael R. Wayne wrote: > > > Missing man page: > > > 4.8 releasse - man netstat has a reference to mbuf(9) but man mbuf > > > says: No manual entry for mbuf > > > > True. This is a bug. Someone from -doc should fix this, because > > mbuf(9) only exists in 5.0 and later. Try submitting a PR and > > filing it to -doc. Here's a link to an on-line version of the mbuf(9) > > man page appearing in 5.x: > > Actually there is a two PR's open for this already: docs/44337 and > docs/50463. So it will be dealt with when someone gets around to it... It was me who has written the initial version of mbuf(9) and now I have a bit of spare time, so I'll deal with this problem immediately. Thank you who have contributed to this thread for collecting together all the relevant pointers. -- Yar From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 08:08:47 2003 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 3714E37B401 for ; Wed, 28 May 2003 08:08:47 -0700 (PDT) Received: from smtp-relay.omnis.com (smtp-relay.omnis.com [216.239.128.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id C11A643F75 for ; Wed, 28 May 2003 08:08:46 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.homeunix.net (66-91-236-204.san.rr.com [66.91.236.204]) by smtp-relay.omnis.com (Postfix) with ESMTP id AEDB71B5C6; Wed, 28 May 2003 08:08:44 -0700 (PDT) From: Wes Peters Organization: Softweyr To: Dag-Erling Smorgrav Date: Wed, 28 May 2003 08:08:43 -0700 User-Agent: KMail/1.5.2 References: <200305232040.30367.wes@softweyr.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305280808.43444.wes@softweyr.com> cc: hackers@freebsd.org cc: Julian Elischer Subject: Re: gcc bug? Openoffice port impossibel to compile on 4.8 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 May 2003 15:08:47 -0000 On Wednesday 28 May 2003 05:12 am, Dag-Erling Smorgrav wrote: > Wes Peters writes: > > GCC 3.2 is broken by design. It insists, amongst other stupidities, > > on type-checking arguments using old style declarations like: > > > > int foo(bar) > > char *bar; > > {} > > > > rendering most UNIX software from before 1996 uncompilable. > > have you tried -traditional? Yup: cc1: warning: -traditional is deprecated and may be removed Didn't help a bit. -- Where am I, and what am I doing in this handbasket? Wes Peters wes@softweyr.com From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 10:27:58 2003 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 C112D37B401; Wed, 28 May 2003 10:27:58 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id B43C943F93; Wed, 28 May 2003 10:27:57 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (localhost [127.0.0.1]) by haldjas.folklore.ee (8.12.3/8.11.3) with ESMTP id h4SHMtBA049361; Wed, 28 May 2003 20:22:56 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost)h4SHMt1Q049357; Wed, 28 May 2003 20:22:55 +0300 (EEST) Date: Wed, 28 May 2003 20:22:55 +0300 (EEST) From: Narvi To: Don Lewis In-Reply-To: <200305280239.h4S2dVM7090522@gw.catspoiler.org> Message-ID: <20030528202029.F40030-100000@haldjas.folklore.ee> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hackers@freebsd.org cc: julian@elischer.org Subject: Re: gcc problem/openoffice failure 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 May 2003 17:27:59 -0000 On Tue, 27 May 2003, Don Lewis wrote: > On 27 May, Julian Elischer wrote: > > > > For the last month (more actually)(and after completely rebuilding my > > system and all the ports on it) I have not been able to compile > > the openoffice port due to gcc failures. > > (I have posted the message earlier several times) > > Has anyone been able to compile the openoffice port recently? > > > > somewhere in it's private compilation of mozilla (why does it do that? I > > already have mozilla running?) gcc (doing c++) has a heart attach and > > keels over dead. > > I think the reason to make the build take longer. Lots of fun on 400 > MHz PII. > the mozilla addresbook <-> OOo integration part of OOo needs a patch that continues suffer the sad fate of many uncomitted mozilla patches. if you change the main mozilla port to use it, you could just use the main one and no longer need the separate build. From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 15:03:58 2003 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 84F1A37B401 for ; Wed, 28 May 2003 15:03:58 -0700 (PDT) Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3D3443F3F for ; Wed, 28 May 2003 15:03:50 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from foem (IDENT:chuckwebweaving.org@foem [10.11.0.2]) h4SM3nv7042257 for ; Thu, 29 May 2003 00:03:49 +0200 (CEST) (envelope-from dirkx@webweaving.org) Date: Thu, 29 May 2003 00:03:49 +0200 (CEST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@foem To: hackers@freebsd.org Message-ID: <20030528235747.W22309-100000@foem> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: pcic setup / wi0 timeout 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 May 2003 22:03:58 -0000 On two (seemingly) identical machines - one works, one fails Kernel: FreeBSD 5.0-RELEASE #0: Tue May 6 01:04:09 CEST 2003 root@xoxo.zorknet.xs4all.nl:/usr/obj/usr/src/sys/WLEIDEN.6316 cvsup as of that day. Machine 1: pcic0: mem 0xe7001000-0xe7001fff irq 15 at device 8.0 on pci0 pccard0: on pcic0 pcic2: mem 0xe7007000-0xe7007fff irq 12 at device 10.0 on pci0 pccard2: on pcic2 wi2 at port 0x200-0x23f irq 15 slot 0 on pccard0 ..cut.. wi3 at port 0x240-0x27f irq 11 slot 1 on pccard1 ..cut.. Happy bunny. /boot/devices.hints as per default. Machine 2, same kernel/userland - but possibly a different BIOS (although both have an award bios of the same version; the text is differntly formatted in the F2 setup display) pcic0: at device 18.0 on pci0 pcic0: PCI Memory allocated: 0x88000000 pcic0: No PCI interrupt routed, trying ISA. pcic0: Polling mode pccard0: on pcic0 pcic1: at device 20.0 on pci0 pcic1: PCI Memory allocated: 0x88001000 pcic1: No PCI interrupt routed, trying ISA. pcic1: Polling mode pccard1: on pcic1 wi2 at port 0x240-0x27f irq 10 slot 0 on pccard0 wi3 at port 0x280-0x2bf irq 11 slot 1 on pccard1 and as soon as it sees any traffic: wi2: watchdog timeout wi3: watchdog timeout What could be the issue - is this purely a BIOS setup thing ? I.e. is the kernel right in saying that pcic is not configured. Should the kernel do so ? Can I force FreeBSD to do so ? Or is this a deeper issue. Note that both machines have 2 more wi0/wi1 Lynksys WMP11 cards. Dw From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 17:25:04 2003 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 3352E37B401 for ; Wed, 28 May 2003 17:25:04 -0700 (PDT) Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 576BF43F85 for ; Wed, 28 May 2003 17:24:56 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from foem (IDENT:chuckwebweaving.org@foem [10.11.0.2]) h4T0Otv7061684 for ; Thu, 29 May 2003 02:24:55 +0200 (CEST) (envelope-from dirkx@webweaving.org) Date: Thu, 29 May 2003 02:24:55 +0200 (CEST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@foem To: hackers@freebsd.org Message-ID: <20030529022139.Y22309-100000@foem> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Who configures the pci/pcmcia bridge 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 May 2003 00:25:04 -0000 Even when the BIOS is instructed to assign an IRQ - boot -v shows FreeBSD 5.0-RELEASE #0: Mon Apr 28 11:24:06 CEST 2003 dirkx@foem.leiden.webweaving.org:/usr/obj/usr/src/sys/WLEIDEN.93264 ... bios32: Found BIOS32 Service Directory header at 0xc00fdb00 bios32: Entry = 0xf5f23 (c00f5f23) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf5ec0+0x2ac pnpbios: Found PnP BIOS data at 0xc00fdb10 pnpbios: Entry = f0000:5159 Rev = 1.0 pci_open(1): mode 1 addr port (0x0cf8) is 0x80000050 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71008086) pcib0: at pcibus 0 on motherboard pci0: on pcib0 pci0: physical bus=0 ... found-> vendor=0x1180, dev=0x0475, revid=0x80 bus=0, slot=17, func=0 class=06-07-00, hdrtype=0x02, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x07 (1750 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 found-> vendor=0x1180, dev=0x0475, revid=0x80 bus=0, slot=18, func=0 class=06-07-00, hdrtype=0x02, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x07 (1750 ns) intpin=a, irq=255 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 3, range 32, base fedfb000, size 12, enabled and hence: pci_cfgintr: can't route an interrupt to 0:17 INTA pcic0: at device 17.0 on pci0 pcic0: PCI Memory allocated: 0x88000000 pci_cfgintr: can't route an interrupt to 0:17 INTA pcic0: No PCI interrupt routed, trying ISA. pcic0: Polling mode ... pccard0: on pcic0 pci_cfgintr: can't route an interrupt to 0:18 INTA pcic1: at device 18.0 on pci0 pcic1: PCI Memory allocated: 0x88001000 pci_cfgintr: can't route an interrupt to 0:18 INTA pcic1: No PCI interrupt routed, trying ISA. pcic1: Polling mode Which I suspect leads tot the wi0..wi4 watchdog time outs. Now -who- should ensure that an IRQ is configured ? Is this the kernel doing something wrong, or the board ? (Ricoh RL5C475 - OEM model, no version #). Dw From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 17:26:00 2003 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 7B98F37B401 for ; Wed, 28 May 2003 17:26:00 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC2A643F85 for ; Wed, 28 May 2003 17:25:59 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h4T0PwkA065799; Wed, 28 May 2003 18:25:58 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 28 May 2003 18:25:49 -0600 (MDT) Message-Id: <20030528.182549.08320992.imp@bsdimp.com> To: dirkx@webweaving.org From: "M. Warner Losh" In-Reply-To: <20030528235747.W22309-100000@foem> References: <20030528235747.W22309-100000@foem> X-Mailer: Mew version 2.1 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: pcic setup / wi0 timeout 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 May 2003 00:26:00 -0000 In message: <20030528235747.W22309-100000@foem> Dirk-Willem van Gulik writes: : pcic0: at device 18.0 on pci0 : pcic0: PCI Memory allocated: 0x88000000 : pcic0: No PCI interrupt routed, trying ISA. You lose. W/o a pci interrupt router, you can't use the cardbus bridge. Warner From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 17:29:31 2003 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 B7AAA37B401 for ; Wed, 28 May 2003 17:29:31 -0700 (PDT) Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABD3C43F3F for ; Wed, 28 May 2003 17:29:30 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from foem (IDENT:chuckwebweaving.org@foem [10.11.0.2]) h4T0TLv7061780; Thu, 29 May 2003 02:29:21 +0200 (CEST) (envelope-from dirkx@webweaving.org) Date: Thu, 29 May 2003 02:29:21 +0200 (CEST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@foem To: "M. Warner Losh" In-Reply-To: <20030528.182549.08320992.imp@bsdimp.com> Message-ID: <20030529022852.V22309-100000@foem> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hackers@freebsd.org Subject: Re: pcic setup / wi0 timeout 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 May 2003 00:29:32 -0000 On Wed, 28 May 2003, M. Warner Losh wrote: > In message: <20030528235747.W22309-100000@foem> > Dirk-Willem van Gulik writes: > : pcic0: at device 18.0 on pci0 > : pcic0: PCI Memory allocated: 0x88000000 > : pcic0: No PCI interrupt routed, trying ISA. > > You lose. W/o a pci interrupt router, you can't use the cardbus > bridge. Good - so who/what should set up a PCI router ? the Bios ? Dw From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 17:36:25 2003 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 EADD337B401 for ; Wed, 28 May 2003 17:36:25 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F64143FB1 for ; Wed, 28 May 2003 17:36:25 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h4T0aCkA065868; Wed, 28 May 2003 18:36:24 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 28 May 2003 18:36:03 -0600 (MDT) Message-Id: <20030528.183603.98561533.imp@bsdimp.com> To: dirkx@webweaving.org From: "M. Warner Losh" In-Reply-To: <20030529022852.V22309-100000@foem> References: <20030528.182549.08320992.imp@bsdimp.com> <20030529022852.V22309-100000@foem> X-Mailer: Mew version 2.1 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: pcic setup / wi0 timeout 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 May 2003 00:36:26 -0000 In message: <20030529022852.V22309-100000@foem> Dirk-Willem van Gulik writes: : > In message: <20030528235747.W22309-100000@foem> : > Dirk-Willem van Gulik writes: : > : pcic0: at device 18.0 on pci0 : > : pcic0: PCI Memory allocated: 0x88000000 : > : pcic0: No PCI interrupt routed, trying ISA. : > : > You lose. W/o a pci interrupt router, you can't use the cardbus : > bridge. : : Good - so who/what should set up a PCI router ? the Bios ? It depends. Really old machines routed interrupts to all PCI slots and assigned devices found there an interrupt. Newer old machines expect the PCI bridge driver of the OS to cope. Newer old machines provide a BIOS interface to route them (which we can use). Newer machines with ACPI have ACPI to do the routing. You might want to do a boot verbose, but I'm not sure how much that would help. PCIBIOS should have something like: bios32: Found BIOS32 Service Directory header at 0xc00f8270 bios32: Entry = 0xfd770 (c00fd770) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd770+0x11e pnpbios: Found PnP BIOS data at 0xc00f82c0 pnpbios: Entry = f0000:a95c Rev = 1.0 etc Warner From owner-freebsd-hackers@FreeBSD.ORG Wed May 28 17:43:28 2003 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 2220537B401 for ; Wed, 28 May 2003 17:43:28 -0700 (PDT) Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56E5243F75 for ; Wed, 28 May 2003 17:43:26 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from foem (IDENT:chuckwebweaving.org@foem [10.11.0.2]) h4T0hMv7062123; Thu, 29 May 2003 02:43:22 +0200 (CEST) (envelope-from dirkx@webweaving.org) Date: Thu, 29 May 2003 02:43:22 +0200 (CEST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@foem To: "M. Warner Losh" In-Reply-To: <20030528.183603.98561533.imp@bsdimp.com> Message-ID: <20030529024013.E22309-100000@foem> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hackers@freebsd.org Subject: Re: pcic setup / wi0 timeout 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 May 2003 00:43:28 -0000 On Wed, 28 May 2003, M. Warner Losh wrote: > It depends. Really old machines routed interrupts to all PCI slots > and assigned devices found there an interrupt. Newer old machines > expect the PCI bridge driver of the OS to cope. And I take it that if I start mucking myself by poke-ing a value into CB_PCI_INT_LINE that I really really shoot myself in the foot. > Newer old machines provide a BIOS interface to route them (which we can > use). Newer machines with ACPI have ACPI to do the routing. You might > want to do a boot verbose, but I'm not sure how much that would help. > PCIBIOS should have something like: Displayed is: bios32: Found BIOS32 Service Directory header at 0xc00fdb00 bios32: Entry = 0xf5f23 (c00f5f23) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf5ec0+0x2ac pnpbios: Found PnP BIOS data at 0xc00fdb10 pnpbios: Entry = f0000:5159 Rev = 1.0 A complete -v below. How does one distinghish/recognize from this who/what is the routing in this case ? Dw. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-RELEASE #0: Mon Apr 28 11:24:06 CEST 2003 dirkx@foem.leiden.webweaving.org:/usr/obj/usr/src/sys/WLEIDEN.93264 Preloaded elf kernel "/boot/kernel/kernel" at 0xc036a000. Calibrating clock(s) ... TSC clock: 199907648 Hz, i8254 clock: 1193205 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 199904646 Hz CPU: Pentium/P55C (199.90-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping = 4 Features=0x8001bf real memory = 33554432 (32 MB) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00391000 - 0x01ff7fff, 29782016 bytes (7271 pages) avail memory = 29007872 (27 MB) bios32: Found BIOS32 Service Directory header at 0xc00fdb00 bios32: Entry = 0xf5f23 (c00f5f23) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf5ec0+0x2ac pnpbios: Found PnP BIOS data at 0xc00fdb10 pnpbios: Entry = f0000:5159 Rev = 1.0 Other BIOS signatures found: Intel Pentium detected, installing workaround for F00F bug Initializing GEOMetry subsystem null: random: mem: npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x80000050 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71008086) pcib0: at pcibus 0 on motherboard pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x8086, dev=0x7100, revid=0x01 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x2200, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7110, revid=0x01 bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 0000fcf0, size 4, enabled found-> vendor=0x8086, dev=0x7111, revid=0x01 bus=0, slot=7, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 0000f800, size 5, enabled found-> vendor=0x8086, dev=0x7112, revid=0x01 bus=0, slot=7, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=9 map[90]: type 4, range 32, base 0000f0b0, size 4, enabled found-> vendor=0x8086, dev=0x7113, revid=0x01 bus=0, slot=7, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0003, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 32, base fedfc000, size 14, enabled map[14]: type 3, range 32, base fd800000, size 23, enabled map[18]: type 1, range 32, base fe000000, size 23, enabled found-> vendor=0x102b, dev=0x051a, revid=0x02 bus=0, slot=8, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0087, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 found-> vendor=0x1180, dev=0x0475, revid=0x80 bus=0, slot=17, func=0 class=06-07-00, hdrtype=0x02, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x07 (1750 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 found-> vendor=0x1180, dev=0x0475, revid=0x80 bus=0, slot=18, func=0 class=06-07-00, hdrtype=0x02, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x07 (1750 ns) intpin=a, irq=255 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 3, range 32, base fedfb000, size 12, enabled found-> vendor=0x1260, dev=0x3873, revid=0x01 bus=0, slot=19, func=0 class=02-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 3, range 32, base fedfa000, size 12, enabled found-> vendor=0x1260, dev=0x3873, revid=0x01 bus=0, slot=20, func=0 class=02-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 powerspec 2 supports D0 D1 D2 D3 current D0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcf0-0xfcff at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 ata0: mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI 00 00 ata0-slave: ATAPI 00 00 ata0: mask=03 stat0=50 stat1=00 ata0-master: ATA 01 a5 ata0: devices=01 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8 ata1: at 0x170 irq 15 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pci0: at device 8.0 (no driver attached) pci_cfgintr: can't route an interrupt to 0:17 INTA pcic0: at device 17.0 on pci0 pcic0: PCI Memory allocated: 0x88000000 pci_cfgintr: can't route an interrupt to 0:17 INTA pcic0: No PCI interrupt routed, trying ISA. pcic0: Polling mode pcic0: PCI Configuration space: 0x00: 0x04751180 0x02100003 0x06070080 0x00020000 0x10: 0x88000000 0x020000dc 0x00000000 0x00000000 0x20: 0x00000000 0x00000000 0x00000000 0x00000000 0x30: 0x00000000 0x00000000 0x00000000 0x07a00100 0x40: 0x010114ef 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x00000001 0x00000000 0x04630463 0x00000000 0x90: 0x00000000 0x00000000 0x00000000 0x00000000 0xa0: 0x00000010 0x00000000 0x00000000 0x00000000 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x010114ef 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0xfe0a0001 0xe0: 0x24c04000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 pccard0: on pcic0 pci_cfgintr: can't route an interrupt to 0:18 INTA pcic1: at device 18.0 on pci0 pcic1: PCI Memory allocated: 0x88001000 pci_cfgintr: can't route an interrupt to 0:18 INTA pcic1: No PCI interrupt routed, trying ISA. pcic1: Polling mode pcic1: PCI Configuration space: 0x00: 0x04751180 0x02100003 0x06070080 0x00020000 0x10: 0x88001000 0x020000dc 0x00000000 0x00000000 0x20: 0x00000000 0x00000000 0x00000000 0x00000000 0x30: 0x00000000 0x00000000 0x00000000 0x07a00100 0x40: 0x010114ef 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x00000000 0x00000000 0x04630463 0x00000000 0x90: 0x00000000 0x00000000 0x00000000 0x00000000 0xa0: 0x00000010 0x00000000 0x00000000 0x00000000 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x010114ef 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0xfe190001 0xe0: 0x24c04000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 pccard1: on pcic1 wi0: mem 0xfedfb000-0xfedfbfff irq 11 at device 19.0 on pci0 wi0: 802.11 address: 00:06:25:a7:a8:46 wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary 1.01.01, Station 1.05.06 wi0: wi_has_wep = 1 wi0: bpf attached wi1: mem 0xfedfa000-0xfedfafff irq 9 at device 20.0 on pci0 wi1: 802.11 address: 00:06:25:a7:a9:42 wi1: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi1: Intersil Firmware: Primary 1.01.01, Station 1.05.06 wi1: wi_has_wep = 1 wi1: bpf attached ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 pnpbios: 13 devices, largest 82 bytes PNP0a03: adding fixed io range 0xcf8-0xcff, size=0x8, align=0x1 PNP0a03: adding fixed io range 0xe6-0xe6, size=0x1, align=0x1 PNP0a03: adding io range 0x80-0x80, size=0x1, align=0 PNP0a03: adding io range 0x4d0-0x4d1, size=0x2, align=0 pnpbios: handle 0 device ID PNP0a03 (030ad041) PNP0800: adding fixed io range 0x61-0x61, size=0x1, align=0x1 pnpbios: handle 1 device ID PNP0800 (0008d041) PNP0c01: adding memory range 0-0x9ffff, size=0xa0000, align=0 PNP0c01: adding memory range 0xe0000-0xfffff, size=0x20000, align=0 PNP0c01: adding fixed memory32 range 0x100000-0x1ffffff, size=0x1f00000 PNP0c01: adding fixed memory32 range 0xfffe0000-0xffffffff, size=0x20000 PNP0c01: adding fixed io range 0x26-0x27, size=0x2, align=0x1 PNP0c01: adding fixed io range 0xf080-0xf08f, size=0x10, align=0x1 PNP0c01: adding fixed io range 0xf0c0-0xf0ff, size=0x40, align=0x1 PNP0c01: adding fixed io range 0xf0b0-0xf0bf, size=0x10, align=0x1 pnpbios: handle 2 device ID PNP0c01 (010cd041) PNP0303: adding fixed io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding fixed io range 0x64-0x64, size=0x1, align=0x1 PNP0303: adding irq mask 0x2 pnpbios: handle 3 device ID PNP0303 (0303d041) PNP0c04: adding fixed io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: adding irq mask 0x2000 pnpbios: handle 4 device ID PNP0c04 (040cd041) PNP0200: adding io range 0-0xf, size=0x10, align=0 PNP0200: adding io range 0x81-0x8f, size=0xf, align=0 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0 PNP0200: adding dma mask 0x10 pnpbios: handle 5 device ID PNP0200 (0002d041) PNP0000: adding io range 0x20-0x21, size=0x2, align=0 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0 PNP0000: adding irq mask 0x4 pnpbios: handle 6 device ID PNP0000 (0000d041) PNP0100: adding io range 0x40-0x43, size=0x4, align=0 PNP0100: adding irq mask 0x1 pnpbios: handle 7 device ID PNP0100 (0001d041) PNP0b00: adding io range 0x70-0x71, size=0x2, align=0 PNP0b00: adding irq mask 0x100 pnpbios: handle 8 device ID PNP0b00 (000bd041) PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 PNP0501: adding irq mask 0x10 pnpbios: handle 10 device ID PNP0501 (0105d041) pnpbios: handle 11 device ID PNP0501 (0105d041) pnpbios: handle 12 device ID PNP0400 (0004d041) pnpbios: handle 13 device ID PNP0700 (0007d041) sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: