Re: Kernel dependencies
'Fernando wrote:'
>
>So, it is very difficult for the Debian dependencies to cover all possible
>situations. I think that what is needed is a way for a sysadmin to register
>the kernel they install (whether provided by Debian or homemade) and all the
>info associated with that particular kernel, which more or less is the
>".config" file used to build it.
There is one more case you are omitting (and it's the killer): I
install some patches from linux-kernel to play with new features in
some modules. How do we make sure all packages know what to do in
this case? I'll repeat my interim solution: make kernel-package and
other kernel packages flexible and requiring user input (else someone
overwrites a perfectly good kernel with something that doesn't support
what they need).
--
Christopher J. Fearnley | Linux/Internet Consulting
cjf@netaxs.com, cjf@onit.net | UNIX SIG Leader at PACS
http://www.netaxs.com/~cjf | (Philadelphia Area Computer Society)
ftp://ftp.netaxs.com/people/cjf | Design Science Revolutionary
"Dare to be Naive" -- Bucky Fuller | Explorer in Universe
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: