src/sys/modules/msdosfs, branch releng/5.3

By popular request, add a workaround that allows large (>128GB or so)

2004-07-03T13:22:38Z

FAT32 filesystems to be mounted, subject to some fairly serious limitations. This works by extending the internal pseudo-inode-numbers generated from the file's starting cluster number to 64-bits, then creating a table mapping these into arbitrary 32-bit inode numbers, which can fit in struct dirent's d_fileno and struct vattr's va_fileid fields. The mappings do not persist across unmounts or reboots, so it's not possible to export these filesystems through NFS. The mapping table may grow to be rather large, and may grow large enough to exhaust kernel memory on filesystems with millions of files. Don't enable this option unless you understand the consequences.

- Support for multibyte charsets in LIBICONV.

2003-09-26T20:26:25Z

- CD9660_ICONV, NTFS_ICONV and MSDOSFS_ICONV kernel options (with corresponding modules). - kiconv(3) for loadable charset conversion tables support. Submitted by: Ryuichiro Imura

Move adding -DPC98 to CFLAGS from each modules to sys/modules/Makefile.inc.

2002-11-06T13:47:00Z

Drop support from .

2002-01-11T15:49:02Z

Not objected to by: -current

- VFS_SET(msdos) -> VFS_SET(msdosfs)

2001-06-01T10:57:26Z

- msdos.ko -> msdosfs.ko - mount_msdos(8) -> mount_msdosfs(8) - "msdos" -> "msdosfs" compatibility glue in mount(8)

Name this module msdos.ko so that mount_msdos(8) can autoload

2001-05-28T17:10:46Z

it with vfsload("msdos"). (The proper fix would be to rename the `msdos' file system to `msdosfs' in VFS_SET(), and mount_msdos(8) to mount_msdosfs(8). But that would break too many existing fstab(5) setups, and would require a lot of unnecessary documentation and code msdos -> msdosfs changes.) Noticed by: markm

- sys/msdosfs moved to sys/fs/msdosfs

2001-05-25T08:14:14Z

- msdos.ko renamed to msdosfs.ko - /usr/include/msdosfs moved to /usr/include/fs/msdosfs

Use a consistent style and one much closer to the rest of /usr/src

2001-01-06T14:00:42Z

Use .include to get to ../../*/conf/kmod.mk instead of

2000-05-27T01:14:33Z

encoding the relative path.

Pull in sys/conf/kmod.mk, rather than /usr/share/mk/bsd.kmod.mk.

2000-05-04T12:08:52Z

This means that the kernel can be totally self contained now and is not dependent on the last buildworld to update /usr/share/mk. This might also make it easier to build 5.x kernels on 4.0 boxes etc, assuming gensetdefs and config(8) are updated.