On Mon, Dec 02, 2013 at 02:48:52PM -0800, Russ Allbery wrote: > > Sure. Both systemd and upstart manage to avoid the problem of > > inconsistent behavior due to tainted admin environments, because daemons > > are always started as children of init and not of the admin's login > > shell. That being the case, hard-coding the path to an executable in > > your initscript equivalent doesn't buy you much added protection, > > compared with just using the system $PATH, and does cause gratuitous > > incompatibilities in exactly those cases that Debian Policy's > > prohibition on hard-coded paths is meant to address.
> I have never seen a gratuitous incompatibility caused by this. Do you > have any examples? I would argue that every single result returned by 'ls -l /usr/sbin/ /usr/bin|grep /bin', preventing us from merging /usr/ into / by default, is an example of such historical incompatibilities. But any other cases where binaries have moved from one directory or another without providing such compat symlinks would also qualify. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature