print something on a piece of paper.

It didn’t take long for having to buy 3 or 4 streaming services to replace cable became more expensive than cable.

Anyway, I have a poopdeck to scrub and a wooden leg to polish.

They might get interested if people start talking about Epstein again.

Sounds like a company that somehow has no boomers dragging it down.

This is happening because Linux is the default OS for servers, robots, machines, etc., it just sucks balls for normie personal computing, so they’ll use Winblows for the basic stuff, and WSL for the server-centric tasks.

Ubuntu can make it as toddler-centric as it wants, it won’t change the fact that eventually a person will find a thing their machine won’t do without an on-staff geek.

If they have heart, they’ll try chasing the black screen into the depths of google oblivion or use AI for infinitely recirculating bad advice. It’s ironic that a LLM running on a Linux server can’t fix Linux.

Most people will punt and go back to Microsucks which grows more evil and abusive every day.

I’m just mad I can’t get any of my file-management containers to work properly.

Firstly, I use linux for self hosting, and have a love-hate relationship for any other purpose. I’ve been trying to make the full transition since about 2009(?) and always end up back on the spyware-riddled Microswamp ad-delivery system.

I’m going to get downvoted for saying this, but if Linux could make hardware tasks as easy as Microsoft, namely printing, Windows would be a thing of the past.

I could put Mint on my 72 y.o.mom’s computer and she probably wouldn’t notice the difference until she had to do something dealing with hardware (connect a camera, or god forbid, print something). inb4 just use cups - My mom doesn’t gasf about dependencies, chown, and chasing terminal errors for 6 hours to print an agenda for the ladies’ church meeting and then have it break itself the next day. This is why it fails. Linux purists who don’t care that people don’t have time for CLI will disagree, and that is precisely what keeps things in the current state.

Thank you all for your input. ultimately I discovered that the volumes that had been stored inside docker’s directory (on WSL) were actually not the ones I was worried about losing.

My container directory where my compose files are categorized and stored turned out to have everything I really needed. It did take reducing the hashed docker internal volumes to tar.gz to figure that out.

Anyway, I just stopped (not “down”) docker and copied the directory onto one of my extra SSDs. Then I shut down the host, took out the Windows nvme, booted from my Debian SSD, made and mounted a new master container directory, and copied the files over. I had to update the compose and config files to use the new file paths, but once that was done, I did a compose up and everything took off pretty much without a hitch.

Bruh, being a conservative is all about missing the fucking point.