From owner-freebsd-stable Sun Jan 30 10:35: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id 4B2F5151BD for ; Sun, 30 Jan 2000 10:34:58 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id LAA10892; Sun, 30 Jan 2000 11:34:49 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id LAA13968; Sun, 30 Jan 2000 11:34:48 -0700 (MST) (envelope-from nate) Date: Sun, 30 Jan 2000 11:34:48 -0700 (MST) Message-Id: <200001301834.LAA13968@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: William Woods Cc: Coleman Kane , freebsd-stable@FreeBSD.ORG, Doug White Subject: Re: FW: DSL natd rules.... In-Reply-To: References: <20000130012354.A86581@evil.2y.net> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, > USWEST says the 675 needs to be in PPP mode and not bridged. I have the 675's > manuals and have been reading them. LIke I said, I have NAT from the 675 to the > router/gateway (Not running a server) and on the gateway/router I am useing > ipfw and natd to the internal LAN. > > Is this not a viable solution? > > On 30-Jan-00 Coleman Kane wrote: > > Doug White had the audacity to say: > >> On Sat, 29 Jan 2000, William Woods wrote: > >> > >> > Hmmm.... > >> > > >> > Well I was planning on running NAT from the cisco to the FreeBSD > >> > router/gateway/firewall and then NATD on the router gateway to deliver to > >> > the > >> > rest of the LAN. This is a bad thing I take it? Let me jump in and state that this is what I did (exact same setup, U.S. West, 675, FreeBSD), and it worked great. However, I switched to a different ISP since they allowed me to have my own block of addresses for a much cheaper price than what U.S. West charged, plus they have a more 'stable' network connection. The original configuration worked well, and I don't think you would notice any problems using the double-NAT configuration whatsoever, although you could simply hook all your boxs directly to the Cisco and use it that way instead, which may be easier for you. The NAT implementation on the cisco seemed to work quite well... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 12:14:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 8185E15060 for ; Sun, 30 Jan 2000 12:14:48 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@pm3b-18.cybcon.com [205.147.75.83]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id MAA08489; Sun, 30 Jan 2000 12:15:00 -0800 (PST) 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: <200001301834.LAA13968@nomad.yogotech.com> Date: Sun, 30 Jan 2000 12:10:10 -0800 (PST) From: William Woods To: Nate Williams Subject: Re: FW: DSL natd rules.... Cc: Doug White , freebsd-stable@FreeBSD.ORG, Coleman Kane Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The original configuration worked well, and I don't think you would > notice any problems using the double-NAT configuration whatsoever, > although you could simply hook all your boxs directly to the Cisco and > use it that way instead, which may be easier for you. > > The NAT implementation on the cisco seemed to work quite well... I would but I want the FreeBSD box to be a firewall for the LAN > > Nate ---------------------------------- E-Mail: William Woods Date: 30-Jan-00 Time: 12:08:51 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 14:30:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id DB3E815E16 for ; Sun, 30 Jan 2000 14:30:40 -0800 (PST) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id PAA12669; Sun, 30 Jan 2000 15:30:31 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id PAA14563; Sun, 30 Jan 2000 15:30:30 -0700 (MST) (envelope-from nate) Date: Sun, 30 Jan 2000 15:30:30 -0700 (MST) Message-Id: <200001302230.PAA14563@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: William Woods Cc: Nate Williams , Doug White , freebsd-stable@FreeBSD.ORG, Coleman Kane Subject: Re: FW: DSL natd rules.... In-Reply-To: References: <200001301834.LAA13968@nomad.yogotech.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The original configuration worked well, and I don't think you would > > notice any problems using the double-NAT configuration whatsoever, > > although you could simply hook all your boxs directly to the Cisco and > > use it that way instead, which may be easier for you. > > > > The NAT implementation on the cisco seemed to work quite well... > > I would but I want the FreeBSD box to be a firewall for the LAN Shouldn't be necessary with NAT on the Cisco. No-one can connect into any internal interfaces because of NAT. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 14:34:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id B783E14D1F for ; Sun, 30 Jan 2000 14:34:37 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@pm3a-41.cybcon.com [205.147.75.170]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id OAA19274; Sun, 30 Jan 2000 14:34:32 -0800 (PST) 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: <200001302230.PAA14563@nomad.yogotech.com> Date: Sun, 30 Jan 2000 14:29:32 -0800 (PST) From: William Woods To: Nate Williams Subject: Re: FW: DSL natd rules.... Cc: Coleman Kane , freebsd-stable@FreeBSD.ORG, Doug White Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, I am a bit confused here, I have herd that I CAN use NAT on the cisco to th the gateway/firewall/router(FreeBSD box) and then I Can't use nat on cisco to firewall if I am going to use natd on the FreeBSD box.... Which is it? On 30-Jan-00 Nate Williams wrote: >> > The original configuration worked well, and I don't think you would >> > notice any problems using the double-NAT configuration whatsoever, >> > although you could simply hook all your boxs directly to the Cisco and >> > use it that way instead, which may be easier for you. >> > >> > The NAT implementation on the cisco seemed to work quite well... >> >> I would but I want the FreeBSD box to be a firewall for the LAN > > Shouldn't be necessary with NAT on the Cisco. No-one can connect into > any internal interfaces because of NAT. > > > Nate ---------------------------------- E-Mail: William Woods Date: 30-Jan-00 Time: 14:27:51 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 15: 2: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 411A11519B; Sun, 30 Jan 2000 15:02:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 32A4C1CD81B; Sun, 30 Jan 2000 15:02:05 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 30 Jan 2000 15:02:05 -0800 (PST) From: Kris Kennaway To: Kenneth W Cochran Cc: John Polstra , stable@freebsd.org Subject: Re: Tracking updates to FreeBSD In-Reply-To: <200001300220.VAA24481@world.std.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Jan 2000, Kenneth W Cochran wrote: > Same here; the volume on cvs-all strikes me as a little much > (almost overwhelming) unless I were, for example, a committer. > I'm very glad cvs-all exists; it just seems more than *I* need > most of the time. Use a procmail filter and filter out everything which isn't in the RELENG_3 branch. There are usually less than 200 messages per day on the cvs-all list. If you can't handle that amount of traffic, what are you doing on the internet? :-) > What he said... :) I was wondering if there is some way I can > access some kind of "change-log," perhaps via Web or ftp. This > might help me decide when I might want to perform maintenance > (cvsup/make {build,install}world). There's the archived commit logs, but that's the same thing you'd be getting on the cvs-all mailing list, without the ability to filter out the non-RELENG_3 commits. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 15:11:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id 6EC1B14ED8 for ; Sun, 30 Jan 2000 15:11:54 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id QAA17314; Sun, 30 Jan 2000 16:05:41 -0700 (MST) Date: Sun, 30 Jan 2000 16:05:40 -0700 (MST) From: "Forrest W. Christian" To: William Woods Cc: Nate Williams , Coleman Kane , freebsd-stable@FreeBSD.ORG, Doug White Subject: Re: FW: DSL natd rules.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, William Woods wrote: > OK, I am a bit confused here, I have herd that I CAN use NAT on the cisco to th > the gateway/firewall/router(FreeBSD box) and then I Can't use nat on cisco to > firewall if I am going to use natd on the FreeBSD box.... Let me see If I can straigten out your assumptions here. Let's first talk about the 675 and what It can do by itself. If that's all you need then why complicate the issue with natd? The 675 runs what is called CBOS. CBOS includes BOTH NAT and Filtering capabilities. Or, in other words, exactly what natd/ipfw does on FreeBSD. In a "normal" environment you would set the 675 to NAT mode and plug it directly into your internal network. You would probably also configure some security-related things like a password, etc. If you are paranoid, you can also set up additional filters. In addition, if you have a static outside IP you can also turn on what I call "static port/address translation", or in other words, re-route inbound traffic destined for a specific protocol/ip to the inside world. (I.E. all inbound mail traffic goes toward a mail server) Unfortunately, this doesn't appear to support a dynamic IP, although CBOS might be smarter than I'm giving it credit for. You can also turn on PPP bridging which basically takes the IP frames and stuffs them out on the ethernet. I can't vouch for how well this works. I can't see how this would work well at all in the dynamic IP world. Athough, if you really wanted to do natd/ipfw on the freebsd box and you had a static IP address this should work well. In essence, you (should) be able to assign your static IP to the outside interface of your FreeBSD box. Again, I can't vouch for this or to how well it works, and it seems likely to not work very well. Now, onto the FreeBSD box. If you really want to go through natd/ipfw (I don't believe there is any security benefits of doing so). Then, you should just be able to plug the FreeBSD box into the 675 and configure natd like normal. Everything should work just fine. However, if you have a static IP and you would like to say recieve inbound mail on port 25, you will need to set up the nat rules on BOTH the 675 and the FreeBSD box. In essense you become "double firewalled" and as such everything has to be checked by both. Unless you have a specific reason not to do so, I would just plug the 675 into your internal lan and be done with it. The only probable exception to that is if you have a static IP and would like to try and see if you can make the ppp bridging work. For your reference, the manuals for the 675 are at: http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/c600s/index.htm You will want to click on the "Cisco Broadband Operating System (CBOS)" link to get to the "real" configuration manual. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 16:40:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from server.hmm.za.net (admin.bsdonline.org [196.28.82.142]) by hub.freebsd.org (Postfix) with ESMTP id 8A14214F02 for ; Sun, 30 Jan 2000 16:40:28 -0800 (PST) (envelope-from david@campsbay.za.net) Received: from DAVID (david [192.168.1.2]) by server.hmm.za.net (8.9.3/8.9.3) with SMTP id CAA55514 for ; Mon, 31 Jan 2000 02:34:02 +0200 (SAST) (envelope-from david@campsbay.za.net) Message-ID: <003e01bf6b84$1ed6ec40$0201a8c0@DAVID> From: "D VAN" To: Subject: Date: Mon, 31 Jan 2000 02:42:55 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG im sure everyone has heard about the 3.4 /proc problem! anyone here know when or if it has been fixed in the cvs so that i can cvsup _STABLE_ and be safe ? Thank you _________________________ David van Rensburg aka Van from Johan* david@van.web.za FreeBSD: The Power to Serve www.freebsd.org __ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 16:54:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 7DCB514D6A; Sun, 30 Jan 2000 16:54:29 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6E3701CD402; Sun, 30 Jan 2000 16:54:29 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 30 Jan 2000 16:54:29 -0800 (PST) From: Kris Kennaway To: D VAN Cc: stable@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <003e01bf6b84$1ed6ec40$0201a8c0@DAVID> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, D VAN wrote: > im sure everyone has heard about the 3.4 /proc problem! > anyone here know when or if it has been fixed in the cvs so that i can cvsup > _STABLE_ and be safe ? Please see the security advisory on the website. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 18:47:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from laker.net (discover.laker.net [205.245.74.3]) by hub.freebsd.org (Postfix) with ESMTP id 4320D14DC3 for ; Sun, 30 Jan 2000 18:47:06 -0800 (PST) (envelope-from gabriel@laker.net) Received: (from gabriel@localhost) by laker.net (8.9.1/8.9.1-LAKERNET+8.9.1-MOD) id VAA16477 for freebsd-stable@freebsd.org; Sun, 30 Jan 2000 21:47:04 -0500 From: Gabriel Message-Id: <200001310247.VAA16477@laker.net> Subject: Adaptec 29160 Support? To: freebsd-stable@freebsd.org Date: Sun, 30 Jan 100 21:47:04 -0500 (EST) Reply-To: gabriel@NOSPAMlaker.net Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am running 2.2.8-stable and wish to upgrade to 3.4-stable. I will need a new hard drive for the upgrade. I currently have an Adaptec 2940AU and a 9.1GB Ultra SCSI drive. I have yet to see any Ultra SCSI drivers larger then 9.1 GB (except for Seagate's 5400 RPM 50GB dinosaur, which I believe is a 5.25" drive?). Adaptec's 2940U2W looks like a good replacement for the 2940AU, but I would rather get their 29160. Will the 29160 series be supported in 3.x and 4.0 in the future? Thank you. -- gabriel@NOSPAMlaker.net remove NOSPAM to reply. ------------------------------------------------------------------------------ Windows 95/NT: 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. (UGU) Windows never crashes because I use FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 19: 6: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id 12FA914F8A for ; Sun, 30 Jan 2000 19:05:59 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id UAA18854; Sun, 30 Jan 2000 20:00:19 -0700 (MST) Date: Sun, 30 Jan 2000 20:00:15 -0700 (MST) From: "Forrest W. Christian" To: Coleman Kane Cc: Doug White , William Woods , freebsd-stable@FreeBSD.ORG Subject: Re: FW: DSL natd rules.... In-Reply-To: <20000130012354.A86581@evil.2y.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In my experiences and knowledge, the phone company's network does a lot of the > NAT and everything. Somewhere along the line your final output IP is bridged > with the ISP's IP to give to you. The NAT and routing is typically internal in > the phone company. Just to put my $0.02 in here. From experience with USWest DSL from both the customer and ISP end, I can guarantee that the phone company does very little to the ATM cells which go between the 675 and our equipment (ATM interface on a Cisco router). If we set the connection up PPP the client has to set it up PPP, if we set it up bridging, so does the client. We can (and do) at times push out a whole subnet bridged to the client end. I have yet to see anything which indicates that the telco does anything to the packets except take them in on the DSLAM and push them out our ATM port. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 19: 7:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7F76E14DAC for ; Sun, 30 Jan 2000 19:07:30 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA18352; Sun, 30 Jan 2000 20:06:47 -0700 (MST) (envelope-from ken) Date: Sun, 30 Jan 2000 20:06:46 -0700 From: "Kenneth D. Merry" To: Gabriel Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Adaptec 29160 Support? Message-ID: <20000130200646.A18269@panzer.kdm.org> References: <200001310247.VAA16477@laker.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001310247.VAA16477@laker.net>; from gabriel@laker.net on Sun, Jan 30, 2000 at 09:47:04PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 30, 2000 at 21:47:04 -0500, Gabriel wrote: > Hello, > > I am running 2.2.8-stable and wish to upgrade to 3.4-stable. I will need a > new hard drive for the upgrade. I currently have an Adaptec 2940AU and a 9.1GB > Ultra SCSI drive. I have yet to see any Ultra SCSI drivers larger then 9.1 > GB (except for Seagate's 5400 RPM 50GB dinosaur, which I believe is a 5.25" > drive?). Adaptec's 2940U2W looks like a good replacement for the 2940AU, > but I would rather get their 29160. Will the 29160 series be supported in > 3.x and 4.0 in the future? The Adaptec 29160 is supported in -current, although right now it will only run at Ultra2 speeds. (Ultra160 speeds will be enabled before too long.) It is not yet supported in -stable, although I'm sure it will be at some point. You can mail Justin Gibbs to inquire about when support might make it into -stable. As for drives, you're more than 2 years behind if you think that 9G drives are the best out there. All the major vendors are shipping 18G and 36G drives, and Seagate is even shipping a 50G Barracuda, which is a 3.5" half height drive, and runs at 7200rpm. The drive you're thinking of is likely Seagate's old 47G drive, which was indeed a 5400rpm full height 5.25" drive. If you're going to get a new drive, I'd suggest getting IBM or Seagate disks. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 19:40:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 29C7E14DD3 for ; Sun, 30 Jan 2000 19:40:32 -0800 (PST) (envelope-from carl@xena.aipo.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id OAA36198 for ; Mon, 31 Jan 2000 14:40:29 +1100 (EST) (envelope-from carl@xena.aipo.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma036188; Mon, 31 Jan 00 14:40:16 +1100 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.3) with ESMTP id OAA53633 for ; Mon, 31 Jan 2000 14:41:11 +1100 (EST) (envelope-from carl@xena.aipo.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Mon, 31 Jan 2000 14:41:11 +1100 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: stable@freebsd.org Subject: i810 Kernel module for XFree86 3.3.6. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anybody played around with porting the agpgart.o Linux kernel module to FreeBSD 3.4? Unfortunately I'm not up to the port myself however I'll help with testing it if anyone else is doing it! Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 19:49:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 23AF314D28 for ; Sun, 30 Jan 2000 19:49:48 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-8.cybcon.com [205.147.75.9]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id TAA10562; Sun, 30 Jan 2000 19:49:55 -0800 (PST) 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: Sun, 30 Jan 2000 19:45:05 -0800 (PST) From: William Woods To: "Forrest W. Christian" Subject: Re: FW: DSL natd rules.... Cc: freebsd-stable@FreeBSD.ORG, Doug White , Coleman Kane Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, what does this mean for me? On 31-Jan-00 Forrest W. Christian wrote: >> In my experiences and knowledge, the phone company's network does a lot of >> the >> NAT and everything. Somewhere along the line your final output IP is bridged >> with the ISP's IP to give to you. The NAT and routing is typically internal >> in >> the phone company. > > Just to put my $0.02 in here. > >>From experience with USWest DSL from both the customer and ISP end, I can > guarantee that the phone company does very little to the ATM cells which > go between the 675 and our equipment (ATM interface on a Cisco router). > > If we set the connection up PPP the client has to set it up PPP, if we set > it up bridging, so does the client. We can (and do) at times push out a > whole subnet bridged to the client end. > > I have yet to see anything which indicates that the telco does anything to > the packets except take them in on the DSLAM and push them out our ATM > port. > > - Forrest W. Christian (forrestc@imach.com) KD7EHZ > ---------------------------------------------------------------------- > iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com > Solutions for your high-tech problems. (406)-442-6648 > ---------------------------------------------------------------------- ---------------------------------- E-Mail: William Woods Date: 30-Jan-00 Time: 19:44:51 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 21:16:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from outlier.axl.net (outlier.axl.net [216.66.11.20]) by hub.freebsd.org (Postfix) with SMTP id 61B2F14F03 for ; Sun, 30 Jan 2000 21:16:07 -0800 (PST) (envelope-from matt@axl.net) Received: (qmail 20854 invoked from network); 31 Jan 2000 05:15:53 -0000 Received: from ws-01.matthennigus.lightningdsl.net (HELO sinister) (216.66.30.66) by outlier.axl.net with SMTP; 31 Jan 2000 05:15:53 -0000 Reply-To: From: "Matthew B. Henniges" To: "D VAN" , Subject: RE: Date: Mon, 31 Jan 2000 00:18:11 -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.2910.0) In-Reply-To: <003e01bf6b84$1ed6ec40$0201a8c0@DAVID> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is fixed in stable. I thought it had been fixed there on the 20th, but I verified that it was fixed in today's sup. Matthew B. Henniges Axl.net Communications http://www.axl.net (203) 552-1714 > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of D VAN > Sent: Sunday, January 30, 2000 7:43 PM > To: stable@FreeBSD.ORG > Subject: > > > im sure everyone has heard about the 3.4 /proc problem! > anyone here know when or if it has been fixed in the cvs so that > i can cvsup > _STABLE_ and be safe ? > > Thank you > > _________________________ > David van Rensburg > aka Van from Johan* > david@van.web.za > > FreeBSD: The Power to Serve > www.freebsd.org > __ > > > > 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-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 21:29:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 83D0B14CFC for ; Sun, 30 Jan 2000 21:29:34 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 12F9Oh-0002lQ-00; Sun, 30 Jan 2000 21:29:12 -0800 Date: Sun, 30 Jan 2000 21:29:06 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Daniel C. Sobral" Cc: Cy Schubert - ITSD Open Systems Group , Ataualpa Albert Carmo Braga , freebsd-stable@FreeBSD.ORG Subject: Re: JFS In-Reply-To: <3893D404.189AA11A@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, Daniel C. Sobral wrote: > > Due to the lack of interest, FreeBSD's LFS has fallen into disrepair > > over the years. With the implementation of softupdates in FreeBSD I > > don't think there is any need for LFS any more. > > Repeat that over and over the next time you wait fsck finish a 40 Gb > filesystem checkup, and see if you manage to convince yourself of that. Actually, one of the goals of the softupdates development is a fsck'less filesystem. I'm not sure how this is to be achieved. Probably a metadata journal, though that is just speculation. All the work on metadata update ordering in softupdates would probably apply very nicely to a journal. > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "If you consider our help impolite, you should see the manager." Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 22:26:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id E600214DFD for ; Sun, 30 Jan 2000 22:22:40 -0800 (PST) (envelope-from gjp@in-addr.com) Received: from localhost ([127.0.0.1] helo=in-addr.com) by noop.colo.erols.net with esmtp (Exim 3.12 #1) id 12FADj-000LZ7-00; Mon, 31 Jan 2000 01:21:55 -0500 To: Tom Cc: freebsd-stable@FreeBSD.ORG From: Gary Palmer Subject: Re: JFS In-Reply-To: Message from Tom of "Sun, 30 Jan 2000 21:29:06 PST." Date: Mon, 31 Jan 2000 01:21:45 -0500 Message-ID: <82900.949299705@in-addr.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom wrote in message ID : > On Sun, 30 Jan 2000, Daniel C. Sobral wrote: > > > > Due to the lack of interest, FreeBSD's LFS has fallen into disrepair > > > over the years. With the implementation of softupdates in FreeBSD I > > > don't think there is any need for LFS any more. > > > > Repeat that over and over the next time you wait fsck finish a 40 Gb > > filesystem checkup, and see if you manage to convince yourself of that. > > Actually, one of the goals of the softupdates development is a fsck'less > filesystem. I'm not sure how this is to be achieved. Probably a metadata > journal, though that is just speculation. All the work on metadata update > ordering in softupdates would probably apply very nicely to a journal. The way I understand it is that SoftUpdates is meant to leave the metadata consistant enough that the filesystem can be mounted read/write immediately at boot, and then have a background fsck go through and remove blocks which are allocated in the bitmaps, but aren't really used. The only thing you lose by not running the background daemon is space. I don't think anyone's running like this today, but that is Kirks plan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 30 23:22:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from everest.overx.com (everest.overx.com [63.82.145.202]) by hub.freebsd.org (Postfix) with ESMTP id D27A614E15 for ; Sun, 30 Jan 2000 23:22:18 -0800 (PST) (envelope-from dayton@overx.com) Received: from polo.overx.com (polo.overx.com [63.82.145.204]) by everest.overx.com (Postfix) with ESMTP id 290142007 for ; Mon, 31 Jan 2000 01:21:59 -0600 (CST) Received: by polo.overx.com (Postfix, from userid 1001) id E69273F01; Mon, 31 Jan 2000 01:22:01 -0600 (CST) From: Soren Dayton Reply-To: dayton@overx.com To: freebsd-stable@freebsd.org Subject: My sa0 stopped working on upgrade Date: 31 Jan 2000 01:22:01 -0600 Message-ID: <86ya9666zq.fsf@polo.overx.com> Lines: 30 User-Agent: Gnus/5.070099 (Pterodactyl Gnus v0.99) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I recently upgraded to -stable (from 3.2) to use some of the fixes to a variety of things like aio_* and some thread stuff. However, I appear to have botched something else entirely: my HP SCSI tape drive does not work. It is found (here's some dmesg output): sa0 at ahc0 bus 0 target 3 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 32) The major and minor numbers are correct (and I did a MAKEDEV). But, if I try to just check on things: $ mt stat mt: /dev/nrsa0: Device not configured Anyone have any ideas? Does this ring any bells? What on earth did I do wrong? I can't imagine that this would matter, but my scsi card is ultra-2, and I have an ultra-2 to wide adapter on it for the tape drive. Thanks a lot. A week of no backups is beginning to wig me out. Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 1:43:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8F0DF14C4B for ; Mon, 31 Jan 2000 01:43:29 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id CAA28362; Mon, 31 Jan 2000 02:08:46 -0800 (PST) Date: Mon, 31 Jan 2000 02:08:45 -0800 From: Alfred Perlstein To: Gary Palmer Cc: Tom , freebsd-stable@FreeBSD.ORG Subject: More than just logging, Re: JFS Message-ID: <20000131020845.T13027@fw.wintelcom.net> References: <82900.949299705@in-addr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <82900.949299705@in-addr.com>; from gjp@in-addr.com on Mon, Jan 31, 2000 at 01:21:45AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Gary Palmer [000130 22:55] wrote: > Tom wrote in message ID > : > > On Sun, 30 Jan 2000, Daniel C. Sobral wrote: > > > > > > Due to the lack of interest, FreeBSD's LFS has fallen into disrepair > > > > over the years. With the implementation of softupdates in FreeBSD I > > > > don't think there is any need for LFS any more. > > > > > > Repeat that over and over the next time you wait fsck finish a 40 Gb > > > filesystem checkup, and see if you manage to convince yourself of that. > > > > Actually, one of the goals of the softupdates development is a fsck'less > > filesystem. I'm not sure how this is to be achieved. Probably a metadata > > journal, though that is just speculation. All the work on metadata update > > ordering in softupdates would probably apply very nicely to a journal. > > The way I understand it is that SoftUpdates is meant to leave the > metadata consistant enough that the filesystem can be mounted > read/write immediately at boot, and then have a background fsck go > through and remove blocks which are allocated in the bitmaps, but > aren't really used. The only thing you lose by not running the > background daemon is space. I don't think anyone's running like this > today, but that is Kirks plan. (This is me (hopefully accurately) repeating something that Terry Lambert brought to my attention, credit where credit is due. The safe-shutdown is my rambling on about a solution.) Why logging filesystems don't work: You generally (with the hardware available in PCs now) can't tell the difference between: 1) loss of power (ok!) 2) crash where the filesystem datastructures weren't corrupted (ok!) 3) crash where the filesystem datastructures were corrupted (ouch) 4) crash where the disk/bus got scrambled (ouch) the problems with 3 and 4 really make a logging filesystem a "shot in the dark" because you never know if "safe" areas on the disk really are safe because there was a chance for corruption. How do you know that a bug in some other code didn't trounce on the filesystem's data and write to a spot that's supposedly "committed"? Since you generally can't tell between 1,2,3 and 4 you really ought to fsck in the background anyway. Good news: afaik Kirk is working on this capability! Bad news: people running depending on _only_ logging are kidding themselves. Mini-fix for this problem: Providing safe shutdown points for the filesystem, if something "weird" is found, disable further access to that file/directory or possibly shutdown the entire filesystem. Basically instead of panic'ing when invalid structures are read from disk, just disallow further access to the objects. patches anyone? :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 5:38: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 2C93314DAE for ; Mon, 31 Jan 2000 05:37:45 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id IAA86151; Mon, 31 Jan 2000 08:37:42 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id IAA10595; Mon, 31 Jan 2000 08:37:41 -0500 (EST) Message-Id: <4.2.2.20000131083329.0435fe88@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 31 Jan 2000 08:36:23 -0500 To: dayton@overx.com, freebsd-stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: My sa0 stopped working on upgrade In-Reply-To: <86ya9666zq.fsf@polo.overx.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:22 AM 1/31/2000 -0600, Soren Dayton wrote: >The major and minor numbers are correct (and I did a MAKEDEV). But, >if I try to just check on things: > > $ mt stat > mt: /dev/nrsa0: Device not configured > >Anyone have any ideas? Does this ring any bells? What on earth did I Yes, I saw this behaviour as well somewhere along the lines of tracking STABLE. Although I get the above error message when there is no tape in the drive, it does work fine for me. Both with sa0 at ahc0 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 7) and my sa0 at ahc0 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 7.812MB/s transfers (7.812MHz, offset 15) ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 7:13:12 2000 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 4298514C27; Mon, 31 Jan 2000 07:13:09 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA14539; Mon, 31 Jan 2000 07:13:08 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda14536; Mon Jan 31 07:13:01 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id HAA17848; Mon, 31 Jan 2000 07:13:00 -0800 (PST) Message-Id: <200001311513.HAA17848@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpde17842; Mon Jan 31 07:12:43 2000 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cschuber To: "Daniel C. Sobral" Cc: Cy Schubert - ITSD Open Systems Group , Kris Kennaway , Ataualpa Albert Carmo Braga , freebsd-stable@FreeBSD.ORG Subject: Re: JFS In-reply-to: Your message of "Sun, 30 Jan 2000 15:02:44 +0900." <3893D404.189AA11A@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Jan 2000 07:12:43 -0800 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3893D404.189AA11A@newsguy.com>, "Daniel C. Sobral" writes: > Cy Schubert - ITSD Open Systems Group wrote: > > > > 4.4BSD has something like JFS, LFS (Log Structured Filesystem). LFS > > developed from a paper by John Ousterhout, the same fellow who > > developed Tcl & Tk. All other log structured filesystems, JFS, AdvFS, > > Veritas Filesystem, are based on Ousterhout's work. > > A journalled structured filesystem is NOT a log structured filesystem. I stand corrected on this point. > > > Due to the lack of interest, FreeBSD's LFS has fallen into disrepair > > over the years. With the implementation of softupdates in FreeBSD I > > don't think there is any need for LFS any more. > > Repeat that over and over the next time you wait fsck finish a 40 Gb > filesystem checkup, and see if you manage to convince yourself of that. Read the CVS logs and tell me how you could interpret the comments any differently: 1.21 Fri Jan 30 11:33:40 1998 UTC by phk CVS Tags: HEAD Diffs to 1.20 FILE REMOVED Retire LFS. If you want to play with it, you can find the final version of the code in the repository the tag LFS_RETIREMENT. If somebody makes LFS work again, adding it back is certainly desireable, but as it is now nobody seems to care much about it, and it has suffered considerable bitrot since its somewhat haphazard integration. R.I.P Obviously you don't know what you're talking about either. Do you? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Province of BC "COBOL IS A WASTE OF CARDS." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 7:26:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 5903F14BF6 for ; Mon, 31 Jan 2000 07:26:09 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p07-dnz02kiryunisiki.gunma.ocn.ne.jp [210.163.200.104]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id AAA16994; Tue, 1 Feb 2000 00:26:05 +0900 (JST) Message-ID: <3895A96A.8ABB0B53@newsguy.com> Date: Tue, 01 Feb 2000 00:25:30 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Cc: "Daniel C. Sobral" , Ataualpa Albert Carmo Braga Subject: Re: JFS References: <200001311513.HAA17848@passer.osg.gov.bc.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cy Schubert wrote: > > > > Due to the lack of interest, FreeBSD's LFS has fallen into disrepair > > > over the years. With the implementation of softupdates in FreeBSD I > > > don't think there is any need for LFS any more. > > > > Repeat that over and over the next time you wait fsck finish a 40 Gb > > filesystem checkup, and see if you manage to convince yourself of that. > > Read the CVS logs and tell me how you could interpret the comments any > differently: > > 1.21 Fri Jan 30 11:33:40 1998 UTC by phk > CVS Tags: HEAD > Diffs to 1.20 > FILE REMOVED > > Retire LFS. > > If you want to play with it, you can find the final version of the > code in the repository the tag LFS_RETIREMENT. > > If somebody makes LFS work again, adding it back is certainly > desireable, but as it is now nobody seems to care much about it, > and it has suffered considerable bitrot since its somewhat haphazard > integration. > > R.I.P > > Obviously you don't know what you're talking about either. Do you? I do know. The main reason why LFS was never updated isn't that it was made obsolete by softupdates, as claimed above, but that it was made obsolete by JFS. Why work on LFS if it is not up to a JFS? Unfortunately, the people who have to suffer enourmous waits after crashes usually have way more to do, even if they have the skills to fix LFS. With the disks getting bigger and bigger, this is due to change. BTW, NetBSD is happy with _their_ _functional_ LFS. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 7:38:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 2C8D914D5B for ; Mon, 31 Jan 2000 07:38:20 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id KAA08743; Mon, 31 Jan 2000 10:38:16 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000131103542.01e40100@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 31 Jan 2000 10:35:42 -0500 To: stable@freebsd.org From: Mike Tancsa Subject: Dummynet changes with latest STABLE ? Cc: luigi@iet.unipi.it Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Since upgrading to the latest STABLE this morning, dummynet is complaining with a series of dolomite /kernel: -- dummynet: warning, event is 1 ticks late I was running with a version from 40 days ago prior to upgrading this morning. I have options "ICMP_BANDLIM" options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable xparent proxy support options "IPFIREWALL_VERBOSE_LIMIT=25000" #limit verbosity options IPDIVERT #divert sockets options DUMMYNET options HZ=1000 My dummynet rules are as follows $fwcmd add 100 pass all from any to any via lo0 $fwcmd add 200 deny all from any to 127.0.0.0/8 $fwcmd pipe 1 config bw 512Kbit/s $fwcmd pipe 2 config bw 8Mbit/s $fwcmd add 500 pipe 1 ip from any to 206.51.23.192/28 $fwcmd add 510 pipe 1 ip from 206.51.23.192/28 to any $fwcmd add 1000 allow ip from 209.112.4.32/27 to any $fwcmd add 1100 allow ip from 207.245.212.128/28 to any $fwcmd add 1110 allow ip from 205.211.164.81 to any $fwcmd add 1200 deny log tcp from any to 207.245.238.168 23 $fwcmd add 620 pipe 2 ip from 207.245.238.173 to any $fwcmd add 621 pipe 2 ip from any 207.245.238.173 $fwcmd add 622 pipe 2 ip from any to 207.245.238.173 $fwcmd add 623 pipe 2 ip from 207.245.238.179 to any $fwcmd add 624 pipe 2 ip from any to 207.245.238.179 $fwcmd add 625 pipe 2 ip from any to 207.245.238.185 $fwcmd add 626 pipe 2 ip from 207.245.238.185 to any ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 7:43:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 3F07A14D54 for ; Mon, 31 Jan 2000 07:43:27 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p07-dnz02kiryunisiki.gunma.ocn.ne.jp [210.163.200.104]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id AAA21750; Tue, 1 Feb 2000 00:43:18 +0900 (JST) Message-ID: <3895AD71.D63405A9@newsguy.com> Date: Tue, 01 Feb 2000 00:42:41 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Alfred Perlstein Cc: Gary Palmer , Tom , freebsd-stable@FreeBSD.ORG Subject: Re: More than just logging, Re: JFS References: <82900.949299705@in-addr.com> <20000131020845.T13027@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > Bad news: people running depending on _only_ logging are kidding themselves. Yeah. Funny how they have been doing so without getting bitten, eh? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 7:53:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id C828714A24 for ; Mon, 31 Jan 2000 07:52:49 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id QAA21966; Mon, 31 Jan 2000 16:51:49 +0100 (MET) Message-ID: <3895AF8A.D4D83A72@we.lc.ehu.es> Date: Mon, 31 Jan 2000 16:51:38 +0100 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Carl Makin Cc: stable@FreeBSD.ORG Subject: Re: i810 Kernel module for XFree86 3.3.6. References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Carl Makin wrote: > > Has anybody played around with porting the agpgart.o Linux kernel module > to FreeBSD 3.4? > > Unfortunately I'm not up to the port myself however I'll help with testing > it if anyone else is doing it! > We had to reject five i810e-based PCs because they wasn't capable of running FreeBSD + XFree86 3.3.6. (Of course, I warned about that, but someone chose the cheaper model "with 133 MHz bus" -- when it runs at 100 MHz with a PIII 500!). Personally, I decided to boycott the i810 chipset. I am absolutely opposed to chipsets including graphics and audio controllers. And IMHO now Intel Corp. attacks the makers of graphics and audio cards, imposing [even] more restrictions on our freedom of choice in the PC market. Rats. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 8:16:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id C2CFD14CEC for ; Mon, 31 Jan 2000 08:16:20 -0800 (PST) (envelope-from steveroo@mothra.bri.hp.com) Received: from mothra.bri.hp.com (mothra.bri.hp.com [15.144.1.185]) by palrel1.hp.com (Postfix) with ESMTP id 6F0D7844; Mon, 31 Jan 2000 08:16:18 -0800 (PST) Received: from localhost (steveroo@localhost) by mothra.bri.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id QAA22565; Mon, 31 Jan 2000 16:15:25 GMT Date: Mon, 31 Jan 2000 16:15:25 +0000 (GMT) From: Stephen Roome To: "Jose M. Alcaide" Cc: Carl Makin , stable@FreeBSD.ORG Subject: Re: i810 Kernel module for XFree86 3.3.6. In-Reply-To: <3895AF8A.D4D83A72@we.lc.ehu.es> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, Jose M. Alcaide wrote: > Personally, I decided to boycott the i810 chipset. I am absolutely > opposed to chipsets including graphics and audio controllers. And IMHO > now Intel Corp. attacks the makers of graphics and audio cards, > imposing [even] more restrictions on our freedom of choice in the > PC market. Rats. While you might happily boycott these chipsets because of some moral standpoint, unfortunately some of the newer combined motherboards are so cheap we can expect to see them in a lot of low end PC's shortly, if not already. There's one board I've seen , that has a 56k modem, 3d (4channel) sound, agp video (8mb ram) and 100mbs network all onboard. (granted it's not i810) It costs about the same as most other boards with none of these features. I think the board I'm thinking of is made by "chips and technologies" but I could be wrong there. So, although many of us here might agree with your sentiment, standing up to it is analagous to trying to blow a hurricane back from where it came. If the technology goes this way it might be best to have support for it in FreeBSD. And although we might not like the way it's going should I still be poor student trying to learn unix again, that would probably be the board I'd have to buy, and it would be nice to think I could expect it to work with my OS choice. Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 8:21: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 0D85E14DC9 for ; Mon, 31 Jan 2000 08:21:04 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id QAA00384; Mon, 31 Jan 2000 16:20:16 GMT (envelope-from steve) 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: <20000131020845.T13027@fw.wintelcom.net> Date: Mon, 31 Jan 2000 16:20:16 -0000 (GMT) From: "Steve O'Hara-Smith" To: Alfred Perlstein Subject: RE: More than just logging, Re: JFS Cc: freebsd-stable@FreeBSD.ORG, Tom , Gary Palmer Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why logging filesystems don't work: > > You generally (with the hardware available in PCs now) > can't tell the difference between: > > 1) loss of power (ok!) > 2) crash where the filesystem datastructures weren't corrupted (ok!) > 3) crash where the filesystem datastructures were corrupted (ouch) > 4) crash where the disk/bus got scrambled (ouch) Nice analysis. I have a vague memory (I can't seem to find the message in the archives) of somebody on -current talking about a proposal for a log device that emitted events from the filesystem. Something like that and a WORM might make a reliable logging filesystem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 8:55:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.wirehub.nl (smtp.wirehub.nl [195.86.25.80]) by hub.freebsd.org (Postfix) with ESMTP id 3B2B414DC9 for ; Mon, 31 Jan 2000 08:55:37 -0800 (PST) (envelope-from bvdijk@peterson.nl) Received: from peterson.nl (tlr-1.peterson.nl [194.165.71.6]) by smtp.wirehub.nl (8.9.3/8.9.3) with ESMTP id RAA20495 for ; Mon, 31 Jan 2000 17:55:35 +0100 (CET) Received: from TLR-1/SpoolDir by peterson.nl (Mercury 1.46); 31 Jan 00 17:53:56 +0200 Received: from SpoolDir by TLR-1 (Mercury 1.46); 31 Jan 00 17:53:51 +0200 Received: from rtwin98ict01 (194.165.71.87) by peterson.nl (Mercury 1.46); 31 Jan 00 17:53:48 +0200 Message-ID: <001301bf6a79$b7899f20$5747a5c2@peterson.nl> From: "Barry van Dijk" To: Subject: PANIC Date: Sat, 29 Jan 2000 17:55:50 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After make buildworld and make installworld... Everything looks fine until loading of final daemons.. FATAL TRAP 12: pagefault in kernel mode fault virtual address = 0x45058 fault code = supervisor read, page not present current process = 117 (mountd) All I can do it reboot... HELP! I can still login in single-user mode... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 9: 1:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 7137114DC7 for ; Mon, 31 Jan 2000 09:01:07 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id MAA25874; Mon, 31 Jan 2000 12:00:55 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000131115821.02b2da60@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 31 Jan 2000 11:58:21 -0500 To: "Barry van Dijk" From: Mike Tancsa Subject: Re: PANIC Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <001301bf6a79$b7899f20$5747a5c2@peterson.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:55 PM 1/29/00 +0100, you wrote: >After make buildworld and make installworld... > >Everything looks fine until loading of final daemons.. > >FATAL TRAP 12: pagefault in kernel mode >fault virtual address = 0x45058 >fault code = supervisor read, page not present >current process = 117 (mountd) > >All I can do it reboot... > >HELP! > >I can still login in single-user mode... You didnt mention it, but did you rebuild and install your kernel as well ? ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 9: 5:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.wirehub.nl (smtp.wirehub.nl [195.86.25.80]) by hub.freebsd.org (Postfix) with ESMTP id 0649614C87 for ; Mon, 31 Jan 2000 09:05:35 -0800 (PST) (envelope-from bvdijk@peterson.nl) Received: from peterson.nl (tlr-1.peterson.nl [194.165.71.6]) by smtp.wirehub.nl (8.9.3/8.9.3) with ESMTP id SAA21685 for ; Mon, 31 Jan 2000 18:05:33 +0100 (CET) Received: from TLR-1/SpoolDir by peterson.nl (Mercury 1.46); 31 Jan 00 18:03:54 +0200 Received: from SpoolDir by TLR-1 (Mercury 1.46); 31 Jan 00 18:03:45 +0200 Received: from rtwin98ict01 (194.165.71.87) by peterson.nl (Mercury 1.46); 31 Jan 00 18:03:45 +0200 Message-ID: <004901bf6a7b$1b038380$5747a5c2@peterson.nl> From: "Barry van Dijk" To: References: <3.0.5.32.20000131115821.02b2da60@marble.sentex.ca> Subject: Re: PANIC Date: Sat, 29 Jan 2000 18:05:55 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 05:55 PM 1/29/00 +0100, you wrote: > >After make buildworld and make installworld... > > > >Everything looks fine until loading of final daemons.. > > > >FATAL TRAP 12: pagefault in kernel mode > >fault virtual address = 0x45058 > >fault code = supervisor read, page not present > >current process = 117 (mountd) > > > >All I can do it reboot... > > > >HELP! > > > >I can still login in single-user mode... > > You didnt mention it, but did you rebuild and install your kernel as well ? Yes, I did... (before booting after make installworld) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 9: 7:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by hub.freebsd.org (Postfix) with ESMTP id AA49014F8A for ; Mon, 31 Jan 2000 09:07:46 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by melete.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id RAA14778; Mon, 31 Jan 2000 17:08:43 GMT Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.8 1999/04/16 15:25:49 steved Exp steved $) with ESMTP id KAA21624; Mon, 31 Jan 2000 10:07:42 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id MAA08856; Mon, 31 Jan 2000 12:07:41 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14485.49500.972288.471636@hip186.ch.intel.com> Date: Mon, 31 Jan 2000 10:07:40 -0700 (MST) To: Mike Tancsa Cc: "Barry van Dijk" , freebsd-stable@freebsd.org Subject: Re: PANIC In-Reply-To: <3.0.5.32.20000131115821.02b2da60@marble.sentex.ca> References: <001301bf6a79$b7899f20$5747a5c2@peterson.nl> <3.0.5.32.20000131115821.02b2da60@marble.sentex.ca> X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Monday, January 31, Mike Tancsa wrote: ] > > You didnt mention it, but did you rebuild and install your kernel as well ? > Aaaa, good point. I'd sent him a message in private e-mail suggesting that he move the .sh scripts in /usr/local/etc/rc.d to a temporary location and try and reboot--perhaps it was a "local package" that was reacting poorly to something new. But, if the kernel wasn't built and installed, that could certainly reek havoc too!!! -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 9:20:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.wirehub.nl (smtp.wirehub.nl [195.86.25.80]) by hub.freebsd.org (Postfix) with ESMTP id DB0CD14D4B for ; Mon, 31 Jan 2000 09:20:28 -0800 (PST) (envelope-from bvdijk@peterson.nl) Received: from peterson.nl (tlr-1.peterson.nl [194.165.71.6]) by smtp.wirehub.nl (8.9.3/8.9.3) with ESMTP id SAA22866 for ; Mon, 31 Jan 2000 18:20:27 +0100 (CET) Received: from TLR-1/SpoolDir by peterson.nl (Mercury 1.46); 31 Jan 00 18:18:48 +0200 Received: from SpoolDir by TLR-1 (Mercury 1.46); 31 Jan 00 18:18:36 +0200 Received: from rtwin98ict01 (194.165.71.87) by peterson.nl (Mercury 1.46); 31 Jan 00 18:18:32 +0200 Message-ID: <006d01bf6a7d$2bed6e20$5747a5c2@peterson.nl> From: "Barry van Dijk" To: Subject: NO MORE PANIC: Thanks to John Reynolds Date: Sat, 29 Jan 2000 18:20:42 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pfew.... After booting in single user mode: Removed apache from autostarting, my machine booted again! Trying 'apachectl start' worked... So everything works again... Tomorrow if figure apache's problem out... For now, I call it a day! Thanks again... I'm still above normal tempareture... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 9:28:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 05C1F14CB3 for ; Mon, 31 Jan 2000 09:28:37 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 12FKcf-000B93-00; Mon, 31 Jan 2000 09:28:21 -0800 Date: Mon, 31 Jan 2000 09:28:19 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Daniel C. Sobral" Cc: freebsd-stable@FreeBSD.ORG, Ataualpa Albert Carmo Braga Subject: Re: JFS In-Reply-To: <3895A96A.8ABB0B53@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Feb 2000, Daniel C. Sobral wrote: > I do know. The main reason why LFS was never updated isn't that it was > made obsolete by softupdates, as claimed above, but that it was made > obsolete by JFS. Why work on LFS if it is not up to a JFS? Well, a log structured file system has some interesting performance characteristics. It is also rather a curiosity too, as there are so few implementations. I understand that the WAFL filesystem is basically log structured. > Unfortunately, the people who have to suffer enourmous waits after > crashes usually have way more to do, even if they have the skills to fix > LFS. > > With the disks getting bigger and bigger, this is due to change. > > BTW, NetBSD is happy with _their_ _functional_ LFS. Maybe somebody should import it. I was kind of disappointed to learn that the U in NetBSD UVM doesn't stand for unified, and that NetBSD still doesn't have a unified VM. This pretty much kills any advantage NetBSD could have these days. > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "If you consider our help impolite, you should see the manager." Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 11:57: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id D155714C01 for ; Mon, 31 Jan 2000 11:56:55 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id EA27412732; Mon, 31 Jan 2000 20:56:38 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Mon, 31 Jan 2000 18:58:19 +0100 To: Tom , "Rodney W. Grimes" From: Brad Knowles Subject: Re: Multiple IP addresses Cc: Mike Bristow , "N.B. DelMore" , freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:45 AM -0800 2000/1/27, Tom wrote: > On a side note, I'd actually like to see a mechanism to attach owners to > IPs, and allows owners to bind to ports < 1024. Perhaps some sort of > role-based control system needs to be looked at. You can't do this via the virtual machine "jail" that Poul-Henning Kamp is going to be talking about at SANE 2000? ;-) -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 12:24:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 7E36614D8A; Mon, 31 Jan 2000 12:24:13 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id PAA24942; Mon, 31 Jan 2000 15:23:38 -0500 (EST) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200001312023.PAA24942@blackhelicopters.org> Subject: NO_NAMED (patch attached) To: current@freebsd.org, stable@freebsd.org Date: Mon, 31 Jan 2000 15:23:38 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, the corporate firewall doesn't allow send-pr, so I'm trying this the noisy way. Sorry. :( We have a no_named flag in /usr/src/usr.sbin/Makefile, right by no_sendmail. A recent discussion on -security shows that at least a couple people have a use for this. Therefore, submitted for your approval, as per the Handbook: *** make.conf~ Mon Jan 24 13:55:29 2000 --- make.conf Mon Jan 31 15:25:49 2000 *************** *** 28,33 **** --- 28,36 ---- # To avoid building sendmail #NO_SENDMAIL= true # + # To avoid building named and related tools + #NO_BIND= true + # # To have 'obj' symlinks created in your source directory # (they aren't needed/necessary) #OBJLINK= yes This is against -stable, about a week old. Sorry, don't have -current on my laptop... I'm not a real hacker. ==ml (Wow, my first patch. Trivial, yet I find myself heady with success. ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 13:43:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 56D4E14C05 for ; Mon, 31 Jan 2000 13:43:37 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id OAA20171; Mon, 31 Jan 2000 14:43:34 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200001312143.OAA20171@freeway.dcfinc.com> Subject: Re: JFS In-Reply-To: <3895A96A.8ABB0B53@newsguy.com> from "Daniel C. Sobral" at "Feb 1, 0 00:25:30 am" To: dcs@newsguy.com (Daniel C. Sobral) Date: Mon, 31 Jan 2000 14:43:34 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG, dcs@newsguy.com, atabraga@iqm.unicamp.br Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Daniel C. Sobral wrote: > I do know. The main reason why LFS was never updated isn't that it > was made obsolete by softupdates, as claimed above, but that it was > made obsolete by JFS. Why work on LFS if it is not up to a JFS? > Unfortunately, the people who have to suffer enourmous waits after > crashes usually have way more to do, even if they have the skills to > fix LFS. To shove this discussion a bit sideways, SGI announced a while back that they were going to release the source code to their Journaled File System. Does anyone here know that status of that? Wouldn't that be the perfect starting place for a FreeBSD JFS? Do we know what their license will look like? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 13:55:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from email.spcgroup.nl (email.spcgroup.nl [212.206.124.3]) by hub.freebsd.org (Postfix) with ESMTP id 2F18615003 for ; Mon, 31 Jan 2000 13:55:36 -0800 (PST) (envelope-from edwinm@email.spcgroup.nl) Received: from localhost (edwinm@localhost) by email.spcgroup.nl (8.9.3/8.9.3) with ESMTP id WAA25693; Mon, 31 Jan 2000 22:54:50 +0100 Date: Mon, 31 Jan 2000 22:54:50 +0100 (CET) From: Edwin Mons To: "Chad R. Larson" Cc: "Daniel C. Sobral" , freebsd-stable@FreeBSD.ORG, atabraga@iqm.unicamp.br Subject: Re: JFS In-Reply-To: <200001312143.OAA20171@freeway.dcfinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, Chad R. Larson wrote: > As I recall, Daniel C. Sobral wrote: > > I do know. The main reason why LFS was never updated isn't that it > > was made obsolete by softupdates, as claimed above, but that it was > > made obsolete by JFS. Why work on LFS if it is not up to a JFS? > > Unfortunately, the people who have to suffer enourmous waits after > > crashes usually have way more to do, even if they have the skills to > > fix LFS. > > To shove this discussion a bit sideways, SGI announced a while back > that they were going to release the source code to their Journaled > File System. Does anyone here know that status of that? Wouldn't > that be the perfect starting place for a FreeBSD JFS? Do we know > what their license will look like? It's not released yet, but there are some code-fragments released to public already. As far as I know, it will be released under the GPL. It's named XFS, and you can find information here: http://http://oss.sgi.com/projects/xfs Regards, Intosi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 14:42:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kinkajou.arc.nasa.gov (kinkajou.arc.nasa.gov [128.102.132.150]) by hub.freebsd.org (Postfix) with ESMTP id C769F14DBE for ; Mon, 31 Jan 2000 14:42:10 -0800 (PST) (envelope-from lamaster@nren.nasa.gov) Received: from localhost (lamaster@localhost) by kinkajou.arc.nasa.gov (8.9.3+Sun/8.9.1) with ESMTP id OAA13943 for ; Mon, 31 Jan 2000 14:41:56 -0800 (PST) X-Authentication-Warning: kinkajou.arc.nasa.gov: lamaster owned process doing -bs Date: Mon, 31 Jan 2000 14:41:56 -0800 (PST) From: Hugh LaMaster X-Sender: lamaster@kinkajou.arc.nasa.gov To: FreeBSD Stable Subject: Problems with Buslogic BT-958C in 3.2-3.4 RELEASE? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I upgraded a few months ago to 3.2-RELEASE, and, immediately started seeing problems with the Buslogic BT-958 controller. I would get the following messages, and then, the system would become unreachable across the network without a reboot, although the console still worked, and you could read disks locally. Strange. Anyway, I got busy, and rather than mess with it more, I decided to go with 3.4-RELEASE instead. Same messages, but, the behavior is better, because it seems to recover, and the system continues to work. Still, I'm concerned about it. The messages are about 6 busy mailbox messages: fred# Jan 25 02:06:48 fred /kernel: bt0: Encountered busy mailbox with 191 out of 192 commands active!!! Jan 25 02:06:48 fred /kernel: bt0: Encountered busy mailbox with 191 out of 192 commands active!!! Jan 25 02:06:49 fred /kernel: bt0: Encountered busy mailbox with 190 out of 192 commands active!!! Jan 25 02:06:49 fred /kernel: bt0: Encountered busy mailbox with 190 out of 192 commands active!!! Jan 25 02:06:49 fred /kernel: bt0: btdone - Attempt to free non-active BCCB 0xc5ca8ec0 Jan 25 02:06:49 fred /kernel: bt0: btdone - Attempt to free non-active BCCB 0xc5ca8ec0 Jan 25 02:07:48 fred /kernel: (da0:bt0:0:0:0): CCB 0xc5ca8c80 - timed out Jan 25 02:07:48 fred /kernel: (da0:bt0:0:0:0): CCB 0xc5ca8c80 - timed out Jan 25 02:08:12 fred /kernel: bt0: btdone - Attempt to free non-active BCCB 0xc5ca83c0 Jan 25 02:08:12 fred /kernel: bt0: btdone - Attempt to free non-active BCCB 0xc5ca83c0 Jan 25 02:08:12 fred /kernel: (da0:bt0:0:0:0): CCB 0xc5ca8c80 - timed out Jan 25 02:08:12 fred /kernel: (da0:bt0:0:0:0): CCB 0xc5ca8c80 - timed out Jan 25 02:08:12 fred /kernel: bt0: No longer in timeout Jan 25 02:08:12 fred /kernel: bt0: No longer in timeout From uname -a: 3.4-RELEASE FreeBSD 3.4-RELEASE #6: Relevant other info from boot messages: Jan 24 12:51:06 fred /kernel: ahc0: rev 0x04 int a irq 0 on pci0.14.0 Jan 24 12:51:06 fred /kernel: ahc1: rev 0x04 int b irq 0 on pci0.14.1 Jan 24 12:51:06 fred /kernel: bt0: rev 0x08 int a irq 11 on pci0.16.0 Jan 24 12:51:06 fred /kernel: bt0: BT-958 FW Rev. 5.07B Ultra Wide SCSI Host Adapter, SCSI ID 7, 192 CCBs Jan 24 12:51:06 fred /kernel: hea0: rev 0x00 int a irq 10 on pci0.18.0 Jan 24 12:51:06 fred /kernel: de0: rev 0x22 int a irq 9 on pci0.20.0 Jan 24 12:51:06 fred /kernel: de0: enabling Full Duplex 100baseTX port Jan 24 12:51:06 fred /kernel: da1 at bt0 bus 0 target 1 lun 0 Jan 24 12:51:06 fred /kernel: da1: Fixed Direct Access SCSI-2 device Jan 24 12:51:06 fred /kernel: da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jan 24 12:51:06 fred /kernel: da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Jan 24 12:51:06 fred /kernel: da3 at bt0 bus 0 target 3 lun 0 Jan 24 12:51:06 fred /kernel: da3: Fixed Direct Access SCSI-2 device Jan 24 12:51:06 fred /kernel: da3: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jan 24 12:51:06 fred /kernel: da3: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Jan 24 12:51:06 fred /kernel: da0 at bt0 bus 0 target 0 lun 0 Jan 24 12:51:06 fred /kernel: da0: Fixed Direct Access SCSI-2 device Jan 24 12:51:06 fred /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jan 24 12:51:06 fred /kernel: da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Jan 24 12:51:06 fred /kernel: da2 at bt0 bus 0 target 2 lun 0 Jan 24 12:51:06 fred /kernel: da2: Fixed Direct Access SCSI-2 device Jan 24 12:51:06 fred /kernel: da2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jan 24 12:51:06 fred /kernel: da2: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Jan 24 12:51:06 fred /kernel: cd0 at bt0 bus 0 target 4 lun 0 Jan 24 12:51:07 fred /kernel: cd0: Removable CD-ROM SCSI-2 device Jan 24 12:51:07 fred /kernel: cd0: 10.000MB/s transfers (10.000MHz, offset 15) Jan 24 12:51:07 fred /kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Any ideas? -- Hugh LaMaster, M/S 233-21, Email: lamaster@nren.nasa.gov NASA Ames Research Center Or: lamaster@nas.nasa.gov Moffett Field, CA 94035-1000 Or: lamaster@george.arc.nasa.gov Phone: 650/604-1056 Disc: Unofficial, personal *opinion*. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 15: 0: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 3524314EAB for ; Mon, 31 Jan 2000 14:59:57 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 12FPn6-000HiN-00; Mon, 31 Jan 2000 14:59:28 -0800 Date: Mon, 31 Jan 2000 14:59:24 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Edwin Mons Cc: "Chad R. Larson" , "Daniel C. Sobral" , freebsd-stable@FreeBSD.ORG, atabraga@iqm.unicamp.br Subject: Re: JFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, Edwin Mons wrote: > On Mon, 31 Jan 2000, Chad R. Larson wrote: > > As I recall, Daniel C. Sobral wrote: > > > I do know. The main reason why LFS was never updated isn't that it > > > was made obsolete by softupdates, as claimed above, but that it was > > > made obsolete by JFS. Why work on LFS if it is not up to a JFS? > > > Unfortunately, the people who have to suffer enourmous waits after > > > crashes usually have way more to do, even if they have the skills to > > > fix LFS. > > > > To shove this discussion a bit sideways, SGI announced a while back > > that they were going to release the source code to their Journaled > > File System. Does anyone here know that status of that? Wouldn't > > that be the perfect starting place for a FreeBSD JFS? Do we know > > what their license will look like? > > It's not released yet, but there are some code-fragments released to > public already. As far as I know, it will be released under the GPL. It's > named XFS, and you can find information here: > http://http://oss.sgi.com/projects/xfs The indications are that it will at least a year before XFS works under Linux. ReiserFS is journalled, and mostly works now. It could be a port candidate. There is also ext3, which is supposed to replace ext2 on Linux. It has journaling and ACLs. It mostly works. Basically, a lot development and testing needs to be done before any open-source OS has a completely working journalled filesystem. > Regards, > Intosi Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 31 15: 3:32 2000 Delivered-To: freebsd-stable@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id E26261509B for ; Mon, 31 Jan 2000 15:03:29 -0800 (PST) (envelope-from patl@phoenix.volant.org) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with esmtp (Exim 1.92 #8) for freebsd-stable@freebsd.org id 12FPqy-0004Zv-00; Mon, 31 Jan 2000 15:03:28 -0800 Received: from localhost (localhost [127.0.0.1]) by asimov.phoenix.volant.org (8.9.1b+Sun/8.9.1) with SMTP id PAA17899 for ; Mon, 31 Jan 2000 15:03:26 -0800 (PST) Date: Mon, 31 Jan 2000 15:03:26 -0800 (PST) From: patl@phoenix.volant.org Reply-To: patl@phoenix.volant.org Subject: ICMP redirects: self => self To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently upgraded an old system to 3.4R. Now I'm getting a lot of ICMP redirect log messages directing that host back to itself: Jan 31 10:44:36 myhost /kernel: icmp redirect from 10.0.0.68: 10.0.0.67 => 10.0.0.67 Jan 31 10:44:57 myhost last message repeated 234 times Jan 31 10:46:59 myhost last message repeated 954 times Jan 31 10:57:01 myhost last message repeated 4695 times (I've changed the network portion and hostname for the example.) I don't understand why the triggering packets ever made it out to the gateway in the first place - shouldn't it loopback for its own IP address? I've checked 'ifconfig -a' and 'netstat -nr' output; and both look OK. (Similar to other hosts on the network.) Thanks, -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 7:25: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id E7F0F37B516; Wed, 16 Feb 2000 07:24:57 -0800 (PST) (envelope-from khera@kciLink.com) Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by builder.freebsd.org (Postfix) with ESMTP id E4D9E132D9; Wed, 16 Feb 2000 07:24:21 -0800 (PST) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id B242DE8A7; Wed, 16 Feb 2000 10:24:51 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id KAA08987; Wed, 16 Feb 2000 10:24:51 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14506.49475.641654.89251@onceler.kcilink.com> Date: Wed, 16 Feb 2000 10:24:51 -0500 (EST) To: Josef Karthauser Cc: questions@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: FreeBSD 3.4, Samba, HP LaserJet 5N, delays, reboots In-Reply-To: <20000216125718.L70401@florence.pavilion.net> References: <20000211123416.A92889@catkin.nothing-going-on.org> <38A48A9C.A3BB2D75@enc.edu> <20000216125718.L70401@florence.pavilion.net> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "JK" == Josef Karthauser writes: JK> Does it make sense to add an additional flag to the printcap? If so JK> what should it be? Nik if you document it, I'll implement it. I've been JK> near that code recently. I'd suggest "brokenremotelpq" to clearly put the blame where it belongs ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 8:43:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 8AAAD37B50B for ; Wed, 16 Feb 2000 08:43:32 -0800 (PST) (envelope-from backi@iki.fi) Received: from jt7-254.tky.hut.fi (jt7-254.tky.hut.fi [130.233.22.92]) by builder.freebsd.org (Postfix) with ESMTP id C955D132E1 for ; Wed, 16 Feb 2000 08:42:55 -0800 (PST) Received: from localhost (backi@localhost) by jt7-254.tky.hut.fi (8.9.3/8.9.3) with ESMTP id SAA75780; Wed, 16 Feb 2000 18:42:06 +0200 (EET) (envelope-from backi@iki.fi) X-Authentication-Warning: jt7-254.tky.hut.fi: backi owned process doing -bs Date: Wed, 16 Feb 2000 18:42:06 +0200 (EET) From: Patrik Backlund X-Sender: backi@jt7-254.tky.hut.fi To: Joao Pedras Cc: freebsd-stable@FreeBSD.org Subject: Re: panic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Feb 2000, Joao Pedras wrote: > When I ftp from some client the nat machine simply panics. > > What am I doing wrong ? Nothing. Ipfilter on 3.x is very old and somewhat buggy. The ftp-proxy doesn't work at all and causes the machine to panic. You can solve the problem by manually updating ipfilter to a newer version (see freebsd-diary). 4.0 will include a new (working) version of ipfilter. -- Patrik To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 9:38: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 3CE5037B521 for ; Wed, 16 Feb 2000 09:38:02 -0800 (PST) (envelope-from ronald@node11a94.a2000.nl) Received: from node11a94.a2000.nl (node11a94.a2000.nl [24.132.26.148]) by builder.freebsd.org (Postfix) with SMTP id 36E09132E7 for ; Wed, 16 Feb 2000 09:37:21 -0800 (PST) Received: (qmail 64202 invoked from network); 16 Feb 2000 17:37:42 -0000 Received: from dlanor.evertsen.nl (10.0.0.3) by node11a94.a2000.nl with SMTP; 16 Feb 2000 17:37:42 -0000 Date: Wed, 16 Feb 2000 18:37:41 +0100 (CET) From: Ronald Klop To: "Valery V. Lunyov" Cc: KAMIL MUHD , freebsd-stable@FreeBSD.ORG Subject: Re: ESS1869 sound card problem.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Feb 2000, Valery V. Lunyov wrote: > On Tue, 15 Feb 2000, KAMIL MUHD wrote: > > > > > Hi... > > > > I have this ESS1869 ver 1.0.10 sound card and having problem to configure > > it. I'm taking this from my windowz settings. > > > > There were many problems with my ESS688 Sound Card with both > snd and pcm drivers. I have installed patched pcm driver from > http://home.jp.freebsd.org/~sanpei/ and my card working > fine now! > > Thanks for developers! > > Only one problem present in this time - sometimes kde mixer > don't work properly. I have a ESS688 (pnp) working with the snd drivers in my FreeBSD box. These are the settings: in /boot/kernel.conf: pnp 1 0 enable os port0 0x240 irq0 5 drq0 3 pnp 1 1 enable os port0 0x388 pnp 1 2 enable os port0 0x201 pnp 1 3 enable os port0 0x320 irq0 7 pnp 1 4 enable os port0 0x170 irq0 15 in my kernel config file: controller snd0 device sb0 at isa? port 0x240 irq 5 drq 3 device opl0 at isa? port 0x388 device mpu0 at isa? port 0x320 irq 7 device joy0 at isa? port 0x201 and the following for the IDE controller (and disk) on the soundcard. controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0x80ff0008 disk wd2 at wdc1 drive 0 > > > DMA - 01 > > DMA - 03 > > IRQ - 05 > > I/O range - 0220-022F > > I/O range - 0388-038B > > I/O range - 0330-0331 > > > > I doesn't really know how to add it into the kernel. Before this I was using > > the OSS (open sound system) but the evaluation copy has expired. Can anyone > > help me? Thank you. > > > Try to install new pcm driver wich supports ESS1869 too. > > > My Bests! > ---------------------------------------------------------- > Valery V. Lunyov - SysAdmin @ ISP NENSI Information Center > Cherkassy, Ukraine > ---------------------------------------------------------- > E-mail: val@nensi.net > ---------------------------------------------------------- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Ronald Klop http://node11a94.a2000.nl/~ronald/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 10:11:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id C71ED37B526 for ; Wed, 16 Feb 2000 10:11:49 -0800 (PST) (envelope-from root@boostworks.com) Received: from luxren2.boostworks.com (luxren2.boostworks.com [194.167.81.214]) by builder.freebsd.org (Postfix) with ESMTP id 06EA2132E8 for ; Wed, 16 Feb 2000 10:10:39 -0800 (PST) Received: from boostworks.com (root@oldrn.luxdev.boostworks.com [192.168.1.99]) by luxren2.boostworks.com (8.9.1/8.9.1) with ESMTP id TAA84958; Wed, 16 Feb 2000 19:10:47 +0100 (CET) Message-Id: <200002161810.TAA84958@luxren2.boostworks.com> Date: Wed, 16 Feb 2000 19:10:39 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@boostworks.com Subject: Re: xl0 packet dropping, still To: cokane@one.net Cc: stable@FreeBSD.ORG In-Reply-To: <20000215210704.A969@evil.2y.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Feb, Coleman Kane wrote: > Well, I switched my xl0 ethernet carc, but I am still recieving > messages saying that there are packets being dropped. Sometimes this > results in the card being shut down. > > --cokane See commit message for Rev 1.71 of if_xl.c: seems to be a known problem with some 3com cards, especially when receiving a lot of packets. It's funny to note that this problem is even not fixed in Win$ drivers !!. A workaround is to set them to 10Mb/s, half-dup. RN. IhM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 10:12:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 46C2137B52D for ; Wed, 16 Feb 2000 10:12:31 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from rover.village.org (rover.village.org [204.144.255.49]) by builder.freebsd.org (Postfix) with ESMTP id 01C48132D9 for ; Wed, 16 Feb 2000 10:11:52 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA72712; Wed, 16 Feb 2000 11:12:15 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA11827; Wed, 16 Feb 2000 11:12:11 -0700 (MST) Message-Id: <200002161812.LAA11827@harmony.village.org> To: rjs@fdy2.demon.co.uk Subject: Re: PCMCIA insertion Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 15 Feb 2000 09:23:45 PST." <20000215172345.4EFC24EBF@builder.freebsd.org> References: <20000215172345.4EFC24EBF@builder.freebsd.org> Date: Wed, 16 Feb 2000 11:12:11 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000215172345.4EFC24EBF@builder.freebsd.org> Robert Swindells writes: : It now fails to detect PCMCIA card insertion and removal, is this a : known problem ? No. Likely you need to tweak the pccard.conf again to deal with this. Another possiblilty is that you haven't tweaked rc.conf to make it use pccard.conf rather than the default pccard.conf.sample. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 10:54:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 02F6C37B53D for ; Wed, 16 Feb 2000 10:54:42 -0800 (PST) (envelope-from swindellsr@genrad.co.uk) Received: from euromail1.genrad.com (x42.genrad.co.uk [195.99.3.42]) by builder.freebsd.org (Postfix) with ESMTP id 63DDE132D9 for ; Wed, 16 Feb 2000 10:54:01 -0800 (PST) Received: from CDP437 (cdp437.uk.genrad.com [132.223.131.31]) by euromail1.genrad.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id 187QL07Z; Wed, 16 Feb 2000 18:54:34 -0000 From: Robert Swindells To: imp@village.org Cc: freebsd-stable@FreeBSD.ORG In-reply-to: <200002161812.LAA11827@harmony.village.org> (message from Warner Losh on Wed, 16 Feb 2000 11:12:11 -0700) Subject: Re: PCMCIA insertion Reply-To: rjs@fdy2.demon.co.uk Message-Id: <20000216185401.63DDE132D9@builder.freebsd.org> Date: Wed, 16 Feb 2000 10:54:01 -0800 (PST) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >: It now fails to detect PCMCIA card insertion and removal, is this a >: known problem ? >No. Likely you need to tweak the pccard.conf again to deal with >this. Another possiblilty is that you haven't tweaked rc.conf to make >it use pccard.conf rather than the default pccard.conf.sample. An IRQ is being assigned to the PCIC but no interrupts are generated. I have just given up for now and changed pcic_probe() to always enable the timeout that polls the PCIC. Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 11:24:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 4E37C37B555 for ; Wed, 16 Feb 2000 11:24:36 -0800 (PST) (envelope-from beng@cag.lcs.mit.edu) Received: from miris.lcs.mit.edu (miris.lcs.mit.edu [18.111.0.89]) by builder.freebsd.org (Postfix) with ESMTP id 9092E132D6 for ; Wed, 16 Feb 2000 11:23:44 -0800 (PST) Received: from cag.lcs.mit.edu (regulus.lcs.mit.edu [18.111.0.196]) by miris.lcs.mit.edu (8.9.3/8.9.3) with ESMTP id OAA25116 for ; Wed, 16 Feb 2000 14:24:12 -0500 (EST) Message-Id: <200002161924.OAA25116@miris.lcs.mit.edu> X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd-stable@freebsd.org Subject: vinum + softupdates From: Benjamin Greenwald X-Sender: beng@lcs.mit.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Feb 2000 14:24:08 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Please pardon if this has been asked before (with the mail archives down and all): Does anyone have experience running softupdates on a vinum partition? Any problems/prohibitions I should be aware of? Thanks, Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 11:33:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 7240837B55F for ; Wed, 16 Feb 2000 11:33:55 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from rover.village.org (rover.village.org [204.144.255.49]) by builder.freebsd.org (Postfix) with ESMTP id 363FC132DE for ; Wed, 16 Feb 2000 11:33:10 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA72904; Wed, 16 Feb 2000 12:33:35 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA12132; Wed, 16 Feb 2000 12:33:31 -0700 (MST) Message-Id: <200002161933.MAA12132@harmony.village.org> To: rjs@fdy2.demon.co.uk Subject: Re: PCMCIA insertion Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 16 Feb 2000 11:54:37 MST." <200002161854.LAA22689@schizoid.village.org> References: <200002161854.LAA22689@schizoid.village.org> Date: Wed, 16 Feb 2000 12:33:31 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200002161854.LAA22689@schizoid.village.org> Robert Swindells writes: : An IRQ is being assigned to the PCIC but no interrupts are generated. Sadly, not all IRQs can be routed with the Libretto {5,7}0CT. IIRC, 10 worked for me. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 11:59:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 2765337B7DF for ; Wed, 16 Feb 2000 11:59:32 -0800 (PST) (envelope-from blk@skynet.be) Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by builder.freebsd.org (Postfix) with ESMTP id BAC3A132DE for ; Wed, 16 Feb 2000 11:58:49 -0800 (PST) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 8B7E1CCC9; Wed, 16 Feb 2000 20:59:21 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200002161924.OAA25116@miris.lcs.mit.edu> References: <200002161924.OAA25116@miris.lcs.mit.edu> Date: Wed, 16 Feb 2000 20:58:37 +0100 To: Benjamin Greenwald , freebsd-stable@FreeBSD.ORG From: Brad Knowles Subject: Re: vinum + softupdates Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:24 PM -0500 2000/2/16, Benjamin Greenwald wrote: > Does anyone have experience running softupdates on a vinum partition? Any > problems/prohibitions I should be aware of? There are some issues with vinum (particularly the RAID-5 code) that I believe are not fixed unless you're running a recent version of -CURRENT, and I don't know whether any of those changes will be back-ported to -STABLE, so keep this in mind. Likewise, there are some issues with running softupdates under certain circumstances (even with -CURRENT), so you don't want to run it on a particular partition unless you know that you actually need the features it provides, and you know that you can live with the problems. I'd encourage you to go to DejaNews and look in the archives they have of the sol.lists.freebsd.stable and sol.lists.freebsd.current newsgroups, which are gatewayed from the mailing lists. -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 13:18:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 6574E37B54D for ; Wed, 16 Feb 2000 13:18:08 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: from evil.2y.net (port-4-118.adsl.one.net [216.2.1.118]) by builder.freebsd.org (Postfix) with ESMTP id 47CF8132EB for ; Wed, 16 Feb 2000 13:17:19 -0800 (PST) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id QAA05255; Wed, 16 Feb 2000 16:19:53 -0500 (EST) (envelope-from cokane) Date: Wed, 16 Feb 2000 16:19:53 -0500 From: Coleman Kane To: Remy Nonnenmacher Cc: cokane@one.net, stable@FreeBSD.ORG Subject: Re: xl0 packet dropping, still Message-ID: <20000216161953.A5237@evil.2y.net> References: <20000215210704.A969@evil.2y.net> <200002161810.TAA84958@luxren2.boostworks.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj" X-Mailer: Mutt 1.0.1i In-Reply-To: <200002161810.TAA84958@luxren2.boostworks.com>; from remy@boostworks.com on Wed, Feb 16, 2000 at 01:33:34PM -0500 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Can this be fixed, or is it caused by a deficiency in the hardware? --cokane Remy Nonnenmacher had the audacity to say: > On 15 Feb, Coleman Kane wrote: > > Well, I switched my xl0 ethernet carc, but I am still recieving > > messages saying that there are packets being dropped. Sometimes this > > results in the card being shut down. > >=20 > > --cokane >=20 > See commit message for Rev 1.71 of if_xl.c: seems to be a known problem > with some 3com cards, especially when receiving a lot of packets. It's > funny to note that this problem is even not fixed in Win$ drivers !!. A > workaround is to set them to 10Mb/s, half-dup. >=20 > RN. > IhM >=20 >=20 >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message --9amGYk9869ThD9tj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE4qxR4ERViMObJ880RAYFIAJ90x0hh+da2THYsQnqJf5BY13hQCACdEaGA xKQO3ejG6pkTgX4GLKTHOMk= =ZEpy -----END PGP SIGNATURE----- --9amGYk9869ThD9tj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 13:20: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id CED3837B54D for ; Wed, 16 Feb 2000 13:20:01 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id AFAA4132E7 for ; Wed, 16 Feb 2000 13:19:23 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id NAA09752; Wed, 16 Feb 2000 13:47:55 -0800 (PST) Date: Wed, 16 Feb 2000 13:47:54 -0800 From: Alfred Perlstein To: Brad Knowles Cc: Benjamin Greenwald , freebsd-stable@FreeBSD.ORG Subject: Re: vinum + softupdates Message-ID: <20000216134754.E3509@fw.wintelcom.net> References: <200002161924.OAA25116@miris.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from blk@skynet.be on Wed, Feb 16, 2000 at 08:58:37PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Brad Knowles [000216 13:31] wrote: > At 2:24 PM -0500 2000/2/16, Benjamin Greenwald wrote: > > > Does anyone have experience running softupdates on a vinum partition? Any > > problems/prohibitions I should be aware of? > > There are some issues with vinum (particularly the RAID-5 code) > that I believe are not fixed unless you're running a recent version > of -CURRENT, and I don't know whether any of those changes will be > back-ported to -STABLE, so keep this in mind. > > Likewise, there are some issues with running softupdates under > certain circumstances (even with -CURRENT), so you don't want to run > it on a particular partition unless you know that you actually need > the features it provides, and you know that you can live with the > problems. What issues with softdep? The out-of-space-panic-kaboom thing was fixed and backported to -stable, is there anything else? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 15:34:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 5323637B568 for ; Wed, 16 Feb 2000 15:34:57 -0800 (PST) (envelope-from rjs@fdy2.demon.co.uk) Received: from fdy2.demon.co.uk (fdy2.demon.co.uk [194.222.102.143]) by builder.freebsd.org (Postfix) with ESMTP id 308CF132DE for ; Wed, 16 Feb 2000 15:34:16 -0800 (PST) Received: (from rjs@localhost) by fdy2.demon.co.uk (8.8.8/8.8.8) id XAA00386; Wed, 16 Feb 2000 23:23:29 GMT (envelope-from rjs) Date: Wed, 16 Feb 2000 23:23:29 GMT Message-Id: <200002162323.XAA00386@fdy2.demon.co.uk> From: Robert Swindells To: imp@village.org Cc: freebsd-stable@FreeBSD.ORG In-reply-to: <200002161933.MAA12132@harmony.village.org> (message from Warner Losh on Wed, 16 Feb 2000 12:33:31 -0700) Subject: Re: PCMCIA insertion Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >: An IRQ is being assigned to the PCIC but no interrupts are generated. >Sadly, not all IRQs can be routed with the Libretto {5,7}0CT. IIRC, >10 worked for me. I'm using 10 for the sound chip, I'll try some others though. I think what was happening with 2.2.8-STABLE was that the boot messages made it look as if IRQ 5 was assigned to the PCIC but the cards would only be detected by the timeout routine. In 3.4-STABLE the timer is only started if no IRQ is assigned. Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 15:51: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id BD5B637B513 for ; Wed, 16 Feb 2000 15:51:06 -0800 (PST) (envelope-from rudy-bulk@monkeybrains.net) Received: from dipsy.monkeybrains.net (dipsy.monkeybrains.net [216.231.58.4]) by builder.freebsd.org (Postfix) with ESMTP id 5025C132E6 for ; Wed, 16 Feb 2000 15:50:22 -0800 (PST) Received: from monkeybrains.net (rururudy-0.dsl.speakeasy.net [216.231.57.142]) by dipsy.monkeybrains.net (8.8.8/8.8.8) with ESMTP id PAA05994 for ; Wed, 16 Feb 2000 15:56:57 -0800 (PST) (envelope-from rudy-bulk@monkeybrains.net) Message-ID: <38AB37E9.2DE98CD3@monkeybrains.net> Date: Wed, 16 Feb 2000 15:51:05 -0800 From: Rudy Rucker X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: en,pdf MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: `w' shows bogus IDLE time (sometimes) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If a user logs in, and runs no commands, they are marked as idle. They will be marked as 'idle since the last login on that tty'. For example, I have a machine with hardly any shell users. If I login 3 times, I grab ttyp5 (relatively, a high numbered tty on this box!). The last time anyone logged into ttyp5 was 27 days ago. So, `last' shows a user who logged in 1 minute ago, but `w' shows they have been idle for 27 days. It's raining, and I am bored, can you tell? Rudy 144> last | head -10 | grep monkey monkey ttyp5 216.231.57.xxx Wed Feb 16 15:43 still logged in monkey ttyp3 216.231.57.xxx Wed Feb 16 15:43 still logged in monkey ttyp2 216.231.57.xxx Wed Feb 16 15:43 still logged in monkey ttyp2 216.231.57.xxx Wed Feb 16 15:04 - 15:34 (00:30) 145> w 3:44PM up 12 days, 22:16, 7 users, load averages: 0.00, 0.01, 0.00 USER TTY FROM LOGIN@ IDLE WHAT monkey p1 xxx.dsl.s 12:57PM - w monkey p2 xxx.dsl.s 3:43PM 9 -tcsh (tcsh) monkey p3 xxx.dsl.s 3:43PM 24 -tcsh (tcsh) monkey p5 xxx.dsl.s 3:43PM 27days -tcsh (tcsh) 146> date Wed Feb 16 15:44:18 PST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 18:25:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id CBA1337B505 for ; Wed, 16 Feb 2000 18:25:33 -0800 (PST) (envelope-from spidey@anarcat.dyndns.org) Received: from anarcat.dyndns.org (phobos.IRO.UMontreal.CA [132.204.20.20]) by builder.freebsd.org (Postfix) with ESMTP id 50DBE132E2 for ; Wed, 16 Feb 2000 18:24:38 -0800 (PST) Received: by anarcat.dyndns.org (Postfix, from userid 1000) id 217721BEF; Wed, 16 Feb 2000 21:25:08 -0500 (EST) From: Spidey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14507.23555.953401.749266@anarcat.dyndns.org> Date: Wed, 16 Feb 2000 21:25:07 -0500 (EST) To: Dario Alcocer Cc: Richard Wackerbarth , freebsd-stable@freebsd.org Subject: Re: Why should I upgrade from 2.2.8 to 3.4 References: <200002160926.CAA09916@harmony.village.org> <00021604155000.08535@nomad.dataplex.net> <14507.4115.743232.801540@pino.localdomain> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Reply-To: beaupran@iro.umontreal.ca Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had this problem too. But it was not due to 3.4. :)) I successfully installed FBSD on a 386 with 3Mb of RAM! I had to use a PICOBSD boot floppy, but I did it. :)) I think the install floppies of FreeBSD are getting a little too big. We could at least keep a smaller kernel that wouldn't support all the devices, for the boxes that don't need it. This is completely off-topic, however... --- Big Brother told Dario Alcocer to write, at 13:14 of February 16: > >>>>> "Richard" == Richard Wackerbarth writes: > > Richard> Perhaps there needs to be a more emphatic public posting > Richard> to the effect that 2.2.x is "moldy" and supported only to > Richard> the extent that the few remaining users of this system > Richard> contribute patches. Unless they have COMPELLING reasons > Richard> to remain with 2.2.x, all users SHOULD UPGRADE to 3.4. > > One problem I've seen with upgrading to 3.4 is installing on > low-memory machines. The 2.2.8 install boot floppy works on an 8MB > machine, but 3.x does not; it needs at least 12MB to install. (I > wonder if it's just a problem with too many drivers in the boot > floppy. Maybe this problem could be addressed by having a smaller > kernel on the install boot floppy.) > > Anyway, I found this problem when I tried upgrading an existing 2.2.8 > firewall/router machine to 3.1, and the install failed due to this 8MB > problem. Others have run into this problem as well: > > http://www.deja.com/=dnc/[ST_rn=ps]/getdoc.xp?AN=515625181 > http://www.deja.com/=dnc/[ST_rn=ps]/getdoc.xp?AN=516009396 > > -- > Dario Alcocer // dalcocer@home.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message -- Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir Lofofora To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 18:43:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 1DFA237B61B for ; Wed, 16 Feb 2000 18:43:35 -0800 (PST) (envelope-from spidey@anarcat.dyndns.org) Received: from anarcat.dyndns.org (phobos.IRO.UMontreal.CA [132.204.20.20]) by builder.freebsd.org (Postfix) with ESMTP id 710CD132EB for ; Wed, 16 Feb 2000 18:42:51 -0800 (PST) Received: by anarcat.dyndns.org (Postfix, from userid 1000) id 793071BEF; Wed, 16 Feb 2000 21:43:01 -0500 (EST) From: Spidey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14507.24625.855271.39462@anarcat.dyndns.org> Date: Wed, 16 Feb 2000 21:42:57 -0500 (EST) To: freebsd-stable@FreeBSD.ORG Subject: Re: Why should I upgrade from 2.2.8 to 3.4 References: <200002160926.CAA09916@harmony.village.org> <00021604155000.08535@nomad.dataplex.net> <14507.4115.743232.801540@pino.localdomain> <14507.23555.953401.749266@anarcat.dyndns.org> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Reply-To: beaupran@iro.umontreal.ca Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hum.. Sorry there.. I forwarded this to the wrong list.. Apologies, The AnarCat -- Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir Lofofora To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Feb 16 22: 3: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id CBF4237B564 for ; Wed, 16 Feb 2000 22:02:59 -0800 (PST) (envelope-from rbezuide@oskar.dev.nanoteq.co.za) Received: from oskar.dev.nanoteq.co.za (oskar.nanoteq.co.za [196.7.114.5]) by builder.freebsd.org (Postfix) with ESMTP id C2312132F0 for ; Wed, 16 Feb 2000 22:02:11 -0800 (PST) Received: (from rbezuide@localhost) by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id HAA05278; Thu, 17 Feb 2000 07:59:19 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <200002170559.HAA05278@oskar.dev.nanoteq.co.za> Subject: Re: ESS1869 sound card problem.... In-Reply-To: from Ronald Klop at "Feb 16, 2000 6:37:41 pm" To: ronald@node11a94.a2000.nl (Ronald Klop) Date: Thu, 17 Feb 2000 07:59:19 +0200 (SAT) Cc: val@nensi.net, changtze@hotmail.com, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... I have a ESS1869 on a 4.0-current machine of a few days old ... and I still only get sound from the right channel only :( Reinier > > > > > > I have this ESS1869 ver 1.0.10 sound card and having problem to configure > > > it. I'm taking this from my windowz settings. > > > > > > > There were many problems with my ESS688 Sound Card with both > > snd and pcm drivers. I have installed patched pcm driver from > > http://home.jp.freebsd.org/~sanpei/ and my card working > > fine now! > > > > Thanks for developers! > > > > Only one problem present in this time - sometimes kde mixer > > don't work properly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 4:23:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id CFADB37B6C1 for ; Thu, 17 Feb 2000 04:23:39 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id C1FD41233A for ; Thu, 17 Feb 2000 13:23:26 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: Date: Thu, 17 Feb 2000 13:22:55 +0100 To: freebsd-stable@freebsd.org From: Brad Knowles Subject: Initial performance testing w/ postmark & softupdates... Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, There have been some discussions going on over on the postfix-users mailing list about how much performance is really hurt by synchronous meta-data operations, and therefore how much additional performance you could expect to get out of a system that was designed to try to eliminate them. Well, I've got a Dell 1300 that I've recently installed with FreeBSD 3.4-STABLE, and I thought I'd run some benchmarks. Please keep in mind that these numbers are *very* preliminary, and that they measure only one aspect of the performance of this system. Nevertheless, I find them quite enlightening, and thought that they were good enough that I should share them with you here. Without further ado, here is the message as I sent it to postfix-users: Folks, Some of you were wondering just how much of a difference eliminating synchronous meta-data operations really could make. Well, I just got back my first set of preliminary testing data with the "postmark" benchmark program from Network Appliance, and I thought I'd share it with you. I do not pretend that what I've done so far is an accurate representation of the kind of speedup you should see, or that this is an accurate simulation of how postfix would actually run on this machine. This is just an example (and a preliminary one at that) of the kind of speedup that you might potentially see, and perhaps give you some kind of idea how much of a difference this really can make under some circumstances. If you go to , you'll see some data I've collected so far, including both the data from original paper from NetApp, plus some of my own testing. This has not (yet) been updated to incorporate my latest results, which are being summarized here for the first time. The machine I tested on is a Dell 1300 PowerEdge dual-CPU machine with Pentium III processors @ 450Mhz and 1MB L2 cache each, 1GB of ECC RAM, and running FreeBSD 3.4-STABLE (I cvsup'ed on Tuesday, so it's pretty recent ;-). Hardware-wise, the base machine is identical to the "2xP3/FreeBSD" entry that is already in the results at the page I listed above, although that machine was a production server at the time and this machine was tested while otherwise totally idle. The disk drive I've tested with so far is also different -- instead of an IBM model, it's a Quantum Atlas IV 9GB WLS 0707 (80MB/s max), connected to the internal AIC-7890 controller. I tested both with and without softupdates. In the postmark results reported by NetApp, there are three tests that are run, with varying numbers of files to be used and transactions to be performed. The first test uses 1000 files (in the same directory) and 50,000 transactions, the second test uses 20,000 files (in the same directory) and 50,000 transactions, the third test uses 20,000 files (in the same directory) and 100,000 transactions, and at the suggestion of Matt Dillon, I also do a fourth test with 20,000 files and 100,000 transactions, and I also use 100 subdirectories. In this summary that I am posting to this list, I will provide the UFS, TMPFS, and NFS/F630 results, in addition to the ones I just generated. This will help you get a better feel for the kinds of performance we're talking about. The last two colums will be the new results, and I will list the non-softupdates data first ("2xP3/FreeBSD") and the softupdates-enabled data second ("+SOFT"): Test 1: 1000 files & 50,000 transactions UFS TMPFS NFS/F630 2xP3/FreeBSD +SOFT ------ ----- -------- ------------ ------- TPS 36 2000 253 54 458 Read 115.67 4880 799.91 171.77 1495.04 Write 118.27 7330 817.89 175.64 1525.76 Test 2: 20,000 files & 50,000 transactions UFS TMPFS NFS/F630 2xP3/FreeBSD +SOFT ------ ----- -------- ------------ ------- TPS 15 438 176 35 142 Read 29.93 663.64 383.41 67.30 318.81 Write 54.22 1530 694.58 121.91 577.55 Test 3: 20,000 files & 100,000 transactions UFS TMPFS NFS/F630 2xP3/FreeBSD +SOFT ------ ----- -------- ------------ ------- TPS 335 169 35 139 Read 613.03 446.69 85.86 379.79 Write 1160 617.45 118.69 524.98 Test 4: 20,000 files/100 subdirectories & 100,000 transactions UFS TMPFS NFS/F630 2xP3/FreeBSD +SOFT ------ ----- -------- ------------ ------- TPS 25 86 Read 60.92 237.10 Write 84.21 327.75 TPS = Transactions Per Second Read = Data read per second (in kilobytes) Write = Data written per second (in kilobytes) Now, if there is any doubt left in anyone's mind, I'd like to hear it. Please note that I came very close to the performance of the previous generation high-end (and extremely expensive) NFS server box on a *SINGLE* lower-speed commodity hard drive, when I enabled softupdates. I don't guarantee that you'll all see 3-5x performance increases if you enable softupdates on your /var/spool/postfix directories, but this should at least give you some kind of idea of how much of a difference optimizing synchronous meta-data operations can make. Now, just think what you could do if you could re-write the application to avoid the synchronous meta-data operations altogether, instead of depending on the filesystem and the OS to try to optimize them out of existance? I'm going to be doing my own memory-based filesystem checks, to get an idea of what the real upper bound of performance is on this hardware. I'll let you know more as I do it myself. I've also got an extremely expensive mainframe-style drive array that is going to be attached to this machine next week, and I'll run some benchmarks on it as well. I'd be willing to bet that I can beat the snot out of NFS on a softupdates-enabled filesystem that is on a software-striped vinum volume, and I could do it at *much* lower cost, too. In fact, I'd be willing to bet that I could put together an NFS server based on that kind of configuration and that I could beat the snot out of the best that NetApp has to give. This is pretty good stuff. I think I should post this to the freebsd-stable list as well. In fact, I think I will. -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 4:51:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from luxren2.boostworks.com (luxren2.boostworks.com [194.167.81.214]) by hub.freebsd.org (Postfix) with ESMTP id 485E837B6B6 for ; Thu, 17 Feb 2000 04:51:42 -0800 (PST) (envelope-from root@boostworks.com) Received: from boostworks.com (root@oldrn.luxdev.boostworks.com [192.168.1.99]) by luxren2.boostworks.com (8.9.1/8.9.1) with ESMTP id NAA89047; Thu, 17 Feb 2000 13:51:18 +0100 (CET) Message-Id: <200002171251.NAA89047@luxren2.boostworks.com> Date: Thu, 17 Feb 2000 13:51:10 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@boostworks.com Subject: Re: xl0 packet dropping, still To: cokane@one.net Cc: stable@FreeBSD.ORG In-Reply-To: <20000216161953.A5237@evil.2y.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16 Feb, Coleman Kane was caught persisting on: > Can this be fixed, or is it caused by a deficiency in the hardware? > > --cokane > Wait for 4.0 to have it fixed or the fix MFC'ed to stable. From a personal POV, I have got too much problems with 3com like cards that i now let Win$ users suffer with that brand (anyway, they keep going stealing me good cards when I'm not looking). I would recommand that you switch to an (Ex-)Digital 2114x or Intel 8255[89] based one. I would favor the Intel chip since it provides the lowest level of interrupts/packets processed, hence a lower system load. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 5: 2:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (Postfix) with ESMTP id 01D3837B70F for ; Thu, 17 Feb 2000 05:02:06 -0800 (PST) (envelope-from steveroo@mothra.bri.hp.com) Received: from mothra.bri.hp.com (mothra.bri.hp.com [15.144.1.185]) by atlrel2.hp.com (Postfix) with ESMTP id 5D4391506 for ; Thu, 17 Feb 2000 08:02:04 -0500 (EST) Received: from localhost (steveroo@localhost) by mothra.bri.hp.com with ESMTP (8.9.3 (PHNE_18979)/8.7.1) id NAA25991; Thu, 17 Feb 2000 13:01:13 GMT Date: Thu, 17 Feb 2000 13:01:13 +0000 (GMT) From: Stephen Roome To: Brad Knowles Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Brad Knowles wrote: > Well, I've got a Dell 1300 that I've recently installed with > FreeBSD 3.4-STABLE, and I thought I'd run some benchmarks. Please > keep in mind that these numbers are *very* preliminary, and that they > measure only one aspect of the performance of this system. > Nevertheless, I find them quite enlightening, and thought that they > were good enough that I should share them with you here. Although these figures are good for a comparison with a pre-softupdates FreeBSD or say, Linux ext2/ext3 (does ext3 it exist yet?), it would be nice to have similar sort of benchmarks to compare with say, HPUX lvm, Solaris, or comparisons between FreeBSD+vinum+softupdates and Whatever+Veritas etc. Benchmarks that are appropriate to guage a comparison with some of the *slightly more expensive* commercial Unix boxes would be good for a number of reasons, not least to show your clients why you didn't spened $1m on commercial Unix no.1 for them but downloaded some "slow unreliable hunk of freeware rubbish that we can't bank our business on". Perhaps it would also improve our chances of finding things like Oracle ported to FreeBSD if commercial customers found out that FreeBSD has better disk i/o than the box they were about to spend far more money on ? Then again, maybe not... it's just an idea or maybe only my mad ramblings. Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 5:10:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 8D65F37B6CC for ; Thu, 17 Feb 2000 05:10:35 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id C6005CBB3 for ; Thu, 17 Feb 2000 14:10:30 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Thu, 17 Feb 2000 14:10:04 +0100 To: freebsd-stable@FreeBSD.ORG From: Brad Knowles Subject: Re: Initial performance testing w/ postmark & softupdates... Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:22 PM +0100 2000/2/17, Brad Knowles wrote: > I'm going to be doing my own memory-based filesystem checks, to get > an idea of what the real upper bound of performance is on this hardware. > I'll let you know more as I do it myself. Just got my own memory-based filesystem (MFS) numbers with the same FreeBSD 3.4-STABLE machine. Let's compare these to the NetApp TMPFS, NetApp NFS/F630, and +SOFT: Test 1: 1000 files & 50,000 transactions MFS TMPFS NFS/F630 +SOFT ------ ----- -------- ------- TPS 1724 2000 253 458 Read 5488.64 4880 799.91 1495.04 Write 5611.52 7330 817.89 1525.76 Test 2: 20,000 files & 50,000 transactions MFS TMPFS NFS/F630 +SOFT ------ ----- -------- ------- TPS 228 438 176 142 Read 504.14 663.64 383.41 318.81 Write 913.29 1530 694.58 577.55 Test 3: 20,000 files & 100,000 transactions UFS TMPFS NFS/F630 +SOFT ------ ----- -------- ------- TPS 228 335 169 139 Read 606.47 613.03 446.69 379.79 Write 838.31 1160 617.45 524.98 Test 4: 20,000 files/100 subdirectories & 100,000 transactions MFS TMPFS NFS/F630 +SOFT ------ ----- -------- ------- TPS 1333 86 Read 3471.36 237.10 Write 4802.56 327.75 TPS = Transactions Per Second Read = Data read per second (in kilobytes) Write = Data written per second (in kilobytes) Hmm. That sure makes me wonder what the *HECK* they were using for their TMPFS tests! That said, notice that performance on MFS goes up *dramatically* when you use subdirectories, implying that directory search overhead at those kinds of speeds is quite significant. Also note that their TMPFS and their NFS/F630 tests slowed down between test #2 and test #3, while my MFS test hardly changed at all (reads were a bit faster, and writes were slightly slower). -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 5:15:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 3191637B717 for ; Thu, 17 Feb 2000 05:15:22 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 1F827CB20; Thu, 17 Feb 2000 14:15:17 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Thu, 17 Feb 2000 14:14:52 +0100 To: Stephen Roome From: Brad Knowles Subject: Re: Initial performance testing w/ postmark & softupdates... Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:01 PM +0000 2000/2/17, Stephen Roome wrote: > Although these figures are good for a comparison with a >pre-softupdates FreeBSD > or say, Linux ext2/ext3 (does ext3 it exist yet?), it would be nice to have > similar sort of benchmarks to compare with say, HPUX lvm, Solaris, or > comparisons between FreeBSD+vinum+softupdates and Whatever+Veritas etc. Yeah, on a broader scale, that would be nice. But I don't have all that kind of hardware, and I don't have the time to do all that much benchmarking. I was primarily looking at what kind of performance hit you take when you get lots of synchronous meta-data updates, and what kind of performance improvement you might theoretically be able to see if you could re-architect your application so as to avoid synchronous meta-data operations whenever possible. That said, I'm willing to collect and centralize benchmarks run on a variety of platforms, but you'll have to use the script I provide to generate the data, and you'll have to give me details about the hardware configuration. If you've made any kernel changes or performance tweaks, you'll need to let me know about those, too. I'll be updating my page at with the new information, and details about what requirements have to be satisfied before I will accept benchmark data from others to be incorporated on the page. -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 6:14:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 55EAF37B6BD for ; Thu, 17 Feb 2000 06:14:45 -0800 (PST) (envelope-from steveroo@mothra.bri.hp.com) Received: from mothra.bri.hp.com (mothra.bri.hp.com [15.144.1.185]) by palrel1.hp.com (Postfix) with ESMTP id 4E2298D8 for ; Thu, 17 Feb 2000 06:14:44 -0800 (PST) Received: from localhost (steveroo@localhost) by mothra.bri.hp.com with ESMTP (8.9.3 (PHNE_18979)/8.7.1) id OAA26945; Thu, 17 Feb 2000 14:13:53 GMT Date: Thu, 17 Feb 2000 14:13:52 +0000 (GMT) From: Stephen Roome To: Brad Knowles Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That said, I'm willing to collect and centralize benchmarks run > on a variety of platforms, but you'll have to use the script I > provide to generate the data, and you'll have to give me details > about the hardware configuration. If you've made any kernel changes > or performance tweaks, you'll need to let me know about those, too. If we have a good benchmark that provides useful information I can run it on a large amount of different HP machines. Then again, it might be worth considering the possibility of using "industry standard" benchmarks - if indeed there are any that are relevant. e.g. http://www.unixsolutions.hp.com/products/servers/lclass/performance.html (I've never seen or used one of these myself, maybe out of the range ?) Any standard database benchmark might be handy.. more information might be useful at : http://linux.cis.nctu.edu.tw/docs/mysql/db-perf.html Anyway, I was pleased to see your original benchmarks anyway, sorry if it sounded otherwise. Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 7:13:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 8965637B6BD for ; Thu, 17 Feb 2000 07:13:45 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 6A922122E0; Thu, 17 Feb 2000 16:13:38 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Thu, 17 Feb 2000 15:37:50 +0100 To: Stephen Roome From: Brad Knowles Subject: Re: Initial performance testing w/ postmark & softupdates... Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:13 PM +0000 2000/2/17, Stephen Roome wrote: > If we have a good benchmark that provides useful information I can >run it on a > large amount of different HP machines. Then again, it might be worth > considering the possibility of using "industry standard" benchmarks - if > indeed there are any that are relevant. When you're looking at the performance of a machine and how it may work as a mail system, I think postmark is at least a decent benchmark. It's not the only one I'd use, but it's certainly one of the main ones. I'd also use rawio (FreeBSD only, unfortunately) to give me some pretty good ideas of what kind of performance I can expect from the underlying hardware, and I haven't really made up my mind with regards to the others. > http://www.unixsolutions.hp.com/products/servers/lclass/performance.html > (I've never seen or used one of these myself, maybe out of the range ?) Uh, yes. Slightly out of range, indeed. We don't have anything here that would be comparable, save possibly one machine. The Dell 1300 I ran that with was a pretty low-end machine, relatively speaking. Maybe the equivalent of a D-Class HP box. > http://linux.cis.nctu.edu.tw/docs/mysql/db-perf.html I personally am not really interested in database benchmarks. I'm looking more at disk performance, both raw and filesystem, in a USENET news/mail spool context. > Anyway, I was pleased to see your original benchmarks anyway, sorry if it > sounded otherwise. Not a problem. Thanks! -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 7:33:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hydrant.intranova.net (hydrant.intranova.net [209.201.95.10]) by hub.freebsd.org (Postfix) with SMTP id C47D437B76C for ; Thu, 17 Feb 2000 07:33:40 -0800 (PST) (envelope-from oogali@intranova.net) Received: (qmail 91958 invoked from network); 17 Feb 2000 15:32:34 -0000 Received: from localhost (oogali@127.0.0.1) by hydrant.intranova.net with SMTP; 17 Feb 2000 15:32:34 -0000 Date: Thu, 17 Feb 2000 10:32:34 -0500 (EST) From: Omachonu Ogali To: Coleman Kane Cc: stable@freebsd.org Subject: Re: xl0 packet dropping, still In-Reply-To: <20000215210704.A969@evil.2y.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had problems with the xl0 devices dropping packets and timing out, so I reverted to using an Intel EtherExpress Pro/100 (fxp0). On Tue, 15 Feb 2000, Coleman Kane wrote: > Well, I switched my xl0 ethernet carc, but I am still recieving > messages saying that there are packets being dropped. Sometimes this > results in the card being shut down. > > --cokane > -- +-------------------------------------------------------------------------+ | Omachonu Ogali oogali@intranova.net | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 8:32:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id 9515937B734 for ; Thu, 17 Feb 2000 08:32:33 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id LAA09594; Thu, 17 Feb 2000 11:32:32 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id LAA07138; Thu, 17 Feb 2000 11:32:31 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200002171632.LAA07138@rtfm.newton> Subject: Re: xl0 packet dropping, still In-Reply-To: from Omachonu Ogali at "Feb 17, 2000 10:32:34 am" To: Omachonu Ogali Date: Thu, 17 Feb 2000 11:32:31 -0500 (EST) Cc: stable@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Well, I switched my xl0 ethernet carc, but I am still recieving => messages saying that there are packets being dropped. Sometimes this => results in the card being shut down. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 9:10:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id E270737B760 for ; Thu, 17 Feb 2000 09:10:39 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 12LURo-00033S-00 for stable@freebsd.org; Thu, 17 Feb 2000 12:10:36 -0500 Date: Thu, 17 Feb 2000 12:10:35 -0500 From: Peter Radcliffe To: stable@freebsd.org Subject: Re: xl0 packet dropping, still Message-ID: <20000217121035.A11090@pir.net> Mail-Followup-To: stable@freebsd.org References: <200002171632.LAA07138@rtfm.newton> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002171632.LAA07138@rtfm.newton>; from mi@kot.ne.mediaone.net on Thu, Feb 17, 2000 at 11:32:31AM -0500 X-fish: < Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin probably said: > Omachonu Ogali once stated: > =I had problems with the xl0 devices dropping packets and timing out, so > =I reverted to using an Intel EtherExpress Pro/100 (fxp0). > > FWIW, a CompUSA clerk told me, those don't work well in, say, AMD > based machines... IMHO, I would say that CompUSA clerk has no idea what he/she is talking about (shocker). I've got 5 test PCs at work with AMD processors, Intel Pro100 cards and gig ether cards, some running freebsd some windows. In both cases I've had zero problems with them (we use them for gig ether testing so the traffic is nontrivial). I've been using pro/100s for a few years in lots of different machines and as far as I've seen they Just Work from 10bT/hdx to 100bTfdx. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 9:33:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id F10C437B7F1 for ; Thu, 17 Feb 2000 09:33:44 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id LAA24594; Thu, 17 Feb 2000 11:33:36 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-79.max1.wa.cyberlynk.net(207.227.118.79) by peak.mountin.net via smap (V1.3) id sma024592; Thu Feb 17 11:33:23 2000 Message-Id: <3.0.3.32.20000217113310.00a5cdd0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 17 Feb 2000 11:33:10 -0600 To: Mikhail Teterin From: "Jeffrey J. Mountin" Subject: Re: xl0 packet dropping, still Cc: stable@FreeBSD.ORG In-Reply-To: <200002171632.LAA07138@rtfm.newton> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:32 AM 2/17/00 -0500, Mikhail Teterin wrote: >Omachonu Ogali once stated: > >=I had problems with the xl0 devices dropping packets and timing out, so >=I reverted to using an Intel EtherExpress Pro/100 (fxp0). > >FWIW, a CompUSA clerk told me, those don't work well in, say, AMD >based machines... The Intel? Did you get a pinch of salt to go with that advice? ;) Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 10:37:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 381DC37B7D1 for ; Thu, 17 Feb 2000 10:37:40 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 12LVnz-000IHN-00; Thu, 17 Feb 2000 10:37:35 -0800 Date: Thu, 17 Feb 2000 10:37:32 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Brad Knowles Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Brad Knowles wrote: ... > Hmm. That sure makes me wonder what the *HECK* they were using > for their TMPFS tests! That said, notice that performance on MFS ... Uhhh... the paper says that an Ultra 1/170 running Solaris 2.5. That is an old system. I'm not sure how comparing benchmark results from 1998 with current hardware is relevant at all. Postmark is performance is influenced more by the disk & controller used, rather than the OS. In fact, CPU is not much of any issue either. In fact, SMP is probably slowing the results down! You also compare results versus a NetApp F630. I hope you realize that these are VERY old units. They came with Wide SCSI disks (not Ultra, not Ultra2) for instance. It doesn't mention, but I expect the test was only done over 100BaseT. In that case, the 100BaseT network would have been the limiting factor. Also, the existing base model NetApp, the F720 has over twice the performance of the F630! And I've been told that NetApp doesn't really sell anything but the high-end F760, which has over twice the performance of the F720. The entire F700 is already pretty old, and is scheduled to be replaced by a new series this year. So please, postmark is a useful tool. See my previous e-mails about postmark+softupdates. But comparing results when a two year old document is meaningless. Especially with disk/controller performance doubling every year or so. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 11:19:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from [192.168.1.254] (proxy.tigertown.k12.mo.us [204.185.250.124]) by hub.freebsd.org (Postfix) with SMTP id 350F737B6E8 for ; Thu, 17 Feb 2000 11:19:36 -0800 (PST) (envelope-from andy@tigertown.k12.mo.us) Received: from admin by [192.168.1.254];Thu, 17 Feb 2000 19:19:30 GMT Message-ID: <005d01bf797a$76ffa660$e7b46ad1@admin> From: "Andy Rowland" To: References: <200002171632.LAA07138@rtfm.newton> <20000217121035.A11090@pir.net> Subject: Re: xl0 packet dropping, still Date: Thu, 17 Feb 2000 13:09:02 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm just running a few machines...just 400 or so and 10 servers, but of all the cards I use, the Intel Pro/100s (E100B) are the best of the bunch. AMD, Intel, doesn't matter. --Andy Rowland Grand River Network andy@tigertown.k12.;mo.us ----- Original Message ----- From: "Peter Radcliffe" To: Sent: Thursday, February 17, 2000 11:10 AM Subject: Re: xl0 packet dropping, still > Mikhail Teterin probably said: > > Omachonu Ogali once stated: > > =I had problems with the xl0 devices dropping packets and timing out, so > > =I reverted to using an Intel EtherExpress Pro/100 (fxp0). > > > > FWIW, a CompUSA clerk told me, those don't work well in, say, AMD > > based machines... > > IMHO, I would say that CompUSA clerk has no idea what he/she is > talking about (shocker). > > I've got 5 test PCs at work with AMD processors, Intel Pro100 cards > and gig ether cards, some running freebsd some windows. In both cases > I've had zero problems with them (we use them for gig ether testing so > the traffic is nontrivial). > > I've been using pro/100s for a few years in lots of different machines > and as far as I've seen they Just Work from 10bT/hdx to 100bTfdx. > > P. > > -- > pir pir@pir.net pir@net.tufts.edu > > > > 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-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 11:35:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 32C5137B7AF for ; Thu, 17 Feb 2000 11:35:25 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id EAA551232C; Thu, 17 Feb 2000 20:35:05 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Thu, 17 Feb 2000 20:33:28 +0100 To: Tom From: Brad Knowles Subject: Re: Initial performance testing w/ postmark & softupdates... Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:37 AM -0800 2000/2/17, Tom wrote: > Uhhh... the paper says that an Ultra 1/170 running Solaris 2.5. That is > an old system. I've run tmpfs tests with postmark on Ultra 2 and Ultra 5 systems with faster CPUs and newer versions of the OS, and they didn't run anywhere *NEAR* that fast (I've got an Ultra 5 I'm testing right now). Heck, one person told me he had an older laptop running Linux with ReiserFS and he was getting better throughput going to disk than Sun did with tmpfs! Again, I have to seriously wonder what they were really testing on. > I'm not sure how comparing benchmark results from 1998 with current > hardware is relevant at all. Postmark is performance is influenced more > by the disk & controller used, rather than the OS. In fact, CPU is not > much of any issue either. In fact, SMP is probably slowing the results > down! My results clearly show that there is a huge filesystem effect, and anything that could prevent operations from getting put into the queue to be flushed to disk would have a similar effect. OS/filesystem implementation efficiency could not *help* but have a huge impact on this. > You also compare results versus a NetApp F630. I hope you realize that > these are VERY old units. Yes, I know that they are the previous generation devices, I've been told as much by folks from NetApp, when I was previously posting results from testing with postmark. I also know just how incredibly bloody expensive these things are, and how I did quite a good job of coming pretty close to their level of performance on a pretty low-end FreeBSD server with a *SINGLE* low-speed Quantum Atlas IV, and all I had to do was turn on softupdates. I also notice that softupdates on a slow disk beat out Linux/ext2fs+async on a single CPU system that was otherwise similarly configured, except for the DPT SmartRAID V controller that the Linux server had to it's advantage, and the 5-way RAID-5 volume that it was writing to. > They came with Wide SCSI disks (not Ultra, not > Ultra2) for instance. It doesn't mention, but I expect the test was only > done over 100BaseT. In that case, the 100BaseT network would have been > the limiting factor. Yes, it was 100BaseT, but I don't see anything in any of these tests that should have come anywhere close to pushing the limits of 100BaseT for speed -- ~400KBps read and ~600KBps write, with ~170 TPS shouldn't come anywhere close to network bottlenecks of 12.5MBps capacity. > Also, the existing base model NetApp, the F720 has > over twice the performance of the F630! And I've been told that NetApp > doesn't really sell anything but the high-end F760, which has over twice > the performance of the F720. The entire F700 is already pretty old, and > is scheduled to be replaced by a new series this year. "Twice the performance." I'm sorry, that term is just a little too vague for me. Can you quantify these numbers in terms of transactions per second, data read per second, and data written per second? > So please, postmark is a useful tool. See my previous e-mails about > postmark+softupdates. But comparing results when a two year old document > is meaningless. Especially with disk/controller performance doubling > every year or so. Their performance may theoretically be doubling every year or so, but the machine I tested with is not anywhere close to what I would consider to be a high-end server, and it definitely did not have the advantage of a vinum nine-way striped filesystem on 10kRPM disks or anything like that, and yet I still came pretty close to their level of performance. Let me get rawio working on this machine, and we can compare the low-level hardware performance of this disk device to the previous four-way 10kRPM vinum striped device I used for my previous benchmarking, and then we can extrapolate as to what might happen on that system if we enabled softupdates on it. I'd be willing to bet that it would beat the crap out of the F630, and if I was allowed to do that on a nine-way striped 10kRPM volume, I could do some pretty good damage against the current crop of NFS servers. Take a look at what Joe Greco is talking about doing for his next-generation USENET news spool server (see message-id <38ac286b$0$86644@news.execpc.com> in news.software.nntp), and tell me that this wouldn't beat the crap out of NetApp as an NFS server. -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 12:28: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id BF1F237B6D7 for ; Thu, 17 Feb 2000 12:28:02 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 12LXWl-000M8h-00; Thu, 17 Feb 2000 12:27:55 -0800 Date: Thu, 17 Feb 2000 12:27:52 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Brad Knowles Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Brad Knowles wrote: > > I'm not sure how comparing benchmark results from 1998 with current > > hardware is relevant at all. Postmark is performance is influenced more > > by the disk & controller used, rather than the OS. In fact, CPU is not > > much of any issue either. In fact, SMP is probably slowing the results > > down! > > My results clearly show that there is a huge filesystem effect, > and anything that could prevent operations from getting put into the > queue to be flushed to disk would have a similar effect. > OS/filesystem implementation efficiency could not *help* but have a > huge impact on this. Not really. You could just use async updates instead of softupdates. Or an OS that uses async updates. Write caching metadata is always faster than re-ordering it intelligently. ... > I also notice that softupdates on a slow disk beat out > Linux/ext2fs+async on a single CPU system that was otherwise > similarly configured, except for the DPT SmartRAID V controller that > the Linux server had to it's advantage, and the 5-way RAID-5 volume > that it was writing to. Perhaps. Or it was the rather new SmartRAID V driver. Or it was the card (there are many different SmartRAID V) models. Or the array was optimized for sequentional io, instead of random io, not that RAID5 is ever optimal for random io to begin with. > > They came with Wide SCSI disks (not Ultra, not > > Ultra2) for instance. It doesn't mention, but I expect the test was only > > done over 100BaseT. In that case, the 100BaseT network would have been > > the limiting factor. > > Yes, it was 100BaseT, but I don't see anything in any of these > tests that should have come anywhere close to pushing the limits of > 100BaseT for speed -- ~400KBps read and ~600KBps write, with ~170 TPS > shouldn't come anywhere close to network bottlenecks of 12.5MBps > capacity. The rates reported by postmark are aggregates. I've noticed that actually throughput over the tests to vary by a 100% or more during the tests. Besides, latency of 100BaseT is rather poor too. ... > > So please, postmark is a useful tool. See my previous e-mails about > > postmark+softupdates. But comparing results when a two year old document > > is meaningless. Especially with disk/controller performance doubling > > every year or so. > > Their performance may theoretically be doubling every year or so, > but the machine I tested with is not anywhere close to what I would > consider to be a high-end server, and it definitely did not have the > advantage of a vinum nine-way striped filesystem on 10kRPM disks or > anything like that, and yet I still came pretty close to their level > of performance. Not just their (NetApp) performance. Disks and controllers in general are a lot faster than they were two years ago. Please forget all those old results. My point here is not to defend NetApp, but to say that old results are meaningless. Big deal. You managed to exceed some results published over two years ago. I bet my TV can exceed the postmark scores you published today, two years from now. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 12:35:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from malasada.lava.net (malasada.lava.net [199.222.42.2]) by hub.freebsd.org (Postfix) with ESMTP id 0D87437B823 for ; Thu, 17 Feb 2000 12:35:18 -0800 (PST) (envelope-from cliftonr@lava.net) Received: from localhost (3671 bytes) by malasada.lava.net via sendmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Thu, 17 Feb 2000 10:35:17 -1000 (HST) (Smail-3.2.0.106 1999-Mar-31 #3 built 1999-Dec-7) Date: Thu, 17 Feb 2000 10:35:17 -1000 From: Clifton Royston To: Brad Knowles Cc: Tom , freebsd-stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... Message-ID: <20000217103516.C19043@lava.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 17, 2000 at 08:33:28PM +0100, Brad Knowles wrote: > At 10:37 AM -0800 2000/2/17, Tom wrote: > > Uhhh... the paper says that an Ultra 1/170 running Solaris 2.5. That is > > an old system. > > I've run tmpfs tests with postmark on Ultra 2 and Ultra 5 systems > with faster CPUs and newer versions of the OS, and they didn't run > anywhere *NEAR* that fast (I've got an Ultra 5 I'm testing right > now). Heck, one person told me he had an older laptop running Linux > with ReiserFS and he was getting better throughput going to disk than > Sun did with tmpfs! > > Again, I have to seriously wonder what they were really testing on. I also found that a bit weird, because from the squid list, I had some correspondence with a guy who'd gotten absolutely *horrible* results benchmarking Squid on the Solaris Ultra 1 tmpfs. (Down at the level of what newer machines saw for throughput to disk file systems.) [other comments excerpted] ... > Let me get rawio working on this machine, and we can compare the > low-level hardware performance of this disk device to the previous > four-way 10kRPM vinum striped device I used for my previous > benchmarking, and then we can extrapolate as to what might happen on > that system if we enabled softupdates on it. I'd be willing to bet > that it would beat the crap out of the F630, and if I was allowed to > do that on a nine-way striped 10kRPM volume, I could do some pretty > good damage against the current crop of NFS servers. I guess the real question as to whether that is a fair comparison, is whether softupdates is getting to the level of predictability and absolutely 100% recoverability for unexpected shutdowns or crashes which is expected of the current crop of NFS servers. I lost around 30GB of Usenet last year via trying out softupdates. It wasn't valuable data - "just Usenet" - but it did cost us some significant downtime failing to fsck it and eventually having to newfs and reinstall the configuration. I know people are saying it's come a long way recently, but I haven't heard anybody yet ready to swear you can pull the plug on the server, disk and all, plug it back in, and have it restart and fsck without errors or manual intervention in a reasonable period of time. That's the kind of performance that a Netapp or an EMC Celerra is currently promising. > Take a look at what Joe Greco is talking about doing for his > next-generation USENET news spool server (see message-id > <38ac286b$0$86644@news.execpc.com> in news.software.nntp), and tell > me that this wouldn't beat the crap out of NetApp as an NFS server. I'll take a look. Joe always has interesting things to say; but I don't know that a news spool server necessarily has the same design priorities as an NFS server. Again, not saying the idea is unworkable, just urging a little caution. -- Clifton -- Clifton Royston -- LavaNet Systems Architect -- cliftonr@lava.net The named which can be named is not the Eternal named. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 12:38:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from maytag.microtech.com (maytag.microtech.com [192.83.234.66]) by hub.freebsd.org (Postfix) with ESMTP id BBBB837B846 for ; Thu, 17 Feb 2000 12:38:03 -0800 (PST) (envelope-from dan@microtech.com) Received: from microtech.com (192.83.234.106) by maytag.microtech.com (Worldmail 1.3.167) for freebsd-stable@freebsd.org; 17 Feb 2000 12:38:26 -0800 Message-ID: <38AC5C40.C82D0133@microtech.com> Date: Thu, 17 Feb 2000 12:38:24 -0800 From: Dan the Man Organization: Microtech Systems X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: gettytab question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe someone out there can shed some light on this for me. My 3.4 system (right off of the CD) seems to be ignoring the 'if' and 'lm' fields in /etc/gettytab. Everything I have read indicates that what I am doing should work, and the 'im' field works fine. There don't appear to be any later entries in the file that override what I have specified in the default. Here's what I've got, anybody have any ideas? default:\ :cb:ce:ck:lc:fd#1000:sp#1200:if=/etc/issue:\ :lm=Please log in\072 :im=\r\n\ +--------------------------+\r\n\ | Welcome to Capricorn.org |\r\n\ +--------------------------+\r\n\r\n: (now you all know the location of my secret lair) -Dan ---------------------------------------------------------------------------- Now I'm concentrating on a specific tank battle toward the end of World War II! _/ My opinions do not necessarily reflect those of my employer, \_ \ ISP, friends, family, or any other carbon-based life forms. / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 12:54:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id A008637B7F3 for ; Thu, 17 Feb 2000 12:54:24 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 80A64123BF; Thu, 17 Feb 2000 21:54:19 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Thu, 17 Feb 2000 21:52:51 +0100 To: Tom From: Brad Knowles Subject: Re: Initial performance testing w/ postmark & softupdates... Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:27 PM -0800 2000/2/17, Tom wrote: > Not really. You could just use async updates instead of softupdates. > Or an OS that uses async updates. Write caching metadata is always faster > than re-ordering it intelligently. We're getting several steps away from the primary reason I originally decided to run these benchmarks -- to get an idea of what kind of performance increase you might be able to expect if you got rid of synchronous meta-data operations altogether. Using async writes is not something I will be testing (or am interested in testing) except on OSes that do it by default. In fact, so far as I know, Linux is the only OS that does this by default, and I can't think of too many OSes that are capable of doing it at all. > Perhaps. Or it was the rather new SmartRAID V driver. Or it was the > card (there are many different SmartRAID V) models. Or the array was > optimized for sequentional io, instead of random io, not that RAID5 is > ever optimal for random io to begin with. Perhaps. That machine still isn't being used for much, so I could fire off another test that used the internal drive, and see what that gets me. I'd be willing to bet that softupdates still beats Linux ext2fs+async. > The rates reported by postmark are aggregates. I've noticed that > actually throughput over the tests to vary by a 100% or more during the > tests. They may vary by 100%, but as an average, these numbers should not be too high nor too low, and the peaks shouldn't be all that much above nor should the valleys be all that much below. However, let's assume that the average is low, and that we should increase it by 100% -- double it, in other words. Well, if we double the numbers they got, 800KBps read and 1.2MBps write still isn't anywhere close to 12.5MBps available. Unless you're telling me that the inherent problem with NFS is that it can't sustain anything more than 1/20th of the available bandwidth due to protocol and other network issues, and if that's the case then things are *far* worse for NetApp and the other NFS vendors than even I think (used to think?). If that's the case, then as far as I'm concerned we can stop the conversation right here, since I know damn good and well that I can get ~18MBps on a four-way vinum striped volume with 10kRPM disks on a AIC-7890 controller, because I did it. And even this isn't enough for the kinds of applications I have in mind. > Besides, latency of 100BaseT is rather poor too. Latency, now that's something I won't try to argue, especially when it comes to really chatty protocols like NFS. However, I see this as just one more strike against NetApp (and NFS in general), and not something to be considered in their favour. > Not just their (NetApp) performance. Disks and controllers in general > are a lot faster than they were two years ago. As I recall, the Adaptec 2940U2W and AIC-7890 controllers are pretty old themselves (the 3950U2 came after it, and now we have the Ultra3 controllers). In addition, this disk isn't coming anywhere close to what this controller is capable of -- the Quantum Atlas IV drive is several years old, old enough that I almost got one years ago for my PCI PowerMac 7200/90, which was the second generation of PowerMacintosh computers (we're now in the fifth generation). Even then, it wasn't the fastest around -- we have some ancient 4GB Seagate "Cheetah" drives that are in Sun Ultra 1 and 2 servers that we are pulling out of production because the machines are just too old and creaky (Solaris 2.5.1? Give me a break...). The machine I'm using for the tests is nowhere near top-of-the-line, either. Again, it might have been top-of-the-line two years ago, but then NetApp was building "screamers" on Alpha EV4 hardware, and with that kind of power, it should run rings around my older hardware. Let's not talk about old unless we consider that I'm using some pretty old stuff myself. > Please forget all those > old results. My point here is not to defend NetApp, but to say that old > results are meaningless. I could have put together a system like this two years ago, and then the results would have been immediately comparable. If they would have been immediately comparable then, I submit that they are immediately comparable now -- with the exception of the software improvements that have occurred in the last two years. > Big deal. You managed to exceed some results > published over two years ago. I bet my TV can exceed the postmark scores > you published today, two years from now. Perhaps. But take a top-of-the-line TV that exists today, and try to exceed the scores I published. Heck, wait two years and take a TV that was top-of-the-line two years ago, and try to exceed the results I published. I dare you. ;-) -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 13:20:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id BE26637B844 for ; Thu, 17 Feb 2000 13:20:48 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id B220B122F8; Thu, 17 Feb 2000 22:20:42 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000217103516.C19043@lava.net> References: <20000217103516.C19043@lava.net> Date: Thu, 17 Feb 2000 22:03:47 +0100 To: Clifton Royston From: Brad Knowles Subject: Re: Initial performance testing w/ postmark & softupdates... Cc: Tom , freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:35 AM -1000 2000/2/17, Clifton Royston wrote: > I guess the real question as to whether that is a fair comparison, is > whether softupdates is getting to the level of predictability and > absolutely 100% recoverability for unexpected shutdowns or crashes > which is expected of the current crop of NFS servers. I disagree that you get 100% guarantees of 100% recoverability for unexpected shutdowns or crashes. Maybe I'm wrong, but I've just seen too many weird problems with trying to write NFS data and not having it work correctly. > That's the kind of performance that a > Netapp or an EMC Celerra is currently promising. Given my past experience with NetApp and EMC, I don't buy it. However, if I were to buy it, I'd want those kinds of features on "local" drives (perhaps connected to a SAN), and I wouldn't want to waste time and effort doing them through NFS. > I'll take a look. Joe always has interesting things to say; but I > don't know that a news spool server necessarily has the same design > priorities as an NFS server. Again, not saying the idea is unworkable, > just urging a little caution. Of course, he's doing RAID-0 across the board for speed on his filesystems for news articles, and no thought given to reliability because he's got multiple servers for that kind of redundancy. However, while software RAID-5 may or may not be rock-solid under vinum, I believe that you could implement it with high-end Mylex, AMI, or DPT controllers and so long as the arrays are configured along the lines that Joe lays out and the controllers have enough battery-backed write-back cache, then you ought to be able to make RAID-5 work well enough for you. Me, I'm going to try a drive array from a competitor of EMC, and see if we can get the reliability, speed, etc... that I'd like to see. We've had some bad experiences with them so far, but then we configured that array ourselves, as opposed to having their experts come in and do it. For now, I'm willing to give them the benefit of the doubt. I'll post updates to my web pages once the benchmarks are done on the array. -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 13:25:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id C76F037B822 for ; Thu, 17 Feb 2000 13:25:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA01506; Thu, 17 Feb 2000 13:36:49 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002172136.NAA01506@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brad Knowles Cc: Clifton Royston , Tom , freebsd-stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... In-reply-to: Your message of "Thu, 17 Feb 2000 22:03:47 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Feb 2000 13:36:49 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > However, while software RAID-5 may or may not be rock-solid under > vinum, I believe that you could implement it with high-end Mylex, > AMI, or DPT controllers and so long as the arrays are configured > along the lines that Joe lays out and the controllers have enough > battery-backed write-back cache, then you ought to be able to make > RAID-5 work well enough for you. I'm not at all convinced that any of these controllers (yet) have the throughput to compete with a well-loaded software-RAID system. It's very hard to argue with the compute and data-moving power of a small pile of GHz-class processors, and very hard to put that much power on an add-in card. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 13:36:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (port-9-153.adsl.one.net [209.50.121.153]) by hub.freebsd.org (Postfix) with ESMTP id DC31537B811 for ; Thu, 17 Feb 2000 13:36:32 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id QAA11311; Thu, 17 Feb 2000 16:39:34 -0500 (EST) (envelope-from cokane) Date: Thu, 17 Feb 2000 16:39:34 -0500 From: Coleman Kane To: Mikhail Teterin Cc: Omachonu Ogali , stable@freebsd.org Subject: Re: xl0 packet dropping, still Message-ID: <20000217163934.A11257@evil.2y.net> References: <200002171632.LAA07138@rtfm.newton> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" X-Mailer: Mutt 1.0.1i In-Reply-To: <200002171632.LAA07138@rtfm.newton>; from mi@kot.ne.mediaone.net on Thu, Feb 17, 2000 at 11:35:03AM -0500 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Well, I do have an AMD based machine, but I don't see how the problem could possibly manifest itself to AMD based machines. There is no hw on the card = that takes advantage of any Intel-only stuff. In fact, the 3Com cards are used in non-x86 boxes sometimes. FWIW, I know enough about CompUSA not to believe w= hat those guys say. I have seen to many dumb responses to queries. Once, one of= them told a customer that he could probably use EDO ram in his 486, but that it wouldn't take advantage of the EDO-ness. In fact, this is a very dangerous = thing to do, and in some cases can fry your poor 486 mobo's cache. Needless to sa= y, I 1-up'd him. --cokane Mikhail Teterin had the audacity to say: >=20 > Omachonu Ogali once stated: >=20 > =3DI had problems with the xl0 devices dropping packets and timing out, so > =3DI reverted to using an Intel EtherExpress Pro/100 (fxp0). >=20 > FWIW, a CompUSA clerk told me, those don't work well in, say, AMD > based machines... >=20 > -mi >=20 --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE4rGqWERViMObJ880RASpDAJ4+DoSPxt0GZSRM3TbvnXBxSYN6JwCg19CK YcXOBXCqGNG67CxnFpfPquI= =5JuO -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 14:36:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 0809E37B514; Thu, 17 Feb 2000 14:36:47 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id ECDC012231; Thu, 17 Feb 2000 23:36:40 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200002172136.NAA01506@mass.cdrom.com> References: <200002172136.NAA01506@mass.cdrom.com> Date: Thu, 17 Feb 2000 22:49:25 +0100 To: Mike Smith From: Brad Knowles Subject: Re: Initial performance testing w/ postmark & softupdates... Cc: Clifton Royston , Tom , freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:36 PM -0800 2000/2/17, Mike Smith wrote: > I'm not at all convinced that any of these controllers (yet) have the > throughput to compete with a well-loaded software-RAID system. It's very > hard to argue with the compute and data-moving power of a small pile of > GHz-class processors, and very hard to put that much power on an add-in > card. That's certainly the argument that Greg has made fairly successfully to me, at least with regards to RAID-0 and RAID-1 (and combinations thereof). However, I'm not yet convinced that RAID-5 under vinum is reliable enough yet to fit into the same category. -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 15: 6:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from natsoft.com.au (natsoft.com.au [203.39.138.130]) by hub.freebsd.org (Postfix) with ESMTP id 0DB7037B84D for ; Thu, 17 Feb 2000 15:06:20 -0800 (PST) (envelope-from craig@natsoft.com.au) Received: from Win95.natsoft.com.au (Win95 [203.39.138.131]) by natsoft.com.au (8.8.5/8.8.5) with SMTP id KAA19848 for ; Fri, 18 Feb 2000 10:08:40 +1100 (EST) Message-ID: <38AC7E01.63D5@natsoft.com.au> Date: Fri, 18 Feb 2000 10:02:25 +1100 From: Craig Wilson Organization: National Software Pty Ltd X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Cardbus And FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry if this is not the correct list for this question, but I have already posted this on freebsd-questions and have had no response. I have looked at documentation and cannot find an answer, and I cannot search the mailing lists etc as the server is down. Could someone please advise as to whether cardbus is supported under FreeBSD 3.4-RELEASE, and if not whether it is supported in current, or if it is to be supported under FreeBSD 3.x. I have some laptops with cardbus slots and require a SCSI pccard. I have a choice between an Adaptec APA-1460 (16bit PCMCIA) or APA-1480 (32bit cardbus). Thanks in advance for any assistance. Craig Wilson National Software Pty Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 15: 9:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id E791437B7B9 for ; Thu, 17 Feb 2000 15:09:31 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id PAA18252; Thu, 17 Feb 2000 15:09:18 -0800 (PST) Date: Thu, 17 Feb 2000 15:09:18 -0800 From: Brooks Davis To: Craig Wilson Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Cardbus And FreeBSD Message-ID: <20000217150918.A17634@orion.ac.hmc.edu> References: <38AC7E01.63D5@natsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <38AC7E01.63D5@natsoft.com.au>; from craig@natsoft.com.au on Fri, Feb 18, 2000 at 10:02:25AM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [-mobile or -questions was the right place] On Fri, Feb 18, 2000 at 10:02:25AM +1100, Craig Wilson wrote: > Sorry if this is not the correct list for this question, but I have > already posted this on freebsd-questions and have had no response. > I have looked at documentation and cannot find an answer, and I cannot > search the mailing lists etc as the server is down. > > Could someone please advise as to whether cardbus is supported under > FreeBSD 3.4-RELEASE, and if not whether it is supported in current, or > if it is to be supported under FreeBSD 3.x. I have some laptops with > cardbus slots and require a SCSI pccard. I have a choice between > an Adaptec APA-1460 (16bit PCMCIA) or APA-1480 (32bit cardbus). CardBus is not supported by any FreeBSD version. Support is in the works for 4.x but will not be available for several months. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 15:20:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id D6A8737B71C for ; Thu, 17 Feb 2000 15:20:32 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id SAA05767; Thu, 17 Feb 2000 18:20:21 -0500 (EST) (envelope-from efutch@nyct.net) Date: Thu, 17 Feb 2000 18:20:20 -0500 (EST) From: "Eric D. Futch" To: Peter Radcliffe Cc: stable@FreeBSD.ORG Subject: Re: xl0 packet dropping, still In-Reply-To: <20000217121035.A11090@pir.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Peter Radcliffe wrote: >> FWIW, a CompUSA clerk told me, those don't work well in, say, AMD >> based machines... > >IMHO, I would say that CompUSA clerk has no idea what he/she is >talking about (shocker). > I've had a CompUSA clerk ask me if FreeBSD ran on Windows 95. I was looking for an emergency copy, the CD burned died at a convient time. I laughed all the way back to the office. -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 16:59:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id F224C37B918 for ; Thu, 17 Feb 2000 16:59:53 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p35-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.100]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id JAA17117; Fri, 18 Feb 2000 09:59:47 +0900 (JST) Message-ID: <38AC994B.915857A3@newsguy.com> Date: Fri, 18 Feb 2000 09:58:51 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Craig Wilson Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Cardbus And FreeBSD References: <38AC7E01.63D5@natsoft.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Craig Wilson wrote: > > Could someone please advise as to whether cardbus is supported under > FreeBSD 3.4-RELEASE, and if not whether it is supported in current, or > if it is to be supported under FreeBSD 3.x. I have some laptops with > cardbus slots and require a SCSI pccard. I have a choice between > an Adaptec APA-1460 (16bit PCMCIA) or APA-1480 (32bit cardbus). CardBus is not support at the moment on FreeBSD at all. APA-1480 will not work. (Though I keep hoping this changes soon... :) APA-1460 is supported under FreeBSD 3.4-PAO and on -current. Standard -stable does not support, as far as I know, APA-1460 (no clue as to why, though). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 17:22:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 72D9037B8A7 for ; Thu, 17 Feb 2000 17:22:11 -0800 (PST) (envelope-from bitsurfr@enteract.com) Received: from wildrock (207-229-142-170.d.enteract.com [207.229.142.170]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id TAA50825; Thu, 17 Feb 2000 19:22:03 -0600 (CST) (envelope-from bitsurfr@enteract.com) From: "Chris Silva" To: "Daniel C. Sobral" , "Craig Wilson" Cc: Subject: RE: Cardbus And FreeBSD Date: Thu, 17 Feb 2000 19:21:44 -0600 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: <38AC994B.915857A3@newsguy.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Since when is there a 3.4-PAO? Last I saw (about a month) it was still 3.3 > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Daniel C. Sobral > Sent: Thursday, February 17, 2000 6:59 PM > To: Craig Wilson > Cc: freebsd-stable@FreeBSD.ORG > Subject: Re: Cardbus And FreeBSD > > > Craig Wilson wrote: > > > > Could someone please advise as to whether cardbus is supported under > > FreeBSD 3.4-RELEASE, and if not whether it is supported in current, or > > if it is to be supported under FreeBSD 3.x. I have some laptops with > > cardbus slots and require a SCSI pccard. I have a choice between > > an Adaptec APA-1460 (16bit PCMCIA) or APA-1480 (32bit cardbus). > > CardBus is not support at the moment on FreeBSD at all. APA-1480 will > not work. (Though I keep hoping this changes soon... :) > > APA-1460 is supported under FreeBSD 3.4-PAO and on -current. Standard > -stable does not support, as far as I know, APA-1460 (no clue as to why, > though). > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "If you consider our help impolite, you should see the manager." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.0.2 iQA/AwUBOKyep4YwDkcZSgMYEQKY+wCeJkAeJ7DMg5nML65h2+fNoEQURakAoOgB 49ENQ8LN3+RZ015OkX8olFX1 =O2FW -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 17:31:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from natsoft.com.au (natsoft.com.au [203.39.138.130]) by hub.freebsd.org (Postfix) with ESMTP id E14CB37B8A7 for ; Thu, 17 Feb 2000 17:31:26 -0800 (PST) (envelope-from craig@natsoft.com.au) Received: from Win95.natsoft.com.au (Win95 [203.39.138.131]) by natsoft.com.au (8.8.5/8.8.5) with SMTP id MAA21728; Fri, 18 Feb 2000 12:32:40 +1100 (EST) Message-ID: <38AC9FC1.676E@natsoft.com.au> Date: Fri, 18 Feb 2000 12:26:25 +1100 From: Craig Wilson Organization: National Software Pty Ltd X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: Chris Silva Cc: "Daniel C. Sobral" , freebsd-stable@FreeBSD.ORG Subject: Re: Cardbus And FreeBSD References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Silva wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Since when is there a 3.4-PAO? Last I saw (about a month) it was still > 3.3 > Looks like end Jan 2000 see: http://www.jp.FreeBSD.org/PAO/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 17:50:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 2EF1637B887 for ; Thu, 17 Feb 2000 17:50:48 -0800 (PST) (envelope-from bitsurfr@enteract.com) Received: from wildrock (207-229-142-170.d.enteract.com [207.229.142.170]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id TAA53747; Thu, 17 Feb 2000 19:50:41 -0600 (CST) (envelope-from bitsurfr@enteract.com) From: "Chris Silva" To: "Craig Wilson" Cc: "Daniel C. Sobral" , Subject: RE: Cardbus And FreeBSD Date: Thu, 17 Feb 2000 19:50:22 -0600 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: <38AC9FC1.676E@natsoft.com.au> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I see that ;) but argh, what's this, PAO3(98) patch for FreeBSD(98) 3.3R-Rev01 On the site, note the FreeBSD(98) - eesh, are they getting a bit of MS naming conventions here? > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Craig Wilson > Sent: Thursday, February 17, 2000 7:26 PM > To: Chris Silva > Cc: Daniel C. Sobral; freebsd-stable@FreeBSD.ORG > Subject: Re: Cardbus And FreeBSD > > > Chris Silva wrote: > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Since when is there a 3.4-PAO? Last I saw (about a month) it was still > > 3.3 > > > > Looks like end Jan 2000 see: > http://www.jp.FreeBSD.org/PAO/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.0.2 iQA/AwUBOKylXYYwDkcZSgMYEQJNAQCdHAIMEx1D7uLWZeH8UelvGux1nAYAniRV GWnu72Er1dUs8JPv02SkXUp6 =JG+G -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 18: 2:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 5A7D237B887 for ; Thu, 17 Feb 2000 18:02:22 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id VAA06827; Thu, 17 Feb 2000 21:02:04 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id VAA96801; Thu, 17 Feb 2000 21:02:03 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id VAA63202; Thu, 17 Feb 2000 21:02:03 -0500 (EST) Date: Thu, 17 Feb 2000 21:02:03 -0500 (EST) From: Thomas David Rivers Message-Id: <200002180202.VAA63202@lakes.dignus.com> To: bitsurfr@enteract.com, craig@natsoft.com.au Subject: RE: Cardbus And FreeBSD Cc: dcs@newsguy.com, freebsd-stable@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I see that ;) but argh, what's this, PAO3(98) patch for FreeBSD(98) > 3.3R-Rev01 > On the site, note the FreeBSD(98) - eesh, are they getting a bit of MS > naming > conventions here? Could that be for PC98? Which is a slightly different PC frequently used in Japan? - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 18: 7:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id B93F437B920 for ; Thu, 17 Feb 2000 18:07:29 -0800 (PST) (envelope-from bitsurfr@enteract.com) Received: from wildrock (207-229-142-170.d.enteract.com [207.229.142.170]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id UAA55468; Thu, 17 Feb 2000 20:07:01 -0600 (CST) (envelope-from bitsurfr@enteract.com) From: "Chris Silva" To: "Thomas David Rivers" , Cc: , Subject: RE: Cardbus And FreeBSD Date: Thu, 17 Feb 2000 20:06:42 -0600 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: <200002180202.VAA63202@lakes.dignus.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Could that be for PC98? Which is a slightly different PC frequently > used in Japan? > > - Dave Rivers - Could be - I would not, nor care to know - being I never left the US (well, 'cept fer Canada) -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.0.2 iQA/AwUBOKypMYYwDkcZSgMYEQKUvQCdFBNt3TWCUbF49BdNgHEd0vnZZLQAni0i VDlLOMEYi0HRYizWEkQO+hRB =/bLB -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 18:16:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.giga.net.tw (mail2.giga.net.tw [203.133.1.11]) by hub.freebsd.org (Postfix) with ESMTP id B2DE537B7C2 for ; Thu, 17 Feb 2000 18:16:04 -0800 (PST) (envelope-from sywang@email.gcn.net.tw) Received: from firefly ([203.133.1.201]) by mail2.giga.net.tw with Microsoft SMTPSVC(5.5.1877.117.11); Fri, 18 Feb 2000 10:14:10 +0800 From: "Starry Wang" To: Cc: Subject: RE: weird crashes Date: Fri, 18 Feb 2000 10:10:34 +0800 Message-ID: <51C38DDEF19ED211AAA10008C71E612FB04C03@gigaexchange.hgc.com.tw> MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: base64 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal In-Reply-To: <3.0.5.32.20000124112937.01eb2ce0@staff.sentex.ca> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG CURlYXIgIFNpcjoNCglXZSBnb3QgdGhlIHNhbWUgcHJvYmxlbSAodGhlIHNhbWUgbWVzc2FnZSkg Li4uIFdlIGFsc28gdGhpbmsgdGhpcyBtYXkgY2F1c2UgYnkgIEhhcmQgRGlzayBmYWlsdXJlLg0K CVNvIHdlIHJlcGxhY2UgYWxsIGJyYW5kIG5ldyBoYXJkIGRpc2tzIHRvIG91ciBzeXN0ZW0uIEJ1 dCBhZnRlciBydW5uaW5nIG9uZSBkYXksIHdlIHN0aWxsIGdldCB0aGUgc2FtZSBlcnJvciBtZXNz YWdlIGxpa2UgdGhhdC4NCglEb3NlIGFueW9uZSBoYXZlIGlkZWEgPz8NCglPdXIgc3lzdGVtIGlz ICBGcmVlQlNEIDMuMyBzdGFibGUgMTk5OTEyMDcsICBJQk0tRFRUQS0zNTEzNTAgICAgDQoJVGhh bmtzIA0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IE1pa2UgVGFuY3NhIFttYWls dG86bWlrZUBzZW50ZXgubmV0XQ0KU2VudDogVHVlc2RheSwgSmFudWFyeSAyNSwgMjAwMCAxMjoz MCBBTQ0KVG86IEplcm9lbiBCdWx0ZW47IGZyZWVic2Qtc3RhYmxlQEZyZWVCU0QuT1JHDQpTdWJq ZWN0OiBSZTogd2VpcmQgY3Jhc2hlcw0KDQpBdCAwNToyMiBQTSAxLzI0LzAwICswMTAwLCBKZXJv ZW4gQnVsdGVuIHdyb3RlOg0KPkhtbS4uLiBqdXN0IGZvdW5kIHRoaXMgaW4gL3Zhci9sb2cvbWVz c2FnZXM6DQo+DQo+SmFuIDI0IDA4OjEwOjU5IHNlYnVsYmEgL2tlcm5lbDogd2QwOiBpbnRlcnJ1 cHQgdGltZW91dCAoc3RhdHVzDQo+NTg8cmR5LHNlZWtkb25lLA0KPmRycT4gZXJyb3IgMTxub19k YW0+KQ0KPkphbiAyNCAwODoxMDo1OSBzZWJ1bGJhIC9rZXJuZWw6IHdkMDogd2R0aW1lb3V0KCkg RE1BIHN0YXR1cyA0DQo+SmFuIDI0IDEwOjExOjAzIHNlYnVsYmEgL2tlcm5lbDogc3dhcF9wYWdl cjogb3V0IG9mIHN3YXAgc3BhY2UNCg0KTXkgZmlyc3QgZ3Vlc3MgaXMgdGhhdCB5b3UgbWlnaHQg aGF2ZSBhIGJhZCBzZWN0b3Igb24geW91ciBJREUgZHJpdmUuICBJZg0KaXRzIG9uIHlvdXIgc3dh cCBwYXJ0aXRpb24sIHRoaXMgd291bGQgYmUgYSBiYWQgdGhpbmcuDQoNCiAgICAgICAgLS0tTWlr ZQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tDQpNaWtlIFRhbmNzYSwgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgIHRlbCArMSA1MTkgNjUxIDM0MDANCk5ldHdvcmsgQWRtaW5pc3RyYXRvciwg ICAgICAgICAgICAgICAgICAgICAgICAgICAgbWlrZUBzZW50ZXgubmV0DQpTZW50ZXggQ29tbXVu aWNhdGlvbnMgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHd3dy5zZW50ZXgubmV0DQpDYW1i cmlkZ2UsIE9udGFyaW8gQ2FuYWRhDQoNCg0KVG8gVW5zdWJzY3JpYmU6IHNlbmQgbWFpbCB0byBt YWpvcmRvbW9ARnJlZUJTRC5vcmcNCndpdGggInVuc3Vic2NyaWJlIGZyZWVic2Qtc3RhYmxlIiBp biB0aGUgYm9keSBvZiB0aGUgbWVzc2FnZQ0K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 19:10:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E79ED37B64D for ; Thu, 17 Feb 2000 19:10:55 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p35-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.100]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id MAA19374; Fri, 18 Feb 2000 12:10:48 +0900 (JST) Message-ID: <38ACADD6.E8566B65@newsguy.com> Date: Fri, 18 Feb 2000 11:26:30 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Brad Knowles Cc: Tom , freebsd-stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > I've run tmpfs tests with postmark on Ultra 2 and Ultra 5 systems > with faster CPUs and newer versions of the OS, and they didn't run > anywhere *NEAR* that fast (I've got an Ultra 5 I'm testing right > now). Heck, one person told me he had an older laptop running Linux > with ReiserFS and he was getting better throughput going to disk than > Sun did with tmpfs! Err... Is it fast or is it slow? You are claiming both up there... :-) > I also notice that softupdates on a slow disk beat out > Linux/ext2fs+async on a single CPU system that was otherwise > similarly configured, except for the DPT SmartRAID V controller that > the Linux server had to it's advantage, and the 5-way RAID-5 volume > that it was writing to. DPT is known to be slow, and write performance on RAID-5 is lower than on single-disk. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 19:11: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 0EB9E37B64D for ; Thu, 17 Feb 2000 19:11:04 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p35-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.100]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id MAA19419; Fri, 18 Feb 2000 12:10:57 +0900 (JST) Message-ID: <38ACAF8B.65E314E9@newsguy.com> Date: Fri, 18 Feb 2000 11:33:47 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Tom Cc: Brad Knowles , freebsd-stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom wrote: > > Not really. You could just use async updates instead of softupdates. > Or an OS that uses async updates. Write caching metadata is always faster > than re-ordering it intelligently. Softupdates reduces the number of writes needed. It can coalesce writes to the same block. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 19:11:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 4289D37B976 for ; Thu, 17 Feb 2000 19:11:07 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p35-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.100]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id MAA19384; Fri, 18 Feb 2000 12:10:50 +0900 (JST) Message-ID: <38ACAF00.92E93FC4@newsguy.com> Date: Fri, 18 Feb 2000 11:31:28 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Brad Knowles Cc: Clifton Royston , Tom , freebsd-stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... References: <20000217103516.C19043@lava.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > Of course, he's doing RAID-0 across the board for speed on his > filesystems for news articles, and no thought given to reliability > because he's got multiple servers for that kind of redundancy. He is doing RAID-0+1, I think. BTW, RAID-0 is mirroring, which has high reliability. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 19:48:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hydrant.intranova.net (hydrant.intranova.net [209.201.95.10]) by hub.freebsd.org (Postfix) with SMTP id 3FEFA37B946 for ; Thu, 17 Feb 2000 19:48:41 -0800 (PST) (envelope-from oogali@intranova.net) Received: (qmail 98202 invoked from network); 18 Feb 2000 03:47:30 -0000 Received: from localhost (oogali@127.0.0.1) by hydrant.intranova.net with SMTP; 18 Feb 2000 03:47:30 -0000 Date: Thu, 17 Feb 2000 22:47:30 -0500 (EST) From: Omachonu Ogali To: Mikhail Teterin Cc: stable@freebsd.org Subject: Re: xl0 packet dropping, still In-Reply-To: <200002171632.LAA07138@rtfm.newton> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've gotten reports of the 3Com NIC's dropping packets in all OS's using an Intel CPU, it's more or less a sporadic problem I say... On Thu, 17 Feb 2000, Mikhail Teterin wrote: > Omachonu Ogali once stated: > > =I had problems with the xl0 devices dropping packets and timing out, so > =I reverted to using an Intel EtherExpress Pro/100 (fxp0). > > FWIW, a CompUSA clerk told me, those don't work well in, say, AMD > based machines... > > -mi > > =On Tue, 15 Feb 2000, Coleman Kane wrote: > = > => Well, I switched my xl0 ethernet carc, but I am still recieving > => messages saying that there are packets being dropped. Sometimes this > => results in the card being shut down. > -- +-------------------------------------------------------------------------+ | Omachonu Ogali oogali@intranova.net | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 20:34: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id BE83637B7E7 for ; Thu, 17 Feb 2000 20:34:03 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id WAA29348; Thu, 17 Feb 2000 22:33:13 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-87.max1.wa.cyberlynk.net(207.227.118.87) by peak.mountin.net via smap (V1.3) id sma029346; Thu Feb 17 22:32:46 2000 Message-Id: <3.0.3.32.20000217223232.0099c370@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 17 Feb 2000 22:32:32 -0600 To: Omachonu Ogali From: "Jeffrey J. Mountin" Subject: Re: xl0 packet dropping, still Cc: stable@FreeBSD.ORG In-Reply-To: References: <200002171632.LAA07138@rtfm.newton> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:47 PM 2/17/00 -0500, Omachonu Ogali wrote: >I've gotten reports of the 3Com NIC's dropping packets in all OS's using >an Intel CPU, it's more or less a sporadic problem I say... The 3Com's have higher collision rates (tested over long periods) and don't autsense most of the time, which the Intel does much better. Frankly I can't see anyone using a 3Com considering all the problems that crop up on the lists, but then I've been happy with Intel NIC since the Pro100B came out. ;) Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 20:45:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 76DCB37B7E7 for ; Thu, 17 Feb 2000 20:45:16 -0800 (PST) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id XAA03739; Thu, 17 Feb 2000 23:45:07 -0500 Date: Thu, 17 Feb 2000 23:45:07 -0500 (EST) From: Mike Nowlin To: Dan the Man Cc: freebsd-stable@FreeBSD.ORG Subject: Re: gettytab question In-Reply-To: <38AC5C40.C82D0133@microtech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Maybe someone out there can shed some light on this for me. My 3.4 > system (right off of the CD) seems to be ignoring the 'if' and 'lm' > fields in /etc/gettytab. Everything I have read indicates that what I > am doing should work, and the 'im' field works fine. There don't appear > to be any later entries in the file that override what I have specified > in the default. Here's what I've got, anybody have any ideas? > > default:\ > :cb:ce:ck:lc:fd#1000:sp#1200:if=/etc/issue:\ > :lm=Please log in\072 :im=\r\n\ > +--------------------------+\r\n\ > | Welcome to Capricorn.org |\r\n\ > +--------------------------+\r\n\r\n: I ran into this one, and finally figured it out.... Keep in mind that it's been about three months since I've looked this, so it might be a little iffy: maxtech288:\ :np:hw:ht:to#60:sp#115200:tt=vt100:\ :pp=/usr/local/bin/pppin:\ :lm=Username\72\40:\ :im=:\ :if=/usr/local/etc/dialupmsg: Note the use of "\40" in the lm field instead of a " " character, and the \72 for a colon... (Octal values). Not sure if you can use "\r" and "\n" -- you may need to convert those into octal as well... Probably putting in: :lm=Please\40log\40in\072\40: ... will work. I also vaguely remember that if the "lm" field was screwed up, the "if" field was ignored. mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 20:47:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 974C937B962 for ; Thu, 17 Feb 2000 20:47:38 -0800 (PST) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id XAA03761; Thu, 17 Feb 2000 23:46:44 -0500 Date: Thu, 17 Feb 2000 23:46:44 -0500 (EST) From: Mike Nowlin To: "Eric D. Futch" Cc: Peter Radcliffe , stable@FreeBSD.ORG Subject: Re: xl0 packet dropping, still In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've had a CompUSA clerk ask me if FreeBSD ran on Windows 95. I was > looking for an emergency copy, the CD burned died at a convient time. I > laughed all the way back to the office. Did you tell him "No, but Windows 95 will run on FreeBSD..."? :) mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 21:30:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id ACC4737B997 for ; Thu, 17 Feb 2000 21:30:32 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (mi@rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id AAA11043 for ; Fri, 18 Feb 2000 00:30:28 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id AAA04558 for stable@freebsd.org; Fri, 18 Feb 2000 00:30:28 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <200002180530.AAA04558@rtfm.newton> Subject: good network card (xl0 packet dropping) In-Reply-To: <3.0.3.32.20000217223232.0099c370@207.227.119.2> from "Jeffrey J. Mountin" at "Feb 17, 2000 10:32:32 pm" To: stable@freebsd.org Date: Fri, 18 Feb 2000 00:30:28 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Thu, 17 Feb 2000 21:38:44 -0800 (PST) (envelope-from saxonww@ufl.edu) Received: from n44-230.dhnet.ufl.edu (gremlin@[128.227.44.230]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id AAA58550; Fri, 18 Feb 2000 00:38:40 -0500 Date: Fri, 18 Feb 2000 00:38:39 -0500 (EST) From: Will Saxon X-Sender: gremlin@localhost To: Mikhail Teterin Cc: stable@FreeBSD.ORG Subject: Re: good network card (xl0 packet dropping) In-Reply-To: <200002180530.AAA04558@rtfm.newton> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Really, if you want a great netowrk card, there are only a couple of options. I prefer Intel por/100 cards, I have 3 82557 based ones (pro/100B) that work great; the newest 82559 based cards (pro/100+ management) go for like $40 and are very very good. I think 3Com has some new cards that may raise the bar again, but given your problems with them you may want to try something else. FWIW I have two linksys LNE-100TX cards that "work." Havent epxerienced drops or anything bad but then again, they arent under heavy use either. Really if you can afford it you should look at the Intel ones. -Will On Fri, 18 Feb 2000, Mikhail Teterin wrote: > Jeffrey J. Mountin once stated: > > =Frankly I can't see anyone using a 3Com considering all the problems > =that crop up on the lists, but then I've been happy with Intel NIC > =since the Pro100B came out. ;) > > Ok, so what about those cards that are based on the Digital's > chipset(s)? > > -mi > > > 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-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 21:46:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from h006097780c24.ne.mediaone.net (h006097780c24.ne.mediaone.net [24.218.250.124]) by hub.freebsd.org (Postfix) with ESMTP id E6CF937BB5C for ; Thu, 17 Feb 2000 21:46:45 -0800 (PST) (envelope-from andy@lewman.com) Received: from lewman.com (localhost [127.0.0.1]) by h006097780c24.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id AAA00503 for ; Fri, 18 Feb 2000 00:46:43 -0500 (EST) (envelope-from andy@lewman.com) Message-ID: <38ACDCC3.43FD94F@lewman.com> Date: Fri, 18 Feb 2000 00:46:43 -0500 From: Andy Organization: Lewman Industries X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: good network card (xl0 packet dropping) References: <200002180530.AAA04558@rtfm.newton> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msFA10F24E2DB8C22D8319BAAF" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------msFA10F24E2DB8C22D8319BAAF Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mikhail Teterin wrote: > > Ok, so what about those cards that are based on the Digital's > chipset(s)? I've had great success with the NetGear PCI cards. They are fairly cheap, and have worked for me in fbsd for quite a while. They work as pn0 cards. Just my $.02. -- | Andy | e-mail | web | | | andy@lewman.com | www.lewman.com | "If you don't want your dog to have bad breath, do what I do: Pour a little Lavoris in the toilet." -- Jay Leno --------------msFA10F24E2DB8C22D8319BAAF Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIJkAYJKoZIhvcNAQcCoIIJgTCCCX0CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B10wggQnMIIDkKADAgECAhAXN8ogLRsvAwDJMiA8WgnMMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTk5MDUxMDAwMDAw MFoXDTAwMDUwOTIzNTk1OVowggEPMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxFjAUBgNVBAMUDUFuZHJldyBMZXdtYW4xHjAcBgkqhkiG 9w0BCQEWD2FuZHlAbGV3bWFuLmNvbTBcMA0GCSqGSIb3DQEBAQUAA0sAMEgCQQC/EaQmMjUQ gdB4D3aH5as3M8CQY0I1RmgYevC7MoGkHezh80n+0XeGNEYE6LpMtwnAmv4NYPbwktR2EAz1 RaTPAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUB BwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsG AQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3Jw LiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEE BAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3Mx LmNybDANBgkqhkiG9w0BAQQFAAOBgQBLxOO6fPb6g7wDdf3nyY05xisVS88KGnl3MXhU4Y7N /rdCNVgoDy4Yj7qrdieJUMLAKZq91PkshncU4Ezzj94H8jmsbwSLOod9biAJ3s58fL6MREdD vH0Xp0cw9k3JMpi4ipM5DkYfbeiCCczfvgYyY7Jly4cl/Iw08l4yQK239TCCAy4wggKXoAMC AQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFy eSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5 NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJ bmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3Mg MSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0G CSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqd ufBou5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIztW5U iE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQABo3wwejAR BglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUF BwIBFh93d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAw CwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bx ndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPHvhnXU0zD vcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWikK5uMYIB +zCCAfcCAQEwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0 ZWQCEBc3yiAtGy8DAMkyIDxaCcwwCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZI hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMDAyMTgwNTQ2NDNaMCMGCSqGSIb3DQEJBDEWBBRT M3uWYRTKa2sLuZqZLTxrC4rKpDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG SIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDANBgkq hkiG9w0BAQEFAARAJ7K89TXyM58xJmFsmiG13KvnD2X5eZFUAEpSE2vwY+PCoMCK8Ysh1AJt wAgVOnJMiNkrMkN9TAOVgdQAy6o2hg== --------------msFA10F24E2DB8C22D8319BAAF-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 21:50:29 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id BCC6237B9DE for ; Thu, 17 Feb 2000 21:50:24 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id WAA21327; Thu, 17 Feb 2000 22:47:23 -0700 (MST) Date: Thu, 17 Feb 2000 22:47:22 -0700 (MST) From: "Forrest W. Christian" To: Will Saxon Cc: Mikhail Teterin , stable@FreeBSD.ORG Subject: Re: good network card (xl0 packet dropping) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Will Saxon wrote: > Really, if you want a great netowrk card, there are only a couple of > options. I prefer Intel por/100 cards, I have 3 82557 based ones > (pro/100B) that work great; the newest 82559 based cards (pro/100+ > management) go for like $40 and are very very good. I would definately second this one. Very very good cards and are very very reliable. Run them exclusively in my client's high end boxes. One possible caveat: I had problems doing an across-the-wire installation of FreeBSD with the lastest Pro/100 card which has the management and the boot rom stuff in it. Ended up installing using a "generic" realtec pci adapter and then putting the Pro/100 in there. I can't say for sure what the problem was, but the card is running like a champ now (perhaps something weird with the install kernel?) > I think 3Com has some new cards that may raise the bar again, but given > your problems with them you may want to try something else. I will NEVER EVER use another 3com card unless I absolutely have to to make a customer happy. I hate 3com almost as much as I hate USWest, primarily because 3com's products have caused me enough grief over the years to make me not want to experience any more. I have a friend who worked at one of 3com's manufacturing plants. They were threatening to remove the test phase of the manufacturing process if they could not get their yields up to a certain point. Or, in other words, "If you can't make enough of them test good, we'll ship them all and let the customer do the test". > FWIW I have two linksys LNE-100TX cards that "work." Havent epxerienced > drops or anything bad but then again, they arent under heavy use > either. I am a BIG fan of the "generic" cards. I build picobsd based nat/firewall boxes which run in a 486. I use Davicom and/or realtec based 10mb/s cards exclusively. For PCI cards, I use cards with the realtec chipset on them. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 22: 3:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108]) by hub.freebsd.org (Postfix) with ESMTP id 93DBB37B9D0 for ; Thu, 17 Feb 2000 22:03:18 -0800 (PST) (envelope-from saxonww@ufl.edu) Received: from n44-230.dhnet.ufl.edu (gremlin@[128.227.44.230]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id BAA168726; Fri, 18 Feb 2000 01:03:13 -0500 Date: Fri, 18 Feb 2000 01:03:12 -0500 (EST) From: Will Saxon X-Sender: gremlin@localhost To: "Forrest W. Christian" Cc: Mikhail Teterin , stable@FreeBSD.ORG Subject: Re: good network card (xl0 packet dropping) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Forrest W. Christian wrote: > On Fri, 18 Feb 2000, Will Saxon wrote: > > > Really, if you want a great netowrk card, there are only a couple of > > options. I prefer Intel por/100 cards, I have 3 82557 based ones > > (pro/100B) that work great; the newest 82559 based cards (pro/100+ > > management) go for like $40 and are very very good. > > I would definately second this one. Very very good cards and are very > very reliable. Run them exclusively in my client's high end boxes. > > One possible caveat: I had problems doing an across-the-wire installation > of FreeBSD with the lastest Pro/100 card which has the management and the > boot rom stuff in it. Ended up installing using a "generic" realtec pci > adapter and then putting the Pro/100 in there. I can't say for sure what > the problem was, but the card is running like a champ now (perhaps > something weird with the install kernel?) > What was the problem? I had a problem once doing the same thing with mine, but it was user error - the other side was 100mbit full duplex and I had forgotten to enable full-duplex. REALLY slow :P. > > > FWIW I have two linksys LNE-100TX cards that "work." Havent epxerienced > > drops or anything bad but then again, they arent under heavy use > > either. > > I am a BIG fan of the "generic" cards. I build picobsd based > nat/firewall boxes which run in a 486. I use Davicom and/or realtec based > 10mb/s cards exclusively. For PCI cards, I use cards with the realtec > chipset on them. I have heard nice things about the realtek chipset for low end cards. The linksys ones I have at home are based on the Lite-On PNIC II chip, which is a tulip clone. Not very impressive credentials, but like I said they havent exploded or rendered the rest of the system unusable so they can't be -that- bad :). Uses mx driver (or whatever the new blanket tulip clone driver is). -Will To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 22: 9:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.uunet.ca (mail1.uunet.ca [209.167.141.3]) by hub.freebsd.org (Postfix) with ESMTP id 1FF0B37B7B5 for ; Thu, 17 Feb 2000 22:09:13 -0800 (PST) (envelope-from matt@ARPA.MAIL.NET) Received: from epsilon.lucida.qc.ca ([216.95.146.6]) by mail1.uunet.ca with ESMTP id <214941-6229>; Fri, 18 Feb 2000 01:09:11 -0500 Date: Fri, 18 Feb 2000 01:09:10 -0500 From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: "Jeffrey J. Mountin" Cc: FreeBSD-STABLE Subject: Re: xl0 packet dropping, still In-Reply-To: <3.0.3.32.20000217223232.0099c370@207.227.119.2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm using 3c905b-TX NICs in 4 servers here, all intels ranging from a beat up p133 doing DNS, to a pII and a couple celerons doing various tasks. These are interconnected via a Cisco 1548M, etc. I personally, have had nothing but good expierence with these cards, I find it strange that this many people are. Personally, I've always held 3com cards in high regard. For example, my friend's company which runs a wide array of intel servers, netfinities and whatnot, use strictly those 3com cards, I haven't heard of them having any problems either. I /have/ however, seen an Intel Etherexpress Pro 10/100 give a machine that I work with (FreeBSD) numerous problems upon problems for a while, it's interesting how both sides of the fence have the opposite problems. Matt -- Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] On Thu, 17 Feb 2000, Jeffrey J. Mountin wrote: : Date: Thu, 17 Feb 2000 23:32:32 -0500 : From: Jeffrey J. Mountin : To: Omachonu Ogali : Cc: stable@FreeBSD.ORG : Subject: Re: xl0 packet dropping, still : : At 10:47 PM 2/17/00 -0500, Omachonu Ogali wrote: : >I've gotten reports of the 3Com NIC's dropping packets in all OS's using : >an Intel CPU, it's more or less a sporadic problem I say... : : The 3Com's have higher collision rates (tested over long periods) and don't : autsense most of the time, which the Intel does much better. : : Frankly I can't see anyone using a 3Com considering all the problems that : crop up on the lists, but then I've been happy with Intel NIC since the : Pro100B came out. ;) : : : Jeff Mountin - jeff@mountin.net : Systems/Network Administrator : FreeBSD - the power to serve : : : : 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-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 22:16:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108]) by hub.freebsd.org (Postfix) with ESMTP id ABFBF37B893 for ; Thu, 17 Feb 2000 22:16:44 -0800 (PST) (envelope-from saxonww@ufl.edu) Received: from n44-230.dhnet.ufl.edu (gremlin@[128.227.44.230]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id BAA168812; Fri, 18 Feb 2000 01:16:37 -0500 Date: Fri, 18 Feb 2000 01:16:37 -0500 (EST) From: Will Saxon X-Sender: gremlin@localhost To: Matt Heckaman Cc: "Jeffrey J. Mountin" , FreeBSD-STABLE Subject: Re: xl0 packet dropping, still In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The main beef that I have heard with 3Com cards is that under moderate to heavy load they just begin eating CPU power. That's just what I have heard - I have no idea if they actually do. Reason I got intel cards is because I got them for $23 apiece. It was only later that I found out they were really good too. -Will On Fri, 18 Feb 2000, Matt Heckaman wrote: > Hi, > > I'm using 3c905b-TX NICs in 4 servers here, all intels ranging from a beat > up p133 doing DNS, to a pII and a couple celerons doing various tasks. > These are interconnected via a Cisco 1548M, etc. I personally, have had > nothing but good expierence with these cards, I find it strange that this > many people are. > > Personally, I've always held 3com cards in high regard. For example, my > friend's company which runs a wide array of intel servers, netfinities > and whatnot, use strictly those 3com cards, I haven't heard of them having > any problems either. > > I /have/ however, seen an Intel Etherexpress Pro 10/100 give a machine > that I work with (FreeBSD) numerous problems upon problems for a while, > it's interesting how both sides of the fence have the opposite problems. > > Matt > -- > Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] > !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] > > On Thu, 17 Feb 2000, Jeffrey J. Mountin wrote: > > : Date: Thu, 17 Feb 2000 23:32:32 -0500 > : From: Jeffrey J. Mountin > : To: Omachonu Ogali > : Cc: stable@FreeBSD.ORG > : Subject: Re: xl0 packet dropping, still > : > : At 10:47 PM 2/17/00 -0500, Omachonu Ogali wrote: > : >I've gotten reports of the 3Com NIC's dropping packets in all OS's using > : >an Intel CPU, it's more or less a sporadic problem I say... > : > : The 3Com's have higher collision rates (tested over long periods) and don't > : autsense most of the time, which the Intel does much better. > : > : Frankly I can't see anyone using a 3Com considering all the problems that > : crop up on the lists, but then I've been happy with Intel NIC since the > : Pro100B came out. ;) > : > : > : Jeff Mountin - jeff@mountin.net > : Systems/Network Administrator > : FreeBSD - the power to serve > : > : > : > : 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-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 22:40: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id CF34637B7F0 for ; Thu, 17 Feb 2000 22:39:59 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id XAA21688; Thu, 17 Feb 2000 23:37:22 -0700 (MST) Date: Thu, 17 Feb 2000 23:37:22 -0700 (MST) From: "Forrest W. Christian" To: Will Saxon Cc: Mikhail Teterin , stable@FreeBSD.ORG Subject: Re: good network card (xl0 packet dropping) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Will Saxon wrote: > > One possible caveat: I had problems doing an across-the-wire installation > > of FreeBSD with the lastest Pro/100 card which has the management and the > > boot rom stuff in it. Ended up installing using a "generic" realtec pci > > adapter and then putting the Pro/100 in there. I can't say for sure what > > the problem was, but the card is running like a champ now (perhaps > > something weird with the install kernel?) > > > > What was the problem? I had a problem once doing the same thing with mine, > but it was user error - the other side was 100mbit full duplex and I had > forgotten to enable full-duplex. REALLY slow :P. It had all the symptoms of a mangled IRQ- could ifconfig it, it would show up and have the right data rate, etc., but could not ping the box, and the install process would hang when it tried to resolve the name of the ftp server. I suspect something in the box (SE440BX-2 M/B, AHA1742U2W, Trident AGP video + this card) was conflicting with it. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 23: 8:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tesla-e0.salk.edu (tesla-e0.salk.edu [198.202.70.1]) by hub.freebsd.org (Postfix) with ESMTP id E156237B7FC for ; Thu, 17 Feb 2000 23:08:43 -0800 (PST) (envelope-from jorge@salk.edu) Received: from purkinje.salk.edu (purkinje.salk.edu [198.202.70.25]) by tesla-e0.salk.edu (8.7.5/8.7.3) with ESMTP id XAA01027; Thu, 17 Feb 2000 23:08:26 -0800 (PST) Date: Thu, 17 Feb 2000 23:08:21 -0800 (PST) From: Jorge Aldana To: "Forrest W. Christian" Cc: Will Saxon , Mikhail Teterin , stable@FreeBSD.ORG Subject: Re: good network card (xl0 packet dropping) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Before you go out and buy any card make sure the network you're plugging it into is going to work with it. Huh, you say. Well we had all Intel Pro/100's working just fine (although we had to muck with ifconfig as follows for 100BT ifconfig_fxp0="inet xx.xx.xx.xx netmask 255.255.255.0 media 100baseTX), then we bought a new switch and the Intel cards went bonkers and caused several problems. Needless to say when we switch to 3Com all was fine, now we burn those Intel's. Not that Intel makes a bad card or 3Com is better, they just happen to work so 3Com it is. So don't just look at the card, the network you're plugging it in to matters as well, switch, hub, bla bla bla... Jorge On Thu, 17 Feb 2000, Forrest W. Christian wrote: > On Fri, 18 Feb 2000, Will Saxon wrote: > > > > One possible caveat: I had problems doing an across-the-wire installation > > > of FreeBSD with the lastest Pro/100 card which has the management and the > > > boot rom stuff in it. Ended up installing using a "generic" realtec pci > > > adapter and then putting the Pro/100 in there. I can't say for sure what > > > the problem was, but the card is running like a champ now (perhaps > > > something weird with the install kernel?) > > > > > > > What was the problem? I had a problem once doing the same thing with mine, > > but it was user error - the other side was 100mbit full duplex and I had > > forgotten to enable full-duplex. REALLY slow :P. > > It had all the symptoms of a mangled IRQ- could ifconfig it, it would show > up and have the right data rate, etc., but could not ping the box, and the > install process would hang when it tried to resolve the name of the ftp > server. > > I suspect something in the box (SE440BX-2 M/B, AHA1742U2W, Trident AGP > video + this card) was conflicting with it. > > - Forrest W. Christian (forrestc@imach.com) KD7EHZ > ---------------------------------------------------------------------- > iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com > Solutions for your high-tech problems. (406)-442-6648 > ---------------------------------------------------------------------- > > > > 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-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 23:22:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 3DFF037B803 for ; Thu, 17 Feb 2000 23:22:09 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id CAA13258; Fri, 18 Feb 2000 02:21:49 -0500 (EST) (envelope-from efutch@nyct.net) Date: Fri, 18 Feb 2000 02:21:49 -0500 (EST) From: "Eric D. Futch" To: Mike Nowlin Cc: Peter Radcliffe , stable@FreeBSD.ORG Subject: Re: xl0 packet dropping, still In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Mike Nowlin wrote: > >> I've had a CompUSA clerk ask me if FreeBSD ran on Windows 95. I was >> looking for an emergency copy, the CD burned died at a convient time. I >> laughed all the way back to the office. > >Did you tell him "No, but Windows 95 will run on FreeBSD..."? :) > >mike > > I missed to mention that to him. I'm sure it would have him scratching his head. I decided to dismiss CompUSA totally after this incident. Of course it was fun asking them questions they wouldn't know where to start with, like what's the difference between ATA and EIDE hehe. Maybe I should go back to harass them some more. -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Feb 17 23:35:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 6AD2837B803 for ; Thu, 17 Feb 2000 23:35:19 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id CAA14861; Fri, 18 Feb 2000 02:35:13 -0500 (EST) (envelope-from efutch@nyct.net) Date: Fri, 18 Feb 2000 02:35:13 -0500 (EST) From: "Eric D. Futch" To: Mikhail Teterin Cc: stable@FreeBSD.ORG Subject: Re: good network card (xl0 packet dropping) In-Reply-To: <200002180530.AAA04558@rtfm.newton> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Mikhail Teterin wrote: >Jeffrey J. Mountin once stated: > >=Frankly I can't see anyone using a 3Com considering all the problems >=that crop up on the lists, but then I've been happy with Intel NIC >=since the Pro100B came out. ;) > >Ok, so what about those cards that are based on the Digital's >chipset(s)? > > -mi > > Our servers here are Kingston NIC's using Digital 21140A. We've never had any problems with them at all. We've got Cisco switches and I can't remember ever having a problem with any network cards in general. The 3Com card in my box at home died a mysterious death however, so I'm not sure if I'd want to go through that again. Now if I could just manage to cram a PCI NIC into my SGI Indy I'd be happy. The NIC on board died mysteriously also. But hey it's just a toy anyway. -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 0: 9:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8586D37B815 for ; Fri, 18 Feb 2000 00:09:54 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA79330; Fri, 18 Feb 2000 01:09:49 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA01681; Fri, 18 Feb 2000 01:09:45 -0700 (MST) Message-Id: <200002180809.BAA01681@harmony.village.org> To: Thomas David Rivers Subject: Re: Cardbus And FreeBSD Cc: bitsurfr@enteract.com, craig@natsoft.com.au, dcs@newsguy.com, freebsd-stable@FreeBSD.org In-reply-to: Your message of "Thu, 17 Feb 2000 21:02:03 EST." <200002180202.VAA63202@lakes.dignus.com> References: <200002180202.VAA63202@lakes.dignus.com> Date: Fri, 18 Feb 2000 01:09:45 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200002180202.VAA63202@lakes.dignus.com> Thomas David Rivers writes: : > I see that ;) but argh, what's this, PAO3(98) patch for FreeBSD(98) : > 3.3R-Rev01 : > On the site, note the FreeBSD(98) - eesh, are they getting a bit of MS : > naming : > conventions here? : : Could that be for PC98? Which is a slightly different PC frequently : used in Japan? PAO3(98) is for FreeBSD/pc98 which is a hardware architecture popular in Japan to this day. It is currently at 3.3R. PAO3 has updated to 3.4R for a little while now. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 0:19:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4789137B81B for ; Fri, 18 Feb 2000 00:19:34 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA79422; Fri, 18 Feb 2000 01:19:32 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA01768; Fri, 18 Feb 2000 01:19:29 -0700 (MST) Message-Id: <200002180819.BAA01768@harmony.village.org> Subject: Re: Cardbus And FreeBSD Cc: Thomas David Rivers , bitsurfr@enteract.com, craig@natsoft.com.au, dcs@newsguy.com, freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Fri, 18 Feb 2000 01:09:45 MST." <200002180809.BAA01681@harmony.village.org> References: <200002180809.BAA01681@harmony.village.org> <200002180202.VAA63202@lakes.dignus.com> Date: Fri, 18 Feb 2000 01:19:29 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200002180809.BAA01681@harmony.village.org> Warner Losh writes: : PAO3(98) is for FreeBSD/pc98 which is a hardware architecture popular : in Japan to this day. It is currently at 3.3R. PAO3 has updated to : 3.4R for a little while now. I hate to followup myself, but the latest offerings may be found at http://www.pc98.nec.co.jp/ From what little Japanese that I can read, it looks to be very much a going concern... The snoopy model looks particularly interesting. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 2:12:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from camelot.bitart.com (camelot.BITart.com [206.103.221.33]) by hub.freebsd.org (Postfix) with SMTP id BCE8C37B8B8 for ; Fri, 18 Feb 2000 02:12:23 -0800 (PST) (envelope-from gerti@bitart.com) Received: (qmail 5238 invoked by uid 101); 18 Feb 2000 10:12:23 -0000 Message-ID: <20000218101223.5237.qmail@camelot.bitart.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.2p1) Received: by NeXT.Mailer (1.148) From: Gerd Knops Date: Fri, 18 Feb 2000 04:12:22 -0600 To: freebsd-questions@FreeBSD.ORG, freebsd-stable@freebsd.org Subject: pam and imap Reply-To: gerti-freebsdq@BITart.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am trying to get pam authentication to work with the Cyrus imapd package on 3.4 stable (cvsup'd Sunday). /etc/pam.conf contains a boilerplate entry that should catch the request: other auth required pam_unix.so try_first_pass However it fails with syslog reporting ... authpam: no modules loaded for `imap' service I duplicated the 'other' entry in pam.conf, replacing 'other' with imap, no help. I made sure the line is read by changing 'pam_unix.so' to a bogus entry and getting the expected error messages about that. Any ideas? Thanks a lot Gerd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 2:24: 6 2000 Delivered-To: freebsd-stable@freebsd.org Received: from maillist.kabelfoon.nl (maillist.kabelfoon.nl [194.178.9.136]) by hub.freebsd.org (Postfix) with ESMTP id 74C9437B7BD for ; Fri, 18 Feb 2000 02:24:03 -0800 (PST) (envelope-from sdehaan@caiw.nl) Received: from 192.168.8.115 (unknown [192.168.8.115]) by maillist.kabelfoon.nl (Postfix) with ESMTP id 0305D3AE2 for ; Fri, 18 Feb 2000 11:24:03 +0100 (CET) Mime-Version: 1.0 X-Sender: sdehaan@192.168.1.133 Message-Id: In-Reply-To: References: X-Company: Kabelfoon B.V. Date: Fri, 18 Feb 2000 11:11:50 +0100 To: stable@FreeBSD.ORG From: Koos de Haan Subject: Re: good network card (xl0 packet dropping) Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I personally have a bad experience with the de driver in general. When using it with ZNYX 4 port cards which have 4 21140A chips it has all kinds of problems, which Vinod described in an earlier message (I attached hereby). The probem occours also on NetBSD (but the same driver code is mosly the same) I had the same problem with a no name 21140A card. The driver from ZNYX does it better, but it is only available as an object. not source code. This driver has problems with tcpdump but does not suffer from the de problems. I mailed znyx support the problems but i didn't receive a response from them. I use the 3C905 cards without problems for some time now. I switched to these cards because the ZNYX cards had problems (Yes it does cost me some slots in my machine) The 3COM cards we buy are in original package, not OEM. There may be a difference in that. The are connected to a 3COM SS3300 switch. Regards, Koos de Haan I am working on a 6 pc test bed (FreeBSD boxes) having the 4 port 100Mbps 21140A Znyx cards. I am running FreeBSD 3.1-Release. I have also tested it on FreeBSD 3.0-Stable. I am facing a few problems with the device driver de. 1. netstat -I gives lots of output errors. Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll de3 1500 10.0.8/24 10.0.8.5 434417 0 290242 289158 0 If I use the device driver provided at the ZNYX website (znyx.com) zxe then I do not see any Oerrs. 2. ifconfig de3 mediaopt full-duplex , returns an error: ifconfig:SIOCSIFMEDIA: Device not configured 3. The throughput of a TCP flow from one FreeBSD box to another (each having a ZNYX card) varies with the packet size. For instance for a packet size of 150bytes I achieve 90Mbps. For packetsize of 500bytes it is only 60-70Mbps. 4. If I run a tcp flow from one FreeBSD box to another via an intermediate FreeBSD box (all having the ZNYX344 card and de device driver) I get a throughput of 40Mbps only for 500 byte packets. All of these above problems are not visible when I use the zxe device driver. thank you for your time, - -- Kabelfoon BV Industriestraat 30, Postbus 45, 2670 AA NAALDWIJK Telefoon: 0174-615430 Fax: 0174-623860 Helpdesk: 0900-5224357 (44ct/min) Abonnementen: 0800-5223666 e-mail info@kabelfoon.nl voor informatie, kabelfoon@kabelfoon.nl voor abonnementszaken, help@kabelfoon.nl voor de helpdesk Homepage : http://www.kabelfoon.nl/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 8:15:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id 1394637B6CE for ; Fri, 18 Feb 2000 08:15:54 -0800 (PST) (envelope-from Thierry.Herbelot@alcatel.fr) Received: from aifhs10.alcatel.fr (mailhub2.alcatel.fr [155.132.188.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id RAA30887 for ; Fri, 18 Feb 2000 17:08:01 +0100 From: Thierry.Herbelot@alcatel.fr Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs10.alcatel.fr (ALCANET/SMTP2) with SMTP id RAA05300 for ; Fri, 18 Feb 2000 17:06:10 +0100 (MET) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id C1256889.0058F6D4 ; Fri, 18 Feb 2000 17:11:43 +0100 X-Lotus-FromDomain: ALCATEL To: stable@freebsd.org Message-ID: Date: Fri, 18 Feb 2000 17:11:31 +0100 Subject: Can't install 3.4-Stable in the second partition of a small IDE drive ! Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have just downloaded the latest, greatest -Stable (18-feb-00) and I can't get it to load as the second BSD version on my machine. I have a specific partitioning scheme : ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=827 heads=32 sectors/track=63 (2016 blks/cyl) parameters to be used for BIOS calculations are: cylinders=827 heads=32 sectors/track=63 (2016 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: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 100737 (49 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 49/ sector 63/ head 31 The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 100800, size 100800 (49 Meg), flag 0 beg: cyl 50/ sector 1/ head 0; end: cyl 99/ sector 63/ head 31 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 201600, size 1465632 (715 Meg), flag 0 beg: cyl 100/ sector 1/ head 0; end: cyl 826/ sector 63/ head 31 The data for partition 4 is: That is : two root partitions at the beginning of the drive, then a big slice where I have one 40Meg-swap, two 20M-/var and then two /usr partitions. I have already installed 4.0 -Current from 14/feb in this manner : pc-bsd103# mount /dev/ad0s1a on / (ufs, local, writes: sync 12 async 69, reads: sync 242 async 9) /dev/ad0s3g on /usr (ufs, local, writes: sync 6 async 143, reads: sync 726 asyn) /dev/ad0s3e on /var (ufs, local, writes: sync 89 async 158, reads: sync 28 asyn) procfs on /proc (procfs, local) Now, when I try to install 3.4's root partition in wd0s2, the install program complains : "this region canot be used for your root partition...please choose another location" I have already fallen into the "1024 cylinders" problem, but it is not applicable here (the whole disk is 827-cylinder-large - note : the ata driver in the dmesg sees the disk as a 1654/16/63 beast). So : what can be done to overcome this surprising limitation ? TfH PS : here is the -Current dmesg : Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-20000214-CURRENT #0: Fri Feb 18 12:51:31 CET 2000 herbelot@pc-bsd103.val9900.telspace.alcatel.fr:/usr/src/sys/compile/P5-ep Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 74539122 Hz CPU: Pentium/P54C (74.54-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping = 6 Features=0x1bf real memory = 33554432 (32768K bytes) config> q avail memory = 29999104 (29296K bytes) Preloaded elf kernel "kernel" at 0xc029c000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc029c09c. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 lnc0: port 0xfce0-0xfcff mem 0xfedffc00-0xfedffc1f irq 9 at device 8.0 on pci0 lnc0: PCnet-PCI II address 08:00:09:bb:26:57 lnc0: driver is using old-style compatability shims vga-pci0: mem 0xfe000000-0xfe7fffff at device 13. 0 on pci0 isab0: at device 15.0 on pci0 isa0: on isab0 ata-pci0: port 0xfcd0-0xfcdf at device 15.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 devclass_alloc_unit: lnc0 already exists, using next available unit number fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 lnc1: not probed (disabled) ep0: <3Com 3C509-Combo EtherLink III> at port 0x280-0x28f irq 5 on isa0 ep0: Ethernet address 00:60:08:78:98:cb ad0: 814MB [1654/16/63] at ata0-master using PIO3 Mounting root from ufs:/dev/ad0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 8:35:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.pedcom.com (ns1.pedcom.com [207.212.209.253]) by hub.freebsd.org (Postfix) with SMTP id A664B37BA36 for ; Fri, 18 Feb 2000 08:34:48 -0800 (PST) (envelope-from asickels@netsworkinc.com) Received: from CORPBDC1 by ns1.pedcom.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 18 Feb 2000 16:34:43 UT Received: by corpbdc1 with Internet Mail Service (5.5.2650.21) id <19S85CYG>; Fri, 18 Feb 2000 08:30:56 -0800 Message-ID: From: Alan Sickels To: "'Daniel C. Sobral'" , Brad Knowles Cc: Clifton Royston , Tom , freebsd-stable@FreeBSD.ORG Subject: RE: Initial performance testing w/ postmark & softupdates... Date: Fri, 18 Feb 2000 08:34:34 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF7A2D.879409EA" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF7A2D.879409EA Content-Type: text/plain; charset="iso-8859-1" Actually RAID 0 is disk striping with *NO* redundancy. RAID *1* is mirroring. -----Original Message----- From: Daniel C. Sobral [mailto:dcs@newsguy.com] Sent: Thursday, February 17, 2000 6:31 PM To: Brad Knowles Cc: Clifton Royston; Tom; freebsd-stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... Brad Knowles wrote: > > Of course, he's doing RAID-0 across the board for speed on his > filesystems for news articles, and no thought given to reliability > because he's got multiple servers for that kind of redundancy. He is doing RAID-0+1, I think. BTW, RAID-0 is mirroring, which has high reliability. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message ------_=_NextPart_001_01BF7A2D.879409EA Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Initial performance testing w/ postmark & = softupdates...

