Blaster M

Meanwhile in Fedora KDE, I have the opposite problem… The system straight up ignores my monitor sleep settings, and something as quick as grabbing a water and coming back to everything in sleep mode on a desktop is kinda a problem when I am relying on the system not going sleep due to a running task.

Here’s the deal. If your server is close to using up all its RAM, then yes, more RAM better.

However, if your server is close to being full on storage, you need to address that with a bigger storage drive.

Yeah no, I’ve used Slackware back in the day… there is no getting back the whole weekends lost chasing dependencies and build dep reqs.

UniGet GUI

Looks like I need to consider flipping back to Debian again… it’s always beeen a Stable relationship…

The factory must grow

How about running an Opnsense VLAN routed through the VPN, so your PC doesn’t have to have a client side VPN app and just assumes by normal router function its WAN IP is the VPN IP, and being in an isolated VLAN it is a device that lives solo on its own little network.

The reason I have been switching my systems over to Fedore KDE is because of Wayland

I was fine with LXDE… until it got abandoned for LXQt… which is alright, but it’s more “kit car hackjobby” in its presentation than LXDE.

Everywhere except in the USA’s Republican states. It’s an unforgiveable sin to be seen with a mask on there for stupid reasons.

I would that too

Pretty much… as long as you didn’t do any custom kernel stuff or driver blacklisting or any other underhood voodoo with the boot system.

That only matters if there’s anything to optimize by source compilation. If the program doesn’t have optimization features in the source, it’s wated time and energy.

LCARS interface… that is something I haven’t seen in a loooooooong time

Ah, yes, Linux around the turn of the century. Let’s see…

GPU acceleration? In your dreams. Only some cards had drivers, and there were more than 2 GPU manufacturers back then, too… We had ATi, nVidia, 3dfx, Cirrus, Matrox, Via, Intel… and almost everyone held their driver source cards close to their chest.

Modems? Not if they were “winmodems”, which had no hardware controller, the CPU and the Windows driver (which was always super proprietary) did all the hard work.

Sound? AC’97 software audio was out of the question. See above. You had to find a sound blaster card if you wanted to get audio to work right.

So, you know how modern linux has software packages? Well, back then, we had Slackware, and it compiled everything gentoo style back then. In addition, everyone had a hardon for " compiling from source is better"… so your single core Pentium II had to take its time compiling on a UDMA66-connected hard drive, constrained with 32 or 64 MB RAM. Updating was an overnight procedure.

RedHat and Debian were godsends for people who didn’t want to waste their time compiling… which unfortinately was more common even so, because a lot of software was source only.

Oh, and then MP3 support was ripped out of RedHat in Version 9 iirc, the last version before they split it into RHEL and Fedora. RIP music.

As for Linux on a Mac, there was Yellowdog, which supported the PPC iMacs and such. It was decently good, but I had to write my own x11 monitor settings file (which I still have on a server somewhere, shockingly, I should throw it on github or somewhere) to get the screen to line up and work right.

Basically, be glad Linux has gone from the “spend a considerable amount of time and have programming / underhood linux knowledge to get it working” to “insert stick, install os, start using it” we have now.

What’s actually happening here is Windows is setting its bootloader first in your EFI when it gets updated. Linux isn’t gone, you just have to press the “boot another drive” button and boot to it, or go into your EFI setup and switch the bootloader back to the Linux one.

Linuxes do the same thing when updating their bootloader.

Note for the Ackshually crowd: If you’re still booting MBR (which comes with the partition eating risk on dual boots) you have a system that is older than Windows 8 - 11+ years old, so eating the MBR is something you’ll have to deal with unconventionally, as all modern systems, OS, and hardware expect you to be using EFI.