Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.unix.programmer > #5129 > unrolled thread

Case sensitive file system?

Back to article view | Back to comp.unix.programmer

Contents

  Case sensitive file system? Siri Cruz <chine.bleu@yahoo.com> - 2014-02-15 19:08 -0800
    Re: Case sensitive file system? Ian Collins <ian-news@hotmail.com> - 2014-02-16 16:15 +1300
    Re: Case sensitive file system? Kaz Kylheku <kaz@kylheku.com> - 2014-02-16 03:19 +0000
    Re: Case sensitive file system? Jolly Roger <jollyroger@pobox.com> - 2014-02-16 03:29 +0000
    Re: Case sensitive file system? David Ritz <dritz@mindspring.com> - 2014-02-15 22:28 -0600
    Re: Case sensitive file system? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-16 06:05 +0000
      Re: Case sensitive file system? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-16 09:18 -0500
    Re: Case sensitive file system? Michael Vilain <vilain@NOspamcop.net> - 2014-02-15 23:28 -0800
      Re: Case sensitive file system? Siri Cruz <chine.bleu@yahoo.com> - 2014-02-16 04:24 -0800
      Re: Case sensitive file system? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-16 09:17 -0500
        Re: Case sensitive file system? Ian Zimmerman <itz@buug.org> - 2014-03-01 10:59 -0800
          Re: Case sensitive file system? Jorgen Grahn <grahn+nntp@snipabacken.se> - 2014-03-01 19:46 +0000
          Re: Case sensitive file system? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2014-03-02 07:53 -0700
      Re: Case sensitive file system? Kaz Kylheku <kaz@kylheku.com> - 2014-03-02 18:19 +0000
        Re: Case sensitive file system? Michael Vilain <vilain@NOspamcop.net> - 2014-03-02 12:37 -0800
          Re: Case sensitive file system? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-03-02 20:23 -0500
            Re: Case sensitive file system? scott@slp53.sl.home (Scott Lurndal) - 2014-03-03 15:06 +0000
              Re: Case sensitive file system? Casper H.S. Dik <Casper.Dik@OrSPaMcle.COM> - 2014-03-03 15:10 +0000
                Re: Case sensitive file system? scott@slp53.sl.home (Scott Lurndal) - 2014-03-03 16:59 +0000
              Re: Case sensitive file system? Tim Streater <timstreater@greenbee.net> - 2014-03-03 15:18 +0000

#5129 — Case sensitive file system?

Is there a simple way in a program to see if a file system uses case sensitive 
names (like traditional Unix) or case irrelevant (like plain old HFS+)?

-- 
:-<> Siri Seal of Disavowal #000-001. Disavowed. Denied. Deleted.
'I desire mercy, not sacrifice.'

[toc] | [next] | [standalone]

#5130

Siri Cruz wrote:
> Is there a simple way in a program to see if a file system uses case sensitive
> names (like traditional Unix) or case irrelevant (like plain old HFS+)?

If open "ZZ? fails, create "zz" and try to open "ZZ"?

-- 
Ian Collins

[toc] | [prev] | [next] | [standalone]

#5131

On 2014-02-16, Siri Cruz <chine.bleu@yahoo.com> wrote:
> Is there a simple way in a program to see if a file system uses case sensitive 
> names (like traditional Unix) or case irrelevant (like plain old HFS+)?

Make a temporary directory in that filesystem, and there create a file "fOO" or
some such mixed-case identifier. If you can open it as "foo", the system is
case-insensitive.  Then list the directory. If the name lists as "fOO", then it
is case-preserving. If it appears as "foo" or "FOO", it is case folding.

Is there are nondestructive way to just find out this info? I don't think
so. There is nothing *standard* out of pathconf or fstat.

Mac OS/Darwin evidently has a _PC_CASE_SENSITIVE constant that can be used with
pathconf. You could detect this in a C program with #ifdef to implement the
test more efficiently. It appears there is also a _PC_CASE_PRESERVING.

I'd detect these individually to short-circuit the relevant parts of the logic,
such that if both are provided, then no temporary modification of the
filesystem takes place.

-- 
Music DIY Mailing List: http://www.kylheku.com/diy
ADA MP-1 Mailing List:  http://www.kylheku.com/mp1

[toc] | [prev] | [next] | [standalone]

#5132

On 2014-02-16, Siri Cruz <chine.bleu@yahoo.com> wrote:
>
> Is there a simple way in a program to see if a file system uses case
> sensitive names (like traditional Unix) or case irrelevant (like plain
> old HFS+)?

This command will tell you whether or not the boot device is
case-sensitive:

# diskutil info `df / | sed -e /Filesystem/d | awk '{print $1}'` | grep
"Personality" 

   File System Personality:  Journaled HFS+

