• mossberg590@lemmy.world
    link
    fedilink
    arrow-up
    74
    ·
    2 months ago

    Real sys admins know this pain (rm suffers no fools) and accept the consequences of recovering from backups as pennance. No backups? Then you aren’t really a sys admin then, are you?

    • AspieEgg@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      35
      ·
      2 months ago

      Once I had to restore an entire organization from shadow copies because the IT director didn’t believe in off-site backups or using endpoint protection. The whole network got a ransomware that included the backups, but did not include the shadow copies on the main file server.

      At least I got to help them build a disaster recovery procedure, and pick out a new EDR.

    • betterdeadthanreddit@lemmy.world
      link
      fedilink
      arrow-up
      13
      ·
      2 months ago

      Next time I’m about to criticize the judgement of a video game boss for having an exposed weak point with a neon orange glow, I’ll think about a sysadmin with no backups. Stupidity adds realism.

    • undefinedTruth@lemmy.zip
      link
      fedilink
      arrow-up
      9
      ·
      2 months ago

      The best part is when you do something like rm path/to/dir/* and after pressing enter you notice there is actually space before the *.

  • JasonDJ@lemmy.zip
    link
    fedilink
    arrow-up
    33
    arrow-down
    1
    ·
    2 months ago

    Don’t forget the dot files and directories. Use sudo in case of trouble…sudo rm -rf .*

    (Don’t actually do this, because some shells will take that to include . and .. recursively)

  • Owl@mander.xyz
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    2 months ago

    US government, people

    They probably dragged a shared folder in the bin on windows or something

  • mlg@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    2 months ago

    shred is what you should be using if you really want to destroy a file, but I’m actually not sure that works well on all filesystems.

    I’m pretty sure FAT32 and NTFS leave behind partial file artifacts when you edit/append data, and especially when you physically move it around.

    It just seems inevitable you’ll leave behind deleted blocks with data, which only a fulle drive wipe would guarantee removal.