[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87iqkj61u7.fsf@devron.myhome.or.jp>
Date: Sat, 02 May 2009 23:01:20 +0900
From: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To: tridge@...ba.org
Cc: Dave Kleikamp <shaggy@...ux.vnet.ibm.com>,
Steve French <sfrench@...ibm.com>,
Mingming Cao <cmm@...ibm.com>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
LKML <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option
tridge@...ba.org writes:
> > Current default (shortname=lower) is just for historically reason.
> > Personally, I'm thinking it's not good as default ("winnt" or "mixed" is
> > prefer).
>
> It might make sense to make the default depend on the fs type. For
> example, make FAT32 use "winnt" and FAT12/16 use "mixed". That would
> give maximum interoperability I think.
>
> I'm presuming that the versions of win95 that supported FAT32 also
> supported the mixed case bits, though I haven't tested that.
"mixed" means created like win95, but support to read winnt field. So,
it is compatible to win95. And even if user is using winnt option, the
file created can be readed on win95, win95 will ignore the lcase field,
and just display filename as upper case though.
I.e. created filename by any options can read on any plathome, it may
ignore the lcase field though. And, even if user is using "winnt", many
plathome wouldn't be supporting it.
Well, I think changing default by fstype is confusable.
--
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
--
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