If it's case-sensitive, it will say: "Case-sensitive Journaled HFS+".
Otherwise it will just say: "Journaled HFS+".

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#5133

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday, 15 February 2014 19:08 -0800, 
 in article <chine.bleu-1E20C5.19082615022014@news.eternal-september.org>, 
 Siri Cruz <chine.bleu@yahoo.com> wrote:

> Is there a simple way in a program to see if a file system uses case 
> sensitive names (like traditional Unix) or case irrelevant (like 
> plain old HFS+)?

$ diskutil info disk0s2 | grep File
   File System Personality:  Journaled HFS+

- -- 
David Ritz <dritz@mindspring.com>
 Be kind to animals; kiss a shark.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (Darwin)

iEYEARECAAYFAlMAPlsACgkQUrwpmRoS3uu0JACghZzt5EnQPb25R5ilIKGhZEef
8gsAn0Fsc6gEoeeyzBLTEfF/89aRSWNV
=3nqS
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#5134

In message <chine.bleu-1E20C5.19082615022014@news.eternal-september.org> 
  Siri Cruz <chine.bleu@yahoo.com> wrote:
> Is there a simple way in a program to see if a file system uses case sensitive 
> names (like traditional Unix) or case irrelevant (like plain old HFS+)?

touch test; touch TEST; ls -1rt

two files = case sensitive.

You can also look in Disk Utility.

-- 
Dinner will be ready when the smoke alarm goes off.

[toc] | [prev] | [next] | [standalone]

#5138

On 2014.02.16, 01:05 , Lewis wrote:
> In message <chine.bleu-1E20C5.19082615022014@news.eternal-september.org>
>    Siri Cruz <chine.bleu@yahoo.com> wrote:
>> Is there a simple way in a program to see if a file system uses case sensitive
>> names (like traditional Unix) or case irrelevant (like plain old HFS+)?
>
> touch test; touch TEST; ls -1rt
>
> two files = case sensitive.
>
> You can also look in Disk Utility.

My first reaction was to open Disk Utility which shows (under the 'info' 
button) "Mac OS Extended (Journaled, Encrypted)" and I'm not sure at all 
that is indicative of case insensitivity.  Is it?

-- 
   Privacy has become an essential personal chore that most
   people are not trained to perform.
                  - Jaron Lanier, Scientific American, 2013.11.

[toc] | [prev] | [next] | [standalone]

#5135

In article 
<chine.bleu-1E20C5.19082615022014@news.eternal-september.org>,
 Siri Cruz <chine.bleu@yahoo.com> wrote:

> Is there a simple way in a program to see if a file system uses case 
> sensitive 
> names (like traditional Unix) or case irrelevant (like plain old HFS+)?

I've recently discovered this thing on the web. It's called Google and 
it's replaced my CRC Handbook, my Sun Tech manuals, and my old DEC 
manuals.  I asked this question at the Google prompt and this came back.

http://apple.stackexchange.com/questions/71357/how-to-check-if-my-hd-is-c
ase-sensitive-or-not

-- 
DeeDee, don't press that button!  DeeDee!  NO!  Dee...
[I filter all Goggle Groups posts, so any reply may be automatically ignored]

[toc] | [prev] | [next] | [standalone]

#5136

In article <vilain-A30470.23285415022014@news.individual.net>,
 Michael Vilain <vilain@NOspamcop.net> wrote:

> I've recently discovered this thing on the web. It's called Google and 

Odd but since Google doesn't actually have a human interpretting the query, all 
it takes is slightly off query and it's useless, no matter how many hours you 
spend on it.

I remember once spending a day trying to find out how to record screen audio 
with screen video, only reading I would need a mic out to sound in 
amplifier/cable. Tried again and now there's a software bit to do that.

-- 
:-<> Siri Seal of Disavowal #000-001. Disavowed. Denied. Deleted.
'I desire mercy, not sacrifice.'

[toc] | [prev] | [next] | [standalone]

#5137

On 2014.02.16, 02:28 , Michael Vilain wrote:
> In article
> <chine.bleu-1E20C5.19082615022014@news.eternal-september.org>,
>   Siri Cruz <chine.bleu@yahoo.com> wrote:
>
>> Is there a simple way in a program to see if a file system uses case
>> sensitive
>> names (like traditional Unix) or case irrelevant (like plain old HFS+)?
>
> I've recently discovered this thing on the web. It's called Google

Snide reply aside I'm glad when these questions come along and there is 
a spectrum of replies on how to find the answers.  Sometimes I learn 
something.  And interesting that it's split between "probers" (find the 
info from the system) and "testers" (contrive a test that shows 
behaviour and thus settings).

Indeed my first reaction was to open Disk Utility which shows (under the 
'info' button) "Mac OS Extended (Journaled, Encrypted)" and I'm not sure 
at all that is indicative of case insensitivity (I'll refer to Lewis in 
his reply).

As to brevity I guess Lewis' method seems best.

-- 
   Those who have reduced our privacy, whether they are state
   or commercial actors, prefer that we do not reduce theirs.
                  - Jaron Lanier, Scientific American, 2013.11.

[toc] | [prev] | [next] | [standalone]

#5144

Siri Cruz <chine.bleu@yahoo.com> wrote:

Siri> Is there a simple way in a program to see if a file system uses
                            ^^^^^^^^^^^^
Siri> case sensitive (like traditional Unix) or case irrelevant

Lewis> touch test; touch TEST; ls -1rt

Lewis> two files = case sensitive.

Lewis> You can also look in Disk Utility.

Alan> As to brevity I guess Lewis' method seems best.

Too bad it doesn't actually answer the question (see above).

-- 
Please *no* private copies of mailing list or newsgroup messages.

gpg public key: 2048R/984A8AE4
fingerprint: 7953 ADA1 0E8E AB57 FB79  FFD2 360A 88B2 984A 8AE4
Funny pic: http://bit.ly/ZNE2MX

[toc] | [prev] | [next] | [standalone]

#5145

On Sat, 2014-03-01, Ian Zimmerman wrote:
> Siri Cruz <chine.bleu@yahoo.com> wrote:
>
> Siri> Is there a simple way in a program to see if a file system uses
>                             ^^^^^^^^^^^^
> Siri> case sensitive (like traditional Unix) or case irrelevant
>
> Lewis> touch test; touch TEST; ls -1rt
>
> Lewis> two files = case sensitive.
>
> Lewis> You can also look in Disk Utility.
>
> Alan> As to brevity I guess Lewis' method seems best.
>
> Too bad it doesn't actually answer the question (see above).

It does: it outlines most of one such program.  (Although modifying
the file system to find out things about it isn't very attractive.)

Slightly better version:

  touch test TEST && [ test -ef TEST ] && echo "weird fs"

/Jorgen

-- 
  // Jorgen Grahn <grahn@  Oo  o.   .     .
\X/     snipabacken.se>   O  o   .

[toc] | [prev] | [next] | [standalone]

#5149

Ian Zimmerman <itz@buug.org> writes:

> Siri Cruz <chine.bleu@yahoo.com> wrote:
>
> Siri> Is there a simple way in a program to see if a file system uses
>                             ^^^^^^^^^^^^
> Siri> case sensitive (like traditional Unix) or case irrelevant
>
> Lewis> touch test; touch TEST; ls -1rt
>
> Lewis> two files = case sensitive.
>
> Lewis> You can also look in Disk Utility.
>
> Alan> As to brevity I guess Lewis' method seems best.
>
> Too bad it doesn't actually answer the question (see above).

Without knowing what language he's writing in, it's hard to give the
exact code.  That answer does outline how to do it; it happens to be
written as a line of shell code, but the approach is the same in any
language you care to use.

[toc] | [prev] | [next] | [standalone]

#5154

On 2014-02-16, Michael Vilain <vilain@NOspamcop.net> wrote:
> In article 
><chine.bleu-1E20C5.19082615022014@news.eternal-september.org>,
>  Siri Cruz <chine.bleu@yahoo.com> wrote:
>
>> Is there a simple way in a program to see if a file system uses case 
>> sensitive 
>> names (like traditional Unix) or case irrelevant (like plain old HFS+)?
>
> I've recently discovered this thing on the web. It's called Google and 
> it's replaced my CRC Handbook, my Sun Tech manuals, and my old DEC 
> manuals.  I asked this question at the Google prompt and this came back.

You and Siri Cruz are not so different, you know, haha:

Siri Cruz:
  User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)

Michael Vilain:
  User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)

Someone who uses an actual newsreader and connects to an actual NNTP server
probably doesn't benefit from "learn how to use a search engine" type advice.

[toc] | [prev] | [next] | [standalone]

#5159

In article <20140302101428.693@kylheku.com>,
 Kaz Kylheku <kaz@kylheku.com> wrote:

> On 2014-02-16, Michael Vilain <vilain@NOspamcop.net> wrote:
> > In article 
> ><chine.bleu-1E20C5.19082615022014@news.eternal-september.org>,
> >  Siri Cruz <chine.bleu@yahoo.com> wrote:
> >
> >> Is there a simple way in a program to see if a file system uses case 
> >> sensitive 
> >> names (like traditional Unix) or case irrelevant (like plain old HFS+)?
> >
> > I've recently discovered this thing on the web. It's called Google and 
> > it's replaced my CRC Handbook, my Sun Tech manuals, and my old DEC 
> > manuals.  I asked this question at the Google prompt and this came back.
> 
> You and Siri Cruz are not so different, you know, haha:
> 
> Siri Cruz:
>   User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)
> 
> Michael Vilain:
>   User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)
> 
> Someone who uses an actual newsreader and connects to an actual NNTP server
> probably doesn't benefit from "learn how to use a search engine" type advice.

