Make a separate home partition, and make fs BTRFS, having subvolune of root system may be tricky for formatting
BCsven
joined 2 years ago
In the BIOS is secure boot enabled? If it is it is easier to install Linux with secure boot disabled. If it isn't that, then could be a hardware bug Linux lite can't deal with. Had that with Ubuntu on one laptop, while RPM distros worked fine
Ubuntu made Linux easily accessible to anyone, so you are probably right.
For the enterprise stuff we work with only REL and SUSE are certified to install on, and work with the software. OpenSUSE works too because of the shared binaries with SUSE
We see SUSE and REL at corps and enterprises, not so much Ubuntu. None offer something like GRID though. Central management tool for Admins to deploy all systems equally from central location, with dashboard view, without having to run scripts or autoYAST to keep systems the same
Wireguard might be what you want. You connect to your remote machine ( assume it is at home). You can setup what traffic goes over wireguard (some or all). On your home machine you can run port forward command and masquerading command once connected on home machine so that you have full lan access too. It is described in the wireguard setup docs.
NVidia has worked great for me, even RTX shading looked good.
Ha. My young coworker said "wow you really know this software in depth, how long have you used it?" me: meh 26 years. He was like "dude that is longer than I have been alive"
Depends how far you want to keep going back...English talking about Russia and Ukraine like they don't still occupy most of Wales
Yeah it definitely is a pain for adding multiple machines.
I can't offer technical network advice on vps headscale; Personally I'm not confident in my network skills. I would be more inclined to go through the pain of manually setting up wireguard instead of having a tailscale or headscale service-- and skipping the middleman so to speak.
Edit: setting up a new system this month, Tumbleweed has moved to SE Linux Enforcing as default. It provided some ssh and samba challenges at first until I learned about setting SEL policies. So maybe hardening with SE Linux would also be smart. For example I could SSH remotely into my machine but due to policies being locked down I could not run user bash, or even see contents of the home folder.
You are welcome. Secure Boot does work on many distros, but it is extra steps, and when the kernel modules update and you often have to reenroll the keys. It is really not worth it unless you are a high profile target where somebody wants to maliciously alter your OS.