Re: [cobalt-developers] Re: (OT) SPARCRaQ (cobalt-developers digest, Vol 1 #1392)

["E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>]

> Date: Sun, 24 Mar 2002 09:29:56 -0800
> From: Jeff Lasman <jblists@xxxxxxxxxxxxx>

(snipping throughout)


> a module?  Swapping the NIC isn't the option; it's built-on to the
> slotless motherboard <frown>.

What NIC?  I've encountered fxp, dc, de, xl, and sis on x86...
dc on Alpha, and hme (I know there are others) on Sun... all are
quite common, except perhaps sis, and I'd expect them to be
supported at the least.  ep are also fairly ubiquitous.

FWIW, I hope that the sis-compatible NatSemi chips become the
"next Tulip".  Now that Intel bought DEC's chip business, and the
future of the Tulip is uncertain, I'd really like an alternative
to 3Com.  And I don't trust Intel to "play nice" with the fxp.

The NS-83815 does support long frames.  If drivers support it,
VLAN tags don't screw up MTU. :-)  I've not yet benched such a
chip under load to compare with dc, de, fxp, or xl, so I can't
comment there.  It's on my neverending "to do" list...

But I'm rambling.  What ether chip do you have, Jeff?

Of course, you can always build your own ISO.  It's not my
favorite thing in the world to do, but I can think of worse. ;-)


> True, but most software vendors/developers/manufacturers do NOT support
> static linking, describe how to do it in their install files, etc.,
> etc.  Making it hard for newbies to figure any of this out.  I'd LOVE to
> use all statically-linked software; drive-space is cheap.

I like to link statically for the mandatory binaries, and
dynamically for the rest.  Library upgrades (zlib comes to mind)
are much quicker when needed.

It's also handy to use "ldd" to see what libs a binary uses.
Else you must 1) keep track or 2) use objdump and grep the
output.


Eddy

Brotsman & Dreger, Inc. - EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
--

Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.

These last few lines are a trap for address-harvesting spambots.  Do NOT
send mail to <blacklist@xxxxxxxxx>, or you are likely to be blocked.