···239239 A description of the process of mounting the root file system can be240240 found in:241241242242- Documentation/early-userspace/early_userspace_support.rst242242+ Documentation/driver-api/early-userspace/early_userspace_support.rst243243244244245245
···105105 - The old initrd file was a gzipped filesystem image (in some file format,106106 such as ext2, that needed a driver built into the kernel), while the new107107 initramfs archive is a gzipped cpio archive (like tar only simpler,108108- see cpio(1) and Documentation/early-userspace/buffer-format.rst). The108108+ see cpio(1) and Documentation/driver-api/early-userspace/buffer-format.rst). The109109 kernel's cpio extraction code is not only extremely small, it's also110110 __init text and data that can be discarded during the boot process.111111···159159set permissions or create device nodes in the new archive. (Note that those160160two example "file" entries expect to find files named "init.sh" and "busybox" in161161a directory called "initramfs", under the linux-2.6.* directory. See162162-Documentation/early-userspace/early_userspace_support.rst for more details.)162162+Documentation/driver-api/early-userspace/early_userspace_support.rst for more details.)163163164164The kernel does not depend on external cpio tools. If you specify a165165directory instead of a configuration file, the kernel's build infrastructure
+1-1
usr/Kconfig
···1818 When multiple directories and files are specified then the1919 initramfs image will be the aggregate of all of them.20202121- See <file:Documentation/early-userspace/early_userspace_support.rst> for more details.2121+ See <file:Documentation/driver-api/early-userspace/early_userspace_support.rst> for more details.22222323 If you are not sure, leave it blank.2424