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

help-circle


  • If you’re scared to do rm -rf, do something else that lets you inspect the entire batch of deletions first. Such as:

    find .git ! -type d -print0 | xargs -0 -n1 echo rm -fv

    This will print out all the rm -fv commands that would be run. It’s basically rm -rf --dry-run, but rm doesn’t have that common option. Once you’ve verified that that’s what you want to do, run it again without echo to do the actual deletion. If you’re scared of having that in your history, either use a full path for .git, or prepend a space to the non-echo version of the command to make it avoid showing up in your shell history (assuming you have ignorespace in your HISTCONTROL env var)

    I use this xargs echo pattern a lot when I’m crafting commands that are potentially destructive or change lots of things.







  • I have been using ubiquiti for years, and I would strongly caution against using them. They are forcing some devices to sign on to ubiquity cloud and synchronize with their cloud services, and are forcing those sign ins to use MFA. I really miss the ubiquity from 2020, where it was all local. Next time I upgrade my gear, I will probably not buy an ubiquiti router/gateway.

    Also the upgrade process from Usg to dream router was awful. Also they don’t let you run unifi in docker with a dream router, you are forced to run it on-device.











  • As many have pointed out, you don’t know that there is not a back door in your software.

    One way to defend against such an unknown is to have a method of quickly reinstalling your system, so if you ever suspect you have been compromised you can reload your OS from scratch and reconfigure it with minimal fuss. This is one reason I recommend folks learn one of the configuration management systems like ansible or puppet, and use those to configure your Linux servers. Having config management also helps you recover anfter unexpected hardware failures.

    Defense is done in layers. No one layer will protect you 100%. Build up several layers that you trust and understand.


  • friend_of_satan@lemmy.worldtoLinux@lemmy.mlnon-Euclidean filesystem
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    3 months ago

    This makes sense. When you use a copy-on-write block device, it is doing things below the level of the filesystem, so you have to use cow-aware tools to get an accurate view of your used disk space. For example, if you have two files that are 100% deduplicated at the cow-block level, they would show up as different inodes on the filesystem and would appear as using twice the space in the filesystem as they do on the block device. Same would go for snapshots and compressed blocks.

    See also: https://www.ctrl.blog/entry/file-cloning.html