From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reiserfs: fix handling of device names with /'s in them
Date: Wed, 12 Jul 2006 22:23:12 -0700 (PDT) [thread overview]
Message-ID: <e94lc0$tsv$1@terminus.zytor.com> (raw)
In-Reply-To: 20060712175542.108e6e37.akpm@osdl.org
Followup to: <20060712175542.108e6e37.akpm@osdl.org>
By author: Andrew Morton <akpm@osdl.org>
In newsgroup: linux.dev.kernel
>
> On Wed, 12 Jul 2006 12:42:28 -0400
> Jeff Mahoney <jeffm@suse.com> wrote:
>
> > On systems with block devices containing slashes (virtual dasd, cciss,
> > etc), reiserfs will fail to initialize /proc/fs/reiserfs/<dev> due to
> > it being interpreted as a subdirectory. The generic block device code
> > changes the / to ! for use in the sysfs tree. This patch uses that
> > convention.
>
> Isn't it a bit dumb of us to be putting slashes in the device names anyway?
> It would be better, if poss, to alter dasd/cciss/etc and stop all these
> s@/@!@everywhere games.
A *lot* of people have been requesting more, not less, hierarchy in
the filenames in /dev, and by now there is plenty of history there,
too. The convention needs to be consistent and stable, though.
-hpa
next prev parent reply other threads:[~2006-07-13 5:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 16:42 [PATCH] reiserfs: fix handling of device names with /'s in them Jeff Mahoney
2006-07-12 16:57 ` Eric Dumazet
2006-07-12 17:02 ` Jeff Mahoney
2006-07-13 0:55 ` Andrew Morton
2006-07-13 3:51 ` Hans Reiser
2006-07-13 4:00 ` Andrew Morton
2006-07-13 7:34 ` Hans Reiser
2006-07-13 5:23 ` H. Peter Anvin [this message]
[not found] <6xQ4C-6NB-43@gated-at.bofh.it>
[not found] ` <6xQea-6ZX-13@gated-at.bofh.it>
2006-07-14 16:10 ` Bodo Eggert
2006-07-14 17:50 ` Jeff Mahoney
2006-07-16 7:12 ` Hans Reiser
2006-07-16 15:56 ` Jeffrey Mahoney
2006-07-16 18:14 ` Hans Reiser
2006-07-16 22:17 ` Jeff Mahoney
2006-07-17 1:21 ` Hans Reiser
2006-07-17 1:50 ` Jeffrey Mahoney
2006-07-17 3:02 ` Hans Reiser
2006-07-17 3:17 ` Jeffrey Mahoney
2006-07-17 7:29 ` Hans Reiser
2006-07-17 14:55 ` Jeff Mahoney
2006-07-17 15:39 ` Carlos Carvalho
2006-07-17 16:05 ` Jeff Mahoney
2006-07-17 18:21 ` Hans Reiser
2006-07-17 18:19 ` Hans Reiser
2006-07-17 18:38 ` Jeff Mahoney
2006-07-17 19:07 ` Hans Reiser
2006-07-17 19:59 ` Jeff Mahoney
2006-07-17 21:03 ` Hans Reiser
2006-07-17 22:26 ` Rudy Zijlstra
2006-07-18 0:26 ` Horst von Brand
2006-07-18 16:38 ` Jan Engelhardt
2006-07-17 18:08 ` Valdis.Kletnieks
2006-07-17 18:16 ` Jeff Mahoney
2006-07-17 18:53 ` Hans Reiser
2006-07-17 19:07 ` Jeff Mahoney
2006-07-17 18:27 ` Hans Reiser
2006-07-17 19:52 ` Valdis.Kletnieks
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='e94lc0$tsv$1@terminus.zytor.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.