From: "Vyacheslav Dubeyko" <slava@dubeyko.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, xfs@oss.sgi.com
Subject: Re: detecting case-insensitivity
Date: Mon, 9 Apr 2012 09:01:11 +0400 [thread overview]
Message-ID: <LBVkglc6jtb7.r3bLKBnl@host202.hostmonster.com> (raw)
Initial message
> Subject: Re: detecting case-insensitivity
> From: Dave Chinner <david@fromorbit.com>
> Date: 09.04.2012 03.30
>
> On Sat, Apr 07, 2012 at 10:00:29AM -0400, J. Bruce Fields wrote:
> > Is there a generic way to detect whether a given filesystem is
> > case-insensitive? If not, how should it be done? (A bit in s_flags?)
>
> I don't think there is a generic flag for it. We could trivially add
> one, I think, as it is generally a fixed property for the entire
> filesystem....
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
But why does it need to detect that filesystem case-insensitive or not? In what use-case does it need to make such detection?
With the best regards,
Vyacheslav Dubeyko.
slava@dubeyko.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-04-09 4:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 5:01 Vyacheslav Dubeyko [this message]
2012-04-09 21:28 ` detecting case-insensitivity J. Bruce Fields
2012-04-09 22:19 ` Dave Chinner
2012-04-09 22:27 ` J. Bruce Fields
2012-04-09 22:44 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2012-04-07 14:00 J. Bruce Fields
2012-04-08 23:02 ` Dave Chinner
2012-04-11 20:03 ` Christoph Hellwig
2012-04-11 20:37 ` J. Bruce Fields
2012-04-30 21:26 ` J. Bruce Fields
2012-04-30 23:01 ` Dave Chinner
2012-05-03 20:22 ` J. Bruce Fields
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=LBVkglc6jtb7.r3bLKBnl@host202.hostmonster.com \
--to=slava@dubeyko.com \
--cc=bfields@fieldses.org \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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