From: belal@sco.COM (Bela Lubkin)
Newsgroups: biz.sco.general
Subject: CD-ROM mounting options (lowercase, version numbers)
Date: 20 Dec 92 13:58:41 GMT
Organization: [resent by] The SCOGEN gateway and Propagation Society
Resent-From: mmdf@xenitec.on.ca
Submit-To: scogen@xenitec.on.ca
Precedence: bulk

Bo Arnklit wrote:

> I'm using a 486/50MHz EISA machine with SCO 3.2.4 to run italy's leading
> on-line service called MC-link. I have mounted 4 cd-rom drives on the
> SCSI bus of a second identical machine and found that the filenames on
> the discs appear as "filename.ext;1". Filename and extension may be in
> upper and lower case and they are always followed by a semicolon and the
> number 1. I can access the file either using "filename.ext" or
> "filename.ext;1", however if I try to use the shell to expand
> metacharacters (like *.gif) it does'nt find anything, I must use
> "*.gif;1", but then if I use cp to copy them to a normal disk the ";1"
> remains attached to the filename. Filenames without extensions always
> have the dot attached just before the ";1", so for example "readme"
> becomes "readme.;1" and it is necessary that the dot is specified. I
> have studied the docs but there is very little about cd-roms.

You are seeing file version numbers, a feature which was added to the
High-Sierra filesystem standard for compatibility with DEC's VMS
operating system.  Most CD-ROM discs destined for use with anything but
VMS are highly unlikely to use file versioning.

> Ok so I've learned to live with it, adapting my programs that interact
> with the cd-roms.
>
> Yesterday I installed the cdrom drives on the production machine
> (identical hardware & software) but to my surprise all filenames
> (including directory names) are now in UPPERCASE and the ";1" suffix has
> disappeared.
>
> I've spent a lot of time to "diff" the various files in /etc/conf to see
> if there is some flag responsible for this weird behaviuor, but I
> haven't found anything yet.

The mount command in SCO UNIX 3.2v4 has options to turn file versioning
on and off.  I'm pretty sure you can store these options in
/etc/default/filesys so that they will automatically be applied each
time you try to mount a CD-ROM.  So I would suggest looking there to see
what's different.

Below is a document that covers these options, from SCO Support's
Information Tools database.

>Bela<

=============================================================================

Are there any special options that I can use when mounting a CD-ROM?

RELEASE:  SCO UNIX System V/386 Release 3.2 Operating System Version 4.0

PROBLEM:  Are there any special options I can use when mounting a CD-ROM
          as a high sierra filesystem on SCO UNIX System V/386 Release 3.2
          Operating System Version 4.0?

SOLUTION: There are three undocumented options to the mount(C) command
          that relate to high sierra.  They are:

          o lower        Used to interpret all files in lower case.

          o nolower      Used to interpret all files in upper case.

          o version      Used to display the version numbers of all
                         files on the CD-ROM.

          o novers       Used to suppress the version numbers of all
                         files on the CD-ROM.

          o showhidden   Used to display files on the CD-ROM that have
                         the hidden attribute set.


          For example, if you want to mount the CD-ROM in /dev/cd0,
          display files in lower case, and show hidden files, you would
          use the command:

                mount -fHS,lower,showhidden /dev/cd0 /mnt

          The default values for this version of SCO UNIX System are nolower
          and novers.

          NOTE:  If you are running the standalone DOS Merge 2.2 product
                 (which expects to see lower case values), you will need
                 to mount your CD-ROM with the 'lower' option.