On Mon, 5 Mar 2001, Mike Galbraith wrote:
> On Mon, 5 Mar 2001, Mike Galbraith wrote:
>
> > On Mon, 5 Mar 2001, Richard B. Johnson wrote:
> >
> > > I tried Linux 2.4.2
> > > Now I'm in a load of trouble. I can't make a boot-disk to get back
> > > to 2.4.1 because I use initrd for my hard disk modules and the loop
> > > device is broken.
> >
> > What's wrong with 2.4.2 that makes you want to go back? Anyway, if
> > you grab Jens' patch, all will be peachy (at least for that kind of
> > basic usage).
>
> P.S.
> Are you saying that the initrd is broken again as well? (having
> trouble understanding the problem.. don't see why you need the
> loop device or rather how its being busted is connected to your
> [interpolation] difficulty in creating a new initrd)
>
> -EAGAIN ;-)
>
The initial RAM disk image is created using the loop device. You
can create a RAM disk image for initrd by using the ram device.
However, that doesn't work once the system has been booted off
it (try it, be ready for a complete hang).
Cheers,
Dick Johnson
Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Mar 07 2001 - 21:00:17 EST