From: "David Gómez" <david@pleyades.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: _id utilities
Date: Thu, 06 Jul 2006 19:03:17 +0000 [thread overview]
Message-ID: <20060706190316.GA2647@fargo> (raw)
In-Reply-To: <20060619121157.GA23044@fargo>
Hi Kay,
On Jun 19 at 02:29:06, Kay Sievers wrote:> > A couple of questions. Why aren't "scsi_id", "cdrom_id", installed> > by default? If they're now the standard utilities to manage persistent> > device naming they should be installed with 'make install'.> > Well it's Linux, there is no "standard". :) It's up to the distro's to> decide what to put in here. There are also no "standard" rules installed> by udev until now.
Yes, i think that to no install any rules is logical, it's up toeach distro to choose what rules to install. But, are there alternativesapproaches in distributions to do persistent naming? If not, i finda sane default to install *_id utilities.
> > And, why is the default path to install them /lib/udev? It's also> > harcoded in the source and it doesn't look good. It'd be better to> > install them in /sbin> > All tools can be called by just using their name: RUN="firmware.sh", if> they are in /lib/udev.
Yes, but because "/lib/udev" is hardcoded in the sources, which isquite ugly ;).
> The tools are not really useful outside of udev> and intentionally don't show up on shell autocompletion (scsi_id has a> symlink to /sbin for backwards compatibility).> > In general the udev tools will not give you any information which is not> already available in /dev/disk/by-*/, so there is no real need to make> them public in /sbin and get the pain of keeping the interfaces stable.
"/lib", according to the FHS standard, is for "essential sharedlibraries and kernel modules". IMHO to hide binaries in /libstandard directories is not good, they should be in sbin.
regards,
-- David Gómez Jabber ID: davidge@jabber.org
Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easierDownload IBM WebSphere Application Server v.1.0.1 based on Apache Geronimohttp://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642_______________________________________________Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.netLinux-hotplug-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-07-06 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 12:11 _id utilities David Gómez
2006-06-19 12:29 ` Kay Sievers
2006-07-06 19:03 ` David Gómez [this message]
2006-07-06 19:05 ` Marco d'Itri
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=20060706190316.GA2647@fargo \
--to=david@pleyades.net \
--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).