Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Message from discussion Almost duplicate filenames [Case (in)sensitivity problems]
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Ron Shepard  
View profile  
 More options Jan 7 2006, 12:28 pm
Newsgroups: comp.sys.mac.misc
From: Ron Shepard <ron-shep...@NOSPAM.comcast.net>
Date: Sat, 07 Jan 2006 11:28:17 -0600
Local: Sat, Jan 7 2006 12:28 pm
Subject: Re: Almost duplicate filenames [Case (in)sensitivity problems]
In article <stevewjackson-717D8B.15525806012...@individual.net>,
 "Steve W. Jackson" <stevewjack...@charter.net> wrote:

> I'm not sure where you got the idea that 10.4 is case-sensitive.  It's
> not the OS behind this at all, but the filesystem.

Yes, 10.4, 10.3, 10.2 and probably earlier versions (I don't
remember) are all the same, they all support case-sensitive file
systems.  There is a ufs filesystem that you can install on your
local disks with disk utility, and there is support, through nfs for
example, for remote case-sensitive file systems.

The new thing that was added with 10.4 is support for a case
sensitive version of HFS+.

The OP's problem is that he is moving a group of files from a case
sensitive filesystem to a case insensitive filesystem, HFS+.  This
is the same problem that many of us have had for the past five years
in moving files from other unix machines to MacOSX.  One solution is
to rename the offending files.

Another approach is to create a ufs disk image on the HFS+ file
system.  This will be a case sensitive filesystem even though it is
sitting on a HFS+ disk.  No actual disk reformatting is necessary.  
You mount the disk image by double clicking it.  If it is just a
matter of temporary storage, this may be the simplest approach.  If
it is a filesystem that will see heavy use and where performance
will be important, then maybe this isn't the best solution.  Also,
there are some Mac applications that do not handle correctly the
case sensitivity (which is why Apple recommends against using HFS+cs
as the startup disk), although in the OP's case this should not an
issue since he is coming from MacOSX in the first place.

$.02 -Ron Shepard


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.