SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The value of envar PATH for processes run by the udev system is "/usr/gnu/bin:/usr/local/bin:/bin:/usr/bin:.". If peer review (that's you!) agrees it is a poor choice how can I submit an enhancement request? The man pages do not say anything about bug reporting.
Here are reasons why it is a bizarre choice:
There is no /gnu/bin directory on as-installed Slackware.
/usr/local/bin is empty (or very nearly empty?) on as-installed Slackware.
Processes running under udev run as root; having "." in PATH is not good practice when running as root.
Processes running under udev are likely to be doing "system" work so executables from the sbin directories are likely to be used. For example, udevadm itself is /sbin/udevadm.
Presumably this PATH is set by udevd itself; it is not the PATH in effect when udevd is started by rc.M.
AFAIK udevd's PATH is not configurable.
The workaround is for processes initiated by udev to set a sane PATH for themselves, perhaps "/usr/sbin:/sbin:/usr/bin:/bin".
EDIT: seen on Slackware 13.0 32 bit.
EDIT2: rc.udev is run from rc.S, not rc.M as stated above
Apparently older udevd cleaned PATH but not anymore (circumstantial). W/o need for patching, could starting Udev like 'env PATH=/usr/sbin:/sbin:/usr/bin:/bin /sbin/udevd --whatever-args' work? That is, if the "Steps to reproduce" method shows that helper apps inherit that path.
Last edited by unSpawn; 04-07-2010 at 03:12 PM.
Reason: //unhide link target
Apparently older udevd cleaned PATH but not anymore (circumstantial: ). W/o need for patching, could starting Udev like 'env PATH=/usr/sbin:/sbin:/usr/bin:/bin /sbin/udevd --whatever-args' work? That is, if the "Steps to reproduce" method shows that helper apps inherit that path.
Thanks unSpawn Have modified rc.udev and will report result after next reboot.
I sent an email to info <antelope> AT <fish> slackware.com asking them to consider modifying udevd to set a PATH or bash to have a default PATH that is useful on Slackware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.