au contraire.  Google has replaced most of my bookshelf of O'Reilly 
books.  While I'm sure it wouldn't have replaced the gray wall of DEC 
manuals, it does answer all the "how do I" questions I've asked it about 
Linux.  And now that I've asked it MacOS questions, it's come up with 
some answers. But it misses more times than on Linux.

-- 
DeeDee, don't press that button!  DeeDee!  NO!  Dee...
[I filter all Goggle Groups posts, so any reply may be automatically ignored]

[toc] | [prev] | [next] | [standalone]

#5160

On 14-03-02 15:37, Michael Vilain wrote:

> au contraire.  Google has replaced most of my bookshelf of O'Reilly 
> books.  While I'm sure it wouldn't have replaced the gray wall of DEC 
> manuals

The Grey Wall was replaced at 5.5-2 in early 1990s. First to CDs and
currently available somewhere on the HP web site where it is preserved
(hopefully) for the no-longer-developped VMS OS.

[toc] | [prev] | [next] | [standalone]

#5165

JF Mezei <jfmezei.spamnot@vaxination.ca> writes:
>On 14-03-02 15:37, Michael Vilain wrote:
>
>> au contraire.  Google has replaced most of my bookshelf of O'Reilly 
>> books.  While I'm sure it wouldn't have replaced the gray wall of DEC 
>> manuals
>
>The Grey Wall was replaced at 5.5-2 in early 1990s. First to CDs and
>currently available somewhere on the HP web site where it is preserved
>(hopefully) for the no-longer-developped VMS OS.
>

I recall it as a Blue wall, then an Orange wall.  Grey must have followed
orange.

[toc] | [prev] | [next] | [standalone]

#5166

scott@slp53.sl.home (Scott Lurndal) writes:

>JF Mezei <jfmezei.spamnot@vaxination.ca> writes:
>>On 14-03-02 15:37, Michael Vilain wrote:
>>
>>> au contraire.  Google has replaced most of my bookshelf of O'Reilly 
>>> books.  While I'm sure it wouldn't have replaced the gray wall of DEC 
>>> manuals
>>
>>The Grey Wall was replaced at 5.5-2 in early 1990s. First to CDs and
>>currently available somewhere on the HP web site where it is preserved
>>(hopefully) for the no-longer-developped VMS OS.
>>

>I recall it as a Blue wall, then an Orange wall.  Grey must have followed
>orange.

I remember "Orange"  Around 1986 or some such?

Casper

[toc] | [prev] | [next] | [standalone]

#5168

Casper H.S. Dik <Casper.Dik@OrSPaMcle.COM> writes:
>scott@slp53.sl.home (Scott Lurndal) writes:
>
>>JF Mezei <jfmezei.spamnot@vaxination.ca> writes:
>>>On 14-03-02 15:37, Michael Vilain wrote:
>>>
>>>> au contraire.  Google has replaced most of my bookshelf of O'Reilly 
>>>> books.  While I'm sure it wouldn't have replaced the gray wall of DEC 
>>>> manuals
>>>
>>>The Grey Wall was replaced at 5.5-2 in early 1990s. First to CDs and
>>>currently available somewhere on the HP web site where it is preserved
>>>(hopefully) for the no-longer-developped VMS OS.
>>>
>
>>I recall it as a Blue wall, then an Orange wall.  Grey must have followed
>>orange.
>
>I remember "Orange"  Around 1986 or some such?

My Blue ones are from 1979-1983.  Orange started 83 or 84, IIRC.

scott

[toc] | [prev] | [next] | [standalone]

#5167

In article <VT0Ru.28054$A94.17200@fx18.iad>, Scott Lurndal
<scott@slp53.sl.home> wrote:

> JF Mezei <jfmezei.spamnot@vaxination.ca> writes:
> >On 14-03-02 15:37, Michael Vilain wrote:
> >
> >> au contraire.  Google has replaced most of my bookshelf of O'Reilly 
> >> books.  While I'm sure it wouldn't have replaced the gray wall of DEC 
> >> manuals
> >
> >The Grey Wall was replaced at 5.5-2 in early 1990s. First to CDs and
> >currently available somewhere on the HP web site where it is preserved
> >(hopefully) for the no-longer-developped VMS OS.
> 
> I recall it as a Blue wall, then an Orange wall.  Grey must have followed
> orange.

And when the gray wall came out my colleague took the orange wall home
with him.

-- 
Tim

"That excessive bail ought not to be required, nor excessive fines imposed,
nor cruel and unusual punishments inflicted"  --  Bill of Rights 1689

[toc] | [prev] | [standalone]

Back to top | Article view | comp.unix.programmer

csiph-web