Systemd 215 Works On Factory Reset, DHCPv4 Server Support

[rob11311]

The use-case for these features, if I understand it correctly, is "kiosk mode", where the system is shipped ready for production and just needs to process information that is either fixed (like a real info kiosk) or that is accessed from other means, e.g. a node on a map-reduce large deployment. You feed it data and the task, it processes it and returns/forwards it somewhere else (maybe even to a Network-Attached Storage)

Stateless, lets you auto generate and deploy new services in a VM for example, based off a standard virtual disks. Things like user info, are stored on a server in network. Lennart did mention that a few files in /etc would need configuring; but the point is you can have /tmp & /var on something like a RAM disk which is just discarded when the instance is not required.

Along time ago in the 90's I had a couple of standard deployments for SunOS4 workstations and small servers, which I'd boot diskless, then install from filesystem images, then tailor with a few scripts and allow the new machine to update itself with latest patches and local software updates.

Big data centre deployments, need to solve issues like this. With "same memory" pages shared between different VM instances to conserve memory, there's a gain to maximise what's identical in each VM, allowing COW to handle real differences between the running systems.

[Pajn]

Why should I have a DHCP server in a INIT SYSTEM?

[Teho]

Why should I have a DHCP server in a INIT SYSTEM?

The DHCP server isn't part of the init system. It's part of systemd-networkd.

[Pajn]

The DHCP server isn't part of the init system. It's part of systemd-networkd.

So SystemD isn't an init system?

[Teho]

So SystemD isn't an init system?

systemd is an ubrella project that includes among other things a init system by the same name. It's nowadays relatively small part of the entire project and calling systemd, the project, an init system is misleading at best. It's a set of building blocks to build an operating system from or a core os.

[doom_Oo7]

systemd is an ubrella project that includes among other things a init system by the same name. It's nowadays relatively small part of the entire project and calling systemd, the project, an init system is misleading at best. It's a set of building blocks to build an operating system from or a core os.

They should just rename it to systemd-init so that everybody would understand.

[chinoto]

They should just rename it to systemd-init so that everybody would understand.

Wonderful idea, why don't you go ahead and contact whoever is in charge of that? It's a great way to contribute, even if it isn't code or a bug report (I guess you could say it is in a way).

[DrYak]

Stateless, lets you auto generate and deploy new services in a VM for example, based off a standard virtual disks. Things like user info, are stored on a server in network.

It also makes possible, when combined with LXC and all the facilities that systemd has for lxc, to create very light-weight and quickly initiated containers.
Think about a way to quickly jail anything you want inside a separate chroot. (like jails, etc.)

Excpet that, thanks to systemd, you get that chroot completely filled up and indistinguishable from the inside from any actual machine.

You don't trust skype ? These kind of facilities in systemd will create quickly a stateless linux container in which to run your skype. you only keep your skype installation and skype configuration, everything is ephermal single-use throw away environment.

[haplo602]

The problem with using a snapshot to restore a system to a pristine state is, that you thereby also looses all security updates and all packages added or removed since.( you also need extra disk space, a problem on embedded devices). A Factory Reset may keep all the binaries in /usr (and can verify them cryptographically to be in a pristine state), so the system remains secure at all times.

Factory Resets (FR) as feature in it self isn't so important for individual people running a traditional desktop system, though a handy feature nonetheless. But the changes needed to get a stateless system are beneficial to all. It will make Linux a more robust system, especially when it comes to system upgrades and installations.

There are +100.000.000 devices running Linux (not counting Android and pc's), from routers, NAS', SmartTVs, Navigation and entertainment systems etc. Such systems can really benefit from a standard, easy way to do a Factory Reset.

Factory Resets, Reproducible Systems, Stateless Systems, Verifiable Systems, are now potentially possible because of Systemd. There are however still a long way to go to actually implement these features in distros, but when that work is done, Linux will be even better that it is now.

Poettering has a good overview here:
http://0pointer.de/blog/projects/

Since when would embedded systems where space is usualy a premium item use a bloated thing like systemd is quickly heading to ?

It is either a generaly used and usefull feature, ot it should have a dedicated implementation. I still fail to see the benefit of integrating this feature into systemd. Any kind of reproducible system has 2 requirements:

1. Non-volatile and non-modifiable storage for base system (i.e. read-only /usr)
2. Appendable configartion area (you simply cut the addon modifications during a reset)

Systemd does not serve either ....

[Luke_Wolf]

They should just rename it to systemd-init so that everybody would understand.

+1 on suggesting you go tell them that as it would solve any legitimate misunderstandings.