On Fri, Jan 27, 2006 at 11:26:04PM +0100, Jonas Smedegaard wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, 27 Jan 2006 20:37:51 +0100 > Sven Luther <[EMAIL PROTECTED]> wrote: > > > On Tue, Jan 24, 2006 at 10:35:43AM +0100, Simon Richter wrote: > > > Hi, > > > > > > Paul TBBle Hampson wrote: > > > > > > >Reading the manpage of mkvmlinuz indicates it can _include_ an > > > >initrd in its output, but doesn't indicate it can assemble a > > > >ramdisk from scripts > > > >+ modules + fairy dust. (Or whatever it is they use...) > > > > > > Yes, that was badly worded. If it is rightfully not detected as a > > > ramdisk creator because it isn't one, then the problem of not > > > depending on one still remains, however. > > > > Bah, the kernel depends on a ramdisk creator, so there should be no > > problem. > > > > The ramdisk can be provided by the user and can be any kind of random > > ramdisk tool, this is used for example by d-i which builds his own > > ramdisk. > > > > Furthermore mkvmlinuz can be used to build zImage kernels without > > ramdisk. > > > > So, no there is no need for a dependency on a ramdisk creator. > > I agree. But perhaps a suggests then? And suggest a kernel image too?
No, i don't think this is needed. The kernel should be fixed though to again include the dependency on yaird or initramfs-tools, don't know who of maks or waldi broke that though :) Will fix tomorrow in any case. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
