I just discovered this bug, and thought I should provide some comments. I am one of the sysvinit maintainers in Debian, and thus the maintainer of sysv-rc.
First of all, when using the legacy way of ordering init.d scripts, like described with sysv-rc and file-rc in this bug, one need to use _different_ sequence numbers to ensure any given order during boot. Expecting scripts with the same sequence number to run in alphabetic order is not possible, and file-rc is perfectly OK to run them in installation order instead of in alphabetic order. To fix this with file-rc and legacy boot ordering, the sequence number need to be changed for netenv. Next, there are confusing messages in this report. Should netenv run after hostname.sh, or before networking? The title talk about hostname.sh, while the emails in the report talk about networking. I assume both are true, yet find no information about the hostname relation. Assuming the netenv script should execute after hostname and before networking and ifupdown, this header fragment probably make sense for the dependency based boot sequencing: # Required-start: $local_fs hostname # X-Start-Before: $network If it should run after ifupdown and before networking, this fragment should be used instead: # Required-start: $local_fs hostname # Should-Start: ifupdown # X-Start-Before: networking Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
