Conversation

Notices

1. Phantasm (phnt@fluffytail.org)'s status on Sunday, 29-Sep-2024 17:53:35 JST Phantasm

   • COOL_FREE_RINGTONES
   • iced quinnsmas :blobcatsanta:
   • 一色いろは :blobcatnomcookie2:
   • Angry Sun
   @sun @icedquinn @wzqtparor @s8n It's not like systemd devs really care about new versions being stable. The recent tmpfiles fiasco convinced me that the only truly usable systemd versions are those that are few years old.
   • † top dog :pedomustdie: likes this.
   • Phantasm (phnt@fluffytail.org)'s status on Sunday, 29-Sep-2024 18:20:27 JST Phantasm

     in reply to

     • COOL_FREE_RINGTONES
     • iced quinnsmas :blobcatsanta:
     • 一色いろは :blobcatnomcookie2:
     • Angry Sun
     @icedquinn @s8n @sun @wzqtparor Forgot the link: https://github.com/systemd/systemd/issues/33349
     † top dog :pedomustdie: likes this.
   • Phantasm (phnt@fluffytail.org)'s status on Sunday, 29-Sep-2024 18:20:28 JST Phantasm

     in reply to

     • COOL_FREE_RINGTONES
     • iced quinnsmas :blobcatsanta:
     • 一色いろは :blobcatnomcookie2:
     • Angry Sun
     @icedquinn @wzqtparor @s8n @sun No, they pulled the Windows 10 Creators update moment where they deleted /home directories if a user ran one of three cleanup commands for systemd-tmpfiles.d.
     
     That was caused by badly written documentation, but what's even worse about this is that one systemd maintainer (Debian dev) actively said that this is the intended behavior, closed few MRs that fixed some of it and downplayed the issue as social media drama created by well known trolls.
     
     The thing where they delete /var/tmp content on a timer is a different issue in some distributions that implemented it.
   • iced quinnsmas :blobcatsanta: (icedquinn@blob.cat)'s status on Sunday, 29-Sep-2024 18:20:29 JST iced quinnsmas :blobcatsanta:

     in reply to

     • COOL_FREE_RINGTONES
     • 一色いろは :blobcatnomcookie2:
     • Angry Sun
     @phnt @wzqtparor @s8n @sun they fucked up /tmp?
     
     (i've been using void >3 years)