Anton Aylward wrote:
Linda Walsh said the following on 04/11/2013 09:59 PM:
why? PATH not working?
Well, on the one hand: <quote src="man page for execcv"> Special semantics for execlp() and execvp() The execlp(), execvp(), and execvpe() functions duplicate the actions of the shell in searching for an executable file if the specified filename does not contain a slash (/) character. The file is sought in the colon-separated list of directory pathnames specified in the PATH environment variable. </quote>
and on the other there is the execve(2) system call that does not have the wrapper that the above form and needs an absolute path name.
But PATH has been a standard that system programs have historically honored. You don't want to have to hard-code paths into an application because they may move.
You're a person that has stripped things down on your system.
---- Not really... I just turn off unneeded functionality.
What do you think the the smallest "init" or init-replacement could be with the least other stuff running, that is without having to start up the shell and all the stuff that drags in?
That would still be compatible with 99% of the the startup software out there? I don't remove things that would break compatibility. That'd be shooting myself in the foot. The point is to reduce unnecessary work and not generate more work. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org