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,
"Mikkel L. Ellertson" <[EMAIL PROTECTED]> writes:
> >
> >
> mkinitrd needs to use the loop device to put files in the RAM disk>
> image. What happens if you run "modprobe loop"? Or if you are
> running a custom kernel, did you leave out loop device support?
> The other major cause of this er
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 s
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.
$ mkboot
