Skip to contentSkip to conversation

documentation: Documentation/initrd.txt

PATCH Bodo Eggert 4 participants 4 messages Jul 27, 2006 1 message not in the archive Documentation

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

(now CCing the list, too)

Quoted 4 lines · Tom Horsley

I spent a long time the other day trying to examine an initrd image on a fedora core 5 system because the initrd.txt file is apparently obsolete. Here is a patch which I hope will reduce future confusion for others.

Your documentation is technically wrong, and there is a better explanation:

Documentation/initrd.txt     2006-07-27 18:58:19.000000000 +0200 renamed from Documentation/initrd.txt.ori 2006-07-27 18:49:25.000000000 +0200 +0 -0
@@ -15,6 +15,9 @@ initrd is mainly designed to allow syste

 where the kernel comes up with a minimum set of compiled-in drivers, and where additional modules are loaded from initrd.

+initrd has recently been obsoleted by initramfs, which is described in +Documentation/filesystems/ramfs-rootfs-initramfs.txt.
+
 This document gives a brief overview of the use of initrd. A more detailed discussion of the boot process can be found in [1].

Signature · 4 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.

http://david.woodhou.se/why-not-spf.html
#2 lore raw
Quoted 7 lines · Bodo Eggert
Quoted 4 lines

I spent a long time the other day trying to examine an initrd image on a fedora core 5 system because the initrd.txt file is apparently obsolete. Here is a patch which I hope will reduce future confusion for others.

Your documentation is technically wrong, and there is a better explanation:

I find it easy to believe my document is wrong, but looking at the Documentation/filesystems/ramfs-rootfs-initramfs.txt file would never have led me to believe that the initrd.img file was related in any way. The ramfs-rootfs-initramfs.txt file describes the the archive as being built into the kernel, so it needs updating too I guess (and fedora should change the name of the initrd files to be initramfs files so I'll look for documentation in the right place :-).

#3 lore raw
Quoted 9 lines · Tom Horsley
Quoted 7 lines · Bodo Eggert
Quoted 4 lines

I spent a long time the other day trying to examine an initrd image on a fedora core 5 system because the initrd.txt file is apparently obsolete. Here is a patch which I hope will reduce future confusion for others.

Your documentation is technically wrong, and there is a better explanation:

Quoted 9 lines

I find it easy to believe my document is wrong, but looking at the Documentation/filesystems/ramfs-rootfs-initramfs.txt file would never have led me to believe that the initrd.img file was related in any way. The ramfs-rootfs-initramfs.txt file describes the the archive as being built into the kernel, so it needs updating too I guess (and fedora should change the name of the initrd files to be initramfs files so I'll look for documentation in the right place :-).

It's largely kept all the old names for historical reasons. We *could* rename stuff, but then we'd also have to rename the mkinitrd package, the scripts that call it, etc etc for no real gain.

Dave

Signature · 1 line
http://www.codemonkey.org.uk
#4 lore raw
In reply to Tom Horsley
Quoted 10 lines · Tom Horsley
Quoted 7 lines · Bodo Eggert
Quoted 4 lines

I spent a long time the other day trying to examine an initrd image on a fedora core 5 system because the initrd.txt file is apparently obsolete. Here is a patch which I hope will reduce future confusion for others.

Your documentation is technically wrong, and there is a better explanation:

Quoted 9 lines

I find it easy to believe my document is wrong, but looking at the Documentation/filesystems/ramfs-rootfs-initramfs.txt file would never have led me to believe that the initrd.img file was related in any way. The ramfs-rootfs-initramfs.txt file describes the the archive as being built into the kernel, so it needs updating too I guess (and fedora should change the name of the initrd files to be initramfs files so I'll look for documentation in the right place :-).

Yes.

Documentation/initrd.txt renamed from Documentation/initrd.txt.ori +3 -0
@@ -15,6 +15,9 @@ initrd is mainly designed to allow syste
 where the kernel comes up with a minimum set of compiled-in drivers, and
 where additional modules are loaded from initrd.
 
+initrd has recently been obsoleted by initramfs, which is described in
+Documentation/filesystems/ramfs-rootfs-initramfs.txt.
+
 This document gives a brief overview of the use of initrd. A more detailed
 discussion of the boot process can be found in [1].
 
Documentation/filesystems/ramfs-rootfs-initramfs.txt renamed from Documentation/filesystems/ramfs-rootfs-initramfs.txt.ori +4 -0
@@ -96,6 +96,10 @@ All this differs from the old initrd in 
     into the linux kernel image.  (The directory linux-*/usr is devoted to
     generating this archive during the build.)
     
+    However, if you use one or more compressed cpio archives (concatenated) 
+    instead of an initrd image, they will be unpacked, too, possibly
+    replacing existing files.
+
   - The old initrd file was a gzipped filesystem image (in some file format,
     such as ext2, that had to be built into the kernel), while the new
     initramfs archive is a gzipped cpio archive (like tar only simpler,
Signature · 3 lines
Fun things to slip into your budget
Request for 'supermodel access' to the UNIX server.
	Just don't tell the PHB why your home directory is named 'jpgs.'