linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev & kernel names
Date: Thu, 28 Apr 2005 04:37:15 +0000	[thread overview]
Message-ID: <20050428043715.GC10034@kroah.com> (raw)
In-Reply-To: <20050426231516.GD2740@us.ibm.com>

On Thu, Apr 28, 2005 at 09:01:29AM +1000, Martin Schwenke wrote:
> >>>>> "Greg" = Greg KH <greg@kroah.com> writes:
> 
>     >> Is there a better way to go about getting these useful log
>     >> messages?
> 
>     Greg> Modify your syslog program to do it.
> 
> /me dons asbestos suit...  :-)
> 
> ... and we've had the following conversation before, but let me try to
> put it more clearly right here.
> 
> Kernel names are evil.  They look like device names, but they are not
> device names.  They are kernel names.  Device names are created in
> userspace and the kernel has no knowledge of them.  The confusion
> occurs because they look the same (or similar)...

I know, we've been over this before.  A very simple solution to this is
just never have the kernel print the name it is internally using :)

> A nicer solution would be to log different canonical labels for
> devices, and pass these to udev.  For SCSI devices this could be
> something like "scsi/1:2:3:4" or even sd/major,minor - it doesn't
> matter too much.

dev_printk() solves this issue nicely.  Care to create a patch for all
places that you object to where the kernel prints out a kernel name?

thanks,

greg k-h



-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
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

  parent reply	other threads:[~2005-04-28  4:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-26 23:15 udev & kernel names Nishanth Aravamudan
2005-04-27 16:05 ` Greg KH
2005-04-27 16:43 ` Daniel Stekloff
2005-04-27 16:53 ` Nishanth Aravamudan
2005-04-27 16:57 ` Greg KH
2005-04-27 17:24 ` Daniel Stekloff
2005-04-27 23:01 ` Martin Schwenke
2005-04-28  4:37 ` Greg KH [this message]
2005-04-28 11:05 ` ocomber
2005-04-28 11:21 ` Michael Buesch
2005-04-28 14:22 ` ocomber
2005-04-28 14:43 ` Kay Sievers
2005-04-28 23:15 ` Martin Schwenke

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=20050428043715.GC10034@kroah.com \
    --to=greg@kroah.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).