Re: UBCD V5.1 beta 1 available for download
Posted: Mon Jul 04, 2011 2:50 am
Victor,
I don't mean to continue with the modification date discussion (as I already said, it's in your hands), but I do want to point out some FACTS.
_Download original zip;
_Extract it;
_Build the CAB archive;
_Copy/Move it to its final location;
_Run the script to build fdubcd.iso.gz;
_Run the script to build ubcd*.iso.
All those steps are NOT changing the modification date of the original files inside the CAB. So the scripts available to the users are not changing the modification date of the original files.
Besides those steps, an additional FACT, contrary to what you are saying, is that NOT "any simple" operation can change the modification date of a file. Some simple operations can change the "access" date, but NOT the "modification" date.
Those are facts.
Searching for "some" tool that “accidentally” is changing modification dates in your system "might" be time consuming. But contrary to your logic that it wouldn't be worth, I would arrive to the opposite conclusion, independently of UBCD.
If something would be changing "modification" dates (not "access" dates) in my system, and this is not intentionally done by me (I don't have real control of it), and I don't even know what exactly is actually causing this changes? I would certainly try to find out what's going on. The minimum I would do is try my best to at least know what is going on in my system that I don't have total control of it. If, after knowing, I can correct it to make it work as I want, then that's even better.
To change modification dates you either open and save a file, or you use special tools/commands. No “simple” operation would change the “modification” date.
My conclusion would be different than yours, and that's fine. That's different from a fact.
If you can avoid/minimize this type of changes in the future, it would make it easier for users to manually update or customize, and to find potential updates.
Thank you.
I don't mean to continue with the modification date discussion (as I already said, it's in your hands), but I do want to point out some FACTS.
_Download original zip;
_Extract it;
_Build the CAB archive;
_Copy/Move it to its final location;
_Run the script to build fdubcd.iso.gz;
_Run the script to build ubcd*.iso.
All those steps are NOT changing the modification date of the original files inside the CAB. So the scripts available to the users are not changing the modification date of the original files.
Besides those steps, an additional FACT, contrary to what you are saying, is that NOT "any simple" operation can change the modification date of a file. Some simple operations can change the "access" date, but NOT the "modification" date.
Those are facts.
Searching for "some" tool that “accidentally” is changing modification dates in your system "might" be time consuming. But contrary to your logic that it wouldn't be worth, I would arrive to the opposite conclusion, independently of UBCD.
If something would be changing "modification" dates (not "access" dates) in my system, and this is not intentionally done by me (I don't have real control of it), and I don't even know what exactly is actually causing this changes? I would certainly try to find out what's going on. The minimum I would do is try my best to at least know what is going on in my system that I don't have total control of it. If, after knowing, I can correct it to make it work as I want, then that's even better.
To change modification dates you either open and save a file, or you use special tools/commands. No “simple” operation would change the “modification” date.
My conclusion would be different than yours, and that's fine. That's different from a fact.
If you can avoid/minimize this type of changes in the future, it would make it easier for users to manually update or customize, and to find potential updates.
Thank you.