Dnia 06-09-2006, śro o godzinie 20:24 +0200, Ralf Ertzinger napisał(a):
The problem is not the RPM database, it's the filesystem. As
long
as you do not have a filesystem that can roll back selected changes
this discussion is rather pointless.
transaction:
echo "mv -f file.bak file" > backlog
mv file file.bak
cp -f file.new file # actual work, this can break
rm -f file.bak backlog
error recovery on next run:
if [ -f backlog ]
sh backlog
fi
Do you know a file system that can't do this?
Lam