Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I want to tar -cf then tar -xf to recover a directory with the orginal
timestamps on subdirectories. I get "... cannot use utime.." error message in the tar -xf procedure, and directories are recovered, but with new timestamps. I want the original ones. Individual file timestamps are recovered, however.
I should have said that I am using SUSE 10 but it is running under VMWare box which is under Windows XP, using NTFS. A Windows person said that this NTFS will not allow copy preserving directory timestamps, so maybe this is inherited by the Linux system??
I don't think that has anything to do with the "underlying" NTFS,
VMWare doesn't use NTFS structures but operates on an image-file
that is (internally) file-system agnostic to its host.
tar actually preserves time-stamps by default. This may fail if
you're extracting to a file-system that's not Linux-native.
A better way to word my question might have been - was the time that was being preserved the same time that was being reported in the listing? Since one is atime and the other ctime, the answer is no - I was reading the wrong timestamp.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.