From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 17 00:07:11 2005 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 426E416A4CE for ; Sun, 17 Apr 2005 00:07:11 +0000 (GMT) Received: from daedalus.desk.pl (daedalus.desk.pl [62.233.238.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6ED043D31 for ; Sun, 17 Apr 2005 00:07:10 +0000 (GMT) (envelope-from creep@daedalus.desk.pl) Received: from localhost (localhost [127.0.0.1]) by daedalus.desk.pl (Postfix) with ESMTP id 393E6366712 for ; Sun, 17 Apr 2005 02:04:27 +0200 (CEST) Received: from daedalus.desk.pl ([127.0.0.1]) by localhost (daedalus [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11774-09 for ; Sun, 17 Apr 2005 02:04:26 +0200 (CEST) Received: by daedalus.desk.pl (Postfix, from userid 1023) id 2069536663F; Sun, 17 Apr 2005 02:04:26 +0200 (CEST) Date: Sun, 17 Apr 2005 02:04:26 +0200 From: Marcin To: freebsd-hackers@freebsd.org Message-ID: <20050417000426.GA13132@daedalus.desk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Antivirus: Skaner Antywirusowy DESK.pl Subject: Determine LD_PRELOAD'ed symbols. (UPDATE) 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, 17 Apr 2005 00:07:11 -0000 Hello Hackers!, My first post got stuck waiting for moderator, and after some investigation I'd like to ask a bit more substantial question on the topic anyway: With program A ptrace'ing program B which runs with LD_PRELOAD'ed library libC.so, how can i find from program A where functions from libC are located in B's memory? The dump generated with LD_DUMP_REL_PRE shows only symbols which already were in B, but were masked by LD_PRELOAD'ing libC.so, does it mean that other symbols exported by libC.so are unaccessible from B? If not, where to search for their locations? Will sections in B and libC.so give any hints? Pointers to doc/code (but please something smaller than src/libexec/rtld-elf ;>) welcome. -- m. Brain power of a glass of water. From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 16 23:31:39 2005 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 B19DA16A4CE for ; Sat, 16 Apr 2005 23:31:39 +0000 (GMT) Received: from daedalus.desk.pl (daedalus.desk.pl [62.233.238.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B69D43D2D for ; Sat, 16 Apr 2005 23:31:39 +0000 (GMT) (envelope-from creep@daedalus.desk.pl) Received: from localhost (localhost [127.0.0.1]) by daedalus.desk.pl (Postfix) with ESMTP id A3916366646 for ; Sun, 17 Apr 2005 01:28:56 +0200 (CEST) Received: from daedalus.desk.pl ([127.0.0.1]) by localhost (daedalus [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08479-03 for ; Sun, 17 Apr 2005 01:28:55 +0200 (CEST) Received: by daedalus.desk.pl (Postfix, from userid 1023) id 636B436663F; Sun, 17 Apr 2005 01:28:55 +0200 (CEST) Date: Sun, 17 Apr 2005 01:28:55 +0200 From: Marcin To: freebsd-hackers@freebsd.org Message-ID: <20050416232855.GA8698@daedalus.desk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Antivirus: Skaner Antywirusowy DESK.pl X-Mailman-Approved-At: Sun, 17 Apr 2005 12:11:05 +0000 Subject: Determine location of LD_PRELOAD'ed shared libraries/functions. 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: Sat, 16 Apr 2005 23:31:39 -0000 Hello Hackers, I'd like to find locations of functions exported by shared lib loaded into the running ptrace'd process via LD_PRELOAD. I want do determine this from tracing process. For shared libraries linked with a program i can just open the program file and search for relocation sections, which eventually point to the plt function entries. My problem is that i cannot figure out how to start searching for symbols which are loaded with LD_PRELOAD. I can see where the library is mapped in /proc/*/map (isn't there a better, less freebsd-specific place to search for this info?) but I'm not quite sure how to interpret the mmapped pages. Searching Elf doc's just makes me run in circles; usually the LD_PRELOAD option is just mentioned as it was obvious; I't isn't quite. Sections describing program memory image are in program file. LD_PRELOAD'ed lib is only in the memory, to which programs sections do not apply. Libraries sections can't know to what address they will be mmapped to, so where to search? Program has relocation entries, but there is no spare space there for something unexpected like LD_PRELOADed library (?) Please point me to right direction, because i've got only one idea left: grep dynamic loader for LD_PRELOAD ;). -- m. Brain power of a glass of water. From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 17 11:34:57 2005 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 2C7DD16A4CE for ; Sun, 17 Apr 2005 11:34:57 +0000 (GMT) Received: from relay.pair.com (relay00.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 6065343D39 for ; Sun, 17 Apr 2005 11:34:56 +0000 (GMT) (envelope-from andrew@binturong.us) Received: (qmail 11982 invoked from network); 17 Apr 2005 11:34:55 -0000 Received: from unknown (HELO ?83.245.20.197?) (unknown) by unknown with SMTP; 17 Apr 2005 11:34:55 -0000 X-pair-Authenticated: 83.245.20.197 Message-ID: <426249D0.6010504@binturong.us> Date: Sun, 17 Apr 2005 12:34:40 +0100 From: Andrew Tappert User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 17 Apr 2005 12:11:05 +0000 Subject: linux call_usermodehelper equivalent in freebsd? 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, 17 Apr 2005 11:34:57 -0000 I tried asking about this on freebsd-questions, but I didn't get a response and I gather this is a more appropriate forum. This is a question about FreeBSD kernel (module) programming. Is there an equivalent in FreeBSD to the Linux kernel function 'call_usermodehelper' which wraps execve to do as its name suggests, call a user mode helper program? If there is, what is it? If not, can some kind person please point me to some code in the kernel--if there is any--which does something similar (i.e., exec's a usermode program from the kernel), so I may see how it's properly done? In what context is it ok just to do the exec? How do I set it up? Thanks, Andrew From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 17 12:25:21 2005 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 4C86816A4CE for ; Sun, 17 Apr 2005 12:25:21 +0000 (GMT) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1EF343D41 for ; Sun, 17 Apr 2005 12:25:20 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (wlan032024.uni-rostock.de [139.30.32.24]) by hydra.bec.de (Postfix) with ESMTP id EE3B835707 for ; Sun, 17 Apr 2005 14:25:18 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1001) id C53A57D03; Sun, 17 Apr 2005 14:25:13 +0200 (CEST) Date: Sun, 17 Apr 2005 14:25:13 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Message-ID: <20050417122513.GA3106@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <426249D0.6010504@binturong.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <426249D0.6010504@binturong.us> User-Agent: Mutt/1.5.9i Subject: Re: linux call_usermodehelper equivalent in freebsd? 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, 17 Apr 2005 12:25:21 -0000 On Sun, Apr 17, 2005 at 12:34:40PM +0100, Andrew Tappert wrote: > Is there an equivalent in FreeBSD to the Linux kernel function > 'call_usermodehelper' which wraps execve to do as its name suggests, > call a user mode helper program? BSD kernels normally don't try to execute helper programs. Setting up a process from scratch is not trivial work. Can you give us for information on what you want to do? Maybe there is a better solution available. Joerg > > If there is, what is it? > > If not, can some kind person please point me to some code in the > kernel--if there is any--which does something similar (i.e., exec's a > usermode program from the kernel), so I may see how it's properly done? > In what context is it ok just to do the exec? How do I set it up? > > Thanks, > Andrew > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 17 12:47:35 2005 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 238C616A4CE for ; Sun, 17 Apr 2005 12:47:35 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97B4043D54 for ; Sun, 17 Apr 2005 12:47:34 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so843349rnf for ; Sun, 17 Apr 2005 05:47:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HrsJD72JD6UuJQTTBQlnO/gFx9zPr1+lGeBY0xYN4qPiANsDDPaFOftGa1P2mGuTF4QC2MTl1wC+3tfO07vew62GxQCpnqFlmW6tDmdiUyd+kWiB3lLZfj2VUsHg4vcSZGk9lEovRL+hybBQ45+C90uijM+boYTEATitgtMquIg= Received: by 10.38.79.74 with SMTP id c74mr2844135rnb; Sun, 17 Apr 2005 05:47:34 -0700 (PDT) Received: by 10.38.209.22 with HTTP; Sun, 17 Apr 2005 05:47:34 -0700 (PDT) Message-ID: <84dead720504170547534b23e5@mail.gmail.com> Date: Sun, 17 Apr 2005 12:47:34 +0000 From: Joseph Koshy To: Marcin In-Reply-To: <20050416232855.GA8698@daedalus.desk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050416232855.GA8698@daedalus.desk.pl> cc: freebsd-hackers@freebsd.org Subject: Re: Determine location of LD_PRELOAD'ed shared libraries/functions. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joseph Koshy List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2005 12:47:35 -0000 > Please point me to right direction, because i've got only one=20 > idea left: grep dynamic loader for LD_PRELOAD ;). Doesn't dlsym() with handle RTLD_DEFAULT work? --=20 FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 17 14:00:28 2005 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 7947116A4F4; Sun, 17 Apr 2005 14:00:28 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A6E943D31; Sun, 17 Apr 2005 14:00:25 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3HE2rPZ069113; Sun, 17 Apr 2005 08:02:53 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42626B36.1090204@samsco.org> Date: Sun, 17 Apr 2005 07:57:10 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org References: <200504080220.57899.max@love2party.net> In-Reply-To: <200504080220.57899.max@love2party.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: monthly@freebsd.org Subject: REMINDER! Call for FreeBSD status reports 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, 17 Apr 2005 14:00:28 -0000 All, This is a reminder that status reports are due. We are going to extend the deadline until the 20th to encourage people to submit a few more reports. If you have any projects that you've been working on in the past 3 months that are interesting and you would like to share, please submit a report as soon as possible. The new web form from Julian makes it incredibly easy to generate a submission without having to know a thing about XML. The link for this is at: http://www.freebsd.org/cgi/monthly.cgi So, please submit your reports to monthly@freebsd.org by the 20th. Thanks, Scott Long, Max Laier, Tom Rhodes Max Laier wrote: > All, > > It's time again for some recapitulation of your FreeBSD activities of the last > months. In order to not collided with the preparation of the 5.4 release we > extended the cycle from bi-monthly to three months, so this one is open for > anything that happend in 2005 until now. Submissions are due by April 15 to > monthly@freebsd.org > > As always, reports about every FreeBSD related activity of the past months and > coming weeks are welcome. In the past there was some focus on technical > issues. In order to turn this into a more complete PR-vehicle, we highly > encourage and welcome reports on non-technical matters as well. > > If you are yet unfamiliar with the status-reports, please take a look at the > past reports: http://www.FreeBSD.org/news/status/ > > To support you in the process of fitting your report into the xml-template > (available from: http://www.freebsd.org/news/status/report-sample.xml for > those who still prefer a plain old text editor) Julian Elischer came up with > the idea and prototype to have a web based form. Many thanks for that work. > The cgi-script is being reviewed on freebsd-www now and will be linked to > from http://www.freebsd.org/news/status/ shortly. > > The new features from last time (categories and task-list) will be available, > again. As a reminder the available categories are listed bellow. Please > feel free to suggest additional entries: > > proj - Projects (non-specific) > docs - Documentation > kern - Kernel > arch - Architectures > ports - Ports > vendor - Vendor / 3rd party software > misc - Miscellaneous > > Submissions are due on April 15. Thanks a lot, and we are hoping for a big > turn-out. > From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 17 15:32:29 2005 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 E68FB16A4CE for ; Sun, 17 Apr 2005 15:32:29 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEFC843D2D for ; Sun, 17 Apr 2005 15:32:29 +0000 (GMT) (envelope-from mhersant@comcast.net) Received: from [192.168.2.102] (c-24-22-136-36.hsd1.wa.comcast.net[24.22.136.36]) by comcast.net (rwcrmhc11) with ESMTP id <2005041715322901300kdt82e>; Sun, 17 Apr 2005 15:32:29 +0000 Message-ID: <42628196.4070608@comcast.net> Date: Sun, 17 Apr 2005 08:32:38 -0700 From: Matt User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Making multiple jails 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, 17 Apr 2005 15:32:30 -0000 I'd like to create five jails on one machine. Is it possible to make them all at the same time? I'm only familiary with creating them individually (DESTDIR=/foo/bar). Thanks much. From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 17 17:14:13 2005 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 BBEB416A4CE for ; Sun, 17 Apr 2005 17:14:13 +0000 (GMT) Received: from mxsf10.cluster1.charter.net (mxsf10.cluster1.charter.net [209.225.28.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5169343D55 for ; Sun, 17 Apr 2005 17:14:13 +0000 (GMT) (envelope-from c0ldbyte@myrealbox.com) Received: from mxip14.cluster1.charter.net (mxip14a.cluster1.charter.net [209.225.28.144])j3HHEB34017445 for ; Sun, 17 Apr 2005 13:14:12 -0400 Received: from 24.247.253.134.gha.mi.chartermi.net (HELO eleanor.us1.wmi.uvac.net) (24.247.253.134) by mxip14.cluster1.charter.net with ESMTP; 17 Apr 2005 13:14:11 -0400 X-Ironport-AV: i="3.92,106,1112587200"; d="scan'208"; a="228360588:sNHT12717032" Date: Sun, 17 Apr 2005 13:14:08 -0400 (EDT) From: c0ldbyte To: freebsd-hackers@freebsd.org In-Reply-To: <42628196.4070608@comcast.net> Message-ID: <20050417131113.G1373@eleanor.us1.wmi.uvac.net> References: <42628196.4070608@comcast.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: Making multiple jails 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, 17 Apr 2005 17:14:13 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 17 Apr 2005, Matt wrote: > I'd like to create five jails on one machine. Is it possible to make them > all at the same time? I'm only familiary with creating them individually > (DESTDIR=/foo/bar). Thanks much. Try: DESTDIR=/foo/bar/jail1 ; DESTDIR=/foo/bar2 You can use those at the same time but you can redo the make installworld and hierachy with each one seperately. Best of luck, --c0ldbyte - -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) Comment: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF7DF979F Comment: Fingerprint = D1DC 0AA4 1C4E EAD4 24EB 7E77 B261 50BA F7DF 979F iD8DBQFCYpljsmFQuvffl58RAqUtAJ0UGYR80EdsVnJIAIpSUAV2miCU3ACfYY1a dE965CVMeFadvnnvhzU+M0U= =DaUB -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 17 23:08:34 2005 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 2082816A4CE; Sun, 17 Apr 2005 23:08:34 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7378543D1D; Sun, 17 Apr 2005 23:08:33 +0000 (GMT) (envelope-from wigglesworth02@comcast.net) Received: from [192.168.2.55] (c-24-125-177-237.hsd1.va.comcast.net[24.125.177.237]) by comcast.net (sccrmhc11) with SMTP id <2005041723083201100hmlnbe>; Sun, 17 Apr 2005 23:08:32 +0000 From: Martes G Wigglesworth To: Hackers-list-bsd , Norfolk Unix Users' Group , freebsd-questions , Bluetooth Content-Type: text/plain Message-Id: <1113779315.669.266.camel@Mobil1.276NET> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 17 Apr 2005 19:08:35 -0400 Content-Transfer-Encoding: 7bit Subject: Possible Kernel patch/hack needed, for use of Ambicom BT2000 CF adapter... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: wigglesworth02@comcast.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2005 23:08:34 -0000 I am having difficulties using my CF/PCCard Bluetooth adapter from Ambicom. I have found similar error messages, associated with an individual that was attempting to get his palm to sync with BSD, back in 2003. The respondent to the individual's inquiry, indicated a patch, and the subsequent response was that the patch worked. I am unable to locate the archived mail, via google, however, I am new to patching, and have not yet been able to figure out where I might do so. I get continuous loop of errors when attempting to use the rc.bluetooth script, or hcseriald with the correct ttyd4 device. Can anyone indicate where I might find a way to patch this problem, or if I may be able to edit some src, that has to do with this device interface driver? (sio4) I get the following in my dmesg output while executing the following: >hcseriald -d -f /dev/ttyd4 -n sio4 -s 115200 >ng_h4_input: sio4 - ignoring unknown packet type=0 >ng_h4_input: sio4 - ignoring unknown packet type=0x80 >dmesg output for the connection renders the following: >sio4: at port 0x3e8-0x3ef irq 11 >function 0 config 2 on pccard1 >sio4: type 16550A >sio4: unable to activate interrupt in fast mode - using normal mode I am stuck, and unable to get any farther than the start of hcseriald. I am unable to use my bluetooth at all, because I am unable to even find a good howto for using hcseriald or even how I am supposed to connect the interface even if I can use hcseriald. Nothing ever happens other than the output listed above. my system is as follows: FreeBSD 5.3-Release Bluetooth CF Adapter: Ambicom BT2000 via PCCard CF adapter Asus M6BN Please give some direction. I am at a loss. From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 18 07:48:39 2005 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 0569816A4CE for ; Mon, 18 Apr 2005 07:48:39 +0000 (GMT) Received: from mail.emict.com (brig.emict.com [212.90.172.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AE5143D45 for ; Mon, 18 Apr 2005 07:48:38 +0000 (GMT) (envelope-from andrit@ukr.net) Received: from [10.0.0.232] (unknown [10.0.0.232]) by mail.emict.com (Postfix) with ESMTP id B66F8330EF; Mon, 18 Apr 2005 10:48:36 +0300 (EEST) From: Andriy Tkachuk Organization: eMICT To: freebsd-hackers@freebsd.org User-Agent: KMail/1.7 References: <426173A4.90200@gmail.com> <20050416170356.E70414@eleanor.us1.wmi.uvac.net> In-Reply-To: <20050416170356.E70414@eleanor.us1.wmi.uvac.net> MIME-Version: 1.0 Content-Disposition: inline Date: Mon, 18 Apr 2005 10:48:36 +0300 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200504181048.36636.andrit@ukr.net> cc: c0ldbyte cc: "M. Parsons" Subject: Re: ext2 drives under 5.3 not umounting on reboots 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, 18 Apr 2005 07:48:39 -0000 I've had the same problem on 5.3. now on my FreeBSD 5.4-RC2 #0: Fri Apr 15 11:28:48 EEST 2005 i386 it seems that problem gone. On Sunday 17 April 2005 00:07, c0ldbyte wrote: > On Sat, 16 Apr 2005, M. Parsons wrote: > > > I have a ext2 linux partition mounted under /linux via the fstab line: > > > > /dev/ad2s1 /linux ext2fs rw 1 2 > > > > It will automount on bootup, but if I do a reboot or shutdown -h now, it > > doesnt get umounted properly. In fact, if this /linux is mounted, then /, > > /usr, /var, and /tmp (all seperate ufs slices on another hard drive) also get > > tainted during a reboot. And on the next startup I get the good ole: > > WARNING: /usr was not properly dismounted, leaving me to fsck the drives in > > single mode (which sucks, as the fbsd machine is a headless NAT machine). > > Running fsck in single mode does fix everything. > > > > So whats going on here? reboot aint properly umounting partitions, and fsck > > doesnt seem to be properly running during bootup if it detects tainted > > filesystems. > > > > Any ideas? > > > > Freebsd 5.3 SMP kernel. > > Try this line: > /dev/ad2s1 /linux ext2fs rw 0 0 > > But remember the ext2 code has been buggy for a while and is not allways > a good choice to try and do writes on it. Might be a better choice to > change rw to ro and to also check that drive/partition for errors with > its original fsck to fix any errors if there is any then it will most > likely mount properly and umount properly. > > Best of luck, > --c0ldbyte > From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 18 09:20:04 2005 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 1847016A4CE for ; Mon, 18 Apr 2005 09:20:04 +0000 (GMT) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFC6643D55 for ; Mon, 18 Apr 2005 09:20:01 +0000 (GMT) (envelope-from konstantin.belousov@zoral.com.ua) Received: from deviant.zoral.local (root@kostik.zoral.local [10.1.1.38]) by fw.zoral.com.ua (8.13.1/8.13.1) with ESMTP id j3I9Kb1n071321 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 18 Apr 2005 12:20:37 +0300 (EEST) (envelope-from konstantin.belousov@zoral.com.ua) Received: from deviant.zoral.local (kostik@localhost [127.0.0.1]) by deviant.zoral.local (8.13.3/8.13.3) with ESMTP id j3I9KdUT031763 for ; Mon, 18 Apr 2005 12:20:39 +0300 (EEST) (envelope-from konstantin.belousov@zoral.com.ua) Received: (from kostik@localhost) by deviant.zoral.local (8.13.3/8.13.3/Submit) id j3I9KdXj031762 for freebsd-hackers@freebsd.org; Mon, 18 Apr 2005 12:20:39 +0300 (EEST) (envelope-from konstantin.belousov@zoral.com.ua) X-Authentication-Warning: deviant.zoral.local: kostik set sender to konstantin.belousov@zoral.com.ua using -f Date: Mon, 18 Apr 2005 12:20:39 +0300 From: Kostik Belousov To: freebsd-hackers@freebsd.org Message-ID: <20050418092038.GB984@deviant.zoral.local> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.82/837/Sun Apr 17 18:25:32 2005 on fw.zoral.com.ua X-Virus-Status: Clean Subject: sigprocmask and fork 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, 18 Apr 2005 09:20:04 -0000 --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I come across the following problem: after fork(), the 5-STABLE system sets the child process blocked signal mask to 0 (let us account single-threaded processes only). I was under impression that signal mask shall be inherited by the child process (according to SUSv3 and man fork). Inheritance _was_ the behaviour of 4-STABLE (there, p_sigmask belongs to struct proc and placed in the copied-on-fork part of the structure) and also seen on other UNIXes (e.g. Solaris). After googling, I found the comment by Dong Xuezhang in http://lists.freebsd.org/pipermail/freebsd-threads/2005-February/002899.html where he said that "Actually fork() do not copy the properties of signal mask". I confirm that fork does not copy mask, but why ? Attached is the program that illustrates this issue on pooma% uname -a ~/work/bsd/sigmask FreeBSD pooma.home 5.4-STABLE FreeBSD 5.4-STABLE #32: Fri Apr 15 22:16:43 EEST 2005 root@pooma.home:/usr/obj/usr/src/sys/POOMA i386 On unpatched 5-STABLE, the child process reports SIGUSR2 immediately after start, despite parent blocked SIGUSR2 before forking. It seems that needs of thread_schedule_upcall() to zero sigmask interfere with the needs of the fork1(). I propose the trivial patch (against 5-STABLE) to fix the problems. It handles td_sigmask in the way similar to td_sigstk, that is also zeroed on _upcall(), as was done by davidxu at kern/kern_fork.c:1.209 rev. Index: kern/kern_fork.c =================================================================== RCS file: /usr/local/arch/ncvs/src/sys/kern/kern_fork.c,v retrieving revision 1.234.2.8 diff -U5 -r1.234.2.8 kern_fork.c --- kern/kern_fork.c 27 Feb 2005 02:36:39 -0000 1.234.2.8 +++ kern/kern_fork.c 18 Apr 2005 08:58:50 -0000 @@ -470,10 +470,11 @@ __rangeof(struct thread, td_startcopy, td_endcopy)); bcopy(&td->td_ksegrp->kg_startcopy, &kg2->kg_startcopy, __rangeof(struct ksegrp, kg_startcopy, kg_endcopy)); td2->td_sigstk = td->td_sigstk; + td2->td_sigmask = td->td_sigmask; /* * Duplicate sub-structures as needed. * Increase reference counts on shared objects. */ Thanks for attention, Kostik Belousov. --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="sigmask1.cc" #include #include #include #include #include #include extern "C" void sigusr2_handler(int signo) { static const char msg[] = "SIGUSR2\n"; write(2, msg, sizeof(msg) - 1); _exit(0); } int main(int argc, char *argv[]) { struct sigaction sa; memset(&sa, 0, sizeof(sa)); sa.sa_handler = sigusr2_handler; sigaction(SIGUSR2, &sa, NULL); sigset_t mask; sigemptyset(&mask); sigaddset(&mask, SIGUSR2); sigprocmask(SIG_BLOCK, &mask, NULL); pid_t child = fork(); if (child == 0) { raise(SIGUSR2); printf("sleeping\n"); sleep(10); printf("enabling SIGUSR2\n"); sigprocmask(SIG_UNBLOCK, &mask, NULL); while (true) ; } int status; wait(&status); return 0; } --yrj/dFKFPuw6o+aM-- From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 18 09:25:52 2005 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 28D4616A4CE; Mon, 18 Apr 2005 09:25:52 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F14B43D4C; Mon, 18 Apr 2005 09:25:51 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 5A4451F007; Mon, 18 Apr 2005 11:25:50 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id 3D63F6746; Mon, 18 Apr 2005 11:25:50 +0200 (CEST) Date: Mon, 18 Apr 2005 11:25:50 +0200 From: Marc Olzheim To: Brian Fundakowski Feldman Message-ID: <20050418092550.GA97539@stack.nl> References: <20050415050821.GO981@green.homeunix.org> <20050415132108.GC85922@stack.nl> <20050415150708.GP981@green.homeunix.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <20050415150708.GP981@green.homeunix.org> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i cc: Marc Olzheim cc: hackers@freebsd.org cc: current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 18 Apr 2005 09:25:52 -0000 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 15, 2005 at 11:07:08AM -0400, Brian Fundakowski Feldman wrote: > > Is this supposed to fix kern/79208 ? >=20 > Yes, it does; would you like to try a more recent version of the patch? > It's actually against -STABLE, but it needs to be tested in -CURRENT if > it's going ot try to make it into 5.x (or hopefully 5.4-RELEASE). >=20 > See: Ok, I'll try it out on -CURRENT then. Marc --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCY30eezjnobFOgrERAqU3AJ99ygotgVaNgz9dOdxZGbmKTpVdigCfT+4V ytpYZ0f+780gZb7pm0lhnoM= =2N4b -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK-- From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 18 11:32:40 2005 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 6156E16A4CE for ; Mon, 18 Apr 2005 11:32:40 +0000 (GMT) Received: from mxsf33.cluster1.charter.net (mxsf33.cluster1.charter.net [209.225.28.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id D68B343D46 for ; Mon, 18 Apr 2005 11:32:39 +0000 (GMT) (envelope-from c0ldbyte@myrealbox.com) Received: from mxip08.cluster1.charter.net (mxip08a.cluster1.charter.net [209.225.28.138])j3IBWcEU025140 for ; Mon, 18 Apr 2005 07:32:38 -0400 Received: from 24.247.253.134.gha.mi.chartermi.net (HELO eleanor.us1.wmi.uvac.net) (24.247.253.134) by mxip08.cluster1.charter.net with ESMTP; 18 Apr 2005 07:32:38 -0400 X-Ironport-AV: i="3.92,109,1112587200"; d="scan'208"; a="863007995:sNHT13658580" Date: Mon, 18 Apr 2005 07:32:37 -0400 (EDT) From: c0ldbyte To: Andriy Tkachuk In-Reply-To: <200504181046.35243.ant@emict.com> Message-ID: <20050418073040.X36802@eleanor.us1.wmi.uvac.net> References: <426173A4.90200@gmail.com> <20050416170356.E70414@eleanor.us1.wmi.uvac.net> <200504181046.35243.ant@emict.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-hackers@freebsd.org cc: "M. Parsons" Subject: Re: ext2 drives under 5.3 not umounting on reboots 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, 18 Apr 2005 11:32:40 -0000 On Mon, 18 Apr 2005, Andriy Tkachuk wrote: > I've had the same problem on 5.3. > now on my FreeBSD 5.4-RC2 #0: Fri Apr 15 11:28:48 EEST 2005 i386 > it seems that problem gone. I would advise once more changing the "Dump" & "Pass#" number fields to "0" for both as I showed on the line below, you would have found out that was causing if any most of your problem with your filesystems being mounted/unmounted properly. > On Sunday 17 April 2005 00:07, c0ldbyte wrote: >> On Sat, 16 Apr 2005, M. Parsons wrote: >> >>> I have a ext2 linux partition mounted under /linux via the fstab line: >>> >>> /dev/ad2s1 /linux ext2fs rw 1 2 >>> >>> It will automount on bootup, but if I do a reboot or shutdown -h now, it >>> doesnt get umounted properly. In fact, if this /linux is mounted, then /, >>> /usr, /var, and /tmp (all seperate ufs slices on another hard drive) also get >>> tainted during a reboot. And on the next startup I get the good ole: >>> WARNING: /usr was not properly dismounted, leaving me to fsck the drives in >>> single mode (which sucks, as the fbsd machine is a headless NAT machine). >>> Running fsck in single mode does fix everything. >>> >>> So whats going on here? reboot aint properly umounting partitions, and fsck >>> doesnt seem to be properly running during bootup if it detects tainted >>> filesystems. >>> >>> Any ideas? >>> >>> Freebsd 5.3 SMP kernel. >> >> Try this line: >> /dev/ad2s1 /linux ext2fs rw 0 0 >> >> But remember the ext2 code has been buggy for a while and is not allways >> a good choice to try and do writes on it. Might be a better choice to >> change rw to ro and to also check that drive/partition for errors with >> its original fsck to fix any errors if there is any then it will most >> likely mount properly and umount properly. >> >> Best of luck, >> --c0ldbyte >> > -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 17 16:26:23 2005 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 4C2AD16A4D2 for ; Sun, 17 Apr 2005 16:26:23 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id C39E243D1F for ; Sun, 17 Apr 2005 16:26:22 +0000 (GMT) (envelope-from franklinchef@gmail.com) Received: by wproxy.gmail.com with SMTP id 49so875601wri for ; Sun, 17 Apr 2005 09:26:22 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:user-agent:x-accept-language:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:from; b=WIVxvPdtpGmEo5sZnn6jJzLsanWAFeX6m21jGPxVOY76Ouex3X8+jFWmiXdnkgEKzcdrZ45gPzQ1X8Pnb8JWTjETsnZOXoue9ypx2uGbthfTfmXktvFBWdrPB6F1WUfXBAqLpyfHa4iRw21ZsSkE/4VhYihb99hyX46PDlVt8vk= Received: by 10.54.20.75 with SMTP id 75mr613006wrt; Sun, 17 Apr 2005 09:26:22 -0700 (PDT) Received: from ?192.168.5.140? ([24.37.150.112]) by mx.gmail.com with ESMTP id 10sm1411447wrl.2005.04.17.09.26.21; Sun, 17 Apr 2005 09:26:22 -0700 (PDT) Message-ID: <42628E25.8010008@gmail.com> Date: Sun, 17 Apr 2005 12:26:13 -0400 User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matt References: <42628196.4070608@comcast.net> In-Reply-To: <42628196.4070608@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit From: "Franklin Chef(news)" X-Mailman-Approved-At: Mon, 18 Apr 2005 11:59:03 +0000 cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Making multiple jails 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, 17 Apr 2005 16:26:23 -0000 Matt wrote: > I'd like to create five jails on one machine. Is it possible to make > them all at the same time? I'm only familiary with creating them > individually (DESTDIR=/foo/bar). Thanks much. > _______________________________________________ > 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" > No problem, you can run multiple jail at the same time. All you have to do is to create different jail directories and edit rc.conf like this: jail_enable="YES" jail_list="jail1 jail2 jail3" jail_jail1_hostname="jail1.jail.org" jail_jail1_ip="192.168.4.100" ... jail_jail2_hostname="jail2.jail.org" jail_jail2_ip="192.168.4.101" ... jail_jail3_hostname="jail3.jail.org" jail_jail3_ip="192.168.4.102" ... From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 18 12:59:00 2005 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 8421016A4CE for ; Mon, 18 Apr 2005 12:59:00 +0000 (GMT) Received: from mxsf30.cluster1.charter.net (mxsf30.cluster1.charter.net [209.225.28.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id C84D943D39 for ; Mon, 18 Apr 2005 12:58:59 +0000 (GMT) (envelope-from c0ldbyte@myrealbox.com) Received: from mxip15.cluster1.charter.net (mxip15a.cluster1.charter.net [209.225.28.145])j3ICwwFM023820 for ; Mon, 18 Apr 2005 08:58:58 -0400 Received: from 24.247.253.134.gha.mi.chartermi.net (HELO eleanor.us1.wmi.uvac.net) (24.247.253.134) by mxip15.cluster1.charter.net with ESMTP; 18 Apr 2005 08:58:59 -0400 X-Ironport-AV: i="3.92,109,1112587200"; d="scan'208"; a="998486436:sNHT13776098" Date: Mon, 18 Apr 2005 08:58:54 -0400 (EDT) From: c0ldbyte To: "Franklin Chef(news)" In-Reply-To: <42628E25.8010008@gmail.com> Message-ID: <20050418085137.U49866@eleanor.us1.wmi.uvac.net> References: <42628196.4070608@comcast.net> <42628E25.8010008@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-hackers@freebsd.org cc: Matt Subject: Re: Making multiple jails 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, 18 Apr 2005 12:59:00 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 17 Apr 2005, Franklin Chef(news) wrote: > Matt wrote: > >> I'd like to create five jails on one machine. Is it possible to make them >> all at the same time? I'm only familiary with creating them individually >> (DESTDIR=/foo/bar). Thanks much. >> > No problem, you can run multiple jail at the same time. All you have to do is > to create different jail directories and edit rc.conf like this: > > jail_enable="YES" > jail_list="jail1 jail2 jail3" > > jail_jail1_hostname="jail1.jail.org" > jail_jail1_ip="192.168.4.100" > .... > > jail_jail2_hostname="jail2.jail.org" > jail_jail2_ip="192.168.4.101" > .... > > jail_jail3_hostname="jail3.jail.org" > jail_jail3_ip="192.168.4.102" > .... I believe he is asking if it is possible to create them at the same time not really run them at the same time. But that is good information for him to know as well anyhow. But the only way to go about that is to do the (make world DESTDIR=/path/to/jail#) for each jail that you need. Now after the first initial build of world, if you didnt do a (make clean) then you should beable to just (make installworld DESTDIR=/path/to/jail#) and the new jail will apear there with the specified parameters that you fed DESTDIR. Hope this all helped you on your quest for knowledge. --c0ldbyte - -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) Comment: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF7DF979F Comment: Fingerprint = D1DC 0AA4 1C4E EAD4 24EB 7E77 B261 50BA F7DF 979F iD8DBQFCY68RsmFQuvffl58RAhnMAJ93XIg2Aw/NMxq0x6x4DJ+IGHTN0gCfYoJP EhVUzcXW/x6mDksaTVLE5Mg= =VpNt -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 18 13:15:23 2005 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 D6E7E16A502 for ; Mon, 18 Apr 2005 13:15:23 +0000 (GMT) Received: from post-22.mail.nl.demon.net (post-22.mail.nl.demon.net [194.159.73.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54B6D43D2F for ; Mon, 18 Apr 2005 13:15:23 +0000 (GMT) (envelope-from albi@scii.nl) Received: from aseed.demon.nl ([83.160.138.119]:10035 helo=mail.aseed.antenna.nl) by post-22.mail.nl.demon.net with esmtp (Exim 4.43) id 1DNW5y-000LPd-B5 for freebsd-hackers@freebsd.org; Mon, 18 Apr 2005 13:15:22 +0000 Received: from http.aseed.antenna.nl (unknown [192.168.0.50]) by mail.aseed.antenna.nl (Postfix) with ESMTP id A787328400B for ; Mon, 18 Apr 2005 15:16:41 +0200 (CEST) Received: from localhost.localdomain (217-19-30-147.dsl.cambrium.nl [217.19.30.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by http.aseed.antenna.nl (Postfix) with ESMTP id 3B9C258CB65 for ; Mon, 18 Apr 2005 15:15:22 +0200 (CEST) Date: Mon, 18 Apr 2005 15:15:20 +0200 From: "albi@scii.nl" To: freebsd-hackers@freebsd.org Message-Id: <20050418151520.37329f12.albi@scii.nl> In-Reply-To: <20050418085137.U49866@eleanor.us1.wmi.uvac.net> References: <42628196.4070608@comcast.net> <42628E25.8010008@gmail.com> <20050418085137.U49866@eleanor.us1.wmi.uvac.net> X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Making multiple jails 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, 18 Apr 2005 13:15:24 -0000 On Mon, 18 Apr 2005 08:58:54 -0400 (EDT) c0ldbyte wrote: > I believe he is asking if it is possible to create them at the same > time not really run them at the same time. But that is good > information for him to know as well anyhow. But the only way to go > about that is to do the (make world DESTDIR=/path/to/jail#) for each > jail that you need. Now after the first initial build of world, if you > didnt do a (make clean) then you should beable to just (make > installworld DESTDIR=/path/to/jail#) and the new jail will apear there > with the specified parameters that you fed DESTDIR. the only way ? i thought UNIX-alikes were known for having always more than one way ;-) another option is to use cpdup to duplicate a fresh jail also quite interesting imho is this : http://www.the-labs.com/FreeBSD/JailTools/fbsd_jails.html this webmin-module offers "light-jails", read-only /usr mount, and also jails installed in a single file if you have that file you can easily reproduce new jails with a simple cp-command From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 18 13:33:40 2005 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 3A44916A4CF for ; Mon, 18 Apr 2005 13:33:40 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF49C43D41 for ; Mon, 18 Apr 2005 13:33:39 +0000 (GMT) (envelope-from slawek.zak@gmail.com) Received: by zproxy.gmail.com with SMTP id 40so3211392nzk for ; Mon, 18 Apr 2005 06:33:38 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=q6MdS8rFbo7z3yfcpg+UD1oJzIX4tjOLTFb7gmOeLq8zsHxDOGb7EI3R/OKGNZb+Z4auJ03s0Zfj6EETFnGF+1w1zY6BVUajHaq9lisov+fHqDG5RkTnfueH4F1AqPJ+akuLUC/UKu3yg8JX+rCCUJhWyBS28xtotA8YRI3FKn8= Received: by 10.36.34.3 with SMTP id h3mr373036nzh; Mon, 18 Apr 2005 06:33:38 -0700 (PDT) Received: by 10.36.88.17 with HTTP; Mon, 18 Apr 2005 06:33:38 -0700 (PDT) Message-ID: <787bbe1c050418063313bf50df@mail.gmail.com> Date: Mon, 18 Apr 2005 15:33:38 +0200 From: =?ISO-8859-2?Q?S=B3awek_=AFak?= To: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: base64 Content-Disposition: inline Subject: 5.4-RC2 keyboard problem on Dell PowerEdge 2850 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: =?ISO-8859-2?Q?S=B3awek_=AFak?= List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2005 13:33:40 -0000 SGksCgpBZnRlciBpbnN0YWxsIGZyb20gQ0QgdGhlIGtleWJvYXJkIGRvZXNuJ3Qgd29yayBvbiB0 aGlzIG1hY2hpbmUuIEhhcwphbnlvbmUgZWxzZSBzZWVuIGl0PwoKL1MKLS0gClOzYXdlayCvYWsg LyBVTklYIFN5c3RlbXMgQWRtaW5pc3RyYXRvcgo= From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 18 13:37:49 2005 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 0518016A4CF for ; Mon, 18 Apr 2005 13:37:49 +0000 (GMT) Received: from marlena.vvi.at (marlena.vvi.at [208.252.225.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id D43E343D2D for ; Mon, 18 Apr 2005 13:37:47 +0000 (GMT) (envelope-from www@marlena.vvi.at) Received: from marlena.vvi.at (localhost.marlena.vvi.at [127.0.0.1]) by marlena.vvi.at (8.12.10/8.12.9) with ESMTP id j3IDcSh3029684; Mon, 18 Apr 2005 06:38:30 -0700 (PDT) (envelope-from www@marlena.vvi.at) Received: (from www@localhost) by marlena.vvi.at (8.12.10/8.12.10/Submit) id j3IDcMWf029681; Mon, 18 Apr 2005 06:38:22 -0700 (PDT) (envelope-from www) Date: Mon, 18 Apr 2005 06:38:22 -0700 (PDT) Message-Id: <200504181338.j3IDcMWf029681@marlena.vvi.at> To: andrit@ukr.net From: "ALeine" cc: c0ldbyte@myrealbox.com cc: mrparsons@gmail.com cc: freebsd-hackers@freebsd.org Subject: Re: ext2 drives under 5.3 not umounting on reboots 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, 18 Apr 2005 13:37:49 -0000 andrit@ukr.net wrote: > I've had the same problem on 5.3. > now on my FreeBSD 5.4-RC2 #0: Fri Apr 15 11:28:48 EEST 2005 i386 > it seems that problem gone. > > On Sunday 17 April 2005 00:07, c0ldbyte wrote: > > On Sat, 16 Apr 2005, M. Parsons wrote: > > > > > I have a ext2 linux partition mounted under /linux via the > > > fstab line: > > > > > > /dev/ad2s1 /linux ext2fs rw 1 2 > > > > > > It will automount on bootup, but if I do a reboot or shutdown > > > -h now, it doesnt get umounted properly. In fact, if this /linux > > > is mounted, then /, /usr, /var, and /tmp (all seperate ufs slices > > > on another hard drive) also get tainted during a reboot. A couple of weeks ago I saw what I believe to be the same problem, but on 4.10-STABLE. My attempt to umount an ext2 volume resulted in failure with the "unknown mount type" error message. I then resorted to using umount -t ext2fs /linux and the volume was unmounted properly, so as a workaround you could specify umount -t ext2fs explicitly in rc.shutdown or similar. I checked the sources in an attempt to find the cause and here is what I found out: In src/sbin/umount.c: RELENG_5: In umountall(): /* Ignore unknown file system types. */ if (getvfsbyname(fs->fs_vfstype, &vfc) == -1) continue; if (checkvfsname(fs->fs_vfstype, typelist)) continue; ... rval = umountall(typelist); rval = checkname(cp, typelist) || rval; free(cp); return (rval); } while ((fs = getfsent()) != NULL); return (0); } In checkname(): if (sfs == NULL) { warnx("%s: unknown file system", name); return (1); } if (checkvfsname(sfs->f_fstypename, typelist)) return (1); return (umountfs(sfs)); } RELENG4: In umountall(): /* If an unknown file system type, complain. */ if (getvfsbyname(fs->fs_vfstype, &vfc) == -1) { warnx("%s: unknown mount type", fs->fs_vfstype); continue; } if (checkvfsname(fs->fs_vfstype, typelist)) continue; ... rval = umountall(typelist); rval = umountfs(cp, typelist) || rval; free(cp); return (rval); } while ((fs = getfsent()) != NULL); return (0); } As you can see, the RELENG_5 code was changed to call a separate function named checkname() instead of checking and reporting name problems directly, but in that process a new check is introduced in a way that makes it possible for umount(8) to fail without reporting the reason for failure. Neither getvfsbyname(3) in src/lib/libc/gen/getvfsbyname.c nor checkvfsname() in src/sbin/mount/vfslist.c have changed in significant ways that would indicate they could be at fault, however there might be a problem with keeping track of filesystem modules, specifically, fs_vfstype (struct fstab) on RELENG_{4,5} and/or f_fstypename (struct statfs) on RELENG_5. Any clues? ALeine ___________________________________________________________________ WebMail FREE http://mail.austrosearch.net From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 18 13:57:42 2005 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 DA89516A4CE; Mon, 18 Apr 2005 13:57:42 +0000 (GMT) Received: from mxsf31.cluster1.charter.net (mxsf31.cluster1.charter.net [209.225.28.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4336F43D5A; Mon, 18 Apr 2005 13:57:42 +0000 (GMT) (envelope-from c0ldbyte@myrealbox.com) Received: from mxip08.cluster1.charter.net (mxip08a.cluster1.charter.net [209.225.28.138])j3IDvetg031515; Mon, 18 Apr 2005 09:57:40 -0400 Received: from 24.247.253.134.gha.mi.chartermi.net (HELO eleanor.us1.wmi.uvac.net) (24.247.253.134) by mxip08.cluster1.charter.net with ESMTP; 18 Apr 2005 09:57:39 -0400 X-Ironport-AV: i="3.92,109,1112587200"; d="scan'208"; a="863182362:sNHT19052966" Date: Mon, 18 Apr 2005 09:57:38 -0400 (EDT) From: c0ldbyte To: =?ISO-8859-2?Q?S=B3awek_=AFak?= In-Reply-To: <787bbe1c050418063313bf50df@mail.gmail.com> Message-ID: <20050418095708.A49866@eleanor.us1.wmi.uvac.net> References: <787bbe1c050418063313bf50df@mail.gmail.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1131860643-1113832658=:49866" cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: 5.4-RC2 keyboard problem on Dell PowerEdge 2850 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, 18 Apr 2005 13:57:43 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1131860643-1113832658=:49866 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed Content-Transfer-Encoding: 8BIT On Mon, 18 Apr 2005, [ISO-8859-2] S砤wek 痑k wrote: > Hi, > > After install from CD the keyboard doesn't work on this machine. Has > anyone else seen it? > > /S Select the correct key map screen map etc... ? -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) --0-1131860643-1113832658=:49866-- From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 18 14:36:11 2005 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 C6EE516A4CF for ; Mon, 18 Apr 2005 14:36:11 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F87043D3F for ; Mon, 18 Apr 2005 14:36:11 +0000 (GMT) (envelope-from slawek.zak@gmail.com) Received: by zproxy.gmail.com with SMTP id 40so3240353nzk for ; Mon, 18 Apr 2005 07:36:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=e/JaDfzU3l50pdWnyACueaFT+jlLHUJC4vICYrxj4l9pxQOO+gKQcAJEBkFowMRGingeME+ofasDBEty4otQStkCgsbkM1oeAe2LP9lPg3lSrqsY1VgKKbM9i7eCcAW881AKU8+4sP/rI0o5pa25VJvoMtg2HYXTRL7181W+zLw= Received: by 10.36.34.3 with SMTP id h3mr379796nzh; Mon, 18 Apr 2005 07:36:10 -0700 (PDT) Received: by 10.36.88.17 with HTTP; Mon, 18 Apr 2005 07:36:09 -0700 (PDT) Message-ID: <787bbe1c05041807366fd8818e@mail.gmail.com> Date: Mon, 18 Apr 2005 16:36:09 +0200 From: =?ISO-8859-2?Q?S=B3awek_=AFak?= To: c0ldbyte In-Reply-To: <20050418095708.A49866@eleanor.us1.wmi.uvac.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <787bbe1c050418063313bf50df@mail.gmail.com> <20050418095708.A49866@eleanor.us1.wmi.uvac.net> cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: 5.4-RC2 keyboard problem on Dell PowerEdge 2850 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: =?ISO-8859-2?Q?S=B3awek_=AFak?= List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2005 14:36:11 -0000 T24gNC8xOC8wNSwgYzBsZGJ5dGUgPGMwbGRieXRlQG15cmVhbGJveC5jb20+IHdyb3RlOgo+IE9u IE1vbiwgMTggQXByIDIwMDUsIFtJU08tODg1OS0yXSBTwrNhd2VrIMKvYWsgd3JvdGU6Cj4gCj4g PiBIaSwKPiA+Cj4gPiBBZnRlciBpbnN0YWxsIGZyb20gQ0QgdGhlIGtleWJvYXJkIGRvZXNuJ3Qg d29yayBvbiB0aGlzIG1hY2hpbmUuIEhhcwo+ID4gYW55b25lIGVsc2Ugc2VlbiBpdD8KPiA+Cj4g PiAvUwo+IAo+IFNlbGVjdCB0aGUgY29ycmVjdCBrZXkgbWFwIHNjcmVlbiBtYXAgZXRjLi4uID8K CkVybS4gV2hlbiBJIHNheSBrZXlib2FyZCBkb2Vzbid0IHdvcmsgSSAqbWVhbiogaXQgZG9lc24n dCB3b3JrIGF0IGFsbC4KVGhlIG9ubHkga2V5IHdoaWNoIHdvcmtzIG9uIHRoZSBib3ggaXMgQlJT LCB3aGljaCBkb2Vzbid0IGdpdmUgbWUKc3VmZmljaWVudCBpbnRlcmFjdGlvbiB3aXRoIHRoZSBz eXN0ZW0uIEkndmUgc2tpcHBlZCBtb3JzZSBjb2RlCmxlc3NvbnMgYW5kIGJveSBzY291dGluZyBp biBteSBsaWZlIGFsdG9nZXRoZXIuCgovUwotLSAKU8WCYXdlayDFu2FrIC8gVU5JWCBTeXN0ZW1z IEFkbWluaXN0cmF0b3IK From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 18 15:11:04 2005 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 8E0E116A4CE; Mon, 18 Apr 2005 15:11:04 +0000 (GMT) Received: from mxsf23.cluster1.charter.net (mxsf23.cluster1.charter.net [209.225.28.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D8F743D3F; Mon, 18 Apr 2005 15:11:04 +0000 (GMT) (envelope-from c0ldbyte@myrealbox.com) Received: from mxip11.cluster1.charter.net (mxip11a.cluster1.charter.net [209.225.28.141])j3IFB2mJ004528; Mon, 18 Apr 2005 11:11:02 -0400 Received: from 24.247.253.134.gha.mi.chartermi.net (HELO eleanor.us1.wmi.uvac.net) (24.247.253.134) by mxip11.cluster1.charter.net with ESMTP; 18 Apr 2005 11:11:03 -0400 X-Ironport-AV: i="3.92,110,1112587200"; d="scan'208"; a="1036045127:sNHT32239450" Date: Mon, 18 Apr 2005 11:10:51 -0400 (EDT) From: c0ldbyte In-Reply-To: <787bbe1c05041807366fd8818e@mail.gmail.com> Message-ID: <20050418110907.S50308@eleanor.us1.wmi.uvac.net> References: <787bbe1c050418063313bf50df@mail.gmail.com> <787bbe1c05041807366fd8818e@mail.gmail.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-390012520-1113837051=:50308" cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: 5.4-RC2 keyboard problem on Dell PowerEdge 2850 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, 18 Apr 2005 15:11:04 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-390012520-1113837051=:50308 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Mon, 18 Apr 2005, [ISO-8859-2] S砤wek 痑k wrote: > On 4/18/05, c0ldbyte wrote: >> On Mon, 18 Apr 2005, [ISO-8859-2] S鲁awek 炉ak wrote: >> >>> Hi, >>> >>> After install from CD the keyboard doesn't work on this machine. Has >>> anyone else seen it? >>> >>> /S >> >> Select the correct key map screen map etc... ? > > Erm. When I say keyboard doesn't work I *mean* it doesn't work at all. > The only key which works on the box is BRS, which doesn't give me > sufficient interaction with the system. I've skipped morse code > lessons and boy scouting in my life altogether. > > /S LOL allright just figured I would ask. It sounded like to me that you allready got the system installed and you couldnt use the keyboard from that point on. Hmm interesting my Dear Watson. Anyway, Best of luck. --c0ldbyte -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) --0-390012520-1113837051=:50308-- From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 18 19:22:41 2005 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 0CC1916A4CE for ; Mon, 18 Apr 2005 19:22:41 +0000 (GMT) Received: from cliffclavin.cs.rpi.edu (cliffclavin.cs.rpi.edu [128.213.1.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C81543D49 for ; Mon, 18 Apr 2005 19:22:40 +0000 (GMT) (envelope-from crossd@cs.rpi.edu) Received: from localhost.localdomain (d48-176.dyn.cs.rpi.edu [128.213.48.176]) (authenticated bits=0)j3IJMdCU067974 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Mon, 18 Apr 2005 15:22:39 -0400 (EDT) From: David Cross To: freebsd-hackers@freebsd.org In-Reply-To: <1113717734.8395.3.camel@kagome> References: <20050416021004.Q91559@monica.cs.rpi.edu> <1113717734.8395.3.camel@kagome> Content-Type: text/plain Date: Mon, 18 Apr 2005 15:22:23 -0400 Message-Id: <1113852143.1016.9.camel@kagome> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.43 Subject: Re: ASUS DRW-1608P, doesn't write anything 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, 18 Apr 2005 19:22:41 -0000 On Sat, 2005-04-16 at 02:16 -0400, David E. Cross wrote: > I have problem with an ASUS DRW-1609P with both 5.3 and 5.4. It won't > write any media. Even "burncd" fails with the following error: > > (Yes, I know I have "test" mode on, I got tired of making coasters) > > burncd -f /dev/acd0 -s max -v -t data file.iso fixate > > adding type 0x08 file mp3.iso.aa size 720000 KB 360000 blocks > > next writeable LBA 2136 > > addr = 2136 size = 737280000 blocks = 360000 > > writing from file mp3.iso.aa size 720000 KB > > written this track 1120 KB (0%) total 1120 KB > > only wrote -1 of 32768 bytes: Device busy > > Relevent line from dmesg: > > acd0: DVDR at ata1-master PIO4 > > atapicam doesn't fix it. UDMA doesn't fix it. GENERIC kernel. > > Reading works fine. > > Suggestions? > Ok, let me ammend this a bit... cdrecord _does_ work. I had tried burncd and growisofs (using CAM) for the ATAPI and ATAPICAM methods. So apparently I can burn cds using atapicam and dvds using dvdrecord (from savanah, this should really be brought into ports). I would like burncd to work, as I don't like opening my entire bus to just write optical media. Any clues on where I should look for this? -- David E. Cross From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 05:11:50 2005 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 F354B16A4CE for ; Tue, 19 Apr 2005 05:11:49 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AFA543D1F for ; Tue, 19 Apr 2005 05:11:49 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [157.185.108.139] (suzy.samsco.org [168.103.85.61]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3J5Dsmr079160; Mon, 18 Apr 2005 23:13:55 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42649308.8050602@samsco.org> Date: Mon, 18 Apr 2005 23:11:36 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Cross References: <20050416021004.Q91559@monica.cs.rpi.edu> <1113717734.8395.3.camel@kagome> <1113852143.1016.9.camel@kagome> In-Reply-To: <1113852143.1016.9.camel@kagome> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-hackers@freebsd.org Subject: Re: ASUS DRW-1608P, doesn't write anything 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, 19 Apr 2005 05:11:50 -0000 David Cross wrote: > On Sat, 2005-04-16 at 02:16 -0400, David E. Cross wrote: > >>I have problem with an ASUS DRW-1609P with both 5.3 and 5.4. It won't >>write any media. Even "burncd" fails with the following error: >> >>(Yes, I know I have "test" mode on, I got tired of making coasters) >> >>>burncd -f /dev/acd0 -s max -v -t data file.iso fixate >>>adding type 0x08 file mp3.iso.aa size 720000 KB 360000 blocks >>>next writeable LBA 2136 >>>addr = 2136 size = 737280000 blocks = 360000 >>>writing from file mp3.iso.aa size 720000 KB >>>written this track 1120 KB (0%) total 1120 KB >>>only wrote -1 of 32768 bytes: Device busy >> >>Relevent line from dmesg: >> >>acd0: DVDR at ata1-master PIO4 >> >>atapicam doesn't fix it. UDMA doesn't fix it. GENERIC kernel. >> >>Reading works fine. >> >>Suggestions? >> > > > Ok, let me ammend this a bit... cdrecord _does_ work. I had tried > burncd and growisofs (using CAM) for the ATAPI and ATAPICAM methods. So > apparently I can burn cds using atapicam and dvds using dvdrecord (from > savanah, this should really be brought into ports). I would like burncd > to work, as I don't like opening my entire bus to just write optical > media. Any clues on where I should look for this? > Whether you are using cdrecord or burncd or whatnot, you're sending MMC-class SCSI commands to the burner to do the work. cdrecord is much more sophisticated in how it does this than burncd (hence why ATAPICAM is needed and not the canned ioctls that stock ATA provides to burncd), so it's likely that your drive has some sort of quirk that burncd can't cope with. Probably the best way to get this fixed is provide access to the hardware to Soeren. Barring that, atapicam + burncd is a fine replacement. I'm not sure what you mean by 'opening the entire bus', though. Scott From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 13:32:29 2005 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 CD07016A4CE; Tue, 19 Apr 2005 13:32:29 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DC2F43D3F; Tue, 19 Apr 2005 13:32:29 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id BE6A81F103; Tue, 19 Apr 2005 15:32:27 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id A07BD615A; Tue, 19 Apr 2005 15:32:27 +0200 (CEST) Date: Tue, 19 Apr 2005 15:32:27 +0200 From: Marc Olzheim To: Brian Fundakowski Feldman , freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Message-ID: <20050419133227.GA11612@stack.nl> References: <20050415050821.GO981@green.homeunix.org> <20050415132108.GC85922@stack.nl> <20050415150708.GP981@green.homeunix.org> <20050418092550.GA97539@stack.nl> <20050418092752.GB97539@stack.nl> <20050418202213.GC1157@green.homeunix.org> <20050418203321.GA88774@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline In-Reply-To: <20050418203321.GA88774@stack.nl> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i cc: Marc Olzheim Subject: Re: NFS client/buffer cache deadlock 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, 19 Apr 2005 13:32:30 -0000 --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 18, 2005 at 10:33:21PM +0200, Marc Olzheim wrote: > On Mon, Apr 18, 2005 at 04:22:13PM -0400, Brian Fundakowski Feldman wrote: > > > > http://green.homeunix.org/~green/nfs_client.deadlock.patch > > > Hmm, could you change it into a diff -u ? > >=20 > > I replaced the patch with one with -u for you. >=20 > Ok, great, I'll do some test on my -CURRENT machine at work > in the morning (CEST). Hmm, sys/vnode.h has changed a lot from RELENG_5 to -CURRENT... Perhaps someone with insight in this overhaul could change the patch to HEAD ? Marc --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZQhrezjnobFOgrERAoMsAJ9S4VosY4rqKCWV0h4v1nShS0FC2wCguh88 sotR5t18dvrEEIVedODVwh0= =54nw -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 15:13:23 2005 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 1C4AE16A4CF for ; Tue, 19 Apr 2005 15:13:23 +0000 (GMT) Received: from orion.erdves.lt (ns2.lrtc.net [217.9.240.98]) by mx1.FreeBSD.org (Postfix) with SMTP id 8F32A43D5A for ; Tue, 19 Apr 2005 15:13:21 +0000 (GMT) (envelope-from donatas@lrtc.net) Received: (qmail 54684 invoked from network); 19 Apr 2005 15:13:20 -0000 Received: from unknown (HELO www.lrtc.net) (217.9.240.99) by orion.erdves.lt with SMTP; 19 Apr 2005 15:13:20 -0000 Received: from donatas ([217.9.241.242]) by www.lrtc.net (Lotus Domino Release 6.0) with ESMTP id 2005041918131958-19206 ; Tue, 19 Apr 2005 18:13:19 +0300 Message-ID: <014201c544f2$5019a700$9f90a8c0@DONATAS> From: "Donatas" To: Date: Tue, 19 Apr 2005 18:13:16 +0300 Organization: AB Lietuvos Radijo ir Televizijos Centras MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-MIMETrack: Itemize by SMTP Server on lotus/LRTC(Release 6.0|September 26, 2002) at 04/19/2005 06:13:19 PM,04/19/2005 06:13:19 PM, Serialize complete at 04/19/2005 06:13:19 PM Content-Type: text/plain; charset="iso-8859-4" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: virtual swich X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Donatas List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2005 15:13:23 -0000 hello, are there any solutions for emulating a network switch between network = interfaces under FreeBSD 5.3? i cannot use ng_hub because it does not filter packets by their mac = addresses... the purpose is switching between ngeth0,ngeth1 and em0. any ideas are welcome Donatas G. From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 15:19:01 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 58C4B16A4CE; Tue, 19 Apr 2005 15:19:01 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.3/8.13.1) with ESMTP id j3JFI09A041298; Tue, 19 Apr 2005 11:18:00 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.3/8.13.1/Submit) id j3JFI0cI041297; Tue, 19 Apr 2005 11:18:00 -0400 (EDT) (envelope-from green) Date: Tue, 19 Apr 2005 11:18:00 -0400 From: Brian Fundakowski Feldman To: Marc Olzheim Message-ID: <20050419151800.GE1157@green.homeunix.org> References: <20050415050821.GO981@green.homeunix.org> <20050415132108.GC85922@stack.nl> <20050415150708.GP981@green.homeunix.org> <20050418092550.GA97539@stack.nl> <20050418092752.GB97539@stack.nl> <20050418202213.GC1157@green.homeunix.org> <20050418203321.GA88774@stack.nl> <20050419133227.GA11612@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050419133227.GA11612@stack.nl> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 19 Apr 2005 15:19:01 -0000 On Tue, Apr 19, 2005 at 03:32:27PM +0200, Marc Olzheim wrote: > On Mon, Apr 18, 2005 at 10:33:21PM +0200, Marc Olzheim wrote: > > On Mon, Apr 18, 2005 at 04:22:13PM -0400, Brian Fundakowski Feldman wrote: > > > > > http://green.homeunix.org/~green/nfs_client.deadlock.patch > > > > Hmm, could you change it into a diff -u ? > > > > > > I replaced the patch with one with -u for you. > > > > Ok, great, I'll do some test on my -CURRENT machine at work > > in the morning (CEST). > > Hmm, sys/vnode.h has changed a lot from RELENG_5 to -CURRENT... Perhaps > someone with insight in this overhaul could change the patch to HEAD ? Does this work for you? cvs diff: Diffing sys Index: sys/buf.h =================================================================== RCS file: /usr/ncvs/src/sys/sys/buf.h,v retrieving revision 1.185 diff -u -r1.185 buf.h --- sys/buf.h 10 Feb 2005 12:17:48 -0000 1.185 +++ sys/buf.h 19 Apr 2005 14:30:54 -0000 @@ -465,6 +465,7 @@ extern int maxswzone; /* Max KVA for swap structures */ extern int maxbcache; /* Max KVA for buffer cache */ extern int runningbufspace; +extern int hibufspace; extern int buf_maxio; /* nominal maximum I/O for buffer */ extern struct buf *buf; /* The buffer headers. */ extern char *buffers; /* The buffer contents. */ cvs diff: Diffing kern Index: kern/vfs_bio.c =================================================================== RCS file: /usr/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.482 diff -u -r1.482 vfs_bio.c --- kern/vfs_bio.c 25 Mar 2005 00:20:37 -0000 1.482 +++ kern/vfs_bio.c 19 Apr 2005 14:30:54 -0000 @@ -127,7 +127,7 @@ static int lobufspace; SYSCTL_INT(_vfs, OID_AUTO, lobufspace, CTLFLAG_RD, &lobufspace, 0, "Minimum amount of buffers we want to have"); -static int hibufspace; +int hibufspace; SYSCTL_INT(_vfs, OID_AUTO, hibufspace, CTLFLAG_RD, &hibufspace, 0, "Maximum allowed value of bufspace (excluding buf_daemon)"); static int bufreusecnt; cvs diff: Diffing nfsclient Index: nfsclient/nfs_bio.c =================================================================== RCS file: /usr/ncvs/src/sys/nfsclient/nfs_bio.c,v retrieving revision 1.150 diff -u -r1.150 nfs_bio.c --- nfsclient/nfs_bio.c 18 Mar 2005 21:23:32 -0000 1.150 +++ nfsclient/nfs_bio.c 19 Apr 2005 15:11:13 -0000 @@ -844,6 +844,7 @@ struct vattr vattr; struct nfsmount *nmp = VFSTONFS(vp->v_mount); daddr_t lbn; + off_t commitleft; /* if non-zero, the amount left we may write */ int bcount; int n, on, error = 0; int haverslock = 0; @@ -873,6 +874,14 @@ */ if (ioflag & (IO_APPEND | IO_SYNC)) { if (np->n_flag & NMODIFIED) { +flush_and_restart: + /* + * Require non-blocking, synchronous writes to + * dirty files to inform the program it needs + * to fsync(2) explicitly. + */ + if (ioflag & IO_NDELAY) + return (EAGAIN); np->n_attrstamp = 0; error = nfs_vinvalbuf(vp, V_SAVE, td, 1); if (error) @@ -953,12 +962,65 @@ } biosize = vp->v_mount->mnt_stat.f_iosize; + commitleft = 0; + /* + * If there are possible modifications, find all of this file's + * B_NEEDCOMMIT buffers. If our writes would exceed the local + * maximum per-file write commit size when combined with those, + * we decide to flush and/or do a short write. + */ + if ((ioflag & (IO_SYNC | IO_INVAL)) != (IO_SYNC | IO_INVAL)) { + commitleft = nmp->nm_wcommitsize; + if (np->n_flag & NMODIFIED) { + int wouldcommit = 0; + BO_LOCK(vp->v_bufobj); + if (vp->v_bufobj.bo_dirty.bv_cnt != 0) { + TAILQ_FOREACH(bp, &vp->v_bufobj.bo_dirty.bv_hd, + b_bobufs) { + if (bp->b_flags & B_NEEDCOMMIT) + wouldcommit += bp->b_bcount; + } + } + BO_UNLOCK(vp->v_bufobj); + /* + * Since we're not operating synchronously and + * bypassing the buffer cache, we are in a commit + * and holding all of these buffers whether + * transmitted or not. If not limited, this + * will lead to the buffer cache deadlocking, + * as no one else can flush our uncommitted buffers. + */ + wouldcommit += uio->uio_resid; + /* + * If we would initially exceed the maximum + * outstanding write commit size, flush and restart. + */ + if (wouldcommit > commitleft) { + if (haverslock) { + nfs_rsunlock(np, td); + haverslock = 0; + } + goto flush_and_restart; + } + } else { + /* + * With no outstanding commits, we are limited only + * by commitleft as to how far we can go. + */ + } + } do { nfsstats.biocache_writes++; lbn = uio->uio_offset / biosize; on = uio->uio_offset & (biosize-1); n = min((unsigned)(biosize - on), uio->uio_resid); + /* Always allow at least the very first write. */ + if (commitleft > 0) { + commitleft -= n; + if (commitleft == 0) + commitleft = -1; + } again: /* * Handle direct append and file extension cases, calculate @@ -1146,10 +1208,21 @@ } else { bdwrite(bp); } - } while (uio->uio_resid > 0 && n > 0); + } while (uio->uio_resid > 0 && n > 0 && commitleft >= 0); - if (haverslock) + if (haverslock) { + haverslock = 0; nfs_rsunlock(np, td); + } + + /* + * On the off chance that we're trying to do a very large + * and non-atomic write, go ahead and let that just continue + * within the same call after flushing out what's been written. + */ + if (error == 0 && uio->uio_resid > 0 && n > 0 && commitleft < 0 && + !(ioflag & IO_UNIT)) + goto flush_and_restart; return (error); } Index: nfsclient/nfs_vfsops.c =================================================================== RCS file: /usr/ncvs/src/sys/nfsclient/nfs_vfsops.c,v retrieving revision 1.172 diff -u -r1.172 nfs_vfsops.c --- nfsclient/nfs_vfsops.c 24 Mar 2005 07:37:22 -0000 1.172 +++ nfsclient/nfs_vfsops.c 19 Apr 2005 14:32:19 -0000 @@ -41,6 +41,8 @@ #include #include #include +#include +#include #include #include #include @@ -626,6 +628,12 @@ else nmp->nm_readahead = NFS_MAXRAHEAD; } + if ((argp->flags & NFSMNT_WCOMMITSIZE) && argp->wcommitsize >= 0) { + if (argp->wcommitsize < nmp->nm_wsize) + nmp->nm_wcommitsize = nmp->nm_wsize; + else + nmp->nm_wcommitsize = argp->wcommitsize; + } if ((argp->flags & NFSMNT_DEADTHRESH) && argp->deadthresh >= 0) { if (argp->deadthresh <= NFS_MAXDEADTHRESH) nmp->nm_deadthresh = argp->deadthresh; @@ -808,6 +816,7 @@ nmp->nm_wsize = NFS_WSIZE; nmp->nm_rsize = NFS_RSIZE; } + nmp->nm_wcommitsize = hibufspace / (desiredvnodes / 1000); nmp->nm_readdirsize = NFS_READDIRSIZE; nmp->nm_numgrps = NFS_MAXGRPS; nmp->nm_readahead = NFS_DEFRAHEAD; Index: nfsclient/nfsargs.h =================================================================== RCS file: /usr/ncvs/src/sys/nfsclient/nfsargs.h,v retrieving revision 1.67 diff -u -r1.67 nfsargs.h --- nfsclient/nfsargs.h 7 Jan 2005 01:45:51 -0000 1.67 +++ nfsclient/nfsargs.h 19 Apr 2005 14:30:54 -0000 @@ -56,7 +56,7 @@ int retrans; /* times to retry send */ int maxgrouplist; /* Max. size of group list */ int readahead; /* # of blocks to readahead */ - int __pad1; /* was "leaseterm" */ + int wcommitsize; /* Max. write commit size in bytes */ int deadthresh; /* Retrans threshold */ char *hostname; /* server's name */ int acregmin; /* cache attrs for reg files min time */ @@ -80,7 +80,7 @@ #define NFSMNT_NFSV3 0x00000200 /* Use NFS Version 3 protocol */ /* 0x400 free, was NFSMNT_KERB */ #define NFSMNT_DUMBTIMR 0x00000800 /* Don't estimate rtt dynamically */ -/* 0x1000 free, was NFSMNT_LEASETERM */ +#define NFSMNT_WCOMMITSIZE 0x00001000 /* set max write commit size */ #define NFSMNT_READAHEAD 0x00002000 /* set read ahead */ #define NFSMNT_DEADTHRESH 0x00004000 /* set dead server retry thresh */ #define NFSMNT_RESVPORT 0x00008000 /* Allocate a reserved port */ Index: nfsclient/nfsmount.h =================================================================== RCS file: /usr/ncvs/src/sys/nfsclient/nfsmount.h,v retrieving revision 1.29 diff -u -r1.29 nfsmount.h --- nfsclient/nfsmount.h 7 Jan 2005 01:45:51 -0000 1.29 +++ nfsclient/nfsmount.h 19 Apr 2005 14:30:54 -0000 @@ -74,6 +74,7 @@ int nm_wsize; /* Max size of write rpc */ int nm_readdirsize; /* Size of a readdir rpc */ int nm_readahead; /* Num. of blocks to readahead */ + int nm_wcommitsize; /* Max size of commit for write */ int nm_acdirmin; /* Directory attr cache min lifetime */ int nm_acdirmax; /* Directory attr cache max lifetime */ int nm_acregmin; /* Reg file attr cache min lifetime */ -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 15:19:30 2005 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 92C3616A4CE for ; Tue, 19 Apr 2005 15:19:30 +0000 (GMT) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 670C343D48 for ; Tue, 19 Apr 2005 15:19:29 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j3JFJS17067993; Tue, 19 Apr 2005 10:19:28 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42652154.6040904@centtech.com> Date: Tue, 19 Apr 2005 10:18:44 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050325 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Donatas References: <014201c544f2$5019a700$9f90a8c0@DONATAS> In-Reply-To: <014201c544f2$5019a700$9f90a8c0@DONATAS> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/840/Mon Apr 18 20:42:09 2005 on mh1.centtech.com X-Virus-Status: Clean cc: freebsd-hackers@freebsd.org Subject: Re: virtual swich 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, 19 Apr 2005 15:19:30 -0000 Donatas wrote: > hello, > > are there any solutions for emulating a network switch between network interfaces under FreeBSD 5.3? > i cannot use ng_hub because it does not filter packets by their mac addresses... > the purpose is switching between ngeth0,ngeth1 and em0. > > any ideas are welcome Is this what you want? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bridging.html Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 15:27:45 2005 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 4A33D16A4CE for ; Tue, 19 Apr 2005 15:27:45 +0000 (GMT) Received: from titan.whee.org (titan.whee.org [207.195.206.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id B52B843D3F for ; Tue, 19 Apr 2005 15:27:44 +0000 (GMT) (envelope-from adam@whee.org) Received: from titan.whee.org (localhost [127.0.0.1]) by titan.whee.org (8.12.9/8.12.9) with ESMTP id j3JFDdjX000552 for ; Tue, 19 Apr 2005 10:13:39 -0500 (CDT) Received: from localhost (adam@localhost) by titan.whee.org (8.12.9/8.12.9/Submit) with ESMTP id j3JFDcpQ000549 for ; Tue, 19 Apr 2005 10:13:38 -0500 (CDT) X-Authentication-Warning: titan.whee.org: adam owned process doing -bs Date: Tue, 19 Apr 2005 10:13:38 -0500 (CDT) From: Adam Maloney X-X-Sender: adam@titan To: freebsd-hackers@freebsd.org In-Reply-To: <42652154.6040904@centtech.com> Message-ID: References: <014201c544f2$5019a700$9f90a8c0@DONATAS> <42652154.6040904@centtech.com> X-GPG-FINGERPRINT: E39B 8D34 5F0A EA2E 4CCA 5B1D 8D55 7C25 0061 10AF X-GPG-PUBLIC_KEY: http://www.whee.org/~adam/adam-whee-org-pubkey.asc MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: virtual swich 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, 19 Apr 2005 15:27:45 -0000 On Tue, 19 Apr 2005, Eric Anderson wrote: > Donatas wrote: >> hello, >> >> are there any solutions for emulating a network switch between network >> interfaces under FreeBSD 5.3? >> i cannot use ng_hub because it does not filter packets by their mac >> addresses... >> the purpose is switching between ngeth0,ngeth1 and em0. >> >> any ideas are welcome > > Is this what you want? > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bridging.html I had a similar need a few months ago, and found two other projects that might be helpful: http://people.freebsd.org/~picobsd/picobsd.html and picobsd(8) http://www.pdos.lcs.mit.edu/click/ I had trouble building the correct configuration with Click. I ended up using a picobsd floppy. Easy-peasy. HTH, Adam From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 16:03:00 2005 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 D19FA16A4CE; Tue, 19 Apr 2005 16:03:00 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id F36D243D1D; Tue, 19 Apr 2005 16:02:59 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 0CBDF1F110; Tue, 19 Apr 2005 18:02:59 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id E5326615A; Tue, 19 Apr 2005 18:02:58 +0200 (CEST) Date: Tue, 19 Apr 2005 18:02:58 +0200 From: Marc Olzheim To: Brian Fundakowski Feldman Message-ID: <20050419160258.GA12287@stack.nl> References: <20050415050821.GO981@green.homeunix.org> <20050415132108.GC85922@stack.nl> <20050415150708.GP981@green.homeunix.org> <20050418092550.GA97539@stack.nl> <20050418092752.GB97539@stack.nl> <20050418202213.GC1157@green.homeunix.org> <20050418203321.GA88774@stack.nl> <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <20050419151800.GE1157@green.homeunix.org> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i cc: Marc Olzheim cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 19 Apr 2005 16:03:01 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Apr 19, 2005 at 11:18:00AM -0400, Brian Fundakowski Feldman wrote: > Does this work for you? ... cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror /usr/src/sys/nfsclient/nfs_bio.c /usr/src/sys/nfsclient/nfs_bio.c: In function `nfs_write': /usr/src/sys/nfsclient/nfs_bio.c:976: error: invalid type argument of `->' /usr/src/sys/nfsclient/nfs_bio.c:976: error: invalid type argument of `->' /usr/src/sys/nfsclient/nfs_bio.c:984: error: invalid type argument of `->' /usr/src/sys/nfsclient/nfs_bio.c:984: error: invalid type argument of `->' *** Error code 1 Mac --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZSuyezjnobFOgrERAnUgAJ9YW1TUn6TJdlo/aswhffqH74EgbACfZmjS RIkNxmHiW7k2vO9X/i6uIlQ= =PjU1 -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 16:09:02 2005 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 16B1916A4CE; Tue, 19 Apr 2005 16:09:02 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id B830143D31; Tue, 19 Apr 2005 16:09:01 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 2300F1F110; Tue, 19 Apr 2005 18:09:01 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id 05457615A; Tue, 19 Apr 2005 18:09:00 +0200 (CEST) Date: Tue, 19 Apr 2005 18:09:00 +0200 From: Marc Olzheim To: Brian Fundakowski Feldman Message-ID: <20050419160900.GB12287@stack.nl> References: <20050415050821.GO981@green.homeunix.org> <20050415132108.GC85922@stack.nl> <20050415150708.GP981@green.homeunix.org> <20050418092550.GA97539@stack.nl> <20050418092752.GB97539@stack.nl> <20050418202213.GC1157@green.homeunix.org> <20050418203321.GA88774@stack.nl> <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="K8nIJk4ghYZn606h" Content-Disposition: inline In-Reply-To: <20050419160258.GA12287@stack.nl> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i cc: Marc Olzheim cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 19 Apr 2005 16:09:02 -0000 --K8nIJk4ghYZn606h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 19, 2005 at 06:02:58PM +0200, Marc Olzheim wrote: > On Tue, Apr 19, 2005 at 11:18:00AM -0400, Brian Fundakowski Feldman wrote: > > Does this work for you? >=20 > ... >=20 > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototy= pes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-ex= tensions -std=3Dc99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/con= trib/dev/acpica -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter= -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/co= ntrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -= D_KERNEL -include opt_global.h -fno-common -finline-limit=3D8000 --param in= line-unit-growth=3D100 --param large-function-growth=3D1000 -mno-align-lon= g-strings -mpreferred-stack-boundary=3D2 -mno-mmx -mno-3dnow -mno-sse -mno= -sse2 -ffreestanding -Werror /usr/src/sys/nfsclient/nfs_bio.c > /usr/src/sys/nfsclient/nfs_bio.c: In function `nfs_write': > /usr/src/sys/nfsclient/nfs_bio.c:976: error: invalid type argument of `->' > /usr/src/sys/nfsclient/nfs_bio.c:976: error: invalid type argument of `->' > /usr/src/sys/nfsclient/nfs_bio.c:984: error: invalid type argument of `->' > /usr/src/sys/nfsclient/nfs_bio.c:984: error: invalid type argument of `->' > *** Error code 1 That's about the BO_LOCK(vp->v_bufobj); and the BO_UNLOCK(vp->v_bufobj); Marc --K8nIJk4ghYZn606h Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZS0cezjnobFOgrERAq8DAKCgY7RxdUXoXxn82VqsHL+8E6ipfQCgu8aa XRz3rvCIHRMZ8fWKrtbBSog= =b9j1 -----END PGP SIGNATURE----- --K8nIJk4ghYZn606h-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 16:17:19 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7563D16A4CE; Tue, 19 Apr 2005 16:17:19 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.3/8.13.1) with ESMTP id j3JGGG2X042458; Tue, 19 Apr 2005 12:16:16 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.3/8.13.1/Submit) id j3JGGGYU042457; Tue, 19 Apr 2005 12:16:16 -0400 (EDT) (envelope-from green) Date: Tue, 19 Apr 2005 12:16:16 -0400 From: Brian Fundakowski Feldman To: Marc Olzheim Message-ID: <20050419161616.GF1157@green.homeunix.org> References: <20050415132108.GC85922@stack.nl> <20050415150708.GP981@green.homeunix.org> <20050418092550.GA97539@stack.nl> <20050418092752.GB97539@stack.nl> <20050418202213.GC1157@green.homeunix.org> <20050418203321.GA88774@stack.nl> <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050419160900.GB12287@stack.nl> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 19 Apr 2005 16:17:19 -0000 On Tue, Apr 19, 2005 at 06:09:00PM +0200, Marc Olzheim wrote: > On Tue, Apr 19, 2005 at 06:02:58PM +0200, Marc Olzheim wrote: > > On Tue, Apr 19, 2005 at 11:18:00AM -0400, Brian Fundakowski Feldman wrote: > > > Does this work for you? > > > > ... > > > > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror /usr/src/sys/nfsclient/nfs_bio.c > > /usr/src/sys/nfsclient/nfs_bio.c: In function `nfs_write': > > /usr/src/sys/nfsclient/nfs_bio.c:976: error: invalid type argument of `->' > > /usr/src/sys/nfsclient/nfs_bio.c:976: error: invalid type argument of `->' > > /usr/src/sys/nfsclient/nfs_bio.c:984: error: invalid type argument of `->' > > /usr/src/sys/nfsclient/nfs_bio.c:984: error: invalid type argument of `->' > > *** Error code 1 > > That's about the BO_LOCK(vp->v_bufobj); and the BO_UNLOCK(vp->v_bufobj); Yeah, I get that too. I have no clue why it's doing that, I was figuring it was just my compile setup... -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 18:58:59 2005 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 CDB0F16A4CE for ; Tue, 19 Apr 2005 18:58:59 +0000 (GMT) Received: from mx.laposte.net (mx.laposte.net [81.255.54.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2DE443D2D for ; Tue, 19 Apr 2005 18:58:58 +0000 (GMT) (envelope-from emmanuel.chriqui@laposte.net) Received: from pcemmanuel (81.57.219.151) by mx.laposte.net (7.0.028) (authenticated as emmanuel.chriqui) id 425309CA00867E1F for freebsd-hackers@freebsd.org; Tue, 19 Apr 2005 20:58:57 +0200 Message-ID: <425309CA00867E1F@lpdnpm09.laposte.net> (added by postmaster@laposte.net) From: "Emmanuel Chriqui" To: Date: Tue, 19 Apr 2005 20:59:11 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcVFEd81cKtiY6qtRICFIa8nxmCgNg== Subject: PXEBOOT/TFTPBOOT + big MD_ROOT problem 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, 19 Apr 2005 18:58:59 -0000 Hi, I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No NFS. It's a sort of diskless machine with all the system on ram. When image is small ( <= 45M ) everything boots ok. But if greater, then the kernel does not find the /sbin/init and then reboots over and over, as if the preloaded image was partially erased or overlapped. In order to be sure I took the mfsroot from boot.flp and put it each time in a bigger image. Same problem. I use a classic mfs_root approche to make my image dd if=/dev/zero of=$MFS_FILE bs=1k count=$SIZE mdconfig -a -t vnode -f $MFS_FILE -u0 bsdlabel -w /dev/md0 newfs /dev/md0c mount /dev/md0c $MFS_FILE_MOUNT cp ... my content... umount $MFS_FILE_MOUNT fsck -t ufs /dev/md0c mdconfig -d -u 0 then I mount the $MFS_FILE_MOUNT . I tried to increase NPTK as suggested on another thread in the past but that seems to get things worse (machine hangs on boot, or starts showing nasty error messages under panic). I use i386/5.4RC3/TFTPD/PXEBOOT+TFTPBOOT . Please advise.. Emmanuel. From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 19:05:59 2005 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 D41A916A4CF; Tue, 19 Apr 2005 19:05:59 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18CE143D2F; Tue, 19 Apr 2005 19:05:59 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id CDCEA1F13B; Tue, 19 Apr 2005 21:05:57 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id A4C44641C; Tue, 19 Apr 2005 21:05:57 +0200 (CEST) Date: Tue, 19 Apr 2005 21:05:57 +0200 From: Marc Olzheim To: Emmanuel Chriqui Message-ID: <20050419190557.GA82027@stack.nl> References: <20050419075158.6444A31931C@postfix4-2.free.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw" Content-Disposition: inline In-Reply-To: <20050419075158.6444A31931C@postfix4-2.free.fr> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem 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, 19 Apr 2005 19:06:00 -0000 --wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote: > Hi,=20 >=20 > I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. = No > NFS. Any reasons for not using NFS ? > I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT .=20 > (same pb with a 5.3).=20 >=20 > Am I missing something obvious?=20 I'm not sure. tftp itself is able to handle 32MB+ files, but maybe the loader isn't. A workaround, no using NFS, could be to tftp a second filesystem image on boot and mount that from the root filesystem. Marc --wac7ysb48OaltWcw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZVaVezjnobFOgrERAkRHAKC7R8Z1RCpP2qphW0k0eo0j14n3hwCg0NLn NYl2XCthRyxkbLTiFzemy7k= =j20q -----END PGP SIGNATURE----- --wac7ysb48OaltWcw-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 19:30:57 2005 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 444C416A4DA; Tue, 19 Apr 2005 19:30:57 +0000 (GMT) Received: from mx.laposte.net (mx.laposte.net [81.255.54.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9223743D41; Tue, 19 Apr 2005 19:30:56 +0000 (GMT) (envelope-from emmanuel.chriqui@laposte.net) Received: from pcemmanuel (81.57.219.151) by mx.laposte.net (7.0.028) (authenticated as emmanuel.chriqui) id 425309CC00851976; Tue, 19 Apr 2005 21:30:55 +0200 Message-ID: <425309CC00851976@lpdnpm10.laposte.net> (added by postmaster@laposte.net) From: "Emmanuel Chriqui" To: "'Marc Olzheim'" Date: Tue, 19 Apr 2005 21:31:10 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <20050419190557.GA82027@stack.nl> Thread-Index: AcVFEtcSFeXGUR1lQPWN/rd/fWnEAwAACOdg cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: RE: PXEBOOT/TFTPBOOT + big MD_ROOT problem 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, 19 Apr 2005 19:30:57 -0000 > -----Message d'origine----- > De=A0: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd- > hackers@freebsd.org] De la part de Marc Olzheim > Envoy=E9=A0: mardi 19 avril 2005 21:06 > =C0=A0: Emmanuel Chriqui > Cc=A0: freebsd-hackers@freebsd.org; freebsd-stable@freebsd.org > Objet=A0: Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem >=20 > On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote: > > Hi, > > > > I'm trying to make very big MD_ROOT (300MB) sent using = PXEBOOT+TFTPBOOT. > No > > NFS. >=20 > Any reasons for not using NFS ? Yes. Mainly : similar system already working great under linux for two years, NFS heavy traffic problems making data loss so difficult to solve = (at least under Linux), cheap memory, better server independence when he got = his system (tftp server shut down after the client servers got theirs = images). >=20 > > I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . > > (same pb with a 5.3). > > > > Am I missing something obvious? >=20 > I'm not sure. tftp itself is able to handle 32MB+ files, but maybe the > loader isn't. TFTP linux->FreeBSD, FreeBsd->FreeBSD, FreeBSD->Linux ok for 500MB, 1GB, 1,5GB, works ok (well... at least on our servers..). >=20 > A workaround, no using NFS, could be to tftp a second filesystem image > on boot and mount that from the root filesyste This is roughly how it works under our linux servers, webservers, etc... = I was hoping to avoid that approach (less work.. less maintenance..).=20 Am I the only one on earth to need a big MFSROOT ???=20 :) Emmanuel. From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 19:38:54 2005 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 9162E16A4CE; Tue, 19 Apr 2005 19:38:54 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44D5043D31; Tue, 19 Apr 2005 19:38:54 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 514701F146; Tue, 19 Apr 2005 21:38:53 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id 36CFF641C; Tue, 19 Apr 2005 21:38:53 +0200 (CEST) Date: Tue, 19 Apr 2005 21:38:53 +0200 From: Marc Olzheim To: Emmanuel Chriqui Message-ID: <20050419193853.GA54430@stack.nl> References: <20050419190557.GA82027@stack.nl> <425309CC00851976@lpdnpm10.laposte.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UlVJffcvxoiEqYs2" Content-Disposition: inline In-Reply-To: <425309CC00851976@lpdnpm10.laposte.net> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i cc: 'Marc Olzheim' cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem 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, 19 Apr 2005 19:38:54 -0000 --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 19, 2005 at 09:31:10PM +0200, Emmanuel Chriqui wrote: > This is roughly how it works under our linux servers, webservers, etc... I > was hoping to avoid that approach (less work.. less maintenance..).=20 >=20 > Am I the only one on earth to need a big MFSROOT ???=20 > :) Hmm, I guess so. :-P Anyway, you might try http://pigseye.kennesaw.edu/~dyeske/freebsd/article.html Although I'm not sure the linker will allow you to link such a huge object into the kernel... I've used this patch on my netbooted FreeBSD 4.x servers, but never larger tham 10 MB. Another idea is to use NFS just to use the loader to 'load -t mfs_root' the mfsroot image. After that, you wouldn't depend on NFS anymore. Marc --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD4DBQFCZV5NezjnobFOgrERAk3/AJjrJNX4clmF2w0MUFCWFUTwlhdwAKDCZjwc 3uShtpIR40cazHGZQwxjuw== =33GT -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 19:53:24 2005 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 0EFA916A4CE; Tue, 19 Apr 2005 19:53:24 +0000 (GMT) Received: from mx.laposte.net (mx.laposte.net [81.255.54.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C19C43D39; Tue, 19 Apr 2005 19:53:23 +0000 (GMT) (envelope-from emmanuel.chriqui@laposte.net) Received: from pcemmanuel (81.57.219.151) by mx.laposte.net (7.0.028) (authenticated as emmanuel.chriqui) id 425309CA0086FED9; Tue, 19 Apr 2005 21:53:22 +0200 Message-ID: <425309CA0086FED9@lpdnpm09.laposte.net> (added by postmaster@laposte.net) From: "Emmanuel Chriqui" To: "'Marc Olzheim'" Date: Tue, 19 Apr 2005 21:53:37 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <20050419193853.GA54430@stack.nl> Thread-Index: AcVFF3F1KFBqHN/TQHiGmVIqrEfYugAAJCxg cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: RE: PXEBOOT/TFTPBOOT + big MD_ROOT problem 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, 19 Apr 2005 19:53:24 -0000 > Objet=A0: Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem >=20 > On Tue, Apr 19, 2005 at 09:31:10PM +0200, Emmanuel Chriqui wrote: > > This is roughly how it works under our linux servers, webservers, = etc... > I > > was hoping to avoid that approach (less work.. less maintenance..). > > > > Am I the only one on earth to need a big MFSROOT ??? > > :) >=20 > Hmm, I guess so. :-P >=20 > Anyway, you might try >=20 > http://pigseye.kennesaw.edu/~dyeske/freebsd/article.html Thx ! > ... >=20 > Another idea is to use NFS just to use the loader to 'load -t = mfs_root' > the mfsroot image. After that, you wouldn't depend on NFS anymore. >=20 > Marc Very good idea. If my problem is related to TFTP + mfs_root than than = this might work.=20 Emmanuel. From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 20:12:46 2005 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 724A916A51E; Tue, 19 Apr 2005 20:12:46 +0000 (GMT) Received: from mx.laposte.net (mx.laposte.net [81.255.54.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id B300443D2F; Tue, 19 Apr 2005 20:12:45 +0000 (GMT) (envelope-from emmanuel.chriqui@laposte.net) Received: from pcemmanuel (81.57.219.151) by mx.laposte.net (7.0.028) (authenticated as emmanuel.chriqui) id 425309D500804D3D; Tue, 19 Apr 2005 22:12:44 +0200 Message-ID: <425309D500804D3D@lpdnpm14.laposte.net> (added by postmaster@laposte.net) From: "Emmanuel Chriqui" To: =?iso-8859-1?B?J0v2dmVzZOFuIEfhYm9yJw==?= , "'Marc Olzheim'" Date: Tue, 19 Apr 2005 22:12:59 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <42655BE6.5020108@t-hosting.hu> Thread-Index: AcVFFmcGV01rvox5Sx+Ekp8iPIrRXAABEZLw cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: RE: PXEBOOT/TFTPBOOT + big MD_ROOT problem 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, 19 Apr 2005 20:12:46 -0000 > Objet=A0: Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem >=20 > Marc Olzheim wrote: >=20 > >On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote: > > > > > >>Hi, > >> > >>I'm trying to make very big MD_ROOT (300MB) sent using = PXEBOOT+TFTPBOOT. > No > >>NFS. > >> > >> > > > >Any reasons for not using NFS ? > > > > > > > >>I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . > >>(same pb with a 5.3). > >> > >>Am I missing something obvious? > >> > >> > > > >I'm not sure. tftp itself is able to handle 32MB+ files, but maybe = the > >loader isn't. > > > >A workaround, no using NFS, could be to tftp a second filesystem = image > >on boot and mount that from the root filesystem. > > > >Marc > > > > > I assume that the PXE clients are diskless clients. If so, do they = have > enough memory to handle this extremely large image? As for tfpt, it = uses YES, diskless. And enough memory. > UDP. UDP is usually used for transfer small datagrams, for instance = DNS > replies. It is also said to be an unreliable protocol. The client = should > repeat the request when no data receives. I doubt this solution is You're right. However, pros : over 2 years this solution has proven to = work *perfectly* for us, Reboots are rare and done using pools (~10 servers = each time), NFS was horrible to handle and we lost data everytime traffic was intense. Cons : this was over linux. I believe NFS over FreeBSD works = better (by I still have my linux servers... and they work great so..). > reliable and flexible enough. My idea for a workaround is creating a > ramdisk from a small boot image, and transfer the less necessary > userland binaries from the boot server to the ramdisk using normal ftp > connection. Yes. Thx. Emmanuel. From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 20:48:35 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 87DF716A4CE; Tue, 19 Apr 2005 20:48:35 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.3/8.13.1) with ESMTP id j3JKlNEK051038; Tue, 19 Apr 2005 16:47:24 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.3/8.13.1/Submit) id j3JKlNO0051037; Tue, 19 Apr 2005 16:47:23 -0400 (EDT) (envelope-from green) Date: Tue, 19 Apr 2005 16:47:23 -0400 From: Brian Fundakowski Feldman To: Marc Olzheim Message-ID: <20050419204723.GG1157@green.homeunix.org> References: <20050415150708.GP981@green.homeunix.org> <20050418092550.GA97539@stack.nl> <20050418092752.GB97539@stack.nl> <20050418202213.GC1157@green.homeunix.org> <20050418203321.GA88774@stack.nl> <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050419161616.GF1157@green.homeunix.org> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 19 Apr 2005 20:48:36 -0000 On Tue, Apr 19, 2005 at 12:16:16PM -0400, Brian Fundakowski Feldman wrote: > On Tue, Apr 19, 2005 at 06:09:00PM +0200, Marc Olzheim wrote: > > On Tue, Apr 19, 2005 at 06:02:58PM +0200, Marc Olzheim wrote: > > > On Tue, Apr 19, 2005 at 11:18:00AM -0400, Brian Fundakowski Feldman wrote: > > > > Does this work for you? > > > > > > ... > > > > > > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror /usr/src/sys/nfsclient/nfs_bio.c > > > /usr/src/sys/nfsclient/nfs_bio.c: In function `nfs_write': > > > /usr/src/sys/nfsclient/nfs_bio.c:976: error: invalid type argument of `->' > > > /usr/src/sys/nfsclient/nfs_bio.c:976: error: invalid type argument of `->' > > > /usr/src/sys/nfsclient/nfs_bio.c:984: error: invalid type argument of `->' > > > /usr/src/sys/nfsclient/nfs_bio.c:984: error: invalid type argument of `->' > > > *** Error code 1 > > > > That's about the BO_LOCK(vp->v_bufobj); and the BO_UNLOCK(vp->v_bufobj); > > Yeah, I get that too. I have no clue why it's doing that, I was figuring > it was just my compile setup... Okay, stupid me. This compiles. cvs diff: Diffing sys Index: sys/buf.h =================================================================== RCS file: /usr/ncvs/src/sys/sys/buf.h,v retrieving revision 1.185 diff -u -u -r1.185 buf.h --- sys/buf.h 10 Feb 2005 12:17:48 -0000 1.185 +++ sys/buf.h 19 Apr 2005 14:30:54 -0000 @@ -465,6 +465,7 @@ extern int maxswzone; /* Max KVA for swap structures */ extern int maxbcache; /* Max KVA for buffer cache */ extern int runningbufspace; +extern int hibufspace; extern int buf_maxio; /* nominal maximum I/O for buffer */ extern struct buf *buf; /* The buffer headers. */ extern char *buffers; /* The buffer contents. */ Index: sys/bufobj.h =================================================================== RCS file: /usr/ncvs/src/sys/sys/bufobj.h,v retrieving revision 1.13 diff -u -u -r1.13 bufobj.h --- sys/bufobj.h 19 Feb 2005 11:44:57 -0000 1.13 +++ sys/bufobj.h 19 Apr 2005 20:39:10 -0000 @@ -109,13 +109,13 @@ #define BO_LOCK(bo) \ do { \ - KASSERT (bo->bo_mtx != NULL, ("No lock in bufobj")); \ + KASSERT((bo)->bo_mtx != NULL, ("No lock in bufobj")); \ mtx_lock((bo)->bo_mtx); \ } while (0) #define BO_UNLOCK(bo) \ do { \ - KASSERT (bo->bo_mtx != NULL, ("No lock in bufobj")); \ + KASSERT((bo)->bo_mtx != NULL, ("No lock in bufobj")); \ mtx_unlock((bo)->bo_mtx); \ } while (0) cvs diff: Diffing kern Index: kern/vfs_bio.c =================================================================== RCS file: /usr/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.482 diff -u -u -r1.482 vfs_bio.c --- kern/vfs_bio.c 25 Mar 2005 00:20:37 -0000 1.482 +++ kern/vfs_bio.c 19 Apr 2005 14:30:54 -0000 @@ -127,7 +127,7 @@ static int lobufspace; SYSCTL_INT(_vfs, OID_AUTO, lobufspace, CTLFLAG_RD, &lobufspace, 0, "Minimum amount of buffers we want to have"); -static int hibufspace; +int hibufspace; SYSCTL_INT(_vfs, OID_AUTO, hibufspace, CTLFLAG_RD, &hibufspace, 0, "Maximum allowed value of bufspace (excluding buf_daemon)"); static int bufreusecnt; cvs diff: Diffing nfsclient Index: nfsclient/nfs_bio.c =================================================================== RCS file: /usr/ncvs/src/sys/nfsclient/nfs_bio.c,v retrieving revision 1.150 diff -u -u -r1.150 nfs_bio.c --- nfsclient/nfs_bio.c 18 Mar 2005 21:23:32 -0000 1.150 +++ nfsclient/nfs_bio.c 19 Apr 2005 20:38:34 -0000 @@ -844,6 +844,7 @@ struct vattr vattr; struct nfsmount *nmp = VFSTONFS(vp->v_mount); daddr_t lbn; + off_t commitleft; /* if non-zero, the amount left we may write */ int bcount; int n, on, error = 0; int haverslock = 0; @@ -873,6 +874,14 @@ */ if (ioflag & (IO_APPEND | IO_SYNC)) { if (np->n_flag & NMODIFIED) { +flush_and_restart: + /* + * Require non-blocking, synchronous writes to + * dirty files to inform the program it needs + * to fsync(2) explicitly. + */ + if (ioflag & IO_NDELAY) + return (EAGAIN); np->n_attrstamp = 0; error = nfs_vinvalbuf(vp, V_SAVE, td, 1); if (error) @@ -953,12 +962,65 @@ } biosize = vp->v_mount->mnt_stat.f_iosize; + commitleft = 0; + /* + * If there are possible modifications, find all of this file's + * B_NEEDCOMMIT buffers. If our writes would exceed the local + * maximum per-file write commit size when combined with those, + * we decide to flush and/or do a short write. + */ + if ((ioflag & (IO_SYNC | IO_INVAL)) != (IO_SYNC | IO_INVAL)) { + commitleft = nmp->nm_wcommitsize; + if (np->n_flag & NMODIFIED) { + int wouldcommit = 0; + BO_LOCK(&vp->v_bufobj); + if (vp->v_bufobj.bo_dirty.bv_cnt != 0) { + TAILQ_FOREACH(bp, &vp->v_bufobj.bo_dirty.bv_hd, + b_bobufs) { + if (bp->b_flags & B_NEEDCOMMIT) + wouldcommit += bp->b_bcount; + } + } + BO_UNLOCK(&vp->v_bufobj); + /* + * Since we're not operating synchronously and + * bypassing the buffer cache, we are in a commit + * and holding all of these buffers whether + * transmitted or not. If not limited, this + * will lead to the buffer cache deadlocking, + * as no one else can flush our uncommitted buffers. + */ + wouldcommit += uio->uio_resid; + /* + * If we would initially exceed the maximum + * outstanding write commit size, flush and restart. + */ + if (wouldcommit > commitleft) { + if (haverslock) { + nfs_rsunlock(np, td); + haverslock = 0; + } + goto flush_and_restart; + } + } else { + /* + * With no outstanding commits, we are limited only + * by commitleft as to how far we can go. + */ + } + } do { nfsstats.biocache_writes++; lbn = uio->uio_offset / biosize; on = uio->uio_offset & (biosize-1); n = min((unsigned)(biosize - on), uio->uio_resid); + /* Always allow at least the very first write. */ + if (commitleft > 0) { + commitleft -= n; + if (commitleft == 0) + commitleft = -1; + } again: /* * Handle direct append and file extension cases, calculate @@ -1146,10 +1208,21 @@ } else { bdwrite(bp); } - } while (uio->uio_resid > 0 && n > 0); + } while (uio->uio_resid > 0 && n > 0 && commitleft >= 0); - if (haverslock) + if (haverslock) { + haverslock = 0; nfs_rsunlock(np, td); + } + + /* + * On the off chance that we're trying to do a very large + * and non-atomic write, go ahead and let that just continue + * within the same call after flushing out what's been written. + */ + if (error == 0 && uio->uio_resid > 0 && n > 0 && commitleft < 0 && + !(ioflag & IO_UNIT)) + goto flush_and_restart; return (error); } Index: nfsclient/nfs_vfsops.c =================================================================== RCS file: /usr/ncvs/src/sys/nfsclient/nfs_vfsops.c,v retrieving revision 1.172 diff -u -u -r1.172 nfs_vfsops.c --- nfsclient/nfs_vfsops.c 24 Mar 2005 07:37:22 -0000 1.172 +++ nfsclient/nfs_vfsops.c 19 Apr 2005 14:32:19 -0000 @@ -41,6 +41,8 @@ #include #include #include +#include +#include #include #include #include @@ -626,6 +628,12 @@ else nmp->nm_readahead = NFS_MAXRAHEAD; } + if ((argp->flags & NFSMNT_WCOMMITSIZE) && argp->wcommitsize >= 0) { + if (argp->wcommitsize < nmp->nm_wsize) + nmp->nm_wcommitsize = nmp->nm_wsize; + else + nmp->nm_wcommitsize = argp->wcommitsize; + } if ((argp->flags & NFSMNT_DEADTHRESH) && argp->deadthresh >= 0) { if (argp->deadthresh <= NFS_MAXDEADTHRESH) nmp->nm_deadthresh = argp->deadthresh; @@ -808,6 +816,7 @@ nmp->nm_wsize = NFS_WSIZE; nmp->nm_rsize = NFS_RSIZE; } + nmp->nm_wcommitsize = hibufspace / (desiredvnodes / 1000); nmp->nm_readdirsize = NFS_READDIRSIZE; nmp->nm_numgrps = NFS_MAXGRPS; nmp->nm_readahead = NFS_DEFRAHEAD; Index: nfsclient/nfsargs.h =================================================================== RCS file: /usr/ncvs/src/sys/nfsclient/nfsargs.h,v retrieving revision 1.67 diff -u -u -r1.67 nfsargs.h --- nfsclient/nfsargs.h 7 Jan 2005 01:45:51 -0000 1.67 +++ nfsclient/nfsargs.h 19 Apr 2005 14:30:54 -0000 @@ -56,7 +56,7 @@ int retrans; /* times to retry send */ int maxgrouplist; /* Max. size of group list */ int readahead; /* # of blocks to readahead */ - int __pad1; /* was "leaseterm" */ + int wcommitsize; /* Max. write commit size in bytes */ int deadthresh; /* Retrans threshold */ char *hostname; /* server's name */ int acregmin; /* cache attrs for reg files min time */ @@ -80,7 +80,7 @@ #define NFSMNT_NFSV3 0x00000200 /* Use NFS Version 3 protocol */ /* 0x400 free, was NFSMNT_KERB */ #define NFSMNT_DUMBTIMR 0x00000800 /* Don't estimate rtt dynamically */ -/* 0x1000 free, was NFSMNT_LEASETERM */ +#define NFSMNT_WCOMMITSIZE 0x00001000 /* set max write commit size */ #define NFSMNT_READAHEAD 0x00002000 /* set read ahead */ #define NFSMNT_DEADTHRESH 0x00004000 /* set dead server retry thresh */ #define NFSMNT_RESVPORT 0x00008000 /* Allocate a reserved port */ Index: nfsclient/nfsmount.h =================================================================== RCS file: /usr/ncvs/src/sys/nfsclient/nfsmount.h,v retrieving revision 1.29 diff -u -u -r1.29 nfsmount.h --- nfsclient/nfsmount.h 7 Jan 2005 01:45:51 -0000 1.29 +++ nfsclient/nfsmount.h 19 Apr 2005 14:30:54 -0000 @@ -74,6 +74,7 @@ int nm_wsize; /* Max size of write rpc */ int nm_readdirsize; /* Size of a readdir rpc */ int nm_readahead; /* Num. of blocks to readahead */ + int nm_wcommitsize; /* Max size of commit for write */ int nm_acdirmin; /* Directory attr cache min lifetime */ int nm_acdirmax; /* Directory attr cache max lifetime */ int nm_acregmin; /* Reg file attr cache min lifetime */ -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 05:07:36 2005 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 A90E116A4CE for ; Wed, 20 Apr 2005 05:07:36 +0000 (GMT) Received: from smtp3.hushmail.com (smtp3.hushmail.com [65.39.178.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 761B743D53 for ; Wed, 20 Apr 2005 05:07:36 +0000 (GMT) (envelope-from james@divide.org) Received: from smtp3.hushmail.com (localhost.hushmail.com [127.0.0.1]) by smtp3.hushmail.com (Postfix) with SMTP id EA1C9A3380 for ; Tue, 19 Apr 2005 22:07:35 -0700 (PDT) Received: from mailserver1.hushmail.com (mailserver1host.hushmail.com [65.39.178.45]) by smtp3.hushmail.com (Postfix) with ESMTP for ; Tue, 19 Apr 2005 22:07:35 -0700 (PDT) Received: (from nobody@localhost) by mailserver1.hushmail.com (8.12.8p1/8.12.8/Submit) id j3K57ZZV033777 for freebsd-hackers@freebsd.org; Tue, 19 Apr 2005 22:07:35 -0700 (PDT) Message-Id: <200504200507.j3K57ZZV033777@mailserver1.hushmail.com> Date: Tue, 19 Apr 2005 22:07:31 -0700 To: freebsd-hackers@freebsd.org Cc: From: "James Thomason" Subject: Re: linux call_usermodehelper equivalent in freebsd? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: james@divide.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2005 05:07:37 -0000 >Is there an equivalent in FreeBSD to the Linux kernel function >'call_usermodehelper' which wraps execve to do as its name >suggests, call a user mode helper program? Andrew, It depends on what your user mode helper program is intended to do, but the traditional approach is to create a user mode program that blocks on a custom system call waiting for an event. See the following 2001 freebsd-hackers thread from Terry Lambert, titled "Invoking a userland function from kernel" for further details and design considerations: http://docs.freebsd.org/cgi/mid.cgi?3B646AAB.688669C5 Regards, James From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 06:26:32 2005 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 21E8116A4CE for ; Wed, 20 Apr 2005 06:26:32 +0000 (GMT) Received: from mail.fci.fsu.edu (mail.fci.fsu.edu [128.186.195.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id E175B43D1D for ; Wed, 20 Apr 2005 06:26:31 +0000 (GMT) (envelope-from neuro@mail.fci.fsu.edu) Received: from mail.fci.fsu.edu (mail.fci.fsu.edu [127.0.0.1]) by mail.fci.fsu.edu (Postfix) with ESMTP id 1AA8729216A for ; Wed, 20 Apr 2005 02:24:14 -0400 (EDT) Date: Wed, 20 Apr 2005 02:24:14 -0400 (EDT) From: neuro@mail.fci.fsu.edu To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: kernel programming 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, 20 Apr 2005 06:26:32 -0000 where's a good place for kernel programming documentation ? From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 06:27:53 2005 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 2DF0416A4CE for ; Wed, 20 Apr 2005 06:27:53 +0000 (GMT) Received: from mail.fci.fsu.edu (mail.fci.fsu.edu [128.186.195.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1BA043D31 for ; Wed, 20 Apr 2005 06:27:52 +0000 (GMT) (envelope-from neuro@mail.fci.fsu.edu) Received: from mail.fci.fsu.edu (mail.fci.fsu.edu [127.0.0.1]) by mail.fci.fsu.edu (Postfix) with ESMTP id 2CB1629216A for ; Wed, 20 Apr 2005 02:25:35 -0400 (EDT) Date: Wed, 20 Apr 2005 02:25:35 -0400 (EDT) From: neuro@mail.fci.fsu.edu To: freebsd-hackers@freebsd.org In-Reply-To: <741675355.1113978425415.JavaMail.nobody@app6.ni.bg> Message-ID: References: <741675355.1113978425415.JavaMail.nobody@app6.ni.bg> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: =?windows-1251?b?QUJWLkJHIODi8u7s4PLo9+XtIO7y4+7i7vA=?= 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, 20 Apr 2005 06:27:53 -0000 i'm not sure i understnad that language ? if you tell me which one it is I could use googles convertor --neuro On Wed, 20 Apr 2005 freebsd-hackers@freebsd.org wrote: > blagodarq za izpratenoto ot Vas pismo nai skoro shte vi otgovorq!! > From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 06:48:31 2005 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 B94D316A4CE for ; Wed, 20 Apr 2005 06:48:31 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4285343D39 for ; Wed, 20 Apr 2005 06:48:31 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by rproxy.gmail.com with SMTP id c51so61463rne for ; Tue, 19 Apr 2005 23:48:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NGj8NM6E2fug+7E5X3v+5NOPcY4TbDhQ67FRVXvbAOnh4cGaabu3VJiU6H9gg8Dpbog0mhhf/KCR0qIN0y5wAfU/fTrpJ6e6VnjOEp68QZC2p0+gSYGku02/MWNHrbqARvt7JsPMaZ3m8SeD3BHjanQzEwGn2xRgRz3hdai2mX4= Received: by 10.38.15.7 with SMTP id 7mr529703rno; Tue, 19 Apr 2005 23:48:30 -0700 (PDT) Received: by 10.38.209.22 with HTTP; Tue, 19 Apr 2005 23:48:30 -0700 (PDT) Message-ID: <84dead72050419234842fd1954@mail.gmail.com> Date: Wed, 20 Apr 2005 06:48:30 +0000 From: Joseph Koshy To: "neuro@mail.fci.fsu.edu" In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: cc: freebsd-hackers@freebsd.org Subject: Re: kernel programming X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joseph Koshy List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2005 06:48:31 -0000 > where's a good place for kernel programming documentation ? In no particular order: 1. The FreeBSD Developer's Handbook. 2. The FreeBSD Architecture Handbook. 3. The book 'The Design and Implementation of the FreeBSD Operating System', by Kirk McKusick and George Neville-Neil. 3. The section 9 manual pages. 4. The source code :). You may want to browse: http://www.freebsd.org/docs.html --=20 FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 06:50:53 2005 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 AFF3E16A4CE for ; Wed, 20 Apr 2005 06:50:53 +0000 (GMT) Received: from mail.fci.fsu.edu (mail.fci.fsu.edu [128.186.195.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76DBD43D54 for ; Wed, 20 Apr 2005 06:50:53 +0000 (GMT) (envelope-from neuro@mail.fci.fsu.edu) Received: from mail.fci.fsu.edu (mail.fci.fsu.edu [127.0.0.1]) by mail.fci.fsu.edu (Postfix) with ESMTP id 86C3829216A; Wed, 20 Apr 2005 02:48:35 -0400 (EDT) Date: Wed, 20 Apr 2005 02:48:35 -0400 (EDT) From: neuro@mail.fci.fsu.edu To: Joseph Koshy In-Reply-To: <84dead72050419234842fd1954@mail.gmail.com> Message-ID: References: <84dead72050419234842fd1954@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-hackers@freebsd.org Subject: Re: kernel programming 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, 20 Apr 2005 06:50:53 -0000 yeah thanks for that, i figured the code was a good start. Now that I know the docs i know where to go, cheers for that --neuro On Wed, 20 Apr 2005, Joseph Koshy wrote: >> where's a good place for kernel programming documentation ? > > In no particular order: > > 1. The FreeBSD Developer's Handbook. > 2. The FreeBSD Architecture Handbook. > 3. The book 'The Design and Implementation of the FreeBSD > Operating System', by Kirk McKusick and George > Neville-Neil. > 3. The section 9 manual pages. > 4. The source code :). > > You may want to browse: http://www.freebsd.org/docs.html > > -- > FreeBSD Volunteer, http://people.freebsd.org/~jkoshy > From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 08:22:15 2005 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 EBB7316A4CE for ; Wed, 20 Apr 2005 08:22:14 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88ABA43D46 for ; Wed, 20 Apr 2005 08:22:14 +0000 (GMT) (envelope-from valenok@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so76916wri for ; Wed, 20 Apr 2005 01:22:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=Y18WlfN1/DNS0ughS4N5H8gufU86dYW0bCD87I/S2ETCUB1D6abpQVJGylMrWTQF0XYzX+hmySEVG7dp7XoW2kpl6gd82kuX6KCPRm+cBWLTRhu7VtSWVAlX5xfwcKt5qcikvYMJyLFlAPvBAY3IC0xzeuvsqAw2JtUuszCb840= Received: by 10.54.53.53 with SMTP id b53mr148177wra; Wed, 20 Apr 2005 01:22:13 -0700 (PDT) Received: by 10.54.44.57 with HTTP; Wed, 20 Apr 2005 01:22:13 -0700 (PDT) Message-ID: <72c3a95705042001227812f6e6@mail.gmail.com> Date: Wed, 20 Apr 2005 08:22:13 +0000 From: Sergey Lyubka To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1250_18247984.1113985333807" Subject: transparent squid proxy + bridge X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Sergey Lyubka List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2005 08:22:15 -0000 ------=_Part_1250_18247984.1113985333807 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi there, Recently I tried to make a transparent web proxy on a machine that run in bridging mode. At last, I decided to make a patch. Here it is for those who want to do the same. One interface should be given an IP address so squid may do a requests. Squid listens on 127.0.0.1:8080. I am using pf firewall, with this redirection rule: rdr on $int proto tcp from any to any port 80 -> (lo0) port 8080 This is what the patch does: static void ether_input() { ... if (packet_is_IP_packet && pf_enabled && mbuf_copy =3D copy_the_mbuf) { strip_ethernet_headers; run_the_firewall; if (packet_redirected_to_127.0.0.1) bypass_the_bridge free_the_mbuf_copy; } ... } The patch is small, so I include it inline. Tested on 5.4 ------=_Part_1250_18247984.1113985333807 Content-Type: application/octet-stream; name="if_ethersubr.c.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="if_ethersubr.c.patch" LS0tIC91c3Ivc3JjL3N5cy9uZXQvaWZfZXRoZXJzdWJyLmMub3JpZwlUaHUgTWFyIDMxIDE0OjU4 OjM2IDIwMDUKKysrIC91c3Ivc3JjL3N5cy9uZXQvaWZfZXRoZXJzdWJyLmMJVHVlIEFwciAxOSAx Mzo1MDowNSAyMDA1CkBAIC02Niw4ICs2NiwxMCBAQAogI2lmIGRlZmluZWQoSU5FVCkgfHwgZGVm aW5lZChJTkVUNikKICNpbmNsdWRlIDxuZXRpbmV0L2luLmg+CiAjaW5jbHVkZSA8bmV0aW5ldC9p bl92YXIuaD4KKyNpbmNsdWRlIDxuZXRpbmV0L2luX3N5c3RtLmg+CiAjaW5jbHVkZSA8bmV0aW5l dC9pZl9ldGhlci5oPgogI2luY2x1ZGUgPG5ldGluZXQvaXBfZncuaD4KKyNpbmNsdWRlIDxuZXRp bmV0L2lwLmg+CiAjaW5jbHVkZSA8bmV0aW5ldC9pcF9kdW1teW5ldC5oPgogI2VuZGlmCiAjaWZk ZWYgSU5FVDYKQEAgLTQ4NSw2ICs0ODcsOCBAQAogfQogI2VuZGlmCiAKKyNpbmNsdWRlIDxuZXQv cGZpbC5oPgorZXh0ZXJuIHN0cnVjdCBwZmlsX2hlYWQgaW5ldF9wZmlsX2hvb2s7CiAvKgogICog UHJvY2VzcyBhIHJlY2VpdmVkIEV0aGVybmV0IHBhY2tldDsgdGhlIHBhY2tldCBpcyBpbiB0aGUK ICAqIG1idWYgY2hhaW4gbSB3aXRoIHRoZSBldGhlcm5ldCBoZWFkZXIgYXQgdGhlIGZyb250LgpA QCAtNDkzLDcgKzQ5Nyw5IEBACiBldGhlcl9pbnB1dChzdHJ1Y3QgaWZuZXQgKmlmcCwgc3RydWN0 IG1idWYgKm0pCiB7CiAJc3RydWN0IGV0aGVyX2hlYWRlciAqZWg7CisJc3RydWN0IG1idWYgKm0y OwogCXVfc2hvcnQgZXR5cGU7CisJaW50IHRvbG9jYWwgPSAwOwogCiAJLyoKIAkgKiBEbyBjb25z aXN0ZW5jeSBjaGVja3MgdG8gdmVyaWZ5IGFzc3VtcHRpb25zCkBAIC01NzYsOCArNTgyLDUwIEBA CiAJCQlyZXR1cm47CiAJfQogCisjaWYgMQorCS8qKioqKioqKioqKioqKiogVUdMWSBIQUNLICEh ICoqKioqKioqKioqKioqKioqKiovCisJaWYgKGV0eXBlID09IDB4ODAwICYmCisJICAgIGluZXRf cGZpbF9ob29rLnBoX2J1c3lfY291bnQgIT0gLTEgJiYKKwkgICAgKG0yID0gbV9kdXAobSwgTV9E T05UV0FJVCkpICE9IE5VTEwpIHsKKwkJc3RydWN0IGlwICppcDsKKwkJCisJCW1fYWRqKG0yLCBF VEhFUl9IRFJfTEVOKTsJLyogcmVtb3ZlIGV0aGVyIGhkciAqLworCQlpcCA9IG10b2QobTIsIHN0 cnVjdCBpcCAqKTsKKworCQlpcC0+aXBfbGVuID0gbnRvaHMoaXAtPmlwX2xlbik7CisJCWlwLT5p cF9vZmYgPSBudG9ocyhpcC0+aXBfb2ZmKTsJCQorCQkKKwkJaWYgKG0yLT5tX3BrdGhkci5sZW4g PiBpcC0+aXBfbGVuKSB7CisJCQlpZiAobTItPm1fbGVuID09IG0yLT5tX3BrdGhkci5sZW4pIHsK KwkJCQltMi0+bV9sZW4gPSBpcC0+aXBfbGVuOworCQkJCW0yLT5tX3BrdGhkci5sZW4gPSBpcC0+ aXBfbGVuOworCQkJfSBlbHNlCisJCQkJbV9hZGoobTIsIGlwLT5pcF9sZW4gLSBtMi0+bV9wa3Ro ZHIubGVuKTsKKwkJfQorCQkKKwkJaWYgKHBmaWxfcnVuX2hvb2tzKCZpbmV0X3BmaWxfaG9vaywg Jm0yLCBtMi0+bV9wa3RoZHIucmN2aWYsCisJCSAgICBQRklMX0lOLCBOVUxMKSAhPSAwKSB7CisJ CQltX2ZyZWVtKG0pOworCQkJcmV0dXJuOworCQl9CisKKwkJaWYgKG0yID09IE5VTEwpCXsKKwkJ CW1fZnJlZW0obSk7CisJCQlyZXR1cm47CisJCX0KKwkJCisJCWlwID0gbXRvZChtMiwgc3RydWN0 IGlwICopOworCQlpZiAoaXAtPmlwX2RzdC5zX2FkZHIgPT0gbnRvaGwoSU5BRERSX0xPT1BCQUNL KSkKKwkJCXRvbG9jYWwgPSAxOworCisJCQorCQltX2ZyZWVtKG0yKTsKKwl9CisJLyoqKioqKioq KioqKioqKiBFTkQgT0YgVUdMWSBIQUNLICoqKioqKioqKioqKioqKioqKiovCisjZW5kaWYKKwog CS8qIENoZWNrIGZvciBicmlkZ2luZyBtb2RlICovCi0JaWYgKEJER19BQ1RJVkUoaWZwKSApIHsK KwlpZiAoQkRHX0FDVElWRShpZnApICYmIHRvbG9jYWwgPT0gMCkgewogCQlzdHJ1Y3QgaWZuZXQg KmJpZjsKIAogCQkvKgo= ------=_Part_1250_18247984.1113985333807-- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 08:24:26 2005 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 01C2016A4CE; Wed, 20 Apr 2005 08:24:26 +0000 (GMT) Received: from mx.laposte.net (mx.laposte.net [81.255.54.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A21E43D1F; Wed, 20 Apr 2005 08:24:25 +0000 (GMT) (envelope-from emmanuel.chriqui@laposte.net) Received: from pcemmanuel (81.57.219.151) by mx.laposte.net (7.0.028) (authenticated as emmanuel.chriqui) id 425309CA008BDE83; Wed, 20 Apr 2005 10:24:06 +0200 Message-ID: <425309CA008BDE83@lpdnpm09.laposte.net> (added by postmaster@laposte.net) From: "Emmanuel Chriqui" To: "'David G. Lawrence'" Date: Wed, 20 Apr 2005 10:24:26 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <20050419231817.GM31779@opteron.dglawrence.com> Thread-index: AcVFNkZO1Jd/6B1DTf26Q3ITGoUoEwAS7lXg cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: RE: PXEBOOT/TFTPBOOT + big MD_ROOT problem 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, 20 Apr 2005 08:24:26 -0000 > Objet=A0: Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem >=20 > > Hi, > > > > I'm trying to make very big MD_ROOT (300MB) sent using = PXEBOOT+TFTPBOOT. > No > > NFS. It's a sort of diskless machine with all the system on ram. = There > is a > > problem when the preloaded image is >~32MB. Kernel loads but it does = not > > seem to find the files. It seems as if only part of the image is = really > > there. With a "small" image (<~32MB), no probleme. I use the same = image, > off > > course, same init etc... just more data for my application in the = big > image > > case. > ... > > Am I missing something obvious? >=20 > I assume you saw this in the tftpd manual page? >=20 > BUGS > Files larger than 33488896 octets (65535 blocks) cannot be > transferred > without client and server supporting blocksize negotiation = (RFC1783). >=20 > Many tftp clients will not transfer files over 16744448 octets = (32767 > blocks). >=20 >=20 > -DG Yes. Saw it. My tftp client and pxe+tftp under linux works ok. The tftp client under FreeBSD seems to work fine (1,5GB tranfered, md5sum = checked, no pb). BUT, maybe the tftp client in the FreeBSD pxeboot has a problem. I am actually trying to make the mfsroot go through NFS. If that works, = it will indicate the FreeBSD pxeboot has indeed this problem with TFTP. Emmanuel. From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 19:29:04 2005 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 E0A5A16A4CE; Tue, 19 Apr 2005 19:29:04 +0000 (GMT) Received: from server.t-hosting.hu (server.t-hosting.hu [217.20.133.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63CC543D4C; Tue, 19 Apr 2005 19:29:04 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from localhost (localhost [127.0.0.1]) by server.t-hosting.hu (Postfix) with ESMTP id B4FC69975C2; Tue, 19 Apr 2005 21:34:33 +0200 (CEST) Received: from server.t-hosting.hu ([127.0.0.1]) by localhost (server.t-hosting.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 07873-01-2; Tue, 19 Apr 2005 21:34:33 +0200 (CEST) Received: from [80.98.207.149] (catv-5062cf95.catv.broadband.hu [80.98.207.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by server.t-hosting.hu (Postfix) with ESMTP id 24967997415; Tue, 19 Apr 2005 21:34:33 +0200 (CEST) Message-ID: <42655BE6.5020108@t-hosting.hu> Date: Tue, 19 Apr 2005 21:28:38 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marc Olzheim , wingman@waika9.com References: <20050419075158.6444A31931C@postfix4-2.free.fr> <20050419190557.GA82027@stack.nl> In-Reply-To: <20050419190557.GA82027@stack.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at t-hosting.hu X-Mailman-Approved-At: Wed, 20 Apr 2005 12:01:55 +0000 cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem 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, 19 Apr 2005 19:29:05 -0000 Marc Olzheim wrote: >On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote: > > >>Hi, >> >>I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No >>NFS. >> >> > >Any reasons for not using NFS ? > > > >>I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . >>(same pb with a 5.3). >> >>Am I missing something obvious? >> >> > >I'm not sure. tftp itself is able to handle 32MB+ files, but maybe the >loader isn't. > >A workaround, no using NFS, could be to tftp a second filesystem image >on boot and mount that from the root filesystem. > >Marc > > I assume that the PXE clients are diskless clients. If so, do they have enough memory to handle this extremely large image? As for tfpt, it uses UDP. UDP is usually used for transfer small datagrams, for instance DNS replies. It is also said to be an unreliable protocol. The client should repeat the request when no data receives. I doubt this solution is reliable and flexible enough. My idea for a workaround is creating a ramdisk from a small boot image, and transfer the less necessary userland binaries from the boot server to the ramdisk using normal ftp connection. Cheers, G醔or K鰒esd醤 From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 21:27:27 2005 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 D2BF216A4CE; Tue, 19 Apr 2005 21:27:27 +0000 (GMT) Received: from grant.org (grant.org [206.190.173.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D16643D55; Tue, 19 Apr 2005 21:27:27 +0000 (GMT) (envelope-from Devon@Jovi.Net) Received: from grant.org (localhost [127.0.0.1]) by grant.org (8.12.11/8.12.11) with ESMTP id j3JLRDMF055799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Apr 2005 17:27:13 -0400 (EDT) (envelope-from Devon@Jovi.Net) Received: (from devon@localhost) by grant.org (8.12.11/8.12.11/Submit) id j3JLR9Oq055796; Tue, 19 Apr 2005 17:27:09 -0400 (EDT) (envelope-from Devon@Jovi.Net) Date: Tue, 19 Apr 2005 17:27:09 -0400 (EDT) Message-Id: <200504192127.j3JLR9Oq055796@grant.org> X-Authentication-Warning: grant.org: devon set sender to Devon@Jovi.Net using -f From: Devon Sean McCullough To: , X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on grant.org X-Virus-Scanned: by amavisd-new X-Mailman-Approved-At: Wed, 20 Apr 2005 12:01:55 +0000 cc: Steven Hartland Subject: sshd dieing? after applying FreeBSD-SA-03:12.openssh 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, 19 Apr 2005 21:27:27 -0000 On Wed, 17 Sep 2003 00:02:33 +0100 Steven Hartland asked this question but no answer was posted. The trouble is likely no client reverse DNS either because it is missing or slow. Adding the client to /etc/hosts on the server seems at first to do nothing but after a minute or so it stops hanging and asks for a password. Could be a coincidence though. To recap: $ ssh -v me@my-freebsd-5.1-RELEASE-box OpenSSH_3.4p1+CAN-2004-0175, SSH protocols 1.5/2.0, OpenSSL 0x0090609f ... debug1: Remote protocol version 1.99, remote software version OpenSSH_3.6.1p1 FreeBSD-20030423 debug1: match: OpenSSH_3.6.1p1 FreeBSD-20030423 pat OpenSSH* Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.4p1+CAN-2004-0175 ... debug1: got SSH2_MSG_SERVICE_ACCEPT <---Here the client hangs until timeout. To debug: kill the server process and run # sshd -ddde ... debug3: Trying to reverse map address ... <---Here the server hangs until timeout. From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 19 23:18:35 2005 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 EB8C416A4CE; Tue, 19 Apr 2005 23:18:35 +0000 (GMT) Received: from dglawrence.com (dsl-230-156.ipns.com [209.210.230.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 615C343D45; Tue, 19 Apr 2005 23:18:33 +0000 (GMT) (envelope-from dg@dglawrence.com) Received: from opteron.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.13.3/8.13.1) with ESMTP id j3JNISup068574; Tue, 19 Apr 2005 16:18:28 -0700 (PDT) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by opteron.dglawrence.com (8.13.3/8.13.1/Submit) id j3JNIHik068573; Tue, 19 Apr 2005 16:18:17 -0700 (PDT) (envelope-from dg@dglawrence.com) Date: Tue, 19 Apr 2005 16:18:17 -0700 From: "David G. Lawrence" To: Emmanuel Chriqui Message-ID: <20050419231817.GM31779@opteron.dglawrence.com> References: <20050419075158.6444A31931C@postfix4-2.free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050419075158.6444A31931C@postfix4-2.free.fr> X-Mailman-Approved-At: Wed, 20 Apr 2005 12:01:55 +0000 cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem 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, 19 Apr 2005 23:18:36 -0000 > Hi, > > I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No > NFS. It's a sort of diskless machine with all the system on ram. There is a > problem when the preloaded image is >~32MB. Kernel loads but it does not > seem to find the files. It seems as if only part of the image is really > there. With a "small" image (<~32MB), no probleme. I use the same image, off > course, same init etc... just more data for my application in the big image > case. ... > Am I missing something obvious? I assume you saw this in the tftpd manual page? BUGS Files larger than 33488896 octets (65535 blocks) cannot be transferred without client and server supporting blocksize negotiation (RFC1783). Many tftp clients will not transfer files over 16744448 octets (32767 blocks). -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 05:17:29 2005 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 CC6FA16A4CE for ; Wed, 20 Apr 2005 05:17:29 +0000 (GMT) Received: from hotmail.com (bay2-f38.bay2.hotmail.com [65.54.247.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA97F43D49 for ; Wed, 20 Apr 2005 05:17:29 +0000 (GMT) (envelope-from jas_arlerr@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 19 Apr 2005 22:17:27 -0700 Message-ID: Received: from 61.187.54.13 by by2fd.bay2.hotmail.msn.com with HTTP; Wed, 20 Apr 2005 05:17:27 GMT X-Originating-IP: [61.187.54.13] X-Originating-Email: [jas_arlerr@hotmail.com] X-Sender: jas_arlerr@hotmail.com From: =?gb2312?B?1cUgt+c=?= To: freebsd-hackers@freebsd.org Date: Wed, 20 Apr 2005 05:17:27 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed X-OriginalArrivalTime: 20 Apr 2005 05:17:27.0622 (UTC) FILETIME=[3E6DB660:01C54568] X-Mailman-Approved-At: Wed, 20 Apr 2005 12:01:55 +0000 Subject: Configuration differences for jails 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, 20 Apr 2005 05:17:29 -0000 Hi, I am now trying to use jail in FreeBSD. I have read the jail(8) man page and some others documents for setting up jails. But I'm a little confused about the procedure and configurations for setting up jails. As known to all, jail can be used for two purposes, i.e. jailing a single application or acting as a virtual host. What i want to know is the concrete configuration (procedure) difference between the two types use of jails. Is there a SMALLEST set of configuration necessary for setting up a jail? If so, what is it? Another question, is there any way to detect the share of files between multiple jails automatically? BTW, what is the meaning of "IMHO"? :) It appears very frequently in the mail list. Sorry for my bad english. Any reply is appreciated! Jas _________________________________________________________________ 与世界各地的朋友进行交流，免费下载 MSN Messenger: http://messenger.msn.com/cn From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 07:07:44 2005 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 6B6D916A4CE; Wed, 20 Apr 2005 07:07:44 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id A341F43D62; Wed, 20 Apr 2005 07:07:42 +0000 (GMT) (envelope-from ftigeot@wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.13.3/8.13.3) with ESMTP id j3K77H2S039562; Wed, 20 Apr 2005 09:07:17 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.3/8.13.1) with ESMTP id j3K77O38033065; Wed, 20 Apr 2005 09:07:24 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.3/8.13.1/Submit) id j3K77ERA033064; Wed, 20 Apr 2005 09:07:14 +0200 (CEST) (envelope-from ftigeot) Date: Wed, 20 Apr 2005 09:07:14 +0200 From: Francois Tigeot To: "David G. Lawrence" Message-ID: <20050420070713.GA32649@aoi.wolfpond.org> References: <20050419075158.6444A31931C@postfix4-2.free.fr> <20050419231817.GM31779@opteron.dglawrence.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050419231817.GM31779@opteron.dglawrence.com> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Wed, 20 Apr 2005 12:01:55 +0000 cc: Emmanuel Chriqui cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem 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, 20 Apr 2005 07:07:44 -0000 On Tue, Apr 19, 2005 at 04:18:17PM -0700, David G. Lawrence wrote: > > I assume you saw this in the tftpd manual page? > > BUGS > Files larger than 33488896 octets (65535 blocks) cannot be transferred > without client and server supporting blocksize negotiation (RFC1783). > > Many tftp clients will not transfer files over 16744448 octets (32767 > blocks). There is a PR open with a patch to fix this: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/67550 -- Francois Tigeot From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 12:33:39 2005 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 2237F16A4CE; Wed, 20 Apr 2005 12:33:39 +0000 (GMT) Received: from mxsf19.cluster1.charter.net (mxsf19.cluster1.charter.net [209.225.28.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DD1A43D46; Wed, 20 Apr 2005 12:33:38 +0000 (GMT) (envelope-from c0ldbyte@myrealbox.com) Received: from mxip17.cluster1.charter.net (mxip17a.cluster1.charter.net [209.225.28.147])j3KCXbXf010331; Wed, 20 Apr 2005 08:33:37 -0400 Received: from 24.247.253.134.gha.mi.chartermi.net (HELO eleanor.us1.wmi.uvac.net) (24.247.253.134) by mxip17.cluster1.charter.net with ESMTP; 20 Apr 2005 08:33:36 -0400 X-Ironport-AV: i="3.92,116,1112587200"; d="scan'208"; a="1022677452:sNHT13937436" Date: Wed, 20 Apr 2005 08:33:36 -0400 (EDT) From: c0ldbyte To: Devon Sean McCullough In-Reply-To: <200504192127.j3JLR9Oq055796@grant.org> Message-ID: <20050420083114.X46699@eleanor.us1.wmi.uvac.net> References: <200504192127.j3JLR9Oq055796@grant.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: security-advisories@freebsd.org cc: freebsd-hackers@freebsd.org cc: Steven Hartland Subject: Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh 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, 20 Apr 2005 12:33:39 -0000 On Tue, 19 Apr 2005, Devon Sean McCullough wrote: > On Wed, 17 Sep 2003 00:02:33 +0100 Steven Hartland asked this question > but no answer was posted. The trouble is likely no client reverse DNS > either because it is missing or slow. Adding the client to /etc/hosts > on the server seems at first to do nothing but after a minute or so it > stops hanging and asks for a password. Could be a coincidence though. > > To recap: > $ ssh -v me@my-freebsd-5.1-RELEASE-box > OpenSSH_3.4p1+CAN-2004-0175, SSH protocols 1.5/2.0, OpenSSL 0x0090609f > .... > debug1: Remote protocol version 1.99, remote software version OpenSSH_3.6.1p1 FreeBSD-20030423 > debug1: match: OpenSSH_3.6.1p1 FreeBSD-20030423 pat OpenSSH* > Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-OpenSSH_3.4p1+CAN-2004-0175 > .... > debug1: got SSH2_MSG_SERVICE_ACCEPT > <---Here the client hangs until timeout. > > To debug: kill the server process and run # sshd -ddde > .... > debug3: Trying to reverse map address ... > <---Here the server hangs until timeout. Dude, that was 2 years ago in 2003 the year now is 2005 and the current date is 'Wed Apr 20 12:32:31 UTC 2005' so umm, am I living in the future or are you dwelling on the past ???. -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 12:48:53 2005 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 EF10C16A4CF; Wed, 20 Apr 2005 12:48:53 +0000 (GMT) Received: from grant.org (grant.org [206.190.173.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 695F843D49; Wed, 20 Apr 2005 12:48:53 +0000 (GMT) (envelope-from Devon@Jovi.Net) Received: from grant.org (localhost [127.0.0.1]) by grant.org (8.12.11/8.12.11) with ESMTP id j3KCmbVq071133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Apr 2005 08:48:37 -0400 (EDT) (envelope-from Devon@Jovi.Net) Received: (from devon@localhost) by grant.org (8.12.11/8.12.11/Submit) id j3KCmYH3071130; Wed, 20 Apr 2005 08:48:34 -0400 (EDT) (envelope-from Devon@Jovi.Net) Date: Wed, 20 Apr 2005 08:48:34 -0400 (EDT) Message-Id: <200504201248.j3KCmYH3071130@grant.org> X-Authentication-Warning: grant.org: devon set sender to Devon@Jovi.Net using -f From: Devon@Jovi.Net To: c0ldbyte In-reply-to: <20050420083114.X46699@eleanor.us1.wmi.uvac.net> (message from c0ldbyte on Wed, 20 Apr 2005 08:33:36 -0400 (EDT)) References: <200504192127.j3JLR9Oq055796@grant.org> <20050420083114.X46699@eleanor.us1.wmi.uvac.net> X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, NO_REAL_NAME autolearn=ham version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on grant.org X-Virus-Scanned: by amavisd-new X-Mailman-Approved-At: Wed, 20 Apr 2005 12:52:57 +0000 cc: security-advisories@freebsd.org cc: freebsd-hackers@freebsd.org cc: FreeBSD-2005@Jovi.Net cc: killing@BarrysWorld.com Subject: Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh 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, 20 Apr 2005 12:48:54 -0000 Date: Wed, 20 Apr 2005 08:33:36 -0400 (EDT) From: c0ldbyte cc: security-advisories@freebsd.org, freebsd-hackers@freebsd.org, Steven Hartland On Tue, 19 Apr 2005, Devon Sean McCullough wrote: > On Wed, 17 Sep 2003 00:02:33 +0100 Steven Hartland asked this question > but no answer was posted. The trouble is likely no client reverse DNS > either because it is missing or slow. Adding the client to /etc/hosts > on the server seems at first to do nothing but after a minute or so it > stops hanging and asks for a password. Could be a coincidence though. > > To recap: > $ ssh -v me@my-freebsd-5.1-RELEASE-box > OpenSSH_3.4p1+CAN-2004-0175, SSH protocols 1.5/2.0, OpenSSL 0x0090609f > .... > debug1: Remote protocol version 1.99, remote software version OpenSSH_3.6.1p1 FreeBSD-20030423 > debug1: match: OpenSSH_3.6.1p1 FreeBSD-20030423 pat OpenSSH* > Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-OpenSSH_3.4p1+CAN-2004-0175 > .... > debug1: got SSH2_MSG_SERVICE_ACCEPT > <---Here the client hangs until timeout. > > To debug: kill the server process and run # sshd -ddde > .... > debug3: Trying to reverse map address ... > <---Here the server hangs until timeout. Dude, that was 2 years ago in 2003 the year now is 2005 and the current date is 'Wed Apr 20 12:32:31 UTC 2005' so umm, am I living in the future or are you dwelling on the past ???. -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) This trouble hit me yesterday, 2005 Apr 19 Tue, Google led me to someone else with the exact same trouble. What use to ask the net if nobody publishes an ANSWER? A good netizen does the right thing. By citing the original question, I create a link to a possible answer. Peace --Devon /~\ \ / Health Care X not warfare / \ Dubya won the digital vote Kerry won the popular vote PS: Can you identify the presumably slavic language of "blagodarq za izpratenoto ot Vas pismo nai skoro shte vi otgovorq!!" From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 12:59:42 2005 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 D295616A4CE for ; Wed, 20 Apr 2005 12:59:42 +0000 (GMT) Received: from smtpout-2.priv.cc.uic.edu (smtpout-2.cc.uic.edu [128.248.155.233]) by mx1.FreeBSD.org (Postfix) with SMTP id 48EE843D2F for ; Wed, 20 Apr 2005 12:59:42 +0000 (GMT) (envelope-from zholla1@uic.edu) Received: (qmail 4594 invoked from network); 20 Apr 2005 07:59:41 -0500 Received: from icarus.cc.uic.edu (128.248.155.80) by smtpout-2.cc.uic.edu with SMTP; 20 Apr 2005 07:59:41 -0500 Date: Wed, 20 Apr 2005 07:59:41 -0500 (CDT) From: Zera William Holladay X-X-Sender: zholla1@icarus.cc.uic.edu To: neuro@mail.fci.fsu.edu In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: kernel programming 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, 20 Apr 2005 12:59:42 -0000 On Wed, 20 Apr 2005 neuro@mail.fci.fsu.edu wrote: > yeah thanks for that, i figured the code was a good start. Now that I > know the docs i know where to go, cheers for that > > --neuro > > On Wed, 20 Apr 2005, Joseph Koshy wrote: > > >> where's a good place for kernel programming documentation ? > > > > In no particular order: > > > > 1. The FreeBSD Developer's Handbook. > > 2. The FreeBSD Architecture Handbook. > > 3. The book 'The Design and Implementation of the FreeBSD > > Operating System', by Kirk McKusick and George > > Neville-Neil. > > 3. The section 9 manual pages. > > 4. The source code :). I like these too (the above is a good list): man 7 development gives a nice model and tutorial to setup an environment. man 7 build documents some of the /usr/src/ targets for make. Good luck, Zera Holladay From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 13:07:00 2005 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 D13F416A4CE for ; Wed, 20 Apr 2005 13:07:00 +0000 (GMT) Received: from mailserv1.neuroflux.com (ns2.neuroflux.com [204.228.228.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7446A43D2D for ; Wed, 20 Apr 2005 13:07:00 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 94735 invoked by uid 1003); 20 Apr 2005 13:07:08 -0000 Received: from ryans@gamersimpact.com by mailserv1.neuroflux.com by uid 89 with qmail-scanner-1.22 (clamscan: 0.65. spamassassin: 2.60. Clear:RC:1(63.231.170.25):. Processed in 1.265977 secs); 20 Apr 2005 13:07:08 -0000 Received: from unknown (HELO ?192.168.0.5?) (63.231.170.25) by mailserv1.neuroflux.com with SMTP; 20 Apr 2005 13:07:07 -0000 Message-ID: <426653FC.8070801@gamersimpact.com> Date: Wed, 20 Apr 2005 08:07:08 -0500 From: Ryan Sommers User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: c0ldbyte References: <200504192127.j3JLR9Oq055796@grant.org> <20050420083114.X46699@eleanor.us1.wmi.uvac.net> In-Reply-To: <20050420083114.X46699@eleanor.us1.wmi.uvac.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh 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, 20 Apr 2005 13:07:01 -0000 c0ldbyte wrote: > > Dude, that was 2 years ago in 2003 the year now is 2005 > and the current date is 'Wed Apr 20 12:32:31 UTC 2005' > so umm, am I living in the future or are you dwelling on > the past ???. > Hey, dude, you aren't helping situations around here. This is one of many inflammatory remarks you've made in recent months. However, I don't believe you're doing it for the express purpose of trolling, so I'm going to give you the benefit of the doubt and advise you. I don't care for your attitude around here, not that that really means anything, but I'm sure others don't either. This is a public list and people are allowed to ask questions. No matter if you, or I, or anyone else considers them stupid. Asking for aid is what the lists are here for. Certain questions might be better directed to questions@ or current@, however, none deserve the treatment you are giving them. None of us have belittled you when you asked questions, you should extend others the same courtesy. You appear to have interest in FreeBSD and I don't want to turn anyone away from it or put a sour taste in their mouth. I have loved the same OS for a long time and like to watch it grow with new list membership, yours the same, however, hang the 'tude at the door and realize this isn't IRC. We help people here instead of giving them a snide remark and say, "RTFM". Sincerely Ryan. -- Ryan Sommers ryans@gamersimpact.com From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 13:08:25 2005 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 75C2916A4CE; Wed, 20 Apr 2005 13:08:25 +0000 (GMT) Received: from multiplay.co.uk (www1.multiplay.co.uk [212.42.16.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7982843D48; Wed, 20 Apr 2005 13:08:24 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [212.42.16.7]) (MDaemon.PRO.v7.2.3.R) with ESMTP id md50001348459.msg; Wed, 20 Apr 2005 14:04:18 +0100 Message-ID: <011901c545a9$e5ac6fc0$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: , "c0ldbyte" References: <200504192127.j3JLR9Oq055796@grant.org><20050420083114.X46699@eleanor.us1.wmi.uvac.net> <200504201248.j3KCmYH3071130@grant.org> Date: Wed, 20 Apr 2005 14:07:21 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Spam-Processed: multiplay.co.uk, Wed, 20 Apr 2005 14:04:18 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDAV-Processed: multiplay.co.uk, Wed, 20 Apr 2005 14:04:22 +0100 cc: security-advisories@freebsd.org cc: freebsd-hackers@freebsd.org cc: FreeBSD-2005@Jovi.Net cc: killing@BarrysWorld.com Subject: Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh 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, 20 Apr 2005 13:08:25 -0000 Sorry I don't remember the solution we came up with. It was a long time ago. I think it was to do with DNS invalid / broken DNS or something like that but I couldn't say for sure. Regards Steve ----- Original Message ----- From: > > This trouble hit me yesterday, 2005 Apr 19 Tue, Google led me to > someone else with the exact same trouble. What use to ask the net > if nobody publishes an ANSWER? A good netizen does the right thing. > By citing the original question, I create a link to a possible answer. ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 13:13:37 2005 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 9C2D316A4CE for ; Wed, 20 Apr 2005 13:13:37 +0000 (GMT) Received: from mxsf01.cluster1.charter.net (mxsf01.cluster1.charter.net [209.225.28.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id E269A43D41 for ; Wed, 20 Apr 2005 13:13:36 +0000 (GMT) (envelope-from c0ldbyte@myrealbox.com) Received: from mxip07.cluster1.charter.net (mxip07a.cluster1.charter.net [209.225.28.137])j3KDDZsK009863 for ; Wed, 20 Apr 2005 09:13:35 -0400 Received: from 24.247.253.134.gha.mi.chartermi.net (HELO eleanor.us1.wmi.uvac.net) (24.247.253.134) by mxip07.cluster1.charter.net with ESMTP; 20 Apr 2005 09:13:35 -0400 X-Ironport-AV: i="3.92,116,1112587200"; d="scan'208"; a="864567252:sNHT14985292" Date: Wed, 20 Apr 2005 09:13:27 -0400 (EDT) From: c0ldbyte To: neuro@mail.fci.fsu.edu In-Reply-To: Message-ID: <20050420083807.R46699@eleanor.us1.wmi.uvac.net> References: <741675355.1113978425415.JavaMail.nobody@app6.ni.bg> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-hackers@freebsd.org Subject: Re: =?windows-1251?b?QUJWLkJHIODi8u7s4PLo9+XtIO7y4+7i7vA=?= 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, 20 Apr 2005 13:13:37 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 20 Apr 2005 neuro@mail.fci.fsu.edu wrote: > i'm not sure i understnad that language ? > if you tell me which one it is I could use googles convertor > > --neuro > > On Wed, 20 Apr 2005 freebsd-hackers@freebsd.org wrote: > >> blagodarq za izpratenoto ot Vas pismo nai skoro shte vi otgovorq!! >> This guy/gal we will call "The so-called idiot" has subscribed to the mailing list and turned his autoreply for his webmail on. So every time there is a posting to a certain list his email address autogens a response and sends it back out to the original sender of the mail. This is in turn something that mailing list software should protect against otherwise we could have a nice flood of webmail autoreply DoS's. I have added a procmail recipe to my $HOME/.procmailrc to delete these emailings along with other unwanted stuff from idiots like this one allready just to solve the problem until someone comes up with a great idea to add a "repeat mailing filter" (hint) to the mailing lists. Following is a procmailrc example for removing email from hosts that you dont want. # ---- Begin $HOME/.procmailrc ---- SHELL=/bin/sh PATH=/bin:/usr/bin:/usr/local/bin MAILDIR=$HOME/mail DEFAULT=/var/mail/$LOGNAME LOGFILE=$HOME/log/procmail.log # Comment this out for no logs MAIL_ALLOW=$HOME/.procmail/mail.allow # List of allowed host patterns MAIL_DENY=$HOME/.procmail/mail.deny # List of denied host patterns :0: * ? formail -x"From" -x"From:" -x"Sender:" \ -x"Reply-To:" -x"Return-Path:" -x"Received:" \ | egrep -is -f $MAIL_DENY DROPBOX :0: * ? formail -x"From" -x"From:" -x"Sender:" \ -x"Reply-To:" -x"Return-Path:" -x"Received:" \ | egrep -is -f $MAIL_ALLOW ${DEFAULT} # ---- End of $HOME/.procmailrc ---- Now just setup a couple of things. Make sure you have procmail installed. Create the $HOME/.procmailrc with the contents above. mkdir $HOME/log for log files. mkdir $HOME/.procmail for keeping the mail.allow and mail.deny filter files. Make sure to at least touch $HOME/.procmail/mail.allow & $HOME/.procmail/mail.deny. All done and set, you can start adding your host patterns to mail.deny or mail.allow in the form of any of the following. user@host.net, user@host, host.net, .host.net, @host.net, hostname.host.net. I would reccomend adding just single words to the deny file just for the reason of it will match if the word shows up anywhere in the fields that it greps and return true and ultimately dumping your mail to a DROPBOX. You can also change the DROPBOX part to a absolute path like "/dev/null" as well. Now just add the following to your $HOME/.forward file and youll have some easy filters setup for your control. "|IFS=' ' && exec /usr/local/bin/procmail -Yf- || exit 75 #USERNAME" ^^^ including the double quotes ^^^ Best of luck. --c0ldbyte - -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) Comment: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF7DF979F Comment: Fingerprint = D1DC 0AA4 1C4E EAD4 24EB 7E77 B261 50BA F7DF 979F iD8DBQFCZlV6smFQuvffl58RAsThAJ96zhD7mB9b+39MWEGjXtgcMNdBewCcC7rm iFxaMo+CsMM0SbYr1pIP8qE= =ZeOL -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 13:18:51 2005 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 CC63C16A4CE; Wed, 20 Apr 2005 13:18:51 +0000 (GMT) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5B2043D46; Wed, 20 Apr 2005 13:18:50 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j3KDIXtW046223; Wed, 20 Apr 2005 08:18:33 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4266567B.2010508@centtech.com> Date: Wed, 20 Apr 2005 08:17:47 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050325 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steven Hartland References: <200504192127.j3JLR9Oq055796@grant.org><20050420083114.X46699@eleanor.us1.wmi.uvac.net> <200504201248.j3KCmYH3071130@grant.org> <011901c545a9$e5ac6fc0$b3db87d4@multiplay.co.uk> In-Reply-To: <011901c545a9$e5ac6fc0$b3db87d4@multiplay.co.uk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: security-advisories@freebsd.org cc: FreeBSD-2005@Jovi.Net cc: Devon@Jovi.Net cc: c0ldbyte cc: killing@BarrysWorld.com cc: freebsd-hackers@freebsd.org Subject: Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh 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, 20 Apr 2005 13:18:52 -0000 Steven Hartland wrote: > Sorry I don't remember the solution we came up with. It was a long time > ago. I think it was to do with DNS invalid / broken DNS or something > like that but I couldn't say for sure. > > Regards > Steve > ----- Original Message ----- From: > >> >> This trouble hit me yesterday, 2005 Apr 19 Tue, Google led me to >> someone else with the exact same trouble. What use to ask the net >> if nobody publishes an ANSWER? A good netizen does the right thing. >> By citing the original question, I create a link to a possible answer. I seem to remember updating the /etc/named/named.root file on a box, and that fixed it for me.. I can't recall for sure, but you might give that a shot. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 13:22:18 2005 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 0FC0C16A4CE for ; Wed, 20 Apr 2005 13:22:18 +0000 (GMT) Received: from titan.whee.org (titan.whee.org [207.195.206.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FAAA43D46 for ; Wed, 20 Apr 2005 13:22:17 +0000 (GMT) (envelope-from adam@whee.org) Received: from titan.whee.org (localhost [127.0.0.1]) by titan.whee.org (8.12.9/8.12.9) with ESMTP id j3KD8BjX012905 for ; Wed, 20 Apr 2005 08:08:11 -0500 (CDT) Received: from localhost (adam@localhost) by titan.whee.org (8.12.9/8.12.9/Submit) with ESMTP id j3KD8Bfc012902 for ; Wed, 20 Apr 2005 08:08:11 -0500 (CDT) X-Authentication-Warning: titan.whee.org: adam owned process doing -bs Date: Wed, 20 Apr 2005 08:08:11 -0500 (CDT) From: Adam Maloney X-X-Sender: adam@titan To: freebsd-hackers@freebsd.org In-Reply-To: <20050420083807.R46699@eleanor.us1.wmi.uvac.net> Message-ID: References: <741675355.1113978425415.JavaMail.nobody@app6.ni.bg> <20050420083807.R46699@eleanor.us1.wmi.uvac.net> X-GPG-FINGERPRINT: E39B 8D34 5F0A EA2E 4CCA 5B1D 8D55 7C25 0061 10AF X-GPG-PUBLIC_KEY: http://www.whee.org/~adam/adam-whee-org-pubkey.asc MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: =?windows-1251?b?QUJWLkJHIODi8u7s4PLo9+XtIO7y4+7i7vA=?= 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, 20 Apr 2005 13:22:18 -0000 >> On Wed, 20 Apr 2005 freebsd-hackers@freebsd.org wrote: >> >>> blagodarq za izpratenoto ot Vas pismo nai skoro shte vi otgovorq!! >>> Sir, this is not the appropriate forum to cast your vote for Pope. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 13:35:16 2005 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 258D516A4CE for ; Wed, 20 Apr 2005 13:35:16 +0000 (GMT) Received: from mxsf40.cluster1.charter.net (mxsf40.cluster1.charter.net [209.225.28.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6573E43D39 for ; Wed, 20 Apr 2005 13:35:15 +0000 (GMT) (envelope-from c0ldbyte@myrealbox.com) Received: from mxip09.cluster1.charter.net (mxip09a.cluster1.charter.net [209.225.28.139])j3KDZDa8017202 for ; Wed, 20 Apr 2005 09:35:13 -0400 Received: from 24.247.253.134.gha.mi.chartermi.net (HELO eleanor.us1.wmi.uvac.net) (24.247.253.134) by mxip09.cluster1.charter.net with ESMTP; 20 Apr 2005 09:35:13 -0400 X-Ironport-AV: i="3.92,116,1112587200"; d="scan'208"; a="856418295:sNHT13738460" Date: Wed, 20 Apr 2005 09:35:09 -0400 (EDT) From: c0ldbyte To: Ryan Sommers In-Reply-To: <426653FC.8070801@gamersimpact.com> Message-ID: <20050420092230.G46699@eleanor.us1.wmi.uvac.net> References: <200504192127.j3JLR9Oq055796@grant.org> <426653FC.8070801@gamersimpact.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-hackers@freebsd.org Subject: Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh 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, 20 Apr 2005 13:35:16 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 20 Apr 2005, Ryan Sommers wrote: > c0ldbyte wrote: >> >> Dude, that was 2 years ago in 2003 the year now is 2005 >> and the current date is 'Wed Apr 20 12:32:31 UTC 2005' >> so umm, am I living in the future or are you dwelling on >> the past ???. >> > > Hey, dude, you aren't helping situations around here. This is one of many > inflammatory remarks you've made in recent months. However, I don't believe > you're doing it for the express purpose of trolling, so I'm going to give you > the benefit of the doubt and advise you. > > I don't care for your attitude around here, not that that really means > anything, but I'm sure others don't either. This is a public list and people > are allowed to ask questions. No matter if you, or I, or anyone else > considers them stupid. Asking for aid is what the lists are here for. Certain > questions might be better directed to questions@ or current@, however, none > deserve the treatment you are giving them. None of us have belittled you when > you asked questions, you should extend others the same courtesy. > > You appear to have interest in FreeBSD and I don't want to turn anyone away > from it or put a sour taste in their mouth. I have loved the same OS for a > long time and like to watch it grow with new list membership, yours the same, > however, hang the 'tude at the door and realize this isn't IRC. We help > people here instead of giving them a snide remark and say, "RTFM". > > Sincerely > Ryan. Well first off that wasnt a snide remark. Second off it was sort of a off lead question of why this was brought up now since it happened 2 or more years ago, but sorry you didnt catch that and that I didnt make that more clear. Third off I dont tell people to RTFM unless I allready know that its defined in the manual and they are asking basic questions that should have allready easyily been picked up from the manual which tells other that they have not read the manual correctly correct ?. Anyhow that email that I sent that Im replying to now was not meant to be taken in any harsh way. That email in question was more of a fundamental way to extract certain information on why things are the way they are now and get more insight in a less direct way. But I appologize to any of you that may have felt hurt or upset at the way that email was written and I tend to do alot of that sometimes due to hell I dont know just do I guess but anywho best of luck to all of ya. PS: Dont mean to offend anyone. If I have drop my name in your ignore list. Email dont have to be read just because its there. Best wishes. --c0ldbyte - -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) Comment: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF7DF979F Comment: Fingerprint = D1DC 0AA4 1C4E EAD4 24EB 7E77 B261 50BA F7DF 979F iD8DBQFCZlqRsmFQuvffl58RAkfUAJkBfSQe3i3/6fhP7eAK6P6mOe0ligCfVJc6 wyBxXHD3l0diy6iAO8BT+w4= =5r0w -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 13:50:57 2005 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 1B13C16A4CE for ; Wed, 20 Apr 2005 13:50:57 +0000 (GMT) Received: from postfix4-1.free.fr (postfix4-1.free.fr [213.228.0.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62D7C43D45 for ; Wed, 20 Apr 2005 13:50:56 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix4-1.free.fr (Postfix) with ESMTP id 003BF3177E3; Wed, 20 Apr 2005 15:50:54 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 56820405A; Wed, 20 Apr 2005 15:50:13 +0200 (CEST) Date: Wed, 20 Apr 2005 15:50:13 +0200 From: Jeremie Le Hen To: ?? ?? Message-ID: <20050420135013.GE91329@obiwan.tataz.chchile.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i cc: freebsd-hackers@freebsd.org Subject: Re: Configuration differences for jails 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, 20 Apr 2005 13:50:57 -0000 Hi, > I am now trying to use jail in FreeBSD. I have read the jail(8) man page > and some > others documents for setting up jails. But I'm a little confused about the > procedure and configurations for setting up jails. > As known to all, jail can be used for two purposes, i.e. jailing a single > application or acting as a virtual host. What i want to know is the > concrete configuration (procedure) difference between the two types use of > jails. Is there a SMALLEST set > of configuration necessary for setting up a jail? If so, what is it? > Another question, > is there any way to detect the share of files between multiple jails > automatically? The following is based on my own experience and therefore may not be what other people feel. I run two main services on a box, Bind and Postfix, and I wanted to separate each other from the base system for security reason. I thought it was quite heavy to boot two virtual hosts as described in the jail(8) manpage for two daemons only, so I decided to just jail each application. In all cases, I strongly wanted the chosen setup to create a very few overhead compared to what it would be without jail. In the per-application case, you will have to be very careful about the things that will be needed by the daemon (dynamic libraries and configuration files as well as spool queues, mailboxes or maildirs, and other filesystem objects such as Unix domain sockets, named pipes, ...) Since I wanted this setup to be as transparent as possible, I decided to null mounts all needed directories from host to jail root, in order to be able to execute administrative commands (postconf(8), mailq(8), ...) from host itself. One exception is /etc : you don't want to null mount it into the jail as it contains very sensible informations like password hashes ; you will have to manually synchronize resolv.conf, localtime, aliases, ... Now with some distance, I must admit that all this gymnastic is quite boring. I now decided to run two virtual hosts as they are managed in a very natural way. These two hosts are just like two real boxes, one running Bind and the other one running Postfix. When I need to update something in the configuration, I login to the box with ssh(1). This take some more memory and in principle no CPU as all processes are sleeping most of the time. > BTW, what is the meaning of "IMHO"? :) > It appears very frequently in the mail list. The port games/wtf will translate acronyms for you. %%% obiwan:ports$ wtf IMHO IMHO: in my humble opinion %%% Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 14:04:11 2005 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 62FC816A4CE; Wed, 20 Apr 2005 14:04:11 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1140C43D60; Wed, 20 Apr 2005 14:04:10 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id D0AD61F1C0; Wed, 20 Apr 2005 16:04:09 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id B2543641C; Wed, 20 Apr 2005 16:04:09 +0200 (CEST) Date: Wed, 20 Apr 2005 16:04:09 +0200 From: Marc Olzheim To: Brian Fundakowski Feldman Message-ID: <20050420140409.GA77731@stack.nl> References: <20050418092550.GA97539@stack.nl> <20050418092752.GB97539@stack.nl> <20050418202213.GC1157@green.homeunix.org> <20050418203321.GA88774@stack.nl> <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UlVJffcvxoiEqYs2" Content-Disposition: inline In-Reply-To: <20050419204723.GG1157@green.homeunix.org> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i cc: Marc Olzheim cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 20 Apr 2005 14:04:11 -0000 --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Apr 19, 2005 at 04:47:23PM -0400, Brian Fundakowski Feldman wrote: > This compiles. It does and it seems to work. The NFS performance drops considerably though, from 8/9 MByte/s to 3/4 on sequential reads for instance. kern/79208 is fixed by this indeed, in that I get short writes (in case of my test server at 1802240+ bytes, so './writev 2 foo' fails... Marc --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZmFZezjnobFOgrERArNtAKC4NvqjLns4i6/ze5g2mtoefl0byQCfZ9Ih a6KDrtrCOjFgVqA/1g5SFC8= =m8tu -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2-- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 14:16:41 2005 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 09E0516A4CE; Wed, 20 Apr 2005 14:16:41 +0000 (GMT) Received: from multiplay.co.uk (www1.multiplay.co.uk [212.42.16.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37EB943D60; Wed, 20 Apr 2005 14:16:40 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [212.42.16.7]) (MDaemon.PRO.v7.2.3.R) with ESMTP id md50001348648.msg; Wed, 20 Apr 2005 15:12:59 +0100 Message-ID: <013c01c545b3$7f193c70$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: References: <200504192127.j3JLR9Oq055796@grant.org><20050420083114.X46699@eleanor.us1.wmi.uvac.net> <200504201248.j3KCmYH3071130@grant.org> <011901c545a9$e5ac6fc0$b3db87d4@multiplay.co.uk> <200504201335.j3KDZMZ4086059@grant.org> Date: Wed, 20 Apr 2005 15:16:04 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Spam-Processed: multiplay.co.uk, Wed, 20 Apr 2005 15:12:59 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDAV-Processed: multiplay.co.uk, Wed, 20 Apr 2005 15:13:02 +0100 cc: security-advisories@freebsd.org cc: c0ldbyte@myrealbox.com cc: FreeBSD-2005@Jovi.Net cc: killing@BarrysWorld.com cc: freebsd-hackers@freebsd.org Subject: Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh 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, 20 Apr 2005 14:16:41 -0000 Usually do post answers when I find them but it was one of those must get it fixed 24 hour jobs as I recall so just slipped way as I fell asleep :) Could be its forcing a name resolution and not using hosts at all? Steve ----- Original Message ----- From: > In the future, please do as I did and publish whatever solution you find, > my answer was somewhat lame but worked for me and will help the next guy. > To the SSH server /etc/hosts I added the client machine, now when it gets > to debug1: got SSH2_MSG_SERVICE_ACCEPT it hangs for only 75 seconds. ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 14:26:35 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8838516A4CE; Wed, 20 Apr 2005 14:26:35 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.3/8.13.1) with ESMTP id j3KEOnN9071973; Wed, 20 Apr 2005 10:24:49 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.3/8.13.1/Submit) id j3KEOmwc071972; Wed, 20 Apr 2005 10:24:48 -0400 (EDT) (envelope-from green) Date: Wed, 20 Apr 2005 10:24:48 -0400 From: Brian Fundakowski Feldman To: Marc Olzheim Message-ID: <20050420142448.GH1157@green.homeunix.org> References: <20050418092752.GB97539@stack.nl> <20050418202213.GC1157@green.homeunix.org> <20050418203321.GA88774@stack.nl> <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050420140409.GA77731@stack.nl> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 20 Apr 2005 14:26:35 -0000 On Wed, Apr 20, 2005 at 04:04:09PM +0200, Marc Olzheim wrote: > On Tue, Apr 19, 2005 at 04:47:23PM -0400, Brian Fundakowski Feldman wrote: > > This compiles. > > It does and it seems to work. The NFS performance drops considerably > though, from 8/9 MByte/s to 3/4 on sequential reads for instance. > > kern/79208 is fixed by this indeed, in that I get short writes (in case > of my test server at 1802240+ bytes, so './writev 2 foo' fails... Performance drops in what cases? -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 14:37:58 2005 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 3076116A500 for ; Wed, 20 Apr 2005 14:37:58 +0000 (GMT) Received: from postfix4-1.free.fr (postfix4-1.free.fr [213.228.0.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC32243D46 for ; Wed, 20 Apr 2005 14:37:57 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix4-1.free.fr (Postfix) with ESMTP id AB4C9317859; Wed, 20 Apr 2005 16:37:56 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 6A312405A; Wed, 20 Apr 2005 16:37:15 +0200 (CEST) Date: Wed, 20 Apr 2005 16:37:15 +0200 From: Jeremie Le Hen To: ?? ?? Message-ID: <20050420143715.GF91329@obiwan.tataz.chchile.org> References: <20050420135013.GE91329@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050420135013.GE91329@obiwan.tataz.chchile.org> User-Agent: Mutt/1.5.9i cc: freebsd-hackers@freebsd.org Subject: Re: Configuration differences for jails 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, 20 Apr 2005 14:37:58 -0000 > Now with some distance, I must admit that all this gymnastic is quite > boring. I now decided to run two virtual hosts as they are managed in > a very natural way. These two hosts are just like two real boxes, one > running Bind and the other one running Postfix. When I need to update > something in the configuration, I login to the box with ssh(1). This > take some more memory and in principle no CPU as all processes are > sleeping most of the time. I forgotten to explain that using virtual hosts require some administration too in order to avoid wasting disk space. The jail(8) manual page advices to make world with DESTDIR set. I prefer using null mounts as it doesn't require additional disk space and an upgrade of the host will automagically upgrade virtual hosts. You will nevertheless have to make distribution and distrib-dirs. Here are the directories I advice you to share : /bin /sbin /lib /libexec /usr/bin /usr/sbin /usr/lib /usr/libexec /usr/libdata /usr/share /usr/doc /usr/compat /usr/ports Sharing ports may be more difficult as it may require sharing the port database, but I think it's still possible. -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 14:38:44 2005 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 C4D4F16A4CE; Wed, 20 Apr 2005 14:38:44 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id F32ED43D4C; Wed, 20 Apr 2005 14:38:43 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 1090D1F19A; Wed, 20 Apr 2005 16:38:43 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id D94BB6583; Wed, 20 Apr 2005 16:38:42 +0200 (CEST) Date: Wed, 20 Apr 2005 16:38:42 +0200 From: Marc Olzheim To: Brian Fundakowski Feldman Message-ID: <20050420143842.GB77731@stack.nl> References: <20050418202213.GC1157@green.homeunix.org> <20050418203321.GA88774@stack.nl> <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KFztAG8eRSV9hGtP" Content-Disposition: inline In-Reply-To: <20050420142448.GH1157@green.homeunix.org> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i cc: Marc Olzheim cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 20 Apr 2005 14:38:44 -0000 --KFztAG8eRSV9hGtP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 20, 2005 at 10:24:48AM -0400, Brian Fundakowski Feldman wrote: > > It does and it seems to work. The NFS performance drops considerably > > though, from 8/9 MByte/s to 3/4 on sequential reads for instance. > >=20 > > kern/79208 is fixed by this indeed, in that I get short writes (in case > > of my test server at 1802240+ bytes, so './writev 2 foo' fails... >=20 > Performance drops in what cases? Hmm, seems only to happen in large sequential reads... It might just be the FreeBSD 4.6 NFS server that is the problem though. I've had more NFS troubles with it. Btw.: I'm not sure write(),writev() and pwrite() are allowed to do short writes on regular files... ? Marc --KFztAG8eRSV9hGtP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZmlyezjnobFOgrERAshmAJ45uor6Jz6tuOrKt20hozLTMDnPbACePn+5 ZE3M6Au5bLATSF+rP5JuuIY= =ufVf -----END PGP SIGNATURE----- --KFztAG8eRSV9hGtP-- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 15:06:48 2005 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 3996B16A4CE for ; Wed, 20 Apr 2005 15:06:48 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id B16B743D3F for ; Wed, 20 Apr 2005 15:06:47 +0000 (GMT) (envelope-from rexroof@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so159424wri for ; Wed, 20 Apr 2005 08:06:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=e2NASuKzlk5Exdx4RIVzjrWaiOu4iJlXgdinRuAmzY9NpF/0f/+PIfq0RNJAKJmfCpOTFdvEqlqkMPXg1YXnQ5bW8WUl0mbryCjfF7WsbpQcBru6w0ryPkxXmuEFfBSQ1Fyte7x8XmyUVQ6Y15CwMLaC6I1looSmvi3LO9vzVkU= Received: by 10.54.3.66 with SMTP id 66mr419359wrc; Wed, 20 Apr 2005 08:06:44 -0700 (PDT) Received: by 10.54.62.14 with HTTP; Wed, 20 Apr 2005 08:06:43 -0700 (PDT) Message-ID: <6afb69aa05042008065db9d0cb@mail.gmail.com> Date: Wed, 20 Apr 2005 11:06:43 -0400 From: Rex Roof To: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: gvinum during bootup X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Rex Roof List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2005 15:06:48 -0000 I'm running a FreeBSD6 machine current as of a few days ago and I'm working on a gvinum configuration, I couldn't find any place where it referenced gvinum on startup so after fussing around with the rc system a little, I wrote an /etc/rc.d/gvinum script that looks like so: #!/bin/sh # PROVIDE: disks # KEYWORD: nojail . /etc/rc.subr name=3D"gvinum" start_cmd=3D"gvinum_start" stop_cmd=3D":" gvinum_start() { case ${gvinum_enable} in [Yy][Ee][Ss]) echo "starting gvinum." /sbin/gvinum start ;; esac } load_rc_config $name run_rc_command "$1" # END I then added=20 gvinum_enable=3D"YES" =20 to my /etc/rc.conf and it seems to be working great. rcorder tells me this is run a few steps before ccd, which is confusing because I used the same keywords and ccd isn't requested anywhere. is there some place this can be added to -current? I'm assuming the change from vinum to gvinum is still in some sort of transition. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 15:09:54 2005 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 6B6DC16A4CF for ; Wed, 20 Apr 2005 15:09:54 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4F2F43D31 for ; Wed, 20 Apr 2005 15:09:53 +0000 (GMT) (envelope-from rexroof@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so160453wri for ; Wed, 20 Apr 2005 08:09:53 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=V4F2/bx7CiJfXn6FgV/DL/q3TeHLkR1OPijq+uclZU5qq65d4S6+1hMP4eyVKKhprbMmms9yWV9gqrH5tqOjDAcN2MHx+V+yZ+r49vBRgrgbqh1i3n5EUvZAeKLAeni6cRalUP2PJxxBsXnFa+PjTiMmHPpTemMHPtUaBecn8GA= Received: by 10.54.3.66 with SMTP id 66mr422500wrc; Wed, 20 Apr 2005 08:09:50 -0700 (PDT) Received: by 10.54.62.14 with HTTP; Wed, 20 Apr 2005 08:09:50 -0700 (PDT) Message-ID: <6afb69aa05042008093d6d59d0@mail.gmail.com> Date: Wed, 20 Apr 2005 11:09:50 -0400 From: Rex Roof To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org In-Reply-To: <6afb69aa05042008065db9d0cb@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <6afb69aa05042008065db9d0cb@mail.gmail.com> Subject: gvinum during bootup X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Rex Roof List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2005 15:09:54 -0000 I'm running a FreeBSD6 machine current as of a few days ago and I'm working on a gvinum configuration, I couldn't find any place where it referenced gvinum on startup so after fussing around with the rc system a little, I wrote an /etc/rc.d/gvinum script that looks like so: #!/bin/sh # PROVIDE: disks # KEYWORD: nojail . /etc/rc.subr name=3D"gvinum" start_cmd=3D"gvinum_start" stop_cmd=3D":" gvinum_start() { case ${gvinum_enable} in [Yy][Ee][Ss]) echo "starting gvinum." /sbin/gvinum start ;; esac } load_rc_config $name run_rc_command "$1" # END I then added gvinum_enable=3D"YES" to my /etc/rc.conf and it seems to be working great. rcorder tells me this is run a few steps before ccd, which is confusing because I used the same keywords and ccd isn't requested anywhere. is there some place this can be added to -current? I'm assuming the change from vinum to gvinum is still in some sort of transition. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 15:12:11 2005 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 6667116A4CE for ; Wed, 20 Apr 2005 15:12:11 +0000 (GMT) Received: from grummit.biaix.org (86.Red-213-97-212.pooles.rima-tde.net [213.97.212.86]) by mx1.FreeBSD.org (Postfix) with SMTP id AC4C043D3F for ; Wed, 20 Apr 2005 15:12:09 +0000 (GMT) (envelope-from lists-freebsd-hackers@biaix.org) Received: (qmail 15719 invoked by uid 1000); 20 Apr 2005 15:11:04 -0000 Date: Wed, 20 Apr 2005 17:11:04 +0200 From: Joan Picanyol i Puig To: freebsd-hackers@freebsd.org Message-ID: <20050420151104.GA11753@grummit.biaix.org> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20050420135013.GE91329@obiwan.tataz.chchile.org> <20050420143715.GF91329@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050420143715.GF91329@obiwan.tataz.chchile.org> User-Agent: Mutt/1.5.6i Subject: Re: Configuration differences for jails 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, 20 Apr 2005 15:12:11 -0000 * Jeremie Le Hen [20050420 16:37]: > > Now with some distance, I must admit that all this gymnastic is quite > > boring. I now decided to run two virtual hosts as they are managed in > > a very natural way. These two hosts are just like two real boxes, one > > running Bind and the other one running Postfix. When I need to update > > something in the configuration, I login to the box with ssh(1). This > > take some more memory and in principle no CPU as all processes are > > sleeping most of the time. > > I forgotten to explain that using virtual hosts require some > administration too in order to avoid wasting disk space. The jail(8) > manual page advices to make world with DESTDIR set. I prefer using > null mounts as it doesn't require additional disk space and an upgrade > of the host will automagically upgrade virtual hosts. You will > nevertheless have to make distribution and distrib-dirs. Here are the > directories I advice you to share : > /bin /sbin /lib /libexec > /usr/bin /usr/sbin /usr/lib /usr/libexec /usr/libdata /usr/share > /usr/doc /usr/compat /usr/ports I'm trying to untangle myself on this issue. I have different filesystems for /, /usr, and /usr/local, mounted in unusual places: 504,p0,1$ ls -l /usr{,/X11R6,/local} lrwxr-xr-x 1 root wheel 18 7 nov 2003 /usr -> fs/base/mount/usr/ lrwxr-xr-x 1 root wheel 25 8 nov 2003 /usr/X11R6 -> ../../../apps/mount/X11R6 lrwxr-xr-x 1 root wheel 25 18 abr 20:40 /usr/local -> ../../../apps/mount/local I know I want to share /usr, but not /usr/local, and only parts of /. So I mount_unionfs /fs/base inside the jail: :/fs/base/mount on /fs/jaildata/mount/fs/base/mount (unionfs, local, read-only, noclusterw) But this way I don't get the "automagically upgrade virtual hosts" behaviour I want, since I'm missing /{,s}bin, /lib and /libexec and I definitely don't want to share /etc. I don't think it's easy to take /etc/ outside the root fs, but I don't see how to share /bin or /lib without leaking info. How do you handle this? What are those distribution targets and how can I use them? tks -- pica From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 15:22:27 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 27EE916A4CE; Wed, 20 Apr 2005 15:22:27 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.3/8.13.1) with ESMTP id j3KFKdre072379; Wed, 20 Apr 2005 11:20:39 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.3/8.13.1/Submit) id j3KFKcc0072378; Wed, 20 Apr 2005 11:20:38 -0400 (EDT) (envelope-from green) Date: Wed, 20 Apr 2005 11:20:38 -0400 From: Brian Fundakowski Feldman To: Marc Olzheim Message-ID: <20050420152038.GI1157@green.homeunix.org> References: <20050418203321.GA88774@stack.nl> <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050420143842.GB77731@stack.nl> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 20 Apr 2005 15:22:27 -0000 On Wed, Apr 20, 2005 at 04:38:42PM +0200, Marc Olzheim wrote: > On Wed, Apr 20, 2005 at 10:24:48AM -0400, Brian Fundakowski Feldman wrote: > > > It does and it seems to work. The NFS performance drops considerably > > > though, from 8/9 MByte/s to 3/4 on sequential reads for instance. > > > > > > kern/79208 is fixed by this indeed, in that I get short writes (in case > > > of my test server at 1802240+ bytes, so './writev 2 foo' fails... > > > > Performance drops in what cases? > > Hmm, seems only to happen in large sequential reads... It might just be > the FreeBSD 4.6 NFS server that is the problem though. I've had more NFS > troubles with it. Reads should be totally unaffected... > Btw.: I'm not sure write(),writev() and pwrite() are allowed to do short > writes on regular files... ? Our manpage is incorrect; POSIX states that they are (see earlier e-mail). There really is no alternative -- we simply can't build an NFS transaction larger than our buffer cache can accomodate. Note that short wries won't happen for normal buffer sizes, only excessively large ones. I really don't believe that writev() is meant to be used so that you can write gigantic data structures in a single transaction... -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 15:35:30 2005 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 4B83716A4CE; Wed, 20 Apr 2005 15:35:30 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3A6F43D45; Wed, 20 Apr 2005 15:35:29 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id E90991F1C7; Wed, 20 Apr 2005 17:35:28 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id CD0DD6583; Wed, 20 Apr 2005 17:35:28 +0200 (CEST) Date: Wed, 20 Apr 2005 17:35:28 +0200 From: Marc Olzheim To: Brian Fundakowski Feldman Message-ID: <20050420153528.GC77731@stack.nl> References: <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> <20050420152038.GI1157@green.homeunix.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="iFRdW5/EC4oqxDHL" Content-Disposition: inline In-Reply-To: <20050420152038.GI1157@green.homeunix.org> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i cc: Marc Olzheim cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 20 Apr 2005 15:35:30 -0000 --iFRdW5/EC4oqxDHL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 20, 2005 at 11:20:38AM -0400, Brian Fundakowski Feldman wrote: > Reads should be totally unaffected... The server was misbehaving. Fixed. :-) > > Btw.: I'm not sure write(),writev() and pwrite() are allowed to do short > > writes on regular files... ? >=20 > Our manpage is incorrect; POSIX states that they are (see earlier > e-mail). There really is no alternative -- we simply can't build > an NFS transaction larger than our buffer cache can accomodate. > Note that short wries won't happen for normal buffer sizes, only > excessively large ones. I really don't believe that writev() is meant > to be used so that you can write gigantic data structures in a single > transaction... Ah, I was reading the SUSv2 page: http://www.opengroup.org/onlinepubs/009695399/functions/write.html instead of the POSIX version. But in neither of those I can extrude the fact that it can return with result < nbyte, without it being a permanent condition. What phrase makes you conclude that it can ? Marc --iFRdW5/EC4oqxDHL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZnbAezjnobFOgrERAqYEAJ9a25uCceVtDReKpiAUkMsNi0h5fACeJvTc dpl7Dp6Sa4k3Bth3VKt/hR0= =qmxF -----END PGP SIGNATURE----- --iFRdW5/EC4oqxDHL-- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 15:54:22 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A495316A4CE; Wed, 20 Apr 2005 15:54:22 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.3/8.13.1) with ESMTP id j3KFqXoh072666; Wed, 20 Apr 2005 11:52:33 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.3/8.13.1/Submit) id j3KFqXqZ072665; Wed, 20 Apr 2005 11:52:33 -0400 (EDT) (envelope-from green) Date: Wed, 20 Apr 2005 11:52:33 -0400 From: Brian Fundakowski Feldman To: Marc Olzheim Message-ID: <20050420155233.GJ1157@green.homeunix.org> References: <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> <20050420152038.GI1157@green.homeunix.org> <20050420153528.GC77731@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050420153528.GC77731@stack.nl> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 20 Apr 2005 15:54:23 -0000 On Wed, Apr 20, 2005 at 05:35:28PM +0200, Marc Olzheim wrote: > On Wed, Apr 20, 2005 at 11:20:38AM -0400, Brian Fundakowski Feldman wrote: > > Reads should be totally unaffected... > > The server was misbehaving. Fixed. :-) > > > > Btw.: I'm not sure write(),writev() and pwrite() are allowed to do short > > > writes on regular files... ? > > > > Our manpage is incorrect; POSIX states that they are (see earlier > > e-mail). There really is no alternative -- we simply can't build > > an NFS transaction larger than our buffer cache can accomodate. > > Note that short wries won't happen for normal buffer sizes, only > > excessively large ones. I really don't believe that writev() is meant > > to be used so that you can write gigantic data structures in a single > > transaction... > > Ah, I was reading the SUSv2 page: > > http://www.opengroup.org/onlinepubs/009695399/functions/write.html > > instead of the POSIX version. > > But in neither of those I can extrude the fact that it can return > with result < nbyte, without it being a permanent condition. > What phrase makes you conclude that it can ? This specific issue is not clear-cut; the best thing to do lies somewhere within the range of these scenarios: "If a write() requests that more bytes be written than there is room for (for example, [XSI] [Option Start] the process' file size limit or [Option End] the physical end of a medium), only as many bytes as there is room for shall be written. For example, suppose there is space for 20 bytes more in a file before reaching a limit. A write of 512 bytes will return 20. The next write of a non-zero number of bytes would give a failure return (except as noted below)." "When attempting to write to a file descriptor (other than a pipe or FIFO) that supports non-blocking writes and cannot accept the data immediately: * If the O_NONBLOCK flag is clear, write() shall block the calling thread until the data can be accepted. * If the O_NONBLOCK flag is set, write() shall not block the thread. If some data can be written without blocking the thread, write() shall write what it can and return the number of bytes written. Otherwise, it shall return -1 and set errno to [EAGAIN]." "[ENOBUFS] Insufficient resources were available in the system to perform the operation." I think the first is more useful behavior than the last. Supporting it should be exactly the same as supporting what happens if the actual filesystem fills up. In this case, the filesystem is being requested to write more "than there is room for." -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 16:56:42 2005 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 9DC0416A4CE for ; Wed, 20 Apr 2005 16:56:42 +0000 (GMT) Received: from postfix3-1.free.fr (postfix3-1.free.fr [213.228.0.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id EADDD43D41 for ; Wed, 20 Apr 2005 16:56:41 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix3-1.free.fr (Postfix) with ESMTP id 1937B173549 for ; Wed, 20 Apr 2005 18:56:40 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 7EC57405A; Wed, 20 Apr 2005 18:56:00 +0200 (CEST) Date: Wed, 20 Apr 2005 18:56:00 +0200 From: Jeremie Le Hen To: freebsd-hackers@freebsd.org Message-ID: <20050420165559.GI91329@obiwan.tataz.chchile.org> References: <20050420135013.GE91329@obiwan.tataz.chchile.org> <20050420143715.GF91329@obiwan.tataz.chchile.org> <20050420151104.GA11753@grummit.biaix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050420151104.GA11753@grummit.biaix.org> User-Agent: Mutt/1.5.9i Subject: Re: Configuration differences for jails 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, 20 Apr 2005 16:56:42 -0000 > I'm trying to untangle myself on this issue. I have different > filesystems for /, /usr, and /usr/local, mounted in unusual places: > > 504,p0,1$ ls -l /usr{,/X11R6,/local} > lrwxr-xr-x 1 root wheel 18 7 nov 2003 /usr -> fs/base/mount/usr/ > lrwxr-xr-x 1 root wheel 25 8 nov 2003 /usr/X11R6 -> > ../../../apps/mount/X11R6 > lrwxr-xr-x 1 root wheel 25 18 abr 20:40 /usr/local -> > ../../../apps/mount/local > > I know I want to share /usr, but not /usr/local, and only parts of /. So > I mount_unionfs /fs/base inside the jail: > > :/fs/base/mount on /fs/jaildata/mount/fs/base/mount (unionfs, > local, read-only, noclusterw) > mount_nullfs(8) will mount one directory and all its content onto another one, but there is no way to exclude one of the subdirectory. You will instead have to mount each subdirectory you need, not more. One other way do achieve this is to make a second null mount over the directory you don't wan't to share (/usr/local) but I'm not aware of the consequences of such setup in term of performance and stability. > But this way I don't get the "automagically upgrade virtual hosts" > behaviour I want, since I'm missing /{,s}bin, /lib and /libexec and I > definitely don't want to share /etc. You won't have a one to one mapping between jail and null mounts. There are generally multiple null mounts for a unique jail. Considering your jail root is /jail/test, and you enabled the jail_$jail_mount (jail_test_mount here) rc.conf(5) variable, here is the content of /etc/fstab.test : %%% /bin /jail/test/bin nullfs ro 0 0 /sbin /jail/test/sbin nullfs ro 0 0 /lib /jail/test/lib nullfs ro 0 0 /libexec /jail/test/libexec nullfs ro 0 0 /usr/bin /jail/test/usr/bin nullfs ro 0 0 /usr/sbin /jail/test/usr/sbin nullfs ro 0 0 /usr/lib /jail/test/usr/lib nullfs ro 0 0 /usr/libexec /jail/test/usr/libexec nullfs ro 0 0 /usr/libdata /jail/test/usr/libdata nullfs ro 0 0 /usr/share /jail/test/usr/share nullfs ro 0 0 /usr/compat /jail/test/usr/compat nullfs ro 0 0 %%% > I don't think it's easy to take /etc/ outside the root fs, but I don't > see how to share /bin or /lib without leaking info. > > How do you handle this? What are those distribution targets and how can > I use them? As I said above, null mount each directory. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 17:12:23 2005 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 DC5E616A4CE; Wed, 20 Apr 2005 17:12:22 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCB3D43D1D; Wed, 20 Apr 2005 17:12:21 +0000 (GMT) (envelope-from jilles@stack.nl) Received: from turtle.stack.nl (turtle.stack.nl [IPv6:2001:610:1108:5010::132]) by mailhost.stack.nl (Postfix) with ESMTP id B84A61F1CD; Wed, 20 Apr 2005 19:12:20 +0200 (CEST) Received: by turtle.stack.nl (Postfix, from userid 1677) id AA0B71CEAA; Wed, 20 Apr 2005 19:12:20 +0200 (CEST) Date: Wed, 20 Apr 2005 19:12:20 +0200 From: Jilles Tjoelker To: Brian Fundakowski Feldman Message-ID: <20050420171220.GB93623@stack.nl> References: <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> <20050420152038.GI1157@green.homeunix.org> <20050420153528.GC77731@stack.nl> <20050420155233.GJ1157@green.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050420155233.GJ1157@green.homeunix.org> X-Operating-System: FreeBSD 5.3-RELEASE-p9 i386 User-Agent: Mutt/1.5.6i cc: Marc Olzheim cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 20 Apr 2005 17:12:23 -0000 On Wed, Apr 20, 2005 at 11:52:33AM -0400, Brian Fundakowski Feldman wrote: > On Wed, Apr 20, 2005 at 05:35:28PM +0200, Marc Olzheim wrote: > > On Wed, Apr 20, 2005 at 11:20:38AM -0400, Brian Fundakowski Feldman wrote: > > > > Btw.: I'm not sure write(),writev() and pwrite() are allowed to do short > > > > writes on regular files... ? > > > Our manpage is incorrect; POSIX states that they are (see earlier > > > e-mail). There really is no alternative -- we simply can't build > > > an NFS transaction larger than our buffer cache can accomodate. > > > Note that short wries won't happen for normal buffer sizes, only > > > excessively large ones. I really don't believe that writev() is meant > > > to be used so that you can write gigantic data structures in a single > > > transaction... It is ok to return partial success if the first chunk of a large write succeeded and a later chunk failed persistently, but not if it cannot be performed as a single NFS transaction. > > Ah, I was reading the SUSv2 page: > > http://www.opengroup.org/onlinepubs/009695399/functions/write.html > > instead of the POSIX version. > > But in neither of those I can extrude the fact that it can return > > with result < nbyte, without it being a permanent condition. > > What phrase makes you conclude that it can ? > This specific issue is not clear-cut; the best thing to do lies somewhere > within the range of these scenarios: > "If a write() requests that more bytes be written than there is room > for (for example, [XSI] [Option Start] the process' file size limit > or [Option End] the physical end of a medium), only as many bytes as > there is room for shall be written. For example, suppose there is > space for 20 bytes more in a file before reaching a limit. A write of > 512 bytes will return 20. The next write of a non-zero number of bytes > would give a failure return (except as noted below)." This only applies to permanent conditions. > "When attempting to write to a file descriptor (other than a pipe or > FIFO) that supports non-blocking writes and cannot accept the data > immediately: > * If the O_NONBLOCK flag is clear, write() shall block the calling > thread until the data can be accepted. > * If the O_NONBLOCK flag is set, write() shall not block the > thread. If some data can be written without blocking the thread, > write() shall write what it can and return the number of bytes > written. Otherwise, it shall return -1 and set errno to [EAGAIN]." I think regular files do not support non-blocking writes, even if they are on NFS; in any case, O_NONBLOCK is disabled by default. > "[ENOBUFS] Insufficient resources were available in the system to > perform the operation." > I think the first is more useful behavior than the last. Supporting it > should be exactly the same as supporting what happens if the actual > filesystem fills up. In this case, the filesystem is being requested to > write more "than there is room for." The filesystem filling up is a totally different case as attempting the rest of the write is futile in that case. In a lot of code, a short write() is treated as a (fairly) persistent error. -- Jilles Tjoelker From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 17:30:33 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id CCC3316A4CE; Wed, 20 Apr 2005 17:30:32 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.3/8.13.1) with ESMTP id j3KHSew1073163; Wed, 20 Apr 2005 13:28:40 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.3/8.13.1/Submit) id j3KHSei8073162; Wed, 20 Apr 2005 13:28:40 -0400 (EDT) (envelope-from green) Date: Wed, 20 Apr 2005 13:28:39 -0400 From: Brian Fundakowski Feldman To: Jilles Tjoelker Message-ID: <20050420172839.GK1157@green.homeunix.org> References: <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> <20050420152038.GI1157@green.homeunix.org> <20050420153528.GC77731@stack.nl> <20050420155233.GJ1157@green.homeunix.org> <20050420171220.GB93623@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050420171220.GB93623@stack.nl> User-Agent: Mutt/1.5.6i cc: Marc Olzheim cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 20 Apr 2005 17:30:33 -0000 On Wed, Apr 20, 2005 at 07:12:20PM +0200, Jilles Tjoelker wrote: > On Wed, Apr 20, 2005 at 11:52:33AM -0400, Brian Fundakowski Feldman wrote: > > On Wed, Apr 20, 2005 at 05:35:28PM +0200, Marc Olzheim wrote: > > > On Wed, Apr 20, 2005 at 11:20:38AM -0400, Brian Fundakowski Feldman wrote: > > > > > Btw.: I'm not sure write(),writev() and pwrite() are allowed to do short > > > > > writes on regular files... ? > > > > > Our manpage is incorrect; POSIX states that they are (see earlier > > > > e-mail). There really is no alternative -- we simply can't build > > > > an NFS transaction larger than our buffer cache can accomodate. > > > > Note that short wries won't happen for normal buffer sizes, only > > > > excessively large ones. I really don't believe that writev() is meant > > > > to be used so that you can write gigantic data structures in a single > > > > transaction... > > It is ok to return partial success if the first chunk of a large write > succeeded and a later chunk failed persistently, but not if it cannot be > performed as a single NFS transaction. What is your rationale for this? > > > Ah, I was reading the SUSv2 page: > > > > http://www.opengroup.org/onlinepubs/009695399/functions/write.html > > > > instead of the POSIX version. > > > > But in neither of those I can extrude the fact that it can return > > > with result < nbyte, without it being a permanent condition. > > > What phrase makes you conclude that it can ? > > > This specific issue is not clear-cut; the best thing to do lies somewhere > > within the range of these scenarios: > > > "If a write() requests that more bytes be written than there is room > > for (for example, [XSI] [Option Start] the process' file size limit > > or [Option End] the physical end of a medium), only as many bytes as > > there is room for shall be written. For example, suppose there is > > space for 20 bytes more in a file before reaching a limit. A write of > > 512 bytes will return 20. The next write of a non-zero number of bytes > > would give a failure return (except as noted below)." > > This only applies to permanent conditions. > > > "When attempting to write to a file descriptor (other than a pipe or > > FIFO) that supports non-blocking writes and cannot accept the data > > immediately: > > > * If the O_NONBLOCK flag is clear, write() shall block the calling > > thread until the data can be accepted. > > > * If the O_NONBLOCK flag is set, write() shall not block the > > thread. If some data can be written without blocking the thread, > > write() shall write what it can and return the number of bytes > > written. Otherwise, it shall return -1 and set errno to [EAGAIN]." > > I think regular files do not support non-blocking writes, even if they > are on NFS; in any case, O_NONBLOCK is disabled by default. POSIX does not specify O_NONBLOCK semantics for regular files. This means we can do whatever is most useful. > > "[ENOBUFS] Insufficient resources were available in the system to > > perform the operation." > > > I think the first is more useful behavior than the last. Supporting it > > should be exactly the same as supporting what happens if the actual > > filesystem fills up. In this case, the filesystem is being requested to > > write more "than there is room for." > > The filesystem filling up is a totally different case as attempting the > rest of the write is futile in that case. No, it isn't. The filesystem may be not-full again soon, possibly even what the program might consider "immediately". > In a lot of code, a short write() is treated as a (fairly) persistent > error. I mentioned this several e-mails ago. Plenty of software is also not going to understand ENOBUFS. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 18:01:39 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 99BA516A4CE; Wed, 20 Apr 2005 18:01:39 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.3/8.13.1) with ESMTP id j3KHxkSc073470; Wed, 20 Apr 2005 13:59:46 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.3/8.13.1/Submit) id j3KHxkf5073469; Wed, 20 Apr 2005 13:59:46 -0400 (EDT) (envelope-from green) Date: Wed, 20 Apr 2005 13:59:46 -0400 From: Brian Fundakowski Feldman To: Garrett Wollman Message-ID: <20050420175946.GL1157@green.homeunix.org> References: <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> <20050420152038.GI1157@green.homeunix.org> <20050420153528.GC77731@stack.nl> <20050420155233.GJ1157@green.homeunix.org> <16998.37222.529748.205885@khavrinen.csail.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16998.37222.529748.205885@khavrinen.csail.mit.edu> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS client/buffer cache deadlock 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, 20 Apr 2005 18:01:40 -0000 On Wed, Apr 20, 2005 at 01:29:10PM -0400, Garrett Wollman wrote: > < said: > > > I think the first is more useful behavior than the last. Supporting it > > should be exactly the same as supporting what happens if the actual > > filesystem fills up. In this case, the filesystem is being requested to > > write more "than there is room for." > > Returning a short write for operations on regular files would > definitely be considered astonishing. The changes that you have made > should be considered flow control, not admission control, and should > appear to the user no differently than if we were waiting for a slow > disk to write something; i.e., the user thread should be blocked until > either the entire write completes, or the process is interrupted by a > signal. So what _would_ be consistent for nfs_bio.c::nfs_write()? IO_UNIT is set for all write calls which means "atomic", and nfs_rslock() and O_APPEND appear to at least attempt this. Please take a detailed look at the current system and the changes... it's far less clear-cut than POLA dictates. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 18:03:33 2005 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 B414116A4CE; Wed, 20 Apr 2005 18:03:33 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66D5343D2F; Wed, 20 Apr 2005 18:03:33 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 763AF1F062; Wed, 20 Apr 2005 20:03:32 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id 58D926583; Wed, 20 Apr 2005 20:03:32 +0200 (CEST) Date: Wed, 20 Apr 2005 20:03:32 +0200 From: Marc Olzheim To: Brian Fundakowski Feldman Message-ID: <20050420180332.GC99695@stack.nl> References: <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> <20050420152038.GI1157@green.homeunix.org> <20050420153528.GC77731@stack.nl> <20050420155233.GJ1157@green.homeunix.org> <20050420171220.GB93623@stack.nl> <20050420172839.GK1157@green.homeunix.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Y7xTucakfITjPcLV" Content-Disposition: inline In-Reply-To: <20050420172839.GK1157@green.homeunix.org> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i cc: Marc Olzheim cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org cc: Jilles Tjoelker Subject: Re: NFS client/buffer cache deadlock 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, 20 Apr 2005 18:03:33 -0000 --Y7xTucakfITjPcLV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 20, 2005 at 01:28:39PM -0400, Brian Fundakowski Feldman wrote: > > It is ok to return partial success if the first chunk of a large write > > succeeded and a later chunk failed persistently, but not if it cannot be > > performed as a single NFS transaction. >=20 > What is your rationale for this? Probably the part that you quoted about the write() after the short write() supposedly returning an error. Besides from that: since it isn't non-blocking, why not just block until everything is written ? That's the way it is done on FreeBSD 4.x and that's how I interpret the standards... Marc --Y7xTucakfITjPcLV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZpl0ezjnobFOgrERAmC1AKCoq4z0NDZ51FqUJYn8gtm6i7mkkACgyC67 Pgy9gPSlOR+D9vEC5vxVX74= =09w3 -----END PGP SIGNATURE----- --Y7xTucakfITjPcLV-- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 19:08:51 2005 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 DA52816A4CE; Wed, 20 Apr 2005 19:08:51 +0000 (GMT) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3B7743D48; Wed, 20 Apr 2005 19:08:50 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j3KJ8mWU082366; Wed, 20 Apr 2005 14:08:48 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4266A893.4010706@centtech.com> Date: Wed, 20 Apr 2005 14:08:03 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050325 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?UTF-8?B?U8WCYXdlayDFu2Fr?= References: <787bbe1c050418063313bf50df@mail.gmail.com> <20050418095708.A49866@eleanor.us1.wmi.uvac.net> <787bbe1c05041807366fd8818e@mail.gmail.com> In-Reply-To: <787bbe1c05041807366fd8818e@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: ClamAV 0.82/842/Tue Apr 19 16:39:01 2005 on mh1.centtech.com X-Virus-Status: Clean cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: 5.4-RC2 keyboard problem on Dell PowerEdge 2850 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, 20 Apr 2005 19:08:52 -0000 S=C5=82awek =C5=BBak wrote: > On 4/18/05, c0ldbyte wrote: >=20 >>On Mon, 18 Apr 2005, [ISO-8859-2] S=C2=B3awek =C2=AFak wrote: >> >> >>>Hi, >>> >>>After install from CD the keyboard doesn't work on this machine. Has >>>anyone else seen it? >>> >>>/S >> >>Select the correct key map screen map etc... ? >=20 >=20 > Erm. When I say keyboard doesn't work I *mean* it doesn't work at all. > The only key which works on the box is BRS, which doesn't give me > sufficient interaction with the system. I've skipped morse code > lessons and boy scouting in my life altogether. Did you get this solved? I have some Dell 2850's I might be able to test= this on. Eric --=20 ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 20:22:59 2005 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 9989E16A4CE; Wed, 20 Apr 2005 20:22:59 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96C6843D1D; Wed, 20 Apr 2005 20:22:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3KKOqQW090159; Wed, 20 Apr 2005 14:24:53 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4266B95A.7000909@samsco.org> Date: Wed, 20 Apr 2005 14:19:38 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org References: <200504080220.57899.max@love2party.net> <42626B36.1090204@samsco.org> In-Reply-To: <42626B36.1090204@samsco.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: monthly@FreeBSD.org Subject: Last REMINDER! Call for FreeBSD status reports 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, 20 Apr 2005 20:22:59 -0000 All, Last call for the quartly status report! If you still intent to submit one, please do so in the next 12 hours. Also, I'd like to remind everyone that submission are open to everyone, not just FreeBSD developers. We welcome all reports on projects and events in the FreeBSD community. Scott Scott Long wrote: > All, > > This is a reminder that status reports are due. We are going to extend > the deadline until the 20th to encourage people to submit a few more > reports. If you have any projects that you've been working on in the > past 3 months that are interesting and you would like to share, please > submit a report as soon as possible. The new web form from Julian makes > it incredibly easy to generate a submission without having to know a > thing about XML. The link for this is at: > > http://www.freebsd.org/cgi/monthly.cgi > > So, please submit your reports to monthly@freebsd.org by the 20th. > > Thanks, > > Scott Long, Max Laier, Tom Rhodes > > Max Laier wrote: > >> All, >> >> It's time again for some recapitulation of your FreeBSD activities of >> the last months. In order to not collided with the preparation of the >> 5.4 release we extended the cycle from bi-monthly to three months, so >> this one is open for anything that happend in 2005 until now. >> Submissions are due by April 15 to monthly@freebsd.org >> >> As always, reports about every FreeBSD related activity of the past >> months and coming weeks are welcome. In the past there was some focus >> on technical issues. In order to turn this into a more complete >> PR-vehicle, we highly encourage and welcome reports on non-technical >> matters as well. >> >> If you are yet unfamiliar with the status-reports, please take a look >> at the past reports: http://www.FreeBSD.org/news/status/ >> >> To support you in the process of fitting your report into the >> xml-template (available from: >> http://www.freebsd.org/news/status/report-sample.xml for those who >> still prefer a plain old text editor) Julian Elischer came up with the >> idea and prototype to have a web based form. Many thanks for that >> work. The cgi-script is being reviewed on freebsd-www now and will be >> linked to from http://www.freebsd.org/news/status/ shortly. >> >> The new features from last time (categories and task-list) will be >> available, again. As a reminder the available categories are listed >> bellow. Please feel free to suggest additional entries: >> >> proj - Projects (non-specific) >> docs - Documentation >> kern - Kernel >> arch - Architectures >> ports - Ports >> vendor - Vendor / 3rd party software >> misc - Miscellaneous >> >> Submissions are due on April 15. Thanks a lot, and we are hoping for >> a big turn-out. >> > From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 20:39:39 2005 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 2C68E16A4CE for ; Wed, 20 Apr 2005 20:39:39 +0000 (GMT) Received: from serl.cs.colorado.edu (serl.cs.colorado.edu [128.138.207.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB47C43D48 for ; Wed, 20 Apr 2005 20:39:38 +0000 (GMT) (envelope-from John.Giacomoni@colorado.edu) Received: from [IPv6???1] (localhost [127.0.0.1]) by serl.cs.colorado.edu (Postfix) with ESMTP id BD98F590CC for ; Wed, 20 Apr 2005 14:39:39 -0600 (MDT) Mime-Version: 1.0 (Apple Message framework v622) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-hackers@freebsd.org From: John Giacomoni Date: Wed, 20 Apr 2005 14:39:35 -0600 X-Mailer: Apple Mail (2.622) Subject: what goes wrong with barrier free atomic_load/store? 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, 20 Apr 2005 20:39:39 -0000 in reading /src/sys/i386/include/atomic.h I found this comment and I'm having trouble understanding what the problem being referred to below is. /* * We assume that a = b will do atomic loads and stores. However, on a * PentiumPro or higher, reads may pass writes, so for that case we have * to use a serializing instruction (i.e. with LOCK) to do the load in * SMP kernels. For UP kernels, however, the cache of the single processor * is always consistent, so we don't need any memory barriers. */ can someone give me an example of a situation where one needs to use memory barriers to ensure "correctness" when doing writes as above? the examples I can come up with seem to boil down to requiring locks or accepting stale values, given that without a synchronization mechanism one shouldn't expect two processes to act in any specific order. In my case I can accept reading a stale value so I'm not understanding the purpose of only having atomic_load/atomic_store wrappers with memory barriers. I saw a brief discussion where someone proposed barrier free load/store but don't think I saw any resolution. thanks, John G -- John.Giacomoni@colorado.edu University of Colorado at Boulder Department of Computer Science Engineering Center, ECCS 121 430 UCB Boulder, CO 80303-0430 USA From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 22:13:15 2005 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 DC53F16A4CE for ; Wed, 20 Apr 2005 22:13:15 +0000 (GMT) Received: from duchess.speedfactory.net (duchess.speedfactory.net [66.23.201.84]) by mx1.FreeBSD.org (Postfix) with SMTP id 33E2B43D2D for ; Wed, 20 Apr 2005 22:13:15 +0000 (GMT) (envelope-from ups@tree.com) Received: (qmail 17123 invoked by uid 89); 20 Apr 2005 22:13:13 -0000 Received: from duchess.speedfactory.net (66.23.201.84) by duchess.speedfactory.net with SMTP; 20 Apr 2005 22:13:13 -0000 Received: (qmail 17117 invoked by uid 89); 20 Apr 2005 22:13:13 -0000 Received: from unknown (HELO palm.tree.com) (66.23.216.49) by duchess.speedfactory.net with SMTP; 20 Apr 2005 22:13:13 -0000 Received: from [127.0.0.1] (localhost.tree.com [127.0.0.1]) by palm.tree.com (8.12.10/8.12.10) with ESMTP id j3KMDDw6030108; Wed, 20 Apr 2005 18:13:13 -0400 (EDT) (envelope-from ups@tree.com) From: Stephan Uphoff To: John Giacomoni In-Reply-To: References: Content-Type: text/plain Message-Id: <1114035193.17300.307.camel@palm> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 20 Apr 2005 18:13:13 -0400 Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: what goes wrong with barrier free atomic_load/store? 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, 20 Apr 2005 22:13:16 -0000 On Wed, 2005-04-20 at 16:39, John Giacomoni wrote: > in reading /src/sys/i386/include/atomic.h > > I found this comment and I'm having trouble understanding what the > problem being > referred to below is. > > /* > * We assume that a = b will do atomic loads and stores. However, on a > * PentiumPro or higher, reads may pass writes, so for that case we have > * to use a serializing instruction (i.e. with LOCK) to do the load in > * SMP kernels. For UP kernels, however, the cache of the single > processor > * is always consistent, so we don't need any memory barriers. > */ > > can someone give me an example of a situation where one needs to use > memory barriers to ensure "correctness" when doing writes as above? volatile int status = NOT_READY; volatile int data = -1; Thread 1: (CPU 0) ---------- data = 123; status = READY; Thread 2: (CPU 1) --------- if (status == READY) { my_data = data; } Read reordering my the CPUs may cause the following: Thread 2: out_of_order_read = data; Thread 1: data = 123; Thread 1: status = READY; Thread 2: if (status == READY) { Thread 2: my_data = out_of_order_read ; /* XXXX Unexpected VALUE */ Basically volatile does not work as expected. > the examples I can come up with seem to boil down to requiring locks > or accepting stale values, given that without a synchronization > mechanism > one shouldn't expect two processes to act in any specific order. The problem is that writes from another CPU (or DMA device) can be observed out of order. > In my case I can accept reading a stale value so I'm not understanding > the > purpose of only having atomic_load/atomic_store wrappers with memory > barriers. > > I saw a brief discussion where someone proposed barrier free load/store > but > don't think I saw any resolution. Do you mean load/store fences? A load fence could solve the problem above by preventing the out of order read of the data by thread 2. I actually found a race condition close to the one mentioned above in the kernel yesterday. So we may need to add fences real soon or rewrite the code to use a spin mutex. Stephan From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 02:07:13 2005 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 0A2D616A4CE for ; Thu, 21 Apr 2005 02:07:13 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA1F843D31 for ; Thu, 21 Apr 2005 02:07:12 +0000 (GMT) (envelope-from opensource.enthousiat@gmail.com) Received: by zproxy.gmail.com with SMTP id 18so58396nzp for ; Wed, 20 Apr 2005 19:07:12 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=AinYCJuu+iSji8fKmAreMftwEaeUUmtGvI3/bUkSkuWzfprDZd1LxCexCrt2pVrf25MJZtbkIzwUiBI5imVWf8by8A/xbZywv9zNYAM1enUYPrE1RNSM0Nlf805TTkH1XV/qb05QEdEyQ++/QED7yk5GQWqQSTxnA2J1HA8beqU= Received: by 10.36.88.3 with SMTP id l3mr140719nzb; Wed, 20 Apr 2005 19:07:12 -0700 (PDT) Received: by 10.36.109.8 with HTTP; Wed, 20 Apr 2005 19:07:12 -0700 (PDT) Message-ID: <37e1316605042019072b5d7a0e@mail.gmail.com> Date: Wed, 20 Apr 2005 22:07:12 -0400 From: Aziz KEZZOU To: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: KLD module with C++ iostreams ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Aziz KEZZOU List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 02:07:13 -0000 Hi hackers, I am wondering if I can use c++ iostreams inside the kernel ? After all the code : cout << "Hello world!" << endl;=20 ends accessing the stdout just like : printf("Hello world!\n"); right ? So if I could compile my KLD module with static linkage to libstdc++, that should be ok, right ? Any one did or knows how to do this ? Thanks, -aziz From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 02:13:09 2005 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 1E8C316A4CE for ; Thu, 21 Apr 2005 02:13:09 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id C695743D1F for ; Thu, 21 Apr 2005 02:13:08 +0000 (GMT) (envelope-from dleimbac@gmail.com) Received: by zproxy.gmail.com with SMTP id 40so388148nzk for ; Wed, 20 Apr 2005 19:13:08 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TfB2fmWeWrvFd34xzxEIWGU0zoKWfrFwYaOFcM8tNFPNA2rg9GIPSA7nqQqurSm7Ycs/Fy+jmmtHiD6F6e9PR1tuf7Ftfm/GwpKnPKxDKswuqHJDclkndoo5uQm6WZHdVqe4I9Tmkq8PD4cThzxJ/KCbXyJLJavz8kq3u0DpahM= Received: by 10.36.41.20 with SMTP id o20mr140565nzo; Wed, 20 Apr 2005 19:13:08 -0700 (PDT) Received: by 10.36.103.17 with HTTP; Wed, 20 Apr 2005 19:13:08 -0700 (PDT) Message-ID: <5bbfe7d4050420191316a629b7@mail.gmail.com> Date: Wed, 20 Apr 2005 19:13:08 -0700 From: David Leimbach To: Aziz KEZZOU In-Reply-To: <37e1316605042019072b5d7a0e@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <37e1316605042019072b5d7a0e@mail.gmail.com> cc: hackers@freebsd.org Subject: Re: KLD module with C++ iostreams ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Leimbach List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 02:13:09 -0000 Interesting question. People usually have to implement the C++ runtime to be usable from within the kernel. Things like exceptions and "stdout" may not be defined in kernel space :) I'm not terribly familiar with how it works on FreeBSD but I know it took a special effort to get C++ support into linux. Dave On 4/20/05, Aziz KEZZOU wrote: > Hi hackers, > I am wondering if I can use c++ iostreams inside the kernel ? > After all the code : cout << "Hello world!" << endl; > ends accessing the stdout just like : printf("Hello world!\n"); right ? >=20 > So if I could compile my KLD module with static linkage to libstdc++, > that should be ok, right ? >=20 > Any one did or knows how to do this ? >=20 > Thanks, > -aziz > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 02:28:55 2005 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 5310616A4CE for ; Thu, 21 Apr 2005 02:28:55 +0000 (GMT) Received: from april.chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id F170943D39 for ; Thu, 21 Apr 2005 02:28:54 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from [66.92.151.195] (july.chuckr.org [66.92.151.195]) by april.chuckr.org (Postfix) with ESMTP id 8A27E11777; Wed, 20 Apr 2005 22:20:05 -0400 (EDT) Message-ID: <42670F63.4000901@chuckr.org> Date: Thu, 21 Apr 2005 02:26:43 +0000 From: Chuck Robey User-Agent: Mozilla Thunderbird 1.0 (X11/20050316) X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Leimbach References: <37e1316605042019072b5d7a0e@mail.gmail.com> <5bbfe7d4050420191316a629b7@mail.gmail.com> In-Reply-To: <5bbfe7d4050420191316a629b7@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Aziz KEZZOU cc: hackers@freebsd.org Subject: Re: KLD module with C++ iostreams ? 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, 21 Apr 2005 02:28:55 -0000 David Leimbach wrote: > Interesting question. People usually have to implement the C++ > runtime to be usable from within the kernel. Things like exceptions > and "stdout" may not be defined in kernel space :) > > I'm not terribly familiar with how it works on FreeBSD but I know it > took a special effort to get C++ support into linux. > > Dave > > On 4/20/05, Aziz KEZZOU wrote: > >>Hi hackers, >>I am wondering if I can use c++ iostreams inside the kernel ? >>After all the code : cout << "Hello world!" << endl; >>ends accessing the stdout just like : printf("Hello world!\n"); right ? No, that's not true, all the iostreams stuff is totally independent. The iostreams stuff is coming from some of the ugliest code in C++. But, that's not the question, or at very least, it shouldn't BE the question. There is ZERO need to bring in features from C++, all it will do is to directly confuse the code base by greatly adding to the complexity of the code, without giving anything like equivalent features. Some very, very elegant work has been code, OO-ing the kernel code, adding OO features, all without violating the C language code base. Adding in C++ features over stdio stuff is so senseless, it's nearly obscene. If the gain at the end of the road was large enough, I wouldn't be against it so stridently, but I see *so* little gain. BTW, you know where the ugliest code in computer science today is: half is in the actual implementation of the cstdio/template code, the other half is the iostreams stuff. The fact that they energize some very elegant code is causing many folks never to see the fact of the horrible code lumps that exist out in the backyard. >> >>So if I could compile my KLD module with static linkage to libstdc++, >>that should be ok, right ? >> >>Any one did or knows how to do this ? >> >>Thanks, >>-aziz >>_______________________________________________ >>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" >> > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 02:33:43 2005 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 68BFC16A4CE for ; Thu, 21 Apr 2005 02:33:43 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8B3543D31 for ; Thu, 21 Apr 2005 02:33:42 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.3/8.13.1) with ESMTP id j3L2WfsX002898; Wed, 20 Apr 2005 20:32:41 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 20 Apr 2005 20:32:57 -0600 (MDT) Message-Id: <20050420.203257.69059150.imp@bsdimp.com> To: opensource.enthousiat@gmail.com From: "M. Warner Losh" In-Reply-To: <37e1316605042019072b5d7a0e@mail.gmail.com> References: <37e1316605042019072b5d7a0e@mail.gmail.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org Subject: Re: KLD module with C++ iostreams ? 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, 21 Apr 2005 02:33:43 -0000 In message: <37e1316605042019072b5d7a0e@mail.gmail.com> Aziz KEZZOU writes: : Hi hackers, : I am wondering if I can use c++ iostreams inside the kernel ? : After all the code : cout << "Hello world!" << endl; : ends accessing the stdout just like : printf("Hello world!\n"); right ? Just like, yes. Exactly the same thing as, no. The details matter here. There's a lot of code to make this happen. : So if I could compile my KLD module with static linkage to libstdc++, : that should be ok, right ? No. : Any one did or knows how to do this ? I've done C++ in the kernel before. IT is realtively easy to get very basic functioanlity. You won't have streams, exceptions, etc. However, to have all the features of C++ would take a lot of work. Warner From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 08:07:36 2005 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 0C29116A4CE for ; Thu, 21 Apr 2005 08:07:36 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2CB643D5A for ; Thu, 21 Apr 2005 08:07:35 +0000 (GMT) (envelope-from pollo.es.pollo@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so348968rne for ; Thu, 21 Apr 2005 01:07:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=XMZXLva4zRlrjw3GBtCr/oYAPmahQocBI7onVcglauOzC2MxW4+1L98a+JyPgkbfUgbcnOKvPMQlLwSfJ2v64dELAoX2cnEzfu0nptQ49l1iQhcmkeV8groLFJQMOBrTru+ATzpswYwa4ED01DGHGAC2HhMIc+4p2OglELa9Sls= Received: by 10.38.11.1 with SMTP id 1mr1923368rnk; Thu, 21 Apr 2005 01:07:35 -0700 (PDT) Received: by 10.38.209.11 with HTTP; Thu, 21 Apr 2005 01:07:35 -0700 (PDT) Message-ID: <98c02f5f050421010735a3cfe2@mail.gmail.com> Date: Thu, 21 Apr 2005 10:07:35 +0200 From: Omar Lopez Limonta To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: ipfw1sysctl and lifetime X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Omar Lopez Limonta List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 08:07:36 -0000 Hi: Anyone know what are the sysctl option to give more lifetime to net packets= ? Or another anything to elongate the net packets lifetime without use ipfw2? Thanks. --=20 http://pollo-es-pollo.blogspot.com Te lo traigo fresco. From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 08:09:11 2005 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 B4B2C16A4CE for ; Thu, 21 Apr 2005 08:09:11 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AFE543D46 for ; Thu, 21 Apr 2005 08:09:11 +0000 (GMT) (envelope-from slawek.zak@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so540433nzo for ; Thu, 21 Apr 2005 01:09:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ijv534WFKX9gOM6MNAZ6L+lFz1ZQsukjRVv4wFsKvMaPGdYWEaDIE5kCtixSHDakgg+Yknh7x4b3i7cMqZ1sX0Q0snbO68p24jAtRfVlofSBgYTte43Umv+TCSUiPxefLwMmEJwVHsSab5uyWCRWXuRpEUfZKk719R/cera3vzg= Received: by 10.36.81.11 with SMTP id e11mr159309nzb; Thu, 21 Apr 2005 01:09:10 -0700 (PDT) Received: by 10.36.88.17 with HTTP; Thu, 21 Apr 2005 01:09:09 -0700 (PDT) Message-ID: <787bbe1c05042101093eaadb26@mail.gmail.com> Date: Thu, 21 Apr 2005 10:09:09 +0200 From: =?ISO-8859-2?Q?S=B3awek_=AFak?= To: Eric Anderson In-Reply-To: <4266A893.4010706@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <787bbe1c050418063313bf50df@mail.gmail.com> <20050418095708.A49866@eleanor.us1.wmi.uvac.net> <787bbe1c05041807366fd8818e@mail.gmail.com> <4266A893.4010706@centtech.com> cc: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: 5.4-RC2 keyboard problem on Dell PowerEdge 2850 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: =?ISO-8859-2?Q?S=B3awek_=AFak?= List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 08:09:11 -0000 T24gNC8yMC8wNSwgRXJpYyBBbmRlcnNvbiA8YW5kZXJzb25AY2VudHRlY2guY29tPiB3cm90ZToK PiA+IEVybS4gV2hlbiBJIHNheSBrZXlib2FyZCBkb2Vzbid0IHdvcmsgSSAqbWVhbiogaXQgZG9l c24ndCB3b3JrIGF0IGFsbC4KPiA+IFRoZSBvbmx5IGtleSB3aGljaCB3b3JrcyBvbiB0aGUgYm94 IGlzIEJSUywgd2hpY2ggZG9lc24ndCBnaXZlIG1lCj4gPiBzdWZmaWNpZW50IGludGVyYWN0aW9u IHdpdGggdGhlIHN5c3RlbS4gSSd2ZSBza2lwcGVkIG1vcnNlIGNvZGUKPiA+IGxlc3NvbnMgYW5k IGJveSBzY291dGluZyBpbiBteSBsaWZlIGFsdG9nZXRoZXIuCj4gCj4gRGlkIHlvdSBnZXQgdGhp cyBzb2x2ZWQ/ICBJIGhhdmUgc29tZSBEZWxsIDI4NTAncyBJIG1pZ2h0IGJlIGFibGUgdG8gdGVz dCB0aGlzIG9uLgoKSGFkIG5vdCB0aW1lIHRvIHRlc3QgaXQuIEknbSBydW5uaW5nIHNlcmlhbCBj b25zb2xlIG9uIHRoZXNlIHRveXMgbm93LgpObyBwcm9ibGVtIGhlcmUuCgpCVFcgQmV3YXJlIG9m IHRoZSBzaGl0dHkgdmlydHVhbCBDRC9GbG9wcHkgZHJpdmVzIG9uIHRoZSBzZXJ2ZXIuIFRoZXJl CmlzIG5vIHdheSB0byB0dXJuIHRoZW0gb2ZmIGZyb20gQklPUy4gSGFkIG5vIGx1Y2sgd2l0aCBo aW50cyBlaXRoZXIuCjUuMyBmYWlscyB0byBib290IG9uIHRoZW0gc28gZG9uJ3QgZXZlbiB0cnkg aXQuIDUuNCBzcGl0cyBvdXQgc29tZQp3YXJuaW5nIG1lc3NhZ2VzIGR1cmluZyBib290IGFib3V0 IHRoZW0gYnV0IHRoZW4gcnVucyBmaW5lLiBEb24ndCBrbm93CmFib3V0IENVUlJFTlQuCgovUwot LSAKU7Nhd2VrIK9hayAvIFVOSVggU3lzdGVtcyBBZG1pbmlzdHJhdG9yCg== From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 08:35:39 2005 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 4F00916A4CE for ; Thu, 21 Apr 2005 08:35:39 +0000 (GMT) Received: from bgo1smout1.broadpark.no (bgo1smout1.broadpark.no [217.13.4.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2A2643D4C for ; Thu, 21 Apr 2005 08:35:36 +0000 (GMT) (envelope-from des@des.no) Received: from bgo1sminn1.broadpark.no ([217.13.4.93]) by bgo1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IFA00AESFLUMW50@bgo1smout1.broadpark.no> for hackers@freebsd.org; Thu, 21 Apr 2005 10:29:54 +0200 (CEST) Received: from dsa.des.no ([80.203.228.37]) by bgo1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IFA003WIFX5AVA0@bgo1sminn1.broadpark.no> for hackers@freebsd.org; Thu, 21 Apr 2005 10:36:42 +0200 (CEST) Received: by dsa.des.no (Pony Express, from userid 666) id 01C14EEE42; Thu, 21 Apr 2005 10:35:34 +0200 (CEST) Received: from xps.des.no (xps.des.no [10.0.0.12]) by dsa.des.no (Pony Express) with ESMTP id 9E10CEECC6; Thu, 21 Apr 2005 10:35:29 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 8588C33C09; Thu, 21 Apr 2005 10:35:29 +0200 (CEST) Date: Thu, 21 Apr 2005 10:35:29 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) In-reply-to: <6afb69aa05042008065db9d0cb@mail.gmail.com> To: Rex Roof Message-id: <864qe0ttm6.fsf@xps.des.no> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on dsa.des.no References: <6afb69aa05042008065db9d0cb@mail.gmail.com> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL autolearn=disabled version=3.0.2 X-Spam-Level: cc: hackers@freebsd.org Subject: Re: gvinum during bootup 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, 21 Apr 2005 08:35:39 -0000 Rex Roof writes: > I'm running a FreeBSD6 machine current as of a few days ago and I'm > working on a gvinum configuration, I couldn't find any place where it > referenced gvinum on startup so after fussing around with the rc > system a little, I wrote an /etc/rc.d/gvinum script that looks like > so: what about just adding geom_vinum_load=3D"YES" to /boot/loader.conf? DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 08:36:20 2005 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 2E25B16A4CE; Thu, 21 Apr 2005 08:36:20 +0000 (GMT) Received: from bgo1smout1.broadpark.no (bgo1smout1.broadpark.no [217.13.4.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE3CC43D1D; Thu, 21 Apr 2005 08:36:19 +0000 (GMT) (envelope-from des@des.no) Received: from bgo1sminn1.broadpark.no ([217.13.4.93]) by bgo1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IFA00AHDFN1ML50@bgo1smout1.broadpark.no>; Thu, 21 Apr 2005 10:30:37 +0200 (CEST) Received: from dsa.des.no ([80.203.228.37]) by bgo1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IFA003GJFYDAUA0@bgo1sminn1.broadpark.no>; Thu, 21 Apr 2005 10:37:25 +0200 (CEST) Received: by dsa.des.no (Pony Express, from userid 666) id 64860EBD28; Thu, 21 Apr 2005 10:36:18 +0200 (CEST) Received: from xps.des.no (xps.des.no [10.0.0.12]) by dsa.des.no (Pony Express) with ESMTP id C9987EBCB4; Thu, 21 Apr 2005 10:36:12 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id C40B733C1C; Thu, 21 Apr 2005 10:36:12 +0200 (CEST) Date: Thu, 21 Apr 2005 10:36:12 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) In-reply-to: <20050420153528.GC77731@stack.nl> To: Marc Olzheim Message-id: <86zmvssf0j.fsf@xps.des.no> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on dsa.des.no References: <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> <20050420152038.GI1157@green.homeunix.org> <20050420153528.GC77731@stack.nl> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL autolearn=disabled version=3.0.2 X-Spam-Level: cc: freebsd-current@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: NFS client/buffer cache deadlock 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, 21 Apr 2005 08:36:20 -0000 Marc Olzheim writes: > Ah, I was reading the SUSv2 page: > > http://www.opengroup.org/onlinepubs/009695399/functions/write.html > > instead of the POSIX version. POSIX =3D=3D SUSv3 these days. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 08:39:52 2005 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 C179D16A4CE for ; Thu, 21 Apr 2005 08:39:52 +0000 (GMT) Received: from bgo1smout1.broadpark.no (bgo1smout1.broadpark.no [217.13.4.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7225143D2F for ; Thu, 21 Apr 2005 08:39:52 +0000 (GMT) (envelope-from des@des.no) Received: from bgo1sminn1.broadpark.no ([217.13.4.93]) by bgo1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IFA00AQXFSYN050@bgo1smout1.broadpark.no> for hackers@freebsd.org; Thu, 21 Apr 2005 10:34:10 +0200 (CEST) Received: from dsa.des.no ([80.203.228.37]) by bgo1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IFA003YYG49AUA0@bgo1sminn1.broadpark.no> for hackers@freebsd.org; Thu, 21 Apr 2005 10:40:58 +0200 (CEST) Received: by dsa.des.no (Pony Express, from userid 666) id DF163EC9C0; Thu, 21 Apr 2005 10:39:50 +0200 (CEST) Received: from xps.des.no (xps.des.no [10.0.0.12]) by dsa.des.no (Pony Express) with ESMTP id 1E9AEEC9BA; Thu, 21 Apr 2005 10:39:47 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 14ECD33C09; Thu, 21 Apr 2005 10:39:47 +0200 (CEST) Date: Thu, 21 Apr 2005 10:39:47 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) In-reply-to: <37e1316605042019072b5d7a0e@mail.gmail.com> To: Aziz KEZZOU Message-id: <86vf6gseuk.fsf@xps.des.no> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on dsa.des.no References: <37e1316605042019072b5d7a0e@mail.gmail.com> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL autolearn=disabled version=3.0.2 X-Spam-Level: cc: hackers@freebsd.org Subject: Re: KLD module with C++ iostreams ? 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, 21 Apr 2005 08:39:52 -0000 Aziz KEZZOU writes: > I am wondering if I can use c++ iostreams inside the kernel ? > After all the code : cout << "Hello world!" << endl;=20 > ends accessing the stdout just like : printf("Hello world!\n"); right ? There is no stdio in the kernel. > So if I could compile my KLD module with static linkage to libstdc++, > that should be ok, right ? No. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 11:25:33 2005 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 5912616A4CE for ; Thu, 21 Apr 2005 11:25:33 +0000 (GMT) Received: from mxsf42.cluster1.charter.net (mxsf42.cluster1.charter.net [209.225.28.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAE3B43D1F for ; Thu, 21 Apr 2005 11:25:32 +0000 (GMT) (envelope-from c0ldbyte@myrealbox.com) Received: from mxip02.cluster1.charter.net (mxip02a.cluster1.charter.net [209.225.28.132])j3LBPVdZ007617 for ; Thu, 21 Apr 2005 07:25:31 -0400 Received: from 24.247.253.134.gha.mi.chartermi.net (HELO eleanor.us1.wmi.uvac.net) (24.247.253.134) by mxip02.cluster1.charter.net with ESMTP; 21 Apr 2005 07:25:31 -0400 X-Ironport-AV: i="3.92,120,1112587200"; d="scan'208"; a="864901726:sNHT12317502" Date: Thu, 21 Apr 2005 07:25:30 -0400 (EDT) From: c0ldbyte To: Omar Lopez Limonta In-Reply-To: <98c02f5f050421010735a3cfe2@mail.gmail.com> Message-ID: <20050421072350.V51738@eleanor.us1.wmi.uvac.net> References: <98c02f5f050421010735a3cfe2@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-hackers@freebsd.org Subject: Re: ipfw1sysctl and lifetime 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, 21 Apr 2005 11:25:33 -0000 On Thu, 21 Apr 2005, Omar Lopez Limonta wrote: > Hi: > > Anyone know what are the sysctl option to give more lifetime to net packets? > Or another anything to elongate the net packets lifetime without use ipfw2? > > Thanks. > sysctl -a |grep ttl will grep for any matching (Time To Live) settings. if thats what your looking for. -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 11:39:14 2005 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 9CEDF16A4CE for ; Thu, 21 Apr 2005 11:39:14 +0000 (GMT) Received: from mxsf10.cluster1.charter.net (mxsf10.cluster1.charter.net [209.225.28.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id B55CE43D55 for ; Thu, 21 Apr 2005 11:39:13 +0000 (GMT) (envelope-from c0ldbyte@myrealbox.com) Received: from mxip12.cluster1.charter.net (mxip12a.cluster1.charter.net [209.225.28.142])j3LBdBiO016619 for ; Thu, 21 Apr 2005 07:39:11 -0400 Received: from 24.247.253.134.gha.mi.chartermi.net (HELO eleanor.us1.wmi.uvac.net) (24.247.253.134) by mxip12.cluster1.charter.net with ESMTP; 21 Apr 2005 07:39:12 -0400 X-Ironport-AV: i="3.92,120,1112587200"; d="scan'208"; a="1084416339:sNHT14208512" Date: Thu, 21 Apr 2005 07:39:08 -0400 (EDT) From: c0ldbyte To: Jeremie Le Hen In-Reply-To: <20050420165559.GI91329@obiwan.tataz.chchile.org> Message-ID: <20050421073009.G51738@eleanor.us1.wmi.uvac.net> References: <20050420135013.GE91329@obiwan.tataz.chchile.org> <20050420151104.GA11753@grummit.biaix.org> <20050420165559.GI91329@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-hackers@freebsd.org Subject: Re: Configuration differences for jails 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, 21 Apr 2005 11:39:14 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 20 Apr 2005, Jeremie Le Hen wrote: >> I'm trying to untangle myself on this issue. I have different >> filesystems for /, /usr, and /usr/local, mounted in unusual places: >> >> 504,p0,1$ ls -l /usr{,/X11R6,/local} >> lrwxr-xr-x 1 root wheel 18 7 nov 2003 /usr -> fs/base/mount/usr/ >> lrwxr-xr-x 1 root wheel 25 8 nov 2003 /usr/X11R6 -> >> ../../../apps/mount/X11R6 >> lrwxr-xr-x 1 root wheel 25 18 abr 20:40 /usr/local -> >> ../../../apps/mount/local >> >> I know I want to share /usr, but not /usr/local, and only parts of /. So >> I mount_unionfs /fs/base inside the jail: >> >> :/fs/base/mount on /fs/jaildata/mount/fs/base/mount (unionfs, >> local, read-only, noclusterw) >> > mount_nullfs(8) will mount one directory and all its content onto another > one, but there is no way to exclude one of the subdirectory. You > will instead have to mount each subdirectory you need, not more. One > other way do achieve this is to make a second null mount over the > directory you don't wan't to share (/usr/local) but I'm not aware of > the consequences of such setup in term of performance and stability. > > >> But this way I don't get the "automagically upgrade virtual hosts" >> behaviour I want, since I'm missing /{,s}bin, /lib and /libexec and I >> definitely don't want to share /etc. > > You won't have a one to one mapping between jail and null mounts. There > are generally multiple null mounts for a unique jail. > > Considering your jail root is /jail/test, and you enabled the > jail_$jail_mount (jail_test_mount here) rc.conf(5) variable, here is > the content of /etc/fstab.test : > %%% > /bin /jail/test/bin nullfs ro 0 0 > /sbin /jail/test/sbin nullfs ro 0 0 > /lib /jail/test/lib nullfs ro 0 0 > /libexec /jail/test/libexec nullfs ro 0 0 > /usr/bin /jail/test/usr/bin nullfs ro 0 0 > /usr/sbin /jail/test/usr/sbin nullfs ro 0 0 > /usr/lib /jail/test/usr/lib nullfs ro 0 0 > /usr/libexec /jail/test/usr/libexec nullfs ro 0 0 > /usr/libdata /jail/test/usr/libdata nullfs ro 0 0 > /usr/share /jail/test/usr/share nullfs ro 0 0 > /usr/compat /jail/test/usr/compat nullfs ro 0 0 > %%% > >> I don't think it's easy to take /etc/ outside the root fs, but I don't >> see how to share /bin or /lib without leaking info. >> >> How do you handle this? What are those distribution targets and how can >> I use them? > > As I said above, null mount each directory. > > Regards, Now I havent caught this whole thread but to my understanding right now you are talking about mounting nullfs's from the root filesystem "/" onto the jail correct ?. Now if that last question is correct and thats the proccess you are using to create a jail then depending on the situation wouldnt that inturn defeat some of the main purposes of the jail, like the following. If you mounted your "/bin" on "/mnt/jail/bin" then if a person that was looking to break in and effect the system that is currently locked in the "jail" all he would have to do is just write something to the "jail/bin" which is actualy your root "/bin" and then the next time a binary is used from your root directories it could still infect the rest of the system ultimately defeating the purpose of what you just set up. To my understanding and use a jail is somewhat totaly independent of the OS that it resides in and wont be if you are using nullfs to mount root binary directories on it. With all due respect "This is a bad idea" given allmost any situation that you would have to create a jail for a unsafe proccess or users. - -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) Comment: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF7DF979F Comment: Fingerprint = D1DC 0AA4 1C4E EAD4 24EB 7E77 B261 50BA F7DF 979F iD8DBQFCZ5DfsmFQuvffl58RAi6FAJ4n1JeS/MCN2s7zowgWrMAzdnarowCfUQ5n sVhxoQT+nepoMnj/yYckQbs= =+Vmn -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 11:41:04 2005 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 D8B0516A4CE for ; Thu, 21 Apr 2005 11:41:04 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71B2C43D48 for ; Thu, 21 Apr 2005 11:41:04 +0000 (GMT) (envelope-from pollo.es.pollo@gmail.com) Received: by rproxy.gmail.com with SMTP id z35so404298rne for ; Thu, 21 Apr 2005 04:41:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VNzkT8/GF6ueUmUjcc99iK7x7rdRxJebg9C8eSSxTjPU24fVd/vRai0A/HENaBQpaxcaYZwn9iLzMbLOiXWRSsfABadwSptnZ8PgEREnl1l+28Qd9AC8IY/TO52HdsS/rrPL75c1iqOuTK8kFn7SDfANHoGUtUHY0+RJiG3muMo= Received: by 10.38.150.79 with SMTP id x79mr2102823rnd; Thu, 21 Apr 2005 04:41:03 -0700 (PDT) Received: by 10.38.209.11 with HTTP; Thu, 21 Apr 2005 04:41:03 -0700 (PDT) Message-ID: <98c02f5f05042104414bb668c3@mail.gmail.com> Date: Thu, 21 Apr 2005 13:41:03 +0200 From: Omar Lopez Limonta To: c0ldbyte In-Reply-To: <20050421072350.V51738@eleanor.us1.wmi.uvac.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <98c02f5f050421010735a3cfe2@mail.gmail.com> <20050421072350.V51738@eleanor.us1.wmi.uvac.net> cc: freebsd-hackers@freebsd.org Subject: Re: ipfw1sysctl and lifetime X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Omar Lopez Limonta List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 11:41:05 -0000 I Change:=20 net.inet.ip.fw.dyn_ack_lifetime: 300 -> 3600 net.inet.ip.fw.dyn_udp_lifetime: 10 -> 10 net.inet.ip.fw.dyn_buckets: 256 -> 1024 net.inet.ip.fw.dyn_max: 1000 -> 2500 =BFAre good these values? , =BFi need chanege another value? =20 2005/4/21, c0ldbyte : > On Thu, 21 Apr 2005, Omar Lopez Limonta wrote: >=20 > > Hi: > > > > Anyone know what are the sysctl option to give more lifetime to net pac= kets? > > Or another anything to elongate the net packets lifetime without use ip= fw2? > > > > Thanks. > > >=20 > sysctl -a |grep ttl >=20 > will grep for any matching (Time To Live) settings. > if thats what your looking for. >=20 > -- > ( When in doubt, use brute force. -- Ken Thompson 1998 ) >=20 --=20 http://pollo-es-pollo.blogspot.com Te lo traigo fresco. From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 11:44:15 2005 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 B91A816A4CE for ; Thu, 21 Apr 2005 11:44:15 +0000 (GMT) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64F1743D3F for ; Thu, 21 Apr 2005 11:44:15 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (wlan032024.uni-rostock.de [139.30.32.24]) by hydra.bec.de (Postfix) with ESMTP id 57F4135707 for ; Thu, 21 Apr 2005 13:44:14 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1001) id D1FEB7D0A; Thu, 21 Apr 2005 13:43:59 +0200 (CEST) Date: Thu, 21 Apr 2005 13:43:59 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Message-ID: <20050421114359.GA10842@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20050420135013.GE91329@obiwan.tataz.chchile.org> <20050420151104.GA11753@grummit.biaix.org> <20050420165559.GI91329@obiwan.tataz.chchile.org> <20050421073009.G51738@eleanor.us1.wmi.uvac.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050421073009.G51738@eleanor.us1.wmi.uvac.net> User-Agent: Mutt/1.5.9i Subject: Re: Configuration differences for jails 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, 21 Apr 2005 11:44:15 -0000 On Thu, Apr 21, 2005 at 07:39:08AM -0400, c0ldbyte wrote: > Now if that last question is correct and thats the proccess you are using > to create a jail then depending on the situation wouldnt that inturn > defeat some of the main purposes of the jail, like the following. If you > mounted your "/bin" on "/mnt/jail/bin" then if a person that was looking > to break in and effect the system that is currently locked in the "jail" > all he would have to do is just write something to the "jail/bin" which is > actualy your root "/bin" and then the next time a binary is used from your > root directories it could still infect the rest of the system ultimately > defeating the purpose of what you just set up. To my understanding and use > a jail is somewhat totaly independent of the OS that it resides in and > wont be if you are using nullfs to mount root binary directories on it. ro mount as written by grant parent protects against this. Joerg From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 13:35:41 2005 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 7C76816A4CE; Wed, 20 Apr 2005 13:35:41 +0000 (GMT) Received: from grant.org (grant.org [206.190.173.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id D838F43D1F; Wed, 20 Apr 2005 13:35:40 +0000 (GMT) (envelope-from Devon@Jovi.Net) Received: from grant.org (localhost [127.0.0.1]) by grant.org (8.12.11/8.12.11) with ESMTP id j3KDZM1s086062 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Apr 2005 09:35:23 -0400 (EDT) (envelope-from Devon@Jovi.Net) Received: (from devon@localhost) by grant.org (8.12.11/8.12.11/Submit) id j3KDZMZ4086059; Wed, 20 Apr 2005 09:35:22 -0400 (EDT) (envelope-from Devon@Jovi.Net) Date: Wed, 20 Apr 2005 09:35:22 -0400 (EDT) Message-Id: <200504201335.j3KDZMZ4086059@grant.org> X-Authentication-Warning: grant.org: devon set sender to Devon@Jovi.Net using -f From: Devon@Jovi.Net To: "Steven Hartland" In-reply-to: <011901c545a9$e5ac6fc0$b3db87d4@multiplay.co.uk> (killing@multiplay.co.uk) References: <200504192127.j3JLR9Oq055796@grant.org><20050420083114.X46699@eleanor.us1.wmi.uvac.net> <200504201248.j3KCmYH3071130@grant.org> <011901c545a9$e5ac6fc0$b3db87d4@multiplay.co.uk> X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, NO_REAL_NAME autolearn=ham version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on grant.org X-Virus-Scanned: by amavisd-new X-Mailman-Approved-At: Thu, 21 Apr 2005 11:51:09 +0000 cc: security-advisories@freebsd.org cc: c0ldbyte@myrealbox.com cc: FreeBSD-2005@Jovi.Net cc: killing@BarrysWorld.com cc: freebsd-hackers@freebsd.org Subject: Re: sshd dieing? after applying FreeBSD-SA-03:12.openssh 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, 20 Apr 2005 13:35:41 -0000 In the future, please do as I did and publish whatever solution you find, my answer was somewhat lame but worked for me and will help the next guy. To the SSH server /etc/hosts I added the client machine, now when it gets to debug1: got SSH2_MSG_SERVICE_ACCEPT it hangs for only 75 seconds. Peace --Devon /~\ \ / Health Care X not warfare / \ Dubya won the digital vote Kerry won the popular vote From: "Steven Hartland" Cc: , , , Date: Wed, 20 Apr 2005 14:07:21 +0100 Sorry I don't remember the solution we came up with. It was a long time ago. I think it was to do with DNS invalid / broken DNS or something like that but I couldn't say for sure. Regards Steve ----- Original Message ----- From: > > This trouble hit me yesterday, 2005 Apr 19 Tue, Google led me to > someone else with the exact same trouble. What use to ask the net > if nobody publishes an ANSWER? A good netizen does the right thing. > By citing the original question, I create a link to a possible answer. ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 16:29:12 2005 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 D753A16A4CE for ; Wed, 20 Apr 2005 16:29:12 +0000 (GMT) Received: from hotmail.com (bay2-f23.bay2.hotmail.com [65.54.247.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id B01AA43D53 for ; Wed, 20 Apr 2005 16:29:12 +0000 (GMT) (envelope-from jas_arlerr@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 20 Apr 2005 09:29:12 -0700 Message-ID: Received: from 61.187.54.13 by by2fd.bay2.hotmail.msn.com with HTTP; Wed, 20 Apr 2005 16:29:11 GMT X-Originating-IP: [61.187.54.13] X-Originating-Email: [jas_arlerr@hotmail.com] X-Sender: jas_arlerr@hotmail.com In-Reply-To: <20050420143715.GF91329@obiwan.tataz.chchile.org> From: =?gb2312?B?1cUgt+c=?= To: jeremie@le-hen.org Date: Wed, 20 Apr 2005 16:29:11 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed X-OriginalArrivalTime: 20 Apr 2005 16:29:12.0083 (UTC) FILETIME=[15C26630:01C545C6] X-Mailman-Approved-At: Thu, 21 Apr 2005 11:51:09 +0000 cc: freebsd-hackers@freebsd.org Subject: Re: Configuration differences for jails 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, 20 Apr 2005 16:29:12 -0000 >From: Jeremie Le Hen >To: ?? ?? >CC: freebsd-hackers@freebsd.org >Subject: Re: Configuration differences for jails >Date: Wed, 20 Apr 2005 16:37:15 +0200 > > > Now with some distance, I must admit that all this gymnastic is quite > > boring. I now decided to run two virtual hosts as they are managed in > > a very natural way. These two hosts are just like two real boxes, one > > running Bind and the other one running Postfix. When I need to update > > something in the configuration, I login to the box with ssh(1). This > > take some more memory and in principle no CPU as all processes are > > sleeping most of the time. > >I forgotten to explain that using virtual hosts require some >administration too in order to avoid wasting disk space. The jail(8) >manual page advices to make world with DESTDIR set. I prefer using >null mounts as it doesn't require additional disk space and an upgrade >of the host will automagically upgrade virtual hosts. You will >nevertheless have to make distribution and distrib-dirs. Here are the >directories I advice you to share : > /bin /sbin /lib /libexec > /usr/bin /usr/sbin /usr/lib /usr/libexec /usr/libdata /usr/share > /usr/doc /usr/compat /usr/ports > >Sharing ports may be more difficult as it may require sharing the >port database, but I think it's still possible. > Good idea! I will take a try! Regards Jas _________________________________________________________________ 享用世界上最大的电子邮件系统— MSN Hotmail。 http://www.hotmail.com From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 17:16:09 2005 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 F1FCC16A4CE; Wed, 20 Apr 2005 17:16:08 +0000 (GMT) Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu [128.30.28.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84F5F43D31; Wed, 20 Apr 2005 17:16:08 +0000 (GMT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (localhost.csail.mit.edu [127.0.0.1]) j3KHG6Ni036897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Wed, 20 Apr 2005 13:16:06 -0400 (EDT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: (from wollman@localhost) by khavrinen.csail.mit.edu (8.13.1/8.13.1/Submit) id j3KHG5C4036894; Wed, 20 Apr 2005 13:16:05 -0400 (EDT) (envelope-from wollman) From: Garrett Wollman MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16998.36437.809896.936800@khavrinen.csail.mit.edu> Date: Wed, 20 Apr 2005 13:16:05 -0400 To: Marc Olzheim In-Reply-To: <20050420143842.GB77731@stack.nl> References: <20050418202213.GC1157@green.homeunix.org> <20050418203321.GA88774@stack.nl> <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-1.6 (khavrinen.csail.mit.edu [127.0.0.1]); Wed, 20 Apr 2005 13:16:06 -0400 (EDT) X-Virus-Scanned: ClamAV 0.83/842/Tue Apr 19 17:39:01 2005 on khavrinen.csail.mit.edu X-Virus-Status: Clean X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on khavrinen.csail.mit.edu X-Mailman-Approved-At: Thu, 21 Apr 2005 11:51:09 +0000 cc: freebsd-hackers@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS client/buffer cache deadlock 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, 20 Apr 2005 17:16:09 -0000 < said: > Btw.: I'm not sure write(),writev() and pwrite() are allowed to do short > writes on regular files... ? I believe it is the intent of the Standard to prohibit this (a paragraph in the rationale says that short writes can only happen if O_NONBLOCK is set, but this is clearly wrong because the normative text says end-of-medium also results in a short write) but there does not appear to be any language which requires atomic behavior for descriptors other than pipes and FIFOs. As a quality-of-implementation matter, for writes to regular files not to be atomic would be considered surprising. -GAWollman From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 20 17:29:12 2005 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 73AF716A4CE; Wed, 20 Apr 2005 17:29:12 +0000 (GMT) Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu [128.30.28.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08E5743D49; Wed, 20 Apr 2005 17:29:12 +0000 (GMT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (localhost.csail.mit.edu [127.0.0.1]) j3KHTANG037030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Wed, 20 Apr 2005 13:29:11 -0400 (EDT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: (from wollman@localhost) by khavrinen.csail.mit.edu (8.13.1/8.13.1/Submit) id j3KHTAmT037027; Wed, 20 Apr 2005 13:29:10 -0400 (EDT) (envelope-from wollman) From: Garrett Wollman MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16998.37222.529748.205885@khavrinen.csail.mit.edu> Date: Wed, 20 Apr 2005 13:29:10 -0400 To: Brian Fundakowski Feldman In-Reply-To: <20050420155233.GJ1157@green.homeunix.org> References: <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> <20050420152038.GI1157@green.homeunix.org> <20050420153528.GC77731@stack.nl> <20050420155233.GJ1157@green.homeunix.org> X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-1.6 (khavrinen.csail.mit.edu [127.0.0.1]); Wed, 20 Apr 2005 13:29:11 -0400 (EDT) X-Virus-Scanned: ClamAV 0.83/842/Tue Apr 19 17:39:01 2005 on khavrinen.csail.mit.edu X-Virus-Status: Clean X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on khavrinen.csail.mit.edu X-Mailman-Approved-At: Thu, 21 Apr 2005 11:51:09 +0000 cc: freebsd-hackers@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS client/buffer cache deadlock 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, 20 Apr 2005 17:29:12 -0000 < said: > I think the first is more useful behavior than the last. Supporting it > should be exactly the same as supporting what happens if the actual > filesystem fills up. In this case, the filesystem is being requested to > write more "than there is room for." Returning a short write for operations on regular files would definitely be considered astonishing. The changes that you have made should be considered flow control, not admission control, and should appear to the user no differently than if we were waiting for a slow disk to write something; i.e., the user thread should be blocked until either the entire write completes, or the process is interrupted by a signal. -GAWollman From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 11:53:28 2005 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 1B47916A4CE for ; Thu, 21 Apr 2005 11:53:28 +0000 (GMT) Received: from mxsf01.cluster1.charter.net (mxsf01.cluster1.charter.net [209.225.28.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9873843D5A for ; Thu, 21 Apr 2005 11:53:27 +0000 (GMT) (envelope-from c0ldbyte@myrealbox.com) Received: from mxip12.cluster1.charter.net (mxip12a.cluster1.charter.net [209.225.28.142])j3LBrQUe026736 for ; Thu, 21 Apr 2005 07:53:26 -0400 Received: from 24.247.253.134.gha.mi.chartermi.net (HELO eleanor.us1.wmi.uvac.net) (24.247.253.134) by mxip12.cluster1.charter.net with ESMTP; 21 Apr 2005 07:53:25 -0400 X-Ironport-AV: i="3.92,120,1112587200"; d="scan'208"; a="1084441718:sNHT48147884" Date: Thu, 21 Apr 2005 07:53:25 -0400 (EDT) From: c0ldbyte To: Omar Lopez Limonta In-Reply-To: <98c02f5f05042104414bb668c3@mail.gmail.com> Message-ID: <20050421075035.P51738@eleanor.us1.wmi.uvac.net> References: <98c02f5f050421010735a3cfe2@mail.gmail.com> <98c02f5f05042104414bb668c3@mail.gmail.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1197859956-1114084405=:51738" cc: freebsd-hackers@freebsd.org Subject: Re: ipfw1sysctl and lifetime 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, 21 Apr 2005 11:53:28 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1197859956-1114084405=:51738 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 21 Apr 2005, Omar Lopez Limonta wrote: > I Change: > > > net.inet.ip.fw.dyn_ack_lifetime: 300 -> 3600 > > net.inet.ip.fw.dyn_udp_lifetime: 10 -> 10 > > net.inet.ip.fw.dyn_buckets: 256 -> 1024 > > net.inet.ip.fw.dyn_max: 1000 -> 2500 > > 緼re good these values? , 縤 need chanege another value? > Dont know my friend. I have no way of testing those out right now. I assume those values are from a 5.x machine I only run 4.x's at the moment untill I test 5.4-RELEASE more and evaluate its potential and gain on my systems. -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) --0-1197859956-1114084405=:51738-- From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 12:23:49 2005 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 630E016A4CE for ; Thu, 21 Apr 2005 12:23:49 +0000 (GMT) Received: from mxsf20.cluster1.charter.net (mxsf20.cluster1.charter.net [209.225.28.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFCB743D55 for ; Thu, 21 Apr 2005 12:23:48 +0000 (GMT) (envelope-from c0ldbyte@myrealbox.com) Received: from mxip04.cluster1.charter.net (mxip04a.cluster1.charter.net [209.225.28.134])j3LCNl0X030896 for ; Thu, 21 Apr 2005 08:23:47 -0400 Received: from 24.247.253.134.gha.mi.chartermi.net (HELO eleanor.us1.wmi.uvac.net) (24.247.253.134) by mxip04.cluster1.charter.net with ESMTP; 21 Apr 2005 08:23:47 -0400 X-Ironport-AV: i="3.92,120,1112587200"; d="scan'208"; a="236680817:sNHT16355016" Date: Thu, 21 Apr 2005 08:23:46 -0400 (EDT) From: c0ldbyte To: freebsd-hackers@freebsd.org In-Reply-To: <20050421114359.GA10842@britannica.bec.de> Message-ID: <20050421081253.S51738@eleanor.us1.wmi.uvac.net> References: <20050420151104.GA11753@grummit.biaix.org> <20050421073009.G51738@eleanor.us1.wmi.uvac.net> <20050421114359.GA10842@britannica.bec.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: Configuration differences for jails 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, 21 Apr 2005 12:23:49 -0000 On Thu, 21 Apr 2005, Joerg Sonnenberger wrote: > On Thu, Apr 21, 2005 at 07:39:08AM -0400, c0ldbyte wrote: >> Now if that last question is correct and thats the proccess you are using >> to create a jail then depending on the situation wouldnt that inturn >> defeat some of the main purposes of the jail, like the following. If you >> mounted your "/bin" on "/mnt/jail/bin" then if a person that was looking >> to break in and effect the system that is currently locked in the "jail" >> all he would have to do is just write something to the "jail/bin" which is >> actualy your root "/bin" and then the next time a binary is used from your >> root directories it could still infect the rest of the system ultimately >> defeating the purpose of what you just set up. To my understanding and use >> a jail is somewhat totaly independent of the OS that it resides in and >> wont be if you are using nullfs to mount root binary directories on it. > > ro mount as written by grant parent protects against this. > > Joerg Right, I saw the (ro) option as you specified, but still there have been flaws in the sytem and forseen more flaws to come as allmost any programmer these days come accross and to just rely on it being (ro) just seems kind of not something that you should look to totaly to protect the system that the jail resides on. Even though in the unpredicted future a jail could be broken out of to such a instance I consider it to be a safer practice to just make installworld $DESTDIR && make distribution DESTDIR=$DESTJAIL -DNO_MAKEDEV_RUN and just delete stuff out of $DESTJAIL that you dont need for things to run properly and then there is never a instance or less of a chance that things will go wrong for you. As I said before depending on the use of the jail as well would also be a determination on how the jail is setup to but should never interact with the main system that holds the jail. Thats only my opinion though and just releaves thought about other security issues that deal with the main part of the system. -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 12:31:19 2005 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 EC37316A4CE for ; Thu, 21 Apr 2005 12:31:18 +0000 (GMT) Received: from smp500.sitetronics.com (sitetronics.com [82.192.77.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3050F43D2F for ; Thu, 21 Apr 2005 12:31:16 +0000 (GMT) (envelope-from dodell@offmyserver.com) Received: from localhost.sitetronics.com ([127.0.0.1] helo=smp500.sitetronics.com) by smp500.sitetronics.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.50 (FreeBSD)) id 1DOanP-000Bz2-18 for freebsd-hackers@freebsd.org; Thu, 21 Apr 2005 14:28:39 +0200 Received: (from dodell@localhost) by smp500.sitetronics.com (8.12.11/8.12.11/Submit) id j3LCScu3046067 for freebsd-hackers@freebsd.org; Thu, 21 Apr 2005 14:28:38 +0200 (CEST) (envelope-from dodell@offmyserver.com) X-Authentication-Warning: smp500.sitetronics.com: dodell set sender to dodell@offmyserver.com using -f Date: Thu, 21 Apr 2005 14:28:37 +0200 From: "Devon H. O'Dell " To: freebsd-hackers@freebsd.org Message-ID: <20050421122837.GK41520@smp500.sitetronics.com> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20050420151104.GA11753@grummit.biaix.org> <20050421073009.G51738@eleanor.us1.wmi.uvac.net> <20050421114359.GA10842@britannica.bec.de> <20050421081253.S51738@eleanor.us1.wmi.uvac.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tAmVnWIZ6lqEAvSf" Content-Disposition: inline In-Reply-To: <20050421081253.S51738@eleanor.us1.wmi.uvac.net> User-Agent: Mutt/1.5.8i Subject: Re: Configuration differences for jails 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, 21 Apr 2005 12:31:19 -0000 --tAmVnWIZ6lqEAvSf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 21, 2005 at 08:23:46AM -0400, c0ldbyte wrote: > On Thu, 21 Apr 2005, Joerg Sonnenberger wrote: >=20 > >On Thu, Apr 21, 2005 at 07:39:08AM -0400, c0ldbyte wrote: > >>Now if that last question is correct and thats the proccess you are usi= ng > >>to create a jail then depending on the situation wouldnt that inturn > >>defeat some of the main purposes of the jail, like the following. If you > >>mounted your "/bin" on "/mnt/jail/bin" then if a person that was looking > >>to break in and effect the system that is currently locked in the "jail" > >>all he would have to do is just write something to the "jail/bin" which= is > >>actualy your root "/bin" and then the next time a binary is used from y= our > >>root directories it could still infect the rest of the system ultimately > >>defeating the purpose of what you just set up. To my understanding and = use > >>a jail is somewhat totaly independent of the OS that it resides in and > >>wont be if you are using nullfs to mount root binary directories on it. > > > >ro mount as written by grant parent protects against this. > > > >Joerg >=20 > Right, I saw the (ro) option as you specified, but still there have > been flaws in the sytem and forseen more flaws to come as allmost > any programmer these days come accross and to just rely on it being > (ro) just seems kind of not something that you should look to totaly > to protect the system that the jail resides on. Even though in the > unpredicted future a jail could be broken out of to such a instance > I consider it to be a safer practice to just make installworld > $DESTDIR && make distribution DESTDIR=3D$DESTJAIL -DNO_MAKEDEV_RUN > and just delete stuff out of $DESTJAIL that you dont need for things > to run properly and then there is never a instance or less of a > chance that things will go wrong for you. As I said before depending > on the use of the jail as well would also be a determination on > how the jail is setup to but should never interact with the main > system that holds the jail. >=20 > Thats only my opinion though and just releaves thought about other > security issues that deal with the main part of the system. Well he's per his statement using it in a virtual server environment where he would simply like to ease administrative work by reducing the number of jails that need to be upgraded every time. The likelyhood of there being an issue with read only mounts is quite low. I'd consider the ability to break out of a jail as more of a threat than that. Additionally, I'm pretty sure it wouldn't be very difficult to prove that there are no issues with this. Read only mounts are so useful, and frequent, that I'm quite sure we'd know if there were security issues with them. As with any jail, you are in part trusting the security of the main machine, since it has access to all the jailed environments. I'd be worried about this being compromised before I point out possible (non-existant) issues with read-only mounts. --Devon > --=20 > ( When in doubt, use brute force. -- Ken Thompson 1998 ) > _______________________________________________ > 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" >=20 > !DSPAM:42679acd458596534657138! >=20 --tAmVnWIZ6lqEAvSf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZ5x1Skf3jVXOdl0RAqANAJ45cSAtX391eM9sCz4vLC4m+WnCnQCgmisx 3s62tN8SN+S0r8Px/HKQRQI= =C29+ -----END PGP SIGNATURE----- --tAmVnWIZ6lqEAvSf-- From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 12:50:09 2005 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 AEA2616A4CE for ; Thu, 21 Apr 2005 12:50:09 +0000 (GMT) Received: from smp500.sitetronics.com (sitetronics.com [82.192.77.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B86D43D41 for ; Thu, 21 Apr 2005 12:50:09 +0000 (GMT) (envelope-from dodell@offmyserver.com) Received: from localhost.sitetronics.com ([127.0.0.1] helo=smp500.sitetronics.com) by smp500.sitetronics.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.50 (FreeBSD)) id 1DOb5g-000C3F-U3 for freebsd-hackers@freebsd.org; Thu, 21 Apr 2005 14:47:33 +0200 Received: (from dodell@localhost) by smp500.sitetronics.com (8.12.11/8.12.11/Submit) id j3LClWi2046328 for freebsd-hackers@freebsd.org; Thu, 21 Apr 2005 14:47:32 +0200 (CEST) (envelope-from dodell@offmyserver.com) X-Authentication-Warning: smp500.sitetronics.com: dodell set sender to dodell@offmyserver.com using -f Date: Thu, 21 Apr 2005 14:47:32 +0200 From: "Devon H. O'Dell " To: freebsd-hackers@freebsd.org Message-ID: <20050421124732.GN41520@smp500.sitetronics.com> Mail-Followup-To: freebsd-hackers@freebsd.org References: <395120190.1114087603580.JavaMail.nobody@app5.ni.bg> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4oQnj4jcM03NhqPN" Content-Disposition: inline In-Reply-To: <395120190.1114087603580.JavaMail.nobody@app5.ni.bg> User-Agent: Mutt/1.5.8i Subject: Re: ABV.BG ??????????? ??????? 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, 21 Apr 2005 12:50:09 -0000 --4oQnj4jcM03NhqPN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Apr 21, 2005 at 03:46:43PM +0300, freebsd-hackers@freebsd.org wrote: > blagodarq za izpratenoto ot Vas pismo nai skoro shte vi otgovorq!! Turn this off. --4oQnj4jcM03NhqPN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZ6DkSkf3jVXOdl0RAv10AJ4u8OwTfOXG3EcywjWFAeHn2T05RwCgjIze aQmDdh11a/AsGPtpX/PQ3z4= =vJI1 -----END PGP SIGNATURE----- --4oQnj4jcM03NhqPN-- From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 13:00:30 2005 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 0B17916A4CF for ; Thu, 21 Apr 2005 13:00:30 +0000 (GMT) Received: from smp500.sitetronics.com (sitetronics.com [82.192.77.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB7AB43D4C for ; Thu, 21 Apr 2005 13:00:29 +0000 (GMT) (envelope-from dodell@offmyserver.com) Received: from localhost.sitetronics.com ([127.0.0.1] helo=smp500.sitetronics.com) by smp500.sitetronics.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.50 (FreeBSD)) id 1DObFh-000C4l-5k for freebsd-hackers@freebsd.org; Thu, 21 Apr 2005 14:57:53 +0200 Received: (from dodell@localhost) by smp500.sitetronics.com (8.12.11/8.12.11/Submit) id j3LCvrdn046422 for freebsd-hackers@freebsd.org; Thu, 21 Apr 2005 14:57:53 +0200 (CEST) (envelope-from dodell@offmyserver.com) X-Authentication-Warning: smp500.sitetronics.com: dodell set sender to dodell@offmyserver.com using -f Date: Thu, 21 Apr 2005 14:57:53 +0200 From: "Devon H. O'Dell " To: freebsd-hackers@freebsd.org Message-ID: <20050421125753.GO41520@smp500.sitetronics.com> Mail-Followup-To: freebsd-hackers@freebsd.org References: <395120190.1114087603580.JavaMail.nobody@app5.ni.bg> <20050421124732.GN41520@smp500.sitetronics.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QGBKWVSgmlsIyJ+t" Content-Disposition: inline In-Reply-To: <20050421124732.GN41520@smp500.sitetronics.com> User-Agent: Mutt/1.5.8i Subject: Re: ABV.BG ??????????? ??????? 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, 21 Apr 2005 13:00:30 -0000 --QGBKWVSgmlsIyJ+t Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 21, 2005 at 02:47:32PM +0200, Devon H. O'Dell wrote: > On Thu, Apr 21, 2005 at 03:46:43PM +0300, freebsd-hackers@freebsd.org wro= te: ^- whoops, I didn't notice that. > > blagodarq za izpratenoto ot Vas pismo nai skoro shte vi otgovorq!! >=20 > Turn this off. Argh, it seems that this person sends the message from the list address. It's been going on for months, really, can't the subscribed address be unsubscribed? --QGBKWVSgmlsIyJ+t Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZ6NRSkf3jVXOdl0RAg/6AJ0XDpAqdEBqJ6CRefh+/RlxYcDhWgCeO7ko girTbZTjcspwPZaJQCovUw0= =HVwh -----END PGP SIGNATURE----- --QGBKWVSgmlsIyJ+t-- From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 15:15:45 2005 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 0DF0916A4CE for ; Thu, 21 Apr 2005 15:15:45 +0000 (GMT) Received: from grummit.biaix.org (86.Red-213-97-212.pooles.rima-tde.net [213.97.212.86]) by mx1.FreeBSD.org (Postfix) with SMTP id 63B4B43D1F for ; Thu, 21 Apr 2005 15:15:43 +0000 (GMT) (envelope-from lists-freebsd-hackers@biaix.org) Received: (qmail 88921 invoked by uid 1000); 21 Apr 2005 15:14:36 -0000 Date: Thu, 21 Apr 2005 17:14:36 +0200 From: Joan Picanyol i Puig To: freebsd-hackers@freebsd.org Message-ID: <20050421151436.GA86490@grummit.biaix.org> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20050420135013.GE91329@obiwan.tataz.chchile.org> <20050420143715.GF91329@obiwan.tataz.chchile.org> <20050420151104.GA11753@grummit.biaix.org> <20050420165559.GI91329@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050420165559.GI91329@obiwan.tataz.chchile.org> User-Agent: Mutt/1.5.6i Subject: Re: Configuration differences for jails 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, 21 Apr 2005 15:15:45 -0000 * Jeremie Le Hen [20050420 18:55]: [snip much appreciated example] > > I don't think it's easy to take /etc/ outside the root fs, but I don't > > see how to share /bin or /lib without leaking info. > > > > How do you handle this? > > As I said above, null mount each directory. Thanks, that was exactly what I was looking for. I hadn't read close enough to appreciate the difference betwen unionfs and nullfs until now. > > What are those distribution targets and how can > > I use them? I've seen them mentioned again in this thread. There apparently is a "make distribution" target designed to address /etc, but I can't find it anywhere. qvb -- pica From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 17:51:41 2005 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 4D5C616A4D0; Thu, 21 Apr 2005 17:51:41 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D217A43D31; Thu, 21 Apr 2005 17:51:39 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3LHrKwj095758; Thu, 21 Apr 2005 11:53:20 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4267E75E.3000600@samsco.org> Date: Thu, 21 Apr 2005 11:48:14 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Content-Type: text/plain; name="report-jan-2005-mar-2005.txt" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="report-jan-2005-mar-2005.txt" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: FreeBSD Status Report Jan-Mar 2005 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, 21 Apr 2005 17:51:41 -0000 January-April 2005 Status Report Introduction The first quarter of 2005 has been extremely active in both FreeBSD-CURRENT and -STABLE. With FreeBSD 5.4 in the final RC stage and an anticipated branch of FreeBSD-6 this summer we have seen a lot of performance improvements in 5 and a couple of exciting new features in 6. The report turnout was extremely good and it seems that the webform provided by Julian Elischer has made it more enjoyable to write reports. Many thanks to Julian for providing this. We also like to get your attention to the open tasks section provided in some reports. On special note, please take a look at the report about the upcoming BSDCan in Ottawa. There will be lots of interesting FreeBSD related talks and activities. If you enjoy reading these reports, you will love the conference. See you there! Thanks to all the reporters, we hope you enjoy reading. _________________________________________________________________ Projects * Common Address Redundancy Protocol - CARP * FreeBSD Java Project * FreeBSD Release Engineering * GELI - GEOM class for providers encryption * GSHSEC - GEOM class for handling shared secret * Secure Updating Documentation * FreeBSD Dutch Documentation Project Kernel * ATAPI/CAM * Coverity Code Analysis * cpufreq * drm * Filesystem journalling for UFS * Infrastructure Cleanup * Interrupt Latency * Low-overhead performance monitoring for FreeBSD * Many subdirs for UFS * Status Report for FreeBSD ATA driver project * Storage driver SMPng locking Network infrastructure * Dingo * IPv6 Support for IPFW * Move ARP out of routing table * netgraph(4) status report * Removable interface improvements. * Support for telephone hardware (aka Zaptel) * Wireless Networking Support Userland programs * libthread * Pipe namespace added to portalfs Architectures * ARM Support for TS-7200 * PowerPC Port * XenFreeBSD - FreeBSD on Xen Ports * FreshPorts * Ports Collection * Update of the Linux userland infrastructure Vendor / 3rd Party Software * OpenBSD packet filter - pf * twa driver Miscellaneous * BSDCan * FreeBSD Security Officer and Security Team * IMUNES - a FreeBSD based kernel-level network topology emulator _________________________________________________________________ ARM Support for TS-7200 URL: http://www.embeddedarm.com/epc/ts7200-spec-h.html URL: http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/jmg /arm&HIDEDEL=NO URL: http://people.freebsd.org/~jmg/dmesg.ts7200 Contact: John-Mark Gurney I have been working on getting FreeBSD/arm running on the TS-7200. So far the board boots, and has somewhat working ethernet (some unexplained packet loss). I can netboot from a FreeBSD/i386 machine, and I can also mount msdosfs's on CF. Open tasks: 1. Figuring out why some small packets transmit with error 2. EP93xx identification information to properly attach various onboard devices _________________________________________________________________ ATAPI/CAM Contact: Thomas Quinot ATAPI/CAM integration with the new ATA (mkIII) framework is now completed. ATAPI/CAM is now available as a loadable module (atapicam.ko). It is also independant from the native ATAPI drivers again, as was the case before mkIII. Thanks to Scott Long and S鴕en Schmidt for their participation in the integration work. _________________________________________________________________ BSDCan URL: http://www.bsdcan.org/ Contact: Dan Langille BSDCan made a strong debut in 2004 . The favorable reception gave us a strong incentive for 2005 . We have been rewarded with a very interesting program and a higher rate of registrations. Percentage-wise, we have more Europeans than last year as they have decided that the trip across the Atlantic is worth taking. We know they won't be disappointed. See you at BSDCan 2005! Open tasks: 1. volunteers needed for the conference _________________________________________________________________ Common Address Redundancy Protocol - CARP URL: http://www.freebsd.org/cgi/man.cgi?query=carp&manpath=FreeBSD+6.0-curr ent URL: http://people.freebsd.org/~mlaier/CARP/ Contact: Max Laier Contact: Gleb Smirnoff CARP is an alternative to VRRP. In contrast to VRRP it has full support for IPv6 and uses crypto to protect the advertisements. It was developed by OpenBSD due to concerns that the HSRP patent might cover VRRP and CISCO might defend its patent. CARP has, since then, improved a lot over VRRP. CARP has been committed to HEAD and MFCed to RELENG_5. It will be available in upcoming 5.4-RELEASE. Big thanks to all users who provided testing and reported bugs to Max and Gleb. Daniel Seuffert has donated hardware to Max for this project. Gleb's work was sponsored by Rambler . Open tasks: 1. Improve vlan(4) support. Test ng_eiface(4). 2. Improve locking, consider removing interface layer. _________________________________________________________________ Coverity Code Analysis URL: http://www.coverity.com/ Contact: Sam Leffler There has been an ongoing effort to review the kernel source code using Coverity's source code analysis tools (http://www.coverity.com). These tools check for a variety of problems such as null pointer dereference, use-after-free of allocated variables, invalid array references, etc. This work is a joint project between FreeBSD and Coverity. Two passes have been completed over the 6-current kernel source code base and all significant problems have been corrected. These runs were done in February and March of this year. A few reports of minor problems await response from outside groups and will be resolved in time for the first 6.x release. Another analysis run over the kernel will happen soon. We are looking for a way to use these tools on a regular basis as they have been helpful in improving the code base. Thanks to Coverity for their help and especially Ted Unangst. Several developers have been especially helpful in resolving reports: Poul-Henning Kamp, David Schultz, Pawel Jakub Dawidek, George V. Neville-Neil, and Matthew Dodd. _________________________________________________________________ cpufreq URL: http://www.freebsd.org/cgi/man.cgi?query=cpufreq&manpath=FreeBSD+6.0-c urrent&format=html Contact: Nate Lawson The cpufreq project was committed to 6-CURRENT in early February and has undergone bugfixes and updates. It will soon be MFCd to 5-STABLE. The cpufreq driver provides a unified kernel and user interface to CPU frequency control drivers. It combines multiple drivers offering different settings into a single interface of all possible levels. Users can access this interface directly via sysctl(8), by indicating to power_profile that it should switch settings when the AC line state changes, or by using powerd(8). For example, an absolute driver offering frequencies of 1000 Mhz and 750 Mhz combined with a relative driver offering settings of 100% and 50% would result in cpufreq providing levels of 1000, 750, 500, and 375 Mhz. Colin Percival helped with powerd(8), which provides automatic control of CPU frequencies. The adaptive mode is especially interesting since it attempts to respond to changes in system load while reducing power consumption. Current hardware drivers include acpi_perf (ACPI CPU performance states), est (Intel Enhanced SpeedStep for Pentium-M), ichss (Intel's original SpeedStep for ICH), and powernow (AMD Powernow! K7 and K8 support). Other drivers for relative hardware include acpi_throttle (ACPI CPU throttling) and p4tcc (Pentium 4 Thermal Control Circuitry) Thanks to Bruno Ducrot for the powernow driver, Colin Percival for the est driver, and the many testers who have sent in feedback. Open tasks: 1. We'd appreciate someone with a Transmeta CPU converting the existing longrun driver to the cpufreq framework. It would also be good if someone wrote a VIA Longhaul driver. See the Linux arch/i386/kernel/cpu/cpufreq directory for examples. 2. Various other architectures, including ARM, have CPU power control that could be implemented as a cpufreq driver. 3. The powerd(8) algorithm is rather simple and we'd appreciate more help in testing it and alternative algorithms with various workloads. The -v flag causes powerd to report frequency transitions and print a summary of total energy used upon termination. This should help testers profile their algorithms. _________________________________________________________________ Dingo URL: http://people.freebsd.org/~gnn/Dingo/notebook/60.html URL: http://zoo.unixdaemons.com/index.php?blog=7 Contact: George Neville-Neil On the protocol conformance tool I have finally made some progress getting a scriptable packet library using libnet, and SWIG. This will hopefully become a port that can then be used to do conformance testing on protocol stack changes. Qing Li has separately taken up the ARP rewrite and that will be taken out of the Dingo project pages. Open tasks: 1. Many :-) _________________________________________________________________ drm URL: http://r300.sourceforge.net/ Contact: Eric Anholt A DRM update was finally committed to -current on 2005-04-15, after jhb@ did the necessary fix to vm_mmap. New development drivers were added for mach64 and r300 (see URL for info). The nearly-finished code for savage and i915 were also added, but left disconnected from the build. However, the most visible change is likely the support for texture tiling, color tiling, and HyperZ on Radeons, which (with updated userland) likely provide a 50-75% framerate increase in many applications. Open tasks: 1. Find someone with newbus knowledge to figure out why the i915 won't attach to drmsub0. 2. Finish porting the savage driver. 3. Integrate busdma code from Tonnerre (NetBSD). _________________________________________________________________ Filesystem journalling for UFS URL: http://repoman.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/scot tl/ufsj Contact: Scott Long It's time to bite the bullet and admit that fsck is no longer scalable for modern storage capacities. While a healthy debate can still be had on the merits and data integrity guarantees of journalling vs. SoftUpdates, the fact that SoftUpdates still requires a fsck to ensure consistency of the filesystem metadata after an unclean shutdown means uptime is lost. While background fsck is available, it saps system performance and stretched the fsck time out to hours. Journalling provides a way to record transactions that might not have fully been written to disk before the system crashed, and then quickly recover the system back to a consistent state by replaying these transactions. It doesn't guarantee that no data will be lost, but it does guarantee that the filesystem will be back to a consistent state after the replay is performed. This contrasts to SoftUpdates that re-arranges metadata updates so that inconsistencies are minimized and easy to recover from, though recovery still requires the traditional full filesystem scan. Journalling is a key feature of many modern filesystems like NTFS, XFS, JFS, ReiserFS, and Ext3, so the ground is well covered and the risks for UFS/FFS are low. I'm aware that groups from CMU and RPI have attempted similar work in the past, but unfortunately the work is either very outdates, or I haven't had any luck in contacting the groups. Is this absence, I've decided to work on this project myself in hopes of having a functional prototype in time for FreeBSD 6.0. The approach is simple and journals full metadata blocks instead of just deltas or high-level operations. This greatly simplifies the replay code at the cost of requiring more disk space for the journal and more work within the filesystem to identify discreet update points. An important design consideration is whether to make the journal data and code compatible with the UFS2 filesystem, or to start a new UFS3 derivative. Since the latter presents a very high barrier to adoption for most people, I'm going to try to make it a compatible option for UFS2. This means that the journal blocks will likely appear as an unlinked file to legacy filesystem and fsck code, and will be treated as such. This will allow seamless fallback to using fsck, though once the unlinked journal data blocks are reclaimed by fsck, the user will have to take action to re-create the journal file again. One key piece of journalling is ensuring that each journal transaction is fully written to disk before the associated metadata blocks are written to the filesystem. I plan to adopt the buffer 'pinning' mechanism from Alexander Kabaev's XFS work to assist with this. This will allow the journalling subsystem fine-grained control over which blocks get flushed to disk by the buffer daemon without having to further complicate the UFS/FFS code. One consideration is how Softupdates falls into this and whether it is multually exclusive of journalling or if it can help provide transaction ordering functionality to the journal. Research here is on-going. Some preliminary work can be found in Perforce in the //depot/user/scottl/ufsj/... tree or at the URL provided. Hopefully this will quickly accelerate. _________________________________________________________________ FreeBSD Dutch Documentation Project URL: http://www.freebsd.org/doc/nl/books/handbook URL: http://www.evilcoder.org/freebsd_html/ URL: http://www.evilcoder.org/content/section/6/39/ Contact: Remko Lodder The FreeBSD Dutch Documentation Project is a ongoing project in translating the English documentation to the Dutch language. Currently we have translated almost the entire handbook, and more to come. If you want to help out by review the Dutch documents, or you want to help translating the remainders of the handbook or other documents, feel free to contact me at remko@FreeBSD.org Open tasks: 1. Translate the English handbook, then review the Dutch handbook 2. Translate the English FAQ, then review the Dutch FAQ 3. Translate the English Articles, then review the Dutch Articles _________________________________________________________________ FreeBSD Java Project URL: http://www.FreeBSD.org/java/ Contact: Greg Lewis Contact: Alexey Zelkin The FreeBSD Java Project released its initial support for JDK 1.5.0 with patch set 1 "Sabretooth" in January. The initial release featured support for both FreeBSD 5.3/i386 and 5.3/amd64. Since then preliminary support for FreeBSD 4.11/i386 has been added and several bug fixes have been made. Updates in the coming months will add support for the browser plug in and Java Web Start, which were not in the initial release. Open tasks: 1. Volunteers to look into some serious problems with JDK 1.5.0 on FreeBSD 4.x _________________________________________________________________ FreeBSD Release Engineering URL: http://www.freebsd.org/releng Contact: RE Team FreeBSD 4.11, the final formal release of the 4.x series, was released on 25 Jan 2005. Many thanks to the all of the developers and users over the past 5 years who made it successful. While no more releases are planned, the security team will continue to support it through security update patches until 2007. Developers are also free to commit bug fixes and low-risk features to the RELENG_4 branch for the foreseeable future. FreeBSD 5.4 is going through its final release candidate stages and is expected to be released in late April. Its focus is mostly bug fixes and minor feature and performance improvements, so it is an excellent target for those looking to upgrade from previous versions or to give FreeBSD a try for the first time. FreeBSD 5.5 will be release in about 4-6 months after 5.4. FreeBSD 6.0 is rapidly approaching also. In contrast to FreeBSD 5.0, the goal is to take a more incremental approach to major changes, and not wait for years to get as many features in as possible. FreeBSD 6.0 will largely be an evolutionary change from the 5.x series, with the largest changes centered around multi-threading and streamlining the filesystem and device layers. Feature freeze and code freeze for 6.0 are coming up in May and June, and we hope to have 6.0 stable and ready for release in July or August. The release engineering team has also started doing monthy informal snapshots of the 6-CURRENT and 5-STABLE trees. These are intended to increase the exposure of new features and get more users involved in testing and providing feedback. Snapshots can be found at http://www.freebsd.org/snapshots. _________________________________________________________________ FreeBSD Security Officer and Security Team URL: http://www.freebsd.org/security/ URL: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff -listing.html#STAFF-SECTEAM URL: http://vuxml.freebsd.org/ Contact: Security Officer Contact: Security Team In January 2005, Warner Losh (Security Officer Emeritus) stepped down from the FreeBSD Security Team in order to better devote his time to other projects. In March, Colin Percival was named as a second Deputy Security Officer, joining Dag-Erling Sm鴕grav in that position. The current Security Team membership is published on the web site. So far in 2005, four security advisories have been issued concerning problems in the base system of FreeBSD, three of which were specific to FreeBSD. The Vulnerabilities and Exposures Markup Language (VuXML) document has continued to be updated by the Security Team and the Ports Committers documenting new vulnerabilities in the FreeBSD Ports Collection. As of April 17, 127 entries have been added in 2005 bringing the FreeBSD VuXML file up to a total of 422 entries. In the past months both the VuXML web site and the FreshPorts VuXML integration have been improved. The VuXML web site has had a face lift and, among other things, each package now has a separate web page which lists all documented vulnerabilities for the particular package. CVE information is now also included directly on the VuXML web site. Finally, the first few months of 2005 also saw FreeBSD 4.8 -- the first release to be offered "extended support" -- reach its designated End of Life. The currently supported releases are FreeBSD 4.10, 4.11, and 5.3. _________________________________________________________________ FreshPorts URL: http://www.freshports.org/ Contact: Dan Langille This is the first status report for FreshPorts. FreshPorts started in early 2000 and now contains over 170,000 commits. FreshPorts is primarily concerned with port commits, but actually processes and records all commits to the FreeBSD source tree. Its sister site, FreshSource uses the same database as FreshPorts but has a wider reporting scope. In recent months, FreshPorts has been enhanced to process and include VuXML information. In addition, RESTRICTED and NO_CDROM have been added to list of things that FreshPorts keeps track of. For unmantained ports, we recently added this message: There is no maintainer for this port. Any concerns regarding this port should be directed to the FreeBSD Ports mailing list via ports@FreeBSD.org FreshPorts, with direct and indirect support from the FreeBSD community, continues to evolve and to provide a great tool for users and developers alike. Open tasks: 1. Provide a copy/paste method for updating watch lists 2. improvement of query times for "People watching this port, also watch" 3. pagination of commits within a port 4. pagination of watch lists 5. create an RSS feed for individual watch lists _________________________________________________________________ GELI - GEOM class for providers encryption URL: http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd /geom%5fclasses/sys/geom/eli&HIDEDEL=NO URL: http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd /geom%5fclasses/sbin/geom/class/eli&HIDEDEL=NO Contact: Pawel Jakub Dawidek GELI is a GEOM class used for GEOM providers encryption. I decided to work on this, as I needed some feature, which cannot be found in similar projects. Here is the list of features, I found interesting: * makes use of crypto(9) * if there is a crypto hardware available, GELI will run cryptography on it automatically; if not, it starts dedicated kernel thread and do crypto software work in there * supports many cryptographic algorithms (AES, Blowfish, 3DES) * is able to take key components from many sources at once (user entered passphrase, random bits from a file, etc.) * allows to encrypt root partition * user will be asked for the passphrase before root file system is mounted * uses "PKCS #5: Password-Based Cryptography Specification Version 2.0" for user passphrase protection (optional) * allows to use two independent keys (e.g. "user key" and "company key") * is fast * GELI does simple sector-to-sector encryption * allows to backup/restore Master Keys, so when user have to quickly destroy keys, it is able to get the data back by restoring keys from the backup * provider can be configured at attach time to automatically detach on last close (so user don't have to remember to detach after unmounting file system) * allows to attach provider with a random, one-time keys * useful for swap partitions and temporary file systems Open tasks: 1. Code audit/review is more than welcome! _________________________________________________________________ GSHSEC - GEOM class for handling shared secret URL: http://www.freebsd.org/cgi/man.cgi?query=gshsec&apropos=0&sektion=0&ma npath=FreeBSD+6.0-current&format=html Contact: Pawel Jakub Dawidek GSHSEC is a GEOM class used for handling shared secret data between multiple GEOM providers. For every write request, SHSEC class splits the data using XOR operation with random data, so N-1 providers gets just random data and one provider gets the data XORed with the random data from the other providers. All of the configured providers must be present in order to reveal the secret. The class is already committed to HEAD and RELENG_5 branches. _________________________________________________________________ if_bridge from NetBSD URL: http://www.fud.org.nz/~andy/if_bridge.diff Contact: Andrew Thompson This project aims to import the bridging code and interface from NetBSD and OpenBSD. The bridge is a cloned interface which can be modified by ifconfig and brconfig. It supports assigning an IP address directly to the bridge (e.g. bridge0) instead of one of the member interfaces, and can be used with tcpdump to inspect the bridged packets. The code also supports spanning tree (802.1D) for loop detection and link redundancy. Any pfil(9) packet filter can be used to filter the bridged packets. Open tasks: 1. Testing performance and functionality against the existing bridge code. Testers welcome! _________________________________________________________________ IMUNES - a FreeBSD based kernel-level network topology emulator URL: http://www.imunes.net/ Contact: Miljenko Mikuc Contact: Marko Zec IMUNES is a scalable kernel-level network topology emulator based on FreeBSD. In IMUNES each virtual node operates on its private instance of network stack state variables, such as routing tables, interface addresses, sockets, ipfw rules etc. Most if not all existing FreeBSD application binaries, including routing protocol daemons such as quagga or XORP, can run unmodified within the context of virtual nodes with no noticeable performance penalty. Complex network topologies can be constructed by connecting the virtual nodes through netgraph-based link-layer paths. A GUI tool allows for simple and intuitive network topology specification, deployment and management. The current version of IMUNES is based on FreeBSD 4.11-RELEASE and supports IPv4. _________________________________________________________________ Infrastructure Cleanup Contact: Warner Losh Contact: Takahashi Yoshihiro Unglamorous cleanup of the code base continues. The focus of recent efforts have been to reduce the number of machine #ifdefs that are in the machine independent code. In addition, we're also trying to increase code sharing between pc98 and i386 ports and reduce the number of #ifdef PC98 instances in the tree. In addition, a number of cleanup tasks are underway for different parts of the kernel that are more complicated than necessary. Recently, the pccard code's allocation routines were simplified to reassign ownership of resources more directly than before. The search is on for other areas that can benefit from cleanup. Open tasks: 1. On pc98, there's no such thing as an ISA bus. It is desirable to move to having cbus appear in the probe messages. This would also allow for additional segregation of pc98 specific code in the drivers and eliminate many ifdefs. Ideally, isa and cbus would share a common newbus ancestor class so their similarities can be exploited (they both have PNPBIOS enumeration methods, for example). 2. cbus devices can have complicated resources. There's support for vectors of resources. Yet there's no support for populating a vector of resources from the plug and play information. Doing so would help the complex world of pc98 a lot, and the odd edge cases in i386 (floppy, ata) a little. 3. The hints mechanism provides a way to associate hardware with drivers and resource that would otherwise be completely unknown to the system. A refinement in the hints mechanism to allow matching of driver instances to resources is desirable. This would allow one to hardwire sio0 to 0x2f8, even when the serial device in the plug and play resource list (or acpi resource list) is listed second. A further refinement could also be wiring sio0 to "port B" as defined by acpi or some other enumeration method. Chances are good that these seemingly related concepts may need separate implementations due to the decision points for unit assignment. 4. Pccard, cardbus and usb probe their devices after interrupts are enabled. It would be desirable to hook into new kernel APIs to allow the mounting of root to be put off until those systems know that they are done with their initial probe of the devices present at boot. _________________________________________________________________ Interrupt Latency Contact: Warner Losh I've setup a test system to measure interrupt latency on FreeBSD 5.3 and current. So far I've measured the baseline latency for a 300MHz embedded cyrix based single board computer. I've tried a number of different strategies to optimize the interrupt path. Most of these strategies resulted in some improvement of the time it takes to get from the start of the interrupt servicing to the driver's ISR. These improvements turned out to be about 1-2% of the processing times on this single board computer, but a wash on faster machines. However, the time between when the interrupt should happen, and when FreeBSD starts to service the interrupt is the dominant factor in these measurements. Despite the fact that these are fast interrupt handlers (so the scheduler is out of the loop), I routinely see average latencies of 18us, with large variations (on the order of 5us standard deviation). Open tasks: 1. I need to measure the latencies with 4.x and current to characterize the differences more precisely. I'm especially interested in the effects on interrupt latency that the elimination of mixed mode will cause. 2. I need to characterize different parts of our ISR routines to see if some of the variation I've seen so far can be reduced by improved coding techniques. 3. I need to re-run my tests with 5.4 and summarize my results in a paper. _________________________________________________________________ IPv6 Support for IPFW URL: http://lists.freebsd.org/pipermail/cvs-all/2005-April/116671.html Contact: Brooks Davis In April 18th, I committed support for IPv6 to IPFW. This support was written by two student of Luigi's, Mariano Tortoriello and Raffaele De Lorenzo. I updated it to use PFIL_HOOKS and fixed a few minor issues. As of this commit, IP6FW should be considered deprecated in favor of IPFW. It should be possible to MFC this change to 5.x, but that is not currently planned. Open tasks: 1. Testing. 2. IP6FW to IPFW migration guide. 3. Patches relative to 5-STABLE. _________________________________________________________________ libthread Contact: David Xu libthread is a pure 1:1 threading library, it had stayed in my perforce branch for a long time, recent it was imported into source tree and replaced libthr. The purpose of the work is to improve 1:1 threading on FreeBSD, the library is designed in mind that simplest is best, currently it can run almost all of the applications libpthread can run, but gives you better SMP performance. The library size is smaller than libpthread. Currently it supports i386, AMD64, sparc64 and ia64 and may support alpha, powerpc and arm. I didn't do many tests on sparc64 and ia64, I only tested it on FreeBSD cluster machines. For i386, I always used LDT, but know that Peter committed GDT code, and now there is no 8191 threads limitation anymore. libthread_db was updated to support debugging the new libthr. It is an assistant library used by gdb to debug threaded process, that understands internal detail of thread libraries. I have improved it a bit to support event reports for libthr, currently it can report thread creation and death events. That means a thread that was created and died will be reported to the user regardless if you are tracking it or not. Open tasks: 1. I am working on thread creation performance, currently it needs considerable number of libc functions and syscalls to create a thread, I would like to introduce a syscall to create a thread in atomicaly. That means one syscall will setup thread entry, tls, and signal mask and PTHREAD_SCOPE_PROCESS/SYSTEM; in future maybe even CPU affinity masks, when userland entry code is executed, the thread is already fully setup. 2. Process shareable synchronization objects. In Current FreeBSD does not support this specification. The idea about the shareable mutex and others is like other systems did, one can use mmap() to create a shared memory page, and put a pthread synchronization object in the page, multiple processes use the shared object to control resource access. I am not working on it, if someone is interested, please let me know. _________________________________________________________________ Low-overhead performance monitoring for FreeBSD URL: http://people.freebsd.org/~jkoshy/projects/perf-measurement Contact: Joseph Koshy Many modern CPUs have on-chip performance monitoring counters (PMCs) that can be used to count low-level hardware events like instruction retirals, branch mispredictions, cache and TLB misses and the like. PMC architectures and capabilities vary between CPU vendors and between CPU generations from the same vendor, making the creation of portable applications difficult. This project attempts to provide a uniform API for applications to use, and the necessary infrastructure to "virtualize" and manage the available PMC hardware resources. The creation of performance analysis tools that use this infrastructure is also part of the project's goals. Work since the last status report: * Support for Intel Pentium-Pro/Pentium-II/Pentium-III/Pentium-M/Celeron style PMCs has been added. * The Pentium-4/HTT machine dependent layer has been overhauled. * A Python language interface to the C library interface pmc(3) has been written. * Many bugs have been fixed and documentation has been updated. Open tasks: 1. The code needs to be tested on Intel Pentium-M, Celeron, Pentium II and Pentium Pro CPUs. _________________________________________________________________ Many subdirs for UFS URL: http://groups-beta.google.com/group/muc.lists.freebsd.fs/browse_frm/th read/a36d1143d695287e/40cad00cf2c0823b?hl=en#40cad00cf2c0823b Contact: David Malone I'm currently looking at the limit on the number of subdirectories a directory can have in UFS. There is currently a limit of 32K subdirectories because of the 16 bit link count field in both struct stat and the on-disk inode format. The thread above shows that dirhash provides acceptable performance for directories with 100k subdirectories using a prototype patch. Two options for allowing many subdirectories seem to exist: changing the link counting scheme for directories and expanding the link count field. The prototype patch implements the first scheme and there are plans to investigate the second scheme (which may require an ABI change). _________________________________________________________________ Move ARP out of routing table URL: http://people.freebsd.org/~qingli/ Contact: Qing Li I have finished the basic functionality for both IPv4 and IPv6. The userland utilities ("arp" and "ndp") have been updated. I have tested the changes with "make buildworld". I have been testing the new code in a production environment and things appear to be stable. Gleb Smirnoff (glebius@FreeBSD.org) has provided review comments and I have incorported these feedback into the patch. I have discussed the IPv6 changes with two of the core KAME developers during the last IETF meeting in March 2005. They indicated that these changes may result in divergence from the KAME project but that is not necessarily a bad thing. Open tasks: 1. I am waiting for review feedback from my mentor Andre. I need locking experts to help me fix my giant-lock shortcut. I am hoping to send out the code for wider review soon. _________________________________________________________________ netgraph(4) status report URL: http://www.freebsd.org/cgi/man.cgi?query=ng_netflow&manpath=FreeBSD+6. 0-current URL: http://www.freebsd.org/cgi/man.cgi?query=ng_ipfw&manpath=FreeBSD+6.0-c urrent URL: http://people.freebsd.org/~glebius/totest/ng_nat/ Contact: Gleb Smirnoff This report covers period since August 2004 until April 2005. New nodes. Two new nodes have been added to base FreeBSD distribution. ng_netflow(4) node, which implements NetFlow version 5 accounting of IPv4 packets. ng_ipfw(4) node, which diverts packets from ipfw(4) to netgraph(4) and back. A well known ng_ipacct node has been added to ports tree. SMP. Nodes, which need to allocate unique names have been protected with mutex in RELENG_5, and subr_unit allocator in HEAD. Nodes, which need to run periodical jobs were reworked to use mpsafe ng_callout() API. ng_tty(4) node has been overhauled to be compatible with debug.mpsafenet=1. NetGraph ISR and callout are now declared MPSAFE in HEAD. NetGraph flow control. Two nodes ng_ether(4) and ng_cisco(4) have been improved to emit flow control messages to upstream node, when state of link changes. New link failure detection method have been introduced in ng_one2many(4) node - listening to these flow control messages from downstream. Open tasks: 1. more SMP testing of many nodes 2. review locking of graph restructuring 3. ng_nat node - an in-kernel natd(8) 4. make ng_bridge(4) multithreaded _________________________________________________________________ OpenBSD packet filter - pf URL: http://pf4freebsd.love2party.net/ URL: http://people.freebsd.org/pf37/ Contact: Max Laier OpenBSD is about to release version 3.7 . There are patches available to catch up with the development done in OpenBSD 3.6 and 3.7. These patches are in an early stage, but ready for testing, please help. Otherwise there was not much activity on pf, as it already is quite stable. Other work, such as CARP and if_bridge are having impact on pf in FreeBSD however, please see the respective reports. Open tasks: 1. Alpha/Betatesting of the 3.7 import 2. Testing with if_bridge _________________________________________________________________ Pipe namespace added to portalfs URL: http://www.spinellis.gr/blog/20050413/index.html Contact: Diomidis Spinellis A new sub-namespace, called pipe, has been added to portalfs. The pipe namespace executes the named command, starting back at the root directory. The command's arguments can be provided after the command's name, by separating them with spaces or tabs. Files opened for reading in the pipe namespace will receive their input from the command's standard output; files opened for writing will send the data of write operations to the command's standard input. The pipe namespace allows us to perform scatter gather operations without using temporary files, create non-linear pipelines, and implement file views using symbolic links. _________________________________________________________________ Ports Collection URL: http://www.freebsd.org/ports/ URL: http://portsmon.firepipe.net/index.html URL: http://www.freebsd.org/portmgr/index.html Contact: Mark Linimon As this report was being written, the 5.4 release was ongoing. A new charter for the Ports Management (portmgr) team was approved by core and has been posted at the URL above. In addition, two other new pages describe the policies of the team, and the range of QA activities both during and between releases. Due to being absent from email discussions for some time, Oliver Eikemeier (eik) was moved to non-voting status on portmgr. We have added several new and very active committers recently; this is helping us to keep the PR count low even with the large numbers of new ports that have been added. Several more iterations of infrastructure changes have been tested on the cluster and committed; see /usr/ports/CHANGES for details. Updates have occurred to x.org, GNOME, KDE, and perl. There have been some updates to the Porter's Handbook, but more sections are still in need of updates to include recent changes in practices. The ports collection now contains almost 12,750 ports. Open tasks: 1. Further progress has been made in cracking down on ports that install files outside the approved directories and/or do not deinstall cleanly (see "Extra files not listed in PLIST" on pointyhat ) and this will remain a focus area. We appreciate everyone who has sent in PRs or committed fixes. 2. Demand for new features and revisions for bsd.port.mk is still very high and the portmgr team is trying to work through them all. 3. We still have a large number of PRs that have been assigned to committers for some time (in fact, they constitute the majority). One goal of portmgr in the coming months is to try to reduce this number, and we would like to ask our committers to help us out as much as possible. _________________________________________________________________ PowerPC Port Contact: Peter Grehan Progress continues. X.Org 6.8.1 server has been up and running on a number of different Macs, and the work is being merged into 6.8.2. There have been successful installs on Mac Minis _________________________________________________________________ Removable interface improvements. URL: http://people.freebsd.org/~brooks/pubs/eurobsdcon2004/ URL: http://www.freebsd.org/projects/dingo/ Contact: Brooks Davis This project is an attempt to clean up handling of network interfaces in order to allow interfaces to be removed reliably. Current problems include panics if Dummynet is delaying packets to an interface when it is removed. I am currently working to remove struct ifnet's from device driver structures to allow them to be managed properly upon device removal. I believe I have removed all known instances of casting a struct ifnet pointer to something else (except that that are just magic values and not real struct ifnets.) I will begin committing these changes to the tree shortly and will then add a new function if_alloc() that will allocate struct ifnets. if_detach() will be modified to destroy them. _________________________________________________________________ Secure Updating URL: http://www.daemonology.net/portsnap/ URL: http://www.daemonology.net/freebsd-update/ Contact: Colin Percival Shortly before the ports freeze for FreeBSD 5.4, I released a new version of Portsnap. In addition to being secure and more efficient than CVSup, this latest version distributes INDEX, INDEX-5, and INDEX-6 files, thereby eliminating the need to run "make fetchindex" and ensuring that the ports INDEX will match the existing ports tree. In addition, portsnap builds have now moved onto hardware managed by the FreeBSD project, thereby sharply increasing portsnap's chances of survival if I get hit by a bus. In early February hardware problems caused both FreeBSD Update and Portsnap to stop functioning for a few days, but those were resolved thanks to a server donated by layeredtech.com. I intend bring Portsnap into the FreeBSD base system before the end of the month, followed by FreeBSD Update a few months later. _________________________________________________________________ Status Report for FreeBSD ATA driver project Contact: S鴕en Schmidt ATA mkIII has been committed to -current after a couple of month testing as patches post on -current and 5-stable. I will continue to provide patches for 5-stable for those that need up-to-date ATA support there. Here a short rehash of what mkIII brings: ATA is now fully modular so each part can be loaded/unloaded at will to provided the wanted functionality. Much improved SATA support that support hotplug events on controllers that support it (Promise, SiS, nVidia so far) ie the system will automagically detect when SATA devices come and go and add/delete device entries etc. Much improved ATA RAID support. The ata-raid driver has been largely rewritten to take advantage of the features the improved infrastructure provides, including composite ATA operations etc. The rebuild functionality has been changed to rebuild on userland reads, so a simple dd of the entire array will get it rebuild (what atacontrol now does). This means that the resources used for this can be better tailored to the actualy usage pattern if needed. ATA RAID now supports 10+ different RAID metadata formats, so most BIOS defined ATA RAID arrays can be picked up and used. The number of metadata formats that can be created from within FreeBSD is still limitted though and is not a high priority feature right now. The lowlevel infrastructure of the ATA driver has been refined even further to support "strange" chipsets much more easily and in most case transparent to the higher levels. This to easy ports to new platforms where ATA controllers doesn't necessarily have the x86 legacy layout. Lots of bug fixes and corrections all over the driver proper. The rework of the infrastructure has revealed bugs and deficiencies that has been fixed in the process of modulerising ATA and making the infrastructure more generic, and hopefully easier to understand. The work continues to keep ATA on top of new chipsets and other advancements in the ATA camp. SATA ATAPI support is in the works and so are support for NCA/TCQ (tags). Donations of unsupported hardware is the way to get it supported as I'm way out of my budget for new hardware for the next decade or so according to my wife :) Open tasks: 1. Lots of testing wanted, especially SATA and RAID support _________________________________________________________________ Storage driver SMPng locking Contact: Scott Long Several storage drivers have been taken out from under the Giant mutex in the past few months. Thanks to sponsorship from FreeBSD Systems, Inc and ImproWare, AG, Switzerland , the LSI MegaRAID (AMR) and IBM/Adaptec ServeRAID (IPS) drivers have been locked. SMPng locking is a key step in improving the performance of system drivers in FreeBSD 5.x and beyond, and both of these drivers are showing the benefits of this. FreeBSD 5.4 will contains these improvements when it is released. Similar work is ongoing with the 3WARE Escalade (TWE) driver, and preliminary patches have been made available to testers. I hope to have this driver complete in time for the next FreeBSD release. Unfortunately, most benefits can only be gained from pure block storage drivers such as the ones mentioned here due to the SCSI subsystem in FreeBSD (CAM) not be locked itself at this time. It is possible, however, to lock a CAM sub-driver and bring the driver's interrupt handler out from under Giant for a partial gain. The Sun FAS366 SCSI driver (ESP) operates like this. Volunteers to lock other drivers or to tackle locking CAM are gladly accepted, so please contact me if you are interested. _________________________________________________________________ Support for telephone hardware (aka Zaptel) URL: http://www.digium.com/index.php?menu=hardware_products Contact: Maxim Sobolev Contact: Oleksandr Tymoshenko Contact: Max Khon During the last 2 months lot of progress has been made. Existing support for TDM400 (FXO/FXS) has been significantly improved. Drivers for PRI and BRI cards have been added and now should be considered beta-quality. Open tasks: 1. More testing of PRI/BRI drivers. 2. Add support for channelized DS3 card(s). _________________________________________________________________ twa driver URL: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/twa/ URL: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/modules/twa/ Contact: Vinod Kashyap A newly re-architected twa(4) driver was committed to 6 -CURRENT on 04/12/2005. Highlights of this release are: 1. The driver has been re-architected to use a "Common Layer" (all tw_cl* files), which is a consolidation of all OS-independent parts of the driver. The FreeBSD OS specific portions of the driver go into an "OS Layer" (all tw_osl* files). This re-architecture is to achieve better maintainability, consistency of behavior across OS's, and better portability to new OS's (drivers for new OS's can be written by just adding an OS Layer that's specific to the OS, by complying to a "Common Layer Programming Interface (CLPI)" API. If there's interest in porting the 3ware driver to any other OS, you may contact ctchu at amcc.com to get a copy of the CLPI specifications. 2. The driver takes advantage of multiple processors. It does not need to be Giant protected anymore. 3. The driver has a new firmware image bundled, the new features of which include Online Capacity Expansion and multi-lun support, among others. More details about 3ware's 9.2 release can be found here: http://www.3ware.com/download/Escalade9000Series/9.2/9.2_Release_N otes_Web.pdf _________________________________________________________________ Update of the Linux userland infrastructure Contact: Alexander Leidinger Contact: Emulation Mailinglist The update to RedHat 8 as discussed in the last status report went smoothly (just some minor glitches which got resolved fast). As a next step a cleanup/streamlining and the possibility of overriding the default linux base is in progress. This depends on changes which need at least one testrun on the ports build cluster, so the final date for those changes depends upon the availability of the cluster resources. Open tasks: 1. Refactoring the common RPM code into bsd.rpm.mk. 2. Determining which up-to-date Linux distribution to use as the next default linux base. Important criteria: + RPM based (to be able to use the existing infrastructure) + good track record regarding availability of security fixes + packages available from several mirror sites + available for several hardware architectures (e.g. i386, amd64, sparc64; Note: not all architectures have a working linuxolator for their native bit with, but as long as there are no userland bits available, no motivation regarding writting the kernel bits will arise) 3. Moving the linuxolator userland to an up-to-date version (see above). _________________________________________________________________ Wireless Networking Support Contact: Sam Leffler Several new drivers by by Damien Bergamini were brought into the tree: iwi, ipw, ral, and ural. WPA-PSK support for the ndis driver was contributed by Arvind Srinivasa. A new tx rate control algorithm for the ath driver was contributed by John Bicket. It will become the default algorithm shortly. Work on multi-bss support is going on outside the cvs tree. A presentation on this work will be given at BSDCan 2005 and the slides for the talk will be made available after. Open tasks: 1. Drivers other than ath and ndis need updates to support the new security protocols. 2. hostapd needs work to support the IAPP and 802.11i preauthentication protocols (these are simple conversions of existing Linux code). 3. The openbsd dhclient program has been ported but needs a developer that will maintain it once it is brought into cvs. _________________________________________________________________ XenFreeBSD - FreeBSD on Xen URL: http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ URL: http://xen.bkbits.net/ Contact: Kip Macy FreeBSD 5.3 runs on the stable and the development branches of xen and is now checked into both trees. Over the next couple of weeks I will be adding improvements for better batching of page table updates and SMP support. Open tasks: 1. FreeBSD support for running as Domain 0, i.e. running as the hosting operating system. 2. FreeBSD support for VM checkpoint and migration. _________________________________________________________________ From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 18:21:59 2005 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 90B9616A4CE for ; Thu, 21 Apr 2005 18:21:59 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37C5C43D45 for ; Thu, 21 Apr 2005 18:21:59 +0000 (GMT) (envelope-from opensource.enthousiat@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so730174nzo for ; Thu, 21 Apr 2005 11:21:58 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pSa/Gb1yzoO1kBLNurMFe9BCHbu8UEdpLghDm+omVv9/HcLqMsRHEBpPdChypYdpT3fA4q0gN6Tys+jp/VgCwOwSyzmcr0LEjJtt2bgT5+xFhxURFmHT9qN0m0Nf+igh2aqLIRevjYh23lHndgrz9tj3ii0tlLEgvFfaYL8QdXM= Received: by 10.36.41.20 with SMTP id o20mr212174nzo; Thu, 21 Apr 2005 11:21:58 -0700 (PDT) Received: by 10.36.109.8 with HTTP; Thu, 21 Apr 2005 11:21:58 -0700 (PDT) Message-ID: <37e1316605042111215c201be9@mail.gmail.com> Date: Thu, 21 Apr 2005 14:21:58 -0400 From: Aziz KEZZOU To: Chuck Robey In-Reply-To: <42670F63.4000901@chuckr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <37e1316605042019072b5d7a0e@mail.gmail.com> <5bbfe7d4050420191316a629b7@mail.gmail.com> <42670F63.4000901@chuckr.org> cc: David Leimbach cc: hackers@freebsd.org Subject: Re: KLD module with C++ iostreams ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Aziz KEZZOU List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 18:21:59 -0000 > David Leimbach wrote: > > Interesting question. People usually have to implement the C++ > > runtime to be usable from within the kernel. Things like exceptions > > and "stdout" may not be defined in kernel space :) > > > > I'm not terribly familiar with how it works on FreeBSD but I know it > > took a special effort to get C++ support into linux. > > > > Dave > > > > On 4/20/05, Aziz KEZZOU wrote: > > > >>Hi hackers, > >>I am wondering if I can use c++ iostreams inside the kernel ? > >>After all the code : cout << "Hello world!" << endl; > >>ends accessing the stdout just like : printf("Hello world!\n"); right ? >=20 > No, that's not true, all the iostreams stuff is totally independent. > The iostreams stuff is coming from some of the ugliest code in C++. > But, that's not the question, or at very least, it shouldn't BE the > question. There is ZERO need to bring in features from C++, all it will > do is to directly confuse the code base by greatly adding to the > complexity of the code, without giving anything like equivalent features. >=20 > Some very, very elegant work has been code, OO-ing the kernel code, > adding OO features, all without violating the C language code base. > Adding in C++ features over stdio stuff is so senseless, it's nearly > obscene. >=20 > If the gain at the end of the road was large enough, I wouldn't be > against it so stridently, but I see *so* little gain. >=20 > BTW, you know where the ugliest code in computer science today is: half > is in the actual implementation of the cstdio/template code, the other > half is the iostreams stuff. The fact that they energize some very > elegant code is causing many folks never to see the fact of the horrible > code lumps that exist out in the backyard. >=20 > >> > >>So if I could compile my KLD module with static linkage to libstdc++, > >>that should be ok, right ? > >> > >>Any one did or knows how to do this ? > >> Thank you guys for responding to my post. Certainly, it is not a good idea to use _all_ C++ stuff inside the kernel ; in the linux community a similar suggestion resulted in a big discussion of pros & cons. I was asking because I have a big portion of C++ code that I am planning to move inside the kernel. But, having compared the effort/time required to port C++ iostreams into the kernel and the effort/time required to get rid of iostreams , I think I will abandon this challenge for now ;-) Just to let you know "virtual methods" and "templates", among others, are supported inside the kernel... Greetings, -aziz From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 20:47:28 2005 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 ACADE16A4CE for ; Thu, 21 Apr 2005 20:47:28 +0000 (GMT) Received: from xor.cs.umd.edu (xor.cs.umd.edu [128.8.128.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2360B43D39 for ; Thu, 21 Apr 2005 20:47:28 +0000 (GMT) (envelope-from capveg@cs.umd.edu) Received: (from capveg@localhost) by xor.cs.umd.edu (8.12.10/8.12.5) id j3LKlQ9E004710; Thu, 21 Apr 2005 16:47:26 -0400 (EDT) Date: Thu, 21 Apr 2005 16:47:26 -0400 From: Rob To: freebsd-hackers@freebsd.org Message-ID: <20050421204726.GK14341@xor.cs.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i cc: Rob Subject: FreeBSD Network Implementation 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: Thu, 21 Apr 2005 20:47:28 -0000 [applogies if this is in a FAQ somewhere... I've looked in a number of places, and am not able to find the answer] Hi, I am trying to figure out how large a specific buffer is in FreeBSD. The buffer in question is the buffer between the network layer and the ethernet device, i.e., if packets are being passed down the network stack from tcp faster than the hardware can handle them, at what point do packets start getting dropped locally? I believe the answer is: % sysctl -a [snip] net.inet.ip.intr_queue_maxlen: 50 But try as I might, I can't find the documentation of the variable to confirm it. Can anyone point me in the right direction? Thanks, - Rob . From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 21:09:50 2005 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 8357B16A4CE for ; Thu, 21 Apr 2005 21:09:50 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F6FD43D39 for ; Thu, 21 Apr 2005 21:09:49 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 72568 invoked from network); 21 Apr 2005 21:11:36 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 21 Apr 2005 21:11:36 -0000 Message-ID: <42681699.8040904@freebsd.org> Date: Thu, 21 Apr 2005 23:09:45 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: Rob References: <20050421204726.GK14341@xor.cs.umd.edu> In-Reply-To: <20050421204726.GK14341@xor.cs.umd.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Network Implementation 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: Thu, 21 Apr 2005 21:09:50 -0000 Rob wrote: > [applogies if this is in a FAQ somewhere... I've looked in a number of places, and > am not able to find the answer] > > Hi, > > I am trying to figure out how large a specific buffer is in FreeBSD. > The buffer in question is the buffer between the network layer and the > ethernet device, i.e., if packets are being passed down the network > stack from tcp faster than the hardware can handle them, at what point > do packets start getting dropped locally? > > I believe the answer is: > > % sysctl -a > [snip] > net.inet.ip.intr_queue_maxlen: 50 > > But try as I might, I can't find the documentation of the variable to > confirm it. Can anyone point me in the right direction? You figured it out correctly. However at that moment TCP flow control would kick in and save you from local packet loss so to say. -- Andre From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 22:06:33 2005 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 1A7BB16A4CE; Thu, 21 Apr 2005 22:06:33 +0000 (GMT) Received: from xor.cs.umd.edu (xor.cs.umd.edu [128.8.128.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88B9543D39; Thu, 21 Apr 2005 22:06:32 +0000 (GMT) (envelope-from capveg@cs.umd.edu) Received: (from capveg@localhost) by xor.cs.umd.edu (8.12.10/8.12.5) id j3LM6Vwh005980; Thu, 21 Apr 2005 18:06:31 -0400 (EDT) Date: Thu, 21 Apr 2005 18:06:31 -0400 From: Rob To: Andre Oppermann Message-ID: <20050421220631.GP14341@xor.cs.umd.edu> References: <20050421204726.GK14341@xor.cs.umd.edu> <42681699.8040904@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42681699.8040904@freebsd.org> User-Agent: Mutt/1.4.1i cc: freebsd-hackers@freebsd.org cc: Rob Subject: Re: FreeBSD Network Implementation 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: Thu, 21 Apr 2005 22:06:33 -0000 > You figured it out correctly. However at that moment TCP flow control > would kick in and save you from local packet loss so to say. Hi, Thanks for the response, but you have actually confused me more. It is my understanding that TCP doesn't have flow control (i.e., local to the node), it has congestion control, which is end-to-end across the network. So it is entirely possible to drop packets locally in this method with a highband width, high latency (so called "long-fat") connection. For example, if there were a giga-bit/second link, with a latency of 100 miliseconds rtt, and window scaling set to 14 (the max), tcp could in theory open it's congestion window up to 2^16*2^14 or 2^30 bytes, which could be ACK'd more quickly than the net.inet.ip.intr_queue_max queue would allow for, causing packets to be dropped locally. Basically, the bandwidth-delay product dictates the size the buffer/queue should be, and in the above (extreme) example, it should be 0.1s*1Gb/s=12.5MB which is larger than the 50 packets at 1500 bytes each that you get with net.inet.ip.intr_queue_max=50. In otherwords, this is the reason for the net.inet.ip.intr_queue_drops counter, right? I'm surprised that more of the tuning guides don't suggest increasing net.inet.ip.intr_queue_max to a higher value - am I missing something? The equivalent setting in Linux is 1000, and Windows 2k appears to be 1500 (not that this should be necessarily taken as any sort of endorsement). If my understanding is incorrect, please let me know. In any case, thanks for the help (and thanks to those that have replied off list). - Rob . From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 22:43:04 2005 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 B6E2516A4D0 for ; Thu, 21 Apr 2005 22:43:04 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 768FE43D1F for ; Thu, 21 Apr 2005 22:43:03 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 73146 invoked from network); 21 Apr 2005 22:44:50 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.54]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 21 Apr 2005 22:44:50 -0000 Message-ID: <42682C78.B1B4E47@freebsd.org> Date: Fri, 22 Apr 2005 00:43:04 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Rob References: <20050421204726.GK14341@xor.cs.umd.edu> <42681699.8040904@freebsd.org> <20050421220631.GP14341@xor.cs.umd.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Network Implementation 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: Thu, 21 Apr 2005 22:43:04 -0000 Rob wrote: > > > You figured it out correctly. However at that moment TCP flow control > > would kick in and save you from local packet loss so to say. > > Hi, > > Thanks for the response, but you have actually confused me more. It is > my understanding that TCP doesn't have flow control (i.e., local to the > node), it has congestion control, which is end-to-end across the network. tcp_output() knows about queue overflows when it tries to send packets and instantly gives up until ACK's get in. This avoids real packet drops locally and allows to retry the same packet a microseconds later again without having to wait for the other side to signal a real packet loss. > So it is entirely possible to drop packets locally in this method > with a highband width, high latency (so called "long-fat") connection. Packets are not exactly dropped. tcp_output() generates and adds one packet after the other to the interface queue. The moment this doesn't work anymore it breaks out of that loop even it would be allowed by the window to send more. The failing packet is not dropped but retried later and further packets are not produced for the time being. It just defers further delivery. A local loss would be different. There it would fail with one packet, drop it, and try again with the next packet which may go through if the network card was done with an earlier packet that moment. However this is not what happens. Because things happens inside the kernel TCP knows how to deal with this in the right way and to avoid any costly recoveries from these cases. > For example, if there were a giga-bit/second link, with a latency of > 100 miliseconds rtt, and window scaling set to 14 (the max), tcp could > in theory open it's congestion window up to 2^16*2^14 or 2^30 bytes, > which could be ACK'd more quickly than the net.inet.ip.intr_queue_max > queue would allow for, causing packets to be dropped locally. Basically, > the bandwidth-delay product dictates the size the buffer/queue should be, > and in the above (extreme) example, it should be 0.1s*1Gb/s=12.5MB which > is larger than the 50 packets at 1500 bytes each that you get > with net.inet.ip.intr_queue_max=50. You are mixing up the socket buffer size with the interface queue size. Those are not the same. TCP will converges to maximal link speed and then is bound by the output rate of the interface even if the window gets larger. > In otherwords, this is the reason for the net.inet.ip.intr_queue_drops > counter, right? I'm surprised that more of the tuning guides don't No, not directly. This counter gets to work when the box is doing routing. Drop happen when you go from a high bandwidth link to a low(er) bandwidth link overloading the slow link. On a box not doing routing you should'nt see any drops. > suggest increasing net.inet.ip.intr_queue_max to a higher value - am I > missing something? The equivalent setting in Linux is 1000, and Windows > 2k appears to be 1500 (not that this should be necessarily taken as any > sort of endorsement). This doesn't really help. What happens with larger queues is just that you fill the larger queues and it takes longer until TCP's limiting kicks in. The queues have to have some size to provide some smoothing of burstiness but should not be too long to keep some direct feedback in place. > If my understanding is incorrect, please let me know. In any case, > thanks for the help (and thanks to those that have replied off list). -- Andre From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 22:57:41 2005 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 05B8C16A4D2 for ; Thu, 21 Apr 2005 22:57:41 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4324943D2F for ; Thu, 21 Apr 2005 22:57:40 +0000 (GMT) (envelope-from max@love2party.net) Received: from p54A3E1E2.dip.t-dialin.net[84.163.225.226] (helo=donor.laier.local) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0ML25U-1DOkc61eC2-0002wr; Fri, 22 Apr 2005 00:57:38 +0200 From: Max Laier To: freebsd-hackers@freebsd.org Date: Fri, 22 Apr 2005 00:57:35 +0200 User-Agent: KMail/1.8 References: <4267E75E.3000600@samsco.org> In-Reply-To: <4267E75E.3000600@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504220057.37368.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Subject: Addendum: FreeBSD Status Report Jan-Mar 2005 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, 21 Apr 2005 22:57:41 -0000 Unfortunately, the following report got lost: New Wireless Drivers URL: http://ipw2100.sourceforge.net/firmware.php?fid=4 URL: http://ralink.rapla.net/ Contact: Damien Bergamini Four new wireless drivers were imported: ipw : driver for Intel PRO/Wireless 2100 adapters (MiniPCI). iwi : driver for Intel PRO/Wireless 2200BG/2225BG/2915ABG adapters (PCI or MiniPCI). ral : driver for Ralink RT2500 wireless adapters (PCI or CardBus). ural : driver for Ralink RT2500USB wireless USB 2.0 adapters. The ipw and iwi drivers require firmwares to operate. These firmwares can't be redistributed with the base system due to license restrictions. See firmware licensing terms here: http://ipw2100.sourceforge.net/firmware.php?fid=4 . Ports which include the firmware images as well as the firmware loader are being worked on. A list of adapters supported by ral and ural can be found here: http://ralink.rapla.net/ . Open tasks: 1. Create ports for ipw and iwi firmwares. 2. Add IBSS support to iwi. 3. Add WPA (802.11i) support to ipw and iwi. 4. Add hardware encryption (WEP, TKIP and CCMP) support in ral and ural. 5. Add automatic rate adaptation support to ural. __________________________________________________________________ From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 06:16:33 2005 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 A288416A4CE for ; Fri, 22 Apr 2005 06:16:33 +0000 (GMT) Received: from orion.erdves.lt (ns2.lrtc.net [217.9.240.98]) by mx1.FreeBSD.org (Postfix) with SMTP id 7050143D2D for ; Fri, 22 Apr 2005 06:16:32 +0000 (GMT) (envelope-from donatas@lrtc.net) Received: (qmail 9786 invoked from network); 22 Apr 2005 06:16:31 -0000 Received: from unknown (HELO www.lrtc.net) (217.9.240.99) by orion.erdves.lt with SMTP; 22 Apr 2005 06:16:31 -0000 Received: from donatas ([217.9.241.242]) by www.lrtc.net (Lotus Domino Release 6.0) with ESMTP id 2005042209162954-20018 ; Fri, 22 Apr 2005 09:16:29 +0300 Message-ID: <002001c54702$d2c500c0$9f90a8c0@DONATAS> From: "Donatas" To: Date: Fri, 22 Apr 2005 09:16:29 +0300 Organization: AB Lietuvos Radijo ir Televizijos Centras MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-MIMETrack: Itemize by SMTP Server on lotus/LRTC(Release 6.0|September 26, 2002) at 04/22/2005 09:16:29 AM,04/22/2005 09:16:30 AM, Serialize complete at 04/22/2005 09:16:30 AM Content-Type: text/plain; charset="iso-8859-4" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: flood with ng_bridge X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Donatas List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 06:16:33 -0000 can you check flood.gif?(it's denied to send gif's to this conference) ftp://temp:temp@217.9.241.242/flood.gif for unknown reasons ng_bridge seems to be working like ng_hub and is=20 flooding network even after establishing session between two mac = addresses. using kernel bridge instead of ng_bridge solves the problem, but on = heavy network loads "unknown" packets apear in random directions (this does = not happed using ng_bridge or ng_hub) os used - only FreeBSD5.3 thank you... From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 08:37:27 2005 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 7D4B216A4CE for ; Fri, 22 Apr 2005 08:37:27 +0000 (GMT) Received: from priv-edtnes40.telusplanet.net (outbound05.telus.net [199.185.220.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0480443D53 for ; Fri, 22 Apr 2005 08:37:27 +0000 (GMT) (envelope-from pfak@telus.net) Received: from [192.168.1.151] (really [64.180.103.26]) by priv-edtnes40.telusplanet.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP <20050422083726.UXDM7936.priv-edtnes40.telusplanet.net@[192.168.1.151]>; Fri, 22 Apr 2005 02:37:26 -0600 Message-ID: <4268B7CA.4090001@telus.net> Date: Fri, 22 Apr 2005 01:37:30 -0700 From: Peter Kieser User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: c0ldbyte References: <98c02f5f050421010735a3cfe2@mail.gmail.com> <98c02f5f05042104414bb668c3@mail.gmail.com> <20050421075035.P51738@eleanor.us1.wmi.uvac.net> In-Reply-To: <20050421075035.P51738@eleanor.us1.wmi.uvac.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: freebsd-hackers@freebsd.org Subject: Re: ipfw1sysctl and lifetime X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 08:37:27 -0000 Why must you continue to respond to threads that you have no answer for, wasting our bandwidth, disk space, and time to read your useless messages? --Peter c0ldbyte wrote: > On Thu, 21 Apr 2005, Omar Lopez Limonta wrote: > >> I Change: >> >> >> net.inet.ip.fw.dyn_ack_lifetime: 300 -> 3600 >> >> net.inet.ip.fw.dyn_udp_lifetime: 10 -> 10 >> >> net.inet.ip.fw.dyn_buckets: 256 -> 1024 >> >> net.inet.ip.fw.dyn_max: 1000 -> 2500 >> >> 緼re good these values? , 縤 need chanege another value? >> > > Dont know my friend. I have no way of testing those out right now. I > assume those values are from a 5.x machine I only run 4.x's at the > moment untill I test 5.4-RELEASE more and evaluate its potential > and gain on my systems. > >------------------------------------------------------------------------ > >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 09:00:17 2005 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 609E716A4D0 for ; Fri, 22 Apr 2005 09:00:17 +0000 (GMT) Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2093C43D4C for ; Fri, 22 Apr 2005 09:00:17 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix4-2.free.fr (Postfix) with ESMTP id B45DC3192E5 for ; Fri, 22 Apr 2005 11:00:15 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id A6336405A; Fri, 22 Apr 2005 10:59:34 +0200 (CEST) Date: Fri, 22 Apr 2005 10:59:34 +0200 From: Jeremie Le Hen To: freebsd-hackers@freebsd.org Message-ID: <20050422085934.GR91329@obiwan.tataz.chchile.org> References: <20050420135013.GE91329@obiwan.tataz.chchile.org> <20050420143715.GF91329@obiwan.tataz.chchile.org> <20050420151104.GA11753@grummit.biaix.org> <20050420165559.GI91329@obiwan.tataz.chchile.org> <20050421151436.GA86490@grummit.biaix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050421151436.GA86490@grummit.biaix.org> User-Agent: Mutt/1.5.9i Subject: Re: Configuration differences for jails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 09:00:17 -0000 > I've seen them mentioned again in this thread. There apparently is a > "make distribution" target designed to address /etc, but I can't find it > anywhere. cd /usr/src/etc # This will create the standard directory hierarchy using mtree(8). make DESTDIR=/jail distrib-dirs # This will install a default /etc, IIUC. make DESTDIR=/jail distribution -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 15:45:05 2005 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 1117216A4CE; Thu, 21 Apr 2005 15:45:05 +0000 (GMT) Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu [128.30.28.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1F1A43D1F; Thu, 21 Apr 2005 15:45:04 +0000 (GMT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (localhost.csail.mit.edu [127.0.0.1]) j3LFirbl049028 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Thu, 21 Apr 2005 11:44:54 -0400 (EDT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: (from wollman@localhost) by khavrinen.csail.mit.edu (8.13.1/8.13.1/Submit) id j3LFirrB049025; Thu, 21 Apr 2005 11:44:53 -0400 (EDT) (envelope-from wollman) From: Garrett Wollman MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <16999.51829.136518.268429@khavrinen.csail.mit.edu> Date: Thu, 21 Apr 2005 11:44:53 -0400 To: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) In-Reply-To: <86zmvssf0j.fsf@xps.des.no> References: <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> <20050420152038.GI1157@green.homeunix.org> <20050420153528.GC77731@stack.nl> <86zmvssf0j.fsf@xps.des.no> X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-1.6 (khavrinen.csail.mit.edu [127.0.0.1]); Thu, 21 Apr 2005 11:44:54 -0400 (EDT) X-Virus-Scanned: ClamAV 0.83/846/Thu Apr 21 10:08:03 2005 on khavrinen.csail.mit.edu X-Virus-Status: Clean X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on khavrinen.csail.mit.edu X-Mailman-Approved-At: Fri, 22 Apr 2005 12:49:56 +0000 cc: freebsd-hackers@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS client/buffer cache deadlock 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, 21 Apr 2005 15:45:05 -0000 < POSIX =3D=3D SUSv3 these days. Not quite. POSIX and SUSv3 use the same specification, but don't require the same things. (Specifically, SUSv3 requires the XSI option to be implemented.) -GAWollman From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 21 17:15:13 2005 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 AFB0216A4CE; Thu, 21 Apr 2005 17:15:13 +0000 (GMT) Received: from hex.databits.net (hex.databits.net [216.118.117.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 473FA43D48; Thu, 21 Apr 2005 17:15:13 +0000 (GMT) (envelope-from will@csociety.org) Received: by hex.databits.net (Postfix, from userid 1001) id AC4A857AE8; Thu, 21 Apr 2005 12:15:12 -0500 (CDT) Date: Thu, 21 Apr 2005 12:15:12 -0500 From: Will Andrews To: Rex Roof Message-ID: <20050421171512.GU1693@hex.databits.net> Mail-Followup-To: Rex Roof , freebsd-hackers@freebsd.org, freebsd-current@freebsd.org References: <6afb69aa05042008065db9d0cb@mail.gmail.com> <6afb69aa05042008093d6d59d0@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ixNtouB4hv1hrEz3" Content-Disposition: inline In-Reply-To: <6afb69aa05042008093d6d59d0@mail.gmail.com> User-Agent: Mutt/1.5.6i X-Mailman-Approved-At: Fri, 22 Apr 2005 12:49:56 +0000 cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: gvinum during bootup 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, 21 Apr 2005 17:15:13 -0000 --ixNtouB4hv1hrEz3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 20, 2005 at 11:09:50AM -0400, Rex Roof wrote: > I'm running a FreeBSD6 machine current as of a few days ago and I'm > working on a gvinum configuration, I couldn't find any place where it > referenced gvinum on startup so after fussing around with the rc > system a little, I wrote an /etc/rc.d/gvinum script that looks like geom_vinum only needs the module loaded on startup to work. So add geom_vinum_load=3D"YES" to your loader.conf. That's why there isn't any rc.d/gvinum script, like there is for old-vinum. This should probably be documented... Regards, --=20 wca --ixNtouB4hv1hrEz3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCZ9+gF47idPgWcsURAsG/AJ9AXYqki1Qx1JwVi8bHYkCzfRuyWACfXbza UuLHQ6MteNiOgx00y5g1uU4= =FvFG -----END PGP SIGNATURE----- --ixNtouB4hv1hrEz3-- From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 14:22:29 2005 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 F0C9B16A4E2 for ; Fri, 22 Apr 2005 14:22:28 +0000 (GMT) Received: from hotmail.com (bay2-f14.bay2.hotmail.com [65.54.247.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC88143D5D for ; Fri, 22 Apr 2005 14:22:28 +0000 (GMT) (envelope-from jas_arlerr@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 22 Apr 2005 07:22:28 -0700 Message-ID: Received: from 61.187.54.10 by by2fd.bay2.hotmail.msn.com with HTTP; Fri, 22 Apr 2005 14:22:28 GMT X-Originating-IP: [61.187.54.10] X-Originating-Email: [jas_arlerr@hotmail.com] X-Sender: jas_arlerr@hotmail.com From: "Jas arlerr" To: joerg@britannica.bec.de, freebsd-hackers@freebsd.org Date: Fri, 22 Apr 2005 14:22:28 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed X-OriginalArrivalTime: 22 Apr 2005 14:22:28.0598 (UTC) FILETIME=[B68E2960:01C54746] X-Mailman-Approved-At: Fri, 22 Apr 2005 14:34:08 +0000 Subject: Re: Configuration differences for jails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 14:22:29 -0000 >From: Joerg Sonnenberger >To: freebsd-hackers@freebsd.org >Subject: Re: Configuration differences for jails >Date: Thu, 21 Apr 2005 13:43:59 +0200 > >On Thu, Apr 21, 2005 at 07:39:08AM -0400, c0ldbyte wrote: > > Now if that last question is correct and thats the proccess you are using > > to create a jail then depending on the situation wouldnt that inturn > > defeat some of the main purposes of the jail, like the following. If you > > mounted your "/bin" on "/mnt/jail/bin" then if a person that was looking > > to break in and effect the system that is currently locked in the "jail" > > all he would have to do is just write something to the "jail/bin" which is > > actualy your root "/bin" and then the next time a binary is used from your > > root directories it could still infect the rest of the system ultimately > > defeating the purpose of what you just set up. To my understanding and use > > a jail is somewhat totaly independent of the OS that it resides in and > > wont be if you are using nullfs to mount root binary directories on it. > >ro mount as written by grant parent protects against this. > I am not very familar with mount_nullfs, but i think it is _one_ copy with _multiple_ references(FIXME).So if we modify something in one jail, the same effect will also impose on other jails,even the real machine. Due to this problem, readonly mounts may be a good choice. BUT if we do some things related to the /etc files, such as passwd, ro mounts can not deal with this situation because different jails need different passwd files for private users. So I think this can only be done by making a copy of relevant files but not ro mounts. Any idea? regards Jas _________________________________________________________________ 享用世界上最大的电子邮件系统— MSN Hotmail。 http://www.hotmail.com From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 15:11:57 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7D9F516A4CE; Fri, 22 Apr 2005 15:11:57 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.3/8.13.1) with ESMTP id j3MF8Zqc087223; Fri, 22 Apr 2005 11:08:35 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.3/8.13.1/Submit) id j3MF8Z8O087222; Fri, 22 Apr 2005 11:08:35 -0400 (EDT) (envelope-from green) Date: Fri, 22 Apr 2005 11:08:35 -0400 From: Brian Fundakowski Feldman To: Garrett Wollman Message-ID: <20050422150835.GM1157@green.homeunix.org> References: <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> <20050420152038.GI1157@green.homeunix.org> <20050420153528.GC77731@stack.nl> <20050420155233.GJ1157@green.homeunix.org> <16998.37222.529748.205885@khavrinen.csail.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16998.37222.529748.205885@khavrinen.csail.mit.edu> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS client/buffer cache deadlock X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 15:11:57 -0000 On Wed, Apr 20, 2005 at 01:29:10PM -0400, Garrett Wollman wrote: > < said: > > > I think the first is more useful behavior than the last. Supporting it > > should be exactly the same as supporting what happens if the actual > > filesystem fills up. In this case, the filesystem is being requested to > > write more "than there is room for." > > Returning a short write for operations on regular files would > definitely be considered astonishing. The changes that you have made > should be considered flow control, not admission control, and should > appear to the user no differently than if we were waiting for a slow > disk to write something; i.e., the user thread should be blocked until > either the entire write completes, or the process is interrupted by a > signal. Can you find any evidence that it's acceptable to interleave multiple writers that are doing O_APPEND? At best, to do what you're asking, they could be kept from being interleaved from the context of one specific NFS client host... -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 15:38:46 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D457916A4CE; Fri, 22 Apr 2005 15:38:45 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.3/8.13.1) with ESMTP id j3MFZMOR087413; Fri, 22 Apr 2005 11:35:22 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.3/8.13.1/Submit) id j3MFZMbb087412; Fri, 22 Apr 2005 11:35:22 -0400 (EDT) (envelope-from green) Date: Fri, 22 Apr 2005 11:35:22 -0400 From: Brian Fundakowski Feldman To: Garrett Wollman Message-ID: <20050422153522.GN1157@green.homeunix.org> References: <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> <20050420152038.GI1157@green.homeunix.org> <20050420153528.GC77731@stack.nl> <20050420155233.GJ1157@green.homeunix.org> <16998.37222.529748.205885@khavrinen.csail.mit.edu> <20050422150835.GM1157@green.homeunix.org> <17001.6159.521697.442481@khavrinen.csail.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17001.6159.521697.442481@khavrinen.csail.mit.edu> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS client/buffer cache deadlock X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 15:38:46 -0000 On Fri, Apr 22, 2005 at 11:28:15AM -0400, Garrett Wollman wrote: > < said: > > > > Can you find any evidence that it's acceptable to interleave multiple > > writers that are doing O_APPEND? At best, to do what you're asking, > > they could be kept from being interleaved from the context of one > > specific NFS client host... > > As far as POSIX goes, the standard says that applications are expected > to handle serialization. It makes no exception for O_APPEND. Then let's fix IO_UNIT so the existing code can DTRT. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 15:42:02 2005 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 61C2F16A4CE for ; Fri, 22 Apr 2005 15:42:02 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 177CF43D55 for ; Fri, 22 Apr 2005 15:42:02 +0000 (GMT) (envelope-from dleimbac@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so330121nzo for ; Fri, 22 Apr 2005 08:42:01 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=EZi13fFNuoZNmDvWVK6GXpM4BKqqIp+wWWYjsKBOwHjxSUUrXDVibbYw8gb7yHXUVmxjDZ1SfWHFINzVwqfr6sd+Luk25T7qX/o8rmq3KHi8RRC2y0du2shM2Ovrd0juBsmEDrwIkHm+zFHIHprYl7DfNs1tohFpd1YIWt3MZYU= Received: by 10.36.91.2 with SMTP id o2mr212368nzb; Fri, 22 Apr 2005 08:42:01 -0700 (PDT) Received: by 10.36.103.17 with HTTP; Fri, 22 Apr 2005 08:42:01 -0700 (PDT) Message-ID: <5bbfe7d40504220842578b2d2d@mail.gmail.com> Date: Fri, 22 Apr 2005 08:42:01 -0700 From: David Leimbach To: FreeBSD Hackers Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: libthread 1:1 threads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Leimbach List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 15:42:02 -0000 Perhaps David Xu could clue me in a bit more :) I just got around to reading the status report for FreeBSD and the 1:1 threading caught my eye. I'm not terribly familiar with FreeBSD's KSE based threading but rather than adding a new system call [which may be ok... though I've worked on systems where a minimal set of system calls is the desired approach.. usually microkernels] would it be possible to add KSEs to a task using rfork()? Maybe I've just been playing around with Plan 9 too much lately :) Anyway, I like that there will be a 1:1 threading library and if I had more free time and wasn't working on other projects I'd be more than willing to help test and work on/with this. Still, very very cool :) Dave From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 15:42:23 2005 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 45B0216A4CE for ; Fri, 22 Apr 2005 15:42:23 +0000 (GMT) Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id C882F43D2D for ; Fri, 22 Apr 2005 15:42:22 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix4-2.free.fr (Postfix) with ESMTP id 138DA319294; Fri, 22 Apr 2005 17:42:21 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 40E49405B; Fri, 22 Apr 2005 17:41:40 +0200 (CEST) Date: Fri, 22 Apr 2005 17:41:40 +0200 From: Jeremie Le Hen To: Jas arlerr Message-ID: <20050422154140.GW91329@obiwan.tataz.chchile.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i cc: freebsd-hackers@freebsd.org cc: joerg@britannica.bec.de Subject: Re: Configuration differences for jails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 15:42:23 -0000 Hi, > I am not very familar with mount_nullfs, but i think it is _one_ copy with > _multiple_ references(FIXME).So if we modify something in one jail, the > same effect will also impose on other jails,even the real machine. Due > to this problem, readonly mounts may be a good choice. Usually, /bin and others are never modified, that's why it may be null mounted readonly. If you want to be able to write to these directories from inside the jail, there are two methods : - First is to use mount_unionfs(8) which will mount another directory above the null mounted directory. Note that unionfs is currently known to be broken, although there are no official list of known bugs, AFAIK. Having a null mount AND an union mount over it may perhaps introduce a non-negligible overhead, I guess. - Make each jail have its own world. > BUT if we do some things related to the /etc files, such as passwd, ro > mounts can not deal with this situation because different jails need > different passwd files for private users. > So I think this can only be done by making a copy of relevant files but not > ro mounts. Once again, /etc is not intended to be null mounted. It contains sensitive informations about the host that should not be published in jails. You will have to use the "distribution" make target from /usr/src/etc (see my previous email). Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 17:51:00 2005 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 2E2FE16A4CE for ; Fri, 22 Apr 2005 17:51:00 +0000 (GMT) Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id E17BA43D54 for ; Fri, 22 Apr 2005 17:50:59 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix4-2.free.fr (Postfix) with ESMTP id 191F33192EF for ; Fri, 22 Apr 2005 19:50:58 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 514FB407F; Fri, 22 Apr 2005 19:50:16 +0200 (CEST) Date: Fri, 22 Apr 2005 19:50:16 +0200 From: Jeremie Le Hen To: freebsd-hackers@freebsd.org Message-ID: <20050422175016.GX91329@obiwan.tataz.chchile.org> References: <20050420135013.GE91329@obiwan.tataz.chchile.org> <20050420143715.GF91329@obiwan.tataz.chchile.org> <20050420151104.GA11753@grummit.biaix.org> <20050420165559.GI91329@obiwan.tataz.chchile.org> <20050421151436.GA86490@grummit.biaix.org> <20050422085934.GR91329@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050422085934.GR91329@obiwan.tataz.chchile.org> User-Agent: Mutt/1.5.9i Subject: Re: Configuration differences for jails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 17:51:00 -0000 > # This will create the standard directory hierarchy using mtree(8). > make DESTDIR=/jail distrib-dirs For the record, I discovered the "hierarchy" make target in /usr/src/Makefile.inc. I think we ought to use this one instead on the internal distrib-dirs target. -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 18:03:47 2005 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 4B67F16A4CF for ; Fri, 22 Apr 2005 18:03:47 +0000 (GMT) Received: from szerver.siodigit.hu (ns.siodigit.hu [194.143.225.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 581BE43D3F for ; Fri, 22 Apr 2005 18:03:46 +0000 (GMT) (envelope-from feczo@siodigit.hu) Received: from feczo.sdi.hu ([192.168.0.217]) by szerver.siodigit.hu with esmtp (Exim 4.50 (FreeBSD)) id 1DP2VE-000Hyy-W5 for freebsd-hackers@freebsd.org; Fri, 22 Apr 2005 20:03:45 +0200 From: Feczak Szabolcs To: freebsd-hackers@freebsd.org Content-Type: text/plain Organization: =?ISO-8859-1?Q?Si=F3digit?= Kft. Date: Fri, 22 Apr 2005 20:07:45 +0200 Message-Id: <1114193265.22867.3.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit X-Spam-Score: -5.9 (-----) X-Spam-Report: Spam detection software: the administrator of that system for details.gothope some of you can answer this: On k, 2005-04-19 at 17:21 -0400, Paul Mather wrote: > to what you describe using geom_gate for the remote component. See > ggated(8) and ggatec(8) for how to set up an use a geom_gate provider. [...] Content analysis details: (-5.9 points, 5.0 required) pts rule name description -------------------------------------------------- -3.3 ALL_TRUSTED Did not pass through any untrusted hosts 1% [score: 0.0000] Subject: Failover cluster for webserver with dynamic content ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 18:03:47 -0000 This happend on the freebsd-questions list, but I got no answer for days. Joshua Tinnin advised me to make a try here. I hope some of you can answer this: On k, 2005-04-19 at 17:21 -0400, Paul Mather wrote: > to what you describe using geom_gate for the remote component. See > ggated(8) and ggatec(8) for how to set up an use a geom_gate provider. > Note that the geom_mirror + geom_gate synchronisation would be one-way. Bad luck, I would like to have something that creates a layer over the two volume of the machines, and when this higher layer accessed both execute the requested operation. Anyway one step further, my question is How can I create a failover cluster with two machines for a freebsd webserver with dynamic content runing apache with php, and postgresql. I read about CARP, but more experienced people advised me to use DNS-LB since its more reliable with service type pings (HTTP GET) than simple is the machine answers for TCP SYN. They made a point with that to me. Im trying to syncronize the postgresql database with Slony, no luck yet, all the examples I found describing master and slave on the same machine. I got slony communicate between the two, but on updates nothing happens on the slave. I access the master on unix socket, maybe other type of access needed .. hm I will see If on failure the switching is done with DNS-LB and the SQL is in sync Im nearly OK, but since I have file uploads on the webserver as well, I need a shared volume which available to both of them and after one is out the other still has access to the data. Maybe Im complettly wrong I have no clear ideas about what happens when this ... and what happens whan that ... scenarios All I want is a higher availability with two machines than one and without messing up the consistency of the data of course. Im not after chasing nearly 100% ... the policy/expectation is if one fails the other should automatically continue the serving data (nearly there) where the other stopped. If anyone did something like that, and aware of some solution without buying expensive HA hardware, please share us. Hope this is possible at all. From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 19:43:02 2005 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 C26DD16A4CE for ; Fri, 22 Apr 2005 19:43:02 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B15643D2F for ; Fri, 22 Apr 2005 19:43:02 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [208.206.78.97] (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 4B0CA7A41E; Fri, 22 Apr 2005 12:43:02 -0700 (PDT) Message-ID: <426953C5.9080502@elischer.org> Date: Fri, 22 Apr 2005 12:43:01 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en, hu MIME-Version: 1.0 To: David Leimbach References: <5bbfe7d40504220842578b2d2d@mail.gmail.com> In-Reply-To: <5bbfe7d40504220842578b2d2d@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD Hackers Subject: Re: libthread 1:1 threads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 19:43:02 -0000 David Leimbach wrote: >Perhaps David Xu could clue me in a bit more :) > >I just got around to reading the status report for FreeBSD and the 1:1 >threading caught my eye. > >I'm not terribly familiar with FreeBSD's KSE based threading but >rather than adding a new system call [which may be ok... though I've >worked on systems where a minimal set of system calls is the desired >approach.. usually microkernels] would it be possible to add KSEs to a >task using rfork()? > > KSE and 1:1 threading are different things. One creatres kernel threads on demand and the other keeps the kernel threads all the time the user thread exists. rfork is not the same.. it creates a new process context. that is what Linux does. it is also what we did before when running the the linuxthreads package. KSE and 1:1 use a lot of the same kernel changes and entities. Which one survives will be judged in time. >Maybe I've just been playing around with Plan 9 too much lately :) > >Anyway, I like that there will be a 1:1 threading library and if I had >more free time and wasn't working on other projects I'd be more than >willing to help test and work on/with this. > > there has been a 1:1 and an M:N library since 5.2 >Still, very very cool :) > >Dave >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 22:02:16 2005 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 688DF16A4CE for ; Fri, 22 Apr 2005 22:02:16 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1314743D2D for ; Fri, 22 Apr 2005 22:02:16 +0000 (GMT) (envelope-from dleimbac@gmail.com) Received: by zproxy.gmail.com with SMTP id 18so141721nzp for ; Fri, 22 Apr 2005 15:02:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ICiSPbR7tU37T5BxehD+mwEU60hOPzLQp2gg1UbvflQ0JSAqzgZzEtZDb0FmKncUTEdwXoNXtZ1aL5lQoynbF4igSs/H4/SW8utVEWLr5zRRSUMJxq8+70Y16sAs01xOj02E1PiuXKgbfZAYTl1U2mgFeW31TvR90fbLouN8SwM= Received: by 10.36.33.6 with SMTP id g6mr195053nzg; Fri, 22 Apr 2005 15:02:15 -0700 (PDT) Received: by 10.36.103.17 with HTTP; Fri, 22 Apr 2005 15:02:15 -0700 (PDT) Message-ID: <5bbfe7d4050422150226c6712d@mail.gmail.com> Date: Fri, 22 Apr 2005 15:02:15 -0700 From: David Leimbach To: Julian Elischer In-Reply-To: <426953C5.9080502@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <5bbfe7d40504220842578b2d2d@mail.gmail.com> <426953C5.9080502@elischer.org> cc: FreeBSD Hackers Subject: Re: libthread 1:1 threads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Leimbach List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 22:02:16 -0000 On 4/22/05, Julian Elischer wrote: >=20 >=20 > David Leimbach wrote: >=20 > >Perhaps David Xu could clue me in a bit more :) > > > >I just got around to reading the status report for FreeBSD and the 1:1 > >threading caught my eye. > > > >I'm not terribly familiar with FreeBSD's KSE based threading but > >rather than adding a new system call [which may be ok... though I've > >worked on systems where a minimal set of system calls is the desired > >approach.. usually microkernels] would it be possible to add KSEs to a > >task using rfork()? > > > > >=20 > KSE and 1:1 threading are different things. > One creatres kernel threads on demand and the other keeps the kernel > threads all the time the user thread exists. >=20 Ah interesting. > rfork is not the same.. it creates a new process context. that is what > Linux does. > it is also what we did before when running the the linuxthreads package. >=20 According to the man page, and plan 9 where rfork originated you can use it to modify an extant process. In fact you have to set the RFPROC flag to make a new process or all the changes apply to the current one. Either that or the man page is wrong. > KSE and 1:1 use a lot of the same kernel changes and entities. > Which one survives will be judged in time. >=20 > >Maybe I've just been playing around with Plan 9 too much lately :) > > > >Anyway, I like that there will be a 1:1 threading library and if I had > >more free time and wasn't working on other projects I'd be more than > >willing to help test and work on/with this. > > > > >=20 > there has been a 1:1 and an M:N library since 5.2 >=20 Yeah but I took a bit of a FreeBSD hiatus around 5.0/5.1 and am just now poking around again so it's all new to me :). Dave From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 23 07:24:01 2005 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 1BA7416A4CE; Sat, 23 Apr 2005 07:24:01 +0000 (GMT) Received: from priv-edtnes51.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id A055743D1F; Sat, 23 Apr 2005 07:24:00 +0000 (GMT) (envelope-from pfak@telus.net) Received: from [192.168.1.151] (really [64.180.103.26]) by priv-edtnes51.telusplanet.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP <20050423072400.UEKN12034.priv-edtnes51.telusplanet.net@[192.168.1.151]>; Sat, 23 Apr 2005 01:24:00 -0600 Message-ID: <4269F816.2080404@telus.net> Date: Sat, 23 Apr 2005 00:24:06 -0700 From: Peter Kieser User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: c0ldbyte References: <98c02f5f050421010735a3cfe2@mail.gmail.com> <98c02f5f05042104414bb668c3@mail.gmail.com> <20050421075035.P51738@eleanor.us1.wmi.uvac.net> <4268B7CA.4090001@telus.net> <20050423030808.B95290@eleanor.us1.wmi.uvac.net> In-Reply-To: <20050423030808.B95290@eleanor.us1.wmi.uvac.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@FreeBSD.org cc: postmaster@FreeBSD.org Subject: List complaint (Was: Re: ipfw1sysctl and lifetime) 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: Sat, 23 Apr 2005 07:24:01 -0000 Someone really needs to remove this guy from the list (or at least give him an "official" warning of some kind). His repeated warnings on the list has not done anything to his conduct nor has it caused him to stop his childish antics. All he is doing is polluting the list archives. In the 4 years I've been subscribed to this list I'm horrified by the rudeness of this user. --Peter c0ldbyte wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, 22 Apr 2005, Peter Kieser wrote: > >> Why must you continue to respond to threads that you have no answer >> for, wasting our bandwidth, disk space, and time to read your useless >> messages? >> >> --Peter >> > > Apparently you have no concern in public lists and it aggravates > your mental cpacity for information. As I do know some things I > dont know everything but am willing to give incite into problems > hoping to lead another to the answer. Now if this is nothing you > would like to read then just shut your fucking mouth"fingers" and > go curl up next to your mommy ya little fuck faced midget. > > - -- ( When in doubt, use brute force. -- Ken Thompson 1998 ) > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.0 (FreeBSD) > Comment: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF7DF979F > Comment: Fingerprint = D1DC 0AA4 1C4E EAD4 24EB 7E77 B261 50BA F7DF 979F > > iD8DBQFCafWmsmFQuvffl58RAoJnAJ99c0MY5R1gRJuYExA77KGTbFSCpwCeImAS > P/HPS18GATsQGXpUhudHFvI= > =A8Rj > -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 23 09:33:39 2005 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 ED37E16A4CE for ; Sat, 23 Apr 2005 09:33:39 +0000 (GMT) Received: from szerver.siodigit.hu (ns.siodigit.hu [194.143.225.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2059A43D1F for ; Sat, 23 Apr 2005 09:33:39 +0000 (GMT) (envelope-from feczo@siodigit.hu) Received: from feczo.sdi.hu ([192.168.0.217]) by szerver.siodigit.hu with esmtp (Exim 4.50 (FreeBSD)) id 1DPH16-000NDp-7h; Sat, 23 Apr 2005 11:33:37 +0200 From: Feczak Szabolcs To: freebsd-hackers@freebsd.org In-Reply-To: <200504221811.49439.soralx@cydem.org> References: <1114193265.22867.3.camel@localhost.localdomain> <200504221811.49439.soralx@cydem.org> Content-Type: text/plain Organization: =?ISO-8859-1?Q?Si=F3digit?= Kft. Date: Sat, 23 Apr 2005 11:37:40 +0200 Message-Id: <1114249060.23167.9.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit X-Spam-Score: -5.9 (-----) X-Spam-Report: Spam detection software: the administrator of that system for details. Content preview: On p, 2005-04-22 at 18:11 -0600, soralx@cydem.org create a failover cluster with two machines > > for a freebsd webserver with dynamic content > > runing apache with php, and postgresql. > > why can't this give you enough redundancy? [...] Content analysis details: (-5.9 points, 5.0 required) pts rule name description -------------------------------------------------- -3.3 ALL_TRUSTED Did not pass through any untrusted hosts 1% [score: 0.0000] Subject: Re: Failover cluster for webserver with dynamic content ? 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: Sat, 23 Apr 2005 09:33:40 -0000 On p, 2005-04-22 at 18:11 -0600, soralx@cydem.org wrote: > > Anyway one step further, my question is > > How can I create a failover cluster with two machines > > for a freebsd webserver with dynamic content > > runing apache with php, and postgresql. > > why can't you have 2 separate machines accessing one mirrored RAID? > can't this give you enough redundancy? I thought about this, but I have several fears with that. First of all which machine would serve the RAID ? If this machine fails, than even though I have the second machine no use of it, since it does not have access to the data anymore. Second: how do I sync the sql database ... even though they use the same filesystem, some caching happens and when one of them writes back earlier what happens when to the other one tries to fsync. Although I do not have deep understanding of the postgresql system I have a fear that this threatens the data consistency. From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 15:28:20 2005 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 B762616A4CE; Fri, 22 Apr 2005 15:28:20 +0000 (GMT) Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu [128.30.28.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 520F843D55; Fri, 22 Apr 2005 15:28:20 +0000 (GMT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (localhost.csail.mit.edu [127.0.0.1]) j3MFSFc5062091 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Fri, 22 Apr 2005 11:28:18 -0400 (EDT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: (from wollman@localhost) by khavrinen.csail.mit.edu (8.13.1/8.13.1/Submit) id j3MFSFv5062088; Fri, 22 Apr 2005 11:28:15 -0400 (EDT) (envelope-from wollman) From: Garrett Wollman MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17001.6159.521697.442481@khavrinen.csail.mit.edu> Date: Fri, 22 Apr 2005 11:28:15 -0400 To: Brian Fundakowski Feldman In-Reply-To: <20050422150835.GM1157@green.homeunix.org> References: <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> <20050420152038.GI1157@green.homeunix.org> <20050420153528.GC77731@stack.nl> <20050420155233.GJ1157@green.homeunix.org> <16998.37222.529748.205885@khavrinen.csail.mit.edu> <20050422150835.GM1157@green.homeunix.org> X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-1.6 (khavrinen.csail.mit.edu [127.0.0.1]); Fri, 22 Apr 2005 11:28:18 -0400 (EDT) X-Virus-Scanned: ClamAV 0.83/848/Thu Apr 21 15:37:33 2005 on khavrinen.csail.mit.edu X-Virus-Status: Clean X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on khavrinen.csail.mit.edu X-Mailman-Approved-At: Sat, 23 Apr 2005 12:09:41 +0000 cc: freebsd-hackers@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS client/buffer cache deadlock X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 15:28:20 -0000 < said: > Can you find any evidence that it's acceptable to interleave multiple > writers that are doing O_APPEND? At best, to do what you're asking, > they could be kept from being interleaved from the context of one > specific NFS client host... As far as POSIX goes, the standard says that applications are expected to handle serialization. It makes no exception for O_APPEND. -GAWollman From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 22 17:51:31 2005 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 F3E5216A4CE for ; Fri, 22 Apr 2005 17:51:30 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52CAB43D41 for ; Fri, 22 Apr 2005 17:51:30 +0000 (GMT) (envelope-from jason@funtigo.com) Received: from pimout3-ext.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102])j3MHoqD5003938 for ; Fri, 22 Apr 2005 13:50:52 -0400 X-ORBL: [67.124.224.18] Received: from tsai (adsl-67-124-224-18.dsl.snfc21.pacbell.net [67.124.224.18])j3MHpN5Z046398 for ; Fri, 22 Apr 2005 13:51:29 -0400 Message-ID: <005901c54764$2e587d20$de010a0a@tsai> From: "Jason Tsai" To: Date: Fri, 22 Apr 2005 10:53:20 -0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-Mailman-Approved-At: Sat, 23 Apr 2005 12:09:41 +0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: SIS NIC drivers problem if use "media 100baseTX mediaopt full-duplex" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 17:51:31 -0000 Hi all, First sorry for my poor writing engish! I don't know if it's right to = post in this mailist, but I think it's best place I can ask this kind of = question. I am using FreeBSD 5.4-RC3 now for testing purpose, I find that if I use = ifconfig_sis0=3D"inet 10.10.1.148 netmask 255.255.255.0" in = /etc/rc.conf, everything goes ok when I am using Jmeter(from Windows = Box) to load testing tomcat(on FreeBSD 5.4-RC3); but if I change = ifconfig_sis0 to "inet 10.10.1.148 netmask 255.255.255.0 media = 100baseTX mediaopt full-duplex", I always got "sis0 watchdog timeout" = error when I am doing testing.=20 Actually, the output of ifconfig if I am using ifconfig_sis0=3D"inet = 10.10.1.148 netmask 255.255.255.0" is like this: sis0: flags=3D18843 mtu = 1500 options=3D48 inet 10.10.1.148 netmask 0xffffff00 broadcast 10.10.1.255 ether 00:06:4f:02:f9:9a media: Ethernet autoselect (100baseTX ) status: active I am wondering if it's a bug? Please CC me when you reply. From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 23 03:54:36 2005 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 C195816A4CE for ; Sat, 23 Apr 2005 03:54:36 +0000 (GMT) Received: from omc3-s26.bay6.hotmail.com (omc3-s26.bay6.hotmail.com [65.54.249.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9779043D41 for ; Sat, 23 Apr 2005 03:54:36 +0000 (GMT) (envelope-from jas_arlerr@hotmail.com) Received: from hotmail.com ([65.54.247.18]) by omc3-s26.bay6.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 22 Apr 2005 20:54:36 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 22 Apr 2005 20:54:36 -0700 Message-ID: Received: from 61.187.54.10 by by2fd.bay2.hotmail.msn.com with HTTP; Sat, 23 Apr 2005 03:54:36 GMT X-Originating-IP: [61.187.54.10] X-Originating-Email: [jas_arlerr@hotmail.com] X-Sender: jas_arlerr@hotmail.com In-Reply-To: <20050422154140.GW91329@obiwan.tataz.chchile.org> From: "Jas arlerr" To: jeremie@le-hen.org Date: Sat, 23 Apr 2005 03:54:36 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed X-OriginalArrivalTime: 23 Apr 2005 03:54:36.0489 (UTC) FILETIME=[2AA44390:01C547B8] X-Mailman-Approved-At: Sat, 23 Apr 2005 12:09:41 +0000 cc: freebsd-hackers@freebsd.org cc: joerg@britannica.bec.de Subject: Re: Configuration differences for jails 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: Sat, 23 Apr 2005 03:54:36 -0000 >From: Jeremie Le Hen >To: Jas arlerr >CC: joerg@britannica.bec.de, freebsd-hackers@freebsd.org >Subject: Re: Configuration differences for jails >Date: Fri, 22 Apr 2005 17:41:40 +0200 > >Hi, > > > I am not very familar with mount_nullfs, but i think it is _one_ copy with > > _multiple_ references(FIXME).So if we modify something in one jail, the > > same effect will also impose on other jails,even the real machine. Due > > to this problem, readonly mounts may be a good choice. > >Usually, /bin and others are never modified, that's why it may be null >mounted readonly. If you want to be able to write to these directories >from inside the jail, there are two methods : > > - First is to use mount_unionfs(8) which will mount another > directory above the null mounted directory. Note that unionfs > is currently known to be broken, although there are no official > list of known bugs, AFAIK. Having a null mount AND an union > mount over it may perhaps introduce a non-negligible overhead, > I guess. > > - Make each jail have its own world. > > > BUT if we do some things related to the /etc files, such as passwd, ro > > mounts can not deal with this situation because different jails need > > different passwd files for private users. > > So I think this can only be done by making a copy of relevant files but not > > ro mounts. > >Once again, /etc is not intended to be null mounted. It contains >sensitive informations about the host that should not be published in >jails. You will have to use the "distribution" make target from >/usr/src/etc (see my previous email). I see! Thanks for your explanation! regards Jas _________________________________________________________________ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 23 04:49:33 2005 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 1A48C16A4CE for ; Sat, 23 Apr 2005 04:49:33 +0000 (GMT) Received: from hotmail.com (bay2-f37.bay2.hotmail.com [65.54.247.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEEFD43D1D for ; Sat, 23 Apr 2005 04:49:32 +0000 (GMT) (envelope-from jas_arlerr@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 22 Apr 2005 21:49:32 -0700 Message-ID: Received: from 61.187.54.10 by by2fd.bay2.hotmail.msn.com with HTTP; Sat, 23 Apr 2005 04:49:32 GMT X-Originating-IP: [61.187.54.10] X-Originating-Email: [jas_arlerr@hotmail.com] X-Sender: jas_arlerr@hotmail.com In-Reply-To: <426953C5.9080502@elischer.org> From: "Jas arlerr" To: julian@elischer.org, dleimbac@gmail.com Date: Sat, 23 Apr 2005 04:49:32 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed X-OriginalArrivalTime: 23 Apr 2005 04:49:32.0827 (UTC) FILETIME=[D76986B0:01C547BF] X-Mailman-Approved-At: Sat, 23 Apr 2005 12:09:41 +0000 cc: freebsd-hackers@freebsd.org Subject: Re: libthread 1:1 threads 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: Sat, 23 Apr 2005 04:49:33 -0000 > >KSE and 1:1 threading are different things. >One creatres kernel threads on demand and the other keeps the kernel >threads all the time the user thread exists. > >rfork is not the same.. it creates a new process context. that is >what Linux does. >it is also what we did before when running the the linuxthreads >package. > >KSE and 1:1 use a lot of the same kernel changes and entities. >Which one survives will be judged in time. > > >there has been a 1:1 and an M:N library since 5.2 > Yes. As Julian said, libthread is a 1:1 model, while libkse(now libpthread) is an M:N model. KSE is very interesting, it originates from Anderson's Scheduler Activation. But it solved some problems existed in the SA. IMHO, libkse lacks supports for real-time applications (also due to the nonpreemptive kernel feature). BTW, anybody familar with Linux NPTL (1:1 thread model)? Can libthread take some ideas from it? Regards Jas _________________________________________________________________ 与世界各地的朋友进行交流，免费下载 MSN Messenger: http://messenger.msn.com/cn From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 23 05:51:46 2005 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 A3A5C16A4CE for ; Sat, 23 Apr 2005 05:51:46 +0000 (GMT) Received: from orthanc.ca (orthanc.ca [209.89.70.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D17C43D48 for ; Sat, 23 Apr 2005 05:51:46 +0000 (GMT) (envelope-from lyndon@orthanc.ca) Received: from d216-232-211-96.bchsia.telus.net (d216-232-211-96.bchsia.telus.net [216.232.211.96]) (authenticated bits=0) by orthanc.ca (8.13.3/8.13.3) with ESMTP id j3N5pLpq062526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 22 Apr 2005 23:51:23 -0600 (MDT) (envelope-from lyndon@orthanc.ca) Date: Fri, 22 Apr 2005 22:51:21 -0700 From: Lyndon Nerenberg To: FreeBSD Hackers Message-ID: <9328DC9EC69D53548F9E444F@peregrin.orthanc.ca> In-Reply-To: <5bbfe7d4050422150226c6712d@mail.gmail.com> References: <5bbfe7d40504220842578b2d2d@mail.gmail.com> <426953C5.9080502@elischer.org> <5bbfe7d4050422150226c6712d@mail.gmail.com> X-Mailer: Mulberry/4.0.0a7 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-DCC-MessageCare-Metrics: orthanc.ca 1108; Body=1 Fuz1=1 Fuz2=1 X-Spam-Status: No, score=3.9 required=5.0 tests=AWL,BAYES_00, HELO_DYNAMIC_IPADDR,RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=no version=3.0.2 X-Spam-Level: *** X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on orthanc.ca X-Mailman-Approved-At: Sat, 23 Apr 2005 12:09:41 +0000 Subject: Re: libthread 1:1 threads 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: Sat, 23 Apr 2005 05:51:46 -0000 --On 2005-4-22 3:02 PM -0700 David Leimbach wrote: > According to the man page, and plan 9 where rfork originated you can > use it to modify an extant process. In fact you have to set the > RFPROC flag to make a new process or all the changes apply to the > current one. Unfortunately the semantics of FreeBSD rfork() have diverted far enough from the original plan9 rfork() such that you can't consider it as the same call. This makes life miserable for things like running Inferno on FreeBSD. --lyndon From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 23 14:30:23 2005 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 BF95516A4CE for ; Sat, 23 Apr 2005 14:30:23 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4682443D2F for ; Sat, 23 Apr 2005 14:30:09 +0000 (GMT) (envelope-from dleimbac@gmail.com) Received: by zproxy.gmail.com with SMTP id 16so1583920nzp for ; Sat, 23 Apr 2005 07:30:08 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GVg0YaklcDhqcXcT4rIHoKe66vOvsTZHMs+t96VUc0wNGpJHrEVs1A7rQa0r+zwPey5yotjpHAliU9kx7BLBUFuiZnHr7iLUBjwSvZdtpqvFFF5FT2EGjtS2UIN34BnyFV6Uyl2ORLH5rT5qaJx4t1cgHQjIpBuAI6WRdp28vMw= Received: by 10.36.101.17 with SMTP id y17mr366918nzb; Sat, 23 Apr 2005 07:30:08 -0700 (PDT) Received: by 10.36.103.17 with HTTP; Sat, 23 Apr 2005 07:30:08 -0700 (PDT) Message-ID: <5bbfe7d405042307305672e71f@mail.gmail.com> Date: Sat, 23 Apr 2005 07:30:08 -0700 From: David Leimbach To: Lyndon Nerenberg In-Reply-To: <9328DC9EC69D53548F9E444F@peregrin.orthanc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <5bbfe7d40504220842578b2d2d@mail.gmail.com> <426953C5.9080502@elischer.org> <5bbfe7d4050422150226c6712d@mail.gmail.com> <9328DC9EC69D53548F9E444F@peregrin.orthanc.ca> cc: FreeBSD Hackers Subject: Re: libthread 1:1 threads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Leimbach List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2005 14:30:23 -0000 On 4/22/05, Lyndon Nerenberg wrote: > --On 2005-4-22 3:02 PM -0700 David Leimbach wrote: >=20 > > According to the man page, and plan 9 where rfork originated you can > > use it to modify an extant process. In fact you have to set the > > RFPROC flag to make a new process or all the changes apply to the > > current one. >=20 > Unfortunately the semantics of FreeBSD rfork() have diverted far enough > from the original plan9 rfork() such that you can't consider it as the > same call. This makes life miserable for things like running Inferno on > FreeBSD. >=20 Yes the latest Inferno snapshot is currently not so happy on FreeBSD.=20 Charles Forsyth is working on getting it going again though [ I believe he's a vitanuova employee]. Inferno is pretty danged cool. Supporting it on FreeBSD would be a bonus. I've used it to do weird things like export my Mac OS X iDisk over an encrypted connection to a linux box. I know of a University that uses Inferno in their Classics department so they can have a mostly OS agnostic grid. Windows, Linux, Mac OS X, Solaris, Irix and Plan 9 [and I think FreeBSD 4.x series] can all attach to the grid by running Inferno on top. Dave > --lyndon > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 23 14:30:38 2005 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 51E2B16A4CE for ; Sat, 23 Apr 2005 14:30:38 +0000 (GMT) Received: from delight.idiom.com (delight.idiom.com [216.240.32.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24A0143D39 for ; Sat, 23 Apr 2005 14:30:38 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id DB7721F0DB0; Sat, 23 Apr 2005 07:30:37 -0700 (PDT) Received: from [192.168.2.3] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id j3NEUaFP022602; Sat, 23 Apr 2005 07:30:37 -0700 (PDT) (envelope-from julian@elischer.org) Message-ID: <426A5C0C.4050700@elischer.org> Date: Sat, 23 Apr 2005 07:30:36 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050214 X-Accept-Language: en, hu MIME-Version: 1.0 To: Lyndon Nerenberg References: <5bbfe7d40504220842578b2d2d@mail.gmail.com> <426953C5.9080502@elischer.org> <5bbfe7d4050422150226c6712d@mail.gmail.com> <9328DC9EC69D53548F9E444F@peregrin.orthanc.ca> In-Reply-To: <9328DC9EC69D53548F9E444F@peregrin.orthanc.ca> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD Hackers Subject: Re: libthread 1:1 threads 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: Sat, 23 Apr 2005 14:30:38 -0000 Lyndon Nerenberg wrote: > --On 2005-4-22 3:02 PM -0700 David Leimbach wrote: > >> According to the man page, and plan 9 where rfork originated you can >> use it to modify an extant process. In fact you have to set the >> RFPROC flag to make a new process or all the changes apply to the >> current one. > > > Unfortunately the semantics of FreeBSD rfork() have diverted far enough > from the original plan9 rfork() such that you can't consider it as the > same call. This makes life miserable for things like running Inferno on > FreeBSD. patches to fix this would probably be accepted.. as long as other functionality wask kept 'available' > > --lyndon > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 23 20:19:59 2005 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 C75FD16A4CE for ; Sat, 23 Apr 2005 20:19:59 +0000 (GMT) Received: from balodis.pvd.gov.lv (balodis.pvd.gov.lv [159.148.155.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 734EA43D2D for ; Sat, 23 Apr 2005 20:19:59 +0000 (GMT) (envelope-from kl@os.lv) Received: by balodis.pvd.gov.lv (Postfix, from userid 65534) id EE974850F9F; Sat, 23 Apr 2005 23:19:55 +0300 (EEST) Received: from [213.182.201.44] (unknown [213.182.201.44]) by balodis.pvd.gov.lv (Postfix) with ESMTP id 2ED93850F9C for ; Sat, 23 Apr 2005 23:19:49 +0300 (EEST) Message-ID: <426AAE16.2020506@os.lv> Date: Sat, 23 Apr 2005 23:20:38 +0300 From: Casper User-Agent: Mozilla Thunderbird 1.0.2-1.3.2 (X11/20050324) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on mail X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.0.0 Subject: Problem ssh to jail 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: Sat, 23 Apr 2005 20:19:59 -0000 Hi, I don`t know is I write to right mail list, but my problem is with FreeBSD 5.4 RC3 just updated, not relised yet. I wanted to try it to set up jail. I followed instrucion in man and in http://lists.freebsd.org/pipermail/freebsd-doc/2004-June/004463.html but still I can ssh to jail. My set up: ~j/etc/rc.conf sendmail_enable="NONE" inetd_flags="-wW -a 192.168.10.1" network_interfaces="" rpcbind_enable="NO" sshd_enable="YES" inetd_enable="NO" syslogd_flags="-ss" usbd_enable="NO" moused_enable="NO" update_motd="NO" ~j/ssh/sshd_config ListenAddress 192.168.10.1 resol.conf is ok etc. I started with: #!/bin/sh jail /jail/mail mail 192.168.10.1 /bin/sh /etc/rc and: # jls JID IP Address Hostname Path 1 192.168.10.1 mail /jail/mail And host have normal internet ip. somebody have idea what`s wrong or some bug in rc with jail? thanks, Casper P.S. nsswitch.conf bug is still there, when you recompile src with "NO_NIS= true".