> And yeah, works fine, but I must add the "ENV{PATH}="
> directive on each
> and every udev rule that runs a program, and that is far from a good
> solution (plus bloats the rules files a lot).
>
> Anyone with a broader perspective can suggest a better solution?
>
> Best regards.
>
> P.S: I'm using FC6 for my desktop and noticed that it does
> not deal with
> the PATH environment variable wherever it executes a program
> in a rule.
> Has red hat patched udev?, or is it just that all external
> programs take
> care of this themselves? (if the program is a shell script,
> it can set
> the PATH right at the start, if the program is an executable
> binary, it
> is ok not to have a PATH as long as you don't call other external
> programs as busybox's ifup does...)
My guess would be that FC6 uses bash and bash has a reasonable /etc/profile
setup.
So perhaps you should check that your udevd is started from a reasonable
environment?
-- Jan Evert
_______________________________________________
busybox mailing list
[email protected]
http://busybox.net/cgi-bin/mailman/listinfo/busybox
