From owner-freebsd-hackers Sun Dec 9 0:11:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7C00437B416 for ; Sun, 9 Dec 2001 00:11:36 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fB98BYD35974; Sun, 9 Dec 2001 00:11:34 -0800 (PST) (envelope-from dillon) Date: Sun, 9 Dec 2001 00:11:34 -0800 (PST) From: Matthew Dillon Message-Id: <200112090811.fB98BYD35974@apollo.backplane.com> To: D J Hawkey Jr Cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD performs worse that Linux - Patches #2 & #3 References: <20011206114725.A836@sheol.localdomain> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Hello all. : :I read with interest (and fair ignorance ;-) ) the thread about delayed :ACKs in the TCP/IP stack. :... :If Matt or any other qualified hackers can make the time to double-check :my patches, I'd appreciate it. Matt's first patch didn't apply (no NewReno :in 4.2REL), and the third patch (to tcp_input.c) required a little more work :(I changed tests for 'tcp_delack_enabled' to 'DELAY_ACK()'). I'd just like :some assurance I got it right. : :All in all, kudos to Matt for this. In day-to-day use, I can "feel" the :improvementi, and everything seems as solid as ever! : :Dave Ach. If you want my specific attention (or any FreeBSD developer's specific attention) you should always Cc: the person specifically. Otherwise my mail filter won't put it in my personal mail box :-) In anycase, your patches look fine. In fact, you not only applied my fixes you also applied a fix in the delayed-ack check that was made (by someone else) some time after 4.2Rel -- the callout_pending() check in DELAY_ACK() fixed a serious bug in prior releases all by itself. Kudos! I'm glad people have been testing this and getting such good results. I MFC'd it fairly quickly into stable (because TCP was seriously messed up) and its nice to get feedback that justifies the decision. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 0:16:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 7C20037B417; Sun, 9 Dec 2001 00:16:16 -0800 (PST) Received: from pool0162.cvx40-bradley.dialup.earthlink.net ([216.244.42.162] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Cz8A-0003OC-00; Sun, 09 Dec 2001 00:16:14 -0800 Message-ID: <3C131DD5.B1569FF8@mindspring.com> Date: Sun, 09 Dec 2001 00:16:21 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Robert Watson , Poul-Henning Kamp , Dave Rufino , freebsd-hackers@FreeBSD.ORG Subject: Re: statefulness in character device drivers References: <20011208054108.C92148@elvis.mu.org> <20011208223850.N92148@elvis.mu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > I'd be glad to assist in any way possible to get this integrated, > we've really been wanting this for various reasons (mostly linnex > compat) let me know if you're too busy and I can try to take over > from your existing work. Point being, I want this done ASAP. :) Not to mention that it'd be really, really nice to be able to run multiple guest OSs under VMWARE under FreeBSD at the same time... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 0:21:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AB48837B416 for ; Sun, 9 Dec 2001 00:21:39 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fB98LbQ36051; Sun, 9 Dec 2001 00:21:37 -0800 (PST) (envelope-from dillon) Date: Sun, 9 Dec 2001 00:21:37 -0800 (PST) From: Matthew Dillon Message-Id: <200112090821.fB98LbQ36051@apollo.backplane.com> To: Terry Lambert Cc: Varshavchick Alexander , freebsd-hackers@FreeBSD.ORG Subject: Re: 4G phisical memory kernel trap References: <3C0F2E1B.7F933520@mindspring.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Varshavchick Alexander wrote: :> > For this to work, you really MUST address the machdep.c problems. :> :> So how can it be done, are there any patches for machdep.c, or is it :> solved in 4.4-stable kernel? : :Matt Dillon took a sideways stab at addressing a bit of these :issues. They didn't do everything that I thought was needed, :but he posted the diffs to the -current list, and may have :committed them to -current (look for them there). It's fixed in -stable and -current. Basically I comitted code that puts a cap on the size of certain KVM blocks that were previously scaled according to the amount of physical memory. Since KVM is limited to the upper quarter of VM (1G) by default, the scaling of these structures blew out our KVM space and paniced machines with large amounts of memory. I also cut the size of the swap map reservation in half. It isn't perfect, but I've tested it on 4G machines and it does work. What we really need to do is rearrange the kernel such that we can calculate all the KVM requirements and scale them properly before actually trying to allocate any of them. :sometimes useful). I will cover where and how to do this for :non-4M pages, in my article. Go for it! I look forward to reading your article Terry! :-- Terry -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 2:58:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bgzone.com (www.bgzone.com [217.79.65.49]) by hub.freebsd.org (Postfix) with ESMTP id 37A5937B416 for ; Sun, 9 Dec 2001 02:58:03 -0800 (PST) Received: from earth.rila.bg (root@localhost [127.0.0.1]) by bgzone.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with SMTP id OAA01454 for ; Sun, 9 Dec 2001 14:58:32 +0200 Date: Sun, 9 Dec 2001 12:57:48 +0200 From: Dimitar Peikov To: hackers@freebsd.org Subject: Performance issue Message-Id: <20011209125748.3d326e32.mitko@bgzone.com> Reply-To: mitko@rila.bg Organization: 4 Net X-Mailer: Sylpheed version 0.6.5 (GTK+ 1.2.10; i386--freebsd4.4) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart_Sun__9_Dec_2001_12:57:48_+0200_08221800" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --Multipart_Sun__9_Dec_2001_12:57:48_+0200_08221800 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, It seems to me that something in memory allocation algorith is not right. When allocate memory using malloc() without touching it FreeBSD is faster than Linuxes. But when some access to this allocated memory is needed (in most cases when have to perform calculations on huge amount of data), something is going not very well. It happends that the same program with the same input data works a times slower than on Linux box. The hardware on both machines is the same, even more Linux box has less memory. And when swapping is going to transfer data from swap area into phisical memory, I think that the things are going much slower, I mean that FreeBSD is doing this slower. I'm trying to find the difference between both implementations on both allocation algorithms, to find the answer why the things are going so. If someone can explain me in more detail both swapping and allocation algorithms currently in use in FreeBSD (I've read /usr/src/lib/libc/stdlib/malloc.c and have compl! etely agreed with it, with 1 exception), please help me. PS: I'm not trying to compare both OS-es but I'm curious on this performance issue. On FreeBSD 4.4 Stable from Nov 22 2001 -------------------------------------------- 1000000 iterations without bzero : FreeBSD$ time ./malloc_test real 0m5.706s user 0m3.169s sys 0m2.487s -------------------------------------------- 10000 iterations with bzero : FreeBSD$ time ./malloc_test real 0m47.915s user 0m12.369s sys 0m34.681s -------------------------------------------- On SuSE Linux host1 2.4.0 -------------------------------------------- 1000000 iterations without bzero : SuSE$ time malloc_test real 0m14.417s user 0m1.370s sys 0m13.040s -------------------------------------------- 10000 iterations with bzero : SuSE$ time malloc_test real 0m34.364s user 0m3.630s sys 0m30.710s -------------------------------------------- -- Dimitar Peikov Programmer Analyst Globalization Group "We Build e-Business" RILA Solutions 27 Building, Acad.G.Bonchev Str. 1113 Sofia, Bulgaria phone: (+359 2) 9797320 phone: (+359 2) 9797300 fax: (+359 2) 9733355 http://www.rila.com --Multipart_Sun__9_Dec_2001_12:57:48_+0200_08221800 Content-Type: application/octet-stream; name="malloc_test.c" Content-Disposition: attachment; filename="malloc_test.c" Content-Transfer-Encoding: base64 I2luY2x1ZGUgPHN0ZGxpYi5oPgoKI2RlZmluZSBNQUxMT0NfU0laRSAxMDI0KjEwMjQKCmludCBt YWluKGludCBhcmdjLCBjaGFyICoqYXJndikgewogIGNoYXIgKnB0cjEsICpwdHIyOwogIGludCBp OwoKICBwdHIxID0gKGNoYXIgKikgbWFsbG9jKE1BTExPQ19TSVpFKTsKICBiemVybyhwdHIxLCBN QUxMT0NfU0laRSk7CiAgZm9yIChpPTA7IGk8MTAwMDA7IGkrKykgewogICAgcHRyMiA9IChjaGFy ICopIG1hbGxvYyhNQUxMT0NfU0laRSk7CiAgICBiemVybyhwdHIyLCBNQUxMT0NfU0laRSk7CiAg ICBmcmVlKHB0cjEpOwogICAgcHRyMSA9IHB0cjI7CiAgfQogIGZyZWUocHRyMSk7Cn0K --Multipart_Sun__9_Dec_2001_12:57:48_+0200_08221800-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 3:44:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id A1C3137B405 for ; Sun, 9 Dec 2001 03:44:24 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fB9Bgpj72362; Sun, 9 Dec 2001 12:42:51 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mitko@rila.bg Cc: hackers@FreeBSD.ORG Subject: Re: Performance issue In-Reply-To: Your message of "Sun, 09 Dec 2001 12:57:48 +0200." <20011209125748.3d326e32.mitko@bgzone.com> Date: Sun, 09 Dec 2001 12:42:50 +0100 Message-ID: <72360.1007898170@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG There are many effects that could cause this, for instance if FreeBSD manages to align things differently in relation to the CPU cache you could get some very interesting waste of time that way. Based on the data you show me, I can't really say that something is wrong or right either way. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 4:49:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bgzone.com (www.bgzone.com [217.79.65.49]) by hub.freebsd.org (Postfix) with ESMTP id 7D09C37B505 for ; Sun, 9 Dec 2001 04:49:28 -0800 (PST) Received: from earth.rila.bg (root@localhost [127.0.0.1]) by bgzone.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with SMTP id QAA01727; Sun, 9 Dec 2001 16:49:12 +0200 Date: Sun, 9 Dec 2001 14:48:26 +0200 From: Dimitar Peikov To: Poul-Henning Kamp Cc: hackers@freebsd.org Subject: Re: Performance issue Message-Id: <20011209144826.557a6ff2.mitko@bgzone.com> In-Reply-To: <72360.1007898170@critter.freebsd.dk> References: <20011209125748.3d326e32.mitko@bgzone.com> <72360.1007898170@critter.freebsd.dk> Reply-To: mitko@rila.bg Organization: 4 Net X-Mailer: Sylpheed version 0.6.5 (GTK+ 1.2.10; i386--freebsd4.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 09 Dec 2001 12:42:50 +0100 Poul-Henning Kamp wrote: > > There are many effects that could cause this, for instance if FreeBSD > manages to align things differently in relation to the CPU cache you > could get some very interesting waste of time that way. Yes, I agree that in this case performance lost can be found in CPU Cache, but this can be true and when run on Linux, isn't it? > > Based on the data you show me, I can't really say that something is > wrong or right either way. Before I post this, I've got several experiments about that and the bottleneck was memory operations. The rest of my algorithm got near the same results. When perform only (malloc/free) operations without any touch of that allocated memory, there is no problem. The problem becames when you try to access it and only for the first memory hit. There is no mather if only one byte or whole memory block should be accessed, the difference is constantly the same. Or the problem is on all FreeBSD boxes installed near me? > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. -- Dimitar Peikov Programmer Analyst Globalization Group "We Build e-Business" RILA Solutions 27 Building, Acad.G.Bonchev Str. 1113 Sofia, Bulgaria phone: (+359 2) 9797320 phone: (+359 2) 9797300 fax: (+359 2) 9733355 http://www.rila.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 5:12:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from chrobd01.vailsys.com (chrobd01.vailsys.com [63.210.102.138]) by hub.freebsd.org (Postfix) with ESMTP id 6437537B405 for ; Sun, 9 Dec 2001 05:11:47 -0800 (PST) Received: from area51.vail (area51.vail [192.168.129.30]) by chrobd01.vailsys.com (Postfix) with ESMTP id 0022A4977 for ; Sun, 9 Dec 2001 07:11:40 -0600 (CST) Received: from cb293842-b.rmdws1.il.home.com (root@gamera.vail [172.16.15.1]) by area51.vail (8.9.3/8.9.3) with ESMTP id HAA49078 for ; Sun, 9 Dec 2001 07:11:40 -0600 (CST) (envelope-from hal@vailsys.com) Received: (from hal@localhost) by cb293842-b.rmdws1.il.home.com (8.11.4/8.11.3) id fB9DBgH29542; Sun, 9 Dec 2001 07:11:42 -0600 (CST) X-Authentication-Warning: cb293842-b.rmdws1.il.home.com: hal set sender to hal@vailsys.com using -f To: hackers@FreeBSD.ORG Subject: Re: cable modem connection problem References: <20011206071926.QTHW27606.mta05-svc.ntlworld.com@there> <3C0F7966.908CD6E6@bturtle.ch> <3C1005ED.4090001@isi.edu> <20011207000918.JIID10846.mta07-svc.ntlworld.com@there> <3C100F4D.3080900@isi.edu> <85k7vyzspp.fsf@stiegl.niksun.com> From: Hal Snyder Date: 09 Dec 2001 07:11:41 -0600 In-Reply-To: <85k7vyzspp.fsf@stiegl.niksun.com> (Andrew Heybey's message of "07 Dec 2001 15:21:54 -0500") Message-ID: <87n10s8rn6.fsf@cb293842-b.rmdws1.il.home.com> Lines: 36 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrew Heybey writes: >> > Somebody mentioned on this list that deleting the arp table entry >> > of the default router of the cable modem provider (as a cron job) >> > solved the problem. I had not tried arp deletion but noticed severe slowdown or apparent disconnect (except able to ping default gateway) occasionally fixed by deleting, then re-adding the default gateway. >> > Could this have something to do with leases being renewed (by the >> > isp dhcp server and consequently the cable modem) and FreeBSD not >> > updating routing tables? (I'm guessing big time here - not an >> > expert by any means) Sounds as if the MAC of the upstream provider occasionally changes. Don't know enough about cable to understand it better, and problem is gone now so can't check for sure. >> If your cable modem provides IP, it's probably not involved in the >> DHCP negotiations. Does your IP address change before you start to >> see this slowdown? > > No new address. Ditto. No new address was received. IP address of default gateway did not change. I even tried this with packet filters off, same thing. > I wondered if there is not some parameter that windows supplies in > the DHCP request that dhclient does not? This started happening to > me when my cable company (with @home) took over the cable modem isp > business from my old ISP. Same timing here. Problem started when @home took over for MediaOne. Haven't seen it in the past few days since attbi took over @home. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 6:56:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21104.mail.yahoo.com (web21104.mail.yahoo.com [216.136.227.106]) by hub.freebsd.org (Postfix) with SMTP id CA79937B417 for ; Sun, 9 Dec 2001 06:56:28 -0800 (PST) Message-ID: <20011209145628.64563.qmail@web21104.mail.yahoo.com> Received: from [62.254.0.5] by web21104.mail.yahoo.com via HTTP; Sun, 09 Dec 2001 06:56:28 PST Date: Sun, 9 Dec 2001 06:56:28 -0800 (PST) From: Hiten Pandya Subject: about boot0 To: freebsd-hackers@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi all, is there a reason behind.. why all Windows related boot options are marked as DOS?... src/sys/boot/i386/boot0.s is it because of the 512-byte limit... ===== -Hiten, Thank You, Yours Sincerely, Hiten Pandya, __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 7:13:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 347AA37B416 for ; Sun, 9 Dec 2001 07:13:56 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fB9FDTi84561; Sun, 9 Dec 2001 10:13:30 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 9 Dec 2001 10:13:29 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Terry Lambert Cc: Alfred Perlstein , Poul-Henning Kamp , Dave Rufino , freebsd-hackers@FreeBSD.ORG Subject: Re: statefulness in character device drivers In-Reply-To: <3C131DD5.B1569FF8@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 9 Dec 2001, Terry Lambert wrote: > Alfred Perlstein wrote: > > I'd be glad to assist in any way possible to get this integrated, > > we've really been wanting this for various reasons (mostly linnex > > compat) let me know if you're too busy and I can try to take over > > from your existing work. Point being, I want this done ASAP. :) > > Not to mention that it'd be really, really nice to be able to run > multiple guest OSs under VMWARE under FreeBSD at the same time... That was actually what prompted me to look into this in the first place :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 8: 9:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brea.mc.mpls.visi.com (brea.mc.mpls.visi.com [208.42.156.100]) by hub.freebsd.org (Postfix) with ESMTP id 7613437B405 for ; Sun, 9 Dec 2001 08:09:20 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by brea.mc.mpls.visi.com (Postfix) with ESMTP id 860C62DDDDE for ; Sun, 9 Dec 2001 10:09:19 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fB9G8tb23080 for hackers@freebsd.org; Sun, 9 Dec 2001 10:08:55 -0600 (CST) (envelope-from hawkeyd) Date: Sun, 9 Dec 2001 10:08:55 -0600 From: D J Hawkey Jr To: hackers@freebsd.org Subject: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011209100855.A22942@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011206114725.A836@sheol.localdomain> <200112090811.fB98BYD35974@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112090811.fB98BYD35974@apollo.backplane.com>; from dillon@apollo.backplane.com on Sun, Dec 09, 2001 at 12:11:34AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Dec 09, at 12:11 AM, Matthew Dillon wrote: > > In anycase, your patches look fine. In fact, you not only applied > my fixes you also applied a fix in the delayed-ack check that was > made (by someone else) some time after 4.2Rel -- the callout_pending() > check in DELAY_ACK() fixed a serious bug in prior releases all by itself. > Kudos! I know it's been discussed before, but if this is considered a "serious bug", shouldn't it also be applied to supported-but-not-stable versions? RELENG_(release - 1) seems to be the target of "backported" security fixes, and I have no problem with that - a line has to be drawn somewhere - but I (and likely many others) would love to see things such as this (things that aren't security focused) be made to RELENG_(release - 1). If I hadn't caught the DELACK thread on this list, I never would have known that TCP/IP throughput could be fixed/enhanced so easily - for me, that is, I only applied a patch, but pro'lly not for Matt. Another candidate for this sort of thing I'd like to see "backported" to RELENG_(release - 1) would be DIRPREFS, but that might be asking too much; I don't know how many modules were hacked for that. I took it upon myself to add ICH sound support to my 4.2REL kernel and another 4.3REL kernel, based on the original patches submitted. This is an example of what pro'lly could be omitted from RELENG_(release - 1), but a FreeBSD.org sanctioned facility where the likes of us unsupported- or-supported-but-not-stable hackers could upload/submit patches would be a nice thing. Just my two-cents' worth of thoguht food. Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 8:54:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by hub.freebsd.org (Postfix) with ESMTP id 5277137B416 for ; Sun, 9 Dec 2001 08:54:32 -0800 (PST) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id ECDB762D01; Sun, 9 Dec 2001 08:54:26 -0800 (PST) Date: Sun, 9 Dec 2001 08:54:52 -0800 (PST) From: Lamont Granquist To: D J Hawkey Jr Cc: Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux In-Reply-To: <20011209100855.A22942@sheol.localdomain> Message-ID: <20011209084620.V14858-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I think what "would be cool" would be to have a RELENG_4_4_BUGFIX tree which was for bugfixes, but was feature frozen. It shouldn't get new features like dirprefs (otherwise its difficult to differentiate it from -STABLE itself) but it should get bugfixes. That way FreeBSD would wind up with some extremely stable and feature frozen code. Unfortunately, I'm not qualified to volunteer to engineer such a branching scheme... On Sun, 9 Dec 2001, D J Hawkey Jr wrote: > On Dec 09, at 12:11 AM, Matthew Dillon wrote: > > > > In anycase, your patches look fine. In fact, you not only applied > > my fixes you also applied a fix in the delayed-ack check that was > > made (by someone else) some time after 4.2Rel -- the callout_pending() > > check in DELAY_ACK() fixed a serious bug in prior releases all by itself. > > Kudos! > > I know it's been discussed before, but if this is considered a "serious > bug", shouldn't it also be applied to supported-but-not-stable versions? > > RELENG_(release - 1) seems to be the target of "backported" security fixes, > and I have no problem with that - a line has to be drawn somewhere - but > I (and likely many others) would love to see things such as this (things > that aren't security focused) be made to RELENG_(release - 1). > > If I hadn't caught the DELACK thread on this list, I never would have > known that TCP/IP throughput could be fixed/enhanced so easily - for me, > that is, I only applied a patch, but pro'lly not for Matt. > > Another candidate for this sort of thing I'd like to see "backported" to > RELENG_(release - 1) would be DIRPREFS, but that might be asking too > much; I don't know how many modules were hacked for that. > > I took it upon myself to add ICH sound support to my 4.2REL kernel and > another 4.3REL kernel, based on the original patches submitted. This is > an example of what pro'lly could be omitted from RELENG_(release - 1), > but a FreeBSD.org sanctioned facility where the likes of us unsupported- > or-supported-but-not-stable hackers could upload/submit patches would > be a nice thing. > > Just my two-cents' worth of thoguht food. > Dave > > -- > ______________________ ______________________ > \__________________ \ D. J. HAWKEY JR. / __________________/ > \________________/\ hawkeyd@visi.com /\________________/ > http://www.visi.com/~hawkeyd/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 9:15:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from breg.mc.mpls.visi.com (breg.mc.mpls.visi.com [208.42.156.101]) by hub.freebsd.org (Postfix) with ESMTP id 7E49937B417 for ; Sun, 9 Dec 2001 09:15:42 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by breg.mc.mpls.visi.com (Postfix) with ESMTP id 7DC0D2D0E3B; Sun, 9 Dec 2001 11:15:41 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fB9HFNC23441; Sun, 9 Dec 2001 11:15:23 -0600 (CST) (envelope-from hawkeyd) Date: Sun, 9 Dec 2001 11:15:23 -0600 From: D J Hawkey Jr To: Lamont Granquist Cc: hackers@freebsd.org Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011209111523.A23357@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011209084620.V14858-100000@coredump.scriptkiddie.org>; from lamont@scriptkiddie.org on Sun, Dec 09, 2001 at 08:54:52AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Dec 09, at 08:54 AM, Lamont Granquist wrote: > > I think what "would be cool" would be to have a RELENG_4_4_BUGFIX tree > which was for bugfixes, but was feature frozen. It shouldn't get new > features like dirprefs (otherwise its difficult to differentiate it from > -STABLE itself) but it should get bugfixes. That way FreeBSD would wind > up with some extremely stable and feature frozen code. Well, this isn't exactly where I was going. The gist of my post was to try to see if some "official" mechanism(s) could be built to enhance and extend (cough) previous releases beyond the RELENG_(release - 1) security upgrade policy introduced with the 4.3 and 4.4 releases. Besides, aren't you describing the CVS snapshots known as RELEASEs? > Unfortunately, I'm not qualified to volunteer to engineer such a branching > scheme... I could maintain a "not-FreeBSD-sanctioned" site for patches of -CURRENT and -STABLE code applyable to previous releases, but that would only muddy the FreeBSD maintenance and distribution waters that I think work well for what they're intended to address, as well as open myself up to all sorts of support and maintenance headaches. Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 9:36: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from diablo.ovinet.hu (diablo.ovinet.hu [217.13.33.205]) by hub.freebsd.org (Postfix) with ESMTP id B072C37B405 for ; Sun, 9 Dec 2001 09:36:06 -0800 (PST) Received: from diablo.ovinet.hu (titanic@localhost [127.0.0.1]) by localhost (MX V4.2 AXP/OpenVMS) with ESMTP id fB9HfimF008141 for ; Sun, 9 Dec 2001 18:41:44 +0100 Received: (from titanic@localhost) by diablo.ovinet.hu (8.12.0.Beta19/8.12.0.Beta19/Debian 8.12.0.Beta19) id fB9Hfh9X008139 for freebsd-hackers@freebsd.org; Sun, 9 Dec 2001 18:41:43 +0100 Date: Sun, 9 Dec 2001 18:41:43 +0100 From: KAISER Laszlo To: freebsd-hackers@freebsd.org Subject: SSL_connect fails Message-ID: <20011209184143.H12621@ovinet.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I'm doing a port of a little OpenSSL program to FreeBSD from linux, but the code which works fine on linux fails on FreeBSD at SSL_connect(). This function allways returns with -1 and SSL_errno is 1. The code creates the CTX in client mode successfully, reads the client certificates, sets session id, sets session, sets the file descriptor, and connect state. Until this point there is no error/warnin. But SSL_connect(). I examined the stunnel source which do the same, but that code works, mine not :/ Compiler options: CFLAGS -fomit-frame-pointer -fpcc-struct-return -O2 -D_REENTRANT \ -D_POSIX_PTHREADS_SEMANTICS LDFLAGS -lc_r -lcrypto -pthread -lssl -fomit-frame-pointer -fpcc-struct-return -O2 OpenSSL version: 0.9.5a What do i wrong? :o TiTaNiC -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 9:57:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id 6AC7F37B423 for ; Sun, 9 Dec 2001 09:57:36 -0800 (PST) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.6/8.11.6) id fB9Hpbl04921; Sun, 9 Dec 2001 17:51:37 GMT (envelope-from nik) Date: Sun, 9 Dec 2001 17:51:37 +0000 From: Nik Clayton To: D J Hawkey Jr Cc: Lamont Granquist , hackers@freebsd.org Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011209175137.B13554@clan.nothing-going-on.org> References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="bCsyhTFzCvuiizWE" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011209111523.A23357@sheol.localdomain>; from hawkeyd@visi.com on Sun, Dec 09, 2001 at 11:15:23AM -0600 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --bCsyhTFzCvuiizWE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 09, 2001 at 11:15:23AM -0600, D J Hawkey Jr wrote: > I could maintain a "not-FreeBSD-sanctioned" site for patches of -CURRENT > and -STABLE code applyable to previous releases, but that would only muddy > the FreeBSD maintenance and distribution waters that I think work well for > what they're intended to address, as well as open myself up to all sorts > of support and maintenance headaches. Actually, that's probably the best thing you could do. Because then it shows that you've got the commitment to do this sort of thing and maintain it. =20 The project isn't short of people having good ideas, it's short of people willing to do the actual work. If you do this, and show that the idea is viable, it will be much easier to come back in a few months time to get these patches integrated in to the various RELENG_* branches, and to bring you in as a committer. I'm sure we can make sure that any site you set up to do this is linked to from the FreeBSD web site. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --bCsyhTFzCvuiizWE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwTpKkACgkQk6gHZCw343VMSwCeJIJmhDnc0g2uSqWA8AqqW84F 9VgAn2dsSjqo7GjxkmkwWyKgpen9dgw+ =LtD/ -----END PGP SIGNATURE----- --bCsyhTFzCvuiizWE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 10:17:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from breg.mc.mpls.visi.com (breg.mc.mpls.visi.com [208.42.156.101]) by hub.freebsd.org (Postfix) with ESMTP id 6BC8237B416; Sun, 9 Dec 2001 10:17:18 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by breg.mc.mpls.visi.com (Postfix) with ESMTP id 6F6672D055D; Sun, 9 Dec 2001 12:17:17 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fB9IH8i23805; Sun, 9 Dec 2001 12:17:08 -0600 (CST) (envelope-from hawkeyd) Date: Sun, 9 Dec 2001 12:17:03 -0600 From: D J Hawkey Jr To: Nik Clayton Cc: Lamont Granquist , hackers@freebsd.org Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011209121703.A23726@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011209175137.B13554@clan.nothing-going-on.org>; from nik@freebsd.org on Sun, Dec 09, 2001 at 05:51:37PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Dec 09, at 05:51 PM, Nik Clayton wrote: > > On Sun, Dec 09, 2001 at 11:15:23AM -0600, D J Hawkey Jr wrote: > > I could maintain a "not-FreeBSD-sanctioned" site for patches of -CURRENT > > and -STABLE code applyable to previous releases, but that would only muddy > > the FreeBSD maintenance and distribution waters that I think work well for > > what they're intended to address, as well as open myself up to all sorts > > of support and maintenance headaches. > > Actually, that's probably the best thing you could do. Because then it > shows that you've got the commitment to do this sort of thing and > maintain it. > > The project isn't short of people having good ideas, it's short of > people willing to do the actual work. If you do this, and show that the > idea is viable, it will be much easier to come back in a few months time > to get these patches integrated in to the various RELENG_* branches, and > to bring you in as a committer. The "viability" thing is the catch, no? Seems to me that were I to do this, and I would, it would only be as viable as the patches themselves. That is, I (and any contributors) would have to be able to stay abreast of those things going on in -STABLE that could get backported to previous releases ("could" being a significant word here). With bugs@, hackers@, stable@, current@, and cross-referencing the CVS tree(s) against these lists, just staying abreast of things seems pretty daunting. > I'm sure we can make sure that any site you set up to do this is linked > to from the FreeBSD web site. So far, I've made three patchfiles that can be applied to 4.2REL and 4.3REL. Not exactly the repertoire one would need to garner interest and momentum. > N Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 10:29:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from red.csi.cam.ac.uk (red.csi.cam.ac.uk [131.111.8.70]) by hub.freebsd.org (Postfix) with ESMTP id 563B437B416; Sun, 9 Dec 2001 10:29:12 -0800 (PST) Received: from dr263 (helo=localhost) by red.csi.cam.ac.uk with local-esmtp (Exim 3.22 #1) id 16D8hI-00009F-00; Sun, 09 Dec 2001 18:29:08 +0000 Date: Sun, 9 Dec 2001 18:29:08 +0000 (GMT) From: Dave Rufino X-X-Sender: To: Alfred Perlstein Cc: Robert Watson , Poul-Henning Kamp , Terry Lambert , Subject: Re: statefulness in character device drivers In-Reply-To: <20011208223850.N92148@elvis.mu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 8 Dec 2001, Alfred Perlstein wrote: > * Robert Watson [011208 19:43] wrote: > > > > I had some patches to do this, but lost them ages ago. If I get really > > bored next week, I'll redo them and stick them in a perforce branch. That > > said, it requires a bit more work, but is easier if you define the void** > > as optional: if it's non-NULL, then you return state, and let it get > > passed back in. Otherwise, you assume it's traditional stateless access. > > It requires some tweaking of the vnode pager, among other things, but is > > actually a relatively straight-forward patch. Maybe I'll give it a spin > > again and post patches to -arch or something. > > I'd be glad to assist in any way possible to get this integrated, > we've really been wanting this for various reasons (mostly linnex > compat) let me know if you're too busy and I can try to take over > from your existing work. Point being, I want this done ASAP. :) I would likewise be glad to assist, and have a similar vested interest in getting this done. I also suspect I have more free time to work on it. :) David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 11:19:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.trit.org (bazooka.trit.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id A5F0437B405; Sun, 9 Dec 2001 11:19:48 -0800 (PST) Received: by bazooka.trit.org (Postfix, from userid 1000) id 6AB703E3A; Sun, 9 Dec 2001 19:19:48 +0000 (UTC) Received: from bazooka (localhost [127.0.0.1]) by bazooka.trit.org (Postfix) with ESMTP id 694463C12E; Sun, 9 Dec 2001 19:19:48 +0000 (UTC) To: chris@FreeBSD.ORG Cc: Igor M Podlesny , freebsd-hackers@FreeBSD.ORG Subject: Re: jail.c.patch (allowing to use hostnames when invoking jail(8)) In-Reply-To: <20011125112748.B511@holly.calldei.com>; from chris@FreeBSD.ORG on "Sun, 25 Nov 2001 11:27:48 -0600" Date: Sun, 09 Dec 2001 19:19:43 +0000 From: Dima Dorfman Message-Id: <20011209191948.6AB703E3A@bazooka.trit.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Chris Costello wrote: > On Saturday, November 24, 2001, Igor M Podlesny wrote: > > i = inet_aton(argv[3], &in); > > - if (!i) > > - errx(1, "Couldn't make sense of ip-number\n"); > > + if (!i) { > > + /* check if it is resolveable */ > > + struct hostent *hp; > > + hp = gethostbyname(argv[3]); > > + if (hp == NULL) { > > + errx(1, "Couldn't make sense of the jail address\n"); > > + } > > + else { > > + char **p = hp->h_addr_list; > > + if (p[1] != NULL) { > > + errx(1, "Jail should have only one ip-address associated with!\n"); > > + } > > + else { > > + memcpy(&in.s_addr, p[0], sizeof(in.s_addr)); > > + } > > + } > > + } > > I'd rewrite the above (`i = inet_aton' all the way down) as > > hp = gethostbyname(argv[3]); > if (hp == NULL) { > errx(1, "%s: %s", argv[3], hstrerror(h_errno)); > } > in = *(struct in_addr *)hp->h_addr_list[0]; > > This makes the call to inet_aton() unnecessary (and really > shortens the code!). As discussed off-list, this is a good idea. Attached is the final patch that I plan to commit unless I hear objections. Please review. Thanks. Index: jail.8 =================================================================== RCS file: /ref/cvsf/src/usr.sbin/jail/jail.8,v retrieving revision 1.30 diff -u -r1.30 jail.8 --- jail.8 2001/09/03 15:42:10 1.30 +++ jail.8 2001/12/09 19:14:30 @@ -43,7 +43,7 @@ .Nm .Ar path .Ar hostname -.Ar ip-number +.Ar hostname .Ar command .Ar ... .Sh DESCRIPTION Index: jail.c =================================================================== RCS file: /ref/cvsf/src/usr.sbin/jail/jail.c,v retrieving revision 1.7 diff -u -r1.7 jail.c --- jail.c 2001/06/24 20:28:19 1.7 +++ jail.c 2001/12/09 19:14:11 @@ -17,6 +17,7 @@ #include #include +#include #include #include #include @@ -25,12 +26,13 @@ int main(int argc, char **argv) { + struct hostent *hp; struct jail j; int i; struct in_addr in; if (argc < 5) - errx(1, "Usage: %s path hostname ip-number command ...\n", + errx(1, "Usage: %s path hostname hostname command ...\n", argv[0]); i = chdir(argv[1]); if (i) @@ -39,9 +41,11 @@ j.version = 0; j.path = argv[1]; j.hostname = argv[2]; + hp = gethostbyname(argv[3]); + if (hp == NULL) + errx(1, "gethostbyname(%s): %s", argv[3], hstrerror(h_errno)); i = inet_aton(argv[3], &in); - if (!i) - errx(1, "Couldn't make sense of ip-number\n"); + in = *(struct in_addr *)hp->h_addr; j.ip_number = ntohl(in.s_addr); i = jail(&j); if (i) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 12:54:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.trit.org (bazooka.trit.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 16C7737B405; Sun, 9 Dec 2001 12:54:43 -0800 (PST) Received: by bazooka.trit.org (Postfix, from userid 1000) id C8D0A3E2F; Sun, 9 Dec 2001 20:54:42 +0000 (UTC) Received: from bazooka (localhost [127.0.0.1]) by bazooka.trit.org (Postfix) with ESMTP id C75383C12E; Sun, 9 Dec 2001 20:54:42 +0000 (UTC) To: chris@FreeBSD.ORG, Igor M Podlesny , freebsd-hackers@FreeBSD.ORG Subject: Re: jail.c.patch (allowing to use hostnames when invoking jail(8)) Date: Sun, 09 Dec 2001 20:54:37 +0000 From: Dima Dorfman Message-Id: <20011209205442.C8D0A3E2F@bazooka.trit.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dima Dorfman wrote: > Chris Costello wrote: > > I'd rewrite the above (`i = inet_aton' all the way down) as > > > > hp = gethostbyname(argv[3]); > > if (hp == NULL) { > > errx(1, "%s: %s", argv[3], hstrerror(h_errno)); > > } > > in = *(struct in_addr *)hp->h_addr_list[0]; > > > > This makes the call to inet_aton() unnecessary (and really > > shortens the code!). > > As discussed off-list, this is a good idea. Attached is the final > patch that I plan to commit unless I hear objections. Please review. Here's an updated patch which is a result of comments from a few people. The changes are: (a) deconfuse the usage message by not naming two arguments as "hostname" (that was sloppiness on my part), and (b) remove a redundant inet_aton call (gethostbyname(3) will DTRT with an IP address) [1]. [1] It probably shouldn't, since as others have pointed out to me, "1.1.1.1" is a valid DNS name. The correct solution would be to have a flag which makes it explicit whether the argument is an IP address or DNS name, but few, if any, other programs in the system do this, and I don't think this is a good place to start. Index: jail.8 =================================================================== RCS file: /ref/cvsf/src/usr.sbin/jail/jail.8,v retrieving revision 1.30 diff -u -r1.30 jail.8 --- jail.8 2001/09/03 15:42:10 1.30 +++ jail.8 2001/12/09 20:45:53 @@ -43,13 +43,16 @@ .Nm .Ar path .Ar hostname -.Ar ip-number +.Ar address .Ar command .Ar ... .Sh DESCRIPTION The .Nm command imprisons a process and all future descendants. +The supplied +.Ar address +may either be a hostname or IPv4 address. .Pp Please see the .Xr jail 2 Index: jail.c =================================================================== RCS file: /ref/cvsf/src/usr.sbin/jail/jail.c,v retrieving revision 1.7 diff -u -r1.7 jail.c --- jail.c 2001/06/24 20:28:19 1.7 +++ jail.c 2001/12/09 20:50:20 @@ -14,23 +14,22 @@ #include #include -#include #include -#include +#include #include -#include #include int main(int argc, char **argv) { + struct hostent *hp; struct jail j; int i; struct in_addr in; if (argc < 5) - errx(1, "Usage: %s path hostname ip-number command ...\n", + errx(1, "Usage: %s path hostname address command ...\n", argv[0]); i = chdir(argv[1]); if (i) @@ -39,9 +38,10 @@ j.version = 0; j.path = argv[1]; j.hostname = argv[2]; - i = inet_aton(argv[3], &in); - if (!i) - errx(1, "Couldn't make sense of ip-number\n"); + hp = gethostbyname(argv[3]); + if (hp == NULL) + errx(1, "gethostbyname(%s): %s", argv[3], hstrerror(h_errno)); + in = *(struct in_addr *)hp->h_addr; j.ip_number = ntohl(in.s_addr); i = jail(&j); if (i) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 13:46: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta02ps.bigpond.com (mta02ps.bigpond.com [144.135.25.134]) by hub.freebsd.org (Postfix) with ESMTP id 3366137B405 for ; Sun, 9 Dec 2001 13:45:59 -0800 (PST) Received: from voicetronix.com.au ([144.135.25.69]) by mta02ps.bigpond.com (Netscape Messaging Server 4.15) with SMTP id GO3JFW00.6HY for ; Mon, 10 Dec 2001 07:52:44 +1000 Received: from 144.137.194.16 ([144.137.194.16]) by PSMAM01.mailsvc.email.bigpond.com(MailRouter V3.0f 65/6615706); 10 Dec 2001 07:45:51 Message-ID: <3C13DCA4.9AAEC29A@voicetronix.com.au> Date: Mon, 10 Dec 2001 08:20:28 +1030 From: David Rowe Organization: Voicetronix X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG unsubscribe hackers-freebsd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 14:16: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21108.mail.yahoo.com (web21108.mail.yahoo.com [216.136.227.110]) by hub.freebsd.org (Postfix) with SMTP id 471FA37B41B for ; Sun, 9 Dec 2001 14:16:07 -0800 (PST) Message-ID: <20011209221607.78673.qmail@web21108.mail.yahoo.com> Received: from [62.254.0.5] by web21108.mail.yahoo.com via HTTP; Sun, 09 Dec 2001 14:16:07 PST Date: Sun, 9 Dec 2001 14:16:07 -0800 (PST) From: Hiten Pandya Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux To: freebsd-hackers@freebsd.org Cc: nik@freebsd.org In-Reply-To: <20011209175137.B13554@clan.nothing-going-on.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, does anyone need any special skills to manage the kind of branch you are talking about... example.. RELENG_4_4_BUGFIX what kind of skills and experience in FreeBSD would be needed for this kind of branch.... -Hiten > I could maintain a "not-FreeBSD-sanctioned" site > for patches of -CURRENT and -STABLE code applyable > to previous releases, > but that would only muddy > the FreeBSD maintenance and distribution waters > that I think work well for > what they're intended to address, as well as open > myself up to all sorts > of support and maintenance headaches. > i wouldn't mind helping.... :-) ===== -Hiten, Thank You, Yours Sincerely, Hiten Pandya, __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 14:27: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 81A8937B405; Sun, 9 Dec 2001 14:27:02 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id fB9MQqk25818; Sun, 9 Dec 2001 17:26:52 -0500 (EST) (envelope-from mwlucas) Date: Sun, 9 Dec 2001 17:26:52 -0500 From: Michael Lucas To: D J Hawkey Jr Cc: Nik Clayton , Lamont Granquist , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011209172652.A25745@blackhelicopters.org> References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011209121703.A23726@sheol.localdomain>; from hawkeyd@visi.com on Sun, Dec 09, 2001 at 12:17:03PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Dec 09, 2001 at 12:17:03PM -0600, D J Hawkey Jr wrote: > So far, I've made three patchfiles that can be applied to 4.2REL and 4.3REL. > Not exactly the repertoire one would need to garner interest and momentum. Everything starts somewhere. When I wrote my first FreeBSD article a few years ago, I had no idea where it would lead. Keep it up, and the Project might well ask you to make it an official FreeBSD resource. If you start now, in a few months you'll have patchsets for 4.2-R, 4.3-R, 4.4-R, and 4.5-R. That looks like a pretty serious investment of time and/or dedication to me. It's cliche, but: ten thousand lines of code begins with the first #define. (Hmmmm.... click click click... okay, style(9) says it should be the first #include. But you get the idea.) ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 15:23:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id DBF6537B419 for ; Sun, 9 Dec 2001 15:23:34 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011209232329.VNA4213.rwcrmhc52.attbi.com@peter3.wemm.org> for ; Sun, 9 Dec 2001 23:23:29 +0000 Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id fB9NNSs31685 for ; Sun, 9 Dec 2001 15:23:28 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 31DC43810; Sun, 9 Dec 2001 15:23:28 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Poul-Henning Kamp Cc: mitko@rila.bg, hackers@FreeBSD.ORG Subject: Re: Performance issue In-Reply-To: <72360.1007898170@critter.freebsd.dk> Date: Sun, 09 Dec 2001 15:23:28 -0800 From: Peter Wemm Message-Id: <20011209232328.31DC43810@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > There are many effects that could cause this, for instance if FreeBSD > manages to align things differently in relation to the CPU cache you > could get some very interesting waste of time that way. > > Based on the data you show me, I can't really say that something is > wrong or right either way. One thing that Linux does that we do not do is that they have different versions of libc compiled specifically for different cpu types, and at boot time set the correct paths. eg: /lib/i386/libc.so.6.whatever This means that Linux's glibc is using an i686 optimized bzero(), but the FreeBSD one is using an i386 optimized bzero(). Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 15:50:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from appsrv1.eol.ca (appsrv1.eol.ca [205.189.152.19]) by hub.freebsd.org (Postfix) with ESMTP id A6CD137B416 for ; Sun, 9 Dec 2001 15:50:00 -0800 (PST) Received: from ntserver.breadsource.com (static-3M-b1-242.highspeed.eol.ca [64.56.238.242]) by appsrv1.eol.ca (Postfix) with ESMTP id 3BBE23715 for ; Sun, 9 Dec 2001 18:50:00 -0500 (EST) Received: from 1Cust184.tnt26.dfw9.da.uu.net by ntserver.breadsource.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1459.44) id X8V3WY5S; Sun, 9 Dec 2001 18:49:39 -0500 Message-ID: <00004ce75426$00000955$000003db@mta.excite.com> To: From: OrderMusic@excite.com Subject: $10.00 off CD's, DVD's QRA Date: Sun, 09 Dec 2001 17:50:17 -1800 MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Reply-To: OrderMusic34@excite.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG

We at Digital Citizen respect your online privacy. We have included contact information and a way for removal from our mailing list. If you wish to be= removed from this list, please click here and provide the address(es) = to be deleted from our list. Any inconvenience caused is sincerely regretted

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 16: 7:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 2549337B417; Sun, 9 Dec 2001 16:07:04 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [fec0::1:12]) by Awfulhak.org (8.11.6/8.11.6) with ESMTP id fB6D78R18133; Thu, 6 Dec 2001 13:07:08 GMT (envelope-from brian@freebsd-services.com) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.6/8.11.6) with ESMTP id fB6D77E46932; Thu, 6 Dec 2001 13:07:07 GMT (envelope-from brian@freebsd-services.com) Message-Id: <200112061307.fB6D77E46932@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: James Housley Cc: Brian Somers , Greg Lane , freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org, brian@freebsd.org, Julian Elischer , brian@freebsd-services.com Subject: Re: [Fwd: Jul 30 changes to ppp break my Telstra ADSL PPPoE connection] In-Reply-To: Message from James Housley of "Wed, 05 Dec 2001 08:16:18 EST." <3C0E1E22.B685EC47@Thehousleys.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Dec 2001 13:07:07 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Brian Somers wrote: > > > > Hi, > > > > Thanks for your report. Would you be able to grab me logs of the > > connection that doesn't work (the latest ppp) and the one that works > > (the pre-July 30 one) with the following set: > > > > set log tun chat lcp ipcp > > > > It may be possible to fix the problem by changing your ``set mru'' > > and ``set mtu'' lines to > > > > set mru max 1454 > > set mtu max 1454 > > > > but, even if this is successful, I'd be interested in the logs. > > > > It may also be worth trying the latest version of ppp from my web > > site (http://www.Awfulak.org/~brian) - just in case it's something > > that I've already fixed but have forgotten to MFC. If that's the > > case, then I should be able to find the bogus code more easily. > > > > I am having great difficulty getting logs. I noticed the last time I had ppp log data was November 20th. But this is what I have. > > /etc/syslog.conf: > !ppp > *.* /var/log/ppp.log > > /var/log/ppp.log: > Dec 5 08:02:26 server ppp[198]: tun0: LCP: deflink: RecvEchoRequest(2) state = Opened > Dec 5 08:02:26 server ppp[198]: tun0: LCP: deflink: SendEchoReply(2) state = Opened This looks ok. Can you show me the logs from when the connection is established in each case ? Cheers. > jhousley@server:~ {13} pppctl -p xxxxxx 3000 show log > Log: Chat IPCP LCP Tun Warning Error Alert > Local: Warning Error Alert > > I am getting this with both RELENG_4_3 ppp and RELENG_4 ppp. Yes syslogd is running as "syslogd -s -s" If I turn on tcp/ip or debug I get lots of information in the log > files. Is it possible that some of the log levels were broken. I will try the latest verson from (http://www.Awfulak.org/~brian) is see if that logs properly > > Jim > -- > /"\ ASCII Ribbon Campaign . > \ / - NO HTML/RTF in e-mail . > X - NO Word docs in e-mail . > / \ ----------------------------------------------------------------- > jeh@FreeBSD.org http://www.FreeBSD.org The Power to Serve > jim@TheHousleys.Net http://www.TheHousleys.net > jhousley@SimTel.Net http://www.SimTel.Net > --------------------------------------------------------------------- > Your mouse has moved. > Windows NT must be restarted for the change to take effect! > > Reboot now? [OK] -- Brian http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 18:25: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 9A39B37B416; Sun, 9 Dec 2001 18:25:01 -0800 (PST) Received: from pool0370.cvx22-bradley.dialup.earthlink.net ([209.179.199.115] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16DG7i-0003ui-00; Sun, 09 Dec 2001 18:24:55 -0800 Message-ID: <3C141CFE.3346BDAF@mindspring.com> Date: Sun, 09 Dec 2001 18:25:02 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dima Dorfman Cc: chris@FreeBSD.ORG, Igor M Podlesny , freebsd-hackers@FreeBSD.ORG Subject: Re: jail.c.patch (allowing to use hostnames when invoking jail(8)) References: <20011209191948.6AB703E3A@bazooka.trit.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This patch will break backward compatability with existing scripts. Since it is an easy matter to call inet_aton() on the buffer, and then call gethostbyname() only if inet_aton() returns INADDR_NONE (which would allow either a host name or an IP address to be used), please use this approach instead. This also implies minor modification to the usage message and the man page, but you are hacking them up anyway. Thanks, -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 18:36:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 3C8C237B42B; Sun, 9 Dec 2001 18:36:08 -0800 (PST) Received: from pool0370.cvx22-bradley.dialup.earthlink.net ([209.179.199.115] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16DGIY-00002E-00; Sun, 09 Dec 2001 18:36:06 -0800 Message-ID: <3C141F9E.D7681BCC@mindspring.com> Date: Sun, 09 Dec 2001 18:36:14 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dima Dorfman Cc: chris@FreeBSD.ORG, Igor M Podlesny , freebsd-hackers@FreeBSD.ORG Subject: Re: jail.c.patch (allowing to use hostnames when invoking jail(8)) References: <20011209205442.C8D0A3E2F@bazooka.trit.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dima Dorfman wrote: > Here's an updated patch which is a result of comments from a few > people. The changes are: (a) deconfuse the usage message by not > naming two arguments as "hostname" (that was sloppiness on my part), > and (b) remove a redundant inet_aton call (gethostbyname(3) will DTRT > with an IP address) [1]. > > [1] It probably shouldn't, since as others have pointed out to me, > "1.1.1.1" is a valid DNS name. The correct solution would be to have > a flag which makes it explicit whether the argument is an IP address > or DNS name, but few, if any, other programs in the system do this, > and I don't think this is a good place to start. This is why the inte_aton() call is still necessary. And it won't "do the right thing", per se, since it wants to kick a DNS query off for a purely numeric tupple set. I, and I suspect others, start jails up at boot time, well before any network connection has been established. You are requiring us to install caching DNS servers with preloaded caches, and delay starting up until after the servers are started. This is marginally unacceptable. One of the reasons I use jails is to establish a set of 13 virtual hosts, one of which acts as the root DNS server for a testbed that pretends that it is the real Internet root DNS server. In other jails, I run "client" DNS machines with DNS delegations from this "root" server, which also do inter-host (inter-jail, in reality) zone synchornization. If/when these zones are in conflict (e.g. when I run a NAT in two or more of them with a 10.x address block for each, and then VPN between them using address block translation to translate 10.1 to 10.2 and vice versa in each, with DNS forwarding for the block so that name lookups work as expected), then I am screwed by your change, since I can't have two canonical names for the same IP address later. Please call inet_aton(), and then _only_ if that fails, call the gethostbyname(). PS: Your man pages are better. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 19: 7:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 644D637B41C; Sun, 9 Dec 2001 19:07:41 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fBA37Qi96320; Sun, 9 Dec 2001 22:07:26 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 9 Dec 2001 22:07:26 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: developers@FreeBSD.org, hackers@FreeBSD.org Subject: Request for submissions: FreeBSD Monthly Development Status Report Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, it's been a bit, but here it is again. This is a request for submissions for the November, 2001 FreeBSD Monthly Development Status Report. All submissions are due by Friday, December 14, 2001. Submissions should made by filling out the following template: http://www.FreeBSD.org/news/status/report-sample.xml Which will allow reports to be automatically processed, reducing the lag involved in generating the overall report :-). A reasonable attempt should be made to prevent duplicate submissions for the same project; however, if it's a large project, seperate submissions may be made for components, as well as a submission sumarizing overall progress on the project. Developers working on multiple projects should feel free to submit entries for each project individually. Submissions are welcome on a variety of topics relating to FreeBSD -- not least, development, but also documentation, advocacy, and processes relating to the development process, such as release engineering, QA, and security updates. All submissions *MUST* be e-mailed to the following address: robert+freebsd.monthly@cyrus.watson.org Submissions made to other e-mail addresses will not be included in the report. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 19:48:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by hub.freebsd.org (Postfix) with SMTP id 84CCB37B405 for ; Sun, 9 Dec 2001 19:48:44 -0800 (PST) Received: (qmail 3667 invoked from network); 10 Dec 2001 03:48:35 -0000 Received: from ken.yumyumyum.org (HELO there) (192.168.0.2) by dsl092-171-091.wdc1.dsl.speakeasy.net with SMTP; 10 Dec 2001 03:48:35 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Kenneth Culver To: Peter Wemm Subject: Re: Performance issue Date: Sun, 9 Dec 2001 22:49:08 -0500 X-Mailer: KMail [version 1.3.1] References: <20011209232328.31DC43810@overcee.netplex.com.au> In-Reply-To: <20011209232328.31DC43810@overcee.netplex.com.au> Cc: hackers@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011210034844.84CCB37B405@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If they're using gcc to compile then that doesn't really matter, last I heard gcc's optimizer wasn't that great, and didn't result in much faster code, but if the glibc people hand optimized stuff, I can see your point. Ken > > This means that Linux's glibc is using an i686 optimized bzero(), but > the FreeBSD one is using an i386 optimized bzero(). > > Cheers, > -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 20: 2:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from w2xo.pgh.pa.us (18.gibs5.xdsl.nauticom.net [209.195.184.19]) by hub.freebsd.org (Postfix) with ESMTP id 5C85737B416 for ; Sun, 9 Dec 2001 20:02:24 -0800 (PST) Received: from there (xolaptop.int [192.168.5.9] (may be forged)) by w2xo.pgh.pa.us (8.11.6/8.11.3) with SMTP id fBA42Ge21093; Sun, 9 Dec 2001 23:02:16 -0500 (EST) (envelope-from durham@w2xo.pgh.pa.us) Message-Id: <200112100402.fBA42Ge21093@w2xo.pgh.pa.us> Content-Type: text/plain; charset="iso-8859-1" From: Jim Durham To: Matthew Dillon , D J Hawkey Jr Subject: Re: FreeBSD performs worse that Linux - Patches #2 & #3 Date: Sun, 9 Dec 2001 23:02:13 -0500 X-Mailer: KMail [version 1.3] Cc: hackers@FreeBSD.ORG References: <20011206114725.A836@sheol.localdomain> <200112090811.fB98BYD35974@apollo.backplane.com> In-Reply-To: <200112090811.fB98BYD35974@apollo.backplane.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday 09 December 2001 03:11 am, Matthew Dillon wrote: > :Hello all. > : > :I read with interest (and fair ignorance ;-) ) the thread about delayed > :ACKs in the TCP/IP stack. > :... > :If Matt or any other qualified hackers can make the time to double-check > :my patches, I'd appreciate it. Matt's first patch didn't apply (no NewReno > :in 4.2REL), and the third patch (to tcp_input.c) required a little more > : work (I changed tests for 'tcp_delack_enabled' to 'DELAY_ACK()'). I'd > : just like some assurance I got it right. > : > :All in all, kudos to Matt for this. In day-to-day use, I can "feel" the > :improvementi, and everything seems as solid as ever! > : > :Dave > > Ach. If you want my specific attention (or any FreeBSD developer's > specific attention) you should always Cc: the person specifically. > Otherwise my mail filter won't put it in my personal mail box :-) > > In anycase, your patches look fine. In fact, you not only applied > my fixes you also applied a fix in the delayed-ack check that was > made (by someone else) some time after 4.2Rel -- the callout_pending() > check in DELAY_ACK() fixed a serious bug in prior releases all by > itself. Kudos! > > I'm glad people have been testing this and getting such good results. > I MFC'd it fairly quickly into stable (because TCP was seriously messed > up) and its nice to get feedback that justifies the decision. > > -Matt > Matthew Dillon > > Matt, could you clarify. Is the patch that Dave applied to 4.2 applicable to 4.4-RELEASE? It sounded like not. I applied the tcp_output.c and uipc_socket.c patch to my 4.4-RELEASE servers and it made a whole lot of difference, like 500KB/sto 954KB/s from my old P200 server to my laptop. Thanks. -- Jim Durham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 20:18:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3CD0E37B417 for ; Sun, 9 Dec 2001 20:18:21 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBA4IJr43345; Sun, 9 Dec 2001 20:18:19 -0800 (PST) (envelope-from dillon) Date: Sun, 9 Dec 2001 20:18:19 -0800 (PST) From: Matthew Dillon Message-Id: <200112100418.fBA4IJr43345@apollo.backplane.com> To: Jim Durham Cc: D J Hawkey Jr , hackers@FreeBSD.ORG Subject: Re: FreeBSD performs worse that Linux - Patches #2 & #3 References: <20011206114725.A836@sheol.localdomain> <200112090811.fB98BYD35974@apollo.backplane.com> <200112100402.fBA42Ge21093@w2xo.pgh.pa.us> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Matt, could you clarify. Is the patch that Dave applied to 4.2 applicable to :4.4-RELEASE? It sounded like not. I applied the tcp_output.c and :uipc_socket.c patch to my 4.4-RELEASE servers and it made a whole lot of :difference, like 500KB/sto 954KB/s from my old P200 server to my laptop. : :Thanks. :-- :Jim Durham Well, the patch is certainly relevant to 4.2, 4.3, and 4.4. Portions of it are relevant to 4.1 and earlier. We've fixed it in -stable (i.e. post 4.4) so if you are tracking -stable you already have it. However, if you are running 4.4-RELEASE and haven't updated then you don't have the patch and it is relevant. While it is a significant fix, it is just one out of a number of fixes made since 4.4-RELEASE. The easiest solution is typically to ugprade your machine to the latest -stable. Unfortunately, upgrading at this exact moment could be problematic as apparently a number of people are having problems with recent IDE changes, at least judging by recent list postings. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 20:28:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dayab.ch (mail.dayab.ch [193.135.253.139]) by hub.freebsd.org (Postfix) with SMTP id 64E8937B419 for ; Sun, 9 Dec 2001 20:28:25 -0800 (PST) Received: (qmail 1060 invoked from network); 10 Dec 2001 00:20:09 -0000 Received: from unknown (HELO bturtle.ch) (193.135.253.141) by mail.dayab.ch with SMTP; 10 Dec 2001 00:20:09 -0000 Message-ID: <3C13ABED.B249B519@bturtle.ch> Date: Sun, 09 Dec 2001 18:22:37 +0000 From: "S. Aeschbacher" X-Mailer: Mozilla 4.75 [en] (X11; U; OpenBSD 3.0 i386) X-Accept-Language: en MIME-Version: 1.0 To: Hal Snyder , hackers@freebsd.org Subject: Re: cable modem connection problem References: <20011206071926.QTHW27606.mta05-svc.ntlworld.com@there> <3C0F7966.908CD6E6@bturtle.ch> <3C1005ED.4090001@isi.edu> <20011207000918.JIID10846.mta07-svc.ntlworld.com@there> <3C100F4D.3080900@isi.edu> <85k7vyzspp.fsf@stiegl.niksun.com> <87n10s8rn6.fsf@cb293842-b.rmdws1.il.home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hal Snyder wrote: > [snip] > Sounds as if the MAC of the upstream provider occasionally changes. > Don't know enough about cable to understand it better, and problem is > gone now so can't check for sure. As far as my cases are concerned, the MAC address does not change. When the arp entry is deleted, the same MAC of the gateway is inserted into the arp table. Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 20:35:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts16-srv.bellnexxia.net (tomts16.bellnexxia.net [209.226.175.4]) by hub.freebsd.org (Postfix) with ESMTP id 8A8E337B419 for ; Sun, 9 Dec 2001 20:35:23 -0800 (PST) Received: from xena.gsicomp.on.ca ([199.243.149.34]) by tomts16-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20011210043522.KHZV11528.tomts16-srv.bellnexxia.net@xena.gsicomp.on.ca>; Sun, 9 Dec 2001 23:35:22 -0500 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.1) with SMTP id fBA4R9W99844; Sun, 9 Dec 2001 23:27:10 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <008201c18134$11ef4320$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Hiten Pandya" , References: <20011209145628.64563.qmail@web21104.mail.yahoo.com> Subject: Re: about boot0 Date: Sun, 9 Dec 2001 23:35:17 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I believe it's because the boot loader goes by partition type. All Microsoft operating systems can use FAT (either FAT16, FAT32 or both). The boot loader can't tell what operating system you've got installed on your FAT partition, so it goes with the lowest common denominator - DOS. -- Matt Emmerton > hi all, > is there a reason behind.. why all Windows related > boot > options are marked as DOS?... > > src/sys/boot/i386/boot0.s > > is it because of the 512-byte limit... > > ===== > -Hiten, > > Thank You, > Yours Sincerely, > Hiten Pandya, > > > > __________________________________________________ > Do You Yahoo!? > Send your FREE holiday greetings online! > http://greetings.yahoo.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 9 23:50:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta06-svc.ntlworld.com (mta06-svc.ntlworld.com [62.253.162.46]) by hub.freebsd.org (Postfix) with ESMTP id 102EE37B416 for ; Sun, 9 Dec 2001 23:50:03 -0800 (PST) Received: from there ([80.4.125.7]) by mta06-svc.ntlworld.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20011210075001.JESP3849.mta06-svc.ntlworld.com@there> for ; Mon, 10 Dec 2001 07:50:01 +0000 Content-Type: text/plain; charset="iso-8859-1" From: Mike D To: hackers@freebsd.org Subject: natd ignores "natd_flags"? Date: Mon, 10 Dec 2001 07:49:37 +0000 X-Mailer: KMail [version 1.3] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011210075001.JESP3849.mta06-svc.ntlworld.com@there> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have in my rc.conf: natd_enable="YES" natd_interface="xl1" natd_flags="-f /etc/natd.conf" and in /etc/natd.conf: interface xl1 dynamic yes use_sockets yes same_ports yes log_denied yes however, since I am still seeing the "host4 natd[198]: failed to write packet back (Permission denied)" messages, I'm guessing "log_denied" is not being picked up. Any help appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 0: 0: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from neptune.deep-ocean.net (APastourelles-102-1-2-228.abo.wanadoo.fr [217.128.208.228]) by hub.freebsd.org (Postfix) with ESMTP id 38A4237B405 for ; Sun, 9 Dec 2001 23:59:50 -0800 (PST) Received: by neptune.deep-ocean.net (Postfix, from userid 1000) id 4FF2D5EF04; Mon, 10 Dec 2001 08:59:48 +0100 (CET) Date: Mon, 10 Dec 2001 08:59:48 +0100 From: Olivier Cortes To: Mike D Cc: freebsd-hackers@freebsd.org Subject: Re: natd ignores "natd_flags"? Message-ID: <20011210085948.B22592@neptune.deep-ocean.local> Mail-Followup-To: Olivier Cortes , Mike D , freebsd-hackers@freebsd.org References: <20011210075001.JESP3849.mta06-svc.ntlworld.com@there> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011210075001.JESP3849.mta06-svc.ntlworld.com@there>; from d01f1n@yahoo.com on Mon, Dec 10, 2001 at 07:49:37AM +0000 X-Operating-System: FreeBSD 4.4-STABLE i386 up 9:26, 1 user, load averages: 0.00, 0.04, 0.05 Organization: Deep-Ocean Network X-URL: http://www.deep-ocean.org/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, [I think this question should be redirected to -questions or -net, but anyway...] do you have IPFIREWALL in your kernel ? is is configured "default to deny" ? This is typically what is bugginig me when natd fails to write a packet : a nasty firewall rule... man ipfw & read the handbook, section networking (correct me if i'm wrong). Olivier On Mon, Dec 10, 2001 at 07:49:37AM +0000, Mike D wrote: > I have in my rc.conf: > > natd_enable="YES" > natd_interface="xl1" > natd_flags="-f /etc/natd.conf" > > and in /etc/natd.conf: > > interface xl1 > dynamic yes > use_sockets yes > same_ports yes > log_denied yes > > however, since I am still seeing the "host4 natd[198]: failed to write packet > back (Permission denied)" messages, I'm guessing "log_denied" is not being > picked up. > > Any help appreciated. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Olivier Cortes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 0:51:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta05-svc.ntlworld.com (mta05-svc.ntlworld.com [62.253.162.45]) by hub.freebsd.org (Postfix) with ESMTP id 8D07337B416 for ; Mon, 10 Dec 2001 00:51:51 -0800 (PST) Received: from there ([80.4.125.7]) by mta05-svc.ntlworld.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20011210085150.TANF27606.mta05-svc.ntlworld.com@there> for ; Mon, 10 Dec 2001 08:51:50 +0000 Content-Type: text/plain; charset="iso-8859-1" From: Mike D To: freebsd-hackers@freebsd.org Subject: Re: natd ignores "natd_flags"? Date: Mon, 10 Dec 2001 08:51:25 +0000 X-Mailer: KMail [version 1.3] References: <20011210075001.JESP3849.mta06-svc.ntlworld.com@there> <20011210085948.B22592@neptune.deep-ocean.local> In-Reply-To: <20011210085948.B22592@neptune.deep-ocean.local> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011210085150.TANF27606.mta05-svc.ntlworld.com@there> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > [I think this question should be redirected to -questions or -net, but > anyway...] should only programming questions be posted here? > do you have IPFIREWALL in your kernel ? is is configured "default to > deny" ? This is typically what is bugginig me when natd fails to write a > packet : a nasty firewall rule... I have a ipfw rules file, the point is I want to log the deny natd messages, not see them. > > man ipfw & read the handbook, section networking (correct me if i'm > wrong). I don't think this is an ipfw issue - the failure msg comes from natd, not ipfw. Could be wrong of course! > > Olivier > > On Mon, Dec 10, 2001 at 07:49:37AM +0000, Mike D wrote: > > I have in my rc.conf: > > > > natd_enable="YES" > > natd_interface="xl1" > > natd_flags="-f /etc/natd.conf" > > > > and in /etc/natd.conf: > > > > interface xl1 > > dynamic yes > > use_sockets yes > > same_ports yes > > log_denied yes > > > > however, since I am still seeing the "host4 natd[198]: failed to write > > packet back (Permission denied)" messages, I'm guessing "log_denied" is > > not being picked up. > > > > Any help appreciated. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 0:55:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cody.jharris.com (cody.jharris.com [205.238.128.83]) by hub.freebsd.org (Postfix) with ESMTP id D97DF37B405 for ; Mon, 10 Dec 2001 00:55:30 -0800 (PST) Received: from localhost (nick@localhost) by cody.jharris.com (8.11.1/8.9.3) with ESMTP id fBA8tOa30504; Mon, 10 Dec 2001 02:55:24 -0600 (CST) (envelope-from nick@rogness.net) Date: Mon, 10 Dec 2001 02:55:23 -0600 (CST) From: Nick Rogness X-Sender: nick@cody.jharris.com To: Mike D Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: natd ignores "natd_flags"? In-Reply-To: <20011210085150.TANF27606.mta05-svc.ntlworld.com@there> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 10 Dec 2001, Mike D wrote: > > [I think this question should be redirected to -questions or -net, but > > anyway...] -Moved to questions. Nick Rogness - Keep on Routing in a Free World... "FreeBSD: The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 1: 6:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mars-gw.morning.ru (ns.morning.ru [195.161.98.5]) by hub.freebsd.org (Postfix) with ESMTP id 07E6637B417; Mon, 10 Dec 2001 01:06:31 -0800 (PST) Received: from NDNM ([195.161.98.250]) by mars-gw.morning.ru (8.11.5/8.11.5) with ESMTP id fBA93N624568; Mon, 10 Dec 2001 16:03:31 +0700 (KRAT) Date: Mon, 10 Dec 2001 16:08:15 +0700 From: Igor M Podlesny X-Mailer: The Bat! (v1.53d) Business Organization: Morning Network X-Priority: 3 (Normal) Message-ID: <136249500292.20011210160815@morning.ru> To: Terry Lambert Cc: Dima Dorfman , chris@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re[2]: jail.c.patch (allowing to use hostnames when invoking jail(8)) In-Reply-To: <3C141F9E.D7681BCC@mindspring.com> References: <20011209205442.C8D0A3E2F@bazooka.trit.org> <3C141F9E.D7681BCC@mindspring.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Dima Dorfman wrote: >> Here's an updated patch which is a result of comments from a few >> people. The changes are: (a) deconfuse the usage message by not >> naming two arguments as "hostname" (that was sloppiness on my part), >> and (b) remove a redundant inet_aton call (gethostbyname(3) will DTRT >> with an IP address) [1]. >> >> [1] It probably shouldn't, since as others have pointed out to me, >> "1.1.1.1" is a valid DNS name. The correct solution would be to have >> a flag which makes it explicit whether the argument is an IP address >> or DNS name, but few, if any, other programs in the system do this, >> and I don't think this is a good place to start. > This is why the inte_aton() call is still necessary. > And it won't "do the right thing", per se, since it wants to kick > a DNS query off for a purely numeric tupple set. > I, and I suspect others, start jails up at boot time, well before > any network connection has been established. You are requiring us > to install caching DNS servers with preloaded caches, and delay > starting up until after the servers are started. > This is marginally unacceptable. > One of the reasons I use jails is to establish a set of 13 virtual > hosts, one of which acts as the root DNS server for a testbed that > pretends that it is the real Internet root DNS server. > In other jails, I run "client" DNS machines with DNS delegations > from this "root" server, which also do inter-host (inter-jail, in > reality) zone synchornization. > If/when these zones are in conflict (e.g. when I run a NAT in two > or more of them with a 10.x address block for each, and then VPN > between them using address block translation to translate 10.1 to > 10.2 and vice versa in each, with DNS forwarding for the block so > that name lookups work as expected), then I am screwed by your > change, since I can't have two canonical names for the same IP > address later. > Please call inet_aton(), and then _only_ if that fails, call the > gethostbyname(). :) My patch was originally made because of this namely. I wanted just to have add-on working as fall-through. Hope you guys will commit it. ;) p.s. I keep my jails hostnames in /etc/hosts > PS: Your man pages are better. > -- Terry -- Igor mailto:poige@morning.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 1:37:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from straylight.ringlet.net (sentinel.office1.bg [217.75.134.126]) by hub.freebsd.org (Postfix) with SMTP id 62D7537B416 for ; Mon, 10 Dec 2001 01:37:21 -0800 (PST) Received: (qmail 14066 invoked by uid 1000); 10 Dec 2001 09:36:28 -0000 Date: Mon, 10 Dec 2001 11:36:28 +0200 From: Peter Pentchev To: "Crist J . Clark" Cc: Joesh Juphland , hackers@FreeBSD.ORG Subject: Re: install and boot on secondary master possible ? seems not... Message-ID: <20011210113628.E757@straylight.oblivion.bg> Mail-Followup-To: "Crist J . Clark" , Joesh Juphland , hackers@FreeBSD.ORG References: <20011208010101.Y8975@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011208010101.Y8975@blossom.cjclark.org>; from cjc@FreeBSD.ORG on Sat, Dec 08, 2001 at 01:01:01AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Dec 08, 2001 at 01:01:01AM -0800, Crist J . Clark wrote: > On Fri, Dec 07, 2001 at 07:23:07PM -0700, Joesh Juphland wrote: > > Hello, > > > > I have a machine whose primary IDE controller is blown. Only the secondary > > works. So, I connected my single IDe drive as the secondary master, and > > proceeded to install FreeBSD. > > > > The install went flawlessly. I installed with the FreeBSD boot manager(the > > first choice on that screen of three boot loader choices) > > > > When I boot, I see the F1 .. Default menu. If I wait, or if I hit enter, I > > am told: > > > > Read error > > > > I reinstalled, and this time didn't use the freeBSD boot manager. Just the > > normal loader. This time, after POST, it goes directly to "read error". > > > > So, what can I do to this disk to make it possible for the machine to boot > > off what I have installed on the secondary master ? I used the fixit disk > > to mount the drive and tried to edit things in /boot, but I cannot figure > > out exactly what to change. > > This is most likely a problem with your BIOS. It doesn't matter what > disk lables and boot blocks you put on your drive on the secondary > controller if the BIOS never attempts to boot it. Go into the BIOS > settings and see if there is a way to try to boot off of that > drive. If that fails, make up a boot floppy. I would assume that the 'F1 .. Default' menu that Joesh is referring to is the BootEasy menu. That would mean that the BIOS does actually get as far as read and pass control to the MBR boot loader. G'luck, Peter -- I am the meaning of this sentence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 1:39:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from diablo.ovinet.hu (diablo.ovinet.hu [217.13.33.205]) by hub.freebsd.org (Postfix) with ESMTP id 9540537B405 for ; Mon, 10 Dec 2001 01:39:52 -0800 (PST) Received: from diablo.ovinet.hu (titanic@localhost [127.0.0.1]) by localhost (MX V4.2 AXP/OpenVMS) with ESMTP id fBA9jUmF012069 for ; Mon, 10 Dec 2001 10:45:30 +0100 Received: (from titanic@localhost) by diablo.ovinet.hu (8.12.0.Beta19/8.12.0.Beta19/Debian 8.12.0.Beta19) id fBA9jUZp012067 for freebsd-hackers@FreeBSD.ORG; Mon, 10 Dec 2001 10:45:30 +0100 Date: Mon, 10 Dec 2001 10:45:30 +0100 From: KAISER Laszlo To: freebsd-hackers@FreeBSD.ORG Subject: Re: SSL_connect fails Message-ID: <20011210104529.A8829@ovinet.hu> References: <20011209184143.H12621@ovinet.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <20011209184143.H12621@ovinet.hu>; from titanic@ovinet.hu on Sun, Dec 09, 2001 at 06:41:43PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Dec 09, 2001 at 06:41:43PM +0100, KAISER Laszlo wrote: > I'm doing a port of a little OpenSSL program to FreeBSD from linux, but the > code which works fine on linux fails on FreeBSD at SSL_connect(). > This function allways returns with -1 and SSL_errno is 1. To answer myself; The problem was trivial. OpenSSL couldn't seed random generator for correct entropy without /dev/urandom or without a specified file, therefore i had to create a temporary file which consists of enough random numbers (1024). This was problem on solaris port, too, but on BSD it caused by chroot environment. OpenSSL got the filename consists of entropy from an environment value named RANDFILE. Some notice: I think an API hasn't consists of exit() calls and if i send a NULL pointer to an API call, it couldn't SEGFAULT. OpenSSL does. I think it is not a feature, or if it is, i'like to turn off. :/ TiTaNiC -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 2:29:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mix.premierbank.dp.ua (premierbank.atlantis.dp.ua [193.108.46.78]) by hub.freebsd.org (Postfix) with SMTP id 49A8837B417 for ; Mon, 10 Dec 2001 02:29:23 -0800 (PST) Received: (qmail 6697 invoked by uid 85); 10 Dec 2001 10:28:44 -0000 Received: from kot@premierbank.dp.ua by mix.premierbank.dp.ua with qmail-scanner-1.01 (. Clean. Processed in 0.363278 secs); 10 Dec 2001 10:28:44 -0000 Received: from kot.premierbank.dp.ua (HELO kot) (192.168.2.136) by mix.premierbank.dp.ua with SMTP; 10 Dec 2001 10:28:43 -0000 Message-ID: <002c01c18165$71512d70$8802a8c0@premierbank.dp.ua> From: "Konstantin Reznichenko" To: Cc: , Subject: IPsec & dummynet - HELP! Date: Mon, 10 Dec 2001 12:28:43 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 Disposition-Notification-To: "Konstantin Reznichenko" X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, All. I do not know already where to dig! Is IPSec the tunnel through dial-up, on it(him) with the help UUCP the file exchange is organized. IPSEC.CONF: #!/bin/sh flush; spdflush; add 10.0.0.51 10.0.0.50 esp 0x10051 -m tunnel -E 3des-cbc "123456789012345678901234" -A hmac-sha1 "12345678901234567890"; add 10.0.0.50 10.0.0.51 esp 0x10050 -m tunnel -E 3des-cbc "123456789012345678901234" -A hmac-sha1 "12345678901234567890"; spdadd 192.168.2.0/24 192.168.3.0/24 any -P out ipsec esp/tunnel/10.0.0.50-10.0.0.51/require; spdadd 192.168.3.0/24 192.168.2.0/24 any -P in ipsec esp/tunnel/10.0.0.51-10.0.0.50/require; RC.CONF: gif_interfaces = "gif0" gifconfig_gif0 = " 10.0.0.50 10.0.0.51" ifconfig_gif0 = " inet 192.168.2.249 192.168.3.212 netmask 255.255.255.0" static_routes = "0" route_0 = "-net 192.168.3.0 192.168.3.212 -netmask 255.255.255.0" ipsec_enable = "YES" I try to organize restriction of the traffic in the tunnel through gif0: IPFW pipe 10 config bw 33600bit/s out IPFW queue 1 config pipe 10 weight 50 IPFW add 60100 queue 1 tcp from any 540 to any via gif0 Under this rule any package does not get, TCPDUMP on gif0 - is silent. On seen IPsec packages do not reach up to ipfw, and at once get in the tunnel. The search in the Internet has not brought expected results. In OpenBSD there is a special device "enc" intended specially for these purposes (through him(it) passes all traffic before that how to get in the tunnel). Really on FreeBSD it cannot be realized? Somebody decided(solved) similar tasks? I shall be grateful for any information! Kot. PS: I am sorry for bad English To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 2:41:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from straylight.ringlet.net (sentinel.office1.bg [217.75.134.126]) by hub.freebsd.org (Postfix) with SMTP id C2DF437B417 for ; Mon, 10 Dec 2001 02:41:45 -0800 (PST) Received: (qmail 14527 invoked by uid 1000); 10 Dec 2001 10:40:49 -0000 Date: Mon, 10 Dec 2001 12:40:49 +0200 From: Peter Pentchev To: Terry Lambert Cc: Dima Dorfman , chris@FreeBSD.ORG, Igor M Podlesny , freebsd-hackers@FreeBSD.ORG Subject: Re: jail.c.patch (allowing to use hostnames when invoking jail(8)) Message-ID: <20011210124049.G757@straylight.oblivion.bg> Mail-Followup-To: Terry Lambert , Dima Dorfman , chris@FreeBSD.ORG, Igor M Podlesny , freebsd-hackers@FreeBSD.ORG References: <20011209205442.C8D0A3E2F@bazooka.trit.org> <3C141F9E.D7681BCC@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C141F9E.D7681BCC@mindspring.com>; from tlambert2@mindspring.com on Sun, Dec 09, 2001 at 06:36:14PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Dec 09, 2001 at 06:36:14PM -0800, Terry Lambert wrote: > Dima Dorfman wrote: > > Here's an updated patch which is a result of comments from a few > > people. The changes are: (a) deconfuse the usage message by not > > naming two arguments as "hostname" (that was sloppiness on my part), > > and (b) remove a redundant inet_aton call (gethostbyname(3) will DTRT > > with an IP address) [1]. > > > > [1] It probably shouldn't, since as others have pointed out to me, > > "1.1.1.1" is a valid DNS name. The correct solution would be to have > > a flag which makes it explicit whether the argument is an IP address > > or DNS name, but few, if any, other programs in the system do this, > > and I don't think this is a good place to start. > > This is why the inte_aton() call is still necessary. [snip] > Please call inet_aton(), and then _only_ if that fails, call the > gethostbyname(). How about inet_pton() and getnameinfo()? G'luck, Peter -- If I had finished this sentence, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 4: 8:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 4A82237B416 for ; Mon, 10 Dec 2001 04:08:47 -0800 (PST) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.33 #1) id 16DPEj-0001Dt-00 for freebsd-hackers@freebsd.org; Mon, 10 Dec 2001 14:08:45 +0200 Received: from localhost ([127.0.0.1] helo=pampa.cs.huji.ac.il ident=danny) by pampa.cs.huji.ac.il with esmtp (Exim 3.22 #2) id 16DPEj-00095k-00 for freebsd-hackers@FreeBSD.ORG; Mon, 10 Dec 2001 14:08:45 +0200 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: freebsd-hackers@FreeBSD.ORG Subject: irq Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Dec 2001 14:08:45 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, in trying to make a klm out of the meteor driver, and in the process im stumbling onto some problems - major understatment :-) for starters, how can i get an unshared irq? at the moment the irq is shared among the video, scsi and the meteor. im using bus_alloc_resource(dev, SYS_RES_IRQ, &sc->irq_rid,0, ~0, 1, RF_ACTIVE|RF_SHAREABLE); if i drop the RF_SHAREABLE it failes :-) the device gets the irq way before i load the module: pci2: (vendor=0x8086, dev=0x1223) at 9.0 irq 9 tia, danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 4:31:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from email01.aon.at (WARSL401PIP7.highway.telekom.at [195.3.96.115]) by hub.freebsd.org (Postfix) with SMTP id A038437B445 for ; Mon, 10 Dec 2001 04:30:20 -0800 (PST) Received: (qmail 657318 invoked from network); 10 Dec 2001 12:30:15 -0000 Received: from n054p029.adsl.highway.telekom.at (HELO mail.kpost.com) ([213.33.6.189]) (envelope-sender ) by qmail1.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 10 Dec 2001 12:30:15 -0000 From: "contractor@kpost.com" To: "5062@lycos.com" <5062@lycos.com> Message-ID: <1007991311.0499569422@mail.kpost.com> Subject: Reduce Travel Costs MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 10 Dec 2001 04:30:20 -0800 (PST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Take Control Of Your Conference Calls

Long Distance Conferencing
Only 18 Cents Per Minute

Connects Up To 100 Participants=21

  • No setup fees
  • No contracts or monthly fees
  • Call anytime, from anywhere, to anywhere
  • International Dial In 18 cents per minute
  • Simplicity in set up and administration
  • Operator Help available 24/7

    • G= et the best quality, the easiest to use, and lowest rate in the industry.

    If you like saving = money, fill out the form below and one of our consultants will contact you.

    Required Input Field*

    Name*
    Web Address*
    Company Name*
    State*
    Business Phone*
    Home Phone
    Email Address*
    Type of Business



    This ad is being sent in compliance with Senate Bill 1618= , Title 3, Section 301. You have recently visited our web site, referral or affiliate sit= es which indicated you were interested in communication services. If this email is reaching = you in error and you feel that you have not contacted us, Click here. We sincerely apologize, and assure you will be r= emoved from our distribution list.

    To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 4:42:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from breg.mc.mpls.visi.com (breg.mc.mpls.visi.com [208.42.156.101]) by hub.freebsd.org (Postfix) with ESMTP id 95FF137B416; Mon, 10 Dec 2001 04:42:38 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by breg.mc.mpls.visi.com (Postfix) with ESMTP id 6EE0F2D0DE9; Mon, 10 Dec 2001 06:42:32 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBACfEx28778; Mon, 10 Dec 2001 06:41:14 -0600 (CST) (envelope-from hawkeyd) Date: Mon, 10 Dec 2001 06:41:14 -0600 From: D J Hawkey Jr To: Michael Lucas Cc: Nik Clayton , Lamont Granquist , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011210064114.A28609@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011209172652.A25745@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011209172652.A25745@blackhelicopters.org>; from mwlucas@FreeBSD.ORG on Sun, Dec 09, 2001 at 05:26:52PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Dec 09, at 05:26 PM, Michael Lucas wrote: > > On Sun, Dec 09, 2001 at 12:17:03PM -0600, D J Hawkey Jr wrote: > > So far, I've made three patchfiles that can be applied to 4.2REL and 4.3REL. > > Not exactly the repertoire one would need to garner interest and momentum. > > Everything starts somewhere. When I wrote my first FreeBSD article a > few years ago, I had no idea where it would lead. Keep it up, and the > Project might well ask you to make it an official FreeBSD resource. > > If you start now, in a few months you'll have patchsets for 4.2-R, > 4.3-R, 4.4-R, and 4.5-R. That looks like a pretty serious investment > of time and/or dedication to me. Yup. To me, too. But as I said, without some sort of barometer I can read that tells me what's going on with -STABLE or -CURRENT that is even half- way portable and worthwhile to previous releases, I'm afraid it'd be a rather stale resource pretty quickly. Ideally, it would be grand if the hackers/committers could mail me the patches they make to -STABLE, and I could then backport them to previous releases, where possible. Just so I'm not read as someone "on the fence", I am prepared to make public the patches I've made (as well as those from others), but there are considerable hurdles to be worked out: - They would be patches against whatever is in place on a machine at a particluar time. If it was something-REL, they might not apply cleanly to something-STABLE or something-HACKED. At a bare minimum, this implies that the user/admin be well-acquainted with the syntax of unified diffs, and the basics of "code discovery". - After such patches are applied, how does one guard against a subsequent 'cvsup' blowing away these "private" updates. That is, someone applies my patch for ICH sound to their 4.3REL base. How can that source be "protected" against a 'cvsup RELENG_4_3' upgrade, which will overwrite those patched files? These two points alone might (should?) scare off all but the most anal of SysAdmins. If such a resource was available (patches site), it seems to me the target audience would be quite small, indeed. One of the things I'm really asking (without explicitely stating so) is, "How can such a site, more specifically, it's content, be made sufficiently painless to install?" I can backport to 4.2REL and 4.3REL (I have these releases), but I don't have the resources (read: "free partitions") to accomodate 4.1 or 4.4. > It's cliche, but: ten thousand lines of code begins with the first > #define. (Hmmmm.... click click click... okay, style(9) says it > should be the first #include. But you get the idea.) Actually, the first part of a source module should be The Abstract. :-) > Michael Lucas Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 4:55: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brea.mc.mpls.visi.com (brea.mc.mpls.visi.com [208.42.156.100]) by hub.freebsd.org (Postfix) with ESMTP id DE9CF37B417 for ; Mon, 10 Dec 2001 04:55:03 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by brea.mc.mpls.visi.com (Postfix) with ESMTP id 0630C2DE00D; Mon, 10 Dec 2001 06:55:03 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBACt2W28836; Mon, 10 Dec 2001 06:55:02 -0600 (CST) (envelope-from hawkeyd) Date: Mon, 10 Dec 2001 06:55:02 -0600 (CST) Message-Id: <200112101255.fBACt2W28836@sheol.localdomain> Mime-Version: 1.0 X-Newsreader: knews 0.9.8a Reply-To: hawkeyd@visi.com Organization: if (!FIFO) if (!LIFO) break; References: <20011209175137.B13554_clan.nothing-going-on.org@ns.sol.net> <20011209221607.78673.qmail_web21108.mail.yahoo.com@ns.sol.net> In-Reply-To: <20011209221607.78673.qmail_web21108.mail.yahoo.com@ns.sol.net> From: hawkeyd@visi.com (D J Hawkey Jr) Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux X-Original-Newsgroups: sol.lists.freebsd.hackers To: hitmaster2k@yahoo.com, hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20011209221607.78673.qmail_web21108.mail.yahoo.com@ns.sol.net>, hitmaster2k@yahoo.com writes: > hi, > does anyone need any special skills to manage the > kind of branch you are talking about... > example.. RELENG_4_4_BUGFIX > > what kind of skills and experience in FreeBSD would > be needed for this kind of branch.... I'm still confused about what this branch would contain; bug fixes to 4.4REL? Isn't that what -STABLE is all about? >> I could maintain a "not-FreeBSD-sanctioned" site >> for patches of -CURRENT and -STABLE code applyable >> to previous releases, >> but that would only muddy >> the FreeBSD maintenance and distribution waters >> that I think work well for >> what they're intended to address, as well as open >> myself up to all sorts >> of support and maintenance headaches. > > i wouldn't mind helping.... :-) Consider yourself "enlisted". :-) What sorts of skills/interests have you to offer? I'm a pretty fair C coder, and can comfortably play with shell, awk, and sed scripts, too. I'm already involved in a few "global" projects, so I'm not too bad at managing/applying/supplying submissions. And guess what? I can write man pages and other documentation, too! I have web/ftp space available at my ISP (midwest USA), and it has some pretty fat pipes. Some logistics and details still need to be worked out before I/we really start anything (I hope to work them out in this thread, if I'm not kicked out for being off-topic). > -Hiten, Is that pronounced with a long or short 'i'? Dave -- Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 5:41:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from breg.mc.mpls.visi.com (breg.mc.mpls.visi.com [208.42.156.101]) by hub.freebsd.org (Postfix) with ESMTP id C9C4537B416; Mon, 10 Dec 2001 05:41:52 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by breg.mc.mpls.visi.com (Postfix) with ESMTP id BF1712D0624; Mon, 10 Dec 2001 07:41:51 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBADfp429294; Mon, 10 Dec 2001 07:41:51 -0600 (CST) (envelope-from hawkeyd) Date: Mon, 10 Dec 2001 07:41:51 -0600 From: D J Hawkey Jr To: Michael Lucas Cc: hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011210074151.A29219@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011209172652.A25745@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011209172652.A25745@blackhelicopters.org>; from mwlucas@FreeBSD.ORG on Sun, Dec 09, 2001 at 05:26:52PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [this is a re-post; apparently my first didn't take?] On Dec 09, at 05:26 PM, Michael Lucas wrote: > > On Sun, Dec 09, 2001 at 12:17:03PM -0600, D J Hawkey Jr wrote: > > So far, I've made three patchfiles that can be applied to 4.2REL and 4.3REL. > > Not exactly the repertoire one would need to garner interest and momentum. > > Everything starts somewhere. When I wrote my first FreeBSD article a > few years ago, I had no idea where it would lead. Keep it up, and the > Project might well ask you to make it an official FreeBSD resource. > > If you start now, in a few months you'll have patchsets for 4.2-R, > 4.3-R, 4.4-R, and 4.5-R. That looks like a pretty serious investment > of time and/or dedication to me. Yup. To me, too. But as I said, without some sort of barometer I can read that tells me what's going on with -STABLE or -CURRENT that is even half- way portable and worthwhile to previous releases, I'm afraid it'd be a rather stale resource pretty quickly. Ideally, it would be grand if the hackers/committers could mail me the patches they commit to -STABLE, and I could then backport them to previous releases, where possible. But, I could easily see this overwhelming me in very short order! Just so I'm not read as someone "on the fence", I am prepared to make public the patches I've made (as well as those from others), but there are considerable hurdles to be worked out: - They would be patches against whatever is in place on a machine at a particluar time. If it was something-REL, they might not apply cleanly to something-STABLE or something-HACKED. At a bare minimum, this implies that the user/admin be well-acquainted with the syntax of unified diffs, and the basics of "code discovery". - After such patches are applied, how does one guard against a subsequent 'cvsup' blowing away these "private" updates. That is, someone applies my patch for ICH sound to their 4.3REL base. How can that source be "protected" against a 'cvsup RELENG_4_3' upgrade, which will overwrite those patched files? These two points alone might (should?) scare off all but the most anal of SysAdmins. If such a resource was available (patches site), it seems to me the target audience would be quite small, indeed. One of the things I'm really asking (without explicitely stating so) is, "How can such a site, more specifically, it's content, be made sufficiently painless to install?" I can backport to 4.2REL and 4.3REL (I have these releases), but I don't have the resources (read: "free partitions") to accomodate 4.1 or 4.4. > It's cliche, but: ten thousand lines of code begins with the first > #define. (Hmmmm.... click click click... okay, style(9) says it > should be the first #include. But you get the idea.) Actually, the first part of a source module should be The Abstract. :-) > Michael Lucas Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 5:50:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 14DC737B41D; Mon, 10 Dec 2001 05:50:40 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id fBADocH29311; Mon, 10 Dec 2001 08:50:38 -0500 (EST) (envelope-from mwlucas) Date: Mon, 10 Dec 2001 08:50:38 -0500 From: Michael Lucas To: D J Hawkey Jr Cc: Michael Lucas , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011210085038.A29274@blackhelicopters.org> References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011209172652.A25745@blackhelicopters.org> <20011210074151.A29219@sheol.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011210074151.A29219@sheol.localdomain>; from hawkeyd@visi.com on Mon, Dec 10, 2001 at 07:41:51AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Dec 10, 2001 at 07:41:51AM -0600, D J Hawkey Jr wrote: > [this is a re-post; apparently my first didn't take?] Nope, we got it. As penance for re-sending, your penance is to implement the ideas discussed below. :-) > On Dec 09, at 05:26 PM, Michael Lucas wrote: > Yup. To me, too. But as I said, without some sort of barometer I can read > that tells me what's going on with -STABLE or -CURRENT that is even half- > way portable and worthwhile to previous releases, I'm afraid it'd be a > rather stale resource pretty quickly. Not necessarily. Read cvs-all. Grab interesting updates (such as the recent TCP changes) and see if they compile. Some will, some won't. If you become known as "Mr. MFS for old releases", people will start sending you sligtly modified patches based on their work, and it will take off. Or, the public will decide they aren't interested, and it won't. In either case, the next time you start a project you'll be taken far more seriously. > - They would be patches against whatever is in place on a machine > at a particluar time. If it was something-REL, they might not > apply cleanly to something-STABLE or something-HACKED. At a bare > minimum, this implies that the user/admin be well-acquainted with > the syntax of unified diffs, and the basics of "code discovery". > - After such patches are applied, how does one guard against a > subsequent 'cvsup' blowing away these "private" updates. That is, > someone applies my patch for ICH sound to their 4.3REL base. How > can that source be "protected" against a 'cvsup RELENG_4_3' > upgrade, which will overwrite those patched files? Valid concerns. You should definitely post this on the web page. > These two points alone might (should?) scare off all but the most anal > of SysAdmins. If such a resource was available (patches site), it seems > to me the target audience would be quite small, indeed. One of the things > I'm really asking (without explicitely stating so) is, "How can such a > site, more specifically, it's content, be made sufficiently painless > to install?" Hmmm... I think you're stuck with patch. If you have your patches properly arranged, however, you can make the patch very simple to install. cd /usr/src patch < /home/admin/4.1R-patchset.diff make buildkernel installkernel > I can backport to 4.2REL and 4.3REL (I have these releases), but I > don't have the resources (read: "free partitions") to accomodate 4.1 > or 4.4. Well, 4.1 is rather elderly. If you support the older ones, and make your techniques available for other people, you might well find that someone else supports 4.4 for you. Or, just keep your eyes open for a used hard drive you can scarf from somewhere. Heck, someone at work offered me a 20 gig drive for free because he'd just updated to a 120-gig drive. Unfortunately, I didn't take him up on it or I'd ship it to you, hopefully solving the hardest issue. This could take a lot of time, but I think a lot of people would thank you for it. ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 6: 6: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 2BF5837B419; Mon, 10 Dec 2001 06:06:01 -0800 (PST) Received: from pool0062.cvx22-bradley.dialup.earthlink.net ([209.179.198.62] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16DR3n-0006Sh-00; Mon, 10 Dec 2001 06:05:35 -0800 Message-ID: <3C14C135.CB9099AD@mindspring.com> Date: Mon, 10 Dec 2001 06:05:41 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Pentchev Cc: Dima Dorfman , chris@FreeBSD.ORG, Igor M Podlesny , freebsd-hackers@FreeBSD.ORG Subject: Re: jail.c.patch (allowing to use hostnames when invoking jail(8)) References: <20011209205442.C8D0A3E2F@bazooka.trit.org> <3C141F9E.D7681BCC@mindspring.com> <20011210124049.G757@straylight.oblivion.bg> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Pentchev wrote: > > This is why the inte_aton() call is still necessary. > [snip] > > Please call inet_aton(), and then _only_ if that fails, call the > > gethostbyname(). > > How about inet_pton() and getnameinfo()? You know, I first thought of this, but then I backed off it. The problem is that the addres is passed in as a 32 bit int, not as the address of a sockaddr_in. I think it would take a lot of work to make the jail code IPv6-safe. You'd have to talk to Poul for details, but it's pretty clear that the "splitting" of the virtual address aliases per jail on the interface(s) in question is very IPv4 specific, right now. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 6:29:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brea.mc.mpls.visi.com (brea.mc.mpls.visi.com [208.42.156.100]) by hub.freebsd.org (Postfix) with ESMTP id 55D8437B417 for ; Mon, 10 Dec 2001 06:29:14 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by brea.mc.mpls.visi.com (Postfix) with ESMTP id 40C9D2DE058; Mon, 10 Dec 2001 08:29:13 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBAETCk29509; Mon, 10 Dec 2001 08:29:12 -0600 (CST) (envelope-from hawkeyd) Date: Mon, 10 Dec 2001 08:29:12 -0600 From: D J Hawkey Jr To: Michael Lucas Cc: hackers@freebsd.org Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011210082912.A29365@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011209172652.A25745@blackhelicopters.org> <20011210074151.A29219@sheol.localdomain> <20011210085038.A29274@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011210085038.A29274@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Mon, Dec 10, 2001 at 08:50:38AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Dec 10, at 08:50 AM, Michael Lucas wrote: > > On Mon, Dec 10, 2001 at 07:41:51AM -0600, D J Hawkey Jr wrote: > > [this is a re-post; apparently my first didn't take?] > > Nope, we got it. As penance for re-sending, your penance is to > implement the ideas discussed below. :-) You did, eh? Hmm. It didn't show up in the INN mirror I monitor (sol.net Network Services, Milwaukee, WI). Sorry. > > On Dec 09, at 05:26 PM, Michael Lucas wrote: > > Yup. To me, too. But as I said, without some sort of barometer I can read > > that tells me what's going on with -STABLE or -CURRENT that is even half- > > way portable and worthwhile to previous releases, I'm afraid it'd be a > > rather stale resource pretty quickly. > > Not necessarily. Read cvs-all. Grab interesting updates (such as the > recent TCP changes) and see if they compile. Some will, some won't. I'll look for this. > If you become known as "Mr. MFS for old releases", people will start > sending you sligtly modified patches based on their work, and it will > take off. Or, the public will decide they aren't interested, and it > won't. In either case, the next time you start a project you'll be > taken far more seriously. Well, this'd be my third "global" project. But the other two are rather obscure. > > - They would be patches against whatever is in place on a machine > > at a particluar time. If it was something-REL, they might not > > apply cleanly to something-STABLE or something-HACKED. At a bare > > minimum, this implies that the user/admin be well-acquainted with > > the syntax of unified diffs, and the basics of "code discovery". > > - After such patches are applied, how does one guard against a > > subsequent 'cvsup' blowing away these "private" updates. That is, > > someone applies my patch for ICH sound to their 4.3REL base. How > > can that source be "protected" against a 'cvsup RELENG_4_3' > > upgrade, which will overwrite those patched files? > > Valid concerns. You should definitely post this on the web page. I thought I read somewhere that the cvsup config file had options to support "protecting" source modules, but I pro'lly didn't read it right. Setting file attributes as read-only would work, but the possibility then exists that some module wouldn't be updated that really ought to be, or that cvsup would fail altogether. Or, let cvsup overwrite the patched modules, and the user/admin would have to re-apply the patches, which would likely generate rejects. Grr. If there's an upshot to this, it is that only still-supported releases fall into this trap, -STABLE and RELENG_(release - 1). Well, other hackers like me, who patch their systems "independantly", could also have problems. > Hmmm... I think you're stuck with patch. If you have your patches > properly arranged, however, you can make the patch very simple to > install. As long as the user/admin understands that the patch is very target- specific, yes. If the target has moved a little, though, things may well get a bit hairy. I guess I don't want "caveat emptor" as the fallback position I would have to assume, though I'd make myself available to help with such cases. > > I can backport to 4.2REL and 4.3REL (I have these releases), but I > > don't have the resources (read: "free partitions") to accomodate 4.1 > > or 4.4. > > Well, 4.1 is rather elderly. If you support the older ones, and make > your techniques available for other people, you might well find that > someone else supports 4.4 for you. Hopefully. And yes, the "rather elderly" would be potential targets. Isn't that the point of all this, after all? > This could take a lot of time, but I think a lot of people would thank > you for it. I take it you, for one, would like to see this take off. I make it two. Another in this thread volunteered his involvement. That's enough for me; I'll give it a shot. When I've got the site up, who (or what mailing list) do I want to notify? > ==ml As they say, "Thank you for your support". Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 6:35:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 1578737B405 for ; Mon, 10 Dec 2001 06:35:25 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id fBAEZOW29553; Mon, 10 Dec 2001 09:35:24 -0500 (EST) (envelope-from mwlucas) Date: Mon, 10 Dec 2001 09:35:24 -0500 From: Michael Lucas To: D J Hawkey Jr Cc: hackers@freebsd.org Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011210093524.A29538@blackhelicopters.org> References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011209172652.A25745@blackhelicopters.org> <20011210074151.A29219@sheol.localdomain> <20011210085038.A29274@blackhelicopters.org> <20011210082912.A29365@sheol.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011210082912.A29365@sheol.localdomain>; from hawkeyd@visi.com on Mon, Dec 10, 2001 at 08:29:12AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Dec 10, 2001 at 08:29:12AM -0600, D J Hawkey Jr wrote: > You did, eh? Hmm. It didn't show up in the INN mirror I monitor (sol.net > Network Services, Milwaukee, WI). Sorry. Ah, INN. It made it to the mailing list. > As long as the user/admin understands that the patch is very target- > specific, yes. If the target has moved a little, though, things may well > get a bit hairy. I guess I don't want "caveat emptor" as the fallback > position I would have to assume, though I'd make myself available to > help with such cases. Well, here's something most people don't really realize: "caveat emptor" is the default FreeBSD fallback position. We don't guarantee any support of our product. These higher-level admins you worry about should know darn well the implications of their actions. And there's always a worst-case fallback; blow away /usr/src and reinstall from known good media. > Hopefully. And yes, the "rather elderly" would be potential targets. > Isn't that the point of all this, after all? True. My point is, you must start somewhere. > When I've got the site up, who (or what mailing list) do I want to notify? If at all possible, take out a full-page ad in the New York Times. FreeBSD could really use the exposure. Failing that, a posting on this list would be fine. :) ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 6:48: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.bu.edu (CS.BU.EDU [128.197.10.2]) by hub.freebsd.org (Postfix) with ESMTP id DA63637B417 for ; Mon, 10 Dec 2001 06:47:58 -0800 (PST) Received: from csa.bu.edu (evms@csa [128.197.12.3]) by cs.bu.edu (8.10.1/8.10.1) with ESMTP id fBAElvF11825 for ; Mon, 10 Dec 2001 09:47:57 -0500 (EST) Received: (from evms@localhost) by csa.bu.edu (8.10.1/8.10.1) id fBAElrY25522; Mon, 10 Dec 2001 09:47:53 -0500 (EST) Date: Mon, 10 Dec 2001 09:47:53 -0500 (EST) Message-Id: <200112101447.fBAElrY25522@csa.bu.edu> From: Evan Sarmiento To: freebsd-hackers@freebsd.org Subject: jail.c patch Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I've been reading this thread. I made the augustments to the patch so that it first checks if it is an IP address, if it is not, it then tries to see if it is a hostname. If neither are true it exits with an error. Hope this is what you're looking for, Evan --- jail.c Mon Jul 30 06:19:54 2001 +++ jail.mod Mon Dec 10 07:51:03 2001 @@ -10,9 +10,8 @@ * */ -#include +#include #include -#include #include #include #include @@ -21,12 +20,13 @@ int main(int argc, char **argv) { + struct hostent *hp; struct jail j; int i; struct in_addr in; if (argc < 5) - errx(1, "Usage: %s path hostname ip-number command ...\n", + errx(1, "Usage: %s path hostname address command ...\n", argv[0]); i = chdir(argv[1]); if (i) @@ -36,14 +36,23 @@ j.path = argv[1]; j.hostname = argv[2]; i = inet_aton(argv[3], &in); + if (!i) - errx(1, "Couldn't make sense of ip-number\n"); + hp = gethostbyname(argv[3]); + if (hp == NULL) + errx(1, "gethostbyname(%s): %s (and) inet_aton(%s): Could not +make sense of ip-number", argv[3], hstrerror(h_errno), argv[3] ); + + if (hp) + in = *(struct in_addr *)hp->h_addr; + j.ip_number = ntohl(in.s_addr); i = jail(&j); if (i) - err(1, "Imprisonment failed"); + err(1, "Imprisonment failed"); i = execv(argv[4], argv + 4); if (i) - err(1, "execv(%s)", argv[4]); + err(1, "execv(%s)", argv[4]); + exit (0); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 7:27:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from parhelion.firedrake.org (parhelion.firedrake.org [212.135.138.219]) by hub.freebsd.org (Postfix) with ESMTP id A46CF37B419 for ; Mon, 10 Dec 2001 07:27:42 -0800 (PST) Received: from float by parhelion.firedrake.org with local (Exim 3.32 #1 (Debian)) id 16DSLF-0000VO-00 for ; Mon, 10 Dec 2001 15:27:41 +0000 Date: Mon, 10 Dec 2001 15:27:41 +0000 To: hackers@freebsd.org Subject: send-prs are being harvested for spam Message-ID: <20011210152741.A1620@parhelion.firedrake.org> Mail-Followup-To: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i From: void Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I created an address to use with send-pr, and it's been getting spam. Perhaps mail sent with send-pr can have the addresses slightly munged before they're placed on a web page? Is there a more appropriate list for discussing this? -- Ben "An art scene of delight I created this to be ..." -- Sun Ra To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 8:21:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 0391637B405 for ; Mon, 10 Dec 2001 08:21:22 -0800 (PST) Received: from isi.edu (ras34.isi.edu [128.9.176.134]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id fBAGLGN14157; Mon, 10 Dec 2001 08:21:16 -0800 (PST) Message-ID: <3C14E0F7.3060902@isi.edu> Date: Mon, 10 Dec 2001 08:21:11 -0800 From: Lars Eggert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.6) Gecko/20011203 X-Accept-Language: en, de MIME-Version: 1.0 To: "S. Aeschbacher" Cc: Hal Snyder , hackers@freebsd.org Subject: Re: cable modem connection problem References: <20011206071926.QTHW27606.mta05-svc.ntlworld.com@there> <3C0F7966.908CD6E6@bturtle.ch> <3C1005ED.4090001@isi.edu> <20011207000918.JIID10846.mta07-svc.ntlworld.com@there> <3C100F4D.3080900@isi.edu> <85k7vyzspp.fsf@stiegl.niksun.com> <87n10s8rn6.fsf@cb293842-b.rmdws1.il.home.com> <3C13ABED.B249B519@bturtle.ch> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG S. Aeschbacher wrote: > Hal Snyder wrote: > > [snip] > >>Sounds as if the MAC of the upstream provider occasionally changes. >>Don't know enough about cable to understand it better, and problem is >>gone now so can't check for sure. >> > As far as my cases are concerned, the MAC address does not change. When > the arp entry is deleted, the same MAC of the gateway is inserted into > the arp table. Actually, it sounds like your provider actively mucks with the link after a certain time - are these "residential" pipes? If so, they may do that to prevent you from running servers. In any case, I'd be surprised if this really was a FreeBSD issue; I really think it's the provider doing something weird. (And on Windows you'll never see the problem, since you typically reboot more frequently than every 10 hours anyway... :-) Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 8:24:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tapil.com (h00609737bede.ne.mediaone.net [65.96.154.231]) by hub.freebsd.org (Postfix) with ESMTP id 62DBF37B417 for ; Mon, 10 Dec 2001 08:24:25 -0800 (PST) Received: from shw2w0001.tapil.com (shw2w0001.shr.intel.com [10.243.69.27]) by tapil.com (8.11.6/8.11.6) with ESMTP id fBAGNmq98717; Mon, 10 Dec 2001 11:23:49 -0500 (EST) (envelope-from lists-ma@tapil.com) Message-Id: <5.1.0.14.0.20011210112100.00a72ef0@inside.tapil.com> X-Sender: madler@inside.tapil.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 10 Dec 2001 11:23:48 -0500 To: Matthew Dillon From: Michael Adler Subject: Re: FreeBSD performs worse that Linux - Patches #2 & #3 Cc: hackers@FreeBSD.ORG In-Reply-To: <200112100418.fBA4IJr43345@apollo.backplane.com> References: <20011206114725.A836@sheol.localdomain> <200112090811.fB98BYD35974@apollo.backplane.com> <200112100402.fBA42Ge21093@w2xo.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 11:18 PM 12/09/2001, Matthew Dillon wrote: > However, if you are running 4.4-RELEASE and haven't updated then you > don't have the patch and it is relevant. While it is a significant > fix, > it is just one out of a number of fixes made since 4.4-RELEASE. The > easiest solution is typically to ugprade your machine to the > latest -stable. Unfortunately, upgrading at this exact moment could > be problematic as apparently a number of people are having problems > with recent IDE changes, at least judging by recent list postings. Too many patches have flown by for me to track exactly what files changed without errors. Would it be possible to summarize with a list of files to change or, even better, one more complete patch file from 4.4-RELEASE? thank you, -Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 8:43: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 9D6AE37B405 for ; Mon, 10 Dec 2001 08:42:57 -0800 (PST) Received: from pool0187.cvx22-bradley.dialup.earthlink.net ([209.179.198.187] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16DTVy-0002F0-00; Mon, 10 Dec 2001 08:42:50 -0800 Message-ID: <3C14E611.16F58D60@mindspring.com> Date: Mon, 10 Dec 2001 08:42:57 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Evan Sarmiento Cc: freebsd-hackers@freebsd.org Subject: Re: jail.c patch References: <200112101447.fBAElrY25522@csa.bu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Evan Sarmiento wrote: > > Hello, > > I've been reading this thread. I made the augustments to the > patch so that it first checks if it is an IP address, if it is not, > it then tries to see if it is a hostname. If neither are true > it exits with an error. > > Hope this is what you're looking for, Cool! This is perfect! It won't mess up any existing scripts, and it will let people go by name, if they want! Actually, now it's tempting to rewrite acouple of scripts to take basename of argv[0], and call jail with that... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 8:58:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 0EA8D37B416 for ; Mon, 10 Dec 2001 08:58:36 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id fBAGwJ048744; Mon, 10 Dec 2001 08:58:19 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id fBAGwFY03265; Mon, 10 Dec 2001 08:58:15 -0800 (PST) (envelope-from jdp) Date: Mon, 10 Dec 2001 08:58:15 -0800 (PST) Message-Id: <200112101658.fBAGwFY03265@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: lamont@scriptkiddie.org Subject: Re: detecting linux emulation in rtld.c? In-Reply-To: <20011129233851.H40312-100000@coredump.scriptkiddie.org> References: <20011129233851.H40312-100000@coredump.scriptkiddie.org> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20011129233851.H40312-100000@coredump.scriptkiddie.org>, Lamont Granquist wrote: > can anyone suggest a method of determining inside > libexec/rtld-elf/rtld.c if a binary being run is native or linux > emulation? If the FreeBSD dynamic linker is running at all, the binary is probably native. Linux programs use the Linux dynamic linker, not ours. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 9: 3:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 9EBC337B405 for ; Mon, 10 Dec 2001 09:03:32 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id fBAH3Wk11569; Mon, 10 Dec 2001 09:03:32 -0800 (PST) (envelope-from rizzo) Date: Mon, 10 Dec 2001 09:03:31 -0800 From: Luigi Rizzo To: hackers@freebsd.org Subject: is anyone seeing stray clock interrupts ? Message-ID: <20011210090331.A11197@iguana.aciri.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, while doing some timing measurements on our test boxes, i noticed that if I compile a kernel with options HZ=1000 I get a number of stray clock interrupts (i.e. occasionally a clock interrupts comes way before its due time -- other measurements showed that the two "regular" clock interrupts around the stray one have the regular spacing, and the stray one tends to be very close to the previous regular one). A quick way to reveal this behaviour is to add the code below to kern_clock.c, and check the value of sysctl hw.short_ticks every now and then. Irrespective of the amount of other events (e.g. network interrupts), for those values of HZ which give problems (e.g. HZ=1000), the count steadily increases over time, maybe by one every few seconds or faster. For lower values of HZ (eg HZ=100, HZ=200, HZ=400) the count remains stationary (that is, i see the 2-3 events, but those might occur at init time when things are not settled yet). I am seeing the problem on STABLE, both on a set of 750MHz Pentium machines, and on a 486-133 (the "net4501"), and with approximately the same frequency (over time). The Pentiums seems to start having problems between HZ=400 and HZ=500, the net4501 seems to start having trouble at HZ=1000. Any ideas on what could be the cause ? cheers luigi Code to test if you are having short ticks, to be put in src/sys/kern/kern_clock.c: --- before hardclock() --- static u_int32_t short_ticks = 0; SYSCTL_ULONG(_hw, OID_AUTO, short_ticks, CTLFLAG_RW, &short_ticks, 0, "How many short ticks"); --- within hardclock(), near the beginning ------------- { static struct timeval prev_t, t; int delta; microuptime(&t); delta = (t.tv_usec - prev_t.tv_usec) + (t.tv_sec - prev_t.tv_sec)*1000000; if (delta * hz < 500000) short_ticks++; else prev_t = t; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 9:16:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8A50737B405 for ; Mon, 10 Dec 2001 09:16:37 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBAHGZ346896; Mon, 10 Dec 2001 09:16:35 -0800 (PST) (envelope-from dillon) Date: Mon, 10 Dec 2001 09:16:35 -0800 (PST) From: Matthew Dillon Message-Id: <200112101716.fBAHGZ346896@apollo.backplane.com> To: Michael Adler Cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD performs worse that Linux - Patches #2 & #3 References: <20011206114725.A836@sheol.localdomain> <200112090811.fB98BYD35974@apollo.backplane.com> <200112100402.fBA42Ge21093@w2xo.pgh.pa.us> <5.1.0.14.0.20011210112100.00a72ef0@inside.tapil.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> be problematic as apparently a number of people are having problems :> with recent IDE changes, at least judging by recent list postings. : :Too many patches have flown by for me to track exactly what files changed :without errors. Would it be possible to summarize with a list of files to :change or, even better, one more complete patch file from 4.4-RELEASE? : :thank you, :-Michael You would have to look at the commit logs yourself to a get a list. There have been a huge number of changes. In regards to updating, refer to www.freebsd.org. There are a number of ways to update but the easiest is probably to use cvsup to maintain a local source tree and do the buildworld yourself. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 9:47: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 2D75C37B416 for ; Mon, 10 Dec 2001 09:47:04 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBAHqMV01179; Mon, 10 Dec 2001 09:52:23 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112101752.fBAHqMV01179@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Danny Braniss Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: irq In-reply-to: Your message of "Mon, 10 Dec 2001 14:08:45 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Dec 2001 09:52:22 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > hi, > in trying to make a klm out of the meteor driver, and in > the process im stumbling onto some problems - major understatment :-) > > for starters, how can i get an unshared irq? at the moment the irq is > shared among the video, scsi and the meteor. > im using > bus_alloc_resource(dev, SYS_RES_IRQ, &sc->irq_rid,0, ~0, 1, > RF_ACTIVE|RF_SHAREABLE); > if i drop the RF_SHAREABLE it failes :-) Er, you don't seem to understand how PCI interrupts work. You must (for now) pass RF_SHAREABLE in; eventually the PCI code will stick it there for you anyway. All PCI interrupts are shareable; you can't "ask" for an unshared vector; you get the one you're given, and you should be thankful for that much. Lots of people are going without these days. 8( -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 10:11:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id B18B737B405; Mon, 10 Dec 2001 10:11:09 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id fBAIB9Z11961; Mon, 10 Dec 2001 10:11:09 -0800 (PST) (envelope-from rizzo) Date: Mon, 10 Dec 2001 10:11:09 -0800 From: Luigi Rizzo To: Mike Smith Cc: Danny Braniss , freebsd-hackers@FreeBSD.ORG Subject: Re: irq Message-ID: <20011210101109.A11664@iguana.aciri.org> References: <200112101752.fBAHqMV01179@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200112101752.fBAHqMV01179@mass.dis.org> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Dec 10, 2001 at 09:52:22AM -0800, Mike Smith wrote: > stick it there for you anyway. All PCI interrupts are shareable; you > can't "ask" for an unshared vector; you get the one you're given, and you > should be thankful for that much. Lots of people are going without these > days. 8( actually, some people wouldn't mind _not_ having one :) cheers luigi (who never loses his sense of humor) (ok, this is a bit cryptic, you have to go and figure it out in -net...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 10:51:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dayab.ch (mail.dayab.ch [193.135.253.139]) by hub.freebsd.org (Postfix) with SMTP id 0224437B41C for ; Mon, 10 Dec 2001 10:51:32 -0800 (PST) Received: (qmail 14390 invoked from network); 10 Dec 2001 18:50:39 -0000 Received: from unknown (HELO bturtle.ch) (193.135.253.141) by mail.dayab.ch with SMTP; 10 Dec 2001 18:50:39 -0000 Message-ID: <3C15127B.8B8C8B3A@bturtle.ch> Date: Mon, 10 Dec 2001 19:52:27 +0000 From: "S. Aeschbacher" X-Mailer: Mozilla 4.75 [en] (X11; U; OpenBSD 3.0 i386) X-Accept-Language: en MIME-Version: 1.0 To: Lars Eggert , hackers@freebsd.org Subject: Re: cable modem connection problem References: <20011206071926.QTHW27606.mta05-svc.ntlworld.com@there> <3C0F7966.908CD6E6@bturtle.ch> <3C1005ED.4090001@isi.edu> <20011207000918.JIID10846.mta07-svc.ntlworld.com@there> <3C100F4D.3080900@isi.edu> <85k7vyzspp.fsf@stiegl.niksun.com> <87n10s8rn6.fsf@cb293842-b.rmdws1.il.home.com> <3C13ABED.B249B519@bturtle.ch> <3C14E0F7.3060902@isi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi [snip] > Actually, it sounds like your provider actively mucks with the link > after a certain time - are these "residential" pipes? If so, they may do This is possible, but I did not verify it (what kind of "mucking" could cause such kind of behaviour?). most of them are "better" residental pipes. > that to prevent you from running servers. In any case, I'd be surprised > if this really was a FreeBSD issue; I really think it's the provider > doing something weird. Never said it was a FreeBSD issue, I saw OpenBSD behave exactly the same. The local IP stays the same, Gateway IP stays the same, Gateway MAC stays the same, don't know about the "modem", maybe it needs an arp-query from the client from time to time... (Just guessing) The problem seems to occur only on Samsung modems. > (And on Windows you'll never see the problem, since you typically reboot > more frequently than every 10 hours anyway... :-) Cannot confirm this as i don't use windows. I heard of a friend of mine, that he has running a windows ftp-server for days on a pipe from the same provider with another modem (a Com21) and that he is not experiencing any of the problems mentioned. Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 11: 3: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.bu.edu (CS.BU.EDU [128.197.10.2]) by hub.freebsd.org (Postfix) with ESMTP id C6A1E37B417 for ; Mon, 10 Dec 2001 11:02:48 -0800 (PST) Received: from csa.bu.edu (evms@csa [128.197.12.3]) by cs.bu.edu (8.10.1/8.10.1) with ESMTP id fBAJ2mF00121 for ; Mon, 10 Dec 2001 14:02:48 -0500 (EST) Received: (from evms@localhost) by csa.bu.edu (8.10.1/8.10.1) id fBAJ2gS23874; Mon, 10 Dec 2001 14:02:42 -0500 (EST) Date: Mon, 10 Dec 2001 14:02:42 -0500 (EST) Message-Id: <200112101902.fBAJ2gS23874@csa.bu.edu> From: Evan Sarmiento To: freebsd-hackers@freebsd.org Subject: jail.c patch (fixed) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey guys. heh. Sorry about that, I just fixed it and it all works fine. :-) Exams are making my brain fry. Here is the revised patch. Thanks, - Evan --- jail.c Mon Jul 30 06:19:54 2001 +++ jail.mod Mon Dec 10 14:00:57 2001 @@ -10,9 +10,8 @@ * */ -#include +#include #include -#include #include #include #include @@ -21,12 +20,13 @@ int main(int argc, char **argv) { + struct hostent *hp; struct jail j; int i; struct in_addr in; if (argc < 5) - errx(1, "Usage: %s path hostname ip-number command ...\n", + errx(1, "Usage: %s path hostname address command ...\n", argv[0]); i = chdir(argv[1]); if (i) @@ -36,14 +36,26 @@ j.path = argv[1]; j.hostname = argv[2]; i = inet_aton(argv[3], &in); - if (!i) - errx(1, "Couldn't make sense of ip-number\n"); + + if (!i) { + hp = gethostbyname(argv[3]); + + if (hp == NULL) + errx(1, "gethostbyname(%s): %s (and) inet_aton(%s): Could not + make sense of ip-number", argv[3], hstrerror(h_errno), argv[3] ); + + else if (hp) + in = *(struct in_addr *)hp->h_addr; + + } + j.ip_number = ntohl(in.s_addr); i = jail(&j); if (i) - err(1, "Imprisonment failed"); + err(1, "Imprisonment failed"); i = execv(argv[4], argv + 4); if (i) - err(1, "execv(%s)", argv[4]); + err(1, "execv(%s)", argv[4]); + exit (0); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 11:36:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21103.mail.yahoo.com (web21103.mail.yahoo.com [216.136.227.105]) by hub.freebsd.org (Postfix) with SMTP id B294837B417 for ; Mon, 10 Dec 2001 11:36:29 -0800 (PST) Message-ID: <20011210193629.98528.qmail@web21103.mail.yahoo.com> Received: from [62.254.0.5] by web21103.mail.yahoo.com via HTTP; Mon, 10 Dec 2001 11:36:29 PST Date: Mon, 10 Dec 2001 11:36:29 -0800 (PST) From: Hiten Pandya Subject: Re: cable modem connection problem To: s.aeschbacher@bturtle.ch Cc: hackers@FreeBSD.org In-Reply-To: <3C15127B.8B8C8B3A@bturtle.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >what kind of "mucking" could cause such kind of >behaviour?. this kind of problem did occur to me several times with NTL (http://ntl.com/) in UK... there were installing a Universal Shared Bandwith Router in their CO (Central Office), after they installed this piece of sh*t, the bandwith was throttled from 5.00pm evening to 5.00am morning, which was to slow down users from downloading large files i.e. Music Sharing and such.... but after 5.00am, it was all fine and back to 85.0KBps when before 5.00am and after 5.00pm was around 12.0KBps which is sad but was true for a while till users complained about it... (like me)... so that is a possibility, or it could be that the signal you are receiving (cable modem signal) is very weak.... thats a possibility too... =Hiten = ===== -Hiten, Thank You, Yours Sincerely, Hiten Pandya, __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 11:38:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 7756837B405; Mon, 10 Dec 2001 11:38:24 -0800 (PST) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.33 #1) id 16DWFq-00022p-00; Mon, 10 Dec 2001 21:38:22 +0200 Received: from localhost ([127.0.0.1] helo=pampa.cs.huji.ac.il ident=danny) by pampa.cs.huji.ac.il with esmtp (Exim 3.22 #2) id 16DWFq-0009U1-00; Mon, 10 Dec 2001 21:38:22 +0200 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Mike Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: irq In-Reply-To: Message from Mike Smith of "Mon, 10 Dec 2001 09:52:22 PST." <200112101752.fBAHqMV01179@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Dec 2001 21:38:22 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Er, you don't seem to understand how PCI interrupts work. > to Er is human, to ... :-) The meteor driver was causing problems with the adpatec, so i thought if i could reasigne the irq it would help. anyway i think i found a work around. now the problem is that at full size, 24bit colour, i'm getting FIFO errors :-( thanks anyway, danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 11:48:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id C05C337B405; Mon, 10 Dec 2001 11:48:04 -0800 (PST) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id fBA80X804332; Mon, 10 Dec 2001 08:00:33 GMT (envelope-from nik) Date: Mon, 10 Dec 2001 08:00:32 +0000 From: Nik Clayton To: D J Hawkey Jr Cc: Nik Clayton , Lamont Granquist , hackers@freebsd.org Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011210080032.A4215@canyon.nothing-going-on.org> References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011209121703.A23726@sheol.localdomain>; from hawkeyd@visi.com on Sun, Dec 09, 2001 at 12:17:03PM -0600 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 09, 2001 at 12:17:03PM -0600, D J Hawkey Jr wrote: > Seems to me that were I to do this, and I would, it would only be as viab= le > as the patches themselves. That is, I (and any contributors) would have to > be able to stay abreast of those things going on in -STABLE that could get > backported to previous releases ("could" being a significant word here). Well, yeah. That's pretty much a pre-requisite. Doesn't mean that you need 100% coverage though. If you produce something that only gets in 80% of the patches that could be applied back that's still better than what we have now. And it makes it easier for someone else to help out with the missing 20%. > So far, I've made three patchfiles that can be applied to 4.2REL and 4.3R= EL. > Not exactly the repertoire one would need to garner interest and momentum. It's a start. What's the URL? N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwUa6AACgkQk6gHZCw343We1QCeIdndKZkmuVZ2agh3e3vHpeU3 y8AAnAsUQPqoXCnC7ICkd1yJVKvngAYt =SzVR -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 12: 7:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id AEDC637B416 for ; Mon, 10 Dec 2001 12:07:19 -0800 (PST) Received: from isi.edu (ras31.isi.edu [128.9.176.131]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id fBAK7CN21585; Mon, 10 Dec 2001 12:07:13 -0800 (PST) Message-ID: <3C1515D9.2090007@isi.edu> Date: Mon, 10 Dec 2001 12:06:49 -0800 From: Lars Eggert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.6) Gecko/20011203 X-Accept-Language: en, de MIME-Version: 1.0 To: "S. Aeschbacher" Cc: hackers@freebsd.org Subject: Re: cable modem connection problem References: <20011206071926.QTHW27606.mta05-svc.ntlworld.com@there> <3C0F7966.908CD6E6@bturtle.ch> <3C1005ED.4090001@isi.edu> <20011207000918.JIID10846.mta07-svc.ntlworld.com@there> <3C100F4D.3080900@isi.edu> <85k7vyzspp.fsf@stiegl.niksun.com> <87n10s8rn6.fsf@cb293842-b.rmdws1.il.home.com> <3C13ABED.B249B519@bturtle.ch> <3C14E0F7.3060902@isi.edu> <3C15127B.8B8C8B3A@bturtle.ch> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG S. Aeschbacher wrote: > This is possible, but I did not verify it (what kind of "mucking" > could cause such kind of behaviour?). most of them are "better" > residental pipes. Having a packet filter drop your traffic after you haven't done ARP/DHCP in a while. But I agree that's pretty far-fetched. > Never said it was a FreeBSD issue, I saw OpenBSD behave exactly the same. Ah sorry, missed that in earlier mails. > The problem seems to occur only on Samsung modems. Ah! Another data point. Then I'd assume it's the modem. Have you tried powercycling it? (That should keep the ARP cache on the client intact). Tried to email Samsung? Is there a firmware update? > Cannot confirm this as i don't use windows. I heard of a friend of > mine, that he has running a windows ftp-server for days on a pipe > from the same provider with another modem (a Com21) and that he is > not experiencing any of the problems mentioned. Can he/she tcpdump for ARP packets? Maybe Windows' ARP cache timeout is lower than FreeBSD's. Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 12:15:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from w250.z064001178.sjc-ca.dsl.cnc.net (w250.z064001178.sjc-ca.dsl.cnc.net [64.1.178.250]) by hub.freebsd.org (Postfix) with SMTP id 15E2637B405 for ; Mon, 10 Dec 2001 12:15:50 -0800 (PST) Received: (qmail 940 invoked by uid 1000); 10 Dec 2001 20:16:11 -0000 Date: Mon, 10 Dec 2001 12:15:49 -0801 From: Jos Backus To: hackers@freebsd.org Subject: sscanf(..., "%lld", ...) broken? Message-ID: <20011210201611.GB595@lizzy.bugworks.com> Reply-To: Jos Backus Mail-Followup-To: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.24i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is this PR-worthy? I am seeing this in both -stable and -current. The lftp author claims it's our bug, not his. Jos ----- Forwarded message from "Alexander V. Lukyanov" ----- Date: Mon, 10 Dec 2001 11:47:16 +0300 From: "Alexander V. Lukyanov" To: Jos Backus Subject: Re: Bug in lftp 2.4.8? On Sun, Dec 09, 2001 at 10:47:43PM -0801, Jos Backus wrote: > Something strange seems to be happening with the interpretation of the size(?) > field: > > lizzy:/usr/ports/ftp/lftp/work/lftp-2.4.8# lftp koobera.math.uic.edu > lftp koobera.math.uic.edu:~> cd software > cd ok, cwd=/software > lftp koobera.math.uic.edu:/software> ls > -rw-r--r-- 579194430267867860 1996-01-04 16:22 acid.shar.3.gz > > This is on FreeBSD -current. Thought you would want to know. It seems to me that sscanf on FreeBSD does not correctly handle long long type (%lld). There is another similar report, the reporter says that initializing the variable to 0 before sscanf helps. This indicates a bug in the libc library. You can report a bug to FreeBSD team. -- Alexander. ----- End forwarded message ----- -- Jos Backus _/ _/_/_/ Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ josb@cncdsl.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 12:37:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 6A2EB37B416; Mon, 10 Dec 2001 12:37:33 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fBAKYwi08014; Mon, 10 Dec 2001 15:34:58 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 10 Dec 2001 15:34:58 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: D J Hawkey Jr Cc: Michael Lucas , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux In-Reply-To: <20011210074151.A29219@sheol.localdomain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 10 Dec 2001, D J Hawkey Jr wrote: > I can backport to 4.2REL and 4.3REL (I have these releases), but I don't > have the resources (read: "free partitions") to accomodate 4.1 or 4.4. For 4.3-RELEASE, there's a RELENG_4_3 branch in CVS that security fixes are committed to; you'd probably want to generate patches with respects to the head of the RELENG_4_3 branch so as not to have to duplicate the security bug fixes, only the non-security ones that don't go into RELENG_4_3. Otherwise, you'd lose out on some of the more desirable bug fixes :-). Note also that as a release gets older, it drops off the "security-officer supported" list, due to a gradual increase in the level of work required to support the release. This tends to happen when a major subsystem has to be replaced in order to fix the bug, rather than a minor tweak being sufficient. For example, the death of RELENG_3 from the SO perspective was when ncurses had to be replaced, rather than patched, to cover all known holes. This required relinking of countless binaries, making a binary update relatively infeasible, and requiring a high level of investment in order to update past changed APIs. How fast the window runs out on a release depends on what needs fixing, so it's hard to predict when it will happen. Having the "release branches" has made generating security updates far more efficient, and permitted us to handle a binary update model for userland binaries. Without version control in place, as it wasn't for this stuff for a long time, it was very hard to generate relative patches, manage large numbers of patchsets for various versions, or keep any notion of binary updates in order. It doesn't fix the windowing issue, but it does make it easier to deal with. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 12:59:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id CC52137B417; Mon, 10 Dec 2001 12:59:13 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.0/8.11.0) with UUCP id fBAKx3B55280; Mon, 10 Dec 2001 21:59:03 +0100 (CET) Received: from mail.cicely.de (cicely20.cicely.de [10.1.1.22]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id fBAKxHtx098656; Mon, 10 Dec 2001 21:59:17 +0100 (CET)?g (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0/8.11.0) with ESMTP id fBAKxHW05271; Mon, 10 Dec 2001 21:59:17 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.6/8.11.6) id fBAKx7S12918; Mon, 10 Dec 2001 21:59:07 +0100 (CET) (envelope-from ticso) Date: Mon, 10 Dec 2001 21:59:05 +0100 From: Bernd Walter To: Danny Braniss Cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: irq Message-ID: <20011210215905.E11774@cicely8.cicely.de> References: <200112101752.fBAHqMV01179@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Dec 10, 2001 at 09:38:22PM +0200, Danny Braniss wrote: > > Er, you don't seem to understand how PCI interrupts work. > > > to Er is human, to ... :-) > > The meteor driver was causing problems with the adpatec, so i thought > if i could reasigne the irq it would help. anyway i think i found a work > around. > now the problem is that at full size, 24bit colour, i'm getting FIFO errors :-( A PCI slot has 4 irq lines named INTA to INTD. On PCs all slots share the same 4 physical irqs and the lines are hardwired on the board in alternating order to each slot. If you want cards not to share irqs you have to swap slots until you get what you want - you can't enforce it with software. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 13:24:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brea.mc.mpls.visi.com (brea.mc.mpls.visi.com [208.42.156.100]) by hub.freebsd.org (Postfix) with ESMTP id C689937B417; Mon, 10 Dec 2001 13:24:25 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by brea.mc.mpls.visi.com (Postfix) with ESMTP id ADCF22DDF22; Mon, 10 Dec 2001 15:24:24 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBALOJx01443; Mon, 10 Dec 2001 15:24:19 -0600 (CST) (envelope-from hawkeyd) Date: Mon, 10 Dec 2001 15:24:14 -0600 From: D J Hawkey Jr To: Nik Clayton Cc: hackers@freebsd.org Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011210152414.A1367@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011210080032.A4215@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011210080032.A4215@canyon.nothing-going-on.org>; from nik@freebsd.org on Mon, Dec 10, 2001 at 08:00:32AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Dec 10, at 08:00 AM, Nik Clayton wrote: > > On Sun, Dec 09, 2001 at 12:17:03PM -0600, D J Hawkey Jr wrote: > > Seems to me that were I to do this, and I would, it would only be as viable > > as the patches themselves. That is, I (and any contributors) would have to > > be able to stay abreast of those things going on in -STABLE that could get > > backported to previous releases ("could" being a significant word here). > > Well, yeah. That's pretty much a pre-requisite. > > Doesn't mean that you need 100% coverage though. If you produce > something that only gets in 80% of the patches that could be applied > back that's still better than what we have now. And it makes it easier > for someone else to help out with the missing 20%. Huh? You completely list me with this. Are you trying to say that some feature of a patch that applies to just the last three of four prior releases is OK, 'cuz right now none are (except for security fixes to RELENG_(current - 1))? > > So far, I've made three patchfiles that can be applied to 4.2REL and 4.3REL. > > Not exactly the repertoire one would need to garner interest and momentum. > > It's a start. What's the URL? You're kidding, right? I only started thinking about doing this yesterday! The patches are sitting right here, in $(HOME)/projects. > N > -- > FreeBSD: The Power to Serve http://www.freebsd.org/ > FreeBSD Documentation Project http://www.freebsd.org/docproj/ > > --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 13:39:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id A2CA937B417 for ; Mon, 10 Dec 2001 13:38:41 -0800 (PST) Received: (qmail 5587 invoked from network); 10 Dec 2001 21:38:40 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 10 Dec 2001 21:38:40 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20011209145628.64563.qmail@web21104.mail.yahoo.com> Date: Mon, 10 Dec 2001 13:38:36 -0800 (PST) From: John Baldwin To: Hiten Pandya Subject: RE: about boot0 Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 09-Dec-01 Hiten Pandya wrote: > hi all, > is there a reason behind.. why all Windows related > boot > options are marked as DOS?... > > src/sys/boot/i386/boot0.s > > is it because of the 512-byte limit... Yes. There used to be a 1024 byte boot0 which did use different names (as well as auto-detecting the need for EDD) but it was backed out since it froze on a few systems. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 13:59:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brea.mc.mpls.visi.com (brea.mc.mpls.visi.com [208.42.156.100]) by hub.freebsd.org (Postfix) with ESMTP id 2C76437B416; Mon, 10 Dec 2001 13:59:27 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by brea.mc.mpls.visi.com (Postfix) with ESMTP id 1418A2DDBAB; Mon, 10 Dec 2001 15:59:25 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBALxOB01612; Mon, 10 Dec 2001 15:59:24 -0600 (CST) (envelope-from hawkeyd) Date: Mon, 10 Dec 2001 15:59:24 -0600 From: D J Hawkey Jr To: Robert Watson Cc: Michael Lucas , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011210155924.A1542@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011210074151.A29219@sheol.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.ORG on Mon, Dec 10, 2001 at 03:34:58PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Dec 10, at 03:34 PM, Robert Watson wrote: > > > On Mon, 10 Dec 2001, D J Hawkey Jr wrote: > > > I can backport to 4.2REL and 4.3REL (I have these releases), but I don't > > have the resources (read: "free partitions") to accomodate 4.1 or 4.4. > > For 4.3-RELEASE, there's a RELENG_4_3 branch in CVS that security fixes > are committed to; you'd probably want to generate patches with respects to > the head of the RELENG_4_3 branch so as not to have to duplicate the > security bug fixes, only the non-security ones that don't go into > RELENG_4_3. Otherwise, you'd lose out on some of the more desirable bug > fixes :-). Good point. > Note also that as a release gets older, it drops off the "security-officer > supported" list, due to a gradual increase in the level of work required > to support the release. > > [SNIP] > > How fast the window runs out on a release depends on what needs fixing, > so it's hard to predict when it will happen. Understood. > [SNIP] So, my question is then, just what is the policy defining non-current-but- still-supported-releases? Right now, these is exactly one such release, 4.3, for security fixes. Will there always be exactly one, such that when 4.5 is released, 4.3 will fall off the planet, and 4.4 takes its place? Or might there be two, 4.3 and 4.4? This comes 'round to one of my original questions, too: Why, as an example, isn't the DELACK patches Matt made recently considered "important" enough to be backported to RELENG_4_3 (which I have more generically referred to as RELENG_(current - 1) or RELENG_(release - 1))? It has been said that a fix might be backported to RELENG_(current - 1) that isn't necessarily a security issue; can't that be expanded to any (or perhaps just "major") fixes that don't imply a new feature of RELENG_(current)? Yes, I know this would mean additional work on the part of the hacker and committer, but is it not better they do it, than the likes of me, an user/ admin that isn't necessarily in a position to stay -STABLE, but knows enough of C and patch(1) to pro'lly get things right most of the time? The problem with the latter is that I can't possibly know of what's getting fixed in -STABLE (or -CURRENT), or the "severity" of the fixes, without considerably more effort than that of the former. Then, I still might not get it right, just 'cuz I'm not the expert the hacker/committer is. The site Michael and I have discussed will be hugely deficient in terms of what can be made available to any previous release (compared to what is applied to -STABLE), but as it sits right now, it would be better than nought for those that can't stay -STABLE. > Robert N M Watson FreeBSD Core Team, TrustedBSD Project Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 14: 2: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21102.mail.yahoo.com (web21102.mail.yahoo.com [216.136.227.104]) by hub.freebsd.org (Postfix) with SMTP id D197637B405 for ; Mon, 10 Dec 2001 14:01:53 -0800 (PST) Message-ID: <20011210220153.50612.qmail@web21102.mail.yahoo.com> Received: from [62.254.0.5] by web21102.mail.yahoo.com via HTTP; Mon, 10 Dec 2001 14:01:53 PST Date: Mon, 10 Dec 2001 14:01:53 -0800 (PST) From: Hiten Pandya Subject: [SUGGESTION] - JFS for FreeBSD To: current@FreeBSD.org Cc: hackers@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi all, this is a wild idea...suggestion... i wanted to ask if there were any _plans_ to port JFS (Journaled File System) to FreeBSD... as for JFS, it is developed by IBM for Linux and is licensed under GPL, so we could put this into src/gnu/ It is used on IBM MainFrames and Enterprise servers for high performance and maximum throughput... ===== -Hiten, Thank You, Yours Sincerely, Hiten Pandya, __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 14: 4: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 986A037B405; Mon, 10 Dec 2001 14:03:55 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 45898485; Mon, 10 Dec 2001 22:03:46 +0000 (GMT) Date: Mon, 10 Dec 2001 22:03:46 +0000 From: Josef Karthauser To: Hiten Pandya Cc: current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011210220346.F28634@tao.org.uk> Mail-Followup-To: Josef Karthauser , Hiten Pandya , current@FreeBSD.org, hackers@FreeBSD.org References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="dWYAkE0V1FpFQHQ3" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011210220153.50612.qmail@web21102.mail.yahoo.com>; from hitmaster2k@yahoo.com on Mon, Dec 10, 2001 at 02:01:53PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --dWYAkE0V1FpFQHQ3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 10, 2001 at 02:01:53PM -0800, Hiten Pandya wrote: > hi all, >=20 > this is a wild idea...suggestion... >=20 > i wanted to ask if there were any _plans_ to port > JFS (Journaled File System) to FreeBSD... Hi Hiten, Search the mail list archives (from www.freebsd.org) for JFS and XFS. You'll see that there have been many discussions about this over the last few years. Joe --dWYAkE0V1FpFQHQ3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwVMUEACgkQXVIcjOaxUBYv/QCfdKzLh5HAqOvc8Y1sSUr3aM7L TXQAoIe29fKvZqPL+kHz181B3MaupJkJ =dfZG -----END PGP SIGNATURE----- --dWYAkE0V1FpFQHQ3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 14:13: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 8592937B405; Mon, 10 Dec 2001 14:12:54 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id fBAMBnj32526; Mon, 10 Dec 2001 17:11:49 -0500 (EST) (envelope-from mwlucas) Date: Mon, 10 Dec 2001 17:11:49 -0500 From: Michael Lucas To: D J Hawkey Jr Cc: Robert Watson , Michael Lucas , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011210171149.A32462@blackhelicopters.org> References: <20011210074151.A29219@sheol.localdomain> <20011210155924.A1542@sheol.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011210155924.A1542@sheol.localdomain>; from hawkeyd@visi.com on Mon, Dec 10, 2001 at 03:59:24PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Dec 10, 2001 at 03:59:24PM -0600, D J Hawkey Jr wrote: > Right now, these is exactly one such release, 4.3, for security fixes. > Will there always be exactly one, such that when 4.5 is released, 4.3 > will fall off the planet, and 4.4 takes its place? Or might there be two, > 4.3 and 4.4? As far back as possible. Bad answer, I know, but it's much like the answer for 3.x. :( > This comes 'round to one of my original questions, too: Why, as an example, > isn't the DELACK patches Matt made recently considered "important" enough > to be backported to RELENG_4_3 (which I have more generically referred to > as RELENG_(current - 1) or RELENG_(release - 1))? It has been said that a > fix might be backported to RELENG_(current - 1) that isn't necessarily a > security issue; can't that be expanded to any (or perhaps just "major") > fixes that don't imply a new feature of RELENG_(current)? Because DELACK isn't a security problem. It's a performance problem. It's a serious performance problem, but not a security problem. They had to draw the line somewhere, and since the security-officer group is supporting this they get to call the shots. If you do a good enough job, perhaps you can wind up supporting this in the main source tree. :) > The site Michael and I have discussed will be hugely deficient in terms > of what can be made available to any previous release (compared to what > is applied to -STABLE), but as it sits right now, it would be better than > nought for those that can't stay -STABLE. Bingo. Something is better than nothing. -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 14:14:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id F3FA937B417 for ; Mon, 10 Dec 2001 14:14:15 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 72F9181D01; Mon, 10 Dec 2001 16:14:10 -0600 (CST) Date: Mon, 10 Dec 2001 16:14:10 -0600 From: Alfred Perlstein To: Hiten Pandya Cc: hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011210161410.L92148@elvis.mu.org> References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011210220153.50612.qmail@web21102.mail.yahoo.com>; from hitmaster2k@yahoo.com on Mon, Dec 10, 2001 at 02:01:53PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Hiten Pandya [011210 16:02] wrote: > hi all, > > this is a wild idea...suggestion... > > i wanted to ask if there were any _plans_ to port > JFS (Journaled File System) to FreeBSD... > > as for JFS, it is developed by IBM for Linux and > is licensed under GPL, so we could put this into > src/gnu/ > > It is used on IBM MainFrames and Enterprise servers > for > high performance and maximum throughput... I'm glad you took the time to read the marketting literature. The problem is that porting it is going to be a bit more complicated than just dumping it into src/gnu. Feel free to take a shot at porting it though, let us know when you're done. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 14:22:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 5E3D037B41F; Mon, 10 Dec 2001 14:22:29 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fBAMLAi09621; Mon, 10 Dec 2001 17:21:10 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 10 Dec 2001 17:21:10 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: D J Hawkey Jr Cc: Michael Lucas , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux In-Reply-To: <20011210155924.A1542@sheol.localdomain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 10 Dec 2001, D J Hawkey Jr wrote: > So, my question is then, just what is the policy defining > non-current-but- still-supported-releases? > > Right now, these is exactly one such release, 4.3, for security fixes. > Will there always be exactly one, such that when 4.5 is released, 4.3 > will fall off the planet, and 4.4 takes its place? Or might there be > two, 4.3 and 4.4? It depends on the level of work required, I expect. Right now, we're actively supporting 4.3-RELEASE and 4.4-RELEASE. Once we get to a point where the cost is greater than can be handled by our all-volunteer staff, we'll cut back. Currently, my hope is that we can keep supporting all branches of 4.x-RELEASE through to 5.0-RELEASE next year. If we try to avoid doing too many releases, that will be easier :-). > This comes 'round to one of my original questions, too: Why, as an > example, isn't the DELACK patches Matt made recently considered > "important" enough to be backported to RELENG_4_3 (which I have more > generically referred to as RELENG_(current - 1) or RELENG_(release - > 1))? It has been said that a fix might be backported to RELENG_(current > - 1) that isn't necessarily a security issue; can't that be expanded to > any (or perhaps just "major") fixes that don't imply a new feature of > RELENG_(current)? > > Yes, I know this would mean additional work on the part of the hacker > and committer, but is it not better they do it, than the likes of me, an > user/ admin that isn't necessarily in a position to stay -STABLE, but > knows enough of C and patch(1) to pro'lly get things right most of the > time? > > The problem with the latter is that I can't possibly know of what's > getting fixed in -STABLE (or -CURRENT), or the "severity" of the fixes, > without considerably more effort than that of the former. Then, I still > might not get it right, just 'cuz I'm not the expert the > hacker/committer is. The quick answer is: because the security-officer team is using the RELENG_4_x branches to generate binary updates, and has extremely limited resources. As such, the only things being merged onto the branch are security fixes. If the release engineering team is willing to take over the task of generating binary updates, and wants to broaden the scope of the branch, then such a proposal might make more sense. The goal of creating the branches was to permit version control to be applied to a series of updates that were previously being managed by hand: security patches. Using CVS allows the security-officer team to make the resulting patches more reproduceable, allows tag management for patchlevels, etc. While I'm sympathetic to the cause of "we want a -NOT-AS-AGRESSIVE-AS-STABLE-BUT-NOT-JUST-SECURITY-FIXES", I think our resources are already spread too thin to support that. If we were to move to a model where the branch was maintained by re@, who generated binary updates based on commits to the branch, and managed the QA process, looking at a broader scope of potential commits might be feasible. In such a scenario, the SO would work with re@ to get security fixes into the branch, but the re@ team would do the leg-work for updates and release notes. > The site Michael and I have discussed will be hugely deficient in terms > of what can be made available to any previous release (compared to what > is applied to -STABLE), but as it sits right now, it would be better > than nought for those that can't stay -STABLE. I think in practice you'll find what is needed is the ability to do local revision management in the form of branches. You may want to investigate version control software other than CVS, in that case. A number of consumers of FreeBSD, such as Yahoo!, make use of Perforce, importing the FreeBSD CVS repo hourly into a vendor branch. They can then maintain local changes relative to that branch easily. Note that you'd still be left with a heavy burden, however: QA. Part of the currently goal of RELENG_4_x is that each change be extensively tested, and usable by a wide audience with low levels of concern about picking up potentially conflicting changes. Most of the changes are very small, and as such have a higher probability of correctness. Broadening the charter for the release branch would mean expanding the QA process. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 14:39:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id CA90E37B405; Mon, 10 Dec 2001 14:39:37 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBAMj2V03977; Mon, 10 Dec 2001 14:45:02 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112102245.fBAMj2V03977@mass.dis.org> To: Bernd Walter Cc: Danny Braniss , Mike Smith , freebsd-hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: irq In-Reply-To: Message from Bernd Walter of "Mon, 10 Dec 2001 21:59:05 +0100." <20011210215905.E11774@cicely8.cicely.de> Date: Mon, 10 Dec 2001 14:45:02 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > A PCI slot has 4 irq lines named INTA to INTD. > On PCs all slots share the same 4 physical irqs and the lines are > hardwired on the board in alternating order to each slot. Not necessarily. This is the classic barber-pole or "PCI swizzle"; it's not mandated for motherboard designs though (but it is for bridges, since bridges have no other interrupt routing metadata). > If you want cards not to share irqs you have to swap slots until you > get what you want - you can't enforce it with software. This is closer to correct, though still not universally so. Better just to say that PCI interrupt routing is weird, and leave it at that. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 14:40:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts12-srv.bellnexxia.net (tomts12.bellnexxia.net [209.226.175.56]) by hub.freebsd.org (Postfix) with ESMTP id 8B71837B417 for ; Mon, 10 Dec 2001 14:39:58 -0800 (PST) Received: from xena.gsicomp.on.ca ([199.243.149.34]) by tomts12-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20011210223952.BIUU14728.tomts12-srv.bellnexxia.net@xena.gsicomp.on.ca>; Mon, 10 Dec 2001 17:39:52 -0500 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.1) with SMTP id fBAMVTW02353; Mon, 10 Dec 2001 17:31:29 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Alfred Perlstein" , "Hiten Pandya" Cc: References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> Subject: Re: [SUGGESTION] - JFS for FreeBSD Date: Mon, 10 Dec 2001 17:39:35 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > * Hiten Pandya [011210 16:02] wrote: > > hi all, > > > > this is a wild idea...suggestion... > > > > i wanted to ask if there were any _plans_ to port > > JFS (Journaled File System) to FreeBSD... > > > > as for JFS, it is developed by IBM for Linux and > > is licensed under GPL, so we could put this into > > src/gnu/ > > > > It is used on IBM MainFrames and Enterprise servers > > for > > high performance and maximum throughput... > > I'm glad you took the time to read the marketting literature. > > The problem is that porting it is going to be a bit more complicated > than just dumping it into src/gnu. > > Feel free to take a shot at porting it though, let us know > when you're done. I'm gainfully employed by IBM (although not for FreeBSD pursuits), and have had this on my TODO list for a while. The licence issue is a real sticky point, especially since the GPL and BSD licences are like oil and water. Because of the GPL licence, JFS support can never become part of the GENERIC kernel, and any related support tools will have to exist as separate binaries (newfs.jfs, fsck.jfs), as is currently done with the EXT2FS filesystem. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 14:43: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id CC14437B416 for ; Mon, 10 Dec 2001 14:43:00 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 701BD81D01; Mon, 10 Dec 2001 16:43:00 -0600 (CST) Date: Mon, 10 Dec 2001 16:43:00 -0600 From: Alfred Perlstein To: Matthew Emmerton Cc: Hiten Pandya , hackers@FreeBSD.ORG Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011210164300.N92148@elvis.mu.org> References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca>; from matt@gsicomp.on.ca on Mon, Dec 10, 2001 at 05:39:35PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Matthew Emmerton [011210 16:40] wrote: > > * Hiten Pandya [011210 16:02] wrote: > > > hi all, > > > > > > this is a wild idea...suggestion... > > > > > > i wanted to ask if there were any _plans_ to port > > > JFS (Journaled File System) to FreeBSD... > > > > > > as for JFS, it is developed by IBM for Linux and > > > is licensed under GPL, so we could put this into > > > src/gnu/ > > > > > > It is used on IBM MainFrames and Enterprise servers > > > for > > > high performance and maximum throughput... > > > > I'm glad you took the time to read the marketting literature. > > > > The problem is that porting it is going to be a bit more complicated > > than just dumping it into src/gnu. > > > > Feel free to take a shot at porting it though, let us know > > when you're done. > > I'm gainfully employed by IBM (although not for FreeBSD pursuits), and have > had this on my TODO list for a while. > > The licence issue is a real sticky point, especially since the GPL and BSD > licences are like oil and water. Because of the GPL licence, JFS support > can never become part of the GENERIC kernel, and any related support tools > will have to exist as separate binaries (newfs.jfs, fsck.jfs), as is > currently done with the EXT2FS filesystem. This is pretty much how they all work, on netbsd the LFS filesystem has its own suite of seperate utilities as well. Don't be discouraged, get hacking! :) -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 14:49: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from science.slc.edu (Science.SLC.Edu [198.83.6.248]) by hub.freebsd.org (Postfix) with ESMTP id BA1CD37B417 for ; Mon, 10 Dec 2001 14:48:55 -0800 (PST) Received: (from aschneid@localhost) by science.slc.edu (8.11.0/8.11.0) id fBAMlCW03248; Mon, 10 Dec 2001 17:47:12 -0500 (EST) (envelope-from aschneid) Date: Mon, 10 Dec 2001 17:47:11 -0500 From: Anthony Schneider To: Matthew Emmerton Cc: Alfred Perlstein , Hiten Pandya , hackers@FreeBSD.ORG Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011210174711.A3208@mail.slc.edu> References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca>; from matt@gsicomp.on.ca on Mon, Dec 10, 2001 at 05:39:35PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm no expert on journaled filesystems, but isn't the freebsd softupdates option similar? perhaps there could be an upgrade to offer options SOFTERUPDATES as an equal-but-different alternative to jfs? -Anthony. On Mon, Dec 10, 2001 at 05:39:35PM -0500, Matthew Emmerton wrote: > > * Hiten Pandya [011210 16:02] wrote: > > > hi all, > > > > > > this is a wild idea...suggestion... > > > > > > i wanted to ask if there were any _plans_ to port > > > JFS (Journaled File System) to FreeBSD... > > > > > > as for JFS, it is developed by IBM for Linux and > > > is licensed under GPL, so we could put this into > > > src/gnu/ > > > > > > It is used on IBM MainFrames and Enterprise servers > > > for > > > high performance and maximum throughput... > > > > I'm glad you took the time to read the marketting literature. > > > > The problem is that porting it is going to be a bit more complicated > > than just dumping it into src/gnu. > > > > Feel free to take a shot at porting it though, let us know > > when you're done. >=20 > I'm gainfully employed by IBM (although not for FreeBSD pursuits), and ha= ve > had this on my TODO list for a while. >=20 > The licence issue is a real sticky point, especially since the GPL and BSD > licences are like oil and water. Because of the GPL licence, JFS support > can never become part of the GENERIC kernel, and any related support tools > will have to exist as separate binaries (newfs.jfs, fsck.jfs), as is > currently done with the EXT2FS filesystem. >=20 > -- > Matt Emmerton >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwVO20ACgkQ+rDjkNht5F0fugCgl29dASt76wPngq55mf3oot6C JKAAn05p9X6kWVr0xe3TNNlWPjt0vS1F =fA5I -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 15: 7: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from parhelion.firedrake.org (parhelion.firedrake.org [212.135.138.219]) by hub.freebsd.org (Postfix) with ESMTP id E720937B416 for ; Mon, 10 Dec 2001 15:06:57 -0800 (PST) Received: from float by parhelion.firedrake.org with local (Exim 3.32 #1 (Debian)) id 16DZVW-0004vB-00; Mon, 10 Dec 2001 23:06:46 +0000 Date: Mon, 10 Dec 2001 23:06:46 +0000 To: Nick Rogness Cc: Lars Eggert , rick norman , freebsd-hackers@FreeBSD.ORG Subject: Re: Nat through two DSL Message-ID: <20011210230646.A17926@parhelion.firedrake.org> Mail-Followup-To: Nick Rogness , Lars Eggert , rick norman , freebsd-hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i From: void Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Dec 07, 2001 at 02:38:04PM -0600, Nick Rogness wrote: > > Damn it, fat fingered it...corrections to firewall: > > > ipfw add 500 divert natd1 ip from $NET to 0.0.0.0/1 out via $DSL_INT#1 > ipfw add 550 divert natd1 ip from 0.0.0.0/1 to any in via $DSL_INT#1 > ipfw add 560 fwd $DSL-2 ip from $NET to 128.0.0.0/1 out via $DSL_INT#1 > ipfw add 570 divert natd2 ip from any to any via $DSL_INT#2 IMHO, you're better off using the last bit in the IP address than the first bit. It's much more random. -- Ben "An art scene of delight I created this to be ..." -- Sun Ra To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 15:26:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21103.mail.yahoo.com (web21103.mail.yahoo.com [216.136.227.105]) by hub.freebsd.org (Postfix) with SMTP id 5782D37B417 for ; Mon, 10 Dec 2001 15:26:39 -0800 (PST) Message-ID: <20011210232635.46609.qmail@web21103.mail.yahoo.com> Received: from [62.254.0.5] by web21103.mail.yahoo.com via HTTP; Mon, 10 Dec 2001 15:26:35 PST Date: Mon, 10 Dec 2001 15:26:35 -0800 (PST) From: Hiten Pandya Subject: Re: [SUGGESTION] - JFS for FreeBSD To: hackers@FreeBSD.org In-Reply-To: <20011210225452.65655.qmail@web21102.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, the license issues dont really affect us... after all we have an src/gnu directory... thats what it is for... dumping GPL'ed stuff.... and talking about GPL, we can even publish the code as the GPL license states... after all we are an open Source Project, but if we were commercial... it would have affected us.. but thats not the case... the only other thing is, i am itermediatory C programmer and i have never ported a filesystem before. but.. that doesn't affect me a lot.. its experience which i will gain... After all the whole of the FreeBSD Team is on my back, so there is nothing to worry about... have already turned the Source code tree for JFS into DoxyGen Generated Pages... i have started to look into it... I am sure it is possible to port it to FreeBSD... though... it may be a bit trickier (not hard)... never say never :-) =Hiten = --- Alfred Perlstein wrote: > * Matthew Emmerton [011210 > 16:40] wrote: > > > * Hiten Pandya [011210 > 16:02] wrote: > > > > hi all, > > > > > > > > this is a wild idea...suggestion... > > > > > > > > i wanted to ask if there were any _plans_ to > port > > > > JFS (Journaled File System) to FreeBSD... > > > > > > > > as for JFS, it is developed by IBM for Linux > and > > > is licensed under GPL, so we could put this > into > > > > src/gnu/ > > > > > > > > It is used on IBM MainFrames and Enterprise > servers > > > > for > > > > high performance and maximum throughput... > > > > > > I'm glad you took the time to read the > marketting literature. > > > > > > The problem is that porting it is going to be a > bit more complicated > > > than just dumping it into src/gnu. > > > > > > Feel free to take a shot at porting it though, > let us know > > > when you're done. > > > > I'm gainfully employed by IBM (although not for > FreeBSD pursuits), and have > > had this on my TODO list for a while. > > > > The licence issue is a real sticky point, > especially since the GPL and BSD > > licences are like oil and water. Because of the > GPL licence, JFS support > > can never become part of the GENERIC kernel, and > any related support tools > > will have to exist as separate binaries > (newfs.jfs, fsck.jfs), as is > > currently done with the EXT2FS filesystem. > > This is pretty much how they all work, on netbsd the > LFS filesystem > has its own suite of seperate utilities as well. > Don't be discouraged, > get hacking! :) ===== -Hiten, Thank You, Yours Sincerely, Hiten Pandya, ===== -Hiten, Thank You, Yours Sincerely, Hiten Pandya, __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 15:32:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from breg.mc.mpls.visi.com (breg.mc.mpls.visi.com [208.42.156.101]) by hub.freebsd.org (Postfix) with ESMTP id 6ED0037B417; Mon, 10 Dec 2001 15:32:08 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by breg.mc.mpls.visi.com (Postfix) with ESMTP id 62DDE2D0693; Mon, 10 Dec 2001 17:32:07 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBANW6g02097; Mon, 10 Dec 2001 17:32:06 -0600 (CST) (envelope-from hawkeyd) Date: Mon, 10 Dec 2001 17:32:06 -0600 From: D J Hawkey Jr To: Robert Watson Cc: Michael Lucas , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011210173206.A1795@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011210155924.A1542@sheol.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.ORG on Mon, Dec 10, 2001 at 05:21:10PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Dec 10, at 05:21 PM, Robert Watson wrote: > > On Mon, 10 Dec 2001, D J Hawkey Jr wrote: > > > So, my question is then, just what is the policy defining > > non-current-but- still-supported-releases? > > > > [SNIP] > > It depends on the level of work required, I expect. Right now, we're > actively supporting 4.3-RELEASE and 4.4-RELEASE. Once we get to a point > where the cost is greater than can be handled by our all-volunteer staff, > we'll cut back. Currently, my hope is that we can keep supporting all > branches of 4.x-RELEASE through to 5.0-RELEASE next year. If we try to > avoid doing too many releases, that will be easier :-). Don't get me wrong - I don't expect the same level of support from the FreeBSD Project than I would from, say, Sybase or Sun. Having said that, I think FreeBSD's is outstanding, even compared to some other commercial *cough*Microsquish(tm)*cough* entities. > > This comes 'round to one of my original questions, too: Why, as an > > example, isn't the DELACK patches Matt made recently considered > > "important" enough to be backported to RELENG_4_3 (which I have more > > generically referred to as RELENG_(current - 1) or RELENG_(release - > > 1))? > > > > [SNIP] > > > > Yes, I know this would mean additional work on the part of the hacker > > and committer ... > > > > [SNIP] > > The quick answer is: because the security-officer team is using the > RELENG_4_x branches to generate binary updates, and has extremely limited > resources. As such, the only things being merged onto the branch are > security fixes. If the release engineering team is willing to take over > the task of generating binary updates, and wants to broaden the scope of > the branch, then such a proposal might make more sense. > > The goal of creating the branches was to permit version control to be > applied to a series of updates that were previously being managed by hand: > security patches ... While I'm sympathetic to the cause of "we want a > -NOT-AS-AGRESSIVE-AS-STABLE-BUT-NOT-JUST-SECURITY-FIXES", I think our > resources are already spread too thin to support that. If we were to move > to a model where the branch was maintained by re@, who generated binary > updates based on commits to the branch, and managed the QA process, > looking at a broader scope of potential commits might be feasible. > > [SNIP] I understand. I also understand that my questions and suggestions have the benefit of 20/20 hindsight. > > The site Michael and I have discussed will be hugely deficient in terms > > of what can be made available to any previous release (compared to what > > is applied to -STABLE), but as it sits right now, it would be better > > than nought for those that can't stay -STABLE. > > I think in practice you'll find what is needed is the ability to do local > revision management in the form of branches. > > [SNIP] My current plans are to have several patchfiles, grouped by subject (bugfix and/or enhancement), and subordinately grouped by FreeBSD release: ich_sound-patch-4.2REL.udiff delayed_ack-patch-4.2REL.udiff ich_sound-patch-4.3REL.udiff delayed_ack-patch-4.3REL.udiff ich_sound-patch-4.3STA.udiff agp_for_xf86-patch-4.2REL.udiff You get the idea. It will be all over the web page(s) that the patches are very narrowly targetted, and will list all the usual paranoia steps that should be taken for a decent fallback position should something fail. I have no intention of trying to emulate the FreeBSD model - not that it's not worth emulating, but rather, I simply don't have the resources. Unless it proves overwhelming, I do plan on offering my help in applying patches to the newbie/clueless. or to already hacked sources. Finally, it will be perfectly clear on the web page(s) that what is presented is not endorsed or supported by The Project, blah-blah-woof-woof. > left with a heavy burden, however: QA. Part of the currently goal of > RELENG_4_x is that each change be extensively tested, and usable by a wide > audience with low levels of concern about picking up potentially > conflicting changes. Most of the changes are very small, and as such have > a higher probability of correctness. Well, I can't provide that level of QA, of course. I can and do run systems with these patches in place, and I pick my targets carefully. I'm not about to backport something like DIRPREFs, but things more discreet/isolated, like ICH sound and delayed ACKs, I can wrap my arms around with fair confidence that I won't muck up something else. C is no stranger to me, and I've hacked/patched a lot of source. I still maintain an X WM that's over ten years old now. Hacking FreeBSD offers one advantage over that - cross-platform compatability isn't an issue! > Broadening the charter for the > release branch would mean expanding the QA process. And, had the Core 20/20 foresight, it might well have chosen that path, no? Granted, any one patch (and therefore, release) might well take longer to complete, but continued previous-release support would be more do-able. Hey, I'm not taking _anything_ away from y'all; I think all the BSDs are outstanding products. I'm just gonna see if I can't fulfill what I percieve as a support deficiency (again, from my own perspective) in my own little way. > Robert N M Watson FreeBSD Core Team, TrustedBSD Project Dave PS, I'm rather honored that such an illustrious group has shown interest enough to even discuss all this with me. -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 16:10:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id C31CE37B41B; Mon, 10 Dec 2001 16:09:57 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fBB08Ui11931; Mon, 10 Dec 2001 19:08:30 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 10 Dec 2001 19:08:30 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: D J Hawkey Jr Cc: Michael Lucas , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux In-Reply-To: <20011210173206.A1795@sheol.localdomain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 10 Dec 2001, D J Hawkey Jr wrote: > Don't get me wrong - I don't expect the same level of support from the > FreeBSD Project than I would from, say, Sybase or Sun. Having said that, > I think FreeBSD's is outstanding, even compared to some other commercial > *cough*Microsquish(tm)*cough* entities. Sounds good to me :-). > My current plans are to have several patchfiles, grouped by subject > (bugfix and/or enhancement), and subordinately grouped by FreeBSD > release: > > ich_sound-patch-4.2REL.udiff delayed_ack-patch-4.2REL.udiff > ich_sound-patch-4.3REL.udiff delayed_ack-patch-4.3REL.udiff > ich_sound-patch-4.3STA.udiff agp_for_xf86-patch-4.2REL.udiff > > You get the idea. It will be all over the web page(s) that the patches > are very narrowly targetted, and will list all the usual paranoia steps > that should be taken for a decent fallback position should something > fail. I have no intention of trying to emulate the FreeBSD model - not > that it's not worth emulating, but rather, I simply don't have the > resources. > > Unless it proves overwhelming, I do plan on offering my help in applying > patches to the newbie/clueless. or to already hacked sources. > > Finally, it will be perfectly clear on the web page(s) that what is > presented is not endorsed or supported by The Project, > blah-blah-woof-woof. Small patches for things like the delayed ack should be no problem. Unfortunately, many of the features I've been interested in back-porting in the past have been big features. That's why my boxes are about split between 4.4-RELEASEpXXX and 4.4-STABLE. > > Broadening the charter for the > > release branch would mean expanding the QA process. > > And, had the Core 20/20 foresight, it might well have chosen that path, > no? Granted, any one patch (and therefore, release) might well take > longer to complete, but continued previous-release support would be more > do-able. In terms of investing resources in QA, I'd rather put those resources into making sure new releases were good, and that the upgrade process was clean so that people could get to the next release easily. As we spin up for 4.5-RELEASE, any insight into that process would be much appreciated -- there's a freebsd-qa mailing list if you're interested (and not already subscribed). > Hey, I'm not taking _anything_ away from y'all; I think all the BSDs are > outstanding products. I'm just gonna see if I can't fulfill what I > percieve as a support deficiency (again, from my own perspective) in my > own little way. I don't mean to discourage you either -- rather, to explain why we haven't done some of the things you're looking at in the past. And if you manage to do it with resounding success, I certainly plan to encourage you to keep doing it. -STABLE has become a widely-supported tradition, and if there are people interested in helping make continuing support for releases easier, it could no doubt become a similarly widely-supported tradition. > PS, I'm rather honored that such an illustrious group has shown interest > enough to even discuss all this with me. Hey, I tend to think of us more as victims than illustrious. The FreeBSD core team is currently an elected body, and the members had to nominate themselves for election. That might put them in the category of "witting victims", to be contrasted with "unwitting victims", who are normally accorded some additional leniency in judgement. I think you'll also find that there's not much difference between core team members and normal FreeBSD developers. :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 16:26:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id 8434537B417; Mon, 10 Dec 2001 16:26:19 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id 2D204786E6; Tue, 11 Dec 2001 10:56:17 +1030 (CST) Date: Tue, 11 Dec 2001 10:56:17 +1030 From: Greg Lehey To: Hiten Pandya , Matthew Emmerton , Anthony Schneider Cc: current@FreeBSD.org, hackers@FreeBSD.org, Alfred Perlstein Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011211105617.K63585@monorchid.lemis.com> References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> <20011210174711.A3208@mail.slc.edu> <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> <20011210220153.50612.qmail@web21102.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011210174711.A3208@mail.slc.edu> <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> <20011210220153.50612.qmail@web21102.mail.yahoo.com> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] Long-short syndrome in first message. On Monday, 10 December 2001 at 14:01:53 -0800, Hiten Pandya wrote: > hi all, > > this is a wild idea...suggestion... > > i wanted to ask if there were any _plans_ to port > JFS (Journaled File System) to FreeBSD... > > as for JFS, it is developed by IBM for Linux and is licensed under > GPL, so we could put this into src/gnu/ Well, JFS was developed by IBM for AIX. If you look at the header files, it is clearly derived from UFS. They later developed a completely new file system, JFS2, for OS/2, and later ported this version to Linux. It's also available for AIX, but the standard AIX file system is still the old JFS1. > It is used on IBM MainFrames and Enterprise servers for high > performance and maximum throughput... I don't think the zSeries (System/390) runs JFS. As I said above, the RS/6000 uses a different JFS file system. On Monday, 10 December 2001 at 17:39:35 -0500, Matthew Emmerton wrote: >> * Hiten Pandya [011210 16:02] wrote: >>> hi all, >>> >>> this is a wild idea...suggestion... >>> >>> i wanted to ask if there were any _plans_ to port >>> JFS (Journaled File System) to FreeBSD... >>> >>> as for JFS, it is developed by IBM for Linux and >>> is licensed under GPL, so we could put this into >>> src/gnu/ >>> >>> It is used on IBM MainFrames and Enterprise servers >>> for >>> high performance and maximum throughput... >> >> I'm glad you took the time to read the marketting literature. >> >> The problem is that porting it is going to be a bit more complicated >> than just dumping it into src/gnu. >> >> Feel free to take a shot at porting it though, let us know >> when you're done. > > I'm gainfully employed by IBM (although not for FreeBSD pursuits), > and have had this on my TODO list for a while. Well, I'm gainfully employed by IBM, both for FreeBSD and JFS. I've thought (and spoken) about this from time to time. It would be a lot of work. > The licence issue is a real sticky point, especially since the GPL > and BSD licences are like oil and water. Because of the GPL > licence, JFS support can never become part of the GENERIC kernel, > and any related support tools will have to exist as separate > binaries (newfs.jfs, fsck.jfs), as is currently done with the EXT2FS > filesystem. As others have pointed out, this is a detail. The real question is: will JFS2 buy anything? The only real way to find out is to try it. On Monday, 10 December 2001 at 17:47:11 -0500, Anthony Schneider wrote: > I'm no expert on journaled filesystems, but isn't the freebsd softupdates > option similar? No, at least not from a technical standpoint. From a user standpoint, they both try to make things faster and more reliable, but they do it in very different ways. > perhaps there could be an upgrade to offer > options SOFTERUPDATES > as an equal-but-different alternative to jfs? And what would that do? Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 16:28:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id B4AB737B405; Mon, 10 Dec 2001 16:28:16 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id 16F3C786E3; Tue, 11 Dec 2001 10:58:15 +1030 (CST) Date: Tue, 11 Dec 2001 10:58:15 +1030 From: Greg Lehey To: Hiten Pandya , Matthew Emmerton , Anthony Schneider Cc: current@FreeBSD.org, hackers@FreeBSD.org, Alfred Perlstein Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011211105815.L63585@monorchid.lemis.com> References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> <20011210174711.A3208@mail.slc.edu> <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011211105617.K63585@monorchid.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011211105617.K63585@monorchid.lemis.com> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday, 11 December 2001 at 10:56:17 +1030, Greg Lehey wrote: > On Monday, 10 December 2001 at 17:39:35 -0500, Matthew Emmerton wrote: >>> * Hiten Pandya [011210 16:02] wrote: >>>> hi all, >>>> >>>> this is a wild idea...suggestion... >>>> >>>> i wanted to ask if there were any _plans_ to port >>>> JFS (Journaled File System) to FreeBSD... >>>> >>>> as for JFS, it is developed by IBM for Linux and >>>> is licensed under GPL, so we could put this into >>>> src/gnu/ >>>> >>>> It is used on IBM MainFrames and Enterprise servers >>>> for >>>> high performance and maximum throughput... >>> >>> I'm glad you took the time to read the marketting literature. >>> >>> The problem is that porting it is going to be a bit more complicated >>> than just dumping it into src/gnu. >>> >>> Feel free to take a shot at porting it though, let us know >>> when you're done. >> >> I'm gainfully employed by IBM (although not for FreeBSD pursuits), >> and have had this on my TODO list for a while. > > Well, I'm gainfully employed by IBM, both for FreeBSD and JFS. I've > thought (and spoken) about this from time to time. It would be a lot > of work. BTW, if anybody wants to do it anyway, let me know. I'm in a position to help with information, though possibly not with coding. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 16:35:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-d.strhg1.mi.home.com [24.13.43.207]) by hub.freebsd.org (Postfix) with ESMTP id 28F0937B416; Mon, 10 Dec 2001 16:35:35 -0800 (PST) Received: by turtle.looksharp.net (Postfix, from userid 1003) id 93CA23EB7; Mon, 10 Dec 2001 19:36:01 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by turtle.looksharp.net (Postfix) with ESMTP id 85FAFBAA5; Mon, 10 Dec 2001 19:36:01 -0500 (EST) Date: Mon, 10 Dec 2001 19:36:01 -0500 (EST) From: "Brandon D. Valentine" To: Greg Lehey Cc: Hiten Pandya , Matthew Emmerton , Anthony Schneider , , , Alfred Perlstein Subject: Re: [SUGGESTION] - JFS for FreeBSD In-Reply-To: <20011211105617.K63585@monorchid.lemis.com> Message-ID: <20011210192952.C34440-100000@turtle.looksharp.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 11 Dec 2001, Greg Lehey wrote: >On Monday, 10 December 2001 at 17:47:11 -0500, Anthony Schneider wrote: >> perhaps there could be an upgrade to offer >> options SOFTERUPDATES >> as an equal-but-different alternative to jfs? > >And what would that do? SOFTERUPDATES includes a switch to diffused gallery lighting and enhanced mood music. For the hacker in touch with his feminine side, it offers the ultimate in warm fuzzies. Brandon D. Valentine -- "Iam mens praetrepidans avet vagari." - G. Valerius Catullus, Carmina, XLVI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 16:59:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from science.slc.edu (Science.SLC.Edu [198.83.6.248]) by hub.freebsd.org (Postfix) with ESMTP id 90B0637B405; Mon, 10 Dec 2001 16:59:07 -0800 (PST) Received: (from aschneid@localhost) by science.slc.edu (8.11.0/8.11.0) id fBB0vPg04755; Mon, 10 Dec 2001 19:57:25 -0500 (EST) (envelope-from aschneid) Date: Mon, 10 Dec 2001 19:57:25 -0500 From: Anthony Schneider To: Greg Lehey Cc: Hiten Pandya , Matthew Emmerton , current@FreeBSD.ORG, hackers@FreeBSD.ORG, Alfred Perlstein Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011210195725.A4697@mail.slc.edu> References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> <20011210174711.A3208@mail.slc.edu> <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210174711.A3208@mail.slc.edu> <20011211105617.K63585@monorchid.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211105617.K63585@monorchid.lemis.com>; from grog@FreeBSD.ORG on Tue, Dec 11, 2001 at 10:56:17AM +1030 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > On Monday, 10 December 2001 at 17:47:11 -0500, Anthony Schneider wrote: > > I'm no expert on journaled filesystems, but isn't the freebsd softupdat= es > > option similar? >=20 > No, at least not from a technical standpoint. From a user standpoint, > they both try to make things faster and more reliable, but they do it > in very different ways. >=20 Well, perhaps I should have made that clearer: I am not an expert on either journaled filesystems not am I an expert on FreeBSD's softupdates option, technically or other. > > perhaps there could be an upgrade to offer > > options SOFTERUPDATES > > as an equal-but-different alternative to jfs? >=20 > And what would that do? My thoughts were that if the two were similar in effect that it might be a relatively easy project to escalate towards achieving the same effects in one as the other. I understand that this is not necessarily the case. =20 > Greg -Anthony. --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwVWfEACgkQ+rDjkNht5F0tMQCfUGJdUfJ/VY4jz32OQc6zQYvq cEoAnRR/wlk0W2XKsd7zBYTwUjYx26tl =YSPd -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 18:30:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id 3F41A37B417 for ; Mon, 10 Dec 2001 18:30:05 -0800 (PST) Received: from ubik.demon.co.uk ([194.222.125.229]) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 16DcgF-000BZc-0B for freebsd-hackers@freebsd.org; Tue, 11 Dec 2001 02:30:04 +0000 Message-ID: <7UAeNSA2SWF8Iwe5@ubik.demon.co.uk> Date: Tue, 11 Dec 2001 01:43:18 +0000 To: freebsd-hackers@freebsd.org From: Tony Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> <20011210174711.A3208@mail.slc.edu> <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210174711.A3208@mail.slc.edu> <20011211105617.K63585@monorchid.lemis.com> <20011210195725.A4697@mail.slc.edu> In-Reply-To: <20011210195725.A4697@mail.slc.edu> MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 5.01 U Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20011210195725.A4697@mail.slc.edu>, Anthony Schneider writes >> > perhaps there could be an upgrade to offer >> > options SOFTERUPDATES >> > as an equal-but-different alternative to jfs? >> >> And what would that do? > >My thoughts were that if the two were similar in effect that it might be >a relatively easy project to escalate towards achieving the same effects >in one as the other. I understand that this is not necessarily the case. The philosophies in designing the file systems were quite different. At the abstract these are efficiency versus reliability. The philosophy behind a file system not only guides the structure of code it also shapes the structures on disk. A transaction based or journal file system will, for example, appear to grow a database file by whole valid records. If the change is interrupted and the system is restarted the file will either be on the state it was in before the change or in the state afterwards. The usual efficiency oriented file systems can be interrupted at intermediate points: extra disk space is marked as allocated, disk space is assigned to file, file write has happened but the file length has not been updated (or vice versa). Most current users will probably not like the speed penalties of a journal file system, and stick to the faster FS. On the other hand a solid journal FS may encourage more take up for back end databases, for e-commerce, data warehousing, etc... Tony -- "One needs literature in one's life, because without it one deteriorates." - Nelson Mandela To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 18:49:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mars-gw.morning.ru (ns.morning.ru [195.161.98.5]) by hub.freebsd.org (Postfix) with ESMTP id 7BF6437B405; Mon, 10 Dec 2001 18:49:11 -0800 (PST) Received: from NDNM ([195.161.98.250]) by mars-gw.morning.ru (8.11.5/8.11.5) with ESMTP id fBB2mu682382; Tue, 11 Dec 2001 09:48:57 +0700 (KRAT) Date: Tue, 11 Dec 2001 09:53:53 +0700 From: Igor M Podlesny X-Mailer: The Bat! (v1.53d) Business Organization: Morning Network X-Priority: 3 (Normal) Message-ID: <123313439001.20011211095353@morning.ru> To: Terry Lambert Cc: Peter Pentchev , Dima Dorfman , chris@FreeBSD.ORG, Subject: Re[2]: jail.c.patch (allowing to use hostnames when invoking jail(8)) In-Reply-To: <3C14C135.CB9099AD@mindspring.com> References: <20011209205442.C8D0A3E2F@bazooka.trit.org> <3C141F9E.D7681BCC@mindspring.com> <20011210124049.G757@straylight.oblivion.bg> <3C14C135.CB9099AD@mindspring.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Peter Pentchev wrote: >> > This is why the inte_aton() call is still necessary. >> [snip] >> > Please call inet_aton(), and then _only_ if that fails, call the >> > gethostbyname(). >> >> How about inet_pton() and getnameinfo()? > You know, I first thought of this, but then I backed off it. > The problem is that the addres is passed in as a 32 bit int, not > as the address of a sockaddr_in. I think it would take a lot of > work to make the jail code IPv6-safe. You'd have to talk to Poul > for details, but it's pretty clear that the "splitting" of the > virtual address aliases per jail on the interface(s) in question > is very IPv4 specific, right now. > -- Terry There's one thing I can't get... we're talking about to use or not to use just one more system call in an "userland"-program which results to the minimal code size increment and affects nothing else. Look at ipfw.c (userland also) men... That's the place to optimize and re-write everything from scratch. And jail.c is just small wrapper for system call. It doesn't worth all these time we've already spent discussing to call or not to call just one more function. This is my own humble (or not too) opinion. -- Igor mailto:poige@morning.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 20:14:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts20-srv.bellnexxia.net (tomts20.bellnexxia.net [209.226.175.74]) by hub.freebsd.org (Postfix) with ESMTP id DEF8A37B419 for ; Mon, 10 Dec 2001 20:14:13 -0800 (PST) Received: from xena.gsicomp.on.ca ([199.243.149.34]) by tomts20-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20011211041412.GBJE975.tomts20-srv.bellnexxia.net@xena.gsicomp.on.ca>; Mon, 10 Dec 2001 23:14:12 -0500 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.1) with SMTP id fBB45xW02997; Mon, 10 Dec 2001 23:06:00 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <00a301c181fa$4764a5b0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: , "Tony" References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> <20011210174711.A3208@mail.slc.edu> <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <002601c181cb$8c6a5e90$1200a8c0@gsicomp.on.ca> <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210174711.A3208@mail.slc.edu> <20011211105617.K63585@monorchid.lemis.com> <20011210195725.A4697@mail.slc.edu> <7UAeNSA2SWF8Iwe5@ubik.demon.co.uk> Subject: Re: [SUGGESTION] - JFS for FreeBSD Date: Mon, 10 Dec 2001 23:14:06 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Most current users will probably not like the speed penalties of a > journal file system, and stick to the faster FS. On the other hand a > solid journal FS may encourage more take up for back end databases, for > e-commerce, data warehousing, etc... The transaction support of JFS isn't really viable for large-scale database implementations because it imposes a real speed penalty. Most large-scale DB2 or Oracle installations use raw disk, and let the transaction support in the database keep everything sane. The real benefit of JFS (or any other journaling FS) is to provide a transactional guarantees for everyday disk activites. The best example I can think of is a large multi-user UNIX box in a programming environment, with multiple CVS trees, local working copies of code, and lots and lots of updates (compiles, checkouts, search-and-replace, etc.) It is in this kind of environment that you want the assurance that any update will either pass or fail -- nothing in between to cause corruption that could potentiall remain undetected and eventually snowball into an unusuable filesystem. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 20:22:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 79CA337B405; Mon, 10 Dec 2001 20:22:28 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBB4MMp50524; Mon, 10 Dec 2001 20:22:22 -0800 (PST) (envelope-from dillon) Date: Mon, 10 Dec 2001 20:22:22 -0800 (PST) From: Matthew Dillon Message-Id: <200112110422.fBB4MMp50524@apollo.backplane.com> To: D J Hawkey Jr Cc: Robert Watson , Michael Lucas , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux References: <20011210155924.A1542@sheol.localdomain> <20011210173206.A1795@sheol.localdomain> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :Dave : :PS, I'm rather honored that such an illustrious group has shown interest :enough to even discuss all this with me. Ha! Just wait until witness one of the many flame wars. First we put two people in the ring and one gets thrown to the lions, then everyone else jumps into the ring and throws the other guy to the lions, then the lions get LOOSE and blood and guts wind up splattered all over the place. And THEN everyone picks their virtual guts off the floor and start the whole thing all over again :-) -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 20:36: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brea.mc.mpls.visi.com (brea.mc.mpls.visi.com [208.42.156.100]) by hub.freebsd.org (Postfix) with ESMTP id E29FF37B419; Mon, 10 Dec 2001 20:36:00 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by brea.mc.mpls.visi.com (Postfix) with ESMTP id E82792DDB12; Mon, 10 Dec 2001 22:35:59 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBB4Zx303480; Mon, 10 Dec 2001 22:35:59 -0600 (CST) (envelope-from hawkeyd) Date: Mon, 10 Dec 2001 22:35:59 -0600 From: D J Hawkey Jr To: Matthew Dillon Cc: Robert Watson , Michael Lucas , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011210223559.A3465@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011210155924.A1542@sheol.localdomain> <20011210173206.A1795@sheol.localdomain> <200112110422.fBB4MMp50524@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112110422.fBB4MMp50524@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Dec 10, 2001 at 08:22:22PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Dec 10, at 08:22 PM, Matthew Dillon wrote: > > : > :Dave > : > :PS, I'm rather honored that such an illustrious group has shown interest > :enough to even discuss all this with me. > > Ha! Just wait until witness one of the many flame wars. First we > put two people in the ring and one gets thrown to the lions, then > everyone else jumps into the ring and throws the other guy to the lions, > then the lions get LOOSE and blood and guts wind up splattered all over > the place. And THEN everyone picks their virtual guts off the floor and > start the whole thing all over again :-) HAAA-HAA-Ha-ha-aaa. Hey, every family has their squabbles. Heck, our family doesn't even need the lions. In fact, they run to the basement, tails slung low, and hide! > -Matt Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 21:33:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.acns.ab.ca (h24-64-56-135.cg.shawcable.net [24.64.56.135]) by hub.freebsd.org (Postfix) with ESMTP id C98A037B417 for ; Mon, 10 Dec 2001 21:33:32 -0800 (PST) Received: from colnta.acns.ab.ca (colnta.acns.ab.ca [192.168.1.2]) by mail.acns.ab.ca (8.11.6/8.11.3) with ESMTP id fBB5XWS00956 for ; Mon, 10 Dec 2001 22:33:32 -0700 (MST) (envelope-from davidc@colnta.acns.ab.ca) Received: (from davidc@localhost) by colnta.acns.ab.ca (8.11.6/8.11.3) id fBB5XWM00540 for hackers@freebsd.org; Mon, 10 Dec 2001 22:33:32 -0700 (MST) (envelope-from davidc) Date: Mon, 10 Dec 2001 22:33:32 -0700 From: Chad David To: hackers@freebsd.org Subject: SMP beeping Message-ID: <20011210223332.A528@colnta.acns.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I sent a message about this to -stable last week, but didn't get any input that resulted in a solution to this problem so... -stable for the last week or more (I did a make world last week for the first time in over a month) beeps on and off when SMP is enabled. The beeping appears to be timed with very short stalls of the system; that is, when moving the mouse across the screen it stops at what seems to be that start of each beep. The beeps are not consistent in length, but the tone does not change. If I boot a kernel with the exact same config only with SMP disabled it does not beep, and mouse cursor movement is fluid. The machine is a dual 1Ghz PIII with 1G memory. As I have no clue about how to debug this I would appreciate any hints at all. The machine had been running fine for about six months so I do not "think" it is hardware. -- Chad David davidc@acns.ab.ca ACNS Inc. Calgary, Alberta Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 22:29:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 3BCD037B405; Mon, 10 Dec 2001 22:29:38 -0800 (PST) Received: from pool0031.cvx40-bradley.dialup.earthlink.net ([216.244.42.31] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16DgQ5-0001LT-00; Mon, 10 Dec 2001 22:29:37 -0800 Message-ID: <3C15A7D9.236B2E4E@mindspring.com> Date: Mon, 10 Dec 2001 22:29:45 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Danny Braniss , freebsd-hackers@FreeBSD.ORG Subject: Re: irq References: <200112101752.fBAHqMV01179@mass.dis.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Smith wrote: > Er, you don't seem to understand how PCI interrupts work. > > You must (for now) pass RF_SHAREABLE in; eventually the PCI code will > stick it there for you anyway. All PCI interrupts are shareable; you > can't "ask" for an unshared vector; you get the one you're given, and you > should be thankful for that much. Lots of people are going without these > days. 8( I've considered the issue of getting network cards onto their own IRQs, and then handling them on different CPUs, for some performance sensitive applications. It's a reasonable thing to want, though the current answer is "you get what you are assigned, and if you want something else, then move the cards around until you are happy". -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 22:37:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 147D837B416; Mon, 10 Dec 2001 22:37:52 -0800 (PST) Received: from pool0031.cvx40-bradley.dialup.earthlink.net ([216.244.42.31] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16DgXw-00070Q-00; Mon, 10 Dec 2001 22:37:44 -0800 Message-ID: <3C15A9C0.4E2901C3@mindspring.com> Date: Mon, 10 Dec 2001 22:37:52 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bernd Walter Cc: Danny Braniss , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: irq References: <200112101752.fBAHqMV01179@mass.dis.org> <20011210215905.E11774@cicely8.cicely.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bernd Walter wrote: > A PCI slot has 4 irq lines named INTA to INTD. Yes. > On PCs all slots share the same 4 physical irqs and the lines are > hardwired on the board in alternating order to each slot. On newer motherboards, post the Intel SErver Products Division PCI motherboards, from a year or so after initial release. > If you want cards not to share irqs you have to swap slots until you > get what you want - you can't enforce it with software. You can do it in software, but we don't, so moving the cards around is a valid workaround. PS: Slot 5, if there is one, is generally INT A, as well. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 22:45:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 43AF637B405; Mon, 10 Dec 2001 22:45:15 -0800 (PST) Received: from pool0031.cvx40-bradley.dialup.earthlink.net ([216.244.42.31] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16DgfC-00047P-00; Mon, 10 Dec 2001 22:45:14 -0800 Message-ID: <3C15AB82.FDF598A8@mindspring.com> Date: Mon, 10 Dec 2001 22:45:22 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Hiten Pandya Cc: current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hiten Pandya wrote: > i wanted to ask if there were any _plans_ to port > JFS (Journaled File System) to FreeBSD... Not unless you have plans. When I was an IBM employee, they would not change the license, and so it's impossible to ship a CDROM where it's the boot FS, or boxes on which it is the boot FS, and still have it be legal, because of the license conflicts. I fought this for about a year within IBM, before I gave up. > It is used on IBM MainFrames and Enterprise servers > for high performance and maximum throughput... No, it's not. The Linux JFS is derived from the OS/2 JFS code, not the good AIX JFS code. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 22:48:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 53E6537B405 for ; Mon, 10 Dec 2001 22:48:52 -0800 (PST) Received: from pool0031.cvx40-bradley.dialup.earthlink.net ([216.244.42.31] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Dgig-0006W3-00; Mon, 10 Dec 2001 22:48:50 -0800 Message-ID: <3C15AC5A.44BFD2BD@mindspring.com> Date: Mon, 10 Dec 2001 22:48:58 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Hiten Pandya , hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein wrote: [ ... Hiten wants someone to GPLify FreeBSD ... ] > I'm glad you took the time to read the marketting literature. > > The problem is that porting it is going to be a bit more complicated > than just dumping it into src/gnu. > > Feel free to take a shot at porting it though, let us know > when you're done. FS porting to FreeBSD is actually pretty trivial(*), though some transactioning changes to the FreeBSD VFS layer consumers (the system calls and NFS server code) would be necessary to make the journal roll-back function correctly, following a failure. (*) Trivial: meaning grunt work is required; not necessarily an indicator of the amount of work, only the intellectual effort required for the job -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 22:51:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 00C8237B405 for ; Mon, 10 Dec 2001 22:51:10 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 7298D81D03; Tue, 11 Dec 2001 00:51:04 -0600 (CST) Date: Tue, 11 Dec 2001 00:51:04 -0600 From: Alfred Perlstein To: Terry Lambert Cc: Hiten Pandya , hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011211005104.U92148@elvis.mu.org> References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <3C15AC5A.44BFD2BD@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C15AC5A.44BFD2BD@mindspring.com>; from tlambert2@mindspring.com on Mon, Dec 10, 2001 at 10:48:58PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Terry Lambert [011211 00:48] wrote: > Alfred Perlstein wrote: > > [ ... Hiten wants someone to GPLify FreeBSD ... ] > > > I'm glad you took the time to read the marketting literature. > > > > The problem is that porting it is going to be a bit more complicated > > than just dumping it into src/gnu. > > > > Feel free to take a shot at porting it though, let us know > > when you're done. > > FS porting to FreeBSD is actually pretty trivial(*), though some > transactioning changes to the FreeBSD VFS layer consumers (the > system calls and NFS server code) would be necessary to make > the journal roll-back function correctly, following a failure. > > (*) Trivial: meaning grunt work is required; not necessarily an > indicator of the amount of work, only the intellectual effort > required for the job Terry, porting an FS is trivial, doing it right less so, but actually taking the time to do it, now that's another matter, considering I don't have any experience with JFS, porting it "just to find out" doesn't make it worth my while. Hence my encouragement of our enthusiastic friend. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 22:59:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id EDB3337B416 for ; Mon, 10 Dec 2001 22:59:29 -0800 (PST) Received: from pool0031.cvx40-bradley.dialup.earthlink.net ([216.244.42.31] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Dgsz-0005hZ-00; Mon, 10 Dec 2001 22:59:29 -0800 Message-ID: <3C15AED9.25414A39@mindspring.com> Date: Mon, 10 Dec 2001 22:59:37 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Hiten Pandya Cc: hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <20011210232635.46609.qmail@web21103.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hiten Pandya wrote: > the license issues dont really affect us... > after all we have an src/gnu directory... thats what > it is for... dumping GPL'ed stuff.... > > and talking about GPL, we can even publish the code > as the GPL license states... after all we are an > open Source Project, but if we were commercial... > > it would have affected us.. but thats not the > case... Please note: none of the code shipped in /usr/src/gnu is in the boot path. In other words, you can build a bootable FreeBSD system without it. For an FS that will be used as the root FS (/), this is not true. It is not legal for us to distribute CDROMS capable of installing a new FreeBSD system wit only JFS partitions, due to the license. You really should follow Alfreds advice, and go read the list archives, where this issue was discussed in detail, before. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 10 23:59: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id 65C5537B405; Mon, 10 Dec 2001 23:58:59 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id EB8C9786E6; Tue, 11 Dec 2001 18:28:56 +1030 (CST) Date: Tue, 11 Dec 2001 18:28:56 +1030 From: Greg Lehey To: Terry Lambert Cc: Hiten Pandya , current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011211182856.A67986@monorchid.lemis.com> References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <3C15AB82.FDF598A8@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C15AB82.FDF598A8@mindspring.com> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday, 10 December 2001 at 22:45:22 -0800, Terry Lambert wrote: > Hiten Pandya wrote: >> i wanted to ask if there were any _plans_ to port >> JFS (Journaled File System) to FreeBSD... > > Not unless you have plans. When I was an IBM employee, they would > not change the license, and so it's impossible to ship a CDROM > where it's the boot FS, or boxes on which it is the boot FS, and > still have it be legal, because of the license conflicts. > > I fought this for about a year within IBM, before I gave up. Since then, it has become possible for the loader to load modules before booting the kernel. This means that, theoretically, it would be possible to have a JFS root file system. Given the strong opposition to the GPL in some factions of the FreeBSD project, I don't see this happening any time soon, especially since we still don't know if it will buy us anything. >> It is used on IBM MainFrames and Enterprise servers >> for high performance and maximum throughput... > > No, it's not. The Linux JFS is derived from the OS/2 JFS code, not > the good AIX JFS code. That's correct, but note that AIX is moving to this code base too, so it's not as if it's second-rate. From what I've seen of the structures, JFS2 is *much* better than JFS1. I haven't compared performance. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 0: 0:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id EF2ED37B405 for ; Tue, 11 Dec 2001 00:00:02 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id 3DF5A786E9; Tue, 11 Dec 2001 18:30:01 +1030 (CST) Date: Tue, 11 Dec 2001 18:30:01 +1030 From: Greg Lehey To: Terry Lambert Cc: Alfred Perlstein , Hiten Pandya , hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011211183001.B67986@monorchid.lemis.com> References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <3C15AC5A.44BFD2BD@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C15AC5A.44BFD2BD@mindspring.com> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday, 10 December 2001 at 22:48:58 -0800, Terry Lambert wrote: > Alfred Perlstein wrote: > > [ ... Hiten wants someone to GPLify FreeBSD ... ] > >> I'm glad you took the time to read the marketting literature. >> >> The problem is that porting it is going to be a bit more complicated >> than just dumping it into src/gnu. >> >> Feel free to take a shot at porting it though, let us know >> when you're done. > > FS porting to FreeBSD is actually pretty trivial(*), though some > transactioning changes to the FreeBSD VFS layer consumers (the > system calls and NFS server code) would be necessary to make > the journal roll-back function correctly, following a failure. > > (*) Trivial: meaning grunt work is required; not necessarily an > indicator of the amount of work, only the intellectual effort > required for the job Considering that the current UFS implementation didn't need to be ported, and people are still working on the details, I think that this is a highly misleading statement. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 0:54:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id B8DE637B405; Tue, 11 Dec 2001 00:54:10 -0800 (PST) Received: from pool0063.cvx21-bradley.dialup.earthlink.net ([209.179.192.63] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Difs-0000WL-00; Tue, 11 Dec 2001 00:54:05 -0800 Message-ID: <3C15C9B4.C74F914@mindspring.com> Date: Tue, 11 Dec 2001 00:54:12 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: Hiten Pandya , current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <3C15AB82.FDF598A8@mindspring.com> <20011211182856.A67986@monorchid.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greg Lehey wrote: > Since then, it has become possible for the loader to load modules > before booting the kernel. This means that, theoretically, it would > be possible to have a JFS root file system. Given the strong > opposition to the GPL in some factions of the FreeBSD project, I don't > see this happening any time soon, especially since we still don't know > if it will buy us anything. ? OK, I load the kernel from the JFS. I mount the root FS, which is a JFS. I read the module "jfs.ko" from the JFS so that I can mount the root FS, which is a JFS, so I can read the module "jfs.ko" from the JFS so that I can mount the root FS, which is a JFS, so I can read the module "jfs.ko" from the JFS so that I can mount the root FS, which is a JFS, so I can... Do you see the problem yet? > >> It is used on IBM MainFrames and Enterprise servers > >> for high performance and maximum throughput... > > > > No, it's not. The Linux JFS is derived from the OS/2 JFS code, not > > the good AIX JFS code. > > That's correct, but note that AIX is moving to this code base too, so > it's not as if it's second-rate. From what I've seen of the > structures, JFS2 is *much* better than JFS1. I haven't compared > performance. None of the Web Connections RS/6000 machines ran this OS/2 derived code. I was under the impression that it was there for Linux compatability. My impression is, layout or not, the original JFS is much better code, overall. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 0:57: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id A936737B405; Tue, 11 Dec 2001 00:56:58 -0800 (PST) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.33 #1) id 16DiiW-0004ai-00; Tue, 11 Dec 2001 10:56:48 +0200 Received: from localhost ([127.0.0.1] helo=pampa.cs.huji.ac.il ident=danny) by pampa.cs.huji.ac.il with esmtp (Exim 3.22 #2) id 16DiiV-000AEf-00; Tue, 11 Dec 2001 10:56:47 +0200 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Terry Lambert Cc: Bernd Walter , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: irq In-Reply-To: Message from Terry Lambert of "Mon, 10 Dec 2001 22:37:52 PST." <3C15A9C0.4E2901C3@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Dec 2001 10:56:47 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG well, if it's not software it must be hardware problem (true or false ?) the test: video capture (using a modified meteor driver) doing full size 24bit colour, the meteor would complain about FIFO errors (which probably mean that the dma did not finish in time - correct?) and sometimes, the adaptec would also complain. so i moved cards around. 1st try: disaster, the adaptec realy complained, had to reboot. 2nd try: Success, fifo errors are down to less than .1% (before it used to be 90%). danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 1: 8:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id C86F737B405; Tue, 11 Dec 2001 01:08:16 -0800 (PST) Received: from pool0063.cvx21-bradley.dialup.earthlink.net ([209.179.192.63] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Ditb-0006ih-00; Tue, 11 Dec 2001 01:08:16 -0800 Message-ID: <3C15CD07.6D5FC2E7@mindspring.com> Date: Tue, 11 Dec 2001 01:08:23 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: Alfred Perlstein , Hiten Pandya , hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <3C15AC5A.44BFD2BD@mindspring.com> <20011211183001.B67986@monorchid.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greg Lehey wrote: > > FS porting to FreeBSD is actually pretty trivial(*), though some > > transactioning changes to the FreeBSD VFS layer consumers (the > > system calls and NFS server code) would be necessary to make > > the journal roll-back function correctly, following a failure. > > > > (*) Trivial: meaning grunt work is required; not necessarily an > > indicator of the amount of work, only the intellectual effort > > required for the job > > Considering that the current UFS implementation didn't need to be > ported, and people are still working on the details, I think that this > is a highly misleading statement. The current UFS has a number of issues which make it non-trivial; it was, in effect, a port; here is the short list: o Soft updates o Unified VM and buffer cache o Interface is still not entirely reflexive o VOP_READDIR restart via cookies, rather than seperate read/externalize VOPS, which would have avoided cookies o Gratuitous difference in cookie parameter order between FreeBSD and OpenBSD/NetBSD o "Default" VOPS considreably complicate stacking, which appears to be a goal nowm when it wasn't a goal before o New block size defaults (what happens to directories, which require atomicity and therefore use 512b blocks, is not explained in the 8K/1K case) o New directory acceleration code (dirhash; probably belongs in the directory name cache, not the FS) o NFS server code and system call code not treated as equal consumers of the VFS interface Live code always has issues, particularly if you are trying to pound a round peg into a square hole (hence Kirk taking up the task of a redesign). FWIW: I was a member of a very small team which ported the entire Heidemann framework, the UFS and FFS code of the time, and also implemented Soft Updates and Soft Read Only in 1996 or so. We had to port to the Windows 95 IFSMgr framework, add a second namespace, add Unicode support, deal with the 512b directory blocks growing to 1024b, while maintaining idempotence in the face of the loss of atomicity, etc.. Three people did almost all the work in about 5 months. The code is _not_ hard to get your head around. I think that everyone saying "Ut oh! SCARY!" gives people the wrong idea, and scares off potential contributors in these areas. Unlike most of the rest of the system, there are at least white papers available. I'd have to say the FS design was one of the better documented parts of FreeBSD, if you take the many McKusick, Heidemann, Ganager/Patt papers and articles into account. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 1:13: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 3252237B416; Tue, 11 Dec 2001 01:12:52 -0800 (PST) Received: from pool0063.cvx21-bradley.dialup.earthlink.net ([209.179.192.63] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Dixo-0003sf-00; Tue, 11 Dec 2001 01:12:36 -0800 Message-ID: <3C15CE0B.FA53281B@mindspring.com> Date: Tue, 11 Dec 2001 01:12:43 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Danny Braniss Cc: Bernd Walter , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: irq References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Danny Braniss wrote: > well, if it's not software it must be hardware problem (true or false ?) > the test: > video capture (using a modified meteor driver) > doing full size 24bit colour, the meteor would complain about FIFO errors > (which probably mean that the dma did not finish in time - correct?) > and sometimes, the adaptec would also complain. > > so i moved cards around. > > 1st try: disaster, the adaptec realy complained, had to reboot. > 2nd try: Success, fifo errors are down to less than .1% (before it > used to be 90%). It looks like IRQ sharing is the only issue here. I don't see this as a hardware problem, unless tou are complaining about the Meteor design (which I'd probably agree with). Sharing of IRQs is supposed to be possible, but if you have incredible bus on times and incredible "I caused this interrupt" register access latency, and are stacking captures into writes ont disk serviced at the same interrupt, well, then, you should expect problems. But I would still blame software (in particular, the firmware on your Meteor). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 1:15:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 4CB6337B416; Tue, 11 Dec 2001 01:14:41 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA11498; Tue, 11 Dec 2001 11:14:26 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h88.229.dialup.iptcom.net [212.9.229.88]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id LAA42169; Tue, 11 Dec 2001 11:14:23 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id fBB9DCF01541; Tue, 11 Dec 2001 11:13:12 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C15CED5.20D65BFE@FreeBSD.org> Date: Tue, 11 Dec 2001 11:16:05 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Terry Lambert Cc: Greg Lehey , Hiten Pandya , current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <3C15AB82.FDF598A8@mindspring.com> <20011211182856.A67986@monorchid.lemis.com> <3C15C9B4.C74F914@mindspring.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > > Greg Lehey wrote: > > Since then, it has become possible for the loader to load modules > > before booting the kernel. This means that, theoretically, it would > > be possible to have a JFS root file system. Given the strong > > opposition to the GPL in some factions of the FreeBSD project, I don't > > see this happening any time soon, especially since we still don't know > > if it will buy us anything. > > ? > > OK, I load the kernel from the JFS. I mount the root FS, which > is a JFS. I read the module "jfs.ko" from the JFS so that I can > mount the root FS, which is a JFS, so I can read the module "jfs.ko" > from the JFS so that I can mount the root FS, which is a JFS, so I > can read the module "jfs.ko" from the JFS so that I can mount the > root FS, which is a JFS, so I can... > > Do you see the problem yet? Libstand (and hence the loader) could be extended to allow reading files from jfs without using any GPL'ed code. For example our loader can load modules from the FAT even though we do not have any M$ code. :) Alternatively, /boot could be placed on separate filesystem, which could be ufs or anything else supported by the loader. -Maxim > > >> It is used on IBM MainFrames and Enterprise servers > > >> for high performance and maximum throughput... > > > > > > No, it's not. The Linux JFS is derived from the OS/2 JFS code, not > > > the good AIX JFS code. > > > > That's correct, but note that AIX is moving to this code base too, so > > it's not as if it's second-rate. From what I've seen of the > > structures, JFS2 is *much* better than JFS1. I haven't compared > > performance. > > None of the Web Connections RS/6000 machines ran this OS/2 derived > code. I was under the impression that it was there for Linux > compatability. My impression is, layout or not, the original JFS > is much better code, overall. > > -- Terry > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 1:35:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 642BC37B417; Tue, 11 Dec 2001 01:35:51 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011211093551.BEIG4213.rwcrmhc52.attbi.com@peter3.wemm.org>; Tue, 11 Dec 2001 09:35:51 +0000 Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id fBB9Zos37788; Tue, 11 Dec 2001 01:35:50 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id D4BF638CC; Tue, 11 Dec 2001 01:35:50 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Terry Lambert Cc: Greg Lehey , Hiten Pandya , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: [SUGGESTION] - JFS for FreeBSD In-Reply-To: <3C15C9B4.C74F914@mindspring.com> Date: Tue, 11 Dec 2001 01:35:50 -0800 From: Peter Wemm Message-Id: <20011211093550.D4BF638CC@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > Greg Lehey wrote: > > Since then, it has become possible for the loader to load modules > > before booting the kernel. This means that, theoretically, it would > > be possible to have a JFS root file system. Given the strong > > opposition to the GPL in some factions of the FreeBSD project, I don't > > see this happening any time soon, especially since we still don't know > > if it will buy us anything. > > ? > > OK, I load the kernel from the JFS. I mount the root FS, which > is a JFS. I read the module "jfs.ko" from the JFS so that I can > mount the root FS, which is a JFS, so I can read the module "jfs.ko" > from the JFS so that I can mount the root FS, which is a JFS, so I > can read the module "jfs.ko" from the JFS so that I can mount the > root FS, which is a JFS, so I can... > > Do you see the problem yet? It is not a problem. The *kernel* does not load jfs.ko, it is loader itself. There is no reason why a trivial non-gpl jfs reader couldn't be written for boot2 and loader if the need was great enough. Or have /boot as a seperate file system (eg: UFS or FAT32). We do this on IA64 where /boot is a FAT32 filesystem (not exactly, but close enough. I usually mount it on /efi and make /boot/ a symlink to /efi/boot so that in EFI we have a /boot as well). Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 2:19:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id D8A5837B417; Tue, 11 Dec 2001 02:19:06 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [fec0::1:12]) by Awfulhak.org (8.11.6/8.11.6) with ESMTP id fB6D78R18133; Thu, 6 Dec 2001 13:07:08 GMT (envelope-from brian@freebsd-services.com) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.6/8.11.6) with ESMTP id fB6D77E46932; Thu, 6 Dec 2001 13:07:07 GMT (envelope-from brian@freebsd-services.com) Message-Id: <200112061307.fB6D77E46932@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: James Housley Cc: Brian Somers , Greg Lane , freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org, brian@freebsd.org, Julian Elischer , brian@freebsd-services.com Subject: Re: [Fwd: Jul 30 changes to ppp break my Telstra ADSL PPPoE connection] In-Reply-To: Message from James Housley of "Wed, 05 Dec 2001 08:16:18 EST." <3C0E1E22.B685EC47@Thehousleys.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Dec 2001 13:07:07 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Brian Somers wrote: > > > > Hi, > > > > Thanks for your report. Would you be able to grab me logs of the > > connection that doesn't work (the latest ppp) and the one that works > > (the pre-July 30 one) with the following set: > > > > set log tun chat lcp ipcp > > > > It may be possible to fix the problem by changing your ``set mru'' > > and ``set mtu'' lines to > > > > set mru max 1454 > > set mtu max 1454 > > > > but, even if this is successful, I'd be interested in the logs. > > > > It may also be worth trying the latest version of ppp from my web > > site (http://www.Awfulak.org/~brian) - just in case it's something > > that I've already fixed but have forgotten to MFC. If that's the > > case, then I should be able to find the bogus code more easily. > > > > I am having great difficulty getting logs. I noticed the last time I had ppp log data was November 20th. But this is what I have. > > /etc/syslog.conf: > !ppp > *.* /var/log/ppp.log > > /var/log/ppp.log: > Dec 5 08:02:26 server ppp[198]: tun0: LCP: deflink: RecvEchoRequest(2) state = Opened > Dec 5 08:02:26 server ppp[198]: tun0: LCP: deflink: SendEchoReply(2) state = Opened This looks ok. Can you show me the logs from when the connection is established in each case ? Cheers. > jhousley@server:~ {13} pppctl -p xxxxxx 3000 show log > Log: Chat IPCP LCP Tun Warning Error Alert > Local: Warning Error Alert > > I am getting this with both RELENG_4_3 ppp and RELENG_4 ppp. Yes syslogd is running as "syslogd -s -s" If I turn on tcp/ip or debug I get lots of information in the log > files. Is it possible that some of the log levels were broken. I will try the latest verson from (http://www.Awfulak.org/~brian) is see if that logs properly > > Jim > -- > /"\ ASCII Ribbon Campaign . > \ / - NO HTML/RTF in e-mail . > X - NO Word docs in e-mail . > / \ ----------------------------------------------------------------- > jeh@FreeBSD.org http://www.FreeBSD.org The Power to Serve > jim@TheHousleys.Net http://www.TheHousleys.net > jhousley@SimTel.Net http://www.SimTel.Net > --------------------------------------------------------------------- > Your mouse has moved. > Windows NT must be restarted for the change to take effect! > > Reboot now? [OK] -- Brian http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 2:22:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id D921E37B41B; Tue, 11 Dec 2001 02:22:19 -0800 (PST) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.33 #1) id 16Dk3E-0005rx-00; Tue, 11 Dec 2001 12:22:16 +0200 Received: from localhost ([127.0.0.1] helo=pampa.cs.huji.ac.il ident=danny) by pampa.cs.huji.ac.il with esmtp (Exim 3.22 #2) id 16Dk3D-000AIb-00; Tue, 11 Dec 2001 12:22:15 +0200 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Terry Lambert Cc: Bernd Walter , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: irq In-Reply-To: Message from Terry Lambert of "Tue, 11 Dec 2001 01:12:43 PST." <3C15CE0B.FA53281B@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Dec 2001 12:22:15 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > It looks like IRQ sharing is the only issue here. > Q: are all interrupt handlers for the shared irq called, or only the 'correct' one? [...] > But I would still blame software (in particular, the firmware on > your Meteor). > > -- Terry isn't firmware another word for hardware :-)? danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 2:26:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21110.mail.yahoo.com (web21110.mail.yahoo.com [216.136.227.112]) by hub.freebsd.org (Postfix) with SMTP id 67E8B37B41B for ; Tue, 11 Dec 2001 02:26:45 -0800 (PST) Message-ID: <20011211102645.46795.qmail@web21110.mail.yahoo.com> Received: from [62.254.0.5] by web21110.mail.yahoo.com via HTTP; Tue, 11 Dec 2001 02:26:45 PST Date: Tue, 11 Dec 2001 02:26:45 -0800 (PST) From: Hiten Pandya Subject: Re: [SUGGESTION] - JFS for FreeBSD To: Peter Wemm Cc: hackers@FreeBSD.org In-Reply-To: <20011211093550.D4BF638CC@overcee.netplex.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > [... Hiten want's to GPL'ify FreeBSD ...] hi, first of all, i would like to clear of some point which have been taken wrongly. o My Intentions were never to GPL'ify FreeBSD :-) o The reason i started this discussion was because i think JFS/JFS2 would be a nice addition to FreeBSD like the rest of the other filesystems. o The JFS does _not_ have to be root, and even if people were to download it because it is GPL'ed, the size of the filesystem is only around 1.0MB o Statistically, not everyone is going to run after IBM's JFS, when there are other similar File Systems o If people did want JFS, they can download it of our website, say http://www.FreeBSD.org/~jfs o It can also be a child project, like the JAVA Project. o I think, (personally), that we migh be able to get more Corporates attracted, if we take the step of porting quality (not exactly) GPL'ed technologies for FreeBSD (my personal thoughts) o It is hard to Port AIX or OS/2 based code, but we have to agree that, BSD Users were meant to take that kind of challenges, have taken before o The JFS, can just be a bonus addition for FreeBSD, and does not have to be part of the base addition, example: CD-ROMS /DVD or any other releases which prohibit GNU Code. ===== -Hiten, Thank You, Yours Sincerely, Hiten Pandya, __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 3:14:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id C71C337B416; Tue, 11 Dec 2001 03:14:07 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id fBBBE6i35902; Tue, 11 Dec 2001 06:14:06 -0500 (EST) (envelope-from mwlucas) Date: Tue, 11 Dec 2001 06:14:06 -0500 From: Michael Lucas To: D J Hawkey Jr Cc: Robert Watson , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011211061406.C35343@blackhelicopters.org> References: <20011210155924.A1542@sheol.localdomain> <20011210173206.A1795@sheol.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011210173206.A1795@sheol.localdomain>; from hawkeyd@visi.com on Mon, Dec 10, 2001 at 05:32:06PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Dec 10, 2001 at 05:32:06PM -0600, D J Hawkey Jr wrote: > Don't get me wrong - I don't expect the same level of support from the > FreeBSD Project than I would from, say, Sybase or Sun. Having said that, > I think FreeBSD's is outstanding, even compared to some other commercial > *cough*Microsquish(tm)*cough* entities. Yep, that's why we're here. Glad you think so, mind you! > My current plans are to have several patchfiles, grouped by subject (bugfix > and/or enhancement), and subordinately grouped by FreeBSD release: > > ich_sound-patch-4.2REL.udiff delayed_ack-patch-4.2REL.udiff > ich_sound-patch-4.3REL.udiff delayed_ack-patch-4.3REL.udiff > ich_sound-patch-4.3STA.udiff agp_for_xf86-patch-4.2REL.udiff > > You get the idea. Excellent Other people will help with QA, if this takes off. Believe me, if a patch blows up a system you'll hear about it. > Hey, I'm not taking _anything_ away from y'all; I think all the BSDs are > outstanding products. I'm just gonna see if I can't fulfill what I percieve > as a support deficiency (again, from my own perspective) in my own little > way. That's the only way anything gets done around here; someone sees a need, and fills it. The only question is, is this a need? From watching the mailing lists, I certainly think it is. > PS, I'm rather honored that such an illustrious group has shown > interest enough to even discuss all this with me. You know, I think I'm going to write an article on this, I say it often enough. #include The FreeBSD group is really not that illustrious. Some of us are -- if Bruce Evans speaks, we all shut up and listen. We are simply the people who do the work. Everything that is done, is done because someone thought there was a need. I got my start in the FreeBSD community back in 1999 by writing articles. This isn't something that *directly* benefits the Project; it adds nothing to the CVS repo, and doesn't get me the coveted @freebsd.org email address. It's important, however, and something that I am very well-qualified to do. So I shut up, and did it. It got me a certain amount of recognition and respect in the community, it was fun, and it satisfied my itch to solve a problem. There is a huge amount of basic grunt work that can be done. Nobody bothers to do it, so it doesn't happen. People such as you and I can ease a vital gap by simply picking some little hole, and doing the work to fill it. It's not glamorous. It's not exciting. But it lets people like $YOURFAVORITECODECOMMITTER get on with stuff that only they can do. Lots of people say that they want to help. Lots of people make suggestions. Some make suggestions that are well beyond their ability to perform. In this case, those suggestions are usually either obvious ("Hey, wouldn't it be cool if FreeBSD supported FireWire?") or clueless ("Why don't we have a kernel option READMYMINDANDDOWHATIWANT?"). These suggestions are generally ignored; both would be good ideas, but one requires convincing a developer to pick it up and the other is brain-dead. Some suggestions are within the ability of the people making the suggestion. Posting on a mailing list and saying "Hey, would this be a good idea?" is a great way to tell if you have a boneheaded idea, or if you have a serious need. Your case is a great example of this. You can't expect a thousand people to write back and say "Oh, it's a good idea." This is a public discussion board, and everyone on it gets far too much email as-is. If we read something we agree with, we aren't going to all post "me too!" But if you get a few people publically agreeing with you, and nobody says "Your idea sucks!", you can generally assume that it's a decent idea. Once you have buy-in, go *DO IT*. I've seen a lot of decent ideas come across the FreeBSD mailing lists since 1996. Most of them die on the vine. The point is this: J D, you have an idea. Your messages have been read by most of the readers of this mailing list. You have gotten a "do it!" from a few people, including a -core member. You have gotten a few side comments from other developers, such as Matt Dillon's comment on your future in the flame wars. So, people have actually read this thread. I might be wrong, but I don't believe that you have received a message saying "Your idea sucks!" You have also received a few comments on other ways this can be handled; this should be taken in the spirit in which it is meant, which is "It's a good idea, here's how you could improve it." In FreeBSD, this is what passes for "management buy-in." This is not the first time I've seen this idea on this mailing list. I sincerely, devoutly hope that it is the last. So, I officially challenge you: are you going to do it, or is this going to wither on the vine like every other time it's been suggested? Consider the gauntlet thrown (in the kindest possible manner, mind you). Put up an initial patchset, announce it here and on, say, daily.daemonnews.org, list an email address for patches on the web page, and see what happens. In fact, if you do it well, you might even find a vaguely well-known BSD columnist picking up your site in a future article. ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 3:22:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tungsten.btinternet.com (tungsten.btinternet.com [194.73.73.81]) by hub.freebsd.org (Postfix) with ESMTP id EA7EF37B416 for ; Tue, 11 Dec 2001 03:22:05 -0800 (PST) Received: from host213-123-128-3.in-addr.btopenworld.com ([213.123.128.3] helo=there) by tungsten.btinternet.com with smtp (Exim 3.22 #8) id 16Dkz5-0006Xd-00; Tue, 11 Dec 2001 11:22:03 +0000 Content-Type: text/plain; charset="iso-8859-1" From: Dominic Marks To: Hiten Pandya Subject: Re: [SUGGESTION] - JFS for FreeBSD Date: Tue, 11 Dec 2001 11:21:42 +0000 X-Mailer: KMail [version 1.3.2] Cc: hackers@FreeBSD.org References: <20011211102645.46795.qmail@web21110.mail.yahoo.com> In-Reply-To: <20011211102645.46795.qmail@web21110.mail.yahoo.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday 11 December 2001 10:26 am, Hiten Pandya wrote: > > [... Hiten want's to GPL'ify FreeBSD ...] > > hi, > first of all, i would like to clear of some point > which > have been taken wrongly. > What mail client do you use? It seems to be playing havoc with your line breaks. > o My Intentions were never to GPL'ify FreeBSD :-) Yes, but your plans do involve making FreeBSD contain potentially more GPL'ed code than it already does. There are good reasons to keep GPL code away from the rest of the source (Legal and emotive). > o The reason i started this discussion was because > i think JFS/JFS2 would be a nice addition to > FreeBSD like the rest of the other filesystems. While I have nothing against JFS support in any way and I suppose it would be a nice addition for some users, what does it really offer that is going to be of use to most FreeBSD users? Commercial ones or otherwise. From the people I've discussed JFS with they seem to agree that its best features are in volume administration (In their opinion) - are the management tools part of the GPL'ed code base at all? If not I think it would be more useful improving what we already have, UFS. > o The JFS does _not_ have to be root, and even if > people were to download it because it is GPL'ed, > the size of the filesystem is only around 1.0MB Okay, but if people do use it and do want it for their system, including as the root filesystem then it is a problem to be resolved. Since quite a few of the pre-existing filesystems (UFS, NFS, ISO9660) do have ability to work in this manner. > o Statistically, not everyone is going to run after > IBM's JFS, when there are other similar File > Systems Yes, but I hope your not planning to port them all :) > o If people did want JFS, they can download it of > our website, say http://www.FreeBSD.org/~jfs > > o It can also be a child project, like the JAVA > Project. This is okay but adds complexity from your point of view as well as the end user. One of the best things about the BSDs as opposed to Linux for example is that in general I do not have to apply any (or many) patches to the kernel. > o I think, (personally), that we migh be able to get > more Corporates attracted, if we take the step of > porting quality (not exactly) GPL'ed technologies > for FreeBSD (my personal thoughts) Corporate investment is like dynamite. It can be a very useful tool for getting things done, and it can also blow up in your face. > o It is hard to Port AIX or OS/2 based code, but we > have to agree that, BSD Users were meant to take > that kind of challenges, have taken before > > o The JFS, can just be a bonus addition for FreeBSD, > and does not have to be part of the base addition, > example: CD-ROMS /DVD or any other releases which > prohibit GNU Code. > > ===== > -Hiten, > Thanks -- Dominic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 3:25:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from chmls16.mediaone.net (chmls16.mediaone.net [24.147.1.151]) by hub.freebsd.org (Postfix) with ESMTP id 6B1FC37B416 for ; Tue, 11 Dec 2001 03:25:50 -0800 (PST) Received: from gandalf (h00045ae37142.ne.mediaone.net [65.96.123.237]) by chmls16.mediaone.net (8.11.1/8.11.1) with SMTP id fBBBPmT20603 for ; Tue, 11 Dec 2001 06:25:48 -0500 (EST) Message-ID: <005c01c18236$a50f1b00$6401a8c0@gandalf> From: "Dragon Fire" To: Subject: KLDs vs static linking Date: Tue, 11 Dec 2001 06:26:09 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Folks, Hopefully a quick question. Is there any reason to prefer KLD modules for drivers etc over static linking? For example, KLDs are covenient, loading and unloading for development but is it a case of using KLD modules for development then building drivers statically into the kernel when development is complete.Or is it a case of KLDs are now supported and are the preferred method of development moving forward. I've read the online KLD docs, developed the code and greped through kern_linker.c so I understand how to develop KLDs it but would like to supplement my understanding. Thanks in advance, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 3:48:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brea.mc.mpls.visi.com (brea.mc.mpls.visi.com [208.42.156.100]) by hub.freebsd.org (Postfix) with ESMTP id E2C8A37B416 for ; Tue, 11 Dec 2001 03:48:20 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by brea.mc.mpls.visi.com (Postfix) with ESMTP id D63072DE2CD; Tue, 11 Dec 2001 05:48:19 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBBBmJ005633; Tue, 11 Dec 2001 05:48:19 -0600 (CST) (envelope-from hawkeyd) Date: Tue, 11 Dec 2001 05:48:19 -0600 From: D J Hawkey Jr To: Michael Lucas Cc: hackers@freebsd.org Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011211054818.A5471@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011210155924.A1542@sheol.localdomain> <20011210173206.A1795@sheol.localdomain> <20011211061406.C35343@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211061406.C35343@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Tue, Dec 11, 2001 at 06:14:06AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Geez. Don't some of you sleep, either? On Dec 11, at 06:14 AM, Michael Lucas wrote: > > > My current plans are to have several patchfiles, grouped by subject (bugfix > > and/or enhancement), and subordinately grouped by FreeBSD release: > > > > ich_sound-patch-4.2REL.udiff delayed_ack-patch-4.2REL.udiff > > ich_sound-patch-4.3REL.udiff delayed_ack-patch-4.3REL.udiff > > ich_sound-patch-4.3STA.udiff agp_for_xf86-patch-4.2REL.udiff > > > > You get the idea. > > Excellent Well, as Mr. Watson pointed out, there are better ways, but for an initial rollout, I don't think that level of sophistication is required. > Other people will help with QA, if this takes off. Believe me, if a > patch blows up a system you'll hear about it. :-) > > Hey, I'm not taking _anything_ away from y'all; I think all the BSDs are > > outstanding products. I'm just gonna see if I can't fulfill what I percieve > > as a support deficiency (again, from my own perspective) in my own little > > way. > > That's the only way anything gets done around here; someone sees a > need, and fills it. The only question is, is this a need? From > watching the mailing lists, I certainly think it is. > > The point is this: > > J D, you have an idea. "D J", actually. But "Dave" or "Hawk" gets my attention faster. > Your messages have been read by most of the > readers of this mailing list. You have gotten a "do it!" from a few > people, including a -core member. You have gotten a few side comments > from other developers, such as Matt Dillon's comment on your future in > the flame wars. So, people have actually read this thread. I might > be wrong, but I don't believe that you have received a message saying > "Your idea sucks!" You have also received a few comments on other > ways this can be handled; this should be taken in the spirit in which > it is meant, which is "It's a good idea, here's how you could improve > it." > > In FreeBSD, this is what passes for "management buy-in." > > So, I officially challenge you: are you going to do it, or is this > going to wither on the vine like every other time it's been suggested? > Consider the gauntlet thrown (in the kindest possible manner, mind > you). Put up an initial patchset, announce it here and on, say, > daily.daemonnews.org, list an email address for patches on the web > page, and see what happens. No challenge necessary. I, too, believe the general attitude is "Go for it.". So I'm going to. It won't be much to look at initially - maybe ever - but I'll bring it up and see what happens. It'll take a few days, but I'll post an "It's here." when it's here. BTW, am I allowed to use the daemon mascot? I spent some time yesterday browsing cvs-all@, and got another little patch that backported easily and fixed a nagging problem I've had since day two (that AGP patch in the above example). > In fact, if you do it well, you might even find a vaguely well-known > BSD columnist picking up your site in a future article. Ack. Don't do that. Sooner or later, the economy will pick up again, I'll get myself the badly-needed job I lost, and my play-time will once again be reduced by a factor of four. The last thing I'll need then is any kind of publicity. > ==ml Thanks for all the encouragement and feedback, Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 4: 1:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21101.mail.yahoo.com (web21101.mail.yahoo.com [216.136.227.103]) by hub.freebsd.org (Postfix) with SMTP id A580637B405 for ; Tue, 11 Dec 2001 04:01:04 -0800 (PST) Message-ID: <20011211120104.28477.qmail@web21101.mail.yahoo.com> Received: from [62.254.0.5] by web21101.mail.yahoo.com via HTTP; Tue, 11 Dec 2001 04:01:04 PST Date: Tue, 11 Dec 2001 04:01:04 -0800 (PST) From: Hiten Pandya Subject: Re: [SUGGESTION] - JFS for FreeBSD To: Dominic Marks Cc: hackers@FreeBSD.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, BTW, i am a first timer at porting a file system... if the proffesionals think that it is not wise or useful to port the FS (especially IBM's), it is OK, but, just in case, anyone else (more than three people) would like to port this FS to FreeBSD, my target would be to get it done by September 2002, if we work in a group... i dont have web-space where i can host this project, and we would need a mailing list... probably freebsd-jfs would help.. and http://people.freebsd.org/~bsdjfs but thats only if three of more people are _really_ interested in porting it... cause as you know... porting an IBM file system (from looks) is not a one man job :-) =Hiten = > What mail client do you use? It seems to be playing > havoc with your > line breaks. Sorry, as you know, i am only 15 years old, and my dad has no plans to get me a pop account and let me have my machine on 24/365 jus' to receive mail.. :-( but... i use Yahoo! Mail, which if by far the fastest mail i am using at the moment... i used to have hotmail but as you know.... Microsft-Hotmail.. so i left it.. You can point me to a better free mail account, which i can use in conjuction with my FreeBSD system having to keep it on 24/7 > Yes, but your plans do involve making FreeBSD > contain potentially > more GPL'ed code than it already does. There are > good reasons to keep > GPL code away from the rest of the source (Legal and > emotive). well.. yeah =Hiten = ===== -Hiten, Thank You, Yours Sincerely, Hiten Pandya, __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 4: 8:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id F1BD537B416 for ; Tue, 11 Dec 2001 04:08:37 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id fBBC8bH36279; Tue, 11 Dec 2001 07:08:37 -0500 (EST) (envelope-from mwlucas) Date: Tue, 11 Dec 2001 07:08:36 -0500 From: Michael Lucas To: D J Hawkey Jr Cc: hackers@freebsd.org Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011211070836.A36258@blackhelicopters.org> References: <20011210155924.A1542@sheol.localdomain> <20011210173206.A1795@sheol.localdomain> <20011211061406.C35343@blackhelicopters.org> <20011211054818.A5471@sheol.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211054818.A5471@sheol.localdomain>; from hawkeyd@visi.com on Tue, Dec 11, 2001 at 05:48:19AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Dec 11, 2001 at 05:48:19AM -0600, D J Hawkey Jr wrote: > > J D, you have an idea. > > "D J", actually. But "Dave" or "Hawk" gets my attention faster. Mea culpa. Please blame this on four hours sleep, followed by four hours blindly running Oracle's "adpatch" before the DBAs arrive... Personally, I respond to just about anything, including "Hey, Loser!" > > In fact, if you do it well, you might even find a vaguely well-known > > BSD columnist picking up your site in a future article. > > Ack. Don't do that. Sooner or later, the economy will pick up again, I'll > get myself the badly-needed job I lost, and my play-time will once again > be reduced by a factor of four. The last thing I'll need then is any kind > of publicity. Well, hang on here a second. I'd say you want publicity for exactly that reason. Eventually, you'll move on to other things. We want someone else to pick up when you depart. I strongly recommend you plan for your successor to come along. Don't worry about who that person is, just leave them an opening. Some poor slob who is hooked on your service will have no choice but to handle it when you're too busy to, and the whole community will benefit. :) For example, I'm working on the FAQ right now. If you check various parts of the FAQ, you'll see that they were originally maintained by jkh, nik, and a long list of other people, all at different times. They would want someone to pick up where they left off. At some point, someone will succeed me as the FAQ "interested party". ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 4:12:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 7B19937B417 for ; Tue, 11 Dec 2001 04:12:43 -0800 (PST) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.33 #1) id 16Dlm3-0007bu-00; Tue, 11 Dec 2001 14:12:39 +0200 Received: from localhost ([127.0.0.1] helo=pampa.cs.huji.ac.il ident=danny) by pampa.cs.huji.ac.il with esmtp (Exim 3.22 #2) id 16Dlm2-000AOu-00; Tue, 11 Dec 2001 14:12:38 +0200 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "Dragon Fire" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: KLDs vs static linking In-reply-to: Your message of Tue, 11 Dec 2001 06:26:09 -0500 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 11 Dec 2001 14:12:38 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I use them - where possible - when i have the same kernel for different boxes and i can configure the differences via klm's. danny > Hi Folks, > > Hopefully a quick question. > > Is there any reason to prefer KLD modules for drivers etc over static > linking? For example, KLDs are covenient, loading and unloading for > development but is it a case of using KLD modules for development then > building drivers statically into the kernel when development is complete.Or > is it a case of KLDs are now supported and are the preferred method of > development moving forward. I've read the online KLD docs, developed the > code and greped through kern_linker.c so I understand how to develop KLDs it > but would like to supplement my understanding. > > Thanks in advance, > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 5:10:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dayab.ch (mail.dayab.ch [193.135.253.139]) by hub.freebsd.org (Postfix) with SMTP id AD26E37B417 for ; Tue, 11 Dec 2001 05:10:13 -0800 (PST) Received: (qmail 28999 invoked from network); 11 Dec 2001 13:07:05 -0000 Received: from unknown (HELO bturtle.ch) (193.135.253.141) by mail.dayab.ch with SMTP; 11 Dec 2001 13:07:05 -0000 Message-ID: <3C1613FB.4E83D50C@bturtle.ch> Date: Tue, 11 Dec 2001 14:11:07 +0000 From: "S. Aeschbacher" X-Mailer: Mozilla 4.75 [en] (X11; U; OpenBSD 3.0 i386) X-Accept-Language: en MIME-Version: 1.0 To: Lars Eggert Cc: hackers@freebsd.org Subject: Re: cable modem connection problem References: <20011206071926.QTHW27606.mta05-svc.ntlworld.com@there> <3C0F7966.908CD6E6@bturtle.ch> <3C1005ED.4090001@isi.edu> <20011207000918.JIID10846.mta07-svc.ntlworld.com@there> <3C100F4D.3080900@isi.edu> <85k7vyzspp.fsf@stiegl.niksun.com> <87n10s8rn6.fsf@cb293842-b.rmdws1.il.home.com> <3C13ABED.B249B519@bturtle.ch> <3C14E0F7.3060902@isi.edu> <3C15127B.8B8C8B3A@bturtle.ch> <3C1515D9.2090007@isi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Lars Eggert wrote: > > S. Aeschbacher wrote: > > This is possible, but I did not verify it (what kind of "mucking" > > could cause such kind of behaviour?). most of them are "better" > > residental pipes. > > Having a packet filter drop your traffic after you haven't done ARP/DHCP > in a while. But I agree that's pretty far-fetched. As I said, seems to be more of a modem problem, but the people from the local provider don't really seem to know what they are doing most of the time (this is only one of several problems they have, e.g. mail and dns which often do not work), so all is possible. > > The problem seems to occur only on Samsung modems. > > Ah! Another data point. Then I'd assume it's the modem. Have you tried > powercycling it? (That should keep the ARP cache on the client intact). > Tried to email Samsung? Is there a firmware update? IIRC powercycling did not help (and for most clients this is no solution as isn't rebooting the gateway). As soon as I found the arp workaround, the problem was solved for me and I did not investigate more. > > Cannot confirm this as i don't use windows. I heard of a friend of > > mine, that he has running a windows ftp-server for days on a pipe > > from the same provider with another modem (a Com21) and that he is > > not experiencing any of the problems mentioned. > > Can he/she tcpdump for ARP packets? Maybe Windows' ARP cache timeout is > lower than FreeBSD's. I see what I can do to find this out (actually this could be measured with any windows machine, maybe somone with windows machines in his net could make a quick tcpdump session?) Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 5:23:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dayab.ch (mail.dayab.ch [193.135.253.139]) by hub.freebsd.org (Postfix) with SMTP id D442137B419 for ; Tue, 11 Dec 2001 05:23:23 -0800 (PST) Received: (qmail 29278 invoked from network); 11 Dec 2001 13:20:19 -0000 Received: from unknown (HELO bturtle.ch) (193.135.253.141) by mail.dayab.ch with SMTP; 11 Dec 2001 13:20:19 -0000 Message-ID: <3C161716.1C479850@bturtle.ch> Date: Tue, 11 Dec 2001 14:24:22 +0000 From: "S. Aeschbacher" X-Mailer: Mozilla 4.75 [en] (X11; U; OpenBSD 3.0 i386) X-Accept-Language: en MIME-Version: 1.0 To: Hiten Pandya Cc: hackers@FreeBSD.org Subject: Re: cable modem connection problem References: <20011210193629.98528.qmail@web21103.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hiten Pandya wrote: > > >what kind of "mucking" could cause such kind of > >behaviour?. > > this kind of problem did occur to me several times > with NTL (http://ntl.com/) in UK... > > there were installing a Universal Shared Bandwith > Router in their CO (Central Office), after they > installed this piece of sh*t, the bandwith was > throttled from 5.00pm evening to 5.00am morning, > which was to slow down users from downloading large > files i.e. Music Sharing and such.... > > but after 5.00am, it was all fine and back to 85.0KBps > when before 5.00am and after 5.00pm was around > 12.0KBps > which is sad but was true for a while till users > complained about it... (like me)... And the problems went away when they stopped limiting the bandwidth? > so that is a possibility, or it could be that the > signal you are receiving (cable modem signal) is very > weak.... thats a possibility too... If this was the problem, it could not be solved by deleting the arp entries. Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 6: 8: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 574CA37B416; Tue, 11 Dec 2001 06:07:59 -0800 (PST) Received: from pool0114.cvx21-bradley.dialup.earthlink.net ([209.179.192.114] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16DnZd-0002IS-00; Tue, 11 Dec 2001 06:07:58 -0800 Message-ID: <3C161343.A62C005C@mindspring.com> Date: Tue, 11 Dec 2001 06:08:03 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Maxim Sobolev Cc: Greg Lehey , Hiten Pandya , current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <20011210220153.50612.qmail@web21102.mail.yahoo.com> <3C15AB82.FDF598A8@mindspring.com> <20011211182856.A67986@monorchid.lemis.com> <3C15C9B4.C74F914@mindspring.com> <3C15CED5.20D65BFE@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > > OK, I load the kernel from the JFS. I mount the root FS, which > > is a JFS. I read the module "jfs.ko" from the JFS so that I can > > mount the root FS, which is a JFS, so I can read the module "jfs.ko" > > from the JFS so that I can mount the root FS, which is a JFS, so I > > can read the module "jfs.ko" from the JFS so that I can mount the > > root FS, which is a JFS, so I can... > > > > Do you see the problem yet? > > Libstand (and hence the loader) could be extended to allow reading > files from jfs without using any GPL'ed code. For example our loader > can load modules from the FAT even though we do not have any M$ code. > :) Alternatively, /boot could be placed on separate filesystem, which > could be ufs or anything else supported by the loader. Patches appreciated. Note that if you do a read-only JFS, you are more than half way there to a n0n-GPL'ed implementation, so you might as well finish it off, instead of porting the IBM code. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 6: 9:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 9DB9A37B419; Tue, 11 Dec 2001 06:09:43 -0800 (PST) Received: from pool0114.cvx21-bradley.dialup.earthlink.net ([209.179.192.114] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16DnbK-0003zf-00; Tue, 11 Dec 2001 06:09:42 -0800 Message-ID: <3C1613AD.53C45B3@mindspring.com> Date: Tue, 11 Dec 2001 06:09:49 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: Greg Lehey , Hiten Pandya , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <20011211093550.D4BF638CC@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Wemm wrote: > It is not a problem. The *kernel* does not load jfs.ko, it is loader > itself. There is no reason why a trivial non-gpl jfs reader couldn't be > written for boot2 and loader if the need was great enough. Or have /boot > as a seperate file system (eg: UFS or FAT32). We do this on IA64 where > /boot is a FAT32 filesystem (not exactly, but close enough. I usually > mount it on /efi and make /boot/ a symlink to /efi/boot so that in EFI > we have a /boot as well). JFS patches? Sysinstall patches? /usr/src/lib/stand patches? /usr/src/sys/boot/* patches? 8^). --- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 6:13: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21101.mail.yahoo.com (web21101.mail.yahoo.com [216.136.227.103]) by hub.freebsd.org (Postfix) with SMTP id 9B9CE37B419 for ; Tue, 11 Dec 2001 06:12:55 -0800 (PST) Message-ID: <20011211141255.63932.qmail@web21101.mail.yahoo.com> Received: from [62.254.0.5] by web21101.mail.yahoo.com via HTTP; Tue, 11 Dec 2001 06:12:55 PST Date: Tue, 11 Dec 2001 06:12:55 -0800 (PST) From: Hiten Pandya Subject: Re: [SUGGESTION] - JFS for FreeBSD To: Terry Lambert Cc: hackers@FreeBSD.org In-Reply-To: <3C161343.A62C005C@mindspring.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG that would be nice i suppose.. :-) BTW, where is this non-GPL code.. i wouldn't mind putting my hands on it and working on it... =Hiten = --- Terry Lambert wrote: > Maxim Sobolev wrote: > > > OK, I load the kernel from the JFS. I mount the > root FS, which > > > is a JFS. I read the module "jfs.ko" from the > JFS so that I can > > > mount the root FS, which is a JFS, so I can read > the module "jfs.ko" > > > from the JFS so that I can mount the root FS, > which is a JFS, so I > > > can read the module "jfs.ko" from the JFS so > that I can mount the > > > root FS, which is a JFS, so I can... > > > > > > Do you see the problem yet? > > > > Libstand (and hence the loader) could be extended > to allow reading > > files from jfs without using any GPL'ed code. For > example our loader > > can load modules from the FAT even though we do > not have any M$ code. > > :) Alternatively, /boot could be placed on > separate filesystem, which > > could be ufs or anything else supported by the > loader. > > Patches appreciated. > > Note that if you do a read-only JFS, you are more > than half way there > to a n0n-GPL'ed implementation, so you might as well > finish it off, > instead of porting the IBM code. > > -- Terry ===== -Hiten, Thank You, Yours Sincerely, Hiten Pandya, __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 6:14:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 4096937B405; Tue, 11 Dec 2001 06:14:49 -0800 (PST) Received: from pool0114.cvx21-bradley.dialup.earthlink.net ([209.179.192.114] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Dng6-0000u3-00; Tue, 11 Dec 2001 06:14:38 -0800 Message-ID: <3C1614D5.B5C3B4C5@mindspring.com> Date: Tue, 11 Dec 2001 06:14:45 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Danny Braniss Cc: Bernd Walter , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: irq References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Danny Braniss wrote: > > > It looks like IRQ sharing is the only issue here. > > Q: are all interrupt handlers for the shared irq called, or only the > 'correct' one? All interrupt handlers are polled -- asked if they have work to do, on the basis of having caused the interrupt. Some cards do not have a hardware "I caused an interrupt" register, and use a differential (e.g. ring head vs. tail inequal after interrupt) to tell if there is work to do. If these cards were to share interrupts, then they most likely do work every interrupt, and less work per interrupt, then would otherwise be the case (i.e. it would defeat hardware interrupt coelescing thresholds, among other things). > [...] > > > But I would still blame software (in particular, the firmware on > > your Meteor). > > > > -- Terry > > isn't firmware another word for hardware :-)? No, because you can fix firmware in software, but you can't fix hardware in software, and get anywhere near the performance (e.g. CMD640B, etc.). For example, you could use the PCI bus management code to ensure broken cards got seperate interrupts from all other cards. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 6:22:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id 0ADD237B419 for ; Tue, 11 Dec 2001 06:22:25 -0800 (PST) Received: (from root@localhost) by bugz.infotecs.ru (8.11.6/8.11.4) id fBBEMMW00972 for freebsd-hackers@freebsd.org; Tue, 11 Dec 2001 17:22:22 +0300 (MSK) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200112111422.fBBEMMW00972@bugz.infotecs.ru> Subject: Re: Motion for removal of xargs(1) from base system To: freebsd-hackers@freebsd.org Date: Tue, 11 Dec 2001 17:22:22 +0300 (MSK) In-Reply-To: <44429.1008026020@winston.freebsd.org> from "Jordan Hubbard" at Dec 10, 2001 03:13:40 PM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > My, is it April 1st already? How quickly time flies! December feels > like it was just yesterday! > > - Jordan Ehe, as far as I can see some people even have taken it seriously :) This probably shows that when you have to read 300 emails/day, your attention slowly but constantly leaves you. :) I think the original author's point was to write some rant about recent removal of some frequently used (as he thinks) tools from the base system. At least I had fun reading it :) Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 6:40:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 846A437B422 for ; Tue, 11 Dec 2001 06:40:39 -0800 (PST) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 78ED54CE6C; Tue, 11 Dec 2001 09:40:38 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id JAA03743; Tue, 11 Dec 2001 09:40:37 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id GAA23402; Tue, 11 Dec 2001 06:40:36 -0800 (PST) Message-Id: <200112111440.GAA23402@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: josb@cncdsl.com Subject: Re: sscanf(..., "%lld", ...) broken? Cc: hackers@freebsd.org Date: Tue, 11 Dec 2001 06:40:36 -0800 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Is this PR-worthy? Not really; the C99 conformance project is already working on this (in particular, I am working on scanf). Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 7:21:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts5-srv.bellnexxia.net (tomts5.bellnexxia.net [209.226.175.25]) by hub.freebsd.org (Postfix) with ESMTP id A790937B417 for ; Tue, 11 Dec 2001 07:21:10 -0800 (PST) Received: from xena.gsicomp.on.ca ([199.243.149.34]) by tomts5-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20011211152058.NSSS23035.tomts5-srv.bellnexxia.net@xena.gsicomp.on.ca>; Tue, 11 Dec 2001 10:20:58 -0500 Received: from localhost (matt@localhost) by xena.gsicomp.on.ca (8.11.1/8.11.1) with ESMTP id fBBFCZc04595; Tue, 11 Dec 2001 10:12:36 -0500 (EST) (envelope-from matt@xena.gsicomp.on.ca) Date: Tue, 11 Dec 2001 10:12:35 -0500 (EST) From: Matthew Emmerton To: Chad David Cc: hackers@FreeBSD.ORG Subject: Re: SMP beeping In-Reply-To: <20011210223332.A528@colnta.acns.ab.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 10 Dec 2001, Chad David wrote: > I sent a message about this to -stable last week, but didn't get any > input that resulted in a solution to this problem so... > > -stable for the last week or more (I did a make world last week for > the first time in over a month) beeps on and off when SMP is enabled. > The beeping appears to be timed with very short stalls of the system; > that is, when moving the mouse across the screen it stops at what > seems to be that start of each beep. The beeps are not consistent > in length, but the tone does not change. If I boot a kernel with > the exact same config only with SMP disabled it does not beep, and > mouse cursor movement is fluid. You never mentioned that the beeps were caused by moving your mouse before! Are you using a KVM? If so, does this problem occur when using a mouse that is directly connected to you system? -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 8:52:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id A325C37B405 for ; Tue, 11 Dec 2001 08:52:39 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fBBGp4j31766 for ; Tue, 11 Dec 2001 17:51:05 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: hackers@freebsd.org Subject: Junior Kernel hacker task: Floppy driver mode handling. From: Poul-Henning Kamp Date: Tue, 11 Dec 2001 17:51:04 +0100 Message-ID: <31764.1008089464@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG There exists a patch for adding a mode to our floppy driver to add DEC RX50 media handling. The crucial part of this is the addition of this line: { 10,2,0xFF,0x10,80, 800,1,FDC_300KBPS,1,0x2E,1 }, /* 400K DEC RX50 */ But if one examines the fd.c driver, one cannot help but notice that the handling of densities is a bit convoluted, to put it mildly. I'm looking for a volounteer to do this, it is a quite simple job and I am quite sure that practically everybody has the hardware they need to do this :-) Cleaning it up consists of the following steps: 1. Define a new set of (bitmap) macros to distinguish the drive type: #define FD_3S 0x0001 /* 3.5" single density */ #define FD_5S 0x0002 /* 5.25" single density */ ... And use these instead of the FD_1200 and similar in struct fd_data->type. 2. Augment the struct fd_type with two new fields: int minor; /* minor device encoding */ int drives; /* bitmap of compatible drives (FD_[35][SD]) */ And fill these fields out in the fd_types[NUMTYPES] array. Add a termination entry at the end of the table so the NUMTYPES, NUMDENS, and FD_%d[5_25] #defines can be eliminated. 3. Change the _clone code to use the new "minor" field instead of the private table it uses now. (Eliminate and avoid any use of NUMTYPES, NUMDENS and FD_%d[5_25]). 4. Change the code in Fdopen to examine the "drives" field in the fd_types[] array instead of the hardcoded switch. (Eliminate and avoid any use of NUMTYPES, NUMDENS and and FD_%d[5_25]); 5. Remove any other use of NUMTYPES, NUMDENS and FD_%d[5_25] 6. Add the "rx50" entry from above to the table to show how simple that is now. 7. Make it possible to define a new mode from userland with an ioctl. (hint: instead of the index, put a pointer to the struct fd_type into the fd_data structure.) Preferably, send one patch per step rather than one huge patch since that will make reviewing easier. First volounteer to send me email gets the assignment. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 9:41:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 8E52C37B405; Tue, 11 Dec 2001 09:41:09 -0800 (PST) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fBBHesi28058; Tue, 11 Dec 2001 12:40:54 -0500 (EST) (envelope-from arr@FreeBSD.org) X-Authentication-Warning: fledge.watson.org: arr owned process doing -bs Date: Tue, 11 Dec 2001 12:40:53 -0500 (EST) From: "Andrew R. Reiter" X-Sender: arr@fledge.watson.org To: Poul-Henning Kamp Cc: hackers@FreeBSD.org Subject: Re: Junior Kernel hacker task: Floppy driver mode handling. In-Reply-To: <31764.1008089464@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Someone already doing this? If not, I'm down. On Tue, 11 Dec 2001, Poul-Henning Kamp wrote: : :There exists a patch for adding a mode to our floppy driver to :add DEC RX50 media handling. : :The crucial part of this is the addition of this line: : { 10,2,0xFF,0x10,80, 800,1,FDC_300KBPS,1,0x2E,1 }, /* 400K DEC RX50 */ : :But if one examines the fd.c driver, one cannot help but notice that the :handling of densities is a bit convoluted, to put it mildly. : :I'm looking for a volounteer to do this, it is a quite simple job and :I am quite sure that practically everybody has the hardware they need to :do this :-) : :Cleaning it up consists of the following steps: : :1. Define a new set of (bitmap) macros to distinguish the drive type: : #define FD_3S 0x0001 /* 3.5" single density */ : #define FD_5S 0x0002 /* 5.25" single density */ : ... : And use these instead of the FD_1200 and similar in : struct fd_data->type. : :2. Augment the struct fd_type with two new fields: : int minor; /* minor device encoding */ : int drives; /* bitmap of compatible drives (FD_[35][SD]) */ : And fill these fields out in the fd_types[NUMTYPES] array. : Add a termination entry at the end of the table so the : NUMTYPES, NUMDENS, and FD_%d[5_25] #defines can be eliminated. : :3. Change the _clone code to use the new "minor" field instead of : the private table it uses now. (Eliminate and avoid any : use of NUMTYPES, NUMDENS and FD_%d[5_25]). : :4. Change the code in Fdopen to examine the "drives" field in the : fd_types[] array instead of the hardcoded switch. (Eliminate : and avoid any use of NUMTYPES, NUMDENS and and FD_%d[5_25]); : :5. Remove any other use of NUMTYPES, NUMDENS and FD_%d[5_25] : :6. Add the "rx50" entry from above to the table to show how simple : that is now. : :7. Make it possible to define a new mode from userland with an ioctl. : (hint: instead of the index, put a pointer to the struct fd_type into : the fd_data structure.) : :Preferably, send one patch per step rather than one huge patch since that :will make reviewing easier. : :First volounteer to send me email gets the assignment. : :-- :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 :phk@FreeBSD.ORG | TCP/IP since RFC 956 :FreeBSD committer | BSD since 4.3-tahoe :Never attribute to malice what can adequately be explained by incompetence. : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : -- Andrew R. Reiter arr@watson.org arr@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 10:42:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.acns.ab.ca (h24-64-56-135.cg.shawcable.net [24.64.56.135]) by hub.freebsd.org (Postfix) with ESMTP id 05F3137B41C for ; Tue, 11 Dec 2001 10:42:14 -0800 (PST) Received: from colnta.acns.ab.ca (colnta.acns.ab.ca [192.168.1.2]) by mail.acns.ab.ca (8.11.6/8.11.3) with ESMTP id fBBIgBS03389; Tue, 11 Dec 2001 11:42:11 -0700 (MST) (envelope-from davidc@colnta.acns.ab.ca) Received: (from davidc@localhost) by colnta.acns.ab.ca (8.11.6/8.11.3) id fBBIgAb00391; Tue, 11 Dec 2001 11:42:10 -0700 (MST) (envelope-from davidc) Date: Tue, 11 Dec 2001 11:42:10 -0700 From: Chad David To: Matthew Emmerton Cc: hackers@FreeBSD.ORG Subject: Re: SMP beeping Message-ID: <20011211114210.B355@colnta.acns.ab.ca> References: <20011210223332.A528@colnta.acns.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from matt@gsicomp.on.ca on Tue, Dec 11, 2001 at 10:12:35AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Dec 11, 2001 at 10:12:35AM -0500, Matthew Emmerton wrote: > On Mon, 10 Dec 2001, Chad David wrote: > > > I sent a message about this to -stable last week, but didn't get any > > input that resulted in a solution to this problem so... > > > > -stable for the last week or more (I did a make world last week for > > the first time in over a month) beeps on and off when SMP is enabled. > > The beeping appears to be timed with very short stalls of the system; > > that is, when moving the mouse across the screen it stops at what > > seems to be that start of each beep. The beeps are not consistent > > in length, but the tone does not change. If I boot a kernel with > > the exact same config only with SMP disabled it does not beep, and > > mouse cursor movement is fluid. > > You never mentioned that the beeps were caused by moving your mouse > before! I didn't mention it because that is not what is does :). If you read the above you will notice that I am still not saying that. What I was saying was that there is a noticable pause in the system when ever a beep begins (every 1/2 sec - 1 sec), and the mouse is an obvious indicator of that. My assumption is that either something is beeping on purpose (there is a hardware/bios/kernel problem that I do not know about), or something in the kernel is writing to a bad address when SMP is enabled. I was hoping that somebody was having the same problem or would at least have a better idea then I do. > > Are you using a KVM? If so, does this problem occur when using a mouse > that is directly connected to you system? Both with and without the switch it beeps. This machine has been runing for months without any problems... the only change was a make world, and a new kernel. The kernel I am running is basically GENERIC with SMP enabled. Since it appears nobody else is having the same problem, I guess I will pull the box out of production, and hack on it. I was hoping not to have to do that (my fault for putting -stable on it in the first place I guess). -- Chad David davidc@acns.ab.ca ACNS Inc. Calgary, Alberta Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 10:45:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 4855C37B41B; Tue, 11 Dec 2001 10:45:48 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fBBIiDj34176; Tue, 11 Dec 2001 19:44:14 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Andrew R. Reiter" Cc: hackers@FreeBSD.org Subject: Re: Junior Kernel hacker task: Floppy driver mode handling. In-Reply-To: Your message of "Tue, 11 Dec 2001 12:40:53 EST." Date: Tue, 11 Dec 2001 19:44:13 +0100 Message-ID: <34174.1008096253@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , "And rew R. Reiter" writes: > >Someone already doing this? If not, I'm down. You won, you're the first one in my inbox :-) Ready ? Steady ? Start! :-) > >On Tue, 11 Dec 2001, Poul-Henning Kamp wrote: > >: >:There exists a patch for adding a mode to our floppy driver to >:add DEC RX50 media handling. >: >:The crucial part of this is the addition of this line: >: { 10,2,0xFF,0x10,80, 800,1,FDC_300KBPS,1,0x2E,1 }, /* 400K DEC RX50 */ >: >:But if one examines the fd.c driver, one cannot help but notice that the >:handling of densities is a bit convoluted, to put it mildly. >: >:I'm looking for a volounteer to do this, it is a quite simple job and >:I am quite sure that practically everybody has the hardware they need to >:do this :-) >: >:Cleaning it up consists of the following steps: >: >:1. Define a new set of (bitmap) macros to distinguish the drive type: >: #define FD_3S 0x0001 /* 3.5" single density */ >: #define FD_5S 0x0002 /* 5.25" single density */ >: ... >: And use these instead of the FD_1200 and similar in >: struct fd_data->type. >: >:2. Augment the struct fd_type with two new fields: >: int minor; /* minor device encoding */ >: int drives; /* bitmap of compatible drives (FD_[35][SD]) */ >: And fill these fields out in the fd_types[NUMTYPES] array. >: Add a termination entry at the end of the table so the >: NUMTYPES, NUMDENS, and FD_%d[5_25] #defines can be eliminated. >: >:3. Change the _clone code to use the new "minor" field instead of >: the private table it uses now. (Eliminate and avoid any >: use of NUMTYPES, NUMDENS and FD_%d[5_25]). >: >:4. Change the code in Fdopen to examine the "drives" field in the >: fd_types[] array instead of the hardcoded switch. (Eliminate >: and avoid any use of NUMTYPES, NUMDENS and and FD_%d[5_25]); >: >:5. Remove any other use of NUMTYPES, NUMDENS and FD_%d[5_25] >: >:6. Add the "rx50" entry from above to the table to show how simple >: that is now. >: >:7. Make it possible to define a new mode from userland with an ioctl. >: (hint: instead of the index, put a pointer to the struct fd_type into >: the fd_data structure.) >: >:Preferably, send one patch per step rather than one huge patch since that >:will make reviewing easier. >: >:First volounteer to send me email gets the assignment. >: >:-- >:Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 >:phk@FreeBSD.ORG | TCP/IP since RFC 956 >:FreeBSD committer | BSD since 4.3-tahoe >:Never attribute to malice what can adequately be explained by incompetence. >: >:To Unsubscribe: send mail to majordomo@FreeBSD.org >:with "unsubscribe freebsd-hackers" in the body of the message >: > >-- >Andrew R. Reiter >arr@watson.org >arr@FreeBSD.org > > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 10:46:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from SRDMAIL.SINP.MSU.RU (bigking.sinp.msu.ru [213.131.9.130]) by hub.freebsd.org (Postfix) with ESMTP id 81AA037B405; Tue, 11 Dec 2001 10:46:03 -0800 (PST) Received: from dima (helo=localhost) by SRDMAIL.SINP.MSU.RU with local-esmtp (Exim 3.33 #3) id 16Drur-000Nat-00; Tue, 11 Dec 2001 21:46:09 +0300 Date: Tue, 11 Dec 2001 21:46:09 +0300 (MSK) From: Dmitry Mottl To: freebsd-questions@FreeBSD.org, Subject: system halt Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi I have problem accessing cuaa0 This is from /var/run/dmesg.boot == sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 == When I write cu -l /dev/cuaa0 system halts (console/network is not working at all) What happens? How can I aid this? ps. FreeBSD-4.0 My kernel uses same sio0 configuration as GENERIC: device sio0 at isa? port IO_COM1 flags 0x10 irq 4 Thank You! -- Dmitry mottl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 11:53:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 42C3F37B405 for ; Tue, 11 Dec 2001 11:53:22 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 73B8C33C; Tue, 11 Dec 2001 19:53:13 +0000 (GMT) Date: Tue, 11 Dec 2001 19:53:13 +0000 From: Josef Karthauser To: Hiten Pandya Cc: Dominic Marks , hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011211195313.E27214@tao.org.uk> References: <20011211120104.28477.qmail@web21101.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5oH/S/bF6lOfqCQb" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211120104.28477.qmail@web21101.mail.yahoo.com>; from hitmaster2k@yahoo.com on Tue, Dec 11, 2001 at 04:01:04AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --5oH/S/bF6lOfqCQb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 11, 2001 at 04:01:04AM -0800, Hiten Pandya wrote: >=20 > but thats only if three of more people are _really_ > interested in porting it... cause as you know... > porting an IBM file system (from looks) is not a=20 > one man job :-) >=20 It is probably a one man job if that man knows the kernel inside and out in these areas, and has the time and energy to see it through. I'd suggest that you find a much much smaller area to work on yourself for now though. (Take a look in the PR database for ideas of where to start). Joe --5oH/S/bF6lOfqCQb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwWZCgACgkQXVIcjOaxUBaEMQCfYfaHDdBFvJWAONXaWGIq1DLQ f6QAn03O+/4M6fB7tgMsYNq2ZauS8qBp =v1bN -----END PGP SIGNATURE----- --5oH/S/bF6lOfqCQb-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 12: 0:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from carbon.btinternet.com (carbon.btinternet.com [194.73.73.92]) by hub.freebsd.org (Postfix) with ESMTP id 9A8A937B417 for ; Tue, 11 Dec 2001 12:00:39 -0800 (PST) Received: from host217-35-43-30.in-addr.btopenworld.com ([217.35.43.30] helo=marvin.penguinpowered.org.uk) by carbon.btinternet.com with esmtp (Exim 3.22 #8) id 16Dt4i-00012b-00; Tue, 11 Dec 2001 20:00:24 +0000 Received: from [192.168.10.11] (helo=pan.realtime.co.uk) by marvin.penguinpowered.org.uk with esmtp (Exim 3.33 #1) id 16Dt8q-0008Ev-00; Tue, 11 Dec 2001 20:04:40 +0000 Received: from waynep by pan.realtime.co.uk with local (Exim 3.33 #1) id 16Dt2S-00007x-00; Tue, 11 Dec 2001 19:58:04 +0000 From: Wayne Pascoe To: Josef Karthauser Cc: freebsd-hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <20011211120104.28477.qmail@web21101.mail.yahoo.com> <20011211195313.E27214@tao.org.uk> Date: 11 Dec 2001 19:58:04 +0000 In-Reply-To: <20011211195313.E27214@tao.org.uk> Message-ID: <86u1uxzfzn.fsf@pan.home.penguinpowered.org.uk> Lines: 20 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Josef Karthauser writes: > It is probably a one man job if that man knows the kernel inside > and out in these areas, and has the time and energy to see it > through. I'd suggest that you find a much much smaller area to > work on yourself for now though. (Take a look in the PR database > for ideas of where to start). What is the PR database of which you speak and where can I find it? I am looking for a project to work on in my free time. Thanks, -- - Wayne Pascoe | The thing is, I was POSITIVE that I freebsd@molemanarmy.com | wasn't actually depressed, just that life http://www.molemanarmy.com | had no meaning and I was tired of living. | -- daystar on k5 | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 12:14:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 4B40E37B405; Tue, 11 Dec 2001 12:14:23 -0800 (PST) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id OAA26878; Tue, 11 Dec 2001 14:14:11 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Tue, 11 Dec 2001 14:14:11 -0600 (CST) From: Chris Dillon To: Dmitry Mottl Cc: , Subject: Re: system halt In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 11 Dec 2001, Dmitry Mottl wrote: > This is from /var/run/dmesg.boot > == > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 > == > > When I write > cu -l /dev/cuaa0 > > system halts (console/network is not working at all) > > What happens? > How can I aid this? You have the serial port disabled in the BIOS, or not set to the I/O port and IRQ that FreeBSD is expecting. Enable it in the BIOS and make sure the BIOS and FreeBSD agree about the settings by changing one or the other. I'm not sure exactly why this causes FreeBSD to freeze, but I have come across the problem as well. It is definately a hardware problem with an unfortunate software side-effect. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet - Available for IA32 (Intel x86) and Alpha architectures - IA64, PowerPC, UltraSPARC, and ARM architectures under development - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 12:27: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id 6F72B37B438; Tue, 11 Dec 2001 12:26:41 -0800 (PST) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id fBBJE3J85620; Tue, 11 Dec 2001 19:14:03 GMT (envelope-from nik) Date: Tue, 11 Dec 2001 19:14:03 +0000 From: Nik Clayton To: D J Hawkey Jr Cc: Nik Clayton , hackers@freebsd.org Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011211191403.B82053@canyon.nothing-going-on.org> References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011210080032.A4215@canyon.nothing-going-on.org> <20011210152414.A1367@sheol.localdomain> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="DKU6Jbt7q3WqK7+M" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011210152414.A1367@sheol.localdomain>; from hawkeyd@visi.com on Mon, Dec 10, 2001 at 03:24:14PM -0600 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --DKU6Jbt7q3WqK7+M Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 10, 2001 at 03:24:14PM -0600, D J Hawkey Jr wrote: > > Doesn't mean that you need 100% coverage though. If you produce > > something that only gets in 80% of the patches that could be applied > > back that's still better than what we have now. And it makes it easier > > for someone else to help out with the missing 20%. >=20 > Huh? You completely list me with this. Are you trying to say that some > feature of a patch that applies to just the last three of four prior > releases is OK, 'cuz right now none are (except for security fixes to > RELENG_(current - 1))? I meant that any effort you put in is better than none. For example, if you decide to start producing patches for 4.4 that bring in some features from -stable (e.g., delayed acks) that's far better than you not doing it at all. Don't feel that because you can't do everything you want to do that you shouldn't do any of it. If you get the ball rolling, and become known as *the* place to go for extra patches, you'll find that other people=20 start sending you additional patches to include. Pretty soon we'll get bored of having people ask "Hey, why aren't these patches in RELENG_4_4" (or whatever) and we'll corral you in to becoming a committer so that you can make this an 'official' part of FreeBSD. > > > So far, I've made three patchfiles that can be applied to 4.2REL and = 4.3REL. > > > Not exactly the repertoire one would need to garner interest and mome= ntum. > >=20 > > It's a start. What's the URL? >=20 > You're kidding, right? I only started thinking about doing this yesterday! > The patches are sitting right here, in $(HOME)/projects. OK. Well, if you put them up on a web site, we can link to them. If you can think of appropriate other places on the FreeBSD web site to mention them then we can do that too. Don't be put off because you want to start small. . . N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --DKU6Jbt7q3WqK7+M Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwWWvsACgkQk6gHZCw343XVaQCfetcqL25P3KrxR3kJR4G+IsOp BRAAn0XwmZzN5mToBxSM0yYEk5iy5GHi =xQXn -----END PGP SIGNATURE----- --DKU6Jbt7q3WqK7+M-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 12:37:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id A04DA37B506 for ; Tue, 11 Dec 2001 12:37:28 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fBBKbQa82076; Tue, 11 Dec 2001 13:37:26 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fBBKbOM30189; Tue, 11 Dec 2001 13:37:24 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200112112037.fBBKbOM30189@harmony.village.org> To: Poul-Henning Kamp Subject: Re: statefulness in character device drivers Cc: Dave Rufino , Alfred Perlstein , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 08 Dec 2001 10:04:18 +0100." <46358.1007802258@critter.freebsd.dk> References: <46358.1007802258@critter.freebsd.dk> Date: Tue, 11 Dec 2001 13:37:24 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <46358.1007802258@critter.freebsd.dk> Poul-Henning Kamp writes: : In message , Dave R : ufino writes: : : >> Most likely he means a per-open(2) opaque datum that is kept in : >> struct file and passed to the underlying routines. : > : >Sorry, unbelievably bad at explaining myself. Per-open data is what i : >meant. The reason I'm interested is it would make a full nvidia driver : >port quite a bit easier. : : Sorry, I know of no current plans which adress this. : : The issue is non-trivial to fix because we currently don't pass : dup(2) events through the vnode layer. I'm using a cloning device driver for my needs in this area. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 12:55:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 85DD237B405 for ; Tue, 11 Dec 2001 12:55:37 -0800 (PST) Received: (from uucp@localhost) by storm.FreeBSD.org.uk (8.11.6/8.11.6) with UUCP id fBBKtOh61407; Tue, 11 Dec 2001 20:55:24 GMT (envelope-from mark@grondar.za) Received: from grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.org (8.11.6/8.11.6) with ESMTP id fBBKojU62597; Tue, 11 Dec 2001 20:50:46 GMT (envelope-from mark@grondar.za) Message-Id: <200112112050.fBBKojU62597@grimreaper.grondar.org> To: Leo Bicknell Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: random + large IRQ's + SMP References: <20011204114843.B97202@ussenterprise.ufp.org> In-Reply-To: <20011204114843.B97202@ussenterprise.ufp.org> ; from Leo Bicknell "Tue, 04 Dec 2001 11:48:43 EST." Date: Tue, 11 Dec 2001 20:50:45 +0000 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > What I need to know is when this was fixed (assuming it was). I > tried to look through i386/i386/mem.c, per the messages to find > the fix, but somewhere between when that message was posted and > now random (and a few other things) were ripped out of there and > scattered across several machine independant files. This has not been fixed. I could look at it (I am the author of that) and look for a solution. It may take a bit of time. > with "unsubscribe freebsd-hackers" in the body of the message -- o Mark Murray \_ FreeBSD Services Limited O.\_ Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 13: 5: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brea.mc.mpls.visi.com (brea.mc.mpls.visi.com [208.42.156.100]) by hub.freebsd.org (Postfix) with ESMTP id D4CD037B405; Tue, 11 Dec 2001 13:05:00 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by brea.mc.mpls.visi.com (Postfix) with ESMTP id B2C422DDF85; Tue, 11 Dec 2001 15:04:59 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBBL4xn08549; Tue, 11 Dec 2001 15:04:59 -0600 (CST) (envelope-from hawkeyd) Date: Tue, 11 Dec 2001 15:04:59 -0600 From: D J Hawkey Jr To: Nik Clayton Cc: hackers@freebsd.org Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011211150459.A8415@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011210080032.A4215@canyon.nothing-going-on.org> <20011210152414.A1367@sheol.localdomain> <20011211191403.B82053@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211191403.B82053@canyon.nothing-going-on.org>; from nik@freebsd.org on Tue, Dec 11, 2001 at 07:14:03PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Dec 11, at 07:14 PM, Nik Clayton wrote: > > I meant that any effort you put in is better than none. For example, if > you decide to start producing patches for 4.4 that bring in some > features from -stable (e.g., delayed acks) that's far better than you > not doing it at all. As others have also said. Yup. > Don't feel that because you can't do everything you want to do that you > shouldn't do any of it. If you get the ball rolling, and become known > as *the* place to go for extra patches, you'll find that other people > start sending you additional patches to include. Oh, no. I don't have a problem with starting small. I wasn't born 6'0", after all. I am rather hoping there's a bunch of packrats lurking in hacker@ that might mail me their backports. It'd make a better initial impression. I don't have any pretentions or aspirations of being "the place to go" for backports. If it happens, it happens. > Pretty soon we'll get bored of having people ask "Hey, why aren't these > patches in RELENG_4_4" (or whatever) and we'll corral you in to becoming > a committer so that you can make this an 'official' part of FreeBSD. Only if I get BSD daemon badges for my machines, a BSD sweatshirt or cap, and an "@freebsd.org" mail addy. :-) > > > > So far, I've made three patchfiles that can be applied to 4.2REL and 4.3REL. > > > > Not exactly the repertoire one would need to garner interest and momentum. > > > > > > It's a start. What's the URL? > > > > You're kidding, right? I only started thinking about doing this yesterday! > > The patches are sitting right here, in $(HOME)/projects. > > OK. Well, if you put them up on a web site, we can link to them. If > you can think of appropriate other places on the FreeBSD web site to > mention them then we can do that too. The page is half-built now. If freebsd.org wants to link to the page (or any other BSD sites, for that matter) that's OK with me. Linking to the individual patchfiles pro'lly isn't a good idea. For those that're interested (and have the time), it's at http://www.visi.com/~hawkeyd/freebsd-backports.html for review/critique. It's only a WIP at this point; please don't do anything to publicize it. I'll mail hackers@ again when it's done, for final review/ critique. > N Let the flaming begin! Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 13:26:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 553F837B419; Tue, 11 Dec 2001 13:26:20 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id fBBLN5Z39867; Tue, 11 Dec 2001 16:23:05 -0500 (EST) (envelope-from mwlucas) Date: Tue, 11 Dec 2001 16:23:05 -0500 From: Michael Lucas To: D J Hawkey Jr Cc: Nik Clayton , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011211162304.A39837@blackhelicopters.org> References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011210080032.A4215@canyon.nothing-going-on.org> <20011210152414.A1367@sheol.localdomain> <20011211191403.B82053@canyon.nothing-going-on.org> <20011211150459.A8415@sheol.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211150459.A8415@sheol.localdomain>; from hawkeyd@visi.com on Tue, Dec 11, 2001 at 03:04:59PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Dec 11, 2001 at 03:04:59PM -0600, D J Hawkey Jr wrote: > I am rather hoping there's a bunch of packrats lurking in hacker@ that might > mail me their backports. It'd make a better initial impression. Let me disabuse you of that notion right now. You're it. Most people in -hackers fall into two groups: 1) track -stable 2) track -current You're it. Congrats. Put up what you've got. > Only if I get BSD daemon badges for my machines, a BSD sweatshirt or cap, > and an "@freebsd.org" mail addy. :-) Nope. Just an @freebsd.org mail addy and a coupon for economy-size Maalox. Sorry. Put up what you've got. > For those that're interested (and have the time), it's at > http://www.visi.com/~hawkeyd/freebsd-backports.html > for review/critique. It's only a WIP at this point; please don't do anything > to publicize it. I'll mail hackers@ again when it's done, for final review/ > critique. Oh. Well, okay, you put up what you got. Good start, now let's get some patches up there. :) -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 13:54:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from breg.mc.mpls.visi.com (breg.mc.mpls.visi.com [208.42.156.101]) by hub.freebsd.org (Postfix) with ESMTP id C173C37B416; Tue, 11 Dec 2001 13:54:50 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by breg.mc.mpls.visi.com (Postfix) with ESMTP id 72C9D2D09EF; Tue, 11 Dec 2001 15:54:45 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBBLsiI08882; Tue, 11 Dec 2001 15:54:44 -0600 (CST) (envelope-from hawkeyd) Date: Tue, 11 Dec 2001 15:54:44 -0600 From: D J Hawkey Jr To: Michael Lucas Cc: Nik Clayton , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011211155444.A8723@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011210080032.A4215@canyon.nothing-going-on.org> <20011210152414.A1367@sheol.localdomain> <20011211191403.B82053@canyon.nothing-going-on.org> <20011211150459.A8415@sheol.localdomain> <20011211162304.A39837@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211162304.A39837@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Tue, Dec 11, 2001 at 04:23:05PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Dec 11, at 04:23 PM, Michael Lucas wrote: > > On Tue, Dec 11, 2001 at 03:04:59PM -0600, D J Hawkey Jr wrote: > > I am rather hoping there's a bunch of packrats lurking in hacker@ that might > > mail me their backports. It'd make a better initial impression. > > Let me disabuse you of that notion right now. You're it. Most people > in -hackers fall into two groups: > > 1) track -stable > 2) track -current You're kidding. A whole bunch of folk, all dedicated to an OS, and nobody's got patch archives?? *Sheesh* NOW what'd I get myself into? The wife is gonna kill me. > You're it. Congrats. Put up what you've got. > > > Only if I get BSD daemon badges for my machines, a BSD sweatshirt or cap, > > and an "@freebsd.org" mail addy. :-) > > Nope. Just an @freebsd.org mail addy and a coupon for economy-size > Maalox. Sorry. Put up what you've got. OK, I'll take the addy (what's the convention, initials? Mine are "djhjr"). The freebsd.org mailserver is POP3able, right? But I'll swap the coupons for daemon PC badges. I don't do over-the-counter drugs. All right, all right. A twelve-pack of Guiness. In cans; the bottled stuff is too flat. > > > Good start, now let's get some patches up there. :) That'll be the time-consuming part. Not the posting of 'em, but describing 'em. I want that part to be as concise as possible. You don't mind if a few others weight in, do you? I can spell, but I'd like opinion on the language vis-a-vis the targetted audience. And some legal kinda guy or girl. I don't know if the disclaimer is adequate protection. > Michael Lucas Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 14:13:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (okc-65-31-201-166.mmcable.com [65.31.201.166]) by hub.freebsd.org (Postfix) with SMTP id DF5E837B41B for ; Tue, 11 Dec 2001 14:13:38 -0800 (PST) Received: (qmail 29277 invoked by uid 100); 11 Dec 2001 22:13:36 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15382.34064.301349.155129@guru.mired.org> Date: Tue, 11 Dec 2001 16:13:36 -0600 To: hawkeyd@visi.com Cc: hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux In-Reply-To: <20011211155444.A8723@sheol.localdomain> References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011210080032.A4215@canyon.nothing-going-on.org> <20011210152414.A1367@sheol.localdomain> <20011211191403.B82053@canyon.nothing-going-on.org> <20011211150459.A8415@sheol.localdomain> <20011211162304.A39837@blackhelicopters.org> <20011211155444.A8723@sheol.localdomain> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA v0.42/Python 2.1.1 (freebsd4) From: "Mike Meyer" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG D J Hawkey Jr types: > On Dec 11, at 04:23 PM, Michael Lucas wrote: > > On Tue, Dec 11, 2001 at 03:04:59PM -0600, D J Hawkey Jr wrote: > > > I am rather hoping there's a bunch of packrats lurking in hacker@ that might > > > mail me their backports. It'd make a better initial impression. > > > > Let me disabuse you of that notion right now. You're it. Most people > > in -hackers fall into two groups: > > > > 1) track -stable > > 2) track -current > > You're kidding. A whole bunch of folk, all dedicated to an OS, and nobody's > got patch archives?? *Sheesh* You can find my patch archives at :-) Basically, I submit patches as prs. Those that I consider really important I'll keep around until the PR gets dealt with. I've as yet to have something that was both important enough for me to keep separately and closed without being added to the base code. Why keep it myself when I can get it added to the base system? http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 14:16:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from acc0.visti.net (acc0.visti.net [195.64.225.233]) by hub.freebsd.org (Postfix) with ESMTP id E185C37B43B for ; Tue, 11 Dec 2001 14:16:19 -0800 (PST) Received: from gw0.visti.net (gw0.visti.net [195.64.225.229]) by acc0.visti.net (8.8.8-Elvisti-980428/8.8.8) with ESMTP id AAA19360 for ; Wed, 12 Dec 2001 00:16:17 +0200 (EET) Received: from cscorp.com.ua (Ivanov-gw7r.visti.net [195.64.224.210] (may be forged)) by gw0.visti.net (8.12.1/8.12.1) with ESMTP id fBBLlx7w082230 for ; Wed, 12 Dec 2001 00:16:13 +0200 (EET)?g (envelope-from csc_seminar@cscorp.com.ua) Date: Wed, 12 Dec 2001 00:16:13 +0200 (EET) Message-Id: <200112112216.fBBLlx7w082230@gw0.visti.net> Received: from tanydura [192.168.101.101] by cscorp.com.ua [195.64.224.210] with SMTP (MDaemon.PRO.v5.0.4.R) for ; Tue, 11 Dec 2001 20:20:41 +0000 From: csc_seminar To: freebsd-hackers@freebsd.org Subject: Invitation for seminar. Ïðèãëàøåíèå íà ñåìèíàð Reply-To: csc_seminar@cscorp.com.ua Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1251 X-MDRemoteIP: 192.168.101.101 X-Return-Path: csc_seminar@cscorp.com.ua X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ïðåäñòàâèòåëüñòâî Êîìïàíèè Capital Standard Corporation ïðèãëàøàåò Âàñ ïðèíÿòü ó÷àñòèå â îäíîäíåâíûõ êîíñóëüòàöèîííûõ ñåìèíàðàõ-ïðàêòèêóìàõ äëÿ ýôôåêòèâíîãî è áûñòðîãî ïîâûøåíèÿ êâàëèôèêàöèè ñîòðóäíèêîâ Âàøåé êîìïàíèè Îäíîäíåâíûé êîíñóëüòàöèîííûé ñåìèíàð-ïðàêòèêóì «Áèðæåâàÿ òîðãîâëÿ íà ìåæäóíàðîäíûõ ôèíàíñîâûõ ðûíêàõ. Ïðàêòè÷åñêèå àñïåêòû» Äàòà ïðîâåäåíèÿ: 19 äåêàáðÿ 2001 ãîäà Âðåìÿ ïðîâåäåíèÿ ñåìèíàðà: 9.30-17.30 Ìåñòî ïðîâåäåíèÿ: Èíñòèòóò ìåæäóíàðîäíûõ îòíîøåíèé  ïðîãðàììå ñåìèíàðà: 1. Ñïåêóëÿöèè - êàê ñïîñîá ïðèóìíîæåíèÿ êàïèòàëà: - ×àñòíûå èíâåñòîðû - Êîðïîðàòèâíûå è äðóãèå ó÷àñòíèêè ðûíêà - Ñóììà, äîñòàòî÷íàÿ äëÿ ðàáîòû 2. Èíñòðóìåíòû ìèðîâûõ òîâàðíûõ è ôèíàíñîâûõ ðûíêîâ: - FOREX - ìåæäóíàðîäíûé ðûíîê îáìåíà âàëþò - Ôüþ÷åðñíûå è îïöèîííûå êîíòðàêòû 3. Òåõíîëîãèÿ è ìåõàíèçì áèðæåâûõ è âíåáèðæåâûõ îïåðàöèé: - Çàêîíîäàòåëüíàÿ áàçà, ïðàâèëà è ïðàêòèêà àìåðèêàíñêîé ìîäåëè òîðãîâëè - Âàëþòíûé ðûíîê «spot» - Áèðæåâûå òîðãîâûå ñèñòåìû - Êîìïüþòåðíûå òîðãîâûå ñèñòåìû - Èíôîðìàöèîííûå ñèñòåìû è êîìïüþòåðíûå òåõíîëîãèè ïî îáåñïå÷åíèþ äèëèíãîâûõ îïåðàöèé 4. Êàê «äîòÿíóòüñÿ» äî ðûíêà: - Áðîêåðñêàÿ êîìïàíèÿ - Ïðèíöèïàë (ìàðêåò-ìåéêåð) - Òîðãîâûé ñ÷¸ò - Ìàðæà - Êðåäèòíîå ïëå÷î - Ñîâåðøåíèå ñäåëêè - Ïëþñû è ìèíóñû "èíòåðíåò-òîðãîâëè" - Ïðèáûëüíîñòü îïåðàöèé 5. Ïðîãíîçèðîâàíèå ðûíî÷íûõ òåíäåíöèé: - Òåõíè÷åñêèé àíàëèç - Ôóíäàìåíòàëüíûé àíàëèç - Ïðîôåññèîíàëüíûå êîìïüþòåðíûå ñèñòåìû è ïðîãðàììíîå îáåñïå÷åíèå, èñïîëüçóåìîå â ðàáîòå äèëåðîâ Ñòîèìîñòü ó÷àñòèÿ â ñåìèíàðå: 440 ãðèâåí Äëÿ âòîðîãî è òðåòüåãî ó÷àñòíèêà îò îäíîé êîìïàíèè ñêèäêà – 10%.  ñòîèìîñòü âêëþ÷åíû: îáó÷åíèå è êîíñóëüòàöèè íà ñåìèíàðå, îáåä, êîôå-áðåéêè. Ýêñêëþçèâíûé àëüáîì ìàòåðèàëîâ «Áèðæåâàÿ òîðãîâëÿ íà ìåæäóíàðîäíûõ ôèíàíñîâûõ ðûíêàõ. Ïðàêòè÷åñêèå àñïåêòû», ïîäãîòîâëåííîãî ýêñïåðòàìè ñïåöèàëüíî äëÿ ó÷àñòíèêîâ ñ ó÷¸òîì âñåõ ïîñëåäíèõ èçìåíåíèé è äîïîëíåíèé. Îäíîäíåâíûé êîíñóëüòàöèîííûé ñåìèíàð-ïðàêòèêóì: «Òàìîæåííîå ðåãóëèðîâàíèå âíåøíåýêîíîìè÷åñêîé äåÿòåëüíîñòè» Äàòà ïðîâåäåíèÿ: 21 äåêàáðÿ 2001 ãîäà Âðåìÿ ïðîâåäåíèÿ ñåìèíàðà: 9.30-17.30 Ìåñòî ïðîâåäåíèÿ: Êîíôåðåíö-çàë ãîñòèíèöû «Ñàíêò-Ïåòåðáóðã» Â ïðîãðàììå ñåìèíàðà: Îñîáåííîñòè òàìîæåííîãî çàêîíîäàòåëüñòâà â ñôåðå âíåøíåýêîíîìè÷åñêîé äåÿòåëüíîñòè. Çàêîí Óêðàèíû «Î Òàìîæåííîì òàðèôå Óêðàèíû» îò 5.04.2001 ¹ 2371-²²². Èçìåíåíèÿ è äîïîëíåíèÿ â Çàêîí Óêðàèíû ïî ñîñòîÿíèþ íà 1.12.01. Óêðàèíñêàÿ òîâàðíàÿ íîìåíêëàòóðà âíåøíåýêîíîìè÷åñêîé äåÿòåëüíîñòè. Îñîáåííîñòè òàìîæåííîãî îôîðìëåíèÿ â ðàìêàõ ñîãëàøåíèé î ñâîáîäíîé òîðãîâëå. Ïåðñïåêòèâà ðàçâèòèÿ çîíû ñâîáîäíîé òîðãîâëè. Íîâûå ïðàâèëà ñòðàíû ïðîèñõîæäåíèÿ òîâàðîâ. Ïîðÿäîê ïðèìåíåíèÿ ñåðòèôèêàòîâ CT-1, EUR 1,2. Âîïðîñû êëàññèôèêàöèè òîâàðîâ. Îáçîð íîðìàòèâíûõ äîêóìåíòîâ ÃÒÑÓ ïî âîïðîñàì òàðèôíîãî ðåãóëèðîâàíèÿ ïî ñîñòîÿíèþ íà 1.12.01. Îñîáåííîñòè çàïîëíåíèÿ ÃÒÄ ïðè ðàçëè÷íûõ òàìîæåííûõ ðåæèìàõ. Ëèçèíãîâûå êîíòðàêòû, âðåìåííûé ââîç òîâàðà. Îôîðìëåíèå ÃÒÄ ïî âíåøíåýêîíîìè÷åñêèì äîãîâîðàì ñ ó÷àñòèåì áîëåå äâóõ ñòîðîí. Êðèòåðèè îïðåäåëåíèÿ òàìîæåííûìè îðãàíàìè Óêðàèíû «ãðóïï ðèñêà» (âíåøíåýêîíîìè÷åñêèå îïåðàöèè, êîòîðûå òðåáóþò äåòàëüíîé ïðîâåðêè íà çàêîííîñòü ñäåëêè). Óñòàíîâëåíèå ôàêòîâ òàìîæåííûõ ïðàâîíàðóøåíèé, êëàññèôèêàöèÿ è ïðîöåññóàëüíîå îôîðìëåíèå ôàêòîâ ïðàâîíàðóøåíèé, ñàíêöèè, ïðåäóñìîòðåííûå çàêîíîäàòåëüñòâîì, ïîñëåäñòâèÿ âîçìîæíûå äëÿ ñóáúåêòîâ ÂÝÄ. Ïðàâîâûå îñíîâû äëÿ îñóùåñòâëåíèÿ ìåæäóíàðîäíîé àäìèíèñòðàòèâíîé ïîìîùè â òàìîæåííûõ çîíàõ (ó÷àñòèå Óêðàèíû â ìåæäóíàðîäíûõ êîíâåíöèÿõ ïî òàìîæåííûì âîïðîñàì, äâóõ- è ìíîãîñòîðîííèå ìåæãîñóäàðñòâåííûå äîãîâîðà). Ïîðÿäîê ðåàëèçàöèè êîíâåíöèé, ñîãëàøåíèé, î âçàèìíîé àäìèíèñòðàòèâíîé ïîìîùè â òàìîæåííûõ âîïðîñàõ. Ñòîèìîñòü ó÷àñòèÿ â ñåìèíàðå 570 ãðèâåí Äëÿ âòîðîãî è òðåòüåãî ó÷àñòíèêà îò îäíîé ôèðìû ñêèäêà – 10%.  ñòîèìîñòü âêëþ÷åíû: îáó÷åíèå è êîíñóëüòàöèè íà ñåìèíàðå, îáåä, êîôå-áðåéêè. Ýêñêëþçèâíûé àëüáîì ìàòåðèàëîâ «Òàìîæåííîå ðåãóëèðîâàíèå âíåøíåýêîíîìè÷åñêîé äåÿòåëüíîñòè», ïîäãîòîâëåííîãî ýêñïåðòàìè ñïåöèàëüíî äëÿ ó÷àñòíèêîâ ñ ó÷¸òîì âñåõ ïîñëåäíèõ èçìåíåíèé è äîïîëíåíèé Íàøà êîìïàíèÿ ïðåäëàãàåò òàêóþ óñëóãó êàê ïðîâåäåíèå èíäèâèäóàëüíûõ êîíñóëüòàöèîííûõ ñåìèíàðîâ ïî âûáðàííîé Âàìè òåìàòèêå ó Âàñ â îôèñå. Äëÿ ó÷àñòèÿ â ñåìèíàðå íåîáõîäèìî çàðåãèñòðèðîâàòüñÿ ïî íàøèì òåëåôîíàì è ïîäòâåðäèòü ñâîå ó÷àñòèå îïëàòîé (044) 494 46 58, E-mail: csc_seminar@cscorp.com.ua Ìû ïðèíîñèì ñâîè èçâèíåíèÿ, åñëè ïîäîáíàÿ ðàññûëêà Âàì íå èíòåðåñíà. Óäàëèòü ñâîé àäðåñ èç ñïèñêà ïîäïèñ÷èêîâ Âû ìîæåòå, îòîñëàâ ïèñüìî ïî àäðåñó unsubscribe_sem@cscorp.com.ua To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 14:52: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 5C9DD37B417; Tue, 11 Dec 2001 14:52:03 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id fBBMq1G40232; Tue, 11 Dec 2001 17:52:01 -0500 (EST) (envelope-from mwlucas) Date: Tue, 11 Dec 2001 17:52:01 -0500 From: Michael Lucas To: D J Hawkey Jr Cc: Nik Clayton , hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011211175201.B39837@blackhelicopters.org> References: <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011210080032.A4215@canyon.nothing-going-on.org> <20011210152414.A1367@sheol.localdomain> <20011211191403.B82053@canyon.nothing-going-on.org> <20011211150459.A8415@sheol.localdomain> <20011211162304.A39837@blackhelicopters.org> <20011211155444.A8723@sheol.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211155444.A8723@sheol.localdomain>; from hawkeyd@visi.com on Tue, Dec 11, 2001 at 03:54:44PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Dec 11, 2001 at 03:54:44PM -0600, D J Hawkey Jr wrote: > On Dec 11, at 04:23 PM, Michael Lucas wrote: > NOW what'd I get myself into? The wife is gonna kill me. Well, yes. > > Nope. Just an @freebsd.org mail addy and a coupon for economy-size > > Maalox. Sorry. Put up what you've got. > > OK, I'll take the addy (what's the convention, initials? Mine are "djhjr"). > The freebsd.org mailserver is POP3able, right? Sorry, I've misspoke here: A lot of people volunteer to do this sort of thing, and never really carry it through. This sadly happens often enough that we don't give out the email addresses until there's actual stuff that gets out there, maintained for a while, and integrated into the project. My sincere apologies for implying anything else. (The following is in no way about you in particular, Hawk; it's just an unfair characterization we're stuck with, because it seems to fit the facts.) Unfortunately, many people start things and never finish them, or don't see them through. Since @freebsd.org is one of the few things we have to offer committers, we don't hand them out to people who are starting things. (If more people actually carried through, I'm sure this would change.) I started doing things is 1999, but got a commit bit last month. Admittedly, most of those didn't go directly into the project. Yours, I suspect, will get picked up quickly if you can coordinate it well. > You don't mind if a few others weight in, do you? I can spell, but I'd like > opinion on the language vis-a-vis the targetted audience. And some legal > kinda guy or girl. I don't know if the disclaimer is adequate protection. Seriously, it's your project. Involve as many people as you want. You are in change. (That's the hardest thing to get used to with this project.) -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 15: 6:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brea.mc.mpls.visi.com (brea.mc.mpls.visi.com [208.42.156.100]) by hub.freebsd.org (Postfix) with ESMTP id 8293237B416 for ; Tue, 11 Dec 2001 15:06:55 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by brea.mc.mpls.visi.com (Postfix) with ESMTP id CB5E22DDE32; Tue, 11 Dec 2001 17:06:53 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBBN6r209303; Tue, 11 Dec 2001 17:06:53 -0600 (CST) (envelope-from hawkeyd) Date: Tue, 11 Dec 2001 17:06:53 -0600 From: D J Hawkey Jr To: Michael Lucas Cc: hackers@freebsd.org Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011211170653.A9288@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011210080032.A4215@canyon.nothing-going-on.org> <20011210152414.A1367@sheol.localdomain> <20011211191403.B82053@canyon.nothing-going-on.org> <20011211150459.A8415@sheol.localdomain> <20011211162304.A39837@blackhelicopters.org> <20011211155444.A8723@sheol.localdomain> <20011211175201.B39837@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211175201.B39837@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Tue, Dec 11, 2001 at 05:52:01PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Dec 11, at 05:52 PM, Michael Lucas wrote: > > > OK, I'll take the addy (what's the convention, initials? Mine are "djhjr"). > > The freebsd.org mailserver is POP3able, right? > > Sorry, I've misspoke here: > > A lot of people volunteer to do this sort of thing, and never really > carry it through. This sadly happens often enough that we don't give > out the email addresses until there's actual stuff that gets out > there, maintained for a while, and integrated into the project. My > sincere apologies for implying anything else. > > [SNIP] Hey, it's OK. I understand. Don't sweat it. > Michael Lucas Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 15:54:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 5145537B405 for ; Tue, 11 Dec 2001 15:54:53 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 0085B46E; Tue, 11 Dec 2001 23:54:43 +0000 (GMT) Date: Tue, 11 Dec 2001 23:54:43 +0000 From: Josef Karthauser To: Wayne Pascoe Cc: freebsd-hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011211235443.A32932@tao.org.uk> Mail-Followup-To: Josef Karthauser , Wayne Pascoe , freebsd-hackers@FreeBSD.org References: <20011211120104.28477.qmail@web21101.mail.yahoo.com> <20011211195313.E27214@tao.org.uk> <86u1uxzfzn.fsf@pan.home.penguinpowered.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <86u1uxzfzn.fsf@pan.home.penguinpowered.org.uk>; from freebsd@molemanarmy.com on Tue, Dec 11, 2001 at 07:58:04PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 11, 2001 at 07:58:04PM +0000, Wayne Pascoe wrote: > Josef Karthauser writes: >=20 > > It is probably a one man job if that man knows the kernel inside > > and out in these areas, and has the time and energy to see it > > through. I'd suggest that you find a much much smaller area to > > work on yourself for now though. (Take a look in the PR database > > for ideas of where to start). >=20 > What is the PR database of which you speak and where can I find it? I > am looking for a project to work on in my free time.=20 http://www.freebsd.org/support.html#gnats Joe --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwWnMMACgkQXVIcjOaxUBYfTwCdEBJxFiHF5NPblIN4fL+NsQW0 tNwAn0SGI+e9Ebzbx4tOaGOzI2Wr4s9W =e8QC -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 17: 4:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 1793F37B419; Tue, 11 Dec 2001 17:04:22 -0800 (PST) Received: from rac4.wam.umd.edu (IDENT:root@rac4.wam.umd.edu [128.8.10.144]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA17504; Tue, 11 Dec 2001 20:04:20 -0500 (EST) Received: from rac4.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id UAA29187; Tue, 11 Dec 2001 20:04:20 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA29183; Tue, 11 Dec 2001 20:04:20 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Tue, 11 Dec 2001 20:04:20 -0500 (EST) From: Kenneth Wayne Culver To: "Andrew R. Reiter" Cc: Poul-Henning Kamp , hackers@FreeBSD.ORG Subject: Re: Junior Kernel hacker task: Floppy driver mode handling. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I was thinking about looking into it, but I won't have time to start until the 18th. if you wanna do it, go for it, and I'll wait my turn for the next thing I can do in the kernel. :-D Ken On Tue, 11 Dec 2001, Andrew R. Reiter wrote: > > Someone already doing this? If not, I'm down. > > On Tue, 11 Dec 2001, Poul-Henning Kamp wrote: > > : > :There exists a patch for adding a mode to our floppy driver to > :add DEC RX50 media handling. > : > :The crucial part of this is the addition of this line: > : { 10,2,0xFF,0x10,80, 800,1,FDC_300KBPS,1,0x2E,1 }, /* 400K DEC RX50 */ > : > :But if one examines the fd.c driver, one cannot help but notice that the > :handling of densities is a bit convoluted, to put it mildly. > : > :I'm looking for a volounteer to do this, it is a quite simple job and > :I am quite sure that practically everybody has the hardware they need to > :do this :-) > : > :Cleaning it up consists of the following steps: > : > :1. Define a new set of (bitmap) macros to distinguish the drive type: > : #define FD_3S 0x0001 /* 3.5" single density */ > : #define FD_5S 0x0002 /* 5.25" single density */ > : ... > : And use these instead of the FD_1200 and similar in > : struct fd_data->type. > : > :2. Augment the struct fd_type with two new fields: > : int minor; /* minor device encoding */ > : int drives; /* bitmap of compatible drives (FD_[35][SD]) */ > : And fill these fields out in the fd_types[NUMTYPES] array. > : Add a termination entry at the end of the table so the > : NUMTYPES, NUMDENS, and FD_%d[5_25] #defines can be eliminated. > : > :3. Change the _clone code to use the new "minor" field instead of > : the private table it uses now. (Eliminate and avoid any > : use of NUMTYPES, NUMDENS and FD_%d[5_25]). > : > :4. Change the code in Fdopen to examine the "drives" field in the > : fd_types[] array instead of the hardcoded switch. (Eliminate > : and avoid any use of NUMTYPES, NUMDENS and and FD_%d[5_25]); > : > :5. Remove any other use of NUMTYPES, NUMDENS and FD_%d[5_25] > : > :6. Add the "rx50" entry from above to the table to show how simple > : that is now. > : > :7. Make it possible to define a new mode from userland with an ioctl. > : (hint: instead of the index, put a pointer to the struct fd_type into > : the fd_data structure.) > : > :Preferably, send one patch per step rather than one huge patch since that > :will make reviewing easier. > : > :First volounteer to send me email gets the assignment. > : > :-- > :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > :phk@FreeBSD.ORG | TCP/IP since RFC 956 > :FreeBSD committer | BSD since 4.3-tahoe > :Never attribute to malice what can adequately be explained by incompetence. > : > :To Unsubscribe: send mail to majordomo@FreeBSD.org > :with "unsubscribe freebsd-hackers" in the body of the message > : > > -- > Andrew R. Reiter > arr@watson.org > arr@FreeBSD.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 17:17:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from haggis.it.ca (haggis.it.ca [216.126.86.9]) by hub.freebsd.org (Postfix) with ESMTP id CA9F037B417 for ; Tue, 11 Dec 2001 17:17:26 -0800 (PST) Received: (from paul@localhost) by haggis.it.ca (8.11.6/8.11.6) id fBC1HNe00557; Tue, 11 Dec 2001 20:17:23 -0500 (EST) (envelope-from paul) Date: Tue, 11 Dec 2001 20:17:23 -0500 From: Paul Chvostek To: D J Hawkey Jr Cc: hackers@FreeBSD.ORG Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011211201723.A97414@mail.it.ca> References: <20011210155924.A1542@sheol.localdomain> <20011210173206.A1795@sheol.localdomain> <20011211061406.C35343@blackhelicopters.org> <20011211054818.A5471@sheol.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211054818.A5471@sheol.localdomain>; from hawkeyd@visi.com on Tue, Dec 11, 2001 at 05:48:19AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Dec 11, 2001 at 05:48:19AM -0600, D J Hawkey Jr wrote: > > No challenge necessary. I, too, believe the general attitude is "Go for it.". > So I'm going to. It won't be much to look at initially - maybe ever - but > I'll bring it up and see what happens. It'll take a few days, but I'll post > an "It's here." when it's here. BTW, am I allowed to use the daemon mascot? I currently have the domains mybsd.(com|net|org|biz). If you'd like the patch database to be associated with any or all of those domains, I'd be happy to oblige. (The hostname "patch.mybsd.com" is pretty. ;> ) I've been trying to figure out what to do with these for quite a while. Perhaps this is an opportunity. > Ack. Don't do that. Sooner or later, the economy will pick up again, I'll > get myself the badly-needed job I lost, and my play-time will once again > be reduced by a factor of four. The last thing I'll need then is any kind > of publicity. Ah, but with fame can come fortune. Once you're widely known as The Man for customizing FreeBSD, you can double your consulting rates, thereby doubling the free time you can allocate to the library. ;-) p -- Paul Chvostek Operations / Development / Abuse / Whatever vox: +1 416 598-0000 IT Canada http://www.it.ca/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 17:25:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from breg.mc.mpls.visi.com (breg.mc.mpls.visi.com [208.42.156.101]) by hub.freebsd.org (Postfix) with ESMTP id C3D1837B405 for ; Tue, 11 Dec 2001 17:25:10 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by breg.mc.mpls.visi.com (Postfix) with ESMTP id C5CEE2D0A3A; Tue, 11 Dec 2001 19:25:09 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBC1P8v09859; Tue, 11 Dec 2001 19:25:08 -0600 (CST) (envelope-from hawkeyd) Date: Tue, 11 Dec 2001 19:25:08 -0600 From: D J Hawkey Jr To: Paul Chvostek Cc: hackers@freebsd.org Subject: Re: Tangent for discussion: FreeBSD performs worse that Linux Message-ID: <20011211192508.A9844@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011210155924.A1542@sheol.localdomain> <20011210173206.A1795@sheol.localdomain> <20011211061406.C35343@blackhelicopters.org> <20011211054818.A5471@sheol.localdomain> <20011211201723.A97414@mail.it.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211201723.A97414@mail.it.ca>; from paul@it.ca on Tue, Dec 11, 2001 at 08:17:23PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Dec 11, at 08:17 PM, Paul Chvostek wrote: > > I currently have the domains mybsd.(com|net|org|biz). If you'd > like the patch database to be associated with any or all of those > domains, I'd be happy to oblige. (The hostname "patch.mybsd.com" > is pretty. ;> ) Indeed. Quite clever. I'll consider this, and get back to you. > On Tue, Dec 11, 2001 at 05:48:19AM -0600, D J Hawkey Jr wrote: > > > > Ack. Don't do that. Sooner or later, the economy will pick up again, I'll > > get myself the badly-needed job I lost, and my play-time will once again > > be reduced by a factor of four. The last thing I'll need then is any kind > > of publicity. > > Ah, but with fame can come fortune. Once you're widely known as The Man > for customizing FreeBSD, you can double your consulting rates, thereby > doubling the free time you can allocate to the library. ;-) Heh. I'll consider this, too. > p Thanks, Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 18:41:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id C6B9137B405; Tue, 11 Dec 2001 18:41:32 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id 46A9A786E3; Wed, 12 Dec 2001 13:11:25 +1030 (CST) Date: Wed, 12 Dec 2001 13:11:25 +1030 From: Greg Lehey To: Terry Lambert , Hiten Pandya Cc: Alfred Perlstein , hackers@FreeBSD.org, Peter Wemm , current@FreeBSD.ORG Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011212131125.A82733@monorchid.lemis.com> References: <3C1613AD.53C45B3@mindspring.com> <20011211102645.46795.qmail@web21110.mail.yahoo.com> <20011211093550.D4BF638CC@overcee.netplex.com.au> <20011211102645.46795.qmail@web21110.mail.yahoo.com> <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <3C15AC5A.44BFD2BD@mindspring.com> <20011211183001.B67986@monorchid.lemis.com> <3C15CD07.6D5FC2E7@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C1613AD.53C45B3@mindspring.com> <20011211102645.46795.qmail@web21110.mail.yahoo.com> <3C15CD07.6D5FC2E7@mindspring.com> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday, 11 December 2001 at 1:08:23 -0800, Terry Lambert wrote: > Greg Lehey wrote: >>> FS porting to FreeBSD is actually pretty trivial(*), though some >>> transactioning changes to the FreeBSD VFS layer consumers (the >>> system calls and NFS server code) would be necessary to make >>> the journal roll-back function correctly, following a failure. >>> >>> (*) Trivial: meaning grunt work is required; not necessarily an >>> indicator of the amount of work, only the intellectual effort >>> required for the job >> >> Considering that the current UFS implementation didn't need to be >> ported, and people are still working on the details, I think that this >> is a highly misleading statement. > > The current UFS has a number of issues which make it non-trivial; > it was, in effect, a port; here is the short list: > > > > Live code always has issues, particularly if you are trying to > pound a round peg into a square hole (hence Kirk taking up the > task of a redesign). Of course. But you're missing the point: ufs is *not* a port, it has been with BSD since the beginning. There is a similar list of items for JFS which would need to be addressed, with the additional issue of the fact that it was not designed for FreeBSD. > I think that everyone saying "Ut oh! SCARY!" gives people the wrong > idea, and scares off potential contributors in these areas. I'm not saying that. I'm saying that it's non-trivial, which I suppose is what you mean when you say "where are the patches?". As I said, I'm quite happy to help people port JFS2 to FreeBSD. On Tuesday, 11 December 2001 at 2:26:45 -0800, Hiten Pandya wrote: >> [... Hiten want's to GPL'ify FreeBSD ...] > > hi, > first of all, i would like to clear of some point which have been > taken wrongly. > > o My Intentions were never to GPL'ify FreeBSD :-) Agreed, I don't think anybody thought that. > o The reason i started this discussion was because > i think JFS/JFS2 would be a nice addition to > FreeBSD like the rest of the other filesystems. > > o The JFS does _not_ have to be root, and even if > people were to download it because it is GPL'ed, > the size of the filesystem is only around 1.0MB If we port JFS2, it will be relatively trivial to have it as the root file system too. > o It is hard to Port AIX or OS/2 based code, but we > have to agree that, BSD Users were meant to take > that kind of challenges, have taken before It's probably easier to port AIX based code than OS/2 or Linux based code. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 19:42:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 5EE5237B41C; Tue, 11 Dec 2001 19:42:26 -0800 (PST) Received: from pool0608.cvx22-bradley.dialup.earthlink.net ([209.179.200.98] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16E0Ho-00024G-00; Tue, 11 Dec 2001 19:42:24 -0800 Message-ID: <3C16D226.F169C43D@mindspring.com> Date: Tue, 11 Dec 2001 19:42:30 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: Hiten Pandya , Alfred Perlstein , hackers@FreeBSD.org, Peter Wemm , current@FreeBSD.ORG Subject: Re: [SUGGESTION] - JFS for FreeBSD References: <3C1613AD.53C45B3@mindspring.com> <20011211102645.46795.qmail@web21110.mail.yahoo.com> <20011211093550.D4BF638CC@overcee.netplex.com.au> <20011211102645.46795.qmail@web21110.mail.yahoo.com> <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <3C15AC5A.44BFD2BD@mindspring.com> <20011211183001.B67986@monorchid.lemis.com> <3C15CD07.6D5FC2E7@mindspring.com> <20011212131125.A82733@monorchid.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greg Lehey wrote: > Of course. But you're missing the point: ufs is *not* a port, it has > been with BSD since the beginning. There is a similar list of items > for JFS which would need to be addressed, with the additional issue of > the fact that it was not designed for FreeBSD. I maintain that the FreeBSD UFS *is* a port of the Heidemann implementation from the FICUS project, which had to be done because certain files were claimed to be "contaminated" with USL IP, and were removed as part of the USL/UCB settlement (6 key files from 5 subsystems, which they thought we couldn't rewrite from scratch in time to be a competitive threat). I also maintain that the most difficult thing is getting the list of items, and, with the information from the UFS work in hand, the JFS specific items not on that list are trivial (there are exactly two items, in fact: log roll forward/backward, and transaction abort). > > I think that everyone saying "Ut oh! SCARY!" gives people the wrong > > idea, and scares off potential contributors in these areas. > > I'm not saying that. I'm saying that it's non-trivial, which I > suppose is what you mean when you say "where are the patches?". As I > said, I'm quite happy to help people port JFS2 to FreeBSD. I ported the entire GFS user space tools set, sans two, to FreeBSD in about 2 hours. If FreeBSD had the necessary hardware drivers for shared disks, I would have finished the two that I didn't do, and then I would have gone to Frys, bought the necessary controllers, disk, and two scratch boxes, and finished porting the whole damn thing. I think I could have it all up and running in about 4 weeks, assuming the Linux implementation actually works for more than one machine, and my test machines were configured dual boot for Linux/FreeBSD. Unlike IBM, the GFS people have indicated a willingness to bend on the license issue. When I say "trivial", I mean "trivial", as the term is used in physics or mathematics: a well understood operation that can be performed rote, and does not require significant original thinking to perform. When I say "where are the patches?" I mean "that's an incredibly stupid idea, given the license, and you aren't going to get me to do that work without paying me, so you might as well send patches -- do the work yourself -- because you are going to have a hell of a time getting buy-in from anyone clued enough to do the work for you". > If we port JFS2, it will be relatively trivial to have it as the root > file system too. Only, you will never be able to build a firewall, router, or other product that ships with it statically linked into the kernel, since that would violate the terms of the GPL (additional restrictions, and linked code not being GPL'ed). What good is the damn thing, if the only people who can use it are big site admins who build their own kernels, and never expect to sell their company to anyone (or are prepared to recompile all the kernels on all their machines, should the company ever sell, since they can't transfer ownership of a FreeBSD kernel with GPL'ed code in it directly, without violating the license)? RMS has indicated a willingness to sue people distributing bipartite distributions, where the linking is delayed until installation to work around the letter of the GPL. Given his religious convictions, I can't see him *not*. Factor that into your decision. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 21:13:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 693CB37B416; Tue, 11 Dec 2001 21:13:49 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fBC5Dla83799; Tue, 11 Dec 2001 22:13:48 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fBC5DkM33078; Tue, 11 Dec 2001 22:13:46 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200112120513.fBC5DkM33078@harmony.village.org> To: Danny Braniss Subject: Re: irq Cc: Terry Lambert , Bernd Walter , Mike Smith , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 11 Dec 2001 12:22:15 +0200." References: Date: Tue, 11 Dec 2001 22:13:46 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message Danny Braniss writes: : Q: are all interrupt handlers for the shared irq called, or only the : 'correct' one? You can't tell which card really interrupted. All of them are called. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 21:16:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 4370537B405; Tue, 11 Dec 2001 21:16:21 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fBC5GJa83812; Tue, 11 Dec 2001 22:16:19 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fBC5GJM33101; Tue, 11 Dec 2001 22:16:19 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200112120516.fBC5GJM33101@harmony.village.org> To: Terry Lambert Subject: Re: irq Cc: Danny Braniss , Bernd Walter , Mike Smith , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 11 Dec 2001 06:14:45 PST." <3C1614D5.B5C3B4C5@mindspring.com> References: <3C1614D5.B5C3B4C5@mindspring.com> Date: Tue, 11 Dec 2001 22:16:19 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3C1614D5.B5C3B4C5@mindspring.com> Terry Lambert writes: : Some cards do not have a hardware "I caused an interrupt" register, : and use a differential (e.g. ring head vs. tail inequal after : interrupt) to tell if there is work to do. If these cards were to : share interrupts, then they most likely do work every interrupt, : and less work per interrupt, then would otherwise be the case (i.e. : it would defeat hardware interrupt coelescing thresholds, among : other things). No such PCI cards can exists. The PCI spec requires that interrupt sharing work. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 21:18:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 7B0D237B419; Tue, 11 Dec 2001 21:18:08 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fBC5I7a83822; Tue, 11 Dec 2001 22:18:07 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fBC5I7M33121; Tue, 11 Dec 2001 22:18:07 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200112120518.fBC5I7M33121@harmony.village.org> To: Poul-Henning Kamp Subject: Re: Junior Kernel hacker task: Floppy driver mode handling. Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 11 Dec 2001 17:51:04 +0100." <31764.1008089464@critter.freebsd.dk> References: <31764.1008089464@critter.freebsd.dk> Date: Tue, 11 Dec 2001 22:18:06 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <31764.1008089464@critter.freebsd.dk> Poul-Henning Kamp writes: : 6. Add the "rx50" entry from above to the table to show how simple : that is now. But rx50 also needs some extra processing to handle the software interleave. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 21:58:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f240.law8.hotmail.com [216.33.241.240]) by hub.freebsd.org (Postfix) with ESMTP id 229C737B41C; Tue, 11 Dec 2001 21:58:38 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 11 Dec 2001 21:58:37 -0800 Received: from 209.52.193.196 by lw8fd.law8.hotmail.msn.com with HTTP; Wed, 12 Dec 2001 05:58:37 GMT X-Originating-IP: [209.52.193.196] From: "Craig R" To: hackers@freebsd.org, current@freebsd.org Subject: Re: [SUGGESTION] - JFS for FreeBSD Date: Tue, 11 Dec 2001 21:58:37 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 12 Dec 2001 05:58:37.0977 (UTC) FILETIME=[0AD83890:01C182D2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I think I would rather see people tweaking the heck out of the existing UFS filesystem and implementing new ways of getting it to go faster. Implementing a whole new filesystem would probably take a lot of work, and the performance wouldn't be much better anyways. IMHO, people interested in making a filesystem faster should stick with UFS. FreeBSD should not do what Linux does, which is make a whole bunch of different filesystems that all suck in a different way. This is an opinion and should be taken as such, not an insult to those that like the whole JFS idea. -Craig _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 22:45:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 0B8F237B405 for ; Tue, 11 Dec 2001 22:45:47 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fBC6i7j48172; Wed, 12 Dec 2001 07:44:08 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: Junior Kernel hacker task: Floppy driver mode handling. In-Reply-To: Your message of "Tue, 11 Dec 2001 22:18:06 MST." <200112120518.fBC5I7M33121@harmony.village.org> Date: Wed, 12 Dec 2001 07:44:07 +0100 Message-ID: <48170.1008139447@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200112120518.fBC5I7M33121@harmony.village.org>, Warner Losh writes: >In message <31764.1008089464@critter.freebsd.dk> Poul-Henning Kamp writes: >: 6. Add the "rx50" entry from above to the table to show how simple >: that is now. > >But rx50 also needs some extra processing to handle the software >interleave. I know. That doesn't change the fact that our floppy density code needs a rewrite. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 22:50:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id 912DF37B416; Tue, 11 Dec 2001 22:50:23 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id DD78B786E6; Wed, 12 Dec 2001 17:20:21 +1030 (CST) Date: Wed, 12 Dec 2001 17:20:21 +1030 From: Greg Lehey To: Terry Lambert Cc: Hiten Pandya , Alfred Perlstein , hackers@FreeBSD.org, Peter Wemm , current@FreeBSD.ORG Subject: Re: [SUGGESTION] - JFS for FreeBSD Message-ID: <20011212172021.L82733@monorchid.lemis.com> References: <20011211093550.D4BF638CC@overcee.netplex.com.au> <20011211102645.46795.qmail@web21110.mail.yahoo.com> <20011210220153.50612.qmail@web21102.mail.yahoo.com> <20011210161410.L92148@elvis.mu.org> <3C15AC5A.44BFD2BD@mindspring.com> <20011211183001.B67986@monorchid.lemis.com> <3C15CD07.6D5FC2E7@mindspring.com> <20011212131125.A82733@monorchid.lemis.com> <3C16D226.F169C43D@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C16D226.F169C43D@mindspring.com> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday, 11 December 2001 at 19:42:30 -0800, Terry Lambert wrote: > Greg Lehey wrote: >> Of course. But you're missing the point: ufs is *not* a port, it has >> been with BSD since the beginning. There is a similar list of items >> for JFS which would need to be addressed, with the additional issue of >> the fact that it was not designed for FreeBSD. > > I maintain that the FreeBSD UFS *is* a port of the Heidemann > implementation from the FICUS project, which had to be done because > certain files were claimed to be "contaminated" with USL IP, and > were removed as part of the USL/UCB settlement (6 key files from 5 > subsystems, which they thought we couldn't rewrite from scratch in > time to be a competitive threat). Which files? Did they require adapting to a different environment? > I also maintain that the most difficult thing is getting the list of > items, and, with the information from the UFS work in hand, the JFS > specific items not on that list are trivial (there are exactly two > items, in fact: log roll forward/backward, and transaction abort). I'd expect these to be the easiest parts, since they don't have too much to do with the rest of the system. One of the issues with Linux is that the interface to the rest of the system, and I don't expect these parts to have much interfacing to do. >>> I think that everyone saying "Ut oh! SCARY!" gives people the wrong >>> idea, and scares off potential contributors in these areas. >> >> I'm not saying that. I'm saying that it's non-trivial, which I >> suppose is what you mean when you say "where are the patches?". As I >> said, I'm quite happy to help people port JFS2 to FreeBSD. > > I ported the entire GFS user space tools set, sans two, to FreeBSD in > about 2 hours. I expect the user space tools for JFS2 to be pretty straightforward too. >> If we port JFS2, it will be relatively trivial to have it as the root >> file system too. > > Only, you will never be able to build a firewall, router, or other > product that ships with it statically linked into the kernel, since > that would violate the terms of the GPL (additional restrictions, > and linked code not being GPL'ed). Fine, so we load the module. What's your point? > What good is the damn thing, if the only people who can use it are > ... Well, I suppose it'll still be good for them. Maybe. > RMS has indicated a willingness to sue people distributing bipartite > distributions, where the linking is delayed until installation to > work around the letter of the GPL. Given his religious convictions, > I can't see him *not*. Factor that into your decision. You want me personally to get him to agree that loading modules at boot time does not violate the GPL? Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 23:10:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 0982D37B41B for ; Tue, 11 Dec 2001 23:10:27 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fBC7ANa84131; Wed, 12 Dec 2001 00:10:24 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fBC7AMM33690; Wed, 12 Dec 2001 00:10:22 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200112120710.fBC7AMM33690@harmony.village.org> To: Poul-Henning Kamp Subject: Re: Junior Kernel hacker task: Floppy driver mode handling. Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 12 Dec 2001 07:44:07 +0100." <48170.1008139447@critter.freebsd.dk> References: <48170.1008139447@critter.freebsd.dk> Date: Wed, 12 Dec 2001 00:10:22 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <48170.1008139447@critter.freebsd.dk> Poul-Henning Kamp writes: : >: 6. Add the "rx50" entry from above to the table to show how simple : >: that is now. : > : >But rx50 also needs some extra processing to handle the software : >interleave. : : I know. : : That doesn't change the fact that our floppy density code needs a : rewrite. No it doesn't. Just wanted whoever was doing it to know... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 11 23:20:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wiuu.kiev.ua (wiuu.kiev.ua [62.244.58.126]) by hub.freebsd.org (Postfix) with ESMTP id B5D2537B447 for ; Tue, 11 Dec 2001 23:19:58 -0800 (PST) Received: from localhost (kao@localhost) by wiuu.kiev.ua (8.9.3/8.9.3) with SMTP id JAA21961; Wed, 12 Dec 2001 09:19:09 +0200 (EET) (envelope-from kao@wiuu.kiev.ua) Date: Wed, 12 Dec 2001 09:19:08 +0200 (EET) From: Alexey Klimov Reply-To: Alexey Klimov To: Poul-Henning Kamp Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: Junior Kernel hacker task: Floppy driver mode handling. In-Reply-To: <48170.1008139447@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 12 Dec 2001, Poul-Henning Kamp wrote: > In message <200112120518.fBC5I7M33121@harmony.village.org>, Warner Losh writes: > >In message <31764.1008089464@critter.freebsd.dk> Poul-Henning Kamp writes: > >: 6. Add the "rx50" entry from above to the table to show how simple > >: that is now. > > > >But rx50 also needs some extra processing to handle the software > >interleave. > > I know. > > That doesn't change the fact that our floppy density code needs a > rewrite. Hi, I have patch for reading/writing DEC RX50 floppy for old 2.2.7-RELEASE, which I made severel years ago. I found two problems then. The first is interliave, and the second is that the first logical track is mapped to the last physical. I may look through my archives, port this patch to CURRNET and send it to you. Alexey Klimov > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 0:48:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 82E5B37B405; Wed, 12 Dec 2001 00:48:31 -0800 (PST) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.33 #1) id 16E53w-0001PP-00; Wed, 12 Dec 2001 10:48:24 +0200 Received: from localhost ([127.0.0.1] helo=pampa.cs.huji.ac.il ident=danny) by pampa.cs.huji.ac.il with esmtp (Exim 3.22 #2) id 16E53w-000BIB-00; Wed, 12 Dec 2001 10:48:24 +0200 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Warner Losh Cc: Danny Braniss , Terry Lambert , Bernd Walter , Mike Smith , freebsd-hackers@FreeBSD.ORG, danny@cs.huji.ac.il Subject: Re: irq In-Reply-To: Message from Warner Losh of "Tue, 11 Dec 2001 22:13:46 MST." <200112120513.fBC5DkM33078@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Dec 2001 10:48:24 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > In message Danny Braniss writes: > : Q: are all interrupt handlers for the shared irq called, or only the > : 'correct' one? > > You can't tell which card really interrupted. All of them are called. > > Warner let me see if i can summarise: 1- irq are shared by definition. 2- all drivers at/in the same irq are called. 3- it's the driver's responsability to do the 'right thing' or in simpler terms, not to screw things up. I fixed the meteor, so that on interrupt checks if there is anything to do, and if not just returns, btw, on interrups time very little is done. my testing was done so: host A ran an X application that does the video grabbing. - with local display, all ok. - with display on host B, via fast ethernet, the adaptec complained. the meteor complained. after some card shuffling: the adaptec is ok. the meteor hardly complains - IMHO it should not, but it's very low count < .01%. btw, host A is Pentium III/450MHz. Dell GX1, with 128M memory. ah, and thanks to all for explaining the darker sides of irq. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 1:43:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21106.mail.yahoo.com (web21106.mail.yahoo.com [216.136.227.108]) by hub.freebsd.org (Postfix) with SMTP id BD82937B417 for ; Wed, 12 Dec 2001 01:43:10 -0800 (PST) Message-ID: <20011212094310.13502.qmail@web21106.mail.yahoo.com> Received: from [62.254.0.5] by web21106.mail.yahoo.com via HTTP; Wed, 12 Dec 2001 01:43:10 PST Date: Wed, 12 Dec 2001 01:43:10 -0800 (PST) From: Hiten Pandya Subject: Re: [SUGGESTION] - JFS for FreeBSD [VOTE] To: Greg Lehey Cc: hackers@FreeBSD.org In-Reply-To: <20011212172021.L82733@monorchid.lemis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, as i said also before, my intentions were never to cause havoc on the mailing list. :-) In simple terms, what i am saying is, the people who would like to port the JFS file system, should put a +1 in their next message and -1 if they dont like to port JFS. Then, i will count the votes, and if +1 outweighs -1, then i will try to gether developers who can help me in this task, and try to finish it by Sept. 2002. BUT, if -1 outweighs +1, then i will cancel the project and live it for my spare time, and will not go around asking everyone about it... OR, another way of doing this would be to, just try and get this JFS porting done by people who would like to do it (including me), and then put it on the FreeBSD site. AND, then we will see which company/corporate would like to use the GPL version of a FreeBSD FileSystem. Suppose, if there are very less, we abandon the project and forget about it. In that way, there would be no hassle. Only people who would like to port this File System should put a +1 in their next reply or -1 if they do not agree with porting JFS. Thanks. =Hiten = ===== -Hiten, Thank You, Yours Sincerely, Hiten Pandya, __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 3: 2:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 980CF37B41B; Wed, 12 Dec 2001 03:02:34 -0800 (PST) Received: from pool0012.cvx22-bradley.dialup.earthlink.net ([209.179.198.12] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16E79R-0001n6-00; Wed, 12 Dec 2001 03:02:13 -0800 Message-ID: <3C17393B.8297E824@mindspring.com> Date: Wed, 12 Dec 2001 03:02:19 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Danny Braniss , Bernd Walter , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: irq References: <3C1614D5.B5C3B4C5@mindspring.com> <200112120516.fBC5GJM33101@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <3C1614D5.B5C3B4C5@mindspring.com> Terry Lambert writes: > : Some cards do not have a hardware "I caused an interrupt" register, > : and use a differential (e.g. ring head vs. tail inequal after > : interrupt) to tell if there is work to do. If these cards were to > : share interrupts, then they most likely do work every interrupt, > : and less work per interrupt, then would otherwise be the case (i.e. > : it would defeat hardware interrupt coelescing thresholds, among > : other things). > > No such PCI cards can exists. The PCI spec requires that interrupt > sharing work. ??? How is setting a local register when an interrupt is triggered antithetical to such cards working? I know of several network cards where I've personally hacked on the driver that have such a register. It's not possbile to take a shared interrupt and not run the ISR, but it's possible for the ISR to check the register and decide on that basis, rather than on data availability, that it will or will not do work. I think that everyone now "gets" that PCI interrupts are like signals, in that they are persistant conditions, so more than one card asserting them doesn't change the fact that "an interrupt" was asserted, and there's no way to tell _from the interrupt_ which cards did or did not assert it in the first place. But we are talking about an extra hardware register on the card that the card sets when it asserts an interrupt, so an ISR can look to ask the card "did you assert an interrupt?" and decide not to process if the answer is "no". The Tigon II interrupt sharing in fact depends on this, or when you had two Tigon II cards, you migh spend the rest of eternity in the ISR. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 6:10:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 8BF4837B41B; Wed, 12 Dec 2001 06:10:17 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.0/8.11.0) with UUCP id fBCEA0U82114; Wed, 12 Dec 2001 15:10:01 +0100 (CET) Received: from mail.cicely.de (cicely20.cicely.de [10.1.1.22]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id fBCE9ftx014021; Wed, 12 Dec 2001 15:09:41 +0100 (CET)?g (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0/8.11.0) with ESMTP id fBCE9eW08266; Wed, 12 Dec 2001 15:09:40 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.6/8.11.6) id fBCE9UD18410; Wed, 12 Dec 2001 15:09:30 +0100 (CET) (envelope-from ticso) Date: Wed, 12 Dec 2001 15:09:28 +0100 From: Bernd Walter To: Terry Lambert Cc: Warner Losh , Danny Braniss , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: irq Message-ID: <20011212150928.F15654@cicely8.cicely.de> References: <3C1614D5.B5C3B4C5@mindspring.com> <200112120516.fBC5GJM33101@harmony.village.org> <3C17393B.8297E824@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C17393B.8297E824@mindspring.com> User-Agent: Mutt/1.3.23i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Dec 12, 2001 at 03:02:19AM -0800, Terry Lambert wrote: > How is setting a local register when an interrupt is triggered > antithetical to such cards working? I know of several network > cards where I've personally hacked on the driver that have such > a register. > > It's not possbile to take a shared interrupt and not run the ISR, > but it's possible for the ISR to check the register and decide on > that basis, rather than on data availability, that it will or will > not do work. > > I think that everyone now "gets" that PCI interrupts are like > signals, in that they are persistant conditions, so more than one > card asserting them doesn't change the fact that "an interrupt" > was asserted, and there's no way to tell _from the interrupt_ > which cards did or did not assert it in the first place. But we > are talking about an extra hardware register on the card that the > card sets when it asserts an interrupt, so an ISR can look to ask > the card "did you assert an interrupt?" and decide not to process > if the answer is "no". > > The Tigon II interrupt sharing in fact depends on this, or when > you had two Tigon II cards, you migh spend the rest of eternity in > the ISR. I never understood why the PCI-bus is not a interupt vector design. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 6:28:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id A987B37B416; Wed, 12 Dec 2001 06:28:32 -0800 (PST) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.33 #1) id 16EAMz-0002Ye-00; Wed, 12 Dec 2001 16:28:25 +0200 Received: from localhost ([127.0.0.1] helo=pampa.cs.huji.ac.il ident=danny) by pampa.cs.huji.ac.il with esmtp (Exim 3.22 #2) id 16EAMz-000BZR-00; Wed, 12 Dec 2001 16:28:25 +0200 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Bernd Walter Cc: Terry Lambert , Warner Losh , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: irq In-Reply-To: Message from Bernd Walter of "Wed, 12 Dec 2001 15:09:28 +0100." <20011212150928.F15654@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Dec 2001 16:28:25 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I never understood why the PCI-bus is not a interupt vector design. > probably because it was DEC's idea ... danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 6:30:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 3084637B417; Wed, 12 Dec 2001 06:30:48 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fBCEUMX74834; Wed, 12 Dec 2001 15:30:22 +0100 (CET) (envelope-from wkb) Date: Wed, 12 Dec 2001 15:30:22 +0100 From: Wilko Bulte To: Danny Braniss Cc: Bernd Walter , Terry Lambert , Warner Losh , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: irq Message-ID: <20011212153022.B74758@freebie.xs4all.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from danny@cs.huji.ac.il on Wed, Dec 12, 2001 at 04:28:25PM +0200 X-OS: FreeBSD 4.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Dec 12, 2001 at 04:28:25PM +0200, Danny Braniss wrote: > > > I never understood why the PCI-bus is not a interupt vector design. > > > probably because it was DEC's idea ... I thought it was Intel's idea? -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 8:24:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 303D537B417 for ; Wed, 12 Dec 2001 08:24:22 -0800 (PST) Received: (from jkh@localhost) by winston.freebsd.org (8.11.6/8.11.6) id fBCGNuY52543; Wed, 12 Dec 2001 08:23:56 -0800 (PST) (envelope-from jkh) Date: Wed, 12 Dec 2001 08:23:56 -0800 (PST) From: Jordan Hubbard Message-Id: <200112121623.fBCGNuY52543@winston.freebsd.org> To: hackers@freebsd.org Subject: NFS: How to make FreeBSD fall on its face in one easy step Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It came up in a meeting today at Apple just how fragile the BSD NFS implementation was before significant work was put in to stabilizing it, and in that discussion came up a little test tool written originally by Avie Tevanian and subsequently improved by one of the folks here. This tool basically tries to do everything it can (legally) to confuse an NFS server. It seeks around, does I/O to and truncates/changes the size of a test file, all while doing everything it can to detect data corruption or other signs of misbehavior which might result from out-of-order replies or any other previously-observed NFS pathology. Very few NFS implementations apparently survive this test and FreeBSD's is no exception. The sources are provided below, courtesy of Avie, for the education and enjoyment(?) of anyone who's motivated to play with (or even pretends to understand) NFS. Usage: cc fsx.c -o fsx ./fsx /some/nfs/mounted/scratchfile [ ** kaboom! ** ] I'm also trying to determine which of the fixes Apple has made to NFS might be adapted to FreeBSD, something which is made more difficult by the fact that much of the code was taken straight from 4.4 Lite some time back and both operating systems have diverged significantly since then. Anyone really keen on investigating this further themselves on it can also go to http://www.opensource.apple.com/projects/darwin and register themselves online (it's easy) to access the Darwin CVS repository, the module in question being "xnu" (the Darwin kernel). Thanks. - Jordan /* * Copyright (C) 1991, NeXT Computer, Inc. All Rights Reserverd. * * File: fsx.c * Author: Avadis Tevanian, Jr. * * File system exerciser. * * Rewritten 8/98 by Conrad Minshall. */ #include #include #ifdef _UWIN # include # include # include # include # define MAP_FILE 0 #else # include #endif #include #include #include #include #include #include #include #include #include #include #include #define NUMPRINTCOLUMNS 32 /* # columns of data to print on each line */ /* * A log entry is an operation and a bunch of arguments. */ struct log_entry { int operation; int args[3]; }; #define LOGSIZE 1000 struct log_entry oplog[LOGSIZE]; /* the log */ int logptr = 0; /* current position in log */ int logcount = 0; /* total ops */ /* * Define operations */ #define OP_READ 1 #define OP_WRITE 2 #define OP_TRUNCATE 3 #define OP_CLOSEOPEN 4 #define OP_MAPREAD 5 #define OP_MAPWRITE 6 #define OP_SKIPPED 7 #ifndef PAGE_SIZE #define PAGE_SIZE 4096 #endif #define PAGE_MASK (PAGE_SIZE - 1) char *original_buf; /* a pointer to the original data */ char *good_buf; /* a pointer to the correct data */ char *temp_buf; /* a pointer to the current data */ char *fname; /* name of our test file */ int fd; /* fd for our test file */ off_t file_size = 0; off_t biggest = 0; char state[256]; unsigned long testcalls = 0; /* calls to function "test" */ unsigned long simulatedopcount = 0; /* -b flag */ int closeprob = 0; /* -c flag */ int debug = 0; /* -d flag */ unsigned long debugstart = 0; /* -D flag */ unsigned long maxfilelen = 256 * 1024; /* -l flag */ int sizechecks = 1; /* -n flag disables them */ int maxoplen = 64 * 1024; /* -o flag */ int quiet = 0; /* -q flag */ unsigned long progressinterval = 0; /* -p flag */ int readbdy = 1; /* -r flag */ int style = 0; /* -s flag */ int truncbdy = 1; /* -t flag */ int writebdy = 1; /* -w flag */ long monitorstart = -1; /* -m flag */ long monitorend = -1; /* -m flag */ int lite = 0; /* -L flag */ long numops = -1; /* -N flag */ int randomoplen = 1; /* -O flag disables it */ int seed = 1; /* -S flag */ int mapped_writes = 1; /* -W flag disables */ int mapped_reads = 1; /* -R flag disables it */ int fsxgoodfd = 0; FILE * fsxlogf = NULL; int badoff = -1; int closeopen = 0; void prt(char *fmt, ...) { va_list args; va_start(args, fmt); vfprintf(stdout, fmt, args); if (fsxlogf) vfprintf(fsxlogf, fmt, args); va_end(args); } void prterr(char *prefix) { prt("%s%s%s\n", prefix, prefix ? ": " : "", strerror(errno)); } void log4(int operation, int arg0, int arg1, int arg2) { struct log_entry *le; le = &oplog[logptr]; le->operation = operation; if (closeopen) le->operation = ~ le->operation; le->args[0] = arg0; le->args[1] = arg1; le->args[2] = arg2; logptr++; logcount++; if (logptr >= LOGSIZE) logptr = 0; } void logdump(void) { int i, count, down; struct log_entry *lp; prt("LOG DUMP (%d total operations):\n", logcount); if (logcount < LOGSIZE) { i = 0; count = logcount; } else { i = logptr; count = LOGSIZE; } for ( ; count > 0; count--) { int opnum; opnum = i+1 + (logcount/LOGSIZE)*LOGSIZE; prt("%d(%d mod 256): ", opnum, opnum%256); lp = &oplog[i]; if ((closeopen = lp->operation < 0)) lp->operation = ~ lp->operation; switch (lp->operation) { case OP_MAPREAD: prt("MAPREAD\t0x%x thru 0x%x\t(0x%x bytes)", lp->args[0], lp->args[0] + lp->args[1] - 1, lp->args[1]); if (badoff >= lp->args[0] && badoff < lp->args[0] + lp->args[1]) prt("\t***RRRR***"); break; case OP_MAPWRITE: prt("MAPWRITE 0x%x thru 0x%x\t(0x%x bytes)", lp->args[0], lp->args[0] + lp->args[1] - 1, lp->args[1]); if (badoff >= lp->args[0] && badoff < lp->args[0] + lp->args[1]) prt("\t******WWWW"); break; case OP_READ: prt("READ\t0x%x thru 0x%x\t(0x%x bytes)", lp->args[0], lp->args[0] + lp->args[1] - 1, lp->args[1]); if (badoff >= lp->args[0] && badoff < lp->args[0] + lp->args[1]) prt("\t***RRRR***"); break; case OP_WRITE: prt("WRITE\t0x%x thru 0x%x\t(0x%x bytes)", lp->args[0], lp->args[0] + lp->args[1] - 1, lp->args[1]); if (lp->args[0] > lp->args[2]) prt(" HOLE"); else if (lp->args[0] + lp->args[1] > lp->args[2]) prt(" EXTEND"); if ((badoff >= lp->args[0] || badoff >=lp->args[2]) && badoff < lp->args[0] + lp->args[1]) prt("\t***WWWW"); break; case OP_TRUNCATE: down = lp->args[0] < lp->args[1]; prt("TRUNCATE %s\tfrom 0x%x to 0x%x", down ? "DOWN" : "UP", lp->args[1], lp->args[0]); if (badoff >= lp->args[!down] && badoff < lp->args[!!down]) prt("\t******WWWW"); break; case OP_SKIPPED: prt("SKIPPED (no operation)"); break; default: prt("BOGUS LOG ENTRY (operation code = %d)!", lp->operation); } if (closeopen) prt("\n\t\tCLOSE/OPEN"); prt("\n"); i++; if (i == LOGSIZE) i = 0; } } void save_buffer(char *buffer, off_t bufferlength, int fd) { off_t ret; ssize_t byteswritten; if (fd <= 0 || bufferlength == 0) return; if (bufferlength > SSIZE_MAX) { prt("fsx flaw: overflow in save_buffer\n"); exit(67); } if (lite) { off_t size_by_seek = lseek(fd, (off_t)0, L_XTND); if (size_by_seek == (off_t)-1) prterr("save_buffer: lseek eof"); else if (bufferlength > size_by_seek) { warn("save_buffer: .fsxgood file too short... will save 0x%qx bytes instead of 0x%qx\n", (unsigned long long)size_by_seek, (unsigned long long)bufferlength); bufferlength = size_by_seek; } } ret = lseek(fd, (off_t)0, SEEK_SET); if (ret == (off_t)-1) prterr("save_buffer: lseek 0"); byteswritten = write(fd, buffer, (size_t)bufferlength); if (byteswritten != bufferlength) { if (byteswritten == -1) prterr("save_buffer write"); else warn("save_buffer: short write, 0x%x bytes instead of 0x%qx\n", (unsigned)byteswritten, (unsigned long long)bufferlength); } } void report_failure(int status) { logdump(); if (fsxgoodfd) { if (good_buf) { save_buffer(good_buf, file_size, fsxgoodfd); prt("Correct content saved for comparison\n"); prt("(maybe hexdump \"%s\" vs \"%s.fsxgood\")\n", fname, fname); } close(fsxgoodfd); } exit(status); } #define short_at(cp) ((unsigned short)((*((unsigned char *)(cp)) << 8) | \ *(((unsigned char *)(cp)) + 1))) void check_buffers(unsigned offset, unsigned size) { unsigned char c, t; unsigned i = 0; unsigned n = 0; unsigned op = 0; unsigned bad = 0; if (bcmp(good_buf + offset, temp_buf, size) != 0) { prt("READ BAD DATA: offset = 0x%x, size = 0x%x\n", offset, size); prt("OFFSET\tGOOD\tBAD\tRANGE\n"); while (size > 0) { c = good_buf[offset]; t = temp_buf[i]; if (c != t) { if (n == 0) { bad = short_at(&temp_buf[i]); prt("0x%5x\t0x%04x\t0x%04x", offset, short_at(&good_buf[offset]), bad); op = temp_buf[offset & 1 ? i+1 : i]; } n++; badoff = offset; } offset++; i++; size--; } if (n) { prt("\t0x%5x\n", n); if (bad) prt("operation# (mod 256) for the bad data may be %u\n", ((unsigned)op & 0xff)); else prt("operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops\n"); } else prt("????????????????\n"); report_failure(110); } } void check_size(void) { struct stat statbuf; off_t size_by_seek; if (fstat(fd, &statbuf)) { prterr("check_size: fstat"); statbuf.st_size = -1; } size_by_seek = lseek(fd, (off_t)0, L_XTND); if (file_size != statbuf.st_size || file_size != size_by_seek) { prt("Size error: expected 0x%qx stat 0x%qx seek 0x%qx\n", (unsigned long long)file_size, (unsigned long long)statbuf.st_size, (unsigned long long)size_by_seek); report_failure(120); } } void check_trunc_hack(void) { struct stat statbuf; ftruncate(fd, (off_t)0); ftruncate(fd, (off_t)100000); fstat(fd, &statbuf); if (statbuf.st_size != (off_t)100000) { prt("no extend on truncate! not posix!\n"); exit(130); } ftruncate(fd, 0); } void doread(unsigned offset, unsigned size) { off_t ret; unsigned iret; offset -= offset % readbdy; if (size == 0) { if (!quiet && testcalls > simulatedopcount) prt("skipping zero size read\n"); log4(OP_SKIPPED, OP_READ, offset, size); return; } if (size + offset > file_size) { if (!quiet && testcalls > simulatedopcount) prt("skipping seek/read past end of file\n"); log4(OP_SKIPPED, OP_READ, offset, size); return; } log4(OP_READ, offset, size, 0); if (testcalls <= simulatedopcount) return; if (!quiet && (progressinterval && testcalls % progressinterval == 0 || debug && (monitorstart == -1 || offset + size > monitorstart && (monitorend == -1 || offset <= monitorend)))) prt("%lu read\t0x%x thru\t0x%x\t(0x%x bytes)\n", testcalls, offset, offset + size - 1, size); ret = lseek(fd, (off_t)offset, SEEK_SET); if (ret == (off_t)-1) { prterr("doread: lseek"); report_failure(140); } iret = read(fd, temp_buf, size); if (iret != size) { if (iret == -1) prterr("doread: read"); else prt("short read: 0x%x bytes instead of 0x%x\n", iret, size); report_failure(141); } check_buffers(offset, size); } void domapread(unsigned offset, unsigned size) { unsigned pg_offset; unsigned map_size; char *p; offset -= offset % readbdy; if (size == 0) { if (!quiet && testcalls > simulatedopcount) prt("skipping zero size read\n"); log4(OP_SKIPPED, OP_MAPREAD, offset, size); return; } if (size + offset > file_size) { if (!quiet && testcalls > simulatedopcount) prt("skipping seek/read past end of file\n"); log4(OP_SKIPPED, OP_MAPREAD, offset, size); return; } log4(OP_MAPREAD, offset, size, 0); if (testcalls <= simulatedopcount) return; if (!quiet && (progressinterval && testcalls % progressinterval == 0 || debug && (monitorstart == -1 || offset + size > monitorstart && (monitorend == -1 || offset <= monitorend)))) prt("%lu mapread\t0x%x thru\t0x%x\t(0x%x bytes)\n", testcalls, offset, offset + size - 1, size); pg_offset = offset & PAGE_MASK; map_size = pg_offset + size; if ((p = (char *)mmap(0, map_size, PROT_READ, MAP_FILE, fd, (off_t)(offset - pg_offset))) == (char *)-1) { prterr("domapread: mmap"); report_failure(190); } memcpy(temp_buf, p + pg_offset, size); if (munmap(p, map_size) != 0) { prterr("domapread: munmap"); report_failure(191); } check_buffers(offset, size); } void gendata(char *original_buf, char *good_buf, unsigned offset, unsigned size) { while (size--) { good_buf[offset] = testcalls % 256; if (offset % 2) good_buf[offset] += original_buf[offset]; offset++; } } void dowrite(unsigned offset, unsigned size) { off_t ret; unsigned iret; offset -= offset % writebdy; if (size == 0) { if (!quiet && testcalls > simulatedopcount) prt("skipping zero size write\n"); log4(OP_SKIPPED, OP_WRITE, offset, size); return; } log4(OP_WRITE, offset, size, file_size); gendata(original_buf, good_buf, offset, size); if (file_size < offset + size) { if (file_size < offset) bzero(good_buf + file_size, offset - file_size); file_size = offset + size; if (lite) { warn("Lite file size bug in fsx!"); report_failure(149); } } if (testcalls <= simulatedopcount) return; if (!quiet && (progressinterval && testcalls % progressinterval == 0 || debug && (monitorstart == -1 || offset + size > monitorstart && (monitorend == -1 || offset <= monitorend)))) prt("%lu write\t0x%x thru\t0x%x\t(0x%x bytes)\n", testcalls, offset, offset + size - 1, size); ret = lseek(fd, (off_t)offset, SEEK_SET); if (ret == (off_t)-1) { prterr("dowrite: lseek"); report_failure(150); } iret = write(fd, good_buf + offset, size); if (iret != size) { if (iret == -1) prterr("dowrite: write"); else prt("short write: 0x%x bytes instead of 0x%x\n", iret, size); report_failure(151); } } void domapwrite(unsigned offset, unsigned size) { unsigned pg_offset; unsigned map_size; off_t cur_filesize; char *p; offset -= offset % writebdy; if (size == 0) { if (!quiet && testcalls > simulatedopcount) prt("skipping zero size write\n"); log4(OP_SKIPPED, OP_MAPWRITE, offset, size); return; } cur_filesize = file_size; log4(OP_MAPWRITE, offset, size, 0); gendata(original_buf, good_buf, offset, size); if (file_size < offset + size) { if (file_size < offset) bzero(good_buf + file_size, offset - file_size); file_size = offset + size; if (lite) { warn("Lite file size bug in fsx!"); report_failure(200); } } if (testcalls <= simulatedopcount) return; if (!quiet && (progressinterval && testcalls % progressinterval == 0 || debug && (monitorstart == -1 || offset + size > monitorstart && (monitorend == -1 || offset <= monitorend)))) prt("%lu mapwrite\t0x%x thru\t0x%x\t(0x%x bytes)\n", testcalls, offset, offset + size - 1, size); if (file_size > cur_filesize) { if (ftruncate(fd, file_size) == -1) { prterr("domapwrite: ftruncate"); exit(201); } } pg_offset = offset & PAGE_MASK; map_size = pg_offset + size; if ((p = (char *)mmap(0, map_size, PROT_READ | PROT_WRITE, MAP_FILE | MAP_SHARED, fd, (off_t)(offset - pg_offset))) == (char *)-1) { prterr("domapwrite: mmap"); report_failure(202); } memcpy(p + pg_offset, good_buf + offset, size); if (msync(p, map_size, 0) != 0) { prterr("domapwrite: msync"); report_failure(203); } if (munmap(p, map_size) != 0) { prterr("domapwrite: munmap"); report_failure(204); } } void dotruncate(unsigned size) { int oldsize = file_size; size -= size % truncbdy; if (size > biggest) { biggest = size; if (!quiet && testcalls > simulatedopcount) prt("truncating to largest ever: 0x%x\n", size); } log4(OP_TRUNCATE, size, (unsigned)file_size, 0); if (size > file_size) bzero(good_buf + file_size, size - file_size); file_size = size; if (testcalls <= simulatedopcount) return; if (progressinterval && testcalls % progressinterval == 0 || debug && (monitorstart == -1 || monitorend == -1 || size <= monitorend)) prt("%lu trunc\tfrom 0x%x to 0x%x\n", testcalls, oldsize, size); if (ftruncate(fd, (off_t)size) == -1) { prt("ftruncate1: %x\n", size); prterr("dotruncate: ftruncate"); report_failure(160); } } void writefileimage() { ssize_t iret; if (lseek(fd, (off_t)0, SEEK_SET) == (off_t)-1) { prterr("writefileimage: lseek"); report_failure(171); } iret = write(fd, good_buf, file_size); if ((off_t)iret != file_size) { if (iret == -1) prterr("writefileimage: write"); else prt("short write: 0x%x bytes instead of 0x%qx\n", iret, (unsigned long long)file_size); report_failure(172); } if (lite ? 0 : ftruncate(fd, file_size) == -1) { prt("ftruncate2: %qx\n", (unsigned long long)file_size); prterr("writefileimage: ftruncate"); report_failure(173); } } void docloseopen(void) { if (testcalls <= simulatedopcount) return; if (debug) prt("%lu close/open\n", testcalls); if (close(fd)) { prterr("docloseopen: close"); report_failure(180); } fd = open(fname, O_RDWR, 0); if (fd < 0) { prterr("docloseopen: open"); report_failure(181); } } void test(void) { unsigned long offset; unsigned long size = maxoplen; unsigned long rv = random(); unsigned long op = rv % (3 + !lite + mapped_writes); /* turn off the map read if necessary */ if (op == 2 && !mapped_reads) op = 0; if (simulatedopcount > 0 && testcalls == simulatedopcount) writefileimage(); testcalls++; closeopen = (rv >> 3) < (1 << 28) / closeprob; if (debugstart > 0 && testcalls >= debugstart) debug = 1; if (!quiet && testcalls < simulatedopcount && testcalls % 100000 == 0) prt("%lu...\n", testcalls); /* * READ: op = 0 * WRITE: op = 1 * MAPREAD: op = 2 * TRUNCATE: op = 3 * MAPWRITE: op = 3 or 4 */ if (lite ? 0 : op == 3 && (style & 1) == 0) /* vanilla truncate? */ dotruncate(random() % maxfilelen); else { if (randomoplen) size = random() % (maxoplen+1); if (lite ? 0 : op == 3) dotruncate(size); else { offset = random(); if (op == 1 || op == (lite ? 3 : 4)) { offset %= maxfilelen; if (offset + size > maxfilelen) size = maxfilelen - offset; if (op != 1) domapwrite(offset, size); else dowrite(offset, size); } else { if (file_size) offset %= file_size; else offset = 0; if (offset + size > file_size) size = file_size - offset; if (op != 0) domapread(offset, size); else doread(offset, size); } } } if (sizechecks && testcalls > simulatedopcount) check_size(); if (closeopen) docloseopen(); } void cleanup(sig) int sig; { if (sig) prt("signal %d\n", sig); prt("testcalls = %lu\n", testcalls); exit(sig); } void usage(void) { fprintf(stdout, "usage: %s", "fsx [-dnqLOW] [-b opnum] [-c Prob] [-l flen] [-m start:end] [-o oplen] [-p progressinterval] [-r readbdy] [-s style] [-t truncbdy] [-w writebdy] [-D startingop] [-N numops] [-P dirpath] [-S seed] fname\n\ -b opnum: beginning operation number (default 1)\n\ -c P: 1 in P chance of file close+open at each op (default infinity)\n\ -d: debug output for all operations\n\ -l flen: the upper bound on file size (default 262144)\n\ -m startop:endop: monitor (print debug output) specified byte range (default 0:infinity)\n\ -n: no verifications of file size\n\ -o oplen: the upper bound on operation size (default 65536)\n\ -p progressinterval: debug output at specified operation interval\n\ -q: quieter operation\n\ -r readbdy: 4096 would make reads page aligned (default 1)\n\ -s style: 1 gives smaller truncates (default 0)\n\ -t truncbdy: 4096 would make truncates page aligned (default 1)\n\ -w writebdy: 4096 would make writes page aligned (default 1)\n\ -D startingop: debug output starting at specified operation\n\ -L: fsxLite - no file creations & no file size changes\n\ -N numops: total # operations to do (default infinity)\n\ -O: use oplen (see -o flag) for every op (default random)\n\ -P: save .fsxlog and .fsxgood files in dirpath (default ./)\n\ -S seed: for random # generator (default 1) 0 gets timestamp\n\ -W: mapped write operations DISabled\n\ -R: read() system calls only (mapped reads disabled)\n\ fname: this filename is REQUIRED (no default)\n"); exit(90); } int getnum(char *s, char **e) { int ret = -1; *e = (char *) 0; ret = strtol(s, e, 0); if (*e) switch (**e) { case 'b': case 'B': ret *= 512; *e = *e + 1; break; case 'k': case 'K': ret *= 1024; *e = *e + 1; break; case 'm': case 'M': ret *= 1024*1024; *e = *e + 1; break; case 'w': case 'W': ret *= 4; *e = *e + 1; break; } return (ret); } int main(int argc, char **argv) { int i, style, ch; char *endp; char goodfile[1024]; char logfile[1024]; goodfile[0] = 0; logfile[0] = 0; setvbuf(stdout, (char *)0, _IOLBF, 0); /* line buffered stdout */ while ((ch = getopt(argc, argv, "b:c:dl:m:no:p:qr:s:t:w:D:LN:OP:RS:W")) != EOF) switch (ch) { case 'b': simulatedopcount = getnum(optarg, &endp); if (!quiet) fprintf(stdout, "Will begin at operation %ld\n", simulatedopcount); if (simulatedopcount == 0) usage(); simulatedopcount -= 1; break; case 'c': closeprob = getnum(optarg, &endp); if (!quiet) fprintf(stdout, "Chance of close/open is 1 in %d\n", closeprob); if (closeprob <= 0) usage(); break; case 'd': debug = 1; break; case 'l': maxfilelen = getnum(optarg, &endp); if (maxfilelen <= 0) usage(); break; case 'm': monitorstart = getnum(optarg, &endp); if (monitorstart < 0) usage(); if (!endp || *endp++ != ':') usage(); monitorend = getnum(endp, &endp); if (monitorend < 0) usage(); if (monitorend == 0) monitorend = -1; /* aka infinity */ debug = 1; case 'n': sizechecks = 0; break; case 'o': maxoplen = getnum(optarg, &endp); if (maxoplen <= 0) usage(); break; case 'p': progressinterval = getnum(optarg, &endp); if (progressinterval < 0) usage(); break; case 'q': quiet = 1; break; case 'r': readbdy = getnum(optarg, &endp); if (readbdy <= 0) usage(); break; case 's': style = getnum(optarg, &endp); if (style < 0 || style > 1) usage(); break; case 't': truncbdy = getnum(optarg, &endp); if (truncbdy <= 0) usage(); break; case 'w': writebdy = getnum(optarg, &endp); if (writebdy <= 0) usage(); break; case 'D': debugstart = getnum(optarg, &endp); if (debugstart < 1) usage(); break; case 'L': lite = 1; break; case 'N': numops = getnum(optarg, &endp); if (numops < 0) usage(); break; case 'O': randomoplen = 0; break; case 'P': strncpy(goodfile, optarg, sizeof(goodfile)); strcat(goodfile, "/"); strncpy(logfile, optarg, sizeof(logfile)); strcat(logfile, "/"); break; case 'R': mapped_reads = 0; break; case 'S': seed = getnum(optarg, &endp); if (seed == 0) seed = time(0) % 10000; if (!quiet) fprintf(stdout, "Seed set to %d\n", seed); if (seed < 0) usage(); break; case 'W': mapped_writes = 0; if (!quiet) fprintf(stdout, "mapped writes DISABLED\n"); break; default: usage(); /* NOTREACHED */ } argc -= optind; argv += optind; if (argc != 1) usage(); fname = argv[0]; signal(SIGHUP, cleanup); signal(SIGINT, cleanup); signal(SIGPIPE, cleanup); signal(SIGALRM, cleanup); signal(SIGTERM, cleanup); signal(SIGXCPU, cleanup); signal(SIGXFSZ, cleanup); signal(SIGVTALRM, cleanup); signal(SIGUSR1, cleanup); signal(SIGUSR2, cleanup); initstate(seed, state, 256); setstate(state); fd = open(fname, O_RDWR|(lite ? 0 : O_CREAT|O_TRUNC), 0666); if (fd < 0) { prterr(fname); exit(91); } strncat(goodfile, fname, 256); strcat (goodfile, ".fsxgood"); fsxgoodfd = open(goodfile, O_RDWR|O_CREAT|O_TRUNC, 0666); if (fsxgoodfd < 0) { prterr(goodfile); exit(92); } strncat(logfile, fname, 256); strcat (logfile, ".fsxlog"); fsxlogf = fopen(logfile, "w"); if (fsxlogf == NULL) { prterr(logfile); exit(93); } if (lite) { off_t ret; file_size = maxfilelen = lseek(fd, (off_t)0, L_XTND); if (file_size == (off_t)-1) { prterr(fname); warn("main: lseek eof"); exit(94); } ret = lseek(fd, (off_t)0, SEEK_SET); if (ret == (off_t)-1) { prterr(fname); warn("main: lseek 0"); exit(95); } } original_buf = (char *) malloc(maxfilelen); for (i = 0; i < maxfilelen; i++) original_buf[i] = random() % 256; good_buf = (char *) malloc(maxfilelen); bzero(good_buf, maxfilelen); temp_buf = (char *) malloc(maxoplen); bzero(temp_buf, maxoplen); if (lite) { /* zero entire existing file */ ssize_t written; written = write(fd, good_buf, (size_t)maxfilelen); if (written != maxfilelen) { if (written == -1) { prterr(fname); warn("main: error on write"); } else warn("main: short write, 0x%x bytes instead of 0x%x\n", (unsigned)written, maxfilelen); exit(98); } } else check_trunc_hack(); while (numops == -1 || numops--) test(); if (close(fd)) { prterr("close"); report_failure(99); } prt("All operations completed A-OK!\n"); exit(0); return 0; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 9:25:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251]) by hub.freebsd.org (Postfix) with ESMTP id 8CD7E37B416 for ; Wed, 12 Dec 2001 09:25:37 -0800 (PST) Received: from hunkular.glarp.com (localhost [127.0.0.1]) by hunkular.glarp.com (8.11.6/8.11.6) with ESMTP id fBCHPa100189 for ; Wed, 12 Dec 2001 10:25:36 -0700 (MST) (envelope-from huntting@hunkular.glarp.com) Message-Id: <200112121725.fBCHPa100189@hunkular.glarp.com> To: freebsd-hackers@FreeBSD.ORG Subject: closeing files in detach() In-Reply-To: Your message of "Tue, 11 Dec 2001 13:37:24 MST." <200112112037.fBBKbOM30189@harmony.village.org> Date: Wed, 12 Dec 2001 10:25:36 -0700 From: Brad Huntting Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG There's a mention in the FBSD hacking guide that a detach() routine for a device driver can forcably close all open descriptors for its device before it unloads. How does one do this? brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 10:13:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id F036237B416 for ; Wed, 12 Dec 2001 10:13:39 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBCIJP100888; Wed, 12 Dec 2001 10:19:26 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112121819.fBCIJP100888@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bernd Walter Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: irq In-reply-to: Your message of "Wed, 12 Dec 2001 15:09:28 +0100." <20011212150928.F15654@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Dec 2001 10:19:25 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I never understood why the PCI-bus is not a interupt vector design. The way the story goes, it wasn't until the last minute that the initial PCI working group realised that they'd forgotten to do something about interrupts, and so the gross hack that we're now stuck with was implemented. It might be more realistic to say that PCI tries to discourage the use of interrupts, and hardware vendors haven't really gotten the message. You should look at recent PCI revisions, however, and the MSI (message-signalled interrupt) mechanism which, if implemented widely, will solve at least some of the major problems with PCI and interrupts. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 10:27:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 28CD737B419; Wed, 12 Dec 2001 10:27:34 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fBCIRWa86654; Wed, 12 Dec 2001 11:27:32 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fBCIRUM37234; Wed, 12 Dec 2001 11:27:31 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200112121827.fBCIRUM37234@harmony.village.org> To: Terry Lambert Subject: Re: irq Cc: Danny Braniss , Bernd Walter , Mike Smith , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 12 Dec 2001 03:02:19 PST." <3C17393B.8297E824@mindspring.com> References: <3C17393B.8297E824@mindspring.com> <3C1614D5.B5C3B4C5@mindspring.com> <200112120516.fBC5GJM33101@harmony.village.org> Date: Wed, 12 Dec 2001 11:27:30 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3C17393B.8297E824@mindspring.com> Terry Lambert writes: : How is setting a local register when an interrupt is triggered : antithetical to such cards working? I know of several network : cards where I've personally hacked on the driver that have such : a register. ... I was tired and confused when I read your message. I thought you were describing the lance chips. Re-reading it now that I'm less tired shows I was in error. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 10:44: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id C1C8437B416; Wed, 12 Dec 2001 10:44:04 -0800 (PST) Received: from pool0253.cvx21-bradley.dialup.earthlink.net ([209.179.192.253] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16EEM6-0000tU-00; Wed, 12 Dec 2001 10:43:47 -0800 Message-ID: <3C17A568.C165AE01@mindspring.com> Date: Wed, 12 Dec 2001 10:43:52 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Danny Braniss , Bernd Walter , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: irq References: <3C17393B.8297E824@mindspring.com> <3C1614D5.B5C3B4C5@mindspring.com> <200112120516.fBC5GJM33101@harmony.village.org> <200112121827.fBCIRUM37234@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Warner Losh wrote: > I was tired and confused when I read your message. I thought you were > describing the lance chips. No problem... I've fallen victim to that same thing myself. As I'm sure people will attest at great volume... 8^). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 10:49:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 362D337B423; Wed, 12 Dec 2001 10:49:36 -0800 (PST) Received: from pool0253.cvx21-bradley.dialup.earthlink.net ([209.179.192.253] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16EERi-0001T5-00; Wed, 12 Dec 2001 10:49:35 -0800 Message-ID: <3C17A6C4.FDBDE16C@mindspring.com> Date: Wed, 12 Dec 2001 10:49:40 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Bernd Walter , freebsd-hackers@FreeBSD.ORG Subject: Re: irq References: <200112121819.fBCIJP100888@mass.dis.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Smith wrote: > It might be more realistic to say that PCI tries to discourage the use of > interrupts, and hardware vendors haven't really gotten the message. 8^). That's because there is no more important task for your CPU to do than to poll devices to see if they need to do I/O; what the heck are these "program" things, anyway, and what exactly is their relevence to electrical engineering, again? > You should look at recent PCI revisions, however, and the MSI > (message-signalled interrupt) mechanism which, if implemented widely, > will solve at least some of the major problems with PCI and interrupts. Thanks for the pointer; I haven't been following PCI standards recently, except for speed and size extensions. It looks like it's time to look at them yet again. Do you know if this is going to be mandatory for PCI-X devices? I don't think it will be very widely used until it's required. 8^(. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 11:15:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f20.law9.hotmail.com [64.4.9.20]) by hub.freebsd.org (Postfix) with ESMTP id EC63D37B416; Wed, 12 Dec 2001 11:15:26 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 12 Dec 2001 11:15:26 -0800 Received: from 24.9.137.53 by lw9fd.law9.hotmail.msn.com with HTTP; Wed, 12 Dec 2001 19:15:26 GMT X-Originating-IP: [24.9.137.53] From: "Chuck T." To: freebsd-small@freebsd.org, freebsd-hackers@freebsd.org Subject: help with loadable module & PicoBSD Date: Wed, 12 Dec 2001 11:15:26 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 12 Dec 2001 19:15:26.0928 (UTC) FILETIME=[5B333500:01C18341] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm trying to write an ISA device driver from scratch and I'm also trying to make it a kernel loadable to make my debugging life easier. I started with /usr/share/examples/kld/cdev and have modified it by adding the following: static int xxx_isa_probe(device_t dev) { int ret = ENXIO; device_printf(dev,"xxx_isa_probe() called.\n"); if(device_get_unit(dev) == 0) { ret = 0; } return ret; } static int xxx_isa_attach(device_t dev) { device_printf(dev,"xxx_isa_attach() called.\n"); return 0; } static int xxx_isa_detach(device_t dev) { device_printf(dev,"xxx_isa_detach() called.\n"); return 0; } static struct isa_pnp_id xxx_ids[] = { { 0, NULL } }; static device_method_t xxx_isa_methods[] = { /* Device interface */ DEVMETHOD(device_probe, xxx_isa_probe), DEVMETHOD(device_attach, xxx_isa_attach), DEVMETHOD(device_detach, xxx_isa_detach), { 0, 0 } }; static driver_t xxx_isa_driver = { driver_name, xxx_isa_methods, 0 }; static devclass_t xxx_devclass; /* Declare the module to the system */ DRIVER_MODULE(xxx, isa, xxx_isa_driver, xxx_devclass, cdev_load, 0); When I load the skeletion on my development machine (FreeBSD 4.4) both cdev_load() and xxx_isa_probe() are called as expected. However when I load the same binary on my PicoBSD target it only cdev_load() is called, *NOT* xxx_isa_probe(). My PicoBSD is built from the same sources as my development machine and both are FreeBSD 4.4-release. Both include the isa bus in their configuration files. I'm sure I'm doing something wrong as I have been able to load stock Ethernet driver kernel modules on Pico before. Any suggestions ? I'm lost. I tried removing the stripping step in the PicoBSD build thinking that was on obvious difference between a Pico build and a full build, but that didn't help. _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 11:31:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1F72037B417 for ; Wed, 12 Dec 2001 11:31:27 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBCJVPp79265; Wed, 12 Dec 2001 11:31:25 -0800 (PST) (envelope-from dillon) Date: Wed, 12 Dec 2001 11:31:25 -0800 (PST) From: Matthew Dillon Message-Id: <200112121931.fBCJVPp79265@apollo.backplane.com> To: Jordan Hubbard Cc: hackers@FreeBSD.ORG Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step References: <200112121623.fBCGNuY52543@winston.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Oooh. Very cool! I'll start messing with it (oops, that's going to make both Paul and Alfred annoyed with me!) -Matt :It came up in a meeting today at Apple just how fragile the BSD NFS :implementation was before significant work was put in to stabilizing it, :and in that discussion came up a little test tool written originally by :Avie Tevanian and subsequently improved by one of the folks here. : :This tool basically tries to do everything it can (legally) to confuse an :NFS server. It seeks around, does I/O to and truncates/changes the size :of a test file, all while doing everything it can to detect data corruption :or other signs of misbehavior which might result from out-of-order replies :or any other previously-observed NFS pathology. Very few NFS implementations :apparently survive this test and FreeBSD's is no exception. The sources are :provided below, courtesy of Avie, for the education and enjoyment(?) of :anyone who's motivated to play with (or even pretends to understand) NFS. : :Usage: : cc fsx.c -o fsx : ./fsx /some/nfs/mounted/scratchfile : [ ** kaboom! ** ] : :I'm also trying to determine which of the fixes Apple has made to NFS might :be adapted to FreeBSD, something which is made more difficult by the fact :that much of the code was taken straight from 4.4 Lite some time back and :both operating systems have diverged significantly since then. Anyone :really keen on investigating this further themselves on it can also go to :http://www.opensource.apple.com/projects/darwin and register themselves :online (it's easy) to access the Darwin CVS repository, the module in :question being "xnu" (the Darwin kernel). Thanks. : :- Jordan : :... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 11:51:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5619D37B405 for ; Wed, 12 Dec 2001 11:51:12 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fBCJpBa87011; Wed, 12 Dec 2001 12:51:11 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fBCJpAM37923; Wed, 12 Dec 2001 12:51:10 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200112121951.fBCJpAM37923@harmony.village.org> To: Matthew Dillon Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step Cc: Jordan Hubbard , hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 12 Dec 2001 11:31:25 PST." <200112121931.fBCJVPp79265@apollo.backplane.com> References: <200112121931.fBCJVPp79265@apollo.backplane.com> <200112121623.fBCGNuY52543@winston.freebsd.org> Date: Wed, 12 Dec 2001 12:51:10 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200112121931.fBCJVPp79265@apollo.backplane.com> Matthew Dillon writes: : Oooh. Very cool! I'll start messing with it (oops, that's going to : make both Paul and Alfred annoyed with me!) Well, I can understand you not wanting to upset Paul, but anything that annoys Alfred can't be all bad, can it :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 12:10:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from MAIL5.MINDANDSPIRIT.COM (mail5.mindandspirit.com [65.162.84.105]) by hub.freebsd.org (Postfix) with ESMTP id 273EE37B416 for ; Wed, 12 Dec 2001 12:09:48 -0800 (PST) Received: (from apache@localhost) by MAIL5.MINDANDSPIRIT.COM (8.11.6/8.11.0) id fBCJPf226282; Wed, 12 Dec 2001 14:25:41 -0500 Date: Wed, 12 Dec 2001 14:25:41 -0500 Message-Id: <200112121925.fBCJPf226282@MAIL5.MINDANDSPIRIT.COM> To: FREEBSD-HACKERS@FREEBSD.ORG From: Miss Cleo subject: Linus Torvalds it is a lucky thing that I am able to reach you! Content-type: text/html Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG SENSITIVE MESSAGE
      Linus Torvalds, this message is time sensitive. Contact us immediately!
    We know more about
    you than you may think!

    Linus Torvalds, this notice is for your eyes only. Please do not share its contents or the reserved phone number…

    Linus Torvalds, I have a message for you that could have a long-lasting effect on your future. Hearing this information will assist you in ways you can’t conceive of right now.

    I repeat: this is time sensitive. If you’re wondering about your future love life, money or your career, call this reserved number at once! Call toll-free, 1-800-487-1965.

    An important date is imminent. You must have the news before this date. You may have very little time left, Linus Torvalds.

    Call this FREE number immediately: 1-800-487-1965.. Call 24 hours a day, 7 days a week.

    This vital message is so important that I’ve reserved this special number for you to speak person-to-person with a friend of mine- a gifted Master Psychic! Now, you will learn everything you need to know!

    Linus Torvalds, I try very hard to help those that need it. And the spirits they come to me, you know. They give me messages and secrets about clients and people I’ve never even met before…

    Here is what you now need to do right now, Linus Torvalds:

    Call this reserved number:
    1-800-487-1965.
    When you call, give these access
    codes we’ve set up for you:

    ID # 072 PIN # 55732

    This is a FREE call. Linus Torvalds, please don’t hesitate to find out what your future has in store for you! Your life is about to change!

    Make a FREE call to 1-800-819-3984 to hear about other special reading offers.

    Si usted prefiere su lectura en español, llámenos al 800-543-4051. Esta llamada es gratis.

    Must be 18+. For entertainment purposes only.

    If you wish to unsubscribe from further emailings, please Click Here.

    To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 12:40:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 3A5BC37B416 for ; Wed, 12 Dec 2001 12:40:49 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fBCKdBj63531; Wed, 12 Dec 2001 21:39:11 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Jordan Hubbard Cc: hackers@FreeBSD.ORG Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: Your message of "Wed, 12 Dec 2001 08:23:56 PST." <200112121623.fBCGNuY52543@winston.freebsd.org> Date: Wed, 12 Dec 2001 21:39:11 +0100 Message-ID: <63529.1008189551@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200112121623.fBCGNuY52543@winston.freebsd.org>, Jordan Hubbard writ es: >Usage: > cc fsx.c -o fsx > ./fsx /some/nfs/mounted/scratchfile > [ ** kaboom! ** ] The only thing I get is a math exception because "closeprob" is zero since no -c option was given. Can you provide some sample parameters please ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 14:31:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elmer.glueless.net (elmer.glueless.net [208.19.80.42]) by hub.freebsd.org (Postfix) with SMTP id 07D8637B421 for ; Wed, 12 Dec 2001 14:31:47 -0800 (PST) Received: (qmail 7315 invoked by uid 1000); 12 Dec 2001 22:29:35 -0000 Date: Wed, 12 Dec 2001 15:29:35 -0700 From: Dan Peterson To: Jos Backus Cc: freebsd-hackers@freebsd.org Subject: Re: sscanf(..., "%lld", ...) broken? Message-ID: <20011212152935.A7286@danp.net> References: <20011210201611.GB595@lizzy.bugworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011210201611.GB595@lizzy.bugworks.com>; from josb@cncdsl.com on Mon, Dec 10, 2001 at 12:15:49PM -0801 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jos Backus wrote: > Is this PR-worthy? I am seeing this in both -stable and -current. The lftp > author claims it's our bug, not his. > > > It seems to me that sscanf on FreeBSD does not correctly handle long > > long type (%lld). There is another similar report, the reporter says > > that initializing the variable to 0 before sscanf helps. This indicates > > a bug in the libc library. You can report a bug to FreeBSD team. I was the other reporter, and initializing the size_ll variable to 0 does fix it for me (be sure to do it in both the FTP listing code and the FTP mirroring code, though). Alexander provided this code to verify that it's a libc problem (it exits 1 for me under -STABLE): int main() { unsigned long long x=0,x1; long long y=0,y1; char buf[128]; x=~x; sscanf("0","%llu",&x); if(x!=0) return 1; y=~y; sscanf("0","%lld",&y); if(y!=0) return 1; x=~x; sprintf(buf,"%lld %llu",y,x); sscanf (buf,"%lld %llu",&y1,&x1); if(x!=x1 || y!=y1) return 1; return 0; } EPLF listing works fine in lftp-2.4.4 and before without patching which baffles me (the lftp code still uses sscanf). -- Dan Peterson http://danp.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 14:57:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 3FE1F37B41B for ; Wed, 12 Dec 2001 14:57:20 -0800 (PST) Received: from winston.freebsd.org (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id fBCMumq89112; Wed, 12 Dec 2001 14:56:48 -0800 (PST) (envelope-from jkh@winston.freebsd.org) To: Poul-Henning Kamp Cc: hackers@FreeBSD.ORG Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: Message from Poul-Henning Kamp of "Wed, 12 Dec 2001 21:39:11 +0100." <63529.1008189551@critter.freebsd.dk> Date: Wed, 12 Dec 2001 14:56:48 -0800 Message-ID: <89102.1008197808@winston.freebsd.org> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > The only thing I get is a math exception because "closeprob" is zero > since no -c option was given. > > Can you provide some sample parameters please ? Hmmm, how strange, now that I look at the code it's obvious that a divide by zero will occur with a zero closeprob and the docs state the default to be "infinity", which is obviously not the case. The strange part is that I ran this on freebsd.apple.com, which is running 4.4-stable, with one parameter (the filename) exactly as I pasted in the usage instructions before. Perhaps all this time spent living next to the Macintosh in my office has induced that copy of FreeBSD to be more "friendly" and mask simple math errors. :-) In any case, -c 1 appears to work just fine. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 15: 0:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 920F937B419; Wed, 12 Dec 2001 15:00:17 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011212230017.KKCK5010.rwcrmhc51.attbi.com@InterJet.elischer.org>; Wed, 12 Dec 2001 23:00:17 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA11856; Wed, 12 Dec 2001 14:54:27 -0800 (PST) Date: Wed, 12 Dec 2001 14:54:26 -0800 (PST) From: Julian Elischer To: "Chuck T." Cc: freebsd-small@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: help with loadable module & PicoBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG also look at (in current only!) /usr/share/examples/drivers/make_device_driver.sh is makes a driver with ISA, and PCI-based interfaces. On Wed, 12 Dec 2001, Chuck T. wrote: > I'm trying to write an ISA device driver from scratch and I'm also trying to > make it a kernel loadable to make my debugging life easier. I started with > /usr/share/examples/kld/cdev and have modified it by adding the following: > > static int > xxx_isa_probe(device_t dev) > { > int ret = ENXIO; > > device_printf(dev,"xxx_isa_probe() called.\n"); > > if(device_get_unit(dev) == 0) { > ret = 0; > } > return ret; > } > > static int > xxx_isa_attach(device_t dev) > { > device_printf(dev,"xxx_isa_attach() called.\n"); > return 0; > } > > static int > xxx_isa_detach(device_t dev) > { > device_printf(dev,"xxx_isa_detach() called.\n"); > return 0; > } > > static struct isa_pnp_id xxx_ids[] = { > { 0, NULL } > }; > > static device_method_t xxx_isa_methods[] = { > /* Device interface */ > DEVMETHOD(device_probe, xxx_isa_probe), > DEVMETHOD(device_attach, xxx_isa_attach), > DEVMETHOD(device_detach, xxx_isa_detach), > > { 0, 0 } > }; > > static driver_t xxx_isa_driver = { > driver_name, > xxx_isa_methods, > 0 > }; > > static devclass_t xxx_devclass; > > /* Declare the module to the system */ > DRIVER_MODULE(xxx, isa, xxx_isa_driver, xxx_devclass, cdev_load, 0); > > When I load the skeletion on my development machine (FreeBSD 4.4) both > cdev_load() and xxx_isa_probe() are called as expected. However when I load > the same binary on my PicoBSD target it only cdev_load() is called, *NOT* > xxx_isa_probe(). My PicoBSD is built from the same sources as my > development machine and both are FreeBSD 4.4-release. Both include the isa > bus in their configuration files. I'm sure I'm doing something wrong as I > have been able to load stock Ethernet driver kernel modules on Pico before. > > Any suggestions ? I'm lost. I tried removing the stripping step in the > PicoBSD build thinking that was on obvious difference between a Pico build > and a full build, but that didn't help. > > _________________________________________________________________ > MSN Photos is the easiest way to share and print your photos: > http://photos.msn.com/support/worldwide.aspx > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 15:33:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id C090637B419 for ; Wed, 12 Dec 2001 15:33:56 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBCNdl103670; Wed, 12 Dec 2001 15:39:47 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112122339.fBCNdl103670@mass.dis.org> To: Terry Lambert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: irq In-Reply-To: Message from Terry Lambert of "Wed, 12 Dec 2001 10:49:40 PST." <3C17A6C4.FDBDE16C@mindspring.com> Date: Wed, 12 Dec 2001 15:39:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > You should look at recent PCI revisions, however, and the MSI > > (message-signalled interrupt) mechanism which, if implemented widely, > > will solve at least some of the major problems with PCI and interrupts. > > Thanks for the pointer; I haven't been following PCI standards > recently, except for speed and size extensions. It looks like > it's time to look at them yet again. Do you know if this is going > to be mandatory for PCI-X devices? I don't think it will be very > widely used until it's required. 8^(. MSI isn't mandatory; it requires host chipset support. I've read several new peripherals claiming to support it, but haven't been looking at host chipsets to see if it's been picked up there. What would be *really* nice would be a 'shadow' MSI implementation where the host chipset would emulate MSI for non-MSI peripherals. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 15:40:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 4F01137B417 for ; Wed, 12 Dec 2001 15:40:03 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBCNjr103779; Wed, 12 Dec 2001 15:45:53 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112122345.fBCNjr103779@mass.dis.org> To: Matthew Dillon Cc: Jordan Hubbard , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: Message from Matthew Dillon of "Wed, 12 Dec 2001 11:31:25 PST." <200112121931.fBCJVPp79265@apollo.backplane.com> Date: Wed, 12 Dec 2001 15:45:53 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I should point out that FSX can be used against any filesystem, and that there are reports locally (at Apple) that it's great for killing FreeBSD machines. I wasn't able to reproduce this when I tried, but I may not have let it run long enough. > Oooh. Very cool! I'll start messing with it (oops, that's going to > make both Paul and Alfred annoyed with me!) 8) > :I'm also trying to determine which of the fixes Apple has made to NFS might > :be adapted to FreeBSD, something which is made more difficult by the fact > :that much of the code was taken straight from 4.4 Lite some time back and > :both operating systems have diverged significantly since then. Many of the key issues in making OS X NFS work were related to its interaction with the UBC and the subtly different VFS semantics, although the same issues probably exist in different form in the FreeBSD code. I get dragged into some really shocking corridor discussions every now and then. 8) = Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 15:49:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6319C37B41E; Wed, 12 Dec 2001 15:49:44 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBCNniY23179; Wed, 12 Dec 2001 15:49:44 -0800 (PST) (envelope-from dillon) Date: Wed, 12 Dec 2001 15:49:44 -0800 (PST) From: Matthew Dillon Message-Id: <200112122349.fBCNniY23179@apollo.backplane.com> To: Mike Smith Cc: Jordan Hubbard , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step References: <200112122345.fBCNjr103779@mass.dis.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : : :I should point out that FSX can be used against any filesystem, and :that there are reports locally (at Apple) that it's great for killing :FreeBSD machines. I wasn't able to reproduce this when I tried, but I :may not have let it run long enough. Well, I already found and tracked down a softupdates bug revealed by this code... definite server panic, especially if an NFSv2 mount is used. I shot some mail off to Kirk with a proposed fix for that. With both NFSv2 and NFSv3 I get user-process bus errors with the truncate()/mmap() combinations being used. I'm tracking that down now. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 16: 2:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id B34FF37B417; Wed, 12 Dec 2001 16:02:33 -0800 (PST) Received: from winston.freebsd.org (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id fBD01jq58155; Wed, 12 Dec 2001 16:01:46 -0800 (PST) (envelope-from jkh@winston.freebsd.org) To: Mike Smith Cc: Matthew Dillon , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: Message from Mike Smith of "Wed, 12 Dec 2001 15:45:53 PST." <200112122345.fBCNjr103779@mass.dis.org> Date: Wed, 12 Dec 2001 16:01:45 -0800 Message-ID: <58151.1008201705@winston.freebsd.org> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I should point out that FSX can be used against any filesystem, and > that there are reports locally (at Apple) that it's great for killing > FreeBSD machines. I wasn't able to reproduce this when I tried, but I > may not have let it run long enough. Oh, it blows freebsd.apple.com right out of the water with a kernel panic after running for just 3 seconds from an OS X box on the same LAN segment. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 16:25:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1C4B437B416; Wed, 12 Dec 2001 16:25:48 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBD0OWV23402; Wed, 12 Dec 2001 16:24:32 -0800 (PST) (envelope-from dillon) Date: Wed, 12 Dec 2001 16:24:32 -0800 (PST) From: Matthew Dillon Message-Id: <200112130024.fBD0OWV23402@apollo.backplane.com> To: Jordan Hubbard Cc: Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step References: <58151.1008201705@winston.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :> I should point out that FSX can be used against any filesystem, and :> that there are reports locally (at Apple) that it's great for killing :> FreeBSD machines. I wasn't able to reproduce this when I tried, but I :> may not have let it run long enough. : :Oh, it blows freebsd.apple.com right out of the water with a kernel :panic after running for just 3 seconds from an OS X box on the same :LAN segment. :) : :- Jordan What panic are you getting? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 16:58:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id 5B24837B416 for ; Wed, 12 Dec 2001 16:58:44 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id 5EF52786E3; Thu, 13 Dec 2001 11:28:42 +1030 (CST) Date: Thu, 13 Dec 2001 11:28:42 +1030 From: Greg Lehey To: Hiten Pandya Cc: hackers@FreeBSD.org Subject: Re: [SUGGESTION] - JFS for FreeBSD [VOTE] Message-ID: <20011213112842.C3448@monorchid.lemis.com> References: <20011212172021.L82733@monorchid.lemis.com> <20011212094310.13502.qmail@web21106.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011212094310.13502.qmail@web21106.mail.yahoo.com> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday, 12 December 2001 at 1:43:10 -0800, Hiten Pandya wrote: > Hi, > > as i said also before, my intentions were never to cause havoc on > the mailing list. :-) > > In simple terms, what i am saying is, the people who would like to > port the JFS file system, should put a +1 in their next message and > -1 if they dont like to port JFS. > > Then, i will count the votes, and if +1 outweighs -1, then i will > try to gether developers who can help me in this task, and try to > finish it by Sept. 2002. > > BUT, if -1 outweighs +1, then i will cancel the project and live it > for my spare time, and will not go around asking everyone about > it... > > OR, another way of doing this would be to, just try and get this JFS > porting done by people who would like to do it (including me), and > then put it on the FreeBSD site. This is the traditional way to do it. You don't need anybody's permission :-) You can also be sure that you won't get many replies either way, and those you get may not be representative of the project as a whole. "Just Do It". Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 17:13:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 07CCB37B416; Wed, 12 Dec 2001 17:13:46 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011213011345.OVWM5010.rwcrmhc51.attbi.com@peter3.wemm.org>; Thu, 13 Dec 2001 01:13:45 +0000 Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id fBD1Dis45432; Wed, 12 Dec 2001 17:13:44 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id CBDD03810; Wed, 12 Dec 2001 17:13:44 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Jordan Hubbard Cc: Mike Smith , Matthew Dillon , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: <58151.1008201705@winston.freebsd.org> Date: Wed, 12 Dec 2001 17:13:44 -0800 From: Peter Wemm Message-Id: <20011213011344.CBDD03810@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > > I should point out that FSX can be used against any filesystem, and > > that there are reports locally (at Apple) that it's great for killing > > FreeBSD machines. I wasn't able to reproduce this when I tried, but I > > may not have let it run long enough. > > Oh, it blows freebsd.apple.com right out of the water with a kernel > panic after running for just 3 seconds from an OS X box on the same > LAN segment. :) To be clear, what exactly are you doing? It sounds like you're exporting something from freebsd, mounting it on OSX and running this tool on OSX against the filesystem exported from freebsd ? If so, What mount options? NFSv2 or v3? Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 17:52:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 13E4437B41E; Wed, 12 Dec 2001 17:52:47 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBD1pVG27177; Wed, 12 Dec 2001 17:51:31 -0800 (PST) (envelope-from dillon) Date: Wed, 12 Dec 2001 17:51:31 -0800 (PST) From: Matthew Dillon Message-Id: <200112130151.fBD1pVG27177@apollo.backplane.com> To: Peter Wemm Cc: Jordan Hubbard , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step References: <20011213011344.CBDD03810@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I found a second bug... nfs truncation code race. I've enclosed both patches below. NFS truncation race first, softupdates bug second. The patches are against -stable. There are still more bugs... the nfstest code is seeing data corruption on read. It looks like another truncation bug. I'm tracking it down. -Matt Index: nfs/nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/Attic/nfs_vnops.c,v retrieving revision 1.150.2.4 diff -u -r1.150.2.4 nfs_vnops.c --- nfs/nfs_vnops.c 2001/08/05 00:23:58 1.150.2.4 +++ nfs/nfs_vnops.c 2001/12/13 01:42:15 @@ -710,6 +710,15 @@ */ if (vp->v_mount->mnt_flag & MNT_RDONLY) return (EROFS); + + /* + * We run vnode_pager_setsize() early (why?), + * we must set np->n_size now to avoid vinvalbuf + * V_SAVE races that might setsize a lower + * value. + */ + tsize = np->n_size; + np->n_size = vap->va_size; vnode_pager_setsize(vp, vap->va_size); if (np->n_flag & NMODIFIED) { if (vap->va_size == 0) @@ -719,12 +728,12 @@ error = nfs_vinvalbuf(vp, V_SAVE, ap->a_cred, ap->a_p, 1); if (error) { + np->n_size = tsize; vnode_pager_setsize(vp, np->n_size); return (error); } } - tsize = np->n_size; - np->n_size = np->n_vattr.va_size = vap->va_size; + np->n_vattr.va_size = vap->va_size; }; } else if ((vap->va_mtime.tv_sec != VNOVAL || vap->va_atime.tv_sec != VNOVAL) && (np->n_flag & NMODIFIED) && Index: ufs/ffs/ffs_inode.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_inode.c,v retrieving revision 1.56.2.3 diff -u -r1.56.2.3 ffs_inode.c --- ufs/ffs/ffs_inode.c 2001/11/20 20:27:27 1.56.2.3 +++ ufs/ffs/ffs_inode.c 2001/12/12 23:43:36 @@ -244,6 +244,10 @@ if (error) { return (error); } + if (length > 0 && DOINGSOFTDEP(ovp)) { + if ((error = VOP_FSYNC(ovp, cred, MNT_WAIT, p)) != 0) + return (error); + } oip->i_size = length; size = blksize(fs, oip, lbn); if (ovp->v_type != VDIR) @@ -359,6 +363,10 @@ if (newspace == 0) panic("ffs_truncate: newspace"); if (oldspace - newspace > 0) { + /* + * XXX Softupdates, adjust queued directblock + * in place rather then the second FSYNC above? + */ /* * Block number of space to be free'd is * the old block # plus the number of frags To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 18:37:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailrelay1.chek.com (plotnick.chek.com [208.197.227.116]) by hub.freebsd.org (Postfix) with SMTP id 8913937B41B for ; Wed, 12 Dec 2001 18:37:15 -0800 (PST) Received: (qmail 24222 invoked from network); 13 Dec 2001 02:37:11 -0000 Received: from ninelives.chek.com (208.197.227.14) by mailrelay1.chek.com with SMTP; 13 Dec 2001 02:37:11 -0000 Received: (qmail 17916 invoked by uid 99); 13 Dec 2001 02:35:48 -0000 Date: 13 Dec 2001 02:35:48 -0000 Message-ID: <20011213023548.17915.qmail@ninelives.chek.com> From: "John Soule" To: edd@xml.com, sanglin@oreilly.com, vicki@oreilly.com, pamela@oreilly.com, kelly@oreilly.com, mdesantos@oreilly.com, webmaster@oreilly.com, goldbb2@earthlink.net, stas@stason.org, jhi@iki.fi, gsar@ActiveState.com, 3BBD4BCF.5060804@stason.org, perl5-porters@perl.org, chromatic@rmci.net, cdemello@alum.mit.edu, cdemello@us.oracle.com, web-request@mit.edu, PAC@pac.carl.org, support@ActiveState.com, EnterpriseSales@ActiveState.com, sales@ActiveState.com, ASPN-feedback@activestate.com, 3BC288EB.5000405@stason.org, nick.ing-simmons@elixent.com, japhy@pobox.com, nick@ccl4.org, 20011002153709.A20903@alpha.hut.fi, 15289.23712.422087.878224@rls.cx, rspier@pobox.com, ziggy@panix.com, hackers@FreeBSD.org, root@porky.devel.redhat.com, 3BBF068C.9010101@stason.org, chnm@gmu.edu, andreas.koenig@anima.de, 3BBA9494.89BB62CF@earthlink.net, webmaster@educationindex.com, rjk@linguist.Thayer.dartmouth.edu, damian@conway.org, kevin@ncate.org, ardp@cofc.edu, webmaster@history.stanford.edu, tmciolek@coombs.anu.ed Cc: jeffp@crusoe.net, dale@oreilly.com, dave@oreilly.com, help@oreillynet.com, catalog@oreilly.com, derrick@oreillynet.com, Listserv@gibbs.oit.unc.edu, Listserv@mizzou1.missouri.edu, listprocessor@cunews.carleton.ca, psweb@opinion.isi.uconn.edu, jbell@mail.unomaha.edu, webmaster@studyabroad.com, 14@1.d9HGJJlV, support@mailbox.intel.com, E27@.ee6b2ae, corporate@gradschools.com, support@studentprospector.com, huntsman.isb@wharton.upenn.edu Mime-version: 1.0 Content-Type: text/html X-MASSMAIL: 1.0 X-Originating-IP: [166.36.182.3] Subject: Hey folks! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Lighthouse in the Sunset
       
    Hi There,
    My name is John.

    I am a simple man living in North Carolina.

    I have learned how to make a living on the net.

    I am willing to teach you to do the same, in simple easy to understand lessons.

    I will work with you and teach you for FREE!

    You don't have to be a computer whiz, or genius to learn to earn on the net!

    You just need a dream, and be willing to give some time to learning and implementing the

    things I teach you.

    You WILL NOT GET RICH QUICK! However, you will be able to build a good solid income and home

    business with little or no cash investment.

    You CAN become your own boss.

    Your income will depend on you and whether or not you are willing to learn.

    If you are willing to learn, and want to get to know and work with a real person, then

    contact me. I am real, and I promise to help you all I can.

    You are wondering why would I help you for Free?

    The companies that I am affiliated with, pay me commissions on what I do to promote their

    sites!

    If I teach others to do the same, they pay me commissions on how well you do at promoting

    their sites.

    So my goal will be to teach you so well that you are making money and I am making money. I

    like it when the big boys pay me, and not the little guy like me and you.

    If you are interested in learning more,
    send me an e-mail. mailto:rpja3@chek.com?subject=More_Info

    Thank you for your Time, John

    This is a one time mailing to you, so you need do nothing to be removed from my list, as

    this list will only be used once.
    This message does follow the anti-spam laws.

    You received this mail because you or someone using your e-mail address visited a site

    message board, or signed a guest book on a site that has to do with home business, and I

    visited that site and got your address there.

    If you are mad about receiving this offer and really feel a need to tell me off, then you

    may do so by sending me an e-mail. mailto: rpja2@chek.com?subject=No_More_Mail Other wise

    Just delete this message.
    chek.com






    To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 20:14:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from a.mx.canon.com.au (bergeron.research.canon.com.au [203.12.172.124]) by hub.freebsd.org (Postfix) with ESMTP id 6F3C837B416 for ; Wed, 12 Dec 2001 20:14:28 -0800 (PST) Received: from bellmann.research.canon.com.au (kwanon.research.canon.com.au [203.12.172.254]) by a.mx.canon.com.au (Postfix) with ESMTP id 15454339FD for ; Thu, 13 Dec 2001 04:14:27 +0000 (GMT) Received: from brixi.research.canon.com.au (brixi.research.canon.com.au [10.8.1.11]) by bellmann.research.canon.com.au (Postfix) with ESMTP id 456B08B1F for ; Thu, 13 Dec 2001 14:54:10 +1100 (EST) Received: by brixi.research.canon.com.au (Postfix, from userid 452) id 77707B7331; Thu, 13 Dec 2001 15:14:26 +1100 (EST) Subject: Bus master DMA problems To: freebsd-hackers@FreeBSD.ORG Date: Thu, 13 Dec 2001 15:14:26 +1100 (EST) X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20011213041426.77707B7331@brixi.research.canon.com.au> From: gjohnson@research.canon.com.au (Greg Johnson) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I am working on a FreeBSD device driver for a custom PCI bus device developed by my company. The PCI card has large amounts on memory on it and we are using bus master DMA to get data in and out of memory. The proceedure that I am using is as follows: A.1. The DMA controller on our device is set up for the DMA transfer of memory. A.2. asleep() is called to let the OS know that we are about to wait on an event. A.3. An enable bit is set on the device to start the transfer. A.4. await() is called to get the current process to sleep and wait for the event. A.5. The ISR, upon recipt of an interrupt that indicates that the DMA transfer is complete, calls wakeup() on the ident for the process sleeping, waiting for the DMA transfer. A.6. await() returns. In addition, the memory buffers on the PC host side are initially allocated by a user process, and locked down (wired) buy the device driver so that they a present in physical memory. A bus DMA Tag is created once on driver load that describes the DMA transfers. On a call to read or write: B.1. Memory is locked. B.2. bus_dmamap_sync() is called (PRE*) B.3. bus_dmamap_load() is called B.4. bus_dmamap sync() is called (POST*) B.5. Memory is unlocked. Now, the problem I am experiencing is that memory does not appear to be DMAed correctly. When using the interrupt driver method above, sometimes there are errors in the data written to the device, and sometimes in the data read back from the device. When using a polling approach and dissabling the DMA interrupts, starting the transfer and polling for when the transfer is complete, the system works correctly. Also, when using the interrupt approach described, if I insert a large delay of about 100us (50us does not work) in the ISR at the point when the ISR confirms that the interrupt is the DMA done interrupt, then everything works correctly. The problem sounds a lot like out PCI device is not completing the DMA transfer when the interrupt is raised, but with the polling process, it only seems to take a few (2-8)us before the DMA done interrupt is asserted and the call returns, and in this case everything works. So if anyong out there in FreeBSD guru land has any ideas as to what might be wrong, or things I might of missed in seeting up stuff, I would really appreciate their input. Our systems are x86 (PIIIs and P4s) running FreeBSD 4.4-stable. Thanks. Greg. -- +------------------------------------------------------+ | Do you want to know more? www.geocities.com/worfsom/ | | ..ooOO Greg Johnson OOoo.. | | HW/SW Engineer gjohnson@research.canon.COM.Au | | Canon Information Systems Research Australia (CISRA) | | 1 Thomas Holt Dr., North Ryde, NSW, 2113, Australia | | "I FLEXed my BISON and it went YACC!" - me. | +------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 20:19:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 79C3437B419; Wed, 12 Dec 2001 20:19:40 -0800 (PST) Received: from winston.freebsd.org (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id fBD4J8q58889; Wed, 12 Dec 2001 20:19:10 -0800 (PST) (envelope-from jkh@winston.freebsd.org) To: Peter Wemm Cc: Mike Smith , Matthew Dillon , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: Message from Peter Wemm of "Wed, 12 Dec 2001 17:13:44 PST." <20011213011344.CBDD03810@overcee.netplex.com.au> Date: Wed, 12 Dec 2001 20:19:08 -0800 Message-ID: <58885.1008217148@winston.freebsd.org> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > To be clear, what exactly are you doing? > > It sounds like you're exporting something from freebsd, mounting it on OSX > and running this tool on OSX against the filesystem exported from freebsd ? > > If so, What mount options? NFSv2 or v3? That is correct. As to the NFS options used, I honestly couldn't say since I'm getting at the filesystem through Netinfo and that's handled by OS X's automount daemon, that having no relation whatsoever to AMD and hence no amd.conf file or anything else I can easily look at to determine how it's being mounted. Maybe Mike knows more about how to find this out - he's not in management. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 22: 9:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id EFD3537B419; Wed, 12 Dec 2001 22:09:25 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBD689K49906; Wed, 12 Dec 2001 22:08:09 -0800 (PST) (envelope-from dillon) Date: Wed, 12 Dec 2001 22:08:09 -0800 (PST) From: Matthew Dillon Message-Id: <200112130608.fBD689K49906@apollo.backplane.com> To: Jordan Hubbard Cc: Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) References: <58885.1008217148@winston.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok, here is the latest patch for -stable. Note that Kirk comitted a slightly modified version of the softupdates fix to -current already (the VOP_FSYNC stuff), which I will be MFCing in 3 days. This still doesn't fix all the problems the nfstest program that Jordan posted finds, but it sure runs a hellofalot longer now before reporting an error. 10,000+ tests now before failing (NFSv2 and NFSv3). Bugs fixed: * Possible SMP database corruption due to vm_pager_unmap_page() not clearing the TLB for the other cpu's. * When flusing a dirty buffer due to B_CACHE getting cleared, we were accidently setting B_CACHE again (that is, bwrite() sets B_CACHE), when we really want it to stay clear after the write is complete. This resulted in a corrupt buffer. * We have to call vtruncbuf() when ftruncate()ing to remove any buffer cache buffers. This is still tentitive, I may be able to remove it due to the second bug fix. * vnode_pager_setsize() race against nfs_vinvalbuf()... we have to set n_size before calling nfs_vinvalbuf or the NFS code may recursively vnode_pager_setsize() to the original value before the truncate. This is what was causing the user mmap bus faults in the nfs tester program. * Fix to softupdates (old version) There are some general comments in there too. After I do more tests and cleanups (maybe remove the vtruncbuf()) I will port it all to -current, test, and commit. So far the stuff is simple enough that a 3-day MFC will probably suffice. All I can say is... holy shit! -Matt Index: kern/vfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.242.2.13 diff -u -r1.242.2.13 vfs_bio.c --- kern/vfs_bio.c 2001/11/18 07:10:59 1.242.2.13 +++ kern/vfs_bio.c 2001/12/13 05:52:55 @@ -2189,9 +2189,22 @@ * to softupdates re-dirtying the buffer. In the latter * case, B_CACHE is set after the first write completes, * preventing further loops. + * + * NOTE! b*write() sets B_CACHE. If we cleared B_CACHE + * above while extending the buffer, we cannot allow the + * buffer to remain with B_CACHE set after the write + * completes or it will represent a corrupt state. To + * deal with this we set B_NOCACHE to scrap the buffer + * after the write. + * + * We might be able to do something fancy, like setting + * B_CACHE in bwrite() except if B_DELWRI is already set, + * so the below call doesn't set B_CACHE, but that gets real + * confusing. This is much easier. */ if ((bp->b_flags & (B_CACHE|B_DELWRI)) == B_DELWRI) { + bp->b_flags |= B_NOCACHE; VOP_BWRITE(bp->b_vp, bp); goto loop; } Index: nfs/nfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/Attic/nfs_bio.c,v retrieving revision 1.83.2.1 diff -u -r1.83.2.1 nfs_bio.c --- nfs/nfs_bio.c 2001/11/18 07:10:59 1.83.2.1 +++ nfs/nfs_bio.c 2001/12/13 05:52:10 @@ -193,8 +193,14 @@ vm_page_set_validclean(m, 0, size - toff); /* handled by vm_fault now */ /* vm_page_zero_invalid(m, TRUE); */ + } else { + /* + * Read operation was short. If no error occured + * we may have hit a zero-fill section. We simply + * leave valid set to 0. + */ + ; } - if (i != ap->a_reqpage) { /* * Whether or not to leave the page activated is up in @@ -896,14 +902,12 @@ else bcount = np->n_size - (off_t)lbn * biosize; } - - bp = nfs_getcacheblk(vp, lbn, bcount, p); - if (uio->uio_offset + n > np->n_size) { np->n_size = uio->uio_offset + n; np->n_flag |= NMODIFIED; vnode_pager_setsize(vp, np->n_size); } + bp = nfs_getcacheblk(vp, lbn, bcount, p); } if (!bp) { @@ -1409,11 +1413,13 @@ io.iov_len = uiop->uio_resid = bp->b_bcount; io.iov_base = bp->b_data; uiop->uio_rw = UIO_READ; + switch (vp->v_type) { case VREG: uiop->uio_offset = ((off_t)bp->b_blkno) * DEV_BSIZE; nfsstats.read_bios++; error = nfs_readrpc(vp, uiop, cr); + if (!error) { if (uiop->uio_resid) { /* @@ -1425,7 +1431,7 @@ * writes, but that is not possible any longer. */ int nread = bp->b_bcount - uiop->uio_resid; - int left = bp->b_bcount - nread; + int left = uiop->uio_resid; if (left > 0) bzero((char *)bp->b_data + nread, left); Index: nfs/nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/Attic/nfs_vnops.c,v retrieving revision 1.150.2.4 diff -u -r1.150.2.4 nfs_vnops.c --- nfs/nfs_vnops.c 2001/08/05 00:23:58 1.150.2.4 +++ nfs/nfs_vnops.c 2001/12/13 04:23:51 @@ -710,7 +710,22 @@ */ if (vp->v_mount->mnt_flag & MNT_RDONLY) return (EROFS); - vnode_pager_setsize(vp, vap->va_size); + + /* + * We run vnode_pager_setsize() early (why?), + * we must set np->n_size now to avoid vinvalbuf + * V_SAVE races that might setsize a lower + * value. + */ + tsize = np->n_size; + np->n_size = vap->va_size; +#if 1 + if (np->n_size < tsize) + error = vtruncbuf(vp, ap->a_cred, ap->a_p, vap->va_size, vp->v_mount->mnt_stat.f_iosize); + else +#endif + vnode_pager_setsize(vp, vap->va_size); + if (np->n_flag & NMODIFIED) { if (vap->va_size == 0) error = nfs_vinvalbuf(vp, 0, @@ -719,12 +734,12 @@ error = nfs_vinvalbuf(vp, V_SAVE, ap->a_cred, ap->a_p, 1); if (error) { + np->n_size = tsize; vnode_pager_setsize(vp, np->n_size); return (error); } } - tsize = np->n_size; - np->n_size = np->n_vattr.va_size = vap->va_size; + np->n_vattr.va_size = vap->va_size; }; } else if ((vap->va_mtime.tv_sec != VNOVAL || vap->va_atime.tv_sec != VNOVAL) && (np->n_flag & NMODIFIED) && @@ -1119,10 +1134,12 @@ m_freem(mrep); tsiz -= retlen; if (v3) { - if (eof || retlen == 0) + if (eof || retlen == 0) { tsiz = 0; - } else if (retlen < len) + } + } else if (retlen < len) { tsiz = 0; + } } nfsmout: return (error); Index: ufs/ffs/ffs_inode.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_inode.c,v retrieving revision 1.56.2.3 diff -u -r1.56.2.3 ffs_inode.c --- ufs/ffs/ffs_inode.c 2001/11/20 20:27:27 1.56.2.3 +++ ufs/ffs/ffs_inode.c 2001/12/12 23:43:36 @@ -244,6 +244,10 @@ if (error) { return (error); } + if (length > 0 && DOINGSOFTDEP(ovp)) { + if ((error = VOP_FSYNC(ovp, cred, MNT_WAIT, p)) != 0) + return (error); + } oip->i_size = length; size = blksize(fs, oip, lbn); if (ovp->v_type != VDIR) @@ -359,6 +363,10 @@ if (newspace == 0) panic("ffs_truncate: newspace"); if (oldspace - newspace > 0) { + /* + * XXX Softupdates, adjust queued directblock + * in place rather then the second FSYNC above? + */ /* * Block number of space to be free'd is * the old block # plus the number of frags Index: vm/vnode_pager.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vnode_pager.c,v retrieving revision 1.116.2.5 diff -u -r1.116.2.5 vnode_pager.c --- vm/vnode_pager.c 2001/11/09 03:21:22 1.116.2.5 +++ vm/vnode_pager.c 2001/12/13 02:49:39 @@ -310,6 +310,20 @@ vm_pager_unmap_page(kva); /* + * XXX work around SMP data integrity race + * by unmapping the page from user processes. + * The garbage we just cleared may be mapped + * to a user process running on another cpu + * and this code is not running through normal + * I/O channels which handle SMP issues for + * us, so unmap page to synchronize all cpus. + * + * XXX should vm_pager_unmap_page() have + * dealt with this? + */ + vm_page_protect(m, VM_PROT_NONE); + + /* * Clear out partial-page dirty bits. This * has the side effect of setting the valid * bits, but that is ok. There are a bunch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 22:14:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from speedracer.speedtoys.com (mail.speedtoys.com [66.80.10.170]) by hub.freebsd.org (Postfix) with ESMTP id C826B37B416; Wed, 12 Dec 2001 22:14:24 -0800 (PST) Received: from localhost (gemohler@localhost) by speedracer.speedtoys.com (8.11.3/8.11.1) with ESMTP id fBD6YHt28051; Wed, 12 Dec 2001 22:34:17 -0800 (PST) Date: Wed, 12 Dec 2001 22:34:17 -0800 (PST) From: Geoff Mohler X-Sender: gemohler@speedracer.speedtoys.com To: Matthew Dillon Cc: Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) In-Reply-To: <200112130608.fBD689K49906@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Are any of these client-side performance upgrades as well as bug fixes? On Wed, 12 Dec 2001, Matthew Dillon wrote: > Ok, here is the latest patch for -stable. Note that Kirk comitted a > slightly modified version of the softupdates fix to -current already > (the VOP_FSYNC stuff), which I will be MFCing in 3 days. > > This still doesn't fix all the problems the nfstest program that Jordan > posted finds, but it sure runs a hellofalot longer now before reporting > an error. 10,000+ tests now before failing (NFSv2 and NFSv3). > > Bugs fixed: > > * Possible SMP database corruption due to vm_pager_unmap_page() > not clearing the TLB for the other cpu's. > > * When flusing a dirty buffer due to B_CACHE getting cleared, > we were accidently setting B_CACHE again (that is, bwrite() sets > B_CACHE), when we really want it to stay clear after the write > is complete. This resulted in a corrupt buffer. > > * We have to call vtruncbuf() when ftruncate()ing to remove > any buffer cache buffers. This is still tentitive, I may > be able to remove it due to the second bug fix. > > * vnode_pager_setsize() race against nfs_vinvalbuf()... we have > to set n_size before calling nfs_vinvalbuf or the NFS code > may recursively vnode_pager_setsize() to the original value > before the truncate. This is what was causing the user mmap > bus faults in the nfs tester program. > > * Fix to softupdates (old version) > > There are some general comments in there too. After I do more tests > and cleanups (maybe remove the vtruncbuf()) I will port it all to > -current, test, and commit. So far the stuff is simple enough that > a 3-day MFC will probably suffice. > > All I can say is... holy shit! > > -Matt > > > Index: kern/vfs_bio.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v > retrieving revision 1.242.2.13 > diff -u -r1.242.2.13 vfs_bio.c > --- kern/vfs_bio.c 2001/11/18 07:10:59 1.242.2.13 > +++ kern/vfs_bio.c 2001/12/13 05:52:55 > @@ -2189,9 +2189,22 @@ > * to softupdates re-dirtying the buffer. In the latter > * case, B_CACHE is set after the first write completes, > * preventing further loops. > + * > + * NOTE! b*write() sets B_CACHE. If we cleared B_CACHE > + * above while extending the buffer, we cannot allow the > + * buffer to remain with B_CACHE set after the write > + * completes or it will represent a corrupt state. To > + * deal with this we set B_NOCACHE to scrap the buffer > + * after the write. > + * > + * We might be able to do something fancy, like setting > + * B_CACHE in bwrite() except if B_DELWRI is already set, > + * so the below call doesn't set B_CACHE, but that gets real > + * confusing. This is much easier. > */ > > if ((bp->b_flags & (B_CACHE|B_DELWRI)) == B_DELWRI) { > + bp->b_flags |= B_NOCACHE; > VOP_BWRITE(bp->b_vp, bp); > goto loop; > } > Index: nfs/nfs_bio.c > =================================================================== > RCS file: /home/ncvs/src/sys/nfs/Attic/nfs_bio.c,v > retrieving revision 1.83.2.1 > diff -u -r1.83.2.1 nfs_bio.c > --- nfs/nfs_bio.c 2001/11/18 07:10:59 1.83.2.1 > +++ nfs/nfs_bio.c 2001/12/13 05:52:10 > @@ -193,8 +193,14 @@ > vm_page_set_validclean(m, 0, size - toff); > /* handled by vm_fault now */ > /* vm_page_zero_invalid(m, TRUE); */ > + } else { > + /* > + * Read operation was short. If no error occured > + * we may have hit a zero-fill section. We simply > + * leave valid set to 0. > + */ > + ; > } > - > if (i != ap->a_reqpage) { > /* > * Whether or not to leave the page activated is up in > @@ -896,14 +902,12 @@ > else > bcount = np->n_size - (off_t)lbn * biosize; > } > - > - bp = nfs_getcacheblk(vp, lbn, bcount, p); > - > if (uio->uio_offset + n > np->n_size) { > np->n_size = uio->uio_offset + n; > np->n_flag |= NMODIFIED; > vnode_pager_setsize(vp, np->n_size); > } > + bp = nfs_getcacheblk(vp, lbn, bcount, p); > } > > if (!bp) { > @@ -1409,11 +1413,13 @@ > io.iov_len = uiop->uio_resid = bp->b_bcount; > io.iov_base = bp->b_data; > uiop->uio_rw = UIO_READ; > + > switch (vp->v_type) { > case VREG: > uiop->uio_offset = ((off_t)bp->b_blkno) * DEV_BSIZE; > nfsstats.read_bios++; > error = nfs_readrpc(vp, uiop, cr); > + > if (!error) { > if (uiop->uio_resid) { > /* > @@ -1425,7 +1431,7 @@ > * writes, but that is not possible any longer. > */ > int nread = bp->b_bcount - uiop->uio_resid; > - int left = bp->b_bcount - nread; > + int left = uiop->uio_resid; > > if (left > 0) > bzero((char *)bp->b_data + nread, left); > Index: nfs/nfs_vnops.c > =================================================================== > RCS file: /home/ncvs/src/sys/nfs/Attic/nfs_vnops.c,v > retrieving revision 1.150.2.4 > diff -u -r1.150.2.4 nfs_vnops.c > --- nfs/nfs_vnops.c 2001/08/05 00:23:58 1.150.2.4 > +++ nfs/nfs_vnops.c 2001/12/13 04:23:51 > @@ -710,7 +710,22 @@ > */ > if (vp->v_mount->mnt_flag & MNT_RDONLY) > return (EROFS); > - vnode_pager_setsize(vp, vap->va_size); > + > + /* > + * We run vnode_pager_setsize() early (why?), > + * we must set np->n_size now to avoid vinvalbuf > + * V_SAVE races that might setsize a lower > + * value. > + */ > + tsize = np->n_size; > + np->n_size = vap->va_size; > +#if 1 > + if (np->n_size < tsize) > + error = vtruncbuf(vp, ap->a_cred, ap->a_p, vap->va_size, vp->v_mount->mnt_stat.f_iosize); > + else > +#endif > + vnode_pager_setsize(vp, vap->va_size); > + > if (np->n_flag & NMODIFIED) { > if (vap->va_size == 0) > error = nfs_vinvalbuf(vp, 0, > @@ -719,12 +734,12 @@ > error = nfs_vinvalbuf(vp, V_SAVE, > ap->a_cred, ap->a_p, 1); > if (error) { > + np->n_size = tsize; > vnode_pager_setsize(vp, np->n_size); > return (error); > } > } > - tsize = np->n_size; > - np->n_size = np->n_vattr.va_size = vap->va_size; > + np->n_vattr.va_size = vap->va_size; > }; > } else if ((vap->va_mtime.tv_sec != VNOVAL || > vap->va_atime.tv_sec != VNOVAL) && (np->n_flag & NMODIFIED) && > @@ -1119,10 +1134,12 @@ > m_freem(mrep); > tsiz -= retlen; > if (v3) { > - if (eof || retlen == 0) > + if (eof || retlen == 0) { > tsiz = 0; > - } else if (retlen < len) > + } > + } else if (retlen < len) { > tsiz = 0; > + } > } > nfsmout: > return (error); > Index: ufs/ffs/ffs_inode.c > =================================================================== > RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_inode.c,v > retrieving revision 1.56.2.3 > diff -u -r1.56.2.3 ffs_inode.c > --- ufs/ffs/ffs_inode.c 2001/11/20 20:27:27 1.56.2.3 > +++ ufs/ffs/ffs_inode.c 2001/12/12 23:43:36 > @@ -244,6 +244,10 @@ > if (error) { > return (error); > } > + if (length > 0 && DOINGSOFTDEP(ovp)) { > + if ((error = VOP_FSYNC(ovp, cred, MNT_WAIT, p)) != 0) > + return (error); > + } > oip->i_size = length; > size = blksize(fs, oip, lbn); > if (ovp->v_type != VDIR) > @@ -359,6 +363,10 @@ > if (newspace == 0) > panic("ffs_truncate: newspace"); > if (oldspace - newspace > 0) { > + /* > + * XXX Softupdates, adjust queued directblock > + * in place rather then the second FSYNC above? > + */ > /* > * Block number of space to be free'd is > * the old block # plus the number of frags > Index: vm/vnode_pager.c > =================================================================== > RCS file: /home/ncvs/src/sys/vm/vnode_pager.c,v > retrieving revision 1.116.2.5 > diff -u -r1.116.2.5 vnode_pager.c > --- vm/vnode_pager.c 2001/11/09 03:21:22 1.116.2.5 > +++ vm/vnode_pager.c 2001/12/13 02:49:39 > @@ -310,6 +310,20 @@ > vm_pager_unmap_page(kva); > > /* > + * XXX work around SMP data integrity race > + * by unmapping the page from user processes. > + * The garbage we just cleared may be mapped > + * to a user process running on another cpu > + * and this code is not running through normal > + * I/O channels which handle SMP issues for > + * us, so unmap page to synchronize all cpus. > + * > + * XXX should vm_pager_unmap_page() have > + * dealt with this? > + */ > + vm_page_protect(m, VM_PROT_NONE); > + > + /* > * Clear out partial-page dirty bits. This > * has the side effect of setting the valid > * bits, but that is ok. There are a bunch > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > --- Geoff Mohler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 22:19:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ardbeg.meer.net (ardbeg.meer.net [209.157.152.23]) by hub.freebsd.org (Postfix) with ESMTP id 852B237B417; Wed, 12 Dec 2001 22:19:25 -0800 (PST) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by ardbeg.meer.net (8.11.3/8.11.3) with ESMTP id fBD6JPD85355; Wed, 12 Dec 2001 22:19:25 -0800 (PST) Received: from neville-neil.com ([209.157.133.226]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id WAA1011588; Wed, 12 Dec 2001 22:18:31 -0800 (PST) Message-Id: <200112130618.WAA1011588@meer.meer.net> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: freebsd-announce@freebsd.org, freebsd-hackers@freebsd.org Subject: Call for Works In Progress talks for BSDCon '02 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Dec 2001 22:18:31 -0800 From: "George V. Neville-Neil" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Folks, This is the first call for participation in the Works In Progress session at BSD Con '02 in San Francisco. Works In Progress talks are 5 to 10 minute presentations of the work you're doing with BSD that would be of interest to other people. Please send a subject, short abstract (3-4 sentences), and a contact email to bsdcon-wips@usenix.org. Do NOT reply directly to this email. General information on the conference can be found at: http://www.usenix.org/events/bsdcon02/ Thanks, George V. Neville-Neil (WIPs Coordinator) PS Apologies if you get this more than once. -- George V. Neville-Neil gnn@neville-neil.com NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 22:22:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 254C937B416; Wed, 12 Dec 2001 22:22:35 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBD6LJS49988; Wed, 12 Dec 2001 22:21:19 -0800 (PST) (envelope-from dillon) Date: Wed, 12 Dec 2001 22:21:19 -0800 (PST) From: Matthew Dillon Message-Id: <200112130621.fBD6LJS49988@apollo.backplane.com> To: Geoff Mohler Cc: Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :Are any of these client-side performance upgrades as well as bug fixes? No, just bug fixes. The softupdates bug fix is server-side. All the other bug fixes are client side (so far). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 22:37:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from niwun.pair.com (niwun.pair.com [209.68.2.70]) by hub.freebsd.org (Postfix) with SMTP id 8001037B419 for ; Wed, 12 Dec 2001 22:37:48 -0800 (PST) Received: (qmail 61360 invoked by uid 3193); 13 Dec 2001 06:37:47 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 13 Dec 2001 06:37:47 -0000 Date: Thu, 13 Dec 2001 01:37:47 -0500 (EST) From: Mike Silbersack X-Sender: To: Matthew Dillon Cc: Geoff Mohler , Jordan Hubbard , Peter Wemm , Mike Smith , , Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) In-Reply-To: <200112130621.fBD6LJS49988@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 12 Dec 2001, Matthew Dillon wrote: > > : > :Are any of these client-side performance upgrades as well as bug fixes? > > No, just bug fixes. The softupdates bug fix is server-side. All > the other bug fixes are client side (so far). > > -Matt Does the softupdates fix affect normal ffs operations as well? Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 22:48:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from speedracer.speedtoys.com (mail.speedtoys.com [66.80.10.170]) by hub.freebsd.org (Postfix) with ESMTP id D131837B417; Wed, 12 Dec 2001 22:48:09 -0800 (PST) Received: from localhost (gemohler@localhost) by speedracer.speedtoys.com (8.11.3/8.11.1) with ESMTP id fBD786n30398; Wed, 12 Dec 2001 23:08:06 -0800 (PST) Date: Wed, 12 Dec 2001 23:08:05 -0800 (PST) From: Geoff Mohler X-Sender: gemohler@speedracer.speedtoys.com To: Matthew Dillon Cc: Peter Wemm , Jordan Hubbard , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: <200112130151.fBD1pVG27177@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I suppose while were on the topic.. Are there any hidden secrets to eeking out more performance from the BSD NFS client (other than version types and the normal fstab tweaks). Im the CS Labs manager at NetApp..and Im always trying to store away a secret here or there when someone comes to me with a problem in the field. FreeBSD since v2..rock on! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 22:53:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 10B7437B405; Wed, 12 Dec 2001 22:53:46 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBD6pxO55283; Wed, 12 Dec 2001 22:51:59 -0800 (PST) (envelope-from dillon) Date: Wed, 12 Dec 2001 22:51:59 -0800 (PST) From: Matthew Dillon Message-Id: <200112130651.fBD6pxO55283@apollo.backplane.com> To: Mike Silbersack Cc: Geoff Mohler , Jordan Hubbard , Peter Wemm , Mike Smith , , Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Does the softupdates fix affect normal ffs operations as well? : :Mike "Silby" Silbersack Yes, we believe so. It's a bug in ftruncate()'s interaction with softupdates. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 22:57:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 157D137B405; Wed, 12 Dec 2001 22:57:46 -0800 (PST) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id fBD6nR273546; Wed, 12 Dec 2001 22:49:27 -0800 (PST) (envelope-from dg) Date: Wed, 12 Dec 2001 22:49:27 -0800 From: David Greenman To: Matthew Dillon Cc: Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) Message-ID: <20011212224927.A73226@nexus.root.com> References: <58885.1008217148@winston.freebsd.org> <200112130608.fBD689K49906@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200112130608.fBD689K49906@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Dec 12, 2001 at 10:08:09PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Very cool. Good job! -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 23: 0:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D513E37B417; Wed, 12 Dec 2001 23:00:50 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBD6xZt55360; Wed, 12 Dec 2001 22:59:35 -0800 (PST) (envelope-from dillon) Date: Wed, 12 Dec 2001 22:59:35 -0800 (PST) From: Matthew Dillon Message-Id: <200112130659.fBD6xZt55360@apollo.backplane.com> To: Geoff Mohler Cc: Peter Wemm , Jordan Hubbard , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :I suppose while were on the topic.. : :Are there any hidden secrets to eeking out more performance from the BSD :NFS client (other than version types and the normal fstab tweaks). : :Im the CS Labs manager at NetApp..and Im always trying to store away a :secret here or there when someone comes to me with a problem in the field. : :FreeBSD since v2..rock on! * Make sure you don't have packet loss in your network (test with larger packets, aka ping -s 8192 rather then just ping, and perhaps test with a pattern (-p)). * Run a sufficient number of nfsd's on the server side, depending on load. 4 or 8 is typical. * Run nfsiod's on the client side. I usually run 4. This will drastically improve read-ahead and, for example, can bump linear read speeds on a 100BaseTX network from 7 MBytes/sec to 11 MBytes/sec (full saturation). * Use NFS version 3 when possible (this is the default) * Sometimes playing around with the various attribute cache timeouts (see 'man mount_nfs') helps. Sometimes it doesn't. For extreme performance there are some zero-copy patches floating around which have not been integrated into the main tree. Generally, though, your NFS performance is going to be ultimately limited by your server's disk performance. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 12 23:17: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from niwun.pair.com (niwun.pair.com [209.68.2.70]) by hub.freebsd.org (Postfix) with SMTP id 64ECE37B416 for ; Wed, 12 Dec 2001 23:16:57 -0800 (PST) Received: (qmail 64071 invoked by uid 3193); 13 Dec 2001 07:16:56 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 13 Dec 2001 07:16:56 -0000 Date: Thu, 13 Dec 2001 02:16:56 -0500 (EST) From: Mike Silbersack X-Sender: To: Matthew Dillon Cc: Geoff Mohler , Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: <200112130659.fBD6xZt55360@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 12 Dec 2001, Matthew Dillon wrote: > :I suppose while were on the topic.. > : > :Are there any hidden secrets to eeking out more performance from the BSD > :NFS client (other than version types and the normal fstab tweaks). > : > :Im the CS Labs manager at NetApp..and Im always trying to store away a > :secret here or there when someone comes to me with a problem in the field. > : > :FreeBSD since v2..rock on! > > For extreme performance there are some zero-copy patches floating around > which have not been integrated into the main tree. Generally, though, > your NFS performance is going to be ultimately limited by your server's > disk performance. > > -Matt > Matthew Dillon And if you hadn't heard, Matt just fixed a couple of bugs in the tcp stack which improves NFS greatly. It sounds like after this round of NFS fixes, the first answer to NFS questions should be: Upgrade to 4.5! Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 0: 2:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 471BE37B405; Thu, 13 Dec 2001 00:02:09 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBD80bb55582; Thu, 13 Dec 2001 00:00:37 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Dec 2001 00:00:37 -0800 (PST) From: Matthew Dillon Message-Id: <200112130800.fBD80bb55582@apollo.backplane.com> To: David Greenman Cc: Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) References: <58885.1008217148@winston.freebsd.org> <200112130608.fBD689K49906@apollo.backplane.com> <20011212224927.A73226@nexus.root.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : : Very cool. Good job! : :-DG : :David Greenman :Co-founder, The FreeBSD Project - http://www.freebsd.org Thanks! I'm slowly whacking the bugs. I just fixed another one... vtruncbuf() handles the buffers beyond the file EOF but doesn't handle the buffer straddling the truncation point, so I had to augment the NFS client's truncation code to deal with that. With that fixed the tester program got to 34483 operations before finding a problem. Hopefully I'm in the home stretch now :-) What I really love about this program is that the problems are so repeatable. So far the same failure occurs at exactly the same place, every time. It makes it unbelievably easy to track the bugs down. I think I can make it perfect. I'll post another patch tomorrow. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 0:20:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id C4C0937B41A; Thu, 13 Dec 2001 00:20:38 -0800 (PST) Received: from winston.freebsd.org (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id fBD8Jsq59691; Thu, 13 Dec 2001 00:19:54 -0800 (PST) (envelope-from jkh@winston.freebsd.org) To: Matthew Dillon Cc: David Greenman , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) In-Reply-To: Message from Matthew Dillon of "Thu, 13 Dec 2001 00:00:37 PST." <200112130800.fBD80bb55582@apollo.backplane.com> Date: Thu, 13 Dec 2001 00:19:53 -0800 Message-ID: <59687.1008231593@winston.freebsd.org> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Thanks! I'm slowly whacking the bugs. I just fixed another one... That's awesome... I'd hoped this program might help you find a few things, but I never expected you to find so many bugs in NFS so... quickly! I certainly didn't expect you to tickle any local filesystem problems either. :) > I think I can make it perfect. I'll post another patch tomorrow. Thanks. With 4.5 imminent these improvements are, to say state the flagrantly obvious, very timely indeed. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 1:39:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-d.strhg1.mi.home.com [24.13.43.207]) by hub.freebsd.org (Postfix) with ESMTP id 6092137B41A; Thu, 13 Dec 2001 01:39:08 -0800 (PST) Received: by turtle.looksharp.net (Postfix, from userid 1003) id 83BED3EBE; Thu, 13 Dec 2001 04:39:58 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by turtle.looksharp.net (Postfix) with ESMTP id 80469BAA6; Thu, 13 Dec 2001 04:39:58 -0500 (EST) Date: Thu, 13 Dec 2001 04:39:58 -0500 (EST) From: "Brandon D. Valentine" To: Matthew Dillon Cc: Jordan Hubbard , Peter Wemm , Mike Smith , , Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) In-Reply-To: <200112130608.fBD689K49906@apollo.backplane.com> Message-ID: <20011213043851.Y56723-100000@turtle.looksharp.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 12 Dec 2001, Matthew Dillon wrote: > All I can say is... holy shit! Dude, you kick ass. At work I've been dealing with Linux's crappy NFS implementation for years, while FreeBSD has always been pretty damn good by comparison. Linux finally got a decent amount of performance under 2.4 (which finally does NFSv3 to hosts other than other Linux boxen), but it still can't touch the FreeBSD NFS implementation. The more robust you make it the easier it is for me to argue for deployment of more FreeBSD systems in NFS server roles. The only advantage Linux has got right now is XFS, which is admittedly a pretty large advantage on multi terabyte filesystems where fsck is impossible. Brandon D. Valentine -- "Iam mens praetrepidans avet vagari." - G. Valerius Catullus, Carmina, XLVI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 2:20:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by hub.freebsd.org (Postfix) with ESMTP id 9896B37B417 for ; Thu, 13 Dec 2001 02:20:16 -0800 (PST) Received: from era_nt3.erabouw.nl (erabouw.nl [194.109.63.85]) by smtpzilla2.xs4all.nl (8.12.0/8.12.0) with ESMTP id fBDAE1gV037464; Thu, 13 Dec 2001 11:14:06 +0100 (CET) Received: from mta.excite.com (1Cust46.tnt2.dfw9.da.uu.net [63.62.208.46]) by era_nt3.erabouw.nl with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YX626P7P; Thu, 13 Dec 2001 11:02:59 +0100 Message-ID: <000012182a04$00007bcc$0000406e@mta.excite.com> To: From: 888salescom@excite.com Subject: Marketing is the LifeBlood of Your Business! Date: Thu, 13 Dec 2001 04:00:06 -1800 MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Reply-To: 888Salescom8@excite.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG American Mailing



    All transactions secured through


    THIS COULD BE YOUR
    FIRM’S MESSAGE…

    REACHING THE MARKET SEGMENT
    YOU NEED TO IMPACT!
    L= et us show you how we can develop, produce,
    TARGET and DELIVER your firm’s interest specific me= ssage.
    • You need your time-sensitive announcement delivered…= ;NOW!
    • You need QUALIFIED leads for your business…NOW!
    • You need to drive traffic to your web site…NOW!
      Let us show you how we can expand your client base:
    • H= TML, FLASH, Streaming Content, Multimedia Attachments
    • D= ynamic E-Marketing Solutions
    • N= ational and International
    • D= emographic Specific
    • I= nterest Specific
     

    Have one of our professionals contact you right away for your E= -Marketing Solution.
    Please click here and complete our inquiry form.

    "Just take a look at some of our customers"<= /font>

    Hewlett Packard, GTE, McDonalds, Subway, United Way,
    American Red Cross,City of Anaheim, Vital Scan, Westec=
     
    If you think, that you will not benefit from this correspondenc= e, please c= lick here
     
    To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 2:59:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3C93637B416; Thu, 13 Dec 2001 02:59:45 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBDAwSR66790; Thu, 13 Dec 2001 02:58:28 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Dec 2001 02:58:28 -0800 (PST) From: Matthew Dillon Message-Id: <200112131058.fBDAwSR66790@apollo.backplane.com> To: Jordan Hubbard Cc: David Greenman , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) References: <59687.1008231593@winston.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG @#$@#$ crap. I think I found a dirty-mmap edge case with truncation. It requires a change to vm_page_set_validclean(), which of course is one of the core routines in the VM system. Basically what happens is that ftruncate() calls vnode_pager_setsize() which eventually calls vm_page_set_validclean(). If you happened to mmap() the truncation point shared R+W and dirty it, then truncate to something that isn't a multiple DEV_BSIZE.. for example, if you were to truncate to an offset of '10', and a buffer has not been instantiated or marked dirty for the block yet, then the truncate operation will clear the dirty bit on the page and your 10 bytes of dirty data will never get synced and will disappear if the page is freed. vm_page_set_validclean() needs to set the valid bits and clear the dirty bits associated with (base,size) within the page. If base and/or size is unaligned then the valid and dirty bits encompass the bits associated with any overlapping DEV_BSIZEd chunks. This is fine for setting valid, but not correct when clearing dirty. Only dirty bits for DEV_BSIZE chunks that are fully enclosed in the range can be cleared. The fix is easy, but a little scary due to being right smack in the middle of the VM system. -- In anycase, I think I got it licked. I'm going to run this nfs tester program overnight on a local filesystem, NFSv2, and NFSv3 mount. Cross your fingers! If it survives I'll start comitting to -current tomorrow. I give it about a 70% chance of surviving. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 4:28:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apache.metrocom.ru (www.metrocom.ru [195.5.128.139]) by hub.freebsd.org (Postfix) with ESMTP id C93BB37B41D for ; Thu, 13 Dec 2001 04:28:39 -0800 (PST) Received: from apache.metrocom.ru (apache.metrocom.ru [195.5.128.150]) by apache.metrocom.ru (8.12.1/8.12.1) with ESMTP id fBDCSYmf012776; Thu, 13 Dec 2001 15:28:34 +0300 (MSK) Date: Thu, 13 Dec 2001 15:28:34 +0300 (MSK) From: Varshavchick Alexander To: Dan Nelson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 4G phisical memory kernel trap - the solution In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 5 Dec 2001, Varshavchick Alexander wrote: > Thank you Dan, can you please give a more detailed description as how to > do it? > > > You can run a 4.4 kernel on a 4.2 userland with no problem. On some of > > my production boxes, I'm running a 4.4 kernel on a 4.0 userland :) You > > should be able to build a 4.4 kernel, copy it to /kernel.test, and do a > > quick reboot to see if it works. That way you can fall back to the 4.2 > > kernel if you have problems. > > > > -- > > Dan Nelson > > dnelson@allantgroup.com The system itself worked with 4.4 stable kernel on a 4.2 userland, but the apache experienced problems in killing unused processes - the apache processes stacked to the MaxProcess number and just sat there. So I upgraded the whole system to 4.4 after it, and it all worked without problems with 4G phisical memory. My big thanks to all who helped in solving this issue! Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)118-3322, 118-3115(fax) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 5:46:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from niwun.pair.com (niwun.pair.com [209.68.2.70]) by hub.freebsd.org (Postfix) with SMTP id E49BB37BECB for ; Thu, 13 Dec 2001 05:44:52 -0800 (PST) Received: (qmail 2330 invoked by uid 3193); 13 Dec 2001 13:44:51 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 13 Dec 2001 13:44:51 -0000 Date: Thu, 13 Dec 2001 08:44:51 -0500 (EST) From: Mike Silbersack X-Sender: To: Mike Smith Cc: Matthew Dillon , Jordan Hubbard , , Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: <200112122345.fBCNjr103779@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 12 Dec 2001, Mike Smith wrote: > Many of the key issues in making OS X NFS work were related to its > interaction with the UBC and the subtly different VFS semantics, > although the same issues probably exist in different form in the > FreeBSD code. I get dragged into some really shocking corridor > discussions every now and then. 8) > > = Mike I just thought of something regarding fsx.c - I think it perhaps needs another set of test vectors added. There's a third way we read files now: through sendfile(). If someone has time, it might be worth adding an OP_SENDFILEREAD case and seeing if it shows any additional bugs. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 6:15:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brea.mc.mpls.visi.com (brea.mc.mpls.visi.com [208.42.156.100]) by hub.freebsd.org (Postfix) with ESMTP id 8501937B417 for ; Thu, 13 Dec 2001 06:15:44 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by brea.mc.mpls.visi.com (Postfix) with ESMTP id 9A9882DE235; Thu, 13 Dec 2001 08:15:43 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBDEFGQ21551; Thu, 13 Dec 2001 08:15:16 -0600 (CST) (envelope-from hawkeyd) Date: Thu, 13 Dec 2001 08:15:16 -0600 From: D J Hawkey Jr To: Michael Lucas Cc: hackers@freebsd.org Subject: ANNOUNCE: FreeBSD Backports site Message-ID: <20011213081516.A21232@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011209100855.A22942@sheol.localdomain> <20011209084620.V14858-100000@coredump.scriptkiddie.org> <20011209111523.A23357@sheol.localdomain> <20011209175137.B13554@clan.nothing-going-on.org> <20011209121703.A23726@sheol.localdomain> <20011210080032.A4215@canyon.nothing-going-on.org> <20011210152414.A1367@sheol.localdomain> <20011211191403.B82053@canyon.nothing-going-on.org> <20011211150459.A8415@sheol.localdomain> <20011211162304.A39837@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011211162304.A39837@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Tue, Dec 11, 2001 at 04:23:05PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi All, On Dec 11, at 04:23 PM, Michael Lucas wrote: > > > For those that're interested (and have the time), it's at > > http://www.visi.com/~hawkeyd/freebsd-backports.html > > for review/critique. It's only a WIP at this point; please don't do anything > > to publicize it. I'll mail hackers@ again when it's done, for final review/ > > critique. > > Oh. Well, okay, you put up what you got. Effective about an hour ago, what I'm considering the final draft is at the above URL. I'll be asking my ISP to set up a counter for it shortly. Anyone want to proofread it for me? > Good start, now let's get some patches up there. :) Five are up now. As soon as I get feedback from a guinea pig^H^H^H^H^H^H^H^H^H^Htester who was foolish^H^H^H^H^H^H^Hkind enough to volunteer his systems to test my patches, another will be put up (it's a commented link right now). Consider this the announcement of a new FreeBSD support site. So, now it's my turn to throw down the gauntlet: Who among you wants to risk your 4.2 or 4.3 system to an unknown hacker's patches? :-) > Michael Lucas Wish me luck! Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 7:30:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 41B9237B419 for ; Thu, 13 Dec 2001 07:30:48 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.6/8.11.6) id fBDFUZr01736; Thu, 13 Dec 2001 09:30:36 -0600 (CST) (envelope-from dan) Date: Thu, 13 Dec 2001 09:30:35 -0600 From: Dan Nelson To: Mike Silbersack Cc: Matthew Dillon , Geoff Mohler , hackers@FreeBSD.ORG Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step Message-ID: <20011213153035.GB56448@dan.emsphone.com> References: <200112130659.fBD6xZt55360@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.2i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Dec 13), Mike Silbersack said: > On Wed, 12 Dec 2001, Matthew Dillon wrote: > > Geoff Mohler wrote: > > :Are there any hidden secrets to eeking out more performance from > > :the BSD NFS client (other than version types and the normal fstab > > :tweaks). > > And if you hadn't heard, Matt just fixed a couple of bugs in the tcp > stack which improves NFS greatly. It sounds like after this round of > NFS fixes, the first answer to NFS questions should be: Upgrade to > 4.5! I don't even bother with TCP mounts; my default amd rule says proto=udp. Is there any reason to add the overhead of the TCP stack if you're not leaving your own ethernet? You should be able to easily saturate a 100mbit link with FreeBSD 4.* machines, and I can do 15-20MB/sec with Netgear GA620 gigabit nics (SMP 2 x pIII/600). -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 8:47:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from speedracer.speedtoys.com (mail.speedtoys.com [66.80.10.170]) by hub.freebsd.org (Postfix) with ESMTP id 0B77937B405 for ; Thu, 13 Dec 2001 08:47:19 -0800 (PST) Received: from localhost (gemohler@localhost) by speedracer.speedtoys.com (8.11.3/8.11.1) with ESMTP id fBDH7BH54315; Thu, 13 Dec 2001 09:07:11 -0800 (PST) Date: Thu, 13 Dec 2001 09:07:11 -0800 (PST) From: Geoff Mohler X-Sender: gemohler@speedracer.speedtoys.com To: Mike Silbersack Cc: Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matt didnt feel the fixes were primarily performance related, just bug fixes. On Thu, 13 Dec 2001, Mike Silbersack wrote: > > On Wed, 12 Dec 2001, Matthew Dillon wrote: > > > :I suppose while were on the topic.. > > : > > :Are there any hidden secrets to eeking out more performance from the BSD > > :NFS client (other than version types and the normal fstab tweaks). > > : > > :Im the CS Labs manager at NetApp..and Im always trying to store away a > > :secret here or there when someone comes to me with a problem in the field. > > : > > :FreeBSD since v2..rock on! > > > > For extreme performance there are some zero-copy patches floating around > > which have not been integrated into the main tree. Generally, though, > > your NFS performance is going to be ultimately limited by your server's > > disk performance. > > > > -Matt > > Matthew Dillon > > And if you hadn't heard, Matt just fixed a couple of bugs in the tcp stack > which improves NFS greatly. It sounds like after this round of NFS fixes, > the first answer to NFS questions should be: Upgrade to 4.5! > > Mike "Silby" Silbersack > > --- Geoff Mohler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 8:59:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from parhelion.firedrake.org (parhelion.firedrake.org [212.135.138.219]) by hub.freebsd.org (Postfix) with ESMTP id C70EC37B420 for ; Thu, 13 Dec 2001 08:58:39 -0800 (PST) Received: from float by parhelion.firedrake.org with local (Exim 3.32 #1 (Debian)) id 16EZBp-0006Fx-00; Thu, 13 Dec 2001 16:58:33 +0000 Date: Thu, 13 Dec 2001 16:58:33 +0000 To: Jordan Hubbard Cc: hackers@freebsd.org Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step Message-ID: <20011213165833.A23824@parhelion.firedrake.org> Mail-Followup-To: Jordan Hubbard , hackers@freebsd.org References: <200112121623.fBCGNuY52543@winston.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200112121623.fBCGNuY52543@winston.freebsd.org> User-Agent: Mutt/1.3.23i From: void Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Has anyone brought this code to the attention of the NetBSD people? I imagine that they would be interested. If not, I will forward it along myself, as soon as I determine the appropriate list. (List recommendations from the dual citizens here are welcome.) On Wed, Dec 12, 2001 at 08:23:56AM -0800, Jordan Hubbard wrote: > It came up in a meeting today at Apple just how fragile the BSD NFS > implementation was before significant work was put in to stabilizing it, > and in that discussion came up a little test tool written originally by > Avie Tevanian and subsequently improved by one of the folks here. > > This tool basically tries to do everything it can (legally) to confuse an > NFS server. It seeks around, does I/O to and truncates/changes the size > of a test file, all while doing everything it can to detect data corruption > or other signs of misbehavior which might result from out-of-order replies > or any other previously-observed NFS pathology. Very few NFS implementations > apparently survive this test and FreeBSD's is no exception. The sources are > provided below, courtesy of Avie, for the education and enjoyment(?) of > anyone who's motivated to play with (or even pretends to understand) NFS. > > Usage: > cc fsx.c -o fsx > ./fsx /some/nfs/mounted/scratchfile > [ ** kaboom! ** ] > > I'm also trying to determine which of the fixes Apple has made to NFS might > be adapted to FreeBSD, something which is made more difficult by the fact > that much of the code was taken straight from 4.4 Lite some time back and > both operating systems have diverged significantly since then. Anyone > really keen on investigating this further themselves on it can also go to > http://www.opensource.apple.com/projects/darwin and register themselves > online (it's easy) to access the Darwin CVS repository, the module in > question being "xnu" (the Darwin kernel). Thanks. > > - Jordan > > /* > * Copyright (C) 1991, NeXT Computer, Inc. All Rights Reserverd. > * > * File: fsx.c > * Author: Avadis Tevanian, Jr. > * > * File system exerciser. > * > * Rewritten 8/98 by Conrad Minshall. > */ > > #include > #include > #ifdef _UWIN > # include > # include > # include > # include > # define MAP_FILE 0 > #else > # include > #endif > #include > #include > #include > #include > #include > #include > #include > #include > #include > #include > #include > > #define NUMPRINTCOLUMNS 32 /* # columns of data to print on each line */ > > /* > * A log entry is an operation and a bunch of arguments. > */ > > struct log_entry { > int operation; > int args[3]; > }; > > #define LOGSIZE 1000 > > struct log_entry oplog[LOGSIZE]; /* the log */ > int logptr = 0; /* current position in log */ > int logcount = 0; /* total ops */ > > /* > * Define operations > */ > > #define OP_READ 1 > #define OP_WRITE 2 > #define OP_TRUNCATE 3 > #define OP_CLOSEOPEN 4 > #define OP_MAPREAD 5 > #define OP_MAPWRITE 6 > #define OP_SKIPPED 7 > > #ifndef PAGE_SIZE > #define PAGE_SIZE 4096 > #endif > #define PAGE_MASK (PAGE_SIZE - 1) > > char *original_buf; /* a pointer to the original data */ > char *good_buf; /* a pointer to the correct data */ > char *temp_buf; /* a pointer to the current data */ > char *fname; /* name of our test file */ > int fd; /* fd for our test file */ > > off_t file_size = 0; > off_t biggest = 0; > char state[256]; > unsigned long testcalls = 0; /* calls to function "test" */ > > unsigned long simulatedopcount = 0; /* -b flag */ > int closeprob = 0; /* -c flag */ > int debug = 0; /* -d flag */ > unsigned long debugstart = 0; /* -D flag */ > unsigned long maxfilelen = 256 * 1024; /* -l flag */ > int sizechecks = 1; /* -n flag disables them */ > int maxoplen = 64 * 1024; /* -o flag */ > int quiet = 0; /* -q flag */ > unsigned long progressinterval = 0; /* -p flag */ > int readbdy = 1; /* -r flag */ > int style = 0; /* -s flag */ > int truncbdy = 1; /* -t flag */ > int writebdy = 1; /* -w flag */ > long monitorstart = -1; /* -m flag */ > long monitorend = -1; /* -m flag */ > int lite = 0; /* -L flag */ > long numops = -1; /* -N flag */ > int randomoplen = 1; /* -O flag disables it */ > int seed = 1; /* -S flag */ > int mapped_writes = 1; /* -W flag disables */ > int mapped_reads = 1; /* -R flag disables it */ > int fsxgoodfd = 0; > FILE * fsxlogf = NULL; > int badoff = -1; > int closeopen = 0; > > > void > prt(char *fmt, ...) > { > va_list args; > > va_start(args, fmt); > vfprintf(stdout, fmt, args); > if (fsxlogf) > vfprintf(fsxlogf, fmt, args); > va_end(args); > } > > void > prterr(char *prefix) > { > prt("%s%s%s\n", prefix, prefix ? ": " : "", strerror(errno)); > } > > > void > log4(int operation, int arg0, int arg1, int arg2) > { > struct log_entry *le; > > le = &oplog[logptr]; > le->operation = operation; > if (closeopen) > le->operation = ~ le->operation; > le->args[0] = arg0; > le->args[1] = arg1; > le->args[2] = arg2; > logptr++; > logcount++; > if (logptr >= LOGSIZE) > logptr = 0; > } > > > void > logdump(void) > { > int i, count, down; > struct log_entry *lp; > > prt("LOG DUMP (%d total operations):\n", logcount); > if (logcount < LOGSIZE) { > i = 0; > count = logcount; > } else { > i = logptr; > count = LOGSIZE; > } > for ( ; count > 0; count--) { > int opnum; > > opnum = i+1 + (logcount/LOGSIZE)*LOGSIZE; > prt("%d(%d mod 256): ", opnum, opnum%256); > lp = &oplog[i]; > if ((closeopen = lp->operation < 0)) > lp->operation = ~ lp->operation; > > switch (lp->operation) { > case OP_MAPREAD: > prt("MAPREAD\t0x%x thru 0x%x\t(0x%x bytes)", > lp->args[0], lp->args[0] + lp->args[1] - 1, > lp->args[1]); > if (badoff >= lp->args[0] && badoff < > lp->args[0] + lp->args[1]) > prt("\t***RRRR***"); > break; > case OP_MAPWRITE: > prt("MAPWRITE 0x%x thru 0x%x\t(0x%x bytes)", > lp->args[0], lp->args[0] + lp->args[1] - 1, > lp->args[1]); > if (badoff >= lp->args[0] && badoff < > lp->args[0] + lp->args[1]) > prt("\t******WWWW"); > break; > case OP_READ: > prt("READ\t0x%x thru 0x%x\t(0x%x bytes)", > lp->args[0], lp->args[0] + lp->args[1] - 1, > lp->args[1]); > if (badoff >= lp->args[0] && > badoff < lp->args[0] + lp->args[1]) > prt("\t***RRRR***"); > break; > case OP_WRITE: > prt("WRITE\t0x%x thru 0x%x\t(0x%x bytes)", > lp->args[0], lp->args[0] + lp->args[1] - 1, > lp->args[1]); > if (lp->args[0] > lp->args[2]) > prt(" HOLE"); > else if (lp->args[0] + lp->args[1] > lp->args[2]) > prt(" EXTEND"); > if ((badoff >= lp->args[0] || badoff >=lp->args[2]) && > badoff < lp->args[0] + lp->args[1]) > prt("\t***WWWW"); > break; > case OP_TRUNCATE: > down = lp->args[0] < lp->args[1]; > prt("TRUNCATE %s\tfrom 0x%x to 0x%x", > down ? "DOWN" : "UP", lp->args[1], lp->args[0]); > if (badoff >= lp->args[!down] && > badoff < lp->args[!!down]) > prt("\t******WWWW"); > break; > case OP_SKIPPED: > prt("SKIPPED (no operation)"); > break; > default: > prt("BOGUS LOG ENTRY (operation code = %d)!", > lp->operation); > } > if (closeopen) > prt("\n\t\tCLOSE/OPEN"); > prt("\n"); > i++; > if (i == LOGSIZE) > i = 0; > } > } > > > void > save_buffer(char *buffer, off_t bufferlength, int fd) > { > off_t ret; > ssize_t byteswritten; > > if (fd <= 0 || bufferlength == 0) > return; > > if (bufferlength > SSIZE_MAX) { > prt("fsx flaw: overflow in save_buffer\n"); > exit(67); > } > if (lite) { > off_t size_by_seek = lseek(fd, (off_t)0, L_XTND); > if (size_by_seek == (off_t)-1) > prterr("save_buffer: lseek eof"); > else if (bufferlength > size_by_seek) { > warn("save_buffer: .fsxgood file too short... will save 0x%qx bytes instead of 0x%qx\n", (unsigned long long)size_by_seek, > (unsigned long long)bufferlength); > bufferlength = size_by_seek; > } > } > > ret = lseek(fd, (off_t)0, SEEK_SET); > if (ret == (off_t)-1) > prterr("save_buffer: lseek 0"); > > byteswritten = write(fd, buffer, (size_t)bufferlength); > if (byteswritten != bufferlength) { > if (byteswritten == -1) > prterr("save_buffer write"); > else > warn("save_buffer: short write, 0x%x bytes instead of 0x%qx\n", > (unsigned)byteswritten, > (unsigned long long)bufferlength); > } > } > > > void > report_failure(int status) > { > logdump(); > > if (fsxgoodfd) { > if (good_buf) { > save_buffer(good_buf, file_size, fsxgoodfd); > prt("Correct content saved for comparison\n"); > prt("(maybe hexdump \"%s\" vs \"%s.fsxgood\")\n", > fname, fname); > } > close(fsxgoodfd); > } > exit(status); > } > > > #define short_at(cp) ((unsigned short)((*((unsigned char *)(cp)) << 8) | \ > *(((unsigned char *)(cp)) + 1))) > > void > check_buffers(unsigned offset, unsigned size) > { > unsigned char c, t; > unsigned i = 0; > unsigned n = 0; > unsigned op = 0; > unsigned bad = 0; > > if (bcmp(good_buf + offset, temp_buf, size) != 0) { > prt("READ BAD DATA: offset = 0x%x, size = 0x%x\n", > offset, size); > prt("OFFSET\tGOOD\tBAD\tRANGE\n"); > while (size > 0) { > c = good_buf[offset]; > t = temp_buf[i]; > if (c != t) { > if (n == 0) { > bad = short_at(&temp_buf[i]); > prt("0x%5x\t0x%04x\t0x%04x", offset, > short_at(&good_buf[offset]), bad); > op = temp_buf[offset & 1 ? i+1 : i]; > } > n++; > badoff = offset; > } > offset++; > i++; > size--; > } > if (n) { > prt("\t0x%5x\n", n); > if (bad) > prt("operation# (mod 256) for the bad data may be %u\n", ((unsigned)op & 0xff)); > else > prt("operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops\n"); > } else > prt("????????????????\n"); > report_failure(110); > } > } > > > void > check_size(void) > { > struct stat statbuf; > off_t size_by_seek; > > if (fstat(fd, &statbuf)) { > prterr("check_size: fstat"); > statbuf.st_size = -1; > } > size_by_seek = lseek(fd, (off_t)0, L_XTND); > if (file_size != statbuf.st_size || file_size != size_by_seek) { > prt("Size error: expected 0x%qx stat 0x%qx seek 0x%qx\n", > (unsigned long long)file_size, > (unsigned long long)statbuf.st_size, > (unsigned long long)size_by_seek); > report_failure(120); > } > } > > > void > check_trunc_hack(void) > { > struct stat statbuf; > > ftruncate(fd, (off_t)0); > ftruncate(fd, (off_t)100000); > fstat(fd, &statbuf); > if (statbuf.st_size != (off_t)100000) { > prt("no extend on truncate! not posix!\n"); > exit(130); > } > ftruncate(fd, 0); > } > > > void > doread(unsigned offset, unsigned size) > { > off_t ret; > unsigned iret; > > offset -= offset % readbdy; > if (size == 0) { > if (!quiet && testcalls > simulatedopcount) > prt("skipping zero size read\n"); > log4(OP_SKIPPED, OP_READ, offset, size); > return; > } > if (size + offset > file_size) { > if (!quiet && testcalls > simulatedopcount) > prt("skipping seek/read past end of file\n"); > log4(OP_SKIPPED, OP_READ, offset, size); > return; > } > > log4(OP_READ, offset, size, 0); > > if (testcalls <= simulatedopcount) > return; > > if (!quiet && (progressinterval && testcalls % progressinterval == 0 || > debug && > (monitorstart == -1 || > offset + size > monitorstart && > (monitorend == -1 || offset <= monitorend)))) > prt("%lu read\t0x%x thru\t0x%x\t(0x%x bytes)\n", testcalls, > offset, offset + size - 1, size); > ret = lseek(fd, (off_t)offset, SEEK_SET); > if (ret == (off_t)-1) { > prterr("doread: lseek"); > report_failure(140); > } > iret = read(fd, temp_buf, size); > if (iret != size) { > if (iret == -1) > prterr("doread: read"); > else > prt("short read: 0x%x bytes instead of 0x%x\n", > iret, size); > report_failure(141); > } > check_buffers(offset, size); > } > > > void > domapread(unsigned offset, unsigned size) > { > unsigned pg_offset; > unsigned map_size; > char *p; > > offset -= offset % readbdy; > if (size == 0) { > if (!quiet && testcalls > simulatedopcount) > prt("skipping zero size read\n"); > log4(OP_SKIPPED, OP_MAPREAD, offset, size); > return; > } > if (size + offset > file_size) { > if (!quiet && testcalls > simulatedopcount) > prt("skipping seek/read past end of file\n"); > log4(OP_SKIPPED, OP_MAPREAD, offset, size); > return; > } > > log4(OP_MAPREAD, offset, size, 0); > > if (testcalls <= simulatedopcount) > return; > > if (!quiet && (progressinterval && testcalls % progressinterval == 0 || > debug && > (monitorstart == -1 || > offset + size > monitorstart && > (monitorend == -1 || offset <= monitorend)))) > prt("%lu mapread\t0x%x thru\t0x%x\t(0x%x bytes)\n", testcalls, > offset, offset + size - 1, size); > > pg_offset = offset & PAGE_MASK; > map_size = pg_offset + size; > > if ((p = (char *)mmap(0, map_size, PROT_READ, MAP_FILE, fd, > (off_t)(offset - pg_offset))) == (char *)-1) { > prterr("domapread: mmap"); > report_failure(190); > } > memcpy(temp_buf, p + pg_offset, size); > if (munmap(p, map_size) != 0) { > prterr("domapread: munmap"); > report_failure(191); > } > > check_buffers(offset, size); > } > > > void > gendata(char *original_buf, char *good_buf, unsigned offset, unsigned size) > { > while (size--) { > good_buf[offset] = testcalls % 256; > if (offset % 2) > good_buf[offset] += original_buf[offset]; > offset++; > } > } > > > void > dowrite(unsigned offset, unsigned size) > { > off_t ret; > unsigned iret; > > offset -= offset % writebdy; > if (size == 0) { > if (!quiet && testcalls > simulatedopcount) > prt("skipping zero size write\n"); > log4(OP_SKIPPED, OP_WRITE, offset, size); > return; > } > > log4(OP_WRITE, offset, size, file_size); > > gendata(original_buf, good_buf, offset, size); > if (file_size < offset + size) { > if (file_size < offset) > bzero(good_buf + file_size, offset - file_size); > file_size = offset + size; > if (lite) { > warn("Lite file size bug in fsx!"); > report_failure(149); > } > } > > if (testcalls <= simulatedopcount) > return; > > if (!quiet && (progressinterval && testcalls % progressinterval == 0 || > debug && > (monitorstart == -1 || > offset + size > monitorstart && > (monitorend == -1 || offset <= monitorend)))) > prt("%lu write\t0x%x thru\t0x%x\t(0x%x bytes)\n", testcalls, > offset, offset + size - 1, size); > ret = lseek(fd, (off_t)offset, SEEK_SET); > if (ret == (off_t)-1) { > prterr("dowrite: lseek"); > report_failure(150); > } > iret = write(fd, good_buf + offset, size); > if (iret != size) { > if (iret == -1) > prterr("dowrite: write"); > else > prt("short write: 0x%x bytes instead of 0x%x\n", > iret, size); > report_failure(151); > } > } > > > void > domapwrite(unsigned offset, unsigned size) > { > unsigned pg_offset; > unsigned map_size; > off_t cur_filesize; > char *p; > > offset -= offset % writebdy; > if (size == 0) { > if (!quiet && testcalls > simulatedopcount) > prt("skipping zero size write\n"); > log4(OP_SKIPPED, OP_MAPWRITE, offset, size); > return; > } > cur_filesize = file_size; > > log4(OP_MAPWRITE, offset, size, 0); > > gendata(original_buf, good_buf, offset, size); > if (file_size < offset + size) { > if (file_size < offset) > bzero(good_buf + file_size, offset - file_size); > file_size = offset + size; > if (lite) { > warn("Lite file size bug in fsx!"); > report_failure(200); > } > } > > if (testcalls <= simulatedopcount) > return; > > if (!quiet && (progressinterval && testcalls % progressinterval == 0 || > debug && > (monitorstart == -1 || > offset + size > monitorstart && > (monitorend == -1 || offset <= monitorend)))) > prt("%lu mapwrite\t0x%x thru\t0x%x\t(0x%x bytes)\n", testcalls, > offset, offset + size - 1, size); > > if (file_size > cur_filesize) { > if (ftruncate(fd, file_size) == -1) { > prterr("domapwrite: ftruncate"); > exit(201); > } > } > pg_offset = offset & PAGE_MASK; > map_size = pg_offset + size; > > if ((p = (char *)mmap(0, map_size, PROT_READ | PROT_WRITE, > MAP_FILE | MAP_SHARED, fd, > (off_t)(offset - pg_offset))) == (char *)-1) { > prterr("domapwrite: mmap"); > report_failure(202); > } > memcpy(p + pg_offset, good_buf + offset, size); > if (msync(p, map_size, 0) != 0) { > prterr("domapwrite: msync"); > report_failure(203); > } > if (munmap(p, map_size) != 0) { > prterr("domapwrite: munmap"); > report_failure(204); > } > } > > > void > dotruncate(unsigned size) > { > int oldsize = file_size; > > size -= size % truncbdy; > if (size > biggest) { > biggest = size; > if (!quiet && testcalls > simulatedopcount) > prt("truncating to largest ever: 0x%x\n", size); > } > > log4(OP_TRUNCATE, size, (unsigned)file_size, 0); > > if (size > file_size) > bzero(good_buf + file_size, size - file_size); > file_size = size; > > if (testcalls <= simulatedopcount) > return; > > if (progressinterval && testcalls % progressinterval == 0 || > debug && (monitorstart == -1 || monitorend == -1 || > size <= monitorend)) > prt("%lu trunc\tfrom 0x%x to 0x%x\n", testcalls, oldsize, size); > if (ftruncate(fd, (off_t)size) == -1) { > prt("ftruncate1: %x\n", size); > prterr("dotruncate: ftruncate"); > report_failure(160); > } > } > > > void > writefileimage() > { > ssize_t iret; > > if (lseek(fd, (off_t)0, SEEK_SET) == (off_t)-1) { > prterr("writefileimage: lseek"); > report_failure(171); > } > iret = write(fd, good_buf, file_size); > if ((off_t)iret != file_size) { > if (iret == -1) > prterr("writefileimage: write"); > else > prt("short write: 0x%x bytes instead of 0x%qx\n", > iret, (unsigned long long)file_size); > report_failure(172); > } > if (lite ? 0 : ftruncate(fd, file_size) == -1) { > prt("ftruncate2: %qx\n", (unsigned long long)file_size); > prterr("writefileimage: ftruncate"); > report_failure(173); > } > } > > > void > docloseopen(void) > { > if (testcalls <= simulatedopcount) > return; > > if (debug) > prt("%lu close/open\n", testcalls); > if (close(fd)) { > prterr("docloseopen: close"); > report_failure(180); > } > fd = open(fname, O_RDWR, 0); > if (fd < 0) { > prterr("docloseopen: open"); > report_failure(181); > } > } > > > void > test(void) > { > unsigned long offset; > unsigned long size = maxoplen; > unsigned long rv = random(); > unsigned long op = rv % (3 + !lite + mapped_writes); > > /* turn off the map read if necessary */ > > if (op == 2 && !mapped_reads) > op = 0; > > if (simulatedopcount > 0 && testcalls == simulatedopcount) > writefileimage(); > > testcalls++; > > closeopen = (rv >> 3) < (1 << 28) / closeprob; > > if (debugstart > 0 && testcalls >= debugstart) > debug = 1; > > if (!quiet && testcalls < simulatedopcount && testcalls % 100000 == 0) > prt("%lu...\n", testcalls); > > /* > * READ: op = 0 > * WRITE: op = 1 > * MAPREAD: op = 2 > * TRUNCATE: op = 3 > * MAPWRITE: op = 3 or 4 > */ > if (lite ? 0 : op == 3 && (style & 1) == 0) /* vanilla truncate? */ > dotruncate(random() % maxfilelen); > else { > if (randomoplen) > size = random() % (maxoplen+1); > if (lite ? 0 : op == 3) > dotruncate(size); > else { > offset = random(); > if (op == 1 || op == (lite ? 3 : 4)) { > offset %= maxfilelen; > if (offset + size > maxfilelen) > size = maxfilelen - offset; > if (op != 1) > domapwrite(offset, size); > else > dowrite(offset, size); > } else { > if (file_size) > offset %= file_size; > else > offset = 0; > if (offset + size > file_size) > size = file_size - offset; > if (op != 0) > domapread(offset, size); > else > doread(offset, size); > } > } > } > if (sizechecks && testcalls > simulatedopcount) > check_size(); > if (closeopen) > docloseopen(); > } > > > void > cleanup(sig) > int sig; > { > if (sig) > prt("signal %d\n", sig); > prt("testcalls = %lu\n", testcalls); > exit(sig); > } > > > void > usage(void) > { > fprintf(stdout, "usage: %s", > "fsx [-dnqLOW] [-b opnum] [-c Prob] [-l flen] [-m start:end] [-o oplen] [-p progressinterval] [-r readbdy] [-s style] [-t truncbdy] [-w writebdy] [-D startingop] [-N numops] [-P dirpath] [-S seed] fname\n\ > -b opnum: beginning operation number (default 1)\n\ > -c P: 1 in P chance of file close+open at each op (default infinity)\n\ > -d: debug output for all operations\n\ > -l flen: the upper bound on file size (default 262144)\n\ > -m startop:endop: monitor (print debug output) specified byte range (default 0:infinity)\n\ > -n: no verifications of file size\n\ > -o oplen: the upper bound on operation size (default 65536)\n\ > -p progressinterval: debug output at specified operation interval\n\ > -q: quieter operation\n\ > -r readbdy: 4096 would make reads page aligned (default 1)\n\ > -s style: 1 gives smaller truncates (default 0)\n\ > -t truncbdy: 4096 would make truncates page aligned (default 1)\n\ > -w writebdy: 4096 would make writes page aligned (default 1)\n\ > -D startingop: debug output starting at specified operation\n\ > -L: fsxLite - no file creations & no file size changes\n\ > -N numops: total # operations to do (default infinity)\n\ > -O: use oplen (see -o flag) for every op (default random)\n\ > -P: save .fsxlog and .fsxgood files in dirpath (default ./)\n\ > -S seed: for random # generator (default 1) 0 gets timestamp\n\ > -W: mapped write operations DISabled\n\ > -R: read() system calls only (mapped reads disabled)\n\ > fname: this filename is REQUIRED (no default)\n"); > exit(90); > } > > > int > getnum(char *s, char **e) > { > int ret = -1; > > *e = (char *) 0; > ret = strtol(s, e, 0); > if (*e) > switch (**e) { > case 'b': > case 'B': > ret *= 512; > *e = *e + 1; > break; > case 'k': > case 'K': > ret *= 1024; > *e = *e + 1; > break; > case 'm': > case 'M': > ret *= 1024*1024; > *e = *e + 1; > break; > case 'w': > case 'W': > ret *= 4; > *e = *e + 1; > break; > } > return (ret); > } > > > int > main(int argc, char **argv) > { > int i, style, ch; > char *endp; > char goodfile[1024]; > char logfile[1024]; > > goodfile[0] = 0; > logfile[0] = 0; > > setvbuf(stdout, (char *)0, _IOLBF, 0); /* line buffered stdout */ > > while ((ch = getopt(argc, argv, "b:c:dl:m:no:p:qr:s:t:w:D:LN:OP:RS:W")) > != EOF) > switch (ch) { > case 'b': > simulatedopcount = getnum(optarg, &endp); > if (!quiet) > fprintf(stdout, "Will begin at operation %ld\n", > simulatedopcount); > if (simulatedopcount == 0) > usage(); > simulatedopcount -= 1; > break; > case 'c': > closeprob = getnum(optarg, &endp); > if (!quiet) > fprintf(stdout, > "Chance of close/open is 1 in %d\n", > closeprob); > if (closeprob <= 0) > usage(); > break; > case 'd': > debug = 1; > break; > case 'l': > maxfilelen = getnum(optarg, &endp); > if (maxfilelen <= 0) > usage(); > break; > case 'm': > monitorstart = getnum(optarg, &endp); > if (monitorstart < 0) > usage(); > if (!endp || *endp++ != ':') > usage(); > monitorend = getnum(endp, &endp); > if (monitorend < 0) > usage(); > if (monitorend == 0) > monitorend = -1; /* aka infinity */ > debug = 1; > case 'n': > sizechecks = 0; > break; > case 'o': > maxoplen = getnum(optarg, &endp); > if (maxoplen <= 0) > usage(); > break; > case 'p': > progressinterval = getnum(optarg, &endp); > if (progressinterval < 0) > usage(); > break; > case 'q': > quiet = 1; > break; > case 'r': > readbdy = getnum(optarg, &endp); > if (readbdy <= 0) > usage(); > break; > case 's': > style = getnum(optarg, &endp); > if (style < 0 || style > 1) > usage(); > break; > case 't': > truncbdy = getnum(optarg, &endp); > if (truncbdy <= 0) > usage(); > break; > case 'w': > writebdy = getnum(optarg, &endp); > if (writebdy <= 0) > usage(); > break; > case 'D': > debugstart = getnum(optarg, &endp); > if (debugstart < 1) > usage(); > break; > case 'L': > lite = 1; > break; > case 'N': > numops = getnum(optarg, &endp); > if (numops < 0) > usage(); > break; > case 'O': > randomoplen = 0; > break; > case 'P': > strncpy(goodfile, optarg, sizeof(goodfile)); > strcat(goodfile, "/"); > strncpy(logfile, optarg, sizeof(logfile)); > strcat(logfile, "/"); > break; > case 'R': > mapped_reads = 0; > break; > case 'S': > seed = getnum(optarg, &endp); > if (seed == 0) > seed = time(0) % 10000; > if (!quiet) > fprintf(stdout, "Seed set to %d\n", seed); > if (seed < 0) > usage(); > break; > case 'W': > mapped_writes = 0; > if (!quiet) > fprintf(stdout, "mapped writes DISABLED\n"); > break; > > default: > usage(); > /* NOTREACHED */ > } > argc -= optind; > argv += optind; > if (argc != 1) > usage(); > fname = argv[0]; > > signal(SIGHUP, cleanup); > signal(SIGINT, cleanup); > signal(SIGPIPE, cleanup); > signal(SIGALRM, cleanup); > signal(SIGTERM, cleanup); > signal(SIGXCPU, cleanup); > signal(SIGXFSZ, cleanup); > signal(SIGVTALRM, cleanup); > signal(SIGUSR1, cleanup); > signal(SIGUSR2, cleanup); > > initstate(seed, state, 256); > setstate(state); > fd = open(fname, O_RDWR|(lite ? 0 : O_CREAT|O_TRUNC), 0666); > if (fd < 0) { > prterr(fname); > exit(91); > } > strncat(goodfile, fname, 256); > strcat (goodfile, ".fsxgood"); > fsxgoodfd = open(goodfile, O_RDWR|O_CREAT|O_TRUNC, 0666); > if (fsxgoodfd < 0) { > prterr(goodfile); > exit(92); > } > strncat(logfile, fname, 256); > strcat (logfile, ".fsxlog"); > fsxlogf = fopen(logfile, "w"); > if (fsxlogf == NULL) { > prterr(logfile); > exit(93); > } > if (lite) { > off_t ret; > file_size = maxfilelen = lseek(fd, (off_t)0, L_XTND); > if (file_size == (off_t)-1) { > prterr(fname); > warn("main: lseek eof"); > exit(94); > } > ret = lseek(fd, (off_t)0, SEEK_SET); > if (ret == (off_t)-1) { > prterr(fname); > warn("main: lseek 0"); > exit(95); > } > } > original_buf = (char *) malloc(maxfilelen); > for (i = 0; i < maxfilelen; i++) > original_buf[i] = random() % 256; > good_buf = (char *) malloc(maxfilelen); > bzero(good_buf, maxfilelen); > temp_buf = (char *) malloc(maxoplen); > bzero(temp_buf, maxoplen); > if (lite) { /* zero entire existing file */ > ssize_t written; > > written = write(fd, good_buf, (size_t)maxfilelen); > if (written != maxfilelen) { > if (written == -1) { > prterr(fname); > warn("main: error on write"); > } else > warn("main: short write, 0x%x bytes instead of 0x%x\n", > (unsigned)written, maxfilelen); > exit(98); > } > } else > check_trunc_hack(); > > while (numops == -1 || numops--) > test(); > > if (close(fd)) { > prterr("close"); > report_failure(99); > } > prt("All operations completed A-OK!\n"); > > exit(0); > return 0; > } > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Ben "An art scene of delight I created this to be ..." -- Sun Ra To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 9: 0:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from speedracer.speedtoys.com (mail.speedtoys.com [66.80.10.170]) by hub.freebsd.org (Postfix) with ESMTP id B6E8A37B405 for ; Thu, 13 Dec 2001 09:00:19 -0800 (PST) Received: from localhost (gemohler@localhost) by speedracer.speedtoys.com (8.11.3/8.11.1) with ESMTP id fBDHKGY55686; Thu, 13 Dec 2001 09:20:16 -0800 (PST) Date: Thu, 13 Dec 2001 09:20:16 -0800 (PST) From: Geoff Mohler X-Sender: gemohler@speedracer.speedtoys.com To: Dan Nelson Cc: Mike Silbersack , Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: <20011213153035.GB56448@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG For some people, the overhead is an acceptible tradeoff to redundancy. Ever since Cisco released thier 6500 10/100 blades that to crappy buffering between a Gigabit NFS server (could be anything, just an example) and an 100Mbit client, people have somewhat been adding that overhead to thier CPU and data-rate budgets as "acceptable losses". On Thu, 13 Dec 2001, Dan Nelson wrote: > In the last episode (Dec 13), Mike Silbersack said: > > On Wed, 12 Dec 2001, Matthew Dillon wrote: > > > Geoff Mohler wrote: > > > :Are there any hidden secrets to eeking out more performance from > > > :the BSD NFS client (other than version types and the normal fstab > > > :tweaks). > > > > And if you hadn't heard, Matt just fixed a couple of bugs in the tcp > > stack which improves NFS greatly. It sounds like after this round of > > NFS fixes, the first answer to NFS questions should be: Upgrade to > > 4.5! > > I don't even bother with TCP mounts; my default amd rule says > proto=udp. Is there any reason to add the overhead of the TCP stack if > you're not leaving your own ethernet? > > You should be able to easily saturate a 100mbit link with FreeBSD 4.* > machines, and I can do 15-20MB/sec with Netgear GA620 gigabit nics (SMP > 2 x pIII/600). > > -- > Dan Nelson > dnelson@allantgroup.com > --- Geoff Mohler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 9: 3:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from niwun.pair.com (niwun.pair.com [209.68.2.70]) by hub.freebsd.org (Postfix) with SMTP id 1EAD037B42F for ; Thu, 13 Dec 2001 09:03:17 -0800 (PST) Received: (qmail 32903 invoked by uid 3193); 13 Dec 2001 17:03:16 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 13 Dec 2001 17:03:16 -0000 Date: Thu, 13 Dec 2001 12:03:16 -0500 (EST) From: Mike Silbersack X-Sender: To: Dan Nelson Cc: Matthew Dillon , Geoff Mohler , Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: <20011213153035.GB56448@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 13 Dec 2001, Dan Nelson wrote: > In the last episode (Dec 13), Mike Silbersack said: > > And if you hadn't heard, Matt just fixed a couple of bugs in the tcp > > stack which improves NFS greatly. It sounds like after this round of > > NFS fixes, the first answer to NFS questions should be: Upgrade to > > 4.5! > > I don't even bother with TCP mounts; my default amd rule says > proto=udp. Is there any reason to add the overhead of the TCP stack if > you're not leaving your own ethernet? > > You should be able to easily saturate a 100mbit link with FreeBSD 4.* > machines, and I can do 15-20MB/sec with Netgear GA620 gigabit nics (SMP > 2 x pIII/600). > > -- > Dan Nelson > dnelson@allantgroup.com I'm not a NFS user, so I can't comment on how NFS is normally used... but my guess would be that while UDP may be faster when you're benchmarking two computers, it'll cause a lot more congestion when you have 200 computers. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 9: 7:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from niwun.pair.com (niwun.pair.com [209.68.2.70]) by hub.freebsd.org (Postfix) with SMTP id EC41137B416 for ; Thu, 13 Dec 2001 09:07:46 -0800 (PST) Received: (qmail 34360 invoked by uid 3193); 13 Dec 2001 17:07:46 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 13 Dec 2001 17:07:46 -0000 Date: Thu, 13 Dec 2001 12:07:46 -0500 (EST) From: Mike Silbersack X-Sender: To: Geoff Mohler Cc: Matthew Dillon , Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 13 Dec 2001, Geoff Mohler wrote: > Matt didnt feel the fixes were primarily performance related, just bug > fixes. Right, the fact that they are bug fixes is what seems to be the most powerful reason to recommend upgrading. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 10:12:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AA88F37B416 for ; Thu, 13 Dec 2001 10:12:36 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBDICWm68171; Thu, 13 Dec 2001 10:12:32 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Dec 2001 10:12:32 -0800 (PST) From: Matthew Dillon Message-Id: <200112131812.fBDICWm68171@apollo.backplane.com> To: Geoff Mohler Cc: Mike Silbersack , hackers@FreeBSD.ORG Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :Matt didnt feel the fixes were primarily performance related, just bug :fixes. I meant just the last two days worth of NFS stuff are just bug fixes. The TCP fixes from earlier in the month are definitely performance fixes. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 10:38:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9CCB837B405; Thu, 13 Dec 2001 10:37:18 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBDIZuL70031; Thu, 13 Dec 2001 10:35:56 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Dec 2001 10:35:56 -0800 (PST) From: Matthew Dillon Message-Id: <200112131835.fBDIZuL70031@apollo.backplane.com> To: David Greenman Cc: Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: NFS Patch #4 -- survived overnight test. (was Re: Found NFS data corruption bug... (was Re:...)) References: <58885.1008217148@winston.freebsd.org> <200112130608.fBD689K49906@apollo.backplane.com> <20011212224927.A73226@nexus.root.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok, here is the latest patch set. This patch set survived an overnight run of the nfs torture test that Jordan posted... it got through 597,000 test calls over NFSv3, 367,000 over NFSv2, and 1.35 million on a local filesystem. This patch set is for -stable. It again has the old version of the softupdates patch (the new version will be MFC'd in two days from -current). In addition to previous bug fixes this patch fixes: * An edge case with shared R+W mmap()'s and truncate * A bug in my previous patch set related to a junked buffer * The straddle case for VM pages and buffer cache buffers when truncating. That's 8 significant bug fixes total, all rolled into one :-) I am going to forward port and test this stuff on -current today and probably commit it to -current tonight, with a 3-day turn to -stable. I would appreciate other VM gurus taking a look at the vm_page_set_validclean() changes. Are there still bugs in NFS? You bet! I'm sure there are bugs related to multiple clients and/or the server modifying files out from under a client, and I think the potential issue with nfsiod ordering that was posted to the list is a definite possibility. But this should go a long way to improving the rock solid reputation of our stack! -Matt Index: kern/vfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.242.2.13 diff -u -r1.242.2.13 vfs_bio.c --- kern/vfs_bio.c 2001/11/18 07:10:59 1.242.2.13 +++ kern/vfs_bio.c 2001/12/13 05:52:55 @@ -2189,9 +2189,22 @@ * to softupdates re-dirtying the buffer. In the latter * case, B_CACHE is set after the first write completes, * preventing further loops. + * + * NOTE! b*write() sets B_CACHE. If we cleared B_CACHE + * above while extending the buffer, we cannot allow the + * buffer to remain with B_CACHE set after the write + * completes or it will represent a corrupt state. To + * deal with this we set B_NOCACHE to scrap the buffer + * after the write. + * + * We might be able to do something fancy, like setting + * B_CACHE in bwrite() except if B_DELWRI is already set, + * so the below call doesn't set B_CACHE, but that gets real + * confusing. This is much easier. */ if ((bp->b_flags & (B_CACHE|B_DELWRI)) == B_DELWRI) { + bp->b_flags |= B_NOCACHE; VOP_BWRITE(bp->b_vp, bp); goto loop; } Index: nfs/nfs.h =================================================================== RCS file: /home/ncvs/src/sys/nfs/Attic/nfs.h,v retrieving revision 1.53.2.3 diff -u -r1.53.2.3 nfs.h --- nfs/nfs.h 2001/09/11 09:49:54 1.53.2.3 +++ nfs/nfs.h 2001/12/13 06:47:28 @@ -721,6 +721,8 @@ struct proc *procp, struct mbuf **mrq)); void nfsrv_rcv __P((struct socket *so, void *arg, int waitflag)); void nfsrv_slpderef __P((struct nfssvc_sock *slp)); +int nfs_meta_setsize __P((struct vnode *vp, struct ucred *cred, struct proc *p, u_quad_t nsize)); + #endif /* _KERNEL */ #endif Index: nfs/nfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/Attic/nfs_bio.c,v retrieving revision 1.83.2.1 diff -u -r1.83.2.1 nfs_bio.c --- nfs/nfs_bio.c 2001/11/18 07:10:59 1.83.2.1 +++ nfs/nfs_bio.c 2001/12/13 18:24:01 @@ -193,8 +193,14 @@ vm_page_set_validclean(m, 0, size - toff); /* handled by vm_fault now */ /* vm_page_zero_invalid(m, TRUE); */ + } else { + /* + * Read operation was short. If no error occured + * we may have hit a zero-fill section. We simply + * leave valid set to 0. + */ + ; } - if (i != ap->a_reqpage) { /* * Whether or not to leave the page activated is up in @@ -896,9 +902,7 @@ else bcount = np->n_size - (off_t)lbn * biosize; } - bp = nfs_getcacheblk(vp, lbn, bcount, p); - if (uio->uio_offset + n > np->n_size) { np->n_size = uio->uio_offset + n; np->n_flag |= NMODIFIED; @@ -1409,11 +1413,13 @@ io.iov_len = uiop->uio_resid = bp->b_bcount; io.iov_base = bp->b_data; uiop->uio_rw = UIO_READ; + switch (vp->v_type) { case VREG: uiop->uio_offset = ((off_t)bp->b_blkno) * DEV_BSIZE; nfsstats.read_bios++; error = nfs_readrpc(vp, uiop, cr); + if (!error) { if (uiop->uio_resid) { /* @@ -1425,7 +1431,7 @@ * writes, but that is not possible any longer. */ int nread = bp->b_bcount - uiop->uio_resid; - int left = bp->b_bcount - nread; + int left = uiop->uio_resid; if (left > 0) bzero((char *)bp->b_data + nread, left); @@ -1597,3 +1603,48 @@ biodone(bp); return (error); } + +/* + * Used to aid in handling ftruncate() operations on the NFS client side. + * Truncation creates a number of special problems for NFS. We have to + * throw away VM pages and buffer cache buffers that are beyond EOF, and + * we have to properly handle VM pages or (potentially dirty) buffers + * that straddle the truncation point. + */ + +int +nfs_meta_setsize(struct vnode *vp, struct ucred *cred, struct proc *p, u_quad_t nsize) +{ + struct nfsnode *np = VTONFS(vp); + u_quad_t tsize = np->n_size; + int biosize = vp->v_mount->mnt_stat.f_iosize; + int error = 0; + + np->n_size = nsize; + + if (np->n_size < tsize) { + struct buf *bp; + daddr_t lbn; + int bufsize; + + /* + * vtruncbuf() doesn't get the buffer overlapping the + * truncation point. We may have a B_DELWRI and/or B_CACHE + * buffer that now needs to be truncated. + */ + error = vtruncbuf(vp, cred, p, nsize, biosize); + lbn = nsize / biosize; + bufsize = nsize & (biosize - 1); + bp = nfs_getcacheblk(vp, lbn, bufsize, p); + if (bp->b_dirtyoff > bp->b_bcount) + bp->b_dirtyoff = bp->b_bcount; + if (bp->b_dirtyend > bp->b_bcount) + bp->b_dirtyend = bp->b_bcount; + bp->b_flags |= B_RELBUF; /* don't leave garbage around */ + brelse(bp); + } else { + vnode_pager_setsize(vp, nsize); + } + return(error); +} + Index: nfs/nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/Attic/nfs_vnops.c,v retrieving revision 1.150.2.4 diff -u -r1.150.2.4 nfs_vnops.c --- nfs/nfs_vnops.c 2001/08/05 00:23:58 1.150.2.4 +++ nfs/nfs_vnops.c 2001/12/13 06:46:32 @@ -710,7 +710,17 @@ */ if (vp->v_mount->mnt_flag & MNT_RDONLY) return (EROFS); - vnode_pager_setsize(vp, vap->va_size); + + /* + * We run vnode_pager_setsize() early (why?), + * we must set np->n_size now to avoid vinvalbuf + * V_SAVE races that might setsize a lower + * value. + */ + + error = nfs_meta_setsize(vp, ap->a_cred, + ap->a_p, vap->va_size); + if (np->n_flag & NMODIFIED) { if (vap->va_size == 0) error = nfs_vinvalbuf(vp, 0, @@ -719,12 +729,12 @@ error = nfs_vinvalbuf(vp, V_SAVE, ap->a_cred, ap->a_p, 1); if (error) { + np->n_size = tsize; vnode_pager_setsize(vp, np->n_size); return (error); } } - tsize = np->n_size; - np->n_size = np->n_vattr.va_size = vap->va_size; + np->n_vattr.va_size = vap->va_size; }; } else if ((vap->va_mtime.tv_sec != VNOVAL || vap->va_atime.tv_sec != VNOVAL) && (np->n_flag & NMODIFIED) && @@ -1119,10 +1129,12 @@ m_freem(mrep); tsiz -= retlen; if (v3) { - if (eof || retlen == 0) + if (eof || retlen == 0) { tsiz = 0; - } else if (retlen < len) + } + } else if (retlen < len) { tsiz = 0; + } } nfsmout: return (error); @@ -3397,3 +3409,4 @@ } return (VOCALL(fifo_vnodeop_p, VOFFSET(vop_close), ap)); } + Index: ufs/ffs/ffs_inode.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_inode.c,v retrieving revision 1.56.2.3 diff -u -r1.56.2.3 ffs_inode.c --- ufs/ffs/ffs_inode.c 2001/11/20 20:27:27 1.56.2.3 +++ ufs/ffs/ffs_inode.c 2001/12/12 23:43:36 @@ -244,6 +244,10 @@ if (error) { return (error); } + if (length > 0 && DOINGSOFTDEP(ovp)) { + if ((error = VOP_FSYNC(ovp, cred, MNT_WAIT, p)) != 0) + return (error); + } oip->i_size = length; size = blksize(fs, oip, lbn); if (ovp->v_type != VDIR) @@ -359,6 +363,10 @@ if (newspace == 0) panic("ffs_truncate: newspace"); if (oldspace - newspace > 0) { + /* + * XXX Softupdates, adjust queued directblock + * in place rather then the second FSYNC above? + */ /* * Block number of space to be free'd is * the old block # plus the number of frags Index: vm/vm_page.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_page.c,v retrieving revision 1.147.2.12 diff -u -r1.147.2.12 vm_page.c --- vm/vm_page.c 2001/11/03 19:59:28 1.147.2.12 +++ vm/vm_page.c 2001/12/13 10:42:52 @@ -1625,10 +1625,27 @@ * use this opportunity to clear the PG_NOSYNC flag. If a process * takes a write fault on a MAP_NOSYNC memory area the flag will * be set again. + * + * We set valid bits inclusive of any overlap, but we can only + * clear dirty bits for DEV_BSIZE chunks that are fully within + * the range. */ pagebits = vm_page_bits(base, size); m->valid |= pagebits; +#if 1 + if ((base & (DEV_BSIZE - 1)) || (size & (DEV_BSIZE - 1))) { + int adj; + + adj = DEV_BSIZE - (base & (DEV_BSIZE - 1)); + base += adj; + if (size < adj) + size = 0; + else + size = (size - adj) & ~(DEV_BSIZE - 1); + pagebits = vm_page_bits(base, size); + } +#endif m->dirty &= ~pagebits; if (base == 0 && size == PAGE_SIZE) { pmap_clear_modify(m); Index: vm/vnode_pager.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vnode_pager.c,v retrieving revision 1.116.2.5 diff -u -r1.116.2.5 vnode_pager.c --- vm/vnode_pager.c 2001/11/09 03:21:22 1.116.2.5 +++ vm/vnode_pager.c 2001/12/13 10:39:21 @@ -290,14 +290,18 @@ } /* * this gets rid of garbage at the end of a page that is now - * only partially backed by the vnode... + * only partially backed by the vnode. + * + * XXX for some reason (I don't know yet), if we take a + * completely invalid page and mark it partially valid + * it can screw up NFS reads, so we don't allow the case. */ if (nsize & PAGE_MASK) { vm_offset_t kva; vm_page_t m; m = vm_page_lookup(object, OFF_TO_IDX(nsize)); - if (m) { + if (m && m->valid) { int base = (int)nsize & PAGE_MASK; int size = PAGE_SIZE - base; @@ -310,6 +314,20 @@ vm_pager_unmap_page(kva); /* + * XXX work around SMP data integrity race + * by unmapping the page from user processes. + * The garbage we just cleared may be mapped + * to a user process running on another cpu + * and this code is not running through normal + * I/O channels which handle SMP issues for + * us, so unmap page to synchronize all cpus. + * + * XXX should vm_pager_unmap_page() have + * dealt with this? + */ + vm_page_protect(m, VM_PROT_NONE); + + /* * Clear out partial-page dirty bits. This * has the side effect of setting the valid * bits, but that is ok. There are a bunch @@ -317,6 +335,10 @@ * m->dirty == VM_PAGE_BITS_ALL. The file EOF * case is one of them. If the page is still * partially dirty, make it fully dirty. + * + * note that we do not clear out the valid + * bits. This would prevent bogus_page + * replacement from working properly. */ vm_page_set_validclean(m, base, size); if (m->dirty != 0) @@ -960,6 +982,9 @@ * may not properly clear the dirty bits for the entire page (which * could be VM_PAGE_BITS_ALL due to the page having been mmap()d). * With the page locked we are free to fix-up the dirty bits here. + * + * We do not under any circumstances truncate the valid bits, as + * this will screw up bogus page replacement. */ if (maxsize + poffset > object->un_pager.vnp.vnp_size) { if (object->un_pager.vnp.vnp_size > poffset) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 10:45: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 65AE637B416 for ; Thu, 13 Dec 2001 10:45:01 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 0B3D881E0E; Thu, 13 Dec 2001 12:45:01 -0600 (CST) Date: Thu, 13 Dec 2001 12:45:01 -0600 From: Alfred Perlstein To: void Cc: hackers@freebsd.org Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step Message-ID: <20011213124500.F79896@elvis.mu.org> References: <200112121623.fBCGNuY52543@winston.freebsd.org> <20011213165833.A23824@parhelion.firedrake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011213165833.A23824@parhelion.firedrake.org>; from float@firedrake.org on Thu, Dec 13, 2001 at 04:58:33PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * void [011213 11:00] wrote: > Has anyone brought this code to the attention of the NetBSD people? > I imagine that they would be interested. If not, I will forward it > along myself, as soon as I determine the appropriate list. (List > recommendations from the dual citizens here are welcome.) tech-kern might be appropriate. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 10:48:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0CA8437B41A for ; Thu, 13 Dec 2001 10:48:31 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBDImUZ70224; Thu, 13 Dec 2001 10:48:30 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Dec 2001 10:48:30 -0800 (PST) From: Matthew Dillon Message-Id: <200112131848.fBDImUZ70224@apollo.backplane.com> To: Dan Nelson Cc: Mike Silbersack , Geoff Mohler , hackers@FreeBSD.ORG Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step References: <200112130659.fBD6xZt55360@apollo.backplane.com> <20011213153035.GB56448@dan.emsphone.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> And if you hadn't heard, Matt just fixed a couple of bugs in the tcp :> stack which improves NFS greatly. It sounds like after this round of :> NFS fixes, the first answer to NFS questions should be: Upgrade to :> 4.5! : :I don't even bother with TCP mounts; my default amd rule says :proto=udp. Is there any reason to add the overhead of the TCP stack if :you're not leaving your own ethernet? : :You should be able to easily saturate a 100mbit link with FreeBSD 4.* :machines, and I can do 15-20MB/sec with Netgear GA620 gigabit nics (SMP :2 x pIII/600). : :-- : Dan Nelson : dnelson@allantgroup.com I think there's a trade-off. TCP mounts deal with heavy parallel client loads better then UDP because they do real congestion and streaming control whereas NFS's UDP implementation fakes it. A UDP mount will work better for a large parallel load from a single client. I tend to use both types of mounts but I personally prefer TCP mounts over UDP because they are more secure and easier to get through a firewall. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 10:48:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id C233A37B419; Thu, 13 Dec 2001 10:48:48 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fBDImZi69992; Thu, 13 Dec 2001 13:48:35 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Thu, 13 Dec 2001 13:48:35 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Matthew Dillon Cc: David Greenman , Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS Patch #4 -- survived overnight test. (was Re: Found NFS data corruption bug... (was Re:...)) In-Reply-To: <200112131835.fBDIZuL70031@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 13 Dec 2001, Matthew Dillon wrote: > Ok, here is the latest patch set. This patch set survived an > overnight run of the nfs torture test that Jordan posted... it > got through 597,000 test calls over NFSv3, 367,000 over NFSv2, and > 1.35 million on a local filesystem. Great! > I am going to forward port and test this stuff on -current today and > probably commit it to -current tonight, with a 3-day turn to -stable. Hmm. I'm OK with a commit to -CURRENT, but would really appreciate it if you made it a week before MFC to -STABLE. Given your statement just a few lines earlier about needing more review from VM types, that would allow a bit more time for necessary review. I agree, given the impending 4.5 release, we should MFC it as far before release as possible, but three days is a little below my threshold for sensitive NFS/file system changes :-). Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 11: 0:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 4B16537B425; Thu, 13 Dec 2001 11:00:33 -0800 (PST) Received: from pool0215.cvx22-bradley.dialup.earthlink.net ([209.179.198.215] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Eb5g-0005u5-00; Thu, 13 Dec 2001 11:00:20 -0800 Message-ID: <3C18FAC9.E743DAA5@mindspring.com> Date: Thu, 13 Dec 2001 11:00:25 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: David Greenman , Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS Patch #4 -- survived overnight test. (was Re: Found NFS data corruption bug... (was Re:...)) References: <58885.1008217148@winston.freebsd.org> <200112130608.fBD689K49906@apollo.backplane.com> <20011212224927.A73226@nexus.root.com> <200112131835.fBDIZuL70031@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: [ ... ] > I would appreciate other VM gurus taking a look at the > vm_page_set_validclean() changes. [ ... ] Not to appoint myself a guru or anything... > +#if 1 > + if ((base & (DEV_BSIZE - 1)) || (size & (DEV_BSIZE - 1))) { > + int adj; > + > + adj = DEV_BSIZE - (base & (DEV_BSIZE - 1)); > + base += adj; > + if (size < adj) > + size = 0; > + else > + size = (size - adj) & ~(DEV_BSIZE - 1); > + pagebits = vm_page_bits(base, size); > + } > +#endif This seems wrong. Specifically, it seems to only get the first block, in the case that (integer math: / is "div"): ((size - adj)/DEV_BSIZE) > 1 How about: else { /* * Drop partial trailing blocks from the size * calculation to maintain correct dirty bits; * note that 'size' might still span more than * one block, though. */ int n_size; /* probably not int? */ n_size = (size - adj) / DEV_BSIZE; size = (size - adj) & ~(DEV_BSIZE - 1); size += n_size * DEV_BSIZE; } -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 11: 3:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 51A0F37B429; Thu, 13 Dec 2001 11:03:02 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fBDJ31i70315; Thu, 13 Dec 2001 14:03:01 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Thu, 13 Dec 2001 14:03:01 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: developers@FreeBSD.org, hackers@FreeBSD.org Subject: REMINDER: Request for submissions: FreeBSD Monthly Development Status Report Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Reminder: the deadline is tomorrow. I've received only about 8 reports so far, and would appreciate receiving more :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services ---------- Forwarded message ---------- Date: Sun, 9 Dec 2001 22:07:26 -0500 (EST) From: Robert Watson To: developers@FreeBSD.org, hackers@FreeBSD.org Subject: Request for submissions: FreeBSD Monthly Development Status Report Well, it's been a bit, but here it is again. This is a request for submissions for the November, 2001 FreeBSD Monthly Development Status Report. All submissions are due by Friday, December 14, 2001. Submissions should made by filling out the following template: http://www.FreeBSD.org/news/status/report-sample.xml Which will allow reports to be automatically processed, reducing the lag involved in generating the overall report :-). A reasonable attempt should be made to prevent duplicate submissions for the same project; however, if it's a large project, seperate submissions may be made for components, as well as a submission sumarizing overall progress on the project. Developers working on multiple projects should feel free to submit entries for each project individually. Submissions are welcome on a variety of topics relating to FreeBSD -- not least, development, but also documentation, advocacy, and processes relating to the development process, such as release engineering, QA, and security updates. All submissions *MUST* be e-mailed to the following address: robert+freebsd.monthly@cyrus.watson.org Submissions made to other e-mail addresses will not be included in the report. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 11: 4:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2B52437B435; Thu, 13 Dec 2001 11:03:54 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBDJ3sq70413; Thu, 13 Dec 2001 11:03:54 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Dec 2001 11:03:54 -0800 (PST) From: Matthew Dillon Message-Id: <200112131903.fBDJ3sq70413@apollo.backplane.com> To: Robert Watson Cc: David Greenman , Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS Patch #4 -- survived overnight test. (was Re: Found NFS data corruption bug... (was Re:...)) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Hmm. I'm OK with a commit to -CURRENT, but would really appreciate it if :you made it a week before MFC to -STABLE. Given your statement just a few :lines earlier about needing more review from VM types, that would allow a :bit more time for necessary review. I agree, given the impending 4.5 :release, we should MFC it as far before release as possible, but three :days is a little below my threshold for sensitive NFS/file system changes ::-). : :Thanks, : :Robert N M Watson FreeBSD Core Team, TrustedBSD Project I can hold-off the vm_page_set_validclean() patch for a week but there is no reason not to 3-day MFC the rest of the bug fixes. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 11:37: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.chem.msu.ru (mail.chem.msu.ru [195.208.208.19]) by hub.freebsd.org (Postfix) with ESMTP id 97F0337B405; Thu, 13 Dec 2001 11:36:56 -0800 (PST) Received: from comp.chem.msu.su ([158.250.32.97]) by mail.chem.msu.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id YH35GH9N; Thu, 13 Dec 2001 22:36:33 +0300 Received: (from yar@localhost) by comp.chem.msu.su (8.11.1/8.11.1) id fBDJapJ07366; Thu, 13 Dec 2001 22:36:51 +0300 (MSK) (envelope-from yar) Date: Thu, 13 Dec 2001 22:36:51 +0300 From: Yar Tikhiy To: hackers@freebsd.org, net@freebsd.org Subject: Solution for an IPFIREWALL_FORWARD panic? Message-ID: <20011213223651.A2089@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello everybody, A kernel panic has been observed in both branches under the following conditions: o ipfw is configured with a "fwd" rule for outgoing packets that will match some RIP datagrams o GateD is started with RIP enabled and consequently sends a broadcast UDP datagram that matches the "fwd" rule The panic happens there (the source file is sys/netinet/ip_output.c; quoted as to rev. 1.99.2.21): 740 if (ro_fwd->ro_rt->rt_flags & RTF_HOST) 741 isbroadcast = 742 (ro_fwd->ro_rt->rt_flags & RTF_BROADCAST); 743 else 744 isbroadcast = in_broadcast(dst->sin_addr, ifp); 745 RTFREE(ro->ro_rt); ^^^^^^^^^^^^^^^^^^^^^^^ 746 ro->ro_rt = ro_fwd->ro_rt; 747 dst = (struct sockaddr_in *)&ro_fwd->ro_dst; ro->ro_rt is NULL, which causes the panic. As far as I understand the ip_output() code, ro->ro_rt being NULL at that point is actually all right, so to solve the problem, the code just must be changed as follows: < RTFREE(ro->ro_rt); -- > if (ro->ro_rt) > RTFREE(ro->ro_rt); Am I right? Or ro->ro_rt should not be NULL there at all and the actual bug hides somewhere else? -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 12: 3:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id E555937B41B for ; Thu, 13 Dec 2001 12:03:33 -0800 (PST) Received: from [192.168.1.129] (212.129.45.146) by mail.libertysurf.net (5.1.053) id 3C1532CE000BD55E; Thu, 13 Dec 2001 21:03:30 +0100 Date: Thu, 13 Dec 2001 18:09:54 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: To: Greg Johnson Cc: Subject: Re: Bus master DMA problems In-Reply-To: <20011213041426.77707B7331@brixi.research.canon.com.au> Message-ID: <20011213175415.R1979-100000@gerard> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG There are a couple of rules in PCI you must have in mind when synchronization between PCI devices is needed. 1) Interrupts are not synchronization events. They just send attention to the device driver (acts as SIGIO, for example). Some bridge may flush posted buffers on interrupt, but since interrupt can be shared, you must not rely on such mechanism. 2) After a write transaction has completed to some target, you must read some data from this target if you want posted buffers to be flushed. (perform a dummy read to some IO register if needed). 3) Prior to looking at data that just have been DMAed, perform a read barrier in order to flush any data prefetched by the CPU. Otherwise you may see stale data. 4) Write barriers must be used to enforce ordering of writes when the system may reorder them. But this does not apply to IA32 architecture that guarantees ordering of write as seen from other agents. The dmamap_* are intended to deal with systems specific issues, system bridges, CPU, etc.... They are not enough to ensure synchronisation will be what your software expects. Even in the hypothesis of them being enough for a given system, a PCI board that incorporates a PCI bridge will require at least rule #2 not to be missed. G=E9rard. On Thu, 13 Dec 2001, Greg Johnson wrote: > Hello, > > I am working on a FreeBSD device driver for a custom > PCI bus device developed by my company. The PCI card > has large amounts on memory on it and we are using > bus master DMA to get data in and out of memory. > > The proceedure that I am using is as follows: > > A.1. The DMA controller on our device is set up > for the DMA transfer of memory. > > A.2. asleep() is called to let the OS know that we > are about to wait on an event. > > A.3. An enable bit is set on the device to start the > transfer. > > A.4. await() is called to get the current process to > sleep and wait for the event. > > A.5. The ISR, upon recipt of an interrupt that indicates > that the DMA transfer is complete, calls wakeup() > on the ident for the process sleeping, waiting for the > DMA transfer. > > A.6. await() returns. > > In addition, the memory buffers on the PC host side are > initially allocated by a user process, and locked down > (wired) buy the device driver so that they a present > in physical memory. > > A bus DMA Tag is created once on driver load that > describes the DMA transfers. > > On a call to read or write: > > B.1. Memory is locked. > > B.2. bus_dmamap_sync() is called (PRE*) > > B.3. bus_dmamap_load() is called > > B.4. bus_dmamap sync() is called (POST*) > > B.5. Memory is unlocked. > > Now, the problem I am experiencing is that memory does not > appear to be DMAed correctly. When using the interrupt driver > method above, sometimes there are errors in the data written > to the device, and sometimes in the data read back from the > device. > > When using a polling approach and dissabling the DMA interrupts, > starting the transfer and polling for when the transfer is complete, > the system works correctly. > > Also, when using the interrupt approach described, if I insert a > large delay of about 100us (50us does not work) in the ISR at the > point when the ISR confirms that the interrupt is the DMA done > interrupt, then everything works correctly. > > The problem sounds a lot like out PCI device is not completing > the DMA transfer when the interrupt is raised, but with the polling > process, it only seems to take a few (2-8)us before the DMA done > interrupt is asserted and the call returns, and in this case > everything works. > > So if anyong out there in FreeBSD guru land has any ideas as > to what might be wrong, or things I might of missed in seeting > up stuff, I would really appreciate their input. > > Our systems are x86 (PIIIs and P4s) running FreeBSD 4.4-stable. > > Thanks. > > Greg. > > -- > +------------------------------------------------------+ > | Do you want to know more? www.geocities.com/worfsom/ | > | ..ooOO Greg Johnson OOoo.. | > | HW/SW Engineer gjohnson@research.canon.COM.Au | > | Canon Information Systems Research Australia (CISRA) | > | 1 Thomas Holt Dr., North Ryde, NSW, 2113, Australia | > | "I FLEXed my BISON and it went YACC!" - me. | > +------------------------------------------------------+ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 12:12:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id D0CD837B41B for ; Thu, 13 Dec 2001 12:12:36 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.5/8.11.5) with ESMTP id fBDKCSg09049; Thu, 13 Dec 2001 13:12:28 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200112132012.fBDKCSg09049@aslan.scsiguy.com> To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: Greg Johnson , freebsd-hackers@FreeBSD.ORG Subject: Re: Bus master DMA problems In-Reply-To: Your message of "Thu, 13 Dec 2001 18:09:54 +0100." <20011213175415.R1979-100000@gerard> Date: Thu, 13 Dec 2001 13:12:28 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > >There are a couple of rules in PCI you must have in mind when >synchronization between PCI devices is needed. > >1) Interrupts are not synchronization events. They just send attention to > the device driver (acts as SIGIO, for example). Some bridge may flush > posted buffers on interrupt, but since interrupt can be shared, you > must not rely on such mechanism. The exception to this rule are Message Signaled Interrupts. The interrupt is asserted by DMAing a token into a mailbox in the chipset. Since posted writes must complete in order, this mechanism guarantees that the interrupt is only asserted once any previous writes have completed. MSI is part of the PCI 2.2 spec, but may only start to be supported in upcoming PCI-X chipsets. I don't know when FreeBSD will gain support for MSI. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 13: 4:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mao.stokely.org (mao.stokely.org [65.84.64.228]) by hub.freebsd.org (Postfix) with ESMTP id 2A2E637B405; Thu, 13 Dec 2001 13:04:32 -0800 (PST) Received: by mao.stokely.org (Postfix, from userid 2074) id 58D754B65D; Thu, 13 Dec 2001 13:04:31 -0800 (PST) Date: Thu, 13 Dec 2001 13:04:31 -0800 From: Murray Stokely To: Matthew Dillon Cc: Robert Watson , David Greenman , Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS Patch #4 -- survived overnight test. (was Re: Found NFS data corruption bug... (was Re:...)) Message-ID: <20011213130431.C8525@windriver.com> References: <200112131903.fBDJ3sq70413@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112131903.fBDJ3sq70413@apollo.backplane.com>; from dillon@apollo.backplane.com on Thu, Dec 13, 2001 at 11:03:54AM -0800 X-GPG-Key-ID: 1024D/0E451F7D X-GPG-Key-Fingerprint: E2CA 411D DD44 53FD BB4B 3CB5 B4D7 10A2 0E45 1F7D Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 13, 2001 at 11:03:54AM -0800, Matthew Dillon wrote: > I can hold-off the vm_page_set_validclean() patch for a week but there > is no reason not to 3-day MFC the rest of the bug fixes. I would also be more comfortable if we gave this change a week in -CURRENT. This is great work, and we'll approve it for MFC in the code freeze. I don't think that 4 extra days is too much to ask for a filesystem related change like this. - Murray To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 13:10:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 1D80837B41B; Thu, 13 Dec 2001 13:10:50 -0800 (PST) Received: from winston.freebsd.org (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id fBDLAKq62011; Thu, 13 Dec 2001 13:10:20 -0800 (PST) (envelope-from jkh@winston.freebsd.org) To: Matthew Dillon Cc: Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: Message from Matthew Dillon of "Wed, 12 Dec 2001 16:24:32 PST." <200112130024.fBD0OWV23402@apollo.backplane.com> Date: Thu, 13 Dec 2001 13:10:20 -0800 Message-ID: <62007.1008277820@winston.freebsd.org> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I can't seem to get a crash dump out of it, but the panic I'm seeing is: panic: allocdirect_check: old 30246736 ! = new 30246736 || ibn 4 >= 12 For some reason the dump also dies, resettting the ata0 bus over and over but not writing out to swap. - Jordan > : > :> I should point out that FSX can be used against any filesystem, and > :> that there are reports locally (at Apple) that it's great for killing > :> FreeBSD machines. I wasn't able to reproduce this when I tried, but I > :> may not have let it run long enough. > : > :Oh, it blows freebsd.apple.com right out of the water with a kernel > :panic after running for just 3 seconds from an OS X box on the same > :LAN segment. :) > : > :- Jordan > > What panic are you getting? > > -Matt > Matthew Dillon > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 13:22: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from iscserv7.nepustil.net (NS.Nepustil.NET [193.96.243.22]) by hub.freebsd.org (Postfix) with ESMTP id F33C537B419 for ; Thu, 13 Dec 2001 13:21:50 -0800 (PST) Received: from peotl.homeip.net (tuebpool-130.pm3.nepustil.net [212.71.200.130]) by iscserv7.nepustil.net (Sendmail) with ESMTP id F37AC79E18; Thu, 13 Dec 2001 22:21:38 +0100 (CET) Received: (from thz@localhost) by peotl.homeip.net (8.11.6/8.11.6) id fBDLIZQ03870; Thu, 13 Dec 2001 22:18:35 +0100 (MET) (envelope-from thz) Date: Thu, 13 Dec 2001 22:12:05 +0100 From: Thomas Zenker To: Matthew Dillon Cc: hackers@freebsd.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) Message-ID: <20011213221204.A2994@peotl.homeip.net> References: <59687.1008231593@winston.freebsd.org> <200112131058.fBDAwSR66790@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Mailer: Mutt 1.0.1i In-Reply-To: <200112131058.fBDAwSR66790@apollo.backplane.com>; from dillon@apollo.backplane.com on Thu, Dec 13, 2001 at 02:58:28AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 13, 2001 at 02:58:28AM -0800, Matthew Dillon wrote: > > @#$@#$ crap. I think I found a dirty-mmap edge case with truncation. > It requires a change to vm_page_set_validclean(), which of course is > one of the core routines in the VM system. > > Basically what happens is that ftruncate() calls vnode_pager_setsize() > which eventually calls vm_page_set_validclean(). > > If you happened to mmap() the truncation point shared R+W and > dirty it, then truncate to something that isn't a multiple DEV_BSIZE.. > for example, if you were to truncate to an offset of '10', and a buffer Matt, what the hell, this seems to very near by a problem I wanted to report since a week: in a data acquisition I have a write process writing to a file backed shared mmapped ringbuffer. There can be several reader processes on this this ringbuffer. Now once i killed the writer for resizing of the ringbuffer and forgot about the readers. The writer truncated the database without unlinking it before. This lead the readers to be running for ever, it seemed so at least. After attaching with gdb I saw, that they were only page faulting nothing more, for ever.... Something similar I saw with netscape going mad. cheers, Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 13:28:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from niwun.pair.com (niwun.pair.com [209.68.2.70]) by hub.freebsd.org (Postfix) with SMTP id 6BAB137B416 for ; Thu, 13 Dec 2001 13:28:44 -0800 (PST) Received: (qmail 84028 invoked by uid 3193); 13 Dec 2001 21:28:43 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 13 Dec 2001 21:28:43 -0000 Date: Thu, 13 Dec 2001 16:28:43 -0500 (EST) From: Mike Silbersack X-Sender: To: Jordan Hubbard Cc: Matthew Dillon , Mike Smith , , Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step In-Reply-To: <62007.1008277820@winston.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 13 Dec 2001, Jordan Hubbard wrote: > I can't seem to get a crash dump out of it, but the panic I'm seeing is: > > panic: allocdirect_check: old 30246736 ! = new 30246736 || ibn 4 >= 12 > > For some reason the dump also dies, resettting the ata0 bus over and over > but not writing out to swap. > > - Jordan Was it allocdirect_merge perhaps? It looks like the debugging info it gives there is incomplete, three things can actually cause the panic to trigger. This panic is in the soft updates code; have you tried running the test with the soft updates patch applied? Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 13:34: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id 9523D37B405 for ; Thu, 13 Dec 2001 13:34:00 -0800 (PST) Received: from [192.168.1.129] (212.129.45.146) by mail.libertysurf.net (5.1.053) id 3C1031E400178ACD; Thu, 13 Dec 2001 22:33:49 +0100 Date: Thu, 13 Dec 2001 19:40:20 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: To: "Justin T. Gibbs" Cc: Greg Johnson , Subject: Re: Bus master DMA problems In-Reply-To: <200112132012.fBDKCSg09049@aslan.scsiguy.com> Message-ID: <20011213193136.P2307-100000@gerard> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 13 Dec 2001, Justin T. Gibbs wrote: > > > >There are a couple of rules in PCI you must have in mind when > >synchronization between PCI devices is needed. > > > >1) Interrupts are not synchronization events. They just send attention t= o > > the device driver (acts as SIGIO, for example). Some bridge may flush > > posted buffers on interrupt, but since interrupt can be shared, you > > must not rely on such mechanism. > > The exception to this rule are Message Signaled Interrupts. The interrup= t > is asserted by DMAing a token into a mailbox in the chipset. Since poste= d > writes must complete in order, this mechanism guarantees that the interru= pt > is only asserted once any previous writes have completed. MSI is part > of the PCI 2.2 spec, but may only start to be supported in upcoming PCI-X > chipsets. I don't know when FreeBSD will gain support for MSI. I didn't hear about this being actually implemented. Anyway, in the situation of the PCI device not stopping operations after signaling interrupts (as, for example, in sym that has hardware phase mismatch really supported for years or ahc), the flushing does not look this useful. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 13:36:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id EAA7337B405; Thu, 13 Dec 2001 13:36:23 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBDLZ7r75297; Thu, 13 Dec 2001 13:35:07 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Dec 2001 13:35:07 -0800 (PST) From: Matthew Dillon Message-Id: <200112132135.fBDLZ7r75297@apollo.backplane.com> To: Jordan Hubbard Cc: Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step References: <62007.1008277820@winston.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :I can't seem to get a crash dump out of it, but the panic I'm seeing is: : :panic: allocdirect_check: old 30246736 ! = new 30246736 || ibn 4 >= 12 : :For some reason the dump also dies, resettting the ata0 bus over and over :but not writing out to swap. : :- Jordan That's the softupdates panic I fixed in the patch set. There are actually three conditions to the panic and the one that isn't being listed is the one that is causing the panic. Weird that you couldn't dump, but don't worry about it, it's been dealt with. -Matt Matthew Dillon :> :> What panic are you getting? :> :> -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 13:43:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from noos.fr (r178m112.cybercable.tm.fr [195.132.178.112]) by hub.freebsd.org (Postfix) with ESMTP id 317E537B416 for ; Thu, 13 Dec 2001 13:43:33 -0800 (PST) Received: (from mux@localhost) by noos.fr (8.11.6/8.11.4) id fBDLhVu25916 for freebsd-hackers@FreeBSD.org; Thu, 13 Dec 2001 22:43:31 +0100 (CET) (envelope-from mux) Date: Thu, 13 Dec 2001 22:43:31 +0100 From: Maxime Henrion To: freebsd-hackers@FreeBSD.org Subject: New vhost bugs.FreeBSD.org Message-ID: <20011213224331.B298@nebula.noos.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello all, The recently added cvsweb.FreeBSD.org vhost makes me think we could also have one pointing to the PR database (/cgi/query-pr-summary.cgi), for example, bugs.FreeBSD.org as the subject of this mail suggests. It would be very useful, IMO, to have a simple URL like this to access the PR database. Opinions ? Maxime Henrion -- Don't be fooled by cheap finnish imitations ; BSD is the One True Code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 13:44: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0447137B405 for ; Thu, 13 Dec 2001 13:44:00 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBDLek699925; Thu, 13 Dec 2001 13:40:46 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Dec 2001 13:40:46 -0800 (PST) From: Matthew Dillon Message-Id: <200112132140.fBDLek699925@apollo.backplane.com> To: Thomas Zenker Cc: hackers@freebsd.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) References: <59687.1008231593@winston.freebsd.org> <200112131058.fBDAwSR66790@apollo.backplane.com> <20011213221204.A2994@peotl.homeip.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Matt, : :what the hell, this seems to very near by a problem I wanted to :report since a week: : :in a data acquisition I have a write process writing to a file :backed shared mmapped ringbuffer. There can be several reader :processes on this this ringbuffer. Now once i killed the writer for :resizing of the ringbuffer and forgot about the readers. The writer :truncated the database without unlinking it before. This lead the :readers to be running for ever, it seemed so at least. After :attaching with gdb I saw, that they were only page faulting nothing :more, for ever.... : :Something similar I saw with netscape going mad. : :cheers, Thomas That's something else. There's no OS bug there. When you mmap() a file only those pages that are within the file's boundries are valid. So if you ftruncate() the file then all the pages occuring after the (new) file EOF will become invalid and BUSfault if the process touches them. You touched upon the correct solution... remove() the file instead of ftruncate()ing it. The file's data then remains intact for the processes still referencing it. The readers must be catching SIGBUS and retrying (not exiting), causing them to run in a signal loop forever. This is a case of bad programming. I've seen it before... there was a popular IRC bot back in my BEST days which constantly got itself into infinite loops because the guy who wrote it installed a signal handler for SIGBUS. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 13:45:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id A597037B419 for ; Thu, 13 Dec 2001 13:45:29 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id fBDLhhu02193; Thu, 13 Dec 2001 22:43:44 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Maxime Henrion Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: New vhost bugs.FreeBSD.org In-Reply-To: Your message of "Thu, 13 Dec 2001 22:43:31 +0100." <20011213224331.B298@nebula.noos.fr> Date: Thu, 13 Dec 2001 22:43:43 +0100 Message-ID: <2191.1008279823@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011213224331.B298@nebula.noos.fr>, Maxime Henrion writes: > Hello all, > >The recently added cvsweb.FreeBSD.org vhost makes me think we could also >have one pointing to the PR database (/cgi/query-pr-summary.cgi), for >example, bugs.FreeBSD.org as the subject of this mail suggests. > >It would be very useful, IMO, to have a simple URL like this to access the >PR database. > >Opinions ? Great idea... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 14: 7:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from iscserv7.nepustil.net (NS.Nepustil.NET [193.96.243.22]) by hub.freebsd.org (Postfix) with ESMTP id D23E437B41C for ; Thu, 13 Dec 2001 14:07:15 -0800 (PST) Received: from peotl.homeip.net (tuebpool-130.pm3.nepustil.net [212.71.200.130]) by iscserv7.nepustil.net (Sendmail) with ESMTP id EA58A79E59; Thu, 13 Dec 2001 23:07:03 +0100 (CET) Received: (from thz@localhost) by peotl.homeip.net (8.11.6/8.11.6) id fBDLxvl05437; Thu, 13 Dec 2001 22:59:57 +0100 (MET) (envelope-from thz) Date: Thu, 13 Dec 2001 22:58:10 +0100 From: Thomas Zenker To: Matthew Dillon Cc: hackers@freebsd.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) Message-ID: <20011213225810.A5144@peotl.homeip.net> References: <59687.1008231593@winston.freebsd.org> <200112131058.fBDAwSR66790@apollo.backplane.com> <20011213221204.A2994@peotl.homeip.net> <200112132140.fBDLek699925@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Mailer: Mutt 1.0.1i In-Reply-To: <200112132140.fBDLek699925@apollo.backplane.com>; from dillon@apollo.backplane.com on Thu, Dec 13, 2001 at 01:40:46PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 13, 2001 at 01:40:46PM -0800, Matthew Dillon wrote: > > :Matt, > : > :what the hell, this seems to very near by a problem I wanted to > :report since a week: > : > :in a data acquisition I have a write process writing to a file > :backed shared mmapped ringbuffer. There can be several reader > :processes on this this ringbuffer. Now once i killed the writer for > :resizing of the ringbuffer and forgot about the readers. The writer > :truncated the database without unlinking it before. This lead the > :readers to be running for ever, it seemed so at least. After > :attaching with gdb I saw, that they were only page faulting nothing > :more, for ever.... > : > :Something similar I saw with netscape going mad. > : > :cheers, Thomas > > That's something else. There's no OS bug there. When you mmap() > a file only those pages that are within the file's boundries are > valid. So if you ftruncate() the file then all the pages occuring > after the (new) file EOF will become invalid and BUSfault if the > process touches them. > > You touched upon the correct solution... remove() the file instead > of ftruncate()ing it. The file's data then remains intact for the > processes still referencing it. > > The readers must be catching SIGBUS and retrying (not exiting), > causing them to run in a signal loop forever. This is a case of > bad programming. I've seen it before... there was a popular IRC > bot back in my BEST days which constantly got itself into infinite > loops because the guy who wrote it installed a signal handler for > SIGBUS. > > -Matt > Matthew Dillon > well, I know, that this was a bug in my software, not to unlink the file first and then truncating :-). But SIGBUS was not catched in the readers. Will try to reproduce it. Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 14:20:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 6DE7737B419 for ; Thu, 13 Dec 2001 14:20:25 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 6C77614C56; Thu, 13 Dec 2001 23:20:23 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Maxime Henrion Cc: freebsd-hackers@FreeBSD.org Subject: Re: New vhost bugs.FreeBSD.org References: <20011213224331.B298@nebula.noos.fr> From: Dag-Erling Smorgrav Date: 13 Dec 2001 23:20:22 +0100 In-Reply-To: <20011213224331.B298@nebula.noos.fr> Message-ID: Lines: 10 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxime Henrion writes: > The recently added cvsweb.FreeBSD.org vhost makes me think we could also > have one pointing to the PR database (/cgi/query-pr-summary.cgi), for > example, bugs.FreeBSD.org as the subject of this mail suggests. Yes, please. DES (Bugmeister) -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 14:24:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 5CCFD37B405; Thu, 13 Dec 2001 14:24:09 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 278BD14C53; Thu, 13 Dec 2001 23:24:08 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Poul-Henning Kamp Cc: hackers@freebsd.org Subject: Re: Junior Kernel hacker task: Floppy driver mode handling. References: <31764.1008089464@critter.freebsd.dk> From: Dag-Erling Smorgrav Date: 13 Dec 2001 23:24:07 +0100 In-Reply-To: <31764.1008089464@critter.freebsd.dk> Message-ID: Lines: 9 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > There exists a patch for adding a mode to our floppy driver to > add DEC RX50 media handling. Clearly a job for Jessem, don't you think? :) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 14:51:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 7AF5337B417 for ; Thu, 13 Dec 2001 14:51:25 -0800 (PST) Received: (qmail 27991 invoked from network); 13 Dec 2001 22:51:24 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 13 Dec 2001 22:51:24 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <2191.1008279823@critter.freebsd.dk> Date: Thu, 13 Dec 2001 14:51:19 -0800 (PST) From: John Baldwin To: Poul-Henning Kamp Subject: Re: New vhost bugs.FreeBSD.org Cc: freebsd-hackers@FreeBSD.ORG, Maxime Henrion Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 13-Dec-01 Poul-Henning Kamp wrote: > In message <20011213224331.B298@nebula.noos.fr>, Maxime Henrion writes: >> Hello all, >> >>The recently added cvsweb.FreeBSD.org vhost makes me think we could also >>have one pointing to the PR database (/cgi/query-pr-summary.cgi), for >>example, bugs.FreeBSD.org as the subject of this mail suggests. >> >>It would be very useful, IMO, to have a simple URL like this to access the >>PR database. >> >>Opinions ? > > Great idea... Yep, I would like it. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 14:56:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21106.mail.yahoo.com (web21106.mail.yahoo.com [216.136.227.108]) by hub.freebsd.org (Postfix) with SMTP id 8738037B419 for ; Thu, 13 Dec 2001 14:56:51 -0800 (PST) Message-ID: <20011213225651.85727.qmail@web21106.mail.yahoo.com> Received: from [80.4.34.175] by web21106.mail.yahoo.com via HTTP; Thu, 13 Dec 2001 14:56:51 PST Date: Thu, 13 Dec 2001 14:56:51 -0800 (PST) From: Hiten Pandya Subject: Re: New vhost bugs.FreeBSD.org To: hackers@FreeBSD.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, i would like it to... it would save an effort for us, and people from typing lond URLs. Cool Idea! =Hiten = ===== -Hiten, Thank You, Yours Sincerely, Hiten Pandya, __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 15: 4:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from oxmail.ox.ac.uk (oxmail2.ox.ac.uk [163.1.2.1]) by hub.freebsd.org (Postfix) with ESMTP id 058D437B405 for ; Thu, 13 Dec 2001 15:04:38 -0800 (PST) Received: from dhcp-2.oriel.ox.ac.uk ([163.1.146.2] helo=sobek.lan) by oxmail.ox.ac.uk with esmtp (Exim 3.12 #1) id 16Eeu4-0004lX-02; Thu, 13 Dec 2001 23:04:36 +0000 Received: (from greid@localhost) by sobek.lan (8.11.5/8.11.5) id fBDN5a235867; Thu, 13 Dec 2001 23:05:36 GMT (envelope-from greid@FreeBSD.org) X-Authentication-Warning: sobek.lan: greid set sender to greid@FreeBSD.org using -f Date: Thu, 13 Dec 2001 23:05:36 +0000 From: George Reid To: Maxime Henrion Cc: freebsd-hackers@FreeBSD.org Subject: Re: New vhost bugs.FreeBSD.org Message-ID: <20011213230536.A35843@FreeBSD.org> References: <20011213224331.B298@nebula.noos.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011213224331.B298@nebula.noos.fr>; from mux@qualys.com on Thu, Dec 13, 2001 at 10:43:31PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 13, 2001 at 10:43:31PM +0100, Maxime Henrion wrote: > It would be very useful, IMO, to have a simple URL like this to access the > PR database. > > Opinions ? Gets my vote. -- George C A Reid Tel: (08701) 200870 Ext. 26654 FreeBSD Committer/Developer greid@FreeBSD.org Oriel College, Oxford University george.reid@oriel.ox.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 15:18:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id 9967E37B405; Thu, 13 Dec 2001 15:18:55 -0800 (PST) Received: from pool0211.cvx21-bradley.dialup.earthlink.net ([209.179.192.211] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Ef7s-0001Fu-00; Thu, 13 Dec 2001 15:18:53 -0800 Message-ID: <3C193762.35C523D8@mindspring.com> Date: Thu, 13 Dec 2001 15:18:58 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: Poul-Henning Kamp , hackers@freebsd.org Subject: Re: Junior Kernel hacker task: Floppy driver mode handling. References: <31764.1008089464@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > Poul-Henning Kamp writes: > > There exists a patch for adding a mode to our floppy driver to > > add DEC RX50 media handling. > > Clearly a job for Jessem, don't you think? :) Kids can be cruel. 8^) 8^). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 15:35: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (oe75.law11.hotmail.com [64.4.16.210]) by hub.freebsd.org (Postfix) with ESMTP id 49EC537B405 for ; Thu, 13 Dec 2001 15:34:58 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 13 Dec 2001 15:34:58 -0800 X-Originating-IP: [63.122.122.73] From: "Mark Brown" To: Subject: uiomove performance? Date: Thu, 13 Dec 2001 18:35:44 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-ID: X-OriginalArrivalTime: 13 Dec 2001 23:34:58.0287 (UTC) FILETIME=[C6DDC7F0:01C1842E] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anyone know if there is a significant performance gain to maintaining scatter/gather lists with uio rather than writing the s/g routine yourself. To be more specific: I currently have a routine that takes a memory segments and places them in a contiguous memory buffer. We need to optimize the routine for better CPU utilization. We currently get the memory list and organize it using memcopy. I would like to use uiomove but it is hard to justify the time needed to convert the current routine to uiomove if there is only a insignificant performance gain. Keep in mind this routine is being called frequently. I would like to justify to my boss that using uiomove would have significant performance benefits over our current routine that uses memcopy. -- Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 15:43:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 39B7737B41B for ; Thu, 13 Dec 2001 15:43:36 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 93B7381E0B; Thu, 13 Dec 2001 17:43:30 -0600 (CST) Date: Thu, 13 Dec 2001 17:43:30 -0600 From: Alfred Perlstein To: Mark Brown Cc: hackers@freebsd.org Subject: Re: uiomove performance? Message-ID: <20011213174330.H79896@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from simm_s_list@hotmail.com on Thu, Dec 13, 2001 at 06:35:44PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Mark Brown [011213 17:35] wrote: > Does anyone know if there is a significant performance gain to maintaining > scatter/gather lists with uio rather than writing the s/g routine yourself. > > To be more specific: > I currently have a routine that takes a memory segments and places them in a > contiguous memory buffer. We need to optimize the routine for better CPU > utilization. We currently get the memory list and organize it using memcopy. > I would like to use uiomove but it is hard to justify the time needed to > convert the current routine to uiomove if there is only a insignificant > performance gain. Keep in mind this routine is being called frequently. > > I would like to justify to my boss that using uiomove would have significant > performance benefits over our current routine that uses memcopy. Uh....... If you have a routine using memcpy then you're effectively making the UIO as you go, making the additional copy is just stupid. It should be trivial to convert the routine and I strongly suggest doing so. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 15:44: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 5C7B537B421 for ; Thu, 13 Dec 2001 15:43:53 -0800 (PST) Received: from bsd.havk.org (user-24-214-88-13.knology.net [24.214.88.13]) by mail.hiwaay.net (8.12.1/8.12.1) with ESMTP id fBDNhoBZ027270 for ; Thu, 13 Dec 2001 17:43:51 -0600 (CST) Received: by bsd.havk.org (Postfix, from userid 1001) id 05B821A786; Thu, 13 Dec 2001 17:43:48 -0600 (CST) Date: Thu, 13 Dec 2001 17:43:47 -0600 From: Steve Price To: hackers@freebsd.org Subject: MMU-less FreeBSD Message-ID: <20011213174347.V597@bsd.havk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.4-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As a rough order of magnitude how hard would it be to port FreeBSD to an architecture (Motorola Coldfire) that doesn't have an MMU? I see some words on their site that the NetBSD folks might be working on some archs that require this. I got my hands on a board similar to the one in the NetTel eLia product and it runs on uClinux. I was just curious if porting FreeBSD would be a couple of month thing or much more involved. Thanks. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 16:33:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 8E1D037B417 for ; Thu, 13 Dec 2001 16:33:38 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBE0dXl04925; Thu, 13 Dec 2001 16:39:33 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112140039.fBE0dXl04925@mass.dis.org> To: "Mark Brown" Cc: hackers@freebsd.org Subject: Re: uiomove performance? In-Reply-To: Message from "Mark Brown" of "Thu, 13 Dec 2001 18:35:44 EST." Date: Thu, 13 Dec 2001 16:39:33 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Does anyone know if there is a significant performance gain to maintaining > scatter/gather lists with uio rather than writing the s/g routine yourself. > > To be more specific: > I currently have a routine that takes a memory segments and places them in a > contiguous memory buffer. We need to optimize the routine for better CPU > utilization. We currently get the memory list and organize it using memcopy. > I would like to use uiomove but it is hard to justify the time needed to > convert the current routine to uiomove if there is only a insignificant > performance gain. Keep in mind this routine is being called frequently. > > I would like to justify to my boss that using uiomove would have significant > performance benefits over our current routine that uses memcopy. It's not clear why you didn't use uiomove to begin with, since it's already written. 8) However, you're most likely constrained by memory bandwidth, and in that case converting to uiomove is unlikely to change things much. It's probably a sane thing to do, however, as uiomove is pretty smart and it will remove what is basically duplicated cod. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 16:43:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3DECC37B405; Thu, 13 Dec 2001 16:43:29 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBE0gBa61696; Thu, 13 Dec 2001 16:42:11 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Dec 2001 16:42:11 -0800 (PST) From: Matthew Dillon Message-Id: <200112140042.fBE0gBa61696@apollo.backplane.com> To: Terry Lambert Cc: David Greenman , Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS Patch #4 -- survived overnight test. (was Re: Found NFS data corruption bug... (was Re:...)) References: <58885.1008217148@winston.freebsd.org> <200112130608.fBD689K49906@apollo.backplane.com> <20011212224927.A73226@nexus.root.com> <200112131835.fBDIZuL70031@apollo.backplane.com> <3C18FAC9.E743DAA5@mindspring.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Matthew Dillon wrote: :[ ... ] :> I would appreciate other VM gurus taking a look at the :> vm_page_set_validclean() changes. :[ ... ] : :Not to appoint myself a guru or anything... : :> +#if 1 :> + if ((base & (DEV_BSIZE - 1)) || (size & (DEV_BSIZE - 1))) { :> + int adj; :> + :> + adj = DEV_BSIZE - (base & (DEV_BSIZE - 1)); :> + base += adj; :> + if (size < adj) :> + size = 0; :> + else :> + size = (size - adj) & ~(DEV_BSIZE - 1); :> + pagebits = vm_page_bits(base, size); :> + } :> +#endif : :This seems wrong. : :Specifically, it seems to only get the first block, in the case that :(integer math: / is "div"): : : ((size - adj)/DEV_BSIZE) > 1 : :How about: : : else { : /* : * Drop partial trailing blocks from the size : * calculation to maintain correct dirty bits; : * note that 'size' might still span more than : * one block, though. : */ : int n_size; /* probably not int? */ : : n_size = (size - adj) / DEV_BSIZE; : size = (size - adj) & ~(DEV_BSIZE - 1); : size += n_size * DEV_BSIZE; : : } : :-- Terry Hmm. Well, my code is definitely broken. My 'adj' calculation is all wrong. However, my size calculation appears to be correct. (size - adj) is the size of the block after the base has been adjusted to the next full chunk. The number of chunks we then generate bits for must be fully enclosed by size and (new_size & ~(DEV_BSIZE - 1)) gives that to us. e.g. if new_size is less then DEV_BSIZE we get 0, correctly indicating that we cannot clear any dirty bits at all. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 16:57:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0695937B405; Thu, 13 Dec 2001 16:57:04 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBE0tmA61806; Thu, 13 Dec 2001 16:55:48 -0800 (PST) (envelope-from dillon) Date: Thu, 13 Dec 2001 16:55:48 -0800 (PST) From: Matthew Dillon Message-Id: <200112140055.fBE0tmA61806@apollo.backplane.com> To: Terry Lambert Cc: David Greenman , Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS Patch #4 -- survived overnight test. (was Re: Found NFS data corruption bug... (was Re:...)) References: <58885.1008217148@winston.freebsd.org> <200112130608.fBD689K49906@apollo.backplane.com> <20011212224927.A73226@nexus.root.com> <200112131835.fBDIZuL70031@apollo.backplane.com> <3C18FAC9.E743DAA5@mindspring.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry's interest prompted me to redo my algorithm a bit and write a program to test it with various combinations of base and size. I've included the program below. My fixed algorithm appears to produce the correct results, which is to generate the DEV_BSIZE aligned range that is fully enclosed within the supplied range. So, for example, a base of 0x0020 and a size of 0x0040 will produce a range of 0x0200 to 0x0200 (i.e. a null range, meaning we can't clear any dirty bits at all for that particular case). I am going to re-test with the new algorithm. Terry, or anyone... if you are interesting in trying out your own algorithm fill it into algorithm2() below and enable the comparison code. Thanks for the comments, Terry! -Matt #include #include #include static void algorithm1(int *base, int *size); static void algorithm2(int *base, int *size); int main(int ac, char **av) { int base; int size; for (base = 0; base <= 4096; base += 32) { for (size = 0; size <= 4096 - base; size += 32) { int nbase1 = base, nsize1 = size; int nbase2 = base, nsize2 = size; algorithm1(&nbase1, &nsize1); printf("%04x-%04x -> %04x-%04x\n", base, base + size, nbase1, nbase1 + nsize1); #if 0 algorithm2(&nbase2, &nsize2); if (nbase1 != nbase2 || nsize1 != nsize2) { printf("%04x-%04x mismatch %04x-%04x vs %04x-%04x\n", base, base + size, nbase1, nbase1 + nsize1, nbase2, nbase2 + nsize2 ); } #endif } } } #define DEV_BSIZE 512 static void algorithm1(int *base, int *size) { int frag; if ((frag = *base & (DEV_BSIZE - 1)) != 0) { frag = DEV_BSIZE - frag; *base += frag; *size -= frag; if (*size < 0) *size = 0; } *size = *size & ~(DEV_BSIZE - 1); } #if 0 static void algorithm2(int *base, int *size) { ... } #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 17:19:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 289DA37B405; Thu, 13 Dec 2001 17:19:44 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fBE1Jga93584; Thu, 13 Dec 2001 18:19:43 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fBE1JgM49561; Thu, 13 Dec 2001 18:19:42 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200112140119.fBE1JgM49561@harmony.village.org> To: Steve Price Subject: Re: MMU-less FreeBSD Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 13 Dec 2001 17:43:47 CST." <20011213174347.V597@bsd.havk.org> References: <20011213174347.V597@bsd.havk.org> Date: Thu, 13 Dec 2001 18:19:42 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011213174347.V597@bsd.havk.org> Steve Price writes: : As a rough order of magnitude how hard would it be to port : FreeBSD to an architecture (Motorola Coldfire) that doesn't : have an MMU? I see some words on their site that the NetBSD : folks might be working on some archs that require this. Hard. Lots of stuff relies on mmap, which basiclly requires an MMU or other tricks. The other tricks can be somewhat expensive... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 19: 4:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 0075037B41B; Thu, 13 Dec 2001 19:04:24 -0800 (PST) Received: from pool0149.cvx22-bradley.dialup.earthlink.net ([209.179.198.149] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Eidy-0004Vy-00; Thu, 13 Dec 2001 19:04:14 -0800 Message-ID: <3C196C33.2A3A6BD0@mindspring.com> Date: Thu, 13 Dec 2001 19:04:19 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: David Greenman , Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: NFS Patch #4 -- survived overnight test. (was Re: Found NFS data corruption bug... (was Re:...)) References: <58885.1008217148@winston.freebsd.org> <200112130608.fBD689K49906@apollo.backplane.com> <20011212224927.A73226@nexus.root.com> <200112131835.fBDIZuL70031@apollo.backplane.com> <3C18FAC9.E743DAA5@mindspring.com> <200112140042.fBE0gBa61696@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: > Hmm. Well, my code is definitely broken. My 'adj' calculation is > all wrong. However, my size calculation appears to be correct. > (size - adj) is the size of the block after the base has been adjusted > to the next full chunk. The number of chunks we then generate bits > for must be fully enclosed by size and (new_size & ~(DEV_BSIZE - 1)) > gives that to us. e.g. if new_size is less then DEV_BSIZE we get 0, > correctly indicating that we cannot clear any dirty bits at all. I missed the size of the operand to the twiddle; mea culpa. I thought you were (effectively) getting a "mod" operation on a "div"'ed value, not the total value. Never mind. 8^). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 19: 6: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (oe43.law11.hotmail.com [64.4.16.15]) by hub.freebsd.org (Postfix) with ESMTP id 6CF9A37B417; Thu, 13 Dec 2001 19:05:57 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 13 Dec 2001 19:05:57 -0800 X-Originating-IP: [24.168.9.122] From: "Mark Brown" To: "Mike Smith" Cc: References: <200112140039.fBE0dXl04925@mass.dis.org> Subject: Re: uiomove (CPU) performance? Date: Thu, 13 Dec 2001 22:06:42 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-ID: X-OriginalArrivalTime: 14 Dec 2001 03:05:57.0203 (UTC) FILETIME=[402B1230:01C1844C] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The code is kernel mode so I do not think the memcopy routine uses uiomove in this case(I could be wrong). Also this code is multiplatform so that the general code uses memcopy and developers optimize the code to work on the different platforms they are in. Speed is not my concern right now because we can max out the speed of the device we are copying from. Our problem lies in the CPU utilization. Will uiomove be better than memcopy in that respect or the same? Thanks in advance, -- Mark ----- Original Message ----- From: "Mike Smith" To: "Mark Brown" Cc: Sent: Thursday, December 13, 2001 7:39 PM Subject: Re: uiomove performance? > > Does anyone know if there is a significant performance gain to maintaining > > scatter/gather lists with uio rather than writing the s/g routine yourself. > > > > To be more specific: > > I currently have a routine that takes a memory segments and places them in a > > contiguous memory buffer. We need to optimize the routine for better CPU > > utilization. We currently get the memory list and organize it using memcopy. > > I would like to use uiomove but it is hard to justify the time needed to > > convert the current routine to uiomove if there is only a insignificant > > performance gain. Keep in mind this routine is being called frequently. > > > > I would like to justify to my boss that using uiomove would have significant > > performance benefits over our current routine that uses memcopy. > > It's not clear why you didn't use uiomove to begin with, since it's already > written. 8) > > However, you're most likely constrained by memory bandwidth, and in > that case converting to uiomove is unlikely to change things much. > > It's probably a sane thing to do, however, as uiomove is pretty smart > and it will remove what is basically duplicated cod. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 19:15:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 1AC1E37B419 for ; Thu, 13 Dec 2001 19:15:32 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id OAA08410 for ; Fri, 14 Dec 2001 14:15:24 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01KBV0J68J28VFJL41@cim.alcatel.com.au> for freebsd-hackers@freebsd.org; Fri, 14 Dec 2001 14:14:52 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.6/8.11.6) id fBE3FJ643173 for freebsd-hackers@freebsd.org; Fri, 14 Dec 2001 14:15:19 +1100 Content-return: prohibited Date: Fri, 14 Dec 2001 14:15:18 +1100 From: Peter Jeremy Subject: Adding a new FS to FreeBSD To: freebsd-hackers@freebsd.org Message-id: <20011214141518.E73243@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Since JFS has come up again... Are there any papers that explain how to integrate a new filesystem into FreeBSD? The relevant chapter in the FreeBSD Developers' Handbook (16) is a bit terse :-). Specifically, I'm looking at being able to read/write 2BSD filesystems on my FreeBSD machines. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 19:35:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id E8A4737B416 for ; Thu, 13 Dec 2001 19:35:32 -0800 (PST) Received: from keenepa.demon.co.uk ([212.228.208.193] helo=keenepa.co.uk) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 16Ej7w-000KrZ-0Y; Fri, 14 Dec 2001 03:35:13 +0000 Received: from mta.excite.com ([63.62.208.92]) by keenepa.co.uk with Microsoft SMTPSVC(5.0.2195.2096); Fri, 14 Dec 2001 03:33:42 +0000 Message-ID: <000006533d36$00006cd0$00006844@mta.excite.com> To: From: SHCCstock@excite.com Subject: SHCC: National Sales Expansion Positions Comapny For Rapid Growth GAGVGXLR Date: Thu, 13 Dec 2001 21:34:45 -1800 MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Reply-To: InewsALert62@excite.com X-OriginalArrivalTime: 14 Dec 2001 03:33:45.0281 (UTC) FILETIME=[226B9310:01C18450] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Investors
     

    Investment Special
    Tonight's Feature Company
    <= font face=3D"Arial" size=3D"3" color=3D"#00CE00">ShareCom, Inc.
    (OTCBB: SHCC)
    <= br>     Current Price: $0.0164

    52 Week High: $2.49
    52 Week Low:= $0.0155

          Why SHCC?
    • SHCC has established business relationships with FEMA, the American Red Cross, AAA, NOAA, and more.

    • SHCC is currently b= ooking revenues of $45,000 per month and projects revenues of $= 13 million for 2002.

    • Partnerships and market ad= vantage fuel exponential growth for SHCC.

    The Time is NOW at Sharecom

    The Federal Emergency Management Agency (FEMA), the National Weather Service (NWS), the Red Cross and AAA are a but a few of the agencies and organizations with whom Share= Com Inc. has forged alliances to ensure clear competitive advantage for its product lines. The past 10 years have = seen a dramatic increase in severe weather conditions=FFFFFF85and with = continued global warming these patterns will exacerbate. Prompted by FEMA = and NWS aggressive programs, demand for the Company=FFFFFF92s NOA= A Weather Radio will soar. Today 7% of American homes possess a NOAA radio=FFFFFF85 the national goal is 100%. 
    ShareCom=FFFFFF92s www.WeatherRadios.com is the site for = consumers to purchase the Company=FFFFFF92s superior product at a significant= discount. SHCC's revenue flow rate is at $45,000/month and rapidly grow= ing. The Company will realize a profit this year and plans to triple = it next.. SHCC's market dominance in this growing "bread and butter", niche business makes it an interesting acquisit= ion candidate and a compelling investment.    <= /p>

    This Just Out: SHCC NEWS
     

    ShareCom, Inc. Ships the First NOAA Weather Radio Feat= uring Instant Localized Setup

    PALATINE, Ill.--(BUSI= NESS WIRE)--Dec. 11, 2001--ShareCom, Inc.(TM), the market le= ader in designing and manufacturing NOAA (Nationa= l Oceanographic and Atmospheric Administration) Weather Radi= o and Disaster Readiness electronics products, today announced availability of its WRP-500 Broadcaster(TM) NOAA Weathe= r Radio, with an SRP of $149.99, available for purchase = via its ecommerce web site and through select retailers around= the country. Like all ShareCom products, the WRP-500 features = a streamlined and fashionable design, coupled with strong pr= ice performance.

    ShareCom manufactures products which are expressly designe= d to support the in-place NOAA Weather Network - an always on (= 24/7) broadcast network that covers 95% of the US. This `= `early warning'' network provides general-purpose weather informa= tion and alerts for hazardous weather or disaster warnings for = people throughout the US.

    The Federal Govern= ment, The American Red Cross and numerous state and lo= cal government agencies are now emphasizing the need for t= he NOAA Weather Radio network, especially since the September= 11th tragedy. A NOAA Weather Radio is now considered as important as having a smoke detector in a home, school or business.

    ``Our market research= indicated a strong need in the marketplace for a NOAA Weather Radio = that looks good in someone's home or office, but that has real = ease of use built into the overall design,'' said Brad Nordling= the CEO of ShareCom, Inc. ``One of the most requested feature enhancements from our consumers has been to provide functionality that enables them to setup a radio right out= of the box, with no cumbersome interface to deal with. The WR= P-500 Broadcaster addresses this need by incorporating our Graph= ical Alert Technology(TM) specialty software - our customers= now have the ability to easily configure their radios in a mat= ter of seconds using a functional scroll down menu.''<= /td>

    Stay tuned for more announcements to come

    More Reasons to Consider Buying SHCC

    1. WeatherRadios.com has been awarded a National Partnership with the Federal Emergency= Management Agency (FEMA) to increase the use of Weather Radios countr= y wide through a program called Project Impact. There are 2,600 Project I= mpact communities in the U.S. The FEMA web site lists WeatherRadios.com = as a national partner providing a banner and link to the WeatherRadios.= com site. The FEMA site receives over 100,000 visitors per day. <= /p>

    2. The National Oceanic and Aerospace Administration (NOAA) has WeatherRadios.com listed first on their web site, telling people w= ere to purchase a NOAA Weather Radio. 

    3. The National Weather Service (NWS) has offered to promo= te corporate sponsorships to the WeatherRadios.com site through recog= nition and media support.   

    4. Local American Red Cross Chapters will promote NOAA Wea= ther Radios through WeatherRadios.com in an exchange for a $5.00 donati= on per radio sold. 

    5. The Chicago Area AAA will feature SHCC's 2WayTalk.com on its web site offering exclusive discounts on Weather Ra= dios, and FRS Family Radios. 2WayTalk.com will also be listed in the AAA magazine called "Home and Away". 

    6. The Federation of Manufactured Home Owners of Florida (FMO) has entered into= a one year agreement that will increase the sale of Weather Radios from = the WeatherRadios.com site. Mailings and web site links will offer a g= roup discount to members and also pay a rebate to the organization for = every radio sold. 

    7. The Owner - Operator Independent Drivers Association (OOIDA)=     has begun to promote the discount that is offered through the WeatherRadios.com site. Magazine articles, mailings, and web site = links will offer a group discount to members and also pay a rebate to th= e organization for every radio sold. This agreement will run for one year. 

    Why Weather Radios are Poised for Growth

    &nbs= p;    NOAA Weather Radios<= /font> automatically alert people of impending severe weather conditions "24/7". This is especially critical for families while sleeping. These devices are fast becoming recognized as essenti= al and potentially life saving for use in homes, businesses, and critical care facilities.

    The National Weather Service (NWS) has stated that there has been an increase in severe weather in th= e last 10 years and this trend is expected to continue. NWS has a publ= ished goal for NOAA Weather Radios to be in every home within the= next 10 years. Currently, approximately just 7% of homes have th= is device. This being said, we can expect a tremendous increas= e in the presence and sale of weather radios over the coming years.= The NWS, NOAA, the Federal Emergency Management Agency (FEMA) and othe= r government agencies have an aggressive education and funding effor= t to reach the 100% goal.

    New technology called Specific Area Message Encoding (SAME) was introduced in the mid 90s. It all= ows users to set an alarm only for their specific geographic area. Thi= s feature is expected to make this tool commonplace in homes alerting families of weather conditions that pose an immediate dan= ger.

    Additionally, 2WayTalk.com will= continue to focus on Internet users who are outdoor enthusiasts. The market continues to be strong and growing. FRS Family Radios are now beco= ming a popular family item on vacations, ski trips, camping, and biking e= vents. They are used for a wide variety of purposes, from staying in touc= h with children playing in the neighborhood, to coordinating soccer tourn= aments and antique auctions. 

    A Final Word About SHCC

    SHCC i= s currently booking $45,000/ month and is conservatively projecting earnings n= ext year of $1.3 million on revenues of $13 million. Unlike mos= t e-commerce ventures, ShareCom's marketing "burn rate" is= very modest. The Company forecasts revenues of $32.5 million the following year, increasing profitability to earn $4.6 million. Giv= en its impressive relationships and the rapidly growing market for its pr= oduct, SHCC's share price of just 1.6 cents makes it a compelling play= for the astute investor. 

    DISCLAIMER: 
    Information within this email contains "forward looking statements" within the meaning of Section 27A of the Securiti= es Act of 1933 and Section 21B of the Securities Exchange Act of 1934. An= y statements that express or involve discussions with respect to predictions, expectations, beliefs, plans, projections, objectives= , goals, assumptions or future events or performance are not stateme= nts of historical fact and may be "forward looking statements."=

    Forward looking statements are based on expectations, estimates an= d projections at the time the statements are made that involve a num= ber of risks and uncertainties which could cause actual results or events to di= ffer materially from those presently anticipated. Forward looking state= ments in this action may be identified through the use of words such as "projects", "foresee", =FFFFFF93expects=FFFFFF= 92=FFFFFF94, =FFFFFF93will,=FFFFFF94  =FFFFFF93anticipates,=FFFFFF94 =FFFFFF93estimates,=FFFFFF94 =FFFFF= F93believes,=FFFFFF94 "understands" or that by statements indicating certain a= ctions =FFFFFF93may,=FFFFFF94 =FFFFFF93could,=FFFFFF94 or =FFFFFF93might=FF= FFFF94 occur.  All information provided within this email pertaining to investing, stocks, securi= ties must be understood as information provided and not investment advi= ce. Investment News Alert advises all readers and subscribers to seek&= nbsp;advice from a registered professional securities representative before de= ciding to trade in stocks featured within this email.  None of the material within this report shall be construed as any kind of inve= stment advice.

    In compliance with the Securities Act of 1933, Section17(b), Inves= tment Special discloses the receipt of $30,000 cash from a third party f= or the publication of this report and additional  services related to SHCC. Be aware of an inherent conflict = of interest resulting from such compensation.  All factual information in this report was gathered from public sources, inclu= ding but not limited to SEC filings, Company Press Releases, and Market Guide.  Investment S= pecial  believes this information to be reliable but can make no guarantee= as to its accuracy or completeness. Use of the material within this emai= l constitutes your acceptance of these terms.
    To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 19:44: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 7C2C337B417 for ; Thu, 13 Dec 2001 19:44:03 -0800 (PST) Received: from bsd.havk.org (user-24-214-88-13.knology.net [24.214.88.13]) by mail.hiwaay.net (8.12.1/8.12.1) with ESMTP id fBE3hvBZ018686; Thu, 13 Dec 2001 21:44:00 -0600 (CST) Received: by bsd.havk.org (Postfix, from userid 1001) id 3CC981A786; Thu, 13 Dec 2001 21:43:53 -0600 (CST) Date: Thu, 13 Dec 2001 21:43:52 -0600 From: Steve Price To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: MMU-less FreeBSD Message-ID: <20011213214352.C597@bsd.havk.org> References: <20011213174347.V597@bsd.havk.org> <200112140119.fBE1JgM49561@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112140119.fBE1JgM49561@harmony.village.org>; from imp@harmony.village.org on Thu, Dec 13, 2001 at 06:19:42PM -0700 X-Operating-System: FreeBSD 4.4-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 13, 2001 at 06:19:42PM -0700, Warner Losh wrote: > > Hard. Lots of stuff relies on mmap, which basiclly requires an MMU or > other tricks. The other tricks can be somewhat expensive... That's sort of what I figured. WRS and possible others use BSD as a basis for their embedded OS on archs without an MMU, right? Got any pointers to these "tricks" you talk about? Thanks. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 19:54:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id BB15D37B405 for ; Thu, 13 Dec 2001 19:54:42 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBE40al06791; Thu, 13 Dec 2001 20:00:37 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112140400.fBE40al06791@mass.dis.org> To: "Mark Brown" Cc: hackers@freebsd.org Subject: Re: uiomove (CPU) performance? In-Reply-To: Message from "Mark Brown" of "Thu, 13 Dec 2001 22:06:42 EST." Date: Thu, 13 Dec 2001 20:00:36 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > The code is kernel mode so I do not think the memcopy routine uses uiomove > in this case(I could be wrong). Also this code is multiplatform so > that the general code uses memcopy and developers optimize the code to work > on the different platforms they are in. Speed is not my > concern right now because we can max out the speed of the device we are > copying from. Our problem lies in the CPU utilization. Will > uiomove be better than memcopy in that respect or the same? Since the restriction is memory bandwidth for the copy, performance is unlikely to be much different. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 19:57:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 039B837B419; Thu, 13 Dec 2001 19:57:53 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBE43pl06844; Thu, 13 Dec 2001 20:03:51 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112140403.fBE43pl06844@mass.dis.org> To: Steve Price Cc: hackers@FreeBSD.ORG Subject: Re: MMU-less FreeBSD In-Reply-To: Message from Steve Price of "Thu, 13 Dec 2001 21:43:52 CST." <20011213214352.C597@bsd.havk.org> Date: Thu, 13 Dec 2001 20:03:51 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Hard. Lots of stuff relies on mmap, which basiclly requires an MMU or > > other tricks. The other tricks can be somewhat expensive... > > That's sort of what I figured. WRS and possible others use BSD > as a basis for their embedded OS on archs without an MMU, right? No. Many embedded operating systems use chunks of BSD code, but you're not going to run a "real" BSD on anything without an MMU; you'll have to cut it down drastically (and effectively rewrite much of the core of the OS. If you want an OS, consider eCOS or one of the "real" embedded systems, don't make too much work for yourself trying to take a system that's entirely unsuited to the task and butchering it... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 20: 6:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id ADA7637B405; Thu, 13 Dec 2001 20:06:34 -0800 (PST) Received: from bsd.havk.org (user-24-214-88-13.knology.net [24.214.88.13]) by mail.hiwaay.net (8.12.1/8.12.1) with ESMTP id fBE46UBZ032687; Thu, 13 Dec 2001 22:06:32 -0600 (CST) Received: by bsd.havk.org (Postfix, from userid 1001) id D05C81A786; Thu, 13 Dec 2001 22:06:27 -0600 (CST) Date: Thu, 13 Dec 2001 22:06:27 -0600 From: Steve Price To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: MMU-less FreeBSD Message-ID: <20011213220627.G597@bsd.havk.org> References: <200112140403.fBE43pl06844@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112140403.fBE43pl06844@mass.dis.org>; from msmith@freebsd.org on Thu, Dec 13, 2001 at 08:03:51PM -0800 X-Operating-System: FreeBSD 4.4-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 13, 2001 at 08:03:51PM -0800, Mike Smith wrote: > > If you want an OS, consider eCOS or one of the "real" embedded systems, > don't make too much work for yourself trying to take a system that's > entirely unsuited to the task and butchering it... In eCOS are you talking about this one? http://sources.redhat.com/ecos/ I'd prefer a free (as in beer) OS so most of the "real" embedded systems won't fit the bill unfortunately. I'd be glad to be proven wrong though if you have some URLs. :) -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 20:10:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 5CF9C37B405; Thu, 13 Dec 2001 20:10:10 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id fBE49uO84394; Thu, 13 Dec 2001 23:09:56 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200112131835.fBDIZuL70031@apollo.backplane.com> References: <58885.1008217148@winston.freebsd.org> <200112130608.fBD689K49906@apollo.backplane.com> <20011212224927.A73226@nexus.root.com> <200112131835.fBDIZuL70031@apollo.backplane.com> Date: Thu, 13 Dec 2001 23:09:54 -0500 To: Matthew Dillon , David Greenman From: Garance A Drosihn Subject: Re: NFS Patch #4 -- survived overnight test. (was Re: Found NFS data corruption bug... (was Re:...)) Cc: Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 10:35 AM -0800 12/13/01, Matthew Dillon wrote: > Are there still bugs in NFS? You bet! I'm sure there are bugs > related to multiple clients and/or the server modifying files out > from under a client, and I think the potential issue with nfsiod > ordering that was posted to the list is a definite possibility. Perhaps the next round of torture-testing (after these are committed!) would be to have multiple clients running the program against a common NFS file server. > But this should go a long way to improving the rock solid > reputation of our stack! This is very excellent! -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 20:16:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 202D837B41B for ; Thu, 13 Dec 2001 20:16:15 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.6/8.11.4) id fBE4FwL84459; Thu, 13 Dec 2001 20:15:58 -0800 (PST) (envelope-from kris) Date: Thu, 13 Dec 2001 20:15:58 -0800 From: Kris Kennaway To: KAISER Laszlo Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SSL_connect fails Message-ID: <20011213201558.B84382@citusc17.usc.edu> References: <20011209184143.H12621@ovinet.hu> <20011210104529.A8829@ovinet.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011210104529.A8829@ovinet.hu>; from titanic@ovinet.hu on Mon, Dec 10, 2001 at 10:45:30AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 10, 2001 at 10:45:30AM +0100, KAISER Laszlo wrote: > On Sun, Dec 09, 2001 at 06:41:43PM +0100, KAISER Laszlo wrote: > > I'm doing a port of a little OpenSSL program to FreeBSD from linux, but= the > > code which works fine on linux fails on FreeBSD at SSL_connect(). > > This function allways returns with -1 and SSL_errno is 1. >=20 > To answer myself; >=20 > The problem was trivial. OpenSSL couldn't seed random generator for corre= ct > entropy without /dev/urandom or without a specified file, therefore i had= to > create a temporary file which consists of enough random numbers (1024). T= his > was problem on solaris port, too, but on BSD it caused by chroot > environment. OpenSSL got the filename consists of entropy from an > environment value named RANDFILE. >=20 > Some notice: > I think an API hasn't consists of exit() calls and if i send a NULL > pointer to an API call, it couldn't SEGFAULT. OpenSSL does. I think it is > not a feature, or if it is, i'like to turn off. :/ Complain to the OpenSSL developers, not us. Kris --qMm9M+Fa2AknHoGS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8GXz8Wry0BWjoQKURApKIAKCgkJzf4coH/DLrSQPjbA9X+MdbHwCdH8ly 3hJf0K95v5eO641BB8eHXYA= =08xF -----END PGP SIGNATURE----- --qMm9M+Fa2AknHoGS-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 20:17:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id C07DC37B416 for ; Thu, 13 Dec 2001 20:17:30 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.6/8.11.4) id fBE4HFm84468; Thu, 13 Dec 2001 20:17:15 -0800 (PST) (envelope-from kris) Date: Thu, 13 Dec 2001 20:17:15 -0800 From: Kris Kennaway To: Peter Wemm Cc: Poul-Henning Kamp , mitko@rila.bg, hackers@FreeBSD.ORG Subject: Re: Performance issue Message-ID: <20011213201715.C84382@citusc17.usc.edu> References: <72360.1007898170@critter.freebsd.dk> <20011209232328.31DC43810@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="/NkBOFFp2J2Af1nK" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011209232328.31DC43810@overcee.netplex.com.au>; from peter@wemm.org on Sun, Dec 09, 2001 at 03:23:28PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --/NkBOFFp2J2Af1nK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 09, 2001 at 03:23:28PM -0800, Peter Wemm wrote: > Poul-Henning Kamp wrote: > >=20 > > There are many effects that could cause this, for instance if FreeBSD > > manages to align things differently in relation to the CPU cache you > > could get some very interesting waste of time that way. > >=20 > > Based on the data you show me, I can't really say that something is > > wrong or right either way. >=20 > One thing that Linux does that we do not do is that they have different > versions of libc compiled specifically for different cpu types, and at > boot time set the correct paths. eg: /lib/i386/libc.so.6.whatever >=20 > This means that Linux's glibc is using an i686 optimized bzero(), but > the FreeBSD one is using an i386 optimized bzero(). This could easily be hung off CPUTYPE like we do for the asm code in OpenSSL, right? Kris --/NkBOFFp2J2Af1nK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8GX1KWry0BWjoQKURArxbAKDEDbXpTaQ+Jn4RjXTiBUk+N2iLbgCeL5JQ EfETjwio2rIyeFf3uJs2wbM= =m9hd -----END PGP SIGNATURE----- --/NkBOFFp2J2Af1nK-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 20:29:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 67A1137B417; Thu, 13 Dec 2001 20:29:09 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBE4Z8l07129; Thu, 13 Dec 2001 20:35:09 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112140435.fBE4Z8l07129@mass.dis.org> To: Steve Price Cc: hackers@FreeBSD.ORG Subject: Re: MMU-less FreeBSD In-Reply-To: Message from Steve Price of "Thu, 13 Dec 2001 22:06:27 CST." <20011213220627.G597@bsd.havk.org> Date: Thu, 13 Dec 2001 20:35:08 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > If you want an OS, consider eCOS or one of the "real" embedded systems, > > don't make too much work for yourself trying to take a system that's > > entirely unsuited to the task and butchering it... > > In eCOS are you talking about this one? > > http://sources.redhat.com/ecos/ Yes. > I'd prefer a free (as in beer) OS so most of the "real" embedded > systems won't fit the bill unfortunately. I'd be glad to be > proven wrong though if you have some URLs. :) Well, eCos is free-as-in-beer. You can try RTEMS as well; www.rtems.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 20:58: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id BD09F37B417; Thu, 13 Dec 2001 20:58:00 -0800 (PST) Received: from bsd.havk.org (user-24-214-88-13.knology.net [24.214.88.13]) by mail.hiwaay.net (8.12.1/8.12.1) with ESMTP id fBE4vsBZ022393; Thu, 13 Dec 2001 22:57:57 -0600 (CST) Received: by bsd.havk.org (Postfix, from userid 1001) id A02EC1A787; Thu, 13 Dec 2001 22:57:52 -0600 (CST) Date: Thu, 13 Dec 2001 22:57:52 -0600 From: Steve Price To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: MMU-less FreeBSD Message-ID: <20011213225752.I597@bsd.havk.org> References: <200112140435.fBE4Z8l07129@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112140435.fBE4Z8l07129@mass.dis.org>; from msmith@freebsd.org on Thu, Dec 13, 2001 at 08:35:08PM -0800 X-Operating-System: FreeBSD 4.4-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 13, 2001 at 08:35:08PM -0800, Mike Smith wrote: > > Well, eCos is free-as-in-beer. From a quick glance at the license it looks to be a lot more like the GPL than a BSD license but I'll dig deeper. 'Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License via an accepted Electronic Distribution Mechanism to anyone to whom you made an Executable...' > You can try RTEMS as well; www.rtems.com. Ah yes, that's the one I was trying to remember. Thanks Mike. Funny thing (or maybe not) is that these folks are right here in town with me and for the life of my I couldn't remember their name. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 13 23:57:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id CC90F37B41B; Thu, 13 Dec 2001 23:57:17 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fBE7vGa94528; Fri, 14 Dec 2001 00:57:17 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fBE7vGM50995; Fri, 14 Dec 2001 00:57:16 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200112140757.fBE7vGM50995@harmony.village.org> To: Steve Price Subject: Re: MMU-less FreeBSD Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 13 Dec 2001 21:43:52 CST." <20011213214352.C597@bsd.havk.org> References: <20011213214352.C597@bsd.havk.org> <20011213174347.V597@bsd.havk.org> <200112140119.fBE1JgM49561@harmony.village.org> Date: Fri, 14 Dec 2001 00:57:16 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011213214352.C597@bsd.havk.org> Steve Price writes: : On Thu, Dec 13, 2001 at 06:19:42PM -0700, Warner Losh wrote: : > : > Hard. Lots of stuff relies on mmap, which basiclly requires an MMU or : > other tricks. The other tricks can be somewhat expensive... : : That's sort of what I figured. WRS and possible others use BSD : as a basis for their embedded OS on archs without an MMU, right? Not sure. : Got any pointers to these "tricks" you talk about? Thanks. Maybe the easiest way to find out about them would be to look at the uclinux stuff. It uses them. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 0:27: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 2502137B438; Fri, 14 Dec 2001 00:26:57 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id AAB7881E11; Fri, 14 Dec 2001 02:26:51 -0600 (CST) Date: Fri, 14 Dec 2001 02:26:51 -0600 From: Alfred Perlstein To: Kris Kennaway Cc: Peter Wemm , Poul-Henning Kamp , mitko@rila.bg, hackers@FreeBSD.ORG Subject: Re: Performance issue Message-ID: <20011214022651.I79896@elvis.mu.org> References: <72360.1007898170@critter.freebsd.dk> <20011209232328.31DC43810@overcee.netplex.com.au> <20011213201715.C84382@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011213201715.C84382@citusc17.usc.edu>; from kris@FreeBSD.ORG on Thu, Dec 13, 2001 at 08:17:15PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Kris Kennaway [011213 22:17] wrote: > On Sun, Dec 09, 2001 at 03:23:28PM -0800, Peter Wemm wrote: > > Poul-Henning Kamp wrote: > > > > > > There are many effects that could cause this, for instance if FreeBSD > > > manages to align things differently in relation to the CPU cache you > > > could get some very interesting waste of time that way. > > > > > > Based on the data you show me, I can't really say that something is > > > wrong or right either way. > > > > One thing that Linux does that we do not do is that they have different > > versions of libc compiled specifically for different cpu types, and at > > boot time set the correct paths. eg: /lib/i386/libc.so.6.whatever > > > > This means that Linux's glibc is using an i686 optimized bzero(), but > > the FreeBSD one is using an i386 optimized bzero(). > > This could easily be hung off CPUTYPE like we do for the asm code in > OpenSSL, right? That's not the point, you're proposing a static configuration which i honestly don't like. What makes more sense is to teach the dynamic linker to look for archetecture specific subdirectories in order to dynamically link in a shared object more suited to the running CPU, not the CPU it was compiled on. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 0:39:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id B4EDA37B43A; Fri, 14 Dec 2001 00:39:17 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBE8dF222658; Fri, 14 Dec 2001 00:39:15 -0800 (PST) (envelope-from dillon) Date: Fri, 14 Dec 2001 00:39:15 -0800 (PST) From: Matthew Dillon Message-Id: <200112140839.fBE8dF222658@apollo.backplane.com> To: Alfred Perlstein Cc: Kris Kennaway , Peter Wemm , Poul-Henning Kamp , mitko@rila.bg, hackers@FreeBSD.ORG Subject: Re: Performance issue References: <72360.1007898170@critter.freebsd.dk> <20011209232328.31DC43810@overcee.netplex.com.au> <20011213201715.C84382@citusc17.usc.edu> <20011214022651.I79896@elvis.mu.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :That's not the point, you're proposing a static configuration :which i honestly don't like. What makes more sense is to :teach the dynamic linker to look for archetecture specific :subdirectories in order to dynamically link in a shared object :more suited to the running CPU, not the CPU it was compiled on. : :-- :-Alfred Perlstein [alfred@freebsd.org] What Alfred said. We could have a base version that the linker uses (and has always used... backwards compatible), and special versions that are cpu-specific that the linker uses instead of it sees them and they match the current cpu. It would work quite nicely and it wouldn't require N different copies of libc. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 0:46: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id E360237B416; Fri, 14 Dec 2001 00:46:00 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.6/8.11.4) id fBE8jx586110; Fri, 14 Dec 2001 00:45:59 -0800 (PST) (envelope-from kris) Date: Fri, 14 Dec 2001 00:45:59 -0800 From: Kris Kennaway To: Alfred Perlstein Cc: Kris Kennaway , Peter Wemm , Poul-Henning Kamp , mitko@rila.bg, hackers@FreeBSD.ORG Subject: Re: Performance issue Message-ID: <20011214004559.B86064@citusc17.usc.edu> References: <72360.1007898170@critter.freebsd.dk> <20011209232328.31DC43810@overcee.netplex.com.au> <20011213201715.C84382@citusc17.usc.edu> <20011214022651.I79896@elvis.mu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011214022651.I79896@elvis.mu.org>; from bright@mu.org on Fri, Dec 14, 2001 at 02:26:51AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 14, 2001 at 02:26:51AM -0600, Alfred Perlstein wrote: > > This could easily be hung off CPUTYPE like we do for the asm code in > > OpenSSL, right? >=20 > That's not the point, you're proposing a static configuration > which i honestly don't like. What makes more sense is to > teach the dynamic linker to look for archetecture specific > subdirectories in order to dynamically link in a shared object > more suited to the running CPU, not the CPU it was compiled on. Yes, well, we already compile the *entire tree* with static (compile-time) optimizations when CPUTYPE is set, so one more (bzero) is no difference except that it gives an extra performance benefit. Kris --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8GbxGWry0BWjoQKURAijvAJ9uUPvSHVGF2gDHhW68piM/9M4ltACg4ViI ktY0M+KS/POZlsjKgKwJwwM= =08oY -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 0:55:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id D515837B416; Fri, 14 Dec 2001 00:55:33 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 53CC881E10; Fri, 14 Dec 2001 02:55:33 -0600 (CST) Date: Fri, 14 Dec 2001 02:55:33 -0600 From: Alfred Perlstein To: Kris Kennaway Cc: Peter Wemm , Poul-Henning Kamp , mitko@rila.bg, hackers@FreeBSD.ORG Subject: Re: Performance issue Message-ID: <20011214025533.J79896@elvis.mu.org> References: <72360.1007898170@critter.freebsd.dk> <20011209232328.31DC43810@overcee.netplex.com.au> <20011213201715.C84382@citusc17.usc.edu> <20011214022651.I79896@elvis.mu.org> <20011214004559.B86064@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011214004559.B86064@citusc17.usc.edu>; from kris@FreeBSD.ORG on Fri, Dec 14, 2001 at 12:45:59AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Kris Kennaway [011214 02:46] wrote: > > Yes, well, we already compile the *entire tree* with static > (compile-time) optimizations when CPUTYPE is set, so one more (bzero) > is no difference except that it gives an extra performance benefit. Wait, you go to each and every freebsd install and do a make world? The point is we can do this dynamically, in fact we don't even need to teach the linker how to do it, we can do it via the startup scripts by checking a sysctl and providing the subdir to ldconfig. :) -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 1:37:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.rila.bg (earth.rila.bg [194.141.1.31]) by hub.freebsd.org (Postfix) with ESMTP id DFC2737B405; Fri, 14 Dec 2001 01:37:10 -0800 (PST) Received: from earth.rila.bg (mitko@localhost.rila.bg [127.0.0.1]) by earth.rila.bg (8.11.6/8.11.6) with SMTP id fBE9at516397; Fri, 14 Dec 2001 11:36:56 +0200 (EET) (envelope-from mitko@rila.bg) Date: Fri, 14 Dec 2001 11:36:55 +0200 From: Dimitar Peikov To: Alfred Perlstein Cc: kris@FreeBSD.ORG, peter@wemm.org, phk@critter.freebsd.dk, hackers@FreeBSD.ORG Subject: Re: Performance issue Message-Id: <20011214113655.75d89751.mitko@rila.bg> In-Reply-To: <20011214025533.J79896@elvis.mu.org> References: <72360.1007898170@critter.freebsd.dk> <20011209232328.31DC43810@overcee.netplex.com.au> <20011213201715.C84382@citusc17.usc.edu> <20011214022651.I79896@elvis.mu.org> <20011214004559.B86064@citusc17.usc.edu> <20011214025533.J79896@elvis.mu.org> Reply-To: mitko@rila.bg Organization: Rila Solutions X-Mailer: Sylpheed version 0.6.5 (GTK+ 1.2.10; i386--freebsd4.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 14 Dec 2001 02:55:33 -0600 Alfred Perlstein wrote: > * Kris Kennaway [011214 02:46] wrote: > > > > Yes, well, we already compile the *entire tree* with static > > (compile-time) optimizations when CPUTYPE is set, so one more (bzero) > > is no difference except that it gives an extra performance benefit. > > Wait, you go to each and every freebsd install and do a make world? > > The point is we can do this dynamically, in fact we don't even need > to teach the linker how to do it, we can do it via the startup > scripts by checking a sysctl and providing the subdir to ldconfig. > > :) > > -- > -Alfred Perlstein [alfred@freebsd.org] > 'Instead of asking why a piece of software is using "1970s technology," > start asking why software is ignoring 30 years of accumulated wisdom.' > http://www.morons.org/rants/gpl-harmful.php3 Yes, this would be great, but I think that bzero() is for example, there are too many functions from the libraries that could be optimized as well. These are all string and memory manipulation routines with extentions such us MMX, SIMD, 3dnow, ... This would not be 5 min implementation at all. -- Dimitar Peikov Programmer Analyst Globalization Group "We Build e-Business" RILA Solutions 27 Building, Acad.G.Bonchev Str. 1113 Sofia, Bulgaria phone: (+359 2) 9797320 phone: (+359 2) 9797300 fax: (+359 2) 9733355 http://www.rila.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 2:10:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id F042237B43E; Fri, 14 Dec 2001 02:10:37 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBEAGYl09882; Fri, 14 Dec 2001 02:16:36 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112141016.fBEAGYl09882@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Steve Price Cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: MMU-less FreeBSD In-reply-to: Your message of "Thu, 13 Dec 2001 22:57:52 CST." <20011213225752.I597@bsd.havk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Dec 2001 02:16:34 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > On Thu, Dec 13, 2001 at 08:35:08PM -0800, Mike Smith wrote: > > > > Well, eCos is free-as-in-beer. > > >From a quick glance at the license it looks to be a lot more like > the GPL than a BSD license but I'll dig deeper. > > 'Any Modification which You create or to which You contribute must > be made available in Source Code form under the terms of this License > via an accepted Electronic Distribution Mechanism to anyone to whom you > made an Executable...' That's free-as-in-beer; what you want is "unrestricted", different entirely. 8) > > You can try RTEMS as well; www.rtems.com. > > Ah yes, that's the one I was trying to remember. Thanks Mike. > Funny thing (or maybe not) is that these folks are right here > in town with me and for the life of my I couldn't remember > their name. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 4:28:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from primus.vsservices.com (primus.vsservices.com [63.66.136.75]) by hub.freebsd.org (Postfix) with ESMTP id 12CEF37B419 for ; Fri, 14 Dec 2001 04:28:31 -0800 (PST) Received: from prime.vsservices.com (conr-adsl-dhcp-26-38.txucom.net [209.34.26.38]) by primus.vsservices.com (8.11.3/8.11.3) with SMTP id fBDLQHC58111 for ; Thu, 13 Dec 2001 13:26:17 -0800 (PST) (envelope-from gclarkii@vsservices.com) Content-Type: text/plain; charset="iso-8859-1" From: GB Clark II To: hackers@FreeBSD.ORG Subject: shared mem and locking it in core (Database usage) Date: Thu, 13 Dec 2001 15:26:18 -0600 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01121315261800.27037@prime.vsservices.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I'm running PostgreSQL and it uses SysV shared mem for alot of its functions. How can verify that the shared mem is wired and not pageable? sysctl settings: kern.ipc.shmmax: 128004097 kern.ipc.shmmin: 1 kern.ipc.shmmni: 512 kern.ipc.shmseg: 1024 kern.ipc.shmall: 31251 kern.ipc.shm_use_phys: 1 <- This wires the mem right? Yes postgres shows to be 119M via top, but is this mem wired? Thanks, GB -- GB Clark II | Roaming FreeBSD Admin gclarkii@VSServices.COM | General Geek CTHULU for President - Why choose the lesser of two evils? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 6:16:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id DD61D37B417 for ; Fri, 14 Dec 2001 06:16:36 -0800 (PST) Received: from pool0017.cvx22-bradley.dialup.earthlink.net ([209.179.198.17] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Et8R-0007bR-00; Fri, 14 Dec 2001 06:16:23 -0800 Message-ID: <3C1A09BB.DEBCB854@mindspring.com> Date: Fri, 14 Dec 2001 06:16:27 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Jeremy Cc: freebsd-hackers@freebsd.org Subject: Re: Adding a new FS to FreeBSD References: <20011214141518.E73243@gsmx07.alcatel.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Jeremy wrote: > Since JFS has come up again... Are there any papers that explain how > to integrate a new filesystem into FreeBSD? The relevant chapter in > the FreeBSD Developers' Handbook (16) is a bit terse :-). > > Specifically, I'm looking at being able to read/write 2BSD filesystems > on my FreeBSD machines. Do you have small images of this FS, as well as header files that are redistributable (e.g. BSD license) and/or code? I could do the work for this as an example, if you wanted, since it should be almost no work at all, with sources under BSD license, but I would need to be able to dictate some FS image contents, which you would then need to "dd" into a file, compress, and ship to me (the intent would be to create an FS writer's tutorial; this may or may not end up in the handbook... I'd probably want to get a Dr. Dobb's article out of it first, I think). In particular, I would want the following images, as small as possible, along with whatever information you could give me in the way of BSD licensed headers and source (start with a "dd" image of all zero, so it will compress very well, and so it will contain only the delta data): 1) An empty FS 2) The same FS, with one one byte file created 3) The same FS, with two one byte files created 4) The same fs, with the first file deleted 5) An empty FS with an empty directory created 6) The same FS, with one one byte file created in the directory etc. (I will ask for more, if I need more). Floppy images are best, if the thing doesn't care what it runs on, since you can pre-"dd" /dev/zero on top of it, and I can get a vanilla "newfs" image. If you have the tools sources (e.g. "newfs", "fsck", etc.), this would be useful, as well, since I could vnconfig a device and recreate an empty FS image with native tools (self hosted), as well. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 6:18:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from www.yahho.com (28.c210-85-16.ethome.net.tw [210.85.16.28]) by hub.freebsd.org (Postfix) with SMTP id C689437B416; Fri, 14 Dec 2001 06:17:23 -0800 (PST) Received: from tpts5 by titan.seed.net.tw with SMTP id ieeaSB0NFVCdBkoUC7sbnj; Fri, 14 Dec 2001 22:24:56 +0800 Message-ID: From: Santa@yahoo.com To: Subject:Merry Christmas MIME-Version: 1.0 Content-Type: multipart/related; type="multipart/alternative"; boundary="----=_NextPart_dWS8e4H5ubXjneRRoat" X-Mailer: oZma3iezzmlIMEBlK X-Priority: 3 X-MSMail-Priority: Normal Date: Fri, 14 Dec 2001 06:17:23 -0800 (PST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_dWS8e4H5ubXjneRRoat Content-Type: multipart/alternative; boundary="----=_NextPart_dWS8e4H5ubXjneRRoatAA" ------=_NextPart_dWS8e4H5ubXjneRRoatAA Content-Type: text/html; charset="big5" Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT5VbnRpdGxlZCBEb2N1bWVudDwvdGl0bGU+DQo8bWV0YSBo dHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD1iaWc1 Ij4NCjwvaGVhZD4NCg0KPGJvZHkgYmdjb2xvcj0iI0ZGRkZGRiI+DQo8b2JqZWN0IGNsYXNzaWQ9 ImNsc2lkOkQyN0NEQjZFLUFFNkQtMTFjZi05NkI4LTQ0NDU1MzU0MDAwMCIgY29kZWJhc2U9Imh0 dHA6Ly9kb3dubG9hZC5tYWNyb21lZGlhLmNvbS9wdWIvc2hvY2t3YXZlL2NhYnMvZmxhc2gvc3dm bGFzaC5jYWIjdmVyc2lvbj00LDAsMiwwIiB3aWR0aD0iNTUwIiBoZWlnaHQ9IjMyNCI+DQogIDxw YXJhbSBuYW1lPSJfY3giIHZhbHVlPSIxNDU1MiI+DQogIDxwYXJhbSBuYW1lPSJfY3kiIHZhbHVl PSI4NTczIj4NCiAgPHBhcmFtIG5hbWU9Ik1vdmllIiB2YWx1ZT0iaHR0cDovL3d3dy5pdmlkZW8u Y29tLnR3L2ZsYXNoL2UtY2FyZC5zd2YiPg0KICA8cGFyYW0gbmFtZT0iU3JjIiB2YWx1ZT0iaHR0 cDovL3d3dy5pdmlkZW8uY29tLnR3L2ZsYXNoL2UtY2FyZC5zd2YiPg0KICA8cGFyYW0gbmFtZT0i V01vZGUiIHZhbHVlPSJXaW5kb3ciPg0KICA8cGFyYW0gbmFtZT0iUGxheSIgdmFsdWU9IjAiPg0K ICA8cGFyYW0gbmFtZT0iTG9vcCIgdmFsdWU9Ii0xIj4NCiAgPHBhcmFtIG5hbWU9IlF1YWxpdHki IHZhbHVlPSJIaWdoIj4NCiAgPHBhcmFtIG5hbWU9IlNBbGlnbiIgdmFsdWU+DQogIDxwYXJhbSBu YW1lPSJNZW51IiB2YWx1ZT0iLTEiPg0KICA8cGFyYW0gbmFtZT0iQmFzZSIgdmFsdWU+DQogIDxw YXJhbSBuYW1lPSJTY2FsZSIgdmFsdWU9IlNob3dBbGwiPg0KICA8cGFyYW0gbmFtZT0iRGV2aWNl Rm9udCIgdmFsdWU9IjAiPg0KICA8cGFyYW0gbmFtZT0iRW1iZWRNb3ZpZSIgdmFsdWU9IjAiPg0K ICA8cGFyYW0gbmFtZT0iQkdDb2xvciIgdmFsdWU+DQogIDxwYXJhbSBuYW1lPSJTV1JlbW90ZSIg dmFsdWU+DQogIDxwYXJhbSBuYW1lPSJTdGFja2luZyIgdmFsdWU9ImJlbG93Ij48ZW1iZWQgc3Jj PSJodHRwOi8vd3d3Lml2aWRlby5jb20udHcvZmxhc2gvZS1jYXJkLnN3ZiIgcXVhbGl0eT0iaGln aCIgcGx1Z2luc3BhZ2U9Imh0dHA6Ly93d3cubWFjcm9tZWRpYS5jb20vc2hvY2t3YXZlL2Rvd25s b2FkL2luZGV4LmNnaT9QMV9Qcm9kX1ZlcnNpb249U2hvY2t3YXZlRmxhc2giIHR5cGU9ImFwcGxp Y2F0aW9uL3gtc2hvY2t3YXZlLWZsYXNoIiB3aWR0aD0iNTUwIiBoZWlnaHQ9IjMyNCI+IA0KPC9v YmplY3Q+IA0KDQo8cD48YSBocmVmPSJodHRwOi8vd3d3Lml2aWRlby5jb20udHcvZmxhc2gvcm9t YW5jZS5hc3AiPjxpbWcgYm9yZGVyPSIwIiBzcmM9Imh0dHA6Ly93d3cuaXZpZGVvLmNvbS50dy9m bGFzaC9pbWFnZXMvaG9tZV8xLmdpZiIgd2lkdGg9IjE1MiIgaGVpZ2h0PSI3MCI+PC9hPjwvcD4N CjwvYm9keT4NCjwvaHRtbD4= ------=_NextPart_dWS8e4H5ubXjneRRoatAA-- ------=_NextPart_dWS8e4H5ubXjneRRoat-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 6:37:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by hub.freebsd.org (Postfix) with ESMTP id 4ED3337B417; Fri, 14 Dec 2001 06:37:02 -0800 (PST) Received: from fwd07.sul.t-online.de by mailout04.sul.t-online.de with smtp id 16EtSP-0003xk-03; Fri, 14 Dec 2001 15:37:01 +0100 Received: from port001.luna8.com (520001623117-0001@[80.132.146.240]) by fmrl07.sul.t-online.com with esmtp id 16EtS6-0KkMmuC; Fri, 14 Dec 2001 15:36:42 +0100 Received: by port001.luna8.com (Postfix, from userid 1001) id 38742B726; Fri, 14 Dec 2001 12:51:59 +0100 (CET) Date: Fri, 14 Dec 2001 12:51:59 +0100 From: Sven Huster To: freebsd-questions@FreeBSD.ORG, freebsd-hackers@freebsd.org Subject: Re: sa output Message-ID: <20011214115158.GA67285@port001.luna8.com> Mail-Followup-To: freebsd-questions@FreeBSD.ORG, freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23.2i X-Sender: 520001623117-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG now cross-posting maybe someone can give me a hint at least On Mon, Dec 10, 2001 at 11:22:55AM +0100, Sven Huster wrote: > ----- Original Message ----- > From: "Josh Paetzel" > To: "Sven Huster" > Cc: "FBSD-Q" > Sent: 09 December, 2001 21:41 > Subject: Re: sa output > > > > On Sun, Dec 09, 2001 at 12:46:56PM +0100, Sven Huster wrote: > > > hi > > > > > > what does this output of sa mean? > > > 5 8.58re 0.00cp 0avio 323600k pipe > > > > > > i am looking especially at the '323600k' other stuff should be clear. > > > > > > > According to the man page it is: CPU-time averaged core usage, in 1k > > units. > > > > Hope that makes sense to you, cause it didn't to me. > > > > that why i asked, already went through the man page... > but to me it does not make sense either > regards -- Sven Huster To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 7: 7:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-m07.mx.aol.com (imo-m07.mx.aol.com [64.12.136.162]) by hub.freebsd.org (Postfix) with ESMTP id A1CDA37B417; Fri, 14 Dec 2001 07:07:36 -0800 (PST) Received: from CB1001@aol.com by imo-m07.mx.aol.com (mail_out_v31_r1.9.) id c.6d.1f1ac6d0 (3973); Fri, 14 Dec 2001 10:07:21 -0500 (EST) From: CB1001@aol.com Message-ID: <6d.1f1ac6d0.294b6fa9@aol.com> Date: Fri, 14 Dec 2001 10:07:21 EST Subject: RE: 3com card problems To: hueber@riic.at Cc: hackers@freebsd.org, isp@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 138 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, You claim the 3Coms are no good choice for FBSD. I have always been very satisfied with 3Com905B devices. And a quick search did not reveal any major problems with the 3com cards. Pls, can you explain the problem in more detail or direct me to more detailed information (how to avoid impacts with STATS ...) Thank you Gernot Hueber To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 7:17:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-m08.mx.aol.com (imo-m08.mx.aol.com [64.12.136.163]) by hub.freebsd.org (Postfix) with ESMTP id F212A37B417; Fri, 14 Dec 2001 07:17:28 -0800 (PST) Received: from CB1001@aol.com by imo-m08.mx.aol.com (mail_out_v31_r1.9.) id c.15d.5ca814f (3973); Fri, 14 Dec 2001 10:17:20 -0500 (EST) From: CB1001@aol.com Message-ID: <15d.5ca814f.294b71ff@aol.com> Date: Fri, 14 Dec 2001 10:17:19 EST Subject: Re: (no subject) To: hueber@riic.at Cc: hackers@freebsd.org, isp@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 138 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 12/14/01 10:09:20 AM Eastern Standard Time, CB1001 writes: > Hi, > > You claim the 3Coms are no good choice for FBSD. I have always been very > satisfied > with 3Com905B devices. > And a quick search did not reveal any major problems with the 3com cards. A "quick search" of what? Get some perspective. The "hackers" are only interested in cards that they use, and they all use intel for high end stuff. Bill paul is too busy writing drivers for some new gigabit card to worry about old stuff. (note that most of his drivers are optimised for the Alpha and not i386...like what pct of people are using Alpha?) And there is apparantly no interest in fixing anything or finding out whats wrong because some guy at freebsd with a 2 inch weener keeps knocking me off the list...they dont like criticism. I've already fixed it, so all im trying to do is save you a lot of time doing work thats already been done. > > Pls, can you explain the problem in more detail or direct me to more > detailed > information (how to avoid impacts with STATS ...) I did in my last post. Im sure one of the hackers can explain it to you. Or you can look at the linux driver and see what they've done about it. Maybe if someone who cares is listening it will make it into the tree. db To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 8: 4: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ws4-4.us4.outblaze.com (205-158-62-105.outblaze.com [205.158.62.105]) by hub.freebsd.org (Postfix) with SMTP id 0330B37B427 for ; Fri, 14 Dec 2001 08:03:55 -0800 (PST) Received: (qmail 3306 invoked by uid 1001); 14 Dec 2001 15:03:49 -0000 Message-ID: <20011214150349.3305.qmail@linuxmail.org> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from ws4-4.us4.outblaze.com for [80.63.107.247] via web-mailer on Fri, 14 Dec 2001 23:03:49 +0800 From: "Rafter Man" To: freebsd-hackers@FreeBSD.org Date: Fri, 14 Dec 2001 23:03:49 +0800 Subject: New feutures........... Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi FreeBSD lovers :-) First af all I would like to thank the FreeBSD developers for making such a great system! Half a year ago, I had to choose an OS for my server and the first decision was between Windows and Unix, ofcourse it didn't take much research to determine that Unix were the better choice. But now I had to choose from Linux, Solaris and one of the BSD's, and one of the BSD's is was. After a little reseach I had nerroed it down to OpenBSD and FreeBSD, and FreeBSD won me over :-) But enough of this, on to the 2 requests: 1. Is there a way to hide a user from other users? Fx programs like w, who, users, netstat, top, ps all show what other users are doing. It would fx be a good idea to hide root or the admin's activities from other users. If you are trying to catch a cracker, then you know that he/she if not stupid enough to login while other users (especial root) are online. But perhaps this feuture to hide a user already exists? 2. After having read "Operating systems - Internals and Design Principles" by William Stallings I have a few questions. He writes, among other things, about VM, process and tread design, and compares Unix SVR4, Solaris and Windows NT. Sometimes he more or less say, that what fx Solaris have done is the way of the future and other times the unix way was the bedst. I don't want to discuss why FreeBSD have designed the kernel as they have, but I know that sometimes when you work very closely with something, you forget to "look up". I mean, does FreeBSD analyse the Linux and Solaris kernel, maybe adobt some of the good thing they have made? I don't expect FreeBSD to rewrite the kernel, but to learn from Solaris and Linux. If FreeBSD allready do this, then I am sorry for having troubled you with this mail!!! Best regards Rafter ps: 1. I hope that in the future FreeBSD will remain a servers only OS. Meaning that I hope the developers don't spend to much time making games, grafical programs and stuff like gnome/kde/x11. 2. I hope that in the furture the FreeBSD developers will rewrite the system in C++. 3. I hope for even more focuse on security. 4. I will do my part and help FreeBSD the bedst I can. -- Get your free email from www.linuxmail.org Powered by Outblaze To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 8:59:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 7C6D637B405 for ; Fri, 14 Dec 2001 08:59:24 -0800 (PST) Received: from pool0017.cvx22-bradley.dialup.earthlink.net ([209.179.198.17] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Evg2-000469-00; Fri, 14 Dec 2001 08:59:14 -0800 Message-ID: <3C1A2FE6.5636393F@mindspring.com> Date: Fri, 14 Dec 2001 08:59:18 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rafter Man Cc: freebsd-hackers@FreeBSD.org Subject: Re: New feutures........... References: <20011214150349.3305.qmail@linuxmail.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Rafter Man wrote: > 1. Is there a way to hide a user from other users? Fx programs > like w, who, users, netstat, top, ps all show what other users > are doing. The most common approach to this is to run the exterior services in a "jail" (see: "man jail"). When the user logs into the jail, they do not see users in other jails, and they do not see users in the host environment (outside the jail). > I mean, does FreeBSD analyse the Linux and Solaris kernel, maybe > adobt some of the good thing they have made? I don't expect > FreeBSD to rewrite the kernel, but to learn from Solaris and Linux. > If FreeBSD allready do this, then I am sorry for having troubled > you with this mail!!! FreeBSD already does this, as for as it can do so without violating license restrictions (e.g. looking at the Solaris sources is risky). > ps: 1. I hope that in the future FreeBSD will remain a servers > only OS. Meaning that I hope the developers don't spend to much > time making games, grafical programs and stuff like gnome/kde/x11. The developers will work on what they want to work on. If that happens to be KDE, then it happens to be KDE. If not, then not. > 2. I hope that in the furture the FreeBSD developers will rewrite > the system in C++. Not likely, due to the overhead. You might want to check out "SPRITE" (out of UCB), or "Choices" (out of UKY), if you are really wanting a C++ based OS. There are several very hard chicken-and-egg problems, e.g. the construction of pure virtual based class shared method instances, and so on, which are normally handled by the host OS calling .init entry points at program startup, which would be difficult or impossible to do without tools modifications for a self-hosting OS. > 3. I hope for even more focuse on security. > 4. I will do my part and help FreeBSD the bedst I can. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 9:26: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from espresso.q9media.com (espresso.q9media.com [216.254.138.122]) by hub.freebsd.org (Postfix) with ESMTP id E64E537B416 for ; Fri, 14 Dec 2001 09:26:03 -0800 (PST) Received: (from mike@localhost) by espresso.q9media.com (8.11.6/8.11.6) id fBEHOKH72356; Fri, 14 Dec 2001 12:24:20 -0500 (EST) (envelope-from mike) Date: Fri, 14 Dec 2001 12:24:19 -0500 From: Mike Barcroft To: Rafter Man Cc: freebsd-hackers@FreeBSD.org Subject: Re: New feutures........... Message-ID: <20011214122419.B68310@espresso.q9media.com> References: <20011214150349.3305.qmail@linuxmail.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011214150349.3305.qmail@linuxmail.org>; from rafter@linuxmail.org on Fri, Dec 14, 2001 at 11:03:49PM +0800 Organization: The FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Rafter Man writes: > 2. I hope that in the furture the FreeBSD developers will rewrite the system in C++. I think you're alone on that one. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 9:29: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 6B77837B417 for ; Fri, 14 Dec 2001 09:29:01 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id C618E14C56; Fri, 14 Dec 2001 18:28:59 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Rafter Man" Cc: freebsd-hackers@FreeBSD.org Subject: Re: New feutures........... References: <20011214150349.3305.qmail@linuxmail.org> From: Dag-Erling Smorgrav Date: 14 Dec 2001 18:28:59 +0100 In-Reply-To: <20011214150349.3305.qmail@linuxmail.org> Message-ID: Lines: 9 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Rafter Man" writes: > 2. I hope that in the furture the FreeBSD developers will rewrite > the system in C++. You need to have your head examined. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 9:34:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id BAF0337B417 for ; Fri, 14 Dec 2001 09:34:17 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 3BEC181D03; Fri, 14 Dec 2001 11:34:12 -0600 (CST) Date: Fri, 14 Dec 2001 11:34:12 -0600 From: Alfred Perlstein To: GB Clark II Cc: hackers@FreeBSD.ORG Subject: Re: shared mem and locking it in core (Database usage) Message-ID: <20011214113412.K79896@elvis.mu.org> References: <01121315261800.27037@prime.vsservices.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01121315261800.27037@prime.vsservices.com>; from gclarkii@vsservices.com on Thu, Dec 13, 2001 at 03:26:18PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * GB Clark II [011214 06:28] wrote: > Hello, > > I'm running PostgreSQL and it uses SysV shared mem for alot of its functions. > > How can verify that the shared mem is wired and not pageable? > > sysctl settings: > kern.ipc.shmmax: 128004097 > kern.ipc.shmmin: 1 > kern.ipc.shmmni: 512 > kern.ipc.shmseg: 1024 > kern.ipc.shmall: 31251 > kern.ipc.shm_use_phys: 1 <- This wires the mem right? > > Yes postgres shows to be 119M via top, but is this mem wired? As long as you set the sysctl before starting postgresql, then yes. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 10:31: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 9D7DA37B405 for ; Fri, 14 Dec 2001 10:30:50 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fBEIUei90063; Fri, 14 Dec 2001 13:30:40 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 14 Dec 2001 13:30:40 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Rafter Man Cc: freebsd-hackers@FreeBSD.org Subject: Re: New feutures........... In-Reply-To: <20011214150349.3305.qmail@linuxmail.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Can't address many of these, but will address one. On Fri, 14 Dec 2001, Rafter Man wrote: > Hi FreeBSD lovers :-) > > First af all I would like to thank the FreeBSD developers for making > such a great system! Half a year ago, I had to choose an OS for my > server and the first decision was between Windows and Unix, ofcourse it > didn't take much research to determine that Unix were the better choice. > But now I had to choose from Linux, Solaris and one of the BSD's, and > one of the BSD's is was. After a little reseach I had nerroed it down to > OpenBSD and FreeBSD, and FreeBSD won me over :-) But enough of this, on > to the 2 requests: 1. Is there a way to hide a user from other users? > Fx programs like w, who, users, netstat, top, ps all show what other > users are doing. It would fx be a good idea to hide root or the admin's > activities from other users. If you are trying to catch a cracker, then > you know that he/she if not stupid enough to login while other users > (especial root) are online. But perhaps this feuture to hide a user > already exists? -STABLE has this facility to a limited degree: you can use jail, or via the sysctl kern.ps_showallprocs. -CURRENT has a much more complete solution here, due to some re-architecting of the way credentials are handled, and has a series of kernel security policy tweaks, including a related kern.security.bsd.see_other_uids sysctl, which also affects the ability to see sockets in netstat, etc. FreeBSD 5.0, depending on the release schedule and how much work we get done, will have some amount of support for several mandatory access control models. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 10:58:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail12.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id 163FB37B423 for ; Fri, 14 Dec 2001 10:58:16 -0800 (PST) Received: (qmail 326 invoked from network); 14 Dec 2001 18:58:15 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Dec 2001 18:58:15 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15d.5ca814f.294b71ff@aol.com> Date: Fri, 14 Dec 2001 10:58:06 -0800 (PST) From: John Baldwin To: CB1001@aol.com Subject: Re: (no subject) Cc: isp@freebsd.org, hackers@freebsd.org, hueber@riic.at Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 14-Dec-01 CB1001@aol.com wrote: > In a message dated 12/14/01 10:09:20 AM Eastern Standard Time, CB1001 writes: > >> Hi, >> >> You claim the 3Coms are no good choice for FBSD. I have always been very >> satisfied >> with 3Com905B devices. >> And a quick search did not reveal any major problems with the 3com cards. > > A "quick search" of what? Get some perspective. The "hackers" are only > interested in cards that they use, and they all use intel for high end stuff. > Bill paul is too busy writing drivers for some new gigabit card to worry > about old stuff. (note that most of his drivers are optimised for the Alpha > and not i386...like what pct of people are using Alpha?) And there is > apparantly no interest in fixing anything or finding out whats wrong because > some guy at freebsd with a 2 inch weener keeps knocking me off the > list...they dont like criticism. I've already fixed it, so all im trying to > do is save you a lot of time doing work thats already been done. Actually, the cards are very much optimized for the i386. See the lack of using bus_dma for example, which is required for these cards to work on things like sparc64. Grow up and realize that not all the world is an i386. Ports like sparc64, powerpc, ia64, and x86-64 are being added and they are not exactly like the i386. I've used 3com cards (xl(4)) without any problems. They are rather nice cards and Bill Paul prefers those to Intel cards since Intel is so nazi with its docco. :) To Guret: Please don't listen to Dennis. He is feeding you lies so that you will go buy his "better" ethernet drivers. He is very obnoxious and thus has been banned from the lists several times. This is just another one of his silly aliases. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 11: 3:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 33C7A37B405 for ; Fri, 14 Dec 2001 11:03:48 -0800 (PST) Received: from rac4.wam.umd.edu (IDENT:root@rac4.wam.umd.edu [128.8.10.144]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA00902; Fri, 14 Dec 2001 14:03:40 -0500 (EST) Received: from rac4.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id OAA08137; Fri, 14 Dec 2001 14:03:40 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA08133; Fri, 14 Dec 2001 14:03:40 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Fri, 14 Dec 2001 14:03:40 -0500 (EST) From: Kenneth Wayne Culver To: Rafter Man Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: New feutures........... In-Reply-To: <20011214150349.3305.qmail@linuxmail.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > First af all I would like to thank the FreeBSD developers for making > such a great system! Half a year ago, I had to choose an OS for my > server and the first decision was between Windows and Unix, ofcourse > it didn't take much research to determine that Unix were the better > choice. But now I had to choose from Linux, Solaris and one of the > BSD's, and one of the BSD's is was. After a little reseach I had > nerroed it down to OpenBSD and FreeBSD, and FreeBSD won me over :-) > But enough of this, on to the 2 requests: 1. Is there a way to hide a > user from other users? Fx programs like w, who, users, netstat, top, > ps all show what other users are doing. It would fx be a good idea to > hide root or the admin's activities from other users. If you are > trying to catch a cracker, then you know that he/she if not stupid > enough to login while other users (especial root) are online. But > perhaps this feuture to hide a user already exists? > > 2. After having read "Operating systems - Internals and Design > Principles" by William Stallings I have a few questions. He writes, > among other things, about VM, process and tread design, and compares > Unix SVR4, Solaris and Windows NT. Sometimes he more or less say, that > what fx Solaris have done is the way of the future and other times the > unix way was the bedst. I don't want to discuss why FreeBSD have > designed the kernel as they have, but I know that sometimes when you > work very closely with something, you forget to "look up". I mean, > does FreeBSD analyse the Linux and Solaris kernel, maybe adobt some of > the good thing they have made? I don't expect FreeBSD to rewrite the > kernel, but to learn from Solaris and Linux. If FreeBSD allready do > this, then I am sorry for having troubled you with this mail!!! I think you misunderstood somewhere along the lines. FreeBSD is just as good as solaris and linux in most things, and better in others. > > Best regards > Rafter > > ps: 1. I hope that in the future FreeBSD will remain a servers only > OS. Meaning that I hope the developers don't spend to much time making > games, grafical programs and stuff like gnome/kde/x11. I hope the opposite. I use FreeBSD all day every day as my desktop system, and I'd die if I didn't have the things that you mention above as hoping that they never happen. > 2. I hope that in the furture the FreeBSD developers will rewrite the > system in C++. This will most likely NEVER happen. One of the reasons FreeBSD and UNIX in general are so fast is because they don't have to deal with the overhead of C++. C is smaller and faster. > 3. I hope for even more focuse on security. As far as I know there is a whole project focusing on FreeBSD's security. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 11:25: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id B704437B41B for ; Fri, 14 Dec 2001 11:24:49 -0800 (PST) Received: from winston.freebsd.org (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id fBEJNuq66132; Fri, 14 Dec 2001 11:24:12 -0800 (PST) (envelope-from jkh@winston.freebsd.org) To: "Rafter Man" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: New feutures........... In-Reply-To: Message from "Rafter Man" of "Fri, 14 Dec 2001 23:03:49 +0800." <20011214150349.3305.qmail@linuxmail.org> Date: Fri, 14 Dec 2001 11:23:56 -0800 Message-ID: <66128.1008357836@winston.freebsd.org> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > 1. Is there a way to hide a user from other users? Fx programs like w, who, u As Terry has already pointed out, jails are probably your best bet. > ps: 1. I hope that in the future FreeBSD will remain a servers only OS. As Terry also said, volunteers work on things they like to work on, but that said it's probably also a safe bet that those who really wanted to work on desktop operating systems are already doing that outside of FreeBSD. "Inside" of FreeBSD, people tend to focus on what customers are expressing a need for and most of our customers are server folks. Draw your own conclusions. :) > 2. I hope that in the furture the FreeBSD developers will rewrite the system in C++. God, I certainly hope NOT. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 13:20:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 61E3437B422; Fri, 14 Dec 2001 13:19:38 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fBELJbi92679; Fri, 14 Dec 2001 16:19:37 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 14 Dec 2001 16:19:36 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: developers@FreeBSD.org, hackers@FreeBSD.org Subject: FINAL REMINDER: Request for submissions: FreeBSD Monthly Development Status Report (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Reports are due tonight to be included in the November, 2001 monthly development report. The turnout is pretty low so far -- given activity in the tree, I know a lot more has been happening. :-) For example, I'd really like to get a report on the SMPng work, and hardware driver work, etc. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services ---------- Forwarded message ---------- Date: Thu, 13 Dec 2001 14:03:01 -0500 (EST) From: Robert Watson To: developers@FreeBSD.org, hackers@FreeBSD.org Subject: REMINDER: Request for submissions: FreeBSD Monthly Development Status Report Reminder: the deadline is tomorrow. I've received only about 8 reports so far, and would appreciate receiving more :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services ---------- Forwarded message ---------- Date: Sun, 9 Dec 2001 22:07:26 -0500 (EST) From: Robert Watson To: developers@FreeBSD.org, hackers@FreeBSD.org Subject: Request for submissions: FreeBSD Monthly Development Status Report Well, it's been a bit, but here it is again. This is a request for submissions for the November, 2001 FreeBSD Monthly Development Status Report. All submissions are due by Friday, December 14, 2001. Submissions should made by filling out the following template: http://www.FreeBSD.org/news/status/report-sample.xml Which will allow reports to be automatically processed, reducing the lag involved in generating the overall report :-). A reasonable attempt should be made to prevent duplicate submissions for the same project; however, if it's a large project, seperate submissions may be made for components, as well as a submission sumarizing overall progress on the project. Developers working on multiple projects should feel free to submit entries for each project individually. Submissions are welcome on a variety of topics relating to FreeBSD -- not least, development, but also documentation, advocacy, and processes relating to the development process, such as release engineering, QA, and security updates. All submissions *MUST* be e-mailed to the following address: robert+freebsd.monthly@cyrus.watson.org Submissions made to other e-mail addresses will not be included in the report. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 14:31:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-m10.mx.aol.com (imo-m10.mx.aol.com [64.12.136.165]) by hub.freebsd.org (Postfix) with ESMTP id 6321837B405; Fri, 14 Dec 2001 14:31:27 -0800 (PST) Received: from HP889@aol.com by imo-m10.mx.aol.com (mail_out_v31_r1.9.) id n.176.cf4901 (4411); Fri, 14 Dec 2001 17:31:24 -0500 (EST) From: HP889@aol.com Message-ID: <176.cf4901.294bd7bc@aol.com> Date: Fri, 14 Dec 2001 17:31:24 EST Subject: RE: 3Com driver problems To: hackers@freebsd.org Cc: isp@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> with 3Com905B devices. >> And a quick search did not reveal any major problems with the 3com cards. > > A "quick search" of what? Get some perspective. The "hackers" are only > interested in cards that they use, and they all use intel for high end stuff. > Bill paul is too busy writing drivers for some new gigabit card to worry > about old stuff. (note that most of his drivers are optimised for the Alpha > and not i386...like what pct of people are using Alpha?) And there is > apparantly no interest in fixing anything or finding out whats wrong because > some guy at freebsd with a 2 inch weener keeps knocking me off the > list...they dont like criticism. I've already fixed it, so all im trying to > do is save you a lot of time doing work thats already been done. >Actually, the cards are very much optimized for the i386. See the lack of >using bus_dma for example, which is required for these cards to work on things >ike sparc64. Grow up and realize that not all the world is an i386. Ports >like sparc64, powerpc, ia64, and x86-64 are being added and they are not >exactly like the i386. I've used 3com cards (xl(4)) without any problems. >They are rather nice cards and Bill Paul prefers those to Intel cards since >Intel is so nazi with its docco. :) >To Guret: >Please don't listen to Dennis. He is feeding you lies so that you will go buy? >his "better" ethernet drivers. He is very obnoxious and thus has been banned >from the lists several times. This is just another one of his silly aliases. We dont sell ethernet drivers, and Im not trying to "hide". Why does linux have specific code to disable the stats under load if Im making this up? Why can you lock up a FreeBSD 4.4 system with a 3com card at 20Kpps due to counter overflow interrupts in about 3 seconds? Its too bad that pointing out bugs is deemed as being obnoxious. Maybe its why they were complaining that linux outperforms Freebsd last week? Guret, I apologize for trying to help. Im sure these fellows at freebsd.org will work painstakingly to help you find your problem. But since they are in denial about there being anything wrong with it, you most likely are sunk. Try to front end your machine with a switch...the 5 cards is most likely your problem. With each device you increase your bus contention (ie worsen the worst case bus master scenario)...either that or get a 4 port card that is more efficient than 5 individual cards. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 15:35:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 9029B37B417; Fri, 14 Dec 2001 15:35:23 -0800 (PST) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id CAA27872; Sat, 15 Dec 2001 02:41:47 +0300 (MSK) Message-Id: <200112142341.CAA27872@aaz.links.ru> Subject: Re: 3Com driver problems In-Reply-To: <176.cf4901.294bd7bc@aol.com> from "HP889@aol.com" at "Dec 14, 1 05:31:24 pm" To: HP889@aol.com Date: Sat, 15 Dec 2001 02:41:47 +0300 (MSK) Cc: hackers@FreeBSD.ORG, isp@FreeBSD.ORG From: "."@babolo.ru MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG HP889@aol.com writes: > Try to front end your machine with a switch...the 5 cards is most likely your > problem. With each device you increase your bus contention (ie worsen the > worst case bus master scenario)...either that or get a 4 port card that is > more efficient than 5 individual cards. I have some opposite expierence. This is my biggest router: 0gw~(1)>uname -a FreeBSD gw.pike 4.4-STABLE FreeBSD 4.4-STABLE #0: Wed Sep 19 06:29:38 MSD 2001 babolo@shikster.pike.ru:/tmp/babolo/usr/src/sys/gw i386 0gw~(2)>ifconfig -a dc0: flags=8843 mtu 1500 dc1: flags=8802 mtu 1500 dc2: flags=8843 mtu 1500 dc3: flags=8843 mtu 1500 xl0: flags=8843 mtu 1500 xl1: flags=8843 mtu 1500 xl2: flags=8843 mtu 1500 6 used 100 M ethernet interfaces among others. dc0..dc3 is one card. xl0 cards are workaround for the fact that processor spent MUCH more time in interrupt state with dc driver than with xl driver with the same load. Yes, I try find xl x 4 card but no success -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 15:47:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 85F9837B41B; Fri, 14 Dec 2001 15:47:09 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011214234709.ENKA403.rwcrmhc52.attbi.com@peter3.wemm.org>; Fri, 14 Dec 2001 23:47:09 +0000 Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id fBENl9s53799; Fri, 14 Dec 2001 15:47:09 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id E9FB33808; Fri, 14 Dec 2001 15:47:08 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: Re: 3Com driver problems In-Reply-To: <176.cf4901.294bd7bc@aol.com> Date: Fri, 14 Dec 2001 15:47:08 -0800 From: Peter Wemm Message-Id: <20011214234708.E9FB33808@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FYI, this is another dennis@etinc.com clone. HP889@aol.com wrote: > >> with 3Com905B devices. > >> And a quick search did not reveal any major problems with the 3com cards. > > > > A "quick search" of what? Get some perspective. The "hackers" are only > > interested in cards that they use, and they all use intel for high end > stuff. > > Bill paul is too busy writing drivers for some new gigabit card to worry > > about old stuff. (note that most of his drivers are optimised for the Alpha > > and not i386...like what pct of people are using Alpha?) And there is > > apparantly no interest in fixing anything or finding out whats wrong > because > > some guy at freebsd with a 2 inch weener keeps knocking me off the > > list...they dont like criticism. I've already fixed it, so all im trying to > > do is save you a lot of time doing work thats already been done. > > >Actually, the cards are very much optimized for the i386. See the lack of > >using bus_dma for example, which is required for these cards to work on > things > >ike sparc64. Grow up and realize that not all the world is an i386. Ports > >like sparc64, powerpc, ia64, and x86-64 are being added and they are not > >exactly like the i386. I've used 3com cards (xl(4)) without any problems. > > >They are rather nice cards and Bill Paul prefers those to Intel cards since > >Intel is so nazi with its docco. :) > > >To Guret: > > >Please don't listen to Dennis. He is feeding you lies so that you will go > buy? > >his "better" ethernet drivers. He is very obnoxious and thus has been banne d > >from the lists several times. This is just another one of his silly aliases . > > We dont sell ethernet drivers, and Im not trying to "hide". Why does linux > have specific code to disable the stats under load if Im making this up? Why > can you lock up a FreeBSD 4.4 system with a 3com card at 20Kpps due to > counter overflow interrupts in about 3 seconds? > > Its too bad that pointing out bugs is deemed as being obnoxious. Maybe its > why they were complaining that linux outperforms Freebsd last week? > > Guret, I apologize for trying to help. Im sure these fellows at freebsd.org > will work painstakingly to help you find your problem. But since they are in > denial about there being anything wrong with it, you most likely are sunk. > > Try to front end your machine with a switch...the 5 cards is most likely your > problem. With each device you increase your bus contention (ie worsen the > worst case bus master scenario)...either that or get a 4 port card that is > more efficient than 5 individual cards. > > DB > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 15:48: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 5F18337B417; Fri, 14 Dec 2001 15:48:00 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011214234800.DLSW5010.rwcrmhc51.attbi.com@peter3.wemm.org>; Fri, 14 Dec 2001 23:48:00 +0000 Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id fBENlxs53808; Fri, 14 Dec 2001 15:47:59 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id CB6E83808; Fri, 14 Dec 2001 15:47:59 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: Re: 3com card problems In-Reply-To: <6d.1f1ac6d0.294b6fa9@aol.com> Date: Fri, 14 Dec 2001 15:47:59 -0800 From: Peter Wemm Message-Id: <20011214234759.CB6E83808@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FYI: This is another dennis@etinc.com clone. CB1001@aol.com wrote: > Hi, > > You claim the 3Coms are no good choice for FBSD. I have always been very > satisfied > with 3Com905B devices. > And a quick search did not reveal any major problems with the 3com cards. > > Pls, can you explain the problem in more detail or direct me to more detailed > information (how to avoid impacts with STATS ...) > > Thank you > > Gernot Hueber > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 15:54:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id 6D36037B405 for ; Fri, 14 Dec 2001 15:54:44 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id A9251786E4; Sat, 15 Dec 2001 10:24:42 +1030 (CST) Date: Sat, 15 Dec 2001 10:24:42 +1030 From: Greg Lehey To: Terry Lambert Cc: Peter Jeremy , freebsd-hackers@freebsd.org Subject: Re: Adding a new FS to FreeBSD Message-ID: <20011215102442.E85108@monorchid.lemis.com> References: <20011214141518.E73243@gsmx07.alcatel.com.au> <3C1A09BB.DEBCB854@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C1A09BB.DEBCB854@mindspring.com> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Friday, 14 December 2001 at 6:16:27 -0800, Terry Lambert wrote: > Peter Jeremy wrote: >> Since JFS has come up again... Are there any papers that explain how >> to integrate a new filesystem into FreeBSD? The relevant chapter in >> the FreeBSD Developers' Handbook (16) is a bit terse :-). >> >> Specifically, I'm looking at being able to read/write 2BSD filesystems >> on my FreeBSD machines. > > Do you have small images of this FS, as well as header files that > are redistributable (e.g. BSD license) and/or code? > > If you have the tools sources (e.g. "newfs", "fsck", etc.), this would > be useful, as well, since I could vnconfig a device and recreate an > empty FS image with native tools (self hosted), as well. I've got everything here, but it sounds like Jeremy does too. Depending on the value of 2, this is either the old 6th edition file system or an early variant of UFS; either's not difficult. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 18: 4:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tungsten.btinternet.com (tungsten.btinternet.com [194.73.73.81]) by hub.freebsd.org (Postfix) with ESMTP id CE88737B419 for ; Fri, 14 Dec 2001 18:04:23 -0800 (PST) Received: from host213-123-132-114.in-addr.btopenworld.com ([213.123.132.114] helo=there) by rhenium with smtp (Exim 3.22 #8) id 16EvwT-0004om-00; Fri, 14 Dec 2001 17:16:13 +0000 Content-Type: text/plain; charset="iso-8859-1" From: Dominic Marks To: "Rafter Man" , freebsd-hackers@FreeBSD.org Subject: Re: New feutures........... Date: Fri, 14 Dec 2001 17:16:23 +0000 X-Mailer: KMail [version 1.3.2] References: <20011214150349.3305.qmail@linuxmail.org> In-Reply-To: <20011214150349.3305.qmail@linuxmail.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Friday 14 December 2001 3:03 pm, Rafter Man wrote: > Hi FreeBSD lovers :-) > 1. Is there a way to hide a user from other users? Fx programs like > w, who, users, netstat, top, ps all show what other users are > doing. It would fx be a good idea to hide root or the admin's > activities from other users. If you are trying to catch a cracker, > then you know that he/she if not stupid enough to login while other > users (especial root) are online. But perhaps this feuture to hide > a user already exists? There is a sysctl you can switch to make users only able to see their own processes. It has a different name from -STABLE to -CURRENT. I don't remember what its name is exactly for -STABLE and I can't check right now, but if you search for 'ps' in the sysctl listing you should find it pretty easily. Also if you want to see what a user is doing on their terminal you can use the snoop device with the watch program. See `man watch' for that. > ps: 1. I hope that in the future FreeBSD will remain a servers only > OS. Meaning that I hope the developers don't spend to much time > making games, grafical programs and stuff like gnome/kde/x11. I don't think you have anything to fear in this respect. Considering X11 and KDE are cross platform projects already working on FreeBSD the real work here is maintaince which is done by the projects concerned and the ports team. > 2. I hope that in the furture the FreeBSD developers will rewrite > the system in C++. Whats that I see! Yes! A flying pig! :) > 3. I hope for even more focuse on security. > 4. I will do my part and help FreeBSD the bedst I can. -- Dominic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 21:34:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cu518.adelaide.adsl.on.net (cu518.adelaide.adsl.on.net [150.101.236.10]) by hub.freebsd.org (Postfix) with ESMTP id 5DFF537B419 for ; Fri, 14 Dec 2001 21:34:24 -0800 (PST) Received: from ns.aus.com (cu518.adsl.adelaide.on.net [127.0.0.1]) by cu518.adelaide.adsl.on.net (8.11.0/8.11.0) with ESMTP id fBF7gx703229 for ; Sat, 15 Dec 2001 18:13:00 +1030 Message-ID: <3C1AEA9E.6010502@ns.aus.com> Date: Sat, 15 Dec 2001 16:45:58 +1030 From: Richard Sharpe Reply-To: rsharpe@ns.aus.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010917 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Does anyone know if the Broadcom BCM5700 has problems with HW csum? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I am playing with a driver for the Broadcom 5700/5701. It recognizes the 5700 in my 3Com cards OK, but seems to screw up the TCP checksum. Switching off hardware checksum capability fixes it. Does anyone know the details of which stepping this stuff worked on? -- Richard Sharpe, rsharpe@ns.aus.com, LPIC-1 www.samba.org, www.ethereal.com, SAMS Teach Yourself Samba in 24 Hours, Special Edition, Using Samba To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 21:41:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 9475337B405 for ; Fri, 14 Dec 2001 21:41:20 -0800 (PST) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id fBF5fIL31660; Fri, 14 Dec 2001 21:41:18 -0800 Date: Fri, 14 Dec 2001 21:41:18 -0800 From: Brooks Davis To: rsharpe@ns.aus.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? Message-ID: <20011214214118.A30560@Odin.AC.HMC.Edu> References: <3C1AEA9E.6010502@ns.aus.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C1AEA9E.6010502@ns.aus.com>; from sharpe@ns.aus.com on Sat, Dec 15, 2001 at 04:45:58PM +1030 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 15, 2001 at 04:45:58PM +1030, Richard Sharpe wrote: > Hi, >=20 > I am playing with a driver for the Broadcom 5700/5701. >=20 > It recognizes the 5700 in my 3Com cards OK, but seems to screw up the=20 > TCP checksum. >=20 > Switching off hardware checksum capability fixes it. >=20 > Does anyone know the details of which stepping this stuff worked on? There was a commit to current a few hours ago disabling hardware checksums on recieve due to corruption problems. It will be MFC'd in three days though it's a two line fix so you could apply it your self: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=3D1.= 4&r2=3D1.5 -- 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 --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8GuJ9XY6L6fI4GtQRArxVAKCb+d0vWm8EdVaaD7p1Rsz2KbsgBACeMkqW AfKiz5GAwBp6mzvu5w8WWlo= =/tmN -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 14 22:53:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 7DD0537B405 for ; Fri, 14 Dec 2001 22:53:21 -0800 (PST) Received: from pool0205.cvx21-bradley.dialup.earthlink.net ([209.179.192.205] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16F8hC-0001aQ-00; Fri, 14 Dec 2001 22:53:19 -0800 Message-ID: <3C1AF362.534BD2F7@mindspring.com> Date: Fri, 14 Dec 2001 22:53:22 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Brooks Davis Cc: rsharpe@ns.aus.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? References: <3C1AEA9E.6010502@ns.aus.com> <20011214214118.A30560@Odin.AC.HMC.Edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Brooks Davis wrote: > There was a commit to current a few hours ago disabling hardware > checksums on recieve due to corruption problems. It will be MFC'd in > three days though it's a two line fix so you could apply it your self: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.4&r2=1.5 I believe you will find that the problem is related to the firmware handling of VLAN tagging, and that the problem only exists if VLAN tagging is enabled. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 0:39:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id AE11D37B416; Sat, 15 Dec 2001 00:39:31 -0800 (PST) Received: from pool0029.cvx22-bradley.dialup.earthlink.net ([209.179.198.29] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16FALy-0003lE-00; Sat, 15 Dec 2001 00:39:30 -0800 Message-ID: <3C1B0C44.E5A108A4@mindspring.com> Date: Sat, 15 Dec 2001 00:39:32 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: Peter Jeremy , freebsd-hackers@freebsd.org Subject: Re: Adding a new FS to FreeBSD References: <20011214141518.E73243@gsmx07.alcatel.com.au> <3C1A09BB.DEBCB854@mindspring.com> <20011215102442.E85108@monorchid.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greg Lehey wrote: > > Do you have small images of this FS, as well as header files that > > are redistributable (e.g. BSD license) and/or code? > > > > If you have the tools sources (e.g. "newfs", "fsck", etc.), this would > > be useful, as well, since I could vnconfig a device and recreate an > > empty FS image with native tools (self hosted), as well. > > I've got everything here, but it sounds like Jeremy does too. > Depending on the value of 2, this is either the old 6th edition file > system or an early variant of UFS; either's not difficult. If anyone wants to put this stuff up on a web site so I can grab it before I go on vacation next week, I can work on it over the break, since I will probably be going stir-crazy anyway, jonesing for some code to write... This works for either the 2BSD or the S51K stuff (or Acer FFS, if that is what was being referred to in the SCO case). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 1: 2:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id 000EF37B405 for ; Sat, 15 Dec 2001 01:02:32 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id 33C31786E3; Sat, 15 Dec 2001 19:32:26 +1030 (CST) Date: Sat, 15 Dec 2001 19:32:26 +1030 From: Greg Lehey To: Terry Lambert Cc: Peter Jeremy , freebsd-hackers@freebsd.org Subject: Re: Adding a new FS to FreeBSD Message-ID: <20011215193226.J87600@monorchid.lemis.com> References: <20011214141518.E73243@gsmx07.alcatel.com.au> <3C1A09BB.DEBCB854@mindspring.com> <20011215102442.E85108@monorchid.lemis.com> <3C1B0C44.E5A108A4@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C1B0C44.E5A108A4@mindspring.com> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Saturday, 15 December 2001 at 0:39:32 -0800, Terry Lambert wrote: > Greg Lehey wrote: >>> Do you have small images of this FS, as well as header files that >>> are redistributable (e.g. BSD license) and/or code? >>> >>> If you have the tools sources (e.g. "newfs", "fsck", etc.), this would >>> be useful, as well, since I could vnconfig a device and recreate an >>> empty FS image with native tools (self hosted), as well. >> >> I've got everything here, but it sounds like Jeremy does too. >> Depending on the value of 2, this is either the old 6th edition file >> system or an early variant of UFS; either's not difficult. > > If anyone wants to put this stuff up on a web site so I can grab > it before I go on vacation next week, I can work on it over the > break, since I will probably be going stir-crazy anyway, jonesing > for some code to write... Unfortunately, it's still copyrighted. You need an SCO license; want to go and get one of them? It doesn't cost anything, but I can't give the software to anybody who hasn't agreed to the conditions. Get the license at http://shop.caldera.com/caldera/ancient.html (yup, that's what SCO has become). Note that the link to PUPS in the follow-on page (http://www2.caldera.com/offers/ancient001/) is broken: it's now http://minnie.tuhs.org/PUPS/ Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 1: 8:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from root.com (unknown [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 97EF837B416 for ; Sat, 15 Dec 2001 01:08:20 -0800 (PST) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id fBF8vdk84884; Sat, 15 Dec 2001 00:57:39 -0800 (PST) (envelope-from dg) Date: Sat, 15 Dec 2001 00:57:39 -0800 From: David Greenman To: Terry Lambert Cc: Brooks Davis , rsharpe@ns.aus.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? Message-ID: <20011215005739.A84861@nexus.root.com> References: <3C1AEA9E.6010502@ns.aus.com> <20011214214118.A30560@Odin.AC.HMC.Edu> <3C1AF362.534BD2F7@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C1AF362.534BD2F7@mindspring.com>; from tlambert2@mindspring.com on Fri, Dec 14, 2001 at 10:53:22PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Brooks Davis wrote: >> There was a commit to current a few hours ago disabling hardware >> checksums on recieve due to corruption problems. It will be MFC'd in >> three days though it's a two line fix so you could apply it your self: >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.4&r2=1.5 > >I believe you will find that the problem is related to the firmware >handling of VLAN tagging, and that the problem only exists if VLAN >tagging is enabled. You would believe wrongly, then, because the problem that I was seeing did not involve VLAN tags. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 1:13: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 3165B37B417 for ; Sat, 15 Dec 2001 01:13:05 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id BB6B981D03; Sat, 15 Dec 2001 03:13:04 -0600 (CST) Date: Sat, 15 Dec 2001 03:13:04 -0600 From: Alfred Perlstein To: David Greenman Cc: Terry Lambert , Brooks Davis , rsharpe@ns.aus.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? Message-ID: <20011215031304.N79896@elvis.mu.org> References: <3C1AEA9E.6010502@ns.aus.com> <20011214214118.A30560@Odin.AC.HMC.Edu> <3C1AF362.534BD2F7@mindspring.com> <20011215005739.A84861@nexus.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011215005739.A84861@nexus.root.com>; from dg@root.com on Sat, Dec 15, 2001 at 12:57:39AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * David Greenman [011215 03:12] wrote: > >Brooks Davis wrote: > >> There was a commit to current a few hours ago disabling hardware > >> checksums on recieve due to corruption problems. It will be MFC'd in > >> three days though it's a two line fix so you could apply it your self: > >> > >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.4&r2=1.5 > > > >I believe you will find that the problem is related to the firmware > >handling of VLAN tagging, and that the problem only exists if VLAN > >tagging is enabled. > > You would believe wrongly, then, because the problem that I was seeing did > not involve VLAN tags. You're probably incorrect, it doesn't matter if vlan tags are active or not, it's most likely wheather or not the firmware is being asked to handle them at all. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 1:14:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from root.com (unknown [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id E522B37B417 for ; Sat, 15 Dec 2001 01:14:24 -0800 (PST) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id fBF94vp84911; Sat, 15 Dec 2001 01:04:57 -0800 (PST) (envelope-from dg) Date: Sat, 15 Dec 2001 01:04:57 -0800 From: David Greenman To: rsharpe@ns.aus.com Cc: freebsd-hackers@freebsd.org Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? Message-ID: <20011215010457.B84861@nexus.root.com> References: <3C1AEA9E.6010502@ns.aus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C1AEA9E.6010502@ns.aus.com>; from sharpe@ns.aus.com on Sat, Dec 15, 2001 at 04:45:58PM +1030 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >I am playing with a driver for the Broadcom 5700/5701. > >It recognizes the 5700 in my 3Com cards OK, but seems to screw up the >TCP checksum. > >Switching off hardware checksum capability fixes it. > >Does anyone know the details of which stepping this stuff worked on? I haven't nailed down the problem that I've seen with them to a specific chipset, but I can confirm that they incorrectly calculate the checksum on input packets in some cases. It seems to be related to both packet size and certain TCP options (or lack of them). I've only seen the problem occur with very small (0-4 byte payload) packets. In any case, after discussing this problem with Bill Paul, I disabled input checksum in the -current driver and intend to merge that to -stable in a few days. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 1:22:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from root.com (unknown [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 1474637B416 for ; Sat, 15 Dec 2001 01:22:52 -0800 (PST) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id fBF9Ajf84927; Sat, 15 Dec 2001 01:10:45 -0800 (PST) (envelope-from dg) Date: Sat, 15 Dec 2001 01:10:45 -0800 From: David Greenman To: Alfred Perlstein Cc: Terry Lambert , Brooks Davis , rsharpe@ns.aus.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? Message-ID: <20011215011045.C84861@nexus.root.com> References: <3C1AEA9E.6010502@ns.aus.com> <20011214214118.A30560@Odin.AC.HMC.Edu> <3C1AF362.534BD2F7@mindspring.com> <20011215005739.A84861@nexus.root.com> <20011215031304.N79896@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011215031304.N79896@elvis.mu.org>; from bright@mu.org on Sat, Dec 15, 2001 at 03:13:04AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >* David Greenman [011215 03:12] wrote: >> >Brooks Davis wrote: >> >> There was a commit to current a few hours ago disabling hardware >> >> checksums on recieve due to corruption problems. It will be MFC'd in >> >> three days though it's a two line fix so you could apply it your self: >> >> >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.4&r2=1.5 >> > >> >I believe you will find that the problem is related to the firmware >> >handling of VLAN tagging, and that the problem only exists if VLAN >> >tagging is enabled. >> >> You would believe wrongly, then, because the problem that I was seeing did >> not involve VLAN tags. > >You're probably incorrect, it doesn't matter if vlan tags are active >or not, it's most likely wheather or not the firmware is being asked >to handle them at all. I would think it would get the checksum wrong most of the time if that were the case. It seems to only have problems with small packets, but the behavior is pretty strange, so who knows. Do you have some specific knowledge about Broadcom and brokeness related to VLAN tag support when not using VLANs? -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 1:24:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web21110.mail.yahoo.com (web21110.mail.yahoo.com [216.136.227.112]) by hub.freebsd.org (Postfix) with SMTP id 841CA37B419 for ; Sat, 15 Dec 2001 01:24:04 -0800 (PST) Message-ID: <20011215092344.54636.qmail@web21110.mail.yahoo.com> Received: from [80.4.35.237] by web21110.mail.yahoo.com via HTTP; Sat, 15 Dec 2001 01:23:44 PST Date: Sat, 15 Dec 2001 01:23:44 -0800 (PST) From: Hiten Pandya Subject: boot0 To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, I found this piece of code in boot0.s, is it possible if you could explain me a bit about it. .set NHRDRV,0x475 # Number of hard drives The hex value comes out to: 1141. Does that mean, that this is the amound of maximum hard drives a user can have on FreeBSD? If that is so, is there a way to boost that value a bit higher, or am I just getting the whole point wrong? Thanks, =Hiten = __________________________________________________ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 2:59:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id F23F637B405 for ; Sat, 15 Dec 2001 02:59:42 -0800 (PST) Received: from pool0048.cvx22-bradley.dialup.earthlink.net ([209.179.198.48] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16FCXa-0006g3-00; Sat, 15 Dec 2001 02:59:39 -0800 Message-ID: <3C1B2D1C.2A148A9C@mindspring.com> Date: Sat, 15 Dec 2001 02:59:40 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: David Greenman Cc: Brooks Davis , rsharpe@ns.aus.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? References: <3C1AEA9E.6010502@ns.aus.com> <20011214214118.A30560@Odin.AC.HMC.Edu> <3C1AF362.534BD2F7@mindspring.com> <20011215005739.A84861@nexus.root.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Greenman wrote: > >I believe you will find that the problem is related to the firmware > >handling of VLAN tagging, and that the problem only exists if VLAN > >tagging is enabled. > > You would believe wrongly, then, because the problem that I was seeing did > not involve VLAN tags. OK; it was worth a shot, since Broadcom was known to get that part wrong (they blew it big time on the Tigon II firmware). Too bad; the checksum offload is usually really helpful, if you can get arounf the quirks. 8^(. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 3:19:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id 6AA9737B426; Sat, 15 Dec 2001 03:18:33 -0800 (PST) Received: from pool0048.cvx22-bradley.dialup.earthlink.net ([209.179.198.48] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16FCpr-0005LQ-00; Sat, 15 Dec 2001 03:18:31 -0800 Message-ID: <3C1B3189.CD0B1D1A@mindspring.com> Date: Sat, 15 Dec 2001 03:18:33 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: Peter Jeremy , freebsd-hackers@freebsd.org Subject: Re: Adding a new FS to FreeBSD References: <20011214141518.E73243@gsmx07.alcatel.com.au> <3C1A09BB.DEBCB854@mindspring.com> <20011215102442.E85108@monorchid.lemis.com> <3C1B0C44.E5A108A4@mindspring.com> <20011215193226.J87600@monorchid.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greg Lehey wrote: > Unfortunately, it's still copyrighted. You need an SCO license; want > to go and get one of them? It doesn't cost anything, but I can't give > the software to anybody who hasn't agreed to the conditions. 8.4(b) says you can't give it to anyone, even if they do have the license, unless you contact Caldera first, and then maintain (in perpeturity) a list of the sources made available. I think we are screwed by section 2.1(d) anyway: Commercial use by LICENSEE of SOURCE CODE PRODUCTS or of any result, enhancement or modification associated with the use of SOURCE CODE PRODUCTS under this AGREEMENT is not permitted. Basically, I couldn't get an article out of it because I could't disclose it to anyone but a licensesee, and only a licensee could use the code, and I couldn't give source to the licensee without the permission of Caldera, and once they had the code, they could not use it for anything commercial unless they negotiated a seperate commercial use license. Frankly, if you want to provide small disk images (preferrably, very small, not multimegabyte) as I've described are needed anyway, along with a description of the what's on the images, along with such layout information as you feel comfortable providing, I'd pretty much rather reverse engineer the stuff than get a Caldera license. At least that way, I can get an article out of doing the thing. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 3:24:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id BCE9E37B417 for ; Sat, 15 Dec 2001 03:24:29 -0800 (PST) Received: from pool0048.cvx22-bradley.dialup.earthlink.net ([209.179.198.48] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16FCvZ-0007N7-00; Sat, 15 Dec 2001 03:24:26 -0800 Message-ID: <3C1B32EB.ACBA8DB@mindspring.com> Date: Sat, 15 Dec 2001 03:24:27 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: David Greenman Cc: Alfred Perlstein , Brooks Davis , rsharpe@ns.aus.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? References: <3C1AEA9E.6010502@ns.aus.com> <20011214214118.A30560@Odin.AC.HMC.Edu> <3C1AF362.534BD2F7@mindspring.com> <20011215005739.A84861@nexus.root.com> <20011215031304.N79896@elvis.mu.org> <20011215011045.C84861@nexus.root.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Greenman wrote: > Alfred Perlstein wrote: > >You're probably incorrect, it doesn't matter if vlan tags are active > >or not, it's most likely wheather or not the firmware is being asked > >to handle them at all. > > I would think it would get the checksum wrong most of the time if that > were the case. It seems to only have problems with small packets, but the > behavior is pretty strange, so who knows. Do you have some specific knowledge > about Broadcom and brokeness related to VLAN tag support when not using > VLANs? If it's very small payload, it's probably a byte-order-in-buffer issue (several Eagle manufactured cards had similar problems, and so did the NE1000, when it came to DMA transfers, back when 16 bit transfers were new 8^). For VLANs, yes, there are specific problems known with the Broadcom cards when the firmware support for VLANs is enabled. The first card known to work with checksum offload enable and VLAN support enabled (whether it's used or not) is the Tigon III. I don't know if Bill Paul fixed the firmware for the Tigon II in this case (he has been known to hack Tigon II firmware), but it could have been fixed by now. In any case, disabling it is what ClickArray ended up doing, as well, for the Tigon II, until the firmware could be fixed. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 3:34:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from siteintegrity.net (siteintegrity.net [216.155.19.9]) by hub.freebsd.org (Postfix) with ESMTP id 844CF37B416 for ; Sat, 15 Dec 2001 03:34:06 -0800 (PST) Received: from siteintegrity.net (localhost [127.0.0.1]) by siteintegrity.net (8.12.1/8.12.1) with ESMTP id fBFBY01Q074085 for ; Sat, 15 Dec 2001 06:34:05 -0500 (EST) Received: from localhost (mike@localhost) by siteintegrity.net (8.12.1/8.12.1/Submit) with ESMTP id fBFBY0gv074082 for ; Sat, 15 Dec 2001 06:34:00 -0500 (EST) Date: Sat, 15 Dec 2001 06:34:00 -0500 (EST) From: Mike Wiacek To: freebsd-hackers@freebsd.org Subject: sha1 program Message-ID: <20011215062918.F74051-400000@siteintegrity.net> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1941351035-1008416040=:74051" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1941351035-1008416040=:74051 Content-Type: TEXT/PLAIN; charset=US-ASCII We currently have a MD5 driver, but no SHA1 driver, even though we have SHA1 as part of libmd. So I took md5.c from /usr/src/sbin/md5 and made sha1.c as well as a respective man page. Attached is the source file, the manual page for it, as well as a makefile. Hope this is useful and makes its way into the tree. Md5 has some questionable attacks against it, and Schneier claims that sha is resillient to such attacks. mike --0-1941351035-1008416040=:74051 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="sha1.c" Content-Transfer-Encoding: BASE64 Content-ID: <20011215063400.H74051@siteintegrity.net> Content-Description: sha1 source file Content-Disposition: attachment; filename="sha1.c" LyoNCiAqIERlcml2ZWQgZnJvbToNCiAqDQogKiBNRERSSVZFUi5DIC0gdGVz dCBkcml2ZXIgZm9yIE1EMiwgTUQ0IGFuZCBNRDUNCiAqLw0KDQovKg0KICog RnVydGhlciBkZXJ2aWVkIGZyb20gdGhlIEZyZWVCU0QgbWQ1IGRyaXZlciBw cm9ncmFtLg0KICogQ29udmVydGVkIHRvIGdlbmVyYXRlIFNIQSAxNjAgYml0 IGhhc2hlcy4NCiAqIE1pa2UgV2lhY2VrIDxtaWtlQHNpdGVpbnRlZ3JpdHku bmV0PiAxMi8xNC8yMDAxDQogKi8NCg0KI2lmbmRlZiBsaW50DQpzdGF0aWMg Y29uc3QgY2hhciByY3NpZFtdID0NCiAgIiRGcmVlQlNEJCI7DQojZW5kaWYg Lyogbm90IGxpbnQgKi8NCg0KI2luY2x1ZGUgPHN5cy90eXBlcy5oPg0KI2lu Y2x1ZGUgPGVyci5oPg0KI2luY2x1ZGUgPHNoYS5oPg0KI2luY2x1ZGUgPHN0 ZGlvLmg+DQojaW5jbHVkZSA8c3RkbGliLmg+DQojaW5jbHVkZSA8c3RyaW5n Lmg+DQojaW5jbHVkZSA8dGltZS5oPg0KI2luY2x1ZGUgPHVuaXN0ZC5oPg0K DQovKg0KICogTGVuZ3RoIG9mIHRlc3QgYmxvY2ssIG51bWJlciBvZiB0ZXN0 IGJsb2Nrcy4NCiAqLw0KI2RlZmluZSBURVNUX0JMT0NLX0xFTiAxMDAwMA0K I2RlZmluZSBURVNUX0JMT0NLX0NPVU5UIDEwMDAwMA0KDQppbnQgcWZsYWc7 DQppbnQgcmZsYWc7DQoNCnN0YXRpYyB2b2lkIFNIQVN0cmluZyhjb25zdCBj aGFyICopOw0Kc3RhdGljIHZvaWQgU0hBVGltZVRyaWFsKHZvaWQpOw0Kc3Rh dGljIHZvaWQgU0hBVGVzdFN1aXRlKHZvaWQpOw0Kc3RhdGljIHZvaWQgU0hB RmlsdGVyKGludCk7DQpzdGF0aWMgdm9pZCB1c2FnZSh2b2lkKTsNCg0KLyog TWFpbiBkcml2ZXIuDQoNCkFyZ3VtZW50cyAobWF5IGJlIGFueSBjb21iaW5h dGlvbik6DQogIC1zc3RyaW5nIC0gZGlnZXN0cyBzdHJpbmcNCiAgLXQgICAg ICAgLSBydW5zIHRpbWUgdHJpYWwNCiAgLXggICAgICAgLSBydW5zIHRlc3Qg c2NyaXB0DQogIGZpbGVuYW1lIC0gZGlnZXN0cyBmaWxlDQogIChub25lKSAg IC0gZGlnZXN0cyBzdGFuZGFyZCBpbnB1dA0KICovDQoNCm1haW4oaW50IGFy Z2MsIGNoYXIgKmFyZ3ZbXSkNCnsNCglpbnQgICAgIGNoOw0KCWNoYXIgICAq cDsNCgl1bnNpZ25lZCBjaGFyCWJ1Zls0MV0gPSB7MH07DQoNCgl3aGlsZSAo KGNoID0gZ2V0b3B0KGFyZ2MsIGFyZ3YsICJwcXJzOnR4IikpICE9IC0xKQ0K CQlzd2l0Y2ggKGNoKSB7DQoJCWNhc2UgJ3AnOg0KCQkJU0hBRmlsdGVyKDEp Ow0KCQkJYnJlYWs7DQoJCWNhc2UgJ3EnOg0KCQkJcWZsYWcgPSAxOw0KCQkJ YnJlYWs7DQoJCWNhc2UgJ3InOg0KCQkJcmZsYWcgPSAxOw0KCQkJYnJlYWs7 DQoJCWNhc2UgJ3MnOg0KCQkJU0hBU3RyaW5nKG9wdGFyZyk7DQoJCQlicmVh azsNCgkJY2FzZSAndCc6DQoJCQlTSEFUaW1lVHJpYWwoKTsNCgkJCWJyZWFr Ow0KCQljYXNlICd4JzoNCgkJCVNIQVRlc3RTdWl0ZSgpOw0KCQkJYnJlYWs7 DQoJCWRlZmF1bHQ6DQoJCQl1c2FnZSgpOw0KCQl9DQoJYXJnYyAtPSBvcHRp bmQ7DQoJYXJndiArPSBvcHRpbmQ7DQoNCglpZiAoKmFyZ3YpIHsNCgkJZG8g ew0KCQkJcCA9IFNIQTFfRmlsZSgqYXJndiwgYnVmKTsNCgkJCWlmICghcCkN CgkJCQl3YXJuKCIlcyIsICphcmd2KTsNCgkJCWVsc2UNCgkJCQlpZiAocWZs YWcpDQoJCQkJCXByaW50ZigiJXNcbiIsIHApOw0KCQkJCWVsc2UgaWYgKHJm bGFnKQ0KCQkJCQlwcmludGYoIiVzICVzXG4iLCBwLCAqYXJndik7DQoJCQkJ ZWxzZQ0KCQkJCQlwcmludGYoIlNIQTEgKCVzKSA9ICVzXG4iLCAqYXJndiwg cCk7DQoJCX0gd2hpbGUgKCorK2FyZ3YpOw0KCX0gZWxzZSBpZiAob3B0aW5k ID09IDEgfHwgcWZsYWcgfHwgcmZsYWcpDQoJCVNIQUZpbHRlcigwKTsNCg0K CXJldHVybiAoMCk7DQp9DQovKg0KICogRGlnZXN0cyBhIHN0cmluZyBhbmQg cHJpbnRzIHRoZSByZXN1bHQuDQogKi8NCnN0YXRpYyB2b2lkDQpTSEFTdHJp bmcoY29uc3QgY2hhciAqc3RyaW5nKQ0Kew0KCXNpemVfdCBsZW4gPSBzdHJs ZW4oc3RyaW5nKTsNCgl1bnNpZ25lZCBjaGFyIGJ1Zls0MV0gPSB7MH07DQoN CglpZiAocWZsYWcpDQoJCXByaW50ZigiJXNcbiIsIFNIQTFfRGF0YShzdHJp bmcsIGxlbiwgYnVmKSk7DQoJZWxzZSBpZiAocmZsYWcpDQoJCXByaW50Zigi JXMgXCIlc1wiXG4iLCBTSEExX0RhdGEoc3RyaW5nLCBsZW4sIGJ1ZiksIHN0 cmluZyk7DQoJZWxzZQ0KCQlwcmludGYoIlNIQTEgKFwiJXNcIikgPSAlc1xu Iiwgc3RyaW5nLCBTSEExX0RhdGEoc3RyaW5nLCBsZW4sIGJ1ZikpOw0KfQ0K LyoNCiAqIE1lYXN1cmVzIHRoZSB0aW1lIHRvIGRpZ2VzdCBURVNUX0JMT0NL X0NPVU5UIFRFU1RfQkxPQ0tfTEVOLWJ5dGUgYmxvY2tzLg0KICovDQpzdGF0 aWMgdm9pZA0KU0hBVGltZVRyaWFsKHZvaWQpDQp7DQoJU0hBX0NUWCBjb250 ZXh0Ow0KCXRpbWVfdCAgZW5kVGltZSwgc3RhcnRUaW1lOw0KCXVuc2lnbmVk IGNoYXIgYmxvY2tbVEVTVF9CTE9DS19MRU5dOw0KCXVuc2lnbmVkIGludCBp Ow0KCWNoYXIgICAqcDsNCgl1bnNpZ25lZCBjaGFyIGJ1Zls0MV0gPSB7MH07 DQoNCg0KCXByaW50Zg0KCSAgICAoIlNIQTEgdGltZSB0cmlhbC4gRGlnZXN0 aW5nICVkICVkLWJ5dGUgYmxvY2tzIC4uLiIsDQoJICAgIFRFU1RfQkxPQ0tf Q09VTlQsIFRFU1RfQkxPQ0tfTEVOKTsNCglmZmx1c2goc3Rkb3V0KTsNCg0K CS8qIEluaXRpYWxpemUgYmxvY2sgKi8NCglmb3IgKGkgPSAwOyBpIDwgVEVT VF9CTE9DS19MRU47IGkrKykNCgkJYmxvY2tbaV0gPSAodW5zaWduZWQgY2hh cikgKGkgJiAweGZmKTsNCg0KCS8qIFN0YXJ0IHRpbWVyICovDQoJdGltZSgm c3RhcnRUaW1lKTsNCg0KCS8qIERpZ2VzdCBibG9ja3MgKi8NCglTSEFfSW5p dCgmY29udGV4dCk7DQoJZm9yIChpID0gMDsgaSA8IFRFU1RfQkxPQ0tfQ09V TlQ7IGkrKykNCgkJU0hBX1VwZGF0ZSgmY29udGV4dCwgYmxvY2ssIFRFU1Rf QkxPQ0tfTEVOKTsNCglwID0gU0hBMV9FbmQoJmNvbnRleHQsYnVmKTsNCg0K CS8qIFN0b3AgdGltZXIgKi8NCgl0aW1lKCZlbmRUaW1lKTsNCg0KCXByaW50 ZigiIGRvbmVcbiIpOw0KCXByaW50ZigiRGlnZXN0ID0gJXMiLCBwKTsNCglw cmludGYoIlxuVGltZSA9ICVsZCBzZWNvbmRzXG4iLCAobG9uZykgKGVuZFRp bWUgLSBzdGFydFRpbWUpKTsNCgkvKiBCZSBjYXJlZnVsIHRoYXQgZW5kVGlt ZS1zdGFydFRpbWUgaXMgbm90IHplcm8uIChCdWcgZml4IGZyb20gUmljDQoJ ICogQW5kZXJzb24sIHJpY0BBcnRpc29mdC5DT00uKSAqLw0KCXByaW50Zg0K CSAgICAoIlNwZWVkID0gJWxkIGJ5dGVzL3NlY29uZFxuIiwNCgkgICAgKGxv bmcpIFRFU1RfQkxPQ0tfTEVOICogKGxvbmcpIFRFU1RfQkxPQ0tfQ09VTlQg LyAoKGVuZFRpbWUgLSBzdGFydFRpbWUpICE9IDAgPyAoZW5kVGltZSAtIHN0 YXJ0VGltZSkgOiAxKSk7DQp9DQovKg0KICogRGlnZXN0cyBhIHJlZmVyZW5j ZSBzdWl0ZSBvZiBzdHJpbmdzIGFuZCBwcmludHMgdGhlIHJlc3VsdHMuDQog Ki8NCnN0YXRpYyB2b2lkDQpTSEFUZXN0U3VpdGUodm9pZCkNCnsNCg0KCXBy aW50ZigiU0hBMSB0ZXN0IHN1aXRlOlxuIik7DQoNCglTSEFTdHJpbmcoIiIp Ow0KCVNIQVN0cmluZygiYSIpOw0KCVNIQVN0cmluZygiYWJjIik7DQoJU0hB U3RyaW5nKCJtZXNzYWdlIGRpZ2VzdCIpOw0KCVNIQVN0cmluZygiYWJjZGVm Z2hpamtsbW5vcHFyc3R1dnd4eXoiKTsNCglTSEFTdHJpbmcNCgkgICAgKCJB QkNERUZHSElKS0xNTk9QUVJTVFVWV1hZWmFiY2RlZmdoaWprbG1ub3BxcnN0 dXZ3eHl6MDEyMzQ1Njc4OSIpOw0KCVNIQVN0cmluZw0KCSAgICAoIjEyMzQ1 Njc4OTAxMjM0NTY3ODkwMTIzNDU2Nzg5MDEyMzQ1Njc4OTBcDQoxMjM0NTY3 ODkwMTIzNDU2Nzg5MDEyMzQ1Njc4OTAxMjM0NTY3ODkwIik7DQp9DQoNCi8q DQogKiBEaWdlc3RzIHRoZSBzdGFuZGFyZCBpbnB1dCBhbmQgcHJpbnRzIHRo ZSByZXN1bHQuDQogKi8NCnN0YXRpYyB2b2lkDQpTSEFGaWx0ZXIoaW50IHRl ZSkNCnsNCglTSEFfQ1RYIGNvbnRleHQ7DQoJdW5zaWduZWQgaW50IGxlbjsN Cgl1bnNpZ25lZCBjaGFyIGJ1ZmZlcltCVUZTSVpdOw0KCXVuc2lnbmVkIGNo YXIgYnVmWzQxXSA9IHswfTsNCg0KCVNIQV9Jbml0KCZjb250ZXh0KTsNCgl3 aGlsZSAoKGxlbiA9IGZyZWFkKGJ1ZmZlciwgMSwgQlVGU0laLCBzdGRpbikp KSB7DQoJCWlmICh0ZWUgJiYgbGVuICE9IGZ3cml0ZShidWZmZXIsIDEsIGxl biwgc3Rkb3V0KSkNCgkJCWVycigxLCAic3Rkb3V0Iik7DQoJCVNIQV9VcGRh dGUoJmNvbnRleHQsIGJ1ZmZlciwgbGVuKTsNCgl9DQoJcHJpbnRmKCIlc1xu IiwgU0hBMV9FbmQoJmNvbnRleHQsYnVmKSk7DQp9DQoNCnN0YXRpYyB2b2lk DQp1c2FnZSh2b2lkKQ0Kew0KDQoJZnByaW50ZihzdGRlcnIsICJ1c2FnZTog c2hhMSBbLXBxcnR4XSBbLXMgc3RyaW5nXSBbZmlsZXMgLi4uXVxuIik7DQoJ ZXhpdCgxKTsNCn0NCg== --0-1941351035-1008416040=:74051 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="sha1.1" Content-Transfer-Encoding: BASE64 Content-ID: <20011215063400.E74051@siteintegrity.net> Content-Description: manual page Content-Disposition: attachment; filename="sha1.1" LlwiICRGcmVlQlNEJA0KLkRkIEZlYnJ1YXJ5IDE0LCAxOTk0DQouRHQgU0hB MSAxDQouT3MNCi5TaCBOQU1FDQouTm0gc2hhMQ0KLk5kIGNhbGN1bGF0ZSBh IG1lc3NhZ2UtZGlnZXN0IGZpbmdlcnByaW50IChjaGVja3N1bSkgZm9yIGEg ZmlsZQ0KLlNoIFNZTk9QU0lTDQouTm0NCi5PcCBGbCBwcXJ0eA0KLk9wIEZs IHMgQXIgc3RyaW5nDQouT3AgQXINCi5TaCBERVNDUklQVElPTg0KLk5tIFNo YTENCnRha2VzIGFzIGlucHV0IGEgbWVzc2FnZSBvZiBhcmJpdHJhcnkgbGVu Z3RoIGFuZCBwcm9kdWNlcw0KYXMgb3V0cHV0IGEgMTYwLWJpdA0KLkRxIGZp bmdlcnByaW50DQpvcg0KLkRxIG1lc3NhZ2UgZGlnZXN0DQpvZiB0aGUgaW5w dXQsIHVzaW5nIHRoZSBOYXRpb25hbCBJbnN0aXR1dGUgb2YgU3RhbmRhcmRz IGFuZCBUZWNobm9sb2d5J3MgU2VjdXJlDQpIYXNoIEFsZ29yaXRobS4gSXQg aXMgY29uamVjdHVyZWQgdGhhdCBpdCBpcyBjb21wdXRhdGlvbmFsbHkgaW5m ZWFzaWJsZSB0bw0KcHJvZHVjZSB0d28gbWVzc2FnZXMgaGF2aW5nIHRoZSBz YW1lIG1lc3NhZ2UgZGlnZXN0LCBvciB0byBwcm9kdWNlIGFueQ0KbWVzc2Fn ZSBoYXZpbmcgYSBnaXZlbiBwcmVzcGVjaWZpZWQgdGFyZ2V0IG1lc3NhZ2Ug ZGlnZXN0Lg0KLlBwDQpUaGUgZm9sbG93aW5nIG9wdGlvbnMgbWF5IGJlIHVz ZWQgaW4gYW55IGNvbWJpbmF0aW9uIGFuZCBtdXN0DQpwcmVjZWRlIGFueSBm aWxlcyBuYW1lZCBvbiB0aGUgY29tbWFuZCBsaW5lLiAgVGhlIFNIQTENCnN1 bSBvZiBlYWNoIGZpbGUgbGlzdGVkIG9uIHRoZSBjb21tYW5kIGxpbmUgaXMg cHJpbnRlZCBhZnRlciB0aGUgb3B0aW9ucw0KYXJlIHByb2Nlc3NlZC4NCi5C bCAtdGFnIC13aWR0aCBpbmRlbnQNCi5JdCBGbCBzIEFyIHN0cmluZw0KUHJp bnQgYSBjaGVja3N1bSBvZiB0aGUgZ2l2ZW4NCi5BciBzdHJpbmcgLg0KLkl0 IEZsIHANCkVjaG8gc3RkaW4gdG8gc3Rkb3V0IGFuZCBhcHBlbmRzIHRoZSBT SEExIHN1bSB0byBzdGRvdXQuDQouSXQgRmwgcQ0KUXVpZXQgbW9kZSAtIG9u bHkgdGhlIFNIQTEgc3VtIGlzIHByaW50ZWQgb3V0LiAgT3ZlcnJpZGVzIHRo ZQ0KLkZsIHINCm9wdGlvbi4NCi5JdCBGbCByDQpSZXZlcnNlcyB0aGUgZm9y bWF0IG9mIHRoZSBvdXRwdXQuICBUaGlzIGhlbHBzIHdpdGggdmlzdWFsIGRp ZmZzLiAgRG9lcyBub3RoaW5nDQp3aGVuIGNvbWJpbmVkIHdpdGggdGhlDQou RmwgcHR4DQpvcHRpb25zLg0KLkl0IEZsIHQNClJ1biBhIGJ1aWx0LWluIHRp bWUgdHJpYWwuDQouSXQgRmwgeA0KUnVuIGEgYnVpbHQtaW4gdGVzdCBzY3Jp cHQuDQouRWwNCi5TaCBTRUUgQUxTTw0KLlhyIGNrc3VtIDENCi5YciBtZDUg MQ0KLlJzDQouJUEgRC4gRWFzdGxha2UNCi4lVCBVUyBTZWN1cmUgSGFzaCBB bGdvcml0aG0gMSAoU0hBMSkNCi4lTyBSRkMzMTc0DQouUmUNCg== --0-1941351035-1008416040=:74051 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=Makefile Content-Transfer-Encoding: BASE64 Content-ID: <20011215063400.A74051@siteintegrity.net> Content-Description: makefile for sha1 belongs (/usr/src/sbin/sha1/) Content-Disposition: attachment; filename=Makefile IwlAKCMpTWFrZWZpbGUJOC4xIChCZXJrZWxleSkgNi85LzkzDQojICRGcmVl QlNEJA0KDQpQUk9HPQlzaGExDQoNCkxEQUREKz0JLWxtZCAtZw0KRFBBREQr PSAke0xJQk1EfQ0KDQouaW5jbHVkZSA8YnNkLnByb2cubWs+DQo= --0-1941351035-1008416040=:74051-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 3:58:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gadolinium.btinternet.com (gadolinium.btinternet.com [194.73.73.111]) by hub.freebsd.org (Postfix) with ESMTP id 751D737B417 for ; Sat, 15 Dec 2001 03:58:02 -0800 (PST) Received: from host213-123-128-172.in-addr.btopenworld.com ([213.123.128.172] helo=there) by gadolinium.btinternet.com with smtp (Exim 3.22 #8) id 16FDS3-0003kr-00; Sat, 15 Dec 2001 11:57:59 +0000 Content-Type: text/plain; charset="iso-8859-1" From: Dominic Marks To: Mike Wiacek , freebsd-hackers@freebsd.org Subject: Re: sha1 program Date: Sat, 15 Dec 2001 11:58:14 +0000 X-Mailer: KMail [version 1.3.2] References: <20011215062918.F74051-400000@siteintegrity.net> In-Reply-To: <20011215062918.F74051-400000@siteintegrity.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Saturday 15 December 2001 11:34 am, Mike Wiacek wrote: > We currently have a MD5 driver, but no SHA1 driver, even though > we have SHA1 as part of libmd. So I took md5.c from > /usr/src/sbin/md5 and made sha1.c as well as a respective man page. > Attached is the source file, the manual page for it, as well as a > makefile. > > Hope this is useful and makes its way into the tree. Md5 has some > questionable attacks against it, and Schneier claims that > sha is resillient to such attacks. > > mike Why not have one program for all the supported hash algorithms as opposed to individual ones for each (md5, sha1) ? You could use something like: > hash -a md5 /some/file > hash -a sha1 /some/other/file -- Dominic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 4:14:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id 5EEC437B419 for ; Sat, 15 Dec 2001 04:14:42 -0800 (PST) Received: from pool0048.cvx22-bradley.dialup.earthlink.net ([209.179.198.48] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16FDiD-00021Q-00; Sat, 15 Dec 2001 04:14:41 -0800 Message-ID: <3C1B3EB2.E6D1F0C0@mindspring.com> Date: Sat, 15 Dec 2001 04:14:42 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Hiten Pandya Cc: hackers@freebsd.org Subject: Re: boot0 References: <20011215092344.54636.qmail@web21110.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hiten Pandya wrote: > I found this piece of code in boot0.s, is it possible > if you could explain me a bit about it. > > .set NHRDRV,0x475 # Number of hard drives > > The hex value comes out to: 1141. > > Does that mean, that this is the amound of maximum > hard drives a user can have on FreeBSD? No. The BIOS bootstrap loaded passes the boot drive in the %DL; this gets pushed, and later poped for the byt compare; the compare is based on a storage location of a relative offset. Frankly, you don't need to understand this code if you are trying to get the boot loader to understand JFS; instead you want to add JFS support into boot1/2 via libstand in /usr/src/lib/libstand. See /usr/src/lib/libstand/ufs.c, and look at how the library is able to select the routines in ufs.c vs. cd9660.c. If you are serious about this, handle read-only non-root JFS mounts of Linux created disks, first, and then work up to read/write, root mount, and then booting (in that order). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 5:35:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 08E8937B405 for ; Sat, 15 Dec 2001 05:35:02 -0800 (PST) Received: from cain.gsoft.com.au (root@localhost [127.0.0.1]) by midget.dons.net.au (8.11.6/8.11.6) with ESMTP id fBFDYpM76173; Sun, 16 Dec 2001 00:04:52 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 16 Dec 2001 00:04:49 +1030 (CST) From: "Daniel O'Connor" To: Dominic Marks Subject: Re: sha1 program Cc: freebsd-hackers@freebsd.org, Mike Wiacek Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 15-Dec-2001 Dominic Marks wrote: > Why not have one program for all the supported hash algorithms as > opposed to individual ones for each (md5, sha1) ? > > You could use something like: > > > hash -a md5 /some/file > > hash -a sha1 /some/other/file Conceivably a fairly simple script or two could be written to use openssl instead. --- 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 7:26:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta05-svc.ntlworld.com (mta05-svc.ntlworld.com [62.253.162.45]) by hub.freebsd.org (Postfix) with ESMTP id EBD3337B416 for ; Sat, 15 Dec 2001 07:26:30 -0800 (PST) Received: from sobek.lan ([62.252.13.211]) by mta05-svc.ntlworld.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with ESMTP id <20011215152629.JJOR27606.mta05-svc.ntlworld.com@sobek.lan>; Sat, 15 Dec 2001 15:26:29 +0000 Received: (from greid@localhost) by sobek.lan (8.11.5/8.11.5) id fBFFQRn06651; Sat, 15 Dec 2001 15:26:27 GMT (envelope-from greid@FreeBSD.org) X-Authentication-Warning: sobek.lan: greid set sender to greid@FreeBSD.org using -f Date: Sat, 15 Dec 2001 15:26:27 +0000 From: George Reid To: Rafter Man Cc: freebsd-hackers@FreeBSD.org Subject: Re: New feutures........... Message-ID: <20011215152627.A6624@FreeBSD.org> References: <20011214150349.3305.qmail@linuxmail.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011214150349.3305.qmail@linuxmail.org>; from rafter@linuxmail.org on Fri, Dec 14, 2001 at 11:03:49PM +0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Dec 14, 2001 at 11:03:49PM +0800, Rafter Man wrote: > 2. I hope that in the furture the FreeBSD developers will rewrite the system > in C++. Geez, talk about a bleak outlook for the future. I see myself flying over a frozen Hell on the back of a pig before that happens. -- George C A Reid Tel: (08701) 200870 Ext. 26654 FreeBSD Committer/Developer greid@FreeBSD.org Oriel College, Oxford University george.reid@oriel.ox.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 7:36:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ms51.hinet.net (ms51.hinet.net [168.95.4.51]) by hub.freebsd.org (Postfix) with ESMTP id 9CEAD37B419; Sat, 15 Dec 2001 07:35:34 -0800 (PST) Received: from u6o9v0 (61-216-40-84.HINET-IP.hinet.net [61.216.40.84]) by ms51.hinet.net (8.8.8/8.8.8) with SMTP id XAA09762; Sat, 15 Dec 2001 23:22:52 +0800 (CST) Message-Id: <200112151522.XAA09762@ms51.hinet.net> From: "dream" To: Subject: ¦æ·Rªº¯u¿Í--ºV¤Ñ°óªºªù Mime-Version: 1.0 Content-Type: text/html; charset="big5" Date: Sat, 15 Dec 2001 23:25:02 +0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG

    • English

        

              

        ¦æ·Rªº¯u¿Í  ºV¤Ñ°óªºªù

       

       

      ·R¬O«í¤[§Ô­@¡A¤S¦³®¦·O¡A·R¬O¤£¶ú§ª¡C·R¬O¤£¦Û¸Ø¡A¤£±i¨g¡A¤£°µ®`²Ûªº¨Æ¡C¤£¨D¦Û¤vªº¯q³B¡A¤£»´©öµo«ã¡A¤£­pºâ¤H®aªº´c¡A¤£³ßÅw¤£¸q¡A¥u³ßÅw¯u²z¡C¤Z¨Æ¥]®e¡A¤Z¨Æ¬Û«H¡A¤Z¨Æ¬ß±æ¡A¤Z¨Æ§Ô­@¡A¤Z¨Æ­n§Ô­@¡A·R¬O¥Ã¤£¤î®§¡C

       

        

         ¡u·Rªº¯u¿Í¡v¬O¸t¸g¤¤ªº¤@¬q¸Ü¡A¸g¤H¾ã²z«á¡AÃЦ¨¤@¦±µÎ½w°ÊÅ¥ªº¤H¶¡¤§ºq¡C³o­ººq±q¤p¦Ü¤µ²`Àò§Ú³ß·R¡A¦L¶H¤¤¬O¦b¤p¾Ç¦X°Û¹Î¾Çªº¡C¦o¨ºÀu¬ü¬X©Mªº±Û«ß¡B¤º²[Â×´Iªººqµü¤£¦ýÀRÀq¦a´þ¾iµÛ§Úµ£¦~ªº¤ßÆF¡A¤]³­§Ú«×¹L¤FµL¼Æ­Ó¤H¥Íªº®À§é»P¦ÒÅç¡A·í§Ú¾D³{­W´o©Î­±¹ïÆg´­®É¡A§Úªº¤ß©³®É±`ÅT°_³o­º¸t¼äµL¤ñªººq¡C

          §Ú±`·t¦Û¨ØªA¨­®Çªº°ò·þ±ÐªB¤Í¡A¦]¬°¯«­n¦o­Ì°µªº¤£¥u¬O´¶³qªº¦n¤H¡A¦Ó¬O¨¥¦æ­Ñ¬ü¡B«~¼w°ª¼äªº¦n¤H¤¤ªº¦n¤H¡I«e¤@°}¤l¡A¤@¦ì°ò·þ±Ð¦P¾Çªº½Í¸Ü¡A«oµ¹¤F§Ú¤@¨Ç«ä¦ÒªºªÅ¶¡¡A§Ú¬ðµM¹ï¦o«H¥õ¤W«Òªº¤è¦¡·P¨ì¦³¨ÇºÃ´b¡C

          ¦o¸g±`¼ö¤ß¦a»P©P³òªº¤H¤À¨É¯«¦p¦ó·RÅ@¥L­Ì¾ã­Ó®a®x¡B¦p¦ó±x¤ß¦w±Æ¦oªº¤H¥Í¾D¹J¡A¯u¤ß¦a¶D»¡µÛ¯«ªºµL¨p¡B°¶¤j»P¥]®e¡C¨º¤ÑÅ¥¨ì¦o»¡¡G¡u¡KµL½×§A¥H«e°µ¤F¤°»ò¤£¦nªº¨Æ¡A¥u­n§A«HÍ¢¡AÍ¢´N·|±a»â§A¨«¦V¤Ñ°ê¡C¡v¹ï¤è°Ý¦o¡G¡u´N³o»ò²³æ¶Ü¡H¥u­n§Ú¬Û«HÍ¢¡A´N¥i¥H¤W¤Ñ°ê¶Ü¡H¡v¦o¦^µª¡G¡u¬O°Ú¡I´N¬O³o»ò²³æ¡I§A¬Ý¤W«Ò¦h»ò°¶¤j§r¡I¡v

           §Ú¥Íªø¦b¤@­Ó¨S¦³¯«¦ò«H¥õ¡B¬Æ¤Ö©v±Ð»ö¦¡ªº®a®x¸Ì¡C¾¨ºÞ¦b¦¨ªø¹Lµ{¤¤¡A»P©v±Ðªº±µÄ²«D±`¦³­­¡A¦ý¬O§Ú¤@ª½²`«H¡A¤HÁ`¸Ó­n¦³ÄÝ©ó¦Û¤vªº«H¥õ¡A¤]¦]¦¹¡A§Ú«K¤£Â_´M§ä¥å¥j¤£Åܪº¯u²z¡C

          ¦]µÛ¦P¾Çªº½Í¸Ü¡A§Ú¦A¤@¦¸«ä¦Ò¤H­Ì¹ï©ó©v±Ðªº»{ª¾¡C¤H¯uªº¤F¸Ñ¯«ªº¦®·N¶Ü¡H§Ú·Q¡A¤£ºÞ¬O­C¿q©Î¬OÄÀ­{¦È¥§¡A¬°¤F±Ï´ç¥@¤H¦Ó¶Ç¹DÁ¿ªk®É¡AÀ³¸Ó¨S¦³»¡¹L¦Û¤v¬O°ò·þ±Ð©Î¬O¦ò±Ð§a¡I·í§Ú»{ÃѨì©v±Ð¬O«á¤H©Ò¦Û³Ðªº¦Wµü¡A»ö¦¡¤]¬O¦]µÛ®ÉªÅ­I´º©Ò¦Û¦æ«Ø¥ßªº¤HÃþ¦æ¬°¡A¦Ó«D¯«ªº¦®·N¡A¤H­Ì«H©^¡BÅ@½Ãªº¬O©v±Ð§Î¦¡¡A¦Ó«D¨ä¤¤©ÒÄÄ´­ªº¯u²z¡A¬è¨Dªº¬O¦Û¤v¦b¥@¶¡ªº¦UºØ²{¹ê§Q¯q®É¡A¹ï©ó²{¤µ½Ñ¦h©v±Ð¶Ã¶H¤]´N¤£¨º»òºN¤£µÛÀYºü¤F¡C¤]Ãø©Ç§Úªº¦P¾Ç·|¦p¦¹¤Ñ¯uªº¥H¬°¥u¦bªí­±¤W¡B§Î¦¡¤W¡u«H­C¿q´N±o¥Ã¥Í¡v¤F¡C

          §Ú»{¬°«H¤£¥u¬Oºë¯«¤Wªº°í¦u¡A§ó¬O¦æ°Ê¤Wªº¸¨¹ê¡C´N¦p¦P§Ú­Ì¦b¾Ç®Õ¾Ç²ß¤@¼Ë¡A¦pªG§Ú¬Û«H¥u­n¦Ò¶i¤@¬y°ª¤¤¡A´N¥i¥H¥]¤¤½Ñ¦h¾Ç¤l¹Ú´K¥H¨Dªº¤j¾Ç¦W®Õ¡A¦Ó¤£¦b¤T¦~ªº°ª¤¤¥Í²P¤¤»{¯uÅ¥Á¿¡AºÉ¤O°µ¦n¤@­Ó¾Ç¥Íªº¥»¤À¡A¤S«ç¯à¹ê²{¦¨¬°¤j¾Ç·sÂA¤Hªº¬üÄR¹Ú·Q©O¡H¥¿½Tªº«ä¦Ò¦ñÀH¿n·¥ªº¦æ°Ê¡A¤£¥¿¬O¦¨´N½Ñ¦h¬ü¨Æªº¥ý¨M­n¥ó¶Ü¡H

          §Ú·Q¤£ºÞ§Ú­Ì¨Ó¦Û¦ó¤è¡A¹LµÛ¤°»ò¼Ëªº¥Í¬¡¡A¬O§_¾Ö¦³©v±Ð«H¥õ¡A§Ú´Á¬ß¤H­Ì³£¯à±N¡u·Rªº¯u¿Í¡vªººë²`¤º²[»P¬ü¦n¼w¦æ¿Ä¤J¥Í¬¡ÂIºw¤§¤¤¡A°µ­Ó¯u¥¿¤ßÆF¼ä²b¡B¹D¼w°ª©|ªº¦n¤H¡C

                                      (ºK¿ý¦Û¤j¬ö¤¸©P³ø)

       

       

       

      ¡·§Úı±o³o¬O¤@½g¦n¤å³¹¡A©Ò¥H·Q©M§ó¦hªº¤H¤À¨É¡A§Æ±æ¨S¦³¥´ÂZ¨ì§A¡C­Y§AÁÙ³ßÅw³o¤å³¹Åwªï¼g«H»P§Ú¤À¨É¡A ­Y§A¤£·Q¦A¦¬¨ìÃþ¦ü¤å³¹¤]½Ð¦^«Hµ¹§Ú¡CÁÂÁ§A¡I
                                                                       Fa-yin

        ¡·¤W¦^¹q¸£·í¾÷¡A¦³¨Ç«H¤£¨£¤F¡A¥i§_½Ð§A¦A±H¤@¦¸µ¹§Ú¡C

            ¡°  This is internet sharing, hope not bothering you. If you can't understand Chinese, please click here reply me, and there will be no  more e-mail from us.  Thank you!

      To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 7:58:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 1409A37B416; Sat, 15 Dec 2001 07:58:37 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fBFFwZn64756; Sat, 15 Dec 2001 16:58:35 +0100 (CET) (envelope-from wkb) Date: Sat, 15 Dec 2001 16:58:35 +0100 From: Wilko Bulte To: George Reid Cc: Rafter Man , freebsd-hackers@FreeBSD.ORG Subject: Re: New feutures........... Message-ID: <20011215165835.A64742@freebie.xs4all.nl> References: <20011214150349.3305.qmail@linuxmail.org> <20011215152627.A6624@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011215152627.A6624@FreeBSD.org>; from greid@FreeBSD.ORG on Sat, Dec 15, 2001 at 03:26:27PM +0000 X-OS: FreeBSD 4.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Dec 15, 2001 at 03:26:27PM +0000, George Reid wrote: > On Fri, Dec 14, 2001 at 11:03:49PM +0800, Rafter Man wrote: > > > 2. I hope that in the furture the FreeBSD developers will rewrite the system > > in C++. > > Geez, talk about a bleak outlook for the future. I see myself flying over > a frozen Hell on the back of a pig before that happens. pig... hmmm. How about a pinguin instead? :) -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 8:28:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from voi.aagh.net (pc1-hart4-0-cust168.mid.cable.ntl.com [62.254.84.168]) by hub.freebsd.org (Postfix) with ESMTP id E977837B405; Sat, 15 Dec 2001 08:28:17 -0800 (PST) Received: from freaky by voi.aagh.net with local (Exim 3.33 #1) id 16FHfW-000FvV-00; Sat, 15 Dec 2001 16:28:10 +0000 Date: Sat, 15 Dec 2001 16:28:09 +0000 From: Thomas Hurst To: Wilko Bulte Cc: George Reid , Rafter Man , freebsd-hackers@FreeBSD.ORG Subject: Re: New feutures........... Message-ID: <20011215162809.GA61084@voi.aagh.net> Mail-Followup-To: Wilko Bulte , George Reid , Rafter Man , freebsd-hackers@FreeBSD.ORG References: <20011214150349.3305.qmail@linuxmail.org> <20011215152627.A6624@FreeBSD.org> <20011215165835.A64742@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011215165835.A64742@freebie.xs4all.nl> User-Agent: Mutt/1.3.24i Organization: Not much. X-Operating-System: FreeBSD/4.4-STABLE (i386) X-Uptime: 4:27PM up 2 days, 1:57, 2 users, load averages: 2.02, 2.02, 2.00 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Wilko Bulte (wkb@freebie.xs4all.nl) wrote: > On Sat, Dec 15, 2001 at 03:26:27PM +0000, George Reid wrote: > > On Fri, Dec 14, 2001 at 11:03:49PM +0800, Rafter Man wrote: > > > > > 2. I hope that in the furture the FreeBSD developers will rewrite > > > the system in C++. > > > > Geez, talk about a bleak outlook for the future. I see myself > > flying over a frozen Hell on the back of a pig before that happens. > > pig... hmmm. How about a pinguin instead? Sorry, the penguin's reserved for when we reimpliment it in Perl. -- Thomas 'Freaky' Hurst - freaky@aagh.net - http://www.aagh.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 9:13: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.mediadesign.nl (md2.mediadesign.nl [212.19.205.67]) by hub.freebsd.org (Postfix) with SMTP id D036D37B41B for ; Sat, 15 Dec 2001 09:12:59 -0800 (PST) Received: (qmail 23418 invoked by uid 1002); 15 Dec 2001 17:12:53 -0000 From: "Alson van der Meulen" Date: Sat, 15 Dec 2001 18:12:53 +0100 To: freebsd-hackers@freebsd.org Subject: Re: sha1 program Message-ID: <20011215181253.U10171@md2.mediadesign.nl> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20011215062918.F74051-400000@siteintegrity.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Dec 15, 2001 at 11:58:14AM +0000, Dominic Marks wrote: > On Saturday 15 December 2001 11:34 am, Mike Wiacek wrote: > > We currently have a MD5 driver, but no SHA1 driver, even though > > we have SHA1 as part of libmd. So I took md5.c from > > /usr/src/sbin/md5 and made sha1.c as well as a respective man page. > > Attached is the source file, the manual page for it, as well as a > > makefile. > > > > Hope this is useful and makes its way into the tree. Md5 has some > > questionable attacks against it, and Schneier claims that > > sha is resillient to such attacks. > > > > mike > > Why not have one program for all the supported hash algorithms as > opposed to individual ones for each (md5, sha1) ? > > You could use something like: > > > hash -a md5 /some/file > > hash -a sha1 /some/other/file It's called openssl. openssl dgst -md5 openssl dgst -sha1 ... You could write a wrapper for this, or just type the 14 extra characters ;) HTH, Alson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 9:18:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 5451B37B417 for ; Sat, 15 Dec 2001 09:18:55 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.6/8.11.4) id fBFHIr491330; Sat, 15 Dec 2001 09:18:53 -0800 (PST) (envelope-from kris) Date: Sat, 15 Dec 2001 09:18:52 -0800 From: Kris Kennaway To: Alson van der Meulen Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: sha1 program Message-ID: <20011215091852.A91288@citusc17.usc.edu> References: <20011215062918.F74051-400000@siteintegrity.net> <20011215181253.U10171@md2.mediadesign.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011215181253.U10171@md2.mediadesign.nl>; from alm@flutnet.org on Sat, Dec 15, 2001 at 06:12:53PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 15, 2001 at 06:12:53PM +0100, Alson van der Meulen wrote: > > Why not have one program for all the supported hash algorithms as=20 > > opposed to individual ones for each (md5, sha1) ? > >=20 > > You could use something like: > >=20 > > > hash -a md5 /some/file > > > hash -a sha1 /some/other/file > It's called openssl. > openssl dgst -md5 > openssl dgst -sha1 > ... >=20 > You could write a wrapper for this, or just type the 14 extra characters > ;) Or just ln -sf /usr/bin/openssl /usr/bin/sha1 OpenSSL already checks the name it's invoked under and behaves accordingly. Kris --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8G4X8Wry0BWjoQKURAp8AAJwKZkY5p//fSsM+3pv/2M4j4c2eDwCg0czC P1WxYFe6AEwI69ikO+Y/0TQ= =8u6B -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 9:29:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salvatore.bol.com.br (salvatore.bol.com.br [200.221.24.47]) by hub.freebsd.org (Postfix) with ESMTP id 093D737B405 for ; Sat, 15 Dec 2001 09:29:50 -0800 (PST) Received: from bol.com.br (200.221.24.84) by salvatore.bol.com.br (5.1.065) id 3BEBE60C0051C3CE for hackers@freebsd.org; Sat, 15 Dec 2001 15:28:25 -0200 Date: Sat, 15 Dec 2001 15:28:24 -0200 Message-Id: Subject: subscribe MIME-Version: 1.0 Content-Type: text/plain;charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable From: "Jorge Teles" To: hackers@freebsd.org X-XaM3-API-Version: 2.4.3.4.4 X-SenderIP: 200.226.145.241 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe Jorge Augusto Teles - JFreeBSD Tecn=F3logo em Processamento de Dados - FATEC - Taquaritinga emails: jorge@fatectq.com.br jorteles@yahoo.com __________________________________________________________________________ Quer ter seu pr=F3prio endere=E7o na Internet? Garanta j=E1 o seu e ainda ganhe cinco e-mails personalizados. Dom=EDniosBOL - http://dominios.bol.com.br To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 9:41:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gwdu60.gwdg.de (gwdu60.gwdg.de [134.76.98.60]) by hub.freebsd.org (Postfix) with ESMTP id DF2F737B417 for ; Sat, 15 Dec 2001 09:41:38 -0800 (PST) Received: from localhost (kheuer@localhost) by gwdu60.gwdg.de (8.11.6/8.11.6) with ESMTP id fBFHfWw50745; Sat, 15 Dec 2001 18:41:32 +0100 (CET) (envelope-from kheuer@gwdu60.gwdg.de) Date: Sat, 15 Dec 2001 18:41:32 +0100 (CET) From: Konrad Heuer To: Jordan Hubbard Cc: Rafter Man , Subject: Re: New feutures........... In-Reply-To: <66128.1008357836@winston.freebsd.org> Message-ID: <20011215183941.Q50729-100000@gwdu60.gwdg.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 14 Dec 2001, Jordan Hubbard wrote: > {.. snip ..} > > 2. I hope that in the furture the FreeBSD developers > > will rewrite the system in C++. > > God, I certainly hope NOT. Jordan, I do agree absolutely and hope your hopes will come true ... :-) Konrad Konrad Heuer Personal Bookmarks: Gesellschaft f=FCr wissenschaftliche Datenverarbeitung mbH G=D6ttingen http://www.freebsd.org Am Fa=DFberg, D-37077 G=D6ttingen http://www.daemonnews.o= rg Deutschland (Germany) kheuer@gwdu60.gwdg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 9:48:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cu518.adelaide.adsl.on.net (cu518.adelaide.adsl.on.net [150.101.236.10]) by hub.freebsd.org (Postfix) with ESMTP id 7BC5B37B416 for ; Sat, 15 Dec 2001 09:48:18 -0800 (PST) Received: from ns.aus.com (cu518.adsl.adelaide.on.net [127.0.0.1]) by cu518.adelaide.adsl.on.net (8.11.0/8.11.0) with ESMTP id fBFJut713917 for ; Sun, 16 Dec 2001 06:26:55 +1030 Message-ID: <3C1B96A9.5060804@ns.aus.com> Date: Sun, 16 Dec 2001 05:00:01 +1030 From: Richard Sharpe Reply-To: rsharpe@ns.aus.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010917 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? References: <3C1AEA9E.6010502@ns.aus.com> <20011215010457.B84861@nexus.root.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Greenman wrote: >>I am playing with a driver for the Broadcom 5700/5701. >> >>It recognizes the 5700 in my 3Com cards OK, but seems to screw up the >>TCP checksum. >> >>Switching off hardware checksum capability fixes it. >> >>Does anyone know the details of which stepping this stuff worked on? >> > > I haven't nailed down the problem that I've seen with them to a specific >chipset, but I can confirm that they incorrectly calculate the checksum on >input packets in some cases. It seems to be related to both packet size and >certain TCP options (or lack of them). I've only seen the problem occur with >very small (0-4 byte payload) packets. > In any case, after discussing this problem with Bill Paul, I disabled >input checksum in the -current driver and intend to merge that to -stable in >a few days. > OK, that makes sense, because I wasn't getting past first base. SYN ACK segments werre being rejected with bad checksum. The driver I modified is actually for the 5701, which works fine with all checksum offloading enabled. I will try to disable just receive TCP checksum and see what happens. -- Richard Sharpe, rsharpe@ns.aus.com, LPIC-1 www.samba.org, www.ethereal.com, SAMS Teach Yourself Samba in 24 Hours, Special Edition, Using Samba To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 10: 3:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F9EA37B41A for ; Sat, 15 Dec 2001 10:03:12 -0800 (PST) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id fBFI3Bu26024 for ; Sat, 15 Dec 2001 10:03:11 -0800 (PST) Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Sat, 15 Dec 2001 10:02:45 -0800 Received: from [17.219.180.26] (minshallidsl1.apple.com [17.219.180.26]) by scv1.apple.com (8.11.3/8.11.3) with ESMTP id fBFI2ua23591; Sat, 15 Dec 2001 10:02:56 -0800 (PST) X-Sender: conrad@mail.apple.com (Unverified) Message-Id: In-Reply-To: <89102.1008197808@winston.freebsd.org> References: Message from Poul-Henning Kamp "of Wed, 12 Dec 2001 21:39:11 +0100." <63529.1008189551@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 15 Dec 2001 09:59:48 -0800 To: Jordan Hubbard , Poul-Henning Kamp From: Conrad Minshall Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 2:56 PM -0800 12/12/01, Jordan Hubbard wrote: >> The only thing I get is a math exception because "closeprob" is zero >> since no -c option was given. >> >> Can you provide some sample parameters please ? > >Hmmm, how strange, now that I look at the code it's obvious that a >divide by zero will occur with a zero closeprob and the docs state the >default to be "infinity", which is obviously not the case. The >strange part is that I ran this on freebsd.apple.com, which is running >4.4-stable, with one parameter (the filename) exactly as I pasted in >the usage instructions before. Perhaps all this time spent living >next to the Macintosh in my office has induced that copy of FreeBSD to >be more "friendly" and mask simple math errors. :-) > >In any case, -c 1 appears to work just fine. That gives a close/open between each "operation". Better is to fix the fsx.c source by inserting an "if" in main()... diff -u -d -b -w -r1.21 fsx.c --- fsx.c 2001/12/11 23:27:20 1.21 +++ fsx.c 2001/12/15 15:31:19 @@ -701,6 +701,7 @@ testcalls++; + if (closeprob) closeopen = (rv >> 3) < (1 << 28) / closeprob; if (debugstart > 0 && testcalls >= debugstart) -- Conrad Minshall, conrad@apple.com, 408 974-2749 Apple Computer, Mac OS X Core Operating Systems To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 10: 3:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id 073B237B405; Sat, 15 Dec 2001 10:03:47 -0800 (PST) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id fBFI3ku26103; Sat, 15 Dec 2001 10:03:46 -0800 (PST) Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Sat, 15 Dec 2001 10:03:12 -0800 Received: from [17.219.180.26] (minshallidsl1.apple.com [17.219.180.26]) by scv1.apple.com (8.11.3/8.11.3) with ESMTP id fBFI31a23606; Sat, 15 Dec 2001 10:03:02 -0800 (PST) X-Sender: conrad@mail.apple.com (Unverified) Message-Id: In-Reply-To: <58885.1008217148@winston.freebsd.org> References: Message from Peter Wemm "of Wed, 12 Dec 2001 17:13:44 PST." <20011213011344.CBDD03810@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 15 Dec 2001 10:00:26 -0800 To: Jordan Hubbard , Peter Wemm From: Conrad Minshall Subject: Re: NFS: How to make FreeBSD fall on its face in one easy step Cc: Mike Smith , Matthew Dillon , hackers@freebsd.org, msmith@mass.dis.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 8:19 PM -0800 12/12/01, Jordan Hubbard wrote: >> To be clear, what exactly are you doing? >> >> It sounds like you're exporting something from freebsd, mounting it on OSX >> and running this tool on OSX against the filesystem exported from freebsd ? >> >> If so, What mount options? NFSv2 or v3? > >That is correct. As to the NFS options used, I honestly couldn't say >since I'm getting at the filesystem through Netinfo and that's handled >by OS X's automount daemon, that having no relation whatsoever to AMD >and hence no amd.conf file or anything else I can easily look at to >determine how it's being mounted. Maybe Mike knows more about how to >find this out - he's not in management. :) In the absence of mount-options the OS X automount tries v3 first, followed by v2 if v3 appears not supported by the server. -- Conrad Minshall, conrad@apple.com, 408 974-2749 Apple Computer, Mac OS X Core Operating Systems To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 10: 4: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id 088BC37B405; Sat, 15 Dec 2001 10:04:03 -0800 (PST) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id fBFI42u26149; Sat, 15 Dec 2001 10:04:02 -0800 (PST) Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Sat, 15 Dec 2001 10:03:33 -0800 Received: from [17.219.180.26] (minshallidsl1.apple.com [17.219.180.26]) by scv1.apple.com (8.11.3/8.11.3) with ESMTP id fBFI3Ta23689; Sat, 15 Dec 2001 10:03:34 -0800 (PST) X-Sender: conrad@mail.apple.com (Unverified) Message-Id: In-Reply-To: <200112130608.fBD689K49906@apollo.backplane.com> References: <58885.1008217148@winston.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 15 Dec 2001 10:02:54 -0800 To: Matthew Dillon , Jordan Hubbard From: Conrad Minshall Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) Cc: Peter Wemm , Mike Smith , hackers@freebsd.org, msmith@mass.dis.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 10:08 PM -0800 12/12/01, Matthew Dillon wrote: > Ok, here is the latest patch for -stable. Note that Kirk comitted a > slightly modified version of the softupdates fix to -current already > (the VOP_FSYNC stuff), which I will be MFCing in 3 days. > > This still doesn't fix all the problems the nfstest program that Jordan > posted finds, but it sure runs a hellofalot longer now before reporting > an error. 10,000+ tests now before failing (NFSv2 and NFSv3). Once it runs aok for a few million operations, try concurrently running: #! /bin/sh while : do sync sleep 1 done In OS X I used that to flush :) out a couple more bugs. -- Conrad Minshall, conrad@apple.com, 408 974-2749 Apple Computer, Mac OS X Core Operating Systems To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 10:50:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-r09.mx.aol.com (imo-r09.mx.aol.com [152.163.225.105]) by hub.freebsd.org (Postfix) with ESMTP id 1F11A37B405; Sat, 15 Dec 2001 10:49:54 -0800 (PST) Received: from TD790@aol.com by imo-r09.mx.aol.com (mail_out_v31_r1.9.) id n.9d.200f9846 (3310); Sat, 15 Dec 2001 13:49:49 -0500 (EST) From: TD790@aol.com Message-ID: <9d.200f9846.294cf54d@aol.com> Date: Sat, 15 Dec 2001 13:49:49 EST Subject: Re: 3Com driver problems To: hackers@freebsd.org Cc: isp@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 12/15/2001 1:07:28 PM Eastern Standard Time, "."@babalo.ru writes: > At 06:41 PM 12/14/2001, you wrote: > >HP889@aol.com writes: > > > Try to front end your machine with a switch...the 5 cards is most > > likely your > > > problem. With each device you increase your bus contention (ie worsen > the > > > worst case bus master scenario)...either that or get a 4 port card that > is > > > more efficient than 5 individual cards. > >I have some opposite expierence. > >This is my biggest router: > >0gw~(1)>uname -a > >FreeBSD gw.pike 4.4-STABLE FreeBSD 4.4-STABLE #0: Wed Sep 19 06:29:38 MSD > >2001 babolo@shikster.pike.ru:/tmp/babolo/usr/src/sys/gw i386 > >0gw~(2)>ifconfig -a > >dc0: flags=8843 mtu 1500 > >dc1: flags=8802 mtu 1500 > >dc2: flags=8843 mtu 1500 > >dc3: flags=8843 mtu 1500 > >xl0: flags=8843 mtu 1500 > >xl1: flags=8843 mtu 1500 > >xl2: flags=8843 mtu 1500 > >6 used 100 M ethernet interfaces among others. > >dc0..dc3 is one card. > >xl0 cards are workaround for the fact that processor > sty > >spent MUCH more time in interrupt state with dc driver > >than with xl driver with the same load. > >Yes, I try find xl x 4 card but no success Interrupt state and bus contention are 2 different problems...the problem with referencing the dc driver is that there are lots of different cards with different results. btw, the if_dc driver is one of the drivers optimized for the alpha (note the m_devget calls)..and can use a bit of tuning. my experience with dlink quad cards and xl is that they are similar in performance if you account for the fact that the quad cards are going through a pci bridge chip...and the reduction in bus contention versus using 4 cards. One issue is that you (and alot of others) dont understand the physical limits of your machine. putting 6 or more 100Mb/s ethernets on one 32bit bus is simply asking for problems. You are dealing with a bus that BURSTs to a bit more than a Gb and probably no more sustained throughput capability than 500Mb/s (with 2 cards you'll get some errors at 400Mb/s and down from there as you add cards)...so how do you expect to handle worst case DMA requirements of 600-800Mb/s in half duplex or twice that if you run 100Mb/s full duplex? Its just not physically possible. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 10:51:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-m05.mx.aol.com (imo-m05.mx.aol.com [64.12.136.8]) by hub.freebsd.org (Postfix) with ESMTP id 4535F37B41D; Sat, 15 Dec 2001 10:50:52 -0800 (PST) Received: from TD790@aol.com by imo-m05.mx.aol.com (mail_out_v31_r1.9.) id n.e4.1f926a1e (3310); Sat, 15 Dec 2001 13:50:46 -0500 (EST) From: TD790@aol.com Message-ID: Date: Sat, 15 Dec 2001 13:50:46 EST Subject: re: Sherlock Wemm reports.... To: hackers@freebsd.org Cc: isp@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sherlock Wemm writes.... >FYI, this is another dennis@etinc.com clone. and your point is? I dont see any of you helping this guy out; you apparently are a lot better at tracking me down than problems with ethernet drivers, which dont ever seem to get addressed unless some company that one of you is working for needs it. Some of you grumble that I dont donate code, but you dont agree that there are problems, so its a bit difficult to contribute something that noone thinks is needed. Im doing bandwidth management on full gigabit streams with FBSD 4.4..and I've come to a full understand of all of the bottlenecks regarding ethernet drivers. Frankly i couldnt give a rats ass if you like me or not or if you perceive that Im making money off of your work or whatever, but if you think that I dont know what im doing then you are either paying attention to the wrong set of issues or you are just plain stupid. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 11:12:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from breg.mc.mpls.visi.com (breg.mc.mpls.visi.com [208.42.156.101]) by hub.freebsd.org (Postfix) with ESMTP id 2B9A037B417 for ; Sat, 15 Dec 2001 11:12:10 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by breg.mc.mpls.visi.com (Postfix) with ESMTP id 3FF1C2D0549 for ; Sat, 15 Dec 2001 13:12:09 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBFJC8D39442 for hackers@freebsd.org; Sat, 15 Dec 2001 13:12:08 -0600 (CST) (envelope-from hawkeyd) Date: Sat, 15 Dec 2001 13:12:08 -0600 From: D J Hawkey Jr To: hackers@freebsd.org Subject: Q: What's the purpose of "Attic" in CVS? Message-ID: <20011215131208.A39406@sheol.localdomain> Reply-To: hawkeyd@visi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello All. The subject asks it all. Sorry if this is off-topic. One other Q, as long as I'm posting: For those releases that have both a RELENG_X_Y and a RELENG_X_Y_BP branch, what's the difference? AFAIK, the first is for bug fixes; what's the second for? Well, now one more: What are RELENG_X and RELENG_X_BP as they relate to RELENG_X_Y and RELENG_X_Y_BP? I'm rifling through CVS to see if the patchfiles I'm offering on the FreeBSD Backports site are applicable to many releases (some are, I've discovered), and I want to make sure I understand the meaning of these CVS branches. Thanks, Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 11:19:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 75F3937B417 for ; Sat, 15 Dec 2001 11:19:23 -0800 (PST) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011215191923.BMMU10701.rwcrmhc53.attbi.com@bmah.dyndns.org>; Sat, 15 Dec 2001 19:19:23 +0000 Received: (from bmah@localhost) by bmah.dyndns.org (8.11.6/8.11.6) id fBFJJM418690; Sat, 15 Dec 2001 11:19:22 -0800 (PST) (envelope-from bmah) Message-Id: <200112151919.fBFJJM418690@bmah.dyndns.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: hawkeyd@visi.com Cc: hackers@FreeBSD.ORG Subject: Re: Q: What's the purpose of "Attic" in CVS? In-Reply-To: <20011215131208.A39406@sheol.localdomain> References: <20011215131208.A39406@sheol.localdomain> Comments: In-reply-to D J Hawkey Jr message dated "Sat, 15 Dec 2001 13:12:08 -0600." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_2108511394P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sat, 15 Dec 2001 11:19:22 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --==_Exmh_2108511394P Content-Type: text/plain; charset=us-ascii If memory serves me right, D J Hawkey Jr wrote: > One other Q, as long as I'm posting: For those releases that have both a > RELENG_X_Y and a RELENG_X_Y_BP branch, what's the difference? AFAIK, the > first is for bug fixes; what's the second for? RELENG_X_Y_BP represents the "Branch Point" where the RELENG_X_Y branch was created from the RELENG_X branch. > Well, now one more: What are RELENG_X and RELENG_X_BP as they relate to > RELENG_X_Y and RELENG_X_Y_BP? Similarly...RELENG_X_BP represents the point where the RELENG_X was branched from HEAD. *_BP is a FreeBSD convention...CVS doesn't have a way of expressing "the point where a branch was made", so we have to tag the tree explicitly. For more information, see Murray Stokely's excellent FreeBSD release engineering article: http://www.freebsd.org/internal/releng.html Bruce. --==_Exmh_2108511394P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE8G6I62MoxcVugUsMRApGnAKCE1ax0YPK/DsoaJfrwZLQlRjRIBgCgoa0f Yur5qv9KZBBlYaq9qZZSEEk= =M9gU -----END PGP SIGNATURE----- --==_Exmh_2108511394P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 11:28:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brea.mc.mpls.visi.com (brea.mc.mpls.visi.com [208.42.156.100]) by hub.freebsd.org (Postfix) with ESMTP id 6D3E737B405 for ; Sat, 15 Dec 2001 11:28:15 -0800 (PST) Received: from sheol.localdomain (hawkeyd-fw.dsl.visi.com [208.42.101.193]) by brea.mc.mpls.visi.com (Postfix) with ESMTP id 99BE32DDBE0 for ; Sat, 15 Dec 2001 13:28:14 -0600 (CST) Received: (from hawkeyd@localhost) by sheol.localdomain (8.11.1/8.11.1) id fBFJSEk39586 for hackers@freebsd.org; Sat, 15 Dec 2001 13:28:14 -0600 (CST) (envelope-from hawkeyd) Date: Sat, 15 Dec 2001 13:28:14 -0600 From: D J Hawkey Jr To: hackers@freebsd.org Subject: Re: Q: What's the purpose of "Attic" in CVS? Message-ID: <20011215132814.A39546@sheol.localdomain> Reply-To: hawkeyd@visi.com References: <20011215131208.A39406@sheol.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011215131208.A39406@sheol.localdomain>; from hawkeyd@visi.com on Sat, Dec 15, 2001 at 01:12:08PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sorry, I mis-wrote: On Dec 15, at 01:12 PM, D J Hawkey Jr wrote: > > One other Q, as long as I'm posting: For those releases that have both a > RELENG_X_Y and a RELENG_X_Y_BP branch, what's the difference? AFAIK, the > first is for bug fixes; what's the second for? ^^^^^^^^^ should be "security fixes" Already got a reply stating the relationship; thanks Bruce. Dave -- ______________________ ______________________ \__________________ \ D. J. HAWKEY JR. / __________________/ \________________/\ hawkeyd@visi.com /\________________/ http://www.visi.com/~hawkeyd/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 11:49:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 7E5E337B417 for ; Sat, 15 Dec 2001 11:49:19 -0800 (PST) Received: from pool0124.cvx22-bradley.dialup.earthlink.net ([209.179.198.124] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16FKoA-00021t-00; Sat, 15 Dec 2001 11:49:18 -0800 Message-ID: <3C1BA93C.D732C8C6@mindspring.com> Date: Sat, 15 Dec 2001 11:49:16 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: hawkeyd@visi.com Cc: hackers@freebsd.org Subject: Re: Q: What's the purpose of "Attic" in CVS? References: <20011215131208.A39406@sheol.localdomain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG D J Hawkey Jr wrote: > > Hello All. > > The subject asks it all. Sorry if this is off-topic. I won't answer the other questions because they were already answered. The subject question, though.. The "Attic" is the directory where deleted files are moved. This is necessary, since a soruce code control system can be used to create the current version of the software... or the software from last month, where there used to be a seperate "ftp.c" instead of "a magic Makefile"... or the software as as it existed for the 3.1-RELEASE. For this to work, it has to be able to access instances of files which have been deleted or moved... so it looks in the directory where the files should be, except in the "Attic" subdirectory. You should really read the CVS FAQ... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 12: 5:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id AF7E537B419 for ; Sat, 15 Dec 2001 12:05:34 -0800 (PST) Received: (qmail 4169 invoked from network); 15 Dec 2001 19:58:54 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 15 Dec 2001 19:58:54 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20011215092344.54636.qmail@web21110.mail.yahoo.com> Date: Sat, 15 Dec 2001 11:58:34 -0800 (PST) From: John Baldwin To: Hiten Pandya Subject: RE: boot0 Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 15-Dec-01 Hiten Pandya wrote: > hi, > I found this piece of code in boot0.s, is it possible > if you could explain me a bit about it. > > .set NHRDRV,0x475 # Number of hard drives > > The hex value comes out to: 1141. > > Does that mean, that this is the amound of maximum > hard drives a user can have on FreeBSD? No. It's the offset in memory of the number of hard drives in the BIOS. The BIOS has a data segment at 0x40, and at 0x40:0x75 (whose physical address is 0x475) it has a byte which is a count of the number of hard drives installed. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 13:25:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.rwwa.com (ns1.rwwa.com [66.92.67.110]) by hub.freebsd.org (Postfix) with ESMTP id E40CD37B41A for ; Sat, 15 Dec 2001 13:25:23 -0800 (PST) Received: from rwwa.com (harvey.rwwa.com [192.124.97.11]) by ns1.rwwa.com (Postfix) with ESMTP id 48EDA322A for ; Sat, 15 Dec 2001 16:25:23 -0500 (EST) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: hackers@freebsd.org Subject: wchar.h, ports packages, and FBSD version? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 15 Dec 2001 16:25:31 -0500 From: Robert Withrow Message-Id: <20011215212523.48EDA322A@ns1.rwwa.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi: I've installed the python-2.1.1 package on a 4.3-RELEASE system, and in the process of building zope, discovered that python is configured with: /* Define if the compiler provides a wchar.h header file. */ #define HAVE_WCHAR_H 1 ...Which I gather is a lie for 4.3. I'm assuming that either STABLE or CURRENT *does* have wchar.h. This leads to questions: 1 - Are port packages built on a CURRENT system? 2 - Is it wrong to install packages on anything but a bleedin' edge current system? 3 - If it isn't wrong, then what is the expected way of dealing with problems like the above? Maybe I'm goofy, but it seems like packages should be built for *compatibility* which would mean building them on something older than either STABLE or CURRENT, since they are then automatically compatible with newer systems. --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 14: 5:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from root.com (unknown [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id DBD0B37B417 for ; Sat, 15 Dec 2001 14:05:52 -0800 (PST) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id fBFLuZu86355; Sat, 15 Dec 2001 13:56:35 -0800 (PST) (envelope-from dg) Date: Sat, 15 Dec 2001 13:56:35 -0800 From: David Greenman To: Terry Lambert Cc: Alfred Perlstein , Brooks Davis , rsharpe@ns.aus.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? Message-ID: <20011215135635.A86349@nexus.root.com> References: <3C1AEA9E.6010502@ns.aus.com> <20011214214118.A30560@Odin.AC.HMC.Edu> <3C1AF362.534BD2F7@mindspring.com> <20011215005739.A84861@nexus.root.com> <20011215031304.N79896@elvis.mu.org> <20011215011045.C84861@nexus.root.com> <3C1B32EB.ACBA8DB@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C1B32EB.ACBA8DB@mindspring.com>; from tlambert2@mindspring.com on Sat, Dec 15, 2001 at 03:24:27AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >David Greenman wrote: >> Alfred Perlstein wrote: >> >You're probably incorrect, it doesn't matter if vlan tags are active >> >or not, it's most likely wheather or not the firmware is being asked >> >to handle them at all. >> >> I would think it would get the checksum wrong most of the time if that >> were the case. It seems to only have problems with small packets, but the >> behavior is pretty strange, so who knows. Do you have some specific knowledge >> about Broadcom and brokeness related to VLAN tag support when not using >> VLANs? > >If it's very small payload, it's probably a byte-order-in-buffer >issue (several Eagle manufactured cards had similar problems, and >so did the NE1000, when it came to DMA transfers, back when 16 bit >transfers were new 8^). The packet itself is fine, it's just the checksum that the hardware calculates is wrong. >For VLANs, yes, there are specific problems known with the Broadcom >cards when the firmware support for VLANs is enabled. The first card >known to work with checksum offload enable and VLAN support enabled >(whether it's used or not) is the Tigon III. I don't know if Bill >Paul fixed the firmware for the Tigon II in this case (he has been >known to hack Tigon II firmware), but it could have been fixed by now. > >In any case, disabling it is what ClickArray ended up doing, as well, >for the Tigon II, until the firmware could be fixed. We're talking about the Tigon III (bge driver for Broadcom BCM5700/BCM5701). -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 14:26:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 0BC0137B405; Sat, 15 Dec 2001 14:26:39 -0800 (PST) Received: from pool0252.cvx21-bradley.dialup.earthlink.net ([209.179.192.252] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16FNGL-0007Im-00; Sat, 15 Dec 2001 14:26:33 -0800 Message-ID: <3C1BCE1B.53643B6D@mindspring.com> Date: Sat, 15 Dec 2001 14:26:35 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: Hiten Pandya , hackers@freebsd.org Subject: Re: boot0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > No. It's the offset in memory of the number of hard drives in the BIOS. The > BIOS has a data segment at 0x40, and at 0x40:0x75 (whose physical address is > 0x475) it has a byte which is a count of the number of hard drives installed. Specifically, Hiten, see: Page 4-9, table 4.002 "BIOS Memory Usage Summary" The Programmers PC Sourcebook Thom Hogan Microsoft Press ISBN: 1-55615-321-X Or: Page 505, Table 11-9 "Hard Disk BIOS Data" The Undocumented PC Frank van Gilluwe Addison-Wesley ISBN: 0-201-62277-7 Seriously, you probably do not need to know how this works. If you are interested enough in PC hardware, and just want to know, you could do worse than buying one or both of these books. You might also want to do a web search for "Ralf Brown Interrupt List". -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 14:44: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id F290137B416 for ; Sat, 15 Dec 2001 14:44:06 -0800 (PST) Received: from pool0252.cvx21-bradley.dialup.earthlink.net ([209.179.192.252] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16FNXB-00056A-00; Sat, 15 Dec 2001 14:43:58 -0800 Message-ID: <3C1BD22F.F3A52BF4@mindspring.com> Date: Sat, 15 Dec 2001 14:43:59 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: David Greenman Cc: Alfred Perlstein , Brooks Davis , rsharpe@ns.aus.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? References: <3C1AEA9E.6010502@ns.aus.com> <20011214214118.A30560@Odin.AC.HMC.Edu> <3C1AF362.534BD2F7@mindspring.com> <20011215005739.A84861@nexus.root.com> <20011215031304.N79896@elvis.mu.org> <20011215011045.C84861@nexus.root.com> <3C1B32EB.ACBA8DB@mindspring.com> <20011215135635.A86349@nexus.root.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Greenman wrote: > >In any case, disabling it is what ClickArray ended up doing, as well, > >for the Tigon II, until the firmware could be fixed. > > We're talking about the Tigon III (bge driver for Broadcom BCM5700/BCM5701). Crap. Thanks for the info. Have you manually calculated the checksum on a bad packet to see how it's off? PS: Is it -0 (0xFFFF)? Maybe they didn't use RFC 1936; maybe they used RFC 1141, which has a bug (RFC 1624 corrects the one's complement error of RFC 1141). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 15:18:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 9F1A737B405 for ; Sat, 15 Dec 2001 15:18:19 -0800 (PST) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id fBFN9Xf86558; Sat, 15 Dec 2001 15:09:33 -0800 (PST) (envelope-from dg) Date: Sat, 15 Dec 2001 15:09:33 -0800 From: David Greenman To: Terry Lambert Cc: Alfred Perlstein , Brooks Davis , rsharpe@ns.aus.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Does anyone know if the Broadcom BCM5700 has problems with HW csum? Message-ID: <20011215150933.B86349@nexus.root.com> References: <3C1AEA9E.6010502@ns.aus.com> <20011214214118.A30560@Odin.AC.HMC.Edu> <3C1AF362.534BD2F7@mindspring.com> <20011215005739.A84861@nexus.root.com> <20011215031304.N79896@elvis.mu.org> <20011215011045.C84861@nexus.root.com> <3C1B32EB.ACBA8DB@mindspring.com> <20011215135635.A86349@nexus.root.com> <3C1BD22F.F3A52BF4@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C1BD22F.F3A52BF4@mindspring.com>; from tlambert2@mindspring.com on Sat, Dec 15, 2001 at 02:43:59PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >David Greenman wrote: >> >In any case, disabling it is what ClickArray ended up doing, as well, >> >for the Tigon II, until the firmware could be fixed. >> >> We're talking about the Tigon III (bge driver for Broadcom BCM5700/BCM5701). > >Crap. Thanks for the info. > >Have you manually calculated the checksum on a bad packet to see >how it's off? Yes. It's typically off by 0x1051, but varies depending on the TCP/IP header contents. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 16:49:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id B2FFB37B405; Sat, 15 Dec 2001 16:49:31 -0800 (PST) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id DAA09823; Sun, 16 Dec 2001 03:56:02 +0300 (MSK) Message-Id: <200112160056.DAA09823@aaz.links.ru> Subject: Re: 3Com driver problems In-Reply-To: <9d.200f9846.294cf54d@aol.com> from "TD790@aol.com" at "Dec 15, 1 01:49:49 pm" To: TD790@aol.com Date: Sun, 16 Dec 2001 03:56:02 +0300 (MSK) Cc: hackers@FreeBSD.ORG, isp@FreeBSD.ORG From: "."@babolo.ru MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG TD790@aol.com writes: > In a message dated 12/15/2001 1:07:28 PM Eastern Standard Time, "."@babalo.ru > writes: > > > At 06:41 PM 12/14/2001, you wrote: > > >HP889@aol.com writes: > > > > Try to front end your machine with a switch...the 5 cards is most > > > likely your > > > > problem. With each device you increase your bus contention (ie worsen > > the > > > > worst case bus master scenario)...either that or get a 4 port card > that > > is > > > > more efficient than 5 individual cards. > > >I have some opposite expierence. > > >This is my biggest router: > > >0gw~(1)>uname -a > > >FreeBSD gw.pike 4.4-STABLE FreeBSD 4.4-STABLE #0: Wed Sep 19 06:29:38 MSD > > >2001 babolo@shikster.pike.ru:/tmp/babolo/usr/src/sys/gw i386 > > >0gw~(2)>ifconfig -a > > >dc0: flags=8843 mtu 1500 > > >dc1: flags=8802 mtu 1500 > > >dc2: flags=8843 mtu 1500 > > >dc3: flags=8843 mtu 1500 > > >xl0: flags=8843 mtu 1500 > > >xl1: flags=8843 mtu 1500 > > >xl2: flags=8843 mtu 1500 > > >6 used 100 M ethernet interfaces among others. > > >dc0..dc3 is one card. > > >xl0 cards are workaround for the fact that processor > > sty > > > >spent MUCH more time in interrupt state with dc driver > > >than with xl driver with the same load. > > >Yes, I try find xl x 4 card but no success > > Interrupt state and bus contention are 2 different problems...the problem > with referencing the dc driver is that there are lots of different cards with > different results. btw, the if_dc driver is one of the drivers optimized for > the alpha (note the m_devget calls)..and can use a bit of tuning. my > experience with dlink quad cards and xl is that they are similar in > performance if you account for the fact that the quad cards are going through > a pci bridge chip...and the reduction in bus contention versus using 4 cards. Mine 4 port card was bought as D-link... What is "a bit of tuning"? Yes, I played with shared and non-shared interrupts to assign non-shared to most loaded ports > One issue is that you (and alot of others) dont understand the physical I come to FreeBSD after I was a hardware developper. Hardware constraints are the things I understand well. I do not connect all high load interfaces to one router and this example has 3 relatively high load interfaces. > limits of your machine. putting 6 or more 100Mb/s ethernets on one 32bit bus > is simply asking for problems. You are dealing with a bus that BURSTs to a > bit more than a Gb and probably no more sustained throughput capability than > 500Mb/s (with 2 cards you'll get some errors at 400Mb/s and down from there > as you add cards)...so how do you expect to handle worst case DMA > requirements of 600-800Mb/s in half duplex or twice that if you run 100Mb/s > full duplex? Its just not physically possible. I have no problem with this router now. There is a home network, so no one want to pay more if quality is sufficient. The worst interface has about 1:10000 loss - it's OK. Average packet rate for last 67 days is 860 pkt/sec only, burst rate is about 5 times more for 2 min intervals. Yes, I have no direct data about real (short) bursts, but total packet loss is sufficiently low. The real restriction is IP rule complexity. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 17:24:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DF1BF37B416; Sat, 15 Dec 2001 17:24:12 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBG1Mtq18851; Sat, 15 Dec 2001 17:22:55 -0800 (PST) (envelope-from dillon) Date: Sat, 15 Dec 2001 17:22:55 -0800 (PST) From: Matthew Dillon Message-Id: <200112160122.fBG1Mtq18851@apollo.backplane.com> To: Conrad Minshall , Jordan Hubbard , Peter Wemm , Mike Smith , hackers@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step ) References: <58885.1008217148@winston.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Once it runs aok for a few million operations, try concurrently running: : :#! /bin/sh :while : :do : sync : sleep 1 :done : :In OS X I used that to flush :) out a couple more bugs. : :-- :Conrad Minshall, conrad@apple.com, 408 974-2749 :Apple Computer, Mac OS X Core Operating Systems Ho! Will do. I'm going to try to speed things up a bit by having the NFS server export an MFS filesystem. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 17:26: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id C6FA737B417 for ; Sat, 15 Dec 2001 17:25:59 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id 73950786E4; Sun, 16 Dec 2001 11:55:56 +1030 (CST) Date: Sun, 16 Dec 2001 11:55:56 +1030 From: Greg Lehey To: Terry Lambert , Warren Toomey Cc: Peter Jeremy , freebsd-hackers@freebsd.org Subject: Re: Adding a new FS to FreeBSD Message-ID: <20011216115556.A62493@monorchid.lemis.com> References: <20011214141518.E73243@gsmx07.alcatel.com.au> <3C1A09BB.DEBCB854@mindspring.com> <20011215102442.E85108@monorchid.lemis.com> <3C1B0C44.E5A108A4@mindspring.com> <20011215193226.J87600@monorchid.lemis.com> <3C1B3189.CD0B1D1A@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C1B3189.CD0B1D1A@mindspring.com> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Saturday, 15 December 2001 at 3:18:33 -0800, Terry Lambert wrote: > Greg Lehey wrote: >> Unfortunately, it's still copyrighted. You need an SCO license; want >> to go and get one of them? It doesn't cost anything, but I can't give >> the software to anybody who hasn't agreed to the conditions. > > 8.4(b) says you can't give it to anyone, even if they do have the > license, unless you contact Caldera first, and then maintain (in > perpeturity) a list of the sources made available. This is rather contradicted by the bottom of http://www2.caldera.com/offers/ancient001/: Now that you have agreed to the license you may choose to apply for access to their archive of older UNIX or request a CD of this archive. I'm one of the people who make the archive available, so feel free to contact me :-) > I think we are screwed by section 2.1(d) anyway: > > Commercial use by LICENSEE of SOURCE CODE PRODUCTS or > of any result, enhancement or modification associated > with the use of SOURCE CODE PRODUCTS under this AGREEMENT > is not permitted. > > Basically, I couldn't get an article out of it because I could't > disclose it to anyone but a licensesee, and only a licensee could > use the code, and I couldn't give source to the licensee without > the permission of Caldera, and once they had the code, they could > not use it for anything commercial unless they negotiated a seperate > commercial use license. That may be easier than you think. I'm copying Warren Toomey on this. Warren is (a) a FreeBSD user and (b) the person who negotiated these contracts in the first place. Warren, Peter is thinking of porting the 2BSD file system (not sure whether that's UFS or the original UNIX file system) to FreeBSD. As Terry observes, the current license doesn't allow that. Terry, the other thing you *can* do is access the source code once you have agreed to the conditions. See the reference to http://minnie.cs.adfa.edu.au/cgi-bin/pupsco.cgi at the bottom of the page http://www2.caldera.com/offers/ancient001/. Change this to http://minnie.tuhs.org/cgi-bin/pupsco.cgi and you should be able to access it. Again, Warren is the person to talk to if you have trouble. > Frankly, if you want to provide small disk images (preferrably, very > small, not multimegabyte) as I've described are needed anyway, along > with a description of the what's on the images, along with such > layout information as you feel comfortable providing, I'd pretty > much rather reverse engineer the stuff than get a Caldera license. It's a slow way of doing things. Of course, if this is an old version of UFS, you might find it easy enough to get our current UFS to grok the layout. Note that Caldera is merely doing due diligence here; I don't think that they really care too much. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 17:56:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id B5BEF37B405; Sat, 15 Dec 2001 17:56:37 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id fBG1uLs65225; Sat, 15 Dec 2001 17:56:21 -0800 (PST) (envelope-from rizzo) Date: Sat, 15 Dec 2001 17:56:21 -0800 From: Luigi Rizzo To: "."@babolo.ru Cc: TD790@aol.com, hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: Re: 3Com driver problems Message-ID: <20011215175620.A64769@iguana.aciri.org> References: <9d.200f9846.294cf54d@aol.com> <200112160056.DAA09823@aaz.links.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200112160056.DAA09823@aaz.links.ru> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Dec 16, 2001 at 03:56:02AM +0300, "."@babolo.ru wrote: >> different results. btw, the if_dc driver is one of the drivers optimized for >> the alpha (note the m_devget calls)..and can use a bit of tuning. my this has been fixed recently in both stable and current. luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 19:27:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id B040337B419; Sat, 15 Dec 2001 19:27:50 -0800 (PST) Received: from cain.gsoft.com.au (root@localhost [127.0.0.1]) by midget.dons.net.au (8.11.6/8.11.6) with ESMTP id fBG3RiM83298; Sun, 16 Dec 2001 13:57:44 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20011215091852.A91288@citusc17.usc.edu> Date: Sun, 16 Dec 2001 13:57:44 +1030 (CST) From: "Daniel O'Connor" To: Kris Kennaway Subject: Re: sha1 program Cc: freebsd-hackers@FreeBSD.ORG, Alson van der Meulen Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 15-Dec-2001 Kris Kennaway wrote: > Or just ln -sf /usr/bin/openssl /usr/bin/sha1 > > OpenSSL already checks the name it's invoked under and behaves > accordingly. Does it grok the options for md5? :) -s would be easy to simulate in a shell script. -p would be much more difficult unless openssl supports it. --- 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 22:18:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from minnie.tuhs.org (minnie.tuhs.org [131.245.7.145]) by hub.freebsd.org (Postfix) with ESMTP id 75D9937B405; Sat, 15 Dec 2001 22:18:54 -0800 (PST) Received: (from wkt@localhost) by minnie.tuhs.org (8.11.3/8.11.3) id fBG6IcK23973; Sun, 16 Dec 2001 17:18:38 +1100 (EST) (envelope-from wkt) From: Warren Toomey Message-Id: <200112160618.fBG6IcK23973@minnie.tuhs.org> Subject: Re: Caldera and the Ancient UNIX license In-Reply-To: <20011216115556.A62493@monorchid.lemis.com> from Greg Lehey at "Dec 16, 2001 11:55:56 am" To: Greg Lehey Date: Sun, 16 Dec 2001 17:18:37 +1100 (EST) Cc: Terry Lambert , Warren Toomey , Peter Jeremy , freebsd-hackers@FreeBSD.org Reply-To: wkt@tuhs.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article by Greg Lehey: [about if and how Caldera is enforcing the Ancient UNIX http://www2.caldera.com/offers/ancient.html. Note also that in fact they allow access to the code via license described at http://www2.caldera.com/offers/ancient001/ without you first agreeing to the license...] > That may be easier than you think. I'm copying Warren Toomey on > this. Warren is (a) a FreeBSD user and (b) the person who negotiated > these contracts in the first place. Warren, Peter is thinking of > porting the 2BSD file system (not sure whether that's UFS or the > original UNIX file system) to FreeBSD. As Terry observes, the current > license doesn't allow that. Firstly, call me crazy, but I thought the 2BSD filesystem layout was essentially UFS, i.e i-nodes at the start, and therefore would be pretty much the same as /sys/ufs/ufs in FreeBSD. I'll have to do a compare of the source code and get back to you .... I concur with Terry that as the license stands, you first have to prove that a person has agreed to the license before you can give them access to the source code. I would really like to get Caldera to at least remove _this_ condition, even if they left the remaining conditions. It would allow me to set up anonymous access to the old UNIX sources. As for commercial use, that's a separate issue. I don't know how easy it would be for us to talk Caldera into allowing that. Which brings me to the question, does anybody know a good contact at Caldera who can point us to the `right person' to negotiate on this. I knew the guy at SCO who dealt with this, but not at Caldera. > Note that Caldera is merely doing due diligence here; I don't think > that they really care too much. > Greg See me comment about URLs at the top about this :) I'll do a code comparison of FreeBSD /sys/ufs/ufs and 2.11BSD ufs while we wait for contact with Caldera. Cheers all, Warren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 15 23:37:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from minnie.tuhs.org (minnie.tuhs.org [131.245.7.145]) by hub.freebsd.org (Postfix) with ESMTP id 1FB0C37B416; Sat, 15 Dec 2001 23:37:42 -0800 (PST) Received: (from wkt@localhost) by minnie.tuhs.org (8.11.3/8.11.3) id fBG7bXt24793; Sun, 16 Dec 2001 18:37:33 +1100 (EST) (envelope-from wkt) From: Warren Toomey Message-Id: <200112160737.fBG7bXt24793@minnie.tuhs.org> Subject: Re: Adding a new FS to FreeBSD In-Reply-To: <20011216115556.A62493@monorchid.lemis.com> from Greg Lehey at "Dec 16, 2001 11:55:56 am" To: Greg Lehey Date: Sun, 16 Dec 2001 18:37:33 +1100 (EST) Cc: Terry Lambert , Warren Toomey , Peter Jeremy , freebsd-hackers@FreeBSD.org Reply-To: wkt@tuhs.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM715206727-24759-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ELM715206727-24759-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit In article by Greg Lehey: > That may be easier than you think. I'm copying Warren Toomey on > this. Warren is (a) a FreeBSD user and (b) the person who negotiated > these contracts in the first place. Warren, Peter is thinking of > porting the 2BSD file system (not sure whether that's UFS or the > original UNIX file system) to FreeBSD. As Terry observes, the current > license doesn't allow that. All, I've had a brief look at the UFS implementation in FreeBSD 4.x, 2.11BSD and a few other systems. I would say that there's enough in FreeBSD's /sys/ufs/ufs code that 2.11BSD's UFS code is not required. Perhaps you could read 2.11BSD's code just to cross check things in FreeBSD's UFS implementation. I've attached a GIF to show the relationship between the various systems al the way back to the UFS in 7th Edition (1979). I have also put up the code for comparison at: http://minnie.tuhs.org/UnixTree/ As per the Caldera license, you need to prove that you agree to this license to get access. This is easily done at: http://www.tuhs.org/archive_access.html and you will be e-mailed your username and password. Obviously, the codebase has diverged between FreeBSD and 2.11BSD, but I would say that FreeBSD already has a nearly-working UFS implementation. Also, the structure of UFS is so well documented in various books that, even if FreeBSD's UFS implementation was deficient, it could be rectified with reference to the books. Hope this helps, Warren --ELM715206727-24759-0_ Content-Type: image/gif Content-Disposition: attachment; filename=ufsdiagram.gif Content-Description: ufsdiagram.gif Content-Transfer-Encoding: base64 R0lGODdhhAGqAYAAAAAAAP///ywAAAAAhAGqAQAC/oyPqcvtD6OctNqLs968+w+GEECWBnCQTMmi iqqeqWvFacAitG3K4g8MCofEoqS1mzl4NCVPebH5cj5c0yQ1arfcrpe4czGX4lXT2smWn6cr9QuP y+f0BayHfKGk+XvsT5Wnc1aGhgM1c1a3yNjoyBEGlWXVY4gG6CR215agNgWDmPg4SlpqyolqOPmH uGnpeqnZSVj1plZ5mqu7a+Qmqcj3uifLOYY52FlFGXqIy/sMHY3hi7p6tRyb6ldMLFo9GxqmKE1e bs53fCvYp0ls252I50np7mx+j5+vv8/f7/8PMKDAgQQLGjyIMKHChQwbOnwIMcikiBQrEpxoMaPG /jR0MG78CHJEO3GAcrRQRsFjyJUsSWpDMkxSBpUsax4clwycsEhjDmmgaTMoQJzMVEXK9AsSUaFM 9y1N9WvYtWXyPABtijXaU0ut3uzsaXVr1rGnxFrTo8POURBXybptZBYYIVo6obIV+zavHLzottW1 h3dmYL2Ee6X80XZD4sKMgQz2+WGx0saUtzzWd6yyZrYNT27+DMmhZ9CkK1zmB7O06iMQBa1+/UKj ZNiMT9O+bdA27t1DefuOqPu38HvBhxuXVvy48l3J+3l+NxVZWq9HKzVfvhdkSbBn09K78TIm9nLX /93yNm6eeMhM7I3nVd65s/Yo7RZiBdX9e+ba/q3PhVzXFG3swYx++5UVknV6YKRePOEYeCAp8Q1V CID6NegNV1JFCN9GbLjG1SzV/ZXEgBzqMiFmgYwGnhkr0mXSSCciOGON/NmIYykp5sijVT3+yMiO QA55GJFGeiHkkUraQViSSzriJELbxTOSH/g9CZdeLn0Vo0xYLhLlTWjthNQ3X9YRZkHdgZVNNWme +cCbF8llIi7tYDMbnCHIOVB39FDzZ1F6WqYlnQGmt9agXPDZp6EFjmmXooY16YZf0mHjnaSE1oYY o5p6quaeoEo6qqYHllpYnqYuYaSqq+Z0pKuvAhgrqjXa+pmsiuJKmq5w8lqar1gCq5qwsc5q/uyQ xNKWmanL4sYiqbMumOyJz96WmrTTUlvtftcO1y12326LLbnm1neus+mSO+66vbo7bbvKciivcSdl +2eV9Sa0r3I9weITm7z1e9y/Gx5KcJ/witTedoCGWO7CccoDXaLhYpWwvenMBc/FTGVccD0Wdgyy eRI3wIZRwrzkW8kDV+wwSR5/fLK6Ne96s7Y56+nyzjT7/CvQZ/b8G9GyCa0TzANS3OJrRu+2ZcNO aNP0Zk9DO2bDMf17qWZXM2uoMVW5CStlX4OdtV9dkh1gqkh3HR5+ozWbqdtvR3qW1GyrZffdEJ+3 Miw0nY2m3w9aurQ4daNMeByNRyzqBI8j/ml42Wk8NvNFlT8y+aSbQ9n5EKGbOzpin5sC8NGnow7h Q6WnGy1Fr8Mee2ur5wKi7bcz17qUu0Mze5G/2xj88CYbrzBqyGslFcz6Irc88AZryDLw0Xc4PWAP 4379jVon3nXmpncPn8xbaghy8TdnS/fYkepIPu7ryEINOh3Gz3tS078vIf7lJ/48AD5Dff6DXgGX Q8ADDlCB/mJgAx1oLwiCS4KjSCCBKAgXGYEvXyZCF5p6h8FFOegrU3tFBb0SQseljUptUsUJxZfC I4SNJ+6j2wdhGEORpO1ga1MZ6BKYMz89Z4M+zGAOO+KoMn1nb0ECYhCTWMRNCKxwR0Ti/iAQF6gO erCKsusUFxMUuS+KcYxkLKMZORKqM1KOc+6BiWvmh0I17umFgPMhwLqBQzLWSx0ri0US8yjGPcql Lw4LnxPdJS8G+adiD5Lj+Cq4gg62r1mA/GK7SlQ9TNRve45E4w+xsJ6N9XGKnQzNJ9X2IootEoSl NE0rOfXKJsVSlrPMyyFrKYJb4pIzuyQLwXQZv35NaYPsSFkvf8K9pcUtE8E4JjJRt0Lw2a9qznSl jmbIzP8IqpoREOQO8WQnTnKzm6yD1BAxNc1xCu+EkFIimyo5Rm+2LTPvBOa69kVITBHRFuqsQTLD 2E/JoQigAWVNQVtyUIQmFIwL1U5D/h16joc6hjgSfSQ57Lm6q2H0dBqtaC4p6lFekiekIr0oSSMD 0pOacqQqXalJW6qYlMJ0GjKdqT8jalOa4jSnN2UpT63p058KdKdCNWhQizqCmiKVVURdKlOP6tRI NjWqTJoqVS2nlas+9aVarSpUu7rFG4EVq9YbK1kXaNbFZTWt1CwrW2m11rd29K1wdStb5ypXpY4V r3fVK1j5mlbAmlWwe/VrVwn7V8NqFbGHVexVGbtYx1IVso+VbFQpO1nLOhWzl9XsUjm7Wc8iFbSf FW1RSTta0woVtadV7U9Zu1rX8hS2r5VtTmk7W9vaFLe31e1Mebtb38IUuL8VbkuJ/jtc46oUucdV 7kmZu1znkhS6Ia2dWAcbx/vdlZWQlCs8P+rdp210c9ztrnetmlj0Nla9dEVre9n73oHG96vrha86 PWKlVcZsYkIswng/pcjqrCdgiTKDOf0r0QHfIHt+gljbHmzRg8LjEyzMYn6ekjdVgjfBRNHa+dJp 4KTRcI4LxVe+RHbFC594wna07kwaamL20U86IObbgushpP8C2D4CHmWBbdwmrpUUxgeLiio9zLB7 3WmJQ56ve51sVyhrV8pTprJ8rXxdLNOos725rAazODeTgCmzyiQhNxTUES7T+MNFDuumRovNMvtR nF3QscTWlN8NhTnNn3XUc1BI/so6bxaKIVrFNkXY53YWesk/XmOiHRROjkUnO2q+CxUrfbkxa/nK m4YmXak7XelWV9QeBfWo7YvpuPYV1aFldWldnVpYt1bWsaV1bW2dW1z3VtfB5XVxfZ1cYDdX2NEl 9nNJXVFTlxrZCWb2Q5WdbGfDWNolpnZCod1sY4da26emb325umpvR5bbyyZ3tM2dbXFXFt3PtraE 3V1QbLeb3dOmd7XtfW14B1Te9VY3mf2d6igPVt/95Pe9Ad5qhL9a4bFGTnbH7fDy3vqiEs81xe18 N/F+t5oax7jQXCy/7VY8SJ8euaZF3mnWeZzIKydyyj398v7FfDwtT2EcGXni/iuC8uEzr/AImdzi 6TS65xCuY4u1yT+iv8/oYfYP3M5tRSBfmDruczAG3RiFN/6Z50nXqdTRh7c71hxqQ9dhCwl8aJNL Fa5MdwcyapxDUPyEfg2eiILn3sO2701wYyc7l5aoNAuDPSeAG0wx5ZxKJHMwnu+QgRTFo/V6Mk5E ff94KM03Px6TjPLz2fh9/UyfNY9MxTrvfOWBVvc13IfuSem6Jrm+WNOPMPEBXPzksaBFpet+9zw6 fcG/vPVhMq4vKUY8lKPGZsFzi8JoB7rvdxZnJsOdb3rro5tjH03p0xkc1Ze8HMeF5+ZZ6ir0dDrp zyh8fa6yrTUA/ZEzhfVaayT//GaUGfNxPOlpELqOmPTq+qvXdUeEKGZmfXVlGlDEfy7GDioDYp6X cQPYfRaTHPkUaaXXYU1XfMaHftHXePT3YtKjRoa2TABodT2FIs/3MrDyfwXogIdVKaDEgA/Tgi4o QLkXaf2HAQUAADs= --ELM715206727-24759-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message