Chapter 2.2 Compiling and installing kernel modules
1. with the kernel not booted, mount the root filesystem in the top level of
the kernel pool:
# mount root_fs mnt -o loop
If the above fails you may need to recompile your host's system kernel,
enabling support for loopback device (under Block Devices).
--- end of change ---
I am sure it is obvious for gurus but regular users can be left puzzled what
exactly is wrong, as there is no error message to suggest that the kernel
needs to be recompiled.
On Tue, Jul 08, 2003 at 01:07:48PM +0930, Vesselin Kostadinov wrote:
> Please add:
> If the above fails you may need to recompile your host's system kernel,
> enabling support for loopback device (under Block Devices).
> --- end of change ---
> I am sure it is obvious for gurus but regular users can be left puzzled what
> exactly is wrong, as there is no error message to suggest that the kernel
> needs to be recompiled.
No contradiction, just an addition:
And a regular user might do a different trick to set up his root_fs: The
umlkernel can be launched with the real root. Then only places writable for
the user launching it will be changeable by the user, so it does not harm.
Using a different init (init=/bin/bash or some own startup script taking
care of proc et al), you can get an environment up where the user is root
;-) but the rc files of the original system are not run.
So you can connect your future rootfs as additional ubd to this process, or
dd it from inside this environment, mkfs and whatever you need...
A missing loop driver in the hosts configuration is no harm for continuing
Get latest updates about Open Source Projects, Conferences and News.