You prolly don't have loopback device support compiled into the kernel,
which you need for a ton of things :)
So go compile in support for it, do any of the MBR config stuff you
need to do, and use:
dd if=kernel_image_name of=/dev/fd0 bs=1440k
To make a bootdisk. I think that's what I use. Now, that won't do the
whole rescue bit but it supports the general single mode stuff, etc.
Plus, the kernel loads into memory really fast when you do it this way
since the kernel image is actually a boot image. Do "file kernel_image_name"
to see what I'm saying :)
[root@circuit /root]# file /boot/vmlinuz-2.4.3
/boot/vmlinuz-2.4.3: x86 boot sector
as it is on my system.
On 4 Apr 2001, Dominic Mitchell wrote:
>
> Hi,
>
> I just made a bootdisk for kernel 2.2.18 which seems to be working
> correctly. However I do not understand why 'mkbootdisk' complains
> that all of my loopback devices are in use and can't open
> /vmlinuz-2.2.18. See below.
>
> Would someone shed some lights on this?
>
> Thanks.
>
> Dominic.
>
> $ mkbootdisk --verbose 2.2.18
> Insert a disk in /dev/fd0. Any information on the disk will be lost.
> Press <Enter> to continue or ^C to abort:
> Formatting /dev/fd0... done.
> Copying /boot/vmlinuz-2.2.18... done.
> Creating initrd image... All of your loopback devices are in use!
> done.
> Setting up lilo... done.
> open /vmlinuz-2.2.18: No such file or directory
>
> But
>
> $ ls -l /vmlinuz-2.2.18
> -rw-r--r-- 1 root root 555336 avr 4 11:30 /vmlinuz-2.2.18
>
>
>
>
--
-Statux
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
