From: Ulrich Drepper <drepper@redhat.com>
To: root@chaos.analogic.com
Cc: viro@parcelfarce.linux.theplanet.co.uk,
Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>,
Jamie Lokier <jamie@shareable.org>,
linux-kernel@vger.kernel.org
Subject: Re: JFS default behavior
Date: Fri, 13 Feb 2004 10:50:16 -0800 [thread overview]
Message-ID: <402D1C68.5030600@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0402131325470.1895@chaos>
Richard B. Johnson wrote:
> I think that all ASCII characters below 0x20 are forbidden in
> Unix file-names
Not true. Filenames in Unix are defined as
3.169 Filename
A name consisting of 1 to {NAME_MAX} bytes used to name a file. The
characters composing the name may be selected from the set of all
character values excluding the slash character and the null byte. The
filenames dot and dot-dot have special meaning. A filename is
sometimes referred to as a pathname component .
Only NUL and / are special.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
next prev parent reply other threads:[~2004-02-13 18:51 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 16:50 JFS default behavior (was: UTF-8 in file systems? xfs/extfs/etc.) Nicolas Mailhot
2004-02-12 18:12 ` Robin Rosenberg
2004-02-13 3:03 ` Jamie Lokier
2004-02-13 10:07 ` Robin Rosenberg
2004-02-13 18:06 ` Nicolas Mailhot
2004-02-13 18:15 ` viro
2004-02-13 18:24 ` Valdis.Kletnieks
2004-02-13 18:31 ` viro
2004-02-13 20:27 ` Jamie Lokier
2004-02-13 18:31 ` Richard B. Johnson
2004-02-13 18:50 ` Ulrich Drepper [this message]
2004-02-13 22:39 ` Robin Rosenberg
[not found] <04Feb13.163954est.41760@gpu.utcc.utoronto.ca>
2004-02-14 14:27 ` JFS default behavior Nicolas Mailhot
2004-02-14 15:40 ` viro
2004-02-14 17:47 ` Nicolas Mailhot
2004-02-14 17:59 ` Nicolas Mailhot
2004-02-14 23:06 ` Robin Rosenberg
2004-02-14 23:29 ` viro
2004-02-15 0:07 ` Robin Rosenberg
2004-02-15 2:41 ` Linus Torvalds
2004-02-15 3:33 ` Matthias Urlichs
2004-02-15 4:04 ` viro
2004-02-15 9:48 ` Robin Rosenberg
2004-02-15 18:26 ` yodaiken
-- strict thread matches above, loose matches on Subject: below --
2004-02-15 14:48 Pascal Schmidt
2004-02-16 14:24 ` Eduard Bloch
2004-02-15 23:03 Nicolas Mailhot
2004-02-16 3:45 ` Jan Knutar
2004-02-16 8:30 ` Nicolas Mailhot
2004-02-16 8:54 ` Valdis.Kletnieks
2004-02-16 6:21 ` jw schultz
2004-02-16 15:55 ` Jamie Lokier
2004-02-17 6:47 ` jw schultz
2004-02-17 21:37 ` Jamie Lokier
2004-02-17 22:12 ` Linus Torvalds
2004-02-18 9:59 ` Jamie Lokier
2004-02-18 15:54 ` Linus Torvalds
2004-02-18 23:58 ` Jamie Lokier
[not found] <1pvUz-6j-1@gated-at.bofh.it>
[not found] ` <1pRVj-2am-29@gated-at.bofh.it>
2004-02-16 15:32 ` Pascal Schmidt
2004-02-16 19:05 ` Eduard Bloch
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=402D1C68.5030600@redhat.com \
--to=drepper@redhat.com \
--cc=Nicolas.Mailhot@laPoste.net \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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