Lines Matching refs:root
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
11 from a different device. The previous root (from initrd) is then moved
30 3) if the root device is not /dev/ram0, the old (deprecated)
31 change_root procedure is followed. see the "Obsolete root change
33 4) root device is mounted. if it is /dev/ram0, the initrd image is
34 then mounted as root
38 6) init mounts the "real" root file system
39 7) init places the root file system at the root directory using the
41 8) init execs the /sbin/init on the new root filesystem, performing
45 Note that changing the root directory does not involve unmounting it.
65 the "normal" root file system is mounted. initrd data can be read
74 root=/dev/ram0
76 initrd is mounted as root, and the normal boot procedure is followed,
77 with the RAM disk mounted as root.
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
170 root=/dev/ram0 rw
177 e.g. LOADLIN C:\LINUX\BZIMAGE initrd=C:\LINUX\INITRD.GZ root=/dev/ram0 rw
185 append = "root=/dev/ram0 rw"
194 Changing the root device
197 When finished with its duties, init typically changes the root device
198 and proceeds with starting the Linux system on the "real" root device.
201 - mounting the new root file system
202 - turning it into the root file system
203 - removing all accesses to the old (initrd) root file system
206 Mounting the new root file system is easy: it just needs to be mounted on
207 a directory under the current root. Example:
209 # mkdir /new-root
210 # mount -o ro /dev/hda1 /new-root
212 The root change is accomplished with the pivot_root system call, which
215 [3]). pivot_root moves the current root to a directory under the new
216 root, and puts the new root at its place. The directory for the old root
219 # cd /new-root
223 Now, the init process may still access the old root via its
225 current root directory. All these references are dropped by the
230 Where what-follows is a program under the new root, e.g. /sbin/init
231 If the new root file system will be used with udev and has no valid
239 process should point to the new root directory
241 for the old root as the second argument
242 - a chroot program must be available under the old and the new root
243 - chroot to the new root afterwards
252 It is also possible to use initrd with an NFS-mounted root, see the
266 2) /sbin/init determines what is needed to (1) mount the "real" root FS
272 4) /sbin/init creates and populates the root file system (this doesn't
274 5) /sbin/init invokes pivot_root to change the root file system and
297 like the location of the root FS partition doesn't have to be provided at
309 Obsolete root change mechanism
316 It works by mounting the "real" root device (i.e. the one set with rdev
317 in the kernel image or with root=... at the boot command line) as the
318 root file system when linuxrc exits. The initrd file system is then
320 such a directory exists on the new root file system.
323 command options root, init, or rw. (If specified, they will affect
324 the real root file system, not the initrd environment.)
326 If /proc is mounted, the "real" root device can be changed from within
327 linuxrc by writing the number of the new root FS device to the special
328 file /proc/sys/kernel/real-root-dev, e.g.
330 # echo 0x301 >/proc/sys/kernel/real-root-dev
342 In case you did not want to use root=/dev/ram0 to trigger the pivot_root
349 echo 0x0100 >/proc/sys/kernel/real-root-dev
352 Once linuxrc exited, the kernel would mount again your initrd as root,
354 to build the right environment (maybe using the root= device passed on