Coming from a Mac OSX environment, I have directory/folder names with the first character of each word
in upper-case, as well as their content, i.e., artists/songs. This is how things were copied to DVD. However,
when I copied everything off DVD to my Linux disk, everything was changed to lower-case, which is really
irritating. WHY DOES LINUX DO THIS?
I’m running openSUSE 11.4 32-bit.
Hi
Because it’s the default… you can turn it off by using the map=off
option when mounting (see man mount).
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop
up 7 days 4:47, 3 users, load average: 0.38, 0.21, 0.22
GPU GeForce 8600 GTS Silent - Driver Version: 280.13
I should also add that most people do not experience case conversion because their Linux CDs have Rock Ridge extension enabled which allows the original filename to be seen. It’s not clear how the OP made his DVD, perhaps with a mastering program that didn’t put RR extension on the DVD or perhaps using HFS extensions instead.
malcolmlewis wrote:
> Hi
> Because it’s the default
Why is it default to alter files when copying from one media to another?
I’m sure there is a reason but it seems very strange to me.
Chris Maaskant
Actually it’s a bit more subtle than that. Here’s what the man 8 mount says about iso9660 options:
map={n[ormal]|o[ff]|a[corn]}
For non-Rock Ridge volumes, normal name translation maps upper to lower case ASCII,
drops a trailing;1', and converts;’ to `.’. With map=off no name translation is
done. See norock. (Default: map=normal.)
So if the OP’s DVD has no RR extensions, map=off might not be much better, instead of getting
myfavouritesong.mp3
he might get
MYFAVOURITESONG.MP3;1
In other words the mixed case information might have been lost if he didn’t burn with RR or HFS extensions enabled.
mount -o man=o /dev/cdrom
mount: only root can do that
sudo mount -o man=o /dev/cdrom
mount: wrong fs type, bad option, bad superblock on /dev/sr0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
After the above, the contents of the cdrom were still all lower-case.
When I first got on Linux, I added the following line to /ect/fstab so I could mount the drive:
/dev/cdrom /media/cdrom iso9660 ro,user,noauto,unhide 0 0
Any further suggestions?
Oh, BTW, on Mac OSX (which is NFS extended) I just inserted a blank DVD in the drive
and dragged and dropped on it what I wanted copied, and then clicked BURN.
I should have said HFS+ extended. I’m not an expert on Mac OSX, nor Linux, for that matter.
maps **upper to lower **case ASCII
converts
MYFAVOURITESONG.MP3;1
to
myfavouritesong.mp3
not vice-versa
I just noticed I typed man instead of map in the above line.
I just redid it using map this time and I got no error. However,
the contents of the cdrom were still all lower-case.
Yes but when you turn mapping off (it’s on by default), you get the original name which is MYFAVOURITESONG.MP3;1
Malcom wrote ‘map=off’
on Mac OSX (which is NFS extended) I just inserted a blank DVD in the drive
Blank media does not have a filesystem. By default openSuSE KDE offers a choice of creating an audio or data disc when it “sees” a new blank CD/DVD. I could change the default for a blank DVD insertion to automatically open it with a media burner, but I would rather have a choice.
Hmm, looks like even with map=off and norock, upper to lower translation is done.
Suggest you run isoinfo to display the metadata of the DVD:
isoinfo -i /dev/cdrom -d
should get you something like this:
CD-ROM is in ISO 9660 format
System id: LINUX
Volume id: CDROM
Volume set id:
Publisher id:
Data preparer id: 2007-08-05 10:40 UTC
Application id: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING
Copyright File id:
Abstract File id:
Bibliographic File id:
Volume set size is: 1
Volume set sequence number is: 1
Logical block size is: 2048
Volume size is: 313433
Joliet with UCS level 3 found
Rock Ridge signatures version 1 found
isoinfo -i /dev/cdrom -d
CD-ROM is in ISO 9660 format
System id: APPLE COMPUTER, INC., TYPE: 0002
Volume id: MUSIC1OF626AUG11
Volume set id:
Publisher id:
Data preparer id:
Application id:
Copyright File id:
Abstract File id:
Bibliographic File id:
Volume set size is: 1
Volume set sequence number is: 1
Logical block size is: 2048
Volume size is: 1999822
Joliet with UCS level 1 found
Rock Ridge signatures version 1 found
Hmm, you do have RR extensions, so you should have the original names in the RR record. Sorry, too strange for me. What do you see when you mount the DVD on another OS, say Windows? That would use the Joliet extension.
BTW, you do know that Apple filesystems are by default case-insensitive, although case-preserving? That is to say, you cannot have two files called FooBar and foobar in the same directory. I discovered this the hard way with subversion.
@rderosier
Can you please use CODE tags like the others do when showing computer text? Posting in Code Tags - A Guide
I just tested this. What a pain finding a data CD without Rock Ridge extensions. I eventually found a Microsoft WindowsNT SDK (1992)
mount -t iso9660 -o ro,nosuid,nodev,relatime,uid=1001,gid=100,iocharset=utf8,mode=0400,dmode=0500,uhelper=udisks,**map=normal** /dev/sr0 /media/
umount /media
mount -t iso9660 -o ro,nosuid,nodev,relatime,uid=1001,gid=100,iocharset=utf8,mode=0400,dmode=0500,uhelper=udisks,**map=off** /dev/sr0 /media/
umount /media
“map=on” is invalid
“map=normal” translates everything to lower case e.g. “file:///media/mips/40291730.ppd”
“map=off” shows everything as upper case e.g. “file:///media/MIPS/40291730.PPD;1”
map undefined == map=normal
From an old Linux distribution:
With Rock Ridge extensions both “map=normal” and “map=off” give mixed case e.g. “file:///media/distributions/MCC/1.0+/documentation/MCC.README.install”
Well his DVD does have RR, so mixed case should work. Question is whether it was written with mixed case on the writing machine.
I have just remembered a long tortured telephone conversation I had with someone (I think a Microsoft user) who had been sent a bunch of files by one of my clients. Our confusion was the result of the recipient’s system displaying all file-names in “normal case” i.e. with capitalised initial letters, irrespective of the actual file-name. I wonder if the OP’s CD was written in lower case, but the OSX viewing program is displaying it with capitalised initials?
rderosier wrote:
> After the above, the contents of the cdrom were still all lower-case.
>
> Any further suggestions?
Everybody is concentrating on completely solving the problem, which is
undoubtedly the ideal solution.
But just in case a workaround is acceptable, I wanted to point out that
it is trivial to write a script to rename all the files and directories
using an upper case first letter.
But; the request was not for a “solution”, but for an explanation of why.