On Tue, Dec 02, 2003 at 08:03:45PM +0100, Karsten Merker wrote: > On Tue, Dec 02, 2003 at 03:26:15PM +0100, Sven Luther wrote: > > On Wed, Nov 19, 2003 at 06:49:37PM +0100, Karsten Merker wrote: > > > On Wed, Nov 19, 2003 at 06:27:55PM +0100, Goswin von Brederlow wrote: > > > > Karsten Merker <[EMAIL PROTECTED]> writes: > [snip] > > > As we have no bootloader capable of pre-loading the ramdisk, the ramdisk > > > must be compiled in statically, which is currently done manually and with > > > patched sources. > > > > How do you solve this ? I have myself, when creating the kernel package, > > extracted all the part of the kernel build tree needed to embed the > > initrd in the kernel and put it in a separate > > (kernel-build-<kver>-<flavour>) package. > > > > Would this work for you also, or would it be problematic ? > > That might be an option, although I would like to avoid handling it > that way. Thiemo has started writing a tool capable of adding a > ramdisk to a "normal" kernel image. It does not yet fully work, but > it looks quite good already and I hope that we will have it fully > working within the next weeks.
There is already a tool doing that for sparc (piggyback it is called i think), and i was thinking about doing such a tool for powerpc too, but i was afraid i would have to redo all the same thing as is in the kernel already, thus duplicating effort. Plus there are various powerpc variants, and i am not (yet) fully familiar with all this stuff, and can only really test on one subarch. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
