On Thu, Aug 06 2009, Philipp Klaus Krause wrote:
> Could you explain this a bit more?
I'll try.
> Why has initrd generation support been dropped?
It has not.
>>From a user perspective:
>
> Build a kernel using
>
> make-kpkg --initrd binary
> and installing it via
> dpkg -i
> results in a working kernel when using 11.015.
> It results in an unbootable system when using 12.017.
That is not correct. I still use exactly that, and it works fine
here. I have one machine that does not use innitramfs, and naother that
does, and both work fine.
> The Rationale.gz states as _first_ reason to use kernel-package:
>
> i) Convenience. I used to compile kernels manually, and it
> involved a series of steps to be taken in order;
> kernel-package was written to take all the required steps (it
> has grown beyond that now, but essentially, that is what it
> does). This is especially important to novices: make-kpkg
> takes all the steps required to compile a kernel, and
> installation of kernels is a snap.
>
> It seems this no longer applies.
Does here.
What I have done, though, is actually read the man page, and
populated my /etc/kernel/*.d directories with the supplied example
scripts, differently on each machine, and things still work fine.
manoj
--
"I'd crawl over an acre of 'Visual This++' and 'Integrated Development
That' to get to gcc, Emacs, and gdb. Thank you." (By Vance Petree,
Virginia Power)
Manoj Srivastava <sriva...@acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
