• 0 Posts
  • 32 Comments
Joined 1 year ago
Cake day: June 19th, 2023
  • friend_of_satan@lemmy.worldtoAsklemmy@lemmy.ml•Men, are you physically affectionate with other male friends? (eg, hugging, snuggling, playful wrestling, etc). If you aren't, do you wish it was more socially acceptable if it isn't in your culture?English
    20·
    19 days ago

    Hugging, definitely.

    Snuggling, maybe? Like maybe we both fell asleep in the back of a van and ended up snuggling a bit and when we woke up we’re not weirded out by it.

    Wrestling, maybe, but it would probably be with kids or pets around. I can’t remember doing it but I wouldn’t be weirded out by it.

    It wasn’t always this way though. I was raised southern Baptist. Becoming OK with male physical interactions and homosexuality was a journey, and I am much happier with how accepting I am now than when I said I was as a Christian who had this low-key hypocritical “I know the truth of god and accept everybody” while also looking down on sinners.

    I have a gay friend who came to visit me and we went around the city and to a house party and had a great time and then fell asleep in the beach. The next day he said “that was one of the best dates I’ve ever been on” and it caught me off guard because I was just “hanging out”, but if it had been a girl, it would have been a great date, and I thought “ok, sure, it was a ‘date’ with a guy friend and that’s ok.” It was a big step for me.

  • friend_of_satan@lemmy.worldtoLinux@lemmy.ml•Can I remove a git repo without resorting to `rm -rf` ?English
    53·
    23 days ago

    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.

  • friend_of_satan@lemmy.worldtoLinux@lemmy.ml•How do we know if there aren't a bunch of more undetected backdoors?English
    4·
    3 months ago

    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.ml•non-Euclidean filesystemEnglish
    28·
    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