From owner-freebsd-hackers Sun Oct 14 0: 5:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id EAC7037B401 for ; Sun, 14 Oct 2001 00:05:08 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9E74va36715; Sun, 14 Oct 2001 09:04:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bsdguru@aol.com Cc: hackers@FreeBSD.ORG Subject: Re: 4-port T1 PCI card with integrated csu/dsu In-Reply-To: Your message of "Sat, 13 Oct 2001 19:33:08 EDT." Date: Sun, 14 Oct 2001 09:04:57 +0200 Message-ID: <36713.1003043097@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Bsdguru@aol.com writes: >In a message dated 10/13/01 3:15:31 PM Eastern Daylight Time, >phk@critter.freebsd.dk writes: > >> >> etinc is not recommendable. >> >> >> > >> >Everyone knows that PHK has a grudge against etinc. How childish. >> >> No, I don't have a grudge against Dennis or Etinc, I merely point >> out that somebody who has caused so much grief in our mailing lists >> without ever actually submitting one single diff to us is not >> a (re)commendable supplier. > >I dont know about you, but I base my recommendations on the ability of the >product to help the person thats asking, not the number of lines of code >they've contributed. I would never trust my data to a closed-source product from somebody behaving like Dennis. You're of course just as free to decide what you do. >I dont see how driving away commercial vendors with such a ridiculous >attitude benefits the FreeBSD community. Very unprofessional. Belive me, I have worked hard to drive Dennis 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 Sun Oct 14 0:44:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 7397D37B401 for ; Sun, 14 Oct 2001 00:44:46 -0700 (PDT) Received: from mindspring.com (dialup-209.247.143.225.Dial1.SanJose1.Level3.net [209.247.143.225]) by falcon.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f9E7i6403300; Sun, 14 Oct 2001 00:44:06 -0700 (PDT) Message-ID: <3BC94279.F9F166BE@mindspring.com> Date: Sun, 14 Oct 2001 00:44:57 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matt Dillon Cc: Valentin Nechayev , hackers@FreeBSD.ORG Subject: Re: sin_zero & bind problems References: <20011013135842.A415@iv.nn.kiev.ua> <200110131717.f9DHHLR43887@earth.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matt Dillon wrote: > Nobody in their right mind uses a struct sockaddr_in or any other > struct sock* type of structure without zeroing it first. I suppose > we can document that in the man pages, but we certainly should not go > hacking up the kernel code to work around bad programmers. It is common practice in Linux to ignore those portions in the connect/bind that aren't applicable. There is a huge amount of code written for Linux which just uses auto variables, jamming only the applicable data into the struct, before passing it. Arguably, FreeBSD should ignore the data not applicable to the bind, but this would mean pretending it was zero in the kernel. A number of other UNIX implementations also puke in this Linux-ism, so it's a good idea to require the zeroing. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 0:51: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 563CC37B401; Sun, 14 Oct 2001 00:51:00 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.3) id f9E7oZi05487; Sun, 14 Oct 2001 09:50:35 +0200 (CEST) (envelope-from sos) From: Søren Schmidt Message-Id: <200110140750.f9E7oZi05487@freebsd.dk> Subject: Re: Severe I/O Problems In-Reply-To: To: mjacob@feral.com Date: Sun, 14 Oct 2001 09:50:34 +0200 (CEST) Cc: Jordan Hubbard , jrossiter@symantec.com, sos@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Matthew Jacob wrote: > Just following up myself on this... with a drive on my PC164 Alpha, the > realtime difference between two different checkouts of cvs src is interesting: > > ------------- > > Script started on Sat Oct 13 10:07:07 2001 > farrago.feral.com > # this is with wc off > farrago.feral.com > /usr/bin/time cvs -q -d /home/ncvs co src > LOG > 2478.99 real 201.48 user 1046.87 sys > farrago.feral.com > exit > exit > > Script done on Sat Oct 13 10:55:36 2001 > Script started on Sat Oct 13 11:04:06 2001 > farrago.feral.com > # this is with wc on > farrago.feral.com > /usr/bin/time cvs -q -d /home/ncvs co src > LOG > 2866.82 real 199.92 user 988.24 sys > farrago.feral.com > exit > exit > > Script done on Sat Oct 13 11:57:51 2001 > ------------- > > All parameters were not totally lab controlled, but pretty close. I'd call it > significant enough that I'll leave WC off for this machine. Well I tried something semilar here, CVS tree on one disk, then newfs and cvs co src on another (both DTLA's on via686b if that matters) to keep things as equal as possible, singleuser mode of cause... -SU: softupdates -wc writecache enabled -tags tagged queing enabled res: 33.973u 19.425s 27:27.88 3.2% 583+7328k 47219+160828io 37pf+0w res-SU: 33.552u 16.235s 9:53.49 8.3% 586+7244k 47180+864io 6pf+0w res-wc: 32.959u 20.104s 3:38.23 24.3% 586+7317k 47232+160828io 37pf+0w res-wc-SU: 33.343u 16.909s 2:52.81 29.0% 585+7269k 47184+863io 6pf+0w res-wc-tags: 33.891u 29.705s 3:40.62 28.8% 587+7595k 47225+160548io 20pf+0w res-wc-tags-SU: 33.946u 20.759s 2:48.97 32.3% 578+7234k 47183+863io 5pf+0w That behaves more or less as I would expect... It is worth nothing that there is close to an order of magnitude in difference from the slowest to the fastest, and that WC is the single option that can make that difference on its own... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 0:54:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 582F237B409 for ; Sun, 14 Oct 2001 00:54:07 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id ABF2C16B13 for ; Sun, 14 Oct 2001 09:54:04 +0200 (CEST) Received: from IBM-HIRXKN66F0W.Go2France.com [66.64.14.18] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id A7B0B920084; Sun, 14 Oct 2001 10:07:12 +0200 Message-Id: <5.1.0.14.0.20011014024215.060624d0@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 14 Oct 2001 02:53:21 -0500 To: FReebsd-hackers@freebsd.org From: Len Conrad Subject: Re: 4-port T1 PCI card with integrated csu/dsu In-Reply-To: <36713.1003043097@critter.freebsd.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Back on the original topic, anybody know the retail for this card: http://www.sbei.net/wanadapt1t1e1.htm The WANic 654 4-port meets the spec at $3200, but no FreeBSD support there. An eBay 3640 is looking better all time. :((( Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 1:10:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id B7F4D37B40A for ; Sun, 14 Oct 2001 01:10:31 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9E8AHa37366; Sun, 14 Oct 2001 10:10:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Len Conrad Cc: FReebsd-hackers@FreeBSD.ORG Subject: Re: 4-port T1 PCI card with integrated csu/dsu In-Reply-To: Your message of "Sun, 14 Oct 2001 02:53:21 CDT." <5.1.0.14.0.20011014024215.060624d0@mail.Go2France.com> Date: Sun, 14 Oct 2001 10:10:17 +0200 Message-ID: <37364.1003047017@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <5.1.0.14.0.20011014024215.060624d0@mail.Go2France.com>, Len Conrad writes: >Back on the original topic, anybody know the retail for this card: > >http://www.sbei.net/wanadapt1t1e1.htm Why don't you call them ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 1:18:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id D2FF037B406 for ; Sun, 14 Oct 2001 01:18:15 -0700 (PDT) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id LGY23303; Sun, 14 Oct 2001 11:18:02 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.11.6/8.11.6) id f9E8GOP05252; Sun, 14 Oct 2001 11:16:24 +0300 (EEST) (envelope-from netch) Date: Sun, 14 Oct 2001 11:16:23 +0300 From: Valentin Nechayev To: Matt Dillon Cc: hackers@FreeBSD.ORG Subject: Re: sin_zero & bind problems Message-ID: <20011014111623.A3718@iv.nn.kiev.ua> References: <20011013135842.A415@iv.nn.kiev.ua> <200110131717.f9DHHLR43887@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200110131717.f9DHHLR43887@earth.backplane.com>; from dillon@earth.backplane.com on Sat, Oct 13, 2001 at 10:17:21AM -0700 X-42: On Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sat, Oct 13, 2001 at 10:17:21, dillon (Matt Dillon) wrote about "Re: sin_zero & bind problems": Matt, excuse me please... Why you send insults to programmers which were as unhappy as to put feet to your BSD-specific rake? They carefully read all documentation and examples (you cannot prove that they didn't do it). Their programs works correct on another platforms - on Linux and even on Win32. And only BSD clones contain such undocumented diversion. One should realize that new applications mainstream is now generated mainly on Linux, which doesn't contain such "feature". All examples I noted were developed on Linux and than ported to FreeBSD. Do you want to generate wide bunch of programmers who don't ever want to deal with system which such hidden stones? Well, let's explore FreeBSD sources. I explored RELENG_4_4 date=2001.10.06.00.00.00 tree for sockaddr_in usage as automatic variable. The very first of found - bin/date/netdate.c - shows use of such structure without prior zero-filling. (Of course it works because wants INADDR_ANY.) I see no reason to explore further.;( > Nobody in their right mind uses a struct sockaddr_in or any other > struct sock* type of structure without zeroing it first. I suppose > we can document that in the man pages, but we certainly should not go > hacking up the kernel code to work around bad programmers. You didn't (and can't) prove that they are bad programmers. You didn't (and can't) prove that programmer's "right mind" must a priori prompt to fill sockaddr* structures with zeros. For any programmer known to me in real life, this knowledge was obtained after intensive "cerebral sex" ((c)local folklore). I don't know another structure which must be filled with zeros without mention in manuals, and rare cases with properly documented requirement. Yoy didn't (and can't IMO) show that there are some real usage of sin_zero, except nonsenseable garbage area. Whatever reason was to create reserved field, it is obsoleted now. I cannot see any sense in your message, except bad-formed emotions.:( Is it so difficult to add one (!) line to kernel source and avoid this tiresome teeth-ache forever? /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 1:20:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postoffice.aims.com.au (eth0.lnk.aims.com.au [203.31.73.253]) by hub.freebsd.org (Postfix) with ESMTP id 2414337B40B for ; Sun, 14 Oct 2001 01:20:29 -0700 (PDT) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2]) by postoffice.aims.com.au with ESMTP id f9E8KQZ62235 for ; Sun, 14 Oct 2001 19:20:26 +1100 (EST) (envelope-from chris@aims.com.au) Received: from ntsts1 by aims.com.au with SMTP (MDaemon.v3.5.3.R) for ; Sun, 14 Oct 2001 19:19:18 +1100 Reply-To: From: "Chris Knight" To: Cc: Subject: RE: 4-port T1 PCI card with integrated csu/dsu Date: Sun, 14 Oct 2001 19:19:16 +1100 Message-ID: <016901c15488$eb2db050$020aa8c0@aims.private> 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 CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <5.1.0.14.0.20011014024215.060624d0@mail.Go2France.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-Return-Path: chris@aims.com.au X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Howdy, About $750USD. The driver's a little rough around the edges, but works OK. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Len Conrad > Sent: Sunday, 14 October 2001 18:53 > To: FReebsd-hackers@FreeBSD.ORG > Subject: Re: 4-port T1 PCI card with integrated csu/dsu > > > Back on the original topic, anybody know the retail for this card: > > http://www.sbei.net/wanadapt1t1e1.htm > > The WANic 654 4-port meets the spec at $3200, but no FreeBSD > support there. > > An eBay 3640 is looking better all time. :((( > > Len > > > http://MenAndMice.com/DNS-training > http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K > http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse > mail gateways > > > 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 Oct 14 1:49: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id C057237B403; Sun, 14 Oct 2001 01:49:02 -0700 (PDT) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f9E8mnH04937; Sun, 14 Oct 2001 01:48:50 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sun, 14 Oct 2001 01:48:46 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: Jordan Hubbard , jrossiter@symantec.com, sos@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Severe I/O Problems In-Reply-To: <200110140750.f9E7oZi05487@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > All parameters were not totally lab controlled, but pretty close. I'd call it > > significant enough that I'll leave WC off for this machine. > > Well I tried something semilar here, CVS tree on one disk, then newfs and > cvs co src on another (both DTLA's on via686b if that matters) to keep > things as equal as possible, singleuser mode of cause... > > -SU: softupdates -wc writecache enabled -tags tagged queing enabled > > res: 33.973u 19.425s 27:27.88 3.2% 583+7328k 47219+160828io 37pf+0w > res-SU: 33.552u 16.235s 9:53.49 8.3% 586+7244k 47180+864io 6pf+0w > res-wc: 32.959u 20.104s 3:38.23 24.3% 586+7317k 47232+160828io 37pf+0w > res-wc-SU: 33.343u 16.909s 2:52.81 29.0% 585+7269k 47184+863io 6pf+0w > res-wc-tags: 33.891u 29.705s 3:40.62 28.8% 587+7595k 47225+160548io 20pf+0w > res-wc-tags-SU: 33.946u 20.759s 2:48.97 32.3% 578+7234k 47183+863io 5pf+0w > > That behaves more or less as I would expect... > > It is worth nothing that there is close to an order of magnitude in > difference from the slowest to the fastest, and that WC is the single > option that can make that difference on its own... > I don't doubt this. I just would suggest that there is such a spread of h/w and configurations that sometimes turning on WC is fantastic, and sometimes not so fantastic. Now- before y'all get huffy about this and suggest that I don't have the right h/w- I'll agree- but when people run into performance issues this is certainly one thing to check. D'ya think you could come up with a little tester program that could predict whether WC would make sense for a particular h/w configuration or not? That'd be darned usefull. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 1:58: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id 518FC37B401 for ; Sun, 14 Oct 2001 01:57:57 -0700 (PDT) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id LWF24436; Sun, 14 Oct 2001 11:57:43 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.11.6/8.11.6) id f9E8kvi06796; Sun, 14 Oct 2001 11:46:57 +0300 (EEST) (envelope-from netch) Date: Sun, 14 Oct 2001 11:46:57 +0300 From: Valentin Nechayev To: "E.B. Dreger" Cc: hackers@FreeBSD.ORG Subject: Re: AIO issues... or not? Message-ID: <20011014114657.C3718@iv.nn.kiev.ua> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from eddy+public+spam@noc.everquick.net on Fri, Oct 05, 2001 at 02:19:58PM +0000 X-42: On Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Fri, Oct 05, 2001 at 14:19:58, eddy+public+spam (E.B. Dreger) wrote about "AIO issues... or not?": > When using aio_* calls, I received ENOSYS. I grepped LINT, and > found that I'd forgotten to "OPTIONS VFS_AIO". Simple enough. > > However, there's a rather ominous and non-descriptive warning > present: "There are numerous stability issues in the current aio > code that make it unsuitable for inclusion on shell boxes." Can > anyone please elaborate? Is this admonition outdated? At least, privilege to use AIO can be simply bound to some group ID. I use it on our http proxy server together with patch for squid to use kernel AIO in aufs code. --- vfs_aio.c.0 Sat Sep 1 13:33:37 2001 +++ vfs_aio.c Sat Sep 8 23:03:58 2001 @@ -97,7 +97,12 @@ static int max_aio_procs = MAX_AIO_PROCS; static int num_aio_procs = 0; static int target_aio_procs = TARGET_AIO_PROCS; +/* VFS_AIO_DISABLE_AT_STARTUP is kernel compiling option */ +#ifdef VFS_AIO_DISABLE_AT_STARTUP +static int max_queue_count = 0; +#else static int max_queue_count = MAX_AIO_QUEUE; +#endif static int num_queue_count = 0; static int num_buf_aio = 0; static int num_aio_resv_start = 0; @@ -108,6 +113,16 @@ static int max_aio_queue_per_proc = MAX_AIO_QUEUE_PER_PROC; static int max_buf_aio = MAX_BUF_AIO; +/* + * aio_group sets group which is allowed to use AIO. + * Two special values: + * -1 - don't check group, allow for all + * -2 - no group is allowed + * Root's process are allowed always to use AIO in this checking. + * But they may fail if any limit above is set to 0. + */ +static long aio_group = 0; /* allow only for group wheel by default */ + SYSCTL_NODE(_vfs, OID_AUTO, aio, CTLFLAG_RW, 0, "AIO mgmt"); SYSCTL_INT(_vfs_aio, OID_AUTO, max_aio_per_proc, @@ -143,6 +158,12 @@ SYSCTL_INT(_vfs_aio, OID_AUTO, aiod_timeout, CTLFLAG_RW, &aiod_timeout, 0, ""); +SYSCTL_LONG(_vfs_aio, OID_AUTO, aio_group, + CTLFLAG_RW, &aio_group, 0, ""); + +SYSCTL_LONG(_vfs_aio, OID_AUTO, jobrefid, + CTLFLAG_RD, &jobrefid, 0, ""); + /* * AIO process info */ @@ -1453,19 +1465,55 @@ } /* + * Check permissions, global and process, to use AIO + * Called from aio_aqueue() and lio_listio() + */ +static int +aio_allowed(struct proc *p) +{ + /* Hard bounce if aio is disabled in sysctl. */ + if (max_queue_count <= 0 || max_aio_procs <= 0 || + max_aio_per_proc <= 0) + return EPROCLIM; + if (num_queue_count >= max_queue_count) + return EAGAIN; + + /* Check permissions. Allow only root or specified group member. */ + /* XXX lock/unlock process? (for FreeBSD5) */ + if (suser_xxx(0, p, PRISON_ROOT) && aio_group != -1) { + int ig; + if (aio_group == -2) + return EPERM; + for (ig = 0; ig < p->p_ucred->cr_ngroups; ig++) { + if (p->p_ucred->cr_groups[ig] == (gid_t)aio_group) + return 0; + } + return EPERM; + } + return 0; +} + +/* * This routine queues an AIO request, checking for quotas. */ static int aio_aqueue(struct proc *p, struct aiocb *job, int type) { struct kaioinfo *ki; + int error; + + /* + * Forward this global check before aio_init_aioinfo(). + * Don't waste resources if it is not allowed. + * max_queue_count is sysctl vfs.aio.max_aio_queue. + */ + error = aio_allowed(p); + if (error) + return error; if (p->p_aioinfo == NULL) aio_init_aioinfo(p); - if (num_queue_count >= max_queue_count) - return EAGAIN; - ki = p->p_aioinfo; if (ki->kaio_queue_count >= ki->kaio_qallowed_count) return EAGAIN; @@ -1921,6 +1978,11 @@ if (nent > AIO_LISTIO_MAX) return EINVAL; + /* Check permissions. */ + error = aio_allowed(p); + if (error) + return error; + if (p->p_aioinfo == NULL) aio_init_aioinfo(p); /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 2:18:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 3CDE137B405; Sun, 14 Oct 2001 02:18:14 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9E9HvT13116; Sun, 14 Oct 2001 02:18:03 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Doug Hass" , , "MurrayTaylor" , , Cc: "Alfred Shippen" Subject: RE: FYI Date: Sun, 14 Oct 2001 02:17:56 -0700 Message-ID: <006001c15491$1c1c6aa0$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG There are other vendors that sell the WanIC than Imagestream. I realize that you see yourself as the only supplier but this isn't true. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Doug Hass >Sent: Friday, October 12, 2001 3:11 PM >To: owner-freebsd-questions@FreeBSD.ORG; Ted Mittelstaedt; MurrayTaylor; >freebsd-hackers@FreeBSD.ORG; freebsd-questions@FreeBSD.ORG >Cc: Alfred Shippen >Subject: Re: FYI > > >I'm providing this to the people whose addresses appear in the original >messages. My apologies if this gets cross-posted or sent multiple times >to the same place. As I mention below, the WANic 400 series cards and all >of the RISCom/N2 series cards are now End Of Life, and only available in >special quantity builds. > >If anyone reading this message needs further information, please contact >me directly and I can go into further depth about the EOL cards mentioned >below and their replacements in the SBS line. > >Regards, > >Doug > >----- > >Doug Hass >ImageStream Internet Solutions >dhass@imagestream.com >http://www.imagestream.com >Office: 1-219-935-8484 >Fax: 1-219-935-8488 > > >On Fri, 12 Oct 2001, Doug Hass wrote: > >> The WANic 400 series is definitely EOL. The cards are available in >> quantities of 100+ only by special order. The RISCom/N2 series cards are >> also EOL. >> >> This is a recent decision--it went into effect as of September 21st. >> Closeout quantities have already been sold to other companies, so the >> cards are only available by special order. >> >> The WANic 521/522 have replaced these cards, and should be used instead. >> There are no drivers for FreeBSD, however. >> >> Doug >> >> >> >> On Sat, 13 Oct 2001, Alfred Shippen wrote: >> >> > This guy is local to you and is under the misapprehension that >the Risc/400 >> > series is not a discontinued item. I dont know if you want to >follow them up >> > or not. My customer (Bytecraft) is fine by this and has passed on the >> > comments to me. >> > >> > Cheers >> > >> > >> > >> > > >> > > ----- Original Message ----- >> > > From: "Ted Mittelstaedt" >> > > To: "MurrayTaylor" ; >> > > ; >> > > Sent: Friday, October 12, 2001 3:07 PM >> > > Subject: RE: Imagestream WanIC-520 interface cards >> > > >> > > >> > > > The WANic 5xx's use an incompatible chipset and the driver will not >> > > > work with them. >> > > > >> > > > I thnk your supplier is feeding you a line of bullshit. SBS >> > > Communications >> > > > has posted no plans whatsover to discontinue or change the >WANic line. >> > > > They are fully aware that the 405's have open source drivers and are >> > > > furthermore used in embedded systems too. >> > > > >> > > > The WANic 5xx series of cards sell for more money and so >naturally your >> > > > supplier is most interested in maximizing his margin and >would prefer to >> > > > push you into a more expensive card. >> > > > >> > > > With the increase in CPU power all of the go-fast hardware on the >> > > higher-level >> > > > cards is less important. >> > > > >> > > > Consider that the Hitachi controller chip used on the WANic >405 is the >> > > > SAME chip that Cisco uses in it's 25xx series of routers, >and the Cisco >> > > > 2501 is the most used router in the world and has the most installed >> > > > units. >> > > > >> > > > SBS Communications is STILL selling the RISCom series of >cards which is >> > > > the predecessor to the WANic, uses the same controller, these are ISA >> > > cards >> > > > that have a design that's over 10 years old. >> > > > >> > > > You tell your supplier that since the 405 is being "phased >out" that he >> > > > should sell you a bunch of them at closeout prices. >> > > > >> > > > Ted Mittelstaedt >> > > tedm@toybox.placo.com >> > > > Author of: The FreeBSD Corporate >Networker's >> > > Guide >> > > > Book website: >> > > http://www.freebsd-corp-net-guide.com >> > > > >> > > > >> > > > >-----Original Message----- >> > > > >From: owner-freebsd-questions@FreeBSD.ORG >> > > > >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of >MurrayTaylor >> > > > >Sent: Thursday, October 11, 2001 4:49 PM >> > > > >To: freebsd-questions@FreeBSD.ORG; freebsd-hackers@FreeBSD.ORG >> > > > >Subject: Imagestream WanIC-520 interface cards >> > > > > >> > > > > >> > > > >As the WanIC-405 is being phased out (according to my supplier >> > > > >down under here in OZ), has any development / testing been >done on the >> > > > >apparent replacement, the WanIC-521 (522, 524 ... ) range >> > > > > >> > > > >I am especially interested in its compatibility with its predecessor >> > > > >which I am using very successfully for frame relay under Netgraph. >> > > > > >> > > > >I'm trying to get compatability info from the supplier here, >> > > > >but we are a long way down the food chain ;-( >> > > > > >> > > > >Tia >> > > > > >> > > > >Murray Taylor >> > > > >Bytecraft Systems Pty Ltd >> > > > >murraytaylor@bytecraftsystems.com >> > > > > >> > > > > >> > > > > >> > > > > >> > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >> > > > >with "unsubscribe freebsd-questions" in the body of the message >> > > > > >> > > > >> > > > >> > >> >> > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" 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 Oct 14 2:35:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id D848D37B40E; Sun, 14 Oct 2001 02:35:06 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.3) id f9E9Z2g25270; Sun, 14 Oct 2001 11:35:02 +0200 (CEST) (envelope-from sos) From: Søren Schmidt Message-Id: <200110140935.f9E9Z2g25270@freebsd.dk> Subject: Re: Severe I/O Problems In-Reply-To: To: mjacob@feral.com Date: Sun, 14 Oct 2001 11:35:02 +0200 (CEST) Cc: Jordan Hubbard , jrossiter@symantec.com, sos@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Matthew Jacob wrote: > I don't doubt this. I just would suggest that there is such a spread of h/w > and configurations that sometimes turning on WC is fantastic, and sometimes > not so fantastic. Hmm, I know of no drives that shuld perform worse with WC on, but your case shows there could be such problems... > D'ya think you could come up with a little tester program that could predict > whether WC would make sense for a particular h/w configuration or not? That'd > be darned usefull. Hmm, that should be pretty easy, but I also have to integrate some of my other stuff so that WC can be changed *safely* with atacontrol... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 3: 7:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.morning.ru (ns.morning.ru [195.161.98.5]) by hub.freebsd.org (Postfix) with ESMTP id 8BC6E37B409 for ; Sun, 14 Oct 2001 03:07:06 -0700 (PDT) Received: (from root@localhost) by ns.morning.ru (8.11.5/8.11.5) id f9EA6WO76429; Sun, 14 Oct 2001 18:06:32 +0800 (KRAST) Date: Sun, 14 Oct 2001 18:06:32 +0800 From: Igor M Podlesny To: "Daniel C. Sobral" Cc: Vadim Vygonets , freebsd-hackers@FreeBSD.ORG Subject: Re: loader.conf conditional assignment Message-ID: <20011014180632.A76030@ns.morning.ru> References: <20011013174339.A21230@cs.huji.ac.il> <3BC86AF9.BB1CF2E8@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BC86AF9.BB1CF2E8@newsguy.com> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Oct 13, 2001 at 01:25:29PM -0300, Daniel C. Sobral wrote: > Vadim Vygonets wrote: > > > > We are working on integration of network-booted FreeBSD system to > > our envoronment. Naturally, different machines need different > > kernels, so we pass the kernel paramater in DHCP response. > > However, it gets overwritten in /boot/defaults/loader.conf. We > > decided that commenting out the assignment of 'kernel' and > > 'kernel_options' is not what we want, because we want both to use > > the default value and to be able to override it via DHCP. > > > > After taking some time to learn Forth (interesting language, I > > must say) and a false start (involving saving environment > > variables (names and values) in a linked list and restoring them > > after the assignment), I decided to use the Makefile syntax of ?= > > to set an environment variable if it's not set yet, so it will be > > possible to say: > > > > kernel?="/kernel" > > > > In this case, if kernel is set via DHCP, the value is not > > changed, but if it's not, it becomes "/kernel". Attached is the > > patch for /boot/support.4th against the version in FreeBSD 4.4. > > Loader.conf's syntax was designed to be such that the files could be > processed by sh(1). I rather prefer to keep faithful to that by using > the shell expansions tricks sh(1) has. OTOH, that wouldn't be a trivial > task to undertake, and I don't have time to do it. Add to that, being > able to sh-process loader.conf files is of dubious usefulness. So I do > not object to such a change, as long as more people weight in first on > this matter. Is there any chance off implementing syntax like kernel=${kernel:-/kernel} which is obviously sh-compilant? > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > capo@the.secret.bsdconspiracy.net > > wow regex humor... I'm a geek > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Igor M Podlesny Morning Network hostmaster http://good.morning.ru phone: +7 3912 296962 mailto:hostmaster@morning.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 8:29:25 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 088C637B40C; Sun, 14 Oct 2001 08:29:19 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f9EFTGB82295; Sun, 14 Oct 2001 11:29:16 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 14 Oct 2001 11:29:16 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: hackers@FreeBSD.org, developers@FreeBSD.org Subject: Request for submissions: FreeBSD Monthly Development Status Report Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It's that time again--despite delays and data loss, I'm now ready to start accepting submissions for the September, 2001 FreeBSD Monthly Status Report. As with previous months, please submit reports by e-mail to robert+freebsd.monthly@cyrus.watson.org. Reports should be submitted by October 19, 2001, and cover activities from September 7 through October 19. Reports may be associated with any aspect of the FreeBSD Project, including but not limited to basic system development, merging activities for the -STABLE branch, documentation, advocacy, third party software development, user group meetings, and conference activities. Each report should consist of one paragraph of status information, and in the event that a particular project has not had a status report submitted before, an additional paragraph can be included introducing the project. When submitting reports, please attempt to coordinate submissions so that only one report is submitted per project, except in the case of large projects where reports should cover independent and non-overlapping status information. Reports should contain a project name (preferably the same as previous submissions for the project), contact address(es), optional URL for the project. Submissions should be formatted as follows: Project: (name) URL: (name) Contact: name1 , name2 And the text goes here, uniformly indented two spaces, and wrapped before the 78th column. For future reports, we will also support SGML submissions using a style sheet developed by Nik Clayton. Thanks, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 9:33:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pelissero.org (dyn35-41.sftm-212-159.plus.net [212.159.41.35]) by hub.freebsd.org (Postfix) with ESMTP id 7608B37B40F for ; Sun, 14 Oct 2001 09:32:56 -0700 (PDT) Received: (from wcp@localhost) by pelissero.org (8.11.6/8.9.3) id f9EGWfI04327; Sun, 14 Oct 2001 17:32:41 +0100 (BST) (envelope-from wcp) From: "Walter C. Pelissero" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15305.48681.337589.764014@hyde.lpds.sublink.org> Date: Sun, 14 Oct 2001 17:32:41 +0100 To: hackers@freebsd.org Subject: apmd fixes X-Mailer: VM 6.92 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: walter@pelissero.org X-Attribution: WP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here are a couple of patches to apmd (as of FreeBSD 4.4-STABLE) to fix a bug and add a feature necessary on my Vaio PCG-XG9. The fix is to handle properly termination signals (currently ignored). The feature is the -s option that lets you fake POWERSTATECHANGE when the BIOS doesn't report it. This enables you to do fancy things like reducing the LCD backlight brightness when you unplug the power supply. Something like this in apmd.conf: apm_event POWERSTATECHANGE { exec "/bin/sh /usr/local/bin/my-preferred-power-state-change-script"; } Here is the patch: --- /usr/home/wcp/tmp/apmd/apmd.c Fri Oct 12 20:22:34 2001 +++ /usr/src/usr.sbin/apmd/apmd.c Sat Oct 13 14:58:35 2001 @@ -55,7 +55,7 @@ extern int yyparse(void); int debug_level = 0; -int verbose = 0; +int verbose = 0, soft_power_state_change = 0; const char *apmd_configfile = APMD_CONFIGFILE; const char *apmd_pidfile = APMD_PIDFILE; int apmctl_fd = -1, apmnorm_fd = -1; @@ -464,7 +464,6 @@ int proc_signal(int fd) { - int rc = -1; int sig; while (read(fd, &sig, sizeof sig) == sizeof sig) { @@ -476,8 +475,7 @@ break; case SIGTERM: syslog(LOG_NOTICE, "going down on signal %d", sig); - rc = 1; - goto out; + return -1; case SIGCHLD: wait_child(); break; @@ -486,9 +484,7 @@ break; } } - rc = 0; - out: - return rc; + return 0; } void proc_apmevent(int fd) @@ -548,6 +544,8 @@ * the event-caught state. */ if (last_state != AC_POWER_STATE) { + if (soft_power_state_change && fork() == 0) + exit(exec_event_cmd(&events[PMEV_POWERSTATECHANGE])); last_state = AC_POWER_STATE; for (p = battery_watch_list ; p!=NULL ; p = p -> next) p->done = 0; @@ -642,7 +640,7 @@ char *prog; int logopt = LOG_NDELAY | LOG_PID; - while ((ch = getopt(ac, av, "df:v")) != EOF) { + while ((ch = getopt(ac, av, "df:vs")) != EOF) { switch (ch) { case 'd': daemonize = 0; @@ -653,6 +651,9 @@ break; case 'v': verbose = 1; + break; + case 's': + soft_power_state_change = 1; break; default: (void) err(1, "unknown option `%c'", ch); -- walter pelissero http://www.pelissero.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 9:59:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-d07.mx.aol.com (imo-d07.mx.aol.com [205.188.157.39]) by hub.freebsd.org (Postfix) with ESMTP id 3CD2E37B40A for ; Sun, 14 Oct 2001 09:59:08 -0700 (PDT) Received: from Bsdguru@aol.com by imo-d07.mx.aol.com (mail_out_v31_r1.8.) id n.11f.5a43fcd (3968) for ; Sun, 14 Oct 2001 12:58:55 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <11f.5a43fcd.28fb1e4e@aol.com> Date: Sun, 14 Oct 2001 12:58:54 EDT Subject: Re: Imagestream WanIC-520 interface cards To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 138 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 10/13/01 9:33:53 PM Eastern Daylight Time, dillon@earth.backplane.com writes: > Hmm. Well, as a person who ran gated at BEST, has hacked on gated on > same, had to deal with BSDI and FreeBSD route table bugs, tracked down > OSPF bugs for a friend running gated, and otherwise spent hundreds of > hours (at least!) keeping boxes running gated operational... well, I'll > take the Cisco any day thank you very much! > > If you are a small ISP and you have enough money to pay for two T1's, > you have enough money to buy a used router that can do BGP for you. > IMHO. > > -Matt > Thats pretty lame Matt. sort of like saying unix sucks because of all of the bugs and growing pains over the years. Zebra has come a long way, and its as easy to configure as a cisco. Your problems with gated and BSDI have more to do with those organizations than anything else, plus it is stuck with an ill conceived interface. Lets face it, if cisco didnt tell you what to type into your config file almost noone would be able to get them to work either. B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 10: 5:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from newsguy.com (smtp.newsguy.com [209.155.56.71]) by hub.freebsd.org (Postfix) with ESMTP id 39D6C37B407 for ; Sun, 14 Oct 2001 10:05:17 -0700 (PDT) Received: from newsguy.com (ppp232-bsace7002.telebrasilia.net.br [200.181.81.232]) by newsguy.com (8.9.1a/8.9.1) with ESMTP id KAA64874; Sun, 14 Oct 2001 10:04:34 -0700 (PDT) Message-ID: <3BC9C6E5.E1257395@newsguy.com> Date: Sun, 14 Oct 2001 14:09:57 -0300 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en,pt-BR,pt,en-GB,en-US,ja MIME-Version: 1.0 To: Igor M Podlesny Cc: Vadim Vygonets , freebsd-hackers@FreeBSD.ORG Subject: Re: loader.conf conditional assignment References: <20011013174339.A21230@cs.huji.ac.il> <3BC86AF9.BB1CF2E8@newsguy.com> <20011014180632.A76030@ns.morning.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Igor M Podlesny wrote: > > > > kernel?="/kernel" > > Is there any chance off implementing syntax like > > kernel=${kernel:-/kernel} > > which is obviously sh-compilant? Perhaps I was unclear. This is what I would prefer, but I don't have time to do it. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net wow regex humor... I'm a geek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 10:54:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 90C1637B40C; Sun, 14 Oct 2001 10:54:18 -0700 (PDT) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f9EHs3H07231; Sun, 14 Oct 2001 10:54:03 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sun, 14 Oct 2001 10:54:03 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: Jordan Hubbard , jrossiter@symantec.com, sos@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Severe I/O Problems In-Reply-To: <200110140935.f9E9Z2g25270@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 14 Oct 2001, Søren Schmidt wrote: > It seems Matthew Jacob wrote: > > I don't doubt this. I just would suggest that there is such a spread of h/w > > and configurations that sometimes turning on WC is fantastic, and sometimes > > not so fantastic. > > Hmm, I know of no drives that shuld perform worse with WC on, but your > case shows there could be such problems... I doubt it's just this case. > > > D'ya think you could come up with a little tester program that could predict > > whether WC would make sense for a particular h/w configuration or not? That'd > > be darned usefull. > > Hmm, that should be pretty easy, but I also have to integrate some of > my other stuff so that WC can be changed *safely* with atacontrol... This kind of performance tool would be useful for all drives- even SCSI drives. Just a thought. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 12:53:47 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 9AF4C37B405 for ; Sun, 14 Oct 2001 12:53:44 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f9EK4Ze01075; Sun, 14 Oct 2001 13:04:36 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200110142004.f9EK4Ze01075@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Igor M Podlesny Cc: "Daniel C. Sobral" , Vadim Vygonets , freebsd-hackers@FreeBSD.ORG Subject: Re: loader.conf conditional assignment In-reply-to: Your message of "Sun, 14 Oct 2001 18:06:32 +0800." <20011014180632.A76030@ns.morning.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Oct 2001 13:04:35 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Is there any chance off implementing syntax like > > kernel=${kernel:-/kernel} > > which is obviously sh-compilant? I don't much like either of these proposals. My principal objection is that they're trying to solve the wrong problem. The original poster is setting $kernel in the DHCP client code, and then having it overwritten when defaults/loader.conf is parsed. If instead they set $dhcp_kernel, and then put kernel=$dhcp_kernel in their "real" loader.conf the entire problem should go away, and we don't have to extend any of the syntax. If there's a reason why this won't work (for example, I don't think that the code that parses loader.conf uses the script line parser, so it's not going to do variable expansion) then that probably needs to be addressed, since there are a lot of places where this sort of thing would be useful. Just my thoughts, anyway. -- ... 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 Sun Oct 14 13:47: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from MASTER.efreightech.com (w238.z064000243.lax-ca.dsl.cnc.net [64.0.243.238]) by hub.freebsd.org (Postfix) with ESMTP id 8A40F37B40E for ; Sun, 14 Oct 2001 13:46:57 -0700 (PDT) Received: from localhost ([64.225.124.232]) by MASTER.efreightech.com with Microsoft SMTPSVC(5.0.2195.2966); Sun, 14 Oct 2001 13:47:05 -0700 To: freebsd-hackers@FreeBSD.org From: friendz@openxxx.net X-Mailer: Perl+Mail::Sender 0.7.08 by Jan Krynicky Subject: Hello, your friend recommended openxxx.net to you Message-ID: X-OriginalArrivalTime: 14 Oct 2001 20:47:05.0640 (UTC) FILETIME=[6250D280:01C154F1] Date: 14 Oct 2001 13:47:05 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You have been invited to check out this adult site by one of your friends who visited us. click here , our URL is: http://www.openxxx.net/ enjoy, OpenXXX TEAM 2001 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 14:30:19 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 AE0BD37B403 for ; Sun, 14 Oct 2001 14:30:13 -0700 (PDT) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f9ELTeV85571; Sun, 14 Oct 2001 17:29:40 -0400 (EDT) (envelope-from arr@watson.org) Date: Sun, 14 Oct 2001 17:29:39 -0400 (EDT) From: "Andrew R. Reiter" To: "Walter C. Pelissero" Cc: hackers@FreeBSD.ORG Subject: Re: apmd fixes In-Reply-To: <15305.48681.337589.764014@hyde.lpds.sublink.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG While fixing/adding that, might as well go ahead and fix the signal handler enque_signal(). I don't believe using err() in in a signal handler is recommended as it could possible allow for undefined behavior to occur. Andrew On Sun, 14 Oct 2001, Walter C. Pelissero wrote: :Here are a couple of patches to apmd (as of FreeBSD 4.4-STABLE) to fix :a bug and add a feature necessary on my Vaio PCG-XG9. : :The fix is to handle properly termination signals (currently ignored). : :The feature is the -s option that lets you fake POWERSTATECHANGE when :the BIOS doesn't report it. This enables you to do fancy things like :reducing the LCD backlight brightness when you unplug the power :supply. Something like this in apmd.conf: : :apm_event POWERSTATECHANGE { : exec "/bin/sh /usr/local/bin/my-preferred-power-state-change-script"; :} : : :Here is the patch: : :--- /usr/home/wcp/tmp/apmd/apmd.c Fri Oct 12 20:22:34 2001 :+++ /usr/src/usr.sbin/apmd/apmd.c Sat Oct 13 14:58:35 2001 :@@ -55,7 +55,7 @@ : extern int yyparse(void); : : int debug_level = 0; :-int verbose = 0; :+int verbose = 0, soft_power_state_change = 0; : const char *apmd_configfile = APMD_CONFIGFILE; : const char *apmd_pidfile = APMD_PIDFILE; : int apmctl_fd = -1, apmnorm_fd = -1; :@@ -464,7 +464,6 @@ : int : proc_signal(int fd) : { :- int rc = -1; : int sig; : : while (read(fd, &sig, sizeof sig) == sizeof sig) { :@@ -476,8 +475,7 @@ : break; : case SIGTERM: : syslog(LOG_NOTICE, "going down on signal %d", sig); :- rc = 1; :- goto out; :+ return -1; : case SIGCHLD: : wait_child(); : break; :@@ -486,9 +484,7 @@ : break; : } : } :- rc = 0; :- out: :- return rc; :+ return 0; : } : void : proc_apmevent(int fd) :@@ -548,6 +544,8 @@ : * the event-caught state. : */ : if (last_state != AC_POWER_STATE) { :+ if (soft_power_state_change && fork() == 0) :+ exit(exec_event_cmd(&events[PMEV_POWERSTATECHANGE])); : last_state = AC_POWER_STATE; : for (p = battery_watch_list ; p!=NULL ; p = p -> next) : p->done = 0; :@@ -642,7 +640,7 @@ : char *prog; : int logopt = LOG_NDELAY | LOG_PID; : :- while ((ch = getopt(ac, av, "df:v")) != EOF) { :+ while ((ch = getopt(ac, av, "df:vs")) != EOF) { : switch (ch) { : case 'd': : daemonize = 0; :@@ -653,6 +651,9 @@ : break; : case 'v': : verbose = 1; :+ break; :+ case 's': :+ soft_power_state_change = 1; : break; : default: : (void) err(1, "unknown option `%c'", ch); : : :-- :walter pelissero :http://www.pelissero.org : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 15:44:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.noos.fr (zola.noos.net [212.198.2.76]) by hub.freebsd.org (Postfix) with ESMTP id 0B8DD37B408 for ; Sun, 14 Oct 2001 15:44:24 -0700 (PDT) Received: (qmail 4260812 invoked by uid 0); 14 Oct 2001 22:44:22 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.231.187]) (envelope-sender ) by 212.198.2.76 (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 14 Oct 2001 22:44:22 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.6/8.11.6) id f9EMiKA73045; Mon, 15 Oct 2001 00:44:20 +0200 (CEST) (envelope-from root) Message-Id: <200110142244.f9EMiKA73045@gits.dyndns.org> Subject: Re: loader.conf conditional assignment In-Reply-To: <200110142004.f9EK4Ze01075@mass.dis.org> To: Mike Smith Date: Mon, 15 Oct 2001 00:44:19 +0200 (CEST) Cc: Igor M Podlesny , "Daniel C. Sobral" , Vadim Vygonets , freebsd-hackers@freebsd.org Reply-To: clefevre@citeweb.net From: Cyrille Lefevre Organization: ACME X-Face: X-Mailer: ELM [version 2.4ME+ PL94c (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Smith wrote: > > Is there any chance off implementing syntax like > > > > kernel=${kernel:-/kernel} > > > > which is obviously sh-compilant? > > I don't much like either of these proposals. > > My principal objection is that they're trying to solve the wrong problem. > > The original poster is setting $kernel in the DHCP client code, and then > having it overwritten when defaults/loader.conf is parsed. > > If instead they set $dhcp_kernel, and then put > > kernel=$dhcp_kernel > > in their "real" loader.conf the entire problem should go away, and we > don't have to extend any of the syntax. what's happen if $dhcp_kernel isn't sets ? Cyrille. -- Cyrille Lefevre mailto:clefevre@citeweb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 16:16:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from demai05.mw.mediaone.net (demai05.mw.mediaone.net [24.131.1.56]) by hub.freebsd.org (Postfix) with ESMTP id 4E5BA37B401 for ; Sun, 14 Oct 2001 16:16:34 -0700 (PDT) Received: from mediaone.net (nic-c61-031.mw.mediaone.net [24.131.61.31]) by demai05.mw.mediaone.net (8.11.1/8.11.1) with ESMTP id f9ENG8909018; Sun, 14 Oct 2001 19:16:09 -0400 (EDT) Message-ID: <3BCA1ACF.A1327370@mediaone.net> Date: Sun, 14 Oct 2001 19:07:59 -0400 From: "M. Greenblatt" X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Valentin Nechayev Cc: hackers@FreeBSD.ORG Subject: Re: sin_zero & bind problems References: <20011013135842.A415@iv.nn.kiev.ua> <200110131717.f9DHHLR43887@earth.backplane.com> <20011014111623.A3718@iv.nn.kiev.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Valentin Nechayev wrote: > > Sat, Oct 13, 2001 at 10:17:21, dillon (Matt Dillon) wrote about "Re: sin_zero & bind problems": > [snip] > I don't know another structure which must be > filled with zeros without mention in manuals, and rare cases with properly > documented requirement. [snip] FYI, this requirement is covered in the example source that G. Adam Stanislav provides in the "Sockets" section of the FreeBSD Developer's Handbook. http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/sockets-essential-functions.html But I guess that only helps UNIX programmers such as myself who are starting with FreeBSD by reading the Handbook :-) - Marshall > > /netch > > 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 Oct 14 16:27: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 B838437B40B; Sun, 14 Oct 2001 16:27:38 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f9ENcgx01642; Sun, 14 Oct 2001 16:38:43 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200110142338.f9ENcgx01642@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: clefevre@citeweb.net Cc: Mike Smith , Igor M Podlesny , "Daniel C. Sobral" , Vadim Vygonets , freebsd-hackers@freebsd.org Subject: Re: loader.conf conditional assignment In-reply-to: Your message of "Mon, 15 Oct 2001 00:44:19 +0200." <200110142244.f9EMiKA73045@gits.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Oct 2001 16:38:42 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > Is there any chance off implementing syntax like > > > > > > kernel=${kernel:-/kernel} > > > > > > which is obviously sh-compilant? > > > > I don't much like either of these proposals. > > > > My principal objection is that they're trying to solve the wrong problem. > > > > The original poster is setting $kernel in the DHCP client code, and then > > having it overwritten when defaults/loader.conf is parsed. > > > > If instead they set $dhcp_kernel, and then put > > > > kernel=$dhcp_kernel > > > > in their "real" loader.conf the entire problem should go away, and we > > don't have to extend any of the syntax. > > what's happen if $dhcp_kernel isn't sets ? $kernel is set to nothing. However, in this user's application, this isn't going to happen unless they're misconfigured. They won't have fetched the loader.conf that contains the above assignment unless they've contacted the right DHCP server in the first place. Note that this could *also* be worked around by setting $dhcp_kernel and then testing for it in an additional Forth procedure that runs after boot-conf. There are lots of ways of customising this. I'm not certain yet how we should handle the integration of DHCP parameters into the loader environment space; any solution needs to work well across the entire spectrum. -- ... 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 Sun Oct 14 17: 4:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wombat.bytecraft.au.com (wombat.bytecraft.au.com [203.39.118.3]) by hub.freebsd.org (Postfix) with ESMTP id 6D25337B406; Sun, 14 Oct 2001 17:04:37 -0700 (PDT) Received: from lt99101401.bytecraft.au.com (unknown [203.39.118.42]) by wombat.bytecraft.au.com (Postfix) with SMTP id 94DC43F0C; Mon, 15 Oct 2001 10:04:35 +1000 (EST) Message-ID: <04a801c1550c$f8af6fa0$2a7627cb@bytecraft.au.com> Reply-To: "MurrayTaylor" From: "MurrayTaylor" To: "Ted Mittelstaedt" Cc: , Subject: WanIC 405 _IS_ End of Life -- what are the (netgraph) based alternatives?? Date: Mon, 15 Oct 2001 10:04:33 +1000 Organization: Bytecraft Systems 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Ted et al, A- thanks for the hint re Ebay. I actually will lookup the card and manufacturer for more detail for when we are in the buying mode again. B- You should have received the End Of Life mail forwarded from Alfred Shippen ( our supplier down under ) by now so you can see where the WanIC 405 stands.... As I am quite happy with Netgraph as it is supporting multiple frame relay links as well as our MPD based VPN for our road worriers ( sorry warriors ), I now expand my original question What are the potential netgraph supported replacement cards now and under consideration, for the WanIC 405 series...?? The new (read more expensive) card is the WanIC 520/521/.... series, but I am willing to look at alternates that provide the interface to the telco NTU for frame relay. (Just as an aside, given the unique nature of the card and the us - au exchange rate, we are already paying AU$2000 ish prices for card and interface cable package, so a cheaper alternate is always welcome ;-) Murray Taylor Bytecraft Systems Pty Ltd email: murraytaylor@bytecraftsystems.com web(s): www.bytecraftsystems.com www.bytecraftentertainment.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 18:29:23 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 5B8E437B408; Sun, 14 Oct 2001 18:29:03 -0700 (PDT) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id CB1486AB08; Mon, 15 Oct 2001 10:58:59 +0930 (CST) Date: Mon, 15 Oct 2001 10:58:59 +0930 From: Greg Lehey To: Rob , Giorgos Keramidas Cc: questions@freebsd.org, hackers@freebsd.org Subject: Re: I am desperate please help my hdd Message-ID: <20011015105859.A69347@wantadilla.lemis.com> References: <20011015020830.A61548@hades.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rob@thechain.com on Sat, Oct 13, 2001 at 07:02:13PM -0400 Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Saturday, 13 October 2001 at 19:08:24 -0400, Rob wrote: > I am writing this mailing list in a desperate attempt to find out how to > restore my hdd with out loosing all the data on it. Recently I added two > additional hard drives to my freebsd 4.2 system. Once I booted up my system > and dl'ed some things with wget a bunch of errors occurred resulting in > "kernel panic" and then system halt. When I rebooted I get and error and > cannot boot freebsd On Saturday, 13 October 2001 at 19:02:13 -0400, Rob wrote: > I am writing this mailing list in a desperate attempt to find out how to > restore my hdd with out loosing all the data on it. Recently I added two > additional hard drives to my freebsd 4.2 system. Once I booted up my system > and dl'ed some things with wget a bunch of errors occurred resulting in > "kernel panic" and then system halt. When I rebooted I get and error and > cannot boot freebsd Once is enough. -hackers is not for this sort of question. > error: > > Verifying DMI Pool Data ......... >> > int=00000000 err=00000000 efl=00010246 eip=00001b2c > eax=00000002 ebx=00000002 ecx=00006564 edx=00000000 > esi=00094cdc edi=000022bf ebp=00094cbc esp=00094ca4 > cs=002b ds=0033 es=0033 fs=0033 gs=0033 gs=0033 ss=0033 > cs:eip=f7 35 98 24 00 00 89 c7-89 f9 0f af 0d 9c 24 00 > ss:esp=00 00 00 00 e0 4c 09 00-dc 4c 09 00 bf 22 00 00 > BTX halted This looks like a boot block problem. I can't see how it fits in with what you said you did. > to try to fix this problem I installed a minimal install of fbsd on another > hdd and ran > fsck /dev/ad1a which said this: > ** /dev/ad1a > BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST > ALTERNATE > /dev/ad1a: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0, size > 9809920 Did you do this while it was mounted? You shouldn't do that. You'll get bogus error messages because fsck goes straight to the disk and ignores buffer cache. If it's not mounted, then it looks like you have overwritten your primary superblock. There should be a backup one at offset 32. Try: # fsck -b 32 -n /dev/ad1a The -n will stop fsck from trying to change anything. This is important for badly mutilated file systems, since fsck is stupid enough to make things worse. > Although it doesn't really help I can still df -h it; > df /dev/ad1a prints: > Filesystem Size Used Avail Capacity Mounted on > /dev/ad1a 4.5G 1.5G 2.7G 36% > > fdisk /dev/ad1a prints: > *****Working on device /dev/ad1a ********* > parameters extracted from in-core disklabel are: > cylinders=621 heads=255 sectors/track=63 (16065 blks/cyl) > > parameters to be used for BIOS calclations are: > cylinders=621 heads=255 sectors/track=63 (16065 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 0, size 50000 (24 meg), flag 80 (active) > beg: cyl 0/ head 0/ sector 1; > end:cyl 1023/ head 255/ sector 63 That's normal enough. > Is the data on my hdd completely unrecoverable? We don't know yet. > Is there anyway I could mount the partion? > > mount /dev/ad1a /blah (/blah is a directory) prints this: > > mount: /dev/ad1a on /blah: incorrect super block You can try mounting it read-only: # mount -o ro /dev/ad1a /mnt but probably you'll get the same error. On Monday, 15 October 2001 at 2:08:31 +0300, Giorgos Keramidas wrote: > Rob wrote: >> fsck /dev/ad1a which said this: > > You are probably looking in the wrong place for a partition table. > Try this: > > # fdisk /dev/ad1 That is incorrect. That would look on a slice. We put file systems in partitions, such as /dev/ad1a. >> ** /dev/ad1a >> BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST >> ALTERNATE >> /dev/ad1a: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0, size >> 9809920 > > Are you using the disk in ``dangerously dedicated mode''? This has nothing to do with dedicated mode. The fdisk output above shows that he is using a Microsoft partition table. > Otherwise your partition table of /dev/ad1 should show some slice, > like /dev/ad1s1 and your BSD filesystems should have names like > /dev/ad1s1a, /dev/ad1s1d, etc. No, /dev/ad1a is a "compatibility partition" and represents partition a of the first FreeBSD slice. > What other disks are on your system? If this is your only disk, why > is BSD on /dev/ad1 and not on /dev/ad0? Well, he did explain that he was adding disks. But you'll also find the system on /dev/ad1a if you have a Microsoft platform on ad0. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 19: 0:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id F2A4737B405; Sun, 14 Oct 2001 19:00:26 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id UAA18462; Sun, 14 Oct 2001 20:59:44 -0500 Date: Sun, 14 Oct 2001 20:59:43 -0500 (EST) From: Doug Hass To: Ted Mittelstaedt Cc: owner-freebsd-questions@FreeBSD.ORG, MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen Subject: RE: FYI In-Reply-To: <006001c15491$1c1c6aa0$1401a8c0@tedm.placo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ted, We're SBS' worldwide distributor. Others who resell them buy them from us or from one of our distributors. In any case, I can ASSURE you without a doubt that the WANic 400 series and the entire RISCom/N2 series are end of life as of the end of September. If you have questions, feel free to contact me at your convenience. Regards, Doug ----- Doug Hass ImageStream Internet Solutions dhass@imagestream.com http://www.imagestream.com Office: 1-219-935-8484 Fax: 1-219-935-8488 On Sun, 14 Oct 2001, Ted Mittelstaedt wrote: > There are other vendors that sell the WanIC than Imagestream. I realize > that you see yourself as the only supplier but this isn't true. > > Ted Mittelstaedt tedm@toybox.placo.com > Author of: The FreeBSD Corporate Networker's Guide > Book website: http://www.freebsd-corp-net-guide.com > > > >-----Original Message----- > >From: owner-freebsd-questions@FreeBSD.ORG > >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Doug Hass > >Sent: Friday, October 12, 2001 3:11 PM > >To: owner-freebsd-questions@FreeBSD.ORG; Ted Mittelstaedt; MurrayTaylor; > >freebsd-hackers@FreeBSD.ORG; freebsd-questions@FreeBSD.ORG > >Cc: Alfred Shippen > >Subject: Re: FYI > > > > > >I'm providing this to the people whose addresses appear in the original > >messages. My apologies if this gets cross-posted or sent multiple times > >to the same place. As I mention below, the WANic 400 series cards and all > >of the RISCom/N2 series cards are now End Of Life, and only available in > >special quantity builds. > > > >If anyone reading this message needs further information, please contact > >me directly and I can go into further depth about the EOL cards mentioned > >below and their replacements in the SBS line. > > > >Regards, > > > >Doug > > > >----- > > > >Doug Hass > >ImageStream Internet Solutions > >dhass@imagestream.com > >http://www.imagestream.com > >Office: 1-219-935-8484 > >Fax: 1-219-935-8488 > > > > > >On Fri, 12 Oct 2001, Doug Hass wrote: > > > >> The WANic 400 series is definitely EOL. The cards are available in > >> quantities of 100+ only by special order. The RISCom/N2 series cards are > >> also EOL. > >> > >> This is a recent decision--it went into effect as of September 21st. > >> Closeout quantities have already been sold to other companies, so the > >> cards are only available by special order. > >> > >> The WANic 521/522 have replaced these cards, and should be used instead. > >> There are no drivers for FreeBSD, however. > >> > >> Doug > >> > >> > >> > >> On Sat, 13 Oct 2001, Alfred Shippen wrote: > >> > >> > This guy is local to you and is under the misapprehension that > >the Risc/400 > >> > series is not a discontinued item. I dont know if you want to > >follow them up > >> > or not. My customer (Bytecraft) is fine by this and has passed on the > >> > comments to me. > >> > > >> > Cheers > >> > > >> > > >> > > >> > > > >> > > ----- Original Message ----- > >> > > From: "Ted Mittelstaedt" > >> > > To: "MurrayTaylor" ; > >> > > ; > >> > > Sent: Friday, October 12, 2001 3:07 PM > >> > > Subject: RE: Imagestream WanIC-520 interface cards > >> > > > >> > > > >> > > > The WANic 5xx's use an incompatible chipset and the driver will not > >> > > > work with them. > >> > > > > >> > > > I thnk your supplier is feeding you a line of bullshit. SBS > >> > > Communications > >> > > > has posted no plans whatsover to discontinue or change the > >WANic line. > >> > > > They are fully aware that the 405's have open source drivers and are > >> > > > furthermore used in embedded systems too. > >> > > > > >> > > > The WANic 5xx series of cards sell for more money and so > >naturally your > >> > > > supplier is most interested in maximizing his margin and > >would prefer to > >> > > > push you into a more expensive card. > >> > > > > >> > > > With the increase in CPU power all of the go-fast hardware on the > >> > > higher-level > >> > > > cards is less important. > >> > > > > >> > > > Consider that the Hitachi controller chip used on the WANic > >405 is the > >> > > > SAME chip that Cisco uses in it's 25xx series of routers, > >and the Cisco > >> > > > 2501 is the most used router in the world and has the most installed > >> > > > units. > >> > > > > >> > > > SBS Communications is STILL selling the RISCom series of > >cards which is > >> > > > the predecessor to the WANic, uses the same controller, these are ISA > >> > > cards > >> > > > that have a design that's over 10 years old. > >> > > > > >> > > > You tell your supplier that since the 405 is being "phased > >out" that he > >> > > > should sell you a bunch of them at closeout prices. > >> > > > > >> > > > Ted Mittelstaedt > >> > > tedm@toybox.placo.com > >> > > > Author of: The FreeBSD Corporate > >Networker's > >> > > Guide > >> > > > Book website: > >> > > http://www.freebsd-corp-net-guide.com > >> > > > > >> > > > > >> > > > >-----Original Message----- > >> > > > >From: owner-freebsd-questions@FreeBSD.ORG > >> > > > >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of > >MurrayTaylor > >> > > > >Sent: Thursday, October 11, 2001 4:49 PM > >> > > > >To: freebsd-questions@FreeBSD.ORG; freebsd-hackers@FreeBSD.ORG > >> > > > >Subject: Imagestream WanIC-520 interface cards > >> > > > > > >> > > > > > >> > > > >As the WanIC-405 is being phased out (according to my supplier > >> > > > >down under here in OZ), has any development / testing been > >done on the > >> > > > >apparent replacement, the WanIC-521 (522, 524 ... ) range > >> > > > > > >> > > > >I am especially interested in its compatibility with its predecessor > >> > > > >which I am using very successfully for frame relay under Netgraph. > >> > > > > > >> > > > >I'm trying to get compatability info from the supplier here, > >> > > > >but we are a long way down the food chain ;-( > >> > > > > > >> > > > >Tia > >> > > > > > >> > > > >Murray Taylor > >> > > > >Bytecraft Systems Pty Ltd > >> > > > >murraytaylor@bytecraftsystems.com > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >> > > > >with "unsubscribe freebsd-questions" in the body of the message > >> > > > > > >> > > > > >> > > > > >> > > >> > >> > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-questions" 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 Oct 14 19: 6:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f60.law12.hotmail.com [64.4.19.60]) by hub.freebsd.org (Postfix) with ESMTP id 7BD3637B401 for ; Sun, 14 Oct 2001 19:06:20 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 14 Oct 2001 19:06:20 -0700 Received: from 200.64.52.137 by lw12fd.law12.hotmail.msn.com with HTTP; Mon, 15 Oct 2001 02:06:20 GMT X-Originating-IP: [200.64.52.137] From: "=?iso-8859-1?B?RmFiaeFuIFNhbGFtYW5jYQ==?=" To: freebsd-hackers@freebsd.org Subject: clustering code Date: Sun, 14 Oct 2001 21:06:20 -0500 Mime-Version: 1.0 Content-Type: text/html; charset=iso-8859-1 Message-ID: X-OriginalArrivalTime: 15 Oct 2001 02:06:20.0350 (UTC) FILETIME=[FB699DE0:01C1551D] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG
Hi!
 
I'd like to try to develop code (maybe kernel code modifications or external modules) for clustering with FreeBSD, but I'd like to see some work in order to know where I might get started, I'm thinking 'bout plain C and maybe C++ and some shell scripting,
 
Do you know any source code I may see to get these project started? It would be nice to include cluster software (for HA and PVM) with future distributions like RedHat's Piranha or HeartBeat HA SW,
 
I dont have so much money, I've just bought an Athlon 1.4 GHz computer for developing with FreeBSD (I tried Linux but it seems not to be as stable as FreeBSD 4.4) and Im out of cash, but I'd like to contribute with some code to the cause!!! And I still have to get another machine for cluster-testing,
 
Any suggestions for distributing my code with the BSD-style Licensing?
Is there a site for registering code? Here in Mexico is a litle bit difficult, I'd like to do it somewhere in the web...
 
thanx,
 
Fabián Salamanca
México City
 

Descargue GRATUITAMENTE MSN Explorer en http://explorer.msn.com
To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 19: 9: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp015.mail.yahoo.com (smtp015.mail.yahoo.com [216.136.173.59]) by hub.freebsd.org (Postfix) with SMTP id 949BA37B408 for ; Sun, 14 Oct 2001 19:09:00 -0700 (PDT) Received: from mkc-65-30-96-67.kc.rr.com (HELO yahoo.com) (65.30.96.67) by smtp.mail.vip.sc5.yahoo.com with SMTP; 15 Oct 2001 02:09:00 -0000 X-Apparently-From: Message-ID: <3BCA453B.8090209@yahoo.com> Date: Sun, 14 Oct 2001 21:08:59 -0500 From: Jim Bryant Reply-To: kc5vdj@yahoo.com User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Doug Hass Cc: Ted Mittelstaedt , owner-freebsd-questions@FreeBSD.ORG, MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen Subject: Re: FYI References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG No offense to you or your sales partners, but the way I see it, this means that tons of these will be available for a song on eBay soon, and will be in the hands of a lot of FreeBSD and Linux people [not all of which can afford top-of-the-line all of the time]. Doug Hass wrote: > Ted, > > We're SBS' worldwide distributor. Others who resell them buy them from us > or from one of our distributors. In any case, I can ASSURE you without a > doubt that the WANic 400 series and the entire RISCom/N2 series are end of > life as of the end of September. > > If you have questions, feel free to contact me at your convenience. > > Regards, > > Doug > > ----- > > Doug Hass > ImageStream Internet Solutions > dhass@imagestream.com > http://www.imagestream.com > Office: 1-219-935-8484 > Fax: 1-219-935-8488 jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! ----------------------------------------------------- POWER TO THE PEOPLE! ----------------------------------------------------- "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali _________________________________________________________ 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 Sun Oct 14 19:22:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id 852FB37B40D; Sun, 14 Oct 2001 19:22:46 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id VAA20569; Sun, 14 Oct 2001 21:22:37 -0500 Date: Sun, 14 Oct 2001 21:22:37 -0500 (EST) From: Doug Hass To: Jim Bryant Cc: Ted Mittelstaedt , owner-freebsd-questions@FreeBSD.ORG, MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen Subject: Re: FYI In-Reply-To: <3BCA453B.8090209@yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG No offense taken--if I was in a position to need the 400 series cards, I'd be snapping up all the used and auction lots I could. Nortel just auctioned off about 1000 of them, so I'd expect that there will be a glut on the used market. If money is the only concern, those cards should be available on the secondary market for next-to-nothing for a long time. If performance, features and form factor are more important, there are better chipsets available on current cards. Both approaches have their merits. Doug On Sun, 14 Oct 2001, Jim Bryant wrote: > No offense to you or your sales partners, but the way I see it, this means that tons of these will be available for a song on eBay > soon, and will be in the hands of a lot of FreeBSD and Linux people [not all of which can afford top-of-the-line all of the time]. > > Doug Hass wrote: > > > Ted, > > > > We're SBS' worldwide distributor. Others who resell them buy them from us > > or from one of our distributors. In any case, I can ASSURE you without a > > doubt that the WANic 400 series and the entire RISCom/N2 series are end of > > life as of the end of September. > > > > If you have questions, feel free to contact me at your convenience. > > > > Regards, > > > > Doug > > > > ----- > > > > Doug Hass > > ImageStream Internet Solutions > > dhass@imagestream.com > > http://www.imagestream.com > > Office: 1-219-935-8484 > > Fax: 1-219-935-8488 > > > jim > -- > ET has one helluva sense of humor! > He's always anal-probing right-wing schizos! > ----------------------------------------------------- > POWER TO THE PEOPLE! > ----------------------------------------------------- > "Religious fundamentalism is the biggest threat to > international security that exists today." > United Nations Secretary General B.B.Ghali > > > _________________________________________________________ > 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 Sun Oct 14 19:23:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id 77C4937B409; Sun, 14 Oct 2001 19:23:43 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id VAA20629; Sun, 14 Oct 2001 21:23:26 -0500 Date: Sun, 14 Oct 2001 21:23:26 -0500 (EST) From: Doug Hass To: Jim Bryant Cc: Ted Mittelstaedt , owner-freebsd-questions@FreeBSD.ORG, MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen Subject: Re: FYI In-Reply-To: <3BCA453B.8090209@yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Also--understand that the replacement for the 400 and 405 is a multi-interface card (supports all of the wiring specs instead of just 1), and costs virtually the same (or less as a reseller or in volume) than the 400/405 did. Doug On Sun, 14 Oct 2001, Jim Bryant wrote: > No offense to you or your sales partners, but the way I see it, this means that tons of these will be available for a song on eBay > soon, and will be in the hands of a lot of FreeBSD and Linux people [not all of which can afford top-of-the-line all of the time]. > > Doug Hass wrote: > > > Ted, > > > > We're SBS' worldwide distributor. Others who resell them buy them from us > > or from one of our distributors. In any case, I can ASSURE you without a > > doubt that the WANic 400 series and the entire RISCom/N2 series are end of > > life as of the end of September. > > > > If you have questions, feel free to contact me at your convenience. > > > > Regards, > > > > Doug > > > > ----- > > > > Doug Hass > > ImageStream Internet Solutions > > dhass@imagestream.com > > http://www.imagestream.com > > Office: 1-219-935-8484 > > Fax: 1-219-935-8488 > > > jim > -- > ET has one helluva sense of humor! > He's always anal-probing right-wing schizos! > ----------------------------------------------------- > POWER TO THE PEOPLE! > ----------------------------------------------------- > "Religious fundamentalism is the biggest threat to > international security that exists today." > United Nations Secretary General B.B.Ghali > > > _________________________________________________________ > 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 Sun Oct 14 19:36:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web11403.mail.yahoo.com (web11403.mail.yahoo.com [216.136.131.233]) by hub.freebsd.org (Postfix) with SMTP id 15D9137B403 for ; Sun, 14 Oct 2001 19:36:52 -0700 (PDT) Message-ID: <20011015023651.45884.qmail@web11403.mail.yahoo.com> Received: from [24.43.32.161] by web11403.mail.yahoo.com via HTTP; Sun, 14 Oct 2001 19:36:51 PDT Date: Sun, 14 Oct 2001 19:36:51 -0700 (PDT) From: Rayson Ho Subject: Re: clustering code To: "Fabián" Salamanca , freebsd-hackers@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The important question is what kind of applications do you run?? There are many clustering projects, espectially for Linux. One interesting project is the "Single System Image Clusters for Linux". http://ssic-linux.sourceforge.net/ And MOSIX is another interesting one. http://www.mosix.org/ Rayson --- Fabián Salamanca wrote: like to try to develop code (maybe kernel code modifications or external modules) for clustering with FreeBSD, but I'd like to see some work in order to know where I might get started, I'm thinking 'bout plain C and maybe C++ and some shell scripting Do you know any source code I may see to get these project started? It would be nice to include cluster software (for HA and PVM) with future distributions like RedHat's Piranha or HeartBeat HA SW, I dont have so much money, I've just bought an Athlon 1.4 GHz computer for developing with FreeBSD (I tried Linux but it seems not to be as stable as FreeBSD 4.4) and Im out of cash, but I'd like to contribute with some code to the cause!!! And I still have to get another machine for cluster-testing Any suggestions for distributing my code with the BSD-style Licensing? Is there a site for registering code? Here in Mexico is a litle bit difficult, I'd like to do it somewhere in the web. __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 20: 5:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with SMTP id CCA4B37B40A for ; Sun, 14 Oct 2001 20:05:45 -0700 (PDT) Received: (qmail 966292 invoked from network); 14 Oct 2001 21:05:45 -0600 Received: from snaresland.acl.lanl.gov (128.165.147.113) by acl.lanl.gov with SMTP; 14 Oct 2001 21:05:45 -0600 Received: (qmail 31510 invoked by uid 3499); 14 Oct 2001 21:05:44 -0600 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 14 Oct 2001 21:05:44 -0600 Date: Sun, 14 Oct 2001 21:05:44 -0600 (MDT) From: Ronald G Minnich X-X-Sender: To: =?iso-8859-1?B?RmFiaeFuIFNhbGFtYW5jYQ==?= Cc: Subject: Re: clustering code In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 14 Oct 2001, Fabián Salamanca wrote: > I'd like to try to develop code (maybe kernel code modifications or > external modules) for clustering with FreeBSD, but I'd like to see some > work in order to know where I might get started, I'm thinking 'bout plain > C and maybe C++ and some shell scripting, no. That's yucky. Take a good hard look at what scyld.com has, or go to the source forge and check out the bproc project. We definitely don't need another ball of C/C++ + scripts. If you're going to do that then just get OSCAR and port it to freebsd. But if you want to do something new and interesting you could get a bproc-like system working on freebsd. We run two 128-node clusters here with this stuff, and one of them uses linuxbios, and I have to say it's a total change in the way we do clusters. Instant cluster boot, no local root disks (local /tmp of course!), upgrade all the software in < 1 minute, ... it's really nice. We distribute our stuff via the sourceforge, you can also try bitkeeper.com. Both are really nice. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 20:22: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with SMTP id A238837B408 for ; Sun, 14 Oct 2001 20:21:59 -0700 (PDT) Received: (qmail 659639 invoked from network); 14 Oct 2001 21:21:58 -0600 Received: from snaresland.acl.lanl.gov (128.165.147.113) by acl.lanl.gov with SMTP; 14 Oct 2001 21:21:58 -0600 Received: (qmail 31529 invoked by uid 3499); 14 Oct 2001 21:21:58 -0600 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 14 Oct 2001 21:21:58 -0600 Date: Sun, 14 Oct 2001 21:21:58 -0600 (MDT) From: Ronald G Minnich X-X-Sender: To: Rayson Ho Cc: =?ISO-8859-1?Q?Fabi=E1n_Salamanca?= , Subject: Re: clustering code In-Reply-To: <20011015023651.45884.qmail@web11403.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 14 Oct 2001, Rayson Ho wrote: > http://ssic-linux.sourceforge.net/ A collection of some really bad ideas, not likely to scale well. Note that they've got up to 30 nodes, wow. Double it once and that's where this kind of "global everything" idea starts to fall over. Badly. It would be neat to see freebsd do something really new and novel in clustering. ssci-linux is not it. It's going to be very hard to pick something new, a lot of the ground is well-trod. For other examples of what you can do (maybe not what you SHOULD do) see npaci ROCKS, OSCAR, and follow the references from there. On the should-do list, see plan 9 -- (on plan 9 I tend to sound like a broken record) read and understand the Plan 9 stuff, see how well it would work as a cluster technology (we have a 32-node plan 9 cluster here, it's quite cool), and see about bringing those neat ideas to freebsd. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 14 22:43: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id 25F5537B40C; Sun, 14 Oct 2001 22:42:55 -0700 (PDT) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id IQL64033; Mon, 15 Oct 2001 08:42:43 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.11.6/8.11.6) id f9F5g3u01507; Mon, 15 Oct 2001 08:42:03 +0300 (EEST) (envelope-from netch) Date: Mon, 15 Oct 2001 08:42:03 +0300 From: Valentin Nechayev To: Bsdguru@aol.com Cc: chat@FreeBSD.ORG Subject: Re: Imagestream WanIC-520 interface cards Message-ID: <20011015084203.A446@iv.nn.kiev.ua> References: <11f.5a43fcd.28fb1e4e@aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11f.5a43fcd.28fb1e4e@aol.com>; from Bsdguru@aol.com on Sun, Oct 14, 2001 at 12:58:54PM -0400 X-42: On Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG (redirected to -chat. it's pity that there are no freebsd-flame@ redirected to /dev/null;)) Sun, Oct 14, 2001 at 12:58:54, Bsdguru (Bsdguru@aol.com) wrote about "Re: Imagestream WanIC-520 interface cards": > Thats pretty lame Matt. I hope you're joking. (Otherwise you should carefully consider your own lameness.;)) > sort of like saying unix sucks because of all of the > bugs and growing pains over the years. Zebra has come a long way, and its as > easy to configure as a cisco. Your problems with gated and BSDI have more to > do with those organizations than anything else, plus it is stuck with an ill > conceived interface. There is a host near me who panic'ed each time zebra was running at it. (I couldn't even understand core dump - stack and process list were filled with garbage. Possibly, nlist was overwritten? And no disctinct diagnosis was got from it...) Now it lives with gated without such strange problems. This was only one small example. If you aren't lame you should understand that external conditions can be so strange that cannot allow your The Only Right Way. > Lets face it, if cisco didnt tell you what to type into your config file > almost noone would be able to get them to work either. Do you work with cisco tightly? (Question maybe is rhitoric) /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 0:10:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.focalnetworks.net (alpha.focalnetworks.net [209.135.104.32]) by hub.freebsd.org (Postfix) with SMTP id 426FE37B405 for ; Mon, 15 Oct 2001 00:10:24 -0700 (PDT) Received: (qmail 3564 invoked by uid 1000); 15 Oct 2001 07:14:02 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 15 Oct 2001 07:14:02 -0000 Date: Mon, 15 Oct 2001 03:14:02 -0400 (EDT) From: project10 To: Cc: Subject: FreeBSD Jails and IRCDs Message-ID: <20011015031331.R3484-100000@alpha.focalnetworks.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey all, Has anyone experienced issues with running IRCDs within FreeBSD jails, specifically hostnames not resolving? After users connect, the ircd attempts to do a reverse lookup on the IP, which fails. I've tracked it down to the point where I believe it is either a bug or a limitation of the jail system, but would like a second opinion. resolv.conf on the host system and the jail are setup properly, 'nslookup' works fine. I've tested many different IRCds in different jails on different hosts. The jails were setup according to the jail man page. I also tried setting up a DNS server within the jail, and specifying it as a nameserver in resolv.conf, and that didn't allow hostnames to be resolved. Additionally, running ircd outside of the jail, on the host system, everything worked fine. I did some tcpdumps from the host system and it doesn't appear that the packets are being sent to the DNS server. It is noteworthy that the hostname resolve attempts 'time out' as opposed to fail almost immediately. Any help or assistance anyone can provide would be greatly appreciated. I am, quite frankly, out of ideas. -Shawn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 0:28:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 79C7137B406; Mon, 15 Oct 2001 00:28:02 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9F7RwT15354; Mon, 15 Oct 2001 00:27:58 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "MurrayTaylor" Cc: , Subject: RE: WanIC 405 _IS_ End of Life -- what are the (netgraph) based alternatives?? Date: Mon, 15 Oct 2001 00:27:56 -0700 Message-ID: <000001c1554a$e922d700$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 In-Reply-To: <04a801c1550c$f8af6fa0$2a7627cb@bytecraft.au.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of MurrayTaylor >Sent: Sunday, October 14, 2001 5:05 PM >To: Ted Mittelstaedt >Cc: freebsd-questions@FreeBSD.ORG; freebsd-hackers@FreeBSD.ORG >Subject: WanIC 405 _IS_ End of Life -- what are the (netgraph) based >alternatives?? > > >Hi Ted et al, > >A- thanks for the hint re Ebay. I actually will lookup the >card and manufacturer for more detail for when we are in the >buying mode again. > >B- You should have received the End Of Life mail forwarded from >Alfred Shippen ( our supplier down under ) by now so >you can see where the WanIC 405 stands.... > SBS, not Imagestream, is the manufacturer of the WANic405. What happened is a long time ago SBS signed some kind of deal with Imagestream to where Imagestream took over driver authorship. Previous to that, SBS (actually SDL Communication) supplied drivers for the cards directly. SDL/SBS transferred all of their code over to Imagestream as a part of that deal, and since that time Imagestream has been unwilling to work with the FreeBSD community to write drivers. (I know because R Grimes attempted a number of times to get source to the drivers and Imagestream sent him in a runaround) Before SDL signed the deal with Imagestream, they were free with the programming details for the WANic cards. In fact I have a bunch of documentation I got with an older RIScom card that I have (in service, actually) that explains how to program it, along with a BSD driver skeleton. Since the WANic 400 series used the same programming interface it was a simple matter to mod the driver for the RISCom card to work with the WANic. Undoubtedly the sr driver that John Hay is responsible for originated from this documentation. Since that deal, SDL (now SBS) will not supply driver programming details undoubtedly because Imagestream has them gagged. And Imagestream will not supply programming details nor driver source for their Linux drivers for the higher-order WANic cards, nor will they port it over to FreeBSD. Imagestream was probably the largest reseller of the WANic 400 series cards. So when they stopped selling them, I would guess that most distributors were buying them from Imagestream, and thus were affected. But I know that Rod actually has filled out the paperwork with SBS to be a reseller for them and has (in the past) sold the cards through his company. (without going through the Imagestream loop) I don't know what he's doing nowadays. I also recall that when SDL was still supplying drivers pre-Imagestream, that there were a number of other resellers listed as selling these. A year ago, at my request, the sister VAR of the ISP that I worked for contacted SBS and got the paperwork from them to resell the WANic cards. They ended up never completing it because we found that when people queried SBS for driver support they were referring them to Imagestream, and since everyone asks this question, it was effectively funneling all sales prospects to Imagestream. Also, Imagestream wasn't marking up the WANic 400 cards that much so we decided that it wasn't worth the trouble to bother with it. Perhaps we should revisit this now that Imagestream has made their announcement. >As I am quite happy with Netgraph as it is supporting >multiple frame relay links as well as our MPD based VPN for our >road worriers ( sorry warriors ), I now expand my original question > > >What are the potential netgraph supported replacement cards now and >under consideration, for the WanIC 405 series...?? > I know that Rod Grimes got pissed off enough with this whole WANic400 series/Imagestream driver problem a year ago that he stopped using those cards and switched to something else. He probably builds 5-10 FreeBSD-based T1 routers a year under contract. I don't remember what he told me that he switched to, though. He was using Netgraph with the 405 before he switched. I still use the SBS cards, and I have a small stash of the 405's that I will continue to use as spares. Also, if there's demand for these I think that my associates would probably start selling them. There's also probably still a number of resellers out there that can still sell these directly from SBS you would just need to get their names and give them the right part numbers for their computers. >The new (read more expensive) card is the WanIC 520/521/.... series, >but I am willing to look at alternates that provide the interface >to the telco NTU for frame relay. > >(Just as an aside, given the unique nature of the card and the >us - au exchange rate, we are already paying AU$2000 ish prices for card and >interface cable package, so a cheaper alternate is always welcome ;-) > As has been pointed out in this forum, a much cheaper alternative is to use a Cisco or other router, and connect that to the FreeBSD system. It's difficult to do this when your running BGP because the external peers must be a single hop away, you cannot have an intermediate router (normally) in between. While bringing the interface into the PC has certain technical advantages in theory, as Matt pointed out, it takes a bit of tweaking to get it to work right. Also it's definitely non-standard so larger organizations aren't going to want to do this. This is one area where FreeBSD could stand to get a lot of work done. Not in the netgraph code (although that needs it) but there's few WAN cards supported under FreeBSD. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 1: 5:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from marimba.wcape.school.za (marimba-sat.wcape.school.za [196.34.234.124]) by hub.freebsd.org (Postfix) with ESMTP id E034C37B403 for ; Mon, 15 Oct 2001 01:05:12 -0700 (PDT) Received: from ukhokho.schoolnet.org.za ([196.14.22.9]) by marimba.wcape.school.za with esmtp (Exim 3.30 #1) id 15t2kE-000L9E-00 for freebsd-hackers@freebsd.org; Mon, 15 Oct 2001 10:05:06 +0200 Subject: Adding support for Duxbury PCI modem to FreeBSD 4.4 Date: Mon, 15 Oct 2001 10:02:27 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: <9DCF7A9E7AD27A4F962A37F7E78607B10CFAEC@ukhokho.ct.schoolnet.org.za> X-MS-Has-Attach: content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 X-MS-TNEF-Correlator: Thread-Topic: Adding support for Duxbury PCI modem to FreeBSD 4.4 Thread-Index: AcFVUBX6wMbjl8FNEdWu5gBQ2rIL2g== From: "Peter van Heusden" To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all I've just installed FreeBSD 4.4, and also recently purchased a \Duxbury 56kpci modem (a real modem, not a winmodem). I'm now trying to get this to work with 4.4, so... I noticed that PCI modems are detected in /sys/isa/sio.c. I added the chip=20 id of the modem to the list of PCI devices (pci_ids), and now sio_pci_probe detects the modem, but the sioprobe() fails. Before I got digging into the sioprobe code (which seems rather complex), I'd like to verify that my pci_ids entry is correct. One thing I don't understand is the rid field of the pci_id structure. Some modems have this set to 0x10, others to 0x14. I'm not sure what to set it=20 to - how do I determine this? Thanks for any help (btw. this is my first attempt to add anything to the FreeBSD kernel, so please excuse any naive questions). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 1:17:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from server.soekris.com (soekris.com [216.15.61.44]) by hub.freebsd.org (Postfix) with ESMTP id 99C4D37B40D; Mon, 15 Oct 2001 01:17:14 -0700 (PDT) Received: from soekris.com (1.4.soekris.com [192.168.1.4] (may be forged)) by server.soekris.com (8.9.2/8.9.2) with ESMTP id BAA11809; Mon, 15 Oct 2001 01:17:15 -0700 (PDT) (envelope-from soren@soekris.com) Message-ID: <3BCA9B7E.BBEC1C7D@soekris.com> Date: Mon, 15 Oct 2001 01:17:02 -0700 From: Soren Kristensen Organization: Soekris Engineering X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ted Mittelstaedt Cc: MurrayTaylor , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: WanIC 405 _IS_ End of Life -- what are the (netgraph) based alternatives?? References: <000001c1554a$e922d700$1401a8c0@tedm.placo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Everybody, I've been following the sync serial board discussion a little, and it seems like that there's no source for inexpensive sync serial boards with FreeBSD, or boards with documentation to make a driver, or from companies with a good policy towards open source and/or FreeBSD.... The only one close seems to be the cronyx, they seems to have full source code, but their boards is not easily available in the US, or available with T1 interfaces. So maybe I should just make one, and sell for cheap, I need them anyway for my small boxes (see http://www.soekris.com).... The most common chip for the PCI bus, the 4 channel Infinion DSCC4 PEB20534 (used by cronyx and others...) cost around $60 in small volume, so the basic 2 ch board would probably go for around $250 qty 1. Boards with more channels or integrated T1/E1 phys will be a little higher. FreeBSd drivers should be relatively easy, t.ex based on the cronyx drivers, they're even netgraph enabled.... I would then be happy to supply hardware and documentation to somebody that could do and maintain the drivers. Regards, Soren Kristensen Soekris Engineering To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 1:51: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 8284F37B401; Mon, 15 Oct 2001 01:50:56 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9F8ooT15501; Mon, 15 Oct 2001 01:50:50 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Doug Hass" , "Jim Bryant" Cc: "MurrayTaylor" , , , "Alfred Shippen" Subject: RE: FYI Date: Mon, 15 Oct 2001 01:50:49 -0700 Message-ID: <002e01c15556$7d0c6fc0$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Doug Hass >Sent: Sunday, October 14, 2001 7:23 PM >To: Jim Bryant >Cc: Ted Mittelstaedt; owner-freebsd-questions@FreeBSD.ORG; MurrayTaylor; >freebsd-hackers@FreeBSD.ORG; freebsd-questions@FreeBSD.ORG; Alfred >Shippen >Subject: Re: FYI > > >Also--understand that the replacement for the 400 and 405 is a >multi-interface card (supports all of the wiring specs instead of just 1), >and costs virtually the same (or less as a reseller or in volume) than the >400/405 did. > And if you want to sell these to FreeBSD users then make your Linux driver source (not the SAND stuff) available so that we can mod it into our own driver. Many other companies do this and as a matter of fact, we (meaning FreeBSD) have even found bugs in crummy Linux drivers that have been reported back to Linux and helped those manufacturers better their products. No offense, but once Imagestream stopped selling WANic400's you ceased being an entity of interest to FreeBSD, as you no longer sell any products that run under it. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >Doug > >On Sun, 14 Oct 2001, Jim Bryant wrote: > >> No offense to you or your sales partners, but the way I see it, >this means that tons of these will be available for a song on eBay >> soon, and will be in the hands of a lot of FreeBSD and Linux >people [not all of which can afford top-of-the-line all of the time]. >> >> Doug Hass wrote: >> >> > Ted, >> > >> > We're SBS' worldwide distributor. Others who resell them buy >them from us >> > or from one of our distributors. In any case, I can ASSURE you without a >> > doubt that the WANic 400 series and the entire RISCom/N2 series >are end of >> > life as of the end of September. >> > >> > If you have questions, feel free to contact me at your convenience. >> > >> > Regards, >> > >> > Doug >> > >> > ----- >> > >> > Doug Hass >> > ImageStream Internet Solutions >> > dhass@imagestream.com >> > http://www.imagestream.com >> > Office: 1-219-935-8484 >> > Fax: 1-219-935-8488 >> >> >> jim >> -- >> ET has one helluva sense of humor! >> He's always anal-probing right-wing schizos! >> ----------------------------------------------------- >> POWER TO THE PEOPLE! >> ----------------------------------------------------- >> "Religious fundamentalism is the biggest threat to >> international security that exists today." >> United Nations Secretary General B.B.Ghali >> >> >> _________________________________________________________ >> 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-questions" 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 Oct 15 1:56:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 3E67937B403; Mon, 15 Oct 2001 01:56:31 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9F8uPT15531; Mon, 15 Oct 2001 01:56:25 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Soren Kristensen" Cc: "MurrayTaylor" , , Subject: RE: WanIC 405 _IS_ End of Life -- what are the (netgraph) based alternatives?? Date: Mon, 15 Oct 2001 01:56:25 -0700 Message-ID: <002f01c15557$44f1d660$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 In-Reply-To: <3BCA9B7E.BBEC1C7D@soekris.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Soren Kristensen [mailto:soren@soekris.com] >Sent: Monday, October 15, 2001 1:17 AM >To: Ted Mittelstaedt >Cc: MurrayTaylor; freebsd-questions@FreeBSD.ORG; >freebsd-hackers@FreeBSD.ORG >Subject: Re: WanIC 405 _IS_ End of Life -- what are the (netgraph) based >alternatives?? > > >Hi Everybody, > >I've been following the sync serial board discussion a little, and it >seems like that there's no source for inexpensive sync serial boards >with FreeBSD, or boards with documentation to make a driver, or from >companies with a good policy towards open source and/or FreeBSD.... > >The only one close seems to be the cronyx, they seems to have full >source code, but their boards is not easily available in the US, or >available with T1 interfaces. > >So maybe I should just make one, and sell for cheap, I need them anyway >for my small boxes (see http://www.soekris.com).... The most common chip >for the PCI bus, the 4 channel Infinion DSCC4 PEB20534 (used by cronyx >and others...) cost around $60 in small volume, so the basic 2 ch board >would probably go for around $250 qty 1. Boards with more channels or >integrated T1/E1 phys will be a little higher. > >FreeBSd drivers should be relatively easy, t.ex based on the cronyx >drivers, they're even netgraph enabled.... > >I would then be happy to supply hardware and documentation to somebody >that could do and maintain the drivers. > An interesting proposition. However, you might find it even easier to do a Hitachi HD64570-based board. It should be much easier to modify the sr driver to work with it than to write a new one from scratch. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 2: 5:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id EA6A837B40B; Mon, 15 Oct 2001 02:05:27 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9F94ea45763; Mon, 15 Oct 2001 11:04:40 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Soren Kristensen Cc: Ted Mittelstaedt , MurrayTaylor , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: WanIC 405 _IS_ End of Life -- what are the (netgraph) based alternatives?? In-Reply-To: Your message of "Mon, 15 Oct 2001 01:17:02 PDT." <3BCA9B7E.BBEC1C7D@soekris.com> Date: Mon, 15 Oct 2001 11:04:40 +0200 Message-ID: <45761.1003136680@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3BCA9B7E.BBEC1C7D@soekris.com>, Soren Kristensen writes: >So maybe I should just make one, and sell for cheap, I need them anyway >for my small boxes (see http://www.soekris.com).... The most common chip >for the PCI bus, the 4 channel Infinion DSCC4 PEB20534 (used by cronyx >and others...) cost around $60 in small volume, so the basic 2 ch board >would probably go for around $250 qty 1. Boards with more channels or >integrated T1/E1 phys will be a little higher. We already have drivers in the tree for the infinion "MUNICHX" chip, when used with a FALC frontend. We also have drivers for the MUSYCC from Conexant. -- 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 Mon Oct 15 2:10:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bubo.vslib.cz (bubo.vslib.cz [147.230.16.1]) by hub.freebsd.org (Postfix) with ESMTP id DDF6137B40C for ; Mon, 15 Oct 2001 02:10:10 -0700 (PDT) Received: from 127.0.0.1 (bubo.vslib.cz [127.0.0.1]) by bubo.vslib.cz (Postfix) with SMTP id EB8F58390; Mon, 15 Oct 2001 11:10:09 +0200 (CEST) Received: from A410A (a410a.kolej.vslib.cz [147.230.152.17]) by bubo.vslib.cz (Postfix) with SMTP id 0DE83839F; Mon, 15 Oct 2001 11:10:09 +0200 (CEST) Message-ID: <000701c15559$8908f340$1198e693@kolej.vslib.cz> From: "Martin Vana" To: , Subject: Date: Mon, 15 Oct 2001 11:12:37 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG still aint working (connection dropped on reset, unknown error 0); Im a total newbie so maybe I did something wrong, i did exactly this, cd /usr/ports/someport make FETCH_BEFORE_ARGS=-p >hi, >when i am trying to port some program from ports directory (4.3stable) it >never connects to a ftp. Problem might be a firewall, there are so few ports >allowed, but 21 is. Anyone has the same experience? Of course, establishing an active data connection also means having the server connect to an ephemeral port on your machine which is not allowed. make FETCH_BEFORE_ARGS=-p will give you passive ftp instead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 2:29:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id E5C2137B40F; Mon, 15 Oct 2001 02:29:32 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9F9TFT16014; Mon, 15 Oct 2001 02:29:15 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Poul-Henning Kamp" , "Soren Kristensen" Cc: "MurrayTaylor" , , Subject: RE: WanIC 405 _IS_ End of Life -- what are the (netgraph) based alternatives?? Date: Mon, 15 Oct 2001 02:29:15 -0700 Message-ID: <003e01c1555b$db6e2c20$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 In-Reply-To: <45761.1003136680@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Poul-Henning Kamp [mailto:phk@critter.freebsd.dk] >Sent: Monday, October 15, 2001 2:05 AM >To: Soren Kristensen >Cc: Ted Mittelstaedt; MurrayTaylor; freebsd-questions@FreeBSD.ORG; >freebsd-hackers@FreeBSD.ORG >Subject: Re: WanIC 405 _IS_ End of Life -- what are the (netgraph) based >alternatives?? > > >In message <3BCA9B7E.BBEC1C7D@soekris.com>, Soren Kristensen writes: > >>So maybe I should just make one, and sell for cheap, I need them anyway >>for my small boxes (see http://www.soekris.com).... The most common chip >>for the PCI bus, the 4 channel Infinion DSCC4 PEB20534 (used by cronyx >>and others...) cost around $60 in small volume, so the basic 2 ch board >>would probably go for around $250 qty 1. Boards with more channels or >>integrated T1/E1 phys will be a little higher. > >We already have drivers in the tree for the infinion "MUNICHX" chip, >when used with a FALC frontend. We also have drivers for the MUSYCC >from Conexant. > Ha hmm - Poul, do you how what the reference boards were that these drivers were tested/developed with? Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 2:52: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from server.soekris.com (soekris.com [216.15.61.44]) by hub.freebsd.org (Postfix) with ESMTP id CF5C737B407; Mon, 15 Oct 2001 02:51:59 -0700 (PDT) Received: from soekris.com (1.4.soekris.com [192.168.1.4] (may be forged)) by server.soekris.com (8.9.2/8.9.2) with ESMTP id CAA12172; Mon, 15 Oct 2001 02:51:51 -0700 (PDT) (envelope-from soren@soekris.com) Message-ID: <3BCAB1B6.FD33B9BA@soekris.com> Date: Mon, 15 Oct 2001 02:51:50 -0700 From: Soren Kristensen Organization: Soekris Engineering X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ted Mittelstaedt Cc: Poul-Henning Kamp , MurrayTaylor , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: WanIC 405 _IS_ End of Life -- what are the (netgraph) based alternatives?? References: <003e01c1555b$db6e2c20$1401a8c0@tedm.placo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Ted Mittelstaedt wrote: > > An interesting proposition. However, you might find it even easier to > do a Hitachi HD64570-based board. It should be much easier to modify > the sr driver to work with it than to write a new one from scratch. > As other people already has said, it don't looks like that Hitachi is in it for the long run, and it's not for higher speeds, I would like to also be able to do E3/T3..... And anyway, the HD64570 is not a PCI chip, requering additional chips to interface to the PCI bus. Poul-Henning Kamp wrote: > > We already have drivers in the tree for the infinion "MUNICHX" chip, > when used with a FALC frontend. We also have drivers for the MUSYCC > from Conexant. > The PEB20321 (Munich32) supported in that driver is a channelized version, that not really what people are asking for.... It's also low speed, and support only one interface if used unchannelized. I don't remember about the Conexant chip, but I think it's channelized too. Paul, do you know how close the PEB20321 and PEB20534 are from a programming point if view ? But the FALC phy might be good for the T1/E1 versions. I have look around for sync serial controllers, but keep comming back to the PEB20534, I think that the best chip available for the job. Regards, Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 2:53:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 34F7D37B401; Mon, 15 Oct 2001 02:53:17 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9F9qwa46742; Mon, 15 Oct 2001 11:52:58 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Ted Mittelstaedt" Cc: "Soren Kristensen" , "MurrayTaylor" , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: WanIC 405 _IS_ End of Life -- what are the (netgraph) based alternatives?? In-Reply-To: Your message of "Mon, 15 Oct 2001 01:56:25 PDT." <002f01c15557$44f1d660$1401a8c0@tedm.placo.com> Date: Mon, 15 Oct 2001 11:52:58 +0200 Message-ID: <46740.1003139578@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <002f01c15557$44f1d660$1401a8c0@tedm.placo.com>, "Ted Mittelstaedt" writes: >An interesting proposition. However, you might find it even easier to >do a Hitachi HD64570-based board. It should be much easier to modify >the sr driver to work with it than to write a new one from scratch. We want something with an integral T1/E1 DSU/CSU, otherwise cost is still prohibitive. -- 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 Mon Oct 15 3: 0: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id B899937B410; Mon, 15 Oct 2001 02:59:55 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9F9xaa46855; Mon, 15 Oct 2001 11:59:36 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Soren Kristensen Cc: Ted Mittelstaedt , MurrayTaylor , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: WanIC 405 _IS_ End of Life -- what are the (netgraph) based alternatives?? In-Reply-To: Your message of "Mon, 15 Oct 2001 02:51:50 PDT." <3BCAB1B6.FD33B9BA@soekris.com> Date: Mon, 15 Oct 2001 11:59:36 +0200 Message-ID: <46853.1003139976@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3BCAB1B6.FD33B9BA@soekris.com>, Soren Kristensen writes: >The PEB20321 (Munich32) supported in that driver is a channelized >version, that not really what people are asking for.... It's also low >speed, and support only one interface if used unchannelized. One one wire you have only one "circuit" if unchannelized. There is a "bigger brother" MUNIC128X now which is suitable for an 4 port card. >I don't >remember about the Conexant chip, but I think it's channelized too. Both the Munich and Connexant can run channelized or unchannelized. >Paul, do you know how close the PEB20321 and PEB20534 are from a >programming point if view ? But the FALC phy might be good for the T1/E1 >versions. > >I have look around for sync serial controllers, but keep comming back to >the PEB20534, I think that the best chip available for the job. I don't know how similar they are, either way, all the work on the if_mn and musycc drivers were in the framers and clocking. The HDLC is just a piece of cake... -- 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 Mon Oct 15 3:10:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 22A4837B40F; Mon, 15 Oct 2001 03:10:37 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9FAAHa47006; Mon, 15 Oct 2001 12:10:17 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Ted Mittelstaedt" Cc: "Soren Kristensen" , "MurrayTaylor" , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: WanIC 405 _IS_ End of Life -- what are the (netgraph) based alternatives?? In-Reply-To: Your message of "Mon, 15 Oct 2001 02:29:15 PDT." <003e01c1555b$db6e2c20$1401a8c0@tedm.placo.com> Date: Mon, 15 Oct 2001 12:10:17 +0200 Message-ID: <47004.1003140617@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <003e01c1555b$db6e2c20$1401a8c0@tedm.placo.com>, "Ted Mittelstaedt" >>We already have drivers in the tree for the infinion "MUNICHX" chip, >>when used with a FALC frontend. We also have drivers for the MUSYCC >>from Conexant. >> >Ha hmm - Poul, do you how what the reference boards were that these >drivers were tested/developed with? Yes I know (since I wrote them :-) The MUNICHX driver were written on the "EASY321" eval kit from Siemens (Now Infinieon) and the MUSYCC was written on LMC's 1504 card which is now discontinued. -- 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 Mon Oct 15 3:13: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id EAABF37B436; Mon, 15 Oct 2001 03:12:44 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9FACaT16141; Mon, 15 Oct 2001 03:12:36 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Poul-Henning Kamp" Cc: "Soren Kristensen" , "MurrayTaylor" , , Subject: RE: WanIC 405 _IS_ End of Life -- what are the (netgraph) based alternatives?? Date: Mon, 15 Oct 2001 03:12:36 -0700 Message-ID: <004001c15561$e9ce88e0$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 In-Reply-To: <46740.1003139578@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Poul-Henning >Kamp >Sent: Monday, October 15, 2001 2:53 AM >To: Ted Mittelstaedt >Cc: Soren Kristensen; MurrayTaylor; freebsd-questions@FreeBSD.ORG; >freebsd-hackers@FreeBSD.ORG >Subject: Re: WanIC 405 _IS_ End of Life -- what are the (netgraph) based >alternatives?? > > >We want something with an integral T1/E1 DSU/CSU, otherwise cost is >still prohibitive. as long as there's a carrier detect and a DTE light I hope. A little button for a hard loop would be good too. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 4: 7:30 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 5116237B407 for ; Mon, 15 Oct 2001 04:07:27 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id E4B7D14C2E; Mon, 15 Oct 2001 13:07:25 +0200 (CEST) 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: Seth Kingsley Cc: Peter Pentchev , Mike Meyer , hackers@freebsd.org Subject: Re: My contributions to the close a PR campaign References: <15301.63455.964624.626361@guru.mired.org> <200110112245.f9BMjAS66764@gits.dyndns.org> <15302.12256.96805.125719@guru.mired.org> <20011012100527.B78786@straylight.oblivion.bg> <20011012213311.A95968@fluff.meowfishies.com> From: Dag-Erling Smorgrav Date: 15 Oct 2001 13:07:25 +0200 In-Reply-To: <20011012213311.A95968@fluff.meowfishies.com> Message-ID: Lines: 9 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Seth Kingsley writes: > Why not remove it after using it to restore the mixer state? It would > only exist to survive a reboot. You'd have to reset everything manually after a crash. 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 Mon Oct 15 4:25:47 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 766DA37B405 for ; Mon, 15 Oct 2001 04:25:44 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 04CBD14C2E; Mon, 15 Oct 2001 13:25:42 +0200 (CEST) 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: David Taylor Cc: Paolo Pisati , freebsd-hackers@FreeBSD.ORG Subject: Re: First prg with sysctl References: <20011013194902.A38183@newluxor.skynet.org> <20011013190909.A29541@gattaca.yadt.co.uk> From: Dag-Erling Smorgrav Date: 15 Oct 2001 13:25:42 +0200 In-Reply-To: <20011013190909.A29541@gattaca.yadt.co.uk> Message-ID: Lines: 8 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Taylor writes: > [...] That, and he should be using sysctlbyname() instead of sysctl(). 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 Mon Oct 15 6:53:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id 69A5237B408; Mon, 15 Oct 2001 06:53:40 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id IAA14106; Mon, 15 Oct 2001 08:53:14 -0500 Date: Mon, 15 Oct 2001 08:53:14 -0500 (EST) From: Doug Hass Reply-To: Doug Hass To: Ted Mittelstaedt Cc: Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen Subject: RE: FYI In-Reply-To: <002e01c15556$7d0c6fc0$1401a8c0@tedm.placo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > And if you want to sell these to FreeBSD users then make your Linux driver > source (not the SAND stuff) available so that we can mod it into our own > driver. Many other companies do this and as a matter of fact, we (meaning > FreeBSD) have even found bugs in crummy Linux drivers that have been reported > back to Linux and helped those manufacturers better their products. I'm not going to get dragged into an OS war. Both Linux and FreeBSD have their share of "crummy" drivers and features. That discussion is honestly beyond the scope of a discussion of ImageStream's SAND architecture and the WANic 400 series. We are bound by third party agreements and are not allowed to release any more free code (legally) than we already have. If we were not restricted by SBS, Trillium, and Rockwell (among others), we would release all of the code under GPL or lGPL. These agreements do NOT prevent us from working with developers to support other platforms, though. It only prevents the free release of portions of the code. That being said, we're always interested in supporting a wide variety of platforms. Without the SAND architecture, though, there really is little hope of having FreeBSD support for the WANic 520 series cards (or other cards, for that matter). If there are developers in the community interested in porting SAND and the various hardware modules (for the 520 series and other cards) to FreeBSD, we'll be happy to work with them and support that effort. It is in ALL of our interests to have the widest support for standards-based technologies as possible. > No offense, but once Imagestream stopped selling WANic400's you > ceased being an entity of interest to FreeBSD, as you no longer sell > any products that run under it. I'll reiterate what I've said to you privately: ImageStream DID NOT make the decision to discontinue the 400 series or the RISCom/N2 series. This decision rested solely with SBS. However, FreeBSD users are NOT without options: 1) FreeBSD users can still get the WANic 400 and RISCom cards from the second hand market, as another person mentioned. 2) WANic 400 series cards are still available in quantity. If the market for FreeBSD is as large as you claim, then you or someone else in the community should have no problem snapping up a quantity of these cards and reselling them to interested parties. I'll go one step further: If anyone contacts me about the WANic 400 series, mentions that they are for FreeBSD, I promise to give an extra 15% discount over and above our normal volume discounts just to illustrate my desire to support the FreeBSD community. 3) Virtually ALL of our customers, save for OEMs making their own products, purchase complete routers. Going this route would eliminate the need to have FreeBSD support, as any user would have a standalone router. Regards, Doug ----- Doug Hass ImageStream Internet Solutions dhass@imagestream.com http://www.imagestream.com Office: 1-219-935-8484 Fax: 1-219-935-8488 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 7:35:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id 07A0437B406; Mon, 15 Oct 2001 07:35:25 -0700 (PDT) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id f9FEZ7h90910; Mon, 15 Oct 2001 10:35:07 -0400 (EDT) (envelope-from bicknell) Date: Mon, 15 Oct 2001 10:35:07 -0400 From: Leo Bicknell To: Doug Hass Cc: Ted Mittelstaedt , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen Subject: Re: FYI Message-ID: <20011015103507.B90657@ussenterprise.ufp.org> Mail-Followup-To: Doug Hass , Ted Mittelstaedt , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen References: <002e01c15556$7d0c6fc0$1401a8c0@tedm.placo.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 dhass@imagestream.com on Mon, Oct 15, 2001 at 08:53:14AM -0500 Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Oct 15, 2001 at 08:53:14AM -0500, Doug Hass wrote: > We are bound by third party agreements and are not allowed to release any > more free code (legally) than we already have. If we were not restricted > by SBS, Trillium, and Rockwell (among others), we would release all of the > code under GPL or lGPL. These agreements do NOT prevent us from working > with developers to support other platforms, though. It only prevents the > free release of portions of the code. Would your agreements allow you to provide resources to a small number of developers (under NDA and all that of course) to produce drivers that you would then release in binary form (eg a kernel module) under a free license? If you cannot release the source code to your drivers, can you release hardware programming specifications (again, perhaps under NDA) that allowed someone to develop an independant free licensed driver? -- Leo Bicknell - bicknell@ufp.org Systems Engineer - Internetworking Engineer - CCIE 3440 Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 8: 4:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id 6A46A37B407; Mon, 15 Oct 2001 08:04:32 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id KAA23801; Mon, 15 Oct 2001 10:04:04 -0500 Date: Mon, 15 Oct 2001 10:04:03 -0500 (EST) From: Doug Hass To: Leo Bicknell Cc: Ted Mittelstaedt , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen Subject: Re: FYI In-Reply-To: <20011015103507.B90657@ussenterprise.ufp.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Would your agreements allow you to provide resources to a small > number of developers (under NDA and all that of course) to produce > drivers that you would then release in binary form (eg a kernel > module) under a free license? It sure would. > If you cannot release the source code to your drivers, can you > release hardware programming specifications (again, perhaps under > NDA) that allowed someone to develop an independant free licensed > driver? Unfortunately, the API to the cards (the driver development kit, hardware programming specifications or whatever you want to call them) are licensed from several third parties and we are bound by agreement not to make them public. The 400 series cards (and, for that matter, the RISCom/N2 series cards) did not require an API, which is how BSDI and FreeBSD drivers came about in the first place. As I mentioned above, we CAN license the driver code and the DDK for development. This means that you could produce FreeBSD drivers which we could then distribute in a binary form under a free end-user license. Regards, Doug ----- Doug Hass ImageStream Internet Solutions dhass@imagestream.com http://www.imagestream.com Office: 1-219-935-8484 Fax: 1-219-935-8488 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 8:36:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id D407537B40A for ; Mon, 15 Oct 2001 08:36:04 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f9FFZxV04169; Mon, 15 Oct 2001 09:35:59 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f9FFZw722167; Mon, 15 Oct 2001 09:35:58 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110151535.f9FFZw722167@harmony.village.org> To: "Peter van Heusden" Subject: Re: Adding support for Duxbury PCI modem to FreeBSD 4.4 Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 15 Oct 2001 10:02:27 +0200." <9DCF7A9E7AD27A4F962A37F7E78607B10CFAEC@ukhokho.ct.schoolnet.org.za> References: <9DCF7A9E7AD27A4F962A37F7E78607B10CFAEC@ukhokho.ct.schoolnet.org.za> Date: Mon, 15 Oct 2001 09:35:58 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <9DCF7A9E7AD27A4F962A37F7E78607B10CFAEC@ukhokho.ct.schoolnet.org.za> "Peter van Heusden" writes: : I noticed that PCI modems are detected in /sys/isa/sio.c. I added the : chip : id of the modem to the list of PCI devices (pci_ids), and now : sio_pci_probe detects the modem, but the sioprobe() fails. Before I got : digging into the sioprobe code (which seems rather complex), I'd like to : verify that my pci_ids entry is correct. : : One thing I don't understand is the rid field of the pci_id structure. : Some modems have this set to 0x10, others to 0x14. I'm not sure what to : set it : to - how do I determine this? look for the I/o space bar. this will be the the ones in the range 0x10-0x24 that are odd (as in bit 0 is set). note, bars are 4 bytes long (except for some 64 bit cards, but you can safely ignore that). Alternatively, pciconf -r pciX:Y:Z 0x10:0x2f and post it to the list. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 8:49: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f166.law12.hotmail.com [64.4.19.166]) by hub.freebsd.org (Postfix) with ESMTP id A325737B40C for ; Mon, 15 Oct 2001 08:48:50 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 15 Oct 2001 08:48:50 -0700 Received: from 128.251.176.112 by lw12fd.law12.hotmail.msn.com with HTTP; Mon, 15 Oct 2001 15:48:50 GMT X-Originating-IP: [128.251.176.112] From: "=?iso-8859-1?B?RmFiaeFuIFNhbGFtYW5jYQ==?=" To: rminnich@lanl.gov, raysonlogin@yahoo.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: clustering code Date: Mon, 15 Oct 2001 10:48:50 -0500 Mime-Version: 1.0 Content-Type: text/html; charset=iso-8859-1 Message-ID: X-OriginalArrivalTime: 15 Oct 2001 15:48:50.0418 (UTC) FILETIME=[E2586520:01C15590] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG

Ok Ron, well you're right, a bunch-of-more code is not really useful, I'll check Plan 9, it seems it convinced you a little bit,  :-)

thanks, and regards,

Fabián

>From: Ronald G Minnich
>To: Rayson Ho
>CC: Fabián Salamanca ,
>Subject: Re: clustering code
>Date: Sun, 14 Oct 2001 21:21:58 -0600 (MDT)
>
>On Sun, 14 Oct 2001, Rayson Ho wrote:
>
> > http://ssic-linux.sourceforge.net/
>
>A collection of some really bad ideas, not likely to scale well. Note that
>they've got up to 30 nodes, wow. Double it once and that's where this kind
>of "global everything" idea starts to fall over. Badly.
>
>It would be neat to see freebsd do something really new and novel in
>clustering. ssci-linux is not it. It's going to be very hard to pick
>something new, a lot of the ground is well-trod.
>
>For other examples of what you can do (maybe not what you SHOULD do) see
>npaci ROCKS, OSCAR, and follow the references from there.
>
>On the should-do list, see plan 9 -- (on plan 9 I tend to sound like a
>broken record) read and understand the Plan 9 stuff, see how well it would
>work as a cluster technology (we have a 32-node plan 9 cluster here, it's
>quite cool), and see about bringing those neat ideas to freebsd.
>
>ron
>

Descargue GRATUITAMENTE MSN Explorer en http://explorer.msn.com
To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 8:57:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id BB79337B401; Mon, 15 Oct 2001 08:56:53 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id KAA29935; Mon, 15 Oct 2001 10:56:21 -0500 Date: Mon, 15 Oct 2001 10:56:21 -0500 (EST) From: Doug Hass To: Leo Bicknell Cc: Ted Mittelstaedt , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a private e-mail, Leo writes: > You offered a discount on these boards on the list. If you think there > is a real opportunity to sell these to the *BSD crowd, I recomend you > take that 15% (or some part of it) and offer to partially fund a driver > developer. There are many freelance programmers working on the project > who for $1000-$5000 (depending on complexity) could make your driver a > reality. A good developer could probably also make them work under > OpenBSD and NetBSD in one fell swoop. I'd be happy to pledge the 15% to a driver developer. That's a great idea! It will accomplish two objectives: 1) There will be at least 100 WANic 400 series cards available for purchase to support existing installations (assuming someone out there places the order). 2) ImageStream will pledge 15% of the purchase price of any lots of these 400 series cards toward porting of our SAND architecture to FreeBSD. That's a MINIMUM of $8,100 that ImageStream is willing to pay a developer or group of developers to port the drivers for the rest of the cards. Ted--you've indicated that there is a significant market for the 400 series cards in the community. Why don't you contact me privately and we'll get you an order of the cards so that we can accomplish the above. Regards, Doug ----- Doug Hass ImageStream Internet Solutions dhass@imagestream.com http://www.imagestream.com Office: 1-219-935-8484 Fax: 1-219-935-8488 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 9:10:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id 88F8937B406 for ; Mon, 15 Oct 2001 09:10:44 -0700 (PDT) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id f9FGAg433017; Mon, 15 Oct 2001 11:10:42 -0500 (CDT) (envelope-from tinguely) Date: Mon, 15 Oct 2001 11:10:42 -0500 (CDT) From: mark tinguely Message-Id: <200110151610.f9FGAg433017@web.cs.ndsu.nodak.edu> To: dillon@earth.backplane.com, tmoestl@gmx.net Subject: Re: contigfree, free what? Cc: freebsd-hackers@FreeBSD.ORG, Patrick.Cipiere@udcast.com, tinguely@web.cs.ndsu.nodak.edu In-Reply-To: <20011012204730.F407@crow.dom2ip.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a potentially silly question about contigmalloc1(), if the very unlikely occurance that the kernel VM space ran out, (the vm_map_findspace() failed) wouldn't we want to return the chunk of contiguous physical space back on the free queue before we return an allocation failure? --mark tinguely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 9:13:46 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 E97E837B407 for ; Mon, 15 Oct 2001 09:13:42 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f9FGDb854996; Mon, 15 Oct 2001 09:13:37 -0700 (PDT) (envelope-from dillon) Date: Mon, 15 Oct 2001 09:13:37 -0700 (PDT) From: Matt Dillon Message-Id: <200110151613.f9FGDb854996@earth.backplane.com> To: mark tinguely Cc: tmoestl@gmx.net, freebsd-hackers@FreeBSD.ORG, Patrick.Cipiere@udcast.com, tinguely@web.cs.ndsu.nodak.edu Subject: Re: contigfree, free what? References: <200110151610.f9FGAg433017@web.cs.ndsu.nodak.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :I have a potentially silly question about contigmalloc1(), if the very :unlikely occurance that the kernel VM space ran out, (the vm_map_findspace() :failed) wouldn't we want to return the chunk of contiguous physical space :back on the free queue before we return an allocation failure? : :--mark tinguely. Ah, you came across that XXX comment? You are absolutely right. The original implementor rushed writing the routine and didn't finish it. contigmalloc() is only supposed to be used in the early life of the system when its loading device drivers that need contiguous space, so the case is not supposed to come up. Of course, that means that it does come up from time to time :-(. If you want to have a go at fixing it I will be happy to review. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 9:22: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 4609837B407 for ; Mon, 15 Oct 2001 09:22:02 -0700 (PDT) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id MAA63597 for ; Mon, 15 Oct 2001 12:22:01 -0400 (EDT) Message-Id: <200110151622.MAA63597@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: debugging question Date: Mon, 15 Oct 2001 12:22:01 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I received the following from gdb today: #0 0x0 in ?? () #1 0x280a8d22 in svc_getreqset2 () from /usr/lib/libc.so.4 #2 0x280a8c5b in svc_getreqset () from /usr/lib/libc.so.4 #3 0x804c85f in yp_svc_run () #4 0x804cd94 in main () #5 0x8049a09 in _start () Uhm... I didn't think that was possible. I thought the kernel stored the last stack frame iteslf, from the SIG handler in kernel-space. -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 9:46:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id C820737B409 for ; Mon, 15 Oct 2001 09:46:18 -0700 (PDT) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id f9FGkGm33248; Mon, 15 Oct 2001 11:46:16 -0500 (CDT) (envelope-from tinguely) Date: Mon, 15 Oct 2001 11:46:16 -0500 (CDT) From: mark tinguely Message-Id: <200110151646.f9FGkGm33248@web.cs.ndsu.nodak.edu> To: dillon@earth.backplane.com, tinguely@web.cs.ndsu.nodak.edu Subject: Re: contigfree, free what? Cc: freebsd-hackers@FreeBSD.ORG, Patrick.Cipiere@udcast.com, tmoestl@gmx.net In-Reply-To: <200110151613.f9FGDb854996@earth.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Assuming we are using Thomas' patch that already removed the vm_page_wire() from the earlier for loop, then at the point of this VM space allocation failure, we haven't done anything too serious to the vm_page nor to the pmap, nor are they in any object. We should be able to simply place it back to the colored free list, something as easy as: *** vm_page.c Mon Oct 15 10:26:14 2001 --- vm_page.c.new Mon Oct 15 11:32:46 2001 *************** *** 1934,1939 **** --- 1934,1942 ---- * above available. */ vm_map_unlock(map); + for (i = start; i < (start + size / PAGE_SIZE); i++) { + (void)vm_add_new_page(VM_PAGE_TO_PHYS(&pga[i])); + } splx(s); return (NULL); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 10:24:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from navgwout.symantec.com (navgwout.symantec.com [198.6.49.12]) by hub.freebsd.org (Postfix) with ESMTP id 744CA37B40E for ; Mon, 15 Oct 2001 10:24:14 -0700 (PDT) Received: from navgwout.symantec.com (navgwout [198.6.49.12]) by navgwout.symantec.com (8.9.3+Sun/8.9.3) with SMTP id KAA26347 for ; Mon, 15 Oct 2001 10:24:14 -0700 (PDT) Received: from mailer.symantec.com ([198.6.49.176]) by navgwout.symantec.com (NAVGW 2.5.1.13) with SMTP id M2001101510241326432 ; Mon, 15 Oct 2001 10:24:13 -0700 Received: from uscu-smtp02.symantec.com (uscu-smtp02.symantec.com [155.64.74.114]) by mailer.symantec.com (8.9.3+Sun/8.9.3) with ESMTP id KAA12809; Mon, 15 Oct 2001 10:24:12 -0700 (PDT) Subject: Re: Severe I/O Problems To: Mikko Tyolajarvi Cc: hackers@freebsd.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Jay Rossiter" Date: Mon, 15 Oct 2001 10:21:35 -0700 X-MIMETrack: Serialize by Router on USCU-SMTP02/SYMSMTP(Release 5.0.8 |June 18, 2001) at 10/15/2001 10:16:58 AM MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG dmesg: atapci0: port 0xffa0-0xffaf at device 31= .1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 38146MB [77504/16/63] at ata0-master UDMA100 acd0: DVD-ROM at ata1-master using PIO4 sysctl: hw.ata.ata_dma: 1 hw.ata.wc: 0 hw.ata.tags: 0 hw.ata.atapi_dma: 0 hw.atamodes: dma,---,pio,---, mount: /dev/ad0s1a on / (ufs, local) /dev/ad0s1d on /home (ufs, local) /dev/ad0s1f on /usr (ufs, local) /dev/ad0s1h on /usr/ports (ufs, asynchronous, local) /dev/ad0s1g on /usr/src (ufs, asynchronous, local) /dev/ad0s1e on /var (ufs, local) All of the data work for this project is taking place on /home The writecache flag appeared as though it was going to help significant= ly, however the total run took about five hours longer than previous. (~21= hours) Start: Fri Oct 12 15:16:35 PDT 2001 Stop: Sat Oct 13 12:28:40 PDT 2001 = = =20 Mikko = = =20 Tyolajarvi To: jrossiter@symantec.com= = =20 Subject: Re: Severe I/O Pr= oblems = =20 = = =20 10/12/2001 = = =20 05:25 PM = = =20 = = =20 = = =20 In local.freebsd.hackers you write: >There appear to be a lot of changes that went into the filesystem and = I/O >code between 4.3 and 4.4. A little over a week ago I upgraded my 4.3 = box >to 4.4-STABLE and immediately I started having I/O slowdown. I do >development and QA on a program that is very I/O bound, but the change= s >between 4.3 and 4.4 aren't small enough that I can ignore them. >A few statistics: >BSD, P4 1.4GHz, ATA100 drives >- Normal test run on 4.3 was taking ~3 hours. >- Normal test run on 4.4 is taking 15-16 hours. >P3-800, ATA66 drives, SuSE Linux 7.1: >- Normal test run takes ~4.5 hours. >UltraSparc 10, Solaris 8, ATA66 drives: >- Normal test run takes ~6 hours. >As you can see, this jump was just phenomenal. Yup, sure looks bad. Post output from at least: % dmesg | grep ata % sysctl -a | grep ata % mount | grep ufs to give people something more to go on. $.02, /Mikko -- Mikko Ty=F6l=E4j=E4rvi_______________________________________mikko@rsasecurit= y.com RSA Security = To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 10:32:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 13D1537B401 for ; Mon, 15 Oct 2001 10:32:15 -0700 (PDT) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f9FHVmH33917; Mon, 15 Oct 2001 10:31:50 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Mon, 15 Oct 2001 10:31:48 -0700 (PDT) From: Matthew Jacob Reply-To: To: Jay Rossiter Cc: Mikko Tyolajarvi , Subject: Re: Severe I/O Problems In-Reply-To: Message-ID: <20011015103122.F29828-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well- that's good to know. WC helps you overall. That was my one idea. On Mon, 15 Oct 2001, Jay Rossiter wrote: > > dmesg: > atapci0: port 0xffa0-0xffaf at device 31.1 > on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ad0: 38146MB [77504/16/63] at ata0-master UDMA100 > acd0: DVD-ROM at ata1-master using PIO4 > > sysctl: > hw.ata.ata_dma: 1 > hw.ata.wc: 0 > hw.ata.tags: 0 > hw.ata.atapi_dma: 0 > hw.atamodes: dma,---,pio,---, > > mount: > /dev/ad0s1a on / (ufs, local) > /dev/ad0s1d on /home (ufs, local) > /dev/ad0s1f on /usr (ufs, local) > /dev/ad0s1h on /usr/ports (ufs, asynchronous, local) > /dev/ad0s1g on /usr/src (ufs, asynchronous, local) > /dev/ad0s1e on /var (ufs, local) > > All of the data work for this project is taking place on /home > > > The writecache flag appeared as though it was going to help significantly, > however the total run took about five hours longer than previous. (~21 > hours) > > Start: Fri Oct 12 15:16:35 PDT 2001 > Stop: Sat Oct 13 12:28:40 PDT 2001 > > > > > > > > > Mikko > Tyolajarvi To: jrossiter@symantec.com > e> Subject: Re: Severe I/O Problems > > 10/12/2001 > 05:25 PM > > > > > > > In local.freebsd.hackers you write: > > >There appear to be a lot of changes that went into the filesystem and I/O > >code between 4.3 and 4.4. A little over a week ago I upgraded my 4.3 box > >to 4.4-STABLE and immediately I started having I/O slowdown. I do > >development and QA on a program that is very I/O bound, but the changes > >between 4.3 and 4.4 aren't small enough that I can ignore them. > > >A few statistics: > > >BSD, P4 1.4GHz, ATA100 drives > >- Normal test run on 4.3 was taking ~3 hours. > >- Normal test run on 4.4 is taking 15-16 hours. > > >P3-800, ATA66 drives, SuSE Linux 7.1: > >- Normal test run takes ~4.5 hours. > > >UltraSparc 10, Solaris 8, ATA66 drives: > >- Normal test run takes ~6 hours. > > >As you can see, this jump was just phenomenal. > > Yup, sure looks bad. Post output from at least: > > % dmesg | grep ata > % sysctl -a | grep ata > % mount | grep ufs > > to give people something more to go on. > > $.02, > /Mikko > -- > Mikko > Työläjärvi_______________________________________mikko@rsasecurity.com > RSA Security > > > > > 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 Oct 15 11:13:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bgmail4.impsat.net.co (bgmail4.impsat.net.co [200.31.19.6]) by hub.freebsd.org (Postfix) with ESMTP id EA52C37B408 for ; Mon, 15 Oct 2001 11:13:49 -0700 (PDT) Received: from [206.114.11.102] (helo=oemcomputer) by bgmail4.impsat.net.co with smtp (Exim 3.16 #1) id 15tAFs-0003mJ-00 for freebsd-hackers@freebsd.org; Mon, 15 Oct 2001 11:06:16 -0500 Reply-To: From: " Rueda" To: Subject: =?iso-8859-1?Q?M=E1s_de_15.000_Empresas_a_su_disposici=F3n?= Date: Mon, 15 Oct 2001 11:04:19 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mensaje enviado por rueda@elsitio.net.co Empres@s - Colombia Potente Herramienta para Mercadeo y Ventas. Encuentre los clientes que usted necesita, con un simple click en nuestra base de datos de más de 15Mil Empresas Importantes de Colombia, con más de 70.000 directivos y ejecutivos. La Base de Datos y la Aplicación le permiten localizar y calificar sus mejores prospectos, aprender más sobre sus clientes, proveedores y competidores y crear eficientes campañas de correo, teléfono, e-mail, fax y campañas de campo. La Base de Datos de Empresas (más de 15Mil) maneja los siguientes campos: Razón Social, sigla, Nit, dirección, teléfono, fax, actividad empresarial (código CIIU Rev. 3.0), número de empleados, ciudad y departamento. La Base de Datos de directivos y ejecutivos (más de 70Mil) maneja los siguientes campos: nombre, cargo, area por cargos, dirección, teléfono, fax. Estas bases de datos se encuentran relacionadas, de tal forma que la aplicación hace búsquedas simples o complejas por todos estos campos, agrupa diferentes tipos de búsquedas, prepara e imprime reportes, rótulos y cartas, hace llamadas telefónicas y envía emailŽs. COMO VALOR AGREGADO le damos acceso a toda la información sobre COMERCIO EXTERIOR, a través de enlaces Vía Internet a las Bases de Datos de MINCOMEX (27000 Importadores), PROEXPO (4.000 Exportadores y sus ejecutivos), Y LA COMUNIDAD ANDINA. También le facilitamos la conexión a sus propios enlaces. Solicite información adicional vía email sobre contenido de la base de datos, fuentes de la información, actualización, funciones que permite ejecutar la aplicación, versiones, precios y empresas que la estan utilizando, o enviando los siguientes datos al Fax 6178102 - 6179073 Bogotá – Colombia o llamando directamente a Florentino Rueda, gerente comercial al Cel. 033-3396180 Empresa Nit Ciudad Dirección Teléfono Fax Nombre Cargo P.D. Si este mensaje no es de su interés, considere dirigirlo a la Gerencia General y/o Mercadeo, si no desea recibir mensajes como este, por favor déjenos saberlo a rueda@elsitio.net.co para eliminar su dirección en nuestra base de datos. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 15: 3:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mtiwmhc23.worldnet.att.net (mtiwmhc23.worldnet.att.net [204.127.131.48]) by hub.freebsd.org (Postfix) with ESMTP id 5ED9937B40C; Mon, 15 Oct 2001 15:03:39 -0700 (PDT) Received: from columbia ([12.93.212.132]) by mtiwmhc23.worldnet.att.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with SMTP id <20011015220337.RUXD6924.mtiwmhc23.worldnet.att.net@columbia>; Mon, 15 Oct 2001 22:03:37 +0000 From: "Andrew C. Hornback" To: "Doug Hass" , "Ted Mittelstaedt" Cc: "Jim Bryant" , "MurrayTaylor" , , , "Alfred Shippen" Subject: RE: FYI Date: Mon, 15 Oct 2001 17:58:33 -0400 Message-ID: <00fd01c155c4$8851d5a0$6600000a@columbia> 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 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 In-Reply-To: Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Doug Hass > Sent: Monday, October 15, 2001 9:53 AM > To: Ted Mittelstaedt > Cc: Jim Bryant; MurrayTaylor; freebsd-hackers@FreeBSD.ORG; > freebsd-questions@FreeBSD.ORG; Alfred Shippen > Subject: RE: FYI > > > And if you want to sell these to FreeBSD users then make your > Linux driver > > source (not the SAND stuff) available so that we can mod it into our own > > driver. Many other companies do this and as a matter of fact, > we (meaning > > FreeBSD) have even found bugs in crummy Linux drivers that have > been reported > > back to Linux and helped those manufacturers better their products. > > I'm not going to get dragged into an OS war. Both Linux and FreeBSD > have their share of "crummy" drivers and features. That discussion is > honestly beyond the scope of a discussion of ImageStream's SAND > architecture and the WANic 400 series. I don't believe Ted was trying to start an OS war, he's not that petty of a person. His point, and I hope that I'm not reading this incorrectly, is that FreeBSD not only has fixed problems with drivers released by hardware vendors, but also with drivers given over to "us" by the Linux group, as that was all that we had to work with when the hardware vendors have refused to provide any help whatsoever. [snip] > > No offense, but once Imagestream stopped selling WANic400's you > > ceased being an entity of interest to FreeBSD, as you no longer sell > > any products that run under it. > > I'll reiterate what I've said to you privately: ImageStream DID NOT make > the decision to discontinue the 400 series or the RISCom/N2 series. This > decision rested solely with SBS. > > However, FreeBSD users are NOT without options: > > 1) FreeBSD users can still get the WANic 400 and RISCom cards from the > second hand market, as another person mentioned. What is wrong with THIS picture? You're telling people to purchase used hardware, instead of purchasing components from your company? *shakes his head* > 2) WANic 400 series cards are still available in quantity. If the market > for FreeBSD is as large as you claim, then you or someone else in the > community should have no problem snapping up a quantity of these cards and > reselling them to interested parties. I'll go one step further: If anyone > contacts me about the WANic 400 series, mentions that they are for > FreeBSD, I promise to give an extra 15% discount over and above our normal > volume discounts just to illustrate my desire to support the FreeBSD > community. Perhaps a better idea, if I may be so bold, would be to offer samples of the newer cards (520 series, I believe they are) to FreeBSD developers interested in producing drivers, software and utilities for these cards. After all, you are saying that the 400 is EOL. Wouldn't the idea of engineering samples be more beneficial to all involved? > 3) Virtually ALL of our customers, save for OEMs making their own > products, purchase complete routers. Going this route would eliminate the > need to have FreeBSD support, as any user would have a standalone router. This sounds quite argumentative to me. Simply because everyone else is buying a router, there's a refusal to support FreeBSD, since people with "true routers" would have no need for using FreeBSD as a router engine. It's a vicious cycle that I believe we're seeing here... chicken and the egg, or rather, the driver and the market. Without a proper driver, there won't be a market for this card to be used with FreeBSD. However, without the manufacturer seeing visability in this market, there won't be a driver as it would be a waste of their developers time. --- Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 15:45:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id 25E3137B405; Mon, 15 Oct 2001 15:45:39 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id RAA08565; Mon, 15 Oct 2001 17:44:58 -0500 Date: Mon, 15 Oct 2001 17:44:57 -0500 (EST) From: Doug Hass To: "Andrew C. Hornback" Cc: Ted Mittelstaedt , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen Subject: RE: FYI In-Reply-To: <00fd01c155c4$8851d5a0$6600000a@columbia> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > 1) FreeBSD users can still get the WANic 400 and RISCom cards from the > > second hand market, as another person mentioned. > > What is wrong with THIS picture? You're telling people to purchase used > hardware, instead of purchasing components from your company? *shakes his > head* Perhaps you missed the earlier post. Someone posted about purchasing used gear or auction gear to "go it on the cheap" so to speak. Personally, I think wasting money on used, out-of-warranty, unsupported gear is akin to playing Russian Roulette with your money. I'd buy new every time. > > > 2) WANic 400 series cards are still available in quantity. If the market > > for FreeBSD is as large as you claim, then you or someone else in the > > community should have no problem snapping up a quantity of these cards and > > reselling them to interested parties. I'll go one step further: If anyone > > contacts me about the WANic 400 series, mentions that they are for > > FreeBSD, I promise to give an extra 15% discount over and above our normal > > volume discounts just to illustrate my desire to support the FreeBSD > > community. > > Perhaps a better idea, if I may be so bold, would be to offer samples of > the newer cards (520 series, I believe they are) to FreeBSD developers > interested in producing drivers, software and utilities for these cards. > After all, you are saying that the 400 is EOL. Wouldn't the idea of > engineering samples be more beneficial to all involved? Those have ALWAYS been available. My phone rings all day. I pick it up, and it's never a BSD developer wanting to order cards and port drivers. :-) All you have to do is ask. Driver source, demo cards, and development tools have been available to the BSD community since 1995. To date, only BSDI took up the effort, and only briefly. Where are all the FreeBSD developers and why aren't they beating down my door for these samples and code? I'll get back to this in a minute. > > 3) Virtually ALL of our customers, save for OEMs making their own > > products, purchase complete routers. Going this route would eliminate the > > need to have FreeBSD support, as any user would have a standalone router. > > This sounds quite argumentative to me. Simply because everyone else is > buying a router, there's a refusal to support FreeBSD, since people with > "true routers" would have no need for using FreeBSD as a router engine. Nope--it's just a matter of laying out the options. There are 4--buy used, buy new in quantity, and buy routers. You can also develop drivers for the "new" cards (they aren't new--they've been out for 3 years). > It's a vicious cycle that I believe we're seeing here... chicken and the > egg, or rather, the driver and the market. Without a proper driver, there > won't be a market for this card to be used with FreeBSD. However, without > the manufacturer seeing visability in this market, there won't be a driver > as it would be a waste of their developers time. It's not a vicious cycle at all. Ted has said repeatedly in earlier e-mails that there is a large market for the 400/405 and that discontinuing them was foolish. I've actually proposed a solution that solves both problems. I'll recap for those who missed my earlier message: 1) If the *BSD community has the 400 series cards in such high demand, someone should step up and order them in quantity. This solves the issue with the cards not being available in one and two unit quantities. You'll have a ready supply from someone in the community, and you'll be supporting the community when you buy the cards from them. 2) If someone from the FreeBSD community orders the cards, ImageStream will put up a minimum of $8,100 for a developer or developer group to port drivers for the rest of the cards. Actually, it's 15% of the purchase price of any 400 series cards. The more "in demand" the current cards are, the more money we'll pledge to make sure that FreeBSd drivers exist for ALL of the cards. My phone number is below. If these cards and the future of the drivers are as important as everyone who has posted says they are, let's move quickly toward a solution. Regards, Doug ----- Doug Hass ImageStream Internet Solutions dhass@imagestream.com http://www.imagestream.com Office: 1-219-935-8484 Fax: 1-219-935-8488 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 17: 6:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.plug.cx (kypo.alfred.cx [150.101.93.134]) by hub.freebsd.org (Postfix) with ESMTP id 3C45A37B407; Mon, 15 Oct 2001 17:06:53 -0700 (PDT) Received: by mail.plug.cx (Postfix, from userid 1000) id 13EF82B8BF; Tue, 16 Oct 2001 10:01:06 +0930 (CST) Date: Tue, 16 Oct 2001 10:01:06 +0930 From: Andrew Reid To: Dan Nelson Cc: j balan , freebsd-questions@FreeBSD.ORG, freebsd-hackers@freebsd.org Subject: Re: Network Startup Message-ID: <20011016100105.D12238@plug.cx> References: <200110152116.f9FLGsL51934@proscouting.com> <20011015162221.B8674@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011015162221.B8674@dan.emsphone.com>; from dnelson@allantgroup.com on Mon, Oct 15, 2001 at 04:22:21PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Oct 15, 2001 at 04:22:21PM -0500, Dan Nelson wrote: > In the last episode (Oct 15), j balan said: > > Does anyone know the command to reload rc.conf > > 'reboot' is the only sure way. That's a bit of a problem as far as I'm concerned. Perhaps the network scripts should be redesigned in a similar manner to the one taken on be RedHat. I started playing around with such a thing, using /usr/local/etc/rc.d/ as a base for 'network' scripts which take arguments such as 'start', 'stop' and 'restart'. Implementation of such a thing would be fairly trivial methinks. What are the thoughts on this sort of approach to management of network interfaces and ancillary services? - andrew -- void signature () { cout << "Andrew Reid -- andrew.reid@plug.cx" << endl; cout << "Cell: +61 401 946 813" << endl; cout << "Quidquid latine dictum sit, altum viditur" << endl; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 19:20:34 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 8627437B40D; Mon, 15 Oct 2001 19:20:28 -0700 (PDT) Received: (from dan@localhost) by dan.emsphone.com (8.11.6/8.11.6) id f9G2KIj85566; Mon, 15 Oct 2001 21:20:18 -0500 (CDT) (envelope-from dan) Date: Mon, 15 Oct 2001 21:20:17 -0500 From: Dan Nelson To: Andrew Reid Cc: j balan , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Network Startup Message-ID: <20011015212017.B73961@dan.emsphone.com> References: <200110152116.f9FLGsL51934@proscouting.com> <20011015162221.B8674@dan.emsphone.com> <20011016100105.D12238@plug.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011016100105.D12238@plug.cx> User-Agent: Mutt/1.3.23i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Oct 16), Andrew Reid said: > On Mon, Oct 15, 2001 at 04:22:21PM -0500, Dan Nelson wrote: > > In the last episode (Oct 15), j balan said: > > > Does anyone know the command to reload rc.conf > > > > 'reboot' is the only sure way. > > That's a bit of a problem as far as I'm concerned. Perhaps the network > scripts should be redesigned in a similar manner to the one taken on be > RedHat. Of course, you can always run the equivalent commands yourself to get the system in synch with what you put in rc.conf. i.e. if you added an alias ip to an interface, you can run ifconfig xxx inet 1.2.3.4 alias > I started playing around with such a thing, using usr/local/etc/rc.d/ > as a base for 'network' scripts which take arguments such as 'start', > 'stop' and 'restart'. > > Implementation of such a thing would be fairly trivial methinks. What > are the thoughts on this sort of approach to management of network > interfaces and ancillary services? Is it smart enough to only add the alias interface on "restart", or does it try to deconfigure the whole NIC, and add all the IPs back? How about if you change an IP number? Is it smart enough to kill and restart named, inetd, smbd, or any other programs that might have bound to that IP? It's not as simple as "I'll just rerun the ifconfig commands", and I stand by "reboot is the only sure way" :) -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 21:14:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.plug.cx (kypo.alfred.cx [150.101.93.134]) by hub.freebsd.org (Postfix) with ESMTP id 05F8D37B403; Mon, 15 Oct 2001 21:14:07 -0700 (PDT) Received: by mail.plug.cx (Postfix, from userid 1000) id A0B952B8BF; Tue, 16 Oct 2001 14:08:39 +0930 (CST) Date: Tue, 16 Oct 2001 14:08:38 +0930 From: Andrew Reid To: Dan Nelson Cc: Andrew Reid , j balan , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Network Startup Message-ID: <20011016140837.C12702@plug.cx> References: <200110152116.f9FLGsL51934@proscouting.com> <20011015162221.B8674@dan.emsphone.com> <20011016100105.D12238@plug.cx> <20011015212017.B73961@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011015212017.B73961@dan.emsphone.com>; from dnelson@allantgroup.com on Mon, Oct 15, 2001 at 09:20:17PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Oct 15, 2001 at 09:20:17PM -0500, Dan Nelson wrote: > > That's a bit of a problem as far as I'm concerned. Perhaps the network > > scripts should be redesigned in a similar manner to the one taken on be > > RedHat. > > Of course, you can always run the equivalent commands yourself to get > the system in synch with what you put in rc.conf. i.e. if you added an > alias ip to an interface, you can run > > ifconfig xxx inet 1.2.3.4 alias Oh, for sure. That's what I, and the majority of the community, do now. I think that it's not particularly convenient if you want to restart the network if you've got 3 or 4 network interfaces. > > I started playing around with such a thing, using usr/local/etc/rc.d/ > > as a base for 'network' scripts which take arguments such as 'start', > > 'stop' and 'restart'. > > > > Implementation of such a thing would be fairly trivial methinks. What > > are the thoughts on this sort of approach to management of network > > interfaces and ancillary services? > > Is it smart enough to only add the alias interface on "restart", or > does it try to deconfigure the whole NIC, and add all the IPs back? I've only gone as far as nuking the entire interface and bringing it all up again, including the alias. I've not tested the time difference between doing it the way it current does, and being 'smart' (as you say), and only configure the alias. However, if someone issues 'sh network.sh restart', I'd expect just that to happen -- the entire network to be restarted, not bits of it. Similarly, if I was to issue 'sh network.sh start rl0', I'd expect it to start the interface from scratch. Perhaps there is room there for some 'smartness' whereby the ifconfig commands are only issued if the current interface configuration is different to that in the configuration file. > How about if you change an IP number? Is it smart enough to kill and > restart named, inetd, smbd, or any other programs that might have bound > to that IP? It's not as simple as "I'll just rerun the ifconfig > commands", and I stand by "reboot is the only sure way" :) Perhaps it could be. For services that are controlled by /usr/local/etc/rc.d/*.sh, it mightn't be that hard. Control of inetd, named, smbd, or anything like that could also be done by a /usr/local/etc/rc.d/*.sh file. I can see this entire issue of startup scripts will spiral quickly into a larger task if it was decided that there needed to be a change in the way that the activity of other daemons such as inetd, named et al. were controlled. Then again, I don't consider such a change as a "bad thing". - andrew -- void signature () { cout << "Andrew Reid -- andrew.reid@plug.cx" << endl; cout << "Cell: +61 401 946 813" << endl; cout << "Quidquid latine dictum sit, altum viditur" << endl; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 23: 5:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 9493537B409; Mon, 15 Oct 2001 23:05:43 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9G65YT18415; Mon, 15 Oct 2001 23:05:34 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Andrew C. Hornback" , "Doug Hass" Cc: "Jim Bryant" , "MurrayTaylor" , , , "Alfred Shippen" Subject: RE: FYI Date: Mon, 15 Oct 2001 23:05:34 -0700 Message-ID: <000201c15608$9170cb20$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: <00fd01c155c4$8851d5a0$6600000a@columbia> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Andrew C. Hornback [mailto:achornback@worldnet.att.net] >Sent: Monday, October 15, 2001 2:59 PM >To: Doug Hass; Ted Mittelstaedt >Cc: Jim Bryant; MurrayTaylor; freebsd-hackers@FreeBSD.ORG; >freebsd-questions@FreeBSD.ORG; Alfred Shippen >Subject: RE: FYI > > >> -----Original Message----- >> From: owner-freebsd-questions@FreeBSD.ORG >> [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Doug Hass >> Sent: Monday, October 15, 2001 9:53 AM >> To: Ted Mittelstaedt >> Cc: Jim Bryant; MurrayTaylor; freebsd-hackers@FreeBSD.ORG; >> freebsd-questions@FreeBSD.ORG; Alfred Shippen >> Subject: RE: FYI >> >> > And if you want to sell these to FreeBSD users then make your >> Linux driver >> > source (not the SAND stuff) available so that we can mod it into our own >> > driver. Many other companies do this and as a matter of fact, >> we (meaning >> > FreeBSD) have even found bugs in crummy Linux drivers that have >> been reported >> > back to Linux and helped those manufacturers better their products. >> >> I'm not going to get dragged into an OS war. Both Linux and FreeBSD >> have their share of "crummy" drivers and features. That discussion is >> honestly beyond the scope of a discussion of ImageStream's SAND >> architecture and the WANic 400 series. > > I don't believe Ted was trying to start an OS war, he's not >that petty of a >person. been there, done that. :-) No, it's not an OS war, just trying to illustrate why making source available is a Good Thing. His point, and I hope that I'm not reading this incorrectly, is >that FreeBSD not only has fixed problems with drivers released by hardware >vendors, but also with drivers given over to "us" by the Linux group, as >that was all that we had to work with when the hardware vendors have refused >to provide any help whatsoever. > correct. >[snip] > >> > No offense, but once Imagestream stopped selling WANic400's you >> > ceased being an entity of interest to FreeBSD, as you no longer sell >> > any products that run under it. >> >> I'll reiterate what I've said to you privately: ImageStream DID NOT make >> the decision to discontinue the 400 series or the RISCom/N2 series. This >> decision rested solely with SBS. >> >> However, FreeBSD users are NOT without options: >> >> 1) FreeBSD users can still get the WANic 400 and RISCom cards from the >> second hand market, as another person mentioned. > > What is wrong with THIS picture? You're telling people to >purchase used >hardware, instead of purchasing components from your company? *shakes his >head* > I'll point out that the "1000 cards closed out" is not "used" hardware, it's brand new stuff that's never been opened. This is quite common in the hardware industry. The difficulty is finding out who that highest bidder was and if they are going to use those 1000 cards for themselves or are going to sell them off in dribs and drabs over the next 10 years. >> 2) WANic 400 series cards are still available in quantity. If the market >> for FreeBSD is as large as you claim, then you or someone else in the >> community should have no problem snapping up a quantity of these cards and >> reselling them to interested parties. I'll go one step further: If anyone >> contacts me about the WANic 400 series, mentions that they are for >> FreeBSD, I promise to give an extra 15% discount over and above our normal >> volume discounts just to illustrate my desire to support the FreeBSD >> community. > > Perhaps a better idea, if I may be so bold, would be to offer >samples of >the newer cards (520 series, I believe they are) to FreeBSD developers >interested in producing drivers, software and utilities for these cards. >After all, you are saying that the 400 is EOL. Wouldn't the idea of >engineering samples be more beneficial to all involved? > Just about every hardware vendor is happy to provide samples to developers, anyone working on this would get plenty of support. >> 3) Virtually ALL of our customers, save for OEMs making their own >> products, purchase complete routers. Going this route would eliminate the >> need to have FreeBSD support, as any user would have a standalone router. > > This sounds quite argumentative to me. Simply because >everyone else is >buying a router, there's a refusal to support FreeBSD, since people with >"true routers" would have no need for using FreeBSD as a router engine. > No company is going to support a product that has no market, and it's reasonable to ask who would buy these cards since Cisco's are so cheap on the seconds market. > It's a vicious cycle that I believe we're seeing here... >chicken and the >egg, or rather, the driver and the market. Without a proper driver, there >won't be a market for this card to be used with FreeBSD. However, without >the manufacturer seeing visability in this market, there won't be a driver >as it would be a waste of their developers time. > This is the truth for commercial projects. Open Source drivers, on the other hand, operate somewhat differently. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 23: 7:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from the-7.net (the-7.net [211.232.190.152]) by hub.freebsd.org (Postfix) with ESMTP id 3992D37B40C for ; Mon, 15 Oct 2001 23:07:20 -0700 (PDT) Received: (from ab@localhost) by the-7.net (8.11.6/8.11.6) id f9G5gIJ35225 for freebsd-hackers@freebsd.org; Tue, 16 Oct 2001 14:42:18 +0900 (KST) (envelope-from ab) Date: Tue, 16 Oct 2001 14:42:17 +0900 From: "Eugene M. Kim" To: freebsd-hackers@freebsd.org Subject: contigmalloc + contigfree = memory leak? Message-ID: <20011016144217.A35188@the-7.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greetings, QUESTION: Does contigfree() really free up memory allocated using contigmalloc()? BACKGROUND: I've been trying to make up a kmod that allocates/deallocates memory in a specific physical address range. Mike Smith suggested using busdma functions to do the job, so I followed it. After allocating and deallocating memory several times, it seemed that bus_dmamem_free() was not freeing the memory properly. I looked at busdma_machdep.c where bus_dmamem_free() was defined, and found: void bus_dmamem_free(bus_dma_tag_t dmat, void *vaddr, bus_dmamap_t map) { /* * dmamem does not need to be bounced, so the map should be * NULL */ if (map != NULL) panic("bus_dmamem_free: Invalid map freed\n"); /* XXX There is no "contigfree" and "free" doesn't work */ if ((dmat->maxsize <= PAGE_SIZE) && dmat->lowaddr >= ptoa(Maxmem)) free(vaddr, M_DEVBUF); } However, there *is* contigfree() and a related patch was applied on -current around August, so I did the same thing (adding an else clause to call contigfree(vaddr, dmat->maxsize, M_DEVBUF)). It didn't solve the memory leak problem either, so I'm stuck here... Could anyone shed a light on this? Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 15 23:29:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from alicia.nttmcl.com (alicia.nttmcl.com [216.69.69.10]) by hub.freebsd.org (Postfix) with ESMTP id 91B5837B408 for ; Mon, 15 Oct 2001 23:29:35 -0700 (PDT) Received: (from gene@localhost) by alicia.nttmcl.com (8.10.1/8.10.1) id f9G6TWS15698; Mon, 15 Oct 2001 23:29:32 -0700 (PDT) Date: Mon, 15 Oct 2001 23:29:32 -0700 From: "Eugene M. Kim" To: "Eugene M. Kim" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: contigmalloc + contigfree = memory leak? Message-ID: <20011015232932.A15142@alicia.nttmcl.com> References: <20011016144217.A35188@the-7.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20011016144217.A35188@the-7.net>; from ab@astralblue.net on Tue, Oct 16, 2001 at 02:42:17PM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Oops, I'm sorry for the self-reply. Just found a highly helpful thread posted from 11th (`contigfree, free what?'), so please disregard my message. /me bonks his head against a wall that says `mea culpa' Thanks, Eugene On Tue, Oct 16, 2001 at 02:42:17PM +0900, Eugene M. Kim wrote: > > > Greetings, > > QUESTION: > Does contigfree() really free up memory allocated using contigmalloc()? > > BACKGROUND: > I've been trying to make up a kmod that allocates/deallocates memory in > a specific physical address range. Mike Smith suggested using busdma > functions to do the job, so I followed it. > > After allocating and deallocating memory several times, it seemed that > bus_dmamem_free() was not freeing the memory properly. I looked at > busdma_machdep.c where bus_dmamem_free() was defined, and found: > > void > bus_dmamem_free(bus_dma_tag_t dmat, void *vaddr, bus_dmamap_t map) > { > /* > * dmamem does not need to be bounced, so the map should be > * NULL > */ > if (map != NULL) > panic("bus_dmamem_free: Invalid map freed\n"); > /* XXX There is no "contigfree" and "free" doesn't work */ > if ((dmat->maxsize <= PAGE_SIZE) && dmat->lowaddr >= ptoa(Maxmem)) > free(vaddr, M_DEVBUF); > } > > However, there *is* contigfree() and a related patch was applied on > -current around August, so I did the same thing (adding an else clause > to call contigfree(vaddr, dmat->maxsize, M_DEVBUF)). > > It didn't solve the memory leak problem either, so I'm stuck here... > > Could anyone shed a light on this? > > Regards, > Eugene > > 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 Oct 16 0:34:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id C1FCD37B407; Tue, 16 Oct 2001 00:34:22 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9G7YET18562; Tue, 16 Oct 2001 00:34:14 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Doug Hass" Cc: "Jim Bryant" , "MurrayTaylor" , , , "Alfred Shippen" Subject: RE: FYI Date: Tue, 16 Oct 2001 00:34:12 -0700 Message-ID: <000301c15614$f30c78a0$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Doug Hass [mailto:dhass@imagestream.com] >Sent: Monday, October 15, 2001 6:53 AM >To: Ted Mittelstaedt >Cc: Jim Bryant; MurrayTaylor; freebsd-hackers@FreeBSD.ORG; >freebsd-questions@FreeBSD.ORG; Alfred Shippen >Subject: RE: FYI > Hi Doug, I'm going to address myself to these points openly as there's some points here which we all need to be familiar with. > >We are bound by third party agreements and are not allowed to release any >more free code (legally) than we already have. If we were not restricted >by SBS, Trillium, and Rockwell (among others), we would release all of the >code under GPL or lGPL. These agreements do NOT prevent us from working >with developers to support other platforms, though. It only prevents the >free release of portions of the code. > You said in a mail to Leo, the following: "Unfortunately, the API to the cards (the driver development kit, hardware programming specifications or whatever you want to call them) are licensed from several third parties and we are bound by agreement not to make them public." I'm going to assume that the programming specs you refer to here are what is being licensed from SBS, Trillium, and Rockwell, because either Rockwell or Trillium is the actual manufacturer of the sync chip. I'll assume that SBS is just making the support chips on the board and the interface chips to the PCI bus. Now, let me discuss for a moment how the current Imagestream WAN drivers operate. (based on my reading of the public code, which of course may be incorrect) Please feel free to interject where you feel I'm full of crap. :-) The "hardware API" or the actual register interface code, is a binary-only module that is "snapped in" to SAND. SAND is GPL and is similar to the FreeBSD Netgraph module - it provides all the higher-level protocol stuff, like Frame Relay, PPP, HDLC, and such. SAND goes between the OS TCP/IP stack and that binary only module. Imagestream has no problem releasing SAND for public consumption basically because all that PPP/HDLC/Frame and other datalink code is already available, PPP code has been available for time out of mind from many places, (including BSD) long before Imagestream ever wrote SAND, and Cisco HDLC was reverse-engineered some time ago (Besides that, Cisco gave up trying to hide their HDLC interface once Wellfleet/Bay Networks died) Obviously, Imagestream had to do some work, but I'd say a lot of it was in the area of supporting these binary snap in modules. The reason that Imagestream went this road is that like Doug said, all those hardware vendors like Rockwell think that there's something valuable in a pure register interface spec publication for their products. So, this way Imagestream can sign their souls away to get access to that interface spec - but they isolate all that contaminated code in this binary snap-in module. It's a hack of a solution but unfortunately is getting more and more common under UNIX because the Linux people have caved in and are busily screwing their own principles of GPL, by soliciting ever greater amounts of closed-source, Linux code. Imagestream isn't the only one out there doing this. Now, you can make all the technical arguments you want about how a modularized development environment like this allows code reuse and this is quite true - but you must keep in mind that SAND's modularized development has a primary goal of being able to keep the contaminated code in the driver snap-in modules, code reuse is secondary. There's other modularized driver development models in which EVERYTHING is publically available including the modules. >That being said, we're always interested in supporting a wide variety of >platforms. Without the SAND architecture, though, there really is little >hope of having FreeBSD support for the WANic 520 series cards (or other >cards, for that matter). This is correct and incorrect. It's correct because what Imagestream wants to have to be able to easily graft in FreeBSD to their supported UNIX os's is SAND - if done right then the actual driver module itself would have trivial changes whether used on FreeBSD or Linux, so you don't have to do much other than keep SAND maintained in FreeBSD. It's incorrect because it's perfectly possible to write a monolithic driver under FreeBSD that's only available as an object module and instead links in to the FreeBSD answer to SAND - which is Netgraph. This is exactly how the WANic 400 driver is now. (except of course the WANic 4xx driver is source available) Of course, this object module will have to be recompiled for every new version of FreeBSD, because it has to either be mod-loaded into the kernel or statically compiled into it. It's a rather icky proposition for a company like Imagestream to contemplate from a support perspective. But it certainly is NOT impossible. >If there are developers in the community >interested in porting SAND and the various hardware modules (for the 520 >series and other cards) to FreeBSD, we'll be happy to work with them and >support that effort. It is in ALL of our interests to have the widest >support for standards-based technologies as possible. > But you see that in this area SAND is no more standard than Netgraph is. SAND provides Linux users that run WANic cards a lot of stuff - but it is GPL which makes it difficult to use in many commercial FreeBSD projects. It's been discussed to death in this forum before but the worst possible thing that Imagestream could have done was to put SAND under GPL. If you had simply put it under BSD license then BOTH the BSD and Linux people could have used it, in fact Netgraph may have never been written, and a lot of other commercial UNIX's might have used it too (like Apple's MacOS X) >> No offense, but once Imagestream stopped selling WANic400's you >> ceased being an entity of interest to FreeBSD, as you no longer sell >> any products that run under it. > >I'll reiterate what I've said to you privately: ImageStream DID NOT make >the decision to discontinue the 400 series or the RISCom/N2 series. This >decision rested solely with SBS. > I believe you, I believe you. But, did the decision makers at SBS even know that the BSD community currently can't use the 500 series and above? And that discontinuting it would cut out that section of their market? Did you guys know that? >However, FreeBSD users are NOT without options: > >1) FreeBSD users can still get the WANic 400 and RISCom cards from the >second hand market, as another person mentioned. > Doug, in this last year alone I've bought about $20K worth of miscellaneous networking crap off Ebay for resale to our customers and other purposes. (keep in mind I hold the technical reins to an ISP and we will do what it takes to get a customer connected to us - and a lot of times that involves getting them a cheap router off Ebay because they cannot afford anything more than a $200 router. And you would have nightmares if you saw what kind of router that $200 fetches. :-)) I've had enough experience with the used networking market to say what I'm going to say here. During that time I've seen WANic or RISCom cards come up for bid exactly SIX times. And, THREE of the times I was the sole bidder and bought them. The other three times, well one was a 56K card, another the seller wanted $500 (hah) and the other the seller wanted another rediculous amount. During that time I've also kept tabs on what the commercial networking resale vendors that I also buy from have been doing and I've not seen anything at all marked RISCom, WANic, or Imagestream. I hope very much that the dump of cards on the market in September will eventually percolate down. But I don't believe that the second's market will be a significant source of WANic 400's anytime soon if ever, and here is why: 1) The cards are almost impossible to identify if they are just loose with no documentation. Some vendors slap their moniker in unmistakable letters across all their cards, SDL/SBS and you guys never did. Understand that the level of people that break up old PC's and sell them for scrap is barely above that of your average parts-puller in any auto wrecking yard. What they can't understand or identify they break while going after what they can identify. I very much doubt that an old WANic or RISCom card will make it through these people if it's inside an old PC that's scrapped out. They will probably toss it in the garbage along with that "weird cable with that screwy rectangular connector on it" 2) The price drop going from the closeout auction sale to the actual market cost is too great for most dealers to take. What I mean by this is that right now, someone is sitting on a stack of 1000 WANic cards that they spend $100K for, with stars in their eyes thinking of how they can make a half million dollars by selling them on the second's market for $500 apiece. What they don't understand is that the best sale price they might get for a closed-out WANic 405 now (since the vendor is no longer making the card) is about $20, $30 if they include a cable. Unless SBS closed out that 1000 cards for $10K, and included boxes and manuals with every card, whatever dealer or company that bought them is going to get totally screwed if they attempt to unload them on the used market. It's going to take that company several years to understand this, and by the time they are willing to write off the $10K, nobody is going to know what the cards are anymore and they will probably be pitched in the trash. 3) In my opinion, about 30% of computer and networking hardware is scrapped because it's broken. That leaves 70% of scrapped gear re-usable. My gut feeling is that the second's market sees about 30% of this. This means that the majority of scrapped WANic 4xx cards will never get near the seconds market, they are going to be pperfectly good, operating cards that are going to go straight to the landfill. Simply due to the percentages, while 1000 cards dumped on the seconds market SEEMS a lot, it's a drop in the bucket of the total amount of computer and networking gear that shows up in the second's market. The seconds market is great when it comes to handling computer gear that was once widely used and very popular. It's horrible at handling gear that is very, very narrowly targeted. And it's not just computers that are like this, many other second's markets operate the same way. >2) WANic 400 series cards are still available in quantity. If the market >for FreeBSD is as large as you claim, then you or someone else in the >community should have no problem snapping up a quantity of these cards and >reselling them to interested parties. As you know, price determines everything. At $777 per WANic405, you elected NOT to purchase 100 of them from SBS and just warehouse them. (I'll assume that your probably paying at least $500 per card, which is $50K for that quantity of 100) If SBS is going to continue to have that offer of they will sell them to you at lots of 100, why then in your shoes I'd make the same decision, because with SBS dumping 1000 of the cards on the used market, you could be putting $50K into a white elephant. I mean, if you sell 100 WANic cards a year, why then if SBS dumped 1000 of them, that's a 10 year supply floating around out there. Surely, if a few years go by and the dumped WANic 405's don't show up on the seconds market, you could then perhaps assume that someone screwed up and pitched the lot of them into a Dumpster, and it might then be safe to consider investing that $50K into a batch of 100 of them. Now, if SBS is willing to do a lot of 100 cards at a wholesale price of, say $50 dollars a card, then I and a lot of other people could probably round up 100 sales very quickly at $100 per card. But I'll stop there because I know that all this is marketing and the technical people on the mailing list are probably asleep by now. :-) I'll go one step further: If anyone >contacts me about the WANic 400 series, mentions that they are for >FreeBSD, I promise to give an extra 15% discount over and above our normal >volume discounts just to illustrate my desire to support the FreeBSD >community. > This is a kind offer but you have to put some pricing to it. If your only selling them in lots of 100 cards, at the price on your website of $777 per card, that's 15% off a $77K sale. I'd guess that your volume discounts would drop that $77K quite a bit - but still out of reach of an individual company, of course. But this is all academic marketing of course - because at those dollar levels, it's far cheaper to simply pay a developer to write FreeBSD drivers for the WANic 5xx series of cards and deal with the licensing issues. >3) Virtually ALL of our customers, save for OEMs making their own >products, purchase complete routers. Going this route would eliminate the >need to have FreeBSD support, as any user would have a standalone router. > Remember, your talking to a bunch of FreeBSD people here, they might not want a router based on Linux. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 1: 5: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 61AD737B408; Tue, 16 Oct 2001 01:05:00 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9G84pT18615; Tue, 16 Oct 2001 01:04:51 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Doug Hass" , "Leo Bicknell" Cc: "Jim Bryant" , "MurrayTaylor" , , , "Alfred Shippen" Subject: RE: FYI Date: Tue, 16 Oct 2001 01:04:51 -0700 Message-ID: <000501c15619$3b30a760$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Doug Hass [mailto:dhass@imagestream.com] >Sent: Monday, October 15, 2001 8:04 AM >To: Leo Bicknell >Cc: Ted Mittelstaedt; Jim Bryant; MurrayTaylor; >freebsd-hackers@FreeBSD.ORG; freebsd-questions@FreeBSD.ORG; Alfred >Shippen >Subject: Re: FYI > > >> Would your agreements allow you to provide resources to a small >> number of developers (under NDA and all that of course) to produce >> drivers that you would then release in binary form (eg a kernel >> module) under a free license? > >It sure would. > >> If you cannot release the source code to your drivers, can you >> release hardware programming specifications (again, perhaps under >> NDA) that allowed someone to develop an independant free licensed >> driver? > >Unfortunately, the API to the cards (the driver development kit, hardware >programming specifications or whatever you want to call them) are licensed >from several third parties and we are bound by agreement not to make them >public. The 400 series cards (and, for that matter, the RISCom/N2 series >cards) did not require an API, which is how BSDI and FreeBSD drivers came >about in the first place. > >As I mentioned above, we CAN license the driver code and the DDK for >development. This means that you could produce FreeBSD drivers which we >could then distribute in a binary form under a free end-user license. > Frankly this is the only way I can see that FreeBSD drivers for the 5xx series would ever come about. Porting SAND over, while having advantages of long term support, is just overkill for this, besides which it's unlikely you will get a FreeBSD developer to work on GPL code. This would end up putting a WANic 5xx driver into the same status as the drivers for the Emerging Technologies, or Sangoma sync cards, which both come with binary-only FreeBSD drivers. It would actually have a leg up over those drivers because it would have Netgraph hooks and I believe that the Sangoma drivers don't (but I've never worked with the Sangoma cards so I don't know for certain) If the register interface to the 5xx cards wasn't tremendously different than the 4xx cards then the sr driver would be a good skeleton to start with. While the offer of the DDK is nice, my guess is most of the code in it is for making SAND modules. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 1:12:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 6D12637B40B; Tue, 16 Oct 2001 01:12:07 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9G8BxT18638; Tue, 16 Oct 2001 01:12:00 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Doug Hass" , "Leo Bicknell" Cc: "Jim Bryant" , "MurrayTaylor" , , Subject: RE: FYI Date: Tue, 16 Oct 2001 01:11:59 -0700 Message-ID: <000601c1561a$3acf7f20$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Doug Hass [mailto:dhass@imagestream.com] >Sent: Monday, October 15, 2001 8:56 AM >To: Leo Bicknell >Cc: Ted Mittelstaedt; Jim Bryant; MurrayTaylor; >freebsd-hackers@FreeBSD.ORG; freebsd-questions@FreeBSD.ORG >Subject: Re: FYI > > >In a private e-mail, Leo writes: > >> You offered a discount on these boards on the list. If you think there >> is a real opportunity to sell these to the *BSD crowd, I recomend you >> take that 15% (or some part of it) and offer to partially fund a driver >> developer. There are many freelance programmers working on the project >> who for $1000-$5000 (depending on complexity) could make your driver a >> reality. A good developer could probably also make them work under >> OpenBSD and NetBSD in one fell swoop. > >I'd be happy to pledge the 15% to a driver developer. That's a >great idea! It will accomplish two objectives: > >1) There will be at least 100 WANic 400 series cards available for >purchase to support existing installations (assuming someone out there >places the order). > >2) ImageStream will pledge 15% of the purchase price of any lots of these >400 series cards toward porting of our SAND architecture to FreeBSD. >That's a MINIMUM of $8,100 that ImageStream is willing to pay a developer >or group of developers to port the drivers for the rest of the cards. > >Ted--you've indicated that there is a significant market for the 400 >series cards in the community. There is depending on the price. I'll freely admit however that I have not priced the competitive serial sync cards that are currently supported under FreeBSD, so I don't know how the WANic 400 or 500 stacks up against them. For all I know right now there's someone just bringing a T1 interface card to the market with integrated CSU that sells for $30 per card which would make this entire discussion moot. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 1:26:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from frere.schoolnet.org.za (frere.schoolnet.org.za [196.14.22.12]) by hub.freebsd.org (Postfix) with ESMTP id AD92A37B405 for ; Tue, 16 Oct 2001 01:26:37 -0700 (PDT) Received: from pvh by frere.schoolnet.org.za with local (Exim 3.16 #2) id 15tPYH-0000CS-00 for freebsd-hackers@FreeBSD.ORG; Tue, 16 Oct 2001 10:26:17 +0200 Date: Tue, 16 Oct 2001 10:26:17 +0200 From: Peter van Heusden To: freebsd-hackers@FreeBSD.ORG Subject: Re: Adding support for Duxbury PCI modem to FreeBSD 4.4 Message-ID: <20011016102617.A28699@schoolnet.org.za> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <9DCF7A9E7AD27A4F962A37F7E78607B10CFAEC@ukhokho.ct.schoolnet.org.za> <200110151535.f9FFZw722167@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200110151535.f9FFZw722167@harmony.village.org> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Oct 15, 2001 at 09:35:58AM -0600, Warner Losh wrote: > In message <9DCF7A9E7AD27A4F962A37F7E78607B10CFAEC@ukhokho.ct.schoolnet.org.za> "Peter van Heusden" writes: > : I noticed that PCI modems are detected in /sys/isa/sio.c. I added the > : chip > : id of the modem to the list of PCI devices (pci_ids), and now > : sio_pci_probe detects the modem, but the sioprobe() fails. Before I got > : digging into the sioprobe code (which seems rather complex), I'd like to > : verify that my pci_ids entry is correct. > : > : One thing I don't understand is the rid field of the pci_id structure. > : Some modems have this set to 0x10, others to 0x14. I'm not sure what to > : set it > : to - how do I determine this? > > look for the I/o space bar. this will be the the ones in the range > 0x10-0x24 that are odd (as in bit 0 is set). note, bars are 4 bytes > long (except for some 64 bit cards, but you can safely ignore that). > > Alternatively, > pciconf -r pciX:Y:Z 0x10:0x2f > and post it to the list. Thanks, Warner, but on further investigation, I discovered that the Duxbury modem is actually a re-branded Motorola SM56 - i.e. a WinModem. No wonder it doesn't work. Aaarrgh! I'm having a look at the Linux 2.4 kernel code, since they apparently have winmodem support (including for the SM56 chipset, which is now no longer supported by Motorola - double Aaaargh!), but will probably have to go with an external modem, since it seems to be impossible to get internal PCI non-winmodems. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 2:43: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from straylight.ringlet.net (straylight.ringlet.net [217.75.134.254]) by hub.freebsd.org (Postfix) with SMTP id 8D49C37B411 for ; Tue, 16 Oct 2001 02:42:53 -0700 (PDT) Received: (qmail 6003 invoked by uid 1000); 16 Oct 2001 09:42:20 -0000 Date: Tue, 16 Oct 2001 12:42:20 +0300 From: Peter Pentchev To: Andrew Reid Cc: Dan Nelson , j balan , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Network Startup Message-ID: <20011016124220.A727@straylight.oblivion.bg> Mail-Followup-To: Andrew Reid , Dan Nelson , j balan , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: <200110152116.f9FLGsL51934@proscouting.com> <20011015162221.B8674@dan.emsphone.com> <20011016100105.D12238@plug.cx> <20011015212017.B73961@dan.emsphone.com> <20011016140837.C12702@plug.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011016140837.C12702@plug.cx>; from andrew.reid@plug.cx on Tue, Oct 16, 2001 at 02:08:38PM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Oct 16, 2001 at 02:08:38PM +0930, Andrew Reid wrote: > On Mon, Oct 15, 2001 at 09:20:17PM -0500, Dan Nelson wrote: > > > > That's a bit of a problem as far as I'm concerned. Perhaps the network > > > scripts should be redesigned in a similar manner to the one taken on be > > > RedHat. > > > > Of course, you can always run the equivalent commands yourself to get > > the system in synch with what you put in rc.conf. i.e. if you added an > > alias ip to an interface, you can run > > > > ifconfig xxx inet 1.2.3.4 alias > > Oh, for sure. That's what I, and the majority of the community, do > now. I think that it's not particularly convenient if you want to > restart the network if you've got 3 or 4 network interfaces. Are you aware of the existence of /etc/netstart? I wasn't, until very recently :) G'luck, Peter -- Hey, out there - is it *you* reading me, or is it someone else? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 5:32:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts9-srv.bellnexxia.net (tomts9.bellnexxia.net [209.226.175.53]) by hub.freebsd.org (Postfix) with ESMTP id 4D8AF37B40D for ; Tue, 16 Oct 2001 05:32:27 -0700 (PDT) Received: from xena.gsicomp.on.ca ([65.93.39.114]) by tomts9-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20011016123226.XBH19094.tomts9-srv.bellnexxia.net@xena.gsicomp.on.ca>; Tue, 16 Oct 2001 08:32:26 -0400 Received: from localhost (matt@localhost) by xena.gsicomp.on.ca (8.11.1/8.11.1) with ESMTP id f9GCOAe16691; Tue, 16 Oct 2001 08:24:10 -0400 (EDT) (envelope-from matt@xena.gsicomp.on.ca) Date: Tue, 16 Oct 2001 08:24:10 -0400 (EDT) From: Matthew Emmerton To: Peter van Heusden Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Adding support for Duxbury PCI modem to FreeBSD 4.4 In-Reply-To: <20011016102617.A28699@schoolnet.org.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 16 Oct 2001, Peter van Heusden wrote: > On Mon, Oct 15, 2001 at 09:35:58AM -0600, Warner Losh wrote: > > In message <9DCF7A9E7AD27A4F962A37F7E78607B10CFAEC@ukhokho.ct.schoolnet.org.za> "Peter van Heusden" writes: > > I'm having a look at the Linux 2.4 kernel code, since they apparently > have winmodem support (including for the SM56 chipset, which is now > no longer supported by Motorola - double Aaaargh!), but will probably > have to go with an external modem, since it seems to be impossible to > get internal PCI non-winmodems. 3Com makes a PCI "hardware" (non-Winmodem) modem. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 7: 5:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cc-gw.1anetworks.net (cc-gw.1anetworks.net [193.243.179.83]) by hub.freebsd.org (Postfix) with SMTP id 647B037B409 for ; Tue, 16 Oct 2001 07:05:53 -0700 (PDT) Received: from brian (brian.1anetworks.net [212.36.98.200]) by parma.1anetworks.net (8.9.3+Sun/8.9.3) with SMTP id PAA20364 for ; Tue, 16 Oct 2001 15:05:50 +0100 (BST) From: "Bri" To: Subject: FreeBSD 4.4-RELEASE - question reguarding 3COM 900TPO 10Mbps net card. Date: Tue, 16 Oct 2001 15:22:37 +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.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi I was previously using FreeBSD 4.2 RELEASE and it ran stable but since I've made a new install on the system on the new hard drive I've put 4.4 RELEASE on the new hard drive and the new Promise TX-2 controller which are both working fine but after 4 or so days the 3COM 900TPO network card on xl0 die's after around this time I know it die's because the light blacks out on the hub and the system then becomes locked up and then it reboots and comes back in ok and a FreeBSD reinitializes the network card again without the need to completely turn off the system. And everything is fine for another 4 days.... any suggestions that would help are appreciated Thanks Bri, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" 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 Oct 16 7:26:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id BEA6E37B408; Tue, 16 Oct 2001 07:26:39 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id JAA19837; Tue, 16 Oct 2001 09:26:17 -0500 Date: Tue, 16 Oct 2001 09:26:17 -0500 (EST) From: Doug Hass To: Ted Mittelstaedt Cc: Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen Subject: RE: FYI In-Reply-To: <000301c15614$f30c78a0$1401a8c0@tedm.placo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > The "hardware API" or the actual register interface code, is a binary-only > module that is "snapped in" to SAND. SAND is GPL and is similar to the > FreeBSD Netgraph module - it provides all the higher-level protocol stuff, > like > Frame Relay, PPP, HDLC, and such. SAND goes between the OS TCP/IP stack and > that binary only module. That's rather simplified, since SAND also does alot of other things, but you have the basics. > The reason that Imagestream went this road is that like Doug said, all > those hardware vendors like Rockwell think that there's something > valuable in a pure register interface spec publication for their > products. So, this way Imagestream can sign their souls away to get > access to that interface spec - but they isolate all that contaminated > code in this binary snap-in module. It's a hack of a solution but > unfortunately is getting more and more common under UNIX because the > Linux people have caved in and are busily screwing their own principles > of GPL, by soliciting ever greater amounts of closed-source, Linux code. > Imagestream isn't the only one out there doing this. Well, not exactly. The SAND architecture was written long before we ever licensed one line of code from ANYONE. The idea behind the hardware modules was very similar to what Netgraph provides. You can "snap in" new hardware, software or pre- and post-processing modules without having to make accomodations in the other code. > Now, you can make all the technical arguments you want about how a modularized > development environment like this allows code reuse and this is quite > true - but you must keep in mind that SAND's modularized development has > a primary goal of being able to keep the contaminated code in the driver > snap-in modules, code reuse is secondary. Again, this is incorrect. Code reuse and shorter devlopment cycles were the reason for SAND. The hardware module code is NOT all licensed code. With the exception of the ATM cards, there's more free code than licensed code in the hardware modules. > It's incorrect because it's perfectly possible to write a monolithic > driver under FreeBSD that's only available as an object module and > instead links in to the FreeBSD answer to SAND - which is Netgraph. > This is exactly how the WANic 400 driver is now. (except of course > the WANic 4xx driver is source available) It is possible to have a monolithic driver set, but it doesn't accomplish the objective that we have (and you noted): to have ONE code tree for ALL platforms (save Windows, which is a different animal altogether). We don't want to see a return to the monolithic drivers of old under ANY platform. I'm not saying that monolithic drivers aren't possible, just that they aren't going to happen again. > But you see that in this area SAND is no more standard than Netgraph is. > SAND provides Linux users that run WANic cards a lot of stuff - but it > is GPL which makes it difficult to use in many commercial FreeBSD > projects. I don't think the use of GPL or LGPL prevents anyone from using it in a commercial project with FreeBSD, Linux or any OS. ImageStream, and other companies, are successfully using GPL and LGPL code in commercial projects. > It's been discussed to death in this forum before but the worst possible > thing that Imagestream could have done was to put SAND under GPL. If you > had simply put it under BSD license then BOTH the BSD and Linux people > could have used it, in fact Netgraph may have never been written, and a > lot of other commercial UNIX's might have used it too (like Apple's > MacOS X) I'll disagree, but the discussion is digressing here from where we started. I'm as disinterested in a license war as I was in an OS war. > I believe you, I believe you. But, did the decision makers at SBS even know > that the BSD community currently can't use the 500 series and above? And > that discontinuting it would cut out that section of their market? Did you > guys know that? They knew it. We knew it. It was such a small portion of the total market that they didn't care. We care, which is why I'm taking the time to have this discussion with all of you. > During that time I've seen WANic or RISCom cards come up for bid exactly SIX > times. And, THREE of the times I was the sole bidder and bought them. The > other three times, well one was a 56K card, another the seller wanted $500 > (hah) and the other the seller wanted another rediculous amount. During that > time I've also kept tabs on what the commercial networking resale vendors > that I also buy from have been doing and I've not seen anything at all marked > RISCom, WANic, or Imagestream. So it's a limited option. I'd never buy commodity hardware used when you could buy it new for next to nothing (compared to even most USED Cisco gear). > 1) The cards are almost impossible to identify if they are just loose with > no documentation. Some vendors slap their moniker in unmistakable letters > across all their cards, SDL/SBS and you guys never did. Incorrect. The SDL or SBS moniker and the words "WANic 400" and the part number are on EVERY card. Ultimately, you CAN get your hands on used equipment. It isn't easy, nor is it desirable in most situations, but it IS an option. I wasn't even the one who suggested it. I just included it in the list. > >2) WANic 400 series cards are still available in quantity. If the market > >for FreeBSD is as large as you claim, then you or someone else in the > >community should have no problem snapping up a quantity of these cards and > >reselling them to interested parties. > > As you know, price determines everything. At $777 per WANic405, you elected > NOT to purchase 100 of them from SBS and just warehouse them. (I'll assume > that your probably paying at least $500 per card, which is $50K for that > quantity of 100) If SBS is going to continue to have that offer of they > will sell them to you at lots of 100, why then in your shoes I'd make > the same decision, because with SBS dumping 1000 of the cards on the > used market, you could be putting $50K into a white elephant. I mean, if > you sell 100 WANic cards a year, why then if SBS dumped 1000 of them, > that's a 10 year supply floating around out there. SBS didn't dump 1000 WANic 400s. One of their OEMs who moved to the 520 series cards did. SBS had nothing to do with that auction. They dumped (sold at regular prices, really) about 400 cards to us and their OEMs. I know who won the auction on the cards, and I doubt you'll see more than a handful ever on the market for resale. The current price at 1 off retail is $676-$693, not $777. The price for 100, which is the minimum quantity required to support a special build, is 20% off of that, or $541. > Now, if SBS is willing to do a lot of 100 cards at a wholesale price of, > say $50 dollars a card, then I and a lot of other people could probably > round up 100 sales very quickly at $100 per card. And you know that this is unreasonable, since you couldn't source the components for $50, much less put together a card. > This is a kind offer but you have to put some pricing to it. If your > only selling them in lots of 100 cards, at the price on your website of > $777 per card, that's 15% off a $77K sale. I'd guess that your volume > discounts would drop that $77K quite a bit - but still out of reach > of an individual company, of course. Well, if the market is as big as you keep saying, 100 cards should be easy to swallow. As I've said, the price is roughly $541, not $777. > But this is all academic marketing of course - because at those dollar > levels, it's far cheaper to simply pay a developer to write FreeBSD > drivers for the WANic 5xx series of cards and deal with the licensing > issues. That's an option, too. One that has been available to everyone for over 5 years. I just was providing another incentive that a) solved the supply problems with the 400s and b) got drivers for all of the cards. > >3) Virtually ALL of our customers, save for OEMs making their own > >products, purchase complete routers. Going this route would eliminate the > >need to have FreeBSD support, as any user would have a standalone router. > > > > Remember, your talking to a bunch of FreeBSD people here, they might not > want a router based on Linux. > They use routers based on IOS, desktops based on Windows, and lots of embedded OSes (including Linux, in some cases, I'll bet). Are you suggesting that all FreeBSD users are OS zealots and refuse to use anything but FreeBSD everywhere? I would disagree with that indictment of the community. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 7:28:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id BE09937B40C; Tue, 16 Oct 2001 07:28:10 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id JAA19950; Tue, 16 Oct 2001 09:28:02 -0500 Date: Tue, 16 Oct 2001 09:28:02 -0500 (EST) From: Doug Hass To: Ted Mittelstaedt Cc: Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: RE: FYI In-Reply-To: <000601c1561a$3acf7f20$1401a8c0@tedm.placo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > There is depending on the price. I'll freely admit however that I have not > priced the competitive serial sync cards that are currently supported > under FreeBSD, so I don't know how the WANic 400 or 500 stacks up against > them. For all I know right now there's someone just bringing a T1 interface > card to the market with integrated CSU that sells for $30 per card which > would make this entire discussion moot. $30 per card? Do tell, do tell. I'll buy 10,000 of them right now, and pay you $60 a card to buy them for me. What company would be foolish enough to offer a $30 T1 card? I have my credit card ready! Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 8: 5:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1CE7837B405 for ; Tue, 16 Oct 2001 08:05:24 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f9GF5MV10055; Tue, 16 Oct 2001 09:05:23 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f9GF5L732042; Tue, 16 Oct 2001 09:05:22 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110161505.f9GF5L732042@harmony.village.org> To: Matthew Emmerton Subject: Re: Adding support for Duxbury PCI modem to FreeBSD 4.4 Cc: Peter van Heusden , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 16 Oct 2001 08:24:10 EDT." References: Date: Tue, 16 Oct 2001 09:05:21 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message Matthew Emmerton writes: : On Tue, 16 Oct 2001, Peter van Heusden wrote: : : > On Mon, Oct 15, 2001 at 09:35:58AM -0600, Warner Losh wrote: : > > In message <9DCF7A9E7AD27A4F962A37F7E78607B10CFAEC@ukhokho.ct.schoolnet.org.za> "Peter van Heusden" writes: : > : > I'm having a look at the Linux 2.4 kernel code, since they apparently : > have winmodem support (including for the SM56 chipset, which is now : > no longer supported by Motorola - double Aaaargh!), but will probably : > have to go with an external modem, since it seems to be impossible to : > get internal PCI non-winmodems. : : 3Com makes a PCI "hardware" (non-Winmodem) modem. I've seen only 3 hardware pci modems. All are based on the lucent "kermit" chipset, but 3com PCI FaxModems have their own id. Well, I take that back. There's at least one pccard based pci modem. There is a PLX part that glues the pccard bus to the pci ala some of the wi adapters. And there's an old modem chipset on the card. These were made out of surplus parts and I never saw them in real channels (and to be honest, only consulted in writing a driver at the high level for them, I've not put one in a machine or had one in hand). I'm not sure that the SurfRider that's listed in the driver really is a hardware modem. All the other cards should likely be moved to my puc bridge driver, but until I have that working, it is best to leave things alone. :-) One problem with sio is that you can't have different clock chip rates than the default. Some multiport boards have faster xtals that allow higher data rates :-(. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 8:59:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nelly.internal.irrelevant.org (irrelevant.demon.co.uk [158.152.220.121]) by hub.freebsd.org (Postfix) with ESMTP id ED60E37B408 for ; Tue, 16 Oct 2001 08:59:26 -0700 (PDT) Received: from simond by nelly.internal.irrelevant.org with local (Exim 3.33 #1) id 15tWap-0000JQ-00; Tue, 16 Oct 2001 16:57:23 +0100 Date: Tue, 16 Oct 2001 16:57:23 +0100 From: Simon Dick To: Warner Losh Cc: Matthew Emmerton , Peter van Heusden , freebsd-hackers@freebsd.org Subject: Re: Adding support for Duxbury PCI modem to FreeBSD 4.4 Message-ID: <20011016165722.A988@irrelevant.org> References: <200110161505.f9GF5L732042@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: <200110161505.f9GF5L732042@harmony.village.org>; from imp@harmony.village.org on Tue, Oct 16, 2001 at 09:05:21AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Oct 16, 2001 at 09:05:21AM -0600, Warner Losh wrote: > In message Matthew Emmerton writes: > : On Tue, 16 Oct 2001, Peter van Heusden wrote: > : > : > On Mon, Oct 15, 2001 at 09:35:58AM -0600, Warner Losh wrote: > : > > In message <9DCF7A9E7AD27A4F962A37F7E78607B10CFAEC@ukhokho.ct.schoolnet.org.za> "Peter van Heusden" writes: > : > > : > I'm having a look at the Linux 2.4 kernel code, since they apparently > : > have winmodem support (including for the SM56 chipset, which is now > : > no longer supported by Motorola - double Aaaargh!), but will probably > : > have to go with an external modem, since it seems to be impossible to > : > get internal PCI non-winmodems. > : > : 3Com makes a PCI "hardware" (non-Winmodem) modem. > > I've seen only 3 hardware pci modems. All are based on the lucent > "kermit" chipset, but 3com PCI FaxModems have their own id. > > Well, I take that back. There's at least one pccard based pci modem. > There is a PLX part that glues the pccard bus to the pci ala some of > the wi adapters. And there's an old modem chipset on the card. These > were made out of surplus parts and I never saw them in real channels > (and to be honest, only consulted in writing a driver at the high > level for them, I've not put one in a machine or had one in hand). > > I'm not sure that the SurfRider that's listed in the driver really is > a hardware modem. All the other cards should likely be moved to my > puc bridge driver, but until I have that working, it is best to leave > things alone. :-) One problem with sio is that you can't have > different clock chip rates than the default. Some multiport boards > have faster xtals that allow higher data rates :-(. Please don't remove the SurfRider one: sio0: port 0xa400-0xa407 irq 12 at device 10.0 on pci0 sio0: moving to sio2 sio2: type 16550A It was me who submitted the ID for it, it's my main modem :) -- Simon Dick simond@irrelevant.org "Why do I get this urge to go bowling everytime I see Tux?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 9:14:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 4662C37B405; Tue, 16 Oct 2001 09:14:44 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9GGEDT19811; Tue, 16 Oct 2001 09:14:17 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Doug Hass" Cc: "Leo Bicknell" , "Jim Bryant" , "MurrayTaylor" , , Subject: RE: FYI Date: Tue, 16 Oct 2001 09:14:13 -0700 Message-ID: <000001c1565d$987a8c80$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Doug Hass >Sent: Tuesday, October 16, 2001 7:28 AM >To: Ted Mittelstaedt >Cc: Leo Bicknell; Jim Bryant; MurrayTaylor; freebsd-hackers@FreeBSD.ORG; >freebsd-questions@FreeBSD.ORG >Subject: RE: FYI > > >> There is depending on the price. I'll freely admit however that I have not >> priced the competitive serial sync cards that are currently supported >> under FreeBSD, so I don't know how the WANic 400 or 500 stacks up against >> them. For all I know right now there's someone just bringing a T1 >interface >> card to the market with integrated CSU that sells for $30 per card which >> would make this entire discussion moot. > >$30 per card? Do tell, do tell. I'll buy 10,000 of them right now, and >pay you $60 a card to buy them for me. > >What company would be foolish enough to offer a $30 T1 card? I have my >credit card ready! > :-) That was an example only, exaggerated to illustrate a point. But, it's a point with some validity too - if T1 circuits were as common as DSL circuits, and DSL circuits were like T1's in volume, you would see ADSL chipsets at the sync port chipset pricing levels, and sync port chipsets at the $30 range. As you pointed out this is a volume thing. Before anyone would dump $50K into a special order of WANic 400 cards, you would need to do a comparison of what's currently available in the market. As someone else pointed out in this forum, the Hitachi chipset is an older design. I'm sure that it's probably possible today to design a sync controller chip that sells for a lot less than the Hitachi part, perhaps even under the $30 level. Certainly, async chips sell at that level in volume. It's too bad that IBM didn't decide to put a sync serial port on the original XT. :-) Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 9:27:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id 3A29E37B405 for ; Tue, 16 Oct 2001 09:27:48 -0700 (PDT) Received: from localhost (thomas@localhost) by brunel.uk1.vbc.net (8.11.6/8.11.6) with ESMTP id f9GGRk818703 for ; Tue, 16 Oct 2001 17:27:46 +0100 (BST) Date: Tue, 16 Oct 2001 17:27:46 +0100 (BST) From: Thomas Dixon To: hackers@freeBSD.org Subject: Problems with booting of CD-ROM (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm trying to make a bootable CD using the cdboot program that come with freeBSD in /sys/i386/boot/cdboot. The computer I'm trying to do this on definately boots other CDs as it has booted several other CDs. However using a CD I've made using mkisofs and cdboot it gives the error; Your BIOS int 0x13 extensions seem to be disabled. It's impossible to boot a CD-ROM without them. (BIOS int 0x13 fn 0x4b01 yielded error 1) I'm using an Asus P5A motherboard, there appears to be no way to enable the int 0x13 extensions in the BIOS and there is nothing in the manual that refers to these. Any ideas why this error is coming up or how to fix it? - Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 9:55:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id 1FCAA37B401; Tue, 16 Oct 2001 09:55:15 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id LAA02828; Tue, 16 Oct 2001 11:54:08 -0500 Date: Tue, 16 Oct 2001 11:54:08 -0500 (EST) From: Doug Hass Reply-To: Doug Hass To: Ted Mittelstaedt Cc: Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: RE: FYI In-Reply-To: <000001c1565d$987a8c80$1401a8c0@tedm.placo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > As someone else pointed out in this forum, the Hitachi chipset is an > older design. I'm sure that it's probably possible today to design a > sync controller chip that sells for a lot less than the Hitachi part, > perhaps even under the $30 level. Certainly, async chips sell at that > level in volume. It's too bad that IBM didn't decide to put a sync > serial port on the original XT. :-) The conjecture and wishful thinking is nice. Unfortunately, the available chipsets today aren't running at or anywhere near the $30 range, which is why you don't see $75 T1 cards with CSUs (you see $750-$1200 ones). Let's dispense with all the talk about $75 T1 cards that don't exist (and won't for some time), whose licensing scheme is better, what driver architecture was developed for what reason and let's get back to the original issues: 1) Availability of the 400 series cards. If the FreeBSD market has the 400 series cards in such demand, then someone should be calling me with an order. I'll cut 20% off list for you if you tell me its for FreeBSD, and I'll still pledge 15% of your purchase price on top of that toward driver development. I'll give up my volume margin as a clear indication of my willingness to work with the community. The drivers BSDI developed and gave to the community for the 400 series are seriously out of date, by the way. Last I knew, they still referred to the cards as the "n2pci" and used some outdated code that has since been much improved. I'd be interested in working with a developer or developers to get some updated drivers out there for FreeBSD. This brings me to... 2) Driver development for FreeBSD We'll pledge 15% of the purchase of the aforementioned 400 series cards toward supporting a developer or developers to bring drivers to the FreeBSD market. The 400 series drivers need to be updated. There are a full line of cards available now that also need drivers. Even if no one in the community is willing to pledge money (through a card purchase or directly to a developer), I'm assuming that someone out there would be interested in developing the drivers. Again, if the FreeBSD market has WAN cards in such a high demand, we need to get developers on the driver development immediately. Now that you know we are interested, the code is available, and that we've pledged money toward it, I'd like to see someone in the community start working toward a solution, instead of complaining about how there isn't one. Regards, Doug ----- Doug Hass ImageStream Internet Solutions dhass@imagestream.com http://www.imagestream.com Office: 1-219-935-8484 Fax: 1-219-935-8488 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 10:34:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail36.sdc1.sfba.home.com (femail36.sdc1.sfba.home.com [24.254.60.26]) by hub.freebsd.org (Postfix) with ESMTP id 3607837B408 for ; Tue, 16 Oct 2001 10:34:21 -0700 (PDT) Received: from laptop.baldwin.cx ([24.2.39.156]) by femail36.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20011016173420.YRTV27661.femail36.sdc1.sfba.home.com@laptop.baldwin.cx>; Tue, 16 Oct 2001 10:34:20 -0700 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: Date: Tue, 16 Oct 2001 10:34:21 -0700 (PDT) From: John Baldwin To: Thomas Dixon Subject: RE: Problems with booting of CD-ROM (fwd) Cc: hackers@freeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 16-Oct-01 Thomas Dixon wrote: > I'm trying to make a bootable CD using the cdboot program that come with > freeBSD in /sys/i386/boot/cdboot. The computer I'm trying to do this on > definately boots other CDs as it has booted several other CDs. However > using a CD I've made using mkisofs and cdboot it gives the error; > > Your BIOS int 0x13 extensions seem to be disabled. > It's impossible to boot a CD-ROM without them. > (BIOS int 0x13 fn 0x4b01 yielded error 1) > > I'm using an Asus P5A motherboard, there appears to be no way to enable > the int 0x13 extensions in the BIOS and there is nothing in the manual > that refers to these. > > Any ideas why this error is coming up or how to fix it? Don't use cdboot or cdldr, they don't qutie work yet. :( Instead, make a floppy image and use that to boot. -- 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 Tue Oct 16 10:48: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 614D237B407 for ; Tue, 16 Oct 2001 10:48:01 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f9GHlxV10652; Tue, 16 Oct 2001 11:48:00 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f9GHlx733032; Tue, 16 Oct 2001 11:47:59 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110161747.f9GHlx733032@harmony.village.org> To: Simon Dick Subject: Re: Adding support for Duxbury PCI modem to FreeBSD 4.4 Cc: Matthew Emmerton , Peter van Heusden , freebsd-hackers@freebsd.org In-reply-to: Your message of "Tue, 16 Oct 2001 16:57:23 BST." <20011016165722.A988@irrelevant.org> References: <20011016165722.A988@irrelevant.org> <200110161505.f9GF5L732042@harmony.village.org> Date: Tue, 16 Oct 2001 11:47:59 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011016165722.A988@irrelevant.org> Simon Dick writes: : Please don't remove the SurfRider one: : sio0: port 0xa400-0xa407 irq 12 at device 10.0 on pci0 : sio0: moving to sio2 : sio2: type 16550A : : It was me who submitted the ID for it, it's my main modem :) Wow! Cool. I didn't think that there were others. Do you know if this is a "kermit" chipset or not? Is there a Lucent part on the card with the word "kermit" on it (well, newer versions don't have kermit on them). I won't remove it. I was just surprised to find another one with the plethera of winmodems. Cool. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 10:57: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 194BE37B405 for ; Tue, 16 Oct 2001 10:57:07 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9GHv5633749; Tue, 16 Oct 2001 10:57:05 -0700 (PDT) (envelope-from dillon) Date: Tue, 16 Oct 2001 10:57:05 -0700 (PDT) From: Matthew Dillon Message-Id: <200110161757.f9GHv5633749@apollo.backplane.com> To: Maxime Henrion Cc: freebsd-hackers@FreeBSD.org Subject: Re: cvs commit: src/sys/vm vnode_pager.c References: <200110121817.f9CIHYU38714@freefall.freebsd.org> <200110122330.f9CNU1u36917@earth.backplane.com> <200110152135.f9FLZpg56816@earth.backplane.com> <20011016172843.A469@nebula.cybercable.fr> <200110161618.f9GGIpM31430@apollo.backplane.com> <20011016190340.A465@nebula.cybercable.fr> <200110161712.f9GHCbg33501@apollo.backplane.com> <20011016194937.A447@nebula.cybercable.fr> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Yes, I removed the option "userquota" from my fstab file and did a :quotaoff -a to be perfectly sure. : :Here is the profiling output without quotas enabled. Note that the :first profiling output was done when sys cpu time was jumping from 0 to :51%, and that this time, due to lack of time for doing massive cvs :update, it was done in a state where it was jumping from 0 to 11%. : :Thanks, :Maxime Henrion This profiled output shows the system completely idle. If something is locking up eating cpu this profile run didn't catch 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 Oct 16 11: 4: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from noos.fr (r178m112.cybercable.tm.fr [195.132.178.112]) by hub.freebsd.org (Postfix) with ESMTP id BDE5237B401 for ; Tue, 16 Oct 2001 11:04:03 -0700 (PDT) Received: (from mux@localhost) by noos.fr (8.11.6/8.11.4) id f9GI35800759; Tue, 16 Oct 2001 20:03:05 +0200 (CEST) (envelope-from mux) Date: Tue, 16 Oct 2001 20:03:00 +0200 From: Maxime Henrion To: Matthew Dillon Cc: freebsd-hackers@freebsd.org Subject: Re: cvs commit: src/sys/vm vnode_pager.c Message-ID: <20011016200300.B447@nebula.cybercable.fr> References: <200110122330.f9CNU1u36917@earth.backplane.com> <200110152135.f9FLZpg56816@earth.backplane.com> <20011016172843.A469@nebula.cybercable.fr> <200110161618.f9GGIpM31430@apollo.backplane.com> <20011016190340.A465@nebula.cybercable.fr> <200110161712.f9GHCbg33501@apollo.backplane.com> <20011016194937.A447@nebula.cybercable.fr> <200110161757.f9GHv5633749@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200110161757.f9GHv5633749@apollo.backplane.com> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > This profiled output shows the system completely idle. If > something is locking up eating cpu this profile run didn't > catch it. Ok, I'll do a new one ASAP, with a system where system cpu time jump is higher. Maxime -- Don't be fooled by cheap finnish imitations ; BSD is the One True Code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 11: 5: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2FDED37B403 for ; Tue, 16 Oct 2001 11:05:00 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9GI4wF33862; Tue, 16 Oct 2001 11:04:58 -0700 (PDT) (envelope-from dillon) Date: Tue, 16 Oct 2001 11:04:58 -0700 (PDT) From: Matthew Dillon Message-Id: <200110161804.f9GI4wF33862@apollo.backplane.com> To: Maxime Henrion Cc: freebsd-hackers@freebsd.org Subject: Re: cvs commit: src/sys/vm vnode_pager.c References: <200110122330.f9CNU1u36917@earth.backplane.com> <200110152135.f9FLZpg56816@earth.backplane.com> <20011016172843.A469@nebula.cybercable.fr> <200110161618.f9GGIpM31430@apollo.backplane.com> <20011016190340.A465@nebula.cybercable.fr> <200110161712.f9GHCbg33501@apollo.backplane.com> <20011016194937.A447@nebula.cybercable.fr> <200110161757.f9GHv5633749@apollo.backplane.com> <20011016200300.B447@nebula.cybercable.fr> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :Matthew Dillon wrote: :> :> This profiled output shows the system completely idle. If :> something is locking up eating cpu this profile run didn't :> catch it. : :Ok, I'll do a new one ASAP, with a system where system cpu time jump is :higher. : :Maxime :-- :Don't be fooled by cheap finnish imitations ; BSD is the One True Code The time jump is irrelevant. It's whether you feel a glitch or not while the sync is running that counts. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 11:10:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from noos.fr (r178m112.cybercable.tm.fr [195.132.178.112]) by hub.freebsd.org (Postfix) with ESMTP id BDEA837B405 for ; Tue, 16 Oct 2001 11:10:18 -0700 (PDT) Received: (from mux@localhost) by noos.fr (8.11.6/8.11.4) id f9GIAEZ00940; Tue, 16 Oct 2001 20:10:14 +0200 (CEST) (envelope-from mux) Date: Tue, 16 Oct 2001 20:10:14 +0200 From: Maxime Henrion To: Matthew Dillon Cc: freebsd-hackers@freebsd.org Subject: Re: cvs commit: src/sys/vm vnode_pager.c Message-ID: <20011016201014.C447@nebula.cybercable.fr> References: <200110152135.f9FLZpg56816@earth.backplane.com> <20011016172843.A469@nebula.cybercable.fr> <200110161618.f9GGIpM31430@apollo.backplane.com> <20011016190340.A465@nebula.cybercable.fr> <200110161712.f9GHCbg33501@apollo.backplane.com> <20011016194937.A447@nebula.cybercable.fr> <200110161757.f9GHv5633749@apollo.backplane.com> <20011016200300.B447@nebula.cybercable.fr> <200110161804.f9GI4wF33862@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200110161804.f9GI4wF33862@apollo.backplane.com> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > The time jump is irrelevant. It's whether you feel a glitch or not > while the sync is running that counts. I don't do profiling on a sync command, I monitore the system with ``iostat -w 1'' then I see where the jump occurs and since it occurs every 30s, I try to launch the profiling in a window around the jump as little as possible. Am I doing it wrong ? Maxime -- Don't be fooled by cheap finnish imitations ; BSD is the One True Code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 11:24:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C45FA37B401 for ; Tue, 16 Oct 2001 11:24:47 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9GIOjT33989; Tue, 16 Oct 2001 11:24:45 -0700 (PDT) (envelope-from dillon) Date: Tue, 16 Oct 2001 11:24:45 -0700 (PDT) From: Matthew Dillon Message-Id: <200110161824.f9GIOjT33989@apollo.backplane.com> To: Maxime Henrion Cc: freebsd-hackers@freebsd.org Subject: Re: cvs commit: src/sys/vm vnode_pager.c References: <200110152135.f9FLZpg56816@earth.backplane.com> <20011016172843.A469@nebula.cybercable.fr> <200110161618.f9GGIpM31430@apollo.backplane.com> <20011016190340.A465@nebula.cybercable.fr> <200110161712.f9GHCbg33501@apollo.backplane.com> <20011016194937.A447@nebula.cybercable.fr> <200110161757.f9GHv5633749@apollo.backplane.com> <20011016200300.B447@nebula.cybercable.fr> <200110161804.f9GI4wF33862@apollo.backplane.com> <20011016201014.C447@nebula.cybercable.fr> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :Matthew Dillon wrote: :> :> The time jump is irrelevant. It's whether you feel a glitch or not :> while the sync is running that counts. : :I don't do profiling on a sync command, I monitore the system with :``iostat -w 1'' then I see where the jump occurs and since it occurs :every 30s, I try to launch the profiling in a window around the jump as :little as possible. : :Am I doing it wrong ? :Maxime Well, 11% over a period of a single second, once every 30 seconds makes sense if there are a lot of vnodes cached. I think you are seeing the same issue, just that on -stable there is much lower overhead. Basically we have two routines that are causing problems: ffs_sync() qsync() (quota sync) The basic problem for both is that either a lock or a mutex is being obtained and released for each loop. Actually two are being obtained and two are being released for each loop. The high level scan of the vnode list for the mount point only requires one mutex to be held through the scan, so if we can flag the situation somehow in a manner that can be detected without having to get the vnode interlock, we can remove all in-loop lock/mutex operations for the degenerate case. We would still be scanning hundreds of thousands of vnodes, but at least we would be scanning them in a tight loop without any subroutine calls.. maybe 15nS/loop instead of 500nS. That would solve the problem. We can accomplish this for ffs_sync(). It's actually fairly easy to do. Accomplishing this for qsync() is harder due to the many-to-one relationship between inodes and their quota structures, and may require a complete rewrite of the quota syncing code. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 11:33:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from noos.fr (r178m112.cybercable.tm.fr [195.132.178.112]) by hub.freebsd.org (Postfix) with ESMTP id C9B0637B401 for ; Tue, 16 Oct 2001 11:33:26 -0700 (PDT) Received: (from mux@localhost) by noos.fr (8.11.6/8.11.4) id f9GIWHK01278; Tue, 16 Oct 2001 20:32:17 +0200 (CEST) (envelope-from mux) Date: Tue, 16 Oct 2001 20:32:12 +0200 From: Maxime Henrion To: Matthew Dillon Cc: freebsd-hackers@freebsd.org Subject: Re: cvs commit: src/sys/vm vnode_pager.c Message-ID: <20011016203212.D447@nebula.cybercable.fr> References: <20011016172843.A469@nebula.cybercable.fr> <200110161618.f9GGIpM31430@apollo.backplane.com> <20011016190340.A465@nebula.cybercable.fr> <200110161712.f9GHCbg33501@apollo.backplane.com> <20011016194937.A447@nebula.cybercable.fr> <200110161757.f9GHv5633749@apollo.backplane.com> <20011016200300.B447@nebula.cybercable.fr> <200110161804.f9GI4wF33862@apollo.backplane.com> <20011016201014.C447@nebula.cybercable.fr> <200110161824.f9GIOjT33989@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200110161824.f9GIOjT33989@apollo.backplane.com> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: > Well, 11% over a period of a single second, once every 30 seconds > makes sense if there are a lot of vnodes cached. I think you are > seeing the same issue, just that on -stable there is much lower > overhead. > > Basically we have two routines that are causing problems: > > ffs_sync() > qsync() (quota sync) [explanation ripped] Perhaps my problem is because of something else ; I recompiled a kernel with a different syncdelay in vfs_subr.c, 42s (sorry ;) instead of 30s. I also bumped SYNCER_MAXDELAY accordingly. But, the problem was still happening every 30s. Maxime -- Don't be fooled by cheap finnish imitations ; BSD is the One True Code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 11:45:19 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 15A0537B40B; Tue, 16 Oct 2001 11:45:00 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 796B914C2E; Tue, 16 Oct 2001 20:44:58 +0200 (CEST) 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: freebsd-hackers@FreeBSD.org Cc: John Baldwin , cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org, Bruce Evans Subject: Re: cvs commit: src/sys/vm vnode_pager.c References: <200110161800.f9GI0QP33797@apollo.backplane.com> From: Dag-Erling Smorgrav Date: 16 Oct 2001 20:44:57 +0200 In-Reply-To: <200110161800.f9GI0QP33797@apollo.backplane.com> Message-ID: Lines: 29 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-=-= Matthew Dillon writes: > Just calling a mutex function hundreds of thousands of times is > going to be enough to cause the problem. I see a way we can fix the > problem... the mount point lock is locking the list, so if the > information we need to determine whether we have work to do is stored in > the vnode itself we can check and loop without having to mess > around with any more mutexes. If the flag says that there > may be something to do, *then* we do the hard work. That sounds reasonable. One stray thought, by the way - could it be that vnodes aren't being reclaimed as fast as they should? What's the policy - do vnodes only get reclaimed when we start running out? Should we re-evaluate the cost of having them slow down ffs_sync() vs. what we save by keeping them around so we don't need to reallocate them? Attached are a patch that adds counters to ffs_sync() (to see how many vnodes are traversed each time, and how many of those actually needed syncing), and a script I'm using to roughly measure the performance of ffs_sync(). DES -- Dag-Erling Smorgrav - des@ofug.org --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=ffs_sync.diff Index: sys/ufs/ffs/ffs_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_vfsops.c,v retrieving revision 1.161 diff -u -r1.161 ffs_vfsops.c --- sys/ufs/ffs/ffs_vfsops.c 2 Oct 2001 14:34:22 -0000 1.161 +++ sys/ufs/ffs/ffs_vfsops.c 16 Oct 2001 17:21:34 -0000 @@ -972,6 +972,9 @@ return (0); } +static int count_synced_vnodes = 0; +SYSCTL_INT(_debug, OID_AUTO, count_synced_vnodes, CTLFLAG_RW, &count_synced_vnodes, 0, ""); + /* * Go through the disk queues to initiate sandbagged IO; * go through the inodes to write those that have been modified; @@ -991,6 +994,7 @@ struct ufsmount *ump = VFSTOUFS(mp); struct fs *fs; int error, count, wait, lockreq, allerror = 0; + int looped = 0, vn_traversed = 0, vn_synced = 0; fs = ump->um_fs; if (fs->fs_fmod != 0 && fs->fs_ronly != 0) { /* XXX */ @@ -1008,6 +1012,7 @@ } mtx_lock(&mntvnode_mtx); loop: + ++looped; for (vp = LIST_FIRST(&mp->mnt_vnodelist); vp != NULL; vp = nvp) { /* * If the vnode that we are about to sync is no longer @@ -1017,6 +1022,7 @@ goto loop; nvp = LIST_NEXT(vp, v_mntvnodes); + ++vn_traversed; mtx_unlock(&mntvnode_mtx); mtx_lock(&vp->v_interlock); ip = VTOI(vp); @@ -1027,6 +1033,7 @@ mtx_lock(&mntvnode_mtx); continue; } + ++vn_synced; if (vp->v_type != VCHR) { if ((error = vget(vp, lockreq, td)) != 0) { mtx_lock(&mntvnode_mtx); @@ -1045,6 +1052,12 @@ mtx_lock(&mntvnode_mtx); } mtx_unlock(&mntvnode_mtx); + + if (count_synced_vnodes) + printf(__FUNCTION__ + "(): %d loops, %d vnodes traversed, %d vnodes synced\n", + looped, vn_traversed, vn_synced); + /* * Force stale file system control information to be flushed. */ --=-=-= Content-Type: application/x-sh Content-Disposition: attachment; filename=measure.sh #!/bin/sh vmstat -m | grep FFS sysctl debug.count_synced_vnodes=1 time sync sysctl debug.count_synced_vnodes=0 dmesg | grep ffs_sync | tail -5 --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 14: 0:36 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 385E237B40E; Tue, 16 Oct 2001 14:00:32 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id C18EB14C2E; Tue, 16 Oct 2001 23:00:28 +0200 (CEST) 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: Andrew Reid Cc: Dan Nelson , j balan , freebsd-questions@FreeBSD.ORG, freebsd-hackers@freebsd.org Subject: Re: Network Startup References: <200110152116.f9FLGsL51934@proscouting.com> <20011015162221.B8674@dan.emsphone.com> <20011016100105.D12238@plug.cx> From: Dag-Erling Smorgrav Date: 16 Oct 2001 23:00:28 +0200 In-Reply-To: <20011016100105.D12238@plug.cx> Message-ID: Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrew Reid writes: > On Mon, Oct 15, 2001 at 04:22:21PM -0500, Dan Nelson wrote: > > In the last episode (Oct 15), j balan said: > > > Does anyone know the command to reload rc.conf > > 'reboot' is the only sure way. > That's a bit of a problem as far as I'm concerned. Perhaps the network > scripts should be redesigned in a similar manner to the one taken on be > RedHat. Furrfu. 'shutdown now' followed by 'exit' at the single-user prompt. The only known problems are 1) secure levels and 2) 'route add default'; the latter can be fixed by having rc.network flush the routing table before trying to set the default route. 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 Oct 16 14:17:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (d211.dhcp212-26.cybercable.fr [212.198.26.211]) by hub.freebsd.org (Postfix) with ESMTP id 6722A37B408; Tue, 16 Oct 2001 14:17:41 -0700 (PDT) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id XAA88805; Tue, 16 Oct 2001 23:34:21 +0200 (CEST) (envelope-from thierry@herbelot.com) Message-ID: <3BCCA36A.F555CF26@herbelot.com> Date: Tue, 16 Oct 2001 23:15:22 +0200 From: Thierry Herbelot X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Network Startup References: <200110152116.f9FLGsL51934@proscouting.com> <20011015162221.B8674@dan.emsphone.com> <20011016100105.D12238@plug.cx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [CC trimmed] Dag-Erling Smorgrav wrote: > [SNIP] > > Furrfu. 'shutdown now' followed by 'exit' at the single-user prompt. > The only known problems are 1) secure levels and 2) 'route add > default'; the latter can be fixed by having rc.network flush the > routing table before trying to set the default route. you may add that pccardd does not very much like being restarted (in my experience) and thus I lose my Ethernet pccard when going to single-user and back to normal TfH > > DES > -- > Dag-Erling Smorgrav - des@ofug.org -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 15:43: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts20-srv.bellnexxia.net (tomts20.bellnexxia.net [209.226.175.74]) by hub.freebsd.org (Postfix) with ESMTP id 3B11637B401; Tue, 16 Oct 2001 15:42:55 -0700 (PDT) Received: from xena.gsicomp.on.ca ([65.93.39.114]) by tomts20-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20011016224254.LZPX14703.tomts20-srv.bellnexxia.net@xena.gsicomp.on.ca>; Tue, 16 Oct 2001 18:42:54 -0400 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.1) with SMTP id f9GMYfW18189; Tue, 16 Oct 2001 18:34:41 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <003f01c15694$1de6d460$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: , Subject: Sizing a Streaming Media Server Date: Tue, 16 Oct 2001 18:44:28 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Folks, I very interesting project just landed in my lap -- I need to setup a FreeBSD server to be a streaming media server for 1000+ clients using Nullsoft's Shoutcast. I have some experience with streaming media, so I know how to size the network side of the equation, but what I'm really at a loss for is how much processing power a server will need to do this effectively, and better yet, how to properly tune the FreeBSD machine to handle that many simultaneous clients. If anyone has any experience with this sort of thing, or has any advice, please contact me directly. Thanks, -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 15:47:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns3.safety.net (ns3.safety.net [216.40.201.32]) by hub.freebsd.org (Postfix) with ESMTP id 5881537B403; Tue, 16 Oct 2001 15:47:52 -0700 (PDT) Received: (from les@localhost) by ns3.safety.net (8.10.2/8.10.2) id f9GMlng07045; Tue, 16 Oct 2001 15:47:49 -0700 From: Les Biffle Message-Id: <200110162247.f9GMlng07045@ns3.safety.net> Subject: Re: Sizing a Streaming Media Server In-Reply-To: <003f01c15694$1de6d460$1200a8c0@gsicomp.on.ca> To: Matthew Emmerton Date: Tue, 16 Oct 2001 15:47:49 -0700 (MST) Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL94 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > If anyone has any experience with this sort of thing, or has any advice, > please contact me directly. Copying the list would be great, too. I would love to hear the answer to this!!! -Les -- Les Biffle (480) 585-4099 les@safety.net http://www.les.safety.net/ Network Safety Corp., 5831 E. Dynamite Blvd., Cave Creek, AZ 85331 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 15:59:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.plug.cx (kypo.alfred.cx [150.101.93.134]) by hub.freebsd.org (Postfix) with ESMTP id 6A0AA37B40B; Tue, 16 Oct 2001 15:59:46 -0700 (PDT) Received: by mail.plug.cx (Postfix, from userid 1000) id 20DF82B8BF; Wed, 17 Oct 2001 08:54:53 +0930 (CST) Date: Wed, 17 Oct 2001 08:54:52 +0930 From: Andrew Reid To: Peter Pentchev Cc: Andrew Reid , Dan Nelson , j balan , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Network Startup Message-ID: <20011017085452.A16064@plug.cx> References: <200110152116.f9FLGsL51934@proscouting.com> <20011015162221.B8674@dan.emsphone.com> <20011016100105.D12238@plug.cx> <20011015212017.B73961@dan.emsphone.com> <20011016140837.C12702@plug.cx> <20011016124220.A727@straylight.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011016124220.A727@straylight.oblivion.bg>; from roam@ringlet.net on Tue, Oct 16, 2001 at 12:42:20PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Oct 16, 2001 at 12:42:20PM +0300, Peter Pentchev wrote: > > > ifconfig xxx inet 1.2.3.4 alias > > > > Oh, for sure. That's what I, and the majority of the community, do > > now. I think that it's not particularly convenient if you want to > > restart the network if you've got 3 or 4 network interfaces. > > Are you aware of the existence of /etc/netstart? I wasn't, until > very recently :) Looking at /etc/netstart, it just seems to be a wrapper to network_pass1(). What it doesn't cater for is shutting down all or individual interfaces via a common, slightly simpler interface; restarting one or all interfaces via said interface. /etc/netstart doesn't seem to be much use other than at boot time. - andrew -- void signature () { cout << "Andrew Reid -- andrew.reid@plug.cx" << endl; cout << "Cell: +61 401 946 813" << endl; cout << "Quidquid latine dictum sit, altum viditur" << endl; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 16:22:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AD85437B405 for ; Tue, 16 Oct 2001 16:22:32 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9GNMN347493; Tue, 16 Oct 2001 16:22:23 -0700 (PDT) (envelope-from dillon) Date: Tue, 16 Oct 2001 16:22:23 -0700 (PDT) From: Matthew Dillon Message-Id: <200110162322.f9GNMN347493@apollo.backplane.com> To: Kirk McKusick Cc: freebsd-hackers@freebsd.org Subject: Need post-commit review of vnode freelist cleanup MFC (on -stable) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In particular, the changes to vfs_subr.c. I've gone over it a bunch of times and done some significant testing, but it doesn't hurt to have other eyes take a look at it as well. -Matt Matthew Dillon dillon 2001/10/16 16:16:25 PDT Modified files: (Branch: RELENG_4) sys/kern vfs_subr.c sys/sys vnode.h sys/vm vm_page.c Log: MFC kern/vfs_subr.c 1.263, sys/vnode.h 1.118, vm/vm_page.c 1.153. This MFCs Kirk's vnode freelist cleanup commit from July 2000 in preparation for further work that will eventually make kern.maxvnodes actually do something. Revision Changes Path 1.249.2.16 +27 -69 src/sys/kern/vfs_subr.c 1.111.2.14 +3 -6 src/sys/sys/vnode.h 1.147.2.10 +2 -6 src/sys/vm/vm_page.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 16:23:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id DD64837B40E; Tue, 16 Oct 2001 16:23:05 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA61443; Tue, 16 Oct 2001 17:28:45 -0700 (PDT) Date: Tue, 16 Oct 2001 17:28:43 -0700 (PDT) From: Julian Elischer To: Doug Hass Cc: Ted Mittelstaedt , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen Subject: RE: FYI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 16 Oct 2001, Doug Hass wrote: > > The "hardware API" or the actual register interface code, is a binary-only > > module that is "snapped in" to SAND. SAND is GPL and is similar to the > > FreeBSD Netgraph module - it provides all the higher-level protocol stuff, > > like > > Frame Relay, PPP, HDLC, and such. SAND goes between the OS TCP/IP stack and > > that binary only module. > > That's rather simplified, since SAND also does alot of other things, but > you have the basics. > If there's a published interface, we could make a netgraph/SAND interface module To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 16:36:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id B5CF337B40A for ; Tue, 16 Oct 2001 16:36:30 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id BD5EB16B1E for ; Wed, 17 Oct 2001 01:36:28 +0200 (CEST) Received: from IBM-HIRXKN66F0W.Go2France.com [66.64.14.18] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id A7282E018E; Wed, 17 Oct 2001 01:47:52 +0200 Message-Id: <5.1.0.14.0.20011016183052.029ec358@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 16 Oct 2001 18:35:43 -0500 To: FReebsd-hackers@freebsd.org From: Len Conrad Subject: RE: FYI In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >If there's a published interface, we could make a netgraph/SAND interface >module I think it's better use of hackers' time to look at vendors who already support FreeBSD, such as SBEI and Cyclades, and see why their support for FreeBSD, while apparently useful, is behind the functionality they have in their Linux drivers and if hackers can help them improve their FreeBSD support, adapt netraph, multilink ppp, channelized RAS, etc. Unfortunately, I still looking for somebody who actually uses SBEI and Cyclades T1 boards with FreeBSD. Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 16:47: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id 02C6037B403 for ; Tue, 16 Oct 2001 16:47:07 -0700 (PDT) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id f9GNl3A46500; Tue, 16 Oct 2001 19:47:03 -0400 (EDT) (envelope-from bicknell) Date: Tue, 16 Oct 2001 19:47:03 -0400 From: Leo Bicknell To: Len Conrad Cc: FReebsd-hackers@FreeBSD.ORG Subject: Re: FYI Message-ID: <20011016194703.A46393@ussenterprise.ufp.org> Mail-Followup-To: Len Conrad , FReebsd-hackers@FreeBSD.ORG References: <5.1.0.14.0.20011016183052.029ec358@mail.Go2France.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.1.0.14.0.20011016183052.029ec358@mail.Go2France.com>; from LConrad@Go2France.com on Tue, Oct 16, 2001 at 06:35:43PM -0500 Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Oct 16, 2001 at 06:35:43PM -0500, Len Conrad wrote: > Unfortunately, I still looking for somebody who actually uses SBEI and > Cyclades T1 boards with FreeBSD. I ran across them earlier when looking for what T1 boards were out there. Their boards seem nice, and they do have a driver, in full source form, that is out of date. The one thing I can't find, is prices. I know that I have never considered using a FreeBSD box to terminate a T1, in part because I didn't think there was reasonable hardware available, and good drivers to support it. I think if someone does make this work, they need to proclaim it loudly in all sorts of FreeBSD forms to drum up interest. I think it's out there, just dorment. -- Leo Bicknell - bicknell@ufp.org Systems Engineer - Internetworking Engineer - CCIE 3440 Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 16:47:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id DCF2B37B40E for ; Tue, 16 Oct 2001 16:47:20 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id TAA12928; Tue, 16 Oct 2001 19:46:56 -0400 (EDT) Date: Tue, 16 Oct 2001 19:46:56 -0400 (EDT) From: "Matthew N. Dodd" To: Len Conrad Cc: FReebsd-hackers@FreeBSD.ORG Subject: RE: FYI In-Reply-To: <5.1.0.14.0.20011016183052.029ec358@mail.Go2France.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 16 Oct 2001, Len Conrad wrote: > Unfortunately, I still looking for somebody who actually uses SBEI and > Cyclades T1 boards with FreeBSD. With IBM 2210 series routers going for well under $100 on the used market I can't see why anyone would opt for a host based solution. The people with cash are gonna go with Cisco anyway so unless the host based solution has great support and lots of features I can't see how any vendor could justify getting into this market. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 17: 1:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postoffice.aims.com.au (eth0.lnk.aims.com.au [203.31.73.253]) by hub.freebsd.org (Postfix) with ESMTP id 62C1337B40B for ; Tue, 16 Oct 2001 17:01:35 -0700 (PDT) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2]) by postoffice.aims.com.au with ESMTP id f9H01XZ69172 for ; Wed, 17 Oct 2001 11:01:33 +1100 (EST) (envelope-from chris@aims.com.au) Received: from ntsts1 by aims.com.au with SMTP (MDaemon.v3.5.3.R) for ; Wed, 17 Oct 2001 11:00:33 +1100 Reply-To: From: "Chris Knight" To: Cc: , Subject: RE: T1 boards (was FYI) Date: Wed, 17 Oct 2001 11:00:30 +1100 Message-ID: <007601c1569e$bd44f8c0$020aa8c0@aims.private> 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 CWS, Build 9.0.2416 (9.0.2911.0) In-reply-to: <20011016194703.A46393@ussenterprise.ufp.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-Return-Path: chris@aims.com.au X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Howdy, The SBE Inc wanADAPT-1T1E1 is USD$750. The driver works fine on FreeBSD 4.x. I have provided them with feedback on their documentation and a patch for BPF support and they are keen on getting the driver incorporated into the FreeBSD source tree. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Leo Bicknell > Sent: Wednesday, 17 October 2001 10:47 > To: Len Conrad > Cc: FReebsd-hackers@FreeBSD.ORG > Subject: Re: FYI > > > On Tue, Oct 16, 2001 at 06:35:43PM -0500, Len Conrad wrote: > > Unfortunately, I still looking for somebody who actually > uses SBEI and > > Cyclades T1 boards with FreeBSD. > > I ran across them earlier when looking for what T1 boards were out > there. Their boards seem nice, and they do have a driver, in full > source form, that is out of date. > > The one thing I can't find, is prices. > > I know that I have never considered using a FreeBSD box to terminate > a T1, in part because I didn't think there was reasonable hardware > available, and good drivers to support it. I think if someone does > make this work, they need to proclaim it loudly in all sorts > of FreeBSD > forms to drum up interest. I think it's out there, just dorment. > > > -- > Leo Bicknell - bicknell@ufp.org > Systems Engineer - Internetworking Engineer - CCIE 3440 > Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.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 Oct 16 17: 9:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id 2CDBC37B40D for ; Tue, 16 Oct 2001 17:09:15 -0700 (PDT) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id f9H08so47326; Tue, 16 Oct 2001 20:08:54 -0400 (EDT) (envelope-from bicknell) Date: Tue, 16 Oct 2001 20:08:54 -0400 From: Leo Bicknell To: Chris Knight Cc: freebsd-hackers@freebsd.org, LConrad@Go2France.com Subject: Re: T1 boards (was FYI) Message-ID: <20011016200854.A47117@ussenterprise.ufp.org> Mail-Followup-To: Chris Knight , freebsd-hackers@freebsd.org, LConrad@Go2France.com References: <20011016194703.A46393@ussenterprise.ufp.org> <007601c1569e$bd44f8c0$020aa8c0@aims.private> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <007601c1569e$bd44f8c0$020aa8c0@aims.private>; from chris@aims.com.au on Wed, Oct 17, 2001 at 11:00:30AM +1100 Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Oct 17, 2001 at 11:00:30AM +1100, Chris Knight wrote: > The SBE Inc wanADAPT-1T1E1 is USD$750. The driver works fine on FreeBSD 4.x. > I have provided them with feedback on their documentation and a patch for > BPF support and they are keen on getting the driver incorporated into the > FreeBSD source tree. That would be a fine thing, I think. It sounds like Netgraph support is a must for a large number of people though. I wonder if someone is interested in adding that. Do you have a price for a v.35 card? Some of us still have piles of external CSU's around. :-) -- Leo Bicknell - bicknell@ufp.org Systems Engineer - Internetworking Engineer - CCIE 3440 Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 17:11:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postoffice.aims.com.au (eth0.lnk.aims.com.au [203.31.73.253]) by hub.freebsd.org (Postfix) with ESMTP id 282E337B410 for ; Tue, 16 Oct 2001 17:11:25 -0700 (PDT) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2]) by postoffice.aims.com.au with ESMTP id f9H0BNZ69236 for ; Wed, 17 Oct 2001 11:11:23 +1100 (EST) (envelope-from chris@aims.com.au) Received: from ntsts1 by aims.com.au with SMTP (MDaemon.v3.5.3.R) for ; Wed, 17 Oct 2001 11:11:07 +1100 Reply-To: From: "Chris Knight" To: Subject: RE: T1 boards (was FYI) Date: Wed, 17 Oct 2001 11:11:06 +1100 Message-ID: <007f01c156a0$37aa5370$020aa8c0@aims.private> 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 CWS, Build 9.0.2416 (9.0.2911.0) In-reply-to: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-Return-Path: chris@aims.com.au X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Howdy, SBEI have recently put up a new FreeBSD 4.x driver up at ftp://ftp.sbei.com/pub/OpenSource/FreeBSD/FreeBSD_4.3.tar.gz for their wanADAPT range of cards, so they're no longer out of date. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 17:21: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.disney.com (mail.disney.com [204.128.192.15]) by hub.freebsd.org (Postfix) with ESMTP id 00E8A37B40A for ; Tue, 16 Oct 2001 17:21:04 -0700 (PDT) Received: from Hermes10.corp.disney.com (root@hermes10.corp.disney.com [153.7.110.102]) by mail.disney.com (Switch-2.2.0/Switch-2.2.0) with SMTP id f9H0Jwv16228 for ; Tue, 16 Oct 2001 17:19:58 -0700 (PDT) Received: from [172.30.50.1] by hermes.corp.disney.com with ESMTP for freebsd-hackers@freebsd.org; Tue, 16 Oct 2001 17:20:09 -0700 Received: from plio.fan.fa.disney.com (plio.fan.fa.disney.com [153.7.118.2]) by pecos.fa.disney.com (8.11.3/8.11.3) with ESMTP id f9H0L3323317 for ; Tue, 16 Oct 2001 17:21:03 -0700 (PDT) Received: from mercury.fan.fa.disney.com (mercury.fan.fa.disney.com [153.7.119.1]) by plio.fan.fa.disney.com (8.9.2/8.9.2) with ESMTP id RAA11762 for ; Tue, 16 Oct 2001 17:21:02 -0700 (PDT) (envelope-from Jim.Pirzyk@disney.com) Received: from [172.30.5.138] by mercury.fan.fa.disney.com with ESMTP for freebsd-hackers@freebsd.org; Tue, 16 Oct 2001 17:21:02 -0700 Message-Id: <3BCCCF74.75B7F36C@disney.com> Date: Tue, 16 Oct 2001 17:23:16 -0700 From: Jim Pirzyk Organization: Walt Disney Feature Animation X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: truss vs ktrace Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG So which should I use? Why is there two around? I see that truss has less command line switches than ktrace, but it is a little bit more standard. I also see that truss works with the linux syscalls where ktrace does not remap the syscall names. - JimP -- --- @(#) $Id: dot.signature,v 1.10 2001/05/17 23:38:49 Jim.Pirzyk Exp $ __o Jim.Pirzyk@disney.com ------------- pirzyk@freebsd.org _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation (*)/ (*) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 18:12: 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 0251637B409; Tue, 16 Oct 2001 18:12:00 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 4160B14C2E; Wed, 17 Oct 2001 03:11:58 +0200 (CEST) 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: hackers@freebsd.org Cc: dillon@freebsd.org Subject: Some questions regarding vfs / ffs From: Dag-Erling Smorgrav Date: 17 Oct 2001 03:11:57 +0200 Message-ID: Lines: 26 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Why do we have a single mntvnode_mtx instead of one per struct mount? It's supposed to protect the (per-mount) vnode list, so logically it should be a per-mount mutex. The only reason I can find for it being global is that it saves a few keystrokes in insmntque(). This is the only place I've found where mntvnode_mtx is held and more than one mount is invloved. Why does ffs_sync() grab the vnode interlock before checking if the vnode is dirty? As far as I can determine (from comments in the headers), none of the information it examines is protected by the interlock. Are the comments wrong, or is the code wrong? If the code is wrong, then this is what is killing interrupt latency on my box: needlessly acquiring and releasing 40,000 or 60,000 vnode interlocks twice per minute. Also, ffs_sync() does a lot of locking and unlocking of mntvnode_mtx, when actually (I think) it could get away with just unlocking it briefly while actually syncing a vnode, and holding it the rest of the time. I believe the reason why it currently does what it does is to avoid a lock reversal between mntvnode_mtx and the vnode locks. This won't be a problem if I'm right about the vnode lock being held unnecessarily. 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 Oct 16 18:39:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id C527337B40C; Tue, 16 Oct 2001 18:39:25 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id UAA01080; Tue, 16 Oct 2001 20:19:18 -0500 Date: Tue, 16 Oct 2001 20:19:18 -0500 (EST) From: Doug Hass To: Julian Elischer Cc: Ted Mittelstaedt , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, Alfred Shippen Subject: RE: FYI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Better than a published interface and white paper, we also provide the direct code itself. You could certainly make a netgraph/SAND interface module. Doug On Tue, 16 Oct 2001, Julian Elischer wrote: > > > On Tue, 16 Oct 2001, Doug Hass wrote: > > > > The "hardware API" or the actual register interface code, is a binary-only > > > module that is "snapped in" to SAND. SAND is GPL and is similar to the > > > FreeBSD Netgraph module - it provides all the higher-level protocol stuff, > > > like > > > Frame Relay, PPP, HDLC, and such. SAND goes between the OS TCP/IP stack and > > > that binary only module. > > > > That's rather simplified, since SAND also does alot of other things, but > > you have the basics. > > > > If there's a published interface, we could make a netgraph/SAND interface > module > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 19: 2: 0 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 D848637B40B for ; Tue, 16 Oct 2001 19:01:56 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 9FB2714C2E; Wed, 17 Oct 2001 04:01:55 +0200 (CEST) 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: Jim Pirzyk Cc: freebsd-hackers@freebsd.org Subject: Re: truss vs ktrace References: <3BCCCF74.75B7F36C@disney.com> From: Dag-Erling Smorgrav Date: 17 Oct 2001 04:01:55 +0200 In-Reply-To: <3BCCCF74.75B7F36C@disney.com> Message-ID: Lines: 47 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jim Pirzyk writes: > So which should I use? Why is there two around? I see that truss has > less command line switches than ktrace, but it is a little bit more > standard. - truss slows down the slave process a *lot* as the slave process stops at every syscall and waits for truss to notice, obtain and process information (a task which in itself requires a bunch of additional context switches and syscalls) and print its output. This also means that if you pipe truss through less and don't page down fast enough, the slave process will hang waiting for truss which is waitig for less to absorb its output. - truss currently can't follow forks and trace children of the original process. This should be fixable, though. ktrace doesn't (as far as I know) noticeably slow down the traced process, and can follow forks, and provides some types of information truss doesn't (like namei translations and context switches). On the other hand, it can't display detailed information about syscall arguments the way truss does (but truss needs to stop the traced process to do this, and can only do it for syscalls it's been taught how to decode). I generally find ktrace more than adequate (and often superior to truss), because I can generally work around the need for examining syscall arguments by instrumenting the program I'm debugging, or the kernel itself. If I were debugging a program to which I didn't have source code, I might prefer truss. (ktrace is actually a lot more powerful than it looks on the surface - it has provisions for letting the traced process add information to the trace, and is designed so that one can add new information types without breaking compatibility with older versions of ktrace and kdump - it is conceptually possible to extend ktrace to include the contents of syscall arguments in the log, at least for selected syscalls, like truss does. A junior kernel hacker task maybe?) > I also see that truss works with the linux syscalls where ktrace does > not remap the syscall names. It's not ktrace's business to remap anything. That's kdump's job, and there is a linux_kdump utility in ports that will do what you want. 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 Oct 16 19:16:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail27.sdc1.sfba.home.com (femail27.sdc1.sfba.home.com [24.254.60.17]) by hub.freebsd.org (Postfix) with ESMTP id C2E5937B409; Tue, 16 Oct 2001 19:16:51 -0700 (PDT) Received: from laptop.baldwin.cx ([24.2.39.156]) by femail27.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20011017021650.PAMG12089.femail27.sdc1.sfba.home.com@laptop.baldwin.cx>; Tue, 16 Oct 2001 19:16:50 -0700 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: Date: Tue, 16 Oct 2001 19:16:49 -0700 (PDT) From: John Baldwin To: Dag-Erling Smorgrav Subject: RE: Some questions regarding vfs / ffs Cc: dillon@freebsd.org, hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 17-Oct-01 Dag-Erling Smorgrav wrote: > Why do we have a single mntvnode_mtx instead of one per struct mount? > It's supposed to protect the (per-mount) vnode list, so logically it > should be a per-mount mutex. The only reason I can find for it being > global is that it saves a few keystrokes in insmntque(). This is the > only place I've found where mntvnode_mtx is held and more than one > mount is invloved. Umm, I dunno. > Why does ffs_sync() grab the vnode interlock before checking if the > vnode is dirty? As far as I can determine (from comments in the > headers), none of the information it examines is protected by the > interlock. Are the comments wrong, or is the code wrong? If the code > is wrong, then this is what is killing interrupt latency on my box: > needlessly acquiring and releasing 40,000 or 60,000 vnode interlocks > twice per minute. > > Also, ffs_sync() does a lot of locking and unlocking of mntvnode_mtx, > when actually (I think) it could get away with just unlocking it > briefly while actually syncing a vnode, and holding it the rest of the > time. I believe the reason why it currently does what it does is to > avoid a lock reversal between mntvnode_mtx and the vnode locks. This > won't be a problem if I'm right about the vnode lock being held > unnecessarily. Not quite. You see, when we set the mount vnode pointer inside the vnode, we get the mntvnode mutex while holding the vnode interlock, so the order is thus vnode -> mntvnode. So, the ffs_sync() loop can't lock the vnode while holding the mntvnode lock. It actually used to do that. -- 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 Tue Oct 16 19:23:35 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 8817937B43E; Tue, 16 Oct 2001 19:23:17 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 427F114C40; Wed, 17 Oct 2001 04:23:16 +0200 (CEST) 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: John Baldwin Cc: dillon@freebsd.org, hackers@freebsd.org Subject: Re: Some questions regarding vfs / ffs References: From: Dag-Erling Smorgrav Date: 17 Oct 2001 04:23:15 +0200 In-Reply-To: Message-ID: Lines: 21 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin writes: > Not quite. You see, when we set the mount vnode pointer inside the > vnode, we get the mntvnode mutex while holding the vnode interlock, > so the order is thus vnode -> mntvnode. So, the ffs_sync() loop > can't lock the vnode while holding the mntvnode lock. It actually > used to do that. You're basically agreeing with me :) ffs_sync() releases the mntvnode lock early so it can grab the vnode lock, but if I'm right about it not needing the vnode lock yet at that point, it can gold the mntvnode lock longer - until after it's decided whether or not the vnode needs syncing - which means one less mntnode lock release / acquisition and one less vnode lock acquisition / release per non-dirty vnode, reducing the number of lock operations per vnode from four to nearly zero (as the ratio of dirty vnodes to clean vnodes is usually very low, the average number of lock operations per vnode examined will approach zero) 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 Oct 16 19:29:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0AEA037B403; Tue, 16 Oct 2001 19:29:54 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9H2Tph84237; Tue, 16 Oct 2001 19:29:51 -0700 (PDT) (envelope-from dillon) Date: Tue, 16 Oct 2001 19:29:51 -0700 (PDT) From: Matthew Dillon Message-Id: <200110170229.f9H2Tph84237@apollo.backplane.com> To: Dag-Erling Smorgrav Cc: John Baldwin , hackers@FreeBSD.ORG Subject: Re: Some questions regarding vfs / ffs References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :John Baldwin writes: :> Not quite. You see, when we set the mount vnode pointer inside the :> vnode, we get the mntvnode mutex while holding the vnode interlock, :> so the order is thus vnode -> mntvnode. So, the ffs_sync() loop :> can't lock the vnode while holding the mntvnode lock. It actually :> used to do that. : :You're basically agreeing with me :) ffs_sync() releases the mntvnode :lock early so it can grab the vnode lock, but if I'm right about it :not needing the vnode lock yet at that point, it can gold the mntvnode :lock longer - until after it's decided whether or not the vnode needs :syncing - which means one less mntnode lock release / acquisition and :one less vnode lock acquisition / release per non-dirty vnode, :reducing the number of lock operations per vnode from four to nearly :zero (as the ratio of dirty vnodes to clean vnodes is usually very :low, the average number of lock operations per vnode examined will :approach zero) : :DES :-- :Dag-Erling Smorgrav - des@ofug.org This would be an improvement, but not enough of an improvement. We need to be able to discard most of the vnodes while simply holding the mntvnode mutex, without even having to get the vnode mutex or release the mntvnode mutex. When we find a vnode that 'might' require some action, that's when we do the heavy-weight mutex junk. At least in the case where it's ok to occassionally not get it right (which is most cases). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 19:53: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id EF78B37B409; Tue, 16 Oct 2001 19:52:59 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f9H2qwV12158; Tue, 16 Oct 2001 20:52:58 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f9H2qv710334; Tue, 16 Oct 2001 20:52:57 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110170252.f9H2qv710334@harmony.village.org> To: Thierry Herbelot Subject: Re: Network Startup Cc: Dag-Erling Smorgrav , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 16 Oct 2001 23:15:22 +0200." <3BCCA36A.F555CF26@herbelot.com> References: <3BCCA36A.F555CF26@herbelot.com> <200110152116.f9FLGsL51934@proscouting.com> <20011015162221.B8674@dan.emsphone.com> <20011016100105.D12238@plug.cx> Date: Tue, 16 Oct 2001 20:52:57 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3BCCA36A.F555CF26@herbelot.com> Thierry Herbelot writes: : you may add that pccardd does not very much like being restarted (in my : experience) and thus I lose my Ethernet pccard when going to single-user : and back to normal I thought I'd fixed that... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 20:36:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5047F37B408; Tue, 16 Oct 2001 20:36:26 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9H3aQI94211; Tue, 16 Oct 2001 20:36:26 -0700 (PDT) (envelope-from dillon) Date: Tue, 16 Oct 2001 20:36:26 -0700 (PDT) From: Matthew Dillon Message-Id: <200110170336.f9H3aQI94211@apollo.backplane.com> To: hackers@FreeBSD.ORG Cc: Dag-Erling Smorgrav , John Baldwin , Maxime Henrion Subject: First cut at kern.maxvnodes implementation Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here is my first cut at implementing kern.maxvnodes. When playing with the sysctl()s note that kern.minvnodes also exists and may have to be messed around with. http://apollo.backplane.com/FreeBSD4/ http://apollo.backplane.com/FreeBSD4/maxvnodes-01.diff These patches are for -stable only. I'm going to get the code working on -stable before I try to do a cut for -current. There are notes up at the URL. Note that you cannot set maxvnodes to an arbitrarily low number. Well, you can, but it won't be able to meet the request because active vnodes (open files), buffer cache references, and namei cache references (for directories containing children) will prevent reuse. Thus, kern.maxvnodes is still a soft-maximum, but if you set it (or leave it) at a reasonable value it shouldn't exceed it by much. Another very interesting effect of this patch is that in order to enforce the requested kern.maxvnodes, we have to clear out vnodes that may still have cached pages (i.e. its the presence of cached pages that prevent the vnodes from being freed and cause the vnode count to blow out the kernel malloc area). This means that it is actually possible to stabilize physical memory use and still have a significant number of truely-free pages. The vast majority of systems never reach their programmed kern.maxvnodes, they run out of physical memory first and so start recycling vnodes that no longer have cached pages. Those that do have large-memory configurations (2G+ typically) and are typically accessing a huge number of small files. For example, a cvs mirror might have this characteristic. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 20:36:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id B6ABC37B403; Tue, 16 Oct 2001 20:36:44 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9H3aUT21689; Tue, 16 Oct 2001 20:36:30 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Julian Elischer" , "Doug Hass" Cc: "Jim Bryant" , "MurrayTaylor" , , , "Alfred Shippen" Subject: RE: FYI Date: Tue, 16 Oct 2001 20:36:30 -0700 Message-ID: <000101c156bc$e8ceec80$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Julian Elischer >Sent: Tuesday, October 16, 2001 5:29 PM >To: Doug Hass >Cc: Ted Mittelstaedt; Jim Bryant; MurrayTaylor; >freebsd-hackers@FreeBSD.ORG; freebsd-questions@FreeBSD.ORG; Alfred >Shippen >Subject: RE: FYI > > > > >On Tue, 16 Oct 2001, Doug Hass wrote: > >> > The "hardware API" or the actual register interface code, is a >binary-only >> > module that is "snapped in" to SAND. SAND is GPL and is similar to the >> > FreeBSD Netgraph module - it provides all the higher-level >protocol stuff, >> > like >> > Frame Relay, PPP, HDLC, and such. SAND goes between the OS >TCP/IP stack and >> > that binary only module. >> >> That's rather simplified, since SAND also does alot of other things, but >> you have the basics. >> > >If there's a published interface, we could make a netgraph/SAND interface >module > Well, you might want to take a shortcut and leave the SAND code out of this and just make that interface one that the driver modules that would normally snap into SAND use. The modules would think that Netgraph is SAND? The goal would be to be able to make use of all the SAND modules that Imagestream has. Then all Imagestream's programmers would need to do is add in defines to the module code for FreeBSD and build the modules. While it's not a _port_ of SAND per-se, it's an emulation of it. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 20:47:15 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 828FA37B40C; Tue, 16 Oct 2001 20:47:07 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 8CB1914C2E; Wed, 17 Oct 2001 05:47:05 +0200 (CEST) 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: Matthew Dillon Cc: John Baldwin , fs@FreeBSD.ORG Subject: Re: Some questions regarding vfs / ffs References: <200110170229.f9H2Tph84237@apollo.backplane.com> From: Dag-Erling Smorgrav Date: 17 Oct 2001 05:47:05 +0200 In-Reply-To: <200110170229.f9H2Tph84237@apollo.backplane.com> Message-ID: Lines: 63 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [moving from -hackers to -fs where this *really* belongs] Matthew Dillon writes: > This would be an improvement, but not enough of an improvement. > We need to be able to discard most of the vnodes while simply > holding the mntvnode mutex, without even having to get the vnode > mutex or release the mntvnode mutex. When we find a vnode that > 'might' require some action, that's when we do the heavy-weight > mutex junk. At least in the case where it's ok to occassionally > not get it right (which is most cases). I think you're basically repeating with different words what I said in the mail you replied to. What I said can be summarized as "don't acquire or release any locks until we know the vnode is dirty". The loop checks three pieces of information to see if the vnode is dirty: - vp->v_type: this can't change while the mntvnode lock is held, because it can only change if the vnode is reclaimed and reused, and you need the mntvnode lock to reclaim a vnode. - vp->v_data: I believe the same comment applies as above; vp->v_data is only manipulated in ffs_vget() and ufs_reclaim(). The first occurs before the vnode is inserted into the list, and the second occurs after it has been removed. - ip->i_flag (where ip == vp->v_data): may possibly require the vnode lock to be held. - vp->v_dirtyblkhd: may possibly require the vnode lock to be held. Actually, I'm willing to take my chances with the latter two; unless there's a possibility that the value read will be corrupted (rather than just stale) in case of a race, it doesn't really matter. There are four possibilities: - vnode is dirty and gets synced: GOOD! - vnode is clean and doesn't get synced: GOOD! - vnode is dirty and doesn't get synced: means it was dirtied while it was being examined by ffs_sync(); the current code already allows that, and the only way to prevent it is to grab a filesystem-wide lock - I don't really see the point. - vnode is clean but gets synced anyway: means it was cleaned while it was being examined by ffs_sync(), which is already possible with the current code (one process calls sync() while another calls fsync()); see above. Somebody on IRC suggested changing ffs_sync() to traverse the synclist instead of the mountpoint's vnode list, and just comparing v_mount to mp and ignoring vnodes that aren't "ours". It would work, but gives me goosebumps for some reason. All of this only solves part of the problem, though - the ffs_sync() part - there's still something screwy with sched_sync(), but I'll need to acquite more profiling data to figure out just *what*. 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 Oct 16 22:33: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id A7BDD37B405; Tue, 16 Oct 2001 22:32:51 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9H5WPT22306; Tue, 16 Oct 2001 22:32:30 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Doug Hass" Cc: "Leo Bicknell" , "Jim Bryant" , "MurrayTaylor" , , Subject: RE: FYI Date: Tue, 16 Oct 2001 22:32:24 -0700 Message-ID: <000901c156cd$19a654a0$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Doug Hass >Sent: Tuesday, October 16, 2001 9:54 AM >To: Ted Mittelstaedt >Cc: Leo Bicknell; Jim Bryant; MurrayTaylor; freebsd-hackers@FreeBSD.ORG; >freebsd-questions@FreeBSD.ORG >Subject: RE: FYI > > >Let's dispense with all the talk about $75 T1 cards that don't exist (and >won't for some time), whose licensing scheme is better, what driver >architecture was developed for what reason and let's get back to the >original issues: > >1) Availability of the 400 series cards. > >If the FreeBSD market has the 400 series cards in such demand, then >someone should be calling me with an order. I'll cut 20% off list for you >if you tell me its for FreeBSD, and I'll still pledge 15% of your purchase >price on top of that toward driver development. I'll give up my volume >margin as a clear indication of my willingness to work with the community. > Well, Murray started all this by asking for ONE WANic 400. ;-) FreeBSD has an eclectic mix of device drivers - some are personal efforts, some are contributed by corporations, some are ports from other OS's and some are a mix of all of the above. The point is that incentives can take forms other than just money. Getting contributed code is a very powerful incentive, and there's a lot of code in the driver modules for the WANic 5xx, 6xx 8xx and the Aries and Maxim cards that Imagestream has driver code for. Is there any way to get some of this - NOT under GPL and NOT under NDA? There's at least one person during this thread who was looking for a DS-3 card like a WANic 8xx You _did_ mention that some of the card modules in SAND are not under NDA? We might be easier getting 10 buyers for DS3 cards than 100 buyers for WANic 4xx cards, if you get my drift. >The drivers BSDI developed and gave to the community for the 400 series >are seriously out of date, by the way. >Last I knew, they still referred >to the cards as the "n2pci" and used some outdated code that has since >been much improved. I'd be interested in working with a developer or >developers to get some updated drivers out there for FreeBSD. Doug, as a FYI, I believe that I can fill in a bit on the state of the sr driver. They don't actually refer to the cards as the n2pci (now, at least) They have had work done to them already by John Hay and Julian. This brings >me to... > >2) Driver development for FreeBSD > >We'll pledge 15% of the purchase of the aforementioned 400 series cards >toward supporting a developer or developers to bring drivers to the >FreeBSD market. The 400 series drivers need to be updated. Yes and no - there is one bug in there that needs killing still but otherwise the driver for the 400 is OK. Let me explain the history as I am aware of it. As you stated, BSDI wrote a driver for the RISCom/N2 card and contributed this back to SDL. I believe that this version made it's way to John Hay and formed the base of the FreeBSD sr driver. At some point, this driver was enhanced by either BSDI or SDL to add support for the later RISCom cards that had an integrated T1 CSU. This support does NOT appear in the FreeBSD driver. It's not possible to use port1 (the one with the CSU port) in a FreeBSD system at this time. It may be that John Hay chopped out this support but more likely he was working with an older version of the driver. I have the source for the later N2 driver that has the integrated CSU. It would be nice if someone would put the CSU support into the FreeBSD driver. I looked at doing it myself but there's now big differences between this BSDI/SDL driver and the one in FreeBSD, too much for me to be able to do it. I would gladly loan a disk with this source plus a later model RISComN2 card with the integrated CSU port to anyone who would do it. I'm sure that someone like Julian or John could do it. At any rate, the FreeBSD fork of this driver was later modified to support the PCI version of the RISCom, the WANic 400/405 cards. Since the WANic 405 series has no integrated CSU, the sr driver works with both ports on it. The sr driver has gone through some debugging by John Hay, and Rodney Grimes. I've worked with Rod on this some, and he has discovered 2 bugs that appear on the WANic405 driver. I've verified that both of these bugs exist. The first bug deals with the interrupt handling of the transmit register. It appears on all RISCom and WANic card variants. Rod has written a patch for this and the patch works. Without the patch, the cards lose packets. John has not gotten a copy of this patch nor integrated it into the current version of the sr driver, unfortunately. The patch is for 1.34.2.2 of the driver that comes in FreeBSD 4.3 and unfortunately Rod got it completed after John made more changes. I don't think Rod has reved it to the current rev. The second bug only appears on WANic 405's and is triggered by high volume rates on both interfaces simultaneously. Rod has been unable to isolate the problem but he and I confirmed that it only appears with dual-port cards. The bug causes about 10% packet loss to be noted on a Pentium 200. I believe that it is possible to minimize the effects of this bug by using the cards in a much faster CPU. Other than that the FreeBSD sr driver is stable, has not caused a crash or other problem on the hardware I've used it on over the last year and a half, on a busy Internet router that runs BGP. >There are a >full line of cards available now that also need drivers. Even if no one >in the community is willing to pledge money (through a card purchase or >directly to a developer), I'm assuming that someone out there would be >interested in developing the drivers. > >Again, if the FreeBSD market has WAN cards in such a high demand, we need >to get developers on the driver development immediately. Now that you >know we are interested, the code is available, and that we've pledged >money toward it, I'd like to see someone in the community start working >toward a solution, instead of complaining about how there isn't one. > Well, we _had_ a solution - the 400/405 that worked well, and has a Netgraph-enabled driver for it. I guess that nobody let you guys know at Imagestream that developers in the FreeBSD community were maintaining the "old" BSDI driver. Sigh. What we don't have is a solution for the 5xx and later cards. But I think that there would be even more interest on a DS3 card like the WANic 8xx Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 22:59: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 972B037B409 for ; Tue, 16 Oct 2001 22:58:56 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9H5wPT22377; Tue, 16 Oct 2001 22:58:26 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "void" Cc: "Matt Dillon" , , Subject: RE: RE: RE: Imagestream WanIC-520 interface cards Date: Tue, 16 Oct 2001 22:58:25 -0700 Message-ID: <001601c156d0$bc3bb360$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: <20011015172147.A32011@parhelion.firedrake.org> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: void [mailto:float@firedrake.org] >Sent: Monday, October 15, 2001 9:22 AM >To: Ted Mittelstaedt >Cc: Matt Dillon; Bsdguru@aol.com; hackers@FreeBSD.ORG >Subject: Re: RE: RE: Imagestream WanIC-520 interface cards > > >On Sat, Oct 13, 2001 at 10:09:44PM -0700, Ted Mittelstaedt wrote: >> >> In our market, and I swear this is true, we have CLEC's that are selling >> fractional T1's (split voice/data with add-drop DSU's) and they >are charging >> less than $50 a month for 768k or greater feeds. It's competitive >with DSL. >> The customer pays for the voice lines which are maybe $1-$5 >cheaper per trunk >> than what the ILEC would charge, then gets in essense a free Internet feed. >> Now, obviously the CLEC is planning on the company growing and >adding trunks >> onto that T1, because they are making their money off the voice >circuits and >> the call termination payments that the RBOC's are paying them. > >I thought the RBOCs got the call termination payment scheme repealed >when it didn't work out in their favor like they thought it would. >But I can't find a reference, at least I haven't yet. > We have been told by our rep at Time Warner Communications that those payments are still continuing. TW (at least in PDX) does not have enough voice sales to be able to get on that pig trough and is equally unhappy as we are that the RBOC's are propping up what are in effect bankrupt CLECs. I used to have sympathy for the CLECs and their beef that the ILEC's are screwing everyone by not allowing competition. But not any more - in our market the CLEC's charge about 95% of what the ILEC charges for voice services, so the customers gain nothing on the voice side of the house. Instead, the way that the CLEC's get customers is by giving away Internet service for free. In short, the call termination payments fund the Internet service, instead of decreasing the cost of the voice service. Basically, the CLEC's have figured out how to use a poor government regulation that needs changing to put their competition out of business. It's no different than what Microsoft does when they use operating system revenue to fund a variety of unprofitable and destructive ventures into software applications like web browsers, web servers, ecommerce apps, etc. The only saving grace is that most of the CLECS are so ignorant when it comes to networking that their Internet service is so awful that at least the good customers are staying away from them for now. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >-- > Ben > >"An art scene of delight > I created this to be ..." -- Sun Ra > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 16 23:52:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wombat.bytecraft.au.com (wombat.bytecraft.au.com [203.39.118.3]) by hub.freebsd.org (Postfix) with ESMTP id 8888237B409; Tue, 16 Oct 2001 23:52:29 -0700 (PDT) Received: from lt99101401.bytecraft.au.com (unknown [203.39.118.42]) by wombat.bytecraft.au.com (Postfix) with SMTP id 614F93F45; Wed, 17 Oct 2001 16:52:26 +1000 (EST) Message-ID: <029301c156d8$45b37cc0$2a7627cb@bytecraft.au.com> Reply-To: "MurrayTaylor" From: "MurrayTaylor" To: "Ted Mittelstaedt" , "Doug Hass" Cc: "Leo Bicknell" , "Jim Bryant" , "MurrayTaylor" , , References: <000901c156cd$19a654a0$1401a8c0@tedm.placo.com> Subject: Re: FYI Date: Wed, 17 Oct 2001 16:52:21 +1000 Organization: Bytecraft Systems 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Ted Mittelstaedt" To: "Doug Hass" Cc: "Leo Bicknell" ; "Jim Bryant" ; "MurrayTaylor" ; ; Sent: Wednesday, October 17, 2001 3:32 PM Subject: RE: FYI > >-----Original Message----- > >From: owner-freebsd-questions@FreeBSD.ORG > >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Doug Hass > >Sent: Tuesday, October 16, 2001 9:54 AM > >To: Ted Mittelstaedt > >Cc: Leo Bicknell; Jim Bryant; MurrayTaylor; freebsd-hackers@FreeBSD.ORG; > >freebsd-questions@FreeBSD.ORG > >Subject: RE: FYI > > > > > >Let's dispense with all the talk about $75 T1 cards that don't exist (and > >won't for some time), whose licensing scheme is better, what driver > >architecture was developed for what reason and let's get back to the > >original issues: > > > >1) Availability of the 400 series cards. > > > >If the FreeBSD market has the 400 series cards in such demand, then > >someone should be calling me with an order. I'll cut 20% off list for you > >if you tell me its for FreeBSD, and I'll still pledge 15% of your purchase > >price on top of that toward driver development. I'll give up my volume > >margin as a clear indication of my willingness to work with the community. > > > > Well, Murray started all this by asking for ONE WANic 400. ;-) > I got my one (1) before the EOL cutoff here in OZ ... and am still looking forward to the next generation .... and to the boss saying "can we create another branch office and link 'em up?" > FreeBSD has an eclectic mix of device drivers - some are personal > efforts, some are contributed by corporations, some are ports from other > OS's and some are a mix of all of the above. The point is that incentives > can take forms other than just money. Getting contributed code is a > very powerful incentive, and there's a lot of code in the driver modules > for the WANic 5xx, 6xx 8xx and the Aries and Maxim cards that > Imagestream has driver code for. > > Is there any way to get some of this - NOT under GPL and NOT under NDA? > There's at least one person during this thread who was looking for a > DS-3 card like a WANic 8xx You _did_ mention that some of the card modules > in SAND are not under NDA? > > We might be easier getting 10 buyers for DS3 cards than 100 buyers for > WANic 4xx cards, if you get my drift. > > >The drivers BSDI developed and gave to the community for the 400 series > >are seriously out of date, by the way. > >Last I knew, they still referred > >to the cards as the "n2pci" and used some outdated code that has since > >been much improved. I'd be interested in working with a developer or > >developers to get some updated drivers out there for FreeBSD. > > Doug, as a FYI, I believe that I can fill in a bit on the state of the sr > driver. They don't actually refer to the cards as the n2pci (now, at least) > They have had work done to them already by John Hay and Julian. > > This brings > >me to... > > > >2) Driver development for FreeBSD > > > >We'll pledge 15% of the purchase of the aforementioned 400 series cards > >toward supporting a developer or developers to bring drivers to the > >FreeBSD market. The 400 series drivers need to be updated. > > Yes and no - there is one bug in there that needs killing still but otherwise > the driver for the 400 is OK. Let me explain the history as I am aware of it. > > As you stated, BSDI wrote a driver for the RISCom/N2 card and contributed > this back to SDL. I believe that this version made it's way to John Hay > and formed the base of the FreeBSD sr driver. > > At some point, this driver was enhanced by either BSDI or SDL to add support > for the later RISCom cards that had an integrated T1 CSU. > > This support does NOT appear in the FreeBSD driver. It's not possible to use > port1 (the one with the CSU port) in a FreeBSD system at this time. It may be > that John Hay chopped out this support but more likely he was working with > an older version of the driver. > > I have the source for the later N2 driver that has the integrated CSU. It > would > be nice if someone would put the CSU support into the FreeBSD driver. I > looked > at doing it myself but there's now big differences between this BSDI/SDL > driver > and the one in FreeBSD, too much for me to be able to do it. I would gladly > loan a disk with this source plus a later model RISComN2 card with the > integrated > CSU port to anyone who would do it. I'm sure that someone like Julian or > John could do it. > > At any rate, the FreeBSD fork of this driver was later modified to support the > PCI version of the RISCom, the WANic 400/405 cards. Since the WANic 405 > series > has no integrated CSU, the sr driver works with both ports on it. > > The sr driver has gone through some debugging by John Hay, and Rodney Grimes. > I've worked with Rod on this some, and he has discovered 2 bugs that appear > on the WANic405 driver. I've verified that both of these bugs exist. > > The first bug deals with the interrupt handling of the transmit register. It > appears on all RISCom and WANic card variants. Rod has written a patch for > this > and the patch works. Without the patch, the cards lose packets. John has > not gotten a copy of this patch nor integrated it into the current version of > the sr driver, unfortunately. The patch is for 1.34.2.2 of the driver that > comes in FreeBSD 4.3 and unfortunately Rod got it completed after John made > more changes. I don't think Rod has reved it to the current rev. > > The second bug only appears on WANic 405's and is triggered by high volume > rates > on both interfaces simultaneously. Rod has been unable to isolate the problem > but he and I confirmed that it only appears with dual-port cards. The bug > causes about 10% > packet loss to be noted on a Pentium 200. I believe that it is possible to > minimize the effects of this bug by using the cards in a much faster CPU. > > Other than that the FreeBSD sr driver is stable, has not caused a crash or > other problem on the hardware I've used it on over the last year and a half, > on a > busy Internet router that runs BGP. > Hear hear ... We have been rock solid with continuous uptime (except when we moved premises) since we started our full time connection... note that I am using the sr-netgraph driver, NOT the base sr driver, so I dont know how much of the original path through the driver code is still followed. > >There are a > >full line of cards available now that also need drivers. Even if no one > >in the community is willing to pledge money (through a card purchase or > >directly to a developer), I'm assuming that someone out there would be > >interested in developing the drivers. > > > >Again, if the FreeBSD market has WAN cards in such a high demand, we need > >to get developers on the driver development immediately. Now that you > >know we are interested, the code is available, and that we've pledged > >money toward it, I'd like to see someone in the community start working > >toward a solution, instead of complaining about how there isn't one. > > > > Well, we _had_ a solution - the 400/405 that worked well, and has a > Netgraph-enabled > driver for it. I guess that nobody let you guys know at Imagestream that > developers in the FreeBSD community were maintaining the "old" BSDI driver. > Sigh. > > What we don't have is a solution for the 5xx and later cards. But I think > that there would be even more interest on a DS3 card like the WANic 8xx > > Ted Mittelstaedt tedm@toybox.placo.com > Author of: The FreeBSD Corporate Networker's Guide > Book website: http://www.freebsd-corp-net-guide.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 4:10:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from w3405.hostcentric.net (w3405.hostcentric.net [216.157.69.254]) by hub.freebsd.org (Postfix) with ESMTP id 0B90137B40B for ; Wed, 17 Oct 2001 04:10:17 -0700 (PDT) Received: by w3405.hostcentric.net (8.10.1/8.9.0) id f9HBAGC18409 for freebsd-hackers@FreeBSD.org; Wed, 17 Oct 2001 07:10:16 -0400 (EDT) Date: Wed, 17 Oct 2001 07:10:16 -0400 (EDT) Message-Id: <200110171110.f9HBAGC18409@w3405.hostcentric.net> From: sales@L5Software.com (L5 Software Development) Subject: Can we help you find more customers? To: undisclosed-recipients:; Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 

Do you have too many customers, too much traffic on your Web site, or what?
No?!?
Then you need MCspider(tm) !! 

MCspider(tm) is a business tool for collecting email addresses from Web pages that meet a user-defined set of criteria.  Using this program, an email address list can be constructed to reach a particular audience.  With MCspider(tm), you can build a list of potential customers that is specific to your business by controlling where and how it searches for addresses.  When connected to the Internet through a cable modem or other reasonably high-speed connection, MCspider(tm) will visit thousands of pages per hour in search of customers for your business.  Since it collects email addresses from publicly available Web sites, you know potential recipients have published their address for the world to know.  You should therefore be able to contact them with little fear of SPAM complaints.

MCspider(tm) is a multi-threaded, fully user configurable Windows application with a complete Help system.  It records the Web pages it visits, in addition to the email addresses it found.  You can therefore rest assured the list it produces is "clean" of duplicates, and that it won't waste time repeatedly looking at the same page for new addresses when it's already found them. 

MCspider(tm) is guaranteed to perform substantially as is described in its documentation, and on its Web page.  Note that this is different from what seems to have become an "industry standard" - the practice of selling software "as-is," without any warranty.  (Have you really read any of the license agreements for software you purchased recently?)  Only by purchasing software from vendors who offer to stand behind their products with a viable warranty can you, the consumer, do anything to combat the proliferation of the "crapware" so common in today's marketplace.

MCspider(tm) was officially released on October 5, 2001 for US$ 249.00 per copy.  However, because of some technical problems with our ordering system, we have decided to extend our pre-release offer until October 20:  Any paid orders received before that date will be granted a 60% discount - only US$ 99.00 per copy.  Please be advised this offer is definitely going to expire at the end of the day Oct. 19.

Act now!  Don't miss out on this special offer!  Go to  http://L5Software.com/go?MCspider  to order your pre-release priced copy today!

In case you're wondering how we got your email address, MCspider(tm) found it in one of the searches we had it do.  The program does work, and quite well!




If you want to be excluded from future mailings by L5Software.com, please go to  http://L5Software.com/cgibin/MailRemove.cgi?freebsd-hackers@FreeBSD.org  to add your address to our list of blocked email addresses.

________________________________________________________________
L5 Software Development - "out of this world" sites and software

MCspider(tm), crawling the World Wide Web for customers
	 http://www.L5Software.com/go?MCspider 
ThmIndxr(tm), the *only* HTML thumbnail/indexer you need!
	 http://www.L5Software.com/go?ThmIndxr 
wCapLock(tm), makes CapsLock work like it does on a typewriter
	 http://www.L5Software.com/go?wCapLock 
BannerAds(tm), join multiple affiliate programs with one banner
	 http://www.L5Software.com/go?BannerAds 
KeywordGo(tm), provides keyword access to your popular pages
	 http://www.L5Software.com/go?KeywordGo
To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 6:43:21 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 5122D37B408 for ; Wed, 17 Oct 2001 06:43:17 -0700 (PDT) Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.6/8.11.6) with ESMTP id f9HDh9b50003; Wed, 17 Oct 2001 09:43:09 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200110171343.f9HDh9b50003@whizzo.transsys.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "Ted Mittelstaedt" Cc: "void" , "Matt Dillon" , Bsdguru@aol.com, hackers@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: Imagestream WanIC-520 interface cards References: <001601c156d0$bc3bb360$1401a8c0@tedm.placo.com> In-reply-to: Your message of "Tue, 16 Oct 2001 22:58:25 PDT." <001601c156d0$bc3bb360$1401a8c0@tedm.placo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Oct 2001 09:43:09 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > We have been told by our rep at Time Warner Communications that those payments > are still continuing. TW (at least in PDX) does not have enough voice sales > to be able to get on that pig trough and is equally unhappy as we are that the > RBOC's are propping up what are in effect bankrupt CLECs. > > I used to have sympathy for the CLECs and their beef that the ILEC's are > screwing everyone by not allowing competition. But not any more - in our > market the CLEC's charge about 95% of what the ILEC charges for voice > services, so the customers gain nothing on the voice side of the house. > Instead, the way that the CLEC's get customers is by giving away Internet > service for free. In short, the call termination payments fund the > Internet service, instead of decreasing the cost of the voice service. > > Basically, the CLEC's have figured out how to use a poor government > regulation that needs changing to put their competition out of business. > It's no different than what Microsoft does when they use operating system > revenue to fund a variety of unprofitable and destructive ventures into > software applications like web browsers, web servers, ecommerce apps, etc. > > The only saving grace is that most of the CLECS are so ignorant when it > comes to networking that their Internet service is so awful that at least > the good customers are staying away from them for now. You have much of this backwards. This whole notion of "reciprocal compensation" for call termination was originally put into the telecom tariffs by the RBOCs to prevent competation in the local space. They figured that the call volume would be asymetrical, with the CLEC customer calling "the rest of the world" connected to the RBOCs. Thus, they created an unlevel playing field and changed the rules of the game. This "poor goverment regulation" is there solely because the RBOCs worked really hard to ensure it would be put there. Surprise, surprise, a bunch of folks came along and decided that the new game was one they could play, and used it to their advantage. D'oh! (And this was sweet, because these same telecom tariffs would be used by the RBOCs on a regular basis to whack their customers/competitors, with the excuse, "Our hands are tied!" Live by the tariff, die by the tariff. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 6:50:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from w3405.hostcentric.net (w3405.hostcentric.net [216.157.69.254]) by hub.freebsd.org (Postfix) with ESMTP id 0706437B40D for ; Wed, 17 Oct 2001 06:50:13 -0700 (PDT) Received: by w3405.hostcentric.net (8.10.1/8.9.0) id f9HDoCW23821 for freebsd-hackers@FreeBSD.org; Wed, 17 Oct 2001 09:50:12 -0400 (EDT) Date: Wed, 17 Oct 2001 09:50:12 -0400 (EDT) Message-Id: <200110171350.f9HDoCW23821@w3405.hostcentric.net> From: sales@L5Software.com (L5 Software Development) Subject: Can we help you find more customers? To: undisclosed-recipients:; Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 

Do you have too many customers, too much traffic on your Web site, or what?
No?!?
Then you need MCspider(tm) !! 

MCspider(tm) is a business tool for collecting email addresses from Web pages that meet a user-defined set of criteria.  Using this program, an email address list can be constructed to reach a particular audience.  With MCspider(tm), you can build a list of potential customers that is specific to your business by controlling where and how it searches for addresses.  When connected to the Internet through a cable modem or other reasonably high-speed connection, MCspider(tm) will visit thousands of pages per hour in search of customers for your business.  Since it collects email addresses from publicly available Web sites, you know potential recipients have published their address for the world to know.  You should therefore be able to contact them with little fear of SPAM complaints.

MCspider(tm) is a multi-threaded, fully user configurable Windows application with a complete Help system.  It records the Web pages it visits, in addition to the email addresses it found.  You can therefore rest assured the list it produces is "clean" of duplicates, and that it won't waste time repeatedly looking at the same page for new addresses when it's already found them. 

MCspider(tm) is guaranteed to perform substantially as is described in its documentation, and on its Web page.  Note that this is different from what seems to have become an "industry standard" - the practice of selling software "as-is," without any warranty.  (Have you really read any of the license agreements for software you purchased recently?)  Only by purchasing software from vendors who offer to stand behind their products with a viable warranty can you, the consumer, do anything to combat the proliferation of the "crapware" so common in today's marketplace.

MCspider(tm) was officially released on October 5, 2001 for US$ 249.00 per copy.  However, because of some technical problems with our ordering system, we have decided to extend our pre-release offer until October 20:  Any paid orders received before that date will be granted a 60% discount - only US$ 99.00 per copy.  Please be advised this offer is definitely going to expire at the end of the day Oct. 19.

Act now!  Don't miss out on this special offer!  Go to  http://L5Software.com/go?MCspider  to order your pre-release priced copy today!

In case you're wondering how we got your email address, MCspider(tm) found it in one of the searches we had it do.  The program does work, and quite well!




If you want to be excluded from future mailings by L5Software.com, please go to  http://L5Software.com/cgibin/MailRemove.cgi?freebsd-hackers@FreeBSD.org  to add your address to our list of blocked email addresses.

________________________________________________________________
L5 Software Development - "out of this world" sites and software

MCspider(tm), crawling the World Wide Web for customers
	 http://www.L5Software.com/go?MCspider 
ThmIndxr(tm), the *only* HTML thumbnail/indexer you need!
	 http://www.L5Software.com/go?ThmIndxr 
wCapLock(tm), makes CapsLock work like it does on a typewriter
	 http://www.L5Software.com/go?wCapLock 
BannerAds(tm), join multiple affiliate programs with one banner
	 http://www.L5Software.com/go?BannerAds 
KeywordGo(tm), provides keyword access to your popular pages
	 http://www.L5Software.com/go?KeywordGo
To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 7: 5:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id CCAA337B405; Wed, 17 Oct 2001 07:05:42 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id JAA16703; Wed, 17 Oct 2001 09:04:46 -0500 Date: Wed, 17 Oct 2001 09:04:46 -0500 (EST) From: Doug Hass To: Ted Mittelstaedt Cc: Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: RE: FYI In-Reply-To: <000901c156cd$19a654a0$1401a8c0@tedm.placo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Is there any way to get some of this - NOT under GPL and NOT under NDA? > There's at least one person during this thread who was looking for a > DS-3 card like a WANic 8xx You _did_ mention that some of the card modules > in SAND are not under NDA? All of the code is licensed under either the LGPL or is available only under NDA. Neither of these should present a problem for developers who want to write FreeBSD drivers (whether they are based on the LGPL'ed SAND or are monolithic). > We might be easier getting 10 buyers for DS3 cards than 100 buyers for > WANic 4xx cards, if you get my drift. Well, if people don't mind buying cards with no drivers...The reason for offering the 400 series at a discount was to solve the supply issue that you raised originally. > Doug, as a FYI, I believe that I can fill in a bit on the state of the sr > driver. They don't actually refer to the cards as the n2pci (now, at least) > They have had work done to them already by John Hay and Julian. I'm glad to hear that the name was corrected. If someone is interested, there is a newer development kit (actually several newer ones) that would improve that driver significantly, especially in high load situations. I'm certain that those improvements are not in the driver, since the development kit containing them is only available under license. > This support does NOT appear in the FreeBSD driver. It's not possible to use > port1 (the one with the CSU port) in a FreeBSD system at this time. It may be > that John Hay chopped out this support but more likely he was working with > an older version of the driver. There's no reason that you can't use the N2csu port in a FreeBSD system. The code to do this has been freely available for nearly 6 years. We released a version of the n2 code to open source as well. > The second bug only appears on WANic 405's and is triggered by high > volume rates on both interfaces simultaneously. Rod has been unable to > isolate the problem but he and I confirmed that it only appears with > dual-port cards. The bug causes about 10% packet loss to be noted on a > Pentium 200. I believe that it is possible to minimize the effects of > this bug by using the cards in a much faster CPU. Actually, it will happen with the one-port cards, too. As you increase the CPU or the clock rate, the problem gets worse. We've fixed this (among other things), which is why I recommended getting ahold of the newer DDK. > Other than that the FreeBSD sr driver is stable, has not caused a crash > or other problem on the hardware I've used it on over the last year and > a half, on a busy Internet router that runs BGP. Great! That's what I like to hear. The hardware is quite reliable and well-proven, and I'm glad your drivers are working well. > Well, we _had_ a solution - the 400/405 that worked well, and has a > Netgraph-enabled driver for it. I guess that nobody let you guys know > at Imagestream that developers in the FreeBSD community were maintaining > the "old" BSDI driver. Sigh. We knew that the driver had undergone some maintainence. It still has bugs, and doesn't take advantage of the later code advances in the development kit, but if it works well enough for you, then that's not an issue. If you don't want to improve the driver beyond where it is now, that's definitely up to you. You know that improvements and bug fixes exist if you ever decide they are affect your use of the card enough to put them in place. > What we don't have is a solution for the 5xx and later cards. But I think > that there would be even more interest on a DS3 card like the WANic 8xx Development tools for the later cards have been freely available (under NDA) for 5 years now. No one is holding anyone in the FreeBSD community back. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 8: 7:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id 8581637B405; Wed, 17 Oct 2001 08:07:40 -0700 (PDT) Received: from localhost (thomas@localhost) by brunel.uk1.vbc.net (8.11.6/8.11.6) with ESMTP id f9HF7cI24606; Wed, 17 Oct 2001 16:07:39 +0100 (BST) Date: Wed, 17 Oct 2001 16:07:38 +0100 (BST) From: Thomas Dixon To: John Baldwin Cc: Thomas Dixon , hackers@FreeBSD.org Subject: RE: Problems with booting of CD-ROM (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 16 Oct 2001, John Baldwin wrote: > > On 16-Oct-01 Thomas Dixon wrote: > > I'm trying to make a bootable CD using the cdboot program that come with > > freeBSD in /sys/i386/boot/cdboot. The computer I'm trying to do this on > > definately boots other CDs as it has booted several other CDs. However > > using a CD I've made using mkisofs and cdboot it gives the error; > > > > Your BIOS int 0x13 extensions seem to be disabled. > > It's impossible to boot a CD-ROM without them. > > (BIOS int 0x13 fn 0x4b01 yielded error 1) > > > > I'm using an Asus P5A motherboard, there appears to be no way to enable > > the int 0x13 extensions in the BIOS and there is nothing in the manual > > that refers to these. > > > > Any ideas why this error is coming up or how to fix it? > > Don't use cdboot or cdldr, they don't qutie work yet. :( > > Instead, make a floppy image and use that to boot. > I've tried this and I couldn't figure out the syntax for loader.rc to load the file system from the cd-rom, any ideas? - Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 8:48:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 393B637B405 for ; Wed, 17 Oct 2001 08:48:40 -0700 (PDT) Received: from onyx (onyx.cs.binghamton.edu [128.226.140.171]) by bingnet2.cc.binghamton.edu (8.11.6/8.11.6) with ESMTP id f9HFmdS04466 for ; Wed, 17 Oct 2001 11:48:39 -0400 (EDT) Date: Wed, 17 Oct 2001 11:47:48 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@onyx To: freebsd-hackers@freebsd.org Subject: Limiting closed port RST response Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I was using FreeBSD a while ago, suddenly a lot of messages show up: Limiting closed port RST responses from 224 to 200 packets per seconds. These messages persist even after reboot. What happened? What should I do? Thanks! -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 9:10:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 47E3B37B401 for ; Wed, 17 Oct 2001 09:10:18 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 17 Oct 2001 17:10:17 +0100 (BST) Date: Wed, 17 Oct 2001 17:10:16 +0100 From: David Malone To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: Limiting closed port RST response Message-ID: <20011017171016.A66131@walton.maths.tcd.ie> 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 zzhang@cs.binghamton.edu on Wed, Oct 17, 2001 at 11:47:48AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Oct 17, 2001 at 11:47:48AM -0400, Zhihui Zhang wrote: > > I was using FreeBSD a while ago, suddenly a lot of messages show up: > > Limiting closed port RST responses from 224 to 200 packets per seconds. > > These messages persist even after reboot. What happened? What should I do? Could someone be port scanning you? Another possibility is that you alot of machines are trying to contact a TCP service on the machine in question, which isn't running. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 9:13:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 370BA37B403; Wed, 17 Oct 2001 09:13:41 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9HGCAT24188; Wed, 17 Oct 2001 09:12:15 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Doug Hass" Cc: "Leo Bicknell" , "Jim Bryant" , "MurrayTaylor" , , Subject: RE: FYI Date: Wed, 17 Oct 2001 09:12:10 -0700 Message-ID: <009301c15726$797d19a0$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Doug Hass >Sent: Wednesday, October 17, 2001 7:05 AM >To: Ted Mittelstaedt >Cc: Leo Bicknell; Jim Bryant; MurrayTaylor; freebsd-hackers@FreeBSD.ORG; >freebsd-questions@FreeBSD.ORG >Subject: RE: FYI > > >We knew that the driver had undergone some maintainence. It still has >bugs, and doesn't take advantage of the later code advances in the >development kit, but if it works well enough for you, then that's not an >issue. If you don't want to improve the driver beyond where it is now, >that's definitely up to you. You know that improvements and bug fixes >exist if you ever decide they are affect your use of the card enough to >put them in place. > >> What we don't have is a solution for the 5xx and later cards. But I think >> that there would be even more interest on a DS3 card like the WANic 8xx > >Development tools for the later cards have been freely available (under >NDA) for 5 years now. No one is holding anyone in the FreeBSD community >back. > Doug, in the entire history of the FreeBSD project, when given a choice between a better driver or code that is closed source, and a worse driver that has open source, the FreeBSD community has never chosen the driver or code with closed source. In fact I can only remember ONCE that the Project has recommended against freely available BSD code - and they did so in favor of GPL code, not closed source code - and this was for the coprocessor emulator (used for 386 and 486SX chips only) If you never keep anything else in mind about FreeBSD, then keep this one thing. FreeBSD is not about closed source. It's about freely available BSD source that is more free even than GPL. If any of the WANic 4xx driver authors had ever signed an NDA or looked at the NDA'd Imagestream code, they could never have touched the BSD driver ever again, without risk of contaminating the open source driver code. We take things like this very seriously. The only time that FreeBSD gets involved in closed-source code is when there is simply NO other alternative - like in this case where the register interface specs are being withheld. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 9:25:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 2AD8837B408 for ; Wed, 17 Oct 2001 09:25:21 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9HGORT24248; Wed, 17 Oct 2001 09:24:33 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Louis A. Mamakos" Cc: "void" , "Matt Dillon" , , Subject: RE: Imagestream WanIC-520 interface cards Date: Wed, 17 Oct 2001 09:24:27 -0700 Message-ID: <009501c15728$30ac6f80$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: <200110171343.f9HDh9b50003@whizzo.transsys.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: louie@whizzo.transsys.com [mailto:louie@whizzo.transsys.com]On >Behalf Of Louis A. Mamakos >Sent: Wednesday, October 17, 2001 6:43 AM >To: Ted Mittelstaedt >Cc: void; Matt Dillon; Bsdguru@aol.com; hackers@FreeBSD.ORG >Subject: Re: Imagestream WanIC-520 interface cards > > > >> >> We have been told by our rep at Time Warner Communications that >those payments >> are still continuing. TW (at least in PDX) does not have enough >voice sales >> to be able to get on that pig trough and is equally unhappy as we >are that the >> RBOC's are propping up what are in effect bankrupt CLECs. >> >> I used to have sympathy for the CLECs and their beef that the ILEC's are >> screwing everyone by not allowing competition. But not any more - in our >> market the CLEC's charge about 95% of what the ILEC charges for voice >> services, so the customers gain nothing on the voice side of the house. >> Instead, the way that the CLEC's get customers is by giving away Internet >> service for free. In short, the call termination payments fund the >> Internet service, instead of decreasing the cost of the voice service. >> >> Basically, the CLEC's have figured out how to use a poor government >> regulation that needs changing to put their competition out of business. >> It's no different than what Microsoft does when they use operating system >> revenue to fund a variety of unprofitable and destructive ventures into >> software applications like web browsers, web servers, ecommerce apps, etc. >> >> The only saving grace is that most of the CLECS are so ignorant when it >> comes to networking that their Internet service is so awful that at least >> the good customers are staying away from them for now. > >You have much of this backwards. > >This whole notion of "reciprocal compensation" for call termination was >originally put into the telecom tariffs by the RBOCs to prevent competation >in the local space. They figured that the call volume would be asymetrical, >with the CLEC customer calling "the rest of the world" connected to the >RBOCs. Thus, they created an unlevel playing field and changed the rules >of the game. This "poor goverment regulation" is there solely because >the RBOCs worked really hard to ensure it would be put there. > >Surprise, surprise, a bunch of folks came along and decided that the >new game was one they could play, and used it to their advantage. D'oh! >(And this was sweet, because these same telecom tariffs would be used >by the RBOCs on a regular basis to whack their customers/competitors, >with the excuse, "Our hands are tied!" > I am perfectly aware of this. The RBOCs deserved to have those "fines" levied against them for a number of years, to punish them for attempting to block the CLECs. However, it's been long enough for this, and in fact the money from the RBOCs is no longer being used to increase the CLEC's reach or service area (ie: infrastructure) and being used by the CLECS to bash each other, instead of bashing the RBOCS. The situation is equivalent to Foreign Aid that the US pays to a country such as Japan. (which we still do to the tune of millions and millions of dollars a year) Japan has long since ceased being a poor relation that needs to be bailed out. The reasons for them being paid off by the US have been fulfilled. Yet, the payments continue, and the money is being used to free up other funding that's being spent on political - not necessary - things. >Live by the tariff, die by the tariff. > then there's also the saw about the kid won't never amount to anything if mommy's apron strings aren't ever cut. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 9:25:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id 08E5637B401; Wed, 17 Oct 2001 09:25:46 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id LAA31166; Wed, 17 Oct 2001 11:19:06 -0500 Date: Wed, 17 Oct 2001 11:19:06 -0500 (EST) From: Doug Hass To: Ted Mittelstaedt Cc: Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: RE: FYI In-Reply-To: <009301c15726$797d19a0$1401a8c0@tedm.placo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Doug, in the entire history of the FreeBSD project, when given a choice > between a better driver or code that is closed source, and a worse > driver that has open source, the FreeBSD community has never chosen the > driver or code with closed source. In fact I can only remember ONCE > that the Project has recommended against freely available BSD code - and > they did so in favor of GPL code, not closed source code - and this was > for the coprocessor emulator (used for 386 and 486SX chips only) > The only time that FreeBSD gets involved in closed-source code is when > there is simply NO other alternative - like in this case where the > register interface specs are being withheld. We certainly support the right for companies to protect their intellectual property in whatever way they see fit, even if the FreeBSD community does not. The lack of flexibility in accepting various requirements illustrates the difference between an OS WITH legs in the market and one WITHOUT legs. Much to my chagrin, FreeBSD continues to fall more and more into the latter category. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 9:36:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id E960937B408 for ; Wed, 17 Oct 2001 09:36:36 -0700 (PDT) Received: from mindspring.com (dialup-209.245.132.242.Dial1.SanJose1.Level3.net [209.245.132.242]) by falcon.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f9HGaQD29656; Wed, 17 Oct 2001 09:36:26 -0700 (PDT) Message-ID: <3BCDB3BE.1B2E6AC6@mindspring.com> Date: Wed, 17 Oct 2001 09:37:18 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: David Malone Cc: Zhihui Zhang , freebsd-hackers@freebsd.org Subject: Re: Limiting closed port RST response References: <20011017171016.A66131@walton.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Malone wrote: > > I was using FreeBSD a while ago, suddenly a lot of messages show up: > > > > Limiting closed port RST responses from 224 to 200 packets per seconds. > > > > These messages persist even after reboot. What happened? What should I do? > > Could someone be port scanning you? Another possibility is that you > alot of machines are trying to contact a TCP service on the machine > in question, which isn't running. I've seen this while doing load testing. In general, you want the limit threshold to be higher than the connections per second rate, or you will get this message. I have modified my code locally to crank it up to twice the listen queue depth. Frequently, you are just better off by turning of the limiting entirely (there's s sysctl; look at the code in netinet that emits the message, or grep sysctl -A for "lim"). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 9:36:45 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 E006037B40D; Wed, 17 Oct 2001 09:36:35 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f9HGkHs00996; Wed, 17 Oct 2001 09:46:17 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200110171646.f9HGkHs00996@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug Hass Cc: Ted Mittelstaedt , Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI In-reply-to: Your message of "Wed, 17 Oct 2001 11:19:06 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Oct 2001 09:46:17 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Doug, in the entire history of the FreeBSD project, when given a choice > > between a better driver or code that is closed source, and a worse > > driver that has open source, the FreeBSD community has never chosen the > > driver or code with closed source. In fact I can only remember ONCE > > that the Project has recommended against freely available BSD code - and > > they did so in favor of GPL code, not closed source code - and this was > > for the coprocessor emulator (used for 386 and 486SX chips only) > > > The only time that FreeBSD gets involved in closed-source code is when > > there is simply NO other alternative - like in this case where the > > register interface specs are being withheld. > > We certainly support the right for companies to protect their intellectual > property in whatever way they see fit, even if the FreeBSD community does > not. Doug; I would recommend against falling for Ted's flamebait here, since that's really all it is. His characterisation of the FreeBSD Project's attitude towards proprietary drivers fails to mention many of the other factors that get weighed into these decisions, and I think he's missing a lot of history. > The lack of flexibility in accepting various requirements illustrates the > difference between an OS WITH legs in the market and one WITHOUT legs. And you probably shouldn't try to respond with generalisations that are meant to be personal attacks. Think about who you're trying to endear yourself to, eh? > Much to my chagrin, FreeBSD continues to fall more and more into the > latter category. If we're legless, it's probably because we're drunk on our own success. 8) Seriously though; if you don't want to release sources for a driver for whatever reason, that's fine. But bear in mind that if you don't support your binary-only driver in a realistic and attentive fashion, you're going to make people unhappy, and they will turn to solutions that they can maintain themselves, or that they can badger other people into maintaining. 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 Oct 17 9:58:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail4.sdc1.sfba.home.com (femail4.sdc1.sfba.home.com [24.0.95.84]) by hub.freebsd.org (Postfix) with ESMTP id 1467C37B403 for ; Wed, 17 Oct 2001 09:58:25 -0700 (PDT) Received: from laptop.baldwin.cx ([24.2.39.156]) by femail4.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20011017165824.QZEF15859.femail4.sdc1.sfba.home.com@laptop.baldwin.cx>; Wed, 17 Oct 2001 09:58:24 -0700 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: Date: Tue, 16 Oct 2001 21:34:59 -0700 (PDT) From: John Baldwin To: Thomas Dixon Subject: RE: Problems with booting of CD-ROM (fwd) Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 17-Oct-01 Thomas Dixon wrote: > > > On Tue, 16 Oct 2001, John Baldwin wrote: > >> >> On 16-Oct-01 Thomas Dixon wrote: >> > I'm trying to make a bootable CD using the cdboot program that come with >> > freeBSD in /sys/i386/boot/cdboot. The computer I'm trying to do this on >> > definately boots other CDs as it has booted several other CDs. However >> > using a CD I've made using mkisofs and cdboot it gives the error; >> > >> > Your BIOS int 0x13 extensions seem to be disabled. >> > It's impossible to boot a CD-ROM without them. >> > (BIOS int 0x13 fn 0x4b01 yielded error 1) >> > >> > I'm using an Asus P5A motherboard, there appears to be no way to enable >> > the int 0x13 extensions in the BIOS and there is nothing in the manual >> > that refers to these. >> > >> > Any ideas why this error is coming up or how to fix it? >> >> Don't use cdboot or cdldr, they don't qutie work yet. :( >> >> Instead, make a floppy image and use that to boot. >> > I've tried this and I couldn't figure out the syntax for loader.rc to load > the file system from the cd-rom, any ideas? You don't really load the filesystem from the CD-ROM as the loader can't read a CD-ROM right now. Instead you use a memory filesystem on the floppy image and use that to boostrap yourself so you can mount the CD. > - Tom -- 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 Wed Oct 17 10: 5:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 2C2F637B401 for ; Wed, 17 Oct 2001 10:05:42 -0700 (PDT) Received: (qmail 47910 invoked by uid 1000); 17 Oct 2001 17:05:38 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Oct 2001 17:05:38 -0000 Date: Wed, 17 Oct 2001 12:05:38 -0500 (CDT) From: Mike Silbersack To: Terry Lambert Cc: David Malone , Zhihui Zhang , Subject: Re: Limiting closed port RST response In-Reply-To: <3BCDB3BE.1B2E6AC6@mindspring.com> Message-ID: <20011017120330.H47595-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 17 Oct 2001, Terry Lambert wrote: > > Could someone be port scanning you? Another possibility is that you > > alot of machines are trying to contact a TCP service on the machine > > in question, which isn't running. > > I've seen this while doing load testing. > > In general, you want the limit threshold to be higher than > the connections per second rate, or you will get this message. > > I have modified my code locally to crank it up to twice the > listen queue depth. Frequently, you are just better off by > turning of the limiting entirely (there's s sysctl; look at > the code in netinet that emits the message, or grep sysctl -A > for "lim"). > > -- Terry Wouldn't fixing your code so that it isn't dropping connections be a better plan? When things are working properly, there should be no need for RSTs to be thrown around the network. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 10:11:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 10F8E37B405 for ; Wed, 17 Oct 2001 10:11:51 -0700 (PDT) Received: (qmail 47933 invoked by uid 1000); 17 Oct 2001 17:11:05 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Oct 2001 17:11:05 -0000 Date: Wed, 17 Oct 2001 12:11:05 -0500 (CDT) From: Mike Silbersack To: Zhihui Zhang Cc: Subject: Re: Limiting closed port RST response In-Reply-To: Message-ID: <20011017120846.H47595-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 17 Oct 2001, Zhihui Zhang wrote: > > I was using FreeBSD a while ago, suddenly a lot of messages show up: > > Limiting closed port RST responses from 224 to 200 packets per seconds. > > These messages persist even after reboot. What happened? What should I do? > Thanks! > > -Zhihui Sounds like nmap - it appears to rate limit its portscans to the rate at which it is receiving replies. You could lower the icmplim to frustrate the portscanners more. (Although if they had any skill you wouldn't be noticing their scan, so perhaps that doesn't matter.) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 10:19:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id AE27A37B401; Wed, 17 Oct 2001 10:19:35 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id MAA06133; Wed, 17 Oct 2001 12:19:34 -0500 Date: Wed, 17 Oct 2001 12:19:34 -0500 (EST) From: Doug Hass To: Mike Smith Cc: Ted Mittelstaedt , Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI In-Reply-To: <200110171646.f9HGkHs00996@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > We certainly support the right for companies to protect their intellectual > > property in whatever way they see fit, even if the FreeBSD community does > > not. > > Doug; I would recommend against falling for Ted's flamebait here, since > that's really all it is. His characterisation of the FreeBSD Project's > attitude towards proprietary drivers fails to mention many of the other > factors that get weighed into these decisions, and I think he's missing a > lot of history. I'm glad someone else is speaking up--all I've heard is Ted's point of view (from him, and from others who have said the same thing: FreeBSD only accepts BSD licensed code, period.) > > The lack of flexibility in accepting various requirements illustrates the > > difference between an OS WITH legs in the market and one WITHOUT legs. > > And you probably shouldn't try to respond with generalisations that are > meant to be personal attacks. Think about who you're trying to endear > yourself to, eh? > > > Much to my chagrin, FreeBSD continues to fall more and more into the > > latter category. > > If we're legless, it's probably because we're drunk on our own success. 8) It's not a generalization at all. Honestly, compared to the market traction that Linux, VxWorks, Solaris and others have, FreeBSD is definitely without legs. The WAN card and RAS card markets are good examples of where the attitude toward "BSD-licensed code or bust" has resulted in FreeBSD being largely left out of the party. Three of the largest manufacturers in these segments (SBS, Cyclades, and Ariel) all support Linux and NT, but do not have BSD support. I've been frusturated repeatedly over the past few years as I try to continue to use FreeBSD myself for different applications. It's too bad we can't find a way to include more companies and solutions instead of continuing to find ways to EXCLUDE them... > Seriously though; if you don't want to release sources for a driver for > whatever reason, that's fine. But bear in mind that if you don't support > your binary-only driver in a realistic and attentive fashion, you're > going to make people unhappy, and they will turn to solutions that they > can maintain themselves, or that they can badger other people into > maintaining. Agreed. Maintaining code has never been a problem for us. We're talking about someone else in the FreeBSD community maintaining these drivers, though, not ImageStream. Their attentiveness to bugs would directly impact that. This will be my last message on this topic. I feel as if this discussion is going round and round and has no real end or purpose at this point. I'll quit wasting bandwidth. :-) If anyone has an interest in adding support for the SBS WAN cards to FreeBSD, feel free to contact me. I'll be glad to help. Regards, Doug ----- Doug Hass ImageStream Internet Solutions dhass@imagestream.com http://www.imagestream.com Office: 1-219-935-8484 Fax: 1-219-935-8488 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 10:27:39 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 CEED537B403 for ; Wed, 17 Oct 2001 10:27:36 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f9HHQYB34444; Wed, 17 Oct 2001 13:26:35 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 17 Oct 2001 13:26:34 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jim Pirzyk Cc: freebsd-hackers@freebsd.org Subject: Re: truss vs ktrace In-Reply-To: <3BCCCF74.75B7F36C@disney.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG There are a fair number of differences, but from my perspective, one of the primary ones is that truss relies on procfs, whereas ktrace uses a seperate kernel tracing facility. For sites wanting to avoid procfs due to its history of security vulnerabilities, having truss rely on procfs means that truss can't be used. truss could probably be easily rewritten to use ptrace() instead. It will be interesting to see how the usefulness of both of these tools changes/evolves due to increases use of threadings and kse. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Tue, 16 Oct 2001, Jim Pirzyk wrote: > So which should I use? Why is there two around? I see that truss has > less command line switches than ktrace, but it is a little bit more > standard. > > I also see that truss works with the linux syscalls where ktrace does > not > remap the syscall names. > > - JimP > > -- > --- @(#) $Id: dot.signature,v 1.10 2001/05/17 23:38:49 Jim.Pirzyk Exp $ > __o Jim.Pirzyk@disney.com ------------- pirzyk@freebsd.org > _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation > (*)/ (*) > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 10:38:47 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 70AA537B403; Wed, 17 Oct 2001 10:38:40 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f9HHo7s01640; Wed, 17 Oct 2001 10:50:07 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200110171750.f9HHo7s01640@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug Hass Cc: Ted Mittelstaedt , Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI In-reply-to: Your message of "Wed, 17 Oct 2001 12:19:34 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Oct 2001 10:50:07 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > It's not a generalization at all. Honestly, compared to the market > traction that Linux, VxWorks, Solaris and others have, FreeBSD is > definitely without legs. The WAN card and RAS card markets are good > examples of where the attitude toward "BSD-licensed code or bust" has > resulted in FreeBSD being largely left out of the party. The point I was trying to make here is that there *is* no such attitude. > Three of the > largest manufacturers in these segments (SBS, Cyclades, and Ariel) all > support Linux and NT, but do not have BSD support. ... yet Linux has a far more entrenched and outspoken "GPLed code or bust" attitude than this mythical "BSD-licensed code or bust" attitude that you allude to. > It's too bad we can't find a way to include more companies and > solutions instead of continuing to find ways to EXCLUDE them... We do try; before I left BSDi this was one of my goals. We certainly don't try to exclude them, just the opposite; we've provided support for companies developing in-house drivers. We have a module architecture that makes writing, maintaining and deploying binary-only drivers a snap. > If anyone has an interest in adding support for the SBS WAN cards to > FreeBSD, feel free to contact me. I'll be glad to help. Just package your driver with your cards, or stick it on your support site. The whole point being that you don't *have* to get your code into the tree; you can maintain it successfully without either a) introducing overhead for us handling your module, or b) introducing latency for you trying to push a new version through our release process. I get the impression you haven't quite gotten the idea here yet; you don't *need* to be in the base distribution, and in many cases it's better not to be simply because it involves less work for everyone. 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 Oct 17 10:40:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by hub.freebsd.org (Postfix) with ESMTP id CBEEE37B407; Wed, 17 Oct 2001 10:40:29 -0700 (PDT) Received: (from ambrisko@localhost) by ambrisko.com (8.11.6/8.11.6) id f9HHdsr11462; Wed, 17 Oct 2001 10:39:54 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200110171739.f9HHdsr11462@ambrisko.com> Subject: Re: Problems with booting of CD-ROM (fwd) In-Reply-To: To: Thomas Dixon Date: Wed, 17 Oct 2001 10:39:54 -0700 (PDT) Cc: John Baldwin , hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thomas Dixon writes: | | | On Tue, 16 Oct 2001, John Baldwin wrote: | | > | > On 16-Oct-01 Thomas Dixon wrote: | > > I'm trying to make a bootable CD using the cdboot program that come with | > > freeBSD in /sys/i386/boot/cdboot. The computer I'm trying to do this on | > > definately boots other CDs as it has booted several other CDs. However | > > using a CD I've made using mkisofs and cdboot it gives the error; | > > | > > Your BIOS int 0x13 extensions seem to be disabled. | > > It's impossible to boot a CD-ROM without them. | > > (BIOS int 0x13 fn 0x4b01 yielded error 1) | > > | > > I'm using an Asus P5A motherboard, there appears to be no way to enable | > > the int 0x13 extensions in the BIOS and there is nothing in the manual | > > that refers to these. | > > | > > Any ideas why this error is coming up or how to fix it? | > | > Don't use cdboot or cdldr, they don't qutie work yet. :( | > | > Instead, make a floppy image and use that to boot. | > | I've tried this and I couldn't figure out the syntax for loader.rc to load | the file system from the cd-rom, any ideas? I'd skip the MFS step and just put the kernel on the boot floppy with loader and friends. Then in /boot/loader.rc add: boot -C So it looks something like: \ Loader.rc \ $FreeBSD: src/sys/boot/forth/loader.rc,v 1.2 1999/11/24 17:59:37 dcs Exp $ \ \ Includes additional commands include /boot/loader.4th \ Reads and processes loader.rc start \ Tests for password -- executes autoboot first if a password was defined check-password \ Unless set otherwise, autoboot is automatic at this point boot -C Atleast this works for me even on IBM machine as of 4.4-Release! If you run out of room for your kernel (even if you gzip it) you can kldload modules off the CD during startup. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 10:50:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id 7135D37B401; Wed, 17 Oct 2001 10:50:50 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id MAA09447; Wed, 17 Oct 2001 12:50:49 -0500 Date: Wed, 17 Oct 2001 12:50:48 -0500 (EST) From: Doug Hass To: Mike Smith Cc: Ted Mittelstaedt , Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI In-Reply-To: <200110171750.f9HHo7s01640@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > If anyone has an interest in adding support for the SBS WAN cards to > > FreeBSD, feel free to contact me. I'll be glad to help. > > Just package your driver with your cards, or stick it on your support > site. The whole point being that you don't *have* to get your code into > the tree; you can maintain it successfully without either a) introducing > overhead for us handling your module, or b) introducing latency for you > trying to push a new version through our release process. > > I get the impression you haven't quite gotten the idea here yet; you > don't *need* to be in the base distribution, and in many cases it's > better not to be simply because it involves less work for everyone. O.k.--one more message. :-) We don't want to be in the base distribution. Never have wanted to be, nor have I indicated in my messages that we wanted to be. All we would like to see drivers for FreeBSD available in the market. Period. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 10:57:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 1FE4937B408; Wed, 17 Oct 2001 10:57:05 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 2CEA081D09; Wed, 17 Oct 2001 12:57:05 -0500 (CDT) Date: Wed, 17 Oct 2001 12:57:05 -0500 From: Alfred Perlstein To: Doug Hass Cc: Mike Smith , Ted Mittelstaedt , Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI Message-ID: <20011017125705.H65676@elvis.mu.org> References: <200110171750.f9HHo7s01640@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dhass@imagestream.com on Wed, Oct 17, 2001 at 12:50:48PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Doug Hass [011017 12:51] wrote: > > > If anyone has an interest in adding support for the SBS WAN cards to > > > FreeBSD, feel free to contact me. I'll be glad to help. > > > > Just package your driver with your cards, or stick it on your support > > site. The whole point being that you don't *have* to get your code into > > the tree; you can maintain it successfully without either a) introducing > > overhead for us handling your module, or b) introducing latency for you > > trying to push a new version through our release process. > > > > I get the impression you haven't quite gotten the idea here yet; you > > don't *need* to be in the base distribution, and in many cases it's > > better not to be simply because it involves less work for everyone. > > O.k.--one more message. :-) > > We don't want to be in the base distribution. Never have wanted to be, > nor have I indicated in my messages that we wanted to be. > > All we would like to see drivers for FreeBSD available in the market. > Period. Even if you wanted it in the base source under a GPL license, we could put it under sys/contrib which is where we put things with questionable licenses. We've also given CVS access to "gateway" developers at companies in order to improve on their drivers in the past and allow us to modify the driver to take into account for interface changes within our bus and system archetectures. Having it in the base is actually kind of cool and doesn't require much effort, the only problem I see is that what you want to add requires a subsystem that is under unfavourable license restrictions that might require modifications to the base. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' http://www.morons.org/rants/gpl-harmful.php3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 11:10:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id 3CB5837B405; Wed, 17 Oct 2001 11:10:26 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id NAA11287; Wed, 17 Oct 2001 13:10:23 -0500 Date: Wed, 17 Oct 2001 13:10:23 -0500 (EST) From: Doug Hass To: void Cc: Mike Smith , Ted Mittelstaedt , Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI In-Reply-To: <20011017190720.C21886@parhelion.firedrake.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If you didn't say it, then you weren't the one I was talking about, was I? :-) I got several other private mails saying that BSD licensed code was the one and only way, and 2 or 3 mails (from Ben, among others) saying that BSD-licensed was preferred. Either approach is as flawed as someone who claims GPL only or GPL preferred. The license terms of add-on drivers and products should be set according to the needs of the authoring person or company, in my opinion. Doug On Wed, 17 Oct 2001, void wrote: > On Wed, Oct 17, 2001 at 12:19:34PM -0500, Doug Hass wrote: > > > > I'm glad someone else is speaking up--all I've heard is Ted's point of > > view (from him, and from others who have said the same thing: FreeBSD only > > accepts BSD licensed code, period.) > > I said to you in private mail that where there's a BSD-licensed solution > and a non-BSD-licensed solution, all else being roughly equal, FreeBSD > tends towards the BSD-licensed solution. Not the same thing at all. > > -- > Ben > > "An art scene of delight > I created this to be ..." -- Sun Ra > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 11:15:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 20EE437B405; Wed, 17 Oct 2001 11:15:27 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9HIF2a39799; Wed, 17 Oct 2001 20:15:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Doug Hass Cc: void , Mike Smith , Ted Mittelstaedt , Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI In-Reply-To: Your message of "Wed, 17 Oct 2001 13:10:23 CDT." Date: Wed, 17 Oct 2001 20:15:02 +0200 Message-ID: <39797.1003342502@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Let me cut through all this with a bit of experience if you permit: 1. BSD licensed sources are undoubtedly always preferred. 2. Other open-source licences are the best alternative. 3. closed source solutions are always risky because you don't know if the company will be willing to, or even around to, update the driver for future versions of the OS. One way to moderate #3 is to do as we did with the DiskOnChip driver for M-systems flash-disks: They gave a copy under NDA to an open source developer (me) who then produces an object only driver. That way at least one person will be able to produce new versions of the driver if the company goes titsup.com or gets bought by M$ or whatever... Over and out... -- 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 Oct 17 11:19:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from w3405.hostcentric.net (w3405.hostcentric.net [216.157.69.254]) by hub.freebsd.org (Postfix) with ESMTP id 0E97C37B40C for ; Wed, 17 Oct 2001 11:19:23 -0700 (PDT) Received: by w3405.hostcentric.net (8.10.1/8.9.0) id f9HIJL509953 for freebsd-hackers@FreeBSD.org; Wed, 17 Oct 2001 14:19:21 -0400 (EDT) Date: Wed, 17 Oct 2001 14:19:21 -0400 (EDT) Message-Id: <200110171819.f9HIJL509953@w3405.hostcentric.net> From: sales@L5Software.com (L5 Software Development) Subject: Can we help you find more customers? To: undisclosed-recipients:; Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 

Do you have too many customers, too much traffic on your Web site, or what?
No?!?
Then you need MCspider(tm) !! 

MCspider(tm) is a business tool for collecting email addresses from Web pages that meet a user-defined set of criteria.  Using this program, an email address list can be constructed to reach a particular audience.  With MCspider(tm), you can build a list of potential customers that is specific to your business by controlling where and how it searches for addresses.  When connected to the Internet through a cable modem or other reasonably high-speed connection, MCspider(tm) will visit thousands of pages per hour in search of customers for your business.  Since it collects email addresses from publicly available Web sites, you know potential recipients have published their address for the world to know.  You should therefore be able to contact them with little fear of SPAM complaints.

MCspider(tm) is a multi-threaded, fully user configurable Windows application with a complete Help system.  It records the Web pages it visits, in addition to the email addresses it found.  You can therefore rest assured the list it produces is "clean" of duplicates, and that it won't waste time repeatedly looking at the same page for new addresses when it's already found them. 

MCspider(tm) is guaranteed to perform substantially as is described in its documentation, and on its Web page.  Note that this is different from what seems to have become an "industry standard" - the practice of selling software "as-is," without any warranty.  (Have you really read any of the license agreements for software you purchased recently?)  Only by purchasing software from vendors who offer to stand behind their products with a viable warranty can you, the consumer, do anything to combat the proliferation of the "crapware" so common in today's marketplace.

MCspider(tm) was officially released on October 5, 2001 for US$ 249.00 per copy.  However, because of some technical problems with our ordering system, we have decided to extend our pre-release offer until October 20:  Any paid orders received before that date will be granted a 60% discount - only US$ 99.00 per copy.  Please be advised this offer is definitely going to expire at the end of the day Oct. 19.

Act now!  Don't miss out on this special offer!  Go to  http://L5Software.com/go?MCspider  to order your pre-release priced copy today!

In case you're wondering how we got your email address, MCspider(tm) found it in one of the searches we had it do.  The program does work, and quite well!




If you want to be excluded from future mailings by L5Software.com, please go to  http://L5Software.com/cgibin/MailRemove.cgi?freebsd-hackers@FreeBSD.org  to add your address to our list of blocked email addresses.

________________________________________________________________
L5 Software Development - "out of this world" sites and software

MCspider(tm), crawling the World Wide Web for customers
	 http://www.L5Software.com/go?MCspider 
ThmIndxr(tm), the *only* HTML thumbnail/indexer you need!
	 http://www.L5Software.com/go?ThmIndxr 
wCapLock(tm), makes CapsLock work like it does on a typewriter
	 http://www.L5Software.com/go?wCapLock 
BannerAds(tm), join multiple affiliate programs with one banner
	 http://www.L5Software.com/go?BannerAds 
KeywordGo(tm), provides keyword access to your popular pages
	 http://www.L5Software.com/go?KeywordGo
To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 12:53:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 337BA37B403; Wed, 17 Oct 2001 12:53:28 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f9HJoKH33299; Wed, 17 Oct 2001 12:50:20 -0700 (PDT) (envelope-from jkh@freebsd.org) To: dhass@imagestream.com Cc: tedm@toybox.placo.com, bicknell@ufp.org, kc5vdj@yahoo.com, taylorm@bytecraft.au.com, freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: RE: FYI In-Reply-To: References: <009301c15726$797d19a0$1401a8c0@tedm.placo.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: <20011017125020N.jkh@freebsd.org> Date: Wed, 17 Oct 2001 12:50:20 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 59 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > We certainly support the right for companies to protect their intellectual > property in whatever way they see fit, even if the FreeBSD community does > not. Oh my. I can see that we've gone somewhat polemic here. As someone who's been around since the very beginning, I think I can fairly state that this point of view mischaracterizes the FreeBSD community somewhat. We're not against companies protecting their intellectual property at all, and the number of companies using FreeBSD in closed-source applications with the full "approval" of the FreeBSD community (where approval is construed by a lack of flames and general pride at FreeBSD's role in each instance) is considerable and growing. What I think Ted may be referring to, and you should be clear on the fact that Ted sometimes finds it difficult to express himself in less than hyperbolic terms, is the fact that the base FreeBSD "product" is one that we take special pains to keep unencumbered for exactly the reasons expressed above. If we're to continue to bill FreeBSD as a product which can be used for any purpose, we need to be careful about the licenses used for its various fundamental building blocks so that *third parties* don't get into trouble by perhaps naively assuming that all of FreeBSD is BSD copyrighted. It wouldn't "hurt" the FreeBSD Project at all if we started distributing some drivers in binary form only (though it would add to our tech support load in having to explain that driver foo was only supported by ABI bar), but it would potentially hurt an embedded systems developer to grab the whole ball of wax and productize it, only to have someone in legal suddenly get to that particular part of the audit and go "Hey! This driver doesn't allow commercial re-use! What the hell does engineering think it's doing?!" Sure, it's THEIR problem to deal with and not ours, but those same engineers won't exactly be thanking us for slipping a hand grenade amidst the roses where they didn't notice it. If the project wants to keep making friends in that community, it's encumbent on it to do as much proactive segregation of differently-licensed code as possible and impose some reasonable standards on what's brought into the base and what's kept at arm's length, again not for its purposes but for the purposes of those who might be re-using it later. That's why the GPL code lives in /usr/src/gnu and /usr/src/sys/gnu - not because we hate GPL code but because we want to make it very clear just what parts needs to be subtracted by any 3rd party doing truly closed-source development. It's also why we prefer BSD-copyrighted solutions to GPL'd ones if we have a choice - it's just simpler all the way down the line. I fully support your idea of offering a "bounty" to anyone writing drivers for your cards and think you're being more than generous in offering it. I wish more vendors would do that and I'm sorry that this discussion has gotten as polarized as it has. If people want to change the support situation for T1 cards, they need to get off their duffs and write the code - as a vendor, you're doing all that might be expected and more to facilitate the process. I hope the zealots in the audience realize that too. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 13: 4: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id A940F37B403; Wed, 17 Oct 2001 13:03:56 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9HK3ga41715; Wed, 17 Oct 2001 22:03:42 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Jordan Hubbard Cc: dhass@imagestream.com, tedm@toybox.placo.com, bicknell@ufp.org, kc5vdj@yahoo.com, taylorm@bytecraft.au.com, freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI In-Reply-To: Your message of "Wed, 17 Oct 2001 12:50:20 PDT." <20011017125020N.jkh@freebsd.org> Date: Wed, 17 Oct 2001 22:03:42 +0200 Message-ID: <41713.1003349022@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011017125020N.jkh@freebsd.org>, Jordan Hubbard writes: >I fully support your idea of offering a "bounty" to anyone writing >drivers for your cards and think you're being more than generous in >offering it. I wish more vendors would do that and I'm sorry that >this discussion has gotten as polarized as it has. If people want to >change the support situation for T1 cards, they need to get off their >duffs and write the code Hey, I got two drivers under my belt already, although only E1, but isn't that enough for a beginning ? :-) I fully agree with Jordan btw, that is a very clear explanation of the situation. And as I said, we do have precedence and procedures for shipping binary drivers with FreeBSD. -- 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 Oct 17 13:57:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.dyndns.org (adsl-208-191-149-224.dsl.hstntx.swbell.net [208.191.149.224]) by hub.freebsd.org (Postfix) with ESMTP id 5321737B403; Wed, 17 Oct 2001 13:57:31 -0700 (PDT) Received: (from chris@localhost) by holly.dyndns.org (8.11.6/8.9.3) id f9HKwJ614761; Wed, 17 Oct 2001 15:58:19 -0500 (CDT) (envelope-from chris) Date: Wed, 17 Oct 2001 15:58:18 -0500 From: Chris Costello To: Robert Watson Cc: hackers@FreeBSD.org, developers@FreeBSD.org Subject: Re: Request for submissions: FreeBSD Monthly Development Status Report Message-ID: <20011017155818.F6252@holly.calldei.com> Reply-To: chris@FreeBSD.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.org on Sun, Oct 14, 2001 at 11:29:16AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, October 14, 2001, Robert Watson wrote: > For future reports, we will also support SGML submissions using a style > sheet developed by Nik Clayton. Those who wish to submit reports in the aforementioned XML format, see http://www.FreeBSD.org/news/status/report-sample.xml -- and remember, the deadline's coming up in just two days! -- +-------------------+------------------------+ | Chris Costello | That does not compute. | | chris@FreeBSD.org | | +-------------------+------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 15:54:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 4B2C837B403 for ; Wed, 17 Oct 2001 15:54:18 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id B776B16B13 for ; Thu, 18 Oct 2001 00:54:15 +0200 (CEST) Received: from IBM-HIRXKN66F0W.Go2France.com [66.64.14.18] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id AE4F69B00C4; Thu, 18 Oct 2001 01:03:43 +0200 Message-Id: <5.1.0.14.0.20011017175006.051ac3e0@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 17 Oct 2001 17:53:27 -0500 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: FYI: Cyclades PC300, PC400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG some snipping done: >Date: Tue, 16 Oct 2001 17:21:55 -0700 (PDT) >From: Cyclades Technical Support >To: Len Conrad >Subject: Re: PC400 >X-Virus-Scanned: by VirusGate.MEIway.com >X-RCPT-TO: > >Hi Len, > My answers are below. >Regards, > >Al Roth > >On Mon, 15 Oct 2001, Len Conrad wrote: > > > Hi Al, > > > > ok, so the PC400 can support "clear-channel", ie, non-channelized > > operation, it seems? > > > > >These are primarily limitations in FreeBSD. > > >There are many more options available in Linux, including Frame > > >Relay support. > > > > oh, I see. It's your FreeBSD driver that isn't as sophisticated as your > > Linux driver? > >Actually, the problem is in the FreeBSD support, not the driver > > > > > You FreeBSD support for the PC400 includes FreeBSD 4.4? > > > >There currently is not a FreeBSD driver for PC400. > > > In the case where I use two or more PC400's to accept, say, 4 T1's, is > > there any outbound loadbalancing where the 4 T1's are going to the same > > upstream, who in turn is doing downstream-load balancing? This load > > balanced, multi-T1 setup seems to be the common way to go above 1.5 > > mbits/sec without going to a full or fractionalized DS3. > > > >Load balancing is an OS issue, not a driver issue. In the case of Linux >2.4.4 and greater, we are able to support MultiLink PPP, so multiple T1 >lines can be combined to increase bandwidth. -------------------------- So they've got some FreeBSD support, but say its weaker driver is due to FreeBSD. hmmmm Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 16:31:42 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 A8D0237B405 for ; Wed, 17 Oct 2001 16:31:39 -0700 (PDT) Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.6/8.11.6) with ESMTP id f9HNVNb56638; Wed, 17 Oct 2001 19:31:23 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200110172331.f9HNVNb56638@whizzo.transsys.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "Ted Mittelstaedt" Cc: "void" , "Matt Dillon" , Bsdguru@aol.com, hackers@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: Imagestream WanIC-520 interface cards References: <009501c15728$30ac6f80$1401a8c0@tedm.placo.com> In-reply-to: Your message of "Wed, 17 Oct 2001 09:24:27 PDT." <009501c15728$30ac6f80$1401a8c0@tedm.placo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Oct 2001 19:31:23 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I am perfectly aware of this. > > The RBOCs deserved to have those "fines" levied against them for a number > of years, to punish them for attempting to block the CLECs. However, it's > been long enough for this, and in fact the money from the RBOCs is no longer > being used to increase the CLEC's reach or service area (ie: infrastructure) > and being used by the CLECS to bash each other, instead of bashing the > RBOCS. The recip-comp charges have nothing to do with extending the reach of a CLEC's network. It's (supposed) to cover the cost of carrying or terminating an inbound POTS voice call. In in more generic view, recip-comp shows up in the "revenue" column of the balance sheet. To assume it's intended to be any more than that is imagination. > The situation is equivalent to Foreign Aid that the US pays to a country such > as Japan. (which we still do to the tune of millions and millions of dollars > a year) Japan has long since ceased being a poor relation that needs to be > bailed out. The reasons for them being paid off by the US have been > fulfilled. > Yet, the payments continue, and the money is being used to free up other > funding that's being spent on political - not necessary - things. Huh? You might also explain the situation as subsidizing the cost of providing Internet service. It's revenue coming into the business which would otherwise need to come from some other source, such as the customers. There are lots of other examples of charges and tariffs which telecom carriers charge each other because of the bizzare reality set up by FCC regulations. You simply siezed upon one with contemporary sex-appeal. If you want to rant about something, go take a look at how half-circuit pricing is done for international private lines. You think the US carriers are evil, go see what state-supported telecom monopolies get to do. Or the hoops which much be jumped through to get licenses to operate telecom, datacom, or Internet lines of business in some countries around the world. Disclaimer: I work for a big stupid phone company, and have unfortunately become aware of this and many other regulatory issues. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 17:37:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 3A50337B403; Wed, 17 Oct 2001 17:37:27 -0700 (PDT) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f9I0bIG89886; Wed, 17 Oct 2001 20:37:21 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20011017125020N.jkh@freebsd.org> References: <009301c15726$797d19a0$1401a8c0@tedm.placo.com> <20011017125020N.jkh@freebsd.org> Date: Wed, 17 Oct 2001 20:37:15 -0400 To: dhass@imagestream.com From: Garance A Drosihn Subject: RE: FYI Cc: Jordan Hubbard , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 12:50 PM -0700 10/17/01, Jordan Hubbard wrote: >I fully support your idea of offering a "bounty" to anyone writing >drivers for your cards and think you're being more than generous in >offering it. I wish more vendors would do that and I'm sorry that >this discussion has gotten as polarized as it has. If people want >to change the support situation for T1 cards, they need to get off >their duffs and write the code - as a vendor, you're doing all that >might be expected and more to facilitate the process. I hope the >zealots in the audience realize that too. The freebsd project is really just a bunch of users who happen to use and work on freebsd. The group of users is such that we'll always PREFER a completely open-source BSD-licensed driver to other alternatives. However, it is also true that the vast majority of those users will prefer having a driver to NOT having a driver! :-) I think that offering some sort of bounty to have a freebsd developer work on drivers for your cards, under NDA, is a generous offer. I'm not the kind of person who writes drivers, but I certainly hope that someone takes you up on the offer. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 19:18:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp005pub.verizon.net (smtp005pub.verizon.net [206.46.170.184]) by hub.freebsd.org (Postfix) with ESMTP id 73D4E37B403 for ; Wed, 17 Oct 2001 19:18:28 -0700 (PDT) Received: from bellatlantic.net ([151.198.117.209]) by smtp005pub.verizon.net with ESMTP ; id f9I2IDW07363 Wed, 17 Oct 2001 21:18:22 -0500 (CDT) Message-ID: <3BCE3BDB.6B5A28@bellatlantic.net> Date: Wed, 17 Oct 2001 22:18:03 -0400 From: Sergey Babkin Reply-To: babkin@FreeBSD.ORG X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Ronald G Minnich Cc: Rayson Ho , "=?iso-8859-1?Q?Fabi=E1n?= Salamanca" , freebsd-hackers@FreeBSD.ORG Subject: Re: clustering code References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ronald G Minnich wrote: > > On Sun, 14 Oct 2001, Rayson Ho wrote: > > > http://ssic-linux.sourceforge.net/ > > A collection of some really bad ideas, not likely to scale well. Note that > they've got up to 30 nodes, wow. Double it once and that's where this kind > of "global everything" idea starts to fall over. Badly. > > It would be neat to see freebsd do something really new and novel in > clustering. ssci-linux is not it. It's going to be very hard to pick > something new, a lot of the ground is well-trod. It definitely looks like it is. Well, though it could definitely benefit from direct support in the database management systems. This DBMS support may be exactly this "something really new and novel". And directly comparing the number of nodes with Beowulf-style clusters is not fair. The Beowulf clusters can be reasonably efficiently used only for a very limited class of problems with very high parallelism of subtasks, high computational complexity of each subtask and very low interactions between them. So they are a quite degenerated case and pretty useless for business applications. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 19:54:20 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 2355937B409; Wed, 17 Oct 2001 19:54:11 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f9I2c1B43362; Wed, 17 Oct 2001 22:38:02 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 17 Oct 2001 22:38:01 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: hackers@FreeBSD.org, developers@FreeBSD.org Subject: REMINDER: FreeBSD Monthly Development Status Report (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Also, for those interested, a sample 'report' XML entry is available at: http://www.FreeBSD.org/news/status/report-sample.xml Which can be used to lower my workload by pre-formatting your status report. You can also submit in plain text and I'll do the conversion manually. Thanks! Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services ---------- Forwarded message ---------- Date: Sun, 14 Oct 2001 11:29:16 -0400 (EDT) From: Robert Watson To: hackers@FreeBSD.org, developers@FreeBSD.org Subject: Request for submissions: FreeBSD Monthly Development Status Report It's that time again--despite delays and data loss, I'm now ready to start accepting submissions for the September, 2001 FreeBSD Monthly Status Report. As with previous months, please submit reports by e-mail to robert+freebsd.monthly@cyrus.watson.org. Reports should be submitted by October 19, 2001, and cover activities from September 7 through October 19. Reports may be associated with any aspect of the FreeBSD Project, including but not limited to basic system development, merging activities for the -STABLE branch, documentation, advocacy, third party software development, user group meetings, and conference activities. Each report should consist of one paragraph of status information, and in the event that a particular project has not had a status report submitted before, an additional paragraph can be included introducing the project. When submitting reports, please attempt to coordinate submissions so that only one report is submitted per project, except in the case of large projects where reports should cover independent and non-overlapping status information. Reports should contain a project name (preferably the same as previous submissions for the project), contact address(es), optional URL for the project. Submissions should be formatted as follows: Project: (name) URL: (name) Contact: name1 , name2 And the text goes here, uniformly indented two spaces, and wrapped before the 78th column. For future reports, we will also support SGML submissions using a style sheet developed by Nik Clayton. Thanks, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 20:16:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with SMTP id 55AAC37B407 for ; Wed, 17 Oct 2001 20:16:48 -0700 (PDT) Received: (qmail 1085343 invoked from network); 17 Oct 2001 21:16:47 -0600 Received: from snaresland.acl.lanl.gov (128.165.147.113) by acl.lanl.gov with SMTP; 17 Oct 2001 21:16:47 -0600 Received: (qmail 17853 invoked by uid 3499); 17 Oct 2001 21:16:47 -0600 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Oct 2001 21:16:47 -0600 Date: Wed, 17 Oct 2001 21:16:47 -0600 (MDT) From: Ronald G Minnich X-X-Sender: To: Cc: Rayson Ho , =?iso-8859-1?Q?Fabi=E1n?= Salamanca , Subject: Re: clustering code In-Reply-To: <3BCE3BDB.6B5A28@bellatlantic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 17 Oct 2001, Sergey Babkin wrote: > And directly comparing the number of nodes with Beowulf-style > clusters is not fair. The Beowulf clusters can be reasonably > efficiently used only for a very limited class of problems > with very high parallelism of subtasks, high computational > complexity of each subtask and very low interactions > between them. So they are a quite degenerated case and pretty > useless for business applications. You can't use qualitative characterizations like "high, high, very low" for this. Do you have numbers? Basically I don't agree. But let's take this off the list. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 21:11:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id CC3F737B403; Wed, 17 Oct 2001 21:11:47 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9I4BWT25811; Wed, 17 Oct 2001 21:11:36 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Doug Hass" Cc: "Leo Bicknell" , "Jim Bryant" , "MurrayTaylor" , , Subject: RE: FYI Date: Wed, 17 Oct 2001 21:11:31 -0700 Message-ID: <000001c1578a$f7962480$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Doug Hass [mailto:dhass@imagestream.com] >Sent: Wednesday, October 17, 2001 9:19 AM >To: Ted Mittelstaedt >Cc: Leo Bicknell; Jim Bryant; MurrayTaylor; freebsd-hackers@FreeBSD.ORG; >freebsd-questions@FreeBSD.ORG >Subject: RE: FYI > > >> Doug, in the entire history of the FreeBSD project, when given a choice >> between a better driver or code that is closed source, and a worse >> driver that has open source, the FreeBSD community has never chosen the >> driver or code with closed source. In fact I can only remember ONCE >> that the Project has recommended against freely available BSD code - and >> they did so in favor of GPL code, not closed source code - and this was >> for the coprocessor emulator (used for 386 and 486SX chips only) > >> The only time that FreeBSD gets involved in closed-source code is when >> there is simply NO other alternative - like in this case where the >> register interface specs are being withheld. > >We certainly support the right for companies to protect their intellectual >property in whatever way they see fit, even if the FreeBSD community does >not. > Whoah whoah here! Where did I say that FreeBSD didn't support intellectual property? Choosing not to include a lot of binary licensed code in the FreeBSD distribution is a free choice that the maintainers have made. How can you fault them for that?!?! I think that your ignoring a lot of issues here when you say that FreeBSD doesen't support IP. For starters I'm only stating what is current in the Project. Unlike Linux, there is not a large quantity of binary-only code distributed with FreeBSD distributions. Companies are free to distribute such as they see fit. Not many of them would allow binary-only code into the FreeBSD CD distribution anyway. In fact one of the reasons that the Ports directory is set up the way it is, is so that the project doesen't have to deal with a bunch of licensing issues. >The lack of flexibility in accepting various requirements illustrates the >difference between an OS WITH legs in the market and one WITHOUT legs. > >Much to my chagrin, FreeBSD continues to fall more and more into the >latter category. > This is a gross simplification of a great many issues. I fail to see why you feel that FreeBSD is threatening anyone's IP and I don't understand why you are reacting this way. Any company is free to take the FreeBSD distribution and customize it the way they want and include any proprietary and binary code they want and hand out distributions as they see fit. Imagestream could do this if it wanted to. I'm just saying that in the past the main FreeBSD distributions have preferred not to do this, and I see no indication that things are changing in the latest release. The fact is that just about everything included in the release has full source code. If Imagestream wants to release binary-only drivers for the WANic card and have them included in the FreeBSD distribution, since there's no alternative I'm sure that nobody would complain - unless Imagestream demanded that anyone getting a FreeBSD distribution with the drivers report back to them, or some such. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 21:17:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 803CB37B407; Wed, 17 Oct 2001 21:17:34 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9I4HST25838; Wed, 17 Oct 2001 21:17:28 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Doug Hass" , "void" Cc: "Mike Smith" , "Leo Bicknell" , "Jim Bryant" , "MurrayTaylor" , , Subject: RE: FYI Date: Wed, 17 Oct 2001 21:17:28 -0700 Message-ID: <000101c1578b$cc3858c0$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Doug Hass [mailto:dhass@imagestream.com] >Sent: Wednesday, October 17, 2001 11:10 AM >To: void >Cc: Mike Smith; Ted Mittelstaedt; Leo Bicknell; Jim Bryant; >MurrayTaylor; freebsd-hackers@FreeBSD.ORG; freebsd-questions@FreeBSD.ORG >Subject: Re: FYI > > >If you didn't say it, then you weren't the one I was talking about, was I? > >:-) > >I got several other private mails saying that BSD licensed code was the >one and only way, well Doug, there's a reason you got those as private mails instead of public posts - because this isn't the viewpoint of the FreeBSD community. >and 2 or 3 mails (from Ben, among others) saying that >BSD-licensed was preferred. > Preferred doesen't mean we are going to throw the baby out with the bathwater and turn up our nose at anyone's effort with FreeBSD. >Either approach is as flawed as someone who claims GPL only or GPL >preferred. The license terms of add-on drivers and products should be set >according to the needs of the authoring person or company, in my opinion. > This is a perfectly valid viewpoint that a lot of companies share which is why they don't include their drivers. For example Sangoma, and Emerging don't include FreeBSD drivers either - but they make them available from their own websites. In My Humble Opinion this is inferior than just giving the binaries over to the project and letting the drivers be handed out where they may, but those companies and you are welcome to do it that way if you prefer. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >Doug > >On Wed, 17 Oct 2001, void wrote: > >> On Wed, Oct 17, 2001 at 12:19:34PM -0500, Doug Hass wrote: >> > >> > I'm glad someone else is speaking up--all I've heard is Ted's point of >> > view (from him, and from others who have said the same thing: >FreeBSD only >> > accepts BSD licensed code, period.) >> >> I said to you in private mail that where there's a BSD-licensed solution >> and a non-BSD-licensed solution, all else being roughly equal, FreeBSD >> tends towards the BSD-licensed solution. Not the same thing at all. >> >> -- >> Ben >> >> "An art scene of delight >> I created this to be ..." -- Sun Ra >> > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 22: 3: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 0015537B42A; Wed, 17 Oct 2001 22:02:49 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9I52mT25960; Wed, 17 Oct 2001 22:02:48 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Mike Smith" , "Doug Hass" Cc: "Leo Bicknell" , "Jim Bryant" , "MurrayTaylor" , , Subject: RE: FYI Date: Wed, 17 Oct 2001 22:02:47 -0700 Message-ID: <000201c15792$2158e440$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: <200110171646.f9HGkHs00996@mass.dis.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Mike Smith [mailto:msmith@FreeBSD.ORG] >Sent: Wednesday, October 17, 2001 9:46 AM >To: Doug Hass >Cc: Ted Mittelstaedt; Leo Bicknell; Jim Bryant; MurrayTaylor; >freebsd-hackers@FreeBSD.ORG; freebsd-questions@FreeBSD.ORG >Subject: Re: FYI > > >> > Doug, in the entire history of the FreeBSD project, when given a choice >> > between a better driver or code that is closed source, and a worse >> > driver that has open source, the FreeBSD community has never chosen the >> > driver or code with closed source. In fact I can only remember ONCE >> > that the Project has recommended against freely available BSD code - and >> > they did so in favor of GPL code, not closed source code - and this was >> > for the coprocessor emulator (used for 386 and 486SX chips only) >> >> > The only time that FreeBSD gets involved in closed-source code is when >> > there is simply NO other alternative - like in this case where the >> > register interface specs are being withheld. >> >> We certainly support the right for companies to protect their intellectual >> property in whatever way they see fit, even if the FreeBSD community does >> not. > >Doug; I would recommend against falling for Ted's flamebait here, since >that's really all it is. That's silly, what did you find in it that's flamebait? I think you didn't read it. >His characterisation of the FreeBSD Project's >attitude towards proprietary drivers fails to mention many of the other >factors that get weighed into these decisions, and I think he's missing a >lot of history. > No, I am well aware of FreeBSD's history and if you don't believe that the project avoids closed-source code then I don't know what to say, frankly. I clearly remember the ruckus over the Adaptec 2740 drivers and the long statement against Adaptec that used to be in the older versions of FreeBSD, that only had AHA 1740 code in them. If things have changed and the majority of the users in the FreeBSD project welcome closed-source code, then please point out where all of this is? I don't see it. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 22:20:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 2E04E37B405; Wed, 17 Oct 2001 22:20:55 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f9I5WFs08081; Wed, 17 Oct 2001 22:32:15 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200110180532.f9I5WFs08081@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ted Mittelstaedt" Cc: "Doug Hass" , "Leo Bicknell" , "Jim Bryant" , "MurrayTaylor" , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI In-reply-to: Your message of "Wed, 17 Oct 2001 22:02:47 PDT." <000201c15792$2158e440$1401a8c0@tedm.placo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Oct 2001 22:32:15 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > >Doug; I would recommend against falling for Ted's flamebait here, since > >that's really all it is. > > That's silly, what did you find in it that's flamebait? I think you didn't > read it. You're a) misrepresenting the project, b) dismissing the opinions and statements of others that are arguably more in touch with the project, and c) you won't let this stupid thread die. That's all flamebait. > >His characterisation of the FreeBSD Project's > >attitude towards proprietary drivers fails to mention many of the other > >factors that get weighed into these decisions, and I think he's missing a > >lot of history. > > No, I am well aware of FreeBSD's history and if you don't believe that the > project avoids closed-source code then I don't know what to say, frankly. You could say "I'm wrong". It'd be a good start. > If things have changed and the majority of the users in the FreeBSD project > welcome closed-source code, then please point out where all of this is? > I don't see it. This isn't what's being said. See above inre: "flamebait". -- ... 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 Oct 17 22:51:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id D59EA37B401; Wed, 17 Oct 2001 22:51:35 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9I5pQT26119; Wed, 17 Oct 2001 22:51:31 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Doug Hass" , "Mike Smith" Cc: "Leo Bicknell" , "Jim Bryant" , "MurrayTaylor" , , Subject: RE: FYI Date: Wed, 17 Oct 2001 22:51:25 -0700 Message-ID: <001801c15798$ec656cc0$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Doug Hass [mailto:dhass@imagestream.com] >Sent: Wednesday, October 17, 2001 10:20 AM >To: Mike Smith >Cc: Ted Mittelstaedt; Leo Bicknell; Jim Bryant; MurrayTaylor; >freebsd-hackers@FreeBSD.ORG; freebsd-questions@FreeBSD.ORG >Subject: Re: FYI > >I'm glad someone else is speaking up--all I've heard is Ted's point of >view (from him, and from others who have said the same thing: FreeBSD only >accepts BSD licensed code, period.) > That is not my point of view and if you read my mail you will see that and I will thank you very much not to go around saying that. To repeat: I said that "The only time that FreeBSD gets involved in closed-source code is when there is simply NO other alternative - like in this case where the register interface specs are being withheld." and "when given a choice between a better driver or code that is closed source, and a worse driver that has open source, the FreeBSD community has never chosen the driver or code with closed source" This is very far from saying that FreeBSD only accepts BSD licensed code, period. When we have a choice, we take the BSD code and improve it as necessary. Otherwise, we take what we can get. Sometimes, even, companies that release the stuff closed source end up opening it up when they see that by doing so that lots more people will contribute bugfixes and such. > >It's not a generalization at all. Honestly, compared to the market >traction that Linux, VxWorks, Solaris and others have, FreeBSD is >definitely without legs. FreeBSD is not a commercial product and there is no pressure for it to steal all the market share away from all the other UNIX and UNIX-like vendors. It's been proven by Microsoft rather well I think that the majority of computer users in the market will fight their way to junk and push the good stuff aside in their stampede. Even you must admit that if Imagestream had 80% of the router market that it would in no way, shape or form resemble what it is today. You would turn into Cisco. It's unavoidable, and just how life works. (this is not to infer that Cisco is junk, BTW, just that they are a big and often unresponsive company) >The WAN card and RAS card markets are good >examples of where the attitude toward "BSD-licensed code or bust" has >resulted in FreeBSD being largely left out of the party. Three of the >largest manufacturers in these segments (SBS, Cyclades, and Ariel) all >support Linux and NT, but do not have BSD support. > The Cyclades Cyclom-Y boards are supported by the "cy" driver in FreeBSD. This was not written by Cyclades. OK - so it's not a RAS card, but where was Cyclades? >It's too bad we can't find a way to include more companies and >solutions instead of continuing to find ways to EXCLUDE them... > It's a shame that so much misinformation is spread over the BSD license. Just ask yourself - why is it that the BSD license is such an object of controversy? People talk about the GPL being controversial? Sheesh! All the license says is to give away code for free. What a revolutionary idea! Most ironic is that it seems like 1/4 of the GPL advocates out there who are making noise about it want us all lined up against the wall and shot for saying that!!! Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 23:13: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 9273E37B401; Wed, 17 Oct 2001 23:12:56 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1098) id 54DF381D06; Thu, 18 Oct 2001 01:12:56 -0500 (CDT) Date: Thu, 18 Oct 2001 01:12:56 -0500 From: Bill Fumerola To: Ted Mittelstaedt Cc: Doug Hass , Mike Smith , Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI Message-ID: <20011018011256.U51024@elvis.mu.org> References: <001801c15798$ec656cc0$1401a8c0@tedm.placo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001801c15798$ec656cc0$1401a8c0@tedm.placo.com>; from tedm@toybox.placo.com on Wed, Oct 17, 2001 at 10:51:25PM -0700 X-Operating-System: FreeBSD 4.4-FEARSOME-20010909 i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Oct 17, 2001 at 10:51:25PM -0700, Ted Mittelstaedt wrote: > When we have a choice, we take the BSD code and improve it as necessary. > Otherwise, we take what we can get. Sometimes, even, companies that release > the stuff > closed source end up opening it up when they see that by doing so that lots > more people will contribute bugfixes and such. you say 'we' an awful lot for someone who isn't part of, doesn't represent, and is in no way affiliated with the freebsd project. thankfully, the project's official word can be found here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/policies-encumbered.html -- - bill fumerola / fumerola@yahoo-inc.com / billf@FreeBSD.org / billf@mu.org - my anger management counselor can beat up your self-affirmation therapist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 17 23:38:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 5276337B408 for ; Wed, 17 Oct 2001 23:38:22 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9I6cCT26283; Wed, 17 Oct 2001 23:38:12 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Louis A. Mamakos" Cc: "void" , "Matt Dillon" , , Subject: RE: Imagestream WanIC-520 interface cards Date: Wed, 17 Oct 2001 23:38:11 -0700 Message-ID: <003101c1579f$750d3160$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: <200110172331.f9HNVNb56638@whizzo.transsys.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: louie@whizzo.transsys.com [mailto:louie@whizzo.transsys.com]On >Behalf Of Louis A. Mamakos >Sent: Wednesday, October 17, 2001 4:31 PM >To: Ted Mittelstaedt >Cc: void; Matt Dillon; Bsdguru@aol.com; hackers@FreeBSD.ORG >Subject: Re: Imagestream WanIC-520 interface cards > > > >> I am perfectly aware of this. >> >> The RBOCs deserved to have those "fines" levied against them for a number >> of years, to punish them for attempting to block the CLECs. However, it's >> been long enough for this, and in fact the money from the RBOCs is >no longer >> being used to increase the CLEC's reach or service area (ie: >infrastructure) >> and being used by the CLECS to bash each other, instead of bashing the >> RBOCS. > >The recip-comp charges have nothing to do with extending the reach of >a CLEC's network. It's (supposed) to cover the cost of carrying or >terminating an inbound POTS voice call. Back up a sec - the reason that Bellcore was busted up is because the trust people claimed that CLECs could provide voice dialup better and cheaper than ILECS by the sheer fact that they were competitive. The FCC has always pushed as hard as it could to give CLECs an advantage over RBOCS to promote competition. The RBOCS forced the call term charges as a fairness issue. Once it was discovered that the cash transfer was going towards the CLECS from the ILECS, the FCC couldn't have been happier. They never wanted things to be fair in the first place between the CLECS and the RBOCS. By the pro-breakup people's definition, the CLECS incur less cost than the RBOCS for terminating a call. If this was a fairness issue then the RBOCS would only have to pay the CLECS the actual cost incurred by the more efficient CLECS for the call term. But instead they pay what it costs the RBOCS to terminate a call (which is higher according to the pro-breakup people's definition) Now, obviously it's hard to know what the truth is because the entire point of Telco accounting is to so confuse the numbers that the PUC's and the FCC and all the other governmental regulators are so baffled by them that they pretty much throw their hands up in the air and accept whatever bullshit the phone companies care to dish out. Telco accounting is the science of making an absolute into a negotiated item. > >Huh? You might also explain the situation as subsidizing the cost >of providing Internet service. It's revenue coming into the business >which would otherwise need to come from some other source, such as the >customers. > And of course the entire point of running a Telco is to not make a profit by the customers that are supposedly paying you for the service your supposedly giving, but to screw everyone else in the business that's otherwise totally unaffiliated into paying for your customers. Yes, I know all about that. :-( >There are lots of other examples of charges and tariffs which telecom >carriers charge each other because of the bizzare reality set up by >FCC regulations. You simply siezed upon one with contemporary sex-appeal. > >If you want to rant about something, go take a look at how half-circuit >pricing is done for international private lines. Don't even get me started. There's a huge litany. Like, why are T1 charges so gouging yet DSL (which delivers more bandwidth in some cases) so rediculously low. Like, why is each trunk on a T1 charged at nearly the same rate as if it were provided by POTS yet it costs the phone company 10% of the expense to deliver trunks over T1 than POTS. Like why is mileage charges allowed in a calling area when it costs the phone company exactly the same amount to run a T1 5 miles as it does to run it 1 mile (and in some cases the CO is 4 miles from both endpoints so the total line length is 8 miles but they still only charge for 5) >You think the US >carriers are evil, go see what state-supported telecom monopolies get >to do. Or the hoops which much be jumped through to get licenses to >operate telecom, datacom, or Internet lines of business in some >countries around the world. > Ah - you mean like China. Don't forget all the state-sponsored porno filtering of the Internet feeds into Iran either. Yes there are some very nasty and greedy people in the world. Frankly, as long as the CLECs and ILECS are using the FCC to beat each other over the heads, I could care less. What I get mad about is that the CLECS seem to have given up fighting with the RBOCS and are turning against the ISPs. It's like they turn around and start bullying the ISP's simply because the ISP's are weaker than they are. Yet it was those ISP's that got the recipri-comp payments wacked out in the CLECs favor to start with. That's gratitude for you. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 0:17:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nelly.internal.irrelevant.org (irrelevant.demon.co.uk [158.152.220.121]) by hub.freebsd.org (Postfix) with ESMTP id 2290437B407 for ; Thu, 18 Oct 2001 00:17:43 -0700 (PDT) Received: from simond by nelly.internal.irrelevant.org with local (Exim 3.33 #1) id 15u7PT-00006B-00; Thu, 18 Oct 2001 08:16:07 +0100 Date: Thu, 18 Oct 2001 08:16:07 +0100 From: Simon Dick To: Warner Losh Cc: Simon Dick , Matthew Emmerton , Peter van Heusden , freebsd-hackers@freebsd.org Subject: Re: Adding support for Duxbury PCI modem to FreeBSD 4.4 Message-ID: <20011018081607.A360@irrelevant.org> References: <20011016165722.A988@irrelevant.org> <200110161505.f9GF5L732042@harmony.village.org> <20011016165722.A988@irrelevant.org> <200110161747.f9GHlx733032@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: <200110161747.f9GHlx733032@harmony.village.org>; from imp@harmony.village.org on Tue, Oct 16, 2001 at 11:47:59AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Oct 16, 2001 at 11:47:59AM -0600, Warner Losh wrote: > In message <20011016165722.A988@irrelevant.org> Simon Dick writes: > : Please don't remove the SurfRider one: > : sio0: port 0xa400-0xa407 irq 12 at device 10.0 on pci0 > : sio0: moving to sio2 > : sio2: type 16550A > : > : It was me who submitted the ID for it, it's my main modem :) > > Wow! Cool. I didn't think that there were others. Do you know if > this is a "kermit" chipset or not? Is there a Lucent part on the card > with the word "kermit" on it (well, newer versions don't have kermit > on them). I didn't see any, here's what's on the various chips on it if this helps: 1) TOPIC TP560i 9935S14 D7S82.1 2) (my guess is a mem chip) HMC HM62H256DJ-12 9815A D84B1 3) The biggest chip on the board EON EN29F002NT -70P 0021 > I won't remove it. I was just surprised to find another one with the > plethera of winmodems. Cool. So was I, I just found it advertised as Linux compatible and took a gamble :) -- Simon Dick simond@irrelevant.org "Why do I get this urge to go bowling everytime I see Tux?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 1:11:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 7F23B37B405; Thu, 18 Oct 2001 01:11:14 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9I8B9T26499; Thu, 18 Oct 2001 01:11:09 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Bill Fumerola" Cc: "Doug Hass" , "Mike Smith" , "Leo Bicknell" , "Jim Bryant" , "MurrayTaylor" , , Subject: RE: FYI Date: Thu, 18 Oct 2001 01:11:09 -0700 Message-ID: <004001c157ac$717b9340$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: <20011018011256.U51024@elvis.mu.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Bill Fumerola [mailto:billf@mu.org] >Sent: Wednesday, October 17, 2001 11:13 PM >To: Ted Mittelstaedt >Cc: Doug Hass; Mike Smith; Leo Bicknell; Jim Bryant; MurrayTaylor; >freebsd-hackers@FreeBSD.ORG; freebsd-questions@FreeBSD.ORG >Subject: Re: FYI > > >On Wed, Oct 17, 2001 at 10:51:25PM -0700, Ted Mittelstaedt wrote: > >> When we have a choice, we take the BSD code and improve it as necessary. >> Otherwise, we take what we can get. Sometimes, even, companies >that release >> the stuff >> closed source end up opening it up when they see that by doing so that lots >> more people will contribute bugfixes and such. > >you say 'we' an awful lot for someone who isn't part of, doesn't represent, >and is in no way affiliated with the freebsd project. > >thankfully, the project's official word can be found here: >http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ >policies-encumbered.html And, what exactly on this page is any different from what I've just said? Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 1:28: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.asplinux.ru (asplinux.ru [195.133.213.194]) by hub.freebsd.org (Postfix) with ESMTP id BAE8437B401; Thu, 18 Oct 2001 01:27:56 -0700 (PDT) Received: from asplinux.ru (sashkin.asplinux.ru [192.168.1.108]) by relay.asplinux.ru (8.11.6/8.11.6) with ESMTP id f9I8Rr816697; Thu, 18 Oct 2001 12:27:54 +0400 Message-ID: <3BCE92F0.8090809@asplinux.ru> Date: Thu, 18 Oct 2001 12:29:36 +0400 From: Alex Levine Reply-To: sashkin@home.com User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.3) Gecko/20010829 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Possible bug in scheduler. Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FreeBSD 4-stable. Suspect the same in FreeBSD-current. resetpriority() calls maybe_resched() at the end after updating p_usrpri based on changed p_estcpu. maybe_resched() uses curpriority_cmp to compare priorities of current and given process and this function ( curpriority_cmp ) uses p_priority which is unchanged yet - the new p_usrpri is not reflected to p_priority yet. I'd appreciate an answer from anybody who can assess this problem. Regards Alex Levine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 2:22:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id DA91D37B407; Thu, 18 Oct 2001 02:22:42 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9I9MgT27081; Thu, 18 Oct 2001 02:22:42 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Mike Smith" Cc: "Doug Hass" , , Subject: RE: FYI Date: Thu, 18 Oct 2001 02:22:41 -0700 Message-ID: <004101c157b6$6fcdb0a0$1401a8c0@tedm.placo.com> 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 8.5, Build 4.71.2173.0 In-Reply-To: <200110180532.f9I5WFs08081@mass.dis.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Mike Smith >Sent: Wednesday, October 17, 2001 10:32 PM >To: Ted Mittelstaedt >Cc: Doug Hass; Leo Bicknell; Jim Bryant; MurrayTaylor; >freebsd-hackers@FreeBSD.ORG; freebsd-questions@FreeBSD.ORG >Subject: Re: FYI > > >> That's silly, what did you find in it that's flamebait? I think you didn't >> read it. > >You're a) misrepresenting the project, b) dismissing the opinions and >statements of others that are arguably more in touch with the project, >and c) you won't let this stupid thread die. > I do not feel that this thread is stupid. To the contrary I'm very concerned when a manufacturer pulls a specialty card supported by FreeBSD off the market and replaces it with nothing that is supported. Every time this happens (and it seems to be happening a lot with network adapters lately) it causes problems for a lot of users, confusion because This rev of the card is supported and That rev isn't, extra work for the maintainers, and in short sets the project back. This does not help FreeBSD to support lots of peripherals, as Doug pointed out we are being ignored by the RAS card manufacturers, and nobody is going to use FreeBSD no matter how good the kernel is if the OS doesen't support the hardware they own. Telling Imagestream we built a module architecture that makes writing, maintaining and deploying binary-only drivers easy is fine, but it does nothing to respond to the problem of how to convert their binary drivers to our framework. They don't even understand we have a framework, let alone how it operates. They are asking us to write the drivers and they don't even understand that some of the developers that could do it have reservations against binary-only drivers only available under NDA, or how much more it could help them if they were to just publish source. And attempting to even talk about this openly leads into irrelevant pointless accusations about stealing intellectual property. Device driver support in PC operating systems seems always to have been a political football no matter what OS vendor - even Microsoft with all their power still was forced into writing drivers for some hardware, despite all the pressure they applied to the hardware vendors to do the work. You seem to be taking the attitude that "we made a framework, and that's as far as we go - you write the driver" and then labeling any further discussion on the matter as stupid. Well, if this is the attitude in the FreeBSD project (which I doubt) then if it was such an effective one then why does Linux seem to have many more drivers written for it? >> >> No, I am well aware of FreeBSD's history and if you don't believe that the >> project avoids closed-source code then I don't know what to say, frankly. > >You could say "I'm wrong". It'd be a good start. > OK, your right, I'm wrong. Contrary to my statement, FreeBSD attempts to get as much closed-source code as possible. That's why the name of the distribution starts with the word "Free" Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 2:31: 8 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 C81A637B405; Thu, 18 Oct 2001 02:31:00 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f9I9gcs10427; Thu, 18 Oct 2001 02:42:38 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200110180942.f9I9gcs10427@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ted Mittelstaedt" Cc: "Mike Smith" , "Doug Hass" , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI In-reply-to: Your message of "Thu, 18 Oct 2001 02:22:41 PDT." <004101c157b6$6fcdb0a0$1401a8c0@tedm.placo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Oct 2001 02:42:38 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > >You're a) misrepresenting the project, b) dismissing the opinions and > >statements of others that are arguably more in touch with the project, > >and c) you won't let this stupid thread die. > > I do not feel that this thread is stupid. This much is obvious. You are, however, largely alone in this opinion. > To the contrary I'm very > concerned when a manufacturer pulls a specialty card supported > by FreeBSD off the market and replaces it with nothing that is > supported. If you're "very concerned" about it, I recommend doing something constructive to mitigate the situation. The vendor in question appears to have offered a bounty for a driver; why don't you get busy on it? > Every time this happens (and it seems to be happening > a lot with network adapters lately) It does? Really? You know, I can only think of one ethernet chipset currently on the market that we don't support, or don't have imminent support coming for. That's not "a lot" by any stretch of the imagination. So I'll say it all again, in a slightly different fashion: You sound too much like Brett Glass. Less hysteria, please, and a little more practicality. = 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 Thu Oct 18 3:40:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.oskarmobil.cz (smtp1.oskarmobil.cz [217.77.161.133]) by hub.freebsd.org (Postfix) with ESMTP id 6EDE037B405; Thu, 18 Oct 2001 03:40:33 -0700 (PDT) Received: from wh01ex01.ceskymobil.cz (wh01ex01.oskarmobil.cz [172.20.116.17]) by smtp1.oskarmobil.cz (8.11.2/8.11.1) with ESMTP id f9IAafV87797; Thu, 18 Oct 2001 12:36:41 +0200 (CEST) (envelope-from Milon.Papezik@oskarmobil.cz) Received: by wh01ex01.oskarmobil.cz with Internet Mail Service (5.5.2653.19) id <40HA4ZNK>; Thu, 18 Oct 2001 12:38:02 +0200 Message-ID: From: Milon Papezik To: "'hackers@freebsd.org'" , "'net@freebsd.org'" Subject: netgraph one2many question Date: Thu, 18 Oct 2001 12:37:56 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-2" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, I would like to extend ng_one2many module to include automatic link failure datection, failover and FEC functionality. My question is: Are interface nodes able to send upstream notification that their state has changed or do I have to poll their status periodically as it is done in ng_fec module made kindly available by wpaul ? Thanks in advance, Milon -- milon.papezik@oskarmobil.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 5:34:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id 5303537B407 for ; Thu, 18 Oct 2001 05:34:22 -0700 (PDT) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id f9ICYJj22088; Thu, 18 Oct 2001 14:34:19 +0200 (MEST) Received: from kawoserv.kawo2.rwth-aachen.de (root@kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/6) with ESMTP id f9ICYJo22084; Thu, 18 Oct 2001 14:34:19 +0200 (MEST) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id OAA28218; Thu, 18 Oct 2001 14:34:15 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id 52AB214A21; Thu, 18 Oct 2001 14:34:15 +0200 (CEST) Date: Thu, 18 Oct 2001 14:34:14 +0200 From: Alexander Langer To: sashkin@home.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Possible bug in scheduler. Message-ID: <20011018143414.C2064@zerogravity.kawo2.rwth-aachen.de> References: <3BCE92F0.8090809@asplinux.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BCE92F0.8090809@asplinux.ru>; from sashkin@asplinux.ru on Thu, Oct 18, 2001 at 12:29:36PM +0400 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Alex Levine (sashkin@asplinux.ru): > resetpriority() calls maybe_resched() at the end after updating p_usrpri > based on changed p_estcpu. > maybe_resched() uses curpriority_cmp to compare priorities of current > and given process and this function ( curpriority_cmp ) uses p_priority > which is unchanged yet - the new p_usrpri is not reflected to p_priority > yet. In -CURRENT, it's more obvious: maybe_resched() only rescheds, if the resetted process' priority level changes. Since resetpriority() doesn't modify the priority level but only the user priority, the call to maybe_resched() has no effect at all -- only some overhead for the comparisons (curproc will have had the higher or same priority level as the resetted process anyways, otherwise it hadn't been curproc :) So, either - p's priority level in resetpriority has to be re-calculted as well, or - the call to maybe_resched() can be removed w/o loss of functionality. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 6:14:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id D3FA037B407 for ; Thu, 18 Oct 2001 06:14:46 -0700 (PDT) Received: from mindspring.com (dialup-209.247.141.141.Dial1.SanJose1.Level3.net [209.247.141.141]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id GAA05658; Thu, 18 Oct 2001 06:14:29 -0700 (PDT) Message-ID: <3BCED5E7.3FAE9EB8@mindspring.com> Date: Thu, 18 Oct 2001 06:15:19 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Silbersack Cc: David Malone , Zhihui Zhang , freebsd-hackers@freebsd.org Subject: Re: Limiting closed port RST response References: <20011017120330.H47595-100000@achilles.silby.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Silbersack wrote: > > > Could someone be port scanning you? Another possibility is that you > > > alot of machines are trying to contact a TCP service on the machine > > > in question, which isn't running. > > > > I've seen this while doing load testing. > > > > In general, you want the limit threshold to be higher than > > the connections per second rate, or you will get this message. > > > > I have modified my code locally to crank it up to twice the > > listen queue depth. Frequently, you are just better off by > > turning of the limiting entirely (there's s sysctl; look at > > the code in netinet that emits the message, or grep sysctl -A > > for "lim"). > > Wouldn't fixing your code so that it isn't dropping connections be a > better plan? When things are working properly, there should be no need > for RSTs to be thrown around the network. The problem is what to do when you are attacked. You need to balance resiliance in the face of attack with the ability to bear a legitimately high load. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 6:35:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 9108437B409; Thu, 18 Oct 2001 06:35:18 -0700 (PDT) Received: from mindspring.com (dialup-209.247.141.141.Dial1.SanJose1.Level3.net [209.247.141.141]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id GAA12566; Thu, 18 Oct 2001 06:35:13 -0700 (PDT) Message-ID: <3BCEDAC4.3A7286D2@mindspring.com> Date: Thu, 18 Oct 2001 06:36:04 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Doug Hass Cc: Mike Smith , Ted Mittelstaedt , Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Doug Hass wrote: > It's not a generalization at all. Honestly, compared to the market > traction that Linux, VxWorks, Solaris and others have, FreeBSD is > definitely without legs. The WAN card and RAS card markets are good > examples of where the attitude toward "BSD-licensed code or bust" has > resulted in FreeBSD being largely left out of the party. Three of the > largest manufacturers in these segments (SBS, Cyclades, and Ariel) all > support Linux and NT, but do not have BSD support. > > I've been frusturated repeatedly over the past few years as I try to > continue to use FreeBSD myself for different applications. > > It's too bad we can't find a way to include more companies and > solutions instead of continuing to find ways to EXCLUDE them... Let's take GPL'ed code as an example (it's just an example; it is not the only license that makes it hard to distribute full systems using the code). Code in the boot path can't be GPL'ed. This is because of the GPL's "poison pill" restrictions against BSD licensed code: 1) All code linked against GPL'ed code becomes GPL'ed Most of the code, we couldn't change the license if we wanted to, so this is a non-starter. 2) No additional restrictions There is still a lot of code (this is not a bad thing) that contains the 4 clause license, which means it includes the "claim credit" clause, which means that if you mention features or use of the code, you have to include the copyright in advertising materials so that you aren't claiming you wrote the feature (e.g., if you included PSC's SYN? cache, and said you had a SYN cache, then you'd have to admit that you didn't write it, PSC did). This is sometimes incorrectly called the "advertising clause" -- it isn't, though, since you don't have to mention features or use of the software in your advertising. Outside the boot path, the code can be loaded as a loadable module, so there's a lot more leeway as far as licensing. But if you wanted to replace the driver for the disk controller you are using, or the file system you are using or something else critical to the boot path (e.g. an ethernet driver, if you are net-booting), then there is the problem that it is no longer legal to distribute the code, under the GPL. Netscape, similarly, restricts the distribution of binaries for Netscape, except by themselves or licensees -- which is why we have both ports and packages, instead of just packages, and why some ports download intact binaries from their distributors. > If anyone has an interest in adding support for the SBS WAN cards to > FreeBSD, feel free to contact me. I'll be glad to help. The driver for these cards could be GPL'ed, and not impact FreeBSD. These drivers will not find themselves in the boot path. It also means that they could be binary-only... so long as they were kept up to date with kernel changes. The problems with a binary-only driver are somewhat more and less annoying at the same time: a binary driver that does not place license restrictions on redistribution or on the code it links with is no problem for the project. But there is not currently a lot of infrastructure for adding such drivers easily, and they can quickly become "stale", with evolution of the kernel code -- and the fact that the source isn't public means that it's impossible to intentionally avoid changing a kernel interface out from under it, to ensure the binary compatability is maintained between versions of the kernel. Doing this would also mean that the driver code could not be shared with other, similar devices. Perhaps this is the intent; if so, one should be certain that the trade-offs are worth it. It would probably be worthwhile to consider abstracting, as completely as possible, the code that can't be distributed as source code, and to make the code that depends on kernel interfaces public, so that the glue code could be changed by the FreeBSD community, as the FreeBSD kernel changes, without needing to chnage the core code, distributed as a shared object file. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 7:40:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id CF3C137B40D for ; Thu, 18 Oct 2001 07:40:12 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f9IEeBV19154; Thu, 18 Oct 2001 08:40:11 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f9IEeA721143; Thu, 18 Oct 2001 08:40:10 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110181440.f9IEeA721143@harmony.village.org> To: Simon Dick Subject: Re: Adding support for Duxbury PCI modem to FreeBSD 4.4 Cc: Matthew Emmerton , Peter van Heusden , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 18 Oct 2001 08:16:07 BST." <20011018081607.A360@irrelevant.org> References: <20011018081607.A360@irrelevant.org> <20011016165722.A988@irrelevant.org> <200110161505.f9GF5L732042@harmony.village.org> <20011016165722.A988@irrelevant.org> <200110161747.f9GHlx733032@harmony.village.org> Date: Thu, 18 Oct 2001 08:40:10 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011018081607.A360@irrelevant.org> Simon Dick writes: : So was I, I just found it advertised as Linux compatible and took a : gamble :) Cool. I've seen several that claimed that, but were not, in fact, actual controller based modems. Thanks for the chip info. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 8: 6: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail6.sdc1.sfba.home.com (femail6.sdc1.sfba.home.com [24.0.95.86]) by hub.freebsd.org (Postfix) with ESMTP id 0952737B405 for ; Thu, 18 Oct 2001 08:06:01 -0700 (PDT) Received: from laptop.baldwin.cx ([24.2.39.156]) by femail6.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20011018150600.ZCDM28629.femail6.sdc1.sfba.home.com@laptop.baldwin.cx>; Thu, 18 Oct 2001 08:06:00 -0700 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: <20011018143414.C2064@zerogravity.kawo2.rwth-aachen.de> Date: Thu, 18 Oct 2001 08:05:59 -0700 (PDT) From: John Baldwin To: Alexander Langer Subject: Re: Possible bug in scheduler. Cc: freebsd-hackers@FreeBSD.ORG, sashkin@home.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Oct-01 Alexander Langer wrote: > Thus spake Alex Levine (sashkin@asplinux.ru): > >> resetpriority() calls maybe_resched() at the end after updating p_usrpri >> based on changed p_estcpu. >> maybe_resched() uses curpriority_cmp to compare priorities of current >> and given process and this function ( curpriority_cmp ) uses p_priority >> which is unchanged yet - the new p_usrpri is not reflected to p_priority >> yet. > > In -CURRENT, it's more obvious: > maybe_resched() only rescheds, if the resetted process' priority > level changes. > > Since resetpriority() doesn't modify the priority level but > only the user priority, the call to maybe_resched() has no > effect at all -- only some overhead for the comparisons > (curproc will have had the higher or same priority level > as the resetted process anyways, otherwise it hadn't been curproc :) > > So, either > - p's priority level in resetpriority has to be re-calculted > as well, or > - the call to maybe_resched() can be removed w/o loss > of functionality. or c) in the preemptive kernel maybe_resched() doesn't exist as it's functionality is more properly handled in other places. -- 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 Thu Oct 18 8:18:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id 7DCA337B403; Thu, 18 Oct 2001 08:18:44 -0700 (PDT) Received: from localhost (thomas@localhost) by brunel.uk1.vbc.net (8.11.6/8.11.6) with ESMTP id f9IFIha30020; Thu, 18 Oct 2001 16:18:43 +0100 (BST) Date: Thu, 18 Oct 2001 16:18:42 +0100 (BST) From: Thomas Dixon To: John Baldwin Cc: Thomas Dixon , hackers@FreeBSD.ORG Subject: RE: Problems with booting of CD-ROM (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 16 Oct 2001, John Baldwin wrote: > > On 17-Oct-01 Thomas Dixon wrote: > > > > > > On Tue, 16 Oct 2001, John Baldwin wrote: > > > >> > >> On 16-Oct-01 Thomas Dixon wrote: > >> > I'm trying to make a bootable CD using the cdboot program that come with > >> > freeBSD in /sys/i386/boot/cdboot. The computer I'm trying to do this on > >> > definately boots other CDs as it has booted several other CDs. However > >> > using a CD I've made using mkisofs and cdboot it gives the error; > >> > > >> > Your BIOS int 0x13 extensions seem to be disabled. > >> > It's impossible to boot a CD-ROM without them. > >> > (BIOS int 0x13 fn 0x4b01 yielded error 1) > >> > > >> > I'm using an Asus P5A motherboard, there appears to be no way to enable > >> > the int 0x13 extensions in the BIOS and there is nothing in the manual > >> > that refers to these. > >> > > >> > Any ideas why this error is coming up or how to fix it? > >> > >> Don't use cdboot or cdldr, they don't qutie work yet. :( > >> > >> Instead, make a floppy image and use that to boot. > >> > > I've tried this and I couldn't figure out the syntax for loader.rc to load > > the file system from the cd-rom, any ideas? > > You don't really load the filesystem from the CD-ROM as the loader can't read a > CD-ROM right now. Instead you use a memory filesystem on the floppy image and > use that to boostrap yourself so you can mount the CD. I have done this now and it loads the mfsroot.gz file, however I can't find any man pages or web pages that tell me how to create an mfsroot file. Any ideas on this? - Tom > > - Tom > > -- > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 8:43:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.gnf.org (relay.gnf.org [208.44.31.36]) by hub.freebsd.org (Postfix) with ESMTP id 7CE3037B40A; Thu, 18 Oct 2001 08:43:07 -0700 (PDT) Received: from mail.gnf.org (smtp.gnf.org [10.0.0.11]) by relay.gnf.org (8.11.6/8.11.6) with ESMTP id f9IFh7s26085; Thu, 18 Oct 2001 08:43:07 -0700 Received: by mail.gnf.org (Postfix, from userid 888) id 8C5C211E508; Thu, 18 Oct 2001 08:40:09 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id 86A8311A576; Thu, 18 Oct 2001 08:40:09 -0700 (PDT) Date: Thu, 18 Oct 2001 08:40:09 -0700 (PDT) From: Gordon Tetlow To: , Subject: New rc.d init script roadmap Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="658176-318202878-1003419609=:30874" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --658176-318202878-1003419609=:30874 Content-Type: TEXT/PLAIN; charset=US-ASCII Alright folks, I finally got off my butt last night and put together a roadmap for the migration to the new rc.d init scripts that were imported from NetBSD a long time ago and just sat in the tree. M1 (Patch included) Setup infrastructure Make rcorder compile Hook rc.subr into the distribution (and mergemaster) Hook rcorder into the world Add toggle in rc.conf to switch between rc_ng and current boot scripts M2 Get FreeBSD to boot with the new boot scripts Rewrite the /etc/rc.d scripts to work with FreeBSD M3 Add some FreeBSD specific support into rc.subr M4 Add true dependency checking to the infrastructure so that starting nfsd will start mountd and rpcbind Add support into rc.subr Add dependencies into rc.d scripts I'd like a couple of people to take a look at this and then I'll submit a pr for it if there aren't too many objections. I'm expecting M2 to run into quite a bikeshed, but hey, I got my nice shiny asbestos back from the cleaners. -gordon --658176-318202878-1003419609=:30874 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="rc-infrastructure.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="rc-infrastructure.diff" LS0tIGV0Yy9NYWtlZmlsZS5vcmlnCVdlZCBPY3QgMTcgMjA6MDQ6MDcgMjAw MQ0KKysrIGV0Yy9NYWtlZmlsZQlXZWQgT2N0IDE3IDIyOjI5OjM4IDIwMDEN CkBAIC0xMyw3ICsxMyw3IEBADQogCW1vdGQgbW9kZW1zIG5ldGNvbmZpZyBu ZXR3b3JrcyBuZXdzeXNsb2cuY29uZiBcDQogCXBhbS5jb25mIHBob25lcyBw cmludGNhcCBwcm9maWxlIHByb3RvY29scyBcDQogCXJjIHJjLmF0bSByYy5k ZXZmcyByYy5kaXNrbGVzczEgcmMuZGlza2xlc3MyIHJjLmZpcmV3YWxsIHJj LmZpcmV3YWxsNiBcDQotCXJjLm5ldHdvcmsgcmMubmV0d29yazYgcmMucGNj YXJkIHJjLnNlcmlhbCByYy5zaHV0ZG93biBcDQorCXJjLm5ldHdvcmsgcmMu bmV0d29yazYgcmMucGNjYXJkIHJjLnNlcmlhbCByYy5zaHV0ZG93biByYy5z dWJyIFwNCiAJcmMuc3lzY29ucyByYy5zeXNjdGwgcmVtb3RlIHJwYyBzZWN1 cml0eSBzZXJ2aWNlcyBzaGVsbHMgc3lzY3RsLmNvbmYgXA0KIAlzeXNsb2cu Y29uZiB1c2JkLmNvbmYgXA0KIAlldGMuJHtNQUNISU5FX0FSQ0h9L2Rpc2t0 YWIgXA0KLS0tIGV0Yy9yYy5kL01ha2VmaWxlLm9yaWcJV2VkIE9jdCAxNyAy MDowNDowMCAyMDAxDQorKysgZXRjL3JjLmQvTWFrZWZpbGUJV2VkIE9jdCAx NyAyMjoyNToyNiAyMDAxDQpAQCAtMSw4ICsxLDYgQEANCiAjICROZXRCU0Q6 IE1ha2VmaWxlLHYgMS4xNiAyMDAxLzAxLzE0IDE1OjM3OjIyIG1pbm91cmEg RXhwICQNCiANCi0uaW5jbHVkZSA8YnNkLm93bi5taz4NCi0NCi1GSUxFUz0J REFFTU9OIExPR0lOIE5FVFdPUksgU0VSVkVSUyBhY2NvdW50aW5nIGFtZCBh cG1kIGJvb3RwYXJhbXMgXA0KK0JJTj0JREFFTU9OIExPR0lOIE5FVFdPUksg U0VSVkVSUyBhY2NvdW50aW5nIGFtZCBhcG1kIGJvb3RwYXJhbXMgXA0KIAli b290Y29uZi5zaCBjY2QgY2xlYXJ0bXAgY3JvbiBkaGNsaWVudCBkaGNwZCBk aGNyZWxheSBkbWVzZyBcDQogCWZzY2sgZ2F0ZWQgaW5ldGQgaXBmaWx0ZXIg aXBtb24gaXBuYXQgaXBzZWMgaXNkbmQga2RjIGxkY29uZmlnIFwNCiAJbGtt MSBsa20yIGxrbTMgbG9jYWwgbHBkIG1vcGQgbW90ZCBtb3VudGFsbCBtb3Vu dGNyaXRsb2NhbCBcDQpAQCAtMTIsOSArMTAsMTIgQEANCiAJc2F2ZWNvcmUg c2NyZWVuYmxhbmsgc2VuZG1haWwgc2VjdXJlbGV2ZWwgc3NoZCBzd2FwMSBz d2FwMiBzeXNkYiBcDQogCXN5c2N0bCBzeXNsb2dkIHRpbWVkIHR0eXMgdmly ZWNvdmVyIHdzY29ucyB4ZG0geGZzIHlwYmluZCBcDQogCXlwcGFzc3dkZCB5 cHNlcnYNCi1GSUxFU0RJUj0JL2V0Yy9yYy5kDQotRklMRVNNT0RFPQkke0JJ Tk1PREV9DQogDQotTk9QUk9HPSBub3Byb2cNCitCSU5ESVI9CS9ldGMvcmMu ZA0KK05PT0JKPQ0KKw0KK2JlZm9yZWluc3RhbGw6DQorCSR7SU5TVEFMTH0g LWMgLW8gJHtCSU5PV059IC1nICR7QklOR1JQfSAtbSA3NTUgJHtCSU59IFwN CisJICAgICR7REVTVERJUn0ke0JJTkRJUn0NCiANCiAuaW5jbHVkZSA8YnNk LnByb2cubWs+DQotLS0gZXRjL2RlZmF1bHRzL3JjLmNvbmYub3JpZwlXZWQg T2N0IDE3IDIwOjAzOjU3IDIwMDENCisrKyBldGMvZGVmYXVsdHMvcmMuY29u ZglXZWQgT2N0IDE3IDIyOjQwOjU0IDIwMDENCkBAIC0xOSw2ICsxOSw3IEBA DQogIyMjICBJbXBvcnRhbnQgaW5pdGlhbCBCb290LXRpbWUgb3B0aW9ucyAg IyMjIyMjIyMjIyMjIyMjIyMjIyMNCiAjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIw0KIA0K K3JjX25nPSJOTyIJCSMgU2V0IHRvIFlFUyB0byBlbmFibGUgbmV3LXN0eWxl IHJjLiBFeHBlcmltZW50YWwuDQogc3dhcGZpbGU9Ik5PIgkJIyBTZXQgdG8g bmFtZSBvZiBzd2FwZmlsZSBpZiBhdXggc3dhcGZpbGUgZGVzaXJlZC4NCiBh cG1fZW5hYmxlPSJOTyIJCSMgU2V0IHRvIFlFUyB0byBlbmFibGUgQVBNIEJJ T1MgZnVuY3Rpb25zIChvciBOTykuDQogYXBtZF9lbmFibGU9Ik5PIgkjIFJ1 biBhcG1kIHRvIGhhbmRsZSBBUE0gZXZlbnQgZnJvbSB1c2VybGFuZC4NCi0t LSBldGMvcmMub3JpZwlXZWQgT2N0IDE3IDIwOjA0OjA2IDIwMDENCisrKyBl dGMvcmMJV2VkIE9jdCAxNyAyMjo0MDo1NCAyMDAxDQpAQCAtNzEsNiArNzEs MzAgQEANCiAJLiAvZXRjL3JjLmNvbmYNCiBmaQ0KIA0KK2Nhc2UgJHtyY19u Z30gaW4NCitbWXldW0VlXVtTc10pDQorCS4gL2V0Yy9yYy5zdWJyDQorDQor CV9yY19jb25mX2xvYWRlZD1ZRVMNCisNCisJaWYgWyAiJDEiID0gYXV0b2Jv b3QgXTsgdGhlbg0KKwkJYXV0b2Jvb3Q9eWVzDQorCQlfcmNfZmFzdF9ydW49 eWVzICAgICAgICAjIHJ1bl9yY19jb21tYW5kKCk6IGRvIGZhc3QgYm9vdGlu Zw0KKwlmaQ0KKw0KKwlmaWxlcz1gcmNvcmRlciAtcyBub3N0YXJ0IC9ldGMv cmMuZC8qYA0KKw0KKwlmb3IgX3JjX2VsZW0gaW4gJGZpbGVzOyBkbw0KKwkJ cnVuX3JjX3NjcmlwdCAkX3JjX2VsZW0gc3RhcnQNCisJZG9uZQ0KKw0KKwll eGl0IDANCisJOzsNCisqKQ0KKwkjIGZhbGwtdGhyb3VnaCB0byB0aGUgb2xk IHJjIHNjcmlwdHMNCisJOzsNCitlc2FjDQorDQogZmVlZF9kZXZfcmFuZG9t KCkgew0KIAlpZiBbIC1mICIkezF9IiAtYSAtciAiJHsxfSIgLWEgLXMgIiR7 MX0iIF07IHRoZW4NCiAjCQllY2hvICJVc2luZyAkezF9IGFzIGFuIGVudHJv cHkgZmlsZSINCi0tLSBldGMvcmMuc2h1dGRvd24ub3JpZwlXZWQgT2N0IDE3 IDIwOjA0OjA3IDIwMDENCisrKyBldGMvcmMuc2h1dGRvd24JV2VkIE9jdCAx NyAyMjo0MDo1NCAyMDAxDQpAQCAtNTIsNiArNTIsMjYgQEANCiAJLiAvZXRj L3JjLmNvbmYNCiBmaQ0KIA0KK2Nhc2UgJHtyY19uZ30gaW4NCitbWXldW0Vl XVtTc10pDQorCS4gL2V0Yy9yYy5zdWJyDQorDQorCWZpbGVzPWByY29yZGVy IC1rIHNodXRkb3duIC9ldGMvcmMuZC8qYA0KKwlmb3IgaSBpbiAkZmlsZXM7 IGRvICAgICAgICAgICAgICAgICAgICAgIyByZXZlcnNlIG9yZGVyIG9mIGZp bGVzDQorCQluZmlsZXM9IiRpICRuZmlsZXMiDQorCWRvbmUNCisJZmlsZXM9 JG5maWxlcw0KKw0KKwlmb3IgaSBpbiAkZmlsZXM7IGRvDQorCQlydW5fcmNf c2NyaXB0ICRpIHN0b3ANCisJZG9uZQ0KKw0KKwlleGl0IDANCisJOzsNCisq KQ0KKwk7Ow0KK2VzYWMNCisNCiAjIFdyaXRlIHNvbWUgZW50cm9weSBzbyB0 aGUgcmVib290aW5nIC9kZXYvcmFuZG9tIGNhbiByZXNlZWQNCiAjDQogY2Fz ZSAke2VudHJvcHlfZmlsZX0gaW4NCi0tLSBzYmluL3Jjb3JkZXIvTWFrZWZp bGUub3JpZwlTYXQgSnVuIDE2IDAwOjE2OjE0IDIwMDENCisrKyBzYmluL3Jj b3JkZXIvTWFrZWZpbGUJV2VkIE9jdCAxNyAyMTo1ODozNSAyMDAxDQpAQCAt MSw0ICsxLDUgQEANCiAjICAgICAgICROZXRCU0Q6IE1ha2VmaWxlLHYgMS4x IDE5OTkvMTEvMjMgMDU6Mjg6MjAgbXJnIEV4cCAkDQorU1lTIT0JdW5hbWUg LXMNCiANCiBQUk9HPSAgIHJjb3JkZXINCiBTUkNTPSAgIGVhbGxvYy5jIGhh c2guYyByY29yZGVyLmMNCkBAIC04LDYgKzksMTIgQEANCiBEUEFERCs9CSR7 TElCVVRJTH0NCiANCiAjIFhYWCBoYWNrIGZvciBtYWtlJ3MgaGFzaC5bY2hd DQorLmlmICR7U1lTfSA9PSBOZXRCU0QNCiBDUFBGTEFHUys9IC1ET1JERVIN CisuZWxpZiAke1NZU30gPT0gRnJlZUJTRA0KK0NGTEFHUys9IC1ET1JERVIN CisuZWxzZQ0KKy5lcnJvciAiVGhpcyBpcyBhbiB1bnN1cHBvcnRlZCBzeXN0 ZW0iDQorLmVuZGlmDQogDQogLmluY2x1ZGUgPGJzZC5wcm9nLm1rPg0KLS0t IHNiaW4vcmNvcmRlci9yY29yZGVyLmMub3JpZwlTYXQgSnVuIDE2IDAwOjE2 OjE0IDIwMDENCisrKyBzYmluL3Jjb3JkZXIvcmNvcmRlci5jCVdlZCBPY3Qg MTcgMjI6MDc6NTEgMjAwMQ0KQEAgLTQxLDcgKzQxLDkgQEANCiAjaW5jbHVk ZSA8c3RkbGliLmg+DQogI2luY2x1ZGUgPHN0cmluZy5oPg0KICNpbmNsdWRl IDx1bmlzdGQuaD4NCisjaWYgZGVmaW5lZChfX05ldEJTRF9fKQ0KICNpbmNs dWRlIDx1dGlsLmg+DQorI2VuZGlmDQogDQogI2luY2x1ZGUgImVhbGxvYy5o Ig0KICNpbmNsdWRlICJzcHJpdGUuaCINCi0tLSBzYmluL01ha2VmaWxlLm9y aWcJRnJpIFNlcCAyMSAxMDo1NTo0NyAyMDAxDQorKysgc2Jpbi9NYWtlZmls ZQlXZWQgT2N0IDE3IDIyOjA5OjQyIDIwMDENCkBAIC02NCw2ICs2NCw3IEBA DQogCXBpbmcgXA0KIAlwaW5nNiBcDQogCXF1b3RhY2hlY2sgXA0KKwlyY29y ZGVyIFwNCiAJcmVib290IFwNCiAJcmVzdG9yZSBcDQogCXJvdXRlIFwNCg== --658176-318202878-1003419609=:30874-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 9:20:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail36.sdc1.sfba.home.com (femail36.sdc1.sfba.home.com [24.254.60.26]) by hub.freebsd.org (Postfix) with ESMTP id 7E85637B407 for ; Thu, 18 Oct 2001 09:20:33 -0700 (PDT) Received: from laptop.baldwin.cx ([24.2.39.156]) by femail36.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20011018162033.XHEJ27661.femail36.sdc1.sfba.home.com@laptop.baldwin.cx>; Thu, 18 Oct 2001 09:20:33 -0700 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: Date: Thu, 18 Oct 2001 09:20:31 -0700 (PDT) From: John Baldwin To: Thomas Dixon Subject: RE: Problems with booting of CD-ROM (fwd) Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Oct-01 Thomas Dixon wrote: > > > On Tue, 16 Oct 2001, John Baldwin wrote: > >> >> On 17-Oct-01 Thomas Dixon wrote: >> > >> > >> > On Tue, 16 Oct 2001, John Baldwin wrote: >> > >> >> >> >> On 16-Oct-01 Thomas Dixon wrote: >> >> > I'm trying to make a bootable CD using the cdboot program that come >> >> > with >> >> > freeBSD in /sys/i386/boot/cdboot. The computer I'm trying to do this >> >> > on >> >> > definately boots other CDs as it has booted several other CDs. However >> >> > using a CD I've made using mkisofs and cdboot it gives the error; >> >> > >> >> > Your BIOS int 0x13 extensions seem to be disabled. >> >> > It's impossible to boot a CD-ROM without them. >> >> > (BIOS int 0x13 fn 0x4b01 yielded error 1) >> >> > >> >> > I'm using an Asus P5A motherboard, there appears to be no way to enable >> >> > the int 0x13 extensions in the BIOS and there is nothing in the manual >> >> > that refers to these. >> >> > >> >> > Any ideas why this error is coming up or how to fix it? >> >> >> >> Don't use cdboot or cdldr, they don't qutie work yet. :( >> >> >> >> Instead, make a floppy image and use that to boot. >> >> >> > I've tried this and I couldn't figure out the syntax for loader.rc to load >> > the file system from the cd-rom, any ideas? >> >> You don't really load the filesystem from the CD-ROM as the loader can't >> read a >> CD-ROM right now. Instead you use a memory filesystem on the floppy image >> and >> use that to boostrap yourself so you can mount the CD. > > I have done this now and it loads the mfsroot.gz file, however I can't > find any man pages or web pages that tell me how to create an mfsroot > file. Any ideas on this? > > - Tom Use dd from /dev/zero to create the file. Then use vnconfig (or mdconfig on -current) to create a disk device on top of the file. You can then disklabel and newfs the disk device, then mount it and stuff files in it like any other FFS filesystem. This is how picobsd and the release boot floppies work. -- 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 Thu Oct 18 10:46:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 6F9C737B409; Thu, 18 Oct 2001 10:46:08 -0700 (PDT) Received: from rac1.wam.umd.edu (IDENT:root@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id NAA12767; Thu, 18 Oct 2001 13:46:07 -0400 (EDT) Received: from rac1.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id NAA17852; Thu, 18 Oct 2001 13:46:06 -0400 (EDT) Received: from localhost (culverk@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id NAA17848; Thu, 18 Oct 2001 13:46:06 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Thu, 18 Oct 2001 13:46:06 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: altq question. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I was wondering if anyone had ever used altq to throttle people on an adsl connection. Basically what I want to do make each user share bandwidth evenly, but in such a way that they can use all the available bandwidth individually if nobody else is using it. However, I also want to be able to set aside some of that bandwidth for ssh. The problem is on my machine, with dummynet, I can do all this, but when I set it up to limit both incoming (608Kbit/s) and outgoing (128Kbit/sec) connections, the ping time through the machine goes up by 5 seconds, if I turn off the queuing options on the outgoing connections/packets, the ping returns to normal. Also, I can't figure out with altq how to set up different incoming and outgoing bandwidths. Does anyone have any experience doing anything like this with altq? if not, can someone tell me how to fix my ping problem with dummynet? Thanks. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 10:53:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 549A537B408; Thu, 18 Oct 2001 10:53:30 -0700 (PDT) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id f9IHoHg82428; Thu, 18 Oct 2001 10:50:17 -0700 (PDT) (envelope-from rizzo) Date: Thu, 18 Oct 2001 10:50:17 -0700 From: Luigi Rizzo To: Kenneth Wayne Culver Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: altq question. Message-ID: <20011018105017.A82131@iguana.aciri.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Oct 18, 2001 at 01:46:06PM -0400, Kenneth Wayne Culver wrote: > I was wondering if anyone had ever used altq to throttle people on an adsl > connection. Basically what I want to do make each user share bandwidth > evenly, but in such a way that they can use all the available bandwidth > individually if nobody else is using it. However, I also want to be able > to set aside some of that bandwidth for ssh. The problem is on my machine, > with dummynet, I can do all this, but when I set it up to limit both > incoming (608Kbit/s) and outgoing (128Kbit/sec) connections, the ping time > through the machine goes up by 5 seconds, if I turn off the queuing either you have set the bandwidth wrong (does "ipfw pipe show" list the speed you want for the pipes ? can you post its output ?) or you are doing the measurement on a saturated link, in which case when you use dummynet with dynamic queues you have a lot more buffering going on, and this would explain why you see higher ping times (but perhaps without it you see some large amount of losses) ? cheers luigi > options on the outgoing connections/packets, the ping returns to > normal. Also, I can't figure out with altq how to set up different > incoming and outgoing bandwidths. Does anyone have any experience doing > anything like this with altq? if not, can someone tell me how to fix my > ping problem with dummynet? Thanks. > > Ken > > > 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 Oct 18 12:42:13 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 C38A637B403; Thu, 18 Oct 2001 12:42:08 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 9E4CA14C2E; Thu, 18 Oct 2001 21:42:01 +0200 (CEST) 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: Gordon Tetlow Cc: , Subject: Re: New rc.d init script roadmap References: From: Dag-Erling Smorgrav Date: 18 Oct 2001 21:42:01 +0200 In-Reply-To: Message-ID: Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Gordon Tetlow writes: > M1 (Patch included) > Setup infrastructure > Make rcorder compile Your rcorder patch is incorrect. FreeBSD lacks a prototype for fparseln(). It so happens that it doesn't make any difference on any of the platforms FreeBSD supports (because our ints and pointers are the same size), but that's no reason not to do things right. Also, I don't see the point in munging the Makefile like you do - I think we can live with having a Makefile that's slightly (and trivially) different from NetBSD's. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 12:47:58 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 E882937B403; Thu, 18 Oct 2001 12:47:54 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 973B114C2E; Thu, 18 Oct 2001 21:47:53 +0200 (CEST) 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: Gordon Tetlow Cc: , Subject: Re: New rc.d init script roadmap References: From: Dag-Erling Smorgrav Date: 18 Oct 2001 21:47:53 +0200 In-Reply-To: Message-ID: Lines: 9 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > Your rcorder patch is incorrect. Here's a correct patch. Does anybody mind if I commit this and connect rcorder(8) to the build? DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 12:48:28 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 E067937B40D; Thu, 18 Oct 2001 12:48:04 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id D94C314C41; Thu, 18 Oct 2001 21:48:03 +0200 (CEST) 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: Gordon Tetlow Cc: , Subject: Re: New rc.d init script roadmap References: From: Dag-Erling Smorgrav Date: 18 Oct 2001 21:48:03 +0200 In-Reply-To: Message-ID: Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-=-= Dag-Erling Smorgrav writes: > Your rcorder patch is incorrect. Here's a correct patch. Does anybody mind if I commit this and connect rcorder(8) to the build? DES -- Dag-Erling Smorgrav - des@ofug.org --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=rcorder.diff Index: Makefile =================================================================== RCS file: /home/ncvs/src/sbin/rcorder/Makefile,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 Makefile --- Makefile 16 Jun 2001 07:16:14 -0000 1.1.1.1 +++ Makefile 18 Oct 2001 19:44:57 -0000 @@ -3,11 +3,12 @@ PROG= rcorder SRCS= ealloc.c hash.c rcorder.c MAN= rcorder.8 +WARNS?= 2 LDADD+= -lutil DPADD+= ${LIBUTIL} # XXX hack for make's hash.[ch] -CPPFLAGS+= -DORDER +CFLAGS+= -DORDER .include Index: rcorder.c =================================================================== RCS file: /home/ncvs/src/sbin/rcorder/rcorder.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 rcorder.c --- rcorder.c 16 Jun 2001 07:16:14 -0000 1.1.1.1 +++ rcorder.c 18 Oct 2001 19:45:27 -0000 @@ -41,7 +41,11 @@ #include #include #include +#if defined(__NetBSD__) #include +#else +char *fparseln(FILE *, size_t *, size_t *, const char[3], int); +#endif #include "ealloc.h" #include "sprite.h" --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 12:49:23 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 8DC0537B408; Thu, 18 Oct 2001 12:49:06 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 8309714C2E; Thu, 18 Oct 2001 21:49:05 +0200 (CEST) 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: Gordon Tetlow Cc: , Subject: Re: New rc.d init script roadmap References: From: Dag-Erling Smorgrav Date: 18 Oct 2001 21:49:05 +0200 In-Reply-To: Message-ID: Lines: 11 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-=-= Dag-Erling Smorgrav writes: > Here's a correct patch. Murphy's Law of Attachments, etc. DES -- Dag-Erling Smorgrav - des@ofug.org --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=rcorder.diff Index: Makefile =================================================================== RCS file: /home/ncvs/src/sbin/rcorder/Makefile,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 Makefile --- Makefile 16 Jun 2001 07:16:14 -0000 1.1.1.1 +++ Makefile 18 Oct 2001 19:44:57 -0000 @@ -3,11 +3,12 @@ PROG= rcorder SRCS= ealloc.c hash.c rcorder.c MAN= rcorder.8 +WARNS?= 2 LDADD+= -lutil DPADD+= ${LIBUTIL} # XXX hack for make's hash.[ch] -CPPFLAGS+= -DORDER +CFLAGS+= -DORDER .include Index: rcorder.c =================================================================== RCS file: /home/ncvs/src/sbin/rcorder/rcorder.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 rcorder.c --- rcorder.c 16 Jun 2001 07:16:14 -0000 1.1.1.1 +++ rcorder.c 18 Oct 2001 19:45:27 -0000 @@ -41,7 +41,11 @@ #include #include #include +#if defined(__NetBSD__) #include +#else +char *fparseln(FILE *, size_t *, size_t *, const char[3], int); +#endif #include "ealloc.h" #include "sprite.h" --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 13:34:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.gnf.org (relay.gnf.org [208.44.31.36]) by hub.freebsd.org (Postfix) with ESMTP id 4F7E637B408; Thu, 18 Oct 2001 13:34:49 -0700 (PDT) Received: from mail.gnf.org (smtp.gnf.org [10.0.0.11]) by relay.gnf.org (8.11.6/8.11.6) with ESMTP id f9IKYns31671; Thu, 18 Oct 2001 13:34:49 -0700 Received: by mail.gnf.org (Postfix, from userid 888) id 94D3111E508; Thu, 18 Oct 2001 13:31:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id 90EA311A572; Thu, 18 Oct 2001 13:31:51 -0700 (PDT) Date: Thu, 18 Oct 2001 13:31:51 -0700 (PDT) From: Gordon Tetlow To: Dag-Erling Smorgrav Cc: , Subject: Re: New rc.d init script roadmap In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18 Oct 2001, Dag-Erling Smorgrav wrote: > Gordon Tetlow writes: > > M1 (Patch included) > > Setup infrastructure > > Make rcorder compile > > Your rcorder patch is incorrect. FreeBSD lacks a prototype for > fparseln(). It so happens that it doesn't make any difference on any > of the platforms FreeBSD supports (because our ints and pointers are > the same size), but that's no reason not to do things right. I was wondering about that warning myself, but it seemed to work and I don't try to pretend to be a master of C. I'll stick to the shell world in general. > Also, I don't see the point in munging the Makefile like you do - I > think we can live with having a Makefile that's slightly (and > trivially) different from NetBSD's. Fair enough, everyone seemed to be touting the flag of portability so I just added it into the mix as well. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 13:38:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.gnf.org (relay.gnf.org [208.44.31.36]) by hub.freebsd.org (Postfix) with ESMTP id 3717837B40A; Thu, 18 Oct 2001 13:38:26 -0700 (PDT) Received: from mail.gnf.org (smtp.gnf.org [10.0.0.11]) by relay.gnf.org (8.11.6/8.11.6) with ESMTP id f9IKcQs31735; Thu, 18 Oct 2001 13:38:26 -0700 Received: by mail.gnf.org (Postfix, from userid 888) id 8F2DC11E508; Thu, 18 Oct 2001 13:35:28 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id 889A311A572; Thu, 18 Oct 2001 13:35:28 -0700 (PDT) Date: Thu, 18 Oct 2001 13:35:28 -0700 (PDT) From: Gordon Tetlow To: Dag-Erling Smorgrav Cc: , Subject: Re: New rc.d init script roadmap In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18 Oct 2001, Dag-Erling Smorgrav wrote: > Dag-Erling Smorgrav writes: > > Your rcorder patch is incorrect. > > Here's a correct patch. Does anybody mind if I commit this and > connect rcorder(8) to the build? Actually, fparseln() is defined in libutil.h (per the man page). I don't have my current box available (power outage at home), but if you could look over it, it should work. -gordon Index: rcorder.c =================================================================== RCS file: /home/ncvs/src/sbin/rcorder/rcorder.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 rcorder.c --- rcorder.c 16 Jun 2001 07:16:14 -0000 1.1.1.1 +++ rcorder.c 18 Oct 2001 19:45:27 -0000 @@ -41,7 +41,11 @@ #include #include #include +#if defined(__NetBSD__) #include +#else +#include +#endif #include "ealloc.h" #include "sprite.h" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 13:42:53 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 2279D37B408; Thu, 18 Oct 2001 13:42:49 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id C5EC314C2E; Thu, 18 Oct 2001 22:42:47 +0200 (CEST) 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: Gordon Tetlow Cc: , Subject: Re: New rc.d init script roadmap References: From: Dag-Erling Smorgrav Date: 18 Oct 2001 22:42:47 +0200 In-Reply-To: Message-ID: Lines: 11 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Gordon Tetlow writes: > Actually, fparseln() is defined in libutil.h (per the man page). I don't > have my current box available (power outage at home), but if you could > look over it, it should work. Ah, that's right - I couldn't find the right header, I should have simply looked at the libutil Makefile. Thanks! DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 13:44:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 4707037B409; Thu, 18 Oct 2001 13:44:24 -0700 (PDT) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA01179; Thu, 18 Oct 2001 16:44:21 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id QAA26723; Thu, 18 Oct 2001 16:44:21 -0400 (EDT) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA26717; Thu, 18 Oct 2001 16:44:21 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Thu, 18 Oct 2001 16:44:20 -0400 (EDT) From: Kenneth Wayne Culver To: Luigi Rizzo Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: altq question. In-Reply-To: <20011018105017.A82131@iguana.aciri.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > either you have set the bandwidth wrong (does "ipfw pipe show" > list the speed you want for the pipes ? can you post its > output ?) or you are doing the measurement on a saturated link, > in which case when you use dummynet with dynamic queues you have > a lot more buffering going on, and this would explain why you > see higher ping times (but perhaps without it you see some > large amount of losses) ? > ipfw pipe show shows the correct amounts. I did the measurements on a non-saturated link, I'm sure of this because when I ipfw flush, ipfw queue flush, the ping goes back to normal. I have no packet loss either way, whether dummynet is configured or not. An added note, this is running on an 533 MHz alpha with a de type card hooked to the dsl modem running at 10Mbit/sec full duplex (dsl connection is rated at 608Kbit/s down and 128 Kbit/s up), and an xl type card connected to the internal net running at 100Mbit/sec Full duplex. My configuration looks like this: ipfw add queue 1 ip from any to x.x.x.x/24 in via de0 ipfw add queue 2 ip from x.x.x.x/24 to any out via de0 ipfw pipe 1 config bw 570Kbit/s queue 47 ipfw pipe 2 config bw 118Kbit/s queue 10 ipfw queue 1 config pipe 1 weight 40 mask dst-ip 0x000000ff ipfw queue 2 config pipe 2 weight 40 mask src-ip 0x000000ff I set it to 570Kbit/s download because this is the top download speed I measured (I get this speed to pretty much every site I download from, to arrive at this number I downloaded a file 2 times from a site that gave me around 62Kbytes/sec (my max speed), then I turned on queueing with successively larger bw values for pipe 1 until I could attain my top speed, then I added 10 Kbit/s just to be sure that I was getting the full wirespeed my connection would support. I did this for the upstream as well) Thanks for your help. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 13:48:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.noos.fr (verlaine.noos.net [212.198.2.73]) by hub.freebsd.org (Postfix) with ESMTP id 762C537B403 for ; Thu, 18 Oct 2001 13:48:04 -0700 (PDT) Received: (qmail 38692662 invoked by uid 0); 18 Oct 2001 20:48:02 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.231.187]) (envelope-sender ) by 212.198.2.73 (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 18 Oct 2001 20:48:02 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.6/8.11.6) id f9IKlsk06562; Thu, 18 Oct 2001 22:47:54 +0200 (CEST) (envelope-from root) Message-Id: <200110182047.f9IKlsk06562@gits.dyndns.org> Subject: Re: Problems with booting of CD-ROM (fwd) In-Reply-To: To: Thomas Dixon Date: Thu, 18 Oct 2001 22:47:54 +0200 (CEST) Cc: John Baldwin , hackers@FreeBSD.ORG Reply-To: clefevre@citeweb.net From: Cyrille Lefevre Organization: ACME X-Face: X-Mailer: ELM [version 2.4ME+ PL94c (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thomas Dixon wrote: [snip] > I have done this now and it loads the mfsroot.gz file, however I can't > find any man pages or web pages that tell me how to create an mfsroot > file. Any ideas on this? see boot.flp target in /usr/src/release/Makefile it is much simple to work on the original boot.flp or mfsroot.flp, such as : mkdir /kern /flp /mfs vnconfig -c /dev/vn0c /tmp/kern.flp mount -t ufs /dev/vn0c /kern ls -l /kern drwxr-xr-x 2 root wheel 512 Apr 21 13:15 boot -r-xr-xr-x 1 root wheel 1241170 Apr 21 13:15 kernel.gz do your stuffs on /kern (use gzip -9 instead of kgzip is you replace the kernel, it a little bit more efficient). umount /kern vnconfig -u /dev/vn0c vnconfig -c /dev/vn0c /tmp/mfsroot.flp mount -t ufs /dev/vn0c /flp ls -l /flp -rw-r--r-- 1 root wheel 860566 Apr 21 13:11 mfsroot.gz gzcat < /iso/mfsroot.gz > /tmp/mfsroot vnconfig -c /dev/vn1c /tmp/mfsroot mount -t ufs /dev/vn1c /mfs ls -l /mfs lrwxrwxrwx 1 root wheel 6 Apr 21 13:11 bin -> /stand drwxr-xr-x 2 root wheel 512 Apr 21 13:11 boot drwxr-xr-x 2 root wheel 512 Apr 21 13:11 dev drwxr-xr-x 3 root wheel 512 Apr 21 13:11 etc drwxr-xr-x 2 root wheel 512 Apr 21 13:11 mnt lrwxrwxrwx 1 root wheel 6 Apr 21 13:11 sbin -> /stand drwxr-xr-x 4 root wheel 1024 Apr 21 13:11 stand do your stuffs on /mfs then reverse everything... umount /mfs vnconfig -u /dev/vn1c gzip -9 < /tmp/mfsroot > /flp/mfsroot.gz umount /flp vnconfig -u /dev/vn0c not tested but should work... Cyrille. -- Cyrille Lefevre mailto:clefevre@citeweb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 14:14: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbeast.ahaza.com (mailbeast.ahaza.com [209.180.221.132]) by hub.freebsd.org (Postfix) with ESMTP id 0182B37B405 for ; Thu, 18 Oct 2001 14:14:05 -0700 (PDT) Received: from akira.ahaza.com (akira.ahaza.com [172.16.30.230]) by relay.ux.ahaza.com (8.11.1/8.11.1) with ESMTP id f9ILBtr19634 for ; Thu, 18 Oct 2001 14:11:55 -0700 (PDT) (envelope-from twiess@ahaza.com) Date: Thu, 18 Oct 2001 14:12:06 -0700 (PDT) From: Tim Wiess X-X-Sender: To: Subject: Re: FYI Message-ID: <20011018141145.V1415-100000@akira.ahaza.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > If anyone has an interest in adding support for the SBS WAN cards to > FreeBSD, feel free to contact me. I'll be glad to help. I'm actually working on a driver for the SBS WANic 600 and 800 cards. There is still a lot of work and testing to be done, but (assuming there are no problems with the powers that be over here, and there are no conflicts with our agreements with SBS) I do eventually plan on posting the code (under a BSD license). I'll keep y'all posted. tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 14:15:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbeast.ahaza.com (mailbeast.ahaza.com [209.180.221.132]) by hub.freebsd.org (Postfix) with ESMTP id 8CA4C37B403 for ; Thu, 18 Oct 2001 14:15:26 -0700 (PDT) Received: from akira.ahaza.com (akira.ahaza.com [172.16.30.230]) by mailbeast.ahaza.com (8.11.1/8.11.1) with ESMTP id f9ILFQb19693 for ; Thu, 18 Oct 2001 14:15:26 -0700 (PDT) (envelope-from twiess@ahaza.com) Date: Thu, 18 Oct 2001 14:15:36 -0700 (PDT) From: Tim Wiess X-X-Sender: To: Subject: Re: FYI Message-ID: <20011018141516.V1415-100000@akira.ahaza.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > If anyone has an interest in adding support for the SBS WAN cards to > FreeBSD, feel free to contact me. I'll be glad to help. I'm actually working on a driver for the SBS WANic 600 and 800 cards. There is still a lot of work and testing to be done, but (assuming there are no problems with the powers that be over here, and there are no conflicts with our agreements with SBS) I do eventually plan on posting the code (under a BSD license). I'll keep y'all posted. tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 14:30:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.noos.fr (racine.noos.net [212.198.2.71]) by hub.freebsd.org (Postfix) with ESMTP id 3A79B37B40A for ; Thu, 18 Oct 2001 14:30:03 -0700 (PDT) Received: (qmail 7736643 invoked by uid 0); 18 Oct 2001 21:30:01 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.231.187]) (envelope-sender ) by 212.198.2.71 (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 18 Oct 2001 21:30:01 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.6/8.11.6) id f9ILTxH07817; Thu, 18 Oct 2001 23:29:59 +0200 (CEST) (envelope-from root) Message-Id: <200110182129.f9ILTxH07817@gits.dyndns.org> Subject: Re: New rc.d init script roadmap In-Reply-To: To: Gordon Tetlow Date: Thu, 18 Oct 2001 23:29:59 +0200 (CEST) Cc: arch@freebsd.org, hackers@freebsd.org, chris@freebsd.org, rwatson@freebsd.org, sheldonh@freebsd.org Reply-To: clefevre@citeweb.net From: Cyrille Lefevre Organization: ACME X-Face: X-Mailer: ELM [version 2.4ME+ PL94c (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM1003440599-5614-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ELM1003440599-5614-0_ Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Hi, I've prepared a status report about this project. the xml file in attachment have to be reviewed since I've just put descriptions from FreeBSD-rc's Yahoo! Group and your email message. first of all, there should be a consensus about the owner of this project ? also, who create the FreeBSD-rc's Yahoo! Group ? then you have to submit a status report to avoid duplicates work... I also done some stuffs on this some months ago, but I have to review it. don't remember the status of my job... :( Cyrille. -- Cyrille Lefevre mailto:clefevre@citeweb.net --ELM1003440599-5614-0_ Content-Transfer-Encoding: 7bit Content-Type: text/xml Content-Disposition: attachment; filename=report.xml Content-Description: report.xml Improving FreeBSD startup scripts Doug Barton Commiter DougB@FreeBSD.org Gordon Tetlow Contributor gordont@gnf.org Improving FreeBSD startup scripts Luke Mewburn's papers NetBSD Initialization and Services Control <-- from http://groups.yahoo.com/group/FreeBSD-rc/ -->

This group is for discussion about the startup scripts in FreeBSD, primarily the scripts in /etc/rc*. Primary focus will be on improvements and importation of NetBSD's excellent work on this topic.

<-- from Pine.LNX.4.33.0110180824570.30874-200000@smtp.gnf.org -->

Alright folks, I finally got off my butt last night and put together a roadmap for the migration to the new rc.d init scripts that were imported from NetBSD a long time ago and just sat in the tree.

M1 (Patch included)
Setup infrastructure
Make rcorder compile
Hook rc.subr into the distribution (and mergemaster)
Hook rcorder into the world
Add toggle in rc.conf to switch between rc_ng and current boot scripts

M2
Get FreeBSD to boot with the new boot scripts
Rewrite the /etc/rc.d scripts to work with FreeBSD

M3
Add some FreeBSD specific support into rc.subr

M4
Add true dependency checking to the infrastructure so that starting nfsd will start mountd and rpcbind
Add support into rc.subr
Add dependencies into rc.d scripts

I'd like a couple of people to take a look at this and then I'll submit a pr for it if there aren't too many objections. I'm expecting M2 to run into quite a bikeshed, but hey, I got my nice shiny asbestos back from the cleaners.

 --ELM1003440599-5614-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 14:33:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail11.sdc1.sfba.home.com (femail11.sdc1.sfba.home.com [24.0.95.107]) by hub.freebsd.org (Postfix) with ESMTP id 2FD6B37B401; Thu, 18 Oct 2001 14:33:52 -0700 (PDT) Received: from laptop.baldwin.cx ([24.2.39.156]) by femail11.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20011018213350.QCEE4652.femail11.sdc1.sfba.home.com@laptop.baldwin.cx>; Thu, 18 Oct 2001 14:33:50 -0700 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: Date: Thu, 18 Oct 2001 14:33:39 -0700 (PDT) From: John Baldwin To: Dag-Erling Smorgrav Subject: Re: New rc.d init script roadmap Cc: hackers@freebsd.org, arch@freebsd.org, Gordon Tetlow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Oct-01 Dag-Erling Smorgrav wrote: > Gordon Tetlow writes: >> M1 (Patch included) >> Setup infrastructure >> Make rcorder compile > > Your rcorder patch is incorrect. FreeBSD lacks a prototype for > fparseln(). It so happens that it doesn't make any difference on any > of the platforms FreeBSD supports (because our ints and pointers are > the same size), but that's no reason not to do things right. Huh? Int on alpha is 32, and pointer is 64. -- 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 Thu Oct 18 14:34:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fortinbras.sanjose.wwwi.com (fortinbras.sanjose.wwwi.com [199.1.92.20]) by hub.freebsd.org (Postfix) with ESMTP id 6F53437B409 for ; Thu, 18 Oct 2001 14:34:05 -0700 (PDT) Received: from polonius (dhcp105.houston.wwwi.com [199.1.94.105]) by fortinbras.sanjose.wwwi.com (8.10.2/8.10.2) with SMTP id f9ILY5H20997 for ; Thu, 18 Oct 2001 14:34:05 -0700 (PDT) From: "Jeffrey D. Wheelhouse" To: Subject: Circular log patches for syslog Date: Thu, 18 Oct 2001 16:32:09 -0500 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 V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, While working on another project, I made some patches to syslogd to support circular logfiles: http://software.wwwi.com/syslogd/ The syslogd patch includes changes to the man page to reflect the new usage. I don't know if this is useful to anyone else, but it came in handy for me on a small-footprint embedded project that couldn't afford to let logs grow unbounded. We have been using this in house without problems for awhile now. Any feedback on this would be appreciated. Thanks, Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 14:35:17 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 952AA37B403; Thu, 18 Oct 2001 14:35:13 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 650A714C2E; Thu, 18 Oct 2001 23:35:12 +0200 (CEST) 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: John Baldwin Cc: hackers@freebsd.org, arch@freebsd.org, Gordon Tetlow Subject: Re: New rc.d init script roadmap References: From: Dag-Erling Smorgrav Date: 18 Oct 2001 23:35:11 +0200 In-Reply-To: Message-ID: Lines: 9 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin writes: > Huh? Int on alpha is 32, and pointer is 64. I thought we were ILP64 on 64-bit archs, but you're right. And I ought to know better... DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 15:20:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.noos.fr (claudel.noos.net [212.198.2.83]) by hub.freebsd.org (Postfix) with ESMTP id A78F537B408 for ; Thu, 18 Oct 2001 15:20:09 -0700 (PDT) Received: (qmail 1293418 invoked by uid 0); 18 Oct 2001 22:20:05 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.231.187]) (envelope-sender ) by 212.198.2.83 (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 18 Oct 2001 22:20:05 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.6/8.11.6) id f9IMK3Z10669; Fri, 19 Oct 2001 00:20:03 +0200 (CEST) (envelope-from root) Message-Id: <200110182220.f9IMK3Z10669@gits.dyndns.org> Subject: Re: New rc.d init script roadmap In-Reply-To: <200110182129.f9ILTxH07817@gits.dyndns.org> To: clefevre@citeweb.net Date: Fri, 19 Oct 2001 00:20:03 +0200 (CEST) Cc: Gordon Tetlow , arch@freebsd.org, hackers@freebsd.org, chris@freebsd.org, rwatson@freebsd.org, sheldonh@freebsd.org Reply-To: clefevre@citeweb.net From: Cyrille Lefevre Organization: ACME X-Face: X-Mailer: ELM [version 2.4ME+ PL94c (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM1003443603-10647-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ELM1003443603-10647-0_ Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII after reading -arch, the contact and links sections have been updated. Cyrille. -- Cyrille Lefevre mailto:clefevre@citeweb.net --ELM1003443603-10647-0_ Content-Transfer-Encoding: 7bit Content-Type: text/xml Content-Disposition: attachment; filename=report.xml Content-Description: report.xml rcNG: Improving FreeBSD startup scripts Doug Barton Commiter DougB@FreeBSD.org Kevin Way Contributor Kevin.Way@overtone.org Gordon Tetlow Contributor gordont@gnf.org Improving FreeBSD startup scripts Luke Mewburn's papers NetBSD Initialization and Services Control FreeBSD rc.d reorganization project <-- from http://groups.yahoo.com/group/FreeBSD-rc/ -->

This group is for discussion about the startup scripts in FreeBSD, primarily the scripts in /etc/rc*. Primary focus will be on improvements and importation of NetBSD's excellent work on this topic.

<-- from Pine.LNX.4.33.0110180824570.30874-200000@smtp.gnf.org -->

Alright folks, I finally got off my butt last night and put together a roadmap for the migration to the new rc.d init scripts that were imported from NetBSD a long time ago and just sat in the tree.

M1 (Patch included)
Setup infrastructure
Make rcorder compile
Hook rc.subr into the distribution (and mergemaster)
Hook rcorder into the world
Add toggle in rc.conf to switch between rc_ng and current boot scripts

M2
Get FreeBSD to boot with the new boot scripts
Rewrite the /etc/rc.d scripts to work with FreeBSD

M3
Add some FreeBSD specific support into rc.subr

M4
Add true dependency checking to the infrastructure so that starting nfsd will start mountd and rpcbind
Add support into rc.subr
Add dependencies into rc.d scripts

I'd like a couple of people to take a look at this and then I'll submit a pr for it if there aren't too many objections. I'm expecting M2 to run into quite a bikeshed, but hey, I got my nice shiny asbestos back from the cleaners.

 --ELM1003443603-10647-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 15:25:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.noos.fr (descartes.noos.net [212.198.2.74]) by hub.freebsd.org (Postfix) with ESMTP id D7BE337B409 for ; Thu, 18 Oct 2001 15:25:24 -0700 (PDT) Received: (qmail 28443635 invoked by uid 0); 18 Oct 2001 22:25:23 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.231.187]) (envelope-sender ) by 212.198.2.74 (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 18 Oct 2001 22:25:23 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.6/8.11.6) id f9IMPMG10961; Fri, 19 Oct 2001 00:25:22 +0200 (CEST) (envelope-from root) Message-Id: <200110182225.f9IMPMG10961@gits.dyndns.org> Subject: Re: Circular log patches for syslog In-Reply-To: To: "Jeffrey D. Wheelhouse" Date: Fri, 19 Oct 2001 00:25:22 +0200 (CEST) Cc: freebsd-hackers@freebsd.org Reply-To: clefevre@citeweb.net From: Cyrille Lefevre Organization: ACME X-Face: X-Mailer: ELM [version 2.4ME+ PL94c (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jeffrey D. Wheelhouse wrote: > > While working on another project, I made some patches to syslogd to support > circular logfiles: > > http://software.wwwi.com/syslogd/ > > The syslogd patch includes changes to the man page to reflect the new usage. how do you decide the size of the circular log ? Cyrille. -- Cyrille Lefevre mailto:clefevre@citeweb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 15:38:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fortinbras.sanjose.wwwi.com (fortinbras.sanjose.wwwi.com [199.1.92.20]) by hub.freebsd.org (Postfix) with ESMTP id AE8F237B409 for ; Thu, 18 Oct 2001 15:38:45 -0700 (PDT) Received: from polonius (dhcp105.houston.wwwi.com [199.1.94.105]) by fortinbras.sanjose.wwwi.com (8.10.2/8.10.2) with SMTP id f9IMchH22063; Thu, 18 Oct 2001 15:38:43 -0700 (PDT) From: "Jeffrey D. Wheelhouse" To: , "Jeffrey D. Wheelhouse" Cc: Subject: RE: Circular log patches for syslog Date: Thu, 18 Oct 2001 17:36:48 -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 V6.00.2600.0000 Importance: Normal In-Reply-To: <200110182225.f9IMPMG10961@gits.dyndns.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > -----Original Message----- > > how do you decide the size of the circular log ? There's a utility included to unwind the log file into time order. It includes a command line option to create logfiles of user-defined size. http://software.wwwi.com/syslogd/clog.html Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 16:47:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web11404.mail.yahoo.com (web11404.mail.yahoo.com [216.136.131.234]) by hub.freebsd.org (Postfix) with SMTP id 1954E37B409 for ; Thu, 18 Oct 2001 16:47:16 -0700 (PDT) Message-ID: <20011018234715.26096.qmail@web11404.mail.yahoo.com> Received: from [24.43.32.161] by web11404.mail.yahoo.com via HTTP; Thu, 18 Oct 2001 16:47:15 PDT Date: Thu, 18 Oct 2001 16:47:15 -0700 (PDT) From: Rayson Ho Subject: Re: clustering code To: hackers@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If you are going to build clusters with over 1000 nodes, you should then install a batch system instead of using kernel-based clustering services. Rayson --- Ronald G Minnich wrote: > well that's just wrong. 4 nodes? nope. I've got buddies at bio > startups > who start at 1024 nodes. There's lots of other companies too. > > ron > __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 17:38:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wombat.bytecraft.au.com (wombat.bytecraft.au.com [203.39.118.3]) by hub.freebsd.org (Postfix) with ESMTP id 0290037B403 for ; Thu, 18 Oct 2001 17:38:29 -0700 (PDT) Received: from lt99101401.bytecraft.au.com (unknown [203.39.118.42]) by wombat.bytecraft.au.com (Postfix) with SMTP id 01B643F41; Fri, 19 Oct 2001 10:38:26 +1000 (EST) Message-ID: <01f801c15836$5d4a1920$2a7627cb@bytecraft.au.com> Reply-To: "MurrayTaylor" From: "MurrayTaylor" To: "Tim Wiess" , References: <20011018141145.V1415-100000@akira.ahaza.com> Subject: Re: FYI Date: Fri, 19 Oct 2001 10:38:25 +1000 Organization: Bytecraft Systems 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Tim Wiess" To: Sent: Friday, October 19, 2001 7:12 AM Subject: Re: FYI > > If anyone has an interest in adding support for the SBS WAN cards to > > FreeBSD, feel free to contact me. I'll be glad to help. > > I'm actually working on a driver for the SBS WANic 600 and 800 cards. > There is still a lot of work and testing to be done, but (assuming there > are no problems with the powers that be over here, and there are no > conflicts with our agreements with SBS) I do eventually plan on posting > the code (under a BSD license). > > I'll keep y'all posted. > > tim > Yay Tim .... Unfortunately my skills(?) lie in the database arena or I would have jumped in myself a _LOT_ earlier and try to solve the EOL runout myself..... Murray T > > > 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 Oct 18 18:24:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with SMTP id 8841C37B401 for ; Thu, 18 Oct 2001 18:24:08 -0700 (PDT) Received: (qmail 1128720 invoked from network); 18 Oct 2001 19:24:08 -0600 Received: from snaresland.acl.lanl.gov (128.165.147.113) by acl.lanl.gov with SMTP; 18 Oct 2001 19:24:08 -0600 Received: (qmail 22696 invoked by uid 3499); 18 Oct 2001 19:24:07 -0600 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 18 Oct 2001 19:24:07 -0600 Date: Thu, 18 Oct 2001 19:24:07 -0600 (MDT) From: Ronald G Minnich X-X-Sender: To: Rayson Ho Cc: Subject: Re: clustering code In-Reply-To: <20011018234715.26096.qmail@web11404.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 18 Oct 2001, Rayson Ho wrote: > If you are going to build clusters with over 1000 nodes, you should > then install a batch system instead of using kernel-based clustering > services. I thought we took this one private. Anyway, as I said in private, scalable kernel services for clustering and batch systems are orthogonal, hence I don't agree. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 19:52:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp006pub.verizon.net (smtp006pub.verizon.net [206.46.170.185]) by hub.freebsd.org (Postfix) with ESMTP id 0C7B737B401; Thu, 18 Oct 2001 19:51:45 -0700 (PDT) Received: from bellatlantic.net (pool-151-198-135-141.mad.east.verizon.net [151.198.135.141]) by smtp006pub.verizon.net with ESMTP ; id f9J2oas20977 Thu, 18 Oct 2001 21:50:37 -0500 (CDT) Message-ID: <3BCF94FB.50F5D295@bellatlantic.net> Date: Thu, 18 Oct 2001 22:50:35 -0400 From: Sergey Babkin Reply-To: babkin@FreeBSD.ORG X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Ted Mittelstaedt Cc: Doug Hass , Leo Bicknell , Jim Bryant , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: FYI References: <000001c1578a$f7962480$1401a8c0@tedm.placo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ted Mittelstaedt wrote: > > >From: Doug Hass [mailto:dhass@imagestream.com] > >The lack of flexibility in accepting various requirements illustrates the > >difference between an OS WITH legs in the market and one WITHOUT legs. > > > >Much to my chagrin, FreeBSD continues to fall more and more into the > >latter category. > > > > This is a gross simplification of a great many issues. I fail to see why you > feel that FreeBSD is threatening anyone's IP and I don't understand why you > are reacting this way. Any company is free to take the FreeBSD distribution > and customize it the way they want and include any proprietary and binary code > they > want and hand out distributions as they see fit. Imagestream could do this Well, honestly, FreeBSD makes the life of the developers of third-party binary-only drivers fairly difficult. The reason is that there are a lot of API changes happening between the releases (take Julian Elisher's recent problem for example). So the driver writers are forced to at least recompile their drivers for each release. Plus people are very active at ripping away the old APIs even when there is no immediate need for that nor benefit from it (think of phk's removal of the LIST-something macros). So often not a simple recompilation but a noticeable rewrite may be required for a driver between different versions of FreeBSD. That actually is true not only for the drivers but for the usual binaries too. For example, there seems to be no way to combine COFF and ELF libraries into one executable. That made porting of Lyx to 4.0 unfeasible, as the binary-only Xforms library it used was at the time available in the COFF form only. And I haven't found how to build even purely COFF binaries on an ELF-ized system either. ALl this is a significant pain for everyone porting their software to FreeBSD and much stronger yet for those doing binary-only distributions. Maybe we should have an official policy of keeping the things compatible and available for as long as possible even if they are considered obsolete, unless carrying them on requires a major effort. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 20: 8: 2 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 A07A337B403; Thu, 18 Oct 2001 20:07:55 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f9J3Jfo06174; Thu, 18 Oct 2001 20:19:41 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200110190319.f9J3Jfo06174@mass.dis.org> To: babkin@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: FYI In-Reply-To: Message from Sergey Babkin of "Thu, 18 Oct 2001 22:50:35 EDT." <3BCF94FB.50F5D295@bellatlantic.net> Date: Thu, 18 Oct 2001 20:19:41 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Well, honestly, FreeBSD makes the life of the developers of third-party > binary-only drivers fairly difficult. It does? On the whole, actually, I'd say we do a pretty good job of making it easy. > The reason is that there > are a lot of API changes happening between the releases (take > Julian Elisher's recent problem for example). It's a poor example. Drivers don't involve themselves in the sysinit chain. > So the driver writers > are forced to at least recompile their drivers for each release. This isn't typically the case, actually. 4.x has in fact been very good in this regard. > Plus people are very active at ripping away the old APIs even > when there is no immediate need for that nor benefit from it (think > of phk's removal of the LIST-something macros). The removal of the LIST* macros doesn't affect the kernel interface (they're macros, not functions). > So often not > a simple recompilation but a noticeable rewrite may be required > for a driver between different versions of FreeBSD. I've been maintaining drivers for a while now, and frankly, I just don't see this. > That actually is true not only for the drivers but for the usual > binaries too. For example, there seems to be no way to combine > COFF and ELF libraries into one executable. Of course there isn't, and there'd be no point in it. > That made porting > of Lyx to 4.0 unfeasible, as the binary-only Xforms library it > used was at the time available in the COFF form only. And I haven't > found how to build even purely COFF binaries on an ELF-ized > system either. Use a cross-gcc setup. Of course, you mean a.out, but your error doesn't help your case much. > Maybe we should have an official policy of keeping the things > compatible and available for as long as possible even if they are > considered obsolete, unless carrying them on requires a major > effort. We do. And we do. Of course, this effort goes largely unnoticed and unthanked, since you're not going to comment on it unless you're personally inconvenienced by it. I've asked before, I'll ask again. Will folks please just let this die? You're producing a great deal of archive-filling material that's just not accurate or relevant, and your misinformation is harmful to the Project in a very real fashion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 18 23:48:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.kebne.se (mail.kebne.se [212.209.134.151]) by hub.freebsd.org (Postfix) with ESMTP id E106537B403; Thu, 18 Oct 2001 23:48:37 -0700 (PDT) Received: by mail.kebne.se with Internet Mail Service (5.5.2653.19) id ; Fri, 19 Oct 2001 08:48:40 +0200 Message-ID: <31A473DBB655D21180850008C71E251A031AB022@mail.kebne.se> From: Gunnar Olsson To: "Freebsd Hackers (E-mail)" , "Freebsd Net (E-mail)" Subject: TCP windowsize... Date: Fri, 19 Oct 2001 08:48:38 +0200 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Is there someone who can tell me how to set TCP windowsize? Best Regards, Gunnar ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Gunnar Olsson Phone: +46 8 5062 5762 Xelerated Packet Devices AB Fax: +46 8 5455 3211 Regeringsgatan 67 Mobile: +46 73 3279765 SE-10386 Stockholm Web: http://www.xelerated.com Email: mailto:gunnar.olsson@xelerated.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 0: 8:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.asplinux.ru (asplinux.ru [195.133.213.194]) by hub.freebsd.org (Postfix) with ESMTP id A925037B403; Fri, 19 Oct 2001 00:08:11 -0700 (PDT) Received: from home.com (sashkin.asplinux.ru [192.168.1.108]) by relay.asplinux.ru (8.11.6/8.11.6) with ESMTP id f9J789818806; Fri, 19 Oct 2001 11:08:10 +0400 Message-ID: <3BCFD1CB.10609@home.com> Date: Fri, 19 Oct 2001 11:10:03 +0400 From: Alex Levine Reply-To: sashkin@home.com User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.3) Gecko/20010829 X-Accept-Language: en-us MIME-Version: 1.0 To: John Baldwin , freebsd-hackers@FreeBSD.org Subject: Re: Possible bug in scheduler. References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: >On 18-Oct-01 Alexander Langer wrote: > >>Thus spake Alex Levine (sashkin@asplinux.ru): >> >>>resetpriority() calls maybe_resched() at the end after updating p_usrpri >>>based on changed p_estcpu. >>>maybe_resched() uses curpriority_cmp to compare priorities of current >>>and given process and this function ( curpriority_cmp ) uses p_priority >>>which is unchanged yet - the new p_usrpri is not reflected to p_priority >>>yet. >>> >>In -CURRENT, it's more obvious: >>maybe_resched() only rescheds, if the resetted process' priority >>level changes. >> >>Since resetpriority() doesn't modify the priority level but >>only the user priority, the call to maybe_resched() has no >>effect at all -- only some overhead for the comparisons >>(curproc will have had the higher or same priority level >>as the resetted process anyways, otherwise it hadn't been curproc :) >> >>So, either >> - p's priority level in resetpriority has to be re-calculted >> as well, or >> - the call to maybe_resched() can be removed w/o loss >> of functionality. >> > > >or c) in the preemptive kernel maybe_resched() doesn't exist as it's >functionality is more properly handled in other places. > I took another look in CURRENT. The same call to maybe_resched from reset_priority is as useless as in STABLE. Only there the recalculation relies on pri_level, which replaced p_priority as I understand but the thing which is being changed is usr_pri. So it's the same. Regards, Alex Levine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 0:26:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 7C70037B405 for ; Fri, 19 Oct 2001 00:26:31 -0700 (PDT) Received: from m5.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0109-Fujitsu Gateway) id QAA16086 for ; Fri, 19 Oct 2001 16:26:29 +0900 (JST) (envelope-from kaneshige.kenji@jp.fujitsu.com) Received: from sxodm.sxo.nm.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0110-Fujitsu Domain Master) id QAA22808 for ; Fri, 19 Oct 2001 16:26:29 +0900 (envelope-from kaneshige.kenji@jp.fujitsu.com) Received: from jp.fujitsu.com by sxodm.sxo.nm.fujitsu.co.jp (8.9.3/3.7W) id QAA16774; Fri, 19 Oct 2001 16:26:28 +0900 (JST) Message-ID: <3BCFD592.1090607@jp.fujitsu.com> Date: Fri, 19 Oct 2001 16:26:10 +0900 From: Kenji Kaneshige User-Agent: Mozilla/5.0 (Windows; U; Win98; ja-JP; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: ja MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: question about mmap() on FreeBSD3.3 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello I have a question about the behavior of mmap() in the kernel built without VM_STACK option. The platform is FreeBSD3.3. When the area allocated by mmap() overlaps the area between vm_maxsaddr and USRSTACK, accessing the overlapped area causes Segmentation Fault, although mmap() is returned successfully. Is this a bug or the intended behavior? Looking through the source code, what happens seems: When grow() is called by the page fault handler trap_pfault(), grow() failes to grow a user stack area because virtual address space has already been taken by mmap(). ----- Kenji Kaneshige kaneshige.kenji@jp.fujitsu.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 4:12:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 9BEC937B401; Fri, 19 Oct 2001 04:12:29 -0700 (PDT) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 15uXZj-000Ntm-0A; Fri, 19 Oct 2001 11:12:27 +0000 Received: from herring (herring [10.0.0.2]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f9JBBB786747; Fri, 19 Oct 2001 12:11:11 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 19 Oct 2001 12:11:11 +0100 (BST) From: Doug Rabson To: Dag-Erling Smorgrav Cc: John Baldwin , , , Gordon Tetlow Subject: Re: New rc.d init script roadmap In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18 Oct 2001, Dag-Erling Smorgrav wrote: > John Baldwin writes: > > Huh? Int on alpha is 32, and pointer is 64. > > I thought we were ILP64 on 64-bit archs, but you're right. And I > ought to know better... Fortunately (?) it doesn't matter in this case. Function arguments which are passed in registers are all promoted to 64bits. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 6:14:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mongrel.pacific.net.au (mongrel.pacific.net.au [61.8.0.107]) by hub.freebsd.org (Postfix) with ESMTP id 3F84B37B407 for ; Fri, 19 Oct 2001 06:14:28 -0700 (PDT) Received: from dungeon.home (ppp223.dyn249.pacific.net.au [203.143.249.223]) by mongrel.pacific.net.au (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id XAA21776; Fri, 19 Oct 2001 23:12:30 +1000 X-Authentication-Warning: mongrel.pacific.net.au: Host ppp223.dyn249.pacific.net.au [203.143.249.223] claimed to be dungeon.home Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.11.3/8.11.1) with ESMTP id f9JDFHS20600; Fri, 19 Oct 2001 23:15:17 +1000 (EST) (envelope-from mckay) Message-Id: <200110191315.f9JDFHS20600@dungeon.home> To: Matt Dillon Cc: hackers@freebsd.org, mckay@thehub.com.au Subject: vmiodirenable vs isofs, some proof Date: Fri, 19 Oct 2001 23:15:17 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG About a month ago I suggested that vfs.vmiodirenable=1 and the cd9660 file system interract badly. I have not got absolute proof, but I think fairly good evidence of a causal link. At work I have an Athlon 1.4GHz with 512MB ram, IDE disk, IDE burner running FreeBSD 4.4 (no special options). For the last few days, I have had vfs.vmiodirenable=1 without any non-CD related strangeness. I mounted a CD full of mp3s (about 600MB). I copied the contents to the IDE disk (using tar piped to tar). Other programs were active (linux opera, xmms, xterms, probably others), but I wasn't thrashing the box. Shortly after copying the files, I noticed that many files had the wrong contents. In particular, in most directories, the n'th file had the contents of the n'th file of the first directory. I verified that the mounted CD was in this peculiar state. Files read from the CD had the wrong contents. I copied the files several more times, and the particular file substitutions remained stable (ie the same files had the same wrong contents). I set vfs.vmiodirenable=0 and copied again. Exactly the same incorrect files. In other words, the corruption, whatever it is, was not magically removed by disabling vmiodirenable while the cache remained. I unmounted and remounted the CD. A copy operation was flawless at this point (vmiodirenable still off). I enabled vmiodirenable and the next copy was corrupt in the same manner (cross linked files), but the set of cross links was different than before. (Dang, I can't remember if I did another unmount/remount cycle before this copy. Oh well.) At this point, I noticed that the cross links were actual hard links in my HD copies. (I should have noticed how fast they were copying, I suppose). Using "ls -li" on the cdrom showed low inode numbers instead of the high numbers you would expect, and most directories contained the same set of low inode numbers. (Again I have erred. I've left my saved directory listings at work. The "bad" inums were < 1000 while normal inums are > 50000, at least on this CD.) Is this enough for you to form a theory? Any more experiments you think would be worthwhile? Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 7:47:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id F09F437B401 for ; Fri, 19 Oct 2001 07:47:46 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id JAA16527; Fri, 19 Oct 2001 09:47:25 -0500 Date: Fri, 19 Oct 2001 09:47:25 -0500 (EST) From: Doug Hass To: Tim Wiess Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FYI In-Reply-To: <20011018111556.J1415-100000@akira.ahaza.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Tim, Your license with SBS for the DDK would prevent you from posting your code. If you read through it, you'll find that it prohibits the release of any of their DDK code under any circumstances. You could release everything EXCEPT the API for the card that SBS provides and offer the rest in object-only format. Doug On Thu, 18 Oct 2001, Tim Wiess wrote: > > If anyone has an interest in adding support for the SBS WAN cards to > > FreeBSD, feel free to contact me. I'll be glad to help. > > I'm actually working on a driver for the SBS WANic 600 and 800 cards. > There is still a lot of work and testing to be done, but (assuming there > are no problems with the powers that be over here, and there are no > conflicts with our agreements with SBS) I do eventually plan on posting > the code (under a BSD license). > > I'll keep y'all posted. > > tim > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 8:24: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail46.sdc1.sfba.home.com (femail46.sdc1.sfba.home.com [24.254.60.40]) by hub.freebsd.org (Postfix) with ESMTP id 38F6F37B403 for ; Fri, 19 Oct 2001 08:23:57 -0700 (PDT) Received: from laptop.baldwin.cx ([24.2.39.156]) by femail46.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20011019152351.HILX2497.femail46.sdc1.sfba.home.com@laptop.baldwin.cx>; Fri, 19 Oct 2001 08:23:51 -0700 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: <3BCFD1CB.10609@home.com> Date: Fri, 19 Oct 2001 08:23:46 -0700 (PDT) From: John Baldwin To: Alex Levine Subject: Re: Possible bug in scheduler. Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 19-Oct-01 Alex Levine wrote: > John Baldwin wrote: > >>On 18-Oct-01 Alexander Langer wrote: >> >>>Thus spake Alex Levine (sashkin@asplinux.ru): >>> >>>>resetpriority() calls maybe_resched() at the end after updating p_usrpri >>>>based on changed p_estcpu. >>>>maybe_resched() uses curpriority_cmp to compare priorities of current >>>>and given process and this function ( curpriority_cmp ) uses p_priority >>>>which is unchanged yet - the new p_usrpri is not reflected to p_priority >>>>yet. >>>> >>>In -CURRENT, it's more obvious: >>>maybe_resched() only rescheds, if the resetted process' priority >>>level changes. >>> >>>Since resetpriority() doesn't modify the priority level but >>>only the user priority, the call to maybe_resched() has no >>>effect at all -- only some overhead for the comparisons >>>(curproc will have had the higher or same priority level >>>as the resetted process anyways, otherwise it hadn't been curproc :) >>> >>>So, either >>> - p's priority level in resetpriority has to be re-calculted >>> as well, or >>> - the call to maybe_resched() can be removed w/o loss >>> of functionality. >>> >> >> >>or c) in the preemptive kernel maybe_resched() doesn't exist as it's >>functionality is more properly handled in other places. >> > I took another look in CURRENT. The same call to maybe_resched from > reset_priority is as useless as in STABLE. Only there the recalculation > relies on pri_level, which replaced p_priority as I understand but the > thing which is being changed is usr_pri. So it's the same. Yes, but in the uncommitted (b/c it's not fully stable and I need to update the patches) preemptive kernel, it doesn't exist. :) So it will be fixed in -current by removing it in favor of something else. -- 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 Fri Oct 19 8:42:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail20.sdc1.sfba.home.com (femail20.sdc1.sfba.home.com [24.0.95.129]) by hub.freebsd.org (Postfix) with ESMTP id 54D9E37B405; Fri, 19 Oct 2001 08:42:40 -0700 (PDT) Received: from laptop.baldwin.cx ([24.2.39.156]) by femail20.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20011019154238.MCGM18047.femail20.sdc1.sfba.home.com@laptop.baldwin.cx>; Fri, 19 Oct 2001 08:42:38 -0700 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: Date: Fri, 19 Oct 2001 08:42:32 -0700 (PDT) From: John Baldwin To: Dag-Erling Smorgrav Subject: Re: New rc.d init script roadmap Cc: hackers@freebsd.org, arch@freebsd.org, Gordon Tetlow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Oct-01 Dag-Erling Smorgrav wrote: > Gordon Tetlow writes: >> Actually, fparseln() is defined in libutil.h (per the man page). I don't >> have my current box available (power outage at home), but if you could >> look over it, it should work. > > Ah, that's right - I couldn't find the right header, I should have > simply looked at the libutil Makefile. Thanks! Or the fparseln(3) manpage which lists the includes. :) -- 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 Fri Oct 19 9:19:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id C876137B407; Fri, 19 Oct 2001 09:19:37 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA74999; Fri, 19 Oct 2001 10:36:11 -0700 (PDT) Date: Fri, 19 Oct 2001 10:36:09 -0700 (PDT) From: Julian Elischer To: Mike Smith Cc: babkin@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: FYI In-Reply-To: <200110190319.f9J3Jfo06174@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 18 Oct 2001, Mike Smith wrote: > > Well, honestly, FreeBSD makes the life of the developers of third-party > > binary-only drivers fairly difficult. > > It does? On the whole, actually, I'd say we do a pretty good job of > making it easy. > > > The reason is that there > > are a lot of API changes happening between the releases (take > > Julian Elisher's recent problem for example). > > It's a poor example. Drivers don't involve themselves in the sysinit > chain. welllllll it gets involved.. if you redefine the SYSINIT values, old drivers's aren't 'notified' (should be a module but the supplier didn't make one..) > > > So the driver writers > > are forced to at least recompile their drivers for each release. > > This isn't typically the case, actually. 4.x has in fact been very > good in this regard. with the above exception, I agree. though in userland, the library changes have caused us some grief. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 9:57: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fortinbras.sanjose.wwwi.com (fortinbras.sanjose.wwwi.com [199.1.92.20]) by hub.freebsd.org (Postfix) with ESMTP id CB03937B405 for ; Fri, 19 Oct 2001 09:56:59 -0700 (PDT) Received: from polonius (dhcp105.houston.wwwi.com [199.1.94.105]) by fortinbras.sanjose.wwwi.com (8.10.2/8.10.2) with SMTP id f9JGupH25830; Fri, 19 Oct 2001 09:56:51 -0700 (PDT) From: "Jeffrey D. Wheelhouse" To: , "Jeffrey D. Wheelhouse" Cc: Subject: RE: Circular log patches for syslog Date: Fri, 19 Oct 2001 11:54:43 -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 V6.00.2600.0000 In-Reply-To: <20011019110440.A4344@pc04.ipc-kallmuenz.de> Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > -----Original Message----- > From: Peter Wullinger [mailto:wullinger@ipc-fabautomation.com] > Subject: Re: Circular log patches for syslog > > Just to spoil the thread: > > Shouldn't things like this be available as additional package, > so that the base system supplies only "bas(e)ic functionality > an everything else should be available as packages only? I would certainly be glad if these patches were incorporated into FreeBSD proper, just to eliminate the need to track future changes to syslogd and produce new (possibly buggy) patches. However, it is not clear that this feature is of wide enough usefulness to warrant that. Since it requires both a patch to an existing system utility and a new utility, it doesn't fit the package metaphor very well either. Hence, the patch and utility are available from my web page. I'm not sure I fully understand your concern, or the definition of "basic functionality" but I can certainly say that it would be tough for it to be more modular and optional than it is right now. :) From what I have learned, it is possible that this would be suited to .../src/release/picobsd/tinyware but even that seems premature right now. Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 10: 7:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from jim.go2net.com (jim.go2net.com [64.50.65.22]) by hub.freebsd.org (Postfix) with SMTP id F397837B403 for ; Fri, 19 Oct 2001 10:07:27 -0700 (PDT) Received: (qmail 28802 invoked from network); 19 Oct 2001 17:10:12 -0000 Received: from unknown (HELO absolut.go2net.com) (10.200.10.74) by jim.go2net.com with SMTP; 19 Oct 2001 17:10:11 -0000 Received: (qmail 8496 invoked from network); 19 Oct 2001 17:07:22 -0000 Received: from hunches.go2net.com (HELO infospace.com) (@[10.225.33.32]) (envelope-sender ) by absolut.go2net.com (qmail-ldap-1.03) with SMTP for ; 19 Oct 2001 17:07:22 -0000 Message-ID: <3BD05DCA.F8F4D8B3@infospace.com> Date: Fri, 19 Oct 2001 10:07:22 -0700 From: Yevgeniy Aleynikov Reply-To: eugene@infospace.com X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.17 i686) X-Accept-Language: ru, en MIME-Version: 1.0 To: Zhihui Zhang Cc: Matt Dillon , Peter Wemm , Ian Dowse , ache@FreeBSD.ORG, mckusick@mckusick.com, Ken Pizzini , hackers@FreeBSD.ORG Subject: Re: patch #3 (was Re: bleh. Re: ufs_rename panic) References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FYI: http://www.securityfocus.com/cgi-bin/archive.pl?id=1&mid=221337&start=2001-10-15&end=2001-10-21 (about how things done in Linux). Zhihui Zhang wrote: > (1) I am always wondering why not use a global rename lock so that there > is only one rename operation in progress at any time. This method is > used by GFS and probably Linux. This could make the code simply. Maybe > we can even get rid of the relookup() stuff. > > This may reduce concurrency, but rename should not be a frequent > operation. > -- Yevgeniy Aleynikov Infospace, Inc. SysAdmin, USE Work: (206)357-4594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 10:43:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D920837B401 for ; Fri, 19 Oct 2001 10:43:44 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9JHh8G47321; Fri, 19 Oct 2001 10:43:08 -0700 (PDT) (envelope-from dillon) Date: Fri, 19 Oct 2001 10:43:08 -0700 (PDT) From: Matthew Dillon Message-Id: <200110191743.f9JHh8G47321@apollo.backplane.com> To: Stephen McKay Cc: hackers@FreeBSD.ORG Subject: Re: vmiodirenable vs isofs, some proof References: <200110191315.f9JDFHS20600@dungeon.home> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -Matt Matthew Dillon :About a month ago I suggested that vfs.vmiodirenable=1 and the cd9660 :file system interract badly. I have not got absolute proof, but I :think fairly good evidence of a causal link. :... :I set vfs.vmiodirenable=0 and copied again. Exactly the same incorrect :files. In other words, the corruption, whatever it is, was not magically :removed by disabling vmiodirenable while the cache remained. Turning off vmiodirenable does not effect things that are already VMIO backed, so this is expected. :I unmounted and remounted the CD. A copy operation was flawless at this :point (vmiodirenable still off). : :I enabled vmiodirenable and the next copy was corrupt in the same manner :(cross linked files), but the set of cross links was different than before. :(Dang, I can't remember if I did another unmount/remount cycle before :this copy. Oh well.) : :At this point, I noticed that the cross links were actual hard links :in my HD copies. (I should have noticed how fast they were copying, I :suppose). :.. :Is this enough for you to form a theory? Any more experiments you :think would be worthwhile? : :Stephen. It sure looks like you can reproduce the bug at will, which is great! Now I need to reproduce it over here. If you could email me an ls -liaR of the CD with vmiodirenable turned off, and another ls -liaR of the CD with vmiodirenable turned on and the corruption present, I should be able to use that to burn a junk CD of my own to try to reproduce the bug. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 10:47:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbeast.ahaza.com (mailbeast.ahaza.com [209.180.221.132]) by hub.freebsd.org (Postfix) with ESMTP id 0294F37B401 for ; Fri, 19 Oct 2001 10:47:07 -0700 (PDT) Received: from akira.ahaza.com (akira.ahaza.com [172.16.30.230]) by mailbeast.ahaza.com (8.11.1/8.11.1) with ESMTP id f9JHkVb27294; Fri, 19 Oct 2001 10:46:35 -0700 (PDT) (envelope-from twiess@ahaza.com) Date: Fri, 19 Oct 2001 10:46:44 -0700 (PDT) From: Tim Wiess X-X-Sender: To: Doug Hass Cc: Subject: SBS WANic (was FYI) In-Reply-To: Message-ID: <20011019102658.F1342-100000@akira.ahaza.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I don't doubt that. As I mentioned, there are several factors that I need to check into, especially our agreements with SBS. tim On Fri, 19 Oct 2001, Doug Hass wrote: > Tim, > > Your license with SBS for the DDK would prevent you from posting your > code. If you read through it, you'll find that it prohibits the release > of any of their DDK code under any circumstances. You could release > everything EXCEPT the API for the card that SBS provides and offer the > rest in object-only format. > > Doug > > On Thu, 18 Oct 2001, Tim Wiess wrote: > > > > If anyone has an interest in adding support for the SBS WAN cards to > > > FreeBSD, feel free to contact me. I'll be glad to help. > > > > I'm actually working on a driver for the SBS WANic 600 and 800 cards. > > There is still a lot of work and testing to be done, but (assuming there > > are no problems with the powers that be over here, and there are no > > conflicts with our agreements with SBS) I do eventually plan on posting > > the code (under a BSD license). > > > > I'll keep y'all posted. > > > > tim > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 11:56: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id D6DC837B405; Fri, 19 Oct 2001 11:56:03 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f9JIthp37668; Fri, 19 Oct 2001 11:55:43 -0700 (PDT) (envelope-from obrien) Date: Fri, 19 Oct 2001 11:55:43 -0700 From: "David O'Brien" To: Dag-Erling Smorgrav Cc: Gordon Tetlow , arch@freebsd.org, hackers@freebsd.org Subject: Re: New rc.d init script roadmap Message-ID: <20011019115543.B37445@dragon.nuxi.com> Reply-To: arch@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Thu, Oct 18, 2001 at 09:47:53PM +0200 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Oct 18, 2001 at 09:47:53PM +0200, Dag-Erling Smorgrav wrote: > Dag-Erling Smorgrav writes: > > Your rcorder patch is incorrect. > > Here's a correct patch. Does anybody mind if I commit this and > connect rcorder(8) to the build? YES I MIND!! What part of "it is on the vendor branch for now" don't you understand? Stop picking at the trival fruit on the ground and instead help with the fruit in /etc/rc.d/. I really didn't think this thread was going to bikeshed, but I was very wrong. Lets work on an actual prototype (who cares if it is rough) so we have something that actually does *something*. If you don't like my patch, you are certainly free to post another one. -- -- David (obrien@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 Oct 19 12: 0:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 268AA37B44B; Fri, 19 Oct 2001 12:00:18 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f9JIxrm37715; Fri, 19 Oct 2001 11:59:53 -0700 (PDT) (envelope-from obrien) Date: Fri, 19 Oct 2001 11:59:53 -0700 From: "David O'Brien" To: Cyrille Lefevre Cc: Gordon Tetlow , arch@freebsd.org, hackers@freebsd.org, chris@freebsd.org, rwatson@freebsd.org, sheldonh@freebsd.org Subject: Re: New rc.d init script roadmap Message-ID: <20011019115953.D37445@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200110182129.f9ILTxH07817@gits.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200110182129.f9ILTxH07817@gits.dyndns.org>; from clefevre@citeweb.net on Thu, Oct 18, 2001 at 11:29:59PM +0200 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Oct 18, 2001 at 11:29:59PM +0200, Cyrille Lefevre wrote: > > I've prepared a status report about this project. the xml file in > attachment have to be reviewed since I've just put descriptions > from FreeBSD-rc's Yahoo! Group and your email message. WHY in the world are you sending in a "status" report about this? From this thread we are still flushing out details to the point there is nothing we can say. > first of all, there should be a consensus about the owner of > this project ? also, who create the FreeBSD-rc's Yahoo! Group ? We don't need a Yahoo! group. There is zero wrong with the archived FreeBSD mailing lists. They have worked for FreeBSD development for 8 years now. -- -- David (obrien@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 Oct 19 12:23:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id ED4E637B401; Fri, 19 Oct 2001 12:23:15 -0700 (PDT) Received: from onyx (onyx.cs.binghamton.edu [128.226.140.171]) by bingnet2.cc.binghamton.edu (8.11.6/8.11.6) with ESMTP id f9JJN8F23025; Fri, 19 Oct 2001 15:23:08 -0400 (EDT) Date: Fri, 19 Oct 2001 15:22:14 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@onyx To: eugene@infospace.com Cc: Matt Dillon , Peter Wemm , Ian Dowse , ache@FreeBSD.ORG, mckusick@mckusick.com, Ken Pizzini , hackers@FreeBSD.ORG Subject: Re: patch #3 (was Re: bleh. Re: ufs_rename panic) In-Reply-To: <3BD05DCA.F8F4D8B3@infospace.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks. I run the mklink.sh script on FreeBSD 4.3, it simply rejects by saying "head: l0: File name too long". So I guess it does not even reach the kernel yet. -Zhihui On Fri, 19 Oct 2001, Yevgeniy Aleynikov wrote: > > FYI: > > http://www.securityfocus.com/cgi-bin/archive.pl?id=1&mid=221337&start=2001-10-15&end=2001-10-21 > > (about how things done in Linux). > > > Zhihui Zhang wrote: > > > (1) I am always wondering why not use a global rename lock so that there > > is only one rename operation in progress at any time. This method is > > used by GFS and probably Linux. This could make the code simply. Maybe > > we can even get rid of the relookup() stuff. > > > > This may reduce concurrency, but rename should not be a frequent > > operation. > > > > -- > Yevgeniy Aleynikov > Infospace, Inc. > SysAdmin, USE > Work: (206)357-4594 > > 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 Oct 19 12:57:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.noos.fr (descartes.noos.net [212.198.2.74]) by hub.freebsd.org (Postfix) with ESMTP id 25AE137B40D for ; Fri, 19 Oct 2001 12:57:38 -0700 (PDT) Received: (qmail 28968505 invoked by uid 0); 19 Oct 2001 19:57:36 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.231.37]) (envelope-sender ) by 212.198.2.74 (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 19 Oct 2001 19:57:36 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.6/8.11.6) id f9JJvYW04832; Fri, 19 Oct 2001 21:57:34 +0200 (CEST) (envelope-from root) Message-Id: <200110191957.f9JJvYW04832@gits.dyndns.org> Subject: Re: New rc.d init script roadmap In-Reply-To: <20011019115953.D37445@dragon.nuxi.com> To: obrien@freebsd.org Date: Fri, 19 Oct 2001 21:57:33 +0200 (CEST) Cc: Gordon Tetlow , arch@freebsd.org, hackers@freebsd.org, chris@freebsd.org, rwatson@freebsd.org, sheldonh@freebsd.org Reply-To: clefevre@citeweb.net From: Cyrille Lefevre Organization: ACME X-Face: X-Mailer: ELM [version 2.4ME+ PL94c (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: > On Thu, Oct 18, 2001 at 11:29:59PM +0200, Cyrille Lefevre wrote: > > > > I've prepared a status report about this project. the xml file in > > attachment have to be reviewed since I've just put descriptions > > from FreeBSD-rc's Yahoo! Group and your email message. > > WHY in the world are you sending in a "status" report about this? to record this task as a real project and to avoid duplicates works... > >From this thread we are still flushing out details to the point there is > nothing we can say. > > > first of all, there should be a consensus about the owner of > > this project ? also, who create the FreeBSD-rc's Yahoo! Group ? > > We don't need a Yahoo! group. There is zero wrong with the archived > FreeBSD mailing lists. They have worked for FreeBSD development for 8 > years now. I'm just reporting this one exists as you report the existence of Kevin Way's work two days ago. of course, it would be better to have a -rc mailing list. Cyrille. -- Cyrille Lefevre mailto:clefevre@citeweb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 13:53:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by hub.freebsd.org (Postfix) with SMTP id 9314137B408 for ; Fri, 19 Oct 2001 13:53:26 -0700 (PDT) Received: from grubby.research.bell-labs.com ([135.104.2.9]) by dirty; Fri Oct 19 16:53:34 EDT 2001 Received: from aura.research.bell-labs.com (aura.research.bell-labs.com [135.104.46.10]) by grubby.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id f9JKqwk36409 for ; Fri, 19 Oct 2001 16:52:58 -0400 (EDT) Received: (from jkf@localhost) by aura.research.bell-labs.com (8.9.1/8.9.1) id QAA20502 for hackers@FreeBSD.org; Fri, 19 Oct 2001 16:52:58 -0400 (EDT) Date: Fri, 19 Oct 2001 16:52:58 -0400 (EDT) From: Jeff Fellin Message-Id: <200110192052.QAA20502@aura.research.bell-labs.com> To: hackers@FreeBSD.org Subject: system hung with runnable processes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I didn't see anything like this in the archives, so I'm sending this to the questions list and hackers list for assistance. I am running FreeBSD 4.3 on a L440GX+ motherboard with dual PCI buses: 32/33 and 32/66 dual Pentium III @ 700MHz with 256KB L2 cache. The system is running in Uniprocessor mode. Although running the tests on FreeBSD 4.1 has not caused the problem. My problem: I have an application that reads from a SCSI bus, and forwards the SCSI CDB's to another system over TCP. When running a large load the system gets SCSI bus device reset's that the application acknowledges and clears an error bit. After a period of time, in this example about 2.5 hours, the system stops processing any SCSI CDB's. In DDB the ps output show 11 runnable process, p_wchan == 0, and curproc points to one of the processes. However, when checking the run queues via gdb, none of the runnable processes is in a run queue. According to rtqueuebits, queuebits, and idqueuebits, only queue[12] has any runnable processes. Examing the proc structures for the runnable processes, their priority is 6, so they should be in queue[6]. I cannot determine anything obvious in the process scheduling code, but something is happening. I am attaching the system dmesg output from boot to taking the system dump, the ddb output on the serial console, and the output from gdb of the process' stack trace and proc structure. If anyone needs more information just ask and I'll try to get it for you. Does anyone believe upgrading to FreeBSD 4.4 would resolve the problem? ====================================== /var/run/dmesg output ===================================== Oct 15 11:15:54 nstg19 su: jkf to root on /dev/ttyp0 Oct 15 11:26:10 nstg19 su: fgu to root on /dev/ttyp1 Oct 15 11:38:54 nstg19 reboot: rebooted by fgu Oct 15 11:38:54 nstg19 syslogd: exiting on signal 15 Oct 15 11:40:55 nstg19 /kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Oct 15 11:40:55 nstg19 /kernel: Waiting (max 60 seconds) for system process `syncer' to stop...stopped Oct 15 11:40:55 nstg19 /kernel: Oct 15 11:40:55 nstg19 /kernel: syncing disks... Oct 15 11:40:55 nstg19 /kernel: done Oct 15 11:40:55 nstg19 /kernel: Uptime: 2d20h1m57s Oct 15 11:40:55 nstg19 /kernel: Rebooting... Oct 15 11:40:55 nstg19 /kernel: Copyright (c) 1992-2001 The FreeBSD Project. Oct 15 11:40:55 nstg19 /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Oct 15 11:40:55 nstg19 /kernel: The Regents of the University of California. All rights reserved. Oct 15 11:40:55 nstg19 /kernel: FreeBSD 4.3-RELEASE #0: Mon Oct 15 11:35:39 EDT 2001 Oct 15 11:40:55 nstg19 /kernel: fgu@nstg19.research.bell-labs.com:/usr/src/sys/compile/NSTG19.FGU.UP Oct 15 11:40:55 nstg19 /kernel: Timecounter "i8254" frequency 1193182 Hz Oct 15 11:40:55 nstg19 /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (999.53-MHz 686-class CPU) Oct 15 11:40:55 nstg19 /kernel: Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Oct 15 11:40:55 nstg19 /kernel: Features=0x383fbff Oct 15 11:40:55 nstg19 /kernel: real memory = 1073676288 (1048512K bytes) Oct 15 11:40:55 nstg19 /kernel: avail memory = 1040621568 (1016232K bytes) Oct 15 11:40:55 nstg19 /kernel: Preloaded elf kernel "kernel" at 0xc04ed000. Oct 15 11:40:55 nstg19 /kernel: Pentium Pro MTRR support enabled Oct 15 11:40:55 nstg19 /kernel: md0: Malloc disk Oct 15 11:40:55 nstg19 /kernel: npx0: on motherboard Oct 15 11:40:55 nstg19 /kernel: npx0: INT 16 interface Oct 15 11:40:55 nstg19 /kernel: pcib0: on motherboard Oct 15 11:40:55 nstg19 /kernel: pci0: on pcib0 Oct 15 11:40:55 nstg19 /kernel: nvram probe: type: 81166 Oct 15 11:40:55 nstg19 /kernel: nvram probe: type: 91166 Oct 15 11:40:55 nstg19 /kernel: pcib4: at device 0.1 on pci0 Oct 15 11:40:55 nstg19 /kernel: pci1: on pcib4 Oct 15 11:40:55 nstg19 /kernel: nvram probe: type: 474d1002 Oct 15 11:40:55 nstg19 /kernel: pci1: at 0.0 irq 11 Oct 15 11:40:55 nstg19 /kernel: nvram probe: type: 61166 Oct 15 11:40:55 nstg19 /kernel: nvram probe: type: 61166 Oct 15 11:40:55 nstg19 /kernel: nvram probe: type: 109005 Oct 15 11:40:55 nstg19 /kernel: ahc0: port 0xde00-0xdeff mem 0xfeafa000-0xfeafafff irq 11 at device 3.0 on pci0 Oct 15 11:40:55 nstg19 /kernel: aic7890/91: Wide Channel A, SCSI Id=7, 32/255 SCBs Oct 15 11:40:55 nstg19 /kernel: nvram probe: type: cf9005 Oct 15 11:40:55 nstg19 /kernel: ahc1: port 0xd000-0xd0ff mem 0xfeafb000-0xfeafbfff irq 5 at device 5.0 on pci0 Oct 15 11:40:55 nstg19 /kernel: aic7899: Wide Channel A, SCSI Id=7, 32/255 SCBs Oct 15 11:40:55 nstg19 /kernel: nvram probe: type: cf9005 Oct 15 11:40:55 nstg19 /kernel: ahc2: port 0xd800-0xd8ff mem 0xfeafe000-0xfeafefff irq 10 at device 5.1 on pci0 Oct 15 11:40:55 nstg19 /kernel: aic7899: Wide Channel B, SCSI Id=7, 32/255 SCBs Oct 15 11:40:55 nstg19 /kernel: fxp0: port 0xd400-0xd43f mem 0xfe900000-0xfe9fffff,0xfeaff000-0xfeafffff irq 9 at device 6.0 on pci0 Oct 15 11:40:55 nstg19 /kernel: fxp0: Ethernet address 00:30:48:10:7e:f3 Oct 15 11:40:55 nstg19 /kernel: nvram probe: type: 2001166 Oct 15 11:40:55 nstg19 /kernel: isab0: at device 15.0 on pci0 Oct 15 11:40:55 nstg19 /kernel: isa0: on isab0 Oct 15 11:40:55 nstg19 /kernel: nvram probe: type: 2111166 Oct 15 11:40:55 nstg19 /kernel: atapci0: port 0xffa0-0xffaf at device 15.1 on pci0 Oct 15 11:40:55 nstg19 /kernel: ata0: at 0x1f0 irq 14 on atapci0 Oct 15 11:40:55 nstg19 /kernel: ata1: at 0x170 irq 15 on atapci0 Oct 15 11:40:55 nstg19 /kernel: nvram probe: type: 2201166 Oct 15 11:40:55 nstg19 /kernel: ohci0: mem 0xfeafd000-0xfeafdfff irq 10 at device 15.2 on pci0 Oct 15 11:40:55 nstg19 /kernel: usb0: OHCI version 1.0, legacy support Oct 15 11:40:55 nstg19 /kernel: usb0: on ohci0 Oct 15 11:40:55 nstg19 /kernel: usb0: USB revision 1.0 Oct 15 11:40:55 nstg19 /kernel: uhub0: (unknown) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Oct 15 11:40:55 nstg19 /kernel: uhub0: 4 ports with 4 removable, self powered Oct 15 11:40:55 nstg19 /kernel: pcib1: on motherboard Oct 15 11:40:55 nstg19 /kernel: pci2: on pcib1 Oct 15 11:40:55 nstg19 /kernel: ti0: mem 0xfebf8000-0xfebfbfff irq 11 at device 1.0 on pci2 Oct 15 11:40:55 nstg19 /kernel: ti0: Ethernet address: 00:02:e3:00:19:1c Oct 15 11:40:55 nstg19 /kernel: nvram probe: type: 54151332 Oct 15 11:40:55 nstg19 /kernel: nvram0: mem 0xe0000000-0xefffffff,0xfebffc00-0xfebffc7f irq 11 at device 2.0 on pci2 Oct 15 11:40:55 nstg19 /kernel: nvram_attach: bus 2 slot 2 unit 0 Oct 15 11:40:55 nstg19 /kernel: nvram_attach: cmdmap 0xfebffc00 memmap: 0xe0000008 Oct 15 11:40:55 nstg19 /kernel: nvram_attach: regs 0xdb566c00 pregs: 0xfebffc00 Oct 15 11:40:55 nstg19 /kernel: nvram_attach: nvram 0xdb567000 pnvram: 0xe0000000 Oct 15 11:40:55 nstg19 /kernel: nvram0: Rev-E Oct 15 11:40:55 nstg19 /kernel: nvram0: conf regs Oct 15 11:40:55 nstg19 /kernel: 0x00: 0x54151332 0x04: 0x4000117 0x08: 0xff000005, 0x0c: 0x4008 Oct 15 11:40:55 nstg19 /kernel: 0x10: 0xfebffc00 0x14: 0xe0000008 0x18: 0, 0x1c: 0 Oct 15 11:40:55 nstg19 /kernel: 0x20: 0 0x24: 0 0x28: 0, 0x2c: 0 Oct 15 11:40:55 nstg19 /kernel: 0x30: 0xfebfe000 0x34: 0 0x38: 0, 0x3c: 0x10b Oct 15 11:40:55 nstg19 /kernel: 0x40: 0 0x44: 0 0x48: 0, 0x4c: 0 Oct 15 11:40:55 nstg19 /kernel: nvram0 cmd reg: 0x117 Oct 15 11:40:55 nstg19 /kernel: nvram0: memreg: 0xe0000008, 0xf0000000 memsize: 0x10000000 Oct 15 11:40:55 nstg19 /kernel: nvram0: regs 59, 73ab10, 0, deadbeef Oct 15 11:40:55 nstg19 /kernel: nvram:0 Battery Status(0): 1-good 2-good 3-good 4-good Oct 15 11:40:55 nstg19 /kernel: nvram0 CMOS: 39 Oct 15 11:40:55 nstg19 /kernel: nvram0 mem ctrl: 0 Oct 15 11:40:55 nstg19 /kernel: nvram0 Initialized Oct 15 11:40:55 nstg19 /kernel: nvram0 CMOS: 39 Oct 15 11:40:55 nstg19 /kernel: nvram0 mem ctrl: 0 Oct 15 11:40:56 nstg19 /kernel: pcib2: on motherboard Oct 15 11:40:56 nstg19 /kernel: pci3: on pcib2 Oct 15 11:40:56 nstg19 /kernel: pcib3: on motherboard Oct 15 11:40:56 nstg19 /kernel: pci4: on pcib3 Oct 15 11:40:56 nstg19 /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Oct 15 11:40:56 nstg19 /kernel: fdc0: FIFO enabled, 8 bytes threshold Oct 15 11:40:56 nstg19 /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Oct 15 11:40:56 nstg19 /kernel: atkbdc0: at port 0x60,0x64 on isa0 Oct 15 11:40:56 nstg19 /kernel: atkbd0: flags 0x1 irq 1 on atkbdc0 Oct 15 11:40:56 nstg19 /kernel: kbd0 at atkbd0 Oct 15 11:40:56 nstg19 /kernel: psm0: irq 12 on atkbdc0 Oct 15 11:40:56 nstg19 /kernel: psm0: model IntelliMouse, device ID 3 Oct 15 11:40:56 nstg19 /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Oct 15 11:40:56 nstg19 /kernel: sc0: at flags 0x100 on isa0 Oct 15 11:40:56 nstg19 /kernel: sc0: VGA <16 virtual consoles, flags=0x100> Oct 15 11:40:56 nstg19 /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Oct 15 11:40:56 nstg19 /kernel: sio0: type 16550A, console Oct 15 11:40:56 nstg19 /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Oct 15 11:40:56 nstg19 /kernel: sio1: type 16550A Oct 15 11:40:56 nstg19 /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 Oct 15 11:40:56 nstg19 /kernel: ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode Oct 15 11:40:56 nstg19 /kernel: ppc0: FIFO with 16/16/8 bytes threshold Oct 15 11:40:56 nstg19 /kernel: plip0: on ppbus0 Oct 15 11:40:56 nstg19 /kernel: lpt0: on ppbus0 Oct 15 11:40:56 nstg19 /kernel: lpt0: Interrupt-driven port Oct 15 11:40:56 nstg19 /kernel: ppi0: on ppbus0 Oct 15 11:40:56 nstg19 /kernel: acd0: CDROM at ata0-master using PIO4 Oct 15 11:40:56 nstg19 /kernel: xpt_config: xpt_create_path() failed for debug target 9:5:0, debugging disabled Oct 15 11:40:56 nstg19 /kernel: Waiting 5 seconds for SCSI devices to settle Oct 15 11:40:56 nstg19 /kernel: (targbh0:ahc0:0:-1:-1): Lun now enabled for target mode Oct 15 11:40:56 nstg19 /kernel: (targbh1:ahc2:0:-1:-1): Lun now enabled for target mode Oct 15 11:40:56 nstg19 /kernel: pass1 at ahc1 bus 0 target 6 lun 0 Oct 15 11:40:56 nstg19 /kernel: pass1: Fixed Processor SCSI-2 device Oct 15 11:40:56 nstg19 /kernel: pass1: 3.300MB/s transfers Oct 15 11:40:56 nstg19 /kernel: da0 at ahc1 bus 0 target 0 lun 0 Oct 15 11:40:56 nstg19 /kernel: da0: Fixed Direct Access SCSI-3 device Oct 15 11:40:56 nstg19 /kernel: da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled Oct 15 11:40:56 nstg19 /kernel: da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) Oct 15 11:40:56 nstg19 /kernel: Mounting root from ufs:/dev/da0s1a Oct 15 11:40:56 nstg19 savecore: no core dump Oct 15 11:40:56 nstg19 ntpd[195]: ntpd 4.0.99b Sat Apr 21 08:31:35 GMT 2001 (1) Oct 15 11:40:56 nstg19 ntpd[195]: using kernel phase-lock loop 2040 Oct 15 11:40:56 nstg19 ntpd[195]: using kernel phase-lock loop 2041 Oct 15 11:40:57 nstg19 /kernel: ti0: gigabit link up Oct 15 11:40:57 nstg19 lpd[248]: lpd startup: logging=0 Oct 15 11:45:32 nstg19 ntpd[195]: time reset 0.188260 s Oct 15 11:45:32 nstg19 ntpd[195]: kernel pll status change 2041 Oct 15 11:49:25 nstg19 /kernel: Configuring Target Mode Oct 15 11:49:25 nstg19 /kernel: (targda0:ahc0:0:0:0): Lun now enabled for target mode Oct 15 14:11:32 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:32 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:32 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:32 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:32 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:32 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:32 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:32 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:32 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:32 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:32 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:32 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:32 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:32 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:32 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:32 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:32 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:32 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:32 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:32 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:32 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:32 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:32 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:32 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:32 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:32 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:32 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:32 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:32 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:32 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:32 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:32 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:32 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:32 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:32 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:32 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:32 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:32 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:33 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:33 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:33 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:33 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:33 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:33 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:33 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:33 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:33 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:33 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:33 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:33 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:33 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:33 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:33 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:33 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:33 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:33 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:33 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:33 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:33 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:33 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:33 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:33 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:33 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:33 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:33 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:33 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:33 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:33 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:33 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:33 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:33 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:33 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:33 nstg19 /kernel: ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted Oct 15 14:11:33 nstg19 /kernel: targda INOT error 76 sense 0 arg c Oct 15 14:11:33 nstg19 /kernel: ahc0: Unexpected busfree while idle Oct 15 14:11:33 nstg19 /kernel: SEQADDR == 0x1 Oct 15 14:11:33 nstg19 /kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Oct 15 14:11:33 nstg19 /kernel: Waiting (max 60 seconds) for system process `syncer' to stop... Oct 15 14:14:12 nstg19 /kernel: stopped Oct 15 14:14:12 nstg19 /kernel: Oct 15 14:14:12 nstg19 /kernel: syncing disks... 15 14 Oct 15 14:14:12 nstg19 /kernel: done Oct 15 14:14:12 nstg19 /kernel: pid 9944 (lhe), uid 47053: exited on signal 11 Oct 15 14:14:12 nstg19 /kernel: pid 10301 (lhe), uid 47053: exited on signal 11 Oct 15 14:14:12 nstg19 /kernel: pid 11751 (lhe), uid 47053: exited on signal 11 Oct 15 14:14:12 nstg19 /kernel: pid 188 (syslogd), uid 0: exited on signal 11 Oct 15 14:14:12 nstg19 /kernel: Uptime: 2h30m49s Oct 15 14:14:12 nstg19 /kernel: Oct 15 14:14:12 nstg19 /kernel: dumping to dev #da/0x20001, offset 128 Oct 15 14:14:12 nstg19 /kernel: dump 1023 1022 1021 1020 1019 1018 1017 1016 1015 1014 1013 1012 1011 1010 1009 1008 1007 1006 1005 1004 1003 1002 1001 1000 999 998 997 996 995 994 993 992 991 990 989 988 987 986 985 984 983 982 981 980 979 978 977 976 975 974 973 972 971 970 969 968 967 966 965 964 963 962 961 960 959 958 957 956 955 954 953 952 951 950 949 948 947 946 945 944 943 942 941 940 939 938 937 936 935 934 933 932 931 930 929 928 927 926 925 924 923 922 921 920 919 918 917 916 915 914 913 912 911 910 909 908 907 906 905 904 903 902 901 900 899 898 897 896 895 894 893 892 891 890 889 888 887 886 885 884 883 882 881 880 879 878 877 876 875 874 873 872 871 870 869 868 867 866 865 864 863 862 861 860 859 858 857 856 855 854 853 852 851 850 849 848 847 846 845 844 843 842 841 840 839 838 837 836 835 834 833 832 831 830 829 828 827 826 825 824 823 822 821 820 819 818 817 816 815 814 813 812 811 810 809 808 807 806 805 804 803 802 801 800 799 798 797 796 795 794 793 792 791 790 789 788 787 786 785 784 783 782 781 780 779 778 77 Oct 15 14:14:12 nstg19 /kernel: 5 774 773 772 771 770 769 768 767 766 765 764 763 762 761 760 759 758 757 756 755 754 753 752 751 750 749 748 747 746 745 744 743 742 741 740 739 738 737 736 735 734 733 732 731 730 729 728 727 726 725 724 723 722 721 720 719 718 717 716 715 714 713 712 711 710 709 708 707 706 705 704 703 702 701 700 699 698 697 696 695 694 693 692 691 690 689 688 687 686 685 684 683 682 681 680 679 678 677 676 675 674 673 672 671 670 669 668 667 666 665 664 663 662 661 660 659 658 657 656 655 654 653 652 651 650 649 648 647 646 645 644 643 642 641 640 639 638 637 636 635 634 633 632 631 630 629 628 627 626 625 624 623 622 621 620 619 618 617 616 615 614 613 612 611 610 609 608 607 606 605 604 603 602 601 600 599 598 597 596 595 594 593 592 591 590 589 588 587 586 585 584 583 582 581 580 579 578 577 576 575 574 573 572 571 570 569 568 567 566 565 564 563 562 561 560 559 558 557 556 555 554 553 552 551 550 549 548 547 546 545 544 543 542 541 540 539 538 537 536 535 534 533 532 531 530 529 528 527 526 525 524 523 522 5 Oct 15 14:14:12 nstg19 /kernel: 19 518 517 516 515 514 513 512 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 Oct 15 14:14:12 nstg19 /kernel: 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 succeeded Oct 15 14:14:12 nstg19 /kernel: Automatic reboot in 15 seconds - press a key on the console to abort Oct 15 14:14:12 nstg19 /kernel: Rebooting... ===================================== ddb output on serial console ===================================== Configuring Target Mode (targda0:ahc0:0:0:0): Lun now enabled for target mode ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 ahc0: Bus Device Reset Received on A:7. 0 SCBs aborted targda INOT error 76 sense 0 arg c ahc0: Unexpected busfree while idle SEQADDR == 0x1 Debugger("manual escape to debugger") Stopped at Debugger+0x34: movb $0,in_Debugger.396 db> tr  where No such command db> trace Debugger(c03ec6a9) at Debugger+0x34 scgetc(c3e9e800,2,c3e97000,c04674c0,c3e97000) at scgetc+0x38e sckbdevent(c04674c0,0,c3e9e800,c3e97000,c3e97000) at sckbdevent+0x1b9 atkbd_intr(c04674c0,0,f1ad4e74,c0321c4f,c04674c0) at atkbd_intr+0x22 atkbd_isa_intr(c04674c0,660b00,10,f1ad0010,c0330010) at atkbd_isa_intr+0x18 Xresume1() at Xresume1+0x2b --- interrupt, eip = 0xc0294491, esp = 0xf1ad4e54, ebp = 0xf1ad4e74 --- ti_rxeof(c3e97000,c3e92e20,400900,f1ad4ea0,c033bee5) at ti_rxeof+0x2bd ti_intr(c3e97000,660a00,0,c0344e20,f1ad4f5c) at ti_intr+0x28 intr_mux(c2057160,400100,400010,c3e90010,10) at intr_mux+0x1d Xresume11() at Xresume11+0x2b --- interrupt, eip = 0xc0334024, esp = 0xf1ad4ee8, ebp = 0xf1ad4f5c --- rtcintr(0,c3e90010,f1ad0010,c0320010,0) at rtcintr doreti_swi() at doreti_swi+0xf db> ps pid proc addr uid ppid pgrp flag stat wmesg wchan cmd 1982 ecbb15e0 f1a14000 0 1 1 004084 3 nanslp c04561c0 perl 11751 f1aa5260 f1ba7000 47053 9366 9365 000086 3 nanslp c04561c0 lhe 11750 f1aa5400 f1ba5000 47053 9366 9365 000086 3 nanslp c04561c0 lhe 11749 f1aa55a0 f1ba3000 47053 9366 9365 000086 2 lhe 11748 f1aa5740 f1ba0000 47053 9366 9365 000086 2 lhe 10301 f1aa58e0 f1b9e000 47053 9366 9365 000086 3 nanslp c04561c0 lhe 10300 f1aa65e0 f1ad6000 47053 9366 9365 000086 3 nanslp c04561c0 lhe 10299 f1aa6100 f1af1000 47053 9366 9365 000086 2 lhe 10298 f1aa62a0 f1ae1000 47053 9366 9365 000086 2 lhe 9944 f1aa5c20 f1b24000 47053 9366 9365 000086 3 nanslp c04561c0 lhe 9943 f1aa6440 f1ada000 47053 9366 9365 000086 3 nanslp c04561c0 lhe 9942 f1aa5a80 f1b51000 47053 9366 9365 000086 2 lhe 9941 f1aa5dc0 f1b20000 47053 9366 9365 000086 2 lhe 9369 f1aa5f60 f1af4000 47053 9366 9365 000086 3 nanslp c04561c0 lhe 9368 f1aa6780 f1ad3000 47053 9366 9365 000006 2 lhe 9367 f1aa6920 f1ac1000 47053 9366 9365 2000086 3 pause c40d0000 lhe 9366 f1aa6ac0 f1abe000 47053 9365 9365 000086 3 poll c046fc54 lhe 9365 f1aa6c60 f1aae000 47053 1438 9365 005086 2 lhe 1438 f1aa6e00 f1aa8000 47053 1437 1438 004086 3 ttyin c205c030 sh 1437 ecbadea0 f1a9e000 0 243 1437 004084 3 select c046fc54 rlogind 308 ecbae040 f1a94000 0 1 1 004084 3 siodcd c4061c00 getty 307 ecbae1e0 f1a91000 0 1 307 004086 2 getty 306 ecbae380 f1a8e000 0 1 306 004086 3 ttyin c4063210 getty 305 ecbae520 f1a8b000 0 1 305 004086 3 ttyin c4060210 getty 304 ecbae6c0 f1a88000 0 1 304 004086 3 ttyin c4060310 getty 303 ecbae860 f1a85000 0 1 303 004086 3 ttyin c4060410 getty 302 ecbaeba0 f1a7e000 0 1 302 004086 3 ttyin c4061110 getty 301 ecbaea00 f1a82000 0 1 301 004086 3 ttyin c4082310 getty 300 ecbaed40 f1a7b000 0 1 300 004086 3 ttyin c4082610 getty 298 ecbb0c20 f1a32000 0 1 298 004086 2 getty 293 ecbb1440 f1a17000 65534 1 6 004186 3 nanslp c04561c0 rmonitor 254 ecbaeee0 f1a72000 0 1 254 000084 3 select c046fc54 usbd 251 ecbaf080 f1a6f000 0 1 251 000184 3 select c046fc54 sendmail 248 ecbaf220 f1a6b000 0 1 248 000084 3 select c046fc54 lpd 245 ecbaf3c0 f1a68000 0 1 245 000084 3 nanslp c04561c0 cron 243 ecbaf560 f1a61000 0 1 243 000084 3 select c046fc54 inetd 228 ecbafd80 f1a4f000 0 1 228 000084 3 select c046fc54 amd 223 ecbaf700 f1a5b000 0 1 218 000084 3 nfsidl c047460c nfsiod 222 ecbaf8a0 f1a58000 0 1 218 000084 3 nfsidl c0474608 nfsiod 221 ecbafa40 f1a55000 0 1 218 000084 3 nfsidl c0474604 nfsiod 220 ecbafbe0 f1a52000 0 1 218 000084 3 nfsidl c0474600 nfsiod 216 ecbaff20 f1a4c000 0 1 216 000084 3 select c046fc54 rpc.statd 213 ecbb00c0 f1a48000 0 208 208 000084 3 nfsd c3fbec00 nfsd 212 ecbb0260 f1a45000 0 208 208 000084 3 nfsd c3fb0a00 nfsd 211 ecbb0400 f1a42000 0 208 208 000084 3 nfsd c3f9f400 nfsd 210 ecbb05a0 f1a3e000 0 208 208 000084 3 nfsd c3fbea00 nfsd 208 ecbb0740 f1a3b000 0 1 208 000084 3 accept ebb691b6 nfsd 206 ecbb08e0 f1a38000 0 1 206 000084 3 select c046fc54 mountd 200 ecbb0a80 f1a35000 0 1 200 000084 3 select c046fc54 ypbind 197 ecbb0dc0 f1a2f000 1 1 197 000184 2 portmap 195 ecbb0f60 f1a2c000 0 1 195 000084 3 select c046fc54 ntpd 188 ecbb1100 f1a22000 0 1 188 000084 3 select c046fc54 syslogd 159 ecbb12a0 f1a1e000 0 1 159 000084 3 select c046fc54 dhclient 5 ecbb1780 ecbbe000 0 0 0 000204 3 syncer c046fbe8 syncer 4 ecbb1920 ecbbc000 0 0 0 100204 3 psleep c0456340 bufdaemon 3 ecbb1ac0 ecbba000 0 0 0 000204 3 psleep c04653e0 vmdaemon 2 ecbb1c60 ecbb8000 0 0 0 100204 3 psleep c0440f78 pagedaemon 1 ecbb1e00 ecbb6000 0 0 1 004284 3 wait ecbb1e00 init 0 c046efc0 c050d000 0 0 0 000204 3 sched c046efc0 swapper db> call boot(0x100) Waiting (max 60 seconds) for system process `bufdaemon' to stop... FreeBSD/i386 s(nstg19.researcht.bell-labs.com) o(ttyd0) logpin: ped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... 15 14 done Uptime: 2h30m49s dumping to dev #da/0x20001, offset 128 ===================================== process information from gdb ===================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 14:27:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (okc-65-31-203-60.mmcable.com [65.31.203.60]) by hub.freebsd.org (Postfix) with SMTP id 11AD337B407 for ; Fri, 19 Oct 2001 14:27:15 -0700 (PDT) Received: (qmail 8492 invoked by uid 100); 19 Oct 2001 21:27:05 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15312.39593.445092.171109@guru.mired.org> Date: Fri, 19 Oct 2001 16:27:05 -0500 To: "Jeffrey D. Wheelhouse" Cc: , Subject: RE: Circular log patches for syslog In-Reply-To: References: <20011019110440.A4344@pc04.ipc-kallmuenz.de> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jeffrey D. Wheelhouse types: > > -----Original Message----- > > From: Peter Wullinger [mailto:wullinger@ipc-fabautomation.com] > > Subject: Re: Circular log patches for syslog > > > > Just to spoil the thread: > > > > Shouldn't things like this be available as additional package, > > so that the base system supplies only "bas(e)ic functionality > > an everything else should be available as packages only? > > I would certainly be glad if these patches were incorporated into FreeBSD > proper, just to eliminate the need to track future changes to syslogd and > produce new (possibly buggy) patches. However, it is not clear that this > feature is of wide enough usefulness to warrant that. > > Since it requires both a patch to an existing system utility and a new > utility, it doesn't fit the package metaphor very well either. I almost commented on this one earlier - there's a utility in ports called "flog" which I use to avoid your general problem - that of running out of space on the logging device. It's not as nice a solution as you've got, though, so I skipped it. However, there are lots of system utilities that have replacements in the ports tree. In particular, there are at least two syslog daemons, one of which - msyslog - supports modules for input and output processing. Possibly this functionality could be done as an output module for msyslog, and that bundled as a port. Or even given back to the msyslog project. http://www.mired.org/home/mwm/ Q: How do you make the gods laugh? A: Tell them your plans. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 16: 5:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from inje.iskon.hr (inje.iskon.hr [213.191.128.16]) by hub.freebsd.org (Postfix) with ESMTP id DEA9537B407; Fri, 19 Oct 2001 16:05:49 -0700 (PDT) Received: from tel.fer.hr (zg06-115.dialin.iskon.hr [213.191.148.116]) by mail.iskon.hr (8.11.4/8.11.4/Iskon 8.11.3-1) with ESMTP id f9JN5fR16234; Sat, 20 Oct 2001 01:05:43 +0200 (MEST) Message-ID: <3BD0B1D4.CFC32A4D@tel.fer.hr> Date: Sat, 20 Oct 2001 01:05:56 +0200 From: Marko Zec X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Cc: freebsd-net@freebsd.org Subject: fxp driver - receive interrupt bundling Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On http://fly.cc.fer.hr/~zec/index.html you can find a 4.4-RELEASE fxp driver source, with patches that incorporate receive interrupt bundling microcode, borrowed from the Intel's Linux e100 driver. Bundling interrupts for a couple of received Ethernet frames can significantly lower interrupt processing overhead, so if you have a really busy server or router or whatever this code can make a noticeable difference. On an 1200 MHz Athlon machine, the microcode saves around 10% of CPU utilization, with incoming traffic of 20k pps on a single interface. The code is tested on 82558 rev B0 hardware, I'd be glad to know how it works on other versions of Intel's fxp cards. Pls. send your comments, suggestions etc. to zec@tel.fer.hr Have fun! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 16:24:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 0B51537B403; Fri, 19 Oct 2001 16:24:32 -0700 (PDT) Received: from hades.hell.gr (patr530-a161.otenet.gr [212.205.215.161]) by mailsrv.otenet.gr (8.11.5/8.11.5) with ESMTP id f9JNOOO21556; Sat, 20 Oct 2001 02:24:24 +0300 (EEST) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id f9JNOPU26790; Sat, 20 Oct 2001 02:24:25 +0300 (EEST) (envelope-from charon@labs.gr) Date: Sat, 20 Oct 2001 02:24:24 +0300 From: Giorgos Keramidas To: Cyrille Lefevre Cc: arch@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: New rc.d init script roadmap Message-ID: <20011020022424.C26569@hades.hell.gr> References: <20011019115953.D37445@dragon.nuxi.com> <200110191957.f9JJvYW04832@gits.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200110191957.f9JJvYW04832@gits.dyndns.org> User-Agent: Mutt/1.3.22.1i X-GPG-Fingerprint: C1EB 0653 DB8B A557 3829 00F9 D60F 941A 3186 03B6 X-URL: http://labs.gr/~charon/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Cyrille Lefevre wrote: > > I'm just reporting this one exists as you report the existence of > Kevin Way's work two days ago. of course, it would be better to > have a -rc mailing list. Not really. One more list to follow, when threads in existing lists will probably be enough for this. We don't have one mailing list for every port category, or for every different part of contrib/. It's overkill to create a list for something like this IMHO :/ -giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 17:16:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id E3EEF37B401; Fri, 19 Oct 2001 17:16:17 -0700 (PDT) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id f9K0EFq89356; Fri, 19 Oct 2001 17:14:15 -0700 (PDT) (envelope-from dg) Date: Fri, 19 Oct 2001 17:14:15 -0700 From: David Greenman To: Marko Zec Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: fxp driver - receive interrupt bundling Message-ID: <20011019171415.B48897@nexus.root.com> References: <3BD0B1D4.CFC32A4D@tel.fer.hr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BD0B1D4.CFC32A4D@tel.fer.hr>; from zec@tel.fer.hr on Sat, Oct 20, 2001 at 01:05:56AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >On http://fly.cc.fer.hr/~zec/index.html you can find a 4.4-RELEASE fxp >driver source, with patches that incorporate receive interrupt bundling >microcode, borrowed from the Intel's Linux e100 driver. > >Bundling interrupts for a couple of received Ethernet frames can >significantly lower interrupt processing overhead, so if you have a >really busy server or router or whatever this code can make a noticeable >difference. On an 1200 MHz Athlon machine, the microcode saves around >10% of CPU utilization, with incoming traffic of 20k pps on a single >interface. > >The code is tested on 82558 rev B0 hardware, I'd be glad to know how it >works on other versions of Intel's fxp cards. > >Pls. send your comments, suggestions etc. to zec@tel.fer.hr > >Have fun! Nifty! -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 19:28:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mw2.texas.net (mw2.texas.net [206.127.30.12]) by hub.freebsd.org (Postfix) with ESMTP id 9791837B401; Fri, 19 Oct 2001 19:28:14 -0700 (PDT) Received: from staff3.texas.net (staff3.texas.net [207.207.0.40]) by mw2.texas.net (8.11.6/8.11.6) with ESMTP id f9K2SDx03732; Fri, 19 Oct 2001 21:28:13 -0500 (CDT) Received: (from doug@localhost) by staff3.texas.net (8.11.6/8.11.6) id f9K2SDj00604; Fri, 19 Oct 2001 21:28:13 -0500 (CDT) (envelope-from doug) Date: Fri, 19 Oct 2001 21:28:08 -0500 From: Doug Swarin To: Matt Dillon Cc: hackers@FreeBSD.ORG, tmoestl@gmx.net, bp@FreeBSD.ORG Subject: Re: more on Re: Please review: bugfix for vinvalbuf() Message-ID: <20011019212807.A538@staff.texas.net> References: <20010711003926.B8799@crow.dom2ip.de> <200107110643.f6B6hTB24707@earth.backplane.com> <20010926204333.A15865@staff.texas.net> <200109281747.f8SHlUP29063@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: <200109281747.f8SHlUP29063@earth.backplane.com>; from dillon@earth.backplane.com on Fri, Sep 28, 2001 at 10:47:30AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Unfortunately, the recent patch to vinvalbuf() hasn't solved all of our problems. We had another, different panic today. The process that caused it was a 'tail' of a growing logfile over NFS. I have actually had this problem before, with FreeBSD 3.4, and reported it then. I believed this PR to be relevant at the time, however, I do not believe this client was writing to the file. [1998/06/23] kern/7028 http://www.freebsd.org/cgi/query-pr.cgi?pr=7028 panic in vinvalbuf when appending/looking at tail of NFS file The system is running 4.4-RELEASE with the vinvalbuf() patch. Debugging information is below. If I can provide any additional information, let me know. Thanks for any help, Doug -- panic message -- SMP 2 cpus IdlePTD 3555328 initial pcb at 2cf300 panicstr: vinvalbuf: flush failed panic messages: --- panic: vinvalbuf: flush failed mp_lock = 01000001; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 syncing disks... 8 done Uptime: 19d20h13m23s -- gdb session -- (kgdb) back #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:473 #1 0xc016cf8f in boot (howto=0x100) at /usr/src/sys/kern/kern_shutdown.c:313 #2 0xc016d3a9 in panic (fmt=0xc028745a "vinvalbuf: flush failed") at /usr/src/sys/kern/kern_shutdown.c:581 #3 0xc019a719 in vinvalbuf (vp=0xd7dde8c0, flags=0x1, cred=0xc2c60780, p=0xd79a0680, slpflag=0x100, slptimeo=0x0) at /usr/src/sys/kern/vfs_subr.c:753 #4 0xc01d0b30 in nfs_vinvalbuf (vp=0xd7dde8c0, flags=0x1, cred=0xc2c60780, p=0xd79a0680, intrflg=0x1) at /usr/src/sys/nfs/nfs_bio.c:1190 #5 0xc01cf668 in nfs_bioread (vp=0xd7dde8c0, uio=0xd7a42ed4, ioflag=0x7f0000, cred=0xc2c60780) at /usr/src/sys/nfs/nfs_bio.c:401 #6 0xc01f68d2 in nfs_read (ap=0xd7a42e64) at /usr/src/sys/nfs/nfs_vnops.c:1008 #7 0xc01a235c in vn_read (fp=0xc254cd40, uio=0xd7a42ed4, cred=0xc2c60780, flags=0x0, p=0xd79a0680) at vnode_if.h:334 #8 0xc017b690 in dofileread (p=0xd79a0680, fp=0xc254cd40, fd=0x3, buf=0x804d000, nbyte=0x200, offset=0xffffffffffffffff, flags=0x0) at /usr/src/sys/sys/file.h:146 #9 0xc017b556 in read (p=0xd79a0680, uap=0xd7a42f80) at /usr/src/sys/kern/sys_generic.c:117 #10 0xc025d7b5 in syscall2 (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0xbfbf002f, tf_edi = 0x4, tf_esi = 0x280fc3a0, tf_ebp = 0xbfbff8c0, tf_isp = 0xd7a42fd4, tf_ebx = 0x280ea424, tf_edx = 0x37, tf_ecx = 0x37, tf_eax = 0x3, tf_trapno = 0x7, tf_err = 0x2, tf_eip = 0x280defcc, tf_cs = 0x1f, tf_eflags = 0x293, tf_esp = 0xbfbff894, tf_ss = 0x2f}) at /usr/src/sys/i386/i386/trap.c:1155 #11 0xc024a62b in Xint0x80_syscall () cannot read proc at 0 (kgdb) up #1 0xc016cf8f in boot (howto=0x100) at /usr/src/sys/kern/kern_shutdown.c:313 313 dumpsys(); (kgdb) up #2 0xc016d3a9 in panic (fmt=0xc028745a "vinvalbuf: flush failed") at /usr/src/sys/kern/kern_shutdown.c:581 581 boot(bootopt); (kgdb) up #3 0xc019a719 in vinvalbuf (vp=0xd7dde8c0, flags=0x1, cred=0xc2c60780, p=0xd79a0680, slpflag=0x100, slptimeo=0x0) at /usr/src/sys/kern/vfs_subr.c:753 753 panic("vinvalbuf: flush failed"); (kgdb) print vp->v_dirtyblkhd $1 = {tqh_first = 0x0, tqh_last = 0xd7dde8f4} (kgdb) print vp->v_cleanblkhd $2 = {tqh_first = 0xcc5fa5ec, tqh_last = 0xcc5fa5f4} (kgdb) print *(vp->v_cleanblkhd->tqh_first) $3 = {b_hash = {le_next = 0xcc607e80, le_prev = 0xcc666e9c}, b_vnbufs = { tqe_next = 0x0, tqe_prev = 0xd7dde8ec}, b_freelist = { tqe_next = 0xcc5f8bfc, tqe_prev = 0xcc6060bc}, b_act = {tqe_next = 0x0, tqe_prev = 0xc2001d90}, b_flags = 537919520, b_qindex = 2, b_xflags = 2 '\002', b_lock = {lk_interlock = {lock_data = 0}, lk_flags = 0, lk_sharecount = 0, lk_waitcount = 0, lk_exclusivecount = 0, lk_prio = 20, lk_wmesg = 0xc02860b0 "bufwait", lk_timo = 0, lk_lockholder = -1}, b_error = 0, b_bufsize = 3584, b_runningbufspace = 0, b_bcount = 3147, b_resid = 0, b_dev = 0xffffffff, b_data = 0xceeec000 ..., b_kvabase = 0xceeec000 ..., b_kvasize = 16384, b_lblkno = 6949, b_blkno = 111184, b_offset = 56926208, b_iodone = 0, b_iodone_chain = 0x0, b_vp = 0xd7dde8c0, b_dirtyoff = 0, b_dirtyend = 0, b_rcred = 0x0, b_wcred = 0x0, b_pblkno = 1771566, b_saveaddr = 0x0, b_driver1 = 0x0, b_driver2 = 0x0, b_caller1 = 0x0, b_caller2 = 0x0, b_pager = {pg_spc = 0x0, pg_reqpage = 0}, b_cluster = { cluster_head = {tqh_first = 0xcc5c66a0, tqh_last = 0xcc640720}, cluster_entry = {tqe_next = 0xcc5c66a0, tqe_prev = 0xcc640720}}, b_pages = {0xc0afb4ac, 0x0 }, b_npages = 1, b_dep = { lh_first = 0x0}, b_chain = {parent = 0x0, count = 0}} (kgdb) up #4 0xc01d0b30 in nfs_vinvalbuf (vp=0xd7dde8c0, flags=0x1, cred=0xc2c60780, p=0xd79a0680, intrflg=0x1) at /usr/src/sys/nfs/nfs_bio.c:1190 1190 error = vinvalbuf(vp, flags, cred, p, 0, slptimeo); (kgdb) print p->p_pid $4 = 0x14594 (kgdb) btp 83348 frame 0 at 0xd7a42cb4: ebp d7a42cd8, eip 0xc016cf8f : push $0xc0282f08 frame 1 at 0xd7a42cd8: ebp d7a42cec, eip 0xc016d3a9 : lea 0x0(%esi),%esi frame 2 at 0xd7a42cec: ebp d7a42d2c, eip 0xc019a719 : lea 0x0(%esi),%esi frame 3 at 0xd7a42d2c: ebp d7a42d60, eip 0xc01d0b30 : add $0x18,%esp frame 4 at 0xd7a42d60: ebp d7a42e2c, eip 0xc01cf668 : mov %eax,0xffffff74(%ebp) frame 5 at 0xd7a42e2c: ebp d7a42e44, eip 0xc01f68d2 : jmp 0xc01f68d9 frame 6 at 0xd7a42e44: ebp d7a42e78, eip 0xc01a235c : mov %eax,0xffffffe8(%ebp) frame 7 at 0xd7a42e78: ebp d7a42ef4, eip 0xc017b690 : mov %eax,%esi frame 8 at 0xd7a42ef4: ebp d7a42f28, eip 0xc017b556 : mov %eax,%esi frame 9 at 0xd7a42f28: ebp d7a42fa0, eip 0xc025d7b5 : mov %eax,0xffffffb8(%ebp) (kgdb) pcb 83348 ip: c017091e sp: d47ecea4 bp: d47ecec0 bx: 00000000 0xc017091e : add $0x4,%esp (kgdb) ps ... 83348 d79a0680 d7a40000 239674 1 83279 004006 2 tail ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 21:51:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7692A37B405; Fri, 19 Oct 2001 21:51:12 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9K4pAU49727; Fri, 19 Oct 2001 21:51:10 -0700 (PDT) (envelope-from dillon) Date: Fri, 19 Oct 2001 21:51:10 -0700 (PDT) From: Matthew Dillon Message-Id: <200110200451.f9K4pAU49727@apollo.backplane.com> To: Doug Swarin Cc: hackers@FreeBSD.ORG, tmoestl@gmx.net, bp@FreeBSD.ORG Subject: Re: more on Re: Please review: bugfix for vinvalbuf() References: <20010711003926.B8799@crow.dom2ip.de> <200107110643.f6B6hTB24707@earth.backplane.com> <20010926204333.A15865@staff.texas.net> <200109281747.f8SHlUP29063@earth.backplane.com> <20011019212807.A538@staff.texas.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :Unfortunately, the recent patch to vinvalbuf() hasn't solved all of :our problems. We had another, different panic today. The process that :caused it was a 'tail' of a growing logfile over NFS. : :I have actually had this problem before, with FreeBSD 3.4, and reported :it then. I believed this PR to be relevant at the time, however, I do :not believe this client was writing to the file. : : [1998/06/23] kern/7028 http://www.freebsd.org/cgi/query-pr.cgi?pr=7028 : panic in vinvalbuf when appending/looking at tail of NFS file : :The system is running 4.4-RELEASE with the vinvalbuf() patch. Debugging :information is below. If I can provide any additional information, :let me know. : :Thanks for any help, :Doug How easily can you reproduce this? How often does it occur if you leave a tail running? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 21:58:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mw1.texas.net (mw1.texas.net [206.127.30.11]) by hub.freebsd.org (Postfix) with ESMTP id 67D3637B403 for ; Fri, 19 Oct 2001 21:58:28 -0700 (PDT) Received: from staff3.texas.net (staff3.texas.net [207.207.0.40]) by mw1.texas.net (8.11.6/8.11.6) with ESMTP id f9K4wRc05426; Fri, 19 Oct 2001 23:58:27 -0500 (CDT) Received: (from doug@localhost) by staff3.texas.net (8.11.6/8.11.6) id f9K4wRb01171; Fri, 19 Oct 2001 23:58:27 -0500 (CDT) (envelope-from doug) Date: Fri, 19 Oct 2001 23:58:22 -0500 From: Doug Swarin To: Matthew Dillon Cc: hackers@FreeBSD.ORG Subject: Re: more on Re: Please review: bugfix for vinvalbuf() Message-ID: <20011019235821.A1155@staff.texas.net> References: <20010711003926.B8799@crow.dom2ip.de> <200107110643.f6B6hTB24707@earth.backplane.com> <20010926204333.A15865@staff.texas.net> <200109281747.f8SHlUP29063@earth.backplane.com> <20011019212807.A538@staff.texas.net> <200110200451.f9K4pAU49727@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200110200451.f9K4pAU49727@apollo.backplane.com>; from dillon@apollo.backplane.com on Fri, Oct 19, 2001 at 09:51:10PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Oct 19, 2001 at 09:51:10PM -0700, Matthew Dillon wrote: > > : > :Unfortunately, the recent patch to vinvalbuf() hasn't solved all of > :our problems. We had another, different panic today. The process that > :caused it was a 'tail' of a growing logfile over NFS. > : > :I have actually had this problem before, with FreeBSD 3.4, and reported > :it then. I believed this PR to be relevant at the time, however, I do > :not believe this client was writing to the file. > : > : [1998/06/23] kern/7028 http://www.freebsd.org/cgi/query-pr.cgi?pr=7028 > : panic in vinvalbuf when appending/looking at tail of NFS file > : > :The system is running 4.4-RELEASE with the vinvalbuf() patch. Debugging > :information is below. If I can provide any additional information, > :let me know. > : > :Thanks for any help, > :Doug > > How easily can you reproduce this? How often does it occur if you > leave a tail running? > > -Matt I'm not able to reproduce this at will at the moment. The PR I mention has a program which it claims can cause the crash, which I will try running. I'll also try tailing various logfiles, including the one which caused this crash, which is being written to on the machine that is the NFS server. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 19 22: 5:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9D56637B403 for ; Fri, 19 Oct 2001 22:05:14 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9K55DB49867; Fri, 19 Oct 2001 22:05:13 -0700 (PDT) (envelope-from dillon) Date: Fri, 19 Oct 2001 22:05:13 -0700 (PDT) From: Matthew Dillon Message-Id: <200110200505.f9K55DB49867@apollo.backplane.com> To: Doug Swarin Cc: hackers@FreeBSD.ORG Subject: Re: more on Re: Please review: bugfix for vinvalbuf() Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :I'm not able to reproduce this at will at the moment. The PR I mention :has a program which it claims can cause the crash, which I will try :running. I'll also try tailing various logfiles, including the one which :caused this crash, which is being written to on the machine that is the :NFS server. : :Doug In looking at the code the solution may simply be to loop back up to the top of vinvalbuf() instead of panic if we wind up with buffer cache buffers. If V_SAVE is set the act of writing dirty VM pages can cause new buffer to instantiate and result in the panic. But I would really like to get the bug reproduceable to make sure that the solution really does fix it. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 20 0:14: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from server3.safepages.com (server3.safepages.com [216.127.146.5]) by hub.freebsd.org (Postfix) with ESMTP id 6549037B405; Sat, 20 Oct 2001 00:13:55 -0700 (PDT) Received: from localhost (unknown [65.138.137.74]) by server3.safepages.com (Postfix) with ESMTP id CE1695EED; Sat, 20 Oct 2001 07:13:30 +0000 (GMT) X-Sender: sronalds@phastnet.com From: Ronald Samuels To: "Mortgage Borrower" Date: Sat, 20 Oct 2001 23:43:00 -0700 Subject: Need a Home Loan? Let Us Help! Reply-To: sronalds@phastnet.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001__52060418_1423.61" Message-Id: <20011020071330.CE1695EED@server3.safepages.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a Multipart MIME message. ------=_NextPart_000_001__52060418_1423.61 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit ------=_NextPart_000_001__52060418_1423.61 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: base64 DQoNCjxIVE1MPg0KDQo8aGVhZD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIg Q09OVEVOVD0idGV4dC9odG1sO2NoYXJzZXQ9aXNvLTg4NTktMSI+DQo8IURPQ1RZUEUgSFRN TCBQVUJMSUMgIi0vL1czQy8vRFREIEhUTUwgNC4wIFRyYW5zaXRpb25hbC8vRU4iPg0KPFRJ VExFPkZyZWUgUmF0ZSBRdW90ZTwvVElUTEU+DQo8TUVUQSBjb250ZW50PSJ0ZXh0L2h0bWw7 IGNoYXJzZXQ9aXNvLTg4NTktMSIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+PFhNRVRBIA0K Y29udGVudD0iTW96aWxsYS80LjcgW2VuXSAoV2luOTg7IEkpIFtOZXRzY2FwZV0iIG5hbWU9 IkdFTkVSQVRPUiI+DQo8TUVUQSBjb250ZW50PSJNaWNyb3NvZnQgRnJvbnRQYWdlIDQuMCIg bmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwvSEVBRD4NCjxCT0RZIGJhY2tn cm91bmQ9aHR0cDovLzMyNDkzMDk2NTAvbW9uZXlfZ3IuanBnIGJnQ29sb3I9I2ZmZmZmZiBi Z3Byb3BlcnRpZXM9ImZpeGVkIj4NCjxESVYgc3R5bGU9IkZPTlQ6IDEwcHQgYXJpYWwiPg0K PERJVj4mbmJzcDs8L0RJVj48L0RJVj4NCjxESVY+PEJSPjwvRElWPg0KPEJSPg0KPFAgYWxp Z249Y2VudGVyPjxiPjxpPjxmb250IGNvbG9yPSIjMDAwMGZmIiBmYWNlPSJCcnVzaCBTY3Jp cHQgTVQiIHNpemU9IjUiPiZxdW90O0FsbCBvdXIgdGhvdWdodHMsIHByYXllcnMgYW5kIGxv dmUgZ28gb3V0IHRvIHRoZSBmYW1pbGllcyBhbmQgZnJpZW5kcyBvZiB0aGUgdmljdGltcyBv ZiB0aGUgV29ybGQgVHJhZGUgQ2VudGVyIHRyYWdlZHkuJnF1b3Q7PC9mb250PjwvaT48L2I+ PC9QPg0KDQo8UCBhbGlnbj1jZW50ZXI+PGVtPjxiPjxmb250IGNvbG9yPSIjZmYwMDAwIiBz aXplPSI2IiBmYWNlPSJhcmlhbCI+JnF1b3Q7UmVmaW5hbmNlIFlvdXINCkN1cnJlbnQgTW9y dGdhZ2UgV2hpbGUgUmF0ZXMgQXJlIExPVyEhJnF1b3Q7PC9mb250PjwvYj48L2VtPjwvUD4N CjxNQVJRVUVFPjxpPjxiPjxGT05UIHNpemU9NCBjb2xvcj0jMDAwMGZmPkhPTUUgRVFVSVRZ IExPQU5TICoqKiBKVU1CTyBMT0FOUyAqKiogSE9NRSBJTVBST1ZFTUVOVCBMT0FOUyAqKiog DQogICAgICBERUJUIENPTlNPTElEQVRJT04gTE9BTlMgKioqIFJFRklOQU5DRSBMT0FOUyAq KiogQUxMIEFSRSBBVkFJTEFCTEUgVE8gWU9VICoqKiBSQVRFUyBBUyBMT1cgQVMgDQogICAg ICAzLjk1JTwvZm9udD48L2I+PC9pPjwvbWFycXVlZT4NCjxCUj48QlI+DQo8cCBhbGlnbj0i Y2VudGVyIj48Yj48Zm9udCBzaXplPSI0Ij5Nb3J0Z2FnZSBSYXRlcyBBcmUgU28gTG93ISZu YnNwOzwvZm9udD48L2I+PC9wPg0KPHAgYWxpZ249ImNlbnRlciI+PGI+PGZvbnQgc2l6ZT0i NCI+WW91IENhbiBTYXZlIFRob3VzYW5kcyBPZiBEb2xsYXJzIEJ5IFRha2luZw0KQWR2YW50 YWdlIE5vdyE8L2ZvbnQ+PC9iPjwvcD4NCjxQIGFsaWduPWNlbnRlcj48RU0+PEI+PEZPTlQg Y29sb3I9I2ZmMDAwMCBzaXplPTU+JnF1b3Q7V0UgQVJFIEFOIEFTU09DSUFUSU9OIE9GDQpN T1JUR0FHRSBCUk9LRVJTIEFORCBMRU5ERVJTIDwvRk9OVD48L0I+PC9FTT48L1A+DQo8UCBh bGlnbj1jZW50ZXI+PEVNPjxCPjxGT05UIGNvbG9yPSNmZjAwMDAgc2l6ZT01PldJVEggVEhF IEJFU1QgUkFURVMgQU5EIFRIRSBMT1dFU1QNCkNPU1RTISZxdW90PC9GT05UPjwvQj48L0VN PjwvUD4NCjxwIGFsaWduPSJjZW50ZXIiPiZuYnNwOzwvcD4NCjxQIGFsaWduPWNlbnRlcj48 Rk9OVCBjb2xvcj0jMDAwMGZmIHNpemU9ND48Qj5XZSZuYnNwO2hhdmUgdGhvdXNhbmRzIG9m IGxvYW4gDQpwcm9ncmFtcyB0aHJvdWdoIGh1bmRyZWRzIG9mIGxlbmRlcnMhPEJSPjwvQj48 L0ZPTlQ+PEZPTlQgc2l6ZT0zPjwvRk9OVD48L1A+DQo8UCBhbGlnbj1jZW50ZXI+PFNUUk9O Rz48Rk9OVCBzaXplPTU+WW91IGNhbiBjaG9vc2UgZnJvbSZuYnNwOyJBZGp1c3RhYmxlIFJh dGUNCk1vcnRnYWdlcyANCmFzIGxvdyBhcyAzLjk1JSZxdW90OzwvRk9OVD48L1NUUk9ORz48 L1A+DQo8UCBhbGlnbj1jZW50ZXI+PFNUUk9ORz48Rk9OVCBzaXplPTU+YW5kJm5ic3A7IkZp eGVkIFJhdGUgTW9ydGdhZ2VzIGFzIGxvdyBhcw0KNS41MCUmbmJzcDs8L0ZPTlQ+PC9TVFJP Tkc+PC9QPg0KPFAgYWxpZ249Y2VudGVyPjxTVFJPTkc+PEZPTlQgc2l6ZT01PmFsbCB3aXRo IHRoZSBsb3dlc3QgY29zdHMgaW4gdGhlDQpOYXRpb24hJnF1b3Q7PC9GT05UPjwvU1RST05H PjxCSUc+PEJJRz48Rk9OVCBjb2xvcj0jZmYwMDAwPio8L0ZPTlQ+PC9CSUc+PC9CSUc+PC9Q Pg0KPFAgYWxpZ249Y2VudGVyPjxGT05UIA0Kc2l6ZT01Pjxmb250IGNvbG9yPSIjRkYwMDAw Ij4mcXVvdDs8Yj48aT5ZT1UgQ0FOIDx1PkJVWSBET1dOIFlPVVIgSU5URVJFU1QgUkFURTwv dT4NClRPPC9pPjwvYj48L2ZvbnQ+PC9GT05UPjwvUD4NCjxQIGFsaWduPWNlbnRlcj48Zm9u dCBjb2xvcj0iI0ZGMDAwMCIgc2l6ZT0iNSI+PGI+PGk+QVMgTE9XIEFTIFlPVSBDQU4NCkFG Rk9SRCEmcXVvdDs8L2k+PC9iPjwvZm9udD48Rk9OVCANCnNpemU9NT48QlI+PC9GT05UPjxG T05UIHNpemU9Mz48L0ZPTlQ+PC9QPg0KPFAgYWxpZ249Y2VudGVyPjxGT05UIHNpemU9KzA+ PEZPTlQgY29sb3I9IzAwMDBmZiBzaXplPTI+PEJJRz48QklHPjxGT05UIA0KY29sb3I9I2Zm MDAwMCBzaXplPTU+KjwvRk9OVD48L0JJRz48U1RST05HPkFsbCByYXRlcyBhcmUgYmFzZWQg b24gDQpxdWFsaWZpY2F0aW9uPC9TVFJPTkc+ITwvQklHPjwvRk9OVD48L0ZPTlQ+PC9QPg0K PFAgYWxpZ249Y2VudGVyPjxGT05UIHNpemU9KzA+PEZPTlQgc2l6ZT0yPjxCSUc+PC9CSUc+ PC9GT05UPjxGT05UIA0KY29sb3I9IzAwMDBmZj48Rk9OVCBmYWNlPUFyaWFsPjxGT05UIHNp emU9Mj48QSBocmVmPSJodHRwOi8vMzI0OTMwOTY1MCIgDQp0YXJnZXQ9X2JsYW5rPjxGT05U IHNpemU9NT48U1RST05HPjxGT05UIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+Q2xpY2sgaGVy ZSBmb3IgDQp5b3VyIDwvRk9OVD48Rk9OVCBzaXplPTY+PEZPTlQgZmFjZT0iVGltZXMgTmV3 IFJvbWFuIj48RU0+IkZSRUUgUkFURSANClFVT1RFIiE8L0VNPjwvRk9OVD48L0ZPTlQ+PC9T VFJPTkc+PC9GT05UPjwvQT48L0ZPTlQ+PC9GT05UPjwvRk9OVD48L0ZPTlQ+PC9QPg0KPFAg YWxpZ249bGVmdD4mbmJzcDs8L1A+DQo8UCBhbGlnbj1sZWZ0PjxpPjxiPjxmb250IGZhY2U9 IkFyaWFsIiBzaXplPSIrMCI+Q0xJQ0sgT04gTE9BTlMgQkVMT1cgRk9SIFlPVVINCkZSRUUg QVBQTElDQVRJT04hPC9mb250PjwvYj48L2k+PEZPTlQgZmFjZT1BcmlhbD48QlI+PC9GT05U PjwvUD4NCjxQIGFsaWduPWxlZnQ+PFNUUk9ORz48RU0+PEEgaHJlZj0iaHR0cDovLzMyNDkz MDk2NTAiIA0KdGFyZ2V0PV9ibGFuaz48Zm9udCBzaXplPSI1IiBjb2xvcj0iIzgwMDA4MCI+ UHVyY2hhc2UgTG9hbnM8L2ZvbnQ+PC9BPiA8Rk9OVCBzaXplPTU+DQo8L0ZPTlQ+IDwvRU0+ PEZPTlQgDQpzaXplPTQ+LSA8RU0+VGhvdXNhbmRzIG9mIHByb2dyYW1zIA0KZm9yIEZpcnN0 IE1vcnRnYWdlcyE8L0VNPjwvRk9OVD48ST48L0k+PC9TVFJPTkc+PEk+PEZPTlQgDQpjb2xv cj0jMDAwMDAwPjxCUj48QlI+PC9GT05UPjwvST48QSBocmVmPSJodHRwOi8vMzI0OTMwOTY1 MCIgX2JsYW5rPz48RU0+PFNUUk9ORz48Zm9udCBzaXplPSI1IiBjb2xvcj0iIzgwMDA4MCI+ UmVmaW5hbmNlIExvYW5zPC9mb250PjwvU1RST05HPjwvRU0+PEk+PEZPTlQgDQpjb2xvcj0j MDAwMDAwIHNpemU9Mj4gPC9GT05UPjwvST48L0E+PEk+PEZPTlQgY29sb3I9IzAwMDAwMCBz aXplPTQ+LSA8Qj5SZWR1Y2UgeW91ciANCm1vbnRobHkgcGF5bWVudHMgYW5kPC9GT05UPjxG T05UIGNvbG9yPSMwMDAwMDAgc2l6ZT0yPiA8L0ZPTlQ+PEZPTlQgDQpjb2xvcj0jZmYwMDAw IHNpemU9NT5HZXQgQ2FzaCBCYWNrITwvRk9OVD48L0I+PEZPTlQgY29sb3I9IzAwMDAwMCBz aXplPTQ+IA0KPC9GT05UPjxGT05UIGNvbG9yPSMwMDAwMDAgc2l6ZT0zPjxCUj48QlI+PC9G T05UPjwvST48QSANCmhyZWY9Imh0dHA6Ly8zMjQ5MzA5NjUwIiB0YXJnZXQ9X2JsYW5rPjxm b250IGNvbG9yPSIjODAwMDgwIj48RU0+PEI+PEZPTlQgc2l6ZT01PlNlY29uZCANCk1vcnRn YWdlczwvRk9OVD48L0I+PC9FTT48ST48Rk9OVCBzaXplPTM+IDwvRk9OVD48L0k+DQo8L2Zv bnQ+IDwvQT48ST48Rk9OVCBjb2xvcj0jMDAwMDAwIHNpemU9Mz4gLSA8L0ZPTlQ+PEI+PEZP TlQgDQpjb2xvcj0jMDAwMDAwIHNpemU9ND5XZSBjYW4gaGVscCB5b3UgZ2V0IGZyb20gPC9G T05UPjxGT05UIGNvbG9yPSNmZjAwMDAgDQpzaXplPTU+OTAlPC9GT05UPjxGT05UIGNvbG9y PSMwMDAwMDAgc2l6ZT00PiB1cCB0byA8L0ZPTlQ+PEZPTlQgY29sb3I9I2ZmMDAwMCANCnNp emU9NT4xMjUlPC9GT05UPjxGT05UIGNvbG9yPSMwMDAwMDAgc2l6ZT00PiBvZiB5b3VyIGhv bWVzIHZhbHVlISAocmF0aW9zIHZhcnkgDQpieSBzdGF0ZSk8L0ZPTlQ+PC9CPjwvUD4NCjxQ IGFsaWduPWxlZnQ+PEEgaHJlZj0iaHR0cDovLzMyNDkzMDk2NTAiIA0KdGFyZ2V0PV9ibGFu az48Qj48Zm9udCBzaXplPSI1IiBjb2xvcj0iIzgwMDA4MCI+RGVidCBDb25zb2xpZGF0aW9u PC9mb250PjwvQj48L0E+PEZPTlQgY29sb3I9IzAwMDAwMCBzaXplPTM+IDxGT05UIGNvbG9y PSMwMDAwMDAgc2l6ZT00Pi0gDQo8Qj5Db21iaW5lIDwvRk9OVD48Rk9OVCBjb2xvcj0jZmYw MDAwIHNpemU9NT5hbGw8L0ZPTlQ+PEZPTlQgY29sb3I9IzAwMDAwMCANCnNpemU9ND4geW91 ciBiaWxscyBpbnRvIDwvRk9OVD48Rk9OVCBjb2xvcj0jZmYwMDAwIHNpemU9NT5PbmUgTG93 IE1vbnRobHkgDQpQYXltZW50ITwvRk9OVD48L0I+PEJSPjxCUj48L0ZPTlQ+PEI+PEEgDQpo cmVmPSJodHRwOi8vMzI0OTMwOTY1MCIgdGFyZ2V0PV9ibGFuaz48Zm9udCBzaXplPSI1IiBj b2xvcj0iIzgwMDA4MCI+Rmlyc3QgVGltZSBIb21lIEJ1eWVyczwvZm9udD48L0E+PEZPTlQg Y29sb3I9IzAwMDAwMCBzaXplPTM+IC0gDQo8Rk9OVCBjb2xvcj0jMDAwMDAwIHNpemU9ND5X ZSBjYW4gaGVscCB5b3UgYnV5IHdpdGggPEZPTlQgY29sb3I9I2ZmMDAwMCANCnNpemU9NT5M b3c8L0ZPTlQ+PC9GT05UPjxGT05UIGNvbG9yPSNmZjAwMDAgc2l6ZT01PiBNb25leSBEb3du PC9GT05UPjxGT05UIA0KY29sb3I9IzAwMDAwMCBzaXplPTQ+LCBhbmQgZXZlbiA8L0ZPTlQ+ PEZPTlQgY29sb3I9I2ZmMDAwMCBzaXplPTU+R2V0IENhc2ggDQpCYWNrITwvRk9OVD48L0ZP TlQ+PC9CPjwvUD48L0k+DQo8UCBhbGlnbj1jZW50ZXI+PEJJRz48QklHPjxGT05UIGNvbG9y PSNmZjAwMDA+KjwvRk9OVD48L0JJRz5BbGwgcmF0ZXMgYXJlIGJhc2VkIA0Kb24gcXVhbGlm aWNhdGlvbiE8L0JJRz48L1A+DQo8UCBhbGlnbj1jZW50ZXI+PEI+PEk+PEZPTlQgY29sb3I9 IzAwMDAwMCBzaXplPTY+V2UgaGF2ZSBwcm9ncmFtcyBmb3IgDQo8L0ZPTlQ+PEZPTlQgY29s b3I9I2ZmMDAwMCBzaXplPTY+PFU+RVZFUlk8L1U+PC9GT05UPjxGT05UIGNvbG9yPSMwMDAw MDAgc2l6ZT02PiANCmNyZWRpdCBzaXR1YXRpb24hPC9GT05UPjxCUj48QlI+PEEgaHJlZj0i aHR0cDovLzMyNDkzMDk2NTAiIHRhcmdldD1fYmxhbms+PEZPTlQgDQpjb2xvcj0jMDAwMGZm IHNpemU9NT5DbGljayBoZXJlIGZvciB5b3VyIEZSRUUgUkFURSBRVU9URSE8L0ZPTlQ+PC9B PjwvST48L0I+PC9QPg0KPFAgYWxpZ249bGVmdD48Rk9OVCBjb2xvcj0jMDA4MDAwPjxTVFJP Tkc+JnF1b3Q7VGhpcyBtZXNzYWdlIGlzIGJlaW5nIHNlbnQgdG8NCnlvdSBpbiBjb21wbGlh bmNlIHdpdGgmbmJzcDtCaWxsIFMuIDE2MTggVGl0bGUgSUlJIHBhc3NlZCBieSB0aGUgMTA1 dGggVVMNCkNvbmdyZXNzLCB3aGljaCBzdGF0ZXMgdGhhdCB0aGlzIGxldHRlciBjYW4gbm90 IGJlIGNvbnNpZGVyZWQgc3BhbSBhcyBsb25nIGFzIHdlDQppbmNsdWRlICgxKSBWYWxpZCBD b250YWN0IEluZm9ybWF0aW9uIGFuZCAoMikmbmJzcDthIHdheSB0byBiZSByZW1vdmVkIGZy b20gYW55DQpmdXJ0aGVyIHRyYW5zbWlzc2lvbnMgYXQgbm8gY29zdCB0byB5b3UgYnkgc3Vi bWl0dGluZyBhIHJlcXVlc3QgdG8gYmUNCnJlbW92ZWQuJnF1b3Q7IC4gPGEgaHJlZj0iaHR0 cDovLzMyNDkzMDk2NTAvcmVtb3ZlLmh0bSI+Q2xpY2sgSGVyZSB0byBTZW5kIGEgUmVtb3Zl IFJlcXVlc3Q8L2E+Lg0KJnF1b3Q7V2UgaG9ub3IgYWxsIHJlbW92ZSBlbWFpbCBhZGRyZXNz IHJlcXVlc3RzJm5ic3A7aW1tZWRpYXRlbHkuJnF1b3Q7PC9TVFJPTkc+PC9GT05UPjwvUD48 L0JPRFk+PC9IVE1MPg== ------=_NextPart_000_001__52060418_1423.61-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 20 11: 0: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 0B87437B401; Sat, 20 Oct 2001 11:00:03 -0700 (PDT) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id KAA82982; Sat, 20 Oct 2001 10:51:08 -0700 (PDT) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.3/8.11.3) id f9KHp1584570; Sat, 20 Oct 2001 10:51:01 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200110201751.f9KHp1584570@arch20m.dellroad.org> Subject: Re: netgraph one2many question In-Reply-To: "from Milon Papezik at Oct 18, 2001 12:37:56 pm" To: Milon Papezik Date: Sat, 20 Oct 2001 10:51:01 -0700 (PDT) Cc: "'hackers@freebsd.org'" , "'net@freebsd.org'" X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Milon Papezik writes: > I would like to extend ng_one2many module to include > automatic link failure datection, failover and FEC functionality. > > My question is: > Are interface nodes able to send upstream notification > that their state has changed or do I have to poll their status periodically > as it is done in ng_fec module made kindly available by wpaul ? They don't now, but I think you could add this in a reasonably unoffensive way. What you would do is add a new function pointer to struct ifnet, say "void (*if_report)(struct ifnet *, int status)" or something. When a device driver detected link going up/down, it could call this function (if non-NULL). Then if_ethersubr() would set this function pointer to point to some function if_ether_report(). When if_ether_report() is called, if ng_ether was loaded, it would call into ng_ether() to generate a control message that would be passed to the node connected to the "lower" hook. Then, ng_one2many could be modified to understand this control message and do the right thing according to its configuration. Or, something like that. Polling might be a quicker and easier though less precise way to do it for starters. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 20 11:23:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by hub.freebsd.org (Postfix) with ESMTP id 044B137B405 for ; Sat, 20 Oct 2001 11:23:15 -0700 (PDT) Received: by sharmas.dhs.org (Postfix, from userid 500) id EC4E95E594; Sat, 20 Oct 2001 11:24:51 -0700 (PDT) From: Arun Sharma To: des@ofug.org Cc: hackers@freebsd.org Subject: Re: truss vs ktrace In-Reply-To: References: <3BCCCF74.75B7F36C@disney.com> Message-Id: <20011020182451.EC4E95E594@sharmas.dhs.org> Date: Sat, 20 Oct 2001 11:24:51 -0700 (PDT) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 17 Oct 2001 02:02:07 +0000 (UTC), Dag-Erling Smorgrav wrote: > Jim Pirzyk writes: > > So which should I use? Why is there two around? I see that truss has > > less command line switches than ktrace, but it is a little bit more > > standard. > > - truss slows down the slave process a *lot* as the slave process > stops at every syscall and waits for truss to notice, obtain and > process information (a task which in itself requires a bunch of > additional context switches and syscalls) and print its output. > This also means that if you pipe truss through less and don't page > down fast enough, the slave process will hang waiting for truss > which is waitig for less to absorb its output. True, the choice depends on which one meets your debugging needs better. I find the performance of truss usually adequate for my purposes. > > - truss currently can't follow forks and trace children of the > original process. This should be fixable, though. > This has been taken care of: http://www.sharma-home.net/~adsharma/projects/freebsd/truss.diff.gz http://www.sharma-home.net/~adsharma/projects/freebsd/truss.tar.gz The above patch supports fork as well as rfork, so can be used with libraries using rfork for pthread implementations. Another advantage of truss is that the output is "online" and interactive. ktrace requires you to use kdump to view the trace. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 20 12:18:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id A4F2D37B405; Sat, 20 Oct 2001 12:18:25 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA80757; Sat, 20 Oct 2001 13:23:18 -0700 (PDT) Date: Sat, 20 Oct 2001 13:23:16 -0700 (PDT) From: Julian Elischer To: Archie Cobbs Cc: Milon Papezik , "'hackers@freebsd.org'" , "'net@freebsd.org'" Subject: Re: netgraph one2many question In-Reply-To: <200110201751.f9KHp1584570@arch20m.dellroad.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill Paul has written a specific NETGRAPH FEC module... he has failover as well.. (it is only PART a netgraph module as it doesn;t use the netgraph hooks to talk to teh ethernet driver.. (strange)) I suggest you look for it in the archives or on http://www.freebsd.org/~wpaul/ On Sat, 20 Oct 2001, Archie Cobbs wrote: > Milon Papezik writes: > > I would like to extend ng_one2many module to include > > automatic link failure datection, failover and FEC functionality. > > > > My question is: > > Are interface nodes able to send upstream notification > > that their state has changed or do I have to poll their status periodically > > as it is done in ng_fec module made kindly available by wpaul ? > > They don't now, but I think you could add this in a reasonably > unoffensive way. > > What you would do is add a new function pointer to struct ifnet, > say "void (*if_report)(struct ifnet *, int status)" or something. > > When a device driver detected link going up/down, it could call > this function (if non-NULL). Then if_ethersubr() would set this > function pointer to point to some function if_ether_report(). > When if_ether_report() is called, if ng_ether was loaded, it > would call into ng_ether() to generate a control message that > would be passed to the node connected to the "lower" hook. > > Then, ng_one2many could be modified to understand this control > message and do the right thing according to its configuration. > > Or, something like that. Polling might be a quicker and easier > though less precise way to do it for starters. > > -Archie > > __________________________________________________________________________ > Archie Cobbs * Packet Design * http://www.packetdesign.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" 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 Oct 20 13:35:18 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 EFA2B37B401 for ; Sat, 20 Oct 2001 13:34:42 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f9KKXh133978 for hackers@freebsd.org; Sat, 20 Oct 2001 15:33:43 -0500 (CDT) (envelope-from jlemon) Date: Sat, 20 Oct 2001 15:33:43 -0500 From: Jonathan Lemon To: hackers@freebsd.org Subject: patch for review: multiple console support Message-ID: <20011020153343.U75389@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This patch adds support for multiple simultaneous low level consoles to the kernel. In essence, it is equivalent to the -D flag in the /boot.config file. Support can be turned on by executing 'boot -D' from the loader, or by using the comcontrol program (which is appended to the end of the patch). The motivation for performing this work (other than wanting to be able to use ddb on vidconsol and comconsole interchangeably) is the upcoming network console support, which requires the ability to add a console after the system is up. Objections and bugs aside, I plan to commit this shortly. -- Jonathan Index: kern/tty_cons.c =================================================================== RCS file: /ncvs/src/sys/kern/tty_cons.c,v retrieving revision 1.92 diff -u -r1.92 tty_cons.c --- kern/tty_cons.c 2001/09/12 08:37:46 1.92 +++ kern/tty_cons.c 2001/10/20 03:23:04 @@ -44,11 +44,15 @@ #include #include #include +#include +#include #include +#include #include #include #include #include +#include #include @@ -78,47 +82,43 @@ /* kqfilter */ cnkqfilter, }; -static dev_t cn_dev_t; /* seems to be never really used */ +struct cn_device { + STAILQ_ENTRY(cn_device) cnd_next; + char cnd_name[16]; + struct vnode *cnd_vp; + struct consdev *cnd_cn; +}; + +#define CNDEVPATHMAX 32 +#define CNDEVTAB_SIZE 4 +static struct cn_device cn_devtab[CNDEVTAB_SIZE]; +static STAILQ_HEAD(, cn_device) cn_devlist = + STAILQ_HEAD_INITIALIZER(cn_devlist); + +#define CND_INVALID(cnd, td) \ + (cnd == NULL || cnd->cnd_vp == NULL || \ + (cnd->cnd_vp->v_type == VBAD && !cn_devopen(cnd, td, 1))) + static udev_t cn_udev_t; SYSCTL_OPAQUE(_machdep, CPU_CONSDEV, consdev, CTLFLAG_RD, &cn_udev_t, sizeof cn_udev_t, "T,dev_t", ""); -static int cn_mute; - int cons_unavail = 0; /* XXX: * physical console not available for * input (i.e., it is in graphics mode) */ - -static u_char cn_is_open; /* nonzero if logical console is open */ -static int openmode, openflag; /* how /dev/console was openned */ +static int cn_mute; +static int openflag; /* how /dev/console was opened */ +static int cn_is_open; static dev_t cn_devfsdev; /* represents the device private info */ -static u_char cn_phys_is_open; /* nonzero if physical device is open */ -static d_close_t *cn_phys_close; /* physical device close function */ -static d_open_t *cn_phys_open; /* physical device open function */ - struct consdev *cn_tab; /* physical console device info */ CONS_DRIVER(cons, NULL, NULL, NULL, NULL, NULL, NULL, NULL); SET_DECLARE(cons_set, struct consdev); void -cninit() +cninit(void) { - struct consdev *best_cp, *cp, **list; - - /* - * Find the first console with the highest priority. - */ - best_cp = NULL; - SET_FOREACH(list, cons_set) { - cp = *list; - if (cp->cn_probe == NULL) - continue; - (*cp->cn_probe)(cp); - if (cp->cn_pri > CN_DEAD && - (best_cp == NULL || cp->cn_pri > best_cp->cn_pri)) - best_cp = cp; - } + struct consdev *best_cn, *cn, **list; /* * Check if we should mute the console (for security reasons perhaps) @@ -131,74 +131,176 @@ |RB_VERBOSE |RB_ASKNAME |RB_CONFIG)) == RB_MUTE); - + /* - * If no console, give up. + * Find the first console with the highest priority. */ - if (best_cp == NULL) { - if (cn_tab != NULL && cn_tab->cn_term != NULL) - (*cn_tab->cn_term)(cn_tab); - cn_tab = best_cp; + best_cn = NULL; + SET_FOREACH(list, cons_set) { + cn = *list; + if (cn->cn_probe == NULL) + continue; + cn->cn_probe(cn); + if (cn->cn_pri == CN_DEAD) + continue; + if (best_cn == NULL || cn->cn_pri > best_cn->cn_pri) + best_cn = cn; + if (boothowto & RB_MULTIPLE) { + /* + * Initialize console, and attach to it. + */ + cnadd(cn); + cn->cn_init(cn); + } + } + if (best_cn == NULL) return; + if ((boothowto & RB_MULTIPLE) == 0) { + cnadd(best_cn); + best_cn->cn_init(best_cn); } - /* - * Initialize console, then attach to it. This ordering allows - * debugging using the previous console, if any. + * Make the best console the preferred console. */ - (*best_cp->cn_init)(best_cp); - if (cn_tab != NULL && cn_tab != best_cp) { - /* Turn off the previous console. */ - if (cn_tab->cn_term != NULL) - (*cn_tab->cn_term)(cn_tab); - } - cn_tab = best_cp; + cnselect(best_cn); +} + +/* add a new physical console to back the virtual console */ +int +cnadd(struct consdev *cn) +{ + struct cn_device *cnd; + int i; + + STAILQ_FOREACH(cnd, &cn_devlist, cnd_next) + if (cnd->cnd_cn == cn) + return (0); + for (i = 0; i < CNDEVTAB_SIZE; i++) { + cnd = &cn_devtab[i]; + if (cnd->cnd_cn == NULL) + break; + } + if (cnd->cnd_cn != NULL) + return (ENOMEM); + cnd->cnd_cn = cn; + STAILQ_INSERT_TAIL(&cn_devlist, cnd, cnd_next); + return (0); } void -cninit_finish() +cnremove(struct consdev *cn) { - struct cdevsw *cdp; + struct cn_device *cnd; - if ((cn_tab == NULL) || cn_mute) + STAILQ_FOREACH(cnd, &cn_devlist, cnd_next) { + if (cnd->cnd_cn != cn) + continue; + STAILQ_REMOVE(&cn_devlist, cnd, cn_device, cnd_next); + if (cnd->cnd_vp != NULL) + vn_close(cnd->cnd_vp, openflag, NOCRED, NULL); + cnd->cnd_vp = NULL; + cnd->cnd_cn = NULL; + cnd->cnd_name[0] = '\0'; +#if 0 + /* + * XXX + * syscons gets really confused if console resources are + * freed after the system has initialized. + */ + if (cn->cn_term != NULL) + cn->cn_term(cn); +#endif return; - - /* - * Hook the open and close functions. - */ - cdp = devsw(cn_tab->cn_dev); - if (cdp != NULL) { - cn_phys_close = cdp->d_close; - cdp->d_close = cnclose; - cn_phys_open = cdp->d_open; - cdp->d_open = cnopen; } - cn_dev_t = cn_tab->cn_dev; - cn_udev_t = dev2udev(cn_dev_t); } -static void -cnuninit(void) +void +cnselect(struct consdev *cn) { - struct cdevsw *cdp; + struct cn_device *cnd; - if (cn_tab == NULL) + STAILQ_FOREACH(cnd, &cn_devlist, cnd_next) { + if (cnd->cnd_cn != cn) + continue; + if (cnd == STAILQ_FIRST(&cn_devlist)) + return; + STAILQ_REMOVE(&cn_devlist, cnd, cn_device, cnd_next); + STAILQ_INSERT_HEAD(&cn_devlist, cnd, cnd_next); return; + } +} - /* - * Unhook the open and close functions. - */ - cdp = devsw(cn_tab->cn_dev); - if (cdp != NULL) { - cdp->d_close = cn_phys_close; - cdp->d_open = cn_phys_open; - } - cn_phys_close = NULL; - cn_phys_open = NULL; - cn_dev_t = NODEV; - cn_udev_t = NOUDEV; +void +cndebug(char *str) +{ + int i, len; + + len = strlen(str); + cnputc('>'); cnputc('>'); cnputc('>'); cnputc(' '); + for (i = 0; i < len; i++) + cnputc(str[i]); + cnputc('\n'); +} + +static int +sysctl_kern_console(SYSCTL_HANDLER_ARGS) +{ + struct cn_device *cnd; + struct consdev *cp, **list; + char *name, *p; + int delete, len, error; + + len = 2; + SET_FOREACH(list, cons_set) { + cp = *list; + if (cp->cn_dev != NULL) + len += strlen(devtoname(cp->cn_dev)) + 1; + } + STAILQ_FOREACH(cnd, &cn_devlist, cnd_next) + len += strlen(devtoname(cnd->cnd_cn->cn_dev)) + 1; + len = len > CNDEVPATHMAX ? len : CNDEVPATHMAX; + MALLOC(name, char *, len, M_TEMP, M_WAITOK | M_ZERO); + p = name; + STAILQ_FOREACH(cnd, &cn_devlist, cnd_next) + p += sprintf(p, "%s,", devtoname(cnd->cnd_cn->cn_dev)); + *p++ = '/'; + SET_FOREACH(list, cons_set) { + cp = *list; + if (cp->cn_dev != NULL) + p += sprintf(p, "%s,", devtoname(cp->cn_dev)); + } + error = sysctl_handle_string(oidp, name, len, req); + if (error == 0 && req->newptr != NULL) { + p = name; + error = ENXIO; + delete = 0; + if (*p == '-') { + delete = 1; + p++; + } + SET_FOREACH(list, cons_set) { + cp = *list; + if (cp->cn_dev == NULL || + strcmp(p, devtoname(cp->cn_dev)) != 0) + continue; + if (delete) { + cnremove(cp); + error = 0; + } else { + error = cnadd(cp); + if (error == 0) + cnselect(cp); + } + break; + } + } + FREE(name, M_TEMP); + return (error); } +SYSCTL_PROC(_kern, OID_AUTO, console, CTLTYPE_STRING|CTLFLAG_RW, + 0, 0, sysctl_kern_console, "A", "Console device control"); + /* * User has changed the state of the console muting. * This may require us to open or close the device in question. @@ -211,165 +313,123 @@ ocn_mute = cn_mute; error = sysctl_handle_int(oidp, &cn_mute, 0, req); - if((error == 0) && (cn_tab != NULL) && (req->newptr != NULL)) { - if(ocn_mute && !cn_mute) { - /* - * going from muted to unmuted.. open the physical dev - * if the console has been openned - */ - cninit_finish(); - if(cn_is_open) - /* XXX curthread is not what we want really */ - error = cnopen(cn_dev_t, openflag, - openmode, curthread); - /* if it failed, back it out */ - if ( error != 0) cnuninit(); - } else if (!ocn_mute && cn_mute) { - /* - * going from unmuted to muted.. close the physical dev - * if it's only open via /dev/console - */ - if(cn_is_open) - error = cnclose(cn_dev_t, openflag, - openmode, curthread); - if ( error == 0) cnuninit(); - } - if (error != 0) { - /* - * back out the change if there was an error - */ - cn_mute = ocn_mute; - } + if (error != 0 || req->newptr == NULL) + return (error); + if (ocn_mute && !cn_mute && cn_is_open) + error = cnopen(NODEV, openflag, 0, curthread); + else if (!ocn_mute && cn_mute && cn_is_open) { + error = cnclose(NODEV, openflag, 0, curthread); + cn_is_open = 1; /* XXX hack */ } return (error); } SYSCTL_PROC(_kern, OID_AUTO, consmute, CTLTYPE_INT|CTLFLAG_RW, - 0, sizeof cn_mute, sysctl_kern_consmute, "I", ""); + 0, sizeof(cn_mute), sysctl_kern_consmute, "I", ""); static int -cnopen(dev, flag, mode, td) - dev_t dev; - int flag, mode; - struct thread *td; +cn_devopen(struct cn_device *cnd, struct thread *td, int forceopen) { - dev_t cndev, physdev; - int retval = 0; + char path[CNDEVPATHMAX]; + struct nameidata nd; + dev_t dev; + int error; - if (cn_tab == NULL || cn_phys_open == NULL) - return (0); - cndev = cn_tab->cn_dev; - physdev = (major(dev) == major(cndev) ? dev : cndev); - /* - * If mute is active, then non console opens don't get here - * so we don't need to check for that. They - * bypass this and go straight to the device. - */ - if(!cn_mute) - retval = (*cn_phys_open)(physdev, flag, mode, td); - if (retval == 0) { - /* - * check if we openned it via /dev/console or - * via the physical entry (e.g. /dev/sio0). - */ - if (dev == cndev) - cn_phys_is_open = 1; - else if (physdev == cndev) { - openmode = mode; - openflag = flag; - cn_is_open = 1; + if (cnd->cnd_vp != NULL) { + if (!forceopen) { + dev = cnd->cnd_vp->v_rdev; + return ((*devsw(dev)->d_open)(dev, openflag, 0, td)); } - dev->si_tty = physdev->si_tty; + vn_close(cnd->cnd_vp, openflag, td->td_proc->p_ucred, td); + cnd->cnd_vp = NULL; + } + if (cnd->cnd_name[0] == '\0') + strncpy(cnd->cnd_name, devtoname(cnd->cnd_cn->cn_dev), + sizeof(cnd->cnd_name)); + snprintf(path, sizeof(path), "/dev/%s", cnd->cnd_name); + NDINIT(&nd, LOOKUP, FOLLOW, UIO_SYSSPACE, path, td); + error = vn_open(&nd, &openflag, 0); + if (error == 0) { + NDFREE(&nd, NDF_ONLY_PNBUF); + VOP_UNLOCK(nd.ni_vp, 0, td); + if (nd.ni_vp->v_type == VCHR) + cnd->cnd_vp = nd.ni_vp; + else + vn_close(nd.ni_vp, openflag, td->td_proc->p_ucred, td); } - return (retval); + return (cnd->cnd_vp != NULL); } static int -cnclose(dev, flag, mode, td) - dev_t dev; - int flag, mode; - struct thread *td; +cnopen(dev_t dev, int flag, int mode, struct thread *td) { - dev_t cndev; - struct tty *cn_tp; + struct cn_device *cnd; - if (cn_tab == NULL || cn_phys_open == NULL) + openflag = flag; + cn_is_open = 1; /* console is logically open */ + if (cn_mute) return (0); - cndev = cn_tab->cn_dev; - cn_tp = cndev->si_tty; - /* - * act appropriatly depending on whether it's /dev/console - * or the pysical device (e.g. /dev/sio) that's being closed. - * in either case, don't actually close the device unless - * both are closed. - */ - if (dev == cndev) { - /* the physical device is about to be closed */ - cn_phys_is_open = 0; - if (cn_is_open) { - if (cn_tp) { - /* perform a ttyhalfclose() */ - /* reset session and proc group */ - cn_tp->t_pgrp = NULL; - cn_tp->t_session = NULL; - } - return (0); - } - } else if (major(dev) != major(cndev)) { - /* the logical console is about to be closed */ - cn_is_open = 0; - if (cn_phys_is_open) - return (0); - dev = cndev; + STAILQ_FOREACH(cnd, &cn_devlist, cnd_next) + cn_devopen(cnd, td, 0); + return (0); +} + +static int +cnclose(dev_t dev, int flag, int mode, struct thread *td) +{ + struct cn_device *cnd; + + STAILQ_FOREACH(cnd, &cn_devlist, cnd_next) { + if (cnd->cnd_vp == NULL) + continue; + vn_close(cnd->cnd_vp, mode, td->td_proc->p_ucred, td); + cnd->cnd_vp = NULL; } - if(cn_phys_close) - return ((*cn_phys_close)(dev, flag, mode, td)); + cn_is_open = 0; return (0); } static int -cnread(dev, uio, flag) - dev_t dev; - struct uio *uio; - int flag; +cnread(dev_t dev, struct uio *uio, int flag) { + struct cn_device *cnd; - if (cn_tab == NULL || cn_phys_open == NULL) + cnd = STAILQ_FIRST(&cn_devlist); + if (cn_mute || CND_INVALID(cnd, curthread)) return (0); - dev = cn_tab->cn_dev; + dev = cnd->cnd_vp->v_rdev; return ((*devsw(dev)->d_read)(dev, uio, flag)); } static int -cnwrite(dev, uio, flag) - dev_t dev; - struct uio *uio; - int flag; +cnwrite(dev_t dev, struct uio *uio, int flag) { + struct cn_device *cnd; - if (cn_tab == NULL || cn_phys_open == NULL) { - uio->uio_resid = 0; /* dump the data */ - return (0); - } + cnd = STAILQ_FIRST(&cn_devlist); + if (cn_mute || CND_INVALID(cnd, curthread)) + goto done; if (constty) dev = constty->t_dev; else - dev = cn_tab->cn_dev; - log_console(uio); - return ((*devsw(dev)->d_write)(dev, uio, flag)); + dev = cnd->cnd_vp->v_rdev; + if (dev != NULL) { + log_console(uio); + return ((*devsw(dev)->d_write)(dev, uio, flag)); + } +done: + uio->uio_resid = 0; /* dump the data */ + return (0); } static int -cnioctl(dev, cmd, data, flag, td) - dev_t dev; - u_long cmd; - caddr_t data; - int flag; - struct thread *td; +cnioctl(dev_t dev, u_long cmd, caddr_t data, int flag, struct thread *td) { + struct cn_device *cnd; int error; - if (cn_tab == NULL || cn_phys_open == NULL) + cnd = STAILQ_FIRST(&cn_devlist); + if (cn_mute || CND_INVALID(cnd, td)) return (0); /* * Superuser can always use this to wrest control of console @@ -382,82 +442,111 @@ constty = NULL; return (0); } - dev = cn_tab->cn_dev; - return ((*devsw(dev)->d_ioctl)(dev, cmd, data, flag, td)); + dev = cnd->cnd_vp->v_rdev; + if (dev != NULL) + return ((*devsw(dev)->d_ioctl)(dev, cmd, data, flag, td)); + return (0); } +/* + * XXX + * poll/kqfilter do not appear to be correct + */ static int -cnpoll(dev, events, td) - dev_t dev; - int events; - struct thread *td; +cnpoll(dev_t dev, int events, struct thread *td) { - if ((cn_tab == NULL) || cn_mute) - return (1); - - dev = cn_tab->cn_dev; + struct cn_device *cnd; - return ((*devsw(dev)->d_poll)(dev, events, td)); + cnd = STAILQ_FIRST(&cn_devlist); + if (cn_mute || CND_INVALID(cnd, td)) + return (0); + dev = cnd->cnd_vp->v_rdev; + if (dev != NULL) + return ((*devsw(dev)->d_poll)(dev, events, td)); + return (0); } static int -cnkqfilter(dev, kn) - dev_t dev; - struct knote *kn; +cnkqfilter(dev_t dev, struct knote *kn) { - if ((cn_tab == NULL) || cn_mute) - return (1); + struct cn_device *cnd; - dev = cn_tab->cn_dev; - if (devsw(dev)->d_flags & D_KQFILTER) + cnd = STAILQ_FIRST(&cn_devlist); + if (cn_mute || CND_INVALID(cnd, curthread)) + return (1); + dev = cnd->cnd_vp->v_rdev; + if (dev != NULL) return ((*devsw(dev)->d_kqfilter)(dev, kn)); return (1); } +/* + * Low level console routines. + */ int -cngetc() +cngetc(void) { int c; - if ((cn_tab == NULL) || cn_mute) + + if (cn_mute) return (-1); - c = (*cn_tab->cn_getc)(cn_tab->cn_dev); - if (c == '\r') c = '\n'; /* console input is always ICRNL */ + while ((c = cncheckc()) == -1) + ; + if (c == '\r') + c = '\n'; /* console input is always ICRNL */ return (c); } int -cncheckc() +cncheckc(void) { - if ((cn_tab == NULL) || cn_mute) + struct cn_device *cnd; + struct consdev *cn; + int c; + + if (cn_mute) return (-1); - return ((*cn_tab->cn_checkc)(cn_tab->cn_dev)); + STAILQ_FOREACH(cnd, &cn_devlist, cnd_next) { + cn = cnd->cnd_cn; + c = cn->cn_checkc(cn->cn_dev); + if (c != -1) { + return (c); + } + } + return (-1); } void -cnputc(c) - register int c; +cnputc(int c) { - if ((cn_tab == NULL) || cn_mute) + struct cn_device *cnd; + struct consdev *cn; + + if (cn_mute || c == '\0') return; - if (c) { + STAILQ_FOREACH(cnd, &cn_devlist, cnd_next) { + cn = cnd->cnd_cn; if (c == '\n') - (*cn_tab->cn_putc)(cn_tab->cn_dev, '\r'); - (*cn_tab->cn_putc)(cn_tab->cn_dev, c); + cn->cn_putc(cn->cn_dev, '\r'); + cn->cn_putc(cn->cn_dev, c); } } void -cndbctl(on) - int on; +cndbctl(int on) { + struct cn_device *cnd; + struct consdev *cn; static int refcount; - if (cn_tab == NULL) - return; if (!on) refcount--; - if (refcount == 0 && cn_tab->cn_dbctl != NULL) - (*cn_tab->cn_dbctl)(cn_tab->cn_dev, on); + if (refcount == 0) + STAILQ_FOREACH(cnd, &cn_devlist, cnd_next) { + cn = cnd->cnd_cn; + if (cn->cn_dbctl != NULL) + cn->cn_dbctl(cn->cn_dev, on); + } if (on) refcount++; } Index: sys/conf.h =================================================================== RCS file: /ncvs/src/sys/sys/conf.h,v retrieving revision 1.135 diff -u -r1.135 conf.h --- sys/conf.h 2001/10/17 18:47:12 1.135 +++ sys/conf.h 2001/10/19 16:04:51 @@ -60,6 +60,8 @@ #define SI_NAMED 0x0004 /* make_dev{_alias} has been called */ #define SI_CHEAPCLONE 0x0008 /* can be removed_dev'ed when vnode reclaims */ #define SI_CHILD 0x0010 /* child of another dev_t */ +#define SI_DEVOPEN 0x0020 /* opened by device */ +#define SI_CONSOPEN 0x0040 /* opened by console */ struct timespec si_atime; struct timespec si_ctime; struct timespec si_mtime; Index: sys/cons.h =================================================================== RCS file: /ncvs/src/sys/sys/cons.h,v retrieving revision 1.25 diff -u -r1.25 cons.h --- sys/cons.h 2001/06/13 10:58:39 1.25 +++ sys/cons.h 2001/09/27 02:25:27 @@ -78,8 +78,7 @@ #define CN_REMOTE 3 /* serial interface with remote bit set */ #ifdef _KERNEL -extern int cons_unavail; -extern struct consdev *cn_tab; +extern int cons_unavail; #define CONS_DRIVER(name, probe, init, term, getc, checkc, putc, dbctl) \ static struct consdev name##_consdev = { \ @@ -88,12 +87,14 @@ DATA_SET(cons_set, name##_consdev) /* Other kernel entry points. */ -int cncheckc __P((void)); -int cngetc __P((void)); -void cninit __P((void)); -void cninit_finish __P((void)); -void cndbctl __P((int)); -void cnputc __P((int)); +void cninit(void); +int cnadd(struct consdev *); +void cnremove(struct consdev *); +void cnselect(struct consdev *); +int cncheckc(void); +int cngetc(void); +void cndbctl(int); +void cnputc(int); #endif /* _KERNEL */ Index: sys/reboot.h =================================================================== RCS file: /ncvs/src/sys/sys/reboot.h,v retrieving revision 1.18 diff -u -r1.18 reboot.h --- sys/reboot.h 1999/08/28 00:51:58 1.18 +++ sys/reboot.h 2001/10/19 06:36:45 @@ -61,6 +61,7 @@ #define RB_GDB 0x8000 /* use GDB remote debugger instead of DDB */ #define RB_MUTE 0x10000 /* Come up with the console muted */ #define RB_SELFTEST 0x20000 /* don't boot to normal operation, do selftest */ +#define RB_MULTIPLE 0x20000000 /* Use multiple consoles */ #define RB_BOOTINFO 0x80000000 /* have `struct bootinfo *' arg */ Index: isa/sio.c =================================================================== RCS file: /ncvs/src/sys/isa/sio.c,v retrieving revision 1.347 diff -u -r1.347 sio.c --- isa/sio.c 2001/09/29 04:49:11 1.347 +++ isa/sio.c 2001/10/20 02:24:30 @@ -2922,13 +2922,14 @@ #else static cn_probe_t siocnprobe; static cn_init_t siocninit; +static cn_term_t siocnterm; #endif static cn_checkc_t siocncheckc; static cn_getc_t siocngetc; static cn_putc_t siocnputc; #ifndef __alpha__ -CONS_DRIVER(sio, siocnprobe, siocninit, NULL, siocngetc, siocncheckc, +CONS_DRIVER(sio, siocnprobe, siocninit, siocnterm, siocngetc, siocncheckc, siocnputc, NULL); #endif @@ -3178,6 +3179,13 @@ struct consdev *cp; { comconsole = DEV_TO_UNIT(cp->cn_dev); +} + +static void +siocnterm(cp) + struct consdev *cp; +{ + comconsole = -1; } #endif Index: i386//i386/autoconf.c =================================================================== RCS file: /ncvs/src/sys/i386/i386/autoconf.c,v retrieving revision 1.158 diff -u -r1.158 autoconf.c --- i386//i386/autoconf.c 2001/09/18 23:31:29 1.158 +++ i386//i386/autoconf.c 2001/09/22 00:38:09 @@ -176,7 +176,7 @@ { int i; - cninit_finish(); +/* cninit_finish(); */ if (bootverbose) { Index: boot/i386/boot2/boot2.c =================================================================== RCS file: /ncvs/src/sys/boot/i386/boot2/boot2.c,v retrieving revision 1.32 diff -u -r1.32 boot2.c --- boot/i386/boot2/boot2.c 2001/07/31 19:50:09 1.32 +++ boot/i386/boot2/boot2.c 2001/10/19 06:37:45 @@ -49,7 +49,7 @@ #define RBX_DUAL 0x1d /* -D */ #define RBX_PROBEKBD 0x1e /* -P */ -#define RBX_MASK 0xffff +#define RBX_MASK 0x2000ffff #define PATH_CONFIG "/boot.config" #define PATH_BOOT3 "/boot/loader" Index: boot/i386/libi386/bootinfo.c =================================================================== RCS file: /ncvs/src/sys/boot/i386/libi386/bootinfo.c,v retrieving revision 1.28 diff -u -r1.28 bootinfo.c --- boot/i386/libi386/bootinfo.c 2001/02/18 10:25:41 1.28 +++ boot/i386/libi386/bootinfo.c 2001/10/19 06:30:27 @@ -88,6 +88,9 @@ case 'd': howto |= RB_KDB; break; + case 'D': + howto |= RB_MULTIPLE; + break; case 'm': howto |= RB_MUTE; break; ---------------------------------- cut here ---------------------------------- # $FreeBSD$ PROG= conscontrol MAN= conscontrol.8 .include ---------------------------------- cut here ---------------------------------- #include #include #include #include #include #include static void __dead2 usage(void) { const char *pname = getprogname(); fprintf(stderr, "usage: %s [list]\n", pname); fprintf(stderr, " %s mute on|off\n", pname); fprintf(stderr, " %s add|delete console\n", pname); exit(1); } #define CONSBUFSIZE 32 static void constatus(void) { int mute; size_t len; char *buf, *p, *avail; len = sizeof(mute); if (sysctlbyname("kern.consmute", &mute, &len, NULL, 0) == -1) goto fail; len = 0; alloc: len += CONSBUFSIZE; buf = malloc(len); if (buf == NULL) err(1, "Could not malloc sysctl buffer"); if (sysctlbyname("kern.console", buf, &len, NULL, 0) == -1) { if (errno == ENOMEM) { free(buf); goto alloc; } goto fail; } avail = strchr(buf, '/'); p = avail; *avail++ = '\0'; if (p != buf) *--p = '\0'; /* remove trailing ',' */ p = avail + strlen(avail); if (p != avail) *--p = '\0'; /* remove trailing ',' */ printf("Configured: %s\n", buf); printf(" Available: %s\n", avail); printf(" Muting: %s\n", mute ? "on" : "off"); free(buf); return; fail: err(1, "Could not get console information"); } static void consmute(const char *onoff) { int mute; size_t len; if (strcmp(onoff, "on") == 0) mute = 1; else if (strcmp(onoff, "off") == 0) mute = 0; else usage(); len = sizeof(mute); if (sysctlbyname("kern.consmute", NULL, NULL, &mute, len) == -1) err(1, "Could not change console muting"); } static void consadd(char *devname) { size_t len; len = strlen(devname); if (sysctlbyname("kern.console", NULL, NULL, devname, len) == -1) err(1, "Could not add %s as a console", devname); } #define MAXDEVNAME 32 static void consdel(const char *devname) { char buf[MAXDEVNAME]; size_t len; snprintf(buf, MAXDEVNAME, "-%s", devname); len = strlen(buf); if (sysctlbyname("kern.console", NULL, NULL, &buf, len) == -1) err(1, "Could not remove %s as a console", devname); } int main(int argc, char **argv) { if (argc < 2 || strcmp(argv[1], "list") == 0) goto done; if (argc < 3) usage(); if (strcmp(argv[1], "mute") == 0) consmute(argv[2]); else if (strcmp(argv[1], "add") == 0) consadd(argv[2]); else if (strcmp(argv[1], "delete") == 0) consdel(argv[2]); else usage(); done: constatus(); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 20 13:53:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id C303337B40A for ; Sat, 20 Oct 2001 13:53:53 -0700 (PDT) Received: from onyx (onyx.cs.binghamton.edu [128.226.140.171]) by bingnet2.cc.binghamton.edu (8.11.6/8.11.6) with ESMTP id f9KKrq506631 for ; Sat, 20 Oct 2001 16:53:52 -0400 (EDT) Date: Sat, 20 Oct 2001 16:52:57 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@onyx To: freebsd-hackers@freebsd.org Subject: where are kernel modules located? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kernel modules are supposed to locate under /modules. It turns out we can find it under /. So where are kernel models located exactly? Thanks, -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 20 14:29:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 3E84D37B403 for ; Sat, 20 Oct 2001 14:29:54 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f9KLTqV36218; Sat, 20 Oct 2001 15:29:52 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f9KLTp749148; Sat, 20 Oct 2001 15:29:51 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110202129.f9KLTp749148@harmony.village.org> To: Zhihui Zhang Subject: Re: where are kernel modules located? Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 20 Oct 2001 16:52:57 EDT." References: Date: Sat, 20 Oct 2001 15:29:51 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message Zhihui Zhang writes: : Kernel modules are supposed to locate under /modules. It turns out we can : find it under /. So where are kernel models located exactly? In -stable it is /modules (except for about 8 hours in the last few days when they bogusly wound up in / due to a foobar by yours truly). In current they live in /boot/kernel/*. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 20 14:31:28 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 C44C637B405; Sat, 20 Oct 2001 14:31:22 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 689DB14C2E; Sat, 20 Oct 2001 15:54:14 +0200 (CEST) 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: Robert Watson Cc: Jim Pirzyk , freebsd-hackers@freebsd.org Subject: Re: truss vs ktrace References: From: Dag-Erling Smorgrav Date: 20 Oct 2001 15:54:13 +0200 In-Reply-To: Message-ID: Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Robert Watson writes: > There are a fair number of differences, but from my perspective, one of > the primary ones is that truss relies on procfs, Truss could be easily be rewritten to use ptrace() instead of procfs. It'd be a lot slower though, because ptrace() can only return one int at a time from process memory whereas with /proc/pid/mem you can read as much as you want in one go. 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 Oct 20 14:41:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kitkat.hotpop.com (kitkat.hotpop.com [204.57.55.30]) by hub.freebsd.org (Postfix) with ESMTP id 6B5E437B405 for ; Sat, 20 Oct 2001 14:41:24 -0700 (PDT) Received: from hotpop.com (unknown [204.57.55.31]) by kitkat.hotpop.com (Postfix) with SMTP id 1A089308C6 for ; Sat, 20 Oct 2001 21:41:13 +0000 (UTC) Received: from hotpop.com (shiva-dhcp-101.dial.upmc.edu [128.147.34.101]) by zagnut.hotpop.com (Postfix) with SMTP id 755CD50014 for ; Sat, 20 Oct 2001 21:40:04 +0000 (UTC) Date: Sat, 20 Oct 2001 17:35:45 -0400 From: Rod Person To: Hackers FreeBSD Subject: bash scripting help/suggestions. Message-Id: <20011020173545.6cf189ff.roddierod@hotpop.com> Reply-To: roddierod@hotpop.com Organization: Open Source Beef X-Mailer: Sylpheed version 0.6.1 (GTK+ 1.2.8; i386--freebsd4.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-HotPOP: ----------------------------------------------- Sent By HotPOP.com FREE Email Get your FREE POP email at www.HotPOP.com ----------------------------------------------- Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm creating a bash script and I need to know if a directory exists and if it doesn't create it. So far the only why I can see to determine if a directory exists is to try to cd to it and if it doesn't exists trap the error. Is there a better way or a function that I am missing? If not how do you trap a error in bash, if at all possible. Rod http://storm.prohosting.com/osbeef/osbeef.htm '....musical rhythms can mess with your head...' - T La Rock "It's your's" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 20 14:44:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id D2CA937B401 for ; Sat, 20 Oct 2001 14:44:46 -0700 (PDT) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id f9KLiUo00609; Sat, 20 Oct 2001 23:44:30 +0200 (CEST) (envelope-from wkb) Date: Sat, 20 Oct 2001 23:44:30 +0200 From: Wilko Bulte To: Rod Person Cc: Hackers FreeBSD Subject: Re: bash scripting help/suggestions. Message-ID: <20011020234430.A568@freebie.xs4all.nl> References: <20011020173545.6cf189ff.roddierod@hotpop.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011020173545.6cf189ff.roddierod@hotpop.com>; from roddierod@hotpop.com on Sat, Oct 20, 2001 at 05:35:45PM -0400 X-OS: FreeBSD 4.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Oct 20, 2001 at 05:35:45PM -0400, Rod Person wrote: man test(1) tells you how to check for a directory (and lots more BTW) mkdir -p might also interest you (see the mkdir man page) > I'm creating a bash script and I need to know if a directory exists and if it doesn't create it. So far the only why I can see to determine if a directory exists is to try to cd to it and if it doesn't exists trap the error. Is there a better way or a function that I am missing? If not how do you trap a error in bash, if at all possible. > > Rod > > http://storm.prohosting.com/osbeef/osbeef.htm > > '....musical rhythms can mess with your head...' > - T La Rock > "It's your's" > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message ---end of quoted text--- -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 20 14:48:45 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 65FF537B403 for ; Sat, 20 Oct 2001 14:48:42 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 47D8F14C2E; Sat, 20 Oct 2001 23:48:41 +0200 (CEST) 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: Arun Sharma Cc: hackers@freebsd.org Subject: Re: truss vs ktrace References: <3BCCCF74.75B7F36C@disney.com> <20011020182451.EC4E95E594@sharmas.dhs.org> From: Dag-Erling Smorgrav Date: 20 Oct 2001 23:48:40 +0200 In-Reply-To: <20011020182451.EC4E95E594@sharmas.dhs.org> Message-ID: Lines: 10 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Arun Sharma writes: > Another advantage of truss is that the output is "online" and interactive. > ktrace requires you to use kdump to view the trace. I certainly wouldn't call truss "interactive". As for "online", see the -l command-line option to kdump. 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 Oct 20 14:51:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kitkat.hotpop.com (kitkat.hotpop.com [204.57.55.30]) by hub.freebsd.org (Postfix) with ESMTP id BDE2037B401 for ; Sat, 20 Oct 2001 14:51:47 -0700 (PDT) Received: from hotpop.com (unknown [204.57.55.31]) by kitkat.hotpop.com (Postfix) with SMTP id 37E4B309A9 for ; Sat, 20 Oct 2001 21:51:20 +0000 (UTC) Received: from hotpop.com (shiva-dhcp-101.dial.upmc.edu [128.147.34.101]) by zagnut.hotpop.com (Postfix) with SMTP id 5E60450022; Sat, 20 Oct 2001 21:51:20 +0000 (UTC) Date: Sat, 20 Oct 2001 17:47:01 -0400 From: Rod Person To: Wilko Bulte Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bash scripting help/suggestions. Message-Id: <20011020174701.7a8f156a.roddierod@hotpop.com> In-Reply-To: <20011020234430.A568@freebie.xs4all.nl> References: <20011020173545.6cf189ff.roddierod@hotpop.com> <20011020234430.A568@freebie.xs4all.nl> Reply-To: roddierod@hotpop.com Organization: Open Source Beef X-Mailer: Sylpheed version 0.6.1 (GTK+ 1.2.8; i386--freebsd4.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-HotPOP: ----------------------------------------------- Sent By HotPOP.com FREE Email Get your FREE POP email at www.HotPOP.com ----------------------------------------------- Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks. That exactly what I needed. It was Sat, 20 Oct 2001 23:44:30 +0200 and I don't really know but somebody said: > On Sat, Oct 20, 2001 at 05:35:45PM -0400, Rod Person wrote: > > man test(1) tells you how to check for a directory (and lots more BTW) > > mkdir -p might also interest you (see the mkdir man page) > > > I'm creating a bash script and I need to know if a directory exists > and if it doesn't create it. So far the only why I can see to determine > if a directory exists is to try to cd to it and if it doesn't exists > trap the error. Is there a better way or a function that I am missing? > If not how do you trap a error in bash, if at all possible. > > > > Rod > > > > http://storm.prohosting.com/osbeef/osbeef.htm > > > > '....musical rhythms can mess with your head...' > > - T La Rock > > "It's your's" > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > ---end of quoted text--- > > -- > | / o / /_ _ email: wilko@FreeBSD.org > |/|/ / / /( (_) Bulte Arnhem, The Netherlands Rod http://storm.prohosting.com/osbeef/osbeef.htm '....musical rhythms can mess with your head...' - T La Rock "It's your's" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 20 15: 3:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from saruman.xwin.net (saruman.xwin.net [205.219.158.250]) by hub.freebsd.org (Postfix) with ESMTP id 21FA337B405 for ; Sat, 20 Oct 2001 15:03:16 -0700 (PDT) Received: from localhost (dp@localhost) by saruman.xwin.net (8.11.4/8.9.1) with ESMTP id f9KH3c720586; Sat, 20 Oct 2001 12:03:38 -0500 Date: Sat, 20 Oct 2001 12:03:38 -0500 (CDT) From: Paul Halliday X-X-Sender: To: Rod Person Cc: Hackers FreeBSD Subject: Re: bash scripting help/suggestions. In-Reply-To: <20011020173545.6cf189ff.roddierod@hotpop.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG on Sat, 20 Oct 2001, Rod Person wrote: > I'm creating a bash script and I need to know if a directory exists > and if it doesn't create it. So far the only why I can see to > determine if a directory exists is to try to cd to it and if it > doesn't exists trap the error. Is there a better way or a function > that I am missing? If not how do you trap a error in bash, if at all if [ -d $dir ]; then ; else mkdir $dir; fi > possible. > > Rod > > http://storm.prohosting.com/osbeef/osbeef.htm > > '....musical rhythms can mess with your head...' > - T La Rock > "It's your's" > > > 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" ___________________ http://dp.penix.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message