On Sun, Sep 17, 2000 at 07:32:08PM +1000, Jeff Waugh wrote:
> > Well you are certainly asking the right list, as Herbert does the
> > kernel stuff ... I tend to do:
> >
> > In the kernel directory (e.g. kernel-source-2.2.17):
>
> Why should I make kernel packages instead of just compiling and using
> kernels straight from tarballs? Seeing that the kernel is largely unrelated
> to everything else (dependencies and what-not - don't pick on me too much
> for this generalisation), what is the point in packaging one that you're
> goign to be building anyway?
A couple of reasons:
- you are building a kernel for a slower machine
- you intend to distribute this kernel onto a lot of machines (e.g. beowulf)
- you'd like to have modules (lm_sensors, alsa, pcmcia) built easily
(look in /usr/src/modules)
- you'd like to have you kernel configuration, system maps, etc. always in
sync (I find if I do it by hand, I always neglect to update the system
map -- which makes kernel opps that much more useless)
/usr/doc/kernel-package/Rationale.gz is useful reading. It lists a further 9
reasons why you'd want to and 3 reasons not to:
- `cookie cutter' approach
- not traditional in the non-Debian world
- requires use of fakeroot/super/sudo in order to create the .deb
Anand
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
