Uploading a gz source archive to a Git repository is absolutely cursed. Still, looks like a cool project.

I’ll also add that if you do enable SSH and are stupid enough to expose port 22, then at least make sure you have key-based authentication instead of password authentication and keep your keys safe.

I could never get Gnome Network Displays to work, but it’s worth a shot.

Not great. I even got GPU passthrough working once, but you get weird graphics glitches because it’s all being sent over RDP.

I think Cassowary might be better than WinApps, but honestly, at this point, I just gave up on those and just use the VM directly.

When it freeze, after you’ve rebooted it, try running sudo journalctl -p 5 -b -1; you might see something in those logs.

Maybe also open a task manager before you do anything graphics intensive, just to see if there’s a process that rapidly increases its memory usage; while it might not be the cause, I’ve experienced similar freezes when I use all my memory (on a machine with 32GB of RAM).

FYI Don’t use this command. I think it was intended as a joke, but I just want to clarify.

Fun fact: you didn’t have to reinstall; you can actually boot up a live usb and chroot into your install to fix things.

That is kind of awesome.

I wish Debian’s default Grub theme was less ugly; I know I could change it (and I have on other installs, but I’m quite lazy about theming these days. Part of it is I have a laptop that I rely on for college and don’t want to risk any theme glitches, so I keep its Debian install as vanilla as possible.

May I ask what your config was, such as distro, packaging format, and extensions were used? Also, what hardware?

Additionally, what issues specifically were you experiencing specifically? Were sites just loading slowly?

I ask because I’ve used recent versions Firefox on decently old hardware with 4 GB of RAM and 2 cores and had almost no problems. Everything rendered correctly and in a reasonable amount of time. I’d be curious to know why that isn’t happening for you.

May I ask: when did you last try Firefox? There was a period during the 2010s when it has truly horrible performance, but they rolled out some major updates several years ago that greatly improved performance (though wouldn’t call some of the UI changes improvements).

Honestly, every major rendering engine is terrible in some way.

• Blink is resource intensive and has so many non-standard APIs for the sake of Google’s version of “Embrace, Extend, Extinguish”.
• WebKit takes 50 years to support the newest standards.
• Gecko (Firefox) is non-modular and is limited to being used in Firefox, Thunderbird, and forks and Firefox as a result. Its performance is also somewhat worse than Chrome’s, but not noticeable for daily use.

Ultimately, I choose Firefox because its issues are the least annoying to me. I do wish its structure was more community-based and less corporation-eating-its-own-hand, but whatever. So long as Debian sees it fit to keep in its repos, I’ll use it.

Honestly, even those don’t run that horrid for me when I have to use them.

Assuming she hasn’t bought it yet, please research that Yoga first. It might work fine, but it could also end up being a miserable experience.

You can check https://linux-hardware.org/ for the model or a similar one.

No, I mean TinyCore literally would run out of RAM during boot.

Like others have said, Debian probably isn’t a bad idea.

I feel like it would be kind of stupid to run a full-on desktop environment even though technically possible, though - I think this is a good use for IceWM.

Also, at worst, you might have a really low power server.

I think less than 64MB is difficult these days - a few years ago, I was backing up a laptop with 48MB of RAM, and to get a minimal Linux terminal running on it, I had to create a custom Buildroot image and throw it on a CD. TinyCore was too much for it.

A more apt comparison would be using the Windows guest to remote into the Linux host via xorg piping, waypipe, VNC, RDP, etcetera, which conveys your feeling of weirdness while being a closer approximation of what this really does.

It’ll definitely be a difficult undertaking, but I plan on really trying to have a 5.25” bay when I build another PC.

That probably won’t be for a couple more years, though. I’m on a Ryzen 5 2600 and RX 580, and I really don’t do that much intense gaming; a GPU upgrade is tempting so I can actually use ROCm for some casual Blender Cycles renders, though. I hope that the already dismal supply of those 5.25 cases doesn’t dwindle even more.

Besides the corrections others have said, I really can’t think of any reason people would intentionally use legacy BIOS on a machine with UEFI for a new install.

Like, I could get doing it for an old install - I know someone who installed Windows 7 in 2015 on their then-new desktop build and later upgraded to 10 but is stuck on legacy BIOS for now with that machine because 7 only ran on that.

I could see something similarly jank happening to someone in the Linux world and then decide not to address it for “if it ain’t broke, don’t fix it reasons”, but certainly not for no reason.

I just ripped the Blu-Ray drive from my father’s PC since he wasn’t using it.

Since my machine doesn’t have 5.25” bays, I just have SATA cables dangling out the side of the case. I’ve probably ripped more CDs than Blu-Rays, though.

Do you have data on the Windows partition?

Either way, a good way to do it might be to use dd (or a different disk image tool) to copy your Linux installation partitions to a portable hard drive, and make sure the image works. Then wipe the drive and copy the Linux partitions back to it via dd or another imaging tool.