From owner-freebsd-hackers Sun Mar 4 1:34:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 7F79437B718 for ; Sun, 4 Mar 2001 01:34:19 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f249YHi27877; Sun, 4 Mar 2001 01:34:17 -0800 (PST) (envelope-from dillon) Date: Sun, 4 Mar 2001 01:34:17 -0800 (PST) From: Matt Dillon Message-Id: <200103040934.f249YHi27877@earth.backplane.com> To: freebsd-hackers@freebsd.org Subject: Machines are getting too damn fast Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was browsing CompUSA today and noticed they were selling Sony VAIO 1.3 and 1.5 GHz desktops, amoung other things. It's amazing how fast processors have gotten just in the last two years! I just had to pick up one of these babies and give it a run through to see how fast the RamBus memory is. I'm suitably impressed, at least when comparing it against other Intel cpu's. Intel is finally getting some decent memory bandwidth. I've included some memory copying tests below. The actual memory bandwidth is 2x what the test reports since it's a copy test. Sony 1.3 GHz Pentium 4 VAIO w/ 128MB RamBus memory (two 64MB RIMMs) 571.20 MBytes/sec (copy) 650 MHz Celleron (HP desktop, DIMM) 114.65 MBytes/sec (copy) 750 MHz P-III (2U VALINUX box, 2-cpu, 1024M ECC-DIMM) 162.20 MBytes/sec (copy) 700 MHz Celeron(?) (1U VALINUX box, 1-cpu, 128MB DIMM) 93.56 MBytes/sec (copy) <---- yuch 550 MHz P-III (4U Dell 2400, 1-cpu, 256MB DIMM) 225.92 MBytes/sec (copy) 600 MHz P-III (2U Dell 2450, 2-cpus, 512MB DIMM)) 228.91 MBytes/sec (copy) I was somewhat disappointed with the VALINUX boxes, I expected them to be on par with the DELLs. In anycase, the Sony VAIO workstation with the RamBus memory blew the field away. The cpu is so fast that a buildworld I did was essentially I/O bound. I'll have to go and buy some more RamBus memory for the thing (it only came with 128MB), which is kinda of annoying seeing as I have a gigabyte worth of DIMMs just sitting on my desk :-( that I can't use. I'm tring to imagine 1.3 GHz. That's over a billion instructions a second. And in a few years with the new chip fab lithography standards it's going to be 10 GHz. We need to find something more interesting then buildworlds to do on these machines. -Matt /* * Attempt to test memory copy speeds. Use a buffer large enough to * defeat the on-cpu L1 and L2 caches. */ #include #include #include #include #include #include #define NLOOP 100 char Buf1[2 * 1024 * 1024]; char Buf2[2 * 1024 * 1024]; int deltausecs(struct timeval *tv1, struct timeval *tv2); int main(int ac, char **av) { int i; double dtime; struct timeval tv1; struct timeval tv2; memset(Buf1, 1, sizeof(Buf1)); for (i = 0; i < 10; ++i) bcopy(Buf1, Buf2, sizeof(Buf1)); gettimeofday(&tv1, NULL); for (i = 0; i < NLOOP; ++i) bcopy(Buf1, Buf2, sizeof(Buf1)); gettimeofday(&tv2, NULL); dtime = (double)deltausecs(&tv1, &tv2); printf("%6.2f MBytes/sec (copy)\n", (double)sizeof(Buf1) * NLOOP / dtime); return(0); } int deltausecs(struct timeval *tv1, struct timeval *tv2) { int usec; usec = (tv2->tv_usec + 1000000 - tv1->tv_usec); usec += (tv2->tv_sec - tv1->tv_sec - 1) * 1000000; return(usec); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 2:54: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.sunflower.com (smtp.sunflower.com [24.124.0.137]) by hub.freebsd.org (Postfix) with ESMTP id B62A137B718 for ; Sun, 4 Mar 2001 02:54:03 -0800 (PST) (envelope-from treznor@sunflower.com) Received: from treznor (dv016s59.lawrence.ks.us [24.124.59.16]) by smtp.sunflower.com (8.9.3/8.9.3) with SMTP id EAA23828; Sun, 4 Mar 2001 04:53:56 -0600 Message-ID: <001001c0a494$d091b920$103b7c18@palisor.yi.org> From: "Tyler K McGeorge" To: "Matt Dillon" , References: <200103040934.f249YHi27877@earth.backplane.com> Subject: Re: Machines are getting too damn fast Date: Sun, 4 Mar 2001 04:21:02 -0600 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 ----- Original Message ----- From: Matt Dillon To: Sent: Sunday, March 04, 2001 3:34 AM Subject: Machines are getting too damn fast | We need to find something more interesting then buildworlds to do on | these machines. Let's just complicate the code more. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 3:39:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from carbon.btinternet.com (carbon.btinternet.com [194.73.73.92]) by hub.freebsd.org (Postfix) with ESMTP id 12F3537B719 for ; Sun, 4 Mar 2001 03:39:13 -0800 (PST) (envelope-from dominic_marks@btinternet.com) Received: from [213.123.128.184] (helo=computer) by carbon.btinternet.com with smtp (Exim 3.03 #83) id 14ZWqv-0006t7-00; Sun, 04 Mar 2001 11:39:05 +0000 From: "Dominic Marks" To: "Tyler K McGeorge" , "Matt Dillon" , Subject: RE: Machines are getting too damn fast Date: Sun, 4 Mar 2001 11:38:39 -0000 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <001001c0a494$d091b920$103b7c18@palisor.yi.org> Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Let's just complicate the code more. Hey it works for Microsoft after all! Perhaps if buildworld takes 3 days even on a an eight CPU AlphaServer FreeBSD will rocket to almost completely domination of the OS market? Then again - maybe not :) Dominic -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Tyler K McGeorge Sent: 04 March 2001 10:21 To: Matt Dillon; freebsd-hackers@FreeBSD.ORG Subject: Re: Machines are getting too damn fast ----- Original Message ----- From: Matt Dillon To: Sent: Sunday, March 04, 2001 3:34 AM Subject: Machines are getting too damn fast | We need to find something more interesting then buildworlds to do on | these machines. Let's just complicate the code more. 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 Mar 4 4:13:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nala.dohd.org (d0030.upc-d.chello.nl [213.46.0.30]) by hub.freebsd.org (Postfix) with ESMTP id F1D0437B718 for ; Sun, 4 Mar 2001 04:13:48 -0800 (PST) (envelope-from freebsd@dohd.org) Received: by nala.dohd.org (Postfix, from userid 1008) id 7ABCDD9C4; Sun, 4 Mar 2001 13:13:41 +0100 (MET) Date: Sun, 4 Mar 2001 13:13:41 +0100 From: Mark Huizer To: freebsd-hackers@freebsd.org Subject: Re: Machines are getting too damn fast Message-ID: <20010304131341.A25688@dohd.org> Mail-Followup-To: Mark Huizer , freebsd-hackers@freebsd.org References: <200103040934.f249YHi27877@earth.backplane.com> <001001c0a494$d091b920$103b7c18@palisor.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001001c0a494$d091b920$103b7c18@palisor.yi.org>; from treznor@sunflower.com on Sun, Mar 04, 2001 at 04:21:02AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 04, 2001 at 04:21:02AM -0600, Tyler K McGeorge wrote: > > ----- Original Message ----- > From: Matt Dillon > To: > Sent: Sunday, March 04, 2001 3:34 AM > Subject: Machines are getting too damn fast > > | We need to find something more interesting then buildworlds to do on > | these machines. > > Let's just complicate the code more. > We could vendor-import win2000? 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 Sun Mar 4 5:13:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from operamail.com (OperaMail.com [199.29.68.79]) by hub.freebsd.org (Postfix) with ESMTP id 0273D37B71C for ; Sun, 4 Mar 2001 05:13:51 -0800 (PST) (envelope-from dansh@operamail.com) X-WM-Posted-At: operamail.com; Sun, 4 Mar 01 08:13:36 -0500 X-WebMail-UserID: dansh Date: Sun, 4 Mar 2001 08:13:36 -0500 From: Dan Shechter To: freebsd-hackers@freebsd.org X-EXP32-SerialNo: 00000000 Subject: Can I pthread with libpcap? Message-ID: <3AD2BBCA@operamail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: InterChange (Hydra) SMTP v3.61.08 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Can I pthread with libpcap? Regards, Dan ------------------------------------------------------------ This e-mail has been sent to you courtesy of OperaMail, a free web-based service from Opera Software, makers of the award-winning Web Browser - http://www.operasoftware.com ------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 9:27:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cx420564-b.tucson1.az.home.com (cx420564-b.tucson1.az.home.com [24.21.112.225]) by hub.freebsd.org (Postfix) with ESMTP id 433C737B718 for ; Sun, 4 Mar 2001 09:27:13 -0800 (PST) (envelope-from fracture@cx420564-b.tucson1.az.home.com) Received: (from fracture@localhost) by cx420564-b.tucson1.az.home.com (8.11.1/8.11.1) id f24AImQ08855 for freebsd-hackers@freebsd.org; Sun, 4 Mar 2001 10:18:48 GMT (envelope-from fracture) Date: Sun, 4 Mar 2001 10:18:47 +0000 From: Jordan DeLong To: freebsd-hackers@freebsd.org Subject: FreeBSD pthreads Message-ID: <20010304101847.A8709@cx420564-b.tucson1.az.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey; I've got a question about the pthread implementation on freebsd. I was looking it over and noticed that the pthread library is green; which is disadvantagous on SMP machines. I found a port of the linux pthreads, but it uses rfork() to create the new threads... Anyway; I was curious if a clone() call is in the works for freebsd 5.0? And if not, is there much interest in getting one at some point, or are there other factors that'd make implemention of one right now more difficult than it would seem? -Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 9:55:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 262A637B719 for ; Sun, 4 Mar 2001 09:55:20 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f24Ht3x24682; Sun, 4 Mar 2001 09:55:03 -0800 (PST) Date: Sun, 4 Mar 2001 09:55:03 -0800 From: Alfred Perlstein To: Jordan DeLong Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD pthreads Message-ID: <20010304095502.N8663@fw.wintelcom.net> References: <20010304101847.A8709@cx420564-b.tucson1.az.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010304101847.A8709@cx420564-b.tucson1.az.home.com>; from fracture@allusion.net on Sun, Mar 04, 2001 at 10:18:47AM +0000 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jordan DeLong [010304 09:27] wrote: > Hey; I've got a question about the pthread implementation on freebsd. I was > looking it over and noticed that the pthread library is green; which is > disadvantagous on SMP machines. I found a port of the linux pthreads, but it > uses rfork() to create the new threads... > > Anyway; I was curious if a clone() call is in the works for freebsd 5.0? And > if not, is there much interest in getting one at some point, or are there other > factors that'd make implemention of one right now more difficult than it would > seem? What's the difference between clone() and rfork()? Last I checked they were pretty much the same. -- -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 Sun Mar 4 9:58:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp3.port.ru (mx3.port.ru [194.67.23.37]) by hub.freebsd.org (Postfix) with ESMTP id ACCEB37B719 for ; Sun, 4 Mar 2001 09:58:24 -0800 (PST) (envelope-from kabaev@mail.ru) Received: from adsl-141-154-120-128.bostma.adsl.bellatlantic.net ([141.154.120.128] helo=kan.dnsalias.net) by smtp3.port.ru with esmtp (Exim 3.14 #24) id 14Zck5-000ETS-00; Sun, 04 Mar 2001 20:56:26 +0300 Received: (from kan@localhost) by kan.dnsalias.net (8.11.2/8.11.2) id f24HuvA01576; Sun, 4 Mar 2001 12:56:57 -0500 (EST) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.7p2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010304101847.A8709@cx420564-b.tucson1.az.home.com> Date: Sun, 04 Mar 2001 12:56:51 -0500 (EST) From: "Alexander N. Kabaev" To: Jordan DeLong Subject: RE: FreeBSD pthreads Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Mar-2001 Jordan DeLong wrote: > Hey; I've got a question about the pthread implementation on freebsd. I was > looking it over and noticed that the pthread library is green; which is > disadvantagous on SMP machines. I found a port of the linux pthreads, but it > uses rfork() to create the new threads... Why do you think that clone syscall on Linux is any different than rfork with appropriate parameters on FreeBSD? > Anyway; I was curious if a clone() call is in the works for freebsd 5.0? And > if not, is there much interest in getting one at some point, or are there > other > factors that'd make implemention of one right now more difficult than it > would > seem? > > -Jordan There is nothing clone syscall can offer which cannot be done with rfork, so implementing it would be a waste of time, IMHO. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 10: 1:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id EAFDD37B71A for ; Sun, 4 Mar 2001 10:01:25 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f24I13P24924; Sun, 4 Mar 2001 10:01:03 -0800 (PST) Date: Sun, 4 Mar 2001 10:01:03 -0800 From: Alfred Perlstein To: "Alexander N. Kabaev" Cc: Jordan DeLong , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD pthreads Message-ID: <20010304100102.O8663@fw.wintelcom.net> References: <20010304101847.A8709@cx420564-b.tucson1.az.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from kabaev@mail.ru on Sun, Mar 04, 2001 at 12:56:51PM -0500 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Alexander N. Kabaev [010304 09:58] wrote: > > On 04-Mar-2001 Jordan DeLong wrote: > > Hey; I've got a question about the pthread implementation on freebsd. I was > > looking it over and noticed that the pthread library is green; which is > > disadvantagous on SMP machines. I found a port of the linux pthreads, but it > > uses rfork() to create the new threads... > > Why do you think that clone syscall on Linux is any different than rfork with > appropriate parameters on FreeBSD? > > > Anyway; I was curious if a clone() call is in the works for freebsd 5.0? And > > if not, is there much interest in getting one at some point, or are there > > other > > factors that'd make implemention of one right now more difficult than it > > would > > seem? > > > > -Jordan > > There is nothing clone syscall can offer which cannot be done with rfork, so > implementing it would be a waste of time, IMHO. Actually, clone() returns to your program with the stack fixed up so that you don't crash immediately, FreeBSD has a way of doing this, it's documented in the manpages and through disucssion on the mailing lists. -- -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 Sun Mar 4 10: 3: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id CC96D37B718 for ; Sun, 4 Mar 2001 10:03:03 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA11298; Sun, 4 Mar 2001 13:02:26 -0500 (EST) Date: Sun, 4 Mar 2001 13:02:25 -0500 (EST) From: Daniel Eischen To: Jordan DeLong Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD pthreads In-Reply-To: <20010304101847.A8709@cx420564-b.tucson1.az.home.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 Sun, 4 Mar 2001, Jordan DeLong wrote: > Hey; I've got a question about the pthread implementation on freebsd. I was > looking it over and noticed that the pthread library is green; which is > disadvantagous on SMP machines. I found a port of the linux pthreads, but it > uses rfork() to create the new threads... > > Anyway; I was curious if a clone() call is in the works for freebsd 5.0? And see rfork_thread(3). A pthreads implementation using it is in the works for 5.0. > if not, is there much interest in getting one at some point, or are there other > factors that'd make implemention of one right now more difficult than it would > seem? -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 10:17:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cx420564-b.tucson1.az.home.com (cx420564-b.tucson1.az.home.com [24.21.112.225]) by hub.freebsd.org (Postfix) with ESMTP id EF47437B719 for ; Sun, 4 Mar 2001 10:17:17 -0800 (PST) (envelope-from fracture@cx420564-b.tucson1.az.home.com) Received: (from fracture@localhost) by cx420564-b.tucson1.az.home.com (8.11.1/8.11.1) id f24B8pk10572; Sun, 4 Mar 2001 11:08:51 GMT (envelope-from fracture) Date: Sun, 4 Mar 2001 11:08:51 +0000 From: Jordan DeLong To: Alfred Perlstein Cc: Jordan DeLong , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD pthreads Message-ID: <20010304110851.A10552@cx420564-b.tucson1.az.home.com> References: <20010304101847.A8709@cx420564-b.tucson1.az.home.com> <20010304095502.N8663@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010304095502.N8663@fw.wintelcom.net>; from bright@wintelcom.net on Sun, Mar 04, 2001 at 09:55:03AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 04, 2001 at 09:55:03AM -0800, Alfred Perlstein wrote: > * Jordan DeLong [010304 09:27] wrote: > > Hey; I've got a question about the pthread implementation on freebsd. I was > > looking it over and noticed that the pthread library is green; which is > > disadvantagous on SMP machines. I found a port of the linux pthreads, but it > > uses rfork() to create the new threads... > > > > Anyway; I was curious if a clone() call is in the works for freebsd 5.0? And > > if not, is there much interest in getting one at some point, or are there other > > factors that'd make implemention of one right now more difficult than it would > > seem? > > What's the difference between clone() and rfork()? Last I checked they > were pretty much the same. clone() wont count against the per uid process limit, right? or maybe it will...... > > -- > -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 Sun Mar 4 10:20:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cx420564-b.tucson1.az.home.com (cx420564-b.tucson1.az.home.com [24.21.112.225]) by hub.freebsd.org (Postfix) with ESMTP id 4BDFB37B718 for ; Sun, 4 Mar 2001 10:20:14 -0800 (PST) (envelope-from fracture@cx420564-b.tucson1.az.home.com) Received: (from fracture@localhost) by cx420564-b.tucson1.az.home.com (8.11.1/8.11.1) id f24BBo910710 for freebsd-hackers@FreeBSD.ORG; Sun, 4 Mar 2001 11:11:50 GMT (envelope-from fracture) Date: Sun, 4 Mar 2001 11:11:50 +0000 From: Jordan DeLong To: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD pthreads Message-ID: <20010304111150.A10676@cx420564-b.tucson1.az.home.com> References: <20010304101847.A8709@cx420564-b.tucson1.az.home.com> <20010304095502.N8663@fw.wintelcom.net> <20010304110851.A10552@cx420564-b.tucson1.az.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010304110851.A10552@cx420564-b.tucson1.az.home.com>; from fracture@allusion.net on Sun, Mar 04, 2001 at 11:08:51AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 04, 2001 at 11:08:51AM +0000, Jordan DeLong wrote: > On Sun, Mar 04, 2001 at 09:55:03AM -0800, Alfred Perlstein wrote: > > * Jordan DeLong [010304 09:27] wrote: > > > Hey; I've got a question about the pthread implementation on freebsd. I was > > > looking it over and noticed that the pthread library is green; which is > > > disadvantagous on SMP machines. I found a port of the linux pthreads, but it > > > uses rfork() to create the new threads... > > > > > > Anyway; I was curious if a clone() call is in the works for freebsd 5.0? And > > > if not, is there much interest in getting one at some point, or are there other > > > factors that'd make implemention of one right now more difficult than it would > > > seem? > > > > What's the difference between clone() and rfork()? Last I checked they > > were pretty much the same. > > clone() wont count against the per uid process limit, right? > > > or maybe it will...... > actually I just realized it'd be incredibly stupid for clone not to count against the per uid process limit hehe. anyway; I guess you're right; rfork() does the trick. > > > > -- > > -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 Sun Mar 4 10:26:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp4.port.ru (mx5.port.ru [194.67.23.40]) by hub.freebsd.org (Postfix) with ESMTP id EC82F37B718 for ; Sun, 4 Mar 2001 10:26:18 -0800 (PST) (envelope-from kabaev@mail.ru) Received: from adsl-141-154-120-128.bostma.adsl.bellatlantic.net ([141.154.120.128] helo=kan.dnsalias.net) by smtp4.port.ru with esmtp (Exim 3.14 #24) id 14ZdCr-0008Gd-00; Sun, 04 Mar 2001 21:26:10 +0300 Received: (from kan@localhost) by kan.dnsalias.net (8.11.2/8.11.2) id f24IOZf07705; Sun, 4 Mar 2001 13:24:35 -0500 (EST) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.7p2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010304100102.O8663@fw.wintelcom.net> Date: Sun, 04 Mar 2001 13:24:34 -0500 (EST) From: "Alexander N. Kabaev" To: Alfred Perlstein Subject: Re: FreeBSD pthreads Cc: freebsd-hackers@FreeBSD.ORG, Jordan DeLong Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, clone() returns to your program with the stack fixed up > so that you don't crash immediately, FreeBSD has a way of doing > this, it's documented in the manpages and through disucssion on > the mailing lists. > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Yes, I know, but LinuxThreads provides nice rfork wrapper everyone can use, so usefullness of the native FreeBSD clone is still questionable. The original message suggested that rfork-based LinuxThreads implementation is somewhat inferior to the 'clone' based one and I was objecting to that. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 10:42:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cx420564-b.tucson1.az.home.com (cx420564-b.tucson1.az.home.com [24.21.112.225]) by hub.freebsd.org (Postfix) with ESMTP id CC98337B718 for ; Sun, 4 Mar 2001 10:42:34 -0800 (PST) (envelope-from fracture@cx420564-b.tucson1.az.home.com) Received: (from fracture@localhost) by cx420564-b.tucson1.az.home.com (8.11.1/8.11.1) id f24BY9d12674; Sun, 4 Mar 2001 11:34:09 GMT (envelope-from fracture) Date: Sun, 4 Mar 2001 11:34:09 +0000 From: Jordan DeLong To: Daniel Eischen Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD pthreads Message-ID: <20010304113409.A12423@cx420564-b.tucson1.az.home.com> References: <20010304101847.A8709@cx420564-b.tucson1.az.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from eischen@vigrid.com on Sun, Mar 04, 2001 at 01:02:25PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 04, 2001 at 01:02:25PM -0500, Daniel Eischen wrote: > On Sun, 4 Mar 2001, Jordan DeLong wrote: > > Hey; I've got a question about the pthread implementation on freebsd. I was > > looking it over and noticed that the pthread library is green; which is > > disadvantagous on SMP machines. I found a port of the linux pthreads, but it > > uses rfork() to create the new threads... > > > > Anyway; I was curious if a clone() call is in the works for freebsd 5.0? And > > see rfork_thread(3). A pthreads implementation using it is in the works > for 5.0. > I just took a look at this. Looks extra cool, hehe. thanks, -Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 11: 1:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imladris.rielhome.conectiva (brutus.conectiva.com.br [200.250.58.146]) by hub.freebsd.org (Postfix) with ESMTP id 4E2BD37B718 for ; Sun, 4 Mar 2001 11:01:16 -0800 (PST) (envelope-from riel@conectiva.com.br) Received: from localhost (IDENT:riel@localhost [127.0.0.1]) by imladris.rielhome.conectiva (8.11.1/8.11.1) with ESMTP id f24IvMK04272; Sun, 4 Mar 2001 15:58:23 -0300 Date: Sun, 4 Mar 2001 15:57:22 -0300 (BRST) From: Rik van Riel X-Sender: riel@imladris.rielhome.conectiva To: Jordan DeLong Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD pthreads In-Reply-To: <20010304111150.A10676@cx420564-b.tucson1.az.home.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 Sun, 4 Mar 2001, Jordan DeLong wrote: > On Sun, Mar 04, 2001 at 11:08:51AM +0000, Jordan DeLong wrote: > > clone() wont count against the per uid process limit, right? > actually I just realized it'd be incredibly stupid for clone not to > count against the per uid process limit It does the exact same check a normal fork() would do, in fact it shares the same code path ;) Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com.br/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 11:18:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.prod.itd.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 0C1AA37B718 for ; Sun, 4 Mar 2001 11:18:15 -0800 (PST) (envelope-from fmela0@sm.socccd.cc.ca.us) Received: from sm.socccd.cc.ca.us (pool0144.cvx15-bradley.dialup.earthlink.net [209.179.44.144]) by scaup.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id LAA11865 for ; Sun, 4 Mar 2001 11:18:14 -0800 (PST) Message-ID: <3AA29546.7D709D6@sm.socccd.cc.ca.us> Date: Sun, 04 Mar 2001 11:19:34 -0800 From: Farooq Mela Reply-To: fmela0@sm.socccd.cc.ca.us X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: pthread_exit proto Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Could someone with CVS write access make the following change in pthread.h void pthread_exit __P((void *)); to void pthread_exit __P((void *)) __dead2; as this function doesnt return and gcc is giving me some annoying warnings ;-) BTW, what is the standard mechanism for submitting a patch such as this. I know this probably isn't the really correct place to post this... --- -farooq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 11:58:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3276F37B718 for ; Sun, 4 Mar 2001 11:58:13 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f24JwCi27817; Sun, 4 Mar 2001 11:58:12 -0800 (PST) Date: Sun, 4 Mar 2001 11:58:11 -0800 From: Alfred Perlstein To: Farooq Mela Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pthread_exit proto Message-ID: <20010304115811.Q8663@fw.wintelcom.net> References: <3AA29546.7D709D6@sm.socccd.cc.ca.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AA29546.7D709D6@sm.socccd.cc.ca.us>; from fmela0@sm.socccd.cc.ca.us on Sun, Mar 04, 2001 at 11:19:34AM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Farooq Mela [010304 11:18] wrote: > > Hi, > > Could someone with CVS write access make the following change in > pthread.h > > void pthread_exit __P((void *)); > > to > > void pthread_exit __P((void *)) __dead2; > > as this function doesnt return and gcc is giving me some annoying > warnings ;-) > > BTW, what is the standard mechanism for submitting a patch such as > this. I know this probably isn't the really correct place to post > this... using send-pr: http://www.freebsd.org/support.html#gnats Is '__dead2' a GNU C thing? or is in any sort of standard? Generally there's some resistance to putting GNU C specific code into the base system, is there a portable way to do this? -- -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 Sun Mar 4 12: 8:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.prod.itd.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id D4E2D37B718 for ; Sun, 4 Mar 2001 12:08:50 -0800 (PST) (envelope-from fmela0@sm.socccd.cc.ca.us) Received: from sm.socccd.cc.ca.us (pool0144.cvx15-bradley.dialup.earthlink.net [209.179.44.144]) by scaup.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id MAA20173; Sun, 4 Mar 2001 12:08:46 -0800 (PST) Message-ID: <3AA2A11F.D2CCE631@sm.socccd.cc.ca.us> Date: Sun, 04 Mar 2001 12:10:07 -0800 From: Farooq Mela Reply-To: fmela0@sm.socccd.cc.ca.us X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pthread_exit proto References: <3AA29546.7D709D6@sm.socccd.cc.ca.us> <20010304115811.Q8663@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: > > * Farooq Mela [010304 11:18] wrote: > > > > Hi, > > > > Could someone with CVS write access make the following change in > > pthread.h > > > > void pthread_exit __P((void *)); > > > > to > > > > void pthread_exit __P((void *)) __dead2; > > > > as this function doesnt return and gcc is giving me some annoying > > warnings ;-) > > > > BTW, what is the standard mechanism for submitting a patch such as > > this. I know this probably isn't the really correct place to post > > this... > > using send-pr: > http://www.freebsd.org/support.html#gnats > > Is '__dead2' a GNU C thing? or is in any sort of standard? > > Generally there's some resistance to putting GNU C specific > code into the base system, is there a portable way to do this? > > -- > -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 Erm... not really... __dead2, __unused, and even __pure2 are littered throughout FreeBSD's header files... nothing wrong with them being there as if the compiler being used is not GCC they are #define'd to nothing. If there is some resistance to putting GCC-specific stuff in the system, its news to me, because these attributes are used all over the place for stuff like exit, _exit, abort, etc. I see nothing wrong with using this GCC extension. -- -farooq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 12:14:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.prod.itd.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 3E83A37B719 for ; Sun, 4 Mar 2001 12:14:17 -0800 (PST) (envelope-from fmela0@sm.socccd.cc.ca.us) Received: from sm.socccd.cc.ca.us (pool0144.cvx15-bradley.dialup.earthlink.net [209.179.44.144]) by scaup.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id MAA06092; Sun, 4 Mar 2001 12:14:15 -0800 (PST) Message-ID: <3AA2A268.111D5261@sm.socccd.cc.ca.us> Date: Sun, 04 Mar 2001 12:15:36 -0800 From: Farooq Mela Reply-To: fmela0@sm.socccd.cc.ca.us X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pthread_exit proto References: <3AA29546.7D709D6@sm.socccd.cc.ca.us> <20010304115811.Q8663@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: > Is '__dead2' a GNU C thing? or is in any sort of standard? See /usr/include/sys/cdefs.h __dead2 is defined to __attribute__((__noreturn__)) if a suitable version of GCC is being used. > Generally there's some resistance to putting GNU C specific > code into the base system, is there a portable way to do this? It's not actually gcc-specific code, its more of a hint to the compiler to not warn about something like, main() "falling off the end" when there is actually an exit(0); at the end of it. If GCC knows exit() never returns to its caller it doesnt warn. -- -farooq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 12:28:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 77F9F37B719 for ; Sun, 4 Mar 2001 12:28:52 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f24KSpj28640; Sun, 4 Mar 2001 12:28:51 -0800 (PST) Date: Sun, 4 Mar 2001 12:28:51 -0800 From: Alfred Perlstein To: Farooq Mela Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pthread_exit proto Message-ID: <20010304122851.R8663@fw.wintelcom.net> References: <3AA29546.7D709D6@sm.socccd.cc.ca.us> <20010304115811.Q8663@fw.wintelcom.net> <3AA2A268.111D5261@sm.socccd.cc.ca.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AA2A268.111D5261@sm.socccd.cc.ca.us>; from fmela0@sm.socccd.cc.ca.us on Sun, Mar 04, 2001 at 12:15:36PM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Farooq Mela [010304 12:14] wrote: > Alfred Perlstein wrote: > > > Is '__dead2' a GNU C thing? or is in any sort of standard? > > See /usr/include/sys/cdefs.h > > __dead2 is defined to __attribute__((__noreturn__)) if a suitable > version of GCC is being used. > > > Generally there's some resistance to putting GNU C specific > > code into the base system, is there a portable way to do this? > > It's not actually gcc-specific code, its more of a hint to the compiler > to not warn about something like, main() "falling off the end" when > there is actually an exit(0); at the end of it. If GCC knows exit() > never returns to its caller it doesnt warn. I understood what it did, I just needed some reference to make sure it was being used in other places as an acceptable option. Thanks, this is what I was expecting you to provide, I'll commit the fix rsn. -- -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 Sun Mar 4 13: 6:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id DE7FB37B71C for ; Sun, 4 Mar 2001 13:06:42 -0800 (PST) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.9.0/8.8.7) with ESMTP id VAA12511 for ; Sun, 4 Mar 2001 21:06:41 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Sun, 4 Mar 2001 21:06:41 +0000 (GMT) From: "E.B. Dreger" To: freebsd-hackers@FreeBSD.ORG Subject: Re: pthread_exit proto In-Reply-To: <3AA2A268.111D5261@sm.socccd.cc.ca.us> 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 > Date: Sun, 04 Mar 2001 12:15:36 -0800 > From: Farooq Mela > > It's not actually gcc-specific code, its more of a hint to the compiler > to not warn about something like, main() "falling off the end" when > there is actually an exit(0); at the end of it. If GCC knows exit() > never returns to its caller it doesnt warn. Much like Borland's "#pragma" directives for the WinDos world. Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division E-Mail: eddy@everquick.net Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 13: 9:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from taupo.cs.waikato.ac.nz (taupo.cs.waikato.ac.nz [130.217.241.30]) by hub.freebsd.org (Postfix) with ESMTP id 3166037B718 for ; Sun, 4 Mar 2001 13:09:44 -0800 (PST) (envelope-from joerg@taupo.cs.waikato.ac.nz) Received: (from joerg@localhost) by taupo.cs.waikato.ac.nz (8.11.1/8.11.1) id f24L9aj95955; Mon, 5 Mar 2001 10:09:36 +1300 (NZDT) (envelope-from joerg) Date: Mon, 5 Mar 2001 10:09:36 +1300 From: Joerg Micheel To: Dan Shechter Cc: freebsd-hackers@freebsd.org Subject: Re: Can I pthread with libpcap? Message-ID: <20010305100936.E82784@cs.waikato.ac.nz> References: <3AD2BBCA@operamail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3AD2BBCA@operamail.com>; from dansh@operamail.com on Sun, Mar 04, 2001 at 08:13:36AM -0500 Organization: Dept of Computer Science, University of Waikato, Hamilton, New Zealand Project: WAND - Waikato Applied Network Dynamics, DAG Operating-System: ... powered by FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 04, 2001 at 08:13:36AM -0500, Dan Shechter wrote: > Can I pthread with libpcap? I doubt it, but you might want to talk to Bill Fenner. Also see www.tcpdump.org. Joerg -- Joerg B. Micheel Email: WAND and NLANR MOAT Email: The University of Waikato, CompScience Phone: +64 7 8384794 Private Bag 3105 Fax: +64 7 8585095 Hamilton, New Zealand Plan: PMA, TINE and the DAG's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 13:39:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id BA81E37B71B for ; Sun, 4 Mar 2001 13:39:22 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@dhcp152.geekhouse.net [192.168.1.152]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f24Le8183772; Sun, 4 Mar 2001 13:40:08 -0800 (PST) (envelope-from jhb@FreeBSD.org) 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: <20010304115811.Q8663@fw.wintelcom.net> Date: Sun, 04 Mar 2001 13:38:58 -0800 (PST) From: John Baldwin To: Alfred Perlstein Subject: Re: pthread_exit proto Cc: freebsd-hackers@FreeBSD.org, Farooq Mela Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Mar-01 Alfred Perlstein wrote: > * Farooq Mela [010304 11:18] wrote: >> >> Hi, >> >> Could someone with CVS write access make the following change in >> pthread.h >> >> void pthread_exit __P((void *)); >> >> to >> >> void pthread_exit __P((void *)) __dead2; >> >> as this function doesnt return and gcc is giving me some annoying >> warnings ;-) >> >> BTW, what is the standard mechanism for submitting a patch such as >> this. I know this probably isn't the really correct place to post >> this... > > using send-pr: > http://www.freebsd.org/support.html#gnats > > Is '__dead2' a GNU C thing? or is in any sort of standard? > > Generally there's some resistance to putting GNU C specific > code into the base system, is there a portable way to do this? Err, __dead2 is a macro. For gcc we define it to something useful, and for other compilers we just define it as nothing. The kernel code uses this for things like exit1(), etc. It's in . Some other kernel functions that need it if they don't have it are kthread_exit() and sigexit(). -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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 Sun Mar 4 14:30:45 2001 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 D17DE37B71A; Sun, 4 Mar 2001 14:30:39 -0800 (PST) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-135-94.nnj.dialup.bellatlantic.net [151.198.135.94]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id RAA25111; Sun, 4 Mar 2001 17:30:01 -0500 (EST) Message-ID: <3AA2C1E8.85E6B318@bellatlantic.net> Date: Sun, 04 Mar 2001 17:30:00 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Doug Barton Cc: Neil Blakey-Milner , Matt Dillon , John Gregor , Gerhard.Sittig@gmx.net, leifn@neland.dk, freebsd-hackers@FreeBSD.org, gjb@gbch.net, Kevin Way Subject: cron and daylight time - revisited References: <200101140244.f0E2i3518278@vieo.com> <3A621ABF.FA2C6432@bellatlantic.net> <200101142155.f0ELtLO64117@earth.backplane.com> <3A6A059C.486F6237@bellatlantic.net> <20010120235412.A42508@rapier.smartspace.co.za> <3A6B3D85.9773C9ED@bellatlantic.net> <3A6B46DF.7BE84F45@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All, I have produced another version of the time zone changes in cron. I ran a few tests and plan to commit it to -current after a bit more testing. Everyone who wants to join the testing efforts is welcome. The comments are welcome as well. The new behavior is enabled by the option "-s", without this option the old behavior is preserved. The files are available from http://people.freebsd.org/~babkin/cron/ cron.df - context diff ct - my test crontab testdst - the test script called from this crontab dst_st.log - log of switch-over from summer time to winter time st_dst1.log - log of switch-over from winter time to summer time, with cron resterted before 1:00 st_dst2.log - log for the same switch but with cron resterted at 1:58 The logic is generally the same as in my previous attempt (see cron.8 version 1.13 in the CVS tree) with the following differences: - new option "-o" that enables the old behavior. This behavior is default now but it makes a pre-defined way to guarantee the same behavior in future in case if the default would change. - no more limitation of one-hour granularities for the time zone changes - handling of the ends ranges which fall into a disappearing time interval is more complicated. Sa can be seen from the st_dst* logs they depend on whether these jobs actually ran within one hour before the disappearing interval. So the crontab line 0 1-2 * * * /home/cron/testdst at one to two range OCLOCK as well as its equivalent 0 1,2 * * * /home/cron/testdst at one to two range OCLOCK on a switch from 2:00 ST to 3:00 DST would not normally run because it ran an hour ago, so it falls under the general ranges rule (see cron(8)) and does not run at 3:00DST (which is the same as 2:00ST). But if cron was restarted or crontab reloaded between 1:00 and 2:00 then this knowledge would be lost and the command would be executed at 3:00DST as well. I don't quite like that but I see no easy and efficient way to check if some command would have run within an hour before its next scheduled run. This time is a fixed hour rather than the difference in offset from GMT because all the commands in cron run by hours (possibly, at multiple minute values, but all the minute values repeat for all the listed hour values). -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 15:30:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-158.dsl.lsan03.pacbell.net [63.207.60.158]) by hub.freebsd.org (Postfix) with ESMTP id 4317337B718; Sun, 4 Mar 2001 15:30:50 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E7CA866B09; Sun, 4 Mar 2001 15:30:49 -0800 (PST) Date: Sun, 4 Mar 2001 15:30:49 -0800 From: Kris Kennaway To: David Xu Cc: freebsd-hackers@FreeBSD.org, freebsd-questions@FreeBSD.org Subject: Re: today cvsup and netstat broken Message-ID: <20010304153049.A38220@mollari.cthul.hu> References: <13013690696.20010302123133@163.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <13013690696.20010302123133@163.net>; from bsddiy@163.net on Fri, Mar 02, 2001 at 12:31:33PM +0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 02, 2001 at 12:31:33PM +0800, David Xu wrote: >=20 >=20 > I have cvsuped 4.2-STABLE today, make buildword and mergemaster, > after reboot, netstat no longer show TCP connections: You didn't say that you built a new kernel: did you? Kris --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6otApWry0BWjoQKURAnAQAJwIQxoqnO7Nv/dsk18KgZbuaK6yqwCcDGGV 9F8dkWDXPGyJI6GsuCP7smw= =qXG7 -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 15:34:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 6603F37B71B for ; Sun, 4 Mar 2001 15:34:05 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f24NXqZ18318; Sun, 4 Mar 2001 15:33:52 -0800 Date: Sun, 4 Mar 2001 15:33:52 -0800 From: Brooks Davis To: Alfred Perlstein Cc: Farooq Mela , freebsd-hackers@FreeBSD.ORG Subject: Re: pthread_exit proto Message-ID: <20010304153352.A8837@Odin.AC.HMC.Edu> References: <3AA29546.7D709D6@sm.socccd.cc.ca.us> <20010304115811.Q8663@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="PNTmBPCT7hxwcZjr" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010304115811.Q8663@fw.wintelcom.net>; from bright@wintelcom.net on Sun, Mar 04, 2001 at 11:58:11AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 04, 2001 at 11:58:11AM -0800, Alfred Perlstein wrote: > using send-pr: > http://www.freebsd.org/support.html#gnats >=20 > Is '__dead2' a GNU C thing? or is in any sort of standard? >=20 > Generally there's some resistance to putting GNU C specific > code into the base system, is there a portable way to do this? __dead2 is the FreeBSD (BSD?) way of writing this. It's an attempt to do so in a way that can be compiler independent, but in reality it's not. Microsoft supports something like __dead2, but places the modifer before the delceration in an __declspec() macro so __dead2 won't work. They do not provide any format string checking at all. Other vendors (Sun and SGI for example) provide format string checking via magic comments on the line before the function, but no support for functions that don't return. As someone else pointed out, some compilers provide this via the #pragma stuff, but you can't use any pragmas but the ones defined by the ANSI/ISO standard in portable code and you can't use #ifdef's to shield them. Since we're already using __dead2 and __printflike type things all over the source, we might as well keep doing so, but fundamentaly this stuff is GCC specific. ANSI/ISO screwed us on this one. :-( Either the GCC or Microsoft option would be fine, but without a standard we're pretty screwed. I've got code that gets developed with both GCC and Visual C compilers which least to crap like this: /* * GCC (and some other compilers) define '__attribute__'; we're using this * macro to alert the compiler to flag inconsistencies in printf/scanf-like * function calls. Just in case '__attribute__' isn't defined, make a dumm= y. * G++ doesn't accept it anyway. */ #if !defined(__GNUC__) && !defined(__attribute__) #define __attribute__(p) /* nothing */ #endif /* * Microsoft and Borland use __declspec for purposes similar to GCC's * __attribute__ support. Unfortunatly, the use it before the * decleration rather then after it so we need to define it seperatly. * Also, they don't support printf or scanf format checking. */ #if !((defined(_MSC_VER) && defined(_WIN32)) || (defined(__BORLANDC__) && define d(__WIN32__))) #define __declspec(p) /* nothing */ #endif __declspec(noreturn) void casp_error(const char *format, ...) __attribute__ ((__noreturn__)) __attribute__ ((__format__ (__printf__, 1, 2))); Actually, that should probably have a magic comment as well so support SGI and Sun format checking, but I just couldn't bring my self to add that as well since those are operation platforms not dev platforms. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6otDfXY6L6fI4GtQRAgMuAJ9Xg2+YL9SfI5YN5BrOQ6CcHsd7fQCeLxlJ ekT3dpuA7OdN/4BBp5oQwX4= =pjS/ -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 17:41:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from uucphost.mcs.net (Kitten2.mcs.com [192.160.127.90]) by hub.freebsd.org (Postfix) with ESMTP id F229E37B719 for ; Sun, 4 Mar 2001 17:41:08 -0800 (PST) (envelope-from dgobe@mcs.net) Received: from mcs.net (dgobe.pr.mcs.net [204.137.234.195]) (authenticated) by uucphost.mcs.net (8.11.1/8.11.1) with ESMTP id f251ePW42524; Sun, 4 Mar 2001 19:40:31 -0600 (CST) (envelope-from dgobe@mcs.net) Message-ID: <3AA2EE3D.17B01E8E@mcs.net> Date: Sun, 04 Mar 2001 19:39:09 -0600 From: "David A. Gobeille" X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Tyler K McGeorge Cc: Matt Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: Machines are getting too damn fast References: <200103040934.f249YHi27877@earth.backplane.com> <001001c0a494$d091b920$103b7c18@palisor.yi.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tyler K McGeorge wrote: > > ----- Original Message ----- > From: Matt Dillon > To: > Sent: Sunday, March 04, 2001 3:34 AM > Subject: Machines are getting too damn fast > > | We need to find something more interesting then buildworlds to do on > | these machines. > > Let's just complicate the code more. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message How about bw/s -- buildworlds per second ;-) It would also be interesting to see the numbers for an Athlon/PIII system with DDR, if anyone has such a machine. -- Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 19:52: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from evil.blunt.yi.org (ip-216-23-55-190.adsl.one.net [216.23.55.190]) by hub.freebsd.org (Postfix) with ESMTP id D4B4537B718 for ; Sun, 4 Mar 2001 19:51:55 -0800 (PST) (envelope-from cokane@evil.blunt.yi.org) Received: (from cokane@localhost) by evil.blunt.yi.org (8.11.3/8.11.2) id f2543hG04034; Sun, 4 Mar 2001 23:03:43 -0500 (EST) (envelope-from cokane) Date: Sun, 4 Mar 2001 23:03:42 -0500 From: Coleman Kane To: Matt Dillon Cc: freebsd-hackers@freebsd.org Subject: Re: Machines are getting too damn fast Message-ID: <20010304230342.A3870@cokane.yi.org> References: <200103040934.f249YHi27877@earth.backplane.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" X-Mailer: Mutt 1.0.1i In-Reply-To: <200103040934.f249YHi27877@earth.backplane.com>; from dillon@earth.backplane.com on Sun, Mar 04, 2001 at 01:34:17AM -0800 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable You should see what speed RamBus they were using, 600 or 800 Mhz. It is pretty fast for large memory writes and reads. It'd be cool to see how the different speeds stack up against one another. DDR comparisons would be cool too. Yeah, for the frequency, you have to take into account that these are different chips than your PIII or Athlons and the performance difference is not simply a linear relation to the frequency rating (i.e.: 1.3Ghz is not really over one-billion instructions per second, just clocks per second). We installed Linux at a UC Free OS User Group installfest here in cincinnati, it was pretty sweet. The machine was a Dell and the case was freakin' huge. It also came with a 21" monitor and stuff. The performace was really good, but not really any better than I hads gleaned from the newer 1Ghz Athlons or PIII's. Matt Dillon had the audacity to say: >=20 > I was browsing CompUSA today and noticed they were selling Sony > VAIO 1.3 and 1.5 GHz desktops, amoung other things. It's amazing > how fast processors have gotten just in the last two years! I just > had to pick up one of these babies and give it a run through to see > how fast the RamBus memory is. >=20 > I'm suitably impressed, at least when comparing it against other Intel > cpu's. Intel is finally getting some decent memory bandwidth. I've > included some memory copying tests below. The actual memory bandwidth > is 2x what the test reports since it's a copy test. >=20 > Sony 1.3 GHz Pentium 4 VAIO w/ 128MB RamBus memory (two 64MB RIMMs) > 571.20 MBytes/sec (copy) >=20 > 650 MHz Celleron (HP desktop, DIMM) > 114.65 MBytes/sec (copy) >=20 > 750 MHz P-III (2U VALINUX box, 2-cpu, 1024M ECC-DIMM) > 162.20 MBytes/sec (copy) >=20 > 700 MHz Celeron(?) (1U VALINUX box, 1-cpu, 128MB DIMM) > 93.56 MBytes/sec (copy) <---- yuch >=20 > 550 MHz P-III (4U Dell 2400, 1-cpu, 256MB DIMM) > 225.92 MBytes/sec (copy) >=20 > 600 MHz P-III (2U Dell 2450, 2-cpus, 512MB DIMM)) > 228.91 MBytes/sec (copy) >=20 > I was somewhat disappointed with the VALINUX boxes, I expected them to > be on par with the DELLs. In anycase, the Sony VAIO workstation with > the RamBus memory blew the field away. The cpu is so fast that a > buildworld I did was essentially I/O bound. I'll have to go and buy = some=20 > more RamBus memory for the thing (it only came with 128MB), which is= =20 > kinda of annoying seeing as I have a gigabyte worth of DIMMs just sit= ting > on my desk :-( that I can't use. >=20 > I'm tring to imagine 1.3 GHz. That's over a billion instructions > a second. And in a few years with the new chip fab lithography > standards it's going to be 10 GHz. >=20 > We need to find something more interesting then buildworlds to do on > these machines. >=20 > -Matt >=20 >=20 > /* > * Attempt to test memory copy speeds. Use a buffer large enough to > * defeat the on-cpu L1 and L2 caches. > */ >=20 > #include > #include > #include > #include > #include > #include >=20 > #define NLOOP 100 >=20 > char Buf1[2 * 1024 * 1024]; > char Buf2[2 * 1024 * 1024]; >=20 > int deltausecs(struct timeval *tv1, struct timeval *tv2); >=20 > int > main(int ac, char **av) > { > int i; > double dtime; > struct timeval tv1; > struct timeval tv2; >=20 > memset(Buf1, 1, sizeof(Buf1)); > for (i =3D 0; i < 10; ++i) > bcopy(Buf1, Buf2, sizeof(Buf1)); >=20 > gettimeofday(&tv1, NULL); > for (i =3D 0; i < NLOOP; ++i) > bcopy(Buf1, Buf2, sizeof(Buf1)); > gettimeofday(&tv2, NULL); >=20 > dtime =3D (double)deltausecs(&tv1, &tv2); > printf("%6.2f MBytes/sec (copy)\n", (double)sizeof(Buf1) * NLOOP / dt= ime); > return(0); > } >=20 > int > deltausecs(struct timeval *tv1, struct timeval *tv2) > { > int usec; >=20 > usec =3D (tv2->tv_usec + 1000000 - tv1->tv_usec); > usec +=3D (tv2->tv_sec - tv1->tv_sec - 1) * 1000000; > return(usec); > } >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message >=20 --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6oxAeERViMObJ880RAW5+AJ0ccLfen8akXJGS0qr4J5bWzM2SCACcDWPw VMHDPW2vWXJfWHlsOTawiBw= =43db -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 19:59:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id 9862E37B71A for ; Sun, 4 Mar 2001 19:59:50 -0800 (PST) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.9.0/8.8.7) with ESMTP id DAA15891 for ; Mon, 5 Mar 2001 03:59:49 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Mon, 5 Mar 2001 03:59:48 +0000 (GMT) From: "E.B. Dreger" To: freebsd-hackers@FreeBSD.ORG Subject: Re: Machines are getting too damn fast In-Reply-To: <3AA2EE3D.17B01E8E@mcs.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 > Date: Sun, 04 Mar 2001 19:39:09 -0600 > From: David A. Gobeille > > It would also be interesting to see the numbers for an Athlon/PIII > system with DDR, if anyone has such a machine. Personally, I'd be [more] interested in a ServerWorks III HE core chipset with four-way interleaved SDRAM. :-) If one _truly_ needs the bandwidth of Rambus (which, IIRC, is higher real-world latency than SDRAM), then how about having the bus bandwidth to back it up? Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division E-Mail: eddy@everquick.net Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 4 21:12:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 4D13537B718; Sun, 4 Mar 2001 21:12:50 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f255CoB32923; Sun, 4 Mar 2001 21:12:50 -0800 (PST) (envelope-from dillon) Date: Sun, 4 Mar 2001 21:12:50 -0800 (PST) From: Matt Dillon Message-Id: <200103050512.f255CoB32923@earth.backplane.com> To: Coleman Kane Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Machines are getting too damn fast References: <200103040934.f249YHi27877@earth.backplane.com> <20010304230342.A3870@cokane.yi.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :You should see what speed RamBus they were using, 600 or 800 Mhz. It is :pretty fast for large memory writes and reads. It'd be cool to see how :the different speeds stack up against one another. DDR comparisons would :be cool too. Yeah, for the frequency, you have to take into account that :these are different chips than your PIII or Athlons and the performance :difference is not simply a linear relation to the frequency rating :(i.e.: 1.3Ghz is not really over one-billion instructions per second, :just clocks per second). We installed Linux at a UC Free OS User Group :installfest here in cincinnati, it was pretty sweet. The machine was a :Dell and the case was freakin' huge. It also came with a 21" monitor and :stuff. The performace was really good, but not really any better than I :hads gleaned from the newer 1Ghz Athlons or PIII's. It says 800 MHz (PC-800 RIMMs) on the side of the box. The technical reviews basically say that bulk transfer rates for RamBus blow DDR away, but DDR wins for random reads and writes due to RamBus's higher startup latency. I don't have any DDR systems to test but I can devise a test program. Celeron 650 MHz (HP desktop) (DIMM) 16.16 MBytes/sec (copy) Pentium III 550 MHz (Dell 2400) (DIMM) 25.90 MBytes/sec (copy) Pentium 4 1.3 GHz / PC-800 RIMMs (Sony VAIO) 32.38 MBytes/sec (copy) -Matt Compile -O2, changing the two occurances of '512' to '4' will reproduce the original bulk-transfer rates. By default this program tests single-transfer (always cache miss). #include #include #include #include #include #include #define NLOOP 100 char Buf1[2 * 1024 * 1024]; char Buf2[2 * 1024 * 1024]; int deltausecs(struct timeval *tv1, struct timeval *tv2); int main(int ac, char **av) { int i; double dtime; struct timeval tv1; struct timeval tv2; memset(Buf1, 1, sizeof(Buf1)); for (i = 0; i < 10; ++i) bcopy(Buf1, Buf2, sizeof(Buf1)); gettimeofday(&tv1, NULL); for (i = 0; i < NLOOP; ++i) { int j; int k; for (k = sizeof(int); k <= 512; k += sizeof(int)) { for (j = sizeof(Buf1) - k; j >= 0; j -= 512) *(int *)(Buf2 + j) = *(int *)(Buf1 + j); } } gettimeofday(&tv2, NULL); dtime = (double)deltausecs(&tv1, &tv2); printf("%6.2f MBytes/sec (copy)\n", (double)sizeof(Buf1) * NLOOP / dtime); return(0); } int deltausecs(struct timeval *tv1, struct timeval *tv2) { int usec; usec = (tv2->tv_usec + 1000000 - tv1->tv_usec); usec += (tv2->tv_sec - tv1->tv_sec - 1) * 1000000; return(usec); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 1: 9:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailf.telia.com (mailf.telia.com [194.22.194.25]) by hub.freebsd.org (Postfix) with ESMTP id 2142037B718 for ; Mon, 5 Mar 2001 01:09:40 -0800 (PST) (envelope-from watchman@ludd.luth.se) Received: from d1o906.telia.com (d1o906.telia.com [195.252.36.241]) by mailf.telia.com (8.9.3/8.9.3) with ESMTP id KAA25838; Mon, 5 Mar 2001 10:09:37 +0100 (CET) Received: from ludd.luth.se (h12n1fls20o906.telia.com [213.64.92.12]) by d1o906.telia.com (8.8.8/8.8.8) with ESMTP id KAA08932; Mon, 5 Mar 2001 10:09:36 +0100 (CET) Message-ID: <3AA357CF.632AE0BB@ludd.luth.se> Date: Mon, 05 Mar 2001 10:09:35 +0100 From: Joachim =?iso-8859-1?Q?Str=F6mbergson?= Organization: Acne X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en-US MIME-Version: 1.0 To: Matt Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Machines are getting too damn fast References: <200103040934.f249YHi27877@earth.backplane.com> <20010304230342.A3870@cokane.yi.org> <200103050512.f255CoB32923@earth.backplane.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Aloha! (Sorry for jumping right in to the thread here...) This might be a good time to mention the STREAM benchmark developed by John McCalpin. It measures sustained bandwidth of systems. The official web page is at: http://www.cs.virginia.edu/stream/ If you check the section under "PC-compatible Results" you should find machines comparable to what you are measuring. Also, there are a tool out there that will measure effective latency for cache levels and main store for a system - both first page and burst transfers. Need to search my ever inflating bookmarks... The news group comp.arch might be a source of info and would probably be interested in your results too. Matt Dillon wrote: > > :You should see what speed RamBus they were using, 600 or 800 Mhz. It is > :pretty fast for large memory writes and reads. It'd be cool to see how > :the different speeds stack up against one another. DDR comparisons would > :be cool too. Yeah, for the frequency, you have to take into account that > :these are different chips than your PIII or Athlons and the performance > :difference is not simply a linear relation to the frequency rating > :(i.e.: 1.3Ghz is not really over one-billion instructions per second, > :just clocks per second). We installed Linux at a UC Free OS User Group > :installfest here in cincinnati, it was pretty sweet. The machine was a > :Dell and the case was freakin' huge. It also came with a 21" monitor and > :stuff. The performace was really good, but not really any better than I > :hads gleaned from the newer 1Ghz Athlons or PIII's. > > It says 800 MHz (PC-800 RIMMs) on the side of the box. > > The technical reviews basically say that bulk transfer rates for > RamBus blow DDR away, but DDR wins for random reads and writes > due to RamBus's higher startup latency. I don't have any DDR > systems to test but I can devise a test program. > > Celeron 650 MHz (HP desktop) (DIMM) > 16.16 MBytes/sec (copy) > > Pentium III 550 MHz (Dell 2400) (DIMM) > 25.90 MBytes/sec (copy) > > Pentium 4 1.3 GHz / PC-800 RIMMs (Sony VAIO) > 32.38 MBytes/sec (copy) > > -Matt -- Cheers! Joachim - Alltid i harmonisk svängning --- FairLight ------ FairLight ------ FairLight ------ FairLight --- Joachim Strömbergson ASIC SoC designer, nice to CUTE animals Phone: +46(0)31 - 27 98 47 Web: http://www.ludd.luth.se/~watchman --------------- Spamfodder: regeringen@regeringen.se --------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 1:31:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from evil.blunt.yi.org (ip-216-23-55-190.adsl.one.net [216.23.55.190]) by hub.freebsd.org (Postfix) with ESMTP id 725FD37B718; Mon, 5 Mar 2001 01:31:49 -0800 (PST) (envelope-from cokane@evil.blunt.yi.org) Received: (from cokane@localhost) by evil.blunt.yi.org (8.11.3/8.11.2) id f259hhU25740; Mon, 5 Mar 2001 04:43:43 -0500 (EST) (envelope-from cokane) Date: Mon, 5 Mar 2001 04:43:42 -0500 From: Coleman Kane To: Matt Dillon Cc: Coleman Kane , freebsd-hackers@FreeBSD.ORG Subject: Re: Machines are getting too damn fast Message-ID: <20010305044342.A23879@cokane.yi.org> References: <200103040934.f249YHi27877@earth.backplane.com> <20010304230342.A3870@cokane.yi.org> <200103050512.f255CoB32923@earth.backplane.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" X-Mailer: Mutt 1.0.1i In-Reply-To: <200103050512.f255CoB32923@earth.backplane.com>; from dillon@earth.backplane.com on Sun, Mar 04, 2001 at 09:12:50PM -0800 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable I believe DDR still has it bead (PC2100 that is), Rambus serailizes all wri= tes to 32 bit or 16 bit (an even 8 bit) depending on the modules. I haven't see= n any 64bit RIMMs. Also, DDR scales higher (up to 333Mhz I think). Just wait for that. I've pretty much given up on RamBus, I saw back in '96 when they talk= ed about how great it would be. I thought it was crap back then. The idea is t= hat it can queue 28 mem ops, where SDRAM can only do like 4. Typical environmen= ts typically don't do the writes that it looks good on, jsut certain special c= ases. That's where you get into the fact that RamBus sucks for use in PCs. Too specialized. Too proprietary. Matt Dillon had the audacity to say: >=20 >=20 > :You should see what speed RamBus they were using, 600 or 800 Mhz. It is > :pretty fast for large memory writes and reads. It'd be cool to see how > :the different speeds stack up against one another. DDR comparisons would > :be cool too. Yeah, for the frequency, you have to take into account that > :these are different chips than your PIII or Athlons and the performance > :difference is not simply a linear relation to the frequency rating > :(i.e.: 1.3Ghz is not really over one-billion instructions per second, > :just clocks per second). We installed Linux at a UC Free OS User Group > :installfest here in cincinnati, it was pretty sweet. The machine was a > :Dell and the case was freakin' huge. It also came with a 21" monitor and > :stuff. The performace was really good, but not really any better than I > :hads gleaned from the newer 1Ghz Athlons or PIII's. >=20 > It says 800 MHz (PC-800 RIMMs) on the side of the box. >=20 > The technical reviews basically say that bulk transfer rates for > RamBus blow DDR away, but DDR wins for random reads and writes > due to RamBus's higher startup latency. I don't have any DDR > systems to test but I can devise a test program. >=20 > Celeron 650 MHz (HP desktop) (DIMM) > 16.16 MBytes/sec (copy) >=20 > Pentium III 550 MHz (Dell 2400) (DIMM) > 25.90 MBytes/sec (copy) >=20 > Pentium 4 1.3 GHz / PC-800 RIMMs (Sony VAIO) > 32.38 MBytes/sec (copy) >=20 >=20 > -Matt >=20 > Compile -O2, changing the two occurances of '512' to '4' will reproduce > the original bulk-transfer rates. By default this program tests=20 > single-transfer (always cache miss). >=20 > #include > #include > #include > #include > #include > #include >=20 > #define NLOOP 100 >=20 > char Buf1[2 * 1024 * 1024]; > char Buf2[2 * 1024 * 1024]; >=20 > int deltausecs(struct timeval *tv1, struct timeval *tv2); >=20 > int > main(int ac, char **av) > { > int i; > double dtime; > struct timeval tv1; > struct timeval tv2; >=20 > memset(Buf1, 1, sizeof(Buf1)); > for (i =3D 0; i < 10; ++i) > bcopy(Buf1, Buf2, sizeof(Buf1)); >=20 > gettimeofday(&tv1, NULL); > for (i =3D 0; i < NLOOP; ++i) { > int j; > int k; > for (k =3D sizeof(int); k <=3D 512; k +=3D sizeof(int)) { > for (j =3D sizeof(Buf1) - k; j >=3D 0; j -=3D 512) > *(int *)(Buf2 + j) =3D *(int *)(Buf1 + j); > } > } > gettimeofday(&tv2, NULL); >=20 > dtime =3D (double)deltausecs(&tv1, &tv2); > printf("%6.2f MBytes/sec (copy)\n", (double)sizeof(Buf1) * NLOOP / dt= ime); > return(0); > } >=20 > int > deltausecs(struct timeval *tv1, struct timeval *tv2) > { > int usec; >=20 > usec =3D (tv2->tv_usec + 1000000 - tv1->tv_usec); > usec +=3D (tv2->tv_sec - tv1->tv_sec - 1) * 1000000; > return(usec); > } >=20 --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6o1/OERViMObJ880RAb3oAKDAV97F1VIw5Ts0bohDoUqgFFxrRwCg51Vt kbhtSIxE/Hlm7t1USZTpWjs= =EAS4 -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 4:52: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 75FA437B719; Mon, 5 Mar 2001 04:51:59 -0800 (PST) (envelope-from nectar@nectar.com) Received: by gw.nectar.com (Postfix, from userid 1001) id 1191F18C97; Mon, 5 Mar 2001 06:51:59 -0600 (CST) Date: Mon, 5 Mar 2001 06:51:58 -0600 From: "Jacques A. Vidrine" To: Mark Murray Cc: freebsd-hackers@freebsd.org Subject: Re: cvs commit: src/kerberos5/usr.bin Makefile src/kerberos5/usr.bin/k5su Makefile Message-ID: <20010305065158.C78960@spawn.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , Mark Murray , freebsd-hackers@freebsd.org References: <200103051118.f25BIZW85891@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103051118.f25BIZW85891@freefall.freebsd.org>; from markm@FreeBSD.org on Mon, Mar 05, 2001 at 03:18:35AM -0800 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 05, 2001 at 03:18:35AM -0800, Mark Murray wrote: > markm 2001/03/05 03:18:35 PST > > Modified files: > kerberos5/usr.bin Makefile > Added files: > kerberos5/usr.bin/k5su Makefile > Log: > *Sigh*. What I did without this, I have no idea. Will we always have this dichotomy between kblah/k5blah utilities? It is fairly annoying. Anecdotally, there don't seem to be many new Kerberos IV installations, & Kerberos V's utilities can get/list/trash version 4 & 5 tickets. Curious, -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@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 Mar 5 5: 2:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sivka.carrier.kiev.ua (sivka.carrier.kiev.ua [193.193.193.101]) by hub.freebsd.org (Postfix) with ESMTP id 767CD37B71B for ; Mon, 5 Mar 2001 05:02:27 -0800 (PST) (envelope-from diman@asd-g.com) Received: from core.is.kiev.ua (p187.is.kiev.ua [62.244.5.187] (may be forged)) by sivka.carrier.kiev.ua (8/Kilkenny_is_better) with ESMTP id OWK03083; Mon, 5 Mar 2001 14:58:13 +0200 (EET) (envelope-from diman@asd-g.com) Received: from ergo.local ([10.203.1.10]) by core.is.kiev.ua (8.11.1/ASDG-2.3-NR) with ESMTP id f25Cw9J18553; Mon, 5 Mar 2001 14:58:10 +0200 (EET) (envelope-from diman@asd-g.com) Date: Mon, 5 Mar 2001 14:56:32 +0200 (EET) From: diman X-Sender: diman@portal.none.ua To: Dan Phoenix Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: easy way to crash 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 Hello, I found a bit more ecsotic way to do this: - put your fdd to a piece of paper to make it roll a bit slower - mount floppy and initiate some write operation - regulating the preassure to the device you can achive the effect (I/O err., autom. reboot in progress :P) On Fri, 2 Mar 2001, Dan Phoenix wrote: > > > symbolic link /etc/resolv.conf > to a non-existant file....throw a bunch of connections at it > and watch it reboot. > > > -- > Dan > > +------------------------------------------------------+ > | BRAVENET WEB SERVICES | > | dan@bravenet.com | > | make installworld | > | ln -s /var/qmail/bin/sendmail /usr/sbin/sendmail | > | ln -s /var/qmail/bin/newaliases /usr/sbin/newaliases | > +______________________________________________________+ > > > > 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 Mar 5 6:20:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 965D637B718; Mon, 5 Mar 2001 06:20:22 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id PAA56655; Mon, 5 Mar 2001 15:20:19 +0100 (CET) (envelope-from assar) To: "Jacques A. Vidrine" Cc: Mark Murray , freebsd-hackers@FreeBSD.ORG Subject: Re: cvs commit: src/kerberos5/usr.bin Makefile src/kerberos5/usr.bin/k5su Makefile References: <200103051118.f25BIZW85891@freefall.freebsd.org> <20010305065158.C78960@spawn.nectar.com> From: Assar Westerlund Date: 05 Mar 2001 15:20:18 +0100 In-Reply-To: "Jacques A. Vidrine"'s message of "Mon, 5 Mar 2001 06:51:58 -0600" Message-ID: <5lk864thzx.fsf@assaris.sics.se> Lines: 13 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jacques A. Vidrine" writes: > Will we always have this dichotomy between kblah/k5blah utilities? It is > fairly annoying. Anecdotally, there don't seem to be many new Kerberos > IV installations, & Kerberos V's utilities can get/list/trash version 4 > & 5 tickets. Yes. My current plan of things to happen (in -current and after 4.3) is to ditch the v4 programs basically and install the v5 ones under the canonical names (with v4-compatibility if compiled in). And to always build and install the krb5 programs/libraries, but ifdef'ing the support in other programs. How does that sounds? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 7:53:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 2178137B71A for ; Mon, 5 Mar 2001 07:53:36 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) 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 JAA75933; Mon, 5 Mar 2001 09:53:32 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 5 Mar 2001 09:53:31 -0600 (CST) From: Chris Dillon To: "E.B. Dreger" Cc: Subject: Re: Machines are getting too damn fast 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 Mon, 5 Mar 2001, E.B. Dreger wrote: > > Date: Sun, 04 Mar 2001 19:39:09 -0600 > > From: David A. Gobeille > > > > It would also be interesting to see the numbers for an Athlon/PIII > > system with DDR, if anyone has such a machine. > > Personally, I'd be [more] interested in a ServerWorks III HE core chipset > with four-way interleaved SDRAM. :-) I've got a ServerWorks III HE-SL system with 512MB of two-way interleaved PC133 SDRAM and dual PIII-800's. Is that close enough? :-) Here is my "memory bandwidth test", much much simpler and less scientific than Matt's: dd if=/dev/zero of=/dev/null bs=10m count=1000 1000+0 records in 1000+0 records out 10485760000 bytes transferred in 23.716504 secs (442129245 bytes/sec) I just did a recent 4.2-STABLE 'make -j 4 buildworld' on that system in just over 34 minutes. Here's the time output: 1980.707u 768.223s 34:20.89 133.3% 1297+1456k 39517+6202io 1661pf+0w > If one _truly_ needs the bandwidth of Rambus (which, IIRC, is > higher real-world latency than SDRAM), then how about having the > bus bandwidth to back it up? The higher real-world latency of RDRAM over SDRAM is what makes the benefits of its higher bandwidth so questionable. PC2100 DDR-SDRAM -- which has higher latencies than regular SDRAM but still lower than RDRAM -- should have it beat soundly, though we'll have to wait for some systems that are actually designed to take advantage of it to say for sure. :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 9:15:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 7B9CF37B718 for ; Mon, 5 Mar 2001 09:15:38 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f25HF9R48503; Mon, 5 Mar 2001 19:15:16 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200103051715.f25HF9R48503@gratis.grondar.za> To: "Jacques A. Vidrine" Cc: freebsd-hackers@FreeBSD.org Subject: Re: cvs commit: src/kerberos5/usr.bin Makefile src/kerberos5/usr.bin/k5su Makefile References: <20010305065158.C78960@spawn.nectar.com> In-Reply-To: <20010305065158.C78960@spawn.nectar.com> ; from "Jacques A. Vidrine" "Mon, 05 Mar 2001 06:51:58 CST." Date: Mon, 05 Mar 2001 19:16:02 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Will we always have this dichotomy between kblah/k5blah utilities? It is > fairly annoying. Anecdotally, there don't seem to be many new Kerberos > IV installations, & Kerberos V's utilities can get/list/trash version 4 > & 5 tickets. When all the K5 utils reliably double-up as K4 ones, I'll fix this. (I think we are really close, BTW). M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 9:17:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 122A337B718; Mon, 5 Mar 2001 09:17:21 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f25HHHR48516; Mon, 5 Mar 2001 19:17:17 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200103051717.f25HHHR48516@gratis.grondar.za> To: Assar Westerlund Cc: "Jacques A. Vidrine" , Mark Murray , freebsd-hackers@FreeBSD.ORG Subject: Re: cvs commit: src/kerberos5/usr.bin Makefile src/kerberos5/usr.bin/k5su Makefile References: <5lk864thzx.fsf@assaris.sics.se> In-Reply-To: <5lk864thzx.fsf@assaris.sics.se> ; from Assar Westerlund "05 Mar 2001 15:20:18 +0100." Date: Mon, 05 Mar 2001 19:18:11 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Jacques A. Vidrine" writes: > > Will we always have this dichotomy between kblah/k5blah utilities? It is > > fairly annoying. Anecdotally, there don't seem to be many new Kerberos > > IV installations, & Kerberos V's utilities can get/list/trash version 4 > > & 5 tickets. > > Yes. My current plan of things to happen (in -current and after 4.3) > is to ditch the v4 programs basically and install the v5 ones under > the canonical names (with v4-compatibility if compiled in). And to > always build and install the krb5 programs/libraries, but ifdef'ing > the support in other programs. How does that sounds? Wonderful! If you need repo-copying done, I'm your man! -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 9:24:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 72C4E37B718 for ; Mon, 5 Mar 2001 09:24:27 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 13460 invoked by uid 1001); 5 Mar 2001 17:24:24 +0000 (GMT) To: freebsd-hackers@freebsd.org Subject: Missing support in FreeBSD for large file sizes? From: sthaug@nethelp.no X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 05 Mar 2001 18:24:24 +0100 Message-ID: <13458.983813064@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to the "Maxtor picks Windows, dumps open source" article at http://news.cnet.com/news/0-1003-200-5009496.html?tag=lh FreeBSD "did not support large file sizes, Macintosh and newer Novell file systems, or backup and management software from companies such as OpenView, Tivoli and Microsoft". Now I can understand what they say about missing Tivoli support - we're using Tivoli backup here ourselves, and the SCO ADSM/TSM client that we currently use to backup FreeBSD is passable, but nothing more. A native FreeBSD client would be much preferable. What I can't understand is the reference to missing support for large file sizes - as far as I know, that's one of FreeBSD's strengths! Anybody care to guess what they mean here? Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 9:37:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.nettoll.com (matrix.nettoll.net [212.155.143.61]) by hub.freebsd.org (Postfix) with ESMTP id 694D137B718 for ; Mon, 5 Mar 2001 09:37:56 -0800 (PST) (envelope-from usebsd@free.fr) Received: by smtp.nettoll.com; Mon, 5 Mar 2001 18:35:09 +0100 (MET) Message-Id: <4.3.0.20010305183820.05eb3920@pop.free.fr> X-Sender: usebsd@pop.free.fr X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Mon, 05 Mar 2001 18:39:05 +0100 To: Alfred Perlstein , Dan Phoenix From: mouss Subject: Re: easy way to crash freebsd Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <20010302152553.H8663@fw.wintelcom.net> References: 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 At 15:25 02/03/01 -0800, Alfred Perlstein wrote: > > On Fri, 2 Mar 2001, Dan Phoenix wrote: > > > > > symbolic link /etc/resolv.conf > > > to a non-existant file....throw a bunch of connections at it > > > and watch it reboot. > >* Dan Phoenix [010302 15:24] wrote: > > > > People asking me how this could be used as a local user. > > Well i guess if you wanted to you could find something root runs > > that writes to /tmp then umask resolv.conf > > and echo "" > resolv.conf > > > > I am in no way supporting that...just answering a question. > >Try overwriting /dev/mem, it's much more interesting. There are a lot of other ways: - reboot - halt ... and the simplest of all: turn off the ON/OFF button. cheers, mouss To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 9:42:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B104837B718 for ; Mon, 5 Mar 2001 09:42:39 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA03291; Mon, 5 Mar 2001 09:42:37 -0800 Date: Mon, 5 Mar 2001 09:42:35 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: sthaug@nethelp.no Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Missing support in FreeBSD for large file sizes? In-Reply-To: <13458.983813064@verdi.nethelp.no> 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 Very annoying. And Maxtor also missed that Networker is available for FreeBSD as well. > According to the "Maxtor picks Windows, dumps open source" article at > > http://news.cnet.com/news/0-1003-200-5009496.html?tag=lh > > FreeBSD "did not support large file sizes, Macintosh and newer Novell > file systems, or backup and management software from companies such as > OpenView, Tivoli and Microsoft". > > Now I can understand what they say about missing Tivoli support - we're > using Tivoli backup here ourselves, and the SCO ADSM/TSM client that we > currently use to backup FreeBSD is passable, but nothing more. A native > FreeBSD client would be much preferable. > > What I can't understand is the reference to missing support for large > file sizes - as far as I know, that's one of FreeBSD's strengths! Anybody > care to guess what they mean here? > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > 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 Mar 5 10: 6:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [192.215.234.86]) by hub.freebsd.org (Postfix) with ESMTP id 43E7737B718; Mon, 5 Mar 2001 10:06:23 -0800 (PST) (envelope-from gordont@bluemtn.net) Received: from localhost (gordont@localhost) by sdmail0.sd.bmarts.com (8.11.2/8.11.2/BMA1.1) with ESMTP id f25I8ET01031; Mon, 5 Mar 2001 10:08:14 -0800 (PST) Date: Mon, 5 Mar 2001 10:08:14 -0800 (PST) From: Gordon Tetlow X-X-Sender: To: "Jacques A. Vidrine" Cc: Mark Murray , Subject: Re: cvs commit: src/kerberos5/usr.bin Makefile src/kerberos5/usr.bin/k5su Makefile In-Reply-To: <20010305065158.C78960@spawn.nectar.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 BTW, is this still valid? From /etc/defaults/make.conf: # Kerberos 5 # If you want KerberosIV (KTH Heimdal), define this: # ** WARNING ** # ** WARNING ** This is very experimental at this stage. If you # ** WARNING ** need stable Kerberos5, rather use the port(s). # ** WARNING ** # #MAKE_KERBEROS5= yes Judging by the amount of work going into the krb5 stuff, I was wondering if this warning was valid or just something that didn't get pulled out. -gordon On Mon, 5 Mar 2001, Jacques A. Vidrine wrote: > Will we always have this dichotomy between kblah/k5blah utilities? It is > fairly annoying. Anecdotally, there don't seem to be many new Kerberos > IV installations, & Kerberos V's utilities can get/list/trash version 4 > & 5 tickets. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 10:41:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 423EC37B718 for ; Mon, 5 Mar 2001 10:41:27 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) 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 MAA79721; Mon, 5 Mar 2001 12:41:16 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 5 Mar 2001 12:41:16 -0600 (CST) From: Chris Dillon To: Matthew Jacob Cc: , Subject: Re: Missing support in FreeBSD for large file sizes? 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 Mon, 5 Mar 2001, Matthew Jacob wrote: > Very annoying. And Maxtor also missed that Networker is available > for FreeBSD as well. And Veritas NetBackup BusinesServer/DataCenter. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 10:54:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (h122n4fls32o892.telia.com [213.64.47.122]) by hub.freebsd.org (Postfix) with ESMTP id 069DC37B718; Mon, 5 Mar 2001 10:54:44 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id TAA58653; Mon, 5 Mar 2001 19:54:29 +0100 (CET) (envelope-from assar) To: Gordon Tetlow Cc: "Jacques A. Vidrine" , Mark Murray , Subject: Re: cvs commit: src/kerberos5/usr.bin Makefile src/kerberos5/usr.bin/k5su Makefile References: From: Assar Westerlund Date: 05 Mar 2001 19:54:29 +0100 In-Reply-To: Gordon Tetlow's message of "Mon, 5 Mar 2001 10:08:14 -0800 (PST)" Message-ID: <5l4rx89hcq.fsf@assaris.sics.se> Lines: 16 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gordon Tetlow writes: > BTW, is this still valid? From /etc/defaults/make.conf: > > # Kerberos 5 > # If you want KerberosIV (KTH Heimdal), define this: > # ** WARNING ** > # ** WARNING ** This is very experimental at this stage. If you > # ** WARNING ** need stable Kerberos5, rather use the port(s). > # ** WARNING ** > # > #MAKE_KERBEROS5= yes I don't think so. It's the same version that the port currently, even thought the port builds more programs. I've nuked the warning. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 11:15:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 1CFBE37B718; Mon, 5 Mar 2001 11:14:25 -0800 (PST) (envelope-from nectar@nectar.com) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 7AB6D18C92; Mon, 5 Mar 2001 13:14:23 -0600 (CST) Received: (from nectar@localhost) by hamlet.nectar.com (8.11.2/8.9.3) id f25JENL21383; Mon, 5 Mar 2001 13:14:23 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Date: Mon, 5 Mar 2001 13:14:23 -0600 From: "Jacques A. Vidrine" To: Assar Westerlund Cc: Mark Murray , freebsd-hackers@FreeBSD.ORG Subject: Heimdal and pam_kerberos5 (was Re: cvs commit: src/kerberos5/usr.bin [...]) Message-ID: <20010305131423.A21365@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , Assar Westerlund , Mark Murray , freebsd-hackers@FreeBSD.ORG References: <200103051118.f25BIZW85891@freefall.freebsd.org> <20010305065158.C78960@spawn.nectar.com> <5lk864thzx.fsf@assaris.sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5lk864thzx.fsf@assaris.sics.se>; from assar@FreeBSD.ORG on Mon, Mar 05, 2001 at 03:20:18PM +0100 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 05, 2001 at 03:20:18PM +0100, Assar Westerlund wrote: > "Jacques A. Vidrine" writes: > > Will we always have this dichotomy between kblah/k5blah utilities? It is > > fairly annoying. Anecdotally, there don't seem to be many new Kerberos > > IV installations, & Kerberos V's utilities can get/list/trash version 4 > > & 5 tickets. > > Yes. My current plan of things to happen (in -current and after 4.3) > is to ditch the v4 programs basically and install the v5 ones under > the canonical names (with v4-compatibility if compiled in). And to > always build and install the krb5 programs/libraries, but ifdef'ing > the support in other programs. How does that sounds? That's what I wanted to hear :-) By the way. In my faithlessness, I did not expect that 0.3e would be MFC'd in time for 4.3. I'm pleasantly surprised. However, I would be sorry that 4.3 shipped without a pam_kerberos5. I am preparing to leave on holiday, and will not be able to make it happen myself. In the hopes that someone else can pick up the pieces, I am attaching a shar that I threw together today. I'm pretty sure that I don't have the dependencies right, but I can't play with a build world at the moment. This contains a pam_kerberos5 module derived from fcusack's (as found in ports/security/pam_krb5). Unfortunately, it does not appear that fcusack is maintaining this. I've been maintaining it on an unofficial basis, initially fixing several bugs and getting it to build with Heimdal, and then integrating fixes from the Kerberos mailings lists. In fact, some Linux distributions now apparently use this `version' from ports/security/pam_krb5. In short, I think it is appropriate to add it to the source tree so that it will be maintained. The license is dual BSD/GPL. If this misses 4.3 it is not the end of the world, but it would be nice. I've been using the port with consoles, sshd, and xdm (actually wdm) for four months or so. Cheers, -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org # This file contains patches and a shar archive. I expect it to # be invoked as follows: # # % (cd /usr/src && /bin/sh ${HOME}/pam_kerberos5.shar) # echo p - share/mk/bsd.libnames.mk (sed 's/^X//' |/usr/bin/patch -Ns) << 'END-of-share/mk/bsd.libnames.mk' X--- share/mk/bsd.libnames.mk.orig Sun Mar 4 10:16:23 2001 X+++ share/mk/bsd.libnames.mk Mon Mar 5 11:37:33 2001 X@@ -10,6 +10,7 @@ X LIBKZTAIL?= ${DESTDIR}${LIBDIR}/kztail.o X X LIBALIAS?= ${DESTDIR}${LIBDIR}/libalias.a X+LIBASN1?= ${DESTDIR}${LIBDIR}/libasn1.a # XXX in secure dist, not base X LIBATM?= ${DESTDIR}${LIBDIR}/libatm.a X LIBC?= ${DESTDIR}${LIBDIR}/libc.a X LIBC_PIC= ${DESTDIR}${LIBDIR}/libc_pic.a X@@ -35,12 +36,14 @@ X LIBGCC_PIC?= ${DESTDIR}${LIBDIR}/libgcc_pic.a X LIBGMP?= ${DESTDIR}${LIBDIR}/libgmp.a X LIBGNUREGEX?= ${DESTDIR}${LIBDIR}/libgnuregex.a X+LIBGSSAPI?= ${DESTDIR}${LIBDIR}/libgssapi.a # XXX in secure dist, not base X LIBHISTORY?= ${DESTDIR}${LIBDIR}/libhistory.a X LIBIPSEC?= ${DESTDIR}${LIBDIR}/libipsec.a X LIBIPX?= ${DESTDIR}${LIBDIR}/libipx.a X LIBISC?= ${DESTDIR}${LIBDIR}/libisc.a X LIBKDB?= ${DESTDIR}${LIBDIR}/libkdb.a # XXX in secure dist, not base X LIBKRB?= ${DESTDIR}${LIBDIR}/libkrb.a # XXX in secure dist, not base X+LIBKRB5?= ${DESTDIR}${LIBDIR}/libkrb5.a # XXX in secure dist, not base X LIBKEYCAP?= ${DESTDIR}${LIBDIR}/libkeycap.a X LIBKVM?= ${DESTDIR}${LIBDIR}/libkvm.a X LIBL?= ${DESTDIR}${LIBDIR}/libl.a X@@ -76,6 +79,7 @@ X LIBRADIUS?= ${DESTDIR}${LIBDIR}/libradius.a X LIBREADLINE?= ${DESTDIR}${LIBDIR}/libreadline.a X LIBRESOLV?= ${DESTDIR}${LIBDIR}/libresolv.a # XXX doesn't exist X+LIBROKEN?= ${DESTDIR}${LIBDIR}/libroken.a # XXX in secure dist, not base X LIBRPCSVC?= ${DESTDIR}${LIBDIR}/librpcsvc.a X LIBSCRYPT?= "don't use LIBSCRYPT, use LIBCRYPT" X LIBDESCRYPT?= "don't use LIBDESCRYPT, use LIBCRYPT" END-of-share/mk/bsd.libnames.mk echo p - lib/libpam/modules/Makefile (sed 's/^X//' |/usr/bin/patch -Ns) << 'END-of-lib/libpam/modules/Makefile' X--- lib/libpam/modules/Makefile.orig Sun Mar 4 10:37:31 2001 X+++ lib/libpam/modules/Makefile Mon Mar 5 12:01:39 2001 X@@ -29,7 +29,7 @@ X .if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) && !defined(NO_OPENSSL) X SUBDIR+= pam_kerberosIV X .endif X-.if defined(MAKE_KERBEROS5__) && !defined(NOCRYPT) && !defined(NO_OPENSSL) X+.if defined(MAKE_KERBEROS5) && !defined(NOCRYPT) && !defined(NO_OPENSSL) X SUBDIR+= pam_kerberos5 X .endif X SUBDIR+= pam_opie END-of-lib/libpam/modules/Makefile # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # lib/libpam/modules/pam_kerberos5 # lib/libpam/modules/pam_kerberos5/Makefile # lib/libpam/modules/pam_kerberos5/pam_krb5_auth.c # lib/libpam/modules/pam_kerberos5/pam_krb5_sess.c # lib/libpam/modules/pam_kerberos5/pam_krb5_pass.c # lib/libpam/modules/pam_kerberos5/support.c # lib/libpam/modules/pam_kerberos5/pam_krb5_acct.c # lib/libpam/modules/pam_kerberos5/compat_mit.c # lib/libpam/modules/pam_kerberos5/compat_heimdal.c # lib/libpam/modules/pam_kerberos5/pam_krb5.h # lib/libpam/modules/pam_kerberos5/COPYRIGHT # lib/libpam/modules/pam_kerberos5/README.fcusack # echo c - lib/libpam/modules/pam_kerberos5 mkdir -p lib/libpam/modules/pam_kerberos5 > /dev/null 2>&1 echo x - lib/libpam/modules/pam_kerberos5/Makefile sed 's/^X//' >lib/libpam/modules/pam_kerberos5/Makefile << 'END-of-lib/libpam/modules/pam_kerberos5/Makefile' X# Copyright 2001 Jacques Vidrine X# All rights reserved. X# X# Redistribution and use in source and binary forms, with or without X# modification, are permitted provided that the following conditions X# are met: X# 1. Redistributions of source code must retain the above copyright X# notice, this list of conditions and the following disclaimer. X# 2. Redistributions in binary form must reproduce the above copyright X# notice, this list of conditions and the following disclaimer in the X# documentation and/or other materials provided with the distribution. X# X# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND X# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE X# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE X# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE X# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL X# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS X# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) X# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT X# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY X# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF X# SUCH DAMAGE. X# X# $FreeBSD$ X XPAMDIR= ${.CURDIR}/../../../../contrib/libpam XKRB5DIR= ${.CURDIR}/../../../../crypto/heimdal X X.if exists(${.OBJDIR}/../../../../kerberos5/lib) XKRB5LIBOBJDIR= ${.OBJDIR}/../../../../kerberos5/lib X.else XKRB5LIBOBJDIR= ${.CURDIR}/../../../../kerberos5/lib X.endif X XASN1OBJDIR= ${KRB5LIBOBJDIR}/libasn1 XKRB5OBJDIR= ${KRB5LIBOBJDIR}/libkrb5 XROKENOBJDIR= ${KRB5LIBOBJDIR}/libroken XGSSAPIOBJDIR= ${KRB5LIBOBJDIR}/libgssapi X XLIB= pam_kerberos5 XSHLIB_NAME= pam_kerberos5.so XSRCS= compat_heimdal.c pam_krb5_acct.c pam_krb5_auth.c \ X pam_krb5_pass.c pam_krb5_sess.c support.c XCFLAGS+= -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \ X -Wcast-qual -Wchar-subscripts -Wconversion -Winline \ X -Wmissing-prototypes -Wnested-externs -Wpointer-arith \ X -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings XCFLAGS+= -I${PAMDIR}/libpam/include XCFLAGS+= -I${.CURDIR}/../../libpam XCFLAGS+= -I${.CURDIR}/../../../../kerberos5/include \ X -I${KRB5DIR}/lib/krb5 \ X -I${KRB5DIR}/lib/asn1 \ X -I${KRB5DIR}/lib/roken \ X -I${KRB5DIR}/include \ X -I${KRB5OBJDIR} \ X -I${ASN1OBJDIR} XDPADD+= ${LIBKRB5} ${LIBGSSAPI} ${LIBASN1} ${LIBROKEN} ${LIBCRYPTO} \ X ${LIBCRYPT} ${LIBCOM_ERR} XLDADD+= -L${KRB5OBJDIR} -L${ROKENOBJDIR} -L${ASN1OBJDIR} \ X -L${GSSAPIOBJDIR} \ X -lkrb5 -lgssapi -lasn1 -lroken -lcrypto -lcrypt XINTERNALLIB= yes XINTERNALSTATICLIB=yes XINCLUDES= ${KRB5DIR}/lib/krb5/krb5.h \ X ${.CURDIR}/../../../../include/krb5-types.h \ X ${KRB5DIR}/lib/krb5/krb5-protos.h heim_err.h krb5_err.h X X.include END-of-lib/libpam/modules/pam_kerberos5/Makefile echo x - lib/libpam/modules/pam_kerberos5/pam_krb5_auth.c sed 's/^X//' >lib/libpam/modules/pam_kerberos5/pam_krb5_auth.c << 'END-of-lib/libpam/modules/pam_kerberos5/pam_krb5_auth.c' X/* X * pam_krb5_auth.c X * X * PAM authentication management functions for pam_krb5 X * X */ X Xstatic const char rcsid[] = "$Id: pam_krb5_auth.c,v 1.18 2000/01/04 08:44:08 fcusack Exp $"; X X#include X#include X#include X#include /* PATH_MAX */ X#include /* getpwnam */ X#include /* tmpnam */ X#include /* malloc */ X#include /* strchr */ X#include /* syslog */ X#include /* chown */ X X#include X#include X X#include X#include X#include "pam_krb5.h" X Xextern krb5_cc_ops krb5_mcc_ops; X X/* A useful logging macro */ X#define DLOG(error_func, error_msg) \ Xif (debug) \ X syslog(LOG_DEBUG, "pam_krb5: pam_sm_authenticate(%s %s): %s: %s", \ X service, name, error_func, error_msg) X X/* Authenticate a user via krb5 */ Xint Xpam_sm_authenticate(pam_handle_t *pamh, int flags, int argc, X const char **argv) X{ X krb5_error_code krbret; X krb5_context pam_context; X krb5_creds creds; X krb5_principal princ; X krb5_ccache ccache, ccache_check; X krb5_get_init_creds_opt opts; X X int pamret, i; X const char *name; X char *princ_name = NULL; X char *pass = NULL, *service = NULL; X char *prompt = NULL; X char cache_name[L_tmpnam + 8]; X char lname[64]; /* local acct name */ X struct passwd *pw; X X int debug = 0, try_first_pass = 0, use_first_pass = 0; X int forwardable = 0, reuse_ccache = 0, no_ccache = 0; X X for (i = 0; i < argc; i++) { X if (strcmp(argv[i], "debug") == 0) X debug = 1; X else if (strcmp(argv[i], "try_first_pass") == 0) X try_first_pass = 1; X else if (strcmp(argv[i], "use_first_pass") == 0) X use_first_pass = 1; X else if (strcmp(argv[i], "forwardable") == 0) X forwardable = 1; X else if (strcmp(argv[i], "reuse_ccache") == 0) X reuse_ccache = 1; X else if (strcmp(argv[i], "no_ccache") == 0) X no_ccache = 1; X } X X /* Get username */ X if ((pamret = pam_get_user(pamh, &name, "login: ")) != PAM_SUCCESS) { X return PAM_SERVICE_ERR; X } X X /* Get service name */ X (void) pam_get_item(pamh, PAM_SERVICE, (const void **) &service); X if (!service) X service = "unknown"; X X DLOG("entry", ""); X X if ((krbret = krb5_init_context(&pam_context)) != 0) { X DLOG("krb5_init_context()", error_message(krbret)); X return PAM_SERVICE_ERR; X } X krb5_get_init_creds_opt_init(&opts); X memset(&creds, 0, sizeof(krb5_creds)); X memset(cache_name, 0, sizeof(cache_name)); X memset(lname, 0, sizeof(lname)); X X if (forwardable) X krb5_get_init_creds_opt_set_forwardable(&opts, 1); X X /* For CNS */ X if ((krbret = krb5_cc_register(pam_context, &krb5_mcc_ops, FALSE)) != 0) { X /* Solaris dtlogin doesn't call pam_end() on failure */ X if (krbret != KRB5_CC_TYPE_EXISTS) { X DLOG("krb5_cc_register()", error_message(krbret)); X pamret = PAM_SERVICE_ERR; X goto cleanup3; X } X } X X /* Get principal name */ X if ((krbret = krb5_parse_name(pam_context, name, &princ)) != 0) { X DLOG("krb5_parse_name()", error_message(krbret)); X pamret = PAM_SERVICE_ERR; X goto cleanup3; X } X X /* Now convert the principal name into something human readable */ X if ((krbret = krb5_unparse_name(pam_context, princ, &princ_name)) != 0) { X DLOG("krb5_unparse_name()", error_message(krbret)); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X X /* Get password */ X prompt = malloc(16 + strlen(princ_name)); X if (!prompt) { X DLOG("malloc()", "failure"); X pamret = PAM_BUF_ERR; X goto cleanup2; X } X (void) sprintf(prompt, "Password for %s: ", princ_name); X X if (try_first_pass || use_first_pass) X (void) pam_get_item(pamh, PAM_AUTHTOK, (const void **) &pass); X Xget_pass: X if (!pass) { X try_first_pass = 0; X if ((pamret = get_user_info(pamh, prompt, PAM_PROMPT_ECHO_OFF, X &pass)) != 0) { X DLOG("get_user_info()", pam_strerror(pamh, pamret)); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X /* We have to free pass. */ X if ((pamret = pam_set_item(pamh, PAM_AUTHTOK, pass)) != 0) { X DLOG("pam_set_item()", pam_strerror(pamh, pamret)); X free(pass); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X free(pass); X /* Now we get it back from the library. */ X (void) pam_get_item(pamh, PAM_AUTHTOK, (const void **) &pass); X } X X /* Verify the local user exists (AFTER getting the password) */ X if (strchr(name, '@')) { X /* get a local account name for this principal */ X if ((krbret = krb5_aname_to_localname(pam_context, princ, X sizeof(lname), lname)) != 0) { X DLOG("krb5_aname_to_localname()", error_message(krbret)); X pamret = PAM_USER_UNKNOWN; X goto cleanup2; X } X DLOG("changing PAM_USER to", lname); X if ((pamret = pam_set_item(pamh, PAM_USER, lname)) != 0) { X DLOG("pam_set_item()", pam_strerror(pamh, pamret)); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X if ((pamret = pam_get_item(pamh, PAM_USER, (const void **) &name) X != 0)) { X DLOG("pam_get_item()", pam_strerror(pamh, pamret)); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X } X pw = getpwnam(name); X if (!pw) { X DLOG("getpwnam()", lname); X pamret = PAM_USER_UNKNOWN; X goto cleanup2; X } X X /* Get a TGT */ X if ((krbret = krb5_get_init_creds_password(pam_context, &creds, princ, X pass, pam_prompter, pamh, 0, NULL, &opts)) != 0) { X DLOG("krb5_get_init_creds_password()", error_message(krbret)); X if (try_first_pass && krbret == KRB5KRB_AP_ERR_BAD_INTEGRITY) { X pass = NULL; X goto get_pass; X } X pamret = PAM_AUTH_ERR; X goto cleanup2; X } X X /* Generate a unique cache_name */ X strcpy(cache_name, "MEMORY:"); X (void) tmpnam(&cache_name[7]); X X if ((krbret = krb5_cc_resolve(pam_context, cache_name, &ccache)) != 0) { X DLOG("krb5_cc_resolve()", error_message(krbret)); X pamret = PAM_SERVICE_ERR; X goto cleanup; X } X if ((krbret = krb5_cc_initialize(pam_context, ccache, princ)) != 0) { X DLOG("krb5_cc_initialize()", error_message(krbret)); X pamret = PAM_SERVICE_ERR; X goto cleanup; X } X if ((krbret = krb5_cc_store_cred(pam_context, ccache, &creds)) != 0) { X DLOG("krb5_cc_store_cred()", error_message(krbret)); X (void) krb5_cc_destroy(pam_context, ccache); X pamret = PAM_SERVICE_ERR; X goto cleanup; X } X X /* Verify it */ X if (verify_krb_v5_tgt(pam_context, ccache, service, debug) == -1) { X (void) krb5_cc_destroy(pam_context, ccache); X pamret = PAM_AUTH_ERR; X goto cleanup; X } X X /* A successful authentication, store ccache for sm_setcred() */ X if (!pam_get_data(pamh, "ccache", (const void **) &ccache_check)) { X DLOG("pam_get_data()", "ccache data already present"); X (void) krb5_cc_destroy(pam_context, ccache); X pamret = PAM_AUTH_ERR; X goto cleanup; X } X if ((pamret = pam_set_data(pamh, "ccache", ccache, cleanup_cache)) != 0) { X DLOG("pam_set_data()", pam_strerror(pamh, pamret)); X (void) krb5_cc_destroy(pam_context, ccache); X pamret = PAM_SERVICE_ERR; X goto cleanup; X } X Xcleanup: X krb5_free_cred_contents(pam_context, &creds); Xcleanup2: X krb5_free_principal(pam_context, princ); Xcleanup3: X if (prompt) X free(prompt); X if (princ_name) X free(princ_name); X X krb5_free_context(pam_context); X DLOG("exit", pamret ? "failure" : "success"); X return pamret; X} X X X X/* redefine this for pam_sm_setcred() */ X#undef DLOG X#define DLOG(error_func, error_msg) \ Xif (debug) \ X syslog(LOG_DEBUG, "pam_krb5: pam_sm_setcred(%s %s): %s: %s", \ X service, name, error_func, error_msg) X X/* Called after a successful authentication. Set user credentials. */ Xint Xpam_sm_setcred(pam_handle_t *pamh, int flags, int argc, X const char **argv) X{ X X krb5_error_code krbret; X krb5_context pam_context; X krb5_principal princ; X krb5_creds creds; X krb5_ccache ccache_temp, ccache_perm; X krb5_cc_cursor cursor; X X int i, pamret; X char *name, *service = NULL; X char *cache_name = NULL, *cache_env_name; X struct passwd *pw = NULL; X X int debug = 0; X uid_t euid; X gid_t egid; X X if (flags == PAM_REINITIALIZE_CRED) X return PAM_SUCCESS; /* XXX Incorrect behavior */ X X if (flags != PAM_ESTABLISH_CRED) X return PAM_SERVICE_ERR; X X for (i = 0; i < argc; i++) { X if (strcmp(argv[i], "debug") == 0) X debug = 1; X else if (strcmp(argv[i], "no_ccache") == 0) X return PAM_SUCCESS; X else if (strstr(argv[i], "ccache=") == argv[i]) X cache_name = (char *) &argv[i][7]; /* save for later */ X } X X /* Get username */ X if (pam_get_item(pamh, PAM_USER, (const void **) &name)) { X return PAM_SERVICE_ERR; X } X X /* Get service name */ X (void) pam_get_item(pamh, PAM_SERVICE, (const void **) &service); X if (!service) X service = "unknown"; X X DLOG("entry", ""); X X if ((krbret = krb5_init_context(&pam_context)) != 0) { X DLOG("krb5_init_context()", error_message(krbret)); X return PAM_SERVICE_ERR; X } X X euid = geteuid(); /* Usually 0 */ X egid = getegid(); X X /* Retrieve the cache name */ X if ((pamret = pam_get_data(pamh, "ccache", (const void **) &ccache_temp)) X != 0) { X DLOG("pam_get_data()", pam_strerror(pamh, pamret)); X pamret = PAM_CRED_UNAVAIL; X goto cleanup3; X } X X /* Get the uid. This should exist. */ X pw = getpwnam(name); X if (!pw) { X DLOG("getpwnam()", name); X pamret = PAM_USER_UNKNOWN; X goto cleanup3; X } X X /* Avoid following a symlink as root */ X if (setegid(pw->pw_gid)) { X DLOG("setegid()", name); /* XXX should really log group name or id */ X pamret = PAM_SERVICE_ERR; X goto cleanup3; X } X if (seteuid(pw->pw_uid)) { X DLOG("seteuid()", name); X pamret = PAM_SERVICE_ERR; X goto cleanup3; X } X X /* Get the cache name */ X if (!cache_name) { X cache_name = malloc(64); /* plenty big */ X if (!cache_name) { X DLOG("malloc()", "failure"); X pamret = PAM_BUF_ERR; X goto cleanup3; X } X sprintf(cache_name, "FILE:/tmp/krb5cc_%d", pw->pw_uid); X } else { X /* cache_name was supplied */ X char *p = calloc(PATH_MAX + 10, 1); /* should be plenty */ X char *q = cache_name; X if (!p) { X DLOG("malloc()", "failure"); X pamret = PAM_BUF_ERR; X goto cleanup3; X } X cache_name = p; X X /* convert %u and %p */ X while (*q) { X if (*q == '%') { X q++; X if (*q == 'u') { X sprintf(p, "%d", pw->pw_uid); X p += strlen(p); X } else if (*q == 'p') { X sprintf(p, "%d", getpid()); X p += strlen(p); X } else { X /* Not a special token */ X *p++ = '%'; X q--; X } X q++; X } else { X *p++ = *q++; X } X } X } X X /* Initialize the new ccache */ X if ((krbret = krb5_cc_get_principal(pam_context, ccache_temp, &princ)) X != 0) { X DLOG("krb5_cc_get_principal()", error_message(krbret)); X pamret = PAM_SERVICE_ERR; X goto cleanup3; X } X if ((krbret = krb5_cc_resolve(pam_context, cache_name, &ccache_perm)) X != 0) { X DLOG("krb5_cc_resolve()", error_message(krbret)); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X if ((krbret = krb5_cc_initialize(pam_context, ccache_perm, princ)) != 0) { X DLOG("krb5_cc_initialize()", error_message(krbret)); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X X /* Prepare for iteration over creds */ X if ((krbret = krb5_cc_start_seq_get(pam_context, ccache_temp, &cursor)) X != 0) { X DLOG("krb5_cc_start_seq_get()", error_message(krbret)); X (void) krb5_cc_destroy(pam_context, ccache_perm); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X X /* Copy the creds (should be two of them) */ X while ((krbret = compat_cc_next_cred(pam_context, ccache_temp, X &cursor, &creds) == 0)) { X if ((krbret = krb5_cc_store_cred(pam_context, ccache_perm, X &creds)) != 0) { X DLOG("krb5_cc_store_cred()", error_message(krbret)); X (void) krb5_cc_destroy(pam_context, ccache_perm); X krb5_free_cred_contents(pam_context, &creds); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X krb5_free_cred_contents(pam_context, &creds); X } X (void) krb5_cc_end_seq_get(pam_context, ccache_temp, &cursor); X X if (strstr(cache_name, "FILE:") == cache_name) { X if (chown(&cache_name[5], pw->pw_uid, pw->pw_gid) == -1) { X DLOG("chown()", strerror(errno)); X (void) krb5_cc_destroy(pam_context, ccache_perm); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X if (chmod(&cache_name[5], (S_IRUSR|S_IWUSR)) == -1) { X DLOG("chmod()", strerror(errno)); X (void) krb5_cc_destroy(pam_context, ccache_perm); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X } X (void) krb5_cc_close(pam_context, ccache_perm); X X cache_env_name = malloc(strlen(cache_name) + 12); X if (!cache_env_name) { X DLOG("malloc()", "failure"); X (void) krb5_cc_destroy(pam_context, ccache_perm); X pamret = PAM_BUF_ERR; X goto cleanup2; X } X X sprintf(cache_env_name, "KRB5CCNAME=%s", cache_name); X if ((pamret = pam_putenv(pamh, cache_env_name)) != 0) { X DLOG("pam_putenv()", pam_strerror(pamh, pamret)); X (void) krb5_cc_destroy(pam_context, ccache_perm); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X Xcleanup2: X krb5_free_principal(pam_context, princ); Xcleanup3: X krb5_free_context(pam_context); X DLOG("exit", pamret ? "failure" : "success"); X (void) seteuid(euid); X (void) setegid(egid); X return pamret; X} X END-of-lib/libpam/modules/pam_kerberos5/pam_krb5_auth.c echo x - lib/libpam/modules/pam_kerberos5/pam_krb5_sess.c sed 's/^X//' >lib/libpam/modules/pam_kerberos5/pam_krb5_sess.c << 'END-of-lib/libpam/modules/pam_kerberos5/pam_krb5_sess.c' X/* X * pam_krb5_sess.c X * X * PAM session management functions for pam_krb5 X * (null functions) X * X */ X Xstatic const char rcsid[] = "$Id: pam_krb5_sess.c,v 1.3 1999/01/19 20:49:44 fcusack Exp $"; X X#include X#include X X/* Initiate session management */ Xint Xpam_sm_open_session(pam_handle_t *pamh, int flags, int argc, const char **argv) X{ X return PAM_SUCCESS; X} X X X/* Terminate session management */ Xint Xpam_sm_close_session(pam_handle_t *pamh, int flags, int argc, const char **argv) X{ X return PAM_SUCCESS; X} END-of-lib/libpam/modules/pam_kerberos5/pam_krb5_sess.c echo x - lib/libpam/modules/pam_kerberos5/pam_krb5_pass.c sed 's/^X//' >lib/libpam/modules/pam_kerberos5/pam_krb5_pass.c << 'END-of-lib/libpam/modules/pam_kerberos5/pam_krb5_pass.c' X/* X * pam_krb5_pass.c X * X * PAM password management functions for pam_krb5 X * X */ X Xstatic const char rcsid[] = "$Id: pam_krb5_pass.c,v 1.3 1999/01/19 23:43:11 fcusack Exp $"; X X#include X#include /* sprintf */ X#include /* malloc */ X#include /* syslog */ X#include X#include X#include X#include X#include "pam_krb5.h" X X/* A useful logging macro */ X#define DLOG(error_func, error_msg) \ Xif (debug) \ X syslog(LOG_DEBUG, "pam_krb5: pam_sm_chauthtok(%s %s): %s: %s", \ X service, name, error_func, error_msg) X X/* Change a user's password */ Xint Xpam_sm_chauthtok(pam_handle_t *pamh, int flags, int argc, const char **argv) X{ X krb5_error_code krbret; X krb5_context pam_context; X krb5_creds creds; X krb5_principal princ; X krb5_get_init_creds_opt opts; X X int result_code; X krb5_data result_code_string, result_string; X X int pamret, i; X char *name, *service = NULL, *pass = NULL, *pass2; X char *princ_name = NULL; X char *prompt = NULL; X X int debug = 0; X int try_first_pass = 0, use_first_pass = 0; X X if (!(flags & PAM_UPDATE_AUTHTOK)) X return PAM_AUTHTOK_ERR; X X for (i = 0; i < argc; i++) { X if (strcmp(argv[i], "debug") == 0) X debug = 1; X else if (strcmp(argv[i], "try_first_pass") == 0) X try_first_pass = 1; X else if (strcmp(argv[i], "use_first_pass") == 0) X use_first_pass = 1; X } X X /* Get username */ X if ((pam_get_item(pamh, PAM_USER, (const void **) &name)) != 0) { X return PAM_SERVICE_ERR; X } X X /* Get service name */ X (void) pam_get_item(pamh, PAM_SERVICE, (const void **) &service); X if (!service) X service = "unknown"; X X DLOG("entry", ""); X X if ((krbret = krb5_init_context(&pam_context)) != 0) { X DLOG("krb5_init_context()", error_message(krbret)); X return PAM_SERVICE_ERR; X } X X if ((krbret = krb5_init_context(&pam_context)) != 0) { X DLOG("krb5_init_context()", error_message(krbret)); X return PAM_SERVICE_ERR; X } X krb5_get_init_creds_opt_init(&opts); X memset(&creds, 0, sizeof(krb5_creds)); X X /* Get principal name */ X if ((krbret = krb5_parse_name(pam_context, name, &princ)) != 0) { X DLOG("krb5_parse_name()", error_message(krbret)); X pamret = PAM_USER_UNKNOWN; X goto cleanup3; X } X X /* Now convert the principal name into something human readable */ X if ((krbret = krb5_unparse_name(pam_context, princ, &princ_name)) != 0) { X DLOG("krb5_unparse_name()", error_message(krbret)); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X X /* Get password */ X prompt = malloc(16 + strlen(princ_name)); X if (!prompt) { X DLOG("malloc()", "failure"); X pamret = PAM_BUF_ERR; X goto cleanup2; X } X (void) sprintf(prompt, "Password for %s: ", princ_name); X X if (try_first_pass || use_first_pass) X (void) pam_get_item(pamh, PAM_AUTHTOK, (const void **) &pass); X Xget_pass: X if (!pass) { X try_first_pass = 0; X if ((pamret = get_user_info(pamh, prompt, PAM_PROMPT_ECHO_OFF, X &pass)) != 0) { X DLOG("get_user_info()", pam_strerror(pamh, pamret)); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X /* We have to free pass. */ X if ((pamret = pam_set_item(pamh, PAM_AUTHTOK, pass)) != 0) { X DLOG("pam_set_item()", pam_strerror(pamh, pamret)); X free(pass); X pamret = PAM_SERVICE_ERR; X goto cleanup2; X } X free(pass); X /* Now we get it back from the library. */ X (void) pam_get_item(pamh, PAM_AUTHTOK, (const void **) &pass); X } X X if ((krbret = krb5_get_init_creds_password(pam_context, &creds, princ, X pass, pam_prompter, pamh, 0, "kadmin/changepw", &opts)) != 0) { X DLOG("krb5_get_init_creds_password()", error_message(krbret)); X if (try_first_pass && krbret == KRB5KRB_AP_ERR_BAD_INTEGRITY) { X pass = NULL; X goto get_pass; X } X pamret = PAM_AUTH_ERR; X goto cleanup2; X } X X /* Now get the new password */ X free(prompt); X prompt = "Enter new password: "; X if ((pamret = get_user_info(pamh, prompt, PAM_PROMPT_ECHO_OFF, &pass)) X != 0) { X DLOG("get_user_info()", pam_strerror(pamh, pamret)); X prompt = NULL; X pamret = PAM_SERVICE_ERR; X goto cleanup; X } X prompt = "Enter it again: "; X if ((pamret = get_user_info(pamh, prompt, PAM_PROMPT_ECHO_OFF, &pass2)) X != 0) { X DLOG("get_user_info()", pam_strerror(pamh, pamret)); X prompt = NULL; X pamret = PAM_SERVICE_ERR; X goto cleanup; X } X prompt = NULL; X X if (strcmp(pass, pass2) != 0) { X DLOG("strcmp()", "passwords not equal"); X pamret = PAM_AUTHTOK_ERR; X goto cleanup; X } X X /* Change it */ X if ((krbret = krb5_change_password(pam_context, &creds, pass, X &result_code, &result_code_string, &result_string)) != 0) { X DLOG("krb5_change_password()", error_message(krbret)); X pamret = PAM_AUTHTOK_ERR; X goto cleanup; X } X if (result_code) { X DLOG("krb5_change_password() (result_code)", ""); X pamret = PAM_AUTHTOK_ERR; X goto cleanup; X } X X if (result_string.data) X free(result_string.data); X if (result_code_string.data) X free(result_code_string.data); X Xcleanup: X krb5_free_cred_contents(pam_context, &creds); Xcleanup2: X krb5_free_principal(pam_context, princ); Xcleanup3: X if (prompt) X free(prompt); X if (princ_name) X free(princ_name); X X krb5_free_context(pam_context); X DLOG("exit", pamret ? "failure" : "success"); X return pamret; X} X END-of-lib/libpam/modules/pam_kerberos5/pam_krb5_pass.c echo x - lib/libpam/modules/pam_kerberos5/support.c sed 's/^X//' >lib/libpam/modules/pam_kerberos5/support.c << 'END-of-lib/libpam/modules/pam_kerberos5/support.c' X/* X * support.c X * X * Support functions for pam_krb5 X */ X Xstatic const char rcsid[] = "$Id: support.c,v 1.8 2000/01/04 09:50:03 fcusack Exp $"; X X#include X#include /* BUFSIZ */ X#include /* malloc */ X#include /* strncpy */ X#include /* syslog */ X#include X#include X#include X#include X#include "pam_krb5.h" X X/* X * Get info from the user. Disallow null responses (regardless of flags). X * response gets allocated and filled in on successful return. Caller X * is responsible for freeing it. X */ Xint Xget_user_info(pam_handle_t *pamh, char *prompt, int type, char **response) X{ X int pamret; X struct pam_message msg; X const struct pam_message *pmsg; X struct pam_response *resp = NULL; X struct pam_conv *conv; X X if ((pamret = pam_get_item(pamh, PAM_CONV, (const void **) &conv)) != 0) X return pamret; X X /* set up conversation call */ X pmsg = &msg; X msg.msg_style = type; X msg.msg = prompt; X X if ((pamret = conv->conv(1, &pmsg, &resp, conv->appdata_ptr)) != 0) X return pamret; X X /* Caller should ignore errors for non-response conversations */ X if (!resp) X return PAM_CONV_ERR; X X if (!(resp->resp && resp->resp[0])) { X free(resp); X return PAM_AUTH_ERR; X } X X *response = resp->resp; X free(resp); X return pamret; X} X X/* X * This routine with some modification is from the MIT V5B6 appl/bsd/login.c X * Modified by Sam Hartman to support PAM services X * for Debian. X * X * Verify the Kerberos ticket-granting ticket just retrieved for the X * user. If the Kerberos server doesn't respond, assume the user is X * trying to fake us out (since we DID just get a TGT from what is X * supposedly our KDC). If the host/ service is unknown (i.e., X * the local keytab doesn't have it), and we cannot find another X * service we do have, let her in. X * X * Returns 1 for confirmation, -1 for failure, 0 for uncertainty. X */ Xint Xverify_krb_v5_tgt(krb5_context context, krb5_ccache ccache, X char * pam_service, int debug) X{ X char phost[BUFSIZ]; X char *services [3]; X char **service; X krb5_error_code retval = -1; X krb5_principal princ; X krb5_keyblock * keyblock = 0; X krb5_data packet; X krb5_auth_context auth_context = NULL; X X packet.data = 0; X X /* X * If possible we want to try and verify the ticket we have X * received against a keytab. We will try multiple service X * principals, including at least the host principal and the PAM X * service principal. The host principal is preferred because access X * to that key is generally sufficient to compromise root, while the X * service key for this PAM service may be less carefully guarded. X * It is important to check the keytab first before the KDC so we do X * not get spoofed by a fake KDC.*/ X services [0] = "host"; X services [1] = pam_service; X services [2] = NULL; X for ( service = &services[0]; *service != NULL; service++ ) { X if ((retval = krb5_sname_to_principal(context, NULL, *service, KRB5_NT_SRV_HST, X &princ)) != 0) { X if (debug) X syslog(LOG_DEBUG, "pam_krb5: verify_krb_v5_tgt(): %s: %s", X "krb5_sname_to_principal()", error_message(retval)); X return -1; X } X X /* Extract the name directly. */ X strncpy(phost, compat_princ_component(context, princ, 1), BUFSIZ); X phost[BUFSIZ - 1] = '\0'; X X /* X * Do we have service/ keys? X * (use default/configured keytab, kvno IGNORE_VNO to get the X * first match, and ignore enctype.) X */ X if ((retval = krb5_kt_read_service_key(context, NULL, princ, 0, X 0, &keyblock)) != 0) X continue; X break; X } X if (retval != 0 ) { /* failed to find key */ X /* Keytab or service key does not exist */ X if (debug) X syslog(LOG_DEBUG, "pam_krb5: verify_krb_v5_tgt(): %s: %s", X "krb5_kt_read_service_key()", error_message(retval)); X retval = 0; X goto cleanup; X } X if (keyblock) X krb5_free_keyblock(context, keyblock); X X /* Talk to the kdc and construct the ticket. */ X retval = krb5_mk_req(context, &auth_context, 0, *service, phost, X NULL, ccache, &packet); X if (auth_context) { X krb5_auth_con_free(context, auth_context); X auth_context = NULL; /* setup for rd_req */ X } X if (retval) { X if (debug) X syslog(LOG_DEBUG, "pam_krb5: verify_krb_v5_tgt(): %s: %s", X "krb5_mk_req()", error_message(retval)); X retval = -1; X goto cleanup; X } X X /* Try to use the ticket. */ X retval = krb5_rd_req(context, &auth_context, &packet, princ, X NULL, NULL, NULL); X if (retval) { X if (debug) X syslog(LOG_DEBUG, "pam_krb5: verify_krb_v5_tgt(): %s: %s", X "krb5_rd_req()", error_message(retval)); X retval = -1; X } else { X retval = 1; X } X Xcleanup: X if (packet.data) X compat_free_data_contents(context, &packet); X krb5_free_principal(context, princ); X return retval; X X} X X X/* Free the memory for cache_name. Called by pam_end() */ Xvoid Xcleanup_cache(pam_handle_t *pamh, void *data, int pam_end_status) X{ X krb5_context pam_context; X krb5_ccache ccache; X X if (krb5_init_context(&pam_context)) X return; X X ccache = (krb5_ccache) data; X (void) krb5_cc_destroy(pam_context, ccache); X krb5_free_context(pam_context); X} END-of-lib/libpam/modules/pam_kerberos5/support.c echo x - lib/libpam/modules/pam_kerberos5/pam_krb5_acct.c sed 's/^X//' >lib/libpam/modules/pam_kerberos5/pam_krb5_acct.c << 'END-of-lib/libpam/modules/pam_kerberos5/pam_krb5_acct.c' X/* X * pam_krb5_acct.c X * X * PAM account management functions for pam_krb5 X * X */ X Xstatic const char rcsid[] = "$Id: pam_krb5_acct.c,v 1.3 1999/01/19 21:26:44 fcusack Exp $"; X X#include /* syslog */ X#include X#include X#include X#include X#include "pam_krb5.h" X X/* A useful logging macro */ X#define DLOG(error_func, error_msg) \ Xif (debug) \ X syslog(LOG_DEBUG, "pam_krb5: pam_sm_acct_mgmt(%s %s): %s: %s", \ X service, name, error_func, error_msg) X X/* Check authorization of user */ Xint Xpam_sm_acct_mgmt(pam_handle_t *pamh, int flags, int argc, const char **argv) X{ X krb5_error_code krbret; X krb5_context pam_context; X krb5_ccache ccache; X krb5_principal princ; X X char *service, *name; X int debug = 0; X int i, pamret; X X for (i = 0; i < argc; i++) { X if (strcmp(argv[i], "debug") == 0) X debug = 1; X } X X /* Get username */ X if (pam_get_item(pamh, PAM_USER, (const void **) &name)) { X return PAM_PERM_DENIED;; X } X X /* Get service name */ X (void) pam_get_item(pamh, PAM_SERVICE, (const void **) &service); X if (!service) X service = "unknown"; X X DLOG("entry", ""); X X if (pam_get_data(pamh, "ccache", (const void **) &ccache)) { X /* User did not use krb5 to login */ X DLOG("ccache", "not found"); X return PAM_SUCCESS; X } X X if ((krbret = krb5_init_context(&pam_context)) != 0) { X DLOG("krb5_init_context()", error_message(krbret)); X return PAM_PERM_DENIED;; X } X X if ((krbret = krb5_cc_get_principal(pam_context, ccache, &princ)) != 0) { X DLOG("krb5_cc_get_principal()", error_message(krbret)); X pamret = PAM_PERM_DENIED;; X goto cleanup; X } X X if (krb5_kuserok(pam_context, princ, name)) X pamret = PAM_SUCCESS; X else X pamret = PAM_PERM_DENIED; X krb5_free_principal(pam_context, princ); X Xcleanup: X krb5_free_context(pam_context); X DLOG("exit", pamret ? "failure" : "success"); X return pamret; X X} X END-of-lib/libpam/modules/pam_kerberos5/pam_krb5_acct.c echo x - lib/libpam/modules/pam_kerberos5/compat_mit.c sed 's/^X//' >lib/libpam/modules/pam_kerberos5/compat_mit.c << 'END-of-lib/libpam/modules/pam_kerberos5/compat_mit.c' X#include X#include X#include X#include X X#include X#include X#include X#include "pam_krb5.h" X Xconst char * Xcompat_princ_component(krb5_context context, krb5_principal princ, int n) X{ X return krb5_princ_component(context, princ, n)->data; X} X Xvoid Xcompat_free_data_contents(krb5_context context, krb5_data *data) X{ X krb5_free_data_contents(context, data); X} X Xkrb5_error_code Xcompat_cc_next_cred(krb5_context context, const krb5_ccache id, X krb5_cc_cursor *cursor, krb5_creds *creds) X{ X return krb5_cc_next_cred(context, id, cursor, creds); X} X Xstatic krb5_error_code Xmit_pam_prompter(krb5_context context, void *data, const char *name, X const char *banner, int num_prompts, krb5_prompt prompts[]) X{ X int pam_prompts = num_prompts; X int pamret, i; X X struct pam_message *msg; X struct pam_response *resp = NULL; X struct pam_conv *conv; X pam_handle_t *pamh = (pam_handle_t *) data; X X if ((pamret = pam_get_item(pamh, PAM_CONV, (const void **) &conv)) != 0) X return KRB5KRB_ERR_GENERIC; X X if (name) X pam_prompts++; X X if (banner) X pam_prompts++; X X msg = calloc(sizeof(struct pam_message) * pam_prompts, 1); X if (!msg) X return ENOMEM; X X /* Now use pam_prompts as an index */ X pam_prompts = 0; X X /* Sigh. malloc all the prompts. */ X if (name) { X msg[pam_prompts].msg = malloc(strlen(name) + 1); X if (!msg[pam_prompts].msg) X goto cleanup; X strcpy((char *) msg[pam_prompts].msg, name); X msg[pam_prompts].msg_style = PAM_TEXT_INFO; X pam_prompts++; X } X X if (banner) { X msg[pam_prompts].msg = malloc(strlen(banner) + 1); X if (!msg[pam_prompts].msg) X goto cleanup; X strcpy((char *) msg[pam_prompts].msg, banner); X msg[pam_prompts].msg_style = PAM_TEXT_INFO; X pam_prompts++; X } X X for (i = 0; i < num_prompts; i++) { X msg[pam_prompts].msg = malloc(strlen(prompts[i].prompt) + 3); X if (!msg[pam_prompts].msg) X goto cleanup; X sprintf((char *) msg[pam_prompts].msg, "%s: ", prompts[i].prompt); X msg[pam_prompts].msg_style = prompts[i].hidden ? PAM_PROMPT_ECHO_OFF X : PAM_PROMPT_ECHO_ON; X pam_prompts++; X } X X if ((pamret = conv->conv(pam_prompts, (const struct pam_message **) &msg, X &resp, conv->appdata_ptr)) != 0) X goto cleanup; X X if (!resp) X goto cleanup; X X /* Reuse pam_prompts as a starting index */ X pam_prompts = 0; X if (name) X pam_prompts++; X if (banner) X pam_prompts++; X X for (i = 0; i < num_prompts; i++, pam_prompts++) { X register int len; X if (!resp[pam_prompts].resp) { X pamret = PAM_AUTH_ERR; X goto cleanup; X } X len = strlen(resp[pam_prompts].resp); /* Help out the compiler */ X if (len > prompts[i].reply->length) { X pamret = PAM_AUTH_ERR; X goto cleanup; X } X memcpy(prompts[i].reply->data, resp[pam_prompts].resp, len); X prompts[i].reply->length = len; X } X Xcleanup: X /* pam_prompts is correct at this point */ X X for (i = 0; i < pam_prompts; i++) { X if (msg[i].msg) X free((char *) msg[i].msg); X } X free(msg); X X if (resp) { X for (i = 0; i < pam_prompts; i++) { X /* X * Note that PAM is underspecified wrt free()'ing resp[i].resp. X * It's not clear if I should free it, or if the application X * has to. Therefore most (all?) apps won't free() it, and I X * can't either, as I am not sure it was malloc()'d. All PAM X * implementations I've seen leak memory here. Not so bad, IFF X * you fork/exec for each PAM authentication (as is typical). X */ X#if 0 X if (resp[i].resp) X free(resp[i].resp); X#endif /* 0 */ X } X /* This does not lose resp[i].resp if the application saved a copy. */ X free(resp); X } X X return (pamret ? KRB5KRB_ERR_GENERIC : 0); X} X Xkrb5_prompter_fct pam_prompter = mit_pam_prompter; END-of-lib/libpam/modules/pam_kerberos5/compat_mit.c echo x - lib/libpam/modules/pam_kerberos5/compat_heimdal.c sed 's/^X//' >lib/libpam/modules/pam_kerberos5/compat_heimdal.c << 'END-of-lib/libpam/modules/pam_kerberos5/compat_heimdal.c' X#include X#include X#include X#include X X#include X#include X#include X#include "pam_krb5.h" X Xconst char * Xcompat_princ_component(krb5_context context, krb5_principal princ, int n) X{ X return princ->name.name_string.val[n]; X} X Xvoid Xcompat_free_data_contents(krb5_context context, krb5_data *data) X{ X krb5_xfree(data->data); X} X Xkrb5_error_code Xcompat_cc_next_cred(krb5_context context, const krb5_ccache id, X krb5_cc_cursor *cursor, krb5_creds *creds) X{ X return krb5_cc_next_cred(context, id, creds, cursor); X} X X Xstatic krb5_error_code Xheimdal_pam_prompter(krb5_context context, void *data, const char *banner, int X num_prompts, krb5_prompt prompts[]) X{ X int pam_prompts = num_prompts; X int pamret, i; X X struct pam_message *msg; X struct pam_response *resp = NULL; X struct pam_conv *conv; X pam_handle_t *pamh = (pam_handle_t *) data; X X if ((pamret = pam_get_item(pamh, PAM_CONV, (const void **) &conv)) != 0) X return KRB5KRB_ERR_GENERIC; X X if (banner) X pam_prompts++; X X msg = calloc(sizeof(struct pam_message) * pam_prompts, 1); X if (!msg) X return ENOMEM; X X /* Now use pam_prompts as an index */ X pam_prompts = 0; X X if (banner) { X msg[pam_prompts].msg = malloc(strlen(banner) + 1); X if (!msg[pam_prompts].msg) X goto cleanup; X strcpy((char *) msg[pam_prompts].msg, banner); X msg[pam_prompts].msg_style = PAM_TEXT_INFO; X pam_prompts++; X } X X for (i = 0; i < num_prompts; i++) { X msg[pam_prompts].msg = malloc(strlen(prompts[i].prompt) + 3); X if (!msg[pam_prompts].msg) X goto cleanup; X sprintf((char *) msg[pam_prompts].msg, "%s: ", prompts[i].prompt); X msg[pam_prompts].msg_style = prompts[i].hidden ? PAM_PROMPT_ECHO_OFF X : PAM_PROMPT_ECHO_ON; X pam_prompts++; X } X X if ((pamret = conv->conv(pam_prompts, (const struct pam_message **) &msg, X &resp, conv->appdata_ptr)) != 0) X goto cleanup; X X if (!resp) X goto cleanup; X X /* Reuse pam_prompts as a starting index */ X pam_prompts = 0; X if (banner) X pam_prompts++; X X for (i = 0; i < num_prompts; i++, pam_prompts++) { X register int len; X if (!resp[pam_prompts].resp) { X pamret = PAM_AUTH_ERR; X goto cleanup; X } X len = strlen(resp[pam_prompts].resp); /* Help out the compiler */ X if (len > prompts[i].reply->length) { X pamret = PAM_AUTH_ERR; X goto cleanup; X } X memcpy(prompts[i].reply->data, resp[pam_prompts].resp, len); X prompts[i].reply->length = len; X } X Xcleanup: X /* pam_prompts is correct at this point */ X X for (i = 0; i < pam_prompts; i++) { X if (msg[i].msg) X free((char *) msg[i].msg); X } X free(msg); X X if (resp) { X for (i = 0; i < pam_prompts; i++) { X /* X * Note that PAM is underspecified wrt free()'ing resp[i].resp. X * It's not clear if I should free it, or if the application X * has to. Therefore most (all?) apps won't free() it, and I X * can't either, as I am not sure it was malloc()'d. All PAM X * implementations I've seen leak memory here. Not so bad, IFF X * you fork/exec for each PAM authentication (as is typical). X */ X#if 0 X if (resp[i].resp) X free(resp[i].resp); X#endif /* 0 */ X } X /* This does not lose resp[i].resp if the application saved a copy. */ X free(resp); X } X X return (pamret ? KRB5KRB_ERR_GENERIC : 0); X} X Xkrb5_prompter_fct pam_prompter = heimdal_pam_prompter; END-of-lib/libpam/modules/pam_kerberos5/compat_heimdal.c echo x - lib/libpam/modules/pam_kerberos5/pam_krb5.h sed 's/^X//' >lib/libpam/modules/pam_kerberos5/pam_krb5.h << 'END-of-lib/libpam/modules/pam_kerberos5/pam_krb5.h' X/* X * pam_krb5.h X * X * $Id: pam_krb5.h,v 1.5 1999/01/19 23:43:10 fcusack Exp $ X */ X Xint get_user_info(pam_handle_t *, char *, int, char **); Xint verify_krb_v5_tgt(krb5_context, krb5_ccache, char *, int); Xvoid cleanup_cache(pam_handle_t *, void *, int); X Xkrb5_prompter_fct pam_prompter; X Xconst char *compat_princ_component(krb5_context, krb5_principal, int); Xvoid compat_free_data_contents(krb5_context, krb5_data *); Xkrb5_error_code compat_cc_next_cred(krb5_context, const krb5_ccache, X krb5_cc_cursor *, krb5_creds *); X X#ifndef ENCTYPE_DES_CBC_MD5 X#define ENCTYPE_DES_CBC_MD5 ETYPE_DES_CBC_MD5 X#endif X X END-of-lib/libpam/modules/pam_kerberos5/pam_krb5.h echo x - lib/libpam/modules/pam_kerberos5/COPYRIGHT sed 's/^X//' >lib/libpam/modules/pam_kerberos5/COPYRIGHT << 'END-of-lib/libpam/modules/pam_kerberos5/COPYRIGHT' Xpam_krb5: X XCopyright (c) Frank Cusack, 1999-2000. Xfcusack@fcusack.com XAll rights reserved X XRedistribution and use in source and binary forms, with or without Xmodification, are permitted provided that the following conditions Xare met: X1. Redistributions of source code must retain the above copyright X notice, and the entire permission notice in its entirety, X including the disclaimer of warranties. X2. Redistributions in binary form must reproduce the above copyright X notice, this list of conditions and the following disclaimer in the X documentation and/or other materials provided with the distribution. X3. The name of the author may not be used to endorse or promote X products derived from this software without specific prior X written permission. X XALTERNATIVELY, this product may be distributed under the terms of Xthe GNU Public License, in which case the provisions of the GPL are Xrequired INSTEAD OF the above restrictions. (This clause is Xnecessary due to a potential bad interaction between the GPL and Xthe restrictions contained in a BSD-style copyright.) X XTHIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED XWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES XOF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE XDISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, XINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES X(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR XSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) XHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, XSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) XARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED XOF THE POSSIBILITY OF SUCH DAMAGE. X X--------------------------------------------------------------------------- X XThis software may contain code from Naomaru Itoi: X XPAM-kerberos5 module Copyright notice. XNaomaru Itoi , June 24, 1997. X X---------------------------------------------------------------------------- XCOPYRIGHT (c) 1997 XTHE REGENTS OF THE UNIVERSITY OF MICHIGAN XALL RIGHTS RESERVED X XPERMISSION IS GRANTED TO USE, COPY, CREATE DERIVATIVE WORKS AND REDISTRIBUTE XTHIS SOFTWARE AND SUCH DERIVATIVE WORKS FOR ANY PURPOSE, SO LONG AS THE NAME XOF THE UNIVERSITY OF MICHIGAN IS NOT USED IN ANY ADVERTISING OR PUBLICITY XPERTAINING TO THE USE OR DISTRIBUTION OF THIS SOFTWARE WITHOUT SPECIFIC, XWRITTEN PRIOR AUTHORIZATION. IF THE ABOVE COPYRIGHT NOTICE OR ANY OTHER XIDENTIFICATION OF THE UNIVERSITY OF MICHIGAN IS INCLUDED IN ANY COPY OF ANY XPORTION OF THIS SOFTWARE, THEN THE DISCLAIMER BELOW MUST ALSO BE INCLUDED. X XTHE SOFTWARE IS PROVIDED AS IS, WITHOUT REPRESENTATION FROM THE UNIVERSITY OF XMICHIGAN AS TO ITS FITNESS FOR ANY PURPOSE, AND WITHOUT WARRANTY BY THE XUNIVERSITY OF MICHIGAN OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING XWITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABITILY AND FITNESS FOR A XPARTICULAR PURPOSE. THE REGENTS OF THE UNIVERSITY OF MICHIGAN SHALL NOT BE XLIABLE FOR ANY DAMAGES, INCLUDING SPECIAL, INDIRECT, INCIDENTAL, OR XCONSEQUENTIAL DAMAGES, WITH RESPECT TO ANY CLAIM ARISING OUT OF OR IN XCONNECTION WITH THE USE OF THE SOFTWARE, EVEN IF IT HAS BEEN OR IS HEREAFTER XADVISED OF THE POSSIBILITY OF SUCH DAMAGES. X XPAM-kerberos5 module is written based on PAM-kerberos4 module Xby Derrick J. Brashear and kerberos5-1.0pl1 by M.I.T. kerberos team. XPermission to use, copy, modify, distribute this software is hereby Xgranted, as long as it is granted by Derrick J. Brashear and XM.I.T. kerberos team. Followings are their copyright information. X---------------------------------------------------------------------------- X XThis software may contain code from Derrick J. Brashear: X X XCopyright (c) Derrick J. Brashear, 1996. All rights reserved X XRedistribution and use in source and binary forms, with or without Xmodification, are permitted provided that the following conditions Xare met: X1. Redistributions of source code must retain the above copyright X notice, and the entire permission notice in its entirety, X including the disclaimer of warranties. X2. Redistributions in binary form must reproduce the above copyright X notice, this list of conditions and the following disclaimer in the X documentation and/or other materials provided with the distribution. X3. The name of the author may not be used to endorse or promote X products derived from this software without specific prior X written permission. X XALTERNATIVELY, this product may be distributed under the terms of Xthe GNU Public License, in which case the provisions of the GPL are Xrequired INSTEAD OF the above restrictions. (This clause is Xnecessary due to a potential bad interaction between the GPL and Xthe restrictions contained in a BSD-style copyright.) X XTHIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED XWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES XOF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE XDISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, XINDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES X(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR XSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) XHOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, XSTRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) XARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED XOF THE POSSIBILITY OF SUCH DAMAGE. X X---------------------------------------------------------------------------- X XThis software may contain code from MIT Kerberos 5: X XCopyright Notice and Legal Administrivia X---------------------------------------- X XCopyright (C) 1996 by the Massachusetts Institute of Technology. X XAll rights reserved. X XExport of this software from the United States of America may require Xa specific license from the United States Government. It is the Xresponsibility of any person or organization contemplating export to Xobtain such a license before exporting. X XWITHIN THAT CONSTRAINT, permission to use, copy, modify, and Xdistribute this software and its documentation for any purpose and Xwithout fee is hereby granted, provided that the above copyright Xnotice appear in all copies and that both that copyright notice and Xthis permission notice appear in supporting documentation, and that Xthe name of M.I.T. not be used in advertising or publicity pertaining Xto distribution of the software without specific, written prior Xpermission. M.I.T. makes no representations about the suitability of Xthis software for any purpose. It is provided "as is" without express Xor implied warranty. X XTHIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR XIMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED XWARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. X XIndividual source code files are copyright MIT, Cygnus Support, XOpenVision, Oracle, Sun Soft, and others. X XProject Athena, Athena, Athena MUSE, Discuss, Hesiod, Kerberos, Moira, Xand Zephyr are trademarks of the Massachusetts Institute of Technology X(MIT). No commercial use of these trademarks may be made without Xprior written permission of MIT. X X"Commercial use" means use of a name in a product or other for-profit Xmanner. It does NOT prevent a commercial firm from referring to the XMIT trademarks in order to convey information (although in doing so, Xrecognition of their trademark status should be given). X XThe following copyright and permission notice applies to the XOpenVision Kerberos Administration system located in kadmin/create, Xkadmin/dbutil, kadmin/passwd, kadmin/server, lib/kadm5, and portions Xof lib/rpc: X X Copyright, OpenVision Technologies, Inc., 1996, All Rights Reserved X X WARNING: Retrieving the OpenVision Kerberos Administration system X source code, as described below, indicates your acceptance of the X following terms. If you do not agree to the following terms, do not X retrieve the OpenVision Kerberos administration system. X X You may freely use and distribute the Source Code and Object Code X compiled from it, with or without modification, but this Source X Code is provided to you "AS IS" EXCLUSIVE OF ANY WARRANTY, X INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY OR X FITNESS FOR A PARTICULAR PURPOSE, OR ANY OTHER WARRANTY, WHETHER X EXPRESS OR IMPLIED. IN NO EVENT WILL OPENVISION HAVE ANY LIABILITY X FOR ANY LOST PROFITS, LOSS OF DATA OR COSTS OF PROCUREMENT OF X SUBSTITUTE GOODS OR SERVICES, OR FOR ANY SPECIAL, INDIRECT, OR X CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT, INCLUDING, X WITHOUT LIMITATION, THOSE RESULTING FROM THE USE OF THE SOURCE X CODE, OR THE FAILURE OF THE SOURCE CODE TO PERFORM, OR FOR ANY X OTHER REASON. X X OpenVision retains all copyrights in the donated Source Code. OpenVision X also retains copyright to derivative works of the Source Code, whether X created by OpenVision or by a third party. The OpenVision copyright X notice must be preserved if derivative works are made based on the X donated Source Code. X X OpenVision Technologies, Inc. has donated this Kerberos X Administration system to MIT for inclusion in the standard X Kerberos 5 distribution. This donation underscores our X commitment to continuing Kerberos technology development X and our gratitude for the valuable work which has been X performed by MIT and the Kerberos community. X X END-of-lib/libpam/modules/pam_kerberos5/COPYRIGHT echo x - lib/libpam/modules/pam_kerberos5/README.fcusack sed 's/^X//' >lib/libpam/modules/pam_kerberos5/README.fcusack << 'END-of-lib/libpam/modules/pam_kerberos5/README.fcusack' XThis is the README for pam_krb5, a PAM module which support Kerberos 5 Xauthentication. X XThis software is Copyright (c) 1999-2000 Frank Cusack. XAll Rights Reserved. X XSee the COPYRIGHT file, included with this distribution, for copyright Xand redistribution information. X XAuthor: XFrank Cusack X X X XI. Kerberos notes X XThis PAM module requires the MIT 1.1+ release of Kerberos, or the Cygnus XCNS distribution. It has not been tested against heimdal or any other XKerberos distributions. X XUnlike other PAM Kerberos 5 modules out there, this one does not Xuse any private Kerberos interfaces. Thus, you need only the Xheader files and libraries that are part of the Kerberos distribution. X X XII. OS notes X XThis software has been tested against Solaris 2.6. It should compile Xagainst Linux (distributions?) with minimal (if any) changes. Reports Xof OS [in]compatibilities are welcomed. X Xdtlogin on Solaris doesn't support xrealm logins (probably a good thing). X XIII. PAM notes/open issues X Xauth module: XWhen is pam_sm_setcred() ever called with flags other than PAM_ESTABLISH_CRED? XIt would be fairly easy to support PAM_DELETE_CRED. X Xacct module: XI believe this to be complete. X Xsession module: XThis is complete (both functions just return success). X Xpasswd module: XWhen is pam_sm_chauthtok() ever called with flags other than XPAM_UPDATE_AUTHTOK? X X XIV. Usage X XSimply change /etc/pam.conf to include this module. Make sure to include Xthe acct category whenever you use the auth category, or .k5login will Xnot get checked. X XYou probably want to make this module "sufficient", before your unix X(or other) module(s). X X XV. Acknowledgements X XThanks to Naomaru Itoi , XCurtis King , and Derrick Brashear , Xall of whom have written and made available Kerberos 4/5 modules. XAlthough no code in this module is directly from these author's modules, X(except the get_user_info() routine in support.c; derived from whichever Xof these authors originally wrote the first module the other 2 copied from), Xit was extremely helpful to look over their code which aided in my design. X END-of-lib/libpam/modules/pam_kerberos5/README.fcusack exit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 12:28: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 4D53837B719 for ; Mon, 5 Mar 2001 12:28:03 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f25KRK442804; Mon, 5 Mar 2001 12:27:20 -0800 (PST) (envelope-from dillon) Date: Mon, 5 Mar 2001 12:27:20 -0800 (PST) From: Matt Dillon Message-Id: <200103052027.f25KRK442804@earth.backplane.com> To: Chris Dillon Cc: "E.B. Dreger" , Subject: Re: Machines are getting too damn fast References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Mon, 5 Mar 2001, E.B. Dreger wrote: : :I've got a ServerWorks III HE-SL system with 512MB of two-way :interleaved PC133 SDRAM and dual PIII-800's. Is that close enough? ::-) : :Here is my "memory bandwidth test", much much simpler and less :scientific than Matt's: : :dd if=/dev/zero of=/dev/null bs=10m count=1000 :1000+0 records in :1000+0 records out :10485760000 bytes transferred in 23.716504 secs (442129245 bytes/sec) : :I just did a recent 4.2-STABLE 'make -j 4 buildworld' on that system :in just over 34 minutes. Here's the time output: :1980.707u 768.223s 34:20.89 133.3% 1297+1456k 39517+6202io 1661pf+0w That is quite impressive for SDRAM, though I'm not exactly sure what's being measured due to the way /dev/zero and /dev/null operate. On my system the above dd test returns around 883MB/sec so I would guess that it is only doing a read-swipe on the memory. (sony 1.3G / RIMM) apollo:/home/dillon> dd if=/dev/zero of=/dev/null bs=10m count=1000 1000+0 records in 1000+0 records out 10485760000 bytes transferred in 11.867550 secs (883565697 bytes/sec) On the DELL 2400 I get: 1048576000 bytes transferred in 2.737955 secs (382977810 bytes/sec) The only thing I don't like about this baby is the IBM IDE hard drive's write performance. I only get 10-12 MBytes/sec. Read performance is incredible, though... I get 37MB/sec dd'ing from /dev/ad0s1a to /dev/null. ad0: 58644MB [119150/16/63] at ata0-master UDMA100 -Matt :> If one _truly_ needs the bandwidth of Rambus (which, IIRC, is :> higher real-world latency than SDRAM), then how about having the :> bus bandwidth to back it up? : :The higher real-world latency of RDRAM over SDRAM is what makes the :benefits of its higher bandwidth so questionable. PC2100 DDR-SDRAM -- :which has higher latencies than regular SDRAM but still lower than :RDRAM -- should have it beat soundly, though we'll have to wait for :some systems that are actually designed to take advantage of it to say :for sure. :-) : : :-- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 14:28:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id 0652D37B718 for ; Mon, 5 Mar 2001 14:28:28 -0800 (PST) (envelope-from dphoenix@bravenet.com) Received: (qmail 29 invoked by uid 1000); 5 Mar 2001 22:25:40 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Mar 2001 22:25:40 -0000 Date: Mon, 5 Mar 2001 14:25:40 -0800 (PST) From: Dan Phoenix To: freebsd-hackers@freebsd.org Subject: systat -vmstat or iostat IO help 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 would like to get a more accurate picture of each. example: webserver....abit of a high load......1 ide drive..memory ok [root@lotho dphoenix]# uptime 2:25PM up 2 days, 21:10, 1 user, load averages: 6.94, 8.23, 9.34 [root@lotho dphoenix]# systat -iostat /0 /10 /20 /30 /40 /50 /60 /70 /80 /90 /100 ad0 MB/s tps|XXXXXXX acd0 MB/s tps| fd0 MB/s tps| md0 MB/s tps| systat -vmstat Disks ad0 acd0 fd0 md0 89 ofod intrn KB/t 4.35 0.00 0.00 0.00 85 %slo-z 61952 buf tps 13 0 0 0 104 tfree 42 dirtybuf MB/s 0.05 0.00 0.00 0.00 36095 desiredvnodes % busy 100 0 0 0 58692 numvnodes 43991 freevnodes well vmstat showing 100% busy and iostat showing 10% busy...... IO an issue here or not? -- Dan +------------------------------------------------------+ | BRAVENET WEB SERVICES | | dan@bravenet.com | | make installworld | | ln -s /var/qmail/bin/sendmail /usr/sbin/sendmail | | ln -s /var/qmail/bin/newaliases /usr/sbin/newaliases | +______________________________________________________+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 14:30:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id A2DE337B718 for ; Mon, 5 Mar 2001 14:30:33 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) 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 QAA84736; Mon, 5 Mar 2001 16:30:22 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 5 Mar 2001 16:30:21 -0600 (CST) From: Chris Dillon To: Matt Dillon Cc: "E.B. Dreger" , Subject: Re: Machines are getting too damn fast In-Reply-To: <200103052027.f25KRK442804@earth.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 Mon, 5 Mar 2001, Matt Dillon wrote: > :On Mon, 5 Mar 2001, E.B. Dreger wrote: > : > :I've got a ServerWorks III HE-SL system with 512MB of two-way > :interleaved PC133 SDRAM and dual PIII-800's. Is that close enough? > ::-) > : > :Here is my "memory bandwidth test", much much simpler and less > :scientific than Matt's: > : > :dd if=/dev/zero of=/dev/null bs=10m count=1000 > :1000+0 records in > :1000+0 records out > :10485760000 bytes transferred in 23.716504 secs (442129245 bytes/sec) > : > :I just did a recent 4.2-STABLE 'make -j 4 buildworld' on that system > :in just over 34 minutes. Here's the time output: > :1980.707u 768.223s 34:20.89 133.3% 1297+1456k 39517+6202io 1661pf+0w > > That is quite impressive for SDRAM, though I'm not exactly sure what's > being measured due to the way /dev/zero and /dev/null operate. On > my system the above dd test returns around 883MB/sec so I would guess > that it is only doing a read-swipe on the memory. I figured if /dev/null and /dev/zero had relatively little memory impact, which I figure is the case, it would matter more how dd does its blocking. If you reduce the blocksize to something that will fit in your L2 caches, you'll see a very significant increase in throughput. For example, on the PIII-850 (116MHz FSB and SDRAM, its overclocked) here on my desk with 256KB L2 cache: dd if=/dev/zero of=/dev/null bs=10m count=200 200+0 records in 200+0 records out 2097152000 bytes transferred in 10.032157 secs (209042982 bytes/sec) dd if=/dev/zero of=/dev/null bs=512k count=4000 4000+0 records in 4000+0 records out 2097152000 bytes transferred in 8.229456 secs (254834825 bytes/sec) dd if=/dev/zero of=/dev/null bs=128k count=16000 16000+0 records in 16000+0 records out 2097152000 bytes transferred in 1.204001 secs (1741819224 bytes/sec) Now THAT is a significant difference. :-) > (sony 1.3G / RIMM) > apollo:/home/dillon> dd if=/dev/zero of=/dev/null bs=10m count=1000 > 1000+0 records in > 1000+0 records out > 10485760000 bytes transferred in 11.867550 secs (883565697 bytes/sec) Very impressive. Looks about right given the theoretical maximum bandwidth of your memory system. From what I've been gathering, that dd-test shows roughly 1/4 of the total theoretical memory bandwidth (two reads and two writes happening?), minus any chipset deficiencies when it comes to memory transfers. For example, this PIII-850 on a BX board is actually an overclocked 700MHz 100MHz FSB PIII. So, it is using a 116MHz FSB and the SDRAM is running at that speed as well. The theoretical maximum bandwidth of this should be 8(bytes-per-clock)*116(MHz)=928MB/sec. I'm seeing about 210MB/sec on the dd-test, so thats pretty close to 1/4. In your case, you are using PC800 RDRAM on a Pentium-4 system on an i850 board, which IIRC uses a dual-channel RDRAM setup, theoretically doubling the bandwidth that you could get with only one channel. Since you're using dual RDRAM channels of PC800 RDRAM, that would be 4(bytes-per-clock)*800(MHz)=3200MB/sec. Again, the dd-test is pretty close to 1/4 the total theoretical bandwidth (actually a little over), since you achieved about 883MB/sec. In an HE-SL system I have here, it uses dual-interleaved PC133 SDRAM. That would be 16(bytes-per-clock)*133(MHz)=2128MB/sec. The dd-test is a little off the mark of 1/4 the theoretical maximum bandwidth at 442MB/sec, but this thing is the only system I've seen the dd-test on so far that hasn't used an Intel chipset. The Intel chipsets have shown in other benchmarks to be more efficient than anybody else's chipsets (VIA, AMD, RCC, etc) at doing the memory thing, so that makes sense. I think I'm on to something here with this 'cheap' dd-test. :-) A PC2100 DDR-SDRAM system will have a theoretical bandwidth of 2100MB/sec (duh), so a dd-test should come out to around 525MB/sec. I'm guessing it will actually be a bit less since the AMD and especially VIA chipsets aren't going to be anywhere near as efficient as the Intels have been. I'm guessing 95% efficiency for the AMD, so about 500MB/sec from the dd-test. 85% efficient for the VIA, so around 450MB/sec. Anyone care to test that on one or both of the new AMD-chipset and VIA-chipset DDR systems and see how close it comes? :-) > The only thing I don't like about this baby is the IBM IDE hard drive's > write performance. I only get 10-12 MBytes/sec. Read performance is > incredible, though... I get 37MB/sec dd'ing from /dev/ad0s1a to > /dev/null. > > ad0: 58644MB [119150/16/63] at ata0-master UDMA100 That is a 75GXP series, which is supposed to be one of the fastest, if not the fastest, IDE drive on the market right now. Hmm. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 14:39:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from jack.go2net.com (jack.go2net.com [64.50.65.20]) by hub.freebsd.org (Postfix) with SMTP id EAEA237B718 for ; Mon, 5 Mar 2001 14:39:22 -0800 (PST) (envelope-from william.carrel@infospace.com) Received: (qmail 94979 invoked from network); 5 Mar 2001 22:44:23 -0000 Received: from ketel.go2net.com (10.200.10.75) by jack.go2net.com with SMTP; 5 Mar 2001 22:44:23 -0000 Received: (qmail 6838 invoked from network); 5 Mar 2001 22:12:27 -0000 Received: from gasket.go2net.com ([10.225.32.118]) (envelope-sender ) by ketel.go2net.com (qmail-ldap-1.03) with SMTP for ; 5 Mar 2001 22:12:27 -0000 Received: by gasket.go2net.com (Postfix, from userid 492) id B46795D40; Mon, 5 Mar 2001 14:12:24 -0800 (PST) To: freebsd-hackers@freebsd.org Subject: Fix for scrambled top display on SMP [PR 22270] From: William Carrel Date: 05 Mar 2001 14:12:24 -0800 Message-ID: Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Thalia) 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 just three lines of code. :) I have SMP machines here that have some pretty absurdly long usernames thanks to some NIS accounts (20+ chars). Unfortunately the namelength truncation code in /usr/bin/top currently doesn't take into account the 'C' (last CPU) field that SMP machines have. This patch makes long names just a little shorter so that the display doesn't wrap weirdly on a 80 column display. http://www.freebsd.org/cgi/query-pr.cgi?pr=22270 PR's been stale for a bit so I thought I'd draw some attention. Thanks for reading. -- Andy Carrel - william.carrel@infospace.com - +1 (206) 357-4607 Internet Sys. Eng. - Enterprise Infrastructure & Security - InfoSpace To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 14:48:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E0F2637B718 for ; Mon, 5 Mar 2001 14:48:23 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f25MmNj10637 for hackers@freebsd.org; Mon, 5 Mar 2001 14:48:23 -0800 (PST) Date: Mon, 5 Mar 2001 14:48:23 -0800 From: Alfred Perlstein To: hackers@freebsd.org Subject: fixing flex definitions? Message-ID: <20010305144823.B8663@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The flex scanner template has this in it: #ifndef YY_ALWAYS_INTERACTIVE #ifndef YY_NEVER_INTERACTIVE extern int isatty YY_PROTO(( int )); #endif #endif Which seems to be the wrong thing to do. Would this be an ok fix? I'm worried about the YY_PROTO() messing things up anyone know what the point of doing it this way is? Index: flex.skl =================================================================== RCS file: /home/ncvs/src/usr.bin/lex/flex.skl,v retrieving revision 1.4 diff -u -u -r1.4 flex.skl --- flex.skl 1999/10/27 07:56:44 1.4 +++ flex.skl 2001/03/05 22:49:01 @@ -1180,7 +1180,8 @@ %- #ifndef YY_ALWAYS_INTERACTIVE #ifndef YY_NEVER_INTERACTIVE -extern int isatty YY_PROTO(( int )); +/* for isatty() */ +#include #endif #endif -- -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 Mar 5 14:55:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id E18ED37B71A for ; Mon, 5 Mar 2001 14:55:47 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f25MtaA13182; Mon, 5 Mar 2001 14:55:36 -0800 (PST) (envelope-from jhb@FreeBSD.org) 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: <20010305144823.B8663@fw.wintelcom.net> Date: Mon, 05 Mar 2001 14:55:22 -0800 (PST) From: John Baldwin To: Alfred Perlstein Subject: RE: fixing flex definitions? Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Mar-01 Alfred Perlstein wrote: > The flex scanner template has this in it: > >#ifndef YY_ALWAYS_INTERACTIVE >#ifndef YY_NEVER_INTERACTIVE > extern int isatty YY_PROTO(( int )); >#endif >#endif > > Which seems to be the wrong thing to do. > > Would this be an ok fix? I'm worried about the YY_PROTO() messing > things up anyone know what the point of doing it this way is? I'm guessing YY_PROTO is like __P() so it can be "compilable with a K&R Old Testament compiler." -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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 Mon Mar 5 15: 6:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 2C57837B71E; Mon, 5 Mar 2001 15:06:42 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f25N6f524147; Mon, 5 Mar 2001 15:06:41 -0800 (PST) (envelope-from obrien) Date: Mon, 5 Mar 2001 15:06:40 -0800 From: "David O'Brien" To: John Baldwin Cc: Alfred Perlstein , hackers@FreeBSD.org Subject: Re: fixing flex definitions? Message-ID: <20010305150639.A23106@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <20010305144823.B8663@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Mon, Mar 05, 2001 at 02:55:22PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 05, 2001 at 02:55:22PM -0800, John Baldwin wrote: > I'm guessing YY_PROTO is like __P() so it can be "compilable with a K&R Old > Testament compiler." Yes. And in this case, the output of lex *must* be portable to K&R. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 15:11: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from leviathan.umiacs.umd.edu (leviathan.umiacs.umd.edu [128.8.120.189]) by hub.freebsd.org (Postfix) with ESMTP id 874A637B718 for ; Mon, 5 Mar 2001 15:11:04 -0800 (PST) (envelope-from bargle@umiacs.umd.edu) Received: from leviathan.umiacs.umd.edu (localhost [127.0.0.1]) by leviathan.umiacs.umd.edu (8.9.3/8.9.1) with ESMTP id SAA25244 for ; Mon, 5 Mar 2001 18:11:03 -0500 (EST) Message-Id: <200103052311.SAA25244@leviathan.umiacs.umd.edu> To: hackers@freebsd.org Subject: Strange, possibly network-related, crashes Date: Mon, 05 Mar 2001 18:11:03 -0500 From: Gary Jackson Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having some problems with a 4.2-Release NAT box. If I leave it up and connected to the outside world for a couple of days, it starts crashing with a page not found type of error (I'm sorry I don't have the full text of the error - it finishes crashing and reboots before I can read the error from the screen). It will continue to come up, then crash, repeatedly, until I turn it off or disconnect it from the outside world. This has happened twice since I set the box up, and it takes two to three days for the fun to begin. I had 4.0 installed on the same machine, and I never had any problems with it: it would stay up for months at a time, with little intervention on my part. The problems started when I made the following changes to the machine: 1. I upgraded the OS to 4.2 2. I installed an 802.11 PCI card The machine is currently configured with two intel FE network cards (using the fxp device), and a Cisco AiroNet 340 802.11 card (using the an device). If someone has any idea as to what this might be, that would be cool if you could tell me. However, I don't expect that kind of luck. I'm interested in information on how to get the kernel to drop to the debugger when it wrecks like that, so I can fix the problem myself, or write a more useful query to this list. -- Gary Jackson bargle@umiacs.umd.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 15:23:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from chopper.Poohsticks.ORG (chopper.poohsticks.org [63.227.60.73]) by hub.freebsd.org (Postfix) with ESMTP id 0314B37B738 for ; Mon, 5 Mar 2001 15:23:31 -0800 (PST) (envelope-from drew@chopper.Poohsticks.ORG) Received: from chopper.Poohsticks.ORG (drew@localhost.poohsticks.org [127.0.0.1]) by chopper.Poohsticks.ORG (8.10.1/8.10.1) with ESMTP id f25NNQn26752; Mon, 5 Mar 2001 16:23:26 -0700 Message-Id: <200103052323.f25NNQn26752@chopper.Poohsticks.ORG> To: Alfred Perlstein Cc: hackers@FreeBSD.ORG Subject: Re: fixing flex definitions? In-reply-to: Your message of "Mon, 05 Mar 2001 14:48:23 PST." <20010305144823.B8663@fw.wintelcom.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <26748.983834606.1@chopper.Poohsticks.ORG> Date: Mon, 05 Mar 2001 16:23:26 -0700 From: Drew Eckhardt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010305144823.B8663@fw.wintelcom.net>, bright@wintelcom.net writes : >Would this be an ok fix? I'm worried about the YY_PROTO() messing >things up anyone know what the point of doing it this way is? Compatability with pre-ANSI 'C' compilers, just like __P from /usr/include/sys/cdefs.h. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 15:25:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 1221C37B718 for ; Mon, 5 Mar 2001 15:25:16 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f25NOin45226; Mon, 5 Mar 2001 15:24:44 -0800 (PST) (envelope-from dillon) Date: Mon, 5 Mar 2001 15:24:44 -0800 (PST) From: Matt Dillon Message-Id: <200103052324.f25NOin45226@earth.backplane.com> To: Chris Dillon Cc: "E.B. Dreger" , Subject: Re: Machines are getting too damn fast References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :throughput. For example, on the PIII-850 (116MHz FSB and SDRAM, its :overclocked) here on my desk with 256KB L2 cache: : :dd if=/dev/zero of=/dev/null bs=512k count=4000 :4000+0 records in :4000+0 records out :2097152000 bytes transferred in 8.229456 secs (254834825 bytes/sec) : :dd if=/dev/zero of=/dev/null bs=128k count=16000 :16000+0 records in :16000+0 records out :2097152000 bytes transferred in 1.204001 secs (1741819224 bytes/sec) : :Now THAT is a significant difference. :-) Interesting. I get very different results with the 1.3 GHz P4. The best I seem to get is 1.4 GBytes/sec. I'm not sure what the L2 cache is on the box, but it's definitely a consumer model. dd if=/dev/zero of=/dev/null bs=512k count=4000 2097152000 bytes transferred in 2.363903 secs (887156520 bytes/sec) dd if=/dev/zero of=/dev/null bs=128k count=16000 2097152000 bytes transferred in 1.471046 secs (1425619621 bytes/sec) If I use lower block sizes the syscall overhead blows up the performance (it gets lower rather then higher). So I figure I don't have as much L2 as on your system. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 15:38:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 13C6237B718 for ; Mon, 5 Mar 2001 15:38:29 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) 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 RAA85408; Mon, 5 Mar 2001 17:38:25 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 5 Mar 2001 17:38:24 -0600 (CST) From: Chris Dillon To: Matt Dillon Cc: "E.B. Dreger" , Subject: Re: Machines are getting too damn fast In-Reply-To: <200103052324.f25NOin45226@earth.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 Mon, 5 Mar 2001, Matt Dillon wrote: > :throughput. For example, on the PIII-850 (116MHz FSB and SDRAM, its > :overclocked) here on my desk with 256KB L2 cache: > : > :dd if=/dev/zero of=/dev/null bs=512k count=4000 > :4000+0 records in > :4000+0 records out > :2097152000 bytes transferred in 8.229456 secs (254834825 bytes/sec) > : > :dd if=/dev/zero of=/dev/null bs=128k count=16000 > :16000+0 records in > :16000+0 records out > :2097152000 bytes transferred in 1.204001 secs (1741819224 bytes/sec) > : > :Now THAT is a significant difference. :-) > > Interesting. I get very different results with the 1.3 GHz P4. The > best I seem to get is 1.4 GBytes/sec. I'm not sure what the L2 cache > is on the box, but it's definitely a consumer model. > > dd if=/dev/zero of=/dev/null bs=512k count=4000 > 2097152000 bytes transferred in 2.363903 secs (887156520 bytes/sec) > > dd if=/dev/zero of=/dev/null bs=128k count=16000 > 2097152000 bytes transferred in 1.471046 secs (1425619621 bytes/sec) > > If I use lower block sizes the syscall overhead blows up the > performance (it gets lower rather then higher). So I figure I don't > have as much L2 as on your system. IIRC, Intel is using a very different caching method on the P4 from what we are used to on just about every other x86 processor we've seen. Well, I can't remember if the data cache has changed much, but the instruction cache has. I doubt the difference in instruction cache behaviour would make a difference here though. Hmm. I wonder if it makes any difference that I'm using -march=pentium -mcpu=pentium for my CFLAGS? Actually, the kernel I tested on might even be using -march/-mcpu=pentiumpro, since I only recently changed it to =pentium to allow me to do buildworlds for another Pentium-class machine. I did wonder the same thing a while back and did the same test with and without the optimizations, and with pentiumpro opts the big block size transfer rate went _down_ a little bit, which was odd. I didn't compare with L2-cache-friendly blocks, though. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 16:13:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 0B25737B718 for ; Mon, 5 Mar 2001 16:13:49 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f260DHY46910; Mon, 5 Mar 2001 16:13:17 -0800 (PST) (envelope-from dillon) Date: Mon, 5 Mar 2001 16:13:17 -0800 (PST) From: Matt Dillon Message-Id: <200103060013.f260DHY46910@earth.backplane.com> To: Chris Dillon Cc: "E.B. Dreger" , Subject: Re: Machines are getting too damn fast References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :IIRC, Intel is using a very different caching method on the P4 from :what we are used to on just about every other x86 processor we've :seen. Well, I can't remember if the data cache has changed much, but :the instruction cache has. I doubt the difference in instruction :cache behaviour would make a difference here though. Hmm. : :I wonder if it makes any difference that I'm using -march=pentium :-mcpu=pentium for my CFLAGS? Actually, the kernel I tested on might :even be using -march/-mcpu=pentiumpro, since I only recently changed :it to =pentium to allow me to do buildworlds for another Pentium-class :machine. I did wonder the same thing a while back and did the same :test with and without the optimizations, and with pentiumpro opts the :big block size transfer rate went _down_ a little bit, which was odd. :I didn't compare with L2-cache-friendly blocks, though. : :-- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net I modified my original C program again, this time to simply read the data from memory given a block size in kilobytes as an argument. I had to throw in a little __asm to do it right, but here are my results. It shows about 3.2 GBytes/sec from the L2 (well, insofar as my 3-instruction loop goes), and about 1.4 GBytes/sec from main memory. NOTE: cc x.c -O2 -o x ./x 4 3124.96 MBytes/sec (read) ./x 8 3242.45 MBytes/sec (read) ./x 16 3060.93 MBytes/sec (read) ./x 32 3359.97 MBytes/sec (read) ./x 64 3362.06 MBytes/sec (read) ./x 128 3365.53 MBytes/sec (read) ./x 240 3307.86 MBytes/sec (read) ./x 256 3232.33 MBytes/sec (read) ./x 512 1396.45 MBytes/sec (read) ./x 1024 1397.90 MBytes/sec (read) In contrast I get 1052.50 MBytes/sec on the Dell 2400 from the L2, and 444 MBytes/sec from main memory. -Matt /* * NOTE: cc x.c -O2 -o x */ #include #include #include #include #include #include int deltausecs(struct timeval *tv1, struct timeval *tv2); int main(int ac, char **av) { int i; int bytes; double dtime; struct timeval tv1; struct timeval tv2; char *buf; if (ac == 1) { fprintf(stderr, "%s numKB\n", av[0]); exit(1); } bytes = strtol(av[1], NULL, 0) * 1024; if (bytes < 4 * 1024 || bytes > 256 * 1024 * 1024) { fprintf(stderr, "Oh please. Try a reasonable value\n"); exit(1); } buf = malloc(bytes); if (buf == NULL) { perror("malloc"); exit(1); } bzero(buf, bytes); gettimeofday(&tv1, NULL); for (i = 0; i < 1000000000; i += bytes) { register int j; for (j = bytes - 4; j >= 0; j -= 4) __asm __volatile("movl (%0,%1),%%eax" : "=r" (buf), "=r" (j) : "0" (buf), "1" (j) : "ax" ); } gettimeofday(&tv2, NULL); dtime = (double)deltausecs(&tv1, &tv2); printf("%6.2f MBytes/sec (read)\n", (double)1000000000 / dtime); return(0); } int deltausecs(struct timeval *tv1, struct timeval *tv2) { int usec; usec = (tv2->tv_usec + 1000000 - tv1->tv_usec); usec += (tv2->tv_sec - tv1->tv_sec - 1) * 1000000; return(usec); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 16:24:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5E02837B719 for ; Mon, 5 Mar 2001 16:24:04 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f260Nrd24686; Mon, 5 Mar 2001 17:23:53 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103060023.f260Nrd24686@harmony.village.org> To: sthaug@nethelp.no Subject: Re: Missing support in FreeBSD for large file sizes? Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 05 Mar 2001 18:24:24 +0100." <13458.983813064@verdi.nethelp.no> References: <13458.983813064@verdi.nethelp.no> Date: Mon, 05 Mar 2001 17:23:53 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <13458.983813064@verdi.nethelp.no> sthaug@nethelp.no writes: : What I can't understand is the reference to missing support for large : file sizes - as far as I know, that's one of FreeBSD's strengths! Anybody : care to guess what they mean here? It is crap. FreeBSD's API supports up to 2^63 byte files, but the kernel internal structures limit this to 2^41, or 2TB. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 16:31:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id B373437B719 for ; Mon, 5 Mar 2001 16:31:45 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f260VjC47207; Mon, 5 Mar 2001 16:31:45 -0800 (PST) (envelope-from dillon) Date: Mon, 5 Mar 2001 16:31:45 -0800 (PST) From: Matt Dillon Message-Id: <200103060031.f260VjC47207@earth.backplane.com> To: Dan Phoenix Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: systat -vmstat or iostat IO help References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :systat -vmstat : :Disks ad0 acd0 fd0 md0 89 ofod intrn :KB/t 4.35 0.00 0.00 0.00 85 %slo-z 61952 buf :tps 13 0 0 0 104 tfree 42 dirtybuf :MB/s 0.05 0.00 0.00 0.00 36095 desiredvnodes :% busy 100 0 0 0 58692 numvnodes : :well vmstat showing 100% busy and iostat showing 10% busy...... :IO an issue here or not? :... :Dan systat -vmstat is correct. I usually use 'systat -vm 1'. If you see 100% busy for more then a few seconds then the disk is saturated (almost certainly seek-limited). Solutions depend on what the system is doing. Mail systems are the least scaleable, requiring you to add additional disks for spools or a stripe, or additional machines and use an MX round robin. Most other services can be scaled well simply by adding memory or cpu. SCSI disks usually do better then IDE in seek-limited situations. Higher-RPM disks can make a big difference too. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 16:38:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id B0A4E37B718 for ; Mon, 5 Mar 2001 16:38:24 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 6639D6A90D; Tue, 6 Mar 2001 11:08:21 +1030 (CST) Date: Tue, 6 Mar 2001 11:08:21 +1030 From: Greg Lehey To: Warner Losh Cc: sthaug@nethelp.no, freebsd-hackers@FreeBSD.ORG Subject: Re: Missing support in FreeBSD for large file sizes? Message-ID: <20010306110821.H13082@wantadilla.lemis.com> References: <13458.983813064@verdi.nethelp.no> <200103060023.f260Nrd24686@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103060023.f260Nrd24686@harmony.village.org>; from imp@harmony.village.org on Mon, Mar 05, 2001 at 05:23:53PM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 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 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 5 March 2001 at 17:23:53 -0700, Warner Losh wrote: > In message <13458.983813064@verdi.nethelp.no> sthaug@nethelp.no writes: >> What I can't understand is the reference to missing support for large >> file sizes - as far as I know, that's one of FreeBSD's strengths! Anybody >> care to guess what they mean here? > > It is crap. FreeBSD's API supports up to 2^63 byte files, but the > kernel internal structures limit this to 2^41, or 2TB. In fact, at the moment we don't seem to be able to build file systems of more than 1 TB. This may be a bug. 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 Mar 5 16:41:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id 96F0E37B72B for ; Mon, 5 Mar 2001 16:41:12 -0800 (PST) (envelope-from dphoenix@bravenet.com) Received: (qmail 15428 invoked by uid 1000); 6 Mar 2001 00:38:25 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Mar 2001 00:38:25 -0000 Date: Mon, 5 Mar 2001 16:38:25 -0800 (PST) From: Dan Phoenix To: Matt Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: systat -vmstat or iostat IO help In-Reply-To: <200103060031.f260VjC47207@earth.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 this is a webserver ......i am trying to figure out if cpu increase or scsi drives is better in this situation. Right now...that is a big decision because there are approx 30 fbsd webservers ....not all showing high IO from vmstat...just the ones with the highest uptime. More of a decision is a cost-effective one. Rather than buying a new machine to bring LA down would increasing IO or cpu give the servers more perf so as to not buy new servers each time...... thanks for your comments....not sure why iostat not giving correct readings, but just glad i know...thanks again. On Mon, 5 Mar 2001, Matt Dillon wrote: > Date: Mon, 5 Mar 2001 16:31:45 -0800 (PST) > From: Matt Dillon > To: Dan Phoenix > Cc: freebsd-hackers@FreeBSD.ORG > Subject: Re: systat -vmstat or iostat IO help > > :systat -vmstat > : > :Disks ad0 acd0 fd0 md0 89 ofod intrn > :KB/t 4.35 0.00 0.00 0.00 85 %slo-z 61952 buf > :tps 13 0 0 0 104 tfree 42 dirtybuf > :MB/s 0.05 0.00 0.00 0.00 36095 desiredvnodes > :% busy 100 0 0 0 58692 numvnodes > : > :well vmstat showing 100% busy and iostat showing 10% busy...... > :IO an issue here or not? > :... > :Dan > > systat -vmstat is correct. I usually use 'systat -vm 1'. If you see > 100% busy for more then a few seconds then the disk is saturated > (almost certainly seek-limited). Solutions depend on what the system > is doing. Mail systems are the least scaleable, requiring you to > add additional disks for spools or a stripe, or additional machines > and use an MX round robin. Most other services can be scaled well > simply by adding memory or cpu. SCSI disks usually do better then IDE > in seek-limited situations. Higher-RPM disks can make a big difference > too. > > -Matt > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 16:45:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id C324A37B71A for ; Mon, 5 Mar 2001 16:45:31 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f260jJg47532; Mon, 5 Mar 2001 16:45:19 -0800 (PST) (envelope-from dillon) Date: Mon, 5 Mar 2001 16:45:19 -0800 (PST) From: Matt Dillon Message-Id: <200103060045.f260jJg47532@earth.backplane.com> To: Greg Lehey Cc: Warner Losh , sthaug@nethelp.no, freebsd-hackers@FreeBSD.ORG Subject: Re: Missing support in FreeBSD for large file sizes? References: <13458.983813064@verdi.nethelp.no> <200103060023.f260Nrd24686@harmony.village.org> <20010306110821.H13082@wantadilla.lemis.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In fact, at the moment we don't seem to be able to build file systems :of more than 1 TB. This may be a bug. : :Greg 2^31 x 512 = 1TB (negative block numbers are 'special'). Not really a bug. Though I seem to recall a year or two ago someone had created a much larger partition, I'm not quite sure how it could have worked. As far as I understand the system we convert a block numbers to 512 byte blocks at the device layer so even FFS filesystems w/ large block sizes wouldn't be sufficient to get past the kernel limitation. We just have to convert everything to 64 bit offsets all the way through, especially with 500GB+ drives coming to market probably this year sometime. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 17: 2:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 3479637B71A for ; Mon, 5 Mar 2001 17:02:16 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2612FH47843; Mon, 5 Mar 2001 17:02:15 -0800 (PST) (envelope-from dillon) Date: Mon, 5 Mar 2001 17:02:15 -0800 (PST) From: Matt Dillon Message-Id: <200103060102.f2612FH47843@earth.backplane.com> To: Dan Phoenix Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: systat -vmstat or iostat IO help References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : : :this is a webserver ......i am trying to figure out if cpu increase or :scsi drives is better in this situation. Right now...that is a big :decision because there are approx 30 fbsd webservers ....not all showing :high IO from vmstat...just the ones with the highest uptime. :... Check the memory load with 'systat -vm 1'... if you are swapping a lot simply adding more memory may solve the problem. Generally speaking, adding more memory to a web server helps a lot even if you aren't swapping because web servers tend to be heavy on reading files. Today's machines are powerful enough that you can serve thousands of users off a single host, but drive technology isn't powerful enough to serve large datasets off a single drive so you need a lot of ram for cache. For example, a 20G hard drive may be able to store 20G worth of files, but it sure won't be able to keep up with a heavily loaded webserver unless you have a lot of ram for caching. Drive seek times tend to top out at 6ms, or 166 seeks per second, and without sufficient memory to cache the web pages this will result in severe limitations to the number of hits/sec the webserver can handle. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 17: 8:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.viasoft.com.cn (unknown [61.153.1.177]) by hub.freebsd.org (Postfix) with ESMTP id D296937B718 for ; Mon, 5 Mar 2001 17:08:08 -0800 (PST) (envelope-from bsddiy@21cn.com) Received: from William ([192.168.1.98]) by mail.viasoft.com.cn (8.9.3/8.9.3) with ESMTP id JAA04559; Tue, 6 Mar 2001 09:04:16 +0800 Date: Tue, 6 Mar 2001 09:13:23 +0800 From: David Xu X-Mailer: The Bat! (v1.48f) Personal Reply-To: David Xu Organization: Viasoft X-Priority: 3 (Normal) Message-ID: <522302651.20010306091323@21cn.com> To: sthaug@nethelp.no Cc: freebsd-hackers@freebsd.org Subject: Re: Missing support in FreeBSD for large file sizes? In-reply-To: <13458.983813064@verdi.nethelp.no> References: <13458.983813064@verdi.nethelp.no> 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 Hello sthaug, Tuesday, March 06, 2001, 1:24:24 AM, you wrote: snn> According to the "Maxtor picks Windows, dumps open source" article at snn> http://news.cnet.com/news/0-1003-200-5009496.html?tag=lh snn> FreeBSD "did not support large file sizes, Macintosh and newer Novell snn> file systems, or backup and management software from companies such as snn> OpenView, Tivoli and Microsoft". snn> Now I can understand what they say about missing Tivoli support - we're snn> using Tivoli backup here ourselves, and the SCO ADSM/TSM client that we snn> currently use to backup FreeBSD is passable, but nothing more. A native snn> FreeBSD client would be much preferable. snn> What I can't understand is the reference to missing support for large snn> file sizes - as far as I know, that's one of FreeBSD's strengths! Anybody snn> care to guess what they mean here? snn> Steinar Haug, Nethelp consulting, sthaug@nethelp.no snn> To Unsubscribe: send mail to majordomo@FreeBSD.org snn> with "unsubscribe freebsd-hackers" in the body of the message this is a stupid decision, let they go. AFAIK, Windows 2000 does not support dump file system to tape or other medias. I was a Windows NT system manager, I know I don't believe all backup softwares for Windows NT, simply because Windows NT system can not be fully backuped. FreeBSD can do, it's strength of Unix File System. -- Best regards, David Xu mailto:bsddiy@21cn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 17:13:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id 32D1137B718 for ; Mon, 5 Mar 2001 17:13:32 -0800 (PST) (envelope-from dphoenix@bravenet.com) Received: (qmail 17458 invoked by uid 1000); 6 Mar 2001 01:10:44 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Mar 2001 01:10:44 -0000 Date: Mon, 5 Mar 2001 17:10:44 -0800 (PST) From: Dan Phoenix To: Matt Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: systat -vmstat or iostat IO help In-Reply-To: <200103060102.f2612FH47843@earth.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 Well we use php mostly. I noticed from moving from php3 to php4 memory consumption on webservers was just incredible and had to increase ram from 256 megs to 500megs on each of webservers. Memory is fine now. [root@lotho dphoenix]# ps aux|grep httpd|wc -l 65 [root@lotho dphoenix]# top |grep -i mem Mem: 193M Active, 138M Inact, 89M Wired, 33M Cache, 61M Buf, 46M Free [root@lotho dphoenix]# uptime 5:06PM up 2 days, 23:51, 1 user, load averages: 3.29, 1.94, 1.70 [root@lotho dphoenix]# load is down now cause peak is off but systat -vm 1 showed about 3-4 seconds of 100% then 1 sec of 0 then 3-4 sec of 100% again...etc. Another factor is mysql with persistant database connections. Waiting on a request back from the mysql server could cause some IO as well i could imagine...another factor. Only thing I have never been able to figure out is how to kill persistant connections when a mysql server goes down. Let's say i drop a mysql server....all the webservers will use up all ram and swap till machine just drops using up all it's resources.....effect on freebsd is unable to free vm free_pages and machine pretty much crashes and requires a hard reboot. There is no fix for this....we have solved some of this bye setting semaphores on site to tell webservers that mysql server is down...then restart apache on those webservers to kill persistant connections to db's. But I am going offtopic....memory is not an issue. So real question is how to calculate then if the drive is doing more than say 166 seeks on disk per sec. Any great tool out there :) On Mon, 5 Mar 2001, Matt Dillon wrote: > Date: Mon, 5 Mar 2001 17:02:15 -0800 (PST) > From: Matt Dillon > To: Dan Phoenix > Cc: freebsd-hackers@FreeBSD.ORG > Subject: Re: systat -vmstat or iostat IO help > > > : > : > : > :this is a webserver ......i am trying to figure out if cpu increase or > :scsi drives is better in this situation. Right now...that is a big > :decision because there are approx 30 fbsd webservers ....not all showing > :high IO from vmstat...just the ones with the highest uptime. > :... > > Check the memory load with 'systat -vm 1'... if you are swapping a > lot simply adding more memory may solve the problem. Generally speaking, > adding more memory to a web server helps a lot even if you aren't > swapping because web servers tend to be heavy on reading files. > > Today's machines are powerful enough that you can serve thousands of > users off a single host, but drive technology isn't powerful enough to > serve large datasets off a single drive so you need a lot of ram for > cache. For example, a 20G hard drive may be able to store 20G worth > of files, but it sure won't be able to keep up with a heavily loaded > webserver unless you have a lot of ram for caching. Drive seek times > tend to top out at 6ms, or 166 seeks per second, and without sufficient > memory to cache the web pages this will result in severe limitations > to the number of hits/sec the webserver can handle. > > -Matt > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 17:25: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 89F8137B718 for ; Mon, 5 Mar 2001 17:24:58 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f261OwH48293; Mon, 5 Mar 2001 17:24:58 -0800 (PST) (envelope-from dillon) Date: Mon, 5 Mar 2001 17:24:58 -0800 (PST) From: Matt Dillon Message-Id: <200103060124.f261OwH48293@earth.backplane.com> To: Dan Phoenix Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: systat -vmstat or iostat IO help References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Well we use php mostly. I noticed from moving from php3 to php4 :memory consumption on webservers was just incredible and had to :increase ram from 256 megs to 500megs on each of webservers. :Memory is fine now. : :[root@lotho dphoenix]# ps aux|grep httpd|wc -l : 65 :[root@lotho dphoenix]# top |grep -i mem :Mem: 193M Active, 138M Inact, 89M Wired, 33M Cache, 61M Buf, 46M Free :[root@lotho dphoenix]# uptime : 5:06PM up 2 days, 23:51, 1 user, load averages: 3.29, 1.94, 1.70 :[root@lotho dphoenix]# : :load is down now cause peak is off but systat -vm 1 showed about 3-4 :seconds of 100% then 1 sec of 0 then 3-4 sec of 100% again...etc. :Another factor is mysql with persistant database connections. :Waiting on a request back from the mysql server could cause some IO You shouldn't have 46MB free. You should have maybe 10MB free. 46MB free would seem to indicate that some progrma is eating a large chunk of memory and then exiting, blowing a big piece of the disk cache away in the process. I would monitor the machine's memory and disk I/O closely to try to figure out which process or processes are responsible. :as well i could imagine...another factor. Only thing I have never been :able to figure out is how to kill persistant connections when a mysql :server goes down. Let's say i drop a mysql server....all the webservers :will use up all ram and swap till machine just drops using up all it's :resources.....effect on freebsd is unable to free vm free_pages and Dunno, but it sounds like a problem you need solve. At the very least set Apache's connection limit so Apache stops working before the machine would otherwise die. :But I am going offtopic....memory is not an issue. So real question :is how to calculate then if the drive is doing more than say 166 seeks on :disk per sec. Any great tool out there :) Memory is always an issue when you have a saturated drive unless the saturation is being caused by a lots of write I/O. For a script, probably the easiest thing to do is to pipe (the continuous) 'iostat ad0 10' output to a script and have the script pull out the tps field and do something with it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 17:54:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id E331E37B718 for ; Mon, 5 Mar 2001 17:54:09 -0800 (PST) (envelope-from dphoenix@bravenet.com) Received: (qmail 31214 invoked by uid 1000); 6 Mar 2001 01:51:22 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Mar 2001 01:51:22 -0000 Date: Mon, 5 Mar 2001 17:51:22 -0800 (PST) From: Dan Phoenix To: Matt Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: systat -vmstat or iostat IO help In-Reply-To: <200103060124.f261OwH48293@earth.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 [Mon Mar 5 11:04:01 2001] [error] (54)Connection reset by peer: getsockname [Mon Mar 5 11:04:01 2001] [error] (54)Connection reset by peer: getsockname i see that from apache error log i have seen that is past from a)either maxclients being set to low or b) freebsd maxusers set to low.... neither is the case on this machine. from /var/log/messages i see Mar 4 23:00:47 drago postfix/flush[73473]: fatal: accept connection: Software caused connection abort Mar 4 23:17:27 drago postfix/flush[74329]: fatal: accept connection: Software caused connection abort Mar 4 23:34:07 drago postfix/flush[75360]: fatal: accept connection: Software caused connection abort Mar 4 23:34:48 drago /kernel: pid 65438 (httpd), uid 506: exited on signal 10 ok httpd exiting of signal 10.....that is a bad one. only 2 things really running on webservers are apache and postfix. all postfix does on webservers is just dish mail off to mail servers, so apache is my concern. Max clients is not set to low. [root@drago dphoenix]# top |grep -i mem Mem: 128M Active, 169M Inact, 77M Wired, 22M Cache, 61M Buf, 106M Free Active: number of pages active Inact: number of pages inactive Wired: number of pages wired down, including cached file data pages Cache: number of pages used for VM-level disk caching Buf: number of pages used for BIO-level disk caching Free: number of pages free Total: total available swap usage I am trying to figure out corelation between Inactive and Free then. Inact would be unused ram right? Free would be what how much of Active is being used? So what you are saying is if there is to much free then alot of active pages are being killed for some reason...as seen in error logs etc? ....just trying to get a quick overview of what a good accessment that was...never thought of that. On Mon, 5 Mar 2001, Matt Dillon wrote: > Date: Mon, 5 Mar 2001 17:24:58 -0800 (PST) > From: Matt Dillon > To: Dan Phoenix > Cc: freebsd-hackers@FreeBSD.ORG > Subject: Re: systat -vmstat or iostat IO help > > > :Well we use php mostly. I noticed from moving from php3 to php4 > :memory consumption on webservers was just incredible and had to > :increase ram from 256 megs to 500megs on each of webservers. > :Memory is fine now. > : > :[root@lotho dphoenix]# ps aux|grep httpd|wc -l > : 65 > :[root@lotho dphoenix]# top |grep -i mem > :Mem: 193M Active, 138M Inact, 89M Wired, 33M Cache, 61M Buf, 46M Free > :[root@lotho dphoenix]# uptime > : 5:06PM up 2 days, 23:51, 1 user, load averages: 3.29, 1.94, 1.70 > :[root@lotho dphoenix]# > : > :load is down now cause peak is off but systat -vm 1 showed about 3-4 > :seconds of 100% then 1 sec of 0 then 3-4 sec of 100% again...etc. > :Another factor is mysql with persistant database connections. > :Waiting on a request back from the mysql server could cause some IO > > You shouldn't have 46MB free. You should have maybe 10MB free. 46MB free > would seem to indicate that some progrma is eating a large chunk of > memory and then exiting, blowing a big piece of the disk cache away > in the process. > > I would monitor the machine's memory and disk I/O closely to try to > figure out which process or processes are responsible. > > :as well i could imagine...another factor. Only thing I have never been > :able to figure out is how to kill persistant connections when a mysql > :server goes down. Let's say i drop a mysql server....all the webservers > :will use up all ram and swap till machine just drops using up all it's > :resources.....effect on freebsd is unable to free vm free_pages and > > Dunno, but it sounds like a problem you need solve. At the very least > set Apache's connection limit so Apache stops working before the machine > would otherwise die. > > :But I am going offtopic....memory is not an issue. So real question > :is how to calculate then if the drive is doing more than say 166 seeks on > :disk per sec. Any great tool out there :) > > Memory is always an issue when you have a saturated drive unless the > saturation is being caused by a lots of write I/O. > > For a script, probably the easiest thing to do is to pipe (the > continuous) 'iostat ad0 10' output to a script and have the script pull > out the tps field and do something with it. > > -Matt > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 18: 7:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id 421CB37B718 for ; Mon, 5 Mar 2001 18:07:36 -0800 (PST) (envelope-from dphoenix@bravenet.com) Received: (qmail 15793 invoked by uid 1000); 6 Mar 2001 02:04:49 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Mar 2001 02:04:49 -0000 Date: Mon, 5 Mar 2001 18:04:49 -0800 (PST) From: Dan Phoenix To: Matt Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: systat -vmstat or iostat IO help 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 guess that machien was a bad example as it is doing well right now. I will have to wait till peak time again to monitor it. On Mon, 5 Mar 2001, Dan Phoenix wrote: > Date: Mon, 5 Mar 2001 17:51:22 -0800 (PST) > From: Dan Phoenix > To: Matt Dillon > Cc: freebsd-hackers@FreeBSD.ORG > Subject: Re: systat -vmstat or iostat IO help > > > > [Mon Mar 5 11:04:01 2001] [error] (54)Connection reset by > peer: getsockname > [Mon Mar 5 11:04:01 2001] [error] (54)Connection reset by > peer: getsockname > > i see that from apache error log > > i have seen that is past from a)either maxclients being set to low or > b) freebsd maxusers set to low.... > > neither is the case on this machine. > > > > from /var/log/messages i see > > > Mar 4 23:00:47 drago postfix/flush[73473]: fatal: accept > connection: Software caused connection abort > Mar 4 23:17:27 drago postfix/flush[74329]: fatal: accept > connection: Software caused connection abort > Mar 4 23:34:07 drago postfix/flush[75360]: fatal: accept > connection: Software caused connection abort > Mar 4 23:34:48 drago /kernel: pid 65438 (httpd), uid 506: exited on > signal 10 > > > ok httpd exiting of signal 10.....that is a bad one. > > > only 2 things really running on webservers are apache and postfix. > all postfix does on webservers is just dish mail off to mail servers, > so apache is my concern. Max clients is not set to low. > > > [root@drago dphoenix]# top |grep -i mem > Mem: 128M Active, 169M Inact, 77M Wired, 22M Cache, 61M Buf, 106M Free > > Active: > number of pages active > > Inact: number of pages inactive > > Wired: number of pages wired down, including cached file > data pages > Cache: number of pages used for VM-level disk caching > > Buf: number of pages used for BIO-level disk caching > > Free: number of pages free > > Total: total available swap usage > > > I am trying to figure out corelation between Inactive and Free then. > Inact would be unused ram right? > Free would be what how much of Active is being used? So what you are > saying is if there is to much free then alot of active pages are being > killed for some reason...as seen in error logs etc? ....just trying to get > a quick overview of what a good accessment that was...never thought of > that. > > > On Mon, 5 Mar 2001, Matt Dillon wrote: > > > Date: Mon, 5 Mar 2001 17:24:58 -0800 (PST) > > From: Matt Dillon > > To: Dan Phoenix > > Cc: freebsd-hackers@FreeBSD.ORG > > Subject: Re: systat -vmstat or iostat IO help > > > > > > :Well we use php mostly. I noticed from moving from php3 to php4 > > :memory consumption on webservers was just incredible and had to > > :increase ram from 256 megs to 500megs on each of webservers. > > :Memory is fine now. > > : > > :[root@lotho dphoenix]# ps aux|grep httpd|wc -l > > : 65 > > :[root@lotho dphoenix]# top |grep -i mem > > :Mem: 193M Active, 138M Inact, 89M Wired, 33M Cache, 61M Buf, 46M Free > > :[root@lotho dphoenix]# uptime > > : 5:06PM up 2 days, 23:51, 1 user, load averages: 3.29, 1.94, 1.70 > > :[root@lotho dphoenix]# > > : > > :load is down now cause peak is off but systat -vm 1 showed about 3-4 > > :seconds of 100% then 1 sec of 0 then 3-4 sec of 100% again...etc. > > :Another factor is mysql with persistant database connections. > > :Waiting on a request back from the mysql server could cause some IO > > > > You shouldn't have 46MB free. You should have maybe 10MB free. 46MB free > > would seem to indicate that some progrma is eating a large chunk of > > memory and then exiting, blowing a big piece of the disk cache away > > in the process. > > > > I would monitor the machine's memory and disk I/O closely to try to > > figure out which process or processes are responsible. > > > > :as well i could imagine...another factor. Only thing I have never been > > :able to figure out is how to kill persistant connections when a mysql > > :server goes down. Let's say i drop a mysql server....all the webservers > > :will use up all ram and swap till machine just drops using up all it's > > :resources.....effect on freebsd is unable to free vm free_pages and > > > > Dunno, but it sounds like a problem you need solve. At the very least > > set Apache's connection limit so Apache stops working before the machine > > would otherwise die. > > > > :But I am going offtopic....memory is not an issue. So real question > > :is how to calculate then if the drive is doing more than say 166 seeks on > > :disk per sec. Any great tool out there :) > > > > Memory is always an issue when you have a saturated drive unless the > > saturation is being caused by a lots of write I/O. > > > > For a script, probably the easiest thing to do is to pipe (the > > continuous) 'iostat ad0 10' output to a script and have the script pull > > out the tps field and do something with it. > > > > -Matt > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 18: 8:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 7722F37B71A for ; Mon, 5 Mar 2001 18:08:25 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2628PT49635; Mon, 5 Mar 2001 18:08:25 -0800 (PST) (envelope-from dillon) Date: Mon, 5 Mar 2001 18:08:25 -0800 (PST) From: Matt Dillon Message-Id: <200103060208.f2628PT49635@earth.backplane.com> To: Dan Phoenix Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: systat -vmstat or iostat IO help References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I am trying to figure out corelation between Inactive and Free then. :Inact would be unused ram right? :Free would be what how much of Active is being used? So what you are :saying is if there is to much free then alot of active pages are being :killed for some reason...as seen in error logs etc? ....just trying to get :a quick overview of what a good accessment that was...never thought of :that. 'free' (from systat -vm or top) is all that matters in your case. Active/Inactive/Cache are best simply added together. Their individual values will depend heavily on the load on the machine because the VM system doesn't bother to keep things in their proper queues if the memory load is low. Normally when a machine is operating you see the 'free' value drop steadily until it hits vm.v_free_min, which is typically 2-4 MB. The VM system then frees up inactive & cache memory up to vm.v_free_target, which is typically around 10MB. Thus the 'free' value will recover to around 10MB, then drop and recover again, add nauseum. Once free memory drops you should never see it get big again unless you run a program which allocates a whole bunch of memory (e.g. 40MB) and then exits. The allocated memory is freed on program exit and may temporarily bump the 'free' value up, but it should steadily drop again and restabilize at 4-10MB or so. Alternatively it is possible that a whole bunch of programs may be started at once and then all exit at around the same time, resulting in the same effect. If you regularly see a large free value (aka 40MB) plus lots of disk activity, something weird may be going on that you need to track down and figure out. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 5 18:32:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 4F53637B718 for ; Mon, 5 Mar 2001 18:32:40 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id DAA05139; Tue, 6 Mar 2001 03:32:37 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Dan Phoenix Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: systat -vmstat or iostat IO help References: From: Dag-Erling Smorgrav Date: 06 Mar 2001 03:32:36 +0100 In-Reply-To: Dan Phoenix's message of "Mon, 5 Mar 2001 14:25:40 -0800 (PST)" Message-ID: Lines: 25 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Phoenix writes: > systat -iostat > > /0 /10 /20 /30 /40 /50 /60 /70 /80 /90 /100 > ad0 MB/s > tps|XXXXXXX > > [...] > systat -vmstat > > Disks ad0 acd0 fd0 md0 89 ofod intrn > KB/t 4.35 0.00 0.00 0.00 85 %slo-z 61952 buf > tps 13 0 0 0 104 tfree 42 dirtybuf > MB/s 0.05 0.00 0.00 0.00 36095 desiredvnodes > % busy 100 0 0 0 58692 numvnodes > 43991 freevnodes > > well vmstat showing 100% busy and iostat showing 10% busy...... No, -vmstat and -iostat are showing 13 and 12 tps (transactions per second), respectively. -iostat doesn't show a "busy percentage". DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 0:50:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 2DD7737B71A for ; Tue, 6 Mar 2001 00:50:52 -0800 (PST) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01K0VEU3M9AC000HIQ@research.kpn.com> for freebsd-hackers@FreeBSD.ORG; Tue, 6 Mar 2001 09:50:50 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Tue, 06 Mar 2001 09:50:50 +0100 Content-return: allowed Date: Tue, 06 Mar 2001 09:50:45 +0100 From: "Koster, K.J." Subject: RE: Missing support in FreeBSD for large file sizes? To: freebsd-hackers@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7C7A@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear All, > > http://news.cnet.com/news/0-1003-200-5009496.html?tag=lh > Microsoft adjusted its licensing terms for the Maxtor system, Wilkins noted. Unlike general-purpose servers, a Maxtor machine doesn't require that customers pay for client access licenses--the fees often required for computers that use the server. "That's the first time Microsoft has done this," Wilkins said. This is a victory for the Open Source community, not a defeat. Microsoft is willing to bleed for real big customers, because they realize that Maxtor had a choice. At some point in the future Microsoft is going to be willing to bleed for little customers also. 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 Mar 6 1:25:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailc.telia.com (mailc.telia.com [194.22.190.4]) by hub.freebsd.org (Postfix) with ESMTP id 3E0F737B718 for ; Tue, 6 Mar 2001 01:25:43 -0800 (PST) (envelope-from watchman@ludd.luth.se) Received: from d1o906.telia.com (d1o906.telia.com [195.252.36.241]) by mailc.telia.com (8.11.2/8.11.0) with ESMTP id f269PfT13589 for ; Tue, 6 Mar 2001 10:25:42 +0100 (CET) Received: from ludd.luth.se (h12n1fls20o906.telia.com [213.64.92.12]) by d1o906.telia.com (8.8.8/8.8.8) with ESMTP id KAA26892 for ; Tue, 6 Mar 2001 10:25:40 +0100 (CET) Message-ID: <3AA4AD13.DA48CFDD@ludd.luth.se> Date: Tue, 06 Mar 2001 10:25:39 +0100 From: Joachim =?iso-8859-1?Q?Str=F6mbergson?= Organization: Acne X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en-US MIME-Version: 1.0 Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Missing support in FreeBSD for large file sizes? References: <59063B5B4D98D311BC0D0001FA7E4522026D7C7A@l04.research.kpn.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Aloha! Still, wouldn't it be prudent if someone from the project talked to Maxtor and got some feedback on this? They obviously (or should we assume conspiracy?) had some real technical issues with FreeBSD, and also had problems dealing with them properly. Clarification on this should (could) be quite good feedback. -- Cheers! Joachim - Alltid i harmonisk svängning --- FairLight ------ FairLight ------ FairLight ------ FairLight --- Joachim Strömbergson ASIC SoC designer, nice to CUTE animals Phone: +46(0)31 - 27 98 47 Web: http://www.ludd.luth.se/~watchman --------------- Spamfodder: regeringen@regeringen.se --------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 1:27:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 46D5737B718 for ; Tue, 6 Mar 2001 01:27:12 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f269QMH53100; Tue, 6 Mar 2001 01:26:22 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: watchman@ludd.luth.se Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Missing support in FreeBSD for large file sizes? In-Reply-To: <3AA4AD13.DA48CFDD@ludd.luth.se> References: <59063B5B4D98D311BC0D0001FA7E4522026D7C7A@l04.research.kpn.com> <3AA4AD13.DA48CFDD@ludd.luth.se> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010306012622J.jkh@osd.bsdi.com> Date: Tue, 06 Mar 2001 01:26:22 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That could be, assuming that we had any idea just who inside of Maxstor to discuss it with. Do you have any names and email addresses? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 4: 7:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhost.i-next.net (i-next.net [202.61.64.11]) by hub.freebsd.org (Postfix) with ESMTP id 1CAE237B719 for ; Tue, 6 Mar 2001 04:07:24 -0800 (PST) (envelope-from webby@bsdi.dhs.org) Received: from martian (unknown [203.176.75.30]) by mailhost.i-next.net (Postfix) with SMTP id 3C773206B4 for ; Tue, 6 Mar 2001 20:07:19 +0800 (PHT) Message-ID: <003201c0a635$df28bb80$1e4bb0cb@martian> From: "jett tayer" To: Subject: anybody pls help im a newbie Date: Tue, 6 Mar 2001 20:06:27 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002F_01C0A678.ED39AC00" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_002F_01C0A678.ED39AC00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable i want to protect my freebsd box from the outside. anyone who can help? any sample configs about=20 ipfw or ipf. which do u guys prefer of the two? my box is running: named apache qmail popper pls help.. thanks jett ------=_NextPart_000_002F_01C0A678.ED39AC00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
i want to protect my freebsd box from = the=20 outside.
anyone who can help? any sample configs = about=20
ipfw or ipf. which do u guys prefer of = the=20 two?
 
my box is running:
named
apache
qmail
popper
 
pls help..
 
thanks
jett
 
 
------=_NextPart_000_002F_01C0A678.ED39AC00-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 4:46:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 643F437B719 for ; Tue, 6 Mar 2001 04:46:38 -0800 (PST) (envelope-from msinz@wgate.com) Received: from sinz.eng.tvol.net ([10.32.2.99]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 152C8XPY; Tue, 6 Mar 2001 07:46:50 -0500 Received: from wgate.com (localhost [127.0.0.1]) by sinz.eng.tvol.net (8.11.1/8.11.1) with ESMTP id f26Ckbk63267 for ; Tue, 6 Mar 2001 07:46:37 -0500 (EST) (envelope-from msinz@wgate.com) Message-ID: <3AA4DC2D.F72208C7@wgate.com> Date: Tue, 06 Mar 2001 07:46:37 -0500 From: Michael Sinz Organization: WorldGate Communications Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: Machines are getting too damn fast References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > Subject: Re: Machines are getting too damn fast > > :throughput. For example, on the PIII-850 (116MHz FSB and SDRAM, its > :overclocked) here on my desk with 256KB L2 cache: > : > :dd if=/dev/zero of=/dev/null bs=512k count=4000 > :4000+0 records in > :4000+0 records out > :2097152000 bytes transferred in 8.229456 secs (254834825 bytes/sec) > : > :dd if=/dev/zero of=/dev/null bs=128k count=16000 > :16000+0 records in > :16000+0 records out > :2097152000 bytes transferred in 1.204001 secs (1741819224 bytes/sec) > : > :Now THAT is a significant difference. :-) > > Interesting. I get very different results with the 1.3 GHz P4. The > best I seem to get is 1.4 GBytes/sec. I'm not sure what the L2 cache > is on the box, but it's definitely a consumer model. > > dd if=/dev/zero of=/dev/null bs=512k count=4000 > 2097152000 bytes transferred in 2.363903 secs (887156520 bytes/sec) > > dd if=/dev/zero of=/dev/null bs=128k count=16000 > 2097152000 bytes transferred in 1.471046 secs (1425619621 bytes/sec) > > If I use lower block sizes the syscall overhead blows up the > performance (it gets lower rather then higher). So I figure I don't > have as much L2 as on your system. The P4 has other issues when you don't do straight line code. Any branch mis-predictions cost a minimum of 20 cycles due to the pipeline plus whatever cache/fetch/decode hits you may get on the actual target. This may be why you get lower values than a PIII or Athelon. (Both have significantly lower penalty for branch mis-prediction) -- Michael Sinz ---- Worldgate Communications ---- msinz@wgate.com A master's secrets are only as good as the master's ability to explain them to others. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 5:39:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailf.telia.com (mailf.telia.com [194.22.194.25]) by hub.freebsd.org (Postfix) with ESMTP id B34EE37B723 for ; Tue, 6 Mar 2001 05:39:45 -0800 (PST) (envelope-from watchman@ludd.luth.se) Received: from d1o906.telia.com (d1o906.telia.com [195.252.36.241]) by mailf.telia.com (8.9.3/8.9.3) with ESMTP id OAA15077; Tue, 6 Mar 2001 14:39:42 +0100 (CET) Received: from ludd.luth.se (h12n1fls20o906.telia.com [213.64.92.12]) by d1o906.telia.com (8.8.8/8.8.8) with ESMTP id OAA13736; Tue, 6 Mar 2001 14:39:40 +0100 (CET) Message-ID: <3AA4E89A.4631FB3E@ludd.luth.se> Date: Tue, 06 Mar 2001 14:39:38 +0100 From: Joachim =?iso-8859-1?Q?Str=F6mbergson?= Organization: Acne X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en-US MIME-Version: 1.0 To: Jordan Hubbard Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Missing support in FreeBSD for large file sizes? References: <59063B5B4D98D311BC0D0001FA7E4522026D7C7A@l04.research.kpn.com> <3AA4AD13.DA48CFDD@ludd.luth.se> <20010306012622J.jkh@osd.bsdi.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hola! Jordan Hubbard wrote: > That could be, assuming that we had any idea just who inside of > Maxstor to discuss it with. Do you have any names and email > addresses? Not personally, but taken from the article about this issue, one person that obviously knows about this is Steve Wilkins, Maxtor's product marketing director. He should be able to reach through the Maxtor switchboard. Contact information from the Maxtor website: ( http://www.maxtor.com/Maxtorhome.htm?http&&&www.maxtor.com/contactUs/default.htm ) Maxtor Corporation 510 Cottonwood Drive Milpitas, CA 95035 USA Telephone: (408)432-1700 Fax: (408)432-4510 There is a press release about the MS deal (which meant kicking out FreeBSD): http://www.maxtor.com/press/2001/nr200103052.html In the press release a few other names appear: * Victor Jipson, president of the Network Systems Group at Maxtor * Mike Cannon, president and CEO of Maxtor. These should also (in some way) be able to reach through the main switchboard (or door for those in the area). The product itself, MaxAttach, have some contact information for technical support and so on: http://www.maxtor.com/Maxtorhome.htm?http&&&www.maxtor.com/contactUs/technicalSupport_MaxAttach.htm Also, I went through their Careers pages to see if I could find any names in connection with job opportunities related to OS development in the NAS-products. Unfortunately, all contact information are directed to the HR department. One (possibly) interesting thing to note is that they have lots of job opportunities for SW development deirected at MS specific things. I'm not sure what the conclusion might be. Either (a) they are changing direction and need a whole new staff. Or, (b) they have been working towards MS-centric systems for a long time. (Or (c) they need people, and these are good buzzwords to ask about). Anyway, hopefully they are positive in letting us know a bit more about why and what concerning what they perceived as problematic about FreeBSD. Was it only technical or was it lack of support? I'm also curious to in what ways they tried to get help with their problems. Personally, I'm not even close to be in Milpitas, and don't see myself as a proper representative for FreeBSD, so I feel I'm not the one to actually make the contact with Maxtor. -- Cheers! Joachim - Alltid i harmonisk svängning --- FairLight ------ FairLight ------ FairLight ------ FairLight --- Joachim Strömbergson ASIC SoC designer, nice to CUTE animals Phone: +46(0)31 - 27 98 47 Web: http://www.ludd.luth.se/~watchman --------------- Spamfodder: regeringen@regeringen.se --------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 6:12:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 6C4DE37B718 for ; Tue, 6 Mar 2001 06:12:41 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.11.1/8.11.1) id f26EBSV08016 for hackers@freebsd.org; Tue, 6 Mar 2001 09:11:28 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200103061411.f26EBSV08016@hda.hda.com> Subject: Log file analysis To: hackers@freebsd.org Date: Tue, 6 Mar 2001 09:11:27 -0500 (EST) 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 have long log files from multi-threaded multi-program simulations that output this sort of thing: > BUS:16:15:35.212525 vme:082a4000 \ irqn: opening shared memory object /var/tmp/vmedir/irqn.bus > BUS:16:15:35.221792 vme:082a4000 \ irqn: Master opening request FIFO blocking. > BUS:16:15:37.193684 foo:082a4000 \ irqn: opening /var/tmp/vmedir/irqn.bus > BUS:16:15:37.194125 foo:082a4000 \ irqn: Opening /var/tmp/vmedir/irqn.request write-only... > BUS:16:15:37.194318 vme:082a4000 \ irqn: blocking for request > BUS:16:15:37.194524 foo:082a4000 \ irqn: creating reply fifo /var/tmp/vmedir/irqn74193.74181.reply > BUS:16:15:37.194771 foo:082a4000 \ irqn: writing request #0 "Attach" (with handshake, sem 0x830f5e0 pSem 0xbfbfe3dc) to request FIFO. > BUS:16:15:37.195009 vme:082a4000 \ irqn: received request #0 (with handshake) "Attach" from client foo I'd like to be able to graphically browse these logs so that unusual sequences jump out. There are time stamps, programs, thread ids, etc, in the fields and I want to plot them along the time axis with different colors, different programs at different heights, etc. I did a little searching for log file analysis, etc, but only see web site oriented utilities. I'll start rolling my own using a tk canvas, but does anyone know of a good starting point tool? Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 7: 7:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id 2225237B71A; Tue, 6 Mar 2001 07:07:18 -0800 (PST) (envelope-from so@server.i-clue.de) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id RAA10529; Tue, 6 Mar 2001 17:13:26 +0100 Message-ID: <3AA4FD63.7870ED63@i-clue.de> Date: Tue, 06 Mar 2001 16:08:19 +0100 From: Christoph Sold Reply-To: so@server.i-clue.de X-Mailer: Mozilla 4.75 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 Followup-To: questions@freebsd.org To: jett tayer , questions@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Re: anybody pls help im a newbie References: <003201c0a635$df28bb80$1e4bb0cb@martian> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Moved from -hackers to -questions, Followup is set.] > jett tayer schrieb: > > i want to protect my freebsd box from the outside. > anyone who can help? any sample configs about > ipfw or ipf. which do u guys prefer of the two? > > my box is running: > named > apache > qmail > popper You may use /stand/sysinstall during installation to enable a firewall with open, medium, or secure policy. If you already installed FreeBSD, have a look at /etc/defaults/rc.conf. It lists the following settings: ------ firewall_enable="NO" # Set to YES to enable firewall functionality firewall_script="/etc/rc.firewall" # Which script to run to set up the firewall firewall_type="UNKNOWN" # Firewall type (see /etc/rc.firewall) firewall_quiet="NO" # Set to YES to suppress rule display firewall_logging="NO" # Set to YES to enable events logging firewall_flags="" # Flags passed to ipfw when type is a file ------ the above mentioned rc.firewall script lists ------ ############ # Define the firewall type in /etc/rc.conf. Valid values are: # open - will allow anyone in # client - will try to protect just this machine # simple - will try to protect a whole network # closed - totally disables IP services except via lo0 interface # UNKNOWN - disables the loading of firewall rules. # filename - will load the rules in the given filename (full path required) # # For ``client'' and ``simple'' the entries below should be customized # appropriately. ############ # # If you don't know enough about packet filtering, we suggest that you # take time to read this book: # # Building Internet Firewalls # Brent Chapman and Elizabeth Zwicky # # O'Reilly & Associates, Inc # ISBN 1-56592-124-0 # http://www.ora.com/ ------ client and simple are default firewalls. For everything else you'll need to read the above mentioned book (~850p.) or to hire an expert, cause there is no such thing than an universal firewall. HTH -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 7:57:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 13A8537B718 for ; Tue, 6 Mar 2001 07:57:19 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA05629; Tue, 6 Mar 2001 10:57:17 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f26Fulc19217; Tue, 6 Mar 2001 10:56:47 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15013.2238.953211.516979@grasshopper.cs.duke.edu> Date: Tue, 6 Mar 2001 10:56:46 -0500 (EST) To: Matt Dillon Cc: Subject: Re: Machines are getting too damn fast In-Reply-To: <200103060013.f260DHY46910@earth.backplane.com> References: <200103060013.f260DHY46910@earth.backplane.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon writes: > > I modified my original C program again, this time to simply read > the data from memory given a block size in kilobytes as an argument. > I had to throw in a little __asm to do it right, but here are my results. > It shows about 3.2 GBytes/sec from the L2 (well, insofar as my > 3-instruction loop goes), and about 1.4 GBytes/sec from main memory. > > > NOTE: cc x.c -O2 -o x > > ./x 4 > 3124.96 MBytes/sec (read) <...> > ./x 1024 > 1397.90 MBytes/sec (read) > > In contrast I get 1052.50 MBytes/sec on the Dell 2400 from the L2, > and 444 MBytes/sec from main memory. > FWIW: 1.2GHz Athlon, VIA Apollo KT133 chipset, Asus A7V motherboard, (PC133 ECC Registered Dimms) ./x 4 2393.70 MBytes/sec (read) ./x 8 2398.19 MBytes/sec (read) <...> ./x 1024 627.32 MBytes/sec (read) And a Dual 933MHz PIII SuperMicro 370DER Serverworks HE-SL Chipset (2-way interleaved PC133 ECC Registered DIMMS) ./x 4 1853.54 MBytes/sec (read) ./x 1024 526.19 MBytes/sec (read) There's something diabolic about your previous bw test, though. I think it only hits one bank of interleaved ram. On the 370DER it gets only 167MB/sec. Every other bw test I've run on the box shows copy perf at around 260MB/sec (Hbench, lmbench). I see the same problem on a PE4400 (also 2-way interleaved); it shows copy perf as 111MB/sec. Every other test has it at 230MB/sec. The Athlon copies at 174MB/sec, which is right about what lmbench, hbench, etc, and your test show. How's your P4 for floating point? Is real-life perf as good as the specbench numbers would indicate, or do you need a better compiler than GCC to get any benefit from it? My wife is a statistician, and she runs some really fp intensive workloads. This Athlon is faster than the Serverworks box and (barely) faster than a year-old Alpha UP1000 for her code. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 8: 2:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id 5969737B718 for ; Tue, 6 Mar 2001 08:02:28 -0800 (PST) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f26G2Qp01291 for ; Tue, 6 Mar 2001 10:02:26 -0600 (CST) Message-Id: <200103061602.f26G2Qp01291@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: freebsd-hackers@freebsd.org Subject: Re: Machines are getting too damn fast In-reply-to: Your message of "Tue, 06 Mar 2001 10:56:46 EST." <15013.2238.953211.516979@grasshopper.cs.duke.edu> Date: Tue, 06 Mar 2001 10:02:26 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <15013.2238.953211.516979@grasshopper.cs.duke.edu>, Andrew Gallatin writes: >FWIW: 1.2GHz Athlon, VIA Apollo KT133 chipset, Asus A7V motherboard, >(PC133 ECC Registered Dimms) Note that the KT does *NOT* support ECC. A few places have claimed it does, but the VIA chipset spec says it doesn't. The KV or KX does (I forget the model #), but the KT is secretly doing no error correcting at all. I got burned on this with an ABit VP6, which proclaims loudly that it supports ECC, but doesn't actually *do* any. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 9:41:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 302B337B718 for ; Tue, 6 Mar 2001 09:41:46 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f26Hf3N55355; Tue, 6 Mar 2001 09:41:03 -0800 (PST) (envelope-from dillon) Date: Tue, 6 Mar 2001 09:41:03 -0800 (PST) From: Matt Dillon Message-Id: <200103061741.f26Hf3N55355@earth.backplane.com> To: Andrew Gallatin Cc: Subject: Re: Machines are getting too damn fast References: <200103060013.f260DHY46910@earth.backplane.com> <15013.2238.953211.516979@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :How's your P4 for floating point? Is real-life perf as good as the :specbench numbers would indicate, or do you need a better compiler :than GCC to get any benefit from it? My wife is a statistician, and :she runs some really fp intensive workloads. This Athlon is faster :than the Serverworks box and (barely) faster than a year-old Alpha :UP1000 for her code. : :Drew : :------------------------------------------------------------------------------ :Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin My understanding is that Intel focused on FP performance in the P4, and that it is very, very good at it. I dunno how to test it though. GCC generally does not produce very good code, but I would expect that it would get reasonably close in regards to FP because Intel's FP instruction set is a good fit with it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 9:57:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bdr-xcon.matchlogic.com (mail.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id D45D537B719 for ; Tue, 6 Mar 2001 09:57:35 -0800 (PST) (envelope-from crandall@matchlogic.com) Received: by mail.matchlogic.com with Internet Mail Service (5.5.2653.19) id ; Tue, 6 Mar 2001 10:56:50 -0700 Message-ID: <5FE9B713CCCDD311A03400508B8B30130828E87D@bdr-xcln.is.matchlogic.com> From: Charles Randall To: 'Matt Dillon' , Andrew Gallatin Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: Machines are getting too damn fast Date: Tue, 6 Mar 2001 10:56:49 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Matt Dillon [mailto:dillon@earth.backplane.com] > My understanding is that Intel focused on FP performance in the P4, > and that it is very, very good at it. I dunno how to test it though. > > GCC generally does not produce very good code, but I would expect that > it would get reasonably close in regards to FP because Intel's FP > instruction set is a good fit with it. Which begs the question I've tried to ask a number of times in different forums. Who's working on P4 optimizations and code generation for the P4? Sure, i386 code will run but the benchmarks seem to indicate that peak performance is heavily dependent on a good optimizing compiler. A query to the gcc mailing list returned no responses. Charles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 10: 3:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (adam042-060.resnet.wisc.edu [146.151.42.60]) by hub.freebsd.org (Postfix) with ESMTP id B51BE37B719 for ; Tue, 6 Mar 2001 10:03:47 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 11803 invoked by uid 1000); 6 Mar 2001 18:03:47 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Mar 2001 18:03:47 -0000 Date: Tue, 6 Mar 2001 12:03:46 -0600 (CST) From: Mike Silbersack To: Matt Dillon Cc: Andrew Gallatin , Subject: Re: Machines are getting too damn fast In-Reply-To: <200103061741.f26Hf3N55355@earth.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, 6 Mar 2001, Matt Dillon wrote: > My understanding is that Intel focused on FP performance in the P4, > and that it is very, very good at it. I dunno how to test it though. From the benchmarks tom's hardware / others did, I got the impression that SSE2 performance is awesome, but x87 FPU operations aren't really improved, so the Athlon still has the advantage there. > GCC generally does not produce very good code, but I would expect that > it would get reasonably close in regards to FP because Intel's FP > instruction set is a good fit with it. > > -Matt I'm quite confused about Intel's strategy wrt that compiler. Every time someone does a benchmark showing Intel's newest processor getting beat at something, they send code compiled with it to the benchmarker. However, they haven't even attempted to make it a popular compiler. Everything I've seen/heard indicates that msvc and gcc are all that gets really used on x86. My only guess is that part of the company wants to have everyone use it to get optimal performance out of intel processors, while the other half wants people to be forced to buy faster processors. This would explain why it's still sold, but in such a way that nobody will really buy it. (The reason I mention this is because someone was talking about trying to compile the kernel with sun's CC. Maybe rigging intel's compiler to do so would be fruitful.) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 10: 8:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 9A8C337B71A for ; Tue, 6 Mar 2001 10:08:29 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA23683; Tue, 6 Mar 2001 11:07:55 -0700 (MST) (envelope-from ken) Date: Tue, 6 Mar 2001 11:07:55 -0700 From: "Kenneth D. Merry" To: Andrew Gallatin Cc: Matt Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: Machines are getting too damn fast Message-ID: <20010306110754.A23400@panzer.kdm.org> References: <200103060013.f260DHY46910@earth.backplane.com> <15013.2238.953211.516979@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <15013.2238.953211.516979@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Tue, Mar 06, 2001 at 10:56:46AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 06, 2001 at 10:56:46 -0500, Andrew Gallatin wrote: > Matt Dillon writes: > > > > I modified my original C program again, this time to simply read > > the data from memory given a block size in kilobytes as an argument. > > I had to throw in a little __asm to do it right, but here are my results. > > It shows about 3.2 GBytes/sec from the L2 (well, insofar as my > > 3-instruction loop goes), and about 1.4 GBytes/sec from main memory. > > > > > > NOTE: cc x.c -O2 -o x > > > > ./x 4 > > 3124.96 MBytes/sec (read) > <...> > > ./x 1024 > > 1397.90 MBytes/sec (read) > > > > In contrast I get 1052.50 MBytes/sec on the Dell 2400 from the L2, > > and 444 MBytes/sec from main memory. > > > > FWIW: 1.2GHz Athlon, VIA Apollo KT133 chipset, Asus A7V motherboard, > (PC133 ECC Registered Dimms) > > ./x 4 > 2393.70 MBytes/sec (read) > ./x 8 > 2398.19 MBytes/sec (read) > <...> > ./x 1024 > 627.32 MBytes/sec (read) > > > And a Dual 933MHz PIII SuperMicro 370DER Serverworks HE-SL Chipset > (2-way interleaved PC133 ECC Registered DIMMS) > > ./x 4 > 1853.54 MBytes/sec (read) > ./x 1024 > 526.19 MBytes/sec (read) Dell Precision 420 (i840 chipset) with a single PIII 800 and probably one RIMM, unknown speed: {rivendell:/usr/home/ken/src:76:0} ./memspeed 4 1049.51 MBytes/sec (read) {rivendell:/usr/home/ken/src:77:0} ./memspeed 1024 378.41 MBytes/sec (read) The above machine may not have been completely idle, it seems a little slow. Dual 1GHz PIII SuperMicro 370DE6 Serverworks HE-SL chipset, 4x256MB PC133 ECC Registered DIMMs: {gondolin:/usr/home/ken/src:51:0} ./memspeed 4 1985.95 MBytes/sec (read) {gondolin:/usr/home/ken/src:52:0} ./memspeed 1024 516.62 MBytes/sec (read) > There's something diabolic about your previous bw test, though. I > think it only hits one bank of interleaved ram. On the 370DER it gets > only 167MB/sec. Every other bw test I've run on the box shows copy > perf at around 260MB/sec (Hbench, lmbench). I see the same problem on > a PE4400 (also 2-way interleaved); it shows copy perf as 111MB/sec. > Every other test has it at 230MB/sec. The previous test showed about 270MB/sec on my Serverworks box: {gondolin:/usr/home/ken/src:53:0} ./memory_speed 269.23 MBytes/sec (copy) 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 Tue Mar 6 10:44:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id D487C37B718 for ; Tue, 6 Mar 2001 10:44:10 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f26Ii9E56479; Tue, 6 Mar 2001 10:44:09 -0800 (PST) (envelope-from dillon) Date: Tue, 6 Mar 2001 10:44:09 -0800 (PST) From: Matt Dillon Message-Id: <200103061844.f26Ii9E56479@earth.backplane.com> To: Charles Randall Cc: Andrew Gallatin , freebsd-hackers@FreeBSD.ORG Subject: Re: RE: Machines are getting too damn fast References: <5FE9B713CCCDD311A03400508B8B30130828E87D@bdr-xcln.is.matchlogic.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Which begs the question I've tried to ask a number of times in different :forums. Who's working on P4 optimizations and code generation for the P4? I'd be happy if GCC -O2 just worked without introducing bugs. I want to be able to compile the kernel with it again. -Matt :Sure, i386 code will run but the benchmarks seem to indicate that peak :performance is heavily dependent on a good optimizing compiler. : :A query to the gcc mailing list returned no responses. : :Charles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 12:15:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 6FC1937B719 for ; Tue, 6 Mar 2001 12:15:17 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f26KEPH72100; Tue, 6 Mar 2001 12:14:25 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: webby@bsdi.dhs.org Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: anybody pls help im a newbie In-Reply-To: <003201c0a635$df28bb80$1e4bb0cb@martian> References: <003201c0a635$df28bb80$1e4bb0cb@martian> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010306121425X.jkh@osd.bsdi.com> Date: Tue, 06 Mar 2001 12:14:25 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 10 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1. Please send messages like this to questions, not to hackers. The hackers mailing list is for development discussions, not Q&A. Thanks. 2. See http://www.daemonnews.org/200103/firewall.html and similar articles on the net for this kind of information. There are many beginner's articles on firewalls and FreeBSD if you just do a little altavista (or your favorite search engine) searching. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 12:41:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.targetnet.com (smtp.targetnet.com [205.150.0.125]) by hub.freebsd.org (Postfix) with ESMTP id AF4F837B718 for ; Tue, 6 Mar 2001 12:41:20 -0800 (PST) (envelope-from bgale@targetnet.com) Received: from gw-101.tor1.targetnet.com ([149.99.36.66] helo=wrk106) by smtp.targetnet.com with smtp (Exim 3.16 #1) id 14aOFN-000K4p-00; Tue, 06 Mar 2001 15:39:53 -0500 From: "Brandon Gale" To: "Kenneth D. Merry" , "Andrew Gallatin" Cc: "Matt Dillon" , Subject: RE: Machines are getting too damn fast Date: Tue, 6 Mar 2001 15:40:25 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <20010306110754.A23400@panzer.kdm.org> Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This explained in great detail exactly why people are seeing the performance they are from the P4 etc. The author knows his stuff. http://www.emulators.com/pentium4.htm Brandon :-----Original Message----- :From: owner-freebsd-hackers@FreeBSD.ORG :[mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Kenneth D. Merry :Sent: Tuesday, March 06, 2001 1:08 PM :To: Andrew Gallatin :Cc: Matt Dillon; freebsd-hackers@FreeBSD.ORG :Subject: Re: Machines are getting too damn fast : : :On Tue, Mar 06, 2001 at 10:56:46 -0500, Andrew Gallatin wrote: :> Matt Dillon writes: :> > :> > I modified my original C program again, this time to simply read :> > the data from memory given a block size in kilobytes as :an argument. :> > I had to throw in a little __asm to do it right, but here :are my results. :> > It shows about 3.2 GBytes/sec from the L2 (well, insofar as my :> > 3-instruction loop goes), and about 1.4 GBytes/sec from :main memory. :> > :> > :> > NOTE: cc x.c -O2 -o x :> > :> > ./x 4 :> > 3124.96 MBytes/sec (read) :> <...> :> > ./x 1024 :> > 1397.90 MBytes/sec (read) :> > :> > In contrast I get 1052.50 MBytes/sec on the Dell 2400 from the L2, :> > and 444 MBytes/sec from main memory. :> > :> :> FWIW: 1.2GHz Athlon, VIA Apollo KT133 chipset, Asus A7V motherboard, :> (PC133 ECC Registered Dimms) :> :> ./x 4 :> 2393.70 MBytes/sec (read) :> ./x 8 :> 2398.19 MBytes/sec (read) :> <...> :> ./x 1024 :> 627.32 MBytes/sec (read) :> :> :> And a Dual 933MHz PIII SuperMicro 370DER Serverworks HE-SL Chipset :> (2-way interleaved PC133 ECC Registered DIMMS) :> :> ./x 4 :> 1853.54 MBytes/sec (read) :> ./x 1024 :> 526.19 MBytes/sec (read) : :Dell Precision 420 (i840 chipset) with a single PIII 800 and probably one :RIMM, unknown speed: : :{rivendell:/usr/home/ken/src:76:0} ./memspeed 4 :1049.51 MBytes/sec (read) :{rivendell:/usr/home/ken/src:77:0} ./memspeed 1024 :378.41 MBytes/sec (read) : :The above machine may not have been completely idle, it seems a little :slow. : :Dual 1GHz PIII SuperMicro 370DE6 Serverworks HE-SL chipset, 4x256MB PC133 :ECC Registered DIMMs: : :{gondolin:/usr/home/ken/src:51:0} ./memspeed 4 :1985.95 MBytes/sec (read) :{gondolin:/usr/home/ken/src:52:0} ./memspeed 1024 :516.62 MBytes/sec (read) : :> There's something diabolic about your previous bw test, though. I :> think it only hits one bank of interleaved ram. On the 370DER it gets :> only 167MB/sec. Every other bw test I've run on the box shows copy :> perf at around 260MB/sec (Hbench, lmbench). I see the same problem on :> a PE4400 (also 2-way interleaved); it shows copy perf as 111MB/sec. :> Every other test has it at 230MB/sec. : :The previous test showed about 270MB/sec on my Serverworks box: : :{gondolin:/usr/home/ken/src:53:0} ./memory_speed :269.23 MBytes/sec (copy) : :Ken :-- :Kenneth Merry :ken@kdm.org : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 13:35:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id D1AB237B71A for ; Tue, 6 Mar 2001 13:35:46 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f26LZiF59836; Tue, 6 Mar 2001 13:35:44 -0800 (PST) (envelope-from dillon) Date: Tue, 6 Mar 2001 13:35:44 -0800 (PST) From: Matt Dillon Message-Id: <200103062135.f26LZiF59836@earth.backplane.com> To: "Brandon Gale" Cc: "Kenneth D. Merry" , "Andrew Gallatin" , Subject: Re: RE: Machines are getting too damn fast References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :This explained in great detail exactly why people are seeing the performance :they are from the P4 etc. The author knows his stuff. : :http://www.emulators.com/pentium4.htm : :Brandon Heh heh. You can practically see the sweat popping off his face while reading his article. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 15: 8:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bdr-xcon.matchlogic.com (mail.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 6F30D37B719 for ; Tue, 6 Mar 2001 15:08:37 -0800 (PST) (envelope-from crandall@matchlogic.com) Received: by mail.matchlogic.com with Internet Mail Service (5.5.2653.19) id ; Tue, 6 Mar 2001 16:07:52 -0700 Message-ID: <5FE9B713CCCDD311A03400508B8B30130828E882@bdr-xcln.is.matchlogic.com> From: Charles Randall To: 'Matt Dillon' Cc: Andrew Gallatin , freebsd-hackers@FreeBSD.ORG Subject: RE: RE: Machines are getting too damn fast Date: Tue, 6 Mar 2001 16:07:50 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Noted. Is there a gcc PR associated with this? http://gcc.gnu.org/cgi-bin/gnatsweb.pl A GNATS searc for "freebsd kernel" didn't return anything. -Charles -----Original Message----- From: Matt Dillon [mailto:dillon@earth.backplane.com] Sent: Tuesday, March 06, 2001 11:44 AM To: Charles Randall Cc: Andrew Gallatin; freebsd-hackers@FreeBSD.ORG Subject: Re: RE: Machines are getting too damn fast :Which begs the question I've tried to ask a number of times in different :forums. Who's working on P4 optimizations and code generation for the P4? I'd be happy if GCC -O2 just worked without introducing bugs. I want to be able to compile the kernel with it again. -Matt :Sure, i386 code will run but the benchmarks seem to indicate that peak :performance is heavily dependent on a good optimizing compiler. : :A query to the gcc mailing list returned no responses. : :Charles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 15:58:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.prod.itd.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 24A6337B71A; Tue, 6 Mar 2001 15:58:48 -0800 (PST) (envelope-from zzcrow@earthlink.net) Received: from vaio (user-2ivfob8.dialup.mindspring.com [165.247.225.104]) by gull.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id PAA28454; Tue, 6 Mar 2001 15:58:45 -0800 (PST) Message-ID: <000801c0a690$9b7c7420$68e1f7a5@vaio> Reply-To: "Louis Thompson" From: "Louis Thompson" To: Cc: Subject: PCMCIA Network Adapter problems Date: Tue, 6 Mar 2001 14:55:53 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C0A64D.8AF55380" 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 This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C0A64D.8AF55380 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Sir, I just started using Free-BSD, and am having some problems making it see = my network adapter on my laptop. It sees the controller fine, just not = the card itself. The card I am attempting to use is a 3Com Megahertz = 10/100Mb Lan + 56K modem card, model number 3CCFEM656B. Any help at all = would be greatly appriciated, and I appologize for the inconvenience. =20 Sincerly, Jason ------=_NextPart_000_0005_01C0A64D.8AF55380 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Dear Sir,
 
I just started using Free-BSD, and am = having some=20 problems making it see my network adapter on my laptop.  It sees = the=20 controller fine, just not the card itself.  The card I am = attempting to use=20 is a 3Com Megahertz 10/100Mb Lan + 56K modem card, model number=20 3CCFEM656B.  Any help at all would be greatly appriciated, and I = appologize=20 for the inconvenience. 
 
 
 
Sincerly,
 
Jason
------=_NextPart_000_0005_01C0A64D.8AF55380-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 16: 6:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id B33D437B718; Tue, 6 Mar 2001 16:06:10 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f27068t22068; Tue, 6 Mar 2001 16:06:08 -0800 Date: Tue, 6 Mar 2001 16:06:08 -0800 From: Brooks Davis To: Louis Thompson Cc: questions@FreeBSD.ORG Subject: Re: PCMCIA Network Adapter problems Message-ID: <20010306160608.B17828@Odin.AC.HMC.Edu> References: <000801c0a690$9b7c7420$68e1f7a5@vaio> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="hQiwHBbRI9kgIhsi" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <000801c0a690$9b7c7420$68e1f7a5@vaio>; from zzcrow@earthlink.net on Tue, Mar 06, 2001 at 02:55:53PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --hQiwHBbRI9kgIhsi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [Please don't send HTML e-mail. Also, don't send questions like this to -hackers.] On Tue, Mar 06, 2001 at 02:55:53PM -0800, Louis Thompson wrote: > I just started using Free-BSD, and am having some problems making it > see my network adapter on my laptop. It sees the controller fine, > just not the card itself. The card I am attempting to use is a 3Com > Megahertz 10/100Mb Lan + 56K modem card, model number 3CCFEM656B. Any > help at all would be greatly appriciated, and I appologize for the > inconvenience. This card is a cardbus card and thus is not supported in FreeBSD 4.x. The Ethernet side probably works in -current, but now is probably not the time to venture into -current for the first time unless you have a very high pain threshold. The 56K modem is unlikely to work anytime soon since it's most likely a WinModem. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --hQiwHBbRI9kgIhsi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6pXtvXY6L6fI4GtQRAqudAKCVASr3KOkXubj1UGHrTx5IFfNcrwCgmAax qq9N6MIe1S21YVIxF/xq/rE= =SLb8 -----END PGP SIGNATURE----- --hQiwHBbRI9kgIhsi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 18: 1:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shakeyjakes.com (cx658371-a.elcjn1.sdca.home.com [24.13.29.199]) by hub.freebsd.org (Postfix) with SMTP id BC1A237B718 for ; Tue, 6 Mar 2001 18:01:07 -0800 (PST) (envelope-from mike.mcclain@shakeyjakes.com) Received: by shakeyjakes.com (wcMail) id 25888W Tue, 06 Mar 2001 17:59:52 -0800 From: mike.mcclain@shakeyjakes.com Subject: Help!!! 2nd HD gone Date: Tue, 06 Mar 2001 17:59:52 -0800 Message-Id: <1885265869@shakeyjakes.com> Organization: Shakey Jake's Free BBS from Santee, Ca... To: freebsd-hackers@freebsd.org X-Mailer: wcMail v5.4.449.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy, I hadn't booted FreeBSD 3.4 for many months but had mounted several partitions on /dev/wd2s* from /etc/fstab. Last week I couldn't get a clean boot 'til I took all references to /dev/wd2s* out of /etc/fstab. Having done that I now see: fbsd:~> mount -t ext2fs /dev/wd2s1 /rh6 ext2fs: /dev/wd2s1: Device not configured fbsd:~> fdisk /dev/wd2.fdisk: cannot open disk /dev/wd2: Device not configured fbsd:~> disklabel /dev/wd2 disklabel: /dev/wd2: Device not configured fbsd:~> ls -l /dev/wd2s* brw-r----- 1 root operator 0, 0x00020012 Mar 20 2000 /dev/wd2s1 ... /dev/wd2s2 through /dev/wd2s8 nearly identical brw-r----- 1 root operator 0, 0x000a0012 Apr 20 2000 /dev/wd2s9 from /var/log/dmesg.today: this is the way it was. wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0:4112MB (8421840 sectors), 8912 cyls, 15 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S from /var/log/messages: May 23 18:15:19 /kernel: wdc1 at 0x170-0x177 irq 15 on isa May 23 18:15:19 /kernel: wdc1: unit 0 (wd2): Feb 11 16:27:36 /kernel: wdc1 not found at 0x170 This makes me think the kernal is not seeing the controller at boot. wd2 aka D: aka /dev/hdc is visible from dos and I'm writing this from Slackware 7.0 mounted on /dev/hdc8. This from Slackware's /var/log/messages: Feb 15 09:20:15 playground kernel: hda: WDC AC24300L, 4112MB w/256kB Cache, CHS=524/255/63, UDMA Feb 15 09:20:15 playground kernel: hdc: WDC AC26400R, 6149MB w/512kB Cache, CHS=13328/15/63, (U)DMA I'm stumped. All suggestions welcome. TIA, MiKe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 6 19:38: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 6211E37B719 for ; Tue, 6 Mar 2001 19:38:01 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f273boh71386; Tue, 6 Mar 2001 19:37:50 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200103070337.f273boh71386@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: David Xu Cc: sthaug@nethelp.no, freebsd-hackers@FreeBSD.ORG Subject: Re: Missing support in FreeBSD for large file sizes? In-Reply-To: <522302651.20010306091323@21cn.com> Date: Tue, 06 Mar 2001 19:37:50 -0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Xu wrote: > Hello sthaug, > > Tuesday, March 06, 2001, 1:24:24 AM, you wrote: > > snn> According to the "Maxtor picks Windows, dumps open source" article at > > snn> http://news.cnet.com/news/0-1003-200-5009496.html?tag=lh > > snn> FreeBSD "did not support large file sizes, Macintosh and newer Novell > snn> file systems, or backup and management software from companies such as > snn> OpenView, Tivoli and Microsoft". > > snn> Now I can understand what they say about missing Tivoli support - we're > snn> using Tivoli backup here ourselves, and the SCO ADSM/TSM client that we > snn> currently use to backup FreeBSD is passable, but nothing more. A native > snn> FreeBSD client would be much preferable. > > snn> What I can't understand is the reference to missing support for large > snn> file sizes - as far as I know, that's one of FreeBSD's strengths! Anybod y > snn> care to guess what they mean here? > > snn> Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > snn> To Unsubscribe: send mail to majordomo@FreeBSD.org > snn> with "unsubscribe freebsd-hackers" in the body of the message > > this is a stupid decision, let they go. AFAIK, Windows 2000 does not > support dump file system to tape or other medias. I was a Windows NT > system manager, I know I don't believe all backup softwares for Windows > NT, simply because Windows NT system can not be fully backuped. > FreeBSD can do, it's strength of Unix File System. There is a lot more to it than technical merit. Also consider the strings that M$ is pulling over the X-box. If Maxtor wanted to get Maxtor or Quantum drives in it, you can bet that Microsoft demanded concessions... You could pretty safely bet your last dollar that this was a management decision, not a technical one. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 8:45:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 6A6A737B719 for ; Wed, 7 Mar 2001 08:45:07 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id LAA69194 for ; Wed, 7 Mar 2001 11:56:29 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010307114211.0241d9e0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 07 Mar 2001 12:00:27 -0500 To: hackers@freebsd.org From: Dennis Subject: if_fxp status? 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 really dont care to ask this on the list, but DG doesnt answer my private emails, so I have little choice. has any progress been made on making the if_fxp driver work with the latest intel NICs? Its been over 3 months since the problems creeped up, and its becoming a serious problem explaining to potential freebsd users why is doesnt work. thanks, DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 9:20:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id B401E37B71B for ; Wed, 7 Mar 2001 09:20:16 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f27HI2133306; Wed, 7 Mar 2001 11:18:02 -0600 (CST) (envelope-from jlemon) Date: Wed, 7 Mar 2001 11:18:02 -0600 (CST) From: Jonathan Lemon Message-Id: <200103071718.f27HI2133306@prism.flugsvamp.com> To: dennis@etinc.com, hackers@freebsd.org Subject: Re: if_fxp status? X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: > >I really dont care to ask this on the list, but DG doesnt answer my private >emails, so I have little choice. > >has any progress been made on making the if_fxp driver work with the latest >intel NICs? Its been over 3 months since the problems creeped up, and its >becoming a serious problem explaining to potential freebsd users why is >doesnt work. You might receive more informed answers if you would detail exactly what problems that you are seeing, and what hardware you are using. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 9:43:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id BD9B937B719 for ; Wed, 7 Mar 2001 09:43:25 -0800 (PST) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f27HhJr00796 for ; Wed, 7 Mar 2001 11:43:21 -0600 (CST) Message-Id: <200103071743.f27HhJr00796@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: hackers@freebsd.org Subject: Re: if_fxp status? In-reply-to: Your message of "Wed, 07 Mar 2001 12:00:27 EST." <5.0.0.25.0.20010307114211.0241d9e0@mail.etinc.com> Date: Wed, 07 Mar 2001 11:43:19 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5.0.0.25.0.20010307114211.0241d9e0@mail.etinc.com>, Dennis writes: >I really dont care to ask this on the list, but DG doesnt answer my private >emails, so I have little choice. Yup. None at all. I mean, you're getting something for free, and the people giving it away don't seem to be able to build their schedules around your life. I can see how you'd have no choice but to bug everyone else, too. Now, frankly, my response isn't a *whole* lot more useful than your message, but hey, maybe there's an off chance that this will be the magical occasion on which you finally *get it*. >has any progress been made on making the if_fxp driver work with the latest >intel NICs? Yes. Yes, Dennis. We have it working. The code is in a special branch of the tree, which we normally don't discuss publically. I'm just bringing this up because I'm sick of living a lie. We are planning to release all the code as soon as you give up on FreeBSD and go use something else. We just don't *like* you. >Its been over 3 months since the problems creeped up, and its >becoming a serious problem explaining to potential freebsd users why is >doesnt work. It doesn't work because we want to keep *you* from using it. It's a conspiracy. If you want it to work, pay someone to fix it. This is how free software *works*. It doesn't work by means of people who don't contribute code whining until they get what they want. It's a *trade-off*. If you want service and support, go buy it. If you want what you get for free, *TAKE* what you get for free, and stop complaining that it's not what you'd have wanted if you were going to pay for it. This keeps coming up, over and over, and you just don't seem to get it. The FreeBSD project doesn't care what you want, or what I want, until such time as we're contributing code. It isn't *supposed* to care what we want. It's government by the people who are willing to put the time and effort in, and complaining about how important something is *to you* doesn't count. If you have trouble explaining to potential FreeBSD users why something doesn't work, I suggest the following: It doesn't work because no one has yet wanted it enough to do it, or to pay for it to be done. If you really want this, perhaps you should look into finding out how much it would cost, and contributing. If a few people shared the cost of a fairly easy piece of new code, it would quite likely be cheaper than buying them a Windows license each. Note that you, yourself, could be one of those few people. I would be, if I needed the fxp driver upgraded. :) -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 9:43:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id D677A37B719 for ; Wed, 7 Mar 2001 09:43:37 -0800 (PST) (envelope-from reichert@natto.numachi.com) Received: (qmail 9628 invoked by uid 3001); 7 Mar 2001 17:43:31 -0000 Received: from natto.numachi.com (198.175.254.216) by numachi.numachi.com with SMTP; 7 Mar 2001 17:43:31 -0000 Received: (qmail 69147 invoked by uid 1001); 7 Mar 2001 17:43:31 -0000 Date: Wed, 7 Mar 2001 12:43:31 -0500 From: Brian Reichert To: freebsd-hackers@freebsd.org Subject: swap info: 'ps' as opposed to 'limits' Message-ID: <20010307124331.E71030@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pardon my ignorance: I'm trying to corral bloated processes, WRT swap usage. I wish to control them via 'limits'. However, I'm (in my ignorance) unable to map the attributes that 'ps' can report on, ie.: # ps -opid,rss,rsz,vsz,command (there are others, of course) To the attributes that can be controlled via the setrlimit(2) utilities (ulimits, limits, et al.) RLIMIT_DATA datasize RLIMIT_RSS memoryuse RLIMIT_STACK stacksize (there are others, of course) Does anyone have any quickie pointers? I _think_ some comination of rss or rsz -> memoryuse will be what I want, but I don't know how to infer stack usage via 'ps'. And what is 'vsz' (virtual size) anway, WRT setrlimit? -- Brian 'you Bastard' Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 10:54:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mobile.hub.org (cr529263-a.wlfdle1.on.wave.home.com [24.42.167.110]) by hub.freebsd.org (Postfix) with ESMTP id F146037B71D for ; Wed, 7 Mar 2001 10:54:07 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.1/8.11.1) with ESMTP id f27Irtl33749; Wed, 7 Mar 2001 14:54:05 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Wed, 7 Mar 2001 14:53:55 -0400 (AST) From: The Hermit Hacker To: Dennis Cc: Subject: Re: if_fxp status? In-Reply-To: <5.0.0.25.0.20010307114211.0241d9e0@mail.etinc.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 Wed, 7 Mar 2001, Dennis wrote: > > I really dont care to ask this on the list, but DG doesnt answer my private > emails, so I have little choice. > > has any progress been made on making the if_fxp driver work with the latest > intel NICs? Its been over 3 months since the problems creeped up, and its > becoming a serious problem explaining to potential freebsd users why is > doesnt work. Have you asked on the -net list, where work on stuff like this happens? Have you checked on -current, to see if maybe its available, just not in the 4.x branch? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 10:56:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mobile.hub.org (cr529263-a.wlfdle1.on.wave.home.com [24.42.167.110]) by hub.freebsd.org (Postfix) with ESMTP id AB88837B719 for ; Wed, 7 Mar 2001 10:56:40 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by mobile.hub.org (8.11.1/8.11.1) with ESMTP id f27Iuat33756; Wed, 7 Mar 2001 14:56:37 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: mobile.hub.org: scrappy owned process doing -bs Date: Wed, 7 Mar 2001 14:56:36 -0400 (AST) From: The Hermit Hacker To: Peter Seebach Cc: Subject: Re: if_fxp status? In-Reply-To: <200103071743.f27HhJr00796@guild.plethora.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 On Wed, 7 Mar 2001, Peter Seebach wrote: > Yes, Dennis. We have it working. The code is in a special branch of > the tree, which we normally don't discuss publically. I'm just > bringing this up because I'm sick of living a lie. We are planning to > release all the code as soon as you give up on FreeBSD and go use > something else. We just don't *like* you. Ummmm ... is this special branch available via CVSup, or only CVS? *grin* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 11:19: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id AFD5137B71C for ; Wed, 7 Mar 2001 11:18:57 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f27JIgr01593; Wed, 7 Mar 2001 11:18:47 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103071918.f27JIgr01593@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: seebs@plethora.net (Peter Seebach) Cc: hackers@freebsd.org Subject: Re: if_fxp status? In-reply-to: Your message of "Wed, 07 Mar 2001 11:43:19 CST." <200103071743.f27HhJr00796@guild.plethora.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Mar 2001 11:18:42 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <5.0.0.25.0.20010307114211.0241d9e0@mail.etinc.com>, Dennis writes: > >I really dont care to ask this on the list, but DG doesnt answer my private > >emails, so I have little choice. > > Yup. None at all. I mean, you're getting something for free, and the > people giving it away don't seem to be able to build their schedules around > your life. I can see how you'd have no choice but to bug everyone else, > too. Uh, folks, and particularly you, Peter. Far be it for me to be seen to be sticking up for Dennis (!), but he *does* have a point here, and his reticence is actually quite understandable. DG has not been maintaining the fxp driver as well as many people would like, and it's fair to say that it *is* slipping behind in support for new hardware coming out of intel. Dennis - to answer your question: no, there is no work in progress (to the best of my knowledge) on the fxp driver that's not already visible in the drivers in current/stable. DG is currently going through some things that make him even more of a challenge than usual to contact, and this isn't improving the situation. I don't have a lot of options to recommend right now, I'm sorry, other than the usual (find someone else willing to do the work, send them samples of troublesome adapters). Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 11:29:31 2001 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 28C6337B719; Wed, 7 Mar 2001 11:29:28 -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 UAA28806; Wed, 7 Mar 2001 20:30:01 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103071930.UAA28806@info.iet.unipi.it> Subject: Re: if_fxp status? In-Reply-To: <200103071918.f27JIgr01593@mass.dis.org> from Mike Smith at "Mar 7, 2001 11:18:42 am" To: Mike Smith Date: Wed, 7 Mar 2001 20:30:00 +0100 (CET) Cc: Peter Seebach , 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 > Dennis - to answer your question: no, there is no work in progress (to > the best of my knowledge) on the fxp driver that's not already visible in i am not sure what the problem is that dennis is referring to, but certainly the lack of documentation does not help. This said, in some recent experiments i have done i found that the intel card (or the driver maybe, i have no idea, though i have tried all possible options with the docs i have) is unable to generate traffic at full link speed with 64-byte packets -- basically it tops around 105-110Kpackets/s as opposed to the 145Kpkt/s that other cards ('dc', 'xl') are capable of -- and mind you, this is not because the system is running out of CPU, it's just the card that (at least as programmed in our driver) appears to wait an additional 3us between back to back packets. Now, the 21143 (which is a pretty nice chip and has available documentation and a decent driver, "dc") is discontinued, but there are clones which work reasonably well (and are even cheaper, around $30 or so at compusa, i think netgear or linksys does one of these cards). I'd go with them. No multiport card, at least as far as i know. cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone (510) 666 2927 . ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 14: 7:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 0873237B719 for ; Wed, 7 Mar 2001 14:07:46 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id RAA70515; Wed, 7 Mar 2001 17:19:15 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010307172249.0231e140@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 07 Mar 2001 17:23:09 -0500 To: Jonathan Lemon , hackers@freebsd.org From: Dennis Subject: Re: if_fxp status? In-Reply-To: <200103071718.f27HI2133306@prism.flugsvamp.com> References: 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 At 12:18 PM 03/07/2001, Jonathan Lemon wrote: >In article > >you write: > > > >I really dont care to ask this on the list, but DG doesnt answer my private > >emails, so I have little choice. > > > >has any progress been made on making the if_fxp driver work with the latest > >intel NICs? Its been over 3 months since the problems creeped up, and its > >becoming a serious problem explaining to potential freebsd users why is > >doesnt work. > >You might receive more informed answers if you would detail >exactly what problems that you are seeing, and what hardware >you are using. The people involved know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 14:21:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id DCE3E37B71B for ; Wed, 7 Mar 2001 14:21:29 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f27MKrA76476; Wed, 7 Mar 2001 14:20:53 -0800 (PST) (envelope-from dillon) Date: Wed, 7 Mar 2001 14:20:53 -0800 (PST) From: Matt Dillon Message-Id: <200103072220.f27MKrA76476@earth.backplane.com> To: Dennis Cc: Jonathan Lemon , hackers@FreeBSD.ORG Subject: Re: if_fxp status? References: <5.0.0.25.0.20010307172249.0231e140@mail.etinc.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :The people involved know. : Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 14:35:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (s014.dhcp212-24.cybercable.fr [212.198.24.14]) by hub.freebsd.org (Postfix) with ESMTP id 0780537B71A for ; Wed, 7 Mar 2001 14:35:13 -0800 (PST) (envelope-from thierry.herbelot@free.fr) Received: from free.fr (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id XAA40813; Wed, 7 Mar 2001 23:34:33 +0100 (CET) (envelope-from thierry.herbelot@free.fr) Message-ID: <3AA6B778.D4E934E0@free.fr> Date: Wed, 07 Mar 2001 23:34:32 +0100 From: Thierry Herbelot Reply-To: thierry@herbelot.com X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Luigi Rizzo Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp status? References: <200103071930.UAA28806@info.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > [SNIP] > Now, the 21143 (which is a pretty nice chip and has available > documentation and a decent driver, "dc") is discontinued, but there > are clones which work reasonably well (and are even cheaper, around > $30 or so at compusa, i think netgear or linksys does one of these > cards). I'd go with them. No multiport card, at least as far as i know. What : no more dc multiport board ? are you sure of this ? if so, it may be wise to buy some D-link 570-TX boards in advance for my project. Cheers -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 16:33:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id CF8A637B71A for ; Wed, 7 Mar 2001 16:33:12 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f280Ush48040; Wed, 7 Mar 2001 18:30:54 -0600 (CST) (envelope-from jlemon) Date: Wed, 7 Mar 2001 18:30:54 -0600 From: Jonathan Lemon To: Dennis Cc: Jonathan Lemon , hackers@freebsd.org Subject: Re: if_fxp status? Message-ID: <20010307183054.N41963@prism.flugsvamp.com> References: <200103071718.f27HI2133306@prism.flugsvamp.com> <5.0.0.25.0.20010307172249.0231e140@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <5.0.0.25.0.20010307172249.0231e140@mail.etinc.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 07, 2001 at 05:23:09PM -0500, Dennis wrote: > At 12:18 PM 03/07/2001, Jonathan Lemon wrote: > >In article > > > >you write: > > > > > >I really dont care to ask this on the list, but DG doesnt answer my private > > >emails, so I have little choice. > > > > > >has any progress been made on making the if_fxp driver work with the latest > > >intel NICs? Its been over 3 months since the problems creeped up, and its > > >becoming a serious problem explaining to potential freebsd users why is > > >doesnt work. > > > >You might receive more informed answers if you would detail > >exactly what problems that you are seeing, and what hardware > >you are using. > > The people involved know. Great! I'm so glad to hear that. I guess then I don't need to worry at all about fixing the driver, I see everything is under control. HAND! -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 16:51:14 2001 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 A884B37B718 for ; Wed, 7 Mar 2001 16:51:11 -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 BAA31339; Thu, 8 Mar 2001 01:51:39 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103080051.BAA31339@info.iet.unipi.it> Subject: Re: if_fxp status? In-Reply-To: <3AA6B778.D4E934E0@free.fr> from Thierry Herbelot at "Mar 7, 2001 11:34:32 pm" To: thierry@herbelot.com Date: Thu, 8 Mar 2001 01:51:39 +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 > What : no more dc multiport board ? are you sure of this ? if so, it may > be wise to buy some D-link 570-TX boards in advance for my project. maybe some producer switch to the tulip clones -- i just do not know who sells them (i'd love to know!) cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 17:17:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id CFE3F37B718 for ; Wed, 7 Mar 2001 17:17:20 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id UAA71398; Wed, 7 Mar 2001 20:28:50 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010307203053.021b22c0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 07 Mar 2001 20:32:46 -0500 To: thierry@herbelot.com, Luigi Rizzo From: Dennis Subject: Re: if_fxp status? Cc: hackers@FreeBSD.ORG In-Reply-To: <3AA6B778.D4E934E0@free.fr> References: <200103071930.UAA28806@info.iet.unipi.it> 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 At 05:34 PM 03/07/2001, Thierry Herbelot wrote: >Luigi Rizzo wrote: > > >[SNIP] > > > Now, the 21143 (which is a pretty nice chip and has available > > documentation and a decent driver, "dc") is discontinued, but there > > are clones which work reasonably well (and are even cheaper, around > > $30 or so at compusa, i think netgear or linksys does one of these > > cards). I'd go with them. No multiport card, at least as far as i know. > >What : no more dc multiport board ? are you sure of this ? if so, it may >be wise to buy some D-link 570-TX boards in advance for my project. The 21143 is not discontinued. Its an afterthought perhaps, but still in use by Dlink for sure and certainly others. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 17:18:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id BED0837B71A for ; Wed, 7 Mar 2001 17:18:14 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id UAA71407; Wed, 7 Mar 2001 20:29:47 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010307203311.023a74f0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 07 Mar 2001 20:33:43 -0500 To: Matt Dillon From: Dennis Subject: Re: if_fxp status? Cc: hackers@freebsd.org In-Reply-To: <200103072220.f27MKrA76476@earth.backplane.com> References: <5.0.0.25.0.20010307172249.0231e140@mail.etinc.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 At 05:20 PM 03/07/2001, you wrote: >: >:The people involved know. >: > > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) > > -Matt its been discussed several times on this list. No need to go into it again. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 17:33:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id A6A4C37B718; Wed, 7 Mar 2001 17:33:23 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id UAA71465; Wed, 7 Mar 2001 20:44:56 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010307203511.023a64b0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 07 Mar 2001 20:48:52 -0500 To: Mike Smith , seebs@plethora.net (Peter Seebach) From: Dennis Subject: Re: if_fxp status? Cc: hackers@FreeBSD.ORG In-Reply-To: <200103071918.f27JIgr01593@mass.dis.org> References: 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 At 02:18 PM 03/07/2001, Mike Smith wrote: > > In message <5.0.0.25.0.20010307114211.0241d9e0@mail.etinc.com>, Dennis > writes: > > >I really dont care to ask this on the list, but DG doesnt answer my > private > > >emails, so I have little choice. > > > > Yup. None at all. I mean, you're getting something for free, and the > > people giving it away don't seem to be able to build their schedules around > > your life. I can see how you'd have no choice but to bug everyone else, > > too. > >Uh, folks, and particularly you, Peter. > >Far be it for me to be seen to be sticking up for Dennis (!), but he >*does* have a point here, and his reticence is actually quite >understandable. > >DG has not been maintaining the fxp driver as well as many people would >like, and it's fair to say that it *is* slipping behind in support for new >hardware coming out of intel. > >Dennis - to answer your question: no, there is no work in progress (to >the best of my knowledge) on the fxp driver that's not already visible in >the drivers in current/stable. DG is currently going through some things >that make him even more of a challenge than usual to contact, and this >isn't improving the situation. Last I heard is that someone sent him a board a few weeks back, so I "ass-umed" that something was in progress. I dont know why he would take a board from someone if he had no expectation of fixing it. The fxp is an important driver. Its been touted as the "driver of choice". The same thing happened when the de driver was consistently out of wack back in the 2.X days. I dont think its good for FreeBSD Unfortunately, it seems that noone other than DG has done any significant work on this driver. so its a big project trying to decode it, particularly with no help from him. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 18:26:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id E22C737B73F for ; Wed, 7 Mar 2001 18:26:30 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f282QLh83988; Wed, 7 Mar 2001 18:26:22 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200103080226.f282QLh83988@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Dennis Cc: Matt Dillon , hackers@FreeBSD.ORG Subject: Re: if_fxp status? In-Reply-To: <5.0.0.25.0.20010307203311.023a74f0@mail.etinc.com> Date: Wed, 07 Mar 2001 18:26:21 -0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > At 05:20 PM 03/07/2001, you wrote: > >: > >:The people involved know. > >: > > > > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) > > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) > > > > -Matt > > > its been discussed several times on this list. No need to go into it again. Then why the hell are you posting if there is no need to go into it again? It is extremely bad form to post asking for something without supplying details or at least a pointer to where they are (msgid's etc). There are other people who can fix it, but they cannot do anything if you refuse to supply all the precise details in an easy to access form. If you are unwilling to do that, then stop bothering us! Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 19:41:10 2001 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 D714337B71A for ; Wed, 7 Mar 2001 19:41:02 -0800 (PST) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-117-6.nnj.dialup.bellatlantic.net [151.198.117.6]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id WAA09315; Wed, 7 Mar 2001 22:40:56 -0500 (EST) Message-ID: <3AA6FF47.A6CD3DB3@bellatlantic.net> Date: Wed, 07 Mar 2001 22:40:55 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Luigi Rizzo Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp status? References: <200103071930.UAA28806@info.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > Now, the 21143 (which is a pretty nice chip and has available > documentation and a decent driver, "dc") is discontinued, but there > are clones which work reasonably well (and are even cheaper, around > $30 or so at compusa, i think netgear or linksys does one of these > cards). I'd go with them. No multiport card, at least as far as i know. Could you tell the exact models ? I know that the SMC cards and some others are using the same chip as well but apparently they have some differences in some parts circuitry, so that they need special support in the driver. So I wonder if you actually got these Linksys and Netgear cards working with FreeBSD. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 22:15:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id C334337B718 for ; Wed, 7 Mar 2001 22:15:26 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f286EpB19932; Thu, 8 Mar 2001 07:14:55 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: Dennis , Matt Dillon , hackers@FreeBSD.ORG Subject: Re: if_fxp status? In-Reply-To: Your message of "Wed, 07 Mar 2001 18:26:21 PST." <200103080226.f282QLh83988@mobile.wemm.org> Date: Thu, 08 Mar 2001 07:14:51 +0100 Message-ID: <19930.984032091@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200103080226.f282QLh83988@mobile.wemm.org>, Peter Wemm writes: >Dennis wrote: >> At 05:20 PM 03/07/2001, you wrote: >> >: >> >:The people involved know. >> >: >> > >> > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) >> > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) >> > >> > -Matt >> >> >> its been discussed several times on this list. No need to go into it again. > >Then why the hell are you posting if there is no need to go into it again? >It is extremely bad form to post asking for something without supplying >details or at least a pointer to where they are (msgid's etc). > >There are other people who can fix it, but they cannot do anything if you >refuse to supply all the precise details in an easy to access form. >If you are unwilling to do that, then stop bothering us! Indeed, I think Dennis could solve two problems by just dropping FreeBSD right away. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 7 23: 5: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by hub.freebsd.org (Postfix) with ESMTP id C56FC37B718 for ; Wed, 7 Mar 2001 23:04:58 -0800 (PST) (envelope-from blaz@amis.net) Received: by titanic.medinet.si (Postfix, from userid 1000) id 3FDD726C02; Thu, 8 Mar 2001 08:04:57 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by titanic.medinet.si (Postfix) with ESMTP id 343D511713 for ; Thu, 8 Mar 2001 08:04:57 +0100 (CET) Date: Thu, 8 Mar 2001 08:04:57 +0100 (CET) From: Blaz Zupan To: Subject: PATCH: workaround for FreeBSD 4.2-STABLE (fwd) 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 Anybody know which bug Wietse is talking about? Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 ---------- Forwarded message ---------- Date: Wed, 7 Mar 2001 10:49:52 -0500 (EST) From: Wietse Venema To: Postfix users Subject: PATCH: workaround for FreeBSD 4.2-STABLE This is an UNTESTED workaround for an incompatible change in FreeBSD 4.2-STABLE that causes data to be lost when a client close()s a socket before the server has accept()ed the connection. This screws up the Postfix flush service, and may make some parts of Postfix fail randomly under a heavy system load. The UNTESTED workaround causes the client to wait until the server closes the connection first. This makes Postfix slower than necessary. The workaround is UNTESTED because I have no time to download and install FreeBSD 4.2-STABLE. To compile this UNTESTED workaround: [ apply patch ] % make makefiles CCARGS=-DBROKEN_FREEBSD_ACCEPT % make % su [ type your root password here ] # make install To: Blaz Zupan Cc: hackers@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: PATCH: workaround for FreeBSD 4.2-STABLE (fwd) Message-ID: <20010307233854.A18351@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from blaz@amis.net on Thu, Mar 08, 2001 at 08:04:57AM +0100 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc'd J Lemon because I think he's the one that made do the ECONNABORTED (sp?) * Blaz Zupan [010307 23:05] wrote: > Anybody know which bug Wietse is talking about? It could be a mistake, but it seems like there might be a problem if: client connects to server client sends data client closes socket server tries an accept It looks like the server won't get the buffered data, only a notification that a connection aborted when in reality it was just close()'d by the client before accept() could be called by the server. Jonathan, is this possible? > > Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia > E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 > > ---------- Forwarded message ---------- > Date: Wed, 7 Mar 2001 10:49:52 -0500 (EST) > From: Wietse Venema > To: Postfix users > Subject: PATCH: workaround for FreeBSD 4.2-STABLE > > This is an UNTESTED workaround for an incompatible change in FreeBSD > 4.2-STABLE that causes data to be lost when a client close()s a > socket before the server has accept()ed the connection. This screws > up the Postfix flush service, and may make some parts of Postfix > fail randomly under a heavy system load. > > The UNTESTED workaround causes the client to wait until the server > closes the connection first. This makes Postfix slower than necessary. > > The workaround is UNTESTED because I have no time to download and > install FreeBSD 4.2-STABLE. > > To compile this UNTESTED workaround: > > [ apply patch ] > % make makefiles CCARGS=-DBROKEN_FREEBSD_ACCEPT > % make > % su > [ type your root password here ] > # make install > Someone can tell the list if this UNTESTED workaround actually works. > > Wietse > > *** ./unix_trigger.c- Sun Mar 21 20:42:20 1999 > --- ./unix_trigger.c Wed Mar 7 10:40:29 2001 > *************** > *** 79,84 **** > --- 79,90 ---- > if (msg_verbose) > msg_warn("%s: write to %s: %m", myname, service); > > + #ifdef BROKEN_FREEBSD_ACCEPT > + if (shutdown(fd, 1) < 0) > + msg_fatal("shutdown: %m"); > + read_wait(fd, -1); > + #endif > + > /* > * Disconnect. > */ > *** ./inet_trigger.c- Fri Dec 11 13:55:36 1998 > --- ./inet_trigger.c Wed Mar 7 10:39:53 2001 > *************** > *** 81,86 **** > --- 81,92 ---- > if (msg_verbose) > msg_warn("%s: write to %s: %m", myname, service); > > + #ifdef BROKEN_FREEBSD_ACCEPT > + if (shutdown(fd, 1) < 0) > + msg_fatal("shutdown: %m"); > + read_wait(fd, -1); > + #endif > + > /* > * Disconnect. > */ > *** ./sane_accept.c- Sun Mar 21 20:25:52 1999 > --- ./sane_accept.c Wed Mar 7 10:32:59 2001 > *************** > *** 53,58 **** > --- 53,61 ---- > ENETUNREACH, > ENOTCONN, > EWOULDBLOCK, > + #ifdef BROKEN_FREEBSD_ACCEPT > + ECONNABORTED, > + #endif > 0, > }; > int count; > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the 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 Thu Mar 8 0:34:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 6138537B719 for ; Thu, 8 Mar 2001 00:34:12 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14asjr-0000Bh-00; Wed, 07 Mar 2001 22:13:23 -0700 Message-ID: <3AA714F3.E28037B5@softweyr.com> Date: Wed, 07 Mar 2001 22:13:23 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sergey Babkin Cc: Luigi Rizzo , hackers@FreeBSD.ORG Subject: Re: if_fxp status? References: <200103071930.UAA28806@info.iet.unipi.it> <3AA6FF47.A6CD3DB3@bellatlantic.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sergey Babkin wrote: > > Luigi Rizzo wrote: > > > Now, the 21143 (which is a pretty nice chip and has available > > documentation and a decent driver, "dc") is discontinued, but there > > are clones which work reasonably well (and are even cheaper, around > > $30 or so at compusa, i think netgear or linksys does one of these > > cards). I'd go with them. No multiport card, at least as far as i know. > > Could you tell the exact models ? I know that the SMC cards > and some others are using the same chip as well but apparently they > have some differences in some parts circuitry, so that they need > special support in the driver. So I wonder if you actually got > these Linksys and Netgear cards working with FreeBSD. NetGear FA310TX. Yes, I have several working under FreeBSD and OpenBSD. -- "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 Mar 8 0:39:17 2001 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 12E8937B719 for ; Thu, 8 Mar 2001 00:39:14 -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 JAA35120; Thu, 8 Mar 2001 09:39:43 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103080839.JAA35120@info.iet.unipi.it> Subject: Re: if_fxp status? In-Reply-To: <3AA714F3.E28037B5@softweyr.com> from Wes Peters at "Mar 7, 2001 10:13:23 pm" To: Wes Peters Date: Thu, 8 Mar 2001 09:39:43 +0100 (CET) Cc: Sergey Babkin , 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 > > Could you tell the exact models ? I know that the SMC cards it was actually the Linksys NC100, whose chipset is strangely labeled but it is recognised by the "dc" driver. I could not find a NetGear with the tulip chipset or clone. cheers luigi > > and some others are using the same chip as well but apparently they > > have some differences in some parts circuitry, so that they need > > special support in the driver. So I wonder if you actually got > > these Linksys and Netgear cards working with FreeBSD. > > NetGear FA310TX. Yes, I have several working under FreeBSD and OpenBSD. > > -- > "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 Mar 8 0:44: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id BC45237B718 for ; Thu, 8 Mar 2001 00:43:57 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14aw1b-0000Ff-00; Thu, 08 Mar 2001 01:43:55 -0700 Message-ID: <3AA7464B.4B6EC710@softweyr.com> Date: Thu, 08 Mar 2001 01:43:55 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Luigi Rizzo Cc: Sergey Babkin , hackers@FreeBSD.ORG Subject: Re: if_fxp status? References: <200103080839.JAA35120@info.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > > > > Could you tell the exact models ? I know that the SMC cards > > it was actually the Linksys NC100, whose chipset is strangely > labeled but it is recognised by the "dc" driver. > > I could not find a NetGear with the tulip chipset or clone. The FA310TX has a PNIC. Linksys and D-Link make cards with Davicom DM9102 and ADMtek chipsets that are also Tulip clones. -- "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 Mar 8 1:58:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 4801737B718 for ; Thu, 8 Mar 2001 01:58:32 -0800 (PST) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01K0Y9RPB5PE000GNS@research.kpn.com> for hackers@FreeBSD.ORG; Thu, 8 Mar 2001 10:58:30 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Thu, 08 Mar 2001 10:58:30 +0100 Content-return: allowed Date: Thu, 08 Mar 2001 10:58:29 +0100 From: "Koster, K.J." Subject: RE: if_fxp status? To: hackers@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7C92@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear All, > > >> > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) > >> > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) > :-) > > > > its been discussed several times on this list. No need to > > > go into it again. > > > > Then why the hell are you posting if there is no need to go > > into it again? > > It is extremely bad form to post asking for something > > without supplying > > details or at least a pointer to where they are (msgid's etc). > http://www.geocrawler.com/archives/3/159/2000/12/0/4775943/ There are other threads, of course, but this is the longest and contains all the technical information you may need. > > > There are other people who can fix it, but they cannot do > > anything if you > > refuse to supply all the precise details in an easy to access form. > I am willing to ship an offending fxp card to whoever offers to fix this problem. We have about 9 useless cards left, IIRC. The 10th is currently on David Greenman's desk. > > > If you are unwilling to do that, then stop bothering us! > > Indeed, I think Dennis could solve two problems by just dropping > FreeBSD right away. > Dennis seems to have a knack for rubbing everyone else the wrong way, David said he'd fix this and hasn't. We all know this, so let's please leave it at that. Let's separate the technical issues from the personal ones. I'd love to see this fixed and I offer all I can to help: hardware and testing time. If someone could detail the problem in highly technical terms this might trigger someone else to offer another piece of the puzzle. What does the message "unsupported PHY" mean? How would one go about tracking down the properties of the PHY? How does Linux/NetBSD/OpenBSD/Windows/Solaris solve this? What halfassed fixes or pointers do we have already? 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 Thu Mar 8 2:47:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ggong.baycis.com (ggong.baycis.com [209.133.107.121]) by hub.freebsd.org (Postfix) with ESMTP id 5F7FF37B71A for ; Thu, 8 Mar 2001 02:47:46 -0800 (PST) (envelope-from ggong@cal.alumni.berkeley.edu) Received: from GGONGW2K (adsl-64-166-95-42.dsl.sntc01.pacbell.net [64.166.95.42]) by ggong.baycis.com (8.11.2/8.11.2) with SMTP id f28AlIH95555; Thu, 8 Mar 2001 02:47:18 -0800 (PST) (envelope-from ggong@cal.alumni.berkeley.edu) Message-ID: <01c501c0a7bc$e770e640$2a5fa640@GGONGW2K> From: "Gilbert Gong" To: "Sergey Babkin" , "Luigi Rizzo" Cc: References: <200103071930.UAA28806@info.iet.unipi.it> <3AA6FF47.A6CD3DB3@bellatlantic.net> Subject: Re: if_fxp status? Date: Thu, 8 Mar 2001 02:45:32 -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.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe the 21143 is not discontinued. It got bought by intel, so they are now manufactured as Intel chips. The Kingston kne100tx uses the now-intel-manufactured chip. They're available for <$50 or quit a bit less if you buy bulk :) (ie www.warehouse.com) They've worked great for me. A quick search on the intel web site brings up such informative links as http://developer.intel.com/design/network/products/lan/controllers/21143.htm Gilbert ----- Original Message ----- From: "Sergey Babkin" To: "Luigi Rizzo" Cc: Sent: Wednesday, March 07, 2001 7:40 PM Subject: Re: if_fxp status? > Luigi Rizzo wrote: > > > Now, the 21143 (which is a pretty nice chip and has available > > documentation and a decent driver, "dc") is discontinued, but there > > are clones which work reasonably well (and are even cheaper, around > > $30 or so at compusa, i think netgear or linksys does one of these > > cards). I'd go with them. No multiport card, at least as far as i know. > > Could you tell the exact models ? I know that the SMC cards > and some others are using the same chip as well but apparently they > have some differences in some parts circuitry, so that they need > special support in the driver. So I wonder if you actually got > these Linksys and Netgear cards working with FreeBSD. > > -SB > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 5:52:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv13-poa.poa.terra.com.br (srv13-poa.poa.zaz.com.br [200.248.149.91]) by hub.freebsd.org (Postfix) with ESMTP id 467A437B718; Thu, 8 Mar 2001 05:51:56 -0800 (PST) (envelope-from rafael.tonin@terra.com.br) Received: from srv8-poa.poa.terra.com.br (srv8-poa.poa.terra.com.br [200.248.149.15]) by srv13-poa.poa.terra.com.br (8.9.3/8.9.3) with ESMTP id KAA12451; Thu, 8 Mar 2001 10:51:55 -0300 Received: from bohr (dl-tnt7-C8B01462.poa.terra.com.br [200.176.20.98]) by srv8-poa.poa.terra.com.br (8.11.0/8.11.1) with SMTP id f28Dpl200510; Thu, 8 Mar 2001 10:51:47 -0300 Message-ID: <003901c0a7d7$91b465e0$6214b0c8@bohr> From: "Rafael Tonin" To: Cc: Subject: Intel PRO/100+ PCI problem Date: Thu, 8 Mar 2001 10:56:26 -0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0036_01C0A7BE.6BD7BF20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0036_01C0A7BE.6BD7BF20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm having some problems on configuring my just purchased Intel PRO/100+ = PCI (reported by Intel as being P#: 689661-004). When booting, FreeBSD 4.2 reports: fxp0: at device 13.0 on pci0 fxp0: could not map memory Anyone knows how to get this card to work? Really Thanks, Rafael Tonin Below is a copy of my dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT 2000 jkh@bento.FreeBSD.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (267.60-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x634 Stepping =3D 4 = Features=3D0x80f9ff real memory =3D 268419072 (262128K bytes) config> di sn0 config> di lnc0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory =3D 257069056 (251044K bytes) Preloaded elf kernel "kernel" at 0xc0436000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc043609c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 = on pci0 pci1: on pcib2 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 = on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 10 at device = 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Microsoft Microsoft IntelliMouse\M-. Explorer, rev 1.10/1.14, addr = 2, iclass 3/1 ums0: 5 buttons and Z dir. pci0: (vendor=3D0x1102, dev=3D0x0002) at 9.0 pci0: (vendor=3D0x1102, dev=3D0x7002) at 9.1 fxp0: at device 13.0 on pci0 fxp0: could not map memory device_probe_and_attach: fxp0 attach returned 6 pcib1: on motherboard pci2: on pcib1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on = isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: MLC,PCL,PML plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio4: at port 0x3e8-0x3ef irq 5 on isa0 sio4: type 16550A ad0: 14324MB [29104/16/63] at ata0-master = UDMA66 afd0: 239MB [239/64/32] at ata0-slave = using PIO3 acd0: CDROM at ata1-master using PIO4 acd1: CD-RW at ata1-slave using = PIO4 Mounting root from ufs:/dev/ad0s2a ------=_NextPart_000_0036_01C0A7BE.6BD7BF20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I'm having some problems on configuring = my just=20 purchased Intel PRO/100+ PCI (reported by Intel as being P#:=20 689661-004).
 
When booting, FreeBSD 4.2 = reports:
 
fxp0: <Intel Pro 10/100B/100+ = Ethernet> at=20 device 13.0 on pci0
fxp0: could not map memory
 
Anyone knows how to get this card to=20 work?
 
Really Thanks,
 
Rafael Tonin
 
Below is a copy of my = dmesg:
 
Copyright (c) 1992-2000 The FreeBSD=20 Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, = 1992, 1993,=20 1994
 The Regents of the University of California. All rights=20 reserved.
FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT=20 2000
    jkh@be= nto.FreeBSD.org:/usr/src/sys/compile/GENERIC
Timecounter=20 "i8254"  frequency 1193182 Hz
CPU: Pentium II/Pentium II = Xeon/Celeron=20 (267.60-MHz 686-class CPU)
  Origin =3D "GenuineIntel"  Id = =3D=20 0x634  Stepping =3D 4
 =20 Features=3D0x80f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MC= A,CMOV,MMX>
real=20 memory  =3D 268419072 (262128K bytes)
config> di = sn0
config> di=20 lnc0
config> di ie0
config> di fe0
config> di=20 ed0
config> di cs0
config> di bt0
config> di=20 aic0
config> di aha0
config> di adv0
config> = q
avail memory=20 =3D 257069056 (251044K bytes)
Preloaded elf kernel "kernel" at=20 0xc0436000.
Preloaded userconfig_script "/boot/kernel.conf" at=20 0xc043609c.
Pentium Pro MTRR support enabled
md0: Malloc = disk
npx0:=20 <math processor> on motherboard
npx0: INT 16 = interface
pcib0:=20 <Host to PCI bridge> on motherboard
pci0: <PCI bus> on=20 pcib0
pcib2: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> = at=20 device 1.0 on pci0
pci1: <PCI bus> on pcib2
pci1: <NVidia = GeForce2 GTS graphics accelerator> at 0.0 irq 11
isab0: <VIA = 82C596B=20 PCI-ISA bridge> at device 4.0 on pci0
isa0: <ISA bus> on=20 isab0
atapci0: <VIA 82C596 ATA66 controller> port 0xd800-0xd80f = at=20 device 4.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 = irq 15=20 on atapci0
uhci0: <VIA 83C572 USB controller> port = 0xd400-0xd41f irq 10=20 at device 4.2 on pci0
usb0: <VIA 83C572 USB controller> on=20 uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, = rev=20 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self = powered
ums0:=20 Microsoft Microsoft IntelliMouse\M-. Explorer, rev 1.10/1.14, addr 2, = iclass=20 3/1
ums0: 5 buttons and Z dir.
pci0: <unknown card> = (vendor=3D0x1102,=20 dev=3D0x0002) at 9.0
pci0: <unknown card> (vendor=3D0x1102, = dev=3D0x7002) at=20 9.1
fxp0: <Intel Pro 10/100B/100+ Ethernet> at device 13.0 on=20 pci0
fxp0: could not map memory
device_probe_and_attach: fxp0 = attach=20 returned 6
pcib1: <Host to PCI bridge> on motherboard
pci2: = <PCI=20 bus> on pcib1
fdc0: <NEC 72065B or clone> at port = 0x3f0-0x3f5,0x3f7=20 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: = <1440-KB=20 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller = (i8042)>=20 at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 = on=20 atkbdc0
kbd0 at atkbd0
vga0: <Generic ISA VGA> at port = 0x3c0-0x3df=20 iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags = 0x100 on=20 isa0
sc0: VGA <16 virtual consoles, flags=3D0x300>
sio0 at = port=20 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at = port=20 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel = port> at=20 port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset = (ECP/EPP/PS2/NIBBLE) in=20 COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0: = IEEE1284=20 device found /NIBBLE/ECP
Probing for PnP devices on = ppbus0:
ppbus0:=20 <HEWLETT-PACKARD DESKJET 640C> MLC,PCL,PML
plip0: <PLIP = network=20 interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0:=20 Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
sio4: = <U.S.=20 Robotics 56K Voice INT> at port 0x3e8-0x3ef irq 5 on isa0
sio4: = type=20 16550A
ad0: 14324MB <QUANTUM FIREBALLlct10 15> [29104/16/63] at = ata0-master UDMA66
afd0: 239MB <IOMEGA ZIP 250 ATAPI Floppy>=20 [239/64/32] at ata0-slave using PIO3
acd0: CDROM <SONY CD-ROM = CDU4821>=20 at ata1-master using PIO4
acd1: CD-RW <Hewlett-Packard CD-Writer = Plus=20 8200> at ata1-slave using PIO4
Mounting root from=20 ufs:/dev/ad0s2a
------=_NextPart_000_0036_01C0A7BE.6BD7BF20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 6:20:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cdc.net (server1.cdc.net [207.244.0.12]) by hub.freebsd.org (Postfix) with SMTP id 3BE6A37B71A for ; Thu, 8 Mar 2001 06:20:43 -0800 (PST) (envelope-from mwade@cdc.net) Received: (qmail 22129 invoked from network); 8 Mar 2001 14:19:01 -0000 Received: from unknown (HELO net-ninja.com) (207.244.6.200) by server1.cdc.net with SMTP; 8 Mar 2001 14:19:01 -0000 Received: by net-ninja.com (Postfix, from userid 1000) id 99B436E8D0; Thu, 8 Mar 2001 09:18:59 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by net-ninja.com (Postfix) with ESMTP id 838A2176020; Thu, 8 Mar 2001 09:18:59 -0500 (EST) Date: Thu, 8 Mar 2001 09:18:59 -0500 (EST) From: Mike Wade X-Sender: mwade@net-ninja.com To: Luigi Rizzo Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp status? In-Reply-To: <200103080839.JAA35120@info.iet.unipi.it> 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, 8 Mar 2001, Luigi Rizzo wrote: > I could not find a NetGear with the tulip chipset or clone. FWIW I've used several NetGear PCI Ethernet cards with good results (and great pricing + availability): Netgear FA310-TX dc(4) / pn(4) driver Netgear FA311-TX sis(4) driver Netgear FA312-TX sis(4) driver --- Mike Wade (mwade@cdc.net) Chief Technical Officer CDC Internet, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 6:29:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id 57B1A37B719 for ; Thu, 8 Mar 2001 06:29:10 -0800 (PST) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f28ET8214009 for ; Thu, 8 Mar 2001 08:29:09 -0600 (CST) Message-Id: <200103081429.f28ET8214009@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: hackers@freebsd.org Subject: Re: if_fxp status? In-reply-to: Your message of "Thu, 08 Mar 2001 10:58:29 +0100." <59063B5B4D98D311BC0D0001FA7E4522026D7C92@l04.research.kpn.com> Date: Thu, 08 Mar 2001 08:29:08 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <59063B5B4D98D311BC0D0001FA7E4522026D7C92@l04.research.kpn.com>, "Ko ster, K.J." writes: >What does the message "unsupported PHY" mean? There's this gizmo that handles the actual physical network connection; it's called a PHY. It must be very expensive to make, and very cheap to design, because ethernet card vendors go through them in bundles. :) >How would one go about tracking down the properties of the PHY? One would be a large commercial organization capable of signing an NDA. :) >How does Linux/NetBSD/OpenBSD/Windows/Solaris solve this? I can't speak for all of the others; NetBSD may or may not have the PHY in question working. Can someone tell me exactly what it is? I can't leak source (probably), but I might be able to confirm whether or not BSD/OS has it working - and if not, I can ask the guy who does our driver about it, and he may be able to get docs. What PHY exactly is this? When was it first introduced? I can tell you that BSDi support isn't getting a whole lot of requests about it, so I *suspect* it's supported. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 7: 7: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mcp.csh.rit.edu (mcp.csh.rit.edu [129.21.60.9]) by hub.freebsd.org (Postfix) with ESMTP id 869B537B719 for ; Thu, 8 Mar 2001 07:07:00 -0800 (PST) (envelope-from jon@csh.rit.edu) Received: from fury.csh.rit.edu (fury.csh.rit.edu [129.21.60.5]) by mcp.csh.rit.edu (Postfix) with ESMTP id 762B11043; Thu, 8 Mar 2001 10:06:54 -0500 (EST) Received: by fury.csh.rit.edu (Postfix, from userid 37404) id 6D5362E159; Thu, 8 Mar 2001 10:06:43 -0500 (EST) Date: Thu, 8 Mar 2001 10:06:43 -0500 From: Jon Parise To: Blaz Zupan Cc: hackers@freebsd.org Subject: Re: PATCH: workaround for FreeBSD 4.2-STABLE (fwd) Message-ID: <20010308100642.A17330@csh.rit.edu> Mail-Followup-To: Blaz Zupan , hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: ; from blaz@amis.net on Thu, Mar 08, 2001 at 08:04:57AM +0100 X-Operating-System: SunOS 5.8 (sun4u) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 08, 2001 at 08:04:57AM +0100, Blaz Zupan wrote: > Anybody know which bug Wietse is talking about? http://marc.theaimsgroup.com/?l=postfix-users&m=98400011427323&w=2 -- Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 8:11:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from filk.iinet.net.au (syncopation-dns.iinet.net.au [203.59.24.29]) by hub.freebsd.org (Postfix) with SMTP id 9F83D37B71D for ; Thu, 8 Mar 2001 08:11:03 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 21876 invoked by uid 666); 8 Mar 2001 16:11:55 -0000 Received: from i003-228.nv.iinet.net.au (HELO elischer.org) (203.59.3.228) by mail.m.iinet.net.au with SMTP; 8 Mar 2001 16:11:55 -0000 Message-ID: <3AA7AEFB.8B8CC779@elischer.org> Date: Thu, 08 Mar 2001 08:10:35 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: hackers@freebsd.org, dg@freebsd.org, terry@freebsd.org, jkh@freebsd.org Subject: Unionfs and 4.x and sendfile() Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unionfs has been used by some people in simple configurations with some success, however sendfile() is apparently incompatible with it. this wasn't a problem until ftpd in -stable recently got upgraded to use sendfile(). How nullfs works in the same situation is not know at this time but may have similar problems. People have been using union mounts and nullfs mounts to populate parts of gaols. However the ftpds in these gaols cannot any more read files but instead send randon junk to the clients.. I know about the "here be dragons, slippery when wet" warnings but the change to 4.x ftpd has removed functionality that some people were using to provide service to customers. (let's just say they are worried). all other operations on the gaol seem to work fine. Julian -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 8:37:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 6A20237B719 for ; Thu, 8 Mar 2001 08:37:38 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id LAA74351; Thu, 8 Mar 2001 11:49:17 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010308114809.01ee3e60@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 08 Mar 2001 11:53:01 -0500 To: "Koster, K.J." , hackers@FreeBSD.ORG From: Dennis Subject: RE: if_fxp status? In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D7C92@l04.research.kpn. 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 At 04:58 AM 03/08/2001, Koster, K.J. wrote: >Dear All, > > > > > >> > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) > > >> > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) > > >:-) > > > > > > > its been discussed several times on this list. No need to > > > > go into it again. > > > > > > Then why the hell are you posting if there is no need to go > > > into it again? > > > It is extremely bad form to post asking for something > > > without supplying > > > details or at least a pointer to where they are (msgid's etc). If i regurgitate, then the flames will fly about "reposting". I chose the lower octane method to save gas. >I am willing to ship an offending fxp card to whoever offers to fix this >problem. We have about 9 useless cards left, IIRC. The 10th is currently on >David Greenman's desk. > > > > > > If you are unwilling to do that, then stop bothering us! > > > > Indeed, I think Dennis could solve two problems by just dropping > > FreeBSD right away. maybe the 1000+ companies that use our stuff to run their businesses would disagree with that. > > >Dennis seems to have a knack for rubbing everyone else the wrong way, David >said he'd fix this and hasn't. We all know this, so let's please leave it at >that. Let's separate the technical issues from the personal ones. I think maybe you need a nice vegetable cocktail. I recommend tomato/celery/carrot juice with a snip of parsley. Its very soothing. You'll live longer. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 8:41:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id AA4C337B719 for ; Thu, 8 Mar 2001 08:41:45 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id LAA74366; Thu, 8 Mar 2001 11:50:43 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010308115359.03707630@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 08 Mar 2001 11:54:26 -0500 To: Poul-Henning Kamp , Peter Wemm From: Dennis Subject: Re: if_fxp status? Cc: Matt Dillon , hackers@FreeBSD.ORG In-Reply-To: <19930.984032091@critter> References: 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 At 01:14 AM 03/08/2001, Poul-Henning Kamp wrote: >In message <200103080226.f282QLh83988@mobile.wemm.org>, Peter Wemm writes: > >Dennis wrote: > >> At 05:20 PM 03/07/2001, you wrote: > >> >: > >> >:The people involved know. > >> >: > >> > > >> > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) > >> > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) > >> > > >> > -Matt > >> > >> > >> its been discussed several times on this list. No need to go into it > again. > > > >Then why the hell are you posting if there is no need to go into it again? > >It is extremely bad form to post asking for something without supplying > >details or at least a pointer to where they are (msgid's etc). > > > >There are other people who can fix it, but they cannot do anything if you > >refuse to supply all the precise details in an easy to access form. > >If you are unwilling to do that, then stop bothering us! > >Indeed, I think Dennis could solve two problems by just dropping >FreeBSD right away. Another intelligent comment from PHK. Bravo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 8:46:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 2C04A37B71B for ; Thu, 8 Mar 2001 08:46:47 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id LAA74402; Thu, 8 Mar 2001 11:55:56 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010308115432.01ee0d60@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 08 Mar 2001 11:59:39 -0500 To: Poul-Henning Kamp From: Dennis Subject: Re: if_fxp status? Cc: Matt Dillon , hackers@FreeBSD.ORG In-Reply-To: <19930.984032091@critter> References: 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 At 01:14 AM 03/08/2001, Poul-Henning Kamp wrote: >In message <200103080226.f282QLh83988@mobile.wemm.org>, Peter Wemm writes: > >Dennis wrote: > >> At 05:20 PM 03/07/2001, you wrote: > >> >: > >> >:The people involved know. > >> >: > >> > > >> > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) > >> > Harrruummmmmmmmmmmmmmmmmmmmmmm. (Gong!) > >> > > >> > -Matt > >> > >> > >> its been discussed several times on this list. No need to go into it > again. > > > >Then why the hell are you posting if there is no need to go into it again? > >It is extremely bad form to post asking for something without supplying > >details or at least a pointer to where they are (msgid's etc). > > > >There are other people who can fix it, but they cannot do anything if you > >refuse to supply all the precise details in an easy to access form. > >If you are unwilling to do that, then stop bothering us! > >Indeed, I think Dennis could solve two problems by just dropping >FreeBSD right away. Why do I get flamed for expressing my concerns about a very important driver and PHK, who hasn't said one intelligent thing on the list in years, regularly makes inflammatory statements with no content whatsoever such as the above and on-one ever "disciplines" him? reminds me of an old george orwell novell.... Jordan? DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 8:50:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.krameria.net (mail.krameria.net [194.78.241.3]) by hub.freebsd.org (Postfix) with ESMTP id 38B0B37B71B for ; Thu, 8 Mar 2001 08:50:41 -0800 (PST) (envelope-from andy@techos.be) Received: from warp-core.skynet.be ([195.238.2.25] helo=Sarabi) by mail.krameria.net with asmtp (Exim 3.20 #1) id 14b3eW-0002OR-00 for freebsd-hackers@freebsd.org; Thu, 08 Mar 2001 17:52:36 +0100 From: "Andy De Petter" To: Subject: memory disk problem (mounted memory "hangs") Date: Thu, 8 Mar 2001 17:55:41 +0100 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have a machine, with 2Gb physical memory, of which I mount 512Mb as a filesystem (/dev/md0c). This partition is very heavily used, and the machine hangs after a certain amount of time, for no obvious reason. What I've found is this, to be configured during kernel compilation time: -- # # Set the number of PV entries per process. Increasing this can # stop panics related to heavy use of shared memory. However, that can # (combined with large amounts of physical memory) cause panics at # boot time due the kernel running out of VM space. # # If you're tweaking this, you might also want to increase the sysctls # "vm.v_free_min", "vm.v_free_reserved", and "vm.v_free_target". # # The value below is the one more than the default. # options "PMAP_SHPGPERPROC=201" -- Now, I have tried this, and set PMAP_SHPGPERPROC=400, and changed set "vm.v_free_reserved=1024" and "vm.v_free_min=1500", but still I have the same problem, that the machine hangs after a certain amount of time. I'm running FreeBSD 4.2-RELEASE. Is there anything else, I should take into account, or anything I should configure, to stop this from happening? Because once the mounted mdisk "hangs", the only way to unlock the machine, is to reboot it :( Thanks, -Andy -- "For nothing can seem foul to those that win." - Henry IV, Pt1, Act 5, Sc 1 *** DISCLAIMER *** This e-mail and any attachments thereto may contain information, which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by persons other than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer. Thank you for your cooperation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 8:59:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id D969437B719 for ; Thu, 8 Mar 2001 08:59:44 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id MAA74480 for ; Thu, 8 Mar 2001 12:11:26 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 08 Mar 2001 12:15:09 -0500 To: hackers@FreeBSD.ORG From: Dennis Subject: if_fxp - the real point 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 dont have time for weenie flame wars with people who are more interested in ignoring problems than fixing them. The point here seems very simple. The intel NICs are on a large number of MBs and the eepro100 is the most popular card on the market. So why is there vitually no maintainer for arguably the most important driver in the freebsd tree when there are maintainers for scads of obscure, must less used cards? freebsd touts a "core team" which provides "direction"...does the "direction" include letting important drivers fall out of maintenance in favor of some crappy netgear card that chokes at 3,000pps? Keeping mainstream FreeBSD releases up to date is more important then working on next years release. Otherwise you just have another linux. DB PS: Whatever happened to all of the "support" that BSDI was going to provide? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 9: 1:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hayseed.net (hayseed.net [207.181.249.194]) by hub.freebsd.org (Postfix) with ESMTP id B789637B71B for ; Thu, 8 Mar 2001 09:01:39 -0800 (PST) (envelope-from cnielsen@pobox.com) Received: from localhost (enkhyl@localhost) by hayseed.net (8.9.3/8.9.3) with ESMTP id IAA15453; Thu, 8 Mar 2001 08:57:23 -0800 X-Authentication-Warning: hayseed.net: enkhyl owned process doing -bs Date: Thu, 8 Mar 2001 08:57:23 -0800 (PST) From: Reply-To: To: Dennis Cc: Poul-Henning Kamp , Matt Dillon , Subject: Re: if_fxp status? In-Reply-To: <5.0.0.25.0.20010308115432.01ee0d60@mail.etinc.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've hesitated to be a part of this, but I can't stand by and watch someone be denigrated that I've both learned from and that has contributed huge amounts of code to the project. On Thu, 8 Mar 2001, Dennis wrote: > Why do I get flamed for expressing my concerns > about a very important driver and PHK, who hasn't > said one intelligent thing on the list in years, > regularly makes inflammatory statements with no > content whatsoever such as the above and on-one > ever "disciplines" him? reminds me of an old george > orwell novell.... PHK has contributed many intelligent and insightful posts in the few years I've been reading the lists. Can we stop with the personal attacks? It does no one any good. -- Christopher Nielsen - Metal-wielding pyro techie cnielsen@pobox.com "Any technology indistinguishable from magic is insufficiently advanced." --unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 9:16:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id 2EB1537B71A for ; Thu, 8 Mar 2001 09:16:00 -0800 (PST) (envelope-from rh@matriplex.com) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id JAA65721; Thu, 8 Mar 2001 09:15:45 -0800 (PST) (envelope-from rh@matriplex.com) Date: Thu, 8 Mar 2001 09:15:45 -0800 (PST) From: Richard Hodges To: Rafael Tonin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Intel PRO/100+ PCI problem In-Reply-To: <003901c0a7d7$91b465e0$6214b0c8@bohr> 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, 8 Mar 2001, Rafael Tonin wrote: > I'm having some problems on configuring my just purchased Intel > PRO/100+ PCI (reported by Intel as being P#: 689661-004). > > When booting, FreeBSD 4.2 reports: > > fxp0: at device 13.0 on pci0 > fxp0: could not map memory > > Anyone knows how to get this card to work? Go into your BIOS config and turn off the option for "PLUG & PLAY OS". It should be with the PCI menu. -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. Product Manager | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 9:20:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id 7464637B719 for ; Thu, 8 Mar 2001 09:20:02 -0800 (PST) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f28HK1201269 for ; Thu, 8 Mar 2001 11:20:02 -0600 (CST) Message-Id: <200103081720.f28HK1201269@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: hackers@freebsd.org Subject: Re: if_fxp - the real point In-reply-to: Your message of "Thu, 08 Mar 2001 12:15:09 EST." <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com> Date: Thu, 08 Mar 2001 11:20:01 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com>, Dennis writes: >PS: Whatever happened to all of the "support" that BSDI was going to provide? I have no doubt that the BSDi sales office would be happy to sell you a contract. For that matter, I believe they are quite happy to do funded development. Want the fxp driver fixed in FreeBSD? Contact your local sales critter, describe what you want done, get an estimate, and if you like the price, pay it. That's how other people with "thousands of customers" get key hardware support that's a bigger priority for them than it is for other people, and it's not hard. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 9:21:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bdr-xcon.matchlogic.com (mail.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 49E1937B71A for ; Thu, 8 Mar 2001 09:21:39 -0800 (PST) (envelope-from crandall@matchlogic.com) Received: by mail.matchlogic.com with Internet Mail Service (5.5.2653.19) id ; Thu, 8 Mar 2001 10:20:51 -0700 Message-ID: <5FE9B713CCCDD311A03400508B8B30130828E8B5@bdr-xcln.is.matchlogic.com> From: Charles Randall To: 'Richard Hodges' , Rafael Tonin Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: Intel PRO/100+ PCI problem Date: Thu, 8 Mar 2001 10:20:49 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If that is a solution, should the error message be changed to fxp0: could not map memory (Is BIOS "Plug & Play OS" diabled?) Charles -----Original Message----- From: Richard Hodges [mailto:rh@matriplex.com] Sent: Thursday, March 08, 2001 10:16 AM To: Rafael Tonin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Intel PRO/100+ PCI problem On Thu, 8 Mar 2001, Rafael Tonin wrote: > I'm having some problems on configuring my just purchased Intel > PRO/100+ PCI (reported by Intel as being P#: 689661-004). > > When booting, FreeBSD 4.2 reports: > > fxp0: at device 13.0 on pci0 > fxp0: could not map memory > > Anyone knows how to get this card to work? Go into your BIOS config and turn off the option for "PLUG & PLAY OS". It should be with the PCI menu. -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. Product Manager | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.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 Thu Mar 8 9:34:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 7A37637B719 for ; Thu, 8 Mar 2001 09:34:50 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f28HZrY01437; Thu, 8 Mar 2001 09:35:54 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103081735.f28HZrY01437@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point In-reply-to: Your message of "Thu, 08 Mar 2001 12:15:09 EST." <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Mar 2001 09:35:53 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The point here seems very simple. The intel NICs are on a large number of > MBs and the eepro100 is the most popular card on the market. So why is > there vitually no maintainer for arguably the most important driver in the > freebsd tree when there are maintainers for scads of obscure, must less > used cards? You appear to have a very wrong idea about how these things work. There's a maintainer for the fxp driver, who currently happens to be out of circulation. Nobody else has stepped up to take it on because obviously nobody is motivated to do the work. As for the rest; there's basically one maintainer for these "scads" of (not actually very) obscure cards - Bill Paul. > freebsd touts a "core team" which provides "direction"...does > the "direction" include letting important drivers fall out of maintenance > in favor of some crappy netgear card that chokes at 3,000pps? I have no idea what you think core should do about this. Are you going to fund a contractor to work on the driver? I didn't think so. What else are we supposed to do? > PS: Whatever happened to all of the "support" that BSDI was going to provide? Call BSDi (numbers on their website) and ask to speak to Gary Johnson (CEO) or Mark Garver (senior VP) and ask them yourself. If you get a useful answer, please tell the rest of us; especially me, since I burnt out trying to make it happen. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 9:46:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.tecc.co.uk (luggage.tecc.co.uk [193.128.6.129]) by hub.freebsd.org (Postfix) with SMTP id 67FCC37B719 for ; Thu, 8 Mar 2001 09:46:14 -0800 (PST) (envelope-from andy@tecc.co.uk) Received: from fw-smtp.tecc.co.uk [195.217.37.39] by relay.tecc.co.uk with esmtp (Exim 1.70 #1) id 14b4UM-0006ut-00; Thu, 8 Mar 2001 17:46:10 +0000 Received: from [195.217.37.155] (helo=southampton) by fw-smtp.tecc.co.uk with smtp (Exim 2.12 #3) id 14b4SK-0004kh-00 for hackers@FreeBSD.ORG; Thu, 8 Mar 2001 17:44:04 +0000 From: "Andy [TECC NOPS]" To: Subject: RE: if_fxp - the real point Date: Thu, 8 Mar 2001 17:50:48 -0000 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <200103081735.f28HZrY01437@mass.dis.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There's a maintainer for the fxp driver, who currently happens to be out > of circulation. Nobody else has stepped up to take it on because > obviously nobody is motivated to do the work. Would love to step up and produce a patch, just too busy at the mo working on other things. However, if this thread is still raging when I get some spare time I'd be happy to contib code. In the meantime, I'll just continue reading this cute conversation. Ak To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 9:53:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.krameria.net (mail.krameria.net [194.78.241.3]) by hub.freebsd.org (Postfix) with ESMTP id DEAF137B718 for ; Thu, 8 Mar 2001 09:53:31 -0800 (PST) (envelope-from andy@techos.be) Received: from warp-core.skynet.be ([195.238.2.25] helo=Sarabi) by mail.krameria.net with asmtp (Exim 3.20 #1) id 14b4dK-0002Tm-00 for freebsd-hackers@freebsd.org; Thu, 08 Mar 2001 18:55:26 +0100 From: "Andy De Petter" To: Subject: RE: memory disk problem (mounted memory "hangs") Date: Thu, 8 Mar 2001 18:58:31 +0100 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been able to reproduce this problem, with "yes >> /mnt/my_mdisk". After it grows 'till about 100Mb (which might be coincidance) used, it hangs again. Do I have to "reserve" memory, for my mdisk, and if so, with which sysctl parameters, and which values to give them, for 512Mb mdisk? -a > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Andy De Petter > Sent: donderdag 8 maart 2001 17:56 > To: freebsd-hackers@freebsd.org > Subject: memory disk problem (mounted memory "hangs") > > > > Hello, > > I have a machine, with 2Gb physical memory, of which I mount 512Mb as a > filesystem (/dev/md0c). This partition is very heavily used, and the > machine hangs after a certain amount of time, for no obvious reason. > > What I've found is this, to be configured during kernel compilation > time: > > -- > # > # Set the number of PV entries per process. Increasing this can > # stop panics related to heavy use of shared memory. However, that can > # (combined with large amounts of physical memory) cause panics at > # boot time due the kernel running out of VM space. > # > # If you're tweaking this, you might also want to increase the sysctls > # "vm.v_free_min", "vm.v_free_reserved", and "vm.v_free_target". > # > # The value below is the one more than the default. > # > options "PMAP_SHPGPERPROC=201" > -- > > Now, I have tried this, and set PMAP_SHPGPERPROC=400, and changed set > "vm.v_free_reserved=1024" and "vm.v_free_min=1500", but still I have the > same problem, that the machine hangs after a certain amount of time. > > I'm running FreeBSD 4.2-RELEASE. > > Is there anything else, I should take into account, or anything I should > configure, to stop this from happening? Because once the mounted mdisk > "hangs", the only way to unlock the machine, is to reboot it :( > > Thanks, > > -Andy > > -- > "For nothing can seem foul to those that win." > - Henry IV, Pt1, Act 5, Sc 1 > > *** DISCLAIMER *** > This e-mail and any attachments thereto may contain information, which > is confidential and/or protected by intellectual property rights and > are intended for the sole use of the recipient(s) named above. Any use > of the information contained herein (including, but not limited to, > total or partial reproduction, communication or distribution in any > form) by persons other than the designated recipient(s) is prohibited. > If you have received this e-mail in error, please notify the sender > either by telephone or by e-mail and delete the material from any > computer. Thank you for your cooperation. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 11:28:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 9EE6D37B718; Thu, 8 Mar 2001 11:28:33 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id OAA75253; Thu, 8 Mar 2001 14:40:14 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010308135349.02818a90@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 08 Mar 2001 14:43:56 -0500 To: Mike Smith From: Dennis Subject: Re: if_fxp - the real point Cc: hackers@FreeBSD.ORG In-Reply-To: <200103081735.f28HZrY01437@mass.dis.org> References: 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 At 12:35 PM 03/08/2001, Mike Smith wrote: > > > > The point here seems very simple. The intel NICs are on a large number of > > MBs and the eepro100 is the most popular card on the market. So why is > > there vitually no maintainer for arguably the most important driver in the > > freebsd tree when there are maintainers for scads of obscure, must less > > used cards? > >You appear to have a very wrong idea about how these things work. > >There's a maintainer for the fxp driver, who currently happens to be out >of circulation. Nobody else has stepped up to take it on because >obviously nobody is motivated to do the work. > >As for the rest; there's basically one maintainer for these "scads" of >(not actually very) obscure cards - Bill Paul. maybe commercial vendors would be willing to fund some freebsd projects if there was a positive relationship. And DG has been MIA for a long time, not just recently. The last time the fxp driver was broken i found the fix and pointed him at the code. I guess I'll have to fix it this time also, as if maintaining drivers for 6 serial cards and the bwmgr isnt enough for me to do. Maybe I'll sell it this time. :-) > > PS: Whatever happened to all of the "support" that BSDI was going to > provide? > >Call BSDi (numbers on their website) and ask to speak to Gary Johnson >(CEO) or Mark Garver (senior VP) and ask them yourself. If you get a >useful answer, please tell the rest of us; especially me, since I burnt >out trying to make it happen. Ive spoken with Mr Johnson several times. hes the biggest reason that BSDI is what it is. Amazing that hes still there. He has no concept of what the market wants. First he wanted to challenge microsoft (at similar prices) for the server market now he wants to be redhat. funny guy. So what is the "relationship" that was announced? If they dont provide support or funds, what do they do? DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 11:29:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 3180237B719 for ; Thu, 8 Mar 2001 11:29:45 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id OAA75267; Thu, 8 Mar 2001 14:41:22 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010308144445.0281f070@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 08 Mar 2001 14:45:03 -0500 To: "Andy [TECC NOPS]" , From: Dennis Subject: RE: if_fxp - the real point In-Reply-To: References: <200103081735.f28HZrY01437@mass.dis.org> 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 At 12:50 PM 03/08/2001, Andy [TECC NOPS] wrote: > > There's a maintainer for the fxp driver, who currently happens to be out > > of circulation. Nobody else has stepped up to take it on because > > obviously nobody is motivated to do the work. > >Would love to step up and produce a patch, just too busy at the mo >working on other things. However, if this thread is still raging >when I get some spare time I'd be happy to contib code. > >In the meantime, I'll just continue reading this cute conversation. "cuteness" is in the eye of the beholder :-) DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 11:32:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 993B837B718 for ; Thu, 8 Mar 2001 11:32:52 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id OAA75284; Thu, 8 Mar 2001 14:44:31 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010308144541.0281a980@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 08 Mar 2001 14:48:12 -0500 To: seebs@plethora.net (Peter Seebach), hackers@FreeBSD.ORG From: Dennis Subject: Re: if_fxp - the real point In-Reply-To: <200103081720.f28HK1201269@guild.plethora.net> References: 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 At 12:20 PM 03/08/2001, Peter Seebach wrote: >In message <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com>, Dennis writes: > >PS: Whatever happened to all of the "support" that BSDI was going to > provide? > >I have no doubt that the BSDi sales office would be happy to sell you a >contract. For that matter, I believe they are quite happy to do funded >development. Want the fxp driver fixed in FreeBSD? Contact your local sales >critter, describe what you want done, get an estimate, and if you like the >price, pay it. That's how other people with "thousands of customers" get >key hardware support that's a bigger priority for them than it is for other >people, and it's not hard. No. Keeping supported drivers up to date is part of the business of distributing an OS. Thats what "supported" implies. The driver is out of date. Noone is looking for a feature here. We just want it to work. >-s > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 11:37:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sentry.gw.tislabs.com (sentry.gw.tislabs.com [192.94.214.100]) by hub.freebsd.org (Postfix) with ESMTP id 261CB37B718 for ; Thu, 8 Mar 2001 11:37:53 -0800 (PST) (envelope-from stevek@tislabs.com) Received: by sentry.gw.tislabs.com; id OAA20884; Thu, 8 Mar 2001 14:41:22 -0500 (EST) Received: from clipper.gw.tislabs.com(10.33.1.2) by sentry.gw.tislabs.com via smap (V5.5) id xma020880; Thu, 8 Mar 01 14:40:25 -0500 Received: from magneto.va.tislabs.com (IDENT:root@magneto.va.tislabs.com [192.168.10.131]) by clipper.gw.tislabs.com (8.9.3/8.9.1) with ESMTP id OAA19258 for ; Thu, 8 Mar 2001 14:36:23 -0500 (EST) Received: from localhost (stevek@localhost) by magneto.va.tislabs.com (8.9.3/8.9.3) with ESMTP id OAA09609 for ; Thu, 8 Mar 2001 14:36:22 -0500 Date: Thu, 8 Mar 2001 14:36:22 -0500 (EST) From: skiernan@nai.com X-Sender: stevek@magneto.va.tislabs.com To: hackers@FreeBSD.ORG Subject: Re: if_fxp status? In-Reply-To: <3AA714F3.E28037B5@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 Wed, 7 Mar 2001, Wes Peters wrote: > Sergey Babkin wrote: > > > > Luigi Rizzo wrote: > > > > > Now, the 21143 (which is a pretty nice chip and has available > > > documentation and a decent driver, "dc") is discontinued, but there > > > are clones which work reasonably well (and are even cheaper, around > > > $30 or so at compusa, i think netgear or linksys does one of these > > > cards). I'd go with them. No multiport card, at least as far as i know. > > > > Could you tell the exact models ? I know that the SMC cards > > and some others are using the same chip as well but apparently they > > have some differences in some parts circuitry, so that they need > > special support in the driver. So I wonder if you actually got > > these Linksys and Netgear cards working with FreeBSD. > > NetGear FA310TX. Yes, I have several working under FreeBSD and OpenBSD. Actually, the FA310TX comes in a couple of different forms. One with the Tulip chipset and another with PNIC, I believe. It seems that they changed chipsets partway into the life of the product code for the card. -- Stephen J. Kiernan NAI Labs @ PGP, Inc. skiernan@nai.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 11:38:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 1FEA637B718 for ; Thu, 8 Mar 2001 11:38:19 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id OAA75313; Thu, 8 Mar 2001 14:47:54 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010308144941.0281d770@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 08 Mar 2001 14:51:36 -0500 To: From: Dennis Subject: Re: if_fxp status? Cc: Poul-Henning Kamp , Matt Dillon , In-Reply-To: References: <5.0.0.25.0.20010308115432.01ee0d60@mail.etinc.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 At 11:57 AM 03/08/2001, cnielsen@pobox.com wrote: >I've hesitated to be a part of this, but I can't stand >by and watch someone be denigrated that I've both >learned from and that has contributed huge amounts of >code to the project. too bad you dont consider contributions to users of freebsd that arent free. The fact that they are willing to pay for those contributions is de facto evidence that they are of great value. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 12: 3:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id 9490F37B719 for ; Thu, 8 Mar 2001 12:03:19 -0800 (PST) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.9.0/8.8.7) with ESMTP id UAA18357 for ; Thu, 8 Mar 2001 20:03:18 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Thu, 8 Mar 2001 20:03:17 +0000 (GMT) From: "E.B. Dreger" To: hackers@FreeBSD.ORG Subject: Re: if_fxp status? 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 > Date: Thu, 8 Mar 2001 14:36:22 -0500 (EST) > From: skiernan@nai.com > > Actually, the FA310TX comes in a couple of different forms. One with > the Tulip chipset and another with PNIC, I believe. It seems that they > changed chipsets partway into the life of the product code for the card. IIRC, Rev. A is Tulip, B is ???, C is PNIC, D is Netgear's own. My memory is fuzzy on this, and I have no NG cards handy, but I think that the progression has been something like that. Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division E-Mail: eddy@everquick.net Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 12: 8: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from black.purplecat.net (ns1.purplecat.net [209.16.228.148]) by hub.freebsd.org (Postfix) with ESMTP id C3CF737B719 for ; Thu, 8 Mar 2001 12:08:00 -0800 (PST) (envelope-from peter@black.purplecat.net) Received: from localhost (peter@localhost) by black.purplecat.net (8.8.8/8.8.8) with ESMTP id PAA28494 for ; Thu, 8 Mar 2001 15:10:23 -0500 (EST) (envelope-from peter@black.purplecat.net) Date: Thu, 8 Mar 2001 15:10:23 -0500 (EST) From: Peter Brezny To: freebsd-hackers@freebsd.org Subject: mini kernel compile problem with twe0 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 trying to compile a mini kernel (to fit on a backup flopy disk) for a system with the 3ware escalade 6200 controller in it. I trimmed down the kernel config file, aparently too much. I don't know what i'm missing. I've provided my config file and some of the error output. Thanks in advance. pb machine i386 cpu I586_CPU cpu I686_CPU ident MINI maxusers 5 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options CD9660 #ISO 9660 Filesystem options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor device isa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives # RAID controllers device twe # 3ware Escalade # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # PCI Ethernet NICs. device vx # 3Com 3c590, 3c595 (``Vortex'') # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wp ointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/dev/twe/twe.c In file included from /usr/src/sys/dev/twe/twe.c:37: /usr/src/sys/dev/twe/twevar.h:243: warning: `struct bio' declared inside parameter list /usr/src/sys/dev/twe/twevar.h:243: warning: its scope is only this definition or declaration, w hich is probably not what you want. /usr/src/sys/dev/twe/twevar.h: In function `twe_enqueue_bio': /usr/src/sys/dev/twe/twevar.h:248: warning: passing arg 2 of `bufq_insert_tail' from incompatib le pointer type /usr/src/sys/dev/twe/twevar.h: In function `twe_dequeue_bio': /usr/src/sys/dev/twe/twevar.h:260: warning: assignment from incompatible pointer type /usr/src/sys/dev/twe/twevar.h:261: warning: passing arg 2 of `bufq_remove' from incompatible po inter type /usr/src/sys/dev/twe/twe.c: In function `twe_startio': /usr/src/sys/dev/twe/twe.c:347: warning: assignment from incompatible pointer type /usr/src/sys/dev/twe/twe.c:352: warning: passing arg 2 of `twe_enqueue_bio' from incompatible p ointer type /usr/src/sys/dev/twe/twe.c: In function `twe_wait_status': /usr/src/sys/dev/twe/twe.c:1134: warning: implicit declaration of function `DELAY' /usr/src/sys/dev/twe/twe.c: At top level: /usr/src/sys/dev/twe/twe.c:720: warning: `twe_set_param_1' defined but not used /usr/src/sys/dev/twe/twe.c:726: warning: `twe_set_param_2' defined but not used /usr/src/sys/dev/twe/twe.c:732: warning: `twe_set_param_4' defined but not used /usr/src/sys/dev/twe/twe.c:99: warning: `twe_request_qlen' declared `static' but never defined cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wp ointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/dev/twe/twe_freebsd.c In file included from /usr/src/sys/dev/twe/twe_freebsd.c:44: /usr/src/sys/dev/twe/twevar.h:243: warning: `struct bio' declared inside parameter list /usr/src/sys/dev/twe/twevar.h:243: warning: its scope is only this definition or declaration, w hich is probably not what you want. /usr/src/sys/dev/twe/twevar.h: In function `twe_enqueue_bio': /usr/src/sys/dev/twe/twevar.h:248: warning: passing arg 2 of `bufq_insert_tail' from incompatib le pointer type To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 12:12: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns0.sitesnow.com (ns0.sitesnow.com [63.166.182.130]) by hub.freebsd.org (Postfix) with ESMTP id B55BC37B718 for ; Thu, 8 Mar 2001 12:11:58 -0800 (PST) (envelope-from gskouby@ns0.sitesnow.com) Received: from gskouby by ns0.sitesnow.com with local (Exim 3.16 #2) id 14b6lQ-000O1D-00; Thu, 08 Mar 2001 15:11:56 -0500 Date: Thu, 8 Mar 2001 15:11:56 -0500 From: Greg Skouby To: Dennis Cc: hackers@freebsd.org Subject: Re: if_fxp - the real point Message-ID: <20010308151156.A92103@sitesnow.com> References: <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com>; from dennis@etinc.com on Thu, Mar 08, 2001 at 12:15:09PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I know this doesn't belong on -hackers so I apologize in advance. However, it seems like the right time and place to ask with the conversation going on. How *broke* is the if_fxp driver? We have them onboard in a handful of pretty low traffic dell machines and have them in a dell machine that pushes a Mb/sec with absolutely no problems at all. So what exactly are you advocating Dennis? Should we avoid them at all costs and go with something else or just use them and hope they don't break? Thanks. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 12:37:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 4F63037B718 for ; Thu, 8 Mar 2001 12:37:24 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id E50945D38; Thu, 8 Mar 2001 21:37:22 +0100 (CET) Date: Thu, 8 Mar 2001 21:37:22 +0100 From: Jesper Skriver To: Matt Dillon Cc: Dan Phoenix , freebsd-hackers@FreeBSD.ORG Subject: Re: systat -vmstat or iostat IO help Message-ID: <20010308213722.A83857@skriver.dk> References: <200103060208.f2628PT49635@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103060208.f2628PT49635@earth.backplane.com>; from dillon@earth.backplane.com on Mon, Mar 05, 2001 at 06:08:25PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 05, 2001 at 06:08:25PM -0800, Matt Dillon wrote: > > :I am trying to figure out corelation between Inactive and Free then. > :Inact would be unused ram right? > :Free would be what how much of Active is being used? So what you are > :saying is if there is to much free then alot of active pages are being > :killed for some reason...as seen in error logs etc? ....just trying to get > :a quick overview of what a good accessment that was...never thought of > :that. > > 'free' (from systat -vm or top) is all that matters in your case. > Active/Inactive/Cache are best simply added together. Their > individual values will depend heavily on the load on the machine > because the VM system doesn't bother to keep things in their > proper queues if the memory load is low. Could you please give a pointer to a description of the meaning of Active, Inactive and Cache, on a machine I see this Mem: 138M Active, 661M Inact, 114M Wired, 48M Cache, 112M Buf, 44M Free Swap: 1612M Total, 16K Used, 1612M Free Yes I know it has too much memory, but I'm surprised why more isn't used for disk caching .... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 12:44: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.dvart.com (mail.dvart.com [64.79.2.12]) by hub.freebsd.org (Postfix) with ESMTP id B67F137B718 for ; Thu, 8 Mar 2001 12:44:00 -0800 (PST) (envelope-from bschwand@dvart.com) Received: from dvart.com (pipin.dvart.com [64.79.2.4]) by mail.dvart.com (Postfix) with ESMTP id 93DD3CCE6 for ; Thu, 8 Mar 2001 12:42:22 +0000 (GMT) Message-ID: <3AA7EF0B.434B8D8F@dvart.com> Date: Thu, 08 Mar 2001 12:43:55 -0800 From: bruno schwander X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: examining the environment References: <200103060208.f2628PT49635@earth.backplane.com> <20010308213722.A83857@skriver.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everybody, How can I examine an other process environment ? I have a daemon that needs to do something according to an environment variable set in a different process. Can I open an other process and lookup environment variables set in his space ? bruno ########################################################################### Bruno Schwander Senior Software Engineer Worldgate Communications, Inc email: bschwand@dvart.com ############################################################################ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 13: 4: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id BF6BC37B719 for ; Thu, 8 Mar 2001 13:03:57 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f28L3mI27539; Thu, 8 Mar 2001 13:03:48 -0800 Date: Thu, 8 Mar 2001 13:03:48 -0800 From: Brooks Davis To: Greg Skouby Cc: Dennis , hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point Message-ID: <20010308130348.C23640@Odin.AC.HMC.Edu> References: <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com> <20010308151156.A92103@sitesnow.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ABTtc+pdwF7KHXCz" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010308151156.A92103@sitesnow.com>; from gskouby@sitesnow.com on Thu, Mar 08, 2001 at 03:11:56PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ABTtc+pdwF7KHXCz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 08, 2001 at 03:11:56PM -0500, Greg Skouby wrote: > I know this doesn't belong on -hackers so I apologize in advance. However, > it seems like the right time and place to ask with the conversation going > on. How *broke* is the if_fxp driver? We have them onboard in a handful > of pretty low traffic dell machines and have them in a dell machine=20 > that pushes a Mb/sec with absolutely no problems at all. So what exactly > are you advocating Dennis? Should we avoid them at all costs and go with > something else or just use them and hope they don't break? If they work for you then the primary problem Dennis is complaining about doesn't effect you since you have a supported PHYs. Frankly, if you're NIC is doing what you want don't worry about it. If it becomes a problem, the most expensive 10/100 nic you could possiably buy is less the $100 bucks so worry about it then. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --ABTtc+pdwF7KHXCz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6p/OzXY6L6fI4GtQRArzPAJ0QW95QODksPt57dgJqm+wFlPu+nwCgmLmQ eWVxmo5WHcE3iuFpFD2c6KY= =Ii8X -----END PGP SIGNATURE----- --ABTtc+pdwF7KHXCz-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 13: 4:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv13-poa.poa.terra.com.br (srv13-poa.poa.zaz.com.br [200.248.149.91]) by hub.freebsd.org (Postfix) with ESMTP id C2D4D37B719 for ; Thu, 8 Mar 2001 13:04:51 -0800 (PST) (envelope-from rafael.tonin@terra.com.br) Received: from srv7-poa.poa.terra.com.br (srv7-poa.poa.terra.com.br [200.248.149.123]) by srv13-poa.poa.terra.com.br (8.9.3/8.9.3) with ESMTP id SAA18542; Thu, 8 Mar 2001 18:04:44 -0300 Received: from bohr (dl-tnt2-C8B00A83.poa.terra.com.br [200.176.10.131]) by srv7-poa.poa.terra.com.br (8.11.0/8.11.1) with SMTP id f28L4g721567; Thu, 8 Mar 2001 18:04:43 -0300 Message-ID: <004401c0a814$0caf4800$830ab0c8@bohr> From: "Rafael Tonin" To: "Richard Hodges" Cc: References: Subject: Re: Intel PRO/100+ PCI problem Date: Thu, 8 Mar 2001 18:09:21 -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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It worked!! Really Thanks for your assistance. Rafael Tonin ----- Original Message ----- From: "Richard Hodges" To: "Rafael Tonin" Cc: Sent: Thursday, March 08, 2001 2:15 PM Subject: Re: Intel PRO/100+ PCI problem > On Thu, 8 Mar 2001, Rafael Tonin wrote: > > > I'm having some problems on configuring my just purchased Intel > > PRO/100+ PCI (reported by Intel as being P#: 689661-004). > > > > When booting, FreeBSD 4.2 reports: > > > > fxp0: at device 13.0 on pci0 > > fxp0: could not map memory > > > > Anyone knows how to get this card to work? > > Go into your BIOS config and turn off the option > for "PLUG & PLAY OS". It should be with the PCI menu. > > -Richard > > ------------------------------------------- > Richard Hodges | Matriplex, inc. > Product Manager | 769 Basque Way > rh@matriplex.com | Carson City, NV 89706 > 775-886-6477 | www.matriplex.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 13:39:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 7E95637B71F for ; Thu, 8 Mar 2001 13:39:09 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f28LXTH31771; Thu, 8 Mar 2001 13:33:30 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: dennis@etinc.com Cc: phk@critter.freebsd.dk, dillon@earth.backplane.com, hackers@FreeBSD.ORG Subject: Re: if_fxp status? In-Reply-To: <5.0.0.25.0.20010308115432.01ee0d60@mail.etinc.com> References: <19930.984032091@critter> <5.0.0.25.0.20010308115432.01ee0d60@mail.etinc.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010308133329U.jkh@osd.bsdi.com> Date: Thu, 08 Mar 2001 13:33:29 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 35 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Dennis Subject: Re: if_fxp status? Date: Thu, 08 Mar 2001 11:59:39 -0500 > Why do I get flamed for expressing my concerns about a very important > driver and PHK, who hasn't said one intelligent thing on the list in years, > regularly makes inflammatory statements with no content whatsoever such as > the above and on-one ever "disciplines" him? reminds me of an old george > orwell novell.... > > Jordan? I do think that many of the responses to this have been rather inappropriate and only serve to fan rather than quench the flames. You don't exactly have a reputation for being Mister Tact, of course, and that leads some to go into knee-jerk reaction mode whenever they see your name on the From line, but that still doesn't explain the lack of answers to your and other people's questions about the fxp driver's current status. Someone in this thread even donated equipment and is now quite understandably waiting for some sort of status report on it. All that said, David's father died very recently and he's still working on all the issues of resolving the estate, so he can also obviously be forgiven a certain lack of responsiveness on this. I know that if I'd just lost my dad, an ethernet card driver would be very near the last thing I'd be immediately concerned with. Perhaps someone else would like to take over maintenance of the fxp driver for awhile? That would be the reasonable and logical thing to do, and if they do a good job of it DG might even be inclined to just leave it in their hands permanently - I'm sure he has a lot on his plate these days as it is. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 13:43:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id F335A37B718 for ; Thu, 8 Mar 2001 13:43:47 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f28LgtH31827; Thu, 8 Mar 2001 13:42:56 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: dennis@etinc.com Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point In-Reply-To: <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com> References: <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010308134255L.jkh@osd.bsdi.com> Date: Thu, 08 Mar 2001 13:42:55 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 43 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Dennis Subject: if_fxp - the real point Date: Thu, 08 Mar 2001 12:15:09 -0500 > I dont have time for weenie flame wars with people who are more interested > in ignoring problems than fixing them. Well, there are different kinds of weenie flame wars. Some come from people who are more interested in ignoring problems than fixing them. Others come from people who are more interested in flaming about problems than fixing them. Both are equally destructive and fail to address the real problem, which is fixing them. This being a volunteer-driven project, each and every one of us here is free to roll up their sleeves and fix a problem rather than simply firing off emails in all directions taking people to task for failing to do what we should be doing ourselves. Arguments about lack of time or energy also cut both ways - you can't argue that someone else should find extra time to address an issue near and dear to your heart out of one side of your mouth and then say that you yourself have no time out of the other side. > The point here seems very simple. The intel NICs are on a large number of > MBs and the eepro100 is the most popular card on the market. So why is > there vitually no maintainer for arguably the most important driver in the > freebsd tree when there are maintainers for scads of obscure, must less > used cards? freebsd touts a "core team" which provides "direction"...does > the "direction" include letting important drivers fall out of maintenance > in favor of some crappy netgear card that chokes at 3,000pps? You seem to be rather seriously deluded about the whole open source process and I find that surprising given the length of time you've been buzzing around here. Core doesn't and cannot "demand" that some maintainer come forward or insist that something be actively maintained when there's nobody interested in doing so. Perhaps if you wanted to endow a "NIC maintainer's chair" at FreeBSD University here, we could hire someone to do it, but otherwise we're just as subject to the whims of volunteerism as you are, Dennis. Why don't you volunteer to do it? If you argue that you don't have the time or interest, then you've pretty much answered all your own questions and this entire thread is particularly pointless. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 13:45:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 5A2FD37B718 for ; Thu, 8 Mar 2001 13:45:15 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f28LiNH31839; Thu, 8 Mar 2001 13:44:23 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: dennis@etinc.com Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point In-Reply-To: <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com> References: <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010308134423I.jkh@osd.bsdi.com> Date: Thu, 08 Mar 2001 13:44:23 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 7 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > PS: Whatever happened to all of the "support" that BSDI was going to provide? It's paid support. BSDi is a company, just like you. You want to buy a contract, we'll sell you one. Or would you just prefer to stand on the doorstep bitching in order to see yourself in print? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 14: 5:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 4CC8A37B718 for ; Thu, 8 Mar 2001 14:05:11 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f28M4CH31971; Thu, 8 Mar 2001 14:04:12 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: gskouby@sitesnow.com Cc: dennis@etinc.com, hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point In-Reply-To: <20010308151156.A92103@sitesnow.com> References: <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com> <20010308151156.A92103@sitesnow.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010308140412P.jkh@osd.bsdi.com> Date: Thu, 08 Mar 2001 14:04:12 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 6 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG They work fine, it's just the newer cards that Dennis is having problems with. I have about 10 cards using the fxp driver here now and I fully expect them to work well into the future. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 14:20: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 5781C37B718 for ; Thu, 8 Mar 2001 14:20:03 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f28MHeZ91216; Thu, 8 Mar 2001 16:17:40 -0600 (CST) (envelope-from jlemon) Date: Thu, 8 Mar 2001 16:17:40 -0600 (CST) From: Jonathan Lemon Message-Id: <200103082217.f28MHeZ91216@prism.flugsvamp.com> To: jkh@osd.bsdi.com, hackers@freebsd.org Subject: Re: if_fxp status? X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Perhaps someone else would like to take over maintenance of the fxp >driver for awhile? That would be the reasonable and logical thing to >do, and if they do a good job of it DG might even be inclined to just >leave it in their hands permanently - I'm sure he has a lot on his >plate these days as it is. I umm... volunteer? (that is, for everyone except Dennis; he obviously has the situation well under control at this point, and doesn't need any assistance). -- Jonathan (for those with broken sarcasm detectors, add smileys as appropriate) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 15: 2:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from taupo.cs.waikato.ac.nz (taupo.cs.waikato.ac.nz [130.217.241.30]) by hub.freebsd.org (Postfix) with ESMTP id BF90037B718 for ; Thu, 8 Mar 2001 15:02:33 -0800 (PST) (envelope-from joerg@taupo.cs.waikato.ac.nz) Received: (from joerg@localhost) by taupo.cs.waikato.ac.nz (8.11.1/8.11.1) id f28N2Cr88159; Fri, 9 Mar 2001 12:02:12 +1300 (NZDT) (envelope-from joerg) Date: Fri, 9 Mar 2001 12:02:12 +1300 From: Joerg Micheel To: freebsd-hackers@freebsd.org Cc: joerg@cs.waikato.ac.nz Subject: Trouble with quotas on FreeBSD 4.2-STABLE Message-ID: <20010309120212.A49897@cs.waikato.ac.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: Dept of Computer Science, University of Waikato, Hamilton, New Zealand Project: WAND - Waikato Applied Network Dynamics, DAG Operating-System: ... powered by FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running a system with a 50GB /home drive. One user is experiencing inconsistencies, for him the system reports being over disk quota. du -sk reports 1.7GB utilization, quota reports 5.2GB. I've been checking the entire drive for files that belong to this user, same result. I have turned off quota, rerun quotacheck. It reports inconsistencies, but minor, does not change the big picture that this user is over quota. Soft limits are set to 5GB, hard to 10GB for all users on this drive. Thank you for any hints. Joerg -- Joerg B. Micheel Email: WAND and NLANR MOAT Email: The University of Waikato, CompScience Phone: +64 7 8384794 Private Bag 3105 Fax: +64 7 8585095 Hamilton, New Zealand Plan: PMA, TINE and the DAG's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 15:15:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 1EB0B37B719 for ; Thu, 8 Mar 2001 15:15:24 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f28NEKH32284; Thu, 8 Mar 2001 15:14:20 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: jlemon@flugsvamp.com Cc: hackers@freebsd.org Subject: Re: if_fxp status? In-Reply-To: <200103082217.f28MHeZ91216@prism.flugsvamp.com> References: <200103082217.f28MHeZ91216@prism.flugsvamp.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010308151420U.jkh@osd.bsdi.com> Date: Thu, 08 Mar 2001 15:14:20 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 13 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Jonathan Lemon Subject: Re: if_fxp status? Date: Thu, 8 Mar 2001 16:17:40 -0600 (CST) > I umm... volunteer? (that is, for everyone except Dennis; he obviously > has the situation well under control at this point, and doesn't need > any assistance). That's great! I think we can assume that David is reading this discussion if he's available and wants to comment, and if he's not then the point is somewhat moot. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 17:26:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id C250F37B719 for ; Thu, 8 Mar 2001 17:26:51 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f291QLO05885; Thu, 8 Mar 2001 17:26:21 -0800 (PST) (envelope-from dillon) Date: Thu, 8 Mar 2001 17:26:21 -0800 (PST) From: Matt Dillon Message-Id: <200103090126.f291QLO05885@earth.backplane.com> To: Jesper Skriver Cc: Dan Phoenix , freebsd-hackers@FreeBSD.ORG Subject: Re: systat -vmstat or iostat IO help References: <200103060208.f2628PT49635@earth.backplane.com> <20010308213722.A83857@skriver.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Mon, Mar 05, 2001 at 06:08:25PM -0800, Matt Dillon wrote: :> :> :I am trying to figure out corelation between Inactive and Free then. :> :Inact would be unused ram right? :> :Free would be what how much of Active is being used? So what you are :> :saying is if there is to much free then alot of active pages are being :> :killed for some reason...as seen in error logs etc? ....just trying to get :> :a quick overview of what a good accessment that was...never thought of :> :that. :> :> 'free' (from systat -vm or top) is all that matters in your case. :> Active/Inactive/Cache are best simply added together. Their :> individual values will depend heavily on the load on the machine :> because the VM system doesn't bother to keep things in their :> proper queues if the memory load is low. : :Could you please give a pointer to a description of the meaning of :Active, Inactive and Cache, on a machine I see this : :Mem: 138M Active, 661M Inact, 114M Wired, 48M Cache, 112M Buf, 44M Free :Swap: 1612M Total, 16K Used, 1612M Free : :Yes I know it has too much memory, but I'm surprised why more isn't used :for disk caching .... : :/Jesper : :-- :Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 It will use all available memory for disk caching if possible, but it only caches things you've accessed at least once so I would say you simply haven't accessed more then 650MB or so worth of file data. Active This queue represents pages that are in active use by programs. The pages may be clean or dirty. Inactive This queue represents pages that are not being actively used but have not been idle long enough to be considered truely idle. These pages may be clean or dirty. The system may choose to 'launder' dirty pages by writing them to their backing store, then marking them clean. A user program may access these pages, causing them to eventually be moved back into the Active queue. Or memory pressure may cause clean pages in this queue to be moved to the Cache. Cache This queue represents pages that are totally idle and clean, but still contain valid data associated with some file or directory. If a program accesses a Cached page it will be moved back into the Active queue. If the system cannot find enough free pages in the Free list the system can reuse pages from this queue for other purposes, destroying any data previously cached in the page. Free This queue represents pages that are totally free, meaning that they are not associated with anything at all, not even as a cache for something. Pages are freed by the system under two conditions: (1) when a program frees general memory, and (2) when the system is under memory pressure and needs more free pages then pages are taken from the cache queue and placed in the free queue. Pages used to hold file and directory information requested by programs are typically not freed. Instead they are eventually moved into the Cache queue where they might reside for long periods of time. The system only reuses these pages when under memory pressure. FreeBSD does not waste time moving pages between queues unless it is under some sort of memory pressure. FreeBSD will happily keep the pages where they fall, be it in the Active queue, Inactive queue, or Cache queue (except for the case when a program accesses such a page, at which point a Cache page will be immediately moved into the Active queue). In an extremely lightly loaded system you cannot really garner anything about memory load by looking at how many pages are in any given queue. In a normal system you can generally assume that Inactive + Cache is the real count of the number of 'cached' pages. In a more heavily loaded system Active really does mean Active, Inactive really does mean Inactive, and Cache really does mean cached. In a very heavily loaded environment the system is forced to recycle pages so quickly that pages residing in the Inactive or Cache queues could actually still be in active use (though if in the Cache queue they are guarenteed to be marked clean so they can be reused immediately without further laundering). The movement, under load, of dirty pages from the Inactive queue to the Cache queue generates the swap paging activity that you see in more heavily loaded system. This is the 'laundering' that the system performs in order to clean a dirty page in order to be able to move it from Inactive to Cache. There are other types of memory load as well.. for example, it is possible to be 'loaded down' with mostly clean pages but the active dataset is too large to fit in memory, so the system is forced to discard clean pages sooner then it would otherwise discard them. This type of load is visible by noting the amount of page scanning the system does (the 'sr' field in vmstat) and the number of reactivations (the 're' field in vmstat). A reactivation occurs when the system has moved a page (typically) to the Inactive or Cache queue, but then some program accesses it again and forces the system to take a VM fault and put the page back into the Active queue. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 17:40:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 9EF5A37B719 for ; Thu, 8 Mar 2001 17:40:12 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f291eBs96392 for freebsd-hackers@freebsd.org; Thu, 8 Mar 2001 17:40:11 -0800 (PST) (envelope-from obrien) Date: Thu, 8 Mar 2001 17:40:11 -0800 From: "David O'Brien" To: freebsd-hackers@freebsd.org Subject: doFS.sh newfs parameters for install floppy Message-ID: <20010308174011.A96364@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know of *any* problems with committing this diff? It changes the % free space from the 8% default to 0. Index: doFS.sh =================================================================== RCS file: /home/ncvs/src/release/scripts/doFS.sh,v retrieving revision 1.24.2.3 diff -u -r1.24.2.3 doFS.sh --- doFS.sh 2001/01/14 08:24:48 1.24.2.3 +++ doFS.sh 2001/03/09 00:23:53 @@ -55,7 +58,7 @@ vnconfig -s labels -c /dev/r${VNDEVICE} ${FSIMG} disklabel -Brw /dev/r${VNDEVICE} ${FSLABEL} - newfs -i ${FSINODE} -T ${FSLABEL} -o space /dev/r${VNDEVICE}c + newfs -i ${FSINODE} -T ${FSLABEL} -o space -m 0 /dev/r${VNDEVICE}c mount /dev/${VNDEVICE}c ${MNT} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 18:13:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id A208937B71A for ; Thu, 8 Mar 2001 18:13:52 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.pacbell.net ([207.214.149.121]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0G9W0003SRHXVL@mta5.snfc21.pbi.net> for hackers@freebsd.org; Thu, 8 Mar 2001 18:13:11 -0800 (PST) Received: by zippy.pacbell.net (Postfix, from userid 1000) id 76920187A; Thu, 08 Mar 2001 18:13:07 -0800 (PST) Date: Thu, 08 Mar 2001 18:13:07 -0800 From: Alex Zepeda Subject: Re: if_fxp - the real point In-reply-to: <5.0.0.25.0.20010308144541.0281a980@mail.etinc.com>; from dennis@etinc.com on Thu, Mar 08, 2001 at 02:48:12PM -0500 To: hackers@freebsd.org Message-id: <20010308181307.A3568@zippy.mybox.zip> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <"Your <5.0.0.25.0.20010308120015.01ee2eb0"@mail.etinc.com> <200103081720.f28HK1201269@guild.plethora.net> <5.0.0.25.0.20010308144541.0281a980@mail.etinc.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 08, 2001 at 02:48:12PM -0500, Dennis wrote: > No. Keeping supported drivers up to date is part of the business of > distributing an OS. Thats what "supported" implies. The driver is out of > date. Noone is looking for a feature here. We just want it to work. Dennis, dear Dennis. I recently re-subbed to -hackers and one of the first posts I caught was the beginning of one of your more recent threads. Go away. I kept telling myself I wasn't going to comment, but I will. Stop attacking people. You're not contributing code, you're not contributing help, you're just out there attacking people and proclaiming you know the only direction that FreeBSD should go in. Go away. Publically blaring your vague rants is really becomming irritating. Go away. If you feel you are obligated out of some misguided sense of greater good to rant, by all means do so. However, there *ARE* some of us who aren't intimate with your fxp problems. Like me: zippy:~#dmesg|grep fxp fxp0: port 0xec00-0xec3f mem 0xdb000000-0xdb0fffff,0xdb100000-0xdb100fff irq 11 at device 10.0 on pci0 fxp0: Ethernet address 00:90:27:d1:83:6a Works well for me. However you rant, and then state the people who should know already know the details. You rant that this shouldn't be brought up again. Okay, so don't do it Dennis. That's fine if the people who should know already know, so why bother the other half? Go away. You've got a valid problem. Go away. As such, you must learn to properly express this problem. Go away. Perhaps you just haven't realized that people won't care what you want if you demand it in a childish way. For the majority of the fxp consumers out there, the fxp driver works just fine. Go away. You're not obligated to use FreeBSD, nor are you obligated to harass the people who spend their time working on it. If you've got a problem, open a PR, submit appropiate details, leave out the heartfelt emotion, and let those who can fix it. Go away. Or maybe you should take up kernel hacking in your spare time and put up some code. Go away. Or you could go away. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 18:16:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id F278937B718 for ; Thu, 8 Mar 2001 18:16:20 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.pacbell.net ([207.214.149.121]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0G9W00LDGRMU0D@mta5.snfc21.pbi.net> for hackers@freebsd.org; Thu, 8 Mar 2001 18:16:07 -0800 (PST) Received: by zippy.pacbell.net (Postfix, from userid 1000) id 836A5187A; Thu, 08 Mar 2001 18:16:05 -0800 (PST) Date: Thu, 08 Mar 2001 18:16:05 -0800 From: Alex Zepeda Subject: Re: if_fxp - the real point In-reply-to: <20010308130348.C23640@Odin.AC.HMC.Edu>; from brooks@one-eyed-alien.net on Thu, Mar 08, 2001 at 01:03:48PM -0800 To: hackers@freebsd.org Message-id: <20010308181605.B3568@zippy.mybox.zip> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <5.0.0.25.0.20010308120015.01ee2eb0@mail.etinc.com> <20010308151156.A92103@sitesnow.com> <20010308130348.C23640@Odin.AC.HMC.Edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 08, 2001 at 01:03:48PM -0800, Brooks Davis wrote: > If it becomes a > problem, the most expensive 10/100 nic you could possiably buy is less > the $100 bucks so worry about it then. You've never tried to find a NuBus 100baseTX adapter have you? About $150 a pop, new. The Asante doesn't do full duplex, is based on the original SMC chipset, not sure about the only other option, the Farallon card. But you were referring to PCI cards, right? ;^) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 18:48:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 93F9A37B718 for ; Thu, 8 Mar 2001 18:48:55 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f292mNR06987; Thu, 8 Mar 2001 18:48:23 -0800 (PST) (envelope-from dillon) Date: Thu, 8 Mar 2001 18:48:23 -0800 (PST) From: Matt Dillon Message-Id: <200103090248.f292mNR06987@earth.backplane.com> To: Joerg Micheel Cc: freebsd-hackers@FreeBSD.ORG, joerg@cs.waikato.ac.nz Subject: Re: Trouble with quotas on FreeBSD 4.2-STABLE References: <20010309120212.A49897@cs.waikato.ac.nz> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I am running a system with a 50GB /home drive. One user is experiencing :inconsistencies, for him the system reports being over disk quota. :du -sk reports 1.7GB utilization, quota reports 5.2GB. I've been checking :the entire drive for files that belong to this user, same result. I have :turned off quota, rerun quotacheck. It reports inconsistencies, but minor, :does not change the big picture that this user is over quota. Soft limits :are set to 5GB, hard to 10GB for all users on this drive. : :Thank you for any hints. : Joerg :-- :Joerg B. Micheel Email: :WAND and NLANR MOAT Email: Is it possible that the user is over his inode quota rather then his disk quota? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 19:12:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from filk.iinet.net.au (syncopation-dns.iinet.net.au [203.59.24.29]) by hub.freebsd.org (Postfix) with SMTP id C886137B718 for ; Thu, 8 Mar 2001 19:12:29 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 26291 invoked by uid 666); 9 Mar 2001 03:13:23 -0000 Received: from i077-118.nv.iinet.net.au (HELO elischer.org) (203.59.77.118) by mail.m.iinet.net.au with SMTP; 9 Mar 2001 03:13:23 -0000 Message-ID: <3AA84A02.9FDC6522@elischer.org> Date: Thu, 08 Mar 2001 19:12:02 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Jordan Hubbard Cc: jlemon@flugsvamp.com, hackers@freebsd.org Subject: Re: if_fxp status? References: <200103082217.f28MHeZ91216@prism.flugsvamp.com> <20010308151420U.jkh@osd.bsdi.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > > From: Jonathan Lemon > Subject: Re: if_fxp status? > Date: Thu, 8 Mar 2001 16:17:40 -0600 (CST) > > > I umm... volunteer? (that is, for everyone except Dennis; he obviously > > has the situation well under control at this point, and doesn't need > > any assistance). > > That's great! I think we can assume that David is reading this > discussion if he's available and wants to comment, and if he's not > then the point is somewhat moot. :) ship that man the sample hardware that was donated! (before he gets away) > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 20:51:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (ashto-0006.sjc.ca.bbnow.net [24.219.121.199]) by hub.freebsd.org (Postfix) with ESMTP id AF8F337B719 for ; Thu, 8 Mar 2001 20:51:29 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f28LNqS01219; Thu, 8 Mar 2001 13:24:02 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103082124.f28LNqS01219@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point In-reply-to: Your message of "Thu, 08 Mar 2001 14:43:56 EST." <5.0.0.25.0.20010308135349.02818a90@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Mar 2001 13:23:52 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > maybe commercial vendors would be willing to fund some freebsd projects if > there was a positive relationship. They do, and there is. I'm continually irritated that we can't work out a better relationship with you/ETinc, since I think it'd be to our mutual benefit. You're just one of those people that we don't seem to get along with. 8( > And DG has been MIA for a long time, not just recently. The last time the > fxp driver was broken i found the fix and pointed him at the code. I guess > I'll have to fix it this time also, as if maintaining drivers for 6 serial > cards and the bwmgr isnt enough for me to do. Maybe I'll sell it this > time. :-) *laugh* If you don't, please file it as a PR and beat people up until it gets committed. This is the best way to go, under the circumstances. > >Call BSDi (numbers on their website) and ask to speak to Gary Johnson > >(CEO) or Mark Garver (senior VP) and ask them yourself. If you get a > >useful answer, please tell the rest of us; especially me, since I burnt > >out trying to make it happen. > > Ive spoken with Mr Johnson several times. hes the biggest reason that BSDI > is what it is. Amazing that hes still there. He has no concept of what the > market wants. First he wanted to challenge microsoft (at similar prices) > for the server market now he wants to be redhat. funny guy. If you're unhappy with the results you're getting from Gary, try calling Kirk McKusick. Keep kicking people. > So what is the "relationship" that was announced? If they dont provide > support or funds, what do they do? That's a Very Good Question. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 22:56: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id C640637B719 for ; Thu, 8 Mar 2001 22:56:02 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.11.1) id f296tvF18394; Fri, 9 Mar 2001 00:55:57 -0600 (CST) (envelope-from dan) Date: Fri, 9 Mar 2001 00:55:57 -0600 From: Dan Nelson To: Matt Dillon Cc: Jesper Skriver , Dan Phoenix , freebsd-hackers@FreeBSD.ORG Subject: Re: systat -vmstat or iostat IO help Message-ID: <20010309005557.A6561@dan.emsphone.com> References: <200103060208.f2628PT49635@earth.backplane.com> <20010308213722.A83857@skriver.dk> <200103090126.f291QLO05885@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.14i In-Reply-To: <200103090126.f291QLO05885@earth.backplane.com>; from "Matt Dillon" on Thu Mar 8 17:26:21 GMT 2001 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Mar 08), Matt Dillon said: > Jesper Skriver wrote: > :Could you please give a pointer to a description of the meaning of > :Active, Inactive and Cache, on a machine I see this > > Active This queue represents pages that are in active use by > programs. The pages may be clean or dirty. [snip excellent explanation] Hey, can we get this into a manpage, like vm(9) or something? Jesper's question is definitely a FAQ, and it'd be nice to point people to some official documentation. -- 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 Mar 8 23:21:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bsdconspiracy.net (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id B286C37B719 for ; Thu, 8 Mar 2001 23:21:39 -0800 (PST) (envelope-from wes@softweyr.com) Received: from zaphod.softweyr.com ([204.68.178.35] helo=softweyr.com ident=wes) by bsdconspiracy.net with esmtp (Exim 3.14 #1) id 14bGd2-0002m0-00; Thu, 08 Mar 2001 23:43:56 -0700 Message-ID: <3AA883DE.BBCBDD09@softweyr.com> Date: Fri, 09 Mar 2001 00:18:54 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: bruno schwander Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: examining the environment References: <200103060208.f2628PT49635@earth.backplane.com> <20010308213722.A83857@skriver.dk> <3AA7EF0B.434B8D8F@dvart.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bruno schwander wrote: > > Hi everybody, > > How can I examine an other process environment ? > > I have a daemon that needs to do something according to an environment > variable set in a different process. Can I open an other process and lookup > environment variables set in his space ? ps can do this, check it's code. -- Where am I, and what am I doing in this handbasket? Wes Peters wes@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 Mar 8 23:31:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shakeyjakes.com (cx658371-a.elcjn1.sdca.home.com [24.13.29.199]) by hub.freebsd.org (Postfix) with SMTP id D530C37B719 for ; Thu, 8 Mar 2001 23:31:14 -0800 (PST) (envelope-from mike.mcclain@shakeyjakes.com) Received: by shakeyjakes.com (wcMail) id 25923W Thu, 08 Mar 2001 23:30:37 -0800 From: mike.mcclain@shakeyjakes.com Subject: Help!!! 2nd HD gone Date: Thu, 08 Mar 2001 23:30:36 -0800 Message-Id: <1885270759@shakeyjakes.com> Organization: Shakey Jake's Free BBS from Santee, Ca... To: freebsd-hackers@freebsd.org X-Mailer: wcMail v5.4.449.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy, I hadn't booted FreeBSD 3.4 for many months but had mounted several partitions on /dev/wd2s* from /etc/fstab. Last week I couldn't get a clean boot 'til I took all references to /dev/wd2s* out of /etc/fstab. fbsd:~> uname -a FreeBSD playground 3.4-RELEASE FreeBSD 3.4-RELEASE #1: Sun Mar 26 16:56:35 PST 2000 root@:/usr/src/sys/compile/McKERNEL i386 From dmesg: CPU: Pentium/P55C (167.05-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 33554432 (32768K bytes) chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip2: rev 0x01 on pci0.7.3 Having done that I now see: fbsd:~> mount -t ext2fs /dev/wd2s1 /rh6 ext2fs: /dev/wd2s1: Device not configured fbsd:~> fdisk /dev/wd2.fdisk: cannot open disk /dev/wd2: Device not configured fbsd:~> disklabel /dev/wd2 disklabel: /dev/wd2: Device not configured fbsd:~> ls -l /dev/wd2s* brw-r----- 1 root operator 0, 0x00020012 Mar 20 2000 /dev/wd2s1 ... /dev/wd2s2 through /dev/wd2s8 nearly identical brw-r----- 1 root operator 0, 0x000a0012 Apr 20 2000 /dev/wd2s9 from /var/log/dmesg.today: this is the way it was. wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0:4112MB (8421840 sectors), 8912 cyls, 15 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S from /var/log/messages: May 23 18:15:19 /kernel: wdc1 at 0x170-0x177 irq 15 on isa May 23 18:15:19 /kernel: wdc1: unit 0 (wd2): Feb 11 16:27:36 /kernel: wdc1 not found at 0x170 This makes me think the kernal is not seeing the controller at boot. wd2 aka D: aka /dev/hdc is visible from dos and I'm writing this from Slackware 7.0 mounted on /dev/hdc8. This from Slackware's /var/log/messages: Feb 15 09:20:15 playground kernel: hda: WDC AC24300L, 4112MB w/256kB Cache, CHS=524/255/63, UDMA Feb 15 09:20:15 playground kernel: hdc: WDC AC26400R, 6149MB w/512kB Cache, CHS=13328/15/63, (U)DMA I've tried various configurations in BIOS with no luck. I'm stumped. All suggestions welcome. TIA, MiKe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 8 23:49:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mr200.netcologne.de (mr200.netcologne.de [194.8.194.109]) by hub.freebsd.org (Postfix) with ESMTP id AED7337B719 for ; Thu, 8 Mar 2001 23:49:26 -0800 (PST) (envelope-from pherman@frenchfries.net) Received: from husten.security.at12.de (dial-194-8-195-149.netcologne.de [194.8.195.149]) by mr200.netcologne.de (Mirapoint) with ESMTP id ACH09626; Fri, 9 Mar 2001 08:49:10 +0100 (CET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.3/8.11.2) with ESMTP id f297n1E61116; Fri, 9 Mar 2001 08:49:01 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Fri, 9 Mar 2001 08:49:00 +0100 (CET) From: Paul Herman To: Matt Dillon Cc: Jesper Skriver , Dan Phoenix , Subject: Re: systat -vmstat or iostat IO help In-Reply-To: <200103090126.f291QLO05885@earth.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 Hi Matt, [...great comments on the VM writeup from the handbook...] On Thu, 8 Mar 2001, Matt Dillon wrote: > This type of load is visible by noting the amount of page scanning > the system does (the 'sr' field in vmstat) and the number of reactivations > (the 're' field in vmstat). A reactivation occurs when the system has > moved a page (typically) to the Inactive or Cache queue, but then some > program accesses it again and forces the system to take a VM fault and put > the page back into the Active queue. About a year ago, I was looking through the VM code, and saw that the 're' field in vmstat is just Cache reactivations, and not both Inactive & Cache. I just figured it was how it was supposed to be. Could it be that 're' should include *all* reactivations? If so, would I be correct in suggesting: Index: vm_page.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_page.c,v retrieving revision 1.147.2.6 diff -u -r1.147.2.6 vm_page.c --- vm_page.c 2001/03/03 23:06:09 1.147.2.6 +++ vm_page.c 2001/03/09 07:36:13 @@ -990,7 +990,8 @@ s = splvm(); if (m->queue != PQ_ACTIVE) { - if ((m->queue - m->pc) == PQ_CACHE) + if ((m->queue - m->pc) == PQ_CACHE || + (m->queue - m->pc) == PQ_INACTIVE) cnt.v_reactivated++; vm_page_unqueue(m); ...or maybe even just something like ( (m->queue - m->pc) != PQ_FREE ) -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 2:21:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 0969A37B719; Fri, 9 Mar 2001 02:21:53 -0800 (PST) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id 541D9317C; Fri, 9 Mar 2001 10:21:58 +0000 (GMT) Date: Fri, 9 Mar 2001 10:21:58 +0000 From: Josef Karthauser To: David O'Brien Cc: freebsd-hackers@freebsd.org Subject: Re: doFS.sh newfs parameters for install floppy Message-ID: <20010309102158.F710@tao.org.uk> Mail-Followup-To: Josef Karthauser , David O'Brien , freebsd-hackers@freebsd.org References: <20010308174011.A96364@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="3yNHWXBV/QO9xKNm" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010308174011.A96364@dragon.nuxi.com>; from obrien@freebsd.org on Thu, Mar 08, 2001 at 05:40:11PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --3yNHWXBV/QO9xKNm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 08, 2001 at 05:40:11PM -0800, David O'Brien wrote: > Does anyone know of *any* problems with committing this diff? > It changes the % free space from the 8% default to 0. I would imagine that this should be fine. We've been doing this in PicoBSD for a long while. BTW, I believe that -o space becomes the default when -m 0 is specified. Joe >=20 > Index: doFS.sh > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/release/scripts/doFS.sh,v > retrieving revision 1.24.2.3 > diff -u -r1.24.2.3 doFS.sh > --- doFS.sh 2001/01/14 08:24:48 1.24.2.3 > +++ doFS.sh 2001/03/09 00:23:53 > @@ -55,7 +58,7 @@ > =20 > vnconfig -s labels -c /dev/r${VNDEVICE} ${FSIMG} > disklabel -Brw /dev/r${VNDEVICE} ${FSLABEL} > - newfs -i ${FSINODE} -T ${FSLABEL} -o space /dev/r${VNDEVICE}c > + newfs -i ${FSINODE} -T ${FSLABEL} -o space -m 0 /dev/r${VNDEVICE}c > =20 > mount /dev/${VNDEVICE}c ${MNT} >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message --3yNHWXBV/QO9xKNm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqorsUACgkQXVIcjOaxUBbQLQCgoaeXBLwWWtXC5vtYQBZFq71i 6rkAoIPyWXg1MM6RQDXw43GtAjLsqRpV =x4wM -----END PGP SIGNATURE----- --3yNHWXBV/QO9xKNm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 2:41:49 2001 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 A9EA637B71A; Fri, 9 Mar 2001 02:41:43 -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 LAA48528; Fri, 9 Mar 2001 11:42:14 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103091042.LAA48528@info.iet.unipi.it> Subject: howto access an oddly shaped partition on a floppy ? To: hackers@freebsd.org Date: Fri, 9 Mar 2001 11:42:13 +0100 (CET) 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 Hi, i have the following problem (related to picobsd this is why this msg is Bcc to -small). We can format 1722KB floppies, which is 21 sectors/2heads/82 tracks, but the bios is unable to boot from them -- it will only read the first 18 sectors of each track and in many cases it will be able to read all 82 tracks. So one approach one would use with picobsd floppies could be the following: format the disk with a 1722 format, but then put a regular filesystem only on the "rectangular" area made of 18 sectors/82 tracks. It would be nice to access the rest of the disk (sectors 19-20-21 of each track) as a separate volume. But how do we achieve this ? One way could be to write some userspace program which knows the mapping and reads/writes/seeks for you in the appropriate places. Another one would be to modify the "fd" driver (apparently you need to touch a couple of places in sys/isa/fd.c:fdstate() ) to do the remapping for you, maybe driven by some table or sysctl variable. The latter method would be more flexible as you would be able to use the volume as an ordinary disk. Suggestions ? cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone (510) 666 2927 . ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 2:52: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 897C837B718 for ; Fri, 9 Mar 2001 02:52:02 -0800 (PST) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id 54D43313F; Fri, 9 Mar 2001 10:51:52 +0000 (GMT) Date: Fri, 9 Mar 2001 10:51:52 +0000 From: Josef Karthauser To: Luigi Rizzo Cc: hackers@freebsd.org Subject: Re: howto access an oddly shaped partition on a floppy ? Message-ID: <20010309105151.B40040@tao.org.uk> References: <200103091042.LAA48528@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ADZbWkCsHQ7r3kzd" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103091042.LAA48528@info.iet.unipi.it>; from luigi@info.iet.unipi.it on Fri, Mar 09, 2001 at 11:42:13AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ADZbWkCsHQ7r3kzd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 09, 2001 at 11:42:13AM +0100, Luigi Rizzo wrote: > Hi, > i have the following problem (related to picobsd this is > why this msg is Bcc to -small). >=20 > We can format 1722KB floppies, which is 21 sectors/2heads/82 tracks, > but the bios is unable to boot from them -- it will only read > the first 18 sectors of each track and in many cases it will be > able to read all 82 tracks. >=20 > So one approach one would use with picobsd floppies could be the > following: format the disk with a 1722 format, but then put > a regular filesystem only on the "rectangular" area made > of 18 sectors/82 tracks. >=20 > It would be nice to access the rest of the disk (sectors 19-20-21 > of each track) as a separate volume. But how do we achieve this ? > One way could be to write some userspace program which knows > the mapping and reads/writes/seeks for you in the appropriate > places. Another one would be to modify the "fd" driver (apparently > you need to touch a couple of places in sys/isa/fd.c:fdstate() ) > to do the remapping for you, maybe driven by some table or sysctl > variable. The latter method would be more flexible as you would What about having the first few tracks, ie. the boot area, 18 sectors, and the rest of the disk 21 sectors, and have the boot code/kernel do the right thing? Isn't this easier? Joe --ADZbWkCsHQ7r3kzd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqotccACgkQXVIcjOaxUBYdGwCeO2+loAB35hrj7hSyIJgF7T5q FjsAoIIdAWUyzwIvxaEcbptsqtFcoGSj =f2Yj -----END PGP SIGNATURE----- --ADZbWkCsHQ7r3kzd-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 2:58:36 2001 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 587F337B718 for ; Fri, 9 Mar 2001 02:58:33 -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 LAA48632; Fri, 9 Mar 2001 11:58:57 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103091058.LAA48632@info.iet.unipi.it> Subject: Re: howto access an oddly shaped partition on a floppy ? In-Reply-To: <20010309105151.B40040@tao.org.uk> from Josef Karthauser at "Mar 9, 2001 10:51:52 am" To: Josef Karthauser Date: Fri, 9 Mar 2001 11:58:55 +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 > What about having the first few tracks, ie. the boot area, 18 sectors, > and the rest of the disk 21 sectors, and have the boot code/kernel do > the right thing? Isn't this easier? It has all sorts of problems: neither the bios nor the disklabel nor the kernel can handle variable length tracks, plus the bootloader (boot2 and /boot/loader) still uses the bios, so the whole area containing the kernel would need to be 18 sectors, and the kernel on picobsd is almost as large as the whole disk... cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 3: 0:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id D133C37B719 for ; Fri, 9 Mar 2001 03:00:20 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f29B0ZV27659; Fri, 9 Mar 2001 12:00:35 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Luigi Rizzo Cc: Josef Karthauser , hackers@FreeBSD.ORG Subject: Re: howto access an oddly shaped partition on a floppy ? In-Reply-To: Your message of "Fri, 09 Mar 2001 11:58:55 +0100." <200103091058.LAA48632@info.iet.unipi.it> Date: Fri, 09 Mar 2001 12:00:35 +0100 Message-ID: <27657.984135635@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200103091058.LAA48632@info.iet.unipi.it>, Luigi Rizzo writes: >> What about having the first few tracks, ie. the boot area, 18 sectors, >> and the rest of the disk 21 sectors, and have the boot code/kernel do >> the right thing? Isn't this easier? > >It has all sorts of problems: neither the bios nor the disklabel >nor the kernel can handle variable length tracks, plus the bootloader >(boot2 and /boot/loader) still uses the bios, so the whole area >containing the kernel would need to be 18 sectors, and the kernel >on picobsd is almost as large as the whole disk... It would be possible to teach the floppy driver that cyl 0-9 has 18 sectors while cyl10-81 has 21. A small matter of hacking... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 3:31:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id C2D3837B718 for ; Fri, 9 Mar 2001 03:31:24 -0800 (PST) (envelope-from roam@orbitel.bg) Received: (qmail 33160 invoked by uid 1000); 9 Mar 2001 11:30:36 -0000 Date: Fri, 9 Mar 2001 13:30:36 +0200 From: Peter Pentchev To: Matt Dillon Cc: Joerg Micheel , freebsd-hackers@FreeBSD.ORG Subject: Re: Trouble with quotas on FreeBSD 4.2-STABLE Message-ID: <20010309133036.C6215@ringworld.oblivion.bg> Mail-Followup-To: Matt Dillon , Joerg Micheel , freebsd-hackers@FreeBSD.ORG References: <20010309120212.A49897@cs.waikato.ac.nz> <200103090248.f292mNR06987@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103090248.f292mNR06987@earth.backplane.com>; from dillon@earth.backplane.com on Thu, Mar 08, 2001 at 06:48:23PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 08, 2001 at 06:48:23PM -0800, Matt Dillon wrote: > > :I am running a system with a 50GB /home drive. One user is experiencing > :inconsistencies, for him the system reports being over disk quota. > :du -sk reports 1.7GB utilization, quota reports 5.2GB. I've been checking > :the entire drive for files that belong to this user, same result. I have > :turned off quota, rerun quotacheck. It reports inconsistencies, but minor, > :does not change the big picture that this user is over quota. Soft limits > :are set to 5GB, hard to 10GB for all users on this drive. > : > :Thank you for any hints. > : Joerg > :-- > :Joerg B. Micheel Email: > :WAND and NLANR MOAT Email: > > Is it possible that the user is over his inode quota rather then his > disk quota? ..or that the quota checks include deleted files, which are still being held open by a long-running process (logfiles and such)? G'luck, Peter -- This sentence claims to be an Epimenides paradox, but it is lying. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 4: 8:10 2001 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 122CB37B71A for ; Fri, 9 Mar 2001 04:08:06 -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 NAA49206; Fri, 9 Mar 2001 13:05:58 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103091205.NAA49206@info.iet.unipi.it> Subject: Re: howto access an oddly shaped partition on a floppy ? In-Reply-To: <27657.984135635@critter> from Poul-Henning Kamp at "Mar 9, 2001 12:00:35 pm" To: Poul-Henning Kamp Date: Fri, 9 Mar 2001 13:05:58 +0100 (CET) Cc: Josef Karthauser , 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 > It would be possible to teach the floppy driver that cyl 0-9 has > 18 sectors while cyl10-81 has 21. this would only work after the kernel has control, and the kernel needs far more than 10 cylinders... cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 4:43: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 8CD0437B71C for ; Fri, 9 Mar 2001 04:43:02 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f29Cgo029011; Fri, 9 Mar 2001 04:42:50 -0800 (PST) (envelope-from obrien) Date: Fri, 9 Mar 2001 04:42:50 -0800 From: "David O'Brien" To: Alex Zepeda Cc: hackers@freebsd.org Subject: Re: if_fxp - the real point Message-ID: <20010309044249.A28945@dragon.nuxi.com> Reply-To: hackers@freebsd.org References: <"Your <5.0.0.25.0.20010308120015.01ee2eb0"@mail.etinc.com> <200103081720.f28HK1201269@guild.plethora.net> <5.0.0.25.0.20010308144541.0281a980@mail.etinc.com> <20010308181307.A3568@zippy.mybox.zip> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010308181307.A3568@zippy.mybox.zip>; from jazepeda@pacbell.net on Thu, Mar 08, 2001 at 06:13:07PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 08, 2001 at 06:13:07PM -0800, Alex Zepeda wrote: > However, there *ARE* some of us who aren't intimate with your fxp > problems. The problem does exist. I have a board that the `fxp' driver splits this out for: fxp0: warning: unsupported PHY, type = 17, addr = 2 fxp1: warning: unsupported PHY, type = 17, addr = 2 > You've got a valid problem. Go away. "You've got a valid problem, go away." huh?? His points are very valid about maintenance of the `fxp' driver. His views on how to make something happen are what is a little out of touch. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 8: 4: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postal.jnpr.net (natint.juniper.net [207.17.136.129]) by hub.freebsd.org (Postfix) with ESMTP id 6D5C937B71B; Fri, 9 Mar 2001 08:04:02 -0800 (PST) (envelope-from walterg@juniper.net) Received: by postal.jnpr.net with Internet Mail Service (5.5.2653.19) id ; Fri, 9 Mar 2001 08:04:02 -0800 Message-ID: From: Walter Goralski To: "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Generating SYN packets. Date: Fri, 9 Mar 2001 08:03:58 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks: Andreas Klemm, who ported cflowd to FreeBSD, suggested I use this vehicle to see if I could get some help. I am a course developer for Juniper Networks, and I have just written a 2-day advanced course on router firewall filters (this is one reason for the cflowd). We have participants in a strictly closed lab environment configuring filters to stop spoofs, smurf, fraggle, etc. In order to show they work, we also have a 4.2 FreeBSD laptop that can launch smurf, fraggle, etc. at the routers and the instructor's PC. The missing piece has been DOS SYN attacks. I have the really common "synk4.c" source that is all over the Web, but I get errors when I try to compile it ("it's the linux includes" someone told me). Now, I last used my C programming skills in the 80s on a Silent 700 teletype and a 3B20 mini, so I tried playing around with "programming by analogy" (hey, it sometimes works). I took fraggle.c and tried to substitute a tcp header for the udp header. Anyway, the compiler tells me there is a syntax error in tcp.h (right before the "n_long"), which strikes me as odd. Then it says I am using an "incomplete type" and dereferences all of my pointers. Sometimes I can force a compile and lonk, but none of my paramters get plugged into the packets when I use it. So: anybody got a quick and dirty SYN packet generator out there? A version of synk4 that runs on 4.2? An executable? I even tried to install hping2 from the FreeBSD ports collection, but of course *that* won't run either. (It says my ep0 interface is not defined (!) and seems to try to use lo.) If I use "make install," I get these run time errors; if I use "./configure" and then "make" I get compile errors, also about "overlapping" includes. (***Are my include files all screwed up?*** How could I tell?) But the cflowd and RADIUS servers, also installed a couple of weeks ago from these ports, run merrily along, so the basic system seems to be intact. I don't think my programming efforts have scrammed the system (and I don't have the cd-rom, since it's a company laptop), but I am very worried that I have somehow harmed the .h files. Meanwhile, I'm re-learning BSD socket coding. But this might be faster if anyone can help. (As a note, if anyone out there works for Juniper, I can configure remote access to the laptop if required.) Walter Goralski walterg@juniper.net 952-938-4483 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 8:16:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palnet.com (mail.palnet.com [217.66.226.37]) by hub.freebsd.org (Postfix) with ESMTP id 3D1B037B71A for ; Fri, 9 Mar 2001 08:16:40 -0800 (PST) (envelope-from mustafa@palnet.com) Received: from mustafa (dogbert.palnet.com [192.116.17.51]) by mail.palnet.com (8.11.0/8.9.3) with SMTP id f29HDTB39423 for ; Fri, 9 Mar 2001 19:13:29 +0200 (EET) Message-ID: <017e01c0a8b4$44b55cd0$8d00000a@mustafa> From: "Mustafa Deeb" To: Subject: Qmail + MYSQL Date: Fri, 9 Mar 2001 18:16:16 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_017B_01C0A8C5.080BD230" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_017B_01C0A8C5.080BD230 Content-Type: text/plain; charset="windows-1256" Content-Transfer-Encoding: quoted-printable hi, Qmail has the capabillity of storing Email inside a table with MYSQL and = do POP3 from it as well is it better to go this approach , or the standard homedir way is = better? need some openions Best Regards Mustafa N. Deeb Technical Manager Palnet Communications Ltd. Email: mustafa@palnet.com Tel: ++970 (2) 2403434 Fax: ++970 (2) 2403430 some countires still use 972 instead of 970 ------=_NextPart_000_017B_01C0A8C5.080BD230 Content-Type: text/html; charset="windows-1256" Content-Transfer-Encoding: quoted-printable
hi,
 
Qmail has the capabillity of storing = Email inside a=20 table with MYSQL and do POP3 from it as well
 
is it better to go this approach , or = the standard=20 homedir way is better?
 
need some openions
 
Best Regards
 
 
 
 
 
Mustafa N. Deeb
Technical = Manager
Palnet=20 Communications Ltd.
Email: mustafa@palnet.com
Tel: ++970 = (2)=20 2403434
Fax: ++970 (2) 2403430
 
some countires still use 972 instead of = 970
------=_NextPart_000_017B_01C0A8C5.080BD230-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 8:40:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 2547837B718 for ; Fri, 9 Mar 2001 08:40:36 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id LAA81132; Fri, 9 Mar 2001 11:52:27 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010309115453.0411ebe0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Fri, 09 Mar 2001 11:55:51 -0500 To: hackers@FreeBSD.ORG, Alex Zepeda From: Dennis Subject: Re: if_fxp - the real point Cc: hackers@FreeBSD.ORG In-Reply-To: <20010309044249.A28945@dragon.nuxi.com> References: <20010308181307.A3568@zippy.mybox.zip> <"Your <5.0.0.25.0.20010308120015.01ee2eb0"@mail.etinc.com> <200103081720.f28HK1201269@guild.plethora.net> <5.0.0.25.0.20010308144541.0281a980@mail.etinc.com> <20010308181307.A3568@zippy.mybox.zip> 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 > > > You've got a valid problem. Go away. > >"You've got a valid problem, go away." huh?? >His points are very valid about maintenance of the `fxp' driver. >His views on how to make something happen are what is a little out of >touch. I tried sitting with my hands folded. It didnt work. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 8:49:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ohm.physics.purdue.edu (ohm.physics.purdue.edu [128.210.146.32]) by hub.freebsd.org (Postfix) with ESMTP id D874F37B718; Fri, 9 Mar 2001 08:49:24 -0800 (PST) (envelope-from will@physics.purdue.edu) Received: (from will@localhost) by ohm.physics.purdue.edu (8.11.2/8.9.3) id f29GpP552199; Fri, 9 Mar 2001 11:51:25 -0500 (EST) (envelope-from will@physics.purdue.edu) X-Authentication-Warning: ohm.physics.purdue.edu: will set sender to will@physics.purdue.edu using -f Date: Fri, 9 Mar 2001 11:51:25 -0500 From: Will Andrews To: Walter Goralski Cc: "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: Generating SYN packets. Message-ID: <20010309115125.D45561@ohm.physics.purdue.edu> Reply-To: Will Andrews References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Do9hQ/bfCb4zBpLo" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from walterg@juniper.net on Fri, Mar 09, 2001 at 08:03:58AM -0800 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Do9hQ/bfCb4zBpLo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 09, 2001 at 08:03:58AM -0800, Walter Goralski wrote: > The missing piece has been DOS SYN attacks. I have the really common > "synk4.c" source that is all over the Web, but I get errors when I try to > compile it ("it's the linux includes" someone told me). Now, I last used = my They're most likely right. Try changing "#include " to "#include " or "#include ". Linux has this weird idea that raw sockets headers should be under . Apparently they are the only OS that supports such behavior. ;) --=20 wca --Do9hQ/bfCb4zBpLo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6qQoMF47idPgWcsURAuycAJ9fphV5OzJjr9opRf3s8/q0ECM9iACdGvOK y5tILIKpASGmq1LlVdovOp8= =Puua -----END PGP SIGNATURE----- --Do9hQ/bfCb4zBpLo-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 8:51:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 147D737B71B for ; Fri, 9 Mar 2001 08:51:52 -0800 (PST) (envelope-from roam@orbitel.bg) Received: (qmail 889 invoked by uid 1000); 9 Mar 2001 16:51:18 -0000 Date: Fri, 9 Mar 2001 18:51:18 +0200 From: Peter Pentchev To: Mustafa Deeb Cc: freebsd-hackers@freebsd.org Subject: Re: Qmail + MYSQL Message-ID: <20010309185118.A526@ringworld.oblivion.bg> Mail-Followup-To: Mustafa Deeb , freebsd-hackers@freebsd.org References: <017e01c0a8b4$44b55cd0$8d00000a@mustafa> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <017e01c0a8b4$44b55cd0$8d00000a@mustafa>; from mustafa@palnet.com on Fri, Mar 09, 2001 at 06:16:16PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 09, 2001 at 06:16:16PM +0200, Mustafa Deeb wrote: > hi, > > Qmail has the capabillity of storing Email inside a table with MYSQL and do POP3 from it as well > > is it better to go this approach , or the standard homedir way is better? > > need some openions "It depends". If you have a single mail storage server, and people a) login to it and read mail locally; b) connect to it and read mail via POP3, or c) read mail from other machines that have NFS-mounted their home dirs, then Maildir delivery is all you need. If, however, you want a more client-server-ish model, where mail is stored in one location, but accessed via many (e.g. a POP3 server farm, or many POP3 servers for many geographical locations), then maybe a central MySQL server could do you good. Of course, all these cases overlap more than a little - e.g. there might be a POP3 server farm that NFS mounts Maildir's from a central server, or there might be a single POP3 server, which, for security reasons, reads mail from a remote MySQL database.. it all depends on how you want to setup your network. G'luck, Peter -- What would this sentence be like if it weren't self-referential? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 8:55:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 36F0237B718 for ; Fri, 9 Mar 2001 08:55:24 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14bQAj-0000KQ-00; Fri, 09 Mar 2001 09:55:21 -0700 Message-ID: <3AA90AF9.E3CFF332@softweyr.com> Date: Fri, 09 Mar 2001 09:55:21 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mustafa Deeb Cc: freebsd-hackers@freebsd.org Subject: Re: Qmail + MYSQL References: <017e01c0a8b4$44b55cd0$8d00000a@mustafa> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mustafa Deeb wrote: > > hi, > > Qmail has the capabillity of storing Email inside a table with MYSQL and > do POP3 from it as well > > is it better to go this approach , or the standard homedir way is better? MySQL has relatively poor insert performance; if your mail server is very busy this would probably not be a great option. I certainly can't see any compelling reason to store mail messages in a database, unless you need to be able to select messages from the database for some 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 Fri Mar 9 9: 5:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id A22B637B719; Fri, 9 Mar 2001 09:05:45 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id MAA81254; Fri, 9 Mar 2001 12:17:40 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010309115846.041255c0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Fri, 09 Mar 2001 12:21:04 -0500 To: Mike Smith From: Dennis Subject: Re: if_fxp - the real point Cc: hackers@FreeBSD.ORG In-Reply-To: <200103082124.f28LNqS01219@mass.dis.org> References: 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 > > > >Call BSDi (numbers on their website) and ask to speak to Gary Johnson > > >(CEO) or Mark Garver (senior VP) and ask them yourself. If you get a > > >useful answer, please tell the rest of us; especially me, since I burnt > > >out trying to make it happen. > > > > Ive spoken with Mr Johnson several times. hes the biggest reason that BSDI > > is what it is. Amazing that hes still there. He has no concept of what the > > market wants. First he wanted to challenge microsoft (at similar prices) > > for the server market now he wants to be redhat. funny guy. > >If you're unhappy with the results you're getting from Gary, try calling >Kirk McKusick. Keep kicking people. Wait. Isn't "kicking people" what I'm getting beat up for in this thread? I dont call BSDI (anymore). Its generally a waste of time. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 9:21: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.targetnet.com (smtp.targetnet.com [205.150.0.125]) by hub.freebsd.org (Postfix) with ESMTP id DCB4737B719; Fri, 9 Mar 2001 09:20:57 -0800 (PST) (envelope-from james@targetnet.com) Received: from james by smtp.targetnet.com with local (Exim 3.16 #1) id 14bQZL-000Far-00; Fri, 09 Mar 2001 12:20:47 -0500 Date: Fri, 9 Mar 2001 12:20:47 -0500 From: James FitzGibbon To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: PR bin/25110 - pthreads signal handling problem Message-ID: <20010309122047.A34827@targetnet.com> Reply-To: jfitz@freebsd.org Mail-Followup-To: James FitzGibbon , freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm wondering if anyone has the time or inclination to take a look at a fix for PR bin/25110. We're having problems using a freshly-built 4.2-stable box (technically 4.3 rc at this point), and the bug is still present. I'm not sure how many people would see this problem (we see it because we have to compile Apache 1.x with the -pthread switch due to add-on modules that are threaded). Under 4.1-stable, everything was fine. At some point between 4.1-stable and 4.2-release, something changed, but my hunt through the CVS repository hasn't revealed anything obvious. In any case, it's a repeatable bug (the PR includes a code sample) and unless looked at, it will be a bug in 4.3-release. If there's any clarification needed, please let me know. TIA. -- j. James FitzGibbon james@targetnet.com Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 9:46:39 2001 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 A915937B718 for ; Fri, 9 Mar 2001 09:46:36 -0800 (PST) (envelope-from sam@errno.com) Received: from melange (melange.errno.com [209.212.166.36]) by gw.errno.com (8.11.2/8.11.2) with SMTP id f29HkZH14492 for ; Fri, 9 Mar 2001 09:46:35 -0800 (PST) Message-ID: <09d901c0a8c0$e2bfed30$24a6d4d1@melange> From: "Sam Leffler" To: References: <"Your <5.0.0.25.0.20010308120015.01ee2eb0"@mail.etinc.com> <200103081720.f28HK1201269@guild.plethora.net> <5.0.0.25.0.20010308144541.0281a980@mail.etinc.com> <20010308181307.A3568@zippy.mybox.zip> <20010309044249.A28945@dragon.nuxi.com> Subject: Re: if_fxp - the real point Date: Fri, 9 Mar 2001 09:46:35 -0800 Organization: Errno Consulting 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.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What board is this? Sam ----- Original Message ----- From: "David O'Brien" To: "Alex Zepeda" Cc: Sent: Friday, March 09, 2001 4:42 AM Subject: Re: if_fxp - the real point > On Thu, Mar 08, 2001 at 06:13:07PM -0800, Alex Zepeda wrote: > > However, there *ARE* some of us who aren't intimate with your fxp > > problems. > > The problem does exist. I have a board that the `fxp' driver splits this > out for: > > fxp0: warning: unsupported PHY, type = 17, addr = 2 > fxp1: warning: unsupported PHY, type = 17, addr = 2 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 10:11:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 1F7E237B718 for ; Fri, 9 Mar 2001 10:11:51 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f29IBXd12334; Fri, 9 Mar 2001 10:11:33 -0800 (PST) (envelope-from dillon) Date: Fri, 9 Mar 2001 10:11:33 -0800 (PST) From: Matt Dillon Message-Id: <200103091811.f29IBXd12334@earth.backplane.com> To: Paul Herman Cc: Jesper Skriver , Dan Phoenix , Subject: Re: systat -vmstat or iostat IO help References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :About a year ago, I was looking through the VM code, and saw that the :'re' field in vmstat is just Cache reactivations, and not both :Inactive & Cache. I just figured it was how it was supposed to be. :Could it be that 're' should include *all* reactivations? : :If so, would I be correct in suggesting: Hmm. I think there might be some gotchas there. The definition I wrote down in my last email wasn't correct... it is in fact only PQ_CACHE pages for reactivations and that's mainly because reactivations are supposed to be an indication that heavier paging is occuring... that pages are being plucked (and saved) from the garbage heap. Counting inactive->active page transitions doesn't give you quite the same formula because the system often deactivates pages on a whim. With reactivations we want to know about pages being saved from destruction at the last moment. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 10:20: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (ashto-0006.sjc.ca.bbnow.net [24.219.121.199]) by hub.freebsd.org (Postfix) with ESMTP id EFCA737B71A for ; Fri, 9 Mar 2001 10:19:52 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f29IKls05981; Fri, 9 Mar 2001 10:20:47 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103091820.f29IKls05981@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point In-reply-to: Your message of "Fri, 09 Mar 2001 12:21:04 EST." <5.0.0.25.0.20010309115846.041255c0@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Mar 2001 10:20:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Ive spoken with Mr Johnson several times. hes the biggest reason that BSDI > > > is what it is. Amazing that hes still there. He has no concept of what the > > > market wants. First he wanted to challenge microsoft (at similar prices) > > > for the server market now he wants to be redhat. funny guy. > > > >If you're unhappy with the results you're getting from Gary, try calling > >Kirk McKusick. Keep kicking people. > > Wait. Isn't "kicking people" what I'm getting beat up for in this thread? Not specifically; it's kicking the *wrong* people, which is usually what gets people upset. Like I said before, you're on the mark with your problem description, just missing it with your solution. At any rate, in case you missed it, Jonathan Lemon has offered to take up the maintenance of the fxp driver, and if you have samples of the offending hardware, you should forward them to him You might want to coordinate with Larry Baird at GTA (lab@gta.com, AFAIR) to make sure you don't double up. I can vouch for Jonathan's reliability and competence; I've also sent him hardware in the past with good results. > I dont call BSDI (anymore). Its generally a waste of time. I wish I could offer anything in their defense. 8( Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 10:21: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (ashto-0006.sjc.ca.bbnow.net [24.219.121.199]) by hub.freebsd.org (Postfix) with ESMTP id E2F4D37B718 for ; Fri, 9 Mar 2001 10:21:04 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f29INLs06070; Fri, 9 Mar 2001 10:23:21 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103091823.f29INLs06070@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Sam Leffler" Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point In-reply-to: Your message of "Fri, 09 Mar 2001 09:46:35 PST." <09d901c0a8c0$e2bfed30$24a6d4d1@melange> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Mar 2001 10:23:21 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What board is this? If this is the board I think it is, it's a Supermicro P6DLE dual Slot-1 motherboard with an integrated Intel 82559 (no external PHY). (I had this board for some time before I gave it to David, it was originally donated to FTL by Bob Willcox.) > Sam > > ----- Original Message ----- > From: "David O'Brien" > To: "Alex Zepeda" > Cc: > Sent: Friday, March 09, 2001 4:42 AM > Subject: Re: if_fxp - the real point > > > > On Thu, Mar 08, 2001 at 06:13:07PM -0800, Alex Zepeda wrote: > > > However, there *ARE* some of us who aren't intimate with your fxp > > > problems. > > > > The problem does exist. I have a board that the `fxp' driver splits this > > out for: > > > > fxp0: warning: unsupported PHY, type = 17, addr = 2 > > fxp1: warning: unsupported PHY, type = 17, addr = 2 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 10:28:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ceasefire.bitstream.net (ceasefire.bitstream.net [216.243.128.220]) by hub.freebsd.org (Postfix) with SMTP id E2F7F37B718 for ; Fri, 9 Mar 2001 10:28:09 -0800 (PST) (envelope-from airboss@bitstream.net) Received: (qmail 82679 invoked from network); 9 Mar 2001 18:28:07 -0000 Received: from unknown (HELO dmitri.bitstream.net) (216.243.132.33) by ceasefire with SMTP; 9 Mar 2001 18:28:07 -0000 Date: Fri, 9 Mar 2001 12:17:51 -0600 (CST) From: Dan Debertin To: Mike Smith Cc: Sam Leffler , "hackers@FreeBSD.ORG" Subject: Re: if_fxp - the real point In-Reply-To: <200103091823.f29INLs06070@mass.dis.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, 9 Mar 2001, Mike Smith wrote: > > What board is this? > > If this is the board I think it is, it's a Supermicro P6DLE dual Slot-1 > motherboard with an integrated Intel 82559 (no external PHY). I've worked with this board before (don't have any on hand anymore). I remember getting the "unsupported PHY" error on `ifconfig fxpX up'; the interface worked tolerably apart from spitting out the error, although it was not possible to get or see the media via ifconfig. I traded them all in for L440GX+'s, though, so I can't send any, unfortunately. Dan Debertin -- ++ Unix is the worst operating system, except for all others. ++ Dan Debertin ++ Senior Systems Administrator ++ Bitstream Underground, LLC ++ airboss@bitstream.net ++ (612)321-9290 x108 ++ GPG Fingerprint: 0BC5 F4D6 649F D0C8 D1A7 CAE4 BEF4 0A5C 300D 2387 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 10:31:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 99CF337B71A for ; Fri, 9 Mar 2001 10:31:54 -0800 (PST) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id D835C317C; Fri, 9 Mar 2001 18:31:59 +0000 (GMT) Date: Fri, 9 Mar 2001 18:31:59 +0000 From: Josef Karthauser To: Luigi Rizzo Cc: Poul-Henning Kamp , hackers@FreeBSD.ORG Subject: Re: howto access an oddly shaped partition on a floppy ? Message-ID: <20010309183159.C761@tao.org.uk> References: <27657.984135635@critter> <200103091205.NAA49206@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="qtZFehHsKgwS5rPz" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103091205.NAA49206@info.iet.unipi.it>; from luigi@info.iet.unipi.it on Fri, Mar 09, 2001 at 01:05:58PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --qtZFehHsKgwS5rPz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 09, 2001 at 01:05:58PM +0100, Luigi Rizzo wrote: > > It would be possible to teach the floppy driver that cyl 0-9 has > > 18 sectors while cyl10-81 has 21. >=20 > this would only work after the kernel has control, and the kernel > needs far more than 10 cylinders... What about /boot/loader? Does that use the bios also? Can't we build one with a modified fd0 in it? Joe --qtZFehHsKgwS5rPz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqpIZ8ACgkQXVIcjOaxUBbFGACfSxOMWA9ubpFHayHxwq2cLdRD XSAAoJi6zB51ozp5Ebd/wOsX2qRdUKk1 =c8XU -----END PGP SIGNATURE----- --qtZFehHsKgwS5rPz-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 10:58:37 2001 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 3C7BA37B71A for ; Fri, 9 Mar 2001 10:58:34 -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 TAA52748; Fri, 9 Mar 2001 19:56:30 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103091856.TAA52748@info.iet.unipi.it> Subject: Re: howto access an oddly shaped partition on a floppy ? In-Reply-To: <20010309183159.C761@tao.org.uk> from Josef Karthauser at "Mar 9, 2001 06:31:59 pm" To: Josef Karthauser Date: Fri, 9 Mar 2001 19:56:29 +0100 (CET) Cc: Poul-Henning Kamp , 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 > > this would only work after the kernel has control, and the kernel > > needs far more than 10 cylinders... > > What about /boot/loader? Does that use the bios also? Can't we build > one with a modified fd0 in it? yes it uses the bios, and it is large enough (100+ KB compressed if you include forth, ~70KB without) to kill most of the savings coming from this trick. cheers luigi, who has been fighting with space on picobsd images for a while :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 12: 7: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 16B0337B71F; Fri, 9 Mar 2001 12:06:36 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f29K6Sh01668; Fri, 9 Mar 2001 15:06:28 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 9 Mar 2001 15:06:27 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Walter Goralski Cc: "'freebsd-hackers@freebsd.org'" , "'freebsd-net@freebsd.org'" Subject: Re: Generating SYN packets. 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 Generally speaking, the most portable way to generate IP packets is to do so using the raw IP socket interface. However, I've also successfully generated packets using IPDIVERT, BPF, and custom kernel modules :-). I found the IPDIVERT performed quite nicely and was useful for exploring firewall rules, as you can reinsert packets at arbitrary points in the ruleset. The key elements of the process involve opening an appropriate raw socket, generating the TCP SYN packet, and then sending the packet out on the raw socket. I'm including excerpts of appropriate code below. If you decide to use some of it, feel free to attach the 2-clause BSD license at the bottom of the file to your resulting code. :-) Opening the socket is fairly straight-forward: socket_raw = socket(PF_INET, SOCK_RAW, IPPROTO_RAW); if (socket_raw == -1) { perror("socket"); return (-1); } There are a few socket options you should sec. This includes IP_OPTIONS to disable any existing IP options: error = setsockopt(socket_raw, IPPROTO_IP, IP_OPTIONS, NULL, 0); if (error) { perror("setsockopt"); return (-1); } Also, IP_HDRINCL to indicate to the IP stack that you're going to include a complete IP header in your packet, so it shouldn't prepend one: int ip_hdrincl = 1; error = setsockopt(socket_raw, IPPROTO_IP, IP_HDRINCL, (char *)&ip_hdrincl, sizeof(ip_hdrincl)); if (error) { perror("setsockopt"); exit(-1); } Depending on how long you're going to have the socket open for, you may want to close the read component of the socket or the buffers there will fill up with other IP garbage coming off the network, including ICMP, etc. error = shutdown(socket_raw, SHUT_RD); if (error) { perror("shutdown"); exit(-1); } Assembling the TCP packet is the more tricky part. There are two important parts: first, filling in the necessary IP and TCP header information, and second, generating the necessary checksums. You can also optionally throw in TCP options, such as MSS negotiation, SACK negotiation, and things like ECN support. Here's some pseudo-code that covers some of this, but you'll need to tweak it as needed. It assumes that the provided struct in_addr's are already in network byte order, but not the port numbers: struct tcphdr_pseudo { u_long thp_from; u_long thp_to; char thp_zero; char thp_proto; u_short thp_len; struct tcphdr thp_tcphdr; }; ... char *buf; int buflen; struct ip *ip; struct tcphdr *tcphdr; struct tcphdr_pseudo tcphdr_pseudo; bzero(buf, buflen); ip = (struct ip *) buf; tcphdr = (struct tcphdr *) (ip + 1); ip->ip_tos = 0; ip->ip_off = 0; ip->ip_p = IPPROTO_TCP; ip->ip_hl = sizeof(struct ip) >> 2; ip->ip_v = 4; ip->ip_len = ntohs(htons(sizeof(struct ip) + sizeof(struct tcphdr))); ip->ip_src = from; ip->ip_dst = to; ip->ip_ttl = 255; ip->ip_sum = 0; ip->ip_id = random(); I usually borrow the IP checksumming routing from /sbin/ping, sticking it in a seperate source file, and naming the function in_cksum(), taking two arguments: a pointer to the data, and size of the data. Generate the IP-layer checksum first. ip->ip_sum = in_cksum((u_short *)ip, sizeof(struct ip)); Now fill in the TCP header. memset(tcphdr, '\0', sizeof(*tcphdr)); tcphdr->th_sport = htons(12312); tcphdr->th_dport = htons(toport); tcphdr->th_seq = htonl(123123123); tcphdr->th_ack = 0; tcphdr->th_off = 5; tcphdr->th_flags = TCP_SYN; tcphdr->th_win = 1024; /* arbitrary */ tcphdr->th_urp = 0; tcphdr->th_sum = 0; Next, you'll need to generate the TCP checksum -- to do this, fill in the pseudo-header using the same fields as the real TCP and IP headers, and set the TCP header checksum to the in_cksum() of the psuedo-header: tcphdr_pseudo.thp_from = ip->ip_src.s_addr; tcphdr_pseudo.thp_to = ip->ip_dst.s_addr; tcphdr_pseudo.thp_zero = 0; tcphdr_pseudo.thp_tcphdr = *tcphdr; tcphdr_pseudo.thp_proto = IPPROTO_TCP; tcphdr_pseudo.thp_len = htons(sizeof(struct tcphdr)); tcphdr->th_sum = in_cksum((u_short *) &tcphdr_pseudo, sizeof(tcphdr_pseudo)); The final length of the packet is sizeof(struct ip) + sizeof(struct tcphdr). Note that I did not initialize the MSS TCP option, and that the window size I selected is probably inappropriate. Finally, I want to send the packet out over the previously opened raw socket: int outlen; outlen = sendto(socket_raw, buf, len, 0, (struct sockaddr *) sa, sizeof(*sa)); if (outlen != len) perror("sendto"); As noted above, a license is attached below. This is fairly straight-forward code, and you can probably find similar stuff in various Stevens books, which I would highly recommend as a source of further information. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services /*- * Copyright (c) 1999, 2000, 2001 Robert N. M. Watson * All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * $FreeBSD: $ */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 13:56:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from panther.cs.ucla.edu (Panther.CS.UCLA.EDU [131.179.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 136C437B718 for ; Fri, 9 Mar 2001 13:56:04 -0800 (PST) (envelope-from joe@CS.UCLA.EDU) Received: from localhost (joe@localhost) by panther.cs.ucla.edu (8.9.1/UCLACS-5.0) with ESMTP id NAA12092 for ; Fri, 9 Mar 2001 13:55:56 -0800 (PST) Date: Fri, 9 Mar 2001 13:55:56 -0800 (PST) From: Joe Albowicz To: Subject: aic7xxx driver & SCBs 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'd like to ask if anyone can share any knowledge about how/if the number of SCBs affects performace for scsi drives. Also I would like to be able to configure the number of SCBs that the scsi driver uses. With Linux this parameter for the aic7xxx driver can be configured via "make menuconfig" step of the kernel build process. Is there a similiar way to configure this varible for BSD? Or do I have to start hacking on the driver code? Thanks in advance. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 14: 1:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id DF02837B719 for ; Fri, 9 Mar 2001 14:01:25 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f29M1PW09247; Fri, 9 Mar 2001 14:01:25 -0800 (PST) Date: Fri, 9 Mar 2001 14:01:25 -0800 From: Alfred Perlstein To: Joe Albowicz Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: aic7xxx driver & SCBs Message-ID: <20010309140124.V18351@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from joe@CS.UCLA.EDU on Fri, Mar 09, 2001 at 01:55:56PM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Joe Albowicz [010309 13:56] wrote: > > Hi, > > I'd like to ask if anyone can share any knowledge about how/if the number > of SCBs affects performace for scsi drives. > > Also I would like to be able to configure the number of SCBs that the scsi > driver uses. With Linux this parameter for the aic7xxx driver can be > configured via "make menuconfig" step of the kernel build process. Is > there a similiar way to configure this varible for BSD? Or do I have to > start hacking on the driver code? I wouldn't worry about it, the driver auto tunes these things. -- -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 Fri Mar 9 14: 3:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp018.mail.yahoo.com (smtp018.mail.yahoo.com [216.136.174.115]) by hub.freebsd.org (Postfix) with SMTP id 8FECB37B718 for ; Fri, 9 Mar 2001 14:03:19 -0800 (PST) (envelope-from averycfay@yahoo.com) Received: from 064-184-209-204.inaddr.vitts.com (HELO tiger) (64.184.209.204) by smtp.mail.vip.sc5.yahoo.com with SMTP; 9 Mar 2001 22:03:19 -0000 X-Apparently-From: Message-ID: <060701c0a8e4$aee61ce0$0101a8c0@tiger> From: "Avery Fay" To: Subject: Getting started (hacking that is) Date: Fri, 9 Mar 2001 17:02:49 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everyone, I am interested in contributing code to the FreeBSD project, specifically the kernel but I am not opposed to helping out with user applications if they are in dire need of improvements. To preface my request for assistance, I should tell everyone that I am young (18) without extensive programming experience although I have held two jobs programming in C and feel fairly comfortable doing so. Although I've never worked on a kernel I am currently reading "The Design and Implementation of the 4.4BSD OS" and "Modern Operating Systems: Design and Implementation" so hopefully I have a rough understanding of the theory. I have heard that writing or improving device drivers if one of the easier methods to introduce oneself to kernel programming. Unfortunately (or fortunately I guess), all of my hardware works with FreeBSD. I guess my question then is this: Can someone suggest a cheap piece of hardware with atleast some documentation that FreeBSD is sourly lacking a driver for? Are there any other relatively "easy" ways to learn how to code kernels? (i.e. not writing a device driver) Finally, I'd rather not work on the fxp driver based on the recent quite hostile discussion on this list =). And if I'm totally out of line sending this message to this list, please point me in the write direction or just tell me to shutup and go away =). Thanks in advance, Avery Fay _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 14: 9: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 6831937B718 for ; Fri, 9 Mar 2001 14:09:01 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f29M90X09452; Fri, 9 Mar 2001 14:09:00 -0800 (PST) Date: Fri, 9 Mar 2001 14:09:00 -0800 From: Alfred Perlstein To: Avery Fay Cc: hackers@FreeBSD.ORG Subject: Re: Getting started (hacking that is) Message-ID: <20010309140900.W18351@fw.wintelcom.net> References: <060701c0a8e4$aee61ce0$0101a8c0@tiger> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <060701c0a8e4$aee61ce0$0101a8c0@tiger>; from averycfay@yahoo.com on Fri, Mar 09, 2001 at 05:02:49PM -0500 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Avery Fay [010309 14:03] wrote: > Hello everyone, > > I am interested in contributing code to the FreeBSD project, specifically > the kernel but I am not opposed to helping out with user applications if > they are in dire need of improvements. To preface my request for assistance, > I should tell everyone that I am young (18) without extensive programming > experience although I have held two jobs programming in C and feel fairly > comfortable doing so. Although I've never worked on a kernel I am currently > reading "The Design and Implementation of the 4.4BSD OS" and "Modern > Operating Systems: Design and Implementation" so hopefully I have a rough > understanding of the theory. > > I have heard that writing or improving device drivers if one of the easier > methods to introduce oneself to kernel programming. Unfortunately (or > fortunately I guess), all of my hardware works with FreeBSD. I guess my > question then is this: Can someone suggest a cheap piece of hardware with > atleast some documentation that FreeBSD is sourly lacking a driver for? Are > there any other relatively "easy" ways to learn how to code kernels? (i.e. > not writing a device driver) > > Finally, I'd rather not work on the fxp driver based on the recent quite > hostile discussion on this list =). And if I'm totally out of line sending > this message to this list, please point me in the write direction or just > tell me to shutup and go away =). Go here: http://www.FreeBSD.org/cgi/query-pr-summary.cgi Submit fixes. :) -- -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 Fri Mar 9 14: 9:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (ashto-0006.sjc.ca.bbnow.net [24.219.121.199]) by hub.freebsd.org (Postfix) with ESMTP id 27F1B37B728 for ; Fri, 9 Mar 2001 14:09:19 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f29MALs09079; Fri, 9 Mar 2001 14:10:21 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103092210.f29MALs09079@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Joe Albowicz Cc: freebsd-hackers@freebsd.org Subject: Re: aic7xxx driver & SCBs In-reply-to: Your message of "Fri, 09 Mar 2001 13:55:56 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Mar 2001 14:10:21 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe; it looks like you have some funny ideas about something that's not actually very relevant. I assume that you have already gone and bought Monster Cable(tm) SCSI cables, and that you have the special oxygen-free-copper SCSI controller PCBs, because none of this is going to mean anything unless you have. > I'd like to ask if anyone can share any knowledge about how/if the number > of SCBs affects performace for scsi drives. If you don't have enough SCBs, you can't deliver enough commands to your drive(s) to keep them busy. > Also I would like to be able to configure the number of SCBs that the scsi > driver uses. With Linux this parameter for the aic7xxx driver can be > configured via "make menuconfig" step of the kernel build process. Is > there a similiar way to configure this varible for BSD? Or do I have to > start hacking on the driver code? You can't do that. Firstly, there isn't a "SCSI driver", secondly there are several different sorts of objects that map to what you, coming from the Linux world, would call an SCB, and thirdly, the CAM subsystem components have a much better idea than you do how many of these that are needed, and will allocate them as necessary. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 14:12:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 2384337B71B; Fri, 9 Mar 2001 14:12:50 -0800 (PST) Subject: Re: if_fxp - the real point In-Reply-To: <200103091823.f29INLs06070@mass.dis.org> from Mike Smith at "Mar 9, 2001 10:23:21 am" To: msmith@freebsd.org (Mike Smith) Date: Fri, 9 Mar 2001 14:12:50 -0800 (PST) Cc: 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 Message-Id: <20010309221250.2384337B71B@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Grrrrr. (Yes, that's a bad omen. Get the women and children to safety now.) (On second thought, leave the women.) I think there's one important point that a lot of you are missing here, which is GETTING DOCUMENTATION. I've seen a couple people suggest that they'd be willing to donate time/code/etc to fix the fxp driver, but I strongly suspect that most of these people don't have the slighest idea what's really involved. You can't just look at the driver code, poke at it for a while, and expect the answer to fall out: you need the damn manual for it. And you can't get that from Intel because they're NDA nazis. (Johnathan Lemon is the one exception to this since he apparently has ways to gain access to Intel documentation thanks to his job. I think he's still subject to NDAs though, so I question just how much help he can really provide. Not that I don't encourge him to do an end run around Intel wherever he can, of course.) I see lots of finger-pointing here, yet nobody seems to be prepared to fault the real culprit, namely Intel. Nobody sends nasty e-mails to their Intel sales reps or other high mucky-mucks taking them to task over their nonsensical NDA requirements. Nobody makes any effort to explain to them just how much more sense it would make and how much more money they would earn by simply preparing some decent manuals for a change and not being so anal-retentive about releasing them. If everyone would concentate their energy on this for a change instead of sniping at each other, I would be a happy man. (Alright, I'm exagerating. It would take significantly more than that to make me happy, but that's a rant for another day.) Right now I'd like to be able to write some more NIC drivers, but I have the following problems: Tigon 3: ------- 3Com now owns Alteon's gigabit NIC business, and Alteon's open driver development program seems to have been killed off. To make matters worse, the Tigon 3 seems to actually be a Broadcom product called the BCM 5700. Broadcom an even bigger NDA nazi than Intel, if you can believe that, and 3Com usually has no idea what's going on with regards to hardware that it it didn't built itself. It also has a tendency to drag its feet when it comes to putting together decent manuals for release to non-NDA partners. 3Com 3CR990 ----------- This is 3Com's ARM-based 10/100 NIC that can do hardware encryption. I have no idea how to get programming info for this NIC out of 3Com without NDA. Level1 LXT1000 -------------- This is a gigabit MAC which D-Link is shipping on their gigabit ethernet cards. Intel owns Level1 now, and documentation for the LXT1000 controller is nowhere to be found. Broadcom 10mbps homePNA ----------------------- I tried navigating Broadcom's sales/support maze looking for info on this chip, they told me they weren't interested in releasing any info without NDA at this time. From what I've been told, this chip has some other functionality built into it which allows it to be used for more than just homePNA networking, and Broadcom simply doesn't want to tell people about it. I don't care one way or the other. USB 802.11 wireless NICs ----------------- Somebody pointed one of these out to me recently, I think they're a D-Link product. Again, I don't know who makes them or where to find manuals. No documentation, no cookie. There's probably other cases here that I've forgotten. Regardless, it really cheeses me off when people ask me "hey, I just saw such-and-such card that looks really neat; if I get you one, can you write a driver for it? I'd be happy to test it for you." Having a sample card doesn't do a damn thing for me THE STINKING PROGRAMMING MANUAL. If I *had* the manuals for these things, I'd be probably already be working on drivers! "But Bill, you work for BSDi now. Can't they get you manuals?" Working for BSDi is irrelevant: I can't sign any NDAs if I want to release driver source, and I do want to release the source. And there isn't a designated person at BSDi that I can turn to to help turn up the heat on recalcitrant vendors. I'm not willing to go sneaking around and mooching these things from secret sources since it just perpetuates the officially sanctioned vendor stupidity. I don't want to have meetings, negotiations or "strategic partnerships," I just want the stupid programming manuals without NDAs. A few other things while I'm here. D-Link, LinkSys and Netgear do *NOT* make their own 10/100 NIC controller chips. They buy them from other companies. In some cases, they buy the whole card and simply stamp their name on it. There were at least 4 companies at one point all selling the exact same PNIC 82c169 card under different names. LinkSys is currently using the ADMtek Centaur PCI and Cardbus chips in their 10/100 NICs. Netgear is using the NatSemi DP83815 chipset on their FA311 and FA312 cards. D-Link uses RealTek 8139 and VIA Rhine II chips depending on just which model NIC you happen to get. The D-Link DFE-570TX quad port card uses the Intel 21143, and it's dirt cheap compared to the ZNYX and Adaptec cards of similar design, assuming you can find them. The interesting thign is that *all* of these chips have manuals available from their respective vendors WITHOUT NDAs, so I don't want to hear people telling me that NDAs are "just the price of doing business." I have stacks of unencumbered manuals here, and I'd be more than happy to smack people upside the head with them to prove them wrong. I'm getting really tired of being the only one beating this drum. I keep telling people to complain to whoever will listen inside these companies in the hopes that *somebody* will get the point. I also keep hoping that other people will appear and demonstrate some driver fu so that I don't have to be the only one people will turn to when they have a NIC that they want supported. I'm only one person, not a code generating machine, and I don't spend 24 hours a day agonizing over how I'm going to support every single network card on the planet. I tried it and it sucked, and not getting any support from the really big vendors or from inside BSDi doesn't make it any more appealing. All I can say is, Johnathan, I'm glad it's you and not me. And Dennis, you deserve a working driver. I really hope you get it. Part of me even wishes I could fix the problems for you, but my hands are tied and my patience has word thin. -Bill ============================================================================= -Bill Paul (925) 691-2800 | Systems Programmer, Master of Unix-Fu wpaul@osd.bsdi.com | BSDi Open Source Solutions ============================================================================= "I like zees guys. Zey are fonny guys. Just keel one of zem." -- The 3 Amigos ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 14:37:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dove.angel.org (dsl-64-194-138-85.telocity.com [64.194.138.85]) by hub.freebsd.org (Postfix) with ESMTP id 9FDA637B718 for ; Fri, 9 Mar 2001 14:37:18 -0800 (PST) (envelope-from dp@penix.org) Received: from penix.org (Toronto-ppp220704.sympatico.ca [64.228.103.29]) by dove.angel.org (8.11.1/8.11.1) with ESMTP id f29MaQG40096 for ; Fri, 9 Mar 2001 17:36:27 -0500 (EST) (envelope-from dp@penix.org) Message-ID: <3AA95B84.E7664C6@penix.org> Date: Fri, 09 Mar 2001 17:39:00 -0500 From: Paul Halliday X-Mailer: Mozilla 4.75 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: if_fxp - the real point References: <20010309221250.2384337B71B@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. Of the 8 machines that I own, all of the NIC's work just fine. Thank you for doing such a great job! To the rest of you: read the hardware.txt. Use a supported card or go suck a rotten egg. Bill Paul wrote: > > Grrrrr. > > (Yes, that's a bad omen. Get the women and children to safety now.) > > (On second thought, leave the women.) > > I think there's one important point that a lot of you are missing here, > which is GETTING DOCUMENTATION. I've seen a couple people suggest that > they'd be willing to donate time/code/etc to fix the fxp driver, but I > strongly suspect that most of these people don't have the slighest idea > what's really involved. You can't just look at the driver code, poke at > it for a while, and expect the answer to fall out: you need the damn > manual for it. And you can't get that from Intel because they're NDA > nazis. (Johnathan Lemon is the one exception to this since he apparently > has ways to gain access to Intel documentation thanks to his job. I think > he's still subject to NDAs though, so I question just how much help he > can really provide. Not that I don't encourge him to do an end run around > Intel wherever he can, of course.) > > I see lots of finger-pointing here, yet nobody seems to be prepared to > fault the real culprit, namely Intel. Nobody sends nasty e-mails to > their Intel sales reps or other high mucky-mucks taking them to task over > their nonsensical NDA requirements. Nobody makes any effort to explain to > them just how much more sense it would make and how much more money they > would earn by simply preparing some decent manuals for a change and not > being so anal-retentive about releasing them. If everyone would concentate > their energy on this for a change instead of sniping at each other, I would > be a happy man. > > (Alright, I'm exagerating. It would take significantly more than that to > make me happy, but that's a rant for another day.) > > Right now I'd like to be able to write some more NIC drivers, but I have > the following problems: > > Tigon 3: > ------- > 3Com now owns Alteon's gigabit NIC business, and Alteon's open driver > development program seems to have been killed off. To make matters worse, > the Tigon 3 seems to actually be a Broadcom product called the BCM 5700. > Broadcom an even bigger NDA nazi than Intel, if you can believe that, and > 3Com usually has no idea what's going on with regards to hardware that it > it didn't built itself. It also has a tendency to drag its feet when it > comes to putting together decent manuals for release to non-NDA partners. > > 3Com 3CR990 > ----------- > This is 3Com's ARM-based 10/100 NIC that can do hardware encryption. > I have no idea how to get programming info for this NIC out of 3Com without > NDA. > > Level1 LXT1000 > -------------- > This is a gigabit MAC which D-Link is shipping on their gigabit ethernet > cards. Intel owns Level1 now, and documentation for the LXT1000 controller > is nowhere to be found. > > Broadcom 10mbps homePNA > ----------------------- > I tried navigating Broadcom's sales/support maze looking for info on > this chip, they told me they weren't interested in releasing any info > without NDA at this time. From what I've been told, this chip has some > other functionality built into it which allows it to be used for more > than just homePNA networking, and Broadcom simply doesn't want to tell > people about it. I don't care one way or the other. > > USB 802.11 wireless NICs > ----------------- > Somebody pointed one of these out to me recently, I think they're a > D-Link product. Again, I don't know who makes them or where to find > manuals. No documentation, no cookie. > > There's probably other cases here that I've forgotten. Regardless, it > really cheeses me off when people ask me "hey, I just saw such-and-such > card that looks really neat; if I get you one, can you write a driver > for it? I'd be happy to test it for you." Having a sample card doesn't > do a damn thing for me THE STINKING PROGRAMMING MANUAL. If I *had* the > manuals for these things, I'd be probably already be working on drivers! > > "But Bill, you work for BSDi now. Can't they get you manuals?" Working for > BSDi is irrelevant: I can't sign any NDAs if I want to release driver > source, and I do want to release the source. And there isn't a designated > person at BSDi that I can turn to to help turn up the heat on recalcitrant > vendors. I'm not willing to go sneaking around and mooching these things > from secret sources since it just perpetuates the officially sanctioned > vendor stupidity. I don't want to have meetings, negotiations or "strategic > partnerships," I just want the stupid programming manuals without NDAs. > > A few other things while I'm here. D-Link, LinkSys and Netgear do *NOT* > make their own 10/100 NIC controller chips. They buy them from other > companies. In some cases, they buy the whole card and simply stamp their > name on it. There were at least 4 companies at one point all selling the > exact same PNIC 82c169 card under different names. LinkSys is currently > using the ADMtek Centaur PCI and Cardbus chips in their 10/100 NICs. > Netgear is using the NatSemi DP83815 chipset on their FA311 and FA312 > cards. D-Link uses RealTek 8139 and VIA Rhine II chips depending on just > which model NIC you happen to get. The D-Link DFE-570TX quad port card > uses the Intel 21143, and it's dirt cheap compared to the ZNYX and > Adaptec cards of similar design, assuming you can find them. The > interesting thign is that *all* of these chips have manuals available > from their respective vendors WITHOUT NDAs, so I don't want to hear > people telling me that NDAs are "just the price of doing business." I > have stacks of unencumbered manuals here, and I'd be more than happy to > smack people upside the head with them to prove them wrong. > > I'm getting really tired of being the only one beating this drum. I keep > telling people to complain to whoever will listen inside these companies > in the hopes that *somebody* will get the point. I also keep hoping that > other people will appear and demonstrate some driver fu so that I don't > have to be the only one people will turn to when they have a NIC that they > want supported. I'm only one person, not a code generating machine, and > I don't spend 24 hours a day agonizing over how I'm going to support > every single network card on the planet. I tried it and it sucked, and > not getting any support from the really big vendors or from inside BSDi > doesn't make it any more appealing. > > All I can say is, Johnathan, I'm glad it's you and not me. And Dennis, > you deserve a working driver. I really hope you get it. Part of me even > wishes I could fix the problems for you, but my hands are tied and my > patience has word thin. > > -Bill > > ============================================================================= > -Bill Paul (925) 691-2800 | Systems Programmer, Master of Unix-Fu > wpaul@osd.bsdi.com | BSDi Open Source Solutions > ============================================================================= > "I like zees guys. Zey are fonny guys. Just keel one of zem." -- The 3 Amigos > ============================================================================= > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Paul H. ============================================================================ Don't underestimate the power of stupid people in large groups. Brute force is the last resort of the incompetent. GPG Key fingerprint: 2D7C A7E2 DB1F EA5F 8C6F D5EC 3D39 F274 4AA3 E8B9 Web: http://www3.sympatico.ca/transmogrify Public Key available here: http://www3.sympatico.ca/transmogrify/dp.txt ============================================================================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 14:51:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6383437B718; Fri, 9 Mar 2001 14:51:55 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id XAA66180; Fri, 9 Mar 2001 23:51:54 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103092251.XAA66180@freebsd.dk> Subject: Re: if_fxp - the real point In-Reply-To: <20010309221250.2384337B71B@hub.freebsd.org> from Bill Paul at "Mar 9, 2001 02:12:50 pm" To: wpaul@FreeBSD.ORG (Bill Paul) Date: Fri, 9 Mar 2001 23:51:54 +0100 (CET) Cc: msmith@FreeBSD.ORG (Mike Smith), 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 Bill Paul wrote: > "But Bill, you work for BSDi now. Can't they get you manuals?" Working for > BSDi is irrelevant: I can't sign any NDAs if I want to release driver > source, and I do want to release the source. And there isn't a designated > person at BSDi that I can turn to to help turn up the heat on recalcitrant > vendors. I'm not willing to go sneaking around and mooching these things > from secret sources since it just perpetuates the officially sanctioned > vendor stupidity. I don't want to have meetings, negotiations or "strategic > partnerships," I just want the stupid programming manuals without NDAs. I hear you! I have the same problems getting ATA controller/device docs out of the vendors, but sometimes it helps trying from another angle. One example is Promise, I mailed and phoned them for about a year, and got exactly nothing back, but it took Jeroen (Asmodai) one mail to get thier attention AND docs (thanks!), the morale being that sometimes it helps getting other people involved. Please understand that I dont mean that everybody and his dog should be mail bombing a vendor to get docs, that we leave for the other guys :)... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 14:58: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from front5m.grolier.fr (front5m.grolier.fr [195.36.216.55]) by hub.freebsd.org (Postfix) with ESMTP id 990A737B718; Fri, 9 Mar 2001 14:58:03 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from nas1-207.cgy.club-internet.fr (nas1-207.cgy.club-internet.fr [195.36.197.207]) by front5m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA28386; Fri, 9 Mar 2001 23:57:59 +0100 (MET) Date: Fri, 9 Mar 2001 21:47:45 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Mike Smith Cc: Joe Albowicz , freebsd-hackers@FreeBSD.ORG Subject: Re: aic7xxx driver & SCBs In-Reply-To: <200103092210.f29MALs09079@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Mar 2001, Mike Smith wrote: > Joe; it looks like you have some funny ideas about something that's not= =20 > actually very relevant. I assume that you have already gone and bought= =20 > Monster Cable(tm) SCSI cables, and that you have the special=20 > oxygen-free-copper SCSI controller PCBs, because none of this is going to= =20 > mean anything unless you have. Pardon and sorry, Mike. It is rather your reply that looks funny to me. The number of SCBs in (both) the Linux and FreeBSD aic7xxx driver(s) is very relevant in my opinion given that it is just the maximum of SCSI command contexts the driver can handle (i.e. maximum number of outstanding IOs). > > I'd like to ask if anyone can share any knowledge about how/if the numb= er > > of SCBs affects performace for scsi drives. >=20 > If you don't have enough SCBs, you can't deliver enough commands to your= =20 > drive(s) to keep them busy. Being busy does not imply doing a good job. You can get a device full busy using only 2 simultaneous IOs for this device. Using more can allow the device to perform optimizations based on actual head positions and possibly coalesce data transfers when possible, for example. > > Also I would like to be able to configure the number of SCBs that the s= csi > > driver uses. With Linux this parameter for the aic7xxx driver can be > > configured via "make menuconfig" step of the kernel build process. Is > > there a similiar way to configure this varible for BSD? Or do I have t= o > > start hacking on the driver code? >=20 > You can't do that. Firstly, there isn't a "SCSI driver", secondly there > are several different sorts of objects that map to what you, coming from > the Linux world, would call an SCB, and thirdly, the CAM subsystem > components have a much better idea than you do how many of these that are > needed, and will allocate them as necessary. You should have been more accurate here, in my opinion. Vague explanations= =20 are worse than no explanations at all, in my opinion. The CAM subsystem does not govern the number of SCBs. It only cares about= =20 limiting the number of simultaneous commands, firstly to the value told=20 by SIM and secondly based on device quirks or conditions as QUEUE FULL=20 status returns. The noticeable difference here with Linux is that, under Linux, the device queue depth is tailored by SIM at device discovery time and will not be dynamically adjusted on QUEUE FULL status by the generic SCSI layer. Given that CAM will reduce the device queue depth on QUEUE FULL status and has appropriate quirks tables, SIMs can just announce to CAM large queue depths at initialisation and then rely on CAM for reducing the queue depth if and as needed. Doing the same under Linux can harm unless the SIM is smart enough for doing what CAM is doing under FreeBSD. In brief, SIMs (low level SCSI drivers) under FreeBSD just use to announce to CAM the largest possible queue depths, and so, having some configuration parameter for that seems useless. Btw, your reply let me think that you want to discourage people to hack=20 our source code or to try to understand how it works. Colour me very surprised. :-) G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 15: 3:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id 45A1C37B718 for ; Fri, 9 Mar 2001 15:03:34 -0800 (PST) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.9.0/8.8.7) with ESMTP id XAA10708 for ; Fri, 9 Mar 2001 23:03:33 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Fri, 9 Mar 2001 23:03:33 +0000 (GMT) From: "E.B. Dreger" To: hackers@FreeBSD.ORG Subject: The ideal NIC (Re: if_fxp - the real point) In-Reply-To: <20010309221250.2384337B71B@hub.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 Bear with me and allow me my delusions while I daydream... What with FPGA technology as reasonable as it is, and the amount of hw/sw talent on these lists, maybe people should band together and come up with a NIC? Maybe have native mode + Tulip/PNIC clone compatibility mode. Take a look at www.opencores.org for a start. What production volumes are required before ASICs are feasible? What about having a FreeBSD CDROM + NIC bundle featuring whatever card gets designed? If ya can't join 'em, beat 'em. Okay. Back to work and reality. :-) Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division E-Mail: eddy@everquick.net Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 15:10:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 7E01C37B71A for ; Fri, 9 Mar 2001 15:10:15 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.2/8.11.0) with ESMTP id f29N9na27176; Fri, 9 Mar 2001 18:09:49 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200103092309.f29N9na27176@whizzo.transsys.com> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Luigi Rizzo Cc: Josef Karthauser , Poul-Henning Kamp , hackers@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: howto access an oddly shaped partition on a floppy ? References: <200103091856.TAA52748@info.iet.unipi.it> In-reply-to: Your message of "Fri, 09 Mar 2001 19:56:29 +0100." <200103091856.TAA52748@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Mar 2001 18:09:49 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > this would only work after the kernel has control, and the kernel > > > needs far more than 10 cylinders... > > > > What about /boot/loader? Does that use the bios also? Can't we build > > one with a modified fd0 in it? > > yes it uses the bios, and it is large enough (100+ KB compressed if > you include forth, ~70KB without) to kill most of the savings coming > from this trick. So how about a options flag on the floppy driver which translates block addresses beyond 1440K into the "extra" sectors? I don't know that there's a "clean" way insert that into the driver, just glancing at the code.. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 15:23:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id BA22637B719 for ; Fri, 9 Mar 2001 15:23:17 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f29NMu434554; Fri, 9 Mar 2001 15:22:56 -0800 (PST) (envelope-from dillon) Date: Fri, 9 Mar 2001 15:22:56 -0800 (PST) From: Matt Dillon Message-Id: <200103092322.f29NMu434554@earth.backplane.com> To: "E.B. Dreger" Cc: hackers@FreeBSD.ORG Subject: Re: The ideal NIC (Re: if_fxp - the real point) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :What production volumes are required before ASICs are feasible? What :about having a FreeBSD CDROM + NIC bundle featuring whatever card gets :designed? : :If ya can't join 'em, beat 'em. : :Okay. Back to work and reality. :-) : :Eddy Designing an ASIC will have an NRE of probably around $50,000, and you'd have to do a run of probably around 10,000 chips (at $1-$2 a chip) for it to even come close to being cost effective. And that's assuming you get the design right the first time. But that's only half the problem. Building the PCI boards themselves in the smallish qantities that we are talking about will be quite expensive. Ultimately you would not be paying much less then you would for a cheap board already on the market (and probably considerably more). An FPGA can be programmed in singles, but they are very expensive to buy in small quantities (lots less then a 1000 chips), and you have all sorts of other issues involved as well including possibly needing to purchase a second chip to help out with the PCI bus, and a serial cmos eprom for chip initialization. And the board, of course. This would probably cost even more then an ASIC. FPGAs also tend to eat a lot of power, and highspeed CMOS FPGAs are very expensive. And, on top of all of that you still need to buy a separate filter / protection block (those black rectangle things you see on ethernet boards), and again those can be quite costly in small quantities. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 15:29:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id AF29D37B71B; Fri, 9 Mar 2001 15:29:31 -0800 (PST) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f29NSkO61063; Fri, 9 Mar 2001 16:28:53 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200103092328.f29NSkO61063@aslan.scsiguy.com> To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: Mike Smith , Joe Albowicz , freebsd-hackers@FreeBSD.ORG Subject: Re: aic7xxx driver & SCBs In-Reply-To: Your message of "Fri, 09 Mar 2001 21:47:45 +0100." Date: Fri, 09 Mar 2001 16:28:46 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >On Fri, 9 Mar 2001, Mike Smith wrote: > >> Joe; it looks like you have some funny ideas about something that's not >> actually very relevant. I assume that you have already gone and bought >> Monster Cable(tm) SCSI cables, and that you have the special >> oxygen-free-copper SCSI controller PCBs, because none of this is going to >> mean anything unless you have. > >Pardon and sorry, Mike. It is rather your reply that looks funny to me. Okay. Everyone take a big breath. My rule of thumb for email is, if you can't reply kindly to someone's question, you shouldn't reply at all. Sometimes I fall shy of that mark too, but I think its a worthy goal for everyone participating on our lists. So, Mike, try to play nice. Okay? As to the original question... SCSI Control Blocks (SCBs) are the controller resources used by the aic7xxx driver to deliver commands. You need to have one SCB for every outstanding transaction the card handles. All cards supported by either Linux or FreeBSD allocate a total of 253 SCBs. This number is *not* configurable on either OS (assuming you are using my driver). One thing that confuses people is the number of SCBs that can be concurrently stored on chip, varies with from chip to chip and sometimes with how the chip is integrated on the MB or HBA. The more hardware SCBs, the better the performance, but due to an SCB paging scheme, the total number of oustanding transactions all controllers support is 253. If you are curious, the driver probe message indicates the number of hardware SCBs and the total number of transactions, like so: aic7899: Wide Channel A, SCSI Id=7, 32/255 SCBs hardware SCBS ==^ ^== total number 2 of the 255 SCBs are reserved for various things hence the actual number of transactions being 253, not 255. If only one nubmer is printed, the hardware and total are equal. The Linux driver allows you to specify the number of transactions that can be queued to any given device on the bus. The default, again if your are using my driver, is to allow up to 253, the maximum the controller supports. The driver will automatically throttle this number based on the capabilities of the individual device. In the FreeBSD environment, this throttling occurs in the SCSI layer, not the controller. So, how many transactions should you allow? To some extent that depends on your workload. For non-sequential I/O (in my opinion the most common scenario), the more tags the merrier. This is why both the Linux and FreeBSD environments default to the maximum number of tags. Some devices, due to limited processing power on the drive or poor firmware engineering do show reduced sequential performance when put under a high tag load. If you know you are only going to do sequential I/O *and* you have the time to experiment with the results, your application might benefit from reducing the number of tags allowed. If you want to change these parameters under FreeBSD, read the camcontrol manpage about the "tags" option. Under linux, as you already know, play with the settings via "make *config". -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 15:32: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gollum.esys.ca (dhcp198-52.esys.ca [198.161.92.52]) by hub.freebsd.org (Postfix) with ESMTP id 03C3537B718 for ; Fri, 9 Mar 2001 15:32:05 -0800 (PST) (envelope-from lyndon@gollum.esys.ca) Received: from localhost (localhost [127.0.0.1]) by gollum.esys.ca (8.11.2/8.11.2) with ESMTP id f29NW4785782 for ; Fri, 9 Mar 2001 16:32:04 -0700 (MST) (envelope-from lyndon@gollum.esys.ca) Message-Id: <200103092332.f29NW4785782@gollum.esys.ca> From: Lyndon Nerenberg Organization: ACI/Messagingdirect X-URL: http://www.messagingdirect.com/ To: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point In-Reply-To: Message from wpaul@FreeBSD.ORG (Bill Paul) of "Fri, 09 Mar 2001 14:12:50 PST." <20010309221250.2384337B71B@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <85774.984180723.1@localhost> Date: Fri, 09 Mar 2001 16:32:04 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think there's one important point that a lot of you are missing here, > which is GETTING DOCUMENTATION. Perhaps a first step towards leaning on the vendors for documentation is to publically declare our support for those vendors who *do* release documentation under reasonable terms. One way to do this is to acknowledge those vendors in the hardware section of the handbook, and encourage people to support them by buying thier products. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 15:33:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A814237B718 for ; Fri, 9 Mar 2001 15:33:56 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA24123; Fri, 9 Mar 2001 15:33:36 -0800 Date: Fri, 9 Mar 2001 15:33:33 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Lyndon Nerenberg Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point In-Reply-To: <200103092332.f29NW4785782@gollum.esys.ca> 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 good. I'd vote for LSI-Logic as being a sterling example of making documentation available. I'd out QLogic and others way down the list as the "don't get it" variety. > > I think there's one important point that a lot of you are missing here, > > which is GETTING DOCUMENTATION. > > Perhaps a first step towards leaning on the vendors for documentation > is to publically declare our support for those vendors who *do* > release documentation under reasonable terms. One way to do this > is to acknowledge those vendors in the hardware section of the > handbook, and encourage people to support them by buying thier > products. > > --lyndon > > 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 Mar 9 15:35:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postal.sdsc.edu (postal.sdsc.edu [132.249.20.114]) by hub.freebsd.org (Postfix) with ESMTP id 3411A37B718 for ; Fri, 9 Mar 2001 15:35:38 -0800 (PST) (envelope-from mjl@SDSC.EDU) Received: from multivac.sdsc.edu (multivac.sdsc.edu [132.249.20.57]) by postal.sdsc.edu (8.9.3/8.9.3/SDSCserver-16) with ESMTP id PAA21337; Fri, 9 Mar 2001 15:35:37 -0800 (PST) Received: from localhost by multivac (8.9.3+Sun/1.11-SolarisClient) with ESMTP id PAA29925; Fri, 9 Mar 2001 15:35:33 -0800 (PST) Date: Fri, 9 Mar 2001 15:35:33 -0800 (PST) From: Matthew Luckie To: Cc: Subject: atexit 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 wondering under what conditions a function specified with atexit() won't get called on FreeBSD when a program terminates. The manual page says it gets called "via exit(3) or via return from the program's main". I take it that the cleanup function won't be called if the program dumps core, or if it is terminated with a kill(1) - or might it? Thanks Matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 15:39:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id B31B737B718 for ; Fri, 9 Mar 2001 15:39:22 -0800 (PST) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f29NdG227303 for ; Fri, 9 Mar 2001 17:39:17 -0600 (CST) Message-Id: <200103092339.f29NdG227303@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: hackers@freebsd.org Subject: Re: atexit In-reply-to: Your message of "Fri, 09 Mar 2001 15:35:33 PST." Date: Fri, 09 Mar 2001 17:39:16 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthe w Luckie writes: >I'm wondering under what conditions a function specified with atexit() >won't get called on FreeBSD when a program terminates. "abnormal" termination. >I take it that the cleanup function won't be called if the program dumps >core, or if it is terminated with a kill(1) - or might it? It shouldn't, in general, or if someone calls _exit(). If the program dies from a signal, that's "abnormal" termination. Note that some signals can be caught, and a program which catches them may choose to exit cleanly, and may thus hit its atexit() registered functions. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 15:46: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from chopper.Poohsticks.ORG (chopper.poohsticks.org [63.227.60.73]) by hub.freebsd.org (Postfix) with ESMTP id 2AB5437B719 for ; Fri, 9 Mar 2001 15:46:06 -0800 (PST) (envelope-from drew@chopper.Poohsticks.ORG) Received: from chopper.Poohsticks.ORG (drew@localhost.poohsticks.org [127.0.0.1]) by chopper.Poohsticks.ORG (8.10.1/8.10.1) with ESMTP id f29Nk0n04208; Fri, 9 Mar 2001 16:46:00 -0700 Message-Id: <200103092346.f29Nk0n04208@chopper.Poohsticks.ORG> To: Matthew Luckie Cc: hackers@FreeBSD.ORG Subject: Re: atexit In-reply-to: Your message of "Fri, 09 Mar 2001 15:35:33 PST." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4204.984181560.1@chopper.Poohsticks.ORG> Date: Fri, 09 Mar 2001 16:46:00 -0700 From: Drew Eckhardt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , mjl@SD SC.EDU writes: >I take it that the cleanup function won't be called if the program dumps >core, Right, unless you dump core by forking a child process and doing it in that context. >or if it is terminated with a kill(1) The function can never be called when some one does a kill -9, although you're free to catch other signals and shutdown gracefully. Terminating with a call to _exit() will also not invoke your function. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 15:49:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id DDDD337B718 for ; Fri, 9 Mar 2001 15:49:11 -0800 (PST) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id 86240595B1; Fri, 9 Mar 2001 17:49:11 -0600 (CST) Date: Fri, 9 Mar 2001 17:49:11 -0600 From: "Michael C . Wu" To: "E.B. Dreger" Cc: hackers@FreeBSD.ORG Subject: Re: The ideal NIC (Re: if_fxp - the real point) Message-ID: <20010309174911.D24830@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20010309221250.2384337B71B@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from eddy+public+spam@noc.everquick.net on Fri, Mar 09, 2001 at 11:03:33PM +0000 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 09, 2001 at 11:03:33PM +0000, E.B. Dreger scribbled: | Bear with me and allow me my delusions while I daydream... | | What with FPGA technology as reasonable as it is, and the amount of hw/sw | talent on these lists, maybe people should band together and come up with | a NIC? Maybe have native mode + Tulip/PNIC clone compatibility mode. Altera and Xilinx do not sell these things in small quantities. And you probably need a high gate count FPGA anyway. (read: expensive) | Take a look at www.opencores.org for a start. I highly doubt their feasibility. The number one problem being the development tools required are not "given out" for free. Do ou have any idea how much work it is to write a complete VHDL/Verilog library? :) Even if you do finish writing one, who is going to test it? You will also note that OpenCore does not have a list of their developers. (I wonder if they have more than 5 master-level VLSI design engineers.) The reason against your idea is the same reason that people do not run Linux on Sun Enterprise 10000's. At that cost level, we want it to just *work*. Then again, who wants to GPL their chips? | What production volumes are required before ASICs are feasible? What The smallest feasible industrial volumes that I have seen are greater than 10000 chips. | about having a FreeBSD CDROM + NIC bundle featuring whatever card gets | designed? | | If ya can't join 'em, beat 'em. I think surrendering ourselves to Big Industries in this case is a smart move. | Okay. Back to work and reality. :-) -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 16:26: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (ashto-0006.sjc.ca.bbnow.net [24.219.121.199]) by hub.freebsd.org (Postfix) with ESMTP id 4432E37B718 for ; Fri, 9 Mar 2001 16:25:54 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2A0QUs11068; Fri, 9 Mar 2001 16:26:31 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103100026.f2A0QUs11068@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: Joe Albowicz , freebsd-hackers@FreeBSD.ORG Subject: Re: aic7xxx driver & SCBs In-reply-to: Your message of "Fri, 09 Mar 2001 21:47:45 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Fri, 09 Mar 2001 16:26:30 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > = > On Fri, 9 Mar 2001, Mike Smith wrote: > = > > Joe; it looks like you have some funny ideas about something that's n= ot = > > actually very relevant. I assume that you have already gone and boug= ht = > > Monster Cable(tm) SCSI cables, and that you have the special = > > oxygen-free-copper SCSI controller PCBs, because none of this is goin= g to = > > mean anything unless you have. > = > Pardon and sorry, Mike. It is rather your reply that looks funny to me.= It's meant to be funny. Telling someome straight up that they're being = silly isn't very amusing, so I like to improve things when I can. > The number of SCBs in (both) the Linux and FreeBSD aic7xxx driver(s) is= > very relevant in my opinion given that it is just the maximum of SCSI > command contexts the driver can handle (i.e. maximum number of outstand= ing > IOs). I'm not referring to the number being relevant, rather I'm referring to = the percieved need that Joe has to tune said number. > > > I'd like to ask if anyone can share any knowledge about how/if the = number > > > of SCBs affects performace for scsi drives. > > = > > If you don't have enough SCBs, you can't deliver enough commands to y= our = > > drive(s) to keep them busy. > = > Being busy does not imply doing a good job. You can get a device full b= usy > using only 2 simultaneous IOs for this device. Using more can allow the= > device to perform optimizations based on actual head positions and > possibly coalesce data transfers when possible, for example. That's a better way of putting it, for sure. > > > Also I would like to be able to configure the number of SCBs that t= he scsi > > > driver uses. With Linux this parameter for the aic7xxx driver can = be > > > configured via "make menuconfig" step of the kernel build process. = Is > > > there a similiar way to configure this varible for BSD? Or do I ha= ve to > > > start hacking on the driver code? > > = > > You can't do that. Firstly, there isn't a "SCSI driver", secondly th= ere > > are several different sorts of objects that map to what you, coming f= rom > > the Linux world, would call an SCB, and thirdly, the CAM subsystem > > components have a much better idea than you do how many of these that= are > > needed, and will allocate them as necessary. > = > You should have been more accurate here, in my opinion. Vague explanati= ons = > are worse than no explanations at all, in my opinion. I find this amusing, mostly because I'm usually asked to dumb down my = explanations so that people can understand them. 8) Your exposition does= = of course give a much more detailed view of the issues. > Btw, your reply let me think that you want to discourage people to hack= = > our source code or to try to understand how it works. Colour me very > surprised. :-) Actually, quite the opposite. I'd much rather have Joe go look at the = source and tools himself than sit here and try to explain it all to him. = = However, I'd take even money on a request like this being from someone = that is expecting everything else to be just like what he's already used = to, and the first step is just to convince them that that's not really = the case... -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 16:34:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.javanet.com (mail1.javanet.com [205.219.162.10]) by hub.freebsd.org (Postfix) with ESMTP id 1003E37B718 for ; Fri, 9 Mar 2001 16:34:23 -0800 (PST) (envelope-from kaworu@sektor7.ath.cx) Received: from wintermute.sekt7.org (dial-2.blk.ma.ultra.net [146.115.112.5]) by mail1.javanet.com (8.9.3/8.9.2) with ESMTP id TAA09415 for ; Fri, 9 Mar 2001 19:34:18 -0500 (EST) Date: Fri, 9 Mar 2001 19:37:45 -0500 (EST) From: kaworu X-Sender: kaworu@wintermute.sekt7 To: freebsd-hackers@freebsd.org Subject: Questions about kernel space functions 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey, Perhaps this is not the right place to post this, if so, I apoligize. But, I have a dilema. Is there any documentation I can find which gives the arguments for all kernel space functions? I'm trying to find a function similar to open(). I'm a newbie at kernel programming. :-) Thanks a lot, Evan Sarmiento (kaworu@sektor7.ath.cx) http://sekt7.org/es -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (SunOS) Comment: Made with pgp4pine 1.75-6 iEYEARECAAYFAjqpd14ACgkQa7CFsJ0L22xAcwCfd6bD9QWSMGll9YwXpa6OAA/x xAMAn1UQJusi3JXGkLtuA4FlcYKxfe1G =EkUk -----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 Fri Mar 9 17: 0:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cx420564-b.tucson1.az.home.com (cx420564-b.tucson1.az.home.com [24.21.112.225]) by hub.freebsd.org (Postfix) with ESMTP id 157B337B718 for ; Fri, 9 Mar 2001 17:00:29 -0800 (PST) (envelope-from fracture@cx420564-b.tucson1.az.home.com) Received: (from fracture@localhost) by cx420564-b.tucson1.az.home.com (8.11.1/8.11.1) id f29HqYp07117 for freebsd-hackers@freebsd.org; Fri, 9 Mar 2001 17:52:34 GMT (envelope-from fracture) Date: Fri, 9 Mar 2001 17:52:33 +0000 From: Jordan DeLong To: freebsd-hackers@freebsd.org Subject: Kernel area libmish stuff Message-ID: <20010309175233.A6880@cx420564-b.tucson1.az.home.com> Mail-Followup-To: Jordan DeLong , freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well here's the story: a few days ago my video card broke, so I'm without X and such, and using a spare 486 box on the freebsd console. Out of lack of other things to do, I did most of the porting of one of the screensavers in the xscreensaver collection to the freebsd syscons. The problem I'm having now is I dunno the _right_ way to get the trig functions from the userland libm in kernel space. _is_ there a right way? or can it be statically linked into the screensaver module? (ouch) I was thinking of just getting a sintable array and making a few simple functions, so the whole of libm doesn't need to be statically linked into the module (from my understanding, once loaded, this module wont ever get paged out, and thus it'd be _bad_ for it to be big). Any thoughts? I get my new card in two days, hehe; so this project is over in two days regardless of if I finish it/find a good way to do this. Thanks, -Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 17:13:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 7669737B71A for ; Fri, 9 Mar 2001 17:13:37 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.9.3) with SMTP id f2A1Bai49252; Fri, 9 Mar 2001 20:11:40 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <001f01c0a8ff$d64273e0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Jordan DeLong" , References: <20010309175233.A6880@cx420564-b.tucson1.az.home.com> Subject: Re: Kernel area libmish stuff Date: Fri, 9 Mar 2001 20:17:08 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well here's the story: a few days ago my video card broke, so I'm without > X and such, and using a spare 486 box on the freebsd console. Out of lack of > other things to do, I did most of the porting of one of the screensavers in the > xscreensaver collection to the freebsd syscons. > > The problem I'm having now is I dunno the _right_ way to get the trig functions > from the userland libm in kernel space. _is_ there a right way? or can it be > statically linked into the screensaver module? (ouch) There's probably a way to include *some* of the libm functions (from /usr/src/lib/msun, since /usr/src/lib/libm is deprecated). However, this would require a considerable amount of Makefile magic, and also require that the msun code be present in order to do a complete build of the kernel with modules. I doubt that this requirement would make you many friends in -questions :) > I was thinking of just getting a sintable array and making a few simple > functions, so the whole of libm doesn't need to be statically linked into the > module (from my understanding, once loaded, this module wont ever get paged out, > and thus it'd be _bad_ for it to be big). This is probably the best way to go, IMO. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 17:30:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 60EEA37B718 for ; Fri, 9 Mar 2001 17:30:38 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2A1UQj39856; Fri, 9 Mar 2001 17:30:26 -0800 (PST) (envelope-from dillon) Date: Fri, 9 Mar 2001 17:30:26 -0800 (PST) From: Matt Dillon Message-Id: <200103100130.f2A1UQj39856@earth.backplane.com> To: "Matthew Emmerton" Cc: "Jordan DeLong" , Subject: Re: Kernel area libmish stuff References: <20010309175233.A6880@cx420564-b.tucson1.az.home.com> <001f01c0a8ff$d64273e0$1200a8c0@gsicomp.on.ca> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can't safely do FP instructions in the kernel. I do not believe the FP context is saved/restored between processes in kernel mode, only from user mode. The kernel saves and restores the fp state in the few places it uses FP instructions (for memory copying). In anycase, I think there'd be a problem here. -Matt :There's probably a way to include *some* of the libm functions (from :/usr/src/lib/msun, since /usr/src/lib/libm is deprecated). However, this :would require a considerable amount of Makefile magic, and also require that :the msun code be present in order to do a complete build of the kernel with :modules. : :I doubt that this requirement would make you many friends in -questions :) : :> I was thinking of just getting a sintable array and making a few simple :> functions, so the whole of libm doesn't need to be statically linked into :the :> module (from my understanding, once loaded, this module wont ever get :paged out, :> and thus it'd be _bad_ for it to be big). : :This is probably the best way to go, IMO. : :-- :Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 17:36: 3 2001 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 AD5A837B719 for ; Fri, 9 Mar 2001 17:35:57 -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 CAA56168; Sat, 10 Mar 2001 02:33:52 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103100133.CAA56168@info.iet.unipi.it> Subject: Re: howto access an oddly shaped partition on a floppy ? In-Reply-To: <200103092309.f29N9na27176@whizzo.transsys.com> from "Louis A. Mamakos" at "Mar 9, 2001 06:09:49 pm" To: "Louis A. Mamakos" Date: Sat, 10 Mar 2001 02:33:51 +0100 (CET) Cc: Josef Karthauser , Poul-Henning Kamp , 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 > So how about a options flag on the floppy driver which translates > block addresses beyond 1440K into the "extra" sectors? I don't > know that there's a "clean" way insert that into the driver, just > glancing at the code.. that is another possibility, yes. But it still remains the challenge of controlling how the filesystem code allocates blocks to make sure that the first things you write really end up into the "initial" part of the disk so the bios can boot from it. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 17:37:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 812C237B718 for ; Fri, 9 Mar 2001 17:37:09 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.2/8.11.0) with ESMTP id f2A1aia28014; Fri, 9 Mar 2001 20:36:44 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200103100136.f2A1aia28014@whizzo.transsys.com> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Luigi Rizzo Cc: Josef Karthauser , Poul-Henning Kamp , hackers@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: howto access an oddly shaped partition on a floppy ? References: <200103100133.CAA56168@info.iet.unipi.it> In-reply-to: Your message of "Sat, 10 Mar 2001 02:33:51 +0100." <200103100133.CAA56168@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Mar 2001 20:36:44 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > So how about a options flag on the floppy driver which translates > > block addresses beyond 1440K into the "extra" sectors? I don't > > know that there's a "clean" way insert that into the driver, just > > glancing at the code.. > > that is another possibility, yes. But it still remains the challenge > of controlling how the filesystem code allocates blocks to > make sure that the first things you write really end up into > the "initial" part of the disk so the bios can boot from it. Depending on the shape of the files you need to have on the disk, you could split this between two FreeBSD partitions (/dev/fd0a and /dev/fd0d or something), with the second partition being the bizzaro extra sectors. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 17:41:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 8847337B719; Fri, 9 Mar 2001 17:41:42 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id UAA83147; Fri, 9 Mar 2001 20:53:40 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010309204335.01fc2b00@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Fri, 09 Mar 2001 20:56:57 -0500 To: wpaul@FreeBSD.ORG (Bill Paul), msmith@FreeBSD.ORG (Mike Smith) From: Dennis Subject: Re: if_fxp - the real point Cc: hackers@FreeBSD.ORG In-Reply-To: <20010309221250.2384337B71B@hub.freebsd.org> References: <200103091823.f29INLs06070@mass.dis.org> 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 At 05:12 PM 03/09/2001, Bill Paul wrote: >Grrrrr. > >(Yes, that's a bad omen. Get the women and children to safety now.) > >(On second thought, leave the women.) > >I think there's one important point that a lot of you are missing here, >which is GETTING DOCUMENTATION. I've seen a couple people suggest that >they'd be willing to donate time/code/etc to fix the fxp driver, but I >strongly suspect that most of these people don't have the slighest idea >what's really involved. You can't just look at the driver code, poke at >it for a while, and expect the answer to fall out: you need the damn >manual for it. And you can't get that from Intel because they're NDA >nazis. (Johnathan Lemon is the one exception to this since he apparently >has ways to gain access to Intel documentation thanks to his job. I think >he's still subject to NDAs though, so I question just how much help he >can really provide. Not that I don't encourge him to do an end run around >Intel wherever he can, of course.) I think its been mentioned several times in this and other threads that intel has a driver for LINUX that is effective documentation on the board, and the code is public (although you may have to stick an intel copyright in the code also). Anyone who has signed an NDA will have trouble doing anything other than telling someone else how to do it (as long as he does it privately). Sometimes NDAs arent really what they are. There is certainly no damage to intel since they've released their own driver for linux for the board...it would be pretty difficult for them to go after someone for disclosing something that they've already disclosed themselves. I've decided to get what i need working myself, although its not clear that 1) what I do will be a generic fix and 2) whether I'll be able to release the code. or 3) whether it will be clean enough for anyone to want for awhile: But I should know soon how much work its going to be. Sometimes when you go to kick someone in the butt you kick yourself :-) >I see lots of finger-pointing here, yet nobody seems to be prepared to >fault the real culprit, namely Intel. Nobody sends nasty e-mails to >their Intel sales reps or other high mucky-mucks taking them to task over >their nonsensical NDA requirements. Nobody makes any effort to explain to >them just how much more sense it would make and how much more money they >would earn by simply preparing some decent manuals for a change and not >being so anal-retentive about releasing them. If everyone would concentate >their energy on this for a change instead of sniping at each other, I would >be a happy man. You guys continue not to understand why companies dont disclose board info freely. You end up competing with your own customers. They dont want people buying gray market parts and selling $9. boards. Its very easy to clone a board with 2 chips on it these days. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 17:52:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9BA3537B71C for ; Fri, 9 Mar 2001 17:52:37 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2A1qYV15760; Fri, 9 Mar 2001 17:52:34 -0800 (PST) Date: Fri, 9 Mar 2001 17:52:34 -0800 From: Alfred Perlstein To: kaworu Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Questions about kernel space functions Message-ID: <20010309175233.Z18351@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from kaworu@sektor7.ath.cx on Fri, Mar 09, 2001 at 07:37:45PM -0500 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * kaworu [010309 16:34] wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hey, > > Perhaps this is not the right place to post this, if so, I apoligize. But, > I have a dilema. Is there any documentation I can find which gives the > arguments for all kernel space functions? I'm trying to find a function > similar to open(). I'm a newbie at kernel programming. :-) See section 9 of the manpages. -- -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 Fri Mar 9 18:11:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id 8D76737B719 for ; Fri, 9 Mar 2001 18:11:08 -0800 (PST) (envelope-from rh@matriplex.com) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id SAA69861 for ; Fri, 9 Mar 2001 18:11:02 -0800 (PST) (envelope-from rh@matriplex.com) Date: Fri, 9 Mar 2001 18:11:01 -0800 (PST) From: Richard Hodges To: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel area libmish stuff In-Reply-To: <200103100130.f2A1UQj39856@earth.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 Fri, 9 Mar 2001, Matt Dillon wrote: > You can't safely do FP instructions in the kernel. I do not > believe the FP context is saved/restored between processes in kernel > mode, only from user mode. The kernel saves and restores the fp state > in the few places it uses FP instructions (for memory copying). > In anycase, I think there'd be a problem here. The last time I tried using FP in a device driver, it caused kernel panics (I hate it when that happens...) -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. Product Manager | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 18:24:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f145.law11.hotmail.com [64.4.17.145]) by hub.freebsd.org (Postfix) with ESMTP id EB4FC37B718; Fri, 9 Mar 2001 18:24:55 -0800 (PST) (envelope-from peterpajak@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 9 Mar 2001 18:24:55 -0800 Received: from 65.92.90.105 by lw11fd.law11.hotmail.msn.com with HTTP; Sat, 10 Mar 2001 02:24:54 GMT X-Originating-IP: [65.92.90.105] From: "peter pajak" To: freebsd-questions@freebsd.org Cc: hackers@FreeBSD.ORG Subject: gimp not opening neither *.jpg nor *.gif files Date: Sat, 10 Mar 2001 02:24:54 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 10 Mar 2001 02:24:55.0184 (UTC) FILETIME=[4B708900:01C0A909] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi there, just wandering if anyone can help. installed gimp1 from the ports, all required components like mpeg, tif, jpeg etc..., still gimp does not open/save the file in either jpeg or gif format. help!!!!!!!!!!!!! p. _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail 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 Fri Mar 9 18:32:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 6AF3F37B718 for ; Fri, 9 Mar 2001 18:32:31 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.9.3) with SMTP id f2A2Uji49388 for ; Fri, 9 Mar 2001 21:30:45 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <000b01c0a90a$e3287360$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: References: Subject: Re: Kernel area libmish stuff Date: Fri, 9 Mar 2001 21:36:18 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 9 Mar 2001, Matt Dillon wrote: > > > You can't safely do FP instructions in the kernel. I do not > > believe the FP context is saved/restored between processes in kernel > > mode, only from user mode. The kernel saves and restores the fp state > > in the few places it uses FP instructions (for memory copying). > > In anycase, I think there'd be a problem here. > > The last time I tried using FP in a device driver, it caused kernel > panics (I hate it when that happens...) Seeing as the original requestor wanted to use FP functions to do number crunching in screen savers, would adding a few strategic FP save/restore calls in the syscons driver be enough to allow FP calculations in screen saver modules? -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 19:34:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 82BF237B71C for ; Fri, 9 Mar 2001 19:34:40 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.9.3) with SMTP id f2A3Wsi49550; Fri, 9 Mar 2001 22:32:54 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <003d01c0a913$923455b0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Matthew Emmerton" , References: <000b01c0a90a$e3287360$1200a8c0@gsicomp.on.ca> Subject: Re: Kernel area libmish stuff Date: Fri, 9 Mar 2001 22:38:28 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Fri, 9 Mar 2001, Matt Dillon wrote: > > > > > You can't safely do FP instructions in the kernel. I do not > > > believe the FP context is saved/restored between processes in kernel > > > mode, only from user mode. The kernel saves and restores the fp > state > > > in the few places it uses FP instructions (for memory copying). > > > In anycase, I think there'd be a problem here. > > > > The last time I tried using FP in a device driver, it caused kernel > > panics (I hate it when that happens...) > > Seeing as the original requestor wanted to use FP functions to do number > crunching in screen savers, would adding a few strategic FP save/restore > calls in the syscons driver be enough to allow FP calculations in screen > saver modules? Please forget I ever said this. I took a look at what would be involved, and it's wayyyy too deep for me to even begin about thinking about it. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 20:32:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 663F937B719 for ; Fri, 9 Mar 2001 20:32:42 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 9C0946A90D; Sat, 10 Mar 2001 15:02:40 +1030 (CST) Date: Sat, 10 Mar 2001 15:02:40 +1030 From: Greg Lehey To: kaworu Cc: freebsd-hackers@freebsd.org Subject: Kernel open(2) (was: Questions about kernel space functions) Message-ID: <20010310150240.I15116@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from kaworu@sektor7.ath.cx on Fri, Mar 09, 2001 at 07:37:45PM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 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 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 9 March 2001 at 19:37:45 -0500, kaworu wrote: > > Perhaps this is not the right place to post this, if so, I apoligize. This is the correct place. -questions is not. > But, I have a dilema. Is there any documentation I can find which > gives the arguments for all kernel space functions? I'm trying to > find a function similar to open(). I'm a newbie at kernel > programming. :-) Others have pointed you to section 9 of the manual. If you've looked there, you'll probably be even more confused than before. The real answer you're looking for is that there is no function similar to open() (or the other I/O functions, for that matter). The closest you'd get would be VOP_OPEN(9), but the parameters are very different from userland open(2). You'd be better off reading the Design and Implementation, or just plain doing it in userland. 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 Mar 9 21:32:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id D8B5637B71B for ; Fri, 9 Mar 2001 21:32:37 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2A22Nq00619; Fri, 9 Mar 2001 18:02:25 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103100202.f2A22Nq00619@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point In-reply-to: Your message of "Fri, 09 Mar 2001 20:56:57 EST." <5.0.0.25.0.20010309204335.01fc2b00@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Mar 2001 18:02:22 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I think its been mentioned several times in this and other threads that > intel has a driver for LINUX that is effective documentation on the board, > and the code is public (although you may have to stick an intel copyright > in the code also). It hasn't been mentioned in this thread that the Intel driver is adequate documentation, because it isn't. (I've read it.) > Sometimes NDAs arent really what they are. There is certainly no damage to > intel since they've released their own driver for linux for the board...it > would be pretty difficult for them to go after someone for disclosing > something that they've already disclosed themselves. Part of the problem is that Intel *haven't* disclosed a lot of the information that's necessary in order to write a driver other than the one they've written. Much of the information that a driver author requires is not clearly disclosed in source for another OS' driver, and again, this is the case with the Intel driver. Just in case it's not clear, I have on a number of occasions been forced to reverse-engineer drivers from source, so I can claim to speak on this topic with some authority. 8) > You guys continue not to understand why companies dont disclose board info > freely. You end up competing with your own customers. They dont want people > buying gray market parts and selling $9. boards. Its very easy to clone a > board with 2 chips on it these days. This actually has almost nothing to do with it; placing the programming documentation under NDA does almost nothing to preclude a competitor from either cloning the part or for that matter obtaining the documentation themselves. NDA's in this particular space serve a limited set of purposes: - They constitute engineering damage control; witness Realtek's unhappiness at Bill's honest commentary on their documented parts. - They provide a theoretical underwriting for the "intellectual property" that a company's accounting department likes to think it has. - They allow a company to control (to some degree) the uses to which its products are put. This is typically a marketting angle (by forcing a customer to negotiate, you can force a variety of concessions, co-deals, etc.). And in our case, they also serve to stifle otherwise legitimate support for a product, simply because we don't fit into a category they understand. Irritating, but difficult to deal with. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 22:11:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id E7AF437B718; Fri, 9 Mar 2001 22:11:24 -0800 (PST) Subject: Re: if_fxp - the real point In-Reply-To: <5.0.0.25.0.20010309204335.01fc2b00@mail.etinc.com> from Dennis at "Mar 9, 2001 08:56:57 pm" To: dennis@etinc.com (Dennis) Date: Fri, 9 Mar 2001 22:11:24 -0800 (PST) Cc: hackers@FreeBSD.ORG, msmith@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 Message-Id: <20010310061124.E7AF437B718@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I think its been mentioned several times in this and other threads that > intel has a driver for LINUX that is effective documentation on the board, > and the code is public (although you may have to stick an intel copyright > in the code also). Whoever mentioned this was not thinking clearly. A manual is effective documentation for a NIC. Sample driver code alone is not. It's handy, but it's not enough. When you write a driver, you make certain design decisions based on the information in the manual and the OS you're developing for. By forcing someone to rely soley on your driver to see how the board works, you're limiting their ability to make their own design decisions. What works well for Windows or Linux may be mediocre for BSD. Besides, Intel engineers have a knack for choosing really confusing register names. And again, saying "but there's a Linux driver" just gives vendors an excuse to perpetuate their stupidity. I'm not keen to give them this opportunity. > You guys continue not to understand why companies dont disclose board info > freely. You end up competing with your own customers. They dont want people > buying gray market parts and selling $9. boards. Its very easy to clone a > board with 2 chips on it these days. I'm sorry, that doesn't wash. *I* am not trying to compete with anyone. Lord knows I can't afford to fabricate my own controller chips on my salary. The users who just want to use the cards certainly don't want to compete with anybody. If anything, I want to help them make money. If your method for squashing competition also angers your allaged 'partners' and costs you money, then you need to come up with a better mechanism. Besides, there's supposed to be competition: it's a free market, remember? If I sell a car with a gas pedal, steering wheel and gear shift, I can't tell all the other car manufacturers not to make their cars with gas pedals, steering wheels and gear shifts, or swear all the people who drive my cars to secrecy so they can't tell anyone how they're meant to be driven. Just because other companies make cars with the same features, that doesn't make them better cars than mine: the consumer should do some research to find the best one instead of buying whatever's cheapest. Naturally, consumers are never that bright. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 9 22:33:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 348A737B71B for ; Fri, 9 Mar 2001 22:33:41 -0800 (PST) (envelope-from zhaoc@cloud9.net) Received: from earl-grey.cloud9.net (earl-grey.cloud9.net [168.100.1.1]) by russian-caravan.cloud9.net (Postfix) with ESMTP id 53A9F28CC2 for ; Sat, 10 Mar 2001 01:33:32 -0500 (EST) Received: by earl-grey.cloud9.net (Postfix, from userid 11022) id 7681D1F1B; Sat, 10 Mar 2001 01:33:31 -0500 (EST) Date: Sat, 10 Mar 2001 01:33:31 -0500 From: Chen Zhao To: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point Message-ID: <20010310013331.A57865@earl-grey.cloud9.net> References: <5.0.0.25.0.20010309204335.01fc2b00@mail.etinc.com> <200103100202.f2A22Nq00619@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200103100202.f2A22Nq00619@mass.dis.org>; from msmith@freebsd.org on Fri, Mar 09, 2001 at 06:02:22PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG \- Mike Smith stated on /- [Fri, Mar 09, 2001 at 06:02:22PM -0800]: > > NDA's in this particular space serve a limited set of purposes: > > - They constitute engineering damage control; witness Realtek's > unhappiness at Bill's honest commentary on their documented parts. \_____End_of_Statement_____/ I have a quick question (this was asked before, but I haven't seen a real answer to it..) for Mr. Paul and other driver authors. Given the NDA situation with Intel, et al., and the possibility that support for the fxp driver may wane a bit, the necessity for future planning prompts me to ask: What is the next most (unofficially of course :) recommended NIC in terms of driver stability, card reliability and performance, and driver efficiency (low overhead, etc.), ignoring for the moment actual NIC price, and just judging from a technical perspective? For instance, the fxp driver has been touted (I've seen this somewhere) as being extremely efficient (the hardware itself also being very high performance), and stable (b/c Mr. Greenman was able to obtain some documents w/o the NDA). The linux analogue of the xl is their driver and NIC of choice. Would the xl be next on the list, or would it be one of the previously mentioned D-Link/Netgear cards for which documentation is freely available? I've always thought that the latter brands were lower performance cards... Thanks for the insights, and (I don't think this ever gets said enough), thanks for a superb OS. Oh, is there also a recommended gigabit adapter? Tigon? Intel? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 3:15:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-158.dsl.lsan03.pacbell.net [63.207.60.158]) by hub.freebsd.org (Postfix) with ESMTP id 526CE37B71F; Sat, 10 Mar 2001 03:15:18 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 59D8466BC9; Sat, 10 Mar 2001 03:15:16 -0800 (PST) Date: Sat, 10 Mar 2001 03:15:15 -0800 From: Kris Kennaway To: hackers@FreeBSD.org Cc: fs@FreeBSD.org Subject: httpfs Message-ID: <20010310031515.A8998@mollari.cthul.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="IJpNTDwzlM2Ie8A6" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline A few of us were talking on IRC tonight about how cool it would be to have an httpfs filesystem -- then it occurred to me we almost have this already, in the form of the (under-utilised) portalfs. Portalfs works by handing off everything to a userland daemon which handles the actual transaction request, so you could easily imagine extending it to provide an http method similar to the tcp method it currently has for initiating tcp connections. One could probably make this more generic and finish implementing the undocumented 'exec' method (which currently exists as a stub): this would run an administrator-specified command (i.e. fixed in /etc/portal.conf) and pipe the output back to the user. A fully navigable httpfs (e.g. one you can ls and cd around in) is more work and probably requires a full stacking layer, but this would still be pretty cool. Is anyone feeling inspired to implement this? :-) Kris --IJpNTDwzlM2Ie8A6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6qgzDWry0BWjoQKURAk8QAKDG8KRZDePyH1IVlS2e1U4B3B63fQCgyTc9 7sLZBMrBbsH/NG4YeHbpApk= =G5nl -----END PGP SIGNATURE----- --IJpNTDwzlM2Ie8A6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 3:33:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [209.247.77.155]) by hub.freebsd.org (Postfix) with ESMTP id 396E637B718; Sat, 10 Mar 2001 03:33:39 -0800 (PST) (envelope-from gordont@bluemtn.net) Received: from localhost (gordont@localhost) by sdmail0.sd.bmarts.com (8.11.3/8.11.2/BMA1.1) with ESMTP id f2ABXB386871; Sat, 10 Mar 2001 03:33:11 -0800 (PST) Date: Sat, 10 Mar 2001 03:33:11 -0800 (PST) From: Gordon Tetlow X-X-Sender: To: Kris Kennaway Cc: , Subject: Re: httpfs In-Reply-To: <20010310031515.A8998@mollari.cthul.hu> 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 have a link handy, but if you search for it, I'm sure it's out there. Linux had something like this called PerlFS which was much more generic. The general gist of it was you could use it to make fs's of things like http and ftp. It was extendable (I think) so you could make your own fs handlers out of perl scripts. I could be making alot of this up as this was a long time ago, and I'm too lazy/tired to pull up a web browser and look. In any event, it might be a good spot to look for ideas. If no one else has, I'll see what I can dig up in the morning. Night. -gordon On Sat, 10 Mar 2001, Kris Kennaway wrote: > A few of us were talking on IRC tonight about how cool it would be to > have an httpfs filesystem -- then it occurred to me we almost have > this already, in the form of the (under-utilised) portalfs. Portalfs > works by handing off everything to a userland daemon which handles the > actual transaction request, so you could easily imagine extending it > to provide an http method similar to the tcp method it currently has > for initiating tcp connections. > > One could probably make this more generic and finish implementing the > undocumented 'exec' method (which currently exists as a stub): this > would run an administrator-specified command (i.e. fixed in > /etc/portal.conf) and pipe the output back to the user. > > A fully navigable httpfs (e.g. one you can ls and cd around in) is > more work and probably requires a full stacking layer, but this would > still be pretty cool. > > Is anyone feeling inspired to implement this? :-) > > Kris > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 4:49:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 4D13637B71A for ; Sat, 10 Mar 2001 04:49:13 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from mobile.wemm.org (mobile.wemm.org [10.0.0.5]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f2ACnDp21976 for ; Sat, 10 Mar 2001 04:49:13 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f2ACnCh16057; Sat, 10 Mar 2001 04:49:12 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200103101249.f2ACnCh16057@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Chen Zhao Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point In-Reply-To: <20010310013331.A57865@earl-grey.cloud9.net> Date: Sat, 10 Mar 2001 04:49:12 -0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chen Zhao wrote: > \- Mike Smith stated on > /- [Fri, Mar 09, 2001 at 06:02:22PM -0800]: > > > > NDA's in this particular space serve a limited set of purposes: > > > > - They constitute engineering damage control; witness Realtek's > > unhappiness at Bill's honest commentary on their documented parts. > > Oh, is there also a recommended gigabit adapter? Tigon? Intel? STAY AWAY FROM THE INTEL GIG CARDS!! (Sorry for the shouting, but it is an important point). I have the NDA'ed docs for the Intel gig and fxp cards. After Intel's spectacular efforts to bury Johnathan Lemon's driver for their gig card (that outperformed the Intel Linux driver by something like a factor of 5), I have lost all respect for Intel's networking division. As long as Intel are being this stupid, Intel hardware is never going to be well supported. The fxp driver is starting to slip behind because Intel wont give DG updated fxp docs without him signing an NDA that prevents him from releasing the updated driver. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 7:49: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from diamond.gpad.ac.ru (diamond.gpad.ac.ru [193.233.9.65]) by hub.freebsd.org (Postfix) with ESMTP id F38C537B719 for ; Sat, 10 Mar 2001 07:48:40 -0800 (PST) (envelope-from dima@cavia.landau.ac.ru) Received: from cavia.landau.ac.ru (cavia.landau.ac.ru [193.233.9.17]) by diamond.gpad.ac.ru (8.11.1/8.11.1) with ESMTP id f2AFmUD31351 for ; Sat, 10 Mar 2001 18:48:31 +0300 (MSK) (envelope-from dima@cavia.landau.ac.ru) Received: (from dima@localhost) by cavia.landau.ac.ru (8.11.2/8.11.2) id f2AFh2i99066 for hackers@freebsd.org; Sat, 10 Mar 2001 18:43:02 +0300 (MSK) (envelope-from dima) Date: Sat, 10 Mar 2001 18:43:00 +0300 From: Dmitry Sivachenko To: hackers@freebsd.org Subject: Problem with K6-2/500 CPU Message-ID: <20010310184300.A83942@netserv1.chg.ru> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="y0ulUmNC+osPPQO6" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --y0ulUmNC+osPPQO6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello! I use recent FreeBSD-4-STABLE. When I changed my processor from Intel Pentium 200 MMX to AMD K6-2 500, I can neither recompile operating system nor compile other programs. From kernel compilation: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../ufs/ffs/ffs_softdep.c cc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 Stop in /usr/src/sys/compile/CAVIA. From compilation of base system: cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/makeinfo/node.c cc: Internal compiler error: program cc1 got fatal signal 4 *** Error code 1 Stop in /usr/src/gnu/usr.bin/texinfo/makeinfo. *** Error code 1 Stop in /usr/src/gnu/usr.bin/texinfo. *** Error code 1 What should I do in order to use FreeBSD on K6-2/500 processor? Please find my kernel config file attached. I'll be glad to provide futher information if necessary. Thank you in advance, Dima. --y0ulUmNC+osPPQO6 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=CAVIA # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.8 2000/07/20 02:51:02 msmith Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU cpu I586_CPU cpu I686_CPU ident CAVIA maxusers 32 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options CPU_WT_ALLOC options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking #options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device #options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs device isa device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers #device ahb # EISA AHA1742 family #device ahc # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Teckram DC-390(T)) #device dpt # DPT Smartcache - See LINT for options! #device isp # Qlogic family #device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets) options SYM_SETUP_LP_PROBE_MAP=0x40 # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured #device adv0 at isa? #device adw #device bt0 at isa? #device aha0 at isa? #device aic0 at isa? # SCSI peripherals device scbus # SCSI bus (required) #device da # Direct Access (disks) #device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers #device ida # Compaq Smart RAID #device amr # AMI MegaRAID #device mlx # Mylex DAC960 family #device twe # 3ware Escalade # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server on a vt console #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 nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support #device card #device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd0000 #device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. #device de # DEC/Intel DC21x4x (``Tulip'') #device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device tx # SMC 9432TX (83c170 ``EPIC'') #device vx # 3Com 3c590, 3c595 (``Vortex'') #device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. #device miibus # MII bus support #device dc # DEC/Intel 21143 and various workalikes #device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device ste # Sundance ST201 (D-Link DFE-550TX) #device tl # Texas Instruments ThunderLAN #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F #device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 #device ex #device ep # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attatement needed # and resources will always be dynamically assigned by the pccard code. device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those paremeters here. #device an # Xircom Ethernet #device xe # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device fe0 at isa? port 0x300 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 # 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 4 # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" #pseudo-device gif 4 # IPv6 and IPv4 tunneling #pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface #device ohci # OHCI PCI->USB interface device usb # USB Bus (required) #device ugen # Generic #device uhid # "Human Interface Devices" #device ukbd # Keyboard #device ulpt # Printer #device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse # USB Ethernet, requires mii #device aue # ADMtek USB ethernet #device cue # CATC USB ethernet #device kue # Kawasaki LSI USB ethernet pseudo-device vn 2 #options IPFIREWALL #options IPFIREWALL_VERBOSE #options IPDIVERT #device pcm0 at isa? port? irq 9 drq 1 flags 0x00 options SC_HISTORY_SIZE=1000 options _KPOSIX_VERSION=199309L options QUOTA device snd0 device mss0 at isa? port 0x530 irq 9 drq 1 options MD_NSECT=40000 --y0ulUmNC+osPPQO6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 7:57:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 3636837B719 for ; Sat, 10 Mar 2001 07:57:54 -0800 (PST) (envelope-from zhaoc@cloud9.net) Received: from earl-grey.cloud9.net (earl-grey.cloud9.net [168.100.1.1]) by russian-caravan.cloud9.net (Postfix) with ESMTP id 7430A28E28 for ; Sat, 10 Mar 2001 10:56:57 -0500 (EST) Received: by earl-grey.cloud9.net (Postfix, from userid 11022) id 0CA881F1B; Sat, 10 Mar 2001 10:56:57 -0500 (EST) Date: Sat, 10 Mar 2001 10:56:56 -0500 From: Chen Zhao To: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point Message-ID: <20010310105656.A70989@earl-grey.cloud9.net> References: <20010310013331.A57865@earl-grey.cloud9.net> <200103101249.f2ACnCh16057@mobile.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200103101249.f2ACnCh16057@mobile.wemm.org>; from peter@netplex.com.au on Sat, Mar 10, 2001 at 04:49:12AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG \- Peter Wemm stated on /- [Sat, Mar 10, 2001 at 04:49:12AM -0800]: > I have the NDA'ed docs for the Intel gig and fxp cards. After Intel's > spectacular efforts to bury Johnathan Lemon's driver for their gig card > (that outperformed the Intel Linux driver by something like a factor of 5), > I have lost all respect for Intel's networking division. Sorry to hear that. The last thing I can find on the Intel gig stuff was dated at the end of 1999, where Johnathan Lemon wasn't sure if he could release his version, and Matt Jacob had a version hacked from the released Linux drivers. I take it Intel didn't give the hoped for permission. > As long as Intel are being this stupid, Intel hardware is never going to be > well supported. The fxp driver is starting to slip behind because Intel > wont give DG updated fxp docs without him signing an NDA that prevents him > from releasing the updated driver. That part I get, hence the question of what's the next best card/driver. I was also (coincidentally) thinking of the Intel ads which feature Yahoo! ads using servers with their processors. I was wondering if perhaps someone technical at Yahoo might have some clout with Intel. Yes, I realize that's pretty naive. :) \_____End_of_Statement_____/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 8:12:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 646E337B72D for ; Sat, 10 Mar 2001 08:12:18 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 14blyZ-0005mu-00; Sat, 10 Mar 2001 16:12:15 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.2/8.11.2) id f2AGE9U16915; Sat, 10 Mar 2001 17:14:09 +0100 (CET) (envelope-from wkb) Date: Sat, 10 Mar 2001 17:14:08 +0100 From: Wilko Bulte To: Dmitry Sivachenko Cc: hackers@freebsd.org Subject: Re: Problem with K6-2/500 CPU Message-ID: <20010310171408.A16883@freebie.demon.nl> References: <20010310184300.A83942@netserv1.chg.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010310184300.A83942@netserv1.chg.ru>; from dima@chg.ru on Sat, Mar 10, 2001 at 06:43:00PM +0300 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 10, 2001 at 06:43:00PM +0300, Dmitry Sivachenko wrote: Smells like dodgy hardware, especially memory. You are not overclocking are you? There are no problems with K6-2 & FreeBSD, I ran it on a K6-2 @400 very successfully (now have an Athlon box). Wilko > Hello! > > I use recent FreeBSD-4-STABLE. > When I changed my processor from Intel Pentium 200 MMX to AMD K6-2 500, > I can neither recompile operating system nor compile other programs. > > >From kernel compilation: > > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../ufs/ffs/ffs_softdep.c > cc: Internal compiler error: program cc1 got fatal signal 11 > *** Error code 1 > > Stop in /usr/src/sys/compile/CAVIA. > > > > >From compilation of base system: > > cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/makeinfo/node.c > cc: Internal compiler error: program cc1 got fatal signal 4 > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/texinfo/makeinfo. > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/texinfo. > *** Error code 1 > > > What should I do in order to use FreeBSD on K6-2/500 processor? > > Please find my kernel config file attached. > > I'll be glad to provide futher information if necessary. > > Thank you in advance, > Dima. > # > # GENERIC -- Generic kernel configuration file for FreeBSD/i386 > # > # For more information on this file, please read the handbook section on > # Kernel Configuration Files: > # > # http://www.FreeBSD.org/handbook/kernelconfig-config.html > # > # The handbook is also available locally in /usr/share/doc/handbook > # if you've installed the doc distribution, otherwise always see the > # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the > # latest information. > # > # An exhaustive list of options and more detailed explanations of the > # device lines is also present in the ./LINT configuration file. If you are > # in doubt as to the purpose or necessity of a line, check first in LINT. > # > # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.8 2000/07/20 02:51:02 msmith Exp $ > > machine i386 > #cpu I386_CPU > #cpu I486_CPU > cpu I586_CPU > cpu I686_CPU > ident CAVIA > maxusers 32 > > #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols > > options CPU_WT_ALLOC > > options MATH_EMULATE #Support for x87 emulation > options INET #InterNETworking > #options INET6 #IPv6 communications protocols > options FFS #Berkeley Fast Filesystem > options FFS_ROOT #FFS usable as root device [keep this!] > options SOFTUPDATES #Enable FFS soft updates support > options MFS #Memory Filesystem > options MD_ROOT #MD is a potential root device > #options NFS #Network Filesystem > #options NFS_ROOT #NFS usable as root device, NFS required > options MSDOSFS #MSDOS Filesystem > options CD9660 #ISO 9660 Filesystem > options CD9660_ROOT #CD-ROM usable as root, CD9660 required > options PROCFS #Process filesystem > options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] > options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI > options UCONSOLE #Allow users to grab the console > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > options KTRACE #ktrace(1) support > options SYSVSHM #SYSV-style shared memory > options SYSVMSG #SYSV-style message queues > options SYSVSEM #SYSV-style semaphores > options P1003_1B #Posix P1003_1B real-time extensions > options _KPOSIX_PRIORITY_SCHEDULING > options ICMP_BANDLIM #Rate limit bad replies > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > > # To make an SMP kernel, the next two are needed > #options SMP # Symmetric MultiProcessor Kernel > #options APIC_IO # Symmetric (APIC) I/O > # Optionally these may need tweaked, (defaults shown): > #options NCPU=2 # number of CPUs > #options NBUS=4 # number of busses > #options NAPIC=1 # number of IO APICs > #options NINTR=24 # number of INTs > > device isa > device eisa > device pci > > # Floppy drives > device fdc0 at isa? port IO_FD1 irq 6 drq 2 > device fd0 at fdc0 drive 0 > device fd1 at fdc0 drive 1 > > # ATA and ATAPI devices > device ata0 at isa? port IO_WD1 irq 14 > device ata1 at isa? port IO_WD2 irq 15 > device ata > device atadisk # ATA disk drives > device atapicd # ATAPI CDROM drives > #device atapifd # ATAPI floppy drives > #device atapist # ATAPI tape drives > options ATA_STATIC_ID #Static device numbering > #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices > > # SCSI Controllers > #device ahb # EISA AHA1742 family > #device ahc # AHA2940 and onboard AIC7xxx devices > #device amd # AMD 53C974 (Teckram DC-390(T)) > #device dpt # DPT Smartcache - See LINT for options! > #device isp # Qlogic family > #device ncr # NCR/Symbios Logic > device sym # NCR/Symbios Logic (newer chipsets) > options SYM_SETUP_LP_PROBE_MAP=0x40 > # Allow ncr to attach legacy NCR devices when > # both sym and ncr are configured > > #device adv0 at isa? > #device adw > #device bt0 at isa? > #device aha0 at isa? > #device aic0 at isa? > > # SCSI peripherals > device scbus # SCSI bus (required) > #device da # Direct Access (disks) > #device sa # Sequential Access (tape etc) > device cd # CD > device pass # Passthrough device (direct SCSI access) > > # RAID controllers > #device ida # Compaq Smart RAID > #device amr # AMI MegaRAID > #device mlx # Mylex DAC960 family > #device twe # 3ware Escalade > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? irq 1 flags 0x1 > device psm0 at atkbdc? irq 12 > > device vga0 at isa? > > # splash screen/screen saver > pseudo-device splash > > # syscons is the default console driver, resembling an SCO console > device sc0 at isa? flags 0x100 > > # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver > #device vt0 at isa? > #options XSERVER # support for X server on a vt console > #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 nexus? port IO_NPX irq 13 > > # Power management support (see LINT for more options) > #device apm0 at nexus? disable flags 0x20 # Advanced Power Management > > # PCCARD (PCMCIA) support > #device card > #device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd0000 > #device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 disable > > # Serial (COM) ports > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > device sio1 at isa? port IO_COM2 irq 3 > device sio2 at isa? disable port IO_COM3 irq 5 > device sio3 at isa? disable port IO_COM4 irq 9 > > # Parallel port > device ppc0 at isa? irq 7 > device ppbus # Parallel port bus (required) > device lpt # Printer > device plip # TCP/IP over parallel > device ppi # Parallel port interface device > #device vpo # Requires scbus and da > > > # PCI Ethernet NICs. > #device de # DEC/Intel DC21x4x (``Tulip'') > #device fxp # Intel EtherExpress PRO/100B (82557, 82558) > #device tx # SMC 9432TX (83c170 ``EPIC'') > #device vx # 3Com 3c590, 3c595 (``Vortex'') > #device wx # Intel Gigabit Ethernet Card (``Wiseman'') > > # PCI Ethernet NICs that use the common MII bus controller code. > #device miibus # MII bus support > #device dc # DEC/Intel 21143 and various workalikes > #device rl # RealTek 8129/8139 > #device sf # Adaptec AIC-6915 (``Starfire'') > #device sis # Silicon Integrated Systems SiS 900/SiS 7016 > #device ste # Sundance ST201 (D-Link DFE-550TX) > #device tl # Texas Instruments ThunderLAN > #device vr # VIA Rhine, Rhine II > #device wb # Winbond W89C840F > #device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') > > # ISA Ethernet NICs. > #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 > #device ex > #device ep > # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really > # exists only as a PCMCIA device, so there is no ISA attatement needed > # and resources will always be dynamically assigned by the pccard code. > device wi > # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will > # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP > # mode (the factory default). If you set the switches on your ISA > # card for a manually chosen I/O address and IRQ, you must specify > # those paremeters here. > #device an > # Xircom Ethernet > #device xe > # The probe order of these is presently determined by i386/isa/isa_compat.c. > #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 > #device fe0 at isa? port 0x300 > #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 > #device lnc0 at isa? port 0x280 irq 10 drq 0 > #device cs0 at isa? port 0x300 > #device sn0 at isa? port 0x300 irq 10 > > # 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 4 # Packet tunnel. > pseudo-device pty # Pseudo-ttys (telnet etc) > pseudo-device md # Memory "disks" > #pseudo-device gif 4 # IPv6 and IPv4 tunneling > #pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) > > # The `bpf' pseudo-device enables the Berkeley Packet Filter. > # Be aware of the administrative consequences of enabling this! > pseudo-device bpf #Berkeley packet filter > > # USB support > device uhci # UHCI PCI->USB interface > #device ohci # OHCI PCI->USB interface > device usb # USB Bus (required) > #device ugen # Generic > #device uhid # "Human Interface Devices" > #device ukbd # Keyboard > #device ulpt # Printer > #device umass # Disks/Mass storage - Requires scbus and da > device ums # Mouse > # USB Ethernet, requires mii > #device aue # ADMtek USB ethernet > #device cue # CATC USB ethernet > #device kue # Kawasaki LSI USB ethernet > > pseudo-device vn 2 > #options IPFIREWALL > #options IPFIREWALL_VERBOSE > #options IPDIVERT > > #device pcm0 at isa? port? irq 9 drq 1 flags 0x00 > > options SC_HISTORY_SIZE=1000 > > options _KPOSIX_VERSION=199309L > > options QUOTA > > device snd0 > device mss0 at isa? port 0x530 irq 9 drq 1 > > options MD_NSECT=40000 ---end of quoted text--- -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 8:13:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from milquetoast.cs.mcgill.ca (milquetoast.CS.McGill.CA [132.206.2.5]) by hub.freebsd.org (Postfix) with ESMTP id B17E637B718; Sat, 10 Mar 2001 08:13:50 -0800 (PST) (envelope-from mat@milquetoast.cs.mcgill.ca) Received: (from mat@localhost) by milquetoast.cs.mcgill.ca (8.9.3/8.9.3) id LAA14413; Sat, 10 Mar 2001 11:12:13 -0500 (EST) Date: Sat, 10 Mar 2001 11:12:13 -0500 From: Mathew KANNER To: Kris Kennaway Cc: hackers@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: httpfs Message-ID: <20010310111213.A13278@cs.mcgill.ca> References: <20010310031515.A8998@mollari.cthul.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: Kris Kennaway's message [httpfs] as of Sat, Mar 10, 2001 at 03:15:15AM -0800 Organization: I speak for myself, operating in Montreal, CANADA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mar 10, Kris Kennaway wrote: > A few of us were talking on IRC tonight about how cool it would be to > have an httpfs filesystem -- then it occurred to me we almost have > this already, in the form of the (under-utilised) portalfs. Portalfs > works by handing off everything to a userland daemon which handles the > actual transaction request, so you could easily imagine extending it > to provide an http method similar to the tcp method it currently has > for initiating tcp connections. [...] Reminds me on something I read. http://zowie.metnet.navy.mil/~oleg/ftp/USENIX99/ --Mat -- Mathew Kanner Sys Admin at large Obtuse quote: He [not me] understands: "This field of perception is void of perception of man." -- The Quintessence of Buddhism To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 8:30:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id 8788A37B718 for ; Sat, 10 Mar 2001 08:30:09 -0800 (PST) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f2AGU8204557 for ; Sat, 10 Mar 2001 10:30:08 -0600 (CST) Message-Id: <200103101630.f2AGU8204557@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: hackers@freebsd.org Subject: Re: if_fxp - the real point In-reply-to: Your message of "Sat, 10 Mar 2001 01:33:31 EST." <20010310013331.A57865@earl-grey.cloud9.net> Date: Sat, 10 Mar 2001 10:30:08 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010310013331.A57865@earl-grey.cloud9.net>, Chen Zhao writes: >What is the next most (unofficially of course :) recommended NIC >in terms of driver stability, card reliability and performance, >and driver efficiency (low overhead, etc.), ignoring for the moment >actual NIC price, and just judging from a technical perspective? For that matter, is the fxp still the most-recommended driver on Alpha? I was playing with ethernet cards on a NetBSD/Alpha system, and under NetBSD, on an Alpha, a 3Com Etherlink XL ran rings around an Intel card... But on i386, I get at least as good performance from the Intel cards. Skimming the driver, I got the impression there were some alignment issues that might be cheaper to solve on i386 than Alpha. >Would the xl be next on the list, or would it be one of the previously >mentioned D-Link/Netgear cards for which documentation is freely >available? I've always thought that the latter brands were lower >performance cards... The tulip cards can be quirky, if nothing else. I used to like the VIA Rhine cards, because they were cheap, and I had no problems with them... until suddenly they started crashing at 100Mbps. I don't know why; I ran some of them under very heavy loads at 100Mbps. I can't tell whether it was new cards or a driver change. Jason Thorpe did a radically reworked Tulip driver for NetBSD that seems to handle the majority of the cheapo 21140-series clones quite nicely. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 9:42:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 9E2D737B71A for ; Sat, 10 Mar 2001 09:42:50 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id MAA87406 for hackers@freebsd.org; Sat, 10 Mar 2001 12:42:49 -0500 (EST) (envelope-from mwlucas) Date: Sat, 10 Mar 2001 12:42:49 -0500 From: Michael Lucas To: hackers@freebsd.org Subject: context or unified diffs in PRs? Message-ID: <20010310124249.A87381@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm afraid I might be walking up to a bikeshed with a can of paint here, but the flood of email in the last twenty-four hours has convinced me to ask. In an article O'Reilly published yesterday, I stated (per the Handbook) that context diffs were the correct way to submit patches with PRs. I've had several people claim that unified diffs are the way to go, and that the handbook is just wrong. Is the Handbook correct, or are unified diffs preferred? I'll be happy to fix my article and submit a PR to correct the Handbook if this is the case. Thanks, Michael -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 10:31:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 6E15F37B729 for ; Sat, 10 Mar 2001 10:31:07 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f2AIUAH63811; Sat, 10 Mar 2001 10:30:11 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: averycfay@yahoo.com Cc: hackers@FreeBSD.ORG Subject: Re: Getting started (hacking that is) In-Reply-To: <060701c0a8e4$aee61ce0$0101a8c0@tiger> References: <060701c0a8e4$aee61ce0$0101a8c0@tiger> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010310103010U.jkh@osd.bsdi.com> Date: Sat, 10 Mar 2001 10:30:10 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 46 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Avery Fay" Subject: Getting started (hacking that is) Date: Fri, 9 Mar 2001 17:02:49 -0500 > I am interested in contributing code to the FreeBSD project, specifically > the kernel but I am not opposed to helping out with user applications if > they are in dire need of improvements. To preface my request for assistance, > I should tell everyone that I am young (18) without extensive programming > experience although I have held two jobs programming in C and feel fairly > comfortable doing so. Although I've never worked on a kernel I am currently > reading "The Design and Implementation of the 4.4BSD OS" and "Modern > Operating Systems: Design and Implementation" so hopefully I have a rough > understanding of the theory. It sounds like you're reading all the right stuff, anyway! Don't worry about your age or lack of experience - we all had to start somewhere. :) We all also weren't fortune enough to have complete source code for some of the OSes we wished to modify, so you're already starting well ahead of the curve. It's a good time to be learning about operating systems. > I have heard that writing or improving device drivers if one of the easier > methods to introduce oneself to kernel programming. Unfortunately (or > fortunately I guess), all of my hardware works with FreeBSD. I guess my I'm not sure writing a device driver is the best place to _start_, though it's certainly something which will acquaint you with many different parts of the OS. If you can actually get a driver written to the point where it probes and talks to a piece of hardware (if only on a rudimentary basis) then you've come pretty far. To begin with, however, you may wish to look through the PR database and find a relatively small problem to work on. That will truly get you into the areas of FreeBSD which need attention (thus making a valuable contribution) and allow you to learn along the way without taking on a big challenge which may prove intimidating. If you're really keen to do a device driver, and I certainly wouldn't want to discourage you if that's your bent, then you might consider working on something like a sound card or helping Cameron Grant with his generic mixing/effects audio framework. There are also a number of USB peripherals which need support, but that's jumping in at the deep end. Good luck! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 10:36:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 3B30337B719 for ; Sat, 10 Mar 2001 10:36:43 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f2AIarV39589; Sat, 10 Mar 2001 19:36:53 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Michael Lucas Cc: hackers@FreeBSD.ORG Subject: Re: context or unified diffs in PRs? In-Reply-To: Your message of "Sat, 10 Mar 2001 12:42:49 EST." <20010310124249.A87381@blackhelicopters.org> Date: Sat, 10 Mar 2001 19:36:53 +0100 Message-ID: <39587.984249413@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010310124249.A87381@blackhelicopters.org>, Michael Lucas writes: >Hello, > >I'm afraid I might be walking up to a bikeshed with a can of paint >here, but the flood of email in the last twenty-four hours has >convinced me to ask. > >In an article O'Reilly published yesterday, I stated (per the >Handbook) that context diffs were the correct way to submit patches >with PRs. I've had several people claim that unified diffs are the >way to go, and that the handbook is just wrong. Unified diffs are also context diffs. Context diffs are named such because they contain undisturbed context around the changed lines, unlike normal diffs. Unified diffs are generally smaller than "plain" context diffs, and some people find them more readable and some don't. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 10:40:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id D422437B719; Sat, 10 Mar 2001 10:40:08 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f2AIaVh18783; Sat, 10 Mar 2001 13:36:31 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 10 Mar 2001 13:36:30 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Kris Kennaway Cc: hackers@FreeBSD.org, fs@FreeBSD.org Subject: Re: httpfs In-Reply-To: <20010310031515.A8998@mollari.cthul.hu> 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 need not remind you that file systems front-ending onto random protocols are a bad idea for a huge number of reasons :-). That said, you might take a look at Intermezzo, which someone has already refered to indirectly in response to your e-mail -- Intermezzo is a file system for Linux (based on Coda) that allows perl programs to provide the back-end for a file system. I assume this is done in the style of AFS/Arla/Coda by having a small kernel module that up-calls to userland using a /dev/whatever entry, and then a userland program that satisfies the requests in some or another way. If you're really interested in implementing yet-another-nasty-file-system-abomination, take a look at Arla and rip out the AFS bits and replace them with HTTP bits :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Sat, 10 Mar 2001, Kris Kennaway wrote: > A few of us were talking on IRC tonight about how cool it would be to > have an httpfs filesystem -- then it occurred to me we almost have > this already, in the form of the (under-utilised) portalfs. Portalfs > works by handing off everything to a userland daemon which handles the > actual transaction request, so you could easily imagine extending it > to provide an http method similar to the tcp method it currently has > for initiating tcp connections. > > One could probably make this more generic and finish implementing the > undocumented 'exec' method (which currently exists as a stub): this > would run an administrator-specified command (i.e. fixed in > /etc/portal.conf) and pipe the output back to the user. > > A fully navigable httpfs (e.g. one you can ls and cd around in) is > more work and probably requires a full stacking layer, but this would > still be pretty cool. > > Is anyone feeling inspired to implement this? :-) > > Kris > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 10:49:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kzsu.stanford.edu (KZSU.Stanford.EDU [171.66.118.90]) by hub.freebsd.org (Postfix) with ESMTP id 68E5A37B718 for ; Sat, 10 Mar 2001 10:49:31 -0800 (PST) (envelope-from romain@kzsu.stanford.edu) Received: (from romain@localhost) by kzsu.stanford.edu (8.9.3/8.9.3) id KAA85992; Sat, 10 Mar 2001 10:49:31 -0800 (PST) (envelope-from romain) Date: Sat, 10 Mar 2001 10:49:31 -0800 (PST) From: Romain Kang Message-Id: <200103101849.KAA85992@kzsu.stanford.edu> To: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point Reply-To: romain@kzsu.stanford.edu Organization: KZSU 90.1 FM, Stanford, Calif. USA X-Newsreader: NN version 6.5.3 (NOV) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As a newcomer to this, I'm a little confused. There's a slew of datasheets at Intel's web site http://www.intel.com/design/network/datashts/index.htm that don't seem to require NDA. (Just this week, I used the 82559 docs to implement a polled version of if_fxp). If the components in question are not there, can anyone identify them? Romain Kang Disclaimer: I speak for myself alone, romain@kzsu.stanford.edu except when indicated otherwise. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 10:52:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2C1AF37B718 for ; Sat, 10 Mar 2001 10:52:34 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2AIoPb10093; Sat, 10 Mar 2001 10:50:25 -0800 (PST) Date: Sat, 10 Mar 2001 10:50:25 -0800 From: Alfred Perlstein To: Poul-Henning Kamp Cc: Michael Lucas , hackers@FreeBSD.ORG Subject: Re: context or unified diffs in PRs? Message-ID: <20010310105020.C18351@fw.wintelcom.net> References: <20010310124249.A87381@blackhelicopters.org> <39587.984249413@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39587.984249413@critter>; from phk@critter.freebsd.dk on Sat, Mar 10, 2001 at 07:36:53PM +0100 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Poul-Henning Kamp [010310 10:37] wrote: > In message <20010310124249.A87381@blackhelicopters.org>, Michael Lucas writes: > >Hello, > > > >I'm afraid I might be walking up to a bikeshed with a can of paint > >here, but the flood of email in the last twenty-four hours has > >convinced me to ask. > > > >In an article O'Reilly published yesterday, I stated (per the > >Handbook) that context diffs were the correct way to submit patches > >with PRs. I've had several people claim that unified diffs are the > >way to go, and that the handbook is just wrong. > > Unified diffs are also context diffs. > > Context diffs are named such because they contain undisturbed context > around the changed lines, unlike normal diffs. > > Unified diffs are generally smaller than "plain" context diffs, and > some people find them more readable and some don't. It's usually a judgement call, depending on the change a context diff can be less of a pain to read. -- -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 Mar 10 10:53:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 6475D37B71C for ; Sat, 10 Mar 2001 10:53:24 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f2AIomg75678; Sat, 10 Mar 2001 12:50:48 -0600 (CST) (envelope-from jlemon) Date: Sat, 10 Mar 2001 12:50:48 -0600 (CST) From: Jonathan Lemon Message-Id: <200103101850.f2AIomg75678@prism.flugsvamp.com> To: zhaoc@cloud9.net, hackers@freebsd.org Subject: Re: if_fxp - the real point X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >\- Peter Wemm stated on >/- [Sat, Mar 10, 2001 at 04:49:12AM -0800]: > >> I have the NDA'ed docs for the Intel gig and fxp cards. After Intel's >> spectacular efforts to bury Johnathan Lemon's driver for their gig card >> (that outperformed the Intel Linux driver by something like a factor of 5), >> I have lost all respect for Intel's networking division. > >Sorry to hear that. The last thing I can find on the Intel gig stuff >was dated at the end of 1999, where Johnathan Lemon wasn't sure if >he could release his version, and Matt Jacob had a version hacked from >the released Linux drivers. I take it Intel didn't give the hoped for >permission. Nope. The last communication I had with Intel was around last May. Initially, the Field Engineer indicated that Intel wanted to get a copy of my driver in order to clean it up and put it on Intel's website. I provided Intel with the driver, and they passed it to their engineering team. The last I heard was that they claimed the driver had 'issues', but were unwilling to tell me what those were, or what I would need to do in order to release the driver. The message I received indicated that they were investigating simply developing their own driver for BSD instead. I never heard anything from Intel since then. So, the status is: 1. I have a working high performance driver, but cannot legally release the source. I have no idea why, since it doesn't reveal any information that can't already be found in the Linux driver. 2. Intel has my driver, under the BSD license, so they could release it if they feel like. Apparently they do not see the need to do so. If anyone wants to lean on their Intel reps to see if they can get the situation changed, or at least provide me with an explanation for what I see as their idiotic behavior, I'd be happy to work with them. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 10:57:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A34F837B71A for ; Sat, 10 Mar 2001 10:56:54 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA27084; Sat, 10 Mar 2001 10:56:52 -0800 Date: Sat, 10 Mar 2001 10:56:49 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jonathan Lemon Cc: zhaoc@cloud9.net, hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point In-Reply-To: <200103101850.f2AIomg75678@prism.flugsvamp.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 > >permission. > > Nope. The last communication I had with Intel was around last May. > Initially, the Field Engineer indicated that Intel wanted to get a > copy of my driver in order to clean it up and put it on Intel's website. > > I provided Intel with the driver, and they passed it to their engineering > team. The last I heard was that they claimed the driver had 'issues', > but were unwilling to tell me what those were, or what I would need to do > in order to release the driver. The message I received indicated that they > were investigating simply developing their own driver for BSD instead. > > I never heard anything from Intel since then. > > So, the status is: > > 1. I have a working high performance driver, but cannot legally > release the source. I have no idea why, since it doesn't reveal > any information that can't already be found in the Linux driver. > 2. Intel has my driver, under the BSD license, so they could release > it if they feel like. Apparently they do not see the need to do so. > > If anyone wants to lean on their Intel reps to see if they can get the > situation changed, or at least provide me with an explanation for what > I see as their idiotic behavior, I'd be happy to work with them. Let me chime in and say I sort of still do support and maintain my version in both OpenBSD and FreeBSD, but if Jonathon's was freed up, I'm sure it'd be better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 11:11:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 3B7C037B718 for ; Sat, 10 Mar 2001 11:11:35 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f2AJ8wr76450; Sat, 10 Mar 2001 13:08:58 -0600 (CST) (envelope-from jlemon) Date: Sat, 10 Mar 2001 13:08:58 -0600 (CST) From: Jonathan Lemon Message-Id: <200103101908.f2AJ8wr76450@prism.flugsvamp.com> To: romain@kzsu.stanford.edu, hackers@freebsd.org Subject: Re: if_fxp - the real point X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >As a newcomer to this, I'm a little confused. There's a slew >of datasheets at Intel's web site > http://www.intel.com/design/network/datashts/index.htm >that don't seem to require NDA. (Just this week, I used the >82559 docs to implement a polled version of if_fxp). > >If the components in question are not there, can anyone identify them? Datasheets != manuals. The datasheet simply tells you "this is the overall purpose of this feature". "This is a high level view of selected registers". What it doesn't tell you is how to put everything together, nor does it provide critical information such as the layout of the datastructures needed. Take a concrete example, the datasheet for the 82558: http://www.intel.com/design/network/datashts/297360.htm S 4.1.2.7 describes how the chip DMAs data to/from host memory. What is the layout of the control block for the transfer? S 4.2 talks about the EEPROM interface. How do you determine the size of the attached EEPROM, which is needed in order to know how many address bits to shift in? S 4.3.2 mentions PHY flow control; PHY based and flow based. How do you select between these two? Where do you set up the flow control parameters? You can't find the answers to any of these in the datasheets. The datasheets may provide a tiny bit of information, and hint at how things actually operate, but there is not sufficient information to develop a driver from them. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 11:33: 4 2001 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 78F5C37B719 for ; Sat, 10 Mar 2001 11:32:56 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p31-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.96]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id EAA05419; Sun, 11 Mar 2001 04:32:44 +0900 (JST) Message-ID: <3AAA80A8.1C6D6D76@newsguy.com> Date: Sun, 11 Mar 2001 04:29:44 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Michael Lucas Cc: hackers@FreeBSD.ORG Subject: Re: context or unified diffs in PRs? References: <20010310124249.A87381@blackhelicopters.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Lucas wrote: > > Hello, > > I'm afraid I might be walking up to a bikeshed with a can of paint > here, but the flood of email in the last twenty-four hours has > convinced me to ask. > > In an article O'Reilly published yesterday, I stated (per the > Handbook) that context diffs were the correct way to submit patches > with PRs. I've had several people claim that unified diffs are the > way to go, and that the handbook is just wrong. > > Is the Handbook correct, or are unified diffs preferred? I'll be > happy to fix my article and submit a PR to correct the Handbook if > this is the case. Either will do. Unified diffs are less verbose, but sometimes they are too confusing to be of any use. The point is to use _either_ of them instead of plain diff (because both of them have "context" -- lines indicating the point were the changes are to take place). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net It's a rewarding life, but hey, somebody has to have all the fun, right? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 11:50:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 4E5E937B718; Sat, 10 Mar 2001 11:50:21 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id PAA85562; Sat, 10 Mar 2001 15:02:28 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010310145045.023a41c0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 10 Mar 2001 15:05:30 -0500 To: wpaul@FreeBSD.ORG (Bill Paul) From: Dennis Subject: Re: if_fxp - the real point Cc: hackers@FreeBSD.ORG, msmith@FreeBSD.ORG In-Reply-To: <20010310061124.E7AF437B718@hub.freebsd.org> References: <5.0.0.25.0.20010309204335.01fc2b00@mail.etinc.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 At 01:11 AM 03/10/2001, Bill Paul wrote: > > > > I think its been mentioned several times in this and other threads that > > intel has a driver for LINUX that is effective documentation on the board, > > and the code is public (although you may have to stick an intel copyright > > in the code also). > >Whoever mentioned this was not thinking clearly. A manual is effective >documentation for a NIC. Sample driver code alone is not. It's handy, but >it's not enough. When you write a driver, you make certain design decisions >based on the information in the manual and the OS you're developing for. >By forcing someone to rely soley on your driver to see how the board >works, you're limiting their ability to make their own design decisions. >What works well for Windows or Linux may be mediocre for BSD. Besides, >Intel engineers have a knack for choosing really confusing register names. confusing or not, the logic to fix the driver is available. You can whine about there being "no full documentation", but guess what? FreeBSD doesnt have "full documentation" either. Do any of your drivers have "full documentation" for anyone that want to modify them? Fixing Greenman's driver is no party either as he hasnt documented any of the phy-related stuff he uses. >And again, saying "but there's a Linux driver" just gives vendors an >excuse to perpetuate their stupidity. I'm not keen to give them this >opportunity. You "guys" regularly say to me "you have the source, fix it". Source that works IS documentation. As someone whose read a few controller specs in my time, I can tell you that "full documentation" is sometimes a lot less useful than code that works, because the docs dont always make it clear what needs to be done to achieve a certain goal. > > > You guys continue not to understand why companies dont disclose board info > > freely. You end up competing with your own customers. They dont want > people > > buying gray market parts and selling $9. boards. Its very easy to clone a > > board with 2 chips on it these days. > >I'm sorry, that doesn't wash. *I* am not trying to compete with anyone. >Lord knows I can't afford to fabricate my own controller chips on my >salary. its not about you, man, its about the clone manufacturers that can make cards that use your or intel's drivers without any engineering. You dont have to "fabricate chips", you buy them from Intel. Thats what I mean by "competing with your own customers". Intel sells chips for $8. and boards for $32. they odnt want to have to compete with boards that sell for $12. with their $8. chips. Your lame argument might be that "they sell the chips anyway" , but that doesnt work, becuase they make money on the boards at 32 and dont at 12. Notice that there arent really any Intel eepro100 clones? Because intel makes sure that the spec isnt public, so they can go after anyone that clones them. Western Digital in the 80s learned the hard way. You do all the marketing, get software written for your cards, and then the taiwanese cash in on it and you have to lower your prices to where you cant make enough money to get back your marketing outlay. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 11:55:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 19FDF37B718 for ; Sat, 10 Mar 2001 11:55:53 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id PAA85582; Sat, 10 Mar 2001 15:08:01 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010310150950.023a05f0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 10 Mar 2001 15:11:02 -0500 To: seebs@plethora.net (Peter Seebach), hackers@FreeBSD.ORG From: Dennis Subject: Re: if_fxp - the real point In-Reply-To: <200103101630.f2AGU8204557@guild.plethora.net> References: 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 > >The tulip cards can be quirky, if nothing else. I used to like the VIA Rhine >cards, because they were cheap, and I had no problems with them... until >suddenly they started crashing at 100Mbps. I don't know why; I ran some of >them under very heavy loads at 100Mbps. I can't tell whether it was new >cards or a driver change. Cards generally arent "quirky"; drivers are incomplete. Its all about the software. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 12: 4:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id CA34F37B718 for ; Sat, 10 Mar 2001 12:04:14 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f2AK3IH64302; Sat, 10 Mar 2001 12:03:18 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: mwlucas@blackhelicopters.org Cc: hackers@FreeBSD.ORG Subject: Re: context or unified diffs in PRs? In-Reply-To: <20010310124249.A87381@blackhelicopters.org> References: <20010310124249.A87381@blackhelicopters.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010310120318O.jkh@osd.bsdi.com> Date: Sat, 10 Mar 2001 12:03:18 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The handbook is wrong. Unidiffs are a far more advanced lifeform than context diffs. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 12:21:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id D33BC37B718 for ; Sat, 10 Mar 2001 12:21:15 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id PAA85678; Sat, 10 Mar 2001 15:33:19 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010310151202.02297a20@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 10 Mar 2001 15:22:46 -0500 To: romain@kzsu.stanford.edu, hackers@FreeBSD.ORG From: Dennis Subject: Re: if_fxp - the real point In-Reply-To: <200103101849.KAA85992@kzsu.stanford.edu> 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 At 01:49 PM 03/10/2001, Romain Kang wrote: >As a newcomer to this, I'm a little confused. There's a slew >of datasheets at Intel's web site > http://www.intel.com/design/network/datashts/index.htm >that don't seem to require NDA. (Just this week, I used the >82559 docs to implement a polled version of if_fxp). Is anyone up on the latest legal stuff? There was a ruling that universities cant be held liable for releasing NDA information....universities and states I think. I know we couldnt sell source to universities or the government because it wasnt protected (ie you couldnt sue them if it leaked out). Maybe we can get an academic to sign something and leak out the info :-) Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 12:22:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from diamond.gpad.ac.ru (diamond.gpad.ac.ru [193.233.9.65]) by hub.freebsd.org (Postfix) with ESMTP id 2A22137B718 for ; Sat, 10 Mar 2001 12:22:35 -0800 (PST) (envelope-from dima@Chg.RU) Received: from ppp170.dialup.corbina.ru (ppp170.dialup.corbina.ru [195.14.32.170]) by diamond.gpad.ac.ru (8.11.1/8.11.1) with ESMTP id f2AKMBD31594; Sat, 10 Mar 2001 23:22:13 +0300 (MSK) (envelope-from dima@Chg.RU) Date: Sat, 10 Mar 2001 23:21:59 +0300 From: =?koi8-r?B?5M3J1NLJyiDzydfB3sXOy88=?= X-Mailer: The Bat! (v1.48f) UNREG / CD5BF9353B3B7091 Reply-To: =?koi8-r?B?5M3J1NLJyiDzydfB3sXOy88=?= Organization: CCAS X-Priority: 3 (Normal) Message-ID: <11116211867.20010310232159@Chg.RU> To: Wilko Bulte Cc: hackers@freebsd.org Subject: Re[2]: Problem with K6-2/500 CPU In-reply-To: <20010310171408.A16883@freebie.demon.nl> References: <20010310184300.A83942@netserv1.chg.ru> <20010310171408.A16883@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Wilko, Saturday, March 10, 2001, 7:14:08 PM, you wrote: WB> On Sat, Mar 10, 2001 at 06:43:00PM +0300, Dmitry Sivachenko wrote: WB> Smells like dodgy hardware, especially memory. You are not WB> overclocking are you? WB> There are no problems with K6-2 & FreeBSD, I ran it on a K6-2 @400 WB> very successfully (now have an Athlon box). WB> Wilko I think that the problem is that I inserted this K6-2/500 into my TXP4 motherboard, and I have only 2.0 volts voltage on processor kernel instead of 2.2 required. But the problem seems to be in hardware really... Thanks for the answer. --dima >> Hello! >> >> I use recent FreeBSD-4-STABLE. >> When I changed my processor from Intel Pentium 200 MMX to AMD K6-2 500, >> I can neither recompile operating system nor compile other programs. >> >> >From kernel compilation: >> >> cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. >> -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../ufs/ffs/ffs_softdep.c >> cc: Internal compiler error: program cc1 got fatal signal 11 >> *** Error code 1 >> >> Stop in /usr/src/sys/compile/CAVIA. >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 12:37:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id E7A4E37B718 for ; Sat, 10 Mar 2001 12:37:45 -0800 (PST) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.11.1/8.11.1) id f2AKbd004373 for hackers@FreeBSD.ORG; Sat, 10 Mar 2001 14:37:39 -0600 (CST) Date: Sat, 10 Mar 2001 14:37:39 -0600 From: Tim To: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point Message-ID: <20010310143739.A3867@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a point of contact at Intel that we could all send e-mail to or even send a formal letter? I am sure my buying 50 or so boards a year isn't going to make a dent at Intel's bottom line, but considering how their stock is doing lately and if we all contribute... Thanks, Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 12:42:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 843BC37B718; Sat, 10 Mar 2001 12:42:51 -0800 (PST) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f2AKgjC03194; Sat, 10 Mar 2001 13:42:50 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200103102042.f2AKgjC03194@aslan.scsiguy.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: wpaul@FreeBSD.ORG (Bill Paul) Cc: hackers@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: call for testers: port aggregation netgraph module In-Reply-To: Your message of "Thu, 08 Feb 2001 13:25:09 PST." <20010208212509.E8D7D37B6AA@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Mar 2001 13:42:45 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Each link is checked once every second to see if the link is still up. >An attempt to send a packet over a dead link will cause the packet to >be shifted over to the next link in the bundle. Any chance this can be done through an async event rather than by polling? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 12:44: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id D705037B718 for ; Sat, 10 Mar 2001 12:44:03 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id PAA85786; Sat, 10 Mar 2001 15:56:13 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010310155434.0329e670@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 10 Mar 2001 15:59:14 -0500 To: Tim , hackers@FreeBSD.ORG From: Dennis Subject: Re: if_fxp - the real point In-Reply-To: <20010310143739.A3867@futuresouth.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 At 03:37 PM 03/10/2001, Tim wrote: >Is there a point of contact at Intel that we could all send e-mail to or >even send a formal letter? I am sure my buying 50 or so boards a year >isn't going to make a dent at Intel's bottom line, but considering how >their stock is doing lately and if we all contribute... Um, I dont think your going to get intel to change its policy The policy exists for a reason. Plus, they are already selling lots of boards with the existing driver, so how many more will they sell? the delta isnt enough for them to put someone on the case. What will really get them is some press on how bad their drivers are. Their eepro100 driver for linux is unusable under load. and from what I've hard their gigabit driver isnt much better. Letters dont do anything. its all about image. Dennis >Thanks, > >Tim > >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 Sat Mar 10 12:46:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id C1D3437B719 for ; Sat, 10 Mar 2001 12:46:25 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f2AKeqH64500; Sat, 10 Mar 2001 12:40:52 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: phk@critter.freebsd.dk Cc: mwlucas@blackhelicopters.org, hackers@FreeBSD.ORG Subject: Re: context or unified diffs in PRs? In-Reply-To: <39587.984249413@critter> References: <20010310124249.A87381@blackhelicopters.org> <39587.984249413@critter> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010310124052O.jkh@osd.bsdi.com> Date: Sat, 10 Mar 2001 12:40:52 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 44 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Unified diffs are also context diffs. > > Context diffs are named such because they contain undisturbed context > around the changed lines, unlike normal diffs. Erm, no. :) Both context and unidiffs show surrounding context, it's simply the meta-data format which changes. In the case of unidiffs, the presentation of multiple diffs in one file is rather more readable and easy to edit without throwing off patch(1), otherwise they look almost identical in their presentation of "undisturbed context" for one diff: From the diff(1) man page: -c Use the context output format. -u Use the unified output format. [and a list of ten numbers, the new version eliding the "five"] % diff -c numbers.orig numbers *** numbers.orig Sat Mar 10 12:34:51 2001 --- numbers Sat Mar 10 12:34:54 2001 *************** *** 2,8 **** two three four - five six seven eight --- 2,7 ---- % diff -u numbers.orig numbers --- numbers.orig Sat Mar 10 12:34:51 2001 +++ numbers Sat Mar 10 12:34:54 2001 @@ -2,7 +2,6 @@ two three four -five six seven eight To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 12:47: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1839937B719 for ; Sat, 10 Mar 2001 12:47:05 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA27576; Sat, 10 Mar 2001 12:47:05 -0800 Date: Sat, 10 Mar 2001 12:47:02 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Tim Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point In-Reply-To: <20010310143739.A3867@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 My point of (failed) contact last April was a Gary @ 503 264 7243 (I was informed by Theo that he was "Intel's 'Open Source' representative) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 12:50:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id D8D8A37B719 for ; Sat, 10 Mar 2001 12:50:26 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f2AKoeV40513; Sat, 10 Mar 2001 21:50:40 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Jordan Hubbard Cc: mwlucas@blackhelicopters.org, hackers@FreeBSD.ORG Subject: Re: context or unified diffs in PRs? In-Reply-To: Your message of "Sat, 10 Mar 2001 12:40:52 PST." <20010310124052O.jkh@osd.bsdi.com> Date: Sat, 10 Mar 2001 21:50:40 +0100 Message-ID: <40511.984257440@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010310124052O.jkh@osd.bsdi.com>, Jordan Hubbard writes: >> Unified diffs are also context diffs. >> >> Context diffs are named such because they contain undisturbed context >> around the changed lines, unlike normal diffs. > >Erm, no. :) > >Both context and unidiffs show surrounding context, it's simply the >meta-data format which changes. In the case of unidiffs, the >presentation of multiple diffs in one file is rather more readable and >easy to edit without throwing off patch(1), otherwise they look almost >identical in their presentation of "undisturbed context" for one diff: I repeat, with added emphasis: >> Unified diffs are *also* context diffs. >> >> Context diffs are named such because they contain undisturbed context >> around the changed lines, unlike *normal* diffs. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 13: 2:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 29B8537B718; Sat, 10 Mar 2001 13:02:39 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id QAA85883; Sat, 10 Mar 2001 16:14:42 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010310161340.01fda9a0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 10 Mar 2001 16:17:43 -0500 To: "Justin T. Gibbs" , wpaul@FreeBSD.ORG (Bill Paul) From: Dennis Subject: Re: call for testers: port aggregation netgraph module Cc: hackers@FreeBSD.ORG, net@FreeBSD.ORG In-Reply-To: <200103102042.f2AKgjC03194@aslan.scsiguy.com> References: 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 At 03:42 PM 03/10/2001, Justin T. Gibbs wrote: > >Each link is checked once every second to see if the link is still up. > >An attempt to send a packet over a dead link will cause the packet to > >be shifted over to the next link in the bundle. > >Any chance this can be done through an async event rather >than by polling? I've been meaning to ask about this...is there a reason that ethernet drivers dont call if_up and if_down like serial drivers on cable events? This is needed for load balancing so that the UP flag can be used instead of polling or an event. Of course a polling protocol is needed also. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 13: 7: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 2284F37B718; Sat, 10 Mar 2001 13:07:00 -0800 (PST) Subject: Re: call for testers: port aggregation netgraph module In-Reply-To: <200103102042.f2AKgjC03194@aslan.scsiguy.com> from "Justin T. Gibbs" at "Mar 10, 2001 01:42:45 pm" To: gibbs@scsiguy.com (Justin T. Gibbs) Date: Sat, 10 Mar 2001 13:07:00 -0800 (PST) Cc: hackers@FreeBSD.ORG, net@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 Message-Id: <20010310210700.2284F37B718@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Each link is checked once every second to see if the link is still up. > >An attempt to send a packet over a dead link will cause the packet to > >be shifted over to the next link in the bundle. > > Any chance this can be done through an async event rather > than by polling? If there was, I would have done it. MII transceivers can't send an interrupt back through the MAC unless the MAC supports it, and many don't. Consequently, the MII spec says nothing about async notification of anything. You have to poll. Resistance is futile. Gigabit MII transceivers are another matter. Polling and gigabit speeds don't go to gether very well. All of the GMII transceivers I've seen (Tigon and SysKonnect cards) have an signal pin of some kind that's wired to an external interrupt source pin on the MAC. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 13:37:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 80C9037B718; Sat, 10 Mar 2001 13:37:49 -0800 (PST) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f2ALbmC04064; Sat, 10 Mar 2001 14:37:48 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200103102137.f2ALbmC04064@aslan.scsiguy.com> To: wpaul@FreeBSD.ORG (Bill Paul) Cc: hackers@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: call for testers: port aggregation netgraph module In-Reply-To: Your message of "Sat, 10 Mar 2001 13:07:00 PST." <20010310210700.2284F37B718@hub.freebsd.org> Date: Sat, 10 Mar 2001 14:37:48 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >Each link is checked once every second to see if the link is still up. >> >An attempt to send a packet over a dead link will cause the packet to >> >be shifted over to the next link in the bundle. >> >> Any chance this can be done through an async event rather >> than by polling? > >If there was, I would have done it. Perhaps it would be best to create an interface that allows async notification but to provide a default implementation of the interface that polls? This would allow hardware that has a mechanism to detect the state change to override the default method while all other cards "just work" without modification by polling. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 14:26:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id A6D1737B719 for ; Sat, 10 Mar 2001 14:26:44 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14brox-000OAC-00; Sat, 10 Mar 2001 22:26:43 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.2/8.11.2) id f2AMSfj28511; Sat, 10 Mar 2001 23:28:41 +0100 (CET) (envelope-from wkb) Date: Sat, 10 Mar 2001 23:28:41 +0100 From: Wilko Bulte To: Dmitrij Sivacenko Cc: hackers@freebsd.org Subject: Re: Problem with K6-2/500 CPU Message-ID: <20010310232841.H28312@freebie.demon.nl> References: <20010310184300.A83942@netserv1.chg.ru> <20010310171408.A16883@freebie.demon.nl> <11116211867.20010310232159@Chg.RU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <11116211867.20010310232159@Chg.RU>; from dima@Chg.RU on Sat, Mar 10, 2001 at 11:21:59PM +0300 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 10, 2001 at 11:21:59PM +0300, Dmitrij Sivacenko wrote: > > WB> Smells like dodgy hardware, especially memory. You are not > WB> overclocking are you? > > WB> There are no problems with K6-2 & FreeBSD, I ran it on a K6-2 @400 > WB> very successfully (now have an Athlon box). > > WB> Wilko > > I think that the problem is that I inserted this K6-2/500 into my TXP4 > motherboard, and I have only 2.0 volts voltage on processor kernel instead of > 2.2 required. But the problem seems to be in hardware really... OK, sounds reasonable. I ran my K6-2/400 in an old T2P4 with a small hardware hack to get the right core voltage. Worked brilliantly. Never tried a TXP4 -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 14:31:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 6EF1237B718; Sat, 10 Mar 2001 14:31:50 -0800 (PST) Subject: Re: call for testers: port aggregation netgraph module In-Reply-To: <200103102137.f2ALbmC04064@aslan.scsiguy.com> from "Justin T. Gibbs" at "Mar 10, 2001 02:37:48 pm" To: gibbs@scsiguy.com (Justin T. Gibbs) Date: Sat, 10 Mar 2001 14:31:50 -0800 (PST) Cc: hackers@FreeBSD.ORG, net@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 Message-Id: <20010310223150.6EF1237B718@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> >Each link is checked once every second to see if the link is still up. > >> >An attempt to send a packet over a dead link will cause the packet to > >> >be shifted over to the next link in the bundle. > >> > >> Any chance this can be done through an async event rather > >> than by polling? > > > >If there was, I would have done it. > > Perhaps it would be best to create an interface that allows async > notification but to provide a default implementation of the interface > that polls? This would allow hardware that has a mechanism to detect > the state change to override the default method while all other > cards "just work" without modification by polling. Perhaps somebody who is not me should investigate this then. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 16: 7:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Spaz.HuntsvilleAL.COM (spaz.huntsvilleal.com [63.147.8.31]) by hub.freebsd.org (Postfix) with ESMTP id 954C737B719 for ; Sat, 10 Mar 2001 16:07:35 -0800 (PST) (envelope-from kris@catonic.net) Received: from localhost (kris@localhost) by Spaz.HuntsvilleAL.COM (8.9.3/8.9.3) with ESMTP id AAA92485; Sun, 11 Mar 2001 00:06:57 GMT (envelope-from kris@catonic.net) Date: Sun, 11 Mar 2001 00:06:57 +0000 (GMT) From: Kris Kirby X-Sender: kris@spaz.huntsvilleal.com To: Dag-Erling Smorgrav Cc: "Koster, K.J." , heckfordj@psi-domain.co.uk, freebsd-hackers@FreeBSD.ORG Subject: Re: Clustering FreeBSD In-Reply-To: Message-ID: X-Tech-Support-Email: bofh@catonic.net 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 Jan 2001, Dag-Erling Smorgrav wrote: > Fun Things To Do With Disks #9,187: > > Take a powered-up disk out of a hot-swap storage array and experiment > with the gyro effect while the disk spins down in your hands. Higher > RPMs give better results; try one of the 'cudas from that E10K in the > corner... "if you do it quickly, nobody will notice" Maybe I need to install more 10K drives in my desktop machine; that should keep it from being able to fall over.... ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "Fate, it seems, is not without a sense of irony." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 17: 6:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 1C4EF37B718 for ; Sat, 10 Mar 2001 17:06:54 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@dhcp152.geekhouse.net [192.168.1.152]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f2B18J152690; Sat, 10 Mar 2001 17:08:21 -0800 (PST) (envelope-from jhb@FreeBSD.org) 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: <20010310120318O.jkh@osd.bsdi.com> Date: Sat, 10 Mar 2001 17:06:28 -0800 (PST) From: John Baldwin To: Jordan Hubbard Subject: Re: context or unified diffs in PRs? Cc: hackers@FreeBSD.org, mwlucas@blackhelicopters.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Mar-01 Jordan Hubbard wrote: > The handbook is wrong. Unidiffs are a far more advanced lifeform > than context diffs. :) > > - Jordan As phk explained, a unified diff is a context diff. :) If many changed lines are interleaved with unchanged lines, I find that a context diff is far easier to read to understand the change than unified diff. For smaller changes, a unified diff is usually more compact and points out the individual changes more readily. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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 Mar 10 17:33:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 3791437B71A for ; Sat, 10 Mar 2001 17:33:27 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id CAA32735; Sun, 11 Mar 2001 02:33:21 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Richard Hodges Cc: Rafael Tonin , freebsd-hackers@FreeBSD.ORG Subject: Re: Intel PRO/100+ PCI problem References: From: Dag-Erling Smorgrav Date: 11 Mar 2001 02:33:20 +0100 In-Reply-To: Richard Hodges's message of "Thu, 8 Mar 2001 09:15:45 -0800 (PST)" Message-ID: Lines: 12 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Hodges writes: > On Thu, 8 Mar 2001, Rafael Tonin wrote: > > Anyone knows how to get this card to work? > Go into your BIOS config and turn off the option > for "PLUG & PLAY OS". It should be with the PCI menu. No, turn "PLUG & PLAY OS" *on* and add 'options PNPBIOS' to your kernel. If that doesn't solve your problem, we have a bug. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 18:13: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8247937B718 for ; Sat, 10 Mar 2001 18:12:58 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id DAA32861; Sun, 11 Mar 2001 03:10:24 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Poul-Henning Kamp Cc: Jordan Hubbard , mwlucas@blackhelicopters.org, hackers@FreeBSD.ORG Subject: Re: context or unified diffs in PRs? References: <40511.984257440@critter> From: Dag-Erling Smorgrav Date: 11 Mar 2001 03:10:24 +0100 In-Reply-To: Poul-Henning Kamp's message of "Sat, 10 Mar 2001 21:50:40 +0100" Message-ID: Lines: 93 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > In message <20010310124052O.jkh@osd.bsdi.com>, Jordan Hubbard writes: > > Both context and unidiffs show surrounding context, it's simply the > > meta-data format which changes. [...] > I repeat, with added emphasis: [...] You're both either slightly off, or not expressing yourselves clearly. Context diffs are called that because they show context around the changes. Unified diffs are also context diffs, but they're unified because they show removed and added lines in a single block instead of separate blocks: des@flood ~% diff -c old new *** old Sun Mar 11 03:04:43 2001 --- new Sun Mar 11 03:05:02 2001 *************** *** 1,7 **** one two three ! fore five six seven --- 1,7 ---- one two three ! four five six seven des@flood ~% diff -u old new --- old Sun Mar 11 03:04:43 2001 +++ new Sun Mar 11 03:05:02 2001 @@ -1,7 +1,7 @@ one two three -fore +four five six seven Unified diffs are almost always easier to read, because you don't have to move your eyes back and forth so much. Context diffs are easier to read in the rare cases where a large nearly-contiguous block of text has changed and diff(1) screws up because it finds that some of lines in the new text are identical to some of the lines in the old text, while in fact they're not related: des@flood ~% diff -c old new *** old Sun Mar 11 03:07:31 2001 --- new Sun Mar 11 03:08:08 2001 *************** *** 1,7 **** ! the little ! horse ! jumped ! over ! the ! fence --- 1,7 ---- ! three ! ducks ! swim ! in ! a little ! pond des@flood ~% diff -u old new --- old Sun Mar 11 03:07:31 2001 +++ new Sun Mar 11 03:08:08 2001 @@ -1,7 +1,7 @@ -the +three +ducks +swim +in +a little -horse -jumped -over -the -fence +pond DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 18:28:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id 7AD7B37B718 for ; Sat, 10 Mar 2001 18:28:29 -0800 (PST) (envelope-from dmiller@sparks.net) Received: by search.sparks.net (Postfix, from userid 100) id 423D9DB2A; Sat, 10 Mar 2001 21:26:55 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id 333E4DB28 for ; Sat, 10 Mar 2001 21:26:55 -0500 (EST) Date: Sat, 10 Mar 2001 21:26:55 -0500 (EST) From: David Miller To: freebsd-hackers@freebsd.org Subject: [OT] Fibre channel enclosures? 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 Apologies for the off topic nature of the question... I see FC drives for sale unbelievably cheap in a number of places. megahaus.com has 36 GB IBM FC drives for $219, pricewatch has 9 GB and 18 GB drives from seagate and IBM for under $100. The issue, of course, is that one needs a low cost enclosure to mount them in. Any suggestions? I'm looking for something less expensive than JMR's Fortra series. Very nice, but a bit pricey at 2 thousand plus. Thanks in advance, --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 18:52:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ghs.ssd.k12.wa.us (locutus.ghs.ssd.k12.wa.us [216.186.55.25]) by hub.freebsd.org (Postfix) with ESMTP id BEDC837B719 for ; Sat, 10 Mar 2001 18:52:09 -0800 (PST) (envelope-from protozoa@ghs.ssd.k12.wa.us) Received: from localhost (protozoa@localhost) by ghs.ssd.k12.wa.us (8.9.3/8.9.3) with ESMTP id SAA88479; Sat, 10 Mar 2001 18:52:01 -0800 (PST) (envelope-from protozoa@ghs.ssd.k12.wa.us) Date: Sat, 10 Mar 2001 18:51:56 -0800 (PST) From: Dan Feldman To: David Miller Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: [OT] Fibre channel enclosures? 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 www.cinonic.com, I think. - dan feldman student, garfield high school, seattle On Sat, 10 Mar 2001, David Miller wrote: > Apologies for the off topic nature of the question... > > I see FC drives for sale unbelievably cheap in a number of > places. megahaus.com has 36 GB IBM FC drives for $219, pricewatch has 9 > GB and 18 GB drives from seagate and IBM for under $100. > > The issue, of course, is that one needs a low cost enclosure to mount > them in. > > Any suggestions? I'm looking for something less expensive than JMR's > Fortra series. Very nice, but a bit pricey at 2 thousand plus. > > Thanks in advance, > > --- David > > > 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 Sat Mar 10 19: 5:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ghs.ssd.k12.wa.us (locutus.ghs.ssd.k12.wa.us [216.186.55.25]) by hub.freebsd.org (Postfix) with ESMTP id BDCAC37B718 for ; Sat, 10 Mar 2001 19:05:27 -0800 (PST) (envelope-from protozoa@ghs.ssd.k12.wa.us) Received: from localhost (protozoa@localhost) by ghs.ssd.k12.wa.us (8.9.3/8.9.3) with ESMTP id TAA89642; Sat, 10 Mar 2001 19:05:25 -0800 (PST) (envelope-from protozoa@ghs.ssd.k12.wa.us) Date: Sat, 10 Mar 2001 19:05:25 -0800 (PST) From: Dan Feldman To: David Miller Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: [OT] Fibre channel enclosures? 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 Sorry to continue more OT stuff, but: What FC host adapters are working well in FreeBSD? I just found an Adaptec model used for very cheap. It's actually possible that Fiber Channel could be cheaper than Ultra160 if you build your own enclosure with Cinonic cards, buy clearance 1 GHz drives, and are lucky enough to find a very cheap used host adapter. I'm not sure this is a good thing, since it doesn't seem like Fiber Channel is easy to set up reliably.... - dan feldman student, garfield high school, seattle On Sat, 10 Mar 2001, David Miller wrote: > Apologies for the off topic nature of the question... > > I see FC drives for sale unbelievably cheap in a number of > places. megahaus.com has 36 GB IBM FC drives for $219, pricewatch has 9 > GB and 18 GB drives from seagate and IBM for under $100. > > The issue, of course, is that one needs a low cost enclosure to mount > them in. > > Any suggestions? I'm looking for something less expensive than JMR's > Fortra series. Very nice, but a bit pricey at 2 thousand plus. > > Thanks in advance, > > --- David > > > 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 Sat Mar 10 19:25:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 34E3837B718 for ; Sat, 10 Mar 2001 19:25:38 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2B3PYI23728; Sat, 10 Mar 2001 20:25:35 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103110325.f2B3PYI23728@harmony.village.org> To: Michael Lucas Subject: Re: context or unified diffs in PRs? Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 10 Mar 2001 12:42:49 EST." <20010310124249.A87381@blackhelicopters.org> References: <20010310124249.A87381@blackhelicopters.org> Date: Sat, 10 Mar 2001 20:25:34 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010310124249.A87381@blackhelicopters.org> Michael Lucas writes: : Is the Handbook correct, or are unified diffs preferred? I'll be : happy to fix my article and submit a PR to correct the Handbook if : this is the case. diff -c or diff -u is 1000% better than palin diff. That's what is ment by "context" in this context :-). I personally find diff -u easier to read, but there are others that find -c easier. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 19:29:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id CC55237B71A for ; Sat, 10 Mar 2001 19:29:27 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2B3TII23768; Sat, 10 Mar 2001 20:29:18 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103110329.f2B3TII23768@harmony.village.org> To: Jonathan Lemon Subject: Re: if_fxp - the real point Cc: romain@kzsu.stanford.edu, hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 10 Mar 2001 13:08:58 CST." <200103101908.f2AJ8wr76450@prism.flugsvamp.com> References: <200103101908.f2AJ8wr76450@prism.flugsvamp.com> Date: Sat, 10 Mar 2001 20:29:18 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200103101908.f2AJ8wr76450@prism.flugsvamp.com> Jonathan Lemon writes: : You can't find the answers to any of these in the datasheets. The : datasheets may provide a tiny bit of information, and hint at how things : actually operate, but there is not sufficient information to develop a : driver from them. Their older parts (the 82593) had this same problem. You had to have some sort of inside tract to get good information. And even then it was difficult at best. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 19:37: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id B93D837B719 for ; Sat, 10 Mar 2001 19:37:02 -0800 (PST) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f2B3b1210404 for ; Sat, 10 Mar 2001 21:37:02 -0600 (CST) Message-Id: <200103110337.f2B3b1210404@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: hackers@freebsd.org Subject: Re: if_fxp - the real point Date: Sat, 10 Mar 2001 21:37:01 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, maybe I'm missing something... 1. Has anyone tried one of these new Intel parts with BSD/OS? 2. Do any of the people involved with this have source licenses to BSD/OS? I am quite sure BSDi hasn't been swamped with "help, my Intel card isn't working" requests. I'm also quite sure that the source license includes the Intel stuff. Now, that doesn't do *much* more good than the Linux driver... but it might help *some*. If anyone has a specific part number or model information about the new unsupported PHY, I'd be happy to look it up and tell you what, if anything, I can find out. I can't send out copies of the source without some kind of formal approval, but I could certainly at least answer questions like "do we have a BSD-flavored driver that works with this". -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 19:45:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 75F6C37B719 for ; Sat, 10 Mar 2001 19:45:36 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2B3m3N03479; Sat, 10 Mar 2001 19:48:03 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103110348.f2B3m3N03479@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: seebs@plethora.net (Peter Seebach) Cc: hackers@freebsd.org Subject: Re: if_fxp - the real point In-reply-to: Your message of "Sat, 10 Mar 2001 21:37:01 CST." <200103110337.f2B3b1210404@guild.plethora.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Mar 2001 19:48:02 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Okay, maybe I'm missing something... > > 1. Has anyone tried one of these new Intel parts with BSD/OS? > 2. Do any of the people involved with this have source licenses to BSD/OS? > > I am quite sure BSDi hasn't been swamped with "help, my Intel card isn't > working" requests. I'm also quite sure that the source license includes the > Intel stuff. Now, that doesn't do *much* more good than the Linux driver... > but it might help *some*. Actually, I don't think it does. I spoke with Jeert about this a while back; his attitude isn't much better than Intel's on this topic. > If anyone has a specific part number or model information about the new > unsupported PHY, I'd be happy to look it up and tell you what, if anything, > I can find out. I can't send out copies of the source without some kind > of formal approval, but I could certainly at least answer questions like > "do we have a BSD-flavored driver that works with this". The FreeBSD project already has a BSD/OS source distribution, however the required information is NOT THERE. Ok? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 19:56:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id 6E40937B719 for ; Sat, 10 Mar 2001 19:56:38 -0800 (PST) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f2B3ub210567 for ; Sat, 10 Mar 2001 21:56:37 -0600 (CST) Message-Id: <200103110356.f2B3ub210567@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: hackers@freebsd.org Subject: Re: if_fxp - the real point In-reply-to: Your message of "Sat, 10 Mar 2001 19:48:02 PST." <200103110348.f2B3m3N03479@mass.dis.org> Date: Sat, 10 Mar 2001 21:56:37 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200103110348.f2B3m3N03479@mass.dis.org>, Mike Smith writes: >The FreeBSD project already has a BSD/OS source distribution, however the >required information is NOT THERE. Ok? Okay. I just figured I'd ask, since it's information I have. Hmm. Out of idle curiousity, has the NIH syndrome died down enough that it might hypothetically be possible for the three major *BSD camps to cooperate on this kind of thing? Form an organization the purpose of which is to get access to driver docs *for all three systems*? An organization which can claim to represent 2N or 3N users, instead of N, *might* be able to get people to listen more closely... Especially if it maintained a page describing hardware and vendor relations, and a lot of people got in the habit of linking to it. Does Intel care if there's a page saying "Intel has refused to provide specs, so we are obliged to recommend Frobozz Magic Ethernet instead"? Probably not, but they *might*. More than they care about mutterings on mailing lists, certainly. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 20: 1:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id B506E37B718 for ; Sat, 10 Mar 2001 20:01:39 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2B44HN03671; Sat, 10 Mar 2001 20:04:17 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103110404.f2B44HN03671@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: seebs@plethora.net (Peter Seebach) Cc: hackers@freebsd.org Subject: Re: if_fxp - the real point In-reply-to: Your message of "Sat, 10 Mar 2001 21:56:37 CST." <200103110356.f2B3ub210567@guild.plethora.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Mar 2001 20:04:17 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Out of idle curiousity, has the NIH syndrome died down enough that it might > hypothetically be possible for the three major *BSD camps to cooperate on this > kind of thing? No, I'm afraid it hasn't. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 21:23:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pebkac.owp.csus.edu (pebkac.owp.csus.edu [130.86.232.245]) by hub.freebsd.org (Postfix) with ESMTP id 2D01737B718 for ; Sat, 10 Mar 2001 21:23:51 -0800 (PST) (envelope-from joseph.scott@owp.csus.edu) Received: from localhost (scottj@localhost) by pebkac.owp.csus.edu (8.9.3/8.9.3) with ESMTP id VAA97091; Sat, 10 Mar 2001 21:23:40 -0800 (PST) (envelope-from joseph.scott@owp.csus.edu) Date: Sat, 10 Mar 2001 21:23:40 -0800 (PST) From: Joseph Scott X-Sender: scottj@pebkac.owp.csus.edu To: Michael Lucas Cc: hackers@FreeBSD.ORG Subject: Re: context or unified diffs in PRs? In-Reply-To: <20010310124249.A87381@blackhelicopters.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 Sat, 10 Mar 2001, Michael Lucas wrote: > Hello, > > I'm afraid I might be walking up to a bikeshed with a can of paint > here, but the flood of email in the last twenty-four hours has > convinced me to ask. > > In an article O'Reilly published yesterday, I stated (per the > Handbook) that context diffs were the correct way to submit patches > with PRs. I've had several people claim that unified diffs are the > way to go, and that the handbook is just wrong. > > Is the Handbook correct, or are unified diffs preferred? I'll be > happy to fix my article and submit a PR to correct the Handbook if > this is the case. When I read your article I thought that perhaps that was a mistake, but quickly started looking at something else and forgot about it. I'd always thought unified was better, and felt justified after reading this section in the FreeBSD Porter's Handbook http://www.freebsd.org/docs/en/books/porters-handbook/port-upgrading.html third paragraph, where the example diff they use is diff -ruN for upgrading a port. -Joseph To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 21:36:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.prod.itd.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id DEAA037B718 for ; Sat, 10 Mar 2001 21:36:07 -0800 (PST) (envelope-from fmela0@sm.socccd.cc.ca.us) Received: from sm.socccd.cc.ca.us (pool0290.cvx14-bradley.dialup.earthlink.net [209.179.39.35]) by gull.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id VAA28429; Sat, 10 Mar 2001 21:35:56 -0800 (PST) Message-ID: <3AAB0F18.E93A0506@sm.socccd.cc.ca.us> Date: Sat, 10 Mar 2001 21:37:28 -0800 From: Farooq Mela Reply-To: fmela0@sm.socccd.cc.ca.us X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jordan DeLong Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel area libmish stuff References: <20010309175233.A6880@cx420564-b.tucson1.az.home.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 DeLong wrote: > I was thinking of just getting a sintable array and making a few simple > functions, so the whole of libm doesn't need to be statically linked into the > module (from my understanding, once loaded, this module wont ever get paged out, > and thus it'd be _bad_ for it to be big). Well, you can't do any FP stuff inside the kernel, as stated by others. But what you can do is use the fact that: sin(x) = x - (x^3)/3! + (x^5)/5! - (x^7)/7! ... and things like sin(-x) = -sin(x), etc, and integer arithmetic. You'd have to multiply X by a suitably large "base" value so that you dont have underflow, and compute it that way, and then divide the final answer by the base. Throughout your program, you'd have to change all your floating point arithmetic to use this sort of arithmetic - first multiplying by the base, doing all calculations, and dividing by the base once you arrive at the _final_ answer. A real pain, at best. The rest of the transcendental trig's can be built using identities like cos(x) = sin(x + pi/2), tan(x) = sin(x)/cos(x), etc. HTH -- farooq "Life's not fair, but the root password helps." -BOFH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 10 21:45:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id A8D8C37B719 for ; Sat, 10 Mar 2001 21:45:45 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14byfx-0000Qo-00; Sat, 10 Mar 2001 22:45:53 -0700 Message-ID: <3AAB1111.9BD24457@softweyr.com> Date: Sat, 10 Mar 2001 22:45:53 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Tim Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp - the real point References: <20010310143739.A3867@futuresouth.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tim wrote: > > Is there a point of contact at Intel that we could all send e-mail to or > even send a formal letter? I am sure my buying 50 or so boards a year > isn't going to make a dent at Intel's bottom line, but considering how > their stock is doing lately and if we all contribute... Craig Barrett, craig.r.barrett@intel.com. That should get somebody's attention pretty quickly. -- "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