Announcement

Collapse
No announcement yet.

SystemD/Lennard Pottering hate thread

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Originally posted by RealNC View Post
    Who cares what the init system is. If the machine boots up and works, I don't give a damn.
    I don't care what the init is per se, as long as its fast.

    From power button to usable desktop, if it takes longer than 10 seconds then it is by definition broke and SOMEONE BETTER DAMN WELL FIX IT!!!

    Comment


    • #12
      Originally posted by halfmanhalfamazing View Post
      I don't care what the init is per se, as long as its fast.

      From power button to usable desktop, if it takes longer than 10 seconds then it is by definition broke and SOMEONE BETTER DAMN WELL FIX IT!!!
      there are more then two init systems that can do that

      also you would want to remove bloat if you want something started faster
      Last edited by gens; 06 March 2014, 08:54 PM.

      Comment


      • #13
        The faster boot of systemd isn't its main feature by any stretch though.

        Comment


        • #14
          Originally posted by xeekei View Post
          The faster boot of systemd isn't its main feature by any stretch though.
          systemd doesn't have a main feature, it has all dem features

          Comment


          • #15
            Originally posted by gens View Post
            systemd doesn't have a main feature, it has all dem features
            I think you confuse the word "main" with "sole". Otherwise your sentence doesn't make sense.

            Comment


            • #16
              Originally posted by xeekei View Post
              I think you confuse the word "main" with "sole". Otherwise your sentence doesn't make sense.
              it makes perfect sense
              no "feature" was ever touted as being main
              the actual init part is the most prominent one

              but tell me, what do you think is the main feature

              Comment


              • #17
                Originally posted by gens View Post
                it makes perfect sense
                no "feature" was ever touted as being main
                the actual init part is the most prominent one

                but tell me, what do you think is the main feature
                Reliable management of services, starting/restarting etc.

                Comment


                • #18
                  Originally posted by gens View Post
                  no "feature" was ever touted as being main
                  Nice bit of trolling, but the answer is quite obvious - the "feature" is bringing up user space faster. From Lennart's blog on the subject:

                  As mentioned, the central responsibility of an init system is to bring up userspace. And a good init system does that fast. Unfortunately, the traditional SysV init system was not particularly fast.

                  For a fast and efficient boot-up two things are crucial:

                  To start less.
                  And to start more in parallel.

                  What does that mean? Starting less means starting fewer services or deferring the starting of services until they are actually needed. There are some services where we know that they will be required sooner or later (syslog, D-Bus system bus, etc.), but for many others this isn't the case. For example, bluetoothd does not need to be running unless a bluetooth dongle is actually plugged in or an application wants to talk to its D-Bus interfaces. Same for a printing system: unless the machine physically is connected to a printer, or an application wants to print something, there is no need to run a printing daemon such as CUPS. Avahi: if the machine is not connected to a network, there is no need to run Avahi, unless some application wants to use its APIs. And even SSH: as long as nobody wants to contact your machine there is no need to run it, as long as it is then started on the first connection. (And admit it, on most machines where sshd might be listening somebody connects to it only every other month or so.)

                  Starting more in parallel means that if we have to run something, we should not serialize its start-up (as sysvinit does), but run it all at the same time, so that the available CPU and disk IO bandwidth is maxed out, and hence the overall start-up time minimized.
                  http://0pointer.de/blog/projects/systemd.html

                  Comment


                  • #19
                    Originally posted by xeekei View Post
                    Reliable management of services, starting/restarting etc.
                    are you saying other init systems can not start or restart a service ?
                    or find out if it's running ?

                    Comment


                    • #20
                      Originally posted by andyprough View Post
                      From Lennart's blog on the subject:[/URL]
                      that blog is propaganda


                      this is how documentation should look like


                      did you miss the name of the topic ?


                      also to add
                      socket activation needs every daemon to be patched and is subject to dependency problems (that is why you can't have /usr over NFS)
                      something not written in that "documentation"
                      Last edited by gens; 06 March 2014, 11:49 PM.

                      Comment

                      Working...
                      X