[opensuse] System Installation Datestamp
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there a particular file that can be used to establish either the original system installation date, or the distribution datestamp that can be used distinguish between files that were part of the original installation and those that have been changed since? I want to avoid having to do this on a file by file basis. - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHLadqasN0sSnLmgIRAinDAKCFEBn5rYD6XPVRIMUdUH/bYtfd5gCfVTq/ ykYOUopwPF1zzlOhuVMPJg8= =8zxJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 G T Smith wrote:
Is there a particular file that can be used to establish either the original system installation date, or the distribution datestamp that can be used distinguish between files that were part of the original installation and those that have been changed since?
I want to avoid having to do this on a file by file basis.
There's always the timestamp on /etc/issue or /etc/SuSE-release... But out of curiosity, what are you doing that something like tripwire or indeed the rpm database itself can't? - -- http://www.DonAssad.com jabber ID: josef.assad@gmail.com Please consider the environment; do you really need to print out this e-mail? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHLbx9Fcf72sjD2+QRAjk1AJwMSQr4oIMfP6vonQb7auJJ8jgeAwCfVQOS PItzR1E6L16OJdyvh52GS+0= =SkRa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Josef Assad wrote:
G T Smith wrote:
Is there a particular file that can be used to establish either the original system installation date, or the distribution datestamp that can be used distinguish between files that were part of the original installation and those that have been changed since?
I want to avoid having to do this on a file by file basis.
There's always the timestamp on /etc/issue or /etc/SuSE-release...
But out of curiosity, what are you doing that something like tripwire or indeed the rpm database itself can't?
I am writing something that essentially will do a multi-volume data archive/backup/migration to DVD. I have looked at dar and rsync and neither really do what I am essentially aiming for.. Tripwire does something very different. RPM database use adds some complexity I would prefer to sidestep, and as I am mainly interested in data related, not application related changes probably would not be helpful. Some data files are created during installation and with possible exception of security certificates, I can see no useful purpose in archiving them if they are never modified, but I am bit interested in identifying how big an impact excluding these would make on archive size (and creation times)... /etc/issue looks promising but as some files are modified during installation (and by the looks of it after the creation of /etc/issue) results using this would need to be used with caution. Thanks... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHLdgGasN0sSnLmgIRAjGLAKDrXnBBgpiHcAkvwzKdljzt632sGgCdGnFK M5UTZ1IplNDM33Ah4Zr8Eks= =TZKm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 04 November 2007 03:05, G T Smith wrote:
Is there a particular file that can be used to establish either the original system installation date, or the distribution datestamp that can be used distinguish between files that were part of the original installation and those that have been changed since?
The RPM database includes an exhaustive list of the files installed and their original checksums, so it can be used to validate existing files, find missing ones and by listing all the files installed, allow you to determine which files were during subsequent operation of the system.
I want to avoid having to do this on a file by file basis.
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Randall R Schulz wrote:
On Sunday 04 November 2007 03:05, G T Smith wrote:
Is there a particular file that can be used to establish either the original system installation date, or the distribution datestamp that can be used distinguish between files that were part of the original installation and those that have been changed since?
The RPM database includes an exhaustive list of the files installed and their original checksums, so it can be used to validate existing files, find missing ones and by listing all the files installed, allow you to determine which files were during subsequent operation of the system.
I want to avoid having to do this on a file by file basis.
Randall Schulz
The RPM database is more than adequate for tracking application installation. At some point I intend to look at this for application installation snapshots. I have looked at the work being done on this elsewhere, and I cannot help thinking there must be a simpler way of doing that with the information in the RPM database (if someone has not done this already). In this case, and at this point I am more interested in data files, and working out whether it would be useful to exclude unchanged RPM installed data files from an archiving process. - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHLei8asN0sSnLmgIRAnLvAKCGjUmzH8cCuLzQwTzBWUbRJw+wjgCg02+P KKENYKeK4RkVKiTtEtUeWxw= =Gbgn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 04 November 2007 07:43, G T Smith wrote:
...
In this case, and at this point I am more interested in data files, and working out whether it would be useful to exclude unchanged RPM installed data files from an archiving process.
Why don't you simply segregate your use of the file system so that your data files never reside in the same place (same directory or hierarchy) as those that constitute installed software? Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Randall R Schulz wrote:
On Sunday 04 November 2007 07:43, G T Smith wrote:
...
In this case, and at this point I am more interested in data files, and working out whether it would be useful to exclude unchanged RPM installed data files from an archiving process.
Why don't you simply segregate your use of the file system so that your data files never reside in the same place (same directory or hierarchy) as those that constitute installed software?
Randall Schulz
Data files include configuration files... and some of these appear in some damn odd places... It would be useful if everything was kept under /etc configuration data or /home for user data but /var and /opt pick up fair bit of data related stuff as well, (e.g. DNS and mysql data is usually kept under /var) putting things kept here in non-standard locations is probably not wise, therefore it is not something one can really make a general assumption about. One can also accumulates a fair bit in various ~/. dirs and files under home directories some of which are rarely (if at all) modified which further adds to the mix... So in essence it is not that simple... and as I said I am more interested at this stage in working out whether it would be a useful thing to do, before I spend time trying to implement it..., if it offers no tangible benefit it will not be done... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHLf/0asN0sSnLmgIRAgo0AKCjmnMK5d5qDWXr50TA1Cb0gzOoYACg7Rts Dk7ag/spQ0Jf9cU48ZWrVu4= =0mzQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 04 November 2007 09:23, G T Smith wrote:
Randall R Schulz wrote:
On Sunday 04 November 2007 07:43, G T Smith wrote:
...
In this case, and at this point I am more interested in data files, and working out whether it would be useful to exclude unchanged RPM installed data files from an archiving process.
Why don't you simply segregate your use of the file system so that your data files never reside in the same place (same directory or hierarchy) as those that constitute installed software?
Randall Schulz
Data files include configuration files... and some of these appear in some damn odd places...
Well, if that's your definition... Use the RPM database to identify any RPM-originating file that has changed (based on either time or MD5 sum) and include them in your list of "data files." I guess that still leaves any file created by an RPM post-installation script—or are those listed in the RPM's payload file list, too?
...
So in essence it is not that simple... and as I said I am more interested at this stage in working out whether it would be a useful thing to do, before I spend time trying to implement it..., if it offers no tangible benefit it will not be done...
Why are you making it so difficult? Back up the entire system and be done with it. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Randall R Schulz wrote:
On Sunday 04 November 2007 09:23, G T Smith wrote:
Randall R Schulz wrote:
On Sunday 04 November 2007 07:43, G T Smith wrote:
...
...
So in essence it is not that simple... and as I said I am more interested at this stage in working out whether it would be a useful thing to do, before I spend time trying to implement it..., if it offers no tangible benefit it will not be done...
Why are you making it so difficult? Back up the entire system and be done with it.
Randall Schulz
I am more interesting in archiving (emphasis on archiving not backup, an archive can be used as a backup, but a backup is not an archive) data files to removable media. In the longer term I will be looking at data migration as part of a data management strategy. Backing up everything in sight is really only OK for disaster recovery on the same machine (a backup which I currently do), but is not a lot of good when the file you use once every 6 months or so gets crocked for some reason and is now the one in your current backup set. Or you really need an older version of the same file, (true CVS and subversion can do this but they are more geared toward development work). The approach can be used for backup, but is intended for a lot more, there does come a time when the volume of data elements accumulated makes it difficult to see the trees for the forest. (My current main backup involves approx 150,000 files which is quite modest compared to what some people can accumulate). The other interesting issue is mail archiving... but that is a different story :-) - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHLhKQasN0sSnLmgIRAnXUAKDA9zIPRnyPSj8NjQ1rvMdH4rZkkgCeKzoJ CJ+QCeZp8eIdJy5C7wM2u1Q= =GGtR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
G T Smith -
Josef Assad -
Randall R Schulz