Thomas Hood wrote:
Implementing the database wouldn't be too hard. update-rc.d
should simply do its thing twice: once to /etc/rc?.d/ and once
to /var/lib/rc/update/start/rc?.d/ and /var/lib/rc/update/stop/rc?.d/
(start links in the former, stop links in the latter).
On second thought, even easier would be for it to do its thing twice:
once to /etc/rc?.d/ and once to /var/lib/rc/update/default/rc?.d/.
I am envisioning a future enhancement to update-rc.d whereby the
caller could specify the sequence numbers for the alternate state
(stop or start) as well as for the installed state (start or stop).
Whereas currently one does:
update-rc.d foo start 75 2 3 4 5 . stop 25 0 1 6 .
one would be able to do:
update-rc.d foo start 75 2 3 4 5 . stop 25 0 1 6 . alt-stop 25 2 3 4 5 .
Then runlevel editors would know that when foo was deactivated
in runlevel 2 its K symlink in rc2.d/ should have sequence number
25.
The alternative sequence numbers could be recorded by creating
symlinks in /var/lib/rc/update/alternate/rc?.d/.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
