From owner-freebsd-stable Mon May 22 2:57:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id 1DE2337BB79 for ; Mon, 22 May 2000 02:57:47 -0700 (PDT) (envelope-from jon@phoenix.welearn.com.au) Received: (from jon@localhost) by phoenix.welearn.com.au (8.9.3/8.9.3) id TAA94068; Mon, 22 May 2000 19:57:34 +1000 (EST) (envelope-from jon) Date: Mon, 22 May 2000 19:57:30 +1000 From: Jonathan Michaels To: Andy Sparrow Cc: freebsd-stable@FreeBSD.ORG Subject: Re: curious about memory report usingfreebsd v3.3-release Message-ID: <20000522195727.B93893@phoenix.welearn.com.au> Reply-To: jon@welearn.com.au Mail-Followup-To: Andy Sparrow , freebsd-stable@FreeBSD.ORG References: <20000515181246.A48481@phoenix.welearn.com.au> <200005151511.IAA17794@mega.geek4food.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200005151511.IAA17794@mega.geek4food.org>; from Andy Sparrow on Mon, May 15, 2000 at 08:11:46AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG andy, On Mon, May 15, 2000 at 08:11:46AM -0700, Andy Sparrow wrote: > Your message dated: Mon, 15 May 2000 18:12:49 +1000 > > >that is what i thought and so i purchased a intel eepro .. only > >to find i got one of teh "new microsoftised ones" with the ake > >on lan cable and all that other paraphenalia. thier was some > >mention of a 'problem' in teh firmware that make it hard to > >have two of these cards on teh same segment. > > This used to be true, the cards would come up with an unrecognised PHY > message and the same MAC address. i seem to remeber this bit from somewhere. > However, DG spliced in the required changes to support this card around > about 3/28, since which time it's been working perfectly for me :-) as i'm not routing the whole .au domain (grin) now that woud seriously stress the old i386dx33 .. smile. or, doing anyting 'serious' i should expect to have a similar responce. so far i've had a very forgiving relationship with freebsd on my hardware .. with the one excption being the linux emulation stuffup on some poorly written linux apps that sig11'ed while running specifically in xfree circa v2.1.5-release and or v2.1.7-release, finally it was revealed to be a programming error and not my hardware .. that was a long few weeks. thank you fro your responce. warm regards, apreciations. jonathan -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message