From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev & kernel names
Date: Wed, 27 Apr 2005 16:05:46 +0000 [thread overview]
Message-ID: <20050427160546.GC2043@kroah.com> (raw)
In-Reply-To: <20050426231516.GD2740@us.ibm.com>
On Tue, Apr 26, 2005 at 04:15:16PM -0700, Nishanth Aravamudan wrote:
> Greg, udev Developers,
>
> One of the most valuable features of new udev-based system is persistent
> device naming. This is especially useful for large systems, which may
> involve upwards of 4000 disks. Rather than determining which disk is
> sdzz, the administrator can name it tray15_disk7 and thus easily access
> the drive. We all know this much, though.
>
> Another interesting idea would be to somehow inform the kernel of these
> new names (sysfs?).
Um, didn't we talk about this before?
And didn't I get across the point that this is pointless, wrong, and
will never happen? :)
> The gist being that currently, even though udev has
> created a new dev node for the device, the kernel is unaware of this
> ``name'' when reporting errors. I think it could be very useful for our
> friendly sysadmin to see ``tray15_disk7 has failed'' rather than ``sdzz
> has failed.'' Or perhaps they want to offline an entire tray; it would
> be simpler in scripts to refer to ``tray15_*'' than the appropriate
> kernel device nodes.
>
> My questions are:
>
> Is this feasible?
No.
> Would a new file per-device in sysfs be the appropriate place for this?
No.
> Is there a better way to go about getting these useful log messages?
Modify your syslog program to do it.
Oh, and what about the fact that I can create 2 device nodes in the fs
that really are the same kernel device?
/me watches the ras developers get all agitated
> If I need to clarify the problem/proposed solution further, please let
> me know.
Please let me know who is trying to drive such a misguided and
ill-conceived issue and I will track them down...
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
next prev parent reply other threads:[~2005-04-27 16:05 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 [this message]
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
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=20050427160546.GC2043@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 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.