Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Jolly Roger <jollyroger@pobox.com>
Newsgroups: comp.sys.mac.apps
Subject: Re: DivX and CaSeSeNsItIvE filesystems ?
Date: 7 Feb 2014 16:50:38 GMT
Organization: People for the Ethical Treatment of Pirates
Lines: 50
Message-ID: <blkh6uF5t73U2@mid.individual.net>
References: <52f2ab1e$0$302$14726298@news.sunsite.dk> <blfptpF6ctvU1@mid.individual.net> <slrnlf5ga5.24vg.g.kreme@amelia.local> <blfue3F7atjU1@mid.individual.net> <slrnlf746p.273m.g.kreme@amelia.local> <barmar-6D922D.11245706022014@news.eternal-september.org> <slrnlf8o5f.273m.g.kreme@amelia.local>
X-Trace: individual.net f3MTSPpxiWTr5FedWEhszAuf92XGyA4LEBTd8ce/v5sYtertrX
Cancel-Lock: sha1:K1ndTlFwbmtMNtII/Qe4GVP4QRM=
X-Face: _.g>n!a$f3/H3jA]>9pN55*5<`}Tud57>1<n@LQ!aZ7vLO_nWbK~@T'XIS0,oAJcU.qLM dk/j8Udo?O"o9B9Jyx+ez2:B<nx(k3EdHnTvB]'eoVaR495,Rv~/vPa[e^JI+^h5Zk*i`Q;ezqDW< ZFs6kmAJWZjOH\8[$$7jm,Ogw3C_%QM'|H6nygNGhhl+@}n30Nz(^vWo@h>Y%b|b-Y~()~\t,LZ3e up1/bO{=-)
User-Agent: slrn/1.0.1 (Darwin)
Xref: csiph.com comp.sys.mac.apps:20992

On 2014-02-07, Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:
> In message <barmar-6D922D.11245706022014@news.eternal-september.org> 
>   Barry Margolin <barmar@alum.mit.edu> wrote:
>> In article <slrnlf746p.273m.g.kreme@amelia.local>,
>>  Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:
>
>>> In message <blfue3F7atjU1@mid.individual.net> 
>>>   Jolly Roger <jollyroger@pobox.com> wrote:
>>> > On 2014-02-05, Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:
>>> >> In message <blfptpF6ctvU1@mid.individual.net> 
>>> >>   Jolly Roger <jollyroger@pobox.com> wrote:
>>> >>> On 2014-02-05, Niels S. Eliasen <nse@delfi-konsult.com> wrote:
>>> >>>>
>>> >>>> Hello
>>> >>>> Anyone that knows how to fix the problems with DivX 
>>> >>>> and casesensitive file systems ?
>>> >>>>
>>> >>>> Apart from getting DiX to fix this..... 
>>> >>
>>> >>> Why bother with a case sensitive file system to begin with?
>>> >>
>>> >> Well, there's HEAD and head, for one.
>>> 
>>> > What's your point?
>>> 
>>> They're different, which is an issue on case-preserving filesystems. A
>>> small issue, to be sure, but still an issue.
>
>> But why would you need to use both filenames in the same directory? 
>> That's the only benefit you gain from having a case-sensitive file 
>> system.
>
> HEAD and head are UNIX commands. Different UNIX commands. It can be am
> issue when compiling source code on a case-preserving system like OS X
> when the code is expecting a case sensitive system to distinguish HEAD
> from head.

You're referring to the Perl LWP module "HEAD" utility, I take it. That
"HEAD" and the BSD "head" utility are *not* in the same directory. So
the utterly simple fix for this minor problem is to specify the full
path to the utility, which is a best practice anyway. Problem easily
solved with a best practice. Again, you will encounter many more issues
(some far more serious and hard to fix) running case-sensitive file
systems.

-- 
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