On Jan 25, 2014, at 9:46 AM, Tomasz Torcz <to...@pipebreaker.pl> wrote:
> On Fri, Jan 24, 2014 at 03:10:04PM -0700, Chris Murphy wrote: >> >> Another possible case it's /etc/ where the either a package or the user could >> make changes during the update. Btrfs allows per file snapshots with cp >> --reflink so there might be a way to carve the snapshot with a scalpel but I >> prefer doing it with subvolume granularity. Plus that granularity translates >> to >> LVM. > > Note that this situation is perfectly handled by Offline Updates. > After reboot, there aren't collateral changes to filesystem, only > upgrade-related > ones. So if there's a need for revert, the previous state is clearly defined. I don't follow this. The realization an update is bad doesn't necessarily occur right away. So we still need a way to separate system domain vs user domain, at least, so that system files are rolled back separately from user files. Chris Murphy -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
