9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
Date: Tue,  9 Jul 2002 11:37:36 +0200	[thread overview]
Message-ID: <25ce3bf663718a1be86b527e95618430@plan9.escet.urjc.es> (raw)

[-- Attachment #1: Type: text/plain, Size: 117 bytes --]

It's ok if the name contains '?', it's just inconvenient but
it's ok. It's like that inconvenient "'chk" name I had.

[-- Attachment #2: Type: message/rfc822, Size: 2762 bytes --]

From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
Date: Tue, 9 Jul 2002 11:28:57 +0200
Message-ID: <20020709112856.L20312@cackle.proxima.alt.za>

On Tue, Jul 09, 2002 at 10:42:04AM +0200, Fco.J.Ballesteros wrote:
> 
> I'm renaming ' ' with ? in u9fs
> There's no problem doing that since there's no ?
> in outside file names.

There could be:

-rw-r--r--   1 lucio  staff         0 Jul  9 11:22 t?uch

produced by "touch t\?uch" on my NetBSD host.  This is from
"man 2 intro" on NetBSD 1.5.2:

     File Name
             Names consisting of up to 255 (MAXNAMELEN) characters may be used
             to name an ordinary file, special file, or directory.

             These characters may be selected from the set of all ASCII char-
             acter excluding 0 (NUL) and the ASCII code for `/' (slash).  (The
             parity bit, bit 7, must be 0.)

             Note that it is generally unwise to use `*', `?', `[' or `]' as
             part of file names because of the special meaning attached to
             these characters by the shell.

It needn't be up to date, but it's a safe indicator.

++L

             reply	other threads:[~2002-07-09  9:37 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09  9:37 Fco.J.Ballesteros [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-10  7:57 Fco.J.Ballesteros
2002-07-09 12:24 Fco.J.Ballesteros
2002-07-09  8:42 Fco.J.Ballesteros
2002-07-09  9:28 ` Lucio De Re
2002-07-09 11:23   ` andrey mirtchovski
2002-07-09 12:05     ` matt
     [not found] ` <Fco.J.Ballesteros@Jul>
2002-07-09 15:29   ` Dave
2002-07-10 15:57   ` Dave
2002-07-09  8:40 Fco.J.Ballesteros
2002-07-09  7:50 Fco.J.Ballesteros
2002-07-09  8:15 ` Lucio De Re
2002-07-09  8:42   ` arisawa
2002-07-09  9:21     ` Lucio De Re
2002-07-09  9:43       ` arisawa
2002-07-09 10:36         ` Lucio De Re
2002-07-09 10:54           ` matt
     [not found]     ` <"arisawa@ar.aichi-u.ac.jp"@Jul>
2002-07-09 15:31       ` Dave
2002-07-09 22:15         ` arisawa
2002-07-09  8:22 ` arisawa
2002-07-09  7:46 Fco.J.Ballesteros
2002-07-09  0:38 okamoto
2002-07-08 16:14 rob pike, esq.
2002-07-08 16:07 rob pike, esq.
2002-07-08 20:58 ` Dave
2002-07-08 22:18   ` arisawa
2002-07-08 16:05 Fco.J.Ballesteros
2002-07-08 16:00 rob pike, esq.
2002-07-08 15:51 Fco.J.Ballesteros
2002-07-08 15:42 rob pike, esq.
2002-07-08 15:18 Fco.J.Ballesteros
2002-07-08 15:16 rob pike, esq.
2002-07-08 15:10 Fco.J.Ballesteros
2002-07-08 15:16 ` Lucio De Re
2002-07-08 14:54 Fco.J.Ballesteros
2002-07-08 15:05 ` Lucio De Re

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=25ce3bf663718a1be86b527e95618430@plan9.escet.urjc.es \
    --to=nemo@plan9.escet.urjc.es \
    --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).