Good job :>
Thanks. :-)
When it comes to something as mission-critical and heavily used as an ethernet card, yer best bet is probably to build the driver into the kernel, unless you'll be poppin cards in and out on a frequent basis!
I left it modular, it seems to be working fine. I do see the wisdom in going monolithic for something like this (see below).
In any case, stay away from copying .config files between kernel versions. =) As you can see it can create a headache!
No kidding... I'm wondering if the "make oldconfig" I read about in the Kernel HOW-TO would allow for a more smooth creation of a new .config using settings in the old... Something to try out for the next kernel I guess... I also was under the impression that if a .config file didn't have an option, it would be added by a new kernel source-tree when I did a "make config" or "make menuconfig". Anyone know whether this is the case?
Heh, now imagine you had to do all of this remotely.
I got a taste of what that was like with this upgrade. I was lucky though, the box I was remotely upgrading was sitting in a closet a few feet away, not in a different state. It gave me a whole new appreciation for the perils of remote admin.
We have a box in VA, roughly 3.5 hours from here, with that same dang 3COM 3c509b card in it.
Er... Mine's a 3c905b... I hate 3com's numbering scheme - it lends itself to digit transposition problems.
The box was running a stock bloated 2.2.12 kernel and there was a need to rebuild the thing just to remove some unnecessary crap (and to upgrade to 2.2.14); the build was done module-less. Using modules in this instance would have been a Bad Thing to do, wouldn't ya say? :]
Agreed, though I'm others could make a case for the "modules are good" camp. My problem was pretty much confusion because "3c90x" appeared in two separate selections of networking hardware under YaST. The next things I want to look at are YP/NIS/NFS login authentication and file shares from the file server, and then SSH/SCP to replace telnet and ftp. More fun. :-) Take care, Argentium -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/