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
It would be useful if update-rc.d were enhanced so that it stored the
configuration that it applies in a database. (This could be a set
of files named like the services.) The database would contain the
"factory default" runlevel configurations for all services. Each
time update-rc.d is run it w
2 matches
Mail list logo