|This version of this document is no longer maintained. For the latest documentation, see http://www.qnx.com/developers/docs.|
QNX 4 compatible filesystem support
driver ... qnx4 qnx4_options... &
Where driver is any of the devb-* drivers, and qnx4_options is one or more of the following, separated by commas:
- Never embed inode details; always place in fixed-size .inodes.
- Enable a more aggressive file-extent over-allocation heuristic.
- Calculate/store .bitmap details for removable media too.
- Attempt to repair any file marked as "busy" on the filesystem (i.e. a file that was being grown or shrunk when the system was improperly shutdown). The default action is to return EBADFSYS to any attempt to open such a file; this option will instead truncate the file to its last-known valid size, unset the "busy" indicator, and allow access. This truncation may result in lost data and unused blocks marked as used in the bitmap, so run chkfsys later to ensure full filesystem consistency.
The fs-qnx4.so shared object provides support for QNX 4 filesystems. It's automatically loaded by the devb-* drivers when mounting a QNX 4 filesystem.
- To enable support for long filenames (more than 48 characters) on an
existing QNX 4 compatible filesystem, login as root and
create an empty, read-only file named .longfilenames in
the root directory of that filesystem.
To enable support for long filenames on a new QNX 4 filesystem, use the -N option to dinit.
"Block-oriented drivers (devb-*)" in the Utilities Summary
"QNX 4 filesystem" in the Working With Filesystems chapter of the User's Guide