public inbox for
 help / color / mirror / Atom feed
From: Shaddy Baddah <>
Subject: managed mounts. hindsight sadness at their departure
Date: Fri, 05 Mar 2010 03:59:00 -0000	[thread overview]
Message-ID: <> (raw)


I apologise if this is inappropriate for this list, or even at all, but
I'd like to record a little bit of sadness that managed mounts are no
longer available.

I was in agreement with the rationale behind deprecating them, partly
described in the 1.7 "what's new" section:

- File names are case sensitive if the OS and the underlying file system
   supports it.  Works on NTFS and NFS.  Does not work on FAT and Samba
   shares.  Requires to change a registry key (see the user's guide).
   Can be switched off on a per-mount base.

- Due to the above changes, managed mounts have been removed.

I would add that also the unicode support was reason to no longer
persist with managed mounts.

But now in hindsight, one feature of the managed mounts that I counted
as not significant enough to keep it included, seems to me to have a
kind of valid use case. That is allowing multiple files of the same name
differing only in case.

This feature of the managed mount would have provided a handy workaround
to a minor issue with cloning the Linux kernel through Cygwin. For
whatever reason, the kernel source includes certain duplications of
filenames (that is, if you discount their case). This leads to the
ignorable, but irritating assertion of a git status that files are
modified. This because they have been incorrectly compared with a
different file, of the same name (but for case), that has been checked
out over the original:

shaddy@***-w7 ~/workarea/linux-2.6
$ git status
# On branch wireless-testing
# Changed but not updated:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working 
#       modified:   Documentation/IO-mapping.txt
#       modified:   include/linux/netfilter/xt_CONNMARK.h
#       modified:   include/linux/netfilter/xt_DSCP.h
#       modified:   include/linux/netfilter/xt_MARK.h
#       modified:   include/linux/netfilter/xt_RATEEST.h
#       modified:   include/linux/netfilter/xt_TCPMSS.h
#       modified:   include/linux/netfilter_ipv4/ipt_CONNMARK.h
#       modified:   include/linux/netfilter_ipv4/ipt_DSCP.h
#       modified:   include/linux/netfilter_ipv4/ipt_ECN.h
#       modified:   include/linux/netfilter_ipv4/ipt_MARK.h
#       modified:   include/linux/netfilter_ipv4/ipt_TCPMSS.h
#       modified:   include/linux/netfilter_ipv4/ipt_TOS.h
#       modified:   include/linux/netfilter_ipv4/ipt_TTL.h
#       modified:   include/linux/netfilter_ipv6/ip6t_HL.h
#       modified:   include/linux/netfilter_ipv6/ip6t_MARK.h
#       modified:   net/ipv4/netfilter/ipt_ECN.c
#       modified:   net/ipv4/netfilter/ipt_TTL.c
#       modified:   net/ipv6/netfilter/ip6t_HL.c
#       modified:   net/netfilter/xt_CONNMARK.c
#       modified:   net/netfilter/xt_DSCP.c
#       modified:   net/netfilter/xt_MARK.c
#       modified:   net/netfilter/xt_RATEEST.c
#       modified:   net/netfilter/xt_TCPMSS.c
no changes added to commit (use "git add" and/or "git commit -a")

Not that I'd assert that this is reason enough to have kept the managed
mounts, it is just an unfortunate limitation that 1.7 now has over 1.5.

If I get the time one day to understand why these duplicates exists,
I'll make a patch and suggest it to the Linux kernel project (I've
dipped my toe in there a while back).


             reply	other threads:[~2010-03-05  3:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05  3:59 Shaddy Baddah [this message]
2010-03-05  4:33 ` Eric Blake
2010-03-05  5:02   ` Shaddy Baddah
2010-03-05  9:36     ` Corinna Vinschen
2010-03-08 13:29       ` Shaddy Baddah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).