It turns out that the filesystem on the cdrom was iso9660 after all but with Joliet extensions. In addition I might have been lacking nls_cp437 support as well. I built a new kernel with Joliet and nls and now all the filenames have mixed case. -- -Time flies like the wind. Fruit flies like a banana. Stranger things have - -happened but none stranger than this. Does your driver's license say Organ -Donor?Black holes are where God divided by zero. Listen to me! We are all- -individuals! What if this weren't a hypothetical question? [EMAIL PROTECTED] On Mon, 20 Nov 2000, cdowns wrote: =>"Steven W. Orr" wrote: => =>> [root@syslang /mnt]# mount -t vfat /dev/cdrom /mnt/cdrom =>> mount: /dev/cdrom has wrong major or minor number =>> =>> I'm stil open to ideas. :-) =>> =>> On Mon, 20 Nov 2000, cdowns wrote: =>> =>> =>"Steven W. Orr" wrote: =>> => =>> =>> I got a cd in the mail from APPGEN. I mount it using: =>> =>> =>> =>> mount /mnt/cdrom =>> =>> =>> =>> and it seems to mount ok. Then I cd /mnt/cdrom and I see the following: =>> =>> =>> =>> [root@syslang cdrom]# ls =>> =>> license readme setup.sh setup~1.kde zag_init zag_li~1 zagjava.gif =>> =>> [root@syslang cdrom]# =>> =>> =>> =>> The problem is that, according to appgen, the file zag_init is supposed to =>> =>> be zaG_INIT. And setup.sh is supposed to be Setup.sh =>> =>> =>> =>> I checked the man page formount and I don't see anything wrong. My mtab =>> =>> file sez: =>> =>> =>> =>> /dev/scd0 /mnt/cdrom iso9660 ro,nosuid,nodev 0 0 =>> =>> =>> =>> and my mount command (with no args) sez =>> =>> =>> =>> /dev/scd0 on /mnt/cdrom type iso9660 (ro,nosuid,nodev) =>> =>> =>> =>> I saw that check=strict is the default, so I am out out of ideas. Anybody =>> =>> have any idea? BTW, APPGEN has no clue at all. "Hey it works for me." =>> =>> =>> =>> TIA =>> =>it is possible that the filesystem on the cd is joliet. and that the =>> =>file formats have not supported long file name... i would mount the th =>> =>cdrom like so : =>> => =>> =>mount -t vfat /dev/cdrom /mnt/cdrom =>> => =>> =>just to verify that the filesystem is FAT. if you mount it this way and the =>> =>filenmes still have ~.1 they do not have long filename and are being treated as =>> =>dos filnames. =>> => =>> =>i hope this makes sense.... i think ive worded it very strangle... =>> => =>> =>well goodluck. =>> => =>> =>chris =>> => =>> => => =>well do you have a symlink to /dev/scd0 ? if not then try this: => =>mount -t vfat /dev/scd0 /mnt/cdrom => =>try this .. => =>chris => ********************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the following text in the *body* (*not* the subject line) of the letter: unsubscribe gnhlug **********************************************************
