Alexander GQ Gerasiov wrote: > lvm update this information every time you change lvm partitioning. > When you do so, it stores new configuration in backup and moves old > configuration from backup to archive. On host, where I use lvm > snapshots for every-day backup, I see many of such archives. > > Lets see what is backup files: that's just a _copy_ of metadata, which > could be used in some rear cases. E.g. you lost all your lvm's > metadata. Or to restore the same partitioning on new, replaced drive. > Do we need history for it? Yes (e.g. to restore suddenly deleted > volume), but lvm tracks enough copies of old metadata in archive dir. > So keeping them in git don't needed.
git should automatically notice that the file was renamed from archive to backup, and only save one copy of the file. My question is, what if I deleted my current /etc and used etckeeper to check out a new copy from git. Would lvm transparently recreate those lvm files as needed, or would it be better if the new /etc checkout included them? > And finally cache dir is for temp file where lvm stores some runtime > cache (to not rescan all physical volumes every time user calls lvm). The cache dir definitly seems removable then. > JH> > JH> I wonder why the menudefs.hook isn't put in /var? A symlink in /etc > JH> would allow twm to find it there if nothing else. > I have no idea. May be we need to file a bug? I do, when have some time. It would be better to file a bug than clutter up the default ignores with this, especially since most people don't have twm installed. -- see shy jo
signature.asc
Description: Digital signature
