Is basic the right systemd target or should there be others?

[dradetsky]

I'm looking into a way to keep my last working kernel around in Arch Linux, so if an update breaks something I don't have to mess around with the rescue system. So I'll want to copy the bzImage &c to e.g. /boot/prev/vmlinuz-linux, and ensure that its modules are not deleted unless the new kernel boots successfully.

I don't have a very strong understanding of systemd, so this might sound kind of stupid, but: If I understand correctly, the cleanup service will attempt to run once we've successfully reached basic.target, and will not run if we do not reach that target. Which sounds fine except that I'm not totally sure that basic.target will meet the requirements for what every user considers as "booting successfully." Other options include

• multi-user.target
• graphical.target
• boot-complete.target

Admittedly, I don't really understand that last one entirely.

In any case, maybe we should ship other versions of the cleanup service which depend on multi-user or graphical, and the user can enable whichever one best meets his needs.

Then again, I can see how you could make the case that these other versions of the cleanup service belong more in whatever keep-the-last-working-kernel package I find/create, and not here, but maybe not.

[WhyNotHugo]

It should point to default.target. This is usually a symlink. On my setup it's a link to graphical.target, on other is might be a link to multi-user.target, or simply basic.target.