Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#41899 - [abs] Basic support for systemd factory reset/atomic upgrades
Attached to Project:
Arch Linux
Opened by Pablo Lezaeta (Jristz) - Tuesday, 09 September 2014, 23:24 GMT
Last edited by Dave Reisner (falconindy) - Monday, 15 September 2014, 17:37 GMT
Opened by Pablo Lezaeta (Jristz) - Tuesday, 09 September 2014, 23:24 GMT
Last edited by Dave Reisner (falconindy) - Monday, 15 September 2014, 17:37 GMT
|
DetailsDescription:
Systemd offers a factory reset feature for a while now. See http://0pointer.net/blog/projects/stateless.html for a discussion of the feature. It would be nice if that was simple to use on arch Linux. To support this feature the following changes would be needed on pacman (AFAICT:-): * Move the abs DB (if have or if have planed one) into /usr, maybe with a fallback for the current location in /var. * Move the default abs.conf into /usr/share/factory/etc. * Provide a tempfiles.d to copy those files to /etc if not already there and create the directories pacman needs to function. With that a user should be able to make use of systemd's factory reset. These changes will also help a lot with the atomic update proposal Lennart made recently ( http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html ). Also related pacman feature #41863 |
This task depends upon
Closed by Dave Reisner (falconindy)
Monday, 15 September 2014, 17:37 GMT
Reason for closing: Won't implement
Monday, 15 September 2014, 17:37 GMT
Reason for closing: Won't implement
Related mkinitcpio feature #41900
Bassically with this systemd feature one could return to a previous state for test pruposes like test testing or a new Xorg release and look if break, dump the system or clone it, mainenaince pruposes, fix or change from hard disks (/home and /etc for exsmple) if need using the factory (and /var in another disk), revert changes that break something simpl asking to systemd to revert that file to they factory state, there are unlimited possibilities.
The fact that /etc/abs.conf is on /etc mean that if some user will do the systemd factory reset that will be removed and eliminated. and as I say if some user do modifications to one that file and well want return to the previous state need to be in the location that systemd spect for work.
The /var/abs is populated manually so could be ignored and simply move the abs.conf to where the factory reset/atomic updates need.
[1] https://mailman.archlinux.org/pipermail/arch-general/2014-September/037233.html
[1] http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html
There are more examples as what systemd want.