From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: getting rid of chassis_id
Date: Sat, 10 Sep 2005 21:34:40 +0000 [thread overview]
Message-ID: <20050910213440.GD13679@kroah.com> (raw)
In-Reply-To: <20050908110033.GA27984@vrfy.org>
On Thu, Sep 08, 2005 at 01:00:33PM +0200, Kay Sievers wrote:
> Does anybody have ever used extras/chassis_id? It calls scsi_id, then
> looks up 3 numbers in a text file. These 3 numbers are returned
> to udev and can be used to form some kind of "chassis mapping" for a
> disk.
> A horrible hack, pretty useless, unmaintained and broken. I really
> don't think that it is ever was useful for anything. A task like this
> is efficiently done with udev rules instead of maintaining an
> external mapping in a file hardcoded to /usr/local/bin/provision.tbl.
>
> If nobody wants to fix it, it will only be available in the older
> releases. :)
Intel provided it, but I never liked it, and unless they protest, I
think it should be removed.
thanks,
greg k-h
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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
prev parent reply other threads:[~2005-09-10 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 11:00 getting rid of chassis_id Kay Sievers
2005-09-10 21:34 ` Greg KH [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=20050910213440.GD13679@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).