maybe I missed that ubuntu does interpret the meaning of /sbin differently than the classic UNIX systems. In that case I'd fix it in my .bashrc.
I really would be interested in a statement of an experienced ubuntu developer about such a decission and the reasons for it.
Anyway I'm a bit surprised, that the "fix" was released that quickly, given that it does not fix anything. Either my point that one cannot assume that /sbin is in $PATH is right. Then the fix is not sufficient. Or it is wrong, then my whole bug report is not justified.
In the former case the logical solution would be, that no executables that a non root user needs should reside in an sbin dir. That would affect the package upstart-bin, that provides /sbin/upstart as well as /sbin/initctl. upstart-bin also has some executables in /bin, so there seems to be some distinction between /bin and /sbin
Now we have a fix for a maybe not justified bug report that actually does not solve the problem. I actually would be happier with "won't fix" and a clear statement that also (/usr)+/sbin should be in the user's $PATH.
Hi Gunnar,
maybe I missed that ubuntu does interpret the meaning of /sbin differently than the classic UNIX systems. In that case I'd fix it in my .bashrc.
I really would be interested in a statement of an experienced ubuntu developer about such a decission and the reasons for it.
Anyway I'm a bit surprised, that the "fix" was released that quickly, given that it does not fix anything. Either my point that one cannot assume that /sbin is in $PATH is right. Then the fix is not sufficient. Or it is wrong, then my whole bug report is not justified.
In the former case the logical solution would be, that no executables that a non root user needs should reside in an sbin dir. That would affect the package upstart-bin, that provides /sbin/upstart as well as /sbin/initctl. upstart-bin also has some executables in /bin, so there seems to be some distinction between /bin and /sbin
Now we have a fix for a maybe not justified bug report that actually does not solve the problem. I actually would be happier with "won't fix" and a clear statement that also (/usr)+/sbin should be in the user's $PATH.