Terry Polzin wrote:
I think the intent here is to have a medium to boot from should grub and or the MBR fail. The boot image off of the CD is meant for install/upgrade.
Don't forget "RESCUE" mode....
That's why I sugguested iso format. I know it's wasteful of a CD but I think it may be the only way to go if the whole initrd is desired.
On Thursday 05 February 2004 14:15, Bevan C. Bennett wrote:
Phil Schaffner wrote:
The above would work for installation boot, but seems he might want to
boot a more current kernel.
Ah. Good point.
Backing up a step, what is the real objective? Is a boot floppy with a
kernel required, or could the objective be satisfied by having (possibly
redundant) kernels on hard disk and making a GRUB boot (or LILO - won't
get into religious discussions) boot floppy?
That's why I was confused... I only ever use boot floppies for performing a reinstall or upgrade.
Going back... I don't seem to be able to reproduce the original problem.
# mkbootdisk --device /tmp/foo.img 2.4.22-1.2149.nptl # ls -l /tmp/foo.img -rw-r--r-- 1 root root 1474560 Feb 5 11:10 foo.img # ls -l .../fedora-1-core/images/*.img -rw-r--r-- 1 root root 1474560 Nov 3 15:44 bootdisk.img -rw-r--r-- 1 root root 1474560 Feb 5 09:42 drvblock.img -rw-r--r-- 1 root root 1474560 Nov 3 15:44 drvnet.img
What version of mkbootimg do you have? Are large numbers of strange drivers involved?
> rpm -q mkbootdisk
mkbootdisk-1.5.1-1
-- Keven Ring | They called it Paradise Lead Software Systems Engineer | I don't know why... The MITRE Corporation | When you call someplace Paradise (703)883-7026 | Kiss it goodbye....
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
