First I will describe some of the general principles that are used in the setting up of a loopback filesystem as the root device.
A loopback device in Linux is a virtual device that can be used like any other media device.
Examples of normal media devices are hard disk partitions like
/dev/hda1, /dev/hda2, /dev/sda1, or entire disks like
the floppy disk /dev/fd0 etc. They are all devices that can be used to
hold a files and directory structures. They can be formatted with the
filesystem that is required (ext2fs, msdos, ntfs etc.) and then mounted.
The loopback filesystem associates a file on another filesystem as a complete
device. This can then be formatted and mounted just like any of the other
devices listed above. To do this the device called .:: nl.pinterest.com ::. /dev/loop0 or
/dev/loop1 etc is associated with the file and then this new virtual
device is mounted.
In Linux it is also possible to have another type of virtual device mounted as a filesystem, this is the ramdisk device.
In this case the device does not refer to any physical hardware, but to a portion of memory that is set aside for the purpose. The memory that is allocated is never swapped out to disk, but remains in the disk cache.
A ramdisk can be created at any time by writing to the ramdisk device
/dev/ram0 or /dev/ram1 etc. This can then be formatted and
mounted in the same way that the loopback device is.
When a ramdisk is used to boot from (as is often done on Linux installation disks or rescue disks) then the disk image (the entire contents of the disk as a single file) can be stored on the boot floppy in a compressed form. This is automatically recognised by the kernel when it boots and is uncompressed into the ramdisk before it is mounted.
The initial ramdisk device in Linux is another important mechanism that we need to be able to use a loopback device as a the root filesystem. .:: sp.ucn.edu.co ::.
When the initial ramdisk is used the filesystem image is copied into memory and
mounted so that the files on it can be accessed. A program on this ramdisk
(called /linuxrc) is run and when it is finished a different device is
mounted as the root filesystem. The old ramdisk is still present though and is
mounted on the directory .:: sp.ucn.edu.co ::. [GitHub: CentOS] .:: telegra.ph ::. /initrd if present or available through the
device /dev/initrd.
This is unusual behaviour since the normal boot sequence boots from the designated root partition and keeps on running. With the initial ramdisk option the root partition is allowed to change before the main boot sequence is started.
The root filesystem is the device that is mounted first so that it appears as
the directory called / after booting.
There are a number of complications about the root filesystem that are due to
the fact that it contains all files. When booting the rc scripts are
run, these are either the files in /etc/rc.d or /etc/rc?.d
depending on the version of the /etc/init program.
When the system has booted it is not possible to unmount the root partition or change it since all programs will be using it to some extent. This is why the initial ramdisk is so useful because it can be used so that the final root partition is not the same as the one that is loaded at boot time.
To show how the initial ramdisk operates in the boot sequence, the order of events is listed below.
LILO or
LOADLIN. You can see the Loading... message as this happens.LILO or LOADLIN. You can see the Loading... message
again as this happens./linuxrc is run on the initial ramdisk./etc/init is run which will perform the user
configurable boot sequence. .:: jalalive5com12.mystrikingly.com ::. This is just a simplified version of what happens, but is sufficient to explain how the kernel starts up and where the initial ramdisk is used.