Lines Matching full:be

9 various pieces of functionality that are important enough to be
10 available while a Linux kernel is coming up, but that don't need to be
26 archive to be used as the image or have the kernel build process build
33 Your cpio archive should be specified in CONFIG_INITRAMFS_SOURCE and it
34 will be used directly.  Only a single cpio file may be specified in
47 CONFIG_INITRAMFS_SOURCE.  Sources can be either directories or files -
51 specified directory name will be mapped to '/'.  When packaging a
52 directory, limited user and group ID translation can be performed.
53 INITRAMFS_ROOT_UID can be set to a user ID that needs to be mapped to
54 user root (0).  INITRAMFS_ROOT_GID can be set to a group ID that needs
55 to be mapped to group root (0).
57 A source file must be directives in the format required by the
59 file format).  The directives in the file will be passed directly to
63 initramfs image will be an aggregate of all of them.  In this way a user
65 Because device-special files cannot be created by a unprivileged user,
66 special files can be listed in a 'root-files' file.  Both 'root-image'
67 and 'root-files' can be listed in CONFIG_INITRAMFS_SOURCE and a complete
68 early userspace image can be built by an unprivileged user.
73 can really be interpreted as any legal argument to
116 - Insert unwieldy subsystem that doesn't really need to be in kernel
143 c) using initramfs.  The call to prepare_namespace() must be skipped.
144    This means that a binary must do all the work.  Said binary can be stored
146    initrd format, an cpio archive.  It must be called "/init".  This binary