Thank goodness I had a newer monitor then, because I would definitely have toasted several.
Thank goodness I had a newer monitor then, because I would definitely have toasted several.
I’m so divorced from normalcy I have no frame of reference. Do normal people who don’t do this stuff for a living use Linux now, outside handheld gaming devices? I figured they just used whatever came on whatever device they wanted to buy.
Did you ever dual boot Linux and windows, and also have VMware installed in both so you could boot the other one from inside whichever you had booted? Because I spent an insane amount of time screwing around with that for as excruciatingly slow as it was back then.
You never know when you’ll need to install period Linux on an old piece of hardware.
I think you need to qualify that having used or tried Linux in college was normal in the 2000s for someone in computer science or engineering, or basically my fellow undiagnosed autistics and autistic adjacents. In my experience it was fairly normal in college for most people to have trouble operating a basic word processor, and they would not have had any idea what Linux was at all.
“mailing list and Usenet support”. Yeah. If you’ve ever looked up some weird issues and the only thing that you can come up with is some Debian message group that looks like it was typed on a typewriter, is extremely difficult to follow the response chain, and is apparently from before Y2K… That’s what it was like to run Linux back then.
How wrong did you have to be to break your monitor? Because I’m positive I got it very wrong a whole lot of times and never managed that.
Yeah, and I assume future me will be even dumber than present day me, so I try to make it really easy for him to find out what he needs to know.
Another good tip is to put timestamps and increase the length of your bash history. That way when I log in half a year from now I’ll know what I was up to.
All of your issues can be solved by a backup. My host went out of business. I set up a new server, pulled my backups, and was up and running in less than an hour.
I’d recommend docker compose. Each service gets its own folder inside your docker folder. All volumes are a folder in the services folder. Each night, run a script that stops all of them, starts duplicati, backs up to a remote server or webdav share or whatever, and then starts them back up again. If you want to be extra safe, back up to two locations. It’s not that complicated if it’s just your own services.
There’s no forgetting where I have something hosted. If I ssh to service.domain.tld I’m on the right server. My services are all in docker compose. All in a ~/docker/service folder, that contains all the volumes for the service. If there’s anything that needed doing, like setting up a docker network or adding a user in the cli, I have a readme file in the service’s root directory. If I need to remember literally anything about the server or service, there’s an appropriately named text file in the directory I would be in when I need to remember it.
If you just want a diagram or something, there are plenty of services online that will generate one in ASCII for you so you can make yourself a nice “network topology” readme to drop in your servers’ home directory.
Landlords are familiar with utility install people and how unpredictable they can be. Even if they get mad, this will put the blame squarely on someone else so it’s probably a good option for you. “I dunno why he put it there. You know how utility guys are. It’s the only place he’d put my hookup.”
Second this. Landlords don’t want their stuff screwed up by inexperienced tenants’ diy projects, and they don’t want to pay for something they think it’s unnecessary. I’d get an estimate for a pro to do it (could be a guy off Craigslist or whatever, just someone who does this for a living) and then just ask the landlord if they’d be alright with you paying to get it done. They’ll probably want to know exactly what they’re going to do, and they’ll likely say yes, especially since you say they already have coax running through the house.
I’m glad you’re happy with Linux. Sometimes I find it hard to believe that things have progressed that far. I’m stuck with the feeling that gui settings and such aren’t reliable, because they didn’t used to be. Moreso, I just know how to do things in the terminal because that’s how I’ve done them for decades.
But you do you. Its great to have options.
I’ve not had a problem with nextclouds experimental selective sync. Have you tried clearing all your nextcloud dotfiles and setting it up from scratch?
I recommend the Thinkpad yoga 11e, which is their education edition. They’re out of stock at the moment, but they’ll come back soon. They always do. It’s an 11 inch laptop with a flip around touch screen and integrated stylus. Works perfectly with Linux. It’s not super fast, but it’s under 300 dollars new. And it’s made for kids so it’s durable. I have one and I love it. You can get one used if you like, but at that point you’re probably better off with an older model.
Great marketing. Debian’s idea of unstable is more stable than everyone else’s unstable.
I hope someone gives you a good answer, because I’d like one myself. My method has just been to do this stuff little by little. I would also recommend calibre web for interfacing instead of calibre. You can run both in docker, and access calibre on your server from whatever computer you happen to be on. I find centralizing collections makes the task of managing them at least more mentally manageable.
You might want to give an idea of the size of your library. What some people consider large, others might consider nothing much. If it is exceedingly large you’re better off asking someplace with more data hoarders instead of a general Linux board.