From: Christoph Hellwig <hch@infradead.org>
To: Michael Clark <michael@metaparadigm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Kevin Corry <corryk@us.ibm.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org,
evms-devel@lists.sourceforge.net
Subject: Re: [Evms-devel] Re: [PATCH] EVMS core 2/4: evms.h
Date: Thu, 3 Oct 2002 16:14:05 +0100 [thread overview]
Message-ID: <20021003161405.A20832@infradead.org> (raw)
In-Reply-To: <3D9C5DD6.40103@metaparadigm.com>; from michael@metaparadigm.com on Thu, Oct 03, 2002 at 11:10:14PM +0800
On Thu, Oct 03, 2002 at 11:10:14PM +0800, Michael Clark wrote:
>
> >>+#define DEV_PATH "/dev"
> >>+#define EVMS_DIR_NAME "evms"
> >>+#define EVMS_DEV_NAME "block_device"
> >>+#define EVMS_DEV_NODE_PATH DEV_PATH "/" EVMS_DIR_NAME "/"
> >>+#define EVMS_DEVICE_NAME DEV_PATH "/" EVMS_DIR_NAME "/" EVMS_DEV_NAME
> >
> >
> > The kernel doesn't know about device names at all.
>
> It does for specifying root devices and for devfs.A
root device should be in do_mount.c and not in obscure headers.
devfs doesn'T need hardcoded "/dev" prefixes, and it's better to not
add defines for the strings in devfs so that crap doesn't get spread
over the code but is localized to the existing devfs damage
next prev parent reply other threads:[~2002-10-03 15:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 12:36 Kevin Corry
2002-10-03 14:50 ` Christoph Hellwig
2002-10-03 15:10 ` [Evms-devel] " Michael Clark
2002-10-03 15:14 ` Christoph Hellwig [this message]
2002-10-03 16:22 ` Linus Torvalds
2002-10-03 17:42 Mark Peloquin
2002-10-04 12:28 ` Robert Varga
2002-10-04 14:08 ` Christoph Hellwig
2002-10-04 14:36 ` Richard B. Johnson
2002-10-03 18:59 Mark Peloquin
2002-10-04 14:14 ` Christoph Hellwig
2002-10-04 14:34 ` Andreas Dilger
2002-10-04 17:10 ` Christoph Hellwig
2002-10-04 13:59 Mark Peloquin
2002-10-04 14:59 Mark Peloquin
2002-10-04 18:45 Steve Pratt
2002-10-07 17:25 ` Christoph Hellwig
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=20021003161405.A20832@infradead.org \
--to=hch@infradead.org \
--cc=corryk@us.ibm.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@metaparadigm.com \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®