Lines Matching full:file
9 This RAM disk can then be mounted as the root file system and programs
10 can be run from it. Afterwards, a new root file system can be mounted
38 6) init mounts the "real" root file system
39 7) init places the root file system at the root directory using the
43 9) the initrd file system is removed
47 procedure. Also note that file systems mounted under initrd continue to
58 Loads the specified file as the initial RAM disk. When using LILO, you
59 have to specify the RAM disk image file in /etc/lilo.conf, using the
65 the "normal" root file system is mounted. initrd data can be read
67 in this case and doesn't necessarily have to be a file system image.
90 Examining the contents of an existing image file is just as simple::
99 First, a directory for the initrd file system has to be created on the
100 "normal" root file system, e.g.::
107 If the root file system is created during the boot procedure (i.e. if
108 you're building an install floppy), the root file system creation
119 needed to execute programs from initrd (e.g. executable format and file
123 file system on a block device, copying files to it as needed, and then
124 copying the content of the block device to the initrd file. With recent
134 2) create an empty file system of the appropriate size, e.g.::
140 3) mount the file system, e.g.::
150 environment. Don't forget the most important file, ``/sbin/init``
164 7) unmount the file system::
168 8) the initrd is now in the file "initrd". Optionally, it can now be
185 (rw is only necessary if writing to the initrd file system.)
217 - mounting the new root file system
218 - turning it into the root file system
219 - removing all accesses to the old (initrd) root file system
220 - unmounting the initrd file system and de-allocating the RAM disk
222 Mounting the new root file system is easy: it just needs to be mounted on
247 If the new root file system will be used with udev and has no valid
283 (i.e. device type, device drivers, file system) and (2) the
288 4) ``/sbin/init`` creates and populates the root file system (this doesn't
290 5) ``/sbin/init`` invokes ``pivot_root`` to change the root file system and
296 ``/dev/ram0`` or ``/dev/rd/0`` to a file)
309 generated with all the necessary modules. Then, only ``/sbin/init`` or a file
334 root file system when linuxrc exits. The initrd file system is then
336 such a directory exists on the new root file system.
340 the real root file system, not the initrd environment.)
344 file /proc/sys/kernel/real-root-dev, e.g.::
348 Note that the mechanism is incompatible with NFS and similar file