Originally posted by Grogan
View Post
Announcement
Collapse
No announcement yet.
Comparing The Ubuntu And Fedora Linux Kernels
Collapse
X
-
-
Originally posted by Sonadow View Postif you use backported drivers such as compat-wireless you will find that building drivers software stacks inside the kernel and not as modules is a huge no-no. Compat-wireless demands that the kernel's entire networking stack be built as a module, and if you build it into the kernel compat-wireless will not even proceed past the ./configure stage and you'd have no choice but to build a new modularized kernel.
I once found that I had to build the ethernet driver as a module in Redhat, or the network wouldn't come up after the reboot. That sucked... I thought I was doing a good thing building it in (this was back when it wasn't unusual to do that) but I had to get a physical reboot at the datacenter and then figure out what went wrong. The worst of it was it wasn't my server, I was doing it for someone else so I had to get them to call. Anyway, the driver was right there in kernel but Redhat wouldn't use it. I think that's because of the silly way they were using module aliases at the time. Calling the module alias both loads the module and is involved in initializing the network. (many years ago, and I can't remember the fine details)
Comment
-
Originally posted by Grogan View Postmake menuconfig
make
cp arch/x86/boot/bzImage /boot/vmlinuz-x.x.xx
make modules_install
cp System.map /boot/System.map-x.x.xx
Comment
Comment