[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090628220518.GB29896@shareable.org>
Date: Sun, 28 Jun 2009 23:05:18 +0100
From: Jamie Lokier <jamie@...reable.org>
To: Jan Engelhardt <jengelh@...ozas.de>
Cc: tridge@...ba.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
john.lanza@...ux.com, linux-fsdevel@...r.kernel.org,
Dave Kleikamp <shaggy@...ux.vnet.ibm.com>,
Steve French <sfrench@...ibm.com>,
Mingming Cao <cmm@...ibm.com>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>
Subject: Re: [PATCH] Added CONFIG_VFAT_FS_DUALNAMES option
Jan Engelhardt wrote:
>
> On Sunday 2009-06-28 23:57, Jamie Lokier wrote:
> >For those of us who don't want to omit the code, because we like
> >compatibility and we're not in affected countries, or for research, it
> >would be useful to have it as a mount option.
> >
> >So there should be these compile-time options:
> > 2. CONFIG_VFAT_FS_DUALNAMES enabled: Create shortnames, unless
> > mount option "dualnames=no" is given, in which case that mount
> > behaves as if CONFIG_VFAT_FS_DUALNAMES is disabled.
>
> If you are not in an affected country, why would you even want
> to disable dualnames? [ on a per-mount basis...]
1. To test it's behaviour, without changing the whole running system.
2. To produce disk images which are the same as would be produced
in an affected country, or would be produced by a Linux distro
adopting the behaviour.
-- Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists