3 ms·

Have you any information about that with systemd, updates of some software that run as service on the machine, would need now to reset the machine ?? For my,

• sandGorgon 12y ago
  Actually, that is another systemd FUD. SystemD enables stateless systems - now that I think of it, very similar to Docker - by clearing out the /var and /etc directories. Which means that when you reboot the system, it acts as a system reset. This is actually, pretty hard to actually implement and systemd is trying really hard to do this. Imagine being able to build your own private DigitalOcean and able to have pristine machines for a new fleet deployment (possibly even avoiding the stale confidential data issues plaguing DigitalOcean). http://0pointer.net/blog/projects/stateless.html http://0pointer.net/blog/projects/stateless.html
  • thwarted 12y ago
    [stateless] is actually, pretty hard to actually implement and systemd is trying really hard to do this. Support for stateless has existed in RedHat based distributions since at least 2003-2004. I, in fact, used it to run a ~50 seat callcenter using read-only NFS root systems, with a dynamically populated /etc, a decade ago.
    • sandGorgon 12y ago
      And that pretty much encapsulates, what systemd is attempting vs what people think it is attempting. Systemd is not innovating on ideas, but on implementation. How do you make things like service dependencies, stateless systems, etc consistently possible. It is bringing something which was possible only for a person of your skill level, down to mine. I would say it is the same difference between Ubuntu and Arch - idiotproofing the Linux ecosystem.