mlfh

I actually have my whole home directory like that for that reason haha

bin - executables
dev - development, git projects
doc - documents
etc - symlinks to all the local user configs
med - pictures, music, videos
mnt - usb/sd mountpoints
nfs - nfs mountpoints
smb - smb mountpoints
src - external source code
tmp - desktop

~/dev/, with project/org subdirectories

The feature request includes the phrase "Behind the scenes there would need to be some cryptographic magic," because it's just yet another "I have a sweet idea for an app, bro, I just need you to do the coding for me" pitch.

The project has 766 contributors with pull requests being accepted all the time. That's not a walled garden.

The real challenge facing a kremlin linux fork isn't opposition, it's deciding what to do once they realize there aren't any maternity wards in the kernel they can shoot ballistic missiles at.

Those kids and their families should sue the fuck out of him.

Mom, can we have military alliance?

Mom: we have military alliance at home

Military alliance at home: 🇷🇺🇰🇵🤡

With rootless podman, the internal PUID/PGID being set to 1000 within the container is likely being remapped into your subuid/subgid range (eg, if your /etc/subuid is cyno:100000:65536, id 1000 within the container becomes id 101000 outside of it). You can use podman's --userns=keep-id parameter to map your own host uid 1000 to id 1000 within the container.

Winnipeg

How in the world does propaganda supporting the aims of a right-wing fascist dictator equate to "deviating leftward"?

Forgejo, a Gitea fork used by Codeberg. I chose it because it's got the right balance of features to weight for my small use case, it has FOSS spirit, and it's got a lovely package maintainer for FreeBSD that makes deployment and maintenance easy peasy (thanks Stefan <3).

If you're trying to have password auth be a second layer on top of key auth (requiring a password after connecting with your ssh key), you can add the following to your server's sshd_conf:

AuthenticationMethods "publickey,password"

/dev/sda is the whole raw disk - you typically don't want to directly interact with /dev/sda, unless you are partitioning or overwriting it. There are a few layers between that device and the files:

• raw disk - /dev/sda
• disk partition - /dev/sda1
• luks container - when unlocked, mapped to /dev/mapper/{name}
• ext4 filesystem inside the luks container, mounted somewhere like /mnt, /media, etc

You'll need to find where that ext4 filesystem is mounted, and run the chown command on that. You can run lsblkand see a tree of the above hierarchy, with the ext4 filesystem's mountpount shown in the right-hand column.