mount command - erroneous file name extensions

[JHL_2]

Hello all. I am currently installing software from a CD. When I mount the cd and check the mounted file system (/cdrom) I get "funky" file name extensions. For example, instead of finding the file "install.sh" I get "INSTALL.SH;1". The ";1" extension and the caps are not expected. The system is a K-class running 11.11

[A. Clay Stephenson · Accepted solution]

You need to add -o cdcase to your mount -F cdfs command. Man mount_cdfs for details.

[David Bell_1]

JHL,

I'm not sure what type of cd you're mounting but try

mount -o cdcase /dev/dsk/cXtXdX /cdrom.

That should rectify the problem.

HTH,

Dave

[Alan Casey]

you need to use pfs_mount


pfsd&
pfs_mountd &
pfs_mount -o xlat=unix /dev/rdsk/c0t2d0 /CDROM



nfs server must also be running at the time

[Steve Steel]

Hi


Sounds like rockridge

need these or later loaded
[PHCO_25841/PACHRDME/English]
[PHKL_25760/PACHRDME/English]
[PHKL_26269/PACHRDME/English]

Then
You must use the additional option, -o rr, when mounting
a Rock Ridge CD:


# mount -F cdfs -o rr /dev/dsk/c#d#t# /cdrom

Regards

Steve Steel

Quote of the moment
-------------------
"We are drowning in information but starved for knowledge."
-- John Naisbitt

[JHL_2]

Actually the application is visifax. Also, I get both the case and the file name extensions on other cd applications as well. Just lookin' to see if there is another way to mount it and avoid both problems.

[Robert-Jan Goossens]

Hi,

Copied from (Procura)Merijn

https://www.beepz.com/personal/merijn/

My CD-ROM doesn't show what I expect
It can be an Oracle CD-ROM, or a CD created on Windows, or whereever they used Rock Ridge extensions. Long names are truncated or show upper case only. Oracle tells you to use pfs_mount.

Do not use pfs_mount!. Install the Rock-Ridge extension patches instead and never worry about these problems. For HP-UX 11.00 you will need forget all about PFS and install PHKL_26448, PHCO_26449, and PHKL_26450 to have HP-UX recognize those file systems automatically on mount! For HP-UX 11i you need PHCO_25841, PHKL_26269 , and PHKL_25760.

No need thereafter to use -o cdfs to mount anymore, provided you enter the CD drive in /etc/fstab like this:

/dev/cd0 /cdrom cdfs ro,rr,noauto 0 0


Kind regards,

Robert-Jan.

[MANOJ SRIVASTAVA]

Hi JHL


there are 2 ways to get over this , if it is a normal mount then

mount -F cdfs -ocdcase /dev/dsk/c0t2d0 /cdrom will do the job , incase it is an oracle cd and u need PFS_MOUNT then you need to the follwing :


pfs_mountd &
pfsd &
pfs_mount -x no_version -x lower_case /dev/rdsk/c0t20d0 /cdrom


will mount with these funky externsions .



Manoj Srivastava

[Wodisch]

Hi,

actually "visifax" sounds like some "Windows" software, so if you are out of luck, then that CD-ROM is NOT really mountable on HP-UX, if it is not ISO9660/High-Sierra/RickRidge-Extension, but "Joliet" (MS gimmicks on top of RockRidge)...
Mount it on a PC, "share" it there, and use "cifs_mount" to access it from HP-UX (that needs the "CIFS/9000 client" to be installed)...

HTH,
Wodisch

[Bill Hassell]

Actually, VsiFax is a very powerful fax package that runs on several flavors of Unix including HP-UX. Clients can be PC or Unix (OK, the server can also be NT or Win2k).

The problem is that the default behavior for HP-UX is to display the filenames exactly as they are stored on the CDROM (UPPERCASE plue ;1 version numbers). Most Unices and PCs translate to lowercase and strip ;1 silently. So mount the VsiFax CD using -ocdcase option and all will be well.

The PFS solution isn't needed but will work (if you start it correctly), and the RockRidge patches will also work (the mount option will be -orr) but there is a big problem with these patches. Certain CDROM formats (specifically, a Cisco router support CD will cause this) will crash the system. For 11.0, the fix is to replace 26448 with 21586, but there is no fix at all for 11.11.

Another alternative is to downlad VsiFax software direct from Esker's ftp server. The big tarball is ready to use (note: 30-60 megs in size).

[Michael Pausche]

I was having a similar problem. Thanks David Bell and Steve Steel your solutions solved my problem.