From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] filename length
Date: Sat, 16 Jun 2001 10:50:43 -0400 [thread overview]
Message-ID: <200106161450.KAA15733@augusta.math.psu.edu> (raw)
In-Reply-To: <002a01c0f605$e2f1a310$6401a8c0@freeze2k>
In article <002a01c0f605$e2f1a310$6401a8c0@freeze2k> you write:
>I'm frustrated by the filename maximum length.
>
>I can't unzip the jargon file :-(
>And some of my mp3 filenames dont survive.
>So no using the cpuserver as an mp3 jukebox
>
>Just wanted that on record :-)
This is one of the many perceived deficiencies that's being address
in 9P2000.
- Dan C.
prev parent reply other threads:[~2001-06-16 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-16 1:32 Matt
2001-06-16 14:32 ` FJ Ballesteros
2001-06-16 14:50 ` Dan Cross [this message]
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=200106161450.KAA15733@augusta.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).