From b41c679e9ef7e7e0cef9f2102d93f825102f831d Mon Sep 17 00:00:00 2001 From: freesource Date: Wed, 9 Jan 2002 19:18:39 +0000 Subject: [PATCH] Even better FAQ 13 explanation. --- doc/html/index.html | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/doc/html/index.html b/doc/html/index.html index 261d76a..df1b136 100644 --- a/doc/html/index.html +++ b/doc/html/index.html @@ -3,7 +3,7 @@ -
$Id: index.html,v 1.66 2002/01/07 19:27:21 freesource Exp $
+
$Id: index.html,v 1.67 2002/01/09 18:40:19 freesource Exp $

@@ -1105,19 +1105,26 @@ filesystem.

If you are creating a boot disk in which the kernel knows where to -find the root filesystem, then nothing else but a kernel is required +find the root filesystem and the root filesystem is uncompressed, then nothing +else but a kernel is required assuming it is copied in a way that is starts at block 0 on the device media, and then rdeved in such a way that it knows that the ramdisk and the prompt flag are on, i.e., rdev -r /dev/fd0 49152, and that the root filesystem starts at block 0 on the other floppy.   -However, the 2 disk compression method just copies over the root filesystem +However, the 2 disk compression method copies over a compressed root +filesystem to the second disk.  In order to boot /dev/fd0 from /dev/fd0 when the root -filesystem is just copied over, the kernel has to -mount the initial boot disk, and then after the new root disk is inserted, -it remounts that disk.  In order to accomplish this an initrd is +filesystem is compressed the kernel has to +mount the initial boot disk, and then after the new root disk is inserted it +uncompresses the root filesystem and then changes over to the real root +device, +which in this case is /dev/ram1 where the uncompressed filesystem now +resides. +   +In order to accomplish this an initrd is required.   Initial ram disks are essentially mini filesystems with the bare necessities to allow a special init type file called linuxrc to