
USAGE
=====

Run the make_initrd script to process the initrd_source directory into a gzipped
initial ram disk. The initial ram disk can be used to pre-load the kernel 
drivers required for the real root file system. In this case we are loading the
drivers for a DiskOnChip module and then setting the real root device to the DOC
so the rest of the INIT process can be run from the DiskOnChip. Take a look at
the initrc script in the initrd_source directory to see how the process happens.

The output of the make_initrd script is the file "initrd.gz"
Use the kernel command line parameter below to boot to the initrd image.

initrd=/some_directory/initrd.gz

If using the TS-5300 the initrd.gz could be stored on the B: drive and the kernel
could be on the A: drive, then you would pass the following to loadlin.exe:

initrd=B:\initrd.gz

NOTES
=====

You must be root user to untar the /initrd_source/dev directory.

When the kernel is done initializing it will run the linuxrc script file. 
If you rename the symlink called bb_linuxrc to linuxrc, the initial ram disk
will start a bash prompt instead of continuing to run INIT from the DiskOnChip.
You can use this to explore the initial ram disk environment.

If you have a directory in the root of the real file system called "initrd" the 
kernel will load the initial ram disk file system under /initrd instead of releasing
the memory back to the kernel

If your application is small enough, less than 1 MB, you can run it directly
from the initial ram disk. This would save the cost of DiskOnChip or Compact
Flash as well as providing immunity from corruption due to power loss.

Please contact us if you have questions or comments.

Technologic Systems, Inc.
info@embeddedx86.com
www.embeddedx86.com
(480) 837-5200 usa
(480) 837-5300

Changelog
---------
20031107 Made to work with DiskOnChip for TS-Linux 3.03r1
20040713 Updated for TS kernel 2.4 kernel 2.4.23
20040811 Updated lib/modules for TS kernel 2.5 kernel 2.4.23



