Page MenuHomeFreeBSD

Mount msdosfs with longnames support by default.
ClosedPublic

Authored by asomers on Sep 23 2016, 4:55 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Nov 21, 5:19 AM
Unknown Object (File)
Sat, Nov 16, 2:25 PM
Unknown Object (File)
Sat, Nov 16, 11:02 AM
Unknown Object (File)
Mon, Nov 11, 10:08 AM
Unknown Object (File)
Sun, Oct 27, 5:53 AM
Unknown Object (File)
Oct 2 2024, 12:22 PM
Unknown Object (File)
Oct 1 2024, 8:12 PM
Unknown Object (File)
Oct 1 2024, 7:40 PM
Subscribers

Details

Summary

Mount msdosfs with longnames support by default.

The old behavior depended on the FAT version and on what files were in the
root directory. "mount_msdosfs -o shortnames" is still supported.

Test Plan

Create short and long filenames in a subdirectory on FAT12, 16, and 32
filesystems. Mount them with and without -o shortnames and verify that all
filenames are displayed correctly.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

asomers retitled this revision from to Mount msdosfs with longnames support by default..
asomers updated this object.
asomers edited the test plan for this revision. (Show Details)
asomers added reviewers: imp, trasz, adrian.
asomers edited edge metadata.

Add sys/sys/param.h to the review

cem added a reviewer: cem.
cem added a subscriber: cem.

There's no reason not to support Win95 long file names ("LFN") by default. Long names are purely backwards compatible with shortname-only filesystems.

Pre-win95 Microsoft systems w/out LFN support can even mount and browse filesystems with LFN entries, due to the fallback 8.3 encoding. If they mount r/w and modify directories, they might destroy the LFN names, but I do not think this is our problem.

This revision is now accepted and ready to land.Sep 23 2016, 5:51 PM
wblock added a reviewer: wblock.
This revision was automatically updated to reflect the committed changes.