From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Weirdness with 9660srv and file names (extensions)?
Date: Thu, 24 Jan 2002 16:53:47 -0500 [thread overview]
Message-ID: <200201242153.QAA15132@math.psu.edu> (raw)
In-Reply-To: Your message of "Thu, 24 Jan 2002 02:36:46 EST." <20020124073650.2B60019A5F@mail.cse.psu.edu>
> 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.
next prev parent reply other threads:[~2002-01-24 21:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 7:36 Russ Cox
2002-01-24 21:53 ` Dan Cross [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-27 19:55 Russ Cox
2002-01-27 19:29 Russ Cox
2002-01-27 19:37 ` Alexander Viro
2002-01-28 18:11 ` Boyd Roberts
2002-01-28 23:23 ` Dan Cross
2002-01-28 23:30 ` William S.
2002-01-25 8:45 forsyth
2002-01-25 22:24 ` Dan Cross
2002-01-24 16:13 Russ Cox
2002-01-24 16:22 ` Boyd Roberts
2002-01-24 3:22 Dan Cross
2002-01-24 15:59 ` Boyd Roberts
2002-01-25 10:00 ` bs
2002-01-25 12:40 ` Boyd Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200201242153.QAA15132@math.psu.edu \
--to=cross@math.psu.edu \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).