answer N.
CONFIG_QNX4FS_FS
- This is the file system used by the operating system QNX 4. Say Y if
- you intend to mount QNX hard disks or floppies. Unless you say Y to
- "QNX4FS read-write support" below, you will only be able to read
- these file systems.
+ This is the file system used by the real-time operating systems
+ QNX 4 and QNX 6 (the latter is also called QNX RTP).
+ Further information is available at <http://www.qnx.com/>.
+ Say Y if you intend to mount QNX hard disks or floppies.
+ Unless you say Y to "QNX4FS read-write support" below, you will
+ only be able to read these file systems.
This file system support is also available as a module ( = code
which can be inserted in and removed from the running kernel
CONFIG_QNX4FS_RW
Say Y if you want to test write support for QNX4 file systems.
+ It's currently broken, so for now:
+ answer N.
+
CONFIG_AUTOFS_FS
The automounter is a tool to automatically mount remote file systems
on demand. This implementation is partially kernel-based to reduce
# breaks.
dep_bool '/dev/pts file system for Unix98 PTYs' CONFIG_DEVPTS_FS $CONFIG_UNIX98_PTYS
-dep_tristate 'QNX4 file system support (read only) (EXPERIMENTAL)' CONFIG_QNX4FS_FS $CONFIG_EXPERIMENTAL
+tristate 'QNX4 file system support (read only)' CONFIG_QNX4FS_FS
dep_mbool ' QNX4FS write support (DANGEROUS)' CONFIG_QNX4FS_RW $CONFIG_QNX4FS_FS $CONFIG_EXPERIMENTAL
tristate 'ROM file system support' CONFIG_ROMFS_FS
+++ /dev/null
-Last update: 1999-12-23
-
-- Fragmented files and directories were incorrectly handled.
- Fixed 1999-12-23, Anders.
-
-- readdir sometimes returned the same dir entry more than once.
- Fixed 1999-12-13, Anders.
-
-- File names with a length of exactly 16 chars were handled incorrectly.
- Fixed 1999-12-11, Anders.
-
-- Files in a subdir can't be accessed, I think that the inode information
- is not correctly copied at some point. Solved 06-06-1998, Richard.
-
-- At some point the mounted device can't be unmounted. I think that somewhere
- in the code a buffer is not given free.
-
-- Make the '..' entry work, I give it a great chance that the above bug
- (not given free) has something to do with this one, after a 'ls -l'
- the mounted device can't be unmounted and that's where the '..' entry
- is accessed.
- Seems to be solved 21-06-1998, Frank.
-
-- File read function not correct, after the first block it goes beserk.
- Solved 21-06-1998, Frank.
-
-- This fs will not work if not built as a module.
- Solved 25-06-1998, Frank.
-
-- Write/truncate/delete functions don't update the bitmap.
+++ /dev/null
-Name : QNX4 TODO list
-Last update: 1999-12-23
-
- - Writing is still unsupported (it may compile, but it certainly won't
- bring you any joy).
-
- - qnx4_checkroot (inode.c), currently there's a look for the '/' in
- the root direntry, if so then the current mounted device is a qnx4
- partition. This has to be rewritten with a look for 'QNX4' in the
- bootblock, it seems to me the savest way to ensure that the mounted
- device is in fact a QNX4 partition.
- Done 20-06-1998, Frank. But some disks (like QNX install floppies)
- don't have 'QNX4' in their bootblock.
-
- - Bitmap functions. To find out the free space, largest free block, etc.
- Partly done (RO), Richard, 05/06/1998. Optimized 20-06-1998, Frank.
-
- - Complete write, unlink and truncate functions : the bitmap should be
-updated.
-
- - Porting to linux 2.1.99+ with dcache support. 20-06-1998, Frank.
-
- - Don't rewrite the file_read function : use the generic_file_read hook,
- and write readpage instead. Done on 21-06-1998, Frank.
-
- - Write dinit and dcheck.
-
- - Solving the bugs.
-
- - Use le32_to_cpu and vice-versa for portability.
projects / linux / commitdiff