Actually RAID 0 is disk striping with *NO* = redundancy. RAID *1* is mirroring.

-----Original Message-----
From: Daniel C. Sobral [mailto:dcs@newsguy.com]
Sent: Thursday, February 17, 2000 6:31 PM
To: Brad Knowles
Cc: Clifton Royston; Tom; = freebsd-stable@FreeBSD.ORG
Subject: Re: Initial performance testing w/ postmark = & softupdates...


Brad Knowles wrote:
>
>         = Of course, he's doing RAID-0 across the board for speed on his
> filesystems for news articles, and no thought = given to reliability
> because he's got multiple servers for that kind = of redundancy.

He is doing RAID-0+1, I think. BTW, RAID-0 is = mirroring, which has high
reliability.

--
Daniel C. = Sobral        =         =         (8-DCS)
dcs@newsguy.com
dcs@freebsd.org

        "If = you consider our help impolite, you should see the = manager."




To Unsubscribe: send mail to = majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the = body of the message

------_=_NextPart_001_01BF7A2D.879409EA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 8:59:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hydrant.intranova.net (hydrant.intranova.net [209.201.95.10]) by hub.freebsd.org (Postfix) with SMTP id D1E7637B9AB for ; Fri, 18 Feb 2000 08:59:14 -0800 (PST) (envelope-from oogali@intranova.net) Received: (qmail 2774 invoked from network); 18 Feb 2000 16:51:21 -0000 Received: from localhost (oogali@127.0.0.1) by hydrant.intranova.net with SMTP; 18 Feb 2000 16:51:21 -0000 Date: Fri, 18 Feb 2000 11:51:21 -0500 (EST) From: Omachonu Ogali To: Matt Heckaman Cc: "Jeffrey J. Mountin" , FreeBSD-STABLE Subject: Re: xl0 packet dropping, still In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a machine here with 2 3C905B-TX's, during heavy traffic I get: xl0: command never completed! xl1: command never completed! I reverted to using my Intel EtherExpress PRO/100+'s and I'm fine here. On Fri, 18 Feb 2000, Matt Heckaman wrote: > Hi, > > I'm using 3c905b-TX NICs in 4 servers here, all intels ranging from a beat > up p133 doing DNS, to a pII and a couple celerons doing various tasks. > These are interconnected via a Cisco 1548M, etc. I personally, have had > nothing but good expierence with these cards, I find it strange that this > many people are. > > Personally, I've always held 3com cards in high regard. For example, my > friend's company which runs a wide array of intel servers, netfinities > and whatnot, use strictly those 3com cards, I haven't heard of them having > any problems either. > > I /have/ however, seen an Intel Etherexpress Pro 10/100 give a machine > that I work with (FreeBSD) numerous problems upon problems for a while, > it's interesting how both sides of the fence have the opposite problems. > > Matt > -- > Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] > !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] > > On Thu, 17 Feb 2000, Jeffrey J. Mountin wrote: > > : Date: Thu, 17 Feb 2000 23:32:32 -0500 > : From: Jeffrey J. Mountin > : To: Omachonu Ogali > : Cc: stable@FreeBSD.ORG > : Subject: Re: xl0 packet dropping, still > : > : At 10:47 PM 2/17/00 -0500, Omachonu Ogali wrote: > : >I've gotten reports of the 3Com NIC's dropping packets in all OS's using > : >an Intel CPU, it's more or less a sporadic problem I say... > : > : The 3Com's have higher collision rates (tested over long periods) and don't > : autsense most of the time, which the Intel does much better. > : > : Frankly I can't see anyone using a 3Com considering all the problems that > : crop up on the lists, but then I've been happy with Intel NIC since the > : Pro100B came out. ;) > : > : > : Jeff Mountin - jeff@mountin.net > : Systems/Network Administrator > : FreeBSD - the power to serve > : > : > : > : 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-stable" in the body of the message > -- +-------------------------------------------------------------------------+ | Omachonu Ogali oogali@intranova.net | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 10:40:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id A23F137BA64 for ; Fri, 18 Feb 2000 10:40:00 -0800 (PST) (envelope-from Thierry.Herbelot@alcatel.fr) Received: from aifhs10.alcatel.fr (mailhub2.alcatel.fr [155.132.188.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id TAA12725 for ; Fri, 18 Feb 2000 19:32:08 +0100 From: Thierry.Herbelot@alcatel.fr Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs10.alcatel.fr (ALCANET/SMTP2) with SMTP id TAA03971 for ; Fri, 18 Feb 2000 19:34:13 +0100 (MET) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id C1256889.006685F2 ; Fri, 18 Feb 2000 19:39:49 +0100 X-Lotus-FromDomain: ALCATEL To: stable@freebsd.org Message-ID: Date: Fri, 18 Feb 2000 19:39:43 +0100 Subject: Can't install 3.4-Stable in the second partition of a small IDE drive ! (followup) Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, (I was trying to install 3.4-Stable as a second version of FreeBSD on a small disk) I have installed "by hand" the bin distribution on these partitions : root : ad0s2a : The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 100800, size 100800 (49 Meg), flag 0 beg: cyl 50/ sector 1/ head 0; end: cyl 99/ sector 63/ head 31 /var ad0s3f and /usr ad0s3h, which are in : The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 201600, size 1465632 (715 Meg), flag 0 beg: cyl 100/ sector 1/ head 0; end: cyl 826/ sector 63/ head 31 This installation boots quite fine (as this was a "bare-bones" hand install, things are missing : in particular /stand) So, the error message that I saw in the installation program "this region cannot be used for your root partition...please choose another location" is plain wrong. As this is a small machine, I have not installed the full sources - I don't konw where to look for a bug in /stand/sysinstall TfH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 10:51:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id E060D37B9A1 for ; Fri, 18 Feb 2000 10:51:49 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id MAA01785; Fri, 18 Feb 2000 12:51:39 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-99.max1.wa.cyberlynk.net(207.227.118.99) by peak.mountin.net via smap (V1.3) id sma001759; Fri Feb 18 12:51:05 2000 Message-Id: <3.0.3.32.20000218125024.009efd00@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 18 Feb 2000 12:50:24 -0600 To: Jorge Aldana From: "Jeffrey J. Mountin" Subject: Re: good network card (xl0 packet dropping) Cc: stable@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:08 PM 2/17/00 -0800, Jorge Aldana wrote: >Before you go out and buy any card make sure the network you're plugging >it into is going to work with it. Huh, you say. Well we had all Intel >Pro/100's working just fine (although we had to muck with ifconfig as >follows for 100BT ifconfig_fxp0="inet xx.xx.xx.xx netmask >255.255.255.0 media 100baseTX), then we bought a new switch and the Intel >cards went bonkers and caused several problems. Needless to say when we >switch to 3Com all was fine, now we burn those Intel's. Not that Intel >makes a bad card or 3Com is better, they just happen to work so 3Com it is. So >don't just look at the card, the network you're plugging it in to matters >as well, switch, hub, bla bla bla... What switch? And why set the media? "Bonkers" is a bit vague. The Intel autosenses speed/duplex well with Intel, 3Com, and Cisco switches from my dealings with and does so with FBSD or Win 9x/NT. Can't say the same about 3Com 9xx (old and new). YMMV Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 10:58:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from malasada.lava.net (malasada.lava.net [199.222.42.2]) by hub.freebsd.org (Postfix) with ESMTP id 2B63E37B9EA for ; Fri, 18 Feb 2000 10:58:39 -0800 (PST) (envelope-from cliftonr@lava.net) Received: from localhost (1713 bytes) by malasada.lava.net via sendmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Fri, 18 Feb 2000 08:58:31 -1000 (HST) (Smail-3.2.0.106 1999-Mar-31 #3 built 1999-Dec-7) Date: Fri, 18 Feb 2000 08:58:31 -1000 From: Clifton Royston To: Mikhail Teterin Cc: stable@freebsd.org Subject: Re: good network card (xl0 packet dropping) Message-ID: <20000218085831.A6162@lava.net> References: <3.0.3.32.20000217223232.0099c370@207.227.119.2> <200002180530.AAA04558@rtfm.newton> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200002180530.AAA04558@rtfm.newton> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 18, 2000 at 12:30:28AM -0500, Mikhail Teterin wrote: > Jeffrey J. Mountin once stated: > > =Frankly I can't see anyone using a 3Com considering all the problems > =that crop up on the lists, but then I've been happy with Intel NIC > =since the Pro100B came out. ;) > > Ok, so what about those cards that are based on the Digital's > chipset(s)? The cards which are based on the DC21140 chipset, such as the DE500A series 100BaseTX cards, are "second best" to the Intels, IMHO. They're decent cards, they've got acceptable performance and reliability, but some 10/100 switches we've tried seem to be a bit touchy about working with them, especially when autosensing speed. Even with both sides locked at 100BaseTX Full-duplex, they're a bit error prone. We used to use them exclusively in all our servers, but have been slowly swapping them out with the Intel Pro/100+s as we do other upgrades. We're down to two servers left with the Dec cards in them. -- Clifton -- Clifton Royston -- LavaNet Systems Architect -- cliftonr@lava.net The named which can be named is not the Eternal named. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 11:23:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail4.uunet.ca (mail4.uunet.ca [209.167.141.34]) by hub.freebsd.org (Postfix) with ESMTP id 3280537BA0E for ; Fri, 18 Feb 2000 11:23:26 -0800 (PST) (envelope-from matt@ARPA.MAIL.NET) Received: from epsilon.lucida.qc.ca ([216.95.146.6]) by mail4.uunet.ca with ESMTP id <208126-12994>; Fri, 18 Feb 2000 14:23:11 -0500 Date: Fri, 18 Feb 2000 14:23:10 -0500 From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: "Jeffrey J. Mountin" Cc: Jorge Aldana , stable@FreeBSD.ORG Subject: Re: good network card (xl0 packet dropping) In-Reply-To: <3.0.3.32.20000218125024.009efd00@207.227.119.2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Jeffrey J. Mountin wrote: [...] : What switch? And why set the media? "Bonkers" is a bit vague. : : The Intel autosenses speed/duplex well with Intel, 3Com, and Cisco switches : from my dealings with and does so with FBSD or Win 9x/NT. Can't say the : same about 3Com 9xx (old and new). YMMV I'm using 3c905b-tx cards with a Cisco 1548M switch, they all autosense quite well at full-duplex 100Mbps, the one 3c509 in there also has no problem autosensing on that particular switch. FYI =) : Jeff Mountin - jeff@mountin.net : Systems/Network Administrator : FreeBSD - the power to serve -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 11:36:56 2000 Delivered-To: freebsd-stable@freebsd.org Received: from tesla-e0.salk.edu (tesla-e0.salk.edu [198.202.70.1]) by hub.freebsd.org (Postfix) with ESMTP id 8208537B907 for ; Fri, 18 Feb 2000 11:36:51 -0800 (PST) (envelope-from jorge@salk.edu) Received: from phelps.salk.edu (phelps.salk.edu [198.202.70.123]) by tesla-e0.salk.edu (8.7.5/8.7.3) with SMTP id LAA01959; Fri, 18 Feb 2000 11:36:41 -0800 (PST) Date: Fri, 18 Feb 2000 11:33:53 -0800 (PST) From: Jorge Aldana Reply-To: Jorge Aldana To: "Jeffrey J. Mountin" Cc: stable@FreeBSD.ORG Subject: Re: good network card (xl0 packet dropping) In-Reply-To: <3.0.3.32.20000218125024.009efd00@207.227.119.2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We upgraded to a newer Xylan Omni Switch/Router basically for more ports from an older Xylan (same model) with less ports. On the older Xylan we had to force the Media to 100baseTX otherwise the intel's would drop to 10base on reboots. With the new switch the Intel cards would have trouble with full duplex, drop to half or not be able to negotiate with the Xylan. Under the worst circumstances the Cards would emit runt packets causing the whole network to go down (a switch thing) thats why we got rid of them. Note: everything was fine with the old Xylan and Intel cards, the new Xylan (only newer technology from what we know) did work with Intels but not the way we needed them full duplex 100BT. We noticed that the 3Coms that were built into some of the machines which were using the Intel pci card did everything without a hitch so we pulled the cards and went with the built in 3Com's. Everything is fine now and like I said, I don't care who makes it just that it works. I'm sure we could of tweeked something somewhere (switch or ifconfig) to get things to work right but that would of been extra time, something I didn't have or want to use on that problem. Jorge On Fri, 18 Feb 2000, Jeffrey J. Mountin wrote: > At 11:08 PM 2/17/00 -0800, Jorge Aldana wrote: > >Before you go out and buy any card make sure the network you're plugging > >it into is going to work with it. Huh, you say. Well we had all Intel > >Pro/100's working just fine (although we had to muck with ifconfig as > >follows for 100BT ifconfig_fxp0="inet xx.xx.xx.xx netmask > >255.255.255.0 media 100baseTX), then we bought a new switch and the Intel > >cards went bonkers and caused several problems. Needless to say when we > >switch to 3Com all was fine, now we burn those Intel's. Not that Intel > >makes a bad card or 3Com is better, they just happen to work so 3Com it > is. So > >don't just look at the card, the network you're plugging it in to matters > >as well, switch, hub, bla bla bla... > > What switch? And why set the media? "Bonkers" is a bit vague. > > The Intel autosenses speed/duplex well with Intel, 3Com, and Cisco switches > from my dealings with and does so with FBSD or Win 9x/NT. Can't say the > same about 3Com 9xx (old and new). YMMV > > > > > Jeff Mountin - jeff@mountin.net > Systems/Network Administrator > FreeBSD - the power to serve > > > > 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-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 13:19: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from malasada.lava.net (malasada.lava.net [199.222.42.2]) by hub.freebsd.org (Postfix) with ESMTP id A331037BAB0 for ; Fri, 18 Feb 2000 13:18:57 -0800 (PST) (envelope-from cliftonr@lava.net) Received: from localhost (1980 bytes) by malasada.lava.net via sendmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Fri, 18 Feb 2000 11:18:50 -1000 (HST) (Smail-3.2.0.106 1999-Mar-31 #3 built 1999-Dec-7) Date: Fri, 18 Feb 2000 11:18:50 -1000 From: Clifton Royston To: "Jeffrey J. Mountin" Cc: Jorge Aldana , stable@FreeBSD.ORG Subject: Re: good network card (xl0 packet dropping) Message-ID: <20000218111850.D6162@lava.net> References: <3.0.3.32.20000218125024.009efd00@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <3.0.3.32.20000218125024.009efd00@207.227.119.2> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 18, 2000 at 12:50:24PM -0600, Jeffrey J. Mountin wrote: > At 11:08 PM 2/17/00 -0800, Jorge Aldana wrote: > >Before you go out and buy any card make sure the network you're plugging > >it into is going to work with it. Huh, you say. Well we had all Intel > >Pro/100's working just fine (although we had to muck with ifconfig as > >follows for 100BT ifconfig_fxp0="inet xx.xx.xx.xx netmask > >255.255.255.0 media 100baseTX), then we bought a new switch and the Intel > >cards went bonkers and caused several problems. Needless to say when we > >switch to 3Com all was fine, now we burn those Intel's. Not that Intel > >makes a bad card or 3Com is better, they just happen to work so 3Com it > is. So > >don't just look at the card, the network you're plugging it in to matters > >as well, switch, hub, bla bla bla... > > What switch? And why set the media? "Bonkers" is a bit vague. > > The Intel autosenses speed/duplex well with Intel, 3Com, and Cisco switches > from my dealings with and does so with FBSD or Win 9x/NT. Add HP Procurve switches to that list, which are really great value. -- Clifton -- Clifton Royston -- LavaNet Systems Architect -- cliftonr@lava.net The named which can be named is not the Eternal named. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 14:14:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from p1fed3.frb.org (p1fed3.frb.org [151.198.183.196]) by hub.freebsd.org (Postfix) with ESMTP id 333B737BAD9 for ; Fri, 18 Feb 2000 14:14:49 -0800 (PST) (envelope-from seth@freebie.dp.ny.frb.org) Received: by p1fed3.frb.org; id RAA22635; Fri, 18 Feb 2000 17:14:47 -0500 (EST) Message-Id: <200002182214.RAA22635@p1fed3.frb.org> Received: from (10.0.0.1) by p1fed3.frb.org via smap (3.2) id xma022630; Fri, 18 Feb 00 17:14:32 -0500 Received: by relay2.frb.org; Fri, 18 Feb 2000 17:14:31 -0500 (EST) Received: by relay.frb.org; Fri, 18 Feb 00 17:14:10 -0500 Received: by mail.frb.org; Fri, 18 Feb 2000 17:13:02 -0500 (EST) Date: Fri, 18 Feb 2000 17:14:09 -0500 From: Seth Subject: Re: xl0 packet dropping, still In-reply-to: <200002180349.VAA06521@p3smtp.frb.org>; from oogali@intranova.net on Thu, Feb 17, 2000 at 10:47:30PM -0500 To: Omachonu Ogali Cc: Mikhail Teterin , stable@FreeBSD.ORG MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <200002171632.LAA07138@rtfm.newton> <200002180349.VAA06521@p3smtp.frb.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just an FYI: I've got 4 3c905's in this box (one on-board, 3 in slots), all seeing fairly heavy use, and haven't ever experienced this problem. Maybe I'm just lucky. SB On Thu, Feb 17, 2000 at 10:47:30PM -0500, Omachonu Ogali wrote: > I've gotten reports of the 3Com NIC's dropping packets in all OS's using > an Intel CPU, it's more or less a sporadic problem I say... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 14:47:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shell.tsoft.com (shell.tsoft.com [198.144.192.5]) by hub.freebsd.org (Postfix) with ESMTP id BBEF637BAC5 for ; Fri, 18 Feb 2000 14:47:34 -0800 (PST) (envelope-from siewsim@prismedia.com) Received: from prismedia.com (m205-186.dsl.tsoft.com [198.144.205.186]) by shell.tsoft.com (8.8.7/8.8.7) with ESMTP id OAA04454 for ; Fri, 18 Feb 2000 14:47:34 -0800 (PST) Message-ID: <38ADCC33.30CC5874@prismedia.com> Date: Fri, 18 Feb 2000 14:48:19 -0800 From: Siew Sim Reply-To: siewsim@prismedia.com Organization: PRISMedia Systems X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-stable@FreeBSD.ORG Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG siewsim@prismedia.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 15: 8:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 87F6137BABA for ; Fri, 18 Feb 2000 15:08:34 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 12LwVc-000KH7-00; Fri, 18 Feb 2000 15:08:24 -0800 Date: Fri, 18 Feb 2000 15:08:20 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Daniel C. Sobral" Cc: Brad Knowles , freebsd-stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... In-Reply-To: <38ACAF8B.65E314E9@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Daniel C. Sobral wrote: > Tom wrote: > > > > Not really. You could just use async updates instead of softupdates. > > Or an OS that uses async updates. Write caching metadata is always faster > > than re-ordering it intelligently. > > Softupdates reduces the number of writes needed. It can coalesce writes > to the same block. Async updates are always as fast as softupdates, if not faster. You should read the softupdates docs. > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "If you consider our help impolite, you should see the manager." Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 15:11:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 6A33437BAA0 for ; Fri, 18 Feb 2000 15:11:14 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 12LwYI-000KVU-00; Fri, 18 Feb 2000 15:11:10 -0800 Date: Fri, 18 Feb 2000 15:11:06 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Daniel C. Sobral" Cc: Brad Knowles , freebsd-stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... In-Reply-To: <38ACADD6.E8566B65@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Daniel C. Sobral wrote: > > I also notice that softupdates on a slow disk beat out > > Linux/ext2fs+async on a single CPU system that was otherwise > > similarly configured, except for the DPT SmartRAID V controller that > > the Linux server had to it's advantage, and the 5-way RAID-5 volume > > that it was writing to. > > DPT is known to be slow, and write performance on RAID-5 is lower than > on single-disk. Big difference between DPT SmartRAID IV, and SmartRAID V. You are probably referring to the IV. BTW, I found the performance of SmartRAID IV on a single disk using postmark with the 1000/50000 test to be 20% faster than a single disk. SmartRAID cards in general usually handle postmark quite well. > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "If you consider our help impolite, you should see the manager." > > > > Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 15:17:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shell.tsoft.com (shell.tsoft.com [198.144.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 903C837BA85 for ; Fri, 18 Feb 2000 15:17:16 -0800 (PST) (envelope-from siewsim@prismedia.com) Received: from prismedia.com (m205-186.dsl.tsoft.com [198.144.205.186]) by shell.tsoft.com (8.8.7/8.8.7) with ESMTP id PAA09936 for ; Fri, 18 Feb 2000 15:17:16 -0800 (PST) Message-ID: <38ADD329.88116263@prismedia.com> Date: Fri, 18 Feb 2000 15:18:01 -0800 From: Siew Sim Reply-To: siewsim@prismedia.com Organization: PRISMedia Systems X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: 3.0 stable does not compile - crtbegin line 32 33 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, My system is currently running FreeBSD 2.2.6. I downloaded 3.0 stable today but I cannot get it to build. I did #make buildworld and here's what I get: /exports/upgrade/stable-3.0/src/lib/csu/i386-elf/crtbegin.c:32: section attributes are not supported for this target /exports/upgrade/stable-3.0/src/lib/csu/i386-elf/crtbegin.c:32: section attributes are not supported for this target {standard input}:Assembler messages: {standard input}:68: Error: Unknown pseudo-op: '.section' Can someone please tell me what I should do? Many thanks!! Siew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 15:20:13 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 202A637BAFA for ; Fri, 18 Feb 2000 15:20:09 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id PAA29941; Fri, 18 Feb 2000 15:48:35 -0800 (PST) Date: Fri, 18 Feb 2000 15:48:35 -0800 From: Alfred Perlstein To: Siew Sim Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3.0 stable does not compile - crtbegin line 32 33 Message-ID: <20000218154835.A21720@fw.wintelcom.net> References: <38ADD329.88116263@prismedia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38ADD329.88116263@prismedia.com>; from siewsim@prismedia.com on Fri, Feb 18, 2000 at 03:18:01PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Siew Sim [000218 15:46] wrote: > Hi, > > My system is currently running FreeBSD 2.2.6. I downloaded 3.0 > stable today but I cannot get it to build. > > I did #make buildworld > > and here's what I get: > > /exports/upgrade/stable-3.0/src/lib/csu/i386-elf/crtbegin.c:32: section > attributes are not supported for this target > /exports/upgrade/stable-3.0/src/lib/csu/i386-elf/crtbegin.c:32: section > attributes are not supported for this target > {standard input}:Assembler messages: > {standard input}:68: Error: Unknown pseudo-op: '.section' > > Can someone please tell me what I should do? Many thanks!! please upgrade to 2.2-stable (RELENG_2_2) before upgrading to 3-stable (RELENG_3). thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 15:30:21 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id 2564437BAEF for ; Fri, 18 Feb 2000 15:30:18 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id QAA29148; Fri, 18 Feb 2000 16:30:06 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id QAA22279; Fri, 18 Feb 2000 16:30:06 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id SAA01652; Fri, 18 Feb 2000 18:30:05 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14509.54781.123844.834507@hip186.ch.intel.com> Date: Fri, 18 Feb 2000 16:30:05 -0700 (MST) To: Alfred Perlstein Cc: Siew Sim , freebsd-stable@freebsd.org Subject: Re: 3.0 stable does not compile - crtbegin line 32 33 In-Reply-To: <20000218154835.A21720@fw.wintelcom.net> References: <38ADD329.88116263@prismedia.com> <20000218154835.A21720@fw.wintelcom.net> X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Friday, February 18, Alfred Perlstein wrote: ] > > please upgrade to 2.2-stable (RELENG_2_2) before upgrading to > 3-stable (RELENG_3). > > thanks, > -Alfred > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message http://home.san.rr.com/freebsd/make-upgrade.html bit outdated, but still a good guide. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 15:33:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id B5F4937BA96 for ; Fri, 18 Feb 2000 15:33:49 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id PAA15878; Fri, 18 Feb 2000 15:33:41 -0800 (PST) Date: Fri, 18 Feb 2000 15:33:41 -0800 From: Brooks Davis To: Alfred Perlstein Cc: Siew Sim , freebsd-stable@FreeBSD.ORG Subject: Re: 3.0 stable does not compile - crtbegin line 32 33 Message-ID: <20000218153341.A15024@orion.ac.hmc.edu> References: <38ADD329.88116263@prismedia.com> <20000218154835.A21720@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000218154835.A21720@fw.wintelcom.net>; from bright@wintelcom.net on Fri, Feb 18, 2000 at 03:48:35PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 18, 2000 at 03:48:35PM -0800, Alfred Perlstein wrote: > * Siew Sim [000218 15:46] wrote: > > Hi, > > > > My system is currently running FreeBSD 2.2.6. I downloaded 3.0 > > stable today but I cannot get it to build. > > > > I did #make buildworld > > > > and here's what I get: > > > > /exports/upgrade/stable-3.0/src/lib/csu/i386-elf/crtbegin.c:32: section > > attributes are not supported for this target > > /exports/upgrade/stable-3.0/src/lib/csu/i386-elf/crtbegin.c:32: section > > attributes are not supported for this target > > {standard input}:Assembler messages: > > {standard input}:68: Error: Unknown pseudo-op: '.section' > > > > Can someone please tell me what I should do? Many thanks!! > > please upgrade to 2.2-stable (RELENG_2_2) before upgrading to > 3-stable (RELENG_3). You will also need to use the upgrade make target instead of the world target to get past the aout->ELF transition. There's a webpage on this out there somewhere, but I don't remember where it is. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Feb 18 21:55:57 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mta4-rme.xtra.co.nz (mta4-rme.xtra.co.nz [203.96.92.15]) by hub.freebsd.org (Postfix) with ESMTP id AA9F137BB49 for ; Fri, 18 Feb 2000 21:55:53 -0800 (PST) (envelope-from dlh@xtra.co.nz) Received: from p400 ([210.55.152.93]) by mta4-rme.xtra.co.nz (InterMail v4.01.01.00 201-229-111) with SMTP id <20000219055512.UGUJ6796593.mta4-rme@p400> for ; Sat, 19 Feb 2000 18:55:12 +1300 Message-ID: <004401bf7a9d$b5e12ab0$0a00a8c0@p400> From: "Dr David Hingston" To: References: <3.0.3.32.20000218125024.009efd00@207.227.119.2> <20000218111850.D6162@lava.net> Subject: Re: good network card Date: Sat, 19 Feb 2000 18:53:50 +1300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear People I have stable 3.3 installed. It has a CNET 110 NIC. It keeps "losing itself" - ie gets lost somehow. If I reboot without powering off I find the card is not found. (ax0) However if I shutdown AND power off this fixes the problem for awhile. TiIl it recurs. The machine, pentium 100, 32M RAM, 2940 SCSI etc is used as an apache server and firewall. The net side is a de0 and seems to run without hitch, so the server continues to run, I just lose internet net access to/thru the box... The CNET driver readme for FreeBSD says: BEGIN PRO110(C) PCI Fast Ethernet Adapter FreeBSD UNIX Driver Installation Guide ====================================== Installation Procedures ======================= Before you start with the installation process, make sure that the FreeBSD UNIX system is properly installed. You must have installed the de "Digital Equipment DC21040/21041/21140/21140A/21142 chipset PCI 10/100M driver". 1. Plug the adapter into your PC. 2. Power on your PC and going to FreeBSD UNIX operating system. 3. Insert the driver diskette into floppy drive 'A'. 4. At the FreeBSD UNIX system prompt, change working directory to 'A' location. # mcd a:\freebsd 5. Copy files into FreeBSD UNIX system. # mcopy a:reg.h /usr/src/sys/pci/dc21040reg.h # mcopy if_devar.h /usr/src/sys/pci/if_devar.h # mcopy if_de.c /usr/src/sys/pci/if_de.c 6. When the system prompts a message if you want to overwrite the files, please type "Y". 7. To recompile the system KERNEL. # cd /usr/src/sys/compile/SERVER # make depend all install 8. Reboot your FreeBSD UNIX system. # reboot END however the CNET card was detected as the ax0 and not the de version ..... The other NIC is a 10 M version which runs as de0. Can anyone offer any advice here? Should I dump the NIC? Can it be more properly installed? Any guidance would be appreciated! With thanks David Hingston PS I have a CNET 120 also, but see it has no FereBSD drivers supplied with it. Can any one advise if this runs under FreeBSD well enough? (Perfectly!) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 0: 0:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from netcore.fi (netcore.fi [193.94.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 8A02D37BB29 for ; Sat, 19 Feb 2000 00:00:49 -0800 (PST) (envelope-from pekkas.NOSPAM@netcore.fi) Received: from oldwolf.home (gap.tky.hut.fi [130.233.25.176]) by netcore.fi (8.9.3/8.9.3) with SMTP id JAA03394 for ; Sat, 19 Feb 2000 09:57:32 +0200 From: Pekka Savola To: freebsd-stable@freebsd.org Subject: Re: 3.0 stable does not compile - crtbegin line 32 33 Date: Sat, 19 Feb 2000 09:57:41 +0200 Message-ID: X-Mailer: Forte Agent 1.6/32.525 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: >> My system is currently running FreeBSD 2.2.6. I downloaded 3.0 >> stable today but I cannot get it to build. > >please upgrade to 2.2-stable (RELENG_2_2) before upgrading to >3-stable (RELENG_3). FYI, that doesn't work :( You have to upgrade to 3.2-RELEASE first (or perhaps 3.3, I didn't try that); compiling 3.4-STABLE fails on an AOUT 2.2.8 system (bin/df). I posted a message here about it less than a week ago. Pekka Savola pekkas at netcore dot fi --- Across the nations the stories spread like spiderweb laid upon spiderweb, and men and women planned the future, believing they knew truth. They planned, and the Pattern absorbed their plans, weaving toward the future foretold. -- Robert Jordan: The Path of Daggers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 1:17: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id D71B837BBB6 for ; Sat, 19 Feb 2000 01:16:55 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id BAA52357; Sat, 19 Feb 2000 01:15:12 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002190915.BAA52357@gndrsh.dnsmgr.net> Subject: Re: good network card (xl0 packet dropping) In-Reply-To: from Will Saxon at "Feb 18, 2000 00:38:39 am" To: saxonww@ufl.edu (Will Saxon) Date: Sat, 19 Feb 2000 01:15:11 -0800 (PST) Cc: mi@kot.ne.mediaone.net (Mikhail Teterin), stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Really, if you want a great netowrk card, there are only a couple of > options. I prefer Intel por/100 cards, I have 3 82557 based ones > (pro/100B) that work great; the newest 82559 based cards (pro/100+ > management) go for like $40 and are very very good. > > I think 3Com has some new cards that may raise the bar again, but given > your problems with them you may want to try something else. > > FWIW I have two linksys LNE-100TX cards that "work." Havent epxerienced > drops or anything bad but then again, they arent under heavy use > either. > > Really if you can afford it you should look at the Intel ones. > -Will And now that Intel owns what was the Semiconductor Division of DEC, that includes the DEC dc21x4x based cards :-). In all seriousness to add roundness to the ``what works well'' either the Intel Pro/100 cards or our favorite DEC/Intel DC based card the KNE100TX (NOTE do _not_ get sold the cheaper KNE110TX, it is _not_ a Tulip based card!) We sell KNE100TX's by the boat load at $42.00 each in singles (we break down 20 or 100 packs) and of course we can negotiate price on larger quantities. And we will stand behind them with a ``if it won't work for you we either fix it or refund your money, only a few questions asked so that we might make it work for the next person :-).''. We well also gladly sell you Intel Etherexpress pro/100's, of course we have to charge the associtated higher product cost associated price. > > On Fri, 18 Feb 2000, Mikhail Teterin wrote: > > > Jeffrey J. Mountin once stated: > > > > =Frankly I can't see anyone using a 3Com considering all the problems > > =that crop up on the lists, but then I've been happy with Intel NIC > > =since the Pro100B came out. ;) > > > > Ok, so what about those cards that are based on the Digital's > > chipset(s)? > > > > -mi -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 1:43:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id D19D337BBCD for ; Sat, 19 Feb 2000 01:43:44 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id DAA08389; Sat, 19 Feb 2000 03:43:11 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-82.max1.wa.cyberlynk.net(207.227.118.82) by peak.mountin.net via smap (V1.3) id sma008387; Sat Feb 19 03:42:44 2000 Message-Id: <3.0.3.32.20000219034203.008f75a0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sat, 19 Feb 2000 03:42:03 -0600 To: Jorge Aldana From: "Jeffrey J. Mountin" Subject: Re: good network card (xl0 packet dropping) Cc: stable@FreeBSD.ORG In-Reply-To: References: <3.0.3.32.20000218125024.009efd00@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:33 AM 2/18/00 -0800, Jorge Aldana wrote: >We upgraded to a newer Xylan Omni Switch/Router basically for more ports >from an older Xylan (same model) with less ports. On the older Xylan we >had to force the Media to 100baseTX otherwise the intel's would drop to >10base on reboots. With the new switch the Intel cards would have trouble >with full duplex, drop to half or not be able to negotiate with the Xylan. >Under the worst circumstances the Cards would emit runt packets causing >the whole network to go down (a switch thing) thats why we got rid of >them. Note: everything was fine with the old Xylan and Intel cards, the >new Xylan (only newer technology from what we know) did work with Intels >but not the way we needed them full duplex 100BT. We noticed that the >3Coms that were built into some of the machines which were using the >Intel pci card did everything without a hitch so we pulled the cards and >went with the built in 3Com's. Everything is fine now and like I said, I >don't care who makes it just that it works. I'm sure we could of tweeked >something somewhere (switch or ifconfig) to get things to work right but >that would of been extra time, something I didn't have or want to use on >that problem. This smells of a switch problem more than a card problem, but like you say "if it works..." Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 1:49:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id CE66C37BBB5 for ; Sat, 19 Feb 2000 01:49:44 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id DAA08413; Sat, 19 Feb 2000 03:49:42 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-82.max1.wa.cyberlynk.net(207.227.118.82) by peak.mountin.net via smap (V1.3) id sma008411; Sat Feb 19 03:49:25 2000 Message-Id: <3.0.3.32.20000219034848.009e4b50@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sat, 19 Feb 2000 03:48:48 -0600 To: Matt Heckaman From: "Jeffrey J. Mountin" Subject: Re: good network card (xl0 packet dropping) Cc: stable@FreeBSD.ORG In-Reply-To: References: <3.0.3.32.20000218125024.009efd00@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:23 PM 2/18/00 -0500, Matt Heckaman wrote: >On Fri, 18 Feb 2000, Jeffrey J. Mountin wrote: >[...] >: What switch? And why set the media? "Bonkers" is a bit vague. >: >: The Intel autosenses speed/duplex well with Intel, 3Com, and Cisco switches >: from my dealings with and does so with FBSD or Win 9x/NT. Can't say the >: same about 3Com 9xx (old and new). YMMV > >I'm using 3c905b-tx cards with a Cisco 1548M switch, they all autosense >quite well at full-duplex 100Mbps, the one 3c509 in there also has no >problem autosensing on that particular switch. FYI =) Ah yes, but what about a mixed environment. Not sure about the newer cards, but 3Com's didn't autosense very well with 9x/NT, but then it's been a while since was responsible for either M$ version. MCSE holders have their uses. Last 3Com I dealt with personally was the 3c959, which was decent, but horrible and needed to be locked in. Gave it away along with many other 3Coms. Heard of too many problems with the 905 varients and was more than happy with Intel. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 1:54:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id B391337BBC1 for ; Sat, 19 Feb 2000 01:54:45 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id DAA08438; Sat, 19 Feb 2000 03:54:43 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-82.max1.wa.cyberlynk.net(207.227.118.82) by peak.mountin.net via smap (V1.3) id sma008430; Sat Feb 19 03:54:19 2000 Message-Id: <3.0.3.32.20000219035342.009ce460@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sat, 19 Feb 2000 03:53:42 -0600 To: Tom From: "Jeffrey J. Mountin" Subject: Re: Initial performance testing w/ postmark & softupdates... Cc: stable@FreeBSD.ORG In-Reply-To: References: <38ACAF8B.65E314E9@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:08 PM 2/18/00 -0800, Tom wrote: >On Fri, 18 Feb 2000, Daniel C. Sobral wrote: > >> Tom wrote: >> > >> > Not really. You could just use async updates instead of softupdates. >> > Or an OS that uses async updates. Write caching metadata is always faster >> > than re-ordering it intelligently. >> >> Softupdates reduces the number of writes needed. It can coalesce writes >> to the same block. > > Async updates are always as fast as softupdates, if not faster. You >should read the softupdates docs. As fast, but not safer. Can't recall the entire analogy, but Terry mentioned on -hacker a long time back something to the effect that softupdates is like having a seatbelt and an airbag rather than just a seatbelt, as well as a faster car too. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 2: 7:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 3B6E237BBD5 for ; Sat, 19 Feb 2000 02:07:40 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id CAA52625; Sat, 19 Feb 2000 02:07:31 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002191007.CAA52625@gndrsh.dnsmgr.net> Subject: Re: Initial performance testing w/ postmark & softupdates... In-Reply-To: <3.0.3.32.20000219035342.009ce460@207.227.119.2> from "Jeffrey J. Mountin" at "Feb 19, 2000 03:53:42 am" To: jeff-ml@mountin.net (Jeffrey J. Mountin) Date: Sat, 19 Feb 2000 02:07:31 -0800 (PST) Cc: tom@uniserve.com (Tom), stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 03:08 PM 2/18/00 -0800, Tom wrote: > >On Fri, 18 Feb 2000, Daniel C. Sobral wrote: > > > >> Tom wrote: > >> > > >> > Not really. You could just use async updates instead of softupdates. > >> > Or an OS that uses async updates. Write caching metadata is always > faster > >> > than re-ordering it intelligently. > >> > >> Softupdates reduces the number of writes needed. It can coalesce writes > >> to the same block. > > > > Async updates are always as fast as softupdates, if not faster. You > >should read the softupdates docs. > > As fast, but not safer. > > Can't recall the entire analogy, but Terry mentioned on -hacker a long time > back something to the effect that softupdates is like having a seatbelt and > an airbag rather than just a seatbelt, as well as a faster car too. Or my own version of this... Async is skydiving with a main, softupdates adds a reserve just in case :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 2:26: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 23CB937BBB3 for ; Sat, 19 Feb 2000 02:25:50 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id CAA16544; Sat, 19 Feb 2000 02:54:19 -0800 (PST) Date: Sat, 19 Feb 2000 02:54:19 -0800 From: Alfred Perlstein To: "Jeffrey J. Mountin" Cc: Tom , stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... Message-ID: <20000219025419.O21720@fw.wintelcom.net> References: <38ACAF8B.65E314E9@newsguy.com> <3.0.3.32.20000219035342.009ce460@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3.0.3.32.20000219035342.009ce460@207.227.119.2>; from jeff-ml@mountin.net on Sat, Feb 19, 2000 at 03:53:42AM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jeffrey J. Mountin [000219 02:24] wrote: > At 03:08 PM 2/18/00 -0800, Tom wrote: > >On Fri, 18 Feb 2000, Daniel C. Sobral wrote: > > > >> Tom wrote: > >> > > >> > Not really. You could just use async updates instead of softupdates. > >> > Or an OS that uses async updates. Write caching metadata is always > faster > >> > than re-ordering it intelligently. > >> > >> Softupdates reduces the number of writes needed. It can coalesce writes > >> to the same block. > > > > Async updates are always as fast as softupdates, if not faster. You > >should read the softupdates docs. > > As fast, but not safer. Depending on the actual situation, softdep can out perform full async because the way it intellegently recognizes things that don't happen and does a better job at delaying rapidly changing meta-data from hitting disk. > Can't recall the entire analogy, but Terry mentioned on -hacker a long time > back something to the effect that softupdates is like having a seatbelt and > an airbag rather than just a seatbelt, as well as a faster car too. The effect of softdep is basically the safeness of a normal mount however with the speed of async. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 3:21:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail5.uunet.ca (mail5.uunet.ca [142.77.1.28]) by hub.freebsd.org (Postfix) with ESMTP id 8DE2737BB7E for ; Sat, 19 Feb 2000 03:21:34 -0800 (PST) (envelope-from matt@ARPA.MAIL.NET) Received: from epsilon.lucida.qc.ca ([216.95.146.6]) by mail5.uunet.ca with ESMTP id <231704-4288>; Sat, 19 Feb 2000 06:22:39 -0500 Date: Sat, 19 Feb 2000 06:21:21 -0500 From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: "Jeffrey J. Mountin" Cc: stable@FreeBSD.ORG Subject: Re: good network card (xl0 packet dropping) In-Reply-To: <3.0.3.32.20000219034848.009e4b50@207.227.119.2> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Jeffrey J. Mountin wrote: [...] : Ah yes, but what about a mixed environment. Not sure about the newer : cards, but 3Com's didn't autosense very well with 9x/NT, but then it's been : a while since was responsible for either M$ version. MCSE holders have : their uses. There is a NT box in that mix, which hasn't had any problems yet *knocks on wood* -Matt [...] : Jeff Mountin - jeff@mountin.net : Systems/Network Administrator : FreeBSD - the power to serve : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 4:17: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id 6374E37BBEA for ; Sat, 19 Feb 2000 04:17:03 -0800 (PST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.9.3/8.9.3) with ESMTP id NAA15170 for ; Sat, 19 Feb 2000 13:17:11 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Sat, 19 Feb 2000 13:17:11 +0100 (CET) From: "O. Hartmann" To: freebsd-stable@freebsd.org Subject: FBSD 4.0 Upgrade Problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now I did all things recommended for upgrading ... on my "old 3.4" system, I catched all the new sources via cvs. Then I compiled and installed config and genassym manually ... rewrtote the kernel configuration definitions, compiled a kernel and after some problems I got a new kernel ... but not the suitable devices in /dev/ (missing /dev/drum etc.). Well, thought this is going away by make world ... but - shit! Compiler breaks due the lack of a special option. I guess it's a new egcs option but the compiler I use is still the one from the original 3.4-STABLE distribution (cvsupded last night before upgading). Can anybody help? I think it would be nice if anyone of the GURUS out of the core team post a file called UPGRADE-STEPS or similar in which they explain rudimentary how to do when upgrading from 3.4-STABLE system up to 4.0. Thanks in advance ... Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 6:56:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27]) by hub.freebsd.org (Postfix) with SMTP id 281A737BC84 for ; Sat, 19 Feb 2000 06:56:23 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 5188 invoked from network); 19 Feb 2000 14:55:55 -0000 Received: from userac41.uk.uudial.com (HELO marder-1.) (62.188.130.239) by smtp.dial.pipex.com with SMTP; 19 Feb 2000 14:55:55 -0000 Received: (from mark@localhost) by marder-1. (8.9.3/8.9.3) id OAA61989 for stable@freebsd.org; Sat, 19 Feb 2000 14:55:18 GMT (envelope-from mark) Date: Sat, 19 Feb 2000 14:55:18 +0000 From: Mark Ovens To: stable@freebsd.org Subject: Help needed with ioctl() calls Message-ID: <20000219145518.C328@marder-1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG # uname -a FreeBSD marder-1 3.4-STABLE FreeBSD 3.4-STABLE #0: Fri Feb 18 18:14:43 GMT 2000 root@marder-1:/usr/src/sys/compile/MARDER-1 i386 I'm trying to debug a problem in the xmms port whereby the volume doesn't get set correctly. It goes wrong after the ioctl() call to set the volume in /dev/mixer. From /usr/include/machine/soundcard.h: #define SOUND_MIXER_PCM 4 #define MIXER_WRITE(dev) _IOWR('M', dev, int) #define SOUND_MIXER_WRITE_PCM MIXER_WRITE(SOUND_MIXER_PCM) and the code in question is int fd, v, l, r; fd = open(devname, O_RDONLY); l = 90; r = 90; v = (r << 8) | l; /* v == 23130 */ ioctl(fd, SOUND_MIXER_WRITE_PCM, &v); /* now v == 23387, which is (91 << 8) | 91 */ Before the ioctl() call the output from mixer(8) was: Mixer pcm is currently set to 88:88 and after: Mixer pcm is currently set to 91:91 when it should be 90:90 The appears to be a bug in ioctl(), but is it? /dev/mixer is being opened read-only but we appear to be writing to it OK, albeit the wrong values. I'm getting a bit out of my depth here so a bit of help would be appreciated. Is this a bug in ioctl()? If not, any suggestions as to what I should do now to find the cause of the problem? Thanks. -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? -Poster at LinuxWorld 2000 ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 7: 0:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from bsd.amplex.net (bsd.amplex.net [209.57.124.1]) by hub.freebsd.org (Postfix) with ESMTP id B90E037BBB6 for ; Sat, 19 Feb 2000 07:00:21 -0800 (PST) (envelope-from mark@amplex.net) Received: from mark (amplex.net [209.57.124.21] (may be forged)) by bsd.amplex.net (8.9.3/8.9.3) with SMTP id KAA59161 for ; Sat, 19 Feb 2000 10:00:14 -0500 (EST) From: "Mark Radabaugh - Amplex" To: Subject: Date: Fri, 18 Feb 2000 22:02:06 -0500 Message-ID: X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe free-sd-stable subscribe cvs-all To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 7: 3:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from thomas.clark.net (thomas.clark.net [168.143.2.191]) by hub.freebsd.org (Postfix) with ESMTP id CC0BC37BCB5 for ; Sat, 19 Feb 2000 07:03:23 -0800 (PST) (envelope-from thomas@clark.net) Received: from minotaur (minotaur [192.168.99.100]) by thomas.clark.net (8.9.3/8.9.3) with SMTP id KAA73995; Sat, 19 Feb 2000 10:01:05 -0500 (EST) (envelope-from thomas@clark.net) Message-Id: <3.0.6.32.20000219100500.00966b80@mail.clark.net> X-Sender: thomas@mail.clark.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sat, 19 Feb 2000 10:05:00 -0500 To: "Rodney W. Grimes" , saxonww@ufl.edu (Will Saxon) From: Mark Thomas Subject: Re: good network card (xl0 packet dropping) Cc: mi@kot.ne.mediaone.net (Mikhail Teterin), stable@FreeBSD.ORG In-Reply-To: <200002190915.BAA52357@gndrsh.dnsmgr.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:15 AM 2/19/00 -0800, Rodney W. Grimes wrote: >And now that Intel owns what was the Semiconductor Division of DEC, >that includes the DEC dc21x4x based cards :-). In all seriousness >to add roundness to the ``what works well'' either the Intel Pro/100 >cards or our favorite DEC/Intel DC based card the KNE100TX (NOTE do >_not_ get sold the cheaper KNE110TX, it is _not_ a Tulip based card!) What about the KNE120TX? Mark --- thomas@clark.net ---> http://www.clark.net/pub/thomas PBEM Eldritch --------> http://www.pbegames.com [TM4463-ORG] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 9:42:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kaon.intercom.com (kaon.intercom.com [198.143.3.30]) by hub.freebsd.org (Postfix) with ESMTP id 7B36537BC10 for ; Sat, 19 Feb 2000 09:42:47 -0800 (PST) (envelope-from jason@intercom.com) Received: from [198.143.3.26] (helo=intercom.com) by kaon.intercom.com with esmtp (Exim 3.13 #1) id 12MDtz-000COU-00 for stable@freebsd.org; Sat, 19 Feb 2000 12:42:44 -0500 Date: Sat, 19 Feb 2000 12:42:43 -0500 (EST) From: "Jason J. Horton" X-Sender: mail@kaon.intercom.com To: stable@freebsd.org Subject: problems booting kernel from large drive Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a -STABLE system with a 27gig IBM EIDE, and when I set up the system, I only made 2 partitions, / and swapspace. The system has been working just fine, till I did a "make world" and installed a new kernel. Now when I boot, I get errors like this: >> FreeBSD/i386 BOOT Default: 0:wd(0,a)/kernel boot: Disk error 0x1 (lba=0xc21e2f) Invalid format I am assuming I am getting this because I made the drive "dangerously dedicated". Is there any way to install my new kernel in such a way that it is loadable? Also, if I want to specify an alternate kernel to boot from on startup, would I make an entry like this in /boot/loader.conf: boot /kernel.old;/kernel.different The loader(8) manpage is kinda vague. Or is there a way to make a bootable floppy that just has a kernel, and have it use the IDE drive as /? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 10:11:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3F1E737BC84 for ; Sat, 19 Feb 2000 10:11:03 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id KAA28849; Sat, 19 Feb 2000 10:37:45 -0800 (PST) Date: Sat, 19 Feb 2000 10:37:45 -0800 From: Alfred Perlstein To: "O. Hartmann" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FBSD 4.0 Upgrade Problems Message-ID: <20000219103744.P21720@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from ohartman@ipamzlx.physik.uni-mainz.de on Sat, Feb 19, 2000 at 01:17:11PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * O. Hartmann [000219 04:47] wrote: > Now I did all things recommended for upgrading ... on my "old 3.4" > system, I catched all the new sources via cvs. Then I compiled and installed > config and genassym manually ... rewrtote the kernel configuration definitions, > compiled a kernel and after some problems I got a new kernel ... but not the > suitable devices in /dev/ (missing /dev/drum etc.). Well, thought this is going > away by make world ... but - shit! Compiler breaks due the lack of a special > option. I guess it's a new egcs option but the compiler I use is still the > one from the original 3.4-STABLE distribution (cvsupded last night before > upgading). Can anybody help? I think it would be nice if anyone of the GURUS > out of the core team post a file called UPGRADE-STEPS or similar in which they > explain rudimentary how to do when upgrading from 3.4-STABLE system up to 4.0. Are there omissions in /usr/src/UPDATING that you would advise updating? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 10:29:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from allesodernix.lrt.mw.tu-muenchen.de (allesodernix.lrt.mw.tu-muenchen.de [129.187.218.1]) by hub.freebsd.org (Postfix) with SMTP id A661337BBC1 for ; Sat, 19 Feb 2000 10:29:32 -0800 (PST) (envelope-from steve@lrt.mw.tum.de) Received: (qmail 85275 invoked from network); 19 Feb 2000 18:35:27 -0000 Received: from superfix.lrt.mw.tu-muenchen.de (129.187.218.65) by allesodernix.lrt.mw.tu-muenchen.de with SMTP; 19 Feb 2000 18:35:27 -0000 Date: Sat, 19 Feb 2000 19:30:48 +0100 (MET) From: Stephan Ullmann X-Sender: steve@superfix.lrt.mw.tu-muenchen.de To: "Jason J. Horton" Cc: stable@FreeBSD.ORG Subject: Re: problems booting kernel from large drive In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi From=20my experience in Linux and NT the problem ist the following: If your boot partition is bigger than 1024 cylinders (8GB)...or better the place where your kernel is stored is beyond this limit, the bios cannot access anymore the kernel. So before the kernel problably was in this limit and after the make world it moved somewhere else and is not accessible anymore for the bios...bummer. Under Linux one normally creates a small boot partition where everything resides that is needed for booting (~about 10-20MB is enough). I don't know how this can be done with FreeBSD - any comments? Cheers, Stephan On Sat, 19 Feb 2000, Jason J. Horton wrote: > I have a -STABLE system with a 27gig IBM EIDE, and when I set up the > system, I only made 2 partitions, / and swapspace. The system has been > working just fine, till I did a "make world" and installed a new kernel. > Now when I boot, I get errors like this:=20 > >> FreeBSD/i386 BOOT=20 > Default: 0:wd(0,a)/kernel=20 > boot: > Disk error 0x1 (lba=3D0xc21e2f) --=20 Dipl.-Ing. Stephan Ullmann Tel: +49 89 289-15997 Fachgebiet Raumfahrttechnik Fax: +49 89 289-16004 Fakult=E4t f=FCr Maschinenwesen Technische Universit=E4t M=FCnchen 85748 Garching Email: steve@lrt.mw.tum.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 10:44:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27]) by hub.freebsd.org (Postfix) with SMTP id 9831737BC3C for ; Sat, 19 Feb 2000 10:44:37 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 24528 invoked from network); 19 Feb 2000 18:41:43 -0000 Received: from usercp90.uk.uudial.com (HELO marder-1.) (62.188.156.119) by smtp.dial.pipex.com with SMTP; 19 Feb 2000 18:41:43 -0000 Received: (from mark@localhost) by marder-1. (8.9.3/8.9.3) id SAA00531; Sat, 19 Feb 2000 18:41:00 GMT (envelope-from mark) Date: Sat, 19 Feb 2000 18:41:00 +0000 From: Mark Ovens To: stable@freebsd.org Cc: hackers@freebsd.org Subject: Bug in ioctl() [Was: Help needed with ioctl() calls] Message-ID: <20000219184059.A327@marder-1> References: <20000219145518.C328@marder-1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000219145518.C328@marder-1> Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Firstly, the cross-post to -hackers seems appropriate but my apologies if it isn't. I am now certain that there is a bug in ioctl() (at least for setting the mixer). This started out as an attempt to fix a bug in xmms, but making a debug version of mixer(8) showed it to be affected the same way. The following illustrates the problem, notice that the pcm is nearly always set to a value different to that which is passed on the command-line. I haven't submitted a PR for this as I'm not 100% certain how for something like this. % mixer pcm Mixer pcm is currently set to 91:91 % mixer pcm 90:90 Setting the mixer pcm to 90:90. % mixer pcm Mixer pcm is currently set to 91:91 % mixer pcm 88:88 Setting the mixer pcm to 88:88. % mixer pcm Mixer pcm is currently set to 88:88 % mixer pcm 86:86 Setting the mixer pcm to 86:86. % mixer pcm Mixer pcm is currently set to 88:88 % mixer pcm 84:84 Setting the mixer pcm to 84:84. % mixer pcm Mixer pcm is currently set to 85:85 % On Sat, Feb 19, 2000 at 02:55:18PM +0000, Mark Ovens wrote: > # uname -a > FreeBSD marder-1 3.4-STABLE FreeBSD 3.4-STABLE #0: > Fri Feb 18 18:14:43 GMT 2000 > root@marder-1:/usr/src/sys/compile/MARDER-1 i386 > > > I'm trying to debug a problem in the xmms port whereby the volume > doesn't get set correctly. > > It goes wrong after the ioctl() call to set the volume in /dev/mixer. > > >From /usr/include/machine/soundcard.h: > > #define SOUND_MIXER_PCM 4 > #define MIXER_WRITE(dev) _IOWR('M', dev, int) > #define SOUND_MIXER_WRITE_PCM MIXER_WRITE(SOUND_MIXER_PCM) > > and the code in question is > > int fd, v, l, r; > > fd = open(devname, O_RDONLY); > > l = 90; r = 90; > > v = (r << 8) | l; /* v == 23130 */ > > ioctl(fd, SOUND_MIXER_WRITE_PCM, &v); > > /* now v == 23387, which is (91 << 8) | 91 */ > > Before the ioctl() call the output from mixer(8) was: > > Mixer pcm is currently set to 88:88 > > and after: > > Mixer pcm is currently set to 91:91 > > when it should be 90:90 > > The appears to be a bug in ioctl(), but is it? > > /dev/mixer is being opened read-only but we appear to be writing to it > OK, albeit the wrong values. > > I'm getting a bit out of my depth here so a bit of help would be > appreciated. Is this a bug in ioctl()? If not, any suggestions as to > what I should do now to find the cause of the problem? > > Thanks. > > -- > Microsoft: Where do you want to go today? > Linux: Where do you want to go tomorrow? > BSD: Are you guys coming, or what? > -Poster at LinuxWorld 2000 > ________________________________________________________________ > FreeBSD - The Power To Serve http://www.freebsd.org > My Webpage http://ukug.uk.freebsd.org/~mark/ > mailto:mark@ukug.uk.freebsd.org http://www.radan.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? -Poster at LinuxWorld 2000 ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 11:17:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id F0B7B37BC5A for ; Sat, 19 Feb 2000 11:17:06 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA54817; Sat, 19 Feb 2000 11:13:28 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200002191913.LAA54817@gndrsh.dnsmgr.net> Subject: Re: good network card (xl0 packet dropping) In-Reply-To: <3.0.6.32.20000219100500.00966b80@mail.clark.net> from Mark Thomas at "Feb 19, 2000 10:05:00 am" To: thomas@clark.net (Mark Thomas) Date: Sat, 19 Feb 2000 11:13:28 -0800 (PST) Cc: saxonww@ufl.edu (Will Saxon), mi@kot.ne.mediaone.net (Mikhail Teterin), stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 01:15 AM 2/19/00 -0800, Rodney W. Grimes wrote: > >And now that Intel owns what was the Semiconductor Division of DEC, > >that includes the DEC dc21x4x based cards :-). In all seriousness > >to add roundness to the ``what works well'' either the Intel Pro/100 > >cards or our favorite DEC/Intel DC based card the KNE100TX (NOTE do > >_not_ get sold the cheaper KNE110TX, it is _not_ a Tulip based card!) > > What about the KNE120TX? Can't tell what chip is on that from the pictures on the web site :-(, I can tell enough that it is _not_ a DEC/Intel DC21x4x chip, and looks more like a Realtek or Realtek clone chip. Anyone have the chip markings off of one of these so I can look it up in a databook? -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 12:18:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7632337BC33 for ; Sat, 19 Feb 2000 12:18:52 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p10-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.11]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id FAA16032; Sun, 20 Feb 2000 05:18:44 +0900 (JST) Message-ID: <38AEFA6C.58CE6857@newsguy.com> Date: Sun, 20 Feb 2000 05:17:48 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Tom Cc: Brad Knowles , freebsd-stable@FreeBSD.ORG Subject: Re: Initial performance testing w/ postmark & softupdates... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom wrote: > > > Softupdates reduces the number of writes needed. It can coalesce writes > > to the same block. > > Async updates are always as fast as softupdates, if not faster. You > should read the softupdates docs. I read the docs and the paper. It has been empirically shown that this is not the case. 'nuff said. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 13:41:30 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 110F537BCE0 for ; Sat, 19 Feb 2000 13:41:23 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id NAA51813; Sat, 19 Feb 2000 13:41:17 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38AF0DFE.5E1FC755@gorean.org> Date: Sat, 19 Feb 2000 13:41:18 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Pekka Savola Cc: freebsd-stable@freebsd.org Subject: Re: 3.0 stable does not compile - crtbegin line 32 33 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pekka Savola wrote: > > Alfred Perlstein wrote: > >> My system is currently running FreeBSD 2.2.6. I downloaded 3.0 > >> stable today but I cannot get it to build. > > > >please upgrade to 2.2-stable (RELENG_2_2) before upgrading to > >3-stable (RELENG_3). > > FYI, that doesn't work :( > > You have to upgrade to 3.2-RELEASE first (or perhaps 3.3, I didn't try > that); compiling 3.4-STABLE fails on an AOUT 2.2.8 system (bin/df). I > posted a message here about it less than a week ago. Do you (or anyone) have more information about that? I want to update my web page on make upgrade for 3.4, but that sounds like a pretty serious pitfall. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 14: 0:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from netcore.fi (netcore.fi [193.94.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 3470B37BCBF for ; Sat, 19 Feb 2000 14:00:06 -0800 (PST) (envelope-from Pekka.Savola@netcore.fi) Received: from unf.netcore.fi (netcore.fi [193.94.160.1]) by netcore.fi (8.9.3/8.9.3) with ESMTP id AAA04369; Sun, 20 Feb 2000 00:00:02 +0200 Message-Id: <4.3.1.20000219235542.00b58c30@127.0.0.1> X-Sender: pekkas@netcore.home X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Sun, 20 Feb 2000 00:00:05 +0200 To: freebsd-stable@freebsd.org From: Pekka Savola Subject: Re: 3.0 stable does not compile - crtbegin line 32 33 Cc: Doug Barton In-Reply-To: <38AF0DFE.5E1FC755@gorean.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You have to upgrade to 3.2-RELEASE first (or perhaps 3.3, I didn't try > > that); compiling 3.4-STABLE fails on an AOUT 2.2.8 system (bin/df). I > > posted a message here about it less than a week ago. > > Do you (or anyone) have more information about that? I want to > update my >web page on make upgrade for 3.4, but that sounds like a pretty serious >pitfall. Unfortunately, I don't know why this is so. Here's the message I sent. I only mentioned 2.2.6-RELEASE there, but I tried it with 2.2.8-RELEASE and -STABLE too. So, upgrading to 3.2-RELEASE first seems necessary (and works from 2.2.6-RELEASE etc. too). I didn't notice this message on the mailing lists. I used freebsd-stable and -bugs in Cc: ; I hope the message wasn't rejected in some anti-spamming checks. ------- Hello, I was upgrading a 2.2.6-RELEASE (GENERIC kernel) to 3.4-STABLE (CVSup'ed previously today) until I got into problems (fixed the typo with games/wargames by hand first). bin/df/Makefile is: # $FreeBSD: src/bin/df/Makefile,v 1.7.2.2 2000/01/23 03:19:33 mharo Exp $ make upgrade [at least 5 hours of code crunching] ----- ===> bin/df cc -nostdinc -O -pipe -I/usr/src/bin/df/../../sbin/mount -Wall -Wformat -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/bin/df/df.c cc -nostdinc -O -pipe -I/usr/src/bin/df/../../sbin/mount -Wall -Wformat -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/bin/df/../../sbin/mount/vfslist.c cc -nostdinc -O -pipe -I/usr/src/bin/df/../../sbin/mount -Wall -Wformat -I/usr/obj/aout/usr/src/tmp/usr/include -static -o df df.o vfslist.o df.o: Undefined symbol `_ilogb' referenced from text segment *** Error code 1 ---- And halt ;<. I tried compiling bin/df by hand, and edited the makefile a bit (added -I/usr/obj/aout... -nostdinc -pipe, but then I get an other error message (note! there also seem to be /usr/lib/libm.a there, dunno why): ----- Warning: Object directory not changed from original /usr/src/bin/df cc -O -I/usr/src/bin/df/../../sbin/mount -I/usr/obj/aout/usr/src/tmp/usr/include -nostdinc -pipe -Wall -Wformat -Wall -Wformat -c df.c cc -O -I/usr/src/bin/df/../../sbin/mount -I/usr/obj/aout/usr/src/tmp/usr/include -nostdinc -pipe -Wall -Wformat -Wall -Wformat -c /usr/src/bin/df/../../sbin/mount/vfslist.c cc -O -I/usr/src/bin/df/../../sbin/mount -I/usr/obj/aout/usr/src/tmp/usr/include -nostdinc -pipe -Wall -Wformat -Wall -Wformat -static -o df df.o vfslist.o /usr/lib/libm.a df.o: Undefined symbol `___error' referenced from text segment df.o: Undefined symbol `___error' referenced from text segment df.o: Undefined symbol `___error' referenced from text segment *** Error code 1 ----- Without any Makefile tweaks: ----- Warning: Object directory not changed from original /usr/src/bin/df cc -O -I/usr/src/bin/df/../../sbin/mount -Wall -Wformat -Wall -Wformat -c df.c In file included from df.c:57: /usr/include/ufs/ufs/ufsmount.h:63: `MAXQUOTAS' undeclared here (not in a function) /usr/include/ufs/ufs/ufsmount.h:64: `MAXQUOTAS' undeclared here (not in a function) /usr/include/ufs/ufs/ufsmount.h:68: `MAXQUOTAS' undeclared here (not in a function) /usr/include/ufs/ufs/ufsmount.h:69: `MAXQUOTAS' undeclared here (not in a function) /usr/include/ufs/ufs/ufsmount.h:70: `MAXQUOTAS' undeclared here (not in a function) /usr/include/ufs/ufs/ufsmount.h:71: field `um_export' has incomplete type df.c: In function `main': df.c:212: warning: implicit declaration of function `mkdtemp' df.c:212: warning: assignment makes pointer from integer without a cast df.c:220: warning: passing arg 1 of `mount' makes integer from pointer without a cast df.c: In function `regetmntinfo': df.c:289: structure has no member named `f_fstypename' df.c: In function `ufs_df': df.c:456: structure has no member named `f_fstypename' *** Error code 1 ----- So, it seems 'make upgrades' from some 2.2.X systems at least are broken. Compiling bin/df on my ELF system works fine. Any ideas? I hope this can be fixed soon. BTW, is there any way to continue 'make upgrade' from where this left off or do I have start from scratch? E.g. 'make -i world' always deletes the old obj directory, this probably does too? TIA, Regards Pekka --------- Pekka Savola pekkas@netcore.fi --- Across the nations the stories spread like spiderweb laid upon spiderweb, and men and women planned the future, believing they knew truth. They planned, and the Pattern absorbed their plans, weaving toward the future foretold. -- Robert Jordan: The Path of Daggers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 14:47:11 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shell.tsoft.com (shell.tsoft.com [198.144.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 0017737BD26 for ; Sat, 19 Feb 2000 14:47:08 -0800 (PST) (envelope-from siewsim@prismedia.com) Received: from prismedia.com (m205-186.dsl.tsoft.com [198.144.205.186]) by shell.tsoft.com (8.8.7/8.8.7) with ESMTP id OAA21509; Sat, 19 Feb 2000 14:46:57 -0800 (PST) Message-ID: <38AF1D91.49F24D6D@prismedia.com> Date: Sat, 19 Feb 2000 14:47:46 -0800 From: Siew Sim Reply-To: siewsim@prismedia.com Organization: PRISMedia Systems X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Doug Barton Cc: Pekka Savola , freebsd-stable@FreeBSD.ORG Subject: Re: 3.0 stable does not compile - crtbegin line 32 33 References: <38AF0DFE.5E1FC755@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Barton wrote: > Pekka Savola wrote: > > > > Alfred Perlstein wrote: > > >> My system is currently running FreeBSD 2.2.6. I downloaded 3.0 > > >> stable today but I cannot get it to build. > > > > > >please upgrade to 2.2-stable (RELENG_2_2) before upgrading to > > >3-stable (RELENG_3). > > > > FYI, that doesn't work :( > > > > You have to upgrade to 3.2-RELEASE first (or perhaps 3.3, I didn't try > > that); compiling 3.4-STABLE fails on an AOUT 2.2.8 system (bin/df). I > > posted a message here about it less than a week ago. > > Do you (or anyone) have more information about that? I want to update my > web page on make upgrade for 3.4, but that sounds like a pretty serious > pitfall. > I'm running into exactly the same problem. Can anyone tell me where I can get 3.2 src? I can't find it at the ftp site. Thanks, Siew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 14:52:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from shemp.palomine.net (shemp.palomine.net [205.198.88.200]) by hub.freebsd.org (Postfix) with SMTP id DADB037BD45 for ; Sat, 19 Feb 2000 14:52:49 -0800 (PST) (envelope-from cjohnson@palomine.net) Received: (qmail 18247 invoked by uid 1000); 19 Feb 2000 22:53:06 -0000 Date: Sat, 19 Feb 2000 17:53:06 -0500 From: Chris Johnson To: Siew Sim Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3.0 stable does not compile - crtbegin line 32 33 Message-ID: <20000219175306.A18228@palomine.net> References: <38AF0DFE.5E1FC755@gorean.org> <38AF1D91.49F24D6D@prismedia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38AF1D91.49F24D6D@prismedia.com>; from siewsim@prismedia.com on Sat, Feb 19, 2000 at 02:47:46PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 19, 2000 at 02:47:46PM -0800, Siew Sim wrote: > Doug Barton wrote: > > > Pekka Savola wrote: > > > > > > Alfred Perlstein wrote: > > > >> My system is currently running FreeBSD 2.2.6. I downloaded 3.0 > > > >> stable today but I cannot get it to build. > > > > > > > >please upgrade to 2.2-stable (RELENG_2_2) before upgrading to > > > >3-stable (RELENG_3). > > > > > > FYI, that doesn't work :( > > > > > > You have to upgrade to 3.2-RELEASE first (or perhaps 3.3, I didn't try > > > that); compiling 3.4-STABLE fails on an AOUT 2.2.8 system (bin/df). I > > > posted a message here about it less than a week ago. > > > > Do you (or anyone) have more information about that? I want to update my > > web page on make upgrade for 3.4, but that sounds like a pretty serious > > pitfall. > > > > I'm running into exactly the same problem. Can anyone tell me where I can get 3.2 > src? I can't find it at the ftp site. I had the same problem, and had the same success going to 3.2-RELEASE first. You can cvsup the source using the tag RELENG_3_2_0_RELEASE. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 15:14:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from netcore.fi (netcore.fi [193.94.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 1728A37BD08 for ; Sat, 19 Feb 2000 15:14:51 -0800 (PST) (envelope-from pekkas@netcore.fi) Received: from localhost (pekkas@localhost) by netcore.fi (8.9.3/8.9.3) with ESMTP id BAA04459; Sun, 20 Feb 2000 01:14:39 +0200 Date: Sun, 20 Feb 2000 01:14:39 +0200 (EET) From: Pekka Savola To: Siew Sim Cc: Doug Barton , freebsd-stable@FreeBSD.ORG Subject: Re: 3.0 stable does not compile - crtbegin line 32 33 In-Reply-To: <38AF1D91.49F24D6D@prismedia.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > You have to upgrade to 3.2-RELEASE first (or perhaps 3.3, I didn't try > > > that); compiling 3.4-STABLE fails on an AOUT 2.2.8 system (bin/df). I > > > posted a message here about it less than a week ago. > > > > Do you (or anyone) have more information about that? I want to update my > > web page on make upgrade for 3.4, but that sounds like a pretty serious > > pitfall. > > > > I'm running into exactly the same problem. Can anyone tell me where I can get 3.2 > src? I can't find it at the ftp site. 3.2-RELEASE was removed from ftp.*.freebsd.org less than two weeks ago. You can obtain it with CVSup though, with tag RELENG_3_2_0_RELEASE. Pekka To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 16:29:31 2000 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (port-9-153.adsl.one.net [209.50.121.153]) by hub.freebsd.org (Postfix) with ESMTP id 3628737BC1A for ; Sat, 19 Feb 2000 16:29:28 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id TAA06973; Sat, 19 Feb 2000 19:32:47 -0500 (EST) (envelope-from cokane) Date: Sat, 19 Feb 2000 19:32:47 -0500 From: Coleman Kane To: Matt Heckaman Cc: "Jeffrey J. Mountin" , FreeBSD-STABLE Subject: Re: xl0 packet dropping, still Message-ID: <20000219193247.D6824@evil.2y.net> References: <3.0.3.32.20000217223232.0099c370@207.227.119.2> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="DrWhICOqskFTAXiy" X-Mailer: Mutt 1.0.1i In-Reply-To: ; from matt@ARPA.MAIL.NET on Fri, Feb 18, 2000 at 01:09:47AM -0500 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --DrWhICOqskFTAXiy Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable I wonder if it is a problem with the 3c900 cards only. I have a roommate with the 905 who doesn't haveany problems. Another one has the cheaper homeconnect 450 that also runs fine. It seems to only be the 3c900 cards that cause problems. I have switched my server back to some AMD-Lance PCNet-SCSI card that is it's onboard controller. I never eally had a problem with it, but I was under the impression that 3Com's stuff was cream-of-the-crop, guess not. I'll probably switch to Tuilp adapters from now on... --cokane Matt Heckaman had the audacity to say: > Hi, >=20 > I'm using 3c905b-TX NICs in 4 servers here, all intels ranging from a beat > up p133 doing DNS, to a pII and a couple celerons doing various tasks. > These are interconnected via a Cisco 1548M, etc. I personally, have had > nothing but good expierence with these cards, I find it strange that this > many people are. >=20 > Personally, I've always held 3com cards in high regard. For example, my > friend's company which runs a wide array of intel servers, netfinities > and whatnot, use strictly those 3com cards, I haven't heard of them having > any problems either. >=20 > I /have/ however, seen an Intel Etherexpress Pro 10/100 give a machine > that I work with (FreeBSD) numerous problems upon problems for a while, > it's interesting how both sides of the fence have the opposite problems. >=20 > Matt > -- > Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] > !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] >=20 > On Thu, 17 Feb 2000, Jeffrey J. Mountin wrote: >=20 > : Date: Thu, 17 Feb 2000 23:32:32 -0500 > : From: Jeffrey J. Mountin > : To: Omachonu Ogali > : Cc: stable@FreeBSD.ORG > : Subject: Re: xl0 packet dropping, still > :=20 > : At 10:47 PM 2/17/00 -0500, Omachonu Ogali wrote: > : >I've gotten reports of the 3Com NIC's dropping packets in all OS's usi= ng > : >an Intel CPU, it's more or less a sporadic problem I say... > :=20 > : The 3Com's have higher collision rates (tested over long periods) and d= on't > : autsense most of the time, which the Intel does much better. > :=20 > : Frankly I can't see anyone using a 3Com considering all the problems th= at > : crop up on the lists, but then I've been happy with Intel NIC since the > : Pro100B came out. ;) > :=20 > :=20 > : Jeff Mountin - jeff@mountin.net > : Systems/Network Administrator > : FreeBSD - the power to serve > :=20 > :=20 > :=20 > : To Unsubscribe: send mail to majordomo@FreeBSD.org > : with "unsubscribe freebsd-stable" in the body of the message > :=20 >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message --DrWhICOqskFTAXiy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE4rzYtERViMObJ880RAWK5AJ92t7ihzGZST6EJpE35tcavA2DqwACg4uZR Ts4TqGxNdk/C/fs5wLhu6u4= =rQOp -----END PGP SIGNATURE----- --DrWhICOqskFTAXiy-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 17:34:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id BB03737BD94; Sat, 19 Feb 2000 17:34:11 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA56463; Sat, 19 Feb 2000 17:34:05 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38AF448E.4569B42@gorean.org> Date: Sat, 19 Feb 2000 17:34:06 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Orintz Cc: stable@freebsd.org, "freebsd-doc@FreeBSD.ORG" Subject: Re: pseudo-device log References: <001101bf6f94$e317e460$0200000a@hal3000.cx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Orintz wrote: > > Hi, > While building my first kernel for 3.4 stable i was reading > http://www.freebsd.org/handbook/kernelconfig-config.html and under section > 5.3.10. pseudo-devices > I noticed this entry about pseudo-device log > pseudo-device log > log is used for logging of kernel error messages. Mandatory. > > I had an error that stated "log" was unknown so commented it out and have so > far not noticed a problem with the new kernel. pseudo-device log is not in > GENERIC so what does the mandatory refer to Eeek. That pseudo-device was removed way back in 1997. Any docs folk want to tune that bad boy up? Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 18:16:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 1527D37BD45 for ; Sat, 19 Feb 2000 18:16:44 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p51-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.116]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id LAA18265; Sun, 20 Feb 2000 11:16:40 +0900 (JST) Message-ID: <38AF3C80.6E4F5267@newsguy.com> Date: Sun, 20 Feb 2000 09:59:44 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Jason J. Horton" Cc: stable@FreeBSD.ORG Subject: Re: problems booting kernel from large drive References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jason J. Horton" wrote: > > I have a -STABLE system with a 27gig IBM EIDE, and when I set up the > system, I only made 2 partitions, / and swapspace. The system has been It's very common the case were it's not possible (due to BIOS) to boot past 8 Gb. > working just fine, till I did a "make world" and installed a new kernel. > Now when I boot, I get errors like this: > >> FreeBSD/i386 BOOT > Default: 0:wd(0,a)/kernel Why are you booting the kernel from the second stage rather than the third? > boot: > Disk error 0x1 (lba=0xc21e2f) > Invalid format > > I am assuming I am getting this because I made the drive "dangerously > dedicated". Is there any way to install my new kernel in such a way that > it is loadable? > > Also, if I want to specify an alternate kernel to boot from on startup, > would I make an entry like this in /boot/loader.conf: > boot /kernel.old;/kernel.different > The loader(8) manpage is kinda vague. Or is there a way to make > a bootable floppy that just has a kernel, and have it use the IDE > drive as /? Read the loader.conf(5) man page instead. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Feb 19 22:18:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kaon.intercom.com (kaon.intercom.com [198.143.3.30]) by hub.freebsd.org (Postfix) with ESMTP id CC56937BE37 for ; Sat, 19 Feb 2000 22:18:46 -0800 (PST) (envelope-from jason@intercom.com) Received: from [198.143.3.26] (helo=intercom.com) by kaon.intercom.com with esmtp (Exim 3.13 #1) id 12MPhZ-000MMf-00; Sun, 20 Feb 2000 01:18:41 -0500 Date: Sun, 20 Feb 2000 01:18:41 -0500 (EST) From: "Jason J. Horton" X-Sender: mail@kaon.intercom.com To: "Daniel C. Sobral" Cc: stable@FreeBSD.ORG Subject: Re: problems booting kernel from large drive In-Reply-To: <38AF3C80.6E4F5267@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > working just fine, till I did a "make world" and installed a new kernel. > > Now when I boot, I get errors like this: > > >> FreeBSD/i386 BOOT > > Default: 0:wd(0,a)/kernel > > Why are you booting the kernel from the second stage rather than the > third? The system boot stuff is standard, not modified by us. If the kernel is being booted from the 2nd stage, thats the way sysinstall set it up. > Read the loader.conf(5) man page instead. Will do, thanks. -J To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message