Specifications

Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.25 (wd@xpert) (gcc version 3.3.3 (DENX ELDK 3.1.1 3.3.3-9)) #1 Sun Jun 12 18:32:18 MEST 2005
On node 0 totalpages: 4096
zone(0): 4096 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock6 rw rootfstype=jffs2 ip=192.168.3.80:192.168.3.1::255.255.255.0:tqm860l:eth1:off panic=1
Decrementer Frequency = 187500000/60
Calibrating delay loop... 49.86 BogoMIPS
...
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (jffs2 filesystem).
Freeing unused kernel memory: 56k init
BusyBox v0.60.5 (2005.03.07-06:54+0000) Built-in shell (msh)
Enter 'help' for a list of built-in commands.
# ### Application running ...
# mount
rootfs on / type rootfs (rw)
/dev/mtdblock6 on / type jffs2 (rw)
/proc on /proc type proc (rw)
# df /
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 4096 2372 1724 58% /
9.5.3. Root File System on a cramfs File System
cramfs is a compressed, read-only file system.
Advantages are:
file system uses compression, thus making efficient use of flash memory•
Allows for quick boot times as only used files get loaded and uncompressed•
Disadvantages are:
only the whole image can be replaced (not individual files)•
additional storage needed for writable persistent data•
mkcramfs tool does not support device table, so we need root permissions to create the required
device files
•
To create a cramfs based root file system please proceed as follows:
Create a directory tree with the content of the target root filesystem. We do this by unpacking our
master tarball:
$ mkdir rootfs
$ cd rootfs
$ tar -zxf /tmp/rootfs.tar.gz
1.
Create the required device files. We do this here by unpacking a special tarball which holds only the
device file entries. Note: this requires root permissions!
# cd rootfs
# tar -zxf /tmp/devices.tar.gz
2.
9.5.3. Root File System on a cramfs File System 116