Thanks for the info. I will try this if Windows clobbers what I have now.

I meant deb based as in those based on Debian OS…which feeds the other Debian based offshoots. I probably over simplified by original comment, I wasn’t claiming deb package management was the issue, just the relation to Debian base OS being the issue. So whatever the base OS of fedora and SUSE is worked fine (those happen to be RPM packages) maybe Arch may have worked or failed also. The point of it all was , if one fails to install, try another distro, and I my case nothing based off of Debian could deal with the hardware issue

Its not the packages its that whatever Debian built and other derivatives of Debian, used as their base, did not work with that hardware. Trust me I distro hopped a ton to try and get a Debian to work. I didn’t save the error, but however the NON Debian OS WORKED AND WOULD ACKNOWLEDGE THE ERROR ON SCREEN AND MOVE ON.

Sorry did not mean caps, caplock after OS lol.

Also an OS is not just the kernel, its your tools that boot the machine and recognize hardware, and what the OS it told to do with issues. So I assume Debian bug for specific hardware, and non deb distros didn’t have the bug.

I deep dive issues as my job and nature, so trust me when I say a deb derived would not work I tried more than 10+ distros deb based. Only Fedora and SUSE ones worked (because non Debian build) not because of packaging

Yeah, it was some BIOS bug or hardware error that halted Debs, but RPM based would show that it worked around the issue and continued. As a Debian branch whatever was missing in main was probably missing throughout all the derivatives.

I tried every single* deb based distro on a Samsung laptop from 2010. Some installed but would freeze with error mid boot, some deb based refused to install and gave error upfront. I tried fedora and opensuse and they acknowledge the error and moved on.

Whatever hardware or bios bug or error handling problem tripped up the system , it was was prevrlant through all of the Debian Branch.

And No it wasn’t secure boot. That was disabled.

Some hardware doesn’t play well with deb based distros vs rpm based, it would be good to point out if your install is failing with errors that another distro may work

For ssh they both have private and public keys. The server could be at risk of having it’s own private key compromised if somebody breaks in, and vice versa a compromised client can lose its private key. The original wording made it sound like a compromised server would steal client keys.

Also passworded keys are recommended

Only the server should have the private key. Why would other systems have the private key?

Yeah same kind of experience, on Windows 10 her laptop would barely run, it lagged so badly because it is a 2 core Celeron. On Linux it is actually peppy and she can run her zoom meetings and excel stuff, plus browsing. It is comparable speed to my new work laptop with 20 core processor running W11…that’s how bad WindowsOS has become

My home computers and servers are all Linux since 2017, even my work Laptop was because the CAD/CAM software had a Linux version. I have been running W11 for work lately and it is such a terrible user experience. I will be mid productivity mode and the Office Ai.exe kicks and and reduces my brand new machine down to a crawl speed. It happened way too many times and it does nothing to improve what I’m working on. I tried deleting the ai.exe and aimgr.exe, but those get reinstalled after an update, so now I have made two empty text files and renamed them to match the two files, this (so far ) has tricked MS into not reinstalling those files.

But there are so many other janky bullshit things that W11 does that I can’t believe a company the size of MS can release this stuff

This has not been my experience. I’m not on Ubuntu, but OpenSUSE and NixOS. Everything works and operates as expected everytime. The only issue once was nvidia driver updated versions before kernel did and I had to reboot to a previous snapshot and wait a few days till the kernel update was released to work with whatever happened to the driver. But 8 years of a dependable system otherwise

Exactly, my wife struugles with tech. She hated windows and how it did unexpected things that made no sense. I put Linux on her computer, she doesn’t bug me with complaints now since it operates the same every day.

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.

Make a separate home partition, and make fs BTRFS, having subvolune of root system may be tricky for formatting

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

It is marketed as direct windows replacement, so it appears they choose absolute safety, over possible breakage. If that GRID product they tout ever launches it will be great for companies.

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.