Sukrit <[EMAIL PROTECTED]> writes:

> 1. How do i decide which modules to load at boot time, which file is
> to be edited?

/etc/modules

> (i am thinking that i'll compile support for lots of devices -
> cd-writer, different network cards - as modules that way i won't
> have to recompile kernel when i add those devices. So i don't want
> all my modules to be loaded at boot time. Also, i don't want to
> dynamically and automatically load/unload modules)

...I was going to suggest using the built-in module autoloading
support, which works well for me, but I guess not.  :-)

> 3. i compiled the kernel, now do i need to get kernel-headers? What is
> the function of kernel-headers?

I'm not entirely clear.  In unstable, there is a kernel-build-*
package, which provides everything you need to build kernel modules
against the kernel in question; the kernel-headers-* package alone
frequently isn't enough.  But if you compiled the kernel, then you
already have kernel source, which means you already have a headers
tree without doing anything special.

> 4. Right now i am copying kernel bzImage into /boot renaming it, and
> editing lilo. Also for modules i 
> #make modules
> #make modules_install
>
> If i already have the same version of kernel running does old module
> tree get over-written or not?

Yes, it does overwrite the existing modules.

> ps please don't suggest i use make-kpkg :) i want to understand the
> process first before i choose automation.

I'm going to go ahead and suggest kernel-package anyways.  The
fundamental steps are the same (configure, compile, install) except
that you use Debian tools to install, which means you can later use
Debian tools to uninstall.  kernel-package also provides a much better
interface if you're going to try to add in modules that don't come
distributed with the kernel (OpenAFS, lm-sensors, ALSA, ...)

-- 
David Maze         [EMAIL PROTECTED]      http://people.debian.org/~dmaze/
"Theoretical politics is interesting.  Politicking should be illegal."
        -- Abra Mitchell


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to