bugmonotone - Bugs: bug #8923, All uppercase filenames (i.e. MT)...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #8923: All uppercase filenames (i.e. MT) upsets vfat (fat32) in Linux

Submitted by:  None
Submitted on:  Wed 12 May 2004 11:59:17 PM UTC  
 
Category: working copySeverity: 3 - Normal
Item Group: incorrect behaviorStatus: Works for me
Privacy: PublicAssigned to: None
Open/Closed: Closed
mtn version --full: 

Thu 13 May 2010 12:13:48 AM UTC, comment #2:

vfat now seems to preserve case with no mount options (possibly related to whatever was done about Microsoft's patents?), and when mounted automatically or through pmount I get the 'shortname=mixed' option which makes it case insensitive (but still case-preserving). So this appears to no longer be an issue. Also, these days NTFS works as a shared filesystem for dualboot.

Timothy Brownawell <tbrownaw>
Project Member
Fri 25 Nov 2005 08:43:10 PM UTC, comment #1:

The same or similar issue perhaps seems to bite me using NetBSD's smbfs to manipulate a working dir shared from an NT4 machine (and perhaps other NAS-type fileservers).

Perhaps a config option for the name of the directory? CVS has an option to change this, too; it's commonly changed to .CVS

Daniel Carosone <uep>
Project Member
Wed 12 May 2004 11:59:17 PM UTC, original submission:

Ever since I found out about this issue, Ive been alergic to all uppercase filenames. Of course this affects directories too. It apparently is so that all uppercase files written to a fat32 filesystem via Linux (its vfat driver) is changed into lowercase. All lowercase is not touched, as well as all mixed-case filenames is preserved. So Makefile and README.txt is fine, but README and MT would be changed into readme and mt. This will confuse Monotone when it tries to find MT, since this is where it expects to find the control files. I propose to rename MT into either mt, ".mt", Mt or something similar.

The reason why people will run into this is when they use a shared storage filesystem betweeen a dualboot system. But probably the most obvious reason is to avoid problems when there is no real reason not to. Look for example at Maildir's usage of semicolon in the filename, which also cant be stored on fat32 thus I cant efficiently have my email offline.

I will also mention the workaround to the default behavious of Linux's vfat. Mount with option shortname=winnt. Either -o shortname=winnt to the mount command or put shortname=winnt after "defaults" in fstab.

Anonymous

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by tbrownaw (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 2 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 13 May 2010 12:13:48 AM UTCtbrownawStatusNone=>Works for me
      Open/ClosedOpen=>Closed

    Back to the top


    Powered by Savane 3.1-cleanup1