| Alexey Dobriyan | a276a52 | 2009-01-22 11:05:02 +0300 | [diff] [blame] | 1 | config UFS_FS |
| 2 | tristate "UFS file system support (read only)" |
| 3 | depends on BLOCK |
| 4 | help |
| 5 | BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD, |
| 6 | OpenBSD and NeXTstep) use a file system called UFS. Some System V |
| 7 | Unixes can create and mount hard disk partitions and diskettes using |
| 8 | this file system as well. Saying Y here will allow you to read from |
| 9 | these partitions; if you also want to write to them, say Y to the |
| 10 | experimental "UFS file system write support", below. Please read the |
| 11 | file <file:Documentation/filesystems/ufs.txt> for more information. |
| 12 | |
| 13 | The recently released UFS2 variant (used in FreeBSD 5.x) is |
| 14 | READ-ONLY supported. |
| 15 | |
| 16 | Note that this option is generally not needed for floppies, since a |
| 17 | good portable way to transport files and directories between unixes |
| 18 | (and even other operating systems) is given by the tar program ("man |
| 19 | tar" or preferably "info tar"). |
| 20 | |
| 21 | When accessing NeXTstep files, you may need to convert them from the |
| 22 | NeXT character set to the Latin1 character set; use the program |
| 23 | recode ("info recode") for this purpose. |
| 24 | |
| 25 | To compile the UFS file system support as a module, choose M here: the |
| 26 | module will be called ufs. |
| 27 | |
| 28 | If you haven't heard about all of this before, it's safe to say N. |
| 29 | |
| 30 | config UFS_FS_WRITE |
| 31 | bool "UFS file system write support (DANGEROUS)" |
| 32 | depends on UFS_FS && EXPERIMENTAL |
| 33 | help |
| 34 | Say Y here if you want to try writing to UFS partitions. This is |
| 35 | experimental, so you should back up your UFS partitions beforehand. |
| 36 | |
| 37 | config UFS_DEBUG |
| 38 | bool "UFS debugging" |
| 39 | depends on UFS_FS |
| 40 | help |
| 41 | If you are experiencing any problems with the UFS filesystem, say |
| 42 | Y here. This will result in _many_ additional debugging messages to be |
| 43 | written to the system log. |