Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Mon, 22 Dec 2008, Derek Atkins wrote: > Jarod Wilson <jarod-ajLrJawYSntWk0Htik3J/w at public.gmane.org> writes: > >>> The thing I like about dkms is that it happens automagically. When a >>> new kernel is installed, dkms recompiles the kernel for it with no user >>> intervention. >> >> For the record, same thing with akmods. > > The only problem with dkms (I've never heard about akmods) is that > it doesn't build the module for the new kernel until you reboot. > That doesn't help if you have a module that needs to be in the > preboot (initrd). Imagine if you need a third-party disk driver > module -- how would you solve that with a dkms or akmod solution? I suppose you'd need an initrd that has the ability to run dkms without gaining access to the local disk. Perhaps mount an NFS volume with access to the necessary kernel headers and tools required for the compile. Alternatively, don't buy a disk controller that requires a third party module.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |