Lines Matching full:system

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
14 initrd is mainly designed to allow system startup to occur in two phases,
25 When using initrd, the system typically boots as follows:
38   6) init mounts the "real" root file system
39   7) init places the root file system at the root directory using the
40      pivot_root system call
43   9) the initrd file system is removed
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.
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
120 system) must be compiled into the kernel.
123 file system on a block device, copying files to it as needed, and then
134  2) create an empty file system of the appropriate size, e.g.::
140  3) mount the file system, e.g.::
160     general system state (e.g. by reconfiguring network interfaces,
164  7) unmount the file system::
185 (rw is only necessary if writing to the initrd file system.)
214 and proceeds with starting the Linux system on the "real" root device.
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
228 The root change is accomplished with the pivot_root system call, which
247 If the new root file system will be used with udev and has no valid
276 kernel configuration at system installation. The procedure would work
279   1) system boots from floppy or other media with a minimal kernel
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
289      have to be a very usable system yet)
290   5) ``/sbin/init`` invokes ``pivot_root`` to change the root file system and
294      modules that was used to bring up the system (e.g. ``/initrd`` can be
297   8) now the system is bootable and additional installation tasks can be
301 normal system operation without requiring the use of a bloated "generic"
307 (ideally only one) and to keep the system-specific part of configuration
314 boot time, but the system loaded from initrd can invoke a user-friendly
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.)