10/8 I have a computer running RedHat 6.0. I just got an ethernet
installing a NIC, but I'd rather not reinstall. Thanks.
\_ You can find a list of drivers in
/usr/src/linux/Documentation/Configure.help; make sure the
driver for your card is configured in your kernel or compiled
as a module.
\_ I installed a bsd box a while ago with totally random hardware
which was all recognized instantly. I had no idea what all that
\_ Did writing that give you a big ego boost?
\_ Don't forget to mention that it isn't a real sentence.
It doesn't have a period at the end.
\_ Uhm, okay.
crap was, but bsd did. And I don't have to rebuild the kernel
every Monday, Thursday and every second Saturday.
\_ WTF?! Isn't linux supposed to just work? This looks worse
than fucking windows! -sameer
\_ This sounds as if you are the victim of one or
more unrealistic expectations. "All OSes suck
equally. Some OSes are less equal than others..."
-brg
\_ yes, everything just magically works right off the
configuration is fairly easy. just
route add -net 128.32.43.0/24 eth0
ifconfig eth0 128.32.43.52
route add default gw 128.32.43.254
insmod 3c509.o
\_ Unless of course you're using a modern OS which
doesn't require you to recompile your kernel just
to add new hardware. At least linux is up to the
level SunOS 4 was at a decade ago and doesn't make
you recompile the kernel to repartition your disks
like the truly ancient Unixes.
route add -host 128.32.43.52 eth0
you're done (i just made up ip numbers).
\_ Oh yeah, that was totally trivial. How obvious to any
fool.
\_ what I originally wrote was something different.
some dipshit changed what i wrote. basically
windows 95 does the exact same thing (load driver,
configure interface, and create routing table) but
has some pretty front end which you could easily
replicate under any other OS.
\_ don't be an idiot. If the support isn't compiled into
the kernel, of course it won't work. -tom
\_ troll deleted
\_ It seems to be fairly common practice these days
for Linux distributors to configure everything as
a module that isn't in the core kernel, so you don't
generally have to recompile kernels. But if you have
an especially outlandish device you might have to
update your kernel sources and recompile. If you buy
a machine from VA Linux, for example, they will
patches and other good things for your box which
constitute their "officially supported" kernel, which
keeps you from having to track down quite so many
random little patches (and they give you precompiled
versions, too.) ... In theory, there's nothing which
prevents you from adding modules in after the kernel
is compiled, provided you get the symbol versions
right. But I haven't seen any concrete examples of
people doing this, especially since reconfiguring
one's kernel isn't particularly difficult, what with
"make xconfig" and all. -brg
\_ wait, I thought people recompiled and installed
linux kernels all the time? Isn't this the point
of an open src? you modify it to your needs? I
remember having to recompile an old version of
slackware on my 386 just to get ps2 mouse
support. - paolo
\_ In the days when 1MB of memory costed $50
yeah. |
http://csua.com/feed/