Bug#405454: [new check] init script in level S must only use commands from /sbin:/bin
Raphael Geissert <atomo64@gmail.com> writes:
> Lately, I've been working on parallel booting and I've been hit by
> some packages relying on which, find, and other tools.
>
> Since the list of binaries in /bin and /sbin shouldn't change too
> often, I think it would be feasible to generate and store that list in
> data/.
Yeah, we should be able to do something based on the Contents file, I'd
think. The only trick is that it may vary by architecture.
> Now that insserv can order the scripts based on their dependencies am
> not sure the "no S script should use binaries from /usr" argument
> still applies, as depending on $remote_fs should be enough.
Agreed. However, I think that means the check is still valid -- it just
needs to check anything that doesn't specify a $remote_fs dependency, if
I remember the meaning of that correctly.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: