From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200201242153.QAA15132@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Weirdness with 9660srv and file names (extensions)?
In-Reply-To: Your message of "Thu, 24 Jan 2002 02:36:46 EST."
             <20020124073650.2B60019A5F@mail.cse.psu.edu>
From: Dan Cross <cross@math.psu.edu>
Date: Thu, 24 Jan 2002 16:53:47 -0500
Topicbox-Message-UUID: 4413b840-eaca-11e9-9e20-41e7f4b1d025

> ls -l /mnt/cd
>
> the owner/group will tell you what sort
> of format the cd is.  that'd be a start.
>
> if it's iso9660 or joliet or plan9, i'm stumped.
>
> if it's ridge or sierra, we might be parsing things
> wrong, or the file might really be named ``readme.''

Shucks, I left my laptop at home this morning, so I'm afraid I can't
tell definitively at the moment, but the problem showed up trying to
read the VN Inferno CD, among others.  The file is most definitely
*not* named ``readme.''; the periods don't show up under other OS's
(I've tried Windows and FreeBSD), and the Inferno installation script
failed when it couldn't find, eg, ``foo'' because ``foo'' was known
as ``foo.''.  Not what VN had intended, I'm guessing.

(this is from memory)  I did modify a routine, called, I believe,
rzdir() in 9660srv.c to remove trailing dots from file names shortly
after a section of code in which file version numbers were being
stripped off.  That seemed to fix at least some of it; it strikes me
that was using a strict iso9660 CD.

	- Dan C.