From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: NIC recommendations (was Re: Repeatable 2.4.0-test13-pre4...)
Date: 1 Jan 2001 15:51:14 -0800 [thread overview]
Message-ID: <92r55i$h7o$1@cesium.transmeta.com> (raw)
In-Reply-To: <3A4DBC02.92C0FD9A@uow.edu.au> <200012302301.eBUN1IF01354@pobox.com>
Followup to: <200012302301.eBUN1IF01354@pobox.com>
By author: "Barry K. Nathan" <barryn@pobox.com>
In newsgroup: linux.dev.kernel
>
> In any case, tulips have been more problematic for me than 8139, pcnet32,
> or 3c905c (whose reliability are all comparable IME). I've never tried
> eepro100, though. (Also, I'm speaking in terms of my experiences across
> all OS's which I've used the cards under, not just under Linux, although
> my Linux experiences are similar to the experiences I've had overall.)
>
I have used eepro100's on *a lot* of boxes, including *.kernel.org;
haven't had any problems whatsoever any time recently.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-02 0:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-28 22:11 Repeatable 2.4.0-test13-pre4 nfsd Oops rears it head again Mike Elmore
2000-12-28 21:59 ` David S. Miller
2000-12-29 3:21 ` Mike Elmore
2000-12-29 3:47 ` Chris Wedgwood
2000-12-29 6:15 ` Linus Torvalds
2000-12-29 10:25 ` Chris Wedgwood
2000-12-30 10:42 ` Andrew Morton
2000-12-30 18:06 ` Francois Romieu
2000-12-30 23:01 ` NIC recommendations (was Re: Repeatable 2.4.0-test13-pre4...) Barry K. Nathan
2001-01-01 23:51 ` H. Peter Anvin [this message]
2000-12-29 8:14 ` Repeatable 2.4.0-test13-pre4 nfsd Oops rears it head again David Ford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='92r55i$h7o$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.