_id utilities
Hi all,
A couple of questions. Why aren't "scsi_id", "cdrom_id", installedby default? If they're now the standard utilities to manage persistentdevice naming they should be installed with 'make install'. And, why is the default path to install them /lib/udev? It's alsoharcoded in the source and it doesn't look good. It'd be better toinstall them in /sbin
cheers,
-- David Gómez Jabber ID: [email protected]
_______________________________________________Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.netLinux-hotplug-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
On Mon, 2006-06-19 at 14:11 +0200, David Gómez 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 todecide what to put in here. There are also no "standard" rules installedby udev until now.
Quoted 1 line
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", ifthey are in /lib/udev. The tools are not really useful outside of udevand intentionally don't show up on shell autocompletion (scsi_id has asymlink to /sbin for backwards compatibility). In general the udev tools will not give you any information which is notalready available in /dev/disk/by-*/, so there is no real need to makethem public in /sbin and get the pain of keeping the interfaces stable. Kay
_______________________________________________Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.netLinux-hotplug-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
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.
Quoted 1 line
Quoted 1 line
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 ;).
Quoted 1 line
The tools are not really useful outside of udev> and intentionally don't show up on shell autocompletion (
scsi_idhas 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: [email protected]
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&kid0709&bid&3057&dat1642_______________________________________________Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.netLinux-hotplug-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 3 lines · David Gómez
"/lib", according to the FHS standard, is for "essential shared libraries and kernel modules". IMHO to hide binaries in /lib standard directories is not good, they should be in sbin.
Not if they are not supposed to be run from the command line. And they are not.
Signature · 11 lines
ciao, Marco 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 easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net [email protected] https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel