From owner-freebsd-hackers Sun Jan 30 7:23:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.svr.pol.co.uk (mail2.svr.pol.co.uk [195.92.193.210]) by hub.freebsd.org (Postfix) with ESMTP id B9AAD150DA; Sun, 30 Jan 2000 07:23:14 -0800 (PST) (envelope-from s.mitchell@computer.org) Received: from modem-54.powder-blue-tang.dialup.pol.co.uk ([62.137.51.54] helo=lungfish.freeserve.co.uk) by mail2.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 12Evpk-0004ON-00; Sun, 30 Jan 2000 15:00:13 +0000 Received: from goatsucker.org (orac.goatsucker.org [192.168.1.2]) by lungfish.freeserve.co.uk (8.8.8/8.8.8) with ESMTP id NAA00958; Sun, 30 Jan 2000 13:56:07 GMT (envelope-from scott) Received: (from scott@localhost) by goatsucker.org (8.9.2/8.9.3) id NAA01265; Sun, 30 Jan 2000 13:51:29 GMT (envelope-from scott) Date: Sun, 30 Jan 2000 13:51:29 +0000 From: Scott Mitchell To: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Cc: freebsd-xircom@lovett.com Subject: clk0 interrupt accounting weirdness ??? Message-ID: <20000130135129.F1158@lungfish.freeserve.co.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=liOOAslEiF7prFVr Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 3.1-RELEASE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Hi all, The attached thread (apologies for the volume of text, but it is all relevant) came up on freebsd-xircom last week. Jose Alcaide actually posted to -mobile on the same subject a week or so before, but got no response. We figure it's definitely nothing to do with the Xircom driver in particular and probably nothing to do with pccard, so I'm bouncing it to any interested kernel gurus. Essentially, the irq line to which clk0 interrupts are accounted (in the output from vmstat -i) changes when pccards are inserted/removed. The same effect has been seen with cards using the xe0 and ed0 drivers. Any ideas? Scott -- =========================================================================== Scott Mitchell | PGP Key ID |"If I can't have my coffee, I'm just Cambridge, England | 0x54B171B9 | like a dried up piece of roast goat" s.mitchell@computer.org | 0xAA775B8B | -- J. S. Bach. --liOOAslEiF7prFVr Content-Type: message/rfc822 Content-Transfer-Encoding: 8bit Return-Path: Received: from valis.goatsucker.org (valis.goatsucker.org [192.168.1.1]) by lungfish.freeserve.co.uk (8.8.8/8.8.8) with ESMTP id VAA01618 for ; Tue, 25 Jan 2000 21:13:36 GMT (envelope-from owner-freebsd-xircom@lovett.com) X-From_: owner-freebsd-xircom@lovett.com Tue Jan 25 16:13:07 2000 Envelope-to: scott@lungfish.freeserve.co.uk Delivery-date: Tue, 25 Jan 2000 16:13:07 +0000 Received: from pop.pol.net.uk by valis.goatsucker.org (fetchmail-4.3.8 POP3) for (multi-drop); Tue, 25 Jan 2000 21:13:36 GMT Received: from [130.88.200.94] (helo=probity.mcc.ac.uk) by mail8.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 12D8aU-0002GG-00 for scott@lungfish.freeserve.co.uk; Tue, 25 Jan 2000 16:13:02 +0000 Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) for scott@lungfish.freeserve.co.uk id 12D8aT-0005nB-00; Tue, 25 Jan 2000 16:13:01 +0000 Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) with ESMTP id QAA12355 for ; Tue, 25 Jan 2000 16:13:00 GMT (envelope-from owner-freebsd-xircom@lovett.com) Received: from [212.74.0.25] (helo=florence.pavilion.net) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) for scott@freebsd-uk.eu.org id 12D8aS-0005mf-00; Tue, 25 Jan 2000 16:13:00 +0000 Received: from gallia.lovett.com (gallia.lovett.com [207.126.105.195]) by florence.pavilion.net (8.9.3/8.8.8) with ESMTP id QAA90328 for ; Tue, 25 Jan 2000 16:07:56 GMT (envelope-from owner-freebsd-xircom@lovett.com) Received: from majordom by gallia.lovett.com with local (Exim 3.12 #1) id 12D8VJ-000EVN-00 for freebsd-xircom-outgoing@lovett.com; Tue, 25 Jan 2000 08:07:41 -0800 Received: from [158.227.6.43] (helo=polaris.we.lc.ehu.es) by gallia.lovett.com with esmtp (Exim 3.12 #1) id 12D8VE-000EVG-00 for freebsd-xircom@lovett.com; Tue, 25 Jan 2000 08:07:38 -0800 Received: from we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id RAA13434 for ; Tue, 25 Jan 2000 17:07:21 +0100 (MET) Message-ID: <388DCA3A.B4AA61B0@we.lc.ehu.es> Date: Tue, 25 Jan 2000 17:07:22 +0100 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: freebsd-xircom@lovett.com Subject: clk0 interrupts accounted to xe ??? Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by polaris.we.lc.ehu.es id RAA13434 Sender: owner-freebsd-xircom@lovett.com Precedence: bulk Reply-To: freebsd-xircom@lovett.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by lungfish.freeserve.co.uk id VAA01618 Hello, I have just purchased a Xircom RE-100BTX. It works fine, but I found something very strange. After booting the system (with no pccard inserted), "vmstat -i" shows: interrupt total rate clk0 irq0 718701 100 ... But, just after I insert the Xircom card and it is detected and enabled, another "vmstat -i" shows: interrupt total rate clk0 irq3 732248 110 (IRQ3 is the first available interrupt in my system, and it is assigned to the Xircom card by the pccardd daemon. I am running FreeBSD 3.4-RELEASE, no PAO.) After inserting the card, the clk0 interrupts are accounted to the interrupt level used by the Xircom card (I have tried other IRQ levels with the same result). The 100 interrupts/second generated by the timer are added to the interrupts generated by the Ethernet adapter. Since I don't have any other PCMCIA cards, I don't know whether this "problem" only happens with the xe driver or, on the contrary, it is a general problem of the FreeBSD's pccard driver. Did anybody find this same behavior? -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein --liOOAslEiF7prFVr Content-Type: message/rfc822 Return-Path: Received: from valis.goatsucker.org (valis.goatsucker.org [192.168.1.1]) by lungfish.freeserve.co.uk (8.8.8/8.8.8) with ESMTP id VAA01629 for ; Tue, 25 Jan 2000 21:13:37 GMT (envelope-from owner-freebsd-xircom@lovett.com) X-From_: owner-freebsd-xircom@lovett.com Tue Jan 25 16:36:46 2000 Envelope-to: scott@lungfish.freeserve.co.uk Delivery-date: Tue, 25 Jan 2000 16:36:46 +0000 Received: from pop.pol.net.uk by valis.goatsucker.org (fetchmail-4.3.8 POP3) for (multi-drop); Tue, 25 Jan 2000 21:13:37 GMT Received: from [130.88.200.93] (helo=serenity.mcc.ac.uk) by mail7.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 12D8xR-0005Vn-00 for scott@lungfish.freeserve.co.uk; Tue, 25 Jan 2000 16:36:45 +0000 Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) for scott@lungfish.freeserve.co.uk id 12D8xQ-0006SD-00; Tue, 25 Jan 2000 16:36:45 +0000 Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) with ESMTP id QAA12726 for ; Tue, 25 Jan 2000 16:36:44 GMT (envelope-from owner-freebsd-xircom@lovett.com) Received: from [212.74.0.25] (helo=florence.pavilion.net) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) for scott@freebsd-uk.eu.org id 12D8xP-0006S2-00; Tue, 25 Jan 2000 16:36:43 +0000 Received: from gallia.lovett.com (gallia.lovett.com [207.126.105.195]) by florence.pavilion.net (8.9.3/8.8.8) with ESMTP id QAA04592 for ; Tue, 25 Jan 2000 16:33:23 GMT (envelope-from owner-freebsd-xircom@lovett.com) Received: from majordom by gallia.lovett.com with local (Exim 3.12 #1) id 12D8tx-000EWl-00 for freebsd-xircom-outgoing@lovett.com; Tue, 25 Jan 2000 08:33:09 -0800 Received: from [194.178.168.50] (helo=smtppzh.pzh.nl) by gallia.lovett.com with smtp (Exim 3.12 #1) id 12D8tv-000EWf-00 for freebsd-xircom@lovett.com; Tue, 25 Jan 2000 08:33:08 -0800 Received: FROM smtp.pzh.nl BY smtppzh.pzh.nl ; Tue Jan 25 17:31:37 2000 0000 Received: from PZH40-1-Message_Server by smtp.pzh.nl with Novell_GroupWise; Tue, 25 Jan 2000 17:31:42 +0100 Message-Id: X-Mailer: Novell GroupWise 5.5.2 Date: Tue, 25 Jan 2000 17:31:08 +0100 From: "ROGIER MULHUIJZEN" To: , Subject: Re: clk0 interrupts accounted to xe ??? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Sender: owner-freebsd-xircom@lovett.com Precedence: bulk Reply-To: freebsd-xircom@lovett.com >After inserting the card, the clk0 interrupts are accounted to the >interrupt level used by the Xircom card (I have tried other IRQ levels >with the same result). The 100 interrupts/second generated by the >timer are added to the interrupts generated by the Ethernet adapter. >Since I don't have any other PCMCIA cards, I don't know whether this >"problem" only happens with the xe driver or, on the contrary, it is >a general problem of the FreeBSD's pccard driver. Hmmm.... taking a quick look at my 'vmstat -i' output I see the same thing: clk0 irq10 2667404 102 ----bunch of others deleted---- IRQ10 is the IRQ I hooked to my RealPort. I'll give the ed0 card I have at home a shot tonight. DocWilco --liOOAslEiF7prFVr Content-Type: message/rfc822 Return-Path: Received: from valis.goatsucker.org (valis.goatsucker.org [192.168.1.1]) by lungfish.freeserve.co.uk (8.8.8/8.8.8) with ESMTP id WAA01507 for ; Wed, 26 Jan 2000 22:14:15 GMT (envelope-from owner-freebsd-xircom@lovett.com) X-From_: owner-freebsd-xircom@lovett.com Wed Jan 26 22:06:38 2000 Envelope-to: scott@lungfish.freeserve.co.uk Delivery-date: Wed, 26 Jan 2000 22:06:38 +0000 Received: from pop.freeserve.net by valis.goatsucker.org (fetchmail-4.3.8 POP3) for (single-drop); Wed, 26 Jan 2000 22:14:15 GMT Received: from [130.88.200.94] (helo=probity.mcc.ac.uk) by mail13.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 12DaaC-0008LC-00 for scott@lungfish.freeserve.co.uk; Wed, 26 Jan 2000 22:06:36 +0000 Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) for scott@lungfish.freeserve.co.uk id 12DaaC-0004tB-00; Wed, 26 Jan 2000 22:06:36 +0000 Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) with ESMTP id WAA38206 for ; Wed, 26 Jan 2000 22:06:35 GMT (envelope-from owner-freebsd-xircom@lovett.com) Received: from [212.74.0.25] (helo=florence.pavilion.net) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) for scott@freebsd-uk.eu.org id 12DaaB-000PMx-00; Wed, 26 Jan 2000 22:06:35 +0000 Received: from gallia.lovett.com (gallia.lovett.com [207.126.105.195]) by florence.pavilion.net (8.9.3/8.8.8) with ESMTP id WAA51861 for ; Wed, 26 Jan 2000 22:04:36 GMT (envelope-from owner-freebsd-xircom@lovett.com) Received: from majordom by gallia.lovett.com with local (Exim 3.12 #1) id 12DaXv-000G4s-00 for freebsd-xircom-outgoing@lovett.com; Wed, 26 Jan 2000 14:04:15 -0800 Received: from [195.92.193.210] (helo=mail2.svr.pol.co.uk) by gallia.lovett.com with esmtp (Exim 3.12 #1) id 12DaXu-000G4m-00 for freebsd-xircom@lovett.com; Wed, 26 Jan 2000 14:04:14 -0800 Received: from modem-33.electric-blue-damsel.dialup.pol.co.uk ([62.137.5.33] helo=lungfish.freeserve.co.uk) by mail2.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 12DaXs-0004iL-00 for freebsd-xircom@lovett.com; Wed, 26 Jan 2000 22:04:12 +0000 Received: (from scott@localhost) by lungfish.freeserve.co.uk (8.8.8/8.8.8) id VAA00408; Wed, 26 Jan 2000 21:31:59 GMT (envelope-from scott) Message-ID: <20000126213159.55106@lungfish.freeserve.co.uk> Date: Wed, 26 Jan 2000 21:31:59 +0000 From: Scott Mitchell To: freebsd-xircom@lovett.com Subject: Re: clk0 interrupts accounted to xe ??? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from ROGIER MULHUIJZEN on Tue, Jan 25, 2000 at 05:31:08PM +0100 X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Sender: owner-freebsd-xircom@lovett.com Precedence: bulk Reply-To: freebsd-xircom@lovett.com On Tue, Jan 25, 2000 at 05:31:08PM +0100, ROGIER MULHUIJZEN wrote: > >After inserting the card, the clk0 interrupts are accounted to the > >interrupt level used by the Xircom card (I have tried other IRQ > levels > >with the same result). The 100 interrupts/second generated by the > >timer are added to the interrupts generated by the Ethernet adapter. > >Since I don't have any other PCMCIA cards, I don't know whether this > >"problem" only happens with the xe driver or, on the contrary, it is > >a general problem of the FreeBSD's pccard driver. > > Hmmm.... taking a quick look at my 'vmstat -i' output I see the same > thing: > > clk0 irq10 2667404 102 > ----bunch of others deleted---- > > IRQ10 is the IRQ I hooked to my RealPort. > > I'll give the ed0 card I have at home a shot tonight. Another data point: Script started on Wed Jan 26 21:18:22 2000 orac 78 ~> vmstat -i interrupt total rate clk0 irq3 23175 99 rtc0 irq8 29662 127 fdc0 irq6 1 0 wdc0 irq14 1934 8 atkbd0 irq1 468 2 psm0 irq12 9 0 Total 55249 238 [xe0 inserted here] orac 79 ~> vmstat -i interrupt total rate clk0 irq10 33303 100 rtc0 irq8 42600 127 fdc0 irq6 1 0 wdc0 irq14 2088 6 atkbd0 irq1 501 1 psm0 irq12 9 0 Total 78502 235 orac 80 ~> exit irq3 is where my pccard controller typically lives; irq10 is (of course) the line occupied by xe0. I'll be interested to see what happens with Rogier's ed0 (I should probably borrow a 3Com card from work and try the same thing) but I suspect this is a case of the generic pccard code being weird rather than anything specific to the xe0 driver. Our code doesn't do much with interrupts except handle them when they go off :-) All the setup stuff is done by pccardd before xe get a look in... Scott -- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" s.mitchell@computer.org | 0xAA775B8B | -- Anon --liOOAslEiF7prFVr Content-Type: message/rfc822 Return-Path: Received: from valis.goatsucker.org (valis.goatsucker.org [192.168.1.1]) by lungfish.freeserve.co.uk (8.8.8/8.8.8) with ESMTP id VAA00328 for ; Thu, 27 Jan 2000 21:08:13 GMT (envelope-from owner-freebsd-xircom@lovett.com) X-From_: owner-freebsd-xircom@lovett.com Wed Jan 26 22:54:23 2000 Envelope-to: scott@lungfish.freeserve.co.uk Delivery-date: Wed, 26 Jan 2000 22:54:23 +0000 Received: from pop.pol.net.uk by valis.goatsucker.org (fetchmail-4.3.8 POP3) for (multi-drop); Thu, 27 Jan 2000 21:08:13 GMT Received: from [130.88.200.94] (helo=probity.mcc.ac.uk) by mail8.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 12DbKR-0007qe-00 for scott@lungfish.freeserve.co.uk; Wed, 26 Jan 2000 22:54:23 +0000 Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) for scott@lungfish.freeserve.co.uk id 12DbKQ-0005wf-00; Wed, 26 Jan 2000 22:54:22 +0000 Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) with ESMTP id WAA38851 for ; Wed, 26 Jan 2000 22:54:22 GMT (envelope-from owner-freebsd-xircom@lovett.com) Received: from [212.74.0.25] (helo=florence.pavilion.net) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) for scott@freebsd-uk.eu.org id 12DbKP-0000Hz-00; Wed, 26 Jan 2000 22:54:21 +0000 Received: from gallia.lovett.com (gallia.lovett.com [207.126.105.195]) by florence.pavilion.net (8.9.3/8.8.8) with ESMTP id WAA57962 for ; Wed, 26 Jan 2000 22:52:17 GMT (envelope-from owner-freebsd-xircom@lovett.com) Received: from majordom by gallia.lovett.com with local (Exim 3.12 #1) id 12DbHx-000GA7-00 for freebsd-xircom-outgoing@lovett.com; Wed, 26 Jan 2000 14:51:49 -0800 Received: from [207.139.235.10] (helo=yossman.net ident=root) by gallia.lovett.com with esmtp (Exim 3.12 #1) id 12DbHw-000GA1-00 for freebsd-xircom@lovett.com; Wed, 26 Jan 2000 14:51:48 -0800 Received: from localhost (drwilco@localhost) by yossman.net (8.9.3/8.9.3) with ESMTP id SAA86008 for ; Wed, 26 Jan 2000 18:06:55 -0500 (EST) (envelope-from drwilco@drwilco.net) Date: Wed, 26 Jan 2000 18:06:55 -0500 (EST) From: drwilco X-Sender: drwilco@yossman.net To: freebsd-xircom@lovett.com Subject: Re: clk0 interrupts accounted to xe ??? In-Reply-To: <20000126213159.55106@lungfish.freeserve.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-xircom@lovett.com Precedence: bulk Reply-To: freebsd-xircom@lovett.com > irq3 is where my pccard controller typically lives; irq10 is (of course) > the line occupied by xe0. I'll be interested to see what happens with > Rogier's ed0 (I should probably borrow a 3Com card from work and try the > same thing) but I suspect this is a case of the generic pccard code being > weird rather than anything specific to the xe0 driver. Our code doesn't do > much with interrupts except handle them when they go off :-) All the setup > stuff is done by pccardd before xe get a look in... > Hmmmm, my dmesg output says: pcic: controller irq 3 And as you can see below clk0 is on irq 7... Anyways here is the log of vmstat -i's with my RealPort in xe0 mode, my ed0 card and my RealPort in sio mode: After a clean boot: interrupt total rate clk0 irq7 15771 100 rtc0 irq8 20182 128 wdc0 irq14 2826 18 fdc0 irq6 1 0 atkbd0 irq1 495 3 psm0 irq12 4503 28 ppc0 irq5 1 0 stray irq4 1 0 Total 43780 278 After insertion of my RealPort in xe0 mode: interrupt total rate clk0 irq10 23540 100 rtc0 irq8 30124 128 wdc0 irq14 2858 12 fdc0 irq6 1 0 atkbd0 irq1 708 3 psm0 irq12 8715 37 ppc0 irq5 1 0 stray irq4 1 0 Total 65948 280 After a ping -f of another host: interrupt total rate clk0 irq10 52835 144 rtc0 irq8 46783 128 wdc0 irq14 2906 7 fdc0 irq6 1 0 atkbd0 irq1 1084 2 psm0 irq12 11997 32 ppc0 irq5 1 0 stray irq4 1 0 Total 115608 316 After a reboot with RealPort inserted in sio mode: interrupt total rate clk0 irq7 15470 101 rtc0 irq8 19656 128 wdc0 irq14 2841 18 fdc0 irq6 1 0 atkbd0 irq1 425 2 psm0 irq12 2550 16 ppc0 irq5 1 0 stray irq4 1 0 Total 40945 267 After a ping -f over ppp: interrupt total rate clk0 irq7 23016 126 rtc0 irq8 23286 127 wdc0 irq14 2864 15 fdc0 irq6 1 0 atkbd0 irq1 563 3 psm0 irq12 2550 14 ppc0 irq5 1 0 stray irq4 1 0 Total 52282 287 Here is my pccard.conf entry for my RealPort: card "Xircom" "16-bit Ethernet + Modem 56" config 0x17 "sio1" 10 # config 0x27 "xe0" 10 insert echo Xircom CreditCard Modem inserted remove echo Xircom CreditCard Modem removed Note that the sio driver has irq 10 configured, but that it doesn't show up on the vmstat list, but that the rate gets skewed a LOT. (The ping -f generated a few interrupt-level buffer overflows) I think we can safely say that this is either something in vmstat, or in pccardd. Warner, what's your take on this? DocWilco (It's weird being called Rogier online =) ) --liOOAslEiF7prFVr Content-Type: message/rfc822 Content-Transfer-Encoding: 8bit Return-Path: Received: from valis.goatsucker.org (valis.goatsucker.org [192.168.1.1]) by lungfish.freeserve.co.uk (8.8.8/8.8.8) with ESMTP id VAA00526 for ; Thu, 27 Jan 2000 21:08:39 GMT (envelope-from owner-freebsd-xircom@lovett.com) X-From_: owner-freebsd-xircom@lovett.com Wed Jan 26 23:29:17 2000 Envelope-to: scott@lungfish.freeserve.co.uk Delivery-date: Wed, 26 Jan 2000 23:29:17 +0000 Received: from pop.pol.net.uk by valis.goatsucker.org (fetchmail-4.3.8 POP3) for (multi-drop); Thu, 27 Jan 2000 21:08:39 GMT Received: from [130.88.200.94] (helo=probity.mcc.ac.uk) by imailg3.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 12DbsD-0000Rk-00 for scott@lungfish.freeserve.co.uk; Wed, 26 Jan 2000 23:29:17 +0000 Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) for scott@lungfish.freeserve.co.uk id 12DbsD-0006Om-00; Wed, 26 Jan 2000 23:29:17 +0000 Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) with ESMTP id XAA39518 for ; Wed, 26 Jan 2000 23:29:16 GMT (envelope-from owner-freebsd-xircom@lovett.com) Received: from [212.74.0.25] (helo=florence.pavilion.net) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) for scott@freebsd-uk.eu.org id 12DbsC-0001Ia-00; Wed, 26 Jan 2000 23:29:16 +0000 Received: from gallia.lovett.com (gallia.lovett.com [207.126.105.195]) by florence.pavilion.net (8.9.3/8.8.8) with ESMTP id XAA62540 for ; Wed, 26 Jan 2000 23:27:22 GMT (envelope-from owner-freebsd-xircom@lovett.com) Received: from majordom by gallia.lovett.com with local (Exim 3.12 #1) id 12DbqB-000GCj-00 for freebsd-xircom-outgoing@lovett.com; Wed, 26 Jan 2000 15:27:11 -0800 Received: from [158.227.6.43] (helo=polaris.we.lc.ehu.es) by gallia.lovett.com with esmtp (Exim 3.12 #1) id 12DbqA-000GCd-00 for freebsd-xircom@lovett.com; Wed, 26 Jan 2000 15:27:10 -0800 Received: from we.lc.ehu.es (lxpx70.lx.ehu.es [158.227.99.70]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id AAA05691 for ; Thu, 27 Jan 2000 00:27:05 +0100 (MET) Message-ID: <388F82C7.B37CF139@we.lc.ehu.es> Date: Thu, 27 Jan 2000 00:27:03 +0100 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: freebsd-xircom@lovett.com Subject: Re: clk0 interrupts accounted to xe ??? References: Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by polaris.we.lc.ehu.es id AAA05691 Sender: owner-freebsd-xircom@lovett.com Precedence: bulk Reply-To: freebsd-xircom@lovett.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by lungfish.freeserve.co.uk id VAA00526 drwilco wrote: > [...] > > I think we can safely say that this is either something in vmstat, or in > pccardd. Warner, what's your take on this? > I absolutely agree. The problem is not in the xe driver. I have carefully examined the vmstat and pccard sources. Vmstat is innocent; it simply uses kvm_read(), so the interrupt accounting is messed up in the kernel memory. Pccardd has nothing to do with interrupt registration; this support is in the pccard driver. And with respect to pccard, the calls to register_intr() appear to be OK. Really, I have no idea of where is the problem. We need a kernel guru :-) This thread should be moved to -mobile, I think. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein --liOOAslEiF7prFVr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 30 9:16:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mtiwmhc09.worldnet.att.net (mtiwmhc09.worldnet.att.net [204.127.131.18]) by hub.freebsd.org (Postfix) with ESMTP id 37DEE15312 for ; Sun, 30 Jan 2000 09:16:25 -0800 (PST) (envelope-from hspio@worldnet.att.net) Received: from default ([12.77.203.107]) by mtiwmhc09.worldnet.att.net (InterMail v03.02.07.07 118-134) with ESMTP id <20000130171618.MGWF7433@default>; Sun, 30 Jan 2000 17:16:18 +0000 From: hspio@worldnet.att.net To: linux-admin@vger.rutgers.edu, cypherpunks@toad.com, hackers@FreeBSD.ORG, linux-admin@vger.rutgers.edu Date: Sun, 30 Jan 2000 12:16:50 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: DreamWeaver Crack 3.0 X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000130171618.MGWF7433@default> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey I know its not a cracking mailing list but does anybody have the Crack for Dreamweaver 3.0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 30 9:18:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mtiwmhc09.worldnet.att.net (mtiwmhc09.worldnet.att.net [204.127.131.18]) by hub.freebsd.org (Postfix) with ESMTP id 1C90414CA8 for ; Sun, 30 Jan 2000 09:18:27 -0800 (PST) (envelope-from hspio@worldnet.att.net) Received: from default ([12.77.203.107]) by mtiwmhc09.worldnet.att.net (InterMail v03.02.07.07 118-134) with ESMTP id <20000130171821.MHQR7433@default>; Sun, 30 Jan 2000 17:18:21 +0000 From: hspio@worldnet.att.net To: hackers@FreeBSD.ORG, linux-admin@vger.rutgers.edu, cypherpunks@toad.com Date: Sun, 30 Jan 2000 12:18:59 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: WebPage X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000130171821.MHQR7433@default> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Im looking for a SERVER that has the most web space available that is FREE can any Body HELP me out?? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 30 10:14:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.dyndns.org (adsl-216-62-157-60.dsl.hstntx.swbell.net [216.62.157.60]) by hub.freebsd.org (Postfix) with ESMTP id ADFED151EA for ; Sun, 30 Jan 2000 10:14:50 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id MAA28821; Sun, 30 Jan 2000 12:15:19 -0600 (CST) (envelope-from chris) Date: Sun, 30 Jan 2000 12:15:18 -0600 From: Chris Costello To: hspio@worldnet.att.net Cc: linux-admin@vger.rutgers.edu, hackers@FreeBSD.ORG Subject: Re: DreamWeaver Crack 3.0 Message-ID: <20000130121518.A28798@holly.calldei.com> Reply-To: chris@calldei.com References: <20000130171618.MGWF7433@default> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i In-Reply-To: <20000130171618.MGWF7433@default> X-URL: http://www.FreeBSD.org/~chris/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, January 30, 2000, hspio@worldnet.att.net wrote: > Hey I know its not a cracking mailing list but does anybody have > the Crack for Dreamweaver 3.0 I don't think freebsd-hackers or linux-admin are the right places to ask for this sort of thing. FreeBSD-hackers is for discussing programming on FreeBSD and for FreeBSD, and I'd imagine linux-admin is for discussing administration on Linux systems. -- |Chris Costello |A list is only as strong as its weakest link. - Don Knuth `---------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 31 1: 9: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6]) by hub.freebsd.org (Postfix) with ESMTP id 4117C14C10 for ; Mon, 31 Jan 2000 01:08:58 -0800 (PST) (envelope-from shigeru@iij.ad.jp) Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8]) by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id SAA28682; Mon, 31 Jan 2000 18:08:55 +0900 (JST) Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id SAA11923; Mon, 31 Jan 2000 18:08:54 +0900 (JST) Received: from mercury.iij.ad.jp (mercury.iij.ad.jp [192.168.4.89]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id SAA17036; Mon, 31 Jan 2000 18:08:54 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by mercury.iij.ad.jp (8.9.3/3.5W) with ESMTP id SAA28292; Mon, 31 Jan 2000 18:08:54 +0900 (JST) To: imp@village.org Cc: dfr@nlsystems.com, freebsd-hackers@FreeBSD.ORG Subject: Re: how to allocate an alined address for a device? In-Reply-To: Your message of "Sat, 29 Jan 2000 11:06:15 -0700" <200001291806.LAA07899@harmony.village.org> References: <200001291806.LAA07899@harmony.village.org> X-Mailer: Mew version 1.93b38 on XEmacs 21.2 (Shinjuku) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Mon_Jan_31_18:08:06_2000_827)--" Content-Transfer-Encoding: 7bit Message-Id: <20000131180852D.shigeru@iij.ad.jp> Date: Mon, 31 Jan 2000 18:08:52 +0900 From: YAMAMOTO Shigeru X-Dispatcher: imput version 991025(IM133) Lines: 230 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Mon_Jan_31_18:08:06_2000_827)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit >>>>> "Warner" == Warner Losh writes: : +u_int32_t : +rman_make_alignment_flags(int size) { : + int i; : + : + for (i = 0; i < 32 && size > 0x01; i ++) { : + size = (size >> 1); : + } : + : + if (i > 31) { : + i = 0; : + } : + : + return(RF_ALIGNMENT_LOG2(i)); : } I found my mistake in my patch. Following is right. u_int32_t rman_make_alignment_flags(int size) { int i; + int count; - for (i = 0; i < 32 && size > 0x01; i ++) { + for (i = 0, count = 0; i < 32 && size > 0x01; i ++) { + if (size & 0x01) { + count ++; + } size = (size >> 1); } + + if (count > 0) { + i ++; + } if (i > 31) { i = 0; } return(RF_ALIGNMENT_LOG2(i)); } Warner> This could more simply be stated as RF_ALIGNMENT_LOG2(ffs(size)). I Warner> don't think that it is really needed. Maybe, 'RF_ALIGNMENT_LOG2(ffs(size) - 1)'. It is very simple. But can we have an assumption that we never pass non 2^n to ffs(3)? I read 'man ffs(3)' and '@src/sys/libkern/ffs.c'. ffs(3), it seems me finding a first set bit from LSB. If we pass a non 2^n value to ffs(3), we have a wrong result. ex. ffs(4) = 3 --> 4 = 2^2 = (1 << 2) = (1 << (ffs(4) - 1)) ffs(6) = 2, ffs(8) = 4 --> 6 < 8 = 2^3 = (1 << 3) = (1 << (ffs(8) - 1)) = (1 << (ffs(6) + 1)) != (1 << (ffs(6) - 1)) = (1 << (2 - 1)) = 2 ffs(63) = 1, ffs(64) = 7 --> 63 < 64 = 2^6 = (1 << 6) = (1 << (ffs(64) - 1)) = (1 << (ffs(63) + 5)) != (1 << (ffs(63) - 1)) = (1 << (1 - 1)) = 1 Warner> : +#define RF_ALIGNMENT_LOG2(x) ((x) << RF_ALIGNMENT_SHIFT) Warner> You might want to add: Warner> #define RF_ALIGNMENT(x) (((x) & RF_ALIGNMENT_MASK) >> RF_ALIGNMENT_SHIFT) I add it. I send my new patch and ffs(3) test program. Thanks, ------- YAMAMOTO Shigeru Internet Initiative Japan Inc. Network Engineering Div. ----Next_Part(Mon_Jan_31_18:08:06_2000_827)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=align3.diff --- kern/subr_rman.c.org Tue Nov 16 08:28:57 1999 +++ kern/subr_rman.c Sun Jan 30 23:55:28 2000 @@ -227,7 +227,19 @@ continue; } rstart = max(s->r_start, start); - rend = min(s->r_end, max(start + count, end)); + if (flags & RF_ALIGNMENT_MASK) { + /* need to align an address */ + u_long aligned_rstart; + u_long alignment_size; + + alignment_size = (1u << RF_ALIGNMENT(flags)); + aligned_rstart = (rstart & (~alignment_size + 1u)); + if ((rstart & (~(~alignment_size + 1u))) != 0) { + aligned_rstart += alignment_size; + } + rstart = aligned_rstart; + } + rend = min(s->r_end, max(max(start + count, end), rstart + count)); #ifdef RMAN_DEBUG printf("truncated region: [%#lx, %#lx]; size %#lx (requested %#lx)\n", rstart, rend, (rend - rstart + 1), count); @@ -608,4 +620,27 @@ rv = int_rman_release_resource(rm, r); simple_unlock(rm->rm_slock); return (rv); +} + +u_int32_t +rman_make_alignment_flags(int size) { + int i; + int count; + + for (i = 0, count = 0; i < 32 && size > 0x01; i ++) { + if (size & 0x01) { + count ++; + } + size = (size >> 1); + } + + if (count > 0) { + i ++; + } + + if (i > 31) { + i = 0; + } + + return(RF_ALIGNMENT_LOG2(i)); } --- sys/rman.h.org Mon Jan 10 08:48:52 2000 +++ sys/rman.h Sun Jan 30 22:43:19 2000 @@ -64,7 +64,12 @@ #define RF_WANTED 0x0010 /* somebody is waiting for this resource */ #define RF_FIRSTSHARE 0x0020 /* first in sharing list */ -#define RF_PCCARD_ATTR 0x10000 /* PCCARD attribute memory */ +#define RF_PCCARD_ATTR 0x10000 /* PCCARD attribute memory */ + +#define RF_ALIGNMENT_SHIFT 10 /* alignment size bit starts bit 10 */ +#define RF_ALIGNMENT_MASK (0x003F << RF_ALIGNMENT_SHIFT) /* resource address alignemnt size bit mask */ +#define RF_ALIGNMENT_LOG2(x) ((x) << RF_ALIGNMENT_SHIFT) +#define RF_ALIGNMENT(x) (((x) & RF_ALIGNMENT_MASK) >> RF_ALIGNMENT_SHIFT) enum rman_type { RMAN_UNINIT = 0, RMAN_GAUGE, RMAN_ARRAY }; @@ -91,6 +96,8 @@ struct resource *rman_reserve_resource(struct rman *rm, u_long start, u_long end, u_long count, u_int flags, struct device *dev); + +extern u_int32_t rman_make_alignment_flags __P((int size)); #define rman_get_start(r) ((r)->r_start) #define rman_get_end(r) ((r)->r_end) ----Next_Part(Mon_Jan_31_18:08:06_2000_827)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=ffs.test.c #include #include rman_make_alignment_flags(int size) { int i; int count; for (i = 0, count = 0; i < 32 && size > 0x01; i ++) { if (size & 0x01) { count ++; } size = (size >> 1); } if (count > 0) { i ++; } if (i > 31) { i = 0; } return(i); } int main() { int i; int max; max = 100; for (i = 0; i < max; i ++) { printf("%d(0x%x):\n\tffs(%d)\t\t\t\t\t= %d\n", i, i, i, ffs(i)); printf("\t(1 << ffs(%d))\t\t\t\t= %d\n", i, (1 << ffs(i))); printf("\trman_make_alignment_flags(%d)\t\t= %d\n", i, rman_make_alignment_flags(i)); printf("\t(1 << rman_make_alignment_flags(%d))\t= %d\n", i, (1 << rman_make_alignment_flags(i))); } return(0); } ----Next_Part(Mon_Jan_31_18:08:06_2000_827)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 31 1:39:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ntua.gr (achilles.noc.ntua.gr [147.102.222.210]) by hub.freebsd.org (Postfix) with ESMTP id 20A9414DD0; Mon, 31 Jan 2000 01:39:49 -0800 (PST) (envelope-from past@netmode.ece.ntua.gr) Received: from netmode.ece.ntua.gr (dolly.netmode.ece.ntua.gr [147.102.13.10]) by ntua.gr (8.9.3/8.9.3) with ESMTP id LAA25259; Mon, 31 Jan 2000 11:39:42 +0200 (EET) Received: by netmode.ece.ntua.gr (Postfix, from userid 410) id 68B9C85C3; Mon, 31 Jan 2000 11:32:50 +0200 (EET) Date: Mon, 31 Jan 2000 11:32:49 +0200 From: Panagiotis Astithas To: Scott Mitchell Cc: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: clk0 interrupt accounting weirdness ??? Message-ID: <20000131113249.A23568@netmode.ece.ntua.gr> Reply-To: past@netmode.ntua.gr Mail-Followup-To: Scott Mitchell , freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: <20000130135129.F1158@lungfish.freeserve.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000130135129.F1158@lungfish.freeserve.co.uk>; from s.mitchell@computer.org on Sun, Jan 30, 2000 at 01:51:29PM +0000 X-Organizational-Unit: Network Management and Optimal Design Laboratory X-Organization: National Technical University of Athens, GREECE X-Work-Phone: +30-1-772-1-450 X-Work-FAX: +30-1-772-1-452 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 30, 2000 at 01:51:29PM +0000, Scott Mitchell wrote: > Essentially, the irq line to which clk0 interrupts are accounted (in the > output from vmstat -i) changes when pccards are inserted/removed. The same > effect has been seen with cards using the xe0 and ed0 drivers. FWIW, I also experience the same behavior: past@laptop$ vmstat -i interrupt total rate clk0 irq10 488774 100 ... past@laptop$ grep config /etc/pccard.conf config 0x0 "ed0" 10 ... I did mention it on this list a while ago. Perhaps we should move this to -stable? -past To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 31 2:51: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.prescient.co.za (mail.prescient.co.za [196.25.167.194]) by hub.freebsd.org (Postfix) with ESMTP id 4AC0214F8A for ; Mon, 31 Jan 2000 02:51:05 -0800 (PST) (envelope-from rip@pinetec.co.za) Received: from rip by mail.prescient.co.za with local (Exim 2.05 #1) id 12FEQB-00086F-00 for hackers@freebsd.org; Mon, 31 Jan 2000 12:51:03 +0200 Date: Mon, 31 Jan 2000 12:51:03 +0200 From: "R.I.Pienaar" To: hackers@freebsd.org Subject: make release + X Message-ID: <20000131125103.C23140@pinetec.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, I have been looking at the make release process, and have succesfully made a 3.4 snapshot release, my problem is it doesnt build/install any X stuff. how do i incorporate the XFree stuff into a freebsd release so that it is in acceptable format for sysinstall? -- R.I. Pienaar rip@pinetec.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 31 9:30: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id A6A7814EC9; Mon, 31 Jan 2000 09:30:01 -0800 (PST) (envelope-from T.Pagtzis@cs.ucl.ac.uk) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Mon, 31 Jan 2000 17:29:44 +0000 X-Mailer: exmh version 2.0.2 To: freebsd-net@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: NFS and removable disks Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Jan 2000 17:29:43 +0000 Message-ID: <1268.949339783@cs.ucl.ac.uk> From: Theo PAGTZIS Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I have the following problem. I have moved my disk with Fbsd 3.3 onto a diff machine with exactly the same network interface on both machines de0. However when I am trying to do mount on the machines NFS responds with NFS Portmap: RPC: Port mapper failure - RPC: Timed out When I ask people what does NFS depend on between client and servers I get the response of only IP address. So since the IP address is the same I am puzzled as to why there is port map failure. Could anyone enlighten on the reason of why this happens? BTW when I ping the ping works ok as well as telnet does Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 31 11:38:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.wplus.net (relay.wplus.net [195.131.52.179]) by hub.freebsd.org (Postfix) with ESMTP id BDB5214DBE for ; Mon, 31 Jan 2000 11:38:31 -0800 (PST) (envelope-from dms@woland.wplus.net) Received: from woland.wplus.net (woland.wplus.net [195.131.0.39]) by relay.wplus.net (8.9.1/8.9.1/wplus.2) with ESMTP id WAA53992; Mon, 31 Jan 2000 22:33:32 +0300 (MSK) X-Real-To: freebsd-hackers@FreeBSD.ORG Received: (from dms@localhost) by woland.wplus.net (8.9.3/8.9.1/wplus.2) id WAA36070; Mon, 31 Jan 2000 22:38:00 +0300 (MSK) Message-ID: X-Mailer: XFMail 1.4.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 31 Jan 2000 22:38:00 +0300 (MSK) From: Dmitry Samersoff To: skafte@worldgate.com, freebsd-hackers@FreeBSD.ORG Subject: HP Type C1559 problems Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have problem with HP SureStore 24x6 I can read(write) only from one tape from catridge Could anybody send me ether shell or C (preferable) sequence need to read tapes one by one? i.e something like: cat /dev/rsa0 camcontrol cmd -n rsa0.ctl -c "1B 00 00" cat /dev/rsa0 Thank you! -- Dmitry Samersoff, dms@wplus.net, ICQ:3161705 http://devnull.wplus.net * There will come soft rains ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 31 12:35:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id F2F8314C05; Mon, 31 Jan 2000 12:35:05 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 31 Jan 2000 20:35:03 +0000 (GMT) Date: Mon, 31 Jan 2000 20:35:02 +0000 From: David Malone To: Theo PAGTZIS Cc: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: NFS and removable disks Message-ID: <20000131203502.A61674@walton.maths.tcd.ie> References: <1268.949339783@cs.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <1268.949339783@cs.ucl.ac.uk>; from T.Pagtzis@cs.ucl.ac.uk on Mon, Jan 31, 2000 at 05:29:43PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 31, 2000 at 05:29:43PM +0000, Theo PAGTZIS wrote: > NFS Portmap: RPC: Port mapper failure - RPC: Timed out Check you've enableld the portmapper on the server in rc.conf. (Or check it's running "ps -auxwww | fgrep portmap"). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 31 12:44:40 2000 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 4ECBA15361 for ; Mon, 31 Jan 2000 12:44:28 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id OAA20659; Mon, 31 Jan 2000 14:43:57 -0600 (CST) (envelope-from dan) Date: Mon, 31 Jan 2000 14:43:56 -0600 From: Dan Nelson To: Dmitry Samersoff Cc: skafte@worldgate.com, freebsd-hackers@FreeBSD.ORG Subject: Re: HP Type C1559 problems Message-ID: <20000131144356.A20190@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from "Dmitry Samersoff" on Mon Jan 31 22:38:00 GMT 2000 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jan 31), Dmitry Samersoff said: > I have problem with HP SureStore 24x6 I can read(write) only from one > tape from catridge > > Could anybody send me ether shell or C (preferable) sequence need to > read tapes one by one? > > i.e something like: > cat /dev/rsa0 > camcontrol cmd -n rsa0.ctl -c "1B 00 00" You'll probably want to check out the "mt" and "chio" commands instead of sending raw SCSI commands :) "mt rewoffl" will rewind and eject a tape. The chio command manages autoloaders. "man mtio" for the C tape interface, and "man ch" for the C autoloader interface. > cat /dev/rsa0 -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 31 15: 2:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from surf.iae.nl (surf.IAE.nl [194.151.66.2]) by hub.freebsd.org (Postfix) with ESMTP id 4761A14D5A for ; Mon, 31 Jan 2000 15:02:22 -0800 (PST) (envelope-from wjw@iae.nl) Received: by surf.iae.nl (Postfix, from userid 74) id 7328CBFD1D; Tue, 1 Feb 2000 00:02:20 +0100 (CET) Subject: Bad memory suspected To: hackers@freebsd.org Date: Tue, 1 Feb 2000 00:02:20 +0100 (CET) Reply-To: wjw@IAE.nl X-NCC-RegID: nl.iae X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1726 Message-Id: <20000131230220.7328CBFD1D@surf.iae.nl> From: wjw@iae.nl (Willem Jan Withagen) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Being probably bitten again by some bad memory, I'm considering applying some of my old (VLSI) testingskills to this. However..... I'm in dire need of some hints, some because I haven't kept up with the intimate details of Intel hardware, nor do I know how to get a lineair memory space for all the fysical memory available in the system. The starting problems are: 1) I'd like to do this als a loadable kernel module, so one would load this module on the boot-prompt and let it eat away CPU time until it is rebooted. Now is there a module example which I can use to get me an easy setup for plugging inthe memory-test modules. Starting with simple things like "walking 0 and 1's", but ending up with O(n^2) tests to check for dependancies on surrounding values 2) Cache is a friend and a fiend in this: It helps fast execution of the code, but prevents data really getting to the silicon. So all experience in this is welcomed. Bluntly I can disable all caching (which would be nice for starters), but once we get to the more complex testingpatterns CPU-cycles do start to count. 3) PC memory layouts used to be a major art just by itself in the old days when we still used DIP 4116's, how is that in the current time with SIMM, DIMM, RAMBUS, PCI-bridges, ECC, ..... Any pointers to nightly reading material?? Thanx, --Willem Jan I once had a TRS-80 test run for 3 days, before it gave in, but then the error was reproducable and pinpointed the actual chip to be replaced. Which did fix the problem. -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 9.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 31 15:24: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.wplus.net (relay.wplus.net [195.131.52.179]) by hub.freebsd.org (Postfix) with ESMTP id 30E0315328 for ; Mon, 31 Jan 2000 15:24:02 -0800 (PST) (envelope-from dms@wplus.net) X-Real-To: freebsd-hackers@FreeBSD.ORG Received: from wplus.net (ppdms.dialup.wplus.net [195.131.52.71]) by relay.wplus.net (8.9.1/8.9.1/wplus.2) with ESMTP id CAA50453; Tue, 1 Feb 2000 02:18:45 +0300 (MSK) Message-ID: <3896191B.5F131A07@wplus.net> Date: Tue, 01 Feb 2000 02:22:03 +0300 From: Dmitry Samersoff X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Dan Nelson Cc: skafte@worldgate.com, freebsd-hackers@FreeBSD.ORG Subject: Re: HP Type C1559 problems References: <20000131144356.A20190@dan.emsphone.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Nelson wrote: > > In the last episode (Jan 31), Dmitry Samersoff said: > > I have problem with HP SureStore 24x6 I can read(write) only from one > > tape from catridge > > > > Could anybody send me ether shell or C (preferable) sequence need to > > read tapes one by one? > > > > i.e something like: > > cat /dev/rsa0 > > camcontrol cmd -n rsa0.ctl -c "1B 00 00" > > You'll probably want to check out the "mt" and "chio" commands instead > of sending raw SCSI commands :) "mt rewoffl" will rewind and eject a > tape. The chio command manages autoloaders. "man mtio" for the C tape > interface, and "man ch" for the C autoloader interface. I'm not so lazy as you belive ;-)) I tried all above before going to camcontrol. mt can rewind, erase end so on current tape, but can't change current slot number. chio report error for every comand except "chio status" . I find now (after lots of experiments) that sending raw SCSI command helps me. Right command causing changer to load next tape looks like: camcontrol stop -n sa -t 100 -v camcontrol cmd -n sa -t 100 -v -c "1B 00 00 00 00 00" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 31 15:27:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vitoria.ddsecurity.com.br (vitoria.ddsecurity.com.br [200.18.130.93]) by hub.freebsd.org (Postfix) with SMTP id D270D14FF3 for ; Mon, 31 Jan 2000 15:27:27 -0800 (PST) (envelope-from grios@ddsecurity.com.br) Received: (qmail 51644 invoked from network); 31 Jan 2000 23:25:25 -0000 Received: from modem00.tdnet.com.br (HELO ddsecurity.com.br) (200.236.148.100) by vitoria.ddsecurity.com.br with SMTP; 31 Jan 2000 23:25:25 -0000 Message-ID: <3895FDC8.42AE03BA@ddsecurity.com.br> Date: Mon, 31 Jan 2000 21:25:28 +0000 From: Gustavo V G C Rios X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: video board Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a video board which is hanging my FreeBSD BOX (Virge S3 GX/2, diamond stealth 3d 4000) I am considering changing it to a new one, which one do you suggest me? PS: I don't need a expensive one, all i need is a video board in the same level of quality than the current one (Obvious, not buggy). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 31 15:31:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 557B214D35 for ; Mon, 31 Jan 2000 15:31:29 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA09627; Mon, 31 Jan 2000 15:31:09 -0800 Date: Mon, 31 Jan 2000 15:31:05 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Dmitry Samersoff Cc: Dan Nelson , skafte@worldgate.com, freebsd-hackers@FreeBSD.ORG Subject: Re: HP Type C1559 problems In-Reply-To: <3896191B.5F131A07@wplus.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It sounds to me that you have this device strapped to be in 'stacker' mode- the command you're sending is the same as an 'mt offline' command- so it's loading the next tape in the changer. that means it won't show up as a changer on lun 1. I haven't seen one these beasts for 5-6 years- I don't recall what the switch settings are, but IIRC HP switch settings made no sense. On Tue, 1 Feb 2000, Dmitry Samersoff wrote: > Dan Nelson wrote: > > > > In the last episode (Jan 31), Dmitry Samersoff said: > > > I have problem with HP SureStore 24x6 I can read(write) only from one > > > tape from catridge > > > > > > Could anybody send me ether shell or C (preferable) sequence need to > > > read tapes one by one? > > > > > > i.e something like: > > > cat /dev/rsa0 > > > camcontrol cmd -n rsa0.ctl -c "1B 00 00" > > > > You'll probably want to check out the "mt" and "chio" commands instead > > of sending raw SCSI commands :) "mt rewoffl" will rewind and eject a > > tape. The chio command manages autoloaders. "man mtio" for the C tape > > interface, and "man ch" for the C autoloader interface. > > I'm not so lazy as you belive ;-)) I tried all above before going > to camcontrol. > mt can rewind, erase end so on current tape, but can't change > current slot number. > chio report error for every comand except "chio status" . > > I find now (after lots of experiments) that sending raw SCSI command > helps me. > Right command causing changer to load next tape looks like: > camcontrol stop -n sa -t 100 -v > camcontrol cmd -n sa -t 100 -v -c "1B 00 00 00 00 00" > > > 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 Jan 31 16: 5:14 2000 From owner-freebsd-hackers Mon Jan 31 22:53:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by builder.freebsd.org (Postfix) with ESMTP id C95F93D0C for ; Mon, 31 Jan 2000 22:53:47 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id WAA55853; Mon, 31 Jan 2000 22:53:34 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 31 Jan 2000 22:53:34 -0800 (PST) From: Doug White To: Willem Jan Withagen Cc: hackers@FreeBSD.ORG Subject: Re: Bad memory suspected In-Reply-To: <20000131230220.7328CBFD1D@surf.iae.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Feb 2000, Willem Jan Withagen wrote: > Being probably bitten again by some bad memory, I'm considering applying > some of my old (VLSI) testingskills to this. However..... > > I'm in dire need of some hints, some because I haven't kept up with the > intimate details of Intel hardware, nor do I know how to get a lineair > memory space for all the fysical memory available in the system. > > The starting problems are: > 1) I'd like to do this als a loadable kernel module, so one would load this > module on the boot-prompt and let it eat away CPU time until it is rebooted. I've found that multiple, parallel `make world's is a better tester than the pattern testers/"Burn-in" tools (ie AMIDiag) that are floating around. Compiling is a full-body workout -- when it hits a bad bit, it'll tank rather spectactularly. I have systems that pass repeated AMIDiag sweeps but couldn't build a kernel or survive a database churn to save their lives. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | 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 Jan 31 23: 7: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by builder.freebsd.org (Postfix) with ESMTP id C0FF63D1D for ; Mon, 31 Jan 2000 23:07:04 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA08456; Tue, 1 Feb 2000 10:38:36 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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: <20000131125103.C23140@pinetec.co.za> Date: Tue, 01 Feb 2000 10:38:35 +1030 (CST) From: "Daniel O'Connor" To: "R.I.Pienaar" Subject: RE: make release + X Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31-Jan-00 R.I.Pienaar wrote: > how do i incorporate the XFree stuff into a freebsd release so that > it is in > acceptable format for sysinstall? Download the binary packages from XFree86.org.. Someone was working on making the port produce tarballs that look like the XFree86 ones but I don't know how far that got. --- 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 Tue Feb 1 0:25:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by builder.freebsd.org (Postfix) with ESMTP id 82B5D3D42 for ; Tue, 1 Feb 2000 00:25:21 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id WAA45924; Mon, 31 Jan 2000 22:26:04 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200002010326.WAA45924@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dmitry Samersoff Cc: Dan Nelson , skafte@worldgate.com, freebsd-hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: HP Type C1559 problems References: <20000131144356.A20190@dan.emsphone.com> <3896191B.5F131A07@wplus.net> In-reply-to: Your message of "Tue, 01 Feb 2000 02:22:03 +0300." <3896191B.5F131A07@wplus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Jan 2000 22:26:04 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using a HP SureStore 24x6 too, and have no problems talking to it with chio. I suspect there's some screwy optioning nonsense for the tape motion stuff that's wrong. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 0:52:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by builder.freebsd.org (Postfix) with ESMTP id D29753D69 for ; Tue, 1 Feb 2000 00:52:42 -0800 (PST) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #35196) with ESMTP id <01JLE0MAQNN8000JD4@research.kpn.com> for freebsd-hackers@freebsd.org; Tue, 1 Feb 2000 09:52:28 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Tue, 01 Feb 2000 09:52:26 +0100 Content-return: allowed Date: Tue, 01 Feb 2000 09:52:19 +0100 From: "Koster, K.J." Subject: RE: Bad memory suspected To: 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522013137AD@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hoi Jan Willem, I would tend to agree with Doug White about a "make world" being a good memory test. However, I suspect Doug has the kind of system that will do a make world in a minute or two. You should run "make world" to verify your test results, but if you've just plopped in a new SIMM, making the world is just too heavy. > > Any pointers to nightly reading material?? > Since FreeBSD systems will start pumping out random signal 11's in the face of bad memory, try searching the -hardware and -questions list for that. I believe that someone actually wrote a signal 11 FAQ, but I don't have a pointer. There is a (Linux) program named memtest that will do just what you suggest. You can dd(1) the binary onto an unused 1 meg partition and have booteasy drop you in without even touching an OS. Kees Jan ============================================== You are only young once, but you can stay immature all your life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 2:57:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.wplus.net (relay.wplus.net [195.131.52.179]) by builder.freebsd.org (Postfix) with ESMTP id 3D1603D81 for ; Tue, 1 Feb 2000 02:57:17 -0800 (PST) Received: from woland.wplus.net (woland.wplus.net [195.131.0.39]) by relay.wplus.net (8.9.1/8.9.1/wplus.2) with ESMTP id NAA50383; Tue, 1 Feb 2000 13:51:53 +0300 (MSK) X-Real-To: skafte@worldgate.com Received: (from dms@localhost) by woland.wplus.net (8.9.3/8.9.1/wplus.2) id NAA37491; Tue, 1 Feb 2000 13:56:26 +0300 (MSK) Message-ID: X-Mailer: XFMail 1.4.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000131173841.A39580@dan.emsphone.com> Date: Tue, 01 Feb 2000 13:56:26 +0300 (MSK) From: Dmitry Samersoff To: Dan Nelson Subject: Re: HP Type C1559 problems Cc: freebsd-hackers@FreeBSD.ORG, skafte@worldgate.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31-Jan-2000 Dan Nelson wrote: > In the last episode (Feb 01), Dmitry Samersoff said: >> > In the last episode (Jan 31), Dmitry Samersoff said: >> > > I have problem with HP SureStore 24x6 I can read(write) only from >> > > one tape from catridge > > What does "chio status" return, and what does a "camcontrol devlist" > print? root@shade:~>chio status slot 0: slot 1: slot 2: slot 3: slot 4: slot 5: drive 0: root@shade:~>camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 4 lun 0 (pass1,da1) at scbus0 target 5 lun 0 (pass2,sa0) at scbus0 target 5 lun 1 (pass3,ch0) > >> I find now (after lots of experiments) that sending raw SCSI command >> helps me. Right command causing changer to load next tape looks like: >> camcontrol stop -n sa -t 100 -v >> camcontrol cmd -n sa -t 100 -v -c "1B 00 00 00 00 00" > > 1B is just an unload request, so your autoloader is probably in "dumb" 1B 00 00 - is unload request. Purpose of three extra bytes (00 xx 00) is unknown for me but 00 xx 01 it loads tape number x. 00 00 00 load next tape. (I find it in news, the same thing described in handbook's appendix for previouse model of HP changer) > or "gravity feed" mode, where an ejected tape causes the next tape to > be loaded automatically. chio is for smart autoloaders with random > access. A "mt rewoffl" should do the same thing as your camcontrol mt rewoffl cause changer to rewind current tape, then unload it. It doesn't load next tape. -- Dmitry Samersoff, dms@wplus.net, ICQ:3161705 http://devnull.wplus.net * There will come soft rains ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 6:30:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by builder.freebsd.org (Postfix) with ESMTP id 1E1223DEE for ; Tue, 1 Feb 2000 06:30:50 -0800 (PST) Received: from localhost (havoc@localhost) by phoenix.student.utwente.nl (8.9.3/8.9.3) with ESMTP id PAA00354 for ; Tue, 1 Feb 2000 15:30:37 +0100 (CET) (envelope-from havoc@cal30b054.student.utwente.nl) Date: Tue, 1 Feb 2000 15:30:36 +0100 (CET) From: Theo van Klaveren To: freebsd-hackers@freebsd.org Subject: Compiler error while compiling XFree86-3.9.17 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I received the following compiler error while compiling the XFree86-3.9.17 snapshot on a (very) fresh -CURRENT system: <-- begin cut'n'paste --> cc -c -O2 -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -I. -I.-I../../../include/fonts -I../mi -I../../../programs/Xserver/hw/xfree86/common -I../../../include/fonts -I../../.. -I../../../exports/include -DCSRG_BASED -DSHAPE -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPIXPRIV -DPANORAMIX -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DSMART_SCHEDULE -DNDEBUG -DFUNCPROTO=15 -DNARROWPROTO xf86vmode.c In file included from xf86vmode.c:41: ../include/extnsionst.h:91: warning: function declaration isn't a prototype ../include/extnsionst.h:100: warning: function declaration isn't a prototype ../include/extnsionst.h:106: warning: function declaration isn't a prototype xf86vmode.c: In function `ProcXF86VidModeGetMonitor': xf86vmode.c:1320: Unable to generate reloads for: (insn 300 298 302 (parallel[ (set (reg:SI 0 %eax) (fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0)))) (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) (const_int -34 [0xffffffde])) 0)) (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) (const_int -36 [0xffffffdc])) 0)) (clobber (mem:SI (plus:SI (reg:SI 6 %ebp) (const_int -40 [0xffffffd8])) 0)) (clobber (scratch:HI)) ] ) 145 {fix_truncsfsi2+1} (insn_list 293 (nil)) (expr_list:REG_DEAD (reg:SI 0 %eax) (expr_list:REG_UNUSED (scratch:HI) (nil)))) *** Error code 1 Stop in /usr/home/havoc/Build/xc/programs/Xserver/Xext. <-- end cut'n'paste --> I assume this is a compiler bug. Is there a workaround or a patch available for the system compiler or should I install the gcc-devel port (for which I probably don't have enough disk space, but oh well)? /^\ | Theo van Klaveren /^\\_//^\ | http://phoenix.student.utwente.nl ICQ #1353681 \_/-|-\_/ | / | This email was powered by FreeBSD `He's the mad scientist, and I'm his beautiful daughter.' - opening sentence from Heinlein's 'The number of the beast' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 8: 3:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by builder.freebsd.org (Postfix) with ESMTP id A5B463E1D; Tue, 1 Feb 2000 08:02:57 -0800 (PST) Received: from we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id RAA26049; Tue, 1 Feb 2000 17:01:23 +0100 (MET) Message-ID: <38970354.56AD3D1@we.lc.ehu.es> Date: Tue, 01 Feb 2000 17:01:24 +0100 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Scott Mitchell Cc: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, freebsd-xircom@lovett.com Subject: Re: clk0 interrupt accounting weirdness ??? References: <20000130135129.F1158@lungfish.freeserve.co.uk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scott Mitchell wrote: > > The attached thread (apologies for the volume of text, but it is all > relevant) came up on freebsd-xircom last week. Jose Alcaide actually > posted to -mobile on the same subject a week or so before, but got no > response. We figure it's definitely nothing to do with the Xircom driver > in particular and probably nothing to do with pccard, so I'm bouncing it to > any interested kernel gurus. > > Essentially, the irq line to which clk0 interrupts are accounted (in the > output from vmstat -i) changes when pccards are inserted/removed. The same > effect has been seen with cards using the xe0 and ed0 drivers. > After searching __again__ (and deeper) the mail list archives, I found that this problem is old. Very, very old. Of all messages I found related to this problem, the more interesting (and "recent": 1998-11-29) ones are: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=43676+50452+/usr/local/www/db/text/1998/freebsd-mobile/19981129.freebsd-mobile and its follow up by Nate Williams: http://www.freebsd.org/cgi/getmsg.cgi?fetch=50452+0+/usr/local/www/db/text/1998/freebsd-mobile/19981129.freebsd-mobile Here is an excerpt: ------------- > > - pccard interrupts doesn't seem to get initialized correctly for statistics > > output (vmstat -i). After I insert a pccard, all of its interrupts get > > accounted for the clock interrupt, with the irq line of the clock interrupt > > changing to the one for the PCCard. > > This is a 'known bug', and requires a re-write of the way PCCARD probing > is done to fix it. (This rewrite would also fix a number of other bugs > as well, but there is no one interested in taking on the laptop issue to > completion.) ------------- Well, I read pccard.c and the calls to register_intr() -which I traced- look correct. I did not find anything bad with IRQ probing, but this does not mean that the problem does not exist :-) Maybe a more detailed explanation by a kernel guru ;-) could help some of us to solve the problem. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 9:25:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by builder.freebsd.org (Postfix) with ESMTP id 1D04A3EA2 for ; Tue, 1 Feb 2000 09:25:39 -0800 (PST) Received: by norn.ca.eu.org (Postfix, from userid 1000) id F2E9216E0; Tue, 1 Feb 2000 09:25:29 -0800 (PST) Date: Tue, 1 Feb 2000 09:25:29 -0800 From: Chris Piazza To: Theo van Klaveren Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Compiler error while compiling XFree86-3.9.17 Message-ID: <20000201092529.A55526@norn.ca.eu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from havoc@cal30b054.student.utwente.nl on Tue, Feb 01, 2000 at 03:30:36PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 01, 2000 at 03:30:36PM +0100, Theo van Klaveren wrote: > > I received the following compiler error while compiling the XFree86-3.9.17 > snapshot on a (very) fresh -CURRENT system: > > <-- begin cut'n'paste --> > <-- snip cut'n'paste --> ...errors... > > <-- end cut'n'paste --> > > I assume this is a compiler bug. Is there a workaround or a patch > available for the system compiler or should I install the gcc-devel port > (for which I probably don't have enough disk space, but oh well)? The workaround is to compile the file that's dying with no optimisations. It compiles fine without them... sorry I don't have a patch handy. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 9:27:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from galileo.poli.hu (polinet-gw.poli.hu [195.199.8.25]) by builder.freebsd.org (Postfix) with ESMTP id 6700F3E7C for ; Tue, 1 Feb 2000 09:27:07 -0800 (PST) Received: from dial-6.poli.hu ([195.199.8.22] helo=aquarius.poli.hu) by galileo.poli.hu with esmtp (Exim 3.12 #1) id 12Fh4Q-0000Es-00; Tue, 01 Feb 2000 18:26:31 +0100 Received: from mauzi (helo=localhost) by aquarius.poli.hu with local-esmtp (Exim 3.12 #1) id 12Fh2k-00004m-00; Tue, 01 Feb 2000 18:24:46 +0100 Date: Tue, 1 Feb 2000 18:24:46 +0100 (CET) From: Gergely EGERVARY Reply-To: mauzi@poli.hu To: Theo van Klaveren Cc: freebsd-hackers@freebsd.org Subject: Re: Compiler error while compiling XFree86-3.9.17 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I assume this is a compiler bug. Is there a workaround or a patch > available for the system compiler or should I install the gcc-devel port > (for which I probably don't have enough disk space, but oh well)? yes, it's a bug, and you can work around it by removing the CFLAG -O2 anyway, XFree86 3.9.16 worked fine for me. 3.9.17 eats up all of my CPU time even if it's idle, so I had to downgrade it to 3.3.6 what is this new int10h code? really want to do real-mode bios calls? hey' guys, is this what we all want? OK, it's not an XFree86 discussion forum, please don't reply to this here :) -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 10:54:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by builder.freebsd.org (Postfix) with ESMTP id 92B323EE6 for ; Tue, 1 Feb 2000 10:54:26 -0800 (PST) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id NAA89760 for ; Tue, 1 Feb 2000 13:54:17 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Tue, 1 Feb 2000 13:54:16 -0500 (EST) From: Chuck Robey To: FreeBSD Hackers List Subject: box seizing up Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was trying to take a box that was running an old version of BSDi and move it to FreeBSD current. My first try was with the first CD I could find, which was 3.2 (I have later ones, they're just deeper in the pile than I cared to look for). The box, after install, was kinda unstable, given to sudden lockups, and the driver for the DNET card with the AX8841 in it would lock right up when I tried it. On reboot, with the older unfixed fsck, it would take multiple reboots to recover from the lockups, so I shuttled (via floppy) a kernel compiled under current (with the dc0 driver) and /bin and /sbin to the new machine. Now, excepting network, it's stable as a rock, but when I try use the network card, it locks up about 1 second after the ifconfig. Let me give more details. The dmesg part that's pertinent: dc0: port 0x6100-0x617f mem 0xf0201000-0xf020107f irq 12 at device 19.0 on pci0 dc0: Ethernet address: 00:80:ad:41:4a:95 miibus0: on dc0 amphy0: on miibus0 amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto I added a little reformatting, my mailer bends lines. Anyhow, doing a ifconfig -a gets me an entry for the dc0, so I tried setting the inet and netmask. The next second, each and every time (I've done this 4 times) it locks up solid. Before I do this, kldstat shows only the kernel loaded, and my /modules comes from the same current as the kernel (I never run kernel and user out of sync anyhow), so an out-of-sync kld being loaded shouldn't, I think, cause a lockup. Anyone know what the dmesg line that reads "amphy0" means? I only have ONE network card in there, that's an absolute fact. The machine's pretty bare, just scsi, vga, and network card (the cdrom's scsi). One scsi disk, one floppy. And problems. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 13:27:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by builder.freebsd.org (Postfix) with ESMTP id 0F55E3F57 for ; Tue, 1 Feb 2000 13:27:09 -0800 (PST) Received: (from dave@localhost) by elvis.mu.org (8.9.1/8.9.1) id PAA06403 for freebsd-hackers@freebsd.org; Tue, 1 Feb 2000 15:27:36 -0600 (CST) (envelope-from dave) Date: Tue, 1 Feb 2000 15:27:36 -0600 From: Dave McKay To: freebsd-hackers@freebsd.org Subject: freebsd specific search? Message-ID: <20000201152736.A6155@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As you may or may not be aware, google.com has a linux specific search engine at http://www.google.com/linux. I have expressed interest in possibly creating a freebsd specific search engine. I need support from the BSD community for this. If this is something we might all enjoy and benefit from please send email to dave@google.com and CC comments@google.com expressing your interest. -- Dave McKay Network Engineer - Google Inc. dave@mu.org - dave@google.com I'm feeling lucky... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 14: 7:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from surf.iae.nl (surf.IAE.nl [194.151.66.2]) by builder.freebsd.org (Postfix) with ESMTP id 912C93F69 for ; Tue, 1 Feb 2000 14:07:37 -0800 (PST) Received: by surf.iae.nl (Postfix, from userid 74) id 0E03CBFD60; Tue, 1 Feb 2000 23:07:29 +0100 (CET) To: hackers@freebsd.org Subject: Re: Bad memory suspected X-Newsgroups: list.freebsd.hackers In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522013137AD@l04.research.kpn.com> Organization: Internet Access Eindhoven BV Cc: Message-Id: <20000201220729.0E03CBFD60@surf.iae.nl> Date: Tue, 1 Feb 2000 23:07:29 +0100 (CET) From: wjw@iae.nl (Willem Jan Withagen) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <59063B5B4D98D311BC0D0001FA7E4522013137AD@l04.research.kpn.com> you write: >Hoi Jan Willem, > >I would tend to agree with Doug White about a "make world" being a good >memory test. However, I suspect Doug has the kind of system that will do a >make world in a minute or two. I too agree with Doug. It is what causes me to ask this question. ;-) make -j 4 buildworld keeps me getting crashes. Even during making the temp-tools. Now I've already replaced the memory once: 4*16M out, in 4*32M, but the crashingis still there. I've even set the timing to it's lowest, but still no go. I could go out an buy more new parts, but this is one of the cases to get to know FreeBSD again a little better. Memory testing skills are a leftover from a previous life. Heck, i've even help design a state-machine to test embeded RAM on VLSI ;-) >You should run "make world" to verify your test results, but if you've just >plopped in a new SIMM, making the world is just too heavy. > >> >> Any pointers to nightly reading material?? >> >Since FreeBSD systems will start pumping out random signal 11's in the face >of bad memory, try searching the -hardware and -questions list for that. I >believe that someone actually wrote a signal 11 FAQ, but I don't have a >pointer. I'll go and see if I can find something like that. >There is a (Linux) program named memtest that will do just what you suggest. >You can dd(1) the binary onto an unused 1 meg partition and have booteasy >drop you in without even touching an OS. That's a nice idea a well, I think a module would learn me something more/new to do. But I'll also try and digout this program. Thanx, --WjW -- Internet Access Eindhoven BV., voice: +31-40-2 393 393, data: +31-40-2 606 606 P.O. 928, 5600 AX Eindhoven, The Netherlands Full Internet connectivity for only fl 9.95 a month. Call now, and login as 'new'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 14:12:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id 0C0863E07 for ; Tue, 1 Feb 2000 14:12:37 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id OAA18788; Tue, 1 Feb 2000 14:38:04 -0800 (PST) Date: Tue, 1 Feb 2000 14:38:03 -0800 From: Alfred Perlstein To: Dave McKay Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: freebsd specific search? Message-ID: <20000201143803.Z24609@fw.wintelcom.net> References: <20000201152736.A6155@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000201152736.A6155@elvis.mu.org>; from dave@mu.org on Tue, Feb 01, 2000 at 03:27:36PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dave McKay [000201 13:54] wrote: > As you may or may not be aware, google.com has a linux specific search engine at http://www.google.com/linux. I have expressed interest in possibly creating a freebsd specific search engine. I need support from the BSD community for this. If this is something we might all enjoy and benefit from please send email to dave@google.com and CC comments@google.com expressing your interest. Of course it would be great, things like Daemonnews, better indexing of the FAQ/handbook. All that good stuff. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 15: 2: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by builder.freebsd.org (Postfix) with ESMTP id 4C7E53F76 for ; Tue, 1 Feb 2000 15:02:05 -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 RAA22636; Tue, 1 Feb 2000 17:01:56 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Tue, 1 Feb 2000 17:01:55 -0600 (CST) From: Chris Dillon To: Willem Jan Withagen Cc: hackers@FreeBSD.ORG Subject: Re: Bad memory suspected In-Reply-To: <20000201220729.0E03CBFD60@surf.iae.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Feb 2000, Willem Jan Withagen wrote: > I too agree with Doug. It is what causes me to ask this question. > ;-) make -j 4 buildworld keeps me getting crashes. Even during > making the temp-tools. > > Now I've already replaced the memory once: 4*16M out, in 4*32M, > but the crashingis still there. I've even set the timing to it's > lowest, but still no go. > > I could go out an buy more new parts, but this is one of the cases > to get to know FreeBSD again a little better. Memory testing > skills are a leftover from a previous life. Heck, i've even help > design a state-machine to test embeded RAM on VLSI ;-) The last time I had a problem like this, it was because I put a P54C (Pentium-MMX) into a board only designed for the P53C (a.k.a standard Pentium), so the core and I/O voltages were not quite correct. I knew this could be a problem, but I tried it anyway, and it worked (mostly). No amount of memory replacement or tweaking fixed the occasional problem, even though that is exactly what the problem looked like. It worked fine 99.9% of the time, but at least once a day it would crash hard. When I popped in a regular old Pentium processor that I knew the board could support, it worked flawlessly for weeks. When I put the Pentium-MMX into a newer board that supported it, it worked flawlessly as well. So, other than memory, you should check out both your motherboard and CPU. Try underclocking the CPU and see if that fixes your problems. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( 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 Feb 1 15: 9:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by builder.freebsd.org (Postfix) with ESMTP id 78F3B3E71 for ; Tue, 1 Feb 2000 15:09:14 -0800 (PST) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id RAA29029; Tue, 1 Feb 2000 17:08:37 -0600 (CST) Date: Tue, 1 Feb 2000 17:08:37 -0600 From: "Matthew D. Fuller" To: Chris Dillon Cc: Willem Jan Withagen , hackers@FreeBSD.ORG Subject: Re: Bad memory suspected Message-ID: <20000201170836.B23708@futuresouth.com> References: <20000201220729.0E03CBFD60@surf.iae.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-OS: FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 01, 2000 at 05:01:55PM -0600, a little birdie told me that Chris Dillon remarked > > The last time I had a problem like this, it was because I put a P54C > (Pentium-MMX) into a board only designed for the P53C (a.k.a standard ITYM P55C on a P54C board. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 16: 9:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.15.210.246]) by builder.freebsd.org (Postfix) with ESMTP id 815623EC0 for ; Tue, 1 Feb 2000 16:09:40 -0800 (PST) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (Windmoon-Patched/8.9.3/8.9.3) with ESMTP id QAA01605 for ; Tue, 1 Feb 2000 16:23:58 -0800 (PST) Date: Tue, 1 Feb 2000 16:23:58 -0800 (PST) From: FengYue To: hackers@FreeBSD.ORG Subject: Re: Bad memory suspected In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If your CPU is not overclocked, then you should pay very good attention to the motherboard if replacing memory didn't solve the problem. That happened to me once. Spent many hours and finally it turned out to be the motherboard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 17:39:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by builder.freebsd.org (Postfix) with ESMTP id DB7323FAB for ; Tue, 1 Feb 2000 17:39:34 -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 TAA23477; Tue, 1 Feb 2000 19:39:24 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Tue, 1 Feb 2000 19:39:23 -0600 (CST) From: Chris Dillon To: "Matthew D. Fuller" Cc: Willem Jan Withagen , hackers@FreeBSD.ORG Subject: Re: Bad memory suspected In-Reply-To: <20000201170836.B23708@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Feb 2000, Matthew D. Fuller wrote: > On Tue, Feb 01, 2000 at 05:01:55PM -0600, a little birdie told me > that Chris Dillon remarked > > > > The last time I had a problem like this, it was because I put a P54C > > (Pentium-MMX) into a board only designed for the P53C (a.k.a standard > > ITYM P55C on a P54C board. Errr, yes. Computers aren't the only things that suffer from off-by-one problems. ;-> -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( 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 Feb 1 21:49:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web3302.mail.yahoo.com (web3302.mail.yahoo.com [204.71.201.25]) by builder.freebsd.org (Postfix) with SMTP id 5D9F93DCE for ; Tue, 1 Feb 2000 21:49:45 -0800 (PST) Message-ID: <20000202054939.4273.qmail@web3302.mail.yahoo.com> Received: from [24.234.80.35] by web3302.mail.yahoo.com; Tue, 01 Feb 2000 21:49:39 PST Date: Tue, 1 Feb 2000 21:49:39 -0800 (PST) From: Derek White Subject: Kernel modules To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey folks, I just wanted to know if anyone could point out a good online resource like a tutorial or developer guide that explains kernel module development under FreeBSD. I am new to FreeBSD coming from a Linux/BeOS background and am interested in playing around with it to maybe contribute back to the FreeBSD source tree. Maybe this is a dumb question but is developing kernel modules for FreeBSD the same as it is technically for Linux? Thanks, Derek __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.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 Feb 1 23:11:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by builder.freebsd.org (Postfix) with ESMTP id 5C4D03D70 for ; Tue, 1 Feb 2000 23:11:29 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA29195; Wed, 2 Feb 2000 02:11:23 -0500 Date: Wed, 2 Feb 2000 02:11:23 -0500 (EST) From: Mike Nowlin To: Willem Jan Withagen Cc: hackers@FreeBSD.ORG Subject: Re: Bad memory suspected In-Reply-To: <20000201220729.0E03CBFD60@surf.iae.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Since FreeBSD systems will start pumping out random signal 11's in the face > >of bad memory, try searching the -hardware and -questions list for that. I > >believe that someone actually wrote a signal 11 FAQ, but I don't have a > >pointer. > > I'll go and see if I can find something like that. > I believe that the Linux mini-HOWTO doc library has one as well -- it might be worth reading, as the info in it basically applies to FreeBSD as well, not to mention any other "good" OS..... --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 23:12:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by builder.freebsd.org (Postfix) with ESMTP id 35C193D37 for ; Tue, 1 Feb 2000 23:12:17 -0800 (PST) Received: from rina.r.dl.itc.u-tokyo.ac.jp (tanimura@localhost.r.dl.itc.u-tokyo.ac.jp [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-rina.r-0.1-11.01.2000) with ESMTP id QAA95808; Wed, 2 Feb 2000 16:12:09 +0900 (JST) Date: Wed, 02 Feb 2000 16:12:09 +0900 Message-ID: <14487.55497.261038.68187Y@rina.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: hackers@FreeBSD.org Subject: FreeBSD-specific extension of struct mtget breaks dump(8) from Solaris Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG rmt(8) returns the result of MTIOCGET filled into struct mtget in response to the 'S' command, issued by dump(8) of some certain OSs including Solaris. (FreeBSD's one seems to not issue the 'S' command) Due to the extention made to struct mtget in FreeBSD, remote dump from, eg Solaris to FreeBSD fails to establish rmt connection. Maybe we would have to provide something like struct mtget_org for compatibility with other OSs. Also, if we were to issue 'S' in our dump(8), some command extention may be required. (any plans?) Any comments? -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 23:30:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by builder.freebsd.org (Postfix) with ESMTP id 210913E6D for ; Tue, 1 Feb 2000 23:30:26 -0800 (PST) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id XAA14887; Tue, 1 Feb 2000 23:28:19 -0800 Date: Tue, 1 Feb 2000 23:28:17 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Seigo Tanimura Cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD-specific extension of struct mtget breaks dump(8) from Solaris In-Reply-To: <14487.55497.261038.68187Y@rina.r.dl.itc.u-tokyo.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > rmt(8) returns the result of MTIOCGET filled into struct mtget in > response to the 'S' command, issued by dump(8) of some certain OSs > including Solaris. (FreeBSD's one seems to not issue the 'S' command) > Due to the extention made to struct mtget in FreeBSD, remote dump > from, eg Solaris to FreeBSD fails to establish rmt connection. > > Maybe we would have to provide something like struct mtget_org for > compatibility with other OSs. Also, if we were to issue 'S' in our > dump(8), some command extention may be required. (any plans?) > > Any comments? Yes. This is definitely an issue. Didn't this come up before and was a PR filed that I somehow forgot to own? After all, I probably broke things. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 1 23:30:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by builder.freebsd.org (Postfix) with ESMTP id 21B933F35 for ; Tue, 1 Feb 2000 23:30:50 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA29340; Wed, 2 Feb 2000 02:30:30 -0500 Date: Wed, 2 Feb 2000 02:30:30 -0500 (EST) From: Mike Nowlin To: dave@google.com Cc: comments@google.com, freebsd-hackers@freebsd.org Subject: Re/Fwd: freebsd specific search In-Reply-To: <20000201152736.A6155@elvis.mu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As you may or may not be aware, google.com has a linux specific search > engine at http://www.google.com/linux. I have expressed interest in > possibly creating a freebsd specific search engine. I need support from > the BSD community for this. If this is something we might all enjoy and > benefit from please send email to dave@google.com and CC > comments@google.com expressing your interest. As an avid user of both Linux and FreeBSD, I would welcome such an addition to your web site. I generally use Linux as a desktop platform, but heavily rely on FreeBSD's emphasis on stability and functionality when it comes to mission-critical uses such as networking and database applications. As the CIO of a medical laboratory, it is critical that our systems have the highest availability rate possible. Over the last few years, I have replaced almost all of our Linux-based servers with FreeBSD, due to the quality-control measures that the FreeBSD development team have implemented. Thank you -- Mike Nowlin -- mike@argos.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 0:18:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by builder.freebsd.org (Postfix) with ESMTP id C70D43D10 for ; Wed, 2 Feb 2000 00:18:46 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id BAA40498; Wed, 2 Feb 2000 01:17:55 -0700 (MST) (envelope-from ken) Date: Wed, 2 Feb 2000 01:17:55 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Cc: Seigo Tanimura , hackers@FreeBSD.ORG Subject: Re: FreeBSD-specific extension of struct mtget breaks dump(8) from Solaris Message-ID: <20000202011755.A40287@panzer.kdm.org> References: <14487.55497.261038.68187Y@rina.r.dl.itc.u-tokyo.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mjacob@feral.com on Tue, Feb 01, 2000 at 11:28:17PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 01, 2000 at 23:28:17 -0800, Matthew Jacob wrote: > > > > rmt(8) returns the result of MTIOCGET filled into struct mtget in > > response to the 'S' command, issued by dump(8) of some certain OSs > > including Solaris. (FreeBSD's one seems to not issue the 'S' command) > > Due to the extention made to struct mtget in FreeBSD, remote dump > > from, eg Solaris to FreeBSD fails to establish rmt connection. > > > > Maybe we would have to provide something like struct mtget_org for > > compatibility with other OSs. Also, if we were to issue 'S' in our > > dump(8), some command extention may be required. (any plans?) > > > > Any comments? > > Yes. This is definitely an issue. Didn't this come up before and was a PR > filed that I somehow forgot to own? After all, I probably broke things. I wonder if this has been broken for a long time, likely by the FreeBSD-specific things in struct mtget. (They first show up in rev 1.2 of mtio.h, and were likely from the 386bsd days.) It would be nice if it worked between systems, though. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 0:30:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by builder.freebsd.org (Postfix) with ESMTP id 855F53DDA for ; Wed, 2 Feb 2000 00:30:48 -0800 (PST) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA15046; Wed, 2 Feb 2000 00:30:31 -0800 Date: Wed, 2 Feb 2000 00:30:29 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Seigo Tanimura , hackers@FreeBSD.ORG Subject: Re: FreeBSD-specific extension of struct mtget breaks dump(8) from Solaris In-Reply-To: <20000202011755.A40287@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Yes. This is definitely an issue. Didn't this come up before and was a PR > > filed that I somehow forgot to own? After all, I probably broke things. > > I wonder if this has been broken for a long time, likely by the > FreeBSD-specific things in struct mtget. (They first show up in rev 1.2 of > mtio.h, and were likely from the 386bsd days.) It would be nice if it > worked between systems, though. Yes, this falls under the "plays well with others" grade. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 0:38: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by builder.freebsd.org (Postfix) with ESMTP id DD4233F03 for ; Wed, 2 Feb 2000 00:37:40 -0800 (PST) Received: from rina.r.dl.itc.u-tokyo.ac.jp (tanimura@localhost.r.dl.itc.u-tokyo.ac.jp [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-rina.r-0.1-11.01.2000) with ESMTP id RAA98959; Wed, 2 Feb 2000 17:37:26 +0900 (JST) Date: Wed, 02 Feb 2000 17:37:26 +0900 Message-ID: <14487.60613.970438.81928B@rina.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: mjacob@feral.com, osela@tactline.co.il Cc: tanimura@r.dl.itc.u-tokyo.ac.jp, hackers@FreeBSD.ORG Subject: Re: FreeBSD-specific extension of struct mtget breaks dump(8) from Solaris In-Reply-To: In your message of "Tue, 1 Feb 2000 23:28:17 -0800 (PST)" References: <14487.55497.261038.68187Y@rina.r.dl.itc.u-tokyo.ac.jp> User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: multipart/mixed; boundary="Multipart_Wed_Feb__2_17:37:25_2000-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Wed_Feb__2_17:37:25_2000-1 Content-Type: text/plain; charset=US-ASCII [Added Oren Sela, the originator of the PR] On Tue, 1 Feb 2000 23:28:17 -0800 (PST), Matthew Jacob said: >> rmt(8) returns the result of MTIOCGET filled into struct mtget in >> response to the 'S' command, issued by dump(8) of some certain OSs >> including Solaris. (FreeBSD's one seems to not issue the 'S' command) >> Due to the extention made to struct mtget in FreeBSD, remote dump >> from, eg Solaris to FreeBSD fails to establish rmt connection. >> >> Maybe we would have to provide something like struct mtget_org for >> compatibility with other OSs. Also, if we were to issue 'S' in our >> dump(8), some command extention may be required. (any plans?) >> >> Any comments? Matthew> Yes. This is definitely an issue. Didn't this come up before and was a PR Matthew> filed that I somehow forgot to own? After all, I probably broke things. You mean this one? I saw exactly the same message. On Wed, 17 Nov 1999 05:50:13 -0800 (PST), osela@tactline.co.il said: >> Number: 14946 >> Category: i386 >> Synopsis: rmt - remote magtape protocol (snip) >> Description: osela> I want to use the rmt on bsd vs. solaris 2.7. osela> When I use ufsdump from the solaris machine to the BSD I get following output: osela> DUMP: Writing 32 Kilobyte records osela> DUMP: Date of this level 0 dump: Wed Nov 17 15:23:38 1999 osela> DUMP: Date of last level 0 dump: the epoch osela> DUMP: Dumping /dev/rdsk/c0t0d0s7 (hope:/export/home) to osela> alice:/dev/nrsa0. osela> DUMP: Mapping (Pass I) [regular files] osela> DUMP: Mapping (Pass II) [directories] osela> DUMP: Estimated 436 blocks (218KB). osela> DUMP: rmtstatus: expected response size 24, got 76 osela> DUMP: This means the remote rmt daemon is not compatible. osela> DUMP: Lost connection to remote host. osela> DUMP: Bad return code from dump: 1 osela> The rmt on Solaris is not compatible with the one on BSD. osela> I need a solution - can any one help :-> The following patch change mtget to mtget_org, and performs necessary conversion. --Multipart_Wed_Feb__2_17:37:25_2000-1 Content-Type: text/plain; type=patch; charset=US-ASCII Content-Disposition: attachment; filename="mtget.diff" Content-Transfer-Encoding: 7bit diff -urN --exclude=CVS src.org/sbin/dump/dumprmt.c src/sbin/dump/dumprmt.c --- src.org/sbin/dump/dumprmt.c Sat Aug 28 09:12:37 1999 +++ src/sbin/dump/dumprmt.c Wed Feb 2 17:08:54 2000 @@ -320,12 +320,28 @@ { register int i; register char *cp; +#if defined(__FreeBSD__) + struct mtget_org mtsorg; +#endif /* __FreeBSD__ */ if (rmtstate != TS_OPEN) return (NULL); rmtcall("status", "S\n"); +#if defined(__FreeBSD__) + for (i = 0, cp = (char *)&mtsorg; i < sizeof(mtsorg); i++) + *cp++ = rmtgetb(); + /* Convert the compatible struct into FreeBSD's one. */ + bzero(&mts, sizeof(mts)); + mts->mt_type = mtsorg->mt_type; + mts->mt_dsreg = mtsorg->mt_dsreg; + mts->mt_erreg = mtsorg->mt_erreg; + mts->mt_resid = mtsorg->mt_resid; + mts->mt_fileno = mtsorg->mt_fileno; + mts->mt_blkno = mtsorg->mt_blkno; +#else for (i = 0, cp = (char *)&mts; i < sizeof(mts); i++) *cp++ = rmtgetb(); +#endif /* __FreeBSD__ */ return (&mts); } diff -urN --exclude=CVS src.org/sys/sys/mtio.h src/sys/sys/mtio.h --- src.org/sys/sys/mtio.h Mon Jan 24 11:34:17 2000 +++ src/sys/sys/mtio.h Wed Feb 2 17:08:11 2000 @@ -136,6 +136,38 @@ u_int32_t mt_comp2; /* compression type for mode 2 */ u_int32_t mt_comp3; /* compression type for mode 3 */ /* end not yet implemented */ +#endif /* __FreeBSD__ */ + daddr_t mt_fileno; /* relative file number of current position */ + daddr_t mt_blkno; /* relative block number of current position */ +}; + +/* The original struct mtget for compatibility of rmt(8) with other OSs */ + +struct mtget_org { + short mt_type; /* type of magtape device */ +/* the following two registers are grossly device dependent */ + short mt_dsreg; /* ``drive status'' register */ + short mt_erreg; /* ``error'' register */ +/* end device-dependent registers */ + short mt_resid; /* residual count */ +#if notdef /* FreeBSD extention */ + daddr_t mt_blksiz; /* presently operating blocksize */ + daddr_t mt_density; /* presently operating density */ + u_int32_t mt_comp; /* presently operating compression */ + daddr_t mt_blksiz0; /* blocksize for mode 0 */ + daddr_t mt_blksiz1; /* blocksize for mode 1 */ + daddr_t mt_blksiz2; /* blocksize for mode 2 */ + daddr_t mt_blksiz3; /* blocksize for mode 3 */ + daddr_t mt_density0; /* density for mode 0 */ + daddr_t mt_density1; /* density for mode 1 */ + daddr_t mt_density2; /* density for mode 2 */ + daddr_t mt_density3; /* density for mode 3 */ +/* the following are not yet implemented */ + u_int32_t mt_comp0; /* compression type for mode 0 */ + u_int32_t mt_comp1; /* compression type for mode 1 */ + u_int32_t mt_comp2; /* compression type for mode 2 */ + u_int32_t mt_comp3; /* compression type for mode 3 */ +/* end not yet implemented */ #endif daddr_t mt_fileno; /* relative file number of current position */ daddr_t mt_blkno; /* relative block number of current position */ diff -urN --exclude=CVS src.org/usr.sbin/rmt/rmt.c src/usr.sbin/rmt/rmt.c --- src.org/usr.sbin/rmt/rmt.c Sat Aug 28 10:19:32 1999 +++ src/usr.sbin/rmt/rmt.c Wed Feb 2 17:01:51 2000 @@ -181,12 +181,30 @@ case 'S': /* status */ DEBUG("rmtd: S\n"); { struct mtget mtget; +#if defined(__FreeBSD__) + struct mtget_org mtgetorg; +#endif /* __FreeBSD__ */ if (ioctl(tape, MTIOCGET, (char *)&mtget) < 0) goto ioerror; +#if defined(__FreeBSD__) + /* Convert FreeBSD's mtget to the compatible one. */ + mtgetorg.mt_type = mtget.mt_type; + mtgetorg.mt_dsreg = mtget.mt_dsreg; + mtgetorg.mt_erreg = mtget.mt_erreg; + mtgetorg.mt_resid = mtget.mt_resid; + mtgetorg.mt_fileno = mtget.mt_fileno; + mtgetorg.mt_blkno = mtget.mt_blkno; + rval = sizeof (mtgetorg); +#else rval = sizeof (mtget); +#endif /* __FreeBSD__ */ (void)sprintf(resp, "A%d\n", rval); (void)write(1, resp, strlen(resp)); +#if defined(__FreeBSD__) + (void)write(1, (char *)&mtgetorg, sizeof (mtgetorg)); +#else (void)write(1, (char *)&mtget, sizeof (mtget)); +#endif /* __FreeBSD__ */ goto top; } --Multipart_Wed_Feb__2_17:37:25_2000-1 Content-Type: text/plain; charset=US-ASCII -- Seigo Tanimura --Multipart_Wed_Feb__2_17:37:25_2000-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 2:14:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from galileo.poli.hu (polinet-gw.poli.hu [195.199.8.25]) by builder.freebsd.org (Postfix) with ESMTP id 9AF653F58 for ; Wed, 2 Feb 2000 02:14:18 -0800 (PST) Received: from faber.poli.hu ([195.199.8.29] ident=mail) by galileo.poli.hu with esmtp (Exim 3.12 #1) id 12FwnK-0000sg-00 for hackers@freebsd.org; Wed, 02 Feb 2000 11:13:54 +0100 Received: from mauzi (helo=localhost) by faber.poli.hu with local-esmtp (Exim 3.12 #1 (Debian)) id 12FwnI-0008C1-00 for ; Wed, 02 Feb 2000 11:13:52 +0100 Date: Wed, 2 Feb 2000 11:13:52 +0100 (CET) From: Egervary Gergely To: hackers@freebsd.org Subject: NMBCLUSTERS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello, what size of $SUBJECT should be used on a box with two _extremely_ busy 100baseTX interfaces? -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 2:21: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iaehv.iae.nl (iaehv.IAE.nl [194.151.64.2]) by builder.freebsd.org (Postfix) with ESMTP id B53133FA7 for ; Wed, 2 Feb 2000 02:21:00 -0800 (PST) Received: from fun (fun.IAE.nl [194.151.66.128]) by iaehv.iae.nl (Postfix) with SMTP id 23D8B7D1E; Wed, 2 Feb 2000 11:20:58 +0100 (CET) Message-ID: <071201bf6d67$d56c0af0$804297c2@iae.nl> From: "Willem Jan Withagen" To: "Matthew D. Fuller" , "Chris Dillon" Cc: References: <20000201220729.0E03CBFD60@surf.iae.nl> <20000201170836.B23708@futuresouth.com> Subject: Re: Bad memory suspected Date: Wed, 2 Feb 2000 10:29:22 +0100 Organization: IAE bv. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG R29vZCBoaW50cywNCg0KV2VsbCBhY3R1YWxseSBpdCBpcyBhIEN5cml4IDI2NiAoYWthIDIwME1o eiBDUFUpIG9uIGFuIEFTVVMgYm9hcmQuDQooSSdtIG5vdCBzdXJlIGFib3V0IHRoZSBudW1iZXJz IHNpbmNlIGl0IGlzIGF0IGhvbWUsIGJ1dCBpdCBkb2VzIFNDU0ksIG5vIG5ldHdvcmspDQpBbmQg SSBkaWQgdXBncmFkZSB0aGUgYmlvcywgYW5kIGxvb2tlZCBmb3Igc3VwcG9ydCwgYW5kIGl0IHNl ZW1zIHN1cG9ydGVkLCBzaW5jZSB0aGUgQklPUyByZWNvZ25pc2VzIHRoZSBDUFUgYW5kIHNwZWVk LiBJJ2xsIGFnYWluIGNoZWNrIHRoZSB2b2x0YWdlcy4uLi4NCg0KLS1XalcNCg0KUGVyaGFwcyB3 ZSBzaG91bGQgIm1lcmdlIiB0aGlzIHRocmVhZCB0byBoYXJkd2FyZUBmcmVlQlNELm9yZyA/DQoN Ci0tLS0tIE9vcnNwcm9ua2VsaWprIGJlcmljaHQgLS0tLS0gDQpWYW46IE1hdHRoZXcgRC4gRnVs bGVyIDxmdWxsZXJtZEBmdXR1cmVzb3V0aC5jb20+DQpBYW46IENocmlzIERpbGxvbiA8Y2RpbGxv bkB3b2x2ZXMuazEyLm1vLnVzPg0KQ0M6IFdpbGxlbSBKYW4gV2l0aGFnZW4gPHdqd0BpYWUubmw+ OyA8aGFja2Vyc0BGcmVlQlNELk9SRz4NClZlcnpvbmRlbjogd29lbnNkYWcgMiBmZWJydWFyaSAy MDAwIDA6MDgNCk9uZGVyd2VycDogUmU6IEJhZCBtZW1vcnkgc3VzcGVjdGVkDQoNCg0KPiBPbiBU dWUsIEZlYiAwMSwgMjAwMCBhdCAwNTowMTo1NVBNIC0wNjAwLCBhIGxpdHRsZSBiaXJkaWUgdG9s ZCBtZQ0KPiB0aGF0IENocmlzIERpbGxvbiByZW1hcmtlZA0KPiA+IA0KPiA+IFRoZSBsYXN0IHRp bWUgSSBoYWQgYSBwcm9ibGVtIGxpa2UgdGhpcywgaXQgd2FzIGJlY2F1c2UgSSBwdXQgYSBQNTRD DQo+ID4gKFBlbnRpdW0tTU1YKSBpbnRvIGEgYm9hcmQgb25seSBkZXNpZ25lZCBmb3IgdGhlIFA1 M0MgKGEuay5hIHN0YW5kYXJkDQo+IA0KPiBJVFlNIFA1NUMgb24gYSBQNTRDIGJvYXJkLg0KPiAN Cj4gDQo+IA0KPiAtLSANCj4gTWF0dGhldyBGdWxsZXIgICAgIChNRjQ4MzkpICAgICB8ICAgIGZ1 bGxlcm1kQG92ZXIteW9uZGVyLm5ldA0KPiBVbml4IFN5c3RlbXMgQWRtaW5pc3RyYXRvciAgICAg IHwgICAgZnVsbGVybWRAZnV0dXJlc291dGguY29tDQo+IFNwZWNpYWxpemluZyBpbiBGcmVlQlNE ICAgICAgICAgfCAgICBodHRwOi8vd3d3Lm92ZXIteW9uZGVyLm5ldC8NCj4gDQo+ICJUaGUgb25s eSByZWFzb24gSSdtIGJ1cm5pbmcgbXkgY2FuZGxlIGF0IGJvdGggZW5kcywgaXMgYmVjYXVzZSBJ DQo+ICAgICAgIGhhdmVuJ3QgZmlndXJlZCBvdXQgaG93IHRvIGxpZ2h0IHRoZSBtaWRkbGUgeWV0 Ig0KPiANCj4gDQo= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 2:42:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tristero.cryptocourier.com (black-3.dsl.speakeasy.net [216.231.56.189]) by builder.freebsd.org (Postfix) with SMTP id 4637C3DDA for ; Wed, 2 Feb 2000 02:42:12 -0800 (PST) Received: (qmail 5159 invoked from network); 2 Feb 2000 10:43:15 -0000 Received: from ae.layer8.net (HELO ae) (192.168.69.10) by tristero.cryptocourier.com with SMTP; 2 Feb 2000 10:43:15 -0000 Message-ID: <003f01bf6d69$cf20f320$0a45a8c0@layer8.net> Reply-To: "Benjamin Black" From: "Benjamin Black" To: "Andrzej Bialecki" , "Joe Abley" Cc: "Tony Finch" , , References: Subject: Re: downed IP addresses/redundancy Date: Wed, 2 Feb 2000 02:39:40 -0800 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.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's actually slightly more complicated than this as you must be able to specify *per IP* which MAC should be used, not simply per interface. That was the barrier which stopped my VRRP implementation as well. > On Sun, 30 Jan 2000, Joe Abley wrote: > > > On Sat, Jan 29, 2000 at 01:19:53AM +0000, Tony Finch wrote: > > > I'd be interested to know of a free implementation of VRRP for the BSD > > > network stack. > > > > I started to look at this a while back, but started to flounder when > > I looked for an existing interface to allow me to source frames on > > a local ethernet with a userland-specified MAC address. > > > > Actually, I think I looked on OpenBSD, and can't remember whether I > > looked on FreeBSD too. If anybody has a good idea about how to send > > and receive frames on a local ethernet interface using one of several > > possible local MAC addresses (most user-specified) I can probably > > resurrect the code. > > Mhmmm... I'm using the code developed by Bill Paul, to change MAC address > via special ioctl. It works just fine for me. > > http://www.freebsd.org/~wpaul/setmac.tar.gz > > Andrzej Bialecki > > // WebGiro AB, Sweden (http://www.webgiro.com) > // ------------------------------------------------------------------- > // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- > > > > > 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 Feb 2 5:16:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by builder.freebsd.org (Postfix) with ESMTP id B62C33FFA for ; Wed, 2 Feb 2000 05:15:01 -0800 (PST) Received: from earth.fxp (oca-u1-11.hitter.net [207.192.78.11]) by pawn.primelocation.net (Postfix) with ESMTP id C72EC9B09; Wed, 2 Feb 2000 08:14:33 -0500 (EST) Date: Wed, 2 Feb 2000 08:14:26 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: Derek White Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel modules In-Reply-To: <20000202054939.4273.qmail@web3302.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Feb 2000, Derek White wrote: > Hey folks, > > I just wanted to know if anyone could point out a good > online resource like a tutorial or developer guide > that explains kernel module development under FreeBSD. See http://thc.pimmel.com/files/thc/bsdkern.html Although not necessarily its indented purpose, this security-related article serves as a fairly complete kld tutorial. > I am new to FreeBSD coming from a Linux/BeOS > background and am interested in playing around with it > to maybe contribute back to the FreeBSD source tree. > Maybe this is a dumb question but is developing kernel > modules for FreeBSD the same as it is technically for > Linux? > ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: 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 Wed Feb 2 8:13:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by builder.freebsd.org (Postfix) with ESMTP id C28BA409C for ; Wed, 2 Feb 2000 08:13:24 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id KAA32964; Wed, 2 Feb 2000 10:07:39 -0600 (CST) (envelope-from dan) Date: Wed, 2 Feb 2000 10:07:39 -0600 From: Dan Nelson To: Egervary Gergely Cc: hackers@FreeBSD.ORG Subject: Re: NMBCLUSTERS Message-ID: <20000202100739.B31919@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from "Egervary Gergely" on Wed Feb 2 11:13:52 GMT 2000 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Feb 02), Egervary Gergely said: > what size of $SUBJECT should be used on a box with two _extremely_ > busy 100baseTX interfaces? Interface type/speed is less important than number of open sockets. I've got an NFS server with a 100mbit card in it that is pretty heavily used the whole day, and after 22 days of uptime, netstat -m shows: 72/596/2112 mbuf clusters in use (current/peak/max) That's just using whatever value of NMBCLUSTERS a 'maxusers 100' gives me. On the other hand, when the Star Wars trailers were released last year, I was a mirror site, and ran out of mbufs a couple times because I had a lot of backed-up FTP connections over a T1 link. Easiest way to determine what you need is to just let the system run for a while, and then rebuild the kernel with your NMBCLUSTERS set at your peak value + 50% . -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 8:18:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by builder.freebsd.org (Postfix) with ESMTP id 04BCE4070 for ; Wed, 2 Feb 2000 08:18:37 -0800 (PST) Received: from bsd1.nyct.net (mbac@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id LAA03034; Wed, 2 Feb 2000 11:18:24 -0500 (EST) (envelope-from mbac@nyct.net) Received: from localhost (mbac@localhost) by bsd1.nyct.net (8.8.8/8.9.3) with ESMTP id LAA11075; Wed, 2 Feb 2000 11:18:23 -0500 (EST) (envelope-from mbac@nyct.net) X-Authentication-Warning: bsd1.nyct.net: mbac owned process doing -bs Date: Wed, 2 Feb 2000 11:18:23 -0500 (EST) From: Michael Bacarella To: Mike Nowlin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Re/Fwd: freebsd specific search In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > systems have the highest availability rate possible. Over the last few > years, I have replaced almost all of our Linux-based servers with FreeBSD, > due to the quality-control measures that the FreeBSD development team have > implemented. Not to start a flame-fest or anything (but who doesn't love em?), I hear the above quite a lot. I'm under the firm belief that a decent sys admin can rub either system to do whatever they want it to do. Not that I am questioning your abilities. I just get the "yeah, Linux is good, but just try to use it in a production environment and you'll understand" a lot. Granted, a lot of Linux distributions are totally unsuited for a server environment. Compared to that, I could understand why the server-orientedness of FreeBSD is attractive, but I certainly couldn't put up a reasonable arguement for either side in Slackware Linux vs. FreeBSD. Could you? -MB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 8:47:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from galileo.poli.hu (polinet-gw.poli.hu [195.199.8.25]) by builder.freebsd.org (Postfix) with ESMTP id C95AA4018 for ; Wed, 2 Feb 2000 08:46:05 -0800 (PST) Received: from faber.poli.hu ([195.199.8.29] ident=mail) by galileo.poli.hu with esmtp (Exim 3.12 #1) id 12G2tx-0000lG-00; Wed, 02 Feb 2000 17:45:09 +0100 Received: from mauzi (helo=localhost) by faber.poli.hu with local-esmtp (Exim 3.12 #1 (Debian)) id 12G2u1-00015j-00; Wed, 02 Feb 2000 17:45:13 +0100 Date: Wed, 2 Feb 2000 17:45:13 +0100 (CET) From: Egervary Gergely To: Dan Nelson Cc: hackers@FreeBSD.ORG Subject: Re: NMBCLUSTERS In-Reply-To: <20000202100739.B31919@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Interface type/speed is less important than number of open sockets. > I've got an NFS server with a 100mbit card in it that is pretty heavily > used the whole day, and after 22 days of uptime, netstat -m shows: > > 72/596/2112 mbuf clusters in use (current/peak/max) > > That's just using whatever value of NMBCLUSTERS a 'maxusers 100' gives > me. hmm right. well I've just compiled with 4096, my statistics after 9 minutes uptime: 2308/3182/4096 mbuf clusters in use (current/peak/max) -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 8:54:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by builder.freebsd.org (Postfix) with ESMTP id A70D8401D for ; Wed, 2 Feb 2000 08:54:42 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id KAA36797; Wed, 2 Feb 2000 10:53:25 -0600 (CST) (envelope-from dan) Date: Wed, 2 Feb 2000 10:53:24 -0600 From: Dan Nelson To: Egervary Gergely Cc: hackers@FreeBSD.ORG Subject: Re: NMBCLUSTERS Message-ID: <20000202105324.E31919@dan.emsphone.com> References: <20000202100739.B31919@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from "Egervary Gergely" on Wed Feb 2 17:45:13 GMT 2000 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Feb 02), Egervary Gergely said: > hmm right. well I've just compiled with 4096, my statistics after 9 > minutes uptime: > > 2308/3182/4096 mbuf clusters in use (current/peak/max) I'd say you need to raise it a bit more then if you're at 75% capacity after only 9 minutes :) Although if you are already at your peak load for the day, you might be okay. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 9: 7:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by builder.freebsd.org (Postfix) with ESMTP id B10A9401D for ; Wed, 2 Feb 2000 09:07:26 -0800 (PST) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 12G3CM-000CoD-00; Wed, 02 Feb 2000 19:04:10 +0200 Date: Wed, 2 Feb 2000 19:04:10 +0200 From: Neil Blakey-Milner To: Michael Bacarella Cc: Mike Nowlin , freebsd-hackers@FreeBSD.ORG Subject: Re: Re/Fwd: freebsd specific search Message-ID: <20000202190409.A49105@mithrandr.moria.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Organization: Rhodes University Computer Users' Society X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed 2000-02-02 (11:18), Michael Bacarella wrote: > > systems have the highest availability rate possible. Over the last few > > years, I have replaced almost all of our Linux-based servers with FreeBSD, > > due to the quality-control measures that the FreeBSD development team have > > implemented. > > Not to start a flame-fest or anything (but who doesn't love em?), I hear > the above quite a lot. (I don't like them.) > I certainly couldn't put up a reasonable arguement for either side in > Slackware Linux vs. FreeBSD. > > Could you? Nope. I can't say I know Slackware or its quality-control measures, so could you please answer some questions for me? What sort of quality-control measures does Slackware have? Where do I access their cvs tree? Where do I access their problem reports? Where do I subscribe to get every commit message? How long are their code freezes? How many committers do they have? What mechanism creates their releases? Where do I get release-candidates? (I apologize if that sounds argumentative, it really isn't. It just addresses some of the things that I do know about FreeBSD with regards to quality control, and what I don't know about Slackware in order to answer your question.) Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 9:12:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by builder.freebsd.org (Postfix) with ESMTP id 3B2EE401D for ; Wed, 2 Feb 2000 09:12:26 -0800 (PST) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id RAA12168; Wed, 2 Feb 2000 17:08:23 GMT (envelope-from geoffb) Date: Wed, 2 Feb 2000 17:08:22 +0000 From: Geoff Buckingham To: Michael Bacarella Cc: Mike Nowlin , freebsd-hackers@FreeBSD.ORG Subject: Re: Re/Fwd: freebsd specific search Message-ID: <20000202170822.A12031@chuggalug.clues.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Michael Bacarella on Wed, Feb 02, 2000 at 11:18:23AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 02, 2000 at 11:18:23AM -0500, Michael Bacarella wrote: > > > systems have the highest availability rate possible. Over the last few > > years, I have replaced almost all of our Linux-based servers with FreeBSD, > > due to the quality-control measures that the FreeBSD development team have > > implemented. > > Not to start a flame-fest or anything (but who doesn't love em?), I hear > the above quite a lot. > > I'm under the firm belief that a decent sys admin can rub either system to > do whatever they want it to do. Not that I am questioning your abilities. > I just get the "yeah, Linux is good, but just try to use it in a > production environment and you'll understand" a lot. > > Granted, a lot of Linux distributions are totally unsuited for a server > environment. Compared to that, I could understand why the > server-orientedness of FreeBSD is attractive, but I certainly couldn't put > up a reasonable arguement for either side in Slackware Linux vs. FreeBSD. > I am going to regret this, but.... For production enviroments FreeBSD has two significant advantages. It's release structure means FreeBSD is a complete operating system (as opposed to a kernel and one of several distributions) and machines are maintainable and upgradable in production over long periods of time via the STABLE branch. The FreeBSD kernel internals seem to have consistantly scaled further than the Linux kernel over the last few years (though linux has improved lots recently). This isn't a problem in most production enviroments however in marginal configurations it can be nasty. I had a very bad day six months ago attemting to patch a linux kernel to have >2048 file descriptors. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 10: 7:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from barracuda.aquarium.rtci.com (barracuda.aquarium.rtci.com [208.11.247.5]) by builder.freebsd.org (Postfix) with ESMTP id B80EA40C5; Wed, 2 Feb 2000 10:07:45 -0800 (PST) Received: from rtci.com (karma [208.11.244.6]) by barracuda.aquarium.rtci.com (8.9.3+Sun/8.9.3) with ESMTP id NAA26701; Wed, 2 Feb 2000 13:04:13 -0500 (EST) Message-ID: <3898715D.1E2FDD41@rtci.com> Date: Wed, 02 Feb 2000 13:03:09 -0500 From: Thomas Stromberg X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Suggestions for Gigabit cards for -CURRENT Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We're currently looking at upgrading several of our FreeBSD servers (dual PIII-600's, 66MHz PCI) and some Sun Ultra's to Gigabit Ethernet. We plan to hook these machines into our Cisco Catalyst 5000 server. They will most likely move to be running FreeBSD 4.x by the time that we actually get our budget approved. What experiences do you guys have with the cards? Currently we're looking at the ~$1000 range, specifically at Alteon 512k's ($1000) for the FreeBSD servers and Sun Gigabit 2.0's ($2000) for the Sun servers. I was interested in the Myrinet cards (for obvious reasons), but they appear to require a Myrinet switch (though I found myself slightly confused so I may be wrong) rather then being able to hook into our Catalyst 5000. The Intel PRO/1000 Gigabit cards look rather nice too, but I haven't seen drivers yet for FreeBSD (Linux yes). I'm pretty much purchasing on marketing and reputation rather then any experience here, so any help would be much appreciated. -- ======================================================================= Thomas R. Stromberg Asst. IS Manager / Systems Guru FreeBSD Contrib, Security Geek, etc. Research Triangle Commerce, Inc. http://www.afterthought.org/ http://www.rtci.com/ thomas@stromberg.org tstromberg@rtci.com ----------------------------------------------------------------------- MCSE: McDonald's Certified Service Engineer =================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 10:12:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by builder.freebsd.org (Postfix) with ESMTP id ADD4E4017 for ; Wed, 2 Feb 2000 10:12:41 -0800 (PST) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id LAA4075333 for ; Wed, 2 Feb 2000 11:07:47 -0700 (MST) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id LAA01345 for ; Wed, 2 Feb 2000 11:07:47 -0700 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Wed, 2 Feb 2000 11:07:46 -0700 (MST) From: "Ronald G. Minnich" X-Sender: rminnich@mini.acl.lanl.gov To: freebsd-hackers@FreeBSD.ORG Subject: Re: Re/Fwd: freebsd specific search In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Feb 2000, Michael Bacarella wrote: > Granted, a lot of Linux distributions are totally unsuited for a server > environment. Compared to that, I could understand why the > server-orientedness of FreeBSD is attractive, but I certainly couldn't put > up a reasonable arguement for either side in Slackware Linux vs. FreeBSD. Linux is definitely a less reliable system for clustering than freebsd. I've got 5 years of running them both at Sarnoff to back me up. Maybe I was doing something wrong, but I'm seeing similar problems here at the ACL on Linux. We ran into four classes of problems that linux had that freebsd did not. These problems are still not fixed as of 2.2.x or 2.3.x. 1) network stack. heavy use of udp can result in a hung kernel. Trivial TCP servers that need to take lots of connections cause trouble -- clients start getting ECONNREFUSED after a while 2) nfs. Hit nfs hard and random clients will hang. The dirty little secret of linux clusters is that 'everyone knows' that you don't run client nfs on linux cluster nodes if you want the cluster to stay up. This came out clearly at a cluster conference last spring (JCP4). 3) vm system. There's still some strange problems in there. 4) ext2. ext2 does not handle unplanned outages well. There is a reasonable chance that after a power fail you're going to have trouble if you have 100 nodes or more. You'll see 2 or 3 in need of help. freebsd was just more solid on our clusters. But note that linux isn't standing still -- it's just not as good as freebsd yet. I had one freebsd cluster that ran through 5 years of anything we could throw at it -- power fail, etc. It took disk death to finally halt one node and require me to hook up a keyboard to it to reload it. Our general experience was that NT fails a lot, esp. if you ask it to talk to a network or run a screensaver. Linux clusters run a long time, but power outages and other unplanned events will cause it trouble. Freebsd tolerates very high levels of abuse. The UFS guys really know their stuff. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 10:38:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by builder.freebsd.org (Postfix) with ESMTP id E596240D2; Wed, 2 Feb 2000 10:38:17 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA43601; Wed, 2 Feb 2000 11:33:00 -0700 (MST) (envelope-from ken) Date: Wed, 2 Feb 2000 11:32:59 -0700 From: "Kenneth D. Merry" To: Thomas Stromberg Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Suggestions for Gigabit cards for -CURRENT Message-ID: <20000202113259.A43505@panzer.kdm.org> References: <3898715D.1E2FDD41@rtci.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3898715D.1E2FDD41@rtci.com>; from tstromberg@rtci.com on Wed, Feb 02, 2000 at 01:03:09PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 02, 2000 at 13:03:09 -0500, Thomas Stromberg wrote: > We're currently looking at upgrading several of our FreeBSD servers > (dual PIII-600's, 66MHz PCI) and some Sun Ultra's to Gigabit Ethernet. > We plan to hook these machines into our Cisco Catalyst 5000 server. They > will most likely move to be running FreeBSD 4.x by the time that we > actually get our budget approved. What experiences do you guys have with > the cards? > > Currently we're looking at the ~$1000 range, specifically at Alteon > 512k's ($1000) for the FreeBSD servers and Sun Gigabit 2.0's ($2000) for > the Sun servers. I was interested in the Myrinet cards (for obvious > reasons), but they appear to require a Myrinet switch (though I found > myself slightly confused so I may be wrong) rather then being able to > hook into our Catalyst 5000. The Intel PRO/1000 Gigabit cards look > rather nice too, but I haven't seen drivers yet for FreeBSD (Linux yes). > > I'm pretty much purchasing on marketing and reputation rather then any > experience here, so any help would be much appreciated. I would recommend getting Alteon boards. It is likely that the Sun boards are Alteon OEM, although I'm not positive. One thing to keep in mind is that both Netgear and 3Com are OEMing Alteon boards, and you'll get them much cheaper that way. The boards are pretty much identical to the Alteon branded boards (which have no identifying marks on them). The performance is the same, at least for the Netgear boards. (I don't have any 3Com boards.) The Netgear GA620 is a 512K Tigon 2 board, and generally goes for around $300 or so. The 3Com boards have 1MB of SRAM, but I'm not sure whether they're Tigon 1 or Tigon 2. You really want a Tigon 2 board. Maybe someone who has one can comment. The Intel cards may look nice, and there is a FreeBSD driver for them, but I wouldn't get one. The first problem with the Intel boards is that there are no docs for them. Supposedly they're using a Cisco chip, and the specs for the chip are top secret. The FreeBSD driver (written by Matt Jacob) is based on the Linux driver, which Intel wrote, and he hasn't yet managed to get decent throughput through the cards. (Maybe Matt will comment.) They also only have 64K of memory on board, which is insufficient for a heavily loaded server, IMO. Even with the 512K Alteon boards, you have a minimum of about 200K, and probably more like 300K of cache for transmit and receive. The Intel boards also don't have the features necessary to really support zero copy TCP receive. The Alteon boards, on the other hand, have most of the features necessary, and if I get some time, I may add the last feature (header splitting) to the firmware. The other alternative is SysKonnect, and that might actually be a good alternative. I haven't seen the boards, don't know how much they cost, etc. etc. You might want to ask Bill Paul about them, he wrote the driver. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 10:51:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by builder.freebsd.org (Postfix) with ESMTP id 41D2B410E for ; Wed, 2 Feb 2000 10:51:51 -0800 (PST) Received: from bsd1.nyct.net (mbac@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id NAA04544; Wed, 2 Feb 2000 13:36:47 -0500 (EST) (envelope-from mbac@nyct.net) Received: from localhost (mbac@localhost) by bsd1.nyct.net (8.8.8/8.9.3) with ESMTP id NAA17342; Wed, 2 Feb 2000 13:36:46 -0500 (EST) (envelope-from mbac@nyct.net) X-Authentication-Warning: bsd1.nyct.net: mbac owned process doing -bs Date: Wed, 2 Feb 2000 13:36:46 -0500 (EST) From: Michael Bacarella To: Neil Blakey-Milner Cc: Mike Nowlin , freebsd-hackers@FreeBSD.ORG Subject: Re: Re/Fwd: freebsd specific search In-Reply-To: <20000202190409.A49105@mithrandr.moria.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What sort of quality-control measures does Slackware have? Where > do I access their cvs tree? Where do I access their problem reports? > Where do I subscribe to get every commit message? How long are > their code freezes? How many committers do they have? What > mechanism creates their releases? Where do I get release-candidates? Hmmm. my face is red. These aren't quite technical limitations as they are political ones. FreeBSD will naturally be more organized in this respect since the entire system is under the survey and control of one organization. This certainly makes it conveniant because you only have one source of information, and thusly it will be (or is easily made) uniform. I can't quite subscribe to a Slackware Linux mailing list and get information on changes to MySQL as well as Apache, but it's not out of the question for me to listen in on MySQL, Apache, and Slackware information channels, although their mechanisms obviously are not uniform. I suppose our needs just vary. :) But hey, we love FreeBSD too. -MB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 10:57:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by builder.freebsd.org (Postfix) with ESMTP id 1F545411C for ; Wed, 2 Feb 2000 10:57:40 -0800 (PST) Received: from bsd1.nyct.net (mbac@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id NAA08480; Wed, 2 Feb 2000 13:54:23 -0500 (EST) (envelope-from mbac@nyct.net) Received: from localhost (mbac@localhost) by bsd1.nyct.net (8.8.8/8.9.3) with ESMTP id NAA18276; Wed, 2 Feb 2000 13:54:22 -0500 (EST) (envelope-from mbac@nyct.net) X-Authentication-Warning: bsd1.nyct.net: mbac owned process doing -bs Date: Wed, 2 Feb 2000 13:54:22 -0500 (EST) From: Michael Bacarella To: Geoff Buckingham Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Re/Fwd: freebsd specific search In-Reply-To: <20000202170822.A12031@chuggalug.clues.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's release structure means FreeBSD is a complete operating system (as > opposed to a kernel and one of several distributions) and machines are > maintainable and upgradable in production over long periods of time via > the STABLE branch. I can agree with you here, as our organization has benefitted from said features. Although we aren't having the most pleasant time going from 2.2.8-STABLE to a 3.3.4-STABLE ever since the elfining. But that's probably our own fault for letting some of them get so out of date. :) > The FreeBSD kernel internals seem to have consistantly scaled further than the > Linux kernel over the last few years (though linux has improved lots recently). > This isn't a problem in most production enviroments however in marginal > configurations it can be nasty. I had a very bad day six months ago attemting > to patch a linux kernel to have >2048 file descriptors. Useless Anecdote Warning: For some particular reason (I'll spare the details of what lead up to this) I ping -f'd a FreeBSD box from a Linux box. The FreeBSD box held up very well. Despite this, my coworker (who owns said box) put icmp limits in place to further lessen the load. This attack was barely noticable on a neighboring Linux machine. (In fact, I was so annoyed that it had such a meager effect that I went to several other machines and had them all join in on the ping -f'ing fun). I experimented with variable packet sizes but I never did quite get to lock down the Linux machine as badly as I could the FreeBSD. Maybe I was just equating dropped packets with increased cpu availability as a plus, whereas FreeBSD put more effort into replying to all of the requests. Anyway, coworker also modified his system to dedicate more memory to the mbuf pool as well as some other tweaks which may or may not have done anything. Frustrated with my inability to saturate his FreeBSD box, I switched my attack to UDP. It was a basic UDP packet flood which, evidently, should've justed pushed as many packets onto the wire as the physical medium would allow. My machine is a P166 whereas his is a dual PPro200. The packet flood rendered the machine useless as far as networks go within 10 seconds. He tried it (out of annoyance) on a Linux machine which barely showed signs of struggle. Then, out of curiousity he turned it towards his Indy running Irix (don't remember the version). The machine fell right off the network in less than 3 seconds. Not only that, but when the flood stopped, the machine still wouldn't come back. One week later, the machine is still dead, despite reboots. Hardware damage? Neat! We are both using fairly recent versions of our respective systems, but I don't claim that either of us configured them optimally. Ho hum. If you can find a moral to this story, let me know. :) -MB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 11: 0:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 4692D4133 for ; Wed, 2 Feb 2000 11:00:52 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA00937; Wed, 2 Feb 2000 10:59:34 -0800 (PST) (envelope-from dillon) Date: Wed, 2 Feb 2000 10:59:34 -0800 (PST) From: Matthew Dillon Message-Id: <200002021859.KAA00937@apollo.backplane.com> To: "Ronald G. Minnich" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Re/Fwd: freebsd specific search References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Wed, 2 Feb 2000, Michael Bacarella wrote: :> Granted, a lot of Linux distributions are totally unsuited for a server :> environment. Compared to that, I could understand why the :> server-orientedness of FreeBSD is attractive, but I certainly couldn't put :> up a reasonable arguement for either side in Slackware Linux vs. FreeBSD. : :Linux is definitely a less reliable system for clustering than freebsd. :I've got 5 years of running them both at Sarnoff to back me up. Maybe I :was doing something wrong, but I'm seeing similar problems here at the ACL :on Linux. : :We ran into four classes of problems that linux had that freebsd did not. :These problems are still not fixed as of 2.2.x or 2.3.x. : :1) network stack. heavy use of udp can result in a hung kernel. Trivial : TCP servers that need to take lots of connections cause trouble -- : clients start getting ECONNREFUSED after a while :2) nfs. Hit nfs hard and random clients will hang. The dirty little : secret of linux clusters is that 'everyone knows' that you don't run : client nfs on linux cluster nodes if you want the cluster to stay up. : This came out clearly at a cluster conference last spring (JCP4). :3) vm system. There's still some strange problems in there. :4) ext2. ext2 does not handle unplanned outages well. There is a : reasonable chance that after a power fail you're going to have trouble : if you have 100 nodes or more. You'll see 2 or 3 in need of help. : :freebsd was just more solid on our clusters. But note that linux isn't :standing still -- it's just not as good as freebsd yet. I had one freebsd :cluster that ran through 5 years of anything we could throw at it -- power :fail, etc. It took disk death to finally halt one node and require me to :hook up a keyboard to it to reload it. : :Our general experience was that NT fails a lot, esp. if you ask it to talk :to a network or run a screensaver. Linux clusters run a long time, but :power outages and other unplanned events will cause it trouble. Freebsd :tolerates very high levels of abuse. The UFS guys really know their stuff. : :ron Linux has made great strides in the performance area -- the are way ahead of us on SMP issues, but they are definitely still behind in the reliable department. They almost caught up when we were going through our 3.0/3.1 fiasco but then fell behind again. I agree with your general assessment (though I'm even more rabid about NT, which I consider plain and simply to be a piece of crap). It interesting to note that two years ago it was well known that running NFSv3 under FreeBSD would destabilize it, so most people ran NFSv2. Even NFSv2 2 years ago had problems. Linux is just reaching the point now with NFSv2 where we were with NFSv3 two years ago. Thus in regards to NFS, FreeBSD is about 2 years ahead of Linux. At this time both NFSv2 and NFSv3 under FreeBSD are considered stable and reliable. -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 Feb 2 11:11:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by builder.freebsd.org (Postfix) with ESMTP id 1B9B240A3 for ; Wed, 2 Feb 2000 11:11:19 -0800 (PST) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 193ED3923; Wed, 2 Feb 2000 13:10:51 -0600 (CST) Received: (from sdk@localhost) by isis.visi.com (8.8.8/8.8.8) id NAA01645; Wed, 2 Feb 2000 13:10:51 -0600 (CST) Date: Wed, 2 Feb 2000 13:10:51 -0600 From: Stephen To: Matthew Dillon Cc: "Ronald G. Minnich" , freebsd-hackers@FreeBSD.ORG Subject: Re: Re/Fwd: freebsd specific search Message-ID: <20000202131051.A645@visi.com> References: <200002021859.KAA00937@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.1i In-Reply-To: <200002021859.KAA00937@apollo.backplane.com>; from Matthew Dillon on Wed, Feb 02, 2000 at 10:59:34AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 02, 2000 at 10:59:34AM -0800, Matthew Dillon wrote: > Linux has made great strides in the performance area -- the are way ahead > of us on SMP issues, but they are definitely still behind in the > reliable department. They almost caught up when we were going through > our 3.0/3.1 fiasco but then fell behind again. I agree with your general > assessment (though I'm even more rabid about NT, which I consider > plain and simply to be a piece of crap). > > It interesting to note that two years ago it was well known that running > NFSv3 under FreeBSD would destabilize it, so most people ran NFSv2. > Even NFSv2 2 years ago had problems. Linux is just reaching the point > now with NFSv2 where we were with NFSv3 two years ago. Thus in regards > to NFS, FreeBSD is about 2 years ahead of Linux. At this time both > NFSv2 and NFSv3 under FreeBSD are considered stable and reliable. > Re NFS stability. What version of the 3.x branch contained the updated NFS code? 3.3? Thanks, sk -- sdk@yuck.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 14: 7: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id 1639E4176; Wed, 2 Feb 2000 14:06:51 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id OAA23299; Wed, 2 Feb 2000 14:05:52 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id OAA19789; Wed, 2 Feb 2000 14:05:52 -0800 Received: from softweyr.com (dyn5.utah.xylan.com [198.206.184.241]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id OAA17724; Wed, 2 Feb 2000 14:05:47 -0800 (PST) Message-ID: <3898AB84.BDCC45F9@softweyr.com> Date: Wed, 02 Feb 2000 15:11:16 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: Thomas Stromberg , freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Suggestions for Gigabit cards for -CURRENT References: <3898715D.1E2FDD41@rtci.com> <20000202113259.A43505@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > > On Wed, Feb 02, 2000 at 13:03:09 -0500, Thomas Stromberg wrote: > > We're currently looking at upgrading several of our FreeBSD servers > > (dual PIII-600's, 66MHz PCI) and some Sun Ultra's to Gigabit Ethernet. > > We plan to hook these machines into our Cisco Catalyst 5000 server. They > > will most likely move to be running FreeBSD 4.x by the time that we > > actually get our budget approved. What experiences do you guys have with > > the cards? > > I would recommend getting Alteon boards. It is likely that the Sun boards > are Alteon OEM, although I'm not positive. > > One thing to keep in mind is that both Netgear and 3Com are OEMing Alteon > boards, and you'll get them much cheaper that way. The boards are pretty > much identical to the Alteon branded boards (which have no identifying > marks on them). The performance is the same, at least for the Netgear > boards. (I don't have any 3Com boards.) > > The Netgear GA620 is a 512K Tigon 2 board, and generally goes for around > $300 or so. The 3Com boards have 1MB of SRAM, but I'm not sure whether > they're Tigon 1 or Tigon 2. You really want a Tigon 2 board. Maybe > someone who has one can comment. I have a couple of GA620's here, too, and they work quite well. They support both 66Mhz and 64-bit PCI bus. We paid $329 from warehouse.com about 4 months ago, quite a reasonable price. You might want to look around and see if anyone has Solaris drivers for the Tigon-2, if you're using PCI Sun machines. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 14:18:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by builder.freebsd.org (Postfix) with ESMTP id 7EEE2419C; Wed, 2 Feb 2000 14:18:30 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA45356; Wed, 2 Feb 2000 15:17:48 -0700 (MST) (envelope-from ken) Date: Wed, 2 Feb 2000 15:17:48 -0700 From: "Kenneth D. Merry" To: Wes Peters Cc: Thomas Stromberg , freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Suggestions for Gigabit cards for -CURRENT Message-ID: <20000202151748.A45307@panzer.kdm.org> References: <3898715D.1E2FDD41@rtci.com> <20000202113259.A43505@panzer.kdm.org> <3898AB84.BDCC45F9@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3898AB84.BDCC45F9@softweyr.com>; from wes@softweyr.com on Wed, Feb 02, 2000 at 03:11:16PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 02, 2000 at 15:11:16 -0700, Wes Peters wrote: > "Kenneth D. Merry" wrote: > > > > On Wed, Feb 02, 2000 at 13:03:09 -0500, Thomas Stromberg wrote: > > > We're currently looking at upgrading several of our FreeBSD servers > > > (dual PIII-600's, 66MHz PCI) and some Sun Ultra's to Gigabit Ethernet. > > > We plan to hook these machines into our Cisco Catalyst 5000 server. They > > > will most likely move to be running FreeBSD 4.x by the time that we > > > actually get our budget approved. What experiences do you guys have with > > > the cards? > > > > I would recommend getting Alteon boards. It is likely that the Sun boards > > are Alteon OEM, although I'm not positive. > > > > One thing to keep in mind is that both Netgear and 3Com are OEMing Alteon > > boards, and you'll get them much cheaper that way. The boards are pretty > > much identical to the Alteon branded boards (which have no identifying > > marks on them). The performance is the same, at least for the Netgear > > boards. (I don't have any 3Com boards.) > > > > The Netgear GA620 is a 512K Tigon 2 board, and generally goes for around > > $300 or so. The 3Com boards have 1MB of SRAM, but I'm not sure whether > > they're Tigon 1 or Tigon 2. You really want a Tigon 2 board. Maybe > > someone who has one can comment. > > I have a couple of GA620's here, too, and they work quite well. They support > both 66Mhz and 64-bit PCI bus. We paid $329 from warehouse.com about 4 months > ago, quite a reasonable price. > > You might want to look around and see if anyone has Solaris drivers for > the Tigon-2, if you're using PCI Sun machines. Alteon includes a Solaris driver in their driver development kit. It might be possible to modify the probe routine to recognize other Tigon boards like the Netgear or 3Com boards. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 14:46:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51]) by builder.freebsd.org (Postfix) with ESMTP id 204F041D4 for ; Wed, 2 Feb 2000 14:46:37 -0800 (PST) Received: from wghicks.mindspring.com (user-33qtgkk.dialup.mindspring.com [199.174.194.148]) by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id RAA26208; Wed, 2 Feb 2000 17:46:37 -0500 (EST) Received: from wghicks.mindspring.com (IDENT:jhix@localhost [127.0.0.1]) by wghicks.mindspring.com (8.9.3/8.9.2) with ESMTP id OAA20615; Wed, 2 Feb 2000 14:49:14 -0800 (PST) (envelope-from jhix@wghicks.mindspring.com) Message-Id: <200002022249.OAA20615@mindspring.com> X-Mailer: exmh version 2.1.0 09/18/1999 To: Michael Bacarella Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Re/Fwd: freebsd specific search In-reply-to: Your message of "Wed, 02 Feb 2000 13:36:46 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Feb 2000 14:49:10 -0800 From: W Gerald Hicks Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > What sort of quality-control measures does Slackware have? Where > > do I access their cvs tree? Where do I access their problem reports? > > Where do I subscribe to get every commit message? How long are > > their code freezes? How many committers do they have? What > > mechanism creates their releases? Where do I get release-candidates? > > Hmmm. my face is red. > > These aren't quite technical limitations as they are political ones. [snip] Not having an orderly development process has caused quite a few technical limitations for Linux. Not having any sort of standardized and reproducible release process is notable; lack of version control is one of the more serious problems I have with Linux. Not really political, but (dis)organizational To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 16:19:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by builder.freebsd.org (Postfix) with ESMTP id D1D94420F for ; Wed, 2 Feb 2000 16:19:38 -0800 (PST) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id QAA94322 for freebsd-hackers@freebsd.org; Wed, 2 Feb 2000 16:19:33 -0800 (PST) From: Archie Cobbs Message-Id: <200002030019.QAA94322@bubba.whistle.com> Subject: Removing interfaces To: freebsd-hackers@freebsd.org Date: Wed, 2 Feb 2000 16:19:33 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With all the PCMCIA card stuff going on, is it now possible to remove a networking interface in FreeBSD (from within the kernel)? If so could someone show me an example how. I'd like to implement this in the ng_iface(8) netgraph node type. Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 19:18: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by builder.freebsd.org (Postfix) with ESMTP id AE1DD4221 for ; Wed, 2 Feb 2000 19:18:03 -0800 (PST) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id WAA02073 for ; Wed, 2 Feb 2000 22:18:05 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id WAA60359 for ; Wed, 2 Feb 2000 22:18:04 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id WAA19864 for freebsd-hackers@freebsd.org; Wed, 2 Feb 2000 22:18:02 -0500 (EST) Date: Wed, 2 Feb 2000 22:18:02 -0500 (EST) From: Thomas David Rivers Message-Id: <200002030318.WAA19864@lakes.dignus.com> To: freebsd-hackers@freebsd.org Subject: IBM releases JFS for Linux. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This came across the Linux/390 mailing list today, I thought it might be interesting for people: >"IBM makes JFS technology available for Linux - Technology based on OS/2 >Warp Journaled File System goes open source". See >http://oss.software.ibm.com/developerworks/opensource/features/jfs_feature.h >tml > The URL there is incorrect - the correct one is: http://oss.software.ibm.com/developerworks/opensource/jfs - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 19:26:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by builder.freebsd.org (Postfix) with ESMTP id 5A53B4267; Wed, 2 Feb 2000 19:25:55 -0800 (PST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA19700; Thu, 3 Feb 2000 13:55:39 +1030 (CST) Date: Thu, 3 Feb 2000 13:55:38 +1030 From: Greg Lehey To: Thomas David Rivers Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: IBM releases JFS for Linux. Message-ID: <20000203135538.F18958@freebie.lemis.com> References: <200002030318.WAA19864@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200002030318.WAA19864@lakes.dignus.com> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 2 February 2000 at 22:18:02 -0500, Thomas David Rivers wrote: > > This came across the Linux/390 mailing list today, I thought it > might be interesting for people: > >> "IBM makes JFS technology available for Linux - Technology based on OS/2 >> Warp Journaled File System goes open source". See >> http://oss.software.ibm.com/developerworks/opensource/features/jfs_feature.html > > The URL there is incorrect - the correct one is: > > http://oss.software.ibm.com/developerworks/opensource/jfs Interesting. I'm downloading and will take a look. Greg -- Finger grog@lemis.com for PGP public key 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 Feb 2 19:30:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.2.7]) by builder.freebsd.org (Postfix) with ESMTP id 4E9814267 for ; Wed, 2 Feb 2000 19:30:47 -0800 (PST) Received: from hermes.tue.nl [131.155.2.46] by kweetal.tue.nl (8.9.3) for id EAA24946 (ESMTP); Thu, 3 Feb 2000 04:30:31 +0100 (MET) Received: from deathstar (n189.dial.tue.nl [131.155.209.188]) by hermes.tue.nl (Postfix) with ESMTP id 099E62E803 for ; Thu, 3 Feb 2000 04:30:30 +0100 (CET) From: "Marco van de Voort" To: freebsd-hackers@freebsd.org Date: Thu, 3 Feb 2000 04:27:52 +0100 Subject: porting linux app. Syscalls In-reply-to: <200002030019.QAA94322@bubba.whistle.com> X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000203033030.099E62E803@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm new to the list (and to BSD development in general), and I'm developper of the FreePascal project (www.freepascal.org) which is a bootstrapping compiler, completely written in Pascal. Currently I started preparations for a port of the linux version to FreeBSD. FreePascal (FPC) doesn't default link to libc for some reasons, and therefore directly calls syscalls, about 60 of them. I started translating the syscalls this week (peeking at the linux "emulator" code), and now I arrived at the "getdents" and readdir calls. (I want to create a native port, the emulator already runs fine) These are supported by the emulator, but actually are emulated (they don't simply change parameters and do a FBSD syscall) However when I looked into sys/syscall.h, I found out that the getdents call seems to exist? So I have a few questions:-) 1. Is there documentation for the syscalls other than the code? I know there are some manpages, but these seem to be outdated (e.g. the named getdents call) 2. Can I use the getdents call to emulate the linux getdents? I use the base functionality, not all details have to be fully the same, just the principle. And why does the emulator not use this call? 3. If I can't use the call, the emulator code seems to call VOP_ functions. Can I access these functions from the application? --- not related to the other 3 4. In the rare event that I get it finished this week; The ports howto doesn't seems to apply to bootstrapping stuff. (It assumes the apps are gcc based or created by a gcc compiled app (like perl). Where does such an app fit into the BSD project? - several megs of Pascal source (entire project + sideprojects + texdocs is 25 MB source) - gmake makefiles. - binary required to start the compile(either native FBSD or linux) . (compiling the bsd version with the linux compiler is also possible I think, if a linux binary can create an ordinary FBSD binary) Marco van de Voort (MarcoV@Stack.nl) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 19:48: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by builder.freebsd.org (Postfix) with ESMTP id BBEE94274 for ; Wed, 2 Feb 2000 19:48:03 -0800 (PST) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA18837; Wed, 2 Feb 2000 22:47:31 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Wed, 2 Feb 2000 22:47:31 -0500 (EST) From: Chuck Robey To: Marco van de Voort Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: porting linux app. Syscalls In-Reply-To: <20000203033030.099E62E803@hermes.tue.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Feb 2000, Marco van de Voort wrote: > --- not related to the other 3 > 4. In the rare event that I get it finished this week; The ports howto doesn't seems to > apply to bootstrapping stuff. (It assumes the apps are gcc based or created by > a gcc compiled app (like perl). > > Where does such an app fit into the BSD project? > > - several megs of Pascal source (entire project + sideprojects + texdocs is 25 MB source) > - gmake makefiles. > - binary required to start the compile(either native FBSD or linux) > > . (compiling the bsd version with the linux > compiler is also possible I think, if a linux binary can create an ordinary FBSD > binary) This is just answering the last point. The modula-3 port is about the same size as yours, and it bootstraps, but (like you said) it does it from C. The lang/objc port *used* to require a binary-only bootstrap image, only. What I did there was to move the linux image home, use it to bootstrap a FreeBSD image, stored that on my home page, and made the port fetch it as one of the distfiles. In building the port, it just referenced the FreeBSD-native binary boot image to bootstrap itself, but it did build a full image of itself from that. Objc doesn't need that anymore (it has a C boot now) but you could take that approach. It's in the archives, probably version 1.5 of the Makefile, from October 97. > > > > Marco van de Voort (MarcoV@Stack.nl) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 20:25:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id F36CB425B for ; Wed, 2 Feb 2000 20:25:33 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id UAA02926; Wed, 2 Feb 2000 20:51:24 -0800 (PST) Date: Wed, 2 Feb 2000 20:51:23 -0800 From: Alfred Perlstein To: Marco van de Voort Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: porting linux app. Syscalls Message-ID: <20000202205123.H25520@fw.wintelcom.net> References: <200002030019.QAA94322@bubba.whistle.com> <20000203033030.099E62E803@hermes.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000203033030.099E62E803@hermes.tue.nl>; from marcov@stack.nl on Thu, Feb 03, 2000 at 04:27:52AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Marco van de Voort [000202 20:02] wrote: > > I'm new to the list (and to BSD development in general), and I'm developper > of the FreePascal project (www.freepascal.org) which is a bootstrapping > compiler, completely written in Pascal. > > Currently I started preparations for a port of the linux version to FreeBSD. > > FreePascal (FPC) doesn't default link to libc for some reasons, and therefore > directly calls syscalls, about 60 of them. > > I started translating the syscalls this week (peeking at the linux "emulator" > code), and now I arrived at the "getdents" and readdir calls. (I want to create > a native port, the emulator already runs fine) > > These are supported by the emulator, but actually are emulated (they don't > simply change parameters and do a FBSD syscall) > > However when I looked into sys/syscall.h, I found out that the getdents call > seems to exist? So I have a few questions:-) > > 1. Is there documentation for the syscalls other than the code? I know there > are some manpages, but these seem to be outdated (e.g. the named > getdents call) see: http://www.freebsd.org/cgi/man.cgi you can view linux syscalls from the slackware docs. > > 2. Can I use the getdents call to emulate the linux getdents? I use the base > functionality, not all details have to be fully the same, just the principle. And > why does the emulator not use this call? It seems that freebsd supports this call but it's hard to tell if the actual implementation is the same, I would just try some simple "hello worlds" to see if you can either use the FreeBSD version (possibly with a wrapper) or if you'll need to emulate it via a library call. It also seems that freebsd's version supports returning more information to the user application, and it's possible that the linux emulation code for getdents() actually pre-dates the FreeBSD emulation (it's happened before) It'd be interesting to know what you find out. > > 3. If I can't use the call, the emulator code seems to call VOP_ functions. Can > I access these functions from the application? no, those are kernel interfaces into the VFS system, you may not access them directly, they don't even exist from the userland's perspective. (mostly) :) what confuses me is that you don't support bootstrapping from the system C compiler. also, can you wrap lines at 70 characters? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 21:27: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 64DC94274 for ; Wed, 2 Feb 2000 21:27:02 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA03163; Wed, 2 Feb 2000 21:27:05 -0800 (PST) (envelope-from dillon) Date: Wed, 2 Feb 2000 21:27:05 -0800 (PST) From: Matthew Dillon Message-Id: <200002030527.VAA03163@apollo.backplane.com> To: Stephen Cc: "Ronald G. Minnich" , freebsd-hackers@FreeBSD.ORG Subject: Re: Re/Fwd: freebsd specific search References: <200002021859.KAA00937@apollo.backplane.com> <20000202131051.A645@visi.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Wed, Feb 02, 2000 at 10:59:34AM -0800, Matthew Dillon wrote: : :Re NFS stability. What version of the 3.x branch contained the updated NFS :code? 3.3? : :Thanks, :sk : :-- :sdk@yuck.net 3.3 got a big chunk of it but 3.4 has even more. 4.0 has all the bug fixes (there were some that we simply couldn't backport, mainly related to garbage beyond the file EOF in mmap() and things like that). -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 Feb 2 21:34: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by builder.freebsd.org (Postfix) with ESMTP id 5A94D4287 for ; Wed, 2 Feb 2000 21:33:56 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA15565; Wed, 2 Feb 2000 22:33:59 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA10257; Wed, 2 Feb 2000 22:34:05 -0700 (MST) Message-Id: <200002030534.WAA10257@harmony.village.org> To: Archie Cobbs Subject: Re: Removing interfaces Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 02 Feb 2000 16:19:33 PST." <200002030019.QAA94322@bubba.whistle.com> References: <200002030019.QAA94322@bubba.whistle.com> Date: Wed, 02 Feb 2000 22:34:04 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200002030019.QAA94322@bubba.whistle.com> Archie Cobbs writes: : With all the PCMCIA card stuff going on, is it now possible to : remove a networking interface in FreeBSD (from within the kernel)? : : If so could someone show me an example how. I'd like to implement : this in the ng_iface(8) netgraph node type. if_detach() is supposed to do this, but there are theoretical problems with our implementation of it. Also, there needs to be some way to propigate the "gone"ness of the interface generically rather than the ad-hoc way we do it now. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 2 22: 4: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.snfc21.pbi.net (mta4.snfc21.pbi.net [206.13.28.142]) by builder.freebsd.org (Postfix) with ESMTP id 8676742E0 for ; Wed, 2 Feb 2000 22:04:03 -0800 (PST) Received: from zippy.dyn.ml.org ([207.214.149.158]) by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FPC008YJBAPJ3@mta4.snfc21.pbi.net> for freebsd-hackers@FreeBSD.ORG; Wed, 2 Feb 2000 21:59:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id B140991523; Wed, 02 Feb 2000 21:59:08 -0800 (PST) Date: Wed, 02 Feb 2000 21:59:08 -0800 (PST) From: Alex Zepeda Subject: Re: Re/Fwd: freebsd specific search In-reply-to: To: Michael Bacarella Cc: Mike Nowlin , freebsd-hackers@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Feb 2000, Michael Bacarella wrote: > Not to start a flame-fest or anything (but who doesn't love em?), I hear > the above quite a lot. > > I'm under the firm belief that a decent sys admin can rub either system to > do whatever they want it to do. Not that I am questioning your abilities. > I just get the "yeah, Linux is good, but just try to use it in a > production environment and you'll understand" a lot. Needless to say I think that FreeBSD makes a great desktop environment too. What contributes to server sanity also makes things much less confusing for a desktop user too :) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 0:43:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scrooge.parallelconsulting.com (www.parallelconsulting.com [195.242.42.108]) by builder.freebsd.org (Postfix) with ESMTP id 5FA96430B for ; Thu, 3 Feb 2000 00:43:07 -0800 (PST) Received: from parallelconsulting.com ([193.150.233.97]) by scrooge.parallelconsulting.com (Netscape Messaging Server 3.6) with ESMTP id AAA6FF2 for ; Thu, 3 Feb 2000 09:29:31 +0100 Message-ID: <38993C48.B32B6BBC@parallelconsulting.com> Date: Thu, 03 Feb 2000 09:28:56 +0100 From: Jonas =?iso-8859-1?Q?B=FClow?= Organization: Parallel Consulting Group X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Hackers Subject: Installing -current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, What is the easiest way to install FreeBSD-current? Do I have to install a 3.x release and then cvsup to the -current followed by a make world? Before I ran into trouble I want to ask if 4.0 supports the 3CCFE574BT NIC? (3com 3c574). Right now I'm running this NIC with FreeBSD3.3+PAO on a Thinkpad570 and it works great. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 1:18:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by builder.freebsd.org (Postfix) with ESMTP id B358F42C8 for ; Thu, 3 Feb 2000 01:18:51 -0800 (PST) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA49479 for ; Thu, 3 Feb 2000 01:19:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Date: Thu, 03 Feb 2000 01:18:59 -0800 Message-ID: <49472.949569539.1@zippy.cdrom.com> From: "Jordan K. Hubbard" Subject: Mailing list search engine at www.freebsd.org down for repair. MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message To: announce@freebsd.org Subject: Mailing list search engine at www.freebsd.org down for repair. Date: Thu, 03 Feb 2000 01:18:59 -0800 Message-ID: <49472.949569539@zippy.cdrom.com> From: "Jordan K. Hubbard" MIME-Version: 1.0 Hi all, Our primary mail server, using the special type of evil ESP abilities which all critical hardware items possess, took advantage of everyone (including our postmaster) being away at LinuxWorld in New York to exhibit the "F" in "MTBF" with respect to hard drive specifications. We have mail services running again on a backup system but it will take a little while longer until all other mail-related services (like web search) are restored. We apologize for the inconvenience and hope to have this problem fixed shortly. A situation almost exactly like this (disk hardware failure) occurred with freefall during FreeBSDCon '99, incidently, and with this second incident we've certainly gotten the message: All critical freebsd.org assets will use (hardware) RAID arrays for storage in the future and we'll begin implementing that just as soon as we return. Regards, - Jordan ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 1:26:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by builder.freebsd.org (Postfix) with ESMTP id 4B4D24305 for ; Thu, 3 Feb 2000 01:26:10 -0800 (PST) Received: by gvr.gvr.org (Postfix, from userid 657) id 9499AA85A; Thu, 3 Feb 2000 10:26:15 +0100 (CET) Date: Thu, 3 Feb 2000 10:26:15 +0100 From: Guido van Rooij To: freebsd-hackers@freebsd.org Subject: open ref counts in CAM and vn Message-ID: <20000203102615.A64986@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A collegue fo mine had the problem that it was possible to vnconfig -u a vn device that was currently in use. This strikes me as odd. When looking through the da device code, I notice a similar problem. Suppose I have a zip fdisk mounted with a disklabel and 2 ufs partitions on it. When I mount both partitions, the disk will be locked. But it will be unlocked at the first unmount. I guess there should be a refcounter that keeps track of the amount of opens and only unlock devices at the last close. Same for vn.c. Any comments? -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 1:56:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by builder.freebsd.org (Postfix) with ESMTP id E013F4335 for ; Thu, 3 Feb 2000 01:56:28 -0800 (PST) Received: (from root@localhost) by Thingol.KryptoKom.DE (8.9.1/8.9.3) id KAA32376 for ; Thu, 3 Feb 2000 10:50:56 +0100 Received: from cirdan.kryptokom.de by KryptoWall via smtpp (Version 1.2.0) id kwa32371; Thu Feb 03 10:50:47 2000 Received: from nt-notes.kryptokom.de (nt-notes.kryptokom.de [192.168.6.247]) by cirdan.kryptokom.de (8.9.3/8.9.3) with SMTP id KAA09141 for ; Thu, 3 Feb 2000 10:49:48 +0100 Received: by nt-notes.kryptokom.de(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id C125687A.0036AE33 ; Thu, 3 Feb 2000 10:57:15 +0100 X-Lotus-FromDomain: UTIMACO From: "Thomas Klein" To: freebsd-hackers@FreeBSD.org Message-ID: Date: Thu, 3 Feb 2000 10:57:11 +0100 Subject: Re: how to catch a wildrunning pointer Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein on 28.01.2000 11:49:34 To: Thomas Klein/Aachen/Utimaco/DE@utimaco cc: freebsd-hackers@FreeBSD.ORG Subject: Re: how to catch a wildrunning pointer > > > > Hi > > > > My Problem: > > Within a kernel timeout routine I allocate memory and fill it with data. > > After a while I lock at this data again and realize that it it was modifyted > > (but not by me). > > How can I set a kernel mode watch point to that data to see which function > > change the data. > > > > Any Ideas ???? > > Look at the vm code, you can probably write protect the pages while > you aren't accessing them, this will cause offending code to panic > the machine so you can figure out who is twiddling your bits. > > Of course you'll have to unprotect the memory when you want to access > it for legitimate reasons. > > You owe the oracle a how-to on acually doing this, a paragraph or two > would suffice. > > thanks, > -Or^H^HAlfred If I understand this correctly I have to use the pmap_protect function. For testing I integrate the following sequence within a device driver attach routine. { int i; char * t_ptr; t_ptr = (char*) malloc(1027,M_DEVBUF,M_NOWAIT); for(i=0;i<1027,i++) *t_ptr = 'x'; pmap_protect(kmem_map,t_ptr,t_prt + 1027,VM_PROT_READ); *t_ptr = 'A'; printf("I can see this\n"); } No exception ocured. What is wrong? Wy dosn't it work? Regards Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 2: 9:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by builder.freebsd.org (Postfix) with ESMTP id A752C434E for ; Thu, 3 Feb 2000 02:09:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id JAA00671; Thu, 3 Feb 2000 09:42:13 GMT (envelope-from n_hibma@webweaving.org) Date: Thu, 3 Feb 2000 09:42:13 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Archie Cobbs Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Removing interfaces In-Reply-To: <200002030019.QAA94322@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG if_kue, if_aue or ask Doug Ambrisko for a copy of the udbp (USB double bulk pipe) driver that should have that as well. Nick On Wed, 2 Feb 2000, Archie Cobbs wrote: > With all the PCMCIA card stuff going on, is it now possible to > remove a networking interface in FreeBSD (from within the kernel)? > > If so could someone show me an example how. I'd like to implement > this in the ng_iface(8) netgraph node type. > > Thanks, > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 3:18:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.2.7]) by builder.freebsd.org (Postfix) with ESMTP id 911B74357 for ; Thu, 3 Feb 2000 03:18:36 -0800 (PST) Received: from hermes.tue.nl [131.155.2.46] by kweetal.tue.nl (8.9.3) for id MAA17805 (ESMTP); Thu, 3 Feb 2000 12:18:33 +0100 (MET) Received: from deathstar (n144.dial.tue.nl [131.155.209.143]) by hermes.tue.nl (Postfix) with ESMTP id 3634A2E802 for ; Thu, 3 Feb 2000 12:18:32 +0100 (CET) From: "Marco van de Voort" To: freebsd-hackers@FreeBSD.ORG Date: Thu, 3 Feb 2000 12:15:55 +0100 Subject: Re: porting linux app. Syscalls In-reply-to: <20000202205123.H25520@fw.wintelcom.net> References: <20000203033030.099E62E803@hermes.tue.nl>; from marcov@stack.nl on Thu, Feb 03, 2000 at 04:27:52AM +0100 X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000203111832.3634A2E802@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > what confuses me is that you don't support bootstrapping from the > system C compiler. How do you propose to do that with an all pascal source? Marco van de Voort (MarcoV@Stack.nl) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 3:20:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhost.tue.nl (mailhost.tue.nl [131.155.2.5]) by builder.freebsd.org (Postfix) with ESMTP id D3AE8408F for ; Thu, 3 Feb 2000 03:20:22 -0800 (PST) Received: from hermes.tue.nl [131.155.2.46] by mailhost.tue.nl (8.9.3) for id MAA09981 (ESMTP); Thu, 3 Feb 2000 12:20:25 +0100 (MET) Received: from deathstar (n144.dial.tue.nl [131.155.209.143]) by hermes.tue.nl (Postfix) with ESMTP id D61E72E802 for ; Thu, 3 Feb 2000 12:20:24 +0100 (CET) From: "Marco van de Voort" To: freebsd-hackers@FreeBSD.ORG Date: Thu, 3 Feb 2000 12:17:48 +0100 Subject: Re: porting linux app. Syscalls In-reply-to: <20000202205123.H25520@fw.wintelcom.net> References: <20000203033030.099E62E803@hermes.tue.nl>; from marcov@stack.nl on Thu, Feb 03, 2000 at 04:27:52AM +0100 X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000203112025.D61E72E802@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > see: http://www.freebsd.org/cgi/man.cgi > you can view linux syscalls from the slackware docs. Thank you that seems to be a good lead to start with. The problem was that I couldn't find any documentation :_) Marco van de Voort (MarcoV@Stack.nl) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 4:31:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lindt.urgle.com (lindt.urgle.com [195.173.172.169]) by builder.freebsd.org (Postfix) with ESMTP id 1A71343AB for ; Thu, 3 Feb 2000 04:31:35 -0800 (PST) Received: from mike by lindt.urgle.com with local (Exim 3.03 #1) id 12GLQ7-0002yR-00; Thu, 03 Feb 2000 12:31:35 +0000 Date: Thu, 3 Feb 2000 12:31:35 +0000 From: Mike Bristow To: Alex Zepeda Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Re/Fwd: freebsd specific search Message-ID: <20000203123135.A10816@lindt.urgle.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jazepeda@pacbell.net on Wed, Feb 02, 2000 at 09:59:08PM -0800 X-Rated: nuclear, www.ntk.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 02, 2000 at 09:59:08PM -0800, Alex Zepeda wrote: > On Wed, 2 Feb 2000, Michael Bacarella wrote: > > > Not to start a flame-fest or anything (but who doesn't love em?), I hear > > the above quite a lot. > > > > I'm under the firm belief that a decent sys admin can rub either system to > > do whatever they want it to do. Not that I am questioning your abilities. > > I just get the "yeah, Linux is good, but just try to use it in a > > production environment and you'll understand" a lot. > > Needless to say I think that FreeBSD makes a great desktop environment > too. What contributes to server sanity also makes things much less > confusing for a desktop user too :) True; but linux has support for a bigger variety of soundcards (my Win98^H^H^H^H^H^HEverQuest machine now has a Live! in it; supported under Linux but not under FreeBSD AFAIK; so the other half of the disk may turn turn into ext2 rather than ffs) The other 2 boxes will, of course, stay FreeBSD. I generally get the feeling that `Workstation Hardware'[1] has a better chance of being supported under Linux than FreeBSD. I may be talking rubbish, though ;-) [1] SoundCards; funky USB magic to talk to your digital camera; that kind of thing. -- Mike Bristow, Geek At Large ``Beware of Invisible Cows'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 7:21:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from eeyore.local.dohd.cx (d0030.dtk.chello.nl [213.46.0.30]) by builder.freebsd.org (Postfix) with ESMTP id C54943E7C for ; Thu, 3 Feb 2000 07:21:29 -0800 (PST) Received: by eeyore.local.dohd.cx (Postfix, from userid 1008) id 82EF1BAAD; Thu, 3 Feb 2000 16:21:31 +0100 (MET) Date: Thu, 3 Feb 2000 16:21:31 +0100 From: Mark Huizer To: freebsd-hackers@freebsd.org Subject: Re: open ref counts in CAM and vn Message-ID: <20000203162131.A22805@eeyore.local.dohd.cx> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20000203102615.A64986@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <20000203102615.A64986@gvr.gvr.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 03, 2000 at 10:26:15AM +0100, Guido van Rooij wrote: > A collegue fo mine had the problem that it was possible to > vnconfig -u a vn device that was currently in use. This strikes > me as odd. When trying to add some refcounting in sys/dev/vn.c, I wanted to switch to using the kernel module for vn, which brought another problem forward, tried to send-pr it, but unfortunately that doesn't work with hub being replaced temporarily.Anyway: on a current machine: dd if=/dev/zero of=/tmp/vntest bs=1024 count=1440 kldload vn vnconfig -c vn0 /tmp/vntest vnconfig -u vn0 kldunload -i SOMENUMBER (found with kldstat) kldload vn vnconfig -c vn0 /tmp/vntest crash, kernelpanic,kabang, kaputt :-( We tried to trace this back somewhere but failed. Mark -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 8: 7:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by builder.freebsd.org (Postfix) with ESMTP id 1A9B53F82 for ; Thu, 3 Feb 2000 08:07:49 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id IAA13283; Thu, 3 Feb 2000 08:07:57 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id IAA90977; Thu, 3 Feb 2000 08:07:57 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 3 Feb 2000 08:07:57 -0800 (PST) Message-Id: <200002031607.IAA90977@vashon.polstra.com> To: chuckr@picnic.mat.net Subject: Re: porting linux app. Syscalls In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Chuck Robey wrote: > The modula-3 port is about the same size as yours, and it > bootstraps, but (like you said) it does it from C. Actually, the standard Modula-3 bootstraps contain assembly-language sources generated by a cross-compiler, not C. John -- John Polstra jdp@polstra.com 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 Thu Feb 3 9: 0:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by builder.freebsd.org (Postfix) with ESMTP id F234B4100 for ; Thu, 3 Feb 2000 09:00:15 -0800 (PST) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA74316; Thu, 3 Feb 2000 09:00:24 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id JAA82870; Thu, 3 Feb 2000 09:00:20 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200002031700.JAA82870@whistle.com> Subject: Re: Removing interfaces To: Nick@whistle.com, Hibma Date: Thu, 3 Feb 2000 09:00:19 -0800 (PST) Cc: Archie@whistle.com, Cobbs , freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma writes: | | if_kue, if_aue or ask Doug Ambrisko for a copy of the udbp (USB double | bulk pipe) driver that should have that as well. The udbp doesn't do it since it just creates a netgraph node. Then you tie that netgraph node to an interface. At that point netgraph makes an interface called ngX. When you remove the USB widget then a new netgraph node is created (the old one destroyed) and then you connect this netgraph node to an interface which is ng(X+1)). This is what Archie is trying to avoid. So no udbp is not a example until Archie fixes netgraph. However, he could look at if_kue, if_aue, or the various pccard ethernet adapters in -current since they all seem to work. Archie you should upgrade your laptop to -current. Then you could go wireless with it and see the anX interface come an go. Also you could play with USB ethernet widgets and USB modem floating around here (BTW Nick it almost works with your umodem.c driver on your web page. The only problem I see is that it doesn't see loss of CD). Doug A. | On Wed, 2 Feb 2000, Archie Cobbs wrote: | | > With all the PCMCIA card stuff going on, is it now possible to | > remove a networking interface in FreeBSD (from within the kernel)? | > | > If so could someone show me an example how. I'd like to implement | > this in the ng_iface(8) netgraph node type. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 9: 6: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by builder.freebsd.org (Postfix) with ESMTP id E43DB414E for ; Thu, 3 Feb 2000 09:05:55 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA52872; Thu, 3 Feb 2000 10:05:22 -0700 (MST) (envelope-from ken) Date: Thu, 3 Feb 2000 10:05:22 -0700 From: "Kenneth D. Merry" To: Guido van Rooij Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: open ref counts in CAM and vn Message-ID: <20000203100522.A52825@panzer.kdm.org> References: <20000203102615.A64986@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000203102615.A64986@gvr.gvr.org>; from guido@gvr.org on Thu, Feb 03, 2000 at 10:26:15AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 03, 2000 at 10:26:15 +0100, Guido van Rooij wrote: > A collegue fo mine had the problem that it was possible to > vnconfig -u a vn device that was currently in use. This strikes > me as odd. > When looking through the da device code, I notice a similar problem. > Suppose I have a zip fdisk mounted with a disklabel and 2 > ufs partitions on it. When I mount both partitions, the disk > will be locked. But it will be unlocked at the first unmount. > I guess there should be a refcounter that keeps track of > the amount of opens and only unlock devices at the last close. > > Same for vn.c. > > Any comments? The reference counting should be handled by PHK's disk layer (which sits above CAM), and the da driver's close routine should only get called on final close. I don't know about the vn device, though. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 9: 7:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by builder.freebsd.org (Postfix) with ESMTP id EADCB4317 for ; Thu, 3 Feb 2000 09:07:22 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id JAA73059; Thu, 3 Feb 2000 09:07:46 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200002031707.JAA73059@troutmask.apl.washington.edu> Subject: Re: porting linux app. Syscalls In-Reply-To: <20000203111832.3634A2E802@hermes.tue.nl> from Marco van de Voort at "Feb 3, 2000 12:15:55 pm" To: Marco van de Voort Date: Thu, 3 Feb 2000 09:07:46 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marco van de Voort wrote: > > what confuses me is that you don't support bootstrapping from the > > system C compiler. > > How do you propose to do that with an all pascal source? > I probably don't need to tell you this, but there is ports/lang/p2c. I've never used p2c, so I can't make any claims about its quality. You might be able to use p2c to bootstrap you compiler. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 10:55:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by builder.freebsd.org (Postfix) with ESMTP id EBE5C3F58 for ; Thu, 3 Feb 2000 10:55:20 -0800 (PST) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA20150; Thu, 3 Feb 2000 10:50:36 -0800 Date: Thu, 3 Feb 2000 10:50:32 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Thomas Stromberg , freebsd-hackers@FreeBSD.ORG Subject: Re: Suggestions for Gigabit cards for -CURRENT In-Reply-To: <20000202113259.A43505@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The FreeBSD driver (written by Matt Jacob) is based on the Linux driver, > which Intel wrote, and he hasn't yet managed to get decent throughput > through the cards. (Maybe Matt will comment.) They also only have 64K of > memory on board, which is insufficient for a heavily loaded server, IMO. That's not memory- that's FIFO- there are two of them, I believe, one for receive, the other for xmit. You can devote 64k to ring descriptors for receive- that's 4096 descriptors- each able to manage a 2k buffer. And you can have two receive rings. You can have the same size for xmit. So, the receive performance bottleneck for this chip/board will be in how good your PCI implementation is at first followed by how low an amount of interrupt latency for reinstruct. If your PCI implementation can keep up with Gigabit speeds, you're fine. If not, I'm not sure that 512K or 1MB buffering buys you much. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 11:26:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by builder.freebsd.org (Postfix) with ESMTP id 8072C400D for ; Thu, 3 Feb 2000 11:26:29 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA53763; Thu, 3 Feb 2000 12:21:14 -0700 (MST) (envelope-from ken) Date: Thu, 3 Feb 2000 12:21:14 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Cc: Thomas Stromberg , freebsd-hackers@FreeBSD.ORG Subject: Re: Suggestions for Gigabit cards for -CURRENT Message-ID: <20000203122114.A53673@panzer.kdm.org> References: <20000202113259.A43505@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mjacob@feral.com on Thu, Feb 03, 2000 at 10:50:32AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 03, 2000 at 10:50:32 -0800, Matthew Jacob wrote: > > > The FreeBSD driver (written by Matt Jacob) is based on the Linux driver, > > which Intel wrote, and he hasn't yet managed to get decent throughput > > through the cards. (Maybe Matt will comment.) They also only have 64K of > > memory on board, which is insufficient for a heavily loaded server, IMO. > > That's not memory- that's FIFO- there are two of them, I believe, one for > receive, the other for xmit. You can devote 64k to ring descriptors for > receive- that's 4096 descriptors- each able to manage a 2k buffer. And > you can have two receive rings. You can have the same size for xmit. > > So, the receive performance bottleneck for this chip/board will be in how good > your PCI implementation is at first followed by how low an amount of > interrupt latency for reinstruct. If your PCI implementation can keep up with > Gigabit speeds, you're fine. If not, I'm not sure that 512K or 1MB buffering > buys you much. I think the memory would come in handy on a heavily loaded system, since you would gain a little extra time in case you were a little late servicing interrupts. i.e. it would smooth out the bumps a little bit. If your PCI implementation won't keep up with gigabit speeds, you'll just go slower. :) Most newer systems (e.g. 440BX) shouldn't have any trouble doing a reasonable amount of speed over gigabit ethernet, though. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 11:27:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by builder.freebsd.org (Postfix) with ESMTP id B30F43DF1 for ; Thu, 3 Feb 2000 11:27:28 -0800 (PST) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA20280; Thu, 3 Feb 2000 11:23:49 -0800 Date: Thu, 3 Feb 2000 11:23:45 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Thomas Stromberg , freebsd-hackers@FreeBSD.ORG Subject: Re: Suggestions for Gigabit cards for -CURRENT In-Reply-To: <20000203122114.A53673@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I think the memory would come in handy on a heavily loaded system, since > you would gain a little extra time in case you were a little late servicing > interrupts. i.e. it would smooth out the bumps a little bit. Yes, but that's what having 8192 2KByte descriptors handy is for... (that's 16MB of buffering). > > If your PCI implementation won't keep up with gigabit speeds, you'll just > go slower. :) Most newer systems (e.g. 440BX) shouldn't have any trouble > doing a reasonable amount of speed over gigabit ethernet, though. Typically I don't see higher than 60 or 70MB/s real throughput on most systems. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 11:40:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by builder.freebsd.org (Postfix) with ESMTP id B207B3E65 for ; Thu, 3 Feb 2000 11:40:21 -0800 (PST) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA20437; Thu, 3 Feb 2000 11:36:13 -0800 Date: Thu, 3 Feb 2000 11:36:10 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Thomas Stromberg , freebsd-hackers@FreeBSD.ORG Subject: Re: Suggestions for Gigabit cards for -CURRENT In-Reply-To: <20000203122953.A53875@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Feb 03, 2000 at 11:23:45 -0800, Matthew Jacob wrote: > > > > > > I think the memory would come in handy on a heavily loaded system, since > > > you would gain a little extra time in case you were a little late servicing > > > interrupts. i.e. it would smooth out the bumps a little bit. > > > > Yes, but that's what having 8192 2KByte descriptors handy is for... (that's > > 16MB of buffering). > > Are those all in card memory, or in host memory? What happens when you've > got some other traffic on the PCI bus, and the card gets a little behind > in DMAing its data into host memory? They're in host memory, and that's why I said "performance is contingent on PCI bus implementation". I think that 64K of FIFO is adequate flow control for PCI traffic avoidance. > > > If your PCI implementation won't keep up with gigabit speeds, you'll just > > > go slower. :) Most newer systems (e.g. 440BX) shouldn't have any trouble > > > doing a reasonable amount of speed over gigabit ethernet, though. > > > > Typically I don't see higher than 60 or 70MB/s real throughput on most > > systems. > > I've seen 100MB/sec on Pentium II 450's (440BX), and 90MB/sec on Pentium II > 350's (440BX). Aw, it just means your employers buy you up to date systems....unlike po' lil' me... :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 11:42:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by builder.freebsd.org (Postfix) with ESMTP id 33AD93DF1 for ; Thu, 3 Feb 2000 11:42:19 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA53919; Thu, 3 Feb 2000 12:29:53 -0700 (MST) (envelope-from ken) Date: Thu, 3 Feb 2000 12:29:53 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Cc: Thomas Stromberg , freebsd-hackers@FreeBSD.ORG Subject: Re: Suggestions for Gigabit cards for -CURRENT Message-ID: <20000203122953.A53875@panzer.kdm.org> References: <20000203122114.A53673@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mjacob@feral.com on Thu, Feb 03, 2000 at 11:23:45AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 03, 2000 at 11:23:45 -0800, Matthew Jacob wrote: > > > > I think the memory would come in handy on a heavily loaded system, since > > you would gain a little extra time in case you were a little late servicing > > interrupts. i.e. it would smooth out the bumps a little bit. > > Yes, but that's what having 8192 2KByte descriptors handy is for... (that's > 16MB of buffering). Are those all in card memory, or in host memory? What happens when you've got some other traffic on the PCI bus, and the card gets a little behind in DMAing its data into host memory? > > If your PCI implementation won't keep up with gigabit speeds, you'll just > > go slower. :) Most newer systems (e.g. 440BX) shouldn't have any trouble > > doing a reasonable amount of speed over gigabit ethernet, though. > > Typically I don't see higher than 60 or 70MB/s real throughput on most > systems. I've seen 100MB/sec on Pentium II 450's (440BX), and 90MB/sec on Pentium II 350's (440BX). Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 13:16:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by builder.freebsd.org (Postfix) with ESMTP id 8BB1443F6; Thu, 3 Feb 2000 13:16:36 -0800 (PST) Received: by gvr.gvr.org (Postfix, from userid 657) id 58812A85B; Thu, 3 Feb 2000 22:14:24 +0100 (CET) Date: Thu, 3 Feb 2000 22:14:24 +0100 From: Guido van Rooij To: "Kenneth D. Merry" Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@freebsd.org Subject: bug in vn, a pnaic and how to debug modules (was Re: open ref counts in CAM and vn) Message-ID: <20000203221424.A66443@gvr.gvr.org> References: <20000203102615.A64986@gvr.gvr.org> <20000203100522.A52825@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <20000203100522.A52825@panzer.kdm.org>; from Kenneth D. Merry on Thu, Feb 03, 2000 at 10:05:22AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 03, 2000 at 10:05:22AM -0700, Kenneth D. Merry wrote: > > The reference counting should be handled by PHK's disk layer (which sits > above CAM), and the da driver's close routine should only get called on > final close. ok. > > I don't know about the vn device, though. > That was the reason fro the posting. vnconfig -u goes directly to the vn device but that device has no track of open count. I don't see any code to notify the upper layer that the device is gove. That is wrong of course. In fact, one can vnconfig -u a device, while the device is used in a mount. The ufs layer doesn't even know that the device is gone and accessing the mount is still possible. Unmounting is not. So in this case, I guess vnconfig -u should fail. I think this is best achieved by using a ref counter in the vn device code. There is another bug in the vn code as well, which has tom do with modules. The following will panic on a page fault in vnsetcred (in the VOP_UNLOCK call): kldload vn vnconfig -c something vnconfig -u something kldunload vn kldload vn vnconfig -c something <--- instant panic I have not been able to debug this further, because it seems (but I have to recheck to be sure), that add-symbol-file /modules/vn does not allow one to look at variables delcared inside the vn module. Is there an easy way btw to determine
? I looked inside the debugger in the linker_files queue and then use the load address there, plus the start address of .text as found by objdump of the vn module. -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 13:29: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from security.za.net (security.za.net [209.212.100.194]) by builder.freebsd.org (Postfix) with ESMTP id 12B44403C for ; Thu, 3 Feb 2000 13:29:04 -0800 (PST) Received: from localhost (lists@localhost) by security.za.net (8.9.3/8.9.3) with ESMTP id XAA03541 for ; Thu, 3 Feb 2000 23:29:04 +0200 (SAST) (envelope-from lists@security.za.net) Date: Thu, 3 Feb 2000 23:28:49 +0200 (SAST) From: To: hackers@freebsd.org Subject: IPFW / IP Filter question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A quick question, is it possible to copy all traffic coming into a particular interface to a divert socket, while still having the traffic also running normally and taking normal routes etc. I would have thought you would use the tee option in ipfw for this, but its not implemented yet according to my man pages, so I was wondering if there was another way to do this, cause it makes traffic analysis a hell of a lot easier if I can do this rather than having to sniff it with bpf or something. Any help would be appreciated Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 15:41:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [194.151.74.97]) by builder.freebsd.org (Postfix) with ESMTP id 2F5FA4C08 for ; Thu, 3 Feb 2000 14:22:46 -0800 (PST) Received: by gvr.gvr.org (Postfix, from userid 657) id 81024A85A; Thu, 3 Feb 2000 23:22:56 +0100 (CET) Date: Thu, 3 Feb 2000 23:22:56 +0100 From: Guido van Rooij To: lists@security.za.net Cc: hackers@freebsd.org Subject: Re: IPFW / IP Filter question Message-ID: <20000203232256.A66818@gvr.gvr.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from lists@security.za.net on Thu, Feb 03, 2000 at 11:28:49PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 03, 2000 at 11:28:49PM +0200, lists@security.za.net wrote: > A quick question, is it possible to copy all traffic coming into a > particular interface to a divert socket, while still having the traffic > also running normally and taking normal routes etc. > > I would have thought you would use the tee option in ipfw for this, but > its not implemented yet according to my man pages, so I was wondering if > there was another way to do this, cause it makes traffic analysis a hell > of a lot easier if I can do this rather than having to sniff it with bpf > or something. I can;t answer this for ipfw (though IIRC there does exist a tee option in -current for ipfw). With ipfilter you can dup al traffic to an alternate device, like a tunnel device. e.g: pass in on lo0 dup-to tun0 from localhost to localhost or: pass in on lo0 dup-to ed0:1.2.3.4 from localhost to localhost where 1.2.3.4 is a machine on the same lan as ed0. -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 16:32: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.2.7]) by builder.freebsd.org (Postfix) with ESMTP id D8F523D5B for ; Thu, 3 Feb 2000 16:32:02 -0800 (PST) Received: from hermes.tue.nl [131.155.2.46] by kweetal.tue.nl (8.9.3) for id BAA15382 (ESMTP); Fri, 4 Feb 2000 01:32:13 +0100 (MET) Received: from deathstar (n165.dial.tue.nl [131.155.209.164]) by hermes.tue.nl (Postfix) with ESMTP id 64D7A2E802 for ; Fri, 4 Feb 2000 01:32:11 +0100 (CET) From: "Marco van de Voort" To: hackers@freebsd.org Date: Fri, 4 Feb 2000 01:29:35 +0100 Subject: Re: porting linux app. Syscalls In-reply-to: <200002031607.IAA90977@vashon.polstra.com> References: X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000204003211.64D7A2E802@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The modula-3 port is about the same size as yours, and it > > bootstraps, but (like you said) it does it from C. > > Actually, the standard Modula-3 bootstraps contain assembly-language > sources generated by a cross-compiler, not C. Actually that is the first plan too for fpc. This because the port of the required libraries and stubs probably will be ready earlier than the actual compiler support (adding of a target in the compiler source), specially because we want to redo the linux definitions to some unix-general and create linux and freebsd as special cases. Marco van de Voort (MarcoV@Stack.nl) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 18:18:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id D39A2404E for ; Thu, 3 Feb 2000 18:18:32 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id SAA18055; Thu, 3 Feb 2000 18:18:08 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id SAA08065; Thu, 3 Feb 2000 18:18:07 -0800 Received: from softweyr.com (dyn5.utah.xylan.com [198.206.184.241]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id SAA09743; Thu, 3 Feb 2000 18:18:05 -0800 (PST) Message-ID: <389A382D.BA09E024@softweyr.com> Date: Thu, 03 Feb 2000 19:23:41 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Thomas David Rivers Cc: freebsd-hackers@freebsd.org Subject: Re: IBM releases JFS for Linux. References: <200002030318.WAA19864@lakes.dignus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas David Rivers wrote: > > This came across the Linux/390 mailing list today, I thought it > might be interesting for people: > > The URL there is incorrect - the correct one is: > > http://oss.software.ibm.com/developerworks/opensource/jfs This has been reported on daily.daemonnews.org. Read the comment I wrote; IBM has an "Open Source Survey" you should respond to as well. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 18:19:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id E2312404E; Thu, 3 Feb 2000 18:19:30 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id SAA18063; Thu, 3 Feb 2000 18:18:33 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id SAA08094; Thu, 3 Feb 2000 18:18:33 -0800 Received: from softweyr.com (dyn5.utah.xylan.com [198.206.184.241]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id SAA09767; Thu, 3 Feb 2000 18:18:32 -0800 (PST) Message-ID: <389A3847.EC2383BB@softweyr.com> Date: Thu, 03 Feb 2000 19:24:07 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: Thomas David Rivers , freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org Subject: Re: IBM releases JFS for Linux. References: <200002030318.WAA19864@lakes.dignus.com> <20000203135538.F18958@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > On Wednesday, 2 February 2000 at 22:18:02 -0500, Thomas David Rivers wrote: > > > > This came across the Linux/390 mailing list today, I thought it > > might be interesting for people: > > > >> "IBM makes JFS technology available for Linux - Technology based on OS/2 > >> Warp Journaled File System goes open source". See > >> http://oss.software.ibm.com/developerworks/opensource/features/jfs_feature.html > > > > The URL there is incorrect - the correct one is: > > > > http://oss.software.ibm.com/developerworks/opensource/jfs > > Interesting. I'm downloading and will take a look. Our hero! ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 18:25:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by builder.freebsd.org (Postfix) with SMTP id 0934F42F2; Thu, 3 Feb 2000 18:25:27 -0800 (PST) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id VAA10541; Thu, 3 Feb 2000 21:29:28 -0500 From: Bill Paul Message-Id: <200002040229.VAA10541@skynet.ctr.columbia.edu> Subject: Re: Suggestions for Gigabit cards for -CURRENT To: ken@kdm.org (Kenneth D. Merry) Date: Thu, 3 Feb 2000 21:29:27 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: <20000202113259.A43505@panzer.kdm.org> from "Kenneth D. Merry" at Feb 2, 2000 11:32:59 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 7018 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Kenneth D. Merry had to walk into mine and say: > On Wed, Feb 02, 2000 at 13:03:09 -0500, Thomas Stromberg wrote: > > We're currently looking at upgrading several of our FreeBSD servers > > (dual PIII-600's, 66MHz PCI) and some Sun Ultra's to Gigabit Ethernet. > > We plan to hook these machines into our Cisco Catalyst 5000 server. They > > will most likely move to be running FreeBSD 4.x by the time that we > > actually get our budget approved. What experiences do you guys have with > > the cards? > > > > Currently we're looking at the ~$1000 range, specifically at Alteon > > 512k's ($1000) for the FreeBSD servers and Sun Gigabit 2.0's ($2000) for > > the Sun servers. I was interested in the Myrinet cards (for obvious > > reasons), but they appear to require a Myrinet switch (though I found > > myself slightly confused so I may be wrong) rather then being able to > > hook into our Catalyst 5000. The Intel PRO/1000 Gigabit cards look > > rather nice too, but I haven't seen drivers yet for FreeBSD (Linux yes). > > > > I'm pretty much purchasing on marketing and reputation rather then any > > experience here, so any help would be much appreciated. > > I would recommend getting Alteon boards. It is likely that the Sun boards > are Alteon OEM, although I'm not positive. I think the first gigabit cards Sun had on the market were OEMed from Alteon, but I've been told that their newer cards are something else entirely. I don't know exactly what, but they're not Tigon-based. > One thing to keep in mind is that both Netgear and 3Com are OEMing Alteon > boards, and you'll get them much cheaper that way. The boards are pretty > much identical to the Alteon branded boards (which have no identifying > marks on them). The performance is the same, at least for the Netgear > boards. (I don't have any 3Com boards.) There are a number of companies selling OEM'ed alteon boards for various prices. IBM sells two cards, one for PC-based hardware and one for RS/6000s which I think are basically the same hardware with different driver kits. Of course, the RS/6000 card is $2100 while the PC-based one is probably around $600 or so. My guess is they're Alteon cards with different PCI device IDs, but I can't confirm this as I don't have one. The SGI gigabit adapter, NEC gigabit adapter, DEC EtherWORKS/1000, 3Com 3c985 and 3c985B, and the Netgear GA620 are all Tigon boards (not to mention the Alteon ACEnic) and should all work fine with the ti driver. Oh, I found another one recently: Farallon also sells a gigabit PCI NIC for the Mac which is Tigon-based. > The Netgear GA620 is a 512K Tigon 2 board, and generally goes for around > $300 or so. The 3Com boards have 1MB of SRAM, but I'm not sure whether > they're Tigon 1 or Tigon 2. You really want a Tigon 2 board. Maybe > someone who has one can comment. The original 3Com 3c985 was a Tigon 1 board (I have one) and the 3c985B is a Tigon 2. The Tigon 1 is no longer in production, though of course I try to maintain support for it for those people who still have them. The Tigon 1 had only a single R4000 CPU in it while the Tigon 2 has two. The Netgear GA620 is by far the cheapest at about $320. The various OEM cards sold for the PC are usually around $600, give or take $100. The GA620 only has 512K of SRAM compared to 1MB on most of the others, however you're not likely to notice a problem with that unless you try to push the card really hard with a really big TCP window size and jumbo frames. > The Intel cards may look nice, and there is a FreeBSD driver for them, but > I wouldn't get one. The first problem with the Intel boards is that there > are no docs for them. Supposedly they're using a Cisco chip, and the specs > for the chip are top secret. This is why I don't buy or recommend Intel NICs. But that's just my personal bias. > The FreeBSD driver (written by Matt Jacob) is based on the Linux driver, > which Intel wrote, and he hasn't yet managed to get decent throughput > through the cards. (Maybe Matt will comment.) They also only have 64K of > memory on board, which is insufficient for a heavily loaded server, IMO. > > Even with the 512K Alteon boards, you have a minimum of about 200K, and > probably more like 300K of cache for transmit and receive. The Alteon cards also need a certain amount of SRAM to run the firmware. > The Intel boards also don't have the features necessary to really support > zero copy TCP receive. > > The Alteon boards, on the other hand, have most of the features necessary, > and if I get some time, I may add the last feature (header splitting) to > the firmware. > > The other alternative is SysKonnect, and that might actually be a good > alternative. I haven't seen the boards, don't know how much they cost, > etc. etc. You might want to ask Bill Paul about them, he wrote the driver. The SysKonnect cards aren't bad. A single port multimode fiber card is around $700, I think. The single mode cards are more expensive. However SysKonnect also makes the only dual port gigabit card on the market right now (though it costs around $1100). The SysKonnect cards also average about 1MB of SRAM. The dual port card that I have has 1MB, which is I divide up between both ports. The SysKonnect boards have two main parts: a XaQti XMAC II gigabit MAC and a controller that interfaces the XMAC to the PCI bus called the GEnesis. (The GEnesis also provides buffering, arbitration and other things.) Dual port cards have one GEnesis and two XMACs, so they appear as a single PCI device to the host. The drivers that SysKonnect currently provides are set up to use the dual port cards in a failover configuration, meaning that you get only one virtual interface, and the driver monitors the link state and such and switches from one port to the other if one of the links goes down. The FreeBSD driver is different: each port on a dual port NIC is a separate interface and can operate independently of the other. So you can have sk0 and sk1 on the same card connected to two networks both running at the same time. Both the Alteon and SysKonnect NICs are 64-bit PCI cards. (Actually, I'm pretty sure all of the PCI gigabit NICs are 64-bit.) Both kinds of cards can do jumbograms on FreeBSD. Also, both vendors have released pretty good hardware documentation, which makes them good choices for custom applications, if you're into that sort of thing. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 18:34:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by builder.freebsd.org (Postfix) with ESMTP id 30F13404E; Thu, 3 Feb 2000 18:34:41 -0800 (PST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA28450; Fri, 4 Feb 2000 13:04:27 +1030 (CST) Date: Fri, 4 Feb 2000 13:04:27 +1030 From: Greg Lehey To: Wes Peters Cc: Thomas David Rivers , freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org Subject: Re: IBM releases JFS for Linux. Message-ID: <20000204130426.C27530@freebie.lemis.com> References: <200002030318.WAA19864@lakes.dignus.com> <20000203135538.F18958@freebie.lemis.com> <389A3847.EC2383BB@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <389A3847.EC2383BB@softweyr.com> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 3 February 2000 at 19:24:07 -0700, Wes Peters wrote: > Greg Lehey wrote: >> >> On Wednesday, 2 February 2000 at 22:18:02 -0500, Thomas David Rivers wrote: >>> >>> This came across the Linux/390 mailing list today, I thought it >>> might be interesting for people: >>> >>>> "IBM makes JFS technology available for Linux - Technology based on OS/2 >>>> Warp Journaled File System goes open source". See >>>> http://oss.software.ibm.com/developerworks/opensource/features/jfs_feature.html >>> >>> The URL there is incorrect - the correct one is: >>> >>> http://oss.software.ibm.com/developerworks/opensource/jfs >> >> Interesting. I'm downloading and will take a look. > > Our hero! ;^) Wait until I deliver. I've taken a look, and there's as good as no docco. It's an OS/2 version, which suggests to me that it would be more difficult to port than the original AIX version. I might get back to it again later on, but don't hold your breath. Greg -- Finger grog@lemis.com for PGP public key 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 Thu Feb 3 18:37:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by builder.freebsd.org (Postfix) with ESMTP id C36F142F2; Thu, 3 Feb 2000 18:37:30 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id TAA57320; Thu, 3 Feb 2000 19:37:10 -0700 (MST) (envelope-from ken) Date: Thu, 3 Feb 2000 19:37:10 -0700 From: "Kenneth D. Merry" To: Bill Paul Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Suggestions for Gigabit cards for -CURRENT Message-ID: <20000203193710.A57242@panzer.kdm.org> References: <20000202113259.A43505@panzer.kdm.org> <200002040229.VAA10541@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002040229.VAA10541@skynet.ctr.columbia.edu>; from wpaul@skynet.ctr.columbia.edu on Thu, Feb 03, 2000 at 09:29:27PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Thanks for the info Bill! ] On Thu, Feb 03, 2000 at 21:29:27 -0500, Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Kenneth D. Merry had > to walk into mine and say: > > > The Netgear GA620 is a 512K Tigon 2 board, and generally goes for around > > $300 or so. The 3Com boards have 1MB of SRAM, but I'm not sure whether > > they're Tigon 1 or Tigon 2. You really want a Tigon 2 board. Maybe > > someone who has one can comment. > > The original 3Com 3c985 was a Tigon 1 board (I have one) and the 3c985B is > a Tigon 2. The Tigon 1 is no longer in production, though of course I try > to maintain support for it for those people who still have them. The Tigon 1 > had only a single R4000 CPU in it while the Tigon 2 has two. Ahh, that's good to know, I was wondering whether they had a Tigon 2 board out, since it would make a cheaper alternative to the 1MB ACEnic. > The Netgear GA620 is by far the cheapest at about $320. The various OEM > cards sold for the PC are usually around $600, give or take $100. The GA620 > only has 512K of SRAM compared to 1MB on most of the others, however you're > not likely to notice a problem with that unless you try to push the card > really hard with a really big TCP window size and jumbo frames. That has been my experience as well. > > The FreeBSD driver (written by Matt Jacob) is based on the Linux driver, > > which Intel wrote, and he hasn't yet managed to get decent throughput > > through the cards. (Maybe Matt will comment.) They also only have 64K of > > memory on board, which is insufficient for a heavily loaded server, IMO. > > > > Even with the 512K Alteon boards, you have a minimum of about 200K, and > > probably more like 300K of cache for transmit and receive. > > The Alteon cards also need a certain amount of SRAM to run the firmware. Yep, thus the 200K-300K number. The minimum amount of buffer that the board will configure is 64K for transmit buffers and 128K for receive buffers. It looks at the size of the firmware and associated data structures, and allocates the rest of the card memory for transmit and receive buffer space. > Both the Alteon and SysKonnect NICs are 64-bit PCI cards. (Actually, I'm > pretty sure all of the PCI gigabit NICs are 64-bit.) Both kinds of cards > can do jumbograms on FreeBSD. Also, both vendors have released pretty good > hardware documentation, which makes them good choices for custom applications, > if you're into that sort of thing. Alteon also provides firmware source, which can really come in handy. Do you know if SysKonnect has released firmware? Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 18:51:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by builder.freebsd.org (Postfix) with ESMTP id 729524325; Thu, 3 Feb 2000 18:51:16 -0800 (PST) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA21713; Thu, 3 Feb 2000 18:50:51 -0800 Date: Thu, 3 Feb 2000 18:50:47 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Greg Lehey Cc: Wes Peters , Thomas David Rivers , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: IBM releases JFS for Linux. In-Reply-To: <20000204130426.C27530@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Wait until I deliver. > > I've taken a look, and there's as good as no docco. It's an OS/2 > version, which suggests to me that it would be more difficult to port > than the original AIX version. I might get back to it again later on, > but don't hold your breath. > I was informed, at Veritas, that indeed this is the OS/2 vs. the AIX version, which really stumped me. JFS for AIX is really not bad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 18:53: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id A9F97432F for ; Thu, 3 Feb 2000 18:53:00 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id SAA18349; Thu, 3 Feb 2000 18:52:30 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id SAA09045; Thu, 3 Feb 2000 18:52:30 -0800 Received: from softweyr.com (dyn5.utah.xylan.com [198.206.184.241]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id SAA11378; Thu, 3 Feb 2000 18:52:29 -0800 (PST) Message-ID: <389A403C.76F0D62F@softweyr.com> Date: Thu, 03 Feb 2000 19:58:04 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Bristow Cc: Alex Zepeda , freebsd-hackers@freebsd.org Subject: Re: Re/Fwd: freebsd specific search References: <20000203123135.A10816@lindt.urgle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Bristow wrote: > > True; but linux has support for a bigger variety of soundcards > (my Win98^H^H^H^H^H^HEverQuest machine now has a Live! in it; supported > under Linux but not under FreeBSD AFAIK; so the other half of the disk > may turn turn into ext2 rather than ffs) > > The other 2 boxes will, of course, stay FreeBSD. You'd switch operating systems for the sake of a sound card? That seems backwards to this correspondent. Just buy a reasonable sound card that works under your system of choice; they're less expensive than a system installation. > I generally get the feeling that `Workstation Hardware'[1] has a better > chance of being supported under Linux than FreeBSD. I may be talking rubbish, > though ;-) > > [1] SoundCards; funky USB magic to talk to your digital camera; that kind of > thing. USB? Linux? I don't think so. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 19:12:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (dyna225-091.nada.kth.se [130.237.225.91]) by builder.freebsd.org (Postfix) with ESMTP id AE22F3EC1 for ; Thu, 3 Feb 2000 19:12:31 -0800 (PST) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id EAA77555; Fri, 4 Feb 2000 04:12:55 +0100 (CET) (envelope-from assar) To: Jonas =?iso-8859-1?q?B=FClow?= Cc: FreeBSD Hackers Subject: Re: Installing -current References: <38993C48.B32B6BBC@parallelconsulting.com> From: Assar Westerlund Date: 04 Feb 2000 04:12:54 +0100 In-Reply-To: Jonas =?iso-8859-1?q?B=FClow's?= message of "Thu, 03 Feb 2000 09:28:56 +0100" Message-ID: <5lhffpsls9.fsf@assaris.sics.se> Lines: 16 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonas Bülow writes: > Hi, Hej. > What is the easiest way to install FreeBSD-current? Grab floopies and install over FTP from current.freebsd.org. And then run cvsup if you want to update to even more current code. > Before I ran into trouble I want to ask if 4.0 supports the > 3CCFE574BT NIC? (3com 3c574). It looks that way. I haven't had the occasion to try myself. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 20: 5:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by builder.freebsd.org (Postfix) with SMTP id 440FD3F06; Thu, 3 Feb 2000 20:05:40 -0800 (PST) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id XAA10688; Thu, 3 Feb 2000 23:09:47 -0500 From: Bill Paul Message-Id: <200002040409.XAA10688@skynet.ctr.columbia.edu> Subject: Re: Suggestions for Gigabit cards for -CURRENT To: ken@kdm.org (Kenneth D. Merry) Date: Thu, 3 Feb 2000 23:09:46 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: <20000203193710.A57242@panzer.kdm.org> from "Kenneth D. Merry" at Feb 3, 2000 07:37:10 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2859 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Kenneth D. Merry had to walk into mine and say: > > [ Thanks for the info Bill! ] No problemo. [...] > > Both the Alteon and SysKonnect NICs are 64-bit PCI cards. (Actually, I'm > > pretty sure all of the PCI gigabit NICs are 64-bit.) Both kinds of cards > > can do jumbograms on FreeBSD. Also, both vendors have released pretty good > > hardware documentation, which makes them good choices for custom applications, > > if you're into that sort of thing. > > Alteon also provides firmware source, which can really come in handy. Do > you know if SysKonnect has released firmware? The SysKonnect GEnesis controller and the XaQti XMAC II chips are both static devices and do not require firmware. If you go to www.syskonnect.com and search their online knowledge base for the word "manual" you should be able to find the gigabit NIC programmer's manual. Similarly, XaQti has the full datasheet for the XMAC II at www.xaqti.com somewhere. (As I recall, you have to go through a brief registration procedure to get it, but once that's done you should be able to download it right away.) Talking of the XMAC II, there's one other thing I forgot to mention earlier. The FreeBSD sk driver does jumbo frames, but the SysKonnect drivers don't. At least, not yet. The XMAC II's receive FIFO is 8K. By default, the chip operates in 'store and forward' mode in order to perform error checking on received frames (it has to get the entire frame in the FIFO in order to do a CRC on it, I think). This is fine for normal frames, but if you want to handle jumbograms larger than 8192 bytes, you have to put the chip into 'streaming' mode, otherwise any frame larger than 8192 bytes will be truncated. To get 'streaming' mode to work, you have to disable all of the RX error checking. Also, the default TX FIFO threshold on the XMAC is very small (8 bytes, I think). The FreeBSD sk driver bumps this up a bit (to 512 bytes, if I remember correctly). This is to deal with the case where you have a dual port card and are pumping data through both XMAC chips at once: with the default FIFO threshold, I would often see TX FIFO underruns from one of the XMACs and performance on that port would get spotty. I think the total TX FIFO memory on the XMAC II is 2K. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 23:24:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by builder.freebsd.org (Postfix) with ESMTP id CE28D43EB; Thu, 3 Feb 2000 23:24:40 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA59394; Fri, 4 Feb 2000 00:24:47 -0700 (MST) (envelope-from ken) Date: Fri, 4 Feb 2000 00:24:46 -0700 From: "Kenneth D. Merry" To: Bill Paul Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Suggestions for Gigabit cards for -CURRENT Message-ID: <20000204002446.A59300@panzer.kdm.org> References: <20000203193710.A57242@panzer.kdm.org> <200002040409.XAA10688@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002040409.XAA10688@skynet.ctr.columbia.edu>; from wpaul@skynet.ctr.columbia.edu on Thu, Feb 03, 2000 at 11:09:46PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 03, 2000 at 23:09:46 -0500, Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Kenneth D. Merry had > to walk into mine and say: > > > > > Alteon also provides firmware source, which can really come in handy. Do > > you know if SysKonnect has released firmware? > > The SysKonnect GEnesis controller and the XaQti XMAC II chips are both static > devices and do not require firmware. If you go to www.syskonnect.com and > search their online knowledge base for the word "manual" you should be > able to find the gigabit NIC programmer's manual. Similarly, XaQti has > the full datasheet for the XMAC II at www.xaqti.com somewhere. (As I recall, > you have to go through a brief registration procedure to get it, but once > that's done you should be able to download it right away.) Well, all-hardware designs can be great when they're done right, and irritating when they're not. Thanks for the manual pointers. I've got the SysKonnect manual, and it seems pretty nifty. > Talking of the XMAC II, there's one other thing I forgot to mention earlier. > The FreeBSD sk driver does jumbo frames, but the SysKonnect drivers don't. > At least, not yet. The XMAC II's receive FIFO is 8K. By default, the chip > operates in 'store and forward' mode in order to perform error checking on > received frames (it has to get the entire frame in the FIFO in order to > do a CRC on it, I think). This is fine for normal frames, but if you want > to handle jumbograms larger than 8192 bytes, you have to put the chip into > 'streaming' mode, otherwise any frame larger than 8192 bytes will be truncated. > To get 'streaming' mode to work, you have to disable all of the RX error > checking. That is unfortunate, since it means you can't do checksum offloading with jumbo frames. FWIW, of the three gigabit ethernet implementations I've seen anything of (Alteon, Intel, SysKonnect), none have implemented all of the hooks necessary for a seamless zero copy receive implementation. Alteon comes the closest, but they don't support splitting out the headers (yet), which is a requirement for us. The only way to do zero copy receive with our VM architecture (that I know of) is page flipping, i.e. receive the page in the kernel, and then trade it for the user's page. You can't do it on anything less than page-sized granularity, and things have to be page aligned. (The IO-Lite stuff from Rice is an exception to all this.) The nice thing about the Alteon boards, though, is that you can modify the firmware, and so header splitting is an option there. It would even be possible to split the headers off of IPv6 packets, or any other protocol that you have knowlege of. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 3 23:38:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by builder.freebsd.org (Postfix) with ESMTP id 37A883E37 for ; Thu, 3 Feb 2000 23:38:12 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA20303 for ; Fri, 4 Feb 2000 00:38:25 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA34757 for ; Fri, 4 Feb 2000 00:38:44 -0700 (MST) Message-Id: <200002040738.AAA34757@harmony.village.org> To: hackers@freebsd.org Subject: mounting openbsd disks Date: Fri, 04 Feb 2000 00:38:44 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a need to mount a disk that was partitioned and labeled on OpenBSD. I'm getting the following errors when I try: # disklabel ad2 disklabel: ioctl DIOCGDINFO: Invalid argument Any chance I can tweak something small and get access to these disks. Here's what fdisk has to say: Information from DOS bootblock is: The data for partition 1 is: sysid 4,(Primary DOS with 16 bit FAT (<= 32MB)) start 63, size 20480 (10 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 20/ sector 5/ head 6 The data for partition 2 is: sysid 166,(OpenBSD) start 20543, size 4198945 (2050 Meg), flag 0 beg: cyl 1023/ sector 63/ head 255; end: cyl 1023/ sector 63/ head 255 The data for partition 3 is: The data for partition 4 is: Of course I can mount slice 1, but have had no luck with slice 2. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 0:20:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by builder.freebsd.org (Postfix) with SMTP id 3F835441D; Fri, 4 Feb 2000 00:20:21 -0800 (PST) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id DAA11089; Fri, 4 Feb 2000 03:24:29 -0500 From: Bill Paul Message-Id: <200002040824.DAA11089@skynet.ctr.columbia.edu> Subject: Re: Suggestions for Gigabit cards for -CURRENT To: ken@kdm.org (Kenneth D. Merry) Date: Fri, 4 Feb 2000 03:24:28 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: <20000204002446.A59300@panzer.kdm.org> from "Kenneth D. Merry" at Feb 4, 2000 00:24:46 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2833 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Kenneth D. Merry had to walk into mine and say: > > Talking of the XMAC II, there's one other thing I forgot to mention earlier. > > The FreeBSD sk driver does jumbo frames, but the SysKonnect drivers don't. > > At least, not yet. The XMAC II's receive FIFO is 8K. By default, the chip > > operates in 'store and forward' mode in order to perform error checking on > > received frames (it has to get the entire frame in the FIFO in order to > > do a CRC on it, I think). This is fine for normal frames, but if you want > > to handle jumbograms larger than 8192 bytes, you have to put the chip into > > 'streaming' mode, otherwise any frame larger than 8192 bytes will be truncated. > > To get 'streaming' mode to work, you have to disable all of the RX error > > checking. > > That is unfortunate, since it means you can't do checksum offloading with > jumbo frames. Uhm. I'm not sure about that. The 8K FIFO limitation is in the XMAC II, not in the GEnesis controller. And I believe it's the GEnesis that actually does the hardware checksumming stuff. Oh, and the XMAC appears to have a 4K TX FIFO, not 2K. My mistake. > FWIW, of the three gigabit ethernet implementations I've seen anything of > (Alteon, Intel, SysKonnect), none have implemented all of the hooks > necessary for a seamless zero copy receive implementation. > > Alteon comes the closest, but they don't support splitting out the headers > (yet), which is a requirement for us. The only way to do zero copy receive > with our VM architecture (that I know of) is page flipping, i.e. receive > the page in the kernel, and then trade it for the user's page. You can't > do it on anything less than page-sized granularity, and things have to be > page aligned. (The IO-Lite stuff from Rice is an exception to all this.) > > The nice thing about the Alteon boards, though, is that you can modify the > firmware, and so header splitting is an option there. It would even be > possible to split the headers off of IPv6 packets, or any other protocol > that you have knowlege of. If you can actually modify the firmware to do this then you have a lot more guru points than I do. :) I've looked at the Alteon firmware code but it's all quite opaque to me. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 1: 0:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by builder.freebsd.org (Postfix) with ESMTP id C86D643F1; Fri, 4 Feb 2000 01:00:48 -0800 (PST) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id KAA02389; Fri, 4 Feb 2000 10:00:35 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: Wes Peters , Thomas David Rivers , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: IBM releases JFS for Linux. In-reply-to: Your message of "Fri, 04 Feb 2000 13:04:27 +1030." <20000204130426.C27530@freebie.lemis.com> Date: Fri, 04 Feb 2000 10:00:34 +0100 Message-ID: <2387.949654834@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000204130426.C27530@freebie.lemis.com>, Greg Lehey writes: >I've taken a look, and there's as good as no docco. It's an OS/2 >version, which suggests to me that it would be more difficult to port >than the original AIX version. I might get back to it again later on, >but don't hold your breath. No, in fact the AIX version was so hard to port that OSF eventually had to give up trying. It was rather closely married to the VM hardware on the Power CPU. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 1:38:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scrooge.parallelconsulting.com (www.parallelconsulting.com [195.242.42.108]) by builder.freebsd.org (Postfix) with ESMTP id E5FD13E37 for ; Fri, 4 Feb 2000 01:38:11 -0800 (PST) Received: from parallelconsulting.com ([10.1.1.42]) by scrooge.parallelconsulting.com (Netscape Messaging Server 3.6) with ESMTP id AAA33FC; Fri, 4 Feb 2000 10:38:33 +0100 Message-ID: <389A9DF5.87EEF514@parallelconsulting.com> Date: Fri, 04 Feb 2000 10:37:57 +0100 From: Jonas =?iso-8859-1?Q?B=FClow?= Organization: Parallel Consulting Group X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Assar Westerlund Cc: FreeBSD Hackers Subject: Re: Installing -current References: <38993C48.B32B6BBC@parallelconsulting.com> <5lhffpsls9.fsf@assaris.sics.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Before I ran into trouble I want to ask if 4.0 supports the > > 3CCFE574BT NIC? (3com 3c574). > > It looks that way. I haven't had the occasion to try myself. It worked! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 3: 9:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lindt.urgle.com (lindt.urgle.com [195.173.172.169]) by builder.freebsd.org (Postfix) with ESMTP id F33183F4A for ; Fri, 4 Feb 2000 03:09:16 -0800 (PST) Received: from mike by lindt.urgle.com with local (Exim 3.03 #1) id 12Ggc4-0003Ub-00; Fri, 04 Feb 2000 11:09:20 +0000 Date: Fri, 4 Feb 2000 11:09:20 +0000 From: Mike Bristow To: Wes Peters Cc: Alex Zepeda , freebsd-hackers@freebsd.org Subject: Re: Re/Fwd: freebsd specific search Message-ID: <20000204110920.A13417@lindt.urgle.com> References: <20000203123135.A10816@lindt.urgle.com> <389A403C.76F0D62F@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <389A403C.76F0D62F@softweyr.com>; from wes@softweyr.com on Thu, Feb 03, 2000 at 07:58:04PM -0700 X-Rated: Honduras, NORAD, IRA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 03, 2000 at 07:58:04PM -0700, Wes Peters wrote: > Mike Bristow wrote: > > > > True; but linux has support for a bigger variety of soundcards > > (my Win98^H^H^H^H^H^HEverQuest machine now has a Live! in it; supported > > under Linux but not under FreeBSD AFAIK; so the other half of the disk > > may turn turn into ext2 rather than ffs) > > > > The other 2 boxes will, of course, stay FreeBSD. > > You'd switch operating systems for the sake of a sound card? That seems > backwards to this correspondent. Just buy a reasonable sound card that > works under your system of choice; they're less expensive than a system > installation. You're right of course. But the system of choice is EverQuest[1], not FreeBSD. 98% of the time it's on, it's running Windows. Until Verant produce a linux or FreeBSD or BeOS or whatever client, I don't have any choice in the matter. [1] at the moment. It'll probably change to some other game later. -- Mike Bristow, Geek At Large ``Beware of Invisible Cows'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 4:51: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by builder.freebsd.org (Postfix) with ESMTP id 97E373F4A for ; Fri, 4 Feb 2000 04:51:03 -0800 (PST) Received: from earth.fxp (oca-p1-17.hitter.net [207.192.76.17]) by pawn.primelocation.net (Postfix) with ESMTP id 53E549B1C; Fri, 4 Feb 2000 07:51:15 -0500 (EST) Date: Fri, 4 Feb 2000 07:51:20 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: Warner Losh Cc: hackers@freebsd.org Subject: Re: mounting openbsd disks In-Reply-To: <200002040738.AAA34757@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 Feb 2000, Warner Losh wrote: > I have a need to mount a disk that was partitioned and labeled on > OpenBSD. I'm getting the following errors when I try: > > # disklabel ad2 > disklabel: ioctl DIOCGDINFO: Invalid argument > root@earth:~# disklabel ad1 disklabel: ioctl DIOCGDINFO: Invalid argument root@earth:~# disklabel /dev/ad1s4 *snip* 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 524097 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 519*) b: 1048320 524097 swap # (Cyl. 519*- 1559) c: 16450497 0 unused 0 0 # (Cyl. 0 - 16319*) e: 262080 1572417 4.2BSD 1024 8192 16 # (Cyl. 1559*- 1819) f: 4194288 1834497 4.2BSD 1024 8192 16 # (Cyl. 1819*- 5980) root@earth:~# mount /dev/ad1s4a /mnt root@earth:~# ls /mnt .cshrc boot emul root tmp .profile bsd etc sbin usr altroot bsd.old home stand var bin dev mnt sys root@earth:~# ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: 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 Feb 4 4:56:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from corpmx1.ess.harris.com (corpmx1.ess.harris.com [130.41.65.49]) by builder.freebsd.org (Postfix) with ESMTP id 6ADA13F4A for ; Fri, 4 Feb 2000 04:56:55 -0800 (PST) Received: by corpmx1 with Internet Mail Service (5.5.2650.21) id ; Fri, 4 Feb 2000 07:57:08 -0500 Message-ID: From: "Potts, Ross" To: "'freeBSD-hackers@freebsd.org'" Subject: Disposable PCs? Date: Fri, 4 Feb 2000 07:57:04 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just rejoined the list after a couple years layoff, so I felt compelled to submit this. I finished reading an article on www.tomshardware.com that said Samsung is trying to make disposable PCs. Cost would be around $200. When I followed the link to get more details it finished with speculation that the could be on a level with or beyond PIIIs. CAN YOU SAY CHEAP CLUSTERING? (pardon me while I wipe the drool offin' my lip) Ross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 4:59:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from corpmx3.CORP.HARRIS.COM (corpmx3.corp.harris.com [137.237.103.9]) by builder.freebsd.org (Postfix) with ESMTP id 9EB9040C6 for ; Fri, 4 Feb 2000 04:59:19 -0800 (PST) Received: by corpmx3 with Internet Mail Service (5.5.2650.21) id <1FVZDHZF>; Fri, 4 Feb 2000 07:59:38 -0500 Message-ID: From: "Potts, Ross" To: "'freebsd-hackers@freeBSD.org'" Subject: Date: Fri, 4 Feb 2000 07:59:33 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth fcec1a83 subscribe freebsd-hackers rpotts@harris.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 5:26:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from meestal.stack.nl (meestal.stack.nl [131.155.140.139]) by builder.freebsd.org (Postfix) with ESMTP id 147B43E54 for ; Fri, 4 Feb 2000 05:26:46 -0800 (PST) Received: from toad.stack.nl (toad.stack.nl [131.155.140.135]) by meestal.stack.nl (Postfix) with ESMTP id 703B410341 for ; Fri, 4 Feb 2000 14:27:01 +0100 (MET) Received: by toad.stack.nl (Postfix, from userid 816) id BAD1396D7; Fri, 4 Feb 2000 14:27:01 +0100 (CET) Subject: elf To: freebsd-hackers@freebsd.org Date: Fri, 4 Feb 2000 14:27:01 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000204132701.BAD1396D7@toad.stack.nl> From: marcov@stack.nl (Marco van de Voort) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How can I disassemble ELF programs? I need to create my own startup code for FPC programs. (copying some variables before pascal code startup) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 6:19:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lame.xnet.is (fire.xnet.is [194.144.122.122]) by builder.freebsd.org (Postfix) with ESMTP id D3D2D4048 for ; Fri, 4 Feb 2000 06:19:47 -0800 (PST) Date: Fri, 4 Feb 2000 14:23:16 +0000 (GMT) From: Einar Orn Eidsson To: "Potts, Ross" Cc: "'freeBSD-hackers@freebsd.org'" Subject: Re: Disposable PCs? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's interesting, I can't find the link on Tom's page though, either I'm blind or I'm having a premature hangover. Could you post the URL? | Einar Orn Eidsson | Tel: +354-696-1352 | SMS: 6961352@sms.tal.is | ICQ: 8818678 ---------------------- -- - - - - On Fri, 4 Feb 2000, Potts, Ross wrote: > I just rejoined the list after a couple years layoff, so I felt compelled to > submit this. > > I finished reading an article on www.tomshardware.com that said Samsung is > trying to make disposable PCs. > Cost would be around $200. When I followed the link to get more details it > finished with speculation that the could be on a level with or beyond PIIIs. > > CAN YOU SAY CHEAP CLUSTERING? (pardon me while I wipe the drool offin' my lip) > > Ross > > > 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 Fri Feb 4 7:24:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mx.globalone.ru (mx.globalone.ru [194.84.254.251]) by builder.freebsd.org (Postfix) with ESMTP id 9176C41B8 for ; Fri, 4 Feb 2000 07:24:38 -0800 (PST) Received: from hq.globalone.ru (hq.globalone.ru [172.16.38.1]) by mx.globalone.ru (8.9.3/8.9.3) with ESMTP id SAA14537 for ; Fri, 4 Feb 2000 18:24:52 +0300 Received: from host205.spb.in.rosprin.ru ([172.17.13.205]) by hq.globalone.ru (Netscape Messaging Server 3.62) with SMTP id 716; Fri, 4 Feb 2000 18:24:56 +0300 Message-ID: <35ae01bf6f24$4d8c2840$cd0d11ac@host205.spb.in.rosprin.ru> Reply-To: "Alexander Voropay" From: "Alexander Voropay" To: Cc: Subject: Re: elf Date: Fri, 4 Feb 2000 18:26:19 +0300 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 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marco van de Voort wrote: >How can I disassemble ELF programs? Try IDA PRO : http://www.datarescue.com/ida.htm http://www.rosprombank.ru/~ig/ -- -=AV=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 7:25:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by builder.freebsd.org (Postfix) with ESMTP id BBFAC40EE for ; Fri, 4 Feb 2000 07:25:16 -0800 (PST) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id KAA66453; Fri, 4 Feb 2000 10:25:30 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200002041525.KAA66453@server.baldwin.cx> 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: <20000204132701.BAD1396D7@toad.stack.nl> Date: Fri, 04 Feb 2000 10:25:29 -0500 (EST) From: John Baldwin To: (Marco van de Voort) Subject: RE: elf Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Feb-00 Marco van de Voort wrote: > > > How can I disassemble ELF programs? > > I need to create my own startup code for FPC programs. > (copying some variables before pascal code startup) Try 'objdump -d'. It's more readable if you don't strip the program. You can also use this to disassemble object files as well, so you could just 'objdump -d /usr/lib/crt0.o'. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "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 Feb 4 11:35:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by builder.freebsd.org (Postfix) with ESMTP id 2198F4557; Fri, 4 Feb 2000 11:33:23 -0800 (PST) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 12GoTl-000PHF-0W; Fri, 4 Feb 2000 19:33:17 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id TAA01021; Fri, 4 Feb 2000 19:22:12 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 4 Feb 2000 19:36:53 +0000 (GMT) From: Doug Rabson To: John Baldwin Cc: marcov@stack.nl, freebsd-hackers@freebsd.org Subject: RE: elf In-Reply-To: <200002041525.KAA66453@server.baldwin.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 Feb 2000, John Baldwin wrote: > > On 04-Feb-00 Marco van de Voort wrote: > > > > > > How can I disassemble ELF programs? > > > > I need to create my own startup code for FPC programs. > > (copying some variables before pascal code startup) > > Try 'objdump -d'. It's more readable if you don't strip the program. > You can also use this to disassemble object files as well, so you > could just 'objdump -d /usr/lib/crt0.o'. My favourite is 'objdump -dS' to include source code. This obviously requires debugging information in the disassembled thing. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 12: 0:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from corpmx1.ess.harris.com (corpmx1.ess.harris.com [130.41.65.49]) by builder.freebsd.org (Postfix) with ESMTP id EA43A469F for ; Fri, 4 Feb 2000 12:00:17 -0800 (PST) Received: by corpmx1 with Internet Mail Service (5.5.2650.21) id ; Fri, 4 Feb 2000 14:15:09 -0500 Message-ID: From: "Potts, Ross" To: 'Einar Orn Eidsson' Cc: "'freeBSD-hackers@freebsd.org'" Subject: RE: Disposable PCs? Date: Fri, 4 Feb 2000 14:15:06 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, here it is. It's dated today(4 Feb 2000). www.tomshardware.com/technews/index.html#0619. -----Original Message----- From: Einar Orn Eidsson [SMTP:eoe@lame.xnet.is] Sent: Friday, February 04, 2000 9:23 AM To: Potts, Ross Cc: 'freeBSD-hackers@freebsd.org' Subject: Re: Disposable PCs? That's interesting, I can't find the link on Tom's page though, either I'm blind or I'm having a premature hangover. Could you post the URL? | Einar Orn Eidsson | Tel: +354-696-1352 | SMS: 6961352@sms.tal.is | ICQ: 8818678 ---------------------- -- - - - - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 12: 1: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by builder.freebsd.org (Postfix) with ESMTP id 96E0A469D for ; Fri, 4 Feb 2000 12:01:02 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA21671; Fri, 4 Feb 2000 09:31:34 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA36603; Fri, 4 Feb 2000 09:31:57 -0700 (MST) Message-Id: <200002041631.JAA36603@harmony.village.org> To: "Chris D. Faulhaber" Subject: Re: mounting openbsd disks Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 04 Feb 2000 07:51:20 EST." References: Date: Fri, 04 Feb 2000 09:31:56 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Chris D. Faulhaber" writes: : root@earth:~# disklabel ad1 : disklabel: ioctl DIOCGDINFO: Invalid argument : root@earth:~# disklabel /dev/ad1s4 disklabel /dev/ad2s2 (which is the OpenBSD partition) fails with the same error. Mounting claims a bad magic number. This is an OpenBSD/arc disk which has a slightly different disklabel I think (since when I say disklabel on the OpenBSD/arc machine I get 16 partitions. Changing the id of the slice doesn't help either. :-( Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 12:11:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.monmouth.com (shell.monmouth.com [209.191.58.1]) by builder.freebsd.org (Postfix) with ESMTP id E07314AE7 for ; Fri, 4 Feb 2000 12:11:22 -0800 (PST) Received: from bg-tc-ppp600.monmouth.com (root@bg-tc-ppp600.monmouth.com [209.191.59.34]) by shell.monmouth.com (8.9.3/8.9.3) with ESMTP id OAA18141 for ; Fri, 4 Feb 2000 14:54:07 -0500 (EST) Received: (from pechter@localhost) by bg-tc-ppp600.monmouth.com (8.9.3/8.9.3) id OAA06981 for freebsd-hackers@freebsd.org; Fri, 4 Feb 2000 14:57:18 -0500 (EST) (envelope-from pechter) From: Bill Pechter Message-Id: <200002041957.OAA06981@bg-tc-ppp600.monmouth.com> Subject: JFS and IBM To: freebsd-hackers@freebsd.org Date: Fri, 4 Feb 2000 14:57:18 -0500 (EST) Reply-To: bpechter@shell.monmouth.com X-Phone-Number: 732-935-0629 X-OS-Type: FreeBSD 4.0-CURRENT X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, while some of us were at Linux expo talking about journaling file systems and *BSD, IBM released jfs to the GPL. Is there anyone working on this as a gpl'd add-in to *BSD? Is this as much of a surprise to all of you as to me... I thought jfs would remain a tightly held OSF/1 component that would never see "free" status. We live in interesting times, indeed. Bill ------------------------------------------------------------------------------- bpechter@monmouth.com|pechter@pechter.dyndns.org|pechter@pechter.bsdonline.org Three things never anger: First, the one who runs your DEC, The one who does Field Service and the one who signs your check. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 12:15:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (ip46-106.eventsdigital.com [160.79.46.106]) by builder.freebsd.org (Postfix) with ESMTP id D5B7542E3; Fri, 4 Feb 2000 12:15:34 -0800 (PST) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA03217; Fri, 4 Feb 2000 09:42:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002041742.JAA03217@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Baldwin Cc: marcov@stack.nl (Marco van de Voort), freebsd-hackers@FreeBSD.org Subject: Re: elf In-reply-to: Your message of "Fri, 04 Feb 2000 10:25:29 EST." <200002041525.KAA66453@server.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Feb 2000 09:42:13 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 04-Feb-00 Marco van de Voort wrote: > > > > > > How can I disassemble ELF programs? > > > > I need to create my own startup code for FPC programs. > > (copying some variables before pascal code startup) > > Try 'objdump -d'. It's more readable if you don't strip the program. > You can also use this to disassemble object files as well, so you > could just 'objdump -d /usr/lib/crt0.o'. The question is not "how" but "why"? You already have access to the source... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 12:23:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id 23EA348C4 for ; Fri, 4 Feb 2000 12:23:19 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id IAA25085; Fri, 4 Feb 2000 08:16:04 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id IAA10608; Fri, 4 Feb 2000 08:16:04 -0800 Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id IAA18193; Fri, 4 Feb 2000 08:15:59 -0800 (PST) Message-ID: <389AFC92.32FC14@softweyr.com> Date: Fri, 04 Feb 2000 09:21:38 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Marco van de Voort Cc: freebsd-hackers@freebsd.org Subject: Re: elf References: <20000204132701.BAD1396D7@toad.stack.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marco van de Voort wrote: > > How can I disassemble ELF programs? objdump --disassemble -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 12:26:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from meestal.stack.nl (meestal.stack.nl [131.155.140.139]) by builder.freebsd.org (Postfix) with ESMTP id 02A6148CE for ; Fri, 4 Feb 2000 12:26:15 -0800 (PST) Received: from toad.stack.nl (toad.stack.nl [131.155.140.135]) by meestal.stack.nl (Postfix) with ESMTP id 6E3DF10341 for ; Fri, 4 Feb 2000 17:13:24 +0100 (MET) Received: by toad.stack.nl (Postfix, from userid 816) id B2DE396D7; Fri, 4 Feb 2000 17:13:24 +0100 (CET) Subject: how to compile without libc (so not static) To: freebsd-hackers@freebsd.org Date: Fri, 4 Feb 2000 17:13:24 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000204161324.B2DE396D7@toad.stack.nl> From: marcov@stack.nl (Marco van de Voort) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I finished the syscalls, so now I moved on the initialisation code. To test that I try to create an empty binary, which doesn't link to libc: I've put in an hour effort, and wrote the following C file: int main (void) { return 0; } gcc -nostdlib empty.c /usr/lib/crti.o /usr/lib/crt0.o -o empty results in: /usr/lib/crt1.o: In function `_start': /usr/lib/crt1.o(.text+0x4f): undefined reference to `atexit' /usr/lib/crt1.o(.text+0x5c): undefined reference to `atexit' /usr/lib/crt1.o(.text+0x6f): undefined reference to `exit' with a grep exit *.o in /usr/lib doesn't find me that label. What am I missing? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 13:47:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by builder.freebsd.org (Postfix) with ESMTP id 359BA40B2 for ; Fri, 4 Feb 2000 13:47:05 -0800 (PST) Received: from bsd1.nyct.net (mbac@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id QAA27637 for ; Fri, 4 Feb 2000 16:47:21 -0500 (EST) (envelope-from mbac@nyct.net) Received: from localhost (mbac@localhost) by bsd1.nyct.net (8.8.8/8.9.3) with ESMTP id QAA05939 for ; Fri, 4 Feb 2000 16:47:20 -0500 (EST) (envelope-from mbac@nyct.net) X-Authentication-Warning: bsd1.nyct.net: mbac owned process doing -bs Date: Fri, 4 Feb 2000 16:47:20 -0500 (EST) From: Michael Bacarella To: freebsd-hackers@FreeBSD.org Subject: General lameness regarding exec() Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I patch my systems to log exec() calls because I think it's useful, but I really don't know how to go about making it a general contribution. Anyone like this idea? Any Suggestions for how I should really implement it? I basically have it end up in syslog, along with who called it and what their credentials were. This is in contrast to process accounting, which only records information on processes which have terminated. /* ---------- Michael Bacarella( mbac@nyct.net ) | (212) 293-2620 Administration / Development / Support | http://nyct.net/ [ N e w Y o r k C o n n e c t . N E T ] | info@nyct.net Bringing New York The Internet Service It Deserves! --------- */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 13:53:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by builder.freebsd.org (Postfix) with ESMTP id 781D33E75 for ; Fri, 4 Feb 2000 13:53:26 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA22476; Fri, 4 Feb 2000 14:53:45 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA00969; Fri, 4 Feb 2000 14:53:34 -0700 (MST) Message-Id: <200002042153.OAA00969@harmony.village.org> To: marcov@stack.nl (Marco van de Voort) Subject: Re: how to compile without libc (so not static) Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 04 Feb 2000 17:13:24 +0100." <20000204161324.B2DE396D7@toad.stack.nl> References: <20000204161324.B2DE396D7@toad.stack.nl> Date: Fri, 04 Feb 2000 14:53:34 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000204161324.B2DE396D7@toad.stack.nl> Marco van de Voort writes: : /usr/lib/crt1.o: In function `_start': : /usr/lib/crt1.o(.text+0x4f): undefined reference to `atexit' : /usr/lib/crt1.o(.text+0x5c): undefined reference to `atexit' : /usr/lib/crt1.o(.text+0x6f): undefined reference to `exit' : in /usr/lib doesn't find me that label. : : What am I missing? nm /usr/lib/crt1.o | egrep exit U atexit U exit Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 14: 1: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by builder.freebsd.org (Postfix) with ESMTP id 31DED4020 for ; Fri, 4 Feb 2000 14:01:03 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA36822; Fri, 4 Feb 2000 17:00:32 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200002041957.OAA06981@bg-tc-ppp600.monmouth.com> References: <200002041957.OAA06981@bg-tc-ppp600.monmouth.com> Date: Fri, 4 Feb 2000 17:00:42 -0500 To: bpechter@shell.monmouth.com, freebsd-hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: JFS and IBM Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:57 PM -0500 2/4/00, Bill Pechter wrote: >Folks, while some of us were at Linux expo talking about journaling >file systems and *BSD, IBM released jfs to the GPL. > >Is there anyone working on this as a gpl'd add-in to *BSD? People outside the expo heard about it too, and there has been an active thread in hackers about this already. Review that thread, so we don't have to go over all the same comments again. There is also something about it at http://daily.daemonnews.org/, which had some interesting pointers. >Is this as much of a surprise to all of you as to me... I thought jfs >would remain a tightly held OSF/1 component that would never see >"free" status. Actually it didn't surprise me too much. IBM realizes it makes it's money in selling hardware and services. They don't have a whole lot to lose by making this JFS source code available, and they might have a fair amount to gain, as they position themselves as a good company to contact for "linux support services". --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 14:20: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id B286C3EB5 for ; Fri, 4 Feb 2000 14:20:01 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id OAA05649; Fri, 4 Feb 2000 14:19:13 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id OAA14788; Fri, 4 Feb 2000 14:19:13 -0800 Received: from softweyr.com (dyn5.utah.xylan.com [198.206.184.241]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id OAA10349; Fri, 4 Feb 2000 14:19:09 -0800 (PST) Message-ID: <389B51B1.BAFD8944@softweyr.com> Date: Fri, 04 Feb 2000 15:24:49 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Potts, Ross" Cc: "'Einar Orn Eidsson'" , "'freeBSD-hackers@freebsd.org'" Subject: Re: Disposable PCs? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Potts, Ross" wrote: > > Okay, here it is. It's dated today(4 Feb 2000). > > www.tomshardware.com/technews/index.html#0619. For the full scoop, see http://www.theregister.co.uk/000203-000022.html If you post complete URLs, *some* of us can just click on them in our mailers. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 14:24: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id 5BCB94293 for ; Fri, 4 Feb 2000 14:23:23 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id OAA05727; Fri, 4 Feb 2000 14:22:55 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id OAA15008; Fri, 4 Feb 2000 14:22:55 -0800 Received: from softweyr.com (dyn5.utah.xylan.com [198.206.184.241]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id OAA10592; Fri, 4 Feb 2000 14:22:54 -0800 (PST) Message-ID: <389B5292.A7A8B6D4@softweyr.com> Date: Fri, 04 Feb 2000 15:28:34 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: bpechter@shell.monmouth.com Cc: freebsd-hackers@freebsd.org Subject: Re: JFS and IBM References: <200002041957.OAA06981@bg-tc-ppp600.monmouth.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Pechter wrote: > > Folks, while some of us were at Linux expo talking about journaling file > systems and *BSD, IBM released jfs to the GPL. > > Is there anyone working on this as a gpl'd add-in to *BSD? You apparently haven't noticed the war of words going on on http://daily.daemonnews.org/ on this very topic? I think this is going to be our most "popular", or at least commented on, article to date. Greg Lehey has downloaded the code and looked at it. Despite my cheering and enthusiasm, he reports that we should wait until he actually produces something to pronounce him a hero. ;^) > Is this as much of a surprise to all of you as to me... I thought jfs > would remain a tightly held OSF/1 component that would never see > "free" status. It's released under GPL, so it's still not free. It is available, though. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 16:34: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by builder.freebsd.org (Postfix) with ESMTP id E9F1A43E3 for ; Fri, 4 Feb 2000 16:34:02 -0800 (PST) Received: by mimer.webgiro.com (Postfix, from userid 66) id 919872DC07; Sat, 5 Feb 2000 01:33:50 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id D94177811; Sat, 5 Feb 2000 01:34:20 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id D494810E12; Sat, 5 Feb 2000 01:34:20 +0100 (CET) Date: Sat, 5 Feb 2000 01:34:20 +0100 (CET) From: Andrzej Bialecki To: Michael Bacarella Cc: freebsd-hackers@FreeBSD.org Subject: Re: General lameness regarding exec() In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 Feb 2000, Michael Bacarella wrote: > > I patch my systems to log exec() calls because I think it's useful, but I > really don't know how to go about making it a general contribution. > > Anyone like this idea? Any Suggestions for how I should really implement > it? Have a look at: http://www.freebsd.org/~abial/spy/README Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 16:58:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by builder.freebsd.org (Postfix) with ESMTP id DBAB74389 for ; Fri, 4 Feb 2000 16:58:12 -0800 (PST) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id QAA16411; Fri, 4 Feb 2000 16:58:00 -0800 (PST) From: Archie Cobbs Message-Id: <200002050058.QAA16411@bubba.whistle.com> Subject: Re: Removing interfaces In-Reply-To: <200002030534.WAA10257@harmony.village.org> from Warner Losh at "Feb 2, 2000 10:34:04 pm" To: imp@village.org (Warner Losh) Date: Fri, 4 Feb 2000 16:58:00 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > : With all the PCMCIA card stuff going on, is it now possible to > : remove a networking interface in FreeBSD (from within the kernel)? > : > : If so could someone show me an example how. I'd like to implement > : this in the ng_iface(8) netgraph node type. > > if_detach() is supposed to do this, but there are theoretical problems > with our implementation of it. Also, there needs to be some way to > propigate the "gone"ness of the interface generically rather than the > ad-hoc way we do it now. Thanks, that works great (so far :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 18:22: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by builder.freebsd.org (Postfix) with ESMTP id D3C28430F for ; Fri, 4 Feb 2000 18:21:58 -0800 (PST) Received: from river ([10.0.128.30]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with SMTP id 227; Fri, 4 Feb 2000 18:18:35 -0800 Message-ID: <185c01bf6f7f$bb381dd0$1e80000a@avantgo.com> From: "Scott Hess" To: "Matthew Dillon" Cc: References: <01b301bf6824$46e928a0$1e80000a@avantgo.com> <200001262330.PAA16635@apollo.backplane.com> Subject: Re: aio_read crashing certain kernels. Date: Fri, 4 Feb 2000 18:21:37 -0800 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.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew Dillon" wrote: > If you can reproduce the bug easily, can you post the program that > causes it plus instructions on how to reproduce the bug? If one of us > can reproduce it we may be able to squeeze more info out of the crash. Sorry I took so long to follow-up on this. The issue is definitely, definitely, definitely related to SMP. On a 3.3-RELEASE kernel compiled without SMP support, my various aio_read() based programs work fine, I've probably pushed terabytes through them by now. On a kernel with SMP support, it locks the entire system up. It might not happen on the first call to aio_read(), or the second, but it always happens relatively quickly. I speculate that if the data is already cached, then sometimes it works by virtue of being able to service the request from the same CPU, so the rfork VM-sharing bug isn't an issue. I saw the same symptoms, working on a uniprocessor kernel, not on an SMP kernel, on kernels based on 3.4-RELEASE. Unfortunately, I haven't had time to build kernels verified to be from the same sources for 3.4-RELEASE. I'm leaning towards not bothering, because I'm not sure what it would prove at this point. I should have some time next week to wrap this up into a solid test which will always invoke the crash. Thanks, scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 18:33:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by builder.freebsd.org (Postfix) with ESMTP id 35C6E4282; Fri, 4 Feb 2000 18:33:31 -0800 (PST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA10063; Sat, 5 Feb 2000 13:03:45 +1030 (CST) Date: Sat, 5 Feb 2000 13:03:45 +1030 From: Greg Lehey To: Wes Peters Cc: bpechter@shell.monmouth.com, freebsd-fs@FreeBSD.ORG Subject: Re: JFS and IBM Message-ID: <20000205130345.D9737@freebie.lemis.com> References: <200002041957.OAA06981@bg-tc-ppp600.monmouth.com> <389B5292.A7A8B6D4@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <389B5292.A7A8B6D4@softweyr.com> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moved to -fs] On Friday, 4 February 2000 at 15:28:34 -0700, Wes Peters wrote: > Bill Pechter wrote: >> >> Folks, while some of us were at Linux expo talking about journaling file >> systems and *BSD, IBM released jfs to the GPL. >> >> Is there anyone working on this as a gpl'd add-in to *BSD? > > You apparently haven't noticed the war of words going on on > http://daily.daemonnews.org/ on this very topic? I think this is going > to be our most "popular", or at least commented on, article to date. There was also a discussion in -fs, so I'm following up there. > Greg Lehey has downloaded the code and looked at it. Despite my > cheering and enthusiasm, he reports that we should wait until he > actually produces something to pronounce him a hero. ;^) Damn it, you keep mentioning my name. I'm certainly no hero based on what I've done or propose to do. For an update, taking in what phk had to say the other day: this is the OS/2 version, which has had the dependencies on the VM system removed. I consider it likely that, as a result, performance will be disappointing. Also I haven't seen any documentation which explains how it works. Given the size of the code base, this would make it quite a challenge. Maybe somebody else more stupid^H^H^H^H^H^Hheroic than I wants to have a go. Greg -- Finger grog@lemis.com for PGP public key 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 Feb 4 19: 3:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by builder.freebsd.org (Postfix) with ESMTP id 85AC244D1 for ; Fri, 4 Feb 2000 19:03:52 -0800 (PST) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id NAA09753 for ; Fri, 4 Feb 2000 13:39:53 -0500 (EST) Date: Fri, 4 Feb 2000 12:25:17 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: FreeBSD Posix threads Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have searched the archive for a while and still have some confusions about this subjects: (1) Some people say "For I/O bound activity, kernel threads are a really bad idea". But I read the following passage from else where: Kernel threads perform better in I/O-intensive applications because system call can be blocking for kernel threads (so there is only one user-to-kernel and kernel-to-user transition per I/O operation rather than two). So which one is the correct answer? I know there is only userland thread in FreeBSD, but I would like to know the answer. (2) User threads are supposed to be faster than kernel threads in context switch. But since we poll devices during each context switch, it is actually slower (poll() is the extra system call). Is this correct? (3) Can I do cooperative thread scheduling on FreeBSD? I guess the constant SCHED_RR (round robin) means preemptive. How about SCHED_FIFO and SCHED_OTHER defined in posix4/sched.h? Can I choose from them? In the case of SCHED_RR, I still do part of scheduling by routines like yield(), cond_signal(). Am I right? Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 19: 5: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by builder.freebsd.org (Postfix) with ESMTP id AC83D41F0 for ; Fri, 4 Feb 2000 19:04:58 -0800 (PST) Received: from zippy.dyn.ml.org ([207.214.116.101]) by mta1.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FPF003XQSER71@mta1.snfc21.pbi.net> for freebsd-hackers@FreeBSD.ORG; Fri, 4 Feb 2000 19:01:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id C335991525; Fri, 04 Feb 2000 19:01:36 -0800 (PST) Date: Fri, 04 Feb 2000 19:01:36 -0800 (PST) From: Alex Zepeda Subject: Re: Re/Fwd: freebsd specific search In-reply-to: <20000203123135.A10816@lindt.urgle.com> To: Mike Bristow Cc: freebsd-hackers@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Feb 2000, Mike Bristow wrote: > True; but linux has support for a bigger variety of soundcards > (my Win98^H^H^H^H^H^HEverQuest machine now has a Live! in it; supported > under Linux but not under FreeBSD AFAIK; so the other half of the disk > may turn turn into ext2 rather than ffs) Well if you buy esoteric or just cheap hardware... > I generally get the feeling that `Workstation Hardware'[1] has a better > chance of being supported under Linux than FreeBSD. I may be talking rubbish, > though ;-) Cheap hardware has a better chance of being supported. If you stick with the name brand stuff, you could piece together a box that'll work great and work great with FreeBSD. Me, I've got my Micron PC (which was a pretty good deal when I bought it), and the onboard sound is AFAIK supported by that comercial Linux sound driver, but nothing else. The box also came with an AWE64, therefore I'm happy. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 19:24:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by builder.freebsd.org (Postfix) with ESMTP id 7018241F0 for ; Fri, 4 Feb 2000 19:24:48 -0800 (PST) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id UAA02233; Fri, 4 Feb 2000 20:25:01 -0700 (MST) Received: from ip-83-040.prc.primenet.com(207.218.83.40), claiming to be "pinyon.org" via SMTP by smtp04.primenet.com, id smtpdAAAEoaiue; Fri Feb 4 20:24:53 2000 Received: from chomsky.Pinyon.ORG (localhost [127.0.0.1]) by pinyon.org (Postfix) with ESMTP id 450F65B; Fri, 4 Feb 2000 20:24:56 -0700 (MST) X-Mailer: exmh version 2.1.0 09/18/1999 To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG, rcarter@pinyon.org Subject: Re: FreeBSD Posix threads In-Reply-To: Message from Zhihui Zhang of "Fri, 04 Feb 2000 12:25:17 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Feb 2000 20:24:56 -0700 From: "Russell L. Carter" Message-Id: <20000205032456.450F65B@pinyon.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG % %I have searched the archive for a while and still have some confusions %about this subjects: % %(1) Some people say "For I/O bound activity, kernel threads are a really %bad idea". But I read the following passage from else where: % %Kernel threads perform better in I/O-intensive applications because system %call can be blocking for kernel threads (so there is only one %user-to-kernel and kernel-to-user transition per I/O operation rather than %two). % %So which one is the correct answer? I know there is only userland thread %in FreeBSD, but I would like to know the answer. % %(2) User threads are supposed to be faster than kernel threads in context %switch. But since we poll devices during each context switch, it is %actually slower (poll() is the extra system call). Is this correct? % %(3) Can I do cooperative thread scheduling on FreeBSD? I guess the %constant SCHED_RR (round robin) means preemptive. How about SCHED_FIFO %and SCHED_OTHER defined in posix4/sched.h? Can I choose from them? In %the case of SCHED_RR, I still do part of scheduling by routines like %yield(), cond_signal(). Am I right? % %Any help is appreciated. Excellent questions. However, what is not stated is perhaps the most important (to me, and other people burning up and showering down $$$). C++ programmers use threads to share class members. In that context, the POSIX realtime scheduling classes (SCHED_*) are quite useful, albeit abstractly for now. IMNSHO, focusing on fine-grained benchmarks ("perform better") for an execution model based on C processes may be misleading in the realistic broader picture. Russell %-Zhihui % % % % %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 Fri Feb 4 19:36:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by builder.freebsd.org (Postfix) with ESMTP id 2289441F0 for ; Fri, 4 Feb 2000 19:36:57 -0800 (PST) Received: from river ([10.0.128.30]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with SMTP id 432; Fri, 4 Feb 2000 19:33:33 -0800 Message-ID: <19b001bf6f8a$349abf70$1e80000a@avantgo.com> From: "Scott Hess" To: "Zhihui Zhang" , References: Subject: Re: FreeBSD Posix threads Date: Fri, 4 Feb 2000 19:36:36 -0800 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.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Zhihui Zhang" wrote: > (1) Some people say "For I/O bound activity, kernel threads are a really > bad idea". But I read the following passage from else where: > > Kernel threads perform better in I/O-intensive applications because system > call can be blocking for kernel threads (so there is only one > user-to-kernel and kernel-to-user transition per I/O operation rather than > two). > > So which one is the correct answer? I know there is only userland thread > in FreeBSD, but I would like to know the answer. Both. All I/O is not created equal. For blockable I/O (sockets, both TCP and UNIX domain, ttys, pipes, etc), userland pthreads are excellent. For disk I/O, they're less excellent because disk I/O is always ready to go, and you'll always block waiting for it. Not having multiple pending disk I/O requests can be killer. OTOH, that doesn't apply if your working set fits in memory. > (2) User threads are supposed to be faster than kernel threads in context > switch. But since we poll devices during each context switch, it is > actually slower (poll() is the extra system call). Is this correct? That's hard to say. If you use a "standard" thread-per-connection, then only the threads waiting for input contribute to the poll(). Threads that are working do not. Furthermore, a system call is not necessarily a cause for alarm - yet, that's a prime location for the kernel to decide to switch to another process, but it's not _required_ to do so. Later, scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 20: 7:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by builder.freebsd.org (Postfix) with ESMTP id E4A4B44D7 for ; Fri, 4 Feb 2000 20:07:50 -0800 (PST) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id FAA27436 for freebsd-hackers@freebsd.org; Sat, 5 Feb 2000 05:08:11 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 547668877; Sat, 5 Feb 2000 01:34:18 +0100 (CET) Date: Sat, 5 Feb 2000 01:34:18 +0100 From: Ollivier Robert To: freebsd-hackers@freebsd.org Subject: Re: how to compile without libc (so not static) Message-ID: <20000205013418.A76713@keltia.freenix.fr> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20000204161324.B2DE396D7@toad.stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: <20000204161324.B2DE396D7@toad.stack.nl>; from marcov@stack.nl on Fri, Feb 04, 2000 at 05:13:24PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Marco van de Voort: > gcc -nostdlib empty.c /usr/lib/crti.o /usr/lib/crt0.o -o empty You mean crt1.o instead of crt0.o here right? crt0.o is the a.out version... > grep exit *.o nm(1) is your Dear Friend® here. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 20: 8: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by builder.freebsd.org (Postfix) with ESMTP id 5642B44F5 for ; Fri, 4 Feb 2000 20:07:55 -0800 (PST) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id FAA27440 for freebsd-hackers@freebsd.org; Sat, 5 Feb 2000 05:08:16 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id BDDCA8877; Sat, 5 Feb 2000 01:36:49 +0100 (CET) Date: Sat, 5 Feb 2000 01:36:49 +0100 From: Ollivier Robert To: freebsd-hackers@freebsd.org Subject: Re: JFS and IBM Message-ID: <20000205013649.B76713@keltia.freenix.fr> Mail-Followup-To: freebsd-hackers@freebsd.org References: <200002041957.OAA06981@bg-tc-ppp600.monmouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002041957.OAA06981@bg-tc-ppp600.monmouth.com>; from pechter@pechter.dyndns.org on Fri, Feb 04, 2000 at 02:57:18PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Bill Pechter: > Is this as much of a surprise to all of you as to me... I thought jfs > would remain a tightly held OSF/1 component that would never see > "free" status. Note that the released version is the OS/2 one (maybe based on HPFS?) not the one in AIX. But I agree this is good news. IBM has been a rather nice player in this field for a long time now (Jikes, Postfix and such). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 4 22:26:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by builder.freebsd.org (Postfix) with ESMTP id 826CA4526 for ; Fri, 4 Feb 2000 22:26:32 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA23640 for ; Fri, 4 Feb 2000 23:26:52 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA03255 for ; Fri, 4 Feb 2000 23:26:46 -0700 (MST) Message-Id: <200002050626.XAA03255@harmony.village.org> To: hackers@freebsd.org Subject: Question about msdosfs Date: Fri, 04 Feb 2000 23:26:46 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In msdosfs_vfsops.c we have: || !pmp->pm_Heads || pmp->pm_Heads > 255 #ifdef PC98 || !pmp->pm_SecPerTrack || pmp->pm_SecPerTrack > 255) { #else || !pmp->pm_SecPerTrack || pmp->pm_SecPerTrack > 63) { #endif error = EINVAL; What's so special about 63? Many scsi drives have more than 63 sectors per track. The only reason that we don't see problems with this is that it appears that CAM appears to be using a geometry with 64 heads and 32 sectors and N cylendars. What's the justification here? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 5 5:18:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.2.7]) by builder.freebsd.org (Postfix) with ESMTP id D809A40FB for ; Sat, 5 Feb 2000 05:18:09 -0800 (PST) Received: from hermes.tue.nl [131.155.2.46] by kweetal.tue.nl (8.9.3) for id OAA05156 (ESMTP); Sat, 5 Feb 2000 14:18:33 +0100 (MET) Received: from deathstar (n194.dial.tue.nl [131.155.209.193]) by hermes.tue.nl (Postfix) with ESMTP id 9D59F2E802 for ; Sat, 5 Feb 2000 14:18:31 +0100 (CET) From: "Marco van de Voort" To: freebsd-hackers@freebsd.org Date: Sat, 5 Feb 2000 14:16:00 +0100 Subject: Re: how to compile without libc (so not static) In-reply-to: <20000205013418.A76713@keltia.freenix.fr> References: <20000204161324.B2DE396D7@toad.stack.nl>; from marcov@stack.nl on Fri, Feb 04, 2000 at 05:13:24PM +0100 X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000205131831.9D59F2E802@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to Marco van de Voort: > > gcc -nostdlib empty.c /usr/lib/crti.o /usr/lib/crt0.o -o empty > > You mean crt1.o instead of crt0.o here right? crt0.o is the a.out version... Yup, my fault. > > grep exit *.o > > nm(1) is your Dear Friend® here. Grep and gcc -S also :-) Anyway I manually patched the .s sources, and now I can compile an empty gcc program. Never knew that that was so hard! gcc -nostdlib crt1.o crtbegin.o empty.c crtend.o -o empty was the final commandline I think. I manually patched crt1 to remove the libc init and the (two!) atexit calls. Marco van de Voort (MarcoV@Stack.nl) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 5 6: 7:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from utogw.gssm.otsuka.tsukuba.ac.jp (utogwgw.gssm.otsuka.tsukuba.ac.jp [130.158.176.189]) by builder.freebsd.org (Postfix) with ESMTP id DDC63400E for ; Sat, 5 Feb 2000 06:07:53 -0800 (PST) Received: from smr00.gssm.otsuka.tsukuba.ac.jp (smr00 [10.2.1.1]) by utogw.gssm.otsuka.tsukuba.ac.jp (8.8.5/8.8.5) with ESMTP id XAA28571; Sat, 5 Feb 2000 23:09:49 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by smr00.gssm.otsuka.tsukuba.ac.jp (8.9.3/8.9.3) with ESMTP id XAA02525; Sat, 5 Feb 2000 23:08:54 +0900 (JST) (envelope-from ohki@gssm.otsuka.tsukuba.ac.jp) Message-Id: <200002051408.XAA02525@smr00.gssm.otsuka.tsukuba.ac.jp> From: Atsuo Ohki To: freebsd-hackers@FreeBSD.org Cc: ohki@gssm.otsuka.tsukuba.ac.jp Subject: some guard against stack overflow attack Mime-Version: 1.0 Content-Type: text/plain;charset="us-ascii" Date: Sat, 05 Feb 2000 23:08:54 +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks I'd like to propse a simple guard against stack overflow attack. The idea is very simple: just prevent system call from writable user area (i.e. data & bss area) except SYS_sigreturn. It has few performance penalty and can prevent trivial stack overflow attack such as simply executing shell. *** /usr/src/sys/i386/i386/trap.c-ORIG Mon Aug 30 01:05:56 1999 --- /usr/src/sys/i386/i386/trap.c Fri Feb 4 22:30:44 2000 *************** *** 1074,1079 **** --- 1074,1090 ---- if (p->p_sysent->sv_mask) code &= p->p_sysent->sv_mask; + /* begin XXXXXXX -- prevent system call from writable user area */ + if (code != SYS_sigreturn && + ((int)(*vtopte(frame.tf_eip-frame.tf_err))&(PG_V|PG_RW|PG_U)) + != (PG_V|PG_U)) { + printf("pid%d: %d@0x%08x\n", + p->p_pid, code, frame.tf_eip-frame.tf_err); + trapsignal(p, SIGILL, T_PRIVINFLT); + error = -1; /* just prevent warning */ + goto bad_syscall; + } + /* end XXXXXXX */ if (code >= p->p_sysent->sv_size) callp = &p->p_sysent->sv_table[0]; *************** *** 1140,1145 **** --- 1151,1159 ---- frame.tf_eflags &= ~PSL_T; trapsignal(p, SIGTRAP, 0); } + /* begin XXXXXXX */ + bad_syscall: + /* end XXXXXXX */ userret(p, &frame, sticks); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 5 10:32:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 6B23D45CB for ; Sat, 5 Feb 2000 10:32:13 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA35677; Sat, 5 Feb 2000 10:32:30 -0800 (PST) (envelope-from dillon) Date: Sat, 5 Feb 2000 10:32:30 -0800 (PST) From: Matthew Dillon Message-Id: <200002051832.KAA35677@apollo.backplane.com> To: Atsuo Ohki Cc: freebsd-hackers@FreeBSD.ORG, ohki@gssm.otsuka.tsukuba.ac.jp Subject: Re: some guard against stack overflow attack References: <200002051408.XAA02525@smr00.gssm.otsuka.tsukuba.ac.jp> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think this will break dynamically loaded code. Also, library fixups may be writable and even if we don't embed jump instructions in them now who knows what might be done in the future. Even if we enforced this all it would accomplish is to make the cracks a little more sophisticated. Linux messes around with the user code segment. By limiting its size it can be made to 'miss' the user stack, preventing code from being executable on the stack. This is a zero-cost solution. However, there has been a lot of resistance to implementing it in FreeBSD because it is an i386-specific solution rather then a general solution, and is really more of a mask on the problem instead of a fix. -Matt Matthew Dillon :Hi folks : : I'd like to propse a simple guard against stack overflow attack. : The idea is very simple: just prevent system call from writable : user area (i.e. data & bss area) except SYS_sigreturn. : : It has few performance penalty and can prevent trivial stack : overflow attack such as simply executing shell. : : :*** /usr/src/sys/i386/i386/trap.c-ORIG Mon Aug 30 01:05:56 1999 :--- /usr/src/sys/i386/i386/trap.c Fri Feb 4 22:30:44 2000 :*************** :*** 1074,1079 **** :--- 1074,1090 ---- : : if (p->p_sysent->sv_mask) : code &= p->p_sysent->sv_mask; :+ /* begin XXXXXXX -- prevent system call from writable user area */ :+ if (code != SYS_sigreturn && :+ ((int)(*vtopte(frame.tf_eip-frame.tf_err))&(PG_V|PG_RW|PG_U)) :+ != (PG_V|PG_U)) { :+ printf("pid%d: %d@0x%08x\n", :+ p->p_pid, code, frame.tf_eip-frame.tf_err); :+ trapsignal(p, SIGILL, T_PRIVINFLT); :+ error = -1; /* just prevent warning */ :+ goto bad_syscall; :+ } :+ /* end XXXXXXX */ : : if (code >= p->p_sysent->sv_size) : callp = &p->p_sysent->sv_table[0]; :*************** :*** 1140,1145 **** :--- 1151,1159 ---- : frame.tf_eflags &= ~PSL_T; : trapsignal(p, SIGTRAP, 0); : } :+ /* begin XXXXXXX */ :+ bad_syscall: :+ /* end XXXXXXX */ : : userret(p, &frame, sticks); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 5 12:23:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.2.7]) by builder.freebsd.org (Postfix) with ESMTP id D58064624 for ; Sat, 5 Feb 2000 12:23:43 -0800 (PST) Received: from hermes.tue.nl [131.155.2.46] by kweetal.tue.nl (8.9.3) for id VAA19633 (ESMTP); Sat, 5 Feb 2000 21:23:40 +0100 (MET) Received: from tilly (n165.dial.tue.nl [131.155.209.164]) by hermes.tue.nl (Postfix) with SMTP id A77122E803 for ; Sat, 5 Feb 2000 21:23:38 +0100 (CET) From: "Marco van de Voort" To: freebsd-hackers@freebsd.org Date: Sat, 5 Feb 2000 21:23:50 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Spontaneous reboot X-mailer: Pegasus Mail for Win32 (v3.01d) Message-Id: <20000205202338.A77122E803@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know this is not meant as a bug reporting list, but since I'm on it for other purposes, I thought I could sent it in anyway. I trashed a FreeBSD (probably 3.4, I get the exact version mailed next week) by creating a bash script that contained ping xxx.yyy.zzz.vvv & line 15 times, and executing the script in the background several times (more like 10) from the commandline with script & (we were trying to slow down my roommates win98 laptop from the FreeBSD dorm firewall machine, over internal dorm network only). Needless to say the roommate wasn't impressed when the FreeBSD machine rebooted, and the win98 machine only slowed down minimally :-) The machine was a p133 with 32 MB, and I started the script as user not as root. I can access the machine for simple tests or configuration data if that is necessary. Since it was the firewall, so we didn't try to replicate the experiment To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 5 14:49:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id 6E557467F; Sat, 5 Feb 2000 14:49:43 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id PAA28581; Sat, 5 Feb 2000 15:16:28 -0800 (PST) Date: Sat, 5 Feb 2000 15:16:28 -0800 From: Alfred Perlstein To: hackers@freebsd.org Cc: jasone@freebsd.org Subject: (forw) Re: readdir_r thread safe? Message-ID: <20000205151627.W25520@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ugh, I should have brought this up before the code freeze but... Maybe we could make 4.0 the transition point for adding locking structures to FILE and DIR structures instead of the hackish way it's done now (maintaining a seperate structure). Does anyone agree or have time for this? It would greatly simplify the code and actually fix the readdir_r problem. -Alfred ----- Forwarded message from "Richard Seaman, Jr." ----- Date: Mon, 29 Nov 1999 15:32:50 -0600 From: "Richard Seaman, Jr." To: Alfred Perlstein Cc: deischen@freebsd.org, jasone@freebsd.org, bde@freebsd.org Subject: Re: readdir_r thread safe? Message-ID: <19991129153250.F29767@tar.com> X-Mailer: Mutt 1.0pre3i On Mon, Nov 29, 1999 at 01:45:14PM -0800, Alfred Perlstein wrote: > > I think the argument is more like what happens with the stream > > functions fread(), fwrite(), etc. There are the flockfile() and > > funlockfile() functions that are used within libc and libc_r to > > lock the FILE structure. Locking the file descriptor element of > > the FILE structure is not sufficient. Moreover, its not the > > programmmer's responsibility to lock the FILE structure before > > accessing the stream functions. libc does it for you. I think > > this is what it means to be "thread safe". > > Ok, that makes sense. > > > Now, if you don't want readdir_r() to be "thread safe", and document > > it as such, that's another matter. > > That's not my intention, I'll see what I can do to fix this. And now.... you're about to open a "can of worms". :) The simplest way, by far, to have implemented flockfile() and funlockfile() would have been to add an element to the FILE structure to hold the lock. The simplest way, by far, to lock the DIR structure is to modify the DIR structure to hold a lock element. Ditto for any other libc shareable structures, if there are any. But, I think this breaks compability, and would require a version bump for libc. I think this is why John Birrell implemented flockfile() etc. in the very convoluted way he did (it was the only other choice). I don't know what every one thinks about a version bump for libc, but I think there are enough thread related changes that libc requires that it should happen. But, probably someone needs to wade through libc and find *all* the changes that are needed, so that if the version bump is agreed to, it only happens once. I started work on this about 9 months ago, got waylaid, and never finished. The alternative "hack" for the DIR structure that might work is to lock the dd_fd every time you access the DIR structure, even if you're not doing a file access. This might be equivalent to locking the DIR structure, but I haven't investigated it fully. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 ----- End forwarded message ----- -- -Alfred Perlstein - [bright@wintelcom.net|alfred@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 Feb 5 15: 6:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by builder.freebsd.org (Postfix) with SMTP id 4E68046A0 for ; Sat, 5 Feb 2000 15:06:37 -0800 (PST) Received: (qmail 17626 invoked by uid 1001); 5 Feb 2000 23:03:12 -0000 Date: Sat, 5 Feb 2000 15:03:12 -0800 From: Jason Evans To: Alfred Perlstein Cc: hackers@freebsd.org, jkh@freebsd.org Subject: Re: (forw) Re: readdir_r thread safe? Message-ID: <20000205150312.J73462@sturm.canonware.com> References: <20000205151627.W25520@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000205151627.W25520@fw.wintelcom.net>; from bright@wintelcom.net on Sat, Feb 05, 2000 at 03:16:28PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 05, 2000 at 03:16:28PM -0800, Alfred Perlstein wrote: > Ugh, I should have brought this up before the code freeze but... > > Maybe we could make 4.0 the transition point for adding locking > structures to FILE and DIR structures instead of the hackish > way it's done now (maintaining a seperate structure). > > Does anyone agree or have time for this? > > It would greatly simplify the code and actually fix the readdir_r > problem. Well, my personal opinion is that we shouldn't muck with this during the code freeze, but if there's agreement (and approval from Jordan) that it should happen before the 4.0 release, I'm willing to do the work. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 5 18:25:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from www.geocrawler.com (sourceforge.net [198.186.203.33]) by builder.freebsd.org (Postfix) with ESMTP id 13D93467D for ; Sat, 5 Feb 2000 18:25:30 -0800 (PST) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id SAA13081; Sat, 5 Feb 2000 18:24:07 -0800 Date: Sat, 5 Feb 2000 18:24:07 -0800 Message-Id: <200002060224.SAA13081@www.geocrawler.com> To: freebsd-hackers@freebsd.org Subject: Broken pipe From: "Alex" Reply-To: "Alex" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message was sent from Geocrawler.com by "Alex" Be sure to reply to that address. Hello When I run my script,sometimes I receive next message: "/usr/sbin/wanrouter: line 5 288 Broken pipe ls $ROUTER_LOCK_DIR/ 289 Exit 1 | grep -q wanpipe*" I use bash-2.03 shell. The line is cause to this message is : ls $ROUTER_LOCK_DIR/ | grep -q wanpipe* && rm $ROUTER_LOCK_DIR/* Is somebody can help me why is happened? Thank you for any help Alex Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 5 19:54:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id 58E2046CB for ; Sat, 5 Feb 2000 19:54:48 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id TAA13546; Sat, 5 Feb 2000 19:55:15 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id TAA19632; Sat, 5 Feb 2000 19:55:15 -0800 Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id TAA11402; Sat, 5 Feb 2000 19:55:13 -0800 (PST) Message-ID: <389CF1F3.6D783A49@softweyr.com> Date: Sat, 05 Feb 2000 21:00:51 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Marco van de Voort Cc: freebsd-hackers@freebsd.org Subject: Re: Spontaneous reboot References: <20000205202338.A77122E803@hermes.tue.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marco van de Voort wrote: > > I know this is not meant as a bug reporting list, but since I'm on it > for other purposes, I thought I could sent it in anyway. > > I trashed a FreeBSD (probably 3.4, I get the exact version mailed > next week) by creating a bash script that contained > > ping xxx.yyy.zzz.vvv & > > line 15 times, and executing the script in the background several > times (more like 10) from the commandline with > > script & > > (we were trying to slow down my roommates win98 laptop from the > FreeBSD dorm firewall machine, over internal dorm network only). > Needless to say the roommate wasn't impressed when the > FreeBSD machine rebooted, and the win98 machine only slowed > down minimally :-) Ugh. Next time, just become root and ping -f that Win98 machine. Running lots of pings isn't going to get you what you're trying for, even if you don't crash your FreeBSD machine. Another great program for offing Windows boxes is spray. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 5 20:23:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by builder.freebsd.org (Postfix) with ESMTP id 32DF046FC; Sat, 5 Feb 2000 20:23:35 -0800 (PST) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA62750; Sat, 5 Feb 2000 20:23:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Alfred Perlstein Cc: hackers@FreeBSD.ORG, jasone@FreeBSD.ORG Subject: Re: (forw) Re: readdir_r thread safe? In-reply-to: Your message of "Sat, 05 Feb 2000 15:16:28 PST." <20000205151627.W25520@fw.wintelcom.net> Date: Sat, 05 Feb 2000 20:23:31 -0800 Message-ID: <62747.949811011@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ugh, I should have brought this up before the code freeze but... I think that pretty much says it all, and reflects my own opinion on the matter. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 5 21:19:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by builder.freebsd.org (Postfix) with ESMTP id 2DBB14703 for ; Sat, 5 Feb 2000 21:19:27 -0800 (PST) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id AAA40733; Sun, 6 Feb 2000 00:19:50 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200002060519.AAA40733@server.baldwin.cx> 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: <200002050626.XAA03255@harmony.village.org> Date: Sun, 06 Feb 2000 00:19:50 -0500 (EST) From: John Baldwin To: Warner Losh Subject: RE: Question about msdosfs Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Feb-00 Warner Losh wrote: > > In msdosfs_vfsops.c we have: > || !pmp->pm_Heads || pmp->pm_Heads > 255 >#ifdef PC98 > || !pmp->pm_SecPerTrack || pmp->pm_SecPerTrack > 255) { >#else > || !pmp->pm_SecPerTrack || pmp->pm_SecPerTrack > 63) { >#endif > error = EINVAL; > > What's so special about 63? Many scsi drives have more than 63 > sectors per track. The only reason that we don't see problems with > this is that it appears that CAM appears to be using a geometry with > 64 heads and 32 sectors and N cylendars. What's the justification > here? The PC BIOS (int 0x13 calls) only allows for 63 sectors numbered 1-63 for each track (cylinder). That is most likely the reason for the 63. > Warner -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "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 Feb 5 22:34:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (43.ppp1-3.image.dk [213.237.1.43]) by builder.freebsd.org (Postfix) with ESMTP id D65CA4680 for ; Sat, 5 Feb 2000 22:34:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id HAA93154; Sun, 6 Feb 2000 07:34:43 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sun, 6 Feb 2000 07:34:43 +0100 (CET) From: Leif Neland To: Wes Peters Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Spontaneous reboot In-Reply-To: <389CF1F3.6D783A49@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 Feb 2000, Wes Peters wrote: > Next time, just become root and ping -f that Win98 machine. Running > lots of pings isn't going to get you what you're trying for, even if > you don't crash your FreeBSD machine. > > Another great program for offing Windows boxes is spray. > > A spray on a windows-box just hangs; no network activity is seen. A spray on a FreeBSD-box: spray: RPC: Program not registered. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 6 3:42:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by builder.freebsd.org (Postfix) with ESMTP id 6EEA73D45 for ; Sun, 6 Feb 2000 03:42:56 -0800 (PST) Received: from daemon.ninth-circle.org ([195.121.196.154]) by smtp05.wxs.nl (Netscape Messaging Server 4.05) with ESMTP id FPIB8H00.18T; Sun, 6 Feb 2000 12:43:29 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id MAA27714; Sun, 6 Feb 2000 12:43:07 +0100 (CET) (envelope-from asmodai) Date: Sun, 6 Feb 2000 12:43:07 +0100 From: Jeroen Ruigrok/Asmodai To: Alex Cc: freebsd-hackers@freebsd.org Subject: Re: Broken pipe Message-ID: <20000206124307.D319@daemon.ninth-circle.org> Reply-To: freebsd-questions@freebsd.org References: <200002060224.SAA13081@www.geocrawler.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002060224.SAA13081@www.geocrawler.com>; from archiver@db.geocrawler.com on Sat, Feb 05, 2000 at 06:24:07PM -0800 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [This does _not_ belong on hackers, follow-ups set to questions] -On [20000206 04:00], Alex (archiver@db.geocrawler.com) wrote: > >When I run my script,sometimes I receive next >message: > >"/usr/sbin/wanrouter: line 5 288 Broken pipe >ls $ROUTER_LOCK_DIR/ 289 Exit 1 | grep -q >wanpipe*" Ehm, the above looks kinda weird and would most certainly explain the broken pipe. A broken pipe is when stdout had a connection to the stdin of the next program but the pipe got severed somehow (or never got set up in the first place). >I use bash-2.03 shell. >The line is cause to this message is : > >ls $ROUTER_LOCK_DIR/ | grep -q wanpipe* && rm >$ROUTER_LOCK_DIR/* And this does work from the command line? It looks ok to me. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project There is no greater sorrow than to recall, in misery, the time when we were happy... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 6 3:50:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by builder.freebsd.org (Postfix) with ESMTP id 4BA8E3D0C for ; Sun, 6 Feb 2000 03:50:19 -0800 (PST) Received: from daemon.ninth-circle.org ([195.121.196.154]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA1552; Sun, 6 Feb 2000 12:50:04 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id MAA27722; Sun, 6 Feb 2000 12:50:00 +0100 (CET) (envelope-from asmodai) Date: Sun, 6 Feb 2000 12:49:59 +0100 From: Jeroen Ruigrok/Asmodai To: lists@security.za.net Cc: hackers@freebsd.org Subject: Re: IPFW / IP Filter question Message-ID: <20000206124959.E319@daemon.ninth-circle.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from lists@security.za.net on Thu, Feb 03, 2000 at 11:28:49PM +0200 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000203 22:43], lists@security.za.net (lists@security.za.net) wrote: >I would have thought you would use the tee option in ipfw for this, but >its not implemented yet according to my man pages, so I was wondering if >there was another way to do this, cause it makes traffic analysis a hell >of a lot easier if I can do this rather than having to sniff it with bpf >or something. Didn't CURRENT add the tee option by now? I really recall a commit message stating tee support has been added... -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project The Eyes of Truth are always watching you... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 6 7:39:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id A257A3D5E for ; Sun, 6 Feb 2000 07:39:09 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id HAA14434; Sun, 6 Feb 2000 07:35:25 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id HAA03994; Sun, 6 Feb 2000 07:35:25 -0800 Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id HAA02290; Sun, 6 Feb 2000 07:35:23 -0800 (PST) Message-ID: <389D960A.6A602CC9@softweyr.com> Date: Sun, 06 Feb 2000 08:40:58 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Leif Neland Cc: freebsd-hackers@freebsd.org Subject: Re: Spontaneous reboot References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > > On Sat, 5 Feb 2000, Wes Peters wrote: > > > Next time, just become root and ping -f that Win98 machine. Running > > lots of pings isn't going to get you what you're trying for, even if > > you don't crash your FreeBSD machine. > > > > Another great program for offing Windows boxes is spray. > > > > > A spray on a windows-box just hangs; no network activity is seen. > A spray on a FreeBSD-box: spray: RPC: Program not registered. sprayd(4). We have a version for Windows floating around the office, it probably came with PC-NFS. Be careful, if you're on a shared network segment everyone else on the network will want to kill you. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 6 10: 7:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by builder.freebsd.org (Postfix) with ESMTP id 462FE3D0F for ; Sun, 6 Feb 2000 10:07:17 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id KAA03972; Sun, 6 Feb 2000 10:07:40 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Sun, 6 Feb 2000 10:07:40 -0800 (PST) From: Doug White To: Egervary Gergely Cc: hackers@FreeBSD.ORG Subject: Re: NMBCLUSTERS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Feb 2000, Egervary Gergely wrote: > what size of $SUBJECT should be used on a box with two _extremely_ busy > 100baseTX interfaces? This is what we run on our mail servers (with only one interface :) ) 867/8780/16384 mbuf clusters in use (current/peak/max) I think we've blown up the max on a couple of occasions, mainly when we lost network connectivity and/or the ensuing rush after it came back. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | 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 Sun Feb 6 13: 0:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by builder.freebsd.org (Postfix) with ESMTP id C236D3DE4 for ; Sun, 6 Feb 2000 13:00:37 -0800 (PST) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id QAA29759; Sun, 6 Feb 2000 16:01:12 -0500 (EST) Date: Sun, 6 Feb 2000 14:46:31 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org, arla-drinkers@stacken.kth.se Subject: Writing a multithreaded daemon process Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After reading part of the Arla daemon code available at http://www.stacken.kth.se/projekt/arla/, I feel it is a real good design. The daemon code is a multi-threaded user process that does most of the job and the kernel is an interface to VFS. They communicate with each other via a character device. But I am wondering if the performance is good since you sometimes have to cross user-system boundary up to four times for a single read operations: read() --> Arla daemon --> network --> install data into kernel If the daemon can somehow reside entirely inside the kernel, like NFS daemon, we can save those crossings. But the daemon is a multi-threaded process and we have no kernel thread yet, so I do not know how to do better if possible. Maybe all user filesystems have to live with this limitation. Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 6 16:53: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vitoria.ddsecurity.com.br (vitoria.ddsecurity.com.br [200.18.130.93]) by builder.freebsd.org (Postfix) with SMTP id C553B3F7B for ; Sun, 6 Feb 2000 16:52:51 -0800 (PST) Received: (qmail 55032 invoked from network); 7 Feb 2000 00:51:14 -0000 Received: from modem20.tdnet.com.br (HELO ddsecurity.com.br) (200.236.148.120) by vitoria.ddsecurity.com.br with SMTP; 7 Feb 2000 00:51:14 -0000 Message-ID: <389DFAE1.5924C3DF@ddsecurity.com.br> Date: Sun, 06 Feb 2000 22:51:13 +0000 From: Gustavo V G C Rios X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: multithreaded IP Stack Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi hackers, Currently, freebsd does lack such a support into its implementation. I would like to give a look into this topic to see what i can do to include support for free. Can anyone here point me some source of information about this topic! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 6 20:52:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from io.yi.org (h24-67-218-186.xx.wave.shaw.ca [24.67.218.186]) by builder.freebsd.org (Postfix) with ESMTP id C3FA23E2C for ; Sun, 6 Feb 2000 20:52:15 -0800 (PST) Received: from io.yi.org (jake@localhost.gvcl1.bc.wave.home.com [127.0.0.1]) by io.yi.org (8.9.3/8.9.3) with ESMTP id UAA46328; Sun, 6 Feb 2000 20:53:34 -0800 (PST) (envelope-from jake@io.yi.org) Message-Id: <200002070453.UAA46328@io.yi.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG, arla-drinkers@stacken.kth.se Subject: Re: Writing a multithreaded daemon process In-reply-to: Your message of "Sun, 06 Feb 2000 14:46:31 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 06 Feb 2000 20:53:33 -0800 From: Jake Burkholder Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If the daemon can somehow reside entirely inside the kernel, like NFS > daemon, we can save those crossings. But the daemon is a multi-threaded > process and we have no kernel thread yet, so I do not know how to do > better if possible. Maybe all user filesystems have to live with this > limitation. There's kernel threads and then there's kernel threads. kthread_create (see sys/kern/kern_kthread.c) will create a new process which shares it's address space with the kernel; that might be what you want. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 0:17:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhost.tue.nl (mailhost.tue.nl [131.155.2.5]) by builder.freebsd.org (Postfix) with ESMTP id D60243D37 for ; Mon, 7 Feb 2000 00:17:14 -0800 (PST) Received: from hermes.tue.nl [131.155.2.46] by mailhost.tue.nl (8.9.3) for id JAA22346 (ESMTP); Mon, 7 Feb 2000 09:17:54 +0100 (MET) Received: from deathstar (n195.dial.tue.nl [131.155.209.194]) by hermes.tue.nl (Postfix) with ESMTP id 9C14D2E803 for ; Mon, 7 Feb 2000 09:17:52 +0100 (CET) From: "Marco van de Voort" To: hackers@FreeBSD.ORG Date: Mon, 7 Feb 2000 09:15:26 +0100 Subject: Re: how to compile without libc (so not static) References: Your message of Fri, 04 Feb 2000 17:13:24 +0100. <20000204161324.B2DE396D7@toad.stack.nl> In-reply-to: <26143.949880575@monkeys.com> X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000207081752.9C14D2E803@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >grep exit *.o > > > >in /usr/lib doesn't find me that label. > > > >What am I missing? > > Try this instead: > > nm /usr/lib/libc.a | grep exit I'm aware of that! That is libc which I'm trying to avoid here! (see man gcc, search for -nostdlib) I was referering to excuting gcc with -nostdlib with a simple c file and startup code(search for a csu directory in /usr/src) So gcc should support NOT linking to libc. So either - the (ELF) initcode (crt1.x) is not implemented well - the gcc (at least the FreeBSD version if it is modified) is buggy, and doesn't select e.g. a correct crt1.o without the call to exit/atexit, or with other patched code. (which is unlikely since I can't find any other files). which was the point. I was trying to make. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 2: 7:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from blubb.pdc.kth.se (blubb.pdc.kth.se [130.237.221.147]) by builder.freebsd.org (Postfix) with SMTP id 1BAAA3EC4 for ; Mon, 7 Feb 2000 02:07:12 -0800 (PST) Received: from joda by blubb.pdc.kth.se with local (Exim 1.71 #3) id 12Hl51-0002AL-00; Mon, 7 Feb 2000 11:07:39 +0100 To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org, arla-drinkers@stacken.kth.se Subject: Re: Writing a multithreaded daemon process References: From: joda@pdc.kth.se (Johan Danielsson) Date: 07 Feb 2000 11:07:39 +0100 In-Reply-To: Zhihui Zhang's message of "Sun, 6 Feb 2000 14:46:31 -0500 (EST)" Message-ID: Lines: 10 User-Agent: Gnus/5.070083 (Pterodactyl Gnus v0.83) Emacs/20.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zhihui Zhang writes: > If the daemon can somehow reside entirely inside the kernel, like > NFS daemon, we can save those crossings. Yes, but the whole point of having the daemon in userspace is that it's *so* much easier to maintain. If you want to work on performance, I suggest that you take a look at other parts of the system, like RX. /Johan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 4:29: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by builder.freebsd.org (Postfix) with ESMTP id D4DEB3DFB for ; Mon, 7 Feb 2000 04:28:52 -0800 (PST) Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by nets5.rz.rwth-aachen.de (8.9.1a/8.9.1/10) with ESMTP id NAA04291 for ; Mon, 7 Feb 2000 13:29:30 +0100 (MET) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id NAA19277 for ; Mon, 7 Feb 2000 13:29:58 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.3/8.6.9) id NAA45432 for hackers@freebsd.org; Mon, 7 Feb 2000 13:29:33 +0100 (CET) Date: Mon, 7 Feb 2000 13:29:33 +0100 (CET) From: Christoph Kukulies Message-Id: <200002071229.NAA45432@gil.physik.rwth-aachen.de> To: hackers@freebsd.org Subject: ntop Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been advised by someone to try to use 'ntop', an network analysis tool. Found it in the FreeBSD ports collection. While building it I found that configure said: ... checking whether time.h and sys/time.h may both be included... yes checking for lsof... no WARNING: unable to locate lsof. Some ntop features will be disabled. checking for main in -lncurses... yes ... Well, always assuming FreeBSD being one of the most fully fledged OSs WRT networking, I'm wondering what sort of feature I'm missing here. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 4:43: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lindt.urgle.com (lindt.urgle.com [195.173.172.169]) by builder.freebsd.org (Postfix) with ESMTP id 031303E39 for ; Mon, 7 Feb 2000 04:42:48 -0800 (PST) Received: from mike by lindt.urgle.com with local (Exim 3.03 #1) id 12HnVY-0005UZ-00; Mon, 07 Feb 2000 12:43:12 +0000 Date: Mon, 7 Feb 2000 12:43:12 +0000 From: Mike Bristow To: Christoph Kukulies Cc: hackers@freebsd.org Subject: Re: ntop Message-ID: <20000207124312.A21102@lindt.urgle.com> References: <200002071229.NAA45432@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002071229.NAA45432@gil.physik.rwth-aachen.de>; from kuku@gilberto.physik.RWTH-Aachen.DE on Mon, Feb 07, 2000 at 01:29:33PM +0100 X-Rated: BATF, NORAD, Uzi Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (This is pobably inapproprate for -hackers. Reply to me alone or move it to -questions, I guess) On Mon, Feb 07, 2000 at 01:29:33PM +0100, Christoph Kukulies wrote: [ntop] > While building it I found that configure said: > > ... > > checking whether time.h and sys/time.h may both be included... yes > checking for lsof... no > > WARNING: unable to locate lsof. Some ntop features will be disabled. > > checking for main in -lncurses... yes > ... > > Well, always assuming FreeBSD being one of the most fully fledged > OSs WRT networking, I'm wondering what sort of feature I'm missing > here. /usr/ports/sysutils/lsof -- Mike Bristow, Geek At Large ``Beware of Invisible Cows'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 4:43:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from msk1.mail.ru (mx1.mail.ru [194.67.23.32]) by builder.freebsd.org (Postfix) with ESMTP id ED8853DFB for ; Mon, 7 Feb 2000 04:43:11 -0800 (PST) Received: from h0050da20495b.ne.mediaone.net ([24.147.104.88] helo=kan.ne.mediaone.net) by msk1.mail.ru with esmtp (Exim 3.02 #116) id 12HnaL-000H8m-00; Mon, 07 Feb 2000 15:48:10 +0300 Received: (from kan@localhost) by kan.ne.mediaone.net (8.9.3/8.9.3) id HAA74045; Mon, 7 Feb 2000 07:43:25 -0500 (EST) (envelope-from kan) 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: <200002071229.NAA45432@gil.physik.rwth-aachen.de> Date: Mon, 07 Feb 2000 07:43:25 -0500 (EST) From: "Alexander N. Kabaev" To: Christoph Kukulies Subject: RE: ntop Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look at /usr/ports/sysutils/lsof To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 5:51:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by builder.freebsd.org (Postfix) with ESMTP id 84F933F13 for ; Mon, 7 Feb 2000 05:51:30 -0800 (PST) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id IAA09334; Mon, 7 Feb 2000 08:52:11 -0500 (EST) Date: Mon, 7 Feb 2000 07:37:28 -0500 (EST) From: Zhihui Zhang To: Johan Danielsson Cc: freebsd-hackers@FreeBSD.ORG, arla-drinkers@stacken.kth.se Subject: Re: Writing a multithreaded daemon process In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 7 Feb 2000, Johan Danielsson wrote: > Zhihui Zhang writes: > > > If the daemon can somehow reside entirely inside the kernel, like > > NFS daemon, we can save those crossings. > > Yes, but the whole point of having the daemon in userspace is that > it's *so* much easier to maintain. If you want to work on performance, > I suggest that you take a look at other parts of the system, like RX. The RX part seems to deal with RPC. I do not see the reason why it can improve performance. Maybe it is some Asynchronous RPC? -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 6:32:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from blubb.pdc.kth.se (blubb.pdc.kth.se [130.237.221.147]) by builder.freebsd.org (Postfix) with SMTP id 14EBE4180 for ; Mon, 7 Feb 2000 06:32:49 -0800 (PST) Received: from joda by blubb.pdc.kth.se with local (Exim 1.71 #3) id 12HpDn-0003By-00; Mon, 7 Feb 2000 15:32:59 +0100 To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG, arla-drinkers@stacken.kth.se Subject: Re: Writing a multithreaded daemon process References: From: joda@pdc.kth.se (Johan Danielsson) Date: 07 Feb 2000 15:32:59 +0100 In-Reply-To: Zhihui Zhang's message of "Mon, 7 Feb 2000 07:37:28 -0500 (EST)" Message-ID: Lines: 11 User-Agent: Gnus/5.070083 (Pterodactyl Gnus v0.83) Emacs/20.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zhihui Zhang writes: > The RX part seems to deal with RPC. I do not see the reason why it > can improve performance. Eh, what do you think is moving the bits to and from your fileserver? For cached (non-network) accesses, arla is just slighly slower than FFS. /Johan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 6:54:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by builder.freebsd.org (Postfix) with ESMTP id 303C93EF6 for ; Mon, 7 Feb 2000 06:54:25 -0800 (PST) Received: from daemon.local.idaemons.org (pc062023.tokyo.jcom.ne.jp [210.155.62.23]) by ms.tokyo.jcom.ne.jp (8.9.1/3.7W 06/01/99) with ESMTP id XAA19302 for ; Mon, 7 Feb 2000 23:55:00 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id XAA36103; Mon, 7 Feb 2000 23:54:29 +0900 (JST) Date: Mon, 07 Feb 2000 23:54:36 +0900 Message-ID: <864sblukpf.wl@archon.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: freebsd-hackers@freebsd.org Subject: enhancement of pkg_* tools User-Agent: Wanderlust/2.2.17 (One Of Us) EMIKO/1.13.11 (Euglena viridis) FLIM/1.13.2 (Kasanui) APEL/10.1 MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Associated I. Daemons MIME-Version: 1.0 (generated by EMIKO 1.13.11 - "Euglena viridis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, there. I'm planning to work on enhancing pkg_install tools following after NetBSD's effort. Seems they've been making some remarkable improvements over FreeBSD's original work since 1997. For example: - pkg_add/pkg_info to speak HTTP as well as FTP - pkg_info/pkg_delete to accept wildcards - pkg_delete to support bidirectional recursive deletion, up and down toward dependencies . . Before proceeding my work, I'd like to know what those in charge of the tools think of that. Is already there a project in which I can join, or any arguments I should refer to? Tell me anything. Thanks in advance. -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( "If you choose not to decide you still have made a choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 9: 3: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by builder.freebsd.org (Postfix) with ESMTP id 4AA233FB3 for ; Mon, 7 Feb 2000 09:03:03 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA01969; Mon, 7 Feb 2000 09:03:06 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA70677; Mon, 7 Feb 2000 09:03:06 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 7 Feb 2000 09:03:06 -0800 (PST) Message-Id: <200002071703.JAA70677@vashon.polstra.com> To: marcov@stack.nl Subject: Re: how to compile without libc (so not static) In-Reply-To: <20000204161324.B2DE396D7@toad.stack.nl> References: <20000204161324.B2DE396D7@toad.stack.nl> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000204161324.B2DE396D7@toad.stack.nl>, Marco van de Voort wrote: > > I finished the syscalls, so now I moved on the initialisation code. > > To test that I try to create an empty binary, which doesn't link to libc: > > I've put in an hour effort, and wrote the following C file: > > int main (void) { > return 0; > } > > gcc -nostdlib empty.c /usr/lib/crti.o /usr/lib/crt0.o -o empty > > results in: > > /usr/lib/crt1.o: In function `_start': > /usr/lib/crt1.o(.text+0x4f): undefined reference to `atexit' > /usr/lib/crt1.o(.text+0x5c): undefined reference to `atexit' > /usr/lib/crt1.o(.text+0x6f): undefined reference to `exit' I suspect that "gcc" isn't the standard FreeBSD C compiler in your case. Try "which gcc" and find out. It works fine for me on both -stable and -current with "cc": blake$ cc -v -nostdlib hello.c Using builtin specs. gcc version 2.95.2 19991024 (release) /usr/libexec/cpp -lang-c -v -D__GNUC__=2 -D__GNUC_MINOR__=95 -Di386 -Dunix -D__FreeBSD__=4 -D__FreeBSD_cc_version=400004 -D__i386__ -D__unix__ -D__FreeBSD__=4 -D__FreeBSD_cc_version=400004 -D__i386 -D__unix -Acpu(i386) -Amachine(i386) -Asystem(unix) -Asystem(FreeBSD) -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -D__ELF__ hello.c /tmp/cciRD216.i GNU CPP version 2.95.2 19991024 (release) (i386 FreeBSD/ELF) #include "..." search starts here: #include <...> search starts here: /usr/include /usr/include End of search list. The following default directories have been omitted from the search path: /usr/include/g++ End of omitted list. /usr/libexec/cc1 /tmp/cciRD216.i -quiet -dumpbase hello.c -version -o /tmp/ccbyU216.s GNU C version 2.95.2 19991024 (release) (i386-unknown-freebsd) compiled by GNU C version 2.95.2 19991024 (release). /usr/libexec/elf/as -v -o /tmp/ccWvs216.o /tmp/ccbyU216.s GNU assembler version 2.9.1 (i386-unknown-freebsdelf), using BFD version 2.9.1 /usr/libexec/elf/ld -m elf_i386 -dynamic-linker /usr/libexec/ld-elf.so.1 -L/usr/libexec/elf -L/usr/libexec -L/usr/lib /tmp/ccWvs216.o /usr/libexec/elf/ld: warning: cannot find entry symbol _start; defaulting to 08048074 /tmp/ccWvs216.o: In function `main': /tmp/ccWvs216.o(.text+0xf): undefined reference to `printf' John -- John Polstra jdp@polstra.com 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 Feb 7 10:37:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by builder.freebsd.org (Postfix) with ESMTP id 5B6813E89 for ; Mon, 7 Feb 2000 10:37:15 -0800 (PST) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA01838; Mon, 7 Feb 2000 09:41:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Akinori -Aki- MUSHA" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: enhancement of pkg_* tools In-reply-to: Your message of "Mon, 07 Feb 2000 23:54:36 +0900." <864sblukpf.wl@archon.local.idaemons.org> Date: Mon, 07 Feb 2000 09:41:26 -0800 Message-ID: <1835.949945286@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm planning to work on enhancing pkg_install tools following > after NetBSD's effort. Seems they've been making some remarkable > improvements over FreeBSD's original work since 1997. For example: As the author of these tools, I would welcome those sorts of enhancements. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 11:13:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id 705E340BD for ; Mon, 7 Feb 2000 11:13:23 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id LAA11978 for hackers@freebsd.org; Mon, 7 Feb 2000 11:40:43 -0800 (PST) Date: Mon, 7 Feb 2000 11:40:43 -0800 From: Alfred Perlstein To: hackers@freebsd.org Subject: Syncing a vector of fileoffsets and lengths? Message-ID: <20000207114042.E25520@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible to submit several offsets of a file to be synced rather than calling fsync or mmap'ing over the file and calling msync()? The only way I can think of doing this is queuing write requests backed by a O_FSYNC fd to an aiod. Even then the desired result isn't really achived as instead of all the buffers being simultaniously queued for immediate IO the aiod will stall on each buffer. Is there a better way to submit multiple buffers for immediate sync without syncing the entire file? It seems that msync with MS_ASYNC would work (a bit kludgy), but it's not implemented according to the manpage. thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@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 Feb 7 11:15: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.2.7]) by builder.freebsd.org (Postfix) with ESMTP id 17443409E for ; Mon, 7 Feb 2000 11:15:05 -0800 (PST) Received: from hermes.tue.nl [131.155.2.46] by kweetal.tue.nl (8.9.3) id UAA03660 (ESMTP); Mon, 7 Feb 2000 20:15:46 +0100 (MET) Received: from deathstar (n95.dial.tue.nl [131.155.209.94]) by hermes.tue.nl (Postfix) with ESMTP id E365F2E802; Mon, 7 Feb 2000 20:15:43 +0100 (CET) From: "Marco van de Voort" To: John Polstra Date: Mon, 7 Feb 2000 20:13:19 +0100 Subject: Re: how to compile without libc (so not static) Cc: hackers@freebsd.org In-reply-to: <200002071703.JAA70677@vashon.polstra.com> References: <20000204161324.B2DE396D7@toad.stack.nl> X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000207191543.E365F2E802@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I suspect that "gcc" isn't the standard FreeBSD C compiler in your > case. Try "which gcc" and find out. It works fine for me on both > -stable and -current with "cc": It is an older one indeed. > blake$ cc -v -nostdlib hello.c > Using builtin specs. > gcc version 2.95.2 19991024 (release) > /usr/libexec/cpp -lang-c -v -D__GNUC__=2 -D__GNUC_MINOR__=95 -Di386 -Dunix -D__FreeBSD__=4 -D__FreeBSD_cc_version=400004 -D__i386__ -D__unix__ -D__FreeBSD__=4 -D__FreeBSD_cc_version=400004 -D__i386 -D__unix -Acpu(i386) -Amachine(i386) -Asystem(unix) -Asystem(FreeBSD) -Acpu(i386) - Amachine(i386) -Di386 -D__i386 -D__i386__ -D__ELF__ hello.c /tmp/cciRD216.i > GNU CPP version 2.95.2 19991024 (release) (i386 FreeBSD/ELF) > #include "..." search starts here: > #include <...> search starts here: > /usr/include > /usr/include > End of search list. > The following default directories have been omitted from the search path: > /usr/include/g++ > End of omitted list. > /usr/libexec/cc1 /tmp/cciRD216.i -quiet -dumpbase hello.c -version -o /tmp/ccbyU216.s > GNU C version 2.95.2 19991024 (release) (i386-unknown-freebsd) compiled by GNU C version 2.95.2 19991024 (release). > /usr/libexec/elf/as -v -o /tmp/ccWvs216.o /tmp/ccbyU216.s > GNU assembler version 2.9.1 (i386-unknown-freebsdelf), using BFD version 2.9.1 > /usr/libexec/elf/ld -m elf_i386 -dynamic-linker /usr/libexec/ld-elf.so.1 -L/usr/libexec/elf -L/usr/libexec -L/usr/lib /tmp/ccWvs216.o > /usr/libexec/elf/ld: warning: cannot find entry symbol _start; defaulting to 08048074 > /tmp/ccWvs216.o: In function `main': > /tmp/ccWvs216.o(.text+0xf): undefined reference to `printf' Still doesn't work though with the newer one :-) (try some arithmetic to see if that works. Marco van de Voort (MarcoV@Stack.nl) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 11:38:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 6B9A9404C for ; Mon, 7 Feb 2000 11:38:04 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA50114; Mon, 7 Feb 2000 11:38:43 -0800 (PST) (envelope-from dillon) Date: Mon, 7 Feb 2000 11:38:43 -0800 (PST) From: Matthew Dillon Message-Id: <200002071938.LAA50114@apollo.backplane.com> To: Alfred Perlstein Cc: hackers@FreeBSD.ORG Subject: Re: Syncing a vector of fileoffsets and lengths? References: <20000207114042.E25520@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Is it possible to submit several offsets of a file to be synced :rather than calling fsync or mmap'ing over the file and calling :msync()? : :The only way I can think of doing this is queuing write requests :backed by a O_FSYNC fd to an aiod. : :Even then the desired result isn't really achived as instead of :all the buffers being simultaniously queued for immediate IO :the aiod will stall on each buffer. : :Is there a better way to submit multiple buffers for immediate :sync without syncing the entire file? There is no way to do this currently. :It seems that msync with MS_ASYNC would work (a bit kludgy), but :it's not implemented according to the manpage. : :thanks, :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] The man page is wrong. It is implemented, but it doesn't guarentee that metadata will be written nor does it guarentee the timing of the data writes. I have long considered this problem. NFSv3 needs to be able to do ranged fsyncs to handle the commit RPC. It used to just fysnc the whole file (bad). Now it has a kludge to scan the buffers and write out the appropriate ones, which is better. However, it has the same problem that msync() has when doing a ranged sync - the metadata is not guarenteed. (When you do a normal fsync() the meta-data is guarenteed, even in the softupdates case). Only minor adjustments are required to brute-force the metadata, and a couple more adjustments to make it work properly with softupdates. Once I do this we can break the code out into its own system call. fsync2(fd, options, offset, size) ??? degenerate case would sync to the EOF if size == 0. synchronously fsyncs by default, FSYNC_ASYNC would run it asynchronously. You could async fsync it, then fsync it normally later on to make sure it has all gone out. We would also have to make a new VOP to do it, VOP_FSYNC2(), which would default to calling VOP_FSYNC() with a 0 offset and 0 size. I've been wanting to do this for a while. There are a huge number of uses for this sort of system call, including database apps and two of my own projects. I'm waiting till after the release before starting work on it. -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 Feb 7 12:29:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id 756784290 for ; Mon, 7 Feb 2000 12:29:16 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id MAA14485; Mon, 7 Feb 2000 12:56:36 -0800 (PST) Date: Mon, 7 Feb 2000 12:56:36 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: hackers@FreeBSD.ORG Subject: Re: Syncing a vector of fileoffsets and lengths? Message-ID: <20000207125636.G25520@fw.wintelcom.net> References: <20000207114042.E25520@fw.wintelcom.net> <200002071938.LAA50114@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002071938.LAA50114@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Feb 07, 2000 at 11:38:43AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000207 12:05] wrote: > > :Is it possible to submit several offsets of a file to be synced > :rather than calling fsync or mmap'ing over the file and calling > :msync()? > : > :The only way I can think of doing this is queuing write requests > :backed by a O_FSYNC fd to an aiod. > : > :Even then the desired result isn't really achived as instead of > :all the buffers being simultaniously queued for immediate IO > :the aiod will stall on each buffer. > : > :Is there a better way to submit multiple buffers for immediate > :sync without syncing the entire file? > > There is no way to do this currently. > > :It seems that msync with MS_ASYNC would work (a bit kludgy), but > :it's not implemented according to the manpage. > : > :thanks, > :-- > :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > > The man page is wrong. It is implemented, but it doesn't guarentee > that metadata will be written nor does it guarentee the timing of > the data writes. > > I have long considered this problem. NFSv3 needs to be able to do > ranged fsyncs to handle the commit RPC. It used to just fysnc the > whole file (bad). Now it has a kludge to scan the buffers and > write out the appropriate ones, which is better. However, it has > the same problem that msync() has when doing a ranged sync - the > metadata is not guarenteed. (When you do a normal fsync() the > meta-data is guarenteed, even in the softupdates case). > > Only minor adjustments are required to brute-force the metadata, and > a couple more adjustments to make it work properly with softupdates. > Once I do this we can break the code out into its own system call. > > fsync2(fd, options, offset, size) ??? > > degenerate case would sync to the EOF if size == 0. > > synchronously fsyncs by default, FSYNC_ASYNC would run it > asynchronously. > > You could async fsync it, then fsync it normally later on to > make sure it has all gone out. > > We would also have to make a new VOP to do it, VOP_FSYNC2(), which > would default to calling VOP_FSYNC() with a 0 offset and 0 size. > > I've been wanting to do this for a while. There are a huge number > of uses for this sort of system call, including database apps and > two of my own projects. I'm waiting till after the release before > starting work on it. I think this is still a step away from what is really needed, scheduling multiple vectors in different files in order to be written. The interface you are proposing is nice but not flexible to gain enough performance. I asked this question because of a problem that Postgresql has, basically multiple processes will be updating a file, they may do scattered IO to multiple offsets into the file, at the end of a transaction they want to sync the data... fsync(). ow. This causes buffers dirtied from multiple processes to be pushed to disk where they really only want thier own. The order doesn't really matter, just that all of the IO is on stable storage. I think two kinds of behavior are needed, ordered range fsync and unordered async fsync. The ordered range could be taken care of easily by your implementation, however for maximum effectiveness you'd want to allow for unordered async fsync and notification. The simplest way I can think of doing this keeping a per-process count of how many buffers where scheduled for async IO and allowing as many async ops to happen, incrementing the count, as each io completes it decrements the count and calls wakeup_one once it reaches 0 again. This would allow multiple sync IOs to be scheduled without stalling the process and at the same time allowing for notification when the IO actually completes. It also allows async fsync to be done across multiple files. The waiting syscall would simply sleep on the count variable in the process structure. I think there's enough fields in the struct buf to support this unordered, i'm not sure it will be possible to do this if the application wants FIFO async fsync. I can see this happenning pretty easily via the buffer interface but doing it via async msync() through the vm system eludes me. :) I assume you can get at the struct buf through the vm as that's how IO is scheduled in general, but I'll need to research it more. What do you think? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 12:56:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id B83C9411A for ; Mon, 7 Feb 2000 12:56:06 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA50540; Mon, 7 Feb 2000 12:56:52 -0800 (PST) (envelope-from dillon) Date: Mon, 7 Feb 2000 12:56:52 -0800 (PST) From: Matthew Dillon Message-Id: <200002072056.MAA50540@apollo.backplane.com> To: Alfred Perlstein Cc: hackers@FreeBSD.ORG Subject: Re: Syncing a vector of fileoffsets and lengths? References: <20000207114042.E25520@fw.wintelcom.net> <200002071938.LAA50114@apollo.backplane.com> <20000207125636.G25520@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I think two kinds of behavior are needed, ordered range fsync and :unordered async fsync. : :The ordered range could be taken care of easily by your implementation, :however for maximum effectiveness you'd want to allow for unordered :async fsync and notification. : :The simplest way I can think of doing this keeping a per-process count :of how many buffers where scheduled for async IO and allowing as many :async ops to happen, incrementing the count, as each io completes it :decrements the count and calls wakeup_one once it reaches 0 again. "Eeek". First, keep in mind that it is not possible to guarentee write ordering after the fact even if we had an interface for it. There are too many other subsystems which might flush a buffer out of order - the page daemon, update daemon, buf daemon, and clustering code, for example. Once the data has been thrown into a filesystem buffer, the game is over. (read the last paragraph for more on this). You can guarentee write ordering in only one place: When you actually issue the write. It should be possible to extend this with the AIO mechanism to handle the necessary synchronous and fsync cases by adding new opcodes, and we can certainly create an AIO call for fsync2, e.g. aio_fsync2(), to handle notification. This would run on top of the fsync2() system call and VOP_FSYNC2() filesystem API. We can add a link pointer dependancy to the aiocb to guarentee commit ordering or even to allow multiple iocb's to be issued in a single system call (and run sequentially). You then issue multiple aio's chained together with dependancies and wait for the last one to complete, then wait for the previous ones to complete (which will not block since you know they've already run once the last one returns). What we do not want to do is to create a whole new kernel notification mechanism *just* for fsync, nor do we want to pollute the argument space up *just* to avoid making multiple system calls. :I think there's enough fields in the struct buf to support this unordered, :i'm not sure it will be possible to do this if the application wants :FIFO async fsync. We aren't going to mess with struct buf. The goal is to simplify struct buf, not complexify it. Dealing with ordering dependancies properly is difficult at best - look at softupdates for example. The chance of getting it right and not introducing new deadlock or runaway bugs in anything under a couple of months is low. We would be letting ourselves in for a world of hurt. -Matt Matthew Dillon :What do you think? : :-Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 14:35:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id 8149A40BD for ; Mon, 7 Feb 2000 14:35:17 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id OAA03016; Mon, 7 Feb 2000 14:35:12 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id OAA03580; Mon, 7 Feb 2000 14:35:09 -0800 Received: from softweyr.com (dyn5.utah.xylan.com [198.206.184.241]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id OAA06275; Mon, 7 Feb 2000 14:35:04 -0800 (PST) Message-ID: <389F49F7.7290B179@softweyr.com> Date: Mon, 07 Feb 2000 15:40:55 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Matthew Dillon , hackers@freebsd.org Subject: Re: Syncing a vector of fileoffsets and lengths? References: <20000207114042.E25520@fw.wintelcom.net> <200002071938.LAA50114@apollo.backplane.com> <20000207125636.G25520@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > I asked this question because of a problem that Postgresql has, > basically multiple processes will be updating a file, they may do > scattered IO to multiple offsets into the file, at the end of a > transaction they want to sync the data... fsync(). ow. This causes > buffers dirtied from multiple processes to be pushed to disk where > they really only want thier own. The order doesn't really matter, > just that all of the IO is on stable storage. So, what you're looking for is something like writev, only having the vector entries consist of (fd, pos, nbytes) triples? And perhaps a sync vs. async flag on the call? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 15:22: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id 44D1C3FFE for ; Mon, 7 Feb 2000 15:22:06 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id PAA20689; Mon, 7 Feb 2000 15:49:25 -0800 (PST) Date: Mon, 7 Feb 2000 15:49:25 -0800 From: Alfred Perlstein To: Wes Peters Cc: Matthew Dillon , hackers@freebsd.org Subject: Re: Syncing a vector of fileoffsets and lengths? Message-ID: <20000207154925.A17536@fw.wintelcom.net> References: <20000207114042.E25520@fw.wintelcom.net> <200002071938.LAA50114@apollo.backplane.com> <20000207125636.G25520@fw.wintelcom.net> <389F49F7.7290B179@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <389F49F7.7290B179@softweyr.com>; from wes@softweyr.com on Mon, Feb 07, 2000 at 03:40:55PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Wes Peters [000207 15:02] wrote: > Alfred Perlstein wrote: > > > > I asked this question because of a problem that Postgresql has, > > basically multiple processes will be updating a file, they may do > > scattered IO to multiple offsets into the file, at the end of a > > transaction they want to sync the data... fsync(). ow. This causes > > buffers dirtied from multiple processes to be pushed to disk where > > they really only want thier own. The order doesn't really matter, > > just that all of the IO is on stable storage. > > So, what you're looking for is something like writev, only having > the vector entries consist of (fd, pos, nbytes) triples? And > perhaps a sync vs. async flag on the call? Yes, and a later callback to use to poll/wait for all the queued IO to complete. But the write interface shouldn't have to be with the sync interface. Someone could do this by opening another fd with O_FSYNC, the problem is that each write blocks until the IO is done instead of allowing it to be disksorted() into optimal ordering and possibly combined with other writes. A process doing this can cause the disk to seek back and forth because it has no idea of the optimal order to sync it's own file ranges. Also it then hangs waiting for IO to complete. We already have hooks to 'do stuff' when IO on a buffer completes, we even 'own' buffers over to processes, it seems like we're just half a step away from realizing this functionality, ie adding a flag to do the accounting, a syscall to poll/wait, a syscall to queue the requests and finally an interface to the filesystem to do range syncs instead of complete syncs. Well maybe it's a bit more than half a step. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 16: 5:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by builder.freebsd.org (Postfix) with ESMTP id E6FF83D90; Mon, 7 Feb 2000 16:05:44 -0800 (PST) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id TAA26117; Mon, 7 Feb 2000 19:06:16 -0500 (EST) Date: Mon, 7 Feb 2000 19:06:16 -0500 (EST) From: Bosko Milekic To: freebsd-stable@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: rtfree panic() (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm. Judging from the last CVS log entry for route.c (See r1.59), this problem can manifest itself in -current as well. I=B4m cross posting on th= e initial send, but please, when replying, redirect to [single, truly] appropriate list. It *appears* that rtfree() is puking because the rnh pointer is somehow (?= ) NULL. The rt_tables tree for the given address family either doesn't hold what's being looked for, or there's a problem with the rt_key macro. In any case, I'm not that comfortable with this part of the code yet, so if some route.c guru with radix tree know-how could take a look at this, I think that Shrihari (along with the others who have experienced this?) would appreciate it.=20 Note that if more infos. are needed, request it at the Shrihari's address below. ------------------------------------------------------------------------- | Bosko Milekic | Coffee vector: 1.0i+1.0j+1.0k | | Email: bmilekic@dsuper.net | Sleep vector: -1.0i-1.0j-1.0k | | WWW: http://pages.infinit.net/bmilekic/ | Resulting life: 0i+0j+0k (DNE)| ------------------------------------------------------------------------- ---------- Forwarded message ---------- Date: Mon, 7 Feb 2000 16:53:28 -0500 From: Shrihari Pandit To: Bosko Milekic Subject: rtfree panic() Hey there. I was hoping you might be able to give us hand in this problem: We have a couple of machines that run FreeBSD 3.4-STABLE and they are panicing randomly in rtfree(). These systems contain over 70,000 routes=20 in the routing table. IdlePTD 2600960 initial pcb at 210e34 panicstr: rtfree panic messages: --- panic: rtfree syncing disks... done dumping to dev 20001, offset 0 dump 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 23= 8 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 2= 19 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 = 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182= 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 16= 3 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 1= 44 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 = 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107= 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 8= 4 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 5= 9 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 3= 4 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9= 8 7 6 5 4 3 2 1 --- #0 boot (howto=3D256) at ../../kern/kern_shutdown.c:285 285 in ../../kern/kern_shutdown.c (kgdb) bt #0 boot (howto=3D256) at ../../kern/kern_shutdown.c:285 #1 0xc012b8e4 in at_shutdown ( function=3D0xc01f20a2 <__set_sysctl__debug_sym_sysctl___debug_if_tun_de= bug+934>, arg=3D0x3, queue=3D-1071640608) at ../../kern/kern_shutdown.c:446 #2 0xc016650f in rtfree (rt=3D0xc2413000) at ../../net/route.c:206 #3 0xc01668f7 in rtrequest (req=3D2, dst=3D0xc243de00, gateway=3D0xc243de1= 0, netmask=3D0xc2415670, flags=3D3, ret_nrt=3D0x0) at ../../net/route.c:50= 9 #4 0xc016be81 in in_ifadownkill (rn=3D0xc243e800, xap=3D0xc0201038) at ../../netinet/in_rmx.c:390 #5 0xc0165d68 in rn_walktree (h=3D0xc23f4200, f=3D0xc016be4c , w=3D0xc0201038) at ../../net/radix.c:959 #6 0xc016bec8 in in_ifadown (ifa=3D0xc23fb500) at ../../netinet/in_rmx.c:4= 10 #7 0xc016ff7f in rip_ctlinput (cmd=3D0, sa=3D0xc23fb548, vip=3D0x0) at ../../netinet/raw_ip.c:396 #8 0xc014148d in pfctlinput (cmd=3D0, sa=3D0xc23fb548) at ../../kern/uipc_domain.c:265 #9 0xc015e343 in if_unroute (ifp=3D0xc023ebc4, flag=3D1, fam=3D0) at ../../net/if.c:414 #10 0xc015e3cf in if_down (ifp=3D0xc023ebc4) at ../../net/if.c:449 #11 0xc01e7308 in etp_linkdown () #12 0xc01e97ab in cisco_keepalive () #13 0xc01e9ba8 in cisco_notify () #14 0xc01ecbad in etp_notify () ---Type to continue, or q to quit--- #15 0xc01e91e4 in hdlc_rcvhandler () #16 0xc01cf35e in l3_rcvhandler () #17 0xc01c857d in lind_event () #18 0xc01e7445 in hdlc_timeout () #19 0xc0130112 in softclock () at ../../kern/kern_timeout.c:132 --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 17:42:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by builder.freebsd.org (Postfix) with ESMTP id 6D83240B4; Mon, 7 Feb 2000 17:42:20 -0800 (PST) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id RAA19125; Mon, 7 Feb 2000 17:43:00 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002080143.RAA19125@gndrsh.dnsmgr.net> Subject: Re: rtfree panic() (fwd) In-Reply-To: from Bosko Milekic at "Feb 7, 2000 07:06:16 pm" To: bmilekic@dsuper.net (Bosko Milekic) Date: Mon, 7 Feb 2000 17:42:59 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=UNKNOWN-8BIT Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [CC: to peter, could you MFC this??] [Charset X-UNKNOWN unsupported, skipping...] ARGHH!!!! > Hmmm. Judging from the last CVS log entry for route.c (See r1.59), this > problem can manifest itself in -current as well. I´m cross posting on the > initial send, but please, when replying, redirect to [single, truly] > appropriate list. No, this problem was fixed in -current with this commit (you looked at the wrong file, fix was in route.h): revision 1.30 date: 1999/06/30 23:11:15; author: msmith; state: Exp; lines: +2 -3 Increase the size of the route reference count from 15 bits to 31 bits. This doesn't change the size or alignment of the structure on either i386 or Alpha, and thus should be binary-compatible (modulo problems with old applications and routes with more than 2^15 references). Reviewed by: peter This has not been MFC's. Quick and easy for for 3.4 is to do this: - short rt_filler; /* was short flags field */ - short rt_refcnt; /* # held references */ + long rt_refcnt; /* # held references */ (Note tabs munged due to cut-n-paste with X). You should then recompile everything that deals with routes. Your experiencing the refcnt wrapping around past zero and then rtfree trying to reclaim the route which is really referenced 65536 times. > > It *appears* that rtfree() is puking because the rnh pointer is somehow (?) > NULL. The rt_tables tree for the given address family either doesn't hold > what's being looked for, or there's a problem with the rt_key macro. > > In any case, I'm not that comfortable with this part of the code yet, so > if some route.c guru with radix tree know-how could take a look at this, I > think that Shrihari (along with the others who have experienced > this?) would appreciate it. > > Note that if more infos. are needed, request it at the Shrihari's address > below. > > ------------------------------------------------------------------------- > | Bosko Milekic | Coffee vector: 1.0i+1.0j+1.0k | > | Email: bmilekic@dsuper.net | Sleep vector: -1.0i-1.0j-1.0k | > | WWW: http://pages.infinit.net/bmilekic/ | Resulting life: 0i+0j+0k (DNE)| > ------------------------------------------------------------------------- > > > ---------- Forwarded message ---------- > Date: Mon, 7 Feb 2000 16:53:28 -0500 > From: Shrihari Pandit > To: Bosko Milekic > Subject: rtfree panic() > > Hey there. > > I was hoping you might be able to give us hand in this problem: > > We have a couple of machines that run FreeBSD 3.4-STABLE and they are > panicing randomly in rtfree(). These systems contain over 70,000 routes > in the routing table. > > IdlePTD 2600960 > initial pcb at 210e34 > panicstr: rtfree > panic messages: > --- > panic: rtfree > > syncing disks... done > > dumping to dev 20001, offset 0 > dump 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 > --- > #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 > 285 in ../../kern/kern_shutdown.c > (kgdb) bt > #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 > #1 0xc012b8e4 in at_shutdown ( > function=0xc01f20a2 <__set_sysctl__debug_sym_sysctl___debug_if_tun_debug+934>, arg=0x3, queue=-1071640608) at ../../kern/kern_shutdown.c:446 > #2 0xc016650f in rtfree (rt=0xc2413000) at ../../net/route.c:206 > #3 0xc01668f7 in rtrequest (req=2, dst=0xc243de00, gateway=0xc243de10, > netmask=0xc2415670, flags=3, ret_nrt=0x0) at ../../net/route.c:509 > #4 0xc016be81 in in_ifadownkill (rn=0xc243e800, xap=0xc0201038) > at ../../netinet/in_rmx.c:390 > #5 0xc0165d68 in rn_walktree (h=0xc23f4200, f=0xc016be4c , > w=0xc0201038) at ../../net/radix.c:959 > #6 0xc016bec8 in in_ifadown (ifa=0xc23fb500) at ../../netinet/in_rmx.c:410 > #7 0xc016ff7f in rip_ctlinput (cmd=0, sa=0xc23fb548, vip=0x0) > at ../../netinet/raw_ip.c:396 > #8 0xc014148d in pfctlinput (cmd=0, sa=0xc23fb548) > at ../../kern/uipc_domain.c:265 > #9 0xc015e343 in if_unroute (ifp=0xc023ebc4, flag=1, fam=0) > at ../../net/if.c:414 > #10 0xc015e3cf in if_down (ifp=0xc023ebc4) at ../../net/if.c:449 > #11 0xc01e7308 in etp_linkdown () > #12 0xc01e97ab in cisco_keepalive () > #13 0xc01e9ba8 in cisco_notify () > #14 0xc01ecbad in etp_notify () > ---Type to continue, or q to quit--- > #15 0xc01e91e4 in hdlc_rcvhandler () > #16 0xc01cf35e in l3_rcvhandler () > #17 0xc01c857d in lind_event () > #18 0xc01e7445 in hdlc_timeout () > #19 0xc0130112 in softclock () at ../../kern/kern_timeout.c:132 > > --- -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 7 20: 5:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 276B23E10; Mon, 7 Feb 2000 20:05:32 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA52606; Mon, 7 Feb 2000 20:06:00 -0800 (PST) (envelope-from dillon) Date: Mon, 7 Feb 2000 20:06:00 -0800 (PST) From: Matthew Dillon Message-Id: <200002080406.UAA52606@apollo.backplane.com> To: "Rodney W. Grimes" Cc: bmilekic@dsuper.net (Bosko Milekic), freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: rtfree panic() (fwd) References: <200002080143.RAA19125@gndrsh.dnsmgr.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :No, this problem was fixed in -current with this commit (you looked at :the wrong file, fix was in route.h): : :revision 1.30 :date: 1999/06/30 23:11:15; author: msmith; state: Exp; lines: +2 -3 :Increase the size of the route reference count from 15 bits to 31 bits. : :This doesn't change the size or alignment of the structure on either i386 :or Alpha, and thus should be binary-compatible (modulo problems with old :applications and routes with more than 2^15 references). :... :> #9 0xc015e343 in if_unroute (ifp=0xc023ebc4, flag=1, fam=0) :> at ../../net/if.c:414 :> #10 0xc015e3cf in if_down (ifp=0xc023ebc4) at ../../net/if.c:449 :> #11 0xc01e7308 in etp_linkdown () :> #12 0xc01e97ab in cisco_keepalive () :> #13 0xc01e9ba8 in cisco_notify () :> #14 0xc01ecbad in etp_notify () :> ---Type to continue, or q to quit--- :> #15 0xc01e91e4 in hdlc_rcvhandler () :> #16 0xc01cf35e in l3_rcvhandler () :> #17 0xc01c857d in lind_event () :> #18 0xc01e7445 in hdlc_timeout () :> #19 0xc0130112 in softclock () at ../../kern/kern_timeout.c:132 :> :> --- :-- :Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net I am only partially familiar with this sync board. I don't know what the bug is but I strongly suspect that if_down() is not being called at splnet() by the sync board's driver code. It might be possible to test this hypothesis by modifying the if_down() routine in net/if.c to surround it with an splnet() call, e.g.: /* * Mark an interface down and notify protocols of * the transition. * NOTE: must be called at splnet or eqivalent. */ void if_down(ifp) register struct ifnet *ifp; { int s = splnet(); /* ADDME */ if_unroute(ifp, IFF_UP, AF_UNSPEC); splx(s); /* ADDME */ } And see if that solves the problem. We fixed another similar bug last year in regards to the low-memory garbage collection code not freeing routes at the correct spl. There could be other similar problems. I recall that this driver's source is not distributed. If I'm wrong then there is an avenue to pursue with the source (namely determining if the source calls the IF routines at the correct spl). -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 Tue Feb 8 1:38: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by builder.freebsd.org (Postfix) with ESMTP id 1E9533F11 for ; Tue, 8 Feb 2000 01:36:44 -0800 (PST) Received: from we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id KAA19175 for ; Tue, 8 Feb 2000 10:35:54 +0100 (MET) Message-ID: <389FE377.51A1972A@we.lc.ehu.es> Date: Tue, 08 Feb 2000 10:35:51 +0100 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: wondering about apm_cpu_{idle,busy}() in sys/i386/apm/apm.c Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am doing some experiments with my new laptop and APM, so I carefully read the apm(4) source (sys/i386/apm/apm.c), and I found the functions apm_cpu_idle() and apm_cpu_busy(). I understand the double CPU halting issue. However, I wonder about where are these two functions invoked from: jose@v-ger[~]$ find /usr/src/sys -name "*.[chsS]" | xargs fgrep apm_cpu_idle /usr/src/sys/i386/apm/apm.c:apm_cpu_idle(void) /usr/src/sys/i386/include/apm_bios.h:void apm_cpu_idle(void); And the same happens with apm_cpu_busy(). Are these functions actually used in the kernel? What did I miss? Cheers, -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 8 9:25: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by builder.freebsd.org (Postfix) with ESMTP id D44CB434F; Tue, 8 Feb 2000 09:24:36 -0800 (PST) Received: from cs.strath.ac.uk (posh.dmem.strath.ac.uk [130.159.202.3]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id RAA15748 Tue, 8 Feb 2000 17:25:10 GMT Message-ID: <38A05163.2A286AD@cs.strath.ac.uk> Date: Tue, 08 Feb 2000 17:24:51 +0000 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: multimedia@freebsd.org, hackers@freebsd.org Subject: Wanted: sound API experts for OpenH323 (NetMeeting for Unix) project Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I need some help with the sound ioctls for the OpenH323 project. (OpenH323 can be called NetMeeting for Unix) OpenH323 is an Open Source H323 Video Conferening package, with full duplex audio and bi-directional video. It is ported to Linux and Windows, and can connect to a wide range of H323 compatible video conferencing programs, including NetMeeting. I'm working on the FreeBSD port and can now stream video from FreeBSD to NetMeeting and visa versa using our Bt848 driver. BUT... I need help with the audio ioctls. I've got all the linux source, but need to cook up FreeBSD audio code, especially for the full duplex audio. And I need some help. If you are interested, take a look at www.openh323.org and email me. I've got the latest source, not yet checked into the OpenH323 project wich fixes a few build errors on FreeBSD 3.4. It would be good to get this done in the next few days as it will make it onto the FreeBSD 4.0 release disks. Any helpers out there? Thanks Roger -- Roger Hardiman Bt848/Bt878 driver maintainer roger@cs.strath.ac.uk roger@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 Feb 8 9:46:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by builder.freebsd.org (Postfix) with ESMTP id F065F3E30 for ; Tue, 8 Feb 2000 09:46:10 -0800 (PST) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id MAA17550 for hackers@freebsd.org; Tue, 8 Feb 2000 12:46:55 -0500 (EST) (envelope-from luoqi) Date: Tue, 8 Feb 2000 12:46:55 -0500 (EST) From: Luoqi Chen Message-Id: <200002081746.MAA17550@lor.watermarkgroup.com> To: hackers@freebsd.org Subject: Yahoo under attack Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just saw it in the news, http://abcnews.go.com/sections/tech/DailyNews/yahoo000207.html Does anyone know the detail? -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 8 9:54: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ms1.meiway.com (ms1.meiway.com [212.73.210.73]) by builder.freebsd.org (Postfix) with ESMTP id EE7B43DD5 for ; Tue, 8 Feb 2000 09:53:46 -0800 (PST) Received: from sv [212.73.210.75] by ms1.meiway.com with ESMTP (SMTPD32-5.05) id A8E6355027C; Tue, 08 Feb 2000 18:56:54 +0100 Message-Id: <4.2.2.20000208185157.00c97100@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 08 Feb 2000 18:54:25 +0100 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: T1 / E1 PCI card for FreeBSD? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Something like the Ariel RS2000 card. Ariel supports NT and Linux, but I'm a pure FreeBSD shop now (on the opens source side) and would not like to add a Linux box just for this. ( may end up buying a used PM 3A 2PT E1 ) thanks, Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 8 10: 5:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from medulla.hippocampus.net (medulla.hippocampus.net [204.138.241.6]) by builder.freebsd.org (Postfix) with ESMTP id 667D5408D for ; Tue, 8 Feb 2000 10:05:27 -0800 (PST) Received: from localhost (marc@localhost) by medulla.hippocampus.net (8.9.3/8.9.2) with ESMTP id NAA10174; Tue, 8 Feb 2000 13:06:36 -0500 (EST) Date: Tue, 8 Feb 2000 13:06:36 -0500 (EST) From: Marc Nicholas X-Sender: marc@medulla.hippocampus.net To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: T1 / E1 PCI card for FreeBSD? In-Reply-To: <4.2.2.20000208185157.00c97100@mail.Go2France.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try: http://www.etinc.com Never used their products, however. -marc ------------------------------------------------------------------- Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com "Fast, Expandable and Affordable Internet Caching Products" 1.877.464.4776 416.979.9000x11 fax: 416.979.8223 cell: 416.346.9255 On Tue, 8 Feb 2000, Len Conrad wrote: > Something like the Ariel RS2000 card. Ariel supports NT and Linux, but I'm > a pure FreeBSD shop now (on the opens source side) and would not like to > add a Linux box just for this. > > ( may end up buying a used PM 3A 2PT E1 ) > > thanks, > Len > > > > > 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 Feb 8 10: 7: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hatfield.mail.easynet.net (hatfield.mail.easynet.net [195.40.1.39]) by builder.freebsd.org (Postfix) with SMTP id 94A6F3ECB for ; Tue, 8 Feb 2000 10:06:47 -0800 (PST) Received: (qmail 28297 invoked from network); 8 Feb 2000 18:07:27 -0000 Received: from frnk-m227-227.pool.mediaways.net (HELO scully) (62.52.227.227) by hatfield.mail.easynet.net with SMTP; 8 Feb 2000 18:07:27 -0000 Message-ID: <001101bf725e$f76d7020$030000ac@scully> From: "Johnathan Meehan" To: References: <200002081746.MAA17550@lor.watermarkgroup.com> Subject: Re: Yahoo under attack Date: Tue, 8 Feb 2000 19:03:49 +0100 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.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Luoqi, Try these for a little more detail: http://www.antionline.com/cgi-bin/AntiLinks.cgi?url=http://www.nytimes.com/l ibrary/tech/00/02/biztech/articles/08yahoo.html http://www.securityfocus.com/templates/frame.html?adgroup=secnews&url=/exter nal/http%3a%2f%2fwww.currents.net%2fnewstoday%2f00%2f02%2f08%2fnews2.html http://www.securityfocus.com/templates/frame.html?adgroup=secnews&url=/exter nal/http%3a%2f%2fnews.cnet.com%2fnews%2f0-1005-200-1544455.html%3ftag%3dst.n e.1002.thed.1005-200-1544455 I don't know. Whatever happened to hackers? *poof* and they went, to be replaced by idiots. You'll note that YahoO! is still regarded as the most reliable web site, though. Jonno ----- Original Message ----- From: Luoqi Chen To: Sent: Tuesday, February 08, 2000 6:46 PM Subject: Yahoo under attack > Just saw it in the news, > http://abcnews.go.com/sections/tech/DailyNews/yahoo000207.html > Does anyone know the detail? > > -lq > > > 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 Feb 8 10:58: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by builder.freebsd.org (Postfix) with ESMTP id 7B6EF4120 for ; Tue, 8 Feb 2000 10:57:34 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA06743; Tue, 8 Feb 2000 10:58:25 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA73853; Tue, 8 Feb 2000 10:58:24 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 8 Feb 2000 10:58:24 -0800 (PST) Message-Id: <200002081858.KAA73853@vashon.polstra.com> To: marcov@stack.nl Subject: Re: how to compile without libc (so not static) In-Reply-To: <20000207191543.E365F2E802@hermes.tue.nl> References: <20000204161324.B2DE396D7@toad.stack.nl> <20000207191543.E365F2E802@hermes.tue.nl> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000207191543.E365F2E802@hermes.tue.nl>, Marco van de Voort wrote: > > I suspect that "gcc" isn't the standard FreeBSD C compiler in your > > case. Try "which gcc" and find out. It works fine for me on both > > -stable and -current with "cc": > > It is an older one indeed. [...] > Still doesn't work though with the newer one :-) > (try some arithmetic to see if that works. What do you mean, "Still doesn't work"? If you are using the /usr/bin/cc that comes with FreeBSD, and if -nostdlib causes the crt* files and libc to be omitted from the link, then it works. Making it do something useful is _your_ problem, not ours. :-) We don't recommend or support linking that way. John -- John Polstra jdp@polstra.com 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 Tue Feb 8 11:15:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by builder.freebsd.org (Postfix) with ESMTP id 969EC4304 for ; Tue, 8 Feb 2000 11:15:30 -0800 (PST) Received: from crbowman.erols.com ([209.122.47.155] helo=fermion) by smtp02.mrf.mail.rcn.net with smtp (Exim 2.12 #3) id 12IG7a-000617-00 for hackers@freebsd.org; Tue, 8 Feb 2000 14:16:23 -0500 X-Sender: crbowman@pop.erols.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 08 Feb 2000 14:14:51 -0500 To: hackers@freebsd.org From: "Christopher R. Bowman" Subject: Books Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I apologize in advance if anyone feels this is in appropriate. If you feel I need to be flamed please do it directly and not via the list. I have 2 books here that I wish to get rid of and since none of the local bookstores want them I will offer them here free of charge (I will pay shipping) to the person(s) who respond directly to me (and not the list) in 24 hours with the best explanation of how one or more will be put to good use. Hennesy and Patterson: Computer Architecture A Quantitative Approach (1st Ed) ISBN 1-881609-08-1 pristine condition Shanley and Anderson: PCI System Architecture (2nd Ed) ISBN 1-55860-069-8 small rip in paperback cover I also have: Wolfram: Mathematica (2nd Ed) ISBN 0-201-51502-4 paperback a little beat up on the corners. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 8 11:24:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by builder.freebsd.org (Postfix) with ESMTP id 857683E8F for ; Tue, 8 Feb 2000 11:24:38 -0800 (PST) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id TAA15471; Tue, 8 Feb 2000 19:25:30 GMT (envelope-from joe) Date: Tue, 8 Feb 2000 19:25:29 +0000 From: Josef Karthauser To: "Christopher R. Bowman" Cc: hackers@FreeBSD.ORG Subject: Re: Books Message-ID: <20000208192529.G3502@florence.pavilion.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 08, 2000 at 02:14:51PM -0500, Christopher R. Bowman wrote: > I apologize in advance if anyone feels this is in appropriate. If > you feel I need to be flamed please do it directly and not via the > list. > > I have 2 books here that I wish to get rid of and since none of > the local bookstores want them I will offer them here free of charge > (I will pay shipping) to the person(s) who respond directly to me > (and not the list) in 24 hours with the best explanation of how > one or more will be put to good use. > > Hennesy and Patterson: Computer Architecture A Quantitative Approach ^^^^^^^ I'm sure that this bloke was a lecturer of mine when I was at uni. Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 8 11:47:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by builder.freebsd.org (Postfix) with ESMTP id 2735E40D7 for ; Tue, 8 Feb 2000 11:47:41 -0800 (PST) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id OAA17110; Tue, 8 Feb 2000 14:55:18 -0500 (EST) (envelope-from cyouse@paradox.nexuslabs.com) Date: Tue, 8 Feb 2000 14:55:17 -0500 (EST) From: Charles Youse To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: T1 / E1 PCI card for FreeBSD? In-Reply-To: <4.2.2.20000208185157.00c97100@mail.Go2France.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lanmedia makes some pretty good T1/E1 PCI cards, and they support FreeBSD. (They actually wrote a FreeBSD driver for one of their cards at my request). Check out www.lanmedia.com. Chuck On Tue, 8 Feb 2000, Len Conrad wrote: > Something like the Ariel RS2000 card. Ariel supports NT and Linux, but I'm > a pure FreeBSD shop now (on the opens source side) and would not like to > add a Linux box just for this. > > ( may end up buying a used PM 3A 2PT E1 ) > > thanks, > Len > > > > > 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 Feb 8 11:49:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by builder.freebsd.org (Postfix) with ESMTP id 776074136 for ; Tue, 8 Feb 2000 11:49:34 -0800 (PST) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA93431; Tue, 8 Feb 2000 11:51:23 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Luoqi Chen Cc: hackers@FreeBSD.ORG Subject: Re: Yahoo under attack In-reply-to: Your message of "Tue, 08 Feb 2000 12:46:55 EST." <200002081746.MAA17550@lor.watermarkgroup.com> Date: Tue, 08 Feb 2000 11:51:23 -0800 Message-ID: <93428.950039483@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just saw it in the news, > http://abcnews.go.com/sections/tech/DailyNews/yahoo000207.html > Does anyone know the detail? I just exchanged email with David Filo this morning about this and it appears to have been a DoS attack using the usual array of stream/synflood tools. It also primarily hit the routers and FreeBSD 3.4 was largely unaffected (2.2 had some problems, but they were already in the process of upgrading those machines). There is some additional hardening work we can do here as a result of what was learned during the attack, however, and you should be seeing the relevant commits going into 4.0 shortly. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 8 12:27: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-03-real.cdsnet.net (mail-03-real.cdsnet.net [204.118.244.93]) by builder.freebsd.org (Postfix) with SMTP id D0A2E3EB4 for ; Tue, 8 Feb 2000 12:27:01 -0800 (PST) Received: (qmail 34437 invoked from network); 8 Feb 2000 20:24:44 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-03-real.cdsnet.net with SMTP; 8 Feb 2000 20:24:44 -0000 Date: Tue, 8 Feb 2000 12:22:23 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Marc Nicholas Cc: Len Conrad , freebsd-hackers@FreeBSD.ORG Subject: Re: T1 / E1 PCI card for FreeBSD? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have several of the etinc cards. If you can live with Dennis's rather curt manner, they're perfectly fine cards. I'm going to get one of the LMC boards though, integrated CSU/DSU would be nice, and possibly save a few bucks. ET has a bandwidth manager that works very nicely, and is a heck of a lot simpler to configure than dummynet. Free with the PCI cards, some $'s if you just want it by itself. My only ET gripe is that the new PCI cards lost the watchdog timer function that was handy for those remote reboots... On Tue, 8 Feb 2000, Marc Nicholas wrote: > Try: > > http://www.etinc.com > > Never used their products, however. > > > -marc > > ------------------------------------------------------------------- > Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com > "Fast, Expandable and Affordable Internet Caching Products" > 1.877.464.4776 416.979.9000x11 fax: 416.979.8223 cell: 416.346.9255 > > On Tue, 8 Feb 2000, Len Conrad wrote: > > > Something like the Ariel RS2000 card. Ariel supports NT and Linux, but I'm > > a pure FreeBSD shop now (on the opens source side) and would not like to > > add a Linux box just for this. > > > > ( may end up buying a used PM 3A 2PT E1 ) > > > > thanks, > > Len > > > > > > > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 8 12:50:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from screech.weirdnoise.com (209-128-78-198.bayarea.net [209.128.78.198]) by builder.freebsd.org (Postfix) with ESMTP id 1034D42FB for ; Tue, 8 Feb 2000 12:50:16 -0800 (PST) Received: from screech.weirdnoise.com (localhost [127.0.0.1]) by screech.weirdnoise.com (8.9.3/8.9.3) with ESMTP id MAA26424; Tue, 8 Feb 2000 12:46:44 -0800 Message-Id: <200002082046.MAA26424@screech.weirdnoise.com> X-Mailer: exmh version 2.0.2 To: Luoqi Chen Cc: hackers@FreeBSD.ORG Subject: Re: Yahoo under attack In-Reply-To: Your message of "Tue, 08 Feb 2000 11:51:23 PST." <93428.950039483@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Feb 2000 12:46:43 -0800 From: Ed Hall Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you want to read some more about this in the mainstream press, check out: http://www.washingtonpost.com/wp-dyn/business/A23174-2000Feb7.html http://news.cnet.com/news/0-1005-200-1544455.html http://news.cnet.com/news/0-1005-200-1543918.html The NY Times coverage is reasonable as well (though you have to be registered to view it on their site). The AP report (which you'll find in many newspapers) was fairly reasonable to start, but sometime during the night the AP reporter decided to add a bit from a self-proclaimed security expert about Yahoo!'s lack of preparation and management. I'll let you decide if he's qualified to comment (the security expert's website is at www.tscm.com). As a Yahoo! employee there isn't any more I can (or reasonably should) say. But I'll say one more thing anyway: FreeBSD wasn't the problem, here. It has been, and will continue to be, part of the solution. -Ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 8 16: 9:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f78.law4.hotmail.com [216.33.149.78]) by builder.freebsd.org (Postfix) with SMTP id 4C6C242FB for ; Tue, 8 Feb 2000 13:43:05 -0800 (PST) Received: (qmail 96552 invoked by uid 0); 8 Feb 2000 21:39:05 -0000 Message-ID: <20000208213905.96551.qmail@hotmail.com> Received: from 209.185.179.170 by www.hotmail.com with HTTP; Tue, 08 Feb 2000 13:39:05 PST X-Originating-IP: [209.185.179.170] From: "Jason Simms" To: hackers@freebsd.org Subject: Localization and locale()? Date: Tue, 08 Feb 2000 16:39:05 EST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am currently writing several programs that, for one reason or another, need to be localized in various sections. On Solaris, I can see what choices I have by running 'locale -a'. However, all my attempts to find a similar function on FreeBSD 3.4 have failed. I would have searched the mailing list archives, but they are, of course, currently down. Also, my search through the handbook also only showed examples for Russian and German encoding (section 12). For my specific problem, I need access to the following three character sets: es_ES.ISO8859-1 pt.PT.ISO8859-1 en_US.ISO8859-1 And within my program (Perl), I need to use the setlocale() function imported from the POSIX module (actually, from the locale_h header file). If I run this on FreeBSD, will the program die on me due to the apparent lack of a locale function? If one is available, where can I get it from? And finally, if these character sets are not installed on my system, what is the best way to go about getting them on there? Any help or insight would be appreciated, so thanks! Jason Simms ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 8 17:46:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vali.uas.alaska.edu (vali.uas.alaska.edu [137.229.150.18]) by builder.freebsd.org (Postfix) with SMTP id 0296E3E69 for ; Tue, 8 Feb 2000 14:36:30 -0800 (PST) Received: from antarctica.jun.alaska.edu [137.229.156.140] (HELO uas.alaska.edu) by vali.uas.alaska.edu (AltaVista Mail V2.0r/2.0r BL25r listener) id 0000_0068_38a0_99b1_a7d5; Tue, 08 Feb 2000 13:33:21 -0900 Message-ID: <38A099AE.2F65E21B@uas.alaska.edu> Date: Tue, 08 Feb 2000 13:33:18 -0900 From: Russ Pagenkopf X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: pthread problem (long and difficult) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiya folks! You've become my last hope for resolving my problem. I'm attempting to install CommuniGatePro and I've got a problem no one has the answer to. I've posted these questions to -questions and the CGPro list with no luck so... I'll list below the steps, questions and answers I've gotten with the hope that *someone* has the answer. ------ I wrote initially: > I'm attempting to install a mail program called CommuniGatePro from > Stalker Software. The program comes as a pre-compiled program. When I > first tried to run it after installation it gave me the following > error: > > /usr/libexec/ld-elf.so.1: ./CGServer: Undefined symbol > "pthread_attr_setscope" > > Okay. "What the hell does that mean" I ask myself. After a call to > tech support he briefly explained that it was for threading in the > kernel and he suggested upgrading to the latest stable (from 3.1). > Soooo... I learned how to use CTM (with some help from the list > archives). Then I learned how to make world (with help from the > handbook). Then I recompiled the kernel (been there, done that). > Then I rebooted. Other than forgetting to rebuild the passwd db, it > all worked (and from 1500 miles away too). > > Onward to installing CommuniGatePro. Installation goes fine, attempt > to run it and guess what? The same error: > > /usr/libexec/ld-elf.so.1: ./CGServer: Undefined symbol > "pthread_attr_setscope" > > uname -a > FreeBSD archives.mac-mgrs.org 3.4-STABLE FreeBSD 3.4-STABLE #0: Fri > Jan 28 04:57:14 PST 2000 > russ@archives.mac-mgrs.org:/usr/src/3.0-stable/sys/compile/ARCHIVES > i386 > > CTM patches through 449 (latest as of this morning). Douglas Brian Quayle wrote: > > pthread_attr_setscope() is a function used by Posix threads. I am > guessing you do not have Pthread support compiled into your kernel, > though I could be wrong. > > In your kernel configuration file, do you have the following three > lines? > > options "P1003_1B" > options "_KPOSIX_PRIORITY_SCHEDULING" > options "_KPOSIX_VERSION=199309L" > > Try adding these three lines and rebuilding the kernel > (config -r KERNEL; cd ../../compile/KERNEL; make depend; make; make > install). I wrote: > Ok, did this, and ... > > One more time I get, > /usr/libexec/ld-elf.so.1: ./CGServer: Undefined symbol > "pthread_attr_setscope" when I try to run the program. Douglas Brian Quayle wrote: > That version of FreeBSD does not support POSIX realtime options. The > way that you can check for this is to test for the preprocessor > constant _POSIX_THREAD_PRIORITY_SCHEDULING. WHOA!! So then I took this to the CGPro list. and Dmitry Akindinov wrote: > Could you please check if the following libraries exist on your > system: > /usr/lib/libc_r.so.3 or /usr/lib/libc_r.so.4 > > What is ldd output on the CGServer executable? I wrote: > They do now. Interesting, they don't get made during a make world. > Made world, made kernel, no luck, no response. > > archives# ldd CGServer > CGServer: > libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x281c8000) > libc_r.so.3 => /usr/lib/libc_r.so.3 (0x281dd000) > > And the relevant ls -lag > > archives# ls -lag /usr/lib/libcrypt.so.2 > lrwxrwxrwx 1 root wheel 16 Mar 20 1999 /usr/lib/libcrypt.so.2 -> > libdescrypt.so.222 > archives# ls -lag /usr/lib/libc_r.so.3 > -r--r--r-- 1 root wheel 566783 Jan 28 09:37 /usr/lib/libc_r.so.3 and finally Dmitry Akindinov wrote: > Quite strange: on our system the size for the "/usr/lib/libc_r.so.3" > library is 596538. That's FreeBSD 3.3-RELEASE. We didn't recompile the > kernel or install any additional libraries. > > Our local FreeBSD guru says that pthread support is built into the > libc_r shared object. I can just confirm that > > nm libc_r.so | grep pthread > > shows the "pthread_attr_setscope" as well. > So, short of reinstalling your FreeBSD clean, I can offer only > sending the libc_r library from our system. Now I can make the 1000 mile trip down to this machine and reinstall everything, but I'd *really* know how to fix what I've got or what the problem is. Any takers? Thanks, Russ Pagenkopf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 8 20: 2:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id A6F32429E for ; Tue, 8 Feb 2000 15:53:25 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA60082; Tue, 8 Feb 2000 15:52:50 -0800 (PST) (envelope-from dillon) Date: Tue, 8 Feb 2000 15:52:50 -0800 (PST) From: Matthew Dillon Message-Id: <200002082352.PAA60082@apollo.backplane.com> To: Ed Hall Cc: Luoqi Chen , hackers@FreeBSD.ORG Subject: Re: Yahoo under attack References: <200002082046.MAA26424@screech.weirdnoise.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :If you want to read some more about this in the mainstream press, check :out: : : http://www.washingtonpost.com/wp-dyn/business/A23174-2000Feb7.html : http://news.cnet.com/news/0-1005-200-1544455.html : http://news.cnet.com/news/0-1005-200-1543918.html : :The NY Times coverage is reasonable as well (though you have to be :registered to view it on their site). : :The AP report (which you'll find in many newspapers) was fairly reasonable :to start, but sometime during the night the AP reporter decided to add :a bit from a self-proclaimed security expert about Yahoo!'s lack of :preparation and management. I'll let you decide if he's qualified to :comment (the security expert's website is at www.tscm.com). : :As a Yahoo! employee there isn't any more I can (or reasonably should) :say. But I'll say one more thing anyway: FreeBSD wasn't the problem, :here. It has been, and will continue to be, part of the solution. : : -Ed Over the years BEST was attacked quite often. The routers were attacked, the machines were attacked, and so forth, a couple of times a month. Most of the attacks were impossible to trace due to source IP spoofing, even when they went on for long periods of time (as in hours), neither MCI nor Alternet were ever able to track down the sources or even really tried very hard to do so. There is only one way to stop this sort of attack, and that is to get on the various backbone's asses (MCI, Alternet, SprintLink, and so forth) and tell them to friggin enforce source filtering on all their border gateways (i.e. so people inside can only spoof IP's that fall in their own address space, thus leaving them traceable). These sorts of attacks have been well understood for years but virtually no action has been taken to make them traceable. Cisco has a few tricks these days but the real problem is that source filtering on border routers is an option rather then a requirement. Yahoo is big enough that it should be able to apply the appropriate pressure to finally get some action on this problem. BEST was never big enough to apply any significant pressure. -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 Tue Feb 8 22: 6:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.2.7]) by builder.freebsd.org (Postfix) with ESMTP id B68134535 for ; Tue, 8 Feb 2000 16:35:09 -0800 (PST) Received: from hermes.tue.nl [131.155.2.46] by kweetal.tue.nl (8.9.3) id BAA01597 (ESMTP); Wed, 9 Feb 2000 01:34:34 +0100 (MET) Received: from deathstar (n191.dial.tue.nl [131.155.209.190]) by hermes.tue.nl (Postfix) with ESMTP id 59C792E803; Wed, 9 Feb 2000 01:34:28 +0100 (CET) From: "Marco van de Voort" To: John Polstra Date: Wed, 9 Feb 2000 01:32:07 +0100 Subject: Re: how to compile without libc (so not static) Cc: hackers@freebsd.org In-reply-to: <200002081858.KAA73853@vashon.polstra.com> References: <20000207191543.E365F2E802@hermes.tue.nl> X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000209003428.59C792E803@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Still doesn't work though with the newer one :-) > > (try some arithmetic to see if that works. > > What do you mean, "Still doesn't work"? I can't compile a working file. >If you are using the > /usr/bin/cc that comes with FreeBSD, and if -nostdlib causes the > crt* files and libc to be omitted from the link, then it works. I'm not necessarily saying that it is a bug in cc, but in the gcc-csu (and maybe libc FreeBSD dependant parts) system as a whole > Making it do something useful is _your_ problem, not ours. :-) I haven't found a solution yet. I don't know what the ctor* and dtor* routines do, and if I can omit them. >We don't recommend or support linking that way. Who is we? And why do you think so? And who knows something about the internals of the CSU files? What can I rip out, what not? If I rip out most stuff it doesn't seem to work. The problem is that I can't find any example about how to do it. Marco van de Voort (MarcoV@Stack.nl) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 8 22:45:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.dynmc.net (ns1.dynmc.net [209.0.37.10]) by builder.freebsd.org (Postfix) with ESMTP id 7E5973ECB for ; Tue, 8 Feb 2000 16:50:37 -0800 (PST) Received: from localhost (omni@localhost) by ns1.dynmc.net (8.9.2/8.9.1) with ESMTP id QAA74603 for ; Tue, 8 Feb 2000 16:47:46 -0800 (PST) Date: Tue, 8 Feb 2000 16:47:46 -0800 (PST) From: "Gregory A. Carter" To: hackers@FreeBSD.ORG Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe omni@dynmc.net Greg +(Omni@Dynmc.Net)------------------------------------------------------+ | Dynamic Networking Solutions InterX Technologies | | Senior Network Administrator bits/keyID 1024/7DF9C285 | | omni@interx.net omni@itstudio.net omni@undernet.org omni@webpop3.com | +--------[ DC 50 57 59 C3 76 46 E8 EB 75 A8 94 FE 96 9E D3 ]----------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 0:30:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by builder.freebsd.org (Postfix) with ESMTP id 0D032403B for ; Tue, 8 Feb 2000 18:03:35 -0800 (PST) Received: from crbowman.erols.com ([209.122.47.155] helo=fermion) by smtp02.mrf.mail.rcn.net with smtp (Exim 2.12 #3) id 12IMST-00068R-00; Tue, 8 Feb 2000 21:02:22 -0500 X-Sender: crbowman@pop.erols.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 08 Feb 2000 21:00:51 -0500 To: Josef Karthauser From: "Christopher R. Bowman" Subject: Re: Books Cc: "Christopher R. Bowman" , hackers@FreeBSD.ORG In-Reply-To: <20000208192529.G3502@florence.pavilion.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:25 PM 2/8/00 +0000, Josef Karthauser wrote: >On Tue, Feb 08, 2000 at 02:14:51PM -0500, Christopher R. Bowman wrote: >> I apologize in advance if anyone feels this is in appropriate. If >> you feel I need to be flamed please do it directly and not via the >> list. >> >> I have 2 books here that I wish to get rid of and since none of >> the local bookstores want them I will offer them here free of charge >> (I will pay shipping) to the person(s) who respond directly to me >> (and not the list) in 24 hours with the best explanation of how >> one or more will be put to good use. >> >> Hennesy and Patterson: Computer Architecture A Quantitative Approach > ^^^^^^^ >I'm sure that this bloke was a lecturer of mine when I was at uni. If you went to Stanford he may well have been since he is a very well know lecturer there who was very involved with the move towards RISC architectures and the MIPS microprocessors that started there. -------- Christopher R. Bowman crb@ChrisBowman.com http://www.ChrisBowman.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 1: 5:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by builder.freebsd.org (Postfix) with ESMTP id 5F665487C for ; Tue, 8 Feb 2000 20:21:31 -0800 (PST) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id XAA76118 for ; Tue, 8 Feb 2000 23:20:55 -0500 (EST) Message-Id: <200002090420.XAA76118@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: rpc.lockd... is done. Date: Tue, 08 Feb 2000 23:20:54 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amitha (the person who has been working on the lockd code) has finished most of his work. There are still some issues with handling async locks and cancel messages. Also we were not able to implement the full NLM protocol as the FreeBSD kernel does not currently request NFS locks (we should fix that ASAP). This code is *ALPHA*. Even we will not be running it on production servers in the near future. PS: the tarball is at "http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-20000208.tar.gz" PPS: I would like to set this up in CVS for everyone's ease, could someone please tell em how to do this, and to make it available via cvsup? (We already have a complete FreeBSD cvsup mirror at cvsup.cs.rpi.edu, this would just be another "module", right? -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 1: 6:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from server1.huntsvilleal.com (www.huntsvilleal.com [207.13.224.7]) by builder.freebsd.org (Postfix) with ESMTP id 6FDD24369 for ; Tue, 8 Feb 2000 21:43:53 -0800 (PST) Received: from barricuda.bsd.nws.net (kris.huntsvilleal.com [207.13.224.46]) by server1.huntsvilleal.com (8.9.3/8.9.3) with ESMTP id AAA31698 for ; Wed, 9 Feb 2000 00:26:56 -0500 Received: from localhost (localhost [127.0.0.1]) by barricuda.bsd.nws.net (8.9.3/8.9.3) with ESMTP id XAA55511 for ; Tue, 8 Feb 2000 23:43:17 -0600 (CST) (envelope-from kris@hiwaay.net) Date: Tue, 8 Feb 2000 23:43:16 -0600 (CST) From: Kris Kirby To: hackers@freebsd.org Subject: PCI IDE Controller (HPT-366) supported? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anyone actively working on a driver for the High Point Technologies PCI disk controller (HPT-366)? I have a machine I can test on, and would be willing to assist. I'm tired of telling people that my motherboard has four IDE ports, but I can't use more than two under FreeBSD :-). --- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "God gave them the ability to reproduce... ... Science gave us the hope they won't." -KBK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 1: 6:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id D26B04335 for ; Tue, 8 Feb 2000 21:51:34 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id VAA29021; Tue, 8 Feb 2000 21:50:57 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id VAA25777; Tue, 8 Feb 2000 21:50:57 -0800 Received: from softweyr.com (dyn4.utah.xylan.com [198.206.184.240]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id VAA03685; Tue, 8 Feb 2000 21:50:56 -0800 (PST) Message-ID: <38A101A4.7500CAD1@softweyr.com> Date: Tue, 08 Feb 2000 22:56:52 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jason Simms Cc: hackers@freebsd.org Subject: Re: Localization and locale()? References: <20000208213905.96551.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Simms wrote: > > Hello, > > I am currently writing several programs that, for one reason or another, > need to be localized in various sections. On Solaris, I can see what > choices I have by running 'locale -a'. However, all my attempts to find a > similar function on FreeBSD 3.4 have failed. > > I would have searched the mailing list archives, but they are, of course, > currently down. Also, my search through the handbook also only showed > examples for Russian and German encoding (section 12). > > For my specific problem, I need access to the following three character > sets: > > es_ES.ISO8859-1 > pt.PT.ISO8859-1 > en_US.ISO8859-1 > > And within my program (Perl), I need to use the setlocale() function > imported from the POSIX module (actually, from the locale_h header file). > If I run this on FreeBSD, will the program die on me due to the apparent > lack of a locale function? If one is available, where can I get it from? > And finally, if these character sets are not installed on my system, what is > the best way to go about getting them on there? Any help or insight would > be appreciated, so thanks! man -k locale reports: mklocale(1) - make LC_CTYPE locale files perllocale(1) - Perl locale handling (internationalization and locali zation) setlocale(3), localeconv(3) - natural language formatting for C setrunelocale(3), setinvalidrune(3), sgetrune(3), sputrune(3) - rune support for C strxfrm(3) - transform a string under locale I18N::Collate(3) - compare 8-bit scalar data according to the current lo cale 1 *** 3 WARNING: starting from the Perl version 5.003_06 the I18N::Co llate interface for comparing 8-bit scalar data according to the current local e 1 HAS BEEN DEPRECATED 4 That is, please do not use it anymore for an y new applications and please migrate the old applications away from it becaus e its functionality was integrated into the Perl core language in the releas e 5.003_06. 1 See the perllocale manual page for further information. 1 *** locale(3) - Perl pragma to use and avoid POSIX locales for built- in operations It seems highly likely that either setlocale(3) or locale(3) are what you're looking for. So, I guess my advice would be to RTFM. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 1: 7:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by builder.freebsd.org (Postfix) with ESMTP id C3E1D4227 for ; Tue, 8 Feb 2000 22:27:45 -0800 (PST) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.3/8.9.3) id TAA12508 for freebsd-hackers@freebsd.org; Wed, 9 Feb 2000 19:27:12 +1300 (NZDT) Date: Wed, 9 Feb 2000 19:27:12 +1300 From: Joe Abley To: freebsd-hackers@freebsd.org Subject: Eclipse/BSD Message-ID: <20000209192710.A26889@patho.gen.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Files: the Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This may be old news, but I follow -hackers, -arch and -current and I hadn't seen it before: http://www.bell-labs.com/project/eclipse/release/ Would be interested to hear informed opinion as to whether these changes might find a permanent home in FreeBSD at some point in the future. ... The Eclipse Operating System is a testbed for Quality of Service (QoS) that is being developed at Information Sciences Research Center in Bell-Labs, Lucent Technologies. The current version of Eclipse, which we refer to as Eclipse/BSD, is based on FreeBSD version 3.4., and is compatible with FreeBSD, thus supporting the same system calls, protocols, device drivers and applications. Eclipse provides flexible and fine-grained QoS support for applications. Its design allows legacy or Eclipse-unaware applications to provide QoS without the need of modification or recompilation. A simple API is provided for (new) applications to take addvantage of the fine-grained QoS support. Currently, the Eclipse project targets QoS support for server applications, in particular, to differentiate the performance of different web sites hosted on the same platform (see the Apache examples). We have implemented: + hierarchical proportional-share cpu, disk and link schedulers, + the /reserv file system providing an API to manipulate "reservations", + a tagging mechanism for the association of reservatios with schedulable operations. The schedulers, such as network, cpu or disk, can easily be replaced by others that implement different algorithms by just implementing the Eclipse scheduler API functions. ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 1: 9:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by builder.freebsd.org (Postfix) with ESMTP id 0D032403B for ; Tue, 8 Feb 2000 18:03:35 -0800 (PST) Received: from crbowman.erols.com ([209.122.47.155] helo=fermion) by smtp02.mrf.mail.rcn.net with smtp (Exim 2.12 #3) id 12IMST-00068R-00; Tue, 8 Feb 2000 21:02:22 -0500 X-Sender: crbowman@pop.erols.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 08 Feb 2000 21:00:51 -0500 To: Josef Karthauser From: "Christopher R. Bowman" Subject: Re: Books Cc: "Christopher R. Bowman" , hackers@FreeBSD.ORG In-Reply-To: <20000208192529.G3502@florence.pavilion.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:25 PM 2/8/00 +0000, Josef Karthauser wrote: >On Tue, Feb 08, 2000 at 02:14:51PM -0500, Christopher R. Bowman wrote: >> I apologize in advance if anyone feels this is in appropriate. If >> you feel I need to be flamed please do it directly and not via the >> list. >> >> I have 2 books here that I wish to get rid of and since none of >> the local bookstores want them I will offer them here free of charge >> (I will pay shipping) to the person(s) who respond directly to me >> (and not the list) in 24 hours with the best explanation of how >> one or more will be put to good use. >> >> Hennesy and Patterson: Computer Architecture A Quantitative Approach > ^^^^^^^ >I'm sure that this bloke was a lecturer of mine when I was at uni. If you went to Stanford he may well have been since he is a very well know lecturer there who was very involved with the move towards RISC architectures and the MIPS microprocessors that started there. -------- Christopher R. Bowman crb@ChrisBowman.com http://www.ChrisBowman.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 1:40: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vali.uas.alaska.edu (vali.uas.alaska.edu [137.229.150.18]) by builder.freebsd.org (Postfix) with SMTP id EB8EB3EF0 for ; Wed, 9 Feb 2000 01:39:11 -0800 (PST) Received: from 134-pm1.jdc.alaska.net [209.112.136.134] (HELO uas.alaska.edu) by vali.uas.alaska.edu (AltaVista Mail V2.0r/2.0r BL25r listener) id 0000_0068_38a1_3593_5382; Wed, 09 Feb 2000 00:38:27 -0900 Message-ID: <389FE489.4A5129DC@uas.alaska.edu> Date: Tue, 08 Feb 2000 00:40:35 -0900 From: Russ Pagenkopf Reply-To: russ.pagenkopf@uas.alaska.edu X-Mailer: Mozilla 4.08 (Macintosh; I; PPC) MIME-Version: 1.0 To: "freebsd-hackers@freebsd.org" Subject: pthread problem (long and difficult) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiya folks! You've become my last hope for resolving my problem. I'm attempting to install CommuniGatePro and I've got a problem no one has the answer to. I've posted these questions to -questions and the CGPro list with no luck so... I'll list below the steps, questions and answers I've gotten with the hope that *someone* has the answer. ------ I wrote initially: > I'm attempting to install a mail program called CommuniGatePro from > Stalker Software. The program comes as a pre-compiled program. When I > first tried to run it after installation it gave me the following > error: > > /usr/libexec/ld-elf.so.1: ./CGServer: Undefined symbol > "pthread_attr_setscope" > > Okay. "What the hell does that mean" I ask myself. After a call to > tech support he briefly explained that it was for threading in the > kernel and he suggested upgrading to the latest stable (from 3.1). > Soooo... I learned how to use CTM (with some help from the list > archives). Then I learned how to make world (with help from the > handbook). Then I recompiled the kernel (been there, done that). > Then I rebooted. Other than forgetting to rebuild the passwd db, it > all worked (and from 1500 miles away too). > > Onward to installing CommuniGatePro. Installation goes fine, attempt > to run it and guess what? The same error: > > /usr/libexec/ld-elf.so.1: ./CGServer: Undefined symbol > "pthread_attr_setscope" > > uname -a > FreeBSD archives.mac-mgrs.org 3.4-STABLE FreeBSD 3.4-STABLE #0: Fri > Jan 28 04:57:14 PST 2000 > russ@archives.mac-mgrs.org:/usr/src/3.0-stable/sys/compile/ARCHIVES > i386 > > CTM patches through 449 (latest as of this morning). Douglas Brian Quayle wrote: > > pthread_attr_setscope() is a function used by Posix threads. I am > guessing you do not have Pthread support compiled into your kernel, > though I could be wrong. > > In your kernel configuration file, do you have the following three > lines? > > options "P1003_1B" > options "_KPOSIX_PRIORITY_SCHEDULING" > options "_KPOSIX_VERSION=199309L" > > Try adding these three lines and rebuilding the kernel > (config -r KERNEL; cd ../../compile/KERNEL; make depend; make; make > install). I wrote: > Ok, did this, and ... > > One more time I get, > /usr/libexec/ld-elf.so.1: ./CGServer: Undefined symbol > "pthread_attr_setscope" when I try to run the program. Douglas Brian Quayle wrote: > That version of FreeBSD does not support POSIX realtime options. The > way that you can check for this is to test for the preprocessor > constant _POSIX_THREAD_PRIORITY_SCHEDULING. WHOA!! So then I took this to the CGPro list. and Dmitry Akindinov wrote: > Could you please check if the following libraries exist on your > system: > /usr/lib/libc_r.so.3 or /usr/lib/libc_r.so.4 > > What is ldd output on the CGServer executable? I wrote: > They do now. Interesting, they don't get made during a make world. > Made world, made kernel, no luck, no response. > > archives# ldd CGServer > CGServer: > libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x281c8000) > libc_r.so.3 => /usr/lib/libc_r.so.3 (0x281dd000) > > And the relevant ls -lag > > archives# ls -lag /usr/lib/libcrypt.so.2 > lrwxrwxrwx 1 root wheel 16 Mar 20 1999 /usr/lib/libcrypt.so.2 -> > libdescrypt.so.222 > archives# ls -lag /usr/lib/libc_r.so.3 > -r--r--r-- 1 root wheel 566783 Jan 28 09:37 /usr/lib/libc_r.so.3 and finally Dmitry Akindinov wrote: > Quite strange: on our system the size for the "/usr/lib/libc_r.so.3" > library is 596538. That's FreeBSD 3.3-RELEASE. We didn't recompile the > kernel or install any additional libraries. > > Our local FreeBSD guru says that pthread support is built into the > libc_r shared object. I can just confirm that > > nm libc_r.so | grep pthread > > shows the "pthread_attr_setscope" as well. > So, short of reinstalling your FreeBSD clean, I can offer only > sending the libc_r library from our system. Now I can make the 1000 mile trip down to this machine and reinstall everything, but I'd *really* know how to fix what I've got or what the problem is. Any takers? Thanks, Russ Pagenkopf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 1:44: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netgroup-serv.polito.it (netgroup-serv.polito.it [130.192.28.4]) by builder.freebsd.org (Postfix) with SMTP id 159D83D7D for ; Wed, 9 Feb 2000 01:43:41 -0800 (PST) Received: from nebbiolo (unverified [130.192.16.135]) by netgroup-serv.polito.it (EMWAC SMTPRS 0.83) with SMTP id ; Wed, 09 Feb 2000 10:46:31 +0100 Message-Id: <3.0.6.32.20000209104307.0090c210@netgroup-serv.polito.it> X-Sender: ceci@netgroup-serv.polito.it X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 09 Feb 2000 10:43:07 +0100 To: freebsd-hackers@FreeBSD.org From: Valerio Ceci Subject: subscribe Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 1:57:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by builder.freebsd.org (Postfix) with ESMTP id B29DB3EAB for ; Wed, 9 Feb 2000 01:56:18 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 4FA891CD7; Wed, 9 Feb 2000 17:55:45 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Kris Kirby Cc: hackers@freebsd.org Subject: Re: PCI IDE Controller (HPT-366) supported? In-Reply-To: Message from Kris Kirby of "Tue, 08 Feb 2000 23:43:16 CST." Date: Wed, 09 Feb 2000 17:55:45 +0800 From: Peter Wemm Message-Id: <20000209095545.4FA891CD7@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kirby wrote: > Is anyone actively working on a driver for the High Point Technologies PCI > disk controller (HPT-366)? I have a machine I can test on, and would be > willing to assist. I'm tired of telling people that my motherboard has > four IDE ports, but I can't use more than two under FreeBSD :-). Under -current only: ata-pci1: port 0xb000-0xb0ff,0xac00-0xac03,0xa800-0xa807 irq 17 at device 13.0 on pci0 ata-pci2: port 0xbc00-0xbcff,0xb800-0xb803,0xb400-0xb407 irq 17 at device 13.1 on pci0 ata-pci3: port 0xc800-0xc8ff,0xc400-0xc403,0xc000-0xc007 irq 16 at device 15.0 on pci0 ata-pci4: port 0xd400-0xd4ff,0xd000-0xd003,0xcc00-0xcc07 irq 16 at device 15.1 on pci0 ata-pci5: port 0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 18 at device 19.0 on pci0 ata-pci6: port 0xec00-0xecff,0xe800-0xe803,0xe400-0xe407 irq 18 at device 19.1 on pci0 ad0: 9787MB [19885/16/63] at ata2-master using UDMA33 ad1: 6149MB [13328/15/63] at ata3-master using UDMA33 ad2: 6149MB [13328/15/63] at ata4-master using UDMA33 ad3: 6149MB [13328/15/63] at ata5-master using UDMA33 ad4: 6149MB [13328/15/63] at ata6-master using UDMA33 ad5: 6149MB [13328/15/63] at ata7-master using UDMA33 vinum list ... 1 plexes: P vol0.p0 R5 State: up Subdisks: 6 Size: 30 GB 6 subdisks: S vol0.p0.s0 State: up PO: 0 B Size: 6149 MB S vol0.p0.s1 State: up PO: 128 kB Size: 6149 MB S vol0.p0.s2 State: up PO: 256 kB Size: 6149 MB S vol0.p0.s3 State: up PO: 384 kB Size: 6149 MB S vol0.p0.s4 State: up PO: 512 kB Size: 6149 MB S vol0.p0.s5 State: up PO: 640 kB Size: 6149 MB It works just nicely here. It leaves the PIIX4 in the dust when both drives on the same controller are active. (not on the same cable, but one disk on each connector so there is no master/slave contention). Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 1:57:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from milhouse.cnbinc.com (martin2.lnk.telstra.net [139.130.137.91]) by builder.freebsd.org (Postfix) with ESMTP id 3A005438E for ; Wed, 9 Feb 2000 01:57:13 -0800 (PST) Received: from bender (bender.cnbinc.com [203.38.182.20]) by milhouse.cnbinc.com (8.9.3/8.9.3) with SMTP id UAA04128; Wed, 9 Feb 2000 20:24:02 +1030 (CST) (envelope-from diskiller@cnbinc.com) Message-ID: <001901bf72e3$8e609460$14b626cb@bender.cnbinc.com> From: "Martin Minkus" To: , "freebsd-hackers@freebsd.org" References: <389FE489.4A5129DC@uas.alaska.edu> Subject: Re: pthread problem (long and difficult) Date: Wed, 9 Feb 2000 20:23:45 +1030 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.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 3.4-RELEASE milhouse:/usr/lib> nm libc_r.so.3 | grep pthread_attr_set 00015d08 T pthread_attr_setcreatesuspend_np 00015ccc T pthread_attr_setdetachstate 00015ca4 T pthread_attr_setinheritsched 00015c78 T pthread_attr_setschedparam 00015c48 T pthread_attr_setschedpolicy 00015c3c T pthread_attr_setscope 00015c10 T pthread_attr_setstackaddr 00015be0 T pthread_attr_setstacksize milhouse:/usr/lib> You'll notice that i have pthread_attr_setscope Maybe something strange happened with make world (i doubt it) and your libc_r hasn't been updated ... ls -al /usr/lib | grep libc What are the date's on the files? (Esp. libc_r). Does it match when you made world ? Or are they much older? -- diskiller@cnbinc.com Linux/FreeBSD hacker ----- Original Message ----- From: Russ Pagenkopf To: freebsd-hackers@freebsd.org Sent: Tuesday, February 08, 2000 8:10 PM Subject: pthread problem (long and difficult) > > /usr/libexec/ld-elf.so.1: ./CGServer: Undefined symbol > > "pthread_attr_setscope" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 2:20:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from racine.cybercable.fr (racine.cybercable.fr [212.198.0.201]) by builder.freebsd.org (Postfix) with SMTP id 4E3425531 for ; Wed, 9 Feb 2000 02:12:31 -0800 (PST) Received: (qmail 4339978 invoked from network); 9 Feb 2000 10:11:59 -0000 Received: from d016.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.16]) (envelope-sender ) by racine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 9 Feb 2000 10:11:59 -0000 Message-ID: <38A13C94.60CFEC57@cybercable.fr> Date: Wed, 09 Feb 2000 11:08:20 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kirby Cc: hackers@freebsd.org Subject: Re: PCI IDE Controller (HPT-366) supported? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of course, it works with FreeBSD (TM) The new IDE driver (ata) from the soon-to-become-Stable 4.0 supports the HPT366 : (from the dmesg of my BP6) ata-pci1: port 0xd400-0xd4ff, 0xd000-0xd003,0xcc00-0xcc07 irq 18 at device 19.0 on pci0 ata2-master: success setting up UDMA4 mode on HPT366 chip ad4: ATA-5 disk at ata2 as master ad4: 17418MB (35673120 sectors), 35390 cyls, 16 heads, 63 S/T, 512 B/S ad4: 16 secs/int, 1 depth queue, UDMA66 TfH Kris Kirby wrote: > > Is anyone actively working on a driver for the High Point Technologies PCI > disk controller (HPT-366)? I have a machine I can test on, and would be > willing to assist. I'm tired of telling people that my motherboard has > four IDE ports, but I can't use more than two under FreeBSD :-). > > --- > Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. > | > ------------------------------------------------------- > "God gave them the ability to reproduce... > ... Science gave us the hope they won't." -KBK > > 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 Feb 9 2:27: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mooseriver.com (superior.mooseriver.com [209.249.56.198]) by builder.freebsd.org (Postfix) with ESMTP id D90CA51C0 for ; Wed, 9 Feb 2000 01:59:47 -0800 (PST) Received: (from jgrosch@localhost) by mooseriver.com (8.9.3/8.9.3) id BAA59631; Wed, 9 Feb 2000 01:58:54 -0800 (PST) (envelope-from jgrosch) Date: Wed, 9 Feb 2000 01:58:53 -0800 From: Josef Grosch To: Joe Abley Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Eclipse/BSD Message-ID: <20000209015853.A59591@mooseriver.com> Reply-To: jgrosch@mooseriver.com References: <20000209192710.A26889@patho.gen.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000209192710.A26889@patho.gen.nz>; from jabley@patho.gen.nz on Wed, Feb 09, 2000 at 07:27:12PM +1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 09, 2000 at 07:27:12PM +1300, Joe Abley wrote: > This may be old news, but I follow -hackers, -arch and -current and > I hadn't seen it before: > > http://www.bell-labs.com/project/eclipse/release/ > > Would be interested to hear informed opinion as to whether these > changes might find a permanent home in FreeBSD at some point in > the future. The license terms do not seem very good. I would advise caution. The last time we got into a pissing contest with these guys over license terms and who owns what it cost us 2 years of development and momentum which we are just now getting back. Josef -- Josef Grosch | Another day closer to a | FreeBSD 3.4 jgrosch@MooseRiver.com | Micro$oft free world | UNIX for the masses To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 2:39:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by builder.freebsd.org (Postfix) with ESMTP id 7E3C64A28 for ; Wed, 9 Feb 2000 02:35:10 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA33396; Wed, 9 Feb 2000 11:34:31 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002091034.LAA33396@freebsd.dk> Subject: Re: PCI IDE Controller (HPT-366) supported? In-Reply-To: from Kris Kirby at "Feb 8, 2000 11:43:16 pm" To: kris@hiwaay.net (Kris Kirby) Date: Wed, 9 Feb 2000 11:34:31 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kris Kirby wrote: > Is anyone actively working on a driver for the High Point Technologies PCI > disk controller (HPT-366)? I have a machine I can test on, and would be > willing to assist. I'm tired of telling people that my motherboard has > four IDE ports, but I can't use more than two under FreeBSD :-). It is fully supported in -current soon to be 4.0. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 2:45:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id C9DF33F09 for ; Wed, 9 Feb 2000 02:45:34 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id DAA23774; Wed, 9 Feb 2000 03:11:53 -0800 (PST) Date: Wed, 9 Feb 2000 03:11:53 -0800 From: Alfred Perlstein To: Russ Pagenkopf Cc: "freebsd-hackers@freebsd.org" Subject: Re: pthread problem (long and difficult) Message-ID: <20000209031153.V17536@fw.wintelcom.net> References: <389FE489.4A5129DC@uas.alaska.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <389FE489.4A5129DC@uas.alaska.edu>; from russ.pagenkopf@uas.alaska.edu on Tue, Feb 08, 2000 at 12:40:35AM -0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Russ Pagenkopf [000209 02:58] wrote: > Hiya folks! > > You've become my last hope for resolving my problem. I'm attempting to > install CommuniGatePro and I've got a problem no one has the answer to. > I've posted these questions to -questions and the CGPro list with no > luck so... I'll list below the steps, questions and answers I've gotten > with the hope that *someone* has the answer. > ------ > I wrote initially: > > > uname -a > > FreeBSD archives.mac-mgrs.org 3.4-STABLE FreeBSD 3.4-STABLE #0: Fri > > Jan 28 04:57:14 PST 2000 > > russ@archives.mac-mgrs.org:/usr/src/3.0-stable/sys/compile/ARCHIVES > > i386 > > > > CTM patches through 449 (latest as of this morning). hmm, I'd have used cvsup: pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz > > Douglas Brian Quayle wrote: > > > > pthread_attr_setscope() is a function used by Posix threads. I am > > guessing you do not have Pthread support compiled into your kernel, > > though I could be wrong. > > > > In your kernel configuration file, do you have the following three > > lines? > > > > options "P1003_1B" > > options "_KPOSIX_PRIORITY_SCHEDULING" > > options "_KPOSIX_VERSION=199309L" > > > > Try adding these three lines and rebuilding the kernel > > (config -r KERNEL; cd ../../compile/KERNEL; make depend; make; make > > install). > Ok, this was wrong, the kernel really shouldn't have anything to do with this error, he's right when he says it's a library issue later... > I wrote: > > > Ok, did this, and ... > > > > One more time I get, > > /usr/libexec/ld-elf.so.1: ./CGServer: Undefined symbol > > "pthread_attr_setscope" when I try to run the program. > > Douglas Brian Quayle wrote: > > That version of FreeBSD does not support POSIX realtime options. The > > way that you can check for this is to test for the preprocessor > > constant _POSIX_THREAD_PRIORITY_SCHEDULING. > > WHOA!! So then I took this to the CGPro list. > > and Dmitry Akindinov wrote: > > > Could you please check if the following libraries exist on your > > system: > > /usr/lib/libc_r.so.3 or /usr/lib/libc_r.so.4 > > > > What is ldd output on the CGServer executable? > > I wrote: > > > They do now. Interesting, they don't get made during a make world. > > Made world, made kernel, no luck, no response. > > > > archives# ldd CGServer > > CGServer: > > libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x281c8000) > > libc_r.so.3 => /usr/lib/libc_r.so.3 (0x281dd000) > > > > And the relevant ls -lag > > > > archives# ls -lag /usr/lib/libcrypt.so.2 > > lrwxrwxrwx 1 root wheel 16 Mar 20 1999 /usr/lib/libcrypt.so.2 -> > > libdescrypt.so.222 > > archives# ls -lag /usr/lib/libc_r.so.3 > > -r--r--r-- 1 root wheel 566783 Jan 28 09:37 /usr/lib/libc_r.so.3 ls -lag /usr/lib/libc_r* -and- nm libc_r.so | grep pthread_attr_setscope please? > > and finally Dmitry Akindinov wrote: > > Quite strange: on our system the size for the "/usr/lib/libc_r.so.3" > > library is 596538. That's FreeBSD 3.3-RELEASE. We didn't recompile the > > kernel or install any additional libraries. > > > > Our local FreeBSD guru says that pthread support is built into the > > libc_r shared object. I can just confirm that > > > > nm libc_r.so | grep pthread > > > > shows the "pthread_attr_setscope" as well. > > So, short of reinstalling your FreeBSD clean, I can offer only > > sending the libc_r library from our system. > > Now I can make the 1000 mile trip down to this machine and reinstall > everything, but I'd *really* know how to fix what I've got or what the > problem is. Any takers? It looks like you may have missed some CTM deltas? I'm not really sure how CTM works at all, I would try cvsup, make world one more time and see what happens. Also get back to me on the ls and nm commands. thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 2:48: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from carina.stf.gov.br (carina.stf.gov.br [200.130.5.6]) by builder.freebsd.org (Postfix) with SMTP id 514AD4343 for ; Wed, 9 Feb 2000 02:47:52 -0800 (PST) Received: from rafael (unverified [200.130.5.11]) by carina.stf.gov.br (EMWAC SMTPRS 0.83) with SMTP id ; Wed, 09 Feb 2000 08:46:47 -0200 Reply-To: From: "Rafael" To: Cc: Subject: Hackers Date: Wed, 9 Feb 2000 09:48:04 -0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Disposition-Notification-To: "Rafael" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matéria retirada do New York Times Several Web Sites Are Attacked on Day After Assault Shut Yahoo By MATT RICHTEL with SARA ROBINSON February 9, 2000 AN FRANCISCO -- Hackers mounted what appeared to be coordinated attacks on the world's largest electronic commerce sites Tuesday. The attacks, which opened a window on the widespread vulnerability of the Internet, began Monday with a three-hour assault on Yahoo.com, one of the world's most popular Web sites, and continued Tuesday, temporarily crippling at least four other major sites, including Amazon.com, eBay.com and Buy.com. By Tuesday night it had spread to a leading media site, CNN.com. Officials from Buy.com, an online retailer, and the popular auction site eBay.com said they could not determine for certain whether all the attacks were related or were by the same person or persons. George Grotz, a spokesman for the San Francisco office of the FBI, said: "We are still in dialogue with Yahoo. We are aware of the others." As for whether the attacks had been by the same people, Grotz said, "I think it would be premature at this point to say anything along those lines." But security experts and the companies themselves said the nature of the attacks seemed too similar to be coincidental. Elias Levy, chief technology officer for SecurityFocus.com, which researches computer security issues, said the scope of the attacks was rare, if not unprecedented. He said the attackers had managed to assault and take down some of the world's most heavily enforced sites. Levy said the evidence suggested the attacks were related. Significantly, he said given how many resources were required to take down these sites, it would have been difficult for a copycat who witnessed Monday's attack on Yahoo to have instantly have followed suit in such similar fashion. "I have no doubt these are coming from the same individual or group," echoed John Vranesevich, the founder of antionline.com, a Web site focusing on computer security and hacking issues. It "is unthinkable" that several groups of hackers would have access to this many computers used to direct the attack, he added. Levy said he expected to see a substantial response from the FBI in the coming days. "We're going to see some very busy law enforcement tomorrow," he said. "I picture planes full of FBI agents heading to San Jose right now." In each case, the attackers used what is known as distributed denial of service, a technique that basically hijacks dozens or even hundreds or computers around the Internet and instructs each of the hijacked computers to bombard the target site with meaningless data. As the site's server tries to accommodate all the phony data, it soon runs out of memory and other resources. As a result, its responses to real customers slows to a crawl or ceases altogether. However, while it cripples the servers ability to deliver Web pages to customers, it does not violate the integrity of the system, nor does it allow access to data stored on the server. So while such attacks are an expensive form of vandalism, they do not threaten sensitive data like credit card numbers or other consumer information. While such attacks are not unusual, the intensity of the recent attacks, as measured by the sheer number of computers thought to have been hijacked for the effort, was virulent enough to bring down e-commerce sites that are typically fortified enough to fend off these kinds of assaults. Opening a window on the vulnerability of the Internet An eBay spokesman, Kevin Pursglove, said the auction site became inaccessible to some customers around 3:20 p.m. Pacific Standard Time, and it was still struggling to thwart the attack two hours later. He said the company had contacted Yahoo and Buy.com to seek advice and assistance in defending its servers. Bloomberg News reported Amazon.com was slowed for an hour by a deluge of junk traffic that started at about 5 p.m. Pacific time. The three-hour assault on Buy.com started at 10:50 a.m. Pacific time and, unfortunately for the company, the timing coincided with the company's initial public offering of stock. In the first day of trading, its shares closed at $25.125 each. Yahoo said it was getting hit with data from "more than 50" computers on the Internet. The company said it was contacted this morning by the FBI in connection with the attack. Greg Hawkins, chief executive of Buy.com, said the timing of the attack on the day of the IPO was "completely out of control, needless to say." "We had some people get in, " he said, "but in most cases, people couldn't get into the site." He said the site "clearly lost revenue" though he did not know how much. "We were hoping to see an increase in traffic because of the IPO." The stock opened at $27 and traded as high as $35. Vranesevich said the preliminary evidence suggested that the same hackers were responsible for each attack. In a denial of service attack, hackers hijack computers not their own and use them to direct random streams of data at the target, essentially causing the target machine to become paralyzed. _______________________________________________________ Rafael de Lara Resende Analista de Suporte - Supremo Tribunal Federal - Fone: (0xx61) 316-5263 mailto:rafael@stf.gov.br http://www.stf.gov.br ________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 5:40:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by builder.freebsd.org (Postfix) with ESMTP id 7DBD73E72 for ; Wed, 9 Feb 2000 05:40:17 -0800 (PST) Received: from newsguy.com (p12-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.141]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id WAA26137; Wed, 9 Feb 2000 22:39:39 +0900 (JST) Message-ID: <38A16386.E2CE324C@newsguy.com> Date: Wed, 09 Feb 2000 21:54:30 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Thierry Herbelot Cc: Kris Kirby , hackers@FreeBSD.ORG Subject: Re: PCI IDE Controller (HPT-366) supported? References: <38A13C94.60CFEC57@cybercable.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thierry Herbelot wrote: > > The new IDE driver (ata) from the soon-to-become-Stable 4.0 supports the > HPT366 : That is incorrect. While HPT-366 is supported on 4.0-CURRENT, 4.0 is not becoming -STABLE anytime soon. What's happening is that a -RELEASE of 4.0 will be made soon. The transition of the 4.x from -CURRENT to -STABLE will happen later this year. Or so I was led to believe by our Release Engineer. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 6:18:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by builder.freebsd.org (Postfix) with ESMTP id CA9643E93 for ; Wed, 9 Feb 2000 06:18:15 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 0584D1CD7; Wed, 9 Feb 2000 22:17:39 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: jgrosch@mooseriver.com Cc: Joe Abley , freebsd-hackers@FreeBSD.ORG Subject: Re: Eclipse/BSD In-Reply-To: Message from Josef Grosch of "Wed, 09 Feb 2000 01:58:53 PST." <20000209015853.A59591@mooseriver.com> Date: Wed, 09 Feb 2000 22:17:38 +0800 From: Peter Wemm Message-Id: <20000209141739.0584D1CD7@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Grosch wrote: > On Wed, Feb 09, 2000 at 07:27:12PM +1300, Joe Abley wrote: > > This may be old news, but I follow -hackers, -arch and -current and > > I hadn't seen it before: > > > > http://www.bell-labs.com/project/eclipse/release/ > > > > Would be interested to hear informed opinion as to whether these > > changes might find a permanent home in FreeBSD at some point in > > the future. > > The license terms do not seem very good. I would advise caution. The last > time we got into a pissing contest with these guys over license terms and > who owns what it cost us 2 years of development and momentum which we are > just now getting back. Without commenting on the license, Bell labs was not the group that was driving the lawsuit. It was AT&T/USG (Unix systems group) and later USL (unix support labs). Bell labs is now a part of Lucent these days anyway. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 6:32:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by builder.freebsd.org (Postfix) with ESMTP id 034E43D7D for ; Wed, 9 Feb 2000 06:32:41 -0800 (PST) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id PAA10985 for freebsd-hackers@freebsd.org; Wed, 9 Feb 2000 15:32:12 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id NAA04131 for freebsd-hackers@freebsd.org; Wed, 9 Feb 2000 13:29:55 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: Localization and locale()? Date: 9 Feb 2000 13:29:54 +0100 Message-ID: <87rmk2$40q$1@bigeye.rhein-neckar.de> References: <20000208213905.96551.qmail@hotmail.com> To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Simms wrote: > On Solaris, I can see what choices I have by running 'locale -a'. > However, all my attempts to find a similar function on FreeBSD 3.4 > have failed. There is no locale(1) command, true. You can find the available locales under /usr/share/locale. > es_ES.ISO8859-1 > pt.PT.ISO8859-1 > en_US.ISO8859-1 Those are available. It's ...ISO_8859-1, though. Notice the underscore. > And within my program (Perl), I need to use the setlocale() function > imported from the POSIX module (actually, from the locale_h header file). Well, then do it. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 8: 1:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by builder.freebsd.org (Postfix) with ESMTP id 05B303E54; Wed, 9 Feb 2000 08:01:21 -0800 (PST) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id RAA30279; Wed, 9 Feb 2000 17:00:41 +0100 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id QAA32385; Wed, 9 Feb 2000 16:51:03 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id E6E3252ACD; Wed, 9 Feb 2000 16:15:01 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id 8E6471F17; Wed, 9 Feb 2000 16:14:55 +0100 (CET) Subject: Re: T1 / E1 PCI card for FreeBSD? In-Reply-To: <4.2.2.20000208185157.00c97100@mail.Go2France.com> from Len Conrad at "Feb 8, 2000 6:54:25 pm" To: lconrad@Go2France.com (Len Conrad) Date: Wed, 9 Feb 2000 16:14:55 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG, phk@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000209151455.8E6471F17@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Len Conrad wrote: > Something like the Ariel RS2000 card. Ariel supports NT and Linux, but I'm > a pure FreeBSD shop now (on the opens source side) and would not like to > add a Linux box just for this. Didn't Poul-Henning wrote an E1 driver for a Siemens Munich chipset based card which is part of -current ? hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 8: 4:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by builder.freebsd.org (Postfix) with ESMTP id AC9F54000 for ; Wed, 9 Feb 2000 08:04:14 -0800 (PST) Received: from cs.rpi.edu (maniattb@dishwasher.cs.rpi.edu [128.213.8.31]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id LAA90603; Wed, 9 Feb 2000 11:03:40 -0500 (EST) Message-Id: <200002091603.LAA90603@cs.rpi.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: "Christopher R. Bowman" Cc: hackers@FreeBSD.ORG, maniattb@cs.rpi.edu Subject: Re: Books In-reply-to: Your message of "Tue, 08 Feb 2000 14:14:51 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 Feb 2000 11:03:37 -0500 From: Bill Maniatty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I apologize in advance if anyone feels this is in appropriate. If > you feel I need to be flamed please do it directly and not via the > list. > > I have 2 books here that I wish to get rid of and since none of > the local bookstores want them I will offer them here free of charge > (I will pay shipping) to the person(s) who respond directly to me > (and not the list) in 24 hours with the best explanation of how > one or more will be put to good use. > > Hennesy and Patterson: Computer Architecture A Quantitative Approach > (1st Ed) ISBN 1-881609-08-1 pristine condition Got this one already > Shanley and Anderson: PCI System Architecture (2nd Ed) > ISBN 1-55860-069-8 small rip in paperback cover I teach operating systems, and would like to add a device driver writing component to the curriculum. I could use this one. > I also have: > Wolfram: Mathematica (2nd Ed) ISBN 0-201-51502-4 paperback a little > beat up on the corners. > Would be nice to have but I don't have a compelling reason for needing it. Prof. William A. Maniatty |------------------------------------------| |Dr. William (Bill) A. Maniatty | |Assistant Professor | |Dept. of Computer Science | |University At Albany | |Albany, NY 12222 | |------------------------------------------| |Phone: (518) 442-4281 | |e-mail: maniatty@cs.albany.edu | |URL: http://www.cs.albany.edu/~maniatty| |------------------------------------------| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 8:20: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ms1.meiway.com (ms1.meiway.com [212.73.210.73]) by builder.freebsd.org (Postfix) with ESMTP id 6864E430E for ; Wed, 9 Feb 2000 08:19:34 -0800 (PST) Received: from sv [212.73.210.75] by ms1.meiway.com with ESMTP (SMTPD32-5.05) id A40516D50260; Wed, 09 Feb 2000 17:21:25 +0100 Message-Id: <4.2.2.20000209171149.054a1dd0@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 09 Feb 2000 17:18:49 +0100 To: freebsd-hackers@FreeBSD.ORG From: Len Conrad Subject: Re: T1 / E1 PCI card for FreeBSD? In-Reply-To: <20000209151455.8E6471F17@bert.kts.org> References: <4.2.2.20000208185157.00c97100@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I emailed with Poul with him a few months ago about HSSI i/f's and he said he was happy with the LanMedia.com LMC 1000. I'm looking at the LMC 1200 for this E1 project. LMC seems to support FreeBSD well. Dennis tells me etinc.com doesn't have any CSU/DSU cards, nor any support more than one channel. I realize, now, the next issue is really an CSU/DSU E1 / PRI card than can support the full 30 channels of 64 kbits/sec ISDN traffic. Suggestions? Len ============= > > Something like the Ariel RS2000 card. Ariel supports NT and Linux, but > I'm > > a pure FreeBSD shop now (on the opens source side) and would not like to > > add a Linux box just for this. > >Didn't Poul-Henning wrote an E1 driver for a Siemens Munich chipset based >card which is part of -current ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 8:50:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from maybe.csap.af.mil (mudd.csap.af.mil [192.203.1.250]) by builder.freebsd.org (Postfix) with SMTP id 3D2143FE7 for ; Wed, 9 Feb 2000 08:49:13 -0800 (PST) Received: from raider.csap.af.mil(really [192.168.70.17]) by maybe.csap.af.mil via sendmail with esmtp id for ; Wed, 9 Feb 2000 10:44:49 -0600 (CST) (Smail-3.2 1996-Jul-4 #5 built 1999-Sep-4) Message-Id: Content-Length: 706 X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 09 Feb 2000 10:45:15 -0600 (CST) From: Corey Leopold To: hackers@freebsd.org Subject: Creating Dedicated disk. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I have a situation where I have a Tar file of a complete 3.4 FreeBSD system from the / directory on down. I'm trying to get this file onto a new system using a "dangerously dedicated" scsi disk, but am having problems getting the boot sector right using, disklabel, fdisk, and boot0cfg on a picobsd boot floppy. The tar file resides on another hard disk. If anyone could give any hints on how to do this, or some documentation, it would be appreciated. If any more info is needed please let me know. Thanks in advance. Corey ---------------------------------- Corey Leopold E-Mail: Corey Leopold Phone (210)-925-3459 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 9:34:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mtolympus.ari.net (newmtolympus.ari.net [198.69.192.180]) by builder.freebsd.org (Postfix) with ESMTP id 01D8A404E; Wed, 9 Feb 2000 09:34:41 -0800 (PST) Received: from skibumnews.com (fedjobs.ari.net [198.69.195.130]) by mtolympus.ari.net (8.8.8/8.8.8) with SMTP id MAA22352; Wed, 9 Feb 2000 12:05:42 -0500 (EST) (envelope-from editor@SkiBumNews.com) Date: Wed, 9 Feb 2000 12:05:42 -0500 (EST) From: editor@SkiBumNews.com Message-Id: <200002091705.MAA22352@mtolympus.ari.net> Reply-To: editor@SkiBumNews.com To: editor@SkiBumNews.com Subject: Trade Hot Links Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We tried to contact you yesterday to see if you would you be interested in exchanging HOT LINKS with the Ski Bum News? There was a problem with our e-mail box, so we are contacting you again and using a different e-mail address. Our URL is http://SkiBumNews.com and we are an Internet skiing and snowboarding newsletter and e-zine. If you would like to have a HOT LINK on our site, just respond to this e-mail and please be sure to send us your URL and a brief description of your site. We are VERY sorry if we have bothered you. This will be the last time we contact you regarding this matter, unless you want to trade links with us. Quid Pro Quo, Paul Maraschiello To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 9:42:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by builder.freebsd.org (Postfix) with ESMTP id E2F5340CD for ; Wed, 9 Feb 2000 09:42:41 -0800 (PST) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id UAA00869; Wed, 9 Feb 2000 20:42:46 +0300 (MSK) Message-Id: <200002091742.UAA00869@aaz.links.ru> Subject: Re: Creating Dedicated disk. In-Reply-To: from "Corey Leopold" at "Feb 9, 0 10:45:15 am" To: leopold@mailcenter.csap.af.mil (Corey Leopold) Date: Wed, 9 Feb 2000 20:42:46 +0300 (MSK) Cc: hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Corey Leopold writes: > I have a situation where I have a Tar file of a complete 3.4 FreeBSD system > from the / directory on down. > > I'm trying to get this file onto a new system using a "dangerously dedicated" > scsi disk, but am having problems getting the boot sector right using, > disklabel, fdisk, and boot0cfg on a picobsd boot floppy. The tar file > resides on another hard disk. > > If anyone could give any hints on how to do this, or some documentation, it > would be appreciated. The easyest way is install FreeBSD on this disk and then untar over. Disable all servises before untar - cron, nfs so on. More powerfull is fdisk, disklabel and newfs disk booting FreeBSD on another disk then mount a slise in some dir (/mnt as example) and mkdir /mnt/usr /mnt/var so on and mount slises on this dirs. then untar, then edit /mnt/etc/fstab and /mnt/boot/... But count, dump/restore is better in regard of precision of fs details copied. > If any more info is needed please let me know. -- @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 Wed Feb 9 9:50:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bartok.lanl.gov (bartok.lanl.gov [128.165.205.72]) by builder.freebsd.org (Postfix) with ESMTP id 496D140C6; Wed, 9 Feb 2000 09:50:39 -0800 (PST) Received: (from john@localhost) by bartok.lanl.gov (8.9.2/8.9.2) id JAA02994; Wed, 9 Feb 2000 09:51:15 -0700 (MST) (envelope-from john) Date: Wed, 9 Feb 2000 09:51:15 -0700 (MST) Message-Id: <200002091651.JAA02994@bartok.lanl.gov> From: John Galbraith To: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: National Instruments AT-GPIB/TNT driver Cc: john@bartok.lanl.gov Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have posted a new version of my GPIB (IEEE 488, or HPIB) driver to www.ece.arizona.edu/~john. This one is a total rewrite of my old one and should be faster on small transfers and a bit more reliable overall. It has also been ported to the FreeBSD-4.0 newbus architecture. I have been running real experiments on it, so the basic stuff is working well for me. There is some documentation and some examples there, and instructions on how to install it. Please let me know if you are interested in this and if it works for you. There aren't many people using GPIB with FreeBSD, so I would like to know about everybody and anybody who ends up using this for anything so we can get it well tested. Thanks, John Galbraith john@bartok.lanl.gov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 10:26: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ms1.meiway.com (ms1.meiway.com [212.73.210.73]) by builder.freebsd.org (Postfix) with ESMTP id 856CB40FA for ; Wed, 9 Feb 2000 10:25:45 -0800 (PST) Received: from sv [212.73.210.75] by ms1.meiway.com with ESMTP (SMTPD32-5.05) id A19927B042E; Wed, 09 Feb 2000 19:27:37 +0100 Message-Id: <4.2.2.20000209191939.060d58a0@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 09 Feb 2000 19:24:58 +0100 To: freebsd-hackers@FreeBSD.ORG From: Len Conrad Subject: Re: T1 / E1 PCI card for FreeBSD? In-Reply-To: <4.2.2.20000209171149.054a1dd0@mail.Go2France.com> References: <20000209151455.8E6471F17@bert.kts.org> <4.2.2.20000208185157.00c97100@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dave@LanMedia.com tells me their P1200 E1 card, with FreeBSD drive, can't work in channelized mode (like the etinc cards can't). Their LMC150xM cards can do channelized, but don't have a FreeBSD driver, but their FreeBSD guy is looking at it. Any hacker care to explain how a channelized T1/E1 (24 or 30 separate ip streams) would be seen within FreeBSD? ifconfig setup? Would we have to assign 30 fixed ip addresses to these "virtual/channel" ip interfaces? thanks, Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 10:49:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by builder.freebsd.org (Postfix) with ESMTP id 57D56413A for ; Wed, 9 Feb 2000 10:49:45 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA34956; Wed, 9 Feb 2000 19:49:13 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002091849.TAA34956@freebsd.dk> Subject: Re: T1 / E1 PCI card for FreeBSD? In-Reply-To: <4.2.2.20000209191939.060d58a0@mail.Go2France.com> from Len Conrad at "Feb 9, 2000 07:24:58 pm" To: lconrad@Go2France.com (Len Conrad) Date: Wed, 9 Feb 2000 19:49:13 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Len Conrad wrote: > dave@LanMedia.com tells me their P1200 E1 card, with FreeBSD drive, can't > work in channelized mode (like the etinc cards can't). Their LMC150xM > cards can do channelized, but don't have a FreeBSD driver, but their > FreeBSD guy is looking at it. > > Any hacker care to explain how a channelized T1/E1 (24 or 30 separate ip > streams) would be seen within FreeBSD? ifconfig setup? Would we have to > assign 30 fixed ip addresses to these "virtual/channel" ip interfaces? Talk to Poul-Henning (phk@freebsd.org) he has done driver for this... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 10:50:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id E85AB41A3 for ; Wed, 9 Feb 2000 10:50:30 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id KAA08506; Wed, 9 Feb 2000 10:49:06 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id KAA14347; Wed, 9 Feb 2000 10:49:06 -0800 Received: from softweyr.com ([198.206.184.94]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id KAA05759; Wed, 9 Feb 2000 10:49:01 -0800 (PST) Message-ID: <38A1B807.F3BC660A@softweyr.com> Date: Wed, 09 Feb 2000 11:55:03 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Joe Abley Cc: freebsd-hackers@freebsd.org Subject: Re: Eclipse/BSD References: <20000209192710.A26889@patho.gen.nz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Abley wrote: > > This may be old news, but I follow -hackers, -arch and -current and > I hadn't seen it before: > > http://www.bell-labs.com/project/eclipse/release/ > > Would be interested to hear informed opinion as to whether these > changes might find a permanent home in FreeBSD at some point in > the future. It doesn't appear, from their licensing page, these changes are ever intended to be released to the FreeBSD project. The license is very restrictive about redistribution. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 11:48:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vali.uas.alaska.edu (vali.uas.alaska.edu [137.229.150.18]) by builder.freebsd.org (Postfix) with SMTP id 3F2094177 for ; Wed, 9 Feb 2000 11:48:20 -0800 (PST) Received: from antarctica.jun.alaska.edu [137.229.156.140] (HELO uas.alaska.edu) by vali.uas.alaska.edu (AltaVista Mail V2.0r/2.0r BL25r listener) id 0000_0068_38a1_c451_088f; Wed, 09 Feb 2000 10:47:29 -0900 Message-ID: <38A1C451.D2662A3A@uas.alaska.edu> Date: Wed, 09 Feb 2000 10:47:29 -0900 From: Russ Pagenkopf X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: "freebsd-hackers@freebsd.org" Cc: Martin Minkus , Alfred Perlstein Subject: Re: pthread problem (long and difficult) References: <389FE489.4A5129DC@uas.alaska.edu> <001901bf72e3$8e609460$14b626cb@bender.cnbinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the replies, I'm combining a couple of posts here. Martin Minkus wrote: > Maybe something strange happened with make world > (i doubt it) and your libc_r hasn't been updated ... > > ls -al /usr/lib | grep libc (ls -lag /usr/lib/libc_r* from below) -r--r--r-- 1 root wheel 1261712 Feb 4 00:09 /usr/lib/libc_r.a lrwxr-xr-x 1 root wheel 11 Feb 4 00:09 /usr/lib/libc_r.so -> libc_r.so4 -r--r--r-- 1 root wheel 566783 Jan 28 09:37 /usr/lib/libc_r.so.3 -r--r--r-- 1 root wheel 611034 Feb 4 00:09 /usr/lib/libc_r.so.4 -r--r--r-- 1 root wheel 1370192 Feb 4 00:09 /usr/lib/libc_r_p.a > What are the date's on the files? (Esp. libc_r). Does > it match when you made world ? Or are they much > older? I had to do a make-make install in /usr/src/lib to get them to compile and then I did a make world, and a kernel recompile. Alfred Perlstein wrote: > > > CTM patches through 449 (latest as of this morning). > > hmm, I'd have used cvsup: > > pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz Unfortunately, I haven't been able to get my brain around cvsup yet. ;) > ls -lag /usr/lib/libc_r* See above. > nm libc_r.so | grep pthread_attr_setscope 0001596c T pthread_attr_setscope > It looks like you may have missed some CTM deltas? I'm not really sure > how CTM works at all, I would try cvsup, make world one more time and > see what happens. I don't think I missed any deltas. I started at 400empty and went up from there, twice. Made world again, and no luck. Thanks for the help so far (and hoping for a solution :). Russ Pagenkopf > ----- Original Message ----- > From: Russ Pagenkopf > To: freebsd-hackers@freebsd.org > Sent: Tuesday, February 08, 2000 8:10 PM > Subject: pthread problem (long and difficult) > > > > /usr/libexec/ld-elf.so.1: ./CGServer: Undefined symbol > > > "pthread_attr_setscope" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 12: 5:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 7ADEF40C5 for ; Wed, 9 Feb 2000 12:05:18 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA67748; Wed, 9 Feb 2000 12:04:52 -0800 (PST) (envelope-from dillon) Date: Wed, 9 Feb 2000 12:04:52 -0800 (PST) From: Matthew Dillon Message-Id: <200002092004.MAA67748@apollo.backplane.com> To: hackers@FreeBSD.ORG Subject: Best article yet on Yahoo (etc.) attacks Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is the first one I've read that actually gets it right. They even try to explain the type of border router source-ip filters necessary to make these attacks traceable. -Matt http://www.sfgate.com/cgi-bin/article.cgi?file=/chronicle/archive/2000/02/09/MN23532.DTL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 12: 5:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from screech.weirdnoise.com (209-128-78-198.bayarea.net [209.128.78.198]) by builder.freebsd.org (Postfix) with ESMTP id 0F43C4177 for ; Wed, 9 Feb 2000 12:05:10 -0800 (PST) Received: from screech.weirdnoise.com (localhost [127.0.0.1]) by screech.weirdnoise.com (8.9.3/8.9.3) with ESMTP id MAA04192; Wed, 9 Feb 2000 12:04:53 -0800 Message-Id: <200002092004.MAA04192@screech.weirdnoise.com> X-Mailer: exmh version 2.0.2 To: Wes Peters Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Eclipse/BSD In-Reply-To: Your message of "Wed, 09 Feb 2000 11:55:03 MST." <38A1B807.F3BC660A@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 Feb 2000 12:04:53 -0800 From: Ed Hall Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : It doesn't appear, from their licensing page, these changes are ever : intended to be released to the FreeBSD project. The license is very : restrictive about redistribution. Not only that, but it contains that pernicious gag clause: "You agree not to release the results of any evaluation of the Licensed Software to any third party without the prior written approval of Lucent Technologies." Yuck! Why would I want to test out their software if I can't even reveal my results to anyone? -Ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 13:19:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vali.uas.alaska.edu (vali.uas.alaska.edu [137.229.150.18]) by builder.freebsd.org (Postfix) with SMTP id B2AE83E75 for ; Wed, 9 Feb 2000 13:19:04 -0800 (PST) Received: from antarctica.jun.alaska.edu [137.229.156.140] (HELO uas.alaska.edu) by vali.uas.alaska.edu (AltaVista Mail V2.0r/2.0r BL25r listener) id 0000_0068_38a1_d993_34a5; Wed, 09 Feb 2000 12:18:11 -0900 Message-ID: <38A1D994.AFB996E7@uas.alaska.edu> Date: Wed, 09 Feb 2000 12:18:12 -0900 From: Russ Pagenkopf X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: "freebsd-hackers@freebsd.org" , " (CommuniGate Pro Discussions)" Cc: "Technical Support, Stalker Labs" , Douglas Brian Quayle , Martin Minkus , Alfred Perlstein Subject: Summary: FreeBSD, posix, pthread problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG YEE HAW! The problem is fixed! The machine: FreeBSD 3.4-STABLE (ctm 451) The Problem: > I'm attempting to install CommuniGatePro. When I first tried to run it > after installation it gave me the following error: > > /usr/libexec/ld-elf.so.1: ./CGServer: Undefined symbol > "pthread_attr_setscope" The Solution: Alfred Perlstein wrote: the symlinks are set properly for you to use the 3 version of the library (you may want to copy libc_r.so.4 over libc_r.so.3). So, chflags noschg libc_r.so.3 mv libc_r.so.3 libc_r.so.3.bkp cp libc_r.so.4 libc_r.so.3 Voila'! Why does this work? Apparently (remember I'm not a C programmer) CGPro is being linked against libc_r.so.3 (which on FreeBSD appears to be an older library) as evidenced by: archives# ldd CGServer CGServer: libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x281c8000) libc_r.so.3 => /usr/lib/libc_r.so.3 (0x281dd000) instead of libc_r.so which symlinks to the latest library - libc_r.so.4. Now something else must also be going on while making world or compiling the kernel, because it seems to me that if the library libc_r.so.3 is physically there it should also be available for use, but apparently not. I'll keep copies of the email I've sent back and forth if anyone wants them, otherwise, just count me as one very happy camper! Thanks to everyone who had suggestions, everyone of them was valuable and helped point me in the right direction! Russ Pagenkopf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 14: 0:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id AEACD3E75 for ; Wed, 9 Feb 2000 13:59:40 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id OAA12933; Wed, 9 Feb 2000 14:26:05 -0800 (PST) Date: Wed, 9 Feb 2000 14:26:05 -0800 From: Alfred Perlstein To: Russ Pagenkopf Cc: "freebsd-hackers@freebsd.org" , " (CommuniGate Pro Discussions)" , "Technical Support, Stalker Labs" , Douglas Brian Quayle , Martin Minkus Subject: Re: Summary: FreeBSD, posix, pthread problems Message-ID: <20000209142605.H17536@fw.wintelcom.net> References: <38A1D994.AFB996E7@uas.alaska.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38A1D994.AFB996E7@uas.alaska.edu>; from russ.pagenkopf@uas.alaska.edu on Wed, Feb 09, 2000 at 12:18:12PM -0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Russ Pagenkopf [000209 13:45] wrote: > YEE HAW! The problem is fixed! glad to hear. :) > > The machine: > FreeBSD 3.4-STABLE > (ctm 451) > > The Problem: > > I'm attempting to install CommuniGatePro. When I first tried to run it > > after installation it gave me the following error: > > > > /usr/libexec/ld-elf.so.1: ./CGServer: Undefined symbol > > "pthread_attr_setscope" > > The Solution: > Alfred Perlstein wrote: the symlinks are set properly for you to use > the 3 version of the library (you may want to copy libc_r.so.4 over > libc_r.so.3). > > So, > > chflags noschg libc_r.so.3 > mv libc_r.so.3 libc_r.so.3.bkp > cp libc_r.so.4 libc_r.so.3 > > Voila'! > > Why does this work? > Apparently (remember I'm not a C programmer) CGPro is being linked against > libc_r.so.3 (which on FreeBSD appears to be an older library) as evidenced by: > > archives# ldd CGServer > CGServer: > libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x281c8000) > libc_r.so.3 => /usr/lib/libc_r.so.3 (0x281dd000) > > instead of libc_r.so which symlinks to the latest library - libc_r.so.4. Now > something else must also be going on while making world or compiling the > kernel, because it seems to me that if the library libc_r.so.3 is physically > there it should also be available for use, but apparently not. Ok well basically I think that the libc_r library version got bumped sometime between the setscope stuff was added and your own upgrade, you're correct that the program was explicitly asking for the .3 version, unfortunatly since the new library is .4 it doesn't replace the .3 version (to help maintain binary compatibility), unfortunatly this seems to have caused you a big headache. :( But then again we got it fixed! :) > I'll keep copies of the email I've sent back and forth if anyone wants them, > otherwise, just count me as one very happy camper! > > Thanks to everyone who had suggestions, everyone of them was valuable and > helped point me in the right direction! Thanks for letting us know what finally fixed it, the record in the mailing list archives should prove helpful to others. -Alfred > > Russ Pagenkopf -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 14:50:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by builder.freebsd.org (Postfix) with ESMTP id 0EAD24283 for ; Wed, 9 Feb 2000 14:50:21 -0800 (PST) Received: from bellatlantic.net (client-151-198-135-148.bellatlantic.net [151.198.135.148]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id RAA06948; Wed, 9 Feb 2000 17:49:52 -0500 (EST) Message-ID: <38A1F0D6.470D8CE4@bellatlantic.net> Date: Wed, 09 Feb 2000 17:57:26 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Bill Maniatty Cc: "Christopher R. Bowman" , hackers@FreeBSD.ORG Subject: Re: Books References: <200002091603.LAA90603@cs.rpi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Maniatty wrote: > > Shanley and Anderson: PCI System Architecture (2nd Ed) > > ISBN 1-55860-069-8 small rip in paperback cover > > I teach operating systems, and would like to add a device driver writing > component to the curriculum. I could use this one. There was a good (though somewhat obsolete now) book on the Unix device drivers written by Egan and Texeira (if I got the spelling right - can't check now, left a xerocopy of it back in Russia). I've also seen some book on the Linux drivers, it's more modern but seems to be worse than the first one. I've only looked at it in the book store, so this is only an opinion from a fast look. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 16:59:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fb02.eng00.mindspring.net (fb02.eng00.mindspring.net [207.69.229.20]) by builder.freebsd.org (Postfix) with ESMTP id 2301E4183 for ; Wed, 9 Feb 2000 16:59:07 -0800 (PST) Received: from mindspring.com (user-37kasif.dialup.mindspring.com [207.69.114.79]) by fb02.eng00.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA12467 for ; Wed, 9 Feb 2000 19:48:09 -0500 (EST) Message-ID: <38A209BE.738ED208@mindspring.com> Date: Wed, 09 Feb 2000 19:43:42 -0500 From: Ed Gold X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "hackers@FreeBSD.ORG" Subject: Regarding DOS violations Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After reading the article, http://www.sfgate.com/cgi-bin/article.cgi?file=/chronicle/archive/2000/02/09/MN23532.DTL I am wondering if FreeBSD should take any action to protect our users. I think it would speak incredibly highly of FreeBSD if Yahoo and other "customers" were to have some kind of protection from such an attack. My initial thoughts are: A web server should know its limitations and not attempt to handle more requests than it can manage. It should invoke a service cutoff of any and all users that cause excessive loading over a measured interval of time. Essentially, the machine would have to track all requests, rank them as to how much effort/resources they require, and then "integrate" this data over a fixed time period. If the overall load is higher than an acceptable threshold, the most offensive clients get "ignored" for a fixed period of time. This will, no doubt, ignore a small number of legitimate users; however, that's far better than not serving anyone. Additionally, the server could log this activity which would make it possible to contact the owners/operators of these most offensive systems. With any luck, this could help them realize that their sites are being hacked into and they could take corrective action to prevent future attacks. If we let them know that FreeBSD identified their problem, it might even be an excellent marketing move for us. Comments Anyone? Regards, Ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 17:11:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by builder.freebsd.org (Postfix) with ESMTP id B3DB24259 for ; Wed, 9 Feb 2000 17:11:33 -0800 (PST) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id UAA26126; Wed, 9 Feb 2000 20:11:08 -0500 (EST) (envelope-from efutch@nyct.net) Date: Wed, 9 Feb 2000 20:11:08 -0500 (EST) From: "Eric D. Futch" To: Ed Gold Cc: "hackers@FreeBSD.ORG" Subject: Re: Regarding DOS violations In-Reply-To: <38A209BE.738ED208@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I could imagine this causing problems with people that are behind a proxy server or NAT. Since whatever would be collecting the statistics could easily write off these systems as being offensive. I could safely assume that this would prevent access of sites to a few of our customers who have a large number of machines behind NAT. Which of course means they'd call up complaining because all of the sudden their favorite search engine no longer works. You could easily set you limits high enough to allow this kind of traffic, but you would definately miss a script kiddie or two who thinks he has enough bandwidth to get the job done. -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Wed, 9 Feb 2000, Ed Gold wrote: >After reading the article, >http://www.sfgate.com/cgi-bin/article.cgi?file=/chronicle/archive/2000/02/09/MN23532.DTL > >I am wondering if FreeBSD should take any action to protect our users. >I think it would speak incredibly highly of FreeBSD if Yahoo and other >"customers" were to have some kind of protection from such an attack. My >initial thoughts are: > >A web server should know its limitations and not attempt to handle more >requests than it can manage. It should invoke a service cutoff of any >and all users that cause excessive loading over a measured interval of >time. Essentially, the machine would have to track all requests, rank >them as to how much effort/resources they require, and then >"integrate" this data over a fixed time period. If the overall load is >higher than an acceptable threshold, the most offensive clients get >"ignored" for a fixed period of time. This will, no doubt, ignore a >small number of legitimate users; however, that's far better than not >serving anyone. > >Additionally, the server could log this activity which would make it >possible to contact the owners/operators of these most offensive >systems. With any luck, this could help them realize that their sites >are being hacked into and they could take corrective action to prevent >future attacks. If we let them know that FreeBSD identified their >problem, it might even be an excellent marketing move for us. Comments >Anyone? > >Regards, >Ed > > > > > >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 Feb 9 17:15:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by builder.freebsd.org (Postfix) with ESMTP id 2FC1C41C5 for ; Wed, 9 Feb 2000 17:15:42 -0800 (PST) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA02031; Wed, 9 Feb 2000 17:16:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Ed Gold Cc: "hackers@FreeBSD.ORG" Subject: Re: Regarding DOS violations In-reply-to: Your message of "Wed, 09 Feb 2000 19:43:42 EST." <38A209BE.738ED208@mindspring.com> Date: Wed, 09 Feb 2000 17:16:24 -0800 Message-ID: <2028.950145384@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am wondering if FreeBSD should take any action to protect our users. Considering the type of attack, a convergence DoS which swamped Yahoo's routers, claiming that FreeBSD could somehow "protect" its users from even this most typical type of attack right now would be untrue. In reality, the Yahoo experience showed us that FreeBSD coped about as well as could be expected (in version 3.4) with this and it's really the "internet infrastructure", as it relates to the various ISPs and ASPs involved, which is long-overdue for some attention in this area. Vendors have simply been too busy selling the gold rush, it seems, to realize (or admit) that only two out of every five covered wagons are currently making it through the Donner pass these days. :-) That's not to say that the FreeBSD project isn't looking at adding "hardening" the OS in all the practical ways in which it's possible to do so, but adding request-rate limiting to, say, Apache would probably provide little more than a false sense of security. I'd expect any reasonably well-known shop to have their border routers overwhelmed by smurf and stream attacks long before such rate-limiting had any practical effect. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 17:17:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by builder.freebsd.org (Postfix) with ESMTP id 226BB42DC for ; Wed, 9 Feb 2000 17:17:37 -0800 (PST) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id LAA46406; Thu, 10 Feb 2000 11:46:15 +1030 (CST) (envelope-from newton) Date: Thu, 10 Feb 2000 11:46:14 +1030 From: Mark Newton To: Ed Hall Cc: Wes Peters , freebsd-hackers@FreeBSD.ORG Subject: Re: Eclipse/BSD Message-ID: <20000210114614.D93305@internode.com.au> References: <38A1B807.F3BC660A@softweyr.com> <200002092004.MAA04192@screech.weirdnoise.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200002092004.MAA04192@screech.weirdnoise.com> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 09, 2000 at 12:04:53PM -0800, Ed Hall wrote: > : It doesn't appear, from their licensing page, these changes are ever > : intended to be released to the FreeBSD project. The license is very > : restrictive about redistribution. > > Not only that, but it contains that pernicious gag clause: "You agree not > to release the results of any evaluation of the Licensed Software to any > third party without the prior written approval of Lucent Technologies." > Yuck! Why would I want to test out their software if I can't even > reveal my results to anyone? Those clauses aren't enforcible - Yet. They will be when (if) the Digital Millenium Copyright Act passes. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 17:19:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by builder.freebsd.org (Postfix) with ESMTP id C351F4283 for ; Wed, 9 Feb 2000 17:19:31 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA25569; Thu, 10 Feb 2000 11:48:59 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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: <20000210114614.D93305@internode.com.au> Date: Thu, 10 Feb 2000 11:48:59 +1030 (CST) From: "Daniel O'Connor" To: Mark Newton Subject: Re: Eclipse/BSD Cc: freebsd-hackers@FreeBSD.ORG, Wes Peters , Ed Hall Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Feb-00 Mark Newton wrote: > Those clauses aren't enforcible - Yet. They will be when (if) the > Digital Millenium Copyright Act passes. Has it been proposed yet? (For .au) --- 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 Wed Feb 9 17:36:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by builder.freebsd.org (Postfix) with ESMTP id 182E34290 for ; Wed, 9 Feb 2000 17:36:45 -0800 (PST) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id MAA86043; Thu, 10 Feb 2000 12:05:34 +1030 (CST) (envelope-from newton) Date: Thu, 10 Feb 2000 12:05:34 +1030 From: Mark Newton To: "Daniel O'Connor" Cc: freebsd-hackers@FreeBSD.ORG, Wes Peters , Ed Hall Subject: Re: Eclipse/BSD Message-ID: <20000210120534.F93305@internode.com.au> References: <20000210114614.D93305@internode.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 10, 2000 at 11:48:59AM +1030, Daniel O'Connor wrote: > On 10-Feb-00 Mark Newton wrote: > > Those clauses aren't enforcible - Yet. They will be when (if) the > > Digital Millenium Copyright Act passes. > > Has it been proposed yet? (For .au) Not for .au, no. Give us five years, though... the companies pushing the DMCA have a lot of cash... - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 17:39:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by builder.freebsd.org (Postfix) with ESMTP id BB82040F9 for ; Wed, 9 Feb 2000 17:39:19 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA02134; Thu, 10 Feb 2000 12:08:34 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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: <20000210120534.F93305@internode.com.au> Date: Thu, 10 Feb 2000 12:08:34 +1030 (CST) From: "Daniel O'Connor" To: Mark Newton Subject: Re: Eclipse/BSD Cc: Ed Hall , Wes Peters , freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Feb-00 Mark Newton wrote: > > Has it been proposed yet? (For .au) > Not for .au, no. Give us five years, though... the companies > pushing > the DMCA have a lot of cash... True, as long as I don't have to panic yet :) --- 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 Wed Feb 9 17:50:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hatfield.mail.easynet.net (hatfield.mail.easynet.net [195.40.1.39]) by builder.freebsd.org (Postfix) with SMTP id 64F7442E6 for ; Wed, 9 Feb 2000 17:50:26 -0800 (PST) Received: (qmail 96732 invoked from network); 10 Feb 2000 01:49:55 -0000 Received: from frnk-m227-177.pool.mediaways.net (HELO scully) (62.52.227.177) by hatfield.mail.easynet.net with SMTP; 10 Feb 2000 01:49:55 -0000 Message-ID: <006101bf7368$bd1dc0e0$030000ac@scully> From: "Johnathan Meehan" To: "Ed Gold" , References: <38A209BE.738ED208@mindspring.com> Subject: Re: Regarding DOS violations Date: Thu, 10 Feb 2000 02:47:00 +0100 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.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Ed, Your second point, on the logging is interesting. It would certainly be worth collecting a central repository of IP addresses relating to the machines used to propogate the attacks. The point to remember is that they are victims too, but obviously despite the wide publicity about these activities they have not bothered to take any action to protect themselves therefore hurting everybody else. This problem is becoming too common to allow chances to organisations that even as of yet have taken no corrective action. Perhaps what is really needed is the ability to remove the connection of these servers from the 'net backbone, refusing to reconnect them until they had corrected the problem. But I don't see how that is going to happen. Maybe, rather like ISPs and spammers (or AOL), your logging idea could be used as a first step - given the provided information in a repository, individual organisations could take the option to refuse to accept packets originating from these servers straight away. The owners could /then/ be contacted and informed, to be removed from the list after correcting the problem. If this were a feature, the list would grow quickly enough to at least make the lives of the perpatrators rather more difficult, and the life of the list administrator rather busy. Some tools to automate things as much as possible, and your away, Ed. I don't see why this couldn't be started by, but by no means limited to, FreeBSD users. Then again, perhaps this is too political a move to make? Johnathan Meehan ----- Original Message ----- From: Ed Gold To: Sent: Thursday, February 10, 2000 1:43 AM Subject: Regarding DOS violations > After reading the article, > http://www.sfgate.com/cgi-bin/article.cgi?file=/chronicle/archive/2000/02/09 /MN23532.DTL > > I am wondering if FreeBSD should take any action to protect our users. > I think it would speak incredibly highly of FreeBSD if Yahoo and other > "customers" were to have some kind of protection from such an attack. My > initial thoughts are: > > A web server should know its limitations and not attempt to handle more > requests than it can manage. It should invoke a service cutoff of any > and all users that cause excessive loading over a measured interval of > time. Essentially, the machine would have to track all requests, rank > them as to how much effort/resources they require, and then > "integrate" this data over a fixed time period. If the overall load is > higher than an acceptable threshold, the most offensive clients get > "ignored" for a fixed period of time. This will, no doubt, ignore a > small number of legitimate users; however, that's far better than not > serving anyone. > > Additionally, the server could log this activity which would make it > possible to contact the owners/operators of these most offensive > systems. With any luck, this could help them realize that their sites > are being hacked into and they could take corrective action to prevent > future attacks. If we let them know that FreeBSD identified their > problem, it might even be an excellent marketing move for us. Comments > Anyone? > > Regards, > Ed > > > > > > 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 Feb 9 18: 0:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by builder.freebsd.org (Postfix) with ESMTP id 730F34336 for ; Wed, 9 Feb 2000 18:00:43 -0800 (PST) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <20000210015759.ORKJ5662.mail.rdc3.on.home.com@tristan.net>; Wed, 9 Feb 2000 17:57:59 -0800 Content-Length: 593 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000209192710.A26889@patho.gen.nz> Date: Wed, 09 Feb 2000 20:56:09 -0500 (EST) From: Colin To: Joe Abley Subject: RE: Eclipse/BSD Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Feb-2000 Joe Abley wrote: > This may be old news, but I follow -hackers, -arch and -current and > I hadn't seen it before: > > http://www.bell-labs.com/project/eclipse/release/ > > Would be interested to hear informed opinion as to whether these > changes might find a permanent home in FreeBSD at some point in > the future. As interesting as this looks, unfortunately the license it comes with efffectively precludes incorporating it into FreeBSD. The license is for single-user non-commercial only. They also included derivative works in the restrictions. Cheers, Colin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 9 18:38:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by builder.freebsd.org (Postfix) with ESMTP id DF10D42FC for ; Wed, 9 Feb 2000 18:38:33 -0800 (PST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA67152; Thu, 10 Feb 2000 13:07:56 +1030 (CST) Date: Thu, 10 Feb 2000 13:07:56 +1030 From: Greg Lehey To: Matthew Dillon , Howard Lowndes Cc: hackers@FreeBSD.ORG, Mail List - Oz-ISP Subject: [Oz-ISP] Cracking bigtime in the US? Message-ID: <20000210130755.B67060@freebie.lemis.com> References: <200002092004.MAA67748@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200002092004.MAA67748@apollo.backplane.com> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 10 February 2000 at 7:16:18 +1100, Howard Lowndes wrote: > A report on ABC this morning said that there had been some major cracking > in the US in the last 24 hours. Sites included eBay & Amazon. > > Has anyone any further info? I haven't read this URL, but Matt is usually pretty reliable. Greg On Wednesday, 9 February 2000 at 12:04:52 -0800, Matthew Dillon wrote: > This is the first one I've read that actually gets it right. They > even try to explain the type of border router source-ip filters > necessary to make these attacks traceable. > > -Matt > > http://www.sfgate.com/cgi-bin/article.cgi?file=/chronicle/archive/2000/02/09/MN23532.DTL -- Finger grog@lemis.com for PGP public key 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 Feb 9 18:44:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by builder.freebsd.org (Postfix) with ESMTP id 5783A4365 for ; Wed, 9 Feb 2000 18:44:01 -0800 (PST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA67195; Thu, 10 Feb 2000 13:14:08 +1030 (CST) Date: Thu, 10 Feb 2000 13:14:08 +1030 From: Greg Lehey To: Matthew Dillon Cc: hackers@FreeBSD.ORG Subject: Re: [Oz-ISP] Cracking bigtime in the US? Message-ID: <20000210131408.C67060@freebie.lemis.com> References: <200002092004.MAA67748@apollo.backplane.com> <20000210130755.B67060@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000210130755.B67060@freebie.lemis.com> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 10 February 2000 at 13:07:56 +1030, Greg Lehey wrote: > On Thursday, 10 February 2000 at 7:16:18 +1100, Howard Lowndes wrote: >> A report on ABC this morning said that there had been some major cracking >> in the US in the last 24 hours. Sites included eBay & Amazon. >> >> Has anyone any further info? > > I haven't read this URL, but Matt is usually pretty reliable. Oops, sorry for the spamming. That was intended for Oz-ISP only. Greg -- Finger grog@lemis.com for PGP public key 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 Feb 9 19:26:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by builder.freebsd.org (Postfix) with ESMTP id BEEC24183 for ; Wed, 9 Feb 2000 19:26:09 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id VAA71518; Wed, 9 Feb 2000 21:25:45 -0600 (CST) (envelope-from dan) Date: Wed, 9 Feb 2000 21:25:45 -0600 From: Dan Nelson To: Ed Gold Cc: "hackers@FreeBSD.ORG" Subject: Re: Regarding DOS violations Message-ID: <20000209212545.B69166@dan.emsphone.com> References: <38A209BE.738ED208@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38A209BE.738ED208@mindspring.com>; from "Ed Gold" on Wed Feb 9 19:43:42 GMT 2000 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Feb 09), Ed Gold said: > After reading the article, > http://www.sfgate.com/cgi-bin/article.cgi?file=/chronicle/archive/2000/02/09/MN23532.DTL > > I am wondering if FreeBSD should take any action to protect our > users. I think it would speak incredibly highly of FreeBSD if Yahoo > and other "customers" were to have some kind of protection from such > an attack. My initial thoughts are: > > A web server should know its limitations and not attempt to handle > more requests than it can manage. It should invoke a service cutoff The problem is that for most flood-type DoS attacks, the target machine doesn't see most of the traffic. The idea is to flood the T1/T3/whatever lines, or send enough small packets that the routers are overwhelmed. The smart limiting you describe is good for servers that have relatively few connections that take a lot of CPU each. I'd say that most database-backended servers have a similar problem, and do have per-IP query limits or some other form of restrictions. The best (worst?) example of this I can think of is the all-too-common IIS "HTTP/1.0 Server Too Busy" message. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 4:50:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iaehv.iae.nl (iaehv.IAE.nl [194.151.64.2]) by builder.freebsd.org (Postfix) with ESMTP id C9CC04446 for ; Thu, 10 Feb 2000 04:50:51 -0800 (PST) Received: from fun (fun.IAE.nl [194.151.66.128]) by iaehv.iae.nl (Postfix) with SMTP id 7DA687D33 for ; Thu, 10 Feb 2000 13:50:31 +0100 (CET) Message-ID: <048c01bf73c6$12d522a0$804297c2@iae.nl> From: "Willem Jan Withagen" To: References: Subject: Re: Bad memory suspected Date: Thu, 10 Feb 2000 13:55:14 +0100 Organization: IAE bv. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG SGksDQoNCk5vdGUgdGhhdCB0aGlzIHdhcyBhIEN5cml4IDY4NiBNLTI2NiB3aGljaCBzaG91bGQg aGF2ZSBhIG5hdGl2ZS9yZWFsIGNsb2Nrc3BlZWQgb2YgMjAwTWh6DQoNCkFmdGVyIHRyeWluZyBh bGwga2luZHMgb2YgcGVybXV0YXRpb25zIG9mOg0KICAgIHZvbHRhZ2UgDQogICAgY2xvY2tzcGVl ZCANCiAgICBjYWNoZXMNCiAgICBhbmQgbXVsdGlwbGllciAgDQoNCkl0IGhhcyBiZWNvbWUgY2xl YXI6DQogICAgdGhlIENQVSBkb2Vzbid0IHJlYWxseSBjYXJlIGZvciAyLjkgb3IgMi44IHZvbHQN CkJ1dA0KICAgIGl0IHJlYWxseSBkb2VzIG5vdCBydW4gb24gMyo2Nk1oei4NCg0KU28gSSdtIGp1 c3QgcnVubmluZyBpdCBvbjogMi41ICogNjYuIA0KDQotLVdqVw0KDQotLS0tLSBPb3JzcHJvbmtl bGlqayBiZXJpY2h0IC0tLS0tIA0KVmFuOiBNaWtlIE5vd2xpbiA8bWlrZUBhcmdvcy5vcmc+DQpB YW46IFdpbGxlbSBKYW4gV2l0aGFnZW4gPHdqd0BpYWUubmw+DQpDQzogPGhhY2tlcnNARnJlZUJT RC5PUkc+DQpWZXJ6b25kZW46IHdvZW5zZGFnIDIgZmVicnVhcmkgMjAwMCA4OjExDQpPbmRlcndl cnA6IFJlOiBCYWQgbWVtb3J5IHN1c3BlY3RlZA0KDQoNCj4gPiA+U2luY2UgRnJlZUJTRCBzeXN0 ZW1zIHdpbGwgc3RhcnQgcHVtcGluZyBvdXQgcmFuZG9tIHNpZ25hbCAxMSdzIGluIHRoZSBmYWNl DQo+ID4gPm9mIGJhZCBtZW1vcnksIHRyeSBzZWFyY2hpbmcgdGhlIC1oYXJkd2FyZSBhbmQgLXF1 ZXN0aW9ucyBsaXN0IGZvciB0aGF0LiBJDQo+ID4gPmJlbGlldmUgdGhhdCBzb21lb25lIGFjdHVh bGx5IHdyb3RlIGEgc2lnbmFsIDExIEZBUSwgYnV0IEkgZG9uJ3QgaGF2ZSBhDQo+ID4gPnBvaW50 ZXIuDQo+ID4gDQo+ID4gSSdsbCBnbyBhbmQgc2VlIGlmIEkgY2FuIGZpbmQgc29tZXRoaW5nIGxp a2UgdGhhdC4NCj4gPiANCj4gDQo+IEkgYmVsaWV2ZSB0aGF0IHRoZSBMaW51eCBtaW5pLUhPV1RP IGRvYyBsaWJyYXJ5IGhhcyBvbmUgYXMgd2VsbCAtLSBpdA0KPiBtaWdodCBiZSB3b3J0aCByZWFk aW5nLCBhcyB0aGUgaW5mbyBpbiBpdCBiYXNpY2FsbHkgYXBwbGllcyB0byBGcmVlQlNEIGFzDQo+ IHdlbGwsIG5vdCB0byBtZW50aW9uIGFueSBvdGhlciAiZ29vZCIgT1MuLi4uLg0KPiANCj4gLS1t aWtlDQo+IA0KPiANCj4gDQo+IA0K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 7:35:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id 85BEE449E for ; Thu, 10 Feb 2000 07:35:40 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id HAA25043; Thu, 10 Feb 2000 07:35:19 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id HAA21214; Thu, 10 Feb 2000 07:35:19 -0800 Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id HAA00525; Thu, 10 Feb 2000 07:35:16 -0800 (PST) Message-ID: <38A2DC23.9A4E995@softweyr.com> Date: Thu, 10 Feb 2000 08:41:23 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Len Conrad Cc: freebsd-hackers@freebsd.org Subject: Re: T1 / E1 PCI card for FreeBSD? References: <20000209151455.8E6471F17@bert.kts.org> <4.2.2.20000208185157.00c97100@mail.Go2France.com> <4.2.2.20000209191939.060d58a0@mail.Go2France.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Len Conrad wrote: > > dave@LanMedia.com tells me their P1200 E1 card, with FreeBSD drive, can't > work in channelized mode (like the etinc cards can't). Their LMC150xM > cards can do channelized, but don't have a FreeBSD driver, but their > FreeBSD guy is looking at it. > > Any hacker care to explain how a channelized T1/E1 (24 or 30 separate ip > streams) would be seen within FreeBSD? ifconfig setup? Would we have to > assign 30 fixed ip addresses to these "virtual/channel" ip interfaces? Fixed, DHCP, PPP-assigned, whatever. Individual addresses would certainly be the easiest way to use them, unless you're going to do aggregation at the link layer. Sorry, my knowlege of channelized T1 doesn't extend quite that far down. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 7:54:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by builder.freebsd.org (Postfix) with ESMTP id A94D144D1 for ; Thu, 10 Feb 2000 07:54:49 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id KAA05565; Thu, 10 Feb 2000 10:54:25 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200002101554.KAA05565@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Wes Peters Cc: Len Conrad , freebsd-hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: T1 / E1 PCI card for FreeBSD? References: <20000209151455.8E6471F17@bert.kts.org> <4.2.2.20000208185157.00c97100@mail.Go2France.com> <4.2.2.20000209191939.060d58a0@mail.Go2France.com> <38A2DC23.9A4E995@softweyr.com> In-reply-to: Your message of "Thu, 10 Feb 2000 08:41:23 MST." <38A2DC23.9A4E995@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Feb 2000 10:54:25 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Len Conrad wrote: > > > > dave@LanMedia.com tells me their P1200 E1 card, with FreeBSD drive, can't > > work in channelized mode (like the etinc cards can't). Their LMC150xM > > cards can do channelized, but don't have a FreeBSD driver, but their > > FreeBSD guy is looking at it. > > > > Any hacker care to explain how a channelized T1/E1 (24 or 30 separate ip > > streams) would be seen within FreeBSD? ifconfig setup? Would we have to > > assign 30 fixed ip addresses to these "virtual/channel" ip interfaces? > > Fixed, DHCP, PPP-assigned, whatever. Individual addresses would certainly > be the easiest way to use them, unless you're going to do aggregation at the > link layer. Sorry, my knowlege of channelized T1 doesn't extend quite that > far down. You've got to look at what you're actually getting as a delivered capability. What you actually have is 24 (or 32 in the case of an E1) 64kb/s bearer channels. Some of them might be combined with others to provide Nx64kb/s coherent bearers. Some of them may be dedicated to framing, transport and signalling (e.g., the "D" channel of a 23B+D ISDN PRI T1). That these bearer channels happen to be delivered on a T1 (or E1) entrance facility as the handy carrying case is mostly orthoganal to how you'd treat each individual bearer channel. There might be configuration associated with the T1 (e.g., AMI or B8ZS line encoding), but it's mostly invisible to the bearer channels, other than enclosing them. So you'd probably end up with 24 network interfaces or devices (in the case of a T1), one for each 64kb/s channel, unless you combine them together somehow as Nx64K aggregate. On the other hand, how the hardware abstraction is presented or exposed by the OS might mask this. Consider an ISDN BRI; this is a 2B+D channelized facility, but due to the typical application it's used for, the completely general abstration may not be necessary. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 8:18:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ms1.meiway.com (ms1.meiway.com [212.73.210.73]) by builder.freebsd.org (Postfix) with ESMTP id 9A87E44B3 for ; Thu, 10 Feb 2000 08:18:46 -0800 (PST) Received: from sv [212.73.210.75] by ms1.meiway.com with ESMTP (SMTPD32-5.05) id A55B28004B0; Thu, 10 Feb 2000 17:20:43 +0100 Message-Id: <4.2.2.20000210170826.00b27e40@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 10 Feb 2000 17:17:57 +0100 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: Re: T1 / E1 PCI card for FreeBSD? Cc: "Louis A. Mamakos" In-Reply-To: <200002101554.KAA05565@whizzo.transsys.com> References: <20000209151455.8E6471F17@bert.kts.org> <4.2.2.20000208185157.00c97100@mail.Go2France.com> <4.2.2.20000209191939.060d58a0@mail.Go2France.com> <38A2DC23.9A4E995@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Louie, >You've got to look at what you're actually getting as a delivered capability. What we are looking for is just 30 x 64 kbit incoming ISDN channels for remote access to Internet. "remote access concentrator". >channels. Some of them might be combined with others to provide Nx64kb/s I see the Portmaster 3 can bond channels even across PM3 chassis, but we would not need anything so fancy as that, as least in the first phase. Much more "sellable" to our clients (paying metered access for local time charges for ISDN in Europe) would be hardware STAC compression, ie, Lucent sells a card for the PM3 for hardware-assisted compression, for all 60 channels compressed in a 2 x E1 chassis. Is there a PCI stac-compression card supported by fbsd? If I can get Poul-Henning to give me a "little" (aka euphemism) help and if I can actually find the Siemens/Infineon PRI PCI card his driver works with, I'd like to give this project a go. Thanks, Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 8:38: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by builder.freebsd.org (Postfix) with ESMTP id 7551A44BC for ; Thu, 10 Feb 2000 08:38:00 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id LAA05863; Thu, 10 Feb 2000 11:37:40 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200002101637.LAA05863@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Len Conrad Cc: freebsd-hackers@freebsd.org From: "Louis A. Mamakos" Subject: Re: T1 / E1 PCI card for FreeBSD? References: <20000209151455.8E6471F17@bert.kts.org> <4.2.2.20000208185157.00c97100@mail.Go2France.com> <4.2.2.20000209191939.060d58a0@mail.Go2France.com> <38A2DC23.9A4E995@softweyr.com> <4.2.2.20000210170826.00b27e40@mail.Go2France.com> In-reply-to: Your message of "Thu, 10 Feb 2000 17:17:57 +0100." <4.2.2.20000210170826.00b27e40@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Feb 2000 11:37:40 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi Louie, > > >You've got to look at what you're actually getting as a delivered capability. > > What we are looking for is just 30 x 64 kbit incoming ISDN channels for > remote access to Internet. "remote access concentrator". > > >channels. Some of them might be combined with others to provide Nx64kb/s > > I see the Portmaster 3 can bond channels even across PM3 chassis, but we > would not need anything so fancy as that, as least in the first > phase. This was different from what I had described, which is combining two or more 64kb/s channels into an aggregate channel of higher capacity; essentially a fractional-E1 (or T1). The "bonding" thing you referred to is really PPP multi-link where a packet is segmented, and sent in parallel over multiple links. > Much more "sellable" to our clients (paying metered access for > local time charges for ISDN in Europe) would be hardware STAC compression, > ie, Lucent sells a card for the PM3 for hardware-assisted compression, for > all 60 channels compressed in a 2 x E1 chassis. Is there a PCI > stac-compression card supported by fbsd? I dunno, if it was me, I'd just buy an Ascend/Lucent MAX or TNT box and declare success. I suppose you expose multiple devices, one per channel, like the sr driver does for one channel. But this is something of a different beast since you'll also need to do something about the ISDN signalling. I'm not too familiar with how the isdn4bsd code is structured. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 10:20:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from corpmx3.CORP.HARRIS.COM (corpmx3.corp.harris.com [137.237.103.9]) by builder.freebsd.org (Postfix) with ESMTP id 3459045E7 for ; Thu, 10 Feb 2000 10:20:40 -0800 (PST) Received: by corpmx3 with Internet Mail Service (5.5.2650.21) id <1FVZF2RN>; Thu, 10 Feb 2000 13:20:14 -0500 Message-ID: From: "Potts, Ross" To: Wes Peters Cc: "'freeBSD-hackers@freebsd.org'" Subject: RE: Disposable PCs? Date: Thu, 10 Feb 2000 13:20:11 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some people don't like embedded HTML mail, especially if they aren't using something that uses it, such as Netscape. Cutting and pasting is just as easy. Personally, I like the idea of using links in mail. I just decided to go for the lowest common denominator. -----Original Message----- From: Wes Peters [SMTP:wes@softweyr.com] Sent: Friday, February 04, 2000 5:25 PM To: Potts, Ross Cc: 'Einar Orn Eidsson'; 'freeBSD-hackers@freebsd.org' Subject: Re: Disposable PCs? "Potts, Ross" wrote: > > Okay, here it is. It's dated today(4 Feb 2000). > > www.tomshardware.com/technews/index.html#0619. For the full scoop, see http://www.theregister.co.uk/000203-000022.html If you post complete URLs, *some* of us can just click on them in our mailers. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 12:51: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by builder.freebsd.org (Postfix) with ESMTP id DE2F84611 for ; Thu, 10 Feb 2000 12:51:03 -0800 (PST) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.2) id MAA51286; Thu, 10 Feb 2000 12:49:12 -0800 (PST) From: Archie Cobbs Message-Id: <200002102049.MAA51286@bubba.whistle.com> Subject: Re: IPFW / IP Filter question In-Reply-To: <20000206124959.E319@daemon.ninth-circle.org> from Jeroen Ruigrok/Asmodai at "Feb 6, 2000 12:49:59 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Thu, 10 Feb 2000 12:49:12 -0800 (PST) Cc: lists@security.za.net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai writes: > >I would have thought you would use the tee option in ipfw for this, but > >its not implemented yet according to my man pages, so I was wondering if > >there was another way to do this, cause it makes traffic analysis a hell > >of a lot easier if I can do this rather than having to sniff it with bpf > >or something. > > Didn't CURRENT add the tee option by now? Yes, I added ``ipfw tee'' to current.. however, it's not completely perfect yet but should be usable. FYI, you can combine ``tee'' with ngctl(8) and netgraph's ksocket node type to get a tcpdump-like effect.. eg: $ ipfw add 100 tee 1234 icmp from any to any in icmptype 8 $ ngctl Available commands: [ ... snip ... ] + mkpeer ksocket foo inet/raw/divert + msg foo bind inet/0.0.0.0:1234 Rec'd data packet on hook "foo": 0000: 45 00 00 54 99 f7 00 00 ff 01 e8 be c3 4c cd 07 E..T.........L.. 0010: c3 4c cd 51 08 00 51 7e 4f c8 00 00 a6 23 a3 38 .L.Q..Q~O....#.8 0020: 15 5a 0d 00 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 .Z.............. 0030: 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 ............ !"# 0040: 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 $%&'()*+,-./0123 0050: 34 35 36 37 4567 + Rec'd data packet on hook "foo": 0000: 45 00 00 54 99 fe 00 00 ff 01 e8 b7 c3 4c cd 07 E..T.........L.. 0010: c3 4c cd 51 08 00 a3 a6 50 c8 00 00 a8 23 a3 38 .L.Q....P....#.8 0020: c8 31 05 00 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 .1.............. 0030: 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 ............ !"# 0040: 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 $%&'()*+,-./0123 0050: 34 35 36 37 4567 + quit -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 13: 6:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by builder.freebsd.org (Postfix) with ESMTP id 86889452E for ; Thu, 10 Feb 2000 13:06:10 -0800 (PST) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.2) id NAA51360; Thu, 10 Feb 2000 13:05:20 -0800 (PST) From: Archie Cobbs Message-Id: <200002102105.NAA51360@bubba.whistle.com> Subject: Re: T1 / E1 PCI card for FreeBSD? In-Reply-To: <200002101637.LAA05863@whizzo.transsys.com> from "Louis A. Mamakos" at "Feb 10, 2000 11:37:40 am" To: louie@TransSys.COM (Louis A. Mamakos) Date: Thu, 10 Feb 2000 13:05:20 -0800 (PST) Cc: lconrad@Go2France.com (Len Conrad), freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Louis A. Mamakos writes: > > What we are looking for is just 30 x 64 kbit incoming ISDN channels for > > remote access to Internet. "remote access concentrator". > > > > >channels. Some of them might be combined with others to provide Nx64kb/s > > > > I see the Portmaster 3 can bond channels even across PM3 chassis, but we > > would not need anything so fancy as that, as least in the first > > phase. > > This was different from what I had described, which is combining two > or more 64kb/s channels into an aggregate channel of higher capacity; > essentially a fractional-E1 (or T1). In my (biased) opinion, the right way to handle this is to make the card appear as a netgraph node. You configure it however you want with control messages, then attach netgraph interfaces, etc. Isn't this what Poul did? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 13:45:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by builder.freebsd.org (Postfix) with ESMTP id 91C97451A for ; Thu, 10 Feb 2000 13:45:20 -0800 (PST) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12IzSv-000CKT-00; Thu, 10 Feb 2000 19:41:25 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #1) id 12IzSv-0001NP-00; Thu, 10 Feb 2000 19:41:25 +0000 Date: Thu, 10 Feb 2000 19:41:25 +0000 From: Ben Smithurst To: "Potts, Ross" Cc: Wes Peters , freeBSD-hackers@freebsd.org Subject: Re: Disposable PCs? Message-ID: <20000210194125.H421@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Potts, Ross wrote: > Some people don't like embedded HTML mail, especially if they aren't > using something that uses it, such as Netscape. Cutting and pasting > is just as easy. uh... I think Wes just meant post the complete URL (actually, that's what he said), i.e. stick http:// on the front if it's a Web address. That way, any half-decent software will allow the user to select the URL somehow (in Mutt, ^B does it). -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 14:14:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id 02442458D for ; Thu, 10 Feb 2000 14:14:14 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id OAA04482; Thu, 10 Feb 2000 14:13:24 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id OAA25596; Thu, 10 Feb 2000 14:13:24 -0800 Received: from softweyr.com (dyn5.utah.xylan.com [198.206.184.241]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id OAA21510; Thu, 10 Feb 2000 14:13:22 -0800 (PST) Message-ID: <38A33971.669F5204@softweyr.com> Date: Thu, 10 Feb 2000 15:19:29 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Potts, Ross" Cc: "'freeBSD-hackers@freebsd.org'" Subject: Re: Disposable PCs? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Potts, Ross" wrote: > > Some people don't like embedded HTML mail, especially if they aren't using > something that uses it, such as Netscape. Cutting and pasting is just as easy. > Personally, I like the idea of using links in mail. I just decided to go for > the lowest common denominator. This has nothing to do with HTML mail. If you're clever enough, you can launch a valid URL from xterm. Standards exist for a reason. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 15:19:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.x-treme.gr (mx1.x-treme.gr [212.120.192.10]) by builder.freebsd.org (Postfix) with ESMTP id B99594592 for ; Thu, 10 Feb 2000 15:19:07 -0800 (PST) Received: from hades.hell.gr (pat26.x-treme.gr [212.120.197.218]) by mail.x-treme.gr (8.9.3/8.9.3/IPNG-ADV-ANTISPAM-0.1) with ESMTP id BAA32339; Fri, 11 Feb 2000 01:17:50 +0200 Received: by hades.hell.gr (Postfix, from userid 1001) id 583DE68E04; Thu, 10 Feb 2000 15:51:49 +0200 (EET) Date: Thu, 10 Feb 2000 15:51:49 +0200 From: Giorgos Keramidas To: Colin Cc: Joe Abley , freebsd-hackers@FreeBSD.ORG Subject: Re: Eclipse/BSD Message-ID: <20000210155149.C478@hades.hell.gr> Reply-To: keramida@ceid.upatras.gr References: <20000209192710.A26889@patho.gen.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cwass99@home.com on Wed, Feb 09, 2000 at 08:56:09PM -0500 X-PGP-Fingerprint: 62 45 D1 C9 26 F9 95 06 D6 21 2A C8 8C 16 C0 8E X-Phone-Number: +30-94-6203692, +30-93-2886457 X-Address: Theodorou Kirinaiou 61, 26334 Patra, Greece Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 09, 2000 at 08:56:09PM -0500, Colin wrote: > > As interesting as this looks, unfortunately the license it comes with > efffectively precludes incorporating it into FreeBSD. The license is > for single-user non-commercial only. They also included derivative > works in the restrictions. So much for Stallman's efforts to be the meanest man on earth when it comes to "derivatives". They sure have beat him here :/ -- Giorgos Keramidas, < keramida @ ceid . upatras . gr > For my public PGP key: finger keramida@diogenis.ceid.upatras.gr PGP fingerprint, phone and address in the headers of this message. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 15:57:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by builder.freebsd.org (Postfix) with ESMTP id 5975945ED for ; Thu, 10 Feb 2000 15:57:04 -0800 (PST) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id JAA60668; Fri, 11 Feb 2000 09:49:11 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <200002102349.JAA60668@mail.theinternet.com.au> Subject: Re: Eclipse/BSD In-Reply-To: <20000210155149.C478@hades.hell.gr> from Giorgos Keramidas at "Feb 10, 2000 03:51:49 pm" To: keramida@ceid.upatras.gr Date: Fri, 11 Feb 2000 09:49:11 +1000 (EST) Cc: Colin , Joe Abley , freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG +----[ Giorgos Keramidas ]--------------------------------------------- | On Wed, Feb 09, 2000 at 08:56:09PM -0500, Colin wrote: | > | > As interesting as this looks, unfortunately the license it comes with | > efffectively precludes incorporating it into FreeBSD. The license is | > for single-user non-commercial only. They also included derivative | > works in the restrictions. | | So much for Stallman's efforts to be the meanest man on earth when it | comes to "derivatives". They sure have beat him here :/ I don't think that that is an entirely fair analysis. They are afterall a business, and business units need to justify their existence. If it goes the normal way Lucent goes, Eclipse as a unit (license, staff etc) will be sold off to the highest bidder at some point down the track. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 18:21:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by builder.freebsd.org (Postfix) with ESMTP id 396E54538 for ; Thu, 10 Feb 2000 18:21:28 -0800 (PST) Received: from localhost (dc2-isdn2179.dial.xs4all.nl [194.109.156.131]) by smtp1.xs4all.nl (8.9.3/8.9.3) with SMTP id CAA15634; Fri, 11 Feb 2000 02:07:14 +0100 (CET) Message-ID: <38A36094.794BDF32@xs4all.nl> Date: Fri, 11 Feb 2000 01:06:28 +0000 From: "W.H.Scholten" Organization: Robots anonymous X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.3-RELEASE i386) MIME-Version: 1.0 To: tech@openbsd.org Cc: hackers@freebsd.org Subject: ls: alpha - numeric sorting Content-Type: multipart/mixed; boundary="------------1CFBAE3959E2B60015FB7483" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------1CFBAE3959E2B60015FB7483 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit L.S. Here are patches for FreeBSD's ls (from version 3.3 release) and OpenBSD's ls (version 2.6, didn't actually test this obsd patch as I'm working on a FreeBSD machine at the moment). What it does is add an option (yes another one) to sort alpha & numeric separately, i.e. instead of something like gsi-0.9.3p1.tgz gsi-0.9.3p10.tgz gsi-0.9.3p11.tgz gsi-0.9.3p12.tgz gsi-0.9.3p13.tgz gsi-0.9.3p14.tgz gsi-0.9.3p15.tgz gsi-0.9.3p16.tgz gsi-0.9.3p17.tgz gsi-0.9.3p18.tgz gsi-0.9.3p2.tgz gsi-0.9.3p3.tgz gsi-0.9.3p4.tgz gsi-0.9.3p5.tgz gsi-0.9.3p6.tgz gsi-0.9.3p7.tgz gsi-0.9.3p8.tgz gsi-0.9.3p9.tgz you will get: gsi-0.9.3p1.tgz gsi-0.9.3p2.tgz gsi-0.9.3p3.tgz gsi-0.9.3p4.tgz gsi-0.9.3p5.tgz gsi-0.9.3p6.tgz gsi-0.9.3p7.tgz gsi-0.9.3p8.tgz gsi-0.9.3p9.tgz gsi-0.9.3p10.tgz gsi-0.9.3p11.tgz gsi-0.9.3p12.tgz gsi-0.9.3p13.tgz gsi-0.9.3p14.tgz gsi-0.9.3p15.tgz gsi-0.9.3p16.tgz gsi-0.9.3p17.tgz gsi-0.9.3p18.tgz Much better! This would be great on ftp servers (trying to find the latest tgz for a given package in a list of around 50 or more is a nuisance with lexicographical ordering). The sort option is invoked with -n on fbsd, -N on obsd (change as you like...). I've also attached a complete little test program with debug output etc. The code could be improved by renaming some variables to longer names (couldn't think of any good ones ;) and probably the implementation too (haven't tried to optimize). Enjoy, Wouter --------------1CFBAE3959E2B60015FB7483 Content-Type: application/x-gzip; name="alpha_num_cmp.c.gz" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="alpha_num_cmp.c.gz" H4sICHhZozgAA2FscGhhX251bV9jbXAuYwCVV39T20gS/dv+FH3ZymFj4Qizu3fBkC1hC1CV kTlJDkuxFCvJMtZGP3ySHI69zXe/1zMj22AgdVQqmpnued39prtn/GGXBvnisYjv5xW1Bm3q 6bpOV93zrhvO86SKsmaTiJxoGpdVEQfLKs4z8rMpLcuI4ozKfFmEkVgJ4swvHmmWF2mp0UNc zSkveDcP82VFaT6NZ3HoM4ZGfhHRIirSuKqiKS2K/Gs8xaCa+xX+i4CTJPlDnN0zRJhn05j3 lWJfGlWHvLzffeZaSfms9inMp9BclhUVUeXDV0b1g/wri1TMDIK/LK/iMNKgEZeUAI9hNm1m 06c+EYyGiR+nUdFljN62IzC4wUjtCOKcLuHcyhflwcqj/98XhbD2iFSs0zxcplFW+fWhfcgL yiEpKPWrqIj9pFwRr1DEsYnNG8FwiCz3zi2X3PGpd2U4JmF86Yw/W0NzSCfXEJpkTLzzsUOG PaTB2PYc62TijR2Xfv/dcBnAcnd2hNSwr8n89dIxXZewwbq4HFmAAa5j2J5luhpZ9mA0GVr2 mUZAIXvsMcLIurA8aHpjTVjc3knjU7owncE5psaJNbK8a2Hy1PJsmGOQU/aRLg3HswaTkeHQ 5cS5HLvwH2ENLXcwMqwLc9iFwzYMk/nZtD1yz43RiI0yhIoU/54EemLCQ+NkZEobiHJoOebA 43DUSPBgD0Ab/Btp5F6aA4sH5q8mgjGca03Buua/JlCCkIbGhXFmCudb28Q8YQVnMpg45gW7 DCrcyYnrWd7EM+lsPB4KCMC7pvPZGphun0ZjV3A2cU0NdjxDmAcKCIMY45OJa9XUWbZnOs7k 0rPGdpvOx1fgBs4a2D0UNI9tETZoGjvXjMt8iFMQkV+dmxA5TKwgzmBuXBA48DY02Sr49DaC 5c22eTayzkx7YLLCmIGuLNds49wsuHjGqGz8yoDliQifcwS+YbiVwJo4V7JOyRh+tth/pY9U cC2VOYLBwbk6gG5z90Oz+UOchckSzeWorKZx3p1/ajbjrKKHeXnnJ4u5f5ct0zBdtMK5X9Cu r5EcBO2+VEzRjVo88Iv7UEp3dzH+2qb/NhssoBiqP0yjWZxFZE8u7pgi+8xFy/vYbEi48uag d3vTu6Vj3tV4V0VlpffeaSRHOo9fXD/YWD94Wd+vl4P1GlpNvbq/Xt3v/rFYrfty8rJMf01o ut7+KzIPMsT9hviZSO9t2uw9Fb4t09cS/ZU9B8/2+G8JN2X7+pvC57zp3xH7T+VBLf+GrGnM FgVSaNZCckZFAaVBni78Ii5xe+Dapa9+skTuko5r1MeFkkSzisr4T9znJZWpnyS4IHANZyQv pBLXw2/ZOyRvAzcZteJjvU/x0UZWYtrpiNx9yzi9700P6X1JR8ef+PMLQDWKNSpv4tsb/VYN 9m/Z0jaQE5XLpDqk+m8DiPg7/S0TgM/RtHVdqrKsNWpzbO8biMMzYVlkpPebmK2qL0Wt+lrQ plbLb4O2Foa/EI8PedxuNj/skoCnPYIF3KshniAF14t4pFjoDHnxBTd3qS7t8pDuI/nKSfLs HmeoAMAUnmHHfvaI2x+vDLwF+Orn14u66HXqduljm2ZFnlKAy5z4ms7ucbKhYFo8LcqoS9aM on8v/eSJoHbQTxiMzZXyxSUdo6h736UeotzXNeKWcFQPOGF6GgWPwuBiwe4lkT9Vfv0ZFTn7 MI/CLyySXkEju6/mnHZ4tYBOJNcj3iXIwiT6Txzm94W/mLM7yknOE4aLZzKMGkC8+kQ4XTxG uAkjOZpbDRetNmjX/RGT3aDfVB01wTTBVExC7sn1JMMkC7hyxCx6uGOx+Abym6m51BJF0O/L fBdo6YLXG4mPVozA4TPSg5M4CdYrovs3GqFSCssF5xW90/d7Bz/+9PM//vlRlFgjDDYUgi2F l0pjjxDe8fspRyg+oZyFPBNFIaPXVODCDihuwZm/HWOB/voLIvp0DEUxDsQ4kDE2EKD0KatJ 1kRZKDQBJ/HSBbbQqiBEPvOLXOaoOEX8BphFBZ6lfIzYtx1Oq9feMAZb76dtEcWWzbpkxQlg ylXcaMC8m2ubLsSlSP7ST/GwxpuW84tj5KCFQGarXxdbyTBUR/GAF3NEwUpYF1HZpwcGfeSF ICrKT1K/RH4fBYcqvu3wDtpsfI9EKqgDUgsyrDoqucZLIrCXjkFtWZP/ikl/m9I6NwSj2PvE tCRUmAWdyCc48/cNSuVZ1qSyLuiy0UHAyNzHTyxUeJ5/IfVjThEk2sBGO0q7kqRMFYWoiU74 UllkwVol6IQvFgY8daKUf+CpzkT6TqksiDIGRCb4lFWOqaT3YR4nEXo63aj6J7yqjmlH3+F0 Vnv39vq1tNPpk+BGdgWGDVawPBXNpYYNathgGzZYwwZrWD5OZRX1KRVfPdsf2ysPaeWPOlsp 2FMImyf8bMvqtF9qLn5Hxn38Hp08kJNATPgs0dzqVGrVmm2Ma8V27YZqgE+y+Ptbvp/cP23k tgLTaqQVkHrBbGe4Ylsy/TrLP4NlpUOtPOMsLynNi3Wu8RW4U24ZkiS/TTB3ljhbRocom45o 3YH4ol6iB8n6nRypiu1kog12skCQLhYkgWKxLanmBF9J2QHOjJWOePV8a/4PLjpZjQMSAAA= --------------1CFBAE3959E2B60015FB7483 Content-Type: application/x-gzip; name="whs_fbsd_ls.diff.gz" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="whs_fbsd_ls.diff.gz" H4sICPRcozgAA3doc19mYnNkX2xzLmRpZmYArVhpc9poEv4Mv6LHMzU24TDg+MJxJjLItrYw sEjE49ra8kjiBVQREiOJOJ6d/Pd9uiVxGE/VJLupFHqPPp4+1fLYm0yoGi175Me1MPKmh+58 UXOxSxfFarW6fVUwlwFpyyk1z6lx0mo0W29PqHF+fl4sl8srvsJdGNC1cohOqV5vHZ+0jo+p Wa/Xix8+UPW4WTmhMn6bTfrwoUg/eoHrL8eK9qBqtrd5oL4kKgrksFheHz/N4kdRtFcsF8te kBTLtr+Y2Y/Bco7zA7tCTqlYLrhhECd0bZl6z6I3OH3jXBTL/8FNpJJlFNABS9pmrb6fJPFj YM8VhKw3pRI4v67URerz/0ujs6nRfkUjsUbio7Umel3TeCeguQc5Nvl6K6z54SuRPd2K7Irw RXBPW0eNdXCP3nJw8XsusaU39NN1pNSV2WlRHLmHjhccbgirfKZG7aTWrDVE12H97JD1v830 LxTISP+yoJ9Y1iGnAbxRoE0P0uPj4OBg2x8V2t6LM4XzReT+NrOEAYpd9xu4aKXyO9jm4fgb eHZDj6eUMj+3Qs4Hr4T7bCvcQvQi1Oeto6N1qBv1BseaH2cSbKCmyWPyvFAXhULh8A3Z4zHx ltyZHdkux3ISRhSEQTVS06VvY+/5KpbIptxPMy9R4TLJJMSz8InyM1JBEnkZuYQTDHEYJeuC uhAmHKUZQj8TDlXkuRSrBTAkyn9m9jScFCEX4O60xMSmo9PKKWw6OseDbSoUJo++FyfjMKFL aghxgUs0XCQegoBDROFxcPtgGm2te1GsFgDXV4SYzXA5VQkoD+xo6qK6o+nnCu01tKv29W13 MLTubccdT6beJz/8PYqT5V6pRD9cAkaJuGd8l6TgFVEwI37yEsiBrOzg8A3/okCtmQJZhapt soMxVX3KbbN9rD+rKPLQdZUN9jCZIYhxiMAo3xeXNZt1ToNms5nVfKHg2rGi/Wi/xRs4EAWg olhJXFIn4tiJlP0JhZWTByAvC/l2SFOO8ppjpSBeKYi9P9SOZAF3yoEsN8/yhgQCZIipfOUi R9JUmSwDlw2uSWIVvAkdbGFmh1ULcv4D8tubp6eMKaXdBiwXBT6buAFQveg4YovyYcCOQHrJ lzV9MWvFMnlEN1FxzHyv8KStJjP/7EzMPz9exUbEwAUjPNBhvInn2mw8sbjMAy8kpo2IQXwl Yf+f3PFdvvhmR+Re2G2Lq+GBu9xqs9UgV6cFa7akf9gBUYPqjRZ6YL2OLnlaz7vkmvI68qRV NoTy6Kz19nzdKuuVOppKBa2So1CG+9vh4hmqZgkdtEtCSPe125rpzkI/UQEPGkQ0VGP0nshz lhIiLs8lGx8gcZeRq+QEr1Q7eubOOo8rhDJHmUbCzmvum5tx5t6h8GKN5l6SqDEtovAzyhuN emYn+FEQ5PvhkxdMRQbeNGMvawdgnKukJeeN2gt0MYWTHJYbomHMl3hFYeyxAZfl2g56Ca4y w0UK/gVh4rkYfZKZFxO3WpazqTUYb8MiaHV9G0GPaiKkuQsFKjfckkOBreMl4K3Q5BhWoL4d TS5iDYoye8ehi3dPkNh57A7x7ksb6Bwvosiz/Xjl/lyMhE+4N+wRM4XCujVMMvvX1r021Anr wbD/0ejoHbp6wKVO2si67Q9J63Wo3e9ZQ+NqZPWHJv32m2aKBMPc35drrfdA+q+DoW6aBA7j btA1IAeCh1rPMnSzQkav3R11jN5NhSCGen1LRHSNO8MCqdWviM5dVupf050+bN9iq10ZXcN6 EJ3XhtWDPpFyzTBpoA0toz3qakMajIaDvgkTYFnHMNtdzbjTOzVA7kE16R951jFvtW6XtYqM zFr83zL2SgdG7aqrp0pgaMcY6m2LLcpWqS96bfgOELsVMgd62+CF/qsOe7ThQyWTa+r/HIEI l9TR7rQbPcV/sOudLc8gMu3RUL9j1HCHOboyLcMaWTrd9PudVAYUmPrwo9HWzQvq9k1x3MjU K9BkaQIAYuA1XGN9NTKNlf+MnqUPh6OBZfR7Jbrt38NBwKuBvSPO7vfEdPiqP3xgwewTiUVq /f2tjrshu1e8p7GDTHixbW2Qsl441dqwV7h7+k3XuNF7bZ0p+izp3jD1EsJnAOUNi2X19xp0 j8QFnCtAh+VuLlckvmRck9b5aLAJGQNSwjSyFBI3tm+zMKAqZJIr/zhWEy9Aw/ECfB45JUxM done0QGWvxCvW7wuMS1PpTIZVteTIV4aKOS0rRkJPYXRJxR6nNV43OLRS2rSD4OpivPZEvMk uvelHTyjWaAtoXVwp+B+l/eFOtVqdF6iSRTOyUHtExd1MI15gp8vuKFCboz3rjEh9fvS9rcu coi2L9JYYZz26RQaqdq0Rk2Y2qhXMKHXm+/yBc7qTXwqPovGxYIB+soe58j+UFHIKGbK/cR3 KS6QBNNkhgvuc3AqJsBnNDJMSr764rnhNLIXMwaUwfTiMBB5eB+LJbkEeVmIRTXuXmmg5NN5 95M7/3bGR8L2NzOP6D4OfD6QnYudu9oF2AW8y/fq6ZEp5OmkzyDb53T8AXJwcZEO2KlMmUN4 59uYHOAJ2ICskeHEd9ZHTimjczM6N15wxtFevdE8ent8cnp2vpeyuc4GhbNLkQ9LkIQhHdR/ /gnb6P0l7JW1I2sng1ngD0ERGOQeq0i6p/4opUpTifMFmGiV55Kl/GZOE0/iwkORivBqkriA Mf/rRD6SFb6mEGVWDiuborxYMjNO/0CC4QJKGS3Dl4s0key8FGKRQzmcJ7z+FDmr2zzF4wt6 YqnPfOBg8n6f0uNTw37ntHKgOU4H9evagjWD+pqH3CyIa79sCcmMzQTAVNe+hOSfN8xN/ZUb LOQwpccfpYpmNuYZVEYYfqJsdsrAS/lsFPK8lhkQZJkjiVN2X82dwFnTOGX3L7IHcIdqzhNV VtZU349zLZL3MjZf5HvJ2cxl2XelTf/KSob+TZeXtF/f59TJuKvVi/y2XL6gzEtpKbFoZy2a 92lV5qKdXLSzK9pZi3Y2RXOUMt2oiZT0RchyaOuK/ov4w7hyCr5UAZp07ZTylvA30yLDlOLZ wSI4tjCwiyWs5VwFe0aCWA6kezDl1+J/AWjfqgx4FQAA --------------1CFBAE3959E2B60015FB7483 Content-Type: application/x-gzip; name="whs_obsd_ls.diff.gz" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="whs_obsd_ls.diff.gz" H4sICPpcozgAA3doc19vYnNkX2xzLmRpZmYArVhpc9pYFv0Mv+KOu6oNFmAWx44hTlsG2dYU Bo8k4vZMTdGSeIDKQiKSiOPuzn+fc58kFpOeSVKTStlvucu567vyxJtOqRqtBuTHtTDyZsfu YllzsUsXxWq1untVuI48+rsdELWocdpunbbrZ9Q4Pz8rKoqy5pNU18KhRoPqjfZJvd1oUbNe rxcvL6n65qRySgp+Npt0eVmkn7zA9VcTQQdQNT/YPhCfExEF8rCobI6f5/FYKjooKkXFC5Ki YvvLuT0OVgucl+wKOeWiUnDDIE7o2jK1gUVHOD1yOkXlD9xEIllFAbGgNedYslbfT5N4HNgL ASGbTRmMX9baIvHp/6XQ2VZo7yskVkh8slFEX1c02Qtn7j+OTL7eCWp+WDDthO7sF6IGwtl+ c9I+kXE9z+O6JnwV2lb75O0mtK1TDi1+nsvI0lHhsvRTec37ttag0pWInoQvXsr05rjVOD5v Md0xBxiWEm37lcbj+1Jp19YK7e7L7CjJ+Soo38wsXVwg23W/gyvlYZU/wLYIJ9/Bsx9W/JZF yr93wskH/zOUkuhVGM/ajdNNGBv1c44j/zqTgWT/TsfJy1J0CoXC8RHZkwnxlty5Hdku4kvT MKIgDKqRmK18G3vPF7GM7IZ74kX/XQAIhJvAlh3W57mXiHCVZLzxPHym/IxEkOTkSkoeh1Gy qbKOZMFRmlr0M+FQRJ5LsVhCdyL8lzQBpbYISYQ4pX5osQOUxkk980OhMB37XpxMwoQuqMF0 VOCKDZeJh8DhEJEb398+mnpX7XeK1QJw+oIQ5zkuZyIBZcmOZi6KPZp9qtBBQ+1e9w3TerDd yXTmPfmLIFx+jOJk9fmgXKa/XQBHmbiHfJuowTfIgiHxs5dAEIRlB8dH/JOOyJoLkFWo2iU7 mFDVx3KRLj9Tbqjt+xR+ElHkoSEL251LhzWbLU6cZvMk6wCFgmvHgg4/HrZ5A/chRZYROzr1 H86cSNhPqMOcdgBaRdLuBjLlUDYca+nRWjoKUkSxkOF+rUACfNvkiDbfnlYa9RShN6XSDuMr B/HRE7erP9YKrx7HA/VOayO8oMP91A2gDjKyPp3CTCXvGlGWN7tM210r5RR+LL5CuJZO+04A JlP/p5Y6Yocr9n5PuaQDzmVKt+obB3whVvejRn+/xd9m7g/YujZ0v2OuJwZugOvNTu9cnxas +SqdcWRvrNfxHw30rJ430A3lbhdtnbdPmpsuWq/U0Tvg5gb7WUEX6obLF6iaJ1TqliUhPdRu a6Y7D/1EBDxeEJGBNhmjpzkrLjVZeCsY7QXoYqvIFfLE8QI7euGeuYgrhKjNKYwkO6+5L+KR 8aaea7MQ7hCCliJaeEkiJrSMwk8oXLTgOR6LBAU/DX0/fPaCmZSBR2jiZYUOxoVI2vK8UXuF LqZwmsNyQ7SCxQqvF4YdG3BZru2gS+AqM1xKwb8gTDwXA08y92LijspytrUGk11YeBli17c9 dO6aFNLchwKVW27JocDWyQrw1mhyDGtQ348mF7EBRZm9k9DF6xIkdh67Y7xqIW4iWuCpiTzb j9fuz8XI8EnuLXukmZLCutVNMofX1oNqaIT1vTH8oPe0HgoBlxqpI+t2aJA66FF3OLAM/Wpk DQ2TfvtNNaUE3Tw8lNfq4JG0X+8NzTQJHPrdfV+HHAg21IGla2aF9EG3P+rpg5sKQQwNhpYU 0dfvdAuk1rAide6z0vCa7jSje4uteqX3detR6rzWrQH0SSnXDJPuVcPSu6O+atD9yLgfmjAB lvV0s9tX9TutVwPkAVST9oHHIPNW7fdZq5SRWYv/O8ZeacCoXvW1VAkM7emG1rXYomyV+mLQ he8AsV8h817r6rzQftVgj2o8VjK5pvaPEYhwST31Tr3RUvylfe/seAaR6Y4M7Y5Rwx3m6Mq0 dGtkaXQzHPZSGVBgasYHvauZHeoPTem4kalVoMlSJQCIgddwjfXVyNTX/tMHlmYYo3tLHw7K dDt8gIOAVwV7Tzp7OJCmw1dD45EFs09kLFLrH2413BnsXuk9lR1kwotda4uU9cKp1pa9knug 3fT1G23Q1ZhiyJIedFMrI3w6UN6wWFb/oEL3SLqAcwXosNzP5YqML+nXpPY+6GxCxoCUMPUs haQbu7dZGFAVPOjha3Aipl6AhuMF+CpyypiL7DK9oxKWvxCv27wuMy3Pm3L2q25mP7waKOS0 rekJPYfREwo9zmo8bvOAJWvSD4OZiPPpERMjuveFHbygWaAtoXVwp+B+l/eFOtVqdF6maRQu yEHtExd1MIt5uF8suaFCbixqpE9JfFzZ/s5FDtH2pTRWGKd9OoVGojarUROmNuoVwhvSfJcv cFZv4gvxRWpcLhmgL+xJjux3EYWMYi7cJ75LcYEkmCVzXHCfg1Mx272gkZGNm8+eG84iezln QBlMLw4DKQ/PvbQklyAfC2lRjbtXGij5wbzz3bvzxYzxf/dLmWdDHwc+H8idi5273gXYBbzL 9+J5zBTyt5P+DrJ9TsefFqVOJx2jU5ly9uCdb/PokESwAVkjBxLf2Rw55YzOzejceMkZRwf1 RrN18ub07O35QcrmOlsUzj6F1I0JCZIwiYP6zz9hG72/gL1y7ci1k8Es8DeiFBjkHqvIdE/9 US5vZi7cg4nWeS6zlF/mNPFkXHgoEhGeJhkXHrayv0msx7AvKUT+XjLDyrYoL5aZGad/FcFw AaWMluHLizSR7LwUYimHcjjPeP4EOevbPMXjDj2z1Bc+cDB/v0/pY+TeO6edA81xOqhf15ZY M6hf85CbBXHjlx0hmbGZAJjq2heQ/POWuam/coMlOUwZ8EenoLmNeQaVEYZPlM1OGXhZPluF vKhlBgRZ5sjEUdyv5k7gbGgcxf2L7AFcQyx4osrKmuqHca5F5r2cnDv5XuZs5rLs69Gmf2Ul Q/+miws6rB9y6mTc1Wonv1WUDmVeSkuJRTsb0bxPqzIX7eSinX3Rzka0sy2ao5TpRk2kpK9C lkPbVPRfxB/GKSn4cgVo0rVTzlvCN6ZFhinFs4dF4tjBwC6WYVVyFewZGUQlkN2DKb8U/wOn f/ENbRUAAA== --------------1CFBAE3959E2B60015FB7483-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 18:28:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.dyndns.org (adsl-208-191-146-189.dsl.hstntx.swbell.net [208.191.146.189]) by builder.freebsd.org (Postfix) with ESMTP id 2A0714642 for ; Thu, 10 Feb 2000 18:28:30 -0800 (PST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id UAA84945; Thu, 10 Feb 2000 20:27:39 -0600 (CST) (envelope-from chris) Date: Thu, 10 Feb 2000 20:27:38 -0600 From: Chris Costello To: "W.H.Scholten" Cc: tech@openbsd.org, hackers@FreeBSD.ORG Subject: Re: ls: alpha - numeric sorting Message-ID: <20000210202738.J67477@holly.calldei.com> Reply-To: chris@calldei.com References: <38A36094.794BDF32@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i In-Reply-To: <38A36094.794BDF32@xs4all.nl> X-URL: http://www.FreeBSD.org/~chris/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, February 11, 2000, W.H.Scholten wrote: > I've also attached a complete little test program with debug output etc. > The code could be improved by renaming some variables to longer names > (couldn't think of any good ones ;) and probably the implementation too > (haven't tried to optimize). FreeBSD already supports an `-n' option, so you probably don't want to go with that. Probably if it does go in, both systems should use -N or something else unused, if only for consistancy amongst the two. -- |Chris Costello |Host System Not Responding, Probably Down. Do you want to wait? (Y/N) `----------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 20: 6:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by builder.freebsd.org (Postfix) with ESMTP id 580AE44F5 for ; Thu, 10 Feb 2000 20:06:19 -0800 (PST) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA07657 for ; Thu, 10 Feb 2000 20:06:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: hackers@freebsd.org Subject: My views on Eclipse/BSD Date: Thu, 10 Feb 2000 20:06:01 -0800 Message-ID: <7654.950241961@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since everyone seems to be jumping up and down on this, I thought I'd just chime in with my two cents on the matter. I saw the Lucent folks behind this when they first brought a demo of Eclipse to FreeBSDCon '99 and, frankly, I was just pleased that they were willing to show up as exhibitors and to show it off at all. Now we see it more widely available under a license which allows us to play with it but not to sell it. Where's the harm in that? We can all still benefit from the experience of examining yet another type of approach in dealing with Quality Of Service issues. The truly interested can also use it as a springboard for looking past Eclipse and into the future of QoS systems, hopefully to then begin implementing something in the open source space which takes us to an even greater level of technical sophistication in FreeBSD's QoS infrastructure. None of that requires Lucent to be any more "open" than they currently are with the licensing of Eclipse and we really ought to be thanking them right now (instead of whining) for allowing us to take such an open and thorough look at their design strategies. It took a lot longer than for Plan9 to escape from Lucent and we should, if anything, be marvelling at the speed at which this has taken place at all. :-) I'd also venture to say that if such a next-generation QoS movement springs up as a result of what people see in Eclipse, it won't be long before these very same folks at Lucent are among the loudest voices of all, screaming for a truly OSS license and the ability to work cooperatively on Eclipse's follow-up act. By the very nature of software engineering Eclipse is already obsolete, and what we can learn from it going forward interests me a lot more than its license at the moment. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 21:22:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id 8D4AF4282 for ; Thu, 10 Feb 2000 21:22:17 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id VAA10218; Thu, 10 Feb 2000 21:18:57 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id VAA21556; Thu, 10 Feb 2000 21:18:56 -0800 Received: from softweyr.com (dyn5.utah.xylan.com [198.206.184.241]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id VAA12139; Thu, 10 Feb 2000 21:18:55 -0800 (PST) Message-ID: <38A39D2F.F367E3DA@softweyr.com> Date: Thu, 10 Feb 2000 22:25:03 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: hackers@freebsd.org Subject: Re: My views on Eclipse/BSD References: <7654.950241961@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > Since everyone seems to be jumping up and down on this, I thought I'd > just chime in with my two cents on the matter. > > None of that requires Lucent to be any more "open" than they currently > are with the licensing of Eclipse and we really ought to be thanking > them right now (instead of whining) for allowing us to take such an > open and thorough look at their design strategies. Thank you for an excellent summation, Jordan. More to the point, our license not only allows this but actively encourages it. If you're upset by this, perhaps some introspection is required. You may find that your gut-level reaction of "Hey, they took something and aren't giving back" is followed up by "Yeah, that's kind of the point," in which case you GET it. If not, you may be in the wrong project, we're thankful for your help so far, and wish you well. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 10 22:28:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from manor.msen.com (manor.msen.com [148.59.4.13]) by builder.freebsd.org (Postfix) with ESMTP id 18B1545FA for ; Thu, 10 Feb 2000 22:28:11 -0800 (PST) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.8.8/8.8.8) with ESMTP id BAA13412 for ; Fri, 11 Feb 2000 01:25:55 -0500 (EST) (envelope-from wayne@manor.msen.com) Message-Id: <200002110625.BAA13412@manor.msen.com> To: hackers@FreeBSD.ORG Subject: Servers with large amounts of RAM? From: "Michael R. Wayne" Date: Fri, 11 Feb 2000 01:25:54 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a good reference URL for configuring FreeBSD with large amounts of RAM? I seem to remember there being "issues" with over 1GB but I don't remember the details and the search engine on www.freebsd.org is currently down. /\/\ \/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 0:11:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by builder.freebsd.org (Postfix) with ESMTP id D17A446B8 for ; Fri, 11 Feb 2000 00:11:17 -0800 (PST) Received: from mailstore.ppp.net (pop3.ppp.net [212.18.80.90]) by mail.ppp.net (8.8.8/8.8.8) with ESMTP id JAA15137; Fri, 11 Feb 2000 09:10:58 +0100 Received: (from uucp@localhost) by mailstore.ppp.net (8.9.3/8.9.3/Debian/GNU) with UUCP id JAA30588; Fri, 11 Feb 2000 09:02:12 +0100 Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 34EC552D26; Fri, 11 Feb 2000 07:34:27 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id 42B061F17; Fri, 11 Feb 2000 07:34:19 +0100 (CET) Subject: Re: T1 / E1 PCI card for FreeBSD? In-Reply-To: <200002102105.NAA51360@bubba.whistle.com> from Archie Cobbs at "Feb 10, 2000 1: 5:20 pm" To: archie@whistle.com (Archie Cobbs) Date: Fri, 11 Feb 2000 07:34:19 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000211063419.42B061F17@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs wrote: > In my (biased) opinion, the right way to handle this is to make > the card appear as a netgraph node. You configure it however > you want with control messages, then attach netgraph interfaces, etc. > > Isn't this what Poul did? Yes. It looks like that. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 1:49:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by builder.freebsd.org (Postfix) with ESMTP id 0072646AA for ; Fri, 11 Feb 2000 01:49:24 -0800 (PST) Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by nets5.rz.rwth-aachen.de (8.9.1a/8.9.1/10) with ESMTP id KAA23737 for ; Fri, 11 Feb 2000 10:49:12 +0100 (MET) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id KAA15163 for ; Fri, 11 Feb 2000 10:49:45 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.3/8.6.9) id KAA14176 for hackers@freebsd.org; Fri, 11 Feb 2000 10:49:24 +0100 (CET) Date: Fri, 11 Feb 2000 10:49:24 +0100 (CET) From: Christoph Kukulies Message-Id: <200002110949.KAA14176@gil.physik.rwth-aachen.de> To: hackers@freebsd.org Subject: bonnie still trustable? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG PIII/500, 128 MB I'm wondering if this is trustable: > bonnie -s 400 File './Bonnie.14321', size: 419430400 Writing with putc()...done Rewriting...done Writing intelligently...done Reading with getc()...done Reading intelligently...done Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 400 20015 73.7 18369 22.9 6750 12.6 22308 81.5 22467 26.0 93.8 1.0 ^^^^ ? wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 19574MB (40088160 sectors), 39770 cyls, 16 heads, 63 S/T, 512 B/S -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 2:25:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from screech.weirdnoise.com (209-128-78-198.bayarea.net [209.128.78.198]) by builder.freebsd.org (Postfix) with ESMTP id B2F5B4660 for ; Fri, 11 Feb 2000 02:25:34 -0800 (PST) Received: from screech.weirdnoise.com (localhost [127.0.0.1]) by screech.weirdnoise.com (8.9.3/8.9.3) with ESMTP id CAA21569; Fri, 11 Feb 2000 02:26:14 -0800 Message-Id: <200002111026.CAA21569@screech.weirdnoise.com> X-Mailer: exmh version 2.0.2 To: "Jordan K. Hubbard" Cc: hackers@FreeBSD.ORG Subject: Re: My views on Eclipse/BSD In-Reply-To: Your message of "Thu, 10 Feb 2000 20:06:01 PST." <7654.950241961@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Feb 2000 02:26:14 -0800 From: Ed Hall Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm quite pleased with what we, as individuals, will be able to learn about Eclipse, and the terms of the license don't interfere with that one bit. But--and this is my *only* objection to the license terms--we each are prohibited from discussing what we discover, absent Lucent's written permission. Such discussion would include posting to this or any other mailing list. I'm not from the GPL-or-hell set. Lucent has a perfect right to share under whatever terms they like. Our license encourages this, which is fundamentally a good thing. But they considerably reduce the usefulness of their offering to us--and, ultimately, to themselves-- by restricting us from discussing our observations of it. One can argue that such prohibitions are unenforcible, or that Lucent isn't likely to attempt to enforce them. And my read of the situation is that this is probably the case. This time. But I, for one, would rather the moral ambiguity be removed, not passed over. -Ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 3:12:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.webclub.ru (gate.web2000.ru [195.58.61.2]) by builder.freebsd.org (Postfix) with ESMTP id C374A3D2C for ; Fri, 11 Feb 2000 03:12:21 -0800 (PST) Received: from newbee.web2000.ru ([195.58.61.40]) by gate.webclub.ru with smtp (Exim 3.02 #1) id 12JDye-0001re-00 for freebsd-hackers@freebsd.org; Fri, 11 Feb 2000 14:11:08 +0300 From: Andrey Novikov Organization: WebClub To: freebsd-hackers@freebsd.org Subject: Tuning up semaphores in kernel Date: Fri, 11 Feb 2000 14:01:49 +0300 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00021114101000.00662@newbee.web2000.ru> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. Resently my PostgreSQL daemon died with: IpcSemaphoreCreate: semget failed (No space left on device) key=5432015, num=16, permission=600 I figured out that the kernel is out of available semaphores, I wanted to rebuild it but the problem is that the options related to semaphores are not documented. This is the mission critical commercial server so I don't want just to make assumptions. Can you please tell me how these all enigmatic numbers are properly choosed: options SEMMAP=31 options SEMMNI=11 options SEMMNS=61 options SEMMNU=31 options SEMMSL=61 options SEMOPM=101 options SEMUME=11 Thanks in advance, Andrey Novikov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 6: 4:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from horse.mail.ru (horse.mail.ru [194.67.23.130]) by builder.freebsd.org (Postfix) with ESMTP id B931B3D58 for ; Fri, 11 Feb 2000 06:03:55 -0800 (PST) Received: from f4.int ([10.0.0.51] helo=f4.mail.ru) by horse.mail.ru with esmtp (Exim 3.02 #116) id 12JGfq-0004WW-00; Fri, 11 Feb 2000 17:03:54 +0300 Received: from mail by f4.mail.ru with local (Exim 3.02 #112) id 12JGfs-000AGS-00; Fri, 11 Feb 2000 17:03:56 +0300 Received: from [195.46.102.248] by win.mail.ru with HTTP; Fri, 11 Feb 2000 14:03:56 +0000 (GMT) From: "Dmitry Chagin" To: "Stefan Esser" Cc: hackers@FreeBSD.ORG Subject: Re[2]: pci_map_mem return 0 Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: unknown via proxy [195.46.102.248] Reply-To: "Dmitry Chagin" Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Date: Fri, 11 Feb 2000 17:03:56 +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On 2000-01-26 21:13 +0800, dmitry@www.asbaikaltv.ru wrote: >> i am working on a specific dev driver for pci genlock >> based on Cirrus Logic GD5446 chip. >> when i try to map the cards memory, pci_map_mem return 0 >> >> map[0]: type 3, range 32, base e4000000, size 25 >> map[1]: type 1, range 32, base e6000000, size 12 >> strm0: rev 0x45 int a irq 12 on >>pci0.11.0 >> >> but map[0] is for Display Memory Base Address, but type = 3 >> it's not a PCI_MAPMEM type and >> map[1] for card registers, but type = 1. it's PCI_MAPMEM type >The PCI code in 3.1 was written by me. In 4.0 it has been much modified >by the NewBus developers, but the function in question is unchanged. >Regarding your problem: I do not see what's wrong with the map. >type 3 == PCI_MAPMEM | PCI_MAPMEMP indicates prefetchable memory, which >is the display memory, as you wrote. >type 1 == PCI_MAPMEM indicates non-prefetchable memory (i.e. memory mapped >registers). >The same map types are working just fine on my system ... Hi, thanks for reply. i decided this problem: GD5446 it's a vga controler, and bios set cmdreg to 0x00200000 i write to func pci_memen(pcicfgregs *cfg) and pci_porten(pcicfgregs *cfg) this code: cfg->cmdreg = pci_cfgread(cfg, PCIR_COMMAND, 2); /* re read command register*/ and ok, but much packed to write data to registers (i need 4 pci vga genlock on one workstation) :(( i write some code void sw_master(u_int8_t bus, u_int8_t slot, u_int8_t func) { outl(0xcf8, (1 << 31) | (bus << 16) | (slot << 11) | (func << 8) | 0x04); outl(0xcfc, 0x00); outl(0xcf8, (1 << 31) | (VGA_MASTER->bus << 16) | (VGA_MASTER->slot << 11) | (VGA_MASTER->func << 8) | 0x04); outl(0xcfc, VGA_MASTER->cmdreg); } void sw_slave(u_int8_t bus, u_int8_t slot, u_int8_t func) { outl(0xcf8, (1 << 31) | (VGA_MASTER->bus << 16) | (VGA_MASTER->slot << 11) | (VGA_MASTER->func << 8) | 0x04); outl(0xcfc, 0x00); outl(0xcf8, (1 << 31) | (bus << 16) | (slot << 11) | (func << 8) | 0x04); outl(0xcfc, 0x03); } where VGA_MASTER it's a pcicfgregs struct of basic vga adapter. is it correctly? thanks, sorry for my bad inglish :) Dmitry Chagin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 8:26:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from proxy.telecoms.bg (proxy.telecoms.bg [193.200.17.2]) by builder.freebsd.org (Postfix) with ESMTP id 8EFCC4714 for ; Fri, 11 Feb 2000 08:26:06 -0800 (PST) Received: from www.bgzone.com (bgzone [193.200.17.161]) by proxy.telecoms.bg (8.9.3/8.9.3) with ESMTP id SAA08773 for ; Fri, 11 Feb 2000 18:25:43 +0200 Received: from www.koral.bg (www.koral.bg [194.12.241.161]) by www.bgzone.com (8.9.2/8.9.2) with ESMTP id SAA14162 for ; Mon, 1 Feb 1999 18:30:24 +0200 (EET) (envelope-from mitko@www.koral.bg) Received: (from mitko@localhost) by www.koral.bg (8.9.3/8.9.2) id SAA01682 for freebsd-hackers@freebsd.org; Fri, 11 Feb 2000 18:26:39 +0200 (EET) (envelope-from mitko) Date: Fri, 11 Feb 2000 18:26:39 +0200 (EET) From: Dimitar Peikov Message-Id: <200002111626.SAA01682@www.koral.bg> To: freebsd-hackers@freebsd.org Subject: Routing problem Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have the following problem and cant see where I wrong or there is another way to do it. Problem: I have one segment in wich are connected different networks. in this case I try to use one workstation using Windows with alone IP -> let it be 192.168.1.1/32 and my freebsd uses 192.168.0.1/24 . The other Win I could setup to see this alone workstation using routing information but in my freebsd machine when I set using : route add -host 192.168.1.1 -netmask 255.255.255.255 -interface ed0 My arp table says that ed0 has IP 192.168.1.1 ????? If set using : route add -host 192.168.1.1 -netmask 255.255.255.255 192.168.0.1 My arp says nothing, but ping returns routing errors???? In fact I cannot route alone IP trought interface. It have no sense but in my case I must use tricks doing that!!! Could someone can explain me how to solve that problem? I see that 2 Windowses in this configuration have ping between, but ping between freebsd and that Windows - no! Mitko P.S.: I forgot that currently I use 3.1 release. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 8:42:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by builder.freebsd.org (Postfix) with ESMTP id DB2633D79 for ; Fri, 11 Feb 2000 08:42:35 -0800 (PST) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id LAA21091; Fri, 11 Feb 2000 11:42:16 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA23242; Fri, 11 Feb 2000 11:41:46 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.1) id LAA48618; Fri, 11 Feb 2000 11:41:46 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <200002111641.LAA48618@dean.pc.sas.com> Subject: Re: Tuning up semaphores in kernel In-Reply-To: <00021114101000.00662@newbee.web2000.ru> from Andrey Novikov at "Feb 11, 2000 02:01:49 pm" To: Andrey Novikov Date: Fri, 11 Feb 2000 11:41:45 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Take a look at: sys/conf/param.c: /* * Values in support of System V compatible semaphores. */ #ifdef SYSVSEM struct seminfo seminfo = { SEMMAP, /* # of entries in semaphore map */ SEMMNI, /* # of semaphore identifiers */ SEMMNS, /* # of semaphores in system */ SEMMNU, /* # of undo structures in system */ SEMMSL, /* max # of semaphores per id */ SEMOPM, /* max # of operations per semop call */ SEMUME, /* max # of undo entries per process */ SEMUSZ, /* size in bytes of undo structure */ SEMVMX, /* semaphore maximum value */ SEMAEM /* adjust on exit max value */ }; #endif You probably want to increase either SEMMNI or SEMMNS. Andrey Novikov wrote: > Resently my PostgreSQL daemon died with: > IpcSemaphoreCreate: semget failed (No space left on device) key=5432015, num=16, permission=600 > > I figured out that the kernel is out of available semaphores, > I wanted to rebuild it but the problem is that the options > related to semaphores are not documented. This is the mission > critical commercial server so I don't want just to make assumptions. > Can you please tell me how these all enigmatic numbers are > properly choosed: > options SEMMAP=31 > options SEMMNI=11 > options SEMMNS=61 > options SEMMNU=31 > options SEMMSL=61 > options SEMOPM=101 > options SEMUME=11 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 9:47:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from outpost.hstn.tensor.pgs.com (outpost.hstn.tensor.pgs.com [157.147.25.67]) by builder.freebsd.org (Postfix) with ESMTP id 9E5BF4765 for ; Fri, 11 Feb 2000 09:47:20 -0800 (PST) Received: from hap.hstn.tensor.pgs.com (hap.hstn.tensor.pgs.com [157.147.132.13]) by outpost.hstn.tensor.pgs.com (8.9.3/8.9.3) with ESMTP id LAA16616 for ; Fri, 11 Feb 2000 11:47:05 -0600 (CST) Received: from prg01.hstn.tensor.pgs.com (prg01.hstn.tensor.pgs.com [157.147.132.150]) by hap.hstn.tensor.pgs.com (8.9.3/8.9.3) with ESMTP id LAA03025 for ; Fri, 11 Feb 2000 11:47:04 -0600 (CST) Received: from prg01.hstn.tensor.pgs.com (localhost [127.0.0.1]) by prg01.hstn.tensor.pgs.com (8.8.8+Sun/8.8.8) with ESMTP id LAA12790 for ; Fri, 11 Feb 2000 11:47:03 -0600 (CST) Message-Id: <200002111747.LAA12790@prg01.hstn.tensor.pgs.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: Detecting PnP devices upon module load Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Feb 2000 11:47:02 -0600 From: Steve Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are there any existing examples of this happening? I'm doing a version of the Linux joystick driver ported to FreeBSD and of course some of the devices are PnP. Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 10:31:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hydrant.intranova.net (hydrant.intranova.net [209.201.95.10]) by builder.freebsd.org (Postfix) with SMTP id 63D734794 for ; Fri, 11 Feb 2000 10:31:02 -0800 (PST) Received: (qmail 23110 invoked from network); 11 Feb 2000 18:29:23 -0000 Received: from localhost (oogali@127.0.0.1) by hydrant.intranova.net with SMTP; 11 Feb 2000 18:29:23 -0000 Date: Fri, 11 Feb 2000 13:29:23 -0500 (EST) From: Omachonu Ogali To: Dimitar Peikov Cc: freebsd-hackers@freebsd.org Subject: Re: Routing problem In-Reply-To: <200002111626.SAA01682@www.koral.bg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG route add -net 192.168.1.0 -netmask 255.255.255.0 -interface ed0 On Fri, 11 Feb 2000, Dimitar Peikov wrote: > Hi, > I have the following problem and cant see where I wrong or there is another way to do it. > Problem: I have one segment in wich are connected different networks. in this case I try to use one workstation using Windows with alone IP -> let it be 192.168.1.1/32 and my freebsd uses 192.168.0.1/24 . The other Win I could setup to see this alone workstation using routing information but in my freebsd machine when I set using : > > route add -host 192.168.1.1 -netmask 255.255.255.255 -interface ed0 > > My arp table says that ed0 has IP 192.168.1.1 ????? > > If set using : > > route add -host 192.168.1.1 -netmask 255.255.255.255 192.168.0.1 > > My arp says nothing, but ping returns routing errors???? > In fact I cannot route alone IP trought interface. It have no sense but in my case I must use tricks doing that!!! > > Could someone can explain me how to solve that problem? I see that 2 Windowses in this configuration have ping between, but ping between freebsd and that Windows - no! > > Mitko > P.S.: I forgot that currently I use 3.1 release. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- +-------------------------------------------------------------------------+ | Omachonu Ogali oogali@intranova.net | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 13: 0:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by builder.freebsd.org (Postfix) with ESMTP id 00E3C4883; Fri, 11 Feb 2000 13:00:07 -0800 (PST) Received: from localhost (987 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Fri, 11 Feb 2000 15:59:49 -0500 (EST) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Fri, 11 Feb 2000 15:59:49 -0500 From: Jim Mercer To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: patches for de driver (full-duplex packet loss problems) Message-ID: <20000211155948.D13211@reptiles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i hear that there are some patches which might fix some serious packet loss problems with the de driver in 100mbps fullduplex. i am running 3.4 (synced to stable via cvsup). with the mailing list archives down, i can't do my own search, but i was hoping someone on these lists could give me some pointers. -- [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ 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 Fri Feb 11 15:22:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by builder.freebsd.org (Postfix) with ESMTP id 7EF973DB7 for ; Fri, 11 Feb 2000 15:22:13 -0800 (PST) Received: from localhost (1101 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Fri, 11 Feb 2000 18:22:00 -0500 (EST) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Fri, 11 Feb 2000 18:22:00 -0500 From: Jim Mercer To: hackers@freebsd.org Subject: if_de and Znyx ZX346Q Message-ID: <20000211182200.G13211@reptiles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i suspect that the ZX346Q has some different registers or something (i'm not a hardware guy). currently, my 3.4 box probes the ZX346Q card as: de2: rev 0x30 int a irq 10 on pci2.4.0 de2: ZNYX ZX31X 21143 [10-100Mb/s] pass 3.0 the identifier "ZX31X" is built during the probe, and using it as a guide, i would say the the 346Q does not follow the same path as the 346. anyone out there with some knowledge about these Znyx cards who might be able to help me patch the driver to recognize the 346Q card? -- [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ 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 Fri Feb 11 16:16:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by builder.freebsd.org (Postfix) with ESMTP id 0D1B13DB6 for ; Fri, 11 Feb 2000 16:16:09 -0800 (PST) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA82907 for ; Fri, 11 Feb 2000 19:16:00 -0500 (EST) Message-Id: <200002120016.TAA82907@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: hard lock under 3.4-STABLE Date: Fri, 11 Feb 2000 19:16:00 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am seeing a situation where a 3.4 system hard-locks while running 3.4 (hard lock being that it does not respond to its serial console, nor is it pingable). I believe (perhaps) that it may be NFS related, with a program running on an NFS client when the executable itself is deleted from the server (although I haven't seen that style of panic in quite some time, and it is usually has a couple of lines earlier in the output to the effect that it lost its backing store. I realize that information is sparse in this, but that is because the information that I have is equally sparse... I have no kernel messages, I cannot drop into the kernel debugger, and no crashdump is ever created (I need to hit the reset button to recover.) I am trying to reproduce a test case, but it is difficult not knowing what has caused the problems in the first place. -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 16:16:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by builder.freebsd.org (Postfix) with ESMTP id DD93341E3 for ; Fri, 11 Feb 2000 16:16:15 -0800 (PST) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id TAA16353 for ; Fri, 11 Feb 2000 19:15:05 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Fri, 11 Feb 2000 19:15:04 -0500 (EST) From: Chuck Robey To: FreeBSD Hackers List Subject: MAKEOBJDIR Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is the kind of thing I normally look into the mailing list archives for, but since they're down now ... Does anyone know where there's a good explanation of how make uses MAKEOBJDIR and MAKEOBJDIRPREFIX? They're listed as being respected by make in the man page, but it doesn't say why. I'm trying to understand how it's used in older systems and current systems, and not able to follow it yet. Something is done via bsd.obj.mk that I can't see (because of make's special relationship with those two). Thanks. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 16:17:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by builder.freebsd.org (Postfix) with ESMTP id 67C963DAE; Fri, 11 Feb 2000 16:17:50 -0800 (PST) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA82957; Fri, 11 Feb 2000 19:17:42 -0500 (EST) Message-Id: <200002120017.TAA82957@cs.rpi.edu> To: freebsd-hackers@freebsd.org Cc: freebsd-current@freebsd.org Subject: rpc.lockd Date: Fri, 11 Feb 2000 19:17:41 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I realize that we are all very busy and the coming 4.0-RELEASE has also compounded things, but I have heard nothing back on the rpc.lockd that was released just a short time ago. I take it no news is good news and we can start the process of bringing it into the source tree? :) -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 17:36: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 278243FD5; Fri, 11 Feb 2000 17:35:59 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA85307; Fri, 11 Feb 2000 17:35:50 -0800 (PST) (envelope-from dillon) Date: Fri, 11 Feb 2000 17:35:50 -0800 (PST) From: Matthew Dillon Message-Id: <200002120135.RAA85307@apollo.backplane.com> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rpc.lockd References: <200002120017.TAA82957@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I realize that we are all very busy and the coming 4.0-RELEASE has also :compounded things, but I have heard nothing back on the rpc.lockd that :was released just a short time ago. I take it no news is good news and :we can start the process of bringing it into the source tree? :) : :-- :David Cross | email: crossd@cs.rpi.edu :Acting Lab Director | NYSLP: FREEBSD :Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd :Rensselaer Polytechnic Institute, | Ph: 518.276.2860 I've been very interested in it, but I was going to wait until after the release before starting to mess with it. -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 Fri Feb 11 18: 3:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 4FE6941CE for ; Fri, 11 Feb 2000 18:03:25 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA85496; Fri, 11 Feb 2000 18:03:16 -0800 (PST) (envelope-from dillon) Date: Fri, 11 Feb 2000 18:03:16 -0800 (PST) From: Matthew Dillon Message-Id: <200002120203.SAA85496@apollo.backplane.com> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: hard lock under 3.4-STABLE References: <200002120016.TAA82907@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I am seeing a situation where a 3.4 system hard-locks while running 3.4 :(hard lock being that it does not respond to its serial console, nor is :it pingable). I believe (perhaps) that it may be NFS related, with a :program running on an NFS client when the executable itself is deleted :from the server (although I haven't seen that style of panic in quite :some time, and it is usually has a couple of lines earlier in the output :to the effect that it lost its backing store. : :I realize that information is sparse in this, but that is because the :information that I have is equally sparse... I have no kernel messages, :I cannot drop into the kernel debugger, and no crashdump is ever created :(I need to hit the reset button to recover.) : :I am trying to reproduce a test case, but it is difficult not knowing what :has caused the problems in the first place. : :-- :David Cross | email: crossd@cs.rpi.edu :Acting Lab Director | NYSLP: FREEBSD I presume its the client that is locking up? If you remove the server binary and the client takes a page fault on the binary, and does not have the page in the cache, what is supposed to happen is that the program is supposed to seg fault when the NFS read fails. It's quite possible that there is a bug in dealing with this situation and if you can get it repeatable we can probably fix it fairly easily. -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 Fri Feb 11 18:21:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fb02.eng00.mindspring.net (fb02.eng00.mindspring.net [207.69.229.20]) by builder.freebsd.org (Postfix) with ESMTP id 1A98E3EFC for ; Fri, 11 Feb 2000 18:21:50 -0800 (PST) Received: from confusion.net (user-2iveaac.dialup.mindspring.com [165.247.41.76]) by fb02.eng00.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA16507; Fri, 11 Feb 2000 21:19:44 -0500 (EST) Message-ID: <38A4C2DE.D57E9209@confusion.net> Date: Fri, 11 Feb 2000 21:18:06 -0500 From: Laurence Berland Organization: B.R.A.T.T. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Ed Hall Cc: "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: My views on Eclipse/BSD References: <200002111026.CAA21569@screech.weirdnoise.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Most licenses aren't all that enforceable. I was speaking with a lawyer friend who theorized that if the person accepting the license was under 18 (in the US at least) then they could do whatever they want with it. Solution? Have someone download it for you...I'm only 17, anybody want unencumbered code? :) Ed Hall wrote: > > One can argue that such prohibitions are unenforcible, or that Lucent > isn't likely to attempt to enforce them. And my read of the situation > is that this is probably the case. This time. But I, for one, would > rather the moral ambiguity be removed, not passed over. > > -Ed > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message PS: No, I wont actually send you the code, I'm kidding. -- Laurence Berland, Stuyvesant HS Debate <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. http://stuy.debate.net icq #7434346 aol imer E1101 The above email Copyright (C) 2000 Laurence Berland All rights reserved To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 20:30:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by builder.freebsd.org (Postfix) with ESMTP id 851B53F0F for ; Fri, 11 Feb 2000 20:30:05 -0800 (PST) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <20000212031822.DDSH25652.mail.rdc3.on.home.com@tristan.net>; Fri, 11 Feb 2000 19:18:22 -0800 Content-Length: 1778 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <7654.950241961@zippy.cdrom.com> Date: Fri, 11 Feb 2000 22:16:25 -0500 (EST) From: Colin To: "Jordan K. Hubbard" Subject: RE: My views on Eclipse/BSD Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As one of the masses that could probably be accused of "whining" about the conditions that eclipse was released under, I figure I better say a little more. I think what Lucent has done here is "a good thing" ;) At the very least it gives us a benchmark to work against. At the best, it gives us a chance to get ahead of the rest of the world in a very important area. Having said that, there seemed to be a nascent movement to absorb what Lucent released into FreeBSD, which I see as a "not quite good thing". Working with network management and QoS all day every day, my experience so far is that we are still too early in the game to say that we have seen the light and it is now available for download at... I think what Lucent is trying to do here is prod the software industry and see what happens. Working for a different telecom, I can say there is a lot of doubt about QoS implementations, not least because the engineers writing the standards aren't all that sure about what they're doing yet. This, I guess, is one of the joys of being out in front ;) On 11-Feb-2000 Jordan K. Hubbard wrote: > I saw the Lucent folks behind this when they first brought a demo of > Eclipse to FreeBSDCon '99 and, frankly, I was just pleased that they > were willing to show up as exhibitors and to show it off at all. > This I definately agree with. Finally, I would hazard to say the licensing that Lucent released Eclipse under is not a great leap back from the BSD license, rather a small step sideways. The BSD license says, in effect, do what you like with this code. Lucent's license says, again in effect, do what you like with this code, just don't use it as the basis for a commercial product. Draw your own conclusions ;) cheers, Colin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 20:58:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51]) by builder.freebsd.org (Postfix) with ESMTP id 8C6B73E07 for ; Fri, 11 Feb 2000 20:58:16 -0800 (PST) Received: from confusion.net (user-2iveaac.dialup.mindspring.com [165.247.41.76]) by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id XAA31135; Fri, 11 Feb 2000 23:40:09 -0500 (EST) Message-ID: <38A4E3C6.4A3F828E@confusion.net> Date: Fri, 11 Feb 2000 23:38:31 -0500 From: Laurence Berland Organization: B.R.A.T.T. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Kenneth Milton , hackers@freebsd.org Subject: Re: My views on Eclipse/BSD References: <200002120419.OAA91247@mail.theinternet.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well the idea is that someone under 18 in the US can't legally be party to a contract, so the contract becomes null and void even if I agree to it. There's lots of legal precedent on this. It may not be this way in other countries (I take it Australia is different). So if we get stuck with evil shrink wrap licenses, I could charge ppl five dollars to unwrap and unseal software for them or something. This certainly isn't something I would do, but I'm talking theory. There was hooplah when Corel wouldn't let ppl under 18 download their Linux, but it was to protect them. However, since I could just lie, I could download it anyway, and they could do nothing. I'd have breeched the contract, but since I can't be a party to it anyway, there's nothing they can do. I'm not a lawyer, heck I'm still in my last term of high school, so this is all of course just my take on it, but it seems fairly consistent in the cases I've seen. Since the Eclipse people didnt put anything about age in there (at least I didn't notice it), it would appear I am now the proud owner of unencumbered code and they have no possible recourse. I don't think this should be abused or anything; I'd probably have trouble when I turn 18, and it just doesn't seem right to me. Perhaps some other minor is braver than I. Regards, Laurence Andrew Kenneth Milton wrote: > > +----[ Laurence Berland ]--------------------------------------------- > | Most licenses aren't all that enforceable. I was speaking with a lawyer > | friend who theorized that if the person accepting the license was under > | 18 (in the US at least) then they could do whatever they want with it. > > If you are unable to enter into that contract, then you would not legally > be able to download the code. > > -- > Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton > The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | > ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon > PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| -- Laurence Berland, Stuyvesant HS Debate <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. http://stuy.debate.net icq #7434346 aol imer E1101 The above email Copyright (C) 2000 Laurence Berland All rights reserved To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 20:59:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by builder.freebsd.org (Postfix) with ESMTP id 0A6A14319 for ; Fri, 11 Feb 2000 20:59:36 -0800 (PST) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id XAA16922 for ; Fri, 11 Feb 2000 23:50:21 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Fri, 11 Feb 2000 23:50:21 -0500 (EST) From: Chuck Robey To: FreeBSD Hackers List Subject: Re: MAKEOBJDIR In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 Feb 2000, Chuck Robey wrote: > This is the kind of thing I normally look into the mailing list archives > for, but since they're down now ... > > Does anyone know where there's a good explanation of how make uses > MAKEOBJDIR and MAKEOBJDIRPREFIX? They're listed as being respected by > make in the man page, but it doesn't say why. I'm trying to understand > how it's used in older systems and current systems, and not able to follow > it yet. Something is done via bsd.obj.mk that I can't see (because of > make's special relationship with those two). Replying to my own message... I was working on an old 2.2.2 system, when I got home and checked the current man pages, there it was, nice as you please. Sorry to bother folks. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 11 21:31: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by builder.freebsd.org (Postfix) with ESMTP id 9B6F23E07 for ; Fri, 11 Feb 2000 21:30:54 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 0CC201CD7; Sat, 12 Feb 2000 13:30:47 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Laurence Berland Cc: Andrew Kenneth Milton , hackers@freebsd.org Subject: Re: My views on Eclipse/BSD In-Reply-To: Message from Laurence Berland of "Fri, 11 Feb 2000 23:38:31 EST." <38A4E3C6.4A3F828E@confusion.net> Date: Sat, 12 Feb 2000 13:30:47 +0800 From: Peter Wemm Message-Id: <20000212053047.0CC201CD7@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One key thing to keep in mind is that copyrights apply automatically regardless of age, contracts etc. You have no right to copy a copyrighted work unless the right to do so is given to you (or you have statutory rights such as making backups etc). In this case, you don't have the right to redistribute it except those granted by the license with it's conditions. If you don't accept the license or cannot because you're under the age of being able to enter into a contract or whatever, then you can't redistribute it *period*. You can download it (they are distributing it, not you), and do pretty much whatever you like with it once they've given it to you, but you can't give it to anyone else. This means that if you were under 18 etc, you probably could use it for commercial purposes if you believed the license didn't apply. (And Lucent/whoever *do* own the copyright on the additional Eclipse stuff). Licenses that attempt to impose conditions on what you can personally do with it once you've got it (especially "shrink wrap" licenses) are on very shakey ground anyway - especially if it's sold. You'll note that many such licenses have a little note that says "this license does not affect whatever statutory rights you may have" - in many cases this shoots the bulk of license down as most of it tries to set up conditions and restrictions on rights that you are granted by law and that the license cannot restrict. This varies a lot from country to country. If you're intending to exploit this sort of thing, you'd better see a lawyer. :-) Laurence Berland wrote: > Well the idea is that someone under 18 in the US can't legally be party > to a contract, so the contract becomes null and void even if I agree to > it. There's lots of legal precedent on this. It may not be this way in > other countries (I take it Australia is different). So if we get stuck > with evil shrink wrap licenses, I could charge ppl five dollars to > unwrap and unseal software for them or something. This certainly isn't > something I would do, but I'm talking theory. There was hooplah when > Corel wouldn't let ppl under 18 download their Linux, but it was to > protect them. However, since I could just lie, I could download it > anyway, and they could do nothing. I'd have breeched the contract, but > since I can't be a party to it anyway, there's nothing they can do. I'm > not a lawyer, heck I'm still in my last term of high school, so this is > all of course just my take on it, but it seems fairly consistent in the > cases I've seen. Since the Eclipse people didnt put anything about age > in there (at least I didn't notice it), it would appear I am now the > proud owner of unencumbered code and they have no possible recourse. I > don't think this should be abused or anything; I'd probably have trouble > when I turn 18, and it just doesn't seem right to me. Perhaps some > other minor is braver than I. > > > Regards, > Laurence > > Andrew Kenneth Milton wrote: > > > > +----[ Laurence Berland ]--------------------------------------------- > > | Most licenses aren't all that enforceable. I was speaking with a lawyer > > | friend who theorized that if the person accepting the license was under > > | 18 (in the US at least) then they could do whatever they want with it. > > > > If you are unable to enter into that contract, then you would not legally > > be able to download the code. > > > > -- > > Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton > > The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | > > ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon > > PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| > > -- > Laurence Berland, Stuyvesant HS Debate > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Windows 98: n. > useless extension to a minor patch release for > 32-bit extensions and a graphical shell for a > 16-bit patch to an 8-bit operating system > originally coded for a 4-bit microprocessor, > written by a 2-bit company that can't stand for > 1 bit of competition. > http://stuy.debate.net > icq #7434346 aol imer E1101 > The above email Copyright (C) 2000 Laurence Berland > All rights reserved To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 2:22:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by builder.freebsd.org (Postfix) with ESMTP id 1176C3FFF for ; Sat, 12 Feb 2000 02:22:35 -0800 (PST) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 12JZh8-000CJv-0K; Sat, 12 Feb 2000 10:22:30 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA94319; Sat, 12 Feb 2000 10:22:59 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 12 Feb 2000 10:25:49 +0000 (GMT) From: Doug Rabson To: Steve Hocking Cc: hackers@freebsd.org Subject: Re: Detecting PnP devices upon module load In-Reply-To: <200002111747.LAA12790@prg01.hstn.tensor.pgs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 Feb 2000, Steve Hocking wrote: > > Are there any existing examples of this happening? I'm doing a version of the > Linux joystick driver ported to FreeBSD and of course some of the devices are > PnP. You need to dike out the unknown driver (near the end of sys/isa/isa_common.c). I'll fix this properly after 4.0 if Matt Dodd doesn't beat me to it. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 5:31:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by builder.freebsd.org (Postfix) with SMTP id 8839E3D10 for ; Sat, 12 Feb 2000 05:31:07 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 12 Feb 2000 13:31:05 +0000 (GMT) Date: Sat, 12 Feb 2000 13:31:04 +0000 From: David Malone To: Matthew Dillon Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG Subject: Re: hard lock under 3.4-STABLE Message-ID: <20000212133104.A48171@walton.maths.tcd.ie> References: <200002120016.TAA82907@cs.rpi.edu> <200002120203.SAA85496@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002120203.SAA85496@apollo.backplane.com>; from dillon@apollo.backplane.com on Fri, Feb 11, 2000 at 06:03:16PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 11, 2000 at 06:03:16PM -0800, Matthew Dillon wrote: > I presume its the client that is locking up? If you remove the > server binary and the client takes a page fault on the binary, > and does not have the page in the cache, what is supposed to happen > is that the program is supposed to seg fault when the NFS read fails. > It's quite possible that there is a bug in dealing with this situation > and if you can get it repeatable we can probably fix it fairly easily. I did some experiments with this sort of thing a few months ago. I think you can kill 3.X NFS client machines by truncating a binary on the NFS server. You can also make the machine extreamly slugish by catching SIGBUS and SIGSEGV in an executable and then causing one of these signals once the binary is modified. We see it quite frequently with people using MPI. I'll see if I can reproduce any of these effects and let you know how to do it. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 8:42:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fb01.eng00.mindspring.net (fb01.eng00.mindspring.net [207.69.229.19]) by builder.freebsd.org (Postfix) with ESMTP id 7F1E73F55 for ; Sat, 12 Feb 2000 08:42:18 -0800 (PST) Received: from ix.netcom.com (pool-209-138-224-195-troy.grid.net [209.138.224.195]) by fb01.eng00.mindspring.net (8.9.3/8.8.5) with ESMTP id LAA02068 for ; Sat, 12 Feb 2000 11:41:41 -0500 (EST) Message-ID: <38A58CFC.92CC1D05@ix.netcom.com> Date: Sat, 12 Feb 2000 11:40:29 -0500 From: Dan Diephouse X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Diskless Workstation with Etherboot Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been trying to turn a 486 that I have into a diskless workstation and have not gotten very far. I have compiled Etherboot, and set up the server with tftp and bootp. I have both daemons enabled. When I boot up the 486 machine tcpdump yields this: [root:dragon]# tcpdump -i de0 -e tcpdump: listening on de0 11:34:14.767283 0:0:b2:0:0:be Broadcast ip 342: 0.0.0.0.0 > 255.255.255.255.bootps: (request) xid:0x52850a00 secs:9 [|bootp] 11:34:24.653629 0:0:b2:0:0:be Broadcast ip 342: 0.0.0.0.0 > 255.255.255.255.bootps: (request) xid:0x52850a00 secs:18 [|bootp] . . . and so on. Bootp then complains, "bootpd[350]: sendto: Can't assign requested address" As you can see, I'm not getting very far. Below are my configuration files, please EMail back if you need other ones. Thank You, Dan Diephouse bootptab: .default:\ :hn:\ :sm=255.255.255.0:\ :ds=199.182.120.203:\ :gw=192.168.2.1:\ :hd=/usr/data/exports/tftpboot:\ :bf=null:\ :vm=rfc1048:\ :to=auto:\ :ra=255.255.255.255: nebula:\ :tc=.default:\ :ha=0000b20000be:\ #:ha=000002026767 :bf=kernel:\ :ip=192.168.2.3: The DISKLESS machine: machine "i386" cpu "I386_CPU" cpu "I486_CPU" ident DISKLESS maxusers 32 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!]options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'edoptions PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options BOOTP # Use BOOTP to obtain IP address/hostname options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info #options BOOTP_NFSV3 # Use NFS v3 to NFS mount root options BOOTP_COMPAT # Workaround for broken bootp daemons. config kernel root on wd0 controller isa0 controller pnp0 # PnP support for ISA controller eisa0 controller pci0 # Floppy drives controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 # IDE controller and disks options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 # ATAPI devices options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM device wfd0 #IDE Floppy (e.g. LS-120) # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at isa? port IO_NPX irq 13 # Serial (COM) ports device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device sio2 at isa? disable port "IO_COM3" tty irq 5 device sio3 at isa? disable port "IO_COM4" tty irq 9 # Parallel port device plip0 at ppbus? # TCP/IP over parallel device ppi0 at ppbus? # Parallel port interface device #controller vpo0 at ppbus? # Requires scbus and da0 # ISA Ethernet NICs. # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device ed0 at isa? port 0x300 net irq 5 iomem 0xd8000 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun 1 # Packet tunnel pseudo-device pty 16 # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 1 #Berkeley packet filter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 9: 2:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ab-bg.net (ab-bg.net [212.56.11.129]) by builder.freebsd.org (Postfix) with SMTP id C1FFA3F8E for ; Sat, 12 Feb 2000 09:02:47 -0800 (PST) Received: (qmail 6791 invoked by uid 1000); 12 Feb 2000 17:01:34 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 12 Feb 2000 17:01:34 -0000 Date: Sat, 12 Feb 2000 19:01:34 +0200 (EET) From: Victor Ivanov To: freebsd-hackers@freebsd.org Subject: bad floppies lock ttys Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't think this is the very right place to put this message, but I don't really want to subscribe to high-traffic mailing lists and maybe this is a device problem... The device is /dev/fd0 (standart 1,44 IDE floppy, controller fdc). When accessing bad floppy disks the kernel complains for a while and then all virtual consoles lock... ttyv*, ttyp* (used by telnet) and don't know about serials. Total lock, when you type it doesn't appear. Everyhing else seem to work fine (networking, routing, services...); the debuger (ddb) too, but I don't know what to do with it :). The solution is the F0 key (Ctrl+Alt+RESET). ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 10:17:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by builder.freebsd.org (Postfix) with ESMTP id 86A283F2A for ; Sat, 12 Feb 2000 10:17:21 -0800 (PST) Received: from newsguy.com (dcs@p18-dnz01kiryunisiki.gunma.ocn.ne.jp [210.132.6.147]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA14603; Sun, 13 Feb 2000 03:16:39 +0900 (JST) Message-ID: <38A5A355.92BE74B5@newsguy.com> Date: Sun, 13 Feb 2000 03:15:49 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Peter Wemm Cc: Laurence Berland , Andrew Kenneth Milton , hackers@FreeBSD.ORG Subject: Re: My views on Eclipse/BSD References: <20000212053047.0CC201CD7@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > One key thing to keep in mind is that copyrights apply automatically > regardless of age, contracts etc. You have no right to copy a copyrighted > work unless the right to do so is given to you (or you have statutory > rights such as making backups etc). In this case, you don't have the right > to redistribute it except those granted by the license with it's > conditions. If you don't accept the license or cannot because you're under > the age of being able to enter into a contract or whatever, then you can't > redistribute it *period*. You can download it (they are distributing it, > not you), and do pretty much whatever you like with it once they've given > it to you, but you can't give it to anyone else. This means that if you > were under 18 etc, you probably could use it for commercial purposes if you > believed the license didn't apply. (And Lucent/whoever *do* own the > copyright on the additional Eclipse stuff). So... basically... you can't redistribute GPL code unless law permits you to enter contracts? How funny... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 10:25:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51]) by builder.freebsd.org (Postfix) with ESMTP id 6578F42AC for ; Sat, 12 Feb 2000 10:25:48 -0800 (PST) Received: from ix.netcom.com ([209.138.224.195]) by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id NAA17618; Sat, 12 Feb 2000 13:25:45 -0500 (EST) Message-ID: <38A5A553.5A08F81E@ix.netcom.com> Date: Sat, 12 Feb 2000 13:24:19 -0500 From: Dan Diephouse X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Parag@ix.netcom.com, freebsd-hackers@freebsd.org Subject: Re: Diskless Workstation with Etherboot References: <81200.950379599@pinhead.parag.codegen.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a leftover from me trying a different Ethernet card. It does not work without that line....I still get the same symptoms. Thanks, Dan Diephouse Parag Patel wrote: > On Sat, 12 Feb 2000 11:40:29 EST, Dan Diephouse wrote: > > >nebula:\ > > :tc=.default:\ > > :ha=0000b20000be:\ > >#:ha=000002026767 > ^^^^^^^^^^^^^^^^^ ^^^ > > :bf=kernel:\ > > :ip=192.168.2.3: > > I hope this isn't what's in your file. bootpd won't parse past the > comment and see the subsequent two lines. All lines must be connected > with a backslash-newline without any intervening comments. > > Hope this helps. > > -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 11:14:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from galileo.poli.hu (polinet-gw.poli.hu [195.199.8.25]) by builder.freebsd.org (Postfix) with ESMTP id 249CA3FAA for ; Sat, 12 Feb 2000 11:14:15 -0800 (PST) Received: from faber.poli.hu ([195.199.8.29] helo=faber.polinet ident=mail) by galileo.poli.hu with esmtp (Exim 3.12 #1) id 12JhzG-000A3s-00 for hackers@freebsd.org; Sat, 12 Feb 2000 20:13:46 +0100 Received: from mauzi (helo=localhost) by faber.polinet with local-esmtp (Exim 3.12 #1 (Debian)) id 12JhzJ-0005RI-00 for ; Sat, 12 Feb 2000 20:13:49 +0100 Date: Sat, 12 Feb 2000 20:13:49 +0100 (CET) From: Egervary Gergely To: hackers@freebsd.org Subject: accounting, ppp Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello, [moving from -questions, as no answers received] I'm running a PPP dialup server. (mgetty-autoppp) Is there any way to do login accounting (like solaris' PAM modules, or linux pam_limits.so) Basically, I have to limit simultaneous connections, and monthly login times. -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 11:44:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by builder.freebsd.org (Postfix) with ESMTP id 9EF0C3F44 for ; Sat, 12 Feb 2000 11:44:28 -0800 (PST) Received: by mimer.webgiro.com (Postfix, from userid 66) id 61D432DC07; Sat, 12 Feb 2000 20:43:41 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 524667811; Sat, 12 Feb 2000 20:43:40 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 4E64510E12 for ; Sat, 12 Feb 2000 20:43:40 +0100 (CET) Date: Sat, 12 Feb 2000 20:43:40 +0100 (CET) From: Andrzej Bialecki To: freebsd-hackers@freebsd.org Subject: Kernel messages, msgbuf and syslog Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was wondering if there is any way currently to emit a message from within kernel, so that syslogd can pick it up later on, but without spoiling the standard message buffer. AFAIK, there is no way to do it right now. The reason I'm asking is that quite a few programs (most notably ipfw) spit countless messages to kernel msgbuf, thus overwriting any other important info. Is there any interest among people to implement such feature? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 12:54:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.aracnet.com (mail2.aracnet.com [216.99.193.35]) by builder.freebsd.org (Postfix) with ESMTP id 8B3CB4156 for ; Sat, 12 Feb 2000 12:53:55 -0800 (PST) Received: from shell1.aracnet.com (IDENT:root@shell1.aracnet.com [216.99.193.21]) by mail2.aracnet.com (8.9.3/8.9.3) with ESMTP id MAA27665 for ; Sat, 12 Feb 2000 12:54:17 -0800 Received: from localhost by shell1.aracnet.com (8.9.3) id MAA12644; Sat, 12 Feb 2000 12:57:46 -0800 X-Authentication-Warning: shell1.aracnet.com: beattie owned process doing -bs Date: Sat, 12 Feb 2000 12:57:46 -0800 (PST) From: Brian Beattie To: hackers@FreeBSD.ORG Subject: CMOS clock won't do 2000 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an older 486 system, running 3.4R that has a cmos clock that seems to be unwilling to accept years out side the range 94-99. The bios seems willing to set dates between 1994-2099, but after reboot any year not between 94-99 is converted to {20,19}94. What I have done is to go into i386/isa/clock.c and in the routines inittodr, resettodr, is to add 6 to and subtract 6 from the years respectively. I was wondering if anybody had any better ideas. Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 13: 1:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by builder.freebsd.org (Postfix) with ESMTP id A1A063F67 for ; Sat, 12 Feb 2000 13:01:12 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id NAA98662; Sat, 12 Feb 2000 13:01:07 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Sat, 12 Feb 2000 13:01:07 -0800 (PST) From: Doug White To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.lockd In-Reply-To: <200002120017.TAA82957@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First of all, don't crosspost to both -hackers and -current. They tend to cover the same audience. On Fri, 11 Feb 2000, David E. Cross wrote: > I realize that we are all very busy and the coming 4.0-RELEASE has also > compounded things, but I have heard nothing back on the rpc.lockd that > was released just a short time ago. I take it no news is good news and > we can start the process of bringing it into the source tree? :) 4.0-RELEASE is in code freeze, so it won't make in there. I suspect someone will be available to get it into -CURRENT after 4.0 ships. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | 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 Feb 12 14:46:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by builder.freebsd.org (Postfix) with ESMTP id 794FB3FF6 for ; Sat, 12 Feb 2000 14:46:31 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.9.2/8.9.3) with UUCP id XAA66366 for freebsd-hackers@freebsd.org; Sat, 12 Feb 2000 23:46:27 +0100 (CET) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id XAA03245 for ; Sat, 12 Feb 2000 23:43:56 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <038101bf75aa$ac3afba0$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: Subject: A can ping C, but not B Date: Sat, 12 Feb 2000 23:31:37 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got 4 machines at home on an Ethernet coax. A-B-C-D. B is FreeBSD server (samba), the rest is win98 (C is split win/fbsd). C and D talks fine to B. A talks nicely to C (haven't tried to D), but = very poorly to B.=20 I got ping losses of 1 out of 3 to 4 from A to B, but no loss A to C. I then took the T-plug from A and put it on a hub, and UTP from hub to = A. Still 100% from A to C, but now no ping at all from A to B! What's going on? Standing waves? I got proper terminators either end. The cable is assembled of well 10 shorter pieces with "empty" T-plugs, = could that be a problem? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 16:46:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rz.fh-wilhelmshaven.de (mail.rz.fh-wilhelmshaven.de [139.13.25.134]) by builder.freebsd.org (Postfix) with ESMTP id 6937B3D99 for ; Sat, 12 Feb 2000 16:46:46 -0800 (PST) Received: from fettesau.stuwo.fh-wilhelmshaven.de (stuwopc5.stuwo.fh-wilhelmshaven.de [139.13.209.5]) by mail.rz.fh-wilhelmshaven.de (8.9.3/8.9.3) with SMTP id BAA17898; Sun, 13 Feb 2000 01:46:44 +0100 (MET) Message-Id: <4.1.20000213014048.009cfa70@mail.rz.fh-wilhelmshaven.de> X-Sender: ohoyer@mail.rz.fh-wilhelmshaven.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 13 Feb 2000 01:47:19 +0100 To: "Leif Neland" From: Olaf Hoyer Subject: Re: A can ping C, but not B Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <038101bf75aa$ac3afba0$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 23:31 12.02.00 +0100, you wrote: >I got 4 machines at home on an Ethernet coax. >A-B-C-D. >B is FreeBSD server (samba), the rest is win98 (C is split win/fbsd). > >C and D talks fine to B. A talks nicely to C (haven't tried to D), but very >poorly to B. >I got ping losses of 1 out of 3 to 4 from A to B, but no loss A to C. > >I then took the T-plug from A and put it on a hub, and UTP from hub to A. >Still 100% from A to C, but now no ping at all from A to B! > >What's going on? Standing waves? I got proper terminators either end. > >The cable is assembled of well 10 shorter pieces with "empty" T-plugs, could >that be a problem? Hi! Yes, that is a very big problem, since the signal gets reflected at every opening of the T-plug. Even if you do that with the special connectors, you will realize severe problems. Windows also does some retries with high timeout values, and therefore gets at least something through, but as a BSD box reacts somewhat different, it tells you what happened directly by slowing down. The prob is that Win always reacts somewhat sluggish, so you cannot notice the difference between failure and normal op... Cables are cheap now, simply buy a new one, or (if you have combo cards) throw away the coax and go for TP cabling. (If you have trouble finding approp. length there in DK for a reasonable price, mail me privately... ) Regards Olaf Hoyer -------- Olaf Hoyer www.nightfire.de mailto:Olaf.Hoyer@nightfire.de FreeBSD- Turning PC's into workstations ICQ:22838075 Liebe und Hass sind nicht blind, aber geblendet vom Feuer, dass sie selber mit sich tragen. (Nietzsche) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 18:53:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id 2E99A3FD7 for ; Sat, 12 Feb 2000 18:53:57 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id SAA01956; Sat, 12 Feb 2000 18:53:25 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id SAA24231; Sat, 12 Feb 2000 18:53:24 -0800 Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id SAA00469; Sat, 12 Feb 2000 18:53:22 -0800 (PST) Message-ID: <38A61E1A.8DA94C8C@softweyr.com> Date: Sat, 12 Feb 2000 19:59:38 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Brian Beattie Cc: hackers@freebsd.org Subject: Re: CMOS clock won't do 2000 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Beattie wrote: > > I have an older 486 system, running 3.4R that has a cmos clock that seems > to be unwilling to accept years out side the range 94-99. The bios seems > willing to set dates between 1994-2099, but after reboot any year not > between 94-99 is converted to {20,19}94. > > What I have done is to go into i386/isa/clock.c and in the routines > inittodr, resettodr, is to add 6 to and subtract 6 from the years > respectively. I was wondering if anybody had any better ideas. Is the clock chip socketed? Are BIOS updates available for the motherboard? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 19:30:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by builder.freebsd.org (Postfix) with ESMTP id 2BE6D4417 for ; Sat, 12 Feb 2000 19:30:12 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id DBB531CD9; Sun, 13 Feb 2000 11:30:13 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Beattie Cc: hackers@FreeBSD.ORG Subject: Re: CMOS clock won't do 2000 In-Reply-To: Message from Brian Beattie of "Sat, 12 Feb 2000 12:57:46 PST." Date: Sun, 13 Feb 2000 11:30:13 +0800 From: Peter Wemm Message-Id: <20000213033013.DBB531CD9@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Beattie wrote: > I have an older 486 system, running 3.4R that has a cmos clock that seems > to be unwilling to accept years out side the range 94-99. The bios seems > willing to set dates between 1994-2099, but after reboot any year not > between 94-99 is converted to {20,19}94. > > What I have done is to go into i386/isa/clock.c and in the routines > inittodr, resettodr, is to add 6 to and subtract 6 from the years > respectively. I was wondering if anybody had any better ideas. Also watch out for day-of-month and day-of-week calulations done in the cmos chip. It's a shame you couldn't set it for 1972 which matches the year 2000 date, day, and leap year sequences exactly. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 19:47:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by builder.freebsd.org (Postfix) with ESMTP id 49D844362 for ; Sat, 12 Feb 2000 19:47:26 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id EA6E81CD9; Sun, 13 Feb 2000 11:47:27 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Daniel C. Sobral" Cc: Laurence Berland , Andrew Kenneth Milton , hackers@FreeBSD.ORG Subject: Re: My views on Eclipse/BSD In-Reply-To: Message from "Daniel C. Sobral" of "Sun, 13 Feb 2000 03:15:49 +0900." <38A5A355.92BE74B5@newsguy.com> Date: Sun, 13 Feb 2000 11:47:27 +0800 From: Peter Wemm Message-Id: <20000213034727.EA6E81CD9@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > Peter Wemm wrote: > > > > One key thing to keep in mind is that copyrights apply automatically > > regardless of age, contracts etc. You have no right to copy a copyrighted > > work unless the right to do so is given to you (or you have statutory > > rights such as making backups etc). In this case, you don't have the right > > to redistribute it except those granted by the license with it's > > conditions. If you don't accept the license or cannot because you're under > > the age of being able to enter into a contract or whatever, then you can't > > redistribute it *period*. You can download it (they are distributing it, > > not you), and do pretty much whatever you like with it once they've given > > it to you, but you can't give it to anyone else. This means that if you > > were under 18 etc, you probably could use it for commercial purposes if you > > believed the license didn't apply. (And Lucent/whoever *do* own the > > copyright on the additional Eclipse stuff). > > So... basically... you can't redistribute GPL code unless law permits > you to enter contracts? How funny... :-) It depends on whether you consider a redistribution license a contract or not. If it says somthing to the effect of "in order to redistribute this, these are the conditions you must follow", that's not necessarily a contract. You don't have any obligations, unless you want the right to distribute it. However, if it's a "click here to accept" in order to download something, then thats closer to a contract as it's getting you to accept obligations regardless of whether you distribute it or not. This covers things like "no commercial use" and so on. You can generally only impose restrictions on *usage* via some sort of contract. The GPL is very much the former. You can pretty much do whatever you damn well please with it and have absolutely no obligations. But to get the right to distribute the copyrighted code (or derivatives), then the license spells out the conditions under which you can distribute it. The BSD license is similar - you don't have any obligations unless you want to distribute it. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 12 20:46:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by builder.freebsd.org (Postfix) with ESMTP id C9C80467E for ; Sat, 12 Feb 2000 20:46:07 -0800 (PST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA97433; Sun, 13 Feb 2000 15:16:50 +1030 (CST) Date: Sun, 13 Feb 2000 15:16:50 +1030 From: Greg Lehey To: Christoph Kukulies Cc: hackers@FreeBSD.ORG Subject: Re: bonnie still trustable? Message-ID: <20000213151650.A97412@freebie.lemis.com> References: <200002110949.KAA14176@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200002110949.KAA14176@gil.physik.rwth-aachen.de> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 11 February 2000 at 10:49:24 +0100, Christoph Kukulies wrote: > PIII/500, 128 MB > > I'm wondering if this is trustable: > >> bonnie -s 400 > File './Bonnie.14321', size: 419430400 > Writing with putc()...done > Rewriting...done > Writing intelligently...done > Reading with getc()...done > Reading intelligently...done > Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > 400 20015 73.7 18369 22.9 6750 12.6 22308 81.5 22467 26.0 93.8 1.0 > ^^^^ > ? > > > wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ff on isa > wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 > wd0: 19574MB (40088160 sectors), 39770 cyls, 16 heads, 63 S/T, 512 B/S There are lies, damn lies, and statistics. I'm sure that the results mean something; the real question is, what do you want them to mean? If you're trying to measure the storage device, rawio (Ports Collection) is a much better choice. Greg -- Finger grog@lemis.com for PGP public key 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 Sun Feb 13 0:57:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by builder.freebsd.org (Postfix) with ESMTP id 284AB4053 for ; Sun, 13 Feb 2000 00:57:10 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA58797; Sun, 13 Feb 2000 01:57:14 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA62668; Sun, 13 Feb 2000 01:58:45 -0700 (MST) Message-Id: <200002130858.BAA62668@harmony.village.org> To: Brian Beattie Subject: Re: CMOS clock won't do 2000 Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 12 Feb 2000 12:57:46 PST." References: Date: Sun, 13 Feb 2000 01:58:45 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Brian Beattie writes: : I have an older 486 system, running 3.4R that has a cmos clock that seems : to be unwilling to accept years out side the range 94-99. The bios seems : willing to set dates between 1994-2099, but after reboot any year not : between 94-99 is converted to {20,19}94. ntpdate on boot is what we use in the village for this sort of thing. We run ntp at other times. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 3:15:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.webclub.ru (gate.web2000.ru [195.58.61.2]) by builder.freebsd.org (Postfix) with ESMTP id E181F4174 for ; Sun, 13 Feb 2000 03:15:20 -0800 (PST) Received: from newbee.web2000.ru ([195.58.61.40]) by gate.webclub.ru with smtp (Exim 3.02 #1) id 12Jwwt-00022m-00; Sun, 13 Feb 2000 14:12:19 +0300 From: Andrey Novikov Organization: WebClub To: Brian Dean Subject: Re: Tuning up semaphores in kernel Date: Sun, 13 Feb 2000 14:08:52 +0300 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: freebsd-hackers@FreeBSD.ORG References: <200002111641.LAA48618@dean.pc.sas.com> In-Reply-To: <200002111641.LAA48618@dean.pc.sas.com> MIME-Version: 1.0 Message-Id: <00021314111301.00418@newbee.web2000.ru> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > struct seminfo seminfo = { > SEMMAP, /* # of entries in semaphore map */ > SEMMNI, /* # of semaphore identifiers */ > SEMMNS, /* # of semaphores in system */ > SEMMNU, /* # of undo structures in system */ > SEMMSL, /* max # of semaphores per id */ > SEMOPM, /* max # of operations per semop call */ > SEMUME, /* max # of undo entries per process */ > SEMUSZ, /* size in bytes of undo structure */ > SEMVMX, /* semaphore maximum value */ > SEMAEM /* adjust on exit max value */ > }; > You probably want to increase either SEMMNI or SEMMNS. I've noticed that but why are they so "round"? Is there any corelation between all these numbers? I don't want to break my kernel by guessing. > > options SEMMAP=31 > > options SEMMNI=11 > > options SEMMNS=61 > > options SEMMNU=31 > > options SEMMSL=61 > > options SEMOPM=101 > > options SEMUME=11 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 7:42:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by builder.freebsd.org (Postfix) with ESMTP id 099F441BD for ; Sun, 13 Feb 2000 07:42:51 -0800 (PST) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id KAA17612; Sun, 13 Feb 2000 10:41:55 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA24691; Sun, 13 Feb 2000 10:41:25 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.1) id KAA70378; Sun, 13 Feb 2000 10:41:25 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <200002131541.KAA70378@dean.pc.sas.com> Subject: Re: Tuning up semaphores in kernel In-Reply-To: <00021314111301.00418@newbee.web2000.ru> from Andrey Novikov at "Feb 13, 2000 02:08:52 pm" To: Andrey Novikov Date: Sun, 13 Feb 2000 10:41:25 -0500 (EST) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG SEMMNI is the number of semaphore ids, i.e., the number of times you can call 'semget()' without deleting any semaphores. SEMMNS is the actual number of semaphores in the system, which should be >= SEMMNI. Of course, you can ask 'semget()' to give you up to SEMMSL semaphores on each call, so SEMMNS should usually be larger than SEMMNI. Ideally, if you know the max number of semaphores that a program obtains via a semget call, set SEMMSL to that value. Then, if you know the max number of semid's that are in use at any given time, then set SEMMNI to that value. Then compute SEMMNS = SEMMNI*SEMMNS. This will guarantee you have enough, as long as your usage information is accurate. Personally, I would just bump up SEMMNI and SEMMNS by 20% (or whatever). Your documentation that came with your application should give you an idea of it's semaphore usage. Use that as the guide as to what to set these things to as a starting point. -Brian Andrey Novikov wrote: > > struct seminfo seminfo = { > > SEMMAP, /* # of entries in semaphore map */ > > SEMMNI, /* # of semaphore identifiers */ > > SEMMNS, /* # of semaphores in system */ > > SEMMNU, /* # of undo structures in system */ > > SEMMSL, /* max # of semaphores per id */ > > SEMOPM, /* max # of operations per semop call */ > > SEMUME, /* max # of undo entries per process */ > > SEMUSZ, /* size in bytes of undo structure */ > > SEMVMX, /* semaphore maximum value */ > > SEMAEM /* adjust on exit max value */ > > }; > > You probably want to increase either SEMMNI or SEMMNS. > > I've noticed that but why are they so "round"? Is there any corelation > between all these numbers? I don't want to break my kernel by guessing. > > > > options SEMMAP=31 > > > options SEMMNI=11 > > > options SEMMNS=61 > > > options SEMMNU=31 > > > options SEMMSL=61 > > > options SEMOPM=101 > > > options SEMUME=11 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 11:13:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [216.99.193.36]) by builder.freebsd.org (Postfix) with ESMTP id 9C9483F11 for ; Sun, 13 Feb 2000 11:13:53 -0800 (PST) Received: from shell1.aracnet.com (IDENT:root@shell1.aracnet.com [216.99.193.21]) by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id LAA13276; Sun, 13 Feb 2000 11:14:18 -0800 Received: from localhost by shell1.aracnet.com (8.9.3) id LAA24271; Sun, 13 Feb 2000 11:18:01 -0800 X-Authentication-Warning: shell1.aracnet.com: beattie owned process doing -bs Date: Sun, 13 Feb 2000 11:18:01 -0800 (PST) From: Brian Beattie To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: CMOS clock won't do 2000 In-Reply-To: <200002130858.BAA62668@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 13 Feb 2000, Warner Losh wrote: > In message Brian Beattie writes: > : I have an older 486 system, running 3.4R that has a cmos clock that seems > : to be unwilling to accept years out side the range 94-99. The bios seems > : willing to set dates between 1994-2099, but after reboot any year not > : between 94-99 is converted to {20,19}94. > > ntpdate on boot is what we use in the village for this sort of thing. > We run ntp at other times. > I'm hopeing to run picobsd-router on this machine so adding extra executables may not be possible. I grabbed the y2k test/fix from the BIOS site (Phoenix bought Award). I includes a windoze95 fix, that seems to adjust the clock on boot by running something from config.sys. Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 13:30: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from egroups.net (teapot.egroups.net [63.76.160.2]) by builder.freebsd.org (Postfix) with SMTP id DF5CE42A1 for ; Sun, 13 Feb 2000 13:30:03 -0800 (PST) Received: (qmail 27614 invoked from network); 13 Feb 2000 21:29:57 -0000 Received: from dhcp-192-168-2-17.egroups.net (HELO egroups.net) (192.168.2.17) by teapot.egroups.net with SMTP; 13 Feb 2000 21:29:57 -0000 Message-ID: <38A7224A.580D21BE@egroups.net> Date: Sun, 13 Feb 2000 13:29:46 -0800 From: Dru Nelson X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: sysctl for stack execute? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a sysctl for FreeBSD which prevents execution in the stack segment? (ie. to prevent attacks from getting root) I'm using 3.4R. -- Dru Nelson Director of Network Operations http://www.egroups.com/ Voice: 415-546-2740 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 13:50: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lanturn.express.ru (lanturn.kmost.express.ru [212.24.37.109]) by builder.freebsd.org (Postfix) with ESMTP id 9AE8B4071 for ; Sun, 13 Feb 2000 13:49:42 -0800 (PST) Received: from vova (helo=localhost) by lanturn.express.ru with local-esmtp (Exim 3.11 #1) id 12K6uK-000LYT-00; Mon, 14 Feb 2000 00:50:20 +0300 Date: Mon, 14 Feb 2000 00:50:20 +0300 (MSK) From: "Vladimir B. Grebenschikov" X-Sender: vova@lanturn.kmost.express.ru To: Andrzej Bialecki Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel messages, msgbuf and syslog In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 12 Feb 2000, Andrzej Bialecki wrote: > I was wondering if there is any way currently to emit a message from > within kernel, so that syslogd can pick it up later on, but without > spoiling the standard message buffer. AFAIK, there is no way to do it > right now. > > The reason I'm asking is that quite a few programs (most notably > ipfw) spit countless messages to kernel msgbuf, thus overwriting any other > important info. > > Is there any interest among people to implement such feature? I've got notice from one russian sysadm about realization of such mechanizm via another kernel buffer and simply program to read it He will send public sources. > Andrzej Bialecki -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 14:22:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by builder.freebsd.org (Postfix) with ESMTP id 0CDE34096 for ; Sun, 13 Feb 2000 14:22:51 -0800 (PST) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id XAA17030; Sun, 13 Feb 2000 23:22:59 +0100 (CET) Message-ID: <20000213232258.A16994@foobar.franken.de> Date: Sun, 13 Feb 2000 23:22:58 +0100 From: Harold Gutch To: Dru Nelson , freebsd-hackers@FreeBSD.ORG Subject: Re: sysctl for stack execute? References: <38A7224A.580D21BE@egroups.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <38A7224A.580D21BE@egroups.net>; from Dru Nelson on Sun, Feb 13, 2000 at 01:29:46PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 13, 2000 at 01:29:46PM -0800, Dru Nelson wrote: > > Is there a sysctl for FreeBSD which prevents execution in > the stack segment? (ie. to prevent attacks from getting root) > I'm using 3.4R. Atsuo Ohki sent a mail to -hackers on Feb 05 with a kernel-patch doing exactly this. The subject of the mail was "some guard against stack overflow attack". There were some problems with it though, like it breaking KLDs (read the reply by Matt Dillon). bye, Harold -- Someone should do a study to find out how many human life spans have been lost waiting for NT to reboot. Ken Deboy on Dec 24 1999 in comp.unix.bsd.freebsd.misc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 14:45: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns3.khmere.com (216-59-86-175.usa2.flashcom.net [216.59.86.175]) by builder.freebsd.org (Postfix) with ESMTP id 9654C43CA; Sun, 13 Feb 2000 14:44:52 -0800 (PST) Received: from khmere.com (IDENT:nathan@ns4.khmere.com [216.59.86.177]) by ns3.khmere.com (8.9.3/8.8.7) with ESMTP id OAA02106; Sun, 13 Feb 2000 14:45:04 -0800 (PST) Message-ID: <38A7344C.71BA918C@khmere.com> Date: Sun, 13 Feb 2000 14:46:37 -0800 From: nathan@khmere.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i586) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-net@FreeBSD.ORG" , "hackers@FreeBSD.ORG" Subject: Setting the default gw (with c) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings ! I have a question, I need to write a small program that sets the default gw. It is written in C and I have looked at several way to do it. One way is using ioctl but that way seems a little "old" and not very well documented. Here is a simple snippet of my code, now when I run it I get an error "error 22" invalid arg. Does anyone have experience with this and can point out what I am doing wrong ? I did have it to where it would work but the kernel never added my netmask to the routing table. So the route would kinda "hang" their and not do anything. I did tell it that it was being sent but..... also the flags never where set proper on the route (when doing route -dvn flush ) Any help would be great ! (oh if this looks familiar, I learned this from reading both ruote.c and netstat.c. ) struct rt_data_msg{ struct rt_msghdr add_rtm; union{ struct sockaddr sa; struct sockaddr_in sin; struct sockaddr_dl sdl; }rt_dst, rt_gate, rt_mask; }; int set_droute(char *gw){ int sockfd, i, err = 0; int flags = 0, r_addrs = 0; u_long inits; char t_gw[32]; register int l; struct rt_data_msg add_rt; pid_t pid; /* check to see if we have a gateway address or quit */ if(!gw){ ERR("set_droute: FREEBSD no route sent ! %d"); return(BAD); } else{ /* convet this address if not valid quit */ if((inet_aton(gw, &so_gate.sin.sin_addr)) < 0){ ERR("set_droute: FREEBSD route not valid ! %d"); return(BAD); } } memset(&add_rt, 0, sizeof(struct rt_data_msg)); /* check to see if thier is an existing route or not make an entry from scratch */ if( (i = get_droute(t_gw)) == BAD){ /* make the address and netmasks */ if((inet_aton("0.0.0.0", &add_rt.rt_mask.sin.sin_addr)) < 0){ err++; } if((inet_aton("0.0.0.0", &add_rt.rt_dst.sin.sin_addr)) < 0) { err++; } if((inet_aton(gw, &add_rt.rt_gate.sin.sin_addr)) < 0){ err++; } if(err > 0){ ERR("get_droute: FREEBSD cannot set mask or dst or gw invalid addresses %d"); return(BAD); } inits = RTV_EXPIRE; inits |= RTV_RPIPE; inits |= RTV_SPIPE; inits |= RTV_SSTHRESH; r_addrs = RTAX_DST; r_addrs |= RTAX_GATEWAY; r_addrs |= RTAX_NETMASK; flags = RTF_UP; flags |= RTF_GATEWAY; flags |= RTF_STATIC; flags |= RTF_PRCLONING; /* add thier size */ #define ADD_SIZE(w) l = ROUNDUP(w.sa.sa_len) #define ROUNDUP(a) ((a) > 0 ? (1 + (((a) - 1) | (sizeof(long) - 1))) : sizeof(long)); ADD_SIZE(add_rt.rt_dst); ADD_SIZE(add_rt.rt_gate); ADD_SIZE(add_rt.rt_mask); /* add their address family */ #define ADD_FAM(x) x.sin.sin_family = AF_INET; ADD_FAM(add_rt.rt_dst); ADD_FAM(add_rt.rt_gate); ADD_FAM(add_rt.rt_mask); ADD_FAM(add_rt.rt_genmask); /* set up all of the flags and tables */ #define RD add_rt.add_rtm RD.rtm_msglen = l; RD.rtm_version = RTM_VERSION; RD.rtm_type = RTM_ADD; RD.rtm_flags = flags; RD.rtm_addrs = rtm_addrs; RD.rtm_inits = RTF_GATEWAY; RD.rtm_pid = pid = getpid(); RD.rtm_seq = ++SEQ; if( (sockfd = socket(PF_ROUTE, SOCK_RAW, 0)) < 0){ ERR("set_droute: FREEBSD cannot open socket %d"); } /* send it to the kernel */ i = write(sockfd, (char *)&add_rt, l); syslog(LOG_ERR, "errno = %d ", errno); } else{ /* get a buffer for the data */ ERR("get_droute returned ok %d "); } return(GOOD); } Thank you nathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 15: 1: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by builder.freebsd.org (Postfix) with ESMTP id 5F94C4999; Sun, 13 Feb 2000 15:00:42 -0800 (PST) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.9.3) id SAA38192; Sun, 13 Feb 2000 18:05:55 -0500 (EST) (envelope-from cjc) Date: Sun, 13 Feb 2000 18:05:55 -0500 From: "Crist J. Clark" To: Jim Mercer Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: patches for de driver (full-duplex packet loss problems) Message-ID: <20000213180555.I31722@cc942873-a.ewndsr1.nj.home.com> Reply-To: cjclark@home.com References: <20000211155948.D13211@reptiles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000211155948.D13211@reptiles.org>; from jim@reptiles.org on Fri, Feb 11, 2000 at 03:59:49PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 11, 2000 at 03:59:49PM -0500, Jim Mercer wrote: > > i hear that there are some patches which might fix some serious packet loss > problems with the de driver in 100mbps fullduplex. > > i am running 3.4 (synced to stable via cvsup). > > with the mailing list archives down, i can't do my own search, but i was > hoping someone on these lists could give me some pointers. Try www.deja.com and search the muc.lists.freebsd.* hierarchy. Just one question I always ask people trying to get things working at full-duplex, is the card plugged into a hub at the other end? -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 17: 3: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by builder.freebsd.org (Postfix) with ESMTP id 6E59D3E1D for ; Sun, 13 Feb 2000 17:02:56 -0800 (PST) Received: from granite.hip.berkeley.edu (granite.hip.berkeley.edu [136.152.155.25]) by shale.csir.co.za (8.9.3/8.9.3) with ESMTP id DAA51125 for ; Mon, 14 Feb 2000 03:03:02 +0200 (SAT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by granite.hip.berkeley.edu (8.9.3/8.9.3) id RAA85373; Sun, 13 Feb 2000 17:01:09 -0800 (PST) (envelope-from reg) Date: Sun, 13 Feb 2000 17:01:09 -0800 From: Jeremy Lea To: "Jordan K. Hubbard" Cc: freebsd-hackers@freebsd.org Subject: Proposal for CD reorganisation for 4.0 Message-ID: <20000213170109.V60507@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was thinking (I know, I know, I shouldn't do that, it's bad for me ;)... Since we now have 3000+ ports, what are the chances of getting a special "FreeBSD Ports Distfiles" CD-ROM subscription set, which would just contain the distfiles? Since this set would be fairly low maintainance (just dump a copy of the FTP site onto CD :) it could be released at a low cost and with a fairly frequent update interval. I'm sure plenty of people would go for something which worked out to around $5 per month, including a lot of Linux people, since the CD would not have anything specific to FreeBSD on it. NetBSD and OpenBSD people should also be interested. This would also make the 4.0 set easier to get onto 4 disks, and it would do out of date slower (since the packages are prebuilt for that snapshot of -CURRENT). Another advantage is that we might be able to get rid of some NO_CDROMs, since the distfiles CD set would be around the cost of the media. Regards, -Jeremy -- | If I was not so weak, if I was not so cold, --+-- If I was not so scared of being broken, growing old, | I would be. I would be... frail. | - jars of clay / much afraid / frail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 18:19: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by builder.freebsd.org (Postfix) with ESMTP id 7203A3EA7 for ; Sun, 13 Feb 2000 18:19:00 -0800 (PST) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA23757; Sun, 13 Feb 2000 18:18:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Jeremy Lea Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Proposal for CD reorganisation for 4.0 In-reply-to: Your message of "Sun, 13 Feb 2000 17:01:09 PST." <20000213170109.V60507@shale.csir.co.za> Date: Sun, 13 Feb 2000 18:18:44 -0800 Message-ID: <23754.950494724@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's something we've been considering. :) > Hi, > > I was thinking (I know, I know, I shouldn't do that, it's bad for me > ;)... > > Since we now have 3000+ ports, what are the chances of getting a special > "FreeBSD Ports Distfiles" CD-ROM subscription set, which would just > contain the distfiles? Since this set would be fairly low maintainance > (just dump a copy of the FTP site onto CD :) it could be released at a > low cost and with a fairly frequent update interval. I'm sure plenty of > people would go for something which worked out to around $5 per month, > including a lot of Linux people, since the CD would not have anything > specific to FreeBSD on it. NetBSD and OpenBSD people should also be > interested. > > This would also make the 4.0 set easier to get onto 4 disks, and it > would do out of date slower (since the packages are prebuilt for that > snapshot of -CURRENT). > > Another advantage is that we might be able to get rid of some NO_CDROMs, > since the distfiles CD set would be around the cost of the media. > > Regards, > -Jeremy > > -- > | If I was not so weak, if I was not so cold, > --+-- If I was not so scared of being broken, growing old, > | I would be. I would be... frail. > | - jars of clay / much afraid / frail > > > 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 Feb 13 18:29:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by builder.freebsd.org (Postfix) with ESMTP id 4ADE449E8; Sun, 13 Feb 2000 18:29:06 -0800 (PST) Received: from localhost (1640 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Sun, 13 Feb 2000 21:29:15 -0500 (EST) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Sun, 13 Feb 2000 21:29:15 -0500 From: Jim Mercer To: cjclark@home.com Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: patches for de driver (full-duplex packet loss problems) Message-ID: <20000213212914.F700@reptiles.org> References: <20000211155948.D13211@reptiles.org> <20000213180555.I31722@cc942873-a.ewndsr1.nj.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000213180555.I31722@cc942873-a.ewndsr1.nj.home.com>; from cjc@cc942873-a.ewndsr1.nj.home.com on Sun, Feb 13, 2000 at 06:05:55PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 13, 2000 at 06:05:55PM -0500, Crist J. Clark wrote: > > with the mailing list archives down, i can't do my own search, but i was > > hoping someone on these lists could give me some pointers. > > Try www.deja.com and search the muc.lists.freebsd.* hierarchy. i'll poke about there. > Just one question I always ask people trying to get things working at > full-duplex, is the card plugged into a hub at the other end? actually, we started with cross over cables, and then suspecting them, tried jacking into a number of 10mbp and 10/100mbps hubs. still getting various problems (from high packet loss to not being able to sync up 100bps/fullduplex). -- [ Jim Mercer jim@reptiles.org +1 416 506-0654 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ 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 Sun Feb 13 19:45:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by builder.freebsd.org (Postfix) with ESMTP id 2A81548EC; Sun, 13 Feb 2000 19:45:25 -0800 (PST) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.9.3) id WAA38829; Sun, 13 Feb 2000 22:50:42 -0500 (EST) (envelope-from cjc) Date: Sun, 13 Feb 2000 22:50:42 -0500 From: "Crist J. Clark" To: Jim Mercer Cc: cjclark@home.com, freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: patches for de driver (full-duplex packet loss problems) Message-ID: <20000213225042.A38809@cc942873-a.ewndsr1.nj.home.com> Reply-To: cjclark@home.com References: <20000211155948.D13211@reptiles.org> <20000213180555.I31722@cc942873-a.ewndsr1.nj.home.com> <20000213212914.F700@reptiles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000213212914.F700@reptiles.org>; from jim@reptiles.org on Sun, Feb 13, 2000 at 09:29:15PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 13, 2000 at 09:29:15PM -0500, Jim Mercer wrote: > On Sun, Feb 13, 2000 at 06:05:55PM -0500, Crist J. Clark wrote: > > > with the mailing list archives down, i can't do my own search, but i was > > > hoping someone on these lists could give me some pointers. > > > > Try www.deja.com and search the muc.lists.freebsd.* hierarchy. > > i'll poke about there. > > > Just one question I always ask people trying to get things working at > > full-duplex, is the card plugged into a hub at the other end? > > actually, we started with cross over cables, and then suspecting them, tried > jacking into a number of 10mbp and 10/100mbps hubs. > > still getting various problems (from high packet loss to not being able to > sync up 100bps/fullduplex). You can't go full-duplex with a hub. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 20:56: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id B46023E29; Sun, 13 Feb 2000 20:56:01 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id UAA05352; Sun, 13 Feb 2000 20:56:06 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id UAA07151; Sun, 13 Feb 2000 20:56:06 -0800 Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id UAA16990; Sun, 13 Feb 2000 20:56:04 -0800 (PST) Message-ID: <38A78C64.A25639F6@softweyr.com> Date: Sun, 13 Feb 2000 22:02:28 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jim Mercer Cc: cjclark@home.com, freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: patches for de driver (full-duplex packet loss problems) References: <20000211155948.D13211@reptiles.org> <20000213180555.I31722@cc942873-a.ewndsr1.nj.home.com> <20000213212914.F700@reptiles.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Mercer wrote: > > On Sun, Feb 13, 2000 at 06:05:55PM -0500, Crist J. Clark wrote: > > > Just one question I always ask people trying to get things working at > > full-duplex, is the card plugged into a hub at the other end? > > actually, we started with cross over cables, and then suspecting them, tried > jacking into a number of 10mbp and 10/100mbps hubs. > > still getting various problems (from high packet loss to not being able to > sync up 100bps/fullduplex). Be warned that hubs don't play the full-duplex tune. You have have to use a crossover or a full-duplex switch. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 21:43:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.uni-bielefeld.de (mail.uni-bielefeld.de [129.70.4.90]) by builder.freebsd.org (Postfix) with ESMTP id 587E5496B for ; Sun, 13 Feb 2000 21:43:27 -0800 (PST) Received: from frolic.no-support.loc (ppp36-376.hrz.uni-bielefeld.de) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FPW002J8NWPZZ@mail.uni-bielefeld.de> for freebsd-hackers@FreeBSD.ORG; Mon, 14 Feb 2000 06:43:38 +0100 (MET) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id HAA00771 for freebsd-hackers@FreeBSD.ORG; Tue, 15 Feb 2000 07:28:36 +0100 (CET envelope-from bjoern) Date: Tue, 15 Feb 2000 07:28:36 +0100 From: Bjoern Fischer Subject: rpath and inter library deps To: freebsd-hackers@FreeBSD.ORG Message-id: <20000215072836.A746@frolic.no-support.loc> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have a problem with shared libraries that need a shared library by themselves (FreeBSD-3.4-STABLE): imagine a shared library `libfoo.so'. This library depends on the X11 lib and therefore has a `libX11.so.6' NEEDED entry. On this system `libX11.so.6' was installed into '/vol/X11/lib', so `libfoo.so' has also an RPATH of '/vol/X11/lib'. `libfoo.so' itself was installed into '/vol/foo/lib'. Now, I want to link a binary against `libfoo.so': My object code does NOT contain a reference to `libX11.so', so linking with '-L/vol/foo/lib -R/vol/foo/lib -lfoo' should be correct. But the linker fails to resolve the references of `libfoo.so' to libX11 unless I specify '-L/vol/X11/lib -R/vol/X11/lib'. I think this should be considered as a bug. Any other opinions? BTW, how does the FreeBSD runtime linker uses RPATHs it finds in shared libraries? Does it use an RPATH only for satisfying the needs of the library in which the RPATH was found, or are all RPATHs concatenated? Bj=F6rn Fischer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 22:56:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from milhouse.cnbinc.com (martin2.lnk.telstra.net [139.130.137.91]) by builder.freebsd.org (Postfix) with ESMTP id 1266D4024 for ; Sun, 13 Feb 2000 22:56:22 -0800 (PST) Received: from bender (bender.cnbinc.com [203.38.182.20]) by milhouse.cnbinc.com (8.9.3/8.9.3) with SMTP id RAA30044; Mon, 14 Feb 2000 17:23:27 +1030 (CST) (envelope-from diskiller@cnbinc.com) Message-ID: <001b01bf76b8$30813f60$14b626cb@bender.cnbinc.com> From: "Martin Minkus" To: "Jeremy Lea" Cc: References: <20000213170109.V60507@shale.csir.co.za> Subject: Re: Proposal for CD reorganisation for 4.0 Date: Mon, 14 Feb 2000 17:23:24 +1030 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.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I was thinking (I know, I know, I shouldn't do that, it's bad for me > ;)... > > Since we now have 3000+ ports, what are the chances of getting a special > "FreeBSD Ports Distfiles" CD-ROM subscription set, which would just > contain the distfiles? Since this set would be fairly low maintainance > (just dump a copy of the FTP site onto CD :) it could be released at a > low cost and with a fairly frequent update interval. I'm sure plenty of > people would go for something which worked out to around $5 per month, > including a lot of Linux people, since the CD would not have anything > specific to FreeBSD on it. NetBSD and OpenBSD people should also be > interested. > > This would also make the 4.0 set easier to get onto 4 disks, and it > would do out of date slower (since the packages are prebuilt for that > snapshot of -CURRENT). > > Another advantage is that we might be able to get rid of some NO_CDROMs, > since the distfiles CD set would be around the cost of the media. Personally, i think thats a pretty good idea! I pay per meg i recieve (dedicated internet with static IPs isn't cheat in australia :(( ) so, i have a subscription order from walnut creek, so i have everything on CDs rather then paying for downloads all the time. What annoys me, is, 1) FBSD releases are probably a little "tooo" often. 2) Port Distfiles/Binary Packages start getting old on the CDs too fast And lately (with 3.4-Release, which *REALLY* annoyed me); 3) Most of the ports distfiles are MISSING on the 4 cd set. Probably because there is just not enough space with so many ports now adays. All the binary package's appear to be there. So. If we create a ports distfiles distribution, it could be released montly, and use 2cds ? (or 4cd, and include all the binary packages too ?) It could also be useful for Linux, and Hurd, and so on, and contain just the FreeBSD ports distfliles. (And still have the FreeBSD name on it ? Unless walnut creek just creates it as a source distribution CD) FBSD releases wouldn't have to be quite so often. It could be 2 cd's (i386 base OS and some common packages, and alpha base OS with some common alpha packages). or 4 cds, with all the binary packages, like we're doing now, minus the distfiles (which most of the important ones are missing anyway!) Well, thats my contribution. Martin. -- diskiller@cnbinc.com Linux/FreeBSD hacker Please use PGP: http://www.diskiller.net/pgp.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 13 23:56:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from akira.lanfear.com (akira.lanfear.com [208.12.10.34]) by builder.freebsd.org (Postfix) with ESMTP id 489853ED5 for ; Sun, 13 Feb 2000 23:56:26 -0800 (PST) Received: from katana (katana.lanfear.com [10.0.0.3]) by akira.lanfear.com (8.9.3/8.9.3) with SMTP id XAA38113 for ; Sun, 13 Feb 2000 23:56:40 -0800 (PST) (envelope-from marcw@lanfear.com) From: "Marc Wandschneider" To: Subject: Loadable Code Modules? Date: Sun, 13 Feb 2000 23:57:48 -0800 Message-ID: <003901bf76c1$302107e0$0300000a@katana> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG howdy! i was wondering if FreeBSD had a kind of like DLL capability? i'd like to be able to do something as follows: // ... construct char *fileName moduleHandle = loadCodeModule(fileName); (char *)(*fn char *) myfn; // ii'm pretty sure i screwed that up myfn = getFunctionAddress(moduleHandle, "doSomethignCool"); // use fn releaseModule(moduleHandle); does such a thing exist in FreeBSD? If not, where would one start looking to add such functionality? thanks. marc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 0: 6:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.calldei.com (adsl-208-191-146-189.dsl.hstntx.swbell.net [208.191.146.189]) by builder.freebsd.org (Postfix) with ESMTP id 9359141B6 for ; Mon, 14 Feb 2000 00:06:27 -0800 (PST) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id CAA04175; Mon, 14 Feb 2000 02:08:11 -0600 (CST) (envelope-from chris) Date: Mon, 14 Feb 2000 02:08:09 -0600 From: Chris Costello To: Marc Wandschneider Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Loadable Code Modules? Message-ID: <20000214020809.A685@holly.calldei.com> Reply-To: chris@calldei.com References: <003901bf76c1$302107e0$0300000a@katana> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i In-Reply-To: <003901bf76c1$302107e0$0300000a@katana> X-URL: http://www.FreeBSD.org/~chris/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, February 13, 2000, Marc Wandschneider wrote: > i was wondering if FreeBSD had a kind of like DLL capability? Yes, try ``man 3 dlopen''. -- |Chris Costello |The programmer's national anthem is 'AAAAAAAAHHHHHHHH'. -Weinberg, p.152 `------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 0:10: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by builder.freebsd.org (Postfix) with ESMTP id 0C4DA4632 for ; Mon, 14 Feb 2000 00:10:00 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id DAA20672; Mon, 14 Feb 2000 03:09:44 -0500 Date: Mon, 14 Feb 2000 03:09:44 -0500 (EST) From: Mike Nowlin To: Marc Wandschneider Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Loadable Code Modules? In-Reply-To: <003901bf76c1$302107e0$0300000a@katana> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > i was wondering if FreeBSD had a kind of like DLL capability? > > i'd like to be able to do something as follows: > > // ... construct char *fileName > moduleHandle = loadCodeModule(fileName); > (char *)(*fn char *) myfn; // ii'm pretty sure i screwed that up > myfn = getFunctionAddress(moduleHandle, "doSomethignCool"); > // use fn > releaseModule(moduleHandle); First, a friendly smack for using a WinDoze term (DLL).... "Thwack!" Second, an answer. Yes, they are supported... Take a look at the man page for "dlopen". I just had a need to (finally) use dynamically loadable objects in a program, and they're pretty easy to implement. (The "dlopen" and related functions apply to most modern UNIX variants.) --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 0:33:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by builder.freebsd.org (Postfix) with ESMTP id E082D40C2 for ; Mon, 14 Feb 2000 00:33:19 -0800 (PST) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id JAA83504; Mon, 14 Feb 2000 09:32:56 +0100 (CET) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id JAA00586; Mon, 14 Feb 2000 09:32:31 +0100 (CET) (envelope-from root@nihil.plaut.de) Date: Mon, 14 Feb 2000 09:32:30 +0100 (CET) From: Michael Reifenberger To: Marc Wandschneider Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Loadable Code Modules? In-Reply-To: <003901bf76c1$302107e0$0300000a@katana> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 13 Feb 2000, Marc Wandschneider wrote: ... > i was wondering if FreeBSD had a kind of like DLL capability? Yes. man dlopen(3) Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 0:40:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by builder.freebsd.org (Postfix) with ESMTP id D8E803FB4; Mon, 14 Feb 2000 00:40:41 -0800 (PST) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id AAA55228; Mon, 14 Feb 2000 00:40:56 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 14 Feb 2000 00:40:55 -0800 (PST) From: Kris Kennaway To: Egervary Gergely Cc: hackers@freebsd.org Subject: Re: accounting, ppp In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 12 Feb 2000, Egervary Gergely wrote: > I'm running a PPP dialup server. (mgetty-autoppp) Is there any way to do > login accounting (like solaris' PAM modules, or linux pam_limits.so) A FreeBSD PAM module? ;) We use the same PAM code as linux, so grab the source of the module you use under linux and compile it on FreeBSD. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 1:38:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from galileo.poli.hu (polinet-gw.poli.hu [195.199.8.25]) by builder.freebsd.org (Postfix) with ESMTP id 8ED133E78; Mon, 14 Feb 2000 01:37:46 -0800 (PST) Received: from faber.poli.hu ([195.199.8.29] ident=mail) by galileo.poli.hu with esmtp (Exim 3.12 #1) id 12KHwg-000BOb-00; Mon, 14 Feb 2000 10:37:30 +0100 Received: from mauzi (helo=localhost) by faber.poli.hu with local-esmtp (Exim 3.12 #1 (Debian)) id 12KHwh-0007Rf-00; Mon, 14 Feb 2000 10:37:31 +0100 Date: Mon, 14 Feb 2000 10:37:31 +0100 (CET) From: Egervary Gergely To: Kris Kennaway Cc: Egervary Gergely , hackers@freebsd.org Subject: Re: accounting, ppp In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm running a PPP dialup server. (mgetty-autoppp) Is there any way to do > > login accounting (like solaris' PAM modules, or linux pam_limits.so) > > A FreeBSD PAM module? ;) > > We use the same PAM code as linux, so grab the source of the module you > use under linux and compile it on FreeBSD. btw. I can't get time accounting to work. I've done accton /var/account/acct, I can query informations with `sa' but I can't do any restrictions in login.conf -- :accounted:\ :sessionlimit=1: and login still let me log in more than once. any ideas? step-by-step docs? URL? -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 3: 5: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by builder.freebsd.org (Postfix) with ESMTP id BA1A03ED7; Mon, 14 Feb 2000 03:04:56 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id RAA20135; Mon, 14 Feb 2000 17:02:13 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Mon, 14 Feb 2000 17:02:12 +0600 (NS) From: Max Khon To: Egervary Gergely Cc: Kris Kennaway , hackers@FreeBSD.ORG Subject: Re: accounting, ppp In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Mon, 14 Feb 2000, Egervary Gergely wrote: > > > I'm running a PPP dialup server. (mgetty-autoppp) Is there any way to do > > > login accounting (like solaris' PAM modules, or linux pam_limits.so) > > > > A FreeBSD PAM module? ;) > > > > We use the same PAM code as linux, so grab the source of the module you > > use under linux and compile it on FreeBSD. > > btw. I can't get time accounting to work. > > I've done accton /var/account/acct, I can query informations with `sa' > but I can't do any restrictions in login.conf -- > :accounted:\ > :sessionlimit=1: > and login still let me log in more than once. both login and pam_unix.so do not have accounting capabilities /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 3:19:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by builder.freebsd.org (Postfix) with ESMTP id CE54C3DE4 for ; Mon, 14 Feb 2000 03:19:13 -0800 (PST) Received: by mimer.webgiro.com (Postfix, from userid 66) id 556BD2DC07; Mon, 14 Feb 2000 12:18:39 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 0D1377811; Mon, 14 Feb 2000 12:18:19 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 0900D10E12 for ; Mon, 14 Feb 2000 12:18:19 +0100 (CET) Date: Mon, 14 Feb 2000 12:18:18 +0100 (CET) From: Andrzej Bialecki To: freebsd-hackers@freebsd.org Subject: SPY 1.0 released Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The new version of SPY - a kernel module for monitoring syscalls - is available for download from: http://www.freebsd.org/~abial/spy/ Please read the README.txt supplied with the package. This module has been tested only with FreeBSD 4.0 - it may require some minor changes to work with other releases. Summary of changes from the previous version: * each syscall can be intercepted, and either monitored (with adjustable level of details) or disabled based on process credentials * setting of per-syscall monitoring/disable options has been implemented * options now have symbolic names, rather than being binary masks. * sysctl tunables now reside under kern.spy.* instead of creating their own root category. * a manpage - thank to Sheldon Hearn, who provided manified version of README included in previous release - it was a good skeleton for the new manpage. As usually, comments and suggestions are welcome. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 4: 0:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ab-bg.net (ab-bg.net [212.56.11.129]) by builder.freebsd.org (Postfix) with SMTP id 5CC2A3D30 for ; Mon, 14 Feb 2000 04:00:21 -0800 (PST) Received: (qmail 3972 invoked by uid 1000); 14 Feb 2000 11:58:54 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 14 Feb 2000 11:58:54 -0000 Date: Mon, 14 Feb 2000 13:58:54 +0200 (EET) From: Victor Ivanov To: freebsd-hackers@freebsd.org Subject: Re: Loadable Code Modules? In-Reply-To: <003901bf76c1$302107e0$0300000a@katana> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dlopen(3): #include void *dlopen(const char *path, int mode); void *dlsym(void *handle, const char *symbol); ... void *dll_handle; char (*my_func)(char *); // me too :) dll_handle = dlopen("/my/tests/something.so", RTLD_NOW); my_func = dlsym(dll_handle, "my_func"); ... something.so should be compiled with the -shared option: cc -shared -o something.so something.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 5: 9:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from galileo.poli.hu (polinet-gw.poli.hu [195.199.8.25]) by builder.freebsd.org (Postfix) with ESMTP id A43613D81; Mon, 14 Feb 2000 05:09:24 -0800 (PST) Received: from faber.poli.hu ([195.199.8.29] ident=mail) by galileo.poli.hu with esmtp (Exim 3.12 #1) id 12KL8T-000BWp-00; Mon, 14 Feb 2000 14:01:53 +0100 Received: from mauzi (helo=localhost) by faber.poli.hu with local-esmtp (Exim 3.12 #1 (Debian)) id 12KL8W-0007YM-00; Mon, 14 Feb 2000 14:01:56 +0100 Date: Mon, 14 Feb 2000 14:01:56 +0100 (CET) From: Egervary Gergely To: Max Khon Cc: Kris Kennaway , hackers@FreeBSD.ORG Subject: Re: accounting, ppp In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > :accounted:\ > > :sessionlimit=1: > > and login still let me log in more than once. > > both login and pam_unix.so do not have accounting capabilities ok, well - I've seen the sources. anyway, what has accounting capabilities, and what are the plans about it? -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 6: 0:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from www.geocrawler.com (sourceforge.net [198.186.203.33]) by builder.freebsd.org (Postfix) with ESMTP id C2500425C for ; Mon, 14 Feb 2000 06:00:13 -0800 (PST) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id GAA29194; Mon, 14 Feb 2000 06:00:21 -0800 Date: Mon, 14 Feb 2000 06:00:21 -0800 Message-Id: <200002141400.GAA29194@www.geocrawler.com> To: freebsd-hackers@freebsd.org Subject: Help me understand dlopen/dlsy From: "Pradesh Chanderpaul" Reply-To: "Pradesh Chanderpaul" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message was sent from Geocrawler.com by "Pradesh Chanderpaul" Be sure to reply to that address. Hello All I know that this question is more suited to the general questions mailing group, but I tried, and failed to obtain a response. So could someone please provide guidance with this topic. I have searched the mailing lists, man pages and the net at large without getting a satisfactory understanding. Consider the following scenario. I need to compile a program consisting of two source files and a makefile file1.c ------- #include #include #include int main() { void *handle; void (*myhellofunc)(void); char *c; handle = dlopen(NULL, 1); c = dlerror(); if (c) abort_with_error(c); myhellofunc = dlsym(handle, "_helloworld"); c = dlerror(); if(c) abort_with_error(c); myhellofunc(); dlclose(handle); } file2.c ------- #include void helloworld(void) { printf(" Hello cruel worldn"); } Makefile -------- file1.o : file1.c gcc -fPIC -c file1.c file1.o : file1.c gcc -fPIC -c file1.c fileit : file1.o file2.o cc -export-dynamic -o fileit file1.o file2.o The two source files will be linked into a single executable, using GCC running on FreeBSD 3.2-RELEASE. Q1 : Are my flags sufficient to compile the individual source files? Q2 : What flags are required to link the object files into the single executable? Q3 : Is there anything else I should be wary of? I have tried various options (like using -rdynamic and -shared but to no avail. dlerror() reports an undefined symbol for _helloworld from calling dlsym. This issue has been "bugging" me for weeks now, so I need to try and get it sorted out. Please assist if you can. Thanking you in advance. Pradesh Chanderpaul Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 7:44:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ppp142080.asahi-net.or.jp (ppp142080.asahi-net.or.jp [202.213.142.80]) by builder.freebsd.org (Postfix) with ESMTP id 0084E3ECB; Mon, 14 Feb 2000 07:44:03 -0800 (PST) Received: from localhost (localhost.tf.or.jp [127.0.0.1]) by galois.tf.or.jp (8.9.3/3.7W-Teddy-99050304) with ESMTP id AAA12908; Tue, 15 Feb 2000 00:40:54 +0900 (JST) To: mauzi@faber.poli.hu Cc: kris@freebsd.org, hackers@freebsd.org Subject: Re: accounting, ppp From: Tetsuro Teddy FURUYA (=?iso-2022-jp?B?GyRCOEVDKxsoQiAbJEJFL086GyhC?=) In-Reply-To: Your message of "Mon, 14 Feb 2000 10:37:31 +0100 (CET)" References: X-Mailer: Mew version 1.93 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000215004054I.tfuruya@galois.tf.or.jp> Date: Tue, 15 Feb 2000 00:40:54 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, From: Egervary Gergely Subject: Re: accounting, ppp Date: Mon, 14 Feb 2000 10:37:31 +0100 (CET) mauzi> > > I'm running a PPP dialup server. (mgetty-autoppp) Is there any way to do mauzi> > > login accounting (like solaris' PAM modules, or linux pam_limits.so) mauzi> > mauzi> > A FreeBSD PAM module? ;) Did you see, `man 1 last` ? Here is a sample output list of last. tf051005.tf.or.jp is my ppp dial-up client. dhcp100.tf.or.jp is my dhcp client. tfuruya ttyp1 chba1132.ppp.inf Fri Dec 31 23:50 - 00:27 (00:36) dialout cuaa0 Fri Dec 31 23:45 - 00:18 (00:33) dialout cuaa0 Fri Dec 31 22:50 - 22:55 (00:05) tfuruya ftp tf051005.tf.or.j Fri Dec 31 21:07 - 21:22 (00:15) tfuruya ttyp1 tf051005.tf.or.j Fri Dec 31 21:05 - 21:12 (00:07) tfuruya cuaa0 Fri Dec 31 21:02 - 21:13 (00:10) dialout cuaa0 Fri Feb 11 16:20 - 16:24 (00:04) tfuruya ttyp1 dhcp100.tf.or.jp Fri Feb 11 13:02 - 15:19 (02:17) tfuruya ttyp2 localhost.tf.or. Fri Feb 11 12:55 - 12:55 (00:00) last uses /var/log/wtmp. Or, you cat get ppp information from /var/log/ppp.log directly. And from /var/db/dhcpd.leases for dhcp. ------------------------------------------------ Tetsuro Teddy Furuya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 7:52:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from galileo.poli.hu (polinet-gw.poli.hu [195.199.8.25]) by builder.freebsd.org (Postfix) with ESMTP id D430B4381; Mon, 14 Feb 2000 07:52:04 -0800 (PST) Received: from faber.poli.hu ([195.199.8.29] ident=mail) by galileo.poli.hu with esmtp (Exim 3.12 #1) id 12KNkz-0000R6-00; Mon, 14 Feb 2000 16:49:49 +0100 Received: from mauzi (helo=localhost) by faber.poli.hu with local-esmtp (Exim 3.12 #1 (Debian)) id 12KNky-0007im-00; Mon, 14 Feb 2000 16:49:48 +0100 Date: Mon, 14 Feb 2000 16:49:48 +0100 (CET) From: Egervary Gergely To: Tetsuro Teddy FURUYA Cc: kris@freebsd.org, hackers@freebsd.org Subject: Re: accounting, ppp In-Reply-To: <20000215004054I.tfuruya@galois.tf.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Did you see, `man 1 last` ? > Here is a sample output list of last. > tf051005.tf.or.jp is my ppp dial-up client. > dhcp100.tf.or.jp is my dhcp client. of course accounting means more than just getting information ;)) eg. limiting, etc ;) -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 8:27:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69]) by builder.freebsd.org (Postfix) with ESMTP id A2577462E; Mon, 14 Feb 2000 08:27:16 -0800 (PST) Received: from gab200r1.ems.att.com ([135.37.94.32]) by kcmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id LAA00272; Mon, 14 Feb 2000 11:27:28 -0500 (EST) Received: from njb140bh2.ems.att.com by gab200r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id LAA13668; Mon, 14 Feb 2000 11:28:28 -0500 (EST) Received: by njb140bh2.ems.att.com with Internet Mail Service (5.5.2448.0) id <1YQRVA2H>; Mon, 14 Feb 2000 11:27:27 -0500 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'freebsd-hackers@freebsd.org'" Cc: "'freebsd-current@freebsd.org'" Subject: raw socket, bpf, netgraph, etc Date: Mon, 14 Feb 2000 10:46:19 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="koi8-r" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, Is it possible to get access to link layer (AF_LINK) via raw socket? kind of Linux SOCK_PACKET. It seems to me that it is not. (hope I wrong :) I can access raw IP via socket(AF_INET, SOCK_RAW, IPPROTO_RAW) and event get access to IP header with setsockopt. But not AF_LINK :( On the other hand is bpf. but here is the small problem. i have interface with bpf attached to it. when i write to /dev/bpf i got the same packet back. kind of loop. the only solution is to filter these packets. but there is no way to find out which packet i wrote, and which is received from outside. i was thinking about netgraph. would't it be nice to have netgraph interface in each network driver? Any ideas? Thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 8:52:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thunk.crazylogic.net (thunk.crazylogic.net [199.45.111.154]) by builder.freebsd.org (Postfix) with ESMTP id 7A6484309 for ; Mon, 14 Feb 2000 08:52:24 -0800 (PST) Received: from localhost (matt@localhost) by thunk.crazylogic.net (8.9.3/8.9.3) with ESMTP id LAA92412 for ; Mon, 14 Feb 2000 11:43:49 -0500 (EST) (envelope-from matt@crazylogic.net) Date: Mon, 14 Feb 2000 11:43:49 -0500 (EST) From: Matt Gostick To: hackers@freebsd.org Subject: set mtu on le0? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm having a hard time setting the mtu on some of my cards. They are DEC 205's. They work fine... but I have to set the mtu to 1492 so adsl works. su-2.03# ifconfig le0 mtu 1492 ifconfig: ioctl (set mtu): Invalid argument su-2.03# ifconfig le0 le0: flags=8843 mtu 1500 inet 192.168.0.3 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:00:f8:51:63:17 I took a look at /usr/src/sys/i386/isa/if_le.c and changed where it set ifp->if_mtu = ETHERMTU; to 1492 instead (then recompiled)... it didn't have any effect. Any ideas? Thanks. -- Matt Gostick http://www.crazylogic.net/~matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 9:37:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by builder.freebsd.org (Postfix) with SMTP id DDAAE4C79 for ; Mon, 14 Feb 2000 09:37:47 -0800 (PST) Received: from grubby.research.bell-labs.com ([135.104.2.9]) by crufty; Mon Feb 14 12:19:07 EST 2000 Received: from aura.research.bell-labs.com ([135.104.46.10]) by grubby; Mon Feb 14 12:19:06 EST 2000 Received: (from ozden@localhost) by aura.research.bell-labs.com (8.9.1/8.9.1) id MAA18497 for freebsd-hackers@freebsd.org; Mon, 14 Feb 2000 12:19:02 -0500 (EST) Message-Id: <200002141719.MAA18497@aura.research.bell-labs.com> From: ozden@research.bell-labs.com (Banu Ozden) Date: Mon, 14 Feb 2000 12:19:02 -0500 X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: freebsd-hackers@freebsd.org Subject: scsi target mode Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG we're trying to figure out how to setup a scsi adapter to function as a target device, and would appreciate some help from anyone who knows how to do it. we've looked at the code (scsi_target.c, scsi_targ_bh.c) and man pages (man scsi), but we're still not clear on the following: a. settings on the controller card (e.g. scsi id, termination) b. freebsd configuration on the initiator and target PCs. (e.g. do we use scsi_pt.c, scsi_target.c, etc). here's a diagram depicting what we want to do. we're trying to setup a PC (PC2 below) with an adaptec controller to act as an emulated disk. PC 1 will access the disks on PC 2. ______________ ______________________________ | PC1 | scsi cable | PC2 scsi bus | | adaptec 2940 | ================= | adaptec 2940 ======== disk | | SCSI ID=7 | | SCSI ID=0 SCSI ID=5 | |______________| |______________________________| thanks wee teck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 9:43:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by builder.freebsd.org (Postfix) with ESMTP id 1D4924C75; Mon, 14 Feb 2000 09:43:20 -0800 (PST) Received: from localhost (lloyd@localhost) by brunel.uk1.vbc.net (8.9.3/8.9.3) with ESMTP id RAA40840; Mon, 14 Feb 2000 17:43:36 GMT Date: Mon, 14 Feb 2000 17:43:36 +0000 (GMT) From: Lloyd Rennie To: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: GateD returns 'No buffer space available' upon a routing table build... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey all; We have several routers storing a full global routing table. Recently, this table has grown rather large (currently at ~75k routes). All are behaving in the same way; When GateD starts, I can watch it growing on a 'top', as it builds a routing table. Suddenly, it stops growing, cpu usage drops to nill, and many kernel messages are spewed-out; Feb 14 13:47:34 gate3 /kernel: arp_rtrequest: malloc failed Feb 14 13:47:34 gate3 /kernel: arplookup 194.207.0.32 failed: could not allocate llinfo Feb 14 13:47:34 gate3 /kernel: arpresolve: can't allocate llinfo for 194.207.0.32rt Feb 14 13:47:34 gate3 gated[88]: KRT SENT type ADD(1)flags UP GW(3) error 55: Nobuffer space available Feb 14 13:47:34 gate3 gated[88]: KRT SENT dest 204.0.41 gateway 194.207.0.46 netmask 255.255.255 Feb 14 13:47:37 gate3 /kernel: arplookup 194.207.0.32 failed: could not allocate llinfo etc... The first symptom seems always to be the malloc failure. This happens within the first minute of uptime on this particular machine, a p2-400/128Mb. All machines run FreeBSD-3.2. The others take longer to develop the fault, but have slower processors. My assumption is that the global routing table has grown to such a size that there is no longer enough kernel memory available to store it. I checked through the LINT file, but couldn't find any useful options. Started looking tentatively through the kernel source, but (bear in mind I'd rather not lower maxusers anymore) came to a dead end with a 0-byte file called vm_opt.h :( So I'd like to ask... * Which particular type of 'buffer space' is this? * What can I do to 'tweak' it (ie. assign more) * Is the issue resolved in a later release of FreeBSD (pref in the STABLE tree, which reminds me - when's the codefreeze on v4 end?) Any help with this issue would be appreciated... -- Lloyd Rennie VBCnet GB Ltd lloyd@vbc.net tel +44 (0) 117 929 1316 http://www.vbc.net fax +44 (0) 117 927 2015 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 10:33:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by builder.freebsd.org (Postfix) with ESMTP id 70FD33E12; Mon, 14 Feb 2000 10:33:49 -0800 (PST) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.2) id KAA05390; Mon, 14 Feb 2000 10:33:47 -0800 (PST) From: Archie Cobbs Message-Id: <200002141833.KAA05390@bubba.whistle.com> Subject: Re: raw socket, bpf, netgraph, etc In-Reply-To: from "Yevmenkin, Maksim N, CSCIO" at "Feb 14, 2000 10:46:19 am" To: myevmenkin@att.com (Yevmenkin Maksim N CSCIO) Date: Mon, 14 Feb 2000 10:33:47 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG ('freebsd-hackers@freebsd.org'), freebsd-current@FreeBSD.ORG ('freebsd-current@freebsd.org') X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yevmenkin, Maksim N, CSCIO writes: > i was thinking about netgraph. would't it be nice to have netgraph interface > in each network driver? You already do. See ng_ether(8). Compile your kernel with options NETGRAPH and then each Ethernet interface is a netgraph node. Take control of it by connecting to the "divert" hook. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 11:53:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 1D2AE3EC8; Mon, 14 Feb 2000 11:53:07 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA11486; Mon, 14 Feb 2000 11:53:07 -0800 (PST) (envelope-from dillon) Date: Mon, 14 Feb 2000 11:53:07 -0800 (PST) From: Matthew Dillon Message-Id: <200002141953.LAA11486@apollo.backplane.com> To: Lloyd Rennie Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: GateD returns 'No buffer space available' upon a routing table build... References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :etc... : :The first symptom seems always to be the malloc failure. This happens :within the first minute of uptime on this particular machine, a :p2-400/128Mb. All machines run FreeBSD-3.2. The others take longer to :develop the fault, but have slower processors. 'vmstat -m' before, during, and after the gated startup. You are probably running into the malloc pool KVM limit. -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 Feb 14 12: 0:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id 333353DD1 for ; Mon, 14 Feb 2000 12:00:18 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id MAA23987; Mon, 14 Feb 2000 12:27:01 -0800 (PST) Date: Mon, 14 Feb 2000 12:27:01 -0800 From: Alfred Perlstein To: Pradesh Chanderpaul Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Help me understand dlopen/dlsy Message-ID: <20000214122701.U17536@fw.wintelcom.net> References: <200002141400.GAA29194@www.geocrawler.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002141400.GAA29194@www.geocrawler.com>; from archiver@db.geocrawler.com on Mon, Feb 14, 2000 at 06:00:21AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Pradesh Chanderpaul [000214 06:33] wrote: > This message was sent from Geocrawler.com by "Pradesh Chanderpaul" > Be sure to reply to that address. > > Hello All > > I know that this question is more suited to the general > questions mailing group, but I tried, and failed to obtain > a response. So could someone please provide guidance with this > topic. I have searched the mailing lists, man pages and the > net at large without getting a satisfactory understanding. > > Consider the following scenario. > > I need to compile a program consisting of two source files > and a makefile > > file1.c > ------- > #include > #include > #include > > int main() { > void *handle; > void (*myhellofunc)(void); > char *c; > > handle = dlopen(NULL, 1); > c = dlerror(); > > if (c) abort_with_error(c); > > myhellofunc = dlsym(handle, "_helloworld"); try "helloworld" (drop the '_') -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 13:51:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by builder.freebsd.org (Postfix) with SMTP id 8D0684BB1; Mon, 14 Feb 2000 13:50:41 -0800 (PST) Date: Mon, 14 Feb 2000 21:50:59 +0000 From: David Malone To: Archie Cobbs Cc: myevmenkin@att.com, freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: raw socket, bpf, netgraph, etc Message-ID: <20000214215059.A34982@salmon.maths.tcd.ie> References: <200002141833.KAA05390@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002141833.KAA05390@bubba.whistle.com>; from archie@whistle.com on Mon, Feb 14, 2000 at 10:33:47AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 14, 2000 at 10:33:47AM -0800, Archie Cobbs wrote: > Yevmenkin, Maksim N, CSCIO writes: > > i was thinking about netgraph. would't it be nice to have netgraph interface > > in each network driver? > > You already do. See ng_ether(8). > > Compile your kernel with options NETGRAPH and then each Ethernet > interface is a netgraph node. Take control of it by connecting > to the "divert" hook. I was trying to figure out if it is possible to route stuff out on a particular interface based on source address using netgraph. At the moment we have an NFS server which pretends to be two machines on the same subnet. To get this to work we're using a small hack in the ipfw divert code. I looked at the netgraph man pages and reckoned it might be possible to do somthing like: fxp0 / ng0 -> bpf \ fxp1 then ifconfig ng0 up with both IP addresses and use the bpf to determine which ethernet card to transmit it on. However, I don't think this will work. First 'cos arp stuff will probably be broken and second because ng0 is a point to point device and won't correctly encapsulate packets for ethernet. Am I correct in thinking that this isn't currently possible with the net graph nodes currently available? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 14: 7:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by builder.freebsd.org (Postfix) with ESMTP id 733D04C8E; Mon, 14 Feb 2000 14:07:11 -0800 (PST) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.2) id OAA66836; Mon, 14 Feb 2000 14:07:14 -0800 (PST) From: Archie Cobbs Message-Id: <200002142207.OAA66836@bubba.whistle.com> Subject: Re: raw socket, bpf, netgraph, etc In-Reply-To: <20000214215059.A34982@salmon.maths.tcd.ie> from David Malone at "Feb 14, 2000 09:50:59 pm" To: dwmalone@maths.tcd.ie (David Malone) Date: Mon, 14 Feb 2000 14:07:14 -0800 (PST) Cc: archie@whistle.com (Archie Cobbs), myevmenkin@att.com, freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone writes: > > Compile your kernel with options NETGRAPH and then each Ethernet > > interface is a netgraph node. Take control of it by connecting > > to the "divert" hook. > > I was trying to figure out if it is possible to route stuff out on > a particular interface based on source address using netgraph. At > the moment we have an NFS server which pretends to be two machines > on the same subnet. To get this to work we're using a small hack > in the ipfw divert code. I looked at the netgraph man pages and > reckoned it might be possible to do somthing like: > > fxp0 > / > ng0 -> bpf > \ > fxp1 > > then ifconfig ng0 up with both IP addresses and use the bpf to > determine which ethernet card to transmit it on. However, I don't > think this will work. First 'cos arp stuff will probably be broken > and second because ng0 is a point to point device and won't correctly > encapsulate packets for ethernet. You're right that that won't work .. you'd be sending raw IP frames on the wire without 14 byte Ethernet headers. > Am I correct in thinking that this isn't currently possible with the > net graph nodes currently available? I think so.. you would have to write a new new node type to add/strip the headers at least. That brings up a good point though.. the ng_iface(8) node type should allow it to configured as a non-point-to-point interface. Ah.. just looked at if_tun.c which does this.. it's trivial. I'll probably check something in after 4.0 then. But even with that change you'd need an add/strip headers thing. In fact, that's another node type I want to write.. just a simple thing that adds & strips headers off packets... or this could be folded into the BPF node type (a BPF program returns a length, after all). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 14:25:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by builder.freebsd.org (Postfix) with ESMTP id 575FB43DB for ; Mon, 14 Feb 2000 14:25:28 -0800 (PST) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id QAA00274 for hackers@freebsd.org; Mon, 14 Feb 2000 16:25:33 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <200002142225.QAA00274@celery.dragondata.com> Subject: Off by one error in ulimit? To: hackers@freebsd.org Date: Mon, 14 Feb 2000 16:25:33 -0600 (CST) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't have access to a -current machine to try this on, so this only applies to 3.4. I have my ulimit set to 8MB for data/etc: ulimit -a core file size (blocks) 8192 data seg size (kbytes) 8192 file size (blocks) 8192 max locked memory (kbytes) 4096 max memory size (kbytes) 8192 open files 24 pipe size (512 bytes) 1 stack size (kbytes) 2048 cpu time (seconds) 5400 max user processes 32 virtual memory (kbytes) 8192 I have a program that starts to attempt mallocing 8MB, and decreasing the malloc size by 1 byte every time malloc fails. I end up with a value somewhere between 7 and 8MB when malloc succeeds, which is fine. However, when I actually use this malloc'ed region, I segv when I touch the very last page. Can anyone explain this? :) As long as my malloc doesn't bump into the ulimit, everything works fine. Either malloc() doesn't take into account a fencepost situation somewhere, or I'm losing my mind. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 14:44:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by builder.freebsd.org (Postfix) with ESMTP id 14BD14B44 for ; Mon, 14 Feb 2000 14:37:07 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id RAA15645 for ; Mon, 14 Feb 2000 17:38:18 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Mon, 14 Feb 2000 17:38:18 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: freebsd-hackers@freebsd.org Subject: uthread: setsockopt while other threads blocked? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using a threaded program to manage ipfw rules, and today discovered the hardware that you cannot simultaneously have a thread blocking on a recvfrom() on the raw socket to read icmp packets, and have another thread perform a setsockopt() to manipulate the ipfw rules. While it's easy to work around, opening a second raw socket, it seems like a bit of a wate, and results in more packet delivery to userland than necessary. Does the pthread spec address this? Would it be possible to set/getsockopt on a socket while it's in use? For example, retrieve peer information from a socket while a thread is blocked on reading the socket, or set buffering parameters? Thanks! Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, 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 Feb 14 16: 5:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from schooner.svjava.com (schooner.svjava.com [204.75.228.3]) by builder.freebsd.org (Postfix) with ESMTP id 2E2834E61 for ; Mon, 14 Feb 2000 16:02:26 -0800 (PST) Received: (from kozowski@localhost) by schooner.svjava.com (8.9.1a/svjava.com) id QAA28918 for hackers@freebsd.org; Mon, 14 Feb 2000 16:02:45 -0800 (PST) Date: Mon, 14 Feb 2000 16:02:45 -0800 From: Eric Kozowski To: hackers@freebsd.org Subject: fsck core dumps Message-ID: <20000214160245.J27189@schooner.svjava.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 3.4-stable fsck core dumps. filesystem is ufs, part of a 36gb ide drive. running "fsck -y /dev/rwd0s2e" produces the following: LINK COUNT FILE I=3690915 OWNER=1562247989 MODE=65764 SIZE=9880933937738515337 MTIME=Oct 19 22:53 1905 COUNT 4352 SHOULD BE 1 ADJUST? yes UNREF FILE I=3690923 OWNER=3135721131 MODE=24571 SIZE=556126950697992736 MTIME=Jun 11 08:35 1997 RECONNECT? yes LINK COUNT FILE I=3690923 OWNER=3135721131 MODE=24571 SIZE=556126950697992736 MTIME=Jun 11 08:35 1997 COUNT -5075 SHOULD BE 1 ADJUST? yes BAD/DUP FILE I=3690925 OWNER=1248146931 MODE=12272 SIZE=2235520281797377464 MTIME=Dec 1 21:09 1966 CLEAR? yes UNREF FILE I=3690930 OWNER=4136256716 MODE=24775 SIZE=12563637446546308215 MTIME=Oct 2 14:22 1928 RECONNECT? yes LINK COUNT FILE I=3690930 OWNER=4136256716 MODE=24775 SIZE=12563637446546308215 MTIME=Oct 2 14:22 1928 COUNT 28908 SHOULD BE 1 ADJUST? yes BAD/DUP FILE I=3690933 OWNER=285247717 MODE=105310 SIZE=13317395247609562347 MTIME=Nov 2 03:07 1983 CLEAR? yes Segmentation fault (core dumped) # gdb /sbin/fsck fsck.core GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... Core was generated by `fsck'. Program terminated with signal 11, Segmentation fault. #0 0x8049bf4 in iblock () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 16: 7:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rz.fh-wilhelmshaven.de (mail.rz.fh-wilhelmshaven.de [139.13.25.134]) by builder.freebsd.org (Postfix) with ESMTP id 76A0F4B2D for ; Mon, 14 Feb 2000 16:02:44 -0800 (PST) Received: from fettesau.stuwo.fh-wilhelmshaven.de (stuwopc5.stuwo.fh-wilhelmshaven.de [139.13.209.5]) by mail.rz.fh-wilhelmshaven.de (8.9.3/8.9.3) with SMTP id BAA09842; Tue, 15 Feb 2000 01:02:55 +0100 (MET) Message-Id: <4.1.20000215005607.00c043c0@mail.rz.fh-wilhelmshaven.de> X-Sender: ohoyer@mail.rz.fh-wilhelmshaven.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 15 Feb 2000 01:03:40 +0100 To: ozden@research.bell-labs.com (Banu Ozden) From: Olaf Hoyer Subject: Re: scsi target mode Cc: freebsd-hackers@freebsd.org In-Reply-To: <200002141719.MAA18497@aura.research.bell-labs.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >a. settings on the controller card (e.g. scsi id, termination) >b. freebsd configuration on the initiator and target PCs. > (e.g. do we use scsi_pt.c, scsi_target.c, etc). > >here's a diagram depicting what we want to do. we're trying to setup >a PC (PC2 below) with an adaptec controller to act as an emulated disk. >PC 1 will access the disks on PC 2. > > ______________ ______________________________ >| PC1 | scsi cable | PC2 scsi bus | >| adaptec 2940 | ================= | adaptec 2940 ======== disk | >| SCSI ID=7 | | SCSI ID=0 SCSI ID=5 | >|______________| |______________________________| > Hi! Well, I'd rather try (for simplification) following combo: I won't connect the two 2940 directly. PC1 goes via the external SCSI-connector to another (50-pin narrow connector), that is directly hooked up to the cabling between the HDD and the 2nd AHA 2940 in PC2. AHA 2940(id5)--------------^^^----------HDD Slot blind with adapter | | to 2940(id7) Those adapters are quite cheap (50 pin from ribbon cable to 50 pin slot blind) In that combo you would bypass the AHA2940 having to act as a "router" with his two SCSI channels, being the external connector one channel. You only would have to worry about right bus negotiation and termination. (Ok, if you want to do this for fun--- nuff said) Regards Olaf Hoyer -------- Olaf Hoyer www.nightfire.de mailto:Olaf.Hoyer@nightfire.de FreeBSD- Turning PC's into workstations ICQ:22838075 Liebe und Hass sind nicht blind, aber geblendet vom Feuer, dass sie selber mit sich tragen. (Nietzsche) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 16:26:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by builder.freebsd.org (Postfix) with ESMTP id 5AD8E448E for ; Mon, 14 Feb 2000 16:12:42 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id TAA05646; Mon, 14 Feb 2000 19:12:51 -0500 (EST) Date: Mon, 14 Feb 2000 19:12:51 -0500 (EST) From: Daniel Eischen Message-Id: <200002150012.TAA05646@pcnet1.pcnet.com> To: freebsd-hackers@FreeBSD.ORG, robert+freebsd@cyrus.watson.org Subject: Re: uthread: setsockopt while other threads blocked? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm using a threaded program to manage ipfw rules, and today discovered > the hardware that you cannot simultaneously have a thread blocking on a > recvfrom() on the raw socket to read icmp packets, and have another thread > perform a setsockopt() to manipulate the ipfw rules. Yea, it's because our threads library locks fds, so the set/getsockopt can't access the fd until the recvfrom() is processed. I kinda think the application should be responsible for protecting access to files, and that the threads library shouldn't have to do this behind the scenes. I'm not exactly sure what the POSIX spec has to say, or implies, in this regard. I'll have to have a look. > While it's easy to work around, opening a second raw socket, it seems like > a bit of a wate, and results in more packet delivery to userland than > necessary. Does the pthread spec address this? Would it be possible to > set/getsockopt on a socket while it's in use? For example, retrieve peer > information from a socket while a thread is blocked on reading the socket, > or set buffering parameters? I don't know if the POSIX spec addresses this. I'll see if I can find something in the spec about this. It doesn't seem like it would hurt anything to be able to set buffering parameters or retrieve peer info from the socket. As long as your not corrupting the data stream that would go to another thread that had previously issued a read request. I'd be very hesitent to change our current method of locking fd's though, without knowing how it would affect other applications. Do you have a sample application that you can try on other systems, like Solaris or True64? I'd be interested to see how Solaris handles this. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 16:49:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by builder.freebsd.org (Postfix) with ESMTP id BCF2E4C00 for ; Mon, 14 Feb 2000 16:48:08 -0800 (PST) Received: from river ([10.0.128.30]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with SMTP id 401; Mon, 14 Feb 2000 16:44:15 -0800 Message-ID: <19c101bf774e$2eead6c0$1e80000a@avantgo.com> From: "Scott Hess" To: "Daniel Eischen" , , References: <200002150012.TAA05646@pcnet1.pcnet.com> Subject: Re: uthread: setsockopt while other threads blocked? Date: Mon, 14 Feb 2000 16:47:06 -0800 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.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you're really certain that you know what you're doing, you might consider using _thread_sys_setsockopt() to go behind the pthread library's back. Non-portable, and a really bad idea if you can get away without it (in this case, I'd probably go with the second socket unless I determined that it really was a drag on performance or something). Later, scott ----- Original Message ----- From: "Daniel Eischen" To: ; Sent: Monday, February 14, 2000 4:12 PM Subject: Re: uthread: setsockopt while other threads blocked? > > I'm using a threaded program to manage ipfw rules, and today discovered > > the hardware that you cannot simultaneously have a thread blocking on a > > recvfrom() on the raw socket to read icmp packets, and have another thread > > perform a setsockopt() to manipulate the ipfw rules. > > Yea, it's because our threads library locks fds, so the set/getsockopt > can't access the fd until the recvfrom() is processed. I kinda think > the application should be responsible for protecting access to files, > and that the threads library shouldn't have to do this behind the > scenes. I'm not exactly sure what the POSIX spec has to say, or > implies, in this regard. I'll have to have a look. > > > While it's easy to work around, opening a second raw socket, it seems like > > a bit of a wate, and results in more packet delivery to userland than > > necessary. Does the pthread spec address this? Would it be possible to > > set/getsockopt on a socket while it's in use? For example, retrieve peer > > information from a socket while a thread is blocked on reading the socket, > > or set buffering parameters? > > I don't know if the POSIX spec addresses this. I'll see if I can > find something in the spec about this. It doesn't seem like it would > hurt anything to be able to set buffering parameters or retrieve peer > info from the socket. As long as your not corrupting the data stream > that would go to another thread that had previously issued a read > request. > > I'd be very hesitent to change our current method of locking fd's > though, without knowing how it would affect other applications. > > Do you have a sample application that you can try on other systems, > like Solaris or True64? I'd be interested to see how Solaris handles > this. > > Dan Eischen > eischen@vigrid.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 Mon Feb 14 17:37:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by builder.freebsd.org (Postfix) with SMTP id 7C38D3E12 for ; Mon, 14 Feb 2000 17:37:39 -0800 (PST) Received: (qmail 99606 invoked by uid 1000); 15 Feb 2000 01:37:58 -0000 Date: Tue, 15 Feb 2000 02:37:58 +0100 From: "Karsten W. Rohrbach" To: Greg Lehey Cc: Christoph Kukulies , hackers@FreeBSD.ORG Subject: Re: bonnie still trustable? Message-ID: <20000215023758.A99113@rohrbach.de> Reply-To: karsten@rohrbach.de References: <200002110949.KAA14176@gil.physik.rwth-aachen.de> <20000213151650.A97412@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000213151650.A97412@freebie.lemis.com>; from grog@lemis.com on Sun, Feb 13, 2000 at 03:16:50PM +1030 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: karsten@rohrbach.de Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i personally like shimon's st.d... it exercises a disk very thoroughly, so if you want to benchmark - and, of course, have plenty of time for the box to run the benchmark - st.d is the choice since you got your free-of-charge(tm) burn in of the disk subsystem with it. what it basically does is simulating a nonlinear load behaviour like you got in a multi-client or large amount of concurrent i/o processes environment and i like it a lot. welps, i won't argue about the command line parameters - just see for yourself ;-) http://www.simon-shapiro.org/st_d/index.html /k Greg Lehey(grog@lemis.com)@Sun, Feb 13, 2000 at 03:16:50PM +1030: > On Friday, 11 February 2000 at 10:49:24 +0100, Christoph Kukulies wrote: > > PIII/500, 128 MB > > > > I'm wondering if this is trustable: > > > >> bonnie -s 400 > > File './Bonnie.14321', size: 419430400 > > Writing with putc()...done > > Rewriting...done > > Writing intelligently...done > > Reading with getc()...done > > Reading intelligently...done > > Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... > > -------Sequential Output-------- ---Sequential Input-- --Random-- > > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > > 400 20015 73.7 18369 22.9 6750 12.6 22308 81.5 22467 26.0 93.8 1.0 > > ^^^^ > > ? > > > > > > wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ff on isa > > wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 > > wd0: 19574MB (40088160 sectors), 39770 cyls, 16 heads, 63 S/T, 512 B/S > > There are lies, damn lies, and statistics. I'm sure that the results > mean something; the real question is, what do you want them to mean? > > If you're trying to measure the storage device, rawio (Ports > Collection) is a much better choice. > > Greg > -- > Finger grog@lemis.com for PGP public key > 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 -- > "Dort wo andere Moral besitzen hat sie ein Loch." -- Erich Kaestner http://www.webmonster.de http://www.apache.de http://www.splatterworld.de (NIC-HDL KR433/KR11-RIPE) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 14 17:56:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by builder.freebsd.org (Postfix) with ESMTP id 09CDF3E69 for ; Mon, 14 Feb 2000 17:56:13 -0800 (PST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA05949; Tue, 15 Feb 2000 12:27:14 +1030 (CST) Date: Tue, 15 Feb 2000 12:27:14 +1030 From: Greg Lehey To: "Karsten W. Rohrbach" Cc: Christoph Kukulies , hackers@FreeBSD.ORG, shimon@simon-shapiro.org Subject: Re: bonnie still trustable? Message-ID: <20000215122714.D4538@freebie.lemis.com> References: <200002110949.KAA14176@gil.physik.rwth-aachen.de> <20000213151650.A97412@freebie.lemis.com> <20000215023758.A99113@rohrbach.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000215023758.A99113@rohrbach.de> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 15 February 2000 at 2:37:58 +0100, Karsten W. Rohrbach wrote: > Greg Lehey(grog@lemis.com)@Sun, Feb 13, 2000 at 03:16:50PM +1030: >> On Friday, 11 February 2000 at 10:49:24 +0100, Christoph Kukulies wrote: >>> PIII/500, 128 MB >>> >>> I'm wondering if this is trustable: >>> >>>> bonnie -s 400 >>> File './Bonnie.14321', size: 419430400 >>> Writing with putc()...done >>> Rewriting...done >>> Writing intelligently...done >>> Reading with getc()...done >>> Reading intelligently...done >>> Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... >>> -------Sequential Output-------- ---Sequential Input-- --Random-- >>> -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- >>> Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU >>> 400 20015 73.7 18369 22.9 6750 12.6 22308 81.5 22467 26.0 93.8 1.0 >>> ^^^^ >>> ? >>> >>> >>> wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ff on isa >>> wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 >>> wd0: 19574MB (40088160 sectors), 39770 cyls, 16 heads, 63 S/T, 512 B/S >> >> There are lies, damn lies, and statistics. I'm sure that the results >> mean something; the real question is, what do you want them to mean? >> >> If you're trying to measure the storage device, rawio (Ports >> Collection) is a much better choice. > > i personally like shimon's st.d... > it exercises a disk very thoroughly, so if you want to benchmark - and, > of course, have plenty of time for the box to run the benchmark - st.d > is the choice since you got your free-of-charge(tm) burn in of the disk > subsystem with it. what it basically does is simulating a nonlinear load > behaviour like you got in a multi-client or large amount of concurrent > i/o processes environment and i like it a lot. welps, i won't argue > about the command line parameters - just see for yourself ;-) > > http://www.simon-shapiro.org/st_d/index.html Interesting. This looks like a well-kept secret. I don't see anything that jumps out and tells me where to get this software, nor where I can get a printable version of the documentation. Shimon, can you help? Greg -- Finger grog@lemis.com for PGP public key 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 Feb 14 19:16:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by builder.freebsd.org (Postfix) with ESMTP id E843B4027; Mon, 14 Feb 2000 19:16:41 -0800 (PST) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id TAA46848; Mon, 14 Feb 2000 19:17:03 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 14 Feb 2000 19:17:03 -0800 (PST) From: Kris Kennaway To: Greg Lehey Cc: "Karsten W. Rohrbach" , Christoph Kukulies , hackers@FreeBSD.ORG, shimon@simon-shapiro.org Subject: Re: bonnie still trustable? In-Reply-To: <20000215122714.D4538@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Feb 2000, Greg Lehey wrote: > > http://www.simon-shapiro.org/st_d/index.html > I don't see anything that jumps out and tells me where to get this > software, nor where I can get a printable version of the > documentation. Shimon, can you help? The above URL links to the documentation, section 1.2.1 of which points to ftp://simon-shapiro.org/pub/st.d/ and contains multiple versions of the documentation (.ps, .dvi, .lyx, .tex, ...) as well as the code itself :-) Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 1:40:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by builder.freebsd.org (Postfix) with ESMTP id 960A342F2 for ; Tue, 15 Feb 2000 01:40:36 -0800 (PST) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id DAA27212 for hackers@freebsd.org; Tue, 15 Feb 2000 03:40:59 -0600 (CST) From: Joe Greco Message-Id: <200002150940.DAA27212@aurora.sol.net> Subject: Filesystem size limit? To: hackers@freebsd.org Date: Tue, 15 Feb 2000 03:40:58 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So I wanted to vinum my new 1.9TB of disks together just for chuckles, and it went OK up to the newfs.. S play.p0.s0 State: up PO: 0 B Size: 46 GB S play.p0.s1 State: up PO: 32 MB Size: 46 GB S play.p0.s2 State: up PO: 64 MB Size: 46 GB S play.p0.s3 State: up PO: 96 MB Size: 46 GB S play.p0.s4 State: up PO: 128 MB Size: 46 GB S play.p0.s5 State: up PO: 160 MB Size: 46 GB S play.p0.s6 State: up PO: 192 MB Size: 46 GB S play.p0.s7 State: up PO: 224 MB Size: 46 GB S play.p0.s8 State: up PO: 256 MB Size: 46 GB S play.p0.s9 State: up PO: 288 MB Size: 46 GB S play.p0.s10 State: up PO: 320 MB Size: 46 GB S play.p0.s11 State: up PO: 352 MB Size: 46 GB S play.p0.s12 State: up PO: 384 MB Size: 46 GB S play.p0.s13 State: up PO: 416 MB Size: 46 GB S play.p0.s14 State: up PO: 448 MB Size: 46 GB S play.p0.s15 State: up PO: 480 MB Size: 46 GB S play.p0.s16 State: up PO: 512 MB Size: 46 GB S play.p0.s17 State: up PO: 544 MB Size: 46 GB S play.p0.s18 State: up PO: 576 MB Size: 46 GB S play.p0.s19 State: up PO: 608 MB Size: 46 GB S play.p0.s20 State: up PO: 640 MB Size: 46 GB S play.p0.s21 State: up PO: 672 MB Size: 46 GB S play.p0.s22 State: up PO: 704 MB Size: 46 GB S play.p0.s23 State: up PO: 736 MB Size: 46 GB S play.p0.s24 State: up PO: 768 MB Size: 46 GB S play.p0.s25 State: up PO: 800 MB Size: 46 GB S play.p0.s26 State: up PO: 832 MB Size: 46 GB S play.p0.s27 State: up PO: 864 MB Size: 46 GB S play.p0.s28 State: up PO: 896 MB Size: 46 GB S play.p0.s29 State: up PO: 928 MB Size: 46 GB S play.p0.s30 State: up PO: 960 MB Size: 46 GB S play.p0.s31 State: up PO: 992 MB Size: 46 GB S play.p0.s32 State: up PO: 1024 MB Size: 46 GB S play.p0.s33 State: up PO: 1056 MB Size: 46 GB S play.p0.s34 State: up PO: 1088 MB Size: 46 GB S play.p0.s35 State: up PO: 1120 MB Size: 46 GB S play.p0.s36 State: up PO: 1152 MB Size: 46 GB S play.p0.s37 State: up PO: 1184 MB Size: 46 GB vinum -> Suspended # newfs -v /dev/vinum/rplay preposterous size -584318976 Bleah. :-( Just thought I'd mention it. I'm putting the machine into production, with the smaller filesystems that I originally intended, but it seemed noteworthy to pass this along. Dunno how many terabyte filesystem folks are out there. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 2:34: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from valis.olywa.net (valis.olywa.net [216.173.192.2]) by builder.freebsd.org (Postfix) with ESMTP id C4A943FA1; Tue, 15 Feb 2000 02:30:50 -0800 (PST) Received: from [216.173.212.205] by valis.olywa.net (Post.Office MTA v3.5.3 release 223 ID# 0-56662U5000L500S0V35) with ESMTP id net; Tue, 15 Feb 2000 02:30:46 -0800 User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630) Date: Tue, 15 Feb 2000 02:31:08 -0800 Subject: Re: kern/16318: Fix for wrong interface when adding new routes From: William Carrel To: , , , Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This patch is applicable for both FreeBSD-stable AND FreeBSD-current, as well as OpenBSD and NetBSD. It has no noticeable ill-effects on the machines of nearly a dozen FreeBSD users that have been testing the patch for me. Nor does it have ill effects on the OpenBSD and NetBSD machines I have access to. It fixes some brain-dead behavior of the kernel routing table on all these operating systems. It causes the routing table to check itself for the ifa to assign to new routes before asking the interfaces. There are occasions (such as Ethernet point to point links) where the interfaces' idea of where a packet should go could disagree with the routing tables user made static entries. This leads to some very bizarre behavior for things like the default gateway if they get their packets routed to the wrong interface. The patch is available here: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=16318 I just thought I'd post this around again to draw attention to my open PR with code included, and mention that I've had successful testing reports on -current. -- William Carrel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 6:18:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by builder.freebsd.org (Postfix) with ESMTP id 2474E4268 for ; Tue, 15 Feb 2000 06:17:47 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id AACBC1CD9; Tue, 15 Feb 2000 22:18:10 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Joe Greco Cc: hackers@freebsd.org Subject: Re: Filesystem size limit? In-Reply-To: Message from Joe Greco of "Tue, 15 Feb 2000 03:40:58 CST." <200002150940.DAA27212@aurora.sol.net> Date: Tue, 15 Feb 2000 22:18:10 +0800 From: Peter Wemm Message-Id: <20000215141810.AACBC1CD9@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Greco wrote: > So I wanted to vinum my new 1.9TB of disks together just for chuckles, and > it went OK up to the newfs.. > > S play.p0.s0 State: up PO: 0 B Size: 46 GB > S play.p0.s1 State: up PO: 32 MB Size: 46 GB [..] > S play.p0.s35 State: up PO: 1120 MB Size: 46 GB > S play.p0.s36 State: up PO: 1152 MB Size: 46 GB > S play.p0.s37 State: up PO: 1184 MB Size: 46 GB > vinum -> > Suspended > # newfs -v /dev/vinum/rplay > preposterous size -584318976 > > Bleah. :-( > > Just thought I'd mention it. I'm putting the machine into production, > with the smaller filesystems that I originally intended, but it seemed > noteworthy to pass this along. Dunno how many terabyte filesystem folks > are out there. /usr/include/sys/disklabel.h: u_int32_t p_size; /* number of sectors in partition */ newfs.c: int fssize; /* file system size */ .. havelabel: if (fssize == 0) fssize = pp->p_size; ie: there is a signed 32 bit sector count limit. 2^31 == 1TB. It shouldn't be too hard to get it to create 2^32 bit (2TB) filesystem though. I'd expect there to be more problems that this to bite you though. :-( 2^31 also happens to be the mmap() file offset limit FWIW. BTW; what on earth is going on this beastie? Is this raid5 or stripe/concat? (And I'd hate to be waiting for a fsck :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 8: 8:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by builder.freebsd.org (Postfix) with ESMTP id 48E274ACC for ; Tue, 15 Feb 2000 08:08:50 -0800 (PST) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id KAA54469; Tue, 15 Feb 2000 10:08:47 -0600 (CST) From: Joe Greco Message-Id: <200002151608.KAA54469@aurora.sol.net> Subject: Re: Filesystem size limit? In-Reply-To: <20000215141810.AACBC1CD9@overcee.netplex.com.au> from Peter Wemm at "Feb 15, 2000 10:18:10 pm" To: peter@netplex.com.au (Peter Wemm) Date: Tue, 15 Feb 2000 10:08:47 -0600 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Joe Greco wrote: > > So I wanted to vinum my new 1.9TB of disks together just for chuckles, and > > it went OK up to the newfs.. > > > > S play.p0.s0 State: up PO: 0 B Size: 46 GB > > S play.p0.s1 State: up PO: 32 MB Size: 46 GB > [..] > > S play.p0.s35 State: up PO: 1120 MB Size: 46 GB > > S play.p0.s36 State: up PO: 1152 MB Size: 46 GB > > S play.p0.s37 State: up PO: 1184 MB Size: 46 GB > > vinum -> > > Suspended > > # newfs -v /dev/vinum/rplay > > preposterous size -584318976 > > > > Bleah. :-( > > > > Just thought I'd mention it. I'm putting the machine into production, > > with the smaller filesystems that I originally intended, but it seemed > > noteworthy to pass this along. Dunno how many terabyte filesystem folks > > are out there. > > /usr/include/sys/disklabel.h: > u_int32_t p_size; /* number of sectors in partition */ > > newfs.c: > int fssize; /* file system size */ > .. > havelabel: > if (fssize == 0) > fssize = pp->p_size; > > ie: there is a signed 32 bit sector count limit. 2^31 == 1TB. It shouldn't > be too hard to get it to create 2^32 bit (2TB) filesystem though. I'd expect > there to be more problems that this to bite you though. :-( > > 2^31 also happens to be the mmap() file offset limit FWIW. I figured somebody'd have a fast, smart answer :-) > BTW; what on earth is going on this beastie? Is this raid5 or stripe/concat? > (And I'd hate to be waiting for a fsck :-) News. Binaries spool server (Diablo). The trick to fsck is that you don't want more inodes than you really need. Once you get past that, fsck flies. The previous generation of binaries server, worked on 27 36GB drives split into 10 partitions, designed for parallelism. Hit RESET and the news filesystems take ~30 seconds to fsck. Thanks for the info, I was mostly just curious. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 9:49: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by builder.freebsd.org (Postfix) with ESMTP id 7167B4F31 for ; Tue, 15 Feb 2000 09:39:02 -0800 (PST) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id LAA18313; Tue, 15 Feb 2000 11:39:24 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Tue, 15 Feb 2000 11:39:24 -0600 (CST) From: David Scheidt To: Banu Ozden Cc: freebsd-hackers@freebsd.org Subject: Re: scsi target mode In-Reply-To: <200002141719.MAA18497@aura.research.bell-labs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 14 Feb 2000, Banu Ozden wrote: > here's a diagram depicting what we want to do. we're trying to setup > a PC (PC2 below) with an adaptec controller to act as an emulated disk. > PC 1 will access the disks on PC 2. I don't do this on FreeBSD, but I do a lot of this under HP/UX. Our configurations look like this: --------------- --------- ---------------- | Host Adaptor0| | DISKS | | Host Adaptor1 | | SCSI ID=7 |======| |=======| SCSI ID=6 | | | | | | | --------------- --------- ----------------- As for termination, remember that SCSI is a bus. It goes from here to there, and has a terminator at each end. We no longer use the on card termination. HP make a nifty pass-through terminator (part number C2980A, for F/W/D busses only) that allows one controller be disconnected without breaking bus termination. Very handy if you need to do work on one system without disturbing the application running on the other. I advise against putting a SCSI controller in the middle, unless you use a Y cable. Regards, David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 9:56:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 4C4564C34 for ; Tue, 15 Feb 2000 09:51:13 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA44270; Tue, 15 Feb 2000 09:50:13 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Feb 2000 09:50:13 -0800 (PST) From: Matthew Dillon Message-Id: <200002151750.JAA44270@apollo.backplane.com> To: Joe Greco Cc: peter@netplex.com.au (Peter Wemm), hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? References: <200002151608.KAA54469@aurora.sol.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> ie: there is a signed 32 bit sector count limit. 2^31 == 1TB. It shouldn't :> be too hard to get it to create 2^32 bit (2TB) filesystem though. I'd expect :> there to be more problems that this to bite you though. :-( :> :> 2^31 also happens to be the mmap() file offset limit FWIW. 2^31 blocks is the limit, because the filesystem uses negative block numbers internally to represent metadata. Theoretically you can use a larger block size and a larger sector size and thus get more blocks, but unfortunately the kernel's device interface translates everything to 512-byte blocks. It is not an insurmountable problem, though, I can definitely see us supporting 2^31 x large_block filesystems in the future. E.G. where a 64K block size would yield a 128TB max fs size. -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 Tue Feb 15 10:26:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 7E78044C4 for ; Tue, 15 Feb 2000 10:18:10 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA44544; Tue, 15 Feb 2000 10:17:15 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Feb 2000 10:17:15 -0800 (PST) From: Matthew Dillon Message-Id: <200002151817.KAA44544@apollo.backplane.com> To: Joe Greco Cc: hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? References: <200002150940.DAA27212@aurora.sol.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :S play.p0.s0 State: up PO: 0 B Size: 46 GB :S play.p0.s1 State: up PO: 32 MB Size: 46 GB :S play.p0.s2 State: up PO: 64 MB Size: 46 GB :... :S play.p0.s35 State: up PO: 1120 MB Size: 46 GB :S play.p0.s36 State: up PO: 1152 MB Size: 46 GB :S play.p0.s37 State: up PO: 1184 MB Size: 46 GB :vinum -> :Suspended :# newfs -v /dev/vinum/rplay :preposterous size -584318976 : :Bleah. :-( : :Just thought I'd mention it. I'm putting the machine into production, :with the smaller filesystems that I originally intended, but it seemed :noteworthy to pass this along. Dunno how many terabyte filesystem folks :are out there. : :... Joe : :------------------------------------------------------------------------------- :Joe Greco - Systems Administrator jgreco@ns.sol.net The scary thing about this posting is that Joe was able to construct his 1TB+ filesystem with *ONLY* 37 hard drives. The second scariest thing about this posting, which Joe didn't mention, is that his sole reason for creating this filesystem is to store his collection of Elvis movies! p.s. I think large filesystems are another reason why NFS (and other remote filesystems) is only going to become more important over time. -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 Tue Feb 15 11:52:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by builder.freebsd.org (Postfix) with ESMTP id 440955797 for ; Tue, 15 Feb 2000 10:56:38 -0800 (PST) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id MAA66327; Tue, 15 Feb 2000 12:56:50 -0600 (CST) From: Joe Greco Message-Id: <200002151856.MAA66327@aurora.sol.net> Subject: Re: Filesystem size limit? In-Reply-To: <200002151817.KAA44544@apollo.backplane.com> from Matthew Dillon at "Feb 15, 2000 10:17:15 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Tue, 15 Feb 2000 12:56:50 -0600 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :S play.p0.s0 State: up PO: 0 B Size: 46 GB > :S play.p0.s1 State: up PO: 32 MB Size: 46 GB > :S play.p0.s2 State: up PO: 64 MB Size: 46 GB > :... > :S play.p0.s35 State: up PO: 1120 MB Size: 46 GB > :S play.p0.s36 State: up PO: 1152 MB Size: 46 GB > :S play.p0.s37 State: up PO: 1184 MB Size: 46 GB > :vinum -> > :Suspended > :# newfs -v /dev/vinum/rplay > :preposterous size -584318976 > : > :Bleah. :-( > : > :Just thought I'd mention it. I'm putting the machine into production, > :with the smaller filesystems that I originally intended, but it seemed > :noteworthy to pass this along. Dunno how many terabyte filesystem folks > :are out there. > > The scary thing about this posting is that Joe was able to construct his > 1TB+ filesystem with *ONLY* 37 hard drives. 37? 38. And you, a programmer! ;-) And that gets you 1.9TB (disk mfr counting-wise). I'd have loved to break 2TB but couldn't imagine how to handle the required number of scsi busses without botchery. I could get 1TB with only 20 drives. These _are_ 50GB drives. Imagine rebuilding the Tertiary Disk project at Berkeley with just two machines. :-) Worse, imagine doing the TD project as designed with 50GB drives. 370 50GB drives = 18.5TB. > The second scariest thing about this posting, which Joe didn't mention, > is that his sole reason for creating this filesystem is to store his collection > of Elvis movies! Huh? No. It's my pr0n server, dewd. Do you know how many nekkid pikturez you can stuff onto 1.8TB? Speaking of which, I'd like to compliment you on the overall design of the Diablo system. It has scaled very well to handle a hundred million articles on-spool. Dumping, hash table 67108864 entries, record size 28 <== :-) :-) :-) @268435472 diload: 104146775/104146944 entries loaded History file trim succeeded: -rw-r--r-- 1 news news 3184549904 Feb 15 05:53 /news/dhistory -rw-r--r-- 1 news news 3184549904 Feb 15 02:45 /news/dhistory.bak 3 hours to rebuild dhistory on a SMP machine. Sigh. /dev/vinum/news 14154136 8491456 5662680 60% /news /dev/vinum/n0 31805976 26465776 5340200 83% /news/spool/news/N.00 /dev/vinum/n1 31805976 26754544 5051432 84% /news/spool/news/N.01 /dev/vinum/n2 31805976 27787840 4018136 87% /news/spool/news/N.02 /dev/vinum/n3 31805976 26834120 4971856 84% /news/spool/news/N.03 /dev/vinum/n4 31805976 27609456 4196520 87% /news/spool/news/N.04 /dev/vinum/n5 31805976 26771072 5034904 84% /news/spool/news/N.05 /dev/vinum/n6 31805976 27396296 4409680 86% /news/spool/news/N.06 /dev/vinum/n7 31805976 26801120 5004856 84% /news/spool/news/N.07 /dev/vinum/n8 31805976 8 31805968 0% /news/spool/news/N.08 Yeah, I'm not using that last spool, so I could probably squeeze 120 million articles on here. No binaries obviously. I remember when local news admins were excited to be able to claim that they had a quarter of a million articles on spool. > p.s. I think large filesystems are another reason why NFS (and other remote > filesystems) is only going to become more important over time. I think "and other remote filesystems" is the concept. I'm using these spool servers instead of NFS. Many ISP's have done the NFS-mounted reader thing, and that works, if you've a NetApp or similar. However, NFS is so chatty, and NFS mounts tend to jam if the server dies. I think you'll continue to see a move towards some sort of "storage appliance" for various applications, just like the Diablo server is a storage appliance for Usenet articles. It's not exactly a filesystem, but it's similar in that it is a fit-for-purpose model to do the required task. Thanks for Diablo, Matt. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 11:53:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from soda.csua.Berkeley.edu (soda.CSUA.Berkeley.EDU [128.32.43.52]) by builder.freebsd.org (Postfix) with ESMTP id B2DFA4491 for ; Tue, 15 Feb 2000 11:25:33 -0800 (PST) Received: from soda.csua.Berkeley.edu (localhost [127.0.0.1]) by soda.csua.Berkeley.edu (8.8.8/) via ESMTP id LAA02584; Tue, 15 Feb 2000 11:24:30 -0800 (PST) env-from (jwm@CSUA.Berkeley.EDU) Message-Id: <200002151924.LAA02584@soda.csua.Berkeley.edu> To: Peter Wemm Cc: Joe Greco , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? In-reply-to: Message from Peter Wemm of "Tue, 15 Feb 2000 22:18:10 +0800." <20000215141810.AACBC1CD9@overcee.netplex.com.au> Date: Tue, 15 Feb 2000 11:24:30 -0800 From: John Milford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > /usr/include/sys/disklabel.h: > u_int32_t p_size; /* number of sectors in partition */ > > newfs.c: > int fssize; /* file system size */ > .. > havelabel: > if (fssize == 0) > fssize = pp->p_size; > > ie: there is a signed 32 bit sector count limit. 2^31 == 1TB. It shouldn't > be too hard to get it to create 2^32 bit (2TB) filesystem though. I'd expect > there to be more problems that this to bite you though. :-( > > 2^31 also happens to be the mmap() file offset limit FWIW. > > BTW; what on earth is going on this beastie? Is this raid5 or stripe/concat? > (And I'd hate to be waiting for a fsck :-) > > Cheers, > -Peter > > > Is there any real interest in moving beyond 1TB? I think that it would incur a non-trival overhead as I believe that unsigned ints would not work and we would be looking at going to 64 bit values. Or I guess something could be done to simulate larger sectors, but that is pure speculation. --John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 11:59: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by builder.freebsd.org (Postfix) with ESMTP id 3F7654F0A for ; Tue, 15 Feb 2000 11:51:07 -0800 (PST) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA13672; Tue, 15 Feb 2000 20:30:54 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA00712; Tue, 15 Feb 2000 19:43:22 +0100 (CET) (envelope-from wilko) Date: Tue, 15 Feb 2000 19:43:22 +0100 From: Wilko Bulte To: David Scheidt Cc: Banu Ozden , freebsd-hackers@FreeBSD.ORG Subject: Re: scsi target mode Message-ID: <20000215194322.B597@yedi.iaf.nl> References: <200002141719.MAA18497@aura.research.bell-labs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dscheidt@enteract.com on Tue, Feb 15, 2000 at 11:39:24AM -0600 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 15, 2000 at 11:39:24AM -0600, David Scheidt wrote: > On Mon, 14 Feb 2000, Banu Ozden wrote: > > > here's a diagram depicting what we want to do. we're trying to setup > > a PC (PC2 below) with an adaptec controller to act as an emulated disk. > > PC 1 will access the disks on PC 2. > > I don't do this on FreeBSD, but I do a lot of this under HP/UX. Our > configurations look like this: > > --------------- --------- ---------------- > | Host Adaptor0| | DISKS | | Host Adaptor1 | > | SCSI ID=7 |======| |=======| SCSI ID=6 | > | | | | | | > --------------- --------- ----------------- > > As for termination, remember that SCSI is a bus. It goes from here to > there, and has a terminator at each end. We no longer use the on card > termination. HP make a nifty pass-through terminator (part number C2980A, > for F/W/D busses only) that allows one controller be disconnected without > breaking bus termination. Very handy if you need to do work on one system > without disturbing the application running on the other. I advise against > putting a SCSI controller in the middle, unless you use a Y cable. Maybe you can find Y-cables from DEC/Compaq. Or something we call a trilink, which has 2 female and 1 male connector. We tend to use trilinks on raid controllers. Generally speaking 'joining' machines into cluster(like) you want to use differential SCSI buses. -- Wilko Bulte Arnhem, The Netherlands WWW : http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 14: 2:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mission.mvnc.edu (mission.mvnc.edu [149.143.2.3]) by builder.freebsd.org (Postfix) with ESMTP id B92F34ACC for ; Tue, 15 Feb 2000 13:04:44 -0800 (PST) Received: from localhost (kdrobnac@localhost) by mission.mvnc.edu (8.9.0/8.9.0) with SMTP id QAA22662; Tue, 15 Feb 2000 16:00:46 -0500 (EST) Date: Tue, 15 Feb 2000 16:00:46 -0500 (EST) From: Kenny Drobnack To: Joe Greco Cc: Peter Wemm , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? In-Reply-To: <200002151608.KAA54469@aurora.sol.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The trick to fsck is that you don't want more inodes than you really need. > Once you get past that, fsck flies. The previous generation of binaries > server, worked on 27 36GB drives split into 10 partitions, designed for > parallelism. Hit RESET and the news filesystems take ~30 seconds to fsck. > > Thanks for the info, I was mostly just curious. I haven't looked much into fsck, so I have no idea how this is accomplished? Is this a modified copy of fsck that only checks inodes marked as used, or is there some other method for doing this (besides a journaling fs that is :-) Also, it seems like 64 bit processors will be in use before 1 TB filesystems are common. Won't the filesystem need to be 64-bitted for that? ----- In computer terms, hardware is the stuff you can hit with a baseball bat, and software is the stuff you can only swear at. -from a web page explaining what hardware, software, and firmware are ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 14: 2:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by builder.freebsd.org (Postfix) with ESMTP id 838AD4CBB for ; Tue, 15 Feb 2000 13:06:47 -0800 (PST) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id PAA75509; Tue, 15 Feb 2000 15:07:04 -0600 (CST) From: Joe Greco Message-Id: <200002152107.PAA75509@aurora.sol.net> Subject: Re: Filesystem size limit? In-Reply-To: from Kenny Drobnack at "Feb 15, 2000 4: 0:46 pm" To: kdrobnac@mission.mvnc.edu (Kenny Drobnack) Date: Tue, 15 Feb 2000 15:07:04 -0600 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The trick to fsck is that you don't want more inodes than you really need. > > > Once you get past that, fsck flies. The previous generation of binaries > > server, worked on 27 36GB drives split into 10 partitions, designed for > > parallelism. Hit RESET and the news filesystems take ~30 seconds to fsck. > > > > Thanks for the info, I was mostly just curious. > > I haven't looked much into fsck, so I have no idea how this is > accomplished? Is this a modified copy of fsck that only checks inodes > marked as used, or is there some other method for doing this (besides a > journaling fs that is :-) No. This is a straight fsck. 30 seconds. Dirty filesystems. Just make sure your amount of metadata that needs checking is reasonably low. > Also, it seems like 64 bit processors will be in use before 1 TB > filesystems are common. Won't the filesystem need to be 64-bitted for > that? I would guess. Matt Dillon commented on this already, though, and is much better suited to having an opinion about it. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 14: 2:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by builder.freebsd.org (Postfix) with ESMTP id CE2DF4DF3 for ; Tue, 15 Feb 2000 13:15:39 -0800 (PST) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA00591; Tue, 15 Feb 2000 13:25:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002152125.NAA00591@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Joe Greco Cc: dillon@apollo.backplane.com (Matthew Dillon), hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? In-reply-to: Your message of "Tue, 15 Feb 2000 12:56:50 CST." <200002151856.MAA66327@aurora.sol.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Feb 2000 13:25:24 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The scary thing about this posting is that Joe was able to construct his > > 1TB+ filesystem with *ONLY* 37 hard drives. > > 37? 38. And you, a programmer! ;-) And that gets you 1.9TB (disk mfr > counting-wise). I'd have loved to break 2TB but couldn't imagine how to > handle the required number of scsi busses without botchery. I could get > 1TB with only 20 drives. These _are_ 50GB drives. An AMI MegaRAID 1500 will give you sixty devices - four LVD channels. At 50GB a disk, that's ~3TB from a single card. Or you could go the FC route, but that's probably too expensive to be fun. > I think you'll > continue to see a move towards some sort of "storage appliance" for various > applications, just like the Diablo server is a storage appliance for Usenet > articles. It's not exactly a filesystem, but it's similar in that it is a > fit-for-purpose model to do the required task. IMO, this is where SAN comes into the picture. But I just want Fibre Fabric working. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 14: 3:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by builder.freebsd.org (Postfix) with ESMTP id BF5E24B6C; Tue, 15 Feb 2000 13:30:53 -0800 (PST) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id PAA77222; Tue, 15 Feb 2000 15:31:19 -0600 (CST) From: Joe Greco Message-Id: <200002152131.PAA77222@aurora.sol.net> Subject: Re: Filesystem size limit? In-Reply-To: <200002152125.NAA00591@mass.cdrom.com> from Mike Smith at "Feb 15, 2000 1:25:24 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Tue, 15 Feb 2000 15:31:19 -0600 (CST) Cc: jgreco@ns.sol.net, dillon@apollo.backplane.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The scary thing about this posting is that Joe was able to construct his > > > 1TB+ filesystem with *ONLY* 37 hard drives. > > > > 37? 38. And you, a programmer! ;-) And that gets you 1.9TB (disk mfr > > counting-wise). I'd have loved to break 2TB but couldn't imagine how to > > handle the required number of scsi busses without botchery. I could get > > 1TB with only 20 drives. These _are_ 50GB drives. > > An AMI MegaRAID 1500 will give you sixty devices - four LVD channels. At > 50GB a disk, that's ~3TB from a single card. Or you could go the FC > route, but that's probably too expensive to be fun. I was under the impression that there were still device number limits with the LVD spec. Besides, figuring out how to actually physically set up more than 9 devices is a pain. The Kingston DS400 will do 9 devices, but to do more, you then have to have another chassis with only 6 (for example). Eats up space real quick :-( ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 14:14:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by builder.freebsd.org (Postfix) with ESMTP id 4DB644432 for ; Tue, 15 Feb 2000 14:00:04 -0800 (PST) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id QAA88115; Tue, 15 Feb 2000 16:00:28 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Tue, 15 Feb 2000 16:00:28 -0600 (CST) From: David Scheidt To: Wilko Bulte Cc: Banu Ozden , freebsd-hackers@FreeBSD.ORG Subject: Re: scsi target mode In-Reply-To: <20000215194322.B597@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Feb 2000, Wilko Bulte wrote: > On Tue, Feb 15, 2000 at 11:39:24AM -0600, David Scheidt wrote: > > Maybe you can find Y-cables from DEC/Compaq. Or something we call a trilink, > which has 2 female and 1 male connector. We tend to use trilinks on raid > controllers. HP sells them, which means that you can get them from someone else for 1/3 the money. I haven't got one to get a part number off of, though. > > Generally speaking 'joining' machines into cluster(like) you want to > use differential SCSI buses. Yes. Of course, I think that you want to use differential SCSI for everything. Cableing is much easier, and much less fussy. It costs more though. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 15:46:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by builder.freebsd.org (Postfix) with ESMTP id DD6A55411 for ; Tue, 15 Feb 2000 14:24:57 -0800 (PST) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id OAA00876; Tue, 15 Feb 2000 14:21:26 -0800 (PST) Date: Tue, 15 Feb 2000 14:21:26 -0800 From: Brooks Davis To: John Milford Cc: Peter Wemm , Joe Greco , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? Message-ID: <20000215142126.B20898@orion.ac.hmc.edu> References: <200002151924.LAA02584@soda.csua.Berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <200002151924.LAA02584@soda.csua.Berkeley.edu>; from jwm@CSUA.Berkeley.EDU on Tue, Feb 15, 2000 at 11:24:30AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 15, 2000 at 11:24:30AM -0800, John Milford wrote: > > Is there any real interest in moving beyond 1TB? I think that > it would incur a non-trival overhead as I believe that unsigned ints > would not work and we would be looking at going to 64 bit values. Or > I guess something could be done to simulate larger sectors, but that > is pure speculation. There should be. The digital library people are talking about tens of petabytes per site and that's probably just the beginning. I think they ordered a petabyte scale array earlier this year. Obviously we'd like FreeBSD to be able to play with those. ;-) -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 17: 3:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 991074B50 for ; Tue, 15 Feb 2000 16:13:25 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA46218; Tue, 15 Feb 2000 16:12:36 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Feb 2000 16:12:36 -0800 (PST) From: Matthew Dillon Message-Id: <200002160012.QAA46218@apollo.backplane.com> To: Joe Greco Cc: kdrobnac@mission.mvnc.edu (Kenny Drobnack), hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? References: <200002152107.PAA75509@aurora.sol.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :sure your amount of metadata that needs checking is reasonably low. : :> Also, it seems like 64 bit processors will be in use before 1 TB :> filesystems are common. Won't the filesystem need to be 64-bitted for :> that? : :I would guess. Matt Dillon commented on this already, though, and is much :better suited to having an opinion about it. : :... Joe : :------------------------------------------------------------------------------- :Joe Greco - Systems Administrator jgreco@ns.sol.net :Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 Personally I think going to 64 bit block numbers is overkill. 32 bits is plenty (for the next few decades) and, generally, people running filesystems that large tend to be in the 'fewer larger files' category rather then the 'billions of tiny files' category, so using a large block size is reasonable. At the moment the filesystem block size is the kernel's minimum disk I/O (at least when accessing portions backed by full blocks), but it is far more likely that we change the kernel to do less then full block reads then it is that we bump up the block number to 64 bits. Given a kernel modified to not have to read full blocks, the filesystem block size becomes more of a 'reservation size' and in multi-terrabyte filesystems it would not be unreasonable to make this something really big, like a megabyte (a fragment would then be 128K). With a blocksize of a megabyte filesystems up to 2048 TB would be possible with 31 bit block numbers. -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 Tue Feb 15 17: 9:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 880524B63; Tue, 15 Feb 2000 16:23:13 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA46284; Tue, 15 Feb 2000 16:22:19 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Feb 2000 16:22:19 -0800 (PST) From: Matthew Dillon Message-Id: <200002160022.QAA46284@apollo.backplane.com> To: Joe Greco Cc: msmith@FreeBSD.ORG (Mike Smith), jgreco@ns.sol.net, hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? References: <200002152131.PAA77222@aurora.sol.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> > > The scary thing about this posting is that Joe was able to construct his :> > > 1TB+ filesystem with *ONLY* 37 hard drives. :> > :> > 37? 38. And you, a programmer! ;-) And that gets you 1.9TB (disk mfr :> > counting-wise). I'd have loved to break 2TB but couldn't imagine how to :> > handle the required number of scsi busses without botchery. I could get :> > 1TB with only 20 drives. These _are_ 50GB drives. :> :> An AMI MegaRAID 1500 will give you sixty devices - four LVD channels. At :> 50GB a disk, that's ~3TB from a single card. Or you could go the FC :> route, but that's probably too expensive to be fun. : :I was under the impression that there were still device number limits with :the LVD spec. Besides, figuring out how to actually physically set up :more than 9 devices is a pain. The Kingston DS400 will do 9 devices, but :to do more, you then have to have another chassis with only 6 (for example). :Eats up space real quick :-( : :... Joe : :------------------------------------------------------------------------------- :Joe Greco - Systems Administrator jgreco@ns.sol.net Not with LVD. The whole point was to be able to have longer SCSI busses. LVD allows SCSI bus cable lengths up to 25 meters. With 16 devices the limit is 12 meters. That's 36 feet, folks! Of course, this is only true if *EVERY* device on the bus is a LVD device, so don't mix and match if you want to use long cables. This works for many reasons but the main one is that the electrical characteristics of a differential line pair are much, much, much easier to engineer for. All sorts of things work in your favor including but limited to noise generation, termination, and current paths. -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 Tue Feb 15 17:13:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 072FB505D for ; Tue, 15 Feb 2000 16:24:49 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA46340; Tue, 15 Feb 2000 16:25:11 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Feb 2000 16:25:11 -0800 (PST) From: Matthew Dillon Message-Id: <200002160025.QAA46340@apollo.backplane.com> To: John Milford Cc: Peter Wemm , Joe Greco , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? References: <200002151924.LAA02584@soda.csua.Berkeley.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> ie: there is a signed 32 bit sector count limit. 2^31 == 1TB. It shouldn't :> be too hard to get it to create 2^32 bit (2TB) filesystem though. I'd expect :> there to be more problems that this to bite you though. :-( :> :> 2^31 also happens to be the mmap() file offset limit FWIW. No it isn't. mmap() (under FreeBSD) takes an off_t for the file offset, so the file offset limit is 2^63. The size of your map is limited to the size of the user address space minus things already mapped -- around 3 GB on IA32. -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 Tue Feb 15 17:22:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 304194A01 for ; Tue, 15 Feb 2000 16:42:33 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA46418; Tue, 15 Feb 2000 16:41:44 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Feb 2000 16:41:44 -0800 (PST) From: Matthew Dillon Message-Id: <200002160041.QAA46418@apollo.backplane.com> To: Joe Greco Cc: hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? References: <200002151856.MAA66327@aurora.sol.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Speaking of which, I'd like to compliment you on the overall design of the :Diablo system. It has scaled very well to handle a hundred million articles :on-spool. : :Dumping, hash table 67108864 entries, record size 28 <== :-) :-) :-) :@268435472 :diload: 104146775/104146944 entries loaded :History file trim succeeded: :-rw-r--r-- 1 news news 3184549904 Feb 15 05:53 /news/dhistory :-rw-r--r-- 1 news news 3184549904 Feb 15 02:45 /news/dhistory.bak : :3 hours to rebuild dhistory on a SMP machine. Sigh. : :/dev/vinum/news 14154136 8491456 5662680 60% /news :/dev/vinum/n0 31805976 26465776 5340200 83% /news/spool/news/N.00 :/dev/vinum/n1 31805976 26754544 5051432 84% /news/spool/news/N.01 :/dev/vinum/n2 31805976 27787840 4018136 87% /news/spool/news/N.02 :/dev/vinum/n3 31805976 26834120 4971856 84% /news/spool/news/N.03 :/dev/vinum/n4 31805976 27609456 4196520 87% /news/spool/news/N.04 :/dev/vinum/n5 31805976 26771072 5034904 84% /news/spool/news/N.05 :/dev/vinum/n6 31805976 27396296 4409680 86% /news/spool/news/N.06 :/dev/vinum/n7 31805976 26801120 5004856 84% /news/spool/news/N.07 :/dev/vinum/n8 31805976 8 31805968 0% /news/spool/news/N.08 : :Yeah, I'm not using that last spool, so I could probably squeeze 120 million :articles on here. No binaries obviously. I have one word for this: "YowZeR!". I assume you bumped up the default hash table size... of course you must have! :> p.s. I think large filesystems are another reason why NFS (and other remote :> filesystems) is only going to become more important over time. : :I think "and other remote filesystems" is the concept. I'm using these :spool servers instead of NFS. Many ISP's have done the NFS-mounted reader :thing, and that works, if you've a NetApp or similar. However, NFS is so :chatty, and NFS mounts tend to jam if the server dies. I think you'll :continue to see a move towards some sort of "storage appliance" for various :applications, just like the Diablo server is a storage appliance for Usenet :articles. It's not exactly a filesystem, but it's similar in that it is a :fit-for-purpose model to do the required task. : :Thanks for Diablo, Matt. : :... Joe : :------------------------------------------------------------------------------- :Joe Greco - Systems Administrator jgreco@ns.sol.net :Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 Your welcome! Yes, I designed the Diablo reader *SPECIFICALLY* to be able to do (multiple) remote spool serving. The idea was to be able to supply spool redundancy so you could take a spool down without taking the whole system down, and so you could run the 'frontend' readers on pure-cpu boxes. It's predicated on the concept that a history lookup is supposed to be cheap, which is usually true. And, of course, the reader uses a multi-fork/multi-thread design, resulting in an extremely optimal footprint. The spools are supposed to be pure message respositories based on the message-id and I've contemplated using the technology to back other uses, such as a web-based messaging system or even email inboxes. The article storage format is very robust in terms of crash recovery though in retrospect I should have added a magic cookie + binary size header to the beginning of each article to make recovery more reliable. I'm glad that you and others are taking over source management of the project, I have no time to do it any more :-(. -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 Tue Feb 15 17:38: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by builder.freebsd.org (Postfix) with ESMTP id 62AEE4FE0 for ; Tue, 15 Feb 2000 17:03:19 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 5F6321CDB; Wed, 16 Feb 2000 09:03:37 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: John Milford , Joe Greco , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? In-Reply-To: Message from Matthew Dillon of "Tue, 15 Feb 2000 16:25:11 PST." <200002160025.QAA46340@apollo.backplane.com> Date: Wed, 16 Feb 2000 09:03:37 +0800 From: Peter Wemm Message-Id: <20000216010337.5F6321CDB@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :> > :> ie: there is a signed 32 bit sector count limit. 2^31 == 1TB. It shouldn 't > :> be too hard to get it to create 2^32 bit (2TB) filesystem though. I'd exp ect > :> there to be more problems that this to bite you though. :-( > :> > :> 2^31 also happens to be the mmap() file offset limit FWIW. > > No it isn't. mmap() (under FreeBSD) takes an off_t for the file offset, > so the file offset limit is 2^63. The size of your map is limited to > the size of the user address space minus things already mapped -- > around 3 GB on IA32. Sorry, my comment was ambigious. mmap(2) is 64 bit aware at the syscall level, but it's the file and device backing that is limited to 2^31 blocks (as you confirmed before). Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 18: 4:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by builder.freebsd.org (Postfix) with ESMTP id C8FD64D59 for ; Tue, 15 Feb 2000 17:27:16 -0800 (PST) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id TAA93538; Tue, 15 Feb 2000 19:22:44 -0600 (CST) From: Joe Greco Message-Id: <200002160122.TAA93538@aurora.sol.net> Subject: Re: Filesystem size limit? In-Reply-To: <200002160041.QAA46418@apollo.backplane.com> from Matthew Dillon at "Feb 15, 2000 4:41:44 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Tue, 15 Feb 2000 19:22:44 -0600 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :Speaking of which, I'd like to compliment you on the overall design of the > :Diablo system. It has scaled very well to handle a hundred million articles > :on-spool. > : > :Dumping, hash table 67108864 entries, record size 28 <== :-) :-) :-) > :@268435472 > :diload: 104146775/104146944 entries loaded > :History file trim succeeded: > :-rw-r--r-- 1 news news 3184549904 Feb 15 05:53 /news/dhistory > :-rw-r--r-- 1 news news 3184549904 Feb 15 02:45 /news/dhistory.bak > : > :3 hours to rebuild dhistory on a SMP machine. Sigh. > : > :/dev/vinum/news 14154136 8491456 5662680 60% /news > :/dev/vinum/n0 31805976 26465776 5340200 83% /news/spool/news/N.00 > :/dev/vinum/n1 31805976 26754544 5051432 84% /news/spool/news/N.01 > :/dev/vinum/n2 31805976 27787840 4018136 87% /news/spool/news/N.02 > :/dev/vinum/n3 31805976 26834120 4971856 84% /news/spool/news/N.03 > :/dev/vinum/n4 31805976 27609456 4196520 87% /news/spool/news/N.04 > :/dev/vinum/n5 31805976 26771072 5034904 84% /news/spool/news/N.05 > :/dev/vinum/n6 31805976 27396296 4409680 86% /news/spool/news/N.06 > :/dev/vinum/n7 31805976 26801120 5004856 84% /news/spool/news/N.07 > :/dev/vinum/n8 31805976 8 31805968 0% /news/spool/news/N.08 > : > :Yeah, I'm not using that last spool, so I could probably squeeze 120 million > :articles on here. No binaries obviously. > > I have one word for this: "YowZeR!". > > I assume you bumped up the default hash table size... of course you > must have! You missed the line above. 64m hash. Required a fix to Diablo to work right. :-) I actually discovered _that_ the hard way: Diablo was ignoring the config file setting, and was creating dhistory with the default hash size, which caused lots of extra disk I/O (but it still worked fairly well!) I didn't really have a reason to track it down until I hit the 60 million article mark, when the slowdown was causing the massive NNTP STAT commands that DSRS likes to throw at servers was resulting in noticeable slowdowns (under fifty lookups per second). And don't tell me that 64m is too big. I know it is probably too big. :-) > Your welcome! > > Yes, I designed the Diablo reader *SPECIFICALLY* to be able to do > (multiple) remote spool serving. The idea was to be able to supply spool > redundancy so you could take a spool down without taking the > whole system down, and so you could run the 'frontend' readers on > pure-cpu boxes. It's predicated on the concept that a history lookup > is supposed to be cheap, which is usually true. You need something to use to retrieve it, and that's a lowest common denominator, portable, etc. It also suits the idea of server-as-network- appliance, suitable for a specific need, rather than trying to take the old hammer and bludgeon NFS into doing what is needed. And I've actually had people _argue_ with me that NFS is still the right way to do it, that the mount problems can be solved, that the chattiness isn't an issue, it blows me away. > And, of course, the reader uses a multi-fork/multi-thread design, > resulting in an extremely optimal footprint. I hate your threads. Still trying to see some parts of the bigger picture. But it was a reasonable design decision, I'll grant. > The spools are supposed to be pure message respositories based > on the message-id and I've contemplated using the technology to back > other uses, such as a web-based messaging system or even email inboxes. > The article storage format is very robust in terms of crash recovery > though in retrospect I should have added a magic cookie + binary size > header to the beginning of each article to make recovery more reliable. "Squid, Squid..." :-) I keep looking at that storage API thing in the newest Squid's. My Chicago open server pumps out 8K/sec rate limited connections to 1200 simultaneous clients, that's about 30-40 megabits of traffic 24/7. One box. If I could make a Squid server perform like that, instead of a twentieth of that, I'd be in heaven. And Squid's issue is I/O bottlenecking. > I'm glad that you and others are taking over source management of > the project, I have no time to do it any more :-(. I was actually despairing a bit, late last year, no one else seemed to care about Diablo. I am already committed to the model, though, so I would have done it all myself if I had been forced to. You'll be pleased to know that there are even more people than you know who are actively interested in what's going on, though, including some folks like Russell who have some really similar visions to mine as to where things need to go in the future. Diablo is going places. Thanks for a great base to start from. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 18:25:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by builder.freebsd.org (Postfix) with ESMTP id 57EC94AD2 for ; Tue, 15 Feb 2000 18:18:34 -0800 (PST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA13477; Wed, 16 Feb 2000 11:59:14 +1030 (CST) Date: Wed, 16 Feb 2000 11:59:14 +1030 From: Greg Lehey To: Joe Greco Cc: hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? Message-ID: <20000216115914.H12517@freebie.lemis.com> References: <200002150940.DAA27212@aurora.sol.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200002150940.DAA27212@aurora.sol.net> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 15 February 2000 at 3:40:58 -0600, Joe Greco wrote: > So I wanted to vinum my new 1.9TB of disks together just for chuckles, and > it went OK up to the newfs.. > > S play.p0.s0 State: up PO: 0 B Size: 46 GB > S play.p0.s1 State: up PO: 32 MB Size: 46 GB > > S play.p0.s37 State: up PO: 1184 MB Size: 46 GB Well, it's a pity you weren't able to newfs it, but I'm glad to see that Vinum could do it. I'm not sure that striping buys you anything here, though, and a 32 MB stripe is going to be worse than concatenation: you'll have *all* your superblocks on the same disk! > Just thought I'd mention it. I'm putting the machine into > production, with the smaller filesystems that I originally intended, > but it seemed noteworthy to pass this along. JOOI, how big are the file systems? Why did you choose this size? > Dunno how many terabyte filesystem folks are out there. None, by the looks of it. Greg -- Finger grog@lemis.com for PGP public key 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 Feb 15 18:26: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by builder.freebsd.org (Postfix) with ESMTP id 709AE49CD for ; Tue, 15 Feb 2000 18:20:29 -0800 (PST) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id UAA97518; Tue, 15 Feb 2000 20:19:12 -0600 (CST) From: Joe Greco Message-Id: <200002160219.UAA97518@aurora.sol.net> Subject: Re: Filesystem size limit? In-Reply-To: <20000216115914.H12517@freebie.lemis.com> from Greg Lehey at "Feb 16, 2000 11:59:14 am" To: grog@lemis.com (Greg Lehey) Date: Tue, 15 Feb 2000 20:19:12 -0600 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tuesday, 15 February 2000 at 3:40:58 -0600, Joe Greco wrote: > > So I wanted to vinum my new 1.9TB of disks together just for chuckles, and > > it went OK up to the newfs.. > > > > S play.p0.s0 State: up PO: 0 B Size: 46 GB > > S play.p0.s1 State: up PO: 32 MB Size: 46 GB > > > > S play.p0.s37 State: up PO: 1184 MB Size: 46 GB > > Well, it's a pity you weren't able to newfs it, but I'm glad to see > that Vinum could do it. I'm not sure that striping buys you anything > here, though, and a 32 MB stripe is going to be worse than > concatenation: you'll have *all* your superblocks on the same disk! For a "play" filesystem, I didn't care, and for an un-newfs-able filesystem, it's irrelevant anyways. For production servers, I take the cylinder group size in sectors and use that for the stripe size, hoping (of course) that metadata and files that are related will end up on the same drive. This is the traditional optimization I've preached here for years. With vinum, it is pretty easy although I usually go through half a dozen "resetconfig"'s before I reach something that I'm completely happy with. > > Just thought I'd mention it. I'm putting the machine into > > production, with the smaller filesystems that I originally intended, > > but it seemed noteworthy to pass this along. > > JOOI, how big are the file systems? Why did you choose this size? It all has to do with unified design strategy. In a news system, you cannot afford to lose the history. I've a hundred million articles on spool, and to reconstruct the history, I'd have to read them all. Even assuming I can do a hundred articles per second (possibly a bit more), that means I'd need 11.5 days to reload the history from the spool. I'd rather not. The history is also the most active filesystem: you have lots of seek activity and lots of small read/writes. The actual spools do not need to have too much speed. So, since I'm using 9-bay Kingston rack-mount drive arrays, what I did for the smaller text spool servers was to set up two shelves of 18GB drives (18 x 18GB ~= 324GB). The history does not need to be large: maybe 15GB total for the partition. So I grab 1.5GB from each drive, and make a plex out of the top 9 drives and another out of the bottom 9 drives, and mirror them. Redundancy. Hard to lose history. For the data, which I'm less concerned about losing due to higher level redundancy in the network, I simply stripe both drive 0's together for my "n0" partition, drive 1's for "n1", ... drive 9's for "n8". This gives me 9 spool fs's and a history fs, both optimized for their tasks, while keeping the number of drives to a minimum - since space can be very expensive! However, working with arbitrarily large numbers of spool filesystems is a pain, so I don't know if I'd have a compelling reason to set up a server with 18 spool fs's. Yet, when I built my binaries spool with 4 shelves, that would have been the model. Instead, I chose to take 750MB from each of the top 18 50GB drives, and stripe them into one half of the history mirror, and the bottom 18 50GB for the other half. I then striped all _four_ drive 0's, 1's, etc. for my spools, yielding 9 190GB spools. Lo and behold, it looks very similar at the application level. This all works out very nicely because accesses within a single spool filesystem will tend to be striped not only between drives but also between _controllers_, at least if the access is big enough to involve more than a single stripe. But, more importantly, it's easy to extend the model, and some sort of logical consistency is important in this business, where someone else may take over next year. > > Dunno how many terabyte filesystem folks are out there. > > None, by the looks of it. :-( ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 19: 0:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from soda.csua.Berkeley.edu (soda.CSUA.Berkeley.EDU [128.32.43.52]) by builder.freebsd.org (Postfix) with ESMTP id 08658497B for ; Tue, 15 Feb 2000 18:44:23 -0800 (PST) Received: from soda.csua.Berkeley.edu (localhost [127.0.0.1]) by soda.csua.Berkeley.edu (8.8.8/) via ESMTP id SAA13218; Tue, 15 Feb 2000 18:27:05 -0800 (PST) env-from (jwm@CSUA.Berkeley.EDU) Message-Id: <200002160227.SAA13218@soda.csua.Berkeley.edu> To: Brooks Davis Cc: Peter Wemm , Joe Greco , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? In-reply-to: Message from Brooks Davis of "Tue, 15 Feb 2000 14:21:26 PST." <20000215142126.B20898@orion.ac.hmc.edu> Date: Tue, 15 Feb 2000 18:27:03 -0800 From: John Milford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brooks Davis wrote: > On Tue, Feb 15, 2000 at 11:24:30AM -0800, John Milford wrote: > > > > Is there any real interest in moving beyond 1TB? I think that > > it would incur a non-trival overhead as I believe that unsigned ints > > would not work and we would be looking at going to 64 bit values. Or > > I guess something could be done to simulate larger sectors, but that > > is pure speculation. > > There should be. The digital library people are talking about tens of > petabytes per site and that's probably just the beginning. I think > they ordered a petabyte scale array earlier this year. Obviously we'd > like FreeBSD to be able to play with those. ;-) > Ok, what I was getting at is that 1TB is a very large single filesystem, but I can understand as time goes by this will become more important. If it is omething that will really help peolple I would be willing to try to do something to fix it, but if these types of filesystems are not within reach now, then it may be a better use of effort to wait on this issue. --John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 19:13:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 8935145F6 for ; Tue, 15 Feb 2000 19:06:40 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA46880; Tue, 15 Feb 2000 17:34:09 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Feb 2000 17:34:09 -0800 (PST) From: Matthew Dillon Message-Id: <200002160134.RAA46880@apollo.backplane.com> To: Joe Greco Cc: hackers@freebsd.org Subject: Re: Filesystem size limit? References: <200002160122.TAA93538@aurora.sol.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> And, of course, the reader uses a multi-fork/multi-thread design, :> resulting in an extremely optimal footprint. : :I hate your threads. Still trying to see some parts of the bigger :picture. But it was a reasonable design decision, I'll grant. heh heh. Be happy, it's second generation -- the first generation was what I did in BestWWWD which was nearly impossible to follow. The procedure-state-based model that dreaderd uses is actually reasonably close to what you would have to use in a threading model anyway, the only difference being that the subroutines would not have to do non-blocking-returns-to-the-main-select-loop. Remember, I did this before we had a working RFMEM rfork() *OR* a reliable aio subsystem. These days I would simply use the linux threads library under FreeBSD (at least until we get our new threads library working) and take the 'thousands of processes' hit (which is ok by me since the page table is shared). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 19:25:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by builder.freebsd.org (Postfix) with ESMTP id 5003C4496 for ; Tue, 15 Feb 2000 19:20:13 -0800 (PST) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id TAA00919; Tue, 15 Feb 2000 19:16:43 -0800 (PST) Date: Tue, 15 Feb 2000 19:16:43 -0800 From: Brooks Davis To: John Milford Cc: Brooks Davis , Peter Wemm , Joe Greco , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? Message-ID: <20000215191643.A27699@orion.ac.hmc.edu> References: <200002160227.SAA13218@soda.csua.Berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <200002160227.SAA13218@soda.csua.Berkeley.edu>; from jwm@CSUA.Berkeley.EDU on Tue, Feb 15, 2000 at 06:27:03PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 15, 2000 at 06:27:03PM -0800, John Milford wrote: > Brooks Davis wrote: > > > On Tue, Feb 15, 2000 at 11:24:30AM -0800, John Milford wrote: > > > > > > Is there any real interest in moving beyond 1TB? I think that > > > it would incur a non-trival overhead as I believe that unsigned ints > > > would not work and we would be looking at going to 64 bit values. Or > > > I guess something could be done to simulate larger sectors, but that > > > is pure speculation. > > > > There should be. The digital library people are talking about tens of > > petabytes per site and that's probably just the beginning. I think > > they ordered a petabyte scale array earlier this year. Obviously we'd > > like FreeBSD to be able to play with those. ;-) > > Ok, what I was getting at is that 1TB is a very large > single filesystem, but I can understand as time goes by this will > become more important. If it is omething that will really help > peolple I would be willing to try to do something to fix it, but > if these types of filesystems are not within reach now, then it > may be a better use of effort to wait on this issue. Joe seem to want one. This size is certaintly within the reach of an ISP now, and disks just keep getting bigger. My administrative bias is that partitioning for a reason other then policy should be avoided and thus I'd love to see filesystem size support keep ahead of volume sizes where possiable. That said, unless someone gives me a very substantial amount of money to build a cluster at work, I'm not going to be building any TB file systems for a few more years. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 19:25:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by builder.freebsd.org (Postfix) with ESMTP id 7BF2C4140 for ; Tue, 15 Feb 2000 19:21:40 -0800 (PST) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id VAA02109; Tue, 15 Feb 2000 21:22:08 -0600 (CST) From: Joe Greco Message-Id: <200002160322.VAA02109@aurora.sol.net> Subject: Re: Filesystem size limit? In-Reply-To: <200002160012.QAA46218@apollo.backplane.com> from Matthew Dillon at "Feb 15, 2000 4:12:36 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Tue, 15 Feb 2000 21:22:08 -0600 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Personally I think going to 64 bit block numbers is overkill. 32 bits > is plenty (for the next few decades) and, generally, people running > filesystems that large tend to be in the 'fewer larger files' category > rather then the 'billions of tiny files' category, so using a large > block size is reasonable. At the moment the filesystem block size is > the kernel's minimum disk I/O (at least when accessing portions backed > by full blocks), but it is far more likely that we change the kernel > to do less then full block reads then it is that we bump up the block > number to 64 bits. > > Given a kernel modified to not have to read full blocks, the filesystem > block size becomes more of a 'reservation size' and in multi-terrabyte > filesystems it would not be unreasonable to make this something really > big, like a megabyte (a fragment would then be 128K). With a blocksize > of a megabyte filesystems up to 2048 TB would be possible with 31 bit > block numbers. After reflecting on this for a few hours: In 1990, I considered a gigabyte to be a lot of space. In 2000, I consider a terabyte to be a lot of space. I'm wondering if "32 bits is plenty (for the next few decades)" is a reasonable statement. I'd extrapolate that: In 2010, I may consider a petabyte to be a lot of space. Since the limit of 2048TB is actually 2PB, I don't know if I'd consider it plenty for more than a decade. It's probably correct to say that it wouldn't be a serious issue for a decade. But more general statements would seem Gates-ian in nature. I do know that I'd really like to be able to use larger block sizes and have it work right, though, regardless of any partial block optimizations put in the kernel. For my uses, right now, I can either be smart enough to optimize or I can know I don't need to worry about the extra baggage of reading extra blocks. Given the growth in Usenet binaries, I'm forced to keep growing the storage, and it is quite possible that within the year I will be building individual filesystems with half-terabyte capacity or more. In 2020, I may consider an exabyte (EB) to be a lot of space. In 2030, I may consider a zettabyte (ZB) to be a lot of space. In 2040, I may consider a yottabyte (YB) to be a lot of space. That's a lottabytes. But I'll probably be too old to care. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 19:35:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by builder.freebsd.org (Postfix) with ESMTP id 49F0A45CE for ; Tue, 15 Feb 2000 19:28:28 -0800 (PST) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id VAA02580; Tue, 15 Feb 2000 21:28:40 -0600 (CST) From: Joe Greco Message-Id: <200002160328.VAA02580@aurora.sol.net> Subject: Re: Filesystem size limit? In-Reply-To: <20000215191643.A27699@orion.ac.hmc.edu> from Brooks Davis at "Feb 15, 2000 7:16:43 pm" To: brooks@one-eyed-alien.net (Brooks Davis) Date: Tue, 15 Feb 2000 21:28:40 -0600 (CST) Cc: jwm@CSUA.Berkeley.EDU, brooks@one-eyed-alien.net, peter@netplex.com.au, jgreco@ns.sol.net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Feb 15, 2000 at 06:27:03PM -0800, John Milford wrote: > > Brooks Davis wrote: > > > > > On Tue, Feb 15, 2000 at 11:24:30AM -0800, John Milford wrote: > > > > > > > > Is there any real interest in moving beyond 1TB? I think that > > > > it would incur a non-trival overhead as I believe that unsigned ints > > > > would not work and we would be looking at going to 64 bit values. Or > > > > I guess something could be done to simulate larger sectors, but that > > > > is pure speculation. > > > > > > There should be. The digital library people are talking about tens of > > > petabytes per site and that's probably just the beginning. I think > > > they ordered a petabyte scale array earlier this year. Obviously we'd > > > like FreeBSD to be able to play with those. ;-) > > > > Ok, what I was getting at is that 1TB is a very large > > single filesystem, but I can understand as time goes by this will > > become more important. If it is omething that will really help > > peolple I would be willing to try to do something to fix it, but > > if these types of filesystems are not within reach now, then it > > may be a better use of effort to wait on this issue. > > Joe seem to want one. This size is certaintly within the reach of an > ISP now, and disks just keep getting bigger. My administrative bias is > that partitioning for a reason other then policy should be avoided and > thus I'd love to see filesystem size support keep ahead of volume sizes > where possiable. That said, unless someone gives me a very substantial > amount of money to build a cluster at work, I'm not going to be building > any TB file systems for a few more years. Well, I just wanted the thrill of it. I should be building additional machines throughout the year. If anyone is seriously interested in work on terabyte filesystem issues, I may be able to shanghai one for a month or two and provide access to it. I may even be able to push it over the 2TB mark (barely). I do not have the qualifications or need to be doing this myself, though, alas. 72GB disks will be available later this year. Expect 2.6TB servers. :-) ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 20:33:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from soda.csua.Berkeley.edu (soda.CSUA.Berkeley.EDU [128.32.43.52]) by builder.freebsd.org (Postfix) with ESMTP id 55CE04527 for ; Tue, 15 Feb 2000 20:26:50 -0800 (PST) Received: from soda.csua.Berkeley.edu (localhost [127.0.0.1]) by soda.csua.Berkeley.edu (8.8.8/) via ESMTP id UAA02729; Tue, 15 Feb 2000 20:25:50 -0800 (PST) env-from (jwm@CSUA.Berkeley.EDU) Message-Id: <200002160425.UAA02729@soda.csua.Berkeley.edu> To: Joe Greco Cc: brooks@one-eyed-alien.net (Brooks Davis), peter@netplex.com.au, hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? In-reply-to: Message from Joe Greco of "Tue, 15 Feb 2000 21:28:40 CST." <200002160328.VAA02580@aurora.sol.net> Date: Tue, 15 Feb 2000 20:25:50 -0800 From: John Milford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Greco wrote: > > > > Joe seem to want one. This size is certaintly within the reach of an > > ISP now, and disks just keep getting bigger. My administrative bias is > > that partitioning for a reason other then policy should be avoided and > > thus I'd love to see filesystem size support keep ahead of volume sizes > > where possiable. That said, unless someone gives me a very substantial > > amount of money to build a cluster at work, I'm not going to be building > > any TB file systems for a few more years. > > Well, I just wanted the thrill of it. > > I should be building additional machines throughout the year. If anyone is > seriously interested in work on terabyte filesystem issues, I may be able > to shanghai one for a month or two and provide access to it. I may even be > able to push it over the 2TB mark (barely). I do not have the > qualifications or need to be doing this myself, though, alas. > > 72GB disks will be available later this year. Expect 2.6TB servers. :-) > I will assert that it is insanity to build and use a 1TB UFS for small files (~ 2.5e8 inodes or 32GB) at least with the current technology. Maybe I am wrong, if anyone thinks so feel free to tell me. Having said this I think that Matt's idea of increasing the effective sector size may be way to go. Does this sound resonable to everyone? I have my doubts about whether I could get something like this done in finite time given my current schedule, but I wil begin looking at it. Matt, Correct me if I am wrong, but the sector size is what has to change, and not just the block size. This being true it would seem that if we wanted 2048TB in a FS, we the minimum fragment size would be 1MB (the virtual sector size) as there would be no way of addressing anything smaller. As a side note, would this cause big problems for the VM system as suddenly it has to page to/from files in chunks of 256 pages? Or is this fairly well isolated in the code? --John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 23:22:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by builder.freebsd.org (Postfix) with ESMTP id 4B4CB3F1A for ; Tue, 15 Feb 2000 23:22:26 -0800 (PST) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id IAA09903; Wed, 16 Feb 2000 08:20:34 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA06098; Tue, 15 Feb 2000 23:39:39 +0100 (CET) (envelope-from wilko) Date: Tue, 15 Feb 2000 23:39:39 +0100 From: Wilko Bulte To: David Scheidt Cc: Banu Ozden , freebsd-hackers@FreeBSD.ORG Subject: Re: scsi target mode Message-ID: <20000215233939.A6080@yedi.iaf.nl> References: <20000215194322.B597@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dscheidt@enteract.com on Tue, Feb 15, 2000 at 04:00:28PM -0600 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 15, 2000 at 04:00:28PM -0600, David Scheidt wrote: > On Tue, 15 Feb 2000, Wilko Bulte wrote: > > > On Tue, Feb 15, 2000 at 11:39:24AM -0600, David Scheidt wrote: > > > > Maybe you can find Y-cables from DEC/Compaq. Or something we call a trilink, > > which has 2 female and 1 male connector. We tend to use trilinks on raid > > controllers. > > HP sells them, which means that you can get them from someone else for 1/3 > the money. I haven't got one to get a part number off of, though. Our VHDCI trilinks come from Amphenol I think. The HD68 variants I don't know. > > Generally speaking 'joining' machines into cluster(like) you want to > > use differential SCSI buses. > > Yes. Of course, I think that you want to use differential SCSI for > everything. Cableing is much easier, and much less fussy. It costs more > though. And consumes a bit more power due to all the external diff xceiver chips. For in-cabinet single-ended or LVD works just fine. -- Wilko Bulte Arnhem, The Netherlands WWW : http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 15 23:48:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dot.crosswinds.net (dot.crosswinds.net [204.50.152.131]) by builder.freebsd.org (Postfix) with ESMTP id 6B1A34156 for ; Tue, 15 Feb 2000 23:48:10 -0800 (PST) Received: from pc1.itos.org (avest.bas-net.by [194.85.255.137] (may be forged)) by dot.crosswinds.net (8.9.3/8.9.3) with ESMTP id HAA44074 for ; Wed, 16 Feb 2000 07:48:40 -0500 (EST) (envelope-from iliaroot@crosswinds.net) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <21757.948433671@zippy.cdrom.com> Date: Wed, 16 Feb 2000 09:48:53 -0000 (GMT) From: iliaroot@crosswinds.net To: freebsd-hackers@FreeBSD.ORG Subject: porting Linux binary distribution of ORACLE server to FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Did anyone port free distribution of ORACLE server for Linux to FreeBSD? Cheers Ilia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 16 0:21:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by builder.freebsd.org (Postfix) with ESMTP id CBF0640C5; Wed, 16 Feb 2000 00:21:07 -0800 (PST) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id IAA10741; Wed, 16 Feb 2000 08:41:50 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id IAA52184; Wed, 16 Feb 2000 08:46:19 +0100 (CET) (envelope-from wilko) Date: Wed, 16 Feb 2000 08:46:19 +0100 From: Wilko Bulte To: Mike Smith Cc: Joe Greco , Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? Message-ID: <20000216084619.B51972@yedi.iaf.nl> References: <200002151856.MAA66327@aurora.sol.net> <200002152125.NAA00591@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002152125.NAA00591@mass.cdrom.com>; from msmith@FreeBSD.ORG on Tue, Feb 15, 2000 at 01:25:24PM -0800 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 15, 2000 at 01:25:24PM -0800, Mike Smith wrote: > > > The scary thing about this posting is that Joe was able to construct his > > > 1TB+ filesystem with *ONLY* 37 hard drives. ... > > I think you'll > > continue to see a move towards some sort of "storage appliance" for various > > applications, just like the Diablo server is a storage appliance for Usenet > > articles. It's not exactly a filesystem, but it's similar in that it is a > > fit-for-purpose model to do the required task. > > IMO, this is where SAN comes into the picture. But I just want Fibre > Fabric working. 8) If only the FC switches came down in price. And the adapters. I get to play with this at work, and it is really the road to go. But for now the $$ involved are really substantial. -- Wilko Bulte Arnhem, The Netherlands WWW : http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 16 4:18:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elwood.akitanet.co.uk (elwood.akitanet.co.uk [212.1.130.149]) by builder.freebsd.org (Postfix) with ESMTP id DAD7B441F for ; Wed, 16 Feb 2000 04:18:31 -0800 (PST) Received: from elwood.akitanet.co.uk (elwood.akitanet.co.uk [212.1.130.149]) by elwood.akitanet.co.uk (8.9.3/8.9.1) with ESMTP id MAA39680; Wed, 16 Feb 2000 12:09:14 GMT Date: Wed, 16 Feb 2000 12:09:14 +0000 (GMT) From: Paul Robinson To: John Milford Cc: Joe Greco , Brooks Davis , peter@netplex.com.au, hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? In-Reply-To: <200002160425.UAA02729@soda.csua.Berkeley.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Feb 2000, John Milford wrote: > I will assert that it is insanity to build and use a 1TB UFS > for small files (~ 2.5e8 inodes or 32GB) at least with the current > technology. Maybe I am wrong, if anyone thinks so feel free to tell It has to be said that whilst reading this thread, I've been sat here silently with phrases like 'Storage-Area Networks' buzzing around my head. I agree that multi-terabyte and even petabyte sytems are possible today using technologies better suited to them... ufs in not the way to do it... it might look impressive, but for redundancy and performance it justs seems there are better ways of doing it by breaking it up into lots of smaller filesystems (and I'm not necessarily talking about NFS or disk-partitioning.. :) -- Paul Robinson - Developer/Systems Administrator @ Akitanet Internet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 16 7: 5:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 79EAB37B536 for ; Wed, 16 Feb 2000 07:05:20 -0800 (PST) (envelope-from ml.ventu@flashnet.it) Received: from mbox01-rm.flashnet.it (mbox1.flashnet.it [194.247.160.2]) by builder.freebsd.org (Postfix) with ESMTP id A44B1132D6 for ; Wed, 16 Feb 2000 07:04:43 -0800 (PST) Received: from bo.flashnet.it (ip113.pool-10.flashnet.it [195.191.10.114]) by mbox01-rm.flashnet.it (8.9.3/8.9.3) with SMTP id QAA23494 for ; Wed, 16 Feb 2000 16:05:08 +0100 Message-Id: <200002161505.QAA23494@mbox01-rm.flashnet.it> To: freebsd-hackers@FreeBSD.ORG X-Mailer: Post Road Mailer for OS/2 (Green Edition Ver 3.0) Date: Wed, 16 Feb 2000 16:02:14 EST From: Andrea Venturoli Reply-To: Andrea Venturoli Subject: Problems ISDN Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there. I've got a problem with an ELSA QuickStep 1000pro ISDN card; I apologize if this might at first sound like a message for freebsd-questions, but I tried that with no answer and I also had a thread with hm on freebsd-isdn and, besides, this is actually fairly technical. Now, the card in subject is an ISA PnP which should be handled by the isic0 device, so I configured my kernel and I get what I expect from dmesg, i.e. isic0: ELSA QuickStep 1000pro (ISA) isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x160) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x10160, AddrB=0x20160) isic0 (i4b_pnp sn 0x00011961) at 0x160 irq 11 flags 0xd on isa When I try to use the card, however, I get some error messages which suggests isdnd can talk to the card, but receives no response, I mean, the io addresses are right (the chips are there), but the isic0 driver never gets an interrupt back. This is not just my opinion, I've been discussing this with Hellmuth Michaelis (the author of i4b) and he also suggested the same thing. If I type vmstat -i I get a list of device and their respective IRQs, but isic0 is not there. Now just to clear the ground from any suspicions, I tried different IRQs, so it's not a problem of conflict, I tried 3 different machines, so it should not be a matter of incompatibilites and the card works perfectly with other 2 operating systems (resp. NT & OS/2); I even tried both the BIOS PnP (on the system where I had it available) and userconfig. In all cases the results are the same. Is this a known problem with FreeBSD 3.4-RELEASE? Does anyone know of a possible work-around? Is there anything I can do to better diagnose the problem? Really any suggestion would be appreciated. Bye & Thanks av. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 16 7:22:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 6C35137B513 for ; Wed, 16 Feb 2000 07:22:03 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by builder.freebsd.org (Postfix) with ESMTP id 017FF132D6 for ; Wed, 16 Feb 2000 07:16:28 -0800 (PST) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.13 #1) id 12L5mm-00036A-00; Wed, 16 Feb 2000 16:50:36 +0200 From: Sheldon Hearn To: Ted Faber Cc: hackers@freebsd.org Subject: Re: Y2K: groff in the tree out of date In-reply-to: Your message of "Wed, 26 Jan 2000 17:29:19 PST." <200001270129.RAA14147@ted.isi.edu> Date: Wed, 16 Feb 2000 16:50:36 +0200 Message-ID: <11913.950712636@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000 17:29:19 PST, Ted Faber wrote: > The groff in 3.4-stable is out of date. Be sure to catch 4.0-RELEASE. :-) > Should I submit a PR on this? You'd probably be wasting your time, given that a Merge From Current is unlikely for something like this. Unless there are critical bugfixes, I wouldn't worry about it. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 16 9:19:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 2DB9037B50B; Wed, 16 Feb 2000 09:19:39 -0800 (PST) (envelope-from ptacek@dashmail.net) Received: from guppy.pond.net (guppy.pond.net [205.240.25.2]) by builder.freebsd.org (Postfix) with ESMTP id 197CE132E2; Wed, 16 Feb 2000 09:19:03 -0800 (PST) Received: from Ptacek (rc1s7p8.dashmail.net [216.36.33.80]) by guppy.pond.net (8.9.3/8.9.3) with SMTP id JAA28726; Wed, 16 Feb 2000 09:07:20 -0800 (PST) Message-ID: <00d601bf78a2$072eb5c0$0301a8c0@Ptacek> From: "Ptacek" To: , Subject: Comtrol RocketPort card problems... Date: Wed, 16 Feb 2000 09:19:47 -0800 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.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have recently installed a Comtrol RocketPort card into a FreeBSD machine and we seem to be having some problems. When attempting to test the board (reading and writing through the ports) it seems that we can only receive at 9600 baud. We are able to transmit at any baudrate, but the receive seems limited to only 9600. The test program doesn't seem to be at fault and it works fine when using the PC's original serial ports. Any ideas would be greatly appreciated. Thanks, Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 16 9:55:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id C50E837B50B for ; Wed, 16 Feb 2000 09:55:12 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from venera.isi.edu (venera.isi.edu [128.9.176.32]) by builder.freebsd.org (Postfix) with ESMTP id 05187132E5 for ; Wed, 16 Feb 2000 09:54:36 -0800 (PST) Received: from ted.isi.edu (ted.isi.edu [128.9.160.104]) by venera.isi.edu (8.8.7/8.8.6) with ESMTP id JAA05963; Wed, 16 Feb 2000 09:55:03 -0800 (PST) Received: from ted.isi.edu (localhost [127.0.0.1]) by ted.isi.edu (8.9.3/8.9.3) with ESMTP id JAA99570; Wed, 16 Feb 2000 09:55:09 -0800 (PST) (envelope-from faber@ted.isi.edu) Message-Id: <200002161755.JAA99570@ted.isi.edu> X-Mailer: exmh version 2.1.1 10/15/1999 To: Sheldon Hearn Cc: hackers@freebsd.org Subject: Re: Y2K: groff in the tree out of date In-Reply-To: Your message of "Wed, 16 Feb 2000 16:50:36 +0200." <11913.950712636@axl.noc.iafrica.com> X-Url: http://www.isi.edu/~faber Date: Wed, 16 Feb 2000 09:55:09 -0800 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-Type: text/plain; charset=us-ascii Sheldon Hearn wrote: > > >On Wed, 26 Jan 2000 17:29:19 PST, Ted Faber wrote: > >> The groff in 3.4-stable is out of date. > >Be sure to catch 4.0-RELEASE. :-) I was planning on it. Just so I understand, 3.x will not have it's groff updated? > >> Should I submit a PR on this? > >You'd probably be wasting your time, given that a Merge From Current is >unlikely for something like this. Unless there are critical bugfixes, I >wouldn't worry about it. I've got a workaround on my systems, but documents are misdated under groff 1.11 without a fix (and I don't know that my fix is comprehensive - I just fixed problems I saw). At one point FreeBSD was making a big point about being Y2K compliant. If that's still an issue, well, groff 1.11 isn't Y2K-compliant and ships installed on FreeBSD systems. If not, I'm apparently the only one using groff to write papers. :-) - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 448-9190 PGP Keys: http://www.isi.edu/~faber/pubkeys.asc -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQA/AwUBOKrkfWlM93/mX/l7EQJLrgCgt74xF9PTUxeInQyvw2DRHM/b62wAn2R2 qIlAa0LJUa9Lo0V5fvTOx0ii =4R1Y -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 16 12: 9:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 51F4337B59A for ; Wed, 16 Feb 2000 12:09:29 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by builder.freebsd.org (Postfix) with ESMTP id 9C4C7132E5; Wed, 16 Feb 2000 12:08:52 -0800 (PST) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA78466; Wed, 16 Feb 2000 12:09:28 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 16 Feb 2000 12:09:28 -0800 (PST) From: Kris Kennaway To: Ted Faber Cc: Sheldon Hearn , hackers@freebsd.org Subject: Re: Y2K: groff in the tree out of date In-Reply-To: <200002161755.JAA99570@ted.isi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Feb 2000, Ted Faber wrote: > >> The groff in 3.4-stable is out of date. > > > >Be sure to catch 4.0-RELEASE. :-) > > I was planning on it. Just so I understand, 3.x will not have it's > groff updated? I think it would be premature to say that. Your best bet is to ask the person who did the groff upgrade in 4.0 to MFC. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 16 13:24:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 99AF137B54D for ; Wed, 16 Feb 2000 13:24:19 -0800 (PST) (envelope-from wes@softweyr.com) Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by builder.freebsd.org (Postfix) with ESMTP id C4496132D6 for ; Wed, 16 Feb 2000 13:23:41 -0800 (PST) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id NAA21697; Wed, 16 Feb 2000 13:19:12 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id NAA09846; Wed, 16 Feb 2000 13:19:12 -0800 Received: from softweyr.com (dyn2.utah.xylan.com [198.206.184.238]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id NAA03974; Wed, 16 Feb 2000 13:19:05 -0800 (PST) Message-ID: <38AB15D5.FCE61463@softweyr.com> Date: Wed, 16 Feb 2000 14:25:41 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: Joe Greco , hackers@freebsd.org Subject: Re: Filesystem size limit? References: <200002150940.DAA27212@aurora.sol.net> <20000216115914.H12517@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > On Tuesday, 15 February 2000 at 3:40:58 -0600, Joe Greco wrote: > > So I wanted to vinum my new 1.9TB of disks together just for chuckles, and > > it went OK up to the newfs.. > > > > S play.p0.s0 State: up PO: 0 B Size: 46 GB > > S play.p0.s1 State: up PO: 32 MB Size: 46 GB > > > > S play.p0.s37 State: up PO: 1184 MB Size: 46 GB > > Well, it's a pity you weren't able to newfs it, but I'm glad to see > that Vinum could do it. You (Greg) asked a few days ago about the time to newfs a largish vinum volume, and then scoffed at my answer. Today I re-initialized that volume and ran newfs again, to answer your question. The output from newfs exactly filled my 1024-line scrollback buffer; here are the first and last few lines of output: bash-2.02# time newfs /dev/vinum/vinum0 newfs: /dev/vinum/vinum0: not a character-special device Warning: 3072 sector(s) in last cylinder unallocated /dev/vinum/vinum0: 488453120 sectors in 119252 cylinders of 1 tracks, 4096 sectors 238502.5MB in 7454 cyl groups (16 c/g, 32.00MB/g, 7936 i/g) super-block backups (for fsck -b #) at: 32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320, 589856, 655392, 720928, 786464, 852000, 917536, 983072, 1048608, 1114144, 1179680, 487718944, 487784480, 487850016, 487915552, 487981088, 488046624, 488112160, 488177696, 488243232, 488308768, 488374304, 488439840, real 5m53.319s user 0m43.394s sys 3m51.363s It looks like my "4 or 5 minute" estimate wasn't that far off; the system was far busier this time, running 80 web spider processes onto the other vinum volume attached to this host adapter. I have a few questions while we're in a Vinum mood here. This volume is comprised of 5x 47GB disks thusly: D vinumdrive0 State: up Device /dev/da6s1e Avail: 0/47700 MB (0%) D vinumdrive1 State: up Device /dev/da7s1e Avail: 0/47700 MB (0%) D vinumdrive2 State: up Device /dev/da8s1e Avail: 0/47700 MB (0%) D vinumdrive3 State: up Device /dev/da9e Avail: 0/47700 MB (0%) D vinumdrive4 State: up Device /dev/da10s1e Avail: 0/47700 MB (0%) V vinum0 State: up Plexes: 1 Size: 232 GB P vinum0.p0 S State: up Subdisks: 5 Size: 232 GB S vinum0.p0.s0 State: up PO: 0 B Size: 46 GB S vinum0.p0.s1 State: up PO: 256 kB Size: 46 GB S vinum0.p0.s2 State: up PO: 512 kB Size: 46 GB S vinum0.p0.s3 State: up PO: 768 kB Size: 46 GB S vinum0.p0.s4 State: up PO: 1024 kB Size: 46 GB bash-2.02# df Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/vinum/vinum0 231164 0 212671 0% /huge (Note the blocksize in the df output) > I'm not sure that striping buys you anything > here, though, and a 32 MB stripe is going to be worse than > concatenation: you'll have *all* your superblocks on the same disk! Have I successfully avoided this problem? I created this volume with the simplified stripe command. Should I consider re-configuring this volume with 2 or more smaller subdisks per physical drive and striping across the top and then bottom of the disks? I have some time to experiment with this volume, so if you need to do some research on large volumes, this might be an ideal time to work with this system. The window of opportunity may only be a week or two long, though. > > Just thought I'd mention it. I'm putting the machine into > > production, with the smaller filesystems that I originally intended, > > but it seemed noteworthy to pass this along. > > JOOI, how big are the file systems? Why did you choose this size? > > > Dunno how many terabyte filesystem folks are out there. > > None, by the looks of it. Sadly, only 1/4 TB (so far). Give us time. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 16 13:47: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 6BD5837B630 for ; Wed, 16 Feb 2000 13:46:58 -0800 (PST) (envelope-from bob@luke.immure.com) Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by builder.freebsd.org (Postfix) with ESMTP id DF084132DD for ; Wed, 16 Feb 2000 13:46:19 -0800 (PST) Received: (from bob@localhost) by luke.immure.com (8.9.3/8.9.3) id PAA54779 for freebsd-hackers@freebsd.org; Wed, 16 Feb 2000 15:46:55 -0600 (CST) (envelope-from bob) Date: Wed, 16 Feb 2000 15:46:54 -0600 From: Bob Willcox To: hackers list Subject: How to troubleshoot fundamental boot failure? Message-ID: <20000216154654.A54592@luke.immure.com> Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just received a Supermicro PIIIDM3 motherboard and have not been successful getting FreeBSD to boot on it (I've tried 3.4-RELEASE and several flavors of 4.0-current). Very early on in the boot (following the 10-second countdown) it prints out the opening message (copyright, I believe) and then immediately reboots. This motherboard has the new Intel 840 chipset, an AGP Pro slot, 4 32-bit PCI slots and 2 64-bit PCI slots. It is a dual CPU board however I only have a single 533MHz PIII installed. I'm not certain on what is the best procedure to proceed with attemting to further debug this. Any/all suggestions will be gratefully received. Thanks, Bob -- Bob Willcox The infliction of cruelty with a good conscience bob@immure.com is a delight to moralists. That is why they Austin, TX invented hell. -- Bertrand Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 16 14: 6:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id C35C837B53D for ; Wed, 16 Feb 2000 14:06:38 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by builder.freebsd.org (Postfix) with ESMTP id E3D4A132E8 for ; Wed, 16 Feb 2000 14:05:59 -0800 (PST) Date: Wed, 16 Feb 2000 16:03:14 -0600 From: Dan Nelson To: Greg Lehey Cc: Joe Greco , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? Message-ID: <20000216160314.B42792@dan.emsphone.com> References: <200002150940.DAA27212@aurora.sol.net> <20000216115914.H12517@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20000216115914.H12517@freebie.lemis.com>; from "Greg Lehey" on Wed Feb 16 11:59:14 GMT 2000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Feb 16), Greg Lehey said: > On Tuesday, 15 February 2000 at 3:40:58 -0600, Joe Greco wrote: > > > Dunno how many terabyte filesystem folks are out there. > > None, by the looks of it. Possibly no FreeBSD folks, but on Solaris, VXFS scales very well to large volumes. We've got 2TB worth of storage on a pair of Sparcs, and we probably could have created two 1TB filesystems. We went with 200gb and 100gb volumes instead, for ease of backup. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 16 17: 0:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 02C4237B505 for ; Wed, 16 Feb 2000 17:00:56 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by builder.freebsd.org (Postfix) with ESMTP id 5B018132EF for ; Wed, 16 Feb 2000 17:00:17 -0800 (PST) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA02262; Wed, 16 Feb 2000 17:12:55 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002170112.RAA02262@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bob Willcox Cc: hackers list Subject: Re: How to troubleshoot fundamental boot failure? In-reply-to: Your message of "Wed, 16 Feb 2000 15:46:54 CST." <20000216154654.A54592@luke.immure.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Feb 2000 17:12:55 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have just received a Supermicro PIIIDM3 motherboard and have not been > successful getting FreeBSD to boot on it (I've tried 3.4-RELEASE and > several flavors of 4.0-current). Very early on in the boot (following > the 10-second countdown) it prints out the opening message (copyright, > I believe) and then immediately reboots. This motherboard has the new > Intel 840 chipset, an AGP Pro slot, 4 32-bit PCI slots and 2 64-bit PCI > slots. It is a dual CPU board however I only have a single 533MHz PIII > installed. > > I'm not certain on what is the best procedure to proceed with attemting > to further debug this. Any/all suggestions will be gratefully received. First step would be to boot with a serial console and -v, so that you can narrow down the point at which it's dying. After that you'll probably need to apply some printf-style debugging. At a guess, I'd be worried about some of the BIOS probing and calls that go on at around that stage, as well as the memory probes. More data would give us a better idea, of course. If anyone in the SF Bay area has one of these boards they could lend for a few days, I could probably help narrow this down fairly quickly. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 16 18:38:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id E08C337B57B; Wed, 16 Feb 2000 18:38:43 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by builder.freebsd.org (Postfix) with ESMTP id 4F905132EF; Wed, 16 Feb 2000 18:38:03 -0800 (PST) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id UAA79564; Wed, 16 Feb 2000 20:37:13 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Wed, 16 Feb 2000 20:37:13 -0600 (CST) From: David Scheidt Reply-To: David Scheidt To: Matthew Dillon Cc: Joe Greco , Mike Smith , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? In-Reply-To: <200002160022.QAA46284@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Feb 2000, Matthew Dillon wrote: > Not with LVD. The whole point was to be able to have longer SCSI > busses. > > LVD allows SCSI bus cable lengths up to 25 meters. With 16 devices > the limit is 12 meters. That's 36 feet, folks! Which isn't really that much, once you get to the lots of busses point. It gets hard to physically fit everything. While you can put 16 devices on a SCSI bus, you can't do that and get highest performance out of them. Depending on what the data access model is, I have found between four and eight devices is best. I helped build a database server with just under 200 disks. If we hadn't been using hardware that let us put I/O controllers 10 meters from the CPU cabinet, we would have had a hard time building the machines with all the busses under the length limit. This was a duplex machine, so that's an additional problem. Of course, today I'd do it with a lot fewer disks. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 16 18:49:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 18A0137B5E4 for ; Wed, 16 Feb 2000 18:49:17 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by builder.freebsd.org (Postfix) with ESMTP id 068DD132E7 for ; Wed, 16 Feb 2000 18:48:36 -0800 (PST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA21763; Thu, 17 Feb 2000 13:18:40 +1030 (CST) Date: Thu, 17 Feb 2000 13:18:39 +1030 From: Greg Lehey To: Matthew Dillon Cc: Joe Greco , Kenny Drobnack , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? Message-ID: <20000217131839.H20710@freebie.lemis.com> References: <200002152107.PAA75509@aurora.sol.net> <200002160012.QAA46218@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200002160012.QAA46218@apollo.backplane.com> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 15 February 2000 at 16:12:36 -0800, Matthew Dillon wrote: >> sure your amount of metadata that needs checking is reasonably low. >> >>> Also, it seems like 64 bit processors will be in use before 1 TB >>> filesystems are common. Won't the filesystem need to be 64-bitted for >>> that? >> >> I would guess. Matt Dillon commented on this already, though, and is much >> better suited to having an opinion about it. > > Personally I think going to 64 bit block numbers is overkill. 32 bits > is plenty (for the next few decades) and, generally, people running > filesystems that large tend to be in the 'fewer larger files' category > rather then the 'billions of tiny files' category, so using a large > block size is reasonable. At the moment the filesystem block size is > the kernel's minimum disk I/O (at least when accessing portions backed > by full blocks), but it is far more likely that we change the kernel > to do less then full block reads then it is that we bump up the block > number to 64 bits. I think that at some point we'll need larger block numbers than will no longer fit in 32 bits. I'd rather we went to byte offsets, though, rather than block numbers. Greg -- Finger grog@lemis.com for PGP public key 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 Feb 16 20:50: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 4F74937B5EE for ; Wed, 16 Feb 2000 20:50:01 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 1D9BE132D6 for ; Wed, 16 Feb 2000 20:49:21 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA56450; Wed, 16 Feb 2000 20:49:53 -0800 (PST) (envelope-from dillon) Date: Wed, 16 Feb 2000 20:49:53 -0800 (PST) From: Matthew Dillon Message-Id: <200002170449.UAA56450@apollo.backplane.com> To: Greg Lehey Cc: Joe Greco , Kenny Drobnack , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? References: <200002152107.PAA75509@aurora.sol.net> <200002160012.QAA46218@apollo.backplane.com> <20000217131839.H20710@freebie.lemis.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I think that at some point we'll need larger block numbers than will :no longer fit in 32 bits. I'd rather we went to byte offsets, though, :rather than block numbers. : :Greg Good point. When we are faced with having to move from 32 to 64 bit block numbers, I agree completely that we should probably turn them into 64 bit byte offsets. -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 Feb 16 23:35:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 8271737B586 for ; Wed, 16 Feb 2000 23:35:36 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by builder.freebsd.org (Postfix) with ESMTP id CEC78132DE for ; Wed, 16 Feb 2000 23:34:54 -0800 (PST) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id CAA75156 for ; Thu, 17 Feb 2000 02:35:34 -0500 (EST) Message-Id: <200002170735.CAA75156@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: SBLive... anyone, anywhere? Date: Thu, 17 Feb 2000 02:35:34 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There was some mention in the SBLive earlier this year (January), whatever became of it? I checked www.posi.net and I do not see the driver listed there at all. Pointers/suggestions? -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 0:36: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from galileo.poli.hu (polinet-gw.poli.hu [195.199.8.25]) by hub.freebsd.org (Postfix) with ESMTP id A154037B622 for ; Thu, 17 Feb 2000 00:34:47 -0800 (PST) (envelope-from mauzi@faber.poli.hu) Received: from faber.poli.hu ([195.199.8.29]) by galileo.poli.hu with esmtp (Exim 3.12 #1) id 12LMNX-0002yv-00; Thu, 17 Feb 2000 09:33:39 +0100 Received: from mauzi (helo=localhost) by faber.poli.hu with local-esmtp (Exim 3.12 #1 (Debian)) id 12LMNR-0003ck-00; Thu, 17 Feb 2000 09:33:33 +0100 Date: Thu, 17 Feb 2000 09:33:33 +0100 (CET) From: Egervary Gergely To: "David E. Cross" Cc: freebsd-hackers@freebsd.org Subject: Re: SBLive... anyone, anywhere? In-Reply-To: <200002170735.CAA75156@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There was some mention in the SBLive earlier this year (January), whatever > became of it? I checked www.posi.net and I do not see the driver listed > there at all. Pointers/suggestions? it's listed there. the guy does not reply the mails, however -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 6: 3:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id C11D637B744 for ; Thu, 17 Feb 2000 06:03:45 -0800 (PST) (envelope-from ragnar@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1004) id F35837555; Thu, 17 Feb 2000 06:07:20 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id F0B9B1D8A; Thu, 17 Feb 2000 06:07:20 -0800 (PST) Date: Thu, 17 Feb 2000 06:07:20 -0800 (PST) From: Jamie Bowden To: Dan Nelson Cc: Greg Lehey , Joe Greco , hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? In-Reply-To: <20000216160314.B42792@dan.emsphone.com> Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Feb 2000, Dan Nelson wrote: :In the last episode (Feb 16), Greg Lehey said: :> On Tuesday, 15 February 2000 at 3:40:58 -0600, Joe Greco wrote: :> :> > Dunno how many terabyte filesystem folks are out there. :> :> None, by the looks of it. : :Possibly no FreeBSD folks, but on Solaris, VXFS scales very well to :large volumes. We've got 2TB worth of storage on a pair of Sparcs, and :we probably could have created two 1TB filesystems. We went with 200gb :and 100gb volumes instead, for ease of backup. We had a 2TB FS on an Origin2000 at NASA. Jamie Bowden -- "Of course, that's sort of like asking how other than Marketing, Microsoft is different from any other software company..." Kenneth G. Cavness To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 11:53:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 455DC37B7AF for ; Thu, 17 Feb 2000 11:53:08 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA19073 for FreeBSD-hackers@freebsd.org; Thu, 17 Feb 2000 20:42:04 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA02293 for FreeBSD-hackers@freebsd.org; Thu, 17 Feb 2000 20:34:36 +0100 (CET) (envelope-from wilko) Date: Thu, 17 Feb 2000 20:34:36 +0100 From: Wilko Bulte To: FreeBSD hackers list Subject: dc / de device probing Message-ID: <20000217203436.A2199@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I recently got this DEC PC which has an 21142 ethernet chip onboard. Using -current's dc driver I get: Feb 17 19:37:39 p6 /kernel: Correcting Natoma config for non-SMP Feb 17 19:37:39 p6 /kernel: dc0: port 0xec00-0xec7f m em 0xfdfffc00-0xfdfffc7f irq 11 at device 3.0 on pci0 Feb 17 19:37:39 p6 /kernel: dc0: Ethernet address: 00:00:f8:75:3c:6a Feb 17 19:37:39 p6 /kernel: miibus0: on dc0 Feb 17 19:37:39 p6 /kernel: dcphy0: on miibus 0 Feb 17 19:37:39 p6 /kernel: dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX- FDX, auto Using the de driver one gets: Feb 17 19:54:17 p6 /kernel: Correcting Natoma config for non-SMP Feb 17 19:54:17 p6 /kernel: de0: port 0xec00-0xec7 f mem 0xfdfffc00-0xfdfffc7f irq 11 at device 3.0 on pci0 Feb 17 19:54:17 p6 /kernel: de0: DEC 21142 [10-100Mb/s] pass 1.1 Feb 17 19:54:17 p6 /kernel: de0: address 00:00:f8:75:3c:6a Feb 17 19:54:17 p6 /kernel: de0: driver is using old-style compatability shims The interesting thing is that the de driver works, the dc does not: Feb 17 19:38:48 p6 login: ROOT LOGIN (root) ON ttyv0 Feb 17 19:39:40 p6 /kernel: dc0: watchdog timeout Feb 17 19:40:02 p6 /kernel: dc0: watchdog timeout The machine has it's 21142 connected to a bulkhead panel with a UTP/10base2 connector. It cannot (unless the panel is swapped for a 100mbit one) do 100mbit UTP. What I wonder: why is the dc driver detecting a 21143 whereas the de sees a 21142 (which is the correct one BTW)? Are the chips not well enough distinguishable from the hardware perspective? Wilko -- Wilko Bulte Arnhem, The Netherlands WWW : http://www.tcja.nl The FreeBSD Project: 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 Feb 17 14:19:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 6ABBF37B877 for ; Thu, 17 Feb 2000 14:19:24 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id RAA22889 for freebsd-hackers@freebsd.org; Thu, 17 Feb 2000 17:19:21 -0500 (EST) (envelope-from steve) Date: Thu, 17 Feb 2000 17:19:21 -0500 (EST) From: Steve Ames Message-Id: <200002172219.RAA22889@virtual-voodoo.com> To: freebsd-hackers@freebsd.org Subject: 64bit OS? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just read this article: http://www.zdnet.com/zdnn/stories/news/0,4586,2440002,00.html Which leads to my potentially ignorant question: Where is FreeBSD w/regards to running on the Itanium (or other 64bit chips)? -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 14:26:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2FD8537B802 for ; Thu, 17 Feb 2000 14:26:10 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA01275; Thu, 17 Feb 2000 14:26:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Steve Ames Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-reply-to: Your message of "Thu, 17 Feb 2000 17:19:21 EST." <200002172219.RAA22889@virtual-voodoo.com> Date: Thu, 17 Feb 2000 14:26:16 -0800 Message-ID: <1272.950826376@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Which leads to my potentially ignorant question: Where is FreeBSD > w/regards to running on the Itanium (or other 64bit chips)? Waiting for somebody at Intel to give us either hardware or simulator time. Without either of those things, "working on" Itanium support is a pretty pointless exercise. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 14:28:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id B912E37B84D for ; Thu, 17 Feb 2000 14:28:15 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id RAA76641; Thu, 17 Feb 2000 17:28:04 -0500 (EST) (envelope-from steve) Date: Thu, 17 Feb 2000 17:28:04 -0500 From: Steve Ames To: "Jordan K. Hubbard" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? Message-ID: <20000217172804.A65123@virtual-voodoo.com> References: <200002172219.RAA22889@virtual-voodoo.com> <1272.950826376@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <1272.950826376@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Feb 17, 2000 at 02:26:16PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 17, 2000 at 02:26:16PM -0800, Jordan K. Hubbard wrote: > > Which leads to my potentially ignorant question: Where is FreeBSD > > w/regards to running on the Itanium (or other 64bit chips)? > > Waiting for somebody at Intel to give us either hardware or simulator > time. Without either of those things, "working on" Itanium support > is a pretty pointless exercise. A pretty tricky exercise also. Thanks for the quick response Jordan. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 14:34:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id B7D3037B85B for ; Thu, 17 Feb 2000 14:34:40 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id JAA22191; Fri, 18 Feb 2000 09:34:30 +1100 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200002172234.JAA22191@mycenae.ilion.eu.org> To: Steve Ames Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-reply-to: Your message of "Thu, 17 Feb 2000 17:19:21 CDT." <200002172219.RAA22889@virtual-voodoo.com> Date: Fri, 18 Feb 2000 09:34:29 +1100 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Just read this article: > > http://www.zdnet.com/zdnn/stories/news/0,4586,2440002,00.html > > Which leads to my potentially ignorant question: Where is FreeBSD > w/regards to running on the Itanium (or other 64bit chips)? Considering the fact that Intel released the IA-64 OS info only on the 15th, and, to my knowledge, haven't signed any NDA's with anyone from the FreeBSD team, I'd assume that we're precisely nowhere. ;) Having said that, I'll be getting Itanium hardware fairly soon after it's avaliable outside of Intel, and would be ultra-happy to work on an IA-64 FreeBSD when that happens. In the meantime, the only alternative would be to convince Intel to give someone their IA-64 SimOS, but there's an extermely slim chance of that happening (from talking to someone on the IA-64 team.) Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 14:42:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 05DC537B514 for ; Thu, 17 Feb 2000 14:42:28 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id OAA80983; Thu, 17 Feb 2000 14:42:40 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200002172242.OAA80983@troutmask.apl.washington.edu> Subject: Re: 64bit OS? In-Reply-To: <200002172234.JAA22191@mycenae.ilion.eu.org> from Patryk Zadarnowski at "Feb 18, 2000 09:34:29 am" To: Patryk Zadarnowski Date: Thu, 17 Feb 2000 14:42:40 -0800 (PST) Cc: Steve Ames , freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patryk Zadarnowski wrote: > FreeBSD when that happens. In the meantime, the only alternative would be to > convince Intel to give someone their IA-64 SimOS, but there's an extermely > slim chance of that happening (from talking to someone on the IA-64 team.) > An alternative to IA-64 is the alpha processor. Last time I checked, FreeBSD ran just peachy on a 64-bit processor. ;-) Check out Cmpaq's test drive program. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 14:57:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id 4B76937B514 for ; Thu, 17 Feb 2000 14:57:46 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id JAA22484; Fri, 18 Feb 2000 09:57:19 +1100 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200002172257.JAA22484@mycenae.ilion.eu.org> To: Steve Kargl Cc: Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-reply-to: Your message of "Thu, 17 Feb 2000 14:42:40 -0800." <200002172242.OAA80983@troutmask.apl.washington.edu> Date: Fri, 18 Feb 2000 09:57:17 +1100 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Patryk Zadarnowski wrote: > > FreeBSD when that happens. In the meantime, the only alternative would be to > > convince Intel to give someone their IA-64 SimOS, but there's an extermely > > slim chance of that happening (from talking to someone on the IA-64 team.) > > > > An alternative to IA-64 is the alpha processor. Last time > I checked, FreeBSD ran just peachy on a 64-bit processor. ;-) > Check out Cmpaq's test drive program. I don't know... I'm still to get it to boot on mine (NetBSD runs fine, but for some bizzare reason, FreeBSD insists on a serial console ;) Anyway, alphas are boring compared to Itanium. What else can you say about a chip with 3MB of L3 cache on the die, a four clock cycle latency to carry the signal from one end of the chip to the other, and the main design limitation being the US power supplies? :) Not to mention the fact that Intel isn't even planning to release any single-cpu system.... Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 15:31:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 6211A37B5C7 for ; Thu, 17 Feb 2000 15:31:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA02639; Thu, 17 Feb 2000 15:42:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002172342.PAA02639@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Patryk Zadarnowski Cc: Steve Kargl , Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-reply-to: Your message of "Fri, 18 Feb 2000 09:57:17 +1100." <200002172257.JAA22484@mycenae.ilion.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Feb 2000 15:42:04 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > An alternative to IA-64 is the alpha processor. Last time > > I checked, FreeBSD ran just peachy on a 64-bit processor. ;-) > > Check out Cmpaq's test drive program. > > I don't know... I'm still to get it to boot on mine (NetBSD runs fine, but for > some bizzare reason, FreeBSD insists on a serial console ;) Anyway, alphas are > boring compared to Itanium. What else can you say about a chip with 3MB of L3 > cache on the die, a four clock cycle latency to carry the signal from one end > of the chip to the other, and the main design limitation being the US power > supplies? :) Not to mention the fact that Intel isn't even planning to release > any single-cpu system.... What can one say to that, apart from "I have one right here and it works just fine" - not something you can say about the IA-64. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 15:32:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhost.tue.nl (mailhost.tue.nl [131.155.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 2860F37B84D for ; Thu, 17 Feb 2000 15:32:20 -0800 (PST) (envelope-from marcov@toad.stack.nl) Received: from hermes.tue.nl [131.155.2.46] by mailhost.tue.nl (8.9.3) for id AAA06185 (ESMTP); Fri, 18 Feb 2000 00:32:09 +0100 (MET) Received: from deathstar (n99.dial.tue.nl [131.155.209.98]) by hermes.tue.nl (Postfix) with ESMTP id 8488E2E804 for ; Fri, 18 Feb 2000 00:32:07 +0100 (CET) From: "Marco van de Voort" To: freebsd-hackers@FreeBSD.ORG Date: Fri, 18 Feb 2000 00:30:07 +0100 Subject: Re: 64bit OS? References: Your message of "Thu, 17 Feb 2000 17:19:21 EST." <200002172219.RAA22889@virtual-voodoo.com> In-reply-to: <1272.950826376@zippy.cdrom.com> X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000217233207.8488E2E804@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Which leads to my potentially ignorant question: Where is FreeBSD > > w/regards to running on the Itanium (or other 64bit chips)? > > Waiting for somebody at Intel to give us either hardware or simulator > time. Without either of those things, "working on" Itanium support > is a pretty pointless exercise. Just a thought: One could use the released 64-bit Itanium gcc, create a i386->itanium crosscompiler, and start preparing some stuff? Marco van de Voort (MarcoV@Stack.nl) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 16:16:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 2A6FE37B893 for ; Thu, 17 Feb 2000 16:16:36 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@one.cs.rpi.edu [128.213.14.1]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA04080 for ; Thu, 17 Feb 2000 19:16:35 -0500 (EST) Message-Id: <200002180016.TAA04080@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: stuck NFS procs Date: Thu, 17 Feb 2000 19:16:34 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is only the second time ever this has happened, but it is still an interesting problem... I have a large number of "emacs" processes stuck in disk-wait. Here is the ps axl line for one such process: 33639 88194 1 0 -22 0 5856 340 vmpfw D qi- 0:01.34 emacs proxy. Any attempt to access emacs on the client system would result in a type of hang for that process. Here is a 'cat /usr/local/bin/emacs >/dev/null': 2371 90317 1 3 -18 0 268 8 pgtblk D p4- 0:00.02 cat /usr/loc To "fix" this I went to the NFS server and 'cp emacs emacs.new;rm emacs;mv emacs.new emacs'. In essence forcing a new FH. The old procs still stick arround. This leads me to believe the problem is entirely on the local system (ie, the kernel isn't asking for pages from the NFS server for that FH) Any ideas what could be corrupting the local cache (I am assuming that is the problem) like this. Nothing of note in the dmesg. -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 16:44: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.errno.com (node-d1d4bd7a.powerinter.net [209.212.189.122]) by hub.freebsd.org (Postfix) with ESMTP id 48D2537B8AB for ; Thu, 17 Feb 2000 16:44:05 -0800 (PST) (envelope-from sam@errno.com) Received: from MELANGE (melange.errno.com [209.212.166.36]) by gw.errno.com (8.9.0/8.9.0) with SMTP id QAA09455; Thu, 17 Feb 2000 16:39:02 -0800 (PST) Message-ID: <0d9e01bf79a8$a957e680$0132a8c0@MELANGE> From: "Sam Leffler" To: "Marco van de Voort" , References: Your message of "Thu, 17 Feb 2000 17:19:21 EST." <200002172219.RAA22889@virtual-voodoo.com> <20000217233207.8488E2E804@hermes.tue.nl> Subject: Re: 64bit OS? Date: Thu, 17 Feb 2000 16:39:48 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Marco van de Voort" To: Sent: Thursday, February 17, 2000 3:30 PM Subject: Re: 64bit OS? > > > Which leads to my potentially ignorant question: Where is FreeBSD > > > w/regards to running on the Itanium (or other 64bit chips)? > > > > Waiting for somebody at Intel to give us either hardware or simulator > > time. Without either of those things, "working on" Itanium support > > is a pretty pointless exercise. > > Just a thought: > > One could use the released 64-bit Itanium gcc, create a i386->itanium > crosscompiler, and start preparing some stuff? > Marco van de Voort (MarcoV@Stack.nl) > > The difficult bits rarely have anything to do with compilers and such (especially given that most of the code has been through a 64-bit port to the alpha). The system-mode pieces of IA-64/Merced were not public until recently; I noticed the full document set just became available on the intel web site this week. There's also the Linux port that was posted to the web in the past week or two; that should show what's needed for a FreeBSD port. Of course, as was mentioned before, without hardware or a simulator it's pretty pointless to put much effort into something like this. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 17: 1:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 2E84237B790 for ; Thu, 17 Feb 2000 17:01:45 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id TAA48486; Thu, 17 Feb 2000 19:00:54 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Thu, 17 Feb 2000 19:00:54 -0600 (CST) From: David Scheidt To: Patryk Zadarnowski Cc: Steve Kargl , Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-Reply-To: <200002172257.JAA22484@mycenae.ilion.eu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Patryk Zadarnowski wrote: > > I don't know... I'm still to get it to boot on mine (NetBSD runs fine, but for > some bizzare reason, FreeBSD insists on a serial console ;) Anyway, alphas are > boring compared to Itanium. What else can you say about a chip with 3MB of L3 > cache on the die, a four clock cycle latency to carry the signal from one end > of the chip to the other, and the main design limitation being the US power > supplies? :) Not to mention the fact that Intel isn't even planning to release > any single-cpu system.... "I could have had a PA-8600!"? Today, and not at some vague point in the future? David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 17: 4: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id E401D37B8CB for ; Thu, 17 Feb 2000 17:03:57 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id MAA23445; Fri, 18 Feb 2000 12:03:39 +1100 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200002180103.MAA23445@mycenae.ilion.eu.org> To: "Sam Leffler" Cc: "Marco van de Voort" , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-reply-to: Your message of "Thu, 17 Feb 2000 16:39:48 -0800." <0d9e01bf79a8$a957e680$0132a8c0@MELANGE> Date: Fri, 18 Feb 2000 12:03:37 +1100 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Which leads to my potentially ignorant question: Where is FreeBSD > > > > w/regards to running on the Itanium (or other 64bit chips)? > > > > > > Waiting for somebody at Intel to give us either hardware or simulator > > > time. Without either of those things, "working on" Itanium support > > > is a pretty pointless exercise. > > > > Just a thought: > > > > One could use the released 64-bit Itanium gcc, create a i386->itanium > > crosscompiler, and start preparing some stuff? > > Marco van de Voort (MarcoV@Stack.nl) > > > > > > The difficult bits rarely have anything to do with compilers and such > (especially given that most of the code has been through a 64-bit port to > the alpha). The system-mode pieces of IA-64/Merced were not public until > recently; I noticed the full document set just became available on the intel > web site this week. There's also the Linux port that was posted to the web > in the past week or two; that should show what's needed for a FreeBSD port. The Linux port is extremely minimalistic and uses the minimum amout of IA-64 features to get the OS to do anything useful. > Of course, as was mentioned before, without hardware or a simulator it's > pretty pointless to put much effort into something like this. Also, you'll find that the actual silicon is somewhat different from the documentation: whole chunks of the architecture are either unimplemented or covered by errata, and not planned to be fixed in the public Itanium silicon. The OS teams that signed NDAs with Intel (including the Linux team: most of their code has been written by IA-64 teams at Intel and HP) have been cooperating very closely with Intel and were given a lot of information that (most of us) can only dream about. That is to say: even the simulator wouldn't help much right now. On the other hand, IA-64 is a very exotic architecture from the OS's point of view, and anyone planning to port *BSD to it should probably start planning ASAP. Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 17: 9: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id 097A637B8CB for ; Thu, 17 Feb 2000 17:09:06 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id MAA23457; Fri, 18 Feb 2000 12:07:57 +1100 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200002180107.MAA23457@mycenae.ilion.eu.org> To: David Scheidt Cc: Steve Kargl , Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-reply-to: Your message of "Thu, 17 Feb 2000 19:00:54 MDT." Date: Fri, 18 Feb 2000 12:07:57 +1100 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "I could have had a PA-8600!"? Today, and not at some vague point in the > future? That sort-of misses the point, as I'm taking a research OS perspective, where IA-64 is trully unique in terms of versitality and a well thought-through design (especially when it comes to SASOS support!) Besides, that point in the future is not all that vague at all ;) Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 20:53:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 9EB2437B93E; Thu, 17 Feb 2000 20:53:49 -0800 (PST) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id XAA03812; Thu, 17 Feb 2000 23:53:46 -0500 Date: Thu, 17 Feb 2000 23:53:46 -0500 (EST) From: Mike Nowlin To: Mike Smith Cc: Patryk Zadarnowski , Steve Kargl , Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-Reply-To: <200002172342.PAA02639@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What can one say to that, apart from "I have one right here and it works > just fine" - not something you can say about the IA-64. 8) I'll just reach down and pat my trusty pair of manufactured-in-1993 Alpha 3000's on their heads... :) Oh, forgot... It's not new until Intel does it... sorry... mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 21:13:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id 78D9C37B957; Thu, 17 Feb 2000 21:13:03 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id QAA24862; Fri, 18 Feb 2000 16:12:56 +1100 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200002180512.QAA24862@mycenae.ilion.eu.org> To: Mike Nowlin Cc: Mike Smith , Steve Kargl , Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-reply-to: Your message of "Thu, 17 Feb 2000 23:53:46 CDT." Date: Fri, 18 Feb 2000 16:12:54 +1100 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > What can one say to that, apart from "I have one right here and it works > > just fine" - not something you can say about the IA-64. 8) > > I'll just reach down and pat my trusty pair of manufactured-in-1993 Alpha > 3000's on their heads... :) > > Oh, forgot... It's not new until Intel does it... sorry... > > mike You're being just plain silly. It takes about 5 minutes with the manuals to realize just how little AXP and IA-64 have in common: one is a classic superscalar out-of-order design, the other is just about the opposite: a typical explicit-ILP architecture. What makes IA-64 great is the 8 years of statistical analysis of real-life software the architecture design team spent fine-tuning the instruction set. What makes AXP great is the clock rates Digital/Compaq manages to pump into the beasts ;) And no, there's nothing fundamentally new in IA-64 apart from the fact that they're the last kids on the block with a 64 bit chip ;) Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 17 22:19:34 2000 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 5C30937B945 for ; Thu, 17 Feb 2000 22:19:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA74819; Thu, 17 Feb 2000 22:12:01 -0800 (PST) (envelope-from dillon) Date: Thu, 17 Feb 2000 22:12:01 -0800 (PST) From: Matthew Dillon Message-Id: <200002180612.WAA74819@apollo.backplane.com> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: stuck NFS procs References: <200002180016.TAA04080@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd say this is more likely a VM bug rather then an NFS bug. I don't think anything is being corrupted, I think it may just be a deadlock. For this sort of problem you should be able to gdb the kernel live on the system (without core'ing it) and then look at the stack backtrace for the processes in question. You need a debug version of the kernel binary that is running. gdb -k kernel.debug /dev/mem proc 88194 back proc 90317 back Also do your ps axl again and make sure there aren't any other processes stuck in an odd state, looking at the code I don't see a possible deadlock between those two blocking states. -Matt Matthew Dillon :This is only the second time ever this has happened, but it is still an :interesting problem... I have a large number of "emacs" processes stuck in :disk-wait. Here is the ps axl line for one such process: : :33639 88194 1 0 -22 0 5856 340 vmpfw D qi- 0:01.34 emacs proxy. : :Any attempt to access emacs on the client system would result in a type of :hang for that process. Here is a 'cat /usr/local/bin/emacs >/dev/null': : :2371 90317 1 3 -18 0 268 8 pgtblk D p4- 0:00.02 cat /usr/loc : :To "fix" this I went to the NFS server and 'cp emacs emacs.new;rm emacs;mv emacs.new emacs'. In essence forcing a new FH. The old procs still stick arround. : :This leads me to believe the problem is entirely on the local system (ie, :the kernel isn't asking for pages from the NFS server for that FH) : :Any ideas what could be corrupting the local cache (I am assuming that is the :problem) like this. Nothing of note in the dmesg. : :-- :David Cross | email: crossd@cs.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 Feb 17 23: 8:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 8601F37B791 for ; Thu, 17 Feb 2000 23:08:15 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id IAA14003; Fri, 18 Feb 2000 08:06:32 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA02328; Thu, 17 Feb 2000 23:32:12 +0100 (CET) (envelope-from wilko) Date: Thu, 17 Feb 2000 23:32:12 +0100 From: Wilko Bulte To: Steve Ames Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? Message-ID: <20000217233211.A2274@yedi.iaf.nl> References: <200002172219.RAA22889@virtual-voodoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002172219.RAA22889@virtual-voodoo.com>; from steve@virtual-voodoo.com on Thu, Feb 17, 2000 at 05:19:21PM -0500 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 17, 2000 at 05:19:21PM -0500, Steve Ames wrote: > > Just read this article: > > http://www.zdnet.com/zdnn/stories/news/0,4586,2440002,00.html > > Which leads to my potentially ignorant question: Where is FreeBSD > w/regards to running on the Itanium (or other 64bit chips)? FreeBSD runs very well on the Alpha, which is a 64 bit chip. There is plenty of 'vapor silicon' (as opposed to vaporware) out there, but until 64 bit chips can be bought readily in the PC world the Alpha port is the 64 bit flagship. -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: 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 Feb 17 23:30:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 331DE37B791 for ; Thu, 17 Feb 2000 23:30:06 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id CAA14119; Fri, 18 Feb 2000 02:30:01 -0500 (EST) Message-Id: <200002180730.CAA14119@cs.rpi.edu> To: Matthew Dillon Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: stuck NFS procs (LONG) In-Reply-To: Message from Matthew Dillon of "Thu, 17 Feb 2000 22:12:01 PST." <200002180612.WAA74819@apollo.backplane.com> Date: Fri, 18 Feb 2000 02:30:00 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok... we'll start with the process table... monica# ps axl | grep D UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.81 (swapper) 0 2 0 0 -18 0 0 0 psleep DL ?? 1:10.93 (pagedaemon 0 3 0 91 18 0 0 0 psleep DL ?? 0:26.62 (vmdaemon) 0 4 0 0 18 0 0 0 syncer DL ?? 1:51.82 (syncer) 17727 74079 1 0 -22 0 5952 340 vmpfw D p4- 0:01.53 emacs websrv 17727 74586 1 0 -22 0 5952 340 vmpfw D p4- 0:01.55 emacs websrv 33639 88342 1 0 -22 0 5856 340 vmpfw D p4- 0:01.27 emacs proxy. 2371 90317 1 3 -18 0 268 8 pgtblk D p4- 0:00.02 cat /usr/loc 2646 83637 1 0 -22 0 6256 528 vmpfw D p9- 0:03.56 emacs 2646 85055 1 0 -22 0 6344 528 vmpfw D p9- 0:03.00 emacs 2937 89546 1 0 -22 0 5576 340 vmpfw D pa 0:00.55 emacs /usr/t 2575 75559 1 0 -22 0 5652 340 vmpfw D pf- 0:00.99 emacs simple 2575 78298 1 0 -22 0 5576 340 vmpfw D pj- 0:00.97 emacs watchf 32837 85464 1 0 -22 0 6264 528 vmpfw D pj- 0:02.81 emacs proj2. 32837 87204 1 0 -22 0 6264 528 vmpfw D pj- 0:03.75 emacs proj2. 17727 90346 1 2 -22 0 5940 344 vmpfw D pk- 0:01.23 emacs comm.c 2575 76313 1 0 -22 0 5656 340 vmpfw D pl- 0:01.54 emacs show_p 33355 84406 1 3 -22 0 7136 528 vmpfw D pl- 0:04.54 emacs osshel 33355 85094 1 0 -22 0 7184 528 vmpfw D pl- 0:04.52 emacs 17727 90000 1 0 -22 0 5940 340 vmpfw D pl- 0:01.17 emacs comm.c 0 64921 63848 0 10 0 476 292 ppwait D pt 0:00.07 -su (csh) 2551 75473 1 0 -22 0 7284 524 vmpfw D q4- 0:05.27 emacs tftp_s 2023 77402 1 0 -22 0 5672 340 vmpfw D q8- 0:00.71 emacs index. 37080 79999 1 0 -22 0 6208 524 vmpfw D q8- 0:02.61 emacs bogosj 2440 86790 1 0 -22 0 7176 524 vmpfw D q9- 0:05.37 emacs bardet 2440 88149 1 1 -22 0 7244 524 vmpfw D q9- 0:04.91 emacs bardet 17727 89837 1 1 -22 0 5940 340 vmpfw D qd- 0:01.13 emacs comm.c 33639 88194 1 0 -22 0 5856 340 vmpfw D qi- 0:01.34 emacs proxy. And we'll move on to some backtraces... (kgdb) proc 74079 (kgdb) back #0 mi_switch () at ../../kern/kern_synch.c:825 #1 0xc0131781 in tsleep (ident=0xc054b220, priority=0, wmesg=0xc0208bc2 "vmpfw", timo=0) at ../../kern/kern_synch.c:443 #2 0xc01cfa3f in vm_fault (map=0xca8028c0, vaddr=136036352, fault_type=3 '\003', fault_flags=8) at ../../vm/vm_fault.c:308 #3 0xc01ea17a in trap_pfault (frame=0xcac7ffbc, usermode=1, eva=136036368) at ../../i386/i386/trap.c:816 #4 0xc01e9cca in trap (frame={tf_es = 136249383, tf_ds = -1078001625, tf_edi = 400, tf_esi = 10, tf_ebp = -1078114780, tf_isp = -892862492, tf_ebx = -1078110248, tf_edx = 136036332, tf_ecx = 137580544, tf_eax = 1210023680, tf_trapno = 12, tf_err = 6, tf_eip = 134831395, tf_cs = 31, tf_eflags = 66195, tf_esp = -1078114788, tf_ss = 39}) at ../../i386/i386/trap.c:358 (kgdb) proc 74586 (kgdb) back #0 mi_switch () at ../../kern/kern_synch.c:825 #1 0xc0131781 in tsleep (ident=0xc054b220, priority=0, wmesg=0xc0208bc2 "vmpfw", timo=0) at ../../kern/kern_synch.c:443 #2 0xc01cfa3f in vm_fault (map=0xca6262c0, vaddr=136036352, fault_type=3 '\003', fault_flags=8) at ../../vm/vm_fault.c:308 #3 0xc01ea17a in trap_pfault (frame=0xcac58fbc, usermode=1, eva=136036368) at ../../i386/i386/trap.c:816 #4 0xc01e9cca in trap (frame={tf_es = 39, tf_ds = 39, tf_edi = 2320, tf_esi = 58, tf_ebp = -1078114780, tf_isp = -893022236, tf_ebx = -1078108328, tf_edx = 136036332, tf_ecx = 137580544, tf_eax = 1210023680, tf_trapno = 12, tf_err = 6, tf_eip = 134831395, tf_cs = 31, tf_eflags = 66195, tf_esp = -1078114788, tf_ss = 39}) at ../../i386/i386/trap.c:358 (kgdb) proc 88342 (kgdb) back #0 mi_switch () at ../../kern/kern_synch.c:825 #1 0xc0131781 in tsleep (ident=0xc054b220, priority=0, wmesg=0xc0208bc2 "vmpfw", timo=0) at ../../kern/kern_synch.c:443 #2 0xc01cfa3f in vm_fault (map=0xca801240, vaddr=136036352, fault_type=3 '\003', fault_flags=8) at ../../vm/vm_fault.c:308 #3 0xc01ea17a in trap_pfault (frame=0xca973fbc, usermode=1, eva=136036368) at ../../i386/i386/trap.c:816 #4 0xc01e9cca in trap (frame={tf_es = 39, tf_ds = 39, tf_edi = 0, tf_esi = 0, tf_ebp = -1078114664, tf_isp = -896057372, tf_ebx = -1078110532, tf_edx = 136036332, tf_ecx = -1078110532, tf_eax = 1210023680, tf_trapno = 12, tf_err = 6, tf_eip = 134831395, tf_cs = 31, tf_eflags = 66195, tf_esp = -1078114672, tf_ss = 39}) at ../../i386/i386/trap.c:358 (this is the cat(1)) (kgdb) proc 90317 (kgdb) back #0 mi_switch () at ../../kern/kern_synch.c:825 #1 0xc0131781 in tsleep (ident=0xc054b220, priority=4, wmesg=0xc01ff83c "pgtblk", timo=0) at ../../kern/kern_synch.c:443 #2 0xc014ea7c in allocbuf (bp=0xc532ec08, size=8192) at ../../kern/vfs_bio.c:1805 #3 0xc014e5b0 in getblk (vp=0xca69b240, blkno=185, size=8192, slpflag=0, slptimeo=0) at ../../kern/vfs_bio.c:1566 #4 0xc0180cde in nfs_getcacheblk (vp=0xca69b240, bn=185, size=8192, p=0xcac45520) at ../../nfs/nfs_bio.c:914 #5 0xc017f9db in nfs_bioread (vp=0xca69b240, uio=0xcacbdf10, ioflag=8323072, cred=0xc16d4180, getpages=0) at ../../nfs/nfs_bio.c:409 #6 0xc01a5204 in nfs_read (ap=0xcacbdec8) at ../../nfs/nfs_vnops.c:963 #7 0xc0159f4f in vn_read (fp=0xc16268c0, uio=0xcacbdf10, cred=0xc16d4180, flags=0) at vnode_if.h:303 #8 0xc013a06d in dofileread (p=0xcac45520, fp=0xc16268c0, fd=3, buf=0x805a000, nbyte=65536, offset=-1, flags=0) at ../../kern/sys_generic.c:179 #9 0xc0139f77 in read (p=0xcac45520, uap=0xcacbdf94) at ../../kern/sys_generic.c:111 #10 0xc01ea777 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 1, tf_esi = 65536, tf_ebp = -1077945672, tf_isp = -892608540, tf_ebx = 0, tf_edx = 16, tf_ecx = 13, tf_eax = 3, tf_trapno = 0, tf_err = 2, tf_eip = 134515596, tf_cs = 31, tf_eflags = 582, tf_esp = -1077945796, tf_ss = 39}) at ../../i386/i386/trap.c:1100 I'll stop here. -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 0:39:18 2000 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 AF84937B599 for ; Fri, 18 Feb 2000 00:39:15 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA75699; Fri, 18 Feb 2000 00:39:13 -0800 (PST) (envelope-from dillon) Date: Fri, 18 Feb 2000 00:39:13 -0800 (PST) From: Matthew Dillon Message-Id: <200002180839.AAA75699@apollo.backplane.com> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: stuck NFS procs (LONG) References: <200002180730.CAA14119@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ah!... ok, it is an NFS bug. I've been trying to track this down for a while ever since you reported the 3.4 lockup bug. This is probably related to a similar problem. There is a bug somewhere related to NFS locking up while doing a pagein from the executable image. It can occur when the binary is ripped out from under the client but it also can apparently occur if the program takes a signal during a pagein on a valid binary that hasn't been ripped out. If you still have this machine up, can you idle it and do a tcpdump looking for NFS packets for a few minutes? I'd like to know if it is doing an infinite retry of the page it got stuck on. Knowing what it is trying to do and why it isn't aborting on error with a segfault is the key. After that, is there any chance you can panic this machine and get a kernel dump? -Matt Matthew Dillon :(kgdb) back :#0 mi_switch () at ../../kern/kern_synch.c:825 :#1 0xc0131781 in tsleep (ident=0xc054b220, priority=4, : wmesg=0xc01ff83c "pgtblk", timo=0) at ../../kern/kern_synch.c:443 :#2 0xc014ea7c in allocbuf (bp=0xc532ec08, size=8192) : at ../../kern/vfs_bio.c:1805 :#3 0xc014e5b0 in getblk (vp=0xca69b240, blkno=185, size=8192, slpflag=0, : slptimeo=0) at ../../kern/vfs_bio.c:1566 :#4 0xc0180cde in nfs_getcacheblk (vp=0xca69b240, bn=185, size=8192, : p=0xcac45520) at ../../nfs/nfs_bio.c:914 :#5 0xc017f9db in nfs_bioread (vp=0xca69b240, uio=0xcacbdf10, ioflag=8323072, : cred=0xc16d4180, getpages=0) at ../../nfs/nfs_bio.c:409 :#6 0xc01a5204 in nfs_read (ap=0xcacbdec8) at ../../nfs/nfs_vnops.c:963 :#7 0xc0159f4f in vn_read (fp=0xc16268c0, uio=0xcacbdf10, cred=0xc16d4180, : flags=0) at vnode_if.h:303 :#8 0xc013a06d in dofileread (p=0xcac45520, fp=0xc16268c0, fd=3, : buf=0x805a000, nbyte=65536, offset=-1, flags=0) : at ../../kern/sys_generic.c:179 :#9 0xc0139f77 in read (p=0xcac45520, uap=0xcacbdf94) : at ../../kern/sys_generic.c:111 :#10 0xc01ea777 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 1, : tf_esi = 65536, tf_ebp = -1077945672, tf_isp = -892608540, tf_ebx = 0, : tf_edx = 16, tf_ecx = 13, tf_eax = 3, tf_trapno = 0, tf_err = 2, : tf_eip = 134515596, tf_cs = 31, tf_eflags = 582, tf_esp = -1077945796, : tf_ss = 39}) at ../../i386/i386/trap.c:1100 : : :I'll stop here. : :-- :David Cross | email: crossd@cs.rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 0:47:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 5867737B833 for ; Fri, 18 Feb 2000 00:47:42 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id DAA15592; Fri, 18 Feb 2000 03:47:38 -0500 (EST) Message-Id: <200002180847.DAA15592@cs.rpi.edu> To: Matthew Dillon Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: stuck NFS procs (LONG) In-Reply-To: Message from Matthew Dillon of "Fri, 18 Feb 2000 00:39:13 PST." <200002180839.AAA75699@apollo.backplane.com> Date: Fri, 18 Feb 2000 03:47:38 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ah!... ok, it is an NFS bug. I've been trying to track this down > for a while ever since you reported the 3.4 lockup bug. This is probably > related to a similar problem. > > There is a bug somewhere related to NFS locking up while doing a > pagein from the executable image. It can occur when the binary > is ripped out from under the client but it also can apparently occur > if the program takes a signal during a pagein on a valid binary > that hasn't been ripped out. > > If you still have this machine up, can you idle it and do a tcpdump > looking for NFS packets for a few minutes? I'd like to know if it is > doing an infinite retry of the page it got stuck on. Knowing what > it is trying to do and why it isn't aborting on error with a segfault > is the key. > > After that, is there any chance you can panic this machine and get > a kernel dump? I can come close to idle... It should be realtively easy to identify the NFS packets in question, they will be stale FH replies from the server (as I pulled the backing store out from under it hoping that the retry would trigger a SEGV). Panic-ing it will be a bit trickier... the kernel is compiled with DDB *BUT* the only console is a serial console and I forgot to enable the ENABLE_DB_ON_SERIAL_BREAK thing-y. I am sure with gdb -k /kernel.debug /dev/mem and your expertise we could trip a panic somehow. For now, let me get you that NFS packetlog... -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 0:57:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 04ECE37B878 for ; Fri, 18 Feb 2000 00:57:33 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id DAA15752; Fri, 18 Feb 2000 03:57:26 -0500 (EST) Message-Id: <200002180857.DAA15752@cs.rpi.edu> To: Matthew Dillon Cc: "David E. Cross" , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: stuck NFS procs (LONG) In-Reply-To: Message from Matthew Dillon of "Fri, 18 Feb 2000 00:39:13 PST." <200002180839.AAA75699@apollo.backplane.com> Date: Fri, 18 Feb 2000 03:57:26 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just ran a tcpdump -s1500 for 5 minutes, gathered ~21k of data over that time, no mentions of stale NFS handles from the NFS server... it would appear the NFS client is not asking for those pages (it makes sense, since if it asked and got the 'stale' error one would expect the SEGV). -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 1:27:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id BAC0A37B7C6 for ; Fri, 18 Feb 2000 01:27:43 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id EAA16299; Fri, 18 Feb 2000 04:27:37 -0500 (EST) Message-Id: <200002180927.EAA16299@cs.rpi.edu> To: freebsd-hackers@freebsd.org, misc@openbsd.org Cc: crossd@cs.rpi.du Subject: bpgetfile Date: Fri, 18 Feb 2000 04:27:36 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Solaris has this nifty little tool for querying the bootparam server on a booting system. Handy little gadget for getting various system configuration at boot time. Neither OpenBSD nor FreeBSD have it (FreeBSD has callbootd, but I cannot get it to work easily), so I wrote a simple 'bpgetfile' for the CSLab to use for some of our diskless systems. The code is available at http://www.cs.rpi.edu/~crossd/FreeBSD/bpgetfile.tar.gz Have fun. -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 5:59:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.218.96.75]) by hub.freebsd.org (Postfix) with ESMTP id 4634237B8AE for ; Fri, 18 Feb 2000 05:59:54 -0800 (PST) (envelope-from jim@thehousleys.net) Received: from baby.int.thehousleys.net (baby.int.TheHousleys.Net [192.168.0.24]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id IAA08564 for ; Fri, 18 Feb 2000 08:59:53 -0500 (EST) Received: from thehousleys.net (localhost [127.0.0.1]) by baby.int.thehousleys.net (8.9.3/8.9.3) with ESMTP id IAA00513 for ; Fri, 18 Feb 2000 08:59:49 -0500 (EST) (envelope-from jim@thehousleys.net) Message-ID: <38AD5055.6300B6DF@thehousleys.net> Date: Fri, 18 Feb 2000 08:59:49 -0500 From: James Housley Organization: The Housleys dot Net X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: Device driver & KLD module Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG History: I had a device driver for a BDM (Background Debug Module for Motorola 683xx CPUs) that worked fine as a kernel device and a LKM. It was based upon the LPT driver, because it attached to the parallel port, and the JOY LKM, cause it was simple. Present: I have updated the driver, it does work as a kernel device. It does not work as a KLD. It does not print its startup nor create a device. It was updated to match the current JOY KLD. It also appears the JOY KLD may not be working. Questions: 1) Does the JOY KLD actually work? What is the simplest way to test it. I have a joystick, but not sure how to read info from it. 2) If not I will fix it, if possible, while fixing my BDM. 3) Looking around it would seem that the VESA KLD might be the simplest KLD to look at. Is this true, or is there a better one? My source for the BDM driver is available, for anyone who wants to peek, is at: http://bdm.thehousleys.net/bdm.tgz . The full page with some more info is at: http://bdm.thehousleys.net . Thanks for all help. Jim -- microsoft: "where do you want to go today?" linux: "where do you want to go tomorrow?" BSD: "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 Fri Feb 18 6:35: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by hub.freebsd.org (Postfix) with ESMTP id 4439637B978 for ; Fri, 18 Feb 2000 06:35:01 -0800 (PST) (envelope-from rik@cronyx.ru) Received: from cronyx.ru by hanoi.cronyx.ru with ESMTP id RAA95796; (8.9.3/vak/2.1) Fri, 18 Feb 2000 17:34:27 +0300 (MSK) Message-ID: <38AD588C.63DAC7BF@cronyx.ru> Date: Fri, 18 Feb 2000 17:34:52 +0300 From: Kurakin Roman Organization: Cronyx X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG, jim@thehousleys.net Subject: Re:Device driver & KLD module Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you want you may see my KLD drivers. Two of them for ISA and one for PCI bus. http://www.cronyx.ru/software/#sigma (version 3.2) Kurakin Roman PS I am not in the list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 6:46:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 70B8837B94A; Fri, 18 Feb 2000 06:46:41 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p12-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.77]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id XAA10781; Fri, 18 Feb 2000 23:46:10 +0900 (JST) Message-ID: <38AD5AFC.D3B15771@newsguy.com> Date: Fri, 18 Feb 2000 23:45:16 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Patryk Zadarnowski Cc: Mike Nowlin , Mike Smith , Steve Kargl , Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? References: <200002180512.QAA24862@mycenae.ilion.eu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patryk Zadarnowski wrote: > > You're being just plain silly. It takes about 5 minutes with the > manuals to realize just how little AXP and IA-64 have in common: one > is a classic superscalar out-of-order design, the other is just about > the opposite: a typical explicit-ILP architecture. What makes IA-64 > great is the 8 years of statistical analysis of real-life software the > architecture design team spent fine-tuning the instruction set. What > makes AXP great is the clock rates Digital/Compaq manages to pump into > the beasts ;) What makes IA-64 great is the fact that it has not been deployed, so Intel can say whatever it pleases them. If you got REAL LIFE NUMBERS, based on REAL LIFE PERFORMANCE, then we can talk. Let's see how it does Quake, then we can talk. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 8:11:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 7639037B9BF for ; Fri, 18 Feb 2000 08:11:15 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id IAA21663; Fri, 18 Feb 2000 08:11:04 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id IAA28899; Fri, 18 Feb 2000 08:11:03 -0800 Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id IAA20630; Fri, 18 Feb 2000 08:10:57 -0800 (PST) Message-ID: <38AD709E.30FF4D9@softweyr.com> Date: Fri, 18 Feb 2000 09:17:34 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "David E. Cross" Cc: freebsd-hackers@freebsd.org, misc@openbsd.org, crossd@xylan.com Subject: Re: bpgetfile References: <200002180927.EAA16299@cs.rpi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" wrote: > > Solaris has this nifty little tool for querying the bootparam server on a > booting system. Handy little gadget for getting various system configuration > at boot time. Neither OpenBSD nor FreeBSD have it (FreeBSD has callbootd, > but I cannot get it to work easily), so I wrote a simple 'bpgetfile' for > the CSLab to use for some of our diskless systems. The code is available > at http://www.cs.rpi.edu/~crossd/FreeBSD/bpgetfile.tar.gz Cool. Wanna wrap it in a port and send-pr it? ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 9: 0:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from home.gtcs.com (home.gtcs.com [209.181.16.2]) by hub.freebsd.org (Postfix) with ESMTP id A10EE37B9DE; Fri, 18 Feb 2000 09:00:15 -0800 (PST) (envelope-from bruce@gtcs.com) Received: from gtcs.com (localhost [127.0.0.1]) by home.gtcs.com (8.8.8/8.8.8) with ESMTP id JAA28578; Fri, 18 Feb 2000 09:59:29 -0700 (MST) (envelope-from bruce@gtcs.com) Message-Id: <200002181659.JAA28578@ home.gtcs.com> Date: Fri, 18 Feb 2000 09:59:20 -0700 (MST) From: Bruce Gingery Reply-To: bgingery@gtcs.com Subject: Recommended addition to FAQ (Troubleshooting) To: freebsd-doc@FreeBSD.org, freebsd-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 X-Loop: FreeBSD.ORG I recently installed FreeBSD on my daughter's machine, remotely. She'd been on Windows3 since growing up and moving away from my NeXT, so "UNIX" wasn't a scary word to her, and she was getting tired of "Windows95 or better" on anything she was interested in, and certainly wanted "better" if she was going to change anyways. Well, just for a quickie, so she could play with it long enough to be familiar with it before moving on to FreeBSD, we tried to install Windows95, first. The install bombed three times, and we thought it was a scratched CD-ROM. VMM32 something-or-other failed to be installed each time, or so the bluescreen said AFTER what was supposedly a complete (minimal) install. So, boom, take the 3.2-STABLE diskettes I'd prepared ... boot up fine ... mfs mount CRASH.... Re-installed Windows3 (95 had thoroughly messed the drive) ... got back on line, got 3.4-RELEASE diskette images and fdimage.exe ... just to be sure, wrote the diskettes three times each from the .flp files. Again, good boot UNTIL the mfs mount. CRASH... So, Win3.1 was still installed on the hard drive, this time, downloaded 2.2.8 boot.flp in hopes that the smaller footprint would install (this is a K6-300 64Mx9-bit system with NO BIOS errors showing, and fast-boot turned off!). It did. Had slight problems getting PPP logged in (the username required a provider prefix). Started the install. Got to about slice 15 or so of the first distribution and BOOM... Kernel fault AGAIN! I can't praise highly enough, two software packages: http://reality.sgi.com/cbrady_denver/memtest86/ and http://www.qcc.sk.ca/~charlesc/software/memtester/ The former is a bootable image memory tester, built from some pieces of LiLo, Linux Kernel, and some good algorithms that sweep flat memory. The latter is a user-space utility that has different algorithms, and built for FreeBSD pretty easily (I've submitted my modifications to the author for a 2.2.8 build -- I don't have any hosts - yet - running 3.x). BOTH of these quickly identified flakey RAM that a supposedly full BIOS sweep of RAM totally missed, and that had caused "normal crashes" with her old Win3.1 installed. I'd really like to recommend that memtest86 be placed in tools/ from now on, including a pre-compiled .flp image. Anybody who's built a kern.flp and mfsroot.flp, or a boot.flp, will have NO problem creating a stand-alone i386 and up, memory tester from the "memtest.bin" file in the ZIP distribution, or the "precomp.bin" in the source .tar.gz Both are .flp images with a custom bootstrap loader. Similarly, I'd like to recommend that the user-space memtester be at LEAST added to the ports, although it wouldn't hurt to have it as a GPL'd part of the base distribution. For people who reboot rarely, it probably wouldn't hurt to run that one just before multiuser startup on every reboot. With the slight tweak I sent the author, the creation of a port for this should be trivial - and might not even be needed with the later FreeBSD versions. The reason I'm sending this to the DOC list, is that at a bare minimum, this info needs to be added to the FAQ and/or manual. To the hackers list because everybody reads it :) and I'm recommending changes to the distribution. Bruce Gingery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 10:28: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 4D6DD37B9DD; Fri, 18 Feb 2000 10:28:02 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA79086; Fri, 18 Feb 2000 10:27:21 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Daniel C. Sobral" Cc: Patryk Zadarnowski , Mike Nowlin , Mike Smith , Steve Kargl , Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-reply-to: Your message of "Fri, 18 Feb 2000 23:45:16 +0900." <38AD5AFC.D3B15771@newsguy.com> Date: Fri, 18 Feb 2000 10:27:21 -0800 Message-ID: <79083.950898441@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you got REAL LIFE NUMBERS, based on REAL LIFE PERFORMANCE, then we > can talk. Let's see how it does Quake, then we can talk. Alpha does quake? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 10:31:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 2DD4937B9DD; Fri, 18 Feb 2000 10:31:12 -0800 (PST) (envelope-from mbac@nyct.net) Received: from bsd1.nyct.net (mbac@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id NAA02077; Fri, 18 Feb 2000 13:31:08 -0500 (EST) (envelope-from mbac@nyct.net) Received: from localhost (mbac@localhost) by bsd1.nyct.net (8.8.8/8.9.3) with ESMTP id NAA18303; Fri, 18 Feb 2000 13:31:07 -0500 (EST) (envelope-from mbac@nyct.net) X-Authentication-Warning: bsd1.nyct.net: mbac owned process doing -bs Date: Fri, 18 Feb 2000 13:31:07 -0500 (EST) From: Michael Bacarella To: Bruce Gingery Cc: freebsd-doc@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Recommended addition to FAQ (Troubleshooting) In-Reply-To: <200002181659.JAA28578@ home.gtcs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Bruce Gingery wrote: > I can't praise highly enough, two software packages: > > http://reality.sgi.com/cbrady_denver/memtest86/ > > and > > http://www.qcc.sk.ca/~charlesc/software/memtester/ Sweet! I never knew that I've wanted one for all of these years until I saw you talking about them. :) Any OS vendor would do good to package these kinds of tools. -MB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 11: 4:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from screech.weirdnoise.com (209-128-78-198.bayarea.net [209.128.78.198]) by hub.freebsd.org (Postfix) with ESMTP id AC9C037B9FC for ; Fri, 18 Feb 2000 11:04:22 -0800 (PST) (envelope-from edhall@screech.weirdnoise.com) Received: from screech.weirdnoise.com (localhost [127.0.0.1]) by screech.weirdnoise.com (8.9.3/8.9.3) with ESMTP id LAA04820; Fri, 18 Feb 2000 11:06:03 -0800 Message-Id: <200002181906.LAA04820@screech.weirdnoise.com> X-Mailer: exmh version 2.0.2 To: "Jordan K. Hubbard" Cc: freebsd-hackers@freebsd.org Subject: Re: 64bit OS? In-Reply-To: Your message of "Fri, 18 Feb 2000 10:27:21 PST." <79083.950898441@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Feb 2000 11:06:03 -0800 From: Ed Hall Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Alpha does quake? :-) It supposedly does under Linux, at least (and if you're talking about Quake I). Sources at: http://www.idsoftware.com/q1source/ These sources might need a bit of work, even for Linux, though there are folks out there who have it running under Linux/Alpha. I'd assume a FreeBSD port would only be moderately difficult, if that. This is the sum total of what I know about this... -Ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 11:11: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3E7E637B9D9; Fri, 18 Feb 2000 11:10:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA79459; Fri, 18 Feb 2000 11:10:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: bgingery@gtcs.com Cc: freebsd-doc@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Recommended addition to FAQ (Troubleshooting) In-reply-to: Your message of "Fri, 18 Feb 2000 09:59:20 MST." <200002181659.JAA28578@ home.gtcs.com> Date: Fri, 18 Feb 2000 11:10:38 -0800 Message-ID: <79456.950901038@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The situation here, I hate to say, is that you were simply very lucky in having a software memory tester show you anything at all. If your experience had been more typical, you would have run memtest86 and it would have declared your memory to be free of errors. Then you'd have gone right on having problems and losing more hair until you finally just came back to the memory and swapped it out on suspicion. Bingo, the problems are suddenly fixed and you're dragging memtest86 to KDE's trashcan with a resolve to never trust it again. The reason why software memory testers are so generally ineffectual is that there's a whole bunch of things getting in their way. Leaving aside for the moment the nasty problem of having your memory checker loaded into the bad memory in question, the cache also seriously gets in your way (and I'll bet you never even thought to turn both L1 and L2 caches off, did you? :-) by masking errors in a way which is transparent to the program. How's it supposed to know its accesses are getting cached or how much cache it has to "defeat" to get meaningful access to main memory? It can't, really, at least not in a way that's truly foolproof or workable across the entire range of Intel/AMD CPUs it might be run on, and that's why serious bench techs use hardware memory testers exclusively. I've used all kinds of software memory checkers, from "CheckIt" to highly proprietary packages that cost even more money, and the only thing they managed to convince me of is that swapping in known-good memory is the best and fastest way out of these situations. Unless you have a hardware memory tester available, trying to test it yourself is just too likely to give you a false sense of security and send you down more blind alleys. I've even put known BAD memory into boxes and had CheckIt tell me "looks good to me, boss!", just to verify my suspicion that it had lied to me before. It's also very slow to run a software memory tester without the caches enabled and swapping the memory is generally a whole lot faster than that. I'm impatient. :) So, to summarize, I am actually somewhat against the idea of including tools like this on the grounds that they can also help to convince people of the wrong things while they're debugging a problem. I also don't look forward to having to argue with users who've just run such tests and are still getting signal 11's but now refuse to believe that the memory could be bad because "they checked it." If I then turn around and tell them not to trust the tool I also stuck on the CD for them, they're going to ask why I put it there in the first place and a nice long argument will then ensue instead of us just replacing that damn memory and moving on. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 11:38:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (Postfix) with ESMTP id 34A7037BA25; Fri, 18 Feb 2000 11:37:51 -0800 (PST) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (postal.sr.hp.com [15.4.46.173]) by atlrel2.hp.com (Postfix) with ESMTP id BCB4FF01; Fri, 18 Feb 2000 14:37:39 -0500 (EST) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id LAA05460; Fri, 18 Feb 2000 11:37:37 -0800 (PST) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id LAA08849; Fri, 18 Feb 2000 11:37:32 -0800 (PST) Message-Id: <200002181937.LAA08849@mina.sr.hp.com> To: freebsd-doc@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Recommended addition to FAQ (Troubleshooting) Reply-To: Darryl Okahata In-reply-to: Your message of "Fri, 18 Feb 2000 11:10:38 PST." <79456.950901038@zippy.cdrom.com> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Fri, 18 Feb 2000 11:37:32 -0800 From: Darryl Okahata Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > I've used all kinds of software memory checkers, from "CheckIt" to > highly proprietary packages that cost even more money, and the only > thing they managed to convince me of is that swapping in known-good > memory is the best and fastest way out of these situations. Unless I'll second this. I've had memory problems in the past, and every memory checker I used said that the memory was good. Only by swapping out the bad memory (I don't have access to an hardware memory checker) was I able to fix my problems. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 11:58: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from krell.webweaver.net (krell.webweaver.net [206.24.105.170]) by hub.freebsd.org (Postfix) with ESMTP id DAC2A37BA08; Fri, 18 Feb 2000 11:57:58 -0800 (PST) (envelope-from nicole@unixgirl.com) Received: from xwin.nmhtech.com (xwin.nmhtech.com [208.138.46.10]) by krell.webweaver.net (Postfix) with ESMTP id DA32620F04; Fri, 18 Feb 2000 11:11:43 -0800 (PST) Content-Length: 2127 Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200002181937.LAA08849@mina.sr.hp.com> Date: Fri, 18 Feb 2000 11:57:52 -0800 (PST) From: "Nicole Harrington." To: freebsd-doc@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Recommended addition to FAQ (Troubleshooting) Cc: Darryl Okahata Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Feb-00 Darryl Okahata wrote: > "Jordan K. Hubbard" wrote: > >> I've used all kinds of software memory checkers, from "CheckIt" to >> highly proprietary packages that cost even more money, and the only >> thing they managed to convince me of is that swapping in known-good >> memory is the best and fastest way out of these situations. Unless > > I'll second this. I've had memory problems in the past, and every > memory checker I used said that the memory was good. Only by swapping > out the bad memory (I don't have access to an hardware memory checker) > was I able to fix my problems. > > -- > Darryl Okahata > darrylo@sr.hp.com > Every "good" software based memory tester I have ever used took so long to tell me anything I could have gone to the store, bought more memory, and swapped it before it was done. I don't think adding it to the ports tree would be bad for those who are desperate, but deffinatly list it as a "basic" memory tester. Nicole > DISCLAIMER: this message is the author's personal opinion and does not > constitute the support, opinion, or policy of Agilent Technologies, or > of the little green men that have been following him all day. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message nicole@unixgirl.com |\ __ /| (`\ http://www.unixgirl.com/ webmistress@dangermouse.org | o_o |__ ) ) http://www.dangermouse.org/ // \\ ---------------------------(((---(((----------------------------------------- -- Powered by Coka-Cola and FreeBSD -- -- Stong enough for a man - But made for a Woman -- -- Microsoft: What bug would you like today? -- ------------------------------------------------------------------------------- -- As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 12:20:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from home.gtcs.com (home.gtcs.com [209.181.16.2]) by hub.freebsd.org (Postfix) with ESMTP id C478B37BA6B; Fri, 18 Feb 2000 12:20:24 -0800 (PST) (envelope-from bruce@gtcs.com) Received: from gtcs.com (localhost [127.0.0.1]) by home.gtcs.com (8.8.8/8.8.8) with ESMTP id NAA29729; Fri, 18 Feb 2000 13:19:37 -0700 (MST) (envelope-from bruce@gtcs.com) Message-Id: <200002182019.NAA29729@ home.gtcs.com> Date: Fri, 18 Feb 2000 13:19:32 -0700 (MST) From: Bruce Gingery Reply-To: bgingery@gtcs.com Subject: Re: Recommended addition to FAQ (Troubleshooting) To: "Jordan K. Hubbard" Cc: freebsd-doc@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <79456.950901038@zippy.cdrom.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Feb 2000, Jordan K. Hubbard issued forth a missive of approximately 3647 bytes, entitled "Re: Recommended addition to FAQ (Troubleshooting) ", the text of which in full or in part is quoted here: -} The situation here, I hate to say, is that you were simply very lucky -} in having a software memory tester show you anything at all. -} -} If your experience had been more typical, you would have run memtest86 -} and it would have declared your memory to be free of errors. Then -} you'd have gone right on having problems and losing more hair until -} you finally just came back to the memory and swapped it out on -} suspicion. Bingo, the problems are suddenly fixed and you're dragging -} memtest86 to KDE's trashcan with a resolve to never trust it again. Hmmm, maybe TkDesk's trashcan :) I use Fvwm2. -} The reason why software memory testers are so generally ineffectual is -} that there's a whole bunch of things getting in their way. Leaving -} aside for the moment the nasty problem of having your memory checker -} loaded into the bad memory in question, the cache also seriously gets -} in your way (and I'll bet you never even thought to turn both L1 and -} L2 caches off, did you? :-) [munch] As I understand it, I was getting a report of page faults in kernel on that machine. I KNEW something was wrong, and was quite sure it wasn't the build of FreeBSD :) With the machine nearly a thousand miles from me, it was difficult to tell for sure that I got a good sense of _everything_ that was going on. This is the second time I've had bad RAM since starting to use FreeBSD (and once, previously, while using NeXTstep) and had difficulty in pinning it down. Actually, I tried another (at the time it was DOS based) memory checker the previous occasion which revealed NOTHING, and that's why I was a little quicker to jump to an assumption that it probably WAS bad RAM this time, rather than bad diskettes etc. In simple point of fact, you're right. I did NOT manually disable cache in the BIOS, because it never got that far. The memtest86 runs a series of tests with and without cache... That machine has one bank of 64M and all internal cache, so chip switching wasn't an easy solution, ESPECIALLY at this distance. [quote memtest86 docs] Test 0 [Address test, walking ones, no cache] Test 1 [Moving Inv, ones&zeros, cached] Test 2 [Modulo 20, ones&zeros, cached] Test 3 [Address test, own address, no cache] Test 4 [Moving inv, 8 bit pat, cached] Test 5 [Moving inv, 32 bit pat, cached] Test 6 [Moving inv, ones&zeros, no cache] Test 7 [Modulo 20+, ones&zeros, cached] Test 8 [Moving inv, 8 bit pat, no cache] Test 9 [Modulo 20, 8 bit, cached] Test 10 [Moving inv, 32 bit pat, no cache] (AND) ...test memory using longer refresh rates. This makes is possible to detect marginal errors that otherwise would go undetected with the normal refresh rate. Three refresh rates are available, the normal rate of 15ms, an extended refresh rate of 150ms and an extra long rate of 500ms. The default refresh rate is used for test 0 and tests 1 - 7 use an extended rate of 150ms. The extended tests (8 - 10) use the extra long refresh rate of 500ms. The refresh rate may be overridden at any time via online configuration commands. [end quote] While I FULLY understand your hesitancy, and yes, even if RAM passes all of these tests that is not a sure indication that the RAM is good, but it's a sure problem when it FAILS. reproducably. With my daughter's machine, the errors started showing on test 4, and from what I can tell, about 1/3 of the way up the 64M. A failure at a different point, of course might have given different symptoms, and a failure of a different type might indeed NOT have been detected by memtest86. Also, not all of us are as happy with fingers inside the case as on the keys or pointer, however long we've been at it. :) The reason I was suggesting the second program be run at boot (before multiuser startup) was not to give a false sense of security, but rather one more possible safety margin. I can completely understand your hesitance, and the reasons for it. I do wonder though, if there isn't some way to make it clear to people that this is a precaution, that may be "better than nothing", even if it is not a 100% effective safeguard against hardware malfunctions. It's EXTREMELY difficult to "bootstrap" a hardware test, by using the same hardware that is questionable. I don't really think it could be 100% effective. OTOH, I really DO understand your position on this. I just argued the opposite direction about the Stacheldraht/TFN2K checker for Solaris and Linux which has been put up on the FBI's NIPC site, and with much of the same reasoning you display about this RAM test software. That "signature checker" which is documented as tested on 3 versions of Solaris, and 2 RedHat distributions, but NOT able to handle a.out nor COFF binaries, is (perhaps) worse than nothing at all, because of the false sense of security it might convey. Of course, one additional thing against it is that it's a binary-only distribution that they say _must_be_run_as_root?! (apparently it does direct memory access to loaded code in addition to scanning stored binaries for a recognizable compiled signature?) Am I the only one seeing something windowsey about that? Who gets to make the recurring profits this time for band-aid solutions to a spurting artery. http://www.fbi.gov/nipc/trinoo.htm So I'll leave it up to you. There should be info at least in a FAQ somewhere that indicates that bad RAM is not something that can be ruled out until tested adequately, and perhaps a checklist of symptoms that (virtually) ALWAYS indicate bad RAM, or at least should make it suspect. Bruce Gingery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 14:20:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 3BD1B37BAF3 for ; Fri, 18 Feb 2000 14:20:55 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id OAA12504; Fri, 18 Feb 2000 14:20:47 -0800 (PST) To: freebsd-hackers@freebsd.org, gnu-gcc@gnu.org Subject: Defending against buffer overflows. Date: Fri, 18 Feb 2000 14:20:47 -0800 Message-ID: <12502.950912447@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My attention has just been called to: http://immunix.org/StackGuard/mechanism.html Given all of the buffer overrun vulnerabilities that have been found in various network daemons over time, this seems like a worthwhile sort of technique to apply when compiling, in particular, network daemons and/or servers. I don't entirely agree with this fellow's approach however. I think that the ``canary'' word should be located at the bottom end of the current stack frame, i.e. in a place where no buffer overrun could possibly clobber it. Seems to me that this would be a nice and useful little enhancement for gcc. I wouldn't mind having something like a -fbuffer-overrun-checks option for gcc, and I would definitely use it when compiling network daemons. Anybody else got an opinion? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 14:49:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 2332237BAD7 for ; Fri, 18 Feb 2000 14:49:56 -0800 (PST) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2650.21) id ; Fri, 18 Feb 2000 15:49:55 -0700 Message-ID: <5FE9B713CCCDD311A03400508B8B301303D965@bdr-xcln.is.matchlogic.com> From: Charles Randall To: "Ronald F. Guilmette" , freebsd-hackers@freebsd.org Subject: RE: Defending against buffer overflows. Date: Fri, 18 Feb 2000 15:49:58 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Only on -hackers] With care and a lot of patience, you can build Immunix StackGuard for FreeBSD. I did this on 3.3-R. If there's interest, I can post build instructions (I probably don't have time to put together a port). Charles -----Original Message----- From: Ronald F. Guilmette [mailto:rfg@monkeys.com] Sent: Friday, February 18, 2000 3:21 PM To: freebsd-hackers@freebsd.org; gnu-gcc@gnu.org Subject: Defending against buffer overflows. My attention has just been called to: http://immunix.org/StackGuard/mechanism.html Given all of the buffer overrun vulnerabilities that have been found in various network daemons over time, this seems like a worthwhile sort of technique to apply when compiling, in particular, network daemons and/or servers. I don't entirely agree with this fellow's approach however. I think that the ``canary'' word should be located at the bottom end of the current stack frame, i.e. in a place where no buffer overrun could possibly clobber it. Seems to me that this would be a nice and useful little enhancement for gcc. I wouldn't mind having something like a -fbuffer-overrun-checks option for gcc, and I would definitely use it when compiling network daemons. Anybody else got an opinion? 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 Fri Feb 18 15: 2:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c62443-a.frmt1.sfba.home.com (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 1C37837BAB5 for ; Fri, 18 Feb 2000 15:02:20 -0800 (PST) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id PAA17775 for freebsd-hackers@freebsd.org; Fri, 18 Feb 2000 15:02:19 -0800 Date: Fri, 18 Feb 2000 15:02:19 -0800 From: Arun Sharma To: freebsd-hackers@freebsd.org Subject: Re: 64bit OS? Message-ID: <20000218150219.A17763@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ My apologies if this is a repeat - my earlier mail didn't seem to make it ] On Fri, 18 Feb 2000 12:03:37 +1100, Patryk Zadarnowski wrote: > On the other hand, IA-64 is a very exotic architecture from the OS's > point of view, and anyone planning to port *BSD to it should probably > start planning ASAP. I'm a former Intel employee and I have worked on the Linux IA-64 project. I think there is plenty of planning to do to get an OS running on IA-64, which is more complex than most other architectures I've known. First of all - there is plenty of reading to do: http://developer.intel.com/design/ia-64/manuals/index.htm http://devresource.hp.com/devresource/Docs/Refs/IA64ISA/index.html Some of the design decisions to make: (a) Programming model - LP64 would probably be the most sensible (b) Page table architecture IA-64 supports both the long and short format VHPT (virtual hash page table). Linux chose to use the short format - which really uses no hashing. Linux has the concept of machine independent multi level page tables and has generic algorithms which manipulate them in machine independent code. Where possible, it tries to map them to hardware dependent page tables. On architectures like IA-64 and Power PC, this becomes a little awkward and Linux essentially treats hardware page tables as TLBs. The problem with the above approach is duplication of information between Linux page tables and hardware page tables and inefficient use of memory for page tables. I think OSes like FreeBSD which don't have a concept of machine independent page table are essentially free to do anything in the hat layer and thus have more flexibility. On Linux/IA-64, such duplication is avoided by having a 3 level page table and overloading the L3 page table with the hardware page table functionality. In a nutshell, all L3 page tables are mapped in a region in the *virtual* address space, such that to get the vtop translation for address P, you can just index into this "linear" virtual page table. Because the page table is in *virtual* address space, recursive faults are possible. A significant chunk of the virtual address space has to be reserved for this sparse, linear page table. The other alternative is to use a global hash page table and walk the collision chains in software. The advantage of this scheme is savings in terms of both physical memory and virtual address space, but a heavier dependence on the hardware implemented hashing algorithm's characteristics. It isn't really clear which one is superior, but FreeBSD's VM architecture allows a choice. (c) Handling the register stack on system call entry and exit Sparc has shown how frequent register stack flushing can offset the good effects of register stacks. IA-64 has some nice tricks which can be used to avoid the flush. (d) Restarting of system calls and interactions with the register stack Linux does this by using a gcc directive which was created for this purpose. The normal calling conventions allow input registers to be treated as scratch. But under this directive they will be preserved, so that system calls can be restarted. The disadvantage of this approach is compiler specific code (which Linux has not been averse to in the past) and some register allocation inefficiency in the kernel. The alternate approach is to return ERESTART from the system call, catch the error in libc and restart the system call with saved args. Other general notes: - Writing assembly code is tricky and writing efficient assembly code is trickier - Lots of architectural state to keep track of - Implementing setjmp and longjmp is tricky, because of the interaction with the register stack - Errata, lack of support can be worked around by looking at Linux sources I'd love to have technical discussions about the IA-64 architecture from an OS perspective, if anyone on this list is interested. Since last September, I've moved on to a new daytime job, which has nothing to do with operating systems or kernels. I have a limited amount of spare time and I'm willing to help out with a IA-64 port, if the FreeBSD project decides to pursue it. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 16: 6:59 2000 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 C619C37BAFE for ; Fri, 18 Feb 2000 16:06:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA82061; Fri, 18 Feb 2000 16:06:55 -0800 (PST) (envelope-from dillon) Date: Fri, 18 Feb 2000 16:06:55 -0800 (PST) From: Matthew Dillon Message-Id: <200002190006.QAA82061@apollo.backplane.com> To: Arun Sharma Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? References: <20000218150219.A17763@sharmas.dhs.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :... :and Linux essentially treats hardware page tables as TLBs. : :The problem with the above approach is duplication of information between :Linux page tables and hardware page tables and inefficient use of memory :for page tables. : :I think OSes like FreeBSD which don't have a concept of machine independent :page table are essentially free to do anything in the hat layer and thus :have more flexibility. If I understand the hardware hash table method correctly, then I think the absolute best choice for FreeBSD is to use that method as it will allow us to get rid of the scaleability problems we have with the pv_entry_t scheme we use for IA32. The number of pv_entry_t's in an IA64 architecture wind up being fixed. How big can we make the hardware-assisted hash table? Also, a hash table scheme is a much better fit for a 64 bit address space model, especially with sparse mappings. The MIPS R4K and later all use a hash table scheme and it seems to work well for them. :I'd love to have technical discussions about the IA-64 architecture :from an OS perspective, if anyone on this list is interested. : :Since last September, I've moved on to a new daytime job, which has :nothing to do with operating systems or kernels. I have a limited amount :of spare time and I'm willing to help out with a IA-64 port, if the :FreeBSD project decides to pursue it. : : -Arun : -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 Fri Feb 18 16:41:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 56D6337BB29 for ; Fri, 18 Feb 2000 16:41:26 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA42255; Sat, 19 Feb 2000 11:10:42 +1030 (CST) Date: Sat, 19 Feb 2000 11:10:42 +1030 From: Greg Lehey To: John Milford Cc: Joe Greco , Brooks Davis , peter@netplex.com.au, hackers@FreeBSD.ORG Subject: Re: Filesystem size limit? Message-ID: <20000219111042.I41278@freebie.lemis.com> References: <200002160425.UAA02729@soda.csua.Berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200002160425.UAA02729@soda.csua.Berkeley.edu> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 15 February 2000 at 20:25:50 -0800, John Milford wrote: > Joe Greco wrote: > >>> >>> Joe seem to want one. This size is certaintly within the reach of an >>> ISP now, and disks just keep getting bigger. My administrative bias is >>> that partitioning for a reason other then policy should be avoided and >>> thus I'd love to see filesystem size support keep ahead of volume sizes >>> where possiable. That said, unless someone gives me a very substantial >>> amount of money to build a cluster at work, I'm not going to be building >>> any TB file systems for a few more years. >> >> Well, I just wanted the thrill of it. >> >> I should be building additional machines throughout the year. If anyone is >> seriously interested in work on terabyte filesystem issues, I may be able >> to shanghai one for a month or two and provide access to it. I may even be >> able to push it over the 2TB mark (barely). I do not have the >> qualifications or need to be doing this myself, though, alas. >> >> 72GB disks will be available later this year. Expect 2.6TB servers. :-) > > I will assert that it is insanity to build and use a 1TB UFS > for small files (~ 2.5e8 inodes or 32GB) at least with the current > technology. Maybe I am wrong, if anyone thinks so feel free to tell > me. Having said this I think that Matt's idea of increasing the > effective sector size may be way to go. The "effective sector size" is really the block size. Frags don't count, since there's a maximum of one of them in any file. We already have the facility to create large blocks, but in the current implementation that drags up the size of the frags too, which is not desirable. The real issue is that ufs measures data in (real) sectors, and they have been fixed at (approximately) 512 bytes for a long time. As Matt and I discussed, I think it's more sensible to count in bytes. > Correct me if I am wrong, but the sector size is what has to > change, and not just the block size. This being true it would seem > that if we wanted 2048TB in a FS, we the minimum fragment size would > be 1MB (the virtual sector size) as there would be no way of > addressing anything smaller. If you stuck to 32 bit block numbers. I don't think that's a good idea. Greg -- Finger grog@lemis.com for PGP public key 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 Feb 18 16:42:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id CC22F37BB24; Fri, 18 Feb 2000 16:42:18 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id LAA31077; Sat, 19 Feb 2000 11:41:35 +1100 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200002190041.LAA31077@mycenae.ilion.eu.org> To: "Daniel C. Sobral" Cc: Mike Nowlin , Mike Smith , Steve Kargl , Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-reply-to: Your message of "Fri, 18 Feb 2000 23:45:16 +0900." <38AD5AFC.D3B15771@newsguy.com> Date: Sat, 19 Feb 2000 11:41:35 +1100 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You're being just plain silly. It takes about 5 minutes with the > > manuals to realize just how little AXP and IA-64 have in common: one > > is a classic superscalar out-of-order design, the other is just about > > the opposite: a typical explicit-ILP architecture. What makes IA-64 > > great is the 8 years of statistical analysis of real-life software the > > architecture design team spent fine-tuning the instruction set. What > > makes AXP great is the clock rates Digital/Compaq manages to pump into > > the beasts ;) > > What makes IA-64 great is the fact that it has not been deployed, so > Intel can say whatever it pleases them. > > If you got REAL LIFE NUMBERS, based on REAL LIFE PERFORMANCE, then we > can talk. Let's see how it does Quake, then we can talk. This is rapidly becoming a stupid flame war so in the interest of keeping the list on-topic, I won't be replying publically to this thread from now on. ;) I *do* have some performance figures, as Intel has had the silicon for over six months now, but, of course, Intel being Intel, their lawyers keep everything under a wrap for now. Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 16:53:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 8584037BB22 for ; Fri, 18 Feb 2000 16:53:35 -0800 (PST) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-231.bellatlantic.net [151.198.117.231]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id TAA27390; Fri, 18 Feb 2000 19:53:09 -0500 (EST) Message-ID: <38ADEB48.F11A8B61@bellatlantic.net> Date: Fri, 18 Feb 2000 20:00:56 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Olaf Hoyer Cc: Banu Ozden , freebsd-hackers@FreeBSD.ORG Subject: Re: scsi target mode References: <4.1.20000215005607.00c043c0@mail.rz.fh-wilhelmshaven.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Olaf Hoyer wrote: > > >a. settings on the controller card (e.g. scsi id, termination) > >b. freebsd configuration on the initiator and target PCs. > > (e.g. do we use scsi_pt.c, scsi_target.c, etc). > > > >here's a diagram depicting what we want to do. we're trying to setup > >a PC (PC2 below) with an adaptec controller to act as an emulated disk. > >PC 1 will access the disks on PC 2. > > > > ______________ ______________________________ > >| PC1 | scsi cable | PC2 scsi bus | > >| adaptec 2940 | ================= | adaptec 2940 ======== disk | > >| SCSI ID=7 | | SCSI ID=0 SCSI ID=5 | > >|______________| |______________________________| > > > Hi! > > Well, I'd rather try (for simplification) following combo: > > I won't connect the two 2940 directly. What's the problem ? The only trick is to get termination right: enable it at the ends of the bus and disable it in the middle. Otherwise there is nothing special and I use configurations like this (mupti-path I/O and clusters) routinely at work. Also independently of the location of the cards on the bus you may have to disable the Adaptec BIOS to get the machines booted. But getting the Adaptec working as a target device may be quite tough if possible at all because it's firmware mey not be able of that. The card of choice for target applications is Symbios 8xx. Symbios even provides an example of a simple disk simulator for DOS in theis driver developer's kit. The next obstacle is that AFAIK scsi_target.c is not implementation of a target device. It is a pass-through interface for the host to pas sthe commands to any otherwise un-identified SCSI device. Some time ago I've written the target mode code for the Symbios cards, including a simple disk emulator (to the degree that it looked like a disk but did not store anything written to it) and a SCSI extender through FastEthernet. This was my little private enterprise but now as its commercial value is zero I feel ready to give the code. But the last version to which I ported it was early '98 3.0-current, so it would need considerable efforts to be ported to the current -current. And the software is not of production but of more prototype level of quality: it generally works but if errors or unexpected conditions happen they are not handled well. Actually, I'm even willing to port it, clean up and provide a generic target mode API if the FreeBSD core team would agree to commit it to the system. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 17: 2:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c62443-a.frmt1.sfba.home.com (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 7380F37BB29 for ; Fri, 18 Feb 2000 17:02:15 -0800 (PST) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id RAA18287; Fri, 18 Feb 2000 17:02:14 -0800 Date: Fri, 18 Feb 2000 17:02:14 -0800 From: Arun Sharma To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? Message-ID: <20000218170214.D18203@sharmas.dhs.org> References: <20000218150219.A17763@sharmas.dhs.org> <200002190006.QAA82061@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <200002190006.QAA82061@apollo.backplane.com>; from Matthew Dillon on Fri, Feb 18, 2000 at 04:06:55PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 18, 2000 at 04:06:55PM -0800, Matthew Dillon wrote: > If I understand the hardware hash table method correctly, then > I think the absolute best choice for FreeBSD is to use that method > as it will allow us to get rid of the scaleability problems we have > with the pv_entry_t scheme we use for IA32. The number of pv_entry_t's > in an IA64 architecture wind up being fixed. How big can we make the > hardware-assisted hash table? Smaller than 2**64. Minimum is 2**15. > > Also, a hash table scheme is a much better fit for a 64 bit address > space model, especially with sparse mappings. The MIPS R4K and later > all use a hash table scheme and it seems to work well for them. > Madhu Talluri's paper on page tables for 64 bit address spaces claims that having collision chains is expensive - for 8 bytes of mapping information, the pointer and tag storage overhead is 16 bytes. Though page table space is important, in the age of big memory computers, I think performance and manageability are more important. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 17: 8:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 9625637BB37 for ; Fri, 18 Feb 2000 17:08:19 -0800 (PST) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-231.bellatlantic.net [151.198.117.231]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA28017; Fri, 18 Feb 2000 20:08:10 -0500 (EST) Message-ID: <38ADEECE.94222AB0@bellatlantic.net> Date: Fri, 18 Feb 2000 20:15:58 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Wilko Bulte Cc: David Scheidt , Banu Ozden , freebsd-hackers@FreeBSD.ORG Subject: Re: scsi target mode References: <20000215194322.B597@yedi.iaf.nl> <20000215233939.A6080@yedi.iaf.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > On Tue, Feb 15, 2000 at 04:00:28PM -0600, David Scheidt wrote: > > > > Generally speaking 'joining' machines into cluster(like) you want to > > > use differential SCSI buses. > > > > Yes. Of course, I think that you want to use differential SCSI for > > everything. Cableing is much easier, and much less fussy. It costs more > > though. > > And consumes a bit more power due to all the external diff xceiver chips. > For in-cabinet single-ended or LVD works just fine. http://www.scsipro.com They make the Y-connectors. They also make the retranslators that can increase the maximal length of the cable dramatically (or at least their web site says so - did not try it myself yet). For the good and reasonably priced cables and terminators I can recommend AESP (http://www.aesp.com , http://www.tla-group.com is the reseller I bought from, had quite good experience). Personally I think that Fibre Channel may be a better choice for the clusters because of thinner cables and longer maximal length. Though it's more expensive. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 17:10:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id B825737BB91 for ; Fri, 18 Feb 2000 17:10:34 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id MAA31421; Sat, 19 Feb 2000 12:10:17 +1100 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200002190110.MAA31421@mycenae.ilion.eu.org> To: Matthew Dillon Cc: Arun Sharma , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-reply-to: Your message of "Fri, 18 Feb 2000 16:06:55 -0800." <200002190006.QAA82061@apollo.backplane.com> Date: Sat, 19 Feb 2000 12:10:14 +1100 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :... > :and Linux essentially treats hardware page tables as TLBs. > : > :The problem with the above approach is duplication of information between > :Linux page tables and hardware page tables and inefficient use of memory > :for page tables. > : > :I think OSes like FreeBSD which don't have a concept of machine independent > :page table are essentially free to do anything in the hat layer and thus > :have more flexibility. > > If I understand the hardware hash table method correctly, then > I think the absolute best choice for FreeBSD is to use that method > as it will allow us to get rid of the scaleability problems we have > with the pv_entry_t scheme we use for IA32. The number of pv_entry_t's > in an IA64 architecture wind up being fixed. How big can we make the > hardware-assisted hash table? > > Also, a hash table scheme is a much better fit for a 64 bit address > space model, especially with sparse mappings. The MIPS R4K and later > all use a hash table scheme and it seems to work well for them. Kevin Elphinstone did a PhD thesis on TLB structures for 64 bit address spaces and it turns out that hash tables perform quite poorly. I'd suggest GPTs instead, or maybe LPCtrie that Chris Szmajda has been working on here at UNSW. Both have the advantage of supporting multiple page sizes that IA64 (and Alpha) offer, and hence dramatically increasing the TLB coverage over what Linux (or any other commercial OS that took a bite at IA64) can achieve. Kevin's paper's at: ftp://ftp.cse.unsw.edu.au/pub/users/disy/papers/Elphinstone:phd.ps.gz Maybe that way we can somehow make use of the Itanium's 4GB page size ;)))) Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 18 19:44:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c62443-a.frmt1.sfba.home.com (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 0F38A37BB6D for ; Fri, 18 Feb 2000 19:44:24 -0800 (PST) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id TAA18841; Fri, 18 Feb 2000 19:44:22 -0800 Date: Fri, 18 Feb 2000 19:44:22 -0800 From: Arun Sharma Message-Id: <200002190344.TAA18841@c62443-a.frmt1.sfba.home.com> To: freebsd-hackers@freebsd.org Subject: Re: 64bit OS? In-Reply-To: <200002190110.MAA31421@mycenae.ilion.eu.org> References: <200002190110.MAA31421@mycenae.ilion.eu.org> Reply-To: adsharma@sharmas.dhs.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000 12:10:14 +1100, Patryk Zadarnowski wrote: > > Kevin Elphinstone did a PhD thesis on TLB structures for 64 bit address spaces > and it turns out that hash tables perform quite poorly. I'd suggest GPTs > instead, or maybe LPCtrie that Chris Szmajda has been working on here at UNSW. > Both have the advantage of supporting multiple page sizes that IA64 (and > Alpha) offer, and hence dramatically increasing the TLB coverage over what > Linux (or any other commercial OS that took a bite at IA64) can achieve. > Kevin's paper's at: > ftp://ftp.cse.unsw.edu.au/pub/users/disy/papers/Elphinstone:phd.ps.gz Thanks for the great pointer. IA-64 short format = Linear virtual arrays described in this paper. Long format = conventional hashed page table. Page 116 on LVAs in the paper talks about the disadvantages of using the short format: (a) Increased TLB misses (b) Memory overhead similar to multilevel page tables I don't know if clustered page tables can be implemented with the hardware support present in IA-64. More investigation is needed. > Maybe that way we can somehow make use of the Itanium's 4GB page size ;)))) The best thing is the abilitity to have large pinned TLB entries - they're called TRs (translation registers) in the manuals. Linux for example maps all of kernel memory with one huge TR. This also accomplishes the traditional Linux way of mapping all of physical memory into kernel virtual. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 1: 2: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cairo.anu.edu.au (cairo.anu.edu.au [150.203.224.11]) by hub.freebsd.org (Postfix) with ESMTP id D499F37BC94 for ; Sat, 19 Feb 2000 01:01:53 -0800 (PST) (envelope-from avalon@cairo.anu.edu.au) Received: (from avalon@localhost) by cairo.anu.edu.au (8.9.3/8.9.3) id TAA22462 for hackers@freebsd.org; Sat, 19 Feb 2000 19:52:37 +1100 (EST) From: Darren Reed Message-Id: <200002190852.TAA22462@cairo.anu.edu.au> Subject: post 4.0...adoption of pfil(9) from NetBSD ? To: hackers@freebsd.org Date: Sat, 19 Feb 2000 19:52:37 +1100 (Australia/NSW) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was just having a quick peek at how ipfw works in FreeBSD-4 for IPv6, to see what's required for IP-Filter (hoping for a clean interface) and the response is "sigh". The old ipfw mechanism needs to be abandoned, IMHO. For those that aren't aware, pfil(9) in NetBSD used to provide two lists for filtering IP packets going in.out. It now provides input and output filtering for both IPv4 and IPv6 with the list heads and other meta data stored in protosw, making it possible to further expand to develop UDP/TCP, etc, specific filters at some later time. The only hurdle I can see for FreeBSD is a missing "forward" list, but that's only a minor issue. The advantage to using pfil(9) from NetBSD (unless someone feels the distinct need to roll their own code to do something the same) is it provides a clean interface rather than requiring people to patch things like ip6_input.c, etc. Bringing pfil(9) into FreeBSD is most definately a post FreeBSD-4.0 exercise. Comments ? Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 2:27:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from oskar.dev.nanoteq.co.za (oskar.dev.nanoteq.co.za [196.7.114.5]) by hub.freebsd.org (Postfix) with ESMTP id 6542C37BBCE for ; Sat, 19 Feb 2000 02:27:05 -0800 (PST) (envelope-from rbezuide@oskar.dev.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id MAA17660 for freebsd-hackers@freebsd.org; Sat, 19 Feb 2000 12:26:56 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <200002191026.MAA17660@oskar.dev.nanoteq.co.za> Subject: Reading lpt status register in NIBBLE mode To: freebsd-hackers@freebsd.org Date: Sat, 19 Feb 2000 12:26:56 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... I want to read the status register of the lpt port in NIBBLE mode. I want to do this wether there is a printer connected or not. What would be the best way to accomplish this ?? Should I use the ppi0 device with the PPIGSTATUS ioctl call, because if there is no printer connected I can't open the printer port. Or is there another device on the ppbus that I should rather use. Thanks Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 2:47: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id C40A437BB6B for ; Sat, 19 Feb 2000 02:47:00 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id LAA84458; Sat, 19 Feb 2000 11:46:41 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200002191046.LAA84458@info.iet.unipi.it> Subject: Re: post 4.0...adoption of pfil(9) from NetBSD ? In-Reply-To: <200002190852.TAA22462@cairo.anu.edu.au> from Darren Reed at "Feb 19, 2000 07:52:37 pm" To: Darren Reed Date: Sat, 19 Feb 2000 11:46:41 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was just having a quick peek at how ipfw works in FreeBSD-4 for IPv6, > to see what's required for IP-Filter (hoping for a clean interface) > and the response is "sigh". The old ipfw mechanism needs to be > abandoned, IMHO. can you comment a bit more ? I am a bit unclear on what exactly is thay you don't find appropriate in ipfw etc. If you have an URL for a pfil(9) manpage i would appreciate it. Some comments: The issue of one vs. multiple lists (per direction, interface, protocol, you name it) has been discussed some time ago. For sure multiple lists are a (minor, given that we can start the ipfw lists with a few of "skipto") performance improvement over a single one, at the possible price of having some duplication in writing filters and even defining how many lists are appropriate. > The advantage to using pfil(9) from NetBSD (unless someone feels > the distinct need to roll their own code to do something the same) > is it provides a clean interface rather than requiring people to > patch things like ip6_input.c, etc. I think that if you want to do tricks such as forward, divert, dummynet and the like, it is unavoidable to have to hook in the middle of ${proto}_{input|output}.c, as you end up doing protocol-specific things... cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 4: 1:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cairo.anu.edu.au (cairo.anu.edu.au [150.203.224.11]) by hub.freebsd.org (Postfix) with ESMTP id 8C99A37BBEE for ; Sat, 19 Feb 2000 04:01:07 -0800 (PST) (envelope-from avalon@cairo.anu.edu.au) Received: (from avalon@localhost) by cairo.anu.edu.au (8.9.3/8.9.3) id XAA01927; Sat, 19 Feb 2000 23:01:26 +1100 (EST) From: Darren Reed Message-Id: <200002191201.XAA01927@cairo.anu.edu.au> Subject: Re: post 4.0...adoption of pfil(9) from NetBSD ? To: luigi@info.iet.unipi.it (Luigi Rizzo) Date: Sat, 19 Feb 2000 23:01:26 +1100 (Australia/NSW) Cc: hackers@FreeBSD.ORG In-Reply-To: <200002191046.LAA84458@info.iet.unipi.it> from "Luigi Rizzo" at Feb 19, 2000 11:46:41 AM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some mail from Luigi Rizzo, sie said: > > > I was just having a quick peek at how ipfw works in FreeBSD-4 for IPv6, > > to see what's required for IP-Filter (hoping for a clean interface) > > and the response is "sigh". The old ipfw mechanism needs to be > > abandoned, IMHO. > > can you comment a bit more ? I am a bit unclear on what > exactly is thay you don't find appropriate in ipfw etc. The problem is that the in kernel support for ipfw/ipfilter is *specific* to each. There is no mechanism for 3rd party people to add their own without making the same ugly hacks as already exists unless they choose to use the ipfw/ipfilter hook instead. i.e. each time we want to filter a new protocol we need to hack the various functions for a filter specific hook rather than using a generic filter/calling mechanism. > If you have an URL for a pfil(9) manpage i would appreciate it. See below for man page from 1.4. > Some comments: > > The issue of one vs. multiple lists (per direction, interface, > protocol, you name it) has been discussed some time ago. For sure > multiple lists are a (minor, given that we can start the ipfw lists > with a few of "skipto") performance improvement over a single one, > at the possible price of having some duplication in writing filters > and even defining how many lists are appropriate. To me, this outlines how bad the current system for ipfw support has become. Need something ? Just hack the appropriate part of the kernel. There's no real design in the infrastructure for ipfw. Sort of what Linux was like before they redesigned their firewalling, etc, interfaces using netfilter. I must point out that whilst pfil(9) as found in NetBSD does not provide enough support for the various FreeBSDisms to be put in as it is, I think it can be expanded upon, whilst still supporting the same interface, to meet FreeBSD's needs. Darren PFIL(9) NetBSD Kernel Manual PFIL(9) NAME pfil, pfil_hook_get, pfil_add_hook, pfil_remove_hook - packet filter in- terface SYNOPSIS #include #include #include #include struct packet_filter_hook * pfil_hook_get(int); void pfil_add_hook(int (*func)(), int flags); void pfil_remove_hook(int (*func)(), int flags); DESCRIPTION The pfil interface allows a function to be called on every incoming or outgoing packets. The hooks for these are embedded in the ip_input() and ip_output() routines. The pfil_hook_get() function returns the first member of a particular hook, either the in or out list. The pfil_add_hook() function takes a function of the form below as it's first argument, and the flags for which lists to add the function to. The pos- sible values for these flags are some combination of PFIL_IN and PFIL_OUT. The pfil_remove_hook() removes a hook from the specified lists. The func argument is a function with the following prototype. func(void *data, int hlen, struct ifnet *net, int dir, struct mbuf **m) The data describes the packet. Currently, this may only be a pointer to a ip structure. The net and m arguments describe the network interface and the mbuf holding data for this packet. The dir is the direction; 0 for incoming packets and 1 for outgoing packets. if the function returns non-zero, this signals an error and no further processing of this packet is performed. The function should set errno to indicate the nature of the error. It is the hook's responsibiliy to free the chain if the pack- et is being dropped. The pfil interface is enabled in the kernel via the PFIL_HOOKS option. RETURN VALUES If successful pfil_hook_get() returns the first member of the packet fil- ter list, pfil_add_hook() and pfil_remove_hook() are expected to always succeed. HISTORY The pfil interface first appeared in NetBSD 1.3. The pfil input and out- put lists were originally implemented as LIST structures; however this was changed in NetBSD 1.4 to TAILQ struc- tures. This change was to allow the input and output filters to be pro- cessed in reverse order, to allow the same path to be taken, in or out of the kernel. BUGS The current pfil implementation will need changes to suit a threaded ker- nel model. SEE ALSO bpf(4) NetBSD 1.4 August 4, 1996 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 5:22:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 2FD6037BBC0 for ; Sat, 19 Feb 2000 05:22:37 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id OAA84928; Sat, 19 Feb 2000 14:22:15 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200002191322.OAA84928@info.iet.unipi.it> Subject: Re: post 4.0...adoption of pfil(9) from NetBSD ? In-Reply-To: <200002191201.XAA01927@cairo.anu.edu.au> from Darren Reed at "Feb 19, 2000 11:01:26 pm" To: Darren Reed Date: Sat, 19 Feb 2000 14:22:15 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The issue of one vs. multiple lists (per direction, interface, > > protocol, you name it) has been discussed some time ago. For sure > > multiple lists are a (minor, given that we can start the ipfw lists > > with a few of "skipto") performance improvement over a single one, > > at the possible price of having some duplication in writing filters > > and even defining how many lists are appropriate. > > To me, this outlines how bad the current system for ipfw support > has become. Need something ? Just hack the appropriate part of > the kernel. There's no real design in the infrastructure for hmmm... this criticism, which i partly share, seems unrelated to the single vs. multiple list issue. I agree with you that having a protocol-independent interface for the firewall would be nicer, but then you should also remember that things like divert, forward, tee and possibly also NAT can only be defined as hacks, and as such i am not very optimistic that one can find common mechanisms for calling the filter unless one tolerates some duplication of work. Example: when the filter forwards a packet to somewhere else, you might have to change the route info associated with the packet. When the filter duplicates or steals a packet, the things to do depend a lot on what the rest of the standard function does. E.g ip_input.c, the handling of diverted packets is scattered all around. I don;t know how easy would it be to pack all of this in one place, before or after the proto_input routine. And honestly, once the initial hooks are in the proto_input routine, it is unlikely that you have to touch them anymore. We don't add a protocol stack everyday, i think we have 3 functional ones at the moment. My second comment is on the usefulness of a unified filter. ipfw is clearly IPv4 centric, ip6fw is IP6 centric, and maybe there is no ipxfilter. Why ? because the authors of the 2/3 different filters know enough about their protocol but not enough about the others. Now we can work on each one separately, and at a much higher rate than we could achieve by having a single monolitic filter which people would be scared to touch fearing to break support of some of the other protocols (or, more likely, people would end up adding features to just one of the protos leaving the other ones unchanged). So, in my opinion a merging effort would be a threat to improvement (and the same applies to having to maintain portable software... i guess you know the problem very well with ipfilter!) Of course there are some common functionalities such as (to speak of a couple with which i am very familiar) traffic shaping, or keeping state. But the common infrastructure (a scheduler in the former case) is very very easy to share, while i see much more difficulty in maintaining a single unified filter for all protocols. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 5:51:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cairo.anu.edu.au (cairo.anu.edu.au [150.203.224.11]) by hub.freebsd.org (Postfix) with ESMTP id 85E3B37BC15 for ; Sat, 19 Feb 2000 05:51:43 -0800 (PST) (envelope-from avalon@cairo.anu.edu.au) Received: (from avalon@localhost) by cairo.anu.edu.au (8.9.3/8.9.3) id AAA06539; Sun, 20 Feb 2000 00:52:01 +1100 (EST) From: Darren Reed Message-Id: <200002191352.AAA06539@cairo.anu.edu.au> Subject: Re: post 4.0...adoption of pfil(9) from NetBSD ? To: luigi@info.iet.unipi.it (Luigi Rizzo) Date: Sun, 20 Feb 2000 00:52:01 +1100 (Australia/NSW) Cc: hackers@FreeBSD.ORG In-Reply-To: <200002191322.OAA84928@info.iet.unipi.it> from "Luigi Rizzo" at Feb 19, 2000 02:22:15 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some mail from Luigi Rizzo, sie said: > > > > The issue of one vs. multiple lists (per direction, interface, > > > protocol, you name it) has been discussed some time ago. For sure > > > multiple lists are a (minor, given that we can start the ipfw lists > > > with a few of "skipto") performance improvement over a single one, > > > at the possible price of having some duplication in writing filters > > > and even defining how many lists are appropriate. > > > > To me, this outlines how bad the current system for ipfw support > > has become. Need something ? Just hack the appropriate part of > > the kernel. There's no real design in the infrastructure for > > hmmm... this criticism, which i partly share, seems unrelated to > the single vs. multiple list issue. > > I agree with you that having a protocol-independent interface for > the firewall would be nicer, but then you should also remember that > things like divert, forward, tee and possibly also NAT can only > be defined as hacks, and as such i am not very optimistic that one > can find common mechanisms for calling the filter unless one > tolerates some duplication of work. NAT can easily be implemented as a `filter'. I suspect all of the others you mention (divert/forward/tee) also can be. IP Filter has, for years, supported a "tee-like" feature where it will send a duplicate of a packet out another interface. It may even do "forward" but not "divert"...I don't follow ipfw features very closely O:-) > Example: when the filter forwards a packet to somewhere else, > you might have to change the route info associated with the > packet. When the filter duplicates or steals a packet, the things > to do depend a lot on what the rest of the standard function > does. Changing routing information is not a problem. For starters, with inbound packets, there is none. > E.g ip_input.c, the handling of diverted packets is > scattered all around. I don;t know how easy would it be to > pack all of this in one place, before or after the proto_input > routine. "divert" is just a mess :-) [...] > My second comment is on the usefulness of a unified filter. > ipfw is clearly IPv4 centric, ip6fw is IP6 centric, and maybe there > is no ipxfilter. Just because ipfw/ip6fw are only associated with a single protocol does not mean they can't use a generic interface in place of one specific to them. I think it is short sighted to assume that whatever is there now will be there in X years time or that nobody will want to use their own whatever. By building a generic framework (not that of a unified filer), you support multiple filters out of the box and each can work without any special changes to the kernel. > Why ? because the authors of the 2/3 different filters > know enough about their protocol but not enough about the others. > Now we can work on each one separately, and at a much higher rate than > we could achieve by having a single monolitic filter which people > would be scared to touch fearing to break support of some of the > other protocols (or, more likely, people would end up adding features > to just one of the protos leaving the other ones unchanged). > So, in my opinion a merging effort would be a threat to improvement > (and the same applies to having to maintain portable software... > i guess you know the problem very well with ipfilter!) I'm not saying merge anything. But in the case of ipfilter, easier to merge ipv6 in than create a whole new 'ipfilter6'. > Of course there are some common functionalities such as (to speak > of a couple with which i am very familiar) traffic shaping, or > keeping state. But the common infrastructure (a scheduler in the > former case) is very very easy to share, while i see much more > difficulty in maintaining a single unified filter for all protocols. That depends on how you view and design it, doesn't it ? In so far as IP is concerned, the only significant difference is address size. If you look at how linux's iptables works, there are separate modules for each of ip, tcp, udp, icmp, etc. A packet is filtered by calling the appropriate filter routine for that protocol. In comparison to ipfw which does all its port checking, etc, in `one place'. The idea with pfil(9) as it is in NetBSD now is to allow a filter module to register if it wants to filter inbound (or outbound or both) packets for a given protocol. e.g. I could write a small anti DDoS thing and filter inbound IPv4 packets only and not need to make any changes to the standard kernel source. Using this approach, ipfw would register for in/fwd/out ipv4 packets and ip6fw would register for in/fwd/out ipv6 packets. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 6:59:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 8323C37BC42 for ; Sat, 19 Feb 2000 06:59:49 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id PAA85263; Sat, 19 Feb 2000 15:59:30 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200002191459.PAA85263@info.iet.unipi.it> Subject: Re: post 4.0...adoption of pfil(9) from NetBSD ? In-Reply-To: <200002191352.AAA06539@cairo.anu.edu.au> from Darren Reed at "Feb 20, 2000 00:52:01 am" To: Darren Reed Date: Sat, 19 Feb 2000 15:59:30 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Changing routing information is not a problem. For starters, > with inbound packets, there is none. for outbound there is, and one of the biggest problems i had with dummynet (as an example) was that some code passed around route structures held in the stack, so you couldn't just keep a reference and reuse it later. Bad engineering you can say, and i agree, but fixing this requires fixing the source, not just defining a filter interface. > > E.g ip_input.c, the handling of diverted packets is > > scattered all around. I don;t know how easy would it be to > > pack all of this in one place, before or after the proto_input > > routine. > > "divert" is just a mess :-) i know. But who has the time to fix it! > I'm not saying merge anything. But in the case of ipfilter, easier > to merge ipv6 in than create a whole new 'ipfilter6'. that's up to the maintainer. does not make a big difference (well, maybe just the syntax becomes a bit more complex -- ipfw syntax in this respect is already a mess). > If you look at how linux's iptables works, there are separate modules > for each of ip, tcp, udp, icmp, etc. A packet is filtered by calling > the appropriate filter routine for that protocol. In comparison to > ipfw which does all its port checking, etc, in `one place'. but layer boundaries are just on paper, in reality especially a firewall looks all over the headers (and maybe in even more places). When you filter TCP, you still look at the IP addresses. In ipfw, you can even look at the UID of the associated PCB. By registering filters per protocol at different layers, you have a problem: suppose your rules are the following (in ipfw style, first match wins): 1: deny ip from A to any 2: allow tcp from any 23 to any when you get a TCP packet, when do you invoke the filter, in tcp_input() or in ip_input() ? You should probably do the call at the highest possible level in the stack (TCP in this case), but then you should duplicate rule 1 in the TCP chain or you are in trouble. Furthermore you need hooks in all protocol at all levels, and you depend on upper-level protocols to be implemented properly or filtering fails -- e.g. if the protocol PGM (to name another one i am working on) forgets to call the filter, then all PGM packet will skip the IP check. What we have now in ipfw is a bit more messy (as you do a lot of work trying to classify packets) but at least understanding the ruleset is rather easy, and the places in the kernel where the match is done are more limited. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 9:10:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netfinity.nxos.com (firewall.nxos.com [209.166.45.226]) by hub.freebsd.org (Postfix) with ESMTP id 9117037BC01 for ; Sat, 19 Feb 2000 09:10:23 -0800 (PST) (envelope-from jja@nxos.com) Received: from 0001 ([209.166.45.232]) by netfinity.nxos.com (8.9.3+Sun/8.9.1) with SMTP id RAA24803 for ; Sat, 19 Feb 2000 17:10:13 GMT Message-ID: <006c01bf7afc$c0e2a790$e82da6d1@nxos.com> From: "Jason Allum" To: References: <20000218220138.0BD819B@woodstock.monkey.net> <38AE34D8.F7F88DBA@softweyr.com> Subject: Re: Crypto progress! (And a Biiiig TODO list) Date: Sat, 19 Feb 2000 12:14: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.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Wes Peters" To: "Jon Hamilton" Cc: "Lyndon Nerenberg" ; Sent: Saturday, February 19, 2000 1:14 AM Subject: Re: Crypto progress! (And a Biiiig TODO list) > And how exactly are they supposed to tell the difference between answering > slowly due to breakin evasion vs. answering slowly because the system is > a 386sx/16? > > You would want to answer all "mistakes" slowly, but valid logins quickly. > yup... and any reasonably-malicious software would timeout well before that, and try something else... think multi-threaded, with a "work queue" of tester-threads and a few control threads that "think up" the requests... now imagine a distributed system. ;) i think a better approach might be to "pre-qualify" the requesting-host before even looking at the request itself. this could be done with diffie-hellman in a relatively straight forward manner... and then the door is open to symmetric encryption of the entire challenge/response exchange. if a "qualified" host is ever compromised, and it's dh-key becomes known, the malicious-user still doesn't have access to any other machines... all she has gained is the right to test login/password combinations herself... (which is already offered in the currently-proposed system.) replay attacks could be thwarted by adding timestamps to the exchange. unless a "qualified" hosts key is compromised, the only method that should be open to our DoS friends is at the protocol level (syn-flooding, pipe-filling, etc.) ...and another idea: if the secure connection is kept up over a period of time, additional authentications could be performed... the log information could also be routed over the connection... the authentication server would also have a simple method of determining whether a given host is up or down: do i have a connection, or not? just a thought. - jason allum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 9:18:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netfinity.nxos.com (firewall.nxos.com [209.166.45.226]) by hub.freebsd.org (Postfix) with ESMTP id 9848737BC6C for ; Sat, 19 Feb 2000 09:18:41 -0800 (PST) (envelope-from jja@nxos.com) Received: from 0001 ([209.166.45.232]) by netfinity.nxos.com (8.9.3+Sun/8.9.1) with SMTP id RAA24836 for ; Sat, 19 Feb 2000 17:18:39 GMT Message-ID: <00bd01bf7afd$ee3e2d30$e82da6d1@nxos.com> From: "Jason Allum" To: References: <200002191533.QAA72945@freebsd.dk> Subject: Re: Big ATA problems Date: Sat, 19 Feb 2000 12:22:43 -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.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Soren Schmidt" To: "Jose Gabriel Marcelino" Cc: Sent: Saturday, February 19, 2000 10:33 AM Subject: Re: Big ATA problems > It seems Jose Gabriel Marcelino wrote: > > Well, rebuild the loader, that helped Bryan, apparently it has > nothing to do with the ata driver.... i've had no troubles on my ata-based dell precision 410, running -current (circa -11pm last night). - jason allum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 9:24:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 84B6937BC85 for ; Sat, 19 Feb 2000 09:24:35 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.com (postfix@pC19F5465.dip0.t-ipconnect.de [193.159.84.101]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id SAA05710; Sat, 19 Feb 2000 18:24:48 +0100 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 71943AC26; Sat, 19 Feb 2000 18:25:43 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id SAA18586; Sat, 19 Feb 2000 18:27:01 +0100 (CET) (envelope-from alex) Date: Sat, 19 Feb 2000 18:27:01 +0100 From: Alexander Langer To: Jason Allum Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Big ATA problems Message-ID: <20000219182701.A18510@cichlids.cichlids.com> References: <200002191533.QAA72945@freebsd.dk> <00bd01bf7afd$ee3e2d30$e82da6d1@nxos.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <00bd01bf7afd$ee3e2d30$e82da6d1@nxos.com>; from jja@nxos.com on Sat, Feb 19, 2000 at 12:22:43PM -0500 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Jason Allum (jja@nxos.com): > > It seems Jose Gabriel Marcelino wrote: > > Well, rebuild the loader, that helped Bryan, apparently it has > > nothing to do with the ata driver.... > i've had no troubles on my ata-based dell precision 410, running -current > (circa -11pm last night). Yes, that's because you are using Windows, Windows it not affected by ATA. ;-) Seriously, I have no problems too: alex:~ $ uname -a ; ls -l /boot/loader FreeBSD cichlids.cichlids.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sat Feb 19 09:56:01 CET 2000 alex@cichlids.cichlids.com:/usr/src/sys/compile/cichlids i386 -r-xr-xr-x 1 root wheel 143360 10 Feb 22:58 /boot/loader* Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 9:25:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netfinity.nxos.com (firewall.nxos.com [209.166.45.226]) by hub.freebsd.org (Postfix) with ESMTP id DE64437BC6C for ; Sat, 19 Feb 2000 09:25:19 -0800 (PST) (envelope-from jja@nxos.com) Received: from 0001 ([209.166.45.232]) by netfinity.nxos.com (8.9.3+Sun/8.9.1) with SMTP id RAA24861 for ; Sat, 19 Feb 2000 17:25:13 GMT Message-ID: <00f301bf7afe$d95fa870$e82da6d1@nxos.com> From: "Jason Allum" To: References: <200002191533.QAA72945@freebsd.dk> <00bd01bf7afd$ee3e2d30$e82da6d1@nxos.com> Subject: my bad! Date: Sat, 19 Feb 2000 12:29: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.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG my bad! those were meant for -current... sorry for the mis-post. - jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 10:44:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27]) by hub.freebsd.org (Postfix) with SMTP id BBC3237B9C0 for ; Sat, 19 Feb 2000 10:44:40 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 24528 invoked from network); 19 Feb 2000 18:41:43 -0000 Received: from usercp90.uk.uudial.com (HELO marder-1.) (62.188.156.119) by smtp.dial.pipex.com with SMTP; 19 Feb 2000 18:41:43 -0000 Received: (from mark@localhost) by marder-1. (8.9.3/8.9.3) id SAA00531; Sat, 19 Feb 2000 18:41:00 GMT (envelope-from mark) Date: Sat, 19 Feb 2000 18:41:00 +0000 From: Mark Ovens To: stable@freebsd.org Cc: hackers@freebsd.org Subject: Bug in ioctl() [Was: Help needed with ioctl() calls] Message-ID: <20000219184059.A327@marder-1> References: <20000219145518.C328@marder-1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000219145518.C328@marder-1> Organization: Total lack of Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Firstly, the cross-post to -hackers seems appropriate but my apologies if it isn't. I am now certain that there is a bug in ioctl() (at least for setting the mixer). This started out as an attempt to fix a bug in xmms, but making a debug version of mixer(8) showed it to be affected the same way. The following illustrates the problem, notice that the pcm is nearly always set to a value different to that which is passed on the command-line. I haven't submitted a PR for this as I'm not 100% certain how for something like this. % mixer pcm Mixer pcm is currently set to 91:91 % mixer pcm 90:90 Setting the mixer pcm to 90:90. % mixer pcm Mixer pcm is currently set to 91:91 % mixer pcm 88:88 Setting the mixer pcm to 88:88. % mixer pcm Mixer pcm is currently set to 88:88 % mixer pcm 86:86 Setting the mixer pcm to 86:86. % mixer pcm Mixer pcm is currently set to 88:88 % mixer pcm 84:84 Setting the mixer pcm to 84:84. % mixer pcm Mixer pcm is currently set to 85:85 % On Sat, Feb 19, 2000 at 02:55:18PM +0000, Mark Ovens wrote: > # uname -a > FreeBSD marder-1 3.4-STABLE FreeBSD 3.4-STABLE #0: > Fri Feb 18 18:14:43 GMT 2000 > root@marder-1:/usr/src/sys/compile/MARDER-1 i386 > > > I'm trying to debug a problem in the xmms port whereby the volume > doesn't get set correctly. > > It goes wrong after the ioctl() call to set the volume in /dev/mixer. > > >From /usr/include/machine/soundcard.h: > > #define SOUND_MIXER_PCM 4 > #define MIXER_WRITE(dev) _IOWR('M', dev, int) > #define SOUND_MIXER_WRITE_PCM MIXER_WRITE(SOUND_MIXER_PCM) > > and the code in question is > > int fd, v, l, r; > > fd = open(devname, O_RDONLY); > > l = 90; r = 90; > > v = (r << 8) | l; /* v == 23130 */ > > ioctl(fd, SOUND_MIXER_WRITE_PCM, &v); > > /* now v == 23387, which is (91 << 8) | 91 */ > > Before the ioctl() call the output from mixer(8) was: > > Mixer pcm is currently set to 88:88 > > and after: > > Mixer pcm is currently set to 91:91 > > when it should be 90:90 > > The appears to be a bug in ioctl(), but is it? > > /dev/mixer is being opened read-only but we appear to be writing to it > OK, albeit the wrong values. > > I'm getting a bit out of my depth here so a bit of help would be > appreciated. Is this a bug in ioctl()? If not, any suggestions as to > what I should do now to find the cause of the problem? > > Thanks. > > -- > Microsoft: Where do you want to go today? > Linux: Where do you want to go tomorrow? > BSD: Are you guys coming, or what? > -Poster at LinuxWorld 2000 > ________________________________________________________________ > FreeBSD - The Power To Serve http://www.freebsd.org > My Webpage http://ukug.uk.freebsd.org/~mark/ > mailto:mark@ukug.uk.freebsd.org http://www.radan.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? -Poster at LinuxWorld 2000 ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 11:11:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id ABD4537B70E for ; Sat, 19 Feb 2000 11:11:18 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id OAA97966; Sat, 19 Feb 2000 14:09:09 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sat, 19 Feb 2000 14:09:08 -0500 (EST) From: Chuck Robey To: Bruce Gingery Cc: FreeBSD Hackers List Subject: Re: Recommended addition to FAQ (Troubleshooting) In-Reply-To: <200002182019.NAA29729@ home.gtcs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Bruce Gingery wrote: > So I'll leave it up to you. There should be info at least in > a FAQ somewhere that indicates that bad RAM is not something > that can be ruled out until tested adequately, and perhaps a > checklist of symptoms that (virtually) ALWAYS indicate bad RAM, > or at least should make it suspect. It's *precisely* that attitude that makes up all immediately and completely against recommending any memory tester whatsoever. You apparently didn't read what Jordan told you closely enough to catch the main point: There is *no possible software method* of catching memory errors, with more than a 25% chance of really catching errors! There is NO "checklist of symptoms that (virtually) ALWAYS indicate bad RAM". Jordan wrote you what appears to be good advice. Like many who've posted before you, you can't believe that all the memory test programs you can purchase are all pretty much useless (only catching an extremely small set of huge memory faults). Your first post spoke of getting the memory failure "although it had supposedly passed the BIOS memory tests". BIOS checks only the existence of memory, not it's functionality. The closest you can come to in-home memory checks *IS* memory swapping, and disabling BIOS. Advocating other advice in FAQs means only giving out definitely bad advice. Your own experience, in having a memory tester find the problem, is exceptional, most folks wouldn't have even found it that way. What do you tell to users, when they claim they haven't any memory problem, because they already *used* your recommended memory tester? After all, the memory test program is in your FAQ, it's gotta mean something, right? Folks won't believe you when you tell them it's very nearly worthless. The mere existence of recommendations of memory testers, no matter how you wrap them in warnings, is enough to make users certain that you're lying when you say that they haven't even reduced the odds of a memory fault, in doing their software memory tests. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 11:51:11 2000 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 7FF2237BC43 for ; Sat, 19 Feb 2000 11:51:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA96660; Sat, 19 Feb 2000 11:47:50 -0800 (PST) (envelope-from dillon) Date: Sat, 19 Feb 2000 11:47:50 -0800 (PST) From: Matthew Dillon Message-Id: <200002191947.LAA96660@apollo.backplane.com> To: Arun Sharma Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? References: <20000218150219.A17763@sharmas.dhs.org> <200002190006.QAA82061@apollo.backplane.com> <20000218170214.D18203@sharmas.dhs.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Madhu Talluri's paper on page tables for 64 bit address spaces claims that :having collision chains is expensive - for 8 bytes of mapping information, :the pointer and tag storage overhead is 16 bytes. : :Though page table space is important, in the age of big memory computers, :I think performance and manageability are more important. : : -Arun I wasn't thinking of having collision chains, at least not long ones. But I see what you mean. -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 Sat Feb 19 12:14:54 2000 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 BFFD637BCFE for ; Sat, 19 Feb 2000 12:14:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA96756; Sat, 19 Feb 2000 12:13:25 -0800 (PST) (envelope-from dillon) Date: Sat, 19 Feb 2000 12:13:25 -0800 (PST) From: Matthew Dillon Message-Id: <200002192013.MAA96756@apollo.backplane.com> To: Patryk Zadarnowski Cc: Arun Sharma , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? References: <200002190110.MAA31421@mycenae.ilion.eu.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Kevin Elphinstone did a PhD thesis on TLB structures for 64 bit address spaces :and it turns out that hash tables perform quite poorly. I'd suggest GPTs :instead, or maybe LPCtrie that Chris Szmajda has been working on here at UNSW. :Both have the advantage of supporting multiple page sizes that IA64 (and :Alpha) offer, and hence dramatically increasing the TLB coverage over what :Linux (or any other commercial OS that took a bite at IA64) can achieve. :Kevin's paper's at: :ftp://ftp.cse.unsw.edu.au/pub/users/disy/papers/Elphinstone:phd.ps.gz : :Maybe that way we can somehow make use of the Itanium's 4GB page size ;)))) : :Pat. Linux has a good idea re: mapping all of real memory into KVM, it's just one that doesn't work well on a 32 bit architecture :-). But on a 64 bit architecture it can be seriously useful. At the very least we can get rid of the private pmap pages and make pmap copying a much faster operation. I read Kevin's thesis. Facinating! The GPT concept is essentially a radix tree (and a degenerate version of the radix tree is, of course, the normal two-level page table IA32 uses). All the memory and performance issues Kevin brings up are exactly the same memory and performance issues that a radix tree has. And he is bang-on in regards to node sharing. With a normal page table node sharing is difficult because each page in the page table represents a large area of memory (4MB on IA32). But using a GPT we can potentially node-share the bulk of the pages associated with shared libraries despite there being COW'd pages in the middle of that space from the dynamic linking. -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 Sat Feb 19 14: 0:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cairo.anu.edu.au (cairo.anu.edu.au [150.203.224.11]) by hub.freebsd.org (Postfix) with ESMTP id 736B037BCAA for ; Sat, 19 Feb 2000 14:00:41 -0800 (PST) (envelope-from avalon@cairo.anu.edu.au) Received: (from avalon@localhost) by cairo.anu.edu.au (8.9.3/8.9.3) id JAA28785; Sun, 20 Feb 2000 09:01:02 +1100 (EST) From: Darren Reed Message-Id: <200002192201.JAA28785@cairo.anu.edu.au> Subject: Re: post 4.0...adoption of pfil(9) from NetBSD ? To: luigi@info.iet.unipi.it (Luigi Rizzo) Date: Sun, 20 Feb 2000 09:01:01 +1100 (Australia/NSW) Cc: hackers@FreeBSD.ORG In-Reply-To: <200002191459.PAA85263@info.iet.unipi.it> from "Luigi Rizzo" at Feb 19, 2000 03:59:30 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some mail from Luigi Rizzo, sie said: > > > Changing routing information is not a problem. For starters, > > with inbound packets, there is none. > > for outbound there is, and one of the biggest problems i had > with dummynet (as an example) was that some code passed > around route structures held in the stack, so you couldn't just keep > a reference and reuse it later. Bad engineering you can say, > and i agree, but fixing this requires fixing the source, not > just defining a filter interface. mmm, fixing the source. > > If you look at how linux's iptables works, there are separate modules > > for each of ip, tcp, udp, icmp, etc. A packet is filtered by calling > > the appropriate filter routine for that protocol. In comparison to > > ipfw which does all its port checking, etc, in `one place'. > > but layer boundaries are just on paper, in reality especially a firewall > looks all over the headers (and maybe in even more places). > When you filter TCP, you still look at the IP addresses. In ipfw, you > can even look at the UID of the associated PCB. So ? > By registering filters per protocol at different layers, you have a problem: > suppose your rules are the following (in ipfw style, first match wins): > > 1: deny ip from A to any > 2: allow tcp from any 23 to any > > when you get a TCP packet, when do you invoke the filter, in > tcp_input() or in ip_input() ? You should probably do the call > at the highest possible level in the stack (TCP in this case), > but then you should duplicate rule 1 in the TCP chain or > you are in trouble. Urgh, I see you're not familiar with theirs either. The filtering is invoked from IP (just like ipfw) but rather than do "if tcp then check ports and flags", it does "call per-protocol check". Maybe I'm just not explaining this clearly... > Furthermore you need hooks in all protocol at all levels, and you > depend on upper-level protocols to be implemented properly or > filtering fails -- e.g. if the protocol PGM (to name another one > i am working on) forgets to call the filter, then all PGM packet > will skip the IP check. Huh ? I think you're not understanding what I'm saying. > What we have now in ipfw is a bit more messy (as you do a lot of > work trying to classify packets) but at least understanding the ruleset is > rather easy, and the places in the kernel where the match is done > are more limited. I wouldn't call it "limited" :) There are more ipfw hooks required than ipfilter hooks for basically the same job :-) You would do well to download a linux kernel and see what they do, as well as looking at how NetBSD now handles it. My descriptions have been heavily modified to be concise and are not doing either OS justice. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 14:28:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ab-bg.net (ab-bg.net [212.56.11.129]) by hub.freebsd.org (Postfix) with SMTP id 4D77137BD1F for ; Sat, 19 Feb 2000 14:28:42 -0800 (PST) (envelope-from v0rbiz@ab-bg.net) Received: (qmail 12176 invoked by uid 1000); 19 Feb 2000 22:27:14 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 19 Feb 2000 22:27:14 -0000 Date: Sun, 20 Feb 2000 00:27:14 +0200 (EET) From: Victor Ivanov To: hackers@freebsd.org Subject: Re: Bug in ioctl() [Was: Help needed with ioctl() calls] In-Reply-To: <20000219184059.A327@marder-1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mixer uses 100 levels for each "device" (master volume, pcm, synth, etc), but your hardware maybe uses 64 (or 128). mixer needs to be universal.. so does the ioctl() and the interface to the hardware mixer. Look at the sources in the kernel :)... maybe you'll find something like this (which looses accuracy, but there's no other way): percent = actual * 100 / 64; in this case both 91 and 92 are 58 when measuring 1..64 and this is not a bug :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 17:42:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id 951F137BD56 for ; Sat, 19 Feb 2000 17:42:40 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id MAA03468; Sun, 20 Feb 2000 12:42:16 +1100 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200002200142.MAA03468@mycenae.ilion.eu.org> To: Matthew Dillon Cc: Arun Sharma , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-reply-to: Your message of "Sat, 19 Feb 2000 12:13:25 -0800." <200002192013.MAA96756@apollo.backplane.com> Date: Sun, 20 Feb 2000 12:42:14 +1100 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :Kevin Elphinstone did a PhD thesis on TLB structures for 64 bit address spaces > :and it turns out that hash tables perform quite poorly. I'd suggest GPTs > :instead, or maybe LPCtrie that Chris Szmajda has been working on here at UNSW. > :Both have the advantage of supporting multiple page sizes that IA64 (and > :Alpha) offer, and hence dramatically increasing the TLB coverage over what > :Linux (or any other commercial OS that took a bite at IA64) can achieve. > :Kevin's paper's at: > :ftp://ftp.cse.unsw.edu.au/pub/users/disy/papers/Elphinstone:phd.ps.gz > : > :Maybe that way we can somehow make use of the Itanium's 4GB page size ;)))) > : > :Pat. > > Linux has a good idea re: mapping all of real memory into KVM, it's > just one that doesn't work well on a 32 bit architecture :-). But on > a 64 bit architecture it can be seriously useful. At the very least > we can get rid of the private pmap pages and make pmap copying a much > faster operation. Actually, on IA64 this is not needed at all. The thing is, we've got eight regions accessible simultaneously (sort of like MIPS address space regions, only fully configurable, with per-region page table), so we can always reserve region 0 for user space, 1 for shared libraries, 2 for physical memory and 3 for KVM, and maybe even disable the page table for region 2, and use Keys to grant physical memory access permissions on demand. That way we don't waste TLB (umm... TC) entries for essentially one-to-one mappings. > I read Kevin's thesis. Facinating! The GPT concept is essentially What is even more fascinating about IA-64 that the software TLB that Kevin describes in his thesis can be walked in hardware, and hence can cache variable page sizes (although unfortunately not all the IA-64 pages sizes are supported by VPHT) The only other architecture that offers that is SPARC, but their software TLB supports only 4KB and 64KB page sizes, so all other pages must be reloaded directly from the page table. > a radix tree (and a degenerate version of the radix tree is, of course, > the normal two-level page table IA32 uses). All the memory and > performance issues Kevin brings up are exactly the same memory and > performance issues that a radix tree has. And he is bang-on in > regards to node sharing. With a normal page table node sharing is What's funny is that nobody (to the best of my knowledge) had the guts to implement node sharing or even variable page sizes in GPTs. They're a nightmare to code. Did I mention that we've been using them on MIPS and Alphas for few years now in our research SASOS? (and a few months on StrongARM, and soon on SPARCs ;) So they are field tested, and not just some piece of benchmark-based theorising. > difficult because each page in the page table represents a large area > of memory (4MB on IA32). But using a GPT we can potentially node-share > the bulk of the pages associated with shared libraries despite there > being COW'd pages in the middle of that space from the dynamic linking. LPCtires look even better. Have a look at http://www.cse.unsw.EDU.AU/~cls/cls.thesis.ps.gz they're designed *specifically* to promote variable pages sizes, and Chris claims that adding node sharing to his current implementation (he's got an almost-generic one that works on MIPS 4K, all Alphas and theoretically SPARCs) would be trivial. One more thing about GPTs (I thought I'll leave that till last. ;) Jochen Liedtke holds a German patent on them, although he will probably be fairly easily convinced to give FreeBSD rights to use them. I'll be happy to ask (if we're interested.) Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 17:49:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id CA6A837BD9B for ; Sat, 19 Feb 2000 17:49:27 -0800 (PST) (envelope-from karsten@rohrbach.de) Received: (qmail 81404 invoked by uid 1000); 20 Feb 2000 01:49:26 -0000 Date: Sun, 20 Feb 2000 02:49:26 +0100 From: "Karsten W. Rohrbach" To: freebsd-hackers@freebsd.org Subject: yamaha japan relationships anyone? Message-ID: <20000220024926.B81021@rohrbach.de> Reply-To: karsten@rohrbach.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Arbitrary-Number-Of-The-Day: 42 X-Sender: karsten@rohrbach.de Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi * this might be a little offtopic... i just messaged the guys from yamaha japan for specs on their pci audio chipsets to get some decent documentation to start torturing those ymf744 soundcards. no response. i mailed again. same result. do they actually read their mail or is this an uncommon thing in .jp? if there's anyone out there who can tell me how to talk with these guys please hit me with your suggestions, since i am starting to get very very pissed about this whole yamaha clan and people from several continents telling me to ask someone else in another division of their rotten company... also if you know who to talk to on these issues, i'd appreciate any information about contacts there... /k -- > Sure eating yogurt will improve your sex life. People know that if > you'll eat that stuff, you'll eat anything. http://www.webmonster.de http://www.apache.de http://www.splatterworld.de (NIC-HDL KR433/KR11-RIPE) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 18:39:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c62443-a.frmt1.sfba.home.com (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 638BA37BDC5 for ; Sat, 19 Feb 2000 18:39:29 -0800 (PST) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id SAA23777; Sat, 19 Feb 2000 18:39:19 -0800 Date: Sat, 19 Feb 2000 18:39:19 -0800 From: Arun Sharma To: Patryk Zadarnowski Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? Message-ID: <20000219183919.C23349@sharmas.dhs.org> References: <200002192013.MAA96756@apollo.backplane.com> <200002200142.MAA03468@mycenae.ilion.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <200002200142.MAA03468@mycenae.ilion.eu.org>; from Patryk Zadarnowski on Sun, Feb 20, 2000 at 12:42:14PM +1100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 20, 2000 at 12:42:14PM +1100, Patryk Zadarnowski wrote: > One more thing about GPTs (I thought I'll leave that till last. ;) > Jochen Liedtke holds a German patent on them, although he will > probably be fairly easily convinced to give FreeBSD rights to use > them. I'll be happy to ask (if we're interested.) It looks like the hardware has to implement GPTs and know how to walk them. How can FreeBSD use them without hardware support ? -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 18:49: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id 63DA637BDD0 for ; Sat, 19 Feb 2000 18:48:56 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id NAA03808; Sun, 20 Feb 2000 13:48:51 +1100 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200002200248.NAA03808@mycenae.ilion.eu.org> To: Arun Sharma Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-reply-to: Your message of "Sat, 19 Feb 2000 18:39:19 -0800." <20000219183919.C23349@sharmas.dhs.org> Date: Sun, 20 Feb 2000 13:48:49 +1100 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Feb 20, 2000 at 12:42:14PM +1100, Patryk Zadarnowski wrote: > > One more thing about GPTs (I thought I'll leave that till last. ;) > > Jochen Liedtke holds a German patent on them, although he will > > probably be fairly easily convinced to give FreeBSD rights to use > > them. I'll be happy to ask (if we're interested.) > > It looks like the hardware has to implement GPTs and know how to > walk them. How can FreeBSD use them without hardware support ? No it doesn't. We've got software GPT implementations for both MIPS64 and Alpha, and they're both peform very well in our somewhat hostile SASOS conditions. I'm not sure why you think that a hardware walk is necessary: the only reason why IA-64 walks VPHT in hardware *at all* is to minimize the impact on the pipeline and improve ILP: remember that the IA-64 hardware walk is *advisory* -- that is, the OS still must supply software TLB refill handlers, even if it uses a linear page table. Specifically, even though the simulator may not display that behaviour, Itanium aborts the VPHT walk early in quite a few cornel cases, even if completing the walk would avoid a TLB miss. Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 20:18:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 5729A37BDF3 for ; Sat, 19 Feb 2000 20:18:32 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id UAA21415; Sat, 19 Feb 2000 20:18:30 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38AF6B15.ECEE957D@gorean.org> Date: Sat, 19 Feb 2000 20:18:29 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John and Jennifer Reynolds Cc: freebsd-hackers@freebsd.org Subject: Re: useful addition to mergemaster (patch included)? References: <14458.48604.671302.610902@whale.home-net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John and Jennifer Reynolds wrote: > > Hi all, > > I was tinkering with mergemaster tonight adding in something that seems useful > to me. I track -stable and have found mergemaster very valuable--however, > sometimes choosing 'd' over and over again for things I don't want touched > (like root's .profile or .cshrc or /etc/networks, etc.) can get tedious. I'm catching up on some old email here. You can accomplish exactly the same effect by adding the appropriate $FreeBSD CVS tags to your files. In 4.0 at least there are $FreeBSD tags for all the files mergemaster touches except for /etc/motd (for which I supplied an override in .mergemasterrc) and sendmail.cf, which I'm still thinking about. One of my design goals for mergemaster involved bypassing files that should only have local modifications (i.e., when the CVS tags match) and requiring examination of files that have been modified in the tree since the last local update. Any sort of "automatic" action outside of this environment contradicts my goals. At the same time, if you've noticed something in 4.0 (other than /etc/motd and /etc/sendmail.cf) that isn't covered by a $FreeBSD tag, please let me know. The tags in 3.x aren't quite as far up to date, but that becomes less and less important as time goes on, since we're getting closer to 4.0-Release. (Yes I know that 3.x still has some life...) Thanks for the suggestion, Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 20:40:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 4AE0137BE32 for ; Sat, 19 Feb 2000 20:40:43 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id UAA03867; Sat, 19 Feb 2000 20:38:40 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id UAA27266; Sat, 19 Feb 2000 20:38:40 -0800 Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id UAA05184; Sat, 19 Feb 2000 20:38:32 -0800 (PST) Message-ID: <38AF715D.ED0DAB03@softweyr.com> Date: Sat, 19 Feb 2000 21:45:17 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Chuck Robey Cc: Bruce Gingery , FreeBSD Hackers List Subject: Re: Recommended addition to FAQ (Troubleshooting) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > On Fri, 18 Feb 2000, Bruce Gingery wrote: > > > So I'll leave it up to you. There should be info at least in > > a FAQ somewhere that indicates that bad RAM is not something > > that can be ruled out until tested adequately, and perhaps a > > checklist of symptoms that (virtually) ALWAYS indicate bad RAM, > > or at least should make it suspect. > > It's *precisely* that attitude that makes up all immediately and > completely against recommending any memory tester whatsoever. You > apparently didn't read what Jordan told you closely enough to catch the > main point: > > There is *no possible software method* of catching memory errors, with > more than a 25% chance of really catching errors! Sure there is, and it's included in FreeBSD by default: make -j 8 world ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 20:59: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c62443-a.frmt1.sfba.home.com (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 9137637BE37 for ; Sat, 19 Feb 2000 20:58:57 -0800 (PST) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id UAA25320; Sat, 19 Feb 2000 20:58:50 -0800 Date: Sat, 19 Feb 2000 20:58:50 -0800 From: Arun Sharma To: Patryk Zadarnowski Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? Message-ID: <20000219205850.A24847@sharmas.dhs.org> References: <20000219183919.C23349@sharmas.dhs.org> <200002200248.NAA03808@mycenae.ilion.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <200002200248.NAA03808@mycenae.ilion.eu.org>; from Patryk Zadarnowski on Sun, Feb 20, 2000 at 01:48:49PM +1100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 20, 2000 at 01:48:49PM +1100, Patryk Zadarnowski wrote: > > It looks like the hardware has to implement GPTs and know how to > > walk them. How can FreeBSD use them without hardware support ? > > No it doesn't. We've got software GPT implementations for both MIPS64 and > Alpha, and they're both peform very well in our somewhat hostile SASOS > conditions. I'm not sure why you think that a hardware walk is necessary: For performance reasons and memory efficiency reasons. My understanding of your proposal is - use VHPT as a large in memory TLB and use GPT as operating system's primary page table. Doesn't that involve duplication of information in memory, especially if the hash table is big ? > the only reason why IA-64 walks VPHT in hardware *at all* is to minimize > the impact on the pipeline and improve ILP: I think that's an important reason. A software only TLB miss handler would be inferior to a VHPT based solution on IA-64, IMO. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 21:29: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id 4DB7C37BDF9 for ; Sat, 19 Feb 2000 21:28:58 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id QAA04257; Sun, 20 Feb 2000 16:28:53 +1100 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200002200528.QAA04257@mycenae.ilion.eu.org> To: Arun Sharma Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? In-reply-to: Your message of "Sat, 19 Feb 2000 20:58:50 -0800." <20000219205850.A24847@sharmas.dhs.org> Date: Sun, 20 Feb 2000 16:28:51 +1100 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Feb 20, 2000 at 01:48:49PM +1100, Patryk Zadarnowski wrote: > > > It looks like the hardware has to implement GPTs and know how to > > > walk them. How can FreeBSD use them without hardware support ? > > > > No it doesn't. We've got software GPT implementations for both MIPS64 and > > Alpha, and they're both peform very well in our somewhat hostile SASOS > > conditions. I'm not sure why you think that a hardware walk is necessary: > > For performance reasons and memory efficiency reasons. My understanding of We must be careful here. Although you're getting a samll immediate performance gain by not flushing the pipelines, the performance is killed if the working set is larger than the TLB (as it usually is on a moderately-loaded system, especially in presence of heavy IPC (eg. UNIX pipes)), in which case a smarter data structure will usually increase the TLB coverage. And don't forget that with VHPT you'll be getting nested TLB faults quite frequently in a sparsely-populated page table (think shared libraries). Efficiency-wise, Kevin has shown that you only need a fairly small VPHT, and it is global, so you ammortise the cost across all running tasks. Further, you can easily share a GPT or LPCtrie subtrees, at which stage the whole memory-wastage argument goes completely out of the window (I'm currently writing a microkernel that is intended to demonstrate just that on UltraSPARC which has an MMU vaguely resembling that of IA-64.). Besides, doesn't Linux duplicate the structure anyway even when it uses a hardware-walked page table? Avoiding data duplication isn't always a good thing: as a rule, caching helps. ;) > your proposal is - use VHPT as a large in memory TLB and use GPT as > operating system's primary page table. Precisely. > Doesn't that involve duplication of information in memory, especially if the > hash table is big ? No, not significantly, for two reasons: first, you don't need a huge VPHT -- 512KB is more than enough. Also, VPHT becomes a cache for the actual page table. It's been empirically demonstrated that 64 bit (esp. sparse 64 bit) page tables really need such a cache (software TLB) anyway. And it's the main way Intel planned VPHT to be used in the first place. The performance improvement tends to be significant (look at Kevin's PhD that I've posed before.) Besides, the amount of space saved due to a smarter page table data structure more than compensates for the additional memory anyway. > > the only reason why IA-64 walks VPHT in hardware *at all* is to minimize > > the impact on the pipeline and improve ILP: > > I think that's an important reason. A software only TLB miss handler > would be inferior to a VHPT based solution on IA-64, IMO. It's the only justification Rumi Zahir (head of the IA-64 team) gave me when I was complaining about it. (as in: ``why bother? 64 bit page tables are an open problem and no other 64 bit platform I know of provides a hardware page table walk''. BTW, does anoone know if HP-PA and IBM 64bit PPC implement a hardware PT walk? Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 19 22:53:14 2000 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 324FE37BF41 for ; Sat, 19 Feb 2000 22:53:10 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA99167; Sat, 19 Feb 2000 22:53:02 -0800 (PST) (envelope-from dillon) Date: Sat, 19 Feb 2000 22:53:02 -0800 (PST) From: Matthew Dillon Message-Id: <200002200653.WAA99167@apollo.backplane.com> To: Patryk Zadarnowski Cc: Arun Sharma , freebsd-hackers@FreeBSD.ORG Subject: Re: 64bit OS? References: <200002200528.QAA04257@mycenae.ilion.eu.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :And don't forget that with VHPT you'll be getting nested TLB faults quite :frequently in a sparsely-populated page table (think shared libraries). : :Efficiency-wise, Kevin has shown that you only need a fairly small VPHT, and :it is global, so you ammortise the cost across all running tasks. Further, :you can easily share a GPT or LPCtrie subtrees, at which stage the whole :memory-wastage argument goes completely out of the window (I'm currently :writing a microkernel that is intended to demonstrate just that on UltraSPARC :which has an MMU vaguely resembling that of IA-64.). Besides, doesn't Linux :duplicate the structure anyway even when it uses a hardware-walked page table? Linux uses a 'machine-independant' two or three level page table which is then 'translated' to a machine dependant version. However, for IA32 and any architecture that supports it, they attempt to overlay the machine dependant and machine independant versions so they wind up having only one page table. This pretty much locks linux into a standard hierarchical page table design at least insofar as minimizing memory overhead goes. They can eat it support other architectures, but it doesn't allow them to get rid of the machine independant version of the page table. Linux also stores persistent information in their machine independant page tables. They aren't throw-away like FreeBSD's are. This will give us a huge advantage when we do the IA64 port. :> your proposal is - use VHPT as a large in memory TLB and use GPT as :> operating system's primary page table. : :Precisely. : :> Doesn't that involve duplication of information in memory, especially if the :> hash table is big ? : :No, not significantly, for two reasons: first, you don't need a huge VPHT -- :512KB is more than enough. Also, VPHT becomes a cache for the actual page :table. It's been empirically demonstrated that 64 bit (esp. sparse 64 bit) :page tables really need such a cache (software TLB) anyway. And it's the main In general I like the idea of using a VHPT as an STLB (are we having fun with terminology yet?). It should be possible to do even better by optimizing the TLB entries into variable-length pages. We would have to rewrite the page allocation code to make it practical, but it could be done. Many of the pages we are talking about here are from shared libraries which generally wind up staying permantly resident in memory anyway, which means that the overhead of making them physically contiguous over time is low. This makes the optimization possible. What I would truely love to do would be to get away with not using a GPT at all and instead doing a vm_map_lookup_entry()/vm_page_lookup() (essentially taking a vm_fault), then optimize the vm_map_entry structural hierarchy to look more like a GPT rather then the linear list it currently is. When coupled with an STLB, especially one that can be optimized, I think performance would be extremely good. :way Intel planned VPHT to be used in the first place. The performance :improvement tends to be significant (look at Kevin's PhD that I've posed :before.) Besides, the amount of space saved due to a smarter page table data :structure more than compensates for the additional memory anyway. : :> > the only reason why IA-64 walks VPHT in hardware *at all* is to minimize :> > the impact on the pipeline and improve ILP: :> :> I think that's an important reason. A software only TLB miss handler :> would be inferior to a VHPT based solution on IA-64, IMO. : :It's the only justification Rumi Zahir (head of the IA-64 team) gave me when I :was complaining about it. (as in: ``why bother? 64 bit page tables are an :open problem and no other 64 bit platform I know of provides a hardware page :table walk''. BTW, does anoone know if HP-PA and IBM 64bit PPC implement a :hardware PT walk? : :Pat. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message