From: Jes Sorensen <jes@wildopensource.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [announce] scsi_id 0.1 - generate unique scsi id
Date: Thu, 23 Oct 2003 07:33:32 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106690734616946@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106684627128777@msgid-missing>
>>>>> "Patrick" = Patrick Mansfield <patmans@us.ibm.com> writes:
Patrick> On Wed, Oct 22, 2003 at 04:52:31PM +0100, Matthew Wilcox
Patrick> wrote:
>> You shouldn't be installing them into the <sys/> namespace, that's
>> basically owned by POSIX. How about <sysfs/> instead?
Patrick> I incorrectly suggested we should use <sys/>.
Patrick> Should we use <linux/>, rather than another new directory?
Rule of thumb: any existing hierachy is reserved, either you want to
drop it in header root, ie. /usr/include or /usr/loca/include or you
want to create your own hierachy, <sysfs/> as Matthew suggested looks
like a good candidate to me.
Cheers,
Jes
-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2003-10-23 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 16:15 [announce] scsi_id 0.1 - generate unique scsi id Patrick Mansfield
2003-10-22 16:23 ` Christoph Hellwig
2003-10-23 7:33 ` Jes Sorensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 0:12 Patrick Mansfield
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=marc-linux-hotplug-106690734616946@msgid-missing \
--to=jes@wildopensource.com \
--cc=linux-hotplug@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 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).