Filter
Top Products
14 Linux RFS v1.3.0 Porting Guide
Figure 3-8 RFS Filesystem configuration for FAT16
If you decide to build RFS Filesystem as FAT16 type, you always make the filenames with the
native language in the 8.3 format regardless of NLS support. Why is this possible?
The NLS is used for the conversion the filenames with the native language to/from Unicode,
but the conversion doesn’t happen at the FAT16. So, FAT16 doesn’t need any codepage.
☞ NOTE
If you make filenames with the native language at FAT16 and the length of the name is longer
than the 8.3 format, the filename could be broken at the last character.
3.3.2 Mounting RFS with codepage
If you want to use RFS Filesystem supporting NLS, you should use “codepage” option to mount
RFS Filesystem like the following.
Shell> mount –t rfs /dev/stl0/3 /tmp –o codepage=cp949
This command mounts the RFS Filesystem found on ‘/dev/stl0/3’ at the directory ‘/tmp’.
If you selected the NLS support when building the kernel image for the target, the mount
option “codepage=cp949” sets the default codepage as ‘cp949’. And then RFS supports
filenames with the native language of ‘cp949’ character set. If the codepage 949 isn’t build at
the target, this command will fail.
Shell> mount –t rfs /dev/stl0/3 /tmp
This command mounts the RFS Filesystem found on ‘/dev/stl0/3’ at the directory ‘/tmp’.
If you didn’t select the NLS support when you built the kernel image, this command will
success and RFS is able to support filenames with the 7-bit ASCII characters only.