Quote:
Originally Posted by kd5pbo
Why is
./configure
make
make install
not reliable?
|
becouse not all make files have an "uninstall" option and so is not so easy to remove the whole set of files. more easy is to install them inside a temp dir and after build your own tgz via makepkg. so you can install and remove binaries via pkgtools.
Quote:
Is there any reason to build modules as opposed to compiling them straight into the kernel? It seems everybody builds kernels differently, but nobody has an argument as to which is better and why.
|
ok: if you are compiling a module which is not part of the official kernel code (eg a driver related to some "unusual" device) you must build it externally, of course

for the common code of a vanilla kernel: to build a drive static or modular is just a problem of "taste". if you use always a device, for example if you use always the same sound card -as I do with my laptop sound card-, you can put the related alsa driver inside the monolitic part of the kernel (/boot/somewhere/vmlinuz). otherwise, if you use a device just few times -for example I plug my usb HD once a month for my backups- you can prefer to put the driver as module : linux will load it via hotplug (in slack is hotplug) just when you'll need it.
of course the more the static drivers the biggest the vmlinuz file. remember that if you want a rescue floppy the monolitic section of the kernel must be <1.44 MB.
I haven't a floppy drive in my laptop so I don't care about vmlinuz dimension and I tend to put almost all as static inside the kernel. but I'm just a desktop user with no special needs.
M