Bug#659955: update-rc.d: add option to specify alternative root (like insserv -p)
Dmitry Bogatov
KAction at debian.org
Fri Jan 11 12:36:49 GMT 2019
[ I believe this bug should be reassigned to bin:insserv, if current
maintainer of bin:init-system-helpers agree. ]
[2012-02-15 11:33] Peter Eisentraut <petere at debian.org>
> part text/plain 238
> Package: sysv-rc
> Version: 2.88dsf-22
> Severity: wishlist
>
> Please add an option like insserv -p or chkconfig --root to specify an
> alternative root for the init scripts. This would be useful for
> testing and for fixing other file systems.
According to insserv(8), it must be possible (insserv=1.18.0):
[[/]path/to/init.d/]
Relative or absolute path to the init scripts base directory.
This defaults to /etc/init.d/ in compliance with the LSB speciā
fication. In this case insserv does not add or remove a script
to the runlevels declared in the script headers, but may
re-order the runlevels if the order of the currently enabled
scripts has changed (see option -d). Note that if a relative
path is used insserv has to be called from the root directory.
but I failed to make use of it:
$ mkdir /tmp/temp-1
$ cp -r /etc/init.d .
$ /sbin/insserv init.d
$ ls
init.d rc0.d rc1.d rc2.d rc3.d rc4.d rc5.d rc6.d rcS.d
$ find -empty
./rcS.d
./rc6.d
./rc5.d
./rc4.d
./rc3.d
./rc2.d
./rc1.d
./rc0.d
Jesse, am I holding it wrong?
More information about the Pkg-systemd-maintainers
mailing list