public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: List created to discuss device naming
Date: Mon, 5 Apr 2004 21:23:25 +0000 (UTC)	[thread overview]
Message-ID: <c4siod$f6l$1@terminus.zytor.com> (raw)
In-Reply-To: A06801158AE07847B27A52C1A074BC1D04C90E2B@fmsmsx404.fm.intel.com

Followup to:  <A06801158AE07847B27A52C1A074BC1D04C90E2B@fmsmsx404.fm.intel.com>
By author:    "Wichmann, Mats D" <mats.d.wichmann@intel.com>
In newsgroup: linux.dev.kernel
>
> This note is to announce creation of a single-topic
> mailing list on common device naming.
> 
> As LSB project lead, I've been asked about specifying
> Linux device naming in the LSB.  We're not set up to do
> that; the LSB can only specify what is already "best
> practice".  
> 
> A number of people think that getting this right in
> the new world of userspace device naming (e.g. udev)
> is important enough that they'd like to get together
> and try to achieve common ground between those
> shipping distributions with the 2.6 kernel.
> 
> Having a common device naming policy would be a nice
> thing for certain classes of applications. Once developed 
> and adopted,  this policy could be a candidate for
> inclusion in the LSB or the FHS.
> 
> If you consider yourself a stakeholder in this, please 
> join the list device_naming@lists.osdl.org at:
> 

There already *is* a Freestandards group chartered to deal with this,
i.e. LANANA.  It's included in the FHS by reference.

	-hpa


      parent reply	other threads:[~2004-04-05 21:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02 22:00 List created to discuss device naming Wichmann, Mats D
2004-04-05  1:42 ` Jeff Garzik
2004-04-05 21:23 ` H. Peter Anvin [this message]

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='c4siod$f6l$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox