Intermec ck1 Reference Guide
Appendix A —
µClinux System
CK1 SDK Programmer’s Reference Manual
331
nodev bdev
nodev proc
nodev sockfs
nodev pipefs
ext2
nodev ramfs
jffs2
cramfs
nodev proc
nodev sockfs
nodev pipefs
ext2
nodev ramfs
jffs2
cramfs
The user application in the CK1
µClinux is compiled into a ROM file
system, which the kernel mounts at the boot time. This file system is quite
simple, space efficient read only file system mainly used for initial RAM
disks. The file structure of the ROM file system is defined in the make file.
All the executables created from the user applications are placed in the /bin
file, which are built in utilities. The GUI system and applications are
placed in /usr/local, which is a ROM file system. The user R/W areas are
/home and /var where the /home is a JFFS2 image in NAND Flash and
/var is an ext2 file system in SDRAM.
simple, space efficient read only file system mainly used for initial RAM
disks. The file structure of the ROM file system is defined in the make file.
All the executables created from the user applications are placed in the /bin
file, which are built in utilities. The GUI system and applications are
placed in /usr/local, which is a ROM file system. The user R/W areas are
/home and /var where the /home is a JFFS2 image in NAND Flash and
/var is an ext2 file system in SDRAM.
The rc script in the vendor specific file is executed in the boot time. This
script contains information of mounting the RAM file system to the end
systems the CK1
script contains information of mounting the RAM file system to the end
systems the CK1
µClinux. The RAM file system is a placement for the
regular table PC hard drives to store information like log files that the
applications produce. The CK1 also has a warm boot mechanism to ensure
that the data kept in RAMdisk does not get lost during warm boot. The
mount point for the file system is /var, but the CK1
applications produce. The CK1 also has a warm boot mechanism to ensure
that the data kept in RAMdisk does not get lost during warm boot. The
mount point for the file system is /var, but the CK1
µClinux also has the
/tmp directory in the root connected via a symbolic link to point to the
/var/tmp. The file system is uncompressed and mounts at the rc script. A
Scratch from the rc script can be like the following code.
/var/tmp. The file system is uncompressed and mounts at the rc script. A
Scratch from the rc script can be like the following code.
# mount ramdisk
/bin/mount -t ext2 /dev/rom0 /var
mkdir /var/tmp
mkdir /var/log
mkdir /var/run
mkdir /var/lock
/bin/mount -t ext2 /dev/rom0 /var
mkdir /var/tmp
mkdir /var/log
mkdir /var/run
mkdir /var/lock
The RAMdisk is mounted to the ext2 file system, which is reserved from
kernel and automatically created to the /dev/rom0 block device. Since the
RAMdisk is not lost when the CK1 warm boots, the system checks the
RAMdisk twice before mounting it.
kernel and automatically created to the /dev/rom0 block device. Since the
RAMdisk is not lost when the CK1 warm boots, the system checks the
RAMdisk twice before mounting it.
Serial Flash File System
The previous file systems used in CK1 are a default set of M5272
configuration file systems. The external serial Flash chip that the CK1
provides is mounted with the JFFS2. In the future, the more convenient
solution is the JFFS2 though it provides some benefits against the older
model and brings some advantages compared to CRAMFS. This section
inspects all of these solutions, including their advantages and
disadvantages.
configuration file systems. The external serial Flash chip that the CK1
provides is mounted with the JFFS2. In the future, the more convenient
solution is the JFFS2 though it provides some benefits against the older
model and brings some advantages compared to CRAMFS. This section
inspects all of these solutions, including their advantages and
disadvantages.
The CK1
µClinux provides two main types of file systems for use in
NAND Flash devices: CRAMFS and JFFS2. T