Finally. This was what was keeping me from using ntfs on Linux
this post was submitted on 05 Dec 2025
83 points (100.0% liked)
Linux
10610 readers
619 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
The last time I had a time zone issue was tomorrow and I still can't figure out how I got there
What's the weather like, down then? I've got plans for the weekend.
I cant imagine that being terribly useful but I'm sure now that I've said it some one will come up with a reason for why I'm wrong.
I set the timestamps of my music to its original release date, so that I can sort it chronologically... OK, I don't actually do that, but now I'm tempted
I was having an anxiety attack for a second.
Seriously though, what are the most common use cases here?
Having the original UNIX source code with fully preserved timestamps?
Yeah I thought of something like that. Something you would pull off of an original tape archive. (An actual tar.) But then why would you put it on ntfs? 🤷
It may have taken a while, but the Year of the Linux Desktop has finally arrived in 1969!
Won't switching from an unsigned 64-bit integer to a signed one of the same size effectively halve how far into the future they can handle dates, exhausting it in 2038?
The 2038 problem is from using a 32 bit int
You're right, I was thinking about 32-bit timestamps. Definitely not an issue for 64-bits.
Hundreds of billions of years should be sufficient t
Won't somebody think of the Eloi?
You only need one sign bit right? So I think you are only losing 1 bit. Not 32.
Very cool for archival work!