• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle

  • …(it is kinda like a bomb after all)…

    WAT? I’ve never heard a UPS referred to as “kinda like a bomb” before.

    Keep your UPS maintained, replace the batteries when they age out, and it will be fine. If your UPS supports automated self-tests, use them.

    My employer has UPS units spread all over the region we operate in, and we don’t have any issues, despite leaving them mostly unattended for years. I have several in my house and I’ve never given them a second thought aside from battery replacements.





  • UID_Zero@infosec.pubtoLinux@lemmy.mlxfsdump questions
    link
    fedilink
    English
    arrow-up
    2
    ·
    5 months ago

    I read the man page, but I didn’t see the answer to your question in there.

    I am assuming that it would only dump the root filesystem in your example. Other mounted filesystems like /home or /media, if they’re separate filesystems, probably aren’t included. You’d have to run a separate dump for each one.

    Best option to find out is to try it and see what happens. No better way to learn than by doing.




  • It’s a long shot, but I hope that they keep the exposure notification framework and work with the CDC/appropriate orgs around the world to make it a generic exposure notification. The technical feature is impressive, and the usefulness (with proper adoption) would be high for the various occasions where other communicable diseases pop up. It seems easy enough to have a generic app to add the various diseases and their incubation/transmission windows to allow others to be notified.

    But, because people are whiny fucks, it’ll die and we’ll be in a rush to reimplement it for the next thing that comes up.

    Even if it did exist in an ideal state, people would still not use it, because people suck.



  • It’s not that it’s deleted automatically. If you define deleting as “not being referenced by the file system,” then it’s deleted as soon as it’s unlinked.

    Fun story - create a big file, and hold it open in an application. Unlink the file. Then compare the output of du and df for the mount point the file was on. It will differ until the app closes and the inode of the file is finally freed.