You only back or-order to restore - How do you fully restore and incremental backup if you loose the first file? Scott
Carlos E. R. wrote: > > The Sunday 2007-05-13 at 08:17 +1000, Registration Account wrote: > > > I have raised a bug because the current system back in yast only offers > > an incremental backup - so if you loose the first achieve your stuffed. > > I don't understand this sentence... could you clarify, please? > > > The reply came back and described it as a Hugh code re-write within Yast > > would that be "huge"? > > > and it was just a font end based on ---I forgot: I suggested that the > > new front end should be written around CPIO . The bug is now Assigned > > for a LATER status.. - Cross you fingers everyone > > > I have not used yast backup in a long time. I did study it, and I have a > script somewhere that reproduces it's capability somehow. > > It was based on the rpm command ability to generate a list of files that > are included in the rpm database, but which were later on modified; > parsing that list it generates a backup of those files in a modified tar > gz format (one tgz per package in a bigger tar, I think). If you combine > this with autoyast, you can recreate the system part of an install, > storing just the files that were modified. > > The snag is that new configuration files that are not in any rpm are not > stored either, unless you tell it to store all files not in rpms - in > which case the backup can be huge if you forget to tell it not to include > home etcetera - and you need enough space to keep a temporary > uncompressed > copy of all. > > Not very usable, but that was two years ago, I don't know wht they have > improved on it. > > I find all backups programs I try in linux to be lacking a lot. > > > PS. Yes, I also think cpio would be better than tgz. Much safer. There > was > a cute backup script inlcuded in the distro around version 7 or 8, using > cpio. > >
smime.p7s
Description: S/MIME Cryptographic Signature
