From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 9 02:12: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 414AE16A4CE for ; Sun, 9 Jan 2005 02:12:58 +0000 (GMT) Received: from node15.coopprint.com (node15.cooperativeprinting.com [208.4.77.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 43D4B43D49 for ; Sun, 9 Jan 2005 02:12:57 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 86034 invoked by uid 0); 9 Jan 2005 02:11:22 -0000 Received: from unknown (HELO ?192.168.0.5?) (63.231.157.250) by node15.coopprint.com with SMTP; 9 Jan 2005 02:11:22 -0000 Message-ID: <41E0933C.9010405@gamersimpact.com> Date: Sat, 08 Jan 2005 20:13:16 -0600 From: Ryan Sommers User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Malone References: <41DE4F3D.8050509@syskonnect.de> <20050107091004.83732.qmail@web52710.mail.yahoo.com> <20050107101006.GA2553@frontfree.net> <20050108135526.GQ49329@submonkey.net> <20050108202605.GA30807@walton.maths.tcd.ie> In-Reply-To: <20050108202605.GA30807@walton.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Charles Sprickman cc: Ceri Davies cc: tjr@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: Benchmark: NetBSD 2.0 beats FreeBSD 5.3 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, 09 Jan 2005 02:12:58 -0000 David Malone wrote: >On Sat, Jan 08, 2005 at 01:21:14PM -0500, Charles Sprickman wrote: > > >>Any idea what type of impact this patch would have on say, a large qmail >>server that's drowning in context-switches? >> >> > >It will depend on how many processes you have running at any one >moment and how often processes are created/destroyed. From the look >of the graphs, you won't really be able to tell unless there are >significantly more than 1000 processes running at any moment. > > David. > > This could be the case. It's my understanding that Qmail spawns a new qmail-local process (specifically qmail-lspawn exec's it) for each locally delivered message. For any remote message qmail-rspawn forks a qmail-remote process. I don't believe these processes live longer than a single instance. Depending on how his mailboxes are setup this can even result in new processes being spawned. If you're running vpopmail qmail-local will pipe the message to vdelivermail. And if you're running anything like spamassassin from vpopmail (as opposed to from qmail via the QMAIL_QUEUE patch, although that will spawn a spamc of it's own) this could result in another executed process (spamc is spamd's light-weight front-end). Depending on how large and busy this qmail server is, there could definately be a large amount of time spent in process creation and teardown. I'm not sure how much Charles is familiar with the Qmail+vpopmail+spamassassin, if he is using spamassassin. But, one of the "hidden" features of using SpamAssassin and Vpopmail as installed from ports is that spamassassin is called from vpopmail. There is no run-time option (only compile time that is defaulted to on) to disable this. A lot of users don't realize this and will use the QMAIL_QUEUE patch and run spamassassin from it. This can result in scanning every email twice, which can be a costly oversight. -- Ryan Sommers ryans@gamersimpact.com From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 9 07:13: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 1B32416A4CE; Sun, 9 Jan 2005 07:13:17 +0000 (GMT) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C3DC43D2F; Sun, 9 Jan 2005 07:13:16 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.1/8.13.1) with ESMTP id j097D3Uo035931; Sun, 9 Jan 2005 10:13:03 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Sun, 9 Jan 2005 10:13:03 +0300 (MSK) From: Dmitry Morozovsky To: David Malone , scrappy@hub.org In-Reply-To: <20050108202605.GA30807@walton.maths.tcd.ie> Message-ID: <20050109101127.K35832@woozle.rinet.ru> References: <41DE4F3D.8050509@syskonnect.de> <20050107091004.83732.qmail@web52710.mail.yahoo.com> <20050108135526.GQ49329@submonkey.net> <20050108202605.GA30807@walton.maths.tcd.ie> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Charles Sprickman cc: Ceri Davies cc: tjr@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: Benchmark: NetBSD 2.0 beats FreeBSD 5.3 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, 09 Jan 2005 07:13:17 -0000 On Sat, 8 Jan 2005, David Malone wrote: DM> On Sat, Jan 08, 2005 at 01:21:14PM -0500, Charles Sprickman wrote: DM> > Any idea what type of impact this patch would have on say, a large qmail DM> > server that's drowning in context-switches? DM> DM> It will depend on how many processes you have running at any one DM> moment and how often processes are created/destroyed. From the look DM> of the graphs, you won't really be able to tell unless there are DM> significantly more than 1000 processes running at any moment. Then perhaps someone like scrappy@ should test it on one of his hosting planets ;-) Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 9 10:48: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 8C8C716A4CE for ; Sun, 9 Jan 2005 10:48:16 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38D3C43D2F for ; Sun, 9 Jan 2005 10:48:16 +0000 (GMT) (envelope-from mhersant@comcast.net) Received: from [192.168.2.102] (c-24-22-136-36.client.comcast.net[24.22.136.36]) by comcast.net (sccrmhc12) with ESMTP id <2005010910481501200orcave>; Sun, 9 Jan 2005 10:48:15 +0000 Message-ID: <41E10BF2.6050101@comcast.net> Date: Sun, 09 Jan 2005 02:48:18 -0800 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: network trunkin 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, 09 Jan 2005 10:48:16 -0000 Does anyone know if FreeBSD supports trunking? By that I mean spreading network traffic over multiple interfaces to achieve a higher aggregate throughtput. I've used this with Solaris. Thanks. From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 9 12:18: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 1911A16A4CE for ; Sun, 9 Jan 2005 12:18:52 +0000 (GMT) Received: from keylime.silverwraith.com (keylime.silverwraith.com [69.55.228.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAD5843D46 for ; Sun, 9 Jan 2005 12:18:51 +0000 (GMT) (envelope-from lists-freebsd@silverwraith.com) Received: from keylime.silverwraith.com ([69.55.228.10]) by keylime.silverwraith.com with esmtp (Exim 4.41 (FreeBSD)) id 1Cnc24-000Cz1-I6; Sun, 09 Jan 2005 04:18:56 -0800 Received: (from avleen@localhost)j09CIuiI049906; Sun, 9 Jan 2005 04:18:56 -0800 (PST) (envelope-from lists-freebsd@silverwraith.com) X-Authentication-Warning: keylime.silverwraith.com: avleen set sender to lists-freebsd@silverwraith.com using -f Date: Sun, 9 Jan 2005 04:18:56 -0800 From: Avleen Vig To: Matt Message-ID: <20050109121856.GI69719@silverwraith.com> References: <41E10BF2.6050101@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41E10BF2.6050101@comcast.net> User-Agent: Mutt/1.5.6i cc: freebsd-hackers@FreeBSD.org Subject: Re: network trunkin 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, 09 Jan 2005 12:18:52 -0000 On Sun, Jan 09, 2005 at 02:48:18AM -0800, Matt wrote: > Does anyone know if FreeBSD supports trunking? By that I mean spreading > network traffic over multiple interfaces to achieve a higher aggregate I believe you can, with VLANs. Not sure about otherwise. -- Avleen Vig Systems Administrator Personal: www.silverwraith.com Screams are expressions of pure joy & fulfillment when extracted in the proper manner. From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 9 12:24: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 DFA1116A4CE for ; Sun, 9 Jan 2005 12:24:46 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8640F43D31 for ; Sun, 9 Jan 2005 12:24:46 +0000 (GMT) (envelope-from kerochan2@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so349592rnf for ; Sun, 09 Jan 2005 04:24:46 -0800 (PST) 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:references; b=bKRaL5opxCo6Rj7ZUTqRow3YZNFXSXHw9M4g1B7NOsEsh5y3GL31rvzgDABFNaT58o//c3KvvABgrFPnMnw5VkUXJl8IZxEfx8OV9lBH1g/JwLpUML6PFnjQIzXf55DTfeVagv0kF0OYDU4Dh1hPLIC287KUA7U6tKZfsAaoVnU= Received: by 10.38.181.3 with SMTP id d3mr350295rnf; Sun, 09 Jan 2005 04:24:45 -0800 (PST) Received: by 10.38.209.70 with HTTP; Sun, 9 Jan 2005 04:24:45 -0800 (PST) Message-ID: <3b793f1a050109042452407f32@mail.gmail.com> Date: Sun, 9 Jan 2005 13:24:45 +0100 From: Kero-Chan To: freebsd-hackers@freebsd.org In-Reply-To: <20050109101127.K35832@woozle.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable References: <41DE4F3D.8050509@syskonnect.de> <20050107091004.83732.qmail@web52710.mail.yahoo.com> <20050108135526.GQ49329@submonkey.net> <20050108202605.GA30807@walton.maths.tcd.ie> <20050109101127.K35832@woozle.rinet.ru> Subject: Re: Benchmark: NetBSD 2.0 beats FreeBSD 5.3 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Kero-Chan List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jan 2005 12:24:47 -0000 FreeBSD vs NetBSD from an other perpective: http://www.cons.org/cmucl/platforms.html PS.: I like both. --=20 /Varga P=E9ter/ From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 9 13:06: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 B8F1716A541 for ; Sun, 9 Jan 2005 13:06:05 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B27F843D3F for ; Sun, 9 Jan 2005 13:06:00 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id j09D5JgQ001059; Sun, 9 Jan 2005 23:35:20 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Date: Sun, 9 Jan 2005 23:35:18 +1030 User-Agent: KMail/1.7.1 References: <41E10BF2.6050101@comcast.net> <20050109121856.GI69719@silverwraith.com> In-Reply-To: <20050109121856.GI69719@silverwraith.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1212854.XV8hvB2KVC"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501092335.19212.doconnor@gsoft.com.au> X-Spam-Score: -4.6 () IN_REP_TO,PGP_SIGNATURE_2,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Matt Subject: Re: network trunkin 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, 09 Jan 2005 13:06:05 -0000 --nextPart1212854.XV8hvB2KVC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sun, 9 Jan 2005 22:48, Avleen Vig wrote: > On Sun, Jan 09, 2005 at 02:48:18AM -0800, Matt wrote: > > Does anyone know if FreeBSD supports trunking? By that I mean spreading > > network traffic over multiple interfaces to achieve a higher aggregate > > I believe you can, with VLANs. Not sure about otherwise. I though there was a netgraph channel bonding node, but I can't remember it= 's=20 name :( =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1212854.XV8hvB2KVC Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBB4SwP5ZPcIHs/zowRAiTXAJ9r4/W1H0HAY9gVB6vyq6/vpXUJ3gCfV6fp Hcoa9hjl+XAVzO0kqHDdm/I= =uCs7 -----END PGP SIGNATURE----- --nextPart1212854.XV8hvB2KVC-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 9 03:17: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 CA14D16A4CE for ; Sun, 9 Jan 2005 03:17:34 +0000 (GMT) Received: from shared10.hosting.flyingcroc.net (shared10.hosting.flyingcroc.net [207.246.149.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96DB943D1F for ; Sun, 9 Jan 2005 03:17:34 +0000 (GMT) (envelope-from dpk@dpk.net) Received: from shared10.hosting.flyingcroc.net (localhost [127.0.0.1]) j093HYLa088188 for ; Sat, 8 Jan 2005 19:17:34 -0800 (PST) Received: from localhost (dpk@localhost)ESMTP id j093HXj4088185 for ; Sat, 8 Jan 2005 19:17:34 -0800 (PST) X-Authentication-Warning: shared10.hosting.flyingcroc.net: dpk owned process doing -bs Date: Sat, 8 Jan 2005 19:17:33 -0800 (PST) From: dpk X-X-Sender: dpk@shared10.hosting.flyingcroc.net To: hackers@freebsd.org Message-ID: <20050108191218.L42157@shared10.hosting.flyingcroc.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Sun, 09 Jan 2005 13:58:28 +0000 Subject: Wondering about a patch (DELL ERA/RAC) 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, 09 Jan 2005 03:17:34 -0000 http://lists.freebsd.org/pipermail/freebsd-hackers/2003-August/002733.html Will this patch be making its way in to the kernel? The Dells are still shipping with cards that have no drivers (this pciconf -v -l is from a 1750): none0@pci0:8:0: class=0xff0000 card=0x000c1028 chip=0x000c1028 rev=0x00 hdr=0x00 vendor = 'Dell Computer Corporation' device = 'Embedded Systems Management Device 4' none1@pci0:8:1: class=0xff0000 card=0x00081028 chip=0x00081028 rev=0x00 hdr=0x00 vendor = 'Dell Computer Corporation' device = 'PowerEdge 3/Di Expandable RAID Controller' none2@pci0:8:2: class=0xff0000 card=0x00091028 chip=0x00091028 rev=0x00 hdr=0x00 vendor = 'Dell Computer Corporation' It'd be most excellent to be able to tweak RAC options via a serial port. Would card=0x000c1028 also be something we could(should?) access via sio? From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 9 14:04: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 7A26F16A4CE for ; Sun, 9 Jan 2005 14:04:42 +0000 (GMT) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DB4643D2F for ; Sun, 9 Jan 2005 14:04:41 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received-SPF: pass (mp2.macomnet.net: domain of maxim@macomnet.ru designates 127.0.0.1 as permitted sender) receiver=mp2.macomnet.net; client_ip=127.0.0.1; envelope-from=maxim@macomnet.ru; Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.12.11/8.12.11) with ESMTP id j09E4W4p038766; Sun, 9 Jan 2005 17:04:33 +0300 (MSK) (envelope-from maxim@macomnet.ru) Date: Sun, 9 Jan 2005 17:04:32 +0300 (MSK) From: Maxim Konovalov To: "Daniel O'Connor" In-Reply-To: <200501092335.19212.doconnor@gsoft.com.au> Message-ID: <20050109170419.X38764@mp2.macomnet.net> References: <41E10BF2.6050101@comcast.net> <20050109121856.GI69719@silverwraith.com> <200501092335.19212.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SpamTest-Info: Profile: Formal (192/041231) X-SpamTest-Info: Profile: Detect Hard (4/030526) X-SpamTest-Info: Profile: SysLog X-SpamTest-Info: Profile: Marking - Keywords (2/030321) X-SpamTest-Status: Not detected X-SpamTest-Version: SMTP-Filter Version 2.0.0 [0124], SpamtestISP/Release cc: freebsd-hackers@freebsd.org cc: Matt Subject: Re: network trunkin 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, 09 Jan 2005 14:04:42 -0000 On Sun, 9 Jan 2005, 23:35+1030, Daniel O'Connor wrote: > On Sun, 9 Jan 2005 22:48, Avleen Vig wrote: > > On Sun, Jan 09, 2005 at 02:48:18AM -0800, Matt wrote: > > > Does anyone know if FreeBSD supports trunking? By that I mean spreading > > > network traffic over multiple interfaces to achieve a higher aggregate > > > > I believe you can, with VLANs. Not sure about otherwise. > > I though there was a netgraph channel bonding node, but I can't remember it's > name :( ng_fec(4) -- Maxim Konovalov From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 9 20:24: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 32BDF16A4CE for ; Sun, 9 Jan 2005 20:24:14 +0000 (GMT) Received: from keylime.silverwraith.com (keylime.silverwraith.com [69.55.228.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0914243D45 for ; Sun, 9 Jan 2005 20:24:14 +0000 (GMT) (envelope-from lists-freebsd@silverwraith.com) Received: from keylime.silverwraith.com ([69.55.228.10]) by keylime.silverwraith.com with esmtp (Exim 4.41 (FreeBSD)) id 1Cnjbk-000PyY-Bf; Sun, 09 Jan 2005 12:24:16 -0800 Received: (from avleen@localhost)j09KOBsi099111; Sun, 9 Jan 2005 12:24:11 -0800 (PST) (envelope-from lists-freebsd@silverwraith.com) X-Authentication-Warning: keylime.silverwraith.com: avleen set sender to lists-freebsd@silverwraith.com using -f Date: Sun, 9 Jan 2005 12:24:11 -0800 From: Avleen Vig To: Maxim Konovalov Message-ID: <20050109202411.GJ69719@silverwraith.com> References: <41E10BF2.6050101@comcast.net> <20050109121856.GI69719@silverwraith.com> <200501092335.19212.doconnor@gsoft.com.au> <20050109170419.X38764@mp2.macomnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050109170419.X38764@mp2.macomnet.net> User-Agent: Mutt/1.5.6i cc: Matt cc: freebsd-hackers@freebsd.org Subject: Re: network trunkin 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, 09 Jan 2005 20:24:14 -0000 > > I though there was a netgraph channel bonding node, but I can't remember it's > > name :( > > ng_fec(4) Is that a 5.x-ism? From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 9 22:03: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 535B616A4CE for ; Sun, 9 Jan 2005 22:03:26 +0000 (GMT) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55BFB43D31 for ; Sun, 9 Jan 2005 22:03:25 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received-SPF: pass (mp2.macomnet.net: domain of maxim@macomnet.ru designates 127.0.0.1 as permitted sender) receiver=mp2.macomnet.net; client_ip=127.0.0.1; envelope-from=maxim@macomnet.ru; Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.12.11/8.12.11) with ESMTP id j09M38qi045581; Mon, 10 Jan 2005 01:03:09 +0300 (MSK) (envelope-from maxim@macomnet.ru) Date: Mon, 10 Jan 2005 01:03:08 +0300 (MSK) From: Maxim Konovalov To: Avleen Vig In-Reply-To: <20050109202411.GJ69719@silverwraith.com> Message-ID: <20050110010149.P45532@mp2.macomnet.net> References: <41E10BF2.6050101@comcast.net> <20050109121856.GI69719@silverwraith.com> <20050109170419.X38764@mp2.macomnet.net> <20050109202411.GJ69719@silverwraith.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SpamTest-Info: Profile: Formal (192/041231) X-SpamTest-Info: Profile: Detect Hard (4/030526) X-SpamTest-Info: Profile: SysLog X-SpamTest-Info: Profile: Marking - Keywords (2/030321) X-SpamTest-Status: Not detected X-SpamTest-Version: SMTP-Filter Version 2.0.0 [0124], SpamtestISP/Release cc: Matt cc: freebsd-hackers@freebsd.org Subject: Re: network trunkin 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, 09 Jan 2005 22:03:26 -0000 On Sun, 9 Jan 2005, 12:24-0800, Avleen Vig wrote: > > > I though there was a netgraph channel bonding node, but I can't > > > remember it's name :( > > > > ng_fec(4) > > Is that a 5.x-ism? The man page, yes. $ locate ng_fec | grep ^/usr/src /usr/src/sys/netgraph/ng_fec.c /usr/src/sys/netgraph/ng_fec.h $ uname -r 4.10-STABLE -- Maxim Konovalov From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 10 05:25: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 2DB0E16A4CF; Mon, 10 Jan 2005 05:25:25 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5BBC43D1D; Mon, 10 Jan 2005 05:25:24 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id B3FE7652FE; Mon, 10 Jan 2005 05:25:23 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 57763-04-2; Mon, 10 Jan 2005 05:25:23 +0000 (GMT) Received: from empiric.dek.spc.org (unknown [213.210.24.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id AD752651EB; Mon, 10 Jan 2005 05:25:19 +0000 (GMT) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id A0C566530; Mon, 10 Jan 2005 05:25:26 +0000 (GMT) Date: Mon, 10 Jan 2005 05:25:26 +0000 From: Bruce M Simpson To: Ivan Voras Message-ID: <20050110052526.GB709@empiric.icir.org> References: <41E06011.4050501@fer.hr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline In-Reply-To: <41E06011.4050501@fer.hr> cc: hackers@freebsd.org cc: Robert Watson Subject: Re: Raw sockets 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: Mon, 10 Jan 2005 05:25:25 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 08, 2005 at 11:34:57PM +0100, Ivan Voras wrote: > I use it in this code: >=20 > /* get interface name by index */ =2E.. Please consider using if_nameindex() or if_nametoindex(), which will retrie= ve the getifaddrs() list for you and considerably simplify the code fragment you've provided. These are specified by RFC 2553 and are used in many places within the XORP open source router. Regards, BMS --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: '' iD8DBQFB4hHGueUpAYYNtTsRAgniAJ0YzZlrx6HG0g1nuxbv3Ycsdo5brgCfXFQZ zUj6J2TsFMoejdhrf+bGH0A= =hsBH -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 10 05:28: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 6484616A4CE for ; Mon, 10 Jan 2005 05:28:44 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EA0543D3F for ; Mon, 10 Jan 2005 05:28:44 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 47569652EC; Mon, 10 Jan 2005 05:28:43 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 57955-03; Mon, 10 Jan 2005 05:28:42 +0000 (GMT) Received: from empiric.dek.spc.org (unknown [213.210.24.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 67B4D651EB; Mon, 10 Jan 2005 05:28:42 +0000 (GMT) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id 51BA36530; Mon, 10 Jan 2005 05:28:49 +0000 (GMT) Date: Mon, 10 Jan 2005 05:28:49 +0000 From: Bruce M Simpson To: dpk Message-ID: <20050110052849.GC709@empiric.icir.org> References: <20050108191218.L42157@shared10.hosting.flyingcroc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050108191218.L42157@shared10.hosting.flyingcroc.net> cc: hackers@freebsd.org Subject: Re: Wondering about a patch (DELL ERA/RAC) 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, 10 Jan 2005 05:28:44 -0000 On Sat, Jan 08, 2005 at 07:17:33PM -0800, dpk wrote: > http://lists.freebsd.org/pipermail/freebsd-hackers/2003-August/002733.html > Will this patch be making its way in to the kernel? The Dells are still > shipping with cards that have no drivers (this pciconf -v -l is from a > 1750): The patch would need to be rewritten to use the puc driver shim or possibly even Marcel's uart stuff, but it's certainly possible. The patch as it stands is applicable to NetBSD. uart would probably be a cleaner place to put it. Regards, BMS From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 10 05:45: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 04E9016A4CE for ; Mon, 10 Jan 2005 05:45:58 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F92943D48 for ; Mon, 10 Jan 2005 05:45:57 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 70735653E8; Mon, 10 Jan 2005 05:45:55 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 58351-02-2; Mon, 10 Jan 2005 05:45:55 +0000 (GMT) Received: from empiric.dek.spc.org (unknown [213.210.24.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id AD73D652FE; Mon, 10 Jan 2005 05:45:54 +0000 (GMT) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id A96F46530; Mon, 10 Jan 2005 05:46:01 +0000 (GMT) Date: Mon, 10 Jan 2005 05:46:01 +0000 From: Bruce M Simpson To: dpk Message-ID: <20050110054601.GF709@empiric.icir.org> References: <20050108191218.L42157@shared10.hosting.flyingcroc.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="R+My9LyyhiUvIEro" Content-Disposition: inline In-Reply-To: <20050108191218.L42157@shared10.hosting.flyingcroc.net> cc: hackers@freebsd.org Subject: Re: Wondering about a patch (DELL ERA/RAC) 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, 10 Jan 2005 05:45:58 -0000 --R+My9LyyhiUvIEro Content-Type: multipart/mixed; boundary="ZfOjI3PrQbgiZnxM" Content-Disposition: inline --ZfOjI3PrQbgiZnxM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Jan 08, 2005 at 07:17:33PM -0800, dpk wrote: > Will this patch be making its way in to the kernel? The Dells are still > shipping with cards that have no drivers (this pciconf -v -l is from a > 1750): Please try the attached patch. You'll need to have these drivers statically compiled into your kernel (with the patch applied) device sio device puc I don't have one of these devices so I'm unable to test. Hope this helps, BMS --ZfOjI3PrQbgiZnxM Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="pucdata-drac.patch" Content-Transfer-Encoding: quoted-printable Index: pucdata.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/dev/puc/pucdata.c,v retrieving revision 1.45 diff -u -p -u -r1.45 pucdata.c --- pucdata.c 17 May 2004 12:57:30 -0000 1.45 +++ pucdata.c 10 Jan 2005 05:43:47 -0000 @@ -1203,5 +1203,14 @@ const struct puc_device_description puc_ }, }, =20 + /* Dell RAC Serial PPP Link */ + { "Dell RAC Serial PPP Link", + { 0x1028, 0x0008, 0, 0 }, + { 0xffff, 0xffff, 0, 0 }, + { + { PUC_PORT_TYPE_COM, 0x14, 0x00, DEFAULT_RCLK * 128 }, + }, + }, + { 0 } }; --ZfOjI3PrQbgiZnxM-- --R+My9LyyhiUvIEro Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: '' iD8DBQFB4haZueUpAYYNtTsRAo0LAJ4l8cVYpHKQ9e5gXVRmPbRrSCqKUgCgi02D FZNflsInLH86SeOAgRI0SCE= =GYMa -----END PGP SIGNATURE----- --R+My9LyyhiUvIEro-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 10 06:02: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 90C9816A4CE for ; Mon, 10 Jan 2005 06:02:43 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AF3C43D3F for ; Mon, 10 Jan 2005 06:02:43 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 4C85C651EE; Mon, 10 Jan 2005 06:02:42 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 58197-06; Mon, 10 Jan 2005 06:02:41 +0000 (GMT) Received: from empiric.dek.spc.org (unknown [213.210.24.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 78C3D651EB; Mon, 10 Jan 2005 06:02:41 +0000 (GMT) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id A7E516530; Mon, 10 Jan 2005 06:02:48 +0000 (GMT) Date: Mon, 10 Jan 2005 06:02:48 +0000 From: Bruce M Simpson To: Matt Message-ID: <20050110060248.GH709@empiric.icir.org> Mail-Followup-To: Matt , freebsd-hackers@FreeBSD.org References: <41E10BF2.6050101@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41E10BF2.6050101@comcast.net> cc: freebsd-hackers@FreeBSD.org Subject: Re: network trunkin 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, 10 Jan 2005 06:02:43 -0000 On Sun, Jan 09, 2005 at 02:48:18AM -0800, Matt wrote: > Does anyone know if FreeBSD supports trunking? By that I mean spreading > network traffic over multiple interfaces to achieve a higher aggregate > throughtput. I've used this with Solaris. Thanks. Were you thinking of any particular Ethernet trunking standard? I assume you're referring to Ethernet. ng_fec(4) is a Netgraph node which suports Fast EtherChannel, which is a Cisco-ism. It may not be what you want. The IEEE standard for Ethernet trunking is 802.3ad Link Aggregation (aka LACP in Cisco-ese). As far as I know we don't currently support 802.3ad. You might also wish to investigate ng_one2many(4), which is a bit more simplistic. Regards, BMS From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 10 06:23: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 A55AB16A4CE for ; Mon, 10 Jan 2005 06:23:29 +0000 (GMT) Received: from angui.sh (angui.sh [216.171.167.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DD3F43D3F for ; Mon, 10 Jan 2005 06:23:29 +0000 (GMT) (envelope-from wfroning@angui.sh) Received: from angui.sh (localhost [127.0.0.1]) by angui.sh (8.12.9p2/8.12.8) with ESMTP id j0A6NS4Q030774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 9 Jan 2005 22:23:28 -0800 (PST) (envelope-from wfroning@angui.sh) Received: from localhost (wfroning@localhost) by angui.sh (8.12.9p2/8.12.8/Submit) with ESMTP id j0A6NRft030771; Sun, 9 Jan 2005 22:23:27 -0800 (PST) (envelope-from wfroning@angui.sh) Date: Sun, 9 Jan 2005 22:23:27 -0800 (PST) From: Will Froning To: Matt In-Reply-To: <20050110060248.GH709@empiric.icir.org> Message-ID: <20050109222004.D98568@angui.sh> References: <41E10BF2.6050101@comcast.net> <20050110060248.GH709@empiric.icir.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.39 cc: freebsd-hackers@freebsd.org Subject: Re: network trunkin 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, 10 Jan 2005 06:23:29 -0000 =>On Sun, Jan 09, 2005 at 02:48:18AM -0800, Matt wrote: =>> Does anyone know if FreeBSD supports trunking? By that I mean spreading =>> network traffic over multiple interfaces to achieve a higher aggregate =>> throughtput. I've used this with Solaris. Thanks. Here is a post that gives some directions on how to do it. Sadly I don't think this guy's specific problem was fixed (bonding and bridging), but he gave 2 different ways to set up bonding. http://lists.freebsd.org/pipermail/freebsd-hackers/2004-September/008195.html Will -- Will Froning Unix Sys. Admin. wfroning@angui.sh From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 10 10:26: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 EC1D816A4CE for ; Mon, 10 Jan 2005 10:26:21 +0000 (GMT) Received: from imo-d06.mx.aol.com (imo-d06.mx.aol.com [205.188.157.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8943343D2F for ; Mon, 10 Jan 2005 10:26:21 +0000 (GMT) (envelope-from Ktilford@aol.com) Received: from Ktilford@aol.com by imo-d06.mx.aol.com (mail_out_v37_r3.8.) id n.fd.aa2876a (15888) for ; Mon, 10 Jan 2005 05:26:19 -0500 (EST) Received: from [192.168.0.196] (ip68-103-230-65.ks.ok.cox.net [68.103.230.65]) by air-id08.mx.aol.com (v104.17) with ESMTP id MAILINID83-3e1041e2584a326; Mon, 10 Jan 2005 05:26:19 -0500 Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <105F3A94-62F2-11D9-A5C6-000502BD9BF8@aol.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-hackers@freebsd.org From: Kris Tilford Date: Mon, 10 Jan 2005 04:26:18 -0600 X-Mailer: Apple Mail (2.619) X-AOL-IP: 68.103.230.65 X-Mailman-Approved-At: Mon, 10 Jan 2005 12:57:31 +0000 Subject: ASIX AX88172 & OS X? 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, 10 Jan 2005 10:26:22 -0000 I saw you wrote a FreeBSD driver for the ASIX AX88172 ethernet/usb chipset. I'm using OS X Panther and would like to be able to enable Ethernet-over-USB. The device I have is a Belkin USB 2.0 Dockstation with an Ethernet-to-USB adpater based on the AX88172 chipset. I'm using some Apple developer USB kexts that have an extension that seems to start to load and then disconnects, it's called AppleUSBCDCEthernet.kext. I'm not a programmer, so I'm kinda out of my league, but I think I need an extension to enable this completely. Probably this extension would need to explicitly name my device by vendor ID# & Product ID# in the info.plist? (these are0x0B95 & 0x1720) I assume your FreeBSD driver could be easily ported to OS X, I could probably figure out how to do it, but I thought I'd ask you for advice since I'm 100% sure you know lots more than I. Any advice would be appreciated, Thanks! Kris Tilford - Topeka, Kansas From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 10 12:09: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 A28C116A4CE; Mon, 10 Jan 2005 12:09:43 +0000 (GMT) Received: from www.portaone.com (support.portaone.com [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEF8643D31; Mon, 10 Jan 2005 12:09:42 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.0.128] (sobohome.portaone.com [193.28.87.24]) (authenticated bits=0) by www.portaone.com (8.12.11/8.12.11) with ESMTP id j0AC9YGq058850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jan 2005 13:09:39 +0100 (CET) (envelope-from sobomax@portaone.com) Message-ID: <41E27076.8080904@portaone.com> Date: Mon, 10 Jan 2005 14:09:26 +0200 From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org, current@freebsd.org Content-Type: multipart/mixed; boundary="------------040104060604090102080808" X-Virus-Scanned: ClamAV 0.80/589/Wed Nov 17 13:38:41 2004 clamav-milter version 0.80j on www.portaone.com X-Virus-Status: Clean X-Mailman-Approved-At: Mon, 10 Jan 2005 12:57:31 +0000 Subject: Attempt to invoke connect(2) on already connected unix domaindatagram socket fails with ECONNRESET 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, 10 Jan 2005 12:09:43 -0000 This is a multi-part message in MIME format. --------------040104060604090102080808 Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Folks, I've discovered very strange behaviour of the connect(2) system call when it's called on already connected unix domain datagram socket. In this case connect(2) fails with ECONNRESET, which is weird. ECONNRESET is not even listed among possible return values of connect(2). I've confirmed this behaviour at 4.10 and 5.3 systems. Linux doesn't exhibit this (mis?)behaviour. As long as I can tell, this behaviour contradicts documentation, connect(2) manpage says: Generally, stream sockets may successfully connect() only once; datagram sockets may use connect() multiple times to change their association. Attached please find small test program which illustrates the problem. It forks itsels at the start, child becomes a server, while parent a client. After each transaction server closes unix domain socket and opens its again, while the client attempts to re-connect() to that unix domain socket using already created socket object. This mimics real-world scenario in which I've encountered the problem. In this scenarion, there are two distinct processes communicating using unix domain socket. Client uses connect() on already connected socket object for performance reasons to avoid calling socket(2) for each transaction. Everything works just fine until server is restarted. After that any attempts to send command from the client to the server fails with ECONNRESET until the client is restarted as well. -Maxim --------------040104060604090102080808 Content-Type: text/plain; name="socket_test.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="socket_test.c" #include #include #include #include #include #include #include #include #include #include #include #define UDS_NAME "/tmp/uds_test.sock" #define sstosa(ss) ((struct sockaddr *)(ss)) static pid_t pid_kill; void prepare_ifsun(struct sockaddr_un *ifsun) { static char ch = '1' * 2; memset(ifsun, '\0', sizeof(*ifsun)); #if !defined(__linux__) && !defined(__solaris__) ifsun->sun_len = strlen(UDS_NAME); #endif ifsun->sun_family = AF_LOCAL; strcpy(ifsun->sun_path, UDS_NAME); //ifsun->sun_path[ifsun->sun_len - 1] = ch / 2; ch++; } int create_uds_server(void) { struct sockaddr_un ifsun; int sock; prepare_ifsun(&ifsun); unlink(ifsun.sun_path); sock = socket(PF_LOCAL, SOCK_DGRAM, 0); if (sock == -1) err(1, "server: can't create socket"); setsockopt(sock, SOL_SOCKET, SO_REUSEADDR, &sock, sizeof(sock)); if (bind(sock, sstosa(&ifsun), sizeof(ifsun)) < 0) err(1, "server: can't bind to a socket"); return sock; } void connect_uds_server(int sock) { struct sockaddr_un ifsun; prepare_ifsun(&ifsun); if (connect(sock, sstosa(&ifsun), sizeof(ifsun)) < 0) err(1, "client: can't connect to a socket"); } static void cleanup(void) { kill(pid_kill, SIGKILL); } int main() { int sock, len; pid_t pid; pid = fork(); if (pid < 0) err(1, "can't fork"); pid_kill = getpid(); if (pid != 0) { /* Parent */ pid_kill = pid; atexit(cleanup); sock = socket(PF_LOCAL, SOCK_DGRAM, 0); if (sock < 0) err(1, "client: can't create socket"); for (;;) { sleep(1); connect_uds_server(sock); len = write(sock, &pid, sizeof(pid)); if (len < 0) err(1, "client: can't write to a socket"); printf("client: wrote %d bytes to the socket\n", len); } } else { /* Child */ atexit(cleanup); for (;;) { sock = create_uds_server(); len = recvfrom(sock, &pid, sizeof(pid), 0, NULL, NULL); if (len < 0) err(1, "server: can't read from a socket"); printf("server: read %d bytes from the socket\n", len); close(sock); } } exit (1); } --------------040104060604090102080808-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 10 17:04: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 0CFF316A4CE for ; Mon, 10 Jan 2005 17:04:21 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BC6243D1F for ; Mon, 10 Jan 2005 17:04:20 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id B2BD265218; Mon, 10 Jan 2005 17:04:18 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 65997-04-3; Mon, 10 Jan 2005 17:04:18 +0000 (GMT) Received: from empiric.dek.spc.org (unknown [213.210.24.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id A7E2365211; Mon, 10 Jan 2005 17:04:17 +0000 (GMT) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id BC2EF64C3; Mon, 10 Jan 2005 17:04:18 +0000 (GMT) Date: Mon, 10 Jan 2005 17:04:18 +0000 From: Bruce M Simpson To: Kris Tilford Message-ID: <20050110170418.GA711@empiric.icir.org> Mail-Followup-To: Kris Tilford , freebsd-hackers@freebsd.org References: <105F3A94-62F2-11D9-A5C6-000502BD9BF8@aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <105F3A94-62F2-11D9-A5C6-000502BD9BF8@aol.com> cc: freebsd-hackers@freebsd.org Subject: Re: ASIX AX88172 & OS X? 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, 10 Jan 2005 17:04:21 -0000 On Mon, Jan 10, 2005 at 04:26:18AM -0600, Kris Tilford wrote: > I assume your FreeBSD driver could be easily ported to OS X, I could=20 [snip] Nope. MacOS X and FreeBSD are completely different in this area. It uses a driver API known as IOKit. Your best bet is to look for driver support =66rom the manufacturer. Regards, BMS From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 10 17: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 2F63216A4CE for ; Mon, 10 Jan 2005 17:13:09 +0000 (GMT) Received: from meisai.numachi.com (meisai.numachi.com [198.175.254.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 22B1E43D45 for ; Mon, 10 Jan 2005 17:13:08 +0000 (GMT) (envelope-from reichert@numachi.com) Received: (qmail 28539 invoked from network); 10 Jan 2005 17:13:07 -0000 Received: from natto.numachi.com (198.175.254.216) by meisai.numachi.com with SMTP; 10 Jan 2005 17:13:07 -0000 Received: (qmail 95814 invoked by uid 1001); 10 Jan 2005 17:13:07 -0000 Date: Mon, 10 Jan 2005 12:13:07 -0500 From: Brian Reichert To: hackers@freebsd.org Message-ID: <20050110171307.GA95568@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: firewire not probing? 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, 10 Jan 2005 17:13:09 -0000 I did some googling on these symtptoms, but couldn't find a good hit. Under FreeBSD 5.3-RELEASE, I have a firewire card, that the kernel finds, then ignores. fwohci0: irq 9 at device 0.0 on pci2 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 08:00:28:64:10:00:12:eb fwohci0: invalid speed 7 (fixed to 3). fwohci0: Phy 1394a available S800, 3 ports. fwohci0: Link S800, max_rec 4096 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 0a:00:28:00:12:eb fwe0: Ethernet address: 0a:00:28:00:12:eb fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode fwohci0: SID Error fwohci0: unrecoverable error fwohci0: phy int But, ifconfig doesn't reveal fwe0, pciconf doesn't reveal the card, and plugging in a firewire device doesn't plumb a SCSI device. I can't infer from the dmesg output what, per se, is wrong. None of those trailing diagnostic messages are, unto themselves, a showstopper. Does anyone have a suggestion as to how I can move forward on this? I can make available a full dmesg, if that woudl help anyone... -- Brian Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 11 04:41: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 86DEF16A4CE; Tue, 11 Jan 2005 04:41:20 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0228C43D55; Tue, 11 Jan 2005 04:41:20 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j0B4imcU042717; Mon, 10 Jan 2005 21:44:48 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41E3588B.2060309@freebsd.org> Date: Mon, 10 Jan 2005 21:39:39 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org References: <41DA5C4D.1060606@freebsd.org> In-Reply-To: <41DA5C4D.1060606@freebsd.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: current@freebsd.org Subject: Reminder: Call for FreeBSD status reports X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: monthly@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 04:41:20 -0000 All, This is a reminder that FreeBSD status report submissions are due by Jan 15. So far there have been a lot of good submissions, so keep them coming! Scott Scott Long wrote: > All, > > It's time again for the bi-monthly status reports. The July-Oct 2004 > status reports were preempted by the 5.3 release, so this one is open > for anything that has happened since June. As always, submissions > having to do with FreeBSD development, documentation, organized events, > etc, are welcome and highly encouraged. Submissions are due by Jan 15 > to monthly@freebsd.org > > There are also a couple of changes to announce. First is that Tom > Rhodes and Max Laier have volunteered to help run the status reports and > keep them more timely. Many thanks to Tom and Max for offering to > help. Second is that a couple of new attributes have been added to the > XML thanks to Max. The first is a project category attribute that will > enable us to group the submissions into categories and render the full > report with these categories for easier viewing. You can choose to use > whatever category tag fits your report best, or omit it entirely and let > us take care of it. The category mapping is listed below. Feel free to > suggest additional categories. > > proj - Projects (non-specific) > docs - Documentation > kern - Kernel > arch - Architectures > ports - Ports > vendor - Vendor / 3rd party software > misc - Miscellaneous > > The second new attribute lets you lists tasks for your project that > others can help with. An example is provided in the template under the > and tags. > > The template is available at > http://www.freebsd.org/news/status/report-sample.xml. I've just > committed the updated version with the new tags, so it might take a few > hours for it to reach the website for downloading. > > Submissions are due on Jan 15. Thanks a lot, and we are looking for a > big turn-out. > > Scott From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 10 14:59: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 6C7EC16A4CE; Mon, 10 Jan 2005 14:59:12 +0000 (GMT) Received: from www.portaone.com (web.portaone.com [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC94143D2F; Mon, 10 Jan 2005 14:59:11 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.1.26] (SIRIUS-ats227-UTC.ukrtel.net [195.5.25.154]) (authenticated bits=0) by www.portaone.com (8.12.11/8.12.11) with ESMTP id j0AEx7VT079060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jan 2005 15:59:09 +0100 (CET) (envelope-from sobomax@portaone.com) Message-ID: <41E29838.9020805@portaone.com> Date: Mon, 10 Jan 2005 16:59:04 +0200 From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org References: <41E27076.8080904@portaone.com> In-Reply-To: <41E27076.8080904@portaone.com> Content-Type: multipart/mixed; boundary="------------040309000406060207060002" X-Virus-Scanned: ClamAV 0.80/589/Wed Nov 17 13:38:41 2004 clamav-milter version 0.80j on www.portaone.com X-Virus-Status: Clean X-Mailman-Approved-At: Tue, 11 Jan 2005 13:45:50 +0000 cc: current@freebsd.org Subject: Re: Attempt to invoke connect(2) on already connected unix domain datagram socket fails with ECONNRESET 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, 10 Jan 2005 14:59:12 -0000 This is a multi-part message in MIME format. --------------040309000406060207060002 Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Further investigation revealed that the said problem only happens when the program is trying to re-connect() socket object which previously has been connected to the unix domain socket closed on the server side at the time when the second connect() is called. Attached please find more simple testcase. -Maxim Maxim Sobolev wrote: > Folks, > > I've discovered very strange behaviour of the connect(2) system call > when it's called on already connected unix domain datagram socket. In > this case connect(2) fails with ECONNRESET, which is weird. ECONNRESET > is not even listed among possible return values of connect(2). I've > confirmed this behaviour at 4.10 and 5.3 systems. Linux doesn't exhibit > this (mis?)behaviour. > > As long as I can tell, this behaviour contradicts documentation, > connect(2) manpage says: > > Generally, stream sockets may successfully connect() only > once; datagram sockets may use connect() multiple times to change > their association. > > Attached please find small test program which illustrates the problem. > It forks itsels at the start, child becomes a server, while parent a > client. After each transaction server closes unix domain socket and > opens its again, while the client attempts to re-connect() to that unix > domain socket using already created socket object. > > This mimics real-world scenario in which I've encountered the problem. > In this scenarion, there are two distinct processes communicating using > unix domain socket. Client uses connect() on already connected socket > object for performance reasons to avoid calling socket(2) for each > transaction. Everything works just fine until server is restarted. After > that any attempts to send command from the client to the server fails > with ECONNRESET until the client is restarted as well. > > -Maxim --------------040309000406060207060002 Content-Type: text/plain; name="socket_test1.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="socket_test1.c" #include #include #include #include #include #include #include #include #include #include #include #include #define UDS_NAME1 "/tmp/uds_test.sock1" #define UDS_NAME2 "/tmp/uds_test.sock2" #define sstosa(ss) ((struct sockaddr *)(ss)) void prepare_ifsun(struct sockaddr_un *ifsun, const char *path) { memset(ifsun, '\0', sizeof(*ifsun)); #if !defined(__linux__) && !defined(__solaris__) ifsun->sun_len = strlen(path); #endif ifsun->sun_family = AF_LOCAL; strcpy(ifsun->sun_path, path); } int create_uds_server(const char *path) { struct sockaddr_un ifsun; int sock; prepare_ifsun(&ifsun, path); unlink(ifsun.sun_path); sock = socket(PF_LOCAL, SOCK_DGRAM, 0); if (sock == -1) err(1, "server: can't create socket"); setsockopt(sock, SOL_SOCKET, SO_REUSEADDR, &sock, sizeof(sock)); if (bind(sock, sstosa(&ifsun), sizeof(ifsun)) < 0) err(1, "server: can't bind to a socket"); return sock; } void connect_uds_server(int sock, const char *path) { struct sockaddr_un ifsun; int e; prepare_ifsun(&ifsun, path); e = connect(sock, sstosa(&ifsun), sizeof(ifsun)); if (e < 0) err(1, "client: can't connect to a socket"); } int main() { int s_sock1, s_sock2, c_sock; s_sock1 = create_uds_server(UDS_NAME1); s_sock2 = create_uds_server(UDS_NAME2); c_sock = socket(PF_LOCAL, SOCK_DGRAM, 0); if (c_sock < 0) err(1, "client: can't create socket"); connect_uds_server(c_sock, UDS_NAME1); close(s_sock1); connect_uds_server(c_sock, UDS_NAME2); exit (0); } --------------040309000406060207060002-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 10 16:46: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 0C8DD16A4CE; Mon, 10 Jan 2005 16:46:24 +0000 (GMT) Received: from www.portaone.com (web.portaone.com [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5F0A43D45; Mon, 10 Jan 2005 16:46:22 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.1.26] (SIRIUS-ats227-UTC.ukrtel.net [195.5.25.154]) (authenticated bits=0) by www.portaone.com (8.12.11/8.12.11) with ESMTP id j0AGkJ03093388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jan 2005 17:46:20 +0100 (CET) (envelope-from sobomax@portaone.com) Message-ID: <41E2B157.3080306@portaone.com> Date: Mon, 10 Jan 2005 18:46:15 +0200 From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@FreeBSD.ORG References: <41E27076.8080904@portaone.com> <41E29838.9020805@portaone.com> In-Reply-To: <41E29838.9020805@portaone.com> Content-Type: multipart/mixed; boundary="------------070202070809080104090402" X-Virus-Scanned: ClamAV 0.80/589/Wed Nov 17 13:38:41 2004 clamav-milter version 0.80j on www.portaone.com X-Virus-Status: Clean X-Mailman-Approved-At: Tue, 11 Jan 2005 13:45:50 +0000 cc: current@FreeBSD.ORG Subject: Re: Attempt to invoke connect(2) on already connected unix domain datagram socket fails with ECONNRESET 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, 10 Jan 2005 16:46:24 -0000 This is a multi-part message in MIME format. --------------070202070809080104090402 Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Maxim Sobolev wrote: > Further investigation revealed that the said problem only happens when > the program is trying to re-connect() socket object which previously has > been connected to the unix domain socket closed on the server side at > the time when the second connect() is called. Attached please find more > simple testcase. It seems that I've found source of the problem. It is caused by the fact that when server closes its side of unix domain socket it causes unp_drop(ref, ECONNRESET) to be called on client side of the connection, which in turn results in so_error member of client's struct socket to be set to ECONNRESET. Since we don't do any more reads on the client side of the connection, this error is never cleared up and then being picked up as a connection error by kern_connect() routine, which is obviously incorrect. The funny thing is that despite that error (ECONNRESET) one can still use resulting socket like if no error has happened. Attached please find which I believe should fix the problem in question. I would appreciate if somebody can review it. Thanks in advance! Regards, Maxim --------------070202070809080104090402 Content-Type: text/plain; name="diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="diff" Index: uipc_socket.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v retrieving revision 1.208.2.6 diff -d -u -r1.208.2.6 uipc_socket.c --- uipc_socket.c 16 Nov 2004 08:15:07 -0000 1.208.2.6 +++ uipc_socket.c 10 Jan 2005 16:23:07 -0000 @@ -530,10 +530,19 @@ */ if (so->so_state & (SS_ISCONNECTED|SS_ISCONNECTING) && ((so->so_proto->pr_flags & PR_CONNREQUIRED) || - (error = sodisconnect(so)))) + (error = sodisconnect(so)))) { error = EISCONN; - else + } else { + SOCK_LOCK(so); + /* + * Prevent accumulated error from previous connection + * from biting us. + */ + so->so_error = 0; + SOCK_UNLOCK(so); error = (*so->so_proto->pr_usrreqs->pru_connect)(so, nam, td); + } + return (error); } --------------070202070809080104090402-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 10 23:15: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 61F6016A4CE for ; Mon, 10 Jan 2005 23:15:21 +0000 (GMT) Received: from web51610.mail.yahoo.com (web51610.mail.yahoo.com [206.190.38.215]) by mx1.FreeBSD.org (Postfix) with SMTP id DD90543D1D for ; Mon, 10 Jan 2005 23:15:20 +0000 (GMT) (envelope-from giffunip@yahoo.com) Received: (qmail 80662 invoked by uid 60001); 10 Jan 2005 23:15:20 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=3a4pKzI+hzh85buBoew/Qm79TDWUKzzpkLBaE5ZaLAh4x1l/94kOjeRmnd7JVWg/iVJpfieynxkBgAPoga+YDQJEp1EgE+x58nJ0G/3SaTxtl7CjEniPGa6sIE1TjfQsE5xeI3Nk/Eu4Z8y+l8X4vh3gpTeAStyMFyvBDvWJMLw= ; Message-ID: <20050110231520.80660.qmail@web51610.mail.yahoo.com> Received: from [63.171.232.105] by web51610.mail.yahoo.com via HTTP; Mon, 10 Jan 2005 15:15:20 PST Date: Mon, 10 Jan 2005 15:15:20 -0800 (PST) From: "Pedro F. Giffuni" To: freebsd-hackers@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailman-Approved-At: Tue, 11 Jan 2005 13:46:14 +0000 Subject: Picture CDs ? 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, 10 Jan 2005 23:15:21 -0000 Hi; It's odd but I couldn't mount a Picture CD on FreeBSD 5.2.1. This is pretty weird as Windows reports it is just CDFS and some jpeg files plus some windows software that let's you view it. I don't know... how can I get it wrong: mount /cdrom right? Here is a link for Picture CDs (with no technical information): http://www.kodak.com/eknec/PageQuerier.jhtml?pq-path=2/3/9/511&pq-locale=en_US There is software for windows to produce them ("EasyShare" is freeware). cheers, Pedro. __________________________________ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 11 15:25: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 7915716A4CE for ; Tue, 11 Jan 2005 15:25:24 +0000 (GMT) Received: from smtpout-1.priv.cc.uic.edu (smtpout-1.cc.uic.edu [128.248.155.232]) by mx1.FreeBSD.org (Postfix) with SMTP id E530143D5C for ; Tue, 11 Jan 2005 15:25:23 +0000 (GMT) (envelope-from zholla1@uic.edu) Received: (qmail 19792 invoked from network); 11 Jan 2005 09:25:23 -0600 Received: from icarus.cc.uic.edu (128.248.155.80) by smtpout-1.cc.uic.edu with SMTP; 11 Jan 2005 09:25:23 -0600 Date: Tue, 11 Jan 2005 09:25:23 -0600 (CST) From: Zera William Holladay X-X-Sender: zholla1@icarus.cc.uic.edu To: "Pedro F. Giffuni" In-Reply-To: <20050110231520.80660.qmail@web51610.mail.yahoo.com> Message-ID: References: <20050110231520.80660.qmail@web51610.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: Picture CDs ? 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, 11 Jan 2005 15:25:24 -0000 On Mon, 10 Jan 2005, Pedro F. Giffuni wrote: > It's odd but I couldn't mount a Picture CD on FreeBSD 5.2.1. This is pretty > weird as Windows reports it is just CDFS and some jpeg files plus some windows > software that let's you view it. I don't know... how can I get it wrong: mount > /cdrom right? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html or man mount -Zera From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 11 21:42:10 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 CD67B16A4CE for ; Tue, 11 Jan 2005 21:42:10 +0000 (GMT) Received: from merlin.alerce.com (w094.z064001164.sjc-ca.dsl.cnc.net [64.1.164.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3515C43D3F for ; Tue, 11 Jan 2005 21:42:10 +0000 (GMT) (envelope-from hartzell@kestrel.alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 21B56209C; Tue, 11 Jan 2005 13:38:27 -0800 (PST) Received: from satchel.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) Authority" (verified OK)) by merlin.alerce.com (Postfix) with ESMTP id D60272093; Tue, 11 Jan 2005 13:38:26 -0800 (PST) Received: from satchel.alerce.com (localhost [127.0.0.1]) by satchel.alerce.com (8.13.1/8.13.1) with ESMTP id j0BLeSlI020430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 11 Jan 2005 13:40:28 -0800 (PST) (envelope-from hartzell@satchel.alerce.com) Received: (from hartzell@localhost) by satchel.alerce.com (8.13.1/8.13.1/Submit) id j0BLeScc020427; Tue, 11 Jan 2005 13:40:28 -0800 (PST) (envelope-from hartzell) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16868.18379.642967.449081@satchel.alerce.com> Date: Tue, 11 Jan 2005 13:40:27 -0800 To: Zera William Holladay In-Reply-To: References: <20050110231520.80660.qmail@web51610.mail.yahoo.com> X-Mailer: VM 7.17 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid X-Virus-Scanned: ClamAV using ClamSMTP cc: "Pedro F. Giffuni" cc: freebsd-hackers@freebsd.org Subject: Re: Picture CDs ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hartzell@kestrel.alerce.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 21:42:11 -0000 Zera William Holladay writes: > > > On Mon, 10 Jan 2005, Pedro F. Giffuni wrote: > > > It's odd but I couldn't mount a Picture CD on FreeBSD 5.2.1. This is pretty > > weird as Windows reports it is just CDFS and some jpeg files plus some windows > > software that let's you view it. I don't know... how can I get it wrong: mount > > /cdrom right? > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html > > or > > man mount I'm not sure about a "Picture CD", but I just double checked and I can't mount a Kodak Photo CD on 5.3. It's not '-t cd9660' and it's not '-t msdos'. Googling around a bit shows that it's a multisession cd, and I get the following devices when I stick on in the drive (satchel)[1:35pm]~>>ls -l /dev/*cd* crw-r--r-- 1 root operator 4, 20 Jan 5 16:04 /dev/acd0 crw-r----- 1 root operator 4, 22 Jan 7 01:03 /dev/acd0t01 crw-r----- 1 root operator 4, 47 Jan 7 01:03 /dev/acd0t02 crw-r----- 1 root operator 4, 48 Jan 7 01:03 /dev/acd0t03 crw-r----- 1 root operator 4, 49 Jan 7 01:03 /dev/acd0t04 crw-r----- 1 root operator 4, 50 Jan 7 01:03 /dev/acd0t05 crw-r----- 1 root operator 4, 51 Jan 7 01:03 /dev/acd0t06 crw-r----- 1 root operator 4, 52 Jan 7 01:03 /dev/acd0t07 crw-r----- 1 root operator 4, 53 Jan 7 01:03 /dev/acd0t08 crw-r----- 1 root operator 4, 54 Jan 7 01:03 /dev/acd0t09 crw-r----- 1 root operator 4, 55 Jan 7 01:03 /dev/acd0t10 crw-r----- 1 root operator 4, 56 Jan 7 01:03 /dev/acd0t11 crw-r--r-- 1 root operator 4, 21 Jan 4 18:03 /dev/cd0 (satchel)[1:36pm]~>>cdcontrol info -f /dev/acd0 Starting track = 1, ending track = 11, TOC size = 98 bytes track start duration block length type ------------------------------------------------- 1 0:02.00 1:01.21 0 4596 data 2 1:03.21 5:25.60 4596 24435 data 3 6:29.06 2:11.57 29031 9882 data 4 8:40.63 3:18.13 38913 14863 data 5 11:59.01 2:50.64 53776 12814 data 6 14:49.65 3:15.22 66590 14647 data 7 18:05.12 3:14.38 81237 14588 data 8 21:19.50 4:02.57 95825 18207 data 9 25:22.32 2:32.45 114032 11445 data 10 27:55.02 0:59.33 125477 4458 data 11 28:54.35 0:22.03 129935 1653 data 170 29:16.38 - 131588 - - (satchel)[1:36pm]~>> If I cat /dev/acd0t02 into a file, it turns out to be a (satchel)[1:36pm]~>>sudo cat /dev/acd0t02 > /tmp/ape (satchel)[1:37pm]~>>file /tmp/ape /tmp/ape: Kodak Photo CD image pack file , landscape mode And display (from the imagemagick suite) is able to show me one of (the first, in fact) image from the CD. It doesn't seem like it's one track per image though, since there are 51 images on the disk. Has anyone worked with PhotoCD's on FreeBSD? g. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 01: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 BF71D16A4CE for ; Wed, 12 Jan 2005 01:19:59 +0000 (GMT) Received: from axe-inc.co.jp (axegw.axe-inc.co.jp [61.199.217.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C275643D39 for ; Wed, 12 Jan 2005 01:19:58 +0000 (GMT) (envelope-from takawata@axe-inc.co.jp) Received: from localhost (localhost [127.0.0.1]) by axe-inc.co.jp (8.9.3+3.2W/3.7W) with SMTP id KAA18948; Wed, 12 Jan 2005 10:19:51 +0900 (JST) Message-Id: <200501120119.KAA18948@axe-inc.co.jp> X-Authentication-Warning: axegw.axe-inc.co.jp: localhost [127.0.0.1] didn't use HELO protocol To: hartzell@kestrel.alerce.com From: takawata@jp.freebsd.org In-reply-to: Your message of "Tue, 11 Jan 2005 13:40:27 PST." <16868.18379.642967.449081@satchel.alerce.com> Date: Wed, 12 Jan 2005 10:19:50 +0900 Sender: takawata@axe-inc.co.jp cc: freebsd-hackers@freebsd.org cc: giffunip@yahoo.com Subject: Re: Picture CDs ? 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, 12 Jan 2005 01:20:00 -0000 In message <16868.18379.642967.449081@satchel.alerce.com>, George Hartzell wrot e: >Zera William Holladay writes: > > > > > > On Mon, 10 Jan 2005, Pedro F. Giffuni wrote: > > > > > It's odd but I couldn't mount a Picture CD on FreeBSD 5.2.1. This is pret >ty > > > weird as Windows reports it is just CDFS and some jpeg files plus some wi >ndows > > > software that let's you view it. I don't know... how can I get it wrong: >mount > > > /cdrom right? > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html > > > > or > > > > man mount > >I'm not sure about a "Picture CD", but I just double checked and I >can't mount a Kodak Photo CD on 5.3. It's not '-t cd9660' and it's >not '-t msdos'. Googling around a bit shows that it's a multisession >cd, and I get the following devices when I stick on in the drive > > (satchel)[1:35pm]~>>ls -l /dev/*cd* > crw-r--r-- 1 root operator 4, 20 Jan 5 16:04 /dev/acd0 > crw-r----- 1 root operator 4, 22 Jan 7 01:03 /dev/acd0t01 > crw-r----- 1 root operator 4, 47 Jan 7 01:03 /dev/acd0t02 > crw-r----- 1 root operator 4, 48 Jan 7 01:03 /dev/acd0t03 > crw-r----- 1 root operator 4, 49 Jan 7 01:03 /dev/acd0t04 > crw-r----- 1 root operator 4, 50 Jan 7 01:03 /dev/acd0t05 > crw-r----- 1 root operator 4, 51 Jan 7 01:03 /dev/acd0t06 > crw-r----- 1 root operator 4, 52 Jan 7 01:03 /dev/acd0t07 > crw-r----- 1 root operator 4, 53 Jan 7 01:03 /dev/acd0t08 > crw-r----- 1 root operator 4, 54 Jan 7 01:03 /dev/acd0t09 > crw-r----- 1 root operator 4, 55 Jan 7 01:03 /dev/acd0t10 > crw-r----- 1 root operator 4, 56 Jan 7 01:03 /dev/acd0t11 > crw-r--r-- 1 root operator 4, 21 Jan 4 18:03 /dev/cd0 > (satchel)[1:36pm]~>>cdcontrol info -f /dev/acd0 > Starting track = 1, ending track = 11, TOC size = 98 bytes > track start duration block length type > ------------------------------------------------- > 1 0:02.00 1:01.21 0 4596 data > 2 1:03.21 5:25.60 4596 24435 data > 3 6:29.06 2:11.57 29031 9882 data > 4 8:40.63 3:18.13 38913 14863 data > 5 11:59.01 2:50.64 53776 12814 data > 6 14:49.65 3:15.22 66590 14647 data > 7 18:05.12 3:14.38 81237 14588 data > 8 21:19.50 4:02.57 95825 18207 data > 9 25:22.32 2:32.45 114032 11445 data > 10 27:55.02 0:59.33 125477 4458 data > 11 28:54.35 0:22.03 129935 1653 data > 170 29:16.38 - 131588 - - > (satchel)[1:36pm]~>> > >If I cat /dev/acd0t02 into a file, it turns out to be a > > (satchel)[1:36pm]~>>sudo cat /dev/acd0t02 > /tmp/ape > (satchel)[1:37pm]~>>file /tmp/ape > /tmp/ape: Kodak Photo CD image pack file , landscape mode > >And display (from the imagemagick suite) is able to show me one of >(the first, in fact) image from the CD. It doesn't seem like it's one >track per image though, since there are 51 images on the disk. As far as I know on VideoCD, which shares CD-ROM XA spec, ISO9660 file system metadata is in the first track only, and , normally mound_cd9660 try to mount the last data track on a disk so that it can mount the newest file system image. So you can mount the cd9660 file system on the disk by -s option. Please refer mount_cd9660 manual page. The some file in the file system contains reference to sector on the other tracks. And sector size on some other tracks are different, so accessing media contents files through file system may cause wrong result. But PhotoCD may able to be accessed without problem. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 01:26: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 CE82A16A4CE; Wed, 12 Jan 2005 01:26:13 +0000 (GMT) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D46243D2F; Wed, 12 Jan 2005 01:26:13 +0000 (GMT) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.13.1/8.13.1) with ESMTP id j0C1PqAc020343; Tue, 11 Jan 2005 20:25:52 -0500 (EST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.13.1/8.13.1/Submit) id j0C1Pn2a020342; Tue, 11 Jan 2005 20:25:49 -0500 (EST) (envelope-from das@FreeBSD.ORG) Date: Tue, 11 Jan 2005 20:25:49 -0500 From: David Schultz To: Ceri Davies , Xin LI , Gerald Heinig , freebsd-hackers@FreeBSD.ORG, kamalp@acm.org, Robert Ryan , tjr@FreeBSD.ORG Message-ID: <20050112012549.GA20259@VARK.MIT.EDU> Mail-Followup-To: Ceri Davies , Xin LI , Gerald Heinig , freebsd-hackers@freebsd.org, kamalp@acm.org, Robert Ryan , tjr@FreeBSD.org References: <41DE4F3D.8050509@syskonnect.de> <20050107091004.83732.qmail@web52710.mail.yahoo.com> <20050107092110.GG49329@submonkey.net> <20050107101006.GA2553@frontfree.net> <20050108135526.GQ49329@submonkey.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050108135526.GQ49329@submonkey.net> Subject: Re: Benchmark: NetBSD 2.0 beats FreeBSD 5.3 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, 12 Jan 2005 01:26:13 -0000 On Sat, Jan 08, 2005, Ceri Davies wrote: > On Fri, Jan 07, 2005 at 06:10:06PM +0800, Xin LI wrote: > > On Fri, Jan 07, 2005 at 09:21:10AM +0000, Ceri Davies wrote: > > > I don't really think that this benchmark is bad news for either OS. My > > > only real concern are the process creation/termination results on FreeBSD. > > > > I guess that this might worth investigating: > > > > http://people.freebsd.org/~das/pbench/pbench.html > > > > (Unfortuantelly, neither tjr@ nor I have touched our patchsets recently. > > A most recent snapshot of the two patchsets are here: > > > > http://research.delphij.net/freebsd/pid.diff > > http://research.delphij.net/freebsd/pid-tjr.diff) > > > > Most of the work was to catch up with Aug 2004's -CURRENT, but it might > > be easier to bring them up-to-date instead of working from the very original > > patches =-) > > Looks great. Any reason why neither has been committed? I've pinged Tim several times, but I think he's busy with his job in the real world to worry about "jobs" in FreeBSD right now. However, there's no rush. There's a lot of lower-hanging fruit in the fork/exec/exit path, including a gratuitous number of acquisitions and releases of Giant. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 02:34: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 0D79116A4CE for ; Wed, 12 Jan 2005 02:34:42 +0000 (GMT) Received: from S2.cableone.net (smtp2.cableone.net [24.116.0.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91CC343D3F for ; Wed, 12 Jan 2005 02:34:41 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from fennec.local.lan (unverified [24.119.123.89]) by S2.cableone.net (CableOne SMTP Service S2) with ESMTP id 7116095 for ; Tue, 11 Jan 2005 19:55:23 -0700 Date: Tue, 11 Jan 2005 18:34:39 -0600 From: Vulpes Velox To: freebsd-hackers@FreeBSD.org Message-ID: <20050111183439.75e6b334@fennec.local.lan> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IP-stats: Incoming Last 2, First 35, in=54, out=0, spam=0 X-External-IP: 24.119.123.89 X-Abuse-Info: Send abuse complaints to abuse@cableone.net Subject: RC scripts and NIS 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, 12 Jan 2005 02:34:42 -0000 I am currently am currently working on making modifications to the rc system to allow NIS to not be started if the server is not present. So far I am just looking at disabling ypbind at start if certain conditions are meet. The idea it is to run a script that checks if the servers or server is present and then if it is, ypbind if enabled, if not it modifies the current variables to stop ypbind from being run and prints a message about it to stdout. >From my understanding this is the one that needs disabled if the system is to operate outside of it's usual network. Allowing it to fall back to /etc/ for it's information. I've tested it by disabling it upon startup manually and it worked fine. Is there any other NIS related scripts I should make changes to, or is this the only one I should worry about? If any one have opinions or any input on any of this, I would be interested to hear it. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 04:54: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 5799716A4CE for ; Wed, 12 Jan 2005 04:54:57 +0000 (GMT) Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F5AA43D2D for ; Wed, 12 Jan 2005 04:54:57 +0000 (GMT) (envelope-from keebler@mindspring.com) Received: from user-11faknj.dsl.mindspring.com ([66.245.82.243] helo=[192.168.1.100]) by smtp6.mindspring.com with esmtp (Exim 3.33 #1) id 1CoaX2-0005Ma-00 for freebsd-hackers@freebsd.org; Tue, 11 Jan 2005 23:54:57 -0500 Message-ID: <41E4AE0B.4060907@mindspring.com> Date: Tue, 11 Jan 2005 23:56:43 -0500 From: Carleton Vaughn User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) 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: growisofs killing every other DVD+R 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, 12 Jan 2005 04:54:57 -0000 [I originally posted this in -questions, no replies yet] I'm new to this list and how to ask it for help, so please bear with me if I have omitted anything critical or have included too much or am in the wrong place entirely. I'm running: > sally# uname -a > FreeBSD sally.keebler.homeunix.net 4.10-RELEASE FreeBSD 4.10-RELEASE > #3: Mon Dec 27 18:45:53 EST 2004 > root@sally.keebler.homeunix.net:/usr/src/sys/compile/C3 i386 And I recently installed a DVD burnerso that I could do system backups: > sally# dmesg|grep cd1 > acd1: DVD-R at ata1-slave PIO4 > acd1: DVD-R at ata1-slave PIO4 > cd1 at ata1 bus 0 target 1 lun 0 > cd1: Removable CD-ROM SCSI-0 device > cd1: 16.000MB/s transfers > cd1: cd present [1 x 2048 byte records] I know there are "better" backup solutions, but this system is for home use and I just want to get backups going. Eventually (e.g. as soon as I figure out how) I will be doing proper dumps, but for now I'm pouring things off into cd9660 filesystems. I've been using growfs > sally# growisofs --version > * growisofs by , version 5.19-1, > front-ending to mkisofs: mkisofs 2.0.3 (i386-unknown-freebsd4.10) to do all this, and for the first disk, it did just fine. The problem is the *second* disk: > sally# growisofs -dvd-compat -Z /dev/cd1c=farm5.iso > Executing 'builtin_dd if=farm5.iso of=/dev/pass1 obs=32k seek=0' > /dev/pass1: "Current Write Speed" is 8.2x1385KBps. > 0/3085238272 ( 0.0%) @0x, remaining ??:?? > 0/3085238272 ( 0.0%) @0x, remaining ??:?? > 0/3085238272 ( 0.0%) @0x, remaining ??:?? > :-? the LUN appears to be stuck writing LBA=10h, retry in 0ms > :-[ WRITE@LBA=80000010h failed with SK=2h/ASC=04h/ACQ=08h]: Resource > temporarily unavailable > :-( write failed: Resource temporarily unavailable > /dev/pass1: flushing cache > /dev/pass1: closing track > /dev/pass1: closing disc When I take the ruined disk out, I can see the physical evidence of a short write, but the disk isn't mountable. The best part of all is that once I replace the ruined media and rerun growisofs, the new disk burns flawlessly. Just to taunt me. I am getting this result every single time. I know very little about SCSI but my theory is that some sort of state is being set on the device but not cleared before the next disk is attempted. Any help would be greatly appreciated, and I will happily provide further information if you clue me on how to obtain it. Thanks. -- Carleton Vaughn College Park, Georgia, USA From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 06:21: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 C863816A4CE for ; Wed, 12 Jan 2005 06:21:23 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C510743D67 for ; Wed, 12 Jan 2005 06:21:22 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id j0C6LDiQ093334; Wed, 12 Jan 2005 16:51:14 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Date: Wed, 12 Jan 2005 16:51:04 +1030 User-Agent: KMail/1.7.1 References: <200501120119.KAA18948@axe-inc.co.jp> In-Reply-To: <200501120119.KAA18948@axe-inc.co.jp> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1534334.otsfQmlVZZ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501121651.12469.doconnor@gsoft.com.au> X-Spam-Score: -5.4 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: giffunip@yahoo.com Subject: Re: Picture CDs ? 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, 12 Jan 2005 06:21:23 -0000 --nextPart1534334.otsfQmlVZZ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 12 Jan 2005 11:49, takawata@jp.freebsd.org wrote: > sector on the other tracks. And sector size on some other tracks are > different, so accessing media contents files through file system > may cause wrong result. But PhotoCD may able to be accessed > without problem. There is the graphics/xpcd port which claims to be able to read PhotoCD's..= =20 I've never used it though. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1534334.otsfQmlVZZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD4DBQBB5MHY5ZPcIHs/zowRAm9cAJjsKkkm79uO+2zO+DvKUtnHS4L8AJ9i6JLE 5NCuzd824Ceg8KFBxr51TQ== =ITBd -----END PGP SIGNATURE----- --nextPart1534334.otsfQmlVZZ-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 09:50: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 701D116A4CE for ; Wed, 12 Jan 2005 09:50:02 +0000 (GMT) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9ABF443D1F for ; Wed, 12 Jan 2005 09:50:01 +0000 (GMT) (envelope-from smckay@internode.on.net) Received: from dungeon.home (ppp231-141.lns1.bne1.internode.on.net [203.122.231.141])j0C9nx6R019044; Wed, 12 Jan 2005 20:19:59 +1030 (CST) Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.13.1/8.11.6) with ESMTP id j0C9nQCZ000573; Wed, 12 Jan 2005 19:49:26 +1000 (EST) (envelope-from mckay) Message-Id: <200501120949.j0C9nQCZ000573@dungeon.home> To: freebsd-hackers@freebsd.org Date: Wed, 12 Jan 2005 19:49:26 +1000 From: Stephen McKay cc: Stephen McKay Subject: Background processes setting O_NONBLOCK on ttys 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, 12 Jan 2005 09:50:02 -0000 [You may see this message twice as it got stuck in the ^$&#@ moderation queue.] Hi! I'm running FreeBSD 4.11-RC2 on an Athlon 2100+ with 768MB of ram and software mirrored 160GB Seagate disks. All pretty straightforward so far. I'm currently a couple of DAYS into compiling Open Office 1.1.3, and while I can tell you all sorts of stories of trouble and woe, I want to concentrate on just one small aspect. I commonly background all builds, this port included, and then I continue doing whatever I like in that window. In this case, things start dying. For example, "tail -f LOG" works for a while, and then mysteriously exits. It's something I've not seen before in 20 years of Unix! After some tracing, I have worked out that the tty is being alternately set to nonblocking and back to normal hundreds of times during the compilation of Open Office, and that's what is killing tail. Tail does not expect stdout to be nonblocking, and will exit if it ever receives EAGAIN. This is because putchar() in stdio passes this back up as an error. This causes tail to exit (return code 1). I haven't found which program is doing the nonblocking flipping yet. I expect I will eventually. What I initially find is quite odd is that a background process is permitted to modify the tty like that. I checked the flow of control of fcntl() as it sets O_NONBLOCK on a file descriptor and eventually control passes to ttioctl() which includes code to prevent background processes messing with the tty. (At least, I think it does. This is code involving many indirections.) But, for whatever reason, setting non-blocking mode (which is called FIONBIO at this point) is not one of the set of things considered as "modification" of the tty, so it is passed through unchallenged. I intend to add the setting of non-blocking mode as one of the things that will cause a background process to receive SIGTTOU and see if my life improves. If it works as well as I hope, I'll push for it being official. I also think this mechanism may be behind occasional failures of vi that I (and some others here and there) have seen over the last few years. By the way, the code seems to be the same in -current and 5.x so this will apply there if it turns out to be sensible. Also, stdio in -current is unchanged, and will report EAGAIN as a failure for putchar(). This is the documented behaviour (at least it is in the Single Unix Specification). Should tail be coded such that EAGAIN on stdout is detected and worked around? That seems like too much to expect tail (and every other ordinary utility) to know about, so I hope my other efforts yield fruit. Stephen. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 13:55: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 172AA16A4CE for ; Wed, 12 Jan 2005 13:55:01 +0000 (GMT) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E58B43D1D for ; Wed, 12 Jan 2005 13:55:00 +0000 (GMT) (envelope-from smckay@internode.on.net) Received: from dungeon.home (ppp231-141.lns1.bne1.internode.on.net [203.122.231.141])j0CDsv6R085880; Thu, 13 Jan 2005 00:24:57 +1030 (CST) Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.13.1/8.11.6) with ESMTP id j0CDscrR002027; Wed, 12 Jan 2005 23:54:38 +1000 (EST) (envelope-from mckay) Message-Id: <200501121354.j0CDscrR002027@dungeon.home> To: freebsd-hackers@freebsd.org References: <200501120949.j0C9nQCZ000573@dungeon.home> In-Reply-To: <200501120949.j0C9nQCZ000573@dungeon.home> from Stephen McKay at "Wed, 12 Jan 2005 19:49:26 +1000" Date: Wed, 12 Jan 2005 23:54:38 +1000 From: Stephen McKay cc: Stephen McKay Subject: Re: Background processes setting O_NONBLOCK on ttys 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, 12 Jan 2005 13:55:01 -0000 On Wednesday, 12th January 2005, Stephen McKay wrote: >[Problems during Open Office compilation on FreeBSD 4.11-RC2] >After some tracing, I have worked out that the tty is being alternately >set to nonblocking and back to normal hundreds of times during the compilation >of Open Office, and that's what is killing tail. Turns out it's 1000's of times, not merely hundreds, but who's counting? :-) And I know what does it now: absolutely every threaded program! Scumbags! Thanks to _thread_fd_table_init() called from _thread_init(), which seems to get called pretty early on in a threaded program, every file descriptor is set to non-blocking, including 0, 1 and 2. Quite often these refer to your tty, which means it gets set to non-blocking, even if the threaded program has been invoked in the background. I first noticed weird problems with vi some years ago which are consistent with the tty (actually pty) being set to non-blocking, but have never found a culprit until now. But, having found the villian, what to do? It is clearly wrong that foreground processes have to deal with the tty spontaneously becoming non-blocking. Every program, even "cat", would have to be patched. So, that's not an option. I've patched my system so that you have to be in the foreground (ie match the tty process group) in order to set non-blocking on a tty. I'm pretty pleased with this as it protects me from threaded programs, but there is a drawback. The unfortunate side effect is that all threaded programs block if invoked with "&". I can imagine others not liking this. So, seriously, we could: a) Rewrite file descriptor handling in libc_r so it does not set O_NONBLOCK on tty file descriptors unless it is in the foreground. I don't know how hard this would be, or whether it even applies to -current with its profusion of threading libraries. I'll leave this to those who believe in threading. b) Add new non-blocking read() and write() call variants and use them in the threading library instead of setting O_NONBLOCK. c) Make O_NONBLOCK be per file descriptor (like FD_CLOEXEC). Thus, descriptors produced from dup() (for example) would have their own O_NONBLOCK flag, just as two descriptors from separate open() calls have today. Option b) is probably a non-starter, though it would have been a better way to do it if O_NONBLOCK wasn't already around (IMHO). Option a) looks hard and still doesn't protect normal processes from all others (including any old libc_r binaries out there). Option c) is my clear choice, and I intend to implement this for my own system before attempting to foist it upon everyone else. Any thoughts? By the way, I could find no documentation or standard that requires that O_NONBLOCK apply in the way it does as opposed to per descriptor like I am suggesting. Stephen. PS If anyone else wants to play with 4.11-RC2 with the background O_NONBLOCK prevention patch, here's what I have so far. The patch to tty.c is straightforward. The patch to kern_descrip.c fixes what I think is a bug anyway: the file flags are updated even if FIONBIO fails. Index: tty.c =================================================================== RCS file: /cvs/src/sys/kern/tty.c,v retrieving revision 1.129.2.5 diff -u -r1.129.2.5 tty.c --- tty.c 11 Mar 2002 01:32:31 -0000 1.129.2.5 +++ tty.c 12 Jan 2005 09:35:23 -0000 @@ -712,6 +712,7 @@ /* If the ioctl involves modification, hang if in the background. */ switch (cmd) { + case FIONBIO: case TIOCCBRK: case TIOCCONS: case TIOCDRAIN: Index: kern_descrip.c =================================================================== RCS file: /cvs/src/sys/kern/kern_descrip.c,v retrieving revision 1.81.2.19 diff -u -r1.81.2.19 kern_descrip.c --- kern_descrip.c 28 Feb 2004 00:43:31 -0000 1.81.2.19 +++ kern_descrip.c 12 Jan 2005 11:56:27 -0000 @@ -218,7 +218,7 @@ register struct file *fp; register char *pop; struct vnode *vp; - int i, tmp, error, flg = F_POSIX; + int i, newflag, tmp, error, flg = F_POSIX; struct flock fl; u_int newmin; @@ -252,22 +252,22 @@ case F_SETFL: fhold(fp); - fp->f_flag &= ~FCNTLFLAGS; - fp->f_flag |= FFLAGS(uap->arg & ~O_ACCMODE) & FCNTLFLAGS; - tmp = fp->f_flag & FNONBLOCK; + newflag = fp->f_flag & ~FCNTLFLAGS; + newflag |= FFLAGS(uap->arg & ~O_ACCMODE) & FCNTLFLAGS; + tmp = newflag & FNONBLOCK; error = fo_ioctl(fp, FIONBIO, (caddr_t)&tmp, p); if (error) { fdrop(fp, p); return (error); } - tmp = fp->f_flag & FASYNC; + tmp = newflag & FASYNC; error = fo_ioctl(fp, FIOASYNC, (caddr_t)&tmp, p); if (!error) { fdrop(fp, p); + fp->f_flag = newflag; return (0); } - fp->f_flag &= ~FNONBLOCK; - tmp = 0; + tmp = fp->f_flag & FNONBLOCK; (void)fo_ioctl(fp, FIONBIO, (caddr_t)&tmp, p); fdrop(fp, p); return (error); From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 11 15:37: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 5803116A4CE for ; Tue, 11 Jan 2005 15:37:52 +0000 (GMT) Received: from web51607.mail.yahoo.com (web51607.mail.yahoo.com [206.190.38.212]) by mx1.FreeBSD.org (Postfix) with SMTP id D705D43D41 for ; Tue, 11 Jan 2005 15:37:51 +0000 (GMT) (envelope-from giffunip@yahoo.com) Received: (qmail 62999 invoked by uid 60001); 11 Jan 2005 15:37:51 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=t3WZ2wLF5BKZ8cvhpVyYtxxM3PFoDDHwP5aQvJpxstqRMxkN8AQ5VOwjDLuVk0Jdsmf5bbNfo0XCc9idbIMxT0uTY81apcGE0ctgaIS/GtmHYvYgNhucCp9ap8R5VF3nEbKlkgv8ZrT+Fa5U/5LaQE/dHn2BYWACulok3LZl+TY= ; Message-ID: <20050111153751.62997.qmail@web51607.mail.yahoo.com> Received: from [200.119.73.14] by web51607.mail.yahoo.com via HTTP; Tue, 11 Jan 2005 07:37:51 PST Date: Tue, 11 Jan 2005 07:37:51 -0800 (PST) From: "Pedro F. Giffuni" To: Zera William Holladay In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailman-Approved-At: Wed, 12 Jan 2005 14:45:37 +0000 cc: freebsd-hackers@freebsd.org Subject: Re: Picture CDs ? 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, 11 Jan 2005 15:37:52 -0000 Thanks! I should've posted this in -questions or check the handbook carefully. Pedro. --- Zera William Holladay wrote: > > > On Mon, 10 Jan 2005, Pedro F. Giffuni wrote: > > > It's odd but I couldn't mount a Picture CD on FreeBSD 5.2.1. This is pretty > > weird as Windows reports it is just CDFS and some jpeg files plus some > windows > > software that let's you view it. I don't know... how can I get it wrong: > mount > > /cdrom right? > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html > > or > > man mount > > -Zera > __________________________________ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 03:35: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 A3C2D16A4CE for ; Wed, 12 Jan 2005 03:35:54 +0000 (GMT) Received: from web51604.mail.yahoo.com (web51604.mail.yahoo.com [206.190.38.209]) by mx1.FreeBSD.org (Postfix) with SMTP id 0854E43D1D for ; Wed, 12 Jan 2005 03:35:54 +0000 (GMT) (envelope-from giffunip@yahoo.com) Received: (qmail 57015 invoked by uid 60001); 12 Jan 2005 03:35:53 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=NvjBYpVldvQmfbn6v+4Ba3qvYdaA03kyDTFwTBwr9s8JBu3+gnlxjg8dUHu6lXDD5kxvBZjqKSkM+YBWJP9dAhXKEaQLwbS235FrgyIN2KAIVpSFCiXRXaV8jFbG5cX3Qq40fclyNIr8YhUry+JEFOM/xTLZmaEvgNZ7ozLzwpM= ; Message-ID: <20050112033553.57013.qmail@web51604.mail.yahoo.com> Received: from [200.119.73.64] by web51604.mail.yahoo.com via HTTP; Tue, 11 Jan 2005 19:35:53 PST Date: Tue, 11 Jan 2005 19:35:53 -0800 (PST) From: "Pedro F. Giffuni" To: hartzell@kestrel.alerce.com In-Reply-To: <16868.18379.642967.449081@satchel.alerce.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailman-Approved-At: Wed, 12 Jan 2005 14:45:37 +0000 cc: freebsd-hackers@freebsd.org Subject: Re: Picture CDs ? 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, 12 Jan 2005 03:35:54 -0000 Hi; The PictureCD mounted with the same command suggested by the mount_cd9660 page for PhotoCDs. I think the difference is that while Picture CDs use jpeg, the PhotoCDs use a Kodak proprietary format. I just learned that the netpbm distributed via Ibiblio has a PhotoCD converter available (it was removed from the netpbm in sourceforge because it's not extrictly "opensource". cheers, PEdro. --- George Hartzell wrote: > Zera William Holladay writes: > > > > > > On Mon, 10 Jan 2005, Pedro F. Giffuni wrote: > > > > > It's odd but I couldn't mount a Picture CD on FreeBSD 5.2.1. This is > pretty > > > weird as Windows reports it is just CDFS and some jpeg files plus some > windows > > > software that let's you view it. I don't know... how can I get it wrong: > mount > > > /cdrom right? > > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html > > > > or > > > > man mount > > I'm not sure about a "Picture CD", but I just double checked and I > can't mount a Kodak Photo CD on 5.3. It's not '-t cd9660' and it's > not '-t msdos'. Googling around a bit shows that it's a multisession > cd, and I get the following devices when I stick on in the drive > > (satchel)[1:35pm]~>>ls -l /dev/*cd* > crw-r--r-- 1 root operator 4, 20 Jan 5 16:04 /dev/acd0 > crw-r----- 1 root operator 4, 22 Jan 7 01:03 /dev/acd0t01 > crw-r----- 1 root operator 4, 47 Jan 7 01:03 /dev/acd0t02 > crw-r----- 1 root operator 4, 48 Jan 7 01:03 /dev/acd0t03 > crw-r----- 1 root operator 4, 49 Jan 7 01:03 /dev/acd0t04 > crw-r----- 1 root operator 4, 50 Jan 7 01:03 /dev/acd0t05 > crw-r----- 1 root operator 4, 51 Jan 7 01:03 /dev/acd0t06 > crw-r----- 1 root operator 4, 52 Jan 7 01:03 /dev/acd0t07 > crw-r----- 1 root operator 4, 53 Jan 7 01:03 /dev/acd0t08 > crw-r----- 1 root operator 4, 54 Jan 7 01:03 /dev/acd0t09 > crw-r----- 1 root operator 4, 55 Jan 7 01:03 /dev/acd0t10 > crw-r----- 1 root operator 4, 56 Jan 7 01:03 /dev/acd0t11 > crw-r--r-- 1 root operator 4, 21 Jan 4 18:03 /dev/cd0 > (satchel)[1:36pm]~>>cdcontrol info -f /dev/acd0 > Starting track = 1, ending track = 11, TOC size = 98 bytes > track start duration block length type > ------------------------------------------------- > 1 0:02.00 1:01.21 0 4596 data > 2 1:03.21 5:25.60 4596 24435 data > 3 6:29.06 2:11.57 29031 9882 data > 4 8:40.63 3:18.13 38913 14863 data > 5 11:59.01 2:50.64 53776 12814 data > 6 14:49.65 3:15.22 66590 14647 data > 7 18:05.12 3:14.38 81237 14588 data > 8 21:19.50 4:02.57 95825 18207 data > 9 25:22.32 2:32.45 114032 11445 data > 10 27:55.02 0:59.33 125477 4458 data > 11 28:54.35 0:22.03 129935 1653 data > 170 29:16.38 - 131588 - - > (satchel)[1:36pm]~>> > > If I cat /dev/acd0t02 into a file, it turns out to be a > > (satchel)[1:36pm]~>>sudo cat /dev/acd0t02 > /tmp/ape > (satchel)[1:37pm]~>>file /tmp/ape > /tmp/ape: Kodak Photo CD image pack file , landscape mode > > And display (from the imagemagick suite) is able to show me one of > (the first, in fact) image from the CD. It doesn't seem like it's one > track per image though, since there are 51 images on the disk. > > Has anyone worked with PhotoCD's on FreeBSD? > > g. > __________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 03:56:22 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 5140A16A4CF for ; Wed, 12 Jan 2005 03:56:22 +0000 (GMT) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 899FF43D5D for ; Wed, 12 Jan 2005 03:56:21 +0000 (GMT) (envelope-from smckay@internode.on.net) Received: from dungeon.home (ppp231-141.lns1.bne1.internode.on.net [203.122.231.141])j0C3uJqT082064; Wed, 12 Jan 2005 14:26:19 +1030 (CST) Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.13.1/8.11.6) with ESMTP id j0C3tLCc052070; Wed, 12 Jan 2005 13:55:22 +1000 (EST) (envelope-from mckay) Message-Id: <200501120355.j0C3tLCc052070@dungeon.home> To: freebsd-hackers@freebsd.org Date: Wed, 12 Jan 2005 13:55:21 +1000 From: Stephen McKay X-Mailman-Approved-At: Wed, 12 Jan 2005 14:45:37 +0000 cc: Stephen McKay Subject: Background processes setting O_NONBLOCK on ttys 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, 12 Jan 2005 03:56:22 -0000 Hi! I'm running FreeBSD 4.11-RC2 on an Athlon 2100+ with 768MB of ram and software mirrored 160GB Seagate disks. All pretty straightforward so far. I'm currently a couple of DAYS into compiling Open Office 1.1.3, and while I can tell you all sorts of stories of trouble and woe, I want to concentrate on just one small aspect. I commonly background all builds, this port included, and then I continue doing whatever I like in that window. In this case, things start dying. For example, "tail -f LOG" works for a while, and then mysteriously exits. It's something I've not seen before in 20 years of Unix! After some tracing, I have worked out that the tty is being alternately set to nonblocking and back to normal hundreds of times during the compilation of Open Office, and that's what is killing tail. Tail does not expect stdout to be nonblocking, and will exit if it ever receives EAGAIN. This is because putchar() in stdio passes this back up as an error. This causes tail to exit (return code 1). I haven't found which program is doing the nonblocking flipping yet. I expect I will eventually. What I initially find is quite odd is that a background process is permitted to modify the tty like that. I checked the flow of control of fcntl() as it sets O_NONBLOCK on a file descriptor and eventually control passes to ttioctl() which includes code to prevent background processes messing with the tty. (At least, I think it does. This is code involving many indirections.) But, for whatever reason, setting non-blocking mode (which is called FIONBIO at this point) is not one of the set of things considered as "modification" of the tty, so it is passed through unchallenged. I intend to add the setting of non-blocking mode as one of the things that will cause a background process to receive SIGTTOU and see if my life improves. If it works as well as I hope, I'll push for it being official. I also think this mechanism may be behind occasional failures of vi that I (and some others here and there) have seen over the last few years. By the way, the code seems to be the same in -current and 5.x so this will apply there if it turns out to be sensible. Also, stdio in -current is unchanged, and will report EAGAIN as a failure for putchar(). This is the documented behaviour (at least it is in the Single Unix Specification). Should tail be coded such that EAGAIN on stdout is detected and worked around? That seems like too much to expect tail (and every other ordinary utility) to know about, so I hope my other efforts yield fruit. Stephen. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 18:39: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 E720416A4CF for ; Wed, 12 Jan 2005 18:39:10 +0000 (GMT) Received: from aker.isnic.is (aker.isnic.is [193.4.58.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D98343D5D for ; Wed, 12 Jan 2005 18:39:10 +0000 (GMT) (envelope-from oli@aker.isnic.is) Received: by aker.isnic.is (Postfix, from userid 1000) id E2AD98A1C5; Wed, 12 Jan 2005 18:39:08 +0000 (UTC) Date: Wed, 12 Jan 2005 18:39:08 +0000 From: Olafur Osvaldsson To: freebsd-hackers@freebsd.org Message-ID: <20050112183908.GA4030@isnic.is> Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.1i Subject: Need help analyzing a 5.3-RELEASE-p2 crash 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, 12 Jan 2005 18:39:11 -0000 This is what I got, could someone help me with the next steps? ================================================================== Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 00 fault virtual address = 0x413db14b fault code = supervisor write, page not present instruction pointer = 0x8:0xc06272e2 stack pointer = 0x10:0xe75cd9bc frame pointer = 0x10:0xe75cd9c4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 6535 (sshd) trap number = 12 panic: page fault cpuid = 1 boot() called on cpu#1 Uptime: 12d6h22m21s Dumping 1023 MB 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008 ================================================================== Backtrace: #0 doadump () at pcpu.h:159 #1 0xc060560f in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:397 #2 0xc0605935 in panic (fmt=0xc07f164a "%s") at /usr/src/sys/kern/kern_shutdown.c:553 #3 0xc07a78c4 in trap_fatal (frame=0xe75cd97c, eva=1094562123) at /usr/src/sys/i386/i386/trap.c:809 #4 0xc07a7607 in trap_pfault (frame=0xe75cd97c, usermode=0, eva=1094562123) at /usr/src/sys/i386/i386/trap.c:727 #5 0xc07a7241 in trap (frame= {tf_fs = -413401064, tf_es = -1067515888, tf_ds = -413401072, tf_edi = -1033200280, tf_esi = 1103114931, tf_ebp = -413345340, tf_isp = -413345368, tf_ebx = -1033594764, tf_edx = 1094562119, tf_ecx = -1064546620, tf_eax = 0, tf_trapno = 12, tf_err = 2, tf_eip = -1067289886, tf_cs = 8, tf_eflags = 66054, tf_esp = -1033594880, tf_ss = -1031246336}) at /usr/src/sys/i386/i386/trap.c:417 #6 0xc079552a in calltrap () at /usr/src/sys/i386/i386/exception.s:140 #7 0xe75c0018 in ?? () #8 0xc05f0010 in fork1 (td=0xc2649874, flags=89, pages=-413345304, procp=0xc0633e91) at pcpu.h:159 #9 0xc0627236 in selwakeuppri (sip=0xc2649874, pri=89) at /usr/src/sys/kern/sys_generic.c:1096 #10 0xc0633e91 in ttwakeup (tp=0x10206) at /usr/src/sys/kern/tty.c:2366 #11 0xc0632b38 in ttymodem (tp=0xc2649800, flag=0) at /usr/src/sys/kern/tty.c:1625 #12 0xc0636823 in ptcopen (dev=0xc2886e00, flag=3, devtype=8192, td=0x0) at linedisc.h:136 #13 0xc05cda2e in spec_open (ap=0xe75cda84) at /usr/src/sys/fs/specfs/spec_vnops.c:207 #14 0xc05cd773 in spec_vnoperate (ap=0x0) at /usr/src/sys/fs/specfs/spec_vnops.c:118 #15 0xc0663861 in vn_open_cred (ndp=0xe75cdbe4, flagp=0xe75cdce4, cmode=0, cred=0xc2892180, fdidx=0) at vnode_if.h:228 #16 0xc0663446 in vn_open (ndp=0x0, flagp=0xe75cdce4, cmode=0, fdidx=3) at /usr/src/sys/kern/vfs_vnops.c:91 #17 0xc065d55f in kern_open (td=0xc3074190, path=0x0, pathseg=UIO_USERSPACE, flags=3, mode=0) at /usr/src/sys/kern/vfs_syscalls.c:957 #18 0xc065d478 in open (td=0xc3074190, uap=0x0) at /usr/src/sys/kern/vfs_syscalls.c:926 #19 0xc07a7bcf in syscall (frame= {tf_fs = 47, tf_es = 134676527, tf_ds = -1078001617, tf_edi = -1077943125, tf_esi = 671947821, tf_ebp = -1077943096, tf_isp = -413344396, tf_ebx = 671955040, tf_edx = 671947836, tf_ecx = 674477548, tf_eax = 5, tf_trapno = 12, tf_err = 2, tf_eip = 673989911, tf_cs = 31, tf_eflags = 658, tf_esp = -1077943188, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1001 #20 0xc079557f in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:201 #21 0x0000002f in ?? () #22 0x0807002f in ?? () #23 0xbfbf002f in ?? () #24 0xbfbfe4ab in ?? () #25 0x280d1c2d in ?? () #26 0xbfbfe4c8 in ?? () #27 0xe75cdd74 in ?? () #28 0x280d3860 in ?? () #29 0x280d1c3c in ?? () #30 0x2833b5ec in ?? () #31 0x00000005 in ?? () #32 0x0000000c in ?? () #33 0x00000002 in ?? () #34 0x282c4517 in ?? () #35 0x0000001f in ?? () #36 0x00000292 in ?? () #37 0xbfbfe46c in ?? () #38 0x0000002f in ?? () #39 0x73652528 in ?? () #40 0x090a2970 in ?? () #41 0x6c6c6163 in ?? () #42 0x67657209 in ?? () #43 0x1fc83000 in ?? () #44 0xc307254c in ?? () #45 0xc3074190 in ?? () #46 0xe75cdb00 in ?? () #47 0xe75cdae8 in ?? () #48 0xc22644b0 in ?? () #49 0xc0615c17 in sched_switch (td=0x280d1c2d, newtd=0x280d3860, flags=Cannot access memory at address 0xbfbfe4d8 ) at /usr/src/sys/kern/sched_4bsd.c:865 -- Ólafur Osvaldsson Kerfisstjóri Internet á Íslandi hf. Sími: 525-5291 Email: oli@isnic.is From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 21:17: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 D427416A4DA for ; Wed, 12 Jan 2005 21:17:45 +0000 (GMT) Received: from mail-svr1.cs.utah.edu (brahma.cs.utah.edu [155.98.64.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DAFD43D53 for ; Wed, 12 Jan 2005 21:17:45 +0000 (GMT) (envelope-from saggarwa@cs.utah.edu) Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 1D14C34867 for ; Wed, 12 Jan 2005 14:17:41 -0700 (MST) Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25458-09 for ; Wed, 12 Jan 2005 14:17:40 -0700 (MST) Received: from faith.cs.utah.edu (faith.cs.utah.edu [155.98.65.40]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id CC83A34864 for ; Wed, 12 Jan 2005 14:17:40 -0700 (MST) Received: by faith.cs.utah.edu (Postfix, from userid 4973) id 4388D2EC21; Wed, 12 Jan 2005 14:17:38 -0700 (MST) Received: from localhost (localhost [127.0.0.1]) by faith.cs.utah.edu (Postfix) with ESMTP id 84B2734406 for ; Wed, 12 Jan 2005 21:17:38 +0000 (UTC) Date: Wed, 12 Jan 2005 14:17:38 -0700 (MST) From: Siddharth Aggarwal To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: amavisd-new at cs.utah.edu Subject: process checkpoint restore facility now in DragonFly BSD 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, 12 Jan 2005 21:17:46 -0000 Hi all, I am responding to a post back in Oct 2003 when the checkpointing feature was announced for DragonFly. I have been doing some research on this, and have seen some projects that use Xen VMM to achieve checkpoints of guest OSes. So I was looking for inputs from people as to what everyone feels about checkpointing, whether it should be done at the physical machine level or VM level. Pros and Cons of each approach, if any further development was done on DragonFly for checkpoint since then and if it was stopped, why? Are there serious limitations to checkpointing a physical machine? Sorry for such a vague posting, but I thought this would be a good platform to get some feedback. Thanks, Sid. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 21:30: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 9C78116A4CE for ; Wed, 12 Jan 2005 21:30:45 +0000 (GMT) Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id D09AE43D1D for ; Wed, 12 Jan 2005 21:30:44 +0000 (GMT) (envelope-from kmacy@netapp.com) Received: from frejya.corp.netapp.com (10.57.157.119) by mx2.netapp.com with ESMTP; 12 Jan 2005 13:30:46 -0800 X-IronPort-AV: i="3.88,118,1102320000"; d="scan'208"; a="120222490:sNHT15646164" Received: from siml3-fe.eng.netapp.com (siml3-fe.eng.netapp.com [10.56.9.153]) j0CLUibr027431; Wed, 12 Jan 2005 13:30:44 -0800 (PST) Date: Wed, 12 Jan 2005 13:30:44 -0800 (PST) From: Kip Macy X-X-Sender: kmacy@siml3.eng.netapp.com To: Siddharth Aggarwal In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: process checkpoint restore facility now in DragonFly BSD 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, 12 Jan 2005 21:30:45 -0000 I've promised Nate to port the functionality to FreeBSD. I'm busy doing some things with the FreeBSD port to Xen at the moment. Checkpointing a process is intrinsically messy for reasons beyond the obvious statefulness of TCP connections. Process state, particularly with regard to devices, is often not cleanly associated with the process in the kernel. What happens if a file that the process had open has gone away? Other issues abound - checkpointing a process pipeline can be made to work, but some work would need to be done on pipes. The list goes on. -Kip On Wed, 12 Jan 2005, Siddharth Aggarwal wrote: > > Hi all, > > I am responding to a post back in Oct 2003 when the checkpointing feature > was announced for DragonFly. I have been doing some research on this, and > have seen some projects that use Xen VMM to achieve checkpoints of guest > OSes. > > So I was looking for inputs from people as to what everyone feels about > checkpointing, whether it should be done at the physical machine level or > VM level. Pros and Cons of each approach, if any further development was > done on DragonFly for checkpoint since then and if it was stopped, why? > Are there serious limitations to checkpointing a physical machine? > > Sorry for such a vague posting, but I thought this would be a good > platform to get some feedback. > > Thanks, > Sid. > _______________________________________________ > 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" > -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 21:37: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 A1B8316A4CE for ; Wed, 12 Jan 2005 21:37:17 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 715A443D58 for ; Wed, 12 Jan 2005 21:37:17 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j0CLe2Fh023244; Wed, 12 Jan 2005 13:40:02 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j0CLe2s3023243; Wed, 12 Jan 2005 13:40:02 -0800 Date: Wed, 12 Jan 2005 13:40:02 -0800 From: Brooks Davis To: Siddharth Aggarwal Message-ID: <20050112214002.GA21038@odin.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-hackers@freebsd.org Subject: Re: process checkpoint restore facility now in DragonFly BSD 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, 12 Jan 2005 21:37:17 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 12, 2005 at 02:17:38PM -0700, Siddharth Aggarwal wrote: >=20 > I am responding to a post back in Oct 2003 when the checkpointing feature > was announced for DragonFly. I have been doing some research on this, and > have seen some projects that use Xen VMM to achieve checkpoints of guest > OSes. >=20 > So I was looking for inputs from people as to what everyone feels about > checkpointing, whether it should be done at the physical machine level or > VM level. Pros and Cons of each approach, if any further development was > done on DragonFly for checkpoint since then and if it was stopped, why? > Are there serious limitations to checkpointing a physical machine? >=20 > Sorry for such a vague posting, but I thought this would be a good > platform to get some feedback. The DragonFly lists would be the logical place to discuss DragonFly features. =46rom my perspective as a scientific computing user, VM level checkpointing is it little use since I get the overhead of the VM and I can't easily do the application level checkpointing required to checkpoing distributed programs. There are probably a number of places where it is useful in scientific computing, but I don't find it to be all that intresting. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFB5ZkpXY6L6fI4GtQRAlG9AJwKKz6OGw5jC8VzAZ1165T2BTbFXQCZAemr F540VRaEwrmV84qWnDAHlsA= =vSbz -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 12 21:40: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 2B51F16A4CE for ; Wed, 12 Jan 2005 21:40:42 +0000 (GMT) Received: from mail-svr1.cs.utah.edu (brahma.cs.utah.edu [155.98.64.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9A6243D2D for ; Wed, 12 Jan 2005 21:40:41 +0000 (GMT) (envelope-from saggarwa@cs.utah.edu) Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id E25EC346EE; Wed, 12 Jan 2005 14:40:39 -0700 (MST) Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26735-06; Wed, 12 Jan 2005 14:40:39 -0700 (MST) Received: from faith.cs.utah.edu (faith.cs.utah.edu [155.98.65.40]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 707C9346E0; Wed, 12 Jan 2005 14:40:39 -0700 (MST) Received: by faith.cs.utah.edu (Postfix, from userid 4973) id 546072EC21; Wed, 12 Jan 2005 14:40:39 -0700 (MST) Received: from localhost (localhost [127.0.0.1]) by faith.cs.utah.edu (Postfix) with ESMTP id 1EE8B34406; Wed, 12 Jan 2005 21:40:39 +0000 (UTC) Date: Wed, 12 Jan 2005 14:40:39 -0700 (MST) From: Siddharth Aggarwal To: Kip Macy In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: amavisd-new at cs.utah.edu cc: freebsd-hackers@freebsd.org Subject: Re: process checkpoint restore facility now in DragonFly BSD 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, 12 Jan 2005 21:40:42 -0000 Thanks for your reply. I understand the complexity of checkpointing a process and I do agree that capturing the complete state of a system is really difficult. So my question is that if a subset of that functinality was to be implemented (e.g. not guaranteeing certain things to processes when they restart, and I believe that you have already implemented this for DragonFly), why is it more difficult to do it for a physical machine versus in a VMM like Xen? Or do you have any arguments in the reverse direction i.e. better/easier/efficient/reliable in a physical machine than a VMM? Or do you now believe since this feature was implemented over a year ago, that a VMM is the way to go? On Wed, 12 Jan 2005, Kip Macy wrote: > I've promised Nate to port the functionality to FreeBSD. I'm busy doing some > things with the FreeBSD port to Xen at the moment. > > Checkpointing a process is intrinsically messy for reasons beyond the obvious > statefulness of TCP connections. Process state, particularly with regard to > devices, is often not cleanly associated with the process in the kernel. What > happens if a file that the process had open has gone away? Other issues abound - > checkpointing a process pipeline can be made to work, but some work would need > to be done on pipes. The list goes on. > > > -Kip > > > On Wed, 12 Jan 2005, Siddharth Aggarwal wrote: > > > > > Hi all, > > > > I am responding to a post back in Oct 2003 when the checkpointing feature > > was announced for DragonFly. I have been doing some research on this, and > > have seen some projects that use Xen VMM to achieve checkpoints of guest > > OSes. > > > > So I was looking for inputs from people as to what everyone feels about > > checkpointing, whether it should be done at the physical machine level or > > VM level. Pros and Cons of each approach, if any further development was > > done on DragonFly for checkpoint since then and if it was stopped, why? > > Are there serious limitations to checkpointing a physical machine? > > > > Sorry for such a vague posting, but I thought this would be a good > > platform to get some feedback. > > > > Thanks, > > Sid. > > _______________________________________________ > > 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" > > > > -- > "Debugging is twice as hard as writing the code in the first place. > Therefore, if you write the code as cleverly as possible, you are, > by definition, not smart enough to debug it." - Brian W. Kernighan > _______________________________________________ > 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 Wed Jan 12 21:45: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 05EB416A4CE for ; Wed, 12 Jan 2005 21:45:59 +0000 (GMT) Received: from mx1.netapp.com (mx1.netapp.com [216.240.18.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAF9F43D1D for ; Wed, 12 Jan 2005 21:45:58 +0000 (GMT) (envelope-from kmacy@netapp.com) Received: from frejya.corp.netapp.com (10.57.157.119) by mx1.netapp.com with ESMTP; 12 Jan 2005 13:45:59 -0800 X-IronPort-AV: i="3.88,118,1102320000"; d="scan'208"; a="84785274:sNHT20513692" Received: from siml3-fe.eng.netapp.com (siml3-fe.eng.netapp.com [10.56.9.153]) j0CLjwbr029200; Wed, 12 Jan 2005 13:45:58 -0800 (PST) Date: Wed, 12 Jan 2005 13:45:58 -0800 (PST) From: Kip Macy X-X-Sender: kmacy@siml3.eng.netapp.com To: Siddharth Aggarwal In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: process checkpoint restore facility now in DragonFly BSD 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, 12 Jan 2005 21:45:59 -0000 Taking this off list. -Kip On Wed, 12 Jan 2005, Siddharth Aggarwal wrote: > > Thanks for your reply. > > I understand the complexity of checkpointing a process and I do agree that > capturing the complete state of a system is really difficult. So my > question is that if a subset of that functinality was to be implemented > (e.g. not guaranteeing certain things to processes when they restart, and > I believe that you have already implemented this for DragonFly), why is it > more difficult to do it for a physical machine versus in a VMM like Xen? > Or do you have any arguments in the reverse direction i.e. > better/easier/efficient/reliable in a physical machine than a VMM? Or do > you now believe since this feature was implemented over a year ago, that a > VMM is the way to go? > > > > On Wed, 12 Jan 2005, Kip Macy wrote: > > > I've promised Nate to port the functionality to FreeBSD. I'm busy doing some > > things with the FreeBSD port to Xen at the moment. > > > > Checkpointing a process is intrinsically messy for reasons beyond the obvious > > statefulness of TCP connections. Process state, particularly with regard to > > devices, is often not cleanly associated with the process in the kernel. What > > happens if a file that the process had open has gone away? Other issues abound - > > checkpointing a process pipeline can be made to work, but some work would need > > to be done on pipes. The list goes on. > > > > > > -Kip > > > > > > On Wed, 12 Jan 2005, Siddharth Aggarwal wrote: > > > > > > > > Hi all, > > > > > > I am responding to a post back in Oct 2003 when the checkpointing feature > > > was announced for DragonFly. I have been doing some research on this, and > > > have seen some projects that use Xen VMM to achieve checkpoints of guest > > > OSes. > > > > > > So I was looking for inputs from people as to what everyone feels about > > > checkpointing, whether it should be done at the physical machine level or > > > VM level. Pros and Cons of each approach, if any further development was > > > done on DragonFly for checkpoint since then and if it was stopped, why? > > > Are there serious limitations to checkpointing a physical machine? > > > > > > Sorry for such a vague posting, but I thought this would be a good > > > platform to get some feedback. > > > > > > Thanks, > > > Sid. > > > _______________________________________________ > > > 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" > > > > > > > -- > > "Debugging is twice as hard as writing the code in the first place. > > Therefore, if you write the code as cleverly as possible, you are, > > by definition, not smart enough to debug it." - Brian W. Kernighan > > _______________________________________________ > > 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" > > > -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 13 05:20: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 6B9A116A4CE for ; Thu, 13 Jan 2005 05:20:38 +0000 (GMT) Received: from S2.cableone.net (smtp2.cableone.net [24.116.0.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id E286543D1F for ; Thu, 13 Jan 2005 05:20:37 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from fennec.local.lan (unverified [24.119.123.89]) by S2.cableone.net (CableOne SMTP Service S2) with ESMTP id 7253161 for ; Wed, 12 Jan 2005 22:41:39 -0700 Date: Wed, 12 Jan 2005 21:20:07 -0600 From: Vulpes Velox To: freebsd-hackers@freebsd.org Message-ID: <20050112212007.633c2d7b@fennec.local.lan> In-Reply-To: <20050111183439.75e6b334@fennec.local.lan> References: <20050111183439.75e6b334@fennec.local.lan> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=Multipart_Wed__12_Jan_2005_21_20_07_-0600_9jTsu5xjt8e25pgj X-IP-stats: Incoming Last 0, First 37, in=60, out=0, spam=0 X-External-IP: 24.119.123.89 X-Abuse-Info: Send abuse complaints to abuse@cableone.net Subject: Re: RC scripts and NIS 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: Thu, 13 Jan 2005 05:20:38 -0000 --Multipart_Wed__12_Jan_2005_21_20_07_-0600_9jTsu5xjt8e25pgj Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Well I got it working. It adds two more variables to rc.conf. nis_server_available_test: Toggles nis test on or off nis_avail_tester: script to use for testing If the script exits with a 1, NIS is not enabled. I am currently using a script that ,using md5, hashes the out put from arp and compares it to a good hash. Any ways, not heard any feed back on this yet. I would be really interested to hear some opinions or suggestions on this. On Tue, 11 Jan 2005 18:34:39 -0600 Vulpes Velox wrote: > I am currently am currently working on making modifications to the > rc system to allow NIS to not be started if the server is not > present. > > So far I am just looking at disabling ypbind at start if certain > conditions are meet. The idea it is to run a script that checks if > the servers or server is present and then if it is, ypbind if > enabled, if not it modifies the current variables to stop ypbind > from being run and prints a message about it to stdout. > > >From my understanding this is the one that needs disabled if the > system is to operate outside of it's usual network. Allowing it to > fall back to /etc/ for it's information. I've tested it by disabling > it upon startup manually and it worked fine. Is there any other NIS > related scripts I should make changes to, or is this the only one I > should worry about? > > If any one have opinions or any input on any of this, I would be > interested to hear it. --Multipart_Wed__12_Jan_2005_21_20_07_-0600_9jTsu5xjt8e25pgj Content-Type: application/octet-stream; name=ypbind Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=ypbind IyEvYmluL3NoCiMKIyAkTmV0QlNEOiB5cGJpbmQsdiAxLjUgMjAwMi8wMy8yMiAwNDozNDowMSB0 aG9ycGVqIEV4cCAkCiMgJEZyZWVCU0Q6IHNyYy9ldGMvcmMuZC95cGJpbmQsdiAxLjguMi4xIDIw MDQvMTAvMTAgMDk6NTA6NTQgbXRtIEV4cCAkCiMKCiMgUFJPVklERTogeXBiaW5kCiMgUkVRVUlS RTogeXBzZXJ2CiMgQkVGT1JFOiAgREFFTU9OCgouIC9ldGMvcmMuc3VicgoKbmFtZT0ieXBiaW5k Igpjb21tYW5kPSIvdXNyL3NiaW4vJHtuYW1lfSIKc3RhcnRfcHJlY21kPSJ5cGJpbmRfcHJlY21k IgoKbG9hZF9yY19jb25maWcgJG5hbWUKcmN2YXI9Im5pc19jbGllbnRfZW5hYmxlIgpjb21tYW5k X2FyZ3M9IiR7bmlzX2NsaWVudF9mbGFnc30iCgppZiBjaGVja3llc25vIG5pc19zZXJ2ZXJfYXZh aWxhYmxlX3Rlc3QgOyB0aGVuCgogICAgbmlzX2F2YWlsX3Rlc3Q9Ii9ldGMvcmMubmlzYXZhaWx0 ZXN0ZXIiCgogICAgaWYgISBgZ3JlcCAtdiAtLW1tYXAgXiMgL2V0Yy9yYy5jb25mIHwgZ3JlcCAt LW1tYXAgXm5pc19hdmFpbF90ZXN0ZXIgfCB0YWlsIC1uIDEgPiAvZGV2L251bGxgIDsgdGhlbgoJ bmlzX2F2YWlsX3Rlc3Q9ImBncmVwIC12IC0tbW1hcCBeIyAvZXRjL3JjLmNvbmYgfCBncmVwIC0t bW1hcCBebmlzX2F2YWlsX3Rlc3RlciB8IHRhaWwgLW4gMSA+IC9kZXYvbnVsbGAiCiAgICBmaQoK ICAgIGlmICEgYCRuaXNfYXZhaWxfdGVzdGA7IHRoZW4KCWVjaG8gRXhpdGluZyB5cGJpbmQgbm93 Li4uCglleGl0CiAgICBmaQoKZmkKCnlwYmluZF9wcmVjbWQoKQp7CglpZiAhIGNoZWNreWVzbm8g cnBjYmluZF9lbmFibGUgICYmIFwKCSAgICAhIC9ldGMvcmMuZC9ycGNiaW5kIGZvcmNlc3RhdHVz IDE+L2Rldi9udWxsIDI+JjEKCXRoZW4KCQlmb3JjZV9kZXBlbmQgcnBjYmluZCB8fCByZXR1cm4g MQoJZmkKCglfZG9tYWluPWBkb21haW5uYW1lYAoJaWYgWyAteiAiJF9kb21haW4iIF07IHRoZW4K CQl3YXJuICJOSVMgZG9tYWlubmFtZSgxKSBpcyBub3Qgc2V0LiIKCQlyZXR1cm4gMQoJZmkKfQoK cnVuX3JjX2NvbW1hbmQgIiQxIgo= --Multipart_Wed__12_Jan_2005_21_20_07_-0600_9jTsu5xjt8e25pgj-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 13 07:42: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 35AC816A4CE for ; Thu, 13 Jan 2005 07:42:19 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id C188943D41 for ; Thu, 13 Jan 2005 07:42:18 +0000 (GMT) (envelope-from tejas.sumant@gmail.com) Received: by rproxy.gmail.com with SMTP id r35so154092rna for ; Wed, 12 Jan 2005 23:42:14 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:from:to:subject:date:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=IcRgeXTbUTqW7y6nPJ1sCZnkdY9kZEBOjCmtbtgUVmeJsi91PpXYZd3scKscK8Zpuyzc4KMUdAHkuZohPQhrp+7/B8ziUYN6MXITbP2FzaUnUTZfImfvg4kkVxRvO90ljZq5B+l6tkt8pHujyCVktA9CfqIdrgJ8Xkcy+cd42TQ= Received: by 10.38.73.77 with SMTP id v77mr110690rna; Wed, 12 Jan 2005 23:42:14 -0800 (PST) Received: from dhruv ([61.11.17.122]) by smtp.gmail.com with ESMTP id 58sm4966rnc.2005.01.12.23.42.13; Wed, 12 Jan 2005 23:42:14 -0800 (PST) Message-ID: <009501c4f943$63581ae0$1500a8c0@indranet.local> From: "Tejas Sumant" To: Date: Thu, 13 Jan 2005 13:12:03 +0530 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Module getting loaded although init fuction returns error 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, 13 Jan 2005 07:42:19 -0000 Hi All, I am working on a FreeBSD loadable module. While loading if I encounter any error I just have returned ENXIO error. I run commond kldstat after kldload. What I observed was kldstat still shows my module in the list of loaded modules. Can anybody pls explain me this? Is it a problem with my module? Tejas From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 13 07:47: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 B948316A4CE for ; Thu, 13 Jan 2005 07:47:26 +0000 (GMT) Received: from mail22.syd.optusnet.com.au (mail22.syd.optusnet.com.au [211.29.133.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0FBC43D39 for ; Thu, 13 Jan 2005 07:47:23 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j0D7lMVp000362 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 13 Jan 2005 18:47:22 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j0D7lLxP053674; Thu, 13 Jan 2005 18:47:21 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j0D7lLRS053673; Thu, 13 Jan 2005 18:47:21 +1100 (EST) (envelope-from pjeremy) Date: Thu, 13 Jan 2005 18:47:21 +1100 From: Peter Jeremy To: Stephen McKay Message-ID: <20050113074721.GC79646@cirb503493.alcatel.com.au> References: <200501120949.j0C9nQCZ000573@dungeon.home> <200501121354.j0CDscrR002027@dungeon.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501121354.j0CDscrR002027@dungeon.home> User-Agent: Mutt/1.4.2i cc: freebsd-hackers@freebsd.org Subject: Re: Background processes setting O_NONBLOCK on ttys 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, 13 Jan 2005 07:47:26 -0000 On Wed, 2005-Jan-12 23:54:38 +1000, Stephen McKay wrote: >a) Rewrite file descriptor handling in libc_r so it does not set O_NONBLOCK >on tty file descriptors unless it is in the foreground. I don't know how >hard this would be, or whether it even applies to -current with its profusion >of threading libraries. I'll leave this to those who believe in threading. In 4.x, threads are totally userland and rely on non-blocking I/O. If background tty file descriptors block on I/O, the entire process will block, not just the thread performing I/O. This is a major POLA violation. In 5.x and later, both kernel and userland threads exist. >b) Add new non-blocking read() and write() call variants and use them in >the threading library instead of setting O_NONBLOCK. See aio_read(2), aio_write(2). >c) Make O_NONBLOCK be per file descriptor (like FD_CLOEXEC). Thus, >descriptors produced from dup() (for example) would have their own O_NONBLOCK >flag, just as two descriptors from separate open() calls have today. It might be useful to see what one of the POSIX experts think about this. FreeBSD, NetBSD, OpenBSD and Linux all explicitly state that dup(2) copies O_NONBLOCK (though Solaris 10 doesn't). It is reasonably likely that existing code relies on the documented behaviour and will therefore break when you move O_NONBLOCK from the file to the file descriptor. -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 13 08:35: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 4CBF016A4CE for ; Thu, 13 Jan 2005 08:35:00 +0000 (GMT) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72C3543D53 for ; Thu, 13 Jan 2005 08:34:59 +0000 (GMT) (envelope-from smckay@internode.on.net) Received: from dungeon.home (ppp231-141.lns1.bne1.internode.on.net [203.122.231.141])j0D8YvsW092128; Thu, 13 Jan 2005 19:04:57 +1030 (CST) Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.13.1/8.11.6) with ESMTP id j0D8YIEf007484; Thu, 13 Jan 2005 18:34:18 +1000 (EST) (envelope-from mckay) Message-Id: <200501130834.j0D8YIEf007484@dungeon.home> To: Peter Jeremy References: <200501120949.j0C9nQCZ000573@dungeon.home> <200501121354.j0CDscrR002027@dungeon.home> <20050113074721.GC79646@cirb503493.alcatel.com.au> In-Reply-To: <20050113074721.GC79646@cirb503493.alcatel.com.au> from Peter Jeremy at "Thu, 13 Jan 2005 18:47:21 +1100" Date: Thu, 13 Jan 2005 18:34:18 +1000 From: Stephen McKay cc: freebsd-hackers@freebsd.org cc: Stephen McKay Subject: Re: Background processes setting O_NONBLOCK on ttys 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, 13 Jan 2005 08:35:00 -0000 On Thursday, 13th January 2005, Peter Jeremy wrote: >On Wed, 2005-Jan-12 23:54:38 +1000, Stephen McKay wrote: >>a) Rewrite file descriptor handling in libc_r so it does not set O_NONBLOCK >>on tty file descriptors unless it is in the foreground. I don't know how >>hard this would be, or whether it even applies to -current with its profusion >>of threading libraries. I'll leave this to those who believe in threading. > >In 4.x, threads are totally userland and rely on non-blocking I/O. If >background tty file descriptors block on I/O, the entire process will >block, not just the thread performing I/O. This is a major POLA violation. Maybe yes, maybe no. The process stops with SIGTTOU. Stopped is stopped. My view is that it's a POLA violation to allow other processes to fiddle with non-blocking mode behind your back. Anyway, this problem goes away if we can have O_NONBLOCK be per file descriptor rather than per file open. Then it doesn't matter if a threaded process changes its own copy of the tty descriptor. Until then, anyone who wants to can protect themselves with my patch. It's working fine for me. :-) >In 5.x and later, both kernel and userland threads exist. I am totally lacking in info on 5.x and 6.x threading. If we can get rid of O_NONBLOCK here (or if it's already gone), then the major problem is solved. And my code to prevent non-blocking being set by background processes can be committed. (Better safe than sorry.) >>b) Add new non-blocking read() and write() call variants and use them in >>the threading library instead of setting O_NONBLOCK. > >See aio_read(2), aio_write(2). These look hard to use. I can't see how they could replace nonblocking reads using O_NONBLOCK. Even if I add kqueue() to the mix I see problems. By the way, I found a note about this from the author of djbdns. He has much the same complaints I have. See http://cr.yp.to/unix/nonblock.html >>c) Make O_NONBLOCK be per file descriptor (like FD_CLOEXEC). Thus, >>descriptors produced from dup() (for example) would have their own O_NONBLOCK >>flag, just as two descriptors from separate open() calls have today. > It might be useful to see what one of the POSIX experts think about this. >FreeBSD, NetBSD, OpenBSD and Linux all explicitly state that dup(2) >copies O_NONBLOCK (though Solaris 10 doesn't). It is reasonably likely >that existing code relies on the documented behaviour and will therefore >break when you move O_NONBLOCK from the file to the file descriptor. You can still have dup() copy the O_NONBLOCK flag. That's probably sensible. But if you did "b = dup(a)" then changed the O_NONBLOCK flag on "b" you wouldn't see that reflected on "a" (unlike now). Even after sleeping on this, I think option c) is the right answer. Stephen. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 13 11:06: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 CFBB016A4CE for ; Thu, 13 Jan 2005 11:06:00 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 161DF43D58 for ; Thu, 13 Jan 2005 11:06:00 +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 A6A211F534; Thu, 13 Jan 2005 12:05:58 +0100 (CET) Received: by turtle.stack.nl (Postfix, from userid 1677) id 8C9911CD4B; Thu, 13 Jan 2005 12:05:58 +0100 (CET) Date: Thu, 13 Jan 2005 12:05:58 +0100 From: Jilles Tjoelker To: Peter Jeremy Message-ID: <20050113110558.GA27286@stack.nl> References: <200501120949.j0C9nQCZ000573@dungeon.home> <200501121354.j0CDscrR002027@dungeon.home> <20050113074721.GC79646@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050113074721.GC79646@cirb503493.alcatel.com.au> X-Operating-System: FreeBSD 5.3-RELEASE-p2 i386 User-Agent: Mutt/1.5.6i cc: freebsd-hackers@freebsd.org cc: Stephen McKay Subject: Re: Background processes setting O_NONBLOCK on ttys 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, 13 Jan 2005 11:06:00 -0000 On Thu, Jan 13, 2005 at 06:47:21PM +1100, Peter Jeremy wrote: > On Wed, 2005-Jan-12 23:54:38 +1000, Stephen McKay wrote: > >c) Make O_NONBLOCK be per file descriptor (like FD_CLOEXEC). Thus, > >descriptors produced from dup() (for example) would have their own O_NONBLOCK > >flag, just as two descriptors from separate open() calls have today. > It might be useful to see what one of the POSIX experts think about this. > FreeBSD, NetBSD, OpenBSD and Linux all explicitly state that dup(2) > copies O_NONBLOCK (though Solaris 10 doesn't). It is reasonably likely > that existing code relies on the documented behaviour and will therefore > break when you move O_NONBLOCK from the file to the file descriptor. POSIX states that the O_NONBLOCK flag is per open file description. File descriptors created with dup(2), fork(2) or similar methods share the same open file description, while new descriptors created with open(2) do not. Consequently, a POSIX-compliant implementation of O_NONBLOCK does not solve the problem, as all descriptors to the terminal refer to the same open file description. O_NONBLOCK is indeed unusable for descriptions shared with other unknowing processes :( -- Jilles Tjoelker From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 13 12:45: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 699A716A4CE for ; Thu, 13 Jan 2005 12:45:01 +0000 (GMT) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id B324343D39 for ; Thu, 13 Jan 2005 12:45:00 +0000 (GMT) (envelope-from smckay@internode.on.net) Received: from dungeon.home (ppp231-141.lns1.bne1.internode.on.net [203.122.231.141])j0DCiwsW089760; Thu, 13 Jan 2005 23:14:59 +1030 (CST) Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.13.1/8.11.6) with ESMTP id j0DCiGga008717; Thu, 13 Jan 2005 22:44:16 +1000 (EST) (envelope-from mckay) Message-Id: <200501131244.j0DCiGga008717@dungeon.home> To: Jilles Tjoelker References: <200501120949.j0C9nQCZ000573@dungeon.home> <200501121354.j0CDscrR002027@dungeon.home> <20050113074721.GC79646@cirb503493.alcatel.com.au> <20050113110558.GA27286@stack.nl> In-Reply-To: <20050113110558.GA27286@stack.nl> from Jilles Tjoelker at "Thu, 13 Jan 2005 12:05:58 +0100" Date: Thu, 13 Jan 2005 22:44:16 +1000 From: Stephen McKay cc: Peter Jeremy cc: freebsd-hackers@freebsd.org cc: Stephen McKay Subject: Re: Background processes setting O_NONBLOCK on ttys 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, 13 Jan 2005 12:45:01 -0000 On Thursday, 13th January 2005, Jilles Tjoelker wrote: >POSIX states that the O_NONBLOCK flag is per open file description. File >descriptors created with dup(2), fork(2) or similar methods share the >same open file description, while new descriptors created with open(2) >do not. Can you quote chapter and verse on this? Or is it merely implied? A pointer to an online copy would be best. I found that "The Open Group Base Specifications Issue 6" at http://www.opengroup.org/onlinepubs/009695399/toc.htm is not clear on the matter. Also "The Single UNIX Specification, Version 2" at http://www.opengroup.org/onlinepubs/007908799/ is similarly unclear. >Consequently, a POSIX-compliant implementation of O_NONBLOCK does not >solve the problem, as all descriptors to the terminal refer to the same >open file description. O_NONBLOCK is indeed unusable for descriptions >shared with other unknowing processes :( If we must be POSIX compliant and if you accept that POSIX demands that dup'd file descriptors share a single O_NONBLOCK flag, then the logical end position is that the threads library must not routinely set stdin, stdout and stderr to non-blocking. Right? Personally, I have no qualms being non-POSIX compliant in a good cause. Wouldn't being non-POSIX on this issue be easier? Hmm. Should this be on -arch now? Stephen. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 13 16:32:03 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 AFA5E16A4CE for ; Thu, 13 Jan 2005 16:32:03 +0000 (GMT) Received: from ns.tjc.ru (ns.tjc.ru [212.30.133.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0183A43D46 for ; Thu, 13 Jan 2005 16:32:03 +0000 (GMT) (envelope-from dvg_lab@mail.ru) Received: from localhost (localhost [127.0.0.1]) by ns.tjc.ru (Postfix) with ESMTP id 1BFFEBDC18 for ; Thu, 13 Jan 2005 19:32:53 +0300 (MSK) Received: from ns.tjc.ru ([127.0.0.1]) by localhost (ns.tjc.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 95384-03 for ; Thu, 13 Jan 2005 19:32:51 +0300 (MSK) Received: from IT1 (unknown [192.168.200.53]) by ns.tjc.ru (Postfix) with ESMTP for ; Thu, 13 Jan 2005 19:32:49 +0300 (MSK) Date: Thu, 13 Jan 2005 19:31:57 +0300 From: Vyacheslav Druzhinin X-Mailer: The Bat! (v3.0.1.33) Professional Organization: DVG_Lab X-Priority: 3 (Normal) Message-ID: <19310572854.20050113193157@mail.ru> To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at tjcollection.ru Subject: FreeBSD 5.3 and some stranges logging in /var/log/messages X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Vyacheslav Druzhinin List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2005 16:32:03 -0000 Hello freebsd-hackers, I use FreeBSD 5.3-RELEASE-p4, builded with ipfw support options IPFIREWALL options IPFIREWALL_VERBOSE options IPDIVERT some times I see some strange messages in /var/log/messages, like this: ------ cut -------- Jan 12 10:01:30 ns kernel: vJan 12 10:01:30 ns kernel: ipfw: 65100 Deny TCP 212.30.133.170:3564 212.30.133.146:349 out via xl1 Jan 12 10:01:30 ns kernel: 4<6:330 11ou8>tJ Jan 12 10:01:30 ns kernel: :0 v Jan 12 10:01:30 ns kernel: 1:30 ns kernel: ipfw: 65100 Deny TCP 212.30.133.170:3565 212.30.133.146:350 out via xl1 Jan 12 10:01:30 ns kernel: :3<37 ou1t 1v8i>a J Jan 12 10:01:30 ns kernel: a:x Jan 12 10:01:30 ns kernel: l<1 Jan 12 10:01:30 ns kernel: 118>01:30 ns kernel: ipfw: 65100 Deny TCP 212.30.133.170:3572 212.30.133.146:357 out via xl1 Jan 12 10:01:30 ns kernel: 3<38 ou1t1 8>vJ Jan 12 10:01:30 ns kernel: :i Jan 12 10:01:30 ns kernel: a< xl1 Jan 12 10:01:30 ns kernel: 118>01:30 ns kernel: ipfw: 65100 Deny TCP 212.30.133.170:3573 212.30.133.146:358 out via xl1 Jan 12 10:01:30 ns kernel: 2.<30.133.1701:130>5 Jan 12 10:01:30 ns kernel: 34 212.3 Jan 12 10:01:30 ns kernel: 0<.133.14116:0>316 Jan 12 10:01:30 ns kernel: 51<00 D1e1n8>y9 Jan 12 10:01:30 ns kernel: < out v11ia0 >xl Jan 12 10:01:30 ns kernel: T31 Jan 12 10:01:30 ns kernel: < Jan 12 10:01:30 ns kernel: 110>0.133.170:3560 212.30.133.146:345 out via xl1 Jan 12 10:01:30 ns kernel: <1<10>ip1f1w8>: Jan 12 10:01:30 ns kernel: 10 Jan 12 10:01:30 ns kernel: 5: Jan 12 10:01:30 ns kernel: 0<1:30 ns11 k0>e1r Jan 12 10:01:30 ns kernel: 0<0 Den11y 8T>n Jan 12 10:01:30 ns kernel: C Jan 12 10:01:30 ns kernel: P< 212.130.181>36 Jan 12 10:01:30 ns kernel: 5<100 D11e0n>y3 Jan 12 10:01:30 ns kernel: .1<70:351691 821> 2T Jan 12 10:01:30 ns kernel: 0 Jan 12 10:01:30 ns kernel: <.30.111383.>14.1 Jan 12 10:01:30 ns kernel: <33.17110:03>546: Jan 12 10:01:30 ns kernel: <354 ou11t 8vi>a 2 Jan 12 10:01:30 ns kernel: <212.30.11130>3 Jan 12 10:01:30 ns kernel: .146:327 out via xl1 Jan 12 10:01:30 ns kernel: 57<6 212.3101.8>1J Jan 12 10:01:30 ns kernel: : Jan 12 10:01:30 ns kernel: <33.14116:8>30 Jan 12 10:01:30 ns kernel: <1:30 n11s 0>k Jan 12 10:01:30 ns kernel: <61 ou1t1 8>ve Jan 12 10:01:30 ns kernel: f Jan 12 10:01:30 ns kernel: >=--> Fido: 2:5085/20.0 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 14 01:19: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 5595516A4CE for ; Fri, 14 Jan 2005 01:19:26 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 866D043D41 for ; Fri, 14 Jan 2005 01:19:25 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id j0E1JLmr046974; Fri, 14 Jan 2005 11:49:22 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Date: Fri, 14 Jan 2005 11:49:19 +1030 User-Agent: KMail/1.7.1 References: <009501c4f943$63581ae0$1500a8c0@indranet.local> In-Reply-To: <009501c4f943$63581ae0$1500a8c0@indranet.local> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2508198.kYRrGKZQ8u"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501141149.20496.doconnor@gsoft.com.au> X-Spam-Score: -5.4 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Tejas Sumant Subject: Re: Module getting loaded although init fuction returns error 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, 14 Jan 2005 01:19:26 -0000 --nextPart2508198.kYRrGKZQ8u Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 13 Jan 2005 18:12, Tejas Sumant wrote: > I am working on a FreeBSD loadable module. > > While loading if I encounter any error I just have returned ENXIO error. > > I run commond kldstat after kldload. > > What I observed was kldstat still shows my module in the list of loaded > modules. > > Can anybody pls explain me this? What does dmesg say after you loaded it? > Is it a problem with my module? Probably. Do you have any source code that we can look at? =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2508198.kYRrGKZQ8u Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBB5x4Y5ZPcIHs/zowRAn03AKCGb9pKObSESOqjPEcu54WwB+/uRwCfaBGj ZPb1jQLskV+OC3HnIttjb3o= =zZOb -----END PGP SIGNATURE----- --nextPart2508198.kYRrGKZQ8u-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 14 02:05: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 AC08A16A4CF for ; Fri, 14 Jan 2005 02:05:23 +0000 (GMT) Received: from afields.ca (afields.ca [216.194.67.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4E2443D41 for ; Fri, 14 Jan 2005 02:05:18 +0000 (GMT) (envelope-from afields@afields.ca) Received: from afields.ca (localhost.afields.ca [127.0.0.1]) by afields.ca (8.12.11/8.12.11) with ESMTP id j0E25Gqa074691; Thu, 13 Jan 2005 21:05:16 -0500 (EST) (envelope-from afields@afields.ca) Received: (from afields@localhost) by afields.ca (8.12.11/8.12.11/Submit) id j0E25GL0074690; Thu, 13 Jan 2005 21:05:16 -0500 (EST) (envelope-from afields) Date: Thu, 13 Jan 2005 21:05:16 -0500 From: Allan Fields To: Brooks Davis Message-ID: <20050114020516.GD26802@afields.ca> References: <20050112214002.GA21038@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050112214002.GA21038@odin.ac.hmc.edu> User-Agent: Mutt/1.4i cc: freebsd-hackers@freebsd.org cc: Siddharth Aggarwal Subject: Re: process checkpoint restore facility now in DragonFly BSD 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, 14 Jan 2005 02:05:24 -0000 On Wed, Jan 12, 2005 at 01:40:02PM -0800, Brooks Davis wrote: > On Wed, Jan 12, 2005 at 02:17:38PM -0700, Siddharth Aggarwal wrote: > > > > I am responding to a post back in Oct 2003 when the checkpointing feature > > was announced for DragonFly. I have been doing some research on this, and > > have seen some projects that use Xen VMM to achieve checkpoints of guest > > OSes. > > > > So I was looking for inputs from people as to what everyone feels about > > checkpointing, whether it should be done at the physical machine level or > > VM level. Pros and Cons of each approach, if any further development was > > done on DragonFly for checkpoint since then and if it was stopped, why? > > Are there serious limitations to checkpointing a physical machine? > > > > Sorry for such a vague posting, but I thought this would be a good > > platform to get some feedback. > > The DragonFly lists would be the logical place to discuss DragonFly > features. > > From my perspective as a scientific computing user, VM level > checkpointing is it little use since I get the overhead of the VM and > I can't easily do the application level checkpointing required to > checkpoing distributed programs. There are probably a number of places > where it is useful in scientific computing, but I don't find it to be > all that intresting. IMHO, it all depends on if process checkpointing is made practical and reliable enough to be employed for non-trivial programs. I'm not entirely convinced if a single system checkpoint is the ultimate answer though that is certainly highly desirable. One potential drawback with full system images is the lack of support for runtime checkpoints (multiple process checkpoints) and the lack of a framework for process migration and/or persistence of a subset of the processes on a system. Persistence is almost non-existent at all levels and sessioning weak. A whole solution is needed (integrating the two). The work thus far shouldn't be brushed off so easily as a multi-tiered approach could be of benefit. Each level of persistence offers it's own pros and cons: - Scope & Granularity of operation (degrees flexibility in specification, checkpoint set); - Storage options; - Interface; - Means of Coordination; - etc. For process checkpoint: The means to coordinate checkpoints and satisfy order of dependency between processes under checkpoint is a next step in the implementation path. Building on previous email: * Process Checkpointing Support: [..] An often overlooked application to process-level persistence is fault-tolerance. It might be possible to have a process survive an otherwise fatal system panic and/or hardware failure. [With-out having to resume from a whole system checkpoint.] [..] > -- Brooks > > -- > Any statement of the form "X is the one, true Y" is FALSE. > PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 -- Allan Fields, AFRSL - http://afields.ca 2D4F 6806 D307 0889 6125 C31D F745 0D72 39B4 5541 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 14 02:58: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 745F816A4CE for ; Fri, 14 Jan 2005 02:58:17 +0000 (GMT) Received: from web52710.mail.yahoo.com (web52710.mail.yahoo.com [206.190.39.161]) by mx1.FreeBSD.org (Postfix) with SMTP id E636243D2F for ; Fri, 14 Jan 2005 02:58:16 +0000 (GMT) (envelope-from kamalpr@yahoo.com) Received: (qmail 99193 invoked by uid 60001); 14 Jan 2005 02:58:15 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=F19EozxM6dcKG1nxcV/NKyeP4eLa0DDTPWbQnzPBLCKUdSKJawfBpUFGL1NfuoA86By7JsfUUwRlSoKIhTZzEhEtZ7Ippn5kyzaPshF4IlO/rGrkrd1GduSofzTeX2Tn4JENiIGbDBDOx6lVGk9ePMSU0zJRp/Iw+VvqzdfU3b4= ; Message-ID: <20050114025815.99191.qmail@web52710.mail.yahoo.com> Received: from [203.195.199.244] by web52710.mail.yahoo.com via HTTP; Thu, 13 Jan 2005 18:58:15 PST Date: Thu, 13 Jan 2005 18:58:15 -0800 (PST) From: "Kamal R. Prasad" To: Allan Fields , Brooks Davis In-Reply-To: <20050114020516.GD26802@afields.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-hackers@freebsd.org cc: Siddharth Aggarwal Subject: Re: process checkpoint restore facility now in DragonFly BSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kamalp@acm.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 02:58:17 -0000 --- Allan Fields wrote: > On Wed, Jan 12, 2005 at 01:40:02PM -0800, Brooks > Davis wrote: > > On Wed, Jan 12, 2005 at 02:17:38PM -0700, > Siddharth Aggarwal wrote: > > > > > > I am responding to a post back in Oct 2003 when > the checkpointing feature > > > was announced for DragonFly. I have been doing > some research on this, and > > > have seen some projects that use Xen VMM to > achieve checkpoints of guest > > > OSes. > > > > > > So I was looking for inputs from people as to > what everyone feels about > > > checkpointing, whether it should be done at the > physical machine level or > > > VM level. Pros and Cons of each approach, if any > further development was > > > done on DragonFly for checkpoint since then and > if it was stopped, why? > > > Are there serious limitations to checkpointing a > physical machine? > > > > > > Sorry for such a vague posting, but I thought > this would be a good > > > platform to get some feedback. > > > > The DragonFly lists would be the logical place to > discuss DragonFly > > features. > > > > From my perspective as a scientific computing > user, VM level > > checkpointing is it little use since I get the > overhead of the VM and > > I can't easily do the application level > checkpointing required to > > checkpoing distributed programs. There are > probably a number of places > > where it is useful in scientific computing, but I > don't find it to be > > all that intresting. > Process level checkpointing can be useful -but the techniques so far have not integrated checkpointing into the UNIX kernel. > IMHO, it all depends on if process checkpointing is > made practical > and reliable enough to be employed for non-trivial > programs. I'm > not entirely convinced if a single system checkpoint > is the > ultimate answer though that is certainly highly > desirable. > It can be made practical if it happens to be user-directed checkpointing at the process level. The system would have to assist in recovering checkpointed programs. > One potential drawback with full system images is > the lack of > support for runtime checkpoints (multiple process > checkpoints) and > the lack of a framework for process migration and/or > persistence > of a subset of the processes on a system. > Yes. Somehow, attempts to provide that functionality have involved providing a library rather than kernel support. > Persistence is almost non-existent at all levels and > sessioning > weak. A whole solution is needed (integrating the > two). The work > thus far shouldn't be brushed off so easily as a > multi-tiered approach > could be of benefit. > > Each level of persistence offers it's own pros and > cons: > - Scope & Granularity of operation (degrees > flexibility in > specification, checkpoint set); > - Storage options; > - Interface; - Means of Coordination; > - etc. > > For process checkpoint: The means to coordinate > checkpoints and > satisfy order of dependency between processes under > checkpoint is > a next step in the implementation path. > Is there any implementation of checkpointing standalone processes at the system level i.e. that the OS provides the functionality? > Building on previous email: > * Process Checkpointing Support: > [..] > An often overlooked application to > process-level persistence > is fault-tolerance. It might be possible to > have a process > survive an otherwise fatal system panic > and/or hardware > failure. [With-out having to resume from a whole > system > checkpoint.] > [..] > either that, or the process itself may crash after a stray input [like a denial of service attack] and it should be given a chance to skip processing input that can cause it to crash. [Hope this makes sense]. regards -kamal > > > -- Brooks > > > > -- > > Any statement of the form "X is the one, true Y" > is FALSE. > > PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 > 5D8E 8BE9 F238 1AD4 > > -- > Allan Fields, AFRSL - http://afields.ca > 2D4F 6806 D307 0889 6125 C31D F745 0D72 39B4 5541 > _______________________________________________ > 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" > __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 14 04:15:03 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 13E7E16A4CF for ; Fri, 14 Jan 2005 04:15:03 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FEDD43D2F for ; Fri, 14 Jan 2005 04:15:00 +0000 (GMT) (envelope-from zbeeble@gmail.com) Received: by wproxy.gmail.com with SMTP id 58so704574wri for ; Thu, 13 Jan 2005 20:14:59 -0800 (PST) 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:references; b=L0y36jW6fu+T0iLl+3NTMvXPgV4vTELLium9H2JhLjw2Qj38rnQIwTNLQmBOVDKZftgxUyA5o37aQCEdtbOkepdiQ6lkMH4qNZ9QW3Zl0YRdYiKjAUhfV/hWvRe+RrkDqqnhdvxE/Qz1wBde3LOnB4txit+dM9tcLu3ftph929g= Received: by 10.54.2.54 with SMTP id 54mr29194wrb; Thu, 13 Jan 2005 20:14:59 -0800 (PST) Received: by 10.54.45.13 with HTTP; Thu, 13 Jan 2005 20:14:59 -0800 (PST) Message-ID: <5f67a8c405011320144fedeb49@mail.gmail.com> Date: Thu, 13 Jan 2005 23:14:59 -0500 From: Zaphod Beeblebrox To: kamalp@acm.org In-Reply-To: <20050114025815.99191.qmail@web52710.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050114020516.GD26802@afields.ca> <20050114025815.99191.qmail@web52710.mail.yahoo.com> cc: freebsd-hackers@freebsd.org cc: Allan Fields cc: Siddharth Aggarwal Subject: Re: process checkpoint restore facility now in DragonFly BSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Zaphod Beeblebrox List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 04:15:03 -0000 Having a process (or full system) checkpoint facility would make the implementation of suspend-to-disk rather trivial --- which is a much desired feature. From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 14 06:00: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 5A5A616A4CE for ; Fri, 14 Jan 2005 06:00:26 +0000 (GMT) Received: from priv-edtnes46.telusplanet.net (defout.telus.net [199.185.220.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFDA243D49 for ; Fri, 14 Jan 2005 06:00:25 +0000 (GMT) (envelope-from pfak@telus.net) Received: from [192.168.1.150] (really [64.180.28.217]) by priv-edtnes46.telusplanet.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP <20050114060025.EJZG18545.priv-edtnes46.telusplanet.net@[192.168.1.150]>; Thu, 13 Jan 2005 23:00:25 -0700 Message-ID: <41E75FFD.1050403@telus.net> Date: Thu, 13 Jan 2005 22:00:29 -0800 From: Peter Kieser User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Siddharth Aggarwal References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: process checkpoint restore facility now in DragonFly BSD 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, 14 Jan 2005 06:00:26 -0000 freebsd-hackers != DragonFly BSD Mailing List... --Peter Siddharth Aggarwal wrote: >Hi all, > >I am responding to a post back in Oct 2003 when the checkpointing feature >was announced for DragonFly. I have been doing some research on this, and >have seen some projects that use Xen VMM to achieve checkpoints of guest >OSes. > >So I was looking for inputs from people as to what everyone feels about >checkpointing, whether it should be done at the physical machine level or >VM level. Pros and Cons of each approach, if any further development was >done on DragonFly for checkpoint since then and if it was stopped, why? >Are there serious limitations to checkpointing a physical machine? > >Sorry for such a vague posting, but I thought this would be a good >platform to get some feedback. > >Thanks, >Sid. >_______________________________________________ >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 Jan 14 09:15: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 780DD16A4CE for ; Fri, 14 Jan 2005 09:15:40 +0000 (GMT) Received: from home.dino.sk (home.dino.sk [213.215.74.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBB4243D5C for ; Fri, 14 Jan 2005 09:15:39 +0000 (GMT) (envelope-from bsd@dino.sk) Received: from [127.0.0.1] ([127.0.0.1]) by home.dino.sk with esmtp; Fri, 14 Jan 2005 10:15:39 +0100 id 0000E89B.41E78DBB.00001C30 From: Milan Obuch To: hackers@freebsd.org Date: Fri, 14 Jan 2005 10:15:37 +0100 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200501141015.37516.bsd@dino.sk> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Geode integrated peripherals support? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 09:15:40 -0000 Hi, is someone working with Geode processors? There are many peripherals integrated, but not all supported under FreeBSD. Has someone already done some patched for this? Regards, Milan From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 14 11:57: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 964F316A4CE for ; Fri, 14 Jan 2005 11:57:11 +0000 (GMT) Received: from afields.ca (afields.ca [216.194.67.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FF6A43D41 for ; Fri, 14 Jan 2005 11:57:11 +0000 (GMT) (envelope-from afields@afields.ca) Received: from afields.ca (localhost.afields.ca [127.0.0.1]) by afields.ca (8.12.11/8.12.11) with ESMTP id j0EBv3to076234; Fri, 14 Jan 2005 06:57:03 -0500 (EST) (envelope-from afields@afields.ca) Received: (from afields@localhost) by afields.ca (8.12.11/8.12.11/Submit) id j0EBv3iA076233; Fri, 14 Jan 2005 06:57:03 -0500 (EST) (envelope-from afields) Date: Fri, 14 Jan 2005 06:57:02 -0500 From: Allan Fields To: Peter Kieser Message-ID: <20050114115702.GE26802@afields.ca> References: <41E75FFD.1050403@telus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41E75FFD.1050403@telus.net> User-Agent: Mutt/1.4i cc: freebsd-hackers@freebsd.org cc: Siddharth Aggarwal Subject: Re: process checkpoint restore facility now in DragonFly BSD 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, 14 Jan 2005 11:57:11 -0000 On Thu, Jan 13, 2005 at 10:00:29PM -0800, Peter Kieser wrote: > freebsd-hackers != DragonFly BSD Mailing List... > --Peter I'd also agree further discussion on DragonFly's checkpoint facility be taken to DragonFly lists unless/until FreeBSD decides on implementing a similar framework. That was the original intent of this thread from what I can see. It's been discussed previously on the FreeBSD lists. In a previous post to DragonFly lists I suggested such features might need be developed further before potentially finding interest in the wider BSD arena. *BSD should implement and refine (in a BSD style) these types of advanced features for their merits, not only because they exist elsewhere. So basically, for the FreeBSD project, this could imply holding off and/or reworking the facility until it is made less experimental, though this assumes some implicit set of flaws in the DragonFly implementation which with time may be disproven. Some technical caveats have been enunciated previously on list. > Siddharth Aggarwal wrote: > > >Hi all, > > > >I am responding to a post back in Oct 2003 when the checkpointing feature > >was announced for DragonFly. I have been doing some research on this, and > >have seen some projects that use Xen VMM to achieve checkpoints of guest > >OSes. > > > >So I was looking for inputs from people as to what everyone feels about > >checkpointing, whether it should be done at the physical machine level or > >VM level. Pros and Cons of each approach, if any further development was > >done on DragonFly for checkpoint since then and if it was stopped, why? > >Are there serious limitations to checkpointing a physical machine? > > > >Sorry for such a vague posting, but I thought this would be a good > >platform to get some feedback. DragonFly has many experimental features. > >Thanks, > >Sid. -- Allan Fields, AFRSL - http://afields.ca 2D4F 6806 D307 0889 6125 C31D F745 0D72 39B4 5541 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 14 13:59: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 5ADDC16A4CE for ; Fri, 14 Jan 2005 13:59:46 +0000 (GMT) Received: from ferengi.borderworlds.dk (ferengi.borderworlds.dk [80.166.152.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F5CD43D41 for ; Fri, 14 Jan 2005 13:59:45 +0000 (GMT) (envelope-from xi@borderworlds.dk) Received: from borg.borderworlds.dk (localhost [127.0.0.1]) by ferengi.borderworlds.dk (Postfix) with ESMTP id E856FB819 for ; Fri, 14 Jan 2005 14:59:42 +0100 (CET) Received: by borg.borderworlds.dk (Postfix, from userid 1001) id 7364111434; Fri, 14 Jan 2005 14:59:42 +0100 (CET) Sender: xi@borderworlds.dk To: freebsd-hackers@freebsd.org References: <20050114020516.GD26802@afields.ca> <20050114025815.99191.qmail@web52710.mail.yahoo.com> <5f67a8c405011320144fedeb49@mail.gmail.com> From: Christian Laursen Date: 14 Jan 2005 14:59:42 +0100 In-Reply-To: <5f67a8c405011320144fedeb49@mail.gmail.com> Message-ID: <86acrcdsc1.fsf@borg.borderworlds.dk> Lines: 10 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: process checkpoint restore facility now in DragonFly BSD 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, 14 Jan 2005 13:59:46 -0000 Zaphod Beeblebrox writes: > Having a process (or full system) checkpoint facility would make the > implementation of suspend-to-disk rather trivial --- which is a much > desired feature. I would definitely use such a feature if it was added to FreeBSD. -- Christian Laursen From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 14 16:27: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 463D016A4CE for ; Fri, 14 Jan 2005 16:27:35 +0000 (GMT) Received: from mail-svr1.cs.utah.edu (mail-svr1.cs.utah.edu [155.98.64.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CC4643D1D for ; Fri, 14 Jan 2005 16:27:35 +0000 (GMT) (envelope-from saggarwa@cs.utah.edu) Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 7036F346FD for ; Fri, 14 Jan 2005 09:27:34 -0700 (MST) Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05850-09 for ; Fri, 14 Jan 2005 09:27:34 -0700 (MST) Received: from faith.cs.utah.edu (faith.cs.utah.edu [155.98.65.40]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 3377D346E0 for ; Fri, 14 Jan 2005 09:27:34 -0700 (MST) Received: by faith.cs.utah.edu (Postfix, from userid 4973) id 152CD2EC21; Fri, 14 Jan 2005 09:27:34 -0700 (MST) Received: from localhost (localhost [127.0.0.1]) by faith.cs.utah.edu (Postfix) with ESMTP id 0B6F134406 for ; Fri, 14 Jan 2005 16:27:34 +0000 (UTC) Date: Fri, 14 Jan 2005 09:27:33 -0700 (MST) From: Siddharth Aggarwal To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: amavisd-new at cs.utah.edu Subject: getting mount points in kernel 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, 14 Jan 2005 16:27:35 -0000 Hi all, Is there a system call to get all the mount points? In a user app, I guess I would probably parse the /etc/fstab, but how do I do it in the kernel? TIA, Sid. From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 14 16:45: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 9872416A4CE for ; Fri, 14 Jan 2005 16:45:47 +0000 (GMT) Received: from smtpout-1.priv.cc.uic.edu (smtpout-1.cc.uic.edu [128.248.155.232]) by mx1.FreeBSD.org (Postfix) with SMTP id 5A51143D49 for ; Fri, 14 Jan 2005 16:45:46 +0000 (GMT) (envelope-from zholla1@uic.edu) Received: (qmail 25960 invoked from network); 14 Jan 2005 10:45:45 -0600 Received: from icarus.cc.uic.edu (128.248.155.80) by smtpout-1.cc.uic.edu with SMTP; 14 Jan 2005 10:45:45 -0600 Date: Fri, 14 Jan 2005 10:45:45 -0600 (CST) From: Zera William Holladay X-X-Sender: zholla1@icarus.cc.uic.edu To: Siddharth Aggarwal In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: getting mount points in kernel 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, 14 Jan 2005 16:45:47 -0000 On Fri, 14 Jan 2005, Siddharth Aggarwal wrote: > > Hi all, > > Is there a system call to get all the mount points? In a user app, I guess > I would probably parse the /etc/fstab, but how do I do it in the kernel? Is are you looking for "man 2 getfsstat"? Entries in /etc/fstab are not nessarily mounted, like a CDROM. -zh From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 14 18:10: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 A885A16A4CE for ; Fri, 14 Jan 2005 18:10:44 +0000 (GMT) Received: from mailserv1.neuroflux.com (ns2.neuroflux.com [204.228.228.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AF6A43D3F for ; Fri, 14 Jan 2005 18:10:44 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 77103 invoked by uid 89); 14 Jan 2005 18:09:13 -0000 Received: from unknown (HELO www2.neuroflux.com) (127.0.0.1) by localhost with SMTP; 14 Jan 2005 18:09:13 -0000 Received: from 208.4.77.66 (SquirrelMail authenticated user ryans@gamersimpact.com); by www2.neuroflux.com with HTTP; Fri, 14 Jan 2005 11:09:13 -0700 (MST) Message-ID: <49415.208.4.77.66.1105726153.squirrel@208.4.77.66> In-Reply-To: References: Date: Fri, 14 Jan 2005 11:09:13 -0700 (MST) From: "Ryan Sommers" To: "Siddharth Aggarwal" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: freebsd-hackers@freebsd.org Subject: Re: getting mount points in kernel 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, 14 Jan 2005 18:10:44 -0000 Siddharth Aggarwal said: > > Hi all, > > Is there a system call to get all the mount points? In a user app, I guess > I would probably parse the /etc/fstab, but how do I do it in the kernel? > > TIA, > Sid. >From userland: man getmntinfo, man getfsstat >From kernel land: I'd have a look at the code for the syscall. -- Ryan Sommers ryans@gamersimpact.com From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 14 23:31: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 1C67216A4CE for ; Fri, 14 Jan 2005 23:31:55 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BD3343D46 for ; Fri, 14 Jan 2005 23:31:54 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0ENTmaC006374; Fri, 14 Jan 2005 16:29:48 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Fri, 14 Jan 2005 16:29:46 -0700 (MST) Message-Id: <20050114.162946.115909881.imp@harmony.village.org> To: bsd@dino.sk From: Warner Losh In-Reply-To: <200501141015.37516.bsd@dino.sk> References: <200501141015.37516.bsd@dino.sk> 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 X-Mailman-Approved-At: Sat, 15 Jan 2005 15:07:45 +0000 cc: hackers@freebsd.org Subject: Re: Geode integrated peripherals support? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 23:31:55 -0000 > is someone working with Geode processors? There are many peripherals > integrated, but not all supported under FreeBSD. Has someone already done > some patched for this? We use the geode and haven't noticed the lack. What's missing? Warner From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 15 18:44: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 C676716A4CE; Sat, 15 Jan 2005 18:44:31 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BD2D43D1D; Sat, 15 Jan 2005 18:44:31 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j0FImSNU011575; Sat, 15 Jan 2005 11:48:28 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41E96426.5020508@freebsd.org> Date: Sat, 15 Jan 2005 11:42:46 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org References: <41DA5C4D.1060606@freebsd.org> In-Reply-To: <41DA5C4D.1060606@freebsd.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: "current@freebsd.org" Subject: Last call! [Re: Call for FreeBSD status reports] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: monthly@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jan 2005 18:44:31 -0000 All, This is a last call for status report submissions. If you intend to submit one, please do it in the next 12 hours. Thanks, Scott Scott Long wrote: > All, > > It's time again for the bi-monthly status reports. The July-Oct 2004 > status reports were preempted by the 5.3 release, so this one is open > for anything that has happened since June. As always, submissions > having to do with FreeBSD development, documentation, organized events, > etc, are welcome and highly encouraged. Submissions are due by Jan 15 > to monthly@freebsd.org > > There are also a couple of changes to announce. First is that Tom > Rhodes and Max Laier have volunteered to help run the status reports and > keep them more timely. Many thanks to Tom and Max for offering to > help. Second is that a couple of new attributes have been added to the > XML thanks to Max. The first is a project category attribute that will > enable us to group the submissions into categories and render the full > report with these categories for easier viewing. You can choose to use > whatever category tag fits your report best, or omit it entirely and let > us take care of it. The category mapping is listed below. Feel free to > suggest additional categories. > > proj - Projects (non-specific) > docs - Documentation > kern - Kernel > arch - Architectures > ports - Ports > vendor - Vendor / 3rd party software > misc - Miscellaneous > > The second new attribute lets you lists tasks for your project that > others can help with. An example is provided in the template under the > and tags. > > The template is available at > http://www.freebsd.org/news/status/report-sample.xml. I've just > committed the updated version with the new tags, so it might take a few > hours for it to reach the website for downloading. > > Submissions are due on Jan 15. Thanks a lot, and we are looking for a > big turn-out. > > Scott