I think the gentoo install guide will be helpful for this chrooting…
I think the gentoo install guide will be helpful for this chrooting…
The bad practise would be to entirely disable IPv6. #ShittySysAdmin
Surely a 1:1 emulator would just run DRM as expected and it would never know… Feels like it may stop day1 piracy via emulators but anything beyond I’m sure would be patched.
This is the most confusing and awesome message I’ve ever had.
Exactly, people seem to think the Rocky/CIQ contract with NASA was the breaker but that was peanuts, we all know it was Oracle.
You also have Teams for Linux which is compatible with Microsoft Teams (Work)but no longer supported. It however isn’t compatible with Microsoft Teams (Personal) but if you try to use Microsoft Teams on Linux for personal use, it tells you to install the now non-existant Teams for Linux that only works with Microsoft Teams (Work).
There’s also two different versions of logging out in Teams for Linux, Logout and Log Out. Both of which log you out but only one lets you log in as a different user.
Don’t get me started with the Microsoft Teams PWA that is now the “way to use Teams on Linux” but isn’t the Teams PWA that installs if you try the normal way…
All hail Microsoft Teams! At least I can stream the games I’m playing to my work meetings so people know I’m skiving.
It’s for work and that’s all…
So my current experience is Lutris-GE-Proton8 doesn’t work properly with all GOG installers and it just gives black flickering… However I used to have great success with Lutris.
ZFS is great but I wouldn’t recommend it for single volume setups. I’ve never lost data with it but the parity has always been the saviour.
Never used BTRFS.
I avoid XFS due to performance reasons as most my systems are comprised of many smaller files which XFS isn’t great for. But the usage I’ve had with it, it’s been great
EXT4 is always my go-to for normal usage. Unless I need to be supporting older machines then it’s ext2/3.
Ext4 with backups
I use the standard system syslog with logrotate every 7 days with 1 month of gzip archive.
However on production systems, I run a central rsyslog server which archives once a week and a year of archives. Considering ELK in the future but for simple retention syslog is fine.
Most people have some compilation tools installed on a binary based Linux, the tool chain yes would increase the surface too but being able to entirely remove specific parts of the os or say kernel code that is entirely unused reduces your surface. You can’t expoilt code that isn’t there.
Because you can compile parts out of many programs and suites; you can also change dependencies, such as never including audio support or MP3 libs for anything. Sure it means no sound but if you’re on a system without speakers then it’s no real loss and you’ve reduced your attack surface.
Maybe try forcing only IPv4 connections for the traffic you want to keep private?
Your biggest leak maybe IPv6 DNS which is probably not that big of a deal really…