Re: How to autoload 3rd part kernel modules?

[David Z Maze <dmaze@debian.org>]

stan <stanb@awod.com> writes:

> I looked at thta, but I don't understand the function of (or how to use)
> the --apend-to-version flag. Could you clarify?

I like my built kernel packages to be labelled with the name of the
machine they're built for.  So,

  make-kpkg --append-to-version -arborway ... kernel-image
  make-kpkg --append-to-version -arborway ... modules-image

builds kernel-image-2.4.20-arborway, openafs-modules-2.4.20-arborway,
alsa-modules-2.4.20-arborway, and so on; modules appear in
/lib/modules/2.4.20-arborway; `uname -r` says 2.4.20-arborway.
Whatever string you provide to --append-to-version becomes part of the
kernel version everywhere it's used.

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