something more useful would be to write (or port say yaboot) a bootloader to dd to the bootstrap partition instead of the kernel, this way the bootloader can read its config from the root filesystem and load the kernel from the root filesystem. that would be much more straightforward... On Fri, May 11, 2001 at 12:04:08AM -0400, Jeremy T. Bouse wrote: > Hopefully someone on here can answer this one for me... I install'd my PPC > back during the Slink days and have just kept it updated all the way > through Potato and now actually have it running Unstable... My question > is if anyone knows how to make the kernel-image-* packages to actually > handle the boot loading steps... Currently this requires me to dd the > kernel image to the PPC PReP boot (type 41) partition manually... The > actually Slink install managed to handle this properly but no kernel > upgrade since then has been able to do so... Now with the current > 2.4.4 kernel-image package available I'm not sure which to dd to the > partition... > > Respectfully, > Jeremy T. Bouse > > -- > ,-----------------------------------------------------------------------------, > |Jeremy T. Bouse, CCNA - UnderGrid Network Services, LLC - www.UnderGrid.net | > | Public PGP/GPG fingerprint and location in headers of message | > | If received unsigned (without requesting as such) DO NOT trust it! | > | Jeremy.Bouse@UnderGrid.net - NIC Whois: JB5713 - undrgrid@UnderGrid.net | > `-----------------------------------------------------------------------------' -- Ethan Benson http://www.alaska.net/~erbenson/
Attachment:
pgpZIq6xC7lFD.pgp
Description: PGP signature