- 06 Aug, 2017 8 commits
-
-
Sean Whitton authored
-
Sean Whitton authored
This is now needed to generate the PS and PDF output.
-
Sean Whitton authored
-
Sean Whitton authored
-
Sean Whitton authored
-
Sean Whitton authored
-
Sean Whitton authored
-
Sean Whitton authored
-
- 05 Aug, 2017 15 commits
-
-
Sean Whitton authored
-
David Bremner authored
this should presumably be customized by a real policy editor
-
David Bremner authored
.txt still needs work
-
Sean Whitton authored
-
Sean Whitton authored
-
Sean Whitton authored
-
Sean Whitton authored
-
Sean Whitton authored
-
David Bremner authored
-
David Bremner authored
-
Sean Whitton authored
-
Sean Whitton authored
-
Sean Whitton authored
-
Sean Whitton authored
-
Sean Whitton authored
-
- 04 Aug, 2017 4 commits
-
-
Sean Whitton authored
-
Sean Whitton authored
-
Sean Whitton authored
-
Sean Whitton authored
-
- 03 Aug, 2017 13 commits
-
-
Sean Whitton authored
-
Sean Whitton authored
There are other things in section 9 that remain to be updated.
-
Sean Whitton authored
-
Sean Whitton authored
-
Sean Whitton authored
Suggested by Holger Levsen.
-
The entire section is specific to sysvinit and already solved by LSB in that case. There's no point in reinventing LSB. Also other init systems handles this in ways that's not at all described here. Just drop the entire section as it gives no practical useful information.
-
In addition to the sysvinit skeleton file also point out where to find systemd integration examples.
-
No idea how long ago this paragraph had any relevance....
-
Slightly reword the paragraph to not sound like anything should be converted (which isn't the normal case these days), rather than just use invoke-rc.d.
-
The intention is to also make sure that eg. it's equally not allowed to directly call 'systemctl <action> <unit>' but maybe the wording can be improved further to more clearly express this. In other words the language is still a bit outdated in this paragraph.
-
Todays init systems calculates a dependency graph (eg. from the dependencies specified in LSB headers) and doesn't go by sequence numbers. See eg. insserv.
-
These days the information in the LSB header is used. Manually specifying/overriding runlevels as a parameter to update-rc.d on command line is even deprecated and a noop stub these days.
-
Get rid of "script" as that doesn't properly describe the equivalent for systems using declarative replacements. Also drop "the" as via update-rc.d you're potentially/likely interfacing with multiple ones at a time. Possibly the word system should be replaced with systems or system(s)?
-