From 7115b71c353c004dbfe70a0d96012a2213e77405 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Sun, 28 Feb 2016 07:12:18 -0500 Subject: whitespace cleanup --- public/arch-systemd.md | 44 ++++++++++++++++++++++---------------------- 1 file changed, 22 insertions(+), 22 deletions(-) (limited to 'public/arch-systemd.md') diff --git a/public/arch-systemd.md b/public/arch-systemd.md index 3ada087..7f6de00 100644 --- a/public/arch-systemd.md +++ b/public/arch-systemd.md @@ -34,27 +34,27 @@ there is compatibility for the variables that used to be there, but that is going away. [^1]: - *I* don't think it's bloated, but that is the criticism. - Basically, I discount any argument that uses "bloated" without - backing it up. I was trying to say that it takes a lot of heat - for being bloated, and that there is be some truth to that (the - systemd-fsck and syslog comments), but that these claims are - largely unsubstantiated, and more along the lines of "I would have - done it differently". Maybe your ideas are better, but you - haven't written the code. - - I personally don't have an opinion either way about SysV-init vs - systemd. I recently migrated my boxes to systemd, but that was - because the SysV init scripts for NFSv4 in Arch are problematic. I - suppose this is another **advantage** I missed: *people generally - consider systemd "units" to be more robust and easier to write - than SysV "scripts".* - - I'm actually not a fan of either. If I had more time on my hands, - I'd be running a `make`-based init system based on a research - project IBM did a while ago. So I consider myself fairly - objective; my horse isn't in this race. + *I* don't think it's bloated, but that is the criticism. + Basically, I discount any argument that uses "bloated" without + backing it up. I was trying to say that it takes a lot of heat + for being bloated, and that there is be some truth to that (the + systemd-fsck and syslog comments), but that these claims are + largely unsubstantiated, and more along the lines of "I would have + done it differently". Maybe your ideas are better, but you + haven't written the code. + + I personally don't have an opinion either way about SysV-init vs + systemd. I recently migrated my boxes to systemd, but that was + because the SysV init scripts for NFSv4 in Arch are problematic. I + suppose this is another **advantage** I missed: *people generally + consider systemd "units" to be more robust and easier to write + than SysV "scripts".* + + I'm actually not a fan of either. If I had more time on my hands, + I'd be running a `make`-based init system based on a research + project IBM did a while ago. So I consider myself fairly + objective; my horse isn't in this race. [^2]: - You can still have `USEDMRAID`, `USELVM`, `interface`, `address`, - `netmask`, and `gateway`. But those are minor. + You can still have `USEDMRAID`, `USELVM`, `interface`, `address`, + `netmask`, and `gateway`. But those are minor. -- cgit v1.2.3