Am 2012-11-26 23:19:08 -0500, Limao Luo schrieb:
In general, should .install files enable systemd service files on
startup by default (even if some custom config may or may not be
required)? Are there any other special considerations when deciding?
[1] provided some info about systemd scripts,
On Tue, Nov 27, 2012 at 9:25 AM, Stefan J. Betz i...@stefan-betz.net wrote:
Never enable any service on install ;-)
+1
Please keep arch passive.
No automated configs, no automated breakage I'll have to search for.
Thank you.
Cheers
mar77i
On 28 Nov 2012 05:13, Martti Kühne mysat...@gmail.com wrote:
On Tue, Nov 27, 2012 at 9:25 AM, Stefan J. Betz i...@stefan-betz.net
wrote:
Never enable any service on install ;-)
+1
Please keep arch passive.
No automated configs, no automated breakage I'll have to search for.
Thank you.
Oon-Ee Ng wrote:
On 28 Nov 2012 05:13, Martti Kühne mysat...@gmail.com wrote:
On Tue, Nov 27, 2012 at 9:25 AM, Stefan J. Betz i...@stefan-betz.net
wrote:
Never enable any service on install ;-)
+1
Please keep arch passive.
No automated configs, no automated breakage I'll have to
In general, should .install files enable systemd service files on
startup by default (even if some custom config may or may not be
required)? Are there any other special considerations when deciding? [1]
provided some info about systemd scripts, but I couldn't find anything
as it relates to
On Mon, Nov 26, 2012 at 9:19 PM, Limao Luo luoli...@gmail.com wrote:
In general, should .install files enable systemd service files on startup by
default (even if some custom config may or may not be required)? Are there
any other special considerations when deciding? [1] provided some info
