I did some more investigation to see if these errors were significant. Unlike Redhat/Fedora/CentOS, Debian and Ubuntu treat runlevels 2-5 as equivalent, so technically there is no problem here. The first warning about missing LSB information indicates that the init info block is missing from /etc/init.d/webmin. The remaining warnings are just update-rc.d noting that the init scripts are being installed with runlevels different than those specified in the LSB.
I installed chkconfig which displayed the following results:
From the man page,
EXAMPLES
Insert links using the defaults: update-rc.d foobar defaults
The equivalent dependency header would have start and stop
dependencies on $remote_fs and $syslog, and start in
runlevels 2-5 and stop in runlevels 0, 1 and 6.
Equivalent command using explicit argument sets: update-rc.d foobar start 20 2 3 4 5 . stop 20 0 1 6 .
More typical command using explicit argument sets: update-rc.d foobar start 30 2 3 4 5 . stop 70 0 1 6 .
I did some more investigation to see if these errors were significant. Unlike Redhat/ Fedora/ CentOS, Debian and Ubuntu treat runlevels 2-5 as equivalent, so technically there is no problem here. The first warning about missing LSB information indicates that the init info block is missing from /etc/init.d/webmin. The remaining warnings are just update-rc.d noting that the init scripts are being installed with runlevels different than those specified in the LSB.
I installed chkconfig which displayed the following results:
# chkconfig --list webmin confconsole di-live inithooks
webmin 0:off 1:off 2:on 3:off 4:off 5:off 6:off
confconsole 0:off 1:off 2:on 3:off 4:off 5:off 6:off
di-live 0:off 1:off 2:off 3:off 4:off 5:off 6:off S:on
inithooks 0:off 1:off 2:on 3:off 4:off 5:off 6:off
From the man page,
update- rc.d foobar defaults
update- rc.d foobar start 20 2 3 4 5 . stop 20 0 1 6 .
update- rc.d foobar start 30 2 3 4 5 . stop 70 0 1 6 .
EXAMPLES
Insert links using the defaults:
The equivalent dependency header would have start and stop
dependencies on $remote_fs and $syslog, and start in
runlevels 2-5 and stop in runlevels 0, 1 and 6.
Equivalent command using explicit argument sets:
More typical command using explicit argument sets: