Conversation

Notices

1. Embed this notice
   Paul Sutton (zleap@qoto.org)'s status on Tuesday, 31-Dec-2024 23:16:14 JST Paul Sutton

   • PonderStibbons
   • Bez Lightyear

   @PonderStibbons @Bez_Lightyear

   I think we are pretty safe then as most distros are moving away from 32 bit

   • Embed this notice
     Paul Sutton (zleap@qoto.org)'s status on Wednesday, 01-Jan-2025 03:46:19 JST Paul Sutton

     in reply to

     • PonderStibbons
     • Bez Lightyear
     • Simon Hewison

     @zymurgic @PonderStibbons @Bez_Lightyear

     Good point

   • Embed this notice
     Simon Hewison (zymurgic@mastodon.online)'s status on Wednesday, 01-Jan-2025 03:46:20 JST Simon Hewison

     in reply to

     • PonderStibbons
     • Bez Lightyear

     @zleap @PonderStibbons @Bez_Lightyear but things like filesystem timestamps might still be an issue, or archive timestamps, and a shedload of proprietary file formats and embedded data structures that just used ctime back in the day.

   • Embed this notice
     Paul Sutton (zleap@qoto.org)'s status on Wednesday, 01-Jan-2025 08:20:28 JST Paul Sutton

     in reply to

     • PonderStibbons
     • Bez Lightyear
     • Simon Hewison

     @zymurgic @PonderStibbons @Bez_Lightyear

     I think i can use the touch command to adjust the time / date on files, so if I create a file on a 32 bit system, copy it over to a 64 bit system would that create a 64 bit time stamp or would using touch to do that also change it from 32 to 64 bit.

     Or does that not make sense.