Home
last modified time | relevance | path

Searched refs:initramfs (Results 1 – 24 of 24) sorted by relevance

/linux-2.6.39/usr/ !
DKconfig2 # Configuration for initramfs
11 initramfs image. A cpio archive should contain a filesystem archive
12 to be used as an initramfs image. Directories should contain a
13 filesystem layout to be included in the initramfs image. Files
18 initramfs image will be the aggregate of all of them.
94 prompt "Built-in initramfs compression mode" if INITRAMFS_SOURCE!=""
96 This option decides by which algorithm the builtin initramfs
104 initramfs, mail me (Alain Knaff) <alain@knaff.lu>.
115 Do not compress the built-in initramfs at all. This may
117 built-in initramfs will be compressed at a later stage
[all …]
DMakefile38 initramfs := $(CONFIG_SHELL) $(srctree)/scripts/gen_initramfs_list.sh macro
54 cmd_initfs = $(initramfs) -o $@ $(ramfs-args) $(ramfs-input)
67 $(Q)$(initramfs) -l $(ramfs-input) > $(obj)/.initramfs_data.cpio.d
/linux-2.6.39/Documentation/filesystems/ !
Dramfs-rootfs-initramfs.txt1 ramfs, rootfs and initramfs
82 What is initramfs?
97 - The old initrd was always a separate file, while the initramfs archive is
103 initramfs archive is a gzipped cpio archive (like tar only simpler,
110 initramfs is not expected to return to the kernel. (If /init needs to hand
115 umount the ramdisk. But initramfs is rootfs: you can neither pivot_root
126 Populating initramfs:
129 The 2.6 kernel build process always creates a gzipped cpio format initramfs
135 initramfs archive, which will automatically be incorporated into the
145 file /bin/busybox initramfs/busybox 755 0 0
[all …]
D00-INDEX87 ramfs-rootfs-initramfs.txt
88 - info on the 'in memory' filesystems ramfs, rootfs and initramfs.
/linux-2.6.39/Documentation/early-userspace/ !
Dbuffer-format.txt1 initramfs buffer format
9 (initramfs) protocol. The initramfs contents is passed using the same
11 is different. The initramfs buffer contains an archive which is
13 the initramfs buffer format.
15 The initramfs buffer format is based around the "newc" or "crc" CPIO
18 initramfs buffer is thus a single .cpio.gz file.
20 The full format of the initramfs buffer is defined by the following
28 initramfs := ("\0" | cpio_archive | cpio_gzip_archive)*
39 In human terms, the initramfs buffer contains a collection of
DREADME17 - initramfs, a chunk of code that unpacks the compressed cpio image
22 The cpio file format used by initramfs is the "newc" (aka "cpio -H newc")
60 initramfs image will be an aggregate of all of them. In this way a user
120 custom initramfs images that meet your needs exactly.
141 c) using initramfs. The call to prepare_namespace() must be skipped.
143 into initramfs either via modifying usr/gen_init_cpio.c or via the new
148 comes via an initramfs cpio archive. If this is not the case,
/linux-2.6.39/init/ !
DMakefile9 obj-$(CONFIG_BLK_DEV_INITRD) += initramfs.o
DKconfig883 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
/linux-2.6.39/Documentation/s390/ !
Dzfcpdump.txt42 To use the zfcpdump userspace application in an initramfs you have to do the
50 * Use an initramfs config file like the following:
77 * Issue "make image" to build the zfcpdump image with initramfs.
/linux-2.6.39/scripts/ !
Dgen_initramfs_list.sh19 -o <file> Create compressed initramfs file named <file> using
29 as direct input to initramfs.
/linux-2.6.39/Documentation/firmware_class/ !
DREADME88 (probably within initramfs).
103 within the kernel image, probably within initramfs.
/linux-2.6.39/arch/score/ !
DKconfig108 add initrd or initramfs image to the kernel image.
/linux-2.6.39/Documentation/ !
Dxz.txt37 For decompressing the kernel image, initramfs, and initrd, there
74 size for in-kernel use (maybe more is OK for initramfs). The presets
Dkeys-trusted-encrypted.txt16 when the kernel and initramfs are updated. The same key can have many saved
D00-INDEX128 - info about initramfs, klibc, and userspace early during boot.
/linux-2.6.39/drivers/net/wireless/ipw2x00/ !
DKconfig38 including the firmware and a firmware loader in an initramfs.
99 including the firmware and a firmware loader in an initramfs.
/linux-2.6.39/arch/unicore32/configs/ !
Ddebug_defconfig8 # Initial RAM filesystem and RAM disk (initramfs/initrd) support
/linux-2.6.39/Documentation/power/ !
Dswsusp-and-swap-files.txt50 to a swap file allowing the resume to be initiated from an initrd or initramfs
Dswsusp.txt291 cannot be initiated from an initrd or initramfs image. See
/linux-2.6.39/Documentation/filesystems/nfs/ !
Dnfsroot.txt13 non-disk device. This may be an initramfs (see Documentation/filesystems/
14 ramfs-rootfs-initramfs.txt), a ramdisk (see Documentation/initrd.txt) or a
/linux-2.6.39/drivers/base/ !
DKconfig47 This option does not affect initramfs based booting, here
/linux-2.6.39/Documentation/fb/ !
Duvesafb.txt25 early boot, you will have to include v86d into an initramfs image, and
/linux-2.6.39/Documentation/usb/ !
Dpower-management.txt187 process, by means of a program or script running from an initramfs
/linux-2.6.39/drivers/scsi/ !
DKconfig272 # complete. The idea is to use it in initrd/ initramfs scripts. You modprobe