1. 10
  1.  

  2. 21

    First they came for the /var/syslog, and I said nothing because I didn’t mind binary logging.

    Then they came for /sbin/init, and I said nothing because I wanted a better init system.

    Then they came for gnome-session, and I said nothing because I don’t use a desktop manager.

    Finally, they came for /boot/grub, and I said nothing, because seriously, fuck grub.

    1. 4

      I think binary logging is my biggest gripe about systemd, that or netctl which has some sinister connection to this whole clusterfuck. I completely agree about grub2 though, it’s like a cruel April Fool’s day joke of editing VERY SPECIFIC files so it can “compile” a steaming pile of crap. Whatever the original grub was called (grub1?) I actually didn’t mind so much but since everything has gone to grub2 I’m sticking to syslinux.

    2. 12

      Some people are probably gonna massively dislike this.

      Another subset of people will probably enjoy it.

      A third just don’t know or care what’s happening.

      Myself, I’m not sure what to think of it.

      1. 10

        I like it (ducks) I had the hardest time with the old system on init and well every time I did something would mean 15-120 minutes of looking up things on wikis and such. Now things are just very consistent. I learned systemd when Arch switched and I really get to do anything by reading the man page or just spamming tab.

      2. 4

        gummiboot is the most simple and easy to use boot manager I can think of. but you’ll be free to use another one with the systemd, if you so choose.

        1. 4

          Isn’t that what they have always said? Looking at the things which were “optional” but became “mandatory” later, I’m not sure whether I should believe it this time.

          1. 5

            That’d be requiring uefi. I think we could assume this wouldn’t happen, would it? Also, what was optional that became mandatory? journald? It was suposed to be mandatory from its origin:

            I am using systemd on an embedded system and am not interested in persistent logging, can I opt out of the journal? No you can’t really. However, what you can do is tell systemd that you don’t want persistent logging, by removing (or not creating in the first place) the /var/log/journal directory, in which case journald will log only to /run/log/journal (which it does in any case during early boot). /run is volatile and lost on reboots, in contrast to /var. On top of that you can configure the maximum disk space the journal may consume to a low value.

            https://docs.google.com/document/pub?id=1IC9yOXj7j6cdLLxWEBAGRL6wl97tFxgjLUEHIX3MSTs

          2. 3

            Sometimes, I have the impression that some software is written for the name alone.

            1. 2

              Would you kindly explain to me where’s the pun? I am not english native

              1. 3

                It’s german. A “boot” is a boat, “gummiboot” is a rubber boat - see the logo for a classic example :).

                http://freedesktop.org/wiki/Software/gummiboot/

                1. 3

                  Huh, that’s cool, I figured it implied that it would keep you clean from having to muck around with all that EFI stuff… boats are pretty nifty too, I suppose.

                  http://www.h-online.com/open/news/item/Gummiboot-is-an-EFI-boot-loader-that-just-works-1628719.html

                2. 1

                  I think it’s a reference to what, as a Canadian, I’d call a “rubber boot” but a Brit might refer to as a Wellington Boot

            2. 3

              Nuke it from orbit–it’s the only way to be